Overview#
Stations, warehouses, caches, and facility stores hold kit against organisational locations. Logistics staff, supervisors, and auditors need to answer a simple question quickly: who holds inventory at this facility? When the only answers are typed UUIDs, unbounded global lists, or spreadsheets exported last quarter, transfers go wrong and audits start with an apology.
Facility Holder Inventory Search is a tenant-safe query that returns holders associated with a chosen facility. It feeds pickers in transfer, issue, and audit workflows, matching the wider platform move toward selection UIs that replace raw identifier typing. Cross-tenant leakage is treated as a defect: automated checks assert facility holders stay invisible across tenants.
For defence, emergency, and utilities customers who already model facilities in Argus, this module is the inventory counterpart to geographic and workforce pickers elsewhere in the suite.
Last Reviewed: 2026-09-15 Last Updated: 2026-09-15
Key Features#
-
Facility-scoped lookup: Queries require facility context so results are about a site, not a platform-wide dump of holders.
-
Tenant isolation: Holders from other tenants never appear. Tests encode that invisibility as a regression gate.
-
Picker-ready payloads: Responses fit selection components used across fe2 and mobile flows that retired typed UUID fields.
-
Empty-facility honesty: Facilities without holders return a clear empty state rather than recycling unrelated global hits.
-
Downstream mutation safety: Callers receive holder identities they are allowed to use in subsequent transfer or issue operations under the same tenant scope.
Use Cases#
-
Station equipment issue: A fire or ambulance supervisor searches holders for their station before issuing kit to a crew.
-
Inter-site transfer: Logistics locates the holding account at the destination facility before confirming a stock move.
-
Audit preparation: Inventory controllers list holders at a facility ahead of a spot check or regulatory visit.
-
Defence and coalition logistics: Facility-scoped search respects tenant boundaries in multi-organisation deployments.
Integration#
Inventory and facility services provide the underlying records. argus_middleware exposes the facility holder search query to authorised GraphQL clients. fe2 and workforce UIs consume results in pickers. auth_service and middleware enforcement keep tenant scope intact on every call.
Open Standards#
- GS1 / GLN (Global Location Number): Facility identity can align with GLN-style location codes when customers maintain them.
- ISO 55000 asset management: Holder search supports the location aspect of asset accountability.
- GraphQL: Client integration uses the platform GraphQL surface with ordinary auth headers.