Maritime C2 Strategy An Innovative Approach to System ... · Maritime C2 Strategy An Innovative Approach to System Transformation 22 June 2010 Patrick Garcia ... Operations CINDY

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

Maritime C2 Strategy An Innovative Approach to System Transformation

22 June 2010Patrick Garcia

Technical DirectorCommand and Control Systems (PMW-150)

[email protected]

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

Maritime C2 StrategyAgenda

• PMW 150 Introduction • Current Maritime C2 Situation• Strategy ObjectivesMission Management Capabilities

Net-Centric Operations TransitionSoftware Acquisition Process Changes

• Summary

2

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

Technical Director

PAT GARCIA

Functional

Deputy Program ManagerCAPT D.A. LeGoff

Deputy Program ManagerCAPT D.A. LeGoff

JWARNJEM

C2PADSI

LINK-16LINK-11

Business Financial Manager (4)

DR. MIKE NAKADA

Business Financial Manager (4)

DR. MIKE NAKADA

Acquisition Manager

DAVE NORD

Acquisition Manager

DAVE NORDAPM (L)

4 EMBEDDEDAPM (L)

4 EMBEDDEDDirector of Operations

CINDY TAYLOR

Director of Operations

CINDY TAYLORAPM (C)

1 EMBEDDEDAPM (C)

1 EMBEDDEDAPM (E)

3 EMBEDDEDAPM (E)

3 EMBEDDED

Programmatic

NTCSS(with

OOMA)

NATO Improved

Link Eleven

PMW 150 Organization

Defensive C2PAPM

SCOTT WHITE

Defensive C2PAPM

SCOTT WHITE

Tactical C2PAPM

PAUL BOBROWICH

Tactical C2PAPM

PAUL BOBROWICH

Maritime C2PAPM

CDR PAT MACK

NILEPAPM

MANUEL GOMEZ

NILEPAPM

MANUEL GOMEZ

GCCS-MGCCS-J

Program ManagerCAPT Steve McPhillipsProgram Manager

CAPT Steve McPhillipsCivilian – 15Military – 13Civilian – 15Military – 13

Support C2PAPM

KEVIN ALLEN

Support C2PAPM

KEVIN ALLEN

3

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

(MTC2) • FY12 proposed new start

• Global-Theater Security Cooperation Management Information System (G-TSCMIS)

• Pending assignment to PEO C4I• Joint Command and Control PortfolioTactical C2• Air Defense System Integrator (ADSI)• Link 22

• POM 12 issueSupport C2• Maintenance Figure of Merit (MFOM)

• Transition from USFF N43 01OCT10• Bar Code Supply Logistics Maintenance

Automated Information System (BCS LMAIS)

• Assume responsibility 01OCT10Technical Director• Command and Control Rapid Prototype

Continuum (C2RPC) • ONR funded initiative

NATO Improved Link Eleven (NILE)

PMW 150 Program Portfolio

Maritime C2• Global Command and Control System-

Maritime (GCCS-M) • ACAT IAC

Tactical C2• Link-16 Network

• ACAT II• Command and Control Processor

(NGC2P) • ACAT II

Support C2• Naval Tactical Command Support

System (NTCSS) • ACAT IAC

Defensive C2• Joint Warning and Reporting Network

(JWARN) • ACAT III

• Joint Effects Model (JEM) • ACAT III

Active ACAT Programs Other Programs and Projects

4

5

Navy GCCS-M Force StructureAs of 19 MAR 2010

1*

2

8

11

0 3 6 9 12

LCC

LHA

LHD

CVN

10 Allied/Coalition Partners

LPD-17 84Group Level 5

57

22

0 10 20 30 40 50 60 70

DDG

CG

0

FFG

PC

2

16

14

30

10 20 30 4013

MCM

LPD 4/LSD

LCS

50 SSNs

14 SSBNs

4 SSGNs

68 Submarines

22Force Level

75 Unit Level

CONUS Sites (20 qty)USJFCOM

