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

CJCSM 3122.02B

25 May 2001

ENCLOSURE I

PROTECTION OF MOVEMENT INFORMATION

1. Definitions. The following definitions apply to movement of forces identified

in JOPES plans through a TPFDD. These definitions are necessary to provide

guidance on the proper security of plans and TPFDD data elements.

a. Movement Data. Movement data consists of those essential elements of

information to schedule lift, obtain transportation assets, manage movement of

forces, and report in-transit visibility of movements and associated forces

(people, equipment, and supplies). As a minimum, movement data must

describe what forces are planned to move or actual loads, where the movement

segment is planned to begin/end or actual movement location, and when the

movement is planned to occur or actual time of movement. (NOTE: All three

groups of data must be present to be considered movement data).

b. Aggregation. Movement data elements that can be grouped to show

multiple sequential segments of a force movement from origin to POE to

POD/destination are considered to be aggregated. Additionally, movement

data elements for multiple movements from either POE to POD or POD to

destination that reflect a flow of force movements into or within a supported

commander’s AOR are considered aggregated.

c. Execution. Execution for a force movement is initiated when a force is

directed to accomplish movement by competent authority. Subsequent

direction by the supported commander to supporting commanders (lift

providers) normally begins the movement process that includes transportation

planning, scheduling of lift, and movement of forces and transportation assets.

Movement begins when forces depart the origin or POE on a transportation

asset.

2. OPLAN Security. Security for OPLANs falls into two broad categories,

information security and operations security. Information security addresses

the proper classification of deployment plans and associated data elements

while operations security is focused on the proper protection of unclassified

movement data, especially when aggregated in automated information systems.

3. Information Security Classification Guidance

a. General. Information security markings in OPLANs will conform to the

requirements in Chapter of reference h; Director of Central Intelligence

Directive (DCID) 1/7, Security Controls in the Dissemination of Intelligence

I-1

Enclosure I

CJCSM 3122.02B

25 May 2001

Information (For Official Use Only); and DCID 1/19, Security Policy Manual for

SCI Control Systems (UNCLASSIFIED), as amplified below.

b. Classification Markings on Plan Elements. See JOPES Volume II,

reference b.

c. Control Markings. See JOPES Volume II, reference b.

d. Paragraph and Subparagraph Markings. See JOPES Volume II,

reference b.

e. Unit Maintained Deployment Data. Generic unit data maintained at the

unit level for the purpose of supporting deployment operations is considered

UNCLASSIFIED/FOR OFFICIAL USE ONLY if not associated with an OPLAN.

Unit deployment data in a TPFDD for an OPLAN is classified in accordance

with the supported commander’s classification guidance.

f. JOPES OPLAN Data Classification. JOPES data will normally be at its

highest classification during initial deliberate or time-sensitive planning

phases. Each supported command will publish specific classification guidance

before the initiation of any planning activities against a specific OPLAN ID.

This guidance can be by message or supplemental TPFDD Instructions.

g. JOPES TPFDD Data Element Classification. The TPFDD is classified at

the same level as the OPLAN using the classification guidance issued by the

supported commander. If in doubt, treat TPFDD information as classified

information. Contact the TPFDD validation authority for clarification of TPFDD

information classification if there is any question on the level of classification.

h. UNCLASSIFIED Movement Data. The following movement data, in

singular or aggregated form, becomes UNCLASSIFIED/FOR OFFICIAL USE

ONLY at execution for the purpose of transportation planning, scheduling,

obtaining transportation assets, managing movements, reporting movement

status, and visibility of in-transit cargo/passengers. All other JOPES data

remains classified at the level specified by the supported commander unless

specifically released as UNCLASSIFIED/FOR OFFICIAL USE ONLY by the

supported commander. Non-JOPES movements are addressed in applicable

regulations.

I-2

Enclosure I

CJCSM 3122.02B

25 May 2001

ULN Number (ULN) ¹

Unit Identification (UIC)

Unit Type Code (UTC)

Service Codes (SVC)

Non-Baseline Extension (load POCs)

Mission Number (MSN #)

Point of Departure/Departure Day ²

Point of Arrival/Arrival Day ³

Scheduled and Actual (Arrival and Departure)

Total Short Tons (STONS) - Bulk, Oversize, Outsize

Total Measurement Tons (MTONS)

Total Square Feet (SQ FT)

Transportation Control Number (TCN)

Number of Pieces

Length Width Height

Cargo Category Codes

Hazardous Material (HAZMAT)

Personnel Requiring Transportation (PAX)

Manifest/Nomenclature

Name, SSN, and Grade ⁴

¹ ULN is comprised of the five-character Force Requirement Number (FRN) along with the

fragmentation and insert codes that are each one character.

² Origin (RLD), POE (ALD), POD (LAD), Intermediate Location (ILOC)

³ POE (ALD), POD (EAD/LAD), Intermediate Location (ILOC)

⁴ Not resident JOPES TPFDD data but collected during the movement manifesting process.

I-3

Enclosure I

CJCSM 3122.02B

25 May 2001

i. Actual destination locations are normally released at execution as

UNCLASSIFIED/FOR OFFICIAL USE ONLY unless the supported commander

requires a higher classification level to protect actual destination locations.

(1) A destination location that the supported commander desires to

maintain as classified can be protected by using an alias entry in the TPFDD or

in unclassified DTS AIS and released as UNCLASSIFIED/FOR OFFICIAL USE

ONLY.

(a) The supported commander defines procedures for the use of alias

names and reference to actual destination locations in the OPLAN/OPORD and

coordinates movement of TPFDD forces to alias destination locations.

(b) Supported commanders can create alias destination names for

use in the TPFDD and movement AIS by contacting the Joint Staff J-33 to

GEOLOC.

(2) Future systems and procedures should allow for the display of an

actual destination and an alias destination that can be passed to unclassified

Defense Transportation System (DTS) Automated Information Systems (AIS) as

UNCLASSIFIED/FOR OFFICIAL USE ONLY.

4. Release of OPLAN Information

a. Reference e provides guidance concerning the release of OPLAN

information.

b. The supported commander through the Chairman of the Joint Chiefs of

Staff should resolve conflicts between procedural guidance contained herein

and directives received from international authorities or provisions of any plan

established by international agreement.

c. Conflicts that arise between procedural provisions in this document and

CJCSI 3100.01A (Joint Strategic Planning System), the Joint Strategic

Capabilities Plan (JSCP), Joint Pub 0-2 (Unified Action Armed Forces), or the

Unified Command Plan (UCP). The provisions of those documents have

precedence.

I-4

Enclosure I

CJCSM 3122.02B

25 May 2001

5. Operations Security of Movement Data

a. People and organizations associated with military operations have a

responsibility to protect planning and movement data so that they do not

inadvertently jeopardize execution of a military operation or force protection for

units supporting an operation. Operations security is focused on the

protection of unclassified information to enhance the commander’s success in

a military operation and maximize force protection. The following JOPES

operations security procedures are implemented to meet these objectives.

b. Unclassified movement data is UNCLASSIFIED/FOR OFFICIAL USE

ONLY. Appropriate markings must be displayed to ensure proper handling.

Guidance for handling UNCLASSIFIED/FOR OFFICIAL USE ONLY data is

found in reference h.

c. Lift providers release to commercial carriers only the minimum

unclassified movement data necessary to obtain and schedule transportation

assets, manifest cargo/passengers, and provide for asset tracking through the

carrier’s system.

d. UNCLASSIFIED/FOR OFFICIAL USE ONLY movement data must not be

displayed in a generally accessible, unclassified medium without approval from

the supported commander. Normally, systems and data are protected via

access controls to ensure only those authorized have access to movement data.

e. Aggregated movement data must be protected to a greater degree than

movement data in a non-aggregated format. Aggregated movement data in DTS

AIS must use access controls (e.g., passwords, voice recognition, retinal scans,

etc.) to limit accessibility to authorized users IAW DOD Directive 5200.28,

Security Requirements for Automated Information Systems (AIS), 21 March

1988. In addition, defined technical measures to enhance the security of

aggregated movement data systems should be implemented to the maximum

extent practicable.

f. Due diligence requires personnel to use prudent measures to preclude

unauthorized access to movement data. To accomplish mission-related

activities, electronic transmission (voice, data or facsimile) of

UNCLASSIFIED/FOR OFFICIAL USE ONLY aggregated movement data should

be by approved secure communications systems whenever practicable.

6. Although DTS AIS are protected, they require continuous upgrades. In the

long term, CINCs will include, where appropriate, protection measures for DTS

AIS in their Integrated Priority Lists, Joint Monthly Readiness Reviews, and

I-5

Enclosure I

CJCSM 3122.02B

25 May 2001

ENCLOSURE J

REFERENCES

a. CJCSM 3122.01, 14 July 2000, "Joint Operation Planning and Execution

System, Volume I, (Planning Policies and Procedures)," with Change 1 (change

to be release soon)

b. CJCSM 3122.03A, 31 December 1999, “Joint Operation Planning and

Execution System, Volume II, Planning Formats and Guidance,” with Change 1,

6 September 2000.

c. Joint Publication 4-01.8, 13 June 2000, “Joint Tactics, Techniques, and

Procedures (JTTP) for Joint Reception, Staging, Onward Movement and

Integration (JRSOI).”

d. DOD Regulation 4500.9-R, Part I-V, “Defense Transportation Regulation.”

e. CJCSI 5714.01A, 1 March 1999, “Release Procedures for Joint Staff and Joint

Papers and Information.”

f. CJCSM 3150.16, 15 March 1996, “Joint Operation Planning and Execution

System Reporting Structure (JOPESREP)” for JOPES Classic and for JOPES 2000

CJCSM 3150.16A, 29 September 2000. JOPESREP, CJSCM 3150.16 and

CJCSM 3150.16A, are projected for reissue as CJCSM 3150.16B (in draft),

containing a Volume I for JOPES Classic and a Volume II for JOPES 2000.

g. CJCSM 3500.03, 1 June 1996, “Joint Training Manual for the Armed Forces

of the United States,” with Change 4, 28 September 1998.

h. DOD Regulation 5200.1-R, January 1997, “Information Security Program.”

i. CJCSM 3150.15, 1 April 1996, “Standard Specified Geographic Location File

Request.” Revision A to be release soon.

J-1

Enclosure J

CJCSM 3122.02B

25 May 2001

GLOSSARY

PART I--ABBREVIATIONS AND ACRONYMS

ACE

air combat element

ACR

armored cavalry regiment

ADP

automated data processing

AEF

Air Expeditionary Force

AFOE

assault follow-on echelon

ALD

available-to-load date at POE

AMC

Air Mobility Command

AOR

area of responsibility

APOD

aerial port of debarkation

APOE

aerial port of embarkation

ARG

amphibious readiness group

ATF

amphibious task force

AUEL

automated unit equipment list

battalion

BTRY

battery

CAP

crisis action planning

CAT

crisis action team

command element

CFL

Combat Logistics Force

CIN

cargo increment number

CJCS

Chairman of the Joint Chiefs of Staff

CJTF

commander, joint task force

COCOM

combatant command (command authority)

COA

course of action

CONPLAN

operation plan in concept format

CONUS

continental United States

COP

common operational picture

CRD

CINC’s required delivery date

combat support

CSS

combat service support

CSSE

combat service support element

CTP

commercial ticket program

CVBG

carrier battle group

DBSELECT

database select

DOD

Department of Defense

DTG

date-time group

DTS

Defense Transportation System

GL-1

Glossary

CJCSM 3122.02B

25 May 2001

EAD

earliest arrival date at POD

force enhancements

FDO

flexible deterrent options

force module(s)

FMID

force module identifier

FRAG

fragmentation code

FVT

force validation tool

GCE

ground combat element

GCCS

Global Command and Control System

GENSER

general service

GEOCODE

geographic code

GEOLOC

geographic location code

GSORTS

Global Status of Resources and Training System

GSSO

GCCS site security officer

GTN

Global Transportation Network

HAZMAT

hazardous material

headquarters

IAW

in accordance with

IPC

initial planning conference

ITV

in-transit visibility

JFAST

Joint Flow and Analysis for Transportation

JMETL

Joint Mission Essential Task List

JNOCC

JOPES Network Operation Control Center

JOPES

Joint Operation Planning and Execution System

JPEC

Joint Planning and Execution Community

JRSOI

joint reception, staging, onward movement, and integration

JSCP

Joint Strategic Capabilities Plan

JTF

Joint Task Force

LAD

latest arrival date at POD

LOI

letter of instruction

M/S

mode and source

MEDEVAC

medical evacuation

MILSTAMP

Military Standard Transportation and Movement

Procedures

MOG

maximum on ground

MPC

mid-planning conference

GL-2

Glossary

CJCSM 3122.02B

25 May 2001

MPF

maritime pre-positioning force

MSC

Military Sealift Command

MTMC

Military Traffic Management Command

MTON

measurement ton(s)

NATO

North Atlantic Treaty Organization

NCA

National Command Authorities

NEO

noncombatant evacuation operations

nonstandard

OPLAN

operation plan in complete format

OPORD

operation order

PAX

passengers

PID

plan identification number

personnel increment number

POC

point of contact

POD

port of debarkation

POE

port of embarkation

POO

point of origin

PROVORG

providing organization

RLD

ready-to-load date (at origin)

ROE

rules of engagement

RO/RO

roll-on/roll-off

RQT

rapid query tool

S&M

scheduling and movement

