To the SLAAD Annual Symposium 29 April 2004 FORCEnet Fleet Requirements and Assessments CAPT John...

To the SLAAD Annual Symposium29 April 2004

FORCEnet Fleet Requirements

and Assessments

CAPT John YurchakNETWARCOM N8

This Brief is UNCLASSIFIED / FOUO

MissionMission PeoplePeople CapabilityCapability

UNCLASSIFIED // FOR OFFICIAL USE ONLY

Scoping the Problem: What is FORCEnet?

Depending on Who You Ask ...• An operational construct and architectural framework• A means• An enabler• A physical thing (i.e., a piece of the GIG)• A distributed system (i.e., shooters, sensors, deciders) • A transformation effort• A collection of capabilities• A design• An implementation strategy• Wicked complex• A mystery



Network Centric Warfare Is the Theory.

Net-centric Operations Is the Concept.

FORCEnet Is the Process of Making the Theory and Concept a Reality.

“FORCEnet is the operational construct and architectural framework for Naval Warfare in the Information Age which

integrates Warriors, sensors, networks, command and control, platforms and

weapons into a networked, distributed combat force, scalable across the

spectrum of conflict from seabed to space and sea to land.”*

*CNO’s Strategic Study Group - XXI definition from 22 July 02 CNO Briefing

What Is FORCEnet?



Key FORCEnet Future Capability Context

Example Core Attributes• Global• Joint• Operational to Tactical• End-to-End• Full-Spectrum of WF /

Business Activity• “One Network”• Secure• Assured Access• IP-based• IT + Comms + Combat

Systems• Self-Organizing• Extensible & Composable• Open-Architecture

• Post/Publish & Subscribe• Agent-Based• Data Models / Meta-Data

Current Architecture Drivers• GIG BE

– Global Info Grid B/W Expansion

• GIG ES (GES / NCES)– GIG Enterprise Services

• TC– Transformational Comms

• Teleports• JTRS

– Joint Tactical Radio System

• IPV6• JBMC2 Integrated Architecture



How We’ve Approached The Reqmnts Problem

Strategy, Warfighter Needs, Concepts, etc.





Sea Strike Sea Shield Sea Basing Sea Warrior





Battlespace Effects& Capabilities

1st

ReqmntsLayers


Time-SensitiveTargeting

ComputerNetworkAttack

SpaceControl

NeutralizeMines in the

Littoral

KillWMDs

NavalFires

. . .CoalitionOperations

What the users are trying to What the users are trying to dodoWhat the users are trying to What the users are trying to dodo





Enabling Effects &Capabilities

Intelligence,Surveillance &

Reconnaissance

Command& Control

Communications &Info Distribution

1st

2nd

ReqmntsLayers


BattlespaceAwareness

ApplicationsFocusedLogistics



SpaceControl


Littoral

KillWMDs

NavalFires



Key capabilities required for ANY effect (warfighting or Key capabilities required for ANY effect (warfighting or business)business)Key capabilities required for ANY effect (warfighting or Key capabilities required for ANY effect (warfighting or business)business)







Reconnaissance

Command& Control


FORCEnetCapabilities

1st

2nd

3rd

ReqmntsLayers






SpaceControl


Littoral

KillWMDs

NavalFires


DataModels

Agent-BasedProtocols

EnterpriseServices

IM / KM . . .


The core capabilities that make information work for The core capabilities that make information work for the userthe userThe core capabilities that make information work for The core capabilities that make information work for the userthe user







Reconnaissance

Command& Control



Vehicle / Media(i.e., physical)

NetworkBackbone

SpaceSegment RF

1st

2nd

3rd

4th

ReqmntsLayers






SpaceControl


Littoral

KillWMDs

NavalFires


ComputerArchitecture

DataModels


EnterpriseServices

IM / KM . . .

DistributedComputing . . .


The physical instantiation of the The physical instantiation of the architecturearchitectureThe physical instantiation of the The physical instantiation of the architecturearchitecture







Reconnaissance

Command& Control




NetworkBackbone

SpaceSegment RF

1st

2nd

3rd

4th

ReqmntsLayers






SpaceControl


Littoral

KillWMDs

NavalFires



DataModels


EnterpriseServices

IM / KM . . .


Sustainment5th ComputerNetworkDefense

NetworkOperations

IntegratedLogisticsSupport

Training IPCommunity


