DoD Acquisition Work System · TRIDENT-SA

Acquisition Work System Analysis

This file contains a set of examples to sequentially walk through a work system analysis of a fictional DoD acquisition case study. The tabs in the left side of the page show example artifacts that focus on specific aspects of the work system. All content is illustrative — TRIDENT-SA is a fictional program not attributed to any real acquisition — and is grounded in publicly available DoD acquisition policy (DoDI 5000.85, 5000.87, and related guidance) but does not represent official DoD policy.

About the analytical approach

A work system analysis of this type would draw on multiple sources of evidence — published policy and doctrine, program documentation, stakeholder interviews, and direct process observation. The fictional TRIDENT-SA case study assumes that kind of study was conducted, combining qualitative and quantitative inputs to surface where the as-is acquisition work system breaks down and where a redesigned system could create measurable value.

1 — Assumed sources
📋
Policy & Doctrine
DoDI 5000.85, 5000.87, DFARS, AAF guidance, GAO reports
📁
Program Documentation
Acquisition decision memoranda, milestone packages, cost estimates
🗣
Stakeholder Interviews
Would include program office, CAPE, oversight staff, and operational users
👁
Process Observation
Would cover milestone prep cycles, reporting events, and coordination meetings
→
2 — Analytical process
Work system decomposition
Map who does what, with what tools and information, and to produce which outputs
Pain point identification
Surface breakdowns in information flow, coordination, and tooling — classified by the type of intervention required
To-be design
Targeted interventions grounded in identified gaps, with quantifiable outcomes defined in advance
In this case study: 20 findings across 4 intervention levels
8 primary (information + tool/role) drive the to-be design · 12 broader context findings explain systemic constraints
→
3 — Artifacts in this file
B Work System Model — full program lifecycle
C D Workflow Diagrams — as-is process detail
★ Pain Points Catalog — 20 classified findings
E F Data Flows & Entity Relationships
G User Models — actor profiles and role changes
H Performance Measures — MOEs, MOPs, IPMs
A.1–B.3 Interface Concepts — to-be wireframe designs
Acquisition Work System
Tabs A – J

These tabs trace the TRIDENT-SA program through the Major Capability Acquisition (MCA) pathway — from the operational need that drove it to the key decisions, workflows, and organizations involved.

A — Operational Context places TRIDENT-SA within a broader joint mission context.
B — Work System Model shows the full 120-month program lifecycle across four organizational echelons.
C and D — Workflows are detailed swimlane diagrams of two critical decision preparation processes: the Analysis of Alternatives and Milestone B.
E — Data Flows maps how information moves between actors and systems in the to-be design.
F — Entity Relationships and G — Actor Profiles document the data model and the key roles most affected by the analysis.
H — Performance Measures defines quantifiable indicators for evaluating whether the proposed changes work.
I — Summary is a searchable catalog of all entities across the file.
J — Resources provides policy references and a glossary.
Interface Concepts — To Be
Tabs A.1 – B.3

These tabs show wireframe-level design concepts for two targeted interventions identified through the work system analysis.

A.1 — Storyboard narrates the Cluster 1 use case: structured AoA data package submission.
A.2, A.3, A.4 are annotated wireframes for the data entry form, CAPE validation view, and CDD traceability interface.
B.1 — Storyboard narrates the Cluster 2 use case: pre-milestone data reconciliation.
B.2, B.3 are annotated wireframes for the reconciliation dashboard and data submission feed.
About this view
Joint Operational Context — Indo-Pacific Theater
Contested A2/AD Environment — Near-Peer Adversary
Joint Task Force Mission: Synchronize Air Force, Navy, and Marine Corps to neutralize advanced missile threats and establish air superiority against a near-peer adversary's anti-access/area-denial (A2/AD) network.
Click any capability area for context details · TRIDENT-SA is highlighted as the focal program · Scroll down for additional JOC context
Air Force
Next-Generation Fighter Integration
Rapid integration of mission systems across next-generation fighters in development and fielding
MCA pathway · EMD phase
Airborne C2 Modernization
Resilient airborne command and control platforms for joint coordination in contested and degraded environments
MCA pathway · TMRR phase
Navy
Focal Program
Maritime Domain Awareness — Sensor Integration
TRIDENT-SA — Integrated sensor suite for persistent maritime domain awareness across contested sea space. Tracks surface, sub-surface, and air contacts in denied-access environments.
MCA pathway · Full lifecycle illustrated in this tool →
Surface Combatant Combat Systems
Upgraded combat management systems for destroyers and unmanned surface vessels; interoperability with carrier strike group networks
MCA pathway · Production & Deployment
Carrier Air Wing Integration
Evolving combat systems integration for carrier air wings operating in high-threat A2/AD environments
Multiple pathways
Marine Corps
Expeditionary Aviation Platforms
Rotary and tiltrotor aviation platforms optimized for distributed maritime operations and littoral maneuver
MCA pathway · LRIP
Distributed Operations C2
Command, control, and logistics systems enabling dispersed force operations at extended range in contested environments
SWP pathway · Active development
TRIDENT-SA applicability in other Joint Operational Contexts
◈ Arctic Littoral — A2/AD & Cyber-Electronic
Contested Arctic sea lines and under-ice ASW environments may leverage TRIDENT-SA sensor architecture
◈ European Corridor — Integrated Air Defense
High-density IADS and EW environments; TRIDENT-SA data-fusion approach applicable to distributed sensing requirements
View:
Diagram Key ▾ click to expand
Scroll or pinch to zoom · Drag to pan · Click any shape for details
100%
View:
Diagram Key ▾ click to expand
Scroll or pinch to zoom · Drag to pan · Click any shape for details
100%
View:
Diagram Key ▾ click to expand
Scroll or pinch to zoom · Drag to pan · Click any shape for details
100%
This diagram presents the conceptual entity-relationship model for the TRIDENT-SA to-be work system — showing the key data objects, who produces and consumes them, and how they connect to each other and to existing systems. Teal dashed entities are new to-be artifacts and systems introduced by Clusters 1 and 2. Gray entities are existing. Click any node for full details.
Schema note: ART-1A, ART-1B, ART-2A, and the Translation Layer are to-be additions not yet in the v5 entity schema — flagged for schema update.
Role / Actor
Organization
Artifact (existing)
Artifact / System (new to-be)
System (existing)
Process / Event
Decision Gate
New to-be flow
Existing flow
Role models for the four actors most directly affected by Clusters 1 and 2. Each card covers what the role needs, provides, does, and what helps or hinders their work. The Systems Engineer includes a full As-Is / To-Be toggle showing what changes under the to-be work system.
Quantifiable indicators for Clusters 1 and 2, organized into three types that answer different questions at different points in time. Read IPMs first (is the change happening?), then MOPs (is the work system running better?), then MOEs (did outcomes improve?). Gaps between types are diagnostic signals. Click any card for full detail.
Type
Cluster
① IPM: Is it happening?
→
② MOP: Is it working?
→
③ MOE: Did it matter?
Building summary…
Building references and glossary…
air.milsuite.mil/acquisition/trident-sa/aoa-data-package/submit
Annotation Panel
SCR-1A
AoA Data Package Entry Form