Difference between revisions of "S3 Department - Standard Operating Procedures"

From 7th Cavalry Wiki
Jump to navigation Jump to search
 
(40 intermediate revisions by 10 users not shown)
Line 2: Line 2:
 
|articlenumber  = 7CAV-DR-03
 
|articlenumber  = 7CAV-DR-03
 
|scope  = S3 Department - Regulations and Procedures
 
|scope  = S3 Department - Regulations and Procedures
−
|version  = Version 1.1
+
|version  = Version 3.0
−
|effectivedate  = 25MAR20
+
|effectivedate  = 09JUN21
−
|approvingauthority  = S3 Officer in Charge
+
|lastmodifieddate = 28JUL22
−
|pointofcontact  = S3 Executive Officer
+
|approvingauthority  = S3 1IC
 +
|pointofcontact  = S3 2IC
 
}}
 
}}
  
  
−
=S3 Operations - Standard Operating Procedures=
+
=Minimum Requirements​=
−
Each S3 Operations sub-department is responsible for the following SOP's:
+
==S3 Operations==
 +
* Each game's Operations sub-department is responsible for conducting at least 2 operations per month as the minimum department requirement.
 +
* Operations Staff members must at minimum hold the rank of Private First Class (E-3).
 +
* Operations Staff members are required to run at least one operation per two months unless otherwise instructed by their Operations Lead. Operations Staff who fail to meet the minimum requirement will receive counseling. Subsequent failures to meet the minimum requirement will result in removal from the department.
  
−
==Operations Staff Minimum Requirements==
+
==S3 Public Operations==
 +
* Public Operations Staff members must at minimum hold the rank of Private First Class (E-3).
 +
* Commit to spending one hour weekly on the public server(s) facilitating gameplay.
 +
* Perform game administration as applicable.
  
−
*Each game's Operations sub-department is responsible for conducting at least 2 operations per month as the minimum department requirement
+
==Other Requirements==
−
*Operations Staff members must at minimum hold the rank of Private First Class (E-3) or above and must have no negative action pending or active. It is strongly advised to require members to have attended 5 official S3 operations within their area of operation before being accepted into the department.
+
* Additional requirements may be required due to the need of the game AO the trooper is assigned such as Server Administration Course (SAC) for BattleMetric access. This will be determined by the S3 Operations Lead or S3 Public Operations Lead.
−
*Operations Staff members are required to run at least one operation per two months (60 days) unless otherwise instructed by their Operations Lead. Operations Staff who fail to meet the minimum requirement will receive a VCS. Subsequent failures to meet the minimum requirement will result in removal from the department.
+
* In the event a game AO does not have a Public Staff, the game AO's Operations Staff can fulfill the same duties. This is determined by S3 HQ based on the needs of the game AO.
  
−
==Operation Creation & Life Cycle==
+
=Public Operations Responsibilities=
 +
==Weekly==
  
−
*The person responsible for creating and running any operation is considered the Mission Controller
+
* Ensure that you are tracking your activity on the public server(s).
−
*Each game/S3 Operation sub-department is responsible for their own mission creation and submission SOP's as established by the game's Operations Lead, S3 Battlestaff Lead, and S3 Command Staff
+
* Being active on the public server(s) for one hour weekly
−
*ALL operations must be reviewed and approved by the game's Operations Lead before posting to ensure proper quality and all S3 SOP's have been followed
+
* Acting as a leadership element
−
*All public and internal operations need to be hosted on an official 7Cav server to be official. Operations with other groups/units need to follow additional S5 Department SOP.
+
* Assisting players (Game Admin, helping new players, etc.)
  
−
===Operation Life Cycle===
+
==Daily==
−
#Create the operation or operation concept
 
−
#Create the initial info required for an OPORD or some other format for use in planning by OIC's to conduct the operation
 
−
#Name the operation
 
−
#Per S1 and S3 Command Staff, ALL campaign and operation names must be unique and may not be repeated due to tracking purposes
 
−
##For weekly/repeatable operations, they should be titled: Campaign Month Op Name Year, Operation Name #
 
−
##Example: Campaign March Warfare Wednesday 2020, Operation Warfare Wednesday #36
 
−
#Submit it to your Operations Lead for approval
 
−
#Once approved, work with your Operations Lead to schedule the op
 
−
#Post it using the S3 Events tool
 
−
#Run the mission as the Mission Controller on the day of the op
 
−
#Before the op, assist the mission's OIC to provide a briefing in the appropriate briefing channel to element leads and be able to answer any mission specific questions
 
−
#At the op's conclusion call "Endex", and alert everyone to conduct an AAR (After Action Report) in-game at the squad level or lower
 
−
#Directly after, assist the designated operation OIC to conduct an out-of-game Leader's Debrief in TeamSpeak with all element leads in the appropriate debriefing channel
 
−
#Any major issues should be passed up the [https://7cav.us/threads/s3-chain-of-command.51957/ S3 CoC] as necessary
 
−
#The op's designated OIC needs to [https://7cav.us/forums/after-action-reports.179/ post the framework of the AAR] within 24 hours. The OIC will have 4 days from the end of the operation to fill in the attendance and other information. S1 will process it as final after 7 days.
 
−
#The OIC will post [https://7cav.us/forums/medal-recommendations.208/ medal recommendations] no later than a week after the operation has concluded
 
