JOINT OPERATION PLANNING AND EXECUTION SYSTEM VOLUME II PLANNING FORMATS AND GUIDANCE (1999)

CJCSM 3122.03A

31 December 1999

(Format, Civil Affairs Annex)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

ANNEX G TO USCINCEUR OPLAN 4999-99 ( )

CIVIL AFFAIRS ( )

( ) References: List documents providing general guidance applicable to

the conduct of civil affairs activities, including inter-

allied and civil-military agreements affecting civil affairs

functions in the operational area.

( ) Situation

( ) General. Refer to Basic Plan and other annexes, as

appropriate. Emphasize areas affecting displaced persons,

government stability, and destruction or degradation of civilian

infrastructure.

(1)

( ) Establish the legal basis for, and expected scope of, civil

affairs activities in this operation and include identification of

pertinent international and civil-military agreements.

(2)

( ) State the purpose of this annex, which normally is to

provide instructions for guiding all relationships between the

military force and civil authorities and inhabitants in the

operational area.

( ) Enemy. Refer to Annex B, Intelligence. Assess the impact of

enemy capabilities and probable COA on the civil affairs situation,

with particular emphasis on identifying requirements for civil affairs

functions and activities. Summarize the expected civil affairs

situation, including government institutions, customs and attitudes

of the population, and availability of indigenous resources.

( ) Friendly. State the civil affairs functions to be performed by

civilian authorities of the United States and friendly governments in

the operational area. Identify local indigenous assets available to

support and assist in civil affairs activities.

G-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix G

C-463

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) Assumptions. List the basic assumptions on which civil affairs

planning are based, with particular attention to enemy COAs,

availability of indigenous resources, and conclusion of necessary

agreements with foreign governments on forces. Consider making

appropriate assumptions concerning US policy, international and

civil-military agreements, enemy COAs, and availability of host-nation

resources.

( ) Mission. State clearly and concisely, the “essential” tasks to be

accomplished with regard to the purpose of this ANNEX as it relates to

the overall mission stated in the Basic Plan. The mission statement

should address the questions (who, what, when, where and why).

( ) Execution. Civil affairs activities range from civil-military liaison

in the operational area to military assumption of full governmental

powers. The functions required may vary widely within the operational

area or between phases of the operation. Therefore, this paragraph may

require considerable detail and possibly alternative plans. Use

appendixes as necessary to provide long or detailed guidance.

( ) Concept of Operations

(1)

( ) For operations not involving the establishment of a military

government, the concept of CA operations should encompass:

(a)

( ) Operational variations due to alternate COAs in Basic

Plan (appendixes may be needed depending on detail required).

(b)

( ) Support of flexible deterrent options.

(c)

( ) Time-phasing of the operation.

(d)

( ) Deployment and employment of forces to support CA

operations.

(e)

( ) Scope and duration, to include post-conflict CA

operations.

(f)

( ) Clear and concise end states in CA activities, subdivided

as necessary, to describe the successful completion of each

phase and COA.

G-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix G

C-464

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(g)

( ) Planned allocation and use of military units and

resources for the performance of CA functions.

(h)

( ) Principal CA functions to be performed within the

command area, including any significant variations by country,

state, or region.

(i)

( ) Function and operation of civil-military operations

centers (CMOCs), if they are to be established.

(2)

( ) When establishing a military government, or whenever

appropriate to an operation involving less than full legislative,

executive and judicial authority, provide constructive or restrictive

guidance on each CA functional area. Use tabs as required.

Include all details of coordination and authorities here and in the

annex’s coordination paragraph. Consider using a separate plan.

( ) Tasks. List the tasks assigned to each element of the supported

and supporting commands in separate numbered subparagraphs.

When the plan requires the establishment of a subordinate joint force,

assign tasks to the component commanders, supporting commanders,

and subordinate joint force commanders, as appropriate. Each task

should be a concise statement of a mission to be performed either in

future planning for the operation or on execution of the OPORD. The

task must include all key elements required for civil affairs functions.

( ) Coordinating Instructions. List the instructions applicable to

the whole command, two or more elements of the command, and the

command, or its elements, and agencies external to the command.

Areas or events requiring coordination include, but are not limited to:

(1)

( ) Establishment of CA boundaries.

(2)

( ) Liaison arrangements with allied forces and between

subordinate commands.

(3)

( ) Claims policies, in consonance with Appendix 4 to Annex E.

(4)

( ) Application or negotiation of status-of-forces agreements, in

consonance with Appendix 4 to Annex E.

G-3

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix G

C-465

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(5)

( ) Liaison and coordination with US Government and non-US

Government agencies, in consonance with Appendix 4 to Annex E

and Basic Plan.

(6)

( ) Proclamations to be issued to the civil populace, in

coordination with Tab D to Appendix 3 to Annex C, PSYOPs.

(7)

( ) Liaison and coordination with host country, or other

friendly countries, government and nongovernment agencies.

(8)

( ) Emergency measures for defense of civil populations.

(9)

( ) PSYOP support to CA operations.

( ) Administration and Logistics

( ) Military Resource Requirements. State any applicable

requirements to maintain military equipment and supplies for

support of the civil affairs function.

(Refer to Annex D, Logistics.)

( ) Civilian Personnel. Estimate the local civilian labor required

and available to support military operations. (Refer to Annex E,

Personnel.)

( ) Civilian Facilities and Supplies. Estimate the local civilian

facilities and supplies required and available to support the

operation.

(Refer to Annex D, Logistics.)

( ) Reports. Establish any necessary administrative reporting

requirements.

( ) Command and Control. Indicate the difference, if any, between the

command channels for the conduct of civil affairs activities and the

command relationships established in Annex J. Specify command

responsibility for OPCON, ADCON, and logistics of CA activities and

forces (emphasize difference between activities and forces). Include any

changes or transitions between command and control organizations and

G-4

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix G

C-466

Enclosure C

CJCSM 3122.03A

31 December 1999

APPENDIX H

PLANNING GUIDANCE, ANNEX H - METEOROLOGICAL AND

OCEANOGRAPHIC OPERATIONS

1. Purpose. To provide guidance for meteorological and oceanographic

support for operation planning by the combatant commands.

2. General

a. The guidance in this annex supports the preparation of Annex H,

Meteorological and Oceanographic (METOC) Operations, to OPLANS and

CONPLANS with/without TPFDDs and FUNCPLANs.

b. References pertinent to METOC are in Appendix U, “References,”

to CJCSM 3122.01, JOPES, Volume I, “Planning Policies and

Procedures.”

Appendix H

C-469

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Meteorological and Oceanographic Operations Annex)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

ANNEX H TO USCINCEUR OPLAN 4999-99 ( )

METEOROLOGICAL AND OCEANOGRAPHIC OPERATIONS ( )

( ) References: a. Joint Pub 3-59, (date), “Joint Doctrine for

Meteorological and Oceanographic Support”

b. List other documents that provide additional

guidance and information required for use with this

annex.

( ) Situation

( ) Concept of Meteorological and Oceanographic Support. State

the general concept of METOC operations to support the forces

assigned to the OPLAN.

( ) Assumptions. State the assumptions that affect the METOC

operations required by the plan. Provide estimates of the availability

of data and facilities in the operational area, availability of support

from non-US and US nonmilitary agencies, and the feasibility of

obtaining METOC data from satellites.

( ) Planning Factors. Identify any significant METOC conditions

that may influence the execution of the plan. The purpose of this

paragraph should be to establish the requirement for any unusual

METOC operations that will clarify the assignment of specific

responsibilities. Include METOC factors that may influence

operations and the probability of their occurrence.

( ) Resource Availability. Identify items supporting units need to

bring to support the mission for a minimum of 90 days. Identify

conventional and nonconventional weather resources (INTERNET,

IMARSAT, etc.) planned to be used.

H-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix H

C-471

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) Mission. State clearly and concisely, the “essential” tasks to be

accomplished with regard to the purpose of this ANNEX as it relates to

the overall mission stated in the Basic Plan. The mission statement

should address the questions (who, what, when, where and why).

( ) Execution

( ) Concept of Operations. Describe the METOC operations

structure and how it will function in the implementation of the plan.

Refer to other documents available to tasked units that establish

doctrine and procedures, as appropriate. Note any deviations from

standard practices and any additional procedures peculiar to the

operation. Detail marshaling, deployment, employment, and

redeployment in separate numbered subparagraphs.

( ) Tasks and Responsibilities. Identify the Service or Services

responsible for providing space and atmospheric, oceanographic, and

terrestrial environmental support to the operation, including weather

communications and centralized database and production

responsibilities. Include responsibility of the senior METOC officer to

provide forecasts to the supported commander. Assign

responsibilities to specific commands and, where feasible, to specific

units. Include OPSEC planning guidance so OPSEC indicators are

not revealed. In separate numbered subparagraphs for each

applicable component or other subdivision of the force, assign

individual METOC services, tasks, and responsibilities.

( ) Coordinating Instructions. In the final subparagraph, include

the instructions common to two or more components or subdivisions.

( ) Administration and Logistics. Provide broad guidance on how

logistic and administrative support is to be furnished for METOC

operations.

(Reference to Annex D or pertinent command directives may

suffice.)

( ) Command and Control. Indicate the channels for control of

METOC operations if different from the command relationships outlined

in the Basic Plan or in Annex J.

H-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix H

C-472

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) Provide a general statement of the scope and type of METOC

operations C4I support appropriate to the operation. (Reference

Annex K.) Include specific details explaining the METOC

communications concept and requirements in Annex K.

( ) Provide instructions to cover periods when communication

circuits are not operational.

( ) Provide instructions for transmitting METOC information at

echelons where special circuits are not available.

( ) Provide instructions for implementation of METCON,

OCEANCON, and ICECON.

General

Commander in Chief

Appendixes

None specified; however, place appropriate matters in appendixes,

when required by length or detail of the guidance required. Do not

include climate data in appendixes.

OFFICIAL

Colonel

Director, Meteorological and Oceanographic Operations

H-3

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix H

C-473

Enclosure C

CJCSM 3122.03A

31 December 1999

APPENDIX J

PLANNING GUIDANCE, ANNEX J - COMMAND RELATIONSHIPS

1. Purpose. To provide guidance relative to command relationships in

operation planning.

2. General

a. The guidance in this annex supports the preparation of Annex J,

Command Relationships, to OPLANS and CONPLANS with/without

TPFDDs and FUNCPLANs.

b. Appendix U, References, CJCSM 3122.03A, JOPES, Volume I,

Planning Policies and Procedures, lists references pertinent to command

relationships.

3. Command Relationships

a. In conducting US operations, the CINCs exercise command

according to the provisions of Joint Pub 0-2. DOD Directives 5105.19,

5105.21, 5105.22, 5105.31, and 5105.60 indicate the relationship of the

Chairman of the Joint Chiefs of Staff and the CINCs to the Directors of

DISA, DIA, DLA, NIMA, and DTRA. DOD Directives S 3115.7, S 5100.20,

and MJCS 111 88 indicate the relationship of the Chairman of the Joint

Chiefs of Staff and CINCs to DIRNSA/CHCSS.

b. Coordinate support between forces in the same or adjacent areas

according to the UCP and Joint Pub 0-2.

c. Discuss planning for succession of command and change of

command location (i.e., alternate C2 procedures).

d. DOD Directive 5100.51, as amended by Changes 1 and 2

delineates the responsibilities for protection of US citizens abroad. In

support of this directive, give special attention to cooperation and

coordination between US diplomatic and military activities during

periods of tension and hostilities.