SAAM

special assignment airlift mission

SOC

Special Operations Command

SPOD

seaport of debarkation

SPOE

seaport of embarkation

SSF

schedule status flag

STON

short ton(s)

TACP

tactical air control party

TCC

Transportation Component Command(s)

TPFDD

time-phased force and deployment data

TUCHA

Type Unit Characteristics File

UIC

unit identification code

ULC

unit level code

ULN

unit line number

USERID

user identification

GL-3

Glossary

CJCSM 3122.02B

25 May 2001

PART II--TERMS AND DEFINITIONS

aggregation-- Movement data elements that can be grouped to show multiple

sequential segments of a force movement from origin to POE to

POD/destination are considered to be aggregated. Additionally, movement

data elements for multiple movements from either POE to POD or POD to

destination that reflect a flow of force movements into or within a supported

commander’s AOR are considered aggregated.

alert order--1. A crisis-action planning directive from the Secretary of Defense,

issued by the Chairman of the Joint Chiefs of Staff, that provides essential

guidance for planning and directs the initiation of execution planning for the

selected course of action authorized by the Secretary of Defense.

2. A

planning directive that provides essential planning guidance and directs the

initiation of execution planning after the directing authority approves a military

course of action. An alert order does not authorize execution of the approved

course of action. (JP 1-02)

available-to-load date-- A day, relative to C-day in a time-phased force and

deployment data, that unit and nonunit equipment and forces can begin

loading on an aircraft or ship at the port of embarkation. Also called ALD.

(JP 1-02)

cargo increment number-- A seven-character alphanumeric field that

uniquely describes a non-unit-cargo entry (line) in a Joint Operation Planning

and Execution System time-phased force and deployment data. (JP 1-02)

CINC’s required date-- The original date relative to C-day, specified by the

combatant commander for arrival of forces or cargo at the destination; shown

in the time-phased force and deployment data to assess the impact of later

arrival. Also called CRD. (JP 1-02)

civil reserve air fleet-- A program in which the Department of Defense uses

aircraft owned by a US entity or citizen. The aircraft are allocated by the

Department of Transportation to augment the military airlift capability of the

Department of Defense. These aircraft are allocated, in accordance with DOD

requirements, to segments, according to their capabilities, such as

International Long Range and Short Range Cargo and Passenger sections,

National (Domestic and Alaskan sections) and Aeromedical Evacuation and

other segments as may be mutually agreed upon by the Department of Defense

and the Department of Transportation. Also called CRAF. (JP 1-02)

CRAF can be incrementally activated by the Department of Defense in three

stages in response to defense-oriented situations, up to and including a

declared national emergency or war, to satisfy DOD airlift requirements.

GL-5

Glossary

CJCSM 3122.02B

25 May 2001

USCINCTRANS may activate, with the approval of the Secretary of Defense, any

CRAF stage or segment to fulfill commercial air augmentation of DOD’s airlift

fleet. When activated, CRAF aircraft are under the mission control of the

Department of Defense while remaining a civil resource under the OPCON of

the responsible US entity or citizen.

a. CRAF Stage I. This stage involves DOD use of civil air resources that air

carriers will furnish to the Department of Defense to support substantially

expanded peacetime military airlift requirements.

b. CRAF Stage II. This stage involves DOD use of civil air resources that

the air carriers will furnish to Department of Defense in a time of defense airlift

emergency.

c. CRAF Stage III. This stage involves DOD use of civil air resources in time

of declared national defense-oriented emergency or war, or when otherwise

necessary for the national defense.

closure-- In transportation, the process of a unit arriving at a specified

location. It begins when the first element arrives at a designated location, e.g.,

port of entry/port of departure, intermediate stops, or final destination, and

ends when the last element does likewise. For the purposes of studies and

command post exercises, a unit is considered essentially closed after 95

percent of its movement requirements for personnel and equipment are

completed. (JP 1-02)

combatant command (command authority)-- 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, 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). Also called

COCOM. (JP 1-02)

GL-6

Glossary

CJCSM 3122.02B

25 May 2001

combatant commander-- A commander in chief of one of the unified or

specified combatant commands established by the President. (JP 1-02)

commander’s estimate of the situation-- A logical process of reasoning by

which a commander considers all the circumstances affecting the military

situation and arrives at a decision as to a course of action to be taken to

accomplish the mission. A commander’s estimate which considers a military

situation so far in the future as to require major assumptions is called a

commander’s long-range estimate of the situation. (JP 1-02)

common-user transportation-- Transportation and transportation services

provided on a common basis for two or more Department of Defense agencies

and, as authorized, non-DOD agencies. Common-user assets are under the

combatant command (command authority) of USCINCTRANS, excluding

Service-unique or theater-assigned transportation assets. (JP 1-02)

concept of operations-- A verbal or graphic statement, in broad outline, of a

commander’s assumptions or intent in regard to an operation or series of

operations. The concept of operations frequently is embodied in campaign

plans and operation plans; in the latter case, particularly when the plans cover

a series of connected operations to be carried out simultaneously or in

succession. The concept is designed to give an overall picture of the operation.

It is included primarily for additional clarity of purpose. Also called

commander’s concept. (JP 1-02)

concept plan-- An operation plan in concept format. Also called CONPLAN.

(JP 1-02)

course of action-- 1. A plan that would accomplish, or is related to, the

accomplishment of a mission. 2. The scheme adopted to accomplish a task or

mission. It is a product of the Joint Operation Planning and Execution System

concept development phase. The supported commander will include a

recommended course of action in the commander’s estimate. The

recommended course of action will include the concept of operations,

evaluation of supportability estimates of supporting organizations, and an

integrated time-phased database of combat, combat support, and combat

service support forces and sustainment. Refinement of this database will be

contingent on the time available for course of action development. When

approved, the course of action becomes the basis for the development of an

operation plan or operation order. Also called COA. (JP 1-02)

GL-7

Glossary

CJCSM 3122.02B

25 May 2001

course of action development-- The phase of the Joint Operation Planning

and Execution System within the CAP process that provides for the

development of military responses and includes, within the limits of the time

allowed: establishing force and sustainment requirements with actual units;

evaluating force, logistic, and transportation feasibility; identifying and

resolving resource shortfalls; recommending resource allocations; and

producing a course of action via a commander’s estimate that contains a

concept of operations, employment concept, risk assessments, prioritized

courses of action, and supporting databases. (JP 1-02)

crisis-- An incident or situation involving a threat to the United States, its

territories, citizens, military forces, possessions, or vital interests that develops

rapidly and creates a condition of such diplomatic, economic, political, or

military importance that commitment of US military forces and resources is

contemplated to achieve national objectives. (JP 1-02)

crisis action planning-- 1. The Joint Operation Planning and Execution

System process involving the time-sensitive development of joint operation

plans and orders in response to an imminent crisis. CAP follows prescribed

crisis action procedures to formulate and implement an effective response

within the time frame permitted by the crisis. 2. The time-sensitive planning

for the deployment, employment, and sustainment of assigned and allocated

forces and resources that occurs in response to a situation that may result in

actual military operations. Crisis action planners base their plan on the

circumstances that exist at the time planning occurs. Also called CAP. (JP 1-

02)

deployment-- 1. In naval usage, the change from a cruising approach or

contact disposition to a disposition for battle.

2. The movement of forces

within areas of operation.

3. The positioning of forces into a formation for

battle.

4. The relocation of forces and materiel to desired areas of operations.

Deployment encompasses all activities from origin or home station through

destination, specifically including intra-continental United States, intertheater,

and intratheater movement legs, staging, and holding areas. (JP 1-02)

deployment database-- The JOPES (Joint Operation Planning and Execution

System) database containing the necessary information on forces, materiel, and

filler and replacement personnel movement requirements to support execution.

The database reflects information contained in the refined time-phased force

and deployment data from the deliberate planning process or developed during

the various phases of the CAP process, and the movement schedules or tables

developed by the transportation component commands to support the

deployment of required forces, personnel, and materiel. (JP 1-02)

GL-8

Glossary

CJCSM 3122.02B

25 May 2001

deployment order-- A planning directive from the Secretary of Defense, issued

by the Chairman of the Joint Chiefs of Staff, that authorizes and directs the

transfer of forces between combatant commands by reassignment or

attachment. A deployment order normally specifies the authority that the

gaining combatant commander will exercise over the transferred forces.

(JP 1-02)

deployment planning-- Operational planning directed toward the movement of

forces and sustainment resources from their original locations to a specific

operational area for conducting the joint operations contemplated in a given

plan. Encompasses all activities from origin or home station through

destination, specifically including intra-continental United States, intertheater,

and intratheater movement legs, staging areas, and holding areas. (JP 1-02)

deployment preparation order-- An order issued by competent authority to

move forces or prepare forces for movement (e.g., increase deployability posture

of units). (JP 1-02)

deterrent options-- A course of action, developed on the best economic,

diplomatic, political, and military judgment, designed to dissuade an adversary

from a current course of action or contemplated operations. (In constructing

an operation plan, a range of options should be presented to effect deterrence.

Each option requiring deployment of forces should be a separate force module.)

(JP 1-02)

diversion-- 1. The act of drawing the attention and forces of an enemy from

the point of the principal operation; an attack, alarm, or feint that diverts

attention.

2. A change made in a prescribed route for operational or tactical

reasons. A diversion order will not constitute a change of destination.

3. A

rerouting of cargo or passengers to a new transshipment point or destination or

on a different mode of transportation prior to arrival at ultimate destination.

In naval mine warfare, a route or channel bypassing a dangerous area. A

diversion may connect one channel to another or it may branch from a channel

and rejoin it on the other side of the danger. (JP 1-02)

earliest arrival date--A day, relative to C-day, that is specified by a planner as

the earliest date when a unit, a resupply shipment, or replacement personnel

can be accepted at a port of debarkation during a deployment. Used with the

latest arrival data, it defines a delivery window for transportation planning.

Also called EAD. (JP 1-02)

GL-9

Glossary

CJCSM 3122.02B

25 May 2001

execute order-- 1. An order issued by the Chairman of the Joint Chiefs of

Staff, by the authority and at the direction of the Secretary of Defense, to

implement a National Command Authorities decision to initiate military

operations.

2. An order to initiate military operations as directed. (JP 1-02)

execution planning-- The phase of the Joint Operation Planning and

Execution System CAP process that provides for the translation of an approved

course of action into an executable plan of action through the preparation of a

complete operation plan or operation order. Execution planning is detailed

planning for the commitment of specified forces and resources. During CAP,

an approved operation plan or other National Command Authorities-approved

course of action is adjusted, refined, and translated into an operation order.

Execution planning can proceed on the basis of prior deliberate planning, or it

can take place in the absence of prior planning. (JP 1-02)

filler personnel-- Individuals of suitable grade and skill initially required to

bring a unit or organization to its authorized strength. (JP 1-02)

Flexible Deterrent Option-- A planning construct intended to facilitate early

decision by laying out a wide range of interrelated response paths that begin

with deterrent-oriented options carefully tailored to send the right signal. The

Flexible Deterrent Option is the means by which the various deterrent options

available to a commander (such as economic, diplomatic, political, and military

measures) are implemented into the planning process. Also called FDO.

(JP 1-02)

force closure-- The point in time when a supported commander determines

that sufficient personnel and equipment resources are in the assigned area of

operations to carry out assigned tasks. (JP 1-02)

force list-- A total list of forces required by an operation plan, including

assigned forces, augmentation forces, and other forces to be employed in

support of the plan. (JP 1-02)

force module-- A grouping of combat, combat support, and combat service

support forces, with their accompanying supplies and the required nonunit

resupply and personnel necessary to sustain forces for a minimum of 30 days.

The elements of force modules are linked together or are uniquely identified so

that they may be extracted from or adjusted as an entity in the Joint Operation

Planning and Execution System databases to enhance flexibility and

usefulness of the operation plan during a crisis. Also called FM.

(JP 1-02)

GL-10

Glossary

CJCSM 3122.02B

25 May 2001

force requirement number-- An alphanumeric code used to uniquely identify

force entries in a given operation plan time-phased force and deployment data.

Also called FRN. (JP 1-02)

fragmentation and insert codes-- Codes that are used to uniquely identify

separately deploying subordinate units, fragmentations, or increments of a

single force. When one force requirement deploys in more than one increment

and those increments require different time phasing or routing, fragmentation

and insert codes will be used to split the requirement into its deployment

increments. (See CJCSM 3150.16, JOPESREP)

grossly transportation feasible-- A determination made by the supported

commander that a draft operation plan can be supported with the apportioned

transportation assets. This determination is made by using a transportation

feasibility estimator to simulate movement of personnel and cargo from port of

embarkation to port of debarkation within a specified time frame. (JP 1-02)

implementation-- Procedures governing the mobilization of the force and the

deployment, employment, and sustainment of military operations in response

to execution orders issued by the National Command Authorities. (JP 1-02)

implementation planning-- Operational planning associated with the conduct

of a continuing operation, campaign, or war to attain defined objectives. At the

national level, it includes the development of strategy and the assignment of

strategic tasks to the combatant commanders. At the theater level, it includes

the development of campaign plans to attain assigned objectives and the

preparation of operation plans and operation orders to prosecute the campaign.

At lower levels, implementation planning prepares for the execution of assigned

tasks or logistic missions. See also joint operation planning. (JP 1-02)

indications and warning-- Those intelligence activities intended to detect and

