APPENDIX C
Orders and Annexes
SUPPORTED-UNIT'S ORDERS AND ENGINEER ANNEX
Orders and annexes are critical components of engineer C2. The engineer commander exercises functional control over the supported-unit engineer operations by including critical instructions in the supported-unit basic order and the engineer annex. He issues a unit order to control the forces he commands. Therefore, he must use a combination of supported-unit and engineer-unit orders to convey the engineer plan.
This appendix addresses the supported-unit OPORD and the engineer annex. Areas covered are the base format of the supported-unit OPORD, highlighting areas where the engineer commander may have direct input, the format and content of the engineer annex, and sample overlays. This appendix also addresses engineer-unit orders. Areas covered are the format and content for the engineer-unit WO and OPORD, including possible annexes, overlays, and FRAGOs.
SUPPORTED-UNIT'S OPORD
Figures C-1a,
C-1b, and
C1c are a sample format of the supported-unit's OPORD. Paragraphs in which the engineer commander may provide engineer input are bolded.
ENGINEER ANNEX
The engineer annex contains information that is not included in the supported-unit basic order but which is critical to the supported-unit engineer plan or required for subordinate engineer planning. It does not include instructions or orders directly to engineer units. All instructions or tasks are addressed to units supported by engineer units, not supporting engineer units. More importantly, the engineer annex covers essential aspects of the entire engineer plan, not just parts that pertain to engineer units.
The engineer annex is not a replacement for a unit order. For example, it does not give subunit orders and service-support instructions to engineer units remaining under the engineer's command. Those orders and instructions are contained in the engineer-unit order. The engineer annex should be clear, complete, brief, and timely and avoid qualified directives. It should include¯
- Critical information derived from the EBA process.
- All critical information and tasks not covered elsewhere in the order.
- Items not covered in SOPs.
- Information and tasks directed to major subordinate elements of the supported unit, not supporting engineer units.
- Information and instructions that have been fully coordinated with other parts of the OPORD, supported-unit commander, and staff.
The engineer annex includes any combination of written instructions, matrices, or overlays needed to convey the necessary details of the engineer plan. The annex in Figures C-2a, C-2b, C-2c, and C-2d provides a standard format for both offensive and defensive operations. This format standardizes the organization of information included as written instructions. The actual content of the annex depends on the type of operation and engineer plan. A standardized annex format makes it easier for the engineer staff officer to remember what should be included and for subordinate staff officers to find required information.
The engineer annex may include matrices and overlays, as necessary, to convey the plan. Matrices may be used as part of the body of the annex or as separate appendixes. They are used to convey or summarize information not needing explanation, such as logistic allocations, obstacle priorities and restrictions, or task summary (execution matrix). Overlays are used to give information or instructions and expedite integration into the overall combined-arms plan. Information included on overlays may include, but is not limited to
- All existing and proposed friendly obstacles and control measures (obstacles, restrictions, and lanes; directed or tactical reserve obstacles; and situational obstacles, including associated NAI/TAI).
- Known and plotted enemy obstacles (must also be on the situation template).
- Logistic locations and routes, as they apply to engineer operations.
- NBC contaminated areas.
- SCATMINE restrictions.
- River-crossing locations and restrictions.
Figures C-3, C-4, and C-5 show sample matrices and overlays.
ENGINEER-UNIT ORDERS
The engineer commander uses a unit order to exercise unit control over engineer units remaining under his command. At the outset of an operation, he uses his order to effect the necessary task organization of engineers, assign initial missions, and establish sustainment integration supporting units. Once the task organization is effective, and during combat operations, the engineer commander directs subsequent unit orders only to those engineers under his command. Orders, missions, and instructions to engineers supporting other units in command relationships are included as tasks to the units in the supported-unit order. The engineer-unit WO is the exception.
The engineer commander issues WOs to engineers to facilitate parallel planning within engineer units and supported-unit engineer staffs. WOs to engineers supporting another unit are for planning only and are not executive.
ENGINEER-UNIT WO
A WO helps engineer staff officers and engineer units initiate planning and preparations for an upcoming operation. It is critical to foster parallel planning at the engineer-unit and supported-unit levels. There is no prescribed format for the WO. It may be either written or oral but should include the following information:
Heading
WOs must always begin with the words "Warning Order" so the recipients understand that they are to use the information as a basis for planning and that orders will follow. The addressees should also be listed in the heading. The engineer-unit WO should address all supporting engineer units.
Situation
This section includes a brief description of friendly and enemy situations and critical events. It may also include probable missions for the supported unit and specified or implied tasks. It may assign tentative tasks for planning only to engineer units.
Attachments and Detachments
This section gives tentative and known changes to the task organization. However, engineers supporting another unit must realize that these changes are for planning purposes and will not be effective until they receive an order from the supported-unit higher HQ.
Earliest Time of Move
This section states the earliest possible time that units must be ready to move. For units under the engineer commander's command, actual movement times may be given, if known. The earliest time of move is critical to synchronizing sustainment operations to support future missions.
Nature and Time of the Operation
This section provides information about the supported-unit plan to foster parallel planning and preparations and to set priorities. Depending on the maturity of the planning process, information may include a concept of engineer operations or tentative scheme of engineer operations. Orders for preliminary action may also be included: assigning engineer tasks such as tactical and technical reconnaissance, establishing Class IV and V supply points, establishing bridge parks, and moving to linkup points. These orders are normally qualified as be-prepared or on-order tasks, depending on how the plan is established. Orders to engineers supporting other units are always on order with execution instructions coming through supported-unit headquarters-generated orders.
Time and Place of Orders Group
Information in this section informs units under the engineer commander's command when and where to receive the entire order and who will attend. Engineer-unit SOPs should identify the composition of the orders group.
Administrative and Logistical Information
This section includes instructions and warning information on changes in unit logistical operations and required coordination/link up with the supported-unit sustainment systems as required by future operations. This information may also direct movement to assembly areas and provide instructions for sustainment after movement.
Acknowledgment
An acknowledgment of receipt is always required to make sure all addressees receive the WO.
ENGINEER-UNIT OPORD
The engineer commander issues OPORDs to all units under his command. Initially, the engineer commander's OPORD may include any engineer unit operating in the supported-unit area, as necessary, to effect the task organization, assign missions, and establish sustainment responsibility at the outset of an operation. Once the task organization is effected, all instructions and missions to engineers supporting other units are conveyed in supported-unit orders and are addressed to the subordinate supported-unit commanders. The following is an outline of the content of engineer-unit OPORDs using the standard five-paragraph field order (Figures C-6a,
C-6b,
C-6c,
C-6d,
C-6e, and
C-6f). When the order is an OPLAN instead of an OPORD, assumptions on which the plan is based are included at the end of the Situation paragraph.
ENGINEER-UNIT FRAGO
The engineer commander will frequently need to modify his OPORD by using FRAGOs to make changes in engineer operations that allow the supported unit to take advantage of tactical and operational opportunities. He issues FRAGOs only to engineer units under his command. (Supported units will issue their own FRAGOs to convey changes in instructions to engineers supporting other units in command relationships.) A FRAGO does not have a specified format, but an abbreviated OPORD format is usually used. A FRAGO should maximize the use of the current OPORD and specify only information and instructions that have changed.
Rarely will the engineer commander issue a FRAGO to his subordinate commanders face-to-face. He will normally issue it over the radio or telephone. He may use a staff member to issue the FRAGO in person to subordinate engineer commanders. This ensures the engineer commander that the commanders understand the FRAGO, and it allows the commander to include graphics. The engineer commander should include the following items in a FRAGO:
Changes to Task Organization
Include any changes to unit task organizations made necessary by modifying the order.
Situation
Include a brief statement of current enemy and friendly situations, which usually gives the reason for the FRAGO. Update subordinate supported units on the current status of engineer missions, if necessary.
Concept
Give changes to the scheme of engineer operations and the corresponding changes to subunit tasks. Include any changes in the supported unit or engineer-unit commander's intent, if necessary.
Coordinating Instructions
Include changes to Service Support and Command and Signal paragraphs of the current OPORD, if made necessary by the change in scheme of engineer operations.
|
NEWSLETTER
|
|
Join the GlobalSecurity.org mailing list
|
|
|
