Defense Daily Open Architecture Summit 2014 PEO IWS Open Architecture Implementation

Transcription

1 Defense Daily Open Architecture Summit 2014 PEO IWS Open Architecture Implementation Mr. Bill Bray, Executive Director Program Executive Office, Integrated Warfare Systems November 4, 2014 DISTRIBUTION STATEMENT A: Approved for public release; Unlimited distribution.

2 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

3 Implementing Open 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 Bundle specific COTS products for a given 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 Commercial Products 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 Build Once Operating System Track Mgmt Display Applications Middleware Hardware Command & Control Sensor Mgmt Middleware Operating System Hardware Weapon Mgmt Vehicle Control

4 Evolution of Open Architecture

5 Combat System Objective Architecture ExComm Vehicles Sensors Combat System LAN Common Core Domains Platform Adaptation Weapons External Comms Sensor Mgmt Display Services Combat Control Vehicle Control Weapon Mgmt Nav Systems Track Mgmt Navigation Integrated Training Infrastructure Training Systems

6 Common Computing & Infrastructure Vision Common Across Baseline configurations Build Process CCI Ships Common Computing & Infrastructure Common Components Across Multiple Combat Systems SSDS 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

7 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

8 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 TI 16 Reverses Trends and Requires Less Power, Less Cooling, & Reduces Weight of the Computing Infrastructure

9 AEGIS Common Source Library (CSL) REUSE within Baseline configurations Build Process CSL Ships Baseline 8 ~3500K SLOC 97% Re use BMD ~500K SLOC Common Source Library Baseline 9 CG Modernization ~6000K SLOC 97% Re use 97% Re use Baseline 9 DDG Modernization ~8000K SLOC BMD 5.0 ~2000K 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 International 99% Re use Baseline 9 DDG New Construction ~8015K SLOC 99% Re use Baseline 9 AEGIS Ashore ~8080K SLOC BMD 5.0 ~2000K SLOC BMD 5.0 ~2000K SLOC SPY 1D(V) Integration ~15K SLOC AEGIS Ashore Adaptation ~66K SLOC AEGIS / MDA AB Cross Program Governance In Place to Coordinate Multiple Programs Using CSL

10 SSDS Single Source Library Software Superset Supports All Platforms Open Standards Based Designs Componentized Architecture Well Defined Interfaces Open Architecture (OA) Foundation CVN 68 Fix it Once 2004 LPD 2003 Core FSEC Interop OA, ESSM/AEC RAM BLK LSD, CIWS 2012 AMIIP, FCLIP Single Source Library DBR, Mode 5 (engagement only), ESSM with uplink, Product Line Software Components, SEWIP Build Process Key Elements of Common Development: Common Mission Capabilities Superset of Specifications Common Program Plans Single Set of Processes & Metrics Integrated Team Structure Enterprise Products Enables Technology/Capability Insertion Across Diverse Platforms Single Install Media LHD LHA LSD CVN 78 Extensible Architecture Translates Into Reduced Development, Maintenance and Training Costs

11 Commonality Across Combat Systems Commonality will address reduced training time, reduced O&S Cost and shorter availabilities Surface and USW Combat Systems Common Components COTS and OA 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 & 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 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 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 Combat System Commonality

12 Better Buying Power 3.0 Achieve Dominant Capabilities While Controlling Life Cycle Costs Strengthen should cost as an important tool for cost management Build stronger partnerships between acquisition, requirements, and intelligence communities Anticipate and plan for responsive and emerging threats Institutionalize stronger DoD level long range (R&D) planning Incentivize Productivity in Industry and Government Align profitability more tightly with Department goals Employ appropriate contract types, but increase use of incentive type contracts Improve the return on investment in DoD laboratories Increase productivity of industry IR&D and CR&D Incentivize Innovation in Industry and Government Increase the use of prototyping and experimentation. Emphasize technology insertion and refresh in program planning Use Modular Open Systems Architecture to stimulate innovation Increase the return on Small Business Innovation Research (SBIR) Eliminate Unproductive Processes and Bureaucracy Promote Effective Competition Improve Tradecraft in the Acquisition of Services Increase small business participation Strengthen contract management Improve Requirements definition Improve the Professionalism of the Total Acquisition Workforce

13 Summary IWS has been proactive in implementing Open Architecture precepts and concepts to the Surface Navy Open Architecture implementation has introduced opportunities to drive down costs and be more effective in the acquisition and deployment of combat capability BUT, Open Architecture implementation is a long term effort with much left to accomplish with a foundation in strong systems engineering discipline Our focus going forward will be to: Transition S&T into Programs of Records more effectively Continue hardware footprint consolidation Identify efficient and effective strategies and opportunities for software, component reuse Mature systems engineering and business processes to support combat system development, reduce costs, and enable rapid deployment Identify opportunities for continued Better Buying Power savings

14 BACK-UP SLIDES

15 USD AT&L 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 Honorable Frank Kendall Under Secretary of Defense for Acquisition, Technology and Logistics Our technological superiority is not assured, and in fact it is being challenged very effectively right now

16 Rising Costs Bring Focus on Total Ownership Costs Total ownership costs Manning Training Mission Mission effectiveness Logistics Interoperability Capability Systems Engineering Focus Open System Architecture Standards Gov t Data Rights Systems effectiveness Testing Modeling & simulation Construction System/Configuration Item performance Total Ownership Costs (TOC) is a focus of Systems Engineering Source: A.W. Meeks, Naval Open Architecture Avoiding Cost Growth through Open System Architecture, 22 April 2009