The life cycle support for the information The life cycle support for the information capabilitycapabilityThe life cycle support for the information The life cycle support for the information capabilitycapability








Reconnaissance

Command& Control




NetworkBackbone

SpaceSegment RF

1st

2nd

3rd

4th

ReqmntsLayers






SpaceControl


Littoral

KillWMDs

NavalFires



DataModels


EnterpriseServices

IM / KM . . .



NetworkOperations



In order to understand the desired capabilities of the enablers …In order to understand the desired capabilities of the enablers … … … we need to understand the needs of the “enabled”we need to understand the needs of the “enabled”In order to understand the desired capabilities of the enablers …In order to understand the desired capabilities of the enablers … … … we need to understand the needs of the “enabled”we need to understand the needs of the “enabled”

Capabilities-based approach …Capabilities-based approach … … … starting with warfighting starting with warfighting effectseffects

Capabilities-based approach …Capabilities-based approach … … … starting with warfighting starting with warfighting effectseffects



FORCEnet Touches Everything





Reconnaissance

Command& Control




NetworkBackbone

SpaceSegment RF

1st

2nd

3rd

4th

ReqmntsLayers






SpaceControl


Littoral

KillWMDs

NavalFires



DataModels


EnterpriseServices

IM / KM . . .



NetworkOperations



What the warfighter is demanding of FORCEnet


What characteristics FORCEnet needs to have to meet the demands


Focal Point Net-CentricCapabilities




The Reqmnts Capture Challenge




Reconnaissance

Command& Control




NetworkBackbone

SpaceSegment RF

1st

2nd

3rd

4th

ReqmntsLayers






SpaceControl


Littoral

KillWMDs

NavalFires



DataModels


EnterpriseServices

IM / KM . . .



NetworkOperations










The Reqmnts Integration Problem





Reconnaissance

Command& Control




NetworkBackbone

SpaceSegment RF

1st

2nd

3rd

4th

ReqmntsLayers






SpaceControl


Littoral

KillWMDs

NavalFires



DataModels


EnterpriseServices

IM / KM . . .



NetworkOperations




… … and integrating them against and integrating them against each of the enablers to look for:each of the enablers to look for:

• Common / recurring themesCommon / recurring themes• Gaps and RedundanciesGaps and Redundancies• Convergence opportunitiesConvergence opportunities• Etc. Etc.

… … and integrating them against and integrating them against each of the enablers to look for:each of the enablers to look for:

• Common / recurring themesCommon / recurring themes• Gaps and RedundanciesGaps and Redundancies• Convergence opportunitiesConvergence opportunities• Etc. Etc.








The Reasons For FORCEnet




Reconnaissance

Command& Control




NetworkBackbone

SpaceSegment RF

1st

2nd

3rd

4th

ReqmntsLayers






SpaceControl


Littoral

KillWMDs

NavalFires



DataModels


EnterpriseServices

IM / KM . . .



NetworkOperations



1. What are the users / effects demanding of the information resource?1. What are the users / effects demanding of the information resource?

The FORCEnet Operational Advisory Group (OAG), a USN-USMC The FORCEnet Operational Advisory Group (OAG), a USN-USMC IPT, is responsible for this part of the requirements problem.IPT, is responsible for this part of the requirements problem.

Led by NETWARCOM and MCCDCLed by NETWARCOM and MCCDC

The FORCEnet Operational Advisory Group (OAG), a USN-USMC The FORCEnet Operational Advisory Group (OAG), a USN-USMC IPT, is responsible for this part of the requirements problem.IPT, is responsible for this part of the requirements problem.

Led by NETWARCOM and MCCDCLed by NETWARCOM and MCCDC



What FORCEnet “Is”




Reconnaissance

Command& Control




NetworkBackbone

SpaceSegment RF

1st

2nd

3rd

4th

ReqmntsLayers






SpaceControl


Littoral

KillWMDs

NavalFires



DataModels


EnterpriseServices

IM / KM . . .



NetworkOperations



A DoN Enterprise process to do this is under developmentA DoN Enterprise process to do this is under development

Key portions to be led by NETWARCOMKey portions to be led by NETWARCOM

A DoN Enterprise process to do this is under developmentA DoN Enterprise process to do this is under development

Key portions to be led by NETWARCOMKey portions to be led by NETWARCOM

2. What does the information resource need to “be like” (FORCEnet attributes), whatare the core, enterprise “information capabilities”?2. What does the information resource need to “be like” (FORCEnet attributes), whatare the core, enterprise “information capabilities”?




