C4I Infrastructure - United States Naval Academy

Transcription

NTTP 6-02
NAVY TACTICS, TECHNIQUES, AND PROCEDURES
C4I INFRASTRUCTURE
NTTP 6-02
EDITION JANUARY 2005
DEPARTMENT OF THE NAVY
OFFICE OF THE CHIEF OF NAVAL OPERATIONS
DISTRIBUTION AUTHORIZED TO THE
DEPARTMENT OF DEFENSE AND U.S. DOD
CONTRACTORS ONLY FOR OPERATIONAL
USE TO PROTECT TECHNICAL DATA OR
INFORMATION FROM AUTOMATIC DISSEMINATION. THIS DETERMINATION WAS MADE
25 APRIL 2004. OTHER REQUESTS SHALL BE
REFERRED TO NAVY WARFARE DEVELOPMENT COMMAND, 686 CUSHING ROAD,
NEWPORT, RI 02841-1207.
URGENT CHANGE/ERRATUM RECORD
NUMBER
DATE
ENTERED BY
PRIMARY REVIEW AUTHORITY:
COMMANDER, NAVAL NETWORK
WARFARE COMMAND
0411LP1040346
1
JAN 2005
NTTP 6-02
INTENTIONALLY BLANK
JAN 2005
2
NTTP 6-02
INTENTIONALLY BLANK
JAN 2005
4
NTTP 6-02
January 2005
ROUTING
PUBLICATION NOTICE
1. NTTP 6-02 (JAN 2005), C4I INFRASTRUCTURE, is available in the Navy Warfare Library. It is effective upon receipt.
2. Summary. This edition provides a complete description of the network composition and
associated systems required for strike group command and control. Navy C4I systems and
networks from a carrier and expeditionary strike group perspective are presented with emphasis being placed on the C4I composition for individual and warfare mission areas.
Navy Warfare Library Custodian
Navy Warfare Library publications must be made
readily available to all users and other interested
personnel within the U.S. Navy.
Note to Navy Warfare Library Custodian
This notice should be duplicated for routing to cognizant personnel to keep them informed of changes to this
publication.
5
JAN 2005
NTTP 6-02
INTENTIONALLY BLANK
JAN 2005
6
NTTP 6-02
CONTENTS
Page
No.
CHAPTER 1 — INTRODUCTION
1.1
PURPOSE AND SCOPE.............................................................................................................. 1-1
1.2
INTENDED AUDIENCE............................................................................................................. 1-1
1.3
1.3.1
1.3.2
1.3.3
1.3.4
ORGANIZATION........................................................................................................................ 1-1
Chapter 1 — Introduction............................................................................................................. 1-1
Chapter 2 — Global and Shore Infrastructure .............................................................................. 1-1
Chapter 3 — Warfare Area C4I Architectures ............................................................................. 1-1
Chapter 4 — C4I Systems ............................................................................................................ 1-2
CHAPTER 2 — GLOBAL AND SHORE INFRASTRUCTURE
2.1
INTRODUCTION ........................................................................................................................ 2-1
2.2
2.2.1
2.2.2
2.2.3
SHORE INFRASTRUCTURE IN SUPPORT OF IT-21 ............................................................. 2-3
Overview....................................................................................................................................... 2-3
Fleet Satellite Access Procedures ................................................................................................. 2-8
Current Regional Area of Responsibility Architecture/Capabilities............................................. 2-8
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
NAVY SHORE NETWORKS AND INFRASTRUCTURE...................................................... 2-12
Fleet Network Operations Centers.............................................................................................. 2-12
Routing Architecture .................................................................................................................. 2-13
Navy/Marine Corps Intranet ....................................................................................................... 2-19
Overseas Navy Enterprise Network............................................................................................ 2-20
Joint Services Imagery Processing System Concentrator Architecture ...................................... 2-21
Video Information Exchange System ......................................................................................... 2-21
2.4
2.4.1
2.4.2
2.4.3
DEPARTMENT OF DEFENSE NETWORKS AND INFRASTRUCTURE............................ 2-23
DOD Teleport System ................................................................................................................ 2-23
Defense Information Systems Network...................................................................................... 2-25
Joint Worldwide Intelligence Communications System............................................................. 2-26
2.5
2.5.1
2.5.2
NAVAL MESSAGING SYSTEM ............................................................................................. 2-27
Defense Message System ........................................................................................................... 2-27
Afloat Messaging........................................................................................................................ 2-27
2.6
2.6.1
2.6.2
2.6.3
SUBMARINE COMMUNICATIONS....................................................................................... 2-28
Submarine Shore Communication Infrastructure ....................................................................... 2-28
Submarine Broadcast Controlling Authorities............................................................................ 2-28
Submarine Communications Capabilities................................................................................... 2-28
2.7
2.7.1
COMPUTER NETWORK DEFENSE ....................................................................................... 2-30
Defense in Depth ........................................................................................................................ 2-30
7
JAN 2005
NTTP 6-02
Page
No.
2.7.2
Computer Network Defense Organization ................................................................................. 2-30
CHAPTER 3 — WARFARE AREA C4I ARCHITECTURES
3.1
INTRODUCTION ........................................................................................................................ 3-1
3.2
COMMON TACTICAL PICTURE/COMMON OPERATIONAL PICTURE............................ 3-1
3.3
3.3.1
3.3.2
3.3.3
3.3.4
AIR DEFENSE............................................................................................................................. 3-2
Situational Awareness .................................................................................................................. 3-2
Planning and Coordination ........................................................................................................... 3-2
Control .......................................................................................................................................... 3-2
Reference ...................................................................................................................................... 3-2
3.4
3.4.1
3.4.2
3.4.3
3.4.4
SURFACE WARFARE................................................................................................................ 3-4
Control .......................................................................................................................................... 3-4
References..................................................................................................................................... 3-5
3.5
3.5.1
3.5.2
3.5.3
3.5.4
MINE WARFARE........................................................................................................................ 3-5
Control .......................................................................................................................................... 3-6
Reference ...................................................................................................................................... 3-6
3.6
3.6.1
3.6.2
3.6.3
3.6.4
ANTISUBMARINE WARFARE................................................................................................. 3-6
Control .......................................................................................................................................... 3-6
References..................................................................................................................................... 3-7
3.7
3.7.1
3.7.2
3.7.3
3.7.4
EXPEDITIONARY WARFARE.................................................................................................. 3-7
Control .......................................................................................................................................... 3-9
References..................................................................................................................................... 3-9
3.8
3.8.1
3.8.2
3.8.3
3.8.4
TLAM STRIKE ............................................................................................................................ 3-9
Control ........................................................................................................................................ 3-11
References................................................................................................................................... 3-11
3.9
3.9.1
3.9.2
3.9.3
3.9.4
EXPANDED MARITIME INTERCEPTION OPERATIONS .................................................. 3-11
Situational Awareness ................................................................................................................ 3-11
Planning and Coordination ......................................................................................................... 3-11
Control ........................................................................................................................................ 3-12
Reference .................................................................................................................................... 3-12
3.10
3.10.1
JOINT TASK FORCE OPERATIONS ...................................................................................... 3-12
JAN 2005
8
NTTP 6-02
Page
No.
3.10.2
3.10.3
Control ........................................................................................................................................ 3-13
3.11
3.11.1
3.11.2
3.11.3
ALLIED/COALITION OPERATIONS ..................................................................................... 3-13
Control ........................................................................................................................................ 3-14
CHAPTER 4 — C4I SYSTEMS
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.1.6
4.1.7
4.1.8
4.1.9
4.1.10
SATELLITE COMMUNICATIONS ........................................................................................... 4-1
Ultrahigh Frequency Satellite Communications........................................................................... 4-1
Super-High Frequency Defense Satellite Communications System............................................. 4-3
Commercial Wideband SATCOM Program................................................................................. 4-8
Wideband Gapfiller System.......................................................................................................... 4-9
Navy Extremely High Frequency Satellite Program .................................................................. 4-11
Mobile Subscriber Service (Iridium) .......................................................................................... 4-15
Inmarsat-B High Speed Data ...................................................................................................... 4-19
Global Broadcast Service ........................................................................................................... 4-20
Television Direct-to-Sailors........................................................................................................ 4-21
Fleet SATCOM Capabilities....................................................................................................... 4-22
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7
NON-SATCOM COMMUNICATIONS.................................................................................... 4-23
High Frequency and Configuration ............................................................................................ 4-23
Very-High-Frequency and Ultrahigh-Frequency Line-of-Sight Communications..................... 4-24
Digital Wideband Transmission System..................................................................................... 4-25
Tactical Switching System ......................................................................................................... 4-25
Enhanced Position Location Reporting System — Data Radio.................................................. 4-26
Very Low Frequency .................................................................................................................. 4-26
Extremely Low Frequency ......................................................................................................... 4-26
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.3.7
4.3.8
4.3.9
4.3.10
4.3.11
ADVANCED TACTICAL DATA LINKS ................................................................................ 4-27
Overview..................................................................................................................................... 4-27
Link 11........................................................................................................................................ 4-27
Link 4.......................................................................................................................................... 4-28
Link 16........................................................................................................................................ 4-29
Link 22........................................................................................................................................ 4-31
Satellite Link 11.......................................................................................................................... 4-32
Satellite Link 16.......................................................................................................................... 4-32
Joint Range Extension Application Protocol .............................................................................. 4-32
Cooperative Engagement Capability .......................................................................................... 4-32
Common Data Link–Navy.......................................................................................................... 4-34
SRQ-4 Hawklink ........................................................................................................................ 4-35
4.4
4.4.1
4.4.2
4.4.3
4.4.4
4.4.5
4.4.6
4.4.7
COMMAND AND CONTROL SYSTEMS............................................................................... 4-35
Global Command and Control System–Maritime ...................................................................... 4-35
Mine Warfare and Environmental Decision Aids Library.......................................................... 4-38
Theater Battle Management Core Systems................................................................................. 4-39
Joint Operation Planning and Execution System........................................................................ 4-40
TOMAHAWK Command and Control....................................................................................... 4-41
Advanced Field Artillery Tactical Data System ......................................................................... 4-42
Naval Fires Control System........................................................................................................ 4-42
9
JAN 2005
NTTP 6-02
Page
No.
4.4.8
4.4.9
4.4.10
Navy Tactical Command Support System.................................................................................. 4-43
AN/KSQ-1 Amphibious Assault Direction System.................................................................... 4-44
Meteorological and Oceanography Systems............................................................................... 4-44
4.5
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.5.7
INTELLIGENCE AND CRYPTOLOGIC SYSTEMS .............................................................. 4-46
Joint Services Imagery Processing System–Navy ...................................................................... 4-46
Global Command and Control System–Integrated Intelligence and Imagery ............................ 4-47
Cryptologic Unified Build .......................................................................................................... 4-47
Joint Deployable Intelligence Support System........................................................................... 4-48
Tactical Exploitation System–Navy ........................................................................................... 4-48
Integrated Broadcast System ...................................................................................................... 4-49
Surface Tactical Cryptologic Systems ........................................................................................ 4-53
4.6
4.6.1
4.6.2
4.6.3
4.6.4
SHIPBOARD NETWORKS ...................................................................................................... 4-55
C4I Afloat Networks................................................................................................................... 4-55
Sensitive Compartmented Information Networks ...................................................................... 4-55
Automated Digital Network System........................................................................................... 4-56
Radiant Mercury ......................................................................................................................... 4-57
4.7
4.7.1
4.7.2
4.7.3
4.7.4
COLLABORATIVE TOOLS ..................................................................................................... 4-58
Collaboration at Sea.................................................................................................................... 4-58
Task Force Web/Navy Enterprise Portal .................................................................................... 4-58
Intra-Amphibious Ready Group Distributive Collaborative Planning ....................................... 4-60
Defense Collaboration Tool Suite............................................................................................... 4-60
4.8
4.8.1
4.8.2
MESSAGING SYSTEMS .......................................................................................................... 4-60
Defense Message System ........................................................................................................... 4-60
Components and Functions......................................................................................................... 4-61
4.9
4.9.1
4.9.2
4.9.3
4.9.4
ALLIED AND COALITION INTEROPERABILITY............................................................... 4-62
Combined Enterprise Regional Information Exchange Systems................................................ 4-62
Strike Force Electronic Mail 66.................................................................................................. 4-63
NATO Initial Data Transfer System........................................................................................... 4-63
Coalition Convergence ............................................................................................................... 4-63
JAN 2005
10
NTTP 6-02
LIST OF ILLUSTRATIONS
Page
No.
CHAPTER 2 — GLOBAL AND SHORE INFRASTRUCTURE
Figure 2-1.
Figure 2-2.
Figure 2-3.
Figure 2-4.
Figure 2-5.
Figure 2-6.
Figure 2-7.
Figure 2-8.
Figure 2-9.
Figure 2-10.
Figure 2-11.
Figure 2-12.
Figure 2-13.
Figure 2-14.
Figure 2-15.
Figure 2-16.
Original IT-21 Bandwidth Requirements................................................................................. 2-4
IT-21 Capabilities Matrix......................................................................................................... 2-4
2007 Estimated Mission Bandwidth Requirements ................................................................. 2-5
Navy Shore Connectivity ......................................................................................................... 2-7
ADNS AOR Autonomous Routing System ........................................................................... 2-14
ADNS AOR Connectivity ...................................................................................................... 2-15
Present NOC ADNS Routing Configuration.......................................................................... 2-15
Present Ship ADNS Routing Configuration........................................................................... 2-16
Future ADNS AOR Black Routing Configuration................................................................. 2-17
Proposed NOC Black Routing Configuration ........................................................................ 2-18
Future Ship Black Routing Configuration.............................................................................. 2-18
NMCI Connectivity to Afloat Forces ..................................................................................... 2-20
Notional JCA.......................................................................................................................... 2-22
DOD Teleport Generation One .............................................................................................. 2-24
DOD Teleport Generation Two.............................................................................................. 2-25
SSN Wideband Communications ........................................................................................... 2-29
CHAPTER 3 — WARFARE AREA C4I ARCHITECTURES
Figure 3-1.
Figure 3-2.
Figure 3-3.
Figure 3-4.
Figure 3-5.
Figure 3-6.
Figure 3-7.
Figure 3-8.
Figure 3-9.
Notional Air Defense C2 Architecture (Single CSG) .............................................................. 3-3
Notional Air Defense C2 Architecture (Multi-SG) .................................................................. 3-3
Notional SUW C2 Architecture ............................................................................................... 3-4
Notional Mine Warfare C2 Architecture.................................................................................. 3-5
Notional ASW Warfare C2 Architecture ................................................................................. 3-7
Notional Expeditionary Warfare C2 Architecture.................................................................... 3-8
Notional TLAM Strike C2 Architecture................................................................................. 3-10
Notional EMIO Warfare C2 Architecture .............................................................................. 3-12
Notional Allied/Coalition C2 Architecture ............................................................................ 3-14
CHAPTER 4 — C4I SYSTEMS
Figure 4-1.
Figure 4-2.
Figure 4-3.
Figure 4-4.
Figure 4-5.
Figure 4-6.
Figure 4-7.
Figure 4-8.
Figure 4-9.
Figure 4-10.
Figure 4-11.
Figure 4-12.
Demand Assigned Multiple Access.......................................................................................... 4-2
UHF Space Segment ................................................................................................................ 4-4
Ground Mobile Force SHF....................................................................................................... 4-5
Primary Navy DSCS Step Sites and Shore Architecture.......................................................... 4-6
SHF DSCS Space Segment ...................................................................................................... 4-7
AN/WSC-6 Variants................................................................................................................. 4-8
CWSP Architecture ................................................................................................................ 4-10
EHF Limited Low Data Rate.................................................................................................. 4-13
EHF Medium Data Rate ......................................................................................................... 4-13
Polar EHF............................................................................................................................... 4-14
EHF Space Segment............................................................................................................... 4-15
EHF Ground Segment ............................................................................................................ 4-17
11
JAN 2005
NTTP 6-02
Page
No.
Figure 4-13.
Figure 4-14.
Figure 4-15.
Figure 4-16.
Figure 4-17.
Figure 4-18.
Figure 4-19.
Figure 4-20.
Figure 4-21.
Figure 4-22.
Figure 4-23.
Figure 4-24.
JAN 2005
Iridium Ground Architecture.................................................................................................. 4-18
Iridium Space Segment .......................................................................................................... 4-18
Inmarsat Architecture ............................................................................................................. 4-20
GBS Spot Beams .................................................................................................................... 4-21
TV-DTS Architecture............................................................................................................. 4-22
SATCOM Distribution by Ship Class .................................................................................... 4-23
USN Link 11 Systems ............................................................................................................ 4-28
USN Link 4 Systems .............................................................................................................. 4-29
USN Link 16 Systems ............................................................................................................ 4-30
Planned Installation of Link 22 Systems ................................................................................ 4-31
Radiant Mercury..................................................................................................................... 4-57
Defense Messaging System.................................................................................................... 4-62
12
NTTP 6-02
PREFACE
NTTP 6-02 (JAN 2005), C4I Infrastructure, provides a complete description of the network composition and
associated systems required for strike group command and control. Navy C4I systems and networks from a carrier
and expeditionary strike group perspective are presented with emphasis being placed on the C4I composition for
individual and warfare mission areas.
The rapidly increasing joint nature of carrier and expeditionary strike group operations and their dependence on
joint networks and systems is reflected in NTTP 6-02 (JAN 2005).
Throughout this publication, references to other publications imply the effective edition.
Report any page shortage by letter to Commander, Navy Warfare Development Command.
ORDERING DATA
Order a new publication or change, as appropriate, through the Navy Supply System.
Changes to the distribution and allowance lists (to add or delete your command from the distribution list, or to
modify the number of copies of a publication that you receive) must be made in accordance with NTTP 1-01.
RECOMMENDED CHANGES
Recommended changes to this publication may be submitted at any time using the accompanying format for
routine changes.
Fleet units and stations submit recommendations to:
COMMANDER
NAVY WARFARE DEVELOPMENT COMMAND
DOCTRINE DIRECTOR (N5)
686 CUSHING ROAD
NEWPORT RI 02841-1207
WEB-BASED CHANGE SUBMISSIONS
Recommended change submissions for this publication may be submitted to the Navy doctrine discussion group
site. This discussion group may be accessed through the Navy Warfare Development Command (NWDC)
SIPRNET website at http://www.nwdc.navy.smil.mil/.
URGENT CHANGE RECOMMENDATIONS
When items for changes are considered to be urgent (as defined in NTTP 1-01 and including matters of safety),
this information shall be sent by message (see accompanying sample message format) to PRA, with information
copies to Navy Warfare Development Command, and all other commands concerned, clearly explaining the
proposed change. Information addressees should comment as appropriate. See NTTP 1-01.
13
JAN 2005
NTTP 6-02
JAN 2005
14
NTTP 6-02
FM ORIGINATOR
TO COMNAVNETWARCOM//JJJ//
INFO COMNAVWARDEVCOM NEWPORT RI//N5//
BT
Others as appropriate
CLASSIFICATION//N03510//
MSGID/GENADMIN/(As required)//
SUBJ/URGENT CHANGE RECOMMENDATION FOR NTTP 6-02 (JAN 2005)//
REF/A/DOC/NWDC//
AMPN/REF A IS NTTP 1-01 (REV. B), THE NAVY WARFARE LIBRARY//
POC/(As required)//
RMKS/1. IAW REF A URGENT (SAFETY) CHANGE IS RECOMMENDED FOR NTTP 6-02 (JAN 2005)
2. PAGE ______ ART/PARA NO ______ LINE NO ______ FIG NO ______
3. PROPOSED NEW TEXT (Include classification)
4. JUSTIFICATION.
BT
Message provided for subject matter; ensure that actual message conforms to MTF requirements.
15
JAN 2005
NTTP 6-02
CHANGE SYMBOLS
Revised text in changes is indicated by a black vertical line in the outside margin of the page, like the one printed
next to this paragraph. The change symbol shows where there has been a change. The change might be material
added or information restated. A change symbol in the outside margin by the chapter number and title indicates a
new or completely revised chapter.
WARNINGS, CAUTIONS, AND NOTES
The following definitions apply to “WARNINGs,” “CAUTIONs,” and “Notes” found throughout the manual.
An operating procedure, practice, or condition that may result in injury or death if not carefully
observed or followed.
An operating procedure, practice, or condition that may result in damage to equipment if not
carefully observed or followed.
Note
An operating procedure, practice, or condition that is essential to emphasize.
WORDING
The concept of word usage and intended meaning which has been adhered to in preparing this publication is as
follows:
“Shall” has been used only when application of a procedure is mandatory.
“Should” has been used only when application of a procedure is recommended.
“May” and “need not” have been used only when application of a procedure is optional.
“Will” has been used only to indicate futurity, never to indicate any degree of requirement for application of a
procedure.
JAN 2005
16
NTTP 6-02
CHAPTER 1
Introduction
1.1 PURPOSE AND SCOPE
The focus of NTTP 6-02 (JAN 2005) is to provide the user with an end-to-end description of the network
architectures and associated systems required for strike group (SG) command and control (C2). It presents Navy
command, control, communications, computers, and intelligence (C4I) systems and networks from a carrier strike
group (CSG)/expeditionary strike group (ESG) perspective with an emphasis on the C4I architectures for
individual warfare and mission areas. Theater and global command, control, communications, computers,
intelligence, surveillance, and reconnaissance (C4ISR) networks are presented from the perspective of how the
SG interfaces with them.
The NTTP reflects the rapidly increasing joint nature of CSG/ESG operations and their corresponding
dependence on joint networks and systems. For this NTTP, joint networks and systems are presented from the
perspective of how the SG interfaces with them.
1.2 INTENDED AUDIENCE
The intended audiences are naval officers involved in CSG/ESG C4I planning, and C4I planners from other
services requiring a broad and comprehensive overview of CSG/ESG C4I architectures and capabilities. It is also
a resource for senior officers, commanding officers, and staff officers.
1.3 ORGANIZATION
1.3.1 Chapter 1 — Introduction
1.3.2 Chapter 2 — Global and Shore Infrastructure
Theater and global C4ISR networks are presented from the perspective of how the SG interfaces with them. A
comprehensive description of the Navy’s shore infrastructure is presented within this framework.
1.3.3 Chapter 3 — Warfare Area C4I Architectures
This chapter will present C4I systems and architectures within a warfare framework. A notional C4I architecture
for different warfare and mission areas will be presented along with a breakdown of associated systems into the
following functional categories:
1. Situational awareness (SA)
2. Planning and coordination
3. Control.
This chapter will have a systems perspective and does not address warfare tactics, techniques, and procedures
(TTP) for each specific warfare area.
1-1
JAN 2005
NTTP 6-02
1.3.4 Chapter 4 — C4I Systems
Brief but detailed functional and technical descriptions of Navy C4I systems are presented. This NTTP does not
address techniques and procedures for each individual C4I system as these are addressed in other referenced
publications.
JAN 2005
1-2
NTTP 6-02
CHAPTER 2
Global and Shore Infrastructure
2.1 INTRODUCTION
The Navy’s information technology for the twenty-first century (IT-21) strategy was designed to deliver the
following capabilities to the afloat operating forces:
1. Extensive use of web technology to manage data to produce knowledge
2. Seamless ashore/afloat transfer of voice, video, and data information
3. Transmission control protocol/internet protocol (TCP/IP)-based, client-server environment with multilevel security
4. Merging of tactical and nontactical data on a common infrastructure
5. A global Department of the Navy (DON) networking architecture to ensure interoperability
6. Improved shipboard C2 capabilities and improved planning and decision tools
7. Robust shipboard local area networks (LANs)
8. Matching capacity upgrades at shore communications hubs
9. Improved information assurance and security.
The Navy’s goal is to transition from a collection of stove-piped communications systems to an integrated,
network-centric environment of voice, video, and data exchange using a global IP communications architecture
focused on the decision maker to provide the warfighter a global network backbone integrated across all naval
missions and functional areas.
Note
While this and other publications refer to IT-21 networks, IT-21 is not a network or
a system per se, but rather an acquisition strategy designed to meld many disparate
programs and systems into a single coherent and modern information technology
infrastructure for afloat naval units. IT-21 also plays a critical role in establishing
Navy-wide standards for software, hardware, and information formats.
With IT-21 as the foundation, FORCEnet is the follow-on initiative that will provide the next generation
integrated C4ISR capabilities. FORCEnet, as defined by CNO, is “The operational construct and architectural
framework for Naval Warfare in the Information Age, integrating warriors, sensors, command and control,
platforms, and weapons into a networked, distributed combat force.”
The following identifies capabilities as necessary to implement the FORCEnet concept:
2-1
JAN 2005
NTTP 6-02
1. The ability to provide robust, reliable communication to all nodes, based on the varying information
requirements and capabilities of those nodes.
2. The ability to provide reliable, accurate, and timely location, identity, and status information on all friendly
forces, units, activities, and entities/individuals.
3. The ability to provide reliable, accurate, and timely location, identification, tracking, and engagement
information on environmental, neutral and hostile elements, activities, events, sites, platforms, and
individuals.
4. The ability to store, catalogue, and retrieve all information produced by any node on the network in a
comprehensive, standard repository so that the information is readily accessible to all nodes and
compatible with the forms required by any nodes, within security restrictions.
5. The ability to process, sort, analyze, evaluate, and synthesize large amounts of disparate information while
still providing direct access to raw data as required.
6. The ability of each decision maker to depict situational information in a tailorable, user-defined, shareable,
primarily visual representation.
7. The ability of distributed groups of decision makers to cooperate in the performance of common command
and control activities by means of a collaborative work environment.
8. The ability to automate certain lower-order command and control subprocesses and to use intelligent
agents and automated decision aids to assist people in performing higher-order subprocesses, such as
gaining situational awareness and devising concepts of operations.
9. The ability to provide information assurance.
10. The ability to function in multiple security domains and multiple security levels within a domain, and to
manage access dynamically.
11. The ability to interoperate with command and control systems of very different types and levels of
sophistication.
12. The ability of individual nodes to function while temporarily disconnected from the network.
13. The ability automatically and adaptively to monitor and manage the functioning of the command and
control system to ensure effective and efficient operation and to diagnose problems and make repairs as
needed.
14. The ability to incorporate new capabilities into the system quickly without causing undue disruption to the
performance of the system.
15. Ultimately, the ability to make and implement good decisions quickly under conditions of uncertainty,
friction, time pressure, and other stresses.
FORCEnet, in turn, is the Navy component of the Department of Defense (DOD) Global Information Grid (GIG),
which is envisioned by the Joint Chiefs of Staff (JCS) as:
JAN 2005
2-2
NTTP 6-02
1. A single secure grid providing seamless end-to-end capabilities to all warfighting, national security, and
support users
2. Supporting DOD and intelligence community requirements from peacetime business support through all
levels of conflict
3. Joint, high-capacity netted operations
4. Fused with weapons systems
5. Supporting strategic, operational, tactical and base/post/camp/station
6. Plug and play interoperability
7. Guaranteed for U.S. and allied users
8. Connectivity for coalition users
9. Tactical and functional fusion a reality
10. Information/bandwidth on demand
11. Defense in depth against all threats.
FORCEnet and GIG requirements are the driving forces behind an ongoing transformation of Navy and DOD
shore infrastructure and satellite communications (SATCOM) systems. This transformation will take at least ten
years to complete and consequently is beyond the scope of this NTTP, but it must be understood that the Navy’s
C4I infrastructure will be in a state of constant change for the foreseeable future as new systems and capabilities
are introduced.
2.2 SHORE INFRASTRUCTURE IN SUPPORT OF IT-21
2.2.1 Overview
IT-21 established minimum bandwidth requirements for Navy ships. These requirements, depicted in Figure 2-1
were, and continue to be, a critical driver in the development of the Navy’s C4I infrastructure. They established
128 kilobits per second (kbps) as the minimum “core” bandwidth for all naval combatants, with additional
bandwidth for specific ships to support additional operational requirements for imagery, collaborative planning,
targeting, and other high bandwidth applications.
In support of IT-21, the 1997 Seattle Agreement defined mission bandwidth requirements for the combatant
commander (COCOM). It established an IT-21 core capability of 128 kbps for all ship classes for fielding a common
tactical picture (CTP) (comprising a common operating picture (COP) and a tactical data network (TDN)). In
addition to the IT-21 core capabilities, requirements for primary imagery and collaborative planning among
flagships, carriers, and large deck amphibious ships that added 768 kbps and 384 kbps respectively were levied.
Certain IT-21 capabilities were defined for the various ship classes within the United States Navy (USN). These
capabilities include radio frequency (RF) management, reachback, wideband receive, internal distribution, secure
processing, and survivable communications. Figure 2-2 relates these various IT-21 capabilities to ship class.
Subsequent to the original Seattle Agreement, mission bandwidth requirements for the fleet have been revised and
projected out to the year 2007. This established an amended core capability of 2652 kbps among ship classes
using SECRET Internet Protocol Router Network (SIPRNET), Non-Secure Internet Protocol Router Network
(NIPRNET), secure voice (SECVOX), and Joint Worldwide Intelligence Communications System (JWICS), and
other applications.
2-3
JAN 2005
NTTP 6-02
Figure 2-1. Original IT-21 Bandwidth Requirements
IT-21 FULL CAPABILITY MATRIX
RF
MANAGEMENT
REACHBACK
WIDEBAND
RECEIVE
INTERNAL
DISTRIBUTION
SECURE
PROCESSING
SURVIVABLE
COMMUNICATIONS
FLAGSHIPS
ADNS/5/25 KHZ
CWSP/SHF
CWSP/SHF/
GBS/DWTS
GIG-E
NETWORK
GCCS-M/
NTCSS
EHF MDR
CV/CVN
ADNS/5/25 KHZ
CWSP/SHF
CWSP/SHF/
GBS
GIG-E
NETWORK
GCCS-M/
NTCSS
EHF MDR
CG
ADNS/5/25 KHZ
INMARSAT B/
SHF
INMARSAT B/
SHF/GBS
GIG-E
NETWORK
GCCS-M/
NTCSS
EHF MDR
DD
ADNS/5/25 KHZ
INMARSAT B
INMARSAT B/
GBS
100 MB
GCCS-M/
NTCSS
EHF MDR
DDG
ADNS/5/25 KHZ
INMARSAT B
INMARSAT B/
GBS
GIG-E
NETWORK
GCCS-M/
NTCSS
EHF MDR
FFG/AOE/TAE/TAO
ADNS/5/25 KHZ
INMARSAT B
INMARSAT B/
GBS
100 MB
GCCS-M/
NTCSS
LHA/LHD
ADNS/5/25 KHZ
CWSP/SHF
CWSP/SHF/
GBS/DWTS
GIG-E
NETWORK
GCCS-M/
NTCSS
EHF MDR
LPD/LSD
ADNS/5/25 KHZ
INMARSAT B/
SHF
INMARSAT B/
SHF/GBS/DWTS
100 MB
GCCS-M/
NTCSS
EHF MDR
SSBN/SSN
ADNS/
Mini-DAMA
EHF MDR
HDR/UHF
ASYMMETRIC
GIG-E
NETWORK
GCCS-M/
NTCSS
EHF MDR
GIG-E = Gigabit Ethernet
Figure 2-2. IT-21 Capabilities Matrix
JAN 2005
2-4
NTTP 6-02
Added to this core capability were requirements for primary imagery and collaborative planning among flagships,
carriers, and large deck amphibious ships that added 11544 kbps and 11178 kbps respectively. Figure 2-3
summarizes the projected COCOM mission bandwidth requirements affecting the various ship classes for the
2007 timeframe.
To meet these bandwidth requirements, the Navy uses the following SATCOM systems:
1. Super-high frequency (SHF) Defense Satellite Communications System (DSCS)
2. Commercial wideband satellite program (CWSP)
3. Navy extremely high frequency (EHF) satellite program (NESP) low data rate (LDR)/medium data rate
(MDR)
4. Ultrahigh frequency (UHF) SATCOM
5. Global Broadcast Service (GBS)
6. Inmarsat-B high speed data (HSD).
Note
Each of these systems is described in detail in Chapter 4.
Mission Bandwidth Requirements
(Template for Combatant Commander 2007 Estimates)
CV/ CVN
AGF / LCC
Precision
Engagement
CJTF
JFACC
22722 kbps – Total
11544 kbps
LHA / LHD
LSD / LPD
OMFTS
CG
DDG
AADC
TMD
DD/FFG
*SUB
*As Equipped
(Contrast with 1997 requirements of 1280 kbps)
Primary Imagery
11178 kbps
Collaborative Planning
SIPRNET - 2007 kbps Voice - 1126 kbps
VTC - 512 kbps
NIRNET - 3350 kbps
Other - 2176 kbps
JWICS - 2007 kbps
5251 kbps
8483 kbps
4939 kbps
SIPR - 926
NIPR - 1080
VOX - 352
VTC - 512
JWICS - 1229
Other - 1152
SIPR - 614
NIPR - 1080
VOX - 352
VTC - 512
JWICS - 1229
Other - 4696
SIPR - 614
NIPR - 1080
VOX - 352
VTC - 512
JWICS - 1229
Other - 1152
2007 CORE
CAPABILITY
2652 kbps
2652 kbps
SIPRNET – 614 kbps NIPRNET – 384 kbps VOX – 323 kbps JWICS – 307 kbps
Other – 1024 kbps
AADC – Area Air Defense Commander
CJTF – Commander Joint Task Force
JFACC – Joint Force Air Component Commander
OMFTS – Operational Maneuver From the Sea
TMD – Theater Missile Defense
Figure 2-3. 2007 Estimated Mission Bandwidth Requirements
2-5
JAN 2005
NTTP 6-02
With the exception of EHF and UHF SATCOM, each satellite system connects to a group of earth stations that
are distributed around the world. These groups of satellite earth stations are then linked together through five
primary Navy shore sites:
1. Naval Computer and Telecommunications Area Master Station Pacific (NCTAMS PAC) Wahiawa, HI
2. NCTAMS Atlantic (LANT) Norfolk, VA
3. NCTAMS Europe Central (EURCENT) Naples (Capodochino), Italy
4. Naval Computer and Telecommunications Station (NCTS) San Diego, CA
5. NCTS Bahrain Manama, Bahrain.
EHF and UHF SATCOM ground terminals are located at the NCTAMS, NCTS, and other C2 nodes. See Chapter
4, Paragraphs 4.1.1 and 4.1.5 for details.
The shore connectivity architecture is periodically modified to best support operational needs. As such the
diagrams depicting this connectivity should be considered notional. Current status and connectivity information
can be found at http://C4.nnsoc.navy.smil.mil/global/.
Each NCTAMS provides operational guidance to area NCTAMS detachments (NCTAMS DETs) and NCTS as
listed below:
NCTAMS AREA
NCTSs
NCTAMS
PACIFIC (PAC)
(Honolulu, HI)
NCTS San Diego, CA
NCTS Puget Sound, WA
NCTS Far East Yokosuka, JA
NCTS Guam
NCTS Diego Garcia
NCTAMS
EUROPE
CENTRAL
(EURCENT)
(Naples, IT)
NCTS Bahrain
NCTAMS
ATLANTIC
(LANT)
(Norfolk, VA)
NCTS Sigonella, Italy
NCTAMS EURCENT DET London, UK
NCTAMS EURCENT DET Rota, SP
NCTAMS EURCENT DET Souda Bay,
GR
NCTS Keflavik, IC
NCTS Jacksonville, FL
NCTS Pensacola, FL
NCTS Washington, DC
NCTAMS LANT DET Brunswick, ME
NCTAMS LANT DET Cutler, ME
NCTAMS LANT DET Guantanamo
Bay, CU
NCTAMS LANT DET Hampton Roads,
VA
JAN 2005
2-6
2-7
NTTP 6-02
JAN 2005
Figure 2-4. Navy Shore Connectivity
NTTP 6-02
A key feature and limitation of Navy afloat communications is their dependence on these central shore sites. All
high bandwidth, networked SG C4I architectures are hub and spoke arrangements with communications between
ships routed through a shore site. Two ships within sight of each other might have a five thousand mile
communications path between them if, for example, one ship was using SHF and the other, Inmarsat.
Implementation of EHF time division multiple access (TDMA) interface processor (TIP) will allow the CSG/ESG
to use fewer resources on EHF within a spot beam than what is currently used by the spoke wheel configuration
of today's network and allow for intra–strike group (SG) IP-based traffic to continue without the support of a
shore node. TIP will do this by using a “pulling” network on EHF that allows all users in that network to
interconnect their IP services within the net they are connected to. With an average throughput per user of 77 kbps
on a network with an aggregate bandwidth of 512 kbps, six users in the net during the testing phase are allowed.
Figure 2-4 depicts Navy shore connectivity among DSCS, CWSP and Inmarsat ground stations, and Navy
NCTAMS and NCTS. It is a notional depiction in that the size of the terrestrial connections shown change
frequently due to operational requirements.
2.2.2 Fleet Satellite Access Procedures
Satellite access for all DOD users is governed by the Joint Staff through the CJCSI 6250.01 approval process,
which mandates that all requirements first be validated by the user's combatant commander and approved by the
joint staff. Bandwidth allocated to the Navy is controlled by Commander, Fleet Forces Command (CFFC) and
Commander, Pacific Fleet (CPF).
Satellite access for CSGs and ESGs is controlled by either CFFC, CPF, Commander, Naval Forces Europe (CNE),
or Commander, United States Naval Forces Central Command (CUSNC) depending on their chain of command. As
a general rule the SG staff will consolidate satellite access requirements for the entire SG and submit a consolidated
request to the appropriate numbered fleet (Second, Third, Fifth, Sixth, and Seventh fleets). Each fleet’s satellite
access procedures are contained in the communications annexes to their operations orders (OPORDs). The fleet N6
will then validate the request and forward it on to the Naval Network Warfare Command for final approval (with
the exception of C5F — they are the same staff as CUSNC so numbered fleet validation is fleet commander
approval).
References:
1. Commander, Second Fleet OPORD 2000 Annex K
2. Commander, Third Fleet OPORD 201 Annex K
3. Commander, Seventh Fleet Instruction C2000.1H
4. Commander, United States Naval Forces Central Command/Commander Fifth Fleet OPORD 1000-01.
2.2.3 Current Regional Area of Responsibility Architecture/Capabilities
2.2.3.1 Pacific AOR
The PAC AOR extends from approximately 105° east latitude to the western coast of the United States. Ships
operating in the PAC fleet AOR receive primary communications support from NCTAMS PAC located at
Wahiawa, HI.
SHF DSCS SATCOM is terminated at the Naval Satellite Communications Facility (NAVSATCOMMFAC)
Wahiawa. Existing infrastructure supports SHF termination for up to 21 ships simultaneously (7 on the eastern
Pacific Ocean (EASTPAC) DSCS satellite, 7 on the western Pacific Ocean (WESTPAC) DSCS satellite, and 7 on
the EASTPAC DSCS residual satellite). If an increase in capability is required on another terminal, existing
modems can be crosspatched to each other’s terminals up to the maximum number of available converters
JAN 2005
2-8
NTTP 6-02
reserved for tactical use on each terminal. Additionally, teleport sites at Fort Buckner, Okinawa, and Camp
Roberts, CA, can terminate 5 additional units for a total of 26 terminations in the Pacific AOR.
CWSP services are terminated in two locations: first at Commercial Earth Station (CES) Steele Valley, CA,
utilizing IS-804 at 176E (5 E-1s) (E1= 2.048 megabits per second (Mbps) data throughput), and AMC-1 (6 E-1s)
and backhauled to NCTS San Diego. From NCTS San Diego, NIPRNET and SIPRNET circuits are backhauled to
NCTAMS PAC. The second termination point is located at CES Pearl City, HI, utilizing IS-604 at 157E (4 E-1s)
with all circuits backhauled to NCTAMS PAC. This existing infrastructure supports the termination of 17 ships.
The space segments on AMC-1 are shared between Steele Valley and Holmdel with 6 E-1s and 2 E-1s
respectively.
The GBS primary injection point (PIP) and satellite broadcast management (SBM) center is located at NCTAMS
PAC located in Wahiawa, HI and provides access to the UFO-8 satellite, which is equipped with five (four active,
one spare) GBS transponders of 23.5 Mbps each, for a total of 94 Mbps per satellite. Data is transmitted to users
from the satellite via three steerable spot beam antennas. Two of these cover an area of 500 nautical miles (nm)
radius and support a nominal data rate of 23.5 Mbps. The third downlink is a wide spot beam that covers an area
of about 2,000 nm radius and supports a data range of 12–23.5 Mbps.
Inmarsat-B HSD service in the PAC AOR is provided by three satellites, the 109E (Indian Ocean region (IOR)),
142W (Pacific Ocean region (POR)), and the 143.5E (IOR) satellites. Ships operating from 20° east to the
continental United States (CONUS) operate through the 142W (POR)/143.5E (IOR) satellite with commercial
SATCOM land Earth station (LES) at Auckland, NZ, and are also terminated at NCTAMS PAC.
Inmarsat connectivity is constrained at three levels: NCTAMS termination equipment, terrestrial connectivity
limitations, and available satellite channels. The existing infrastructure at NCTAMS PAC can accommodate a
maximum of 70 Inmarsat-B HSD terminations (54 voice/data and 16 data-only terminations). The LES is, by
contract, capable of landing 50 legacy 64 kbps channels. The existing terrestrial connectivity infrastructure (three
T-1s) (T1 = 1.544 Mbps data throughput) is capable of supporting up to 72 legacy 64 kbps Inmarsat-B HSD
terminations from the LES at Auckland, NZ, supporting the 109E (IOR) with 24 leases, 142W (POR) with 30
leases, and 143.5E (IOR) with 8 leases of satellite service. NCTAMS PAC has a theoretical channel capability of
up to 66 channels. However, the USN is not the only customer competing for the assets, and therefore not all 66
may be available.
2.2.3.2 Atlantic AOR
Geographically, the LANT AOR extends from the east coast of the United States to approximately 5° west
longitude where the United States Navy Europe (NAVEUR) Command AOR begins. Commander, Fleet Forces
Command (COMFLTFORCOM) policy is that any Navy vessel operating in the LANT AOR will terminate
communications at NCTAMS LANT located in Norfolk, VA.
SHF DSCS SATCOM is supported at NAVSATCOMMFAC Northwest located in Chesapeake, VA (also a DOD
teleport site referred to as “Northwest Teleport”). NAVSATCOMMFAC Northwest, VA, has sufficient modems
to support 23 SHF terminations simultaneously. The current configuration is aligned to support eight terminations
on the western Atlantic (WESTLANT) SATCOM terminal, eight terminations on the eastern Atlantic
(EASTLANT) SATCOM terminal, and seven terminations on the middle Atlantic (MIDLANT) residual utilizing
the recently activated satcom terminal. Given the degree of overlap between respective footprints of the
WESTLANT and EASTLANT DSCS satellites, the 23 terminations are available throughout the LANT AOR. If
an increase in capability is required on either terminal, existing modems can be crosspatched to each terminal up
to the maximum number of available converters reserved for tactical use on each terminal.
CWSP commercial C-band is terminated at CES Holmdel, NJ. Coverage is provided through the following
satellites: AMC-9 at 27.5E (4 E-1s), IntelSat (ISAT) 706 at 30.7E (3 E-1s), and AMC-1 at 25.7E (2 E-1s). This
existing infrastructure supports the termination of nine ships. The space segments on AMC-1 are shared between
Steele Valley and Holmdel with 6 E-1s and 2 E-1s respectively.
2-9
JAN 2005
NTTP 6-02
The GBS PIP and SBM center is located at NCTAMS LANT located in Norfolk, VA, and provides access to the
UFO-9 satellite, which is equipped with four GBS transponders of 23.5 Mbps each, for a total of 94 Mbps per
satellite. Data is transmitted to users from the satellite via three steerable spot beam antennas. Two of these cover
an area of 500 nm radius and support a nominal data rate of 23.5 Mbps. The third downlink is a wide spot beam
that covers an area of about 2,000 nm radius, and supports a data range of 12–23.5 Mbps.
Inmarsat-B HSD service in the LANT AOR is provided by the 98W (AOR-W) with 30 leases on the satellite. The
AOR-W satellite’s footprint covers from 179° west, in the Pacific, eastward to 20° west in the Atlantic. It is
anticipated that service via the AOR-W satellite will be used by the Atlantic Fleet only. Channels are supported
by the commercial SATCOM LES at Laurentides, Canada, and terminated at NCTAMS LANT Norfolk, VA.
limitations, and available satellite channels. NCTAMS LANT is outfitted with termination equipment to support
48 channels. The LES is, by contract, capable of landing 50 legacy 64 kbps channels. Current terrestrial
connectivity (two T-1s) can support up to 48 legacy 64 kbps Inmarsat-B HSD terminations. NCTAMS LANT has
a theoretical channel capability of up to 48 channels. However, the USN is not the only customer competing for
the assets, and therefore not all 48 may be available.
In all cases, the aggregate of the satellite links are backhauled over terrestrial links (commercial or Defense
Information Systems Network (DISN)) to NCTAMS LANT for distribution to individual users or product
sources. Obtaining terrestrial connectivity from the various SATCOM Earth terminals to NCTAMS LANT is low
risk as the terrestrial connectivity is shore-based and within CONUS.
2.2.3.3 EUROPEAN AOR
The NAVEUR AOR reaches from approximately 5° west to 35° east latitude. Commander, United States Naval
Forces, Europe (COMUSNAVEUR) policy is that any Navy vessel operating in the NAVEUR AOR will
terminate communications at NCTAMS EURCENT located in Naples, Italy.
SHF DSCS SATCOM is supported at NAVSATCOMMFAC Lago di Patria, Italy (also known as “Lago di Patria
Teleport”). NAVSATCOMMFAC Lago di Patria, Italy, is currently allocated to support 24 SHF terminations
simultaneously (eight WESTLANT, nine EASTLANT, and seven on the Indian Ocean (IO) residual satellite).
NAVEUR CWSP commercial C-band is terminated at CES Holmdel, NJ, CES Martlesham, UK, and CES
Madley, UK, utilizing IS-707 at 359E (8 E-1s), IS-906 at 64E (4 E-1s), and IS-704 at 66E (7 E-1s). EURCENT
units terminating C-band with Martlesham, UK, requires that these circuits be transported via transoceanic cable
from NCTAMS LANT to Martlesham, UK. The actual number of E-1s available to units operating in the
Mediterranean depends on unit placement and the number of E-1s used by units operating in the IO. This existing
infrastructure supports the termination of 19 ships. The space segments on all three satellites are shared between
fleet commanders on an as-needed basis.
The NAVEUR GBS PIP and SBM center is located at the NCTS in Sigonella, Italy, and provides access to the
UFO-9 and UFO-10 satellites, which provide coverage to the eastern LANT and the Mediterranean respectively.
Each satellite is equipped with four GBS transponders of 23.5 Mbps each, for a total of 94 Mbps per satellite.
Data is transmitted to users from the satellite via three steerable spot beam antennas. Two of these cover a 500 nm
radius and support a nominal data rate of 23.5 Mbps. The third downlink is a wide spot beam that covers an area
of about 2,000 nm radius and supports a data range of 12–23.5 Mbps.
Inmarsat-B HSD service in the NAVEUR AOR is provided by the 25E (AOR-E) with 33 leases on the satellite.
The AOR-E satellite footprint covers from 60° west, in the Atlantic, eastward to 100° east in the South China Sea.
The satellite supports assigned users in the Mediterranean Sea, as well as the IO and the Persian Gulf. Channels
are supported by the commercial SATCOM LES at Goonhilly, UK, and are terminated at NCTAMS EURCENT
Naples, Italy.
JAN 2005
2-10
NTTP 6-02
limitations, and available satellite channels. NCTAMS EURCENT is equipped to terminate up to 50 Inmarsat-B
HSD channels. The LES is, by contract, capable of landing 50 legacy 64 kbps channels. Current terrestrial
connectivity (one E-1) between the LES and NCTAMS EURCENT, however, limits the number of channels to a
maximum of up to 50.
In all cases, the aggregate of the satellite links are backhauled over terrestrial links (commercial or DISN) to
NCTAMS EURCENT for distribution to individual users or product sources. Obtaining terrestrial connectivity
from the various SATCOM Earth terminals to NCTAMS EURCENT can be problematic. Terrestrial connectivity
for Inmarsat-B HSD and SHF SATCOM is handled in the AOR by either a commercial vendor or the DISN.
2.2.3.4 Central Command AOR
The Navy Component, Central Command (NAVCENT) AOR extends from approximately 35° east to 90° east
longitude. NAVCENT policy is that any Navy vessel operating in the NAVCENT AOR will terminate
communications at NCTS Bahrain.
SHF DSCS SATCOM is supported at Bahrain through the standard tactical entry point (STEP) site. SHF
SATCOM terminations are forwarded from the Bahrain NAVSATCOMMFAC site to the Bahrain TCF and
present no real limitations on terrestrial connectivity. NCTS Bahrain is currently allocated to support up to eight
SHF terminations simultaneously (five IO and three EASTLANT). NAVSATCOMMFAC Lago di Patria, Italy, is
currently allocated to support up to eight SHF terminations simultaneously (two IO and six EASTLANT). The
terminations at NCTS Bahrain and NAVSATCOMMFAC Lago di Patria, Italy, are crosspatchable.
CWSP is terminated at CES Holmdel, NJ, CES Martlesham, UK, and CES Madley, UK, utilizing IS-707 at 359E
(4 E-1s), IS-906 at 64E (4 E-1s), and IS-704 at 66E (7 E-1s). EURCENT units terminating C-band with
Martlesham, UK, requires that these circuits be transported via transoceanic cable from NCTAMS LANT to
Martlesham, UK. The actual number of E-1s available to units operating in the Mediterranean depends on unit
placement and the number of E-1s used by units operating in the IO. This existing infrastructure supports the
termination of 15 ships. The space segments on all three satellites are shared between fleet commanders on an asneeded basis. The difference between the NAVEUR total and the NAVCENT total is that the IS-707 has a global
and a HEMI transponder. Only the EURCENT can see the HEMI gaining them 4 additional channels.
GBS services are provided from the NAVEUR PIP at NCTS Sigonella, Italy, via UFO-10, which provides
coverage to the CENTCOM AOR. The satellite is equipped with four GBS transponders of 23.5 Mbps each, for a
total of 94 Mbps per satellite. Data is transmitted to users from the satellite via three steerable spot beam antennas.
Two of these cover an area of 500 nm radius and support a nominal data rate of 23.5 Mbps. The third downlink is
a wide spot beam that covers an area of about 2,000 nm radius, and supports a data range of 12–23.5 Mbps.
Inmarsat-B HSD service in the NAVCENT AOR is available from two satellites, the 25E with 33 leases (AOR-E)
and 109E (IOR) with 24 leases on the satellites. The AOR-E satellite footprint covers from 60° west, in the
Atlantic, eastward to 100° east in the South China Sea; the IOR satellite footprint covers from 30° east, in the
eastern Mediterranean Sea, eastward to 107° west in the Pacific. AOR-E channels are supported by the Goonhilly,
UK, LES and terminated at NCTS Bahrain. IOR channels are supported by the Auckland, NZ, LES and are
terminated at NCTS Bahrain. Typically, Inmarsat-B HSD-equipped ships physically located in the Persian Gulf
are terminated at Goonhilly, UK, and routed to Bahrain. Naval units in the IOR and not physically located in the
Persian Gulf will normally be terminated with the Inmarsat LES located in Auckland, NZ. These terminations are
forwarded to NCTAMS PAC Wahiawa, HI, for distribution to users and product sources.
limitations, and available satellite channels. Two satellites, 109E and 25E, support the NAVCENT AOR. As those
satellites also have responsibilities to cover other AORs (25E in the Mediterranean and 109E in the IO) interfleet
coordination may be required to meet the fleet’s Inmarsat requirements. Current capacity is up to 48 channels via
the 25E satellite, shared with Sixth Fleet requirements in the Mediterranean, and up to 66 channels via the 109E
satellite, shared with Seventh Fleet requirements in the IO. The NAVCENT Inmarsat shore architecture provides
2-11
JAN 2005
NTTP 6-02
a single T-1 between NCTAMS EURCENT and the Indian Ocean region network operations center (IORNOC) in
Bahrain to backhaul Inmarsat data.
2.3 NAVY SHORE NETWORKS AND INFRASTRUCTURE
2.3.1 Fleet Network Operations Centers
There are four fleet network operations centers (NOCs), under the administrative control of the Network Warfare
Command (NETWARCOM), throughout the world to provide regional IP access to and from SGs located in the
corresponding AOR:
1. Pacific Region Network Operations Center (PRNOC), Wahiawa, HI (PAC)
2. Unified Atlantic Region Network Operations Center (UARNOC), Norfolk, VA (LANT)
3. European Central Region Network Operations Center (ECRNOC), Naples, Italy (Mediterranean)
4. Indian Ocean Region Network Operations (IORNOC), Manama, Bahrain (Arabian Gulf and IO).
The fleet NOC is the IP gateway from a ship’s satellite’s terrestrial connectivity (via the NCTAMS) to the rest of
the worldwide IP infrastructure. Additionally, several networked applications use the fleet NOC as a host for
various server applications and networking service access points. Each fleet NOC is required to provide these
services to all underway or in port SGs in its AOR.
Fleet NOCs serve several functions in the end-to-end, IP-networking architecture. This includes serving as an IP
node with the following interfaces:
1. Navy/Marine Corps Intranet (NMCI) or Overseas Navy Enterprise Network (ONE-Net)
2. Ships in the AOR via satellite connections
3. The DISN (NIPRNET, SIPRNET, and JWICS)
4. Piers
5. Submarine Broadcast Control Authority (BCA)
6. Allied/NATO, or coalition IP networks
7. Dial-in access for ships without Automated Digital Network System (ADNS).
Fleet NOCs provide hosting of various application services, which includes:
1. E-mail store and forward
2. Domain name server (DNS) resolution (and reverse)
3. Application hosting (on a FLT NOC server)
4. Application server hosting (on a FLT NOC LAN segment)
5. Web-page hosting and caching.
A critical function of the fleet NOCs is information security, which is provided through:
JAN 2005
2-12
NTTP 6-02
1. Firewalls
2. Intrusion detection
3. Virtual private networks (VPNs)
4. Communications security (COMSEC)
5. Transmission security (TRANSEC)
6. Software virus detection.
The fleet NOCs currently function as independent TCP/IP domains of control. Each NOC is its own autonomous
system that provides an external wide-area network (WAN) interface to all fleet assets that are within its AOR
(see Paragraph 2.3.2 for details). Fleet TCP/IP communications between AORs must exit and re-enter the Navy’s
routing/security domain, creating an inefficient “chop process” as ships moving between AORs must switch all IP
connections from one NOC to another. Another shortfall with the present architecture is the lack of an end-to-end
quality of service (QOS) implementation.
2.3.2 Routing Architecture
2.3.2.1 Introduction
The Navy is significantly changing the way fleet’s networks are integrated into the global routing infrastructure.
They are transitioning from existing stove-piped networks to a modern, robust system integrated across all naval
missions and functional areas supporting the requirements of FORCEnet and the DOD GIG. Exact technical
specifications and timelines for these changes are under development; however, a general description of the path
ahead is presented in Paragraph 2.3.2.5.
2.3.2.2 Present Regional Routing Architecture
The Navy’s global routing architecture is built on three elements:
1. Four NOCs and their AORs:
a. PRNOC, Wahiawa, HI (PAC)
b. UARNOC, Norfolk, VA (LANT)
c. ECRNOC, Naples, Italy (Mediterranean)
d. IORNOC, Manama, Bahrain (Arabian Gulf and IO).
2. The ADNS (see Paragraph 4.6.3 for a detailed description).
3. The DISN (see Paragraph 2.4.2 for a detailed description).
In this architecture, each NOC is the center of a regionally autonomous ADNS routing system with the DISN
backbone linking each NOC, and therefore each region, together.
Figure 2-5 shows an overview of the current routing architecture between the NOC and ships within each AOR.
There is a single autonomous system centered on an NOC with separate routers for each RF medium and a single
ADNS router for policy decisions. Features of this architecture include:
2-13
JAN 2005
NTTP 6-02
1. All routing is done at the SECRET level using TACLANE (KG-175) network encryption devices.
2. All sensitive compartmented information (SCI) traffic is routed via TACLANEs through a generic routing
encapsulation (GRE) tunnel between the ship’s GENSER SECRET ADNS router and the shore SCI router.
It is also possible to have the SCI TACLANE remotely located so the SCI traffic flows over the SIPRNET
to reach the destination TACLANE.
3. Unclassified traffic uses the TACLANE in the internet protocol security (IPSec) tunnel mode with all
unclassified traffic flowing encrypted between the two TACLANEs.
4. The open shortest path first (OSPF) routing protocol is used to automatically choose the optimum path
between routers.
Figure 2-6 shows how the NOCs are connected through the Defense Information Systems Agency (DISA)
SIPRNET and NIPRNET networks.
2.3.2.3 Present NOC Architecture
Figure 2-7 depicts in greater detail the NOC routing architecture, showing:
JWCS
NIPRNET
SCI
GRE Tunnel
Fleet
Pt to Multi Pt OSPF
SIPRNET
TACLANE
TACLANE
AOR
Autonomous
System
IPSec in Tunnel Mode
Fleet
ADNS Policy
Shore
Links
Inmarsat1
CWSP
Inmarsat2
SHF
EHF
RF Links
Ship 1
Ship 2
Ship 3
Ship 4
Ship 5
Ship 6
Ship 21
Ship 22
Figure 2-5. ADNS AOR Autonomous Routing System
JAN 2005
2-14
Ship 23
NTTP 6-02
Figure 2-6. ADNS AOR Connectivity
SIPRNET
NIPRNET
Inner and
Outer Premise
Routers and
Firewall
Inner and
Outer Premise
Routers and
Firewall
Fleet
Fleet
JWICS
DATMS-C
SCI
CENTRIX
JCA
Mail Server
DNS
Taclane
Taclane
Mail Server
DNS
Taclane
Voice
IP MUX
ADNS Policy
PBX
PSTN
Inmarsat
CWSP
SHF
Pt-to-Pt
Pt-to-Pt
Pt-to-Pt
EHF TIP
EHF TIP
Figure 2-7. Present NOC ADNS Routing Configuration
2-15
JAN 2005
NTTP 6-02
1. A central ADNS policy router
2. Individual routers for each RF medium
3. Interface routers for the following DOD global networks:
a. SIPRNET
b. NIPRNET
c. JWICS
d. Combined enterprise regional information exchange system (CENTRIXS)
e. Joint Services Imagery Processing System (JSIPS) concentrator architecture (JCA) (via the DISN
Asynchronous Transfer Mode Services–Classified (DATMS–C) network).
2.3.2.4 Present Ship Configuration
The current ship terminal configuration is shown in Figure 2-8. It shows multiple security enclaves attached to the
SECRET routing domain through TACLANE devices. The Marine air-ground task force (MAGTF) router with its
border gateway protocol (BGP 4) connection to the SECRET router is found only on amphibious ships with
Marines embarked.
2.3.2.5 Future Developments
The Navy’s future routing architecture incorporates two major changes:
Taclane
CENTRIXS
TIP
Ethernet
EHF TIP
Ship to Ship
and Ship to Shore
Taclane
SCI
Serial
Secret
Radio's
DWTS Pt-Pt
Ship to Ship
Secret
Serial
Radio's
JCA
Taclane
Voice
IP MUX
BGP4
Unclass
PBX
Radio
MAGTF
Radio
Figure 2-8. Present Ship ADNS Routing Configuration
JAN 2005
2-16
SATCOM Pt-Pt
Ship to Shore
SHF, CWSP
Inmarsat, etc.
NTTP 6-02
1. A transition from an ADNS red routing architecture to a private black routing architecture
2. A transition from IP version 4 (IPv4) networking protocol to IP version 6 (IPv6) networking protocol.
Precise technical standards and implementation timelines are under development with the transition beginning in
2005 and being completed by 2008.
2.3.2.5.1 Private Black Routing
The present ADNS routing architecture uses GENSER SECRET routing, where all network traffic between the
NOCs and the ships is encrypted using only COMSEC encryption. As seen in Figure 2-9 the Navy will implement
a private black routing ADNS architecture, where the WAN backbone has been changed to a private black routing
architecture where all network traffic is encrypted at the data level and the shore routing domains are in separate
IPSec domains. This architecture will provide additional IPSec to the system.
The proposed NOC configuration to support black routing is shown in Figure 2-10. High assurance internet
protocol encryption (HAIPE) is a government-developed IPSec protocol used for encryption, authentication, and
key exchange.
The proposed ship configuration to support black routing is shown in Figure 2-11.
2.3.2.5.2 IP Version 6 Transition
IP version 6 (IPv6) is an evolutionary improvement over IPv4 that provides the following enhancements:
SIPRNET Land Domain
Secret
NIPRNET Land Domain
Unclass
NOC1
Security
Gateway
Remote
Secret
Remote
Unclass
NOC2
Secret
Unclass
Unclass
Secret
IPSec
IPSec
IPSec
IPSec
Private
Security
Gateway
Private
Private Black Afloat Domain
SATCOM
SATCOM
LOS
Private
IPSec
Private
IPSec
Secret
IPSec
IPSec
Secret
Unclass
Ship 1
Unclass
Ship 2
Figure 2-9. Future ADNS AOR Black Routing Configuration
2-17
JAN 2005
NTTP 6-02
SIPRNET
NIPRNET
Inner and
Outer Premise
Routers and
Firewall
Inner and
Outer Premise
Routers and
Firewall
Fleet
Fleet
HAIPE
HAIPE
JWICS
DATMS-C
SCI
CENTRIXS
JCA
Mail Server
DNS
HAIPE
PBX
PSTN
HAIPE
HAIPE
Mail Server
DNS
ADNS Policy
Voice
IP MUX
SHF
CWSP
EHF
Pt-to-Pt
Pt-to-Pt
Pt-to-Pt
EHF TIP
EHF TIP
Figure 2-10. Proposed NOC Black Routing Configuration
HAIPE
COWAN
Ethernet
TIP
EHF TIP
Ship to Ship
and Ship to Shore
HAIPE
SCI
Private
Secret
Serial
HAIPE
Radio
Serial
HAIPE
Radio
JCA
HAIPE
Voice
IP MUX
Unclass
PBX
Radio
RGP4
MAGTF
Radio
Figure 2-11. Future Ship Black Routing Configuration
JAN 2005
2-18
DWTS Pt-Pt
Ship to Ship
SATCOM Pt-Pt
Ship to Shore
SHF, CWSP
Inmarsat
NTTP 6-02
1. A larger address size (128 bits vice 32 bits) that allows an enormous increase in the number of available
addresses in addition to the creation of more complex network hierarchies and structures
2. An efficient routing infrastructure with smaller routing tables and dynamic discovery of attached networks
3. Built-in IPSec features that support information assurance, authentication, and data encryption
4. Simpler and more automatic configuration of addresses and other configuration settings to reduce network
administration requirements
5. Better support for real-time delivery of data — also called QOS.
The exact implementation of IPv6 has yet to be determined. It is anticipated that the Navy’s networks will include
both IPv4 and IPv6 (commonly referred to as “dual stack routing”) for an extended period until the entire DOD
transitions to IPv6.
2.3.3 Navy/Marine Corps Intranet
The Navy/Marine Corps Intranet (NMCI) was developed to procure and manage information technologies (IT) for
the Navy at the enterprise level. NMCI is a partnership between the Navy and industry whereby industry provides
IT services purchased by individual Navy commands. The key point is that the Navy does not own or manage the
hardware, software, or communications infrastructure. Rather, a command purchases the IT services it requires
from a catalog of standard services, and industry will then provide the necessary hardware and infrastructure to
deliver those services. Performance requirements for each service are governed by standard service-level
agreements (SLAs) to ensure that the command’s operational requirements are met.
The NMCI contract was designed to support all basic networking needs of shore users to include:
Network access:
1. NIPRNET
2. SIPRNET
3. Fleet NOC/USN ships
4. Internet (via NIPRNET)
5. Ships via piers
6. Legacy USN networks (Non-NMCI standard).
End-user services:
1. Standard office suites
2. Web hosting and browsing
3. E-mail.
Key concepts that contribute to the full operational capabilities of NMCI include:
1. Standardizing DON (Navy and Marine Corps) polices, architectures, and products
2-19
JAN 2005
NTTP 6-02
2. Providing basic protection across the DON via the regional network operations centers (RNOCs) to
include piers, bases, commands, posts, and stations
3. Maximizing use of commercial off-the-shelf (COTS) internet technology security components (i.e.,
firewalls, intrusion detection, virtual private network (VPN), virus scanning, etc.)
4. Hardening infrastructure and diverse connections (i.e., protect against denial of service and/or respond to
existing vulnerabilities).
NMCI physical infrastructure consists of numerous LANs connected by base area networks (BANs) for each base
or region. Base and regional server and data farms with associated support staffs provide data services. The BANs
are connected by two separate WANs to form the Navy enterprise network. Network management and monitoring
is provided by four NOCs located at Norfolk, VA; San Diego, CA; Pearl Harbor, HI, and Quantico, VA.
As seen in Figure 2-12, NMCI is designed to provide end-to-end communications within the Navy, seamlessly
integrating with afloat naval forces.
2.3.4 Overseas Navy Enterprise Network
There are currently three ONE-Nets with major concentrations of IT users: Europe, Bahrain, and the Pacific Far
East. Commands in each region operate and maintain their own IT infrastructure. The Navy is presently extending
its enterprise network OCONUS under the ONE-Net modernization program at 16 major fleet concentration
areas:
1. Europe — Naples, London, Rota, Souda Bay, Sigonella, and La Maddalena
2. Pacific Far East — Yokosuka, Sasebo, Misawa, Atsugi, Okinawa, Korea, Guam, Singapore, and Diego
Garcia
Base Area
Network
Metropolitan
Area Network
NMCI/IT-21 Interface
LAN
Long Haul
(DISN, with Commercial as necessary)
BASE
CLINIC
LAN
TRNG CEN
Wide
Area
Network
HQ
MC AIR
NAVAL
STATION
AMPHIBIOUS
BASE
DOD TELEPORT
BASE
NOC
IMA
FISC
NMCI to
the pier
NCTAMS
TRAINING
CENTER
USN/USMC
LOGISTIC
BASE
Network
Operations
Center
Figure 2-12. NMCI Connectivity to Afloat Forces
JAN 2005
2-20
Deployed/
Mobile
Units
NTTP 6-02
3. Middle East — Bahrain.
ONE-Net is intended to replace legacy Navy IT networks and will serve an OCONUS population of 26,000 users.
ONE-Net will implement a gigabit ethernet backbone network on Navy and Marine Corps bases located
OCONUS. The ONE-Net architecture is modeled after the NMCI design in order to insure compatibility and
connects to NMCI and afloat networks via the DISN.
In addition to shore networks, ONE-Net has installed network connectivity at CONUS and OCONUS piers at
Pearl Harbor, Japan, and Guam. There are validated additional requirements for OCONUS pierside connectivity
at Italy, Spain, and Greece.
Operation of ONE-Nets is envisioned to be taken over by NMCI; however, host-nation agreement (HNA) and
status-of-forces agreement (SOFA) issues need to be resolved beforehand. Therefore, the Navy Network
OCONUS will continue to operate as a Government-owned/Government-operated (GOGO) network until
transition to a contractor-owned/contractor-operated (COCO) environment occurs under NMCI.
2.3.5 Joint Services Imagery Processing System Concentrator Architecture
Imagery is the highest use of bandwidth for the CSG or ESG, typically on the order of 768 kbps. The JSIPS JCA
was developed for the fast and efficient delivery of imagery while providing increased flexibility in bandwidth
management. The JCA is a client-server based architecture, with web-like browsing features and capabilities for
fleet imagery subscribers that is scalable up to 8 Mbps. Present ship terminations are limited to 2.048 Mbps. It
provides the fleet with a SECRET, GENSER, user-friendly network-centric, imagery delivery system. The JCA
has four major components, including imagery sources, concentrators, sites, and communications. Figure 2-13
provides an illustration of the Navy’s commercial wideband JCA.
1. Imagery sources — Sources originate imagery and imagery-related products that are required by users for
various operational needs such as tactical reconnaissance, battle damage assessment (BDA), and targeting.
2. JCA concentrator — The primary concentrator is the JCA central repository of imagery and imageryrelated products that are supplied to the fleet. The data comes from the source, and populates databases
based on standing fleet imagery requirements as well as individual fleet-initiated requests for imagery and
imagery-related products.
3. JCA sites — Navy afloat JCA sites are command ships, carriers, and large deck amphibious ships
(LHD/LHA). Each site houses an image product library (IPL) workstation that is used to coordinate
delivery, ordering and acknowledging receipt of imagery products.
4. JCA communications — Communications between the concentrator and ESG and CSG ships are via
CWSP connectivity (see Paragraph 4.1.3 for details on CWSP).
2.3.6 Video Information Exchange System
The video information exchange system (VIXS) provides a secure, GENSER SECRET and SCI, multipoint,
interactive video teleconference (VTC) capability that facilitates efficient communications among CNO, fleet
commanders, commanders at sea, Navy and Marine Corps fleet command authorities, and other users. It was
originated in 1992 as CNO VTC and expanded to the fleet flagships in 1993. In 1994 the name was changed to
VIXS and it expanded to include CVs, CVNs, and large deck amphibious ships, LHAs and LHDs.
VIXS was implemented with COTS VTC systems and multipoint control units (MCUs) (bridging units) and
utilizes Navy-standard cryptographic equipment. This integrated system supports global tactical C2 requirements
to conduct distributed, collaborative planning.
2-21
JAN 2005
NTTP 6-02
JAN 2005
2-22
Figure 2-13. Notional JCA
NTTP 6-02
Through the use of compressed digital transmission, the system provides a cost-effective means of producing
high-quality video images using reduced bandwidth. VIXS conferences are normally held at 128–256 kbps. This
reduced bandwidth requirement minimizes the expense of long distance service to Europe and allows SATCOM
connectivity to Navy ships at sea. Normal shipboard bandwidth is 128 kbps, but CWSP gives equipped ships the
bandwidth required to conference at 256 or 384 kbps. Live motion video, camera auto queue on speaker,
computer graphics, videotape, document images, white boarding, and file sharing can currently be transmitted
over the system. Support can be provided for up to 16 conferencing sites, enabling 8 simultaneous point-to-point
conferences, or a series of mixed point-to-point and multipoint conferences. Gateways located at MCU sites
provide access to other networks.
VIXS hubs are located at:
1. NCTAMS LANT Norfolk, VA
2. NCTAMS EURCENT Naples, Italy
3. NCTAMS PAC Makalapa, HI
4. NCTS Bahrain.
VIXS shore access is provided to COMPACFLT, USPACOM, CFFC, United States Joint Forces Command
(USJFCOM), COMUSNAVEUR London and Naples, NAVCENT Bahrain, and CNO. An additional 30-plus sites
have been certified as VIXS network users via ISDN dial-up. A support hub at Space and Naval Warfare
(SPAWAR) Systems Center (SSC) Charleston provides testing and diagnostics support in addition to providing
backup multipoint conference support.
The VIXS shipboard configuration consists of one suite of VTC hardware and two separate encryption paths. One
path is classified (GENSER) and the other is JWICS SCI. Both paths are encrypted via a KG-194 or KG-194A.
In FY02, upgrades included incorporation of a second MCU at VIXS hub sites to support simultaneous local
unclassified and/or NATO multipoint conferences. Future hub upgrade requirements will include support of IPbased systems such as adding an H.323 MCU and H.320/H.323 Gateway to accommodate NMCI user sites as
well as adding additional port capacity to the Madge and Montage units to accommodate additional afloat and
ashore VIXS users. Additional afloat platforms are expected to include CG and DDG utilizing SHF.
2.4 DEPARTMENT OF DEFENSE NETWORKS AND INFRASTRUCTURE
2.4.1 DOD Teleport System
The current primary wideband SATCOM transport and site access to pre-positioned DISN services ashore is over
the DSCS through standard tactical entry point (STEP) gateways. The STEP concept evolved from Operation
Desert Storm after-action reports, doctrinal changes, and subsequent contingencies all of which highlighted
several C4I successes and deficiencies. These deficiencies included the lack of interoperability and
standardization amongst the military departments (MILDEPs) and the lack of sufficient military satellite and
shore infrastructure capacity to support immediate and seamless C4I information support requirements. As a
result of these deficiencies, there was increased focus on delivering expanded worldwide DISN service to the
deployed warrior and standardization of equipment configuration to ensure C4I systems interoperability. The
DOD teleport system was designed to address the warrior’s need for a more robust system than is available
through STEP.
The teleport program design calls for upgrading the capabilities at six STEP sites. The teleport sites will build on
the existing STEP infrastructure, providing additional SATCOM, baseband, and DISN capabilities. Teleports will
provide deployed forces with interfaces for multiband and multimedia connectivity from deployed locations
anywhere in the world to online DISN service delivery nodes (SDNs) and legacy C4I systems. Teleports can be
thought of as an extension of the DISN SDNs that extends the DISN to the deployed warfighter. Thus, teleports
2-23
JAN 2005
NTTP 6-02
facilitate the interoperability between multiple SATCOM systems and deployed networks and provide the user
with a seamless interface into the DISN network and to legacy C4I systems.
The objective DOD teleport facility will integrate X-, C-, Ku-, Ka-, UHF, EHF (LDR and MDR), advanced EHF
(AEHF), and L-band SATCOM, as well as HF radio capabilities to provide connectivity for deployed tactical
communications systems. DOD teleport facilities will provide worldwide, integrated communications nodes that
also have the ability to modularly insert emerging systems adopted by the DOD to support deployed forces and
joint task forces (JTFs).
The DOD teleport is being implemented in multiple generations, from program start beginning in FY01 to full
operational capability (FOC) in FY10. Operational capabilities will be deployed at all sites on an incremental
basis, in accordance with the Teleport Operational Requirements Document (ORD) dated 31 Jul 2000 and as
amended for each generation. By the FOC phase of the program, the DOD teleport will integrate X-, C-, L-, Ku-,
Ka-, UHF, EHF (LDR, MDR), AEHF, mobile user objective system (MUOS), and future advanced wideband
systems (AWSs) as well as HF radio.
Teleport Generation One build resulted in the addition of UHF, C- and Ku- band terminals positioned at STEP
sites, and designated teleports, already configured with X-band terminals. The DOD Teleport Generation One
architecture, shown in Figure 2-14, added capabilities to a subset of existing STEP sites. DOD Teleport
Generation One provides satellite connectivity for deployed tactical communications systems operating in X-band
(i.e., DSCS and follow-on X-band satellites), commercial C- and Ku-bands, and UHF band. The initial teleport
core sites are Fort Buckner, Okinawa, Japan; Wahiawa, HI; and Northwest, VA. A European split core site
consists of Lago di Patria, Italy, and Ramstein, Germany. That split core site takes advantage of existing C and Ku
earth terminals at Ramstein. Because of the commercial Ku-band coverage available in CONUS, Camp Roberts
supports Wahiawa with Ku-band access via direct DISN connectivity. The remaining STEP sites will continue to
provide X-band connectivity into the DISN as part of the DOD teleport system.
Navy ships that are deployed and have DSCS/SHF SATCOM terminals currently connect through Navy-operated
STEP sites only. The aggregate connections from each ship are not broken out at the STEP site and
interconnected to other circuits, but are left in their aggregate form and backhauled over the existing Navy
Timeplex/Nextira TDM multiplexer system to the nearest Navy Fleet NOC site for circuit breakout. In Generation
One of teleport, how Navy ships will connect to the teleports is under study. A multiplexer system is planned for
each teleport site, which will provide for circuit termination. How these circuits will access the DISN services is
yet to be determined.
Wahiawa
Ft. Buckner
3X
2 C, 2 Ku
STEP
2 UHF
Core Site
Core Site
Existing Terminals
New Earth Terminals
Directly Connected Via DISN
Backbone
Existing STEP Sites
Ft. Meade
STEP
Ft. Bragg
STEP
Existing DISN Community
Ramstein
1X
STEP
1 C, 1 Ku
Split Core
Ft. Detrick Ft. Belvoir
STEP
STEP
Camp Roberts
3X
STEP
2 Ku
Supporting Site
DISN
Lago Patria
3X
STEP
2 C, 2Ku
NCTAMS
2 UHF
3X
2C
2 UHF
STEP
NCTAMS
Northwest
3X
STEP
1 Ku (E-2)
NCTAMS 2 C, 2 Ku
2 UHF
Core Site
MacDill
STEP
Croughton Landetuhl Bashrain
STEP
STEP
STEP
Figure 2-14. DOD Teleport Generation One
JAN 2005
2-24
SWA 1
STEP
NTTP 6-02
Implementation of Teleport Generation Two architecture, shown in Figure 2-15, is presently in progress. The
DOD teleport system is being supplemented with Ka-band, L-band, and EHF SATCOM capabilities. Existing HF
radio capabilities are being integrated. Camp Roberts, Lago Di Patria, and Ramstein/Landstuhl are being
expanded to independent core sites. Bahrain will continue to provide SHF services, expand EHF services, and
provide Ka-band capabilities while the three NCTAMS sites will have their existing HF radio capabilities
integrated into the system.
Generation Three consists of technology insertion for the AEHF system, the advanced narrowband system, and
the advanced wideband system, including technology upgrades for baseband equipment. The exact
implementation of these systems within the teleport architecture is undefined.
DOD teleport sites will connect users to DISN network services (NIPRNET, SIPRNET, JWICS, DSN, Defense
Red Switch Network (DRSN), and VTC) and Fleet NOC services. Initially much of the Navy DSN, DRSN, and
DVS-G services will be directly accessed from the teleport sites. The remainder of Navy communication will be
sent to the Fleet NOC, via tail circuits, where NIPRNET, SIPRNET, VIXS and JWICS, and legacy services will
be broken out for DISN access.
2.4.2 Defense Information Systems Network
The DISN is the DOD’s global, end-to-end information transfer infrastructure. DISN provides the
communications infrastructure and services needed to satisfy national defense, command, control,
communications, and intelligence requirements and meets corporate defense requirements. DISN provides the
transmission and switching of voice, data, video, and point-to-point bandwidth services for wide area, local area,
metropolitan area, and long-haul networks. DISN uses available commercial products and services, while
providing DOD with the degree of network control necessary to ensure rapid response to the warfighters. The
DISN includes the NIPRNET, its secured counterpart, the SIPRNET, DRSN, DSN, DISN video services (DVS),
TRANSPORT services, and DATMS.
2.4.2.1 SECRET IP Router Network
The SIPRNET is the DOD’s largest interoperable C2 data network, supporting the Global Command and Control
System (GCCS), the defense message system (DMS), collaborative planning, and numerous other classified
warfighter applications. Direct connection data rates range from 56 kbps to 45 Mbps. Remote dial-up services are
available up to 56 kbps.
Existing Terminals
New Earth Terminals
or Capacity
Core Site
Ft. Buckner
Wahiawa
3X
2C
2 UHF
HF
1 Ka
2 Ku
3 EHF
L
3X
2 C, 2 Ku
2 UHF
1 Ka
3 EHF
L
Supporting Site
Ramstein/
Landstuhl
Camp Roberts
4X
1 C, 1 Ku
1 C, 1 Ku
2 Ka
2 UHF
3 EHF
L
3X
2 Ku
2C
2 UHF
1 Ka
3 EHF
L
DISN
3X
2 C, 1 Ku
2 UHF
HF
1 C, 1 Ku
1 Ka
3 EHF
L
2X
1 Ka
3 EHF
Existing DISN Connectivity
Lago Patria
Bahrain
Northwest
3X
2 C, 2 Ku
1 Ku (E-2)
2 UHF
HF
1 Ka
3 EHF
L
Existing STEP Sites
Ft. Detrick
STEP
Ft. Balvoir
STEP
Ft. Meade
STEP
Ft. Bragg
STEP
MacDill
STEP
Croughton
STEP
SWA I
STEP
Figure 2-15. DOD Teleport Generation Two
2-25
JAN 2005
NTTP 6-02
2.4.2.2 Unclassified but Sensitive IP Router Network
The NIPRNET provides seamless interoperability for unclassified combat support applications, as well as
controlled access to the Internet. Direct connection data rates range from 56 kbps to 155 Mbps. Remote dial-up
services are available up to 56 kbps.
2.4.2.3 DISN Video Service
DVS provides worldwide dedicated and dial-up conferencing services from video hubs located at Dranesville,
VA; Atlanta, GA; San Diego, CA; Pearl Harbor, HI; and Vaihingen, GE. Service is provided from the
UNCLASSIFIED to TOP SECRET security levels. Both dedicated service and dial-up service are provided at
multiple data rates from 56/64 kbps to 768 kbps for dial-up and 56/64 kbps to T-1 for dedicated users. Through
network bridging and speed matching, DVS provides total interoperability for any H.320 compliant coder-decoder
(CODEC), operating on any transport network, i.e., DISN, DSN, DSCS, FTS-2001, and/or commercial terrestrial
or space-based systems. DVS allows subscribers to access the Navy’s tactical VTC to the fleet (VIXS).
2.4.2.4 Defense Switched Network
The DISN provides global non-SECVOX services through the Defense Switched Network (DSN), a worldwide
circuit-switched communications network. Multiple-level precedence and preemption capabilities are provided on
the DSN for C2 users to ensure completion of calls that must get through. Although designed primarily as a global
voice network, DSN also provides limited data and video services using dial-up switched 56/64 kbps ISDN
services. Voice service can also be secured when user encryption devices, secure telephone unit/secure telephone
equipment (STU/STE), are used. Interfaces are provided between strategic and tactical forces, allied military
networks, and enhanced mobile satellite services.
2.4.2.5 Defense Red Switch Network
The DRSN provides global, SECVOX services to the President, Vice President, Secretary of Defense, JCS,
combatant commanders, and selected agencies with C2 SECVOX and voice conferencing capabilities up to the
TOP SECRET SCI level.
2.4.2.6 Transport Services
DISN transport provides bandwidth/circuits to DOD services and agencies as well as to other DISN service
providers. It also manages transport networks and programs, supports customer requirements from 2.4 kbps to
155 Mbps (OCONUS) to 2.5 gigabytes per second (CONUS), and makes available network solutions that include
joint interoperability, assured security, redundancy, high reliability/availability, 7x24 in-band and out-band
network management, engineering support, and customer service.
2.4.2.7 DISN ATM Services
The DATMS provides unclassified ATM services, and the DATMS-C provides SECRET ATM services at data
rates from 1 Mbps to 155 Mbps.
2.4.3 Joint Worldwide Intelligence Communications System
The JWICS is operated by the Defense Intelligence Agency (DIA) as a secure global network designed to meet
the requirements for TS/SCI multimedia intelligence communications worldwide. It provides users an SCI-level
high-speed multimedia network using high-capacity communications to handle data, voice, imagery, and
graphics. Secure e-mail, chat rooms, point-to-point and multipoint VTCs, broadcast of the DIN, and website
access are the primary uses of JWICS by afloat users. The system also provides network services for collaborative
electronic publishing, the electronic distribution of finished intelligence, and tools to accommodate the transfer of
reference imagery, maps, and geodetic materials, as well as other high-end graphics products.
JAN 2005
2-26
NTTP 6-02
2.5 NAVAL MESSAGING SYSTEM
Naval messaging is undergoing a major transformation as the Navy implements the DMS. The Navy has
implemented DMS for all shore commands, but afloat implementation plans are uncertain beyond plans to convert
carriers, command ships, and large deck amphibious ships. In any case, until all ships have been converted to
DMS, the Navy will operate a hybrid architecture of DMS ashore and a mix of DMS and legacy systems afloat.
2.5.1 Defense Message System
DMS is a network-centric system that leverages COTS technology. It provides secure, scalable, reliable, efficient,
and interoperable electronic message handling and directory services to all organizations in the DOD, including
tactically deployed users, to our Allies, and to other Federal institutions such as the Department of State and the
intelligence community.
DMS uses TCP/IP, thus it leverages existing communications backbones already in place and operational within
the DOD. The DMS uses the transport services of the DISN for long-haul transmission and the local subscriber
network infrastructure to deliver messages from writer to reader.
DMS is designed to be a “writer-to-reader” system. The writer uses the DMS client software to draft, sign,
encrypt, and initiate the transmission of the message. The DMS infrastructure delivers the message to the
recipient, and the reader uses the local client software to decrypt and check the validity of the sender’s identity. In
this regard, the DMS is an end-to-end messaging system.
For more information on DMS, see Chapter 4, Paragraph 4.8.1.
2.5.2 Afloat Messaging
An SG’s interface to the shore DMS infrastructure is via a tactical messaging gateway (TMG) located at each
NCTAMS. The TMG provides DMS-to-legacy and legacy-to-DMS translation. A message sent by a shore DMS
user to a ship or embarked staff would travel via SIPRNET over the DISN to the appropriate NCTAMS/TMG.
There it goes through a DMS multifunction interpreter (MFI), where it is converted to the proper legacy format
for transmission by one of three paths:
1. Fleet multichannel broadcast (FLT BCST), which has 15 subchannels of message traffic with an input rate
of 75 BPS per channel. These subchannels are time-division multiplexed and transmitted over RF at 1,200
bps, 1,125 bps available for message transmission (channel 16 is used for timing, therefore is not used to
transmit messages). The NCTAMS transmits data on a direct sequence, spread-spectrum SHF signal to the
UHF satellites, which then translate the signal to UHF and downlink to the individual ships. This is a oneway receive-only broadcast.
2. The common user digital information exchange system (CUDIXS), a shore-based, computer controlled,
message store-and-forward system that automates the message exchange between ship/shore/ship.
CUDIXS uses the UHF satellite link resources of the fleet satellite communications (FLTSATCOM)
system. CUDIXS provides a 2,400-baud, full duplex, netted circuit capability. CUDIXS provides a twoway exchange of messages.
3. Fleet SIPRNET messaging (FSM), which uses Microsoft exchange and defense message dissemination
system (DMDS) software to deliver GENSER organizational messages via the SIPRNET using the simple
mail transfer protocol (SMTP).
Onboard each ship, the Naval Modular Automated Communications System II (NAVMACS II) is used to
automatically receive, process, store, and distribute incoming messages from any of the above three paths.
NAVMACS II is also used to process and transmit outgoing messages.
2-27
JAN 2005
NTTP 6-02
The Navy plans to install DMS on ships starting in FY04. Initially, CVN/LHA/LHD/LCC class ships will be
converted, due primarily to their potential role as JTF flagships, with a targeted completion date of FY07. DMS
afloat will be provided to the remaining shipboard platforms by integrating the DMS software with the integrated
ship network system (ISNS), which will start in the FY07 timeframe.
DMS-equipped ships dispense with NAVMACS and all other legacy systems and receive messages directly from
shore DMS users via the NIPRNET and SIPRNET to the shipboard DMS system.
2.6 SUBMARINE COMMUNICATIONS
2.6.1 Submarine Shore Communication Infrastructure
The primary submarine shore infrastructure elements are the submarine Operational Control Centers (OPCON
Centers), the submarine Broadcast Controlling Authorities (BCAs), the Submarine Special Intelligence Broadcast
Facilities (SIBFs), Very Low Frequency/Low Frequency (VLF/LF), and Extremely Low Frequency (ELF)
transmitter facilities.
The submarine shore communication infrastructure utilizes ELF, VLF/low frequency (LF), HF, UHF SATCOM,
SHF SATCOM, and EHF SATCOM systems to communicate with submarines at sea. While pierside, submarines
use network services and applications provided by the ONE-Net, DISN, and NMCI.
2.6.2 Submarine Broadcast Controlling Authorities
The submarine shore infrastructure currently includes six key nodes that manage, process, store, and disseminate
the flow of information to and from submarines. These nodes, the submarine BCAs, contain personnel and
communication systems necessary to send and receive essential C4ISR information from land-based shore
facilities to submarines. The submarine BCAs are located at:
1. Commander Submarines Force, U.S. Atlantic Fleet (COMSUBLANT), Norfolk, VA (SIBF Collocated)
2. Commander Submarine Force, U.S. Pacific Fleet (COMSUBPAC), Pearl Harbor, HI (SIBF Collocated)
3. Commander Submarine Group (COMSUBGRU) EIGHT, Naples, Italy (SIBF Collocated)
4. COMSUBGRU TEN, Kings Bay, GA
5. COMSUBGRU NINE, Bangor, WA
6. COMSUBGRU SEVEN, Yokosuka, Japan (SIBF Collocated).
The submarine force plans to transition by FY05 to a shore configuration of four BCAs (vice six) located at:
1. COMSUBLANT, Norfolk, VA
2. COMSUBPAC, Pearl Harbor, HI
3. COMSUBGRU EIGHT, Naples, Italy
4. COMSUBGRU SEVEN, Yokosuka, Japan.
2.6.3 Submarine Communications Capabilities
The submarine force IP transition plan is the submarine force’s program to make every submarine (SSN and
SSBN) capable of receiving IP traffic replacing the legacy information exchange systems (IXSs). The IP
transition plan is designed to provide the following enhanced operational capabilities:
JAN 2005
2-28
NTTP 6-02
1. IP capability for all security enclaves (UNCLASSIFIED, SECRET, TOP SECRET, SCI) with access to
NIPRNET, SIPRNET, and SCI networks
2. IP messaging solution, including emission control (EMCON) delivery
3. IP TLAM MDUs, including EMCON delivery
4. IP common operational tactical picture received from SG force over-the-horizon track coordinator (FOTC)
5. SG collaborative planning using chat, secure e-mail, and web browsing.
This plan has two elements: the wideband plan and the narrowband plan.
The wideband plan delivers end-to-end wideband C4I capability as shown in Figure 2-16. The centerpieces of
wideband are the submarine high data rate (SubHDR) antenna, and the higher data rate terminals for EHF, SHF,
and GBS.
Wideband end-to-end is installed on usually two SSNs per CSG deployment, both PAC and LANT. At this rate
the entire submarine force will transition to wideband IP communications by FY06.
Wideband C4I is the “minimum IP requirement” for SSNs and the minimum acceptable capability for IT-21.
However a lesser capability, specifically to achieve IP migration on the remaining boats scheduled to receive
wideband after 01 June 2004, is needed in order to achieve 100 percent completion of IP cutover by 01 June 2004.
It is for this reason that the narrowband plan was developed.
Figure 2-16. SSN Wideband Communications
2-29
JAN 2005
NTTP 6-02
The narrowband plan, a subset of the wideband plan, attempts to achieve IP migration during a maintenance
availability prior to a submarine’s wideband deployment. The narrowband plan delivers end-to-end TCP/IP
connectivity using a 32 kbps connection via UHF SATCOM. This provides the SSN the following capabilities:
1. IP messaging
2. Tactical voice communications
3. Chat, secure e-mail, and web browsing
4. CTP.
2.7 COMPUTER NETWORK DEFENSE
2.7.1 Defense in Depth
Computer network defense (CND) of the CSG and ESG is based on the concept of defense of depth, whereby a
global array of organizations and technology supporting standard policies and doctrine protect Navy C4I networks
from attack in order to ensure the availability and integrity of critical systems and data. The DOD has identified
four specific layers for a defense in depth:
1. Host or end user systems
2. Enclaves and the enclave boundary — in this case a shipboard LAN
3. Networks that link the enclaves, typically WANs
4. Supporting infrastructures.
CND for the CSG or ESG is primarily focused on the first three layers.
CSG/ESG CND begins at the fleet NOC. There all IP traffic addressed to the SG goes through a sophisticated
array of screening routers, firewalls, network intrusion detection sensors, and virus scanning software before
being routed to the SG.
The WAN links between the NOC and an individual SG ship consist of satellite communication links, which vary
depending on ship class and installed systems. These links are encrypted at the appropriate classification level by
standard cryptographic devices. For wideband SATCOM systems such as SHF, additional bulk encryption of the
entire communications channel is done to provide TRANSEC.
On the ship, CND is provided by routers, firewalls, intrusion detection devices, virus protection software, and
network monitoring tools. Exact configurations vary greatly, with CVNs and other ship classes with large LANs
having the most comprehensive and sophisticated capabilities. The Navy is moving as much as possible toward
embedded security features that are built in to both software applications and hardware, in an effort to minimize
network complexity and to automate CND functions.
2.7.2 Computer Network Defense Organization
2.7.2.1 Navy CND Organization
2.7.2.1.1 Naval Network Warfare Command
Commander, NETWARCOM acts as the Navy’s central operational authority for space IT requirements and
network and information operations in support of naval forces afloat and ashore. NETWARCOM operates a
secure and interoperable naval network that enables effects-based operations and innovation. Additionally,
JAN 2005
2-30
NTTP 6-02
NETWARCOM serves as the naval component commander to United States Strategic Command
(USSTRATCOM).
Together, this command improves the fleet’s ability to conduct network-centric operations by linking space
capabilities to warfighting effectiveness, integrating IT and interoperability throughout the interdeployment
training cycle (IDTC), and improving defense of naval networks. NETWARCOM is the immediate superior in
command (ISIC) of the following:
1. Fleet information warfare center (FIWC)
2. Naval computer incident response team (NAVCIRT)
3. Naval Network and Space Operations Command (NNSOC)
4. SPAWAR (under an additional duty relationship)
5. Naval Center for Tactical Systems Interoperability (NCTSI)
6. Director, COMSEC Material Systems (DCMS)
7. Navy and Marine Corps Spectrum Center (NMSC).
2.7.2.1.2 Naval Computer Incident Response Team
NAVCIRT, designated by NETWARCOM as the Navy component commander-to-commander JTF for global
network operations (GNO), coordinates the defense of Navy computer networks from attack. This component
directly supports the Navy’s commitment of “Critical Infrastructure Protection,” Presidential Decision Directive
63 (PDD-63), and Joint Vision 2020, “Full Spectrum Dominance,” which includes the capability to collect,
process, and disseminate a secure uninterrupted flow of information. At a minimum, NAVCIRT performs the
following functions:
1. Maintain 24 hours-per-day, 7 days-per-week network operations access and coordination.
2. Report all incidents in accordance with OPNAVINST 2201.2 (Navy and Marine Corps computer network
incident response).
3. Coordinate. computer network vulnerability assessments.
4. Monitor status of information assurance vulnerability alert (IAVA) compliance.
5. Be cognizant of monitoring computer networks for incident and technical vulnerabilities. Provide status to
JTF-GNO.
6. Conduct preliminary assessments of incidents against Navy computer networks.
7. Operate and maintain C2 connectivity in accordance with the JTF-GNO CONOP.
8. Recommend nonoffensive countermeasures to incidents against Navy computer networks.
9. Direct and coordinate the restoration of, and maintain network functionality following incidents against,
Navy computer networks.
10. Analyze threats to Navy computer network systems.
11. Oversee and coordinate the correlation of disparate computer and network incidents.
2-31
JAN 2005
NTTP 6-02
12. Recommend to the Navy command center changes to the Navy’s information operations condition
(INFOCON). Monitor INFOCON status across the DOD and the Navy.
13. Provide recovery assistance worldwide (deployable if necessary).
14. Provide awareness of vulnerabilities and fixes through NAVCIRT advisories and other reports.
15. Gather and maintain statistical data for trend analysis.
16. Coordinate with operational commands, CERTs, DISA, Naval Criminal Investigative Service (NCIS), and
other CND or CND-related organizations.
2.7.2.1.3 Fleet Information Warfare Center
FIWC serves as the IW center of excellence for the Navy. FIWC’s CND objectives are aimed toward improving
the defensive posture of the Navy and Marine Corps networked IT systems via:
1. IO/IW doctrine and tactics development
2. CND afloat training continuum support
3. CND training across the fleet response plan
4. Red Team operations for afloat and ashore
5. Operations security (OPSEC) and web-risk assessments
6. Advising and alerting the NAVCIRT/DON/DOD
7. Collecting data for analysis and “lessons learned”
8. Conducting initial intelligence analysis.
FIWC provides CND-trained support personnel to conduct (operationalize) network defense and ensures CND
readiness of the CSGs/ESGs.
2.7.2.1.4 Naval Network and Space Operations Command
The NNSOC was formed in July 2002 by the merger of elements of the Naval Space Command and the Naval
Network Operations Command. The command operates and maintains the Navy’s space and global
telecommunications systems and services, directly supports warfighting operations and command and control of
naval forces, and promotes innovative technological solutions to warfighting requirements. NNSOC enables naval
forces to use information and space technologies and expertise to achieve and maintain knowledge superiority
essential for dominating the battlespace.
2.7.2.1.5 Network Operations Center
There are four fleet NOCs that provide afloat units with shore connectivity, security, and IT services. In addition,
the NOCs provide information assurance (IA) services including firewall protection, intrusion detection, and virus
scanning of e-mail attachments.
The NOCs are the:
1. UARNOC, Norfolk, VA
JAN 2005
2-32
NTTP 6-02
2. PRNOC, Wahiawa, HI
3. ECRNOC, Naples, Italy
4. IORNOC, located in Bahrain.
For further information on the NOCs, refer to Paragraph 2.3.1.
2.7.2.1.6 Space and Naval Warfare Systems Command
SPAWAR provides technical support to NETWARCOM on network-related systems and equipment. PMW-161
manages the DON IA program. PMW-165 serves as the Naval Afloat Networks Program Office, with
responsibilities for consolidating information processing and sharing of infrastructure requirements. PMW-161
and PMW-165 work together to provide system engineering and integration support to the systems commands and
operational commanders, providing security solutions for information systems.
2.7.2.1.7 Naval Criminal Investigative Service
NCIS conducts reactive and proactive investigations, gathers information, and conducts activities to protect Navy
computer networks against espionage, other intelligence activities, sabotage, and other unlawful acts conducted
by or on behalf of foreign governments or elements, foreign organizations, foreign persons, international
terrorists, and criminal elements. NCIS computer forensic specialists provide direct support to NAVCIRT on
investigative and counterintelligence matters of interest to the DON.
2.7.2.2 Joint Computer Network Defense Organization
Recognizing the electronic attack (EA) threat, the DOD has created numerous joint organizations to counter this
new threat. The most significant organizations that provide support for Navy CND efforts are described in the
following paragraphs.
2.7.2.2.1 Joint Task Force for Global Network Operations
The JTF-GNO is the focal point for the defense of DOD computer systems and networks. The JTF-GNO is
located in Washington, DC, with DISA as its supporting agency. This allows the JTF-GNO to be collocated with
DISA’s global operations and security center (GOSC), and to leverage DISA’s existing global presence, its
network operational view, intrusion analysis, and core technical capabilities with the unified commands and the
law enforcement community. The JTF-GNO is organized as follows:
1. J2 provides intelligence and indications and warnings (I&W).
2. J3/J6 provides correlation and fusion of operational, intelligence, and technical reports received by JTFCND staff and components into operational strategies for defending the defense information infrastructure
(DII).
3. J5/J7 leads planning and ensures interoperability of JTF-CND and its components as required to conduct
CND operations in support of DOD missions worldwide, across the spectrum of military operations.
2.7.2.2.2 Department of Defense Computer Emergency Response Team
The DOD Computer Emergency Response Team’s (CERT’s) mission is to protect, defend, and restore the
integrity and availability of the essential elements and applications of the DII. In addition, the DOD CERT
provides timely and accurate strategic CND analysis and technical decisionmaking support to the JTF-CND. The
DOD CERT is responsible for global intrusion detection, vulnerability analysis and management, and the
investigation of incidents.
2-33
JAN 2005
NTTP 6-02
The DOD CERT collects information about new vulnerabilities from various sources. Upon identification of a
new vulnerability, the DOD CERT conducts a preliminary evaluation to determine the potential operational
impact of the vulnerability. Based on the impact of the vulnerability to the DII, the DOD CERT decides whether
or not to release an IAVA, an information assurance vulnerability bulletin (IAVB), or a technical advisory to the
DOD community.
The DOD CERT’s virus support team works closely with major antivirus vendors to detect new viruses and to
provide up-to-date virus protection to DOD customers. In addition, the DOD CERT virus team provides technical
services required to maintain, configure, and update antivirus software. Upon being notified of a potential
problem, the DOD CERT virus team performs an analysis to determine whether a suspicious event is malicious
code in nature and then provides appropriate guidance to the customer.
2.7.2.2.3 Regional CERT
DISA regional CERTs (RCERTs) are functionally and organizationally embedded within the five DISA RNOCs.
They provide a comprehensive picture of the status of network assets, near-real-time (NRT) data on network
anomalies, and intrusive behavior. RCERTs provide CND support to the COCOMs/major commands
(MAJCOMs), services, agencies, and local control centers (LCCs). Each RCERT is responsible for intrusion
detection, monitoring, vulnerability analysis, and computer-security incident handling/reporting within its area of
responsibility (AOR). The RCERTs also provide direct support to the DOD CERT in global intrusion detection
monitoring, vulnerability analysis, computer forensics, and incident investigations for DII. RCERTs maintain a
mirror of DOD CERT's restricted public file transfer protocol (FTP) server. This provides the RCERT access to
DISA standard products, including DOD antiviral products, bulletins, and advisories for customer elements within
its AOR. RCERTs also provide technical support for the antiviral products.
RCERTs facilitate periodic vulnerability assessments of customers' computer systems/networks to ensure
protective measures are being implemented. In addition, each RCERT has a dedicated customer support desk,
which provides help in resolving computer security problems within its AOR. Each RCERT is the responsible
agent for the resolution of computer security events/incidents within its AOR.
DISA Western Hemisphere (WESTHEM) operates and maintains the two RNOSCs located in CONUS. The
Columbus-RNOSC/Regional CERT, Columbus, OH, provides CND support to DISA WESTHEM and all DOD
agencies in CONUS. Scott-RNOSC/Regional CERT, Belleville, IL, supports the CONUS-based CINCs. The
RCERTs located OCONUS are operated and maintained by their respective DISA field activity. The PacificRNOSC/Regional CERT, Oahu, HI, provides direct CND support to PACOM and its service components. The
Central-RNOSC/Regional CERT, Manama, Bahrain, supports CENTCOM and JTF elements within it. The
Europe-RNOSC/Regional CERT, Patch Barracks, Vaihingen, Germany, provides direct CND support to
EUCOM.
JAN 2005
2-34
NTTP 6-02
CHAPTER 3
Warfare Area C4I Architectures
3.1 INTRODUCTION
This chapter presents notional C4I architectures for various warfare areas. There is a discussion of CSG/ESG C4I
architectures and systems categorized into the following three areas:
1. SA
2. Planning and coordination
3. Control.
For each warfare area there is a diagram depicting notional C4I architectures.
It is important to note that this chapter does not address warfare tactics, TTP for each warfare area or system, as
these are more than adequately addressed in other naval warfare doctrine publications. Bold type indicates
material discussed in greater depth in Chapter four.
3.2 COMMON TACTICAL PICTURE/COMMON OPERATIONAL PICTURE
For this publication, the term CTP will be used to describe the U.S. Navy surface and subsurface tactical picture
at the CSG and ESG level while using COP to refer to the joint theater-level operational picture.
Creation of the CTP centers on the FOTC concept within the U.S. Navy. The FOTC is responsible for correlating,
fusing, and maintaining geolocated track information on friendly, hostile, and neutral land, sea, and air forces
within a geographically defined area. This track data is maintained in a Global Command and Control SystemMaritime (GCCS-M) track database. Each CSG and ESG will have a FOTC (usually located on the
CVN/LHA/LHD) with each ship in the SG passing track information to FOTC via the officer in tactical
command information exchange system (OTCIXS), or, more commonly, via the SIPRNET. FOTC in turn will
broadcast a fused and integrated CTP back to the SG over OTCIXS or the SIPRNET (commonly referred to as the
“FOTC broadcast”). The key to the FOTC process is that all information is evaluated at a central node before
being disseminated.
Within a theater of operations there may be multiple FOTCs. For example, in addition to each CSG and ESG
FOTC, there may be a theater antisubmarine warfare (ASW) FOTC responsible for maintaining the theater ASW
CTP. Each FOTC will maintain an independent track database using GCCS-M.
Individual ships are required to use the SG’s CTP received through their SG’s FOTC broadcast. SG staffs and
other commanders have the option to receive and display multiple FOTC broadcasts, therefore allowing them a
broader operational picture.
The Navy’s interface to the COP is through the FOTC. The FOTC will operated in a Mixed (Navy term) or
Unique Identifier Correlation Mode (joint term) using COP Synchronization (COP Sync) tools to add his CTP to
the COP. The COP is fundamentally different from the CTP in that the data within it is not centrally analyzed,
fused, or managed. Within a theater of operations, there is a hierarchy of participants with a single top-level
commander (or “Top COP”) determining who may contribute to the COP, and what they may contribute. Once
3-1
JAN 2005
NTTP 6-02
granted permission to contribute to the COP, any data a FOTC sends to the COP is instantaneously disseminated
to all COP participants.
3.3 AIR DEFENSE
3.3.1 Situational Awareness
The key to air defense SA for the CSG centers on tactical data links due to the extremely dynamic nature of air
warfare and the requirement for rapid decisionmaking and action. The primary CSG tactical data link is Link
16/tactical digital information link (TADIL) J, which is installed on all modern air defense ships in addition to
all CVNs. It is also installed on E2C airborne early warning (AEW) aircraft and F14D fighter and F18 strike
aircraft. Link 16 is not installed on older ship classes such as FFGs and DDs, which depend solely on Link
11/TADIL A. As shown in Figure 3-1, Link 16 and Link 11 networks within the CSG are combined through a
data forwarding ship to provide an integrated air picture. Satellite Link 16/S-TADIL J is being fielded to extend
Link 16 networks over extended ranges without the need for a dedicated airborne relay. Satellite Link 16 has
reduced data throughput due to UHF SATCOM limitations and therefore requires additional information
management and filtering.
As shown in Figure 3-2, the CSG exchanges information with joint theater link architectures via the joint air
operations center (JAOC) through Satellite Link 16/S-TADIL J and the joint range extension (JRE) system.
JRE allows Link 16 data to be transmitted via TCP/IP format over the SIPRNET. Satellite Link 16 and JRE are
also used to forward data to other CSGs and Navy units requiring access to the air picture. The Navy’s interim
solution is Air Defense System Integrator (ADSI) Version 12 (JRE MIL STD 3011) to meet the fleet’s need for a
fused operational and tactical picture.
Cooperative engagement capability (CEC), while presently not a widespread capability, significantly enhances
the CSG SA by providing composite tracking of air contacts by netting CSG sensors through high data-rate data
links
Complementing the integrated air picture provided by the tactical data links is the CTP as described in Paragraph 3.2.
3.3.2 Planning and Coordination
The air defense planning process is extremely flexible and dynamic due to the introduction of collaborative planning
tools and CSG websites fielded through the Collaboration at Sea (CAS) program. All CSG planning and tasking
messages and documents such as OPTASKs, OPGENs, and Air Tasking Orders/Air Control Orders along with other
vital planning information such as intelligence, weather, and readiness data, are centrally located on CSG websites
for instant access to any user with SIPRNET access. Coupled with dedicated SIPRNET chat rooms, the AWC and
air defense ships have a collaborative environment to quickly and efficiently plan air defense operations.
Permanent, dedicated CAS chat rooms for air defense planning and link management have replaced naval messages
and voice communications as the primary means of coordination within the CSG; however, naval messages and
voice communications are still used, especially with units such as allied and coalition ships that do not have access
to the SIPRNET. For ships with CAS installed, a commander’s intentions and tasking orders are rapidly
promulgated and accessed via CSG web pages which are automatically replicated to web servers on every CSG ship.
3.3.3 Control
Control of individual air defense tactical units is primarily through Link 16/TADIL J and UHF/VHF line of sight
(LOS) voice communications. Link 4A/TADIL C is used by air defense ships and E-2C aircraft for control of
non-Link 16 equipped F-14 and F-18 aircraft.
3.3.4 Reference
NWP 3-01.01, Antiair Warfare.
JAN 2005
3-2
NTTP 6-02
Figure 3-1. Notional Air Defense C2 Architecture (Single CSG)
Satellite Link 16/
S-TADIL J
JRE
JAOC
ESG
CSG #1
CSG #2
Figure 3-2. Notional Air Defense C2 Architecture (Multi-SG)
3-3
JAN 2005
NTTP 6-02
3.4 SURFACE WARFARE
SG ships and staffs access the CTP and COP as described in Paragraph 3.2 and depicted in Figure 3-3.
Maritime patrol aircraft (MPA) use HF Link 11/TADIL A to link to the SG or a shore-based tactical support
center (TSC). These link tracks are then passed to GCCS for inclusion into the CTP.
SH-60B helicopters use the SRQ-4 Hawklink data link to send radar and ESM data to a controlling surface ship
for onboard display and evaluation. This information can also be sent to GCCS-M via the ship’s combat system
for inclusion in the CTP.
Antisurface warfare (ASUW) planning and coordination is done through web-based collaborative planning tools
and information exchange provided through CAS and other SIPRNET chat tools. Planning and tasking messages
and documents such as OPTASKs, along with other vital planning information such as intelligence, weather, and
readiness data, are centrally located on websites for instant access via the SIPRNET. The surface warfare
commander (SUWC), surface action group (SAG), and ships use dedicated SIPRNET chat rooms, web pages, and
e-mail to collaboratively plan and coordinate SUW operations. SUW planning and tasking messages are also
disseminated via the naval messaging system.
SUW operations may involve allied and coalition forces. Allied and coalition planning and coordination is
described in Paragraph 3.11 of this chapter.
3.4.3 Control
Control of individual SUW tactical units is primarily through voice communications — UHF LOS or UHF
SATCOM for ships and VHF/UHF LOS or UHF SATCOM for helicopters and MPA. The preferred method of
control for SH-60 helicopters is through the SRQ-4 Hawklink, which provides secure point-to-point voice
communications between the helicopter and its controlling ship.
Figure 3-3. Notional SUW C2 Architecture
JAN 2005
3-4
NTTP 6-02
3.4.4 References
1. NWP 3-20.1, Antisurface Warfare Commanders Manual
2. NWP 3-20.3, Surface Ship Antisurface Warfare Tactics.
3.5 MINE WARFARE
Mine countermeasures (MCM) units report mines and other MCM data to a tactical MCM database manager
using Mine Warfare Environment Decision Aids Library (MEDAL) over OTCIXS or the SIPRNET using the
system notionally identified in Figure 3-4. The tactical MCM database manager may be the theater mine warfare
commander (TMIWC) or the tactical MCM commander (TMCMC) depending on the scope of the mine threat and
the operational situation. MEDAL is a GCCS-M software module that graphically displays tactical MCM data.
The tactical MCM database manager serves as a data fusion center, using GCCS-M to combine and analyze data
from MCM ships, helicopters, and explosive ordnance disposal (EOD) units to create a comprehensive MCM
tactical picture. This tactical picture is then disseminated via GCCS-M to the CSG or ESG TMCMC.
MCM ships and staffs also access the CTP and COP as described in Paragraph 3.2.
MCM planning and coordination at the operational level is done by the TMIWC through web-based collaborative
planning tools and information exchange provided through CAS and other SIPRNET chat tools. MCM planning
and tasking messages and documents such as OPTASKs, along with other vital planning information such as
intelligence, weather, and readiness data, are centrally located on websites for instant access via the SIPRNET.
The TMIWC and the TMCMC use dedicated SIPRNET chat rooms to collaboratively plan and coordinate MCM
operations. MCM planning and tasking messages are also disseminated via the naval messaging system.
Figure 3-4. Notional Mine Warfare C2 Architecture
3-5
JAN 2005
NTTP 6-02
MCM operations commonly involve allied and coalition MCM forces. Allied and coalition planning and
coordination is described in Paragraph 3.13 of this chapter.
3.5.3 Control
Control of individual MCM tactical units is primarily done via voice communications.
3.5.4 Reference
NWP 3-15A, Naval Mine Warfare.
3.6 ANTISUBMARINE WARFARE
The ASW planner is faced with two distinct but related ASW problems: the local ASW problem centered on the
CSG/ESG and its organic units, sensors, and weapons and the theater ASW problem involving theater assets such
as MPA, submarine, and national sensors. These theater assets may operate in direct support of a CSG/ESG, but
will also conduct independent ASW operations in support of the theater commander. As such, the SG
antisubmarine warfare commander (ASWC) may use both the SG and theater ASW FOTC broadcasts as
described in Paragraph 3.2 in order to see the entire ASW CTP. A notional ASW warfare C2 architecture is
depicted in Figure 3-5.
MPA use HF Link 11/TADIL A to link to the CSG or a shore-based TSC. These link tracks are then passed to
GCCS-M for inclusion into the CTP.
SH-60 LAMPS III ASW helicopters use the SRQ-4 Hawklink data link to send acoustic, radar, and ESM data to
a controlling surface ship for onboard display and evaluation. This information can also be sent to GCCS-M for
inclusion in the CTP.
ASW planning has moved to web-based collaborative planning tools and information exchange with the
introduction of the Web-Centric Antisubmarine Net (WeCAN). Part of CAS, WeCAN is specifically tailored to
support SG and theater ASW operations. The central node of the WeCAN network is a shore-based ASW
“reachback cell” (RBC). Other nodes in the network include the ASWC’s planning cell and ASW module aboard
the CVN, key watch standers aboard other strike group ships, MPA shore-based TSCs, shore intelligence centers,
and meteorological and oceanographic (METOC) centers. The RBC, functioning as part of the ASWC’s
organization, is staffed, equipped, and located to collect data, evaluate information, and conduct analysis to
formulate assessments and recommendations. The RBC assesses the ASW battlespace and collaborates with the
ASWC via web pages and secure e-mail to formulate a mission plan and assess plan execution. There is presently
no permanent RBC; rather RBCs are stood up in an ad hoc manner as required. In the absence of an RBC, the
functions of the RBC are absorbed by the ASWC.
3.6.3 Control
Control of individual ASW tactical units is primarily through voice communications — UHF LOS or UHF
SATCOM for ships, and VHF or UHF SATCOM for helicopters and MPA SIPRNET chat.
The preferred method of control for SH-60 helicopters is through the SRQ-4 Hawklink, which provides secure
point-to-point voice communications between the helicopter and its controlling ship.
Control of submarines in direct support of the SG is through voice, SIPRNET chat, and naval messages over EHF
and UHF SATCOM. Short-range underwater communications are available with the WQC-2.
JAN 2005
3-6
NTTP 6-02
ASW Reachback
Cell
UHF
SATCOM
INMARSAT
EHF
SHF
EHF
SATCOM
- Voice
- OTCIXS
SIPRNET
WeCan
Chat
Voice
SH 60B
Hawklink
CDL
VHF Voice
P3C
VHF, UHF Voice
Link 11
VHF, UHF Voice
Link 11
Chat
Naval
Messages
SSN
Underwater
COMMS
Figure 3-5. Notional ASW Warfare C2 Architecture
3.6.4 References
1. NWP 3-21, Navy ASW
2. NWP 3-21.0 (Rev. A), Coordinated Submarine/Task Group Operations Manual
3. NWP 3-21.1.2, ASW Commanders Manual, Vol. 2.
3.7 EXPEDITIONARY WARFARE
Figure 3-6 illustrates a notional expeditionary warfare C2 architecture.
ESG ships and staffs access the CTP and COP as described in Paragraph 3.2.
Link 16/TADIL J and Link 11/TADIL A, which are installed on all modern air defense ships in addition to the
LHD/LHA/LPD 17 class ships, provide air defense SA for the ESG. All other amphibious ships such as LPDs or
LSDs are not equipped with tactical data links.
The ESG exchanges information with joint theater link architectures via the JAOC through Satellite Link 16/STADIL J and the JRE system. JRE allows Link 16 data to be transmitted via TCP/IP format over the SIPRNET.
Satellite Link 16 and JRE are also used to forward data to other CSGs, ESGs, and Navy units requiring access to
the air picture.
Enhanced position location reporting system–data radio (EPLRS-DR) provides position locating information
on Marine and Army units ashore. The amphibious assault direction system (AN/KSQ-1) uses EPLRS-DR to
provide position locating information on amphibious assault craft.
3-7
JAN 2005
NTTP 6-02
Figure 3-6. Notional Expeditionary Warfare C2 Architecture
Expeditionary warfare planning and coordination is done through web-based collaborative planning tools and
information exchange provided through CAS, the intra-ARG/ESG distributive collaborative planning (IDCP)
system, and other SIPRNET chat tools. Planning and tasking messages and documents, along with other vital
planning information such as intelligence, weather, and readiness data, are centrally located on websites for
instant access via the SIPRNET. Dedicated SIPRNET chat rooms and classified e-mail are used to collaboratively
plan and coordinate operations. Planning and tasking messages are also disseminated via the naval messaging
system.
In addition to the SIPRNET, the IDCP system provides an alternative path for voice, IP data transfer, and VTC
collaboration among the amphibious ships (LHA/LHD/LPD/LSD) in the ESG. Using a hub and spoke architecture
with the LHD or LHA as the hub, IDCP uses the Digital Wideband Transmission System (DWTS), which is a
wideband LOS RF system to link all the amphibious ships.
ESG connectivity ashore to Marine tactical units is primarily through:
1. SHF ground mobile force (GMF), with the LHA/LHD acting as a communications link between IDCPequipped amphibious ships and tactical units ashore. In addition to IP data transfer, this allows tactical
telephone voice communications using the Tri-Service Tactical Communications Program (TRI-TAC)
systems.
JAN 2005
3-8
NTTP 6-02
2. EPLRS-DR is the backbone for Marine Corps tactical data networks and provides IP data exchange in
addition to providing position locating information on tactical units. EPLRS is a LOS system that may
require an airborne relay to connect afloat and ashore units.
3. Single channel radio.
a. HF
b. VHF
c. UHF LOS (communications with Marine air)
d. UHF SATCOM.
4. DWTS.
Naval gunfire support (NGS) is coordinated using the Advanced Field Artillery Tactical Data System
(AFATDS) located in the supporting arms coordination center (SACC) on the LHD/LHA. The AFATDS receives
a digital call to fire requests from the beach via SHF GMF, EPLRS, or any communications system capable of IP
data exchange. The SACC in turn sends digital firing orders to naval fires control system (NFCS)-equipped
surface combatants via the SIPRNET.
3.7.3 Control
Control of units while executing amphibious operations is through voice communications or SIPRNET chat. The
Amphibious Assault Direction System (AN/KSQ-1) is used to control the movement of amphibious assault craft.
3.7.4 References
1. NWP 3-02.1, Ship to Shore Movement
2. NWP 3-02.1, Employment of Landing Craft Air Cushion (LCAC)
3. NWP 3-09.11M, Supporting Arms in Amphibious Operations.
3.8 TLAM STRIKE
A notional TLAM strike architecture is shown in Figure 3-7.
Ships and staffs involved in TLAM strike operations access the CTP and COP as described in Paragraph 3.2.
TLAM strike planning and coordination has two distinct components, the first of which is the mission planning
process required to plan and disseminate the TOMAHAWK command information (TCI) required for TLAM
employment. This is a deliberate process where mission libraries are created based on the requirements of the
combatant commanders. Firing units deploy with the complete database of TCI. Firing units can receive new or
revised TCI based on changing or emergent operational requirements while they are deployed. When directed to
execute TLAM tasking, firing units apply power to the missile for initialization and navigation alignment, pair a
preplanned mission to an appropriate missile, and execute the tasking at the directed time.
The second component of TLAM strike planning and coordination involves the planning and coordination at the
TOMAHAWK strike coordinator level to plan and execute TLAM strike missions. This step involves analyzing
3-9
JAN 2005
NTTP 6-02
SHF
EHF
UHF SATCOM
Numbered Fleet
(Theater TEA)
EHF
UHF SATCOM
MDUs
CVN
Voice
MDUs
Naval Messages
Voice
Naval Messages
SHF
CMSA
TLAM Firing Unit
INMARSAT
IP Based
Web pages
Chat
T1 Land Line
Figure 3-7. Notional TLAM Strike C2 Architecture
the tasked operation, linking the stated strike objective with suitable target and aimpoints, weaponeering these
aimpoints to ensure the appropriate level of damage is achieved when the strike is executed, selecting the most
appropriate missions from the TCI database to execute the tasking, and assigning these missions with the correct
number of missiles to the firing units to execute the strike.
3.8.2.1 TLAM Mission Planning
TLAM mission planning has two separate components: the overwater section of the missile flight path and the
overland section. Planning the overwater portion of the TLAM mission is the responsibility of the firing ship and
is done using the TOMAHAWK weapon control system (TWCS) or the advanced TOMAHAWK weapon
control system (ATWCS).
The over land portion of the missile flight path cannot be planned by the firing units. The primary locations for
TLAM mission planning are the cruise missile support activities (CMSAs) located in Norfolk, Virginia; Pearl
Harbor, Hawaii; and Northwood, UK. The CMSAs (as theater mission planning centers (TMPCs)) create and
disseminate TCI using the C4I infrastructure.
MDUs are the collective term referring to new missions that have been planned and added to the database and are
in the process of being distributed to firing units. They are distributed to the firing units over multiple
communication paths with EHF SATCOM as the preferred method. Other communication paths include: UHF
SATCOM, data transfer via STU-III secure telephone, and IP data transfer.
The second location for TLAM mission planning is at the CSG level with strike planning cells (SPCs). The SPC
has the requisite equipment to exploit imagery and plan and disseminate TCI. The SPC component systems are
installed on all CVNs and at COMFIFTHFLT and are designed to provide the theater and SG commander with
organic, afloat TLAM mission planning and operational flexibility. MDU dissemination from an SPC is identical
to dissemination conducted by a CMSA.
JAN 2005
3-10
NTTP 6-02
3.8.2.2 CSG TLAM Strike Coordination
TLAM strike planning and coordination may be done through web-based collaborative planning tools and
information exchange provided through CAS and other IP-based collaborative tools. TLAM planning and tasking
messages and documents such as OPTASKs, as well as other vital planning information such as intelligence,
weather, and readiness data, may be centrally located on websites for instant access via the SIPRNET. The
TOMAHAWK Strike Coordinator, CSG commander, and the firing units use dedicated SIPRNET chat rooms to
collaboratively coordinate TLAM strike execution. TLAM planning and tasking messages are also disseminated
via naval messages. A combination of message traffic and voice communications can be used as an additional
means of planning and coordination.
3.8.3 Control
Control of individual TLAM firing units while executing strike mission is through voice communications, IPbased information exchange, and existing UHF SATCOM data circuits.
3.8.4 References
1. NWP 3-03.4, Naval Strike and Air Warfare, Chapter 4
2. NTTP 3-03.1, TLAM Employment
3. NWP 3-03.2, TOMAHAWK Land-Attack Missile (TLAM) Launch Platform Weapon Systems and
Tactics.
3.9 EXPANDED MARITIME INTERCEPTION OPERATIONS
Expanded maritime interception operations (EMIO) usually requires extensive and dedicated intelligence,
surveillance, and reconnaissance (ISR) support to identify, locate, and track targets of interest. EMIO planners
and participants, in addition to accessing national and theater-intelligence databases via SIPRNET, liaison
directly with EMIO shore-based intelligence support cells using SIPRNET chat and e-mail.
MPA use HF Link 11/TADIL A to link to the SG or a shore-based TSC. These link tracks are then passed to
GCCS for inclusion into the CTP.
SH-60B helicopters use the SRQ-4 Hawklink data link to send radar and ESM data to a controlling surface ship
for onboard display and evaluation.
In addition to dedicated ISR support, the maritime interception operations (MIO) commander, on-scene
commander (OSC), and ships conducting EMIO access the CTP and COP as described in Paragraph 3.2. A
notional EMIO warfare C2 architecture is shown in Figure 3-8.
EMIO planning and coordination is done through web-based collaborative planning tools and information
exchange provided through CAS and other SIPRNET chat tools. Planning and tasking messages and documents
such as OPTASKs, along with other vital planning information such as intelligence, weather, and readiness data, are
centrally located on websites for instant access via the SIPRNET. The MIO commander, OSC, and ships conducting
EMIO use dedicated SIPRNET chat rooms, web pages, and e-mail to collaboratively plan and coordinate SUW
operations. EMIO planning and tasking messages are also disseminated via the naval messaging system.
EMIO often involve allied and coalition forces. Allied and coalition planning and coordination is described in
Paragraph 3.13 of this chapter.
3-11
JAN 2005
NTTP 6-02
Figure 3-8. Notional EMIO Warfare C2 Architecture
3.9.3 Control
Control of individual EMIO tactical units is primarily through voice communications — UHF LOS or UHF
SATCOM for ships and VHF LOS or UHF SATCOM for helicopters and MPA. The preferred method of control
for SH-60 helicopters is through the SRQ-4 Hawklink, which provides secure point-to-point voice
communications between the helicopter and its controlling ship.
Control of boarding teams is primarily through encrypted UHF and VHF portable radios.
Communications with suspect vessels is through VHF bridge-to-bridge radios.
3.9.4 Reference
NTTP 3-07.11, Maritime Interception Operations.
3.10 JOINT TASK FORCE OPERATIONS
Navy CSG and ESG staffs are not manned or trained to direct a JTF without significant augmentation. A more
likely scenario is the embarkation of a higher echelon Navy, Marine, or Army commander and staff (a Marine
expeditionary brigade (MEB) commander, for example), which is organized and trained to lead a JTF.
LCCs are the Navy’s most capable command ships, followed by LHA/LHD and CVN classes respectively. As a
practical matter, only the LCCs and LHAs/LHDs have both the space and C4I systems required to embark a joint
staff of any appreciable size.
The JTF commander and his staff have access to the CTP and COP as described in Paragraph 3.2. Additionally,
they have access to national and theater intelligence and cryptologic databases through SIPRNET and SCI
networks connectivity over SHF, CWSP, EHF, and INMARSAT.
JAN 2005
3-12
NTTP 6-02
The Joint Operation Planning and Execution System (JOPES) is the integrated, joint, conventional C2 system
used to conduct joint planning, execution, and monitoring. It is used for operational-level planning and
coordination by the JTF staff and higher echelons of command.
JTF planning and coordination is heavily dependent on web-based collaborative planning tools and information
exchange such as e-mail, chat rooms, websites, central document depositories, and VTC. The Defense
Collaboration Tool Suite (DCTS) is the joint standard for collaborative planning and is used widely by all
services except the Navy, which has determined that DCTS uses too much bandwidth for use in the limitedbandwidth shipboard environment. The Navy uses CAS for its collaborative environment, and a DCTS compliant
chat tool is being fielded as part of CAS during FY05.
A combination of message traffic and voice communications can be used as an additional means of planning and
coordination. JTF planning and tasking messages are also disseminated via naval messages. Ships capable of
supporting a JTF commander (CVN/LHA/LHD/LCC) will receive the DMS starting in FY04.
3.10.3 Control
Control of individual units within the JTF encompasses the entire spectrum of communications capabilities within
the force.
3.11 ALLIED/COALITION OPERATIONS
Communications and data exchange with allied and coalition forces is extremely complex due to information
releasability and cryptographic keymat requirements in addition to the wide array of C2 and communications
systems installed on foreign ships. When planning operations with allied and coalition navies, great care must be
taken to identify and address unique policy and technical issues that may vary significantly from country to
country. A notional allied coalition C2 architecture is shown in Figure 3-9.
HF Link 11 is used to share the air, surface, and subsurface tactical picture with allied and coalition ships.
Additionally, sanitized GCCS-M data can be transmitted via UHF SATCOM to foreign navy C2 systems.
Radiant Mercury is the Navy’s current multilevel security sanitization device.
With CENTRIXS, the USN has duplicated the technologies and operational capabilities of CaS to provide webpage replication, secure e-mail, and chat communications to allied and coalition naval forces over SATCOM
links. Due to differing information releasability issues, separate CENTRIXS networks must be established for
different foreign navies. Present CENTRIXS networks include:
1. CENTRIXS Four Eyes (CFE) — Multinational network with U.S./UK/CAN/AUS, formerly COWAN A.
2. CENTRIXS J — Bilateral network with Japan.
3. CENTRIXS K — Bilateral network with Korea.
4. CENTRIXS N — NATO network, formerly LOCE.
5. CENTRIXS MCFI — Multinational network serving nations who have joined the United States for
operations in Iraq. Currently connects approximately 50 countries.
3-13
JAN 2005
NTTP 6-02
Figure 3-9. Notional Allied/Coalition C2 Architecture
6. CENTRIXS GCTF — Multinational network serving nations who have joined the United States in the war
on terrorism. Currently connects approximately 60 countries.
Complementing CENTRIXS is Strike Force E-mail 66 (SFEM66), which uses HF radio communications for
secure e-mail transfer. Presently 11 foreign navies have installed SFEM66 systems.
3.11.3 Control
Tactical control of allied/coalition ships and aircraft is exercised primarily through voice communications. UHF
LOS, VHF, and HF are the most common, with UHF SATCOM available to some foreign nations.
JAN 2005
3-14
NTTP 6-02
CHAPTER 4
C4I Systems
4.1 SATELLITE COMMUNICATIONS
This paragraph describes the following SATCOM systems used by Navy operating forces: UHF, SHF, EHF,
GBS, CWSP, and Inmarsat-B. The Wideband Gapfiller System (WGS), expected to begin deployment in 2006, is
also discussed briefly. The SATCOM terminals that the Navy uses with each system are also described. A graphic
depicting the current satellite constellation configuration (accurate as of the date of this writing) of each existing
system is provided to help the user visualize where the satellites are deployed. However, the reader should note
that satellite constellation configurations do change from time to time to account for factors such as changing
operational needs or satellite failures. The user should consult the NNSOC SIPRNET website for the current
status and configuration of each SATCOM constellation at http://c4.nnsoc.navy.smil.mil/global/.
4.1.1 Ultrahigh Frequency Satellite Communications
The Navy UHF SATCOM system provides reliable, long-haul communications services to Navy users operating a
variety of terminal systems ranging from single channel equipment to complex multiple subsystem terminals.
UHF military satellite communications (MILSATCOM) systems provide capacity on demand for transport
services that support a wide variety of applications including SECVOX, messaging, facsimile, secondary image
transfer, packetized data service, and e-mail used during normal and contingency or crisis operations.
The UHF follow-on satellite system (UFO) is the predominant UHF system in use today. UFO satellites have
been launched to maintain an eight-satellite constellation (two per area of responsibility (AOR)) through 2010,
plus one spare. There are 39 UHF channels per satellite: seventeen 25-kHz channels, twenty-one 5-kHz channels
(Note: UFOEE-11 is equipped with two additional 5-kHz channels for a total of twenty-three 5-kHz channels),
and one jam-resistant SHF/EHF uplink 25-kHz UHF downlink channel supporting either the fleet broadcast or the
Integrated Broadcast System-Simplex (IBS-S). Eight UFOs are also EHF-capable; three UFOs were launched
with Ka-band GBS packages.
Data rates employed by UHF SATCOM networks are 64 kbps and below, but typically operate in the 2.4–9.6 kbps
range. Tactical circuits that are supported by UHF SATCOM include half-duplex voice (2.4 kbps) and data (2.4–9.6
kbps), point-to-multipoint broadcast (one way) data (2.4–9.6 kbps), and various intelligence and special user circuits.
4.1.1.1 Functions and Capabilities
The primary systems that are associated with UHF SATCOM are the high-speed fleet broadcast, UHF demand
assigned multiple access (DAMA), and mini-DAMA. DAMA serves to multiplex signals from multiple systems.
These include the CUDIXS and the NAVMACS, for messaging and teletype services; the tactical data
information exchange system (TADIXS); the tactical intelligence (TACINTEL) system; and SECVOX services.
4.1.1.2 Demand Assigned Multiple Access
DAMA is an automated channel-sharing method for multiple users, supporting concurrent use of a single UHF
MILSATCOM channel (see Figure 4-1). It allows MILSATCOM system managers to increase effective
throughput of a fixed number of satellite channels, thereby expanding available resources to support everincreasing user requirements. Demand-based assignment dynamically reallocates unused transponder space in
4-1
JAN 2005
NTTP 6-02
1 CHANNEL
4
3
4
4
3
4
3
1
2
2
1
4
3
0
ONE
FRAME
1
4
4
3
3
ONE
SLOT
4
3
2
2
1
1
OTCIXS
4
3
2
3
0
3
4
2
3
3
2
SECURE VOICE
1
SSIXS
0
TACINTEL
TADIXS
NOTES
1. GRAPHIC REPRESENTATION OF FRAMES AND SLOTS NOT TO SCALE.
2. ONE SATELLITE CHANNEL CARRIES ALL CIRCUITS.
TELETYPE
Figure 4-1. Demand Assigned Multiple Access
NRT, based on service precedence, increasing loading efficiency by roughly 4 to 20 times over the current
system. DAMA channels are partitioned into TDMA intervals of varying duration called “timeslots,” each of
which can accommodate communications at various specific data rates. DAMA protocols allow user terminals to
request channel access from a channel controller (CC); the CC then assigns user timeslots based on:
1. User data rate
2. User priority
3. Service precedence
4. Timeslot availability
5. Link quality.
When access to the channel is no longer required, the CC releases that timeslot for assignment to another
communications service, consequently providing users increased effective throughput over the dedicated FLTSAT
and UFO access. Both the 5-kHz and the 25-kHz UHF SATCOM waveforms provide a DAMA capability.
There are currently two hardware implementations of DAMA: full (or quad) and mini-DAMA. AN/USC-72(V)1
DAMA is specifically designed for ship, shore, and submarine platforms and consists of the TD-1271 multiplexer
and the AN/WSC-3 transceiver. Mini-DAMA (AN/USC-42) integrates the TD 1271 and AN/WSC-3 transceiver
functions into a single system reducing the DAMA system size and footprint requirements. Mini-DAMA provides
additional UHF communications modes such as interoperable 5-KHz Air Force TDMA, 5-KHz Navy non-TDMA
and UHF LOS communications.
4.1.1.3 Shore-Based Terminal Locations
Shore-based installations use existing naval communications centers and reside at command operations centers.
Three NCTAMS and one NCTS in selected geographical areas are primarily responsible for naval UHF SATCOM:
JAN 2005
4-2
NTTP 6-02
1. NCTAMS LANT, Norfolk, VA
2. NCTAMS EURCENT, Capodichino, Italy
3. NCTAMS PAC, Wahiawa, HI
4. NCTS Guam, Finegayan, Guam.
4.1.1.4 Space Segment
The UHF space segment is comprised of 2 FLTSAT satellites (FLTSAT 7 and 8) and 10 UFO satellites (UFO 2–
11) as shown in Figure 4-2.
4.1.2 Super-High Frequency Defense Satellite Communications System
SHF DSCS provides tactical commanders and warfighters seamless and robust access to the DII/DISN for
improved C4ISR support, as well as enhanced communications interoperability with other U.S. forces operating
in a joint tactical environment.
The SHF SATCOM terminal AN/WSC-6(V)5/7/9 is designed for use on a variety of fleet platforms and provides
single or dual channel access to the DSCS. Single channel access provides up to 2048 kbps of data and supports
plain old telephone system (POTS), METOC, record message traffic, VIXS, telemedicine, NIPRNET, SIPRNET,
and JWICS. The single channel system aboard ship utilizes a dual or single antenna system to provide an
uninterrupted look angle to the satellite.
The dual channel system’s Channel One interfaces ashore with DSCS Earth terminals and supports POTS,
METOC, record message traffic, VIXS, telemedicine, NIPRNET, SIPRNET, and JWICS. Channel Two interfaces
ashore with either DSCS Earth terminals or with the GMF Network. Shipboard Channel Two supports joint tritactical communications through the AN/SSQ-122(V) series tactical switching system (TSS).
Ship-to-shore DSCS link data rates can range from 128 kbps to 1536 kbps as validated by appropriate authority to
support the ship’s training or operational mission communications requirements. DSCS is one of two high data
rate SATCOM systems installed on board command and large deck ships, and variant systems (AN/WSC-7(V)7
and 9) are being fielded on the smaller platforms supporting their wideband requirements.
SHF SATCOM interface to shipboard systems is accomplished through the use of various multiplexers and the
ADNS. This same infrastructure is provided ashore for interfacing the shore network.
4.1.2.1 Ground Mobile Force
GMF SHF SATCOM terminals operate as a special-user subnetwork through the DSCS. The GMF SHF SATCOM
media extends the range of terrestrial communications with improved reliability, speed, and deployment setup time
to ground users. It supports the need to exchange communications traffic during all phases of actual conflicts and
training exercises. GMF terminals can be deployed in subnetworks ranging in complexity from a small independent
cluster up to an elaborate network capable of supporting joint and combined operations. These subnetworks are built
on the basis of interconnected clusters or stars using nodal or hub terminals to support spoke and link terminals.
Figure 4-3 illustrates a simplified concept for a typical Tri-Service GMF deployment.
4.1.2.2 Ground Site Locations
DSCS terminals are located at 14 teleport/step sites throughout the world. Of these sites, the Navy has equipped
nine for ship support and uses the Fort Gordon site for training. Specifically, the Navy uses four primary sites
(Northwest, VA; Wahiawa, HI; Manama, Bahrain; and Lago di Patria, Italy) to support continuous fleet
requirements (see Figure 4-4). The remaining five sites (Landstuhl, Germany; Fort Buckner, Okinawa, Japan; Fort
Detrick, MD; Camp Roberts, CA; and Fort Belvoir, VA) serve as secondary/alternate sites for restoral and/or
4-3
JAN 2005
NTTP 6-02
JAN 2005
4-4
Figure 4-2. UHF Space Segment
NTTP 6-02
contingency service. Navy sites provide full-duplex ship-to-shore and ship-to-ship communications, supporting
data and voice operational and administrative communications requirements. Additional Step sites include
MacDill AFB, FL; Croughton, UK; Riyadh, Saudi Arabia; Fort Bragg, NC; and Fort Meade, MD.
4.1.2.3 DSCS Space Segment
The SHF DSCS space segment is comprised of 5 operational DSCS satellites and 11 spares as shown in Figure 4-5.
4.1.2.4 Shipboard Configuration
SHF SATCOM capability is provided to Navy surface ships and submarines by several WSC-6 variants according
to the requirements of those platforms.
1. The AN/WSC-6(V)4 is a single channel SHF SATCOM terminal currently installed on several
conventional and nuclear aircraft carriers (CVs/CVNs). It is made up of either a single or dual antenna
system depending on ship class.
2. The AN/WSC-6(V)5 is an upgrade to the AN/WSC-6(V)4 on CVs/CVNs, amphibious assault ships
(LHAs/LHDs) and fleet flagships. The AN/WSC-6(V)5 is either a single or dual 7-foot antenna system
that provides dual channel access to the DSCS satellite constellation. While no mission is specifically
designated for the second channel on CVs/CVNs, on LHAs/LHDs and fleet flagships, the second channel
is utilized for support of embarked Marines.
3. The AN/WSC-6(V)7 is a dual 7-foot antenna system for cruisers and an upgrade for amphibious transport
dock ships (CGs/LSDs/LPDs) that provides single channel access to the DSCS satellite constellation.
4. The AN/WSC-6(V)9 is a dual 5-foot antenna system on guided missile destroyers (DDGs) that provides
nonsimultaneous access to either X-band (DSCS) or C-band (commercial satellites).
Details for each AN/WSC-6 variant are shown in Figure 4-6.
Figure 4-3. Ground Mobile Force SHF
4-5
JAN 2005
NTTP 6-02
JAN 2005
4-6
Figure 4-4. Primary Navy DSCS Step Sites and Shore Architecture
NTTP 6-02
Figure 4-5. SHF DSCS Space Segment
4.1.2.5 SHF SATCOM Access
Access to SHF SATCOM service is provided through full-period terminations established between afloat users
and gateway Earth-station service providers ashore. Full-period terminations are dedicated circuits that provide
communications between commanders afloat and ashore. These terminations require allocation of limited assets;
therefore, the rules for request, approval, and establishing such circuits are stringent. Commanders and individual
units may request full-period termination during special operations, deployments, periods of intense training, or
exercises when it is determined that normal ship-shore links will not satisfy volume, data rate, sensitivity, or
effective C2 requirements. Ships will include a SHF SATCOM termination request to the DSCS network manager
and terminating NCTAMS. The following guidance applies:
1. All DOD and non-DOD organizations needing access to MILSATCOM services are required to follow the
procedures for submitting requests outlined in the DISA TMS-C Toolkit Users Manual. In accordance with
CJCSI 6250.01, all long-term requirements for use of MILSATCOM systems must be validated by the
theater combatant commander, and approved by the Chairman of the Joint Chiefs of Staff (CJCS) before
access to a space segment is authorized.
2. Users with short-term, one-time, nonrecurring requirements may be authorized access without validation.
This may occur if the system operational manager (SOM) determines the requirement satisfies the CJCSI
6250.01 criteria, and can be supported without adversely impacting other approved user requirements.
4-7
JAN 2005
NTTP 6-02
Terminal
Channels
& Bands
Power
Amp
Modem
Antenna
Current
Installation
(V)1
Single X
8 KW
50 Kbps
4 ft (1.2 m)
SURTAS
(V)4
Single X
350 W
COTS 2048 Kbps
7 ft (2.2 m)
5
Upgrade to Dual
Channel (V)7
(V)5
Dual X
2 KW
COTS 2048 Kbps
1
7 ft (2.2 m)
13 Dual Ant
Terminal
Objective*
0
(V)7 Upgrade
0
(V)5 Upgrade
27
11 Single Ant
(V)7
Single X
700 W
3
(V)9
Dual X
Dual X
Single C
Dual X
2 KW
800 W
2 KW
(V)9
Upgrade
Single Ka
40 W
Single C
800 W
4
COTS 2048 Kbps
COTS 2048 Kbps
1
2
EBEM
10 Mbps Transmit
30 Mbps Receive
21 Dual Ant
3 Single
TBI FY04
43
5 ft (1.5 m)
3 Dual Antenna
31
1.5 m (2X/Ka+C)
2.5 m (2X+C)
0
84
7 ft (2.2 m)
5
Notes:
* Includes SCN-funded ships.
1. Modem will be upgraded with EBEM in FY05-FY07.
2. All (V)9 terminals will be back-fitted with Ka-Band and EBEM.
3. POWER COMBINED DUAL 350W HPAs, TOTAL LINEAR POWER 700W.
4. 16W linear power at each antenna.
Figure 4-6. AN/WSC-6 Variants
3. Users with urgent requirements to support crisis, contingency, or wartime operational missions can be
authorized access without validation if the requirement is supported by a combatant commander and
approved by the joint communications satellite center (JCSC).
4. All other requirements must be validated and approved through the CJCSI 6250.01 process, and assigned a
Satellite Communications Database number before the user is authorized to request access to a space
segment.
5. Although each naval unit with SATCOM capability may have a valid operational requirement, other
higher priority operational requirements and limited space-segment capacity can restrict access. Naval
units requesting a routine SATCOM termination must submit the request to the appropriate fleet
commander in accordance with fleet commander instructions. Each COCOM may impose their own
SATCOM termination submission time line criteria.
4.1.3 Commercial Wideband SATCOM Program
The C-band commercial SATCOM capability provides the bulk wideband supplementary support not available
via the SHF DSCS. The CWSP is an outgrowth of the Challenge Athena (CA) series of demonstrations that began
in FY92 to provide full-duplex low, medium, and high data rates up to T-1 (1.544 Mbps) on Navy ships using
commercial services. The Navy currently uses leased services on General Electric and INTELSAT commercial
satellites via leased gateway Earth stations and COTS/nondevelopmental item (NDI) shipboard terminals from
Harris. Commercial INTELSAT-compatible gateway sites at Pearl City, HI; Steele Valley, CA; and Holmdel, NJ;
and a British TELECOM site at Martlesham, UK, provide shore uplink/downlink facilities. Connectivity is extended
via leased terrestrial means to Navy gateway hubs at NCTAMS LANT, NCTAMS PAC, and NCTS San Diego.
JAN 2005
4-8
NTTP 6-02
4.1.3.1 System Characteristics
1. Leverages commercial SATCOM service/terminals
2. Modem/connectivity up to 2.048 Mbps
3. Global coverage (9 satellites/12 transponders)
4. 5 Earth stations
5. Nine-foot shipboard antenna
6. Full-duplex LDR, MDR, and high data rate (HDR) up to E1 (2.048 Mbps)
7. Primary imagery path until GBS fully operational
8. Uses COTS/NDI SATCOM terminal equipment and leased commercial satellite bandwidth.
9. Surge capability — on orbit inventory
10. Satellite reliability historically excellent.
CWSP terminals operate in the SHF C-band frequency spectrum and provide capacity for HDR requirements,
e.g., full motion VTC, primary national imagery, Tactical Engagement Simulation System (TESS), JWICS, joint
deployable intelligence support system (JDISS), Joint Services Image Processing System–Navy (JSIPS–N),
telemedicine, teletraining, distance learning, as well as NIPRNET/SIPRNET, telephones, and e-mail. CWSP
connects to all naval command ships including commander task force (CTF), command ships (LCCs and AGFs),
and CSG (CV/CVN) and large deck ESG ships (LHD, LHA, and soon LPD 17). These ships each support the
communications requirements for the operational battle staffs that support planning and execution of joint/combined
naval operations.
4.1.3.2 Ground Site Locations
Commercial wideband currently connects to ships at sea through one of 4 major Earth stations. Those Earth
stations are located at Steele Valley, CA; Pearl City, HI; Holmdel, NJ; and Martlesham, UK (Figure 4-7). The
Earth stations are operated by commercial entities. The CWSP leases bidirectional commercial satellite bandwidth
from these commercial sites to support wide bandwidth voice, video, and data requirements of Navy command
ships (LCC, AGF, CVN, CV, LHD, LHA, LPD-17) at sea. Each Earth station is connected to one of three major
Navy fleet gateways. The three facilities are NCTAMS PAC at Wahiawa, HI, and NCTS San Diego, CA, for
Pacific Ocean connections, and NCTAMS LANT at Norfolk, VA, for Atlantic and IO connections.
T-3 circuits (45 Mbps) are used to connect each of the Earth stations to the central naval communications
facilities. The connectivity to each ship is provided over a single E-1 from the Earth station to the AN/WSC-8
terminal aboard the ship. Imagery typically consumes 768 kbps of the total of 2,048 kbps on the E-1, leaving the
additional bandwidth available for the ship’s needs. This available bandwidth is used for a variety of other circuits
including voice, video, and data.
4.1.4 Wideband Gapfiller System
Starting in mid-2005, WGS satellites will provide near-term service continuation and augmentation currently
provided by DSCS, and GBS Ka services available via GBS payloads on UFO satellites. WGS satellites will
complement the DSCS III service life enhancement program (SLEP) and GBS payloads and offset the eventual
decline in DSCS III capability. Together these assets will provide wideband services during the transition period
between today’s systems and the advent of the objective X/Ka wideband system or AWS in 2008. This
4-9
JAN 2005
NTTP 6-02
Figure 4-7. CWSP Architecture
combination of WGS and DSCS satellites, GBS and wideband payloads and platform control assets, and Earth
terminals operating with them has been referred to as the interim wideband system (IWS).
WGS will provide services to the DOD and the Ministry of Defense for Canada as well as to other Government
and allied users under unstressed conditions. The system will support continuous 24-hours-per-day wideband
satellite services to tactical users and some fixed infrastructure users. Limited protected services will be provided
under conditions of stress to selected users employing terrestrial modems capable of providing protection against
jamming.
The combined wideband SATCOM system consists of space vehicles of multiple types, control terminals and
facilities, and user terminals. The WGS is limited to the Gapfiller satellites and associated control equipment and
software that augment currently existing facilities.
The space segment will support communication services by operating in the military X-band frequency, and in the
WGS broadcast Ka-band frequency, similar to the Phase II GBS in service today, in order to interoperate with
existing and new X-band and GBS terminals. The WGS will also provide a new two-way military Ka-band
capability to support the expected military mobile/tactical two-way Ka terminal population with greatly increased
system capacity. The satellite payload shall be capable of supporting at least a 1.2 gigabytes per second (GBps)
aggregate simplex throughput. Each satellite orbital configuration will provide services from 65° north latitude to
65° south latitude, and for all longitudes accommodated within the field of view of the satellite. As an objective,
the satellite will provide services to 70° north latitude. X-band services will augment services provided by DSCS
III satellites. The Ka-band services will augment broadcast service provided by GBS payloads on UFO satellites,
and also support two-way network services besides broadcast. Additionally, Gapfiller satellites will support
services that require crossbanded connectivity: X-band uplinks to Ka-band downlinks and Ka-band uplinks to Xband downlinks. All Gapfiller satellite configurations will be of a functionally identical design within each orbital
position.
JAN 2005
4-10
NTTP 6-02
Gapfiller will provide an increase in access for both transportable/mobile and fixed users. At the same time, the
expected number of Gapfiller satellites alone will not provide full 65°N-to-65°S worldwide coverage across all
intended coverage areas and all longitudes. There will be a continuing need for these users to access the Gapfiller
satellites and the two or more DSCS III service life enhancement programs (SLEPs) to provide worldwide
coverage.
The Gapfiller satellites will support a variety of network topologies that include broadcast, hub-spoke, netted, and
point-to-point connectivities. Limited protection against jamming or interference will, in general, only be possible
for those communications networks that employ modems with modulation schemes capable of providing
protection against jamming. In certain situations, gain discrimination that may be inherent in the design and
emplacement of the Gapfiller satellite antenna patterns may also provide some measure of protection against
jamming and interference sources located at various distances from friendly forces.
The Gapfiller satellites will support Ka-band terminals located in several narrow coverage areas, and in at least one
expanded narrow coverage area. The Gapfiller satellites will provide two-way and broadcast services within narrow
coverage areas to deployed tactical forces in theater as well as to fixed gateways, broadcast injection sites, satellite
control sites, and out-of-theater tactical users such as air bases and naval SGs. The expanded narrow coverage area is
several times larger than the narrow coverage area.
4.1.5 Navy Extremely High Frequency Satellite Program
The Navy’s EHF SATCOM Program provides highly reliable tactical and strategic communication services to the
USN, United States Marine Corps (USMC), and joint elements ashore and afloat. This high degree of reliability is
achieved with an advanced technology waveform that distinguishes EHF SATCOM from all other
communications systems. EHF has two operating modes: LDR and MDR.
4.1.5.1 Capabilities
The EHF spectrum possesses characteristics absent or relatively limited in the lower frequency bands: wide
operating bandwidth, narrow uplink beamwidth, low susceptibility to scintillation, and low probability of
intercept/detection. EHF provides or supports:
1. Point-to-point (one-to-one)
2. Netted (many-to-many)
3. Half-full duplex (one way/two way)
4. Broadcast (one to many)
5. Low probability of intercept (LPI)
6. High anti-jam (AJ) and scintillation threat protection
7. Very wide bandwidth
8. Worldwide coverage
9. Polar coverage
10. Joint interoperability
11. Narrow antenna beamwidth
12. Independence from shore terminal support
4-11
JAN 2005
NTTP 6-02
13. Shore-shore, ship-shore, ship-ship, sub-shore, sub-ship service
14. Selected electromagnetic pulse hardened terminals.
The EHF SATCOM system is designed to support services for, but is not limited to, the following services:
1. Emergency action message (EAM) dissemination
2. Theater command force direction and reporting networks (voice-data)
3. JTF (voice-data)
4. Exchange of targeting data
5. Group and force command (voice)
6. Fleet broadcast
7. Submarine reportback
8. Submarine information exchange (data).
4.1.5.2 EHF Low Data Rate
EHF LDR is capable of supporting several discrete data rates up to and including 2,400 BPS. However, each
satellite has been designed with a slightly different set of rates that can be accommodated (see Figure 4-8).
FLTSAT EHF package (on FLTSAT 7–8) supports 75, 150, 300, 1,200, and 2,400 BPS; UFO EHF package (UFO
3–10) supports these same rates and is also capable of crossbanding (receiving a signal in one portion of the RF
spectrum and retransmitting the signal in another portion of the RF spectrum) to UHF at 4,800 and 9,600 BPS;
MILSTAR (Flight 1, 2, 4, 5, 6) can support all the FEP rates with an additional 600 BPS service.
4.1.5.3 EHF Medium Data Rate
EHF MDR protocol supports up to a T-1 data rate (1.544 Mbps) (see Figure 4-9). Throughput being a function of
gain calculations (primarily determined by antenna dimensions) means not all terminals will be capable of
utilizing MDR’s maximum potential. What MDR lacks in signal robustness (compared to EHF LDR), it more
than makes up for in data rates: 4.8, 9.6, 16, 19.2, 32, 64, 128, 256, 512, 1024, and 1544 kbps, with up to 128+
kbps for protected systems. EHF MDR broadcast service does not include the ability to crossband the fleet
broadcast to UHF. Three MILSTAR II satellites (Flights 4, 5, and 6) provide the space segment MDR capability.
The current connectivity for large and small deck ships is based upon a hub-spoke ADNS architecture, with the
hub being at the NOC and the spokes being individual 128 kbps circuits to MDR-equipped platforms. The hub
consists of an ADNS router with 12 high-speed serial ports. Although the router supports 12 ports, only enough
cryptographic assets are installed to support 10 circuits.
The ADNS connectivity via EHF MDR is installed at four shore sites: NCTAMS LANT, NCTAMS PAC,
NCTAMS EURCENT, and NCTAMS Bahrain. The remaining MDR capacity is used for ship-ship links (e.g.,
VTC) or SG voice networks (e.g., advanced narrowband digital voice terminal (ANDVT)).
EHF MDR is available to all naval command ships including CTF command ships (LCCs and AGFs), SG
command ships (CVs and CVNs), and ESG command ships (LHD, LHA, and soon LPD 17), as well as all
TOMAHAWK platforms (DDG and CG).
JAN 2005
4-12
NTTP 6-02
Figure 4-8.
EHF Limited Low Data Rate
Figure 4-9. EHF Medium Data Rate
4-13
JAN 2005
NTTP 6-02
4.1.5.4 Polar EHF
The polar EHF system provides EHF communications supporting mission-essential C2 requirements above 65º
north latitude (see Figure 4-10).
The polar orbiting satellites and associated EHF communications payloads comprise the space segment for the
polar EHF system. Polar satellites are provided and maintained by a classified host agency of the Federal
Government. Each of these satellites circles the earth in an inclined highly elliptical orbit (HEO), commonly
referred to as the “Molniya” orbit.
The polar EHF system currently employs a single payload hosted on a classified satellite platform. In the 2004
timeframe a second payload (on a separate hosted satellite) will be added to provide 24-hour coverage, and in
2005, the third and final polar EHF payload will be activated aboard another host satellite.
Polar coverage is defined as the geographic region of the earth above 65º north latitude. The polar EHF system
will provide 14-hour coverage to this region in the near term and 24-hour coverage after 2004.
Near-term polar coverage provided by a single payload is available twice daily for 7 hours at a time. After 2004,
24-hour coverage will be achieved using two such payloads with their orbits phased near 180º apart. It is
important to note that the two-satellite constellation will still provide only 7 hours of continuous polar
communications to individual users. As one satellite sets over the horizon (OTH), the second satellite will be
rising, and users will need to transition from one to the other. This requires tearing down services on the setting
satellite and re-establishing communications on the rising satellite.
POLAR EHF
Space Segment
Modified UFO/EE Payload in
Molniya Orbit on Classified Host
Satellite
12 Hour Orbital Period
7 Hours of Coverage per Orbit
14 Hours of Coverage per Day Above 65°N
Land Lines
SATCOM
Gateway
Bangor/Brunswick
Gateway Terminal
COMSUBGRUS
Bangor, WA
Gateway Terminal
TSC Brunswick
Brusnwick, ME
All EHF Submarine Terminals
Northern Deployers Have Priority
COMSUBPAC
COMSUBLANT
Figure 4-10. Polar EHF
JAN 2005
4-14
NTTP 6-02
Polar EHF payloads each have two steerable beams: an 18º steerable Earth coverage (EC) beam and a 5º steerable
spot beam. The motors used for pointing each beam will be deactivated at the end of each 7-hour operations
period. When the payload is reactivated at the beginning of the next operations period, both beams will
automatically point to their last commanded position.
Polar EHF communications payloads are currently capable of LDR-only communications with maximum service
data rates of 2.4 kbps per channel.
The terminal at Bangor, WA, is the primary network control terminal supporting naval units operating on polar
EHF payloads. If the shore gateway terminal at Bangor, WA, becomes inoperative, restoral connectivity is
obtained via the EHF terminal at Brunswick, ME.
4.1.5.5 EHF Space Segment
The EHF space segment consists of one polar, five MILSTAR, and seven UFO satellites as shown in Figure 4-11.
4.1.5.6 Ground Infrastructure
EHF ground infrastructure is shown in Figure 4-12.
4.1.6 Mobile Subscriber Service (Iridium)
Mobile subscriber service (MSS) systems are satellite-based commercial communications services providing
voice and data communications to users equipped with mobile satellite terminals (see Figure 4-13). Common
characteristics of MSS systems include coverage of significant portions of the Earth's surface, cellular telephonelike use, and connectivity to the public switched telephone network (PSTN) and the Internet. Navy MSS use is
currently limited to Iridium. Although authorized, the Navy does not use Inmarsat as an MSS application. Use of
other MSS providers requires a waiver from DISA.
Figure 4-11. EHF Space Segment
4-15
JAN 2005
NTTP 6-02
The Iridium system is the first commercially available, cross-linked, pole-to-pole global MSS. It is a satellitebased, global wireless personal communications network designed to permit any type of narrowband wireless
transmission (i.e., voice, data, fax, or paging) to reach its destination nearly anywhere on Earth.
The Iridium network consists of a space segment (see Figure 4-14) employing a constellation of 66 satellites in
six evenly spaced, nearly polar orbital planes, about 420 nm above the Earth’s surface. By linking the satellites
and terrestrial gateways, the system provides global access and coverage through specially designed portable and
mobile telephones. Seamless connectivity to cellular systems anywhere in the world is provided to phones
equipped with an optional cellular cassette.
An Iridium gateway links the orbiting Iridium constellation with the various terrestrial telecommunication
systems located within the gateway's territory. It enables subscribers to call and receive calls (unless barred) from
non-Iridium telephones throughout the world and provides a “home” where the subscriber’s location and calling
activity are discretely captured and monitored.
For MSS customers, DOD has established a dedicated Government MSS gateway in Wahiawa, HI, for
government use through the DISN. Through this gateway EMSS subscribers will have a direct connection into the
DISN, which is capable of providing secure services, in addition to providing nonsecure access to the PSTN.
The Iridium system is owned and operated by Iridium LLC, a private international consortium of leading
telecommunication and industrial companies. Motorola is the exclusive supplier of the gateways that interconnect
the Iridium satellite network with the various terrestrial public (and private) switched telephone networks
(PSTNs) and cellular telephone systems throughout the world.
DISA has contracted with Motorola to provide EMSS services to DOD and other Federal agencies. Provisioning
EMSS equipment and services will be accomplished through DOD’s process for procuring telecommunications
services, managed by the Defense Information Technology Contracting Organization (DITCO). The requester is
responsible for completing the approval actions as specified in the Service/agency EMSS approval procedures.
Iridium provides:
1. One full duplex channel capability for small platforms, subs, mobile, littoral, or shore/beach units secure or
unsecure voice
2. Unsecure data/Internet up to 10 kbps
3. True global coverage (90° N to 90° S)
4. Small battery-operated handheld terminals and shoebox-sized shipboard terminals
5. 8-inch omnidirectional antenna
6. L-band
7. Secure capable system
8. NSA certified type 1 crypto module
9. Data capable 2.4 ISP dial-up or up to 10 kbps direct Internet connection.
JAN 2005
4-16
4-17
EHF Ground Segment
NTTP 6-02
JAN 2005
Figure 4-12.
NTTP 6-02
Figure 4-13. Iridium Ground Architecture
The Constellation
- 66 Satellites
- 6 Planes
- 11 Satellites Per Plane
- 89 Degree Inclination
- Birds in Constant Motion
Key Points
- Global Coverage — Including Poles
- Cross Linked Processing Satellites
- Unique in Commercial Arena
- User Always in View of at Least 2
Satellites
- Constellation Viable to Mid 2010
Figure 4-14. Iridium Space Segment
JAN 2005
4-18
NTTP 6-02
4.1.7 Inmarsat-B High Speed Data
Note
INMARSAT formerly was an acronym for international maritime satellite. As of 1999, it
is the registered trademark of Inmarsat LLC and is no longer an acronym; therefore, it is
spelled in sentence case.
The Inmarsat HSD system continues to be a critical communications path for SIPRNET, NIPRNET, and
telephone ship-to-shore access for all Navy ships less the CV/CVN/LHA/LHD/AGF and LCC classes. This
multipurpose SATCOM system provides both simultaneous voice and IP data at 64 kbps. By providing access to
the DOD unclassified and classified IP networks, all ships of an SG become participants in a WAN that enables
real-time collaborative planning and significantly improved unit SA and group C2. In addition, it supports quality
of life communications supporting voice and e-mail exchange between sailors at sea and friends and family
ashore.
The Inmarsat program augments MILSATCOM systems to provide added capacity for fleet voice and data
services. The program provides for leases of commercial Inmarsat satellite channels and procurement and fielding
of Inmarsat terminals and ancillary equipment to enhance the leased service. In addition the program
accommodates the lease of necessary terrestrial connectivity between Navy hubs (NCTAMS, NCTS San Diego,
NCTS Bahrain) and the commercial Stratos Mobile Networks–owned Earth terminals in Canada, the United
Kingdom, and New Zealand.
The Inmarsat terminals operate in the UHF L-band via the geostationary Inmarsat satellite constellation, enabling
point-to-point voice, facsimile, and data. The Inmarsat-A terminal provides up to 9.6 kbps, and is being replaced
with Inmarsat-B terminals. The Inmarsat-B terminal is based on digital technology, provides digital voice at 16
kbps, data and facsimile up to 9.6 kbps. The Navy’s primary fleet implementation of Inmarsat utilizes a built-in
digital modem with capability up to 64 kbps (see Figure 4-15).
As part of IT-21 requirements, Inmarsat-B HSD multiplexers (AN/FCC-100(V)9s) have been procured and
installed in conjunction with leasing dedicated full-time 64 kbps channels. Some ships are receiving dual
Inmarsat-B HSD installations. Ships receiving dual installations receive one system that is multiplexed through an
AN/FCC-100(V)9 for voice and facsimile, and one system that is configured for data only. These are currently
two independent systems. Multiplexers and other equipment have also been installed at the Navy hubs to support
Inmarsat HSD. The multiplexers are reconfigurable and support variable voice/data rates up to 64 kbps aggregate,
including voice (nominally 3 official lines and one for unofficial Navy Exchange Command (NEXCOM)–
supported afloat personal telephone service (APTS), and a data link for NIPRNET, SIPRNET, and JWICS at a
nominal data rate of 32 kbps).
A summary of Inmarsat capabilities include:
1. Worldwide coverage
2. Narrowband point-to-point voice, fax, and data
3. Inmarsat-B HSD single system = 64 kbps; dual system = 128 kbps (2 independent 64 kbps systems)
4. SIPRNET, NIPRNET, and JWICS — 32 kbps
5. Voice channels (dial tones are at San Diego, Norfolk, and Hawaii)
6. Three official lines: 9.6 kbps STU III, 9.6 kbps, and 4.8 kbps
4-19
JAN 2005
NTTP 6-02
IOR
109° E
IOR
143.5° E
POR
142° W
AOR-W
98° W
APTS Breakout
AOR-E
25° E
Commercial Site
Government Site
Official Phone
Commercial
Terrestrial
Connectivity
ISDN Connection
Auckland,
NZ
(72 Total)
E-1
66 Terminations
50 Data/Voice &
16 Data Only
23 ISDN Drops (4QFY03)
E-1
Phone Switch
NCTAMS
LANT
DS3
T-1
NCTAMS
EURCENT
Phone Switch
Phone Switch
T-1
Phone Switch
APTS
APTS
NCTS SAN
DIEGO
T-1
48 Terminations
(31 Total)
E-1
(60 Total)
T-1
T-1
Goonhilly,
UK
(48 Total)
T-1
3 x T-1
NCTAMS
PAC
Laurentides,
CAN
ISDN
Cloud
- 4QFY03
50 Terminations
E-1
E-1
Phone
Backhaul
NCTS
BAHRAIN
Phone Switch
48 Terminations
30 ISDN Drops
(4QFY03)
(31 Total) E-1 AUK to BAH
Figure 4-15. Inmarsat Architecture
7. NEXCOM APTS: 4.8 kbps
8. Dual system adds one 64 kbps data-only channel.
4.1.7.2 Platforms
DDG/FFG/AOE/ARS/MCM/MHC-ship classes are equipped with single Inmarsat-B HSD systems.
CG/DDG/LPD/LSD-ship classes are equipped with dual Inmarsat systems in order to provide additional
bandwidth above 64 kbps as well as system redundancy to mitigate superstructure-antenna blockage outages.
4.1.8 Global Broadcast Service
The GBS is a joint service program formally established in March 1996 with the United States Air Force (USAF)
designated as the executive agent for management. The GBS provides a near-worldwide, high-capacity, one-way
transmission of video, mapping, charting and geodesy, imagery, weather, and other digital data as required to
support joint military forces in garrison and in theater. The GBS system will broadcast via communication
payloads on a constellation of 3 UFO geosynchronous satellites, augmented by leased commercial satellites.
The transmit segment of the GBS system includes both fixed and transportable uplinks. The fixed version of this
segment PIP provides the collection of data from the DISN, scheduling of the broadcasts, and transmitting of the
broadcasts to the space segment. The transportable version of the transmit segment (transportable injection point)
will provide theater commanders the capability to transmit theater information directly to forward users or rear
areas to augment the information in the PIP broadcast. The transmit segment will be fitted with equipment to
support multiple frequency bands allowing operation with both military and commercial satellites.
JAN 2005
4-20
NTTP 6-02
There are three PIPs collocated at the SBM centers at NCTAMS LANT in Norfolk, VA; NCTAMS PAC in
Wahiawa, HI; and the NCTS in Sigonella, Italy.
Each SBM performs information and packaging functions, and generates the uplinks to the satellite on up to four
carriers. The SBM also responds to and prioritizes user information requests from the field and the fleet. The PIP
uplink terminal for GBS is designed to support inland, mobile, and afloat platforms. Each PIP provides access to
one of three UFO satellites equipped with a GBS payload (UFO-8, UFO-9, and UFO-10). The GBS payload
includes four transponders of 23.5 Mbps each, for a total of 94 Mbps per satellite. The satellite has two receive
antennas: one fixed and one steerable. The fixed narrow spot beam receives data from the PIP, and the steerable
beam downlinks the signals to receive terminals in the theater of operations (see Figure 4-16).
4.1.8.2 Transmitted Data
Data is transmitted to users from the satellite via three steerable spot beam antennas. Two of these cover an area
of 500 nm radius and support a nominal data rate of 23.5 Mbps. The third downlink is a wide spot beam that
covers an area of about 2,000 nm radius, and supports a data range of 12–23.5 Mbps. The ships and ground
terminals must be in a spot beam to receive information.
A total of 434 GBS receive suites including shipboard, subsurface, and shore-based systems are envisioned to be
fielded by the year 2010. All combatant ship and submarine requirements are expected to be equipped by 2006.
Submarines shall be equipped in conjunction with installation of their submarine HDR antenna capability.
4.1.9 Television Direct-to-Sailors
Television direct-to-sailors (TV-DTS) brings enhanced SA and quality-of-life programming to Sailors and
Marines at sea. The TV-DTS program provides capability for a continuous worldwide Armed Forces Radio and
Television Service (AFRTS) television, audio, and data broadcast to Navy forces. TV-DTS is a Navy-funded
initiative and provides major networks such as CNN and ESPN broadcast via C-band with nearly worldwide
coverage television and radio programming obtained by, and generated from, the AFRTS broadcast center. The
installed system includes:
UFO-10
UFO-9
Indian Ocean
Atlantic
500 nm
Steerable Spotbeams
23.5 Mbps
UFO-8
Pacific
2000 nm
Steerable Spotbeam
12 Mbps
Satellite Field of View
Figure 4-16. GBS Spot Beams
4-21
JAN 2005
NTTP 6-02
1. Video Channel One — ABC, CBS, CNN, Fox, NBC/News Programming
2. Video Channel Two — ABC, CBS, CNN, ESPN, Fox, NBC/Sports Programming
3. Video Channel Three — ABC, CBS, CNN, Fox, NBC/Entertainment Programming
4. Four radio channels — Music, News, Live Sports, Information
5. Data Channel — 24-hour news feed: Early Bird, NAVNEWS, Stars and Stripes, Times Fax.
TV-DTS uses C-band commercially leased frequencies to broadcast a 3.6 Mbps signal to shipboard terminals with
a 1.2 meter receive-only antenna. Shipboard terminals also have a Ku capability to receive satellite television
broadcasts directly from commercial providers such as Direct TV, Dish Network, etc. AFRTS programming
originates from facilities at March AFB, CA, and is relayed to uplink facilities located in CONUS east and west
coast, and Europe (see Figure 4-17).
4.1.10 Fleet SATCOM Capabilities
Figure 4-18 shows the distribution of SATCOM systems by ship class.
Terrestrial/Space Architecture
TV-DTS
IS-701
@ 180E
AMC-1
@ 103W
STEELE VALLEY
CA
MARCH ARB
RIVERSIDE CA
HOLMDEL
NJ
AMC – Americom
ARB – Air Reserve Base
IS – INTELSAT Satellite
NSS – New Skies Satellite
Figure 4-17. TV-DTS Architecture
JAN 2005
IS-906
@ 64E
NSS-7
@ 338E
4-22
GOONHILLY
UK
NTTP 6-02
Fleet
Terminal Configuration
CV/CVN AGF/LCC LHA LHD LPD17 LPD
LSD
CG
DDG
DD
MCM/ SSN/
FFG MHC SSBN T-AH AS
USC-38 EHF
SSR-2(A) GBS
WSC-6(V)5 SHF
WSC-6(V)7 SHF
WSC-6(V)9 SHF
WSC-8(V) CWSP
INMARSAT B
INMARSAT B HSD
TV-DTS
Commercial
Wideband
Protected
Broadcast
HSD: High Speed Data
Figure 4-18. SATCOM Distribution by Ship Class
4.2 NON-SATCOM COMMUNICATIONS
4.2.1 High Frequency and Configuration
U.S. shipboard HF equipment currently covers the range of 14 kHz–30 MHz for receive and 2 MHz–30 MHz for
transmit. Many ships still have 20- to 30-year-old technology (e.g., AN/URT-23 radio, R-1051 receivers), but the
high frequency radio group (HFRG) has been rapidly replacing the older systems.
HF circuits are used for Link-11 and SFEM, and for coordination between allied and coalition forces. On some
ships, it can also serve as a long-haul backup for SATCOM and for receipt of high-speed fleet broadcast.
There are two primary configurations of legacy HF equipment currently in use onboard USN ships. The first
configuration utilizes narrowband transmitters (such as the AN/URT-23) and receivers (e.g., R-2368), in
conjunction with narrowband multicouplers (i.e., SRA-49, 56, 57, and 58), and narrowband couplers (i.e., URA38). The second consists of the HF broadband systems such as the AN/URC-131(V) HFRG. For both
configurations, baseband audio and digital interfaces are encrypted and then routed either directly to the radios or
via an external modem. The actual quantity of circuits will vary by ship class to fulfill the circuit requirements
and range from a minimum of 2 HF transmit and receive circuits to a maximum of 32 transmit and 49 receive
circuits.
The HFRG is a sophisticated radio system providing improvements in reliability, survivability, collocation, and
electromagnetic interference (EMI) performance. The system is a completely integrated, solid-state
communications suite, engineered to provide the ideal balance between transmitter and receiver performance in a
collocated shipboard environment. The system is designed ready to accept expansions and technology upgrades as
they become available. The HFRG receive system covers the frequency range from 0.014 to 30 MHz. The same
4-23
JAN 2005
NTTP 6-02
antenna can support as many as 49 circuits. The system operates without performance degradation, with a
frequency separation between transmit and receive as small as 5 percent. The sensitivity for reception is limited
only by atmospheric noise.
4.2.2 Very-High-Frequency and Ultrahigh-Frequency Line-of-Sight Communications
VHF and UHF LOS communications support ship-to-ship, ship-to-shore, and ship-to-air LOS communications.
Shipboard tactical VHF radios use the 30 to 88 MHz and 108 to 156 MHz segments of the VHF radio band for
ship-to-shore communications in amphibious operations and for land-mobile shore communications. A portion of
the VHF band (225 to 300 MHz) and the lower end of the UHF band (300 to 400 MHz) provide tactical ship-toship, ship-to-shore, and ship-to-aircraft radio nets. Havequick II and Link 4A also share the UHF spectrum.
4.2.2.1 Systems
VHF and UHF LOS communication systems use a variety of equipment. Only some equipment are transmitters
and receivers. The majority fit into a category called transceivers — a combination transmitter and receiver that is
generally compact, portable, and uses a single antenna. The following is a compilation of commonly used VHF
and UHF LOS equipment and systems and their uses.
1. AN/ARC-182 VHF/UHF radio — A multiband/multimode radio (30 to 400 MHz) used for close air
support, air traffic control, maritime radiotelephone, and NATO communications.
2. AN/GRT-21(V)3 VHF/UHF transmitter and AN/GRR-23(V)6 VHF/UHF receiver — Used for
transmitting and monitoring aircraft distress communications (116.0 to 151.975 MHz) in the VHF range
and for air traffic control (225.0 to 399.97 MHz) in the high VHF and low UHF range.
3. AN/URC-93 VHF/UHF LOS radio — The several configurations available (225 to 400 MHz) are for use
with voice, electronic counter-countermeasures (ECCM), LPI, data, and wideband communications.
4. AN/VRC-40 series VHF radio — Used aboard ship as well as in vehicles (30 to 76 MHz) to support shortrange, two-way VHF communications.
5. AN/WSC-3(V)6 UHF LOS radio — The standard Navy shipboard LOS UHF transceiver (225 to 400
MHz) used for voice, data, and teletype (TTY).
6. Havequick — A modification of several existing tactical UHF radios for use in providing ECCM
capability in the 225 to 400 MHz frequency range.
7. JTIDS — A high-capacity TDMA system that provides integrated communications, navigation, and IFF
capabilities. It provides ECCM capabilities for aircraft and surface ships, extended range of communications, and OTH communications for surface ships with an airborne relay platform. It is also designed to
accommodate secure voice and the digital information associated with Links 4A, 11, and 14.
8. Single-channel ground and airborne radio system (SINCGARS) — A frequency-hopping, frequencymodulating, spread-spectrum system (30 to 88 MHz) designed to provide SECVOX and data
communications in jamming environments.
4.2.2.2 VHF/UHF Communications System
The VHF/UHF communications system is used on amphibious ships to transmit and receive tactical, operational,
and administrative information (both voice and data) in the VHF range (30–300 MHz) and the UHF range (300
MHz–3 GHz). The VHF/UHF communications system primarily supports LOS communications between
accomplishing units. This VHF/UHF communications system is comprised of the following subsystems: bridgeto-bridge radio group, Prifly/HDC radio group, GRC-211 radio transceiver set, GRC-171 radio group, VRC-90
JAN 2005
4-24
NTTP 6-02
radio group, the DWTS, WSC-3 LOS radio group, and the Maritime Cellular Information Exchange Service
(MCIXS).
1. The bridge-to-bridge provides short-range, nonsecure, bridge-to-bridge voice communications in the VHF
range.
2. The Prifly/HDC radio group provides both Prifly and HDC personnel the capability to exchange tactical
operational information with ownship aircraft in the VHF/UHF range. This radio group is used primarily
as a backup in the event of a power failure to the normal communication systems.
3. The GRC-211 radio transceiver set provides for nonsecure, LOS, ship-to-ship, and ship-to-aircraft,
voice/radio-telephone communications in the VHF range.
4. The GRC-171 radio group provides for secure/nonsecure, line-of-sight, Link 4A/Link 11/locallycontrolled aircraft communications in the UHF range.
5. The VRC-90 radio group provides for secure/nonsecure, frequency hopping, ship-to-ship, and ship-toshore, radio-telephone communications in the VHF range.
6. The DWTS (future) provides for high capacity secure/nonsecure, LOS, ship-to-ship, and ship-to-shore,
digital voice/data/imagery communications in the UHF range.
7. The WSC-3 LOS radio group provides for secure/nonsecure, line-of-sight, voice/teletype/digital
communications in the UHF range; this radio group is also capable of providing for satellite
communications.
8. The MCIXS provides for a secure/nonsecure, nontactical independent radio path in the commercial UHF
cellular range, allowing intra-SG personnel to communicate using the ship’s dial telephone systems.
4.2.3 Digital Wideband Transmission System
DWTS is a high-bandwidth, full-duplex, LOS UHF communications system designed primarily to support the
USMC in intra-ESG distributed collaborative planning and ship-to-tactical shore network communications. It
provides up to 2,048 kbps of multiplexed data throughput within the amphibious ready groups and provides
interoperation with the USMC’s AN/MRC-142 radios to support TRITAC voice and IP data. Via its
interconnection to ADNS, it provides an alternate path for ship’s IP data to effectively extend broadband satellite
coverage to other ships within the ESG. Baseband systems supported by DWTS are the TSS for TRITACcompatible voice, and ADNS for all network IP traffic and tactical VTC. The system consists of two radio suites
on each ship that normally connect to each of the other two ships within the ESG, establishing a ring
configuration. Automatic relaying by the baseband systems provides redundant paths within the ring. When
interconnected to an MRC-142 ashore, the ring topology is broken and the closest ship connects to the Marine
radio, which then provides a nonredundant connection between all ships of the ESG and the shore.
4.2.4 Tactical Switching System
The TSS (AN/SSQ-122(V)1) program provides ancillary baseband enabler equipment for SHF SATCOM
terminals and UHF LOS wideband systems. It supports the exchange of tactical automated voice services between
afloat joint commanders, landing force command elements at Marine regiment or Marine expeditionary unit
(MEU) and higher, Army brigade and higher, and disembarked forces ashore. The TSS switched multiplex unit
(SMU-96) and ancillary equipment (including automatic key distribution center (AKDC/HGX-93) provides the
baseband switching for shipboard trunk interoperability with TRITAC equipment operated ashore, e.g., TRITAC
switches, mobile subscriber equipment (MSE), GMF equipment, and transparent interface to commercial
international networks. The TSS SMU interfaces include:
4-25
JAN 2005
NTTP 6-02
1. UHF LOS DWTS AN/SRC-57(V) for communications with USMC elements ashore and with non-SHF
SATCOM capable amphibious ships.
2. SHF SATCOM AN/WSC-6(V)5 (2nd channel) for GMF communications via teleport/step gateways
(LCC/LHA/LHD class ships).
The TSS is capable of handling a variety of TRITAC digital transmission groups (DTGs) (up to 4 standard DTGs
with data rates up to 1152 kbps).
4.2.5 Enhanced Position Location Reporting System — Data Radio
EPLRS-DR is a secure, spread-spectrum, frequency-hopping, UHF networking radio system. It provides digital
communications for the Amphibious Force command element at the regiment to company level with reachback to
the ESG. Via its connection to the ADNS, EPLRS-DR provides a 57.6 kbps digital IP data path between
command elements aboard ship and Marine networks ashore. Additionally, EPLRS provides the position location
information of each radio, which is used to track and identify unit movement within the operational area for SA.
The EPLRS-DR network is self-healing and provides automatic relaying up to six times for increased mobility
and range extension. The radio utilizes synchronous TDMA, frequency division multiple access (FDMA), and
code division multiple access technology, combined with embedded COMSEC for a secure, low probability of
intercept, low probability of jamming RF-network. EPLRS provides interoperability with the Marine Corps,
Army, and Air Force. Shipboard configurations will consist of one, three, and four radio suites depending on
platform size and mission. A radio suite consists of the RT-1720 radio, antenna, MUTE interface (for LHD class
ships), user readout unit, printer, EPLRS network manager (ENM) computer, power adapter, KOK-13 COMSEC
equipment, and various mounts and interface adapters.
4.2.6 Very Low Frequency
The Navy shore VLF/LF transmitter facilities transmit a 50 baud submarine C2 broadcast, which is the backbone
of the submarine broadcast system. The VLF/LF radio broadcast provides robustness (i.e., improved performance
in atmospheric noise), availability, and global coverage and has seawater penetrating properties. The submarine
VLF/LF broadcasts operate in a frequency range from 14 to 60 kHz and consist of six high-powered,
multichannel fixed VLF (FVLF) sites and seven multichannel LF sites located worldwide.
The submarine VLF/LF broadcasts are generated by the BCA or alternate BCA from messages created locally by
the C2 processor or the submarine/satellite information exchange system (SSIXS) processor, or accepted for relay
by the submarine operating authority (SUBOPAUTH). The BCAs and alternate BCAs are connected to the
transmitter sites by dedicated intersite links (ISLs) with the ability for the JCS and USSTRATCOM to seize
BCAs, at any time, for EAM dissemination. At each of the transmitter sites, messages received over the ISLs are
decrypted and input into the integrated submarine automated broadcast processor system (ISABPS). Submarine
VLF/LF broadcasts a continuous transmission sequence of prioritized messages that normally lasts two hours. It is
generated by ISABPS and sent to the VERDIN transmit terminal. The VERDIN transmit terminal is used to
multiplex, encrypt, encode, and modulate up to four 50 BPS submarine broadcast channels into VLF/LF radio
frequency signals that are amplified/radiated by the VLF/LF transmitter antenna.
4.2.7 Extremely Low Frequency
The Navy uses the ELF portion of the RF spectrum as a strategic communications asset in support of the
submarine broadcast system. ELF permits submarines to remain covert and acts as a “Bellringer” to notify the
submarine to come shallow to copy a higher data-rate broadcast. The ELF communications system consists of two
high-power shore transmitter stations controlled by a submarine BCA. The two ELF transmitter facilities are
located at Clam Lake, WI, and Republic, MI. This unique communication system is designed to transmit short
alerting messages to submarines operating far below the ocean surface. The ELF frequencies used, in the 40–80
Hz range, were selected for their long-range signal propagation (i.e., global) and ability to penetrate seawater to
depths several hundred feet below the surface. In addition to the inherent covertness this communication system
JAN 2005
4-26
NTTP 6-02
provides, it also provides the submarine commanding officer with operational flexibility to remain at required
mission depth and speed.
COMSUBLANT in Norfolk, VA, and COMSUBPAC in Pearl Harbor, HI, alternate as the ELF BCA. The BCA
injects messages generated by the SUBOPAUTHs into the ELF system via the C2 processor known as the
message entry operator terminal (MEOT). These messages are relayed to the transmit sites by dedicated
communication links, usually leased telephone lines, called ISLs. At each transmitter site, the messages received
over the ISLs are decrypted and input into the message processing element (MPE). The MPE develops the ELF
broadcast by encoding, queuing, and encrypting the messages to be transmitted. The transmit processor element
(TPE) produces the drive signals for the power amplifier and antenna. The two ELF transmitter facilities are
located at Clam Lake, WI, and Republic, MI.
4.3 ADVANCED TACTICAL DATA LINKS
4.3.1 Overview
The sharing of critical time-sensitive information has always been a key element of warfare, but ever-increasing
information exchange requirements have produced dramatic changes in how we fight wars today. The
development and use of radar, increased tactical communications, and the emergence of jet aircraft with improved
weapon systems all increased the magnitude of information required to be processed in the post–World War II
era. During the 1950s, significant efforts were made to address the emerging data exchange requirements resulting
in the development and fielding of the naval tactical data system (NTDS), Link 11, and Link 4.
Since the initial deployment of data links, their importance has increased with the exponential increase in data
required to be shared among platforms and their commanders. Instead of focusing exclusively on the exchange of
data derived from radar systems, today all forms of data are candidates for information exchange, including
mission planning data, order of battle data, platform/weapon system status, SA information, and even
imagery/photographic data. The continuous progression and expansion of information exchange requirements
lead to extremely complex yet capable tactical data systems that have become critical components of warfighting
and have ushered in the new paradigm of network-centric warfare.
4.3.2 Link 11
Fielded in the early 1960s, Link 11 is a secure TDL employing netted communication techniques and
standardized M-series message formats. It operates over HF and UHF frequencies and can also be transmitted
over a 25 KHz SATCOM channel. HF operation provides omnidirectional coverage to approximately 300 nm
while UHF is limited to LOS. The maximum transmission rate is 2.250 kbps with an effective data throughput of
1.800 kbps. A net control station (NCS) controls platform transmissions by interrogating each unit in a round
robin fashion and allowing each unit to reply with data when interrogated. Net cycle time is the time it takes the
NCS to make one complete interrogation cycle through all platforms. Air and surface tracks are updated every 12
seconds, but this can be impacted when net cycle time exceeds 12 seconds. Land tracks are reported less
frequently than air tracks. Tracks are reported in X, Y, and height coordinates relative to a system coordinate
center. The X and Y fields limit the distance that tracks can be reported to 512 miles from the system coordinate
center and at that scale the position resolution is 500 yards. The system coordinate center can be collocated with
the reporting unit’s position, or it can be a separate position defined by the reporting unit. System coordinate
centers are reported as delta latitude and delta longitude from a predefined data link reference point (DLRP). Link
11 is widely employed throughout the world and is installed in the Navy aboard surface platforms and submarines
(CV/CVN, CG, DD-963, DDG-51, FFG, LHA/LHD, LCC/AGF, LPD-17, SSN), air platforms (E-2C, EP-3, P-3,
S3), and at numerous ground sites.
The Navy anticipates phasing out Link 11 in favor of Link 22 by 2015. Figure 4-19 reflects the total number of
air, surface, and ground Link 11 systems installed on Navy platforms as documented in the joint TDL
management plan (JTDLMP), as well as a notional schedule for the phasing out of Link 11 by 2015.
4-27
JAN 2005
NTTP 6-02
400
Total Platforms
347
347
350
Notional
Phasing out
300
250
200
197
Surface
198
176
Air
Ground
150
104
100
50
25
25
13
0
0
FY02
FY05
FY10
FY15
Figure 4-19. USN Link 11 Systems
From the early 1960s through the mid 1990s, Link 11 was the primary TDL for the Navy. In addition to SA, Link 11
supported ASW and electronic warfare (EW) data exchange, force weapons control, engagement status reporting,
and to a limited degree platform status reporting. With the introduction of Link 16, Link 11 has taken a secondary
role in the Navy as a TDL. Link 16 provides all the functionality of Link 11, plus better resolution, higher
throughput, more detailed information, and an air control capability. Additionally, Link 16 can report tracks
anywhere on the earth, is non-nodal, and provides extensive AJ capability, but is limited to LOS unless relay is used.
HF Link 11 is used on occasion for beyond LOS communication but the primary use today for Link 11 is
communication with other legacy Link 11 systems and non Link 16 capable allied forces. Link 11B continues to be
employed by other services and connectivity to the Navy is accomplished through gateways that forward data
between Link 11 and Link 11B. The arrival of Link 22 will further reduce the need for Link 11, as it serves as a
functional replacement for Link 11 and incorporates many Link 16 features. The Link 22 message standard is
based on Link 16, with most messages either identical or almost identical to Link 16. Additionally, data
translation from Link 16 to Link 22 is far less complicated than the Link 11 to Link 16 translation. Current plans
are to integrate Link 22 into a multilink environment through the common data link management system
(CDLMS); however, early standalone implementations of Link 22 are also being investigated.
4.3.3 Link 4
Link 4 is a nonsecure TDL employing time division multiplexed (TDM) communication techniques and
standardized V-series and R-series message formats. The basic Link 4 waveform does not support an AJ
capability and has a maximum transmission rate of 5 kbps with an effective data throughput of 3.06 kbps. Initially
Link 4 was developed as a one-way air intercept control link providing basic track and vector data from a
controlling unit to a tactical aircraft. In the 1970s mission computer improvements in fighter aircraft led to the
development of Link 4A that provided a means for two-way air intercept control. This enhancement provided the
capability for controlled aircraft to downlink ownship position and status and basic target/track information to the
controlling unit. Although Link 4A included a two-way capability, it also maintained backward compatibility with
all one-way systems and as such completely replaced the basic Link 4. In the mid-1980s another variant, Link 4C,
was developed, which added a fighter-to-fighter capability. This variant allowed sharing of data between
controlled fighter aircraft and added limited AJ resistance. Link 4C is backward compatible with Link 4A, but
because the two waveforms differ, platforms can communicate on one variant or the other but not both
simultaneously. Link 4A is employed by the Navy and the USMC and is installed on all carrier-based fixed wing
aircraft (E-2C, F-14D, F/A-18 A/B, F/A-18 C/D, F/A-18 E/F, EA-6B, S-3, C2). It is also installed aboard surface
air control platforms (CV/CVN, CG, DDG-51, LHA/LHD) and at air control ground sites. Link 4C is installed
only on the F-14. Figure 4-20 reflects the number of air and surface Link 4 systems installed on Navy platforms.
JAN 2005
4-28
NTTP 6-02
1200
1012
927
Total Platforms
1000
755
800
713
Surface
600
Air
400
200
125
133
133
109
0
FY02
FY05
FY10
FY15
From the 1960s through the mid-1990s Link 4 was the primary air control data link in the Navy. With the
introduction of Link 16, Link 4 has taken a secondary role in the Navy as an air control data link. Link 16
provides a significantly more robust air control capability over Link 4 as well as providing interoperability with
other services and allied nations. The Navy desires to phase out Link 4A/C as an air control data link as soon as
possible but Link 4A/C terminals are dual purpose and also support the automatic carrier landing system (ACLS).
Since ACLS is a required capability for all carrier-based fixed-wing aircraft, the Link 4A/C terminals will not be
replaced until a suitable replacement for ACLS has been developed and approved. The joint precision approach
and landing system (JPALS) is under development and may serve as a replacement for ACLS. Although several
successful test flights of JPALS have been conducted, it is still in the research and development phase and it will
be some time before it is approved and certified. Additionally, roughly 200 F/A-18 A/B variants are planned to be
in service until at least 2010. Currently, the F/A-18 A/B is not scheduled to be backfitted with Link 16 Multifunctional Information Distribution System (MIDS) terminals and must rely on Link 4 for air control.
4.3.4 Link 16
Link 16 is a secure TDL employing TDMA communication techniques and standardized J-series message
formats. Developed as a follow-on and eventual replacement for Link 11, a primary goal was to eliminate many of
the shortcomings of Link 11. Link 16 is gaining extensive acceptance and employment throughout the world and
has been designated as DOD’s primary TDL for command, control, and intelligence. Link 16 is designed to be
non-nodal, meaning it does not require an NCS or grid reference unit (GRU) to operate within a tactical network
or “net.” This is important from a single point of failure perspective because loss of a “node,” such as the NCS or
GRU, renders a Link 11 net useless for some period of time until another unit within the net can assume those
functions. Link 16 does not require the assignment of a frequency and provides a simplified link set-up through
use of a JTIDS Network Library (JNL) initialization file. Link 16 supports improved joint interoperability and
provides significant technical and operational enhancements over Link 11 and Link 4 TDL capabilities, including:
1. Increased data rate (throughput)
2. Standardized identity reporting
3. Increased position reporting accuracy
4. Increased amounts and types of information that can be exchanged
5. Secure waveform
4-29
JAN 2005
NTTP 6-02
6. Embedded digitized secure voice capability
7. Embedded relative navigation capability with precise participant location and identification (PPLI)
8. Increased numbers of participants.
Link 16 operates over UHF frequencies (L band from 960–1215 MHz), which limits the range to LOS, but a builtin relay capability is supported. Significant AJ resistance is provided as well as a sophisticated error detection and
correction (EDAC) capability. The maximum transmission rate with full AJ and EDAC is 59.5 kbps with an
effective data throughput of 26.8 kbps. Data throughput of 107.5 kbps is attainable but with a sacrifice of some
anti-jam and EDAC capability. Timeslots are preassigned for transmission, which eliminates the need for an NCS.
Air and surface tracks are nominally updated once every 12 seconds. Land tracks are reported less frequently than
air tracks (nominally at 48 seconds). Tracks are reported in latitude, longitude, and height coordinates, which
allows for reporting of tracks anywhere on Earth. This approach eliminates the need for a system coordinate
center and the predefined DLRP. Most tracks can be reported with a position accuracy of roughly 30 feet and
reporting units can report ownship positions with an accuracy of roughly 6 feet. Link 16 with JTIDS is installed or
scheduled for installation aboard surface platforms (CV/CVN, CG, DDG-51, LHA/LHD, LCC/AGF, LPD-17), air
platforms (E-2C, F-14D, EP-3), and at ground sites. Link 16 with MIDS is scheduled for installation aboard
surface platforms (CV/CVN, DDG-51, LHA/LHD, LPD-17, CVX, DD(X)), air platforms (F/A-18 C/D, F/A-18
E/F, E/A-6B, E-2C, P-3, HH-60, MH-60), and at ground sites. Per various TDL and platform specific planning
documents, Figure 4-21 reflects the total number of air, surface, and ground Link 16 systems installed on Navy
platforms.
To date, the operational use of Link 16 has been predominantly in the surveillance, C2, and air-to-air/surface-toair engagement arenas. With the ability to employ Link 16 at the individual surface- and airborne-unit level has
come a significant improvement in SA and knowledge of the real-time operational environment. Successful
execution of combat operations in the current and emerging lethal battlespace environment requires seamless data
communications at the individual unit level. The jam-resistant, secure, LPI, and low probability of exploitation
(LPE) features of the Link 16 tactical network provide the required seamless interoperability among tactical units
and ensure the delivery of accurate, relevant, and timely information to individual units. With operators no longer
limited to a “single ship”–generated tactical picture, operational forces employing Link 16 have seen significant
improvements in combat effectiveness across the spectrum of operational functions including Blue Force tracking
and status, force and unit level C2, threat system ID and tracking, and engagement tasking, management, and
execution.
1163
Total Platforms
1163
Surface
693
Air
Ground
296
157
124
165
0
FY02
165
2
8
FY05
FY10
JAN 2005
4-30
8
FY15
NTTP 6-02
400
347
350
Notional
Phasing In
Total Platforms
300
250
Surface
200
Air
165
159
Ground
150
80
100
TBD
50
0
FY02
29
16
0
FY05
FY10
FY15
Figure 4-22. Planned Installation of Link 22 Systems
As the Navy embarks on transformation of operational forces from “stove-pipe” to “Network Centric,” Link 16
will be increasingly relied upon to provide the tactical network architecture solutions required to support this
transformation. Operational users will be provided access to the tactical network at the platform level through the
expanded installation of Link 16 terminals on individual units. As an example, with the installation and full
integration of Link 16 on the F/A 18, EA-6B, EP-3, and P-3 AIP, strike package participation on the network will
grow from the current 10 percent to over 95 percent.
4.3.5 Link 22
Link 22 is the emergent data link initiative developed under the multinational initiative known as the NATO
Improved Link 11 (NILE) program. This link is not an enhancement to Link 11 as is implied by the program title,
but an entirely new link that interfaces Navy units and NATO allied systems. The forwarding requirements
to/from Link 16 networks are simplified by the new F-series messages in the Link 22 message standard, which are
essentially comprised of J-series data elements. The multinational Link 22 development effort consisted of several
phases. The first phase completed the Link 22 system specification, the system network controller (SNC), and the
NILE reference system (NRS) segment specification and was called the NILE Project Definition Phase. Phase II
was composed of the software design and development for the SNC, which is the heart of Link 22, and the test
equipment “rig” called the NRS that was used to ensure that the completed SNC met the required specifications.
All of these documents are available to each NILE participating nation.
Link 22 is anticipated to serve as a replacement for Link 11, with a plan to phase out Link 11 systems by 2015.
Figure 4-22 is a notional schedule that reflects the projected number of air, surface, and ground Link 22 systems
planned for Navy platforms through 2015.
With the ongoing transformation of the Navy, the challenges of unit-level interoperability will remain as one of
the significant challenges that must be met. Experiences by operational forces in recent conflicts such as
Operations Allied Force, Desert Fox, Enduring Freedom, and Iraqi Freedom continue to highlight the necessity
for seamless integration of unit-level operations in the battlespace environment with allied/coalition forces. Much
of the data and information required to support joint service combat operations is also necessary to ensure
coordinated allied/coalition combat operations. As the joint services transition to network-centric operations
supported by TDL architectures, unit level interoperability with allied/coalition units will be supported through
the implementation and fielding of the Link 22 system. Employing Link 22, allied/coalition forces will be able to
participate in the development and utilization of the CTP and gain improved SA. Location and distribution of
4-31
JAN 2005
NTTP 6-02
primary “friendly” force elements will also be provided with resultant improvements in combat action
coordination and deconfliction.
4.3.6 Satellite Link 11
Early Satellite Link 11 was demonstrated in 1984 when the USS Saratoga (CV-60) transmitted one-way Link 11
over a 25 kHz Gapfiller SATCOM channel. The demonstration successfully provided the track picture of the
western Mediterranean to units of the Lebanon operations area in the eastern Mediterranean. Since that display
was achieved, the use of satellites in long-range Link 11 communications has significantly increased. Now that
Gapfiller SATCOM channels are no longer being used, the current configuration operates on a standard 25 kHz
SATCOM channel. The DTS is operated in mixed mode, which means data received over an audio interface is
retransmitted over a digital serial interface. This is accomplished by connecting the digital interface of the DTS to
a satellite-capable WSC-3 radio. Satellite Link 11 may be operated as either a one-way or two-way link.
4.3.7 Satellite Link 16
Satellite Link 16 is an element of the C2 program that was developed exclusively by the Navy to overcome the
Link 16 LOS range limitation using SATCOM instead of the conventional JTIDS relay currently being used by
organic airborne host platforms. The program began in 1994 with an investigation of the feasibility of developing
a satellite interface for the command and control processor (C2P) to operate JRE. This effort was in response to a
requirement to support up to 16 units in a network and meet a 20-second surveillance track update rate. The
requirement was also specified that there be a seamless and uninterrupted exchange of data between JTIDS/Link
16 and S-TDL J. Designed to provide a communications path for SGs beyond line of sight (BLOS) J-series
message exchange, Satellite Link 16 was a welcome addition to the Navy SG TDL architecture. Implementation
of this capability in the fleet has been conducted on an SG-by-SG basis.
4.3.8 Joint Range Extension Application Protocol
The joint range extension application protocol (JREAP) program is a means of providing the warfighter with a
capability of exchanging essential J-series messages BLOS without the use of a dedicated airborne relay. JREAP
is an answer to a growing problem where large combat theaters require large-scale Link 16 networks that
necessitate significant use of relay capabilities. The positioning of key airborne assets will be driven by
communications requirements, and this presents a suboptimal use of scarce combat resources. The airborne relay
function consumes valuable timeslot capacity, and some C2 centers may be out of range of airborne relays. The
JRE architecture will employ a mix of UHF, SHF, EHF SATCOM, and landline media. The long-term JRE goal
is to use EHF MDR SATCOM with a TDMA architecture to increase the data rate and provide access to more C2
platforms. The interim architecture will also remain, but will replace service-unique data exchange standards with
a joint standard for data exchange. Once JRE is fully implemented, it will supersede the Navy Satellite Link 16
and other service-unique range extension implementations.
The JRE and Satellite Link 16 programs addressed the requirement to pass secure/AJ data and voice via a
common means in a timely manner BLOS without the use of a dedicated airborne relay. These initiatives include
implementation of an EHF MDR SATCOM interface using the TIP, which is being developed for the AN/USC38 shipboard EHF SATCOM terminal and EHF SATCOM terminals of the other military services. The TIP
interface will allow multi-Link 16 SATCOM range extension among up to 256 surface and land platforms at a
rate of up to 1.536 Mbps (T1 rate). The current C2P interface allows a rate of 256 kbps, two to four times the data
rate of a typical LOS Link 16 network.
4.3.9 Cooperative Engagement Capability
CEC brings revolutionary new capability to naval air and missile defense, not by adding new radars or weapon
systems, but by distributing sensor and weapons data from existing systems in a new and significantly different
manner. CEC fuses high quality tracking data from participating sensors and distributes it to all other participants
in a filtered and combined state, using identical algorithms to create a single, common air defense tactical display
(“air picture”). The result is a superior air picture based on all sensor data available that permits significantly
JAN 2005
4-32
NTTP 6-02
earlier detection and more consistent tracking of air contacts. CEC was designed against the air threat (e.g., from
cruise missiles), especially in littoral waters. Undergirding CEC is a robust communications system with several
orders of magnitude in improvement to bandwidth and electronic countermeasures, as well as the systemic
advantages offered by the global positioning system (GPS).
CEC provides real-time integration of fire control quality sensor data into a single composite data source that can
be used by multiple CEC ships and airborne units for direct and remote missile engagements. CEC significantly
improves strike force (SF) antiair warfare (AAW) capability by coordinating all force AAW sensors into a single
real-time, fire control quality composite track picture. CEC, when integrated with AAW weapon systems in an SF
or SAG, results in a distributed AAW weapon system among participating cooperating units. Successful AAW in
an SF or SAG relies on coordinating and controlling AAW assets among AAW-capable ships. As threat
inventories increase and hostile countermeasures become more sophisticated, fleet AAW movements must
address individual ship AAW capabilities and coordinate the sensors and weapons of individual ships into a
cooperative SF- or SAG-distributed AAW system. Data sharing from primary AAW sensors of an SF provides
timely, accurate data ensuring greater engagement decision and prosecution responsiveness in case of battle
engagement. Coherent, high-quality sensor data and engagement status information shared among multiple ships
automates engagement decisions.
With CEC, data from each unit is distributed to all other units, filtered, and combined using identical algorithms
into a single, common air picture. Each CEC unit combines ownship radar measurement data with those from all
other CEC units using the same CEC algorithms. The result is an air picture based on all the data available (thus
superior to that of any single sensor), providing tracks with identical track numbers throughout the net.
CEC distributes radar measurement data (not tracks) from each CEC unit to all other CEC units. Units
communicate in pairs during short transmit/receive periods through a narrow directional signal. Data is thus sent
across the net in NRT and communication is virtually jam-proof. CEC units are able to engage on the basis of
CEC composite tracks, even when the firing unit does not hold the track, because CEC provides precision
gridlock and fire control quality tracks.
CEC improves warfighting capability in amphibious operations by enabling cooperating units to allocate radar
energy to different areas of the battlefield, enlarging the area of radar coverage. Naval operations conducted in the
littoral environment require that attacking aircraft and missiles be detected and engaged over land or over water in
the face of heavy land clutter. Search sector cooperation between the defending ships using CEC can significantly
increase their detection and track ranges and consequently increase battlespace.
Operating independently, without CEC, each of the ships must spread its radar energy over the entire volume,
limiting the time and energy available to search in the difficult land clutter region. Operating together with CEC, a
single ship can search the entire volume while the other ships concentrate on the land clutter region. Data from
each ship are distributed to all the ships and combined into an identical composite track picture on each ship. This
picture, superior to that available from any single sensor, allows significantly earlier detection and more
consistent track on attackers in the clutter.
Because CEC combines radar measurement data from all the ships, the CEC picture covers a larger geographic
area than that of any single sensor, providing greatly increased SA and opportunities for tactical coordination.
Contributions from CEC-equipped AEW aircraft will extend this coverage even further, providing surface units
more accurate tracking and SA at ranges well beyond shipboard sensor coverage. The airborne CEC also provides
for relay of the CEC air picture between widely separated surface units, maintaining connectivity and SA at
greatly extended ranges.
Radar measurement data from CEC air units also greatly increase coverage over land, where the altitude of the
airborne radar mitigates terrain masking and radar horizon limitations affecting shipboard radars. CEC provides
airborne radars the same improvements in track accuracy, track continuity, and ID consistency afforded shipboard
radars resulting in improved detection and tracking as well as greater SA.
4-33
JAN 2005
NTTP 6-02
Additionally, CEC contributes to theater ballistic missile defense by providing a continuous fire control quality
track on the missile from acquisition through splash. Although each ship is only able to maintain track for part of
the missile flight, the CEC composite track, based on all the data, is continuous. Cues based on the composite
track allow the downrange ships to detect the target earlier and to maintain track longer. The CEC cues and relay
of composite track data will allow defending ships maximum battlespace in which to engage theater ballistic
missiles when the SM-2 Block IVA missile becomes available.
4.3.10 Common Data Link–Navy
Common data link–Navy (CDL–N) shipboard terminal, AN/USQ-123(V), is a multifunction shipboard data link
terminal installed aboard aircraft carriers and LHA/LHD class ships to support reconnaissance and surveillance
missions. CDL–N is an automated communications node that acquires data-linked signals from airborne
reconnaissance vehicles (manned or unmanned) and distributes the received signals to the appropriate shipboard
intelligence user for processing/exploitation. CDL–N will support the Navy’s efforts by providing a wideband,
full-duplex, digital data communications link between the ship and the airborne sensor platform equipped with the
common data link–airborne (CDL–A/B) subsystem.
CDL–N provides full duplex data communications (at LOS ranges) between aircraft, equipped with a CDL–A/B,
and shipboard users’ signal processing equipment. The terminal receives variable data rates with an encryption
and decryption capability in accordance with the interface specifications of the supported systems. The CDL–N
transmits user commands to the CDL–A/B for SG passive horizon extension system (SGPHES) or JSIPS–N
Advanced Tactical Airborne Reconnaissance System (ATARS) prime mission equipment (PME) in the aircraft.
CDL–N receives link status and user mission data in the downlink and provides this mission data to the SGPHESST and JSIPS–N shipboard processors. The command uplink has LPI characteristics based upon parabolic
antenna directivity, signal modulation format, and transmitter power output control. The system is capable of
operating only one link at a time.
1. CDL–N characteristics include:
a. Full duplex, X/Ku-band data link
b. 200 kbps uplink
c. 10.71, 137, or 274 Mbps downlink
d. Full 360° coverage with two antennas
e. CDL standard — interoperable with Army/Air Force payloads.
2. The CDL family has five classes of links:
a. Class I — ground-based applications with airborne platforms operating at speeds Mach 2.3 at an
altitude up to 80,000 ft.
b. Class II — speeds up to Mach 5 and altitudes up to 150,000 ft.
c. Class III — speeds up to Mach 5 and altitudes up to 500,000 ft.
d. Class IV — terminals in satellites orbiting at 750 nm.
e. Class V — terminals in relay satellites operating at greater altitudes. All Navy shipboard CDL–N
terminals use Class I links.
JAN 2005
4-34
NTTP 6-02
4.3.11 SRQ-4 Hawklink
The SRQ-4 Hawklink is a C-band, LOS datalink that provides automatic information flow between Navy surface
combatants (CG-47, DDG-51, DD-963, and FFG-7 class ships) and SH-60B LAMPS III helicopters. This
information includes voice, digital, video, and sensor data. The Hawklink operates in two control modes: ship
control mode and helo control mode. In ship control mode, the ship controls the Hawklink. While in helo control
mode, the aircraft controls the Hawklink. Regardless of the control mode, the downlinked information consists of
voice, video, sensor data, and system status information. Uplink information consists of voice and system control
commands. The Hawklink functions in two operating modes — ASW and antiship surveillance and targeting
(ASST) — that are independent of the control modes. The designation of ASW or ASST specifies the sensor data
that is downlinked from the helicopter to the ship. In ASST mode radar, FLIR, IFF, and electronic warfare
support (ES) sensor data are downlinked to the ship. In ASW mode, acoustic and ES sensor information is
downlinked.
4.4 COMMAND AND CONTROL SYSTEMS
4.4.1 Global Command and Control System-Maritime
GCCS-M is the maritime implementation of the joint services GCCS providing a single, integrated, scalable C4I
system. The system supplies information that aids Navy commanders in a full range of tactical decisions. In
functional terms, GCCS-M fuses, correlates, filters, and maintains raw data and displays image-building
information as a tactical picture. Specifically, the system displays the location of air, sea, and land units anywhere
in the world and identifies whether those units represent friendly, neutral, or enemy forces. It operates in NRT and
constantly updates unit positions and other SA data. GCCS-M also records the data in appropriate databases and
maintains a history of the changes to those records. The user can then use the data individually or in concert with
other data to construct relevant tactical pictures, using maps, charts, map overlays, topography, oceanographic,
meteorological, imagery, and all-source intelligence information all coordinated into what is known as a CTP that
can be shared. Supplied with this information, Navy commanders can review and evaluate the general tactical
situation, determine and plan actions and operations, direct forces, synchronize tactical operations, and integrate
force maneuver with firepower. The system operates in a variety of environments and supports joint, coalition,
and allied forces.
The GCCS-M architecture is composed of three variants: GCCS-M afloat, GCCS-M ashore, and GCCS-M
tactical/mobile that includes TSCs, mobile operations control center (MOCC), and joint mobile ashore support
terminal (JMAST).
4.4.1.1 GCCS-M Afloat
The GCCS-M afloat variant C4I system is installed on all ships, submarines, and at certain shore sites. It provides
the afloat tactical commander with a timely, authoritative, fused CTP with integrated intelligence services and
databases. The GCCS-M afloat variant disseminates intelligence and surveillance data in support of warfare
mission planning, execution, and assessment.
4.4.1.2 GCCS-M Ashore
The GCCS-M ashore variant provides a single integrated C4I system that receives, processes, displays, maintains,
and assesses the unit characteristics, employment scheduling, material condition, combat readiness, warfighting
capabilities, positional information, and disposition of own and allied forces. It allows decision makers to optimize
the allocation of resources. GCCS-M ashore provides current geolocational information on hostile and neutral land,
sea, and air forces integrated with intelligence and environmental information, and NRT weapons targeting data to
submarines as part of the shore targeting terminal (STT) replacement effort. GCCS-M ashore supports real-time
tasking of MPA assets in conjunction with force high level terminal (FHLT) replacement efforts.
4-35
JAN 2005
NTTP 6-02
4.4.1.3 GCCS-M Tactical/Mobile
The GCCS-M tactical/mobile program provides evolutionary systems and ancillary equipment upgrades to
support the unified, fleet, and Navy component commanders, the maritime sector, theater, and the naval liaison
element commanders (ashore) with the capability to plan, direct, and control the tactical operations of joint and
naval expeditionary forces and other assigned units within their respective AOR. These operations include littoral,
open ocean, and over land all-sensor (i.e., EO, IR, ISAR, etc.) surveillance, antisurface warfare, over-the-horizon
targeting (OTHT), counterdrug operations, power projection, ASW, mining, search and rescue, and special
operations. The C2 services provided include core GCCS-M capabilities, analysis, and correlation of diverse
sensor information, data management support, command decisions aids, access to rapid data communication,
mission planning and evaluation, dissemination of ocean surveillance positional data, and threat alerts to
operational users ashore and afloat.
4.4.1.4 Tactical Support Center
The TSC is a node of the GCCS-M incorporating communications and warfighter and aircraft interface support
functions. TSCs are located at maritime patrol and reconnaissance aircraft (MPRA) homeports and principal
deployment sites, providing maritime sector commanders with C4I3SRT capability to plan, direct, and control
tactical maritime air forces in support of MPRA missions within the assigned AOR. The TSC design provides for
a permanent, reliable C4I3SRT support system from air facilities dedicated to MPRA operations during peacetime
contingencies and full wartime mobilization. During mission planning, TSC personnel provide aircrews with
OPCON information and support, coordination, and integration of MPRA assets during SF-direct support
operations. In maintaining a COP, the TSC prevents prosecution of friendly units by keeping the aircrews up-todate with requisite information to perform their mission effectively. The TSC includes various sensor data
analysis tools to obtain data produced during flight. The data collected from missions is capable of being inserted
into formatted and unformatted messages or shared through other electronic means as required.
Core components include three primary enclaves:
1. Communications, which includes various HF, UHF, VHF, and SHF LOS and BLOS radios and voice and
data communications assets supporting GCCS-M, SIPRNET, and DCCS/NAVMACS II messaging.
2. Warfighter interface support consisting of maritime resource management, flight planning, mission brief,
tactical data insertion, flight following, tactical mission extraction, and mission debrief/reporting
capabilities.
3. Aircraft interface support, which includes sensor analysis, voice and data link communications, and unique
aircraft support software.
The core components of TSC are identical among all sites, with minor differences in floor plan layout.
4.4.1.5 Mobile Operations Control Center
The MOCC is a node of the GCCS-M incorporating mobility, facilities, communications, and warfighter and
aircraft interface support functions. The MOCC provides nearly all the TSC capabilities within modular, mission
configurable, and self-contained components. MOCCs are designed to be rapidly deployable and capable of
supporting MPRA operations in nontraditional areas that are not equipped with the stable communications,
advanced sensor analysis, and C4I3SRT functions of the fixed site TSC. Due to the mission configurable design,
specific mission requirements determine which MOCC hardware is needed for any particular deployment.
Core components include five primary enclaves:
1. Mobility is ensured by the design of individual MOCC hardware components to fit through a P-3/MMA
aircraft main cabin door, meet P-3/MMA floor loading requirements, and be two-man portable.
JAN 2005
4-36
NTTP 6-02
2. Facilities support element provides the physical support infrastructure including generators and power
distribution.
3. Communications includes various HF, UHF, VHF, and SHF LOS and BLOS radios and voice and data
communications assets supporting GCCS-M, SIPRNET, and DCCS/NAVMACS II messaging.
4. Warfighter interface support consisting of maritime resource management, flight planning, mission brief,
tactical data insertion, flight following, tactical mission extraction, and mission debrief/reporting
capabilities.
5. Aircraft interface support includes sensor analysis, voice and data link communications, and unique
aircraft support software.
The core components of MOCC are identical among all units.
4.4.1.6 Joint Mobile Ashore Support Terminal
JMAST is a node of the GCCS-M incorporating mobility, facilities, communications, and warfighter interface
support functions. JMAST is equivalent to a unit level with shared data server (i.e., cruiser with intelligence
server), and can support the naval component commander ashore during initial deployment. JMAST supports the
operational readiness of fleet and force commanders, JTF commanders, deployed components, and other military
commanders from forward deployed bases or operational sites that are not equipped with C4I3SRT facilities.
JMAST provides commanders the mobile ability to command, control, and communicate with assigned forces
through voice, video, and data media forms during all aspects of military operations, including joint, combined,
and coalition operations. JMAST provides quick response in support of theater contingencies worldwide. JMAST
(with the exception of fuel) is completely self-contained, with a modular design for power; heating, ventilation,
and air conditioning (HVAC); communications; and computer resources. The modular design permits deploying
only those system components required for mission support.
Core components include four primary enclaves:
1. Mobility is constrained by airlift transportation requirements, which for JMAST can be supported by C130 or higher capability aircraft. Subsystems are integrated into two-man lift containers that are configured
for standalone operations or integration into complete systems.
2. JMAST facilities support element provides the physical support infrastructure including generators, power
distribution, HVAC, and deployable rapid assembly shelters (DRASH).
4. Warfighter interface support provides supported commands with an underlying C4I3SRT infrastructure of
communications, data systems, and facilities equivalent to the tools that would be available on a large
combatant or command ship, from which commanders and staffs can conduct their assigned deployed
missions.
4.4.1.7 Reserve Mobile Ashore Support Terminal
Reserve mobile ashore support terminal (RMAST) is a node of the GCCS-M incorporating mobility, facilities,
communications, and warfighter interface support functions. RMAST is a comprehensive C4I suite that provides
tactical C2 capabilities in support of naval port/harbor control, amphibious operations, or theater joint operations.
RMAST can also support the naval component commander ashore during initial deployment. RMAST is a rapidly
deployable C4I mission system to support naval coastal warfare missions, usually deployed in conjunction with
mobile inshore undersea warfare (MIUW) units. RMAST supports military commanders and operational
readiness from forward deployed bases to operational sites that are not equipped with C4I facilities. RMAST
4-37
JAN 2005
NTTP 6-02
provides commanders the mobile ability to command, control, and communicate with assigned forces through
voice, video, and data media forms during all aspects of military operations, including joint, combined, and
coalition operations. RMAST provides the Commander, Navy Coastal Warfare Groups 1 and 2 with the tools
necessary to support a Commander, Navy Forces (COMNAVFOR) detachment ashore with the capability to
maintain timely and effective communications with naval forces at sea.
Core components include four primary enclaves:
1. Mobility is constrained by airlift transportation requirements, which for RMAST can be supported by C130 or higher capability aircraft. Subsystems are integrated into two-man lift containers that are configured
for standalone operations or integration into complete systems.
2. RMAST facilities support element provides the physical support infrastructure including generators, power
distribution, HVAC, DRASH, and general purpose (GP) shelters.
4. Warfighter interface support provides supported commands with an underlying C4I infrastructure of
communications, data systems, and facilities for ashore commanders to display a tactical situation as it
develops ashore and at sea, allowing the commander to fully integrate and interact with afloat commanders
in an operational environment.
4.4.2 Mine Warfare and Environmental Decision Aids Library
MEDAL provides the MIW-unique functionality to the GCCS-M.
The mine countermeasures segment (MCMSEG) is a Commander, Mine Warfare Command
(COMINEWARCOM)–approved segment and was the first in a series of MIW applications, followed by mining
planning and mainstream MIW segments. Together with EOD planning tools, these segments comprise the
MEDAL. MEDAL is the single, approved tactical decision aid for MIW in the USN and has been operational
since 1996.
MEDAL provides the complete MIW portion of the CTP. MCMSEG supports surface and airborne MCM
(SMCM and AMCM) and EOD missions for dedicated and organic MCM operations, as well as expeditionary
and SG integrated operations. It can be deployed at varying levels of command (unit level up to task force level)
wherever MCM operations are required. Integrated NATO and allied operations are also supported.
1. The MCMSEG provides the planning, evaluation, situation assessment, and asset management tools for
conducting MCM operations. This segment makes full use of environment, threat, and route survey data to
support MCM operations, and integrates models and algorithms to determine optimum minehunting and
minesweeping strategies and employment of forces assigned. MCMSEG also provides for exchange of
MCM information among the MCM commander, tasked units, command authorities, coalition forces, and
other relevant units. MCMSEG provides MCM planning and evaluation functions and MIW reference
databases. The MCM planning and evaluation tool provides MCM area, contact, and asset management,
plot display controls and filters, and planning and evaluation tools — including risk calculations,
communications, and system functions. The MIW reference databases provide environment, mine threat,
assets, imagery, and route survey data for the installed application segments (and other GCCS-M segments
as appropriate). The environment database contains mine and littoral warfare specific METOC parameters,
including bathymetry, bottom characteristics, bottom features, water currents, physical properties,
atmospherics, plus MIW magnetic and acoustic data. It allows for the storage, display, and exchange of
historical and onscene (in-situ) collected data. The environment data is used for overall tactical
assessments by the MCM commander, as well as for inputs to the system performance prediction models.
The threat database contains reference information on mine characteristics, such as size, shape, operating
depths, user and manufacturing countries, etc. The route survey database contains a historical reference of
JAN 2005
4-38
NTTP 6-02
all minelike contacts found in the operational area. MCMSEG also has the capability to display imagery of
mines and minelike contacts, and has electronic interfaces with most MCM sensor and combat systems.
2. MIW essentials, the mainstreaming MIW segment, provides the core MIW SA and some basic mine threat
self-protection tools to each deploying platform (ship and subsurface) in the Navy.
3. The mining segment (MINT) automates the minefield planning folders within the GCCS-M and MEDAL
framework.
Each segment runs independently, or as a set, on multiple networked workstations operating off a common sybase
relational database server. A typical installation includes a database segment at one workstation, and an
application segment wherever the capability is required (the application and database segments may be loaded on
a single workstation). Supplemental, classified segments with detailed planning parameters are available.
MEDAL communicates through standard GCCS-M links, including the SIPRNET, for automated message and
database exchanges, and follows all FORCEnet principles. The segment can be configured to support various
levels of user expertise and understanding. These include core, organic user, dedicated, command, and METOC.
4.4.3 Theater Battle Management Core Systems
Theater battle management core system (TBMCS) is a USAF program with joint interest. The USN implements a
subset of the TBMCS “force-level” applications aboard command ships (AGF/LCC), aircraft carriers (CVNs),
and large deck amphibious ships (LHA/LHD). Additionally TBMCS is incorporated into the area air defense
commander (AADC) program on selected CGs. TBMCS is also fielded at selected training sites and shore
commands (COMPACFLT HQ and NAVCENT HQ).
The operational mission of TBMCS is to provide computer-supported management of theater airborne assets in
peacetime, exercise, and wartime environments. TBMCS provides automated C2 and decision support tools to
improve the planning, preparation, and execution of joint air combat capabilities. The tools also provide C2
support for operations other than war, e.g., humanitarian, United Nations peacekeeping, etc. The system provides
full support to force-level and unit-level warfighters throughout all phases of military operations: readiness,
deployment, employment, sustainment, and reconstitution. TBMCS provides a wide range of support to the
organization, personnel, procedures, and equipment collectively known as the theater air control system (TACS).
At the force level, TBMCS supports the Air Force and Navy air operations centers (AOCs) and the Marine
tactical air command center (TACC).
TBMCS is the C2 system for the senior theater air commander, the joint force air component commander
(JFACC). It links various organizational levels of air command, control, and execution. TBMCS facilitates air
battle planning, intelligence operations, and execution functions for all theater air operations. TBMCS provides
tasking for all air assets in the AOR and provides the joint air tasking order (ATO), airspace control order (ACO),
and the air defense tactical operational data message (TACOPDAT). TBMCS is a modular system designed to
build up or scale down capabilities accommodating added or deleted information sources, operating units,
weapons available, participating services and allies, dispersal requirements, and intensity of operations.
TBMCS provides the JFACC with the means to plan, direct, and control all theater air operations in support of
command objectives and to coordinate with ground and maritime elements engaged in the same operation. The
system fully supports peacetime training and daily operations as well as timely reaction to contingencies. TBMCS
implements interoperability with other C4I systems.
TBMCS implementation on Navy ships consists of two distinct configurations: host and remote. The host
configuration consists of a server-client suite aboard command ships and aircraft carriers. Currently, LHAs and
LHDs are remotes consisting of one or two client machines that must be connected to a host suite via a VPN
within the SIPRNET. Host configurations include the databases and applications that support the planning and
execution processes for air operations. The remote configurations support the execution of air operations only.
4-39
JAN 2005
NTTP 6-02
TBMCS within the Navy is loaded on SIPRNET LANS. TBMCS is loaded on top of GCCS-M to make use of the
embedded infrastructure, applications, services, and COE provided by GCCS-M. Access to the applications is
made via pull-down menus and icons.
Some of the more commonly used TBMCS applications include the following:
1. Theater air planning (TAP)
2. Airspace deconfliction (AD)
3. ATO/ACO tool (AAT)
4. Execution management control (EMC)
5. Execution management reports (EM reports)
6. Execution management replanner (EMR)
7. Target and weaponeering module (TWM)
8. Joint Munitions Effectiveness Manual (JMEM)
9. TK talk
10. Message services.
4.4.4 Joint Operation Planning and Execution System
The JOPES, a component of the Global Command and Control System-Joint (GCCS-J), is the integrated, joint,
conventional C2 system used by the joint planning and execution community (JPEC) to conduct joint planning,
execution, and monitoring activities. JOPES supports senior-level decision makers and their staffs at the National
Command Authorities (NCA) level and throughout the JPEC. Combatant commanders use JOPES to determine
the best course of action (COA) to accomplish assigned tasks and direct the actions necessary to accomplish the
mission. JOPES is a system that includes people and procedures.
JOPES is not a single application; rather, it is a set of applications that can be used independently but interact with
a shared database. While by no means an exhaustive list, key application include:
1. Requirements, development, and analysis (RDA) — RDA allows planners to analyze and edit time-phased
force and deployment data (TPFDD). It can also provide a preliminary analysis of the transportation
feasibility of a COA.
2. GCCS status of resources and training system (GSORTS) — GSORTS provides information about the
status and location of registered units of U.S. military forces and other registered foreign or domestic
agencies or organizations.
3. Joint flow and analysis system for transportation (JFAST) — JFAST determines the transportation
feasibility of an operation plan (OPLAN) or COA, makes closure estimates, determines optimum
transportation modes, assesses attrition effects, identifies shortfalls, and determines gross lift capability.
4. Scheduling & movement (S&M) — S&M allows the user to review, update, schedule, and create
manifests of both transportation component command (TCC) carrier and organic movement data before
and during deployment. It provides the capability to review and analyze an extensive variety of source
requirements and scheduling and movement data.
JAN 2005
4-40
NTTP 6-02
5. Force Augmentation Planning and Execution System (FAPES) — FAPES furnishes planning information
for mobilizing forces, monitors mobilization, and displays data to the user.
6. Logistics sustainment analysis and feasibility estimator (LOGSAFE) — LOGSAFE estimates logistics
sustainment requirements of a proposed OPLAN for deliberate or crisis planning, evaluates overall
logistics feasibility of OPLANs and COAs, and furnishes sustainment data to transportation feasibility
analysis tools. It also generates CIN records for TPFDD.
7. Medical planning and execution system (MEPES) — MEPES assists the medical planner in quantifying
the impact of an OPLAN on the medical system. MEPES can define medical working files (MWF),
compute the medical requirements, and print an appropriate set of reports.
4.4.5 TOMAHAWK Command and Control
4.4.5.1 Theater Mission Planning Center
The Navy’s three shore-based CMSAs use the TMPC to plan the routing and flight profile for TLAM missions
from the first preplanned waypoint to the target. TMPC is configured in three segments: the TOMAHAWK
planning system (TPS), the digital imagery workstation suite (DIWS), and the mission distribution system. All
equipment is located in a SCIF because of the classification of data processed in the DIWS. The TPS, DIWS, and
mission distribution system all have standalone capabilities and can function independently should a system
failure occur to any of the segments. While the classified LAN is a critical interface between segments, the ability
to pass data via magnetic media provides a backup capability.
1. The TPS segment controls the work flow of the TMPC, prepares and maintains the planning databases,
generates TLAM missions in response to tasking, and performs detailed independent quality verification
checks (IQVCs) on selected missions.
2. The DIWS segment provides the image management and mensuration needed to exploit imagery in
support of the CMSA and afloat planning system (APS) mission. Specifically, DIWS generates imagerybased products to support TLAM route planning as tasked by the TPS. It provides automatic and
interactive exploitation of both monoscopic and stereoscopic imagery from a wide range of sensors. The
DIWS receives imagery from sources external to the CMSA and APS, screens and catalogs image support
data for the TPS, and manages the active imagery files used to accomplish a set of DIWS tasks. The DIWS
high-performance workstations permit the operators to display, measure, correlate, control, manipulate,
and enhance images. It includes functions for product collection and output and for graphics processing,
including viewing stereo displays on a single screen.
3. The mission distribution system serves as an external link between the TMPC and the operating forces,
providing command information and data on data transport devices to TWCS-equipped surface ships and
submarines. ATWCS vessels receive media via transfer tape or TOMAHAWK command information
distribution order tape. The mission distribution system also provides the capability to electronically add
mission data to deployed conventional TLAM mission databases, and provides accountability, C2, strike
support decision aids, and mission descriptive information to designated commanders.
4.4.5.2 Advanced TOMAHAWK Weapon Control System
The surface combatant’s ATWCS performs engagement planning, missile preparation, and launch control
functions for missiles executing TLAM missions assigned to the ship. Firing units equipped with ATWCS cannot
employ Block IV missiles, but they can use all Block II and Block III TOMAHAWK missiles variants. ATWCS
also supports SA functions for operators by incorporating surface track information from external sources like
Link 11 and GCCS-M.
4-41
JAN 2005
NTTP 6-02
The ATWCS was designed for TOMAHAWK Weapon System Baseline III and replaced the original TWCS with
COTS-based hardware and software. ATWCS incorporated an open-system architecture, eliminated standalone
desktop computers, and enhanced C2 through accelerated mission processing.
ATWCS enables shipboard operators to generate and maintain a non-real-time surface track database in a given
theater of operations, to coordinate strike activities both on ownship and with other firing units in an SG, to plan
TOMAHAWK engagements, and to initialize, prepare, and launch TOMAHAWK missiles.
4.4.6 Advanced Field Artillery Tactical Data System
AFATDS is a multiservice automated fire support C2 system. It provides the capabilities to process, analyze, and
exchange combat information within the AFATDS architecture and other C2 systems such as the Army Battle
Command System (ABCS), 6 MAGTF C4I 7 system, and NFCS. The system is also compatible with the C2
systems used by several NATO nations.
AFATDS is capable of managing field artillery cannons and rockets/missiles, mortars, NSFS, close air support,
and Army/Marine Corps aviation (helicopter) attack systems at echelons from Corps (Army)/MEF (Marine
Corps) to platoon level.
AFATDS automates the functions and tasks performed by agencies involved in fire support, i.e., fire planning,
tactical fire direction, and fire support coordination. It filters, screens, and processes requests for fire support and
prioritizes target engagements based on selected factors. These factors include the supported maneuver unit
commander’s targeting guidance and attack criteria for fire support, target characteristics, target value analysis,
weapon systems availability, weapon system capabilities, and JMEM data. AFATDS ensures that fire missions
comply with fire support coordination measures and unit zones of responsibility. It selects and generates an
engage/fire order to the optimum weapon system available to engage a target and, based upon target priority,
recommends the best attack method for the selected system.
AFATDS is being developed and fielded in a multiversion, phased approach. The A98 baseline, with incorporated
Marine Corps specific requirements, is currently fielded. The A99 baseline, which incorporates technical fire
direction for field artillery guns, rockets, and missiles, is currently being fielded. Additional baselines are planned
through FY05.
AFATDS, as part of the SACC automation program, is installed in all 12 of the LHD/LHA class amphibious
assault ships. It is planned for installation on the LPD-17 class ships.
4.4.7 Naval Fires Control System
The NFCS is a shipboard naval fires planning and coordination system designed to automate all shipboard firesupport battle management duties. NFCS will be installed aboard all surface combatants receiving 5-inch/62caliber gun installations. It provides an interface to AFATDS. NFCS provides the surface combatant a digital link
through various systems interfaces to the automated fires support network used by the maneuver forces ashore.
The introduction of NFCS reduces the number of personnel required to perform NSFS functions. The
configuration of NFCS and ATWCS/TTWCS further reduces the number of personnel by allocating NSFS
responsibilities to the strike watch team positions. NFCS also provides land attack SA by accessing and
presenting the tactical picture of the area of operations received from GCCS-M and AFATDS.
NFCS processes both digital and voice calls for fire from forward observers (FOs) and in the future will support
precision land attack weapons such as:
1. Extended range guided munition (ERGM) — A long range (up to 60 nm) rocket assisted, GPS-guided 5inch artillery round.
2. Land attack standard missile (LASM) — A missile designed to extend land attack operations out to 100 nm.
JAN 2005
4-42
NTTP 6-02
3. Tactical TOMAHAWK — A modification to the TOMAHAWK weapons system that introduces the
concept of onstation loitering as the weapon awaits assignment to target.
NFCS software validates the targets for this new generation of weapons and selects the correct number of rounds
based on target type and behavior. NFCS also deconflicts the various targets and safeguards against fratricidal
strikes against friendly forces. It also executes the fire missions via digital interfaces to gun and missile weapon
control systems. NFCS software supplies the following tools and functionality:
1. Fire plan construction, maintenance, execution, and dissemination
2. Digital/voice call-for-fire request displays
3. Tactical picture of the littoral battlespace
4. Coordination and deconfliction of fire missions
5. Target data and engagement commands for ERGM and LASM fire control systems
6. Platform and munitions monitoring.
Whether performing autonomous ship operations, managing multiple ship operations, or executing fires in support
of amphibious task force operations, NFCS provides warfighters with the capability to plan and execute fires
against preplanned targets ashore as well as stationary targets. It also enables them to respond to direct calls-forfire from organic and nonorganic sensors.
GCCS-M provides an interface for NFCS to receive certain data communications directly including ATO data and
air coordination order data. This information will be received by NFCS in the form of a USMTF message via
TCP/IP. GCCS-M will be set up to autoforward the ATO/air coordination messages to NFCS.
NFCS will be installed on Arleigh Burke class destroyers (DDG-51) and Ticonderoga class cruisers (CG-47)
beginning with the USS LASSEN (DDG-82), with subsequent installations on DDGs 79–107.
4.4.8 Navy Tactical Command Support System
Navy tactical command support system (NTCSS) provides an IT portfolio of software applications and requisite
hardware to perform the supply, maintenance, and administrative information management functions for ships,
submarines, Naval and Marine Corps aviation squadrons, and intermediate maintenance activities (afloat and
ashore). NTCSS is the primary system that enables management and assessment of unit material and personnel. It
enables efficient and cost-effective management of nontactical information resources through the use of
standardized hardware and software to meet the force readiness and sustainment requirements of the USN and
Marine Corps.
NTCSS provides a full range of application segments to satisfy readiness and logistics business needs of operating
forces:
1. Ship and submarine maintenance — Organizational maintenance management system–next generation
(OMMS–NG) is a full-featured maintenance and configuration management system for ship and
submarine organizational-level maintenance.
2. Aviation maintenance — Optimized intermediate maintenance activity (OIMA) automates intermediate
maintenance and configuration management on board aircraft carriers, amphibious assault ships, and Navy
and Marine Corps air stations.
3. Supply, inventory, and finance — Relational supply (RSupply) automates supply, inventory, and financial
management for our operating forces.
4-43
JAN 2005
NTTP 6-02
4. Manpower management — Relational administrative data management (R ADM) automates manpower
management functions such as personnel qualifications, watch bills, station assignments, lifeboats, awards,
and much more.
5. Easy access to technical data — The advanced technical information support system (ATIS) provides an
easily retrievable and comprehensive warehouse of shipboard technical data.
4.4.9 AN/KSQ-1 Amphibious Assault Direction System
The AN/KSQ-1 amphibious assault direction system provides the ESG with the capability to identify, track, and
communicate with AN/KSQ-1 equipped ships and assault craft from launch through recovery to support
operational maneuvers from the sea. When helicopter relay is available, it operates without restricting or reducing
capability when unit separation does not exceed 100 nm.
AN/KSQ-1 provides:
1. Accurate, NRT assault craft position and ID information
2. AN/KSQ-1 and EPLRS-equipped units’ ID and position
3. OTH operating ranges via airborne relay
4. Limited text message exchange among network members via digital data link
5. Cryptographic security
6. AJ and LPI operation.
4.4.10 Meteorological and Oceanography Systems
METOC support is an important element of SG C2 (more of a factor in planning and execution), encompassing
such elements as:
1. Sonar detection and counterdetection range predictions in support of ASW and MIW
2. Electromagnetic propagation predictions:
a. Radar detection and counterdetection range prediction in support of air defense and antisurface warfare
b. Radio-wave predictions in support of communications planning
c. Sensor range predictions in support of strike warfare
(1) Electro-optical
(2) Electro-magnetic.
3. Cloud cover, hazards to air-navigation, and en route flight weather forecasts in support of flight operations
4. Surf conditions and tide predictions in support of expeditionary warfare.
4.4.10.1 Architecture
Navy METOC support is organized into three levels:
JAN 2005
4-44
NTTP 6-02
1. Global production centers that provide numerical analysis and prediction and historical data archiving:
a. Fleet Numerical Meteorology and Oceanography Center (FNMOC), Monterey, CA
b. Naval Oceanographic Office (NAVOCEANO), Stennis Space Center, MS.
2. Regional centers and facilities that provide tailored METOC support to all naval forces within their
assigned AOR, using products from global production centers in addition to locally produced products,
global observations, analysis, and prediction:
a. Naval Pacific Meteorology and Oceanography Center (NPMOC), San Diego, CA
b. Naval Pacific Meteorology and Oceanography Center (NPMOC), Yokosuka, Japan
c. Naval Atlantic Meteorology and Oceanography Center (NLMOC), Norfolk, VA
d. Naval European Meteorology and Oceanography Center (NEMOC), Rota, Spain
e. Naval Central Meteorology and Oceanography Center (NCMOC), Bahrain
f. NPMOC/Joint Typhoon Warning Center (JTWC), Pearl Harbor, HI.
3. SG METOC personnel assigned as ships company to carriers, large-deck amphibious ships, and command
ships. They provide tailored METOC support to the SG commander, embarked air wings, and SG ships,
using products from global production centers and regional METOC centers and facilities in addition to
locally produced products, observations, analysis, and prediction.
4.4.10.2 Shipboard Meteorological and Oceanography Systems
4.4.10.2.1 Navy Integrated Tactical Environmental System 2002
The Navy Integrated Tactical Environmental System (NITES) 2002 is a software suite of METOC applications,
services, and data servers that are used for both oceanographic and meteorological forecasting, weapon system
performance prediction, and sensor detection/counterdetection capabilities. It receives data from atmospheric and
oceanographic remote sensing satellites, the global production centers in Monterey and the Stennis Space Center,
regional METOC centers, world meteorological organization offices, civilian reporting broadcasts, local
observations, and databases. NITES can be used to produce detailed meteorological and oceanographic data
displays (e.g., wind speed/direction, air pressures, sea-state) along with the effects of these physical
environmental parameters on military operations.
NITES 2002 is located on board all USN capital ships, including carriers, large-deck amphibious ships, and
command ships.
4.4.10.2.2 METOC Satellite Receiver Processor (AN/SMQ-11)
The AN/SMQ-11 is a standalone environmental satellite ground receiver. The SMQ-11 is capable of receiving
raw imagery data in the visible, IR, and water vapor wavelengths from both the military Defense Meteorological
Satellite Program (DMSP) and the NOAA TIROS polar orbiting satellites. Additionally, satellite pictures and a
limited selection of weather charts can be received from the GOES satellites on the WEFAX channel. It is
digitally interfaced to the NITES 2002.
4.4.10.2.3 Shipboard Meteorological and Oceanographic Observing System
The Shipboard Meteorological and Oceanographic Observing System (SMOOS) is a suite of environmental
sensors that is designed to provide continuous automated measurement of meteorological and oceanographic
4-45
JAN 2005
NTTP 6-02
parameters. The sensors automatically send the data to NITES 2002, where it is processed, error-checked,
displayed, and distributed. The observer may supplement or override data from the automatic sensors. SMOOS
will input data from shipboard wind speed and direction transmitters and from the following sensors:
1. Atmospheric pressure sensor
2. Temperature/dew-point sensor
3. Cloud height detector
4. Visibility sensor
5. Precipitation sensor
6. Seawater temperature sensor.
4.5 INTELLIGENCE AND CRYPTOLOGIC SYSTEMS
4.5.1 Joint Services Imagery Processing System–Navy
The JSIPS-N is a shipboard digital imagery system with the capability to receive, process, exploit, store, and
disseminate imagery products and imagery-derived intelligence reports based upon multisource imagery from
national and tactical sensors. The primary purpose of JSIPS-N is to increase the self-sufficiency afloat of tactical
aviators and strike, naval fire support, and expeditionary force planners in the precision delivery of ordnance. The
system is installed in intelligence and mission planning spaces onboard aircraft carriers and amphibious assault
ships (LHA/LHD), as well as at three shore sites. JSIPS-N provides afloat national imagery reception, ground
station for tactical reconnaissance and unmanned aerial vehicles, and intelligence exploitation. Segments of
JSIPS-N are also installed on fleet flag ships (LCC/AGF) and in rapid deployment suites (RDSs) deployed as part
of unified commands (USJFCOM and USCOMPAC) for the TOMAHAWK APS.
System design is based on the integration and upgrade of functional capabilities in three primary components.
These include the digital imagery workstation suite afloat (DIWSA), which is a shared resource with the APS, the
tactical input segment (TIS), which is a modification of one segment of the USAF-led JSIPS program, and the
NIS, which is procured through the Defense Dissemination Program Office (DDPO). The DIWSA and the
precision targeting workstation (PTW) provide soft-copy exploitation segment (SES) functionality to enable
targeting of precision-guided munitions (PGM). In addition, JSIPS-N electronically interfaces with the GCCS-M,
JDISS, and the common high-bandwidth data link-shipboard terminal (CHBDL-ST).
Major JSIPS-N components include the DIWSA, PTW, strike planning archive (SPA), national input segment
dissemination element (NISDE), and TIS.
1. DIWSA is the “high end” system that is capable of extensive soft copy image processing, exploitation, and
mensuration. It is also capable of digitizing small amounts of hardcopy imagery for the same purposes.
2. PTW is the “low end” soft copy exploitation system that supports tactical air (TACAIR) mission planning
evolutions through imagery exploitation capabilities where precise coordinates are not required,
perspective scene imagery file generation, DIWSA image product manipulation, and electronic target
folder production.
3. SPA is a standards-based bridge that allows wide user access to JSIPS-N products and services while
isolating tactical users from JSIPS-N hardware/software requirements and the SCI security environment.
4. NISDE serves as a communications interface and processor system to receive NRT imagery from national
sources. Due to the nature of data it processes, the NISDE must operate at, and be located in shipboard
intelligence and mission planning spaces classified at the TS/SCI level.
JAN 2005
4-46
NTTP 6-02
5. TIS incorporates a common imagery processor (CIP) as the primary sensor processing element. The CIP is
a multisensor processor capable of accepting raw imagery and auxiliary support data necessary for
exploitation from existing communications links and magnetic media, formatting the data into exploitable
imagery, and transferring this information to other segments of JSIPS-N in common data formats.
4.5.2 Global Command and Control System-Integrated Intelligence and Imagery
Global Command and Control System-Integrated Intelligence and Imagery (GCCS-I3) provides COP-centric
imagery and intelligence-related capabilities developed by the four military services and selected agencies in
response to joint warfighter requirements. Through the GCCS-I3 integration process, these tools provide
intelligence support to operations seamlessly within the GCCS family of systems.
GCCS-I3 enhances the operational commander’s situation awareness by providing a standard set of integrated,
linked tools and services that give ready access to imagery and intelligence directly from the operational display.
GCCS-I3 gives tactical operators and intelligence analysts direct access to the nationally produced modernized
integrated database (MIDB) for order of battle (OOB) data, weapons systems characteristics and performance
information, and national imagery. GCCS-I3 also gives those users the capability to integrate locally collected
tactical imagery, live video stream, and other intelligence with national and theater-produced intelligence. This
intelligence can be plotted directly on operational/tactical displays alongside continuously updating operational
and operational-intelligence information, providing tactical operators and intelligence analysts vastly improved
knowledge of the tactical battlespace. The all-source fusion capabilities of GCCS-I3 provide decision makers with
a composite picture of the battlespace augmented with SCI-level intelligence, bringing together NRT track, OOB,
maps and imagery, military overlays, and other forms of specialized intelligence data to produce a CIP. When
combined with other enabling technologies, such as database replication and guards, GCCS-I3 supplies
geographically focused, OPINTEL to the GCCS-M CTP battlespace view, aiding decision support and improved
SA for the intelligence and operations elements of the commander’s staff.
Included in the GCCS-I3 suite are the following applications:
1. Joint threat analysis tools/ground template toolkit (JTAT/GTT) generates terrain suitability and other
tactical decision aids based on military aspects of terrain and contributes to intelligence preparation of the
battlespace (IPB) analysis. It supports the joint force and component commanders’ campaign/mission
planning and decisionmaking by identifying, assessing, and estimating the adversary’s battlespace center
of gravity, critical vulnerabilities, capabilities, limitations, intentions, most likely COA, and COA most
dangerous to friendly forces.
2. Joint targeting toolbox (JTT) provides a common standardized, scalable, and DII-COE compliant set of
targeting tools to manage and/or produce targets, target data, and target-derived products and services in
response to customer requirements in a manner consistent with targeting mission objectives and warfighter
requirements.
3. Improved many-on-many (IMOM) models electronic combat scenarios and can provide threat evaluation.
It is a 2-D graphics oriented user-interactive program which aids in mission planning and IPB analysis.
IMOM visually displays the complex interaction of multiple ground-based radar systems being acted upon
by multiple airborne ECM aircraft. IMOM models the detection capabilities of radar effects, the effects of
stand-off jamming platforms, and the effects of self-protection jamming platforms. The model adds the
effects of terrain masking and ECM on any OOB, exploits the results to perform a variety of analyses, and
provides hard copy post processing in a variety of formats.
4.5.3 Cryptologic Unified Build
The cryptologic unified build (CUB) is a collection of software segments that address common functional
requirements across the naval cryptologic community. CUB is a centralized “clearinghouse” for cryptologic
system applications providing a commonality of design, look, and feel. The segments run within the framework of
the GCCS-M. The CUB approach is to provide a shared library of DII COE compliant reusable software segments
4-47
JAN 2005
NTTP 6-02
to assist the tactical cryptologic operator. It is designed to be the common functional backbone supporting
COBLU, CCOP, SGPHES, CDF, and SSEE systems.
4.5.4 Joint Deployable Intelligence Support System
The JDISS program provides a family of hardware and software capabilities that allow connectivity and
interoperability with intelligence systems supporting forces, in garrison, and deployed during peace, crisis, and
war. It provides the joint intelligence center (JIC), JTF, and operational commanders with onsite automation
support and the connectivity necessary to execute the intelligence mission. The JDISS and the JWICS comprise
the joint standard and foundation for commonality among intelligence support systems. JDISS provides joint
intelligence centers, JTFs, and operational commanders with onsite automation support and the connectivity to
make the best use of the intelligence community’s resources. JDISS is also the technical baseline for the DODIIS
client-server environment.
JDISS provides automated support for the following:
1. Transmitting and receiving specific requests for intelligence
2. Accessing theater, service, and national intelligence databases
3. Supporting digitized imagery exchange
4. Accessing automated record message processing systems, I&W systems, and collection management
systems
5. Inputting intelligence data into a variety of operations/intelligence systems
6. Performing multimedia functions, such as voice electronic publishing and video teleconferencing.
The core software for JDISS is:
1. E-mail/chat
2. Word processing/message generator
3. Imagery manipulation
4. Communications interfaces/map graphics
5. Briefing tools/utilities
6. Desktop video/voice.
JDISS is not an intelligence system, it’s an intelligence support system. It has no intelligence database and no
strictly intelligence applications.
4.5.5 Tactical Exploitation System–Navy
Tactical exploitation system–Navy (TES-N) is the Navy shipboard implementation of the Army tactical
exploitation system (TES-A). TES-N is presently installed only on PAC Fleet CVNs. It is an integrated, scalable,
multi-intelligence system specifically designed for rapid correlation of national and theater ISR information to
support network-centric operations. TES-N provides the warfighting commander with access to NRT,
multisource, and continuously updated day/night battlespace ISR information. TES-N supports strike operations
using numerous ISR collection planning, data correlation, geolocation, data dissemination, and storage functions.
JAN 2005
4-48
NTTP 6-02
It is interoperable with other service derivatives of the TES system: TES-A, the Marine Corps’ tactical
exploitation group (TEG), and the Air Force’s ISR manager.
4.5.6 Integrated Broadcast System
IBS has integrated several existing intelligence and information dissemination systems into a single system of
broadcasts that will allow for the receipt of data via a single receiver (the joint tactical terminal). IBS will
disseminate threat avoidance, targeting, maneuvers, force protection, target tracking, and target/situation
awareness information, and will be continuously refined by data from national, theater, and tactical sensors. The
reported information will contain unique references (e.g., report or track/event number) to allow IBS producers
and users to correlate IBS products. IBS will allow the tactical user to construct successively detailed intelligence
pictures of the battlespace. IBS will interface with TDLs such as Link 16 and joint variable message formats
(VMFs) networks to ensure a seamless flow of intelligence information onto those networks.
The IBS architecture will be theater-based dissemination with global connectivity through terrestrial and highcapacity communications paths. IBS will take advantage of the communications paths users already have by
implementing an information management scheme integrated with other DOD information management systems
(e.g., GBS information dissemination manager).
The effective dissemination of NRT intelligence data requires secure, worldwide data communications with
prioritized use of available bandwidth between producers and users at all echelons of command. The existing
components of the IBS are:
1. Simplex (IBS-S) — Formerly known as the TRAP data dissemination system (TDDS)
2. Interactive (IBS-I) — Formerly known as the tactical information broadcast service (TIBS)
3. Network (IBS-N) — Formerly known as the NRT dissemination (NRTD) system
4. LOS (IBS-LOS) — Formerly known as the tactical reconnaissance intelligence exchange system (TRIXS).
Additionally, the TADIXS-B is currently part of the overall IBS network but will not migrate into the final IBS
architecture. The legacy intelligence dissemination systems were developed to support the operational
requirements of specific groups of users. They each provide a portion of the total operational requirements
necessary for an effective intelligence data dissemination architecture that supports the warfighter. IBS will
migrate (combine) these legacy systems into a new system that has theater-focused dissemination architecture,
with global connectivity, and uses a common information transfer language (standardized message formats). For
the USN, the strategy for the implementation of IBS will be known as the maritime integrated broadcast system
(MIBS).
4.5.6.1 IBS-Simplex
IBS-S supports the continuous rapid delivery of national systems and other vital, time-critical data, via UHF
SATCOM broadcast, to operational users deployed worldwide. IBS-S dissemination currently has four channels
available on each of three classified host satellites and one channel on each of four MILSATCOM satellites to
provide redundant worldwide coverage. Each of the four geographic combatant commands are responsible for the
Simplex broadcast requirements within their AOR.
IBS-S Components
1. MILSATCOM — A system of MILSATCOM that carries the IBS-S broadcast to users worldwide.
Includes FLTSATs and UFO satellites and will include the MUOS satellites when deployed.
2. MILSATCOM uplink site (MUS) — Facilities used to provide the broadcast to the communications
satellites.
4-49
JAN 2005
NTTP 6-02
3. P5 — A communications package on each of two classified host satellites that together with P8 (see
below) provides 4 UHF channels of IBS-S broadcast to users worldwide.
4. P8 — A communications package on the GeoLite satellite that together with the P5 communications
packages provides 4 UHF channels of IBS-S broadcast to users worldwide.
5. Terrestrial communications network (TCN) — The component that provides connectivity between sites
via direct, independent communication links.
6. Network management center (NMC) — The component that functions as a communications hub, receiving
and relaying data throughout the broadcast via the TCN. The NMC also monitors the operational status of
the entire broadcast.
4.5.6.2 IBS-Interactive
IBS-Interactive (IBS-I) is designed to allow theater producers to provide NRT data to IBS users and an interactive
exchange among data providers (producers). Four master/relay stations (one each in CONUS, Europe, the Pacific
and Southwest Asia) comprise the worldwide IBS-I broadcast architecture. Each master supports a theaterfocused broadcast network. Currently, each theater network can support 10 simultaneous producers, 4 highpriority talkers, 50 active query subscribers, and an unlimited number of receive-only terminals.
IBS-I Components
1. Net master — During operations, the IBS-I master processor is responsible for handling all network
protocol, and for automatically maintaining the continuity of the network.
2. Net manager — The net manager processor is responsible for maintaining the data flow to accommodate
all producers’ information. The net manager function allows the operator to change bandwidth allocations
and enable or disable query capabilities for terminals. The network manager and master functions are
normally on the same node; however, they can reside on different geographically separated nodes.
3. UHF MILSATCOM — IBS-I uses UHF MILSATCOM as a communications pathway and normally uses
UFO satellites. It is possible for IBS-I to use other UHF SATCOM systems or terrestrial LOS pathways.
4. Master/relays — Four master/relay stations that comprise the worldwide architecture support the
interactive broadcast.
a. CONUS — The IBS Support Office, Ft. Meade, MD. Worldwide IBS-I manager, master, and manager
for the CONUS net. Serves as the relay between the CONUS, PAC, and EUR nets, and maintains net
discipline among users, producers, and relays.
b. EUR — Vogelweh AB, Germany. Master and manager for the EUR and SWA nets. Ensures the relay
of information between the EUR and Southwest Asia nets and maintains net discipline among users.
c. PAC — Hickam AFB, HI. Master and manager of the PAC net and the alternate master for the CONUS
net. Ensures the relay of information between the EUR and Southwest Asia nets and maintains net
discipline among users.
d. Southwest Asia — Kadena AB, Japan. Master and manager of the Southwest Asia network. Vogelweh
AB currently serves as master for the Southwest Asia net.
JAN 2005
4-50
NTTP 6-02
4.5.6.3 IBS-Network
IBS-Network (IBS-N) consolidates data from the IBS-S and IBS-I broadcasts and other sources, sanitizes the
information to the appropriate user classification level (if necessary), and provides the data over network clientserver systems. The data disseminated via IBS-N falls into the following categories:
1. National systems data
2. Theater/tactical systems data.
The data is broken down into various data streams, access to which can be controlled from the IBS-N servers
(radiant ether (RE), global network initiative (GNI), and NRTD). RE provides data carried on TDDS/TADIXS-B
and TIBS to Navy, Air Force, and Army users via the SIPRNET without an organic capability to receive the overthe-air broadcasts. Data tailored to specific user requirements is delivered over a narrow bandwidth (~3 kb)
SIPRNET feed. GNI provides data from TDDS/TADIXS-B, TIBS, and NRTD over SIPRNET. GNI users have
the capability to customize data filters and to translate the data to one of the numerous available output formats.
NRTD will be used to provide data to, and receive data from, the collaborating nations (Australia, Canada, New
Zealand, and United Kingdom). NRTD will also be used to disseminate/receive SCI-level data.
IBS-N Architecture Components
1. COCOM/national SCI IBS-N server
2. COCOM/national SECRET IBS-N servers
3. NSA IBS-N server
4. Secure TCP/IP computer network (i.e., JWICS, NSANET, and SIPRNET).
4.5.6.4 IBS Line-of-Sight
IBS-LOS is the NRT dissemination portion of the TRIXS, used to disseminate data primarily from the guardrail
common sensor (GRCS). The Air Force distributed common ground system (DCGS) can use the U-2
reconnaissance aircraft equipped with the TRIXS radio relay system (RRS) to disseminate data to the LOS
producers and users. The GRCS integrated processing facility (IPF) is also an authorized producer on the IBS-I
and IBS-S broadcasts.
4.5.6.5 Receivers/Controllers
The systems listed below are normally found in the fleet today and have been designed to handle and process
incoming “raw” ISR data. The Navy is replacing all legacy tactical terminals with the joint tactical terminal.
4.5.6.5.1 Joint Tactical Terminal
The joint tactical terminal is part of a new family of tactical terminals that can be provided in multiple
configurations to meet various user requirements in support of the IBS. The terminal is designed to handle all of
the IBS formats and is scheduled to transition to the common message format (CMF) and new IBS waveform
when required. The terminal ranges from a minimum configuration consisting of eight receive channels and one
transmit channel, up to a maximum configuration of twelve receive channels and four transmit channels. JTT will
support the use of different portions of the RF spectrum as well as support for DAMA in 5 and 25 kHz SATCOM
channels and general purpose links (GPL) in both LOS and SATCOM modes of operation. Joint tactical terminals
can be found on CVNs, CGs, and DDGs.
4-51
JAN 2005
NTTP 6-02
4.5.6.5.2 Commander’s Tactical Terminal
This equipment is designed for service in a tactical, sheltered, military environment aboard ships, helicopters, jet
and propeller-driven aircraft, wheeled and tracked vehicles, and fixed sites. The commander’s tactical terminal
(CTT) has embedded crypto, message processing and filtering, and multiple input/output capabilities and can
interface with a wide variety of TDPs. It is capable of processing TADIXS-B, IBS-S, and IBS-I. While this is a
joint system, the Navy has a modified version of CTT known as CTT-N. It uses a versa module Eurocard (VME)
card (also known as VME tactical receive equipment (VTRE)) to accept the TDIMF output of the CTT (H3 or
HR). This TDIMF output stream is replicated to provide six independent outputs, each of which can be filtered
according to user inputs. This data stream can then be reformatted into over-the-horizon Gold (OTG),
SENSOREP, TABULAR, or TACELINT format depending on user needs. CTT-N/VTRE can be used with either
the AN/USQ-141 or AN/USQ-143 (CTT receivers). CTT is a legacy receiver that will be phased out as the joint
tactical terminal is fielded.
4.5.6.5.3 Tactical Receive Equipment
Tactical receive equipment (TRE) receives, demodulates, decodes, decrypts, processes, and distributes TDDS
data. There are seven versions of TRE: AN/USQ-101(V)3 USN surface ship TRE; AN/USQ-101(V)4 USN
submarine TRE; AN/USQ-101(V)6 USN shore TRE; AN/USQ-101(V)5 USMC team transportable TRE;
AN/USQ-101(V)1 USA TRE; AN/USQ-101(V)2 single-channel USAF TRE; and AN/USQ-101(V)7 dualchannel USAF TRE. Each of the configurations output the contact reports to tactical data processors (TDPs),
display terminals, or other systems. TRE equipment is no longer available and most equipment suites are in the
process of being replaced. It is considered a “legacy” receiver. The joint tactical terminal has been designated as
the transition receiver of choice.
4.5.6.5.4 Standard Tactical Receive Equipment Display
The standard tactical receive equipment display/display and control system (STRED/DACS) is a tactical display
commonly used as an I&W display or an SA tool. Its primary purpose is as a tactical receiver controller to control
(i.e., filter incoming IBS-S information) a TRE suite, multimission advanced tactical terminal (MATT), or VTRE.
STRED can be found in numerous spaces onboard ships. On CVNs, STRED is commonly found in supplementary
plots (SUPPLOTs), tactical flag command centers (TFCCs), aircraft carrier intelligence centers (CVICs), combat
decision centers (CDCs), ship’s signals exploitation spaces (SSESs), and the EW module. On other afloat platforms,
it is normally found in cryptologic spaces, intelligence spaces, and combat and EW spaces. Normally, only one
STRED terminal will operate the DACS portion of the system. STRED is currently managed and funded by the
NRO. It is scheduled to be replaced when the joint tactical terminal architecture is fully implemented.
4.5.6.5.5 Multimission Advanced Tactical Terminal
MATT is in use in airborne platforms (Navy=EA6B/P3(AIP)) and in support of special operations forces. It is an
UHF multichannel receiver capable of processing TADIXS-B, IBS-S, and IBS-I. It includes embedded crypto,
message processing, filtering, and report correlation.
4.5.6.5.6 TIBS Integrated Processor and Online Fusion Function
TIBS Integrated Processor and Online Fusion Function (also known as TNT (TIPOFF for NT)) is software that
turns a basic PC workstation into an IBS-I operator terminal, and normally functions in conjunction with a TIBS
interface unit (TIU). It allows for participation in the IBS-I intelligence link as a consumer and as an injector of
remote producers’ data. It can control the IBS-I data-link equipment and provides data translation for several
formats so that data may be broadcast on the network or disseminated to other sites. It can also operate as a
standalone I&W/SA TDP. TIPOFF was designed to operate on a Windows NT platform. Onboard Navy ships,
TIPOFF is normally found in either SUPPLOT, TFCC, or combat spaces. At USAF commands, it is normally
found in communications-related spaces. TNT is currently the principal software used to control the IBS-I
broadcast and related equipment.
JAN 2005
4-52
NTTP 6-02
4.5.6.6 Tactical Data Processors
There are currently numerous TDPs available to the operator/analyst. Below are a few of the more common TDPs
in use today.
4.5.6.6.1 Global Command and Control System-Maritime
See Paragraph 4.4.1.
4.5.6.6.2 TOMAHAWK Weapons Control System/Advanced TOMAHAWK Weapons Control System
TWCS is currently being replaced by ATWCS. ATWCS enables shipboard operators to generate and maintain a
surface track database in a given area, to coordinate strike activities both on ownship and between other ships in
the SG, to plan TOMAHAWK engagements, and to initialize and launch TOMAHAWK missiles.
ATWCS currently has a single serial port dedicated for receipt of broadcast data, but can also receive data via a
GFCP connection from other ports. ATWCS maintains its own tactical picture that can be shared with other THawk ships for battle coordination, and ATWCS is networked with GCCS-M and can be configured for the
sharing of data. Additionally, ATWCS can transmit data via OTCIXS. ATWCS is based on a suite of HP TAC-III
or TAC-IV computers.
4.5.6.6.3 Generic Area Limitation Environment–Lite
The generic area limitation environment (GALE)–Lite (GL) application is an electronic intelligence (ELINT)
analysis tool used to perform in-depth analysis of electronic signals of interest. Onboard CVNs, it is normally
found in either CVIC or SUPPLOT (and sometimes SSES). On large deck amphibs, it can be found in the JIC,
XPLOT, or even SSES. Ashore, GL can normally be found on analytical watch floors and combat support centers.
The system supports a large database allowing storage of numerous contacts of interest for later historical analysis
and comparison. Additionally, it provides multiple, automatic, multisource correlators/trackers for real-time
monitoring of incoming data.
4.5.7 Surface Tactical Cryptologic Systems
4.5.7.1 Classic OUTBOARD AN/SSQ-108(V)/Cooperative OUTBOARD Logistics Update
Classic organizational unit tactical baseline operational area radio detection (OUTBOARD) countermeasures
exploitation system is a USN shipboard direction-finding system. OUTBOARD provides EW signals acquisition
and direction-finding systems (AN/SRS-1) with the capability to detect, locate, and identify hostile targets at
long- range, and input this information into the ship’s tactical data system. This widely deployed system consists
of the SSQ-108 OUTBOARD VHF Adcock direction-finding antenna as well as 24 small deck-edge antennas for
LF/MF-HF band direction finding.
The OUTBOARD system is ineffective against elements of the current/projected threat environment that includes
counternarcotics operations. Its equipment is old and becoming expensive to maintain. An OUTBOARD logistic
update program was established to correct these deficiencies. It replaces outdated equipment, establishes a
common logistic support baseline, upgrades the subsystem direction finder to increase throughput speed, upgrades
direction finder on sky-wave signals, and modernizes the subsystems. A joint cooperative program between the
United States and the United Kingdom provides upgrades to the existing OUTBOARD system (AN/SSQ-108) to
provide comprehensive surface tactical capability to the 21st century. The program will make maximum use of
already developed military and commercial signal exploitation equipment. The systems architecture will require
minimal effort to implement future technologies necessary to handle the evolving threat.
4-53
JAN 2005
NTTP 6-02
4.5.7.2 Combat Direction Finding AN/SRS-1A(V)
The Navy’s combat direction-finding (CDF) system is an automated long-range hostile target signal acquisition
and direction finding system that can detect, locate, categorize, and archive data into the ship’s tactical data
system. CDF greatly improves on existing OUTBOARD system technology by providing greater flexibility
against a wider range of threat signals and increased reliability at lower cost through use of COTS workstations.
The CDF Block 0 (AN/SRS-1) electronic support, signal acquisition, and direction finding system provides
warship commanders NRT I&W, SA, and cueing information for targeting systems.
The operator interface CSCI provides the operator with the ability to analyze and control the system, dynamically
tune local receivers to frequencies of interest, control the CDF TACINTEL terminal, view system data
management and signal-parameter-type displays, and monitor overall system status.
The CDF Block 1 system (AN/SRS-1A(V)) is comprised of two major subsystems: AN/SRS-1(V) or CDF Block
0 and the automated digital acquisition subsystem (ADAS). The AN/SRS-1(V) is the basic shipboard direction
finding architecture that features an improved, more robust HFDF deck-edge antenna array, a mast-mounted
VHF-UHF antenna, narrowband signals exploitation, architecture that facilitates LAN connectivity, and sky-wave
capability. The ADAS features full digital “front-end stare” parallel architecture, programmable exotic signal
recognizer, wideband signals exploitation, and mixed mode DF, as well as the ability to integrate new signal
recognition algorithms.
Block 1 is now in full-rate production and is being installed on Wasp (LHD-1) and Arleigh Burke Flight II (DDG72 and follow-on) class ships. Block 1 systems are also being installed as back-fits on in-service LHDs and DDG51s. The Block 1 system will eventually outfit seven LHDs, 35 DDG-51 Flight IIs, and three shore sites.
4.5.7.3 Ship’s Signals Exploitation Equipment
The ship’s signals exploitation equipment Phase 2 program is a signals exploitation system that allows the
operators to monitor and analyze signals of interest within the SSES aboard a variety of ship classes. It evolved
from the AN/SSQ-80 local monitoring subsystem (LMS) and the TRUMP system that provided the system with a
basic cryptologic analysis. SSEE will integrate the tactical SIGINT technology adaptive recognizer (TSTAR) and
the narrowband acquisition subsystem (NAS) from the CDF system. A phased approach to procuring the SSEE
system has led to three existing baseline systems and two planned systems increments. Over 35 systems have
been procured and installed on surface combatants and at shore sites. SSEE is using the same hardware and
software as cryptologic carry-on program’s (CCOP) advanced cryptologic carry-on exploitation system (ACCES),
and some common hardware and software with PRIVATEER, a SOCOM program.
4.5.7.4 Strike Group Passive Horizon System
The SGPHES AN/ULQ-20 extends the SG’s LOS radio horizon by allowing operators on board USN surface
vessels to control U-2 SIGINT sensors and exploit the data in NRT. Intercepted signals of interest are sent via the
CDL to the surface terminal (SGPHES-ST).
4.5.7.5 Transportable Radio Direction Finding
Transportable radio direction finding (T-RDF) provides DF capabilities to SSEE-equipped ships. The single
V/UHF and six HF antennas are permanently installed on SSEE-equipped ships. There are fewer operational or
below-decks systems, which are cross-decked to ships just prior to their deployments. The below-decks rack is
permanently installed; the equipment is what gets cross-decked.
4.5.7.6 Hostile-Forces Integrated Targeting Subsystem
A tactical precision geolocation capability for Navy units that produces actionable intelligence on target emitters
through the timely correlation of location with intent. As part of the CCOP, the hostile-forces integrated targeting
JAN 2005
4-54
NTTP 6-02
subsystem (HITS) utilizes an evolutionary acquisition process to deliver needed capability improvements to the
fleet early and often.
4.6 SHIPBOARD NETWORKS
4.6.1 C4I Afloat Networks
C4I afloat networks (C4IAN) is the Navy’s program to design and install shipboard LANs to support mission
critical warfighting, manpower, and logistics systems. C4IAN supports the warfighter’s mission to exchange
tactical and tactical support information, internal to the ship, between warfighting units/elements and embarked
staffs and units.
The C4IAN program will eventually consolidate the following:
1. ISNS
2. SCI networks
3. CENTRIXS
4. NATO initial data transfer system (NIDTS)
5. Afloat workstation procurement and software licensing
6. VIXS
7. IXS
8. Naval global directory service (NGDS).
C4IAN, along with transport systems such as ADNS, extends DISN, SIPRNET and NIPRNET, and JWICS
services, as well as allied, coalition, and NATO enclaves and other terrestrial WAN connectivity, to afloat units.
C4IAN consolidates all shipboard information processing and sharing infrastructure requirements into a single,
fully integrated core infrastructure. C4IAN provides a secure environment for sharing information and knowledge
to enable interactive collaboration, improved information access, database replication, remote support, rapid
transfer and dissemination of communications, internal distribution, efficiency improvement, increased learning,
productivity improvement, and improved quality of life.
Features of C4IAN include:
1. Automated information service/system that leverages open standards and applicable commercial standards
interfaces
2. An open architecture, COTS and GOTS IT infrastructure hardware devices, as well as COTS and GOTS
software applications
3. Secure data separation for each security level (GENSER, SCI, allied/coalition).
4.6.2 Sensitive Compartmented Information Networks
SCI networks (formerly SCI ADNS) provide multimedia delivery of tactical, administrative, and intelligence
information to ships at sea and provide ships access to shore cryptologic and intelligence resources. SCI networks
are based on the integration of COTS/GOTS protocols, processors, and routers and provide network services such
as secure e-mail, chat, websites, and file transfer.
4-55
JAN 2005
NTTP 6-02
The implementation of SCI networks will enable existing communications/network programs to migrate away
from stovepiped IXS protocols with their associated communications paths toward a single network with voice,
video, and data transmission based on the TCP/IP protocol.
Depending on individual ship configuration, SCI networks use DSCS SHF, CWSP, UHF DAMA, EHF
LDR/MDR, and Inmarsat-B HSD RF satellite connectivity through a single ADNS point of entry. Since the
ADNS network operates at the GENSER SECRET level, SCI data is in-line encrypted to allow transport over the
ADNS backbone using Motorola network encryption system (NES) devices. NES is capable of providing data
confidentiality and integrity and peer identification and authentication, as well as mandatory/discretionary access
control services. IP tunneling via the SIPRNET is used by SCI networks to reduce stovepipe connectivity,
simplifies NES and network administration, and provides for secure alternate routing via standard ADNS
connectivity.
Compartmented traffic, other than SI, is routed by SCI-ADNS to BORDERGUARD equipment and a separate
computer workstation in SSES for use by appropriately cleared personnel.
4.6.3 Automated Digital Network System
The ADNS is the WAN gateway for all IP communications between afloat and ashore units.
ADNS is a system of commercial and government-developed hardware and software components that allows
ship-to-shore IP communications using existing commercial and MILSATCOM, LOS radio systems, and pier
connectivity when in port. ADNS provides this capability by utilizing a standard routing architecture that
interconnects all ADNS-equipped units in a particular theater of operations. ADNS is the node between the
shipboard LANs and the baseband infrastructure on ships and is the node between the fleet router and the ADNS
infrastructure on shore.
ADNS provides seamless and secure connectivity for voice, video, and data applications afloat and pier side
through automated network and RF resource management (Navy, coalition, and joint). ADNS program
requirements include:
1. Multimedia delivery of tactical/admin/intel information
2. Increasing information transfer efficiency through network bandwidth management
3. Joint interoperability
4. IP connectivity for UNCLAS, SECRET, and SCI LANs
5. Utilizing RF assets and pier connectivity
6. Providing support for applications:
a. E-mail
b. Web services (NIPRNET, SIPRNET, JWICS, CENTRIXS)
c. FTP services
d. VTC
e. Tactical messaging
f. DMS.
JAN 2005
4-56
NTTP 6-02
An ADNS has two functional elements: network management performed by the ADNS integrated network
manager (INM) and routing and switching (R&S) performed by the router and software. The associated crypto
(NES or TACLANE) provides separation of the information classification levels.
There are four ADNS shore sites configured for surface ship connectivity, each of which consists of multiple
ADNS shore nodes. NCTAMS PAC has five nodes; NCTAMS LANT, five nodes; NCTAMS EURCENT, four
nodes; and NCTS Bahrain, four nodes. There are a total of 18 ADNS nodes worldwide. NCTAMS PAC will be
the first of the four ADNS shore sites to receive a Cisco router-based configuration that is designed to support
future communications requirements.
There are four ADNS shore sites configured for submarine connectivity. Each site contains a BCA node
architecture (PAC, LANT, COMSUBGRU-8 in EURCENT, and COMSUBGRU-7 in the Far East) that provides
dedicated support to the submarine community.
ADNS supports multiple SG/ESG operations simultaneously in each respective AOR. In the current architecture,
each SG/ESG is assigned its own AS, and, as such, has a dedicated ADNS node assigned to support operations.
Under the Router Replacement Program, the current Proteon-based architecture is being replaced with a Cisco
router-based architecture that will convert the current SG/ESG “Node” architecture to one utilizing “frequency”
routing.
4.6.4 Radiant Mercury
Radiant Mercury is a hardware and software application that automatically sanitizes and downgrades formatted data
from SCI to GENSER. It is also used to sanitize data from U.S.-Only to Releasable for sharing with allied and coalition
partners.
It only sanitizes formatted (OTG family, USMTF family, tabular, TDMIF, NITF, etc.) data. Message transliteration
provides interoperability with other systems by allowing one format to come in and multiple different formats with
the same data to go out (see Figure 4-23). The headers of NITF imagery files are formatted extensively, and Radiant
Mercury is able to perform all of its capabilities on the header. Radiant Mercury cannot examine the image itself, so
classified objects in the image pixels will pass through a Radiant Mercury screening untouched.
Radiant Mercury capabilities include:
1. Automating sanitization and guarding from higher to lower classifications
Multiple Input
Security Levels
1
2
Multiple Input
Sources
3
4
5
6
Multiple Output
Security Levels
Top Secret/SCI
Format A
JTF
Top Secret/SCI
Format B
Top Secret/SCI
Format C
Secret
Secret
Format A
Secret Rel NATO
Format D
Exercise
Units
Addressees
Secret
Format B
Secret
Format C
Radiant
Mercury
NATO
Units
Supports Total of 32 Serial Input/Output Channels
Supports Maximum of 10 Physical Network Connections
Figure 4-23. Radiant Mercury
4-57
JAN 2005
NTTP 6-02
2. Downgrading to lower classification levels
3. Providing message format transliteration
4. Facilitating releasability to allies
5. Providing communications port guard (low to high)
6. Providing mechanism for data field integrity
7. Providing mechanism for selected data field checking
8. Providing a complete audit record
9. Supporting postevent reconstruction
10. Providing dirty word searches on full text or specific fields.
4.7 COLLABORATIVE TOOLS
4.7.1 Collaboration at Sea
CAS is the Navy’s global collaborative network, using the SIPRNET as its communications path. Providing chat
rooms and standardized SG websites, the fundamental concept behind CAS is that users access a standardized
strike group website that resides on servers aboard every ship in the SG. Each ship’s web server is synchronized
with the other ships in the SG and with a shore-based master web server through a database replication scheme.
Because shipboard users access a local web server, limited bandwidth is not used to support off-ship web
browsing to the CAS SG site. Complementing these web servers are shore- and several shipboard-based chat
servers that provide chat rooms and whiteboard capabilities. To accomplish this, CAS uses Lotus Sametime web
server software with the Sametime chat client.
NETWARCOM centrally manages CAS, with shipboard server administration and web development by CAS
support teams located ashore. The shore component of CAS consists of four central CAS servers located at the
theater NOCs of NCTAMS LANT, NCTAMS PAC, NCTAMS EURCENT, and NCTS Bahrain. All SG websites
are located on these servers.
These central servers are synchronized through a replication scheme whereby changes to any website are
replicated every 15 minutes to the others. Any shore-based user with access to the SIPRNET and a web browser
can access any SG’s CAS website by going to one of these four central CAS servers.
Ships update their web servers through their SIPRNET connectivity to the closest NOC. Replication is done
hourly but can be more frequent if the operational situation requires. Due to server size and bandwidth limitations,
ships receive only the website of their assigned SG. CAS has implemented selective replication allowing low
bandwidth units to replicate only the large files requested vice all documents. If a shipboard user wants to access
another SG’s website, they must browse off the ship to the NOC. Sametime chat servers are also located at each
NOC and several CVNs, where they provide chat and whiteboard capabilities to each SG. SGs can use Microsoft
Netmeeting if necessary, but Sametime and Netmeeting clients are not compatible, and therefore cannot talk to
each other.
4.7.2 Task Force Web/Navy Enterprise Portal
The purpose of the Navy enterprise portal (NEP) architecture is to provide a tool for transformation of the Navy to
a web-based business and operations capability. By using the Navy NEP architecture as a tool, “as-is”
architectures can be developed that will facilitate the transformation of the Navy. Many of these “as-is” systems
are complex and interrelated to other systems. By using the NEP as a tool these systems migrate toward common
JAN 2005
4-58
NTTP 6-02
implementations of hardware and software solutions. In addition, the architecture encompasses the resources and
plans currently being developed for the network-centric infrastructures and services. The goal is to better enable
Navy personnel to perform their mission by providing enterprise-wide access to knowledge bases and IT tools.
4.7.2.1 Navy Enterprise Portal Architecture
The NEP framework is presented as a three-tiered architecture describing where the different technologies reside.
The three tiers — presentation/client, application, and data/content — are described below:
1. Presentation/client — The presentation/client tier focuses on browser-based implementations and other
devices such as personal digital assistants (PDAs) or cellular phones. At present, the NMCI configuration
requires Microsoft’s Internet Explorer (IE). IE supports the display of hypertext mark-up language
(HTML), dynamic hypertext mark-up language (DHTML), and extensible mark-up language (XML), and
can access data sources via hypertext transfer protocol (HTTP) and hypertext transfer protocol secure
(HTTPS).
2. Application — The application tier consists of both application logic, often referred to as “components,”
and the server that supports these components, which is referred to as the application server. “Component
Based Design” is the commercial term applied to the process of developing individual, functionally
segregated application logic that can be integrated to form higher level applications. Implementing a
component-based design process is the underlying strategy for providing an integrated, interoperable NEP.
Application servers provide supporting infrastructure for the components. At the application layer,
enterprise-wide systems are recommended. Java 2 Enterprise Edition (J2EE) is the preferred distribution
object model. J2EE is based upon open standards that promote common interfaces for object use, storage,
and run-time interactions. However, minimum standards and message formats are provided that ensure
interoperability with networks Navy-wide, joint, or coalition.
3. Data/content — Web content is typically derived from either static HTML files stored on the web server,
or from dynamic data, as in a database. Static HTML is easy to create, but is difficult to maintain on large
websites because the look and feel of the website is stored inseparably from the data. Best commercial
software development practices dictate that the look and feel (presentation) should be separated from the
data (content) thus allowing them to be managed separately. Data can originate from a variety of sources
including relational databases, local file stores, legacy systems, e-mail systems, GroupWare systems,
directories, search engines, other web services, intelligent agents, and even other websites. Information
sources may also be information consumers, resulting in bidirectional information flows. At the
data/content layer, application logic may use a range of data source access methods; however, primary
relational databases will be accessed with structured query language via Java database connectivity
(JDBC) or open database connectivity.
Each of the three tiers (and the overall structure of NEP) is supported by information assurance and
interoperability.
1. Information assurance is provided at each of the tiers. At the presentation/client tier, users must
authenticate to their workstations and to the portal server. It is strongly desired that the user will use the
DOD public key infrastructure (PKI)-issued digital certificate stored in the common access card (CAC) to
authenticate to the portal server. At this tier, the web browser and the portal server communicate over
HTTPS. At the application tier, the portal uses HTTPS for user interaction and provides access control,
content management, centralized administration, and software application services. At the data/content
tier, the portal must authenticate itself to the application to obtain information requested by the user. All
transactions between the portal and the application accessing the content are audited for security purposes.
2. Interoperability is the inter/intra-tier interface between and within each of the components in the NEP
architecture. Standards and technologies are used to communicate between and within the levels of the
three-tier architecture. Interfaces to data, registering services, querying through a common interface, and
interfaces to services are all used to communicate between and within each of the three tiers.
4-59
JAN 2005
NTTP 6-02
4.7.2.2 NEP Implementation Schedule
NEP portals will be implemented in the FY03–FY04 timeframe. NEP ashore:
1. Fleet NOCs in Norfolk, Naples, and Bahrain
2. All NMCI NOCs (NMCI GNOC will be the replication master site)
3. The NEP will also be installed on OCONUS hardware being deployed as part of ONE-Net.
The schedule for deployment of the NEP to every ship in the Navy is determined by existing funding, ship
availabilities, and fleet initiatives.
4.7.3 Intra-Amphibious Ready Group Distributive Collaborative Planning
IDCP is a capability provided to amphibious platforms. This capability includes voice, IP data, and VTC
exchanged over a wideband LOS RF path. Four key systems make up the IDCP set:
1. DWTS (see Paragraph 4.2.3)
2. TSS
3. ADNS
4. TAC-VTC.
4.7.4 Defense Collaboration Tool Suite
The DCTS is a flexible, integrated set of applications providing interoperable, synchronous, and asynchronous
collaboration capability to the DOD’s agencies, combatant commands, and military services. The DCTS program
identifies, fields, and sustains a dynamic set of evolving standard collaboration tools that bridge between the DOD
and the intelligence community. These tools enhance simultaneous, ad hoc crisis and deliberate continuous
operational action planning (vertically and horizontally) across operational theaters and other domains that
provide operational units and defense organizations simultaneous access to real-time operational, tactical, and
administrative information.
DCTS offers voice and video conferencing, document and application sharing, instant messaging, and whiteboard
functionality to support defense planning. It enables two or more distributed operational users to simultaneously
participate in the mission-planning process without the need to be collocated. With DCTS, military forces enjoy
the capability to link various C4I and mission-planning systems together on a common network to share data,
conduct collaborative planning, and collaboratively consult on information and data at various locations around
the world. As noted in Paragraph 3.10.2, full utilization of DCTS for video and application sharing is too
bandwidth-intensive for effective shipboard use. However, the Navy is fielding a DCTS-compliant version of
sametime chat during FY05.
4.8 MESSAGING SYSTEMS
4.8.1 Defense Message System
DMS is the DOD system of record that replaced the aging AUTODIN system. It is a network-centric system that
leverages COTS technology. DMS functions are very similar to those of the legacy messaging system except that
modern protocols, standards, and technology are used. It is a major component of the DII. It provides secure,
scalable, reliable, efficient, and interoperable electronic message handling and directory services to all
organizations and individuals in the DOD, including tactically deployed users, to our allies, and to other Federal
institutions such as the Department of State and the intelligence community.
JAN 2005
4-60
NTTP 6-02
DMS uses TCP/IP, thus it leverages existing communications backbones already in place and operational within
the DOD. The DMS uses the transport services of the DISN for long-haul transmission and the local subscriber
network infrastructure to deliver messages from writer-to-reader.
DMS is an evolving system that operates in separate sensitive but unclassified (SBU), SECRET, TOP SECRET,
and SCI domains. The current release (DMS 3.0) includes the implementation of the DII Guard, which operates in
a multilevel secure environment allowing messaging between the SBU and SECRET networks. DMS has the
following functions:
1. Message handling system (MHS)
2. Directory services
3. Service management
4. PKI.
4.8.2 Components and Functions
The following is a brief description of each of the DMS components and functions:
1. MHS components — The MHS is the portion of the architecture that formats and provides the means for
moving messages from the originator to a recipient. The user agent (UA) provides the DMS user’s primary
interface to the MHS. The message transfer agent/groupware servers (MTA/GWS) process and transfer
messages to the recipient’s MTA/GWS. The message store (MS) provides the capability for the user to
filter, store, and retrieve messages delivered by MTAs. The MFI is a protocol converter, providing DMS
the capability to exchange messages with non-DMS compliant message handling systems such as
AUTODIN. The mail list agent (MLA) provides X.400 message processing users with access to mail list
services.
2. Directory services components — The directory services is the portion of the messaging support service
function that supports the addressing functionality necessary for the originator to send a message to a valid
recipient. The directory system agent (DSA) is a repository of user certificates containing public key
material and access control information for the X.400 message handling system and multilevel information
systems security initiative (MISSI) security components. The directory user agent (DUA) provides
standardized access to the X.500 directory system for DMS and MISSI components. The administrative
directory user agent (ADUA) performs the same functions as a DUA in addition to administrative
functions (i.e., add entries, remove entries, and modify entries).
3. System management components — The DMS service management system (SMS) includes the
components and procedures required to manage the DMS MHS, directory services, and network time
protocol (NTP) services. The MWS is an integrated suite of tools that, when used in conjunction with
management agents residing on the various DMS components, provides the following capabilities: fault
management, performance management, configuration management, security management, and accounting
management. The embedded management agent (EMA) is a functional entity embedded within each of the
other DMS functional entities. It responds to configuration reporting requests from the MWS.
4. PKI — DMS is the first DOD application to implement PKI technology. It uses the high assurance
hardware token known as Fortezza and a dedicated certificate management infrastructure to establish policy,
enforce procedures, and issue, cancel, and revoke certificates. Within PKI, the certification authority
workstation (CAW) is used to program the Fortezza cards (used to sign and encrypt messages within DMS).
It assigns the public/private key set to users and devices. The DII High Assurance Guard (DII Guard or
“HAG”) is an approved system/utility for separating networks of different classification levels on an NSA
B3-certified platform. It controls the flow of data through the use of various filter settings.
4-61
JAN 2005
NTTP 6-02
DMS is designed to be a “writer-to-reader” system. The writer uses the DMS UA (i.e., client) to draft, sign,
encrypt, and initiate the transmission of the message. The DMS infrastructure delivers the message to the
recipient, and the reader uses the local UA client to decrypt and check the validity of the sender’s identity. In this
regard, the DMS is an end-to-end messaging system. Often at the reader’s location there are business practices
that call for the decryption and validation process not be at a single reader/client workstation. A design that
accommodates a larger reading audience is said to be using a “domain Fortezza” approach. Domain Fortezza is
exploited at larger commands where there is a need to promulgate the received organizational message to several
or many individuals (probably via individual e-mail or via a web-based access system). The more simplistic
writer-to-reader end-to-end concept is depicted in Figure 4-24. Note that on the right side of the figure are Navy
legacy messaging systems, thus DMS messages must traverse a MFI (in this case, located at the TMG).
4.9 ALLIED AND COALITION INTEROPERABILITY
4.9.1 Combined Enterprise Regional Information Exchange Systems
With the CENTRIXS, formally referred to as the Combined Operations Wide Area Network (COWAN), the USN
has duplicated the technologies and operational capabilities of CAS to provide secure web page replication, email, and chat communications to allied and coalition naval and ground forces over SATCOM links. Due to
differing information releasability issues, separate CENTRIXS networks (enclaves) must be established for
different foreign partners. Present CENTRIXS networks include:
1. CENTRIX-4EYES (CFE) — Multinational network with US/UK/CAN/AUS, formerly COWAN A.
2. CENTRIXS JPN — Bilateral network with Japan.
3. CENTRIXS KOR — Bilateral network with Korea.
Figure 4-24. Defense Messaging System
JAN 2005
4-62
NTTP 6-02
4. CENTRIXS N — NATO network, formerly LOCE.
5. CENTRIXS Multinational Coalition Forces Iraq (MCFI) — Multinational network serving nations who
have joined the United States for operations in Iraq. Currently this community encompasses NATO and
approximately 60 other countries.
6. CENTRIXS Global Counterterrorism Task Force (GCTF) — Multinational network serving nations who
have joined the United States in the war on terrorism. Currently connects approximately 70 countries.
7. CENTRIX GCTF Combined Naval Forces CENTCOM (CNFC) — A subset of the CENTRIX GCTF
network servicing maritime forces operating in CENTCOM.
CENTRIXS is not directly connected to the SIPRNET, but KG-175 TACLANE encryption devices can be used to
tunnel CENTRIX through the SIPRNET to provide its services to U.S. users. Additionally, e-mail on CFE and
CENTRIX JPN can be transferred between these enclaves and SIPRNET via a DII guard. There is currently no
automatic guard for transfer of web information, but regular periodic manual relay of web data is conducted for
certain enclaves. Also, releasable COP information is provided on certain enclaves via use of guarding devices.
CENTRIXS access currently requires ships at sea to use SATCOM for all services. Full-time SATCOM access is
generally not available to allied and coalition partners for a number of reasons. Allied units typically “dial-in” to
shore-based CENTRIXS servers four times per day (or as required) for chat, e-mail, and web replication.
4.9.2 Strike Force Electronic Mail 66
SFEM66 is based on NATO standards (STANAG 5066 and 4539) and takes advantage of recent advancements in
HF communications, networking, and modem technologies to provide a low-cost alternative for secure intra-SG
communications and information exchange. SFEM66 has been installed on over 150 ships in the USN, and on
over 60 ships in the navies of Australia, Canada, the United Kingdom, New Zealand, Germany, Belgium, Italy,
France, Japan, and Oman.
SFEM66 provides secure basic IP data transfer (i.e., e-mail with attachments) capability between allied/coalition
afloat forces using HF communications in the 2–10 Mhz range. Present data exchange rate is 9.6 kbps with
upgrades in progress to support 19.2 kbps.
4.9.3 NATO Initial Data Transfer System
NATO established the NIDTS to provide IP services for e-mail, web browsing, and COP/recognized maritime
picture (RMP) to NATO Maritime Command and Control Information Systems (MCCIS) for both land and
maritime elements. It is the approved secure IP delivery path for NATO information in the COMUSNAVEUR
AOR. Typical maritime elements requiring NIDTS connectivity are:
1. NATO command ships (Commander, Standing Naval Forces Atlantic (COMSTANAVFORLANT))
2. U.S. Navy force-level ships operating in the CFFC and COMUSNAVEUR AORs.
CNO has provided funding for NIDTS installation on approximately 20 ships and two shore nodes. There is no
direct connection to the SIPRNET from the NATO WAN. COMLANTFLT ships with the NIDTS are members of
the NATO WAN and are capable of participating in the NATO RMP, e-mail, and web services.
4.9.4 Coalition Convergence
With the proliferation of allied and coalition networks within the various AORs, CNO, the fleet, and SPAWAR
have created a convergence strategy to merge the various allied and coalition network infrastructures. The first
phase of the plan is to merge NIDTS, CENTRIXS, and SFEM66 infrastructures into a single allied coalition
4-63
JAN 2005
NTTP 6-02
infrastructure. Designs for an integrated and low-cost, ship-to-shore and ship-to-ship-capable coalition LAN
afloat, with the supporting shore infrastructure, have been developed.
Standardized CENTRIXSs are currently being fielded on USN ships — CENTRIXS Block 0 with three
workstations on unit-level ships such as DDGs and CENTRIXS Block 1 with ten workstations on large deck
platforms. With Block 0 and Block 1, ships switch security enclaves, based on operational requirements, by
swapping out hard drives on the local servers and workstations and loading the appropriate cryptographic key. Off
ship connectivity is accomplished through SATCOM by tunneling within SIPRNET using a KG-175 TACLANE
encryption device.
Allied vessels have neither SIPRNET nor the same standardized CENTRIXS installs as the U.S. For them, the
connection into the network is direct connection, typically an ISDN call using Inmarsat, to a shore-based U.S. or
indigenous network facility. Occasional use of a U.S.-leased Inmarsat channel is granted for use by the allies in
special circumstances. It has been recognized that not all allied ships have SATCOM. In such circumstances,
SFEM66 can be used to relay information first to a CENTRIXS-equipped platform with satellite capability for
further distribution.
CENTRIXS Block II, which incorporates multi-level thin client (MLTC) technology, will be fielded as a followon to Block 0 and Block 1. The Block II MLTC design will provide significant savings in space, weight, power,
and administrative requirements, and will allow the user to access several CENTRIXS enclaves and SIPRNET at
the same time. The system has been prototyped on two command ships and versions will be installed on unit-level
and additional force-level ships in the next several years.
JAN 2005
4-64
NTTP 6-02
LIST OF ACRONYMS AND ABBREVIATIONS
AADC
area air defense commander
AAT
ATO/ACO tool
AAW
antiair warfare
ABCS
Army Battle Command System
ACCES
advanced cryptologic carry-on exploitation system
ACLS
automatic carrier landing system
ACO
airspace control order
AD
airspace deconfliction
ADAS
automated digital acquisition subsystem
ADNS
Automated Digital Network System
ADUA
administrative directory user agent
AEHF
advanced extremely high frequency
AEW
airborne early warning
AFATDS
Advanced Field Artillery Tactical Data System
AFRTS
Armed Forces Radio and Television Service
AJ
anti-jam
AKDC
automatic key distribution center
AMCM
airborne mine countermeasures
ANDVT
advanced narrowband digital voice terminal
AOC
air operations center
AOR
area of responsibility
APS
afloat planning system
APTS
afloat personal telephone service
ASST
antiship surveillance and targeting
LOAA-1
JAN 2005
NTTP 6-02
ASUW
antisurface warfare
ASW
antisubmarine warfare
ASWC
antisubmarine warfare commander
ATARS
Advanced Tactical Airborne Reconnaissance System
ATIS
advanced technical information support system
ATM
Asynchronous Transfer Mode
ATO
air tasking order
ATWCS
advanced TOMAHAWK weapon control system
AW
air warfare
AWS
advanced wideband system
BAN
base area network
BCA
Broadcast Control Authority
BDA
battle damage assessment
BGP
border gateway protocol
BLOS
beyond line of sight
C2
command and control
C2P
command and control processor
C3
command, control, and communications
C3I
command, control, communications, and intelligence
C4I
command, control, communications, computers, and intelligence
C4IAN
C4I afloat network
C4ISR
command, control, communications, computers, intelligence, surveillance, and
reconnaissance
CA
Challenge Athena
CAC
common access card
CAS
collaboration at sea
JAN 2005
LOAA-2
NTTP 6-02
CAW
certification authority workstation
CC
channel controller
CCOP
cryptologic carry-on program
CDC
combat decision center
CDF
combat direction finding
CDL–A/B
common data link–airborne
CDLMS
common data link management system
CDL–N
common data link–Navy
CEC
cooperative engagement capability
CENTRIXS
combined enterprise regional information exchange system
CERT
computer emergency response team
CES
Commercial Earth Station
CFE
CENTRIX-4EYES
CFFC
Commander, Fleet Forces Command
CHBDL-ST
common high-bandwidth data link-shipboard terminal
CIP
common imagery processor
CJCS
Chairman of the Joint Chief of Staff
CJTF
Commander, Joint Task Force
CMF
common message format
CMSA
cruise missile support activity
CND
computer network defense
CNE
Commander, Naval Forces Europe
CNFC
Combined Naval Forces CENTCOM
CNVA
computer network vulnerability assessment
COA
course of action
COBLU
cooperative OUTBOARD logistics update
COCO
contractor-owned/contractor-operated
COCOM
combatant commander
LOAA-3
JAN 2005
NTTP 6-02
CODEC
coder-decoder
COMFLTFORCOM
Commander, Fleet Forces Command
COMINEWARCOM
Commander, Mine Warfare Command
COMNAVFOR
Commander, Navy Forces
COMPACFLT
Commander, Pacific Fleet
COMSEC
communications security
COMSUBGRU
commander submarine group
COMSUBLANT
Commander Submarine Force, United States Atlantic Fleet
COMSUBPAC
Commander Submarine Force, United States Pacific Fleet
COMUSNAVCENT
Commander, United States Navy, Central Command
COMUSNAVEUR
Commander, United States Naval Forces, Europe
CONUS
continental United States
COP
common operational picture
COTS
commercial off-the-shelf
COWAN
Combined Operations Wide Area Network
CPF
Commander, Pacific Fleet
CSG
carrier strike group
CTP
common tactical picture
CTT
commander’s tactical terminal
CUB
cryptologic unified build
CUDIXS
common user digital information exchange system
CUSNC
Commander, United States Naval Forces Central Command
CVIC
aircraft carrier intelligence center
CWSP
commercial wideband satellite program
DACS
display and control system
DAMA
demand assigned multiple access
DATMS
DISN ATM Services
JAN 2005
LOAA-4
NTTP 6-02
DATMS–C
DISN ATM Services–Classified
DCGS
distributed common ground system
DCMS
Director, COMSEC Material Systems
DCTS
Defense Collaboration Tool Suite
DDG
guided missile destroyer
DDPO
Defense Dissemination Program Office
DET
detachment
DHTML
dynamic hypertext mark-up language
DIA
Defense Intelligence Agency
DII
defense information infrastructure
DIN
defense intelligence network
DISA
Defense Information Systems Agency
DISN
Defense Information Systems Network
DITCO
Defense Information Technology Contracting Organization
DIWS
digital imagery workstation suite
DIWSA
digital imagery workstation suite afloat
DLRP
data link reference point
DMDS
defense message dissemination system
DMS
defense message system
DMSP
Defense Meteorological Satellite Program
DNS
domain name server
DOD
Department of Defense
DON
Department of the Navy
DRASH
deployable rapid assembly shelters
DRSN
Defense Red Switch Network
DSA
directory system agent
DSCS
Defense Satellite Communications System
DSN
Defense Switched Network
LOAA-5
JAN 2005
NTTP 6-02
DTG
digital transmission group
DUA
directory user agent
DUCA
distributed user coverage antenna
DVS
DISN video services
DWTS
Digital Wideband Transmission System
EA
electronic attack (previously ECM)
EAM
emergency action message
EASTLANT
eastern Atlantic
EASTPAC
eastern Pacific Ocean region
EC
Earth coverage
ECCM
electronic counter-countermeasures
ECRNOC
European Central region network operations center
EDAC
error detection and correction
EHF
extremely high frequency
ELF
extremely low frequency
ELINT
electronic intelligence
EMA
embedded management agent
EMC
execution management control
EMCON
emissions control
EMI
electromagnetic interference
EMIO
expanded maritime interception operations
EMR
execution management replanner
ENM
EPLRS network manager
EOD
explosive ordnance disposal
EPLRS-DR
enhanced position location reporting system–data radio
ERGM
extended range guided munitions
ES
electronic warfare support (previously ESM)
JAN 2005
LOAA-6
NTTP 6-02
ESF
expeditionary strike force
ESG
expeditionary strike group
EURCENT
Europe Central
EW
electronic warfare
FAPES
Force Augmentation Planning and Execution System
FDMA
frequency division multiple access
FHLT
force high level terminal
FIWC
fleet information warfare center
FLT BCST
fleet multichannel broadcast
FLTSATCOM
fleet satellite communications
FNMOC
Fleet Numerical Meteorology and Oceanographic Center
FO
forward observer
FOC
full operational capability
FOTC
force over-the-horizon track coordinator
FSM
fleet SIPRNET messaging
FTP
file transfer protocol
FY
fiscal year
GALE–Lite
generic area limitation environment–lite
GBps
gigabytes per second
GBS
Global Broadcast Service
GCCS
Global Command and Control System
GCCS-I3
Global Command and Control System-Integrated Intelligence and Imagery
GCCS-J
Global Command and Control System-Joint
GCCS-M
Global Command and Control System-Maritime
GCTF
Global Counterterrorism Task Force
GIG
Global Information Grid
LOAA-7
JAN 2005
NTTP 6-02
GMF
ground mobile force
GNI
global network initiative
GNO
global network operations
GOGO
Government-owned/Government-operated
GOSC
global operations and security center
GP
general purpose
GPL
general purpose links
GPS
global positioning system
GRCS
guardrail common sensor
GRE
generic routing encapsulation
GRU
grid reference unit
GSORTS
GCCS status of resources and training system
HAG
high assurance guard
HAIPE
high assurance internet protocol encryption
HEO
highly elliptical orbit
HFRG
high frequency radio group
HHR
high hop rate
HITS
hostile-forces integrated targeting subsystem
HNA
host-nation agreement
HSD
high speed data
HTML
hypertext mark-up language
HTTP
hypertext transfer protocol
HTTPS
hypertext transfer protocol secure
HVAC
heating, ventilation, and air conditioning
I&W
indications and warning
IA
information assurance
JAN 2005
LOAA-8
NTTP 6-02
IAVA
information assurance vulnerability alert
IAVB
information assurance vulnerability bulletin
IBS
Integrated Broadcast System
IBS-I
IBS-Interactive
IBS-LOS
IBS-Line of Sight
IBS-N
IBS-Network
IDCP
intra-ARG/ESG distributive collaborative planning
IDTC
interdeployment training cycle
IE
Internet Explorer
IFF
identification, friend or foe
IMOM
improved many-on-many
INFOCON
information operations condition
INM
integrated network manager
IO
Indian Ocean
IOR
Indian Ocean region
IORNOC
Indian Ocean region network operations center
IP
Internet Protocol
IPB
intelligence preparation of the battlespace
IPF
integrated processing facility
IPL
image product library
IPSec
internet protocol security
IQVC
independent quality verification check
ISABPS
integrated submarine automated broadcast processor system
ISAT
IntelSat
ISIC
immediate superior in command
ISL
intersite links
ISNS
integrated ship network system
ISR
intelligence, surveillance, and reconnaissance
LOAA-9
JAN 2005
NTTP 6-02
IT
information technologies
IT-21
information technology for the 21st century
IW
information warfare
IWS
interim wideband system
IXS
information exchange system
J2EE
Java 2 Enterprise Edition
JAOC
joint air operations center
JCA
JSIPS concentrator architecture
JCS
Joint Chiefs of Staff
JCSC
joint communications satellite center
JDBC
Java database connectivity
JDISS
joint deployable intelligence support system
JFACC
joint force air component commander
JFAST
joint flow and analysis system for transportation
JIC
joint intelligence center
JMAST
joint mobile ashore support terminal
JMEM
Joint Munitions Effectiveness Manual
JNL
JTIDS Network Library
JOPES
Joint Operation Planning and Execution System
JPALS
joint precision approach and landing system
JPEC
joint planning and execution community
JRE
joint range extension
JREAP
joint range extension application protocol
JSIPS
Joint Services Imagery Processing System
JSIPS–N
Joint Services Imagery Processing System–Navy
JTAT/GTT
joint threat analysis tools/ground template toolkit
JTDLMP
joint TDL management plan
JAN 2005
LOAA-10
NTTP 6-02
JTF
joint task force
JTF-GNO
joint task force for global network operations
JTIDS
Joint Tactical Distribution System
JTT
joint targeting toolbox
JTWC
Joint Typhoon Warning Center
JWICS
Joint Worldwide Intelligence Communications System
kbps
kilobits per second
LAN
local area network
LANT
Atlantic
LASM
land attack standard missile
LCAC
landing craft air cushion
LCC
local control center
LDR
low data rate
LES
land Earth station
LF
low frequency
LHR
low hop rate
LMS
local monitoring subsystem
LOGSAFE
logistic sustainment analysis and feasibility estimator
LOS
line of sight
LPE
low probability of exploitation
LPI
low probability of intercept
MAGTF
Marine air-ground task force
MAJCOM
major command (USAF)
MATT
multimission advanced tactical terminal
Mbps
megabits per second
LOAA-11
JAN 2005
NTTP 6-02
MCCIS
maritime command and control information systems
MCFI
Multinational Coalition Forces Iraq
MCIXS
Maritime Cellular Information Exchange Service
MCM
mine countermeasures
MCMSEG
mine countermeasures segment
MCU
multipoint control unit
MDR
medium data rate
MDS
message distribution system
MEB
Marine expeditionary brigade
MEDAL
Mine Warfare Environment Decision Aids Library
MEOT
message entry operator terminal
MEPES
medical planning and execution system
METOC
meteorological and oceanographic
MEU
Marine expeditionary unit
MFI
multifunction interpreter
MHS
message handling system
MHz
megahertz
MIBS
maritime integrated broadcast system
MIDB
modernized integrated database
MIDLANT
middle Atlantic
MIDS
Multi-function Distribution System
MILDEP
military department
MILSATCOM
military satellite communications
MILSTAR
military strategic and tactical relay system
MINT
mining segment
MIO
maritime interception operations
MISSI
multilevel information systems security initiative
MIUW
mobile inshore undersea warfare
JAN 2005
LOAA-12
NTTP 6-02
MIW
mine warfare
MLA
mail list agent
MLTC
multi-level thin client
MMD
mean mission duration
MOCC
mobile operations control center
MPA
maritime patrol aircraft
MPE
message processing element
MPRA
maritime patrol and reconnaissance aircraft
MS
message store
MSE
mobile subscriber equipment
MSS
mobile subscriber service
MTA/GWS
message transfer agent/groupware server
MUOS
mobile user objective system
MWF
medical working file
NAS
narrowband acquisition subsystem
NATO
North Atlantic Treaty Organization
NAVCENT
Navy Component, Central Command
NAVCIRT
naval computer incident response team
NAVEUR
United States Navy Europe
NAVMACS
Naval Modular Automated Communications System II
NAVOCEANO
Naval Oceanographic Office
NAVSATCOMMFAC
naval satellite communications facility
NCA
National Command Authorities
NCIS
Naval Criminal Investigative Service
NCMOC
Naval Central Meteorology and Oceanography Center
NCS
net control station
NCTAMS
naval computer and telecommunications area master station
LOAA-13
JAN 2005
NTTP 6-02
NCTF-CND
Navy component task force for computer network defense
NCTS
naval computer and telecommunications station
NCTSI
Naval Center for Tactical Systems Interoperability
NDI
nondevelopmental item
NEMOC
Naval European Meteorology and Oceanography Center
NEP
Navy enterprise portal
NES
network encryption system
NESP
Navy extremely high frequency satellite program
NETWARCOM
Network Warfare Command
NEXCOM
Navy Exchange Command
NFCS
naval fires control system
NGDS
naval global directory service
NGS
naval gunfire support
NIDTS
NATO initial data transfer system
NILE
NATO Improved Link 11
NIPRNET
Non-Secure Internet Protocol Router Network
NISDE
national input segment dissemination element
NITES
Navy Integrated Tactical Environmental System
NLMOC
Naval Atlantic Meteorology and Oceanography Center
nm
nautical mile
NMC
network management center
NMCI
Navy/Marine Corps Intranet
NMSC
Navy and Marine Corps Spectrum Center
NNSOC
Naval Network and Space Operations Command
NOC
network operations center
NPMOC
Naval Pacific Meteorology and Oceanography Center
NRS
NILE reference system
NRT
near real time
JAN 2005
LOAA-14
NTTP 6-02
NRTD
near real time dissemination
NSB
narrow spot beams
NSG
Naval Security Group
NTCSS
Navy tactical command support system
NTDS
naval tactical data system
NTP
network time protocol
OCONUS
outside the continental United States
OIMA
optimized intermediate maintenance activity
OMFTS
operational maneuver from the sea
OMMS–NG
organizational maintenance management system–next generation
ONE-Net
Overseas Navy Enterprise Network
ONI
Office of Naval Intelligence
OOB
order of battle
OOMA
optimized organizational maintenance activity
OPCON
operational control
OPLAN
operation plan
OPORD
operation order
OPSEC
operations security
ORD
Operational Requirements Document
OSC
on-scene commander
OSPF
open shortest path first
OTCIXS
officer in tactical command information exchange system
OTG
over-the-horizon Gold
OTH
over the horizon
OUTBOARD
organizational unit tactical baseline operational area radio detection
PAC
Pacific
LOAA-15
JAN 2005
NTTP 6-02
PCO
procurement contracting officer
PDA
personal digital assistant
PDD
Presidential decision directive
PEO
program executive officer
PGM
precision-guided munitions
PIP
primary injection point
PKI
public key infrastructure
PME
prime mission equipment
POR
Pacific Ocean region
POTS
plain old telephone system
PPLI
precise participant location and identification
PRNOC
Pacific region network operations center
PSTN
public switched telephone network
PTW
precision targeting workstation
QOS
quality of service
R&S
routing and switching
R ADM
relational administrative data management
RBC
reachback cell
RCERT
regional computer emergency response team
RDA
requirements, development, and analysis
RDS
rapid deployment suites
RE
radiant ether
RF
radio frequency
RMAST
reserve mobile ashore support terminal
RMP
recognized maritime picture
RNOC
regional network operations center
JAN 2005
LOAA-16
NTTP 6-02
RRS
radio relay system
RSupply
relational supply
S&M
scheduling and movement
SA
situational awareness
SACC
supporting arms coordination center
SAG
surface action group
SATCOM
satellite communications
SBM
satellite broadcast management
SBU
sensitive but unclassified
SCI
sensitive compartmented information
SDB
Satellite Communications Database
SDN
service delivery node
SECVOX
secure voice
SES
soft copy exploitation segment
SF
strike force
SFEM66
Strike Force E-mail 66
SG
strike group
SGPHES
strike group passive horizon extension system
SHF
super-high frequency
SIBF
special intelligence broadcast facilities
SINCGARS
single-channel ground and airborne radio system
SIPRNET
SECRET Internet Protocol Router Network
SLA
service-level agreement
SLEP
service life enhancement program
SMCM
surface mine countermeasures
SMOOS
Shipboard Meteorological and Oceanographic Observing System
SMS
service management agent
LOAA-17
JAN 2005
NTTP 6-02
SMTP
simple mail transfer protocol
SMU
switched multiplex unit
SNC
system network controller
SOFA
status-of-forces agreement
SOM
system operational manager
SPA
strike planning archive
SPAWAR
Space and Naval Warfare Systems Command
SPC
strike planning cell
SSC
SPAWAR Systems Center
SSEE
ship’s signals exploitation equipment
SSES
ship’s signals exploitation spaces
SSIXS
submarine/satellite information exchange system
STE
secure telephone equipment
STEP
standard tactical entry point
STRED
standard tactical receive equipment display
STT
shore targeting terminal
STU
secure telephone unit
SubHDR
submarine high data rate
SUBOPAUTH
submarine operating authority
SUPPLOT
supplementary plot
SUWC
surface warfare commander
TACAIR
tactical air
TACC
tactical air command center (USMC)
TACINTEL
tactical intelligence
TACOPDAT
tactical operational data
TACS
theater air control system
TADIL
tactical digital information link
JAN 2005
LOAA-18
NTTP 6-02
TADIXS
tactical data information exchange system
TAP
theater air planning
TBMCS
theater battle management core system
TCC
transportation component command
TCF
technical control facility
TCI
TOMAHAWK command information
TCN
terrestial communications network
TCP/IP
transmission control protocol/internet protocol
TDDS
TRAP data dissemination system
TDL
tactical data link
TDM
time division multiplexed
TDMA
time division multiple access
TDN
tactical data network
TDP
tactical data processor
TES–A
tactical exploitation system–Army
TES–N
tactical exploitation system–Navy
TEG
tactical exploitation group
TESS
tactical engagement simulation system
TFCC
tactical flag command center
TFW
task force web
TIBS
tactical information broadcast service
TIP
time division multiple access interface processor
TIPOFF
TIBS Integrated Processor and Online Fusion Function
TIS
tactical input segment
TIU
TIBS interface unit
TLAM
TOMAHAWK land-attack missile
TMCMC
tactical mine countermeasures commander
TMG
tactical messaging gateway
LOAA-19
JAN 2005
NTTP 6-02
TMIWC
theater mine warfare commander
TMPC
theater mission planning center
TPE
transmit processor element
TPFDD
time-phased force and deployment data
TPS
TOMAHAWK planning system
TRANSEC
transmission security
T-RDF
transportable radio direction finding
TRE
tactical receive equipment
TRITAC
Tri-Service Tactical Communications Program
TRIXS
tactical reconnaissance intelligence exchange system
TSC
tactical support center
TSS
tactical switching system
TSTAR
tactical SIGNIT technology adaptive recognizer
TTP
tactics, techniques, and procedures
TTY
teletype
TV-DTS
television direct-to-sailors
TWCS
TOMAHAWK weapon control system
TWM
target and weaponeering module
UA
user agent
UARNOC
unified Atlantic region network operations center
UFO
ultrahigh frequency (UHF) follow-on satellite system
UHF
ultrahigh frequency
USAF
United States Air Force
USMC
United States Marine Corps
USN
United States Navy
USSTRATCOM
United States Strategic Command
JAN 2005
LOAA-20
NTTP 6-02
VIXS
video information exchange system
VLF
very low frequency
VME
versa module Eurocard
VMF
variable message format
VPN
virtual private network
VTC
video teleconference
VTRE
versa module Eurocard/tactical receive equipment
WAN
wide-area network
WeCAN
Web-Centric Antisubmarine Net
WESTHEM
western hemisphere
WESTLANT
western Atlantic
WESTPAC
western Pacific Ocean region
WGS
Wideband Gapfiller System
XML
extensible mark-up language
LOAA-21
JAN 2005
NTTP 6-02
INTENTIONALLY BLANK
JAN 2005
LOAA-22
NTTP 6-02
LIST OF EFFECTIVE PAGES
Effective Pages
Page Numbers
JAN 2005
JAN 2005
JAN 2005
JAN 2005
JAN 2005
JAN 2005
JAN 2005
1 thru 16
1-1, 1-2
2-1 thru 2-34
3-1 thru 3-14
4-1 thru 4-64
LOAA-1 thru LOAA-22
LEP-1, LEP-2
LEP-1
JAN 2005
NTTP 6-02
INTENTIONALLY BLANK
JAN 2005
LEP-2
NTTP 6-02
EDITION JAN 2005

C4I Infrastructure - United States Naval Academy

Transcription

Similar documents

Let AutoHunter track `em down to save you time and money. Let

CAX Barbarian Bruiser

The New Command Culture of Cooperative

2015 Winners

ITT Exelis - Communications Modernization

Satellite Communications within the Army`s WIN

mediterranean dialogue navies

What Women Want! AD

Pass The Word President`s Message