Difference between revisions of "MEMBER ASSIGNMENT / OPORD SOP"

From RTRWIKI
Jump to: navigation, search
 
(21 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
This [[OPORD]] has three different uses that are all closely related. It can be issued as an "Assignment", as an "Operational Order", or as a combination of the two "Assignment/Operational Order".  
 
This [[OPORD]] has three different uses that are all closely related. It can be issued as an "Assignment", as an "Operational Order", or as a combination of the two "Assignment/Operational Order".  
  
All "Assignment/Operational Orders" OPORD's will begin as a PAF. Once the PAF has been processed by the Division Administration Office a DAFN will be issued. The OPORD can now be filled out and filled ( The DAFN is one of a couple "Compulsory Questions" )
+
All "Assignment/Operational Orders" OPORD's will begin as a PAF. Once the PAF has been processed by the [[S1|Division Administration Office]], a DAFN will be issued. The OPORD can now be filled out and filled ( The DAFN is one of a couple "Compulsory Questions" ). Once filed, the DAO will send a PM of the OPORD's link in the "MEMBER ASSIGNMENT /OPORD'S" in the forums and then finalizes the PAF.
  
 +
==MEMBER ASSIGNMENT / OPERATIONAL ORDERS FORMAT==
  
==MEMBER ASSIGNMENT / OPORD SOP ==
+
1.DATE OF ORDERS ( ''Date that the OPORD is filed'' )
  
*1. File PAF , wait for processing
+
2.MEMBER INFO
*2. Obtain DAFN from processed PAF and /or from DAO
+
:a.USE OF FORM - (''ASSIGNMENT, OPERATION ORDERS or ASSIGNMENT AND OPERATION ORDERS '')
*3. File OPORD, use this WIKI for help
+
:b.MEMBERS NAME - ('' The name of the Member, RANK first, that the OPORDS are for'')
*4. P.M. link to OPORD to member (DAO can then mark PAF as "F" Final)
+
:c.PMOS - (''Name of member's POST or Position'')
 +
:d.UNIT - (''Name the UNIT the the member is in, if being ASSIGNED TO A NEW UNIT, NAME THAT UNIT ''
 +
:e.COMMANDING OFFICER - ('' Name there Commanding Officer, this may be different then the OIC of a Operation if you are filing an OPORD also.'')
 +
 
 +
3.ISSUING AUTHORITY
 +
:a.APPROVING AUTHORITY FOR ASSIGNMENT / ORDERS - ('' Rank first , then the name of the Officer Approving the assignment/order that you are filing.'') 
 +
:b.PMOS - (''The POST/DUTY STATION of Officer Approving the assignment/order that you are filing.'')
 +
::;*Sections 4 and 5 are ONLY needed if the form includes a Operational Order.
 +
4.MISSION -
 +
:a.MISSION - ('' Name in a few words, while still being clear the nature of the Mission and it's goals.'')
 +
:b.TASKS - ('' Name specific tasks involved in the Mission.'')
 +
:c.PERSONAL - ('' Name personal involved in the OP.'')
 +
:d.SUPPORT - ('' Name members that can help, offer advice, etc. with the OPORD.'')
 +
:e.EQUIPMENT - (''List Servers and other systems needed and /or to be used in said OPORD.'')
 +
:f.SERVICES - ('' List Resources, Reference Material, Manuals , SOP's needed for OPORD.'')
 +
 
 +
5.SUSTAINMENT
 +
:a.TIME FRAME OF ASSIGNMENT AND OR ORDER
 +
 
 +
6.COMMAND AND CONTROL
 +
:a.OFFICER IN COMMAND OF OPERATION -('' Name Officer in Charge of the OPORD, this maybe different then the members Commanding Officer.'')
 +
:b.OFFICER TO REPORT TO - ('' Name Officer that reports on the OPORD go.'')
 +
:c.INTERVAL OF REPORTS - ('' How often or when a report should be made on an OPORD;'')
 +
 
 +
7.MISSION NOTES
 +
:a.MISSION NOTES -(Any other info that maybe useful for the fulfillment of the OP.'')
 +
 
 +
8.LINK TO PAF - ('' Place the LINK to the originating PAF here.'')

Latest revision as of 21:25, 22 May 2013

This OPORD has three different uses that are all closely related. It can be issued as an "Assignment", as an "Operational Order", or as a combination of the two "Assignment/Operational Order".

All "Assignment/Operational Orders" OPORD's will begin as a PAF. Once the PAF has been processed by the Division Administration Office, a DAFN will be issued. The OPORD can now be filled out and filled ( The DAFN is one of a couple "Compulsory Questions" ). Once filed, the DAO will send a PM of the OPORD's link in the "MEMBER ASSIGNMENT /OPORD'S" in the forums and then finalizes the PAF.

MEMBER ASSIGNMENT / OPERATIONAL ORDERS FORMAT

1.DATE OF ORDERS ( Date that the OPORD is filed )

2.MEMBER INFO

a.USE OF FORM - (ASSIGNMENT, OPERATION ORDERS or ASSIGNMENT AND OPERATION ORDERS )
b.MEMBERS NAME - ( The name of the Member, RANK first, that the OPORDS are for)
c.PMOS - (Name of member's POST or Position)
d.UNIT - (Name the UNIT the the member is in, if being ASSIGNED TO A NEW UNIT, NAME THAT UNIT
e.COMMANDING OFFICER - ( Name there Commanding Officer, this may be different then the OIC of a Operation if you are filing an OPORD also.)

3.ISSUING AUTHORITY

a.APPROVING AUTHORITY FOR ASSIGNMENT / ORDERS - ( Rank first , then the name of the Officer Approving the assignment/order that you are filing.)
b.PMOS - (The POST/DUTY STATION of Officer Approving the assignment/order that you are filing.)
  • Sections 4 and 5 are ONLY needed if the form includes a Operational Order.

4.MISSION -

a.MISSION - ( Name in a few words, while still being clear the nature of the Mission and it's goals.)
b.TASKS - ( Name specific tasks involved in the Mission.)
c.PERSONAL - ( Name personal involved in the OP.)
d.SUPPORT - ( Name members that can help, offer advice, etc. with the OPORD.)
e.EQUIPMENT - (List Servers and other systems needed and /or to be used in said OPORD.)
f.SERVICES - ( List Resources, Reference Material, Manuals , SOP's needed for OPORD.)

5.SUSTAINMENT

a.TIME FRAME OF ASSIGNMENT AND OR ORDER

6.COMMAND AND CONTROL

a.OFFICER IN COMMAND OF OPERATION -( Name Officer in Charge of the OPORD, this maybe different then the members Commanding Officer.)
b.OFFICER TO REPORT TO - ( Name Officer that reports on the OPORD go.)
c.INTERVAL OF REPORTS - ( How often or when a report should be made on an OPORD;)

7.MISSION NOTES

a.MISSION NOTES -(Any other info that maybe useful for the fulfillment of the OP.)

8.LINK TO PAF - ( Place the LINK to the originating PAF here.)