PEOC4I.NAVY.MIL

Program Executive Office Command, Control, Communications, Computers and Intelligence (PEO C4I)

Statement A: Approved for public release, distribution is unlimited. (21 October 2016)

Integrated Information Warfare for the

21st Century

Strategic Management of C4I Capability Baselines to Achieve Cost and Schedule Efficiencies

October 2016 CAPT William W. DeBow Major Program Manager,

PMW 760 william.debow@navy.mil

619.524.7279

Alignment of PEO C4I Baselines with Strategic Priorities

• CNO Tenet: Strengthen Naval Power At and From Sea Maintain a fleet that is trained and ready to operate and fight decisively Further advance and ingrain information warfare. Expand the

Electromagnetic Maneuver concept to encompass all of information warfare, to include space and cyberspace

Explore alternative fleet designs. This effort will include exploring new naval platforms and formations – again in a highly “informationalized” environment

• CNSF: “Distributed lethality” is about Increasing offensive power Defensive hardening of individual ships Employing the ships “in a more

distributed manner • Strike Group Interoperability • Cyber Secure / CYBERSAFE

Environment

2

SPAWAR / PEO C4I Strategic Alignment

• PMW 760’s C4I Builds and Baselines effort: Provides the design, integration, testing, configuration management and

training / ILS support for end-to-end modernized capabilities

3

SPAWAR End State

ONE Accelerate and Streamline Delivery

PEO C4I GOAL

ONE Increase warfighting readiness through

the improved development, testing,

deployment, sustainment of, and training

of C4I capabilities

PEO C4I OBJECTIVE

1.3 Deliver integrated, tested, and supported

baselines for new and modernized capabilities

SPAWAR OBJECTIVE

1. A Increase Commonality in Deployed C4I

Configurations

Reducing Variance, Increasing Cost Efficiencies & Improving Readiness of Deployed Capabilities

C4I Baselines Design and Integration “Wholeness” Efforts

• PMW 760 will instill System of Systems (SoS) engineering, testing, training, ILS and Configuration Management rigor into delivery of C4I Baselines

• SoS Systems Engineering Benefits Reduced installation time and cost Validated capability ISO integrated systems

(e.g., combat systems) Reduced variance in fielded baselines Integrated and repeatable end-to-end tests Timely and relevant end-to-end training Increased Fleet reputation

• CSRR is the PEO C4I model for Platform PMW systems integration • PEO IWS’s Advanced Capability Build (ACB) delivery is the model for AMOD

(BL 9C.2) and AEGIS Ashore • PMW 760 utilizing CSRR / ACB concepts for Platform C4I Design & Integration • Pursuing Combat Systems engineering expertise to deliver C5I integrated

solutions – IWS and MDA 4

C4I Capability Baseline Target

Class Date

DDG Baseline 1.0 DDG Class FY18

CG Baseline 1.0 CG Class FY18

LPD Baseline 1.0 LPD Class FY18

LSD Baseline 1.0 LSD Class FY18

FF Baseline 1.0 FF 33 Class (NEWCON)

FY22*

* GFE Delivery In-Line to NEWCON

PEO C4I Organizational Structure

5

Chief of Staff – CAPT Kyle Turco Executive Assistant – Gary Galloway DPEO Acquisition Management – John Metzger DPEO Manpower & Budget – Lisa Ramsey DPEO Plans & Strategy – Suzanne Arney DPEO Platform Integration & Modernization – Jerry Nies DPEO Technical Direction & Program Integration – Bob Parker

APEO Installations (FRD) – Cheryl Carlton APEO Logistics (4.0) – Sean Zion APEO Engineering (5.0) – Nic Bergeron APEO S&T (7.0) – Rafe Pei

SPAWAR Space Field Activity

SSC Pacific

SSC Atlantic

CURRENT READINESS REPORTING

PEO C4I RDML C. D. Becker

SPAWAR RADM David Lewis

ASN(RDA) Assistant Secretary of the Navy

(Research, Development & Acquisition)

CNO Chief of Naval Operations

Updated 13 April 2015

Shore & Expeditionary Integration PMW 790

Les Hubbard CDR Ken Ebert

International C4I Integration PMW 740

Sean Moone Rob Cerwonka (Acting)

Carrier and Air Integration PMW 750

CAPT Andy Gibbons CAPT Robert Cassol

Ship Integration PMW 760

CAPT William DeBow David Rodriguez

Undersea Integration PMW 770

