Minimum Requirements for Third Party Systems

To achieve integration with other Trapeze applications, a third party system should have the following minimum requirements:

  1. Ability to capture ridership attributes (for example, passenger count data) and associate them with schedule data elements at the stop level (for example, StopID and TripID). The data elements can arrive in any sequence provided that the data elements are associated with a StopID and TripID.
  2. Ability to parse associated data into a structured data stream or structured flat file.
  3. Provide a data exchange format that:
    • Integrates with other systems that is well-documented and published.
    • Conforms with a format specified by Trapeze and controlled by an Interface Control Document (ICD).

Ideally, the count system should offer a standard data processing form to facilitate communication, data exchange, and application integration. If a third party vendor can not offer some form of system and user interaction, then a file transfer should be sufficient.

The ideal method for data transmission would be during bulk data transfer when a bus returns to a depot, for example, passenger load is “0” and all runs have been completed.