SynapseCommand and the Thales TACTICOS Combat Management System
TACTICOS is a combat management system in wide naval service, connecting a ship's sensors and effectors and supporting the operators who fight her. Nothing on this page proposes putting an analytical layer inside that. What it describes is the layer outside it, where the maritime picture is wide, the timescale is hours rather than seconds, and the hard question is which of a great many ordinary-looking contacts deserves the watch team's attention.
What Thales TACTICOS is
Thales describes a combat management system as the central command and decision-making element of a military naval vessel, connecting the ship's sensors and effectors to enable and support operators. In its naval combat management material Thales presents TACTICOS alongside the M-cube mine countermeasure management system as the products through which it supports decision-making across sky, surface and underwater operations for the fleet.
Thales emphasises the operator experience in its published positioning, describing visualisation of all primary operations on a single screen and rule-based identification and classification capabilities that translate data into actionable information through its human machine interface.
On installed base, Thales stated in a March 2022 press release announcing the strategic cooperation agreement with the PGZ-MIECZNIK Consortium for the Polish Navy's future MIECZNIK frigates that TACTICOS was already operational in the Polish Navy and in 24 other navies around the world, from offshore patrol craft to destroyers.
Thales also publishes a wider collaborative naval combat position covering secure and interoperable systems for data sharing across platforms. That is Thales describing Thales products, and this page does not extend it to SynapseCommand.
Your C2 stays. SynapseCommand adds the decision layer.
The combat system boundary is treated here as an assurance boundary. TACTICOS is accredited with the sensors and effectors it coordinates, and engagement decisions belong to the command team operating it. SynapseCommand does not enter that boundary, does not perform combat system functions and does not control sensors or effectors.
One layer out, the work is different in kind. A shore command or a task group staff is reasoning about hundreds or thousands of contacts over days, most of them civilian, and about options that will be argued rather than executed in seconds. That is where an inspectable decision layer earns its place.
Information reaching SynapseCommand comes through whatever authorised export path the customer's architecture provides at the command information layer. Analytical products return to staff, never into the combat picture.
Because Thales places rule-based identification and classification inside TACTICOS itself, the complement offered here is deliberately not more rules. It is behavioural reasoning over sequences with the argument exposed, which is a different instrument for a different timescale.
- 01Thales TACTICOSThe combat management system and its sensor and effector coupling remain untouched. Nothing from SynapseCommand is installed into it.
- 02Combat system boundaryNot crossed. No analytical component participates in identification for engagement, weapon assignment or effector control.
- 03Authorised export at the command information layerTrack, contact and reporting information already available outside the combat system boundary in the customer's architecture.
- 04Canonical data model normalisationProvenance, timing, confidence, classification and releasability preserved on every record entering the model.
- 05SynapseCommand decision-intelligence environmentRuns inside the customer enclave, ashore or afloat, and continues to function while the unit is disconnected.
- 06Assessments and options for the staffShortlists, argued adversary cases and comparable options delivered to authorised users and released by a named human.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Wide-area triage the ship does not have time for
A combat system is optimised for a small number of contacts at high fidelity. Deciding which of several hundred routine tracks across an area of operations deserves attention is a different workload, sustained across every watch.
Reasoning that can be challenged
Every judgement arrives with the behaviour, history and context behind it, so a watch officer can disagree with the case rather than accept or dismiss an alert.
A coalition-safe picture
Releasability is carried at record level, so a maritime assessment shared with allied units respects the caveats attached to each contributing source.
An evidential decision record
Append-only records mean a maritime incident can be reconstructed months later in terms of what was known and who decided, not only what the platform did.
How the decision cycle runs
Maritime domain awareness at scale
Behaviour over time across a wide picture drives what is brought forward, so the watch team spends its attention on an argued shortlist instead of assembling one from raw traffic.
Escort and protection planning
Options for escort, screening and patrol tasking are developed against constraints, tested against an independently argued adversary case, and compared on criteria the staff can inspect.
Undersea infrastructure watch
Persistence, proximity and repetition around cables, pipelines and offshore assets are assessed continuously, with escalation accompanied by its reasoning.
Disconnected task group operation
A task group operating without shore reachback keeps analytical support locally, with a visibly ageing picture and reconciliation when the link returns.
How this sits in a real environment
Command information layer only
Deployment is outside the combat system boundary, ashore or in a shipboard enclave. There is no installation into TACTICOS and no impact on its accreditation.
Sovereign and self-contained
The environment runs inside the customer's own infrastructure, disconnected if required, with no external service dependency during operational use.
Interface access is a programme step
Thales publishes no TACTICOS interface specification. Any integration therefore begins with the customer establishing an authorised export path under their own arrangements with the vendor.
Scope agreed at the outset
What is exchanged, in which direction and at which classification is defined explicitly at the start of a programme rather than inferred from a product datasheet.
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 enforced as an assurance boundary, and no decision-layer output participates in sensor or effector control.
- Classification and releasability are held at record level, so coalition sharing does not depend on manual redaction.
- Records are append-only and ML-DSA-signed in assured deployments, giving an incident review 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.
Thales publishes TACTICOS as its naval combat management system, operational in the Polish Navy and, as stated in 2022, in 24 other navies from offshore patrol craft to destroyers. Thales publishes no interface specification for TACTICOS, SynapseCommand implements no TACTICOS 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 Thales TACTICOS describe potential technical interoperability only as explicitly stated on this page. They do not imply sponsorship, certification, endorsement or partnership with Thales, nor a completed deployment.
Interfaces and data standards
Thales publishes TACTICOS as its naval combat management system and describes broad interoperability across its collaborative naval combat portfolio, but publishes no interface specification for the product. SynapseCommand implements no TACTICOS 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 Thales TACTICOS and implies no interface to it.
Public sources
- Thales: Naval Combat Management System
- Thales: TACTICOS selected for the Polish Navy MIECZNIK frigates (press release, 4 March 2022)
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 Thales TACTICOS?
- 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 integrate directly with TACTICOS?
- Not today. Any exchange would take place at the command information layer through a path the customer authorises, not through a bespoke channel into the combat system.
- Does SynapseCommand identify or classify contacts for engagement?
- No. Identification and classification for engagement are combat system functions. SynapseCommand assesses behaviour over longer timescales to support command decisions, and holds no engagement authority.
- How is this different from the decision support already in a combat management system?
- Timescale and breadth. A combat management system supports the operator in the engagement. The decision layer reasons across a wide picture over days and exposes the argument behind each judgement.
- Does it work when the ship has no reachback?
- Yes. SynapseCommand is designed to run disconnected, ages what it holds when reporting stops, and reconciles when connectivity returns.
- Is there an official Thales partnership or certification?
- No. There is no partnership, certification or endorsement from Thales, 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.