Defense Daily Open Architecture Summit 2014 Defense Daily Open - - PowerPoint PPT Presentation

▶
defense daily open architecture summit 2014 defense daily
SMART_READER_LITE
LIVE PREVIEW

Defense Daily Open Architecture Summit 2014 Defense Daily Open - - PowerPoint PPT Presentation

Aug 06, 2023 256 likes •427 views

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

slide-1
SLIDE 1

Defense Daily Open Architecture Summit 2014 “PEO IWS Open Architecture Implementation” 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

  • Mr. Bill Bray, Executive Director

Program Executive Office, Integrated Warfare Systems November 4, 2014

DISTRIBUTION STATEMENT A: Approved for public release; Unlimited distribution.

slide-2
SLIDE 2

2

Simultaneous Raids Across Multiple Mission Areas Short and Medium Range Ballistic Missiles Intermediate Range Ballistic Missiles Stealth Under-Sea Cyber Warfare Complex Threats Employing Advanced Technology in Challenging Environments Sub-Sonic Anti-Air & Anti-Surface Missiles Super-Sonic Anti-Air & Anti-Surface Missiles Small Boat Attacks Advanced Super-Sonic Anti-Air & Anti-Ship Missiles Torpedoes Anti-Ship Ballistic Missiles Anti-Piracy Humanitarian Assistance Mines Disaster Relief Persistent ISR

Operational Environment

Evolving Joint Environments

Fire Support Missions

slide-3
SLIDE 3

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

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

  • n 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

Commercial Products “Build Once”

Hardware Operating System Middleware

Hardware Operating System Middleware Applications

Display Track Mgmt Command & Control Sensor Mgmt Weapon Mgmt Vehicle Control

slide-4
SLIDE 4

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

Evolution of Open Architecture

slide-5
SLIDE 5

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

Combat System Objective Architecture

Platform Adaptation

Common Core Domains

Track Mgmt Infrastructure External Comms Display Services Vehicle Control Weapon Mgmt Navigation Sensor Mgmt Integrated Training Sensors ExComm Weapons Vehicles Nav Systems Training Systems Combat Control Combat System LAN

slide-6
SLIDE 6

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

Common Computing & Infrastructure Vision

Common Across Baseline configurations

“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

Common Computing & Infrastructure

Build Process Build Process CCI Ships CCI Ships

Common Computing, Storage and Operating Environment

AEGIS, SSDS, Coast Guard, LCS Cross Program Representation

SSDS

slide-7
SLIDE 7

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

AEGIS TI 16 Enabled Consolidation

Today’s Technology Enables a 2:1 Reduction in Footprint With Remaining Margin for Processing and Storage

AEGIS Example

No longer needed

TI 16 TI 12

CEM role caption reduced cables

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

slide-8
SLIDE 8

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

Processing Margin Cabinet Count

AEGIS TI 16 State Of The Practice Improvements

TI 16 Reverses Trends and Requires Less Power, Less Cooling, & Reduces Weight of the Computing Infrastructure With Fewer Cabinets, TI 16 Architecture Continues the Upward Progress on Processing Margin

slide-9
SLIDE 9

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

International

AEGIS Common Source Library (CSL)

REUSE within Baseline configurations

AEGIS / MDA AB Cross Program Governance In Place to Coordinate Multiple Programs Using CSL

Baseline 8 ~3500K SLOC BMD 4.0.1 ~500K SLOC Baseline 9 CG Modernization ~6000K SLOC Baseline 9 DDG Modernization ~8000K SLOC Baseline 9 DDG New Construction ~8015K SLOC Baseline 9 AEGIS Ashore ~8080K SLOC

BMD 5.0 ~2000K SLOC BMD 5.0 ~2000K SLOC BMD 5.0 ~2000K SLOC

SPY‐1D(V) Integration ~15K SLOC AEGIS Ashore Adaptation ~66K SLOC

97% Re‐use 97% Re‐use 99% Re‐use 99% Re‐use 97% Re‐use

“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

Common Source Library

Build Process Build Process CSL Ships CSL Ships

slide-10
SLIDE 10

Distribution Statement A: Approved for Public Release; Distribution is unlimited. RAM BLK 2 - 2010 OA, ESSM/AEC - 2006

SSDS Single Source Library Software Superset Supports All Platforms

CVN 68 LHA LPD CVN 78 LSD

Extensible Architecture Translates Into Reduced Development, Maintenance and Training Costs

LHD 2014

Build Process

“Fix it Once”

Key Elements of Common Development:

  • Common Mission Capabilities
  • “Superset” of Specifications
  • Common Program Plans
  • Single Set of Processes & Metrics
  • Integrated Team Structure
  • Enterprise Products

2003

  • Open Standards‐Based Designs
  • Componentized Architecture
  • Well‐Defined Interfaces
  • Open Architecture (OA) Foundation

Enables Technology/Capability Insertion Across Diverse Platforms

Single Install Media

Core - 2003 FSEC Interop - 2005

Single Source Library

LSD, CIWS 2012 DBR, Mode 5 (engagement only), ESSM with uplink, Product Line Software Components, SEWIP - 2014

2004 2004 2005 2012 2014 2015

AMIIP, FCLIP - 2013

slide-11
SLIDE 11
  • 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

Commonality Across Combat Systems

  • 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

Surface and USW Combat Systems Common Components 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)

ESSM ESSM

Commonality will address reduced training time, reduced O&S Cost and shorter availabilities

Standardize hardware and software components across surface Navy combat system elements

20140808 Combat System Commonality

“Configuration variance in surface ships is not sustainable and must be reduced to manageable levels”

USFFC Letter 01 Aug 13

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
slide-12
SLIDE 12

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

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

slide-13
SLIDE 13

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

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

slide-14
SLIDE 14

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

BACK-UP SLIDES

slide-15
SLIDE 15

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

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

slide-16
SLIDE 16

Distribution Statement A: Approved for Public Release; Distribution is unlimited.

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

Total Ownership Costs (TOC) is a focus of Systems Engineering

Systems Engineering Focus

  • Open System

Architecture

  • Standards
  • Gov’t Data Rights

Source: A.W. Meeks, Naval Open Architecture Avoiding Cost Growth through Open System Architecture, 22 April 2009