CAPT Edward Anderson Mark Mukanos

Command and Control PMW 150

CAPT Allan Walters Mark Compton

Tactical Networks PMW 160

CAPT William “Ben” McNeal Jim Churchill

Communications PMW/A 170

CAPT Mark Glover Dan Brothers

Information Assurance & Cyber Security

PMW 130

Steve Bullard Rob Diaz

Battlespace Awareness & Information

Operations PMW 120

CAPT Mark Kempf Susie Hartzog

EXECUTIVE DIRECTOR John Pope

SPAWAR ED Mr. Pat Sullivan

SPAWAR 5.0-RDML Fritzemeier

SPAWAR FRD - RDML Ailes

PMW 760 Overview Ship Integration Program Office

• New Construction (NEWCON) C4I Participating Acquisition Resource

Manager (PARM) for C4I to PEO Ships, PEO LCS, and MDA

Deliver integrated and tested PEO C4I portfolio as part of overall ship acquisition

• Modernization (MOD) C4I Plan C4I alteration installs into CNO

and other avails Integrate into NAVSEA “One Book”

modernization planning efforts Act as a source for Platform C4I

Baseline Configuration Management

Transition planned alterations to SPAWAR Fleet Readiness Directorate (FRD) for installation

6

NEWCON: Plan, Integrate & Test as part of a C4I suite

MOD: Plan and mature individual

alterations within Navy Modernization Plan (NMP)

Strategic Management of C4I Capability Proposal

7

Business Efficiencies from Reduced Variation

• Better reliability, operational availability • More thorough testing of fewer combinations of systems • Better training of end to end capability • Combined training pipelines, NEC / Training Cert reduction • More manning flexibility – ships are more alike, skills

transfer from ship to ship better • Efficiencies in logistic products – parts, manuals, etc.

Reliably deliver Capability to the Fleet

Study Team / CNA

Evaluate and validate efficiencies

Capstone C4I Requirements

Establish C4I Builds linked to Capstone

Requirements

Consistently fund and field full builds

+

Magnitude of the Challenge

CSRR Program • System of Systems (SoS) POR &

funding • Integrated end-to-end process

(NEWCON and MOD) Requirements, Design, Integration,

Test process 2 year block upgrade cycle

• CSRR Technical Direction Authority (TDA) and Design Agent through NUWC NPT Land based integration and testing Common logistics Common training (Multiple

Reconfigurable Training System [MRTS])

Configuration Management (by class) Class drawings vs. hull drawings

CRR / Surface Programs • System / Product level designs • No C4I “integration” funding resources • Separate MOD process (NMP) and

NEWCON process • No single Design Agent

No end-to-end land based integration and test for MOD

– NEWCON does incorporate a radio room (not network) integration and test effort

No SoS T&E plan for MOD System-level hull drawings vice Class

drawings No SoS ILS support plan

– Non-integrated (system-level) training Manning requirements assume non-

integrated operations & maintenance for each system

8

Capability Baseline Design, Integration & CM Strategy

• C4I HW / SW Variants • C4I Test Pedigrees • C4I Dependencies Technical / Install / Other

• RTA – Platform – System Trace

Platform Baseline CM

• POM / C4I CBs • Variance and Platform

Wholeness Metrics • Reference Target

Architectures (RTAs) Platform RTAs

• DoD Funct Implement Arch (DFIA) (CYBER)

• CBR – Initial (CBR-I)

• C4I CB Elements FID Elements

• Platform Arch As Is Arch / FID To Be Arch / FID

• Platform ECR Stage 1 • CBR – Design (CBR-D) • Dependencies Interoperability Install

• Training Planning

Advanced Planning

Prior to A-36 A-30 A-20 A-10 A-9 A-4 A-0 A+

• CBR – Readiness (CBR-R) • Platform BL Pre-Install

Testing (e.g. E2C) w/ Report Event Management

Plans C4I CB-based (e.g.,

BMD 5.1)

C4I Capability Baseline Design, Integration and CM Strategy

SIDs

CBR – Initial CBR – Design

ILS Cert Platform BL

Stage I Platform BL

Stage II A-9 Transition

System IRD Required

Install SOW Finalized Global install Contract

Integration Testing (E2C, et al.)

• SPEG-Compliant System SOVTs

• System of Systems (SoS) Test Plan / Procedures

• Platform Test Arch As Is Arch To Be Arch

• Technical and Install Dependencies

• QRGs and Tech Aids

Platform BL Stage III

SOVTs SOT

