Read Sustaining Today's Force Structure and Building the Future Force text version

Surface Navy Combat System Development Strategy Update

Presented to the Sea Air Space Symposium

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

Mr. Chris Deegan PEO Integrated Warfare Systems 3 May 2010

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

Surface Navy Association Panel Discussion ­ 14 January 2010

1

SNA Symposium

15 January 2008 and 19 March 2008

2008 Strategy Goals:

­ Decouple hardware from software ­ Componentize combat systems architecture and common information standards ­ government owned architecture and interfaces ­ Establish a combat system product line approach based on a common objective architecture ­ Decouple combat system development from platform development while continuing to accommodate platform specific needs ­ Compete where and when appropriate

Surface Navy Association Panel Discussion ­ 14 January 2010

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

2

Looking Ahead to Advanced Capability Build (ACB) 12 and Beyond

Combat Systems must transition to a network-based COTS Computing Environment to support future warfighting improvements System Engineering Guidance has been documented, will be updated based on experience We will continue the transition to a network-based COTS Computing Environment as fast as feasible Competitions are being conducted when and where appropriate

Increased computing power and network-based performance will enable significant combat system warfighting improvements

Surface Navy Association Panel Discussion ­ 14 January 2010 Distribution Statement A: Approved for Public Release: Distribution is unlimited

3

Surface Navy Combat System

Transition to Objective Architecture On Track

As of November 2009

Decoupling of Software from Hardware on NIMITZ & BUNKER HILL completed NIMITZ final SSDS Software Cert completed June 09 BUNKER HILL CSSQT successfully completed 30 July 09 BUNKER HILL Software Cert completed November 09

DDG 1000

DDG 1000

Legacy Components

3rd Party Development

RCIP S&T Rapid Development

AMOD

Aegis

Objective Architecture

Component Development available for competition, where appropriate, starting in 2009

· Defined superset component requirements · Establish interfaces IAW objective architecture · Develop/deliver authenticated components

SSDS

SSDS

2012

2012

Aegis modernization (ACB 12) component level interfaces delivered at CDR (1Qtr FY10) and with each delivered computer program build SSDS interfaces already documented at component level Small number of common components integrated in both Aegis & SSDS-ACB 12

A component is a bounded module with: · Associated requirements (in DOORS) · Design description · Defined Interface (modeled in UML)

Common Assets Library

Available for fielding in FSC and backfit in 2014 & beyond

2014 - 2022

Number of common components will increase with each ACB eventually moving to a common software core for all Surface Navy Combat Systems Required warfighting capabilities will determine which components modified

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

Surface Navy Association Panel Discussion ­ 14 January 2010

4

PEO IWS System Engineering Guidance

System Engineering Guidance to align PEO IWS' efforts beginning with POM 12

Surface Navy Association Panel Discussion ­ 14 January 2010 Distribution Statement A: Approved for Public Release: Distribution is unlimited

5

Surface Warfare Tactical Requirements Group (SWTRG) ACB Content Definition Process

N86 defined Advanced Capability Build (ACB) content for the Acquisition Community

­ Informal, collaborative approach between Action Officers and PEO IWS SIPMs / MPMs for content definition and alignment ­ SWTRG is formal content definition governance process

Required attendance for: Required attendance for: 1. Air and Ballistic Missile Defense 1. Air and Ballistic Missile Defense capability issues capability issues 2. Intelligence capability issues 2. Intelligence capability issues 3. Amphibious capability issues 3. Amphibious capability issues 4. Aircraft Carrier capability issues 4. Aircraft Carrier capability issues

