SynapseCommand Integration with SitaWare Frontline
SitaWare Frontline is a battle management application for the mounted commander, built around friendly force tracking, tactical communication and a clear operational view inside the vehicle. The integration question at this echelon is not the same as at a headquarters. A vehicle commander does not want a planning environment on a screen under contact. What the tactical level can contribute, and benefit from, is a faster and better-evidenced flow between what is observed forward and the analysis happening behind.
What SitaWare Frontline is
Systematic positions SitaWare Frontline as battle management and tactical communications for the mounted commander, oriented around shortening the observe, orient, decide and act cycle. Its published capabilities include friendly force tracking distributed automatically across the radio network and its subnets, planning and geo-analysis tools, integrated chat and messaging, and live video from unmanned aircraft and vehicle cameras, including the sharing of an unmanned aircraft position as a friendly force track.
Communications are central to the published product. Systematic states that SitaWare Frontline employs the SitaWare Tactical Communication protocol to move large volumes of data across the battlespace in denied, degraded and limited bandwidth conditions. That protocol is Systematic's own, and it is the mechanism through which the friendly force tracking picture is distributed widely at the tactical level.
On standards, Systematic publishes that SitaWare Frontline, as part of the SitaWare suite, is compliant with MIL-STD-2525 symbology and with ADatP-3 messaging through integration with IRIS Forms, and describes a Quick Forms module adhering to ADatP-3 that can be added to SitaWare Frontline and SitaWare Edge. The product is described as an off-the-shelf solution with an open architecture that enables external integrations.
Within the suite, SitaWare Frontline sits between SitaWare Edge for dismounted commanders and SitaWare Headquarters at command level, giving a single command chain from the dismounted soldier through to the highest echelon.
Your C2 stays. SynapseCommand adds the decision layer.
The value of tactical information to a decision layer is not the individual track. It is the aggregate: what the forward picture says about the adversary's pattern of movement, about the feasibility of a branch that was planned an hour ago, and about whether the assumptions behind the current plan still hold.
SynapseCommand is not a replacement tactical client and is not intended to appear on a vehicle screen. Where a customer authorises it, tactical information reaching an authorised exchange point is normalised into the canonical data model with its source, timing and confidence intact, and is then available to the same agents that support the operational level. The reasoning happens where there is compute, power and an accredited environment, not in the turret.
The useful direction of travel is upward. Tactical reporting becomes evidence that changes an operational assessment, and it does so with provenance, so a staff officer can see that a revised assessment rests on three reports from two units in the last twenty minutes rather than on an unattributed feeling that something has changed.
Anything flowing back down is deliberately modest and deliberately human-gated. A decision layer output that reaches a mounted commander should be a short, authorised product that a human has released, not an automated instruction generated by a model.
- 01SitaWare FrontlineThe mounted commander's battle management environment stays unchanged, on the bearer and the hardware already fielded.
- 02Tactical operational informationFriendly force tracking, reports and observations as they exist in the tactical network. What is available for exchange is determined by the deployment, not assumed here.
- 03Authorised data exchangeAn exchange point agreed for the deployment. SynapseCommand does not claim to speak SitaWare Tactical Communication, which is Systematic's proprietary protocol.
- 04SynapseCommand integration layerNormalisation against a published data contract, with an adapter written for whatever interface the customer and the vendor make available.
- 05Multi-agent analysisFusion, adversary reasoning and blue force assessment applied to the aggregate tactical picture rather than to single reports.
- 06Tactical and operational decision supportRevised assessments, threat interpretation and branch triggers presented to the staff responsible for the sector.
- 07Human decision authorityA named human releases anything that will be acted on. The decision layer never issues a tactical instruction.
- 08ReplayThe tactical inputs behind an assessment are retained, so a decision can be reconstructed exactly rather than reconstructed from recollection.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Aggregate reading of the forward picture
Patterns across many tactical reports, rather than the individual contact report that a vehicle commander can already see perfectly well without help.
Threat interpretation with confidence stated
An assessment that says how confident it is and on what it rests, which is what allows a staff officer to weigh it against their own judgement.
Branch triggers
Continuous testing of whether the conditions that would trigger a prepared branch have been met, so a planned alternative is offered before the situation forces an unplanned one.
Escalation into planning
Tactical change that invalidates an operational assumption is surfaced as a planning input rather than left to be noticed at the next update brief.
Attributable reporting upward
When a tactical picture informs a higher decision, the chain from report to recommendation is recorded, which matters in coalition sectors where units answer to different nations.
How the decision cycle runs
Sector assessment refresh
Authorised tactical reporting updates the operational assessment for a sector continuously, so the staff sees a moving picture with provenance rather than a snapshot assembled for the next brief.
Counter-unmanned-aircraft cueing support
Where unmanned aircraft observations are shared as part of the tactical picture, the fusion and adversary agents contribute to the interpretation of a developing air threat. The engagement decision remains entirely a human one, held under existing rules of engagement.
Force protection reasoning
Movement and reporting patterns are tested against the adversary case to identify where the friendly disposition has become predictable, with the reasoning attributable rather than presented as a verdict.
Coalition sector coordination
Where a sector is held by units from several nations, releasability is enforced per record, so an assessment can be shared with the partners entitled to see the evidence behind it.
Post-action reconstruction
The tactical inputs that shaped an assessment are replayable, which supports honest lessons work rather than a narrative assembled after the fact.
How this sits in a real environment
Nothing runs in the vehicle
SynapseCommand is not deployed onto the mounted client. The decision layer runs in an accredited environment with the compute and power to support it, and the tactical estate is left as it is.
The bearer is the constraint
Tactical bearers are intermittent by nature. An integration is designed to degrade with the bearer: gaps in reporting are visible as gaps in the assessment, not silently smoothed over.
Proprietary protocol boundary
SitaWare Tactical Communication is Systematic's own protocol. Any exchange happens at a point where the customer already terminates or gateways that traffic, not by SynapseCommand attempting to speak it.
Scope agreed before build
Which tactical data is in scope, at what classification and with what releasability, is a customer decision recorded before any adapter is written.
Where the data goes, and where it does not
- Tactical data is processed inside the customer enclave. No operational data is sent to an external service and no external model calls are made during operational use.
- Every tactical record keeps its originating unit, timing and confidence, so an assessment can never present a single unconfirmed report as an established fact.
- Human decision authority is structural rather than advisory: the decision layer produces options and assessments and has no mechanism for issuing a tactical instruction.
- The wider assurance model is set out on the trust page, and the layered design is described on the architecture page.
What is claimed, and what is not
A dedicated connector can be developed for a customer, integration programme or deployment.
Systematic publishes that SitaWare Frontline has an open architecture enabling external integrations and that, as part of the SitaWare suite, it is compliant with MIL-STD-2525 symbology and ADatP-3 messaging through integration with IRIS Forms. Its principal bearer protocol, SitaWare Tactical Communication, is proprietary to Systematic. SynapseCommand has no adapter for any of these and claims no validated exchange with SitaWare Frontline. A dedicated integration can be developed for an authorised customer or programme with access to the relevant interfaces.
Qualification
References to SitaWare Frontline describe potential technical interoperability only as explicitly stated on this page. They do not imply sponsorship, certification, endorsement or partnership with Systematic, nor a completed deployment.
Interfaces and data standards
Systematic publishes that SitaWare Frontline is compliant with MIL-STD-2525 symbology and ADatP-3 messaging through integration with IRIS Forms, and that it uses the proprietary SitaWare Tactical Communication protocol. SynapseCommand does not currently implement MIL-STD-2525 symbology exchange, ADatP-3 messaging or SitaWare Tactical Communication, so no shared standard is claimed. SynapseCommand's supported standards and its published JSON Schema contract are documented in the open integration layer, and an adapter for an authorised interface would be written against that same contract.
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 SitaWare Frontline 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 SitaWare Frontline?
- No. The mounted commander keeps the battle management client they are trained on. SynapseCommand adds analysis behind it and never appears as a competing tactical display.
- How could tactical information from SitaWare Frontline support SynapseCommand workflows?
- Authorised tactical reporting would be normalised with its source, timing and confidence preserved, then read in aggregate by the fusion, adversary and blue force agents to refresh the operational assessment and to test whether planned branch conditions have been met.
- Does SynapseCommand support SitaWare Tactical Communication?
- No. SitaWare Tactical Communication is Systematic's proprietary protocol. Any exchange would take place at a point in the customer's architecture where that traffic is already terminated or gatewayed.
- What is the current status of SynapseCommand alongside SitaWare Frontline?
- Available on request. No adapter exists, no exchange has been validated, and no deployment has taken place. An integration can be developed for an authorised customer or programme with access to the relevant interfaces and a representative test environment.
- Has Systematic certified this integration?
- No. There is no Systematic certification, endorsement or partnership, and none is implied anywhere on this page.
- Could SynapseCommand send instructions to a vehicle?
- No. The decision layer produces assessments and options for a named human to weigh. It has no mechanism for issuing tactical instructions, and any product that reaches a mounted commander does so because a human released it.
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.