Military reference books and manuals (2009-2023, Volume 7)

Fixed Regional Hub Node Operations and Control Plan

JOINT NETWORK NODE-NETWORK SERVICES CAPABILITIES

I-16. A service is a package of one or more related capabilities or functions that provide value to a

customer. This section will describe a set of services which will be provided by or accessible via any JNN-

N hub node.

I-17. Due to their mobile nature, the MRHN and THN may not provide the full suite of services at the hub

node site. Services that are not provided at the MRHN or THN location would be provided remotely from

other locations, such as an FRHN, DOD Gateway, APC, and/or TNOSC. The placement of services

supporting MRHN or THN users is dependent upon unique theater and operational factors, and will be

determined by the unit or organization with operational control of the service.

I-18. The exact location of FRHN services within each theater will also be determined by the unique

architecture and resources of the theater. For the purposes of this document, the FRHN will consist of a

Services Facility and Communications Facility. The FRHN Communications Facility will house the satellite

intermediate frequency equipment and the baseband communications equipment. It is envisioned that the

Communications Facility will co-locate and occupy floor space inside the DOD Gateway Earth Terminal

Complex. The Communications Facility will be manned with personnel from the theater strategic signal

brigade.

I-19. Liaison personnel from the supported tactical units will deploy to the FRHN to assist with the

initial configuration of Tier 2 equipment that interfaces with their deployed forces, as dictated by mission

requirements. The liaisons will also facilitate NETOPS and troubleshooting issues between the FRHN and

deployed force personnel. Ideally, a liaison presence will remain at the FRHN throughout the duration of

their operation. However, deployed force mission requirements may prevent a full-time presence at the

FRHN. For example, if the primary hub node supporting the deployed force transitions from the FRHN to a

THN (when it arrive in-theater), the liaison personnel will likely transfer to the THN, and the FRHN will

become a backup capability for the deployed force.

I-20. Deployed force technicians could then remotely access Tier 2 devices inside the FRHN, as

required. During the initial phases of an operation, it is critical that the deployed force S-6/G-6 coordinate

with the theater signal brigade S-3 to define liaison support activities at the FRHN. Tier 2 equipment

configurations must be well understood by liaison and FRHN personnel to ensure tactical units can

successfully integrate into the FRHN. Liaison and deployed force personnel will have local and remote

access capabilities to Tier 2 equipment that includes routers, switches, call managers, and NETOPS servers.

Any Tier 2 application servers installed at the FRHN will be configured and managed by the division and

BCT liaison officer (LNO) teams.

I-21. The FRHN Services Facility should not reside on the Communications Facility floor, but could

reside in the same building or an adjacent building interconnected with high bandwidth assured

connectivity. However, this may not be achievable at every FRHN location. The Services Facility is

envisioned to house NETOPS management, common user, and functional area business servers, at both the

UNCLASSIFIED and SECRET levels. At this time, it is not anticipated that the JNN-N hub nodes will

provide any services above the SECRET classification level. However, encrypted data above the SECRET

level, such as TS/SCI traffic, will tunnel through a JNN-N hub node to be decrypted at other locations.

I-22. FRHN Services Facility operators will be responsible for the operation and maintenance of Tier 1

NETOPS servers at the FRHN Services Facility which provide shared or theater-level services. Liaison

personnel from the deployed tactical units will assist the Services Facility personnel with the configuration

of Tier 2 devices, which include routers, switches, call managers, and NETOPS servers ESM/NM and

IA/CND. Liaison or deployed force personnel are responsible for the configuration and operation of any

Tier 2 application servers placed at the FRHN. During initial deployment, liaison personnel are expected to

have the technical skills to configure their assigned Tier 2 equipment.

I-23. The FRHN Services Facility is also supported remotely by the TNOSC. The TNOSC has technical

authority over the FRHN Services Facility. Figure I-1 is a simplified block diagram showing the

19 November 2008

FMI 6-02.71

I-5

FOR OFFICIAL USE ONLY

Appendix I

relationship of a CONUS FRHN to the TNOSC. Figure I-2 is a block diagram showing the relationship of

an OCONUS FRHN to the TNOSC.

•Mgt & config of

21st Signal

FRHN tier 1 routing

and IA, oversight of

Brigade

FRHN tier 2 IA

TNOSC

•NetOps integration

into NETCROP

•Service Desk

24X7X365

Technical Authority

Fixed Regional Hub Node

SATCOM &

Network &

Technical

Sys Admin

Control

(NetOps )

•Mgt & config of FRHN SATCOM,

multiplexers, PBX, tier 1 NetOps

aggregation, MIDAS, Marconi ATM

