ASNE Combat System Symposium PEO IWS Approach to Open Systems Architecture Mr. Bill Bray, Executive Director Program Executive Office, Integrated Warfare Systems 9 December 2014 DISTRIBUTION STATEMENT A: Approved for public release; Unlimited distribution. Evolving Joint Environments Operational Environment Humanitarian Assistance Short and Medium Range Ballistic Missiles Sub-Sonic Anti-Air & Anti-Surface Missiles Super-Sonic Anti-Air & Anti-Surface Missiles Advanced Super-Sonic Anti-Air & Anti-Ship Missiles Persistent ISR Simultaneous Raids Across Multiple Mission Areas Anti-Piracy Disaster Relief Mines Small Boat Attacks Torpedoes Complex Threats Employing Advanced Technology in Challenging Environments Intermediate Range Ballistic Missiles Cyber Warfare Fire Support Missions Anti-Ship Ballistic Missiles Stealth Under-Sea 2 Implementing Open Systems Architecture: Strategy, Interfaces and Open Standards Treat computing environment as a commodity – Select commercial mainstream COTS products that conform to well-established open system interface standards Commercial Products – Bundle specific COTS products for a given timeframe and revisit selections on a regular basis Applications Middleware Operating System Hardware Isolate applications from high rate-of-change COTS through selection of standard APIs – Upgrade H/W and S/W Independently and on different refresh intervals Transform application development from singleplatform development to multi-platform portfolio – Objective architecture defines key interfaces that support extensibility and reuse goals based on common data model – Eliminate redundant software development efforts Distribution Statement A: Approved for Public Release; Distribution is unlimited. “Build Once” Track Mgmt Command Sensor Weapon Vehicle & Mgmt Mgmt Control Control Display Middleware Operating System Hardware Evolution of Open Systems Architecture Distribution Statement A: Approved for Public Release; Distribution is unlimited. Combat System Objective Architecture Vehicles Platform Adaptation ExComm Combat System LAN Weapons Sensors Nav Systems Common Core Domains External Comms Display Services Vehicle Control Sensor Mgmt Combat Control Weapon Mgmt Track Mgmt Navigation Distribution Statement A: Approved for Public Release; Distribution is unlimited. Integrated Training Infrastructure Training Systems Common Computing & Infrastructure Vision Common Across Baseline Configurations Build Process CCI Ships Common Computing & Infrastructure SSDS “Common Components Across Multiple Combat Systems” Common Computing, Storage and Operating Environment Key Elements of Common Development: • Common Requirements • Single Specifications • Program Plans Aligned • Single Set of Processes & Metrics • Integrated Team Structure • Enterprise Products AEGIS, SSDS, Coast Guard, LCS Cross Program Representation Distribution Statement A: Approved for Public Release; Distribution is unlimited. AEGIS TI 16 Enabled Consolidation TI 12 TI 16 6 CPS Cabinets to be replace by 2 CCS; 2 ASAN Cabinets 4 TI 12 ACEG and IOPs Cabinets to be replace by 2 TI 16 ACEG/IO Cabinets 4 TI 12 DPC - 0 TI 16 DPC 0 No longer needed CEM role caption reduced cables AEGIS Example Today’s Technology Enables a 2:1 Reduction in Footprint With Remaining Margin for Processing and Storage Distribution Statement A: Approved for Public Release; Distribution is unlimited. TI 16 Common Building Blocks for Navy Combat Systems 3064 Edge Switch 3U Server 3132 Core Switch Storage 1U Server Remote Access Server DC Power Distro Power Control Device VMEbus Chassis Improved Capabilities – – – – – – • Reduced Qualification Effort Firewall Enclosure Monitor DVI Tray Encoder Tray • Fewer Unique Parts 40% Processing Capacity Increase 3X Computing Density 300% Increase Bandwidth 35% Increase in Storage (115 TB) Dual Network Redundancy Redundant Display Connection Tactical Server Chassis • Common Use Across Multiple Programs Sailor Benefits − − − − − − 60% Reduction in Maintenance Effort 20% Increase in Redundancy Reduced Mean Time To Repair Decreased Maintenance Training Imbedded Videos & Repair Procedures Closed Door troubleshooting Common Building Blocks is the Key Concept of TI-16 for Reduced Fleet Maintenance, Training and Life Cycle Costs Distribution Statement A: Approved for Public Release; Distribution is unlimited. AEGIS TI 16 State Of The Practice Improvements Processing Margin Cabinet Count With Fewer Cabinets, TI 16 Architecture Continues the Upward Progress on Processing Margin Distribution Statement A: Approved for Public Release; Distribution is unlimited. TI 16 Reverses Trends and Requires Less Power, Less Cooling, & Reduces Weight of the Computing Infrastructure SSDS Single Source Library Software Superset Supports All Platforms 2004 • • • • Open Standards-Based Designs Componentized Architecture Well-Defined Interfaces Open Systems Architecture (OSA) Foundation CVN 68 2014 “Fix it Once” 2003 Single Source Library FSEC Interop - 2005 OSA, ESSM/AEC - 2006 RAM BLK 2 - 2010 LPD 2005 Build Process Single Install Media Key Elements of Common Development: • Common Mission Capabilities • “Superset” of Specifications • Common Program Plans • Single Set of Processes & Metrics • Integrated Team Structure • Enterprise Products Core - 2003 2004 LHD 2012 LHA 2014 LSD LSD, CIWS 2012 Enables Technology/Capability Insertion Across Diverse Platforms AMIIP, FCLIP - 2013 DBR, Mode 5 (engagement only), ESSM with uplink, Product Line Software Components, SEWIP - 2014 Extensible Architecture Translates Into Reduced Development, Maintenance and Training Costs 2015 CVN 78 AEGIS Common Source Library (CSL) REUSE within Baseline configurations Build Process CSL Ships Baseline 8 BMD 4.0.1 ~3500K SLOC ~500K SLOC 97% Re-use Common Source Library Baseline 9 CG Modernization 97% Re-use ~6000K SLOC 97% Re-use Baseline 9 DDG Modernization ~8000K SLOC “Fix Once… Use Many Times” Key Elements of Common Development: • Common Mission Capabilities • Single Set of Specifications • Common Program Plans • Single Set of Processes & Metrics • Integrated Team Structure • Enterprise Products ~2000K SLOC 99% Re-use International Baseline 9 DDG New Construction ~8015K SLOC BMD 5.0 SPY-1D(V) Integration ~2000K SLOC ~15K SLOC 99% Re-use Baseline 9 AEGIS Ashore ~8080K SLOC AEGIS / MDA AB Cross Program Governance In Place to Coordinate Multiple Programs Using CSL Distribution Statement A: Approved for Public Release; Distribution is unlimited. BMD 5.0 BMD 5.0 ~2000K SLOC AEGIS Ashore Adaptation ~66K SLOC Commonality Across Combat Systems Commonality will address reduced training time, reduced O&S Cost and shorter availabilities Surface and USW Combat Systems • COTS and OSA based computing • Increase network-based Computing Equipment Capabilities • Common Source Library, Single Source Library and USW AxB • Common training and sailor qualification Standardize hardware and software components across surface Navy combat system elements Common Components • • • • • • • JTM- Joint Track Manager CDS- Common Display System CPS- Common Processing System BFTT- Battle Force Team Trainer CANES Gateway CIWS – SeaRAM – LPWS MH 60R Integration Common & Single Source-code Libraries Key Elements of Common Development: • Common Mission Capabilities • Single Set of Specifications • Common Program Plans • Single Set of Processes & Metrics • Integrated Team Structure • Enterprise Products Near-term Efforts • Navigation Wholeness: ECDIS-N, VMS • ASTAC: Common operator mode for MH-60R • Combat System LAN: External Comms, Display Services, Vehicle Control, Weapon Management ESSM • ESSM BLK II • SEWIP BLK II/III • Enterprise Air Surveillance Radar (EASR) “Configuration variance in surface ships is not sustainable and must be reduced to manageable levels” USFFC Letter 01 Aug 13 20140808 Combat System Commonality USD AT&L Honorable Frank Kendall Under Secretary of Defense for Acquisition, Technology and Logistics • BBP 1.0 and 2.0 focused on cost consciousness and professionalism as critical elements of our culture • BBP 3.0 is focused on achieving dominant capabilities through innovation and technical excellence • Our technological superiority is not assured, and in fact it is being challenged very effectively right now Distribution Statement A: Approved for Public Release; Distribution is unlimited. PEO IWS Systems Engineering Safe Firing Bearings 1. UNDERSTAND THE CURRENT DESIGN before you try to improve it. 2. FLOW REQUIREMENTS DOWN from the Force and Combat System levels to Sensors, C4I, and Weapons through a disciplined systems engineering process. 3. PACE THREATS in any new design. 4. CHANGE ONLY TO IMPROVE Combat Systems Cornerstones. 5. ENABLE BOTH A COMMON TACTICAL PICTURE AND INTEGRATED FIRE CONTROL in any new design. 6. CONSIDER COST as an equal factor with technical performance. 7. DOCUMENT SYSTEMS ENGINEERING DECISIONS made for performance, cost, and risk management. 8. PREDICT PERFORMANCE through the use of evolved endto-end models and simulations. Judiciously use LIVE FIRE TO VERIFY …not discover. 9. TEST REALISTICALLY AT EXISTING LAND-BASED TEST SITES before initiating shipboard testing. 10. BUILD A LITTLE, TEST A LITTLE, LEARN A LOT! Distribution Statement A: Approved for Public Release; Distribution is unlimited. PEO IWS Letter Dated Nov 6 2014 Summary • IWS Combat Systems Engineering using Open Systems Architecture has introduced opportunities to drive down costs and deliver combat capability to the war-fighter • BUT, Open Systems Architecture implementation is a long term effort that requires strong systems engineering discipline • Areas of focus going forward will be to: – Continue hardware footprint consolidation, keeping component obsolescence in mind – Identify effective strategies and opportunities for hardware/software component reuse – Mature systems engineering and business processes to support combat system development, reduce costs, and enable rapid deployment – Better align S&T transition plans to existing Programs of Records – Identify opportunities for continued Better Buying Power savings Enabling Open, Modular, Scalable, and Extensible Designs Distribution Statement A: Approved for Public Release; Distribution is unlimited.