SynapseCommand Integration with the NATO Common Operational Picture
NCOP is the Alliance capability for bringing a shared operational picture together and distributing it. SynapseCommand is designed to work from a picture of that kind rather than to produce one, adding analysis, options and an inspectable decision record on top of the command system already in place.
What NCOP is
The NATO Common Operational Picture is described in NATO acquisition material as a capability that brings battlespace object information together from other functional area services, reconciles it and republishes a single shared picture for Alliance staff. It is procured through the NATO Communications and Information Agency, and it is treated in that documentation as a hub rather than as an originating sensor system.
The publicly released interface documentation for the NCOP and ballistic missile defence acquisition tabulates inbound interfaces from other Alliance systems, including maritime, logistics, land, planning and track distribution services. The exchange mechanisms named there are service interfaces and Alliance information exchange formats rather than a single public API, and several of the listed interfaces are marked in the source document itself as still to be confirmed.
There is no dedicated first-party public product page for NCOP. What is publicly known therefore comes from acquisition and interface documentation, and this page deliberately stops where that documentation stops. Nothing here describes access that Decent Cybersecurity holds, an interface it has implemented, or a deployment it has completed.
Your C2 stays. SynapseCommand adds the decision layer.
SynapseCommand is not a common operational picture and is not a candidate to replace one. A COP answers what is where and when. The decision work that follows, comparing options against constraints and recording why one was chosen, is what the agent mesh exists to support.
In an authorised deployment SynapseCommand would consume picture data as an input, normalise it into the canonical data model so that source, timing, classification and confidence survive the journey, and return analytical products to the staff who already work from the shared picture.
The honest limit is the interface. SynapseCommand publishes an open REST and gRPC contract with a validated JSON Schema, which is what an integration would be built against on the SynapseCommand side. The Alliance-side exchange mechanisms named in NCOP documentation are not implemented in SynapseCommand today, and an integration would begin by agreeing that path with the authority that owns it.
- 01NATO Common Operational PictureExisting Alliance capability, unchanged and authoritative for the shared picture.
- 02Authorised data exchangeInterface to be agreed with the owning authority. Not implemented, not assumed.
- 03SynapseCommand integration layerPublished, inspectable contract: REST, gRPC and a validated JSON Schema.
- 04Canonical data modelSource, timing, classification and confidence preserved on every entity.
- 05Specialist agentsISR fusion, friendly force reasoning and course-of-action analysis.
- 06Analysis and course-of-action workOptions developed against stated constraints and compared on explicit criteria.
- 07Human decision gateThe commander or authorised operator decides. Always.
- 08Decision record and replayAppend-only record of what was known, what was recommended and who approved it.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Understanding, not just display
A shared picture shows what is present. The agent mesh reasons about what it means, keeping the provenance and age of every contributing entity attached to the conclusion.
Multi-agent analysis
Several specialist agents examine the same picture in parallel and each contribution remains separately attributable, so a conclusion can be traced to the reasoning that produced it.
Course-of-action development and comparison
Options are generated against stated constraints and compared on criteria the staff can see, rather than presented as a single unexplained recommendation.
Decision record and replay
What was known at the moment of decision is recorded and can be replayed afterwards, which matters when a picture that has since moved on is being reviewed.
Human decision gates
Material decisions require an authorised human decision-maker, and the authorisation is part of the record rather than an afterthought.
How the decision cycle runs
Exploiting the shared picture
Staff working from a fused picture rarely lack data. They lack time to interrogate it. Agents work through the picture continuously and surface what has changed materially rather than what has changed at all.
Building situational understanding
Entities arriving from different contributing systems carry different ages and confidence. Normalising them into one model makes disagreement visible instead of averaging it away.
From picture to options
Once a situation is understood, options are developed and compared against the constraints that actually apply, with the reasoning attached to each one.
Review after the fact
The decision record allows a headquarters to reconstruct what the picture showed at a given moment, which is a different question from what the picture shows now.
What is claimed, and what is not
SynapseCommand is architecturally capable of integrating with the system, but the specific system has not undergone validated end-to-end testing.
NCOP is publicly documented in NATO acquisition material as a picture fusion and distribution capability that exchanges data with other functional area services over service interfaces. SynapseCommand is architecturally capable of consuming and returning that class of data through its published contract, but no connector for NCOP has been built and no end-to-end testing with the system has taken place.
Qualification
This status describes SynapseCommand integration architecture only. It does not imply NATO certification, NATO endorsement, an accredited interface or a completed deployment with NCOP. Any integration would require authorised access to NATO interfaces, data and deployment environments.
Interfaces and data standards
SynapseCommand supports ASTERIX, STANAG 4676, STANAG 4607, Cursor-on-Target, AIS, ADS-B, REST and gRPC. None of those has been publicly documented as an NCOP interface, so none is claimed here. The interfaces named in NCOP acquisition documentation are Alliance service interfaces and information exchange formats that SynapseCommand does not currently implement. The integration path would be defined with the owning authority rather than assumed from this page.
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 NATO Common Operational Picture 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
Factual statements about the named system on this page are drawn from these public sources.
Frequently asked
- Does SynapseCommand replace NCOP?
- No. NCOP remains the authoritative shared picture. SynapseCommand adds a decision layer alongside it and produces no command and control picture of its own.
- Is there a working NCOP connector today?
- No. The status is integration-ready, which means SynapseCommand is architecturally capable of working with this class of data. No NCOP connector has been built and no end-to-end testing with the system has taken place.
- What would a NCOP integration actually require?
- Authorised access to the relevant NATO interface and deployment environment, agreement on the exchange mechanism with the owning authority, and then adapter work against the published SynapseCommand contract, followed by testing.
- Is this integration NATO certified or endorsed?
- No. Nothing on this page implies NATO certification, endorsement, approval or partnership. It describes SynapseCommand architecture and publicly documented information about NCOP.
- Can SynapseCommand run inside a sovereign environment alongside it?
- Yes. SynapseCommand is designed for deployment up to NATO SECRET, runs disconnected, and makes no external AI calls, so the analysis stays inside the environment that holds the data.
Where to go next
Relevant use cases
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.