Building C 4 ISR Capabilities in a Dynamic

Building C 4 ISR Capabilities in a Dynamic Environment ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP

MISSION ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP Explore innovative ways to improve Do. D system design and acquisition processes so that we can better transform advances in information technology into operational capabilities. 2

Context and Expectations ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • The workshop has been divided into three panels – Builing C 4 ISR Capabilities in a Dynamic Environment – Design and Development Risk Management – Lifecycle Accountability • Formulate Problem Statement • Identify Impediments, Constraints and Opportunities • Provide Recommendations for Incremental Improvements • Queue up issues for QDR • Identify venue for follow-up 3

Members ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP Al Grasso Alex Levis Stuart Starr Rich Ivanetich Iris Kameny Jude Franklin Bill Sieg John Mitchell Edwin B. Stear MITRE GMU MITRE IDA RAND Litton PRC USD(AT&L)IO JBC IDA 703 -883 -6138 703 -993 -1619 703 -883 -5494 703 -845 -6600 703 -393 -0411 703 -559 -1990 703 -413 -3143 757 -686 -7045 703 -845 -6676 ag@mitre. org aleis@gmu. edu starr@mitre. org rivan@ida. org kameny@rand. org franklin_jude@prc. com siegb@mail. etas. com mitchell@jbc. js. mil estear@ida. com 4

Proposed Concept of Operations ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Identify candidate major issues (building on a strawman set) • Discuss and rank order the major issues • For a selected set of high priority major issues, formulate preliminary – Findings – Recommendations • Formulate a process for follow-on activities; e. g. , – Identify relevant references – Clarify the nature of the problem – Identify additional organizations to be represented on the team – Identify organizations to visit – Establish a schedule for future meetings 5

Nature of the Problem ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • There are several factors that contribute to the “dynamic environment” in which future C 3 I systems-of-systems will be acquired – Threat • The New World Disorder is characterized by – Extreme uncertainty about future adversaries, areas of operation – The need to coordinate, interoperate with different organizations (e. g. , NGOs, law enforcement agencies) – Concepts of operations • There is a much greater emphasis being placed on joint operations • Politically, it is important to conduct operations in the context of ad hoc coalitions of the willing – Commercial information technology • Do. D use is increasing • This technology is characterized by an 18 month time scale 6

Acquiring Systems-of-Systems -Strawman Major Issues (1 of 3) ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Evolutionary Acquisition – Barriers to implementation; e. g. , • Reaction of Congress • Concerns of T&E Community • Existing Do. D policy, guidance – Tools to support implementation • CTSF experience (US Army) – Steps to facilitate assimilation of commercial products (with their 18 month characteristic time cycle) • Requirements-Acquisition-Operations Relationship – What is the appropriate relationship between the two processes? – How does one formally capture the requirements insights that emerge during an evolutionary acquisition? 7

Where Are We Now? ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP MAJCOMS Industry Labs Hurlburt (TIC) ESC (CUBE) Academia Field Ad hoc Joint Ops Field JBC/JED/USACOM CECOM (DIL) SPAWAR C 4 ISR-SIE Technical Integration. Development Ft. Hood CTSF Sea Based BL Field Force-Level Service Integration System Fielding Field DARPA 8

Acquiring Systems-of-Systems -Strawman Major Issues (2 of 3) ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Confederations of Allied/Coalition Systems-of-Systems – What steps can be taken to ensure that US and allied/coalition acquisitions are • Interoperable? • Mutually reinforcing? • Architectures – To what extent can families of architectures (e. g. , operational, system, technical) help us acquire systemsof-systems more effectively and efficiently? – What is the state-of-the-art in architecture development and application? • Simulation Based Acquisition – Applicability to C 3 I acquisitions? – Availability of supporting tools, data, knowledge 9

