S3 Department - Standard Operating Procedures

This is the Document Release Information
Article Number:	7CAV-DR-03
Scope:	S3 Department - Regulations and Procedures
Version:	Version 1.0
Effective Date:	25MAR20
Last Modified Date:	DDMMMYYYY
Approving Authority:	MAJ.Tharen.R
Point of Contact:	CPT.Waldie.A

Standard Operating Procedures

Each S3 Operations sub-department is responsible for the following SOP's:

Operations Staff Minimum Requirements

• 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) 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.
• 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.

Operation Creation & Life Cycle

• The person responsible for creating and running any operation is considered the Mission Controller
• 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
• 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

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 OIC's to conduct the operation
3. Name the operation
4. Per S1 and S3 Command Staff, ALL campaign and operation names must be unique and may not be repeated due to tracking purposes
   1. For weekly/repeatable operations, they should be titled: Campaign Month Op Name Year, Operation Name #
   2. Example: Campaign March Warfare Wednesday 2020, Operation Warfare Wednesday #36
5. Submit it to your Operations Lead for approval
6. Once approved, work with your Operations Lead to schedule the op
7. Post it using the S3 Events tool
8. Run the mission as the Mission Controller on the day of the op
9. 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
10. 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
11. 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
12. Any major issues should be passed up the S3 CoC as necessary
13. The op's designated OIC needs to post the official AAR immediately, and update the AAR within 48 hours
14. The OIC will post medal recommendations no later than a week after the operation has concluded
15. After the op is run, the Mission Controller is responsible to un-stick the operation posting in the operation posting forum

Operation Scheduling

1. Operations must be posted at least 1 week (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 S3 Ops & Training Calendar as operations are scheduled
3. Further guidance on operation scheduling can be determined by S3 Command Staff and Battalion Staff as required

Operation OIC's

• 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.
• 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 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

It is the operation's designated OIC's responsibility to post an AAR immediately after the mission, so while it is not the Mission Controller's responsibility, the Mission Controller should still be knowledgeable of the process and guide the OIC as required All AAR guidance can be found at the AAR Standard Operating Procedure post or as determined by S3 Command Staff

Exceptions

Exceptions to all of the above may be made at the discretion of the S3 Command Staff.