DEVCOM - DEVCOM to ACD Handover Process
  |
|---|
| This is the Document Release Information | |
| Article Number: | 7CAV-DR-062 |
| Scope: | DEVCOM to ACD Handover Process |
| Version: | 0.1 |
| Effective Date: | UNAPPROVED |
| Last Modified Date: | 22JUN25 |
| Approving Authority: | Regimental Reserve & Development Commander |
| Point of Contact: | DEVCOM 1iC |
Development Command to Auxiliary Combat Detachment Handover Process
The Development Command is the organisation responsible for the identification, planning, launch and support of new Areas of Operation in the 7th Cavalry Regiment. This page lays out the process for game launch planning conducted by the DEVCOM Lead.
Intent
The intent of the DEVCOM 1iC is to ensure there is a structured and repeatable process for the successful internal promotion of games which become new mature Areas of Operation in the 7th Cavalry Gaming Regiment. This shall be achieved by utilising a consistent and robust checklist which ensures all departments are engaged after the game achieves the target 40-members required to promote into ACD. By utilising a clear and publicly declared process all chains of command, including secondary and regimental departments can engage with the Commander’s intent and ensure that the process undergoes continuous improvement as we learn from experience game-to-game. The DEVCOM 2iC and DEVCOM Leads are accountable to the DEVCOM 1iC for achieving his intent.
Handover Checklist
All Department Engagement will be performed by Support Clerks. If this cannot be done, the Chain of Command will be utilised as follows, in addition to resolving any escalations from a Support Clerk as necessary:
DEVCOM Support Clerk DEVCOM Lead Support Clerk DEVCOM 2iC DEVCOM 1iC R&DC Commander
All Department Engagements will include the 1iC and 2iC of the supporting Department (S1, S2 etc..)
The following Handover Checklist will be planned in a Forum Post:
| Unit | Action | Details |
|---|---|---|
| RDC Commander & ACD | Integration Kick Off meeting | The DEVCOM 1iC will notify the RDC Commander and ACD that the game is ready to prepare for Handover and review this checklist/plan with the DEVCOM Lead. |
| DEVCOM Lead | Role Decision | The DEVCOM Lead shall decide at this point whether they intend to stay with the game or return to DEVCOM to pursue another Game launch. |
| S1 | Notification of game handover in Coordination PM | The S1 team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| S2 | Notification of game handover in Coordination PM | The S2 team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| S3 | Notification of game handover in Coordination PM | The S3 team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| S5 | Notification of game handover in Coordination PM | The S5 team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| S6 | Notification of game handover in Coordination PM | The S6 team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| S7 | Notification of game handover in Coordination PM | The S7 team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| RRD | Notification of game handover in Coordination PM | The RRD team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| RTC | Notification of game handover in Coordination PM | The RTC team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| NCOA | Notification of game handover in Coordination PM | The NCOA team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| ODS | Notification of game handover in Coordination PM | The ODS team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| WAG | Notification of game handover in Coordination PM | The WAG team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| MP | Notification of game handover in Coordination PM | The MP team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| ACD | Notification of game handover in Coordination PM | The ACD HQ team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| SECOPS | Notification of game handover in Coordination PM | The SECOPS HQ team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| ROO | Notification of game handover in Coordination PM | The ROO HQ team will be informed of the new destination unit designation into ACD to update their records as appropriate. |
| ACD | Leadership Selection Discussion | The DEVCOM Lead will prepare a recommendation for leadership when the game transfers to ACD. This shall include pros, cons and recruitment numbers for each candidate for each position. The discussion shall be centred around what is best for the Cav and attended by the RDC Commander, DEVCOM 1iC or delegate, Lead Support Coordinator or delegate and DEVCOM Lead. |
| ACD | Transfers-Out Notification | The DEVCOM Lead shall prepare a full and complete transfer recommendation in the style of a transfer post, incorporating the outcomes of the Leadership discussion with ACD. The draft transfer orders shall be sent to the ACD HQ team for review. |
| Discord Team | New channels & roles (if needed) | The DEVCOM Lead Support Coordinator, 2iC or 1iC will communicate using a Discord Request ticket on the Discord app to initiate new roles, permissions and channels as required. |
| S6 | New forums & roles (if needed) | If the ACD forums experience technical issues or require amendment / expansion, then the DEVCOM Lead shall submit a S6 Ticket on the website clearly articulating what the desired state and current state are, so that S6 can easily comprehend what must be done to amend the forums. |
| WAG | Game Handover – Front-page | The Lead Support Coordinator (or delegate) shall submit a ticket to WAG to change the front-page of the Wiki to show a new supported game being handed over to ACD indicating the unit designation, providing an image as required, and any public server information to be included as required. |
| WAG | Game Handover – DEVCOM page | The Lead Support Coordinator (or delegate) shall submit a ticket to WAG to change the DEVCOM-page of the Wiki to show that the supported game has been transferred to ACD. |
| WAG | Game Handover – ACD page | The Lead Support Coordinator (or delegate) shall submit a ticket to WAG to change the ACD-page of the Wiki to show that the supported game has been transferred from DEVCOM, providing an image as required and the unit designation that the game has been attributed to. |
| DEVCOM | Public Announcement – Handover | 24 hours after instructing WAG to change the Wiki and the Transfer post is agreed with ACD, the DEVCOM 1iC or 2iC will post in Public Announcements that a game has been handed over for Official Support to ACD. |
| DEVCOM | Transfers Start | The DEVCOM 2iC or 1iC shall inform the Regiment when all planned transfers-out have commenced. |
| ACD | Transfers Complete notification | The DEVCOM 2iC or 1iC shall inform the ACD when all planned transfers-out have been completed to signal the end of any disruption. |
Plan submission, review and approval
The DEVCOM Lead will submit the Handover Plan (with dates for when each event is required) for the approval of the DEVCOM Lead Support Coordinator, 2iC and 1iC, as well as the RDC Commander and ACD HQ. The DEVCOM 1iC shall ensure that no work commences until the plan is agreed with RDC Commander and ACD HQ. The DEVCOM Lead will allow 72 hours for review and approval of the plan before the first date of action is required. This ensures that the reviewers are aware of their responsibilities to support the plan before it is enacted. The DEVCOM Lead may submit this plan after reaching 35 troopers. Approval will not be given unless there are 40 troopers in the unit excluding the DEVCOM Lead. The DEVCOM 1iC, 2iC or Lead Support Coordinator, as well as RDC Commander and ACD HQ may request changes prior to approval as required. They may delegate their review and approval if on LOA and their responsibilities must be covered in their absence where indicated in the plan.
Conclusion
This DEVCOM DEVCOM to ACD Handover Process serves as a descriptive guide to the last DEVCOM scope of work, to hand over a mature game to ACD to continue it’s development as a Line Unit company, and the sixth key event in game development in the 7th Cavalry Gaming Regiment.