(Communications

(Services

Switches, and TDMA net control

(when acting as TDMA Master

Facility)

Reference Terminal)

•Legacy communications interface

via STEP

•Mgt & config of

Deployable Force

tier 2 routing,

IA, & services

Liaisons

hosted within

the tier 2

enclave

Figure I-1. CONUS FRHN/TNOSC relationship

Strategic Signal

•Mgt & config of

FRHN tier 1 routing

and IA, oversight of

Brigade

FRHN tier 2 IA

TNOSC

•NetOps integration

into NETCROP

24X7X365

•Service Desk

Fixed Regional Hub Node

Technical Authority

SATCOM &

Network &

Technical

Sys Admin

Control

(NetOps)

•Mgt & config of FRHN SATCOM,

multiplexers, PBX, tier 1 NetOps

aggregation, MIDAS, Marconi ATM

(Communications

(Services

Switches, and TDMA net control

(when acting as TDMA Master

Facility)

Reference Terminal)

•Legacy communications interface

via STEP

•Mgt & config of

Deployable Force

tier 2 routing,

IA, & services

Liaisons

hosted within

the tier 2

enclave

Figure I-2. OCONUS FRHN/TNOSC relationship

I-6

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

I-24. For TS/SCI services tunneled through the JNN-N, the FRHN will ensure the transmission path is

operational from the hub node to the deployed JNN or CPN. The TS/SCI users are responsible for the

proper configuration of their encryption, decryption and terminal equipment to ensure end-to-end system

connectivity. The help desks located at the TNCCs will provide TS/SCI network management support to

intelligence users. The FRHN locations must have network connectivity to the TNCCs in order to assure

these TS/SCI users get the required quality of service, as well as connectivity to the wide area services not

available at the DOD Gateway locations.

I-25. The TNOSC might not be co-located with the FRHNs. However, high-bandwidth and robust

NIPRNET and SIPRNET connectivity via the DISN is required between the two facilities. The FRHN

Services Facility will provide aggregated NETOPS data to the TNOSC for integration into the theater

network common relevant operational picture. The TNOSC will also provide technical support to the

Services Facility NETOPS personnel and provide NETOPS support for some Tier 1 and IA services in the

FRHN and other deployed force locations.

PLANNING AND ENGINEERING

I-26. Communications planning and engineering shall be performed at all echelons. The SC(T) will have

the overall responsibility for planning and engineering new missions into the FRHN and MRHN. For JNN-

N equipped units that will be interfacing with theater Army assets (e.g., FRHN), requirements such as

communications architecture and space segment requirements will be consolidated by the SC(T). The SC(T)

will coordinate with supported unit G-6/S-6 representatives to complete an integrated theater JNN-N

architecture. The SC(T) will coordinate the architecture with the supported JTF J-6. The SC(T) will also

coordinate space segment requirements directly with the regional satellite support center (RSSC) or via the

JTF J-6, as appropriate. The SC(T) will coordinate with the FRHN staff and TNOSC to perform detailed

engineering of the legacy baseband systems and IA and IP transport, respectively.

DISN SERVICES

I-27. One of the primary roles of the JNN-N hub nodes is extending the GIG services to the Soldier. The

FRHN interfaces with Army Tier 1/1 routers for the extension of DISN IP services. Non-IP services (e.g.,

DSN) are extended directly from the DOD Gateway. It is expected that the MRHN and THN will also be

co-located with a DISN point of presence and provide the following services to the tactical users:

NIPRNET.

SIPRNET.

DSN.

DRSN.

DISN video services.

I-28. The FRHN will be configured to provide two DRSN circuits per division enclave

(via the

FDMA/Promina network links). The DISN Video Services-Global is expected to have completed the

migration from H.320 serial connectivity to H.323 IP connectivity by the time the first FRHN is

operational. Therefore, serial circuits will not be planned or provisioned for H.320 based DISN Video

Services-Global service. The IP-based DISN Video Services-II will be carried over the NIPRNET and

SIPRNET links.

I-29. The FRHN will not decrypt or breakout Joint Worldwide Intelligence Communications System. Any

Joint Worldwide Intelligence Communications System traffic will pass through the FRHN in encrypted

format. It would then be routed via a tunneled connection over an available IP network or extended via a

dedicated DISN connection to the appropriate operating facility. It is technically feasible to decrypt or

breakout coalition traffic at the FRHN, as driven by theater ASCC requirements.

I-30. The MRHN and THN may or may not have terrestrial connectivity to a DISN point of presence.

Several factors must be taken into account by commanders and signal planners regarding the best location

for a MRHN and/or THN. The amount of time available for mission planning and the required proximity of

19 November 2008

FMI 6-02.71

I-7

FOR OFFICIAL USE ONLY

Appendix I

the JNN-N hub node to the Soldier may result in tradeoffs where DISN connectivity is not available at the

start of an operation, if at all. Ideally, all deployed JNN-N hub nodes will have direct terrestrial DISN

connectivity for redundant and robust communications. However, at a minimum, the FRHN will be DISN

connected.

BASEBAND SERVICES

I-31. The MRHN and THN have a separate baseband shelter which provides baseband services, while the

FRHN integrates these services inside a DOD Gateway Earth Terminal Complex. Services provided

include:

Multiplexing.

Link encryption (e.g., KIV-19A and KIV-7HSB).

IP encryption (e.g., KG-175).

Patch and test.

Private branch exchange phone service with DSN connectivity.

Tier 1/2 NIPRNET and SIPRNET routing services.

Tier 2 NIPRNET and SIPRNET routing services.

IA services (e.g., intrusion detection, firewall, and deep packet inspection).

VOIP.

Secure VOIP.

I-32. Satellite and baseband planning and engineering shall be performed at all echelons. For JNN-N

equipped units that will be interfacing with theater Army assets (e.g., FRHN), baseband service and space

segment requirements will be consolidated through the operational chain(s) of command and communicated

to the ASCC G-6 and SC(T). The prioritization and deconfliction of theater resource allocation ultimately

resides with the GCC. The FRHN personnel will have the responsibility to coordinate with SC(T), JTF J-6,

and supported unit G-6/S-6 representatives to engineer an integrated theater JNN-N architecture. The SC(T)

will also coordinate space segment requirements directly with the DISA RSSC, GCC J-6, or via the JTF J-6,

as appropriate.

SATELLITE TERMINAL SERVICES

I-33. At the FRHN, the antennas, radio frequency equipment, and a portion of the intermediate frequency

equipment will be located outside of the Communications Facility. This equipment will be located inside an

environmentally controlled shelter that is located in close proximity to the antennas. The equipment will be

operated, maintained, configured, and managed by the Communications Facility personnel IAW the FRHN

BOIP.

I-34. The L-band intermediate frequency will be transported from the satellite terminal equipment to the

Communications Facility via fiber optic modems. The L-band interfaces from each terminal will terminate

on L-band combiners and dividers inside the DISA Earth Terminal facility. L-band patch panels provide the

interface to the TDMA, FDMA, and mounted battle command on the move satellite modems. This

equipment will also be operated and maintained by the Communications Facility personnel. The SATCOM

shelters at the MRHN and THN will be operated, maintained, configured, and managed by the Theater

MRHN Team and the division signal company, respectively.

I-35. Master reference terminals are TDMA satellite modems that interface with the NCCs to provide

timing and control for the TDMA network. The master reference terminals are under the OPCON of the

Communications Facility at the FRHN, ITSB/ESB at the MRHN, and the division signal company at the

THN. Each master reference terminal fielded is also fielded with an alternate master reference terminal. The

current TDMA satellite implementation allows an automatic failover capability from a master reference

terminal to an alternate master reference terminal, if the two devices are co-located on the same network

segment. The automatic failover option will be enabled for all operational master reference terminals. In the

I-8

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

event that the entire node (e.g., THN) becomes inoperable, it is possible to manually failover to a remote

node (e.g., FRHN). However the manual cutover will incur TDMA network downtime.

I-36. The FRHN will participate in all TDMA networks that are operating in-theater, assuming resources

are available. Resources may not be available if additional missions are supported off the FRHN, such as

support for autonomous BCTs, functional user support, or ESB/ITSBs not operationally controlled by a

division. The FRHN has the capability to provide the primary master reference terminal/network control

center (NCC) functionality for all TDMA networks. As units prepare and then deploy into the theater, the

FRHN will provide the primary master reference terminal functionality. This ensures that satellite carriers

are operational and waiting for the units as they arrive in theater. Having the primary master reference

terminal/NCC functionality initially at the FRHN allows units at all echelons to join and leave the TDMA

network in an ad hoc manner, which is ideally suited for a dynamic battlefield. As the TDMA network

stabilizes, primary master reference terminal/NCC control for carriers assigned to the division can transition

to the THN. However, due to satellite vendor equipment limitations, this requires a manual configuration

and cutover process, which will incur downtime.

I-37. The DISA Teleport Generation II design will support ―current force‖ modems (for example, Linkway

and iDirect) in the near future (i.e., fiscal year 07-fiscal year 08). DISA supported current force modems do

not replace the FRHN modems operated by the Army, but provide an increased pool of modems available

that the Army may be able to leverage to meet operational requirements. The current force modems will

operate on DISA terminals and require appropriate DISA SAR procedures to gain access. While Teleport

Generation II provides TDMA and FDMA capabilities, FRHNs are required to ensure modular Army forces

are provided with assured satellite access. Hub node personnel must also be responsive to deployed force

network management and reallocation needs IAW the tactical commander’s requirements. The hub nodes

also support the deployed forces’ need for intra-theater Tier 1 and Tier 2 networking and applications

services.

I-38. ESBs/ITSBs supporting a division formation will interface with Tier 2 division enclaves at the THN,

MRHN, and/or FRHN. ESB/ITSBs supporting support brigades will interface directly with Tier 2 separate

enclaves in the FRHN. ESBs/ITSBs supporting theater-level missions will interface directly with a DOD

Teleport. The Army CIO/G-6 identified Army Teleport Generation II requirements in an 11 AUG 06 White

Paper titled:

―Army’s Adjusted Teleport Generation II Satellite Communications (SATCOM) Circuit-

Switched and Internet Protocol (IP) Requirements.‖ For a major combat operation, teleports must be

capable of supporting Tier 2 routing for seven ESBs/ITSBs and be the master reference terminal/NCC for

the ESB/ITSB networks. Procedures outlined in the ―DISA Global Contingency and Exercise Planning

Guide,‖ dated 01-2003, are required to acquire services from a teleport.

MULTIPLEXING AND LEGACY CONNECTIVITY SERVICES

I-39. The FRHN Communications Facility will house traditional devices such as fiber optic modems,

copper modems, multiplexing equipment, and patch and test equipment. Inside the FRHN, the

Communications Facility personnel will have the responsibility for operation and maintenance support of

that equipment IAW FRHN BOIP. The theater MRHN team and division signal company will provide

operation and maintenance support IAW the BOIP for the equipment at the MRHN and THN, respectively.

I-40. Promina multiplexers located at the FRHN, MRHN, and THN will be configured and managed by the

Communications Facility, MRHN Team, and signal company personnel IAW BOIP, respectively. Promina

multiplexers within the FRHN will be placed at the Tier 2 level and operated by the Communications

Facility. Deployed force liaisons will work with Communications Facility personnel to ensure Promina

configurations support end-to-end operation. The Promina multiplexers may be placed within a separate

tactical domain, as required.

I-41. A General Dynamics Vantage gateway switch is present in the MRHN and THN only. The Vantage

provides a secure VOIP interface into the tactical legacy voice network. The Vantage switch in the MRHN

and THN will be operated by the theater MRHN team and division signal company, respectively, IAW

BOIP.

19 November 2008

FMI 6-02.71

I-9

FOR OFFICIAL USE ONLY

Appendix I

ENCRYPTION SERVICES

I-42. Both bulk (e.g., KIV-19A and KIV-7HSB) and packet (e.g., KG-175) encryption devices will be

located in the hub nodes. On-site operation and maintenance, configuration, and management will be

provided by the Communications Facility at the FRHN, theater MRHN team, and division THN IAW the

BOIP.

PRIVATE BRANCH EXCHANGE SERVICES

I-43. The private branch exchange is used to extend DSN connectivity to tactical users. The private branch

exchange provides synchronous serial trunk connectivity via the Promina multiplexers to other hub nodes

and JNN terminals via FDMA satellite links. These circuit switched trunks can support secure calls via

secure telephone unit III and secure terminal equipment. The private branch exchange also interfaces with

the Unclassified IP network, enabling VOIP users to tie into the DSN for unsecured calls. The

Communications Facility personnel will provide the operation and maintenance, configuration, and

management for the private branch exchange in the FRHN, while the theater MRHN team and division

network support companies will operate, maintain, configure, and manage the MRHN and THN private

branch exchanges, respectively. In addition, there is a requirement to include Public Switched Telephone

Network access to the FRHN.

TIER 1 ROUTING SERVICES

I-44. For the purposes of this document, Tier 0 devices are DISA owned and operated, and they form the

backbone and edge of the DISN network. Tier 1 devices are theater assets owned and operated by the

services and CCDRs. Tier 1 devices directly connect to Tier 0 devices and extend communications into

theater level enclaves. Further distinction is made in this document to Tier 1/1 and Tier 1/2 devices. Tier

1/1 devices reside at and above a theater IA boundary and interface directly to Tier 0 devices. Tier 1/2

devices reside below a theater IA boundary and interface to Tier 2 enclaves and devices. Tier 2 devices

provide communications for the deployable force (tactical units).

I-45. Tier 1 NIPRNET and SIPRNET routers are installed inside the MRHN and THN. The Tier 1 routers

interface with the DISA Tier 0 routers for NIPRNET and SIPRNET connectivity. They also tie into Tier 2

routers to extend packet services to the tactical users. At the FRHN, Tier 1/2 NIPRNET and SIPRNET

routers will tie into existing Army Tier 1/1 routers for NIPRNET and SIPRNET connectivity. The Tier 1/2

routers inside the FRHN will be operated and maintained by the Communications Facility personnel, and

configured and managed by the TNOSC. Tier 1 routers in the MRHN and THN, which are connected

directly into a Tier 1 Army Theater infrastructure, will be operated and maintained by the MRHN team and

division signal company, and configured and managed by the TNOSC.

TIER 2 ROUTING SERVICES

I-46. Tier 2 NIPRNET and SIPRNET routers are installed inside each hub node. The Tier 2 routers are

associated with a division level routed network, but could also belong to a corps, functional area, joint

operational command, or ESB/ITSB. Separate routers will be used to provide a unique Tier 2 interface

within the FRHN for each supported unit’s autonomous system. The operation and maintenance

responsibility for the Tier

2 routers in the FRHN, MRHN, and THN is the responsibility of the

Communications Facility personnel, theater MRHN team, and division signal company, respectively. The

configuration and management of the Tier 2 router in the FRHN, MRHN, and THN is the responsibility of

the tactical unit which controls the Tier 2 autonomous system. At a minimum, the local TNOSC will have

read-only access to the full configuration and operational status of all FRHN, MRHN, and THN routers.

I-47. Figure I-3 illustrates conceptually the architecture of the Tier

2 router network at the FRHN

Communications Facility, and how this architecture connects to the Tier 1, IA, and FRHN Service Facility

devices.

I-10

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

Figure I-3. Tier 1 and Tier 2 router connectivity

SECURITY SERVICES

I-48. IA border security will be installed in each hub node between Tier 1 and Tier 2 routing domains on

the NIPRNET and SIPRNET connections. This border security will tentatively consist of a firewall, NIDS,

and deep packet inspection device. Inside the FRHN, IA (physical or logical) will be provided for each unit

supported. An additional Army theater IA stack (i.e., LWN perimeter security) will be present, or leveraged

if co-located, to maintain a baseline IA boundary between Army theater users and the theater Tier 0

infrastructure.

I-49. The devices will be physically maintained by the FRHN operators, while the configuration and

management will be distributed between the TNOSC and the tactical units supported. Each supported

tactical unit (i.e., division or corps) will be allocated a separate physical or logical firewall instantiation to

allow the unit to maintain its IA boundary and to provide a sufficient level of granularity to allow for unit-

specific requirements. The supported tactical unit is responsible for the configuration and management of

IA/CND equipment within the Tier 2 sanctuary created by the firewall. The tactical unit designated

approving authority is responsible for ensuring all Tier 2 systems that interface with the FRHN are properly

patched and meet all IA compliance criteria. The TNOSC will operate, maintain, configure, and manage the

Army Theater IA stack.

I-50. Within the MRHN, the theater strategic signal brigade will operate and maintain the Tier 1 and Tier

2 IA devices, with shared management of the Tier 2 IA posture by the supported tactical unit(s). The

division signal company will have operation and maintenance responsibility for the IA devices installed in

19 November 2008

FMI 6-02.71

I-11

FOR OFFICIAL USE ONLY

Appendix I

the THN. The TNOSC will provide technical oversight for all IA devices within the Army theater. At a

minimum, the TNOSC will have read-only access to the full configuration and operational status of all Tier

2 IA devices within the JNN-N hub nodes. Table I-1 is a summary of the operation and maintenance

responsibilities for the FRHN, MRHN, and THN services. Table I-2 identifies the configuration

and

management responsibilities for equipment in the FRHN, MRHN, and THN.

Table I-1. Operation and maintenance responsibilities

for JNN-N hub node services

Service

Operations and

O&M at MRHN

O&M at THN

Maintenance (O&M)

at FRHN

Satellite Terminals

Communications

Theater MRHN Team

Division Signal Company

Facility Personnel

Master Reference

Communications

Theater MRHN Team

Division Signal Company

Terminal

Facility Personnel

Multiplexers

Communications

Theater MRHN Team

Division Signal Company

Facility Personnel

Private Branch

Communications

Theater MRHN Team

Division Signal Company

Exchange

Facility Personnel

Tier 1 Routers

Communications

Theater MRHN Team

Division Signal Company

Facility Personnel

Tier 2 Routers

Communications

Theater MRHN Team

Division Signal Company

Facility Personnel

Tier 1 IA Devices

Communications

Theater MRHN Team

Division Signal Company

Facility Personnel

Tier 2 IA Devices

Communications

Theater MRHN Team

Division Signal Company

Facility Personnel

Satellite Terminals

Communications

Theater MRHN Team

Division Signal Company

Facility Personnel

Table I-2. Configuration and management responsibilities

for JNN-N hub node equipment

Service

FRHN

MRHN

THN

Master Reference

Communications

Theater MRHN Team

Division Signal Company

Terminal

Facility Personnel

Multiplexers

Communications

Theater MRHN Team

Division Signal Company

Facility Personnel

Private branch

Communications

Theater MRHN Team

Division Signal Company

exchange

Facility Personnel

Tier 1 Routers

TNOSC

Tier 2 Routers

Supported Unit

Division Signal Company

Tier 1 IA Devices

TNOSC

N/A

Tier 2 IA Devices

Supported Unit

Supported Unit and/or

Division Signal Company

and/or TNOSC

TNOSC

I-12

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

DISTRIBUTED USER SERVICES

I-51. User services are those services that are utilized by all tactical Soldiers, regardless of branch or unit.

Distributed user services are services which are implemented using a distributed server hierarchy which

includes server operation and management within the tactical unit echelons. The THN and MRHN will host

limited user services to support their directly connected tactical users. The FRHN will host servers to

support the following functions:

Direct support to Army theater tactical users that do not derive services from an organic or

assigned tactical unit.

Integrate and provide common user services that are also hosted at lower echelons, but require

theater level support to operate across the entire AOR and between theaters.

Provide COOP for common user services which are hosted at lower echelons within the deployed

force.

I-52. The FRHN will be capable of hosting two classifications (i.e., UNCLASSIFIED and SECRET) of

servers. Services above the SECRET classification level will be provided by the appropriate functional

area, and are not anticipated within the JNN-N hub nodes.

I-53. Within the FRHN, Services Facility personnel (IAW the BOIP) will centrally operate and maintain

the servers supporting theater-level common user services (to be determined), while deployed force liaisons

will configure and manage any servers supporting their tactical users. For example, a division may pre-stage

user services out of the FRHN prior to deployment, enabling subordinate units to deploy in phases and draw

services from the FRHN until the division assets are completely deployed and operational. The same

construct can also be used for redeployment. COOP is also a requirement, particularly for units participating

in major combat operations. The FRHN will provide a stable, sanctuary location where services can be

provided with a lower risk of service disruption. The following are examples of distributed common user

services that could be hosted out of the FRHN. Note the initial operational capability (IOC) of the first

FRHN will only include VOIP call management. When available, these services would be hosted out of an

APC—

E-mail.

Organizational messaging.

Domain and directory services.

Collaboration servers.

Information portal servers (Web servers).

VOIP call management.

FTP/Trivial FTP servers.

Storage.

I-54. At the FRHN, the servers associated with these services will be located in the Services Facility.

Ideally, the MRHN and THN would simply be used as a transport mechanism to reach unit services staged

at the FRHN Services Facility via terrestrial connections. In certain operational scenarios, however, network

connectivity between the mobile and fixed hub nodes may not support reaching back to the FRHN for

certain critical user services. Therefore, at the MRHN and THN, the tactical unit may stage common user

services within the baseband shelter or via transit cases as necessary.

CENTRALLY HOSTED USER SERVICES

I-55. Centrally hosted user services are those services that are currently hosted at the Army theater, joint

theater, or global level, and are not actively managed by the tactical echelons. The tactical users rely on the

service, and may remotely access the service to execute unit functions, but do not actively manage the

service within the operational environment.

I-56. The identification of distributed versus centrally hosted user services is based upon the current

architecture and standard operating procedures of each specific service. Therefore, many services which are

19 November 2008

FMI 6-02.71

I-13

FOR OFFICIAL USE ONLY

Appendix I

currently implemented using a distributed architecture may eventually become centrally hosted as more

sophisticated service architectures and tactical network infrastructures are developed. This difference

should be largely, if not entirely, transparent to the end user. This document lists examples of systems which

are currently centrally hosted, with the understanding that this may change.

I-57. Table I-3 identifies some examples of centrally hosted user services; the organization responsible for

providing the operation, maintenance, configuration, and management; and the location from where the

service is provided.

Table I-3. Centrally hosted user services

Service

O&M, configuration and management responsibilities

Physical location

AKO-F

AKO Program Management Office

FRHN Service Facility APC

DNS

TNOSC

Anti-Virus

FRHN (with TNOSC configuration and management

FRHN Service Facility

Server

oversight)

FUNCTIONAL AREA SERVICES

I-58. Functional area services (sometimes referred to as Battlefield Functional Area services) are those

specific battlefield operating systems that the Solders use to accomplish their mission. Examples are ABCS

applications, sustainment systems, and Military Intelligence systems. These servers can be located at the

FRHN or APC and configured and managed by tactical unit liaison personnel at the JNN-N hub nodes to

ensure stable and single hop access to functional area AOR services.

I-59. When the unit prepares to deploy, functional area services can be pre-positioned at the FRHN

Services Facility. These services can then be duplicated or moved to the THN as the operation progresses.

G-6/S-6 coordination at appropriate echelons will be required to ensure assets (e.g., rack space) are

reserved at the JNN-N hub nodes to support these services. In instances where the hardware and software is

provided by the deployed unit, both operation and management and configuration and management

responsibility will fall to the deployed force personnel requiring the service. In instances where the

hardware is provided by the FRHN, the operation and maintenance responsibility for the hardware will fall

to FRHN personnel while the configuration and management responsibility for the software will fall to the

deployed force personnel.

NETOPS MANAGEMENT SERVICES

I-60. NETOPS management services are those services required to keep network transport systems and

network devices operating efficiently and with sufficient quality of service to ensure the Soldier can achieve

and maintain command and control and information dominance. Specific services are described in the

following sub-sections, followed by the organization that will provide the service. The A-GNOSC is the

program of record focal point to the PEOs for any NETOPS design and fielding.

I-61. It should be noted that only NIPRNET and SIPRNET NETOPS management services are provided at

the JNN-N hub nodes. Coalition management services may also be hosted within a JNN-N hub node as the

mission dictates. Management for TS/SCI or other higher network classification levels is not supported at

the JNN-N hub nodes. TS/SCI NETOPS management services are provided at the TNCC.

Frequency Assignment Management

I-62. The SC(T) has the overall responsibility for coordinating the satellite frequency requirements for the

TDMA and FDMA networks of the Army Theater. Tactical unit G-6/S-6 requiring the use of an FRHN or

theater-controlled MRHN will coordinate frequency requirements with the SC(T). The SC(T) will then

coordinate with the GCC J-6 (or JTF J-6) and regional DISA RSSC to lease the appropriate commercial

Ku-band space segment. The Communications Facility personnel in the FRHN will coordinate closely with

tactical organizations and the SC(T) to ensure spectrum allocations for the JNN-N are accurately captured

I-14

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

in the Spectrum XXI spectrum management system, and will be responsible for monitoring and reporting

any discrepancies or issues with the JNN-N TDMA and FDMA frequency assignments.

I-63. The Communications Facility personnel operating the FRHN will conduct real-time frequency

monitoring of the commercial TDMA and FDMA space segment using an L-band spectrum analyzer inside

the Communications Facility. It is anticipated that a minimum of three analyzers will be available inside the

FRHN for personnel to monitor active carriers on the satellites. Communications Facility personnel will

coordinate with the commercial satellite service provider and tactical users to resolve frequency issues (e.g.,

polarization and power level adjustments, etc.). The SC(T) will coordinate with the GCC J-6 and RSSC to

obtain the JNN-N transmission plan for the theater.

I-64. In the future, military Ka-band space segment will be used to support the JNN-N. When that occurs,

applicable DOD spectrum management policies and procedures will be used for all Ka-band satellite links.

Time Division Multiple Access Management

I-65. The FRHN will be a participant in all TDMA meshes operating in the theater, assuming sufficient

satellite and baseband resources are available. A master reference terminal and NCC combination will be

established in the FRHN for all TDMA domains. A functioning master reference terminal/NCC performs

overall management and control of a TDMA network, and is required for operation of the network. The

master reference terminal/NCC communicates with the TDMA modems in the network and coordinates the

transmissions from each terminal. Each master reference terminal/NCC will be a primary or alternate

system for the TDMA domain, depending upon whether the FRHN is the controlling authority for the

domain. The FRHN will be the controlling authority for the TDMA domains supporting theater level JNN-

N users and functional area users supported by JNN-N assets. The FRHN will also be the controlling

authority for JNN-N units that are transiting into or out of the theater. At the FRHN, the master reference

terminal/NCC platforms will be installed in the Communications Facility and configured and managed by

the Communications Facility satellite support personnel.

I-66. The FRHN would also be the controlling authority for a BCT deployment in an expeditionary mode.

In this scenario, the FRHN would provide both the primary and alternate master reference terminal/NCCs.

I-67. When a THN is deployed and operational in a theater, the THN is the controlling authority for the

TDMA domains supporting its subordinate units. The THN would have the primary master reference

terminal/NCC responsibility, and the FRHN would provide the alternate master reference terminal/NCC

capability.

Frequency Division Multiple Access Management

I-68. The FDMA links are single channel per carrier links. In the JNN-N equipped units, these are all

currently setup for Ku-band transmission (Ka-band supported in the future). While the same satellite

modem is used throughout the JNN-N to ensure interoperability, the modem is generally compatible with

other FDMA single channel per carrier satellite modems and will communicate with a variety of military

multi-band terminals and DISA Teleport facilities via Ku-band transmission. Detailed monitor and control

of the satellite modems is performed via the front panel interface. A monitor and control capability for the

satellite modems and other equipment in the radio frequency and intermediate frequency chain is also

performed using a monitor and control application. At the FRHN, the monitor and control application will

be installed inside the Communications Facility and will be operated and maintained by the

Communications Facility satellite support personnel.

I-69. The controlling authority for each FDMA link will be the higher echelon organization. For example,

the FRHN would be the controlling authority for an FDMA link between the FRHN and a JNN at the BCT.

If a BCT has an FDMA link into a JTF headquarters, then the JTF would be the controlling authority for the

circuit.

19 November 2008

FMI 6-02.71

I-15

FOR OFFICIAL USE ONLY

Appendix I

Network Monitoring and Management

I-70. One of the near-term challenges is the expectation that the network management applications used in

the TNOSC are different than the management applications used in the JNN-N. In the near-term, one or

more network management tools may be required at the FRHN Services Facility to allow tactical network

management data to be hierarchically consolidated at the Army theater level. The network monitoring tools

at the FRHN and MRHN will also be able to act as an alternate network monitoring capability for the

tactical unit if the tactical unit-owned network monitoring platform is temporarily out of service. The Tier 1

FRHN monitoring platforms will be operated, maintained, configured, and managed by the Services Facility

personnel.

I-71. Tier 2 FRHN monitoring platforms will be operated and maintained by Services Facility personnel,

and configured and managed by liaison personnel from the supported tactical units. JNN-N network

management data will be integrated into the TNOSC for network common relevant operational picture

purposes and forwarded to the A-GNOSC. As NETOPS management applications are standardized across

the Army, theater NETOPS servers will be consolidated at the TNOSC. The TNOSC is also capable of

providing network common relevant operational picture views to joint NOSCs when supported units are

operating in a joint environment.

I-72. The MRHN will also have the standard tactical network management suite of applications and

hierarchically report its information to the FRHN, if present, or alternatively to the TNOSC. Likewise, the

THN has the standard tactical application suite and reports its information vertically to an FRHN or

MRHN, as appropriate.

I-73. The tactical unit has management and configuration control of network monitoring within its AOR.

Therefore, the hierarchical view provided to the FRHN shall be read-only, allowing the FRHN and TNOSC

personnel to determine network status. The FRHN will have read/write access for theater level (i.e., Tier 1)

assets. There are ongoing efforts to integrate the deployable force and theater network management and

trouble ticketing systems to provide a near real-time status and hierarchical reporting of the JNN-N status.

Firewall Management Server

I-74. Host LAN and perimeter firewalls are installed throughout the JNN-N on NIPRNET and SIPRNET

connections. Multiple firewalls (physical or virtual) will also be located within the THN, MRHN, and

FRHN, depending on the number of different autonomous routing domains (i.e., different divisions,

expeditionary brigades, or functional area units) supported. Firewall management platforms will be installed

in each of the hub nodes. The BCTs also have an organic firewall management capability for use during

autonomous operations.

I-75. The firewall manager will be operated and maintained by the Services Facility at the FRHN, and by

the Theater MRHN Team and division signal company at the MRHN and THN, respectively. At the FRHN,

the firewall management server will reside in the FRHN Services Facility. Each supported tactical unit will

have the responsibility of properly configuring the Tier 2 firewalls within their unit AOR per the technical

direction from the TNOSC and RCERT. The supported tactical units will be able to leverage the FRHN,

MRHN, and/or THN firewall management server to manage firewalls within their unique AORs.

Tactical Local Area Network Encryptor Management

I-76. The General Dynamics Tactical FASTLANE Tactical Local Area Network Encryptor (TACLANE)

(KG-175) is a National Security Agency certified Type 1 packet encryption device used in the JNN-N

architecture to tunnel classified traffic across the BLACK core network. The General Dynamics ESM/NM

Encryptor Manager Solo version is installed in each of the hub nodes. The NM/ESM Encryptor Manager

Solo in the THN is currently used to manage all of the TACLANEs in the division JNN-N infrastructure.

The NM/ESM Encryptor Manager Solo in the FRHN and MRHN will manage and configure their Tier 1

TACLANEs. Any Tier 2 TACLANEs will be configured and managed by the deployed force unit.

I-16

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

I-77. At the FRHN, the ESM/NM Solo will be installed in the FRHN Services Facility and will be

operated, maintained, configured, and managed by Services Facility personnel. The NM/ESM Solo in the

MRHN and THN will be operated, maintained, configured, and managed by the network administrators

operating in the baseband shelter.

I-78. The BCTs also have the Lite version of the ESM/NM Encryptor Manager Solo application for use

during autonomous operations.

I-79. It should be noted that the TACLANE device can only be monitored and managed by a single

ESM/NM. Consequently, it is imperative that clearly delineated roles and responsibilities are established

and maintained.

Router and Switch Management

I-80. Router and switch element management capabilities exist in each of the hub nodes, as well as the

JNNs at brigade, division, and corps levels. The responsibility for router and switch operation and

maintenance is the same as depicted in Table 8-1 above. The responsibility for Tier 1/2 router and switch

configuration and management within the FRHN, MRHN, and THN is the same as depicted in Table I-2

above.

I-81. The element management capability at the THN and JNN will be used to manage and configure the

Tier 2 routers and switches within the division and BCT, respectively. The element managers at the MRHN

and FRHN will be used to manage and configure routers and switches that are theater level assets and any

functional area users supported directly from either of the hub nodes. The element managers at the MRHN

and FRHN can also be leveraged by the supported unit to manage and configure Tier 2 devices within the

unit AOR.

Network Equipment Technologies Inc. Promina Element Management

I-82. A Promina element manager will be installed in the FRHN Communications Facility. The element

manager will have the capability to manage, monitor, and configure all JNN-N Promina resources in the

theater. Inside the FRHN, the Communications Facility personnel will operate, maintain, configure, and

manage the element management platform. For theater level operations, the SC(T) will develop and

coordinate the overall JNN-N multiplexer plan with the GCC J-6 and DISA field offices, where appropriate.

The multiplexer plan will be distributed to theater and division G-6/S-6 representatives for implementation.

I-83. Each hub node and JNN will configure, operate, and maintain their respective Promina multiplexers,

while permitting visibility into their Promina via the element manager located at the FRHN. Excluding the

FRHN, units will monitor and configure their Promina multiplexers using the console interface.

Network Intrusion Detection System Management Services

I-84. The JNN-N NIDS architecture consists of NIDS sensor devices which collect and forward network

information to a NIDS management platform. NIDS sensor devices are installed in all of the JNN-N hub

nodes between the Tier 1 and Tier 2 routers, as part of the IA stack. NIDS sensor devices are also installed

throughout the JNN-N network. Two NIDS event correlation and management platforms

(such as,

UNCLASSIFIED and SECRET) will be installed in each FRHN, MRHN, and THN. In the future (time to

be determined), network IPS devices are planned to replace NIDS devices in the Army’s IA architecture.

I-85. The FRHN Services Facility, Theater MRHN Team, and division signal company will operate and

maintain their respective NIDS management platforms and NIDS sensors within the FRHN, MRHN, and

THN. All Tier 1 NIDS in the FRHN, MRHN, and THN will be configured and managed by the TNOSC.

Tier 2 NIDS in the FRHN, MRHN, and THN will be configured and managed by tactical unit liaisons,

Theater MRHN Team, and division signal company, respectively. JNN-N units can choose to send NIDS

sensor data directly to the NIDS management platform within the FRHN or to the NIDS management

platform within the THN (when available).

19 November 2008

FMI 6-02.71

I-17

FOR OFFICIAL USE ONLY

Appendix I

I-86. Regardless of which hub node is used to collect sensor data, tactical units may access the

corresponding NIDS management platform to view and manage NIDS events within their AOR. Event and

log data from all hub NIDS management platforms will be forwarded to the TNOSC for analysis. Signature

policies will be set by the A-GNOSC and promulgated via the TNOSCs to the respective units.

Network Common Relevant Operational Picture

I-87. The FRHN Services Facility is responsible for consolidating all Army NETOPS data from the tactical

environment in support of theater operational commands. The TNOSC will be responsible for integrating

relevant data from the tactical environment to build the theater network common relevant operational

picture. The TNOSCs will further forward network common relevant operational picture data to the A-

GNOSC for global Army NETOPS SA. Upon request, the TNOSC will provide remote access views into

the theater network common relevant operational picture for the tactical user’s SA.

Vulnerability Management Services

I-88. Vulnerability assessment and remediation servers (e.g., Hercules and Retina) will be installed at the

UNCLASSIFIED and SECRET levels in each of the JNN-N hub nodes. The operation and maintenance of

vulnerability management servers will be performed by Services Facility personnel, theater MRHN Team,

and division signal company for their respective hub nodes. The FRHN, MRHN, and THN vulnerability

management servers will be configured and managed by the TNOSC, theater, MRHN Team, and division

signal company, respectively. Supported tactical units will conduct local vulnerability management for

devices with unit-controlled sanctuaries located at the FRHN Services Facility. Similarly, the theater

MRHN Team and division G-6 personnel will provide vulnerability management support for the MRHN

and THN, respectively. The TNOSC will provide technical guidance.

Service Desk

I-89. A distributed trouble ticket application is expected to be used throughout the JNN-N, and is typically

operated by the TNOSC and supported units S-6/G-6. This hierarchical service desk capability extends

through the division and/or corps level to the theater and global Army levels. When a separate joint chain of

command exists within the joint operational area, trouble ticket information is also exchanged with the joint

command.

I-90. One of the near-term challenges is the trouble ticket application used in the TNOSCs are different

than the application selected for use in the JNN-N. The lack of integration among disparate applications

results in manual intervention to maintain trouble tickets and work flow across application boundaries. In

the near-term, service desk tools compatible with those fielded throughout the JNN-N will be required at the

FRHN Services Facility to allow incidents, problems, and changes being tracked within the JNN-N to be

hierarchically consolidated at the theater level. This will allow FRHN personnel visibility of the incidents,

problems, and changes being tracked within the JNN-N service desk tool. These tools will be operated and

maintained by the Services Facility personnel. Future efforts will address the integration of service desk

tools used in the JNN-N architecture and at the TNOSCs for network common relevant operational picture

and global workflow purposes.

I-91. In the interim, the FRHN will have a limited service desk capability to maintain visibility into JNN-N

incidents, problems, and changes as described above. This will allow tactical users to escalate trouble

tickets for theater level issues to the FRHN electronically. This will allow the TNOSC to track critical

incidents, problems, and changes in its Service Desk application while prioritizing FRHN work based on

theater mission requirements. It should be noted that there will be no automated synchronization between

the JNN-N and TNOSC Service Desk applications. The FRHN will operate using a pre-established criteria

published in an OPORD published by the A-GNOSC for the reporting of incident, problem, status, and

change information to the TNOSC and A-GNOSC.

I-18

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

I-92. Trouble tickets for TS/SCI users will still be the responsibility of the TNCC Network Management

Help Desk staff. Trouble tickets will be coordinated with the Services Facility service desk staff as needed.

This collaboration must be worked out as part of the JNN testing of TS/SCI requirements.

FIXED REGIONAL HUB NODE OPERATIONS AND CONTROL PLAN

BACKGROUND

I-93. The introduction of the AN/FSC-133 FRHN will enable the deployment of JNN-N equipped or

compatible units into a theater where they can immediately begin to draw their satellite and Defense

Information Systems Network (DISN) services from a fully pre-positioned hub node operating in sanctuary.

The FRHN NOC will activate satellite carriers prior to the flow of forces into the theater as well as DISN

connectivity for deployed force access to national networks. The FRHN is the primary hub node when a

THN is not present in-theater. Additionally, it provides backup services in support of a division when their

THN is deployed and fully operational and will be the primary hub node for ESBs supporting corps or

theater Army assets. The FRHN can also provide service to other service components (e.g., Air Force and

Marines), provided their terminals are compatible with the SATCOM and baseband equipment inside the

FRHN. The procedures outlined in this document would also be used by the other service components.

PURPOSE

I-94. The purpose of the FRHN Operations and Control Plan is to establish an integrated framework with

standardized terminology and to consolidate operations, management and control policies; processes; and

procedures for the FRHN NOC and JNN-N enabled/compatible units. This manual identifies the processes

that will be utilized to allocate and manage services provided by the FRHN. It also outlines how some

existing processes will be modified to meet the specific needs of the FRHN and how services are provided

by the FRHN. One of the primary objectives is operational agility, which will allow services to be

provisioned quickly upon initial entry. Of equal importance is the placement of mechanisms to facilitate

rapid change to meet the Soldier’s evolving requirements during all phases of full spectrum operations.

Figure I-4 illustrates where the FRHN fits in an overall communications hierarchy. To achieve a high

degree of operational agility, the following capabilities will need to be realized:

Well defined DAA chain and a streamlined authority to connect (ATC)/ATO process IAW the

DOD Information Assurance Certification and Accreditation Process

(DIACAP) dated 28

November 2007.

Pre-positioned or pre-negotiated SATCOM space segment.

Pre-positioned baseband services and the use of connectivity templates.

19 November 2008

FMI 6-02.71

I-19

FOR OFFICIAL USE ONLY

Appendix I

DISA

COCOM

Field Office

ASCC

Air Force

Navy

Marines

Army

GNOSC

Corps/Div/Bde

THN/JNN/CPN

Planning &

SC(T)

Engineering Cell

TNOSC

Current Ops

Operational Base

(Strategic)

Bde/Bn

Current Ops

FRHN

Figure I-4. FRHN hierarchical relationship

FRHN CAPABILITIES

I-95. This section describes the services that the FRHN will be capable of providing to the JNN-N

enabled/compatible unit to include cross-service support, e.g. the US Marine Corps). The services provided

to the JNN-N enabled/compatible units fall into two categories: wideband access services and baseband

access services.

WIDEBAND (SATELLITE) ACCESS SERVICES

I-96. The FRHN can provide access, via TDMA and FDMA satellite, to DISN services for up to three

divisions (or two divisions and four separates (e.g., expeditionary BCT, ESB, etc.). The FRHN is fielded

with 48 FDMA modems, 48 TDMA modems, and 16 mounted battle command on the move modems. Rack

space is also being reserved for potential integration of Army Airborne Command and Control System

integration into the FRHN.

I-97. The goal is to have a set amount of pre-provisioned space segment available in each AOR to support

short notice warfighter deployments. The pre-provisioned space segment would be supplemented with a

process to rapidly procure additional space segment to support the additional flow of forces into the AOR.

This capability is still in the early stages of development. The capability and its associated

processes/procedures will be provided in separate correspondence and upon subsequent update of this

document.

I-20

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

I-98. The FRHN will serve as the controlling earth terminal for access to and maintenance of the satellite

links between itself and the JNN-N enabled/compatible units. As the controlling earth terminal, the FRHN

NOC will act as the intermediary between the JNN-N enabled/compatible units and the commercial satellite

NOC. The tactical unit will contact the FRHN NOC to initiate initial access or troubleshooting. The FRHN

NOC will bring up the commercial SATCOM NOC in a three-way conference call. Direction for transmit

power initiation, adjustments, and polarization changes can come only from the DISN Satellite

Transmission Service-Global contractor.

I-99. When the Wideband Global SATCOM constellation is operational, and JNN-N equipped/compatible

units and FRHNs are capable of Ka-band operations, the operational control for the Ka-band trunks will be

performed by the USSTRATCOM Wideband Satellite Operations Center.

BASEBAND (DISN) ACCESS SERVICES

I-100. The FRHN will have a permanent set of DISN subscriber services through the normal request for

service/telecommunications request/telecommunications order process with DISA, and these services will

be established at FRHN IOC. This set of DISN subscriber services will be extended to requesting JNN-N

enabled/compatible units via a Tier 2 to Tier 1 Army Service Request (ASR) submitted to the SC(T) via the

ASCC. If the requirement cannot be met by existing FRHN DISN resources, the SC(T) will coordinate with

the ASCC to provision additional services via the telecommunications request/telecommunications order

process. The key to the IOC DISN subscriber services provisioning process is to establish an amount of pre-

positioned services such that the probability of having to provision additional services via request for

service/telecommunications request/telecommunications order process is minimized to the greatest extent

possible. Avoiding this time intensive process will help maintain a high degree of operational agility.

I-101. Figure I-5 provides a graphical representation of this concept. As shown, a set of DISN subscriber

services from the DISN at Tier 0 (i.e., DSN and DRSN) will be pre-provisioned and activated to the FRHN

at Tier 1. The FRHN will interface to an existing Tier 1 LWN perimeter security stack (co-located on the

installation) for access to NIPRNET and SIPRNET. JNN-N enabled/compatible units at Tier 2 will request

access to DISN services from the FRHN and access those services via the FRHN’s Tier 1 connectivity,

rather than directly from the DISN at Tier 0. Upon request, the FRHN NOC will allocate DISN services to

the requesting JNN-N enabled unit from its pre-provisioned set of DISN subscriber services.

19 November 2008

FMI 6-02.71

I-21

FOR OFFICIAL USE ONLY

Appendix I

Tier 0

DISN Services

Tier 1

Pre-provisioned DISN Subscriber

Services (DSS) via a pre-existing

LandWarNet

FRHN (Tier 1) to DISN (Tier 0)

RFS/TR/TO process:

DSN

DRSN

Pre-provisioned

LandWarNet

SIPR

NIPR

FRHN

Tier 2

Tier 2 to Tier 1 ASR to access

DISN Services via the RHN

pre-existing DSS

JNTC-

Enabler

Warfighter

Figure I-5. FRHN/JNN-N DISN services design model

I-102. The DISN operates as a sub-element of the GIG, providing the DOD with consolidated worldwide

telecommunications infrastructure that delivers the end-to-end information transfer network for support to

military operations. It is transparent to its users, facilitates the management of information resources, and is

responsive to national security and defense needs under all conditions in the most efficient manner. DISN

provides interoperable, secure IP data communications services such as NIPRNET and SIPRNET, as well

as voice communication services such as DSN and DRSN. Video teleconferencing services are also offered

via DISN Video Services-II, which is a pass through service in the FRHN. Examples of services that would

be provided through the FRHN are—

NIPRNET provides seamless interoperability for unclassified combat support applications, as

well as controlled access to the Internet.

SIPRNET is the DOD’s largest interoperable command and control data network supporting the

Global Command and Control System, the Defense Message System, collaborative planning and

numerous other classified Warfighter applications.

DSN provides command and control circuit switched service. As a command and control

network, the DSN has military requirements to provide assured service and global connectivity

under stress conditions. The switched voice service of the DSN allows calls originated from

I-22

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

DISN locations to be connected to any other DISN location. The service includes long-haul

switched voice, facsimile, and conference calling.

DRSN is the secure command and control system and is a key component of the DOD global

secure voice services. The DRSN supports the secure voice and secure conferencing

requirements of the President or the SECDEF or their duly deputized alternates or successors,

National Command Authority, components, DOD, and select federal agencies in peacetime,

crisis situations, and wartime. It is a separate, secure switched network that is considered part of

the DISN. Access to this network is provided IAW CJCSI 6215.01C.

DISN Video Services-II, controlled under DISA’s GIG-Combat Support Branch, is responsible

for management and oversight of the DISN Video Services-II implementation and program

sustainment. This replacement to the DISN Video Services-Global is IP based and supports

Integrated Services Digital Network users.

Unclassified VOIP service is provided in the JNN-N. The FRHN has the ability to bridge the

JNN-N VOIP into the DSN for worldwide voice communications.

Secure VOIP is a closed VOIP system that operates on the Secret JNN-N IP network

infrastructure. The system operates at the Secret-High level.

I-103. The project manager for DCATS will provide the FRHN Type Accreditation to the SC(T) DAA.

The SC(T), as the DAA for the theater LWN (to include the FRHN), will issue the FRHN ATC for

connection to the Army theater (Tier 1) point of presence. Additionally, the SC(T) will submit an ATO to

the DISA DAA and obtain the ATC for FRHN services that connect directly to DISA Tier 0. The FRHN

Type Accreditation effort will be accomplished as part of the FRHN IOC. This process is illustrated in

Figure I-6.

SC(T) Submits ATO (2)

Theater LandWarNet

GIG

(DAA=SC(T))

DISA Issued ATC (3)

(DAA=DISA)

SC(T)/DISA

Issued ATCs (4)

FRHN

PM DCATS

(DAA=SC(T))

(DAA = PEO EIS)

Figure I-6. ATO/ATC process for FRHN IOC

REQUESTING FRHN SERVICES

I-104. This section describes the process that will be followed to request satellite and gateway

connectivity into the FRHN. These requests will leverage and utilize DISA’s SAR and Gateway Access

Request (GAR) procedures. It is important to note that these procedures have been streamlined for the sake

of operational agility. SAR and ASR templates will be available on NETCOM/9^th SC(A)’s Regional Hub

Node AKO portal (AKO Files →U.S. Army Organizations →Army CIO/G-6 →NETCOM 9th SC(A)

→Headquarters Staff ACofS, →G-3 Knowledge Centers Regional Hub Node) or the United States Army

19 November 2008

FMI 6-02.71

I-23

FOR OFFICIAL USE ONLY

Appendix I

Forces Command

(FORSCOM) G-6 Spectrum Management AKO portal

(AKO Files U.S. Army

Organizations →FORSCOM Knowledge Centers →G6 →Spectrum Management). For all space segment

requests, a SAR will be required. A SAR will also be required if changes are made to the existing allocation

of the satellite space segment, or terminating equipment (e.g., antenna size) change. This is due to the

continued need to interface with the GSSC or RSSC as an interface to the DISN Satellite Transmission

System-Global for generation of a transmission plan, licensing, etc. The SC(T) will submit a request for

service to DISA to establish initial DISN services provisioned to the FRHN. This will be accomplished as

part of the IOC of the FRHN.

I-105. A request for service and telecommunications request will be submitted by the SC(T) to DISA if

the baseband and/or DISN Tier 0 service requirements exceed the quantity pre-positioned and/or installed

DISN services at the FRHN. An ASR will be submitted by the Soldier to the ASCC for the original

requirement. An ASR is a modified GAR that is scoped for FRHN baseband operations. The ASR is not

intended to go to DISA for any actions and will be handled internal to the theater Army organizations in a

highly expedited manner.

I-106. ESBs supporting division and corps assets will obtain Ku-band (future Ka-band) services from the

FRHN using the SAR/ASR process. The ESB’s supported S-6/G-6 will be responsible for submitting the

SAR and ASR. The ESB S-3 or SB(T) will assist the supported unit with SAR and ASR development. ESBs

may support joint operations (e.g., JTF) and may derive their services via a DOD Gateway. This would

require a normal DISA SAR and GAR submission. All X-band requirements (Ground Mobile Force and

Phoenix terminals) for service through a DOD gateway will continue to follow the DISA SAR and GAR

submission procedures. Note that the IP connectivity (e.g., NIPRNET and SIPRNET) between the FRHN

and co-located gateway will be accomplished via Army Tier 1 and DISA Tier 0 connectivity on the

installation therefore, terminals downlinking at a DOD gateway will have high-bandwidth, low-latency

connectivity to users operating off of the FRHN. The ability to leverage a local LWN perimeter security

stack will provide a high level of assured connectivity between FRHN and DOD Gateway customers by

keeping the interface local to both facilities, thereby keeping traffic between them internal to the theater.

I-107. The FRHN is the intermediary between the DISN and the JNN-N enabled units, and will extend

access to DISN services to the JNN-N enabled tactical unit. As part of the initial communications request,

the Deployable Forces will submit an ATO to the SC(T) to obtain the required ATC. While this is part of

the initial request package that is submitted to the ASCC, the SC(T), as the FRHN DAA, is responsible for

issuing the ATC. This process is shown in Figure I-7.

I-24

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

SC(T)

Customer IAM

SC(T) DAA

submits ATO

issues ATC

(1)

(2)

FRHN

FRHN NOC and

Customer

FRHN Customer

Deployable Forces Information Assurance Manager submits signed

Authorization to Operate (ATO) to FRHN Designated Approval Authority (DAA)

SC(T) is the FRHN DAA

SC(T) authorizes FRHN user’s ATO and issues Authorization to Connect (ATC)

This authorizes the FRHN user to draw IP service from the FRHN

Figure I-7. ATO and ATC process for user connection to FRHN

DETAILS OF THE SATELLITE ACCESS REQUEST/ARMY SERVICE

REQUEST PROCESS

I-108. Each JNN-N enabled Soldier will be required to possess an interim authority to operate (IATO)

certification from their responsible DAA prior to the submission of their SAR/ASR.

I-109. Figure I-8 outlines the SAR/ASR process that will be used for training. Training missions are

assumed to be conducted within Army channels; therefore the only external interaction is with DISA

SATCOM entities.

19 November 2008

FMI 6-02.71

I-25

FOR OFFICIAL USE ONLY

Appendix I

Step 7: Mission Execution/Coordination

Signal Command (Theater)

Phase 6:

Planning & Engineering Cell

Process ASR to ASA

JNN/CPN/ESB/

Maintain access schedule

Submit SAR/RFS/CSS to RSSC/CST for

Step 6:

MBCOTM/A2C2S

Step 6:

SAA/ASA

detailed engineering

SAA/ASA

Coordinates with FRHN, TNOSC, and user

Step 1:

throughout the process

SAR/CSS/RFS/

Incorporates mission number from SAA

ASR/IATO/ATO

into ASA

Corps/Division/BCT

Forwards SAA & ASA forward to FRHN

- Planning Cell

and user

- Submits Request

- Assigns Circuit Priority

Step 4:

Regional Hub

Coordinated through C2

Step 5:

Channels

New COMSAT

SAA/TP

Focal point for Operations

Processing

Step 2:

Step 3:

Verify SAR/CSS/RFS/ASR/

SAR/CSS/RFS/

IATO/ATO + Priority

RSSC/DISA CST (Ku-Band)

ASR/IATO/ATO

Assigns mission number

ASCC

Commercial cell for planning & engineering

- Validates Request &

Review for errors and request resubmission

Army/DISN Services

Priority

for changes, as required

SIPRNET NIPRNET

- Approves Request

Develop transmission plan (TP), coordinate

DSN

/DMS DRI

licensing/landing rights/frequency clearance

DVS-II

Send TP and SAA back to SC(T)

Provides oversight of the quality of service

received from the commercial satellite

vendor

Figure I-8. SAR/ASR process for training missions

I-110. The top half of Figure I-9 illustrates the SAR/ASR process for exercises and operational missions.

In this process, it is assumed that tactical units will be operating in a joint environment, and as a result there

will be CCDR adjudication/validation of resource usage. The following organizational references only

identify parent organization relationships. Inter-organizational communications and coordination will be

handled IAW standard Army doctrine, policy, and procedures.

I-111. Step 1: Soldier submits a SAR, request for service, Commercial Satellite Team (CST) Service

Survey, ASR, network diagram and ATO/IATO to the theater ASCC (OCONUS) or US Army Forces

Command (CONUS). Other steps required are listed below:

Warfighter coordinates with corps/division (as appropriate/applicable) during the development

and submission of the SAR/request for service/CST service survey/ASR, network diagram, and

ATO process.

The corps validates the submission paperwork and forwards to ASCC/FORSCOM.

I-112. Step

2: ASCC/FORSCOM validates request and assigns mission priority and conducts the

following:

ASCC coordinates with the SC(T) and the FRHN NOC to ensure resources are available to

support mission requirements.

ASCC coordinates requirement with CCDR if: space segment is funded by CCDR; Joint mission

supported

(e.g., JTF); adjudication of resources necessary for competing joint mission

requirements.

If disapproved, the SAR/ASR is sent back to the requesting unit noting disapproval. Alternate

COAs may be conducted as follows:

The ASCC and SC(T) will work with the tactical unit to identify alternative

COAs (e.g., Out-of-theater FRHN or Teleport access).

ASCC submits SAR/CST service survey to the organization responsible for commercial

SATCOM management. The commercial SATCOM manager for CONUS is located within

NETCOM/9^th SC(A). The commercial SATCOM manager for OCONUS is located within the

SC(T).

I-26

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

Step 7: Mission Execution/Coordination

Signal Command (Theater)

Phase 6:

Planning & Engineering Cell

Process ASR to ASA

JNN/CPN/ESB/

Maintain access schedule

Submit SAR/RFS/CSS to RSSC/CST for

Step 6:

MBCOTM/A2C2S

Step 6:

SAA/ASA

detailed engineering

SAA/ASA

Coordinates with FRHN, TNOSC, and user

Step 1:

throughout the process

SAR/CSS/RFS/

Incorporates mission number from SAA

ASR/IATO/ATO

into ASA

Corps/Division/BCT

Forwards SAA & ASA forward to FRHN

- Planning Cell

and user

- Submits Request

- Assigns Circuit Priority

Coordinated through C2

Step 4:

Regional Hub

Step 5:

Channels

New COMSAT

Focal point for Operations

SAA/TP

Processing

Step 2:

Step 3:

Verify SAR/CSS/RFS/ASR/

SAR/CSS/RFS/

IATO/ATO + Priority

RSSC/DISA CST (Ku-Band)

ASR/IATO/ATO

Assigns mission number

ASCC

Commercial cell for planning & engineering

- Validates Request &

Step 2a

Review for errors and request resubmission

Army/DISN Services

Priority

for changes, as required

SIPRNET NIPRNET

- Approves Request

Develop transmission plan (TP), coordinate

DSN

/DMS DRI

licensing/landing rights/frequency clearance

DVS-II

Send TP and SAA back to SC(T)

Provides oversight of the quality of service

Combatant Command

received from the commercial satellite

When the ASCC is tasked by the combatant

vendor

command to support a joint mission, or in cases

where the spaee segment is funded by the

combatant command, the combatant command

will:

Process to Initiate First Access

Validate and approve mission request &

priority

Adjudicate resources in the event of

competing joint mission requirements

Step 4: Mission Execution/Coordination

Signal Command (Theater)

Phase 6:

JNN/CPN/ESB/

Step 3:

Required

MBCOTM/A2C2S

TDMA

Planning & Engineering Cell

Updates

Step 5:

Updates Satellite Access Records

Step 1:

Record

Change Request

Update

Step 2:

Regional Hub

Corps/Division/BCT

SAR Change

Focal point for Operations

- Planning Cell

Request

- Submits Request

- Assigns Circuit Priority

Step 6:

Coordinated through C2

Record Update

Channels

Army/DISN Services

RSSC/DISA CST (Ku-Band)

SIPRNET NIPRNET

DSN

/DMS DRI

DVS-II

Updates Satellite Access Records

Provides oversight of the quality of service

received from the commercial satellite

vendor

Process to Initiate a Change

Figure I-9. SAR/ASR process for exercises and operational missions

I-113. Step 3: SC(T) or NETCOM/9^th SC(A) incorporates mission requirement into SATCOM access

schedule: Determines whether there are competing requirements for space segment resources and

adjudicates conflicts with ASCC and/or CCDR for Army or Joint missions, respectively.

Step 4: SC(T)/NETCOM/9^th SC(A) forwards SAR/CST service survey to the GSSC or RSSC before the

following happens:

The GSSC/RSSC satellite support center receives SAR/CST service survey from commercial

SATCOM manager and submits the package to the commercial satellite vendors.

The DISN Satellite Transmission System-Global contractor selected develops transmission plan

and coordinates licensing, landing rights, and frequency clearance.

The GSSC/RSSC assigns mission number and develops the satellite access authorization (SAA).

19 November 2008

FMI 6-02.71

I-27

FOR OFFICIAL USE ONLY

Appendix I

I-114. Step 5: The SAA and transmission plan are sent back to SC(T)/ NETCOM/9^th SC(A). In the case

of training missions, the commercial SATCOM manager tracks space segment utilization. In the case of

joint missions (exercise and operational), the commercial SATCOM manager disseminates the SAA and

transmission plan to the CCDR J-6 for theater space segment utilization and frequency management. The

SC(T) also:

Reviews IATO/ATO and authorizes connectivity.

Coordinates with FRHN NOC to identify equipment set to support mission.

Develops the Army Service Authorization (ASA) from the ASR and incorporates the mission

number from the SAA into the ASA.

I-115. Step 6: The SC(T)/NETCOM/9^th SC(A) provides the ATC, ASA, and SAA/transmission plan to

the tactical unit and FRHN NOC. The FRHN and tactical unit—

Coordinate, as necessary, the development of equipment crew assignment sheets.

Implement crew assignment sheets and prepare systems for operation such as—

FRHN NOC develops crew assignment sheets and implements equipment

configurations as per SAA/ASA/transmission plan/crew assignment sheets,

and provides coordinating authority for satellite and baseband services at the

FRHN.

Tactical

unit

implements equipment configurations as per

SAA/ASA/transmission plan/crew assignment sheets and coordinates with

the FRHN NOC for access to satellite and baseband services.

I-116. The bottom half of Figure I-9 illustrates the process to make a change to the original SAA once the

mission has already been initiated. For changes that don’t affect the space segment or power allocation on

the transponder, the process can be streamlined to support the Soldier’s needs. For example, if a battalion is

directed to jump to another location, the associated battalion CPN would also be geographically relocated.

Prior to the jump, the FRHN may need to cut a new boot file for the CPN’s Linkway modem to update

latitude and longitude information (or other) to ensure transmit and receive synchronization when the CPN

comes up at its new location. This coordination and execution can be handled rapidly between the unit’s S-

6/G-6 and the FRHN NOC. The FRHN NOC would notify the SC(T) of the minor changes. The SC(T)

would notify the RSSC /GSSC of the terminal location changes.

I-117. In establishing the service, the JNN-N equipped/compatible unit will work with the FRHN NOC to

initiate and troubleshoot the service as required. The FRHN NOC will in turn establish the required

coordination with the commercial satellite NOC.

I-118. DISN services will be extended to the JNN-N enabled/compatible tactical unit by the FRHN from a

pre-positioned set of DISN subscriber services. These services include, but are not limited to, SIPRNET,

NIPRNET, DSN, DRSN, and DISN Video Services-II. Since the JNN-N enabled/compatible tactical unit’s

gateway connectivity into the DISN will be extended and managed by the FRHN NOC, the JNN-N

enabled/compatible unit will submit an ASR to the SC(T) (via the ASCC) rather than to the DISA Regional

Contingency and Exercise Branch to request gateway access to DISN services. The JNN-N

enabled/compatible unit’s ASR will be internal to the Army, as direct connectivity to DISN services will be

pre-positioned. However, in the event the FRHN NOC is unable to fulfill a mission requirement (due to

competing or higher priority missions, special circuits, or user-requested STEP circuits), the deployed user

will be responsible for submitting a GAR to the DISA contingency and exercise (via the CCDR for

validation) to request baseband equipment and/or DISN service access via the DOD Gateway.

I-119. For extension of DISA services that the FRHN is not configured or pre-provisioned to support

(e.g., Joint Worldwide Intelligence Communications System encrypted serial circuit), the unit will be

required to submit a GAR via the standard DISA process. The SC(T) and FRHN NOC will assist the unit

with the request to ensure the proper services are provisioned and extended via the hub node.

I-120. A FRAGO ASR is required to initiate a change request to existing FRHN baseband services

provisioned to the unit. A FRAGO ASR is required for any baseband changes driven by mission

I-28

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

requirements. The FRAGO ASR is not intended to go to DISA for any actions and will be handled internal

to the theater Army organizations in a highly expedited manner. It should be noted that not all adjustments

will require theater Army adjudication, requiring only coordination with the FRHN NOC. This will further

streamline the process and keep responsiveness at the necessary level. The FRAGO ASR process is

highlighted in Figure I-10.

SC(T) Planning

Updated from

Change Request

Expedited Change

(ASR)

Update equipment

database and

mission folder

(collaboration portal)

Approve

Update Approved

Updated from

Yes

Change

Expedited Change

Coordinate/Execute Change

User

FRHN NOC

Expedited Change Request

Figure I-10. Change request process

FIXED REGIONAL HUB NODE SITE ADMINISTRATION AND

OPERATION

I-121. This subsection describes critical areas of operational management and site administration for the

FRHN. Once the mission is validated and the unit is drawing services from the FRHN, any requests for

additional services should be coordinated via an ASR with the SC(T).

FRHN DISN SERVICES PROVISIONING

I-122. All FRHNs will have pre-provisioned DISN subscriber services via an initial request for

service/telecommunications request/telecommunications order process coordinated through DISA. Any

modifications or changes to the DISN subscriber services will be coordinated between the SC(T) and DISA

using a request for service/telecommunications request/telecommunications order. The FRHN NOC will

extend the DISN subscriber services to the deployed user. The following guidelines apply:

Deployed users will request the extension of DISN services via an ASR submission.

Deployed users will request changes to existing services via a change request (ASR) to the

SC(T).

In the event that user requests exceed the capacity of pre-positioned DISN subscriber services

between the FRHN and DISA, the SC(T) may be required to submit a request for

service/telecommunications request/telecommunications order to DISA to expand service

capabilities.

MISSION FOLDER

I-123. The FRHN NOC will maintain a mission folder for each deployed customer (e.g., JNN-N enabled

tactical unit). These folders are kept until one year after the circuit deactivates.

19 November 2008

FMI 6-02.71

I-29

FOR OFFICIAL USE ONLY

Appendix I

I-124. Each FRHN NOC will host a SIPRNET asynchronous collaboration portal server (e.g., Microsoft

Sharepoint) with the following mission folder information:

Mission/Exercise name.

Dates/Times of mission/exercise.

Mission priority.

Operational satellite.

Circuit types and data rates.

Points of contact.

Call sign of site and tactical terminal for out-of-band orderwire.

SAR/ASR/ASA/SAA/telecommunications order/telecommunications request/request for service

(Keep all revisions so changes and history can be tracked. Place the most current one on top for

easy reference.)

Mission diagrams, network topology provided by the deployed unit and other drawings. Place the

electronic drawing in the circuit’s folder under circuit actions, and print a copy for the physical

folder.

In-Effect/Completion/Exemption reports—keep all revisions.

Delayed service reports—keep all revisions.

Miscellaneous—all other related information includes:

Crew assignment sheets for the FRHN and each deployed customer.

COMSEC callout message.

ATO/IATO package for deployed unit—complete with statements of

residual risk and consent to monitor/scan signed by the unit DAA.

ATC letter signed by the FRHN DAA.

After action review messages.

NETCOM/9^th SC(A) NETOPS OPORD 05-01.

Circuit priority and status matrix.

Point of contact information for supported unit.

MISSION TRACKING AND STATUS REPORTS

I-125. Reporting will be conducted IAW OPORD 05-01. The SC(T) can supplement the reporting

procedures to meet theater specific requirements.

MISSION PLANNING AND EXECUTION

I-126. Multiple organizations have a role in the planning and engineering for new missions landing at the

FRHN. The ASCC will have overall oversight of the COMSEC layout supporting new missions. The ASCC

will coordinate with the Joint COMSEC Management Office (controlling authority) to ensure keying

material is compatible with JNN-equipped deploying units. The SC(T) will have overall FRHN planning

and engineering responsibilities to include the identification of equipment strings (Tier 1 and Tier 2) and

high-level device configuration (Tier 1). The FRHN NOC will have the responsibility for detailed device

configuration (Tier 1) of VOIP, encryption, and private branch exchange; Tier 2 SATCOM and Promina

configuration; operation and maintenance of the FRHN facility; and NOC operations for the FRHN. The

TNOSC will have responsibility for detailed configuration of Tier 1 routers, IA devices, Army theater

service desk, and develop SA views. The tactical unit will perform detailed device configuration for the

remainder of Tier 2 equipment in the FRHN (e.g., routers, switches, VOIP, and encryption).

I-127. The ASCC will act as the COMSEC coordination point, while the SC(T) will:

Coordinate mission planning with the deployed user and any other third party circuit providers as

necessary.

Conduct the planning and engineering for missions utilizing the FRHN.

I-30

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

Develop ASA and disseminate to tactical unit and FRHN.

Coordinate with the TNOSC to have Remedy ARS accounts created for the deployable force

LNOs inside the FRHN NOC.

Verify SAA and transmission plan with the tactical user and FRHN.

Review COMSEC callout or intent to use message.

Initiate wideband pre-access procedures.

I-128. The wideband pre-access process for the FRHN is dependent upon receipt of the SAA and

transmission plan. During the wideband pre-access process, the following items must be confirmed by the

SC(T):

Satellite earth terminal is available and is in view of the assigned satellite.

Availability of terminal equipment high power amplifier, low noise amplifier, up and down

converters, and modems).

Equipment can perform the mission (verify frequencies, capabilities of equipment, data rates,

types of modulation, etc.).

Verify commercial satellite vendor certification number (as required).

Verify antenna polarization.

Verify Host Nation approval, frequency clearance, landing rights and Federal Communications

Commission licensing (as required).

For cross-banding, ensure equipment requirements and availability.

I-129. The FRHN NOC will:

Provide pre-defined ―connectivity templates‖ to tactical units to streamline the requirements

submission process. Connectivity templates are SAR and ASR templates that are tailored for

specific types of units (e.g., division, BCT, ESB, etc.) to facilitate service request from the

FRHN. The templates are tailored for each theater and made available on the FRHN portal

server.

Develop and implement equipment crew assignment sheets, including, but not limited to:

Private branch exchange configuration.

Tier 2 router and switch configuration—as requested by supported unit.

KIV-19 and KIV-7 configuration—per DISA standard configuration.

TACLANE KG-175 configuration.

Multiplexer Integration and Defense Communications Satellite Subsystem

Automation System (MIDAS) configuration.

NET Promina Multiplexer configuration.

Activate and troubleshoot circuits through the deployed user's lowest level multiplexer. The

FRHN NOC is the controlling authority for the circuits extended to the deployed tactical user.

Develop and disseminate reports IAW OPORD 05-01.

Provide continuous (24 hour a day, 7 days a week, 365 days) operation and maintenance and

expert assistance on mission and circuit activations through mission completion date (end of

exercise [ENDEX]).

Generate the COMSEC call out message.

Ensure COMSEC updates Hotel Juliet are done daily or as required for on-going missions

specified by the controlling authority (i.e., FRHN).

Lead troubleshooting of SATCOM, VOIP, and legacy baseband (e.g., MIDAS, Promina, KGs,

etc.)

Ensure FRHN satellite contractor holds license to transmit/operate.

Support LNOs with Tier 2 troubleshooting, as required.

Provide Tier 2 configuration and management support in the absence of on-site LNOs or remote

access from the deployed force.

19 November 2008

FMI 6-02.71

I-31

FOR OFFICIAL USE ONLY

Appendix I

Report security incidents IAW Army and command procedures.

Maintain operational CM of systems and devices in-use at the FRHN.

Conduct real-time spectrum monitoring of the commercial TDMA and FDMA space segment.

I-130. The TNOSC will:

Create Remedy ARS accounts for unit NETOPS cell personnel and LNOs located at the FRHN.

Provide theater service desk support for the deployed force, FRHN, SC(T), and ASCC staff.

Provide technical support for troubleshooting involving Tier 1 service support to the deployed

forces.

If requested from the unit, provide telephonic troubleshooting assistance with Tier 2 routing and

IA issues.

Develop NETOPS SA in support of theater NOSCs (e.g., tactical unit NOCs, JNCC, TNC, and

TNCC) and the A-GNOSC.

Configure and manage Tier 1 IA devices and routers in the FRHN.

Have oversight of performance and health of the tactical Promina network that interfaces with the

FRHN.

Coordinate Tier 2 firewall access to supported units.

Analyze IA sensor events throughout the deployed force network.

I-131. The supported tactical unit will:

Submit the SAR, request for service, CST service survey, ASR, network diagram, and

IATO/ATO to the ASCC.

Collaborate with SC(T) engineers and FRHN technicians regarding requirements and equipment

configuration.

Verify accuracy and completeness of SAA and transmission plan.

Review equipment crew assignment sheets for accuracy and ability to execute.

Ensure COMSEC is on-hand at deployed locations.

Operationally control Tier 2 equipment (less the SATCOM modems and Promina multiplexers).

The unit is responsible for the configuration and management of the devices. The FRHN NOC

retains the maintenance responsibility for the equipment.

Identify and deploy LNOs to FRHN to configure and establish Tier 2 connectivity with their

respective unit. Ideally, LNOs will remain onsite for the duration of the operation, and remain

under the OPCON of their parent unit; however, the strategic signal brigade will provide

administrative control support to the LNOs. The supported commander will determine manpower

availability for LNOs deployed to the FRHN. It is feasible for the tactical unit to remotely

administer their assigned Tier 2 devices in the FRHN.

Provide the TNOSC and FRHN NOC access to information required to develop theater NETOPS

shared SA.

Implement equipment crew assignment sheets at deployed locations.

Implement equipment crew assignment sheets for assigned Tier 2 equipment in the FRHN.

Assist with troubleshooting communications connectivity with their assigned unit between their

assets and the FRHN (with LNOs at the FRHN).

Configure and manage assigned Tier 2 NETOPS packages in FRHN.

Verify trouble tickets are input into the TNOSC service desk application.

Coordinate with FRHN NOC for satellite access and baseband communications.

Coordinate authorized service interruptions (ASIs) with TNOSC and FRHN NOC.

Ensure that mission status and circuits are properly reported.

Coordinate ENDEX with ASCC, SC(T), TNOSC, and FRHN NOC.

Prepare and submit an after action report within 10 working days after end of access (format

available at the FORSCOM G6 Spectrum Management AKO Knowledge portal

I-32

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

[AKO˘ Files˘ U.S. Army Organizations˘ FORSCOM˘ Knowledge Centers˘ G6 Spectrum

Management])

NETWORK OPERATIONS REPORTING AND TROUBLESHOOTING

PROCEDURES

I-132. For deployed force units that interface to the FRHN, NETOPS reporting will be conducted up

through appropriate echelon NOSCs to the TNOSC. Deployed force units that are associated with a joint

operation will report NETOPS data to a JNCC, with a lateral reporting responsibility to the TNOSC for SA.

The deployed force units will provide the TNOSC access to information required to develop theater

NETOPS shared SA for the JNN-N IP transport (i.e., VPN, Tier 1 routers, and Tier 2 routers). It should be

noted that there is a lack of integration between deployable force and theater NETOPS systems, which

complicates NETOPS reporting. The flow of NETOPS data is illustrated in Figure I-11.

JTF-GNO

DISA

COCOM

TNC

TNCC

A-GNOSC

JTF

JNCC

THN

TNOSC

Required NetOps SA Data Flow

Corp/DIV/BCT

NetOps SA Data Flow, as Required

FRHN

NOSC(s)

Connect

Theater ITSB/ESB,

Autonomous BCT,

and DIV (w/o THN)

NOSC(s)

Figure I-11. Flow of NETOPS data

I-133. The FRHN NOC is notified of and/or identifies service degradation and outages and initiates the

troubleshooting process. The FRHN NOC will determine the appropriate organization or entity to route the

service calls to and initiate troubleshooting. See Figure I-12 for a high level diagram depicting the

troubleshooting relationships.

19 November 2008

FMI 6-02.71

I-33

FOR OFFICIAL USE ONLY

Appendix I

Warfighter

Initiated Request

for Assistance

Trouble

Telephone

Ticket

TNOSC

(Tier 1 IP and IP

Networks

Interfaces to Tier 0)

FRHN NOC

Expert Assistance

(Promina, MIDAS,

to Lower Echelon

Sys Admin

Crypto, VoIP, DRSN,

Organizations

DSN, SATCOM, Tier 2

IP)

Security Events

LNOs

RCERT

Coordination

as Necessary

Issues that

Cannot be

Resolved by the

RHN NOC will

be Escalated to

the Army

Commercial

Theater NOSC

SATCOM

NOC

Figure I-12. Troubleshooting relationships

I-134. The FRHN NOC will:

Be initial point of contact for FRHN NETOPS and troubleshooting issues.

Initiate trouble tickets in support of the tactical units (as required).

Escalate trouble tickets to TNOSC for theater level support (as required).

Coordinate scheduled ASIs with the designated service desk no later than (NLT) 72 hours prior

to outage (using Army theater service desk application).

Coordinate emergency ASIs with the designated service desk NLT 24 hours (where possible)

prior to the outage (using Army theater service desk application).

Report unscheduled outages to the TNOSC IAW OPORD 05-01 (using TNOSC service desk

application).

Submit IA event reports (e.g., IAVM, incident/intrusions/virus, and data spillage, etc.) IAW AR

25-2 and Army Best Business Practices.

Work with the TNOSC to close trouble tickets upon successful restoral (within 15 minutes of

restoral).

I-135. The TNOSC will:

Be the theater service desk for the deployed force.

I-34

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

Set up reporting system to support FRHN and tactical formations (with A-GNOSC oversight).

Set up NETOPS views.

Set up and collect NETOPS SA data for the deployed force and disseminate to tactical NOCs,

JNCCs, CCDR TNCC, DISA TNC, and the A-GNOSC per existing SOP.

Create custom SA views to support joint theater level NOSCs.

I-136. The unit will:

Report scheduled ASIs affecting the WAN transport to the FRHN NOC NLT 72 hours prior to

the outage (via telephonic or electronic means [Army theater service desk application]).

Report emergency ASIs affecting the WAN transport to the FRHN NOC NLT 24 hours (where

possible) prior to the outage (via telephonic or electronic means [Army theater service desk

application]).

Report unscheduled outages to the FRHN NOC IAW OPORD 05-01 (via telephonic [in-band or

out-of-band] or electronic means [Army theater service desk application]).

Work with FRHN NOC to close trouble tickets upon successful service restoral.

Submit IA event reports (e.g., IAVM, incident/intrusions/virus, and data spillage, etc.) IAW AR

25-2 and Army Best Business Practices.

Interface and report to the JNCC per JTF requirements.

I-137. In the near-term, there is a disparity in the NETOPS applications that have been fielded to JNN-N

equipped units and the TNOSCs/A-GNOSC. The FRHN is fielded with JNN-N compatible applications,

and will aggregate NETOPS data from the deployed forces with which it interfaces. FRHN NETOPS data

will be interfaced with the TNOSC to develop SA views for lateral and vertical consumers.

ACCESS PROCEDURES

I-138. The following paragraphs discuss access procedures.

WIDEBAND ACCESS PROCEDURES

I-139. The following is guidance for the FRHN on satellite access:

Deployed user calls FRHN NOC using out of band communications (e.g., cell phone, Iridium,

international maritime satellite, etc.) and indicates they are ready to access the satellite.

FRHN NOC has assigned FDMA and TDMA carriers online awaiting deployed force access.

Deployed user acquires FDMA or TDMA receive carrier(s) and adjusts azimuth/elevation and

polarization to maximize receive signal.

Deployed user calls FRHN NOC, using out-of-band communications, and indicates ready to

begin transmitting.

FRHN NOC initiates conference call to include deployed force user and DISN Satellite

Transmission System-Global NOC.

DISN Satellite Transmission System-Global hub operator works with deployed force user to fine

tune polarization and adjust transmit power.

BASEBAND ACCESS PROCEDURES

I-140. The FRHN NOC is the controlling authority for the activation of all circuits as well as

troubleshooting, etc. The following information is a high-level example of baseband access procedures.

More detailed information will be contained in tactics, techniques, and procedures and SOPs, which will be

available on the FRHN SIPRNET portal servers. Other procedures include:

Once the FRHN FDMA carrier is on the satellite, the operator shall confirm by bit error rate test

via transmit satellite loopback. In certain cases, this will be impossible to do because of satellite

antenna configuration, etc. The FRHN operator shall also normalize the receive frequency on the

down converter and then qualify the link by running the bit error rate test for 30 minutes (period

19 November 2008

FMI 6-02.71

I-35

FOR OFFICIAL USE ONLY

Appendix I

can be shortened or testing terminated, depending on coordination between the commercial

satellite NOC, the FRHN, and the JNN-N enabled tactical user) end to end with the JNN-N

enabled tactical user’s Firebird, preferably between the Red side of the FRHNs crypto device and

the JNN-N enabled tactical user’s crypto device. Some units lack Firebird equipment, so a

loopback at the tactical end back towards the gateway should be performed to confirm

connectivity, again at to the lowest level possible). This provides validation that the radio

