If you want to change to using your national operator code, you should first know the following information before attempting to migrate:
What the operator code(s) currently are within your TransXChange
Where these codes are used (within Passenger Cloud and with your other suppliers)
What your national operator code(s) are
What the impact is of these codes not matching between Passenger and supplier(s) for any period of time
When the switchover will occur
In which order any changes will be made
Before starting any migration, you should ensure that all relevant parties are informed of the above details alongside your migration plan.
When you are informed and prepared with the information above we suggest the migration to using your National Operator Code, follows these steps:
Document your migration plan and inform Passenger + relevant suppliers
Confirm with Passenger + relevant suppliers if any other actions are required to minimise downtime
For all existing lines, set the end date to the day before the agreed date for switching over
If the end date is set to the same date as the switchover, your line list will be duplicated until the old lines are deleted.
Prepare a TransXChange dataset using your national operator code in both the
Ensure the line start dates are set to the agreed date in the future for switching over
Ensure the newly defined operator has the correct name, ideally this is set via TransXChange but can be updated via Passenger Cloud
Upload the TransXChange dataset to Passenger Cloud, this will create new lines and operators immediately
Confirm in Passenger Cloud that your new operator/lines are correctly defined
Setup the new lines within Passenger Cloud, e.g. colours, names, PDF’s and linked lines
Update any suppliers to use the national operator code
They should match 1 to 1 exactly with your TransXChange or data may be mismatched/unavailable
This should take effect on the switchover or start date of the new lines, otherwise there will be downtime where Passenger may be unable to match real time data to your TransXChange
Sometimes suppliers will require a re-subscribe to pick up changes to the configuration, this can be triggered within Passenger Cloud
Passenger can temporarily map operator codes from one to another for real time feeds; this can be requested ahead of time to enable a smoother migration.
We need prior notice in order to factor this into our engineering teams work so it's good to mention this as early in the process as possible.
Confirm that data from suppliers is correctly matching your lines using the national operator code
Remove the lines under the old operator code(s)
Let Passenger and any relevant suppliers know that you have successfully migrated
We’ll ensure your configuration is correct moving forward, to prefer using the
We recommend attempting to minimise how long duplicate operators/lines are defined. Uploading a future/draft dataset with new operator codes will still create persistent lines/operators, even if not yet published.