COMUSNAVSO / C4FCOMNAVSPECWARGRU2COMNAVSPECWARGRU4

COMEXSTRIKGRU2COMSOCJFCOM

COMNAVFACENGCOMNOLSC

CBCCOMEXSTRIKGRU3

NFELCCOMFIRSTNCD

CNOAlt Navy CMD Center

USFFCOMTHIRDFLT

COMSECONDFLT COMNAVSPECWARCOM-West

COMSUBFORCOMSUBRON-11

OCONUS Sites (14 qty)USFJ

USPACOMCOMNAVFORJAPANCOMEXSTRIKGRU7

CTF-72CTF-73 / COMLOG WESTPAC

PA-RSCCOMPACFLT

COMUSNAVCENT/C5FCOMUSNAVEUR / COMSUBGRU 8

CTF74 / COMSUBGRU 7COMSUBPAC

CTF-34COMSUBGRU 8 Rep

Training Sites (8 qty)SWOSCOLCOM

CSCS U Dam NeckCID LS Dam Neck

NMITCFLEASWTRACENCID LS San Diego

FITCPACNSAWC Fallon

• 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 55




• Summary

WP 5-01 Planning

Maritime C2 Situation: Where are we now?

Maintainalignment

Adjustapportionment Provide SA

Counter theEnemy

Advancethe plan

Comply with procedure

Current Ops(Comms, COP, Intel)

Define Future Ops(Intel, Mission Planning)

Mission Execution (Tasks & Plans)

Commander’s IntentDaily Intentions

Rules of Engagement(OPTASK Supplements)

Request for Forces(Redeployment)

NWP 3-32 Maritime Warfare at

Operational Level of War

C2 Today:“Tracks and Maps”

POR Programst support mostWP 5-01 or 3-32 tenets.

Goal is to address thetenets of Maritime

Operations at the OLW

Synchronizing the Worldof Maritime C2

JFMCCJFMCC CTF/CTGCTF/CTG CVCV CGCG DDGDDG FFGFFG

CPF, JTF, JFMCC MOCC2 Objective

AdjustApportionment

AdjustApportionment

MaintainAlignmentMaintain

AlignmentAdvancethe PlanAdvancethe Plan

SituationAwareness

SituationAwareness

Comply withProceduresComply withProcedures

Counterthe Enemy

Counterthe Enemy

Centralized GuidanceFederated Execution

Shared SA for Synchronization

Commander’s Control Measures

Plans/TasksCOP

LogCOP

NetOpsCOP

“What is this unit tasked to do? Against what target?”

How are his tasks synchronized with his Force

tasking?

Are there alternate resources that could be assigned?

What is the task status & mission effects status?

Are there any readiness, Logistics, NetCOP, METOC,

or Task Sync conflicts?

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

N l W f P bli ti (NWP) 50 1 N Pl i

M a r i t i m e C 2 S t r a t e g y

Agenda



• Summary

Pillars of Future C2 system

Intelligence & CM ISR Data Fusion

Capabilities& Readiness

Planning, xecution, AssessmentPlans/Tasks Data Service

Unit tasking & task statusAuthoritative plans data

PlanningMission managementDecision Points, LOOCMD relationships, COA sketch

ExecutionSynchronization

• 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

• GCCS- I3• Analysis products & IPOE • Red Force Service

- Units/Sites & Capabilities- Enemy COAs- NAI Characteristics- Targets

• Info Req’s• Collection Req’s

• Conditions of Interest Alerts- Area entry- Task execution deviations- (others TBD)

• OTM (new track mgr) • Associate GCCS- I3 info w/

OTM reporting

Establish C2 Relationships and Strategyfor Deployment of Capabilities

Command & Control Monitoring and Assessment Direction and Coordination

Combat SystemsTODAY: TRACKS ONLY

ISR/IOTODAY: TRACKS ONLY

Combat SupportTODAY: NO COLLABORATION

t/Coalition/p/One downY: TRACKS ONLY

