About Ancillary Data

Ancillary data is created based on your transit site policies and customizes PASS to the needs of your transit agency.

Ancillary data for PASS is created in Trapeze4 and Trapeze5.

Ancillary data is one of several tiers of information that must be set up in sequence:
  1. Ancillary data must be created and system properties must be set up.
  2. Clients and employees must be registered.
  3. A database of common locations must be created.
  4. Garages and vehicles must be registered.
  5. Polygons must be defined.
  6. Runs must be created.

After this framework has been created, you can book trips for clients, schedule trips to runs, and perform dispatching activities on the day of operation.

Ancillary Data

Ancillary data reflects the needs of each individual transit agency. As a result, information defined for the space types or mobility types used by one transit agency typically does not reflect the information defined for another transit agency.

Ancillary data is one of the primary layers of settings within PASS, but it is itself layered. Some types of ancillary data can only be created if other types of ancillary data have already been defined. For example, to define Passenger Types, Space Types and Fare Types must already be defined. If a drop-down list is provided, there's a good chance it contains a type of ancillary data. If the drop-down list is empty, it almost certainly contains ancillary data.
Space Types and Fare Types ancillary data and arrows showing how they are used in Passenger Types ancillary data. Space Types feeds the Default space type list and Fare Types feeds the FareType list.

Typically, ancillary data is set up in advance based on your transit agency's needs by your Trapeze representative. However, if new definitions must be added to existing ancillary data in the system, system administrators may the ones performing these duties.