Daily Open Architecture Summit 2014 PEO IWS Open Architecture Implementation Mr Bill Bray Executive Director Program Executive Office Integrated Warfare Systems November 4 2014 ID: 177903
Download Presentation The PPT/PDF document "Defense" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Defense Daily Open Architecture Summit 2014“PEO IWS Open Architecture Implementation”
Mr. Bill Bray, Executive DirectorProgram Executive Office, Integrated Warfare SystemsNovember 4, 2014
DISTRIBUTION STATEMENT
A: Approved for public release; Unlimited distribution.Slide2
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
Integrated AAW & Situational Awareness
Advanced
Super-Sonic
Anti-Air
& Anti-Ship Missiles
Torpedoes
Anti-Ship
Ballistic Missiles
Anti-Piracy
Humanitarian
Assistance
Mines
DisasterRelief
PersistentISR
Capability Advancements
Operational Environment
Area Air DefenseIn Clutter Environments
High Data RateBattle Group Networks
Over LandDefense
Integrated Air and Missile Defense
Enhanced Shipboard Sensors(Radar + ES/EA)
Multi-ShipResource Coordination
Cyber Defense
ImprovedSelf-Defense
UAVIntegration
DirectedEnergy
Rail Guns
Advanced ASW
Engage Long Range Ballistic Missiles
Evolving Joint Environments
Fire Support MissionsSlide3
Implementing Open Architecture: Strategy, Interfaces and Open StandardsTreat 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 basisIsolate applications from high rate-of-change COTS through selection of standard APIsUpgrade H/W and S/W Independently and on different refresh intervalsTransform 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 modelEliminate redundant software development efforts
Commercial
Products
“Build
Once”
Hardware
Operating System
Middleware
Hardware
Operating System
Middleware
Applications
Display
Track
Mgmt
Command
&
Control
Sensor
Mgmt
WeaponMgmtVehicleControlSlide4
Evolution of Open ArchitectureSlide5
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 SystemsTraining SystemsCombat Control
Combat System LANSlide6
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 AlignedSingle Set of Processes & MetricsIntegrated Team Structure
Enterprise ProductsCommon Computing & Infrastructure
Build Process
CCI Ships
Common Computing, Storage and Operating Environment
AEGIS, SSDS, Coast Guard, LCS Cross Program Representation
SSDSSlide7
AEGIS TI 16 Enabled Consolidation
Today’s Technology Enables a 2:1 Reduction in Footprint With Remaining Margin for Processing and Storage
AEGIS Example
0
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 DPCSlide8
Processing
Margin
Cabinet
Count
19
16
11
44.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 MarginSlide9
InternationalAEGIS Common Source Library (CSL) REUSE within Baseline configura
tions
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 SLOCBMD 5.0~2000K SLOCBMD 5.0~2000K SLOC
SPY-1D(V)Integration~15K SLOCAEGIS AshoreAdaptation~66K SLOC97% Re-use97% Re-use99% Re-use99% Re-use97% Re-use
“Fix Once…Use Many Times”Key Elements of Common Development:Common Mission CapabilitiesSingle Set of Specifications
Common Program PlansSingle Set of Processes & MetricsIntegrated Team StructureEnterprise ProductsCommon Source LibraryBuild Process
CSL ShipsSlide10
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
Proces
s
“Fix it Once”
Key Elements of Common Development:
Common Mission Capabilities
“Superset”
of Specifications
Common Program Plans
Single Set of Processes & MetricsIntegrated Team StructureEnterprise Products2003Open Standards-Based Designs Componentized ArchitectureWell-Defined Interfaces
Open Architecture (OA) FoundationEnables Technology/Capability Insertion Across Diverse Platforms
SingleInstallMediaCore - 2003FSEC Interop - 2005SingleSourceLibraryLSD, CIWS 2012DBR, Mode 5 (engagement only), ESSM with uplink, Product Line Software Components, SEWIP
- 2014
2004
2004
2005
2012
20142015
AMIIP, FCLIP - 2013Slide11
JTM- Joint Track ManagerCDS- Common Display System
CPS- Common Processing SystemBFTT- Battle Force Team TrainerCANES 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 ComponentsNear-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
Commonality will address reduced training time, reduced O&S Cost and shorter availabilitiesStandardize 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 13Common & Single Source-code LibrariesKey Elements of Common Development:Common
Mission CapabilitiesSingle Set of SpecificationsCommon Program PlansSingle Set of Processes & MetricsIntegrated Team StructureEnterprise ProductsSlide12
Better Buying Power 3.0
Achieve Dominant Capabilities While Controlling Life Cycle CostsStrengthen “should cost” as an important tool for cost managementBuild stronger partnerships between acquisition, requirements, and intelligence communitiesAnticipate and plan for responsive and emerging threats
Institutionalize stronger DoD level long range (R&D) planningIncentivize Productivity in Industry and Government
Align profitability more tightly with Department goals
Employ appropriate contract types, but increase use of incentive type contractsImprove 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 BureaucracyPromote Effective CompetitionImprove Tradecraft in the Acquisition of ServicesIncrease small business participation
Strengthen contract managementImprove Requirements definitionImprove the Professionalism of the Total Acquisition WorkforceSlide13
SummaryIWS 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 consolidationIdentify 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 deploymentIdentify opportunities for continued Better Buying Power savingsSlide14
BACK-UP SLIDESSlide15
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 excellenceOur 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 LogisticsSlide16
Rising Costs Bring Focus on Total Ownership CostsTotal ownership costsManningTrainingMissionMission effectivenessLogistics
InteroperabilityCapabilitySystems effectivenessTestingModeling & simulationConstructionSystem/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