SynapseCommand and NIRIS Track Distribution
NIRIS is one of the systems named in NATO acquisition documentation as a source of track data for the Alliance common operational picture. Public information about it is thin, and this page says only what that documentation supports.
What NIRIS is
The single public reference identified for NIRIS is in the interface documentation issued with the NATO acquisition for the common operational picture and ballistic missile defence capability. In that document NIRIS appears as a provider of track data to the picture, through a named application interface.
No public source located here gives an expansion of the name, states which NATO body owns or operates it, defines its scope, or lists the data formats it uses. Its role in track distribution is therefore inferred from a single line in an interface table and nothing more.
That is unusual for a page on this site, and it is stated openly rather than concealed behind confident prose. Where a system's public record is this thin, the correct engineering response is to make the uncertainty visible.
Your C2 stays. SynapseCommand adds the decision layer.
Track distribution is a natural input to SynapseCommand. The canonical data model exists precisely to hold tracks from heterogeneous sources with their timing, provenance and confidence intact so that ISR fusion can reason across them.
In principle, a track feed of this kind would be consumed by the ISR fusion agent and contribute to the same picture the mesh reasons over. That is a statement about SynapseCommand architecture, not about NIRIS.
In practice nothing can be designed against an interface whose specification is not available. A connector would be scoped with a customer who has authorised access to the system and its documentation.
- 01NIRIS track sourceReferenced in NATO acquisition documentation as a track provider. Scope not publicly defined.
- 02Authorised data exchangeInterface specification not publicly available. Scoped with the customer holding access.
- 03SynapseCommand integration layerPublished contract and validated JSON Schema on the SynapseCommand side.
- 04Canonical data modelTracks held with source, timing, classification and confidence.
- 05ISR fusion agentReasoning across tracks from multiple contributing sources.
- 06Analysis and optionsFused understanding feeding option development where relevant.
- 07Human decision gateAuthorised human decision authority, as everywhere else in the platform.
- 08Decision record and replayWhat the track picture showed at the time, preserved for later review.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Track fusion with provenance
Tracks from several contributing sources are reconciled into single entities that keep a history, rather than being overwritten by whichever report arrived last.
Confidence and age carried forward
An entity derived from a track is presented with how old it is and how strongly it is held, because a stale track rendered as current is a hazard.
Disagreement made visible
Where contributing sources conflict, the conflict is surfaced to the analyst instead of resolved silently in favour of one source.
How the decision cycle runs
Ingesting a track feed
A track feed enters the canonical data model, where timing and provenance are preserved so later reasoning can be audited back to the report.
Contributing to fused understanding
The ISR fusion agent reasons across track sources, and its contribution to any conclusion remains separately attributable.
Supporting review
Because the track state at a moment is recorded, a later review can examine the picture as it was rather than as it became.
What is claimed, and what is not
A dedicated connector can be developed for a customer, integration programme or deployment.
Public information about NIRIS is very limited. It appears in NATO acquisition documentation as a source of track data to the common operational picture capability, through an interface named in that document. No public source defines its scope, owner or data formats, so no integration claim beyond a connector developed on request can be supported.
Qualification
This status describes what could be developed for a customer or programme. It does not imply NATO certification, endorsement or a completed deployment, and this page does not assert capabilities of NIRIS that public sources do not establish.
Interfaces and data standards
No data standard has been publicly documented for NIRIS in the sources reviewed. The interface named in NATO acquisition documentation is not publicly specified. SynapseCommand therefore claims no supported interface for this system, and any work would begin with documentation supplied by an authorised customer.
The SynapseCommand data contract is published for inspection in the open integration layer.
Open interoperability layer
SynapseCommand connects to external systems through an openly published interoperability layer rather than proprietary point interfaces. The canonical data model, the JSON Schema and the format adapters are inspectable before any integration is committed to. That layer describes what SynapseCommand implements; it is not a statement about NIRIS and implies no interface to it.
Public sources
- NATO Communications and Information Agency
- NCI Agency invitation for bid IFB-CO-115461 (NCOP/BMD), interface annex naming NIRIS as a track source
Factual statements about the named system on this page are drawn from these public sources.
Frequently asked
- Why is this page shorter than the others?
- Because the public record for NIRIS is thin. Padding the page would mean inventing detail about a NATO system, which is exactly what this site does not do.
- Is there a NIRIS connector?
- No. The status is available on request. A connector would be scoped with a customer who holds authorised access to the system and its interface documentation.
- What could SynapseCommand do with a track feed of this kind?
- Hold the tracks in the canonical data model with provenance intact and reason across them with the ISR fusion agent, contributing to a fused picture that supports option development.
- Is any of this NATO endorsed?
- No. Nothing on this page implies NATO certification, endorsement, approval or partnership.
Where to go next
Relevant use cases
Assurance and architecture
Discuss an integration
Briefings are available under NDA. SynapseCommand® integration work begins from the published data contract, so the interface can be reviewed before any commitment.
Third-party systems and trademarks
Product names, trademarks and registered trademarks referenced on this site are the property of their respective owners. References to third-party systems describe implemented, planned or potential technical interoperability as stated on each page and do not imply sponsorship, certification, endorsement or partnership unless expressly stated.
Category: NATO command and control. Last reviewed 2026-09-06.