AIAI10-401

AIR INTELLIGENCE AGENCY INSTRUCTION 10-401

15 FEBRUARY 1995

DEPARTMENT OF THE AIR FORCE HQ AIR INTELLIGENCE AGENCY

Operations Planning

UNITS PLANS PROGRAM

This instruction implements AFPD 10-4, Operations Planning. It provides basic HQ Air Intelligence Agency (AIA) guidance and assigns responsibilities for managing the plans program at AIA field units and subordinate levels of command. This instruction applies to all AIA centers, units, detachments, and operating locations worldwide. It applies to AIA-gained Air Force Reserve units. It does not apply to wing, groups, operational support squadrons, mission support squadrons, and AIA-gained Air National Guard units.

This revision aligns this instruction with AFPD 10-4 and AIAI 10-203, Unit Emergency Actions Program. It changes information and clearly defines unit mission plans functions, contents and format of a unit emergency actions plan, formerly found in ESCR 28-1, The Unit Emergency-Actions and Plans Program.

ESCR 28-1, 7 September 1988.

HQ AIA/DOXX

MSgt Suzanne D. Wade

HQ AIA/DOX

Col Michael C. Livingston

5

F; X:

AUL/LSE

1

HQ AFRES/ IMPM

1

HQ AIA/DOXX

3

HQ AIA/ IMSP

2

1. Introduction:

1.1. This instruction describes plans, defines administrative procedures and training requirements, and describes the management tools available to the unit's contingency planner.

1.2. Address requests for exceptions to having a unit plans program to the appropriate intermediate theater headquarters.

2. Plans. The effectiveness of a military organization depends on the efficiency of its planning. Through planning, effective and economical use of available resources are ensured; this is especially important within AIA.

2.1. What Is a Plan? A plan is a systematic list of actions to accomplish a specific mission. The primary purpose of any plan, at any level of command, is to identify a limited, attainable mission and then provide guidance to assist a commander in successfully achieving that mission.

2.2. Types of Plans. There are many different types of missions that require documented planning. Generally, AIA plans are categorized as war and contingency operations, emergency actions, and programming plans. Other types are either variations of these or are specialized documents written to fulfill specific situations. A general description of some plans follows:

2.2.1. War and Mobilization Plans. The war and mobilization plans are a series of plans which show the capabilities of AIA to transition from peace, through crisis or tension, to war.

2.2.2. Operation Plan. The operation plan is any plan, except the single integrated operational plan (SIOP), to conduct a single military operation or series of connected operations. This plan is carried out simultaneously or in succession in a hostile environment. It is prepared by the commander of a unified or specified command in response to a requirement established by the Joint Chiefs of Staff (JCS). It is usually based on stated assumptions. "Operation plan" is a generic term that refers to either an operation plan in complete format (OPLAN) or an operation plan in concept format (CONPLAN). An operation plan may be put into effect at a prescribed time, at which time it becomes an operation order (OPORD). AIA units are primarily concerned with two types of operation plans:

2.2.2.1. An OPLAN is to conduct joint military operations that can be used to develop an OPORD and execute the operation. It includes deployment and employment phases. An OPLAN includes all required annexes, appendices, and a supporting time-phased force deployment document (TPFDD).

2.2.2.2. A CONPLAN is a fully defined concept of operations. A CONPLAN is in an abbreviated format that requires considerable expansion to convert into an OPLAN or OPORD. Some CONPLANs contain selected annexes and appendices, and even portions of a TPFDD (as may be required by the supported commander); but this is not normal practice.

2.2.3. Deployment Plans (Formerly Mobility Plans). Each unit, subject to deployment tasking, prepares an input to the host-base (Air Force) deployment plan. These instructions may be included in an in-garrison emergency action plan (EAP) or in a separate document. They explain how the unit:

2.2.3.1. Supports the base deployment plans.

2.2.3.2. Separate instructions for deployment operations to include all deployed emergency actions.

2.2.4. EAPs. If used, EAPs provide the emergency measures and actions necessary for the safety and well-being of a unit, its personnel, and equipment. It is intended to provide the unit with a single-source document for all required actions during an emergency or crisis. The EAP is usually supplemented with workcenter checklists.

NOTE: Unit EAPs are optional.

2.2.5. National Security Agency, Central Security Service (NSA/CSS) Plans. NSA/CSS publishes two main types of plans:

2.2.5.1. Cryptologic Support Plans (CSP). CSPs direct the realignment of the US Signals Intelligence (SIGINT) System (USSS) to support unified-command operations plans.