N86 will document ACB content requirement via formal documentation (e.g., Commander's Guidance Letter) Approved ACBs will require resourcing to the approved requirement

PEO IWS Execution Review Science & Technology (S&T) Program of Record (PoR)

N86 Commander's Guidance

1

ESG

N86 (Chair) CNSL N6F ABMD 2 N22 3 N85 4 N88

BOD N86E / N86F (Co-Chair)

Fleet Requirements

CNSL N8 ACOS Requirements & Assessments N6F2 COTP Applications N6F4 Program Integration and Interoperability N6N1 Afloat and Shore Networks N862 Current Ships N864 Maritime Warfare Systems / Strike Warfare N865 Theatre Air and Missile Defense N866 Combat Systems Integration N867 Anti Terrorism / Force Protection / CBRN 1 PD-452 2 N22 Technical liaison to N86 3 N853 Amphibious Warfare 4 N885 Deputy Aircraft Carriers

Rapid Capability Insertion Process (RCIP)

Working Group

N866 (Chair)

N865C EW N6F21 Operational C2 N864A ASW N867F1 ATFP/ EMIO -VBSS N865G Missile Systems N6F22 Tactical Picture / N864F Strike / Tomahawk N867F2 CBRN N865R Radars Interoperability 1 N864G Naval Surface Fire PD-452 2 N866C CEC N6F413 C4I Requirements N22 Technical liaison to N86 Support N866J IAMD / NIFC -CA 3 N853C Amphip Ship Req Integration N865A Air Defense 4 N866O OA / SFI N6N1 ISNS / CANES N885D In-Service CVN N865B BMD 4 N866T Training / N862C CG / DDG Mod N885E Future CVN 1 PD-452 Navigation

PEO IWS Execution Letter SWTRG Working Group Action Officers PM Input

Surface Navy Association Panel Discussion ­ 14 January 2010

SWTRG Board of Directors (BOD) Branch Heads Financial Input

SWTRG Executive Steering Group (ACB ESG) Flags

NCD Annex

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

6

Major Warfighting Capabilities Delivered Through Advanced Capability Builds (ACBs)

ACB 08

­ Decoupled software from hardware with COTS

ACB 12

­ Network-based COTS computing environment with significant computing performance improvements (AMOD) ­ Common Processor System (CPS) / Common Display System (CDS) ­ Common Track Manager / Track Server components in SSDS (CVN 78) and AMOD ships ­ Initial MH-60R capability (CVN) ­ Naval Integrated Fire Control ­ Counter Air (NIFC-CA) (AMOD) ­ Ballistic Missile Defense (BMD) Capability 5.0 (AMOD) ­ SM-6 (AMOD)

ACB 14

­ MH-60R Control Common Components will be introduced into SSDS and Aegis Combat Systems Across ACB 14 & 16 as development funding permits ­ Full ACB 14 definition under development in conjunction with POM 12

Surface Navy Association Panel Discussion ­ 14 January 2010 Distribution Statement A: Approved for Public Release: Distribution is unlimited

7

Aegis Weapon System Hardware Architecture Roadmap

Pre-Aegis

Year 1960

B/L 1/2/3/4/5

DDG 51-78 DDG 51-78 CG 47-73 CG 47-73 1980

B/L 6 Ph I/III B/L 7 Ph I ACB 08/TI 08

DDG 79-90 DDG 79-90 CG 66 & 69 CG 66 & 69 1994 DDG 91-112 DDG 91-112

Advanced Capability Advanced Capability Build (ACB) Build (ACB) Technology Insertion (TI) Technology Insertion (TI)

ACB 12/TI 12

ACB 16/TI 16

2002

2009

2012

2016

Weapon System

CPS

CPS

MIL Spec Design

MIL Spec Design

Mixed COTS and MILSpec Design

Mission Critical Enclosure (MCE) All COTS computers

(MCE) Common Processing Common Processing A Scaleable Pool of System (CPS) & MCE System (CPS) & MCE Interchangeable A Scaleable Pool of A Scaleable Pool of Processors Interchangeable Processors Interchangeable Processors

Processors

UYK-7

UYK-7 UYK-43 UYK-20 UYK-44

UYK-43/44+ Adjunct COTS

COTS SMP's

COTS Blades

COTS Blades

COTS TBD

Normalized Equivalent 2 UYK-43 Capability UYH-4

4 UYK-43

120 UYK-43

270 UYK-43

875 UYK-43

~2500 UYK-43

TBD

Displays

UYH-4

UYQ-21 (TGC)

UYQ-21/UYQ-70

Thin Client Displays

Thin Client Displays

Common Display Systems (CDS)

Connectivity

All NTDS

Point-to-Point

Point-to-Point

Point-to-Point

All Network Pub Sub

All Network Pub Sub

Surface Navy Association Panel Discussion ­ 14 January 2010

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

8

Surface Combat System Top Level Architecture

(ACB 12) Common Track Manager / Track Server Components

Operational Command & Control GCCS, NECC, NCCT

Platform Adaptation External Communications Domain

Link 16 S TDL J JRE Link 11 Link 22 CDL-N DDS SIPRNET NIPRNET JTT / IBS SPY-1 DBR AMDR SPQ-9B SPS-49A SPS-48E SPS-67 SPS-73 SPS-74 UPX-29 UPX-37 CIWS MK 9 SLQ-32 EDO ESM SEWIP EO/IR FLIR MH-60R Towed Sonar Hull Sonar Bridge System TDL Interface Controller CDL Interface Controller DDS Interface Controller SATCOM Router Interface IBS Interface Controller Comms Domain Manager External Comms Coordinator

Display Domain

Platform Specific GUIs

Platform Specific Display Apps

Vehicle Control Domain

Vehicle Vehicle Vehicle Domain Sensor Coordinator Manager Coordinator Vehicle Vehicle Vehicle Weapon Comms Scheduler Coordinator Coordinator Asset Launch/ Controller Recovery Module Asset Vehicle Controller Controller

Common Core

Training Training Common Dev Env Dev Env GUIs Common Display Apps Remote Display Controller Operator Task Manager

Vehicles Fixed Wing MH-60R Small Boats UAV UUV USV

TACSIT Display Services

GUI Display Services

Display Renderer

Audio/ Video Services

Weapon Mgmt AMD Domain Coordinator

Weapon Domain Manager Engagement Scheduler USW Coordinator SUW Coordinator Strike Coordinator

Collaboratio n Manager

Sensor Sensor Missile Control Control Controller (one per missile) Sensor Sensor Weapon Control Control Controller (one per weapon)

Sensor Mgmt Domain

Sensor Sensor Sensor Control Control Controller (one per sensor)

Sensor Domain Manager Above Water Sensor Coordinator Below Water Sensor Coordinator

Track Mgmt Domain

Track Server System Track Manager MultiSource Integrator Link Data Manager Combat Identification Geodetic Registration

Combat Control Domain

Logistics Support Domain Services Tactical Action Manager Decision Support Services Tactical Mission Planners Ship Resource Manager Readiness Assessor Data Reduction Scenario Controller Combat System Trainer ASW Trainer EW Trainer Ship Control Trainer Computer Based Training Sensor Sensor Sensor Sim/Stim Simulator/ Sim/Stim Stimulator Weapon Weapon Weapon Simulator Simulator Simulator Weapon Weapon Ext. Comms Simulator Simulator Simulator Nav System Simulator

Training Domain

Knowledge Manager Training Dev Env Planning Core Data Collector After Action Reviewer Performance Analyzer

Navigation Domain

Bridge Interface Controller

Ship Movement Coordinator Chart Server

Single Sensor Tracker

Composite Tracker

CC Support Services

Missiles SM-2 SM-3 SM-6 ESSM RAM ASROC Weapons MK 41 VLS MK 57 VLS MK 29 GMLS RAM GMLS SeaRAM MK 160 AGS MK 160 GFCS CIGS CIWS TTWCS Harpoon MK 36 DLS Nulka SLQ-32 EA OTST ATT NIXIE NLOS

GPS Inertial / Gyro Water Speed Log Depth Sounder Magnetic Compass METOC Sensors AIS

ECDIS-N Navigation Data Fuser

C.S. C.S. C.S. LAN Network Interior Mgr Security Comms Data Data Computing SOA Core Precision Mediation Extraction / Resource Services Nav & Time Services Recording Mgr Computing Distributed Messaging Data C.S Security/ Environment Objects Services Mgmt Info Assur.

Infrastructure Domain Component Framework

Computing Equipment Domain Surface Navy Association Panel Discussion ­ 14 January 2010

Consoles

Displays

Cabinets

Processors

Storage

Networks

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

9

SSDS Combat System Transition to Open Architecture

SSDS used modular SSDS used modular design and development design and development to fulfill self defense to fulfill self defense requirements across requirements across multiple platform types multiple platform types with existing combat with existing combat system elements system elements SSDS MK 2 OA adds SSDS MK 2 OA adds flexibility to accommodate flexibility to accommodate change (threat, sensors, change (threat, sensors, weapons, requirements, weapons, requirements, ship class modifications) ship class modifications) Computing infrastructure Computing infrastructure common with Aegis common with Aegis middleware fielded in middleware fielded in NIMITZ FY08 NIMITZ FY08

Bllk 2 Bk2 RAM RAM

ol ontr ent C M gem ESS d Enga tive k 0 / 1 an FY10 Adap M Bl RA

FY09 FY08

1 LHD 1 CVN 3 CVN 1 LPD CVN 68 USS NIMITZ 2 LPD 1 LHA 1 LPD 2 LSD 1 LPD 2 LSD

4 14 ACB 1 ACB

ry Libra urce n So FY16 mo FY15 Com

FY14 FY13 FY12 FY11

2 CVN 1 LPD 3 CVN 3 LSD 3 LSD 1 LPD 1 LSD 1 LHD

2 12 ACB 1 ACB

FY18 FY17

FY19

2 LSD 2 LPD 1 LHD 2 LSD 1 LSD

1 LSD

Legend

AEC RAM Blk 0/1 and ESSM RAM Blk 2 ACB 12 ACB 14 ACB 16 and Beyond

Open Computing Hardware is Foundation for New Capability

Surface Navy Association Panel Discussion ­ 14 January 2010 Distribution Statement A: Approved for Public Release: Distribution is unlimited

10

Capability

1 LPD

Aegis Combat System Transition to Open Architecture

The AEGIS system was initially The AEGIS system was initially designed as an integrated and designed as an integrated and tightly coupled hardware and tightly coupled hardware and software Combat System software Combat System OA-based ACB08 // TI08 (CR2) OA-based ACB08 TI08 (CR2) hardware and software hardware and software installed in BUNKER HILL in installed in BUNKER HILL in FY08 using modular design FY08 using modular design Computing infrastructure Computing infrastructure common with SSDS common with SSDS middleware fielded in middleware fielded in BUNKER HILL FY08 BUNKER HILL FY08 CG 47 Class completion CG 47 Class completion Network-based Open Network-based Open Architecture Computing Architecture Computing Environment in 2017 Environment in 2017 POM 10 Estimates for DDG 51 POM 10 Estimates for DDG 51 Class Show Transitioning Class Show Transitioning

­ ­ ­ ­ 3 ships/year FY12-16 3 ships/year FY12-16 6 ships/year FY17-on 6 ships/year FY17-on

2 CGs CG 52 USS Bunker HIll

16 ACB

...

12 ACB

rary e Lib ourc on S FY18 m FY17 Com FY16

FY15 FY14 FY13

6 DDGs 6 DDGs 3 CGs 3CGs 3CGs 3 DDGs 3DDGs 3 DDGs

14 ACB

FY26

...

4 DDGs

FY12

08 ACB

FY09 FY08

FY11 FY10

3 CGs

2 CGs 2 CGs 2 CGs 2 DDGs ACB 08 ACB 12 ACB 14 ACB 16 ACB 18 and Beyond 3DDGs

Legend

DDG 51 Class will complete DDG 51 Class will complete Transitioning to Network-based Transitioning to Network-based Open Architecture Computing Open Architecture Computing Environment in 2026 Environment in 2026

Open Computing Hardware is Foundation for New Capability

Surface Navy Association Panel Discussion ­ 14 January 2010 Distribution Statement A: Approved for Public Release: Distribution is unlimited

11

Capability

1 CGs

Transitioning to Objective Architecture Based Combat System

2008

· Aegis designed as an integrated combat system · Aegis ACB 08 / TI 08 decoupled hardware from software · SSDS designed with federated combat system network and hardware decoupled from software · SSDS ACB 08 adds open standard middleware · Future capability improvements planned for both programs through Advanced Capability Build (ACB)

2012

· Aegis modernization (ACB 12) component level interfaces delivered at CDR (1Qtr FY10) and with each delivered computer program build · SSDS interfaces already documented at component level · Small number of common components integrated both Aegis & SSDS ACB 12

2014-2022

· Number of common components will increase with each ACB moving to a common software core for all Surface Navy Combat System

Objective Architecture

Platform Adaptation External Communications Domain Common Core

TDL Interface Controller CDL Interface Controller DDS Interface Controller SATCOM Router IBS Interface Controller Comms Domain Manager TACSIT Services

Display Domain

Training Training UniqueEnv Dev Dev Env GUIs

Vehicle Control Domain

Asset Launch/ Controller Recovery Module

Combat Mgmt Software

Training Training Common Dev Env Dev Env GUIs

Vehicle Domain Manager Vehicle Admin

Vehicle Coordinator Vehicle Weapon Coordinator

Vehicle Sensor Coordinator Vehicle Comms Coordinator

Asset Vehicle Controller Controller

Asset Vehicle Controller Interface

Work Services

HCI Services

Manning Services

Weapon Mgmt Domain

Weapon Domain Manager Mission Mission Area Mission Area Mission Coordinator Area Coordinator Area Coordinator Coordinator

Display Framework Services

Sensor Sensor Control Missile Control Controller (one per missile) Sensor Sensor Control Weapon Control Controller

Sensor Mgmt Domain

Sensor Tracker Sensor Domain Manager

Track Mgmt Domain

Track Server System Track Manager MultiSource Integrator Link Data Manager

Combat Control Domain

C2 Data Server

Weapon Scheduler

(one per weapon)

Sensor Sensor Control Sensor Control Controller (one per sensor)

Combat ID

Tactical Decision Support Tactical Decide & Assess

Tactical Mission Planning Ship Resource Manager

Support Domain

Knowledge Manager Training Dev Env

Readiness Assessment Logistics Support Combat System Trainer ASW Trainer EW Trainer Ship Control Trainer Computer Based Training

Sensor Sensor Sensor Sim/Stim Sim/Stim Simulator/ Stimulator

Geodetic Registration

ACB 14-22*

Sensor Command & Control Weapons Mgt.

Ship Control Domain

Ship Domain Manager Integ. Bridge / Voyage Mgmt

Composite Tracker

C2 Support Services

Weapon Weapon Simulator Weapon Simulator Simulator

Scenario Controller Planning Core

Device Monitors

Nav/Time Distribution Engineering Control Damage Control

Actuator Controllers

Infra. Resource Mgmt

Infrastructure Domain

Precision Nav/Time Network Mgmt Svc.

Weapon Weapon Simulator Ext. Comms Simulator Simulator

Business & Collaboration DX/DR Internal Comms

Distributed Computing Mediation Services Data Mgmt

Application Services Messaging Services Security Services

Data Collector After Action Reviewer Performance Analyzer

Nav System Simulator

Computing Env. Svc.

Computing Equipment Domain

Consoles

Displays

Cabinets

Processors

Storage

Networks

SSDS ACB 12

Coordinated interface (blue)

Display

Weapon Controller

Sensor SPY Command & Control C&D

Weapons Mgt. WCS Weapon Controller VLS

End State 100% Government Controlled Element and Component Level Interfaces

SSDS ACB 08

Sensor Weapons Mgt. Command & Control

Display ADS

Aegis ACB 12*

Government Controlled Element and Selected Component Level Interfaces

SPY

Display

WCS

Weapon Controller

Correlated Interface - Contractor described & controlled; not vetted through government coordination process Coordinated Interface - Government Controlled and Validated

*Number of components shown is limited for illustrative purposes. Refer to ADD or top level objective architecture for additional component decomposition

C&D VLS

Aegis ACB 08

ADS

Government Controlled Element Level Interfaces

Required warfighting capabilities determine components modified

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

Surface Navy Association Panel Discussion ­ 14 January 2010

12

Surface Combat System Top Level Architecture Phasing Common MH-60R Vehicle Control Components in ACB 14 Through ACB 16

Operational Command & Control GCCS, NECC, NCCT

Platform Adaptation External Communications Domain

Link 16 S TDL J JRE Link 11 Link 22 CDL-N DDS Interface Controller SATCOM Router Interface IBS Interface Controller TDL Interface Controller CDL Interface Controller Comms Domain Manager TACSIT Display Services GUI Display Services Audio/ Video Services

Display Domain

Platform Specific GUIs

Platform Specific Display Apps

Vehicle Control Domain

Vehicle Domain Manager Vehicle Sensor Coordinator Vehicle Comms Coordinator Asset Launch/ Controller Recovery Module

Common Core

Training Training Common Dev Env Dev Env GUIs Common Display Apps

Vehicle Coordinator Vehicle Weapon Coordinator

Vehicles Fixed Wing MH-60R Small Boats UAV UUV USV

Vehicle Scheduler

Asset MH-60R Controller Controller Missiles SM-2 SM-3 SM-6 ESSM RAM ASROC Weapons MK 41 VLS MK 57 VLS MK 29 GMLS RAM GMLS SeaRAM MK 160 AGS MK 160 GFCS CIGS CIWS TTWCS Harpoon MK 36 DLS Nulka SLQ-32 EA OTST ATT NIXIE NLOS

DDS

SIPRNET NIPRNET

External Comms Coordinator

Remote Display Controller

Operator Task Manager

Weapon Mgmt Domain

Weapon Domain Manager

IAMD Coordinator USW Coordinator SUW Coordinator Strike Coordinator

Sensor Sensor Control Missile Control Controller (one per missile) Sensor Sensor Control Weapon Control Controller

JTT / IBS

Display Renderer

Collaboration Manager

SPY-1 DBR AMDR SPQ-9B SPS-49A SPS-48E SPS-67 SPS-73 SPS-74 UPX-29 UPX-37 CIWS MK 9 SLQ-32 EDO ESM SEWIP EO/IR FLIR MH-60R Towed Sonar Hull Sonar

Sensor Mgmt Domain

Sensor Sensor Control Sensor Control Controller (one per sensor)

Sensor Domain Manager

Track Mgmt Domain

Track Server System Track Manager MultiSource Integrator Link Data Manager

Combat Control Domain

Engagement Scheduler

(one per weapon)

Above Water Sensor Coordinator Below Water Sensor Coordinator

Support Domain

Tactical Action Manager Decision Support Services Tactical Mission Planners Ship Resource Manager Readiness Assessor

Logistics Services Data Reduction

Combat Identification

Geodetic Registration

Training Domain

Knowledge Manager Training Dev Env Planning Core Data Collector After Action Reviewer Performance Analyzer

Scenario Controller Combat System Trainer ASW Trainer EW Trainer Ship Control Trainer Computer Based Training Sensor Sensor Sim/Stim MH-60R Sim/Stim Simulator

Navigation Domain

Bridge Interface Controller

Ship Movement Coordinator

MH-60R Radar/IFF Tracker

Composite Tracker

CC Support Services

Bridge System

Chart Server

GPS Inertial / Gyro Water Speed Log Depth Sounder Magnetic Compass METOC Sensors AIS

Infrastructure Component Domain

Framework SOA Core Services Computing Environment Computing Resource Mgr Distributed Objects

Weapon Weapon Simulator Weapon Simulator Simulator

ECDIS-N

C.S. Network Security

C.S. LAN Mgr

C.S. Interior Comms Data Extraction / Recording

Navigation Data Fuser

Precision Nav & Time Messaging Services

Data Mediation Services Data Mgmt

Weapon Weapon Simulator Ext. Comms Simulator Simulator

C.S Security/ Info Assur.

Nav System Simulator

Computing Equipment Domain

Consoles

Displays

Cabinets

Processors

Storage

Networks

Surface Navy Association Panel Discussion ­ 14 January 2010

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

13

Combat Systems Engineering Strategy Summary

Transitioning to network-based COTS computing environment which enables significant computing and warfighting improvements in current and future force Establishing a Combat System based on a common objective architecture with products applicable to multiple ship classes

­ Government owned architecture and authenticated interfaces

Conducting Combat System development through disciplined systems engineering principles and processes Future Surface Combat Systems will be created from existing and new development components

Surface Navy Association Panel Discussion ­ 14 January 2010

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

14

Back-up

Surface Navy Association Panel Discussion ­ 14 January 2010

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

15

Terms of Reference

Advanced Capability Build (ACB) ­ Software build for the combat system, delivered to a specific platform to integrate combat system elements. ACBs include:

­ Interface software for all platform specific elements ­ Combat Management System (CMS) ­ Other software integral to the overall core functions of the combat system

Technology Insertion (TI) ­ Replacement and/or upgrade of combat system hardware and associated middleware / firmware to take advantage of technology advances in hardware capability Rapid Capability Insertion Process (RCIP) ­ A process to provide faster transition of capability upgrades to the fleet

­ Introduced to the next 2-year ACB for integration, test, certification, and fielding

Common Source Library (CSL) ­ is an approach where the software for all ship classes within a combat system family (e.g., SSDS or Aegis) comes from a single source library. This allows new capability development investments to be applicable across those ships

Surface Navy Association Panel Discussion ­ 14 January 2010 Distribution Statement A: Approved for Public Release: Distribution is unlimited

16

Terms of Reference

Common Asset Library (CAL) ­ A library of objective architecture compliant common software components that can be integrated with other components to create advanced capability builds, including:

­ Requirements and design documentation ­ Models ­ Test procedures and results

Software-Hardware Asset Reuse Enterprise (SHARE) ­ A mechanism for discovering, accessing, sharing, managing, and sustaining reusable assets and associated metadata Note: the key distinction between SHARE and CAL is that SHARE is a repository of components deposited by SHARE participants while CAL status indicates that the specific component, has been selected and approved for reuse

Surface Navy Association Panel Discussion ­ 14 January 2010

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

17

Common Architecture Promotes Reuse, Reduced Testing, Fewer Baselines and Affordability

Present Carrier / Amphib Integration

CVN 78

SSDS Update

EW EW Integ. Integ. RAM/ RAM/ CIWS CIWS Control Control

Future

CVN78

ESSM ESSM (ICWI) (ICWI) EW EW Integ. Integ.

RAM/ RAM/ CIWS CIWS Control Control DBR DBR

DDG 1000 Integration

DDG 1000

Total Ship Total Ship Infrastructure Infrastructure C2 //Planning C2 Planning Services Services ESSM ESSM (ICWI) (ICWI) SM-2 SM-2 (ICWI) (ICWI) DBR DBR

CG(X) Integration / Future Surface Combatant

AMDR AMDR

Potential AMDR New Development

AMDR AMDR

NIFC-CA NIFC-CA USW USW Suite Suite

Sea-based Sea-based Terminal Terminal

IAMD IAMD

Aegis Integration

Track Track Server Server Infrastructure Infrastructure & Display & Display Services Services Weapon Weapon Mgmt Services Mgmt Services IAMD IAMD Merge Merge USW USW Suite Suite

Shared Components for Future Applications and Back Fit Built to Objective Architecture

Cruisers

Destroyers

NIFC-CA NIFC-CA

Sea-based Sea-based Terminal Terminal

New construction combat systems will utilize government specified architectures with GFE combat system elements and limited new development elements

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

Surface Navy Association Panel Discussion ­ 14 January 2010

18

Implementing Open Architecture:

Third-Party Surface Combat Systems Development

Current-Platform Based Development Future-Capability Based Development

Ship Builder Planning Yard

Many Vendors

SB

PY

PY ... Contracts

... Platform System

Engineering Agent (PSEA)

Separate

Prime Sys Integ

CS Integrator

Aegis Mk 7 SEWIP TTWCS

Ship Builder

CS Integrator

SSDS SEWIP CIWS

Ship Builder

CS Integrator

Other C&D Other ESM SUW

Common Asset Library

PSEA PSEA PSEA

External Comms Domain

Display Domain

Vehicle Control Domain Weapon Mgmt Domain

SQQ-89

ADDC ATC GUNS MIW UV Control

Sensor Mgmt Domain Ship Control Domain

Track Comm Mgmt Control Domain Domain

Support Domain Infrastructure Domain

Competition to develop Common S/W Components and Capabilities within Objective Architecture

Many Current Systems Have Their Own Sensor Control, Decide / Assess, Track Management, and Weapon Control Function

Decouple H/W from S/W

Systems Engineering Model Based on OA that:

Decouples hardware from software Utilizes standards-based interfaces to network Componentizes software applications Leverages advances made in commercial industry Enables competitive pressure to spark innovation

Middleware Operating System

Processing System (H/W) Display (H/W)

COTS Computing Systems H/W System Engineering & Component / Capability Competition

19

Surface Navy Association Panel Discussion ­ 14 January 2010

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

Advanced Capability Build / Technology Insertion

ACB / TI Notional Model

· Requires transition to COTS computing via initial TI · Each ACB builds on prior ACBs while adding new capabilities · Transitioned ships receive new ACB every 2 years · Every ship receives every other TI

FY 2012

Ship A

2014

2016

2018

2020

Hardware Refresh

2022

2024

2026

ACB 12 ACB 14 ACB 16 ACB 18

TI-12 COTS Hardware

ACB 20 ACB 22 ACB 24 ACB 26

TI-20 COTS Hardware Hardware Refresh

Ship B

ACB 16 ACB 18 ACB 20 ACB 22

TI-16 COTS Hardware

ACB 24 ACB 26

TI-24 COTS Hardware

ACB Definition

Aegis ACB 14

DDG 1000

CVN 78/ CVN 79

Aegis ACB 16 FSC

Objective Architecture Based Combat System

ACB 08

ACB 12

ACB 14

ACB 16

Executing

Defined / In Development

Being Defined

Future Work

PARM Programs Tech IWS 1.0 ­ 7.0 Insertion

Surface Navy Association Panel Discussion ­ 14 January 2010

S/W Maintenance

RCIP

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

?

...

20

Notional ACB Scoping and Development Process

CY09 FY09

CS Development Advanced Capability Build (ACB)

CY10 FY10

CY12 CY13 CY14 CY11 CY15 CY16 CY17 FY11 FY12 FY13 FY14 FY15 FY16 FY17

Develop ACB 12 Testing/Cert Field ACB 12

Develop ACB 14

Testing/Cert Develop ACB 16

Field ACB 14 Testing/Cert

ACB 14 Development

ACB Scoping Definition Study & System Engineering Requirements

Architecture, Requirements Specification (System, Element, Component), Interface Definition SSR/ CDR SRR SDR PDR 2 6 Early Code

Cut in Decision

TRR DEMO MRA 8 9 3

CSSQT 7 9 Final 2 Cert ACB 14 Backfit

3

3

Software Code Integration & Test

Cut in Decision Cut in Decision

In Process

Component Development

N86

SWTRG

ACB 14 CDR 'S Intent Ltr

Establish PORs for ACB 14 First Cut In Decision ­ New POR Development Scope ACB 14 / Create Execution Letter and Requirements Plan Second Cut In Decision ­ Integrate Existing C/S Elements

Final ACB 14 Cut in Decision

Final Cut In Decision ­ RCIP Components

PEO IWS

Translate CDR' CDR'S Intent

ACB 14 Development

ACB 14 In-Service Support

· Requirements Development · Product Line System Engineering Integration · Cost Estimating · PARM Alignment · Long Range HW Design & Build · Coordination with N86

Deliver H/W Lead Ship SI&T ACB 14 CSSQT ACB 14 Final Cert SI&T Backfit ACB 14

9

2

Surface Navy Association Panel Discussion ­ 14 January 2010

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

21

Implementing Open Architecture:

Surface Navy OA Technical Model

Infrastructure:

· Common Services and APIs · Flexibility to Support Forward-Fit and Back-Fit

Track Mgmt Display

Command & Control

Componentized Objective Architecture:

Sensor Mgmt Weapon Mgmt Vehicle Control

· Common Reusable Components · Platform Specific Components · Data Model · Extensible to the Future

Common Computing Environment:

· Standards-based Interfaces to network · Commercial Mainstream Products and Technologies

Middleware

Decouple Hardware (H/W) from Software (S/W)

Operating System

Hardware

Upgrade H/W and S/W Independently and on Different Refresh Intervals

Surface Navy Association Panel Discussion ­ 14 January 2010 Distribution Statement A: Approved for Public Release: Distribution is unlimited

22

Information

Sustaining Today's Force Structure and Building the Future Force

22 pages

Find more like this

Report File (DMCA)

Our content is added by our users. We aim to remove reported files within 1 working day. Please use this link to notify us:

Report this file as copyright or inappropriate

820628


You might also be interested in

BETA