SynapseCommand Integration with Saab 9CCIS
Saab 9CCIS is a command and control information system for planning, resource management, assessment and evaluation, positioned by Saab as the deliberate, non-real-time companion to its tactical command and control products. That places it in exactly the part of the operational cycle where a decision layer is useful, and away from the real-time control functions where it is not.
What Saab 9CCIS is
Saab publishes 9CCIS as a command and control information system providing tools for enhanced planning, resource management, assessment and evaluation, with functions for multidomain and joint headquarters work across air, land and maritime operations, and for civil users who require a classified working environment.
Saab describes it as a near real-time military system designed to handle information up to Secret level, highly scalable and modular to the customer's need, and as a natural extension of Saab's air, land and naval tactical command and control products, naming 9Air C4I, 9Land BMS, 9LV CMS and 9Maritime. Within the wider 9Air offer, Saab presents 9CCIS alongside 9Air C4I and the 9Air Trainer as the planning and assessment element of a complete solution.
Published functions include air mission management with air support request handling, targeting, intelligence and reconnaissance product management, a common operational picture built on recognised air, maritime and ground pictures, and resource management with interfaces to logistics systems. Published support functions include geographic information and geodata processing, meteorological management, document and office automation, chat, conferencing, and system and security management.
Saab publishes external interfaces to joint-level systems for orders, intelligence and targeting; to intelligence, surveillance and reconnaissance systems including still and motion imagery and intelligence reports; to meteorological systems; to air command and control systems; to air operation planning and tasking products including the air operations directive, airspace control order and air tasking order; to squadron and pilot mission planning systems; to air operation assessment and reporting; to land battle management systems; and to naval shore-based surveillance centres and shipborne combat management systems.
At the time of review Saab publishes no standalone 9CCIS product page and no public interface specification. The factual material above comes from Saab's own 9AIR C4I Solutions brochure, which is cited below.
Your C2 stays. SynapseCommand adds the decision layer.
9CCIS occupies the planning, resource and assessment space at a joint or air headquarters. SynapseCommand contributes to the same space without duplicating it. The information system holds the plans, products, resources and assessments; the decision layer reasons over the picture those artefacts describe and produces distinct options, adversary responses and feasibility findings that a staff would otherwise develop by hand under time pressure.
Because 9CCIS is already a headquarters-level, near real-time environment rather than a real-time control system, the integration question is comparatively clean. There is no engagement loop to stay clear of. What matters instead is that the analysis is traceable, that classification and releasability are respected, and that a named human owns every decision that leaves the headquarters.
The published breadth of 9CCIS interfaces, spanning joint, air, land, maritime, intelligence and logistics sources, is what makes it an interesting integration point in principle: a decision layer benefits from a wide and already-reconciled input picture. It remains a possibility rather than a route, because no interface specification is published and no exchange has been built or validated.
- 01Saab 9CCISJoint planning, resource management and assessment, retained as the system of record for plans, products and resources.
- 02Authorised operational data exchangeA customer-authorised path agreed with the system owner. No interface is assumed.
- 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, independent of the source system's structure.
- 05Specialist agentsPlanning, sustainment, adversary and course-of-action reasoning over the same canonical picture.
- 06Operational analysisFeasibility, resource pressure, gap detection, confidence and staleness against the commander's stated intent.
- 07Course-of-action development and comparisonDistinct options, tested against an adversary and against sustainment, compared with their evidence.
- 08Human decision gateNo option becomes a plan without a named human accepting it.
- 09ReplayThe full sequence of inputs, analysis and human choices is retained for assessment and evaluation.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Options rather than a single staffed plan
The headquarters sees several genuinely different ways to meet the intent, each with its assumptions, its resource cost and its point of fragility.
Adversary reasoning inside the planning cycle
Options are tested against an adversary before they are staffed further, rather than after a plan has acquired momentum.
Resource feasibility as a hard constraint
9CCIS holds resource management and logistics interfaces. The decision layer uses that reality to mark options that cannot be resourced, instead of leaving the discovery to execution.
Assessment with the reasoning intact
Evaluation is a published 9CCIS function. Replay supplies what evaluation usually lacks: what was known at each point, what was proposed, and why the chosen option was chosen.
Cross-domain reasoning over a joint picture
Where air, land and maritime inputs arrive in the same headquarters, analysis runs over one canonical picture rather than three separate readings of it.
Releasability applied per item
In a joint or multinational headquarters, releasability travels with the item, so partner-visible products are correct by construction.
How the decision cycle runs
Deliberate joint planning
Authorised plan, resource and picture data are exchanged into the decision layer, which returns option sets with adversary responses and resource findings for the staff to work with inside its own process.
Air support request and tasking analysis
Where air support requests and tasking products are held in the information system, the decision layer can reason about competing demands against stated priorities and present the trade-off explicitly to a human.
Sustainment and resource pressure
Resource data is treated as a feasibility constraint across options, so the headquarters sees which plans the logistics reality actually supports.
Operational assessment
Between cycles, the decision layer contributes a reconstructed account of what was known, analysed and decided, alongside the options that were rejected and the reasons recorded at the time.
Coalition headquarters working
Options and products are generated with per-item releasability, so a partner-facing version is produced by rule rather than by manual redaction.
How this sits in a real environment
Headquarters echelon
This integration is a headquarters capability. Nothing in it is intended for a vehicle, a soldier-carried device or a real-time control position.
Classification environment
Saab publishes that 9CCIS is designed to handle information up to Secret level. SynapseCommand is designed for deployment up to NATO SECRET within the customer's own accreditation boundary; the two must be accredited together, by the customer, before any exchange.
Data direction
Read-only by default. A write path into the information system is a deliberate, separately authorised customer decision.
What an integration would require
Authorised access to an agreed data exchange path and its documentation, a representative test environment, and a decision on which of the many published 9CCIS information domains are in scope.
Where the data goes, and where it does not
- Deployment is designed for environments up to NATO SECRET, inside the customer's accreditation boundary and under the customer's control.
- Classification and releasability are carried with each item through analysis, not applied at the point of display.
- Records are ML-DSA-signed in assured deployments, so an assessment can be verified rather than taken on trust.
- Fail-closed behaviour applies: where an input is missing, stale or of unverified provenance, the analysis declares it.
- The decision layer runs disconnected and makes no external artificial intelligence calls, so no operational data leaves the environment.
What is claimed, and what is not
A dedicated connector can be developed for a customer, integration programme or deployment.
Saab publishes that 9CCIS supports open civilian and military standards and interfaces and eases integration of customer-specific or third-party tools and subsystems, and lists external interfaces to joint-level, intelligence, surveillance and reconnaissance, weather, air command and control, land battle management and naval systems. Saab publishes no interface specification for 9CCIS and, at the time of review, no standalone product page. SynapseCommand has 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 9CCIS 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
The external interfaces listed by Saab for 9CCIS describe what that system connects to in a customer's architecture. They are not SynapseCommand connections. SynapseCommand implements none of them and claims no exchange with 9CCIS 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 9CCIS 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 9CCIS?
- No. 9CCIS remains the command and control information system holding plans, products, resources and assessments. SynapseCommand is a decision layer alongside it, producing options, adversary reasoning, feasibility findings and replay.
- What is the current status of SynapseCommand alongside Saab 9CCIS?
- Available on request. There is no SynapseCommand adapter for 9CCIS, 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 9CCIS certified or endorsed by Saab?
- No. There is no certification, endorsement, partnership or commercial relationship with Saab.
- Why does this page cite a brochure rather than a product page?
- At the time of review Saab publishes no standalone 9CCIS product page. The factual description here is taken from Saab's own 9AIR C4I Solutions brochure, which contains a dedicated 9CCIS section, and from Saab's air command and control overview.
- Does 9CCIS handle classified information?
- Saab publishes that 9CCIS is designed to handle information up to Secret level. Any deployment alongside it is accredited by the customer, within the customer's own security boundary.
- Which parts of 9CCIS would an integration touch?
- That is a customer decision. The published functional breadth is wide, spanning planning, resources, intelligence products, targeting and assessment, so scope is agreed explicitly rather than assumed at the start of an integration.
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: Air C2 and IAMD. Last reviewed 2026-09-06.