Unlocking Potential 1 Open Systems Architecture for Payloads and Platforms for Flexible Modular...

Unlocking Potential 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


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

Unlocking Potential 3Unlocking Potential

Naval OSA Strategy

3

https://acc.dau.mil/osastrategy


Goals of Naval OSA Strategy

Develop OSA RecommendationsDevelop OSA Recommendations

Issue Issue Guidance/Tools Guidance/Tools

Authorities Direct Change Authorities Direct Change

Affordable Design/ Test OSA Working Groups

TRF Communications

Rewards/ Incentives Training

Open Business Model

Tools / Guides


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

The Naval Business Model – Top-Level Strategy

Modular Spaces Modular Capabilities

TBD

TBD

Unlocking Potential 6Unlocking Potential

Speed of change for Shipboard Systems

6


Common SWFTS Product Line

Seawolf

BEFORE

Ohio (SSBN)

Los Angeles

Virginia

Common SWFTS

Processes &Systems

SWFTS

SWFTS

Submarine Classes Contain the Same Basic Set of Subsystems and Information Architecture; Variations are due to sensors and mission capabilities

BSY - 2

Trident CCS

CCS Mk-2

NPES

Ohio (SSBN)

Trident CCS

Seawolf

Los Angeles

Virginia

Ohio (SSGN)

SWFTS

SWFTS

SWFTS

SWFTS

AFTER FUTURE

OR

Virginia BLK IV

Unlocking Potential 8Unlocking Potential 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.

BACKBONE REQUIREMENTS

POWER COOLING VOLUME

PLATFORM

Payload D

Payload E

Payload B

Payload F

Payload C

Payload A


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


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


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


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)

Renault CMF architecture concept

Source: http://wardsauto.com/vehicles-amp-technology/big-rewards-hurdles-seen-next-gen-flexible-vehicle-architectures

The appearance of products, services, or corporate names does not constitute endorsement by the Department of Defense


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

Source: http://wardsauto.com/vehicles-amp-technology/big-rewards-hurdles-seen-next-gen-flexible-vehicle-architectures



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

Sources:http://wardsauto.com/management-amp-strategy/gm-vehicle-platform-consolidation-accelerating-product-chief-sayshttp://wardsauto.com/auto-makers/gm-taking-new-approach-global-engineering-vehicle-architectureshttp://wardsauto.com/auto-makers/new-management-team-lifts-veil-gm-strategy



• 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

Modular and Open Warship VisionModular and Open Warship Vision

Top-level Objective: Affordable Relevance over the Life CycleTop-level Objective: Affordable Relevance over the Life Cycle

Flexible Ship =Platform +Payload +

Growth Margin

Unlocking Potential

CONTRACTS

Module 1O-C

Module 2R-P

Integration O-C

Competition Across the Lifecycle

•Competition for O-C•Replacement for R-P

NEW Naval Business Model

REQUIREMENTS

WARFIGHTER

TECHNOLOGY

Functional Module 1 O-C R-P

Functional Module 2

Integration O-C…


Mission Design/ Warfighting Architecture

Vision: Open Acquisition Model Relationship to Resourcing

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

MISSION

COMMONCAPABILITIES

PLATFORMS

Built on Open Technical Reference Frameworks and Open Acquisition Strategies

The Open Business Model: Cross-Program Partnering

Unlocking Potential 1 Open Systems Architecture for Payloads and Platforms for Flexible Modular...

Documents

Transcript of Unlocking Potential 1 Open Systems Architecture for Payloads and Platforms for Flexible Modular...