−
#After the op is run, the Mission Controller is responsible to un-stick the operation posting in the [https://7cav.us/forums/operations.21/ operation posting forum]
 
  
−
==Special Operations==
+
* Respond to requests for assistance in a timely manner. E.g., for ARMA, if the @tactA3 role is pinged because the mission needs to be rolled or the server restarted (can be done via BattleMetrics #shutdown command), you are expected to respond to these requests if you are available and have access.
−
This SOP is native to Arma 3 only.
 
  
−
===Special Operations Definition===
+
=Operational Roles and Responsibilities​=
−
A "Special event" is an event in which any of the following are true:
+
==Mission Controller​==
−
*The event would require an alteration in the Server mods.
+
The Mission controller is the creator of the operation currently being played. They have also constructed the Initial Operations order and will likely provide administrative and interactive support during the operation where required.
−
*The event would require a deviation in faction.
+
==Officer In Command (OIC)​==
−
**For example, playing as Russian forces.
+
An operation's Officer In Command (OIC) for an official operation is ideally the person acting in overall command of 7Cav in-game forces, regardless of rank or billet. While actual officers or senior NCO billets would be preferred and receive priority for those roles in operations, rank or primary leadership billet are not a requirement to be an OIC. The highest ranked individual on the scene is not the OIC of the operation by default, however, OIC may be delegated to qualified individuals per Mission Controller's discretion. OIC's and Mission Controllers are intended and encouraged to be different roles fulfilled by different people, however, they can sometimes overlap to be the same person.
−
*The event is based upon the premise of PVP or three faction contention.
+
==Element Leader​==
 +
An Element Leader is a soldier who has signed up for and acts as a combat leader, leading a group of individuals in support of the OIC. This is usually identifiable by being assigned a Platoon Level callsign, such as Viking-1, Able, or Tincan. Squad Leaders & Pilots are two examples of Element leaders.
 +
==Troopers​==
 +
If you are neither the Officer In Command, Mission Controller nor an Element Leader, you fall under the Trooper definition. Troopers don't have a lot of responsibilities during operations beyond having a good time and participating. As good practice, sometime within the week after the operation, a Trooper should go to the AAR thread for the operation they attended and ensure their name is listed there. If it isn't, contact whoever your element leader was and make sure they are aware.
 +
=Operation Scheduling​=
  
−
===Approving Authority===
+
# Operations must be posted at least 7 days prior to the run date to allow troopers reasonable time to sign up
−
The approving authority for all special events is the S3 Command Staff, upon review by Regimental Command Staff.
+
# All operations must be added as events to the [https://7cav.us/events/ Events Calendar] on the forums as operations are scheduled
 +
# Operations should not be scheduled that would interfere with upcoming FTXs or classes
  
−
===Restrictions===
+
=Operation Creation & Life Cycle​=
−
*For events with a different mod-set:
+
==Overview​==
−
**There may be only one special event which requires the changing of mods every three months.
 
−
*For events with the same mod-set as standard operations:
 
−
**There is no limit for the number of special events which require no modification changeovers.
 
  
−
===Approval process===
+
* All operations must be reviewed and approved by the game's Operations Lead before posting by that operations lead to ensure proper quality and all S3 SOPs have been followed.
−
#An S3 staff member has an idea for a special event.
+
* All public and internal operations need to be hosted on an official 7Cav server. Operations with other groups/units may be hosted on said groups/units' servers. See Special Event Operations for details on the approval process with other groups/units.
−
#The staff member writes up his proposal and starts a PM with the Battlestaff Lead.
 
−
#The Battlestaff Lead reviews viability of the operation proposal.
 
−
#If the operation seems viable and appealing to a wide audience within the CAV, the proposal is forwarded to S3 Command Staff.
 
−
#The proposal is reviewed by S3 Command Staff & the Battlestaff Lead for playability and is ranked with other proposals for selection.
 
−
#S3 Command Staff approaches Regimental Staff for Operation Signoff and Date assignment.
 
  
−
===Production and execution process===
+
==Operation Life Cycle​==
−
*Once approved the operation is constructed by a designated team - usually, those who created the idea, under the direct supervision of the Battlestaff lead and S3 Command Staff.
 
−
*If the operation requires altered mods, S6 should be contacted to assist with mod changeover.
 
−
*All other Mission production SOPs are to be followed.
 
  
−
==Operation Scheduling==
+
# Create the operation or operation concept.
 +
# Create the initial info required for an OPORD or some other format for use in planning by OICs to conduct the operation as needed as determined by the S3 AO lead.
 +
# Name the operation. All campaign and operation names must be unique and may not be repeated due to tracking purposes
 +
## For weekly/repeatable operations, they should repeat on the calendar and be titled: Campaign Month Year
 +
## Example: March Warfare Wednesday 2020
 +
# Submit it to your Operations Lead for approval with enough time for the operation to be posted at least one week in advance of the planned run date.
 +
# Once approved, work with your Operations Lead to schedule the op.
 +
# Your respective AO's Operations Lead or Assistant Operations Lead will then post the event at least one week in advance.
 +
# If the server needs to be locked, a ticket must be submitted to S6 once the calendar event is posted.
 +
# Upon the selection of an OIC, the Operation Planning SOP comes into effect.
 +
# Run the mission as the Mission Controller on the day of the operation.
 +
# Before the op, assist the mission's OIC to provide a briefing to element leads and answer any mission-specific questions.
 +
# At the op's conclusion call "EndEx", and alert everyone to conduct an AAR (After Action Review).
 +
# Directly after, assist the designated operation OIC to conduct an out-of-game Leader's Debrief in Discord or TeamSpeak (Arma 3 AO) with all element leads.
 +
# The op's designated mission controller or delegated personnel needs to post the AAR within 24 hours. The Attendance must be finalized within 7 days from the end of the operation.
 +
# Medal recommendations must be posted no later than a week after the operation has concluded and may be posted by anyone with medal recommendation authority following the Medal Recommendation SOP Policy Guidelines.
 +
# After the op is run, the Mission Controller is responsible for un-sticking the operation posting.
  
−
#Operations must be posted at least 1 week (7 days) prior to the run date to allow troopers reasonable time to sign up
+
==Special Event​s==
−
#ALL operations must be added as events to the [https://calendar.google.com/calendar/render?cid=ude514e5mllhv7p5lh1704qlhs@group.calendar.google.com#main_7 S3 Ops & Training Calendar] as operations are scheduled
+
Special events are defined as any operation that deviates from the standard 7th Cav modpack, utilizes non-standard assets, or generally deviates from the standard "vanilla" gameplay style as defined by the AO's highest primary billeted HQ. Hence these events must be approved prior to execution. Content decisions for any AO rest solely in the hands of the AO's highest primary billeted HQ and it is the responsibility of S3 to ensure any events that are outside the scope of these content decisions are first approved by said staff prior to execution.
−
#Further guidance on operation scheduling can be determined by S3 Command Staff and Battalion Staff as required
 
  
−
==Operation OIC's==
+
==External Operations==
 +
When organizing an external event involving any personnel not within the 7th Calvary, S5 and S3 must work in conjunction to prepare, plan, and execute the mission. The following steps must be taken before organizing an event with another unit:
 +
# The S5 and S3 AO Leads must agree on a mission they would like to run as a joint operation.
 +
# An S5 and S3 staff member must agree to run the event.
 +
# The operation must be run internally at least once to ensure the operation is squared away which includes a rerun if any changes are made to the operation after testing.
 +
# The S5 and S3 members then agree on a range of dates and times that they can run the event.
 +
# S5/S3 leads then approve these dates for an external event.
 +
# The proposal is then passed to the AO battalion for approval. Battalion Staff may delegate this approval to S5/S3 leads at their discretion. Any events with monetary or requiring significant resources from the battalion or regiment must gain approval from both Battalion Staff and Regimental Staff. Depending on the nature of the event, a private message containing the event post and any relevant SOPs specific to the event must be provided to Battalion Staff when requesting approval. Upon approval from Battalion Staff, Regimental Staff will be given the proposal for approval.
 +
# S5 member then finds another community and organizes the event details with that community.
 +
# S3 member organizes the event internally and runs the event.
  
−
*An operation's Officer-In-Charge (OIC) for an official operation is the person acting in overall command of 7Cav in-game forces, regardless of rank or billet. While actual officers or senior NCO billets would be preferred and receive priority for those roles in operations, rank or primary leadership billet are not a requirement to be an OIC. The highest ranked individual on scene is not the OIC of the operation by default.
+
=The Operational Planning & Briefing Process​=
−
*OIC's and Mission Controller's are intended and encouraged to be different roles fulfilled by different people, however, they can sometimes overlap to be the same person. While this is not encouraged, it is allowed, because it is sometimes unavoidable in games such as Squad, PS, and HLL. For Arma 3, the OIC and *Mission Controller should almost never be the same person.
 
−
*Guidance for attendance at operations can be found [https://7cav.us/threads/attendance-at-operations.24545/ here]. This is the OIC's responsibility to enforce, but a Mission Controller should be knowledgeable about our attendance policy and guide the OIC as required.
 
  
−
==Operation AAR's==
+
# The S3 Department has finished its Pre-Planning preparation and the operation has been posted, including the Mission Controller name.
−
It is the operation's designated OIC's responsibility to post an AAR within 24 hours of the end of the operation. While it is not the Mission Controller's responsibility, the Mission Controller should still be knowledgeable of the process and can guide the OIC as required. All AAR guidance can be found at the [[After Action Report (AAR) SOP]] page or as determined by S3 Command Staff.
+
# A member is selected for the Officer In Command Role, more details on this process can be found in the slotting priorities section.
 +
# The Signed up OIC must then contact the Mission Controller to confirm their slot, and arrange an operation planning meeting. In the event of a player-versus-player operation, both OICs must contact the mission controller.
 +
# The OIC & Mission Controller should then meet to brief the OIC on the mission, the duties of the OIC, and answer any questions they may have, and if necessary, provide guidance on the finalization of the OPORD. Ideally, this will be conducted in Discord. However, a discussion via PMs or Teamspeak, if appropriate, will suffice. This meeting should take place at least one day before the operation is due to start.
 +
# It is then the OICs responsibility to create a plan for the execution of the mission outlined in the OPORD.
 +
# The OIC & the Mission Controller are then able to perform a briefing of the operation jointly. The Mission Controller will provide a brief situation overview, as well as specify the mission. The OIC is responsible for the execution of the mission.
  
−
==Exceptions==
+
=S3 & Leadership Planning Meeting​=
−
Exceptions to all of the above may be made at the discretion of the S3 Command Staff.
+
Once contact is made the OIC & Mission Controller should meet to brief them on the operation they will be planning and leading.
  
−
=S3 Training - Standard Operating Procedures=
+
This will usually cover:
 +
* SITUATION
 +
* MISSION
 +
* Any additional requirements/rules or systems in place which may affect the operation.
 +
* Providing the Officer In Command the Execution portion of the OPORD in order to finalize their plan.
 +
* Providing assistance where required on how to fill in the Operations Order.
 +
* Answering any other questions the OIC may have.
  
−
Each Training School is responsible for the following SOP's:
+
==Operations Order (OPORD) Finalization​==
 +
===Operations Order Completion Deadline​===
 +
The OIC must finish completing the Operations Order (OPORD) at least one hour prior to the start of the operation.
  
−
==Course Scheduling==
+
==What The OIC Is Responsible For In Completing The Operations Order (OPORD)​==
 +
The Officer In Command of the operation is responsible for the filling in of the EXECUTION section of the OPORD primarily. This includes the Commander's Intent and all phases of the execution. The OIC may choose to utilize any planning or briefing methods, however, the OPORD will be provided for their convenience.
  
−
*Unless otherwise approved by the S3 Training Lead and/or S3 Command Staff, each course is run at least once monthly at a time that works for both NA and EU timezones. If this isn't possible, a second running of the course should be done to ensure that at least once per month each course is run for each continent. *More advanced courses can be run less frequently on an approved basis as demand requires.
+
==Operational Briefing​==
−
*Courses must be posted at least 1 week (7 days) prior to the run date to allow troopers reasonable time to sign up
+
In essence, the operational briefing is where you take your planning, and you inform your Element Leaders of your intent and respond to suggestions made by them.
−
*ALL courses must be added as events to the [https://calendar.google.com/calendar/render?cid=ude514e5mllhv7p5lh1704qlhs@group.calendar.google.com#main_7 S3 Ops & Training Calendar] as courses are scheduled
 
−
*Use the https://7cav.us/s3events tool to schedule a class and [https://7cav.us/threads/s3-training-posting-a-class.63517/ follow these instructions]
 
−
*After a class is run, the Lead Instructor is responsible to un-stick the class announcement post
 
  
−
==Course Development & Updates==
+
The briefing is usually done in tandem by the Mission Controller and the Officer In Command.
−
*New Courses:
 
−
**New courses require a proposal form to be sent to the School Lead and then must be sent up the S3 CoC for approval
 
−
***[https://docs.google.com/forms/d/e/1FAIpQLScNRgSBU8swU-XS_Ce6A6IgucuaiUiCj7SL8M_e4Z7zsIvLbw/viewform S3 New Course Proposal Form]
 
−
**After approval is granted by S3 Command Staff, the proposal should then be distributed to the company staff of the affected company of the proposed class for review and approval
 
−
**After approval is granted by Company Staff, the lesson plan and field manual drafts must be developed and once ready, sent up the S3 CoC for review and approval
 
−
**After approval is granted by S3 Command Staff, a demo course must be run and observed by the School Lead plus the S3 Training Lead or a member of S3 Command Staff in order to receive final approval for the school to consistently run the class
 
−
***Demo classes can be run as the first class that includes a normal class posting and regular student participation that counts for class credit
 
−
***The intention is that the course developers/instructors, School Lead, plus the S3 Training Lead or a member of S3 Command Staff can do a final audit together of the demo course and make any final LP or map adjustments as necessary
 
−
*Updates to existing courses:
 
−
**If existing courses require an update, updates need to be handled on a case-by-case basis. The intention is that minor lesson plan or map updates can be approved by School Leads. Larger lesson plan content changes/overhauls should go all the way up the S3 CoC for review and approval.
 
−
*School Leads must ensure Lesson Plans, Manuals, and maps (if applicable) are kept up-to-date and the most current versions are available in each School's respective Google Drive folders.
 
  
−
==Tracking==
+
While there is no SOP in place for the structure of the briefing, a good practice is for the Mission Controller to provide context, situation, and mission for the operation, as well as be present to answer mission or technical questions. While the OIC usually focuses on his intent, and the execution of the mission itself, answering questions and applying suggestions from staff on those subjects.
−
*All classes and instructor accountability data should be tracked and the information provided on all [https://7cav.us/forums/s3-graduations.196/ S3 Graduation posts] recorded on the S3 Master Tracker and each school's own individual tracker, which is maintained by the appropriate School Lead, Training Lead, S3 Command Staff, or its designates
 
−
*Ensure the Lead Instructor forum post on each School's respective forum is kept updated as instructors become lead qualified for each class so each School can track who is qualified to lead instruct/teach which class
 
  
−
==Instructor Minimum Requirements==
+
==Operations & Campaigns Exempt From The Leadership Planning Process​==
−
*Instructors in any course should have the course qualification prior to attending as an assistant instructor. For new courses, the course developers will run the course for the first few runs.
+
This section serves as a maintained list of the campaigns and operations which are exempt from having to follow this process:
−
*Instructors must hold the rank of Private First Class (E-3) or above and must have no negative action pending or active
+
Each AO is allowed to exempt one, recurring event from the leadership planning process; generally, these operations are public with the goal of recruitment. For example:
−
*Instructors are required to assist or lead instruct a course at least once monthly. Instructors who fail to meet this minimum requirement will receive a VCS. Subsequent failures to meet the minimum requirement will result in removal from the department.
+
* Warfare Wednesday.
−
*Previous Instructors that were out of the S3 Department longer than 6 months have to do a refresher on all courses the school offers in the form of one assist before they can teach courses on their own
+
* Trenched n' Tuesday.
  
−
==Lead Instructor Requirements==
+
=Slotting and Slot Priority​=
−
Lead Instructors must go through the following process:
+
Due to the wide variety of MOS's and a number of troopers available in the Cavalry, a slotting priority and claim system is in place to ensure that slots are staffed by those most qualified for those positions, whilst still allowing the opportunity for other junior staff to fill those positions upon request, or when required. Only leadership and speciality specialty slots are under this purview.
−
#Attended the course first as a student
 
−
#Attend 1 run-through of the course as an assistant
 
−
#Lead instruct the course at least once under the supervision of a qualified lead instructor for that specific course
 
  
−
==Arma 2 Class Equivalencies==
+
==Operational Signups​==
−
Soldiers who have successfully completed an Arma 2 class are not required to re-do the class in Arma 3. Students are able to sign up and participate in the course however, and will receive credit as a new MILPACS entry.  
+
To assert your "claim" for a specialty or leadership slot in an operation you must:
 +
Sign up in the mission thread containing your desired leadership role ahead of the operational briefing at least 24 hours prior to operation start to guarantee placement.
 +
All levels of leadership (including pilots) must be in the appropriate Briefing/Debriefing TS channel in time for briefing or are subject to losing their spot at least 30 minutes prior to the start of the operation.
 +
If you fail to complete any of the above requirements, your claim on the slot is forfeit and the next individual according to the below slot priority can take your slot.
  
−
==Recruit Eligibility to Attend Classes==
+
==Officer In Command Signups​==
−
Recruits are permitted to attend any S3 Classes or Operations if they have successfully completed Basic Combat Training. S3 Instructors may ask a recruit if they are unsure of their status, or discuss with Recruit Training Command personnel.
+
If the member is applying for the OIC position for the operation, in addition to the above requirements, the member must reserve the role three days in advance to the start of the operation and contact the mission controller at least one day prior to the operation for leadership briefing. Failure to comply may result in loss of OIC role. In the event multiple individuals request to be OIC before the three-day cut-off period, priority will be given as follows:
  
−
==Staff taking ELOA==
+
# <span class="fixed-color">Officer from AO of operation by rank</span>
 +
# <span class="fixed-color">NCO from AO of operation by rank</span>
 +
# <span class="fixed-color">Officer not from AO of operation by rank</span>
 +
# <span class="fixed-color">NCO not from AO of operation by rank</span>
 +
# <span class="fixed-color">Enlisted by rank</span>
 +
<span class="fixed-color">The slotting priority listed above only applies until 72 hours prior to the operation. During that time, any higher slot can "bump" a lower slot from an OIC signup. Once the operation is within 72 hours, the OIC position is now locked. if someone of a lower slot priority has signed up to OIC, they will be allowed to retain their role. It is within the discretion of the highest ranking officer within an AO (generally Battalion CO) to overrule this retainment of role on a case by case basis.</span>
  
−
When an instructor goes on ELOA, they are automatically removed from the department. When they return, if you want them back in your school, you must make a new position announcement post.
+
==Slot Priority List​==
 +
Slot priority is based upon (in combination):
 +
* MOS matches the slot they are applying for.
 +
* Qualifications or certifications from classes that support the role.
 +
* Order of sign-up.
  
−
==Surveys==
+
==Slot Priority Matrix==
  
−
For all courses that are run, a survey will be sent to the participants at the end of the class. Use the appropriate game AO survey located here: [https://7cav.us/threads/s3-training-survey.25941/ S3 Training Survey].
+
{| class="wikitable" style="width:75%; margin:1.2em 0 6px 0; border-width:1px border-style:solid #000000;"
 +
|-
 +
| style="width: 120px; text-align: center;" data-mce-style="width: 120px; text-align: center;"|'''Signed up'''
 +
| style="width: 200px; text-align: center;" data-mce-style="width: 200px; text-align: center;"|'''Correct MOS'''
 +
| style="width: 200px; text-align: center;" data-mce-style="width: 200px; text-align: center;"|'''Qualified'''
 +
| style="width: 200px; text-align: center;" data-mce-style="width: 200px; text-align: center;"|'''Priority'''
  
−
==Exceptions==
+
|-
 +
| style="width: 120px;" data-mce-style="width: 120px;"|Yes
 +
| style="width: 200px;" data-mce-style="width: 200px;"|Yes
 +
| style="width: 200px;" data-mce-style="width: 200px;"|Yes
 +
| style="width: 200px;" data-mce-style="width: 200px;"|1st
 +
|-
 +
| style="width: 120px;" data-mce-style="width: 120px;"|Yes
 +
| style="width: 200px;" data-mce-style="width: 200px;"|Yes
 +
| style="width: 200px;" data-mce-style="width: 200px;"|No
 +
| style="width: 200px;" data-mce-style="width: 200px;"|2nd
 +
|-
 +
| style="width: 120px;" data-mce-style="width: 120px;"|Yes
 +
| style="width: 200px;" data-mce-style="width: 200px;"|No
 +
| style="width: 200px;" data-mce-style="width: 200px;"|Yes
 +
| style="width: 200px;" data-mce-style="width: 200px;"|3rd
 +
|-
 +
| style="width: 120px;" data-mce-style="width: 120px;"|Yes
 +
| style="width: 200px;" data-mce-style="width: 200px;"|No
 +
| style="width: 200px;" data-mce-style="width: 200px;"|No
 +
| style="width: 200px;" data-mce-style="width: 200px;"|4th
 +
|}
  
−
Exceptions to all of the above may be made at the discretion of S3 Command Staff
+
==OIC Prerogative​==
 +
The OIC is the arbiter and end-all for slotting within the operation. For example; two individuals sign up for the same leadership slot. The OIC can adjust who is slotted in each role based on the priority above, the order of slot claiming and who is in attendance at the briefing.
 +
 
 +
In the event that there are still slots left over, be civil, be kind. If you are the OIC, take up your responsibility to guide the other troopers to slot in a civil manner. Where possible, if slots or specialist roles are unclaimed, encourage junior leaders to take the position of those who have not had the opportunity to do so.
 +
 
 +
Be civil, respect your fellow members and have fun.
 +
=After Action Reports=
 +
It is the Mission Controller's responsibility to track overall attendance and post an AAR containing the master attendance list within 24 hours of the end of the operation. Mission controllers may delegate this responsibility to willing delegates such as the OIC, other S3 Staff, or any Officer/NCO. While it is not always the OIC's responsibility, the OIC should still be knowledgeable of the process and assist S3 Staff by sending a reminder to all Element Leads to respond to the AAR Post. Element Leads are charged with recording the attendance of troopers within their squad and maintaining their sub-unit AAR response in the AAR thread.
 +
This SOP will detail the After Action Report (AAR) process, starting from when “EndEx” is called in an Operation to when the S1 Department processes the attendance and medals.
 +
==AAR Guidance==
 +
# "Endex" will be called by the mission controller.
 +
# Mission controllers and OIC may adjust the form of debrief how they see fit.
 +
## Squad Leaders, pilots, and other element leaders as applicable will conduct an AAR debrief in game with their respective elements. This debrief should include feedback, pros & cons, and constructive criticism about the unit's performance and the operation itself. Troopers will voice any questions, comments, or concerns in regards to the operation and the squad leader will make note of all points. Once the in-game debrief is complete, the squad leader will dismiss all troopers and then move into the leaders' debriefing TS channel. Once all elements are present in the leaders debrief channel, the leaders debrief will begin and be conducted by the op's OIC. Each element lead can share their AAR and once completed, the OIC can dismiss everyone.
 +
# The Mission Controller, or a designated replacement - such as the assisting S3 Staff, will create the AAR post, using the "AAR Template" listed below. The designated Individual must agree to this prior to the operation commencing. The designated individual/Mission controller needs to post the framework of the AAR within 24 hours of the end of the operation. The Mission controller or designated individual will have 5 days from the end of the operation to fill in the attendance and other information. S1 will process it as final after 7 days.
 +
# All element leads will post their attendance using the "AAR Response Template" listed below. This must be completed within 24 hours of the operation.
 +
# Once an AAR thread is locked by S1, no further edits can be made to the post. At that point, an S1 Operations ticket would be required to change anything.
 +
 
 +
==Medal Recommendation Procedure​==
 +
Please reference: [[Awards and Decorations]]
 +
 
 +
==AAR Posting Templates​==
 +
Post title examples:
 +
 
 +
GAME | Campaign - Operation
 +
ARMA 3 | Campaign Juniper Spear - Operation Lucky Leaf
 +
SQUAD | Operation Texan
 +
 
 +
==AAR Template==
 +
 
 +
 
 +
===AAR Posting Templates===
 +
Post title examples:
 +
 
 +
GAME | Campaign - Operation<br />
 +
ARMA 3 | Campaign Juniper Spear - Operation Lucky Leaf<br />
 +
SQUAD | Operation Texan<br />
 +
<br />
 +
'''AAR Template'''
 +
<br />
 +
{| class="wikitable mw-collapsible mw-collapsed"
 +
!Click to
 +
|-
 +
|
 +
<div style="text-align: center;">
 +
 
 +
'''DEPARTMENT OF THE ARMY'''<br />
 +
'''S3 BATTLE STAFF'''<br />
 +
'''Headquarters'''<br />
 +
'''7th Cavalry Regiment'''<br />
 +
'''COMBAT AFTER ACTION REPORT'''​<br />
 +
</div>
 +
Name of Combat Mission:<br />
 +
Campaign of Combat Mission (If applicable):<br />
 +
Number within campaign:<br />
 +
Game:<br />
 +
Server Hosted on:<br />
 +
Date of Combat Mission:<br />
 +
Time of Combat Mission (Zulu):<br />
 +
Mission OIC:<br />
 +
Mission Controller:<br />
 +
 
 +
Number of Attendees:<br />
 +
 
 +
7th Cavalry Personnel Involved in Action:<br />
 +
 
 +
Mission Controller Actionable Improvements for the Operation:<br />
 +
1.<br />
 +
2.<br />
 +
3.<br />
 +
 
 +
If your name is not listed, please first ensure your element lead posted their AAR response and included your name in their response. If your name is not listed by your element lead please contact them. If your name is listed in the AAR response, but not the master AAR list, please contact whomever posted this AAR.<br />
 +
|}
 +
 
 +
==AAR Response Templates==
 +
===AAR Response Template===
 +
{| class="wikitable mw-collapsible mw-collapsed"
 +
!Click to
 +
|-
 +
|
 +
<div style="text-align: center;">'''DEPARTMENT OF THE ARMY'''<br />
 +
'''S3 BATTLE STAFF<br />'''
 +
'''Headquarters<br />'''
 +
'''7th Cavalry Regiment<br />'''
 +
'''COMBAT AFTER ACTION REPORT<br />'''
 +
</div>
 +
<br />
 +
'''Element Callsign:'''<br />
 +
'''Element Leader:'''<br />
 +
<br />
 +
'''7th Cavalry Personnel Within Element:'''<br />
 +
<br />
 +
'''Pros:'''<br />
 +
<br />
 +
'''Cons:'''<br />
 +
|}
 +
<br />
 +
===Example of AAR Response===
 +
{| class="wikitable mw-collapsible mw-collapsed"
 +
!Click to
 +
|-
 +
|
 +
<div style="text-align: center;">'''DEPARTMENT OF THE ARMY'''<br />
 +
'''S3 BATTLE STAFF<br />'''
 +
'''Headquarters<br />'''
 +
'''7th Cavalry Regiment<br />'''
 +
'''COMBAT AFTER ACTION REPORT<br />'''
 +
</div>
 +
<br />
 +
'''Element Callsign:'''Savage-1<br />
 +
'''Element Leader:'''Sergeant Jonathan Rivers<br />
 +
<br />
 +
'''7th Cavalry Personnel Within Element'''''(Must be dragged and dropped from the Combat Roster and list names only, not any additional information such as roles within a section):''<br />
 +
Sergeant Jonathan Rivers<br />
 +
Sergeant Vishan Seenath<br />
 +
Corporal Kevin Graves<br />
 +
Corporal Rubs Ronen<br />
 +
Specialist Aapeli Djadic<br />
 +
Specialist Al Kubbo<br />
 +
<br />
 +
'''Pros:'''
 +
 
 +
*Excellent Professionalism from all Savage-1 troopers
 +
*Good communications between ground and air assets
 +
 
 +
<br />
 +
'''Cons:'''
 +
 
 +
*Took too long to get geared up
 +
 
 +
<br />
 +
|}
 +
 
 +
==Exceptions to AAR Responses​==
 +
Due to the sheer length of time for some operations, it may not be possible to maintain a single OIC, or element lead per callsign for the entire period. In the case of this event then, the following is acceptable be done:
 +
 
 +
* AAR Responses are not necessary
 +
* S3 Staff will be responsible for posting AAR and monitoring attendance
 +
 
 +
This pertains specifically to 24 hour operations and those run on a weekly basis for public recruiting purposes such as Trenched in Tuesdays, Warfare Wednesdays, ect.
 +
 
 +
=Operational Credit​=
 +
A Soldier is eligible for credit for attending an Operation if all of the following are true:
 +
 
 +
* Their name is on the AAR Post
 +
* They have attended at least one hour of this operation. The only exception to this rule is during 1 life operations, and being killed before playing for one hour.
 +
* The soldier is not currently under a No-Favorable Action (NFA) period.
 +
* The soldier is not currently on Extended Leave of Absence (ELOA)
 +
* The member is not retired or discharged or an active reservist.
 +
* If the member is a recruit, they must have completed boot camp.
 +
 
 +
==Best Practice​==
 +
Best practice for all levels of leadership involved in attendance tracking is for a screenshot of in-game scoreboard and/or Discord attendance (or Teamspeak for Arma 3 AO) to be taken at the beginning, during and at the end of each operational setting.

Latest revision as of 01:43, 20 February 2024

This is the Document Release Information
Article Number: 7CAV-DR-03
Scope: S3 Department - Regulations and Procedures
Version: Version 3.0
Effective Date: 09JUN21
Last Modified Date: 28JUL22
Approving Authority: S3 1IC
Point of Contact: S3 2IC


Minimum Requirements​

S3 Operations

  • Each game's Operations sub-department is responsible for conducting at least 2 operations per month as the minimum department requirement.
  • Operations Staff members must at minimum hold the rank of Private First Class (E-3).
  • Operations Staff members are required to run at least one operation per two months unless otherwise instructed by their Operations Lead. Operations Staff who fail to meet the minimum requirement will receive counseling. Subsequent failures to meet the minimum requirement will result in removal from the department.

S3 Public Operations

  • Public Operations Staff members must at minimum hold the rank of Private First Class (E-3).
  • Commit to spending one hour weekly on the public server(s) facilitating gameplay.
  • Perform game administration as applicable.

Other Requirements

  • Additional requirements may be required due to the need of the game AO the trooper is assigned such as Server Administration Course (SAC) for BattleMetric access. This will be determined by the S3 Operations Lead or S3 Public Operations Lead.
  • In the event a game AO does not have a Public Staff, the game AO's Operations Staff can fulfill the same duties. This is determined by S3 HQ based on the needs of the game AO.

Public Operations Responsibilities

Weekly

  • Ensure that you are tracking your activity on the public server(s).
  • Being active on the public server(s) for one hour weekly
  • Acting as a leadership element
  • Assisting players (Game Admin, helping new players, etc.)

Daily

  • Respond to requests for assistance in a timely manner. E.g., for ARMA, if the @tactA3 role is pinged because the mission needs to be rolled or the server restarted (can be done via BattleMetrics #shutdown command), you are expected to respond to these requests if you are available and have access.

Operational Roles and Responsibilities​

Mission Controller​

The Mission controller is the creator of the operation currently being played. They have also constructed the Initial Operations order and will likely provide administrative and interactive support during the operation where required.

Officer In Command (OIC)​

An operation's Officer In Command (OIC) for an official operation is ideally the person acting in overall command of 7Cav in-game forces, regardless of rank or billet. While actual officers or senior NCO billets would be preferred and receive priority for those roles in operations, rank or primary leadership billet are not a requirement to be an OIC. The highest ranked individual on the scene is not the OIC of the operation by default, however, OIC may be delegated to qualified individuals per Mission Controller's discretion. OIC's and Mission Controllers are intended and encouraged to be different roles fulfilled by different people, however, they can sometimes overlap to be the same person.

Element Leader​

An Element Leader is a soldier who has signed up for and acts as a combat leader, leading a group of individuals in support of the OIC. This is usually identifiable by being assigned a Platoon Level callsign, such as Viking-1, Able, or Tincan. Squad Leaders & Pilots are two examples of Element leaders.

Troopers​

If you are neither the Officer In Command, Mission Controller nor an Element Leader, you fall under the Trooper definition. Troopers don't have a lot of responsibilities during operations beyond having a good time and participating. As good practice, sometime within the week after the operation, a Trooper should go to the AAR thread for the operation they attended and ensure their name is listed there. If it isn't, contact whoever your element leader was and make sure they are aware.

Operation Scheduling​

  1. Operations must be posted at least 7 days prior to the run date to allow troopers reasonable time to sign up
  2. All operations must be added as events to the Events Calendar on the forums as operations are scheduled
  3. Operations should not be scheduled that would interfere with upcoming FTXs or classes

Operation Creation & Life Cycle​

Overview​

  • All operations must be reviewed and approved by the game's Operations Lead before posting by that operations lead to ensure proper quality and all S3 SOPs have been followed.
  • All public and internal operations need to be hosted on an official 7Cav server. Operations with other groups/units may be hosted on said groups/units' servers. See Special Event Operations for details on the approval process with other groups/units.

Operation Life Cycle​

  1. Create the operation or operation concept.
  2. Create the initial info required for an OPORD or some other format for use in planning by OICs to conduct the operation as needed as determined by the S3 AO lead.
  3. Name the operation. All campaign and operation names must be unique and may not be repeated due to tracking purposes
    1. For weekly/repeatable operations, they should repeat on the calendar and be titled: Campaign Month Year
    2. Example: March Warfare Wednesday 2020
  4. Submit it to your Operations Lead for approval with enough time for the operation to be posted at least one week in advance of the planned run date.
  5. Once approved, work with your Operations Lead to schedule the op.
  6. Your respective AO's Operations Lead or Assistant Operations Lead will then post the event at least one week in advance.
  7. If the server needs to be locked, a ticket must be submitted to S6 once the calendar event is posted.
  8. Upon the selection of an OIC, the Operation Planning SOP comes into effect.
  9. Run the mission as the Mission Controller on the day of the operation.
  10. Before the op, assist the mission's OIC to provide a briefing to element leads and answer any mission-specific questions.
  11. At the op's conclusion call "EndEx", and alert everyone to conduct an AAR (After Action Review).
  12. Directly after, assist the designated operation OIC to conduct an out-of-game Leader's Debrief in Discord or TeamSpeak (Arma 3 AO) with all element leads.
  13. The op's designated mission controller or delegated personnel needs to post the AAR within 24 hours. The Attendance must be finalized within 7 days from the end of the operation.
  14. Medal recommendations must be posted no later than a week after the operation has concluded and may be posted by anyone with medal recommendation authority following the Medal Recommendation SOP Policy Guidelines.
  15. After the op is run, the Mission Controller is responsible for un-sticking the operation posting.

Special Event​s

Special events are defined as any operation that deviates from the standard 7th Cav modpack, utilizes non-standard assets, or generally deviates from the standard "vanilla" gameplay style as defined by the AO's highest primary billeted HQ. Hence these events must be approved prior to execution. Content decisions for any AO rest solely in the hands of the AO's highest primary billeted HQ and it is the responsibility of S3 to ensure any events that are outside the scope of these content decisions are first approved by said staff prior to execution.

External Operations

When organizing an external event involving any personnel not within the 7th Calvary, S5 and S3 must work in conjunction to prepare, plan, and execute the mission. The following steps must be taken before organizing an event with another unit:

  1. The S5 and S3 AO Leads must agree on a mission they would like to run as a joint operation.
  2. An S5 and S3 staff member must agree to run the event.
  3. The operation must be run internally at least once to ensure the operation is squared away which includes a rerun if any changes are made to the operation after testing.
  4. The S5 and S3 members then agree on a range of dates and times that they can run the event.
  5. S5/S3 leads then approve these dates for an external event.
  6. The proposal is then passed to the AO battalion for approval. Battalion Staff may delegate this approval to S5/S3 leads at their discretion. Any events with monetary or requiring significant resources from the battalion or regiment must gain approval from both Battalion Staff and Regimental Staff. Depending on the nature of the event, a private message containing the event post and any relevant SOPs specific to the event must be provided to Battalion Staff when requesting approval. Upon approval from Battalion Staff, Regimental Staff will be given the proposal for approval.
  7. S5 member then finds another community and organizes the event details with that community.
  8. S3 member organizes the event internally and runs the event.

The Operational Planning & Briefing Process​

  1. The S3 Department has finished its Pre-Planning preparation and the operation has been posted, including the Mission Controller name.
  2. A member is selected for the Officer In Command Role, more details on this process can be found in the slotting priorities section.
  3. The Signed up OIC must then contact the Mission Controller to confirm their slot, and arrange an operation planning meeting. In the event of a player-versus-player operation, both OICs must contact the mission controller.
  4. The OIC & Mission Controller should then meet to brief the OIC on the mission, the duties of the OIC, and answer any questions they may have, and if necessary, provide guidance on the finalization of the OPORD. Ideally, this will be conducted in Discord. However, a discussion via PMs or Teamspeak, if appropriate, will suffice. This meeting should take place at least one day before the operation is due to start.
  5. It is then the OICs responsibility to create a plan for the execution of the mission outlined in the OPORD.
  6. The OIC & the Mission Controller are then able to perform a briefing of the operation jointly. The Mission Controller will provide a brief situation overview, as well as specify the mission. The OIC is responsible for the execution of the mission.

S3 & Leadership Planning Meeting​

Once contact is made the OIC & Mission Controller should meet to brief them on the operation they will be planning and leading.

This will usually cover:

  • SITUATION
  • MISSION
  • Any additional requirements/rules or systems in place which may affect the operation.
  • Providing the Officer In Command the Execution portion of the OPORD in order to finalize their plan.
  • Providing assistance where required on how to fill in the Operations Order.
  • Answering any other questions the OIC may have.

Operations Order (OPORD) Finalization​

Operations Order Completion Deadline​

The OIC must finish completing the Operations Order (OPORD) at least one hour prior to the start of the operation.

What The OIC Is Responsible For In Completing The Operations Order (OPORD)​

The Officer In Command of the operation is responsible for the filling in of the EXECUTION section of the OPORD primarily. This includes the Commander's Intent and all phases of the execution. The OIC may choose to utilize any planning or briefing methods, however, the OPORD will be provided for their convenience.

Operational Briefing​

In essence, the operational briefing is where you take your planning, and you inform your Element Leaders of your intent and respond to suggestions made by them.

The briefing is usually done in tandem by the Mission Controller and the Officer In Command.

While there is no SOP in place for the structure of the briefing, a good practice is for the Mission Controller to provide context, situation, and mission for the operation, as well as be present to answer mission or technical questions. While the OIC usually focuses on his intent, and the execution of the mission itself, answering questions and applying suggestions from staff on those subjects.

Operations & Campaigns Exempt From The Leadership Planning Process​

This section serves as a maintained list of the campaigns and operations which are exempt from having to follow this process: Each AO is allowed to exempt one, recurring event from the leadership planning process; generally, these operations are public with the goal of recruitment. For example:

  • Warfare Wednesday.
  • Trenched n' Tuesday.

Slotting and Slot Priority​

Due to the wide variety of MOS's and a number of troopers available in the Cavalry, a slotting priority and claim system is in place to ensure that slots are staffed by those most qualified for those positions, whilst still allowing the opportunity for other junior staff to fill those positions upon request, or when required. Only leadership and speciality specialty slots are under this purview.

Operational Signups​

To assert your "claim" for a specialty or leadership slot in an operation you must: Sign up in the mission thread containing your desired leadership role ahead of the operational briefing at least 24 hours prior to operation start to guarantee placement. All levels of leadership (including pilots) must be in the appropriate Briefing/Debriefing TS channel in time for briefing or are subject to losing their spot at least 30 minutes prior to the start of the operation. If you fail to complete any of the above requirements, your claim on the slot is forfeit and the next individual according to the below slot priority can take your slot.

Officer In Command Signups​

If the member is applying for the OIC position for the operation, in addition to the above requirements, the member must reserve the role three days in advance to the start of the operation and contact the mission controller at least one day prior to the operation for leadership briefing. Failure to comply may result in loss of OIC role. In the event multiple individuals request to be OIC before the three-day cut-off period, priority will be given as follows:

  1. Officer from AO of operation by rank
  2. NCO from AO of operation by rank
  3. Officer not from AO of operation by rank
  4. NCO not from AO of operation by rank
  5. Enlisted by rank

The slotting priority listed above only applies until 72 hours prior to the operation. During that time, any higher slot can "bump" a lower slot from an OIC signup. Once the operation is within 72 hours, the OIC position is now locked. if someone of a lower slot priority has signed up to OIC, they will be allowed to retain their role. It is within the discretion of the highest ranking officer within an AO (generally Battalion CO) to overrule this retainment of role on a case by case basis.

Slot Priority List​

Slot priority is based upon (in combination):

  • MOS matches the slot they are applying for.
  • Qualifications or certifications from classes that support the role.
  • Order of sign-up.

Slot Priority Matrix

Signed up Correct MOS Qualified Priority
Yes Yes Yes 1st
Yes Yes No 2nd
Yes No Yes 3rd
Yes No No 4th

OIC Prerogative​

The OIC is the arbiter and end-all for slotting within the operation. For example; two individuals sign up for the same leadership slot. The OIC can adjust who is slotted in each role based on the priority above, the order of slot claiming and who is in attendance at the briefing.

In the event that there are still slots left over, be civil, be kind. If you are the OIC, take up your responsibility to guide the other troopers to slot in a civil manner. Where possible, if slots or specialist roles are unclaimed, encourage junior leaders to take the position of those who have not had the opportunity to do so.

Be civil, respect your fellow members and have fun.

After Action Reports

It is the Mission Controller's responsibility to track overall attendance and post an AAR containing the master attendance list within 24 hours of the end of the operation. Mission controllers may delegate this responsibility to willing delegates such as the OIC, other S3 Staff, or any Officer/NCO. While it is not always the OIC's responsibility, the OIC should still be knowledgeable of the process and assist S3 Staff by sending a reminder to all Element Leads to respond to the AAR Post. Element Leads are charged with recording the attendance of troopers within their squad and maintaining their sub-unit AAR response in the AAR thread. This SOP will detail the After Action Report (AAR) process, starting from when “EndEx” is called in an Operation to when the S1 Department processes the attendance and medals.

AAR Guidance

  1. "Endex" will be called by the mission controller.
  2. Mission controllers and OIC may adjust the form of debrief how they see fit.
    1. Squad Leaders, pilots, and other element leaders as applicable will conduct an AAR debrief in game with their respective elements. This debrief should include feedback, pros & cons, and constructive criticism about the unit's performance and the operation itself. Troopers will voice any questions, comments, or concerns in regards to the operation and the squad leader will make note of all points. Once the in-game debrief is complete, the squad leader will dismiss all troopers and then move into the leaders' debriefing TS channel. Once all elements are present in the leaders debrief channel, the leaders debrief will begin and be conducted by the op's OIC. Each element lead can share their AAR and once completed, the OIC can dismiss everyone.
  3. The Mission Controller, or a designated replacement - such as the assisting S3 Staff, will create the AAR post, using the "AAR Template" listed below. The designated Individual must agree to this prior to the operation commencing. The designated individual/Mission controller needs to post the framework of the AAR within 24 hours of the end of the operation. The Mission controller or designated individual will have 5 days from the end of the operation to fill in the attendance and other information. S1 will process it as final after 7 days.
  4. All element leads will post their attendance using the "AAR Response Template" listed below. This must be completed within 24 hours of the operation.
  5. Once an AAR thread is locked by S1, no further edits can be made to the post. At that point, an S1 Operations ticket would be required to change anything.

Medal Recommendation Procedure​

Please reference: Awards and Decorations

AAR Posting Templates​

Post title examples:

GAME | Campaign - Operation ARMA 3 | Campaign Juniper Spear - Operation Lucky Leaf SQUAD | Operation Texan

AAR Template

AAR Posting Templates

Post title examples:

GAME | Campaign - Operation
ARMA 3 | Campaign Juniper Spear - Operation Lucky Leaf
SQUAD | Operation Texan

AAR Template

Click to

DEPARTMENT OF THE ARMY
S3 BATTLE STAFF
Headquarters
7th Cavalry Regiment
COMBAT AFTER ACTION REPORT​

Name of Combat Mission:
Campaign of Combat Mission (If applicable):
Number within campaign:
Game:
Server Hosted on:
Date of Combat Mission:
Time of Combat Mission (Zulu):
Mission OIC:
Mission Controller:

Number of Attendees:

7th Cavalry Personnel Involved in Action:

Mission Controller Actionable Improvements for the Operation:
1.
2.
3.

If your name is not listed, please first ensure your element lead posted their AAR response and included your name in their response. If your name is not listed by your element lead please contact them. If your name is listed in the AAR response, but not the master AAR list, please contact whomever posted this AAR.

AAR Response Templates

AAR Response Template

Click to
DEPARTMENT OF THE ARMY

S3 BATTLE STAFF
 Headquarters
 7th Cavalry Regiment
 COMBAT AFTER ACTION REPORT


Element Callsign:
Element Leader:

7th Cavalry Personnel Within Element:

Pros:

Cons:


Example of AAR Response

Click to
DEPARTMENT OF THE ARMY

S3 BATTLE STAFF
 Headquarters
 7th Cavalry Regiment
 COMBAT AFTER ACTION REPORT


Element Callsign:Savage-1
Element Leader:Sergeant Jonathan Rivers

7th Cavalry Personnel Within Element(Must be dragged and dropped from the Combat Roster and list names only, not any additional information such as roles within a section):
Sergeant Jonathan Rivers
Sergeant Vishan Seenath
Corporal Kevin Graves
Corporal Rubs Ronen
Specialist Aapeli Djadic
Specialist Al Kubbo

Pros:

  • Excellent Professionalism from all Savage-1 troopers
  • Good communications between ground and air assets


Cons:

  • Took too long to get geared up


Exceptions to AAR Responses​

Due to the sheer length of time for some operations, it may not be possible to maintain a single OIC, or element lead per callsign for the entire period. In the case of this event then, the following is acceptable be done:

  • AAR Responses are not necessary
  • S3 Staff will be responsible for posting AAR and monitoring attendance

This pertains specifically to 24 hour operations and those run on a weekly basis for public recruiting purposes such as Trenched in Tuesdays, Warfare Wednesdays, ect.

Operational Credit​

A Soldier is eligible for credit for attending an Operation if all of the following are true:

  • Their name is on the AAR Post
  • They have attended at least one hour of this operation. The only exception to this rule is during 1 life operations, and being killed before playing for one hour.
  • The soldier is not currently under a No-Favorable Action (NFA) period.
  • The soldier is not currently on Extended Leave of Absence (ELOA)
  • The member is not retired or discharged or an active reservist.
  • If the member is a recruit, they must have completed boot camp.

Best Practice​

Best practice for all levels of leadership involved in attendance tracking is for a screenshot of in-game scoreboard and/or Discord attendance (or Teamspeak for Arma 3 AO) to be taken at the beginning, during and at the end of each operational setting.

Retrieved from "https://wiki.7cav.us/index.php?title=S3_Department_-_Standard_Operating_Procedures&oldid=11030"