Overview#
Connect an existing NATO-NICS deployment to Argus with a single authenticated call, so every annotated map feature and in-room message becomes searchable intelligence on your shared operational picture within seconds. NATO-NICS (the Next-Generation Incident Command System) is the open-source collaborative situational awareness suite developed across the DoD and NATO community, used by first-responder agencies, emergency operations centres, and coalition military commands to share live maps, overlays, and messaging within collaborative rooms.
Argus provides a bi-directional bridge to NICS. Once a room is linked, its GeoJSON map features and messages are pulled into a governed store, indexed for search, and promoted onto the same common operational picture that already carries your Link-16 air tracks, ATAK ground positions, and sensor fusions. There is no manual re-keying of incident data and no separate login for analysts to maintain. Annotations made by responders in NICS appear alongside every other operational source, and new features generated in Argus can be pushed straight back into the live NICS room so that the people on the ground see them too.
Clearance-level filtering is applied to every read, which means a mixed-classification workforce can safely work from the same multi-classification room without exposing records above an individual's authorisation. Every pull from NICS and every push back to it is written to an immutable interoperability audit trail, giving incident commanders and compliance teams a complete, attributable record for post-incident review.
Key Features#
- One-call room linking. A single authenticated GraphQL operation links a NICS collaborative room to Argus, pulling its features and messages into the governed store in one round trip and returning a summary of exactly how many records were ingested.
- Bi-directional GeoJSON exchange. Map features flow both ways. Geometry annotated in NICS is ingested as standard GeoJSON, and analysts can publish new GeoJSON features from Argus back into the live NICS room so responders see them in place.
- In-room message ingest. Text messages exchanged within a NICS collaborative room are captured alongside the map data, giving analysts the conversational context behind every overlay and annotation.
- Promotion to the shared operational picture. Each linked room is surfaced as a coalition mission-context entity on the operational dashboard, so incident workspaces appear next to air, ground, and sensor sources without any extra configuration.
- Clearance-level enforcement on every read. Rooms, features, and messages are filtered against the requesting user's clearance, making multi-classification rooms safe to expose to a mixed-classification workforce.
- Full ingest and export audit trail. Every pull from and push to a NICS deployment is recorded with the acting user, organisation, record reference, and classification, satisfying post-incident review and accreditation requirements.
- Organisation-scoped persistence. Ingested NICS data is stored per organisation and served from that governed store rather than re-fetched on demand, so search and operational-picture views stay fast and consistent.
- Aggregate statistics at a glance. A single statistics query returns the total number of linked rooms, ingested features, and captured messages for the organisation, giving operations staff an immediate sense of coverage.
Use Cases#
Emergency Operations Centres#
An emergency operations centre running NICS during a wildfire or flood links each active incident room to Argus. Evacuation zones, road closures, and resource positions drawn by field teams in NICS become immediately searchable and appear on the centre's shared picture next to weather feeds and sensor data, giving command staff a single screen for the whole response.
First-Responder Agencies#
Police, fire, and medical services collaborating in shared NICS rooms gain a unified view across agencies. Annotations made by one service are visible to all participants on the Argus operational picture, while message history preserves the decision trail for after-action reporting.
Coalition and Joint Military Commands#
A coalition command already operating NICS for shared situational awareness connects it to Argus so that incident overlays sit alongside Link-16 tracks, ATAK ground positions, and fused sensor detections. Clearance-level filtering allows partners of differing classifications to draw from the same rooms without over-disclosure.
Multi-Classification Workforces#
Organisations with analysts at several clearance levels can open the same NICS rooms to the whole team. Each person sees only the features and messages their clearance permits, removing the need to silo data into separate rooms for separate audiences.
Integration#
Argus exposes the NICS capability through its GraphQL surface, secured with the platform's standard OAuth2 and JWT authentication and scoped to the caller's organisation. Read operations cover collaborative rooms, map features, in-room messages, and aggregate statistics. Write operations cover linking a room (which performs the pull and persistence) and publishing a feature back to a live room. Each operation carries clear, descriptive field names so client teams can wire up dashboards and automations quickly.
Under the bridge, an asynchronous REST connector talks to the NICS deployment over its open API, reading from /collabroom, /collabroom/{id}/features, and /collabroom/{id}/messages, and posting new features and messages to the same room endpoints. A customer plugs in nothing more than the base URL of their NICS deployment and an optional bearer token. The benefit is immediate: an existing NICS environment becomes a first-class, searchable, audited data source on the Argus operational picture with no bespoke development on the customer side. Ingested records are normalised into a common operational model so that NICS features sit consistently beside every other connected source, and the same interoperability bridge that handles Link-16 and ATAK governs NICS, so behaviour is identical across channels.
Open Standards#
- GeoJSON (RFC 7946): The geometry interchange format for map features, used both when pulling annotations in from a NICS room and when publishing new features back to it, so geospatial data round-trips without lossy conversion.
- NATO-NICS REST API: The open-source DoD and NATO collaborative situational awareness platform (github.com/NATO-NICS, spanning more than thirteen repositories); Argus interoperates with its collaborative-room, features, and messages endpoints to read and write incident data.
- GraphQL: The strongly typed read and write surface for the capability, exposing rooms, features, messages, and statistics for reading, plus room-linking and feature-publishing operations for writing, all under a single authenticated, organisation-scoped contract.
- OAuth2 and JWT: Bearer-token authentication and authorisation applied to every NICS operation, aligning the capability with the platform-wide identity model used across all Argus integrations.
Security & Compliance#
Every NICS operation requires authentication and is scoped to the caller's organisation, so one tenant can never read or write another tenant's incident data. Reads of rooms, features, and messages are filtered against the requesting user's clearance level, which makes multi-classification rooms safe to expose to a mixed workforce without leaking records above a user's authorisation. Both directions of data movement are recorded on an immutable interoperability audit trail that captures the acting user, organisation, the affected record, the classification, and, for outbound publishes, the destination deployment. That trail provides the attributable, tamper-resistant evidence base needed for post-incident review, accreditation, and ongoing compliance reporting.
Last Reviewed: 2026-05-26 Last Updated: 2026-05-26