e. Discuss command relationships between USIA and the US Armed

Forces in the conduct of PSYOP.

Appendix J

C-475

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Command Relationships Annex)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

ANNEX J TO USCINCEUR OPLAN 4999-99 ( )

COMMAND RELATIONSHIPS ( )

( ) References: a. CJCSI 5130.01A, Relationships between Commanders

of Combatant Commands and International Commands

and Organizations, 31 Aug 97 (S)

b. List other documents that provide necessary guidance

on the command relationships of forces concerned.

( ) General

( ) Purpose. To establish the relationships between:

(1)

( ) The NCA and USCINCEUR.

(2)

( ) USCINCEUR and other combatant commanders.

(3)

( ) USCINCEUR and multinational commands and

organizations.

(4)

( ) Service and functional component commanders and the

commander of the theater special operations command.

(5)

( ) USCINCEUR and subordinate uni-Service forces and CJTFs.

(6)

( ) Coordinating authorities.

(7)

( ) USCINCEUR and other subordinate military activities, such

as MAAGs and missions.

(8)

( ) USCINCEUR and US diplomatic missions.

J-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix J

C-477

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(9)

( ) USCINCEUR and US Government departments or agencies

that support the operations.

(10)

( ) USCINCEUR and forces and agencies of other nations.

( ) Scope. Specify the scope and applicability of the command

relationships established in this annex for specific military operations

or functions within an assigned geographic area; or for specific

military operations or functions not limited to a geographic area, and

the times or circumstances when the relationships become effective.

( ) Command Lines

( ) Service and Functional Components. Indicate which functional

components will be established. Indicate the command lines to

Service and functional components of the force and to subordinate

elements, as appropriate. Indicate whether operations will be

conducted through Service or functional components.

( ) Other Subordinate Commands. Indicate the established

command lines to subordinate commanders for conducting this

operation and the conditions under which forces will be transferred to

their operational control.

( ) Augmentation Forces. Indicate the purpose, time, and

approximate duration of the attachment and the degree of authority

over and responsibility for the augmentation forces.

( ) Alternate Procedures. Discuss procedures for succession of

command and change of command location (alternate C2 procedures).

( ) Specialized Assignments. Indicate the assignment of

specialized coordination and control functions and responsibilities

such as Airspace Control Authority (ACA), Area Air Defense

Commander (AADC), and Joint Rear Area Coordinator (JRAC), if used.

Discuss the authority, duties, and responsibilities of these

assignments.

( ) Operational Areas. Discuss the designation theaters of war and

subordinate theaters of operations for each major threat. Discuss the

J-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix J

C-478

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

establishment of combat zones and communications zones. Indicate

whether other operational areas such as joint operations areas, areas of

operation, amphibious objective areas, joint rear areas, and joint special

operations areas will be designated for subordinate commanders.

( ) Support and Coordination Relationships

( ) Supporting Military Forces. Indicate established relationships

with military organizations operating in support of the originating

command.

( ) Coordinating Authorities. As necessary, assign a commander

or another person the responsibility for coordinating specific functions

or activities.

( ) Supporting Agencies. Indicate the relationships between the

elements of the force and any supporting agencies, such as

DIRNSA/CHCSS and USIA. (Refer to other annexes or appendixes, as

appropriate.)

( ) Inter-Service Support Arrangements. Refer to Annex D,

subparagraph 2b(7), Inter-Service Logistic Support.

( ) Coordination With Diplomatic Agencies. Indicate any

requirement for coordination with chiefs of US diplomatic missions

that is not included elsewhere in the plan and who is responsible for

such coordination.

( ) Relationships With Multinational and Foreign Commands and

Organizations. Indicate established command arrangements or relations

with multinational commands and organizations (for example, NATO,

USELEMNORAD), foreign military commands, or guerrilla organizations.

Also indicate the conditions under which such relations would become

effective.

( ) Planning Relationships. Specify established relationships between

military commands for developing supporting plans. Include any

J-3

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix J

C-479

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Command Relationships Diagram Appendix)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

APPENDIX 1 TO ANNEX J TO USCINCEUR OPLAN 4999-99 ( )

COMMAND RELATIONSHIPS DIAGRAM ( )

( ) There is no specific format for this appendix. However, the diagram

should include only enough detail to give a clear understanding of

command lines and supporting arrangements. If appropriate, show

coordination lines effective upon execution of the OPORD.

J-1-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix J

C-481

Enclosure C

CJCSM 3122.03A

31 December 1999

APPENDIX K

PLANNING GUIDANCE, ANNEX K - COMMAND, CONTROL,

COMMUNICATION, AND COMPUTER SYSTEMS

1. Purpose. To provide guidance for C4 Systems (C4S) in operation

planning. Do not include C4 tasks and purposes. Refer to an

appropriate section of the Basic Plan unless this annex is issued

separately. In that case, include a brief description of the general

situation as it will affect C4 planning.

2. References. CJCSM 3122.01, “JOPES, Volume I, Planning Policies

and Procedures.” See Appendix 1 to Annex A for augmentation forces.

See Joint Pubs 6-0 and 6-02 for C4 systems guidance. See CJCSM

6231.07, “Joint Network Management,” and CJCSIs 3110.09 and

3110.10, “Supplemental Instructions to the JSCP,” for C2W planning

guidance.

Appendix K

C-483

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Command, Control, Communication, and Computer Systems

Annex)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

COMMAND, CONTROL, COMMUNICATION, AND COMPUTER

SYSTEMS ( )

( ) References: a. Joint Pub 6-02, (date), “Doctrine for Employment of

Operational/Tactical C3 Systems”

b. List documents specifically referred to in this plan

element. References are complementary plans,

publications, and C4 systems policy documents.

( ) Situation

( ) Enemy. Assess, in detail, enemy counter C2, signal-intercept,

and computer system entry capabilities that may threaten or

constrain effective friendly command and control. Address enemy

doctrine and capabilities to gain the initiative, achieve surprise, bring

friendly forces to battle on enemy terms, and disorganize friendly

forces during engagements. Discuss past enemy uses of OPSEC

measures, signal interception, deception, jamming, and

lethal/nonlethal attacks on command, control, communication, and

computer systems. Also, define capabilities that represent a threat to

the success of the C4 mission and list exploitable enemy

vulnerabilities.

( ) Friendly. Provide an analysis of friendly C4 facilities,

resources, and organizations that affect the planning of subordinate

commands. Indicate the manner in which C4 forces not included in

the task organization will contribute to the operation. Include

appropriate interoperability considerations for joint, combined, and

neutral forces in the operational area. Place special emphasis on

listing applicable international bilateral arrangements that have been

made to obtain or provide C4 support.

K-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-485

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) Assumptions. State the assumptions that establish essential

criteria for development of the C4 annex; for example, availability of

mobile or transportable CJCS/Service-controlled assets and security

of key facilities outside the combat zone.

( ) Mission. State clearly and concisely, the “essential” tasks to be

accomplished with regard to the purpose of this ANNEX as it relates to

the overall mission stated in the Basic Plan. The mission statement

should address the questions (who, what, when, where and why). Define

the broad tasks and the purpose to establish a basis for “integration” and

“coordination” of actions to be taken.

(The C4 mission statement may

require several subparagraphs in view of the many aspects of C4

support.)

( ) Execution

( ) Guiding Principles. Make maximum use of established

doctrine and include the principles necessary for the coordination

and guidance of all commands and agencies. Mention selected

policies, doctrine, or procedures that need emphasis for guidance in

the operation. State completely any procedures not previously

published that are to be followed during the operation, as well as any

authorized deviations from standard practices.

( ) Operational Concept. Describe the operation briefly, in

narrative form, emphasizing phasing and aspects of the Basic Plan

that establish C4 requirements and that affect C4 capabilities and

limitations. Provide OPSEC planning guidance for planning,

preparing for, and executing command and control (C2) functions,

particularly guidance for transmission and LAN/WAN network

infrastructure security planning.

( ) Tasks and Responsibilities. In separate numbered

subparagraphs for each subordinate component or other subdivision

of the force, assign individual C4 tasks and responsibilities and

include instructions that apply to that component or subdivision.

Cover the entire COA listed in paragraph 5 of the C4 estimate, giving

the task and the unit that is to perform it. Consider liaison team

participation as part of a multinational force to interface C4

K-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-486

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

operations during multinational warfare. Use coordinating

instructions in the final subparagraph to frame tasks and

considerations common to all forces.

( ) Intelligence and Reconnaissance. State intelligence and

reconnaissance support required even if covered in Annexes B and C.

If the information is very detailed, prepare an appendix to the C4

systems annex. Cover MILSATCOM in Appendix 4, if required.

( ) Special Measures

(1)

( ) Provide a separate lettered subparagraph of information

regarding each special measure or procedure necessary for the

support of the mission not covered in paragraph 3.

(2)

( ) Include information on C4 operations that are not part of

the main effort.

(Examples of such measures are routing indicator

allocations, frequency plans, electronic identification procedures,

and analytical assistance provisions for electromagnetic

compatibility and spectrum planning.)

(3)

( ) For Defensive Information Warfare, refer to Appendix 2.

( ) Administration and Logistics

( ) Logistics

(1)

( ) State broad instructions concerning logistic support for C4

operations. Include Annex D and current logistic instructions in

references.

(2)

( ) Repeat important logistic coordination matters even if

covered in Annex D. (Remarks in this paragraph will normally

pertain to inter-Service C4 supply and maintenance matters.) If

the information is detailed, prepare a logistic appendix to the C4

annex. (Examples of items that should appear in this paragraph

are assignments of logistic or maintenance responsibilities to a

single component or other cross-servicing arrangements.)

K-3

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-487

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) Administration. Include requirements for C4 administrative

records and reports and other miscellaneous matters that are

significant to joint operations but are not classified according to any

of the subjects above.

( ) Command and Control

( ) Command. Refer to Annex J for command relationships

( ) Command, Control, Communication, and Computer Systems.

Refer the appendixes for C4 requirements.

General

Commander in Chief

Appendixes

1 -- Information Assurance (IA)

2 -- Command, Control, Communications, and Computer Planning¹

3 -- Satellite Communications Planning

4 -- Defense Courier Service

5 -- Foreign Data Exchange

6 -- Frequency Spectrum Planning

7 -- JTF C4 Deployment Checklist

OFFICIAL

Major General

Director, J-6

¹ Appendix not all-inclusive or specifically required in every OPLAN. Additional

appendixes will be developed as necessary to describe special-purpose

networks or systems; e.g., meteorological and oceanographic services, air-to-

ground, ship-to-shore, air defense.

K-4

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-488

Enclosure C

CJCSM 3122.03A

31 December 1999

PLANNING GUIDANCE FOR APPENDIX 1 TO ANNEX K

INFORMATION ASSURANCE

1. Purpose. To provide guidance for planning Information Assurance

(IA) activities in support of overall operations. IA is a process that

integrates and coordinates policies and procedures, operations,

intelligence, law, and technology to protect information and defend

information systems. IA objectives are to ensure access to timely,

accurate, and relevant information when and where needed, and to deny

an adversary the opportunity to exploit friendly information and systems

for their own purposes. Effective IA implementation ensures the

availability, integrity, authentication, confidentiality, and nonrepudiation

of US Government information and required service levels of US

Government information systems. IA activities are organized around

four fundamental principles: protect, detect, restore, and respond.

a. Protect. Information protection is critical to the military’s ability to

conduct operations. Information producers, processors, and users are

responsible for information protection. Information protection applies to

