Skip to main content

Sync the Schedule with the timeplan

Updated over 2 weeks ago

S-079-V4-EN

With the Sync feature, any changes you make in the timeplan will automatically be reflected in your schedule.
This way you do not have to export a new dataset whenever you make changes to the timeplan, which can improve your workflow.

The feature is represented by the green checkmark next to the name of the schedule:

image.png

Syncing your timeplan and schedule for the first time

The initial sync happens once you export a dataset and create/import a schedule with that dataset. That links the schedule to the timeplan.

image.png


Viewing the linked timeplan

To quickly open the timeplan linked to your schedule, open the side menu by clicking the “burger” icon in the top-left corner. There, click Linked Timeplan. This will open the linked timeplan in the Planning module.

image.png

You can also go to the timeplan by right-clicking on a trip in the Gantt view and selecting View in timeplan:

image.png



Sync notifications

Once the timeplan is updated, all linked schedules will automatically be synced as soon as you open them. You will see a green banner saying that your schedule is synced with your timeplan.

image.png


In some cases (described below), the sync will require your confirmation.

Manual sync

If you modify the timeplan while your schedule is open, the sync will require your confirmation. You will see a yellow banner at the top of the Scheduling screen.

image.png


Once your schedule will be synced you’ll be notified about it at the top of the screen. You'll also see a checkmark in a green circle indicating that your schedule and timeplan are synced.

image.png

Revert sync actions

You can revert sync actions if needed, using the link in the banner, or the menu next to the schedule name.

image.png

Unlock your schedule

Your schedule won’t sync if it’s locked, and changes in the timeplan won't affect it. If your schedule is locked, you'll get a yellow notification.

image.png


To sync, you can do one of two things:

  1. Unlock the schedule and refresh it.

  2. Make a copy of the schedule. Work with the synced schedule while keeping a copy locked (and unsynced) for reference or comparison.


Resolve timeplan errors

Your schedule won’t sync if the timeplan has validation errors, and you’ll get a yellow notification.

To sync, fix the validation errors in the timeplan, and refresh the schedule.

image.png


Undo and redo

You will continue to be able to undo and redo actions.

While undo and redo will function normally when the timetable remains unchanged, once the timetable is changed and syncs with the schedule, undo and redo will apply only to actions taken after each sync.

Sync use cases

There are several ways you can use the sync feature, depending in part on whether you have one or multiple timeplans.

Each timeplan can be associated with one dataset or if you need filtered data, several datasets. And each dataset can be associated with several schedules, which can differ from one another based on the preferences selected or manual edits performed on each individual schedule.



Use case 1: One timeplan, multiple schedules

Before the sync feature was introduced, there were many similar datasets for a single timeplan, because each update required exporting a new dataset.

With sync, the baseline should be one dataset for every timeplan. Each dataset can have many schedules, which can have different preferences or different manual edits, but with the same trip information and the same dataset.

image.png

The schedules can have different results and different KPIs, based on the manual edits and specific preferences.

If this timeplan is changed, the schedules will be changed accordingly.

Use case 2: One timeplan, multiple datasets

This use case is for when you have one main timeplan but need to create different schedules that show only certain elements (e.g. one timeplan for all sites, but each site needs to see only its own routes).

You can create these filtered datasets when you export a timeplan to a dataset. In the export, you can filter routes or service IDs.

The schedules will be fit to the filtered dataset

image.png


Use case 3: Multiple timeplans, multiple schedules

The third use case is for when you have different timeplan scenarios such as different routes, travel times, or timetables. Then you should have different timeplans. In that case, each schedule reflects the data that's on the related timeplan.

image.png


Backward sync

If you update trip start times in your schedule, Backward sync lets you reflect those changes in the linked timeplan. Check the article Backward Sync to learn more.

Did this answer your question?