1. Open Systems Architecture for Payloads and Platforms for Flexible Modular Warships
Nickolas Guertin, PE
DASN RDT&E, Director for Transformation
CAPT Paul J. VanBenthem, USN
DASN RDT&E, Naval Open Architecture Implementation
ASNE Day 2015
Distribution Statement A: Approved for public release

2. Building on a Solid Foundation
We have evolved the Naval Open Systems Architecture Strategy
We are working on Open Technical Reference Architectures
We have established an IP Strategy for acquiring systems
The Navy has experience in building common combat systems
Portfolio management of common and open product lines
Opinions expressed are those of the authors and do not reflect official policy or position of the US Government

3. Naval OSA Strategy

4. Goals of Naval OSA Strategy
Authorities Direct Change
Issue Guidance/Tools
Develop OSA Recommendations
Affordable Design/ Test
OSA Working Groups
TRF
Communications
Rewards/ Incentives
Training
Open Business Model
Tools / Guides

5. The Naval Business Model – Top-Level Strategy
Procure Basic Platforms
Decouple the mission systems and integration from the platform
Able to quickly change modular components for future flexibility
Stabilize platform production – segregate from rapid change
Develop/ Maintain Capability Product Lines
Reduce and manage vendor-locked and stove-piped products
Improve core competencies across the force
Design for robust, affordable testing
Build in adaptability
Integrate and Deliver
Manage Platform-unique elements
Reduce acquisition cost and risk
Spur innovation and enhance warfighter capability
Modular Spaces
Modular Capabilities D B T
TBD

6. Speed of change for Shipboard Systems

7. Common SWFTS Product Line
BEFORE
AFTER
FUTURE
Seawolf
Seawolf
BSY - 2
SWFTS
Common SWFTS
Processes &
Systems
Los Angeles
Los Angeles
CCS Mk-2
SWFTS
Ohio (SSGN)
SWFTS
Virginia
Virginia
Virginia BLK IV
NPES
SWFTS
SWFTS
Ohio (SSBN)
Ohio (SSBN) OR
Trident CCS
Trident CCS
SWFTS
Submarine Classes Contain the Same Basic Set of Subsystems and Information Architecture; Variations are due to sensors and mission capabilities

8. CNOs Challenge: Create Modularity
THINK Open Architecture
THINK Plug and Play
THINK Payloads over Platforms
The Navy’s future depends on vessels that use common, open architectures, allowing individual systems to be removed and new ones to be plugged in as warfighting requirements change.
Payload E
Payload D
Payload B
Payload A
Payload C
Payload F
POWER
COOLING
VOLUME
BACKBONE REQUIREMENTS
PLATFORM

9. Open Acquisition Intellectual Property Strategy
Government as Business Integrator
Choose where to invoke generous license rights to design data
Architecture and interfaces
What the Government paid to develop
Choose where to invoke innovation
Where warfighting requirements change quickly
Where the Commercial sector is investing
Where there are multiple strong providers

10. Learning from Industry
DoD can learn from commercial industry's playbook
Leverage their “lessons learned” based on product-line success
Industry has proven that investment in initial product-line architecture reaps system life cycle cost reductions due to:
Integration
Planning for obsolescence
Technical refresh
Common components and software across platforms

11. Typical Industry Standard Practices
Multi-use – multiple levels
Architecture
Hardware modules and structures
Software
Common core components
Design
Standardized interfaces
Require use of standard interfaces between modules
Multiple vendors able to produce modules meeting form/fit/function requirements

12. Renault
“Automakers rapidly are moving toward a new era in vehicle architectures that promises lower costs, turn- on-a-dime manufacturing and shorter product- development lead times” (WardsAuto, Oct 28, 2013)
The appearance of products, services, or corporate names does not constitute endorsement by the Department of Defense
Renault CMF architecture concept
Source:

13. Volkswagen
MQB architecture to underpin 39+/- models covering eight size and market segments
Allows for quicker product development as future vehicles are derived from the existing platform
Photo courtesy WardsAuto, Oct 28, 2013
The appearance of products, services, or corporate names does not constitute endorsement by the Department of Defense
Source:

14. General Motors Adopting a more flexible approach
mixes and matches modules across product portfolio
Modular architectures enable:
quick reaction to changes in consumer preferences
shorten vehicle development times
Reduce architectures from 30 in 2010
to 17 in 2018, core platforms from 39% to 96%
to 99% on core architectures by 2020
to 4 basic vehicle sets in 2025
Consolidate lead engineering to one center
drive inefficiency out of product-development process
The appearance of products, services, or corporate names does not constitute endorsement by the Department of Defense
Sources:

15. Modular and Open Warship Vision
Efficient and frequent capability insertion and technology refresh to overcome obsolescence at the lowest possible cost
Greater mission adaptability and warfighting dominance via re-configuration
Increased efficiencies in ship design, construction, testing, sustainment, and disposal achieve affordable relevance over the lifecycle
Flexible Ship =
Platform +
Payload +
Growth Margin
Top-level Objective: Affordable Relevance over the Life Cycle

16. … NEW Naval Business Model CONTRACTS TECHNOLOGY REQUIREMENTS
Competition Across the Lifecycle
Competition for O-C
Replacement for R-P
REQUIREMENTS
WARFIGHTER
TECHNOLOGY
CONTRACTS
Module 1
O-C
Module 2
R-P
Integration O-C
RP = Restricted-Proprietary Model: when EITHER the data rights OR the data deliverables  do not allow competitive life cycle activities
OC = Open-Competitive Model: when BOTH the data rights AND the data deliverables  allow competitive life cycle activities
Functional Module 1
O-C
R-P
Functional Module 2
Integration …

17. Vision: Open Acquisition Model Relationship to Resourcing
The Open Business Model: Cross-Program Partnering
Vision: Open Acquisition Model Relationship to Resourcing
Mission Design/ Warfighting Architecture
Common Capabilities
Platforms
MISSION
COMMON
CAPABILITIES
PLATFORMS
Radar / EW
Networks & Comms
EO/ IR
Navigation
Sonar
Combat C2
Intel Analysis
CVN
Surface
Fast AIR
Big AIR
Submarines
Land
Space
Air Weap.-UaV
Undersea Wep.- Us/uV
Built on Open Technical Reference Frameworks and Open Acquisition Strategies