NTP 2 NAVAL TELECOMMUNICATIONS PROCEDURES
NAVY SUPER HIGH FREQUENCY SATELLITE COMMUNICATIONS

8 Page 9 10
NTP 2 SECTION 1 (D)

ORIGINAL 1-1

CHAPTER 1 INTRODUCTION

101. PURPOSE The purpose of this section of Naval Telecommunications Procedures 2 (NTP 2) is to promulgate information concerning direction, management, and control of super high frequency (SHF) satellite communications (SATCOM) systems operating in the X-band which are employed to support naval operations. Recent Department of Defense (DOD) studies project a threefold to fivefold increase in warfighter information transfer requirements that must be satisfied by SATCOM systems in the next decade. This surge in required data transfer capabilities is due largely to the need to perform information exchanges to accomplish distributed collaborative planning, video teleconferencing (VTC), video telemedicine, primary imagery distribution, video teletraining, and remote maintenance/ technical assistance. SHF SATCOM is a joint asset whose wide bandwidth and high data rate characteristics provide the additional satellite capacity required by all of the Services. This section of NTP 2 is applicable to surface ships, submarines, airborne, and ashore subscribers of SHF SATCOM systems. New SHF access procedures and a new access request message format are introduced. These procedures and message format are to be used by joint forces afloat when requesting access to Defense Satellite Communications System (DSCS). Ongoing and future enhancements to SHF SATCOM systems are discussed such as the Service Life Enhancement Program (SLEP), which will provide improved satellite capability for the last four DSCS satellites to be launched beginning in 1999. Information presented in this document will provide the user with the planning guidance needed to employ SHF SATCOM. It is anticipated that modifications to this document will be required based on feedback reports from fleet users of SHF SATCOM.

102. SCOPE This section of NTP 2 applies to naval staff planning at all echelons and to the supervisors of terminal operators. It is intended to complement existing directives, publications, and other NTPs. SHF SATCOM procedural changes promulgated as Fleet Telecommunications Procedures (FTP) or Communications Information Bulletins/ Communications Information Advisories (CIB/ CIA), which modify information contained herein, will be reflected in subsequent revisions to this document as appropriate. Sections 3 and 4 of this NTP 2 provide planning information for naval extremely high frequency (EHF) and commercial SATCOM operations, respectively. Information on ultra high frequency (UHF) SATCOM operations, formerly provided in NTP 2, Section 2, is now provided in the Joint UHF SATCOM Management Manual.

103. DIRECTION The DSCS is a collective resource of DOD, managed and operated as a joint system in accordance with priorities established by the Chairman of the Joint Chiefs of Staff. The command 9

9 Page 10 11
NTP 2 SECTION 1 (D)

ORIGINAL 1-2

relationships for SHF SATCOM operations are illustrated in figure 1-1 and described in the remainder of this paragraph.

Figure 1-1
SATCOM Command Relationships

A. Chairman of the Joint Chiefs of Staff (CJCS). The Chairman of the Joint Chiefs of Staff allocates Military SATCOM (MILSATCOM) resources, including SATCOM assets used in military operations, to satisfy national defense requirements and specifies operational procedures and responsibilities for system managers, operators, and users. The Chairman of the Joint Chiefs of Staff recommends to the Secretary of Defense those actions required for shared use of MILSATCOM assets and services, and reviews proposed cooperative agreements between DOD and other agencies or governments relative to shared use. The Chairman of the Joint Chiefs of Staff also reviews and approves user connectivity requirements, defines the process for requirements documentation, and approves acquisition of transponder bandwidth. The Joint Communications Satellite Center (JCSC) is the DOD focal point for monitoring, coordinating, and formulating actions requiring CJCS approval for all MILSATCOM tactical and contingency operational access; resolving conflicts in resource allocation; and performing other duties as discussed in CJCS Memorandum of Policy (MOP) 37. 10

10 Page 11 12
NTP 2 SECTION 1 (D)

ORIGINAL 1-3

B. Commander in Chief, U. S. Space Command (USCINCSPACE). USCINCSPACE serves as a principal advocate and advisor to the Chairman of the Joint Chiefs of Staff for MILSATCOM systems that support Commander in Chief (CINC) operational requirements. USCINCSPACE is a unified commander responsible for identifying and quantifying emergent SATCOM requirements to the DOD Space Architect. Space assessments are also a responsibility of USCINCSPACE in support of the Joint Staff.

