FM 3-34.22 - Army Electronic Publications & Forms - U.S. Army
FM 3-34.22 - Army Electronic Publications & Forms - U.S. Army
FM 3-34.22 - Army Electronic Publications & Forms - U.S. Army
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Appendix F<br />
Engineer Running Estimate<br />
As previously discussed in chapter 2, the running estimate is a logical thought<br />
process and extension of the MDMP. RI in the engineer running estimate supports the<br />
commander’s visualization and decisionmaking. The ENCOORD prepares and<br />
refines the running estimate concurrently with the planning process of the supported<br />
maneuver force and maintains it continuously throughout planning, preparation,<br />
execution, and assessment. This appendix provides more detail on how mission<br />
analysis, facts, assumptions, and variables furnish the structure for the running<br />
estimate and how the estimate supports the planning, preparation, execution, and<br />
assessment of operations. Commanders are rarely briefed on the contents of every<br />
staff section running estimate. The ENCOORD only briefs the part of the estimate<br />
that applies to the situation and the issue or decision being addressed. During<br />
operations, running estimates are usually presented orally, especially during<br />
preparation and execution. Written estimates may be prepared to support contingency<br />
planning during peacetime. Even then, they are normally prepared only at higher<br />
level headquarters. (Written estimates follow the generic format in <strong>FM</strong> 5-0, figure E-<br />
1. See <strong>FM</strong>s 3-0, 5-0, and 6-0 for more information on the running estimate.)<br />
PLANNING<br />
F-1. Prior to receiving a mission, the engineer staff running estimate consists of the ENCOORD’s broad<br />
assessment of the OE and SA of engineer capabilities. Once a mission is assigned, the estimate becomes<br />
focused on RI to assist the commander in decisionmaking.<br />
Mission analysis (MDMP, Step 2) enables commanders to refine their SU of the OE and determine their<br />
mission. Mission variables (see <strong>FM</strong> 6-0) are considered during mission analysis. From the engineer perspective<br />
(see chapter 1), mission analysis equates to seeing the tactical problem and sharing the engineer view of the<br />
OE, identifying engineer requirements, and determining what engineer capabilities are required to solve the<br />
problem. Once the problem is identified, the balancing of requirements versus capabilities and the integration of<br />
engineer capabilities into the concept of the operation become the objectives during COA development and<br />
implementation.<br />
F-2. As stated in chapter 2, the running estimate parallels the MDMP. Mission analysis, facts, and<br />
assumptions, and variables (METT-TC) furnish the structure for the running estimate. The engineer<br />
running estimate is initiated by—<br />
� Analyzing the higher-headquarters order.<br />
� Conducting IPB.<br />
� Analyzing the engineer mission.<br />
� Conducting a risk assessment.<br />
ANALYZE THE HIGHER-HEADQUARTERS ORDER<br />
F-3. The ENCOORD thoroughly analyzes the higher-headquarters order by initially focusing on the<br />
engineer annex, which conveys the overall maneuver unit mission, commander’s intent, and concept of the<br />
operation (two levels up). Analysis includes understanding—<br />
11 February 2009 <strong>FM</strong> 3-<strong>34.22</strong> F-1
Change language