SynapseCommand Integration with SitaWare Edge
SitaWare Edge is a dismounted command-and-control application: a soldier-carried device, a constrained bearer, and a user whose attention belongs to the ground rather than to a screen. The honest position on artificial intelligence at this echelon is that most of it does not belong there. This page sets out what a dismounted C2 application can realistically contribute to a decision layer, and what a decision layer should not attempt to push back down to a dismounted user.
What SitaWare Edge is
Systematic describes SitaWare Edge as comprehensive situational awareness and command-and-control for the dismounted commander, designed around infantry units operating at the tip of the spear. Its published capabilities include an advanced mapping system supporting multiple map types in two and three dimensions, planning and geospatial tools, advanced force tracking distributed to all members of the tactical network, integrated chat, and live video and imagery from unmanned aircraft and cameras.
Communications are the defining constraint of the product as Systematic presents it. SitaWare Edge employs the proprietary SitaWare Tactical Communication protocol to move data over limited bandwidth in denied and degraded conditions, and Systematic states that it shares situational awareness and messages across existing radio equipment rather than requiring new bearers.
Systematic also publishes that SitaWare Edge enables up-and-down communications with mounted and higher echelon commanders through its integration with the rest of the SitaWare suite, giving what the vendor describes as top-to-bottom situational awareness with common symbology and a common look and feel across echelons. On extensibility, Systematic states that SitaWare Edge has an open architecture with application programming interfaces allowing integration of a wide variety of data types from different sources, and that the ADatP-3 compliant Quick Forms module can be added to it.
The relevant characteristic for any integration discussion is therefore not the device. It is that SitaWare Edge is the origin point of a great deal of first-hand observation, and that this observation already has a documented path upward inside the suite.
Your C2 stays. SynapseCommand adds the decision layer.
SynapseCommand does not run on a dismounted device, and this page makes no claim that it could. The full decision-intelligence environment requires compute, power and an accredited enclave. A dismounted user has none of those to spare, and a claim to the contrary would be marketing rather than engineering.
The realistic relationship runs one way for the most part. Observations originating at the dismounted level, once they have travelled the path the suite already provides and reached an authorised exchange point, are normalised into the canonical data model with their originating unit, timing and confidence preserved, and become part of the evidence base the agents reason over.
That preservation matters more at this echelon than at any other. A dismounted report is often the only human observation of a location, it is frequently partial, and it is sometimes wrong. A decision layer that treats it as equal in confidence to a correlated sensor track produces a confident and misleading picture. Holding the difference explicitly is the point of the canonical data model.
What comes back down should be small. A dismounted commander does not need an analytical product. Where anything is returned at all, it is a short, human-released item of context delivered through the command chain and the tools the user already has, and the decision to release it is taken by a named human at a connected layer.
- 01SitaWare EdgeThe dismounted application and the device stay exactly as fielded. Nothing from SynapseCommand is installed on them.
- 02Tactical observations and reportsFirst-hand observations, force tracking and reporting as they exist in the dismounted network, moving upward by the path the deployment already uses.
- 03Authorised exchange pathAn exchange point in the customer's architecture where dismounted traffic is already consolidated. SynapseCommand does not claim to speak SitaWare Tactical Communication.
- 04SynapseCommand decision-intelligence environmentRuns at a connected layer with the compute and accreditation to support it, never on the dismounted device.
- 05Analysis, planning and decision supportFusion and blue force agents place dismounted observation in context, with confidence and staleness carried explicitly rather than averaged away.
- 06Relevant outputs to authorised usersProducts go to the staff who need them. Anything returning toward the dismounted level is short, human-released and delivered through the existing command chain.
Data flows top to bottom; authority stays with the human decision gate.
Decision intelligence around the existing picture
Context for a single observation
One dismounted report gains meaning when it is placed against everything else known about that location over the preceding hours. That correlation is exactly what a dismounted user has no capacity to perform.
Confidence that survives the journey
A partial visual observation stays marked as a partial visual observation all the way into an operational assessment, instead of hardening into fact as it moves up the chain.
Gap visibility
Where dismounted reporting has stopped, the assessment shows a gap rather than continuing to display the last known picture as though it were current.
Evidence for the decision that follows
When a dismounted observation contributes to a higher decision, the link is recorded, so the contribution of the forward unit is visible in the replay rather than lost in aggregation.
How the decision cycle runs
Observation into fused picture
Dismounted reports reaching the authorised exchange point are correlated with other sources by the ISR fusion agent, contributing to a picture in which human observation and sensor data are distinguishable rather than merged.
Confirming or breaking an assumption
Plans rest on assumptions about ground, routes and presence. A dismounted observation is often the first thing that confirms or breaks one, and the decision layer treats that as a planning event rather than a map update.
Staleness management in disconnected conditions
Dismounted reporting is intermittent by design. The assessment ages what it holds, so a staff officer sees how old the forward picture is at the moment of decision.
Coalition releasability at the forward edge
Observations from a partner nation's dismounted units carry their releasability with them, so the picture that reaches each participant respects the caveats attached to the original report.
How this sits in a real environment
No dismounted footprint
SynapseCommand is not installed on a soldier-carried device and is not designed to be. The decision layer sits at a connected layer with the resources to run it.
Exchange happens where traffic consolidates
Any integration takes place where the customer already consolidates or gateways dismounted traffic, not at the device and not on the tactical bearer.
Designed for intermittence
SynapseCommand runs disconnected, so an environment fed by an intermittent forward flow behaves predictably: the picture ages visibly and reconciles when reporting resumes.
Interface access before anything else
Systematic publishes that SitaWare Edge exposes application programming interfaces, but not their specification. A programme therefore begins with the customer obtaining that access, which is a contractual step before it is a technical one.
Where the data goes, and where it does not
- Dismounted reporting is handled inside the customer enclave. Nothing is sent to an external service and no external model calls are made during operational use.
- Position and identity data from forward units is subject to the same record-level classification and releasability controls as any other source, which matters most where the disclosure risk is to people on the ground.
- Nothing generated by the decision layer reaches a dismounted user without a named human releasing it through the existing command chain.
- The assurance position is set out in full 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.
Systematic publishes that SitaWare Edge has an open architecture with application programming interfaces allowing integration of a variety of data types, and that it uses the proprietary SitaWare Tactical Communication protocol. Those interfaces are not published openly, SynapseCommand has no adapter for them, and no exchange with SitaWare Edge has been validated. A dedicated integration can be developed for an authorised customer or programme with access to the relevant interfaces.
Qualification
References to SitaWare Edge 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 Edge has an open architecture with application programming interfaces and that the ADatP-3 compliant Quick Forms module can be added to it, alongside the proprietary SitaWare Tactical Communication protocol. SynapseCommand implements none of these today, so no shared interface or standard is claimed. 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 SitaWare Edge 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 run directly on SitaWare Edge devices?
- No. The decision-intelligence environment requires compute, power and an accredited enclave that a dismounted device does not have. SynapseCommand runs at a connected layer and nothing is installed on the soldier-carried device.
- How could SitaWare Edge information contribute to SynapseCommand analysis?
- Dismounted observations that reach an authorised exchange point would be normalised with their originating unit, timing and confidence intact, then correlated with other sources so that first-hand human observation is weighed properly rather than merged into an average.
- Can SynapseCommand support decisions at the tactical edge?
- It supports the decisions taken about the tactical edge by staff at a connected layer. Anything returning toward a dismounted user is short, released by a named human and delivered through the existing command chain.
- What is the current status of SynapseCommand alongside SitaWare Edge?
- 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 the relevant interfaces and a representative environment are accessible.
- Is there an official Systematic partnership or certification?
- No. There is no partnership, certification or endorsement from Systematic, and nothing here should be read as suggesting otherwise.
- What happens when the forward link drops?
- The assessment ages what it holds and shows the gap. SynapseCommand runs disconnected by design, so an intermittent forward flow produces a visibly stale picture rather than a confident but outdated one.
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.