1. Navy Vision For FORCEnet To Support Joint Functional Capabilities
RDML(S) Betsy Hight (CNO N61R)
NDIA Science & Engineering Technology Conference
22 April 2004
I will be discussing how the Navy’s vision for FORCEnet is proceeding, and how it is aligned with Joint Functional Capabilities.
I’ll first provide some background on FORCEnet, then discuss efforts we are executing with the other Services and the Joint community, how we are implementing joint interoperability via the FORCEnet Consolidated Compliance Checklist, and how we are integrating Science and Technology throughout the FORCEnet process.

2. FORCEnet Goals Within Sea Power 21
Ubiquitous, secure communication
Persistent ISR
Fully netted sensors
Flawless combat ID & Blue Force Tracking
Transparent Joint Interoperability
Is this is part of where we are going with FORCEnet. By 2012, networks will enable SeaPower 21 by providing a robust, secure network which provides throughput and information assurance to support network-centric operations and warfare.
Shared Maritime picture
Guaranteed Coalition Interoperability
Iron clad network defense-in-depth
Integrated Sea Warrior Capabilities
Fully Integrated Logistic Support
Robust Links

3. FORCEnet Overview FORCEnet is not:
An acquisition program, system, thing, or “just a net”
FORCEnet is the USN/USMC alignment & integration effort for:
DoN/DoD Transformation, Joint Interoperability, and Network Centric Warfare
Innovation, demonstration, testing, and assessment to achieve CNO’s goal of “Speed to Capability”
Operational Requirements, Architectures, Standards, Compliance, and Oversight of Naval Programs to achieve Joint Warfighting Capability
So what is FORCEnet ?
First let’s define what it is not. FORCEnet is not an acquisition program or a “thing”, and it is more than “just a net.”
I think of FORCEnet as a forcing function for the goals you see here, and a transformational “state of mind.” It

4. FORCEnet for the Warfighter (Sensor to Shooter)
Theater Sensors
Theater Comms
ISR IER’s
GEOGRAPHIC COVERAGE
TARGET TYPE
SENSOR ALLOCATION
SIGINT
IMINT
BDI
SATCOM
TACAIR IER’s
TACTICAL AIR STATUS
FLIGHT REPORT
AIRCRAFT MISSION STATUS
BDI
ID FRIENDLY FORCES
TARGET INTELLIGENCE
JTF
JFACC
REACHBACK
CAOC
CDL -N
Airborne
Sensors
C2 IERs
Force Assessment
Common Operational Picture
Target Information
BDA
Mission Information
Weapons Control Orders
Target Actions
Mission Status
Engagement Order
Direct Air Support
Airborne
C2 Nodes PR
NAVY
Weapons
Platforms
In doing so, we will be enabling critical warfighting capabilities --- and a more efficient and effective implementation of those capabilities under Network Centric Warfare.
Data Links
Detect ID Track Decide Engage Assess
Data Links
Weapons
Platforms
This page UNCLASSIFED

5. FORCEnet: Naval Link to Joint Capabilities
Sea Strike
Precision Engagement
Dominant Maneuver
Sea Shield
Full Dimensional Protection
Sea Basing
Focused Logistics
FORCEnet
Joint C4ISR
FORCEnet Initial Capabilities Document
Joint Operating Concepts
FORCEnet Consolidated Compliance Checklist
Joint Functional Concepts
In order to reach these visions, we must implement and enable the Joint Operating Concepts and Joint Functional Capabilities.
Two key FORCEnet documents and forcing functions in this process will be:
The FORCEnet Initial Capabilities Document, to identify the top level FORCEnet functional/operational requirements and capabilities, forming the foundation for FORCEnet Architectures and Standards; and
The FORCEnet Consolidated Compliance Checklist, to provide a mechanism for implementing and enforcing top-level requirements on all Navy and Marine Corps programs and initiatives.
Capabilities FORCEnet must provide to support the GIG and enable Naval Power21
ISR C2
Applications
Battlespace Awareness
Focused Logistics
Comms & Information Distribution