CBR – Readiness

• C4I System SOVTs • Integrated Platform C4I SOVT / SOT • Total Ship Interop Test w/ C4I • C4I SoS Training • SoS ILS Capability QRGs and Tech Aids

WSIA (SPAWAR C4I Authorization) WSCRR D-3: WSCD

(SPAWAR C4I Certification)

TSCIT E2C Event Start

CB – Capability Build CBR – C4I Capability Build Review QRG – Quick Reference Guide WSCD – Warfare Systems Certification Decision WSCRR – Warfare Systems Certification Readiness Review WSIA – Warfare Systems Installation Authorization D-3: 3 Months prior to Deployment

NWSCP Certification

Capability Testing

Design Integration

Integration Documentation

Delivery / Support / Training

9

BMD 5.1 C4I Baseline “Cradle to Grave” Concepts

Requirements

Design

Implementation

Integration, Test & Verification

System Verification & Validation

Open Architecture Feature Data Exchange

Threat Set

Black Core

New Capabilities (i.e., Engage On Remote)

Ascent Phase Operations

C4I Top Level Requirements

A-Specification

Element Capability Specification

BMD System Specification

Functional Block Diagrams

C4I Target Baseline

Systems Engineer Tech Review (SETR) Platform Technical Review Board (PTRB) Local Configuration Control Board (LCCB)

In-Process Review (IPR)

Installation System Operational Verification (SOVT) Systems Operability Test (SOT) Total Ship C5I Interoperability Test (TSCIT)

Concept White Papers

BMDS Communications Specification

BMDS Interface Control Documents

MTJ Quick Reference Guide SAILOR Help Desk ISEA Tech Assists

C4I Top Level Design Document

Operations & Maint Navy Capabilities Document (NCD)

C4I Certification Configuration Management

Systems Engineer Tech Review (SETR) Platform Technical Review Board (PTRB) Local Configuration Control Board (LCCB) C4I Certification Element level testing E2C Testing AEGIS Integration Events (AIE)

ILS; Tech Manuals MRCs, CSOSS Training Configuration Mgmt

Verification & Validation

10

Interface Design Specifications

C4I Capstone Requirements Will Drive C4I Baselines

11

Communications

Narrowband

Wideband

Protected

Broadcast

Tactical Data Links

Tactical Comms

FY18-19 DDG Objective Platform Class Baseline (OPCB)

Mission Areas

AAW ASW SUW BMD STW NCO

l l l l l l

l l l l l l

l l l l l l

Flight-I

Flight-II

Flight-IIA

Mission Functional Decomposition

Networks

Terrestrial Transport/Backhaul Network WAN Gateway Networks Afloat Networks Afloat Management Communications Circuit Management Terrestrial Transport/Backhaul

Application Services

Business Apps

Logistics Organizational Messaging Strategic Messaging Intelligence Surveillance and Reconnaissance Information Operations Environmental

Maritime C2 Navy Air Operations Command and Control (NAOC2)

Common Services

Computing Systems Management Data Management Position Navigation and Timing Visualization Communications Services (Voice) Core Services (Tactical Edge)

Information Assurance

Cross Domain Solutions (CDS) Integrity/non-Repudiation (INR) Computer Network Defense (CND) High Availability Enterprise (HAE) Confidentiality and Encryption

Functions

Functional Allocation

Tactical C2 (TDL) Performance

Requirements & Data Exchanges

Navy Technical Reference Model (NTRM)

Baselines Represented are Notional

Taci

tal D

ata

Link

s

Networks Afloat

Network WAN Gateway

Protected Comms

Confidentiality & Encryption

Maritime C2 (CDLMS)

Tactical Comms

Tactical Data Links

Cyb

er S

ecur

e N

etw

orks

Networks Afloat

Network WAN Gateway

Protected Comms

Confidentiality & Encryption

Maritime C2 (MTC2)

I/O a

nd IS

R

Signals Explotation

Confidentiality & Encryption

Navigation

Intelligence Processing

Testable Sequences / Threads (E2C Lab)

C4I Capability Builds supporting Flt I BMD Mission

FY18 / 19 DDG Flight 1 Target Builds

12

Baselines Methodology End-to-End Mission Mapping to Architecture

Architecture

•The mission threads are from the classified ExAMS database. •The systems functions are decomposed from the mission threads. •Map the system functions to test sequences. •The test sequences define the systems. •The platform architecture characterizes integration of systems on the platform.

