engineer on a task-by-task basis. The division engineer controls
all engineer support forward of the LD and coordinates the
support on an area basis.
(5) Until committed to the fight, divisions and separate armored
brigades move behind attacking divisions and over routes that
have been cleared by lead divisions and maintained by corps
combat engineer groups, combat engineer battalions, and CSE
companies. Although the attacking unit's organic engineers clear
sudden blockages along march routes, their mass is forward to
facilitate rapid handover of obstacle-breached lanes.
They
conduct a passage of lines after they are committed on the
continued attack or penetration.
2-6. Summary.
a. Figure 2-5 outlines the decision-making process for determining a
command or a support relationship.
It delineates relationships
based on the necessary response time to the receiving maneuver
element.
Command, administrative, and logistical responsibilities
remain with the parent engineer unit in a support relationship. The
engineer unit commander organizes the unit and suballocates tasks to
effective support the maneuver commander's intent. Table 2-1 shows
who is responsible for C2, task organization and assignment, and
It also shows who reorganizes engineers as
infantry, when necessary.
NOTE: Figure 2-5 and Table 2-1 are quick reference charts that were
designed for use during this correspondence course, and they can be
used as guides during the task-organization process. They are NOT a
substitute for the planning process during the employment of
engineers.
b. Command relationships prescribe the chain of command and the degree
of authority a commander exercises over an engineer unit. Command
authority over engineer units can be given to a maneuver commander
when
he
requires
immediately
responsive
engineer
forces.
Attachment, OPCON, and OPCOM are the primary command relationships
used at division level and below.
These relationships are well-
suited for fluid situations, such as exploitations and pursuit.
Ultimately, task organizations are based on mission and not on
habitual association. Habitual association is training relationship
and does not preclude task organization that allows the most
efficient use of available engineer elements.
EN5483
2-10
Previous Page