report time-sensitive intelligence information on foreign developments that

could involve a threat to the United States or allied/coalition military, political,

or economic interests or to US citizens abroad. It includes forewarning of

enemy actions or intentions; the imminence of hostilities; insurgency;

nuclear/non-nuclear attack on the United States, its overseas forces, or

allied/coalition nations; hostile reactions to US reconnaissance activities;

terrorists’ attacks; and other similar events. Also called I&W. (JP 1-02)

in-place force-- 1. A NATO assigned force which, in peacetime, is principally

stationed in the designated combat zone of the NATO command to which it is

committed.

2. Force within a combatant commander’s area of responsibility

and under the combatant commander’s combatant command (command

authority). (JP 1-02)

GL-11

Glossary

CJCSM 3122.02B

25 May 2001

in-transit visibility-- The ability to track the identity, status, and location of

Department of Defense units, and non-unit cargo (excluding bulk petroleum,

oils, and lubricants) and passengers; medical patients; and personal property

from origin to consignee or destination across the range of military operations.

(JP 1-02)

joint operation planning-- Planning for contingencies which can reasonably

be anticipated in an area of responsibility or joint operations area of the

command. Planning activities exclusively associated with the preparation of

operation plans, operation plans in concept format, campaign plans, and

operation orders (other than the single integrated operation plan) for the

conduct of military operations by the combatant commanders in response to

requirements established by the Chairman of the Joint Chiefs of Staff. Joint

operation planning is coordinated at the national level to support Secretary of

Defense Contingency Planning Guidance, strategic requirements in the

National Military Strategy, and emerging crises. As such, joint operation

planning includes mobilization planning, deployment planning, employment

planning, sustainment planning, and redeployment planning procedures.

Joint operation planning is performed in accordance with formally established

planning and execution procedures. (JP 1-02)

Joint Operation Planning and Execution System-- A continuously evolving

system that is being developed through the integration and enhancement of

earlier planning and execution systems: Joint Operation Planning System and

Joint Deployment System. It provides the foundation for conventional

command and control by national- and theater-level commanders and their

staffs. It is designed to satisfy their information needs in the conduct of joint

planning and operations. Joint Operation Planning and Execution System

(JOPES) includes joint operation planning policies, procedures, and reporting

structures supported by communications and automated data processing

systems. JOPES is used to monitor, plan, and execute mobilization,

deployment, employment, and sustainment activities associated with joint

operations. Also called JOPES. (JP 1-02)

joint planning and execution community-- Those headquarters, commands,

and agencies involved in the training, preparation, movement, reception,

employment, support, and sustainment of military forces assigned or

committed to a theater of operations or objective area. It usually consists of

the Joint Staff, Services, Service major commands (including the Service

wholesale logistics commands), unified commands (and their certain Service

component commands), subunified commands, transportation component

commands, joint task forces (as applicable), Defense Logistics Agency, and

GL-12

Glossary

CJCSM 3122.02B

25 May 2001

other Defense agencies (e.g., Defense Intelligence Agency) as may be

appropriate to a given scenario. Also called JPEC. (JP 1-02)

joint staff-- 1. The staff of a commander of a unified or specified command,

subordinate unified command, joint task force, or subordinate functional

component (when a functional component command will employ forces from

more than one Military Department), which includes members from the several

Services comprising the force. These members should be assigned in such a

manner as to ensure that the commander understands the tactics, techniques,

capabilities, needs, and limitations of the component parts of the force.

Positions on the staff should be divided so that Service representation and

influence generally reflect the Service composition of the force.

(capitalized

as Joint Staff) The staff under the Chairman of the Joint Chiefs of Staff as

provided for in the National Security Act of 1947, as amended by the

Goldwater-Nichols Department of Defense Reorganization Act of 1986. The

Joint Staff assists the Chairman and, subject to the authority, direction, and

control of the Chairman, the other members of the Joint Chiefs of Staff and the

Vice Chairman in carrying out their responsibilities. (JP 1-02)

latest arrival date-- A day, relative to C-day, that is specified by a planner as

the latest date when a unit, a resupply shipment, or replacement personnel

can arrive and complete unloading at the port of debarkation and support the

concept of operations. Also called LAD. (JP 1-02)

level of detail-- Within the current joint planning and execution systems,

movement characteristics are described at five distinct levels of detail. These

levels are: a. level I. aggregated level. Expressed as total number of

passengers and total short tons, total measurement tons, total square feet

and/or total hundreds of barrels by unit line number (ULN), cargo increment

number (CIN), and personnel increment number (PIN). b. level II. summary

level. Expressed as total number of passengers by ULN and PIN and short

tons, measurement tons (including barrels), total square feet of bulk, oversize,

outsize, and non-air-transportable cargo by ULN and CIN. c. level III. detail

by cargo category. Expressed as total number of passengers by ULN and PIN

and short tons, and/or measurement tons (including barrels), total square feet

of cargo as identified by the ULN or CIN three-position cargo category code. d.

level IV. detail expressed as number of passengers and individual dimensional

data (expressed in length, width, and height in number of inches) of cargo by

equipment type by ULN. e. level V. detail by priority of shipment. Expressed

as total number of passengers by Service specialty code in deployment

sequence by ULN individual weight (in pounds) and dimensional data

(expressed in length, width, and height in number of inches) of equipment in

deployment sequence by ULN. (JP 1-02)

GL-13

Glossary

CJCSM 3122.02B

25 May 2001

limiting factor-- A factor or condition that, either temporarily or permanently,

impedes mission accomplishment. Illustrative examples are transportation

network deficiencies, lack of in-place facilities, malpositioned forces or materiel,

extreme climatic conditions, distance, transit or overflight rights, political

conditions, etc. (JP 1-02)

logistic assessment-- An evaluation of: a. The logistic support required to

support particular military operations in a theater of operations, country, or

area. b. The actual and/or potential logistics support available for the

conduct of military operations either within the theater, country, or area, or

located elsewhere. (JP 1-02)

logistics-- The science of planning and carrying out the movement and

maintenance of forces. In its most comprehensive sense, those aspects of

military operations which deal with: a. design and development, acquisition,

storage, movement, distribution, maintenance, evacuation, and disposition of

materiel; b. movement, evacuation, and hospitalization of personnel; c.

acquisition or construction, maintenance, operation, and disposition of

facilities; and d. acquisition or furnishing of services. (JP 1-02)

major combat element-- Those organizations and units described in the Joint

Strategic Capabilities Plan that directly produce combat capability. The size of

the element varies by Service, force capability, and the total number of such

elements available. Examples are Army divisions and separate brigades, Air

Force squadrons, Navy task forces, and Marine expeditionary forces. (JP 1-02)

major force-- A military organization comprised of major combat elements and

associated combat support, combat service support, and sustainment

increments. The major force is capable of sustained military operations in

response to plan employment requirements. See also major combat element.

(JP 1-02)

manifest-- A document specifying in detail the passengers or items carried for

a specific destination. (JP 1-02)

materiel-- All items (including ships, tanks, self-propelled weapons, aircraft,

etc., and related spares, repair parts, and support equipment, but excluding

real property, installations, and utilities) necessary to equip, operate, maintain,

and support military activities without distinction as to its application for

administrative or combat purposes. (JP 1-02)

mobility analysis-- An in-depth examination of all aspects of transportation

planning in support of operation plan and operation order development.

(JP 1-02)

GL-14

Glossary

CJCSM 3122.02B

25 May 2001

movement data-- Movement data consists of those essential elements of

information to schedule lift, obtain transportation assets, manage movement of

forces and report in-transit visibility of movements and associated forces

(people, equipment, and supplies). As a minimum movement data must

describe what forces are planned to move or actual loads, where the movement

segment is planned to begin/end or actual movement location, and when the

movement is planned to occur or actual time of movement. (NOTE: All three

groups of data must be present to be considered movement data).

movement execution-- Execution for a force movement is initiated when a force

is directed to accomplish movement by competent authority. Normally, direction

by the supported commander to supporting commanders (lift providers) begins

the movement process that includes transportation planning, scheduling of lift,

and movement of forces and transportation assets. Movement begins when

forces depart the origin or POE on a transportation asset.

movement schedule-- A schedule developed to monitor or track a separate

entity whether it is a force requirement, cargo or personnel increment, or lift

asset. The schedule reflects the assignment of specific lift resources (such as

an aircraft or ship) that will be used to move the personnel and cargo included

in a specific movement increment. Arrival and departure times at ports of

embarkation, etc., are detailed to show a flow and workload at each location.

Movement schedules are detailed enough to support plan implementation.

(JP 1-02)

noncombatant evacuation operations-- Operations directed by the

Department of State, the Department of Defense, or other appropriate authority

whereby noncombatants are evacuated from foreign countries when their lives

are endangered by war, civil unrest, or natural disaster to safe havens or to the

United States. Also called NEO. (JP 1-02)

noncombatant evacuees-- 1. US citizens who may be ordered to evacuate by

competent authority include: a. Civilian employees of all agencies of the US

Government and their dependents, except as noted in 2a below. b. Military

personnel of the US Armed Forces specifically designated for evacuation as

noncombatants. c. Dependents of members of the US Armed Forces. 2. US

(and non-US) citizens who may be authorized or assisted (but not necessarily

ordered to evacuate) by competent authority include: a. Civilian employees of

US Government agencies and their dependents, who are residents in the

country concerned on their own volition, but express the willingness to be

evacuated. b. Private US citizens and their dependents. c. Military personnel

and dependents of members of the US Armed Forces outlined in 1c above,

short of an ordered evacuation. d. Designated aliens, including dependents of

GL-15

Glossary

CJCSM 3122.02B

25 May 2001

persons listed in 1a through 1c above, as prescribed by the Department of

State. (JP 1-02)

non-common-user lift-- Lift not under the control of the US Transportation

Command, usually organic to a particular combatant commander, unit, or

Service such as combatant commander controlled airlift or withhold shipping.

non-unit-related cargo-- All equipment and supplies requiring transportation

to an area of operations, other than those identified as the equipment or

accompanying supplies of a specific unit (e.g., resupply, military support for

allies, and support for nonmilitary programs, such as civil relief). (JP 1-02)

non-unit-related personnel-- All personnel requiring transportation to or from

an area of operations, other than those assigned to a specific unit (e.g., filler

personnel; replacements; temporary duty/temporary additional duty personnel;

civilians; medical evacuees; and retrograde personnel). (JP 1-02)

on-call-- 1. A term used to signify that a prearranged concentration, air strike,

or final protective fire may be called for.

2. Preplanned, identified force or

materiel requirements without designated time-phase and destination

information. Such requirements will be called forward upon order of

competent authority. (JP 1-02)

operation-- A military action or the carrying out of a strategic, tactical, service,

training, or administrative military mission; the process of carrying on combat,

including movement, supply, attack, defense and maneuvers needed to gain

the objectives of any battle or campaign. (JP 1-02)

operational control-- Transferable 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).

Operational control may be delegated and 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 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.

Operational control does not, in and of itself, include authoritative direction for

GL-16

Glossary

CJCSM 3122.02B

25 May 2001

logistics or matters of administration, discipline, internal organization, or unit

training. Also called OPCON. (JP 1-02)

operation order-- A directive issued by a commander to subordinate

commanders for the purpose of effecting the coordinated execution of an

operation. Also called OPORD. (JP 1-02)

operation plan-- Any plan, except for the Single Integrated Operation Plan, for

the conduct of military operations. Plans are prepared by combatant

commanders in response to requirements established by the Chairman of the

Joint Chiefs of Staff and by commanders of subordinate commands in response

to requirements tasked by the establishing unified commander. Operation

plans are prepared in either a complete format (OPLAN) or as a concept plan

(CONPLAN). The CONPLAN can be published with or without a time-phased

force and deployment data (TPFDD) file. a. OPLAN--An operation plan for the

conduct of joint operations that can be used as a basis for development of an

operation order (OPORD). An OPLAN identifies the forces and supplies

required to execute the CINC’s Strategic Concept and a movement schedule of

these resources to the theater of operations. The forces and supplies are

identified in TPFDD files. OPLANs will include all phases of the tasked

operation. The plan is prepared with the appropriate annexes, appendixes, and

TPFDD files as described in the Joint Operation Planning and Execution

System manuals containing planning policies, procedures, and formats. Also

called OPLAN. b. CONPLAN--An operation plan in an abbreviated format that

would require considerable expansion or alteration to convert it into an OPLAN

or OPORD. A CONPLAN contains the CINC’s Strategic Concept and those

annexes and appendixes deemed necessary by the combatant commander to

complete planning. Generally, detailed support requirements are not calculated

and TPFDD files are not prepared. Also called CONPLAN. c. CONPLAN with

TPFDD--A CONPLAN with TPFDD is the same as a CONPLAN except that it

requires more detailed planning for phased deployment of forces. (JP 1-02)

organic-- Assigned to and forming an essential part of a military organization.

Organic parts of a unit are those listed in its table of organization for the Army,

Air Force, and Marine Corps, and are assigned to the administrative

organizations of the operating forces for the Navy. (JP 1-02)

origin-- Beginning point of a deployment where unit or non-unit-related cargo

or personnel are located. (JP 1-02)

personnel increment number-- A seven-character, alphanumeric field that

uniquely describes a non-unit-related personnel entry (line) in a Joint

Operation Planning and Execution System time-phased force and deployment

data. Also called PIN. (JP 1-02)

GL-17

Glossary

