Slide 1

Slide 2 Battle Command Migration Partnering Day Slide 3 3 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 todays capabilities into tomorrow Establish a system of systems perspective: Across all PEO C3T programs and Joint Interfaces Technology improvements for interoperability and integration Goal is life-cycle cost reduction Provide a System of Systems Path Forward Slide 4 4 Army Battle Command Systems (ABCS) Tactical Operation Centers GCCS-A Global Command and Control System - Army FBCB2 Force XXI Battle Command - Brigade and Below DTSS Digital Topographic Support System MCS Maneuver Control System BCS3 Battle Command Sustainment Support System AMDWS Air and Missile Defense Workstation ASAS All-Source Analysis System TAIS Tactical Airspace Integration System AFATDS Advanced Field Artillery Tactical Data System IMETS Integrated Meteorological Environmental Terrain System JTF HQS A FAMILY OF SYSTEMS AIS ABCS Information Server Slide 5 5 Developing the ABCS 6.4 Solution Warfighter Perspective & User Feedback Warfighter Perspective & User Feedback 69 Good Enough Operational Requirements 69 Good Enough Operational Requirements TSM & PM technical feasibility review TSM & PM technical feasibility review 866 Technical Supporting Reqts derived & prioritized ABCS 6.4 software delivery to system test in April 04 ABCS 6.4 software delivery to system test in April 04 Field ABCS 6.4 across force within 48 months Constrained by OIF Driven Schedules Slide 6 6 Current ABCS Product-Centric System Implementation Slide 7 7 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 JC2 and FCS. Slide 8 8 DACT C2PC GCCS-M JC2 What Happened since Good Enough? JTCW CPoF GCCS-A ABCS Good Enough Joint Web COP FCS WEEMC FBCB2 JBC-P Horizontal Fusion (18 th ABN & JBFSA) Various NCES Need to incorporate initiatives into ABCS. Must maintain compatibility with ABCS 6.4. Slide 9 9 Path Forward Today Future GCCS ABCS 6.4 ABCS 6.4 FBCB2 JC2 FCS BC JBC-P XXX XX X UA Near-Term FBCB2 X JC2 + ABCS with technology insertions Migration Plan under development Slide 10 10 Migration Plan Key Drivers and Goals Migration Plan ModularityArmy at War Joint ABCS Sustainment Technology Insertions NetCentricity Team produces requirements, architecture, and schedule 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 Slide 11 11 BC System Convergence Vision Slide 12 12 Layered Approach to BC Software Architecture Application Presentation Session Transport Network Data Link Physical OSI Layers TCP/IP LayersC2 Layers Application Transport Network Network Access Network Infrastructure Services Battle Command Services Presentation Services LAN, Hardware (including servers) Routers, Hubs, Switches, Routing Protocols Messaging, Collaboration, Discovery, IA, Data Dissemination, Comms Network Management, QOS, Real-time Services Mapping/Overlays, Planning, Logistics, Airspace Mgmt & Deconfliction, Attack Analysis, Weapons Management, Target/Effects Queuing User-Centric Design, Common Role-based User Interface Reduce cognitive burden by automating Battle Command and Network Infrastructure Services. (HCI) Slide 13 13 BC Path Forward Near-Term Thrusts Consolidation Of Servers/Services Reduce Server Duplication Centralize Servers/Service C2 Bridge To The Future Expose ABCS Capabilities As Services Leverage Middleware Services Compliant with NCES Positions BC Server For Transition To JC2 And FCS Spirals Common Presentation Services Leverage CPOF HCI Goodness Role-Based User-Centric Design Slide 14 14 Cleaning Up Product-Centric Issues Complex Duplicative Unique Stovepipes Heavy Training Burden Product-Centric Systems Engineering and Acquisition Drives the need for*: Consistent Acquisition Strategy & Management Practices Unified Systems Engineering and Integration Common Architecture, Software and Hardware Solutions Usability Strategy and Solutions CurrentNear Term Slide 15 15 Server Consolidation Slide 16 16 Application Consolidation on JTCW Framework GCCS-A FBCB2 JBC-P AMDWS TAIS AFATDS MCS BCS3 CPOF JTCW AFATDS unique technical fire control AMDWS unique AD mgmt C-RAM TAIS unique Airspace Mgmt Application/injector BCS3 EIS app JC2 BC Server TAIS ISYSCON AMPS AMPS unique functions Application/injector TIMS Common Role-based User Interface Common Hardware, Software, and Architecture Infrastructure and Application Service Consolidation Strategic Tactical Platform Strategic Tactical Platform Common JTCW Client Application/injector Slide 17 17 What is CPOF? 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. May04 MOA Between Army and DARPA CPOF Network Fielded to 1 st CAV and 3ID $62M being Invested by DARPA Since 1998 $62M being Invested by DARPA Since 1998 "We do virtually every rehearsal using the CPOF tool." MG Peter Chiarelli CPOF Servers CPOF Workstation PM GC C2 Actively Working Transition To Support Apr06 Handoff Slide 18 18 Objective ABCS Service-Based Framework Slide 19 19 Where Were Headed Single Authority for Battle Command Systems Engineering Single Army/Marine Corps Land/Littoral C2 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