6. Observed Trends Increased Technology Capabilities
Increased Reliance on Commercial Sources
Increased Bandwidth Needs
Increased Need For Joint Interoperability
The reason why this is so important is shown in the trends shown here.
Increased Technology Capabilities:
As recent as 15 years ago…Command and Control environment can be characterized as: Push-to-talk single channel, radios,
a few secure telephones, limited automation, limited LAN’s
C2 existed by linear/sequential processes driven mainly by organizational hierarchy. It derived too many capabilities from Service stove-piped systems, and reliance was on “closed”/Point-to-Point or Peer-to-Peer networks, with limited or “kluged” interoperability.
We’ve come a long way in a short amount of time
Increased Reliance on Commercial Sources:
Strategic Bandwidth Shift: IRAQI FREEDOM: 70%--30% commercial v. MILSATCOM bandwidth; DESERT STORM: 30%-70%
Increased Bandwidth Needs:
In Desert Storm we averaged 183 bits per second per body (99,000,000/542,000)
In Iraqi Freedom we averaged: bps/body (3,200,000,000/350,000)
Increased Need for Joint Interoperability: An imperative in today’s and tomorrow’s warfighting environment, effecting Network Centric Warfare with our Service, Allied, and Coalition partners.

7. The DoD Plan: Transition to Joint Network Centric Architecture
Stovepipe Applications
Independent Frameworks
Government Standards
Federated Architectures
Multiple Levels of Security
Isolated Coalition Enclaves
Today
Warrior Components
Global Combat
Support System (GCSS)
Global Applications
Common Applications
Common Frameworks
Commercial Standards
Federated Architectures
Multiple Levels of Security
Multiple Coalition Enclaves
Mid-Term
Medical
Business Applications
To address these needs and trends, we must capitalize on the ASD(NII) Net Centric Initiatives under the Global Information Grid, using key technologies as the bridge:
Joint Tactical Radio System (JTRS): Provides IP-based, self managed, BLOS, mobile data and voice communications services.
GIG-BE: Provides ubiquitous, secure, robust optical IP foundation network
TCA SATCOM: Incorporates mobile/tactical users and global intelligence via optical cross links and EHF IP links
Net-Centric Enterprise Services: Provides information and data services to all GIG users
Information Assurance: Enables trusted computer, networking, and services to all GIG users
Horizontal Fusion: Means/tools to enable the smart pull and fusion of data by users.
Information Management
Megacenter Services
Software Distribution
from Central Files
Network Operations
Electronic Mail Delivery
Computing
Web Services
MSS
Wireless
Comm
SATCOM
Communications
Teleports
Commercial Fiber
RF Nets
Common Applications
Common Frameworks
Commercial Standards
Enterprise Architecture
Multi-Level Security
Multi-National Info Sharing
End-State
DISN
Doctrine
Policy
Governance
Foundation
Engineering
Spectrum
Architectures
Standards

8. FORCEnet Architecture Transition - “As Is” vs. “To Be” -
FORCEnet Target
Stovepipe Communications
Integrated Networks & Communications
GIG-BE
GIG
JTRS
TCS
CDL IP
TDL
Representative
Building Blocks
Distributed Services
Key Enablers
XML IP
End-to-End
Information Assurance
Open Systems
ISR C2
Combat
Systems
Security
ISR C2
Security
Security
Combat Systems
JC2
DJC2
DCGS
NCES OA
Servers
B2B
B2B
FORCEnet is doing this by developing the necessary architectures to provide an effective and efficient migration strategy that moves Naval PORs from their current platform/stovepipe domain to the future Joint Network Centric domain. This slide illustrates the challenge. Today our C4I infrastructure consists of a myriad of systems, each with their own communications infrastructure, their own security implementations, their own servers, etc. The vision of FORCEnet, the target we are working towards, is enterprise implementation through distributed services with common core services built on an integrated networks and communications backplane.
B2C
B2C
B2C
B2C
Consumers
C2C
C2C
C2C
Clients

