JOINT DOD · FUNCTION-TO-PORTFOLIO CROSSWALK · NOVEMBER 10, 2026
One mission question. Different service functions, systems and program owners.
SHIELD | ATLAS is a proposed interoperable decision-support layer across military services and joint organizations. The Army VBK is one bounded pilot. No branch loses its own system of record or decision authority.
1. Operational WFF / mission-function mapping
Read across a row to identify the equivalent mission problem, then select the government's actual program owner and source. These are planning examples, not verified field workflows.
| Comparable function | Army | Navy | Marine Corps | Air Force | Space Force | Joint / agencies |
|---|---|---|---|---|---|---|
| Command and control | Mission command; NGC2 | Fleet C2; Overmatch | MAGTF C2; expeditionary networks | AOC and DAF Battle Network | Space battle management | Joint Staff C4; mission-partner exchange |
| Intelligence and awareness | IPB; reconnaissance; source confidence | Maritime awareness; ISR | Expeditionary ISR; cyber | Air ISR; fusion; airspace | Space domain awareness; warning | Approved cross-domain intelligence; provenance |
| Fires and effects | Fires coordination; air defense awareness | Integrated warfare; air defense | Joint fires and air defense support | Air tasking and effects coordination | Space-effects support within command authority | Human authority and evidence custody; no weapon dispatch |
| Movement and maneuver | Ground and mounted movement | Fleet, littoral and maritime operations | Amphibious and expeditionary maneuver | Air mobility and air-base operations | Space operational maneuver context | Shared mission-object continuity and constraints |
| Protection and cyber | Force protection; C-UAS awareness | Maritime protection and cyber defense | Expeditionary protection and CBRN | Installation protection; cyber | Space-system resilience and network security | Authentication, adapter attestation, tenant isolation |
| Sustainment | Supply; maintenance; fuel; medical | Afloat/ashore logistics and readiness | Expeditionary logistics and transport | Air-base and mission support logistics | Space ground-system sustainment | Request, receipt, acknowledgment and effect separate |
| Training and assessment | Unit and formation exercise; AAR | Fleet and maritime rehearsal | MAGTF exercises | AOC / C2WSPTT rehearsal | Space-domain training | Joint simulated scenarios and independently measured outcomes |
2. Candidate acquisition and integration pathways
The organization is selected after the mission owner confirms a gap. Official institutional references are linked; no office here is represented as an existing ATLAS customer.
| Service or partner | Candidate public portfolio / integration office | Recommended first evaluation gate |
|---|---|---|
| Army | Army CPE C3N; applicable maneuver/protection portfolio | Army-authorized schema, C2 and mounted-crew handoffs |
| Navy | Department of Navy PAE Mission Systems (former PEO C4I/IWS and related programs) | Fleet-owned maritime source rights, shipboard acceptance and DDIL proof |
| Marine Corps | PAE Marine Corps: C2, intelligence, protection, fires/maneuver, logistics | MAGTF command owner, endpoint permissions and expeditionary rehearsal |
| Air Force | DAF PAE C3BM; relevant air and ISR program portfolio | Authorized air-operations contract and measured cross-system value |
| Space Force | Space Systems Command BMC3I | Authorized space feeds; source timing, security and classification evidence |
| Joint / DoD agencies | Joint Staff J6, DISA, DIU; named J2/J3/J4 or acquisition owner | Joint interoperability and releasability, trial sponsor, baseline outcomes |
| National Guard / Coast Guard | Mission-specific state/federal sponsor; Coast Guard normally DHS | Legal chain of command, permitted data exchange and partner authorization |
3. How to conduct a defensible pilot
Orient and audit
Specify who needs a decision, which existing systems they use, the baseline delay or failure, and what better evidence changes.
Map systems and authority
Document owner, data permissions, authentication, interface version, timestamps, releasability, known limits and partner approvals.
Test and sustain
Exercise source failure, DDIL, false positives, duplicates, recovery, operator workload, named-recipient delivery, acknowledgment and cost.
4. Capability and assurance boundaries
Prototype software, training demonstrations and published API schemas are not a certification, ATO, military network authorization, observed operational exchange or proof of field performance. AI output requires human scrutiny, and GPU requirements vary with workloads. A green simulated test is not a certification or fielded result. Never classify a missing or stale source as zero. Separate record saved, transport accepted, human acknowledged and independently measured outcome.
Synthetic training and rehearsal · Evidence-based evaluator main page · Twenty-five joint evaluator questions