text: Chapter 5
  Engineer Planning
  The engineer planning process is the primary tool for developing engineer estimates.
  The engineer estimate enables the early integration of engineer capabilities into
  combined arms operations. The engineer estimate is an extension of the MDMP.
  SECTION I – INTEGRATED PLANNING
  Commanders direct their staffs and integrate input from subordinate commanders into their planning
  processes. Engineer leaders must understand (and be integral participants in) the planning processes that
  impact engineer operations at their echelon of employment. Supporting engineer unit commanders and
  leaders conduct parallel planning processes that provide effective outcomes for the engineer units employed
  and appropriate input to the higher commander’s process. Geospatial support elements and engineer staff
  planners integrate directly within the planning staff at each echelon to participate in the planning process.
  ENGINEER SUPPORT TO THE PLANNING PROCESS
  Engineer operations are complex and resource- (time-, manpower-, equipment-, and material-)
  intensive, and they require extensive and proactive coordination. Additionally, a successful engineering effort
  requires an understanding of all engineer disciplines (combat, general, and geospatial) and their role in
  supporting the concept of operations. Engineer operations must be directed and synchronized through
  planning as one of the critical activities in the operations process. Many engineer activities also require logic,
  technical expertise, and problem-solving techniques that form the base logic for the planning processes, as
  shown in ADP 5-0. Engineer operations involve the use of some functionally unique analytic tools to solve
  construction, design, facility, and other engineer-specific problems.
  As a significant part of the planning process, the staff recommends the appropriate command and
  support relationship between engineer and maneuver units to the commander. Each situation is unique and
  requires its own solution. Whatever the selected relationship, engineer commanders are inherently
  responsible for ensuring that engineer support tasks are accomplished by subordinate units. In a command
  relationship, command authority over engineer units is given to a maneuver commander for the immediate
  availability of engineer forces, when needed. This relationship is well-suited for offensive tasks and fluid
  situations, allowing the maneuver commander more flexibility in using engineer assets. Command,
  administrative, and logistical responsibilities remain with the parent engineer unit in a support relationship.
  Commanders are assigned a support relationship during the conduct of offense, defense, stability, and DSCA
  operations when subordination of one unit to another is inappropriate. The engineer unit commander
  organizes the unit and allocates tasks so that they effectively meet the needs of the maneuver commander.
  In some cases, the command and support relationship changes during the conduct of operations at a
  time or place at which assigned tasks terminate or resources have been exhausted, such as during the
  execution of a breach. During the breach, a supporting engineer unit may revert from OPCON task
  organization to their organic unit. Similarly, engineers who are task-organized as tactical control during the
  preparation of a BCT defense can be reassigned as tactical control to the United States Army Reserve.
  Table 5-1, page 5-2, depicts the Army command relationship responsibilities of the gaining and losing
  commands. Army command relationships define superior and subordinate relationships between unit
  commanders. By specifying a chain of command, command relationships unify effort and enable
  commanders to use subordinate forces with maximum flexibility. Army command relationships identify the
  degree of control of the gaining Army commander. The type of command relationship often relates to the