ATP-5-0-2-1 Staff Reference Guide Volume 1 Download
Page 109 of 440
Planning 07 December 2020 ATP 5-0.2-1 93 offense, defense, insurgent ambush, or terrorist kidnapping). When possible, templates should be graphically depicted as an overlay, on a command and control system, or through some other means. 2-283. Threat templates are tailored to the needs of the unit or staff creating them. For example, an intelligence section's threat template differs in scope from a brigade or battalion intelligence section's template. Some threat templates consider threat forces as a whole while others focus on a single warfighting function, such as intelligence or fires support. Other products depict pattern analysis, time event charts, and association matrices. Threat templates may depict, but are not limited to, unit frontages, unit depths, boundaries, EAs, and obstacles. 2-284. When creating threat templates— Construct templates by analyzing the intelligence database and evaluating the threat's past operations. Determine how the threat normally organizes for combat and how it deploys and employs its forces and assets. Look for patterns in how the threat organizes its forces and uses time, distance, relative locations, groupings, and terrain and weather. 2-285. Templating requires continuous refinement to accurately portray threat patterns, activities, and practices. Because implementation time is a consistent planning factor, an analyst can evaluate implementation time to determine the likelihood of location or participants. Figure 2-24 on page 94 depicts a threat template. Describe the Threat's Tactics, Options, and Peculiarities 2-286. When creating the threat model, consider the threat's tactics, options, and peculiarities. Tactics 2-287. A threat model describes a threat's preferred tactics, including, but not limited to, defend, reinforce or retrograde, attack, withdraw, and disrupt. A description is required even if preferred tactics are depicted in graphic form. This allows the template to become more than a "snapshot in time"; the template assists in mentally war gaming the operation during the development of threat COAs and SITEMPs. Options 2-288. List options in a description such as identified threat capabilities, branches, and sequels. Branches and sequels are used primarily for changing deployments or direction of movement and accepting or declining combat. Branches provide a range of alternatives often built into the basic plan. Sequels anticipate and plan for subsequent operations based on the possible outcomes of the current operation. List branches and sequels available to the threat in success or failure. For example, the threat might sequel a successful attack with a pursuit, or if an attack begins to fail, a branch plan might include committing reserves or shifting the main effort. Should a threat attack fail, a preferred sequel might be a hasty defense. 2-289. Also describe— Supporting warfighting functions' relevant actions in order to identify and develop HVTs and examine timelines and phases of operations because target values may change from phase to phase. Threat objectives. Threat objectives are often, but not always, what the unit's mission tries to prevent. Threat objectives also are actions the threat takes to prevent a unit from accomplishing its mission. Threat objectives are specific to the type of threat, the AO, the unit's composition and mission, and other factors, such as when and where a unit transitions from one form of maneuver to another. Threat objectives are explained in terms of task, purpose, and end state. A number of different functions must be executed each time a threat force attempts to achieve a goal.