Overview#
NFFI / STANAG 5527 ingestion lets any NATO-conformant system push own-force and coalition unit positions into Argus and fuse them with the wider operational picture in seconds.
Friendly Force Information is the NATO standard for sharing the location, identity, and status of own and allied units between national command-and-control systems. In a multi-partner coalition operation, every nation runs its own tracking system, and the single hardest question on the watch floor remains "where are my people right now". Argus answers it by accepting NFFI track updates from any STANAG 5527 producer and persisting them to a position store scoped to your organisation, ready for the recognised picture without a bespoke national bridge.
Each track carries a track ID, a MIL-STD-2525 symbol code, a callsign, an affiliation, a geospatial position with altitude, speed, heading, a timestamp, and a secrecy level. Once ingested, those tracks sit alongside Link-16 air tracks, ATAK ground positions, and radar detections on one multi-tenant picture, so commanders see friendly forces and the threat picture in the same view rather than across disconnected screens.
Last Reviewed: 2026-05-26 Last Updated: 2026-05-26
Key Features#
- STANAG 5527 Track Ingestion: Accept friendly-force position updates from any NFFI-capable producer through a single ingest entry point, with no custom transport to build per national system.
- MIL-STD-2525 Symbology: Every track carries a Common Warfighting Symbology symbol code, so units render with the correct affiliation and role on any standards-aware map client.
- Full Track Detail: Persist track ID, identity, callsign, affiliation, latitude, longitude, altitude, speed, heading, and timestamp for each unit, giving operators a complete movement record rather than a bare dot.
- Organisation-Scoped Store: Tracks are written to a position store partitioned by the authenticated organisation, keeping each tenant's friendly-force picture isolated by default.
- Clearance-Level Filtering: Returned tracks are filtered against the requesting analyst's clearance, so UNCLASSIFIED, RESTRICTED, SECRET, and TOP SECRET positions surface only to cleared users.
- Affiliation Statistics: A counts-by-affiliation summary gives watch staff an at-a-glance breakdown of friendly, neutral, and other tracked units in the current picture.
- Coalition Picture Fusion: Each ingested track is emitted as an operational entity in the coalition domain, fusing it automatically with air, land, and sensor feeds on the common operational picture.
- Tamper-Evident Audit: Every ingest writes an audit record naming the standard, the track, the acting user, the organisation, and the secrecy level, supporting accountability reviews and exercise reconstruction.
Use Cases#
Coalition Operations#
A multinational task force runs national tracking systems that have never spoken to one another. Each nation points its NFFI producer at Argus, and within minutes the combined friendly-force picture appears on one shared map, letting the force commander deconflict movement and avoid fratricide without waiting on liaison voice reports.
National Command and Control#
A national C2 programme team needs own-force positions fused with the threat picture rather than displayed in a separate stovepipe. NFFI tracks ingested into Argus sit next to Link-16 air tracks and radar detections, so the duty watch sees friendly units and contacts in a single recognised picture.
Multi-Coalition-Partner Deployments#
Partners operating at different classification levels share a deployment but not the same need-to-know. Clearance-level filtering ensures each partner's analysts see only the tracks their credentials permit, satisfying NATO need-to-know rules while still contributing to a common picture.
Exercise and After-Action Review#
During a combined exercise, ingested friendly-force tracks and their audit records provide a complete, time-stamped movement history. Planners replay the picture afterwards to reconstruct timelines, validate coordination, and capture lessons learned.
Integration#
Friendly-force tracks flow in and out of Argus over GraphQL. Producers post position updates through the ingestNffiTrack mutation, while watch staff and analysts read the picture through the nffiTracks and nffiStats queries. Every operation runs under OAuth2 with JWT bearer credentials and is scoped to the caller's organisation, so authentication and tenancy are enforced on the first call rather than bolted on later.
Tracks are normalised into a shared position model the moment they arrive, which is what allows a single NFFI feed to fuse with Link-16 air tracks, ATAK ground positions, GMTI radar detections, and effector-matching workflows without per-source glue code. Customers plug in any STANAG 5527-conformant system as a producer and consume the fused picture over the same GraphQL endpoint, or wire ingest events into downstream tooling through webhooks and connectors. The benefit is direct: one integration, and friendly-force position data becomes a first-class layer of the common operational picture.
Open Standards#
- NATO STANAG 5527 (Friendly Force Information / NFFI): The track ingestion and read model conform to STANAG 5527, the NATO standard for exchanging own-force and coalition unit positions between national systems.
- MIL-STD-2525 (Common Warfighting Symbology): Each track carries a MIL-STD-2525 symbol code in its symbol field, so units render with the correct affiliation and role on any symbology-aware client.
- OAuth2 and JSON Web Token (JWT): All ingest and read operations authenticate with OAuth2 bearer tokens carried as JWTs, the open standards for delegated authorisation and signed access claims.
- GraphQL: The ingest mutation and read queries are exposed over GraphQL, the open specification for typed application interfaces.
Security & Compliance#
NFFI track access is governed by clearance-level filtering applied after every read, so tracks classified UNCLASSIFIED, RESTRICTED, SECRET, or TOP SECRET are returned only to analysts whose credentials match or exceed the track's secrecy level. This enforces NATO need-to-know across coalition partners operating at different classifications in the same deployment.
Every ingest call is recorded to a tamper-evident audit trail that names the source standard, the track, the acting user, the organisation, and the secrecy level. Combined with strict organisation scoping on all reads and writes, this gives programme teams the accountability evidence and tenant isolation expected in a defence-grade deployment.