any medium and form including hardcopy (message, letter, or fax),

electronic, magnetic, video, imagery, voice (radio or telephone, including

cellular), telegraph, teletype, computer, human, etc. Information

protection ensures the accuracy, speed, security, availability, integrity,

authenticity, confidentiality, and nonrepudiation of information. The

information protection process involves determining the scope (what to

protect, based on the value of information), and the standards for

protection (protect to what extent, through the conduct of operations

and the application of protective measures and technologies).

b. Detect. Attack detection requires close cooperation and

coordination among information system developers, vendors,

administrators, and users, service providers, law enforcement, and

intelligence agencies. The speeds at which information system attacks

occur have outpaced our ability to detect and respond via human

means. An automated way to assess the severity (including system

damage, information compromise, and malicious logic insertion) and to

mitigate these effects is essential to effective IA. Timely attack detection

and reporting is key to initiating restoration and response processes.

Threat capability assessment and activity analysis are critical for attack

warning dissemination.

c. Restore. Capability restoration relies on pre-established

mechanisms for prioritized restoration to minimum essential

capabilities. Capability restoration may rely on backup or redundant

Appendix K

C-489

Enclosure C

CJCSM 3122.03A

31 December 1999

links or system components, backup databases, or even alternative

means of information transfer. Design of future information systems and

modification of current information systems must consider incorporating

automated restoration capabilities and other redundancy tactics. In

some cases, required technical restoration capabilities are beyond the

abilities of the affected sites. On-line or deployable restoration

assistance capabilities provide required expertise and tools to restore

services. Common types of restoration assistance are the computer

emergency response team (CERT) and computer incident response team

(CIRT). CERT and/or CIRT type programs exist at DISA, the Services,

and commercially.

d. Respond. Attack response involves determining the methods of

attack and identifying adversary actors and their motives, establishing

cause and complicity, and may involve appropriate action(s) against

perpetrators. The process contributes to information protection by

responding to attacks by direct response or removing threats and

enhancing deterrence by indirect response. Direct response is action

taken to or within a systems to halt or disrupt the attack. Indirect

response is action taken against individuals or groups conducting the

attack. Indirect response may include using law enforcement officials or

military action. For example:

(1) Law enforcement. Law enforcement can contribute to

information protection by imprisoning information criminals.

Imprisoning information criminals may deter other information

criminals/adversaries.

(2) Military Force. Military force is a response option that directly

eliminates the threat, or interrupts the means or systems that an

adversary uses to conduct an attack.

2. Planning Guidance

a. Initiation of IA Planning (Phase 1).

(1) Commands continuously perform IA activities before, during,

and after all military operations. The onset of operational planning to

accomplish a specific mission necessitates considering additional

protective and defensive measures.

(2) CJCS tasking may also initiate specific IA planning.

b. Concept Development (Phase II)

Appendix K

C-490

Enclosure C

CJCSM 3122.03A

31 December 1999

(1) The commander’s decision determines the concept of

operations for each stage of an operation. The commander selects the IA

concept with a view toward how the concept supports the overall concept

of operations.

(2) IA estimate preparation follows many steps similar to the

offensive IO estimate. The IO response cell ensures coordination of these

two estimates.

(3) Estimate preparation includes developing and summarizing

alternative IA COAs.

c. Plan Development (Phase III). Appendix 1 to Annex K documents

the developed IA concept.

d. Plan Review (Phase IV). Plan review determines if the IA concept is

sufficiently broad to effectively support mission achievement.

3. The IA Estimate

a. Planning Problems. IA planning considerations must address two

key requirements.

(1) Determine information requiring protection (what to protect).

(2) Determine incremental protective measure application under

changing situations (standards and protection levels). Protective

measures include passive and active measures to protect friendly

information and systems and measures to deny adversary opportunities

to affect friendly information and information systems. It is not possible

to defend all information at all locations and times. Therefore, risk

assessment methodology must be adopted and applied to a list of

defense priorities.

b. Preparing the IA Estimate

(1) Outline the general situation; state the commander’s tasks and

intentions and the adversary’s assumed tasks and intentions.

(2) Outline the commander’s information needs in each phase of

the operation and protection priorities. Identify organizations and units

involved in IA mission accomplishment. State desired control and

coordination levels.

(3) Identify friendly information systems (including C4 centers,

navigation aids, sensors, and intelligence-gathering capabilities) used in

mission accomplishment.

Appendix K

C-491

Enclosure C

CJCSM 3122.03A

31 December 1999

(4) Determine information system vulnerabilities.

(5) Identify joint and combined friendly forces, host-nation, and

neutral entity actions that degrade information system effectiveness. List

potential effects and mission accomplishment impacts. Determine

alternate information transfer capabilities (message alternate routes,

backup relay/terminal stations or crypto guards, rerouted satellite or

circuit paths, Contingency of Operations Plans (COOP) for processing

data, couriers, etc.) to use during these operations. Coordinate with

friendly activities to maintain friendly information system capabilities in

accordance with established priorities.

(6) Determine appropriate measures and procedures (such as anti-

jamming techniques) to apply to friendly information systems.

(7) Identify enemy capabilities to affect friendly information and

information systems.

(8) Determine measures appropriate for mitigating or minimizing

adversary IO effects.

(9) Identify offensive measures (including offensive information

warfare) to negate adversary offensive IO capabilities. Refer to Annex C

as required.

(10) Determine the restoration priority of all information systems.

Appendix K

C-492

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Information Assurance Appendix)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

APPENDIX 1 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

INFORMATION ASSURANCE (IA) ( )

( ) References: List DOD, CJCS, Service, or command directives, plans,

or guidance documents pertinent to the conduct or

support of IA activities.

( ) Situation

( ) General. Outline IA objectives and how such objectives relate

mission accomplishment (paragraph 2 of the Basic Plan).

( ) Enemy. Refer to Annex B, Intelligence, and appropriate

paragraphs of Annex K for the basic enemy situation. Highlight

enemy capabilities to affect friendly information and information

systems, and operations not already discussed in the "Enemy

Situations" paragraph of Annex K.

( ) Friendly. List the organizations that are not subordinate to this

command and specific tasks assigned to each supporting IA

objectives.

( ) Mission. Refer to the Basic Plan.

( ) Execution

( ) Concept of Operations

(1)

( ) General. Summarize overall concept for ensuring friendly

information access and availability despite enemy IO use. Pay

particular attention to physical security and survivability of

friendly information system capabilities and facilities.

K-1-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-493

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(2)

( ) Phasing. Outline IA activities occurring in each operational

phase. Describe activity sequences in each phase keyed to phase

initiation, and supported operational events. Provide a time-

phased planning guide for accomplishing actions implementing the

IA plan.

( ) Tasks. Identify a command element responsible for

coordinating IA actions. In separate numbered subparagraphs, assign

tasks and responsibilities to each subordinate command to implement

and accomplish IA actions (including identification of vulnerabilities).

( ) Coordinating Instructions

(1)

( ) Integration. Provide detailed instructions for accomplishing

integration of physical security and survivability measures and

other means of performing IA. Provide instructions for mitigation

and/or negation of adversary IO capabilities (refer to appropriate

paragraphs of Annex C as required).

(2)

( ) Coordination. Establish detailed requirements for

facilitating coordinating elements involved in IA. Emphasize close

coordination with IO and other key planners that rely on friendly

information resources. Cross-reference appropriate portions of

other appendixes and annexes to minimize redundancy.

(3)

( ) Security. Establish or reference any special security or

handling requirements for IA planning and actions envisaged by

this appendix.

(4)

( ) Reports. Reference operational reporting requirements

necessary for effective monitoring of IA activities.

( ) Administration and Logistics

( ) Personnel. Identify any requirements for specialized personnel

qualifications and/or augmentation.

( ) Supply. Identify any specialized equipment supply

requirements.

K-1-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-494

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Information Security Tab)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

TAB A TO APPENDIX 1 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

INFORMATION SECURITY (INFOSEC) ( )

NOTE: Address INFOSEC in all OPLANS and CONPLANS with/without

TPFDDs and FUNCPLANs, either as an internal portion of the C4 annex

or as an appendix. As a minimum, address INFOSEC measures and

crypto material considerations.

( ) References: a. DOD D-5200.5, Communications Security (INFOSEC)

b. USAFINTEL 201-1

c. CJCS Instruction 3210.01, 2 January 1996, “Joint

Information Warfare Policy.”

d. CJCS Instruction 6510.01B, 22 August 1997,

“Defensive Information Warfare Implementation.”

e. Joint Pub 3-13, 9 October 1998, “Joint Doctrine for

Information Operations.”

List any other documents that are of primary interest to

the considerations of the plan being developed.

( ) Purpose. Briefly describe the operational situation and the

supporting C4. Summarize areas of the plan requiring INFOSEC

consideration. Emphasize unclassified administrative and operational

reporting, use of changing call signs and frequencies, interoperability,

physical security of INFOSEC material involved, and any other

appropriate INFOSEC area.

( ) General. Provide general objectives, including transmission

security, crypto security, and physical security; all INFOSEC needs and

corrections required to protect the classified content of the plan; security

K-1-A-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-497

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

of the supporting communications; INFOSEC training; and general

responsibilities and appropriate policy guidance.

( ) Execution

( ) Concept of INFOSEC Support Operations. Outline specific

INFOSEC support requirements, including special intelligence (SI)

support.

( ) Tasks. Provide specific tasks for participating and supporting

organizations, including both cryptologistic and cryptologic

organizations and identify the component responsible for joint

issuance of cryptographic materials. Provide guidance on procedures

to obtain cryptography support.

( ) Coordinating Instructions. Provide for specific coordination

among activities concerned.

( ) Administration and Logistics

( ) Identify cryptologistic support responsibilities.

( ) Identify command, control, and logistic support related to

INFOSEC surveillance activities.

( ) Command and Control

( ) Identify specific INFOSEC keying material and crypto systems

to be employed in support of the overall operation.

( ) Provide for control and reporting of compromises of crypto

material and Controlled Crypto-Graphic Items (CCI) incidents.

( ) Provide for control of INFOSEC surveillance support activities.

( ) Identify and provide for joint and multinational INFOSEC

support.

K-1-A-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-498

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Command, Control, Communications, and Computer Planning

Appendix)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

APPENDIX 2 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

COMMAND, CONTROL, COMMUNICATIONS, AND COMPUTER

PLANNING ( )

( ) References: List documents that are of primary interest to the

considerations of the plan being developed.

Note: Numerous sources of information may be used to answer the

checklist questions. The following list is representative:

• Existing operation plans and operation orders.

• The JFC’s planning guidance, estimate, intent, and concept of

operations.

• Area studies.

• Unit files.

• CJCSM 6230.01, "C4 Planners Handbook."

• CJCSM 6231, "Manual for Employing Joint Tactical

Communications."

• CJCSM 6230.04, "Manual for Employing Revised Battlefield

Electronic CEOI Systems."

• CJCSM 6230.05, "Joint Have Quick Planners Manual."

• DISA Contingency Plan 10-95.

• "Joint Communications Support Element Planning Guide."

K-2-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-499

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

• Lessons-learned databases from previous operations and exercises,

especially the Joint Universal Lessons Learned System.

• Systems Description Document, Volumes I & II.

• Time-phased force and deployment data and time-phased force and

deployment list.

• Joint Pub 5-00.2 “Joint Task Force Planning Guidance and

Procedures.”

• Joint Pub 6-0, “Doctrine for Command, Control, Communications,

and Computer (C4) Systems Support to Joint Operations.”

