1 / 18

Battle Command Migration

Battle Command Migration. “Partnering Day” 15 November 05. Paul Manz Technical Director PM Ground Combat C2 Paul.Manz@us.army.mil. 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

margot
Download Presentation

Battle Command Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Battle Command Migration “Partnering Day” 15 November 05 Paul Manz Technical Director PM Ground Combat C2 Paul.Manz@us.army.mil

  2. 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 C3T 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 AIS ABCS Information Server FBCB2 Force XXI Battle Command - Brigade and Below ASAS All-Source Analysis System GCCS-A Global Command and Control System - Army DTSS Digital Topographic Support System JTF HQS BCS3 Battle CommandSustainment SupportSystem TAIS Tactical Airspace Integration System AFATDS Advanced Field Artillery Tactical Data System AMDWS Air and Missile Defense Workstation Tactical Operation Centers A FAMILY OF SYSTEMS

  4. Developing the ABCS 6.4 Solution Warfighter Perspective & User Feedback 69 “Good Enough” OperationalRequirements TSM & PM technical feasibility review 866 Technical Supporting Reqts derived & prioritized ABCS 6.4 software delivery to system test in April ‘04 Constrained by OIF Driven Schedules 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 JC2 and FCS.

  7. What Happened since Good Enough? ABCS“Good Enough” Joint WebCOP JTCW DACT C2PC JBC-P FBCB2 FCS CPoF WEEMC JC2 VariousNCES Horizontal Fusion (18th ABN & JBFSA) GCCS-A GCCS-M Need to incorporate initiatives into ABCS. Must maintain compatibility with ABCS 6.4.

  8. Path Forward Future Today Near-Term GCCS JC2 + ABCS with technology insertions XXX ABCS 6.4 JC2 XX UA X X FBCB2 FCS BC JBC-P FBCB2 Migration Plan under development

  9. Migration Plan Key Drivers and Goals Army at War Modularity • 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 Joint Migration Plan Team produces requirements, architecture, and schedule ABCS Sustainment NetCentricity Technology Insertions

  10. DTSS DTSS DTSS J-GES J-GES J-GES FCS Sp 3 FCS Sp 1eval FCS Sp 2 FCS Sp 1 Cap Block 1 In-Svc 06-09 Cap Block 2 In-Svc 08-11 Cap Block 3 In-Svc 10-13 Cap Block 4 In-Svc 12-15 Cap Block 5 In-Svc 14-17 Cap Block 6 In-Svc 16-19 GCCS-A JC2v1 C2PC JTCW MCS JC2v2 JC2v3 JC2v4 JC2v5 CPOF TAIS TAIS AFATDS AFATDS AFATDS AFATDS AFATDS AMDPCS AMDPCS AMDPCS AMDPCS AMDPCS FCS BC (Sp 4) BCS3 BCS3 BCS3 BCS3 BCS3 ASAS-L or ASAS-L DCGS-A (ISR comp.) DCGS-A (ISR comp.) DCGS-A (ISR comp.) DCGS-A (ISR comp.) IMETS FBCB2 JBC-P JBC-P JBC-P JBC-P JBC-P ISYSCON ISYSCON or ISYSCONv4 or WIN-T WIN-T WIN-T WIN-T WIN-T AIS PASS B1, IDM-T TOC Srvr PASS B2, IDM-T (C2IEDM) TOC Srvr PASS B3, IDM-T (JC3IEDM) TOC Srvr PASS B4, IDM-T (JBCIEDMv1) TOC Srvr PASS B5, IDM-T (JBCIEDMv2) TOC Srvr PASS B5, IDM-T (JBCIEDMv3) ABCS 6.4 Transition A Transition B Transition C Transition D Transition E BC System Convergence Vision

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

  12. BC Path ForwardNear-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

  13. Cleaning Up Product-Centric Issues Current Near Term • 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

  14. Server Consolidation

  15. TAIS TAIS Application Consolidation on JTCW Framework Strategic Strategic GCCS-A JC2 Application/injector BCS3 BCS3 EIS app Application/injector CPOF Application/injector Tactical Tactical JTCW BC Server Application/injector Common JTCW Client MCS Application/injector ISYSCON Application/injector AFATDS unique technical fire control Application/injector AFATDS • Common Role-based User Interface • Common Hardware, Software, and Architecture • Infrastructure and Application Service Consolidation Application/injector AMDWS unique AD mgmt C-RAM AMDWS TAIS unique Airspace Mgmt TAIS AMPS unique functions AMPS Platform Platform TIMS JBC-P FBCB2

  16. What is CPOF? $62M being Invested by DARPA Since 1998 • An executive level decision support system that provides situational awareness and collaborative tools tosupport decision making, planning, rehearsal and execution management. • Designed to allow operators to interactively collaborate, and share workspaces and plans. CPOF Servers CPOF Workstation CPOF Network Fielded to 1st CAV and 3ID May04 MOA Between Army and DARPA "We do virtually every rehearsal using the CPOF tool." MG Peter Chiarelli PM GC C2 Actively Working Transition To Support Apr06 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 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

More Related