AppendixHAT21-CDD-Revised-21Feb07forPublicRelease.pdf

Joint Capabilities Board – Recommended Changes Included – 1 February 2007 Agile Transportation for the 21st Century (AT21) Capability Development Document (CDD)

FINAL REVISION – 21 Feb 07 3/6/2007

UNCLASSIFIED

CAPABILITY DEVELOPMENT DOCUMENT

FOR

USTRANSCOM

Agile Transportation for the 21st Century (AT21)

Enabling the USTRANSCOM Focus Warfighter Operations Vision

Increment: I

ACAT: III

Validation Authority: JROC

Approval Authority: JROC

Milestone Decision Authority: Chief of Staff, USTRANSCOM

Designation: JROC Interest

Prepared for Milestone B Decision

Date: 21 February 2007

FINAL REVISION – 21 Feb 07 3/6/2007 i

THIS PAGE INTENTIONALLY LEFT BLANK

FINAL REVISION – 21 Feb 07 3/6/2007 ii

Agile Transportation for the 21st Century (AT21) Capability Development Document

12 October 2006

Program Manager: 3

________________________________ 7

DEAN PEEBELS 8

GS-14 9

USTRANSCOM/TCAQ (Acquisition) 10

Program Manager, AT21 11

Submitted: Approved: 15

________________________________ _________________________________ 19

PAUL SELVA WILLIAM JOHNSON 20

Brigadier General, USAF Major General, USA 21

Director, Operations and Logistics Chief of Staff 22

Functional Sponsor Milestone Decision Authority (MDA) 23

OPR: USTRANSCOM TCJ3-OI 29

DSN 779-1849 30

Commercial (618) 229-1849 31

FINAL REVISION – 21 Feb 07 3/6/2007 iii

Executive Summary 32

This CDD provides the operational performance attributes necessary for USTRANSCOM 33 to design, develop, deliver, and deploy transformed processes and technologies to fulfill 34 warfighter distribution and deployment command and control capabilities. This initiative 35 is entitled USTRANSCOM Agile Transportation for the 21st Century (AT21). 36

For over a decade USTRANSCOM has engaged in broad efforts to modernize the Defense 37 distribution system business practices while updating and integrating myriad disparate information 38 systems. Evolving world events and the challenge of being designated the Distribution Process 39 Owner (DPO) are driving requirements for higher levels of interoperability across the Services and 40 among U.S. allies and coalition partners. To answer increasing demands on the DPO to support 41 force projection and sustainment, the AT211 is focused on identifying, exploring, and applying best 42 commercial business processes and practices and supporting Government Off-the-shelf (GOTS) and 43 commercial-off-the-shelf (COTS) software tools to improve the planning and managing of DPO 44 distribution and deployment assets in support of the combatant commands (combatant command). 45 The DPO transformation into a fourth party logistics (4PL) service provider is underway. As a 4PL, 46 the DPO will combine process and technology under the AT21 business enterprise umbrella to 47 centralize accessibility to the information from the execution elements (Transportation Component 48 Commands (TCCs) and commercial carriers) making the information readily available to all 49 customers. The USTRANSCOM Focus Warfighter I (FW I) initiative took place during Spring 50 2005 when TCJ3 reorganized – involving combatant command-oriented branches and the redesign 51 of the requirements/ validation process. This effort proved successful from USTRANSCOM and 52 other combatant commands’ perspectives and resulted in better warfighter support. The follow-on 53 FW II concept transformation realigns2 planning functions while realigning current processes to 54 meet specific combatant command support requirements. FW II provides the baseline for IT 55 development to increase effectiveness in delivering combat power to the warfighter while enhancing 56 visibility and efficiency of the distribution process. The concept permits USTRANSCOM to tailor 57 its Deployment & Distribution Operations Center (DDOC) operations to respond to world events at 58 the appropriate level of effort required—by standing-up combatant command-specific divisions in a 59 Fusion Center. FW II transitions TCJ3 from the strategic planning/monitoring function to a more 60 heavily focused E2E planning/concept of operations (CONOPS) event management development 61 role. 62

This document describes the requirements and capabilities necessary to support continuous and 63 distributed joint force operations, demanding unprecedented logistics agility and precision. AT21 64 must support global maneuver across intertheater distances and operational maneuver throughout a 65 geographic combatant commander’s (CCDR) area of responsibility (AOR); and must be able to 66 manage and sustain distribution and deployment support to widely dispersed joint forces over a large 67 area of operations. AT21 will aid the DPO in the successful accomplishment of both strategic and 68

