ATP-5-0-2-1 Staff Reference Guide Volume 1 Download

Page 44 of 440

Chapter 2 28 ATP 5-0.2-1 07 December 2020 information about the threat and other aspects of the operational environment that the commander considers most important. Lessons from recent operations show that intelligence about civil considerations may be as critical as intelligence about the enemy. The intelligence officer, in coordination with the staff, manages PIRs for the commander. PIR serve as the framework for the information collection plan. 2-79. A friendly force information requirement is information the commander and staff need to understand the status of friendly force and supporting capabilities (JP 3-0). FFIRs identify information about a mission; troops and support available; and time available for friendly forces that the commander considers most important. In coordination with the staff, the operations officer manages FFIRs for the commander. 2-80. An essential element of friendly information is a critical aspect of a friendly operation that, if known by a threat would subsequently compromise, lead to failure, or limit success of the operation and therefore should be protected from enemy detection (ADP 6-0). In addition to nominating CCIRs to the commander, the staff also identifies and nominates essential elements of friendly information (EEFIs). Although EEFIs are not CCIRs, they have the same priority as CCIRs and require approval by the commander. Like CCIRs, EEFIs change as an operation progresses. 2-81. Depending on the situation, the commander and selected staff members meet prior to the mission analysis brief to approve initial CCIRs and EEFIs. This is especially important if the commander intends to conduct IC early in the planning process. Early approval of initial CCIRs assists the staff in developing the initial IC plan. Early approval of EEFIs allows the staff to begin planning and implementing measures to protect friendly force information, such as military deception and operations security. Note. Once in the execution phase, every CCIR must be tied to a decision and be focused enough for use in the decision support matrix (DSM) and template. Step 2.9. Develop the Initial Information Collection Plan 2-82. Information collection is an activity that synchronizes and integrates the planning and employment of sensors and assets as well as the processing, exploitation, and dissemination systems in direct support of current and future operations (FM 3-55). The initial IC plan is crucial to beginning or adjusting the IC effort and sets in motion intelligence operations, surveillance, and reconnaissance. The plan may be part of a WARNORD, a FRAGORD, or an OPORD. Available information is incorporated into a complete IC plan (Annex L) to the OPORD (see the section on IC beginning in paragraph 2-312 for more details about the initial IC plan). 2-83. The intelligence staff creates the requirements management tools for the IC plan, but responsibility for a plan resides with the operations officer. This is because only a commander and an operations officer can task subordinates and allocate resources. The operations officer reviews the risk for each named area of interest (NAI) and the collection assets assigned to them. Committing assets to reconnaissance potentially constrains a COA by reducing capabilities that could be used later. The operations and intelligence staff must work closely to ensure they fully synchronize and integrate IC activities into the overall plan. 2-84. An operations officer considers several factors when developing an initial IC plan, including— Requirements for collection assets in subsequent missions. Time available to develop and refine the initial IC plan. Risk the commander is willing to accept if IC missions begin before the IC plan is fully integrated into the scheme of maneuver. Insertion and extraction methods for reconnaissance, security, surveillance, and intelligence operations assets. Technique. CCIRs and EEFIs should always be current and relevant to the operation. To accomplish this, recommend different CCIRs and EEFIs for each phase of an operation. Alternatively, list all CCIRs and EEFIs, and designate when each is active or inactive, depending on the latest time information is of value (LTIOV).