SynapseCommand and the NATO Maritime Command and Control Information System
MCCIS has been the Alliance maritime command and control information system for a long time, gathering the maritime picture for maritime component commanders. SynapseCommand is designed to add maritime decision support alongside a capability of that kind, and this page is deliberately cautious about what is publicly known.
What MCCIS is
MCCIS was procured through the Alliance technical agency that preceded the NATO Communications and Information Agency and has been described as the command and control tool of choice for NATO maritime component commanders, merging information from satellite, network, tactical data processing and message sources into a maritime picture.
Its current programme position is genuinely unclear from public material. One supplier states that a replacement interoperable services capability has been delivered in place of MCCIS at a NATO command, while NATO has separately sought industry input relating to a maritime command and control information system under a closely similar designation. Public sources do not settle whether that represents a rename, a successor or a parallel effort.
NATO acquisition documentation for the common operational picture capability records MCCIS as a contributor of maritime overlays and tracks to that picture. That is the extent of the interface detail identified in public sources, and no further technical characteristics are asserted here.
Your C2 stays. SynapseCommand adds the decision layer.
The maritime problem is rarely a shortage of tracks. It is deciding which of many vessels behaving unusually deserves attention, and being able to justify that judgement afterwards.
SynapseCommand would take maritime picture data as an input, hold it in the canonical data model with its source and timing intact, and apply agent analysis to behaviour over time rather than to a single position report. The maritime command system remains the authority for the picture.
Because the target system is ambiguous in public documentation, the honest position is that a connector would be developed for a specific customer, programme or deployment against whatever interface that customer is authorised to expose. Nothing has been built in advance.
- 01Alliance maritime command systemExisting capability and authority for the maritime picture.
- 02Authorised maritime data exchangeInterface defined per deployment with the owning authority. Not implemented in advance.
- 03SynapseCommand integration layerPublished contract and validated JSON Schema, inspectable before any work starts.
- 04Canonical data modelVessel tracks and reporting retained with source, timing and confidence.
- 05Specialist agentsISR fusion and course-of-action analysis applied to maritime behaviour over time.
- 06Analysis and optionsAnomalies raised with the evidence that supports them, and response options compared.
- 07Human decision gateMaritime decisions rest with the commander or authorised operator.
- 08Decision record and replayAppend-only record supporting later scrutiny of a maritime judgement.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Behaviour over time
Maritime signals are slow. Agents reason across a track history rather than a snapshot, which is where anomalies actually become visible.
Anomaly triage with evidence
Something raised for attention arrives with what supports it, so a watch officer can dismiss it quickly when it does not hold up.
Response option comparison
Where a response is warranted, options are compared on explicit criteria including the cost of being wrong.
Decision record and replay
Maritime decisions are frequently reviewed long afterwards. The record preserves what was known at the time rather than what is known now.
How the decision cycle runs
Maritime situational awareness
Reporting from several sources is reconciled into one model so that a vessel is one entity with a history, not several entries that happen to agree.
Watch floor triage
Continuous analysis reduces a large picture to the handful of contacts that merit a human look, with the reasoning attached to each.
Naval decision support
Where action is considered, options are developed against sea state, presence, legal constraint and available units as stated by the staff.
Post-event review
The replay supports the review that follows any maritime incident, which is where an undocumented judgement usually becomes a problem.
What is claimed, and what is not
A dedicated connector can be developed for a customer, integration programme or deployment.
MCCIS is long established as an Alliance maritime command and control information system, but its current programme position is not clear from public sources: one supplier account describes a replacement capability delivered in its place, while NATO has separately sought industry input on a maritime command and control information system under a similar name. Because the target system itself is ambiguous in public documentation, no integration claim beyond a dedicated connector on request is appropriate.
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 it does not assert which maritime capability is currently in Alliance service.
Interfaces and data standards
SynapseCommand supports AIS and other maritime relevant inputs through its published contract. No public source establishes AIS, Link series messaging or any other named standard as an MCCIS interface, so no such interface is claimed on this page. The exchange path would be established per deployment with the authority that owns the system.
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 Maritime Command and Control Information System and implies no interface to it.
Public sources
- NATO Communications and Information Agency
- NATO Allied Command Transformation request for information on a maritime command and control information system
Factual statements about the named system on this page are drawn from these public sources.
Frequently asked
- Is there an MCCIS connector today?
- No. The status is available on request, which means a dedicated connector can be developed for a customer, programme or deployment. Nothing has been built or tested against the system.
- Why is the status weaker than for other NATO systems on this site?
- Because the public record does not clearly establish the current programme position of MCCIS, and a status badge should reflect evidence rather than familiarity with a name.
- Does SynapseCommand replace a maritime command system?
- No. It performs no combat system function, controls no sensor or effector, and adds analysis alongside the maritime command system in use.
- What would an integration require?
- A named deployment, authorised access to whatever maritime interface that deployment can expose, connector development against the published SynapseCommand contract, and testing.
- Is this NATO endorsed?
- No. Nothing here implies NATO certification, endorsement, approval or partnership.
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.