SynapseCommand Integration with SitaWare Maritime
SitaWare Maritime is a naval C4ISR environment for the recognised maritime picture, held ashore at a maritime operations centre, afloat with a task group commander, or on an individual ship. It is a command information system rather than a combat system, which makes it the part of the maritime architecture where an added decision layer is a reasonable proposition rather than an intrusion. This page sets out where SynapseCommand would sit, and states plainly that no integration has been built or validated.
What SitaWare Maritime is
Systematic describes SitaWare Maritime as an operationally proven C4ISR solution that presents commanders with a detailed recognised maritime picture and, through data sharing across domains, a shared common operational picture. The vendor states it can be used throughout the maritime domain, at maritime operations centres ashore, with task group commanders at sea and on individual ships.
The published capability set is specific. It includes a configurable recognised maritime picture spanning surface, sub-surface and air, holding both the classified military picture and the unclassified civilian white picture; SitaWare Fusion track correlation that correlates and fuses tracks in near real time from sources including AIS, OTH-Gold, radar systems, remote sensors and vessel traffic systems; and anomaly detection driven by user-defined rules that notify on vessels of interest, tracks entering or leaving defined areas, or deviations from chosen conditions.
Sub-surface coordination is treated as a first-class function. Systematic publishes water space management for coordinating sub-surface warfare and synchronising weapon deployment across submarines, surface ships and aircraft, and prevention of mutual interference for detecting conflicts between planned friendly submarine operations and other elements such as restricted areas and units towing underwater sensors.
Planning, tasking and messaging follow Alliance formats. Systematic publishes management of OPGEN and OPTASK messages in APP-11 or USMTF using IRIS Forms, military messaging over STANAG 4406 and ACP-127, and instant messaging in XMPP and JCHAT compliant clients suited to low-bandwidth networks. The published interoperability list also includes ADatP-3, OTH-Gold, AIS, WAIS, Link 11, Link 16 SIMPLE, Link 16 JREAP, ADS-B, NVG, KML, VMF, NFFI and MIP.
Systematic states that SitaWare Maritime already integrates with NATO solutions and draws on developments in artificial intelligence and big data. Those are the vendor's statements about the vendor's product, and this page does not extend them to SynapseCommand.
Your C2 stays. SynapseCommand adds the decision layer.
SitaWare Maritime already produces a fused, curated picture. The gap a decision layer addresses is not fusion, it is the sustained judgement applied to that picture over a long watch: which of several hundred normal-looking contacts deserves a person's attention, and why.
SynapseCommand would sit alongside the command information layer, consuming an authorised export of track, reporting and planning information and returning analytical products to the staff, never writing into the maritime picture and never touching a combat system.
Systematic's own anomaly detection is rule-based: the operator defines conditions and is notified when they are met. That is precise and predictable, and it is bounded by what someone thought to encode. The complement SynapseCommand offers is behavioural reasoning over sequences, where the output is an argued case for interest rather than a rule firing, and where the argument itself is inspectable.
The reasoning is written append-only alongside the picture it was drawn from. In a domain where an incident near a cable route or a boarding decision is reconstructed months later, the value of a record of what was known, what was inferred and who decided is disproportionate to its cost.
- 01SitaWare MaritimeThe naval C4ISR environment stays as fielded. Nothing from SynapseCommand is installed into it and nothing is written back into the recognised maritime picture.
- 02Authorised export of picture and reportingTrack, contact, reporting and planning information leaving through an interface the customer authorises. Systematic publishes no interface specification, so the route is a customer decision.
- 03Canonical data model normalisationEvery item carries its source, timing, confidence, classification and releasability into the model. Cooperative reporting is never silently promoted to the confidence of a sensor track.
- 04SynapseCommand decision-intelligence environmentRuns inside the customer enclave, ashore or afloat, designed for disconnected operation when reachback to shore is unavailable.
- 05Agent reasoning over behaviourFusion, scenario, course-of-action and adversary agents assess pattern of life, persistence and intent, and state the case for each judgement.
- 06Products to the watch team and staffShortlists, argued assessments and option comparisons delivered to authorised users, with the supporting evidence attached and the decision left to a named human.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
A shortlist with an argument attached
Instead of an alert that a rule fired, the watch team receives a ranked set of contacts with the behaviour, history and context that make each one interesting, so the first act of the shift is challenging a case rather than assembling one.
Behaviour that a rule would not catch
Loitering that only matters given what lies beneath, a rendezvous pattern that repeats across weeks, a transponder gap at a convenient moment: judgements about a sequence, made continuously, without depending on somebody having anticipated the pattern.
Confidence carried, not averaged
Cooperative reporting, radar, patrol observation and intelligence keep their separate weights through the assessment, so a picture built largely from self-reported positions is visibly that.
A record that survives the watch handover
What was known, what was inferred, what was recommended and who authorised it are written append-only, which is what makes a maritime incident reconstructable long after the contact has gone.
How the decision cycle runs
Wide-area maritime domain awareness
Across a large area of operations the analytical problem is triage. The fusion agent assesses behaviour over time across the whole picture and brings forward the contacts whose history, not whose position, is anomalous.
Critical undersea infrastructure protection
Proximity and persistence around cables, pipelines and offshore assets are assessed continuously, with escalation accompanied by the reasoning that produced it rather than an unexplained warning.
Task group option development
Where a response is required, options are developed against constraints such as endurance, positioning and rules of engagement, with the adversary case argued separately by the red team agent and the comparison left inspectable.
Sustained watch under intermittent reachback
A unit operating without shore reachback keeps analytical support locally. The assessment ages what it holds and shows the gap, then reconciles when the link returns rather than presenting a stale picture as current.
How this sits in a real environment
Ashore and afloat, the same software
The decision layer runs at a maritime operations centre or aboard a unit inside the customer enclave. Sizing differs; the assurance model does not.
Disconnected by design
SynapseCommand makes no external model calls in operational use and requires no reachback to function, which is the baseline condition for a deployed maritime unit rather than an edge case.
Command information layer only
Integration scope stops at the maritime command information system. The decision layer does not participate in sensor or effector control and does not enter a combat system boundary.
Interface access precedes engineering
Systematic publishes no interface specification for SitaWare Maritime. A programme therefore begins with the customer establishing an authorised export path, which is a contractual step before it is a technical one.
Where the data goes, and where it does not
- All processing takes place inside the customer enclave. No maritime picture data leaves the deployment and no external model calls are made during operational use.
- Classification and releasability travel at record level, so a coalition task group sees a picture that respects the caveats attached to each contributing source.
- Records are written append-only and are ML-DSA-signed in assured deployments, giving a maritime incident an evidential trail rather than a screenshot.
- The decision layer holds no authority. Every recommendation is released by a named human, and that authorisation is recorded with the decision.
- The full assurance position is set out on the trust page, and the layered design on the architecture page.
What is claimed, and what is not
A dedicated connector can be developed for a customer, integration programme or deployment.
Systematic publishes a broad interoperability list for SitaWare Maritime, including AIS, OTH-Gold, APP-11, ADatP-3, USMTF, Link 16 SIMPLE and JREAP, NVG, KML, VMF, NFFI and MIP. SynapseCommand ingests AIS reporting for maritime domain awareness, but consuming the same public source is not an exchange between the two systems, and Systematic publishes no interface specification for SitaWare Maritime. There is no adapter, no validated exchange and no completed deployment. A dedicated integration can be developed for an authorised customer or programme with access to the relevant interfaces.
Qualification
References to SitaWare Maritime describe potential technical interoperability only as explicitly stated on this page. They do not imply sponsorship, certification, endorsement or partnership with Systematic, nor a completed deployment.
Interfaces and data standards
Systematic publishes support in SitaWare Maritime for standards including APP-11, ADatP-3, OTH-Gold, AIS, WAIS, USMTF, Link 11, Link 16 SIMPLE, Link 16 JREAP, ADS-B, NVG, KML, VMF, NFFI and MIP. SynapseCommand ingests AIS reporting for maritime domain awareness, but both systems consuming the same public source is not an exchange between them, and no shared interface with SitaWare Maritime is claimed. SynapseCommand's own interfaces and published JSON Schema contract are documented in the open integration layer, and any adapter would be written against that contract once an authorised interface is available.
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 SitaWare Maritime and implies no interface to it.
Public sources
Factual statements about the named system on this page are drawn from these public sources.
Frequently asked
- What is the current status of SynapseCommand alongside SitaWare Maritime?
- Available on request. There is no adapter, no validated exchange and no deployment. An integration can be developed for an authorised customer or programme once an authorised interface and a representative environment are accessible.
- Both systems handle AIS. Does that make them interoperable?
- No. Systematic publishes AIS among the sources SitaWare Maritime correlates, and SynapseCommand ingests AIS reporting separately. Consuming the same public source is not an exchange between the two systems, and this page claims none.
- Does SynapseCommand duplicate SitaWare Fusion or the built-in anomaly detection?
- No. Track correlation and rule-based anomaly detection are functions of SitaWare Maritime. SynapseCommand reasons about behaviour over time on top of a picture of that kind and states the case for its judgements, which is a different task from firing a rule.
- Would SynapseCommand write into the recognised maritime picture?
- No. The relationship is read-oriented. Analytical products go to authorised staff, not back into the operational picture, and nothing is installed into SitaWare Maritime.
- Does this involve a combat management system?
- No. SitaWare Maritime is a command information system. SynapseCommand does not perform combat system functions and does not control sensors or effectors.
- Is there an official Systematic partnership or certification?
- No. There is no partnership, certification or endorsement from Systematic, and nothing here should be read as suggesting otherwise.
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: Maritime C2 and combat management. Last reviewed 2026-09-06.