Navy Warfare Development Command

1
2002 Fall Simulation Interoperability
Workshop MODELING NETWORK CENTRIC WARFARE and
INFORMATION WARFARE
Navy Warfare Development Command Mr. Guy R.
Purser Director, Modeling and Simulation Chief
Engineer 401 841 7054 purserg_at_nwdc.navy.mil
2
Topics of Interest

• Mission of NWDC MS
• Environment Boundaries
• Environment Hierarchy
• Environment Transport
• VVA (in context)

3
NWDC TASKS

• Holder of Concepts for CNOs SEAPOWER 21- Network
  Centric Operations
• Sea Strike
• Sea Shield
• Sea Basing
• Sea Trial
• JFCOM Navy Component Activity for Joint
  Experimentation
• Assigned to provide recommended future
  architecture for Navy Battle Group Training to
  CFFC

4
NWDC MS and Engineering Objective

• To create a simulated environment where novel
  war fighting concepts involving C2 architectures,
  organizations, and technologies can be end to end
  and repeatedly stimulated in a robust and
  scalable manner in the field and laboratory.

Directly relates to the direction, management of
information flow to critical nodes of war
fighting decision makers
5
Simulation System
Simulated Environment
RESULTANT BEHAVIOR OR STATE
INITIAL BEHAVIOR OR STATE
STATE CHANGE
Organizations Procedures/Processes Technology/Tool
s
Stimulation
6
Simulation System
BOUNDRY
Simulated Environment
RESULTANT BEHAVIOR OR STATE
INITIAL BEHAVIOR OR STATE
STATE CHANGE
Organizations Procedures/Processes Technology/Tool
s
Stimulation
Simulation Environment
7
Mensuration-4 Target Nomination with
Geo-Refinement Options(Engagement requests
geo-refinement)
8
Hierarchy and Boundaries
EXPERIMENT C2 RESPONSE
EXPERIMENT AUDIENCE
FEEDBACK LOOP TO Participants
Action/Reaction
C4I
VOICE
C2
STIMULATION OF C2AUDIENCE
C4I/WEAPONS SYSTEMS
Stimulation a result of C4I and Weapons System
injection
Common Operational Picture
GCCS
C2 Systems
Stimulation
C4I
TADL
VOICE
RTI
C4I BUILD
C4I INTERFACES
Generation of Link 11/16 Picture from simulated
AWACS/E2 OTCIXs/TRAP/TRE/TIBS
Common Operational Picture
TACTICAL C4I
WEAPONS SYS
OPERATIONAL C4I
NATIONAL C4I
RTI
VOICE
TACTICAL FORCES GENERATION
SIMULATION INTERFACE and GENERATION
Generation of simulated USN CVBG/ATF , Joint
Forces and OPFOR from Simulated Forces
Common Operational Picture
JECG/SIMULATION CONTROL
9
Hierarchy Boundaries

• GCCS Example
• Hierarchy 1 Operational Staff (JFMCC)
• Staff is delivered a managed GCCS COP
• Staff makes decisions based on managed COP
• Hierarchy 2 CVBG Staff
• Staff is delivered tactical COP inputs
• Staff must manage tactical inputs to deliver to
  higher HQ
• Hierarchy 3 Warfare Commanders
• Staff is delivered tactical data
• Staff must manage tactical data to deliver
  tactical COP inputs

10
Boundaries

• Each Simulated Environment requires its own
  boundaries dependent on requirements challenge
  is to identify all of them
• Each boundary has its own information
  requirements challenge is to define all of them
• Each boundary has its own control requirements
  challenge is to define how they work

11
Mensuration-4 Target Nomination with
Geo-Refinement Options(Engagement requests
geo-refinement)
12
Boundaries in a Federation

• What does this mean to a federation?
• Simulations require Federation
• Simulated environments must be compatible
• Boundary Points must support the Simulated
  Environment
• Hierarchical boundary points either
• Support one another
• Be compatible

13
Technical Implications Complex Simulated
Environments

• Multi-resolution tool chest
• Implies an HLA solution
• More resolution requires more data and
  preparations
• ATO
• MIDB
• Cultural and Natural Data
• Civil Processes (social, political, economic)
• Environments
• Terrain, ocean
• In-situ to serve Live, Virtual, Constructive mix

14
Transport - Architectural Considerations

• NETWORK CENTRIC
• Access
• Enabling Force
• Support to Information Management (Forcenet)
• 100s/1000s Sensors
• Shared Information/Knowledge
• ARCHITECTURE to support Joint and Naval
  Operations
• Capacity
• Dynamic Bandwidth
• Dynamic Access
• Advanced Networking and Management
• Interoperability

15
FBE JConnecting the Force
16
Seatel Ku Band Terminal

• Commercial Maritime Design
• Proven Reliability in worldwide commercial use
  and through 5 FBEs
• 120K off the shelf

17
Top Level and below
18
FBE J Networking Objectives

• Capacity - Three Ku networks
• Joint Strategic Link 14Mbps to JTASC (will
  increase to 45Mbps)
• Navy Operational semi-meshed network among Naval
  Forces
• 2-4 Mbps - Dynamic B/W Access
• experimental TDMA (4 MB/sec)
• Joint Compatibility - Employ ATM architecture to
  enable
• teleport capabilities with other services
• more efficient encryption (for VTC and VoIP)
• transport of serial (other than IP) signals
• Advanced Networking and Management- Improvements
  in transport layer to reduce satellite network
  latency effects
• TCP stack optimization
• Protocol Enhancement Proxies (PEPs)
• Class of Service and Quality of Service
  Management Issues
• Class - Source, Destination, and Port (Layer 3
  and 4)
• Quality - Multi Protocol Label Switching (Layer
  2)

19
FBE J Networking Objectives

• Advanced Applications - Multicast IP VTC
• Large Scale VTC application and management
• H323
• 12 Systems simultaneous
• Network Management - CISCO VoIP and MCUs
• Use of VoIP in previous FBEs has been less than
  successful
• CISCO demonstrated in small numbers to be
  successful in KB(X)
• Network Centric
• Link 16 over IP
• Tactical and Operational Voice (VoIP)
• Systems (NFN, GCCS, ADOCS, etc.)
• VTC
• High B/W tactical link to NP-3D
• Extend Hawkeye 2000 Q-70 LAN to the HSV
• Advanced Networking Capabilities adding
  additional capabilities
• BFTT to Sea
• Information Management
• Enabling Share Point Portal
• Collaborative Tools (IWS)