Battle Command Migration Partnering Day Purpose

Battle Command Migration “Partnering Day”

Purpose • Present an initial overview of Battle Command (BC) migration beyond ABCS 6. 4 for near and mid-term – Define technical vision for future BC systems – Maintain relevance of fielded ABCS systems via key technology insertions – Maximize ROI by leveraging today’s capabilities into tomorrow • Establish a system of systems perspective: – Across all PEO C 3 T programs and Joint Interfaces – Technology improvements for interoperability and integration – Goal is life-cycle cost reduction Provide a System of Systems Path Forward 3

Army Battle Command Systems (ABCS) IMETS Integrated Meteorological Environmental Terrain System MCS Maneuver Control System ABCS Information Server ASAS All-Source Analysis System FBCB 2 Force XXI Battle Command - Brigade and Below GCCS-A Global Command Control System - Army DTSS Digital Topographic Support System JTF HQS BCS 3 TAIS Tactical Airspace Integration System Battle Command Sustainment Support System AMDWS Air and Missile Defense Workstation AIS Tactical Operation Centers A FAMILY OF SYSTEMS AFATDS Advanced Field Artillery Tactical Data System 4

Developing the ABCS 6. 4 Solution Warfighter Perspective & User Feedback 69 “Good Enough” Operational Requirements TSM & PM technical feasibility review 866 Technical Supporting Reqts derived & prioritized Constrained by OIF Driven Schedules ABCS 6. 4 software delivery to system test in April ‘ 04 Field ABCS 6. 4 across force within 48 months… 5

Current ABCS Product-Centric System Implementation 6

What Have We Learned? • Disparate data formats • Interoperability • Utilization of Bandwidth • Collaboration • Difficult to configure • Too many systems to train • Stovepipe Design – Different user interface for each system – Many servers providing similar functionality – More expensive to maintain – Training impacts Must leverage current capability to address these issues as ABCS evolves toward JC 2 and FCS. 7

What Happened since Good Enough? JTCW C 2 PC CPo. F ABCS “Good Enough” FBCB 2 JC 2 GCCS-A GCCS-M JBC-P Joint Web COP DACT FCS WEEMC Various NCES Horizontal Fusion (18 th ABN & JBFSA) Need to incorporate initiatives into ABCS. Must maintain compatibility with ABCS 6. 4. 8

Path Forward Today Near-Term Future GCCS JC 2 XXX ABCS 6. 4 XX X FBCB 2 + ABCS JC 2 with technology insertions X FBCB 2 UA FCS BC JBC-P Migration Plan under development 9

Migration Plan Key Drivers and Goals Army at War Modularity Joint Migration Plan ABCS Sustainment Team produces requirements, architecture, and schedule Net. Centricity Goals • Lower lifecycle cost • Reduce Complexity • Smaller footprint • Common User Interface • Reduced training and cognitive burden • Fewer soldiers needed to run/maintain the System of Systems Technology Insertions 10

BC System Convergence Vision Cap Block 1 In-Svc 06 -09 GCCS-A C 2 PC MCS CPOF TAIS AFATDS AMDPCS BCS 3 ASAS-L IMETS Cap Block 2 In-Svc 08 -11 Cap Block 3 In-Svc 10 -13 Cap Block 4 In-Svc 12 -15 Cap Block 6 JC 2 v 5 In-Svc 14 -17 In-Svc 16 -19 JC 2 v 1 JTCW JC 2 v 2 TAIS AFATDS AMDPCS BCS 3 ASAS-L or DCGS-A JC 2 v 3 JC 2 v 4 AFATDS AMDPCS BCS 3 DCGS-A (ISR comp. ) DTSS FBCB 2 DTSS JBC-P ISYSCON or WIN-T DCGS-A (ISR comp. ) AIS PASS B 1, IDM-T TOC Srvr PASS B 2, IDM-T (C 2 IEDM) FCS Sp 1 eval (ISR comp. ) J-GES JBC-P ISYSCONv 4 or WIN-T TOC Srvr PASS B 3, IDM-T (JC 3 IEDM) FCS Sp 1 FCS BC (Sp 4) DCGS-A (ISR comp. ) J-GES JBC-P WIN-T TOC Srvr PASS B 4, IDM-T (JBCIEDMv 1) FCS Sp 2 JBC-P WIN-T TOC Srvr WIN-T PASS B 5, IDM-T (JBCIEDMv 2) TOC Srvr PASS B 5, IDM-T (JBCIEDMv 3) FCS Sp 3 ABCS 6. 4 Transition A Transition B Transition C Transition D Transition E 11

