Inheritance rules for shift constraints
When creating shift Work period in WFM that has a definite length. collections and setting shift constraints Feature in WFM that assists in limiting the number of shifts scheduled for each day for an organization during a specific date range for all of the shifts in a shift collection., there are different parent-child org inheritance rules.
Inheritance rules when creating Shift Collections
Child organizations inherit the shift collections defined for the parent organization. When assigning shifts to a collection Group of back-office Contributions from one or more employees connected to a single customer or account captured by DPA. Collections are used for analyzing and improving back-office efficiency and quality. for a child organization, the available shifts include all shifts associated with the parent and child organizations.
Inheritance rules when setting shift constraints
When setting shift constraints, there are no parent-child org inheritance values. Each organization has separate and independent shift constraints.
For example, the shift constraint for the UK parent organization is set to 90, while its child organizations have different constraints. The constraints set for the child organizations do not roll up to the parent organization.
|
Parent or Child |
Organization |
Constraints |
|---|---|---|
|
Parent |
UK |
90 |
|
Child |
Scotland |
40 |
|
Child |
England |
60 |
|
Child |
Wales |
70 |
On the other hand, the number of scheduled shifts for each shift collection Group of shifts in WFM used to control costs or resources around specific shifts. Typically, the shifts in a shift collection are related in some way, such as a group of night shifts or delivery shifts. rolls up from the child to the parent organization.
For example, the UK parent organization has 60 scheduled shifts, which is the sum of all of the scheduled shifts in its child organizations (20 + 20 + 20).
|
Parent or Child |
Organization |
Shift Count |
|---|---|---|
|
Parent |
UK |
60 |
|
Child |
Scotland |
20 |
|
Child |
England |
20 |
|
Child |
Wales |
20 |
Example: Parent Constraint Exceeded Due to Child Shift Counts
While the number of scheduled shifts for a child organization might not exceed the shift constraint for the child, it might result in exceeding the constraint set for the parent organization.
In the following example, the constraints have been set so that the number of scheduled shifts for each child organization should not exceed 25. The number of scheduled shifts for each child org is 20, so the shift count for each child org has not broken the constraint.
The constraint for the parent org is 50. As the number of scheduled shifts for the child organizations roll up to the parent, the shift count for the parent org is 60, which breaks the constraint of 50 for the parent organization.
|
Parent or Child |
Organization |
Constraints |
Shift Count |
|---|---|---|---|
|
Parent |
UK |
50 |
60 |
|
Child |
Scotland |
25 |
20 |
|
Child |
England |
25 |
20 |
|
Child |
Wales |
25 |
20 |
To prevent the shift count from exceeding the constraint for the parent organization, do one of the following:
-
Remove the right number of scheduled shifts from the child organizations.
-
Set the constraint on the parent organization to be higher.