Overview#
A major incident commander needs to know, right now, which ambulances are available and within ten minutes of the scene, which equipment caches are stocked with trauma supplies, and whether the mobile command post is in maintenance or ready to deploy. The Resource domain answers those questions. It maintains a live catalogue of every organisational asset, tracks each asset's status and location, and exposes the data through an API that dispatch and planning systems can query the moment a need arises.
Key Features#
-
Resource Catalog: Maintain a comprehensive inventory of all organisational assets with clear categorisation by type, including equipment, personnel, vehicles, facilities, and consumable supplies.
-
Availability Tracking: Monitor resource status in real time with statuses such as Available, In Use, Maintenance, Reserved, and Unavailable, so dispatchers and managers always know what is ready for deployment.
-
Location Awareness: Associate each resource with a geographic location for spatial awareness and track movement history as resources are relocated across sites.
-
Programmable API Access: Integrate resource data with other systems through a structured API that supports creating, retrieving, and listing resources with full filtering capabilities.
Use Cases#
Resource tracking applies wherever teams must coordinate physical assets across multiple locations under time pressure. Industries served include emergency services, defence and security operations, and healthcare logistics.
-
Emergency Response: Quickly identify which vehicles, personnel, and equipment are available and closest to an incident for rapid deployment.
-
Operational Planning: Review the full resource inventory before large operations to ensure adequate coverage and identify gaps.
-
Fleet Management: Track vehicle availability, maintenance schedules, and current assignments to optimise fleet utilisation.
-
Facility Coordination: Manage rooms, buildings, and staging areas to ensure physical spaces are reserved and available when needed.
Resource Types#
| Type | Description | Examples |
|---|---|---|
| Vehicle | Fleet vehicles | Patrol cars, trucks |
| Equipment | Hardware and tools | Radios, laptops |
| Personnel | Human resources | Officers, analysts |
| Facility | Physical locations | Buildings, rooms |
| Consumable | Expendable items | Supplies, fuel |
Integration#
The Resource domain connects with the broader platform to support coordinated operations:
- Location Services: Geographic context for resource placement
- Staffing: Personnel management and scheduling
- Asset Tracking: Detailed asset lifecycle management
- Dispatch: Resource allocation during active incidents
Open Standards#
- GraphQL (June 2018 specification): All resource catalogue queries and mutations are exposed through a strongly typed GraphQL API, with named types, input types, and per-field permission enforcement.
- OAuth 2.0 / OpenID Connect (RFC 6749 / OpenID Connect Core 1.0): Every resource endpoint requires a verified bearer identity resolved by the platform's authentication and role-based access control checks before any data is returned or written.
- ISO 8601 / RFC 3339: All timestamps are stored and exchanged as timezone-aware UTC datetimes serialised in ISO 8601 format.
- RFC 4122 (UUID): Every resource, zone, plan, allocation, movement, and assessment record is identified by a version-4 UUID primary key, ensuring globally unique identifiers without a central registry.
- WGS 84 (EPSG:4326): Pre-positioning zones carry decimal-degree latitude and longitude coordinates conforming to the WGS 84 geodetic datum, enabling interoperation with any standard mapping or geospatial service.
- OASIS EDXL-SitRep 1.0: Resource status records from this domain can be serialised into EDXL-SitRep 1.0 XML envelopes for federated distribution to partner agencies.
- IETF RFC 8259 (JSON): Resource records and API payloads are exchanged as JSON throughout the service layer, conforming to the IETF JSON specification for interoperable structured data exchange.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14