C. Defense Information Systems Agency (DISA). This agency is the DOD-designated manager of the Defense Communications System (DCS). DISA designs, engineers, and develops the DCS to satisfy validated requirements. DISA has overall responsibility for planning, developing, and supporting command, control, communications, computers, and intelligence (C4I) systems that serve the needs of the National Command Authorities (NCA). DISA is subject to the direction, authority, and control of the Assistant Secretary of Defense (Command, Control, Communications, and Intelligence) (ASD[ C3I]), but is responsible to the Chairman of the Joint Chiefs of Staff for operational matters, as well as requirements associated with the joint planning process. For these purposes, the Chairman of the Joint Chiefs of Staff is authorized to communicate directly with the Director, DISA and may task the Director, DISA to the extent authorized by the ASD( C3I).

D. Chief of Naval Operations (CNO). The Department of the Navy (DON) is the systems manager for the Navy's SATCOM program. Acting for DON, CNO approves and directs the implementation of the SATCOM program. Within CNO, the Director, Space, Information Warfare, Command and Control (N6) is tasked with overall responsibility for SATCOM planning and development, and for the sponsorship of the SATCOM program in the budgeting process. The Director, Information Transfer Division (N61) provides policy for operation, maintenance, and management of the Naval Computer and Telecommunications System (NCTS). CNO N61 sponsors and authorizes development and procurement of general communications equipment, and determines personnel and training requirements for communications systems. The Director, Navy Space Systems Division (N63) is responsible for program coordination and acquisition of space systems. CNO N63 assesses future SATCOM concepts, policies, and applications. This office also coordinates Navy requirements with the Chairman of the Joint Chiefs of Staff, the other Services, and DISA. This includes managing the functions of procurement, installation, operation, and logistical support of SATCOM systems.

E. Commandant of the Marine Corps (CMC). CMC approves and directs implementation and usage of SATCOM resources assigned to the Marine Corps. Within Headquarters, Marine Corps (HQMC), the Assistant Chief of Staff, Command, Control, Communications, Computers, Intelligence, and Interoperability is tasked with the overall responsibility for management and oversight of Marine Corps SATCOM requirements.

1. The Commanding General, Marine Corps Combat Development Center (CG, MCCDC) approves and submits nonoperational Fleet Marine Force requirements (e. g., training, testing, etc.) for SATCOM support to HQMC for further processing. 11

11 Page 12 13
NTP 2 SECTION 1 (D)

ORIGINAL 1-4

2. The Commanding General, Marine Corps Systems Command is responsible for the acquisition of Marine Corps SATCOM terminals, including the required logistics support.

F. Unified and Specified (U& S) Commanders. These warfighting commanders are assigned either geographic or functional areas of responsibility. They are responsible to the Chairman of the Joint Chiefs of Staff for the preparation of war plans. The CINCs consolidate and prioritize all SATCOM requirements (including requirements of components and supporting CINCs or commands) that support validated war plans and assigned missions at all levels of conflict within their area.

G. Fleet Commanders in Chief (FLTCINC). The FLTCINCs define their requirements and submit them via the supported CINC to the Chairman of the Joint Chiefs of Staff for validation. FLTCINCs manage assigned SATCOM assets and those assigned to other naval users in their assigned area. They exercise operational direction over assigned SATCOM assets through their supporting Naval and Computer Telecommunications Area Master Station (NCTAMS) and prepare SATCOM communications plans (COMMPLAN) in support of the operations plans of unified or specified commanders.

H. Commanding Generals, Fleet Marine Forces (CG, FMF). These commanders define their SATCOM requirements for naval operations and submit them to the operational commander for further processing. Nonoperational requirements are submitted to CG, MCCDC for approval and further processing by HQMC and the Joint Staff.

I. Commander, Naval Space Command (COMNAVSPACECOM). This commander exercises command authority over subordinate activities assigned by CNO. COMNAVSPACECOM coordinates with DISA and Commander, Naval Computer and Telecommunications Command (COMNAVCOMTELCOM) concerning naval SATCOM requirements, present and future, as directed by CNO. COMNAVSPACECOM is also the naval component commander under USCINCSPACE.

J. Commander, Space and Naval Warfare Systems Command (COMSPAWARSYSCOM). This commander provides the management authority for terminal support of SHF SATCOM systems through PMW 176-4.

