SynapseCommand Integration with NATO TOPFAS
TOPFAS is the planning support environment used by NATO staff working the Operational Planning Process. SynapseCommand is built around the same problem from a different direction: developing, testing and comparing courses of action quickly enough to matter, with the reasoning left visible.
What TOPFAS is
TOPFAS is publicly documented as the data and planning support system for operational planning and force activation in accordance with the NATO Operational Planning Process. It originated in the Alliance technical agency that preceded the NATO Communications and Information Agency, and it continues to be the subject of NATO procurement activity for its application suite.
Its expansion has been rendered in more than one way across the years, from the earlier tool for operational planning, force activation and simulation to the later reading as tools for operations planning functional area services. Both point at the same role: supporting the staff process by which an operation is planned rather than the way it is executed.
NATO acquisition documentation for the common operational picture capability records a service interface between TOPFAS and that capability. Beyond that, no first-party public technical specification for TOPFAS interfaces was identified, and nothing further is claimed here.
Your C2 stays. SynapseCommand adds the decision layer.
SynapseCommand does not replace a planning functional area service and does not attempt to be the system of record for a plan. The plan stays where the staff and the process already keep it.
What the agent mesh adds is speed and breadth inside the analytical part of planning: generating options against stated constraints, stress testing them against an adversarial view, comparing them on explicit criteria, and showing why one option is ranked above another.
A realistic integration would exchange planning products in both directions, so that options developed with agent support can be taken into the staff process and the staff product can be brought back for further analysis. That exchange path is not implemented and would be defined with the owning authority.
- 01TOPFAS planning environmentExisting NATO planning support service and system of record for the plan.
- 02Authorised exchange of planning productsInterface to be agreed with the owning authority. Not implemented, not assumed.
- 03SynapseCommand integration layerPublished, inspectable contract with a validated JSON Schema.
- 04Canonical data modelObjectives, constraints, forces and assumptions carried with their provenance.
- 05Specialist agentsPlanning support, course-of-action analysis, strategic reasoning and an adversarial view.
- 06Course-of-action developmentOptions generated against the stated constraints, not against convenient ones.
- 07Rehearsal and comparisonOptions tested and ranked on criteria staff can inspect and challenge.
- 08Human decision gateThe plan is owned, approved and directed by the commander.
- 09Decision record and replayAssumptions and reasoning preserved so a plan can be re-examined later.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Course-of-action generation
Multiple viable options are developed against the constraints as stated, rather than a single option elaborated because time ran out.
Adversarial testing
A dedicated red agent argues against the plan, so weaknesses surface during planning rather than during execution.
Comparison on explicit criteria
Options are ranked against criteria that are written down, which makes the ranking arguable, which is the point.
Scenario rehearsal
A course of action can be run forward under varied assumptions before anyone commits to it.
Assumption tracking
Planning assumptions are recorded with the option they support, so it is clear which assumption failing would invalidate which plan.
Replay for lessons
The record supports honest post-operation review, because what was assumed at the time is still available afterwards.
How the decision cycle runs
Framing the problem
Objectives, constraints, forces and assumptions are captured in one model so that later analysis argues about the same problem the staff are working.
Option development
Agents produce several distinct options rather than variations on one, each traceable to the constraints it respects and the assumptions it rests on.
Staff wargaming
Options are rehearsed against an adversarial view, and the resulting friction is presented to the staff as material to argue with, not as a verdict.
Decision and direction
The comparison supports the commander's decision. The decision itself, and the authority behind it, remain human and are recorded as such.
What is claimed, and what is not
SynapseCommand is architecturally capable of integrating with the system, but the specific system has not undergone validated end-to-end testing.
TOPFAS is publicly documented as the planning support system used with the NATO Operational Planning Process, and NATO acquisition material records a service interface between TOPFAS and the common operational picture capability. SynapseCommand planning and course-of-action agents work on the same class of product, but no TOPFAS connector exists and no end-to-end testing with the system has taken place.
Qualification
This status describes SynapseCommand integration architecture only. It does not imply NATO certification, NATO endorsement or a completed deployment with TOPFAS, and it does not describe an approved planning tool for the NATO Operational Planning Process.
Interfaces and data standards
The only publicly documented TOPFAS interface identified is the service interface recorded in NATO acquisition material for the common operational picture capability. SynapseCommand implements an open REST and gRPC contract, and no claim is made that either side has been connected to the other. Sensor and track standards supported elsewhere in SynapseCommand have no established relationship to TOPFAS and are therefore not listed on this page.
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 TOPFAS and implies no interface to it.
Public sources
- NATO Communications and Information Agency
- NC3A conference paper describing TOPFAS and the NATO Operational Planning Process
Factual statements about the named system on this page are drawn from these public sources.
Frequently asked
- Does SynapseCommand replace TOPFAS?
- No. The planning functional area service remains the system of record for the plan and for the staff process around it. SynapseCommand supports the analytical work inside that process.
- Is SynapseCommand approved for the NATO Operational Planning Process?
- No. It is not an approved or certified planning tool for the Alliance process. It is a decision support platform designed to work alongside the tools that are.
- What is the current status of SynapseCommand alongside TOPFAS?
- Integration-ready. The architecture supports exchanging planning products, but no TOPFAS connector has been built and no end-to-end testing with the system has taken place.
- Which SynapseCommand functions are relevant here?
- Planning support, course-of-action generation and comparison, adversarial testing, scenario rehearsal and the decision record. Sensor fusion functions are largely beside the point in this context.
- Does the agent mesh decide anything?
- No. Agents develop and test options and make their reasoning inspectable. The commander decides, and the authorisation is recorded with the decision.
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: NATO command and control. Last reviewed 2026-09-06.