Loading in 2 Seconds...
Loading in 2 Seconds...
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.
Evolving Joint Environments Operational Environment Complex Threats Employing Advanced Technology in Challenging Environments Short and Medium Range Ballistic Missiles Humanitarian Assistance Persistent ISR Simultaneous Raids Across Multiple Mission Areas Sub-Sonic Anti-Air & Anti-Surface Missiles Intermediate Range Ballistic Missiles Small Boat Attacks Cyber Warfare Anti-Piracy Fire Support Missions Super-Sonic Anti-Air & Anti-Surface Missiles DisasterRelief Torpedoes Anti-Ship Ballistic Missiles Advanced Super-Sonic Anti-Air & Anti-Ship Missiles Stealth Under-Sea Engage Long Range Ballistic Missiles Mines Rail Guns Advanced ASW Cyber Defense Over Land Defense Multi-Ship Resource Coordination Enhanced Shipboard Sensors (Radar + ES/EA) Capability Advancements Directed Energy ImprovedSelf-Defense Area Air Defense In Clutter Environments UAVIntegration Integrated Air and Missile Defense Integrated AAW & Situational Awareness High Data Rate Battle Group Networks
Track Mgmt Command & Control Sensor Mgmt WeaponMgmt VehicleControl Display 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 • Transform application development from single-platform 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 Applications Middleware Commercial Products Operating System Hardware “Build Once” Middleware Operating System Hardware
Combat System Objective Architecture Vehicles ExComm Platform Adaptation Combat System LAN Weapons Sensors Common Core Domains External Comms Display Services Vehicle Control Weapon Mgmt Sensor Mgmt Combat Control TrackMgmt Integrated Training Nav Systems Navigation Infrastructure Training Systems
Common Computing & Infrastructure VisionCommon Across Baseline configurations CCI Ships Build Process Common Computing, Storage and Operating Environment Common Computing & Infrastructure SSDS “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
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
AEGIS TI 16 State Of The Practice Improvements 115.2% Processing Margin 19 16 Cabinet Count 76.8% 11 44.8% 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
AEGIS Common Source Library (CSL) REUSE within Baseline configurations CSL Ships Build Process Baseline 8 ~3500K SLOC BMD 4.0.1 ~500K SLOC 97% Re-use 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 99% Re-use “Fix Once… Use Many Times” SPY-1D(V) Integration ~15K SLOC Baseline 9 DDG New Construction ~8015K SLOC BMD 5.0 ~2000K SLOC International • 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 99% Re-use AEGIS Ashore Adaptation ~66K SLOC Baseline 9 AEGIS Ashore ~8080K SLOC BMD 5.0 ~2000K SLOC AEGIS / MDA AB Cross Program Governance In Place to Coordinate Multiple Programs Using CSL
SSDS Single Source LibrarySoftware Superset Supports All Platforms 2004 • Open Standards-Based Designs • Componentized Architecture • Well-Defined Interfaces • Open Architecture (OA) Foundation CVN 68 2014 2004 LHA “Fix it Once” 2003 2005 Single Source Library Single Install Media LHD 2012 Core - 2003 • Key Elements of Common Development: • Common Mission Capabilities • “Superset” of Specifications • Common Program Plans • Single Set of Processes & Metrics • Integrated Team Structure • Enterprise Products LPD FSEC Interop - 2005 Build Process OA, ESSM/AEC - 2006 RAM BLK 2 - 2010 LSD, CIWS 2012 2014 AMIIP, FCLIP - 2013 DBR, Mode 5 (engagement only), ESSM with uplink, • Product Line Software Components, SEWIP - 2014 LSD Enables Technology/Capability Insertion Across Diverse Platforms 2015 CVN 78 Extensible Architecture Translates Into Reduced Development, Maintenance and Training Costs
ESSM 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 • 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 Standardize hardware and software components across surface Navy combat system elements Common & Single Source-code Libraries 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 BLK II • SEWIP BLK II/III • Enterprise Air Surveillance Radar (EASR) • 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 “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 • 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 • 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
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
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 • Our technological superiority is not assured, and in fact it is being challenged very effectively right now Honorable Frank Kendall Under Secretary of Defense for Acquisition, Technology and Logistics
Rising Costs Bring Focus on Total Ownership Costs • Total ownership costs • Manning • Training • Mission • Mission effectiveness • Logistics • Interoperability • Capability • Systems effectiveness • Testing • Modeling & simulation • Construction • System/Configuration Item performance • Systems Engineering Focus • Open System Architecture • Standards • Gov’t Data Rights 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