• Joint Pub 6-02, “Joint Doctrine for Employment of

Operational/Tactical Command, Control, Communications, and

Computer Systems.”

( ) Purpose. Provide a brief, general statement of the purpose for this

appendix referencing the objectives of Annex K.

( ) Execution. Provide general procedures for the development and

operation of the communications system.

( ) Tasks and Responsibilities. Identify the tasks and responsibilities

of the component commands and agencies to provide, install, and/or

operate and maintain designated portions of the system. (CINC staffs

must coordinate with the Joint Staff before inclusion of CJCS-controlled

assets in global OPLANs to preclude dual tasking.)

( ) System Description. Described desired connectivity of the system.

( ) Planning Considerations. Provides C4 planners with the

minimum mandatory planning items that must be answered in order to

ensure proper C4 planning. The list is by no means definitive. Each

applicable item should be addressed in appropriate appendixes in Annex

K, or in this appendix.

( ) Common Questions. These questions apply to any mission.

They elicit background information, and each serves as a data point

K-2-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-500

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

to answer other questions. (A more definitive list can be found in

Appendix A to Joint Pub 6-02.)

(1)

( ) Parameters

(a)

( ) Are there any satellite landing rights?

(b)

( ) When are the operations planning meetings scheduled?

How will C4 planning meetings fit into this schedule? Has

DISA been involved regarding coordination of technical

requirements?

(c)

( ) What are the planning constraints?

(d)

( ) What are the special C4 requirements? Who has them?

What national space-based assets are required and/or

available to support the operation? Has a USSPACECOM Joint

Space Support Team been contacted?

(e)

( ) What C4 capabilities are available to the joint force;

Super-High Frequency (SHF) and/or Ultra High Frequency

(UHF) commercial satellite, DSCS, fleet satellite

communications, MILSTAR satellite terminals, JWICS,

MILSTAR, high frequency (HF)/VHF radio, tropospheric and

LOS microwave systems, LANs/WANs, AUTODIN, DMS, DISN,

land mobile radio, and personal communications systems?

(f)

( ) What frequencies are available for the joint operations

area?

(g)

( ) What are the general communications security

(COMSEC) requirements? Will the Intertheater

Communications Security Package (ICP) be used? Which

agency will draft the callout message?

(h)

( ) Who is the potential adversary? What are their

capabilities to conduct offensive information warfare? Does a

joint force plan exist to counter the threat?

(i)

( ) What are the releasability requirements for

multinational operations? What procedures and mechanisms

K-2-3

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-501

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

exist for screening and releasing information to allies; e.g.,

Radiant Mercury or Trusted Guard Operations Intelligence

Work Stations?

(j)

( ) What capacity does the joint command center have to

monitor, direct, control, and coordinate US, allied, and HN C4I

support throughout the entire AOR?

(k)

( ) What are the handling procedures for the air task order

to meet all mission requirements?

(l)

( ) What is the call sign and combat identification process

established to improve friendly coordination and minimize the

possibility of fratricide?

(m) ( ) What portion of the total asset and in-transit visibility

system be established?

(2)

( ) Subordinate Component Forces

(a)

( ) Where will their C4 nodes be located?

(b)

( ) What are their C4 requirements?

(c)

( ) What are their C4 capabilities?

(d)

( ) What type of C4 systems do they have (power, frequency

availability, bandwidth capabilities, interoperability and

compatibility with other subordinate components’ equipment,

and mobility)?

(e)

( ) Which agency is the component C4 staff point of contact

for planning and technical management and direction?

(f)

( ) What are the special C4 requirements resulting from the

mission and the JFC’s estimate, intent, and concept of

operations?

(g)

( ) Are subordinate and supporting C4 plans consistent

with the supported JFC’s C4 plan?

(3)

( ) Supporting Forces and Activities

K-2-4

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-502

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(a)

( ) What is the mission of the supporting forces and/or

activities (this includes allies and coalitions)?

(b)

( ) What are their C4 capabilities?

(c)

( ) What information does the supported JFC need from the

supporting forces and/or activities (intelligence, weather,

imagery, mapping, deployment) and how will it be accessed?

(d)

( ) What C4 support will the supporting forces or activities

require from the supported JFC?

(4)

( ) Nonorganic C4

(a)

( ) DISA

( ) Does the operational area have a DISA Regional

Control Center or field office?

( ) Who is the DISA point of contact?

( ) What is the DISN infrastructure in the operational

area?

( ) Are sufficient gateways available? What are the

interface requirements to access the gateways? Is the

equipment available?

( ) Is Telecommunications Service Provisioning and/or

National Security Emergency Preparedness involving

authority provided and current?

( ) What are the anticipated DSCS and commercial

satellite requirements?

( ) Has modeling of space networks been initiated by

DISA?

(b)

( ) Commercial Networks

( ) Are commercial networks available for use? Who

can approve access to them? Are funds available? Has

K-2-5

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-503

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

DISA been contacted to ensure required lead times for

normal allocations? (1) Satellite (2) Data

(3) Voice

(4)

Video?

( ) What special interfaces are required to access the

commercial network and where are the access points?

( ) What are the locations and types of switches in the

commercial network? What are their technical

parameters?

( ) Where are the locations and types of systems

providing the backbone transmission network?

( ) What type of power is used; voltage, current,

commercial grid, or generator?

( ) Does the operational area have a cellular network?

What are the transmission media, frequency band, and

interface requirements? What are the system standards?

Is the system available for use?

(c)

( ) External Controlled C4 Assets

( ) What USJFCOM or other controlled assets are

available?

( ) What capabilities are available?

( ) Will Joint Communications Support Element (JCSE)

support be required in the operational area, or will other

defense and commercial assets be sufficient?

( ) Will JCSE support be needed for en route

communications?

( ) Has a support request for USJFCOM controlled C4

assets been submitted?

( ) What are the JCSE’s logistic support and electrical

power requirements?

K-2-6

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-504

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) What are the JCSE airlift considerations, allocations,

and/or priority?

(d)

( ) Other C4 Support

( ) Is C4 support needed from specialized

communications units?

( ) Who are the points of contact (POCs), and what are

the request procedures?

( ) What are the units’ C4 capabilities and limitations?

( ) Planning Activities. This paragraph assumes that the basic

questions have been answered and covers high-level and detailed C4

planning. Although these functions are listed separately, they are

concurrent rather than sequential actions. The planners interact to

refine the planning products, C4 estimates, Annex K, and joint

communications-electronics operating instructions (JCEOI).

(1)

( ) High-Level Planning

(a)

( ) What nodes will be necessary to provide a global C4

network and where will they be located?

(b)

( ) Which nodes will have to be connected?

(c)

( ) What transmission media will be used to interconnect

the nodes?

(d)

( ) What types of C4 equipment will be located at each

node (equipment strings, interoperability of the equipment)?

(e)

( ) What are the frequency requirements for each node?

How will the frequencies be allotted (joint, multinational, and

subordinate components)? Are there potential frequency

conflicts?

(f)

( ) What are the call signs and/or words for each node?

K-2-7

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-505

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(g)

( ) What units will provide, install, operate, and maintain

the equipment for each node? What is their operational

readiness status?

(h)

( ) What lift assets are available to deploy these units?

When will the units deploy and activate the nodes or network?

(i)

( ) Is the deployment schedule of C4 assets consistent with

the phases of the plan? Will it permit the provision of C4

support when and where needed?

(j)

( ) What is the phased buildup of C4I in the operational

area?

(k)

( ) Has C4 scheduling information been added to the time-

phased force and deployment data and/or time-phased force

and deployment list?

(l)

( ) Have the JFC and J-3 been informed of potential C4

shortfalls and recommended solutions?

(m) ( ) How will keying material be managed (identification of

Controlling Authorities, ordering, generation, storing,

distribution, transfer, crypto periods, and destruction)? What

are the procedures for handling compromises and CCI

incidents? Is a COMSEC logistics management activity needed

in the joint operations area? What access will allies have to US

COMSEC?

(n)

( ) Are network and node diagrams available?

(o)

( ) Have special C4 requirements been addressed (search

and rescue, SOF, en route C4, embarkation and debarkation

connectivity)?

(p)

( ) How will the joint, JSOTF, subordinate component, and

supporting forces networks interface with nonorganic networks

(DISN, commercial, JCSE)?

(q)

( ) When and where will the Joint Communications Control

Center be established?

K-2-8

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-506

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(r)

( ) Are the subordinate component, JSOTF, and supporting

C4 plans consistent with the joint C4 plan?

(2)

( ) Detailed Planning

(a)

( ) Circuit Switches

( ) Does a circuit switch network diagram exist that

shows information about the switch and circuit switch

network connectivity (switch type, area code, trunk groups,

capacity)?

( ) How does the switch route calls: flood, deterministic,

or circuit switch routing task execution plan?

( ) Where do circuit switches need to be located? How

will they be connected?

( ) What special features or restrictions will be imposed

on subscribers? Who will authorize and enforce these

restrictions?

( ) Where are the Defense Switched Network (DSN)

interfaces? Are precedents authorized? By whom?

( ) How will subscriber assistance be handled?

( ) Where is the greatest anticipated traffic load? Does

sufficient capacity exist to handle it?

( ) What types of status reports are required, and when

and to whom will they be submitted?

( ) How will traffic metering and network loading be

measured, modeled, and managed?

10. ( ) What agency will publish telephone directories and

how will they be distributed?

(b)

( ) Data Networking

K-2-9

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-507

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) What is the anticipated JTF component data

requirements?

( ) Has automation been planned and/or engineered

into the network (x.25, IEEE 802.3, TCP/IP)?

( ) What and/or where are the network identifications

and gateways?

( ) Will data of various classifications "ride" a secure

tactical backbone? How will traffic of various

classifications be controlled and managed? Are multilevel

information systems security initiative devices needed and

are resources available?

( ) What is the joint architecture topology?

( ) Who is the joint data networks manager?

( ) What are the NIPRNET, SIPRNET, and JWICS

connectivity requirements?

( ) What Integrated Tactical Strategic Data Networking

points of presence will be used? Has a gateway access

request been submitted in accordance with DISA

contingency and/or exercise plans?

( ) What is the addressing scheme?

(c)

( ) Message Switches

( ) Where are the message switches required?

( ) What is the trunking plan?

( ) What is the network connectivity of all message

switches?

( ) Have routing indicators been developed and routing

tables established?

( ) Is this an R and/or Y network?

K-2-10

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-508

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) Has a plain language address directory been

created?

( ) How will special category traffic be handled? Who

will be authorized to have access?

( ) What are the intranodal and internodal terminals?

( ) What types of status reports are required and when

and to whom will they be submitted?

10. ( ) What AUTODIN Switching Centers/Defense

Message System Transition Hubs (DTH) are connected to

the message switch?

11. ( ) Who is the Automated Message Process System

Security Officer?

12. ( ) Who will act as the AUTODIN controller?

13. ( ) What are the handling procedures for the air task

order to meet all mission requirements?

(d)

( ) Transmission Systems

( ) Are the circuit requirements, routing,

channelization, and other parameters identified in high-

level planning valid? Have satellite access requests been

submitted? Have frequency requests been approved and

published?

( ) What are the characteristics and connectivity of

multiplexers in the network? Are they compatible?

( ) What are the timing requirements for the network

components? How will timing be accomplished?

( ) What types of status reports are required and when

and to whom will they be submitted?

( ) Technical Management and Direction

K-2-11

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-509

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(1)

( ) Joint Communications Control Center

(a)

( ) What are the operational procedures for the JCCC?

(b)