CJCSM 3122.02B

25 May 2001

plan identification number-- 1. A command-unique four-digit number

followed by a suffix indicating the Joint Strategic Capabilities Plan (JSCP) year

for which the plan is written, e.g., "2220-95".

2. In the Joint Operation

Planning and Execution System (JOPES) database, a five-digit number

representing the command-unique four-digit identifier, followed by a one

character, alphabetic suffix indicating the operation plan option, or a one-digit

number numeric value indicating the JSCP year for which the plan is written.

Also called PID. (JP 1-02)

planning order-- 1. An order issued by the Chairman of the Joint Chiefs of

Staff to initiate execution planning. The planning order will normally follow a

commander’s estimate and a planning order will normally take the place of the

Chairman of the Joint Chiefs of Staff alert order. National Command

Authorities approval of a selected course of action is not required before issuing

a Chairman of the Joint Chiefs of Staff planning order. 2. A planning directive

that provides essential planning guidance and directs the initiation of

execution planning before the directing authority approves a military course of

action. (JP 1-02)

port of debarkation-- The geographic point at which cargo or personnel are

discharged. May be a seaport or aerial port of debarkation. For unit

requirements, it may or may not coincide with the destination. Also called

POD. (JP 1-02)

port of embarkation-- The geographic point in a routing scheme from which

cargo or personnel depart. May be a seaport or aerial port from which

personnel and equipment flow to port of debarkation. For unit and nonunit

requirements, it may or may not coincide with the origin. Also called POE.

(JP 1-02)

procedure-- A procedure begins with a specific, documentable event that

causes an activity to occur. The activity must produce a product that normally

affects another external organization. Frequently, that product will be the

event that causes another procedure to occur. It is important to recognize that

a procedure determines "what" an organization must do at critical periods but

does not direct "how" it will be done. (JP 1-02)

readiness planning-- Operational planning required for peacetime operations.

Its objective is the maintenance of high states of readiness and the deterrence

of potential enemies. It includes planning activities that influence day-to-day

operations and the peacetime posture of forces. As such, its focus is on

general capabilities and readiness rather than the specifics of a particular

crisis, either actual or potential. The assignment of geographic responsibilities

GL-18

Glossary

CJCSM 3122.02B

25 May 2001

to combatant commanders, establishment of readiness standards and levels,

development of peacetime deployment patterns, coordination of reconnaissance

and surveillance assets and capabilities, and planning of joint exercises are

examples of readiness planning. No formal joint planning system exists for

readiness planning such as exists for contingency and execution planning.

(JP 1-02)

ready-to-load date-- The day, relative to C-day, in a time-phased force and

deployment data when the unit, nonunit equipment, and forces are prepared to

depart their origin on organic transportation or are prepared to begin loading

on US Transportation Command-provided transportation. Also called RLD.

(JP 1-02)

replacements-- Personnel required to take the place of others who depart a

unit. (JP 1-02)

required delivery date-- A date, relative to C-day, when a unit must arrive at

its destination and complete offloading to properly support the concept of

operations. Also called RDD. (JP 1-02)

requirement-- In a time-phased force and deployment data, any force (unit line

number), group of replacement personnel, or resupply that requires

transportation from an origin to a destination in support of an operation plan.

restricted-access plan-- Operation plan with access to operation plan

information extremely limited to specifically designated Worldwide Military

Command and Control System user IDs and terminal IDs during initial course

of action development before the involvement of outside commanders, agencies,

combatant commanders, Services, or the Joint Staff. (Joint Pub 1-02)

resupply-- The act of replenishing stocks in order to maintain required levels of

supply. (JP 1-02)

retrograde cargo-- Cargo evacuated from a theater of operations. (JP 1-02)

retrograde personnel-- Personnel evacuated from a theater of operations who

may include medical patients, noncombatants, and civilians. (JP 1-02)

scheduled arrival date-- The projected arrival date of a specified movement

requirement at a specified location. (JP 1-02)

schedules-- The carrier itinerary which may involve cargo and passengers.

(JP 1-02)

GL-19

Glossary

CJCSM 3122.02B

25 May 2001

scheduling and movement capability-- The capability required by Joint

Operation Planning and Execution System planners and operators to allow for

review and update of scheduling and movement data before and during

implementation of a deployment operation. (JP 1-02)

Service-unique transportation assets-- Transportation assets that are: a.

Assigned to a Military Department for functions of the Secretaries of the

Military Departments set forth in Sections 3013(b), 5013(b), and 8013(b) of

Title 10 of the United States Code, including administrative functions (such as

motor pools), intelligence functions, training functions, and maintenance

functions; b. Assigned to the Department of the Army for the execution of the

missions of the Army Corps of Engineers; c. Assigned to the Department of the

Navy as the special mission support force of missile range instrumentation

ships, ocean survey ships, cable ships, oceanographic research ships, acoustic

research ships, and naval test support ships; the naval fleet auxiliary force of

fleet ammunition ships, fleet stores ships, fleet ocean tugs, and fleet oilers;

hospital ships; Marine Corps intermediate maintenance activity ships, Marine

Corps helicopter support to senior Federal officials; and, prior to the complete

discharge of cargo, maritime pre-positioning ships; d. Assigned to the

Department of the Air Force for search and rescue, weather reconnaissance,

audiovisual services, and aeromedical evacuation functions, and transportation

of senior Federal officials. (JP 1-02)

shortfall-- The lack of forces, equipment, personnel, materiel, or capability,

reflected as the difference between the resources identified as a plan

requirement and those apportioned to a combatant commander for planning,

that would adversely affect the command’s ability to accomplish its mission.

(JP 1-02)

sourcing-- In the development of time-phased force and deployment data, the

process of identifying an actual unit by unit name and unit identification code

for any notional requirement.

subordinate command-- A command consisting of the commander and all

those individuals, units, detachments, organizations, or installations that have

been placed under the command by the authority establishing the subordinate

command. (JP 1-02)

supported commander-- The commander having primary responsibility for all

aspects of a task assigned by the Joint Strategic Capabilities Plan or other joint

operation planning authority. In the context of joint operation planning, this

term refers to the commander who prepares operation plans or operation

orders in response to requirements of the Chairman of the Joint Chiefs of Staff.

(JP 1-02)

GL-20

Glossary

CJCSM 3122.02B

25 May 2001

supporting commander-- A commander who provides augmentation forces or

other support to a supported commander or who develops a supporting plan.

Includes the designated combatant commands and Defense agencies as

appropriate. (JP 1-02)

supporting forces-- Forces stationed in, or to be deployed to, an area of

operations to provide support for the execution of an operation order.

Combatant command (command authority) of supporting forces is not passed

to the supported commander. (JP 1-02)

supporting plan-- An operation plan prepared by a supporting commander or

a subordinate commander to satisfy the requests or requirements of the

supported commander’s plan. (JP 1-02)

sustainability-- The ability to maintain the necessary level and duration of

operational activity to achieve military objectives. Sustainability is a function

of providing for and maintaining those levels of ready forces, materiel, and

consumables necessary to support military effort. See military capability. (JP

1-02)

sustainment-- The provision of personnel, logistic, and other support required

to maintain and prolong operations or combat until successful accomplishment

or revision of the mission or of the national objective. (JP 1-02)

theater-- The geographical area outside the continental United States for

which a commander of a combatant command has been assigned

responsibility. (JP 1-02)

Theater Engagement Plan-- Deliberate engagement plans for all military

activities involving other nations intended to shape the security environment in

peacetime. A TEP is comprised of the CINC’s Theater Engagement Strategic

Concept plus Engagement Activities Annexes. (CJCSM 3113.01, Theater

Engagement Planning, 1 Feb 98)

theater-assigned transportation assets-- Transportation assets that are

assigned under the combatant command (command authority) of a geographic

combatant commander. (JP 1-02)

throughput-- The average quantity of cargo and passengers that can pass

through a port on a daily basis from arrival at the port to loading onto a ship or

plane, or from the discharge from a ship or plane to the exit (clearance) from

the port complex. Throughput is usually expressed in measurement tons,

GL-21

Glossary

CJCSM 3122.02B

25 May 2001

short tons, or passengers. Reception and storage limitation may affect final

throughput. (JP 1-02)

times-- (C-, D-, M-days end at 2400 hours Universal Time (zulu time) and are

assumed to be 24 hours long for planning.) The Chairman of the Joint Chiefs

of Staff normally coordinates the proposed date with the commanders of the

appropriate unified and specified commands, as well as any recommended

changes to C-day. L-hour will be established per plan, crisis, or theater of

operations and will apply to both air and surface movements. Normally, L-

hour will be established to allow C-day to be a 24-hour day.

a. C-day. The unnamed day on which a deployment operation commences

or is to commence. The deployment may be movement of troops, cargo,

weapon systems, or a combination of these elements using any or all types of

transport. The letter "C" will be the only one used to denote the above. The

highest command or headquarters responsible for coordinating the planning

will specify the exact meaning of C-day within the aforementioned definition.

The command or headquarters directly responsible for the execution of the

operation, if other than the one coordinating the planning, will do so in light of

the meaning specified by the highest command or headquarters coordinating

the planning.

b. D-day. The unnamed day on which a particular operation commences or

is to commence.

c. F-hour. The effective time of announcement by the Secretary of Defense

to the Military Departments of a decision to mobilize Reserve units.

d. H-hour. The specific hour on D-day at which a particular operation

commences.

e. L-hour. The specific hour on C-day at which a deployment operation

commences or is to commence.

f. M-day. The term used to designate the unnamed day on which full

mobilization commences or is due to commence.

g. N-day. The unnamed day an active duty unit is notified for deployment

or redeployment.

h. R-day. Redeployment day. The day on which redeployment of major

combat, combat support, and combat service support forces begins in an

operation.

i. S-day. The day the President authorizes Selective Reserve callup (not

more than 200,000).

j. T-day. The effective day coincident with Presidential declaration of

National Emergency and authorization of partial mobilization (not more than

1,000,000 personnel exclusive of the 200,000 callup).

k. W-day. Declared by the National Command Authorities, W-day is

associated with an adversary decision to prepare for war (unambiguous

strategic warning). (JP 1-02)

GL-22

Glossary

CJCSM 3122.02B

25 May 2001

time-phased force and deployment data-- The Joint Operation Planning and

Execution System database portion of an operation plan; it contains time-

phased force data, non-unit-related cargo and personnel data, and movement

data for the operation plan, including: a. In-place units. b. Units to be

deployed to support the operation plan with a priority indicating the desired

sequence for their arrival at the port of debarkation. c. Routing of forces to be

deployed. d. Movement data associated with deploying forces. e. Estimates of

non-unit-related cargo and personnel movements to be conducted concurrently

with the deployment of forces. f. Estimate of transportation requirements that

must be fulfilled by common-user lift resources as well as those requirements

that can be fulfilled by assigned or attached transportation resources. Also

called TPFDD. (JP 1-02)

transportation feasibility-- OPLANs/CONPLANs are considered

transportation feasible when the capability to move forces, equipment, and

supplies exists from the point of origin to the final destination according to the

plan. Transportation feasibility determination will require concurrent analysis

and assessment of available strategic and theater lift assets, transportation

infrastructure, and competing demands and restrictions:

a. The supported commander will analyze deployment, joint reception,

staging, onward movement, and integration (JRSOI); and theater distribution

of forces, equipment, and supplies to final destination.

b. Supporting CINCs will provide an assessment on movement of forces

from point of origin to APOE/SPOE.

c. USCINCTRANS will assess the strategic leg of the TPFDD for

transportation feasibility, indicating to the CJCS and supported commander

that movements arrive at POD consistent with the supported commander’s

assessment of JRSOI and theater distribution.

d. Following analysis of all inputs, the supported commander is responsible

for declaring a plan end-to-end executable.

type unit-- A type of organizational or functional entity established within the

Armed Forces and uniquely identified by a five-character, alphanumeric code

called a unit type code. (JP 1-02)

type unit data file-- A file that provides standard planning data and

movement characteristics for personnel, cargo, and accompanying supplies

associated with type units. (JP 1-02)

GL-23

Glossary

CJCSM 3122.02B

25 May 2001

unit designation list-- A list of actual units by unit identification code

designated to fulfill requirements of a force list. (JP 1-02)

unit identification code-- A six-character, alphanumeric code that uniquely

identifies each Active, Reserve, and National Guard unit of the Armed Forces.

Also called UIC. (JP 1-02)

unit line number-- A seven-character, alphanumeric field that uniquely

describes a unit entry (line) in a Joint Operation Planning and Execution

System time-phased force and deployment data. Also called ULN. (JP 1-02)

unit type code-- A five-character, alphanumeric code that uniquely identifies

each type unit of the Armed Forces. Also called UTC. (JP 1-02)

validate-- Execution procedure used by combatant command components,

supporting combatant commanders, and providing organizations to confirm to

the supported commander and US Transportation Command that all the

information records in a time-phased force and deployment data not only are

error-free for automation purposes, but also accurately reflect the current

status, attributes, and availability of units and requirements. Unit readiness,

movement dates, passengers, and cargo details should be confirmed with the

unit before validation occurs. (JP 1-02)

warning order-- 1. A preliminary notice of an order or action which is to

follow.

(DOD) 2. A CAP directive issued by the Chairman of the Joint Chiefs

of Staff that initiates the development and evaluation of courses of action by a

supported commander and requests that a commander’s estimate be

