|
|
| (82 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| == Show/Hide sections == | | [[Category:Regulations]] |
| Here's an example of collapsed/expandable sections:
| | {{DocRelInfo |
| | |articlenumber = 7Cav-AACD-005 |
| | |scope = Supported Airframe Disclosure SOP |
| | |version = Version 1.0 |
| | |effectivedate = 15MAY26 |
| | |lastmodifieddate = 15MAY26 |
| | |approvingauthority = Auxiliary Combat Detachment Commander |
| | |pointofcontact = Auxiliary Combat Detachment HQ |
| | }} |
|
| |
|
| <div class="NavFrame" style="border-style: none; padding: 0px; font-size: 100%;">
| | =A/ACD - Supported Airframe Disclosure= |
| <div class="NavFrame" style="border-style: none; text-align: left; border: #3232CD solid 2px; -moz-border-radius: 10px; padding: 5px; font-size: 85%;">
| |
| <div class="NavHead" style="{{Round corners}}; background: #dcc5fc; text-align: center; padding: 2px; font-size: 160%;"><font face="arial" color="#6B00A8" size="+1">'''About me'''</font></div>
| |
| <div class="NavContent" style="background: #EEEEFF; display: none; font-size: 100%;">
| |
| <!-- Display area is below -->
| |
|
| |
|
| Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text. Sample text.
| | =Purpose= |
| | The purpose of this SOP is to establish a clear and consistent definition of what constitutes a "supported" airframe within A/ACD. The intent of this disclosure is to encourage Troopers to fly the airframes they enjoy, while also establishing a reasonable standard for the unique nature of certain airframes and the expectations placed upon Section Leaders. |
|
| |
|
| <!-- Display area is above -->
| | =Scope= |
| </div></div></div><br />
| | This SOP applies to all sections within the DCS area of operations. |
|
| |
|
| === Test === | | =Policy= |
| {{PortalTest}}[[Category:Main]]__NOTOC____HIDDENCAT____NOGALLERY__
| | Troopers are responsible for communicating their preferred airframes to their Section Staff. |
| <!-- = CREATE TWO COLUMNS = -->
| |
| {| style="width:; margin:0px; color:#000; background:none;"
| |
| |-
| |
| | <!-- == LEFT COLUMN == -->
| |
| | style="border:1px solid #aaaaaa; vertical-align:top; padding:5px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;" |
| |
|
| |
|
| <!-- === INTRODUCTION === -->
| | ===== Operationally Appropriate Airframes: ===== |
| <div style="background-color:#f9f9f9; padding:5px 10px 5px; margin-top: -2px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;">
| | In the event a Trooper wishes to fly a unique airframe during operations, the mission controller reserves the right to decline the request on the basis of realism, mission integration, or the request being submitted too late in the mission-making process, such as during the brief. |
| <div style="text-align:left;position:relative; left:-10px; top:0px; margin-bottom:5px;">[[File:300px-Black-bg rounded cropped.png|300px|link=]]
| |
| <div style="position:absolute; left:10px; top:2px;"><h2 style="font-weight:bold; border-bottom:none; font-size:120%; padding:.15em .4em; color:#f9f9f9;">Upcoming Events</h2></div></div>
| |
|
| |
|
| {|class="wikitable sortable" border="1" style="border-collapse:collapse; font-size:90%;" cellpadding="3px" width="99%"
| | ===== Section Practice Appropriate Airframes: ===== |
| ! Unit<br />
| | Each Trooper requests a particular section prior to their initial primary billet transfer out of RTC. This also applies to transfers both internal and external to A/ACD. It is a reasonable expectation that, when choosing an assigned section or transitioning airframes, Troopers make every effort to match either the airframe or its role to the receiving section. Regardless, practice time will take precedence for the Trooper. |
| ! Description<br />
| |
| ! Date<br />
| |
| ! Time<br />
| |
| |-
| |
| |[[1st Battalion|1st BN]]
| |
| |[http://www.7thcavalry.us/topic/117697-7th-cavalry-arma-3-brcc-09sep15-1900z/ BRCC (ArmA3)]
| |
| |9 September 2015
| |
| |1900Z
| |
| |-
| |
| |[[1st Battalion|1st BN]]
| |
| |[http://www.7thcavalry.us/topic/117743-7th-cavalry-arma3-fsoc-10sep15-1930z/ FSOC (ArmA3)]
| |
| |10 September 2015
| |
| |1930Z
| |
| |-
| |
| |[[2nd Battalion|2nd BN]]
| |
| |[http://www.7thcavalry.us/topic/117695-7th-cavalry-ins-brcc-12-sept-1900z-1500eastern/ BRCC (Insurgency}]
| |
| |12 September 2015
| |
| |1500Z
| |
| |-
| |
| |[[2nd Battalion|2nd BN]]
| |
| |[http://www.7thcavalry.us/topic/117725-2nd-battalion-operation-ins-operation-warhead-13sep15-1900z/ Operation WARHEAD (Insurgency}]
| |
| |13 September 2015
| |
| |1900Z
| |
| |-
| |
| |[[1st Battalion|1st BN]]
| |
| |[http://www.7thcavalry.us/topic/117801-7th-cavalry-arma3-baac-20th-sept2015-1700-zulu/ BAAC (ArmA3)]
| |
| |20 September 2015
| |
| |1700Z
| |
| |-
| |
| |[[1st Battalion|1st BN]]
| |
| |[http://www.7thcavalry.us/topic/117992-7th-cavalry-arma-3-bac-22sept15-2100z/ BAC (ArmA3)]
| |
| |22 September 2015
| |
| |2100Z
| |
| |-
| |
| |[[2nd Battalion|2nd BN]]
| |
| |[http://www.7thcavalry.us/topic/117889-7th-cavalry-20sep15-1800zulu-insurgency-bamc/ BAMC (Insurgency)]
| |
| |20 September 2015
| |
| |1300Z
| |
| |}</div>
| |
|
| |
|
| <!-- === COURSES AND SCHOOLS === -->
| | ===== Unable to Switch: ===== |
| <div style="background-color:#f9f9f9; padding:5px 10px 5px; margin-top: -2px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;">
| | If a Trooper is unwilling or unable to switch airframes to match the section, this is acceptable as long as the Section Leader is making a reasonable effort to include the Trooper in the practice. In DCS, each aircraft is effectively its own game. A Trooper learning an aircraft from the ground up will need to practice both during SP and outside of it to support their own enjoyment and proficiency. SLs are not expected to hold up an entire section to extensively train a Trooper on a differing airframe. |
| <div style="text-align:left;position:relative; left:-10px; top:0px; margin-bottom:5px;">[[File:300px-Black-bg rounded cropped.png|300px|link=]]
| |
| <div style="position:absolute; left:10px; top:2px;"><h2 style="font-weight:bold; border-bottom:none; font-size:120%; padding:.15em .4em; color:#f9f9f9;">Courses and Schools</h2></div></div>
| |
| *[[Basic Combat Training Phase 1 (Bootcamp)|Basic Combat Training Phase 1]]
| |
| *[[Basic Combat Training Phase 2 (Training Unit)|Basic Combat Training Phase 2]]
| |
| *[[Basic Rotary Wing Evaluation]]
| |
| *[[Basic Radio Communications Course (BRCC)|Basic Telephone Operator]]
| |
| *[[Basic Armor Crewman Course (BACC)|Basic Armor Crewman Course]]
| |
| *[[Basic Cannon Crewman Course (BCCC)|Basic Cannon Crewman Course]]
| |
| :''[[1st Battalion Courses|More courses can be found by clicking here!]]''
| |
| </div>
| |
|
| |
|
| <!-- === REPORTS AND LOGS === -->
| | ===== Newly Added Airframes: ===== |
| <div style="background-color:#f9f9f9; padding:5px 10px 5px; margin-top: -2px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;">
| | In the event of a newly added airframe in DCS, the PL has a recommended minimum observation period of two weeks. This cooldown period is recommended, but not required, before allowing the airframe to be used during an SP. This allows Eagle Dynamics and third-party developers time to address immediate bugs associated with the airframe and gives Troopers time to determine whether they intend to continue using the airframe in the future. |
| <div style="text-align:left;position:relative; left:-10px; top:0px; margin-bottom:5px;">[[File:300px-Black-bg rounded cropped.png|300px|link=]]
| |
| <div style="position:absolute; left:10px; top:2px;"><h2 style="font-weight:bold; border-bottom:none; font-size:120%; padding:.15em .4em; color:#f9f9f9;">Reports and Logs</h2></div></div><div class="plainlinks">[[File:7thCavNewPages.PNG|border|right|200px|New Pages|link=Special:NewPages]]
| |
| Various reports and logs relating to site content can be generated, the most popular are the following:
| |
| * [[Special:RecentChanges|Recent changes]] — list all the recent activity and any changes made to any page will be shown here.
| |
| * [[Special:PopularPages|Popular pages]] — give you an idea of which articles are viewed more than others.
| |
| * [[Special:NewPages|New pages]] — list any new articles that have been recently created.
| |
| * [[Special:NewFiles|New files]] — show you a thumbnail gallery of the most recent images uploaded to the site.
| |
| * [[Special:Statistics|Statistics]] — lists page, edit, user and view statistics along with the ten most popular pages.
| |
| </div>
| |
|
| |
|
| | =Definition of Supported Airframe= |
| | In the case of a section not already established around a particular airframe, once the section is stood up, the primary airframe or airframes of that section must be either rotary-wing or fixed-wing, but not both. Once this distinction is made, the airframe designated for use within that section is officially considered "supported." Supported airframes are intended to have basic airframe courses developed for them, allowing Troopers an opportunity to achieve their Senior and Master Wings. |
|
| |
|
| | ''Rotary Wing MOS - 15T & 153A'' |
|
| |
|
| | ''Fixed Wing MOS - 155F & 155A'' |
|
| |
|
| <!-- == SEPERATOR COLUMN == -->
| | ''Refer to 7CAV-R-001 in regard to section minimums. It is recommended to have six Troopers total to establish a section: one Section Leader and five Troopers. This is to ensure parent unit health and prevent section closure due to lost membership.'' |
| |style="border:2px solid transparent;" |
| |
|
| |
|
| <!-- == RIGHT COLUMN == -->
| | =Exceptions= |
| | style="width:450px; border:1px solid #aaaaaa; vertical-align:top; padding:5px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px; background:#fff;"|
| | Approving authority for rotary/fixed-wing mixed sections is the PL. The MOS 155F and 155A will take precedence for assignment to all Troopers within that section. |
| <!-- === FORUM === -->
| |
| <div style="background-color:#f9f9f9; padding:5px 10px 5px; margin-top: -2px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;">
| |
| <div style="text-align:left;position:relative; left:-10px; top:0px; margin-bottom:5px;">[[File:300px-Black-bg rounded cropped.png|300px|link=]]
| |
| <div style="position:absolute; left:10px; top:2px;"><h2 style="font-weight:bold; border-bottom:none; font-size:120%; padding:.15em .4em; color:#f9f9f9;">Our Forum</h2></div></div><div class="plainlinks">
| |
| {| class="mw-collapsible wikitable"
| |
| !Click to
| |
| |-
| |
| |
| |
| The [http://www.7thcavalry.us/index 7th Cavalry Forum] is the Wiki's sister site specifically set up for members and friends of our tactical gaming community. There are a handful of threaded discussions open to visitors where you can ask questions or report issues. Our members enjoy access to much more. We encourage you to sign up for Forum access today! |[[File:7thCavForum.PNG|right|200px|7th Cavalry Forum|link=http://www.7thcavalry.us/index]]
| |
| <br />
| |
| <span style="font-size:200%;">[http://www.7thcavalry.us/index '''Register Now''']</span>
| |
| |}
| |
| </div></div>
| |
|
| |
|
| <!-- === STAFF DEPARTMENTS === -->
| | In the case of a section that has five Troopers assigned to a specific airframe, but cannot afford to split without negatively affecting the parent section or platoon's health, the section must maintain no fewer than five Troopers on said airframe for a period of no less than four Cav weeks to ensure sustainability. |
| <div style="background-color:#f9f9f9; padding:5px 10px 5px; margin-top:; margin-bottom:4px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;">
| |
| <div style="text-align:left;position:relative; left:-10px; top:0px; margin-bottom:5px;">[[File:300px-Black-bg rounded cropped.png|300px|link=]]
| |
| <div style="position:absolute; left:10px; top:2px;"><h2 style="font-weight:bold; border-bottom:none; font-size:120%; padding:.15em .4em; color:#f9f9f9;">Staff Departments</h2></div></div>
| |
| {| class="mw-collapsible wikitable"
| |
| !Click to
| |
| |-
| |
| |
| |
| A '''Staff Department''' is a group of officers and enlisted personnel that provides a bi-directional flow of information between a commanding officer and subordinate military units.
| |
|
| |
|
| *[[S1|Personnel Administration (S1)]]
| | The authority responsible for notifying Company Staff and the DCS ITW S7 Lead of an additional airframe being added to the list of active airframes with developed courses is the Platoon Leader of the subordinate section in question. |
| *[[S2|Intelligence and Security (S2)]]
| |
| *[[S3|Operations and Training (S3)]]
| |
| *[[S5|Public Affairs (S5)]]
| |
| *[[S6|Regimental Information Management Systems (S6)]]
| |
| |}
| |
| </div>
| |
|
| |
|
| <!-- === Regimental Departments === -->
| | =Accountability= |
| <div style="background-color:#f9f9f9; padding:5px 10px 5px; margin-top:; margin-bottom:4px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;">
| | Failure to adhere to the outlined requirements has historically resulted in higher attrition among new Troopers. The DCS AO also cannot reasonably expect to sustain growth if it locks down sections to specific airframes without flexibility. |
| <div style="text-align:left;position:relative; left:-10px; top:0px; margin-bottom:5px;">[[File:300px-Black-bg rounded cropped.png|300px|link=]]
| |
| <div style="position:absolute; left:10px; top:2px;"><h2 style="font-weight:bold; border-bottom:none; font-size:120%; padding:.15em .4em; color:#f9f9f9;">Regimental Departments</h2></div></div>
| |
| {| class="mw-collapsible wikitable"
| |
| !Click to
| |
| |-
| |
| |
| |
| Regimental Departments are groups of officers and enlisted personnel that provide specific functions for the 7th Cavalry.
| |
|
| |
|
| *[[Regimental Recruiting Department]]
| | =Effective Date= |
| *[[Recruit Training Command]]
| | This SOP is effective immediately upon publication and remains in force until amended or revoked by Company-level directive. |
| *[[Judge Advocate General Corps]]
| |
| *[[Military Police Corps]]
| |
| |}
| |
| <!-- === OUR ORGANIZATION === -->
| |
| <div style="background-color:#f9f9f9; padding:5px 10px 5px; margin-top:; margin-bottom:4px; -moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius:10px;">
| |
| <div style="text-align:left;position:relative; left:-20px; top:0px; margin-bottom:5px;">[[File:300px-Black-bg rounded cropped.png|300px|link=]]
| |
| <div style="position:absolute; left:10px; top:2px;"><h2 style="font-weight:bold; border-bottom:none; font-size:120%; padding:.15em .4em; color:#f9f9f9;">Our Organization</h2></div></div><div class="plainlinks">
| |
| {| class="mw-collapsible mw-collapsed wikitable"
| |
| !Click to
| |
| |-
| |
| |
| |
| *[[Regimental Organization|Command Structure]] leading from the Regimental Commander through the Regimental Command Staff (HQ) and Battalion Staff down to the newest recruits.
| |
| *[[Rank|Rank System]] of hierarchical relationships in the 7th Cavalry. It is modeled after the US military ranking system.
| |
| *[[Uniform military code of justice|UCMJ]] for 7th Cavalry is based on the Uniform Code of Military Justice used by the United States military. It has been modified and simplified to support the needs of our gaming community. All members of 7th Cavalry are subject to the standards set forth in the UCMJ.
| |
| |}
| |
| </div>
| |
| </div>
| |
| | |
| == Testing Sections ==
| |
| | |
| === SOP UI/UX Revamp
| |
| This is the Document Release Information
|
| Article Number:
|
7Cav-AACD-005
|
| Scope:
|
Supported Airframe Disclosure SOP
|
| Version:
|
Version 1.0
|
| Effective Date:
|
15MAY26
|
| Last Modified Date:
|
15MAY26
|
| Approving Authority:
|
Auxiliary Combat Detachment Commander
|
| Point of Contact:
|
Auxiliary Combat Detachment HQ
|
A/ACD - Supported Airframe Disclosure
Purpose
The purpose of this SOP is to establish a clear and consistent definition of what constitutes a "supported" airframe within A/ACD. The intent of this disclosure is to encourage Troopers to fly the airframes they enjoy, while also establishing a reasonable standard for the unique nature of certain airframes and the expectations placed upon Section Leaders.
Scope
This SOP applies to all sections within the DCS area of operations.
Policy
Troopers are responsible for communicating their preferred airframes to their Section Staff.
Operationally Appropriate Airframes:
In the event a Trooper wishes to fly a unique airframe during operations, the mission controller reserves the right to decline the request on the basis of realism, mission integration, or the request being submitted too late in the mission-making process, such as during the brief.
Section Practice Appropriate Airframes:
Each Trooper requests a particular section prior to their initial primary billet transfer out of RTC. This also applies to transfers both internal and external to A/ACD. It is a reasonable expectation that, when choosing an assigned section or transitioning airframes, Troopers make every effort to match either the airframe or its role to the receiving section. Regardless, practice time will take precedence for the Trooper.
Unable to Switch:
If a Trooper is unwilling or unable to switch airframes to match the section, this is acceptable as long as the Section Leader is making a reasonable effort to include the Trooper in the practice. In DCS, each aircraft is effectively its own game. A Trooper learning an aircraft from the ground up will need to practice both during SP and outside of it to support their own enjoyment and proficiency. SLs are not expected to hold up an entire section to extensively train a Trooper on a differing airframe.
Newly Added Airframes:
In the event of a newly added airframe in DCS, the PL has a recommended minimum observation period of two weeks. This cooldown period is recommended, but not required, before allowing the airframe to be used during an SP. This allows Eagle Dynamics and third-party developers time to address immediate bugs associated with the airframe and gives Troopers time to determine whether they intend to continue using the airframe in the future.
Definition of Supported Airframe
In the case of a section not already established around a particular airframe, once the section is stood up, the primary airframe or airframes of that section must be either rotary-wing or fixed-wing, but not both. Once this distinction is made, the airframe designated for use within that section is officially considered "supported." Supported airframes are intended to have basic airframe courses developed for them, allowing Troopers an opportunity to achieve their Senior and Master Wings.
Rotary Wing MOS - 15T & 153A
Fixed Wing MOS - 155F & 155A
Refer to 7CAV-R-001 in regard to section minimums. It is recommended to have six Troopers total to establish a section: one Section Leader and five Troopers. This is to ensure parent unit health and prevent section closure due to lost membership.
Exceptions
Approving authority for rotary/fixed-wing mixed sections is the PL. The MOS 155F and 155A will take precedence for assignment to all Troopers within that section.
In the case of a section that has five Troopers assigned to a specific airframe, but cannot afford to split without negatively affecting the parent section or platoon's health, the section must maintain no fewer than five Troopers on said airframe for a period of no less than four Cav weeks to ensure sustainability.
The authority responsible for notifying Company Staff and the DCS ITW S7 Lead of an additional airframe being added to the list of active airframes with developed courses is the Platoon Leader of the subordinate section in question.
Accountability
Failure to adhere to the outlined requirements has historically resulted in higher attrition among new Troopers. The DCS AO also cannot reasonably expect to sustain growth if it locks down sections to specific airframes without flexibility.
Effective Date
This SOP is effective immediately upon publication and remains in force until amended or revoked by Company-level directive.