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

Maritime C2 Strategy An Innovative Approach to System Transformation

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

22 June 2010 Patrick Garcia Technical Director Command and Control Systems (PMW-150) 619.307.9167 [email protected]

Maritime C2 Strategy Agenda

• PMW 150 Introduction • Current Maritime C2 Situation • Strategy Objectives  Mission Management Capabilities  Net-Centric Operations Transition  Software Acquisition Process Changes

• Summary 2

PMW 150 Organization Program Program Manager Manager

Civilian Civilian––15 15 Military – 13 Military – 13

CAPT CAPT Steve Steve McPhillips McPhillips Deputy Deputy Program Program Manager Manager CAPT CAPT D.A. D.A. LeGoff LeGoff

Programmatic

Maritime C2 PAPM CDR PAT MACK

Support SupportC2 C2 PAPM PAPM KEVIN KEVINALLEN ALLEN

Tactical TacticalC2 C2 PAPM PAPM PAUL PAULBOBROWICH BOBROWICH

NILE NILE PAPM PAPM MANUEL MANUELGOMEZ GOMEZ

Defensive DefensiveC2 C2 PAPM PAPM SCOTT SCOTT WHITE WHITE

GCCS-M GCCS-J

NTCSS (with OOMA)

C2P ADSI LINK-16 LINK-11

NATO Improved Link Eleven

JWARN JEM

Functional Acquisition Acquisition Manager Manager DAVE DAVENORD NORD

Business BusinessFinancial Financial Manager Manager(4) (4) DR. DR.MIKE MIKENAKADA NAKADA

Technical Director PAT GARCIA

Director Directorof of Operations Operations CINDY CINDYTAYLOR TAYLOR

APM APM(E) (E) 33EMBEDDED EMBEDDED

APM APM(C) (C) 11EMBEDDED EMBEDDED

APM APM(L) (L) 44EMBEDDED EMBEDDED

Transforming operational needs into effective and affordable Command and Control capabilities for Navy, Marine Corps, Joint and Coalition warfighters. The pre-eminent authority and provider of choice for Command and Control capability.

3

PMW 150 Program Portfolio Other Programs and Projects

Active ACAT Programs Maritime C2 • Global Command and Control SystemMaritime (GCCS-M) •

ACAT IAC

Tactical C2 • Link-16 Network •

•

ACAT II

Support C2 • Naval Tactical Command Support System (NTCSS) •

•

ACAT III

Joint Effects Model (JEM) •

•

ACAT III

FY12 proposed new start

Global-Theater Security Cooperation Management Information System (GTSCMIS) •

Pending assignment to PEO C4I

• Joint Command and Control Portfolio Tactical C2 • Air Defense System Integrator (ADSI) • Link 22 •

POM 12 issue

Support C2 • Maintenance Figure of Merit (MFOM) •

ACAT IAC

Defensive C2 • Joint Warning and Reporting Network (JWARN) •

•

ACAT II

Command and Control Processor (NGC2P) •

Maritime C2 • GCCS-J – DISA ACAT IAM • Maritime Tactical Command & Control (MTC2)

•

Transition from USFF N43 01OCT10

Bar Code Supply Logistics Maintenance Automated Information System (BCS LMAIS) •

Assume responsibility 01OCT10

Technical Director • Command and Control Rapid Prototype Continuum (C2RPC) •

ONR funded initiative

NATO Improved Link Eleven (NILE) 4

Navy GCCS-M Force Structure As of 19 MAR 2010

CONUS Sites (20 qty) USJFCOM COMUSNAVSO / C4F COMNAVSPECWARGRU2 COMNAVSPECWARGRU4 COMEXSTRIKGRU2 COMSOCJFCOM COMNAVFACENGCOM NOLSC CBC COMEXSTRIKGRU3 NFELC COMFIRSTNCD CNO Alt Navy CMD Center USFF COMTHIRDFLT COMSECONDFLT COMNAVSPECWARCOM-West COMSUBFOR COMSUBRON-11