K. COMNAVCOMTELCOM. This commander exercises command authority over the Naval Computer and Telecommunications Command. COMNAVCOMTELCOM operates the earth segment of the NCTS within assigned parameters and in accordance with prescribed procedures. NCTAMS personnel act on behalf of the FLTCINCs to manage SHF SATCOM assets allocated to those FLTCINCs.

L. Commanding Officer, NCTAMS. Under the authoritative direction and control of the respective CINC and FLTCINC, each NCTAMS will maintain for COMNAVCOMTELCOM, the operational direction and management control of those assigned assets of the NCTS. The NCTAMS supports the DISA concept of seamless Defense Integrated Services Network (DISN) 12

12 Page 13 14
NTP 2 SECTION 1 (D)

ORIGINAL 1-5

extension by providing Standardized Tactical Entry Point (STEP)/ Teleport services to deployed joint/ fleet forces. In addition, unified Network Operations Centers (NOC) and Joint Fleet Telecommunications Operations Centers (JFTOC) are being established within the NCTAMS for each region. This supports a streamlined C4I infrastructure since the unified NOC will be responsible for providing seamless telecommunications support to joint/ fleet forces.

104. BACKGROUND From the early 1900s, the Navy relied on high frequency radio as the principal transmission medium for long distance communications. This situation began to change in 1963 when the Navy installed and tested SATCOM terminals aboard selected platforms in support of North Atlantic Treaty Organization requirements at shore sites and on flagships. The Navy's early DSCS/ SHF SATCOM access supported afloat Numbered Fleet Commanders using jam-resistant (spread-spectrum/ code-division multiple access [SSMA/ CDMA]) mode of operation that provided a 4800 bits per second (bps) maximum aggregate, full-duplex capability, and Surveillance Towed Array Sensor System (SURTASS) asymmetrical frequency-division multiple access (FDMA) mode of operation. The afloat Numbered Fleet Commander capability was limited to a few medium data rate (1200-2400 bps) circuits with most of the C4I direct connectivity provided via low data rate (LDR) channels.

During Operation DESERT SHIELD/ STORM, Navy C4I requirements increased significantly, saturating all available satellite assets. It was evident that additional satellite assets and capacity were required to support the navy tactical mission and to provide a greater degree of joint and allied communications interoperability. The wide bandwidth and high data rate characteristics of DSCS/ SHF SATCOM allowed SHF SATCOM to emerge as the best solution to provide the additional satellite capacity. In addition, the extent of C4I and warfighting communication requirements had accelerated both in the number of users to include aircraft carriers, cruisers, destroyers, and amphibious flag-configured ships; as well as the total aggregate of mission essential information exchange requirements. These requirements, coupled with the reduced Soviet threat, the use of larger, more capable SHF antennas and the use of demand assigned multiple access (DAMA), resulted in a change in operational philosophy from jam resistant to an unprotected operating mode that provided increased tactical service to the warfighter as afloat SHF tactical terminal installations were expanded and Navy access to DSCS/ SHF SATCOM increased.

Navy SHF SATCOM networks provide afloat units with high capacity telecommunications trunks that are terminated at NCTAMS STEP facilities. The transmission systems and radio frequency (RF) formats employed incorporate advanced bandwidth management features to enhance network operations.

End user applications supported through SHF SATCOM systems fall in four general categories: command and control, mission planning/ support, nontactical initiatives, and SURTASS. 13

13 Page 14 15
NTP 2 SECTION 1 (D)

ORIGINAL 1-6

A. Command and Control Applications. Command and control is supported via SHF SATCOM, primarily through full-duplex X-band circuits that provide secure telephone unit-third generation (STU-III) secure voice, and Global Command and Control System (GCCS) connectivity. In addition, the secure Video Information Exchange System (VIXS) and the Joint Worldwide Intelligence Communications System (JWICS) use SHF SATCOM to provide video-based command, control, and intelligence support to the warfighter. Upon activation of the Global Broadcast Service (GBS), high bandwidth video circuits will likely migrate to virtual duplex architectures.

B. Mission Planning/ Support. Mission planning and support functions are serviced at varying data rates via SHF SATCOM systems. In addition, the Joint Maritime Command Information System (JMCIS), the Joint Deployable Intelligence Support System (JDISS), and the Tactical Environmental Support System (TESS-3) are supported via X-band full-duplex SATCOM links. Upon activation of the GBS, high bandwidth imagery dissemination circuits will likely migrate to virtual duplex architectures.