2.2.5.2. Cryptologic Redeployment Plans (CRP). CRPs provide, by geographic area, peacetime planning data for relocating USSS activities if basing rights are lost. These plans are published to handle peacetime, political situations which require the relocation of cryptologic assets, and tasking.

2.2.6. Requests. The unit plans office is the focal point for requesting plans from other agencies. All requests for plans are sent to the intermediate headquarters for action.

3. Responsibilities:

3.1. Unit commanders appoint an experienced individual (preferably a technical sergeant or civilian equivalent or above) to act as the unit chief of plans. The individual selected has at least 50 percent remaining of their tour of duty. The chief of plans:

3.1.1. Has a direct line of communication with the commander or vice commander.

3.1.2. Serves as the focal point for the unit commander regarding unit planning matters and for accomplishing unit wartime planning responsibilities according to this instruction.

3.1.3. Identifies the support requirement from functional staff elements needed to develop, coordinate, and implement plans of the unit.

3.1.4. Acts as the unit single point of contact for host-base, theater, NSA, or HQ AIA plans coordination and correspondence.

3.1.5. Maintains a close liaison with the plans office of the host base to ensure unit tasking is realistic and comprehensive. Also ensures access to host, theater, or other headquarters plans offices which affect the unit. If necessary, contacts intermediate headquarters if additional assistance is needed.

3.1.6. Ensures that each staff function tasked, prepares detailed checklists to support unit or host-base plans.

3.1.7. Maintains the master plans library (MPL) (see paragraph 4.1.1) and provides a background folder for each plan maintained.

3.1.8. Annually reviews appropriate plans indexes to ensure that the unit maintains only the current plans.

3.1.9. Maintains "how-to" guidance which provides detailed instructions and procedures about how the plans responsibilities are done for the unit.

3.1.10. Prepares flowcharts, periodically reviews key processes, and makes appropriate changes.

3.1.11. Forwards a review of actions or "lessons learned" to the next higher level echelon of command whenever a unit implements any portion of a plan in a real-world situation. Briefly summarizes positive and problem areas, identifies actions to take or to correct any problems.

3.2. The chief of plans acts in an advisory capacity to offer advice or recommend areas or events to be exercised. The chief of plans is not assigned the duties of an exercise-evaluation team (EET) member or team chief.

4. Planning Process. Correctly managing the plans library is a very important link in a successful wartime planning program. Plans must be accounted for, reviewed, and coordinated; changes posted; and correctly distributed.

4.1. Management. All organizations that maintain plans must keep a current record of those plans. This applies regardless of the origin of the plan. File plans in either the MPL or in the reference plans library (RPL), and group the plans by originating agency. Air Force units are tasked in Air Force component plans. Normally, AIA units do not require access to unified or specified plans, such as, USCINCEUR (United States Commander in Chief European Command) or USCINCPAC (United States Commander in Chief Pacific Command) OPLANs.

4.1.1. MPL. The MPL contains plans which directly task the unit. The MPL can also contain high-interest plans which the commander feels are appropriate for annual review. Plans maintained in the MPL must have an initial review immediately upon receipt, coordinating with the commander and appropriate key staff. Thereafter, plans maintained in the MPL require an annual review unless exempted by the originator of the plan. MPL must contain background folders for each plan. Background folders contain:

4.1.1.1. Either a master copy of the plan; an Optional Form 21, Cross-Reference Sheet; or an AF Form 614, Charge-Out Record.

4.1.1.2. A plan summary and any pertinent background information or correspondence.

4.1.1.3. An AIA Form 193, Record of Coordination, documenting the latest review.

4.2.2. Separately Published Annexes. When a plan contains an annex or parts published separately due to security, bulk, or some other consideration; file this information in separate background folders.

4.2.3. MPL Exemptions. Some plans are exempt from maintenance in the MPL, the appropriate action agency should maintain them. These plans are the Logistics-Support Plans, Integrated Logistics-Support Plans, Management Plans, Master Plan and Strategic Plans, Emergency Procurement Support Plans, OPORDs or Fragmentary Orders, Advisory Support Plans, PPlans (Programming Plans), PAD (Program Action Directives).

4.2.4. RPL. Plans that indirectly task the unit or are held for information or background material are filed in the RPL. A plan summary is required for each plan in the reference library.

4.3. Review Procedures. Review all plans upon receipt and, annually if maintained in the MPL. Document all review actions. The last three coordinators are:

NOTE: Do not initial off on this last coordination until all required actions have been initiated.

