Welcome
Combat Operations
Combat Photo Gallery
Uniforms at the OP
Equipment Regulations
Rules of Engagement
The Cimmerians
Contact
Charity Work
10 Troops Are Signed Up For
OP: EARLY PUNCH

Cimmerian Log In

Enter Your Email Address:
Enter Your Password:
 
© Cimmerians Airsoft Association
1992—2007
The name "Cimmerians" is a Federally registered trademark of the Cimmerians Airsoft Association and may not be used without written permission.


SOP_OPCOM
VIEW SPONSORED LINKS

SOP Adotped :
SOP Drafted :
8 FEB 05  

This SOP describes describes the primary duties of the Operation Commander (OPCOM).  All activities are under the oversight of the S3.

 

1)     Operations Planning

a)     90 days to Op:

i)        Report to S3 with initial OP concepts, genre, and historical context

ii)      Write up a scenario brief for the S3 to post to the Op web page

iii)    AO selection (may be pre-selected and/or AO recon may be necessary)

(1)  Begin to study maps and requirements for the specific AO

(2)  Determine what special props, vehicles, or equipment is desired

(a)   Check availability with owners

iv)    Before costs are incurred, review through S3 for solutions / allowances

b)     60 days to Op:

i)        Develop a Flow Of Battle (FOB) sketch (.PPT format) 

(1)   SAMPLE.PPT  or SAMPLE 2.PPT

(2)  This will describe the flow of each evolution (EVO)

(a)   Attack/Defend, Tactical Withdrawal, DEMO, Ambush, etc

(b)   "This team goes here, that team goes there" approach

c)      30 days to Op:

i)        Write up and send a Warning Order to Warriors@cimmerians.org 1 week after the previous Op

ii)      Develop Op Outline

(1)  This is based on the story line of the scenario

(2)  Include historical context and an Op command structure

iii)    Review with S3 for AO and map development (.PDF format)

(1)  Maps must be aerial or topographical, with a grid & compass rose

d)     14 days to Op:

i)        “Flesh-Out” FOB into Op Orders for each EVO (.DOC format)

(1)    SAMPLE OpOrders.doc   andSAMPLE 2 OpOrders.doc

(a)     2 columns helps in planning mission interactions

(b)     Focus on a Radio Plan, Vehicle Plan, and Regeneration Plan

ii)      Review scenario with S3 to determine if the desired “scripted” effect is there

(1)  Do we have the safety valves to “heat up” or “cool-off” the EVO?

(2)    Provide any “FRAG order” inputs at this time

e)     7 days to Op:

i)        Final revisions and review with S3 for Op, attendance, and equipment status

ii)      Coordinate printing out enough Op Orders and maps for operators

2)     Downrange Operations

a)     Stay on the Op Plan as worked out through Operations Planning

b)     Arrive as early as possible to AO to direct AO setup and assign tasks

c)      Coordinate with S3 on issues and brief commanders to set their strategies

d)     Give morning scenario and OP briefing to troops

e)     Facilitate as required w/ S3 and Commanders for ideal flow of battle

i)        This must be transparent to troops

ii)      Act as higher HQ for both sides during EVOs

3)     Post- Operations

a)     After Action Report

i)        Write-up and/or solicit commander AARs and any pictures and videos input from troops

b)     Transfer to S3 for posting to web page

 

 

 

 7feb05 CW

SOP History*********************************************************************

OPCOM - SOP

*************BEFORE THE OP*************

  1. Volunteer well in advance of op 2-3 MONTHS
  2. Report to S3 for duty
  3. Develop initial concepts  - review w/ S3
  4. Identify Historical context for OP
  5. Write up Web Blurb
  6. Write up Warning Order for the Warriors List
  7. Send Warning Order at the end of the previous month
  8. S2 Posts Web blurb
  9. AO selection (may be selcted already)
           -map study req to ident specific AO
  10. Develop Flow of battle sketches (ppt is best)  SAMPLE.PPT  or SAMPLE 2.PPT
           Flow of each evolution w/o scenario overlay (A/D, TacWith, DEMO, Ambush, etc)
           These are very schematic and do not have any scenario details attached. "This team goes
            here that team goes there".
  11. S3 - review - revision
  12. Develop Scenario Outline - short story line of the scenario w/ historical ctxt
  13. Flesh-Out Flow of Battle into Standard CIMM op orders for each EVO SAMPLE OpOrders.doc   and SAMPLE 2 OpOrders.doc
    It is important here that the .doc format be followed, that way we all know where to look for the info when needed. Using the 2 columns helps in planning to see how the 2 forces missions will interact.
        - Radio Plan
        - Vehicle Plan 
        - Regen Plan
  14. Determine what special equipment or props will be needed. Check availability with owners. If costs are incurred get S3 approval.
  15. S3 Review - Would these orders produce the desired scripted effect? Do we have "Real time safety valves" to heat  up or cool-off the EVO.  Revise
  16. S2 - AO Map Development - Aerial or Topo, Grid, compass rose. May require recon to AO.
  17. Define Command Structure for OP - approach indiv cmdrs, special characters, etc
       - CO1 -> CO2 mutial HQ, OpcCom is HQ for both
  18. Develop Frag Order - as needed for detials to inform troops of OP specifics, gear, techniques, ligistics


********* AT THE OP **********

  1. Arrive Early - Maintain an Air of Confidence and Decisiveness
  2. Assign setup tasks
  3. Report to S3 - Progress - Problems
  4. Brief Cmdrs
  5. Give OP Briefing to troops
  6. Act as HQ during EVO
  7. Make adjustments as required in consult w/ S3 and Cmdrs. (This must be transparent to troops)

************After the OP***************

  1. AAR - write up, solicite Cmdrs AARs and any write ups from troops.
  2. Solicit  pics and videos
  3. Transfer to S2/S5 for posting to webpage

 

 



TechShop