C. Nontactical Applications. Logistics, administration, training, and online technical assistance describe some of the nontactical applications served by SHF SATCOM systems. The Streamlined Alternate Logistic Transmission System (SALTS) is the largest nontactical user of services, while medical and Public Affairs Office (PAO) VTC applications are the largest nontactical users of SATCOM services. In addition, desktop VTC is an emerging nontactical application that may be served primarily through SHF SATCOM links.

D. SURTASS. SURTASS is a Navy user of DSCS/ SHF. It is a worldwide system of platforms that tow passive acoustic sonar arrays. The shipboard SHF terminal used for this program is the AN/ WSC-6( V). It passes data collected from the sonar arrays via DSCS to the Naval Ocean Processing Facilities at Dam Neck, Virginia, or Whidbey Island, Washington.

105. FUTURE APPLICATIONS

The desire to provide cost-effective solutions that support the increasing communications information transfer needs of afloat commanders has necessitated a reevaluation and realignment of the means available to satisfy naval circuit requirements. Navy SATCOM programs are being refined to meet these needs.

The Copernicus Architecture involves a major restructuring of Navy C4I to put the warfighter at the center of the command and control universe by providing the supporting information needed, when it is required. The Joint Maritime Communications Strategy (JMCOMS) provides the technical and implementation strategy for the communications portion of Copernicus. JMCOMS technical thrusts are designed to introduce systems that facilitate the collection, correlation, and fusion of data to produce and efficiently disseminate information that is required by joint task force (JTF) and joint task group (JTG) commanders in a format that can be readily used. The major components of Copernicus are the CINC Command Complex (CCC) ashore, the Tactical Command Centers (TCC) afloat, the Global Information Exchange System (GLOBIXS), Tactical Data Information Exchange System (TADIXS), and Battle Cube 14

14 Page 15 16
NTP 2 SECTION 1 (D)

ORIGINAL 1-7

Information Exchange System (BCIXS). The Navy SHF SATCOM architecture will support Copernicus by providing additional/ supplemental media for the TADIXS and BCIXS networks. The Automated Digital Networking System (ADNS) is the primary JMCOMS technical thrust for integrating the Navy's SHF SATCOM assets into Copernicus. Figure 1-2 illustrates the major components (pillars) of the Copernicus Architecture. The following paragraphs briefly describe TADIXS and ADNS.

Figure 1-2
Pillars of the Copernicus Architecture

A. TADIXS. These are not physical nets, but rather logical nets established at the request of, and in the mix desired by, the tactical commander. This operational flexibility is at the heart of the Copernican philosophy of placing the operator at the center of the information universe. Technologically, this will be accomplished by addressing data packets across the GLOBIXS, over the CCC metropolitan/ local area network, and onward via the TADIXS to the TCC for assimilation and further dissemination via BCIXS networks as required. The ADNS will provide automated communications media management during this process.

B. ADNS. ADNS is a communications subarchitecture that enhances battle force communications connectivity, flexibility, and survivability through multimedia access and media 15

15 Page 16 17
NTP 2 SECTION 1 (D)

ORIGINAL 1-8

sharing. An ADNS connection plan will automatically control user interfaces, routing functions, and other resources to permit users to share total network capacity on a priority demand basis. The ADNS connection plan will automatically implement the theater, force, and group COMMPLANs. In addition, automated network monitoring and management capabilities will be provided to assist operators in the real-time allocation of communications resources according to selected criteria (e. g., suitability, anti-jam (AJ), priority, etc.).

C. SHF DAMA. DSCS DAMA as proposed by DISA will be supported by FDMA single channel per carrier (SCPC) circuits and will offer a broad range of messaging, director, port in-network, and billing services. It will support semipermanent fixed bandwidth and bandwidth-on-demand through user recognition. DAMA Network Control Terminals (NCT) will be given a certain amount of bandwidth and power to manage. These allocations may not be confined to a single transponder and may not be contiguous within a given transponder. The majority of terminals in the net will be multicarrier capable. The acronym DAMA when used as the implementation standard in SHF DSCS is misleading; it would be better to use the name FDMA Network Management System (FNMS). FNMS is defined as a control system to monitor and control links using standard FDMA modems (OM-73, EFD-8650, CQM-248). FNMS will eventually replace Interim Tactical Orderwire System (ITOS)/ Ground Mobile Force (GMF) orderwires (O/ W). The system capabilities include: login/ logout, O/ W services, FDMA link setup and characterization, FDMA link maintenance and teardown, NCT handover, remote NCT operations, and control circuit transmission security (TRANSEC) (CCT) protection. Eventually, the FNMS will replace the Automatic FDMA Power Control and Link performance reporting functions and be able to control links on leased commercial communications satellite transponders.

