20.11.2012 Views

ATTP 5-0.1 Commander and Staff Officer Guide - Army Electronic ...

ATTP 5-0.1 Commander and Staff Officer Guide - Army Electronic ...

ATTP 5-0.1 Commander and Staff Officer Guide - Army Electronic ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Plans <strong>and</strong> Orders<br />

employment of units in operations, including the ordered arrangement <strong>and</strong> maneuver of units in relation to<br />

each other <strong>and</strong> to the enemy within the framework of an operational-level or campaign plan. There are<br />

several types of plans:<br />

� Campaign plan.<br />

� Operation plan.<br />

� Supporting plan.<br />

� Concept plan.<br />

� Branch.<br />

� Sequel.<br />

12-13. A campaign plan is a joint operation plan for a series of related major operations aimed at<br />

achieving strategic or operational objectives within a given time <strong>and</strong> space (JP 5-0). Developing <strong>and</strong><br />

issuing a campaign plan is appropriate when the contemplated simultaneous or sequential military<br />

operations exceed the scope of a single major operation. Only joint force comm<strong>and</strong>ers develop campaign<br />

plans.<br />

12-14. An operation plan is plan for the conduct of military operations prepared in response to actual <strong>and</strong><br />

potential contingencies (JP 5-0). An operation plan (OPLAN) may address an extended period connecting a<br />

series of objectives <strong>and</strong> operations, or it may be developed for a single part or phase of a long-term<br />

operation. An OPLAN becomes an operation order when the comm<strong>and</strong>er sets an execution time or<br />

designates an event that triggers the operation.<br />

12-15. A supporting plan is an operation plan prepared by a supporting comm<strong>and</strong>er, a subordinate<br />

comm<strong>and</strong>er, or an agency to satisfy the requests or requirements of the supported comm<strong>and</strong>er’s plan<br />

(JP 5-0). For example, the ARFOR comm<strong>and</strong>er develops a supporting plan as to how <strong>Army</strong> forces will<br />

support the joint force comm<strong>and</strong>er’s campaign plan or OPLAN.<br />

12-16. In the context of joint operation planning level 3 planning detail, a concept plan is an operation<br />

plan in an abbreviated format that may require considerable expansion or alteration to convert it into a<br />

complete operation plan or operation order (JP 5-0). Often branches <strong>and</strong> sequels are written as concept<br />

plans. As time <strong>and</strong> the potential allow for executing a particular branch or sequel, these concept plans are<br />

developed in detail into OPLANs.<br />

TYPES OF ORDERS<br />

12-17. An order is a communication—verbal, written, or signaled—which conveys instructions from a<br />

superior to a subordinate. <strong>Comm<strong>and</strong>er</strong>s issue orders verbally or in writing. The five-paragraph format<br />

(situation, mission, execution, sustainment, <strong>and</strong> comm<strong>and</strong> <strong>and</strong> signal) remains the st<strong>and</strong>ard for issuing<br />

orders. The technique used to issue orders (verbal or written) is at the discretion of the comm<strong>and</strong>er; each<br />

technique depends on time <strong>and</strong> the situation. <strong>Army</strong> organizations use three types of orders:<br />

� Operation order (OPORD).<br />

� Fragmentary order (FRAGO).<br />

� Warning order (WARNO).<br />

12-18. An operation order is a directive issued by a comm<strong>and</strong>er to subordinate comm<strong>and</strong>ers for the<br />

purpose of effecting the coordinated execution of an operation (JP 5-0). <strong>Comm<strong>and</strong>er</strong>s issue OPORDs to<br />

direct the execution of long-term operations as well as the execution of discrete short-term operations<br />

within the framework of a long-range OPORD.<br />

12-19. A fragmentary order is an abbreviated form of an operation order issued as needed after an<br />

operation order to change or modify that order or to execute a branch or sequel to that order (JP 5-0).<br />

FRAGOs include all five OPORD paragraph headings <strong>and</strong> differ from OPORDs only in the degree of detail<br />

provided. An example of a proper naming convention for a FRAGO to an OPORD is, “FRAGO 11 to<br />

OPORD 3411.” If a FRAGO contains an entire annex, then the proper naming convention would be,<br />

“Annex A (Task Organization) to FRAGO 12 to OPORD 3411.”<br />

14 September 2011 <strong>ATTP</strong> 5-<strong>0.1</strong> 12-3

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

Saved successfully!

Ooh no, something went wrong!