Scope of Interoperability: ABCS Exemplar ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP GCCS-A Interop. AIBS-army-96 FAISA-army-97 TARSTAT-army-97 -98 AMSAA-joint-96 APC-joint-96 ASAS-joint-97 ATCOM-joint-96 AWDS-joint-97 CASCOM-joint-96 CTAPS/TBMCS-joint-97 DAMO-ODR-joint-96 DES-joint-96 DLA/ICIS-joint-96 GCCS/GSORTS-joint-98 GCCS/GSRDI-joint-98 GCCS/JOPES-joint-98 IOC-joint-96 ISC-P-joint-96 JTAV-joint-97 LOGSA-joint-96 MCS-joint-96 PERSCOM-joint-96 RAMS-joint-96 REQVAL-joint-96 SAMAS-joint-96 TAV-joint-96 Legend: example: JMCIS-joint-98 System Interface Level: ALLIED ARMY JOINT Implementation Year (U= Unscheduled) MCS Interop. LFCS-army-97 CTAPS-joint-97 JMCIS-joint-98 JStars. GCS-joint-98 TCO-joint-98 AUSTACCS-allied-98 HEROS-allied-96 LFCCIS-allied-97 QIFS-allied-98 SIACCON-allied-98 SICF-allied-96 IMETS Interop. FAST-Joint. JSTARS CGS-joint. MITT-Joint- GCCS-A DTSS MCS FAAD C 2 IMETS CSSCS ASAS AFATDS FBCB 2 IMETS Interop. GPS-army. MMS-army. UAV-army. JSTARS CGS-joint. CSSCS Interop. GCCS/A-army-99 SAMS/2 -army-97 SARSS/1 -army-97 SARSS/2 A/D-army-98 SIDPERS/2. 75 -army-97 SIDPERS-3 -army-98 SPBS/R-army-97 TAMMIS-army-98 ULLS/S 4 -army-98 FAAD C 2 Interop. LLAPI-allied-95 GBS Radar-army-94 HIMAD-army-94 LSDIS Radar-army-97 TIBS-army-U AWACS-joint-93 Hawkeye-joint-93 FBCBS Interop. BCIS-army-U KIOWA-army-U LVRS-army-U M 1 A 2 SEP-army-U M 2 A 2 -army-U MICAD-U NBCRS-army-U Paladin-AFCS PLGR-army-97 Land. Warrior-army-U AFATDS Interop. ATHS-army-97 BCS-army-97 FDS-army-97 Firefinder--army-97 FIST DMD-army-97 FOCC-army-97 FOS-army-98 IDM-army-99 IFSAS-army-97 Ltac. Fire-army-97 MBC-army-97 MDS-army-97 MFCS-army-99 MMS-army-97 UAV/TS/00 -army-U AFATDS-joint-99 (MC) CTAPS/TBMCS-joint-98 IFSAS-joint-97 (MC) JStars/GCS-joint-97 Tac. Fire-01 -joint-U (MC) ADLER-allied-98 ATLAS-allied-98 BATES-allied-98 ASAS Interop. Adv. Quickfix-army-U AMS-army-00 ARL-army-U ATCAE-army-97 CTS/CTAPS-army-97 DAI-army-97 Enhan. Trackwolf-army-U EPDS-army-97 ETRAC-army-U ETUT-army-97 GBCS-army-U Guardrail-army-97 IEWCS-army-U IPF-army-97 MIES-army-97 MITT-army-97 NGIC-army-U NPIC-army-U NSA-army-97 SSP/S-army-97 TEAMMATE-army-97 TES-army-97 THMT-army-97 Traffic. Jam-army-97 Trailblazer-army-97 TRRIP-army-U UAV GCS-army-97 UAV MPCS-army-97 CARS/TRIGS-joint-97 IAC-joint-97 JMCIS-joint-97 JStars. CGS-joint-97 NIPS-joint-97 TBMCS-joint-U TCAC-joint-97 PASS-K-allied-U RAPIDE-allied-97

Preliminary Analysis of Joint C 4 ISR Interoperability & Integration Processes I & I Planning & Assessment & Validation Joint Elements of the Policy Constructs and Prescriptions Process Architectures Interoperability & Integration Di Ov Integrated Enabling Capabilities & Implementation Options Imple. ASD (C 3 I) DESIGN Prototyping r Method Joint mentation. SYSTEMS e Maturity Certifi. Assurance e r Assess- & Experi- cation Criteria & Tools Models c Equation s OP SYS TECH mentation t Processes Consortia -JROC/JWCA -MCEB IIP -CMS/ISB/ISS -JIIB -Do. DIIS Mgmt Board -CIO “Councils” Organizations -Joint Staff -OSD -DISA -CINCs -MILDEPs -Defense Agencies -DSC -JBC/Federated Labs -JEXP -JITC -JNTF -JITF -Intelink Mgmt Office Initiatives -C 4 ISR Architecture Framework -Do. DD/Do. DI 4630 -JTA -JIER -LISI -DII COE -SHADE -Do. DIIS SIMO -JWIDs/ACTDs i v e s i g h t Procedures. Applications. Infrastructure. Data Standards Process & Metrics ments Systems Status 7/15/98 Acquisition Life Cycle Development Evolutionary System Do. D-Wide & ACQUISITION WORKSHOP Profiles Improve. Requirements Procurement Systems & Performanc Interop MNSs Repository IERs e ORDs Measures Other ments

