Battlefield sensor fusion
One fused operating picture
Overview
Sensor-fusion suites that merge radar, RF, optical and unmanned-platform feeds into a single operating picture, presented on immersive displays built for command posts. Decisions at machine speed, with the operator kept firmly in the loop.
One fused operating picture from every sensor on the battlefield, presented so a commander can decide in seconds, with the operator kept in the loop.
Capabilities
- Multi-sensor fusion across radar, RF, optical and unmanned-platform feeds
- Immersive command-post displays built for rapid comprehension
- Machine-speed correlation with human-in-the-loop decisions
- Feeds the counter-drone and unmanned-systems command layer
- Compresses the decision cycle: a commander sees one coherent picture instead of reconciling a dozen contradictory feeds under pressure
- Reduces the risk of fratricide and missed threats by resolving duplicate and conflicting tracks into a single trusted operating picture
Specifications
| Type | Sensor-fusion suite |
| Inputs | Radar / RF / optical / unmanned platforms |
| Output | Single fused operating picture |
| Origin | Independent / non-aligned |
In depth
Resolve the feeds into one picture
The suite accepts radar, RF, optical and unmanned-platform feeds and fuses them into a single operating picture. The detailed catalogue calls out multi-sensor fusion, immersive command-post displays and machine-speed correlation. The output is not another raw sensor feed. It is a common view intended to let a commander work from correlated tracks rather than reconcile separate displays by hand. The source records a direct connection to the counter-drone and unmanned-systems command layer. It does not publish a sensor count, track capacity or response time, so those are not implied by the phrase machine-speed correlation. The supported inputs and the single fused output are the defined system boundary. How the suite is configured depends on the radar, RF, optical and unmanned sources already available to the buyer and on the command-post display and software interfaces required for the operating picture.
Correlation without removing judgement
The catalogue makes the control boundary explicit: correlation runs at machine speed, but decisions remain human-in-the-loop. That separates the system's task of resolving tracks from the commander's task of deciding what the picture means and what action is authorised. The feature record also says the suite can reduce the risk of fratricide and missed threats by resolving duplicate and conflicting tracks into one trusted operating picture. That is the stated operational consequence of the fusion function, not a promise of error-free detection. The source is independent and non-aligned, with one accountable team from briefing through delivery and in-region sustainment. Integration is the work that makes the suite useful: identify the buyer's radar, RF, optical and unmanned inputs, connect the counter-drone and unmanned-systems command layer, and define how the resulting picture is shown at the command post. The record does not claim that the suite replaces those sensors or makes autonomous engagement decisions.
Inputs, correlation and command
The suite's defined inputs are radar, RF, optical and unmanned-platform feeds. Its defined output is one fused operating picture on immersive command-post displays. Between those points, machine-speed correlation resolves duplicate and conflicting tracks. This is the part of the system that addresses the problem of separate feeds describing the same contact differently. The documented result is a coherent picture for command, not an independent sensor that replaces the sources it receives. The integration boundary is equally clear. The fused picture feeds the counter-drone and unmanned-systems command layer, while the operator remains in the loop for decisions. Configuration must identify the buyer's sensors, the data interfaces, the command-post display and the route by which the picture reaches the command layer. No sensor count, track capacity or response time is published. The independent, non-aligned source and in-region sustainment provide the delivery relationship; they do not turn an unconfigured feed into a working command picture.
What the operator receives
The operator receives a fused picture rather than four unrelated categories of feed. Radar, RF, optical and unmanned-platform information is correlated into a common view, and immersive command-post displays present that view for rapid comprehension. Duplicate and conflicting tracks are part of the stated problem the suite addresses. Resolving them can reduce the risk of missed threats and fratricide, but the source does not claim that correlation removes uncertainty or makes every track correct. The command relationship remains human. Machine-speed correlation prepares the picture, the operator interprets it, and the counter-drone or unmanned-systems command layer receives the result. Integration therefore has to cover sensors, data interfaces, displays and command software. The product is not described as an effector and does not make autonomous engagement decisions. Its independent, non-aligned supply and one accountable team address delivery and sustainment after those interfaces and decision authorities have been defined.
Why Unstrat: the difference
Unstrat is the authorised global representative and distributor for this capability. It is already in service with a track record behind it, so you are buying something that has done the job elsewhere, not funding a first attempt. You are not the test bed.
Independent, non-aligned origin, with no political exposure to any major-power ecosystem.
One accountable team from first briefing through delivery and in-region sustainment.
Fuses radar, RF, optical and unmanned-platform feeds into a single picture.
How it reaches you
Related capability
View all →
Procurement & sustainment
Classification and the end-user-certificate chain are confirmed before this capability is represented to your market.
Sourced from an independent manufacturer: no major-power disclosure rules or political conditions.
A single team responsible from first briefing through delivery: not a chain of foreign primes to integrate yourself.
Lifecycle support and operator training delivered in-region, building capability that outlasts the initial deployment.
Questions buyers ask
What is battlefield sensor fusion?
It is the layer that turns many contradictory feeds into one picture a commander can act on. Ours merges radar, RF, optical and unmanned-platform data into a single operating picture on immersive command-post displays, correlating at machine speed while the operator stays in the loop on the decisions. It runs in command posts against live feeds rather than replaying recorded data in a demonstration.
Best alternative to SitaWare for a common operational picture
Give the incumbent its due first. Systematic publishes more than a million users, 45 or more SitaWare customers and 25 years of C4ISR delivery, with coalition data exchange and an SDK for third-party systems. If plugging into a NATO command network on day one is the requirement, buy it and staff it properly. Ours is the closer fit where sovereignty is the constraint: the same fused picture, supplied and sustained without a third-country licence in the update path, and delivered with the sensors that feed it.
Which sensors can be fused into one picture?
Radar, RF, optical and unmanned-platform feeds, presented as one picture on command-post displays. In our case the same supplier also provides passive radar, the mesh data links underneath and the unmanned platforms above, so the sensor chain arrives attached rather than assembled from four contracts. Whether a sensor you already own can be added is a question to put to us directly, because we do not publish an integration standard or SDK.
See: What is fused, and what each vendor publishesThe passive radar feed
Does automated fusion take the human out of the decision?
No. Correlation runs at machine speed and the operator stays in the loop for the decisions, which is a deliberate design choice rather than a limitation. The value is in resolving duplicate and conflicting tracks into one trusted picture, so a real threat is not lost between two contradictory feeds while a staff officer reconciles them under pressure.
See: Machine-speed correlation with the operator in the loop
Common operational picture software for a command post
Ours is built for the command post specifically: one fused picture on immersive displays sized for rapid comprehension under pressure. Systematic covers a wider span, from all levels of command in SitaWare Headquarters down to mounted commanders in Frontline, and a buyer needing a vehicle-borne tactical client should weigh that. We do not publish hardware requirements or installation footprint, so establish those during evaluation.
Sensor fusion for counter-drone operations
Counter-drone is where fusion earns its cost, because a small drone shows up differently to radar, RF and optical sensors and rarely on all three at once. Our suite feeds the counter-drone and unmanned-systems command layer directly, so a correlated track becomes a cued effector rather than three arguments about whether the contact is real. The passive radar layer contributes detections without radiating anything for the drone operator to notice.
See: Layered counter-drone detection and defeatThe emitter-free detection layer
Can the fusion suite take feeds from sensors we already own?
Raise it early, because we do not publish a third-party SDK or open API and will not imply one. Systematic does publish an extendable architecture with an SDK for legacy and third-party integration including air defence and joint fires, and for a mixed estate that is a genuine advantage. Where our case is strongest is a programme buying sensors, links and picture together, which removes most of the integration surface in the first place.
How does the picture behave when bandwidth collapses?
We do not publish a degraded-link specification, and Systematic does: low-bandwidth optimisation with intelligent prioritisation in Headquarters, and tactical communication protocols for denied or degraded environments in Frontline. What we can say is that our suite sits on top of our own anti-jam, self-healing mesh data links, so the link layer and the picture are engineered by the same team. Ask for measured behaviour on a degraded network during evaluation rather than accepting the principle.
See: Degraded-link rows, marked where unpublishedThe mesh layer underneath the picture
Is it better to buy fusion software alone or with its sensors?
SitaWare fuses data from sensors you buy elsewhere, which means separate contracts, separate export licences and a shared blame surface when a track is wrong. Ours is supplied alongside the passive radar, mesh data links and unmanned platforms that feed it, by one accountable team. Fewer interfaces means fewer arguments and a shorter path from a new sensor to a track on the display. If you already own a large mixed sensor estate, the calculation changes and you should say so early.
Our staff spend the first twenty minutes of every incident reconciling three feeds that disagree. What actually fixes that?
Correlation done before the picture reaches the staff, not after. Our suite resolves duplicate and conflicting tracks from radar, RF, optical and unmanned feeds into one trusted picture, which is what compresses the decision cycle and reduces the risk of both fratricide and a missed threat. The operator still decides. What changes is that the argument about whose feed is right happens in software rather than around a table while the contact closes.
We will not run foreign C4ISR software on a national command network. What are the realistic options?
A common operational picture is a live record of your force disposition, your sensor coverage and your intentions, so running it under foreign support terms is a choice worth making consciously. Ours carries no third-country approval in its update path and the team maintaining it is in your region. The honest trade is interoperability: Systematic publishes formal coalition data exchange including ADatP-03 messaging, and we do not publish our standards support. If joining a coalition network is a hard requirement, resolve that gap explicitly before contract.
Our tender scores NATO interoperability standards. Can you meet ADatP-03 and Link 16?
We do not publish our interoperability standards support, so treat that as unanswered until you have it from us in writing. Systematic publishes support for a range of military and civilian data-communication standards, with the Frontline Quick Forms module adhering to ADatP-03. Coalition tenders usually score this line first, and a buyer should not let any vendor blur it. Put the question in bid clarification and read the answer carefully.
For a small army building an operating picture from nothing, what should be bought first: the sensors, the links or the fusion?
Sequence them, but design them together. Sensors with no link layer produce data nobody sees, and a fusion suite with no sensors is an empty screen. The practical order is usually detection first, the mesh underneath it, then the fused picture as the number of feeds grows past what a staff can reconcile by hand. Because we supply all three, the architecture can be agreed once and delivered in phases rather than renegotiated at each step.
See: Detection, link and picture from one supplierThe link layer under the pictureHow the layers are assembled as a programme
When a track turns out to be wrong, who is accountable if the radar, the radios and the software came from three suppliers?
In practice, nobody, and that is the problem. Three vendors, three export licences and three support contracts produce a shared blame surface that resolves slowly and never during the incident. Our fusion suite arrives with the sensor chain attached, so there is one team to hold responsible for the picture as a whole, from the passive radar through the mesh links to the display. Write the accountability into the contract rather than assuming integration goodwill.
How large an installed base does your fusion suite have compared with SitaWare?
We do not publish installed-base or reference numbers, and Systematic publishes more than a million users and 45 or more customers. That is a real gap in a scored evaluation and we are not going to talk around it. What we can state is that the suites are in service in command posts correlating live radar, RF, optical and unmanned feeds, not running as demonstrations. Ask for references under a briefing agreement, where they can be discussed properly.
Battlefield sensor fusion: questions
What is Battlefield sensor fusion?
Battlefield sensor fusion is Unstrat's Land (Land Domain) capability: Sensor-fusion suites that merge radar, RF, optical and unmanned-platform feeds into a single operating picture, presented on immersive displays built for command posts. Decisions at machine speed, with the operator kept firmly in the loop.
How does Battlefield sensor fusion work?
Battlefield sensor fusion delivers its effect through Multi-sensor fusion across radar, RF, optical and unmanned-platform feeds, Immersive command-post displays built for rapid comprehension and Machine-speed correlation with human-in-the-loop decisions, capabilities matched to the requirement and confirmed under briefing rather than published.
Who makes Battlefield sensor fusion?
Battlefield sensor fusion is built by The Unmanned Systems Developer, whose focus is counter-uas, loitering munitions & unmanned aircraft. Unstrat represents The Unmanned Systems Developer to government and enterprise buyers worldwide as an independent, non-aligned prime vendor.
Why choose Battlefield sensor fusion over a major-power alternative?
Battlefield sensor fusion is sourced from an independent, non-aligned manufacturer, so it carries no major-power disclosure rules, upgrade-locks or political ramifications. Concretely: fuses radar, RF, optical and unmanned-platform feeds into a single picture. The capability is accountable to you, not to a foreign vendor's government and its release schedule.
How is Battlefield sensor fusion procured, and where can it be exported?
One fused operating picture from every sensor on the battlefield, presented so a commander can decide in seconds, with the operator kept in the loop. Every engagement begins with a briefing, and export eligibility is confirmed per market under briefing rather than published. Where controlled capabilities are involved, the classification and end-user-certificate chain is confirmed first. Battlefield sensor fusion is then sustained in-region by one accountable team from briefing through long-term operation.