1 In March 2005, Commander, United States Transportation Command (USTRANSCOM) completed an Advanced Concept Technology Demonstration (ACTD) aimed at applying mature technologies for capturing distribution requirements, collaboratively visualizing requirements and distribution resources, optimizing and synchronizing modes and assets, and producing schedules and execution orders. These objectives are now an integral part of the USTRANSCOM Fusion Center. USTRANSCOM briefed the ACTD Military Utility Assessment (MUA) results to the Deputy Under Secretary of Defense (DUSD), Advanced Systems & Concepts (AS&C), in February 2005, who approved a new start acquisition program that would build on the pilot effort and expand the initial capabilities.

2 The Focus Warfighter II realignment charter is to develop a process that capitalizes on a joint fused effort to assess and plan multi-modal E2E solutions. This process will synchronize the distribution of forces and sustainment into the theater through collaborative planning, proactive transportation analysis, performance monitoring, increasing distribution effectiveness and customer confidence. Combatant command-oriented branches in the Fusion Center will process all combatant command E2E requirements and provide a natural link into the respective theater Joint DDOC (JDDOC).

FINAL REVISION – 21 Feb 07 3/6/2007 iv tactical capabilities of the distribution E2E process. This initiative will directly support Joint 69 Logistics/Distribution Joint Integrating Concept (JL (D) JIC) imperatives and significantly 70 contribute to Joint Deployment and Distribution Enterprise (JDDE) capability gaps. Focus 71 Warfighter and AT21 rest on three pillars: Process improvement; Organization; and Information 72 Technology. AT21 is just a portion of the larger USTRANSCOM effort to improve E2E 73 distribution for the Department of Defense (DOD). FW II focuses on transportation planning and 74 customer relationship management (CRM). Within twelve to thirty-six months, AT21 will deploy 75 an initial increment to support the combatant command. Increment 1 capability addresses 76 Requirements Consolidation and Workflow Management. Following increment 1 initial operational 77 capability (IOC) increments 2 and 3 will focus on strategic and operational level optimization 78 respectively. The objective is to optimize controlled distribution processes by employing advanced, 79 globally networked tools and techniques. Advanced customer interfaces will amplify the combatant 80 commands’ understanding of distribution bridge constraints and accelerate optimal development and 81 execution of force deployment and sustainment requirements. The external and internal looking 82 domains depend on accurate, timely and complete data availability across the E2E distribution 83 enterprise. FW II capability and processes operate in an environment that embraces net-centricity, 84 seamless data capture and situational awareness of all constrained cargo and passenger 85 distribution/movement requirements for Deployment, Sustainment, and Redeployment. In 86 conjunction with the DLA Integrated Data Environment (IDE) FWII will enable situational 87 awareness of unconstrained movements. AT21 will provide situational awareness of distribution and 88 movement requirement closure to the satisfaction of the combatant command. AT21 must provide 89 accurate3, timely and decision-relevant information and data that associate resource constraints 90 involving lift assets, distribution infrastructure and resources and node processing issues. AT21 will 91 provide the customer a web-enabled interface to track distribution/deployment requirements 92 throughout the workflow process. AT21 will provide CRM-like capabilities that capture customer 93 point of contact (POC) and profile information and workflow status; and provide requirements 94 tracking, exception management, and feedback/reporting capabilities (when fully implemented). 95 AT21 will have the ability to pass movement requirements and status of lift assets from the 96 automated optimization engine that produces optimized, intermodal schedules to the execution 97 systems that perform the booking functions to reserve space on conveyances, and accept the return 98 information confirming the booking execution. This schedule will include passenger and cargo, 99 force deployment, sustainment, redeployment, and retrograde information. Based on the schedule, 100 forecasting and advanced shipment notification will be provided to downstream distribution pipeline 101 nodes. In accordance with the tenets of the Clinger-Cohen Act (CCA), AT21 will harmonize with 102 business process improvements so that the resultant integrated and synchronized distribution/ 103 deployment processes provide consistent, increasingly more effective/efficient operations that meet 104 warfighter/customer requirements. 105

Key Performance Parameters: AT21 is an integrated user environment through which all 106 distribution movement process business transactions and collaborative sessions will be conducted. 107 The AT21 solution must provide accurate, timely and decision-relevant information and data that 108 associate resource constraints involving lift assets, distribution infrastructure and resources and 109 node processing issues. AT21 must be continuously available, reliable, and secure, while 110 producing significant improvements in the responsiveness and productivity of the USTRANSCOM 111 distribution planning staff and business processes. Failure to meet any AT21 KPP threshold listed 112 in Table 5 can be cause for the process or system selection to be reevaluated or the program to be 113 reassessed or terminated. Appendix A contains tables defining additional attributes and the Net 114 Ready-KPP (NR-KPP). 115

3 confirmed accurate data from the authoritative source; data is current as determined by established business processes

FINAL REVISION – 21 Feb 07 3/6/2007 v

Revision History 116

Revision No. Date of Revision Approved By

.01 SOEDE

