09.01.2013 Views

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Appendix G<br />

� Provide subordinate leaders with the linkage between the engineer mission, scheme of<br />

engineer operations, and tasks to subordinate engineer units.<br />

� Do not describe the scheme of engineer operations or subunit tasks.<br />

b. Scheme of engineer operations.<br />

� Write a clear, concise narrative of the engineer plan from the beginning to the end. Use the<br />

same phases of the supported maneuver unit’s concept of operation (if the operation is<br />

phased) to organize the narrative.<br />

� Focus on the essential tasks for M/CM/S.<br />

� Do not entail a summary of all engineer tasks.<br />

� Clearly identify the priority of effort and priority of support for each phase of the supported unit<br />

concept of operation.<br />

(1) Obstacles.<br />

� Supplement the narrative above, focusing specifically on the intent of the countermobility<br />

effort.<br />

� Identify obstacle belts and groups used to support maneuver unit operations throughout<br />

the depth of the AO.<br />

� Assign belt and group responsibilities, priorities, and restrictions to subordinate engineer<br />

units.<br />

� Reference an obstacle matrix if used.<br />

� Identify and assign responsibilities for directed and reserve obstacles.<br />

(2) Situational obstacles.<br />

� Describe the concept for the employment of situational obstacles, focusing on how they<br />

will be used to complement or augment conventional, tactical obstacle efforts.<br />

� Provide details on NAIs, TAIs, decision points, and execution criteria or reference an<br />

obstacle matrix if used.<br />

� Clearly state the headquarters maintaining the authority to use SCATMINEs and any<br />

restrictions on duration (by belt).<br />

c. Tasks to subordinate units.<br />

� State the missions or tasks assigned to each unit that reports directly to the headquarters<br />

issuing the order. Tactical tasks include a purpose that links it to the supported unit concept of<br />

operation.<br />

� Use a separate subparagraph for each unit. Tasks are generally listed in the order they are<br />

executed during the operation.<br />

� Clearly distinguish “be prepared” and “on order” tasks from normal tasks.<br />

d. Coordinating instructions. Include tasks and instructions that are common to two or more<br />

subordinate units and not covered in unit SOPs, including—<br />

� Time or condition when a plan or an order becomes effective.<br />

� CCIR.<br />

� Risk reduction control measures. These are measures unique to this operation. They are not<br />

included in unit SOPs and may include mission-oriented protective posture, vehicle recognition<br />

signals, and fratricide prevention measures.<br />

� Rules of engagement (refer to an annex if required).<br />

� Environmental considerations.<br />

� Additional coordinating instructions, such as—<br />

� Pertinent coordinating instructions listed in the supported unit order.<br />

� Reporting requirements common to two or more units if not covered in the “signal”<br />

paragraph.<br />

� Authorization for direct coordination between subordinate or adjacent engineer-specific<br />

tasks.<br />

Figure G-3. Engineer unit OPORD (continued)<br />

G-8 <strong>FM</strong> 3-<strong>34.22</strong> 11 February 2009

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!