submitted. 3. A planning directive that describes the situation, allocates

forces and resources, establishes command relationships, provides other initial

planning guidance, and initiates subordinate unit mission planning. (JP 1-02)

WARNING ORDER (Chairman of the Joint Chiefs of Staff)-- A CAP directive

issued by the Chairman of the Joint Chiefs of Staff that initiates the

development and evaluation of COAs by a supported commander and requests

that a commander’s estimate be submitted. See also warning order. (JP 1-02)

GL-24

Glossary

CHAIRMAN OF THE JOINT

CHIEFS OF STAFF

MANUAL

J-3

CJCSM 3212.02C

DISTRIBUTION: A, B, C, and S

20 March 2011

PERFORMING ELECTRONIC ATTACK IN THE UNITED STATES AND CANADA

FOR TESTS, TRAINING, AND EXERCISES

References: See Enclosure N.

1. Purpose. This manual implements guidance for the conduct of electronic

attack (EA) in tests, training and exercises in the United States and Canada.

Background information on the authority to conduct EA and Service

responsibilities for coordinating planned EA are contained in Enclosures A and

B respectively.

2. Cancellation. This manual supersedes CJCSM 3212.02B, 15 October 2003,

which is hereby canceled.

3. Applicability. EA is a subdivision of electronic warfare (EW), a broader term

that also includes the electronic protect (EP) and EW support (ES)

subdivisions. EA is defined as a division of EW involving the use of

electromagnetic energy, directed energy, or anti-radiation weapons to attack

personnel, facilities, or equipment with the intent of degrading, neutralizing, or

destroying enemy combat capability and is considered a form of fires. The

restrictions and procedures covered by this manual, however, specifically refer

to nondestructive radio frequency (RF) EA having the potential to interfere with

authorized RF spectrum use. Specific requirements addressing space-related

EA issues are outlined in Enclosure A of reference a, and must comply with

paragraph 4.14 of reference b, unless otherwise noted. This manual outlines

the coordination requirements and operational procedures governing EA

conducted by U.S. forces in the United States and Canada. It applies to:

a. All Department of Defense (DOD) components in the United States and

Canada that are:

(1) Engaged in EA operations for tests, training, and exercises.

CJCSM 3212.02C

20 March 2011

(2) Operating electromagnetic radiating or receiving equipment that

may be subjected to interference from EA.

b. Contractors performing EA for the DOD. These contractors must meet

the following criteria:

(1) The contractor must be performing under a U.S. military contract.

(2) The EA equipment used by the contractor has been contracted for,

or is owned by, the U.S. Government.

(3) A resident military representative must be available to assist the

contractor in the application of this regulation and in obtaining the EA

clearance approval.

(4) The approved EA clearance must be on file with the DOD office

administering the contract.

4. Procedures. See Enclosures C through H.

5. Summary of Changes. This manual should be reviewed in its entirety. The

guidance and directives herein were revised from the previous version.

Procedures, restrictions, and definitions have been added, updated, or clarified.

Global Positioning System (GPS) EA procedures are now detailed in CJCSM

3212.03. Basic responsibilities and most terms and definitions remain

unchanged.

6. Releasability. This manual is approved for limited release. DOD

components (to include the combatant commands) and other Federal agencies

may obtain copies of this manual through controlled Internet access only

(limited to .mil and .gov users) from the CJCS Directives Home Page, reference

c. Joint Staff activities may access or obtain copies of this manual from the

Joint Staff LAN.

7. Effective Date. This manual is effective upon receipt.

CRAIG A. FRANKLIN

Major General, USAF

Vice Director, Joint Staff

CJCSM 3212.02C

20 March 2011

Enclosures:

A -- Authority to Conduct Electronic Attack

B -- Responsibilities

C -- Frequency Clearance and Notification Requirements

D -- Radio Controlled Improvised Explosive Device (RCIED) EA Frequency

Clearance Requests

E -- EA Coordination Flowcharts

F -- OPSEC Considerations

G -- EA Frequency Clearance Notification

H -- CEASE BUZZER/CEASE MUSIC Procedures

I -- EW Frequency Band Designations

J -- FCC Field Offices

K -- FAA Regional Offices and Areas of Responsibility

L -- DOD Geographic Area of Cognizance/Agencies DOD Area Frequency

Coordinators

M -- NORAD EA Coordination Addresses

N -- References

GL -- Glossary

CJCSM 3212.02C

20 March 2011

DISTRIBUTION

Distribution A, B, C, and J plus the following:

Copies

Director, Developmental Test and Evaluation

Defense Intelligence Agency

Liaison Office National Security Agency

National Defense University

Air War College

President, Joint Forces Staff College

Naval War College

Army War College

Joint Warfare Analysis Center

Joint Spectrum Center

Commander, Air Force Frequency Management Agency

Naval Electromagnetic Spectrum Center

Director, Joint Navigation Warfare Center (JNWC)

Director, Army Spectrum Management Office

Director, Joint IED Defeat Organization

Director, Joint Information Operations Warfare Center/EWD

CJCSM 3212.02C

20 March 2011

TABLE OF CONTENTS

ENCLOSURE

Page

AUTHORITY TO CONDUCT ELECTRONIC ATTACK

A-1

The Communications Act of 1934 as amended by the

Telecommunications Act of 1996

A-1

NTIA Authority

A-1

In Canada

A-1

RESPONSIBILITIES

B-1

FREQUENCY CLEARANCE AND NOTIFICATION

REQUIREMENTS

C-1

Purpose

C-1

EA Coordination

C-1

EA Clearance Request Coordination Requirements

C-1

MILDEP FMOs

C-3

The EA Coordination Process

C-4

Routine, Special, and Short-Notice EA Operations

C-4

Summary of Operations for which EA Clearance Requests are Not

Required

C-6

EA Coordination with Canada

C-6

EA Clearance Request Procedures

C-6

Clearance Requests for Chaff Operations

C-12

RADIO CONTROLLED IMPOVISED EXPLOSIVE DEVICE (RCIED) EA

FREQUENCY CLEARANCE REQUESTS

D-1

Purpose

D-1

Applicability

D-1

Policy

D-2

Responsibilities and Procedures

D-3

Program Executive Officer for Littoral and Mine Warfare, PMS-408 JCREW

for the Joint CREW (JCREW) Acquisition Program of Record and Joint

Improvised Explosive Device Defeat Organization (JIEDDO) for Urgent

Funded CREW Systems

D-4

Joint Spectrum Center (JSC)

D-5

Coordination

D-5

CEASE BUZZER

D-5

EA COORDINATION FLOWCHARTS

E-1

OPSEC CONSIDERATIONS

F-1

EA FREQUENCY CLEARANCE NOTIFICATION

G-1

iii

CJCSM 3212.02C

20 March 2011

Office Responsible for EA Clearance Notification

G-1

Contents of EA Approval Clearance Notification

G-1

In-Flight EA Notification

G-2

Clearance Notification

G-3

CEASE BUZZER/CEASE MUSIC PROCEDURES

H-1

CEASE BUZZER/CEASE MUSIC Procedures

H-1

EW FREQUENCY BAND DESIGNATIONS

I-1

Operational Band and Channel Codes

I-1

EA Coordination Requirements by Frequency Band

I-2

FCC FIELD OFFICES

J-1

FAA REGIONAL OFFICES AND AREAS OF RESPONSIBILITY

K-1

DOD GEOGRAPHIC AREA OF COGNIZANCE/AGENCIES, DOD AREA

FREQUENCY COORDINATORS

L-1

EA Geographic Area of Cognizance

L-1

DOD Geographic Area of Cognizance and AFCs

L-1

M NORAD EA COORDINATION ADDRESSES

M-1

REFERENCES

N-1

GLOSSARY

GL-1

PART I -- ABBREVIATIONS/ACRONYMS

GL-1

PART II -- DEFINITIONS

GL-4

TABLES

Table 1 Example EA Frequency Requirement and Specification Table

C-11

Table 2 Example EA Request CHAFF Information

C-14

Table 3 EW Frequency Band Designations

I-1

Table 4 Coordination Level Required by Channel and Frequency

I-2

FIGURES

Figure 1 EA Coordination

E-1

Figure 2 Eastern AFC Coordination

E-2

Figure 3 AFC Coordination

E-3

Figure 4 FACSFAC Coordination

E-4

Figure 5 Coordination Other Than DOD AFC or FACSFAC

E-5

Figure 6 FAA Region Map

K-4

Figure 7 Map of Geographic Areas

L-4

Figure 8 Map of NORAD Regions and Sectors

M-2

CJCSM 3212.02C

20 March 2011

ENCLOSURE A

AUTHORITY TO CONDUCT ELECTRONIC ATTACK

1. The Communications Act of 1934 as amended by the Telecommunications

Act of 1996. Reference a regulates the frequencies for radio stations “belonging

to and operated by the United States which are assigned by the President.” In

the United States, radio spectrum may be allocated to either federal

government or nonfederal government use exclusively, or for shared use.

Regulatory responsibility for the radio spectrum is divided between the Federal

Communications Commission (FCC) and the National Telecommunications and

Information Administration (NTIA). The FCC, an independent regulatory

agency, is assigned responsibility for the regulation of nongovernment

interstate and foreign telecommunications. The Presidential authority for

federal government RF spectrum use has been delegated to the Administrator,

NTIA, an operating unit within the Department of Commerce.

2. NTIA Authority. The Administrator, NTIA, discharges radio communication

and frequency management functions for the federal government with the

advice of the Interdepartmental Radio Advisory Committee (IRAC). The IRAC

consists of representatives from key government departments and agencies,

including each Military Department. The United States Table of Frequency

Allocations, published by the Federal Register, is the source document listing

authorized federal government and nonfederal government RF spectrum

allocations for the United States. This table defines frequency allocations as

primary and secondary services. Authorized users have the right to operate in

their respective services free from interference. Outside of DOD EW test and

training ranges, EA is not recognized by the NTIA or the FCC as an authorized

service. With the proper coordination, however, EA may be performed under

the condition that harmful interference will not affect authorized services.

3. In Canada. Reciprocity agreements between the United States and Canada

allow U.S. forces to carry out EA exercises within Canadian territory.

Legislative authority can be found in (Canadian) section 12b of the Radio

Communication Regulations made pursuant to section 4(1) of the (Canadian)

Radio Communications Act 1989, c.17, s.2. The Canadian Department of

Industry (Industry Canada) is the national authority for spectrum

management.

A-1

Enclosure A

CJCSM 3212.02C

20 March 2011

ENCLOSURE B

RESPONSIBILITIES

1. This manual sets forth Agency and organizational responsibilities regarding

RF clearance coordination for the performance of EA in the United States and

Canada during tests, training, and exercises.

2. U.S. forces are employed under the authority of the Combatant

Commanders. Services must ensure forces can operate in an intense EW

environment; therefore, DOD training, tests and exercises involving EA are vital

to the effective employment of combat forces. Counter Improvised Explosive

Device (IED) and asymmetric warfare EA requirements have become one of the

most intense and integrated forms of EW on the modern battlefield and

requires continuous development and testing of technology.

3. Reference a is designed to serve national security and defense as well as

other national policies and goals involving spectrum-dependent equipment.

Additionally reference d and as later amended states “The Secretary of

Transportation shall… give full consideration to the requirements of national

defense.” DOD EA operations are a part of national defense and once approved

under the auspices of this manual should not be terminated except as specified

below. Operators will comply with Enclosures C, D, H, and CJCSM 3212.03

for termination of EA (“cease buzzer” procedures). The following are valid

reasons for termination:

a. Safety of flight.

b. Harmful interference.

c. Operations security (OPSEC).

d. Determination of the EA user.

4. The conduct of EA, in areas as defined in this manual’s glossary under the

definitions of Canada and United States and Possessions (US&P), is governed

by this manual under the authority of references d and e. International Civil

Aviation Organization (ICAO) and reference e provide further considerations for

conducting EA within international airspace, but do not govern DOD

component EA operations.

5. The impact of the electromagnetic environment (EME) upon the operational

capability of military forces, equipment, systems, and platforms is referred to

as electromagnetic environmental effects (E3). E3 refers to the impact of the

B-1

Enclosure B

CJCSM 3212.02C

20 March 2011

EME upon the operational capability of military forces, equipment, systems,

and platforms. It encompasses all EM disciplines, including EM compatibility

(EMC) and EM interference; EM vulnerability; EM pulse; EP, hazards of EM

radiation to personnel, ordnance, and volatile materials; and natural

phenomena effects of lightning and precipitation static. Equipment and

systems operating on the principles of electromagnetism are characterized by

EM vulnerability. Once subjected to E3, equipment and systems operating

within, or as part of, the electromagnetic spectrum (EMS), may suffer

degradation and become (incapable of performing the designated mission). The

environmental consequences of EA and its employment must be analyzed in

accordance with provisions of reference f and the accompanying Council on

Environmental Quality Regulations. Consult specific-Service regulations.

B-2

Enclosure B

CJCSM 3212.02C

20 March 2011

ENCLOSURE C

FREQUENCY CLEARANCE AND NOTIFICATION REQUIREMENTS

1. Purpose. This enclosure explains coordination requirements and delineates

procedures for submitting EA clearance request messages.

2. EA Coordination. EA coordination minimizes the likelihood of EA

interference to authorized RF spectrum users. In an increasingly crowded and

dynamic RF spectrum, proper EA coordination serves to protect the portions of

