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
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
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
Commercial
Products
– Bundle specific COTS products for a given
timeframe and revisit selections on a regular basis
Applications
Middleware
Operating System
Hardware
 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 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
Distribution Statement A: Approved for Public Release; Distribution is unlimited.
“Build
Once”
Track
Mgmt
Command
Sensor Weapon Vehicle
&
Mgmt
Mgmt Control
Control
Display
Middleware
Operating System
Hardware
Evolution of Open Architecture
Distribution Statement A: Approved for Public Release; Distribution is unlimited.
Combat System Objective Architecture
Vehicles
Platform Adaptation
ExComm
Combat System LAN
Weapons
Sensors
Nav Systems
Common Core Domains
External
Comms
Display
Services
Vehicle
Control
Sensor
Mgmt
Combat
Control
Weapon
Mgmt
Track
Mgmt
Navigation
Distribution Statement A: Approved for Public Release; Distribution is unlimited.
Integrated
Training
Infrastructure
Training Systems
Common Computing & Infrastructure Vision
Common Across Baseline configurations
Build Process
CCI Ships
Common Computing &
Infrastructure
SSDS
“Common Components Across
Multiple Combat Systems”
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
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
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
Distribution Statement A: Approved for Public Release; Distribution is unlimited.
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
Distribution Statement A: Approved for Public Release; Distribution is unlimited.
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
Build Process
CSL Ships
Baseline 8
BMD 4.0.1
~3500K SLOC
~500K SLOC
97% Re-use
Common Source
Library
Baseline 9
CG Modernization
97% Re-use
~6000K SLOC
97% Re-use
Baseline 9
DDG Modernization
~8000K 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
~2000K SLOC
99% Re-use
International
Baseline 9
DDG New Construction
~8015K SLOC
BMD 5.0
SPY-1D(V)
Integration
~2000K SLOC
~15K SLOC
99% Re-use
Baseline 9
AEGIS Ashore
~8080K SLOC
AEGIS / MDA AB Cross Program Governance
In Place to Coordinate Multiple Programs Using CSL
Distribution Statement A: Approved for Public Release; Distribution is unlimited.
BMD 5.0
BMD 5.0
~2000K SLOC
AEGIS
Ashore
Adaptation
~66K SLOC
SSDS Single Source Library
Software Superset Supports All Platforms
2004
•
•
•
•
Open Standards-Based Designs
Componentized Architecture
Well-Defined Interfaces
Open Architecture (OA) Foundation
CVN 68
2014
“Fix it Once”
2003
Build
Process
Single
Install
Media
Key Elements of Common Development:
• Common Mission Capabilities
• “Superset” of Specifications
• Common Program Plans
• Single Set of Processes & Metrics
• Integrated Team Structure
• Enterprise Products
FSEC Interop - 2005
OA, ESSM/AEC - 2006
RAM BLK 2 - 2010
LPD
2005
Single
Source
Library
Core - 2003
2004
LHD
2012
LHA
2014
LSD
LSD, CIWS 2012
Enables Technology/Capability
Insertion Across Diverse Platforms
AMIIP, FCLIP - 2013
DBR, Mode 5 (engagement only), ESSM with uplink,
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.
2015
CVN 78
Commonality Across Combat Systems
Commonality will address reduced training time, reduced O&S Cost and shorter availabilities
Surface and USW 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
Standardize hardware and software components
across surface Navy combat system elements
Common Components
•
•
•
•
•
•
•
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
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
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 13
20140808 Combat System Commonality
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
•
Incentivize Innovation in Industry and
Government
—
—
—
—
•
•
•
Eliminate Unproductive Processes and
Bureaucracy
Promote Effective Competition
Improve Tradecraft in the Acquisition of
Services
–
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
Distribution Statement A: Approved for Public Release; Distribution is unlimited.
—
•
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)
Increase small business participation
Strengthen contract management
Improve Requirements definition
Improve the Professionalism of the Total
Acquisition Workforce
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
Distribution Statement A: Approved for Public Release; Distribution is unlimited.
BACK-UP SLIDES
Distribution Statement A: Approved for Public Release; Distribution is unlimited.
USD AT&L
Honorable Frank Kendall
Under Secretary of Defense for
Acquisition, Technology and
Logistics
•
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
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 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
Distribution Statement A: Approved for Public Release; Distribution is unlimited.