OCONUS Sites (14 qty) USFJ USPACOM COMNAVFORJAPAN COMEXSTRIKGRU7 CTF-72 CTF-73 / COMLOG WESTPAC PA-RSC COMPACFLT COMUSNAVCENT/C5F COMUSNAVEUR / COMSUBGRU 8 CTF74 / COMSUBGRU 7 COMSUBPAC CTF-34 COMSUBGRU 8 Rep

Training Sites (8 qty)

CVN

SWOSCOLCOM CSCS U Dam Neck CID LS Dam Neck NMITC FLEASWTRACEN CID LS San Diego FITCPAC NSAWC Fallon

11

LHD

8

LHA

2

LCC

22 Force Level

1*

0

3

CG

68 Submarines

84 Group Level

5

0

10

20

30

• • • • *

GCCS-M systems installed; does not account for SCN Hulls Sites in purple have Navy installed GCCS-J systems Sites in blue have Navy installed GCCS-M/GCCS-J systems Sites in black have Navy installed GCCS-M systems LCC19 has GCCS-J 4.1.0.4 GENSER, GCCS-M 4.0.1.2 SCIC

5

40

50

FFG

60

70

30

MCM

4 SSGNs

12

57

DDG

50 SSNs 14 SSBNs

9

22

LPD-17

10 Allied/Coalition Partners

6

14

LPD 4/LSD

16

LCS

2

75 Unit Level

13

PC 0

10

20

30

405

5

Maritime C2 Strategy Agenda

• PMW 150 Introduction • Current Maritime C2 Situation • Strategy Objectives

 Mission Management Capabilities  Net-Centric Operations Transition  Software Acquisition Process Changes

• Summary

Maritime C2 Situation: Where are we now?

POR Programs t support most WP 5-01 or 3-32 tenets.

Commander’s Intent Daily Intentions

Request for Forces (Redeployment)

Maintain alignment

Adjust apportionment

C2 Today: “Tracks and Maps” Current Ops (Comms, COP, Intel) Provide SA

NWP 3-32 Maritime Warfare at Operational Level of War

WP 5-01 Planning

Counter the Enemy

Goal is to address the tenets of Maritime Operations at the OLW

Advance the plan

Define Future Ops (Intel, Mission Planning)

Comply with procedure Rules of Engagement

Mission Execution (Tasks & Plans)

Synchronizing the World of Maritime C2

C2 Objective

CPF, JTF, JFMCC MOC “What is this unit tasked to do? Against what target?”

Plans/ Tasks COP Log COP

How are his tasks synchronized with his Force tasking?

NetOps COP

Are there any readiness, Logistics, NetCOP, METOC, or Task Sync conflicts? What is the task status & mission effects status? Are there alternate resources that could be assigned?

Situation Situation Awareness Awareness

Centralized Guidance Federated Execution Shared SA for Synchronization

Advance Advance the the Plan Plan

Comply Comply with with Procedures Procedures

Counter Counter the the Enemy Enemy

Adjust Adjust Apportionment Apportionment

Commander’s Control Measures

Maintain Maintain Alignment Alignment

•

•

•

Maritime C2 Strategy Objectives Provide Expanded Mission Management Capabilities  Add “What”, “When”, “Why”, and “How” to currently provided “Who” and “Where” information  Needed to fulfill NWP 3-32 and NWP 50-1* requirements

Transition from Stove-Pipe Solutions to Net-Centric Operations  Implement “component portfolio” approach to C2 system development  Use rapid prototyping and technology insertion to speed change and engage warfighter

Establish Government Management and Governance of IT Software Acquisition Processes  Implement agile IT acquisition and Test & Evaluation (T&E) processes “modeled on successful commercial practices for the rapid acquisition and continuous upgrades and improvement of IT systems.” (National Defense Acquisition Act of FY2010)  Execute agile performance-based contracting strategy by reducing vendor’s “Institutional Knowledge Lock”  Synchronize Government testing with private-industry development – testing early and often

