What happens after the vehicle receives sensor data?
Choose an exercise in the left control area. Watch how source observations, their limits, the crew display, and the commander's information brief change. The test uses the existing ATLAS commander-brief projectors and evidence scorer with a public VBK-inspired, vendor-neutral exercise contract.
Take the next information decision.
Review a fictional report, choose an information step, then watch the modeled handoff. Change a condition and see what still needs verification.
No real sensor, recipient or action is connected. Receipt, acknowledgment and understanding stay separate. This tab's replay is temporary; it is not a durable operational record.
Loading the local exercise…
The model is loading. No action is being performed.
- Modeled recipient availability
- Unknown
- Modeled acknowledgment
- None
- Recipient understanding
- Unknown
- Source observation offset
- Unknown
- Exercise elapsed time
- 0 s
- Modeled receipt offset
- Not produced
- State revision
- 0
Times are fictional exercise offsets, not measured latency. A restored link never makes an old observation current.
Your next information step
Choose deliberately. The model pauses at each decision.
Inspect the modeled event trail
1. See every stage, including what is missing
Proposed approved read-only data product; mock values here
Source, units, observed time, evidence class and quality
Do observations describe the same object? UNKNOWN until independently proven
Know, unknown, next information request, ownership
NOT SENT in training; live source/recipient workflow is separate
Choose a scenario
No exercise loaded
No measurement selected.
2. Soldier / vehicle crew
3. Commander / protection staff
4. What the Government evaluator can actually measure
No labeled track ledger yet.
No simulated event counts toward 99.5% independently validated real-world accuracy.
No military data link, crew authorization or recipient has been connected.
Select a scenario to inspect trace provenance.
5. How we interface with existing Army systems
VBK physical connectivity does not imply permitted read access to its message contracts. This table describes candidate integration paths and the evidence required to qualify each one.
| Source / system | Proposed integration | Currently demonstrated | Next required gate |
|---|---|---|---|
| Bradley VBK Gen3 / MAC / MAF | Approved read-only data product from OEM/Government gateway | Public interface concept + vendor-neutral exercise schema only | Army ICD, version, physical connection and witness |
| Acoustic arrays | Source-specific sound feature and quality contract | ATLAS acoustic modules and synthetic test evidence | Actual array, time sync and independent field truth |
| RF, radar, EO/IR | Separate authorized adapter per device / data type | Existing ATLAS fusion/adapter software and bounded test harness | OEM schema, actual measurement fidelity and independent match performance |
| TAK / CoT | Authorized information-only CoT exchange and named receipt | Existing ATLAS software translator and partner routes | Approved server/endpoints, recipient and actual transport witness |
| Signal Sights / Unity | Versioned ATLAS partner JSON snapshot → Unity presentation | Code-backed partner API and Unity client pattern | Partner device/session witness, latency and role-specific usability |
| Other Army / DoD programs | One approved ICD and supported transport adapter per program | NOT universally integrated or certified | System owner, data rights, compliance profile and an acceptance exercise |