frequencies are correct, the modem settings are correct, the crypto device strappings are

compatible, and the correct COMSEC segment is being used. A multiplexer loopback can be

extended to include the Promina SA-TRK card. The Promina will indicate green up with a

downloop condition on the SA-TRK card. This quickly verifies the path and all equipment in the

string at that point through the satellite.

After the link has been qualified, the FRHN operator shall normalize both sides to connect the

multiplexers end-to-end. The multiplexers should lock up. After the SA-TRKs are working, the

individual circuits can then be programmed and/or mapped.

If there is adequate bandwidth in the overall aggregate, a permanent test circuit should be

provisioned.

FRHN personnel will work with the deployed units to establish DSN trunks, DRSN trunks, and

the IP subsystems.

CONFIGURATION MANAGEMENT PROCEDURES

I-141. The program manager for DCATS will maintain physical plant CM of rack face elevations,

hardware, software version, and firmware version control for equipment in the FRHNs. Coordination

between the program manager, DCATS; the program manager, tactical radio communications systems;

SC(T); FRHN NOC; and the TNOSC will be necessary to ensure accuracy of the CM database. The

program manager, DCATS, will disseminate software and firmware updates and hardware modifications to

the appropriate organizations for coordination and activation. The program manager, DCATS, will test all

updates/modifications prior to dissemination to the field. Figure I-13 is a high level diagram illustrating the

