Criteria for Ride Check Data

From Date/To Date

Displays check data collected on or between the specified dates. The system searches for check dates of trips that match date values but NOT the date that the trips were extracted for checking.

For example, if you type 04-01-18 and 04-08-18 in the From Date and To Date fields, respectively, only the check data that was recorded for trips within that week appears. If you do not specify any dates, all check data recorded for trips as well as the extraction status (for example, 1/2) appears.

Check Mode

Allows you to display trip or trip data according to a specific check type. The different options are:

Table 2. Check Type Options
Options	Description
All Riding Checks	Displays data for all ride checks regardless of how the data was collected.
Handheld Riding Checks	Only displays data for ride checks where the data was collected on a handheld device.
Survey Sheet Riding Checks	Only displays data for ride checks where the data was collected on survey sheets.
Automated Riding Checks	Displays data collected from an APC and/or ETM. Choose this option only if your vehicles are equipped with an APC or ETM that allows you to import ridership data into the system. For more information, contact your Trapeze representative.
All Point Checks	Displays data for all the point checks regardless of how the data was collected.
Handheld Point Checks	Only displays data for the point checks where the data was collected on a hand-held device.
Survey Sheet Point Checks	Only displays data for the point checks where the data was collected on survey sheets.

Check Type

Transit sites may define custom check types for site specific purposes: for example, a custom transit site ride check type could be NTD or park and ride facilities. Custom Check Types are available for both ride checks and point checks. They are entered into PLAN by your system administrator or Trapeze representative.

Trip Start Time Offset

Trip times may vary from one sign-up period to another. Since ridership is not dependent on one sign-up period, if a date range spans more than one sign-up period, you must decide what time variance (either forward or backward) can be tolerated before trips for different sign-up periods are no longer considered to be the same trip.

The default value is ± 5 minutes. For example, if in Sign-up Period 1, trip 101 has a start time of 7:00 but in Sign-up Period 2, trip 101 has a start time of 7:03, then they are considered the same trip because of the ± 5 minute tolerance. All check/extract data performed for the trip in both signup periods appears.

You can accept the value of five minutes set as the default or change it to a value that is more appropriate to your site.

Note: The trip’s attribute names (direction, service, line, and pattern) must be the same across sign-up periods; otherwise, the system does not view the trips as the same, even if they fall within the acceptable offset time. For example, if the pattern Name 0701 for trip 101 in Sign\-up Period 1 is changed to 0711 in Sign-up Period 2, but the Name values of all the other attributes in trip 101 remain the same, the system treats trip 101 in Sign-up Period 2 as different from trip 101 in Sign-up Period 1.

Checker

Allows you to view check data recorded by a specific checker.

Note: The system generates trip data assigned to a checker only after it has been extracted and not before the trip has been checked.

Comment Type

Allows you to select the appropriate comment type.

Comment Code

Allows you to select the applicable comment code.

BlockId

Information for all blocks appears by default. You can use this filter to see trips and trip data for a single block only.

Pattern

Allows you to see trips and trip data for a specific pattern.

Bus Number

Allows you to filter data to locate vehicles with APC device issues.