How FORCEnet Will Be Delivered And Sustained




Reconnaissance

Command& Control




NetworkBackbone

SpaceSegment RF

1st

2nd

3rd

4th

ReqmntsLayers






SpaceControl


Littoral

KillWMDs

NavalFires



DataModels


EnterpriseServices

IM / KM . . .



NetworkOperations



3. How do we implement (design, engineer, deliver, sustain) this capability?3. How do we implement (design, engineer, deliver, sustain) this capability?

This has been the domain of the communicators and IT prosThis has been the domain of the communicators and IT pros(Fleet N6s / NETWARCOM / OPNAV / SPAWAR / PEOs)(Fleet N6s / NETWARCOM / OPNAV / SPAWAR / PEOs)This has been the domain of the communicators and IT prosThis has been the domain of the communicators and IT pros(Fleet N6s / NETWARCOM / OPNAV / SPAWAR / PEOs)(Fleet N6s / NETWARCOM / OPNAV / SPAWAR / PEOs)




The Current Reqmnts Process

Fn OAGFn OAG

WF NeedsWF Needs(Effects)(Effects)

Opnl LLsOpnl LLs

Current Info* Current Info* Capability Capability

AssessmentsAssessments

* Comms, networks, IM/KM, collaboration, interoperability, etc.

User-User-Prioritized Prioritized / Validated / Validated OperationaOperationa

l Needsl Needs

CFFCCFFC

MCCDCMCCDC(EFDS)(EFDS)

““Off-Ramps”Off-Ramps”

• Service Service StrategyStrategy

• Service POMsService POMs

• DoN Reqmnts DoN Reqmnts DocumentationDocumentation

• DoN Enterprise DoN Enterprise IT Reqmnts IT Reqmnts ProcessProcess

• N6 ConferenceN6 Conference

• Fn MatrixFn Matrix

• Fn Integrated Fn Integrated ArchitectureArchitecture

• JBMC2JBMC2

• JCIDs /FCBsJCIDs /FCBs

• Service / Joint Service / Joint I&EI&E

StrategyStrategy

Working-LevelValidation

3-starValidation

To Develop This



Major Tracks of Reqmnts Activity

• Fleet Operational Reqmnts Integration & Assessment– IT, Space, FORCEnet

• Joint Reqmnts Integration and Assessment– JBMC2 / MID-912

• Bilateral Reqmnts Integration and Interoperability– NNWC-USAF C2ISRC– NNWC-MCCDC– NNWC-Army TRADOC Futures Center

• Navy Enterprise IT Reqmnts Integration– Unified tactical (warfighting) / non-tactical (business)

IT reqmnts for DoN



Fleet Operational Reqmnts Integration & Assessment

• Actions– Lead the FORCEnet Operational Advisory Group (OAG) with MCCDC

• Unified USN-USMC operational reqmnts process, database & docs for FORCEnet– Lead / support FFC N8 Collaborative Teams and ad hoc tasks

• OIF Lessons Learned (collected our own, and supported FFC, Deep Blue, JFCOM)• NCDP / NCP / MCP support (assessments)

– Maintain Navy’s SATCOM reqmnts database• Bandwidth assessments, SATCOM reqmnts integration

– Participate / represent-Fleet in various future architecture forums• Transformational Comms (TC), GIG, Teleports, JTRS, etc.

– Reqmnts and PPBE / POM support to FFC and OPNAV (via FFC)• Program reviews, needs prioritization, formal document reviews, LOE, etc.• TYCOM Priority Lists (TPL), Integrated Priority List (IPL) inputs, issue papers, etc.

• Outputs– First joint USN-USMC validated and prioritized warfighter capability reqmnts

for Fn– Unified USN-USMC capability – assessment framework, aligned with

JFCOM/JCS– Single USN-USMC consolidated warfighter needs database– Draft FORCEnet Initial Capabilities Document (ICD) compliant with new CJCSI

3170– Annual updates of the Navy SATCOM requirements database to JCS– Comprehensive OIF network / comms LLs



Joint Reqmnts Integration and Assessment

• Actions– Represent Fleet & Navy to JFCOM JBMC2 / MID-912 efforts

• NETWARCOM 00 sits on JFCOM JBMC2 Board of Directors• Coordinate Fleet reqmnts-related activities in support of SJFHQ, JC2, DJC2,