concept.

I-36

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Appendix I

SC(T) Planning

Daily Equipment

Configuration Updates

Daily Equipment

TNOSC

FRHN

Configuration Updates

Figure I-14. Operational configuration management process

FAILOVER FROM A TACTICAL HUB NODE TO A FIXED

REGIONAL HUB NODE

I-143. Two failover options are available. One failover option is to preposition tactical unit configuration

information at the FRHN NOC, and perform a manual cutover at the direction of the tactical commander.

This option will likely take several hours to execute and bring the tactical unit up on the FRHN.

I-144. The second failover option is to have the FRHN participate in the supported unit’s TDMA meshes

at all times. If the THN becomes inoperable, the NCC in the FRHN NOC will be brought online to control

the mesh. This option provides the fastest failover capability for the TDMA network. FDMA circuits will

still require a manual cutover. Development of a technical solution to this failover option is being pursued

by the Systems Engineering Integrated Product Team.

I-145. If a failover is necessary and FRHN resources are unavailable, the ASCC (ICW the CCDR) will

adjudicate mission priorities. Ideally, initial priorities should be established as part of the mission planning

process.

I-146. The following factors will have to be considered to execute a failover:

Is the FRHN in the same satellite coverage area as the THN? This may require transfer of

mission(s) to new satellite.

