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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 8<br />

Sustainment Support for Engineer Operations<br />

Good logistics is combat power.<br />

—Lieutenant General William G. Pagonis<br />

Director of Logistics, Gulf War, 1991<br />

Sustaining engineer capabilities in combat poses a tremendous challenge to engineer<br />

commanders and staff at all echelons. With <strong>Army</strong> transformation into a modular<br />

force, the engineer company organic to the BCT became completely dependent upon<br />

BCT sustainment organizations for support. Engineer forces augmenting the BCT<br />

may also rely substantially on those sustainment organizations. The efforts of<br />

engineer planners at all levels to plan and coordinate engineer sustainment are<br />

essential to the full integration of engineers into BCT sustainment structure. Within<br />

the IBCT and HBCT, battalion level sustainment support for the engineer company is<br />

provided through the BSTB. Support is provided through the BSB and headquarters<br />

and headquarters company (HHC) for the SBCT engineer company. Sustainment<br />

support for engineer operations includes logistics provisions, personnel services, and<br />

HSS necessary to maintain and prolong operations until mission accomplishment.<br />

Logistics tasks include transportation, maintenance, supply, EOD, distribution<br />

management, contracting, and field services. This chapter focuses on sustainment<br />

support for the organic engineer company in the BCT and highlights the sustainment<br />

norms within the BCTs that affect augmenting engineer elements. (See <strong>FM</strong> 3-90.5,<br />

<strong>FM</strong> 3-90.6, <strong>FM</strong> 3-90.61, and <strong>FM</strong> 4-90.7 for more information.)<br />

PLANNING<br />

8-1. Successful sustainment involves balancing effectiveness with efficiency. Sustainment operations are<br />

characterized by being able to anticipate requirements, integrate joint and multinational sustainment,<br />

improvise solutions, and be responsive and continuous.<br />

8-2. During the operations process, engineer commanders and staff must plan, prepare, execute, and<br />

continuously assess sustainment support for engineer capabilities. During the MDMP, engineer planners<br />

concurrently develop a sustainment plan while conducting other operational planning. To ensure an<br />

effective sustainment plan, the engineer planner must understand the engineer and supported unit mission,<br />

commander’s intent, and concept of the operation.<br />

8-3. The development of the sustainment plan begins during mission analysis and is refined during<br />

war-gaming. Upon receipt of the mission, engineer planners initiate their portion of the logistics estimate<br />

process, which is described in <strong>FM</strong> 5-0 as an analysis of logistics factors affecting mission accomplishment.<br />

Engineer planners focus the logistics estimate on the requirements for the upcoming mission and the<br />

sustainment of all subordinate engineer units that are organic and task-organized to the supported unit. The<br />

engineer planner predicts support requirements by determining the—<br />

� Type of support required (maintenance, supply, transportation, medical support).<br />

� Quantity of support required.<br />

� Priority of support (type and unit).<br />

8-4. After determining the support requirements, the engineer planner assesses the—<br />

� Sustainment resources available (supported unit, parent unit, contractor, HN).<br />

� Status of sustainment resources (location, maintenance, personnel).<br />

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

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

Saved successfully!

Ooh no, something went wrong!