[old] Passenger Help

With the introduction of BODS PTI there’s a call for operators to use their National Operator Codes (NOC) which represent a unique operator at a national level. 

Operator codes are the core piece of information all other network information is built around, they should match your National Operator Code defined in the Traveline NOC dataset.

Operator codes need to match between your TransXChange and any 3rd party suppliers, if these codes are changed it can often lead to downtime of features unless the changes are properly managed.

So if you want to change to using your National Operator Code in your TransXChange (TXC), you should first know the following information before attempting to migrate:

Preparation

1. What your current TransXChange Operator Code(s) are

2. What your National Operator Code(s) are

3. Where these codes are defined (within Passenger Cloud and with your other suppliers)

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

5. When the switchover to your NOC(s) will occur

6. In which order any changes will be made

7. 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 your migration to using your National Operator Code follows these steps:

Recommended steps to change

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. Upload TransXChange to Passenger Cloud using your National Operator Code in both the NationalOperatorCode and OperatorCode fields, this will create new lines and operators in Passenger Cloud immediately

   1. Set the line start dates for all new lines to the agreed date in the future for switching over

   2. Set the line end dates of all old lines to the same date (this will be based upon the time the switchover will actually occur)

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

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

5. Setup the new lines within Cloud, e.g. line branding, colours, names and linked lines

6. Update any suppliers to use the newly defined National Operator Code(s) and lines

   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 date/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. (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.)

7. Confirm that data from suppliers is correctly matching the national operator code(s)/lines.

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

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