To the SLAAD Annual Symposium

1
FORCEnet Fleet Requirements and Assessments
To the SLAAD Annual Symposium 29 April 2004
CAPT John Yurchak NETWARCOM N8
This Brief is UNCLASSIFIED / FOUO
2
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

3
What Is FORCEnet?
Network Centric Warfare Is the Theory. Net-centri
c 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.
CNOs Strategic Study Group - XXI definition
from 22 July 02 CNO Briefing
4
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

5
How Weve Approached The Reqmnts Problem
Strategy, Warfighter Needs, Concepts, etc.
6
How Weve Approached The Reqmnts Problem
Strategy, Warfighter Needs, Concepts, etc.
7
How Weve Approached The Reqmnts Problem
Strategy, Warfighter Needs, Concepts, etc.
What the users are trying to do
Reqmnts Layers
Battlespace Effects Capabilities
1st
8
How Weve Approached The Reqmnts Problem
Strategy, Warfighter Needs, Concepts, etc.
Reqmnts Layers
Key capabilities required for ANY effect
(warfighting or business)
Battlespace Effects Capabilities
1st
Intelligence, Surveillance Reconnaissance
Battlespace Awareness
Focused Logistics
Communications Info Distribution
Applications
Enabling Effects Capabilities
Command Control
2nd
9
How Weve Approached The Reqmnts Problem
Strategy, Warfighter Needs, Concepts, etc.
Reqmnts Layers
Battlespace Effects Capabilities
1st
The core capabilities that make information work
for the user
Intelligence, Surveillance Reconnaissance
Battlespace Awareness
Focused Logistics
Communications Info Distribution
Applications
Enabling Effects Capabilities
Command Control
2nd
FORCEnet Capabilities
3rd
10
How Weve Approached The Reqmnts Problem
Strategy, Warfighter Needs, Concepts, etc.
Reqmnts Layers
Battlespace Effects Capabilities
1st
Intelligence, Surveillance Reconnaissance
Battlespace Awareness
Focused Logistics
Communications Info Distribution
Applications
Enabling Effects Capabilities
Command Control
2nd
The physical instantiation of the architecture
. . .
FORCEnet Capabilities
3rd
Data Models
Enterprise Services
IM / KM
Agent-Based Protocols
. . .
Vehicle / Media (i.e., physical)
Network Backbone
Space Segment
Computer Architecture
Distributed Computing
RF
4th
11
How Weve Approached The Reqmnts Problem
Strategy, Warfighter Needs, Concepts, etc.
Reqmnts Layers
Battlespace Effects Capabilities
1st
Intelligence, Surveillance Reconnaissance
Battlespace Awareness
Focused Logistics
Communications Info Distribution
Applications
Enabling Effects Capabilities
Command Control
2nd
. . .
FORCEnet Capabilities
3rd
Data Models
Enterprise Services
IM / KM
Agent-Based Protocols
. . .
Vehicle / Media (i.e., physical)
The life cycle support for the information
capability
Network Backbone
Space Segment
Computer Architecture
Distributed Computing
RF
4th
Sustainment
5th
12
How Weve Approached The Reqmnts Problem
Strategy, Warfighter Needs, Concepts, etc.
Capabilities-based approach starting with
warfighting effects
Reqmnts Layers
Battlespace Effects Capabilities
1st
Intelligence, Surveillance Reconnaissance
Battlespace Awareness
Focused Logistics
Communications Info Distribution
Applications
Enabling Effects Capabilities
Command Control
2nd
. . .
FORCEnet Capabilities
3rd
Data Models
Enterprise Services
IM / KM
Agent-Based Protocols
. . .
Vehicle / Media (i.e., physical)
Network Backbone
Space Segment
Computer Architecture
Distributed Computing
RF
4th
Sustainment
5th
In order to understand the desired capabilities
of the enablers we need to understand
the needs of the enabled
13
FORCEnet Touches Everything
Strategy, Warfighter Needs, Concepts, etc.
What the warfighter is demanding of FORCEnet
Reqmnts Layers
Battlespace Effects Capabilities
1st
Intelligence, Surveillance Reconnaissance
Battlespace Awareness
Focused Logistics
Communications Info Distribution
Applications
Enabling Effects Capabilities
Command Control
2nd
. . .
FORCEnet Capabilities
Net-Centric Capabilities
3rd
Data Models
Enterprise Services
IM / KM
Focal Point
Agent-Based Protocols
. . .
Vehicle / Media (i.e., physical)
Network Backbone
Space Segment
Computer Architecture
Distributed Computing
RF
4th
Sustainment
5th
What characteristics FORCEnet needs to have to
meet the demands
14
The Reqmnts Capture Challenge
Strategy, Warfighter Needs, Concepts, etc.
What the warfighter is demanding of FORCEnet
Reqmnts Layers
Battlespace Effects Capabilities
1st
Intelligence, Surveillance Reconnaissance
Battlespace Awareness
Focused Logistics
Communications Info Distribution
Applications
Enabling Effects Capabilities
Command Control
2nd
. . .
FORCEnet Capabilities
Net-Centric Capabilities
3rd
Data Models
Enterprise Services
IM / KM
Focal Point
Agent-Based Protocols
. . .
Vehicle / Media (i.e., physical)
Network Backbone
Space Segment
Computer Architecture
Distributed Computing
RF
4th
Sustainment
5th
What characteristics FORCEnet needs to have to
meet the demands
15
The Reqmnts Integration Problem
Strategy, Warfighter Needs, Concepts, etc.
What the warfighter is demanding of FORCEnet
Reqmnts Layers
Battlespace Effects Capabilities
1st
Intelligence, Surveillance Reconnaissance
Battlespace Awareness
Focused Logistics
Communications Info Distribution
Applications
Enabling Effects Capabilities
Command Control
2nd
. . .
FORCEnet Capabilities
Net-Centric Capabilities
3rd
Data Models
Enterprise Services
IM / KM
Focal Point
Agent-Based Protocols
. . .
Vehicle / Media (i.e., physical)
Network Backbone
Space Segment
Computer Architecture
Distributed Computing
RF
4th

