SynapseCommand and the Saab 9LV Combat Management System
9LV is a combat management system: the software that coordinates a warship's sensors and weapons and supports the command team in the seconds and minutes that decide an engagement. A general-purpose analytical layer does not belong inside that boundary, and SynapseCommand does not attempt to enter it. This page describes what a decision layer can usefully do around a 9LV-equipped platform, and states the integration position without embellishment.
What Saab 9LV CMS is
Saab describes 9LV as a combat management system that coordinates all sensors and weapons, performs probability-based evaluation, and provides data fusion and decision support. Saab states it is designed to cope with extremely heavy workloads and multiple tasking, and presents it as a complete C4I for all types of naval platform, including patrol vessels, frigates, larger vessels and submarines.
The published mission scope runs from the littorals to the open sea and across the three dimensions of naval warfare, air, surface and sub-surface, together with the internal decision cycle. Saab lists mission types including anti access and area denial operations, protection and escort, maritime patrol and response, border control and interdiction, peace support operations, anti-piracy, search and rescue, and environmental control.
Saab states that 9LV offers support for interoperability and for allied and coalition operations as part of an international force, and that it also provides command team training, recording and debriefing.
On architecture, Saab publishes that the 9LV software follows the principles of Naval Open Architecture, which the company states enables faster and more affordable upgrades as well as the easy integration of any third-party module, reducing lifecycle cost and avoiding unwanted ties to proprietary technology and single-source supply. Saab publishes the principle, not the interfaces, and this page treats it accordingly.
Your C2 stays. SynapseCommand adds the decision layer.
The boundary is the important part of this page. A combat management system is accredited as a unit with its sensors and effectors, operates on timescales measured in seconds, and is subject to safety and engagement authority that no analytical layer should sit inside. SynapseCommand does not enter that boundary, does not perform combat system functions and does not control sensors or effectors.
The useful position is one layer out, at the command information layer, where the questions are slower and wider: what is this pattern of activity, what does the last fortnight of behaviour suggest, what options exist for the task group, what would an adversary do about each of them.
Information reaching the decision layer comes through whatever authorised export path the customer's architecture provides, not through a bespoke channel into the combat system. Products go back to staff, never into the combat picture.
That separation is also what makes the record useful. Combat system logs answer what the ship did. The decision record answers why the command judged as it did, which is the question an inquiry, a lessons process or a coalition partner tends to ask afterwards.
- 01Saab 9LV CMSThe combat management system and its accredited sensor and effector coupling stay untouched. Nothing from SynapseCommand is installed into it.
- 02Combat system boundaryA hard line. No analytical component crosses it, and no SynapseCommand output participates in engagement decisions or effector control.
- 03Authorised export at the command information layerTrack, reporting and planning information that the customer's architecture already makes available outside the combat system boundary.
- 04Canonical data model normalisationSource, timing, confidence, classification and releasability preserved for every record entering the model.
- 05SynapseCommand decision-intelligence environmentRuns inside the customer enclave, ashore or afloat, and is designed to keep working while the unit is disconnected.
- 06Assessments and options to the staffPattern-of-life analysis, argued adversary cases and comparable options for the command team, released by a named human.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
The slow picture around the fast one
A combat management system is built for the engagement timescale. Weeks of behaviour around a contact, a route or an installation are a different problem, and that is the one the decision layer takes on.
An adversary case argued separately
Options developed for a task group are tested against a red team agent that argues the opposing case on its own terms, so the plan meets its objections before the sea does.
Coalition-aware releasability
Assessments carry classification and releasability at record level, so what reaches an allied unit respects the caveats attached to each contributing source rather than being redacted by hand.
A reconstructable command record
What was known, what was recommended and who authorised it is written append-only, giving the debrief a foundation beyond recollection and system logs.
How the decision cycle runs
Pre-sortie option development
Before a patrol or escort task, options are developed against endurance, positioning and rules of engagement constraints, compared on stated criteria, and left inspectable rather than delivered as a single recommendation.
Interdiction and boarding triage
In border control, interdiction and anti-piracy tasks the decision layer assesses which contacts merit attention on the basis of history and behaviour, so a boarding decision starts from an argued case.
Sub-surface and infrastructure context
Persistence and proximity around cables, pipelines and offshore assets are assessed over time and brought forward with the reasoning stated, complementing rather than replacing the platform's own sensor picture.
Debrief and lessons
Saab publishes that 9LV provides recording and debriefing. The decision record adds the command reasoning alongside it, so a lessons process can examine judgement as well as execution.
How this sits in a real environment
Outside the combat system boundary
Deployment is at the command information layer, ashore or in a shipboard enclave separate from the combat system. There is no installation into 9LV and no change to its accreditation.
Built for a unit at sea
SynapseCommand runs disconnected and makes no external model calls in operational use, so analytical support does not depend on reachback to shore.
Interface access before engineering
Saab publishes the Naval Open Architecture principle but not the interfaces. A programme therefore begins with the customer establishing an authorised export path, which is a contractual step before it is a technical one.
Scope agreed explicitly
The published functional breadth of 9LV is wide. What is exchanged, in which direction and at which classification is agreed at the start of a programme rather than assumed.
Where the data goes, and where it does not
- Processing takes place inside the customer enclave. No operational data leaves the deployment and no external model calls are made during operational use.
- The combat system boundary is treated as an assurance boundary, not only an architectural one. Nothing from the decision layer participates in sensor or effector control.
- Classification and releasability are enforced at record level, which is what allows an assessment to be shared with a coalition unit without hand-editing.
- Records are append-only and ML-DSA-signed in assured deployments, so a debrief or inquiry has an evidential trail.
- 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.
Saab publishes that the 9LV software follows the principles of Naval Open Architecture, which it states enables faster and more affordable upgrades and the easy integration of third-party modules. Saab publishes no interface specification for 9LV, SynapseCommand implements no 9LV interface, and 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, and scoped to the command information layer rather than the combat system.
Qualification
References to Saab 9LV CMS describe potential technical interoperability only as explicitly stated on this page. They do not imply sponsorship, certification, endorsement or partnership with Saab, nor a completed deployment.
Interfaces and data standards
Saab publishes that 9LV follows the principles of Naval Open Architecture and supports interoperability for allied and coalition operations. Saab does not publish an interface specification, and SynapseCommand implements no 9LV interface, so no shared interface or standard is claimed here. 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 Saab 9LV CMS 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 Saab 9LV CMS?
- 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 export path and a representative environment are accessible.
- Does SynapseCommand run inside the combat management system?
- No. A combat management system is accredited with its sensors and effectors and operates on engagement timescales. SynapseCommand stays at the command information layer and does not cross that boundary.
- Does SynapseCommand control sensors or weapons?
- No, on any platform or system. It develops and tests options and makes its reasoning inspectable. Authority remains with the command team and the authorisation is recorded with the decision.
- Saab publishes that 9LV follows Naval Open Architecture. Does that mean integration is straightforward?
- It is an encouraging principle rather than a published interface. Saab does not publish the specification, so an integration still begins with the customer providing authorised access.
- Would this work on a deployed unit without reachback?
- Yes. SynapseCommand is designed for disconnected operation, ages what it holds when reporting stops, and reconciles when connectivity returns rather than presenting a stale picture as current.
- Is there an official Saab partnership or certification?
- No. There is no partnership, certification or endorsement from Saab, 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.