Row versions for template and rotation rows

Master Rotation (MR) rotation rows and One-time Schedule (OTS) template rows are used as templates to create schedules. After the MR or OTS template is activated, changes to the schedule template are performed by creating new versions of schedule rows.

New row versions can be created to change the shifts and labor metrics on the row. Row versions are created with a DRAFT status. Each row version has an effective date range that is specified during creation. Row versions are activated to apply the new shifts and labor metrics to the schedule. During the effective date range of the activated row version, the row's existing schedule is replaced with the shifts and labor metrics in the activated row version. The status of the row version is changed from DRAFT to ACTIVE.

When they are activated, row versions are given a version number that is one higher than the last row version that was activated on the row. The schedule on a given day is determined by the row version with the highest version number that is effective on that day. Therefore, shifts and labor metrics for the day are provided by the row version that was activated most recently. The order in which the row versions were created does not effect the final schedule.

Here is an example of a schedule created from multiple row versions. Susan is scheduled using an MR with a seven-day rotation with DAY shifts on each working day. The start date of the MR is January 1, 2018. Her assignment is permanent, so the system maximum date (January 1, 3000 by default) is used as the end date. This is used as the original version 1 of her schedule row.

After the MR was created, Susan's rotation was updated because one of her coworkers resigned. Susan was assigned to cover NIGHT shifts until a replacement could be hired, and she was assigned to train the replacement. The scheduler asked Susan if she wanted to cover the night shift indefinitely, but she declined.

This table lists the row versions created by the scheduler to respond to the changes in Susan's unit:

Row version Effective Dates Shifts Description Status
1 1/1/20181/1/3000 DAY Original rotation row ACTIVE
2 2/1/201802/28/2018 NIGHT Covering night shift for coworker who resigned ACTIVE
3 2/21/20183/7/2018 TRAIN Training new staff member ACTIVE
2/1/20181/1/3000 NIGHT Proposed permanent night shift schedule DRAFT
MR rotation row versions example

When the schedule is generated, Susan's schedule looks like this:

MR example of generated schedule
Dates Shifts Source version
1/1/20181/31/2018 DAY V1 original rotation row
2/1/20182/20/2018 NIGHT V2
2/21/20183/7/2018 TRAIN V3, which supersedes row V2
3/8/2018–1/1/3000 DAY V1 original rotation row

The row version that is in DRAFT status does not affect the schedule.