Shifts

The Shifts view defines the shifts available to be worked, and associated attributes. The optimiser will select from these for each day and worker to create the roster as well as providing the manual options that can be selected. They also are used to define the targets, requests, and availability.

Shift types:

O - the “Rostered Off” shift. This is the default chosen for when a worker is not rostered on for that day.
Leave - these are costed, but do not count as work. They are not set as optimisable since they are not to be chosen, but are set/negotiated by the worker.
Normal worked shifts. These are to be chosen by the optimiser to meet the various staffing targets
Un-optimised worked shifts.

Attributes that can be set for each shift are:

Code - the master identifier for each shift. Used throughout the application.

Do not use a plain number as a shift code (e.g. “9”). Something like “3C” is acceptable.

Group - for grouping shifts if appropriate (eg weekday and weekend shifts). This is for defining targets. If not required for a shift, then it is recommended to define the group as a group of one with the same name as the single shift.
Worked - this shift is actually worked
Costed - this shift is counted towards the reported cost for the roster

An example of a shift worked but not costed would be an employee working a shift in another department.

Optimised - this shift can be chosen by the optimiser.
Leave - this shift is costed, but does not count as work
Category -
Start Time - time the shift starts
End Time - time the shift ends
Break - break time for the shift
Competency - used in reporting