Need CDL

The Need CDL callout rule ensures that selected crews have someone with a commercial driver license. This rule uses the NeedCDL roster preference and the CDL Required callout attribute. When the callout attribute is enabled along with the roster preference, ARCOS will only call employees with a CDL in roster until an employee with a CDL accepts.  

Note: The Require CDL callout attribute is designed to work with the Serial Calling callout attribute. This means ARCOS will call the first sub-callout and not call the next sub-callout until the required number of employees has accepted from the first sub-callout or some other intervention has occurred on the first sub-callout.

In the instance a CDL required callout is initiated to a roster that does not have the NeedCDL preference enabled, ARCOS will call the roster in its original order because the CDL logic requires both the roster preference and the callout attribute. If however, a CDL callout is initiated to a Non CDL roster, and there is an accept by an employee that has a CDL, the callout will recognize the CDL even though the roster does not have the NeedCDL preference enabled.

In order for the callout to recognize employees as having their CDL, the employees must be designated as having a CDL in ARCOS. This is accomplished by adding Extended Employee Attributes. Creating an Extended Employee Attribute, called CDL, setting the type of the attribute to Checkbox, and assigning that Extended Employee Attribute to an employee, will designate the employee as having a CDL.

The CDL functionality exists so that employees with the CDL Extended Attribute will be contacted first, regardless of position on the roster. Employees without a CDL Extended Attribute will be skipped, until an employee with a CDL accepts the callout. Once the CDL requirement has been met, all non-CDL employees will be contacted in roster order, until the number requested has been filled. If there are more CDL employees on the roster, we will call them if we did not call them during the CDL only portion of the callout, when we reach them on the roster.

Note: CDL logic is applied to a sub-callout based on the first sequence's setting. Meaning, if the first sequence has the Need CDL option enabled, then the CDL logic will be applied to the entire chained list. If the first sequence does not have the Need CDL option enabled, the CDL logic will not be applied to any sequence within the chained list, event if a subsequent chain has it enabled.

Callout Examples

Example 1:

First sequence - The NeedCDL roster preference is enabled

Callout requesting four employees

Employee	Has CDL?
Adam Miller	No
Bill Smith	No
Charles Jones	Yes
Doug Johnson	Yes
Edward Thompson	No
Frank White	No
George Barnes	Yes

Once the callout was initiated, Adam Miller and Bill Smith would be skipped, due to not having a CDL. The first employee called would be Charles Jones. Charles declines and Doug Johnson is called. He accepts. ARCOS moves to the first skipped employee, Adam Miller. Adam is not home. ARCOS calls Bill Smith. Bill declines. ARCOS moves to Edward Thompson. Edward accepts. The callout moves to Done status. Had Edward declined, the next employees called would be Frank White then George Barnes.

Example 2:

First sequence - The NeedCDL roster preference is enabled

Second sequence - The NeedCDL roster preference is not enabled

Callout requesting four employees

Employee	Has CDL?
Adam Miller	No
Bill Smith	No
Charles Jones	Yes
Doug Johnson	Yes
Edward Thompson	No
Frank White	No
George Barnes	No
Chained Roster
Joe Smith	No
John White	Yes
Alex Wilson	No
Katie Williams	Yes

Once the callout is initiated, Adam Miller and Bill Smith will be skipped, due to not having a CDL. Charles Jones is the first employee called. Charles declines. Doug Johnson will be called next. Doug declines. Edward Thompson and Frank White will be skipped. George is called next and he is not home. Joe Smith will be skipped. John White is called next and he accepts. ARCOS then goes back to the skipped employees and since there are three positions still open, ARCOS will call three employees at a time, Adam Miller, Bill Smith and Edward Thompson will be called at the same time. Adam and Bill accept, Edward declines. ARCOS will move on to Frank White. Frank declines. Next will be Joe Smith. Joe is not home. ARCOS moves to Alex Wilson. Alex does not answer. ARCOS then calls Katie Williams, who accepts. The callout is filled and goes to Done status.

Example 3:

First sub-callout - The NeedCDL roster preference is enabled

Callout requesting two employees

Employee	Has CDL?
Adam Miller	No
Bill Smith	No
Charles Jones	Yes
Doug Johnson	Yes
Edward Thompson	No

Second sub-callout - The NeedCDL roster preference is enabled

Callout requesting two employees

Employee	Has CDL?
Joe Smith	No
John White	Yes
Alex Wilson	No
Katie Williams	Yes

Once the callout is initiated, the second sub-callout, Line Worker, will go into Hold status. ARCOS will begin with the first sub-callout, Adam Miller and Bill Smith will be skipped, due to not having a CDL. Charles Jones will be called. Charles accepts and ARCOS will return to the skipped employees. Adam Miller is called and he accepts. The first sub-callout is filled and it will go to Done status.

The second sub-callout will go into Running status and begin making calls. Since the CDL requirement for the callout has been filled, ARCOS will call the employees in roster order. Since two is requested for this sub-callout, Joe Smith and John White will be called at the same time. Both employees accept, the sub-callout goes to Done status, moving the Callout to Done status.

---

*Note: Not all companies have all of the items described in the Online Help.

*Please note, the ARCOS online documentation is a living document that is always under review. If you see information that is inconsistent with the behavior in the application, or you do not see a page covering an ARCOS feature you would like to know more about, please contact the ARCOS Support Center.