What is the current command relationship specifically as it pertains to the THNs division

commander and the FRHN’s SC(T) commander? The direction could come from the ASCC or

the CCDR or both depending on the environment.

Are transmission plans and link budgets pre-positioned?

Are frequency clearances for FRHN pre-positioned?

Is authority to transmit for FRHN pre-positioned?

Is synchronization of the network and reroute plan available?

I-38

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Fixed Regional Hub Node Operations and Control Plan

CONTINUITY OF OPERATIONS

I-147. COOP capability between FRHNs would be a manual process. Figure I-15 depicts the relationships

and information gaps that would require full synchronization for immediate COOP capability between

FRHNs.

NETCOM

ASCC

Planning &

SC(T)

Planning &

Engineering

Equipment Configurations, SAA, ASA,

Change information, COMSEC, Diagrams,

Planning Databases, Engineering Data, etc.

TNOSC

Current Ops

A-GNOSC

NETOPS views, equipment configurations,

IAVA, reporting system, helpdesk, SA,

network topologies, etc.

FRHN

Current Ops

Collaboration Portal, Equipment, Config,

Operational Database, Mission Folders,

ASR, SAA/RFS Circuit Changes,

Freq License, ATC, LNO, etc.

Figure I-15. COOP precursors

END OF EXERCISE PROCEDURES

I-148. The unit identifies the Start of Exercise, or mission, and ENDEX times in the SAR/ASR

submission. Prior to communications termination, the unit will coordinate with the TNOSC service desk 24

hours prior to communications termination, and again 30 minutes prior to communications termination.

I-149. If the ENDEX time/date is different than what is identified in the SAR/ASR, a formal record

message shall be sent by the unit to the ASCC identifying the point of contact details, original SAR/ASR

ENDEX date time group, requested new ENDEX date time group, and the purpose for extension or early

termination. It is imperative that the message for an extension be sent as early as possible to ensure space

segment is available and leased to support the duration of the mission.

I-150. The unit will submit an after action review within 10 days of ENDEX to the ASCC and SC(T).

Once the after action review has been disseminated, the TNOSC will post an electronic copy in the mission

planning folder. The after action review will be in Microsoft Word or Adobe Acrobat format. The after

action review should be used to identify processes and procedures that worked well and/or need

improvement. Recommendations to improve the processes and procedures are encouraged. Recommended

categories include:

19 November 2008

FMI 6-02.71

I-39

FOR OFFICIAL USE ONLY

Appendix I

Service request process (e.g., SAR/ASR/CST service survey and validation/adjudication).

Planning and engineering process which includes:

Collaborative planning process involving the unit, SC(T), FRHN NOC,

TNOSC, and CCDR J-6.

Detail and accuracy of equipment crew assignment sheets.

Service acquisition process for:

SATCOM.

Baseband.

TNOSC categories:

Service delivery.

Reporting.

Troubleshooting.

Responsiveness.

FIXED REGIONAL HUB NODE TRAINING

I-151. The FRHN personnel will receive new equipment training by the fielding agency. The FRHN

leadership will capitalize on the provided training materials and set up an in-house sustainment training

program to be taught by personnel organic to the organization. Training will be incorporated into the unit’s

mission essential task list. The training program will:

Cover all equipment operations, maintenance, management, and administration tasks.

Provide a matrix/planning schedule that ensures that all training tasks are trained at least

annually.

Identify all training skill level shortcomings.

Provide a training assessment of site personnel and the site overall.

Schedule, conduct, and document any additional or supplemental training, as required.

Make training records available for review during command inspections, performance

evaluations, etc.

I-40

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Glossary

The glossary lists acronyms and terms with Army, multi-service, or joint definitions, and other selected terms.

Where Army and joint definitions are different, (Army) follows the term. Terms for which FM 6-02.71 is the

proponent manual (the authority) are marked with an asterisk (*). The proponent manual for other terms is listed

in parentheses after the definition.

SECTION I - ACRONYMS AND ABBREVIATIONS

A2C2S

Army Airborne Command and Control System

A2TOC

Army Global Network Operations and Security Center and Army Computer

Emergency Response Team Tactical Operations Center

A&VTR

Army asset and vulnerability tracking resource

ABCS

Army Battle Command System

ACERT

Army computer emergency response team

ACES

Automated Communications Engineering Software

ACL

access control list

ACOM

Army Command

active directory

ADCON

administrative control

AEI

Army Enterprise Infrastructure

AENIA

Army enterprise network operations integrated architecture

A-GNOSC

Army global network operations and security center

AIAP

Army Information Assurance Program

AKO

Army Knowledge Online

AOR

area of responsibility

APC

area processing centers

Army regulation

ARFOR

Army forces

ARSTRAT

United States Army Forces Strategic Command

ASA

Army service authorization

ASAS

All Source Analysis System

ASCC

Army Service component command

ASI

authorized service interruption

ASR

Army Service Request

ATC

authority to connect

ATM

asynchronous transfer mode

ATO

authority to operate

BCT

brigade combat team

bde

brigade

BFSB

battlefield surveillance brigade

BFT

Blue Force Tracking

19 November 2008

FM 6-02.71

Glossary-1

FOR OFFICIAL USE ONLY

Glossary

battalion

BOIP

basis of issue plan

BPMN

business process modeling notation

command and control

CC/S/A

combatant commands, services, and agencies

CCB

configuration control board

CCDR

combatant commander

CDRUSSTRATCOM

Commander, United States Strategic Command

CENTCOM

Central Command

CERT

computer emergency response team

Commanding General

configuration item

CIO

chief information officer

CJCS

Chairman of the Joint Chiefs of Staff

CJCSI

Chairman of the Joint Chiefs of Staff instruction

CJCSM

Chairman of the Joint Chiefs of Staff manual

CJTF

commander, joint task force

CJTF-GNO

commander, joint task force-global network operations

configuration management

CMD

command

CMDB

configuration management database

CND

computer network defense

COA

course of action

COCOM

combatant command (command authority)

COMSEC

communications security

CONOPS

concept of operations

CONUS

continental United States

COOP

continuity of operations

command post

CPN

command post node

content staging

CSS

combat service support

CST

commercial satellite team

DAA

designated approval authority

DET

detachment

DCATS

Defense Communications and Army Transmissions System

DHCP

dynamic host configuration protocol

DID

defense in depth

DIACAP

Department of Defense Information Assurance Certification and Accreditation

Process

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Glossary

DIMHRS

Defense Integrated Military Human Resources System

DIRLAUTH

Direct Liaison Authorized

DISA

Defense Information Systems Agency

DISN

Defense Information Systems Network

div

Division

DMAIN

division main

DMZ

demilitarized zone

DNS

domain name service

DOD

Department of Defense

DOD-CERT

Department of Defense Computer Emergency Response Team

DOIM

directorate of information management

DRSN

Defense Red Switch Network

DSN

Defense Switched Network

DTAC

division tactical command post

EHF

extremely high frequency

EIS

Enterprise Information Systems

e-mail

electronic-mail

ENDEX

end of exercise

ENM

Enhanced Position Location Reporting System network manager

EPLRS

Enhanced Position Location Reporting System

ERP

Enterprise Resource Planning

ESB

expeditionary signal battalion

ESM

enterprise systems management

EUCOM

European Command

EUSA

Eighth United States Army

EKMS

Electronic Key Management System

FBCB2

Force XXI Battle Command, Brigade and Below

FCC

functional component commander

FDMA

frequency division multiple access

field manual

FMI

field manual interim

FORSCOM

United States Army Forces Command

FRAGO

fragmentary order

FRHN

fixed regional hub node

FTP

File Transfer Protocol

G-1

assistant chief of staff, personnel

G-2

assistant chief of staff, intelligence

G-3

assistant chief of staff, operations

G-4

assistant chief of staff, logistics

G-6

assistant chief of staff, command, control, communications, and computer

19 November 2008

FM 6-02.71

Glossary-3

FOR OFFICIAL USE ONLY

Glossary

operations

G-7

assistant chief of staff, information operations

GAR

gateway access request

GBS

Global Broadcast Service

GCC

geographic combatant commander

GCM

Global Information Grid content management

GEM

Global Information Grid enterprise management

GIG

Global Information Grid

GISMC

Global Infrastructure Service Management Center

GMF

ground mobile forces

GNC

global network operations center

GNCC

global network operations control center

GND

Global Information Grid network defense

GNO

global network operations

GNOSC

global network operations and security center

GNSC

global network operations support center

GSALT

global command and control system administration log tool

GSSC

global satellite communications support center

HCLOS

high capacity line of sight

headquarters

HTTP

Hypertext Transfer Protocol

HTTPS

Hypertext Transfer Protocol Secure

HSOC

homeland security operations center

information assurance

IAM

information assurance manager

IANM

information assurance network manager

IANO

information assurance network operator

IAPM

information assurance program manager

IASO

information assurance security officer

IATO

interim authority to operate

IAVA

information assurance vulnerability alert

IAVB

information assurance vulnerability bulletin

IAVM

information assurance vulnerability management

IAW

in accordance with

IC-IRC

Intelligence Community-Incident ResponseCenter

ICW

in coordination with

infantry division

IDM

information dissemination management

IDM-T

information dissemination management-tactical

IDS

intrusion detection system

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Glossary

IMCEN

information management center

INFOCON

information operations condition

INMARSAT

international maritime satellite

information operations

IOC

initial operational capability

IO CMD

information operations command

Internet Protocol

IPS

intrusion prevention system

ISDN

Integrated Services Digital Network

ISYSCON

integrated systems control

information technology

ITSB

integrated theater signal battalion

J-2

intelligence directorate of a joint staff; intelligence staff section

J-6

communications system directorate of a joint staff; command, control,

communications, and computer systems staff section

JFCC-NW

Joint Functional Component Command Network Warfare

JFLCC

joint force land component commander

JNCC

joint network operations control center

JNN

joint network node

JNN-N

joint network node-network

JNTC

Joint Network Transport Capability

joint publication

JTA-A

joint technical architecture-Army

JTF

joint task force

JTF-GNO

joint task force-global network operations

JTRS

joint tactical radio system

JTSSNMCCB

Joint Tactical Switched Systems Network Management Configuration Control

Board

LAN

local area network

LIAA

LandWarNet information assurance architecture

LNO

liaison officer

LCMS

Local COMSEC Management Software

LMD/KP

Local Management Device /Key Processor

LOS

line of sight

Log-Net

Logistics-Network

LWN

LandWarNet

MBCOTM

mounted battle command on the move

MBITR

multiband inter/intra team radio

Mbps

megabits per second

MEDCOM

United States Army Medical Command

19 November 2008

FM 6-02.71

Glossary-5

FOR OFFICIAL USE ONLY

Glossary

MIDAS

Multiplexer Integration and Defense Communications Satellite Subsystem

Automation System

MRHN

mobile regional hub node

MSS

Mobile satellite service

MTSS

military training service support

NCC

network control center

NET

network

NETCOM

Network Enterprise Technology Command

NETOPS

network operations

NIDS

network intrusion detection system

NIPR

Non-Secure Internet Protocol Router

NIPRNET

Non-Secure Internet Protocol Router Network

NLT

no later than

network management

NOC

network operations center

NORTHCOM

Northern Command

NOSC

network operations and security center

O&M

operations and maintenance

OCONUS

outside the continental United States

OIF/OEF

Operation Iraqi Freedom/Operation Enduring Freedom

OPCON

operational control

OPORD

operation order

OPSEC

operations security

PACOM

Pacific Command

PBX

private branch exchange

PEO

program executive office

PKE

public key enabled

PKI

public key infrastructure

program manager

PM DCATS

Program Manager-Defense Communications and Army Transmissions System

RADIUS

remote authentication dial-in user server

RCERT

regional computer emergency response team

RCIO

regional chief information officer

RFS

request for service

RHN

regional hub node

RNOSC

regional network operations and security center

RSSC

regional satellite support center

S-2

intelligence staff officer

S-3

operations staff officer

S-6

command, control, communications, and computer operations

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Glossary

situational awareness

SAA

satellite access authorization

SAR

satellite access request

SATCOM

satellite communications

SBDE

support brigade

SB(T)

signal brigade (tactical)

SC(A)

signal command (Army)

SC(T)

signal command (theater)

SECDEF

Secretary of Defense

SGNOSC

service global network operations and security center

SIGOPS

signal operations

SINCGARS

single-channel ground and airborne radio system

SIPR

SECRET Internet Protocol Router

SIPRNET

SECRET Internet Protocol Router Network

SLA

service level agreement

SMART-T

Secure Mobile Antijam Reliable Tactical Terminal

SMTP

Simple Mail Transfer Protocol

SNMP

Simple Network Management Protocol

SOP

standing operating procedure

SOUTHCOM

Southern Command

SSIO

system integration oversight

STB

special troops battalion

STEP

standard tactical entry point

STIG

security technical implementation guide

STNOSC

Service theater network operations and security center

SVCS

services

TAC

tactical

TACLANE

tactical local area network encryptor

TACON

tactical control

TDMA

time division multiple access

THN

tactical hub node

THSDN

tactical high speed data network

TIC

tactical integration cell

TJTNCCB

Theater Joint Tactical Network Configuration Control Board

TLT

tactical liaison team

TNC

theater network operations center

TNCC

theater network operations control center

TNOSC

theater network operations and security center

TNT

tactical network team

TOC

tactical operations center

19 November 2008

FM 6-02.71

Glossary-7

FOR OFFICIAL USE ONLY

Glossary

Transmission plan

TRADOC

United States Army Training and Doctrine Command

TRCS

tactical radio communications systems

Trojan SPIRIT

Trojan special purpose integrated remote intelligence terminal

TSO

telecommunications service order

TS/SCI

top secret/sensitive compartmented information

UHF

ultrahigh frequency

UHN

unit hub node

United States

USARCENT

United States Army, Central

USAREUR

United States Army, Europe

USARPAC

United States Army, Pacific

USASC&FG

United States Army Signal Center and Fort Gordon

USARSO

United Stated Army, South

USASMDC

United States Army Space and Missile Defense Command

USCENTCOM

United States Central Command

USEUCOM

United States European Command

USJFCOM

United States Joint Forces Command

USMC

United States Marine Corps

USNORTHCOM

United States Northern Command

USPACOM

United States Pacific Command

USSOCOM

United States Special Operations Command

USSOUTHCOM

United States Southern Command

USSTRATCOM

United States Strategic Command

VOIP

Voice over Internet Protocol

VPN

virtual private network

WAN

wide area network

WATCHCON

watch condition

WIN-T

Warfighter Information Network-Tactical

WISC

warfighter integration and support cell

SECTION II - TERMS

ARFOR

(Army) The senior Army headquarters and all Army forces assigned or attached to a combatant

command, subordinate joint force command, joint functional command, or multinational command.

(FM 3-0)

combatant command (command authority)

(joint) Nontransferable command authority established by Title 10 (―Armed Forces‖), United States

Code, Section 164, exercised only by commanders of unified or specified combatant commands unless

otherwise directed by the President or the Secretary of Defense. Combatant command (command

authority) cannot be delegated and is the authority of a combatant commander to perform those

functions of command over assigned forces involving organizing and employing commands and forces,

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Glossary

assigning tasks, designating objectives, and giving authoritative direction over all aspects of military

operations, joint training, and logistics necessary to accomplish the missions assigned to the command.

Combatant command (command authority) should be exercised through the commanders of subordinate

organizations. Normally this authority is exercised through subordinate joint force commanders and

Service and/or functional component commanders. Combatant command (command authority)

provides full authority to organize and employ commands and forces as the combatant commander

considers necessary to accomplish assigned missions. Operational control is inherent in combatant

command (command authority). (JP 1-02)

computer network defense

(joint) Actions taken through computer networks to protect, monitor, analyze, detect and respond to

unauthorized activity within Department of Defense information systems and computer networks. (JP

6-0)

Global Information Grid

(joint) The globally interconnected, end-to-end set of information capabilities, associated processes and

personnel for collecting, processing, storing, disseminating, and managing information in demand to

warfighters, policy makers, and support personnel. The Global Information Grid includes owned and

leased communications and computing systems and services, software (including applications), data,

security services, other associated services and National Security Systems. (JP 6-0)

information assurance

(joint) Measures that protect and defend information and information systems by ensuring their

availability, integrity, authentication, confidentiality, and nonrepudiation. This includes providing for

restoration of information systems by incorporating protection, detection, and reaction capabilities. (JP

3-13)

information superiority

(joint) The operational advantage derived from the ability to collect, process, and disseminate an

uninterrupted flow of information while exploiting or denying an adversary’s ability to do the same. (JP

3-13)

*LandWarNet

The Army’s portion of the GIG.

local area network

A data communications system that (a) lies within a limited spatial area, (b) has a specific user group,

connected to one. Note 1: LANs are usually restricted to relatively small areas, such as rooms,

buildings, ships, and aircraft. Note 2: An interconnection of LANs within a limited geographical area,

such as a military base, is commonly referred to as a campus area network. An interconnection of

LANs over a city-wide geographical area is commonly called a metropolitan area network. An

interconnection of LANs over large geographical areas, such as nationwide, is commonly called a wide

area network. Note 3: LANs are not subject to public telecommunications regulations. (Federal

Standard 1037C)

metropolitan area network

A data communications network that (a) covers an area larger than a campus area network and smaller

than a wide area network (WAN), (b) interconnects two or more LANs, and (c) usually covers an entire

metropolitan area, such as a large city and its suburbs. (Federal Standard 1037C)

network operations

(joint) Activities conducted to operate and defend the Global Information Grid. (JP 6-0)

operational control

(joint) Command authority that may be exercised by commanders at any echelon at or below the level

of combatant command. Operational control is inherent in combatant command (command authority)

19 November 2008

FM 6-02.71

Glossary-9

FOR OFFICIAL USE ONLY

Glossary

and may be delegated within the command. When forces are transferred between combatant commands,

the command relationship the gaining commander will exercise (and the losing commander will

relinquish) over these forces must be specified by the Secretary of Defense. Operational control is the

authority to perform those functions of command over subordinate forces involving organizing and

employing commands and forces, assigning tasks, designating objectives, and giving authoritative

direction necessary to accomplish the mission. Operational control includes authoritative direction over

all aspects of military operations and joint training necessary to accomplish the missions assigned to the

