Defense Daily Open Architecture Summit 2014 Defense Daily Open Architecture Summit 2014 “PEO IWS Open Architecture Implementation” “PEO IWS Open Architecture Implementation” Mr. Bill Bray, Executive Director Mr. Bill Bray, Executive Director Program Executive Office, Integrated Warfare Systems Program Executive Office, Integrated Warfare Systems November 4, 2014 November 4, 2014 DISTRIBUTION STATEMENT A: Approved for public release; Unlimited distribution.
Evolving Joint Environments Operational Environment Complex Threats Employing Advanced Technology Short and Medium Range Humanitarian in Challenging Environments Ballistic Missiles Persistent Assistance ISR Simultaneous Sub-Sonic Raids Across Anti-Air & Intermediate Range Multiple Mission Areas Anti-Surface Missiles Ballistic Missiles Small Boat Cyber Anti-Piracy Fire Support Super-Sonic Attacks Warfare Missions Anti-Air & Anti-Surface Missiles Disaster Torpedoes Relief Anti-Ship Ballistic Missiles Advanced Stealth Super-Sonic Under-Sea Mines Anti-Air & Anti-Ship Missiles 2
Implementing Open Architecture: Strategy, Interfaces and Open Standards Treat computing environment as a commodity Applications – Select commercial mainstream COTS products that conform to well-established open system interface Middleware standards Commercial Operating System Products – Bundle specific COTS products for a given Hardware timeframe and revisit selections on a regular basis 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 Track “Build Mgmt Command Sensor Weapon Vehicle Transform application development from single- Once” & Mgmt Mgmt Control Control Display platform development to multi-platform portfolio Middleware – Objective architecture defines key interfaces that support extensibility and reuse goals based on common data model Operating System – Eliminate redundant software development efforts Hardware Distribution Statement A: Approved for Public Release; Distribution is unlimited.
Evolution of Open Architecture Distribution Statement A: Approved for Public Release; Distribution is unlimited.
Combat System Objective Architecture Vehicles ExComm Platform Adaptation Combat System LAN Weapons Sensors Common Core Domains External Display Vehicle Comms Services Control Sensor Combat Weapon Mgmt Control Mgmt Track Integrated Mgmt Training Nav Systems Navigation Infrastructure Training Systems Distribution Statement A: Approved for Public Release; Distribution is unlimited.
Common Computing & Infrastructure Vision Common Across Baseline configurations CCI Ships CCI Ships Build Process Build Process Common Computing & Common Infrastructure Computing, SSDS Storage and Operating Environment “Common Components Across Multiple Combat Systems” 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 0 4 TI 12 DPC ‐ 0 TI 16 DPC 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.
AEGIS TI 16 State Of The Practice Improvements Processing Margin Cabinet Count TI 16 Reverses Trends and Requires Less With Fewer Cabinets, TI 16 Architecture Power, Less Cooling, & Reduces Weight of Continues the Upward Progress on the Computing Infrastructure Processing Margin Distribution Statement A: Approved for Public Release; Distribution is unlimited.
AEGIS Common Source Library (CSL) REUSE within Baseline configurations Build Process CSL Ships CSL Ships Build Process Baseline 8 BMD 4.0.1 ~3500K SLOC ~500K SLOC 97% Re ‐ use Baseline 9 Common Source CG Modernization 97% Re ‐ use Library ~6000K SLOC 97% Re ‐ use Baseline 9 BMD 5.0 DDG Modernization ~2000K SLOC ~8000K SLOC 99% Re ‐ use “Fix Once… SPY ‐ 1D(V) Baseline 9 Use Many Times” BMD 5.0 Integration International DDG New Construction ~2000K SLOC ~15K SLOC ~8015K SLOC Key Elements of Common Development: • Common Mission Capabilities 99% Re ‐ use • Single Set of Specifications • Common Program Plans AEGIS Baseline 9 Ashore BMD 5.0 • Single Set of Processes & Metrics AEGIS Ashore Adaptation • Integrated Team Structure ~2000K SLOC ~66K SLOC ~8080K SLOC • Enterprise Products AEGIS / MDA AB Cross Program Governance In Place to Coordinate Multiple Programs Using CSL Distribution Statement A: Approved for Public Release; Distribution is unlimited.
SSDS Single Source Library Software Superset Supports All Platforms 2004 • Open Standards ‐ Based Designs CVN 68 • Componentized Architecture • Well ‐ Defined Interfaces 2014 • Open Architecture (OA) Foundation 2004 LPD “Fix it Once” 2003 2005 Single Single LHD Build Source Install Proces s Media Library 2012 Key Elements of Common Development: Core - 2003 LHA • Common Mission Capabilities • “Superset” of Specifications FSEC Interop - 2005 • Common Program Plans 2014 OA, ESSM/AEC - 2006 • Single Set of Processes & Metrics LSD • Integrated Team Structure RAM BLK 2 - 2010 • Enterprise Products LSD, CIWS 2012 Enables Technology/Capability 2015 AMIIP, FCLIP - 2013 Insertion Across Diverse Platforms DBR, Mode 5 (engagement only), ESSM with uplink, CVN 78 Product Line Software Components, SEWIP - 2014 Extensible Architecture Translates Into Reduced Development, Maintenance and Training Costs Distribution Statement A: Approved for Public Release; Distribution is unlimited.
Commonality Across Combat Systems Commonality will address reduced training time, reduced O&S Cost and shorter availabilities Surface and USW Combat Systems Common Components • JTM- Joint Track Manager • COTS and OA based computing • CDS- Common Display System • Increase network-based Computing Equipment • CPS- Common Processing System Capabilities • BFTT- Battle Force Team Trainer • Common Source Library, Single Source Library and USW AxB • CANES Gateway • CIWS – SeaRAM – LPWS • Common training and sailor qualification • MH 60R Integration Standardize hardware and software components across surface Navy combat system elements Common & Single Source-code Libraries Near-term Efforts • Navigation Wholeness: ECDIS-N, VMS Key Elements of Common Development: • ASTAC: Common operator mode for MH-60R • Common Mission Capabilities • Combat System LAN: External Comms, Display • Single Set of Specifications Services, Vehicle Control, Weapon Management • Common Program Plans ESSM ESSM • Single Set of Processes & Metrics • ESSM BLK II • Integrated Team Structure • SEWIP BLK II/III • Enterprise Products • 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
Better Buying Power 3.0 • Achieve Dominant Capabilities Incentivize Innovation in Industry and • While Controlling Life Cycle Costs Government – Strengthen “should cost” as an Increase the use of prototyping and — important tool for cost management experimentation. – Build stronger partnerships between Emphasize technology insertion and refresh in — acquisition, requirements, and program planning intelligence communities Use Modular Open Systems Architecture to — – Anticipate and plan for responsive and stimulate innovation emerging threats Increase the return on Small Business — – Institutionalize stronger DoD level long Innovation Research (SBIR) range (R&D) planning Eliminate Unproductive Processes and • Bureaucracy • Incentivize Productivity in Industry Promote Effective Competition • and Government Improve Tradecraft in the Acquisition of • – Align profitability more tightly with Services Department goals – Employ appropriate contract types, but Increase small business participation — increase use of incentive type contracts Strengthen contract management — – Improve the return on investment in Improve Requirements definition — DoD laboratories Improve the Professionalism of the Total • – Increase productivity of industry IR&D Acquisition Workforce and CR&D Distribution Statement A: Approved for Public Release; Distribution is unlimited.
Recommend
More recommend
