Policy: ORBAT Slot Allocation - Administration - United Task Force (UNITAF) Arma 3


P15-145 Policy: ORBAT Slot Allocation

UNITAF / Arma 3 / Administration Procedures



Version 1 / 9min read / Updated Tue 02 Mar 2021 / 275 views


Philosophy 

Our dynamic ORBAT system is one of the hallmarks of UNITAF and this section serves to communicate the current policies surrounding slot allocation. The purpose of the dynamic ORBAT system is to ultimately fill all ORBATs with the most experienced and capable person available. It is primarily first come first serve, but the purpose of this policy is that slot allocation must always be fair and transparent and various nuances within the system are communicated here, as well as some future plans. It is designed as a reference for field leaders and to clarify current policy around slot allocation.

 

Minimum and Maximum Rank Restrictions

At a global level, an ORBAT can be set to have both a minimum and maximum rank if desired. All combat operations by default have a minimum rank of Recruit, this is to ensure that all those attending have been through Recruit Core Infantry Training and that they have a basic understanding of our SOP. The only exception to this is Recruit Core Infantry Training itself, which has a minimum rank of Candidate.

Minimum Rank operations are typically special forces operations, and are typically PFC+ or Cpl+ (Otherwise known as NCO or ORGCOC operations) although it's worth noting that any rank can be applied. The purpose of minimum rank operations is to provide an experience for more seasoned members of UNITAF and in the case of ORGCOC operations, typically to build relations between members of the ORGCOC where they are not usually able to deploy together. 

Maximum rank operations work the same way as minimum rank operations, but are typically used to tailor operations to less seasoned members within UNITAF, such as "Recruit Operations", such operations offer less competition for slot allocation and therefore allow newer members to try out slots that are usually taken before they are able to access them. A limited number of senior members, typically of the ORGCOC will always attend such operations, which is also a good opportunity to meet newer members.

It's common, although not essential to remove these restrictions after some time after the intial release to fill an ORBAT, if needed. ORBATs with rank restrictions are always at the discretion of the command staff and are approved on a case-by-case basis, as the majority of operations should have no such restrictions.

 

Tiers and up-tiering

On release of an ORBAT only those with an equal tier to the role in question will be able to acquire the slot, a 24 hour window from release is given for anyone holding the required tier to acquire the slot. Should nobody do so, 24 hours after release the automatic up-tiering process begins.

  • 24 hours after release, anyone with 1 tier below the required tier of any vacant slot can acquire it, known as a 1UP
  • 48 hours after release, 24 hours after 1UP anyone with 2 tiers below the required tier of any vacant slot can acquire it, known as a 2UP

 

Exceptions

There are a number of limitations to the up-tiering system, which are noted below;

  • It is only possible to up-tier a maximum of 2 tiers (2UP)
  • You cannot up-tier in a combat area if you have no practice hours in that area
  • If you have acquired a valid policy violation in the past 7 days ("reprimand") then you will be barred from up-tiering for that 7 day period - see below section "Restrictions" for more information.
  • If you have acquired an active procedure correction flag ("flagged") then you will be barred from up-tiering for the duration it is active - see below section "Restrictions" for more information.

In any case, the system will always tell you why you cannot acquire a slot and will state the reason in a tooltip when the cursor is hovered over it.

 

Restrictions

Since up-tiering is a privilege, a number of actions can cause access to it to be restricted those are;

  • Reprimands are reports submitted by members of the ORGCOC when someone violates a unit policy, this could be anything from no-showing an operation to breaking any of UNITAFs policies or code of conduct items. If you receive a Reprimand your Chain of Command will inform you and so long as it is a valid report, you'll not be able to use the up-tiering system from 7 days of the date in which it was raised. You'll know if this is the case, since on the ORBAT it will state the reason for up-tiering being disabled. If you need to query this, speak to your chain of command.
     
  • Procedure Correction Flags are markers placed by members of the ORGCOC when someone is observed to not be following correct procedures for any given combat area, they are not time limited and remain as active markers until removed. If you have a marker, it will be a specific SOP that is marked (or multiple) and any role or role area that the SOP is attached to will not be accessible through up-tiering to you until the flag is removed. Flags are removed once it is deemed that the target of the marker fully understands (and/or can demonstrate) an understanding or application of those procedures.

 

Locked Slots

It is possible for field leaders to 'lock' slots on an ORBAT, if a slot is locked it is denoted by a greyed out slot and an absent deployment button replaced by the message "Contact Field Leader". Locked slots should be used sparingly and only be used in a number of circumstances;

  • For mission critical roles in which the field leader deems the person needs to be vetted prior to slot allocation, typical examples are specific role play characters, or complicated piloting slots or aircraft
     
  • For missions where the ORBAT is deemed that it may not fill, and a number of roles are locked to funnel slot allocation across multiple teams, before unlocking additional slots.

In any case, locked slots filled by manual allocation must follow manual allocation guidelines.

 

Pre-slotting

