Air C2 and Integrated Air Defence Integration
Air command and control is a continuous cycle running against a picture that changes by the second, and an integrated air defence environment compresses that cycle further. SynapseCommand is designed to support the analytical work inside the cycle while the air command system, and the authority it carries, stay in place.
What air C2 looks like in practice
Air operations run on a planning cycle with hard edges. Guidance becomes an apportionment decision, apportionment becomes a tasking order, and the order is executed while the next one is already being built. The cycle is disciplined, but it is also unforgiving: an assumption made early propagates into hundreds of downstream tasks and cannot easily be withdrawn.
The recognised air picture underneath it is assembled from many sensors with different update rates, coverage and error characteristics. Surveillance data arrives in formats such as ASTERIX from radar, and cooperative reporting arrives separately again. Correlating those into a single track and deciding what a track is remain distinct problems, and the second one is a judgement rather than a calculation.
Integrated air and missile defence sharpens the timeline further. Engagement decisions are governed by rules and by authority that is delegated in advance precisely because there is not time to consult during the event. Anything introduced into that environment has to be explicit about which part of the problem it touches.
Air is also the domain where weather is an operational constraint rather than a background condition. Ceilings, winds and icing determine what can be tasked at all, and the meteorological picture has to be reconciled against the tasking picture continuously.
Where the decision layer fits
SynapseCommand supports the planning and assessment work around the cycle rather than the engagement decision inside it. Air tasking support, ISR fusion, option development and comparison, and the reconciliation of tasking against constraints are where the agent mesh contributes.
Surveillance and ISR reporting reaches the canonical data model through the reference adapters in the published integration layer, so a track that informs an analytical product can be traced back to the sensor report and the moment it was received, including its confidence.
SynapseCommand does not perform targeting or generate engagement authority. Recommendations concerning the employment of force are produced as options with stated assumptions and stated gaps, and they pass a human decision gate held by an authorised commander. That boundary is a design constraint, not a configuration setting.
Because the platform is built to run inside a sovereign environment without external model calls, the analysis available to an air operations centre does not depend on a commercial service being reachable, which is a precondition for use in a hardened facility.
Air tasking support
A dedicated agent supports the construction and review of tasking against apportionment guidance, asset availability and stated constraints, producing options rather than an unexplained schedule.
Sensor and surveillance ingest
ASTERIX surveillance data, motion-imagery derived tracks under STANAG 4676 and ground moving target reporting under STANAG 4607 are normalised with source, timing and confidence preserved.
ISR fusion and gap statement
Fusion output states what is corroborated, what rests on a single source and what is simply not known, which is the part most often lost when a picture is summarised for a decision.
Meteorological constraint reasoning
Weather is treated as a first-class operational constraint on feasibility, so an option that cannot be flown is identified as such during planning rather than at execution.
Analysis is produced for a human decision gate, never in place of one.
Systems in air c2 and iamd
Each entry states its integration status in plain terms, and no further.
Air command and control decision support alongside NATO air C2 information services.
Air operations planning and decision support alongside the Alliance ICC environment.
Air command and control with a sovereign decision layer alongside it.
Joint planning, resource management and assessment with sovereign decision intelligence alongside it.
Also held in the catalogue, connector available on request
Fortion 1SkyControl, Fortion SAMOC, Fortion IBMS. A dedicated connector can be developed for a customer, integration programme or deployment. Request an integration.
Standards that matter here
- ASTERIXIntegration status: Adapter available
ASTERIX surveillance messages are normalised into the SynapseCommand canonical data model, so radar and sensor tracks reach the agent mesh with their source, timing and confidence intact.
- STANAG 4676Integration status: Adapter available
STANAG 4676 tracks are ingested through a reference adapter in the open integration layer and carried into ISR fusion with full provenance.
- STANAG 4607Integration status: Adapter available
GMTI reporting is ingested through a reference adapter and correlated with other sensor feeds by the ISR Fusion Agent.
- ADS-BIntegration status: Adapter available
ADS-B feeds provide cooperative air tracks that supplement the recognised air picture inside SynapseCommand.
- RESTIntegration status: Available on request
SynapseCommand deployments expose versioned service interfaces, but no REST implementation or interface specification is published in the open integration layer, so no coverage is claimed here. The published JSON Schema describes the canonical objects such an interface would carry.
Discuss an integration in this domain
Briefings are available under NDA. SynapseCommand® integration work starts from the published data contract, so the interface can be reviewed before any commitment is made.
Third-party systems and trademarks
SynapseCommand is not a weapon system, a fire control system or an engagement authority. Nothing on this page describes certification, endorsement or partnership by NATO or by any vendor named, nor a completed integration with any air command or air defence system.
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.