• and integrating them against each of the
  enablers to look for
• Common / recurring themes
• Gaps and Redundancies
• Convergence opportunities
• Etc.

Sustainment
5th
What characteristics FORCEnet needs to have to
meet the demands
16
The Reasons For FORCEnet
Strategy, Warfighter Needs, Concepts, etc.
Reqmnts Layers
1. What are the users / effects demanding of the
information resource?
Battlespace Effects Capabilities
1st
Intelligence, Surveillance Reconnaissance
Battlespace Awareness
Focused Logistics
Communications Info Distribution
Applications
Enabling Effects Capabilities
Command Control
2nd
. . .
FORCEnet Capabilities
3rd
Data Models
Enterprise Services
IM / KM
The FORCEnet Operational Advisory Group (OAG), a
USN-USMC IPT, is responsible for this part of the
requirements problem. Led by NETWARCOM and MCCDC
Agent-Based Protocols
. . .
Vehicle / Media (i.e., physical)
Network Backbone
Space Segment
Computer Architecture
Distributed Computing
RF
4th
Sustainment
5th
17
What FORCEnet Is
Strategy, Warfighter Needs, Concepts, etc.
Reqmnts Layers
Battlespace Effects Capabilities
1st
2. What does the information resource need to be
like (FORCEnet attributes), what are the core,
enterprise information capabilities?
Intelligence, Surveillance Reconnaissance
Battlespace Awareness
Focused Logistics
Communications Info Distribution
Applications
Enabling Effects Capabilities
Command Control
2nd
. . .
FORCEnet Capabilities
3rd
Data Models
Enterprise Services
IM / KM
Agent-Based Protocols
. . .
Vehicle / Media (i.e., physical)
Network Backbone
Space Segment
Computer Architecture
Distributed Computing
A DoN Enterprise process to do this is under
development Key portions to be led by NETWARCOM
RF
4th
Sustainment
5th
18
How FORCEnet Will Be Delivered And Sustained
Strategy, Warfighter Needs, Concepts, etc.
Reqmnts Layers
Battlespace Effects Capabilities
1st
Intelligence, Surveillance Reconnaissance
Battlespace Awareness
Focused Logistics
Communications Info Distribution
Applications
Enabling Effects Capabilities
Command Control
2nd
. . .
FORCEnet Capabilities
3rd
Data Models
Enterprise Services
IM / KM
Agent-Based Protocols
3. How do we implement (design, engineer,
deliver, sustain) this capability?
. . .
Vehicle / Media (i.e., physical)
Network Backbone
Space Segment
Computer Architecture
Distributed Computing
RF
4th
Sustainment
5th
This has been the domain of the communicators and
IT pros(Fleet N6s / NETWARCOM / OPNAV / SPAWAR /
PEOs)
19
The Current Reqmnts Process
Strategy

• Off-Ramps
• Service Strategy
• Service POMs
• DoN Reqmnts Documentation
• DoN Enterprise IT Reqmnts Process
• N6 Conference
• Fn Matrix
• Fn Integrated Architecture
• JBMC2
• JCIDs /FCBs
• Service / Joint IE

Working-Level Validation
3-star Validation
WF Needs (Effects)
CFFC
User-Prioritized / Validated Operational Needs
Fn OAG
MCCDC (EFDS)
Opnl LLs
Current Info Capability Assessments
To Develop This
Comms, networks, IM/KM, collaboration,
interoperability, etc.
20
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

21
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 Navys 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

22
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

23
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)

24
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 FFCs emerging reqmnnts ROE /
  CONOPS
• Preparing a pilot project to test the process
• Outputs
• In progress

25
Navy Enterprise IT and Telecom Business
Efficiencies

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

26
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

27
Reqmnts Guidelines and GuidepostsHow Were
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, Integrate
28
Questions???