( ) How will the JCCC be manned?

(c)

( ) What reports will be required, how often will they be

required, and when will they be submitted?

(d)

( ) How will network reconfiguration be accomplished?

(e)

( ) Who are the POCs at the subordinate control centers?

(f)

( ) Who will submit the Telecommunications Service

Request and Telecommunications Service Order?

(g)

( ) Who will coordinate changes to connectivity with the

DISN? With the commercial networks?

(h)

( ) What kind of statistics will be kept? Who will analyze

them? What will be done with them?

(i)

( ) How will changes caused by the evolving tactical

situation be handled?

(j)

( ) How does the JCCC direct changes within subordinate

component networks to optimize C4 within the joint operations

area?

(k)

( ) Where is the boundary between technical direction and

operational direction?

(l)

( ) How will frequency deconfliction be managed? How can

potential conflicts be anticipated?

(m) ( ) Who will control frequency spares and authorize their

use?

(n)

( ) Who manages the allocated satellite bandwidth used by

the geographic joint forces?

(2)

( ) JCSE

K-2-12

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-510

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(a)

( ) Who is the JCSE POC?

(b)

( ) How will JCSE participate in the technical management

process?

(c)

( ) Are there any special reporting requirements for systems

provided by the JCSE?

( ) Other Planning Functions

(1)

( ) Spectrum Management

(a)

( ) What are the provisions and procedures for frequency

planning and use for opposed and/or unopposed entry

operations into a operational area?

(b)

( ) What frequency allotments and assignments are

available for the operational area?

(c)

( ) Can the allotted and assigned frequencies support the

equipment deployed to the operational area (communications,

computer LANs and/or WANs, sensors, surveillance radars,

GPS, airspace control radars)?

(d)

( ) Will the frequencies work (propagation and topographic

analyses)?

(e)

( ) Does the allocation and assignment of frequencies to

subordinate component commands contribute to mission

accomplishment?

(f)

( ) What are the enemy capabilities to interfere with allotted

and assigned frequencies? Does a joint plan exist to counter

the threat?

(g)

( ) How will Joint Spectrum Interference Report (JSIR) be

reported?

(h)

( ) Who will submit JSIR reports to the Joint Spectrum

Center (JSC)?

K-2-13

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-511

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(i)

( ) Will the JCCC resolve electromagnetic interference

issues? Will JSC support be required to resolve interference

issues?

(j)

( ) Are sufficient spare frequencies available?

(k)

( ) What emission control measures will be applied?

(l)

( ) Will the JFC implement an electronic deception plan? Are

sufficient frequencies available to support this plan?

(2)

( ) Security

(a)

( ) Will the cryptographic equipment interoperate?

(b)

( ) What are the keying material requirements?

(c)

( ) Does a key management plan exist?

(d)

( ) How will cryptographic compromises be detected,

reported, evaluated, and corrected?

(e)

( ) What computer security measures will be employed on

the LANs and WANs in the operational area?

(f)

( ) How will access to the various networks be controlled

(electronic and physical)?

(g)

( ) What are the COMSEC emergency destruction

procedures?

(h)

( ) What is the logistics plan for the cryptographic

equipment?

(i)

( ) Are equipment and keymat sufficient to support planned

and unplanned operations?

(j)

( ) What are the key change times and have they been

promulgated?

(k)

( ) What are the provisions for over-the-air rekeying, when

applicable?

K-2-14

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-512

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(l)

( ) Is an ICP available? Is it needed?

(m) ( ) What will we transition to and when?

(n)

( ) What is the foreign information warfare threat facing the

C4I systems?

(o)

( ) Are virus detection software applications installed and

operational? Are passwords issued and in use? Has a

contingency plan been developed to guide recovery actions

should data be modified or destroyed by unauthorized

intrusions?

(p)

( ) Do remotely accessed computer systems possess

features to identify users and substantiate their identification

before allowing information to be processed?

(q)

( ) What are the procedures and mechanisms for screening

and releasing information to allies; e.g., Radiant Mercury or

Trusted Guard Operations Intelligence Work Stations?

( ) Summary. This list of questions is not all-inclusive. These

questions should be asked repeatedly throughout the planning

process as C4 planners adapt to an evolving operational and tactical

situation. They provide a framework for supporting C4 planning for

each phase of an operation, focusing C4 planners on the mission, and

how the JFC intends to accomplish it.

K-2-15

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-513

Enclosure C

CJCSM 3122.03A

31 December 1999

PLANNING GUIDANCE FOR APPENDIX 3 TO ANNEX K

SATELLITE COMMUNICATIONS PLANNING

1. Purpose

a. To provide guidance for planning military satellite communications

(MILSATCOM) support in CJCS-directed OPLANS and CONPLANS

with/without TPFDDs and FUNCPLANs.

b. To prescribe satellite communications (SATCOM) planning and

actions to support operational planning.

c. To support preparation of Appendix 4 to Annex K, Satellite

Communications Planning.

2. References. See Appendix U, CJCSM 3122.01, “JOPES, Volume 1,

Planning Policies and Procedures”. CJCS policy for management of

MILSATCOM systems is in CJCS MOP 37 and Joint Pub 0-2.

Appendix K

C-515

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Satellite Communications Planning Appendix)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

APPENDIX 3 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

SATELLITE COMMUNICATIONS PLANNING ( )

( ) References: List DOD, CJCS, Service, or command directives, plans,

or guidance documents relating to SATCOM support for

the OPLAN.

( ) Situation

( ) General. Outline basic concepts and principles used by the

command in planning SATCOM support for this OPLAN.

( ) Threat. Consider enemy capabilities to disrupt SATCOM

supporting this plan and identify potential effects on OPLAN

execution. Discuss friendly action to mitigate the enemy threat. Also,

discuss coordination details to get specific space weather information

from appropriate channels that may help identify factors that may

negatively impact satellite communications.

( ) UHF SATCOM Requirements. Identify UHF SATCOM requirements

for this OPLAN. Identify specific requirements by attaching a UHF

Network diagram (Tab A).

( ) SHF SATCOM Requirements. Identify SHF SATCOM requirements

for this OPLAN. Identify specific requirements by attaching a SHF

Network Diagram (Tab B). DISA and Regional Signals Intelligence

Support Center (RSSC) will compute capacity required based on SHF

MILSATCOM requirements in Tabs B, C, and D and provide supported

commander results of the analysis to ensure executability of the OPLAN

and to address shortfalls.

( ) Extremely High Frequency (EHF) SATCOM Requirements. Identify

EHF SATCOM requirements to this OPLAN. As applicable, identify

specific requirements by attaching an EHF Network Diagram.

K-3-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-517

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) Commercial Satellite Resources. If applicable, discuss any

planned use of commercial satellite resources. Identify specific

requirements by attaching a Commercial Network Diagram (Tab D).

Include a contingency plan to move service from DoD-owned SATCOM to

commercial SATCOM, should mission requirements dictate.

( ) SATCOM Resources. For all systems (UHF, SHF, EHF, and

commercial), the Regional SATCOM Support Center (RSSC) and/or the

Global SATCOM Support Center (GSSC) will work to provide optimum

SATCOM support to the supported commander. This includes a

shortfall analysis coordinated with the Joint Staff/J6Z, Joint

Communications Satellite Center (JCSC), and the respective SATCOM

System Experts (SSEs)—AFSPC (EHF), NAVSPACE (UHF), ARSPACE

(SHF), and DISA (commercial).

( ) CJCS-Controlled Equipment. Identify and justify any CJCS-

controlled satellite terminal equipment or gateway terminals required to

execute the OPLAN.

( ) DII-DISN Integration. Work with DISA to identify all required

interfaces to allow SATCOM systems integration into the DII-DISN.

Include in the discussion an explanation of how both military ground

entry point interfaces, such as Standard Tactical Entry Point (STEP) sites

and/or commercial teleport requirements, will be used.

Tabs

A -- UHF SATCOM Network Diagram

B -- SHF SATCOM Network Diagram

C -- EHF SATCOM Network Diagram

D -- Commercial SATCOM Network Diagram

K-3-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-518

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, UHF SATCOM Network List Tab)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

TAB A TO APPENDIX 3 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

UHF SATCOM NETWORK LIST ( )

MAX DATA SATELLITE

DADA/

ICDB

CRYPTO

CINC

NETWORK

RATE

AREA

NONDADA

KEYMAT

RANKING

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(1) Network acronym. Enter network acronym defined on CJCS ICDB validation.

(2) Maximum data rate. Enter maximum data rate that will be transmitted by the circuit.

(3) Satellite coverage area. Enter the satellite coverage area under which the terminals fall.

(4) DADA/NONDADA. Enter “D” if the circuit can be satisfied by a DADA channel or “ND” if the

channel cannot be on a DADA channel.

(5) ICDB number. Enter CJCS supporting ICDB number for the network.

(6) Crypto KEYMAT. Enter the short title of the KEYMAT that will be used on the circuit.

(7) CINC ranking. Identify the relative importance of the network compared to other UHF

networks required by the OPLAN. For example, if six networks are required, rank the most

important “1 (1 of 6)” and the least important “6 (6 of 6)”.

Note: Each network must be accompanied by a diagram of the network

which will include terminal ID for each terminal in the network.

K-3-A-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-519

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, SHF SATCOM Network List Tab)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

TAB B TO APPENDIX 3 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

SHF SATCOM NETWORK LIST ( )

DISTANT

END

NETWORK TERMINAL TERMINAL ANTENNA NAMED LAT/LONG DATA

TERMINAL ICDB

TYPE

TYPE/SIZE

LOCAL

OR UTM RATE

NO.

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(1) NETWORK TYPE: Identify as point-to-point, hub spoke, or mesh, as appropriate.

(2) TERMINAL ID: Enter a three-digit alpha-numeric designator for the terminal (example: H01).

(3) TERMINAL TYPE: Enter the terminal nomenclature (example: TSC-85B). If the terminal is a DSCS Gateway, enter

“gateway”.

(4) ANTENNA TYPE & SIZE: Enter the antenna diameter and any special type identifier (example: 20/QRSA).

(5) NAMED LOCATION: Enter location name, if known. Include the unit headquarters supported (example: Ft

Bragg/ARFOR).

(6) LATITUDE/LONGITUDE OR UTM COORDINATES: Enter the geographic coordinates of the terminal.

(7) DATA RATE: Enter the data rate of the uplink to include the link/orderwire overhead.

(8) DISTANT END TERMINAL ID: Enter the three-digit terminal ID for each terminal that will connect to this terminal.

(9) ICDB NO.: Enter the CJCS-assigned support ICDB number for this network.

Note: Each network must be accompanied by a diagram of the network

which will include terminal ID for each terminal in the network.

K-3-B-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-521

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, EHF SATCOM Network List Tab)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

TAB C TO APPENDIX 3 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

EHF SATCOM NETWORK LIST ( )

NETWORK MAX DATA

SATELLITE ICDB

CRYPTO

CINC

NAME/ID

RATE

AREA

NO.

KEYMAT

RANKING

(1)

(2)

(3)

(4)

(5)

(6)

(1) Network acronym or ID. Service name/4-digit Service ID.

(2) Max Data Rate. Enter maximum data rate that will be transmitted by the circuit.

(3) Satellite coverage area. Enter the satellite coverage area that the terminals fall

under (e.g., Milstar, UFO-E, FEP).

(4) ICDB number. Enter CJCS supporting ICDB number for the network.

(5) Crypto KEYMAT. Enter the short title of the KEYMAT that will be used on this

circuit.

(6) CINC Ranking. Identify the relative importance of the network compared to other

