A roster is a list of employees and is defined by a location, a classification , and a list status .
Primary Class
A Primary Class is an employee's job title or skill associated with a roster. An employee can have only one primary job classification; however, he can be on rosters for other job classifications as well as other workgroups. ARCOS automatically configures rosters for each defined Job Classification.
List Status
Each roster is a list of employees defined by Location and Classification or Workgroup. Some companies have an additional component for the roster definition which is "List Status." Some examples of list statuses are Regular, Preferred, Non-Preferred, Standby, Temporarily Assigned (TA), Ask-On, and Ask-Off. Several of these list status types are used in conjunction with chaining.
There are three types of roster lists: Primary Classification (Primary Class or Job Class), Workgroup , and Storm Role .
Workgroup
A roster that is manually built by the ARCOS user by adding employees based on some criteria of the company, union agreement, or user. The user can add and remove employees from the roster whenever necessary. The callout order of the roster may be based on overtime, seniority, or a manual ordering by the user. The primary classification of the employee does not matter and the list is not auto-populated in a workgroup unless SuperClass Configuration is used.
Storm Roles
Storm Roles are a secondary job skill that can be assigned to employees and used for storm modes. On the List Maintenance page for a Storm Role list, employee's last trained dates can be tracked.
Rosters are established in ARCOS to function according to specific business rules, such as list ordering, employee rotation, schedule exceptions, etc. Every roster in the system has a set of preferences associated with it that are controlled on the Roster List Ordering Admin page.
When employees are set up in ARCOS, they are assigned to a primary class, i.e. lineman, senior lineman, crane operator. Primary Classification Roster Lists automatically include all employees with that Primary Class. Workgroup Roster Lists allow you to manually choose the employees to be included in the list regardless of the Primary Class to which they are assigned. Workgroup lists are built manually by adding employees based on some criteria of the user's choice and can contain either one or several job classifications. Not all employees in Primary Class Roster Lists are assigned to a Workgroup, but all employees in Workgroups belong to a Primary Class.
The following table provides a description of the functions associated with each button on the List Mnt tab. Not all companies use all of the features discussed below.
Button |
Description |
Allows employees to be assigned to a Major Event by either Primary Class or by Location. Once an employee is assigned to a Major Event they will be placed on Working Major Event status and will be synced RoD via the WSI.
RoDStands for Resources on Demand which is a third-party application from MacroSoft™ that provides web-enabled emergency resource management for utility companies. RoD manages resource requests, tracks personnel movements, and supports logistics during a large-scale restoration event.
WSIStands for Web Services Interface which is an interface (or translator) between two applications. Web services can be setup in ARCOS to communicate with a company's internal system such as RoD. |
|
Allows users to lookup callouts by their Callout ID and make changes to employees' responses. For example, change an Accept to a Decline because the employee was unable to come in and preform the work. |
|
Allows hours to be entered manually for employees on a daily bases. Hours that are entered will not appear on a list until the next list is in effect. The default time span for each day is midnight to midnight, unless your company specifies a different range. |
|
Provides access to edit overtime hours for employees on a cumulative weekly basis for the user's current Level 4 location. |
|
OT - Employee Overtime Entry |
Allows OT hours to be modified per an employee and pay period basis. Hours worked/refused are applied per callout basis. |
Allows new OT hours to be applied per pay period to a location. Hours are applied to the lists that have an effective date prior to the pay period start date. |
|
Allows similar (same start time, paycode, etc.) OT hours to be saved for multiple employees at the same time. |
|
Allows pointers to be reset for multiple list within the same location at one time. |
|
The Roster List Ordering screen provides configuration options in order for the roster to function according to specific business rules such as list sorting methods, rotation, chains, call methods, On/Off Call status, etc. |
|
Allows the user to search multiple locations to view selected rosters by their list status. The generated report is what the user would see if they clicked the view button on the Roster List Ordering page. |
|
Allows sign-on and sign-off preferences to be changed for the Linemen Underground list. |
Comments
0 comments
Please sign in to leave a comment.