the spectrum currently available for EA from future restrictions caused by

occurrences of unintentional interference. EA coordination is required when a

user desires to conduct EA in a frequency band where authorized users of

primary or secondary services are assigned. National-level coordination

involves submitting an EA clearance request through the applicable Military

Department Frequency Management Offices (MILDEP FMOs) in order to obtain

an EA clearance. In Canada, all EA requires national coordination. In the

United States, some portions of some bands may not require national-level

coordination via an EA clearance request. Even in these cases, however,

coordination with applicable agencies familiar with local EA restrictions is

always required.

3. EA Clearance Request Coordination Requirements. The coordination

requirements for EA in the United States and Canada are based on the desired

EA frequency band, the geographical area, proposed duration and time of the

EA operation.

a. All EA operations conducted in frequency bands annotated as “national”

in Enclosure I require national-level coordination. For these operations, an “EA

Clearance Request for Nationally Controlled Frequencies” must be submitted to

the respective MILDEP FMO for review and approval 60 days prior to the

requested start date. Requests will normally be submitted via message with

the exception of GPS, remote controlled improvised explosive device (RCIED),

and other space-related EA requests, which will normally be submitted via

SIPRNET (unclassified requests may be submitted via NIPRNET). Details

regarding GPS EA requests can be found in CJCSM 3212.03. Other space-

related EA requests will use references a and b for guidance. The proposed

geographical area determines which DOD Area Frequency Coordinator (AFC),

Fleet Area Control and Surveillance Facility (FACSFAC), or Service point of

contact (POC) is responsible for coordinating the EA request and submitting it,

if required, to the respective MILDEP FMO.

(1) Geographic Areas under the Cognizance of DOD AFCs or

FACSFACs. EA clearance request messages will only be submitted to the

C-1

Enclosure C

CJCSM 3212.02C

20 March 2011

MILDEP FMO by the DOD AFC or FACSFAC (for afloat naval operations) having

jurisdiction over a controlled geographic area (Enclosure L). As an exception,

the DOD Eastern AFC (EAFC) at Patrick AFB, FL, requires EA users or

planners requesting to conduct EA along the Eastern Range to first coordinate

with the EAFC and then submit an EA clearance request directly to the

MILDEP FMO.

(2) Areas Not under the Cognizance of DOD AFCs or FACSFACs. For

geographic areas not under the cognizance of an AFC or FACSFAC as listed in

Enclosure L, review COCOM area policy for spectrum support and submission

requirements. EA users must coordinate EA clearance requests through

Service POCs. Users requesting to perform EA under the procedures in this

manual coordinate through established Service POCs and must be familiar

with their Service’s specific procedures. Service POCs are familiar with the EA

coordination process as well as local EA coordination issues. These POCs vary

between Services and geographical areas and are not listed in this manual.

Services may submit them as future changes. EA users not aware of the

proper Service POC to use in the EA coordination process should contact their

MILDEP FMO for that information (paragraph 4 of this enclosure).

b. Frequencies with “Local” or “Local (FCC)” Coordination Requirement.

Frequencies listed in Enclosure I with “Local” or “Local (FCC)” coordination

requirements do not normally require an EA clearance request to be submitted

to the MILDEP FMO. These frequencies have been nationally coordinated.

However, local coordination is still required. Users desiring to perform EA in or

within line-of-sight (LOS) of a DOD AFC or FACSFAC area must coordinate

with that agency. In all other areas not covered under COCOM area of

responsibility (AOR) policy, users coordinate through their Service POCs.

c. Tactical Communications Frequencies. Enclosure I lists frequencies in

the 30-400 MHz region as requiring national-level EA coordination. An

exception to the requirement for national coordination in this band applies to

units conducting EA on assigned tactical frequencies. When EA on these

specific frequencies has been coordinated with the applicable units and EA

parameters fall within the assignment restrictions, no national coordination is

required. For example, EA against communications systems may be conducted

by attaching jamming signal simulators to standard communications

equipment. When this procedure uses assigned communications frequencies

at their assigned power, bandwidth, and location, no special clearance

procedures are required. Service POC coordination is sufficient to determine

whether this situation applies, clearance to enter into an approved MOA is also

clearance to perform EA.

d. Coherent Repeaters. Non-communications coherent repeater jamming

(such as angle deceivers and break lock techniques) does not have a significant

effect on non-victim receivers and does not require an EA frequency clearance.

C-2

Enclosure C

CJCSM 3212.02C

20 March 2011

e. EW Test Equipment/EW Range Emitters. Clearance procedures for the

operation of threat emitters used on EW ranges are not covered in this manual.

The normal frequency assignment process outlined in the NTIA “Manual of

Regulations and Procedures for Federal Radio Frequency Management” should

be used to obtain frequency assignments for devices that are not jammers.

Each of the Services has instructions implementing NTIA manual guidance.

f. EW test equipment falling under certain MIL-STD requirements having

undergone a variety of assessments to determine their vulnerability to EMI, are

waived of any additional requirement for operational certifications or

clearances

4. MILDEP FMOs. The reallocation of federal RF spectrum is an ongoing

process that can affect EA clearance coordination requirements. The MILDEP

FMOs have the latest information on spectrum use and ongoing spectrum

reallocation actions and will factor this knowledge into the national

coordination process. MILDEP FMOs will work with DOD AFCs, FACSFACs,

Service POCs, and users to ensure users desiring to conduct EA are able to do

so while minimizing the impact to other spectrum users. The following are the

MILDEP FMOs for the Services and Canada:

a. Army: Army Spectrum Management Office

2461 Eisenhower Ave

Hoffman I Room 1204

Alexandria, VA 22331-2200

(703) 325-8213/8200 (DSN 221)

DMS MSG ADD: ARMY SPECTRUM MGT (SC)

b. Navy/Marine Corps:

Navy and Marine Corps Spectrum Center

2461 Eisenhower Ave

Hoffman I Room 1201

Alexandria, VA 22331-1500

NMCSC: (703) 325-2822. DSN: 221

DMS MSG ADD: NAVMARSPECCEN

WASHINGTON DC (SC)

c. Air Force: Air Force Frequency Management Agency

2461 Eisenhower Ave

Hoffman I Room 1203

Alexandria, VA 22331-3012

(703) 428-1544 (DSN 328)

DMS MSG ADD: AFFMA (SC)

C-3

Enclosure C

CJCSM 3212.02C

20 March 2011

d. Canada:

ATTN: DTSES 5

National Defence Headquarters

Colonel By Drive

Ottawa, Ontario K1A0K2

(613) 992-8744

DMS MSG ADD: NDHQ OTTAWA//DTSES 5//

5. The EA Coordination Process. All EA operations require coordination with

the applicable AFC or FACSFAC when conducted inside of or within LOS of

their geographic area of jurisdiction. At the initiation of this coordination

process, the DOD AFC or FACSFAC will determine whether local coordination

will meet the EA requirement, whether an existing EA clearance covers the

situation, or whether a new national EA clearance request and notification

procedure is required. For EA operations in other geographic areas, Service

POCs will determine the coordination requirements when not specified by

COCOM guidance. To aid in the understanding of the EA coordination process,

Enclosure E includes a series of flow charts (Figures 1 through 5).

6. Routine, Special, and Short-Notice EA Operations

a. Routine EA Operations. Routine EA operations are defined as frequently

recurring EA training or EA equipment checks with standardized times and/or

procedures in an approved area. Requests for routine EA operations in each

test range area, training area, restricted area, warning area, or military

operating area (MOA) will be submitted through the channels noted above. If

required, the MILDEP FMO will submit requests to the appropriate Federal

Aviation Administration (FAA) and FCC national and regional offices (see

Enclosures J and K) as information addressees. For afloat naval operations,

FACSFACs will submit blanket EA requests for the warning areas where fleet

exercises and EA operations are routine events (such as SOCAL or VACAPES).

When the requester of an EA clearance is notified by the MILDEP FMO of the

approved EA activity for an area, notification should be sent from the requester

(i.e., AFC, FACSFACS, etc.) by message to all users detailing the operating

conditions under which the EA operations are authorized.

(1) Prior to submitting an EA clearance request or scheduling EA

operations, coordination with FAA and FCC regional offices is encouraged. The

MILDEP FMO will affect the final coordination with the FAA headquarters

(ASR-100) and the FCC headquarters (spectrum management and other

applicable national-level agencies) in order to issue an EA clearance

notification for national frequencies. The FAA or FCC headquarters will

normally respond to such EA clearance requests within 30 calendar days of

receiving the request. Approval can be granted for up to a maximum of 1 year

for a specific frequency and/or frequency band, geographic area, altitude, time

of activation, and set of transmission parameters. This allows the conduct of

C-4

Enclosure C

CJCSM 3212.02C

20 March 2011

EA activity on a routine (training or annual exercises) or prescheduled (testing)

basis within the defined operating limits contained in the approved clearance

request.

(2) Test ranges and AFCs having yearly EA clearance requests approved

at the national level can issue clearances for any operation in their area based

on the operating parameters authorized in the EA clearance notification for

national frequencies message. Once a yearly request has been approved, it will

be subject to review and revalidation for reapproval by national level agencies 1

year from the approval date. Users must review and revalidate requirements at

least 45 days prior to expiration of the clearance. If no changes are required,

users submit a new request with the new dates and reference the old

clearance. If modifications to a current authorization are required, they will be

submitted through the MILDEP FMO, with the original approval request

number and dates cited.

b. Special EA Operations. Special EA operations are defined as exercises,

tests, and/or training, conducted on other than a frequently recurring basis.

Special EA operations may require a planning conference for coordination of

operating areas, times, and/or procedures. If the controlling agency for the

area you wish to operate in has an approved clearance for the required

frequency/area, you do not have to submit an EA clearance request as long as

your operations do not exceed the existing assigned parameters. An EA

planning conference is recommended in order to facilitate coordination. The

sponsoring controlling agency will notify appropriate agencies of the planning

conference. If a planning conference is not held, the appropriate controlling

agency or Service-specific POC for each area may coordinate with the regional

FAA or FCC frequency managers and North American Aerospace Defense

Command (NORAD) to expedite the clearance process as necessary.

c. Short-Notice Events. Short-notice events are those events not meeting

the required lead-time for the submission of an EA clearance request. To

minimize the impact of unforeseen clearance needs, the operational user shall

make every effort to predetermine geographic areas, frequencies, time etc., and

submit requirements for routine or special EA operations. When short-notice

approval is needed for bands requiring national coordination, the AFC/Service

POC will contact the Service MILDEP FMO directly and follow up with a

message or written request to the proper addressees. The MILDEP FMO will

determine the urgency of the request and accomplish the required coordination

for approval. When short-notice approval is needed for bands not requiring

national coordination, coordination with the FCC, DOD AFC and/or the

controlling agency for the area shall be accomplished prior to the operation.

d. GPS EA. EA clearance requests for routine, special, and short-notice EA

operations involving emissions on GPS frequencies L1 through L5.

C-5

Enclosure C

CJCSM 3212.02C

20 March 2011

e. RCIED EA. EA clearance requests for routine, special, and short-notice

EA operations involving emissions in the RCIED threat bands must be

submitted 45 calendar days prior to the requested mission start date in order

to allow sufficient time for national coordination and spectrum plot analysis

(see Enclosure D).

f. Space Systems. Specific requirements addressing space-related EA

issues are outlined in reference a and must comply with reference b, unless

otherwise noted.

g. Directed Energy (DE) Systems. Specific requirements addressing DE

issues are outlined in reference a. Laser specific issues must also comply with

reference g.

7. Summary of Operations for which EA Clearance Requests are Not Required

a. EA operations in frequency bands where initial coordination with DOD

AFCs, FACSFACs, Service POCs, or MILDEP FMOs has determined an

applicable EA clearance exists.

b. EA operations in frequencies listed in Enclosure I as “Local” or “Local

(FCC).” Local coordination is still required through the DOD AFC or FACSFAC

when within LOS of their geographical area of jurisdiction, or Service POC in

other areas.

c. Assigned tactical communications frequencies in the 225-400 MHz

region as discussed in subparagraph 3c above.

d. Coherent repeaters as previously described in subparagraph 3d above.

e. EA operations in frequency bands operating in “training-mode.”

8. EA Coordination with Canada. Coordination with National Defence

Headquarters (NDHQ), Ottawa, Director Telecommunications and Spectrum

Engineering and Support 5 (DTSES 5), is required to conduct any EA in

Canada. NDHQ/DTSES 5 (Canadian MILDEP FMO) will accomplish the

coordination for all types of EA including chaff. EA requests are to follow the

procedures outlined in paragraphs 9 and 10 below. MILDEP FMOs will

coordinate applicable EA clearance requests with NDHQ/DTSES 5.

9. EA Clearance Request Procedures. The following information will be

provided when initial coordination determines an EA clearance request is

required for national coordination. Detailed information assists national

coordinating agencies in assessing the impact of EA operations on the RF

spectrum and expedites the approval process. However, do not delay

submission of initial requests to achieve completeness. Follow-on requests can

C-6

Enclosure C

CJCSM 3212.02C

20 March 2011

be forwarded when additional information becomes available. Ensure written

requests are properly classified. See CJCSM 3212.03 for guidance concerning

submission of GPS EA requests and Enclosure D for guidance concerning

submission of RCIED EA requests.

a. Submitting Clearance Requests. EA clearance request messages will be

submitted using the coordination process specified above and in Enclosure E,