4.3.1. Initial Reviews. Immediately upon receipt, the plans office reviews the plan to determine possible tasking. The plans office also:

4.3.1.1. Determines which unit agencies are tasked.

4.3.1.2. Notifies these agencies by using a coordination sheet attached to the plan.

4.3.1.3. Suspenses the tasked agency with enough time to review the plan.

4.3.1.4. Informs each tasked agency of their responsibilities. After review the tasked agencies prepare necessary implementing directives (instruction, checklist, or operating instruction (OI)) within 30 days to ensure that the unit assumes its responsibilities.

4.3.2. Annual Reviews. Annually review each plan in the MPL unless it is exempted by the OPR. Each tasked agency reviews the plan to ensure that the tasking can be accomplished. File the coordination sheet in the background folder. Remove previous coordination sheets for annual and special reviews and destroy any documentation associated with those reviews if it no longer applies.

4.3.3. Special Reviews. Document special reviews and file them in the background folder until the next annual review. Perform special reviews for any of the following reasons:

4.3.3.1. When there is a significant change to the plan or unit capabilities.

4.3.3.2. When new, key personnel are assigned to the unit and there are 6 months or more until the next annual review.

4.3.3.3. Immediately, when conditions indicate the possible implementation of a particular plan. In this situation, do not complete a formal coordination sheet, make a record of this review and file it in the background folder.

4.4. Correspondence. Address plans correspondence to the appropriate action addressees as follows:

4.4.1. Send your requests for theater or NSA/CSS plans to the intermediate theater headquarters.

4.4.2. Send requests for, and recommended changes to, host-base plans directly to the host-base OPR.

4.5. Plans Index. Most plans-publishing authorities publish an index or listing of plans. The index provides detailed information as to which plans are rescinded or superseded and lists published changes. The chief of plans should have appropriate indexes for those plans on file. When a new index is received, check the plans file to ensure that only current plans are maintained. Do not forget to check the RPL. File the plans index in the MPL in front of the appropriate plans group.

4.5.1. Unified or specified command listings are not maintained at unit level due to their classification and need-to-know limitations. Obtain required information on unified or specified plans from HQ AIA/DOXX (Plans and Readiness Branch).

4.6. Plans Summary. Prepare a brief summary for each plan maintained. Extract plan information from the plan summary or mission statement in the plan and outline AIA and unit tasking. This will help during special reviews when new, key personnel must review several plans at once. File the summary in the background folder. Do not include Top Secret information on the plans summary. See attachment 1 for a sample plans summary (format is optional).

5. Quality Program Review (QPR):

5.1. During QPRs, staff personnel review appropriate planning and provide constructive comments and recommendations for noted problem areas.

5.1.1. Newly assigned plans personnel conduct a QPR within 90 days of assignment.

5.1.2. Units perform QPRs as part of the unit self-assessment.

5.1.3. Groups conduct QPRs at the commander's discretion for subordinate units.

5.1.4. Group or unit commanders may request a QPR at any time.

6. Conferences:

6.1. Readiness Conferences. Use conferences to review and discuss taskings, interpret current or new directives, and provide assistance and training for personnel newly assigned to the plans function.

6.1.1. Each intermediate headquarters ensure that funds are available to conduct readiness conferences.

6.1.2. Unit commanders ensure that plans personnel attend the applicable intermediate headquarters conference.

JOHN S. GRAHAM

Colonel, USAF

Director of Operations

SAMPLE PLANS SUMMARY CINCUSAFE OPLAN 9999 ()

A1.1. ( ) Purpose. Briefly explain the purpose, what will be achieved by executing the plans.

A1.2. ( ) Conditions For Implementation. Summarize the politico-military situation in which the plan is considered for execution. The following example includes:

A1.2.1. ( ) CINCUSAFE OPLAN 9999 provides for the deployment of United States Air Force assigned forces for employment in a wide range of military operations against ORANGE LAND. A number of politico-military situations could conceivably arise which would call for a measured response according to provision of CINCUSAFE OPLAN 9999.

A1.2.1.1. ( ) Hostile ORANGE LAND action against US bases.

A1.2.1.2. ( ) Hostile ORANGE LAND action against US aircraft or shipping.

A1.2.1.3. ( ) Hostile ORANGE LAND action against a land with whom the US undertakes or has undertaken a collective self-defense commitment.

A1.3. ( ) Unit Tasking: 

SOURCE       RDD        LOCATION       

PFHCM        NA         In place       

PF Z99       C003       (Country)

NOTE: List the appropriate unit tasking for your unit.

A1.4. ( ) Other Comments: