How do other OFS implementations handle 'On-Call' Shifts that cross midnight?

Summary:

We're curious how other Users of OFS have setup their 24/7 operations. The way we work is functional, but understanding other implementations might help refine and improve it. I'll try and express the 2 methods we've tried during our experience of OFS to date, but i'd like to understand how other customers are doing it to see if we can find a solution that handles both SLA and Service Window driven activities without negatively impacting the user experience.

To support our 24/7 operations we currently have our 'on-call' shifts setup as follows:

The 'on-call' shift starts directly after the 'regular' shift, crosses midnight and ends at 08:30 (Configuration is setup to not lock the activities until after this time). To work around the OFS limitation where a Resource needs to deactivate their 'regular' shift and activate their 'on-call' shift, there is a routing plan capable of scheduling reactive faults during the 'on-call' time by using a combination of Resource Filters and very high 'Overtime' configuration.