Follow the sun (2 locations)
Demonstrates a schedule balancing two 12-hour shifts between a UK and US west coast pair of teams.
This schedule configuration enables each team to have the majority of their on-call hours within typical day/waking hours. It involves 3 separate schedules, one for each of the local teams and a third schedule which is then used to co-ordinate and join the local schedules together.
Main Schedule Shift Configuration Entries
The main schedule is configured in the America/Los_Angeles time zone and uses a simple shift configuration pattern that rotates between a nested schedule for each team at the appropriate time each day.
| Day: | Hour: | Minute: | Primary: | Secondary: |
|---|---|---|---|---|
| Weekdays | 10 | 00 | sfo-team | [Not assigned] |
| Weekdays | 22 | 00 | lon-team | [Not assigned] |
Sample shifts
2023-07-24 10:00 sfo-team
2023-07-24 22:00 lon-team
2023-07-25 10:00 sfo-team
2023-07-25 22:00 lon-team
2023-07-26 10:00 sfo-team
2023-07-26 22:00 lon-team
2023-07-27 10:00 sfo-team
2023-07-27 22:00 lon-team
2023-07-28 10:00 sfo-team
2023-07-28 22:00 lon-team
2023-07-31 10:00 sfo-team
London Team Shift Configuration Entries
The London team’s schedule is configured in the GMT time zone and the team has chosen to schedule themselves using a 4 day/3 day split across the week.
| Day: | Hour: | Minute: | Primary: | Secondary: |
|---|---|---|---|---|
| Mon | 06 | 00 | BEST_MEMBER | [Not assigned] |
| Fri | 06 | 00 | BEST_MEMBER | [Not assigned] |
The 06:00 UTC shift start time is selected to match the 22:00 America/Los_Angeles shift start time in the main schedule.
Sample shifts
2023-07-24 06:00 london-member1@example.com # Mon
2023-07-28 06:00 london-member3@example.com # Fri
2023-07-31 06:00 london-member2@example.com # Mon
2023-08-04 06:00 london-member4@example.com # Fri
2023-08-07 06:00 london-member3@example.com # Mon
2023-08-11 06:00 london-member1@example.com # Fri
2023-08-14 06:00 london-member4@example.com # Mon
2023-08-18 06:00 london-member2@example.com # Fri
US Team
The US team uses a simple daily rotation (specifically the Simple Daily Rotation example ).
Sample shifts
2023-07-24 10:00 member2@example.com # Mon
2023-07-25 10:00 member1@example.com # Tue
2023-07-26 10:00 member3@example.com # Wed
2023-07-27 10:00 member4@example.com # Thu
2023-07-28 10:00 member3@example.com # Fri
2023-07-29 10:00 member4@example.com # Sat
2023-07-30 10:00 member1@example.com # Sun
2023-07-31 10:00 member2@example.com # Mon
Fully Rendered Schedule
When viewed in the On-Call Optimizer web UI, or exported to an on-call products the “fully rendered” schedule combining combining all of the above configuration will result in the following shifts:
# Rendered in UTC
2023-07-24 05:00 london-member1@example.com # Mon 6am LON / 10pm Sun SFO
2023-07-24 17:00 member2@example.com # Mon 6pm LON / 10am Mon SFO
2023-07-25 05:00 london-member1@example.com # Tue 6am LON / 10pm Mon SFO
2023-07-25 17:00 member1@example.com # Tue 6pm LON / 10am Tue SFO
2023-07-26 05:00 london-member1@example.com # Wed 6am LON / 10pm Tue SFO
2023-07-26 17:00 member3@example.com # Wed 6pm LON / 10am Wed SFO
2023-07-27 05:00 london-member1@example.com # Thu 6am LON / 10pm Wed SFO
2023-07-27 17:00 member4@example.com # Thu 6pm LON / 10am Thu SFO
2023-07-28 05:00 london-member3@example.com # Fri 6am LON / 10pm Thu SFO
2023-07-28 17:00 member3@example.com # Fri 6pm LON / 10am Fri SFO
2023-07-29 05:00 london-member3@example.com # Sat 6am LON / 10pm Fri SFO
2023-07-29 17:00 member4@example.com # Sat 6pm LON / 10am Sat SFO
2023-07-30 05:00 london-member3@example.com # Sun 6am LON / 10pm Sat SFO
2023-07-30 17:00 member1@example.com # Sun 6pm LON / 10am Sun SFO
2023-07-31 05:00 london-member2@example.com # Mon 6am LON / 10pm Sun SFO
2023-07-31 17:00 member2@example.com # Mon 6pm LON / 10am Mon SFO