Validation for FX/BlockBuster Scheduling

When importing schedules created in FX/BlockBuster, OPS performs validation.

To avoid errors at import, check for the following scenarios.

Table 1. FX/BlockBusterValidation
What went wrong How to fix it
Duplicate run/ExcCombo combinations.

Run '[xxxxx]', ExcCombo '[xxxxx]' is a duplicate.

In BlockBuster, click BlockBuster > Generate Exception Runs.
Duplicate Rosters. In FX, click Rostering > Renumber.
Duplicate piece numbers within a run.

"Cannot import Run:[xxxxx], Service Group:[xxxxx], ExcCombo:[xxxxx] because it contains duplicate piece numbers."

In BlockBuster, click BlockBuster > Cost > Edit Extras.
Run types not found in the sign up period and division. In BlockBuster, in the Run Types screen, add the missing run types.
Runs without a line group are not imported. Create line groups in FX ancillary data. Click File > Ancillary Data > Fixed > Lines. On the Line Groups tab, click Add.
If a BlockBuster run type is configured for more than one operator, the run type number must be a positive integer below 100. Runs that do not meet this criteria are not imported. In BlockBuster, in the Run Types screen, adjust the run type numbers appropriately.
If a roster contains runs with a run type configured for more than one operator, the RosterTypeNum must be a positive integer below 100. Rosters that do not meet this criteria are not imported. Add a roster type. In FX, in the Rostering screen, select the run and right-click. Click Union Contract, and then click Add Type.
Runs without names but with negative run numbers are not imported. In FX, click Rostering > Run Renumber.
If a roster type has been defined as manual within OPS it cannot be imported. Do one of the following:
  • Remove the rosters from the FX schedule. You can view the roster type on the Rostering screen Display tab.
  • Change the roster type in OPS.
OPS imports runs first and then rosters. It checks to see if the runs in a roster have already been imported. If not, the roster is not imported. Review other validation messages in the log to see if there are warnings on the run. The run may have been skipped due to, for example, a missing run type or line group. Make corrections on the source data, and then import the schedule data again.
If a roster type is not found, rosters of that type are not imported. Add a roster type. In FX, in the Rostering screen, select the run and right-click. Click Union Contract, and then click Add Type.
There are no exceptions in your division.

Warning - division [xxxxx] does not have any exceptions.

This is a warning message. If that is your intent, you can ignore.
BlockBuster imports require a BlockBuster mapping file.

The BlockBuster mapping file was not found. Use the OPS Client Files screen to attach the mapping file.

This is an XML file that maps the fields in the source to the correct OPS schedule field. Use the Update Attached Client File feature in the OPS Client Files screen to attach the mapping file. A sample mapping file can be found in the following location: \Hw\Apps\FixedRoute\Operations\BlockBusterImportMapping.xml