If you want to change to using your national operator code, you should first know the following information before attempting to migrate: 


  1. What the operator code(s) currently are within your TransXChange

  2. Where these codes are used (within Passenger Cloud and with your other suppliers)

  3. What your national operator code(s) are

  4. What the impact is of these codes not matching between Passenger and supplier(s) for any period of time

  5. When the switchover will occur

  6. 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: 


  1. Document your migration plan and inform Passenger + relevant suppliers

  2. Confirm with Passenger + relevant suppliers if any other actions are required to minimise downtime

  3. For all existing lines, set the end date to the day before the agreed date for switching over

    1. 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.

  4. Prepare a TransXChange dataset using your national operator code in both the NationalOperatorCode and OperatorCode fields

    1. Ensure the line start dates are set to the agreed date in the future for switching over

    2. Ensure the newly defined operator has the correct name, ideally this is set via TransXChange but can be updated via Passenger Cloud

  5. Upload the TransXChange dataset to Passenger Cloud, this will create new lines and operators immediately

  6. Confirm in Passenger Cloud that your new operator/lines are correctly defined

  7. Setup the new lines within Passenger Cloud, e.g. colours, names, PDF’s and linked lines

  8. Update any suppliers to use the national operator code

    1. They should match 1 to 1 exactly with your TransXChange or data may be mismatched/unavailable

    2. 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

    3. Sometimes suppliers will require a re-subscribe to pick up changes to the configuration, this can be triggered within Passenger Cloud

    4. 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.

      1. 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.

  9. Confirm that data from suppliers is correctly matching your lines using the national operator code

  10. Remove the lines under the old operator code(s)

  11. Let Passenger and any relevant suppliers know that you have successfully migrated

    1. We’ll ensure your configuration is correct moving forward, to prefer using the NationalOperatorCode field

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.