"Date of Instruction - Spell Month Out Completely"
15 November 1994
"Long Title - Type In All Capital Letters"
BATTLE STAFF OPERATIONS
This instruction implements AFSPCPD10-1, 13 April 1994, Battle Staff Operations, for Battle Staff and Crisis Action Team (CAT) Operations. It applies to HQ Air Force Space Command (AFSPC) and all subordinate units. It does not apply to the Air Force Reserve nor the Air National Guard. This instruction may be supplemented as required by the commander. Send correspondence pertaining to this instruction to HQ AFSPC/DOCO, 150 Vandenberg St, STE 1105, Peterson AFB CO 80914-4190.
SUMMARY OF REVISIONS
Realigns publication to bring in line with AFSPCPD10-1.
1. General. The wing/groupcommander must be able to plan, direct, coordinate, and control assigned forces in response to taskings by HQ AFSPC and NAF HQ, supporting US peacetime activities as
well as situations/contingencies across the spectrum of conflict. This instruction:
1.1 Establishes AFSPC battle staffs to assist the commander in directing and controlling assigned forces throughout the spectrum of contingency or crisis situations.
1.2 Prescribes policies and procedures for AFSPC units to plan and execute time-sensitive operations.
2.1. HQ AFSPC, Directorate of Operations, Command and Control Division (DOC), is the office of primary responsibility (OPR) for HQ AFSPC, NAFs, wing, and unit battle staff and CAT operation.
3. Definitions and Abbreviations:
3.1. Battle Staff. A staff formed to plan operations and direct forces in response to contingencies and crises, develop courses of action, and execute the commander's directives.
3.2. Crisis action team (CAT). A limited staff formed when the crisis is limited in scope and resolution does not require formation of the entire battle staff.
3.3. Unit crisis response element (CRE). The CRE plans, directs, and coordinates activities in
response to various situations and advises the commander in the accomplishment of the mission. The purpose of the CRE is to relieve the operations crew of designated emergency or LERTCON change actions so the crew can focus on operational events.
3.4. Air Force Space Operations Center (AFSPOC). The operations center provides the NAFs a focal point for service related reporting and support.
3.5. 14th Air Force Command Post (14 AF/CP). The Command Post that provides space Wings/Groups a focal point for service support and all reporting. It provides the 14 AF Commander command and control of his assigned forces.
3.6. 20th Air Force Command Post (20 AF/CP). The Command Post that provides missile Wings/Groups a focal point for service support and all reporting. It provides the 20 AF Commander command and control of his assigned forces.
4. Supporting Procedures. This instruction establishes a requirement for battle staffs at the NAF/wing/group level. It also establishes required operational procedures and training to support those battle staffs.
5. Waiver Requests. Requests for clarification and waivers to this instruction, including justification, may be sent to HQ AFSPC/DOC via the parent NAF for DO approval.
6. Battle Staff. Mission, Organization, Functions, and Responsibilities:
6.1. General. Each NAF/wing/group commander establishes a battle staff according to organizational structure and mission requirements. Additional support elements may be formed at the wing/group commander's discretion.
6.2. Mission. The mission of the battle staff is to plan, direct, coordinate, and control AFSPC forces in response to NCA, USCINCSPACE, USCINCSTRAT, Commander AFSPC, Commander NAF and wing/group commander directives.
6.3. Organization. Each battle staff is manned to respond to the commander's needs. It may range from a fully formed battle staff to a CAT consisting of only those individuals required to respond to a developing situation. Once convened, the response element functions as a team and is only released by direction of the commander or designated alternate. Battle staff/CAT personnel may be put on call and respond as required/directed. In host/tenant situations, local commanders determine the size, composition, location and operating procedures for their battle staffs/CATs in order to meet their specific requirements. Operating agreements are recommended between host and tenant units in order to maximize use of existing facilities, training capabilities, and staffs. The suggested composition of each element is as follows:
6.3.1. Wing/Group battle staff. This element consists of representatives from those functional areas required for the situation. Specific functional areas and taskings are tailored to meet unit mission requirements. Size and composition depend on the situation and are determined by the commander or designated alternate.
6.3.2. CAT. A CAT is composed of a team chief and functional experts required to respond to a specific situation. Size and composition are determined by the commander or designated alternate.
6.3.3. Support Cells. Units may, at the commander's discretion, establish support cells located separately from the battle staff. A support cell may exist at a geographically separated unit (GSU ) and respond to the wing or host unit battle staff/CAT needs. The support cell functions to allow others assigned at the GSU to conduct normal daily operations. (Suggested for remote sites.)
6.4. Function. The function of the battle staff is to support the commander and to develop courses of action responding to higher headquarters taskings or contingency situations.
6.5. Activation. The battle staff, CAT, or CRE is formed when directed by the commander or designated alternate, or higher headquarters.
6.6. Notification. Units notify their wings which then notify their respective NAF Command Post (14/20 AF/CP), and the NAF/CP will notify the AFSPOC and parent Unified Command center of wing/unit battle staff/CAT activation.
6.7. Responsibilities. Wings/Groups will develop written guidance for battle staff/CAT operations. In host/tenant situations, an addendum to host wing guidance satisfies this requirement. The following areas should be examined for possible inclusion in this guidance with the commander determining what best meets his or her needs.
6.7.1. Composition of battle staff/CAT and duties/functional responsibilities of members.
6.7.2. Training procedures.
6.7.3. Location of operations and physical configuration.
6.7.4. Communications procedures and requirements, including alternates.
6.7.5. Checklists for each staff position.
6.7.6. Security procedures, including OPSEC/COMSEC requirements.
6.7.7. Message traffic handling and logistic support procedures.
6.7.8. A current unit "Succession to Command" list.
6.7.9. Recall procedures for unit personnel.
6.7.10. Written guidance on subordinate unit's crisis response elements.
6.8. Situation Reports (SITREP). Refer to AFMAN10-206, Operational Reporting, USSPACECOMR 55-18(S), Commander's Situation Report (U) (under revision), and AFSPCR55-2, AFSPC Reporting System (under revision), for more detailed instruction.
6.9. Information Flow. In order for battle staffs/CATs to receive timely information, the flow of information to and from the teams must be logical and reliable. It is recommended that the unit command post be the single, official point of contact (POC) for all external agencies and units. All events and significant information should be received by and transmitted through the command post using established command and control procedures. This does not preclude communication directly between the wings/units and the NAF battle staff; however, the command post should be briefed to assure it also has the same information.
7. Battle Staff Training:
7.1. General. Training and exercise participation are the means by which a high state of readiness is achieved. Since battle staff personnel perform functions that may be dissimilar to their normal duties, they must receive training in their assigned wing battle staff/CAT functions.
7.2.1. Pre-identify battle staff/CAT members and ensure they are knowledgeable of, and able to operate in the battle staff environment.
7.2.2. At the discretion of the commander, establish unit crisis response elements (CRE) or similar teams at subordinate units. When established, the wing/group will provide written guidance to subordinate units specifying training requirements.
7.2.3. Wings/Groups maintain training documentation on their battle staff/CAT personnel and ensure that CRE training is conducted and documented for their respective units that they designate to have a CRE. In host/tenant situations, it may be desirable to consolidate all training documentation with the host wing if a common training program is used.
7.3. Training Requirements. Wings/Groups develop training programs to ensure battle staff/CAT personnel are proficient in the functions and general operations of the battle staff/CAT. In host/tenant situations, an addendum to host wing guidance satisfies this requirement.
7.3.1. Recommend training be divided into two types:
18.104.22.168. Initial training. This is comprehensive training for all newly assigned battle staff/CAT/CRE personnel. Initial training should be accomplished as soon as possible after personnel are assigned to a battle staff/CAT/CRE position.
22.214.171.124. Recurring training. This training is for existing members of the battle staff/CAT/CRE and should be a refresher. It is recommended that the last exercise "lessons learned" be included.
7.3.2. Recommend the following be included in initial battle staff/CAT/CRE training.
126.96.36.199. Battle staff activation procedures.
188.8.131.52. LERTCON attainment procedures.
184.108.40.206. OPlan taskings.
220.127.116.11. "Action Item" and "Significant Event" processing procedures.
18.104.22.168. Construction of applicable battle staff briefings.
22.214.171.124. SITREP reporting procedures.
126.96.36.199. Operation of communication systems, office machines, and computer software (FAX, STU-III, MLP-2, SARAH-Lite, and automated briefing systems).
8. Quality Assistance Visit Program:
8.1. General. The following procedures are employed during HQ AFSPC quality assistance visits (QAV) to wings/groups and NAFs. HQ AFSPC/DOC will conduct QAVs at the request of commanders.
8.2. Purpose of the QAV is to:
8.2.1. Provide assistance.
8.2.2. Identify structural and procedural concerns.
8.2.3. Solicit feedback and suggestions on how to improve battle staff functions.
8.2.4. Identify and disseminate good ideas.
8.3. Procedures. The battle staff QAV team reviews battle staff operating procedures and documentation as applicable to the unit.
8.3.1. Attention is focused on management policy and procedures, compliance with local directives, personnel and resource utilization, training/documentation, and overall battle staff effectiveness.
8.4. Findings Report. During the outbrief a review of findings is presented. All areas of concern are addressed.
JOHN A. GORDON, Brig Gen, USAF
Director of Operations