SynapseCommand Integration with Saab 9Land BMS
Saab 9Land BMS is a tactical command and control system for land forces, scaled through three standard configurations from an individual tracker to a headquarters-level net commander. A battle management system of this kind is deliberately built to keep a formation synchronised and to move orders and reports quickly. It is not built to argue with a plan. That is the gap a decision layer fills, and it is the only gap this page claims.
What Saab 9Land BMS is
Saab describes 9Land BMS as a tactical command and control system that lets a force use its full potential by raising the level of awareness in all units at all times. It is published as one coherent system, scalable to a customer's needs, and as being in operational use and deployable within armed forces today.
The product is published in three standardised configurations that are parts of the same system. Tracker covers navigation and route management, blue force tracking, reports, and alarms and alerts. Integrator adds vehicle information system integration, sensor and video integration, remote sensor management, fire support, multi-role functionality and collaborative mission management. Net Commander adds headquarters functions: interoperability, mission and network management, an enhanced three-dimensional common operational picture, decision support, planning support, logistics support and evaluation support.
Two further published characteristics matter for any integration discussion. Saab states that 9Land BMS is based on an open integration platform that eases adaptation to change and the integration of legacy systems and third-party products, and that the system is built on a decentralised architecture and replication model that tolerates the loss of systems without the loss of functionality. Saab also publishes interoperability with NFFI and with MIP Block 2 and Block 3 in the Net Commander configuration, and a pre-configured automatic warning and reporting capability for chemical, biological, radiological and nuclear events.
Nothing beyond the above is asserted here. Saab publishes no public interface specification, schema or developer documentation for 9Land BMS, so this page describes what an integration would involve rather than how one is built.
Your C2 stays. SynapseCommand adds the decision layer.
SynapseCommand is not a battle management system and does not seek to become one. A land formation running 9Land BMS already has a tracked friendly force picture, an order flow and a reporting chain. Replacing any of that would be a downgrade. The decision layer sits behind it and consumes authorised operational data to produce analysis that a battle management system is not designed to produce: distinct courses of action, adversary reasoning against them, sustainment feasibility, and an attributable record of why the chosen option was chosen.
The natural echelon for this is the Net Commander level, where planning, decision support and evaluation already live, rather than in the vehicle or on the dismounted soldier. The commander and staff keep working in the environment they trained in. The analysis arrives as options with evidence attached, and a human decides.
The direction of flow matters. The default pattern is read-only: authorised data is exchanged into the decision layer, and the products that come back are advisory. Writing anything into a land command system is a separate, deliberate customer decision that still passes a human authorisation gate before anything is issued as an order.
- 01Saab 9Land BMSTactical land command and control, retained as the system of record for the picture and the order flow.
- 02Authorised operational data exchangeA customer-authorised path agreed with the system owner. No interface is assumed, and none is published by Saab.
- 03SynapseCommand integration layerNormalises the exchanged data and records provenance, classification and time of receipt for every item.
- 04Canonical data modelOne internal representation of entities, tasks, units and events, so analysis never depends on the shape of a particular source system.
- 05Specialist agentsBlue force reasoning, adversary reasoning and course-of-action development run over the same canonical picture.
- 06Operational analysisAggregation, gap detection, confidence and staleness assessment against the formation's stated intent.
- 07Course-of-action development and comparisonDistinct options, tested against an adversary and against sustainment, presented side by side with the evidence behind each.
- 08Human decision gateNo option becomes a decision without a named human accepting it. The system proposes; the commander decides.
- 09ReplayEvery input, agent contribution and human choice is retained so the sequence can be reconstructed after the fact.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Options a battle management system does not generate
9Land BMS distributes and displays. It does not produce three materially different ways to achieve the mission and then stress each of them. SynapseCommand does, and shows the assumptions each option depends on.
Adversary reasoning applied to your own plan
The red agent works against the courses of action the staff is considering, surfacing the counters that make an option fragile before the formation is committed to it.
Sustainment tested rather than assumed
Logistics support exists in the Net Commander configuration as a function. The decision layer treats sustainment as a constraint on feasibility, so an option that cannot be supplied is marked as such rather than presented as viable.
Confidence and staleness made explicit
A land picture assembled from reports and sensors ages unevenly. Every input carries its age and its source, and analysis states plainly where a conclusion rests on data that is old or thin.
An attributable record
Who saw what, which analysis was produced, what the human decided and when. That record supports after-action evaluation, which the Net Commander configuration already treats as a distinct function.
Coalition reasoning at formation level
Where a formation operates with partners, releasability is treated as a property of each item, so what is shown to a partner cell is governed by rule rather than by operator judgement under time pressure.
How the decision cycle runs
Course-of-action development at brigade or battlegroup headquarters
The staff frames the problem in its own process. Authorised picture, task organisation and readiness data are exchanged into the decision layer, which returns distinct options with adversary responses and sustainment findings. The staff selects, refines and issues through 9Land BMS as it always has.
Branch and sequel triggers
The formation defines the conditions that would force a change of plan. The decision layer watches the exchanged picture against those conditions and raises a candidate branch with its evidence when one is approaching, rather than after it has been crossed.
Force protection and counter-uncrewed-aircraft support
Where uncrewed aircraft activity is being reported into the land picture, the decision layer aggregates the pattern across the formation rather than the single unit, and presents the response options to a human. Any engagement decision remains entirely with the authorised chain of command.
Rehearsal before commitment
A selected option can be rehearsed against an adversary model, with the sustainment and timing consequences shown, before the formation is committed. Nothing about the rehearsal touches the live command system.
After-action evaluation
Evaluation support is a published Net Commander function. The decision layer contributes the reconstructed sequence: what was known, what was analysed, what was decided, and what the alternatives were at each point.
How this sits in a real environment
Echelon
The intended integration point is the headquarters echelon, where planning and decision support already sit. Nothing in this integration requires software on a vehicle or on a dismounted soldier's device.
Data direction
Read-only by default. A write path back into the command system is a deliberate customer decision, authorised separately, and still subject to a human gate.
Disconnected operation
SynapseCommand runs disconnected. It makes no external calls and depends on no external model service, which matters where 9Land BMS is deployed on a decentralised, loss-tolerant network.
What an integration would require
Authorised access to a data exchange path agreed with the system owner and the customer, a representative test environment, and a customer decision on scope and direction of flow. The adapter is written against SynapseCommand's published data contract.
Where the data goes, and where it does not
- Deployment is designed for environments up to NATO SECRET, within the customer's own accreditation boundary. Classification and releasability travel with each item rather than being applied at the display.
- Cryptographic assurance follows the platform standard: records are ML-DSA-signed in assured deployments, so the analysis trail can be verified rather than trusted.
- The system is fail-closed. Where a required input is missing, stale beyond tolerance or of unverified provenance, the analysis says so instead of quietly proceeding.
- No operational data leaves the customer's environment. There are no external artificial intelligence calls at any point in the analysis path.
What is claimed, and what is not
A dedicated connector can be developed for a customer, integration programme or deployment.
Saab publishes that 9Land BMS is built on an open integration platform intended to ease adaptation and the integration of legacy systems and third-party products, and lists interoperability with NFFI and with MIP Block 2 and Block 3 in its Net Commander configuration. Saab publishes no interface specification for the system, and SynapseCommand implements none of those interoperability profiles today. 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 Saab 9Land BMS 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 NFFI and MIP Block 2 and Block 3 interoperability for the Net Commander configuration of 9Land BMS. SynapseCommand does not implement NFFI or MIP and makes no claim of exchange over either. They are noted here because they describe the system a customer already has, not a route that exists today.
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 9Land BMS 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
- Does SynapseCommand replace Saab 9Land BMS?
- No. 9Land BMS remains the battle management system and the system of record for the land picture and the order flow. SynapseCommand is a decision layer that works alongside it, adding analysis, course-of-action development, rehearsal and replay.
- What is the current status of SynapseCommand alongside Saab 9Land BMS?
- Available on request. There is no SynapseCommand adapter for 9Land BMS, no validated exchange and no completed deployment. An integration can be developed for an authorised customer or programme once the relevant interfaces and technical environment are accessible.
- Is any work on 9Land BMS certified or endorsed by Saab?
- No. There is no certification, endorsement, partnership or commercial relationship with Saab, and nothing on this page should be read as implying one.
- Does SynapseCommand support NFFI or MIP?
- No. Saab publishes NFFI and MIP Block 2 and Block 3 interoperability for the Net Commander configuration. SynapseCommand implements neither today and claims no exchange over either.
- Would anything run inside a vehicle?
- No. The integration point is the headquarters echelon. The decision layer consumes authorised data and returns analysis to the staff; it places no software on vehicles or soldier-carried devices.
- Does SynapseCommand issue orders?
- No. It produces options and evidence. A named human accepts an option, and orders are issued through the command system by the authorised chain of command.
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: Land C2 and battle management. Last reviewed 2026-09-06.