Follow the sun (multiple locations)
Demonstrates a schedule balancing three 8-hour shifts that follow the sun around the globe.
In this example there are 3 teams, one in London, one in Sydney and one in San Francisco, who work together to provide an overall on-call schedule. The London and San Francisco teams are equally sized and participate every day of the week, while the Sydney team with fewer people only participates during their week days, with the weekend shifts covered only from London and San Francisco.
Like the two-location example, this uses one schedule per team, plus a fourth schedule that joins them into the overall rotation.
Main Schedule Shift Configuration Entries
The main schedule uses the Australia/Sydney time zone so the weekend shift start times for London and San Francisco are easy to see.
Sydney and London start a shift every weekday. San Francisco’s shift starts at 02:00 Sydney time from Tuesday to Saturday, which needs one row per day, and at 03:00 on Sunday and Monday. The last row is the extra shift London needs for weekend cover. This uses all 10 shifts a template can have.
| Day: | Hour: | Minute: | Primary: | Secondary: |
|---|---|---|---|---|
| Weekdays | 10 | 00 | syd-team | [Not assigned] |
| Weekdays | 18 | 00 | lon-team | [Not assigned] |
| Tue | 02 | 00 | sfo-team | [Not assigned] |
| Wed | 02 | 00 | sfo-team | [Not assigned] |
| Thu | 02 | 00 | sfo-team | [Not assigned] |
| Fri | 02 | 00 | sfo-team | [Not assigned] |
| Sat | 02 | 00 | sfo-team | [Not assigned] |
| Sun | 03 | 00 | sfo-team | [Not assigned] |
| Mon | 03 | 00 | sfo-team | [Not assigned] |
| Weekends | 15 | 00 | lon-team | [Not assigned] |
Sample shifts
2023-07-24 03:00 sfo-team
2023-07-24 10:00 syd-team
2023-07-24 18:00 lon-team
2023-07-25 02:00 sfo-team
2023-07-25 10:00 syd-team
2023-07-25 18:00 lon-team
2023-07-26 02:00 sfo-team
2023-07-26 10:00 syd-team
2023-07-26 18:00 lon-team
2023-07-27 02:00 sfo-team
2023-07-27 10:00 syd-team
2023-07-27 18:00 lon-team
2023-07-28 02:00 sfo-team
2023-07-28 10:00 syd-team
2023-07-28 18:00 lon-team
2023-07-29 02:00 sfo-team
2023-07-29 15:00 lon-team
2023-07-30 03:00 sfo-team
2023-07-30 15:00 lon-team
2023-07-31 03:00 sfo-team
2023-07-31 10:00 syd-team
2023-07-31 18:00 lon-team
London Team Shift Configuration Entries
The London team schedule (configured in the GMT time zone) uses the same 4 day/3 day split as seen in the previous follow the sun example.
| 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
Sydney Team
The small Sydney team uses basic week long rotations.
2023-07-24 10:00 person2@example.com
2023-07-31 10:00 person3@example.com
2023-08-07 10:00 person1@example.com
2023-08-14 10:00 person3@example.com
Fully Rendered Schedule
In the On-Call Optimizer web UI, or exported to an on-call product, the combined schedule looks like this:
# Rendered in UTC
2023-07-24 00:00 person2@example.com # Mon 10am SYD / Sun 5pm SFO / Mon 1am LON
2023-07-24 08:00 london-member1@example.com # Mon 6pm SYD / Mon 1am SFO / Mon 9am LON
2023-07-24 16:00 member2@example.com # Tue 2am SYD / Mon 9am SFO / Mon 5pm LON
2023-07-25 00:00 person2@example.com # Tue 10am SYD / Mon 5pm SFO / Tue 1am LON
2023-07-25 08:00 london-member1@example.com # Tue 6pm SYD / Tue 1am SFO / Tue 9am LON
2023-07-25 16:00 member1@example.com # Wed 2am SYD / Tue 9am SFO / Tue 5pm LON
2023-07-26 00:00 person2@example.com # Wed 10am SYD / Tue 5pm SFO / Wed 1am LON
2023-07-26 08:00 london-member1@example.com # Wed 6pm SYD / Wed 1am SFO / Wed 9am LON
2023-07-26 16:00 member3@example.com # Thu 2am SYD / Wed 9am SFO / Wed 5pm LON
2023-07-27 00:00 person2@example.com # Thu 10am SYD / Wed 5pm SFO / Thu 1am LON
2023-07-27 08:00 london-member1@example.com # Thu 6pm SYD / Thu 1am SFO / Thu 9am LON
2023-07-27 16:00 member4@example.com # Fri 2am SYD / Thu 9am SFO / Thu 5pm LON
2023-07-28 00:00 person2@example.com # Fri 10am SYD / Thu 5pm SFO / Fri 1am LON
2023-07-28 08:00 london-member3@example.com # Fri 6pm SYD / Fri 1am SFO / Fri 9am LON
2023-07-28 16:00 member3@example.com # Sat 2am SYD / Fri 9am SFO / Fri 5pm LON
2023-07-29 05:00 london-member3@example.com # Sat 3pm SYD / Fri 10pm SFO / Sat 6am LON
2023-07-29 17:00 member4@example.com # Sun 3am SYD / Sat 10am SFO / Sat 6pm LON
2023-07-30 05:00 london-member3@example.com # Sun 3pm SYD / Sat 10pm SFO / Sun 6am LON
2023-07-30 17:00 member1@example.com # Mon 3am SYD / Sun 10am SFO / Sat 6pm LON
2023-07-31 00:00 person3@example.com # Mon 10am SYD / Sun 5pm SFO / Mon 1am LON