M

a r i t i m

e

C

2

S

t r a t e g

y

Agenda

• PMW 150 Introduction • Current Maritime C2 Situation • Strategy Objectives

 Mission Management Capabilities  Net-Centric Operations Transition  Software Acquisition Process Changes

• Summary

Pillars of Future C2 system Intelligence & CM • GCCS- I3 • Analysis products & IPOE • Red Force Service - Units/Sites & Capabilities - Enemy COAs - NAI Characteristics - Targets • Info Req’s • Collection Req’s

Planning, xecution, Assessment

Plans/Tasks Data Service Unit tasking & task status Authoritative plans data Planning Mission management Decision Points, LOO CMD relationships, COA sketch Execution Synchronization

ISR Data Fusion • Conditions of Interest Alerts - Area entry - Task execution deviations - (others TBD) • OTM (new track mgr) • Associate GCCS- I3 info w/ OTM reporting

Capabilities & Readiness • Blue Force Service - Units data (Admin,Op) - Platf’s/Systems Capab - Networks Config • Readiness COP - Platforms/Systems Status - NetOps Status • Capabilities • Conditions of Interest Heuristics & Alerts - Plan/Task readiness

Establish C2 Relationships and Strategy for Deployment of Capabilities National & Theater Intelligence

time rations ters CCIRs, PIRs Decision info rqts (DSTs) Trks of interest Measures of effects

Confirm Red OOB/COAs Decision-focused triggers Hi interest track info MOE/BDA indicators

ISR/IO TODAY: TRACKS ONLY

Request Sensor status Provide trks of interests Provide NERF/EPL data Cue target locs & info

sion and tasking mmanders Intent sion assessment planning

t/Coalition/ p/One down

Y: TRACKS ONLY

Command & Control

 Monitoring and Assessment  Direction and Coordination

)

oups,

TODAY: TRACKS ONLY Sensor status trks of interests Request NERF/EPL data Target prosecution status

sking & Coordination asures of performance sk progress -planning effects COA/Plan readiness Capability readiness data Systems/Aircraft status Logistics status data

Combat Systems

Request COA readiness Rqst unit/capab readiness Rqst Systems/Aircraft status Request logistics data

Combat Support TODAY: NO COLLABORATION

Support

Unifying Maritime Missions into a Navy Mission Planner View Maritime Missions Ballistic Missile Defense Maritime Interdiction Operations (MIO) • Law Enforcement Operations • Visit, Board, Search and Seizure • Blockade UnderSea Warfare (USW) Anti-Surface Warfare (ASUW) • Anti-Submarine Warfare (ASW) Mine Warfare (MIW) • Mine Hunting • Mine Clearance • Offensive Mining Amphibious Operations Strike Operations Cruise missile • Manned Aircraft • Naval Fires Humanitarian Assistance / Disaster Relief (HA/DR) • Non-combatant Evacuation Operations (NEO) Protection of Shipping at Sea / Freedom of Navigation

Maritime Planning & OLW Execution HHQ, Joint, Coalition

JFMCC MOC

Plan (NPP, JOPP)

Align CDR’s DIRECT Intent MONITOR ISR

Prioritize targets & resources

Synchronize timeline

Advance the Plan

Assess (MOEs, MOPs)

TF/TG CDR

tasks

task status

Subordinate Units,

Maritime C2 Strategy Agenda

• PMW 150 Introduction • Current Maritime C2 Situation • Strategy Objectives

 Mission Management Capabilities  Net-Centric Operations Transition  Software Acquisition Process Changes

• Summary

Maritime C2 Program of Record Migration FY10

FY12

C

JC2C/MTC2

GCCS-M

GCCS-M MOC

3.X.X

MOC 4.1 (FORCE)

CE

4.0.1

FORCE

UP

4.0.2

GROUP

T

4.0.3

TODAY

GCCS-M provides a robust ational Awareness of Who and Where across the Wide Area Network

