One system. Many missions.
One decision trail.
ATLAS is a joint DoD-ready design proposition for multiple services and defense agencies—not an Army-only platform or a replacement for existing military systems. It helps authorized people gather evidence, understand what changed, compare alternatives, coordinate responsibilities, and preserve the record of decisions and outcomes.
Not just “a sensor sends something.” Here is the usable output.
1 · Crew receives a fact with limitations
What was reported? Which sensor? When? Sound, direction, distance and speed only where measured. Missing values remain UNKNOWN. The crew sees if the information is old or uncorroborated.
2 · Commander receives a decision brief
What we know, what we do not know, who should verify, and what coordination is appropriate. No unverified aircraft identity or autonomous effect approval.
3 · Program office sees what is proven
Which source actually exchanged data? Was the recipient's receipt verified? What accuracy was measured? Which VBK/TAK/partner integration still requires authorization and physical testing?
If no authorized sensor is connected, the display explicitly says so. The page does not insert fictional readings to manufacture an impressive demonstration.
Whose problem are we solving?
Select a stakeholder. The explanation, available application links, current evidence limits and next acceptance gate change to match that mission.
Follow a real workflow
Six components, not hundreds of unexplained tabs
Every other module is a capability within one of these six jobs. Different users see different views over the same principles of ownership, evidence and decision authority.
Connector / USEIF
What: Input contracts, source identity, data validation.
For: OEM interfaces, sensor partners, units, authorized feeds.
How: Approved HTTP/CoT/SensorThings or purpose-built adapter; each connection and use case needs its own authority.
Evidence and Fusion
What: Attribute, reconcile and qualify observations.
For: Intelligence and operational staff.
How: Validation, freshness and provenance; do not infer unobserved data or turn a classification hypothesis into a fact.
Common Operating Picture
What: Role-specific situational context.
For: Crews, commanders, emergency managers.
How: Present the approved sources relevant to each echelon, with unknowns and stale data visible.
Planning and Support
What: Compare draft courses of action, dependencies and consequences.
For: Fires, maneuver, sustainment and protection staffs.
How: Bounded synthetic rehearsal first; real operational use requires validated data and permissions.
Human Decision and Handoff
What: Named responsibility, approval and reported outcome.
For: Staff owners and recipients.
How: Existing authenticated source-linked administrative handoff; this does not authorize weapon, jammer or VBK effects.
Evaluator and Partner Interfaces
What: Acceptance evidence and external display contracts.
For: PMs, engineers, primes, Unity/XR/TAK consumers.
How: Versioned schemas, source evidence, tests and independent partner/client validation.
The integration evidence map
“Can connect” is not the same as “connected.” Each row identifies who supplies the information, what ATLAS does with it, and what has actually been witnessed.
| Existing system or sensor | How it would reach ATLAS | What is proven now | What the authorized DoD sponsor would need to accept |
|---|---|---|---|
| Approved OGC SensorThings provider | Server makes a bounded HTTPS read; saves source, time, units, completeness and record digest | Code-backed authenticated source adapter and durable record; a particular source must be configured and witnessed | Actual owned device, calibration and field conditions |
| Acoustic microphone / audio detector | Audio feature or classifier report through a specific approved software path | Classifier software and limited prior test record, including documented Mavic/Mini misclassification | Real mounting, environmental noise, independent label set, bearing/range instrumentation if required |
| RF, radar and electro-optical/infrared sensor | Vendor-provided permitted data product adapted into ATLAS observation contract | Adapter and fusion concepts exist; no universal sensor compatibility or calibration claim | Device/OEM interface, data rights, measurements, time sync, independent test |
| Army VBK / VIPERS / MAF | Proposed read-only interface from existing vehicle protection controller | NOT CONNECTED to a witnessed Army vehicle | Government-approved interface documents, safety, security and on-the-move hardware test |
| TAK / Cursor on Target | Published software bridge and separately configured authorized TAK Server | Code-backed CoT interchange; military recipient receipt and certified vehicle deployment unverified | Named TAK owner, real configuration, actual receipt and interoperability witness |
| Signal Sights / Unity immersive display | Existing ATLAS partner JSON/snapshot APIs read by an independently configured Unity client | ATLAS API and Unity client pattern; prospective partner, not a signed/fielded integration | Partner agreement, actual client data ingestion, human-factors/performance witness |
| IBCS, FAAD C2, AFATDS and other programs of record | Would require individual Government interfaces and accredited network boundaries | DESIGN ALIGNMENT ONLY; not a connection receipt | Appropriate program owner, ICD, network/security authorization, validation |
| Named staff/commander information handoff | Existing ATLAS source-linked administrative workflow and recipient inbox | Code-backed administrative receipt pathway; no live tactical command network assumed | Authorized command users, correct military network, independently confirmed delivery and usability |
Technical inventory: existing ATLAS Connections, fusion, partner, CoT/TAK and crew modules. This is not a blanket compatibility or certification claim.
One decision chassis; service-specific missions and authorities
The Army vehicle example below is a deliberately bounded evaluation wedge—not the definition of ATLAS. A joint sponsor must select the system of record, source rights, operational authority, releasability, deployment boundary, acceptance tests, and recipient for every service or agency use case.
Army & Marine Corps
Maneuver, expeditionary operations, force protection, fires coordination and contested sustainment. Existing tactical systems keep control and record ownership.
Navy
Maritime common picture, surface and subsurface observations, afloat sustainment and joint handoffs. No claim of authenticated shipboard or certified fleet-system integration.
Air Force & Space Force
Air operations and ISR coordination, installation protection, PNT resilience and space-domain context. Native operational feeds require sponsor-approved interfaces and independent trials.
Joint commands & defense agencies
Multi-echelon coordination, evidence fusion, logistics and geospatial/cyber support; share only with verified organization, unit and releasability authority.
Guard, Coast Guard & partners
Defense support and interagency/coalition handoffs remain separately authorized. Coast Guard service status and National Guard command authority depend on mission and legal context.
How to challenge the fit
Measure gaps against existing DoD programs. If the current system already delivers equivalent timely, reliable, secure outcomes, ATLAS should not create redundant infrastructure.
Review the full joint-DoD evaluator FAQ →Joint DoD warfighting-function / program-office crosswalk
The Navy, Marine Corps, Air Force and Space Force are not forced into Army doctrine. Compare the actual function, service program portfolio, existing system, operator impact and proof required for each pilot. Candidate offices are not sponsors.
Scoped Army vehicle-protection evaluation example
The Army's current PAE Maneuver Ground emphasizes taking care of Soldiers, being a great teammate, and delivering formation-based capabilities. Its Assistant Capability Program Executive publishes Futures, Adaptive Squad Architecture, Soldier Integration Facility and Soldier Enhancement Program as lines of effort. These are Army-described priorities and LOEs. The application mapping below is **ISS analysis**, not an Army endorsement.
| Army priority / published LOE | SHIELD contribution and existing mission owner | Truthful evaluation question |
|---|---|---|
| Deliver formation-based capabilities | Mounted crew → dismount → platoon/company shared evidence, role-relevant views, human review | Can two verified users receive consistent source meaning while the vehicle changes position and communications vary? |
| Take care of our people | Reduced transcription burden and clearer failure indication; protection awareness before additional dashboard complexity | Does crew workload improve against current process in a representative supervised trial? |
| Be a great teammate | Complement VBK, installed computers, TAK and the Government's chosen C2 backbone; retain OEM data rights and ownership | Can one approved read-only data product be connected without altering safety-critical control? |
| Futures / Adaptive Squad Architecture | Digital interface contract and operator/echelon filtering, documented adaptations; no claim of Army plug-in certification | Can a modular software adapter be introduced and independently tested under existing MOSA processes? |
| Soldier Integration Facility | Instrumented end-to-end field configuration and human-factors acceptance | Can a witnessed actual-device test reproduce the claimed latency, data quality and handoff? |
| Soldier Enhancement Program / industry | Government and industry-owned joint evaluation with ISS as a candidate software component, rather than a replacement platform | Who sponsors the requirements and test protocol, and who owns transition? |
| PM XM30 Digital Trinity: MOSA, digital engineering, DevSecOps | Versioned interfaces, regression evidence, change and release controls | Can the software satisfy the actual program interface, cyber and configuration criteria? |
Primary Army references: PAE Maneuver Ground mission and priorities · Assistant Capability Program Executive LOEs · PM XM30 digital acquisition.
Which kind of proof is this?
We make existing systems work together, then prove the value.
“Start with the Soldier, not the catalog. A crew or sensor already knows something, but another staff element may not see it in time or understand its limitations. ATLAS's first job is an authorized, trustworthy connection. Its second is to show the evidence in the language of the person who needs it. Its third is to support a human choice and preserve a verified handoff. We would test that chain against the sponsoring DoD organization's actual process. The Army VBK example does not replace VBK, TAK, the vehicle computer or the commander, and Navy, Air Force, Marine Corps, Space Force and joint-command trials require their own source and acceptance contracts. We will show exactly what works today, what is a software rehearsal, what requires an interface agreement, and what must be proven on an actual moving vehicle.”