for action to the MILDEP FMO.

b. EA Request Information Addressees. Use the following INFO

addressees, as applicable, when submitting EA clearance requests:

(1) CDR USNORTHCOM PETERSON AFB CO//J3/J6/J653/J7//.

(2) CDR USJFCOM NORFOLK VA//J3/J6/J7// and JFMO LANT

NORFOLK VA (for training/exercises conducted under USJFCOM auspices).

(a) AUTODIN MSD ADD: HQ USPACOM HONOLULU

HI//J613/J39// and JFMO PAC HONOLULU HI//J613// for Hawaii OPAREA

within 200 nm.

DMS MSG ADD: HQ USPACOM J6 and JFMO PAC (SC) for

Hawaii OPAREA within 200 nm.

(b) AUTODIN MSG ADD: HQ USPACOM HONOLULU

HI//J613/J39// and JFMO GUAM ISLAND GU for Guam OPAREA within 200

nm.

DMS MSG ADD: HQ USPACOM J6 and JFMO GUAM (SC) for

Guam OPAREA within 200 nm.

(3) CMOC CHEYENNE MOUNTAIN AFS

CO//J3/J35/AWC/MWC/SCC//.

(4) DOD AFC (See Enclosure L).

(5) FAA NATIONAL HQ WASHINGTON DC//ASR-100//.

(6) FAA Regional FMO (See Enclosure K).

(7) Appropriate FAA Air Route Traffic Control Center (ARTCC).

(8) FCC WASHINGTON DC//Frequency Liaison Branch//.

(9) Appropriate FCC field operations office.

C-7

Enclosure C

CJCSM 3212.02C

20 March 2011

(10) Appropriate NORAD regions and sectors that may be affected.

(11) NDHQ OTTAWA//DTSES 5//(for Canadian EA clearances).

(12) HQ USAF WASHINGTON DC// AF/A5RE //, and additionally for

GPS or space-related operations: AF/A3Z-SC, AF/A3Z-ST, AF/A3Z-SO.

(13) COGARD NAVCEN ALEXANDRIA VA//NIS// (for maritime

operations).

(14) DISA JSC COMMCTR.

(15) NTIA WASHINGTON DC.

c. Message Information Requirements

(1) Subject.

(Routine, Special, or Short-Notice).

“EA Clearance Request

For Nationally Controlled Frequencies”

(2) Point of Contact. Enter unit/designator, Service/MILDEP, POC,

commercial and DSN telephone numbers, and e-mail address.

(3) EA Clearance Request Control Number. This number will consist of

an appropriate controlling agency designation/abbreviation, the calendar year,

and a hyphen followed by a consecutively assigned number.

Example: 1ECRG 01-4 is the fourth clearance request for CY 2001 by HQ

ACC, 1st Electronic Combat Range.

(4) Period of Request. From approval date until required review.

(5) EA Operating Areas, Flight Routes, Altitudes, Times and Radius of

Operation

(a) Operating Areas. Specifically define the geographic bounds in

which EA operations will occur. Coordinates will be used to indicate location of

ground-operated EA equipment (not radars or other radar/emitter simulators -

- see subparagraph 3e). Airborne, shipboard, and/or ground-based EA usage

will be defined from a central point (or a group of central points, identified by

geographic coordinates and radius of operations of each). The

name/nomenclature of known MOA(s), restricted areas and warning areas,

flight levels or a combination of these will be included in proposed test areas.

Example: (for warning area) “route of flight within W-368/369

entering from SE” and the central geographic coordinates and

nautical mile radius of test areas.

C-8

Enclosure C

CJCSM 3212.02C

20 March 2011

Example: (Geographic bounds) 3023N 08600W, 3023N 08700W,

2958N 08600W, 2958N 08700W. Operations occur within a 25

nm radius of 302300N 08626W.

(b) Route of Flight. Provide a complete description of the

operational portion of flight routes, including turn points. Include all EA start

and stop geographic coordinates in the area. Specify any flexibility available in

flight routes. Provide an appropriate rationale if variations in activities

preclude providing specific details. Without this rationale or operational

specifics, the resulting clearance may not meet all requirements.

Example: 25 nm N/S and 25 nm E/W routes from a central

point on the Eglin range located at 3023N/08626W. Some test

flights extend further south over water into warning areas W155

and W151A. Routine EA start and stop points are on routes

defined by longitude 08600W to 08700W at a latitude of 3023N

and 2958N to 3048N at a longitude of 08626W, with turn points

at the extreme of each route. Other flight routes are available,

but it is important to maintain certain aircraft/ground simulator

relationships to ensure adequate testing.

sea level (MSL) if over water or over areas where specifying AGL altitude is

impractical. Provide the complete range of altitudes acceptable for operations,

and specify the most desired altitude within the acceptable range. Lower

altitudes increase the probability of approval. Specify AGL altitudes where

chaff drops will occur.

Example: 0 - 50,000 ft AGL; for most operations 20,000 ft is the

most desired altitude for fuel economy reasons. Lower altitudes

can be accepted, but will degrade the continuity of training due

to reduction in flight duration. Flying at 10,000 ft will increase

the cost of operations by an average of 30 percent for fuel.

Flying below 9,000 ft places aircraft in a visual flight rules (VFR)

traffic corridor near the Florida coastline. All use of EA

expendables are at or below 10,000 ft AGL and conducted over

water in W151A.

(d) Topographical Layout. Identify specific terrain features masking

the effects of the proposed EA and reduce unintended harmful interference.

Example: Area of EA operations is bordered by 5,000-7,000 ft

mountains to the north and west.

(e) Times. Provide the daily timeframe in which operations may

occur. Express times in Coordinated Universal Time (UTC) and local time.

C-9

Enclosure C

CJCSM 3212.02C

20 March 2011

State if operating hours are inflexible or limited and why. Identify flexibility in

operating times.

Example: 0000-2400 hrs daily, however, operations are not

continuous, and the operating period is normally no longer than

12 hours, from 0600L-1800L (1100Z-2300Z, 1000Z-2200Z

during daylight savings time) daily with variations based on need

of the testers.

(f) Expected Duration per Activity. Provide expected duration, in

minutes, of an average EA event.

Example: A single EA event lasts no longer than 90 minutes and

may start at any time during the operating period.

(6) Positive Control. Provide information concerning standard

regulations and/or special operating procedures followed, notification

procedures, crew-monitoring procedures, range-monitoring procedures, and

how chaff drops are controlled.

Example: Positive control is provided for all EA activity.

(a) Coordination is accomplished in accordance with this manual,

reference g, and other applicable guidance for specific geographical areas.

(b) Users must monitor appropriate Air Traffic Control (ATC) and

guard frequencies at all times, and range controllers must monitor

communications channels and any jammers employed for frequency drift.

“Cease Buzzer” calls require immediate shutdown of EA operations.

Additionally, a CEASE BUZZER call should be accompanied by the appropriate

band and channel designators whenever possible to preclude unnecessarily

causing all EA training within radio range of the CEASE BUZZER call to be

interrupted or cease (e.g. “CEASE BUZZER, E10, and FOX1”).

chaff is dispensed to determine if conditions are favorable and to preclude

unplanned drifting of chaff clouds. For afloat naval operations, policy prohibits

dropping chaff if predicted impact footprint is within 30 nm of any landmass.

(7) EA Frequency Requirements and Specifications Tables. Provide a

listing of required frequencies and specifications of EA jamming equipment to

be used. Table 1 is an example of an EA jamming requirements table, which

shows the frequency requirements and jamming equipment specifications

delineated below. Ensure information provided is properly classified.

C-10

Enclosure C

CJCSM 3212.02C

20 March 2011

(a) Frequencies Requested. Specify the actual operating frequencies

of each ground, shipborne, or airborne “simulator” or radar that EA will be

conducted against. If the simulator/radar is frequency-agile, give the tuning

limits (or operating channels if tuning range is channelized). In general, if

FAA/FCC bands are affected, they will bracket their restricted frequency ranges

and allow DOD use of the rest of the band, if appropriate.

Frequency/Tuning Range¹

Min BW/PWR

Max BW/PWR

Ant/BMW²

2,400/None

50/20 Watts

200/5 Watts

Horn/120

2,450/2,400-2,600

3,200/3,200-3,400⁴

3,320/3,200-3,400⁴

3,700/3,600-3,800

5,250/5,200-5,400⁵

5,350/5,200-5,400⁵

6,500/6,200-6,800

6,900/None

7,100/6,700-7,400⁶

7,125/6,700-7,400⁶

7,150/6,700-7,400⁶

7,850/7,800-8,500

8,900/7,800-8,400³

50/200 Watts

200/50 Watts

Horn/120

9,150/9,100-9,600

9,160/Fixed

9,200/8,500-9,600

12,700/12,700-13,300

14,500/14,000-15,000⁶

14,750/14,300-15,200

Remarks/Notes:

¹EA in these bands is either noise or deception jamming.

²Effective antenna coverage is within 120^o of the nose and tail of aircraft. Sidelobes 60^o-120o and

240^o-300^o are up to 30 dB down.

³Same bandwidth (BW)/power (PWR)/beamwidth (BMW) as listed in “2400/none” line.

⁴Must have 60-MHz separation between these frequencies.

⁵Must have 100-MHz separation between these frequencies.

⁶Fixed channels in tuning range with 100-MHz separation.

Table 1. Example EA Frequency Requirement and Specification Table

(b) EA Jamming Equipment Specifications. Submit nominal worst-

case equipment parameters, (i.e., do not list every transmitter or jammer

operating in a requested frequency range). Equipment nomenclature is not

required. Provide the following information for each frequency or frequency

range of operation:

1. EA Transmitter Bandwidth and Power. Provide the proposed

bandwidth of the jammer signal at the half-power (-3 dB) points and the

jammer transmitting power in watts. If more than one bandwidth and

transmitter power setting will be used, list the widest bandwidth and its

C-11

Enclosure C

CJCSM 3212.02C

20 March 2011

associated power, as well as the highest transmitter power and its associated

bandwidth.

2. Antenna Gain and Directivity. Provide the antenna gain and

directivity associated with the transmitters in each band of operation. Antenna

gain is specified in dBi, while the antenna directivity is either non-directional or

directional on a specific azimuth or azimuth range, for example 090-120

degrees True North. This information enables the deconfliction of EA and may

preclude interference to others.

3. Remarks Section. Provide a short summary of the proposed

purpose of the EA event. For example, “The purpose of this exercise is to

prepare the carrier battle group for operations in a radar-denied environment.”

Identify types of jamming used (i.e., noise spot, deception jamming, etc.) and

any other pertinent information, such as frequency change limitations or

antenna information.

10. Clearance Requests for Chaff Operations

a. Environmental Policy. Due to the potential environmental hazards,

chaff will not be dropped unless specific authorization is granted from the

Service’s environmental division. Training routes, ranges, and civil airspace in

CONUS must have an approved environmental assessment before chaff may be

released. Once environmental assessments have been accomplished, frequency

clearances may be requested to dispense chaff. Once these requirements are

met, chaff may be dispensed only under the following conditions:

(1) There are no Environmental Protection Agency restrictions in

CONUS restricted air spaces (for example, air-to-ground gunnery ranges, or

warning areas).

(2) Flying activities, complying with FAA regulations, are dispersed over

a wide area and do not frequently (exceeding once per day) pass over the same

ground points.

b. Interference. To eliminate harmful interference in dense air traffic areas

and reduce the number of early EA terminations, every effort should be made

to conduct chaff drops away from major air routes and air route hubs. Winds

aloft will be plotted to ensure the chaff does not drift into major air routes and

air route hubs. Even when chaff dispensing is terminated at the request of the

ATC radar facility, the interference due to chaff may remain for some time.

c. Designated Chaff Drop Areas. Chaff drop areas throughout the

continental United States (CONUS) (primarily within controlled airspace--

MOAs, restricted areas, and warning areas) are established using normal

clearance request procedures per paragraph 5. These areas, in general, were

C-12

Enclosure C

CJCSM 3212.02C

20 March 2011

selected to provide safe separation distances from commercial air routes and

airports. Once a clearance request is approved, any Service organization may

use these areas as long as the activity is scheduled with the controlling agency

(airspace owner), coordinated with the appropriate DOD AFC, conducted within

the limits of the national clearance approval, and compliant with the following

criteria:

(1) Chaff drops must be thoroughly mission planned. For each

mission, consider the following factors during the planning phase:

(a) The geographic features where the chaff is to be dispensed.

(b) The wind conditions aloft.

(d) Allowances for error.

(2) INDIA and JULIET band chaffs may be dropped within the

designated chaff drop areas with minimal restrictions, once an original

clearance request has been approved (refer to Table 2). Interference to FAA

systems by this chaff is considered minimal. However, the ARTCC shall be

notified 10 minutes prior to the scheduled drop.

d. Restrictions on Rope Chaff. Rope chaff requires national-level approval,

in addition to environmental approval. Rope chaff can damage high-voltage

transmission lines and create hazards to life and property. Every precaution

must be taken to ensure the rope chaff falls on water or on land devoid of high-

voltage electric power transmission lines.

e. Chaff Frequency Requirements and Specifications

(1) Frequency Bands Affected. Include the chaff’s cut frequency or

specified frequency response in MHz. INDIA and JULIET-frequency bands are

considered to have the least potential impact on air traffic control radars. State

whether INDIA/JULIET band chaff has been considered for all training/testing.