UNIT

JC2C

MTC2

FORCE 4.0.3 4.1 (TACT)

NEAR TERM

GROUP MTC2 UNIT

FYDP MTC2 will address “Who, What, When, Where, Why, How” in Mission Management Planning, Assessment, and Monitoring tools

ew Start Maritime Tactical C2 (MTC2) Program will deliver required new capabilities which will not be addressed in any Joint C2 Program

C2 Rapid Prototyping Continuum (C2RPC) Origins

Coalition of PEO C4I, Office of Naval Research, and COMPACFLT  Accelerate development of Operational Level of Warfare (OLW) C2/ISR mission applications  COMPACFLT: “Use COMPACFLT as a “Petri Dish”  Advance the state of the art of C2 (and CS)  Reduce uncertainty and increase OPTEMPO  Ensure systems meet fleet prioritized requirements

 Develop a MOC prototype that feeds back into enduring, supported programs of record

PEO-C4I Approach (Three 2-year spirals of incremental Planning, Execution, & Assessment Capabilities)

ntain nment

Real time, crossDomain tasking & assessment

djust ortionment

unter Enemy

ply with cedure

C 2 R P C

Improved mission Area COA analysis & Execution Assessment

Basic Maritime planning & Execution Monitoring

vance e Plan

ovide SA

Feeder Technologies FY10-11

2012

2014

2016

Capabilities & Readiness

Planning & Execution

Intel & CM

ISR Data Fusion

C2RPC New Capabilities

Apps support Data Mgmt

Enterprise Services

• TBD • ISR mgt to plan rqts • CM/CCIRs link to decision points • OTM • R/W/B Data Services • R/W objects in COP • IPOE assoc w/plan • Plan/task assoc w/units & resources • Shore MOCs COA & decision support tools • CPF readiness pilot hardened (plan heuristics & data feeds) • Study & Initial shore capability (AIF study) • IR COP, UFS,

• Targeting • CCIR tracking vs decisions • IMA • MOC & below (TG) distributed planning/exec’n (DIL environmt) • Core plan tool • Addnl’ mission area heuristics & threat sit’ns • Org (GFM) C&M linked to planning (& data fill) • Initial shore/ ship capability (TBD by study) • Collaborative

• CS track/plans /readiness/I&W/ status data exch • TBD w/PMW120 • Mission & asset status/avail

• TBD w/PMW120 • Joint planning/ APEX (complete legacy migration)

• Integrated mission mgmt w/distributed legacy systems

• Ship level tactical plan execution monitoring & feedback • Task direction via IP TADIL

• Tactical assets readiness in decision making • TG planning tools

• Continuous readiness assessment for real time decisions

• Fully functional Distrib data svc

•Full-up AIF (apps support & ES abstract’n

• CS-interface to enable mission mgmt

• ROW C2 v2

ISR Data Fusion

C2RPC 2011 Capabilities

Capabilities & Readiness

Planning & Execution

Intel & CM

Implemented

Apps support Data Mgmt

Enterprise Services

• OTM

• R/W objects in IR COP

• Plan/task demo of assoc w/units & resources

• CPF readiness pilot (OPLAN readiness for apportion’d ships) • AMCRs, OIS, TRMS,MFOM • LogCOP • NetOps COP • IR COP, selected data

• Red force svc on IR COP halo • Track mgmt widgets – initial capability • Red force svc (I3 objects in OTM COP) • IPOE assoc w/plan • Task Navigator (task drill-down PTDS fm IR COP) • Decision Point, SOP & Cmd Relationships • CPF readiness pilot (Priority missions readiness) initial integr’n w/PTDS • OPREP-5, BMD and ASW plan readiness) • Blue capab/orgs • UFS APIs & WebTop

• White force svc • Blue force mov’t (WebSked), Environmental conditions/Wx • Targets • IPOE integr’n with Maritime COA Sketch • COA sketch, Line of Ops tools first look • COA collaboration