Concepts Insertion

1 Dec 2005 DRAFT ONLY – NO APPROVAL

NECESSARY

.02 KPPs 12 Dec 2005 DRAFT ONLY – NO APPROVAL

NECESSARY

.03 (Draft for WIPT Review)

10 Feb 2006 DRAFT ONLY – NO APPROVAL

NECESSARY

.04 (Draft for IPT Review)

14 Feb 2006 DRAFT ONLY – NO APPROVAL

NECESSARY

.05 (Internal staffing revisions)

1 May 2006 DRAFT ONLY – NO APPROVAL

NECESSARY

.06 (Incorporates Directorate, TCC Comments)

1 June 2006 DRAFT ONLY – NO APPROVAL

NECESSARY

.07 (Updates Appendix A)

24 July 2006 DRAFT ONLY – NO APPROVAL

NECESSARY

.08 (Final Draft Submission to

KM/DS

3 August 2006 USTRANSCOM/TCCS (Milestone Decision Authority) Approval

1 (Incorporates and adjudicates all

KM/DS

Comments)

12 October 2006 USTRANSCOM/TCCS (Milestone Decision Authority) Approval

1.1 (Incorporates and adjudicates all FCB-Level KM/DS Comments)

1 December 2006 Technical corrections only, no additional approval necessary

1.2 (Incorporates

JCB

recommended changes)

1 February 2007 Technical corrections only, no additional approval necessary

1.3 (Incorporates JROCM staffing recommendations)

21 February 2007 Technical corrections only, no additional approval necessary

FINAL REVISION – 21 Feb 07 3/6/2007 vi

Table of Contents 118

1. CAPABILITY DISCUSSION................................................................................................................................1 119

1.1 Agile Transportation for the 21st Century (AT21) Advanced Concept Technology Demonstration 120 (ACTD) and Military Utility Assessment (MUA) – November 2004-March 2005.................................................1 121

1.2 USTRANSCOM Focus Warfighter (FW) (See Appendix G) ......................................................................2 122

1.3 Process-Advancing-Technology (Prototype, Initial and Full Operational Capability, IOC and FOC)....3 123

1.4 Joint Future Concepts/Mission Need/Capabilities Defined.......................................................................3 124

1.4.1 Focused Logistics ..................................................................................................................................5 125

1.4.2 Applicability to DPO Mission Transformation Requirements ...............................................................6 126

2. ANALYSIS SUMMARY........................................................................................................................................7 127

2.1 AT21 contributes to the USTRANSCOM Focus Warfighter II Operations initiative...............................10 128

2.2 Data Accuracy .........................................................................................................................................10 129

2.3 Process Control .......................................................................................................................................11 130

2.4 Optimization ............................................................................................................................................12 131

2.5 Collaboration ..........................................................................................................................................13 132

2.6 Analysis of Alternatives Summary ...........................................................................................................14 133

2.7 System Attributes: ....................................................................................................................................15 134

3. CONCEPT OF OPERATIONS – SUMMARY (SEE APPENDIX G)..............................................................17 135

4. THREAT SUMMARY.........................................................................................................................................22 136

4.1 Threat / Operational Environment ..........................................................................................................22 137

4.2 Potential System Threats ...............................................................................................................................24 138

5. PROGRAM SUMMARY.....................................................................................................................................25 139

5.1 AT21 ACTD .............................................................................................................................................25 140

5.2 New Program Start..................................................................................................................................25 141

5.2.1 Deployment Strategy: ..........................................................................................................................25 142

6. SYSTEM CAPABILITIES REQUIRED FOR AT21 INCREMENT 1 ...........................................................27 143

6.1 Increment 1 Key Performance Parameters..............................................................................................27 144

6.1.1 On-Time Delivery (Customer Satisfaction/Responsiveness)................................................................33 145

6.1.3 System Availability .....................................................................................................................................34 146

6.2 Increment 1 System Attributes .................................................................................................................34 147

6.3 Increment 1 Technical Requirements ......................................................................................................38 148

6.4 System Availability and Reliability Parameters ...........................................................................................40 149

6.4.1 Reliability ...................................................................................................................................................40 150

6.4.2 Information Integrity (Transmission Assurance)........................................................................................41 151

6.4.3 Data Availability.........................................................................................................................................41 152

6.4.4 System Compatibility ..................................................................................................................................41 153

6.5 Additional Increment 1 Attributes............................................................................................................41 154

6.5.1 Human-Computer Interface (HCI) ......................................................................................................41 155

6.5.2 Workload .............................................................................................................................................42 156

6.5.3 Data Accuracy .....................................................................................................................................42 157

6.6 Summary of Increment 2 and Increment 3 attributes (to be developed using evolutionary acquisition 158 strategy (see paragraph 5-1) under follow-on CDD). .........................................................................................43 159

7. FAMILY OF SYSTEM AND SYSTEM OF SYSTEMS SYNCHRONIZATION .......................................49 160

8. INFORMATION TECHNOLOGY AND NATIONAL SECURITY SYSTEMS (IT AND NSS) 161

SUPPORTABILITY..................................................................................................................................................62 162

9. INTELLIGENCE SUPPORTABILITY..........................................................................................................64 163

9.1 Geospatial Information (see paragraph 2.2c) .........................................................................................65 164

FINAL REVISION – 21 Feb 07 3/6/2007 vii

9.2 Source Information Requirements (Reference Appendix A, SV-6)...........................................................65 165

10. ELECTROMAGNETIC ENVIRONMENTAL EFFECTS (E3) AND SPECTRUM 166

SUPPORTABILITY..................................................................................................................................................65 167

11. ASSETS REQUIRED TO ACHIEVE IOC.................................................................................................65 168

12. SCHEDULE AND IOC / FOC DEFINITIONS ..........................................................................................66 169

13. OTHER DOCTRINE, ORGANIZATION, TRAINING, MATERIEL, LEADERSHIP AND 170

EDUCATION, PERSONNEL AND FACILITIES (DOTMLPF) CONSIDERATIONS ....................................66 171

13.1 DOTMLPF Analysis ................................................................................................................................66 172

13.1.1 Doctrine...............................................................................................................................................66 173

13.1.2 Organization........................................................................................................................................66 174

13.1.3 Training ...............................................................................................................................................67 175

13.1.4 Materiel ...............................................................................................................................................67 176

13.1.5 Leadership and Education...................................................................................................................68 177

13.1.6 Personnel .............................................................................................................................................68 178

13.1.7 Facilities ..............................................................................................................................................68 179

13.2 Ideas for Materiel Approaches ................................................................................................................69 180

13.3 Analysis of Material Approaches (AMA).................................................................................................69 181

13.4 Final Materiel Recommendations............................................................................................................69 182

13.4.1 Material Recommendations .................................................................................................................69 183

13.4.2 Key Boundary Conditions....................................................................................................................69 184

13.5 Non-material/DOTMLPF Implications and Constraints.........................................................................70 185

13.5.1 Doctrine...............................................................................................................................................70 186

13.5.2 Organization........................................................................................................................................70 187

13.5.3 Training ...............................................................................................................................................70 188

13.5.4 Leadership and Education...................................................................................................................70 189

13.5.5 Personnel .............................................................................................................................................70 190

13.5.6 Facilities ..............................................................................................................................................70 191

14. OTHER SYSTEM ATTRIBUTES...............................................................................................................70 192

15. PROGRAM AFFORDABILITY..................................................................................................................71 193

APPENDIX A. ARCHITECTURE PRODUCTS ................................................................................................A-1 194

A1. AV-1 OVERVIEW AND SUMMARY INFORMATION .............................................................................A-1 195

A1. AV-1...................................................................................................................................................................A-1 196

A3. OV-2 OPERATIONAL NODE CONNECTIVITY DESCRIPTION.........................................................A-11 197

A4. OV-4 ORGANIZATIONAL RELATIONSHIPS CHART .........................................................................A-20 198

A10. SYSTEMS DATA EXCHANGE MATRIX (SV-6)...................................................................................A-48 199

A.12 MISSION AREA INITIAL CAPABILITY DOCUMENTS (MA ICD) -KPP REQUIREMENTS CROSS-200 WALK AND LINKAGE.....................................................................................................................................A-130 201

A.13.1 NET-READY KEY PERFORMANCE PARAMETER.......................................................................A-130 202

A.16.1 TRANSPORT FAMILY (TERRESTRIAL DOMAIN) KIP 1: DISN SERVICE NETWORK / DISN 203 TRANSPORT ......................................................................................................................................................A-132 204

A.16.2 TRANSPORT FAMILY (TERRESTRIAL DOMAIN) KIP 7: DISN SERVICE 205

NETWORK/CUSTOMER INTERFACE .........................................................................................................A-132 206

A.16.3 APPLICATION ENTERPRISES SERVICE FAMILY KIP 9: APPLICATIONS SERVER TO 207

DATABASE SERVER (NCES TRANSITION)................................................................................................A-133 208

A.16.4 APPLICATION ENTERPRISES SERVICE FAMILY KIP 10: CLIENT TO SERVER (NCES 209

TRANSITION) ....................................................................................................................................................A-134 210

FINAL REVISION – 21 Feb 07 3/6/2007 viii

A.16.5 APPLICATION ENTERPRISES SERVICE FAMILY KIP 17: APPLICATIONS SERVER TO 211

SHARED DATA (NCES TRANSITION)..........................................................................................................A-134 212

APPENDIX B. REFERENCES.............................................................................................................................B-1 213

APPENDIX C. ACRONYM LIST ........................................................................................................................C-1 214

APPENDIX D – ANALYSIS DETAILS................................................................................................................D-1 215

D1. BACKGROUND...............................................................................................................................................D-1 216

D2. OUTCOMES AND EXECUTION PLANS ....................................................................................................D-1 217

APPENDIX E. GLOSSARY..................................................................................................................................E-1 218

APPENDIX F. SOEDE REQUIREMENTS ARCHITECTURE .......................................................................F-1 219

F1. BACKGROUND ...............................................................................................................................................F-1 220

F2. EXPECTED OUTCOMES...............................................................................................................................F-3 221

F3. ANTICIPATED PERFORMANCE GAINS: .................................................................................................F-3 222

APPENDIX G. AT21 CONCEPT OF OPERATIONS / FOCUS WARFIGHTER INITIATIVE ................. G-1 223

G1. AT21 Concept of Operations ......................................................................................................................G-1 224 G1.1 Situation....................................................................................................................................................G-2 225 G1.2 AT21 Support Mission .............................................................................................................................G-2 226 G1.3 Operating Environment ...........................................................................................................................G-3 227 G1.4 Execution ................................................................................................................................................G-4 228 G1.5 Service Support Functions .......................................................................................................................G-5 229 G1.6 System and Process Integration...............................................................................................................G-8 230

G2. OVERVIEW ................................................................................................................................................. G-13 231

G2.1 FOCUS WARFIGHTER I – Organizational Realignment ......................................................................G-14 232 G2.2 FOCUS WARFIGHTER II – Single Customer Point of Entry ................................................................G-14 233 G2.3 FOCUS WARFIGHTER III – Fusion Center / BRAC Integration ..........................................................G-15 234 G2.3.1 Critical Success Imperatives................................................................................................................G-15 235

G3. FUSION CENTER CONCEPT OF OPERATIONS ................................................................................. G-16 236

G3.1 ASSESS: combatant command Plan Assessment and Capacity Management ........................................G-16 237 G3.2 FUTURE PLANS: Mission Allocation and Capacity Management........................................................G-17 238 G3.3 CURRENT PLANS: Task Component Commands..................................................................................G-17 239 G4 AT21 and Fusion Center Operational Benefits..........................................................................................G-18 240

Table of Figures 242

Figure 1. Stovepiped Planning Loses Synergy and Visibility ........................................................................................4 243 Figure 2. End-to-End Distribution Process...................................................................................................................7 244 Figure 3. AT21 Functional Pillars ..............................................................................................................................10 245 Figure 4. AT21 Process Control Pillar .......................................................................................................................11 246 Figure 5. AT21 Optimization Pillar ...........................................................................................................................12 247 Figure 6. AT21 Collaboration Pillar...........................................................................................................................13 248 Figure A-1. AT21 High-Level Operational Concept Graphic (OV-1)..................................................................... A-10 249 Figure A-2a. AT21 Operational Node Connectivity Description (OV-2) High Level ............................................. A-11 250 Figure A-2b. OV-2 Joint Deployment and Distribution Architecture – AT21 Mission Area................................... A-14 251 Figure A-3. AT21 Organizational Relationships Chart (OV-4) .............................................................................. A-23 252 Figure A-4. AT21 Operational Activity Model (OV -5) [1 of 5].............................................................................. A-24 253 Figure A-5. AT21 Operational Activity Model (OV -5) [2 of 5].............................................................................. A-26 254 Figure A-6. AT21 Operational Activity Model (OV -5) [3 of 5].............................................................................. A-29 255

FINAL REVISION – 21 Feb 07 3/6/2007 ix

Figure A-7. AT21 Operational Activity Model (OV -5) [4 of 5].............................................................................. A-31 256 Figure A-8. AT21 Operational Activity Model (OV -5) [5 of 5].............................................................................. A-33 257 Figure A-9. JDDA OV-6c Template ........................................................................................................................ A-35 258 Figure A-10. AT21 Operational Event-Trace Description Diagram (OV 6-c)........................................................ A-37 259 Figure A-11a. AT21 Notional System Environment ................................................................................................ A-38 260 Figure A-11b. AT21 Systems Communications Description (SV-2) ........................................................................ A-39 261 Figure A-12. AT21 System Functionality Description (SV-4) ................................................................................. A-41 262 Figure A-13. SYSTEMS DATA EXCHANGE MATRIX (SV-6) ................................................................................ A-50 263 Table A-4. AT21 Technical Standards Profile (TV-1) ........................................................................................... A-121 264 Figure F-1. SOEDE DPO Operational Requirements ..............................................................................................F-1 265 Figure F-2. SOEDE AT21 Increment 3 Requirements ..............................................................................................F-3 266 Figure G-1. Requirements, Constraints, and Single Booking ...................................................................................G-7 267 Figure G-2. AT21 Data Flow ....................................................................................................................................G-8 268 Figure G-2a. AT21 Process Flow (Joint Booking Initiative, JBI, is notional) ..........................................................G-9 269 Figure G-2b. AT21 Corporate Operating Environment ..........................................................................................G-10 270 Figure G-3. Integrated, Intermodal Corporate Operating Environment ................................................................G-13 271 Figure G-4. Fusion Center Process ........................................................................................................................G-16 272

Index of Tables 274

Table 1. Related Documents.......................................................................................................................................17 275 Table 2 – POTENTIAL System Threats .......................................................................................................................24 276 Table 3. Capability Deployment INCREMENTS.........................................................................................................26 277 Table 4. AT21 INCREMENT 1 Key Performance Parameters Summary...................................................................28 278 Table 5. INCREMENT 1 System Attributes .................................................................................................................35 279 Table 6. INCREMENT 1 TECHNICAL REQUIREMENTS .........................................................................................38 280 Table 7. INCREMENT 1 System Performance Parameters (Summary) ......................................................................40 281 Table 8. AT21 Additional Increment 1 Attributes.......................................................................................................41 282 Table 9. AT21 FOLLOW-ON (Increment 2 & 3) Attributes .......................................................................................43 283 Table 10. Supported ICDs/JCDs and Related ICDS/CDDs/CPDs.............................................................................50 284 Table 11. AT21 Algorithm reasoning requirements/source systems...........................................................................65 285 Table 12 – Potential Operational Threats...................................................................................................................71 286 Table 13. AT21 Program affordability ($ Million).....................................................................................................72 287 Table A-1. AV-1 Architecture Project identification ................................................................................................A-1 288 Table A-2. Operational node/NEED LINE reference............................................................................................. A-14 289 Table A-3a. AT21 Operational Activities to System Functions Traceability Matrix (SV-5).................................... A-47 290 Table A-3b. AT21 Joint Deployment/Distribution Architecture – UJTL/JMETL – Master Capability List – JL 291 (D)/JIC – Capability Gap Crosswalk ...................................................................................................................... A-51 292 Table A-4. AT21 Technical Standards Profile (TV-1) ........................................................................................... A-124 293 Table A-5. MA ICD KPP / IER Crosswalk ............................................................................................................ A-130 294 Table A-6 CDD Net Ready-Key Performance Parameter Statement .................................................................... A-130 295 Table A-7 AT21 KIP Declaration table ................................................................................................................. A-130 296 Table F-1 AT21 and SOEDE REQUIREMENTS CORRELATION MATRIX ............................................................F-3 297

FINAL REVISION – 21 Feb 07 3/6/2007 x

Points of Contact 298

Name Title Office Phone Email

Mr. Dean Peebels

Program Manager

TCAQ DSN 576-4300 Dean.Peebels@ustranscom.mil

Ms. Roni McDaniels

Deputy Program Manager

TCAQ DSN 576-4300 Roni.McDaniels@ustranscom.mil

Mr. Gregory Hoebing

Technical Manager

TCJ6-PS DSN 779-5079 Gregory.Hoebing@ustranscom.mil

LTC Darrell Gregg

Functional Manager

TCJ3-OI DSN 779-1849 Darrell.Gregg@ustranscom.mil

FINAL REVISION – 21 Feb 07 3/6/2007 1

1. Capability Discussion 299

1.1 Agile Transportation for the 21st Century (AT21) Advanced Concept Technology 300 Demonstration (ACTD) and Military Utility Assessment (MUA) – November 2004-March 301 2005 302

a. USTRANSCOM and the Defense Information Systems Agency (DISA), working 303 in concert with Joint Vision 2020, developed the AT21 ACTD as a solution set 304 that employs best-of-breed commercial business processes and COTS products 305 that have been fully demonstrated under real-world use cases for distribution 306 management and execution. The FW-II concept transformation enabling 307 capabilities demonstrated in the AT21 MUA embrace the key aspects of capacity, 308 control, and reliability as addressed in the Joint Logistics (Distribution) Joint 309 Integrating Concept (JIC)4 and support or demonstrate the potential to support the 310 three essential Joint Deployment and Distribution Enterprise (JDDE5) tasks: 311

(1) Move the joint force 313

(2) Sustain the joint force; and 314

(3) Operate in the JDDE 315

b. To meet combatant command distribution and deployment requirements 317

USTRANSCOM must move beyond nonspecific coordination among staffs to 318 full, action-oriented collaboration for joint and combined distribution planning, 319 exercises, training, and education. USTRANSCOM must become more actively 320 involved throughout the adaptive planning process6 and proactively build 321 collaborative partnerships to better anticipate the needs of the combatant 322 commands and fulfill those needs with time-sensitive execution options that assist 323 combatant commands in the development of more operationally and logistically 324 supportable plans. As a combatant command, USTRANSCOM has the 325 responsibility to fulfill the operational deployment and distribution requirements 326

4 Focused Logistics is the ability to provide the joint force the right personnel, equipment, supplies, and support in the right place, at the right time, and in the right quantities, across the full range of military operations. This will be made possible through a real-time, net-enabled information system providing accurate, actionable visibility as part of an integrated operational picture, effectively linking the operator and logistician across joint forces, Services, and support agencies. Through transformational innovations to processes, systems, and organizations, Focused Logistics will provide the joint warfighter with support for all functions. The FL JFC identifies these seven key joint logistics capability areas: Joint Deployment/Rapid Distribution, Agile Sustainment, Operational Engineering, Multinational Logistics, Force Health Protection, Information Fusion, and Joint Theater Logistics Management. The FL JFC identifies nine key joint logistics attributes and are described in detail in Appendix 1 of the DoD Logistics Transformation Strategy: Achieving Knowledge-Enabled Logistics, DTD 10 Dec 04.

5 Domain-wide visibility is the ability to see requirements, resources, and capabilities across the joint logistics domain. Three fundamental enablers frame the ability to achieve this imperative: (1) connectivity; (2) standard enterprise data architecture – enabling a common logistics operational picture; and (3) global focus – the view of joint logistics over the processes that deliver support to the Joint Force Commander (JFC).

6 Joint Staff guidance for Adaptive Planning addresses contingency planning and crisis action planning. AT21 will explore the capability to perform “what if” planning for real-world data and notional (non-real world) for adaptive planning. This is consistent with the traditional USTRANSCOM charter to evaluate the transportation feasibility of Combatant Commander Operation Plans (OPLAN) and alternative courses of action during the logistics and sustainment phases of plan development before the completed OPLAN was submitted for approval by the Chairman of the Joint Chiefs of Staff.

FINAL REVISION – 21 Feb 07 3/6/2007 2 of supported combatant commands while simultaneously exercising financial 327 stewardship of all transportation assets of the Military Departments (and 328 management support for Service-unique or theater-assigned transportation assets) 329 in accordance with DOD Directive 5158.4. This authority imbues the 330 Commander, USTRANSCOM with the authority to meet the needs of the 331 combatant commands efficiently, effectively, and with fiscal restraint. 332

1.1.1 AT21 inserts mature commercially available, integrated process control, 334 optimization, and collaboration tools into the framework of the DPO, significantly 335 improving peacetime and wartime distribution and deployment operations for the 336 combatant commands, Services, and other governmental entities. At a high level, 337

AT21: 338

a. Enhances business process control in the USTRANSCOM Deployment and 339 Distribution Center (DDOC) / Fusion Center; and 340

b. Obtains and transitions commercially available transportation management 341 system (TMS) technologies to support Defense distribution operations 342 worldwide. 343

1.1.2 By enhancing collaborative access to distribution and deployment-related 345 information at all operational levels, AT21 will optimize deployment and logistics 346 planning with improved efficiency of the distribution/deployment infrastructure. 347

a. Among the advantages to the warfighter are: 349

(1) Effective communication of operational lift requirements data 350

(2) Active, flexible lift schedules that accommodate dynamic re-tasking 351

(3) Data-driven distribution plans that provide visibility of flow statistics, 352 potential bottlenecks, contingency re-planning options, etc. 353

(4) Automated planning processes that accelerate the definition of movement 354 requirements 355

(5) Improved planning outcomes through early collaborative decision-making 356

(6) Avoidance of non-supportable courses of action 357

(7) Personnel and cargo visibility across the strategic deployment bridge; and 358

(8) Effective assimilation of Reception, Staging, Onward Movement and 359

Integration (RSO&I) operations within the Strategic Deployment and 360 Distribution Bridge. 361

1.2 USTRANSCOM Focus Warfighter (FW) (See Appendix G) 362

Following the documented successes of the AT21 ACTD and MUA, this CDD describes 363 the integration of process and technology transformation. AT21 aims to leverage 364 commercial best practices with minimal software code development. The primary focus 365 of FW II concept transformation is change management centered on the development 366 of efficient, standardized, repeatable processes. The secondary focus of FW II concept 367 transformation is integrating the appropriate supporting information technology tools. 368 The objective of AT21 tool integration aims at leveraging the integrated distribution 369 software suites that are available from the commercial sector that currently support the 370 full spectrum of supply chain management processes and activities. 371

FINAL REVISION – 21 Feb 07 3/6/2007 3

1.3 Process-Advancing-Technology (Prototype, Initial and Full Operational Capability, 372 IOC and FOC) 373

AT21 will follow an incremental development approach applying the lessons learned 374 from the AT21 ACTD and MUA as the initial concept increment upon which the 375 framework for transforming distribution and deployment operations will be based. As 376 technology advances, process improvements result; and as process efficiencies 377 develop, technology requirements will improve. The objective of phased releases is to 378 provide early capability to the combatant commands. As new capabilities are 379 incrementally added and tested, USTRANSCOM will deploy new capabilities to 380 operational activities encompassing the combatant command Joint Operations Areas 381 (JOAs) and USTRANSCOM enterprise. 382

a. AT21 will achieve Initial Operational Capability (IOC) when the threshold 384 capabilities for Increment 1 are satisfied and the IOC Key Performance 385 Parameters (KPPs) are achieved. 386

b. AT21 will achieve Full Operational Capability (FOC) when the threshold 388 capabilities identified for Increment 3 are satisfied and the FOC Key Performance 389 Parameters (KPPs) are achieved. Specific timelines are dependent on the 390 initiation of future acquisition efforts. 391

1.4 Joint Future Concepts/Mission Need/Capabilities Defined 392

a. The US National Military Strategy demands simultaneous deployment and 394 redeployment of units (force deployment/projection), replacement personnel, 395 and supplies (sustainment), across multiple theaters on a daily basis; and a 396 constant reprioritization/shifting in response to rapidly changing operational 397 demands. 398

Bottlenecks, ineffectiveness, and inefficiencies throughout the overall 400 distribution pipeline can be traced to multiple “owners” and the lack of 401 communication between these owners, coupled with systems 402 communication and interoperability failures. 403

b. Lack of visibility by customers and logisticians throughout the distribution 405 chain results in a lack of trust in the reliability of the overall system. 406

• This lack of trust creates delays, lowers expectations, inflates priorities, 408 decreases warfighter combat capability; and decreases flexibility and 409 effectiveness to meet global warfighter requirements. 410

c. These negative outcomes bog down the entire system – leading to duplication 412 of effort (multiple orders of like items) and contributing to unnecessary 413 shortfalls, decreased combat capability and decreased flexibility and 414 effectiveness to meet combatant command requirements. 415

FINAL REVISION – 21 Feb 07 3/6/2007 4

d. Figure 1 illustrates this situation as multiple funnels with different capacities 417 and different systems providing visibility over requirements generated into each 418 funnel. Each funnel represents the spectrum of operations from e.g., 419 contingency, exercise support, special airlift, and sustainment. 420

Contingency

Contingency

Contingency

Exercise

Exercise

Exercise

SAAM

SAAM

SAAM

Sustainment

Sustainment

Sustainment

COCOM

USTC

TCC

• Limitations

– No Single View of Total

Requirements

– Lack of Integration

– Non-optimized Distribution

Stove Piped Planning Loses Synergy and Visibility

Current Process

Figure 1. Stovepiped Planning Loses Synergy and Visibility 422

e. BRAC. USTRANSCOM is implementing the 2005 Department of Defense 424

(DOD) Base Realignment and Closure (BRAC) study recommendations.7 425 USTRANSCOM is consolidating their DDOC with certain planning, assessment 426 and monitoring functions of 18 AF TACC and SDDC into a combined Fusion 427 Center. 428

(1) The Fusion Center will bring improvements to a portion of the JDDE. The 430 goal is to create an effective, comprehensive, synchronized, and efficient 431 JDDE. Consolidating some DDOC, SDDC, and TACC processes will not 432 create a complete deployment and distribution enterprise. This will entail 433

7 The recommendations announced by DOD Secretary Rumsfeld on May 13, 2005 comprised, by the Commission’s count, 190 separate DOD recommendations that would produce as many as 837 distinct and identifiable recommended BRAC “close" or "realign" actions. The 837 distinct actions involved an additional 160 installations that would gain missions or resources due to the proposed closures and realignments. The 2005 BRAC recommendations exceeded the number considered by all prior BRAC Commissions combined. In addition to the unprecedented number, many DOD recommendations were extremely complex, proposing intertwining movements between and among numerous installations. Other DOD proposals consolidated apparently unrelated actions within the same recommendation.

FINAL REVISION – 21 Feb 07 3/6/2007 5 integrating many more national partners. The enterprise already exists; it 434 just does not function in a cohesive manner. 435

(2) AT21 will provide seamless visibility, while developing the processes and 437 algorithms to sense the operating environment and respond with 438 overwhelming speed and effectiveness to deliver and sustain combat power 439 globally for the warfighter 440

1.4.1 Focused Logistics 441

The Joint Logistics (Distribution) Joint Integrating Concept (JIC)8, posits that 442 logistics capabilities be capable of supporting future joint forces that…