Consumers - Activities • APM-Es - E2C • FRD / C4I – SOT • NAVIDFOR – CSI • Ship’s Force – M&C

Persistent CM for Platform C4I Baselines: Background

• Problem Statement(s): CM: Relentless change to hardware and software elements, virtual

machine configurations and services settings makes it nearly impossible to manage a platform’s “near real-time” baseline.

– Holding ships accountable for remaining “in baseline” mandates a tool that quickly and accurately answers:

1) “What is my real-time platform baseline configuration?” 2) “How is my current baseline different from the originally installed and tested baseline?”

Cyber: Inability to rapidly and accurately identify the Platform C4I Baseline makes assessments against vulnerabilities nearly impossible

– Maintaining a platform as-tested and certified Platform C4I CM baseline is the critical foundation for rigorous cyber initiatives

• Effort PMW 760 is leveraging existing funding for PCM Phase I development

and demonstration in 2016/2017 13

Persistent CM For Platform C4I Baselines:

Concept of Operations FLEET DEPLOYED CONOPS (FY18 END-STATE)

14

CANES

ADNS

GCCS-M

AVAIL START

A-0 HACSIM SOVT

DGSIT

SOT

INT/TEST

10wks

SoS TEST

1wk

C5I TEST

PRODUCTION

AVAIL END

OPERATIONAL CAPABILITY

IMPACT OPERATIONAL CAPABILITY

SUPPORT REQUEST

DEPLOYMENT

LOSS OF

OPERATIONAL CAPABILITY

OPERATIONAL CAPABILITY RESTORED

REVERT TO BASELINE

CYBER SECURE BASELINE

BLx PBL1 Platform Baseline (PBL)

PBL2

LCCB

Stage 1 2 3

SPAWAR 5.9 CERT

PBL3

IAVA 1=>n

PBL3

Denotes Automatic Platform Baseline Audit Opportunity

IAVA PBL

DELTAS*

A-12

* PMW-760 tracked via PPCM output reports

DDG Variance Reduction Measurement

15 Migrating to Common, Modern Baselines (Large Green Boxes)

8-System Analysis • Network • ADNS • GCCS-M • EHF • SHF • GBS • COMSAT • ISR (e.g., SSEE)

Total # of in-service ships in a given year

Color reflects

C4I Score range

Box size reflects # of hulls in common config.

C4I Score Measures the “modernity” of a hull’s configuration on a 4-point scale

PMW 760 Contract Laydown

Contract Awarded Scope Small Business Impact

Ship Integration Program Office (PMW 760) Program Management & System Engineering

Dec 2011 5 year PoP

• Program / Project Management • Acquisition • Systems Engineering • Contract Management • Logistics • Administrative Support

Large Business Prime; Small Business Targets

AEGIS BMD & AEGIS Ashore Systems Engineering Navy Modernization / Execution (Design Center)

July 2016 5 year PoP

• Systems Engineering • Program Management • Configuration Management • Logistics • Modernization/Execution (Design Center) • Integration/ SoS Testing and Training

Small Business Prime

Enterprise Platform Integration Contract (EPIC)

Feb 2008 8 year PoP

• Integration • Engineering • Configuration Management • Procurement • Fabrication / Assembly • Test / Inspection • Installation (New Construction)

Large Business Prime; Small Business Targets

C4I Testing, Integration, and Installation (CTII) Contract

Sep 2014 5 year PoP

• Same as EPIC; follow-on Large Business Prime; Small Business Targets

16

C4I System of Systems Baseline Navy/Fleet Benefits

• Supports CNO Tenet: Strengthen Naval Power At and From Sea, CNSF Distributed Lethality Concept and Strike Group Interoperability

• Fleet Benefits Validated capability ISO external integrated systems (e.g., IWS) Move from C4I to C5I approach Increase Cost Efficiencies

– CM rigor - Reduced variance in C4I suite – End-to-end testing and evaluation – Relevant end-to-end training – Reduced installation time

• C4I Builds better link material solutions to delivery of overall C4I capability Deliver end to end solutions Capstone requirements would help rigorously link systems to overall C4I capability

• C4I Builds reduce variance by Platform Variance reduction requires consistently fielding complete builds over a period of time Efficiencies that support a business case for change derive largely from variance reduction

• Engineering design and integration efforts maintain internal and external System of Systems alignments

17 Support and Defend the Constitution…

Visit us at www.peoc4i.navy.mil

We Deliver Information Warfare Capabilities to the

Fleet.

18