S6 – Regimental Information Management Systems: Difference between revisions

From 7th Cavalry Wiki
Jump to navigation Jump to search
Munch.R (talk | contribs)
m Rollback change from test of Visual Editor Test 2
Tags: Manual revert Visual edit
ScarselliT (talk | contribs)
No edit summary
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:Staff Departments]]
[[Category:Staff Departments]]
{{infobox department
{{Infobox department
|DepName=S6 IMO
|DepName=S6 - Information Systems
|DepImg=S6.png
|DepImg=S6.png
|SupDept=[[Regimental Headquarters|Regimental HQ]]
|SupDept=[https://7cav.us/rosters/profile/327/ BG Artyom Stetchkov]
|DepMotto=Innovatione et Excellentia
|DepMotto=Innovatione et Excellentia
|DepOIC= [https://7cav.us/rosters/profile/327/ COL Artyom Stetchkov]
|DepOIC=[https://7cav.us/rosters/profile/1196/ 1LT Rob Corbin]
|DepXO =  
|DepXO=[https://7cav.us/rosters/profile/1420/ 2LT Zachary Markel]
}}
}}


=Introduction=
= Introduction =
The 7th Cavalry Gaming Regiment is the premier gaming clan in the tactical realism community which is due in no small way to the breadth and professional excellence of our technology platforms and services. A carefully tested and maintained collection of custom and off the shelf software provides our members with the tools necessary to build and expand a vibrant virtual community. These tools help bind us together in common goals and values in spite of our divergence into multiple games. Carefully selected and maintained server hardware with complex hosting relationships are the foundation of the S6 Department which is expertly administered 24/7 by a dedicated cadre of highly skilled volunteer system administrators and development staff. The S6 Department is the home to those hard working individuals.


==Ticket System==
The S6 Department serves as the 7th Cavalry Gaming Regiment's technical branch, responsible for the administration, development, and support of the Regiment's information systems and digital services. Through the operation of community platforms, game services, and custom software solutions, the department enables the technology that supports the Regiment's daily operations.
The S6 Department tracks current and ongoing issues with our servers and resources via a forum based [https://7cav.us/applicationform/s6-ticket.21/form Ticket System]. Request for Features, Support, or Inquiries on our servers, website, or other resources are handled by S6 Staff via Tickets.
 
Tickets for S6 Issues, Feature Requests, and Inquiries are assigned specific categories depending on what service they are related to:
S6 is committed to providing reliable, secure, and well-maintained services for the Regiment while supporting its members and leadership. Department personnel are entrusted with privileged access to Regimental systems and are expected to conduct themselves with professionalism, accountability, and adherence to established policies at all times.
{| class="wikitable"
 
! style="width: 20%; background-color: #ffd900; text-align: center;" data-mce-style="width: 20%; text-align: center;"|'''Ticket Category'''
The department is organized into three specialized sub-departments, each responsible for a distinct area of technical operations:
! style="width: 80%; background-color: #ffd900; text-align: center;" data-mce-style="width: 80%; text-align: center;"|'''Description'''
 
* '''Game Staff'''
* '''Forum Staff'''
* '''Development Team'''
 
= Mission and Responsibilities =
 
The mission of the S6 Department is to provide, support, and improve the technical services necessary for the continued operation of the 7th Cavalry Gaming Regiment.
 
The S6 Department is responsible for:
 
* Administering and supporting Regimental information systems and technical services within its assigned authority.
* Supporting official community platforms and game services.
* Developing and maintaining approved custom software solutions.
* Providing technical assistance to Regimental leadership, staff, and members.
* Managing access to S6-supported systems according to assigned duties and established policy.
* Maintaining departmental documentation, technical standards, and operational procedures.
* Protecting systems and information entrusted to S6 through responsible administration and established security practices.
* Responding to and escalating technical incidents affecting supported services.
* Promoting continuous improvement through automation, documentation, and process refinement.
* Advising Regimental leadership on technical matters within the department's areas of responsibility.
 
= Department Structure =
 
== Game Staff ==
 
Game Staff are responsible for the day-to-day administration and support of the Regiment's official game servers within the scope of their authorized access. Staff monitor server availability, perform authorized administrative and configuration actions through approved management tools, assist with issue resolution, and coordinate with the appropriate personnel when an issue falls outside their access or authority.
 
Game Staff access is limited to the approved management panels and tools required for their assigned duties. Game Staff do not administer the underlying server infrastructure, manage server lifecycles, perform operating-system or application patch management, or initiate infrastructure maintenance windows unless separately authorized through another billet or assignment.
 
Issues requiring access or authority beyond that provided to Game Staff must be documented and escalated to S6 Headquarters or the appropriate authorized technical personnel.
 
== Forum Staff ==
 
Forum Staff are responsible for administering the Regiment's forums and the underlying community platform. Their duties include managing user permissions, maintaining forum structure and configuration, assisting with account-related issues, supporting approved extensions and platform features, and helping ensure the continued operation of the Regiment's online community services.
 
Forum Staff coordinate with the Development Team when an issue or request requires custom software development or modification rather than platform administration.
 
== Development Team ==
 
The Development Team is responsible for designing, developing, testing, deploying, documenting, and maintaining approved custom software that supports the Regiment's operations. This includes web applications and features, Discord integrations, automation tools, APIs, and other internally developed systems intended to improve functionality, efficiency, and the member experience.
 
Development work must comply with the Member-Developed Software Policy, applicable S6 policies, established technical standards, and approved development and change-management procedures.
 
= Supported Services =
 
S6 supports technical services assigned to the department by Regimental leadership. Responsibility for a particular service does not imply that every S6 member possesses administrative access to that service. Access is limited according to billet, assignment, operational need, and the principle of least privilege.
 
S6-supported service areas include:
 
* Official game services and approved game-server management tools.
* The Regimental forums and underlying community platform.
* Website applications and custom features.
* S6-managed Discord integrations and automation.
* Regimental APIs, scripts, and internally developed software.
* Approved game-administration, development, repository, monitoring, and integration platforms.
* Access requests, technical incidents, troubleshooting, and service support within the department's assigned authority.
 
Some S6-supported services are hosted or operated through third-party platforms. S6 personnel administer only the functions placed under the department's authority. Infrastructure, vendor, contractual, account-owner, or other issues outside that authority must be escalated to the appropriate personnel.
 
= Requesting S6 Support =
 
Technical assistance is provided through the Regiment's official support channels. Members requiring assistance with game services, website or forum access, S6-managed Discord integrations, or other supported systems must submit a request through the designated S6 ticketing system.
 
Individual S6 clerks must not be contacted directly to request technical assistance. Every request for S6 assistance must be submitted as a ticket so it can be properly documented, tracked, assigned, and escalated when necessary.
 
Support requests should contain sufficient information to allow S6 personnel to identify, reproduce, and resolve the issue efficiently. When applicable, members should provide:
 
* The affected service or system.
* A clear description of the issue or request.
* The approximate time the issue occurred.
* Any relevant error messages.
* Steps already taken to troubleshoot the problem.
* Screenshots or other supporting information that do not disclose sensitive information.
 
Passwords, authentication codes, recovery codes, private keys, access tokens, or other credentials must never be included in a support request.
 
Requests are reviewed and assigned to the appropriate S6 sub-department or authorized personnel. Issues outside an assigned staff member's access or authority must be escalated through the appropriate S6 chain of command.
 
Security concerns, suspected unauthorized access, exposed credentials, or other potentially sensitive incidents should be reported promptly through the approved private escalation channel. Such matters should not be discussed in publicly visible tickets or forum posts.
 
Technical instructions and solutions to common issues may also be available through the S6 Knowledge Base.
 
= Joining the Department =
 
The S6 Department is staffed by volunteers who possess an interest in technology and a commitment to supporting the Regiment. Opportunities within the department vary according to operational requirements and available billets.
 
Prospective staff members are evaluated based on technical aptitude, professionalism, communication skills, reliability, and the ability to work effectively within a collaborative environment. While prior technical experience is beneficial, a willingness to learn and contribute to the department's success is equally valued.
 
S6 assignments may require an application, interview, technical assessment, probationary period, or appointment by departmental leadership. Appointment to S6 does not automatically grant access to every system administered or supported by the department. Access is assigned according to billet, approved duties, demonstrated need, and applicable policy.
 
Opportunities may be available in the following areas:
 
* '''Game Staff''' — Supporting official game services through approved administrative and management tools.
* '''Forum Staff''' — Supporting the forums, community platform, user access, permissions, and platform configuration.
* '''Development Team''' — Developing and maintaining approved custom software, integrations, and automation.
 
Members interested in serving within S6 should monitor Regimental announcements for billet openings and application opportunities. Applicants and serving personnel must comply with the Billet Restriction Policy and all other applicable requirements.


|-
= Department Policies and Procedures =
|Forums
|
* Requests for modification, creation or deletion of threads, forums or permissions to view or special actions.
* Requests or modification of special extensions, widgets or custom scripts in use or suggested.
* Issues with viewing, editing or creating threads or posts.
* Issues with user account, logins or any technical issues with the www.7cav.us website as a whole.
|-
|Discord
|
* Requests for modification, creation or deletion of roles, messages or channels.
* Requests for Features such as but not limited to, Discord bots, API/Website integrations.
* Issues with roles, Discord bot permissions, permissions on channels.


|-
The S6 Department has various policies and procedures governing all aspects of the S6 organization, including use of assets, operating procedures, and responsibilities.
|Battlemetrics
|
* Requests for access to RCON for Battlemetrics supported games that are operated by 7th Cavalry.
* Requests for Features such as but not limited to, Triggers, notifications, Global messages, Player Tags.
* Issues with permissions, roles assigned or technical issues with the third-party application.
* Issues with adding/removing bans, player tracking, native bans and community bans.


{| class="wikitable"
! Document Number
! Policy or Standard Operating Procedure
|-
|-
|Teamspeak
| 7CAV-DR-037
|
| [[S6 Department - Regulations and Procedures]]
* Requests for modification, creation or deletion of Channels, Server Groups, Group Icons.
* Requests for features such as but not limited to, Teamspeak bots, TS3 Server Side Addons/Extensions.
* Issues with permissions, Server group assignments or teamspeak in general.
 
|-
|-
|Github
| 7CAV-DR-038
|
| [[S6 Department - Acceptable Use Policy]]
* Requests for invite into 7Cav organization github.
* Requests forinvitation to Teams or Collaborator access to specific repositories.
* Modification, removal, archival or deletion of Repositories, Workflows, Projects.
 
|-
|-
|Hell Let Loose
| 7CAV-DR-039
|
| [[S6 Department - Responsibilities and Duties]]
* Requests for in-game admin.
* Issues with game server(s) availability or performance.
|-
|-
|Arma 3
| 7CAV-DR-042
|
| [[S6 Department - Billet Restriction Policy]]
* Requests for addition, modification or deletion of mission files or game mods.
|}
* Requests for in-game admin, server password changes, "Zeus" Access on public servers.
* Issues with game server configuration or allocation of resources.
* Issues with game server(s) availability or performance.


|-
== Wiki and Knowledge Base ==
|Squad
|
* Requests for addition or deletion of game mods.
* Requests for in-game admin, server password changes.
* Issues with game server configuration or allocation of resources.
* Issues with game server(s) availability or performance.


|-
The Regimental Wiki and the S6 Knowledge Base serve different documentation purposes.
|Post Scriptum
|
* Requests for addition or deletion of game mods.
* Requests for in-game admin, server password changes.
* Issues with game server configuration or allocation of resources.
* Issues with game server(s) availability or performance.


{| class="wikitable" style="width:75%;"
! style="width:25%; background-color:#ffd900; text-align:center;" | '''Resource'''
! style="width:75%; background-color:#ffd900; text-align:center;" | '''Purpose'''
|-
|-
|API
| '''Regimental Wiki'''
|
| Authoritative departmental policies, responsibilities, governance requirements, and approved Standard Operating Procedures.
* Request for Token Approval or Removal.
* Request for Features such as but not limited to, Endpoints, Additional functions, Oauth.
* Issues with the API, Rate limits, or general use.
|-
|-
|Other
| '''S6 Knowledge Base'''
|
| Technical instructions, platform-specific walkthroughs, configuration guidance, troubleshooting information, and solutions to common issues.
* Issues or Requests that do not pertain to the above categories and is a function or resource maintained by S6
 
|}
|}


=S6 Applications=
Technical instructions should not be duplicated unnecessarily in formal policies or SOPs. Where appropriate, an SOP should establish the required process and refer personnel to the applicable Knowledge Base article for detailed technical instructions.
The S6 department has a commitment to providing administration and development of our services and operations. While this is a voluntary position, we have high standards for our department staff and require a vetting process to determine if a candidate for S6 is best suited for the responsibilities and duties that come with the position. This vetting process will evaluate your skills, talents, past experience, and overall knowledge and availability to do the tasks required. With exception of the S6 - Developer role, availability of these roles are upon position opening and are not available by request.


'''Roles:'''
= S6 Leadership History =
* ARMA Game Clerk
* Squad Game Clerk
* Hell Let Loose Game Clerk
* Post Scriptum Game Clerk
* Developer


==S6 Game Clerk==
The following members have served as the S6 1IC and contributed to the development of the Regiment's technical operations.
Game Clerks are responsible for operation and basic administrative tasks for their respective game server(s). While in some cases a game clerk may have assigned duties to more than one game, they are considered subject matter experts in their role. Game Clerks are expected to know and understand how to configure, troubleshoot, and maintain our game servers where in addition they are the first point of contact for issues with our game servers and the first to respond.
==S6 Developer==
The 7th Cavalry Gaming Regiment has several custom services, scripts, and software actively maintained by S6 Administrators and Developer staff. With efficiency and accessibility in mind, S6 Developers actively work to improve day-to-day operations by introducing new ways to automate tasks, implement services, and the overall development of the technologies we use. Developers are individuals with an aspiration to further their knowledge and to learn or work with several programming languages or systems in order to improve our organization and member experience. S6 Developers are given special tools or access to resources that are required to perform duties as assigned where they otherwise would not be available or not permitted. While other S6 roles have defined duties or responsibility, development staff, due to their nature are chosen projects or duties as per their individual skills or interest. An understanding of programming languages such as JavaScript, Golang, PHP, Python, C#/C++, Powershell, etc. are typically what is looked for when we are assessing if someone has the knowledge required. Development staff positions are a position given by request or invitation.
===Internship===
We are looking for members who are willing to learn and have an interest in taking lessons or working with another developer with consideration to availability. Developers are always open to provide feedback and opportunities to train new members for posterity. Internship within the S6 Department as a Jr. Developer is available upon request.


=Policies and Procedures=
{| class="wikitable" style="width:75%;"
The S6 Department has various policies and procedures governing all aspects of the S6 organization, including use of assets, operating procedures, and responsibilities.
! style="width:20%; background-color:#ffd900; text-align:center;" | '''Rank'''
{| class="wikitable" style="width:50%; background:#ffffff; margin:1.2em 0 6px 0; border-width:1px border-style:solid #000000;"
! style="width:35%; background-color:#ffd900; text-align:center;" | '''Name'''
|style="background-color: #ffd900; text-align:center;border:1px solid #000000;width:25%;" |'''Document Number'''
! style="width:45%; background-color:#ffd900; text-align:center;" | '''Dates of Service'''
|style="background-color: #ffd900; text-align:center;border:1px solid #000000;" |'''Policy or Standard Operating Procedure'''
|-
|-
| 7CAV-DR-037 || [[S6 Department - Regulations and Procedures]]
| First Lieutenant
|-align=left
| [https://7cav.us/rosters/profile/1196/ Rob Corbin]
|  7CAV-DR-038 || [[S6 Department - Acceptable Use Policy]]
| 08JUN26 – Present
|-align=left
|  7CAV-DR-039 || [[S6 Department - Responsibilities and Duties]]
|-align=left
|  7CAV-DR-042 || [[S6 Department - Billet Restriction Policy]]
|-align=left
 
|}
 
=Traditions and History=
Below is a list of all previous S6 Officers in Charge.
{| class="wikitable" style="width:75%; margin:1.2em 0 6px 0; border-width:1px border-style:solid #000000;"
! style="width: 120px; background-color: #ffd900; text-align: center;" data-mce-style="width: 120px; text-align: center;"|'''Rank'''
! style="width: 200px; background-color: #ffd900; text-align: center;" data-mce-style="width: 200px; text-align: center;"|'''Name'''
! style="width: 200px; background-color: #ffd900; text-align: center;" data-mce-style="width: 200px; text-align: center;"|'''Dates of Service'''
|-
|-
| style="width: 120px;" data-mce-style="width: 120px;"|Colonel
| Colonel
| style="width: 200px;" data-mce-style="width: 200px;"|[https://7cav.us/rosters/profile/327/ Artyom Stetchkov]
| [https://7cav.us/rosters/profile/327/ Artyom Stetchkov]
| style="width: 200px;" data-mce-style="width: 200px;"|18 Mar 2024 - present
| 18MAR24 – 31MAY26
|-
|-
| style="width: 120px;" data-mce-style="width: 120px;"|Captain
| Captain
| style="width: 200px;" data-mce-style="width: 200px;"|[https://7cav.us/rosters/profile/597/ Ron Sypolt]
| [https://7cav.us/rosters/profile/597/ Ron Sypolt]
| style="width: 200px;" data-mce-style="width: 200px;"|10 Jan 2023 07 Jan 2024
| 10JAN23 07JAN24
|-
|-
| style="width: 120px;" data-mce-style="width: 120px;"|Colonel
| Colonel
| style="width: 200px;" data-mce-style="width: 200px;"|[https://7cav.us/rosters/profile/284/ Isaac Sweetwater]
| [https://7cav.us/rosters/profile/284/ Isaac Sweetwater]
| style="width: 200px;" data-mce-style="width: 200px;"|22 Jul 2020 08 January 2023
| 22JUL20 08JAN23
|-
|-
| style="width: 120px;" data-mce-style="width: 120px;"|Colonel
| Colonel
| style="width: 200px;" data-mce-style="width: 200px;"|[https://7cav.us/rosters/profile/1/ Adam Jarvis]
| [https://7cav.us/rosters/profile/1/ Adam Jarvis]
| style="width: 200px;" data-mce-style="width: 200px;"|11 Feb 2019 - 22 Jul 2020
| 11FEB19 – 22JUL20
|-
|-
| style="width: 120px;" data-mce-style="width: 120px;"|Colonel
| Colonel
| style="width: 200px;" data-mce-style="width: 200px;"|[https://7cav.us/rosters/profile/42/ Matt Treck]
| [https://7cav.us/rosters/profile/42/ Matt Treck]
| style="width: 200px;" data-mce-style="width: 200px;"|15 Feb 2016 - 11 Feb 2019
| 15FEB16 – 11FEB19
|-
|-
| style="width: 120px;" data-mce-style="width: 120px;"|General
| General
| style="width: 200px;" data-mce-style="width: 200px;"|[https://7cav.us/rosters/profile/2829/ Stephen Carter]
| [https://7cav.us/rosters/profile/2829/ Stephen Carter]
| style="width: 200px;" data-mce-style="width: 200px;"|13 Mar 2009 - 15 Feb 2016
| 13MAR09 – 15FEB16
|}
|}

Latest revision as of 04:56, 2 August 2026


S6 - Information Systems
Regimental Oversight BG Artyom Stetchkov
Motto Innovatione et Excellentia
HQ Staff
1IC 1LT Rob Corbin
2IC 2LT Zachary Markel
3IC {{{DepNCOIC}}}
Aide to S6 - Information Systems {{{DepAide}}}
Aide to SecOps {{{Aide}}}
Lead {{{DepLead}}}
Senior {{{DepSr}}}
Reporting Units



Introduction

The S6 Department serves as the 7th Cavalry Gaming Regiment's technical branch, responsible for the administration, development, and support of the Regiment's information systems and digital services. Through the operation of community platforms, game services, and custom software solutions, the department enables the technology that supports the Regiment's daily operations.

S6 is committed to providing reliable, secure, and well-maintained services for the Regiment while supporting its members and leadership. Department personnel are entrusted with privileged access to Regimental systems and are expected to conduct themselves with professionalism, accountability, and adherence to established policies at all times.

The department is organized into three specialized sub-departments, each responsible for a distinct area of technical operations:

  • Game Staff
  • Forum Staff
  • Development Team

Mission and Responsibilities

The mission of the S6 Department is to provide, support, and improve the technical services necessary for the continued operation of the 7th Cavalry Gaming Regiment.

The S6 Department is responsible for:

  • Administering and supporting Regimental information systems and technical services within its assigned authority.
  • Supporting official community platforms and game services.
  • Developing and maintaining approved custom software solutions.
  • Providing technical assistance to Regimental leadership, staff, and members.
  • Managing access to S6-supported systems according to assigned duties and established policy.
  • Maintaining departmental documentation, technical standards, and operational procedures.
  • Protecting systems and information entrusted to S6 through responsible administration and established security practices.
  • Responding to and escalating technical incidents affecting supported services.
  • Promoting continuous improvement through automation, documentation, and process refinement.
  • Advising Regimental leadership on technical matters within the department's areas of responsibility.

Department Structure

Game Staff

Game Staff are responsible for the day-to-day administration and support of the Regiment's official game servers within the scope of their authorized access. Staff monitor server availability, perform authorized administrative and configuration actions through approved management tools, assist with issue resolution, and coordinate with the appropriate personnel when an issue falls outside their access or authority.

Game Staff access is limited to the approved management panels and tools required for their assigned duties. Game Staff do not administer the underlying server infrastructure, manage server lifecycles, perform operating-system or application patch management, or initiate infrastructure maintenance windows unless separately authorized through another billet or assignment.

Issues requiring access or authority beyond that provided to Game Staff must be documented and escalated to S6 Headquarters or the appropriate authorized technical personnel.

Forum Staff

Forum Staff are responsible for administering the Regiment's forums and the underlying community platform. Their duties include managing user permissions, maintaining forum structure and configuration, assisting with account-related issues, supporting approved extensions and platform features, and helping ensure the continued operation of the Regiment's online community services.

Forum Staff coordinate with the Development Team when an issue or request requires custom software development or modification rather than platform administration.

Development Team

The Development Team is responsible for designing, developing, testing, deploying, documenting, and maintaining approved custom software that supports the Regiment's operations. This includes web applications and features, Discord integrations, automation tools, APIs, and other internally developed systems intended to improve functionality, efficiency, and the member experience.

Development work must comply with the Member-Developed Software Policy, applicable S6 policies, established technical standards, and approved development and change-management procedures.

Supported Services

S6 supports technical services assigned to the department by Regimental leadership. Responsibility for a particular service does not imply that every S6 member possesses administrative access to that service. Access is limited according to billet, assignment, operational need, and the principle of least privilege.

S6-supported service areas include:

  • Official game services and approved game-server management tools.
  • The Regimental forums and underlying community platform.
  • Website applications and custom features.
  • S6-managed Discord integrations and automation.
  • Regimental APIs, scripts, and internally developed software.
  • Approved game-administration, development, repository, monitoring, and integration platforms.
  • Access requests, technical incidents, troubleshooting, and service support within the department's assigned authority.

Some S6-supported services are hosted or operated through third-party platforms. S6 personnel administer only the functions placed under the department's authority. Infrastructure, vendor, contractual, account-owner, or other issues outside that authority must be escalated to the appropriate personnel.

Requesting S6 Support

Technical assistance is provided through the Regiment's official support channels. Members requiring assistance with game services, website or forum access, S6-managed Discord integrations, or other supported systems must submit a request through the designated S6 ticketing system.

Individual S6 clerks must not be contacted directly to request technical assistance. Every request for S6 assistance must be submitted as a ticket so it can be properly documented, tracked, assigned, and escalated when necessary.

Support requests should contain sufficient information to allow S6 personnel to identify, reproduce, and resolve the issue efficiently. When applicable, members should provide:

  • The affected service or system.
  • A clear description of the issue or request.
  • The approximate time the issue occurred.
  • Any relevant error messages.
  • Steps already taken to troubleshoot the problem.
  • Screenshots or other supporting information that do not disclose sensitive information.

Passwords, authentication codes, recovery codes, private keys, access tokens, or other credentials must never be included in a support request.

Requests are reviewed and assigned to the appropriate S6 sub-department or authorized personnel. Issues outside an assigned staff member's access or authority must be escalated through the appropriate S6 chain of command.

Security concerns, suspected unauthorized access, exposed credentials, or other potentially sensitive incidents should be reported promptly through the approved private escalation channel. Such matters should not be discussed in publicly visible tickets or forum posts.

Technical instructions and solutions to common issues may also be available through the S6 Knowledge Base.

Joining the Department

The S6 Department is staffed by volunteers who possess an interest in technology and a commitment to supporting the Regiment. Opportunities within the department vary according to operational requirements and available billets.

Prospective staff members are evaluated based on technical aptitude, professionalism, communication skills, reliability, and the ability to work effectively within a collaborative environment. While prior technical experience is beneficial, a willingness to learn and contribute to the department's success is equally valued.

S6 assignments may require an application, interview, technical assessment, probationary period, or appointment by departmental leadership. Appointment to S6 does not automatically grant access to every system administered or supported by the department. Access is assigned according to billet, approved duties, demonstrated need, and applicable policy.

Opportunities may be available in the following areas:

  • Game Staff — Supporting official game services through approved administrative and management tools.
  • Forum Staff — Supporting the forums, community platform, user access, permissions, and platform configuration.
  • Development Team — Developing and maintaining approved custom software, integrations, and automation.

Members interested in serving within S6 should monitor Regimental announcements for billet openings and application opportunities. Applicants and serving personnel must comply with the Billet Restriction Policy and all other applicable requirements.

Department Policies and Procedures

The S6 Department has various policies and procedures governing all aspects of the S6 organization, including use of assets, operating procedures, and responsibilities.

Document Number Policy or Standard Operating Procedure
7CAV-DR-037 S6 Department - Regulations and Procedures
7CAV-DR-038 S6 Department - Acceptable Use Policy
7CAV-DR-039 S6 Department - Responsibilities and Duties
7CAV-DR-042 S6 Department - Billet Restriction Policy

Wiki and Knowledge Base

The Regimental Wiki and the S6 Knowledge Base serve different documentation purposes.

Resource Purpose
Regimental Wiki Authoritative departmental policies, responsibilities, governance requirements, and approved Standard Operating Procedures.
S6 Knowledge Base Technical instructions, platform-specific walkthroughs, configuration guidance, troubleshooting information, and solutions to common issues.

Technical instructions should not be duplicated unnecessarily in formal policies or SOPs. Where appropriate, an SOP should establish the required process and refer personnel to the applicable Knowledge Base article for detailed technical instructions.

S6 Leadership History

The following members have served as the S6 1IC and contributed to the development of the Regiment's technical operations.

Rank Name Dates of Service
First Lieutenant Rob Corbin 08JUN26 – Present
Colonel Artyom Stetchkov 18MAR24 – 31MAY26
Captain Ron Sypolt 10JAN23 – 07JAN24
Colonel Isaac Sweetwater 22JUL20 – 08JAN23
Colonel Adam Jarvis 11FEB19 – 22JUL20
Colonel Matt Treck 15FEB16 – 11FEB19
General Stephen Carter 13MAR09 – 15FEB16