ASNE Combat System Symposium PEO IWS Approach to Open Systems Architecture Mr. Bill Bray, Executive...

ASNE Combat System SymposiumPEO IWS Approach to Open Systems Architecture

Mr. Bill Bray, Executive DirectorProgram Executive Office, Integrated Warfare Systems

9 December 2014

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

2

Simultaneous Raids Across

Multiple Mission Areas

Short and Medium Range Ballistic Missiles

Intermediate RangeBallistic Missiles

StealthUnder-Sea

CyberWarfare

Complex ThreatsEmploying Advanced Technology

in Challenging Environments

Sub-Sonic Anti-Air &

Anti-Surface Missiles

Super-Sonic Anti-Air &

Anti-Surface Missiles

Small Boat Attacks

Integrated AAW

& Situational

Awareness

Advanced Super-Sonic

Anti-Air & Anti-Ship Missiles

Torpedoes Anti-ShipBallistic Missiles

Anti-Piracy

Humanitarian Assistance

Mines

DisasterRelief

PersistentISR

Capability Advancements

Operational Environment

Area Air Defense

In Clutter Environments

High Data Rate

Battle Group Networks

Over Land

Defense

Integrated Air

and Missile Defense

Enhanced

Shipboard Sensors

(Radar + ES/EA)

Multi-Ship

Resource

Coordination

Cyber

Defense

Improved

Self-DefenseUAV

Integration

Directed

Energy

Rail GunsAdvanced ASW

Engage Long Range

Ballistic Missiles

Evolving Joint Environments

Fire Support Missions

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

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

– 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

Commercial Products

“Build Once”

Hardware

Operating System

Middleware

Hardware

Operating System

Middleware

Applications

Display

Track Mgmt

Command&

Control

SensorMgmt

WeaponMgmt

VehicleControl


Evolution of Open Systems Architecture


Combat System Objective Architecture

Plat

form

Ada

ptat

ion

Common Core Domains

TrackMgmt

Infrastructure

External Comms

DisplayServices

Vehicle Control

Weapon Mgmt

Navigation

Sensor Mgmt

IntegratedTraining

Sensors

ExComm

Weapons

Vehicles

Nav Systems

Training Systems

Combat Control

Combat System LAN


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 ProcessCCI Ships

Common Computing, Storage and Operating

Environment

AEGIS, SSDS, Coast Guard, LCS Cross Program Representation

SSDS


AEGIS TI 16 Enabled Consolidation

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

AEGIS Example

0No longer needed

TI 16TI 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


• Fewer Unique Parts

• Reduced Qualification Effort

• Common Use Across Multiple Programs

TI 16 Common Building Blocks for Navy Combat Systems

3U Server

VMEbus Chassis

3064 Edge Switch

Remote Access Server

Power Control Device

1U Server

Enclosure Monitor

Storage

Tactical ServerChassis

DC Power Distro

3132 Core Switch

DVI TrayEncoder Tray

Firewall

Improved Capabilities– 40% Processing Capacity Increase– 3X Computing Density– 300% Increase Bandwidth– 35% Increase in Storage (115 TB)– Dual Network Redundancy– Redundant Display Connection

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

Common Building Blocks is the Key Concept of TI-16 for Reduced Fleet Maintenance, Training and Life Cycle Costs


Processing Margin

Cabinet Count

19

16

1144.8%

76.8%

115.2%

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

RAM BLK 2 - 2010

OSA, ESSM/AEC - 2006

SSDS Single Source LibrarySoftware 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 Systems Architecture (OSA) Foundation

Enables Technology/Capability Insertion Across Diverse Platforms

SingleInstallMedia

Core - 2003

FSEC Interop - 2005

SingleSourceLibrary

LSD, CIWS 2012

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

2004

2004

2005

2012

2014

2015AMIIP, FCLIP - 2013


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 SLOCBMD 4.0.1

~500K SLOC

Baseline 9CG Modernization

~6000K SLOC

Baseline 9DDG Modernization

~8000K SLOC

Baseline 9DDG New Construction

~8015K SLOC

Baseline 9AEGIS 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 ProcessCSL Ships

• 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 OSA 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)

ESSMESSM

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


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


PEO IWS Systems EngineeringSafe 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 end-

to-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!

PEO IWS LetterDated 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

ASNE Combat System Symposium PEO IWS Approach to Open Systems Architecture Mr. Bill Bray, Executive...

Documents

Transcript of ASNE Combat System Symposium PEO IWS Approach to Open Systems Architecture Mr. Bill Bray, Executive...