Settings
These settings affect the way that schedule compliance rules operate.
| Setting | Description | Rules Affected |
|---|---|---|
| Hour | Unless otherwise specified, the hour rule setting requires
you to input a decimal value. Some standard decimal values:
|
ALL unless otherwise specified |
| Day | The day setting starts at midnight (00:00:00) and ends at
23:59:59. All shift hours count against the day when the shift started. For example, if the user adds a morning shift on Monday that starts at 1:00 am and ends at 9:00 am, this shift logically belongs to Tuesday because it starts after midnight (the start of the next day). Note: In general, daily and aggregate rule compliance calculations
are performed based on the day.
|
ALL |
| Week | The week setting determines the first day of the schedule
week (7 day period, not schedule period). The schedule week starts on this day,
not necessarily at the beginning of the calendar week. Depending on the module you use to create your schedule, there are two ways to define the start of the week. LFSO The start day for the schedule week is defined for each LFSO location: MVS and RTSS, Staff Scheduler, Time and Attendance MVS and RTSS uses the schedule period start date for the team. This is the maintenance form location where you define schedule periods: This is the maintenance form location where you assign teams to schedule periods: Shift Trades The start day for the schedule week is defined globally in this registry parameter:
|
WEEKLY |
| Shift | Shifts are a group of shift details to clearly establish
when a shift begins and ends. Shifts are defined based on the scheduling module
you use: LFSO, MVS, RTSS, or Time and Attendance. Schedule Compliance does not define shifts, but instead uses the shift definition determined by the scheduling module used to generate the schedule. |
ALL SHIFT |
| Schedule Period | The typical schedule period is 7 days, 10 days, or 14
days. Each business has a schedule period that suits their unique business
needs. Staff Scheduler and Time & Attendance These scheduling modules do not use a schedule period. MVS and RTSS Schedule period is defined in schedule settings and then associated to each team, thereby allowing for different teams to have different schedule periods. For example, Team A has a weekly schedule period and Team B has a 4-week schedule period. Schedule periods can be inherited to sub-teams. The correct schedule period is retrieved when MVS is accessed. This is the maintenance form location where you define schedule periods: This is the maintenance form location where you assign teams to one specific schedule period: LFSO LFSO does not explicitly use schedule period definitions. The length of the generated LFSO schedule is considered as the schedule period. |
ALL |