Confirm Red OOB/COAsDecision-focused triggersHi interest track infoMOE/BDA indicators

Sensor statustrks of interestsRequest NERF/EPL dataTarget prosecution status

Request COA readinessRqst unit/capab readinessRqst Systems/Aircraft statusRequest logistics data

COA/Plan readinessCapability readiness dataSystems/Aircraft statusLogistics status data

sking & Coordinationasures of performancesk progress-planning effects

CCIRs, PIRsDecision info rqts (DSTs)Trks of interestMeasures of effects

Request Sensor statusProvide trks of interestsProvide NERF/EPL dataCue target locs & info

sion and taskingmmanders Intentsion assessmentplanning

timerationsters

oups,its

SupportCommands

National &Theater

Intelligence

)

Unifying Maritime Missionsinto a Navy Mission Planner View

JFMCC MOC

TF/TG CDR

Synchronizetimeline

Prioritizetargets &resources

Advance thePlan

Align CDR’sIntent

Plan(NPP, JOPP)

Assess(MOEs, MOPs)

HHQ,Joint, Coalition

Subordinate Units,CS/CSS Combat Systems

tasks taskstatus

DIRECTMONITOR

ISR

Maritime MissionsMaritime MissionsBallistic Missile DefenseMaritime 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 OperationsStrike 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 NavigationI t lli C ll ti

Maritime Planning & OLW ExecutionMaritime Planning & OLW Execution




• Summary

Maritime C2 Program of Record Migration

CE

FY10 FY12

C

UP

T

GCCS-M GCCS-M JC2C/MTC2

4.0.1

3.X.X

4.0.2

4.0.3

TODAY NEAR TERM

FYDP

FORCE

MOC

GROUP

UNIT

4.0.34.1 (TACT)

FORCE

MOC

GROUP

UNIT

JC2C4.1 (FORCE)

MTC2

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

GCCS-M provides a robust ational Awareness of Who and

Where across the Wide Area Network

MTC2 will address “Who, What, When, Where, Why, How” in Mission Management

Planning, Assessment, and Monitoring tools

MTC2

C2 Rapid PrototypingContinuum (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)

2012 2014 2016

Improved missionArea COA analysis

& Execution Assessment

Basic Maritime planning& Execution Monitoring

Real time, cross-Domain tasking& assessment

unterEnemy

ovideSA

vancee Plan

djustortion-

ment

ntainnment

ply withcedure

C2RPC

Feeder Technologies

FY10-11

C2RPC New Capabilities

Appssupport

DataMgmt

EnterpriseServices

b t ti

Cap

abili

ties

& R

eadi

ness

Plan

ning

&Ex

ecut

ion

Inte

l & C

MIS

R D

ata

Fusi

on

• OTM• R/W/B Data

Services • R/W objects

in COP• IPOE assoc

w/plan• Plan/task

assoc w/units& resources

• Shore MOCsCOA & decisionsupport tools

• CPF readinesspilot hardened(plan heuristics& data feeds)

• ISR mgtto plan rqts

• CM/CCIRslink to decisionpoints

• Targeting• CCIR tracking

vs decisions• IMA

• MOC & below(TG) distributedplanning/exec’n(DIL environmt)

• Core plan tool• Addnl’ mission

area heuristics& threat sit’ns

• Org (GFM) C&Mlinked to plan-

ning (& data fill)

• CS track/plans/readiness/I&W/status data exch

• TBD w/PMW120• Mission & asset

status/avail

• Integratedmission mgmtw/distributedlegacy systems

• Tactical assetsreadiness indecisionmaking

• TG planningtools

• Continuousreadinessassessmentfor real timedecisions

• Joint planning/APEX (completelegacy migration)

• Ship leveltactical planexecutionmonitoring &feedback

• Task directionvia IP TADIL

• TBDw/PMW120

• TBD

• Initial shore/ship capability(TBD by study)

• Collaborative

• Fully functionalDistrib data svc