Pre-slotting is a muster period that occurs after ORBAT creation and before ORBAT release. The pre-slotting stage is typically 24 hours before release. During the pre-slotting stage members of the ORGCOC (NCO+) are able to slot ahead of general release - however pre-slotting is restricted to the following roles or role areas;

  • Field Leadership Roles
  • Mission Support Roles

There are a number of reasons for this, firstly members of the ORGCOC have a leadership quota as part of UNITAFs aim to have the majority of field leaders also as members of the ORGCOC. During the preslotting phase, the assigned field leader and mission developers or campaign team, also slot to ensure they are allocated before general release. No other roles are possible to be pre-slotted before general release, and pre-slotting is a self served process - except as outlined in the 'Manual Allocation' section.

 

Manual Allocation

In addition to all of the above,  senior officers have access to a manual allocation tool this is the only method by which someone can be slotted without doing it personally via the ORBAT and therefore is the only technical method by which someone can bypass any requirement. Manual allocation can be used in a limited number of circumstances, as outlined below;

  • leaders and game-masters who have planned the mission; such as the field leader and mission developers
  • any agreed leadership assignments, typically where an agreement has been made that such persons will take those positions for that operation
  • any person in the pre-slotting approved role areas who is unable to slot themselves in the pre-slotting window
  • in some circumstance a junior leader with an experienced supporting leader, or visa-versa, whereby the supporting leader could be in roles such as AR 2IC (Fireteam), Squad Medic (Squad) or Platoon Sergeant / Platoon Medic (Platoon) depending on the circumstances. In any case, these allocations should be limited to 1 pair per ORBAT.

In any case, manual allocation is for certain circumstances, and outside of ORGCOC members in Field Leadership roles, and all members in mission support roles, should generally follow all normal procedures, meaning;

  • no manual assignment of persons not meeting minimum or maximum rank requirements
  • no manual assignment of persons with reprimands within the last 7 days
  • no manual assignment of persons with active flags in the assigned combat area
  • no manual assignment of non pre-slotting combat areas where the user doesn't have the required tier;
    • except when;
      • manually assigning a 1UP within a valid 1UP window
      • manually assigning a 2UP within a valid 2UP window
      • assigning a slot which has not been filled after ORBAT lock (or within 24 hours of deployment execution)
      • changing a role for METT-TC purposes after ORBAT lock

Finally, in the case that nobody in the active force has the requirements for a slot, then the next most experienced person can be manually assigned (operation+practice hours), should they not pursue the slot, this process can be repeated until filled - in this case there is no need to await the 1UP or 2UP windows.

 

Slot priority in manual allocation

When manually allocating slots, priority should be given to those with the most official requirements - taking into account all other factors of this policy.

 

Future Plans

As communicated in recent SITREPs, the dynamic ORBAT system is expected to receive a number of substantial changes, all of which are designed around making the system fairer still. The tier system will remain the primary method of allocation, and changes will focus on balancing having the most experienced members in a role, while giving an opportunity to new members to access the first rung of the ladder. Some of the notable planned changes are;

  • a movement away from fixed up-tiering and deployment times towards dynamic release times, this will see each person having slightly different access times for roles based on a number of factors such as;
    • how frequently they have recently acquired a slot of the same type or area
    • how many deployments they have attended in the prior 30 day period
    • the players reputation
  • alternate access methods, such as;
    • capability based access, such as a test or course that grants access to a role or set of roles, but still using tiers to allocate in sequence of most experienced
    • 'L' plate or 'learner plate' slots, designated slots that can be used on an orbat sparingly, that prevent an experienced member from accessing them, and allow an inexperience person to try out for that role.

 

Summary

We will communicate updates to this vital policy regularly, but this policy serves as the central authority for slot allocation, and supersedes all previous SITREPs which communicate changes to this system. If you have any questions about this policy, please use j6-training-and-sop.



REFERENCES:
UNITAF Standard Operating procedures (SOP)
are adapted primarly from US Army Training and Doctrine Command (TRADOC). Our written and audio procedures are a combination of the following primary source materials, as well as our own learnings, modifications and adaptations:
- US Army Techniques Publication, Infantry Platoon and Squad (ATP 3-21.8)
- Soldier’s Manual of Common Tasks Warrior Leader Skills Level 2, 3, and 4 (STP 21-24-SMCT)
- The Warrior Ethos and Soldier Combat Skills (FM 3-21.75 / FM 21-75)
- Leadership Development (FM 6-22)
- Dyslexi's Tactics, Techniques, & Procedures for Arma 3 (TTP3)




Some aspects of this website are fictional. United Task Force is an online gaming organisation that simulates real-world military operations using Arma 3, a sandbox PC game and custom software. Any usage herein of logos, representations of nations or military organisations is done for the sole purpose of historical representation and under fair use.

The UTFN software, utfn.net and unitedtaskforce.net is the sole intellectual property of United Task Force (UNITAF) and it's IP rights holders, All rights are reserved. ©2019-2021