106. RELATED DOCUMENTS The following documents provide guidance or assistance in the utilization of SHF SATCOM systems:

A. CJCS MOP 37 MILSATCOM Systems (dated 14 May 1992). This MOP is published to establish operational policy and procedures and provide guidance on MILSATCOM systems as directed by DOD Directive 5105.44. Procedural provisions of the document apply to all users of MILSATCOM systems. It concerns overall MILSATCOM policy and objectives; responsibilities of the Chairman of the Joint Chiefs of Staff, Military Departments, MILSATCOM system managers, the CINCs, the JCSC, and Director, DISA; and operational policy and procedures relative to MILSATCOM systems planning and employment.

B. Joint Chiefs of Staff Instruction (JCSI) 6250.01 DOD MILSATCOM Systems, Draft (dated 1 January 1996). This instruction updates the operational policy and procedures described in CJCS MOP 37 and provides new guidance on MILSATCOM systems. It will supersede CJCS MOP 37. 16

16 Page 17 18
NTP 2 SECTION 1 (D)

ORIGINAL 1-9

C. Integrated Communications Database (ICDB). This database (formerly Integrated SATCOM Database [ISDB]) is administered by DISA under direction of the Chairman of the Joint Chiefs of Staff. It serves as the central database in the DISA Telecommunications Management System-Classified (TMS-C) and is the single source of information relative to all validated DOD telecommunications requirements supported by all communications media. ICDB submissions for SHF SATCOM are addressed in chapter 4.

D. DISA Circular 800-70-1 (dated February 1993). This document provides information relative to satellite techniques, systems concepts, and hardware.

E. DISA Defense Satellite Communications System (DSCS) Standardized Tactical Entry Point (STEP) Concept of Operations (CONOPS) (dated 28 August 1995). This document provides an overview of DSCS STEP procedures and describes system elements necessary for optimal utilization of the DSCS.

F. Emergent Requirements Database (ERDB). This database is administered by USCINCSPACE under direction of the DOD Space Architect. It contains those telecommunications requirements submitted by unified/ specified CINCs that have not been validated through joint action, but which must be considered when formulating future DOD space architecture options.

G. Capstone Requirements Document (CRD). This document, developed by USCINCSPACE for the DOD Space Architect, provides a consolidated set of SATCOM requirements and identifies the technology options that are available to construct an objective DOD architecture. Doctrine, CONOPS, forces, threat, mission needs statements/ operational requirements documents (MNS/ ORD), technology, the ICDB, the ERDB, opportunity, and information infrastructure are considered in the development of the CRD.

H. FLTCINC Operation Orders (OPORD). These documents are the FLTCINC's communications plans to support the joint commander's requirements. They identify the communications systems, procedures, and coordinating instructions for communications operators.

I. Fleet Telecommunications Procedures (FTP). These publications are issued by the NCTAMS to promulgate standard telecommunications procedures for use by communications personnel operating in a particular ocean area. They incorporate procedures unique to that area in amplification of information in NTPs. Changes to the FTP may initially be promulgated in CIB/ CIAs.

J. CIB/ CIAs. These bulletins are promulgated by the NCTAMS to provide accurate and readily accessible reference information on specific tactical communications subjects. CIB/ CIAs provide operations personnel with procedural information applicable to a specific communications area and normally are promulgated by message. Ships and units are required to maintain a complete and current file of CIB/ CIAs as a primary source of communications information. 17

17 Page 18 19
NTP 2 SECTION 1 (D)

ORIGINAL 1-10

Changes in SHF SATCOM operations procedures, for example, may initially be identified via CIB/ CIAs before incorporation into an FTP or NTP.

K. Tactical SHF DSCS Afloat C4I Network CONOPS, Draft (dated 28 October 1996). This document provides an overview of the SHF satellite communications system elements necessary to provide the afloat SHF SATCOM tactical warfighter with reliable command, control, communications, computers, intelligence, surveillance, and reconnaissance (C4ISR) services. 18