• CS-interfaceto enablemission mgmt

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

• ROW C2 v2

• Study & Initialshore capability(AIF study)

• IR COP, UFS,selected data

C2RPC 2011 Capabilities

Appssupport

DataMgmt

EnterpriseServices

b t ti

Cap

abili

ties

& R

eadi

ness

Plan

ning

&Ex

ecut

ion

Inte

l & C

MIS

R D

ata

Fusi

on

• OTM

• R/W objectsin IR COP

• Plan/task demoof assoc w/units& resources

• CPF readinesspilot (OPLANreadiness forapportion’d ships)

• AMCRs, OIS,TRMS,MFOM

• LogCOP• NetOps COP

• Red force svcon IR COP halo

• Track mgmtwidgets – initialcapability

• Red force svc(I3 objects inOTM COP)

• IPOE assocw/plan

• Task Navigator(task drill-down

PTDS fm IR COP)• Decision Point,

SOP & CmdRelationships

• CPF readinesspilot (Prioritymissions readi-ness) initialintegr’n w/PTDS

• OPREP-5, BMDand ASW planreadiness)

• Blue capab/orgs

• White force svc• Blue force mov’t

(WebSked),Environmentalconditions/Wx

• Targets• IPOE integr’n

with MaritimeCOA Sketch

• COA sketch,Line of Opstools first look

• COA collabo-ration

• Additionalreadinessheuristics

• Additionalmission areas

• Readinessintegratedwith planningprocesses &tools

• Maritime COASketch/LOO &Decision PtsIntegrat’d capab

• Ops Sync tool(Sync Matrix)

• Distributedplanning amongMOCs, TFs,&TGs

• Initial link ofCCIRs to plan& decis points

• Blue force mov’t(OTSR)

• OTM link tracks& acoustic trks

• UFS APIs &WebTop

• AIF capabilities

• CollaborativeCOP initialcapability

• AIF prototype

• Initial AIFcapability(ashore, afloat)

• UFS processworkflowsupport

• IR COP,selected data

Implemented

Office of Naval Research effort, with PEO C4I and PEO S cooperation to exchange of real-time and near-real-e tracks and other data to and from CS and C2 systemsInitial experimentation phase will focus on CS publishing ASW tracks, tactical readiness and video – September ’10

Next experimentation event scheduled for June ’11

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

RapidtotypetinuumRPC)

C2hnologyertiontiative

C2TII)

2011 2012 2014 2016

DT&E

OT&E

DT&E

OT&E

DT&E

OT&E

DT&E

OT&E

ritime C2POR

igrationGCCS-M MTC2

ONR-funded prototyping

MAR2010

AUG2010

Nov2010

Future C2 Program EvolutionVenues of Prototyping, Experimentation, & Hardening

TF/TGUnit

MOC

Drop1 Drop

2Drop

3

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

PMW-150 architecture S&T INTEGRATION and TRANSITION to POR


• PMW 150 Introduction• Current Maritime C2 Situation• Strategy ObjectivesMission Management Capabilities


• 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 ‘sole-

source 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 mentize – the current

nce – the final delivery

RITE PILLARS

Life Cycle Comparison

Overall schedule is reduced and total program cost is lower

Implement Test Approve Maintain

STRCCBContract

30% 20% 15% 30%

Procure

5%

Maint Trouble Reports

Release TimelineRelease Timeline

= RITE Frequent Touch Points

Develop, Integration and Test seamless and accelerated

Source code analysis allows for test events

Less Rework (Tot # and Repair Duration) reduces over project

MaintainTest ApproveProcure

& Design

Support and Maintenance

RITE ProcessRITE Process

Implement

erCycle Model

Cycle Model

NotionalLevel of Effort

Release TimelineRelease Timeline

10% 10% 15%15% 50%

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.

Documents

Maritime C2 Strategy An Innovative Approach to System ... · Maritime C2 Strategy An Innovative Approach to System Transformation 22 June 2010 Patrick Garcia ... Operations CINDY