command. Operational control should be exercised through the commanders of subordinate

organizations. Normally this authority is exercised through subordinate joint force commanders and

Service and/or functional component commanders. Operational control normally provides full authority

to organize commands and forces and to employ those forces as the commander in operational control

considers necessary to accomplish assigned missions; it does not, in and of itself, include authoritative

direction for logistics or matters of administration, discipline, internal organization, or unit training. (JP

1-02)

tactical control

(DOD) Command authority over assigned or attached forces or commands, or military capability or

forces made available for tasking, that is limited to the detailed direction and control of movements or

maneuvers within the operational area necessary to accomplish missions or tasks assigned. Tactical

control is inherent in operational control. Tactical control may be delegated to, and exercised at any

level at or below the level of combatant command. When forces are transferred between combatant

commands, the command relationship the gaining commander will exercise (and the losing commander

will relinquish) over these forces must be specified by the Secretary of Defense. Tactical control

provides sufficient authority for controlling and directing the application of force or tactical use of

combat support assets within the assigned mission or task. (JP 1-02)

*technical channels

Technical channels provides commanders with the means to rapidly employ or modify functional

capabilities for mission requirements. It enables the timely implementation of techniques, procedures,

standards, configurations, and designs in support of operations at all levels. Technical channels neither

constitutes nor bypasses command authority, but serves as the mechanism for ensuring the execution of

clearly delineated technical tasks, functions, and capabilities to meet the dynamic requirements of full

spectrum operations. The orders process will delineate the appropriate authorities required to

implement functional capabilities from Army down to the lowest echelons of command through the use

of technical channels.

wide area network

A physical or logical network that provides data communications to a larger number of independent

users than are usually served by a local area network and is usually spread over a larger geographic

area than that of a LAN. Note 1: WANs may include physical networks, such as Integrated Services

Digital Networks, X.25 networks, and T1 networks. Note 2: A metropolitan area network is a WAN

that serves all the users in a metropolitan area. WANs may be nationwide or worldwide. (Federal

Standard 1037C)

Wireless Personal Area Network

A system that provides electromagnetic communication connectivity over a few yards. Currently it uses

either RF (e.g., Bluetooth) or IR technology. (DOD Directive 8100.2)

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

References

SOURCES USED

These are the sources quoted or paraphrased in this publication.

ARMY PUBLICATIONS

AR 10-87. Army Commands, Army Service Component Commands, and Direct Reporting Units. 04

September 2007.

AR 25-1. Army Knowledge Management and Information Technology. 15 July 2005.

AR 25-2. Information Assurance. 24 October 2007.

AR 25-6. Military Affiliate Radio System (Mars) and Amateur Radio Program. 01 May 2007.

AR 380-5. Department of the Army Information Security Program. 29 September 2000.

AR 380-40. Policy for Safeguarding and Controlling Communications Security (COMSEC) Materiel.

30 June 2000.

AR 380-53. Information Systems Security Monitoring. 29 April 1998.

AR 500-3. U.S. Army Continuity of Operations (COOP) Program Policy and Planning. 12 April 2006.

Bronson, J. and Knight, L. CIO/G6 White Paper v6.5. Army’s Adjusted Teleport Gen II Satellite

Communications (SATCOM) Circuit-switched and Internet Protocol (IP) Requirements. 11

August 2006.

FM 3-0. Operations. 27 February 2008.

FM 3-13. Information Operations: Doctrine, Tactics, Techniques, and Procedures. 28 November

2003.

FM 3-21.21. The Stryker Brigade Combat Team Infantry Battalion. 8 April 2003.

FM 5-19. Composite Risk Management. 21 August 2006.

FM 6-0. Mission Command: Command and Control of Army Forces. 11 August 2003.

FMI 5-0.1. The Operations Process (with change 1). 31 March 2006.

FMI 6-02.45. Signal Support to Theater Operations. 05 July 2007.

FMI 6-02.60. Tactics, Techniques, and Procedures (TTPs) for the Joint Network Node-Network (JNN-

N). 05 September 2006.

FMI 6-02.70. Army Electromagnetic Spectrum Management Operations. 05 September 2006.

NETCOM. Fixed Regional Hub Node (FRHN) Operations and Control (O&C) Plan. Version 1.3. 17

July 2007

Technical Bulletin 380-41. Security: Procedures for Safeguarding, Accounting, and Supply Control of

COMSEC Material. 16 June 2006. (Current as of 16 June 2006.)

US Army Chief Information Officer/G-6. Army Network Operations Concept of Operations (version

1.0).

US Army Chief Information Officer/G-6 Policy Memorandum. Enterprise Network Operations

Integrated Architecture Implementation. 24 April 06.

US Army Chief Information Officer/G-6 White Paper. Fight the Network. 08 September 2004.

US Army Office of Information Assurance and Compliance. Army Password Standards. Version 2.5. 1

MAY 08

19 November 2008

FM 6-02.71

Reference-1

FOR OFFICIAL USE ONLY

References

JOINT PUBLICATIONS

Chairman of the Joint Chiefs of Staff, Director for Strategic Plans and Policy, J-5, Strategy Division.

Joint Vision 2020. September 2000.

CJCSI 6211.02B. Defense Information System Network: Policy, Responsibilities and Processes. 31

July 2003.

CJCSI 6215.01C. Policy for Department of Defense Voice Networks with Real Time Service. 09

November 2007.