EHF networks required by the OPLAN. For example, if 6 networks are required, rank

the most important “1” and the least important “6”.

Note: Each network must be accompanied by a diagram of the network

which will include terminal ID for each terminal on the network.

K-3-C-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-523

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, COMMERCIAL SATCOM Network List Tab)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

TAB D TO APPENDIX 3 TO ANNEX K TO USCINCEUR OPLAN 4999-99

COMMERCIAL SATCOM NETWORK LIST ( )

MAX DATA SATELLITE

DADA/

ICDB CRYPTO

CINC

NETWORK RATE

AREA

NONDADA

NO. KEYMAT RANKING

(1)

(2)

(3)

(4)

(5)

(6)

(7)

(1) Network acronym. Enter network acronym defined on CJCS ICDB validation.

(2) Maximum data rate. Enter maximum data rate that will be transmitted by the

circuit.

(3) Satellite coverage area. Enter the satellite coverage area under which the

terminals fall.

(4) DADA / NonDADA. Enter “D” if the circuit can be satisfied by a DADA channel or

“ND” if the channel cannot be on a DADA channel.

(5) ICDB number. Enter CJCS supporting ICDB number for the network.

(6) Crypto KEYMAT. Enter the short title of the KEYMAT that will be used on the

circuit.

(7) CINC ranking. Identify the relative importance of the network compared to other

UHF networks required by the OPLAN. For example, if 6 networks are required, rank

the most important “1” and the least important “6”.

Note: Each network must be accompanied by a diagram of the network

which will include terminal ID for each terminal in the network. SHF or

EHF commercial SATCOM requirements should be presented as separate

Exhibits to this Tab.

K-3-D-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-525

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Defense Courier Service Appendix)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

APPENDIX 4 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

DEFENSE COURIER SERVICE ( )

( ) References: List documents specifically referred to in this plan

element.

( ) Purpose. To provide instructions to guide support relationships

between the Defense Courier Service (DCS) and supported units.

Summarize areas of the plan requiring courier consideration,

emphasizing required frequency of service and protection, control, and

movement considerations of the most sensitive classified materials

concerned.

( ) General. Provide general objectives, including qualification of

material to be transported, command responsibilities, and appropriate

policy guidance. In addition, if national disclosure policy or other

releasability/disclosure authorities are needed, annotate with an outline

of how those authorities will be requested.

( ) Concept of Defense Courier Service Support Operations. Outline

specific requirements for courier service support, including special

movement requirements. Define the scope of service, based on DCS

projection of service to major subordinate commands only.

( ) Task. Provide specific tasks for DCS and supported

commands. Identify component commands responsible for providing

support to DCS, including facilities, surface, and air transportation.

( ) Transportation Policies. List currently approved categories of

qualified material or refer to appropriate policy documents. Identify

requirements for movement in the TPFDD files and cross-referenced

in this appendix.

( ) Courier Operations. Establish the general concept for DCS

operations, including service provided to allied organizations, nature

K-4-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-527

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

and level or command responsibility (including staff element) for

interface, and distribution and dispatch of qualified material.

Distinguish between DCS couriers, command couriers, and

messengers when assigning these responsibilities. Provide geographic

locations and command identifier and organizations to be supported

by DCS. Identify theater port of entry and dispatch for air movement

of courier material.

( ) Coordinating Instructions. Assign staff responsibility for

courier matters at all echelons of command and provide for specific

coordination among activities concerned.

K-4-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-528

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Foreign Data Exchanges Appendix)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

APPENDIX 5 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

FOREIGN DATA EXCHANGES ( )

( ) References: List DOD, CJCS, Service, command, or international

directives, plans, or guidance documents specifically

referred to in this plan element. pertinent to the foreign

data sharing.

1. Purpose. Provide a summary of categories and types of information

exchanges, by country, needed to effectively and efficiently execute the

plan. Summary must include data provided to foreign countries, data

provided from foreign countries and data generated cooperatively by two

or more countries.

2. General. Outline the information to be either disclosed to, released to

or received from foreign entities and the planned approach, including

safe guarding steps to be taken. In addition, if national disclosure policy

or other releasability/disclosure authorities are needed, annotate with an

outline of how those authorizations will be requested.

3. Execution.

a. Concept of Foreign Data Sharing Support Operations. Outline

specific Foreign Data Sharing requirements, including overall foreign

data sharing approach. Outline procedures to prevent unauthorized

disclosure and release of classified information on SIPRNET and

JWICS.

b. Tasks. For each country with which data is to be shared,

completion of an entry for each data element in the following chart is

required. In subsequent paragraphs, provide approaches to sending,

receiving, safeguarding, and utilizing the shared data.

K-5-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-529

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

Information Category/

Disclosure

Participant

Exchange Direction

Approvals In

Timeframe

Country

(Send/Receive)

place?

Purpose

of Need

Objectives

Resources

Participant Country. Indicate the country or countries which

information exchanges are required.

Information Category/Exchange Direction. Indicate the category of

information to be exchanged (e.g., command and control, near real-time

early warning, etc., as well as the anticipated security level of the

information) and the exchange direction (to US, from US, or

bidirectional).

Disclosure Approvals In Place. Indicate if the required national-level

information disclosure approvals have been requested and received for

each information exchange indicated. If covered under standing or pre-

established agreements, indicate agreement.

Purpose. State the rational for the information exchange and expected

outcomes. What is the perceived benefit of the information exchange.

Timeframe of Need. Indicate when the information is required, planning

phases, prehostilities, OOOW, campaign execution, etc..

Objectives. What are the objectives of the information exchange itself

(i.e., provide early warning within two minutes, etc.)?

Resources. Identify resources required to conduct the information

exchanges (e.g., personnel, ADP support, training, equipment). Indicate

whether the information exchange is currently established (and funded).

Identify processes and/or resources (e.g., electronic high assurance

guards) to prevent unauthorized foreign national access to SIPRNET and

JWICS.

K-5-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-530

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Frequency Spectrum Planning Appendix)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

APPENDIX 6 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

FREQUENCY SPECTRUM PLANNING ( )

( ) References: a. Theater Spectrum Management

Manual/Regulation/Instruction.

b. CJCSI 3220.01, “Electromagnetic Spectrum Use in

Joint Military Operations”

c. CJCSM 3220.01, “Joint Operations in the

Electromagnetic Battlespace”

d. CINC Directive 00-01, “Joint Task Force Headquarters

and Standing Operating Procedures (JTF HQ SOP)” ( )

( ) Purpose. To provide guidance for frequency spectrum planning

(Electromagnetic Battlespace Management) to support operations in the

electromagnetic battlespace (EMB). The EMB is the three dimensional

environment of the battlefield and includes background environmental

information (BEI); and hostile, friendly, UN, coalition, and host-nation

forces electronic order of battle (EOB).

( ) General. Electromagnetic battlespace management provides for

efficient use of all frequency emitters within an AOR. This enormous

task requires substantial coordination between the J-2, J-3, and J-6.

This evolved concept of spectrum-use planning and management

ensures electromagnetic compatibility (EMC) and frequency

supportability of telecommunication requirements (including

weapon/radar systems) and electronic requirements (i.e., sensors);

frequency assignment; electromagnetic interference (EMI) resolution; EW

deconfliction; JCEOI and Joint Restricted Frequency List production;

and database management of frequency resources.

K-6-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-531

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) Specific. Given the complexity of systems and communication

requirements on the battlefield to effectively manage the electromagnetic

battlespace, the JFMO (JTF Spectrum Management Element (JSME)

when stood up) will maintain centralized control, with decentralized

execution of frequency resources to components. The JFMO/JSME will

coordinate all frequency requests with nation “X” and allies. Component

spectrum managers will submit requests for frequencies in Standard

Frequency Action Format (SFAF) to the JFMO/JSME, and will manage all

spectrum assets once approved.

( ) Resourcing agreements between the CINC and component

commanders, and staff relationships among the J-2, J-3, and J-6

must be firmly established to ensure success in a short/no-notice

deployment of forces. Specifically, force deployment information must

be shared with the J-6 to ensure frequency supportability for units

arriving into theater.

( ) Current joint doctrine calls for each JTF to form a JTF

Spectrum Management Element, comprised of frequency managers

from each Service component expected to commit forces, and for a

Joint Commanders Electronic Warfare Staff (JCEWS) to facilitate

coordination among J-2, J-3, and J-6. When standing multiple JTFs,

the JSME should be collocated with the lead JCCC.

( ) To prevent electronic fratricide, the JSME must be stood-up

during predeployment, or during crisis assessment (when in crisis

action planning) to ensure frequency supportability/compatibility and

friendly force control of the EMB prior to deployment of forces.

( ) The BEI of the AOR needs to be developed to protect tracking,

telemetry and control (TTC) links for smart munitions, current

frequency assignments, the standing theater JRFL, area studies,

international assignments (ITU), and intelligence sources.

( ) The CINC ensures the JCEOI is developed to reflect current

force deployment plans. The Master Net List will contain all possible

component forces, call word dictionaries, and CINC suffix and

expander listing.

( ) Training plans should emphasize CINC spectrum management

operations, cover Service unique, joint, UN, allied, and coalition

K-6-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-532

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

policies and procedures, and spectrum management software

applications.

( ) Planners need to ensure intelligence/operations input is

provided to the JRFL to protect critical C2 circuits (weapon/radar

systems), intelligence collection, and safety of life from friendly EW

effects. The end result is the IO/EW cells need to share mission

specific requirements for JSME to conduct EW deconfliction and

identify mission impacts.

( ) The CINC JFMO must establish procedures for granting the

JSME “military assignment” frequency authorization for critical

systems when host-nation approval is not forthcoming.

( ) Responsibilities

( ) JFMO/JSME

(1)

( ) Establish JTF command policy on the use and management

of the spectrum.

(2)

( ) In accordance with J-5 guidance, coordinate spectrum use

with the host-nation/allied spectrum management authorities.

(3)

( ) Serve as the senior frequency assignment coordination

authority for subordinate task force units, and develop and

distribute spectrum-use plans.

(4)

( ) Provide representation to the JCEWS.

(5)

( ) Combine inputs from all JTF staff levels and components

and develop a proposed JRFL for J-3 approval.

(6)

( ) Maintain and publish J-3 approved JRFL.

(7)

( ) In conjunction with J-6, and in coordination with the J-3,

develop, publish, promulgate, and maintain the JCEOI.

(8)

( ) Provide administrative and technical support for spectrum

use.

K-6-3

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-533

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(9)

( ) Maintain the common database for planning, coordinating,

and controlling spectrum use.

(10)

( ) Implement JSIR procedures IAW CJCSI 3220.02.

(11)

( ) Evaluate, analyze, and attempt to resolve interference

incidents at the lowest level possible.

(See Tab A for JSIR report

format).

( ) JTF J-3

(1)

( ) Establish net structure for developing into the JCEOI.

Provide inputs to the JFMO/JSME.

(2)

( ) Approve JRFL for publication and dissemination.

(3)

( ) Resolve spectrum-use conflicts between users IAW

commander’s priorities (e.g., J-2 requirement to exploit vice J-6

requirement to communicate).

(4)

( ) Provide frequency-input list to JCEWS for inclusion into the

JRFL.

( ) JTF J-2

(1)

( ) Provide GUARDED frequency list to JCEWS for inclusion

into the JRFL.

(2)

( ) Assist in the resolution of interference incidents.

( ) Component Commands

(1)

( ) Submit spectrum requirements in SFAF format to JSME.