JBMC2• Participate in various reqmnts IPTs and actions• Participate in Joint architecture integration efforts & working groups

– Coordinate Fleet responses with OPNAV to JBMC2 Roadmap• Reqmnts and program synchronization to achieve Joint interoperability

– Formed (with USAF AFC2ISRC) a Tidewater Joint Integration and interoperability WG• Staffs and unifies USN-USAF-Army-USMC actions in support of JFCOM JBMC2 /

MID-912 efforts• Hold regular Integration & Interoperability conferences to propose, disseminate

and vet relevant issues & actions– Coordinate with USSTRATCOM on emerging missions and CONOPS

• Global ISR and IO• Outputs

– JFCOM Joint Integrated Architecture process– Navy inputs to the JBMC2 roadmap– Fleet-vetted DJC2 and JC2 operational reqmnts– Fleet-vetted Naval ISR reqmnts to Space-Based Radar



Bilateral Reqmnts Integration and Interoperability

• Actions– Active partnership with USAF C2ISRC

• Lead FORCEnet / C2 Constellation architecture integration and alignment

• Initiate, coordinate and staff various C2, TST and ISR CONOPS integration and alignment actions of interest (incl ISR Management, Tactical Data Links, Time-Sensitive Targeting, etc.)

– Partnership with USMC• Unified operational reqmnts process, database and

documentation for FORCEnet

• Outputs– Incorporation of Navy reqmnts into DCGS 10.2– Unified USN-USAF Tactical Datalink Roadmap– Navy-USAF ISR Sensor Strategy for FORCEnet and C2

Constellation (in progress)– JTRS Cluster 3 and 4 alignment (in progress)



Navy Enterprise IT Reqmnts Integration

• Actions– Leading Enterprise IT Reqmnts Process Development– Leading, at the request of DDCIO(Navy) and PEO(IT),

unification and integration of Navy tactical & non-tactical IT reqmnts process using an OAG process similar to FORCEnet OAG

– Aligning process to FFC’s emerging reqmnnts ROE / CONOPS– Preparing a pilot project to test the process

• Outputs– In progress



Navy Enterprise IT and Telecom Business Efficiencies

• Transforming our core business processes– Significantly reducing our manpower profile– Aligning near-term IT modernization plans

Study Name Timeline Activities Involved / AffectedFleet-NNWC Functional Alignment February-May 2004 FFC, CPF, NNWC, NNSOCFlag Pole March-August 2004 ALL NETWARCOM

May-04 ALL NCTAMSJuly-04 NNSOCJanuary-March 2004 NCTS LANT DET HAMPTON ROADSApril-June 2004 NCTS SAN DIEGO , CMFO SD, NCTS

SICILY, NCTS SICILY TSCOMM DET SIG, NCTS SICILY SATCOM

July-September 2004 FIWC NORFOLK AND SAN DIEGO, NCTS FAR EAST

Voice and Communications Study June-04 ALL NAVYShore Infrastructure Master Plan July-04 ALL NAVY

CMAT Reviews(several)

NNSOC ZBR



Key Challenges and Road Ahead

• Vertical and Horizontal Integration– Within the efforts of the “new” aligned NETWARCOM– Between “Fleet” and Navy Echelon I Activities– Within and across all Navy, DoN, Joint efforts

• Standing Up an Effective Enterprise IT Effort– Aligning Afloat and Ashore– Warfighting and “Business” processes and capabilities– Deriving the right Enterprise Information Services

• Balancing Responsibilities– Near vs Far term priorities– Readiness vs modernization & recap– Fleet with Joint

• Metrics– Needs vs wants– First, second, third-order effects



Reqmnts Guidelines and GuidepostsHow We’re Trying to Do Business

Guidelines• Avoid duplication and competition• Become integral to customer / stakeholder processes• Emphasize distributed over centralized SMEs and work• Collaborate to gain acceptance, then force action /

decisions / outcomes

Guideposts• Emphasize Joint over Service• Emphasize Naval over Navy• Emphasize Enterprise over Niche• Emphasize Commonality over Stovepipes

Bottom Line: Leverage, Partner, Align, IntegrateBottom Line: Leverage, Partner, Align, Integrate

Questions???

To the SLAAD Annual Symposium 29 April 2004 FORCEnet Fleet Requirements and Assessments CAPT John...

Documents

Transcript of To the SLAAD Annual Symposium 29 April 2004 FORCEnet Fleet Requirements and Assessments CAPT John...