• Blue force mov’t (OTSR) • OTM link tracks & acoustic trks • Initial link of CCIRs to plan & decis points • Maritime COA Sketch/LOO & Decision Pts Integrat’d capab • Ops Sync tool (Sync Matrix) • Distributed planning among MOCs, TFs,& TGs

• Additional readiness heuristics • Additional mission areas

• Readiness integrated with planning processes & tools

• Collaborative COP initial capability • AIF prototype

• Initial AIF capability (ashore, afloat) • UFS process workflow support

Joint Combat Systems (CS)/C2 Limited Technology Experiment (LTE)

Office of Naval Research effort, with PEO C4I and PEO S cooperation to exchange of real-time and near-reale tracks and other data to and from CS and C2 systems

Initial experimentation phase will focus on CS publishing ASW tracks, tactical readiness and video – September ’10

Next experimentation event scheduled for June ’11

Future C2 Program Evolution Venues of Prototyping, Experimentation, & Hardening 2012

2014

2016

MOC ONR-funded prototyping

TF/TG Unit

Drop 3

MTC2

OT &E

S&T INTEGRATION and TRANSITION to POR

Expand and harden capabilities for MOC and below C2 on Navy GCCS-M platforms & sites

GCCS-M

&E DT

&E DT

PMW-150 architecture

OT &E

Drop 2

OT &E

Drop 1

&E DT

ritime C2 POR igration

2011

Nov 2010

&E DT

C2 hnology ertion tiative C2TII)

AUG 2010

OT &E

Rapid totype tinuum RPC)

MAR 2010

Maritime C2 Strategy Agenda

• PMW 150 Introduction • Current Maritime C2 Situation • Strategy Objectives

 Mission Management Capabilities  Net-Centric Operations Transition  Software Acquisition Process Changes

• Summary

Maritime C2 Acquisition Issues

oor Government – Industry Relationship

 Insufficient non-functional Requirements Definition and Product Design

 Inadequate quantitative performance measures

 Poor data rights management

nstitutional Knowledge Lock

 Contractor monopoly on ‘proprietary source code’ level knowledge created ‘solesource contracting environment due to unacceptable program risk associated with vendor change

 Reliance on private-industry for s/w architecture, design, code and integration resulted (over time) in loss of government in-house s/w expertise

 Government left with limited ability to set development cost, schedule, or performance targets or to employ risk mitigation strategies when the contractor does not meet program needs

igh Sustainment Cost

 Above issues resulted in release of poor quality software to operational forces

The RITE Vision

Integration nd Test vironment (RITE)

sses S/W ition issues facilitates pment and ution of Navy tems: k –software ment ize – the current

nce – the final delivery

RITE PILLARS

Life Cycle Comparison Contract

er Cycle Model

Procure 5%

Maint Trouble Reports

STR

Implement

Test

Approve

30%

20%

15%

Maintain 30%

Release Timeline

Notional Level of Effort

Cycle Model

CCB

Release Timeline 15% Procure & Design

50%

10% Test

Implement

10% Approve

15% Maintain

RITE Process Develop, Integration and Test seamless and accelerated Source code analysis allows for test events Less Rework (Tot # and Repair

Support and Maintenance

= RITE Frequent Touch Points

Overall schedule is reduced and total program cost is lower

In Summary…..

Three Maritime C2 Objectives  Expand Mission Management Capabilities by providing access to Who, What, Where, When, Why, and How information  Transition to a Open Source/Net-Centric Architecture (component portfolio approach) using Rapid Prototyping (C2RPC) and S&T insertion (LTE/C2TII) to augment C2 Program of Record (POR) migration  Create agile software acquisition processes through implementation of RITE initiative

The Achilles' Heel to effective C2 is data exposure!  We don’t necessarily own and/or control services and/or data sources (IWS, OPNAV N4) – NOR - do we WANT, or NEED, to  We need to support Navy and Joint processes and standards to

We get it. We also integrate it, install it and support it. For today and tomorrow.