Keep each asset distinct.
Review location, availability and assigned task together. Keep individual identities visible within the wider battlefield picture.
Drones. Personnel. Vehicles.
One command view to test.
We want to test Heimdall as a Command and Control (C2) layer for coordinating moving assets on a battlefield: where a drone, personnel team or vehicle was last reported, what it is assigned to do, and whether an instruction has been received. The aim is clearer oversight and a traceable control loop across existing systems, with people retaining command authority.
Pilots under development
The proposed pilot asks whether one shared view can connect friendly-asset status, assigned tasks and acknowledgements across existing telemetry, radios and reporting systems. Position freshness, permissions and interrupted communications are central questions to test.
Review location, availability and assigned task together. Keep individual identities visible within the wider battlefield picture.
Test issuing an authorised instruction, confirming receipt and following status changes. An issued instruction, acknowledgement and completed task are different states.
Hold a disconnected asset at its last reported position. Show the gap and pending acknowledgements instead of implying that the current position is known.
Explore a fictional friendly-asset group. Replay movement, select a drone, personnel team or vehicle, and simulate a status request. Confirm receipt separately, then interrupt the drone link to see how the picture changes.
Scrubbing or replaying starts a new command review and clears earlier simulated requests.
No request issued
Inspect a fictional site, add an activity register or interrupt a reporting feed. See why a duplicate message adds no independent confirmation, and why a schedule match does not establish identity.
All records and thresholds are illustrative. No live sensors, AI services or operational systems are connected. Association does not establish a common cause.
The ambition is to help a command team maintain oversight of drones, personnel and vehicles, connect instructions to the right asset, and see whether information or acknowledgement is missing. A pilot would test the full loop—from reported status to authorised task, receipt and follow-up—under human command.
Pilots are under development. Integration, access controls, information-sharing rules and operational suitability are assessed for each intended use. This synthetic demonstration has no live reporting or control connection.
Contact daniel@veil.systemsNATO / multi-source situational awareness
These sources inform the monitoring context. The scenarios and association rules are VEIL illustrations, not claims of partnership or validated product performance.