Nominate specific frequencies to be coordinated with nation “X”. If

coordination with nation “X” is required, each proposal must

contain a releasability code in SFAF item 005.

(2)

( ) Ensure users comply with their frequency assignment

parameters (power, bandwidth, and location).

K-6-4

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-534

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(3)

( ) Attempt to resolve any frequency conflicts and interference

incidents locally. If resolution cannot be accomplished, report to

JSME for resolution.

(4)

( ) Provide frequency list to JCEWS for inclusion into the JRFL.

( ) Deploying units

(1)

( ) Submit frequency requests in SFAF format through higher

headquarters to JFMO/JSME.

(2)

( ) Ensure only those frequencies assigned are used and

comply with parameters of the assignment; e.g., power, bandwidth,

and location.

(3)

( ) Attempt to resolve any frequency interference incidents

locally. If unable to resolve, comply with CJCSI 3220.02, Joint

Spectrum Interference Resolution.

( ) Administrative

( ) Service component frequency managers operating under JTF

“X” will consolidate frequency requests from subordinate units and

forward these requirements to the JFMO/JSME.

( ) Automation. The Joint Spectrum Management System for

Windows (JSMSW) is the standard database management system.

The JCEOI will be developed using the Revised Battlefield

Communications Electronic Operating Instructions System (RBECS).

Transmission of frequency requests and assignments will be via

electronic mail, AUTODIN message, PC-to-PC transfer, or diskette.

( ) Security Classification

( ) Frequency requests will be classified at the lowest level

possible. If classified, each SFAF item will have a classification

marking (U, C, or S) prior to the text.

K-6-5

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-535

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Electromagnetic Interference (EMI) Reporting Tab)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

TAB A TO APPENDIX 6 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

ELECTROMAGNETIC INTERFERENCE (EMI) REPORTING ( )

( ) References: a.

( ) Theater Spectrum Management

Manual/Regulation/Instruction

( ) CJCSI 3320.02, Joint Spectrum Interference

Resolution Program

( )CINC Directive 00-01, Joint Task Force

Headquarters and Standing Operating Procedures (JTF

HQ SOP).

( ) General. This Tab to Appendix 4 provides guidance and direction

for reporting interference incidents encountered during Operation JTF

“X”.

( ) Procedures

( ) Interference incidents will be reported using the enclosed

format. All reports of suspected hostile interference will be submitted

via secure means.

( ) The operator/user experiencing the interference is responsible

for submitting the interference report. All interference reports

submitted during this JTF Operation will be coordinated through the

component C2W office before transmission.

( ) Attempt to resolve interference problems at the lowest levels

possible before submitting JSIR reports to higher headquarters.

( ) Definitions

K-6-A-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-537

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(1)

( ) Meaconing. A system of receiving radio beacon signals and

intentionally rebroadcasting them on the same frequency to

confuse navigation.

(2)

( ) Intrusion. The intentional insertion of electromagnetic

energy into transmission paths in any manner with the objective of

deceiving operators or causing confusion.

(3)

( ) Jamming. The deliberate radiation, reradiation, or

reflection of electromagnetic energy to disrupt use of electronic

devices, equipment, or systems.

(4)

( ) Unintentional disruptions are known as interference.

( ) Interference reports are submitted at a minimum to the

following addresses depending on type of report:

(1)

( ) Hostile Interference

ACTION: JSME

CINC JFMO

JC2WC SAN ANTONIO TX//OWS//

INFO:

NSACSS FT GEORGE G MEADE MD//W9M//

DIA WASHINGTON DC//PGI-3A//

OTHER COMPONENT COMMANDS

THEATER CINC

(2)

( ) Interference involving Space Systems

ACTION: JSME

CINC JFMO

CMOC/SCC CHEYENNE MOUNTAIN AFS

CO//SCC//

INFO:

JSC ANNAPOLIS MD//OP/JSIR//

K-6-A-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-538

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

DISA ARLINGTON VA//DITF/UTTF// (Only for DSCS

systems)

DISA WASHINGTON DC//333//

OTHER COMPONENT COMMANDS

THEATER CINC

(3)

( ) Nonhostile Interference

ACTION: CINC JFMO

JSME/

INFO:

JSC ANNAPOLIS MD//OP/JSIR//

OTHER COMPONENT COMMANDS

THEATER CINC

( ) Reporting Format. To the maximum extent possible the JSIR

generation capability in JSMSW will be used. If it is not available,

then submit the following as minimum.

(1)

( ) Organization affected by EMI. Point of contact information:

Name and telephone number. Make sure when listing a POC that

individual is familiar with the problem.

(2)

( ) Place name, latitude, and longitude where EMI occurred.

(3)

( ) Times, dates, periods EMI occurred. Indicate whether the

duration of the interference is continuous or intermittent, the

approximate repetition rate of interference, and whether the

amplitude of the interference is varying or constant. Indicate if the

interference occurs at a regular or irregular time of day.

(4)

( ) Systems and equipment affected by the EMI. Affected

system function, name, nomenclature, manufacturer with model

number or other system description.

K-6-A-3

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-539

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(5)

( ) Allocated frequency band or authorized frequency of

equipment affected.

(6)

( ) Station and/or equipment causing the interference and the

location or call sign, if known.

(7)

( ) Allocated frequency band or authorized frequency of the

station and/or equipment causing the interference, if known.

(8)

( ) Probable cause of interference (for example, co-channel

assignment, harmonics, inter-modulation, spurious products,

jamming, etc.).

(9)

( ) Extent of impairment to operational capability of affected

equipment. Characteristics of interference (reduced range, false

targets, reduced intelligibility, data errors, etc.)

(10)

( ) Corrective measures taken to resolve or work around the

interference.

(11)

( ) Effect of corrective measures.

(12)

( ) Any additional useful remarks. Provide a clear,

unstructured narrative summary on the interference and local

actions that have been take to resolve the problem.

K-6-A-4

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-540

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, JTF JCEOI Concept Tab)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

TAB B TO APPENDIX 6 TO ANNEX K TO USCINCEUR OPLAN

4999-99 ( )

JTF JCEOI CONCEPT ( )

( ) References: a. CJCS message DTG 182218Z OCT 93.

b. CJCSM 6230.04, (date), “Manual for Employing

Revised Battlefield Electronic CEOI System (RBECS).”

( ) Purpose. This tab provides information concerning the JCEOI

concept and its use during JTF “X’”.

( ) The RBECS version 2.X will be used during JTF “X” operations,

along with RBECS Merge for Windows 2.X, to create, modify, and

generate the JCEOI.

( ) The JCEOI is a single, comprehensive document that contains

frequencies, nets, Single-channel Ground and Airborne Radio System

(SINCGARS) information, and call signs/words for all participants. To

provide adequate lead-time for submission of frequency requirements for

allied coordination and to design, publish, and distribute the JCEOI, the

following relationships and milestones are established:

( ) Submit all JCEOI data through component headquarters for

consolidation and forwarding to the JTF “X” JSME for inclusion in

JCEOI.

( ) Inputs are required from ARFOR, NAVFOR, AFFOR, MARFOR,

JSOTF, and Coalition Forces Component Headquarters.

( ) The desired input method for JTF JCEOI inputs are electronic

RBECS format; however, as a minimum a paper copy of the Master Net

List, Net Groups, Separation Plans are required. Coalition forces will

submit and coordinate all requirements directly to the JSME for

assistance in completing RBECS input.

K-6-B-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-541

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) To create the JCEOI the following information is required:

( ) List of all radio nets:

(1)

( ) Identify radio nets, having a specific title; e.g., Alternate

(ALT), or Antijam (AJ). Radio net titles may contain sixteen (16)

characters including spaces; e.g., (29TH INF DIV ALT). Also

identify the frequency band that radio net will operate in; e.g., HF,

VHF/FM, VHF/AM, UHF, SHF, or EHF.

(2)

( ) Identify radio nets requiring a fixed frequency.

(3)

( ) Identify nets that require frequency separation.

(4)

( ) Identify nets that can be included in a share plan.

(5)

( ) Satellite net names will appear in the JCEOI but may not

have frequencies due to time constraints and availability of

channels.

(6)

( ) HF DCS entry frequencies.

(7)

( ) Frequencies to be included in the JRFL must be identified

prior to final generation of JCEOI.

(8)

( ) Nets requiring restriction codes and the restriction code

definitions.

( ) List of all nets requiring a call sign to build the call sign

vocabulary. Daily changing alphanumeric, trigraph (letter-number

letter) call signs will be used; e.g., B3K, C9Q. The capability to

provide fixed trigraph call signs is not available.

( ) Identify all net groups to ensure listing in your component layer

of the JCEOI.

( ) Listing of units net names. These names can contain a

maximum of sixteen (16) characters including spaces; e.g., 9TH MAR

TOW PLT. Net names cannot be used more than once within your

component; net names must be unique.

K-6-B-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-542

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) List of all nets requiring a call word in order to build the call

word vocabulary include fixed and daily changing call words. The

JSME will deconflict the call word dictionary against any fixed call

words that are requested.

( ) List of the suffixes that each component will use. The suffix is a

two-digit number attached to a call sign or call word used to identify

personnel or staff sections within a unit. The suffix vocabulary may

contain a maximum of 99 assignments. There will be one master

changing suffix vocabulary for the JCEOI.

( ) List of expander titles that your unit will use. The expander is a

single letter assignment used to further identify personnel within a

unit. Expander vocabulary can contain a maximum of twenty (20)

expander titles. There will be one master changing expander

vocabulary for the JCEOI.

( ) Instructions for the use of changing suffixes/expanders are

provided in the Quick Reference pages of the JCEOI.

( ) The JCEOI when completed will be transmitted electronically to all

component commanders. Coalition forces will be given paper copies.

( ) The JTF JCEOI will be in half-page 52-line format, generated in

three (3) editions. One active edition, one reserve edition transmitted to,

but not distributed below component headquarters, and a third edition

to be used in case of a compromise.

K-6-B-3

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-543

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Spectrum Use Plan Tab)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

TAB C TO APPENDIX 6 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

SPECTRUM USE PLAN ( )

( ) References: a. Unified command regulation or Spectrum-

Management Manual

b. Unified command Joint Communications-Electronics

Standing Instructions (JCESI)

c. Other applicable directives or instructions, as

appropriate

( ) Purpose. To describe spectrum-use plan for operation JTF ”X”.

( ) Frequency Plan. Subject to any limitations noted (such as power,

bandwidth, hours of operation, etc.), list the frequencies authorized for

use in the exercise/operation. Sort frequency authorizations according

to frequency band to facilitate reference and use. The JCEOI frequency

authorization information is also included in the JTF Frequency Plan.

Present each sort list as a tab to this appendix (Tab E & F).

K-6-C-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-545

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, JTF C4 Deployment Checklist)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

APPENDIX 7 TO ANNEX K TO USCINCEUR OPLAN 4999-99 ( )

JTF C4 DEPLOYMENT CHECKLIST ( )

( ) References: List documents that provide additional guidance and

information required for use with this appendix.

( ) General. This appendix provides a list of subjects that should be

considered for pre-execution planning and inclusion in implementing

orders and messages.

( ) Communication Planning

( ) User Requirements

(1)

( ) Is the C4 planner brought to the planning process early?

(2)

( ) Can command and control systems support each course of

action being addressed?

(3)

( ) Is a joint C4 planning meeting scheduled? Is a C4 planner

from each organization attending and are C4 decisions to be

promulgated in a timely manner?

(4)

( ) Are the command and control relationship decisions being

made by the operational planners in sufficient time to allow

