HEIMDALL / COMMAND AND CONTROL (C2)

Battlefield coordination.
Every moving part
in view.

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.

Explore asset coordination ↗

Pilots under development

FRIENDLY ASSETS / COMMAND VIEWILLUSTRATIVE
SECTOR A / CANDIDATE OVERLAPSECTOR BFICTIONAL SITE · NO LIVE SYSTEMS · NO REAL LOCATIONSDRONE-01TEAM-01VEHICLE-01SEPARATE AREA
Know the status. Confirm receipt.SYNTHETIC
Connected moving assets.Visible task and receipt status.Human command authority.
01 / A BATTLEFIELD COORDINATION PILOT WE WANT TO TEST

See the moving assets.
Close the command loop.

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.

DRONES / PERSONNEL / VEHICLES

Keep each asset distinct.

Review location, availability and assigned task together. Keep individual identities visible within the wider battlefield picture.

TASK / RECEIPT / FOLLOW-UP

Know whether it arrived.

Test issuing an authorised instruction, confirming receipt and following status changes. An issued instruction, acknowledgement and completed task are different states.

COMMUNICATIONS / DATA FRESHNESS

Keep lost contact visible.

Hold a disconnected asset at its last reported position. Show the gap and pending acknowledgements instead of implying that the current position is known.

02 / TEST THE COMMAND LOOP

Three moving assets.
One place to coordinate.

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.

HEIMDALL / FRIENDLY ASSET COORDINATIONPILOT CONCEPT / SIMULATION
Fictional training area · Anonymous asset IDs
FRIENDLY ASSET GROUP AILLUSTRATIVE MOVEMENT
Current report Last known / link lostMovement is pre-authored
3current asset reports
0last-known positions
3distinct friendly assets
T+36 s

Scrubbing or replaying starts a new command review and clears earlier simulated requests.

FRIENDLY ASSETSSELECT TO COORDINATE
DRONE-01

Reconnaissance drone

Assigned task
Reported update
Source
STATUS REQUEST / RECEIPT

No request issued

WHAT THE COMMAND TEAM CAN SEE

01 / Reported status02 / Authorised request03 / Confirmed receipt04 / Follow-up
This is a pilot concept we want to test. All movement and acknowledgements are simulated in this browser; no command is sent to equipment or personnel.

03 / THE SENSOR PICTURE BENEATH THE COMMAND VIEW

A common picture.
With its limits in view.

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.

HEIMDALL / SITE A / COMMON PICTURESYNTHETIC CASE / 041

SITE A / COMMON PICTUREILLUSTRATIVE AREAS
Associated Separate / same origin Unavailable
—records associated
—independent source types
—unavailable records

SOURCE RECORDSSELECT TO INSPECT
SITUATION 041 / EVIDENCE REVIEW

Why associated?

    What is still missing?

      What could be checked next?

      This demo does not send alerts or execute actions.
      See the rules behind this demo

      All records and thresholds are illustrative. No live sensors, AI services or operational systems are connected. Association does not establish a common cause.

      Synthetic records · Anonymous areas · Source provenance retained

      04 / PILOTS UNDER DEVELOPMENT

      From shared awareness.
      Towards coordinated control.

      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.systems
      Background reading

      NATO / 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.

      CONTINUE EXPLORINGForestry →Command and Control C2 →