Battle Command Collapse and M&S April 8 2011 Ted Troccola PD Common Software, PM BC Contractor (Viecore FSD Inc.) 1
Topics for Discussion • Background • BC Collapse Strategy – Operational – Technical – Programmatic • Simulation in Battle Command 2
Background 3
PM Battle Command Value To The Army • Battle Command Products are Successfully Supporting Army, Joint, and Coalition Operations Worldwide • PM BC Products Support Small Unit Tactical Operations through COCOM Strategic C2 • PM BC Delivers Three Key Capabilities that are Critical to Force Employment Success – Applications – Information Services Infrastructure (primarily BCCS & GCCS) – Worldwide support structure • PM BC Is the Army’s Primary Organization Engaging NATO to support Unified Coalition C2 in OEF • PM BC Achieves Success by implementing a Disciplined S/W Delivery Process that Rapidly Delivers Capability to Warfighters Reinforcing Battle Command Reinforces Success 4
Current Army Battle Command Capability TBC ¡(Tac9cal ¡Ba;le ¡Command ¡) ¡ ¡ CPOF, ¡BCCS, ¡Joint ¡Convergence ¡ GCCS-‑A/NECC ¡ EAC ¡C2 ¡ Maneuver ¡ Shared ¡SA ¡ Ba;le ¡Command ¡ Net-‑Ready ¡ Common ¡Services ¡ MANUEVER ¡ Interoperability ¡ Automa7c ¡Database ¡Replica7on ¡ Display ¡and ¡disseminate ¡COP ¡ Disseminate ¡Orders ¡ NBC ¡ Blue ¡Force/SA ¡ FBCB2/JBC-‑P ¡ Tac7cal ¡Collabora7on ¡ Interoperability ¡between ¡ ¡ Tac7cal ¡and ¡Theater ¡levels ¡ PLI/SA ¡ ENGINEER ¡ Chem-‑Bio ¡Rad-‑Nuc ¡(CBRN) ¡ MEDEVAC ¡ Orders ¡ FIRE ¡SUPPORT ¡ AFATDS ¡ JADOCS ¡ Fire ¡Support ¡ AIR ¡DEFENSE ¡ AMDWS ¡ Air ¡Defense ¡ AIR ¡PICTURE ¡ Air ¡Defense ¡to ¡Maneuver ¡Units ¡ Synchronized ¡Fires, ¡Effects, ¡& ¡Maneuver ¡ Posi7ve ¡AircraF ¡ID ¡ Execute ¡Responsive ¡Fires ¡ Weapon ¡Coverage ¡ Target ¡ ¡Management ¡ LOGISTICS ¡ Forward ¡Observer ¡Handhelds ¡ Radar/Observer ¡Loca7ons ¡ Logis7cs ¡ BCS3 ¡ TAIS ¡ Airspace ¡ Joint ¡Automated ¡Air ¡Space ¡ ¡Combat ¡Power ¡ Control ¡with ¡the ¡JFACC ¡ ¡In-‑transit ¡Visibility ¡ ¡ Air ¡Support ¡Request ¡ 10+ Systems = 10+ Individual sets of Hardware, 5 Software, Development, Test, Logistics… 5
Pre-Collapse Inefficiencies… Some Examples CX-I Data Tagging Client Side IED Symbology Change System Time Cost System 1 - $- • Oct 08 – Received 3 Star Note requiring all BC systems incorporate 4 new IED System 2 65 days $80K symbols System 3 60 days $50K • 21 Systems across 4 PEOs needed to change System 4 90 days $350K - 21 different implementation schedules System 5 60 days $95K - 21 different contracts modified - 21 different CONOPS/opinions System 6 60 days $100K • 9 Months to get consensus on implementation System 7 14 days $10K details System 8 - - • Execution of changes ranged anywhere from System 9 75 days $172K 1 week at no cost to 6 months at $250K Total (PdM) 90 days $857K • Quarterly releases approved in Jul 09 SoS Test 10 days $0 Total PM BC 100 days $857K CX-I Banner Baseline Change System A System B System C System D System E System F System G System H Time FSR 35 days FSR 5 days FSR - FSR 1.5 Months Cost $0 $75K $0 $7K $0 - $0 $132K 6
BC Collapse Strategy 7
BC “Collapse” Strategy 2009 2013 2015+ 2011 BFA GNEC Services GNEC BFA Services Enterprise WIN-T WIN-T Services Infrastructure Network Information Network GCCS-A/JC2C GCCS JC2C GCCS BCS3 BCS3 BCS3 BC Infr BC Infr BCCS BCCS Collaboration Collaboration CoMotion CoMotion DDS/MIP DDS/MIP PASS DDS/MIP Enterprise Enterprise Enterprise Enterprise Network Network BC Workstation “v0.5” BC Workstation“v1.0” BC Workstation “v2.0” Mvr Air Air Mvr Mvr Air CPOF BC BC BC BC BC BC Workstation Workstation Workstation Workstation Workstation ` Workstation Log Fires Log Fires Fires Log CPOF BC BC BC BC BC BC Workstation Workstation Workstation Workstation Workstation Workstation Collaborative Environment BC Environment (Based on CPOF/CoMotion) (Standard, Open Framework) Others MCS BC Applications Workstation GCCS-A BC Environment GCCS-A JADOCS JADOCS Coalition Coalition AMDWS AMDWS AFATDS AFATDS AFATDS Others Others Others Coalition BCS3 AMDWS BCS3 Others TAIS Web Web Web Services Services Services Environment Environment Environment 8 Version 5.1
PM BC Strategic Intent • Shift from a Battle Command family of uniquely distinct applications with unique data storing and sharing mechanisms and collapse these systems towards a consolidated Battle Command product line • Attributes of the consolidated approach – Significantly enhanced commander and staff ability to effectively conduct collaborative mission planning and execution across a range of operations and the spectrum of conflict – A singular battle command product line with a common government owned and managed architecture sharable by all – A unified approach to data handling and infrastructure procurement – Focus warfighting function development of subordinate PM’s on warfighting functions rather than draining resources on common tasks 9
PM BC Strategic Intent - Operational Extend and Significantly Enhance Staff Collaboration while Reducing the Complexity of Operations and Sustainment • Centrally stored Services & Data to enable Flexible, Rapid Deployment • Consolidated infrastructure; reduced burden on end users & FSRs • Extended and Enhanced Common Collaborative Environment • Widely available (limited) Collaboration and Shared Services Driven by a Set of Operational User Stories 10
PM BC Strategic Intent - Technical Shift from a family of uniquely distinct applications with unique data storing and sharing mechanisms and collapse these systems towards a consolidated software product line • Physical Consolidation • Services Consolidation - Tactical - Enterprise - Network • Enterprise Data Architecture - Standard Data Sharing (DDS) - Collaborative Data Environment (CoMotion) • Thick Client Consolidation • Common Collaborative Environment • Common ‘Thin Client’ Environment • Web Services (leveraging the Services Infrastructure above) 11
Executing Technical Intent – Status (1) Decisions Made/Course Set - • BC Collapse Architecture – Architecture has been base-lined and is being refined through a series of Design Reviews • Information Services Infrastructure - – Battle Command Common Services (BCCS) will continue to serve as BC’s single, unifying physical tactical infrastructure server – Data Dissemination Service (DDS) is being tested and certified as part of SWB11-12; will be the standard, default mechanism for data management and dissemination • Common BC ‘Thick Client’ Workstation – – Set of User Stories were delivered in Oct 10 – Initial architecture and framework is based on CPOF/CoMotion; Oct 11 delivery based on 3PDK v2.0 – All Oct 11 and beyond Collapse (and non-Collapse workstations) will be based off of the same Army Gold Master (AGM), Common Client Install (CCI), Security Configuration 12
PM BC Strategic Intent - Programmatic Shift from a family of uniquely distinct applications with unique data storing and sharing mechanisms and collapse these systems towards a consolidated software product line • One standard BC Infrastructure • Ability to compete enhancements to the infrastructure and standard clients (‘Thick’ & ‘Thin’) • One standard BC Thick Client/ Workstation • Ability to compete for new apps/ services built on the common infr/clients • One standard BC Thin Client Environment 13
The iPhone Analogy… …from a business model perspective Maneuver/ Logistics Planning Battle Command is standardizing on a common server and client(s) with a standard set of enterprise capabilities (data, collaboration, mapping, etc) and BC services… Air Fires …That will be developed, integrated, tested, accredited, and approved once per major release…and ultimately purchased, fielded, and supported centrally “Starter Kit” 14
Recommend
More recommend