State under which circumstances other frequency band types of chaff (for

example, RR-180) must be dropped. If it is necessary to drop chaff affecting

the DELTA/ECHO frequency bands, describe safety precautions you intend to

employ to prevent chaff from drifting into air traffic corridors or airport areas.

(2) Chaff Dispensing Information. Provide dispenser type, estimated

fall, and dispersal rates if known, and the amount of chaff normally dispensed.

(3) Remarks or Notes. Add any germane information regarding

specifics of chaff employment.

C-13

Enclosure C

CJCSM 3212.02C

20 March 2011

Type

Frequency Range¹

Resonant Frequencies

Fall Rate

RR-1111

8,000 - 22,000

9, 12, 18, 21 GHz

98ft/min²

RR-0000³

1,500 - 17,000

2, 4, 8, 16 GHz

Same

Remarks: Chaff drop activity is normally about 60 minutes or less in duration. Dispersal

rate varies with wind conditions. The amount of chaff dropped varies between 50 and 500

bundles per operation. The percentage stream and burst is about 20 percent and 80

percent, respectively.

¹Effective Frequency Range. Frequency response range is greater, but radar return is

significantly reduced at lower or higher frequencies.

²Slowest estimated fall rate.

³RR-180 chaff is required periodically for testing of equipment that operates in the lower

portion of its frequency range. Testing cannot be accomplished with RR-172.

Table 2. Example EA Request CHAFF Information

f. Security Instructions. Classify in accordance with reference h and any

applicable classification guides. Enter statement indicating which item entries

singularly or collectively (note compilation rule in the directive) make the

request classified.

C-14

Enclosure C

CJCSM 3212.02C

20 March 2011

ENCLOSURE D

RADIO-CONTROLLED IMPROVISED EXPLOSIVE DEVICE (RCIED) EA

FREQUENCY CLEARANCE REQUESTS

1. Purpose. This Enclosure outlines the coordination requirements and

operational procedures governing RCIED EA tests and training conducted by

U.S. forces and by civilian contractors supporting the DOD. These procedures

are to be used for all testing and training conducted in the United States and

Canada. Current Counter RCIED Electronic Warfare (CREW) systems are used

in supporting major combat operations to prevent IEDs detonated by radio

controlled or RF means. CREW systems are designed to prevent the receiver of

an RCIED trigger from receiving its detonation signal through different forms of

jamming techniques. CREW systems have the potential to cause unintentional

electromagnetic interference (EMI) to civil and military RF spectrum users, with

numerous instances of this occurring causing varying levels of interference and

risk to operations and personnel. As these capabilities are developed, it is

imperative that testing be accomplished, prior to fielding, to determine

effectiveness against a variety of targets, while maintaining compatibility with

other spectrum-reliant equipment, such as Blue Force communications, ISR

systems, Explosive Ordnance Disposal Robots, RADARS, SIGINT, and other

CREW systems. This enclosure provides the requirements and procedures for

submitting RCIED EA frequency clearance requests for testing and training in

U.S. and Canada. It has been closely coordinated with the FAA and FCC to

ensure it meets the required coordination lead-times and technical criteria to

prevent EMI to ATC and non-government systems. Organizations submitting

RCIED EA requests covered in this Enclosure should provide a complete

package as far in advance as possible. The request coordination and approval

progress can be time consuming.

2. Applicability. The restrictions and procedures covered by this enclosure

refer to nondestructive RF emissions generated during EA having the potential

to interfere with authorized RF spectrum use, and apply to:

a. All DOD components in the United States and Canada that are:

(1) Engaged in RCIED operations for tests and training,

(2) Operating electromagnetic radiating or receiving equipment

subjected to interference from EA.

b. Civilian contractors performing RCIED operations development and

testing for the DOD. These contractors must meet the following criteria:

D-1

Enclosure D

CJCSM 3212.02C

20 March 2011

(1) The contractor must be performing under a U.S. military contract.

(2) The EA equipment used by the contractor has been contracted for

or is owned by the U.S. government.

(3) A resident military must be available to assist the contractor in the

application of this manual and the EA clearance approval.

(4) The approved EA clearance must be on file with the DOD office

administering the contract or their delegated representative.

3. Policy. The following request and coordination procedures described in this

manual are required to prevent EMI to ATC and other non-government

systems. These procedures have been developed using lessons learned from

tests, training, and interagency coordination, particularly with the FAA and

FCC. Timelines of less that 65 days may be entertained based on the criticality

of testing required.

a. Requesting units, organizations, and agencies within the CONUS and

Canada will submit complete request packages via the appropriate chain of

command (Major Command (MAJCOM) frequency coordinators, regional and

area frequency coordinators (AFCs), FACSFACs, etc.) for active RF emission in

FAA and FCC frequency bands. Complete request packages must be received

by the MILDEP FMO no later than 60 days prior to the first planned RF

emission. Organizations should plan to submit requests to ensure local and

regional level coordination is complete prior to the 65-day national timeline.

The contents of the EA frequency clearance request package are outlined in

paragraph 6 of this Enclosure. Additional guidance on national level

coordination is provided in references a, b, and d.

b. Local FAA and FCC coordination is not required for RCIED requests.

RCIED requests are only analyzed at the FAA and FCC headquarters.

c. All RCIED requests for frequencies in FAA and FCC bands must include

computer modeling of RF interference to determine areas of potential impact

from RCIED emissions. These impact areas will be produced using an FAA-

approved model, such as the Interactive Scenario Builder model developed by

the Naval Research Laboratory (NRL), and will provide graphic plots to support

analysis of interference to potential victim receivers, i.e., FAA ATC and non-

government systems. A copy of Builder, the current FAA-approved modeling &

simulation (M & S) program, and training can be requested through NRL at

BuilderSupport@nrl.navy.mil, 202-767-6812. The process for collecting data

supporting the builder analysis process is still in development and needs to be

closely coordinated with the CREW PM’s, JIEDDO, JSC, J39, and the

appropriate test range frequency managers.

D-2

Enclosure D

CJCSM 3212.02C

20 March 2011

d. Security Instructions: classify the request package in accordance with

reference i and other applicable classification guides. Enter a statement

indicating which item entries singularly or collectively (note compilation rule in

the directive) make the request package, or parts of it, classified. Even if the

request itself is unclassified, it should be submitted via secure means because

the association of the request with the modeling and analysis reveals a

capability or possible vulnerability. RCIED testing and EA will not compromise

classified capabilities. Security measures to minimize the risk of compromise

should be considered.

e. Safety: RCIED EA and testing must not threaten human life or safety of

flight.

4. Responsibilities and Procedures. The responsibilities described in this

section detail the RCIED coordination process as diagramed in Enclosure E

(Figures 1 through 5).

a. Range Frequency Managers. The frequency managers at the ranges

tasked with RCIED testing shall work with the requestor to prepare the EA

request and the M & S analysis plots. Since M & S software training is

required, all frequency managers tasked/responsible for submitting RCIED

requests need to be trained as soon as practical, well in advance of the 60 day

lead time for submitting an EA package. At the initiation of the coordination

process, the range frequency manager, or other requestor, will determine

whether an existing EA clearance meets the requirement, or whether a new

national EA clearance request and notification is required. All requests must

indicate whether the request is new or is a renewal. If the request is a renewal,

it must include the previous control number and highlight any changes from

the previous request. Ranges should deconflict schedules when there is

overlapping operations within ranges and AFC FMOs should deconflict

surrounding AORs before submission to the Service FMOs.

b. AFCs and FACSFACS. Area frequency managers and/or FACSFACs will

also check the items listed in para 3.a. above. In addition, they must ensure

the requests are complete:

(1) Meet the requirements per this regulation;

(2) and are coordinated with all local entities operating within their

area of responsibility.

(3) If another local or federal agency is impacted by the EA/testing and

has a local representative available, pre-coordinate potential impacts and

deconflict testing schedules to preclude major changes to the EA request after

it is submitted for national-level coordination.

D-3

Enclosure D

CJCSM 3212.02C

20 March 2011

(4) Service MAJCOM, Installation Spectrum Manager(s) (ISM), AFCs,

Testers, and COCOM (s) are required to ensure a complete request package is

submitted, and coordination is complete with affected regional and AFCs.

(5) Submit CREW request packages to MILDEP FMOs via the

appropriate chain of command using SIPRNET email SIPRNET official

government message (DMS, AMHS, AUTODIN), or other secure means, in

accordance with (IAW) appropriate Security Classification Guidelines.

c. MILDEP FMOs. The MILDEP FMOs have the latest information on

spectrum use, ongoing spectrum reallocation actions, and interagency

coordination issues. They will factor this knowledge into the national

coordination process. MILDEP FMOs will work with DOD AFCs, FACSFACs,

ranges and other Service points of contact, and project managers to ensure

users desiring to conduct EA or testing are able to do so while minimizing the

impact to other spectrum users. (MILDEPs will review) MILDEP FMOs, as the

last stop prior to initiating interagency coordination, will check the items listed

in para 3.a. above, verify the originator’s request package and assist in

resolving conflicts between tests or exercises prior to submitting for outside

agency coordination (FAA, FCC, etc.).

5. Program Executive Officer for Littoral and Mine Warfare, PMS-408 JCREW

for the Joint CREW (JCREW) Acquisition Program of Record and Joint

Improvised Explosive Device Defeat Organization (JIEDDO) for Urgent Funded

CREW Systems. JCREW and JIEDDO are together the U.S. center of

excellence for CREW System development, acquisition, and testing.

Accordingly, JCREW and JIEDDO shall:

a. Provide technical support to facilities and or activities in producing or

modifying an EA clearance request and analysis as required.

b. Be available and able to coordinate and provide a forum for DOD

organizations and other federal agencies to convene technical working groups,

as necessary for EA clearance activities.

c. Provide RCIED technical data and advice , as required for required

interagency (i.e.: FAA, FCC) coordination, and dispute resolution meetings, if

necessary. This technical support may include measurement plans or test

protocols that appropriately measure and produce spectral occupation for

analysis and M & S.

d. In Addition, JIEDDO shall:

(1) Be available and able to provide a forum for DOD organizations and

other federal agencies to convene technical working groups, boards,

information as necessary.

D-4

Enclosure D

CJCSM 3212.02C

20 March 2011

(2) Ensure technical and operational support through the JTB for all

counter IED testing.

(3) Continue to facilitate the coordination and sharing of information in

regard to current IED threats and operational EW considerations.

6. Joint Spectrum Center (JSC). The JSC shall provide a quality assurance

(QA) of the requestor’s M & S plots and associated files within 10 working days

of MILDEP FMO notification that M & S plots are ready for review. If questions

arise from JSC’s QA, JSC will contact the requestor directly via SIPRNET e-mail

or telecon. JSC and the requestor will advise the MILDEP FMO, AFC, etc of

any changes to the original request package. The JSC will immediately notify

the MILDEP FMO (and other agencies as required) once the plots are verified

accurate and ready for analysis. The JSC QA will consist of, at minimum, the

following review checks:

a. Accuracy of the transmitter coordinates and/or operating areas.

b. Accuracy of the transmitter technical specifications (i.e. antenna type,

gain, transmitter power (to confirm accurate effective isotropic radiated power),

waveform type, and transmitter bandwidth).

c. Accuracy of the data input including the FCC non-government systems

and FAA’s ATC receiver thresholds and FAA-required M & S parameters.

7. Coordination. The request package consists of two separate components.

One is the EA request message submitted through the appropriate chain of

command to the MILDEP FMO. The second consists of multiple M & S plots

and associated data files, which must be provided both via secure means and

as unclassified data files to JSC for QA checks as annotated in paragraph 6.

The M & S plots provide a geographic and digital representation of potential

interference.

a. Create and submit the RCIED request message using the process

described in Enclosure C.

b. Submit the M & S plots and associated data files to support the

interagency analysis (i.e. FAA and FCC).

8. CEASE BUZZER. These requests will adhere to CEASE BUZZER

procedures as described in Enclosure H.

D-5

Enclosure D

CJCSM 3212.02C

20 March 2011

Eastern AFC

Coordination

User coordinates w/

Service POC

Denied

Service POC

coordinates w/EAFC

End

National

Require local

EAFC

Approved

coordination

FCC or other

approval?

End

required?

coordination?

Yes

User submits EA request

through Service POC

User/Service POC

coordinates with

Local

Approved

Service POC validates

local FCC or

approval?

End

and submits EA

specified agency

Yes

(Note 1)

clearance request to

MILDEP FMO

Denied

End

MILDEP FMO

coordinates EA

Denied

Request

End

Approved

End

Note 1: FCC Watch officer (202) 418-1122

Figure 2. Eastern AFC Coordination

E-2

Enclosure E

CJCSM 3212.02C

20 March 2011

AFC Coordination

(except EAFC)

User Coordinates

with Service POC

Denied

End

Service POC coordinates

with DOD AFC

National

Require local

AFC

Yes

coordination

Approved

FCC or other

approval?

required?

End

coordination?

Yes

AFC submits EA

User/Service POC

clearance request

coordinates with

Yes

to MILDEP FMO

Local

Approved

local FCC or

approval?

End

specified agency

(Note 1)

Denied

MILDEP FMO

End

coordinates EA

Denied

request

End

Approved

End

Note 1: FCC Watch Officer (202) 418-1122

Figure 3. AFC Coordination

E-3

Enclosure E

Military reference books and manuals (2009-2023, Volume 5) - page 18