CJCSI 6510.01E. Information Assurance (IA) and Computer Network Defense (CND. 15 August 2007

CJCSM 6231.01C. Manual for Employing Joint Tactical Communications Joint Systems Management.

21 June 2007.

CJCSM 6231.07D. Manual for Employment of Joint Tactical Communications-Joint Network

Management and Control. 24 October 2007.

CJCSM 6510.01. Defense-in-Depth: Information Assurance (IA) and Computer Network Defense

(CND). 14 March 2007.

Defense Information Systems Agency (DISA). Global Contingency and Exercise Planning (CONEX)

Guide. January 2003.

Department of the Army Pamphlet 25-1-2. Information Technology Contingency Planning. 16

November 2006.

Department of Defense Directive 8100.02. Use Of Commercial Wireless Devices, Services, And

Technologies In The Department Of Defense (DOD) Global Information Grid (GIG). 14 April

2004.

JP 1-02. Department of Defense Dictionary of Military and Associated Terms. 12 April 2001.

JP 3-0. Joint Operations. 17 September 2006.

JP 3-13. Information Operations.13 February 2006.

JP 5-0. Joint Operation Planning. 26 December 2006.

JP 6-0. Joint Communications System. 20 March 2006.

Strategic Command Directive (SD) 527-1. DOD Information Operations Condition (INFOCON)

System Procedures. 27 January 2006.

United States Strategic Command. Joint Concept of Operations for Global Information Grid NetOps.

04 August 2006.

United States. Unified Command Plan 2002.

United States. Unified Command Plan 2004. March 2005

DOCUMENTS NEEDED

These documents must be available to the intended users of this publication.

DA Form 2028. Recommended Changes to Publications and Blank Forms. February 1974.

Business Process Modeling Notation (version 1.0 specification). May 2004.

READINGS RECOMMENDED

These sources contain relevant supplemental information.

CJCSM 3122.01A. Joint Operation Planning and Execution System (JOPES., Volume I. 29 September

2006.

CJCSM 3122.03B. Joint Operation Planning and Execution System (JOPES., Volume II. 28 February

2006.

CJCSM 3150.16A. Joint Operation Planning and Execution System Reporting Structure (JOPESREP).

29 September 2000.

CJCSM 3320.01B. Joint Operations in the Electromagnetic Battlespace. 25 March 2006.

References-2

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Index

2-14, 2-17, 2-20, 2-21, 2-22,

authority to connect, iv, I-24, I-

2-26, 2-27, 4-9, 5-4, 5-11, 5-

27, I-28, I-29, I-33, I-36

active directory, iii, v, 1-14, 2-

26, C-7, C-8, C-14, C-17

authority to operate, iv, A-13, I-

33, 3-7, 4-18, 5-22, A-1, A-2,

Army Information Assurance

24, I-27, I-28, I-29, I-30, I-33,

A-3, A-4, A-5, A-6, A-7, A-8,

Program, 2-5, 2-19

I-36, I-39

A-9, A-10, A-11, A-12, A-13,

Army Service component

A-14, A-15, A-23, F-2, F-8,

command, 2-19, 3-4, 3-6, 3-

F-13, F-14, F-15

9, 3-11, 3-13, 3-16, 3-17, 4-

Blue Force Tracking, B-12, B-

area processing centers, 4-18,

3, 4-9, 4-23, 5-4, D-3, D-5,

I-1, I-2, I-5, I-16, I-17

D-6, D-7, H-1, H-3, I-9, I-10,

brigade combat team, iii, iv, 2-

Army asset and vulnerability

I-25, I-28, I-29, I-30, I-31, I-

1, 2-2, 2-16, 2-25, 2-26, 2-

tracking resource, 2-28, 2-

32, I-34, I-37, I-38, I-39, I-40,

33, 3-1, 3-4, 3-15, 3-17, 3-

29, F-19, F-20, F-21, F-22,

I-45, I-46, I-47

18, 3-19, 3-21, 4-20, 4-23, 4-

F-23

Army Service Request, iv, I-25,

24, 5-3, 5-5, 5-6, 5-9, 5-10,

Army Battle Command

I-28, I-29, I-30, I-31, I-32, I-

5-11, 5-12, 5-13, 5-14, 5-15,

System, B-12, B-13, B-16,

33, I-34, I-35, I-36, I-37, I-39,

5-16, 5-17, 5-18, 5-19, 5-21,

B-17, B-18, I-17

I-46, I-47

5-22, 5-23, 5-27, 5-29, 5-30,

Army Command, 2-23, 3-12

assistant chief of staff,

A-14, A-23, C-4, C-5, C-8,

command, control,

C-10, C-11, C-12, C-14, C-

Army computer emergency

communications, and

15, C-17, C-18, D-4, D-6, E-

response team, 2-21, 2-22,

1, F-20, G-1, G-2, G-3, G-4,

computer operations, ii, iii,

2-29, 4-8, 4-9, F-16, F-23

H-1, I-3, I-6, I-19, I-21, I-25,

1-3, 1-13, 2-19, 2-21, 2-25,

Army Enterprise Infrastructure,

I-37

2-26, 2-27, 2-28, 3-4, 3-5, 3-

A-4, A-7, A-10, A-12, A-13,

9, 3-13, 3-14, 3-15, 3-16, 3-

business process modeling

A-14, B-1, F-18

17, 3-18, 3-19, 3-20, 3-22, 4-

notation, iii, C-1, C-2, C-3

Army enterprise network

15, 4-18, 4-19, 4-21, 4-22, 4-

operations integrated

23, 4-24, 5-2, 5-3, 5-4, 5-5,

architecture, 1-3, 1-13, 1-14,

5-6, 5-7, 5-10, 5-12, 5-13, 5-

Chairman of the Joint Chiefs of

3-10, 5-1, B-1, B-3, B-5, B-7,

14, 5-15, 5-16, 5-17, 5-19, 5-

Staff, 3-2, 4-10, H-1

B-9, C-1

20, 5-22, 5-23, 5-26, 5-27,

Chairman of the Joint Chiefs of

Army forces, 3-4, 3-5, 3-9, 3-

A-4, A-13, A-14, A-15, B-12,

Staff instruction, 2-13, 2-23,

11, 4-15, 4-17, 4-23, 4-24, 5-

C-4, C-5, C-8, C-10, C-11,

2-27, I-27

4, 5-7, 5-10, 5-11, 5-12, 5-

C-14, C-15, C-18, D-1, D-2,

Chairman of the Joint Chiefs of

D-3, D-4, D-5, D-6, D-7, F-6,

13, 5-14, 5-15, 5-16, 5-17, 5-

Staff manual, 2-10, 3-4

F-15, F-16, F-18, F-20, G-4,

18, 5-19, 5-20, 5-21, 5-22, 5-

H-3, I-1, I-2, I-6, I-8, I-10, I-

chief information officer, 1-3, 1-

23, 5-27, 5-28, 5-29, 5-30,

C-4, C-5, C-7, C-8, C-10, C-

11, I-17, I-18, I-21, I-22, I-28,

13, 2-19, 2-21, 2-26, 2-29, 3-

12, C-14, C-15, C-18, C-19,

I-29, I-34

5, 5-2, 5-8, A-4, A-11, A-13,

A-14, C-14, F-6, F-15, F-16,

D-5, D-7, G-1, G-2, H-2

assistant chief of staff,

F-23, I-1, I-2, I-11, I-28

information operations, D-5

Army global network

combatant command

operations and security

assistant chief of staff,

center, v, 2-14, 2-21, 2-22,

intelligence, iv, 2-24, 3-5, 3-

(command authority), 2-17

2-27, 2-29, 3-7, 3-8, 4-1, 4-

16, D-5, G-3, G-4

combatant commander, 2-16,

3, 4-8, 4-9, 4-13, 4-14, 5-7,

3-2, 3-3, 3-4, 3-8, 3-9, 4-1,

assistant chief of staff,

5-8, 5-9, 5-10, 5-11, 5-12, 5-

4-2, 4-3, 4-6, 4-8, 4-10, 4-

logistics, iv

15, 5-20, 5-29, 5-30, A-3, A-

11, 4-12, 4-13, 4-14, 4-15, 4-

assistant chief of staff,

6, A-9, A-10, A-11, A-12, B-

16, 5-8, 5-11, 5-20, 5-29, A-

operations, iv, 4-19, 4-23, 4-

1, B-3, B-5, B-7, B-9, F-16,

4, C-18, G-1, G-2, H-1, I-1, I-

24, D-1, D-3, D-4, D-5, D-6,

F-23, I-2, I-17, I-19, I-22, I-

30, I-31, I-32, I-33, I-34, I-42,

G-5, I-28

23, I-39, I-42

I-45, I-46, I-47

assistant chief of staff,

Army Global Network

combatant commands,

personnel, ii, iv, D-6, G-2, G-

Operations and Security

services, and agencies, 2-

3, I-20, I-38

Center and Army Computer

17, 4-2, 4-5, 4-6, 4-7

Emergency Response Team

asynchronous transfer mode,

command post, D-8

Tactical Operations Center,

4-19, 4-20

19 November 2008

FM 6-02.71

Index-1

FOR OFFICIAL USE ONLY

Index

command post node, 3-12, I-8,

configuration control board, 1-

I-12, I-25, I-26, I-27, I-34, I-

I-33

3, 4-18, A-4, A-7, A-10, A-

12, A-13

command, control,

Department of Defense, 1-1, 1-

communications, and

configuration item, 5-12, 5-13,

2, 1-3, 1-13, 2-6, 2-7, 2-10,

computer operations, ii, 2-

5-14

2-13, 2-14, 2-16, 2-17, 2-19,

25, 2-27, 2-28, 3-4, 3-13, 3-

2-27, 2-28, 2-31, 3-1, 3-2, 3-

configuration management, 1-

15, 3-17, 3-18, 3-19, 3-20, 3-

3, 3-6, 3-7, 3-12, 4-1, 4-4, 4-

6, 1-14, 2-3, 2-33, 3-5, 3-7,

21, 3-22, 4-24, 5-3, 5-4, 5-5,

6, 4-7, 4-8, 4-10, 4-12, 4-14,

3-16, 4-2, 4-18, 4-19, 4-24,

5-6, 5-7, 5-10, 5-11, 5-12, 5-

5-8, B-1, B-2, B-3, B-5, B-7,

5-2, 5-11, 5-12, 5-13, 5-14,

13, 5-14, 5-15, 5-16, 5-18, 5-

B-9, B-17, F-2, F-13, F-14,

5-26, A-6, A-8, A-9, A-12, B-

27, A-15, B-12, C-4, C-5, C-

F-15, F-19, F-20, F-21, F-22,

1, B-3, B-16, C-3, C-7, C-10,

8, C-10, C-11, C-12, C-14,

F-22, I-3, I-5, I-6, I-8, I-9, I-

C-15, D-5, F-16, F-18, I-38,

C-17, C-18, E-1, F-20, G-1,

11, I-18, I-24, I-26, I-27, I-29,

I-44

G-2, H-1, I-6, I-8, I-10, I-17,

I-34

configuration management

I-18, I-21, I-22, I-29, I-34

Department of Defense

database, I-44

communications system

Computer Emergency

content staging, 1-4, 1-5, 1-11,

directorate of a joint staff, 3-

Response Team, 2-17, 2-27

1-12, 2-1, 2-30, 2-31, 2-32,

2, 3-3, 3-4, 3-9, 3-15, 3-16,

Department of Defense

2-33, 2-34, 3-2, 3-19, 4-9, 4-

3-17, 3-18, 4-24, 5-3, 5-4, 5-

Information Assurance

14, 4-17, 4-18, 4-22, 4-23,

5, 5-6, 5-7, 5-10, 5-12, 5-13,

Certification and

A-17, A-20, A-21, A-23, B-1,

5-14, 5-16, D-5, G-2, H-1, H-

Accreditation Process, I-24

D-7

2, I-8, I-10, I-18, I-21, I-33, I-

designated approval authority,

continental United States, iv, 2-

A-8, I-24, I-27, I-29, I-30, I-

9, 3-6, 3-7, 3-10, 3-13, 4-7,

commander, joint task force, 2-

A-1, A-3, A-11, A-14, H-1, H-

18, 3-1, 3-4, 3-8, 4-3, 4-5, 4-

2, I-3, I-4, I-5, I-6, I-7, I-30, I-

directorate of information

6, 5-12, 5-14, 5-15, 5-16, 5-

management, 2-22, 2-29, 2-

17, 5-20, 5-22, 5-23, 5-27

32, 2-33, 3-8, 3-12, A-1, A-6,

continuity of operations, iv, 2-

commander, joint task force-

A-8, A-9, A-11, A-13, F-2, F-

10, 2-16, 2-30, 3-8, 4-20, A-

global network operations,

15, F-17, F-20, F-23

13, B-14, I-3, I-16, I-46

2-18, 3-1, 4-3, 4-5, 4-6

domain name service, 2-33, 3-

course of action, 4-4, 4-6, 4-24

Commander, United States

7, 4-18, 4-19, 5-21, 5-22, A-

Strategic Command, 1-2, 2-

3, A-4, A-7, A-8, A-10, A-13,

16, 2-17, 2-18, 3-1, 4-2, 4-3,

A-14, A-15, F-3, F-8, I-17

Defense Communications and

4-4, 4-5, 4-9, 4-10

Army Transmissions

dynamic host configuration

Commanding General, 2-19, 3-

System, I-4, I-27, I-44

protocol, 5-22, A-3, A-4, A-8

defense in depth, 1-10, 2-4, 2-

communications security, 1-10,

5, 2-6, 4-20, 5-22, F-1, F-2,

2-5, 2-11, 2-12, 2-13, 2-14,

electronic-mail, vii, 1-14, 2-12,

F-18

2-23, 2-30, 3-3, 4-19, 4-22,

2-13, 2-32, 2-33, 2-34, 3-8,

Defense Information Systems

B-14, B-15, B-16, D-2, D-7,

3-10, 5-29, A-6, A-7, B-17,

Agency, 2-10, 2-17, 2-19, 2-

I-36, I-37, I-38, I-39, I-43

D-4, F-3, F-7, F-8, F-10, F-

33, 3-3, 3-5, 3-6, 3-7, 4-19,

computer emergency response

14, G-1, G-3

4-20, 5-28, B-2, B-3, B-5, F-

team, 2-17, 2-22, 2-23, 2-27,

Enhanced Position Location

15, F-16, F-17, F-21, G-3, I-

2-29, F-23

Reporting System, B-12, B-

3, I-10, I-11, I-12, I-18, I-19,

computer network defense, v,

I-21, I-25, I-27, I-28, I-29, I-

1-4, 1-5, 1-8, 1-9, 1-10, 1-

30, I-34, I-35, I-38, I-42

Enhanced Position Location

11, 1-13, 2-1, 2-5, 2-6, 2-7,

Reporting System network

Defense Information Systems

2-17, 2-18, 2-19, 2-21, 2-22,

manager, B-12

Network, iv, 3-14, A-10, A-

3-1, 3-2, 3-6, 3-13, 3-21, 4-

14, B-4, F-2, F-3, F-4, F-5,

enterprise systems

4, 4-5, 4-6, 4-7, 4-9, 4-14, 4-

F-6, F-7, F-8, G-2, H-2, I-3,

management, 1-4, 1-5, 1-6,

22, 4-23, A-3, A-6, A-8, A-9,

I-4, I-5, I-8, I-9, I-12, I-23, I-

1-7, 1-8, 2-1, 2-2, 2-3, 2-4,

B-1, B-2, B-3, B-5, B-7, B-9,

25, I-26, I-27, I-28, I-29, I-33,

3-7, 3-10, 3-21, 4-9, 4-14, 4-

B-15, D-2, D-7, F-1, F-2, F-

I-34, I-35, I-43

22, B-1, B-10, I-6, I-20, I-21

3, F-10, F-11, F-13, F-14, F-

Defense Red Switch Network,

expeditionary signal battalion,

15, F-16, F-17, I-6, I-14

4-19, I-8, I-9, I-25, I-26, I-27,

3-11, 3-12, 3-14, 3-17, 4-21,

concept of operations, 3-2, 4-5,

I-34, I-44

5-7, 5-10, 5-11, 5-12, 5-13,

5-8, A-9, A-10, A-11, A-12,

5-14, 5-15, 5-16, 5-17, 5-18,

Defense Switched Network, 3-

C-1

5-19, 5-20, 5-21, 5-23, 5-26,

10, 4-19, A-15, B-1, I-8, I-9,

Index-2

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Index

D-3, H-2, H-3, I-4, I-10, I-11,

global network operations, 1-

information assurance network

I-12, I-25, I-29, I-37

10, 2-17, 2-18, 2-19, 2-21, 2-

manager, v, 2-14, 2-19, 2-

22, 2-27, 2-32, 3-1, 3-3, 3-6,

20, 2-23, 2-24, 2-25, 2-26, 2-

3-21, 4-1, 4-2, 4-3, 4-4, 4-5,

27, F-19, F-20

File Transfer Protocol, F-3, F-

4-6, 4-7, 4-8, 4-9, 4-10, 4-

information assurance network

7, F-8, I-16

12, 4-13

operator, v, F-19, F-20

fixed regional hub node, iv, E-

global network operations and

information assurance program

1, I-1, I-2, I-3, I-4, I-5, I-6, I-

security center, 2-14, 2-19,

manager, 2-19, 2-20, 2-23,

7, I-8, I-9, I-10, I-11, I-12, I-

2-21, 2-22, 2-27, 2-29, 3-7,

2-24

13, I-14, I-15, I-16, I-17, I-18,

3-8, 4-1, 4-3, 4-8, 4-9, 4-13,

information assurance security

I-19, I-20, I-21, I-22, I-23, I-

4-15, 5-7, 5-8, 5-9, 5-10, 5-

officer, v, 2-14, 2-15, 2-16,

24, I-25, I-26, I-27, I-28, I-29,

11, 5-12, 5-15, 5-20, 5-29, 5-

2-19, 2-20, 2-22, 2-23, 2-24,

I-31, I-33, I-34, I-35, I-36, I-

30, A-3, A-7, A-10, A-11, A-

2-25, 2-26, 2-27, 2-28, 2-29,

37, I-38, I-39, I-40, I-41, I-42,

12, B-1, B-3, B-5, B-7, B-9,

F-20, F-21, F-23

I-43, I-44, I-45, I-46, I-47

F-16, F-23, I-2, I-17, I-19, I-

22, I-23, I-39, I-42

information assurance

Force XXI Battle Command,

vulnerability alert, 2-27, 2-

Brigade and Below, B-12, B-

global network operations

29, 4-20, 4-23, 5-29, A-10,

center, 3-2, 4-2, 4-5, 4-6, 4-

A-12, A-13, F-22, F-23, F-24

7, 4-8

fragmentary order, 4-23, 4-24,

information assurance

B-14, D-1, I-34

global network operations

vulnerability management,

control center, 4-8, 4-13, 4-

frequency division multiple

1-14, 2-18, 2-21, 2-23, 2-24,

14, 4-15

access, D-8, G-2, G-3, I-3, I-

2-27, 2-28, 2-29, 2-30, 3-1,

4, I-9, I-10, I-11, I-12, I-18, I-

global network operations

3-14, 5-26, F-22, F-24, I-42

19, I-25, I-38, I-43, I-45

support center, 2-2, 4-7, 4-8

information dissemination

functional component

global satellite communications

management, 1-4, 1-5, 1-11,

commander, 4-5

support center, 4-6, I-28, I-

1-12, 2-1, 2-30, 2-31, 2-32,

32, I-33, I-34

2-33, 2-34, 2-35, 3-2, 3-7, 3-

8, 3-9, 3-19, 3-21, 4-9, 4-14,

gateway access request, I-28,

4-17, 4-18, 4-22, 4-23, A-6,

I-29, I-34

Hypertext Transfer Protocol, B-

A-7, B-1, B-17, D-1, D-2, D-

17, F-3, F-4, F-7, F-8

geographic combatant

3, D-7

commander, 3-3, 4-5, 4-11,

Hypertext Transfer Protocol

information dissemination

4-12, 4-24, I-10, I-18, I-21

Secure, B-17, F-3, F-4, F-7,

management-tactical, A-6,

GIG, 1-1

F-8

A-7, B-17

global command and control

information operations, 2-4, 2-

system administration log

7, 2-9, 2-16, 2-17, 2-20, 2-

infantry division, A-23

tool, B-17, B-18

21, 2-22, 2-23, 2-24, 3-5, 3-

information assurance, iii, v, 1-

16, 3-18, 4-4, 4-9, 5-22

Global Information Grid, 1-1, 1-

4, 1-5, 1-8, 1-9, 1-10, 1-11,

2, 1-3, 1-4, 2-2, 2-7, 2-13, 2-

information operations

1-13, 2-1, 2-4, 2-5, 2-6, 2-7,

17, 2-18, 2-22, 2-31, 2-32, 2-

command, 2-20, 2-21, 2-22,

2-9, 2-10, 2-11, 2-13, 2-16,

34, 3-1, 3-2, 3-3, 3-4, 3-5, 3-

4-9

2-17, 2-19, 2-21, 2-22, 2-23,

6, 3-8, 3-15, 3-16, 3-18, 3-

information operations

2-24, 2-25, 2-26, 2-28, 2-29,

19, 4-1, 4-2, 4-3, 4-4, 4-5, 4-

condition, 2-14, 2-18, 2-24,

2-30, 3-2, 3-3, 3-5, 3-6, 3-7,

6, 4-7, 4-8, 4-9, 4-10, 4-11,

3-2, 4-5, F-18

3-8, 3-9, 3-10, 3-12, 3-14, 3-

4-12, 4-13, 4-14, 4-15, 4-16,

16, 3-17, 3-19, 3-21, 4-9, 4-

information superiority, 1-1

4-24, 5-8, 5-28, B-15, D-1,

14, 4-20, 4-22, 4-23, 5-1, 5-

D-3, D-6, D-8, F-2, G-3, G-5,

information technology, 1-6, 1-

22, 5-24, 5-25, 5-26, 5-27,

I-4, I-8, I-26, I-27

7, 1-13, 2-2, 2-7, 2-14, 2-17,

B-1, B-15, D-1, D-2, D-3, D-

2-32, 2-34, 3-6, 3-13, 3-14,

Global Information Grid content

5, D-7, E-1, F-1, F-2, F-13,

3-15, 4-9, 5-5, 5-17, 5-27, A-

management, 1-4, 2-31, 4-1,

F-14, F-15, F-16, F-17, F-18,

1, A-7, A-8, A-9, A-10, A-11,

4-2, 4-3, 4-13

F-19, F-20, F-21, F-22, F-22,

A-12, A-13, B-5, D-4, F-18,

Global Information Grid

F-23, H-2, I-6, I-8, I-9, I-12,

F-19, F-20

enterprise management, 1-

I-13, I-14, I-15, I-21, I-37, I-

initial operational capability, iv,

4, 4-1, 4-3

38, I-39, I-42

I-16, I-25, I-27, I-28

Global Information Grid

information assurance

integrated systems control, 3-

network defense, 1-4, 2-22,

manager, v, 2-14, 2-16, 2-

10, B-12, B-13, B-14, B-15

3-3, 4-1, 4-2, 4-3, 4-6, 4-7,

19, 2-20, 2-22, 2-23, 2-24, 2-

4-13, 4-14

25, 2-27, 2-29, F-18, F-19,

integrated theater signal

F-20, F-21, F-24

battalion, 3-4, 3-11, 3-14, 3-

19 November 2008

FM 6-02.71

Index-3

FOR OFFICIAL USE ONLY

Index

17, 4-21, 5-7, 5-10, 5-11, 5-

13, 4-16, 4-24, 5-10, 5-17, 5-

network operations, iii, iv, v, 1-

12, 5-13, 5-14, 5-15, 5-16, 5-

22, 5-27, 5-30, D-3, D-4, D-

1, 1-2, 1-4, 1-5, 1-6, 1-7, 1-

17, 5-18, 5-19, 5-20, 5-21, 5-

5, D-6, D-7, F-2, G-1, G-3,

9, 1-12, 1-13, 1-14, 2-1, 2-2,

23, 5-26, 5-27, 5-28, D-3, H-

H-1, H-3, I-8, I-10, I-18, I-19,

2-3, 2-5, 2-14, 2-15, 2-17, 2-

2, H-3, I-3, I-4, I-10, I-11, I-

I-29, I-31, I-42

18, 2-19, 2-21, 2-24, 2-26, 2-

30, 2-31, 2-32, 3-1, 3-2, 3-3,

joint task force-global network

3-4, 3-5, 3-6, 3-7, 3-8, 3-9,

intelligence staff officer, 2-24,

operations, 1-10, 2-17, 2-19,

3-10, 3-11, 3-12, 3-13, 3-14,

2-25, 3-18

2-21, 2-22, 2-27, 2-31, 3-3,

3-16, 3-17, 3-18, 3-19, 3-20,

3-6, 3-21, 4-1, 4-2, 4-3, 4-4,

intelligence directorate of a

3-21, 3-22, 3-23, 4-1, 4-2, 4-

4-5, 4-7, 4-8, 4-9, 4-10, 4-

joint staff, 4-5

3, 4-4, 4-5, 4-6, 4-7, 4-8, 4-

12, 4-13

interim authority to operate, I-

9, 4-10, 4-11, 4-12, 4-13, 4-

joint technical architecture-

30, I-33, I-36, I-39

14, 4-15, 4-16, 4-17, 4-18, 4-

Army, 1-3, 3-6

Internet Protocol, 1-13, 1-14, 2-

19, 4-20, 4-21, 4-22, 4-23, 4-

12, 4-19, 5-20, 5-22, A-3, A-

24, 5-1, 5-2, 5-3, 5-4, 5-5, 5-

15, B-5, B-9, B-10, B-18, F-

6, 5-7, 5-8, 5-9, 5-10, 5-11,

LandWarNet, 1-1, 1-3, 1-4, 1-

7, F-8, F-10, F-12, I-8, I-9, I-

5-12, 5-13, 5-14, 5-15, 5-16,

5, 1-6, 1-7, 1-8, 1-10, 1-11,

11, I-12, I-26, I-27, I-29, I-40,

5-17, 5-18, 5-19, 5-20, 5-21,

1-12, 1-13, 2-3, 2-4, 2-5, 2-

I-44

5-22, 5-23, 5-24, 5-25, 5-26,

7, 2-13, 2-20, 2-21, 2-22, 2-

5-27, 5-28, 5-29, 5-30, A-5,

intrusion detection system, 2-

30, 3-1, 3-5, 3-6, 3-7, 3-8, 3-

A-6, A-8, A-9, A-11, B-1, B-

11, 2-25, 4-20, 5-22, A-12,

9, 3-10, 3-19, 3-20, 4-9, 4-

3, B-5, B-7, B-9, C-1, C-3, C-

B-3, B-5, B-7, B-15, F-13

15, 4-24, 5-7, 5-8, 5-28, 5-

7, C-10, C-17, C-18, C-19,

intrusion prevention system, 2-

29, B-10, D-1, D-2, F-16, G-

D-1, D-2, D-3, D-6, D-8, E-1,

25, F-16, I-21

2, I-2, I-13, I-25, I-27, I-29

G-2, G-4, G-5, H-1, H-2, I-2,

LandWarNet information

I-3, I-4, I-6, I-8, I-17, I-19, I-

assurance architecture, v, 4-

22, I-36, I-38, I-39, I-40, I-41,

joint force land component

9, F-1, F-2, F-3, F-13, F-14,

I-42

commander, 3-9, 3-11, 4-17,

F-15

network operations and

5-12, 5-14, 5-15, 5-16, 5-17,

liaison officer, I-6

security center, 2-2, 2-15, 2-

5-20, 5-22, 5-23, 5-27, 5-30,

local area network, 2-8, 2-10,

22, 2-23, 2-24, 2-26, 2-29, 3-

D-4, G-1, G-3, H-1, H-2, H-3

3-18, 3-21, 4-19, 4-20, 5-22,

7, 3-9, 3-11, 3-18, 3-22, 3-

Joint Functional Component

23, 4-9, 4-10, 4-15, 4-16, 4-

A-1, B-12, B-13, B-14, B-16,

Command Network Warfare,

17, 4-21, 4-22, 4-23, 5-15,

B-17, E-1, F-2, F-11, F-16, I-

4-4, 4-5

B-1, B-3, B-5, B-7, B-9, C-4,

joint network node, iv, vi, 3-12,

C-5, C-7, C-8, C-10, C-12,

4-23, B-10, B-15, D-4, E-1,

C-18, C-19, D-1, D-6, D-7,

F-2, I-1, I-2, I-3, I-5, I-6, I-8,

F-23, G-2, H-2, H-3

mobile regional hub node, I-1,

I-9, I-12, I-14, I-15, I-16, I-

I-3, I-4, I-5, I-8, I-9, I-10, I-

network operations center, I-

17, I-18, I-19, I-20, I-21, I-22,

11, I-12, I-14, I-15, I-16, I-18,

23, I-25, I-26, I-31, I-33, I-34,

I-23, I-24, I-25, I-26, I-27, I-

I-19, I-20, I-21, I-22

I-35, I-36, I-37, I-38, I-39, I-

29, I-30, I-34, I-36, I-37, I-40,

40, I-41, I-42, I-43, I-44, I-45,

Multiplexer Integration and

I-42, I-43

I-47

Defense Communications

joint network node-network, iv,

Satellite Subsystem

networks, 1-2

vi, E-1, I-1, I-2, I-3, I-5, I-6, I-

Automation System, I-38

Non-Secure Internet Protocol

8, I-9, I-14, I-15, I-16, I-17, I-

Router, A-14, A-15, A-17, A-

18, I-19, I-20, I-21, I-22, I-23,

18, A-19, A-20, A-21, B-10,

I-24, I-25, I-26, I-27, I-29, I-

network control center, I-10, I-

B-15

30, I-34, I-36, I-40, I-42, I-43

11, I-18, I-19, I-45

Non-Secure Internet Protocol

joint network operations control

Network Enterprise Technology

Router Network, 2-11, 2-21,

center, 3-3, 3-4, 3-9, 4-16,

Command, 1-3, 1-13, 2-19,

A-7, A-14, D-3, F-2, F-3, F-

D-7, I-39, I-40, I-42

2-20, 2-21, 2-29, 3-5, 3-6, 3-

5, G-2, I-8, I-9, I-12, I-13, I-

Joint Tactical Switched

9, 3-10, 3-12, 3-13, 5-2, A-1,

17, I-20, I-26, I-27, I-29, I-34

Systems Network

A-4, A-6, A-9, A-10, A-11, A-

Management Configuration

12, A-13, A-14, A-15, B-1, B-

Control Board, 1-3, 3-6

3, B-5, B-7, F-15, F-23, I-4,

operation order, 4-24, 5-7, 5-8,

I-28, I-31, I-32, I-33, I-36

joint task force, 1-10, 2-17, 2-

5-9, B-14, C-17, C-18, D-3,

19, 2-21, 2-22, 2-27, 2-31, 3-

network intrusion detection

I-23, I-36, I-38, I-41, I-42

3, 3-4, 3-6, 3-9, 3-11, 3-16,

system, F-3, F-4, F-6, F-11,

operational control, 2-17, 2-18,

3-21, 4-1, 4-2, 4-3, 4-4, 4-5,

F-16, I-13, I-21, I-22

2-22, 3-2, 3-3, 3-4, 3-9, 3-

4-7, 4-8, 4-9, 4-10, 4-12, 4-

Index-4

FM 6-02.71

19 November 2008

FOR OFFICIAL USE ONLY

Index

10, 3-11, 3-13, 4-1, 4-2, 4-3,

SECRET Internet Protocol

tactical integration cell, iii, 4-

4-4, 4-8, 4-9, 4-10, 4-11, 4-

Router, A-14, A-15, A-17, A-

16, 4-17, 4-21, 5-13, 5-18, 5-

12, 4-13, 4-15, 4-16, 5-12, 5-

18, A-19, A-20, A-21, B-10,

21, 5-26, 5-27, C-10, C-14,

20, 5-22, 5-26, F-19, H-3, I-

B-15

C-17, H-2

10, I-39

SECRET Internet Protocol

tactical liaison team, iii, 4-17,

operations and maintenance, I-

Router Network, 2-21, 3-3,

4-20, 4-21, 5-11, 5-12, 5-14,

14, I-17

A-7, A-14, D-3, F-5, G-2, I-8,

5-15, 5-19

I-9, I-12, I-13, I-17, I-20, I-

operations security, 2-5, 2-12,

tactical local area network

26, I-27, I-29, I-34, I-36, I-43

2-21

encryptor, I-20, I-21, I-38

Secretary of Defense, 2-17, 4-

operations staff officer, ii, 2-26,

tactical network team, iii, 4-16,

4, 4-5, 4-9, I-27

2-27, 3-11, 3-13, 4-17, 4-21,

4-17, 4-21, 5-10, 5-14, 5-15,

4-24, F-19, I-6, I-29

signal brigade (tactical), 3-11,

5-17, 5-20, 5-21, 5-23, 5-26,

4-21, 5-21, H-2, I-29

5-27, 5-30, H-2, H-3

outside the continental United

States, iv, 2-9, 3-11, 3-12, 3-

signal command (Army), 1-3,

tactical operations center, 3-

13, 4-7, 4-19, A-1, I-3, I-4, I-

2-19, 2-20, 2-21, 3-5, 3-6, 3-

15, 3-18, 4-22, 4-23, 5-21,

6, I-7, I-30, I-31

9, 3-10, 3-12, 3-13, 5-2, A-1,

B-12, B-13

I-28, I-31, I-32, I-33, I-36

telecommunications service

signal command (theater), iii,

order, 4-23, 4-24, D-5

program executive office, 2-23,

3-4, 3-8, 3-9, 3-10, 3-11, 3-

teleport facilities, 1-1

F-17

13, 3-15, 3-18, 4-1, 4-15, 4-

Theater Joint Tactical Network

public key enabled, F-2, F-13,

16, 4-19, 5-6, 5-13, 5-17, 5-

Configuration Control Board,

F-14

22, D-5, G-2, H-2, H-3, I-8, I-

1-3

10, I-18, I-21, I-25, I-27, I-28,

public key infrastructure, 1-14,

I-29, I-31, I-32, I-33, I-34, I-

theater network operations and

2-32, A-2, F-2, F-13, F-14,

35, I-36, I-37, I-38, I-39, I-40,

security center, iii, iv, v, 2-3,

F-15

I-44, I-45, I-47

2-14, 2-29, 3-7, 3-8, 3-9, 3-

10, 3-13, 3-14, 3-17, 3-19, 3-

signal operations, D-2

22, 4-9, 4-13, 4-14, 4-15, 4-

regional chief information

Simple Mail Transfer Protocol,

16, 4-17, 4-18, 4-19, 4-20, 4-

officer, 2-22, 2-29, 3-12, 3-

F-3, F-7, F-8, F-10

21, 4-22, 4-23, 5-7, 5-8, 5-9,

13, A-9, A-11, F-23

single-channel ground and

5-10, 5-12, 5-13, 5-15, 5-17,

regional computer emergency

airborne radio system, B-13

5-18, 5-22, 5-23, 5-24, 5-29,

response team, 2-14, 2-16,

5-30, A-1, A-3, A-6, A-8, A-

situational awareness, iii, 1-2,

2-22, 2-24, 2-26, 2-29, 3-17,

9, A-10, A-11, A-12, A-13, B-

2-18, 2-21, 2-31, 3-1, 3-2, 4-

D-7, F-16, F-17, F-23, I-20

1, B-3, B-5, B-7, B-9, C-4, C-

1, 4-3, 4-4, 4-6, 4-7, 4-8, 4-

regional hub node, I-5, I-6, I-

5, C-7, C-8, C-9, C-10, C-12,

9, 4-10, 4-11, 4-12, 4-13, 4-

11, I-14, I-22

C-17, C-18, C-19, D-7, F-2,

14, 4-15, 4-16, 4-18, 4-19, 4-

F-8, F-12, F-15, F-16, F-17,

regional network operations

21, 5-7, 5-8, 5-9, 5-10, 5-17,

F-23, G-2, H-1, H-2, H-3, I-2,

and security center, 2-33, 3-

5-18, 5-20, 5-26, A-6, A-7,

I-5, I-6, I-7, I-8, I-12, I-13, I-

8, 4-19

B-5, B-12, B-13, C-17, C-18,

14, I-15, I-17, I-19, I-20, I-21,

C-19, F-21, H-3, I-2, I-22, I-

regional satellite support

I-22, I-23, I-37, I-38, I-39, I-

33, I-36, I-37, I-39, I-40, I-42,

center, I-8, I-10, I-18, I-28, I-

40, I-41, I-42, I-44, I-46, I-47

I-43

32, I-33, I-34

theater network operations

standard tactical entry point, 1-

remote authentication dial-in

center, 3-2, 3-7, 4-1, 4-6, 4-

1, 4-7, 4-19, G-1, G-2, I-34

user server, 4-18, 4-20

8, 4-10, 4-11, 4-12, 4-13, 4-

standing operating procedure,

14, 4-15, 4-16, I-39, I-42

2-27, 3-19, I-42

theater network operations

satellite access authorization,

STEP, 1-1

control center, 3-3, 4-1, 4-

I-33, I-36, I-37, I-39

system integration oversight,

10, 4-11, 4-12, 4-13, 4-14, 4-

satellite access request, iv, I-

D-4

15, 4-16, G-2, I-18, I-23, I-

11, I-28, I-29, I-30, I-31, I-32,

39, I-42

I-33, I-36, I-37, I-39, I-46, I-

time division multiple access,

tactical, D-1, D-3, D-8

D-6, D-8, G-2, G-3, G-4, I-3,

satellite communications, 1-7,

tactical control, 4-4

I-4, I-5, I-10, I-11, I-18, I-19,

2-3, 3-11, 4-6, 4-14, B-13, I-

tactical hub node, I-1, I-3, I-4, I-

I-25, I-38, I-43, I-45

1, I-3, I-4, I-5, I-10, I-11, I-

5, I-6, I-8, I-9, I-10, I-11, I-

top secret/sensitive

23, I-24, I-25, I-30, I-31, I-32,

12, I-14, I-15, I-16, I-17, I-19,

compartmented information,

I-33, I-37, I-38, I-39, I-47

I-20, I-21, I-22, I-23, I-45

I-3, I-6, I-8, I-18, I-23

19 November 2008

FM 6-02.71

Index-5

FOR OFFICIAL USE ONLY

TC 3-19.5

Training Circular

Headquarters

No. 3-19.5

Department of the Army

Washington, DC, 5 November 2009

Nonlethal Weapons Training

Contents

Page

Preface

vii

Chapter 1

Introduction

1-1

Purpose

1-1

Scope

1-1

Background

1-1

Policy for Nonlethal Weapons

1-2

Nonlethal Capability Requirements

1-2

Nonlethal Weapons Support in Army Operations

1-2

Nonlethal Multi-Media Training Support Package

1-3

Joint Nonlethal Weapons Educational Resources

1-3

Chapter 2

Conduct of Training

2-1

Training Strategy

2-1

User Training

2-1

Nonlethal Munitions Training Requirements

2-1

Certification and Familiarization Training

2-2

Composite Risk Assessment

2-4

Recommended Range Procedures

2-5

Rules of Engagement

2-6

Doctrinal Guidance for Nonlethal Weapons

2-8

Chapter 3

Employ 12-Gauge Point and Area Target Munitions

3-1

Overview

3-1

M1012 12-Gauge Nonlethal Point Round Specifications

3-1

DISTRIBUTION RESTRICTION: Distribution authorized to DOD and DOD contractors only to protect technical or operational

information from automatic dissemination under the International Exchange Program or by other means. This determination was

made on 6 November 2006. Other requests for this document must be referred to the Commandant, USAMPS, ATTN: ATSJ-L,

401 MANSCEN Loop, Suite 1088, Fort Leonard Wood, Missouri 65473-8929.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

5 November 2009

TC 3-19.5

Contents

M1012 Employment Considerations

3-2

M1012 Certification Standards

3-2

M1012 Sighting

3-3

M1013 12-Gauge Crowd Dispersal Cartridge Specifications

3-3

M1013 Employment Considerations

3-4

M1013 Familiarization Standards

3-4

M1013 Sighting

3-5

Chapter 4

Employ 40 Millimeter Nonlethal Munitions

4-1

Overview

4-1

M1006 Sponge Grenade Specifications

4-1

M1006 Employment Considerations

4-2

M1006 Certification Standards

4-2

M1006 Sighting

4-2

M1029 40MM Nonlethal Crowd Dispersal Cartridge Specifications

4-3

M1029 Employment Considerations

4-4

M1029 Familiarization Standards

4-5

M1029 Sighting

4-5

Chapter 5

Employ Nonlethal Grenades

5-1

Overview

5-1

M84 Stun Hand Grenade Specifications

5-1

M84 Employment Considerations

5-2

M84 Safety Considerations

5-2

Arm M84 Stun Hand Grenade

5-3

M104 Sting Ball Grenade Specifications

5-4

M104 Employment Considerations

5-5

M104 Safety Considerations

5-5

Arm M104 Sting Ball Grenade

5-5

Chapter 6

Employ Modular Crowd Control Munition

6-1

Overview

6-1

M5 MCCM Specifications

6-1

M5 MCCM Employment Considerations

6-4

M5 MCCM Safety Considerations

6-4

Emplacing, Aiming, and Arming the M5 MCCM

6-5

Misfire Procedures

6-6

Handling and Recovery Procedures

6-7

Practical Exercise

6-8

TC 3-19.5

5 November 2009

Contents

Chapter 7

Employ 66 Millimeter Nonlethal Grenades

7-1

Overview

7-1

66MM Nonlethal Grenade Specifications

7-1

Nonlethal Grenade Loading and Unloading Procedures

7-2

Nonlethal Grenade Launching Procedures

7-3

Chapter 8

Employ Individual Riot Control Agent Disperser

8-1

Overview

8-1

Definitions

8-1

M39 IRCAD Specifications

8-2

IRCAD Employment Techniques

8-4

IRCAD Safety Considerations

8-6

Decontamination, Recovery, and First Aid

8-6

Characteristics of OC

8-7

Physical and Psychological Effects of OC

8-8

Environmental and Storage Considerations

8-9

Chapter 9

Employ Electro-Muscular Disruption Device

9-1

Overview

9-1

Electro-Muscular Disruption Specifications

9-1

Loading and Unloading Procedures

9-9

Preventive Maintenance, Checks, and Services

9-10

X26E Firing Procedures

9-13

Probe Removal

9-15

Download Usage Data

9-15

Chapter 10

Employ Vehicle Barriers and Arresting Devices

10-1

Overview

10-1

Portable Vehicle Arresting Barrier Specifications

10-1

PVAB Site Selection

10-1

Bump Module Assembly

10-2

Brake Box Installation

10-3

Anchor Installation

10-4

Erector Assembly

10-6

Net Assembly

10-6

Vehicle Light Arresting Device Specifications

10-10

VLAD Site Selection

10-11

VLAD Rapid Deployment

10-11

VALD Lanyard Deployment

10-12

Remove Net From Vehicle

10-12

Rapid Deploy Vehicle Denial Systems

10-13

5 November 2009

TC 3-19.5

iii

Contents

Chapter 11

Employ Communication Devices

11-1

Overview

11-1

Phraselator Specifications

11-1

Phraselator Employment Considerations

11-2

Operate Phraselator

11-2

Phraselator Operator Maintenance

11-7

Demonstrate Phraselator Operation

11-8

Voice Response Translator Specifications

11-9

VRT Employment Considerations

11-9

Operate VRT

11-9

Demonstrate VRT Operation

11-11

Magnetic Audio Device Specifications

11-11

MAD Employment Considerations

11-12

Operate MAD

11-13

Demonstrate MAD Operation

11-15

Appendix A

Nonlethal Capabilities Set

A-1

Appendix B

Nonlethal Munitions Practical Exercise

B-1

Appendix C

M5 MCCM Practical Exercise

C-1

Appendix D

X26E TASER Performance Evaluation

D-1

Appendix E

Components of the Checkpoint Operations Mission Module

E-1

Glossary

....................................................................................................................Glossary-1

References

................................................................................................................References-1

Index

..........................................................................................................................Index-1

TC 3-19.5

5 November 2009

Contents

Figures

Figure

2-1

Nonlethal Munitions Shot Placement Zones

2-2

Figure

2-2

Force Continuum

2-7

Figure

2-3

Doctrinal and Training Resources

2-8

Figure

3-1

Cut-Away View of the M1012 12-Gauge Point Cartridge

3-1

Figure

3-2

M1012 Sighting at 10-20 Meter Targets

3-3

Figure

3-3

Cut-Away View of the M1013 12-Gauge Crowd Dispersal Cartridge

3-4

Figure

3-4

M1013 Sighting at 10-20 Meters

3-5

Figure

4-1

M1006 Sponge Grenade Cut-Away View

4-1

Figure

4-2

M1006 Sighting at 50 Meters

4-3

Figure

4-3

M1006 Sighting at 10 to 45 Meters

4-3

Figure

4-4

M1029 Cut-Away View of the M1029

4-4

Figure

4-5

M1029 Sighting at 15 to 30 Meters

4-5

Figure

4-6

M1029 Sighting at 10 to 15 Meters

4-5

Figure

5-1

M84 Stun Grenade

5-1

Figure

5-2

M84 Stun Grenade Right Handed Procedure

5-3

Figure

5-3

M84 Stun Grenade Left Handed Procedure

5-4

Figure

5-4

Cut-Away View of the M104 Sting Ball Grenade

5-4

Figure

6-1

M5 MCCM with Components

6-1

Figure

6-2

M81 Igniter

6-3

Figure

8-1

M39 Individual Riot Control Agent Disperser

8-3

Figure

9-1

X26E Parts and Functions

9-1

Figure

9-2

X26E with Holster

9-2

Figure

9-3

Cut-Away View of the X26E Cartridge

9-6

Figure

9-4

X26E Probe Types

9-8

Figure

9-5

Results of Improper Handling Technique

9-10

Figure

10-1

Site Requirements for PVAB

10-2

Figure

10-2

Bump Module Assembly

10-3

Figure

10-3

Brake Box Installation

10-4

Figure

10-4

Anchor Installation

10-5

Figure

10-5

Net Assembly

10-7

Figure

10-6

Pack Net

10-9

Figure

10-7

Pack Net Continued

10-9

Figure

10-8

VLAD System Packed for Transport

10-10

Figure

10-9

VLAD Positioned Across Roadway

10-11

Figure

10-10

Magnum Spike System

10-13

Figure

10-11

Caltrops

10-13

Figure

11-1

Phraselator Features and Controls

11-1

5 November 2009

TC 3-19.5

Preface

This Training Circular (TC) serves as a training support package for nonlethal training. The TC provides guidance

for leaders conducting nonlethal weapons (NLW) training. It focuses on effective use of NLW and capabilities.

This TC applies to the Active Army, the Army National Guard (ARNG)/National Guard of the United States

(ARNGUS), and the United States Army Reserves (USAR) unless otherwise stated.

TC 3-19.5 is organized into the following eleven chapters and five appendices that provide nonlethal weapons

training strategies and training support materials:

Chapter 1, Introduction, explains the purpose and scope of the TC and describes the Army’s

nonlethal capability requirements.

Chapter 2, Conduct of Training, provides the training strategy for nonlethal weapons training.

Chapter 3, Employ 12 Gauge Point and Area Target Munitions, describes the characteristic,

employment techniques, and training for the 12 gauge nonlethal rounds.

Chapter 4, Employ 40 Millimeter Nonlethal Munitions, describes the characteristic, employment

techniques, and training for the 40mm nonlethal munitions.

Chapter

5, Employ Nonlethal Grenades, describes the specifications, safety features, and

employment considerations for nonlethal hand thrown grenades.

Chapter 6, Employ Modular Crowd Control Munition, explains how to train Soldiers to emplace,

aim, and arm the M5 Modular Crowd Control Munition.

Chapter 7, Employ 66 Millimeter Nonlethal Grenades, describes the loading, unloading, and

launching procedures for 66mm nonlethal grenades.

Chapter 8, Employ Individual Riot Control Agent Disperser, provides employment procedures for

the M39 individual riot control agent disperser and describes physical and psychological effects of

riot control agents.

Chapter 9, Employ Electro-Muscular Disruption Device, explains the function, characteristics, and

employment of the X26E TASER®.

Chapter 10, Employ Vehicle Barriers and Arresting Devices, describes training and employment

of portable nonlethal vehicle barriers, arresting devices, spike systems, and caltrops.

Chapter 11, Employ Communication Devices, explains the techniques for operating handheld

language translators and voice amplifier.

Appendix A, Nonlethal Capabilities Set, list the components currently available in the nonlethal

capabilities set.

Appendix B, Nonlethal Munitions Practical Exercise, contains instructor guidance and firing

commands for conducting a practical exercise on 12 gauge and 40mm nonlethal munitions.

Appendix C, M5 MCCM Practical Exercise, provides instructor guidance and firing commands

for conducting a practical exercise on the M5 Modular Crowd Control Munition.

5 November 2009

TC 3-19.5

vii

Chapter 1

Introduction

PURPOSE

1-1. TC 3-19.5 provides guidance on specific NLW training with emphasis on User Training, Train-the-Trainer

Training, and Unit Training. It is designed to be used with FM 3-22.40, Multi-Service TTP for the Tactical

Employment of Nonlethal Weapons, and the Multi-Media Training Support Package (MMTSP). The MMTSP is

a Warrior TSP designed to train individual tasks.

SCOPE

1-2. TC 3-19.5 is designed to train leaders and Soldiers, primarily at company-level and below, on the tactical

employment of NLW in support of operating forces.

1-3. Leader training for Field Grade Officers, though not included in this publication, consists of formulating

nonlethal policies, establishing the appropriate rules of engagement (ROE), and deciding when the use of

nonlethal capabilities is best suited.

BACKGROUND

1-4. United States Forces will respond to a myriad of situations across the range of military operations. At the

same time, the military will face increased media attention, worldwide environmental concerns, and a low

national tolerance for long, lethal, and costly campaigns even where vital interests of the nation are clearly

defined. Nonlethal capabilities can expand options and tools available to Commanders.

1-5. NLW enhance the Army’s ability to meet requirements of applying force proportional to the threat and

discriminating in the application of force during military operations. Nonlethal capabilities can reduce the risks

of perceived excessive force, promote international political support, alleviate environmental concerns, enhance

post conflict transitions and termination, and reduce the cost of post conflict reconstruction.

1-6. Many situations that begin as standoffs have the potential to escalate to a point where lethal force may be

justified. However, early and aggressive use of NLW may prevent many of these types of situations from

escalating to deadly force levels. In this aspect NLW can reduce Soldier and non-combatant injuries by

stopping threats from a safe distance.

1-7. It must be made clear that, NLW are not meant to be a substitute for lethal force. Commanders must

ensure that NLW are not deployed without lethal support in the form of lethal overwatch. Employing lethal

overwatch in support of NLW benefits the commander in several ways. First, lethal overwatch provides

Soldiers employing NLW with confidence in knowing that if the situation were to escalate lethal fire is

immediately available. Additionally, lethal overwatch becomes the on-scene eyes and ears of the commander

providing valuable information that could influence future actions and planning.

1-8. NLW and capabilities provide a valuable set of tools for a variety of missions, particularly when deadly

force is not authorized or the preferred course of action. If used effectively, NLW can contribute to mission

accomplishment and:

Limit destruction.

Reduce fratricide.

Limit civilian casualties.

Reduce the likelihood for conflict escalation.

Enhance protection

5 November 2009

TC 3-19.5

1-1

Chapter 1

Reduce reconstruction cost.

Gain public trust and acceptance.

Provide greater range of graduated response options.

POLICY FOR NONLETHAL WEAPONS

1-9. The Army proponent for NLW policy is The Office of the Provost Marshal General. All question

regarding NLW policy, both tactical and non-tactical should be directed to The Office of the Provost Marshal

General, Military Police Policy Division, 2800 Army Pentagon, Washington, DC 20310-2800.

NONLETHAL CAPABILITY REQUIREMENTS

1-10. The tools that make up nonlethal capabilities are broken down into two groups: Counter-Personnel and

Counter-Materiel. Capabilities that are considered Counter-Personnel characteristically influence behavior and

activities of a potentially hostile crowd, incapacitate personnel, aid in the seizure of personnel and deny

personnel access to key areas. Capabilities considered Counter-Materiel provide the ability to disable or

neutralize vehicles or facilities without destroying them. Counter-Materiel capabilities can also deny vehicle

access to certain areas or facilities.

1-11. Counter-Personnel Capabilities. Counter-personnel capabilities currently consist of rounds such as 12-

gauge and 40 millimeter point and area rounds, chemical irritants, impact weapons, and electro muscular

disruption devices such as TASER^®.

1-12. Counter-Materiel capabilities currently consist of vehicle stopping / arresting devices. Some of the items

available are the Portable, Vehicle Arresting Device (M1, PVAB), the Vehicle Lightweight Arresting Device

(M2, VLAD) and an array or caltrops and spike strips. The above listed and other Counter-Personnel and

Counter-Materiel devices can be found in the current Nonlethal Capabilities Set (NLCS). Appendix A provides

a detailed listing of NLCS items.

1-13. The NLCS is designed to equip a Brigade size element with all the appropriate equipment to carry out its

basic missions in accordance with current Rules of Engagement (ROE) and Escalation of Force (EOF)

procedures. The NLCS is an updated version of the Platoon NLCS which contained mainly riot control gear.

These kits are more mission specific and are tailored to a specific purpose.

1-14. A NLCS contains the equipment required to satisfy most operational requirements for an enhanced

capability to apply nonlethal force. It is designed to augment lethal forces and will be employed in a manner

that will incapacitate personnel or material, while minimizing fatalities or permanent injury or damage to

property and the environment.

NONLETHAL WEAPONS SUPPORT IN ARMY OPERATIONS

1-15. NLW support all military operations from peacetime military engagement to major combat operations.

Nonlethal capabilities have particular application in civil support operations where there is the need to enhance

the Army’s ability to meet requirements of applying force proportional to the threat and the desire to protect

non-combatants, promote international political support, alleviate environmental concerns, and enhance post

conflict transitions and termination.

1-16. Specific missions where NLW complement lethal force include the following:

Convoy security in urban operations where population density and characteristics of the area

require the careful employment of force to minimize loss of life and destruction of property.

Crowd control and civil disturbance operations where nonlethal munitions, protective equipment,

and support equipment enable Army elements to execute population control missions and provide

protection while minimizing collateral damage and injury to personnel.

Cordon and search operations where friendly forces come in close contact with the local

population under stressful and often hostile circumstances.

1-2

TC 3-19.5

5 November 2009

Introduction

Checkpoint operations where nonlethal capabilities protect friendly forces and improve public

opinion and acceptance.

In Detainee Operations where all displays of violence must be brought under control quickly while

avoiding unnecessary injury or death to the detainees.

1-17. When Commanders integrate NLW training into unit training, field training exercises, and situational

training Soldiers gain the confidence and skills necessary for the proper employment of NLW.

NONLETHAL MULTI-MEDIA TRAINING SUPPORT PACKAGE

1-18. The Army Nonlethal Scalable Effects Center (ANSEC) at Fort Leonard Wood, Missouri, develops and

implements overarching nonlethal strategies that address solutions to identified gaps in required Army mission

tasks. The nonlethal MMTSP is one of the critical tools used to ensure both the success of today’s Soldier and

that of the future operating force.

1-19. The MMTSP focuses on the Soldier’s use and deployment of the NLCS. Development of the MMTSP

included the assessment and selection of required tasks, development of lesson plans, training materials and

aids, student courseware, and student assessment tools. The MMTSP target audience is at the squad and team

leader level.

1-20. To ensure Soldiers are properly trained, equipped, and educated in the application of nonlethal

capabilities, ANSEC deploys Mobile Training Teams. Mobile Training Teams are currently being deployed

world-wide to assist units with their nonlethal training needs. The MMTSP serves as the primary training tool

used by the Mobile Training Teams and is included in the NLCS.

1-21. To ensure qualified nonlethal instructors are properly managed, ANSEC requested and U.S. Army

Human Resources Command established an Additional Skill Identifier (ASI) 2A (Nonlethal Advisor) to identify

all Army Soldiers, enlisted or officer, who are Inter-Service Nonlethal Individual Weapons Instructor Course

(INIWIC) trained and qualified to be NLW instructors. Soldiers possessing an ASI 2A should be used to assist

planners at Brigade and Division levels on the employment of NLW and the integration of nonlethal capabilities

into training.

JOINT NONLETHAL WEAPONS EDUCATIONAL RESOURCES

1-22. The Joint Nonlethal Weapons Program uses a wide range of educational programs to promote increased

understanding of non-lethal weapons and technologies. A web-based online course taught through Penn State

University Fayette allows interested military and government personnel to increase their knowledge of

nonlethal technology through the internet (http://www.fe.psu.edu/CE/23514.htm ). The latest version of the

course is available on a single DVD for those personnel who may have limited internet access.

1-23. The Penn State’s Nonlethal Weapons: Policies, Practices, and Technologies course consists of nine

modules that include the following:

Introduction and Theory.

Kinetics.

Riot Control Agents and Related Technologies.

Maritime Vehicle Stoppers.

Advanced Technologies.

Emerging Technologies.

Public Order.

Integration of Nonlethal Weapons in Decision-Making.

5 November 2009

TC 3-19.5

1-3

Military reference books and manuals (2009-2023, Volume 7) - page 34