9. Joint RAPTOR 04-1 Joint Distributed Services
USN / USMC
FORCEnet
USA
LAND WARnet
USAF
C2 Constellation
NSA/IC Network
Testbeds
DISA Teleport
Test Locations
TSAT Testbed (MIT/LL)
Optical Comm Testbed
RF Testbed
Network Testbed
DISA Terrestrial
GIG-BE Test Segments
GIG Testbed
Optical Core (NRL)
ATD Net
BOSSnet
JTRS Testbeds
JTEL
Joint RAPTOR 04-1 Joint Distributed Services
GOAL
Technical evaluation of JOINT tactical use of distributed services that enable increased Joint situational awareness, improved TST timeline (TPPU vs. TPED)
The Joint Rapid Architecture Experimentation (JRAE) is a FORCEnet initiative which we started this year, and is being conducted in coordination with the other Services and the Office of the Secretary of Defense to support consistent, joint development of Service Transformation Architectures and capabilities. The JRAE effort consists of a series of Joint RAPTOR experiments, the first of which (Joint RAPTOR 04-1) was successfully completed in March Joint Raptor 04-1 looked specifically at how the Army, Air Force, Navy and Marine Corps can implement joint tactical use of distributed services. It demonstrated that the JTF Commander can reduce his area of uncertainty via automated chemical/biological plume analysis, automated weather updates, blue force tracking, mensurated imagery, weapons pairing and targeting all through distributed services overlayed on the web enabled Common Operational Picture (COP). Could this change the way we fight? Yes. It enabled us to compose the information “on the fly” (“Composeable FORCEnet”) that allowed us to reduce the area of uncertainty and carry out the mission successfully in a significantly reduced timeline. In working with the Joint community and other services, we also learned more about the technical challenges in implementing joint functional capabilities via distributed services. An example of a lessons learned is that in order to publish and subscribe to each others services, we had to cross many firewalls. Not only did each service have their own policy for implementing firewalls, but each command with the services had different policies for implementing firewalls. This demonstrated that a DoD-wide security policy is necessary if we are ever going to move to Joint Distributed Services or an NCES environment. .

10. Trident Warrior 03 JTF WARNET Expeditionary Strike Group -IBGWN- DISN
Other
National
Assets
Enhanced Joint IP Network Infrastructure – provides dynamic, adaptable ship-to-ship/sub and ship to air connectivity
Comm Teleport CA III
ONI
RSOC
Joint Ashore
FLT NOC
NCTAMS
USMC Ashore
DISN
JTF WARNET
To complement and mature the FORCEnet laboratory-based efforts such as JRAE and its Joint Raptor experiments, FORCEnet employs a range of operational events under Sea Trial and the FORCEnet Innovation Continuum. Our primary operational event is Trident Warrior. Trident Warrior 03 was the first such event, and was successfully conducted from Sept , 2003, with activities occurring onboard the ESSEX Expeditionary
Strike Group (ESG) (CTF 76), and ashore in Japan and Hawaii. Trident Warrior 03 represented the first large-scale event in the FORCEnet
development continuum. It represented a significant departure from prior Fleet exercises in that innovation and long term sustainment were built into the event. This approach permitted greater flexibility in both planning and execution and provided a greater return on investment. Additionally, the leave- behinds were the first increment of bringing FORCEnet to the Fleet.
One of the improvements was IBGWN for LOS networking between the ships as shown by the blue bubble in the lower center. This slide shows some of the area we worked to improve, IP networking, increased Satellite bandwidth, Joint connectivity, LOS networking. Not specifically shown are the QoS improvement, and COP improvements
Application integration – for sensor fusion, targeting, joint fires, and situational awareness.
Combat capability – increases speed and quality of command / decision making, expanded battlespace, more adaptable / agile force, improved engagement of difficult land targets, increased volume of fires, affordability and reduced manning requirements.
Expeditionary
Strike Group
-IBGWN-

11. Composeable Warfighting Capability Vision
Changing the way we fight
“Composeability” -- The Ability to Select “On the Fly” From a Vast Network, the Specific Information Resources Which Are Best Suited to Solving a Particular Problem or Providing Specific Information
“On the Fly” -- Sources Will Change With the Information Needs of the Scenario
Distributed Networks
Efforts such as JRAE, Joint Raptor, and Trident Warrior allow us to bring FORCEnet vision to reality. One of these, enabled by joint distributed services discussed previously, is the concept of FORCEnet composeability. Composeability is the ability to select “on the fly” the specific information resources and capabilities to fight a specific mission. And then to dynamically reconfigure, form new communities of interest, and develop new information resources on the fly to fight a new and changing mission as required. This is part of the DoN vision to integrate joint functional concepts and capabilities.
Plug-n-Fight!