Acquiring Systems-of-Systems -Strawman Major Issues (3 of 3) ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Education & Training – How can we educate and train Program Managers on the processes that must be performed to acquire systems-of -systems? – How can we educate and train the operators who will man the systems-of-systems (particularly as CONOPS evolve to respond to the evolving system-of-systems)? 12

Selected References ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Annette Krygiel, “Behind the Wizard’s Curtain”, NDU and Do. D CCRP, July 1999 • Stuart Starr, “Modeling & Simulation to Support The Acquisition Process”, Chapter 9 of Military Modeling for Decision Making, MORS, 1997 • “Rapid Development”, Microsoft • “Institutionalizing the Good Idea: CTSF”, Grasso • “Spiral Development: Experience, Principles and Refinement, ” Barry Boehm 13

Problem Statement(s) ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Systems are not interoperable and they should be to act as a system-of-systems • Rapid insertion of evolving technology • Co-evolution of DOTLMP, requirements, capability, technology, value and cost • Incentive rewards in acquisition (risk mgmt deferred to other group) • Achieving effective (function/joint/coalition, secure, interoperable, evolveable, scaleable, . . . ) affordable C 4 ISR systems to accommodate: – – Diverse uncertain threats New and evolving ops concepts Inability to fully specify reqmts upfront Rapidly advancing technology 14

Problem Decomposed ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Achieving effective (function/joint/coalition, secure, robust, interoperable, evolveable, scaleable, . . . ) affordable C 4 ISR systems to accommodate: – Diverse uncertain threats – New and evolving ops concepts – Inability to fully specify reqmts upfront – Rapidly advancing technology • Acquisition process oriented toward weapons systems vice software/IT systems • Right Industry/Govt partnership • Dealing with Legacy as the least common denominator- legacy system migration • Architecture Framework contains no process description - needs implementation guidance • No process to evaluate and review architectures no sign off - how does it fit in acquisition process 15

Light Bulbs ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Robust systems (hardware, software and people) – Software error recovery – Robust testing - scale of test (LRIP too limited) Alpha and beta testing – Redundancy - divers solutions -h/w, s/w, people – Contingencies -h/w, s/w, people – Consumers Union for COTS – Red teaming • Architecture Framework in 5000 series – ASD C 3 I should explicitly examine how to execute spiral development within the relook of the Architecture Framework – Need champion • Support coalition interoperability experimentation 16

Light Bulbs ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Support establishment of a joint rapid acquisition program element - leverage success of current WRAP 17

Synthesis ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Cultural - joint/coalition mindset, incentives, leadership/champions • Organization - champions, streamline interop orgs - zero base • People - collective training - ops and acquisition • Vision/Policy - rationalize cross-service visions • Processes - partnerships w/o borders, spiral/helical development, architectural views & framework - how to? Synchronization events, portfolio mgmt • Resources - joint rapid acquisition PE, incentives • Tools/Experiments - coalition (in test bed), purple CTSF, Experimentation Best Practice • Products - Architectural Views (e. g. , security, error recovery) 18

Preliminary Recommendations ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Provide for “joint funding” resources to support joint/coalition activities - not a service take away • Fail fast - too tough • Implement CIO role as “Bully Pulpit” • Zero base interoperability organizations • Extend CTSF model for joint use - collective environment/training • Establish a joint rapid acquisition PE • Develop and disseminate Best Practices for Experimentation 19

Preliminary Recommendations ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • Rationalize cross service operational visions • ASD C 3 I should explicitly relook the Architecture Framework within a spiral development environment • C 3 I, A&T develop and cosign a policy paper on spiral/helical development and its relationship to new 5000 directive - emphasis on co-evolution and experimentation across DOTLMSP • Re-examine the Architecture Framework to ensure the inclusion of necessary view to include security and robustness/error recovery 20

Way Forward ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP 21

Backup Material ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP 22

Solution Mechanisms ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • • Experimentation Architectures Policy Organization 23

Problem/Solution Matrix ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP 24

Today’s Timeline ASD (C 3 I) SYSTEMS DESIGN & ACQUISITION WORKSHOP • 9: 00 - 9: 15 Reformulate Problem Statement • 9: 15 - 10: 00 Lessons Learned/Roadblocks/Constraints • 10: 00 - 10: 45 Light Bulbs • 10: 45 - 11: 30 Synthesis • 11: 30 - 11: 45 Revisit Problem Statement • 11: 45 - 12: 00 Way Forward 25