On-Call Scheduling with overlapping schedules
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-01-2016 08:12 AM
How do you create overlapping schedules for the same group?
The Service Desk group has several shifts. 6:30am-3:30pm, 7am-4pm, 7:30am-4:30pm, etc. but the On-Call Scheduling wizard does not allow for overlapping schedules.
How do you accommodate for this? Seems like a basic feature of scheduling so I must be missing something. I've searched several threads on here, but no luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2017 04:13 AM
I had same question some time back and was struggling to create On-call Calendar since we had many overlapping shifts.
System definitely does not allow overlapping shifts out of the box.
We implemented a workaround where our on-Call shifts are different as compared to actual working shift. On-Call shifts are 'non-overlapping' and members in these shifts are adjusted in such a way that it roughly maps to members in actual working shifts.
For example we had five overlapping shifts as:
Shifts (EST) |
11:30 AM - 8:30 PM |
8:00 AM - 5:00 PM |
5:00 AM - 2:00 PM |
7:00 AM - 4:00 PM |
3:30 AM - 12:30 PM |
1:00 AM - 10:00 AM |
We identified which of these are primary or Important shifts. Then created three on-call shifts which maps to these primary shifts.
On-Call Shift | Working Shifts (Mapped) |
1 AM - 8AM | 1:00 AM - 10:00 AM |
8AM - 3PM | 8:00 AM - 5:00 PM |
3PM - 9PM | 11:30 AM - 8:30 PM |
Though this is not exactly what we wanted. But serves our purpose well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-07-2017 07:11 AM
I hate to add to the "No Answer"...but:
Avoid schedule overlaps wherever possible !
If you ever try to scale up to a process of "Human Resource Predictive Analytics", you will have issues determining resource availability per hour when using rota's and rosters as "Shift Schedules"....
make a rule now: shift schedules represent the dates and times that users are available to RECEIVE new work...
That definition will help the business understand why schedule overlaps are a bad idea (yes, hand-off times are required between shifts, but no...the schedules do not have to represent those times). After having a conversation with the business, they begin to understand that you may not want to have the "off-going" resource accepting new work and instead have the "on-coming" resource accept it...