OPORD

From RTRWIKI
Revision as of 15:20, 4 March 2012 by Sym (Talk | contribs) (TYPES)

Jump to: navigation, search

An Operations Order, often abbreviated as OPORD, is an executable plan that directs a unit to conduct a operation. An Operations Order will describe the situation facing the unit, the mission of the unit, and what activities the unit will conduct to achieve the mission goals. Normally an Operations Order will be generated at a Division, or Company headquarters and then given to lower echelons to implement. Each lower echelon as they receive an operations order will in turn develop their own Operations Order which removes extraneous detail and adds details focused on what and how that subunit will implement the higher level OPORD. So an Operations Order at a particular level of the military organization will trigger units involved in the operation to develop their own Operations Order which will borrow from the Operations Order given them so far as the situation and mission but will then add additional details for the activities a specific unit is to conduct.

A standardized multiple paragraph format is used by the Right to Rebel Community as defined by the Division Administration Office. An OPORDER is designed to organize both generalities and specifics of a mission into five standard topics (paragraphs): Situation, Mission, Execution, Service Support, and Command and Signal. Higher level units which have extensive lists or details in a topic will move most of the material to an Annex or an Appendix to the order. This also allows an order be customized to a recipient by easily removing extraneous information for that recipient.

TYPES

MEMBER ASSIGNMENT / OPERATIONAL ORDERS FORMAT

1.DATE OF ORDERS

2.MEMBER INFO

a.USE OF FORM:
b.MEMBERS NAME:
c.PMOS
d.UNIT:
e.COMMANDING OFFICER:

3.ISSUING AUTHORITY

a.APPROVING AUTHORITY FOR ASSIGNMENT / ORDERS
b.PMOS

4.MISSION

a.MISSION:
b.TASKS:
c.PERSONAL:
d.SUPPORT:
e.EQUIPMENT:
f.SERVICES:

5.SUSTAINMENT

a.TIME FRAME OF ASSIGNMENT AND OR ORDER

6.COMMAND AND CONTROL

a.OFFICER IN COMMAND OF OPERATION
b.OFFICER TO REPORT TO.
c.INTERVAL OF REPORTS

7.MISSION NOTES

a.MISSION NOTES:

8.DAFN

a.ORIGINATING AND/OR ASSOCIATED DAFN:

UNIT OPERATIONAL ORDERS FORMAT

1.UNIT OPERATIONAL ORDERS

a.DATE OF ORDERS
b.ORDER NUMBER

2.UNIT

a.UNIT DESIGNATION:
b.COMMANDING OFFICER:

3.ISSUING AUTHORITY

a.UNIT OF ISSUING AUTHORITY
b.APPROVING AUTHORITY FOR ASSIGNMENT / ORDERS
c.PMOS

4.MISSION

a.MISSION:
b.TASKS:
c.PERSONAL:
d.SUPPORT:
e.EQUIPMENT:
f.SERVICES:

5.COMMAND AND CONTROL

a.OFFICER IN COMMAND OF OPERATION
b.OFFICER TO REPORT TO.
c.INTERVAL OF REPORTS

6.MISSION NOTES

a.MISSION NOTES:

Variations

The OPORD is the primary order that is given for a mission however it is not the only type of order that may be issued for a mission. Other types of orders may be issued to tell units an Operations Order may be forthcoming, a WARNO "Warning Order". Or to inform units during the execution of an Operations Order that the situation has changed, and identifying changes in situation and mission, FRAGO "Fragmentary Order".

A Warning Order, or WARNO, is given in advance of the OPORD to let soldiers under the command know that they may be receiving an Operations Order. The WARNO contains a few basic details of the situation and what the mission may entail however much of the pertinent information for a proper Operations Order is still forthcoming.

Once an OPORD is given, the situation may change before the mission has actually begun or during the operation, the situation may change so that the Operations Order must be modified. In these cases the commander will issue a Fragmentary Order, or FRAGO. The FRAGO will state exactly how the situation and/or mission has been changed and what must be done to make up for the change.


References

See also