Donate $25 for two DVDs of the Cryptome collection of files from June 1996 to the present

Natsios Young Architects

Table of Contents of main report.


Appendix A

Plans and Orders

This appendix illustrates and explains how IO and C2W could be incorporated into a basic plan or order. The OPLAN format is used for this illustration. Annex A provides a sample campaign plan model and identifies the key annexes related to IO support. Annex B illustrates how a C2W annex is written.


Commanders use operations, administrative, and logistics plans and orders to convey information and instructions to subordinate units. Plans and orders are similar in format and content. Although a plan may be effective immediately for planning purposes or for specified preparatory action, it is not executed until the commander so directs, usually when certain specified conditions, as set forth in the plan, are determined to exist. A plan specifies the time or conditions under which it is to be placed in effect.


A plan becomes an order when execution is directed. An order carries with it the obligation of immediate execution at a specified time or date. The major difference between a plan and an order is that a plan normally contains assumptions. See Chapter 6 for general information about planning and execution.

Annex A

Major Operations Plan Model
Operational Level

(Sample Campaign OPLAN)

Copy No. ___
Issuing Headquarters
Place of Issue
Date/Time Group of Signature

MAJOR OPERATION PLAN: (Number or code name)

References: Maps, charts, and other documents


1. SITUATION. Integrate tactical considerations important to IO in the early phases of an operation into the overall description of the operational situation. Refer to command and staff estimates, country studies, or OPLANs. Indicate trigger events that would signal execution of specific components to an IO within the OPORD.

2. MISSION. Address IO to the degree necessary to fully state the overall operational mission.


4. SUPPORT. Insert specific information as to how IO support Army elements involved in an operation. In this paragraph or in a support annex (Annex R), the ARFOR commander includes IO among descriptions of those support matters necessary to accomplish the combat mission of his force. The IO support plan phases must coincide with OPLAN phases.


ANNEXES: In recognition of the expanding contribution that IO can make to the accomplishment of the overall mission, OPLAN annexes have been reorganized by creating a new C2W Annex that consolidates the traditional annexes dealing with deception, EW, and PSYOP.

A Task Organization/Command Relationships. In a plan for a major operation composed of several phases, within this annex, identify and integrate the task organization required to conduct IO. Outline command relationships and their changes, if any, as the IO progresses from one phase to the next. Include information-specific task organizations for Army component support to contingencies in the annexes referring to the plans for those operations. Relate the informational structure against interfaces expected with the following activities involved in the operation:

B Intelligence. This annex should incorporate critical information needed to support IO and integrate those elements into the larger overview of the enemy situation. Detailed information needed to conduct C2W operations should be further developed in the C2W Annex.

C Operations Overlay. This annex is a graphic representation of the concept of operations.

D C2W Annex. The C2W annex focuses on providing the necessary information to conduct C2W operations and consolidates all information previously found in the annexes dealing with deception (formerly Annex D), EW (formerly Annex I), and PSYOP (formerly Annex K). The intent is to integrate all aspects of C2W to best identify and synchronize the application of available capabilities to achieve the overall mission. A sample C2W Annex is provided in Annex B of this appendix.

E Constraints. This annex contains those political, humanitarian, economic, and social/cultural limitations on applying military power during the operation.

F Rules of Engagement. This annex contains guidelines to subordinate and supporting organizations regarding the rules for the control of forces and their weapons systems, to include guidance on the conduct of IO.

G Fire Support. This annex contains a statement of the fire support operations to be carried out, to include major groupings of fire support means and priorities and the integration of nuclear, chemical, and conventional fires, as appropriate.

H Air Defense. This annex should state the air defense operation to be carried out, to include air defense priorities and reference to the deployment overlays appendix. It should contain the allocation of counterair units, tasks, and coordinating instructions.

I Not Used.

J Engineer. This annex should include a statement of how the engineering support is to be carried out, to include priorities of mobility, countermobility, and survivability tasks within sectors and priority of uncommitted engineering resources to subordinate units or sectors.

K Not Used.

L Rear Operations. This annex contains guidance and priorities for securing the rear areas and facilities to prevent or minimize enemy interference, disruption of combat support and service support, or movement of friendly troops. It designates a unit to find, fix, and destroy enemy incursions into the rear area and provides area damage control after an attack or incident.

M Protection. This annex contains instructions for the protection of bases, installations, military personnel, family members, and other US nationals in the theater from terrorism, natural disasters, and other dangers. It also contains information on protection of C4I architecture.

N Provost Marshal. This annex prioritizes the four MP battlefield missions: area security, battlefield circulation control, enemy prisoner-of-war operations, and law enforcement. It should specify any tasks and/or coordinating instructions not covered in the OPORD.

O Public Affairs. This annex contains guidance for facilitating the media effort to cover the operation and for supporting the information needs of soldiers and their families. While PA is clearly a part of IO, it is addressed in its own annex since it falls outside C2W as defined by joint doctrine.

P Space Operations. This annex describes planned and available space support to the OPLAN. It explains how to obtain and coordinate space support and lists operational constraints and shortfalls. This annex is linked to space-based systems such as communications and, as such, is closely related to IO.

Q Training. This annex contains guidance for multinational, joint, and service training of individuals and units assigned or attached to the theater army, which includes liaison teams and other forms of connectivity that enable coalition C4I.

R Support. This annex spells out in detail the necessary support for subordinate formations to accomplish their missions. It may include special instructions for INFOSYS support of software support, configuration support, evacuating criteria, repair criteria, and so forth.

S Communications-Electronics. This annex describes the link provided by the force headquarters between the ATCCS, which exists among its subordinate units and joint and multinational C2 systems, as well as those of the sustaining base. It addresses INFOSYS and must be carefully coordinated with C2W operations.

T Civil Affairs. This annex describes civil affairs operations and organizations that affect the overall operation. It specifies how CA activities can provide relevant information supporting the CCIR from nontraditional sources in the GIE. While CA is clearly a part of IO, it is addressed in its own annex since it falls outside C2W as defined by joint doctrine.


Annex B

Sample C2W Annex

Copy No____
Issuing Headquarters
Place of Issue
Date/Time Group of Signature

Annex D to ( ) Corps OPORD Exercise Xxxx Xxxx
Command and Control Warfare (U)

(U) REFERENCES: List appropriate joint and Army publications or documents on IO such as the following:

1. (U) SITUATION. Thoroughly describe the operational environment as it applies to IO, as well as appropriate aspects of the strategic environment that may impact IO. Include tactical considerations important to IO in the early phases of an operation and establish the adversary's most probable C2-attack course of action. Indicate trigger events that would signal execution of specific components of an IO within the OPORD.

2. (U) MISSION. Include an explicit statement of the C2W mission to support the operation, such as the following: On order, ( ) Corps conducts C2W operations to deter (country name) attack on (country name). If deterrence fails, D-Day, H-Hour ( ) Corps conducts C2W operations to support combat operations to disrupt (country name) C2 of operational forces and degrade situational awareness of ( ) Corps operations, while protecting coalition C2 capabilities from enemy disruption and destruction.






Table of Contents of main report.