supporting C4 to be adequately planned and C4 decisions to be

promulgated in a timely manner?

(5)

( ) Are the C4 planners familiar with the command and control

relationships?

(6)

( ) Are the operational impacts of potential C4 problems

brought to the attention of the operational planners and senior

commanders?

K-7-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-547

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(7)

( ) Is there a network diagram or description showing

connectivity to all commands/organizations included in the OPLAN

or implementing instructions?

( ) Communications Security

(1)

( ) Do all planners understand close-hold procedures?

(2)

( ) Is planning adequate to ensure all communications nets

have compatible COMSEC devices and keying material? Is secure-

equipment availability and installation adequate for this operation

(e.g., VINSON, ANDVT).

(3)

( ) Is the use of intertheater COMSEC Package (ICP) being

considered? Do all forces hold all necessary components of the

ICP?

(4)

( ) Are forces trained to transmit and receive COMSEC key

electronically through over-the-air rekey (OTAR)/OTAT?

(5)

( ) Is there adequate planning to ensure communications-

electronics operating instructions (CEOI), and frequency

management decisions are made in a timely manner to enable

dissemination to participating units when needed?

(6)

( ) Are provisions being made to ensure that each participating

organization is notified which frequencies, call signs, and COMSEC

to use for this operation?

(7)

( ) Are operations codes available for all commands?

(8)

( ) Are adequate plans made for secure interoperability for

coalition partners?

( ) Special Network C-4 Networks/Procedures

(1)

( ) Is planning/equipment installation adequate for Air Combat

Command (ACC) aircrews to talk secure to all forces, as required?

(2)

( ) Is planning for interoperability between special operations

forces and conventional forces adequate for the exercise?

K-7-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-548

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(3)

( ) Are procedures in place to adequately plan C-4 for special

operations under both special operations and mission-imposed

close-hold restrictions?

(4)

( ) Are theater/tactical C4 systems interfaces (DCS entry

points) adequate to provide timely and accurate situation reporting

for crisis management reporting to senior commanders, the

Chairman (CJCS), and NCA?

(5)

( ) Does C4 planning for deployment include command

relationships, force OPCON procedures, force communications for

underway sea or airlift and for Air Mobility Command (AMC) C4

adequate?

(6)

( ) Are deployable Global Command and Control System

(GCCS) terminal needed/planned?

( ) Time-Phased C4

(1)

( ) Is planning adequate to have communications into the

objective area in the proper sequence and in sufficient amount and

type to support the tactical operation?

(2)

( ) Is planning adequate to have the buildup of C4 in the

objective area early enough to prevent overload of the initially

deployed single channel communications systems?

(3)

( ) Is the operational impact of C4 equipment arrival times

brought to the attention of tactical commanders?

(4)

( ) Are CJCS-controlled assets (Joint Communications Support

Element- JCSE) requested to support the plan?

(a)

( ) Is there a CJCSI 6201.01 request for assets?

(b)

( ) Have transportation requirements for CJCS-controlled

assets been coordinated?

(5)

( ) Are communications units, equipment and personnel,

including CJCS-controlled assets, included in the TPFDD?

K-7-3

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-549

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(6)

( ) Is there enough detail in the TPFDD about C4 assets to

assist in C4 planning?

(7)

( ) Are there any special communications needs for mapping,

charting, and geodesy?

( ) EW/C4CM/EMCOM

(1)

( ) Is the impact of EW and C4CM considered in planning? Are

EW, C4CM, and communications frequency deconfliction

addressed?

(2)

( ) Are EMCON procedures, requirements for OPSEC, military

deception, and avoiding mutual interference addressed in

planning?

(3)

( ) Are IFF procedures and exchange of aircrew data

(rendezvous procedures) adequately coordinated?

( ) Coast Guard Support

(1)

( ) Are the command and control relationships with the Coast

Guard understood?

(a)

( ) Are the C4 needs of the Coast Guard adequately

addressed in planning?

(b)

( ) Does the Coast Guard have sufficient interoperable C4

equipment and COMSEC for this operation?

( ) Intelligence Support. Are C4 planners included early in

planning for communications support for intelligence systems?

(1)

( ) Have the J-2, J-3, and J-6 prioritized the intelligence

requirements within the overall C4 requirements?

(2)

( ) Are intelligence system frequencies independently procured

by the intelligence community and integrated into the overall

communications planning, and were provisions made for

frequency deconfliction?

K-7-4

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-550

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

(3)

( ) Are there adequate C4 systems available to get near-real

time photo imagery, signals data, and an accurate picture of the

local situation to the tactical commanders?

( ) Search and Rescue, Combat Search And Rescue/

MEDEVAC/Media Support

(1)

( ) Have SAR and medical personnel and C4 personnel

coordinated SAR and MEDEVAC communications early?

(a)

( ) Are SAR and MEDEVAC communications adequately

covered in planning? Do C4 planners hold USCINCEUR

Medical Communications Plan?

(b)

( ) Are plans for SAR and MEDEVAC communications

adequately promulgated to the operating forces?

(2)

( ) Are secure communications for public affairs and the media

pool adequately covered in planning?

(3)

( ) Have procedures been established for emergency

destruction of classified materials?

(4)

( ) Is there a heavy dependence on any one means of

communications during this operation (e.g., UHF SATCOM)?

( ) Predeployment Communications. Does the JTF HQ and identified

component HQ have systems to provide secure voice, record, and data

communications (including GCCS) for:

( ) Issuing command instructions?

( ) Updating the force database?

( ) Coordinating OAS?

( ) Managing force status and generation?

( ) Advanced Echelon (ADVON) Deployment Communications

( ) If an advanced party deploys aboard a ship, are C4 capabilities

adequate? Can transmission security be maintained?

K-7-5

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-551

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) If ADVON deploys by air, are secure communications available

to communicate with the JTF HQ, the supported/supporting

commander, and the appropriate US Embassy.

( ) Once in the assigned JOR, does the ADVON have secure voice,

common-user telephone circuits, and secure record and facsimile

capabilities for effective exchange of current intelligence, graphics,

planning, and adjustment to operational assessments/orders?

( ) Are liaison officer (LNO) C4 requirements identified?

( ) Main Force Deployment

( ) Are arrangements required for an airborne command post

capability (e.g., ABCCC or AWACS)?

( ) Have radio nets for en route communications been developed

and coordinated with CINCs and components?

( ) If an intermediate staging base is used:

(1)

( ) Have independent sideband (ISB)/SHF C4 requirements

been developed and coordinated?

(2)

( ) Has a responsible elements been identified to make

installation?

( ) ID-Theater Communications Requirements

( ) As forces deploy into the area and the JTF HQ joins the

advanced party (if used), has the ground/sea-based C4 package,

capable of providing secure voice, record, and data transmission

capabilities been made available to satisfy requirements for

communications links with:

(1)

( ) CINCs?

(2)

( ) NCA?

(3)

( ) Component headquarters?

(4)

( ) Allied headquarters?

K-7-6

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix K

C-552

Enclosure C

CJCSM 3122.03A

31 December 1999

(Format, Environmental Considerations)

CLASSIFICATION

HEADQUARTERS, US EUROPEAN COMMAND

APO AE 09128

28 February 1999

ANNEX L TO USCINCEUR OPLAN 4999-99 ( )

ENVIRONMENTAL CONSIDERATIONS ( )

( ) References:

a. Joint Pub 4-04, 26 September 1995, “Joint Doctrine

for Civil Engineering Support.”

b. DOD Directive 6050.7, 31 March 1979,

“Environmental Effects Abroad of Major Department of

Defense Actions.”

c. Joint Staff Instruction 3820.01B, 1 May 1998,

“Environmental Engineering Effects of DOD Actions.”

d. DOD Instruction 4715.5, 22 April 1996,

“Management of Environmental Compliance at Overseas

Installations.”

e. DOD Instruction 4715.8, 2 February 1998,

“Environmental Remediation for DOD Activities

Overseas.”

f. Applicable Country-Specific Final Governing Standard

(FGS).

g. DOD Overseas Environmental Baseline Guidance

Document (OEBGD).

( ) Situation

(

) Purpose. Provide a statement of the purpose of this annex, the

relationship between environmental considerations and the

supported OPLAN, CONPLAN, or FUNCPLAN.

L-1

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix L

C-557

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) Assumptions. State the assumptions affecting environmental

planning/compliance from the supported OPLAN, CONPLAN, or

FUNCPLAN.

( ) Limiting Factors. Outline limitations that are due to lack of

foreign access, time, OPSEC, host-nation rules or sensitivities, public

affairs (foreign and domestic), legal considerations, and resources.

( ) Mission. State clearly and concisely, the “essential” tasks to be

accomplished with regard to the purpose of this ANNEX as it relates to

the overall mission stated in the Basic Plan. The mission statement

should address the questions (who, what, when, where and why).

( ) Execution

( ) Concept of Operations. Summarize the commander’s concept

of environmental issues and actions required to support the OPLAN,

CONPLAN, or FUNCPLAN. Identify issues and actions which should

be addressed during all five phases of the operation: pre-hostilities,

lodgment, decisive combat and stabilization, follow-through, and

posthostilities.

(1)

( ) Compliance Requirements. State regulatory, legal, and

host-nation compliance requirements based on whether an

operation is a combatant operation (in which many requirements

not applicable) or a noncombatant operation “other than war.”

(2)

( ) Phased Compliance. Describe in general terms the different

environmental concerns in the supported OPLAN, CONPLAN, or

FUNCPLAN during different phases of the operation.

(3)

( ) Mission Support. Identify those environmental planning

factors which, although not mandated as a matter of law or

regulation, will support successful execution of the OPLAN,

CONPLAN, or FUNCPLAN in all phases and protect the health and

safety of US, allied forces, and noncombatants. As a minimum,

address certification of local water sources by medical field units,

solid and liquid waste management, hazardous material

management, flora and fauna protection, archeological and

historical preservation, and spill response.

L-2

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix L

C-558

Enclosure C

CJCSM 3122.03A

31 December 1999

CLASSIFICATION

( ) Tasks. Identify inter-service responsibilities of subunified, joint

task force, and component commanders for environmental support.

Key elements to consider include, but are not limited to, the

formulation of a Joint Environmental Management Board (see

Appendix 3), individual component responsibilities for the tasks in

paragraph 3.a.(3) above, environmental planning, and staff training.

( ) Coordinating Instructions. Outline key coordination that must

be accomplished. Particular emphasis on coordination requirements

with higher headquarters, OSD, and other Federal agencies. Where

applicable, this section should define procedures for transboundary

shipment of hazardous material and waste, disposal of hazardous

waste, and any potential conflicts with the host-nation.

( ) Administration and Logistics

a. ( ) Logistics. Address any necessary guidance for administering the

environmental effort by combatant commander. Provide guidance for

logistic support for environmental support and compliance when such

support is outside the scope of component command responsibilities

and resources.

b. ( ) Reports. Specify format and instructions for required reports.

( ) Joint Environmental Management Board. The Joint

Environmental Management Board (JEMB) is a temporary board

activated to establish policies, procedures, priorities, conflict

resolution, and overall direction for environmental management in the

theater. Appendix 3 provides guidance for the formulation of the

JEMB.

General

Commander in Chief

Appendixes

1 -- Environmental Assessments

(Continued on next page)

L-3

CLASSIFICATION

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Appendix L

C-559

Enclosure C

JOINT OPERATION PLANNING AND EXECUTION SYSTEM VOLUME II PLANNING FORMATS AND GUIDANCE (1999) - page 6