12. Composeable Warfighting Capability Benefit
An example of how this vision could be applied in future warfare is shown on this slide depicting Navy and Army exchange of Blue Force information.. Currently (“As Is”), Blue Force tracks are shared via the COP in a vertical fashion. Army tracks are rolled up and sent to the Top COP. This is because
GCCS-A does not want to flood the COP with 30,000 ground troops. Then, the Top COP distributes the tracks to everyone. However, many times they
are filtered out. Rolled up and filtered is not sufficient to support joint call for fires from the Army to the Navy and to provide tactical Blue Force Situational awareness. Yet , nor would we want all 30,000 ground tracks if they weren't rolled up and filtered. Hence, this is the problem of the "as is" architecture.
A far more effective approach would be to have a horizontal or lateral exchange of BFT information via publish and subscribe. This could be only be possible because we are moving to a publish-subscribe architecture for our PORs. What we are doing in Joint RAPTOR is ensuring they are interoperable so we can indeed do this lateral information exchange. Since both the Army and Navy are moving to a publish and
subscribe architecture, we can now simply subscribe to the Blue Force Tracks in the geographic area where we are supporting a joint call for
fires. This can all be done technically and we are working with GCCS-M and GCCS-A to test it in Joint RAPTOR However, policy and TTP will also have to be changed to support this lateral exchange of information.

13. The FORCEnet S&T Process
- Delivering Increased Warfighting Capability to the Fleet -
CFFC
Articulate Fleet Requirements/
Concepts (NWDC/NNWC)
OPNAV
Validate FORCEnet Requirements (N61)
Balance Capabilities (N704/N706)
SYSCOMS
Integration of S&T into POR
S&T is a critical element in addressing current and projected warfighting capability needs. The FORCEnet S&T process is a collaborative effort between the many organizations you see here.
ONR
Identify S&T challenges (ONR Fn WG/IPT)
Develop S&T Strategy
NWDC (and SYSCOMS)
Fleet Experimentation (Sea Trial)
Lab Experimentation
Integrated Product Demonstration

14. FORCEnet Support of Technology Transition - Technology Readiness Levels/DoD 5000.2-R -
IOC
Actual system proven through successful mission operations
Prototype
Deployment
Actual system completed and qualified through test and
demonstration
System prototype demonstration in an operational environment
Sea
Trial
System/subsystem model or prototype demonstration in a
relevant environment
ACTD
Component and/or breadboard validation in relevant environment
Demo
Within this process, FORCEnet looks across the full spectrum of technologies.
This slide shows a representation of the technology spectrum.
On the right side of this slide are the Technology Readiness Levels that were developed by NASA in coordination with Industry.
On the left side are the commensurate DoD/FORCEnet phases.
The DoN Future Naval Capability process works primarily in the TRL 3 to TRL 7 domain, with Sea Trial and the Innovation Continuum focusing on TRL 6 to TRL 7, and FORCEnet’s Trident Warrior event focusing in the TRL 8 arena. The FORCEnet process provides a progression of technology all the way through deployment.
Component and/or breadboard validation in laboratory environment
Proof of
Principle
Analytical and experimental critical function and/or characteristic
proof of concept
6.2
Technology concept and/or application formulated
Basic principles observed and reported

15. Recent Technology Success Story
Knowledge Desks
For USS Carl Vinson TFCC
Knowledge Web Technologies
Improves speed of command by the timely dissemination of multi-media information to the operational commander.
Information is disseminated in a distributed command environment (30-60 min vice 8-24 hrs).
Provides near real-time SA in a distributed command environment (15 min updates vice 4-8 hrs)
Leveraged Navy initiatives on Web enablement and applied Open Standards for Web Services and Navy and Industry Standard Collaboration Tools to improve Asynchronous, Distributed C2 and Speed of Command.
Considering a full range of Technology Readiness Levels allows us to investigate promising new technologies while also working to actually deploy mature technologies. One of the recent technology success stories is Knowledge Web. Knowledge Web Technologies include software that has been integrated into the Fleet’s Collaboration at Sea software suite. These capabilities:
-- Enables GCCS-M to organize and display web-based information from heterogeneous warfare domain data sources
-- Provide Command staffs in Navy and Marine Corps command centers an integrated set of tools that facilitate data aggregation, value-added interpretation, and dissemination to the rest of the network, via Knowledge Desks and Knowledge Walls, for example:
-- Library of templates for different functional areas tailored to support command decision problems;
-- Knowledge Web Management Tools – aids for creating and altering the content of K-Webs;
-- Summary Maker –aid for the capture and presentation of an operational situation summary;
-- A Change History Made Explicit (CHEX) tool to support situation awareness recovery by organizing and visualizing the inter-relationships between significant past changes); and
-- A course of action (COA) modeling tool with enhanced graphical input and output visualization
Transitioned to GCCS-M and Operational in OEF and OIF