Layered Approach to BC Software Architecture OSI Layers TCP/IP Layers User-Centric Design, Common Role-based User Interface Application Presentation Application Session Transport Network Data Link Physical C 2 Layers (HCI) Mapping/Overlays, Planning, Logistics, Airspace Mgmt & Deconfliction, Attack Analysis, Weapons Management, Target/Effects Queuing Messaging, Collaboration, Discovery, IA, Data Dissemination, Comms Network Management, QOS, Real-time Services Network Access Presentation Services LAN, Hardware (including servers) Routers, Hubs, Switches, Routing Protocols Battle Command Services Network Infrastructure Services Reduce cognitive burden by automating Battle Command Network Infrastructure Services. 12

BC Path Forward Near-Term Thrusts • Consolidation Of Servers/Services – Reduce Server Duplication – Centralize Servers/Service • “C 2 Bridge To The Future” – Expose ABCS Capabilities As Services – Leverage Middleware Services Compliant with NCES – Positions BC Server For Transition To JC 2 And FCS Spirals • Common Presentation Services – Leverage CPOF HCI “Goodness” – Role-Based User-Centric Design 13

Cleaning Up Product-Centric Issues Current Near Term • Complex Drives the need for*: • Duplicative Unique Stovepipes • Consistent Acquisition Strategy & Management Practices • Heavy Training Burden • Product-Centric Systems Engineering and Acquisition • Unified Systems Engineering and Integration • Common Architecture, Software and Hardware Solutions • Usability Strategy and Solutions 14

Server Consolidation 15

Application Consolidation on JTCW Framework GCCS-A BCS 3 EIS app on/injecto r Application/injector CPOF n/injecto tio Applica Tactical r JTCW BC Server ctor /inje ation c Appli MCS j n/in tio lica jec t tio or ca li pp in n/ in je A io n/ AFATDS je ct at ic pl • Common Role-based User Interface pl ica tio n/ in Ap AMDWS unique Common JTCW Client or ct AFATDS unique technical fire control Tactical or ect p Ap ISYSCON Strategic JC 2 Applicati BCS 3 or Strategic Ap AD mgmt C-RAM AMDWS TAIS • Infrastructure and Application Service Consolidation TAIS unique Airspace Mgmt • Common Hardware, Software, and Architecture TAIS AMPS unique functions AMPS Platform FBCB 2 TIMS JBC-P 16

What is CPOF? $62 M being Invested by DARPA Since 1998 CPOF Servers CPOF Workstation • An executive level decision support system that provides situational awareness and collaborative tools to support decision making, planning, rehearsal and execution management. • Designed to allow operators to interactively collaborate, and share workspaces and plans. May 04 MOA Between Army and DARPA CPOF Network Fielded to 1 st CAV and 3 ID "We do virtually every rehearsal using the CPOF tool. " MG Peter Chiarelli PM GC C 2 Actively Working Transition To Support Apr 06 Handoff 17

Objective ABCS Service-Based Framework 18

Where We’re Headed • Single Authority for Battle Command Systems Engineering • Single Army/Marine Corps Land/Littoral C 2 Solution • Maximizing commonality of architecture and services • Taking advantage of communications and network infrastructure • Incorporation of usability engineering in a common presentation layer design Translating BC Vision into a Viable System Architecture Leveraging ABCS 6. 4 Capabilities 19