16. Critical Technologies to Address Capability Gaps
Robust, high throughput connectivity
Large, pervasive sensor and reconnaissance networks for detection, identification, and tracking of difficult and time sensitive targets
Automated exploitation of information and data
MLS solutions for networking and common operational & tactical picture
As we move forward, we are investigating critical technologies to address critical gaps --- to identify promising areas for investment. These are some of the near-term areas.
Gaps related to Multi-Path Redundancy
Large, pervasive sensor and reconnaissance networks” relates to: 1) Bottlenecks, 2) Leverage National Sensors, 3) USW Collaboration, and 4) Optimal Mix. The technology gap (the U.S. does not have a large, pervasive sensor and reconnaissance network) inhibits the ability to rapidly develop a comprehensive COTP and distribute it to all users. Information assurance is essential for this capability.
Automated exploitation of information and data” relates to: 1) Bottlenecks, 2) COTP Integration, 3) COTP to all users, and 4) USW Collaboration. Information assurance is essential for this capability. he bullet “MLS solutions” relates to the need for Information Assurance across coalitions and levels of security.
Robust, high throughput connectivity is required for ground mobile forces, unmanned vehicles, aircraft, and covert platforms as well as for ships and submarines. The technology problems to be addressed are listed. Undersea connectivity is particularly an issue: ONR plans to have a workshop on undersea optical connectivity in FY04.
Large, pervasive sensor networks address the lack of timely and accurate information at the operational and tactical scale, available to naval warfighters. Research in this area, coordinated with and leveraged from Army and Air Force research, will provide sensing capability under naval operational and tactical control.
New sources of data and information, and increasing volume of data and information from traditional sources, must be exploited and used more productively than is possible with human intervention. Humans must be assisted by computers, not replaced by them, and must be allowed to ask creative and challenging analytic questions rather than performing repititious tasks. Computers much take over work that humans are doing today, such as figuring out what an enemy means when they use information, and translating that to the potential effect on naval forces. In presenting information to humans, computers must be much more effective than they currently are. Instead of cluttering visual channels, they must understand the individual’s cognitive load and present information through channels that are underutilized.

17. FORCEnet Capabilities ONR Discovery and Invention Focus
Long Term S&T Investment
FORCEnet Capabilities
ONR Discovery and Invention Focus
Distributed, Collaborative Command and Control
Flexible command structure to enable optimum speed and precision of decision making
Adaptive / Automated Decision Aids
Improving the assimilation of information.
Dynamic, Multi-path and Survivable Networks
Low-power, high capability computer/communications technology
 Information Assurance
 Mission-focused network Quality of Service
 Underwater networks
Multi-tiered, Sensor & Weapon
Automated integration of disparate sensors and sources of information including metadata
Human-Centric Integration
 Integration and presentation of information to humans for maximum rate of comprehension and optimal utilization
We are also working closely with the Office of Naval Research to identify long-term FORCEnet investment in S&T.

18. Additional S&T Needs Batteries Multi-Beam Antennas
LPD/LPI of RF Emissions
Knowledge Management Tools
Open Architecture/Standards-based Computing
Efficient Bandwidth Utilization
Sailor-friendly Information Assurance Tools
Effective Data Strategy
The Office of the Chief of Naval Operations are also investigating other S&T needs, as shown here.
There is much to be done, and this is an area we particularly need Industry involvement.

19. Your participation is critical to the success of FORCEnet
Summary
Joint interoperability and Network Centric Warfare are primary drivers
Technology is a primary enabler
Joint Operating and Functional Concepts are “Rules of the Road”
Service/Program Compliance is an imperative
Industry is a primary contributor and partner
In summary, these are some of the points I have covered.
Our success in FORCEnet thus far has been be result of the outstanding partnership we have with Industry.
Our continued progress requires our further and increased collaboration
Your contribution is critical to the future of FORCEnet and of DoN/DoD transformation, and it has been a privilege and pleasure to discuss
our the Navy vision of FORCEnet and the our planned implementation of Joint Functional Capabilities.
Your participation is critical
to the success of FORCEnet