ITS - Intelligent Transportation Systems Report ITS Home Page

3. Evaluation Methodology

The main objective of this evaluation was to measure or confirm the expected outcomes of the CRRAFT system. To accomplish this objective, the evaluation methodology had four main phases:

  1. Develop hypotheses
  2. Determine approach to assess hypotheses
  3. Collect Data
  4. Analyze Data

This evaluation approach was first presented in the Evaluation Plan and Test Plan document, which discussed the first two phases and provided guidelines to conduct Phases 3 and 4. The following sections describe the efforts undertaken during Phases 1 through 3. The data analysis (Phase 4) is described at length in the next chapter - Evaluation Results.

3.1 Hypotheses Development

The first step of the evaluation was to take the expected outcomes presented in Table 2-2 and develop them into hypotheses. The hypotheses are statements that describe the expected outcomes in a more detailed and measurable manner. The expected outcomes and the set of 12 hypotheses developed are listed in Table 3-1. Hypotheses one, two, three and five are considered "key hypotheses."

Table 3-1. CRRAFT Expected Outcomes and Preliminary Set of Research Hypotheses
No.
Hypothesis
Expected Outcome
1
Use of the system saves transit providers time invoicing and reporting to funding agencies
Reduce transit provider time required to prepare and submit reports to funding agencies.
2
Use of the system results in funding agencies having faster access to reports
Reduce transit provider time required to prepare and submit reports to funding agencies.
3
Reports created by the system are accurate and reliable. Use of the system reduces the time funding agencies spend checking and correcting reports and reduces money incorrectly allocated or invoiced
Provide transit providers with improved tracking of transportation benefits used, more accurate allocation of costs resulting in better quality reports to funding agencies.
4
Use of the system reduces the time funding agencies spend researching and collecting information
Provide funding agencies with improved access to information about transit systems, vehicle inventories, clients, client use of transportation benefits, sanctions, transit costs, and budget expenditures.
5
Use of the system reduces the overall time required for transit providers to schedule demand response trips
Speed up trip scheduling process by improving access to client eligibility and vehicle availability information
6
Use of the system results in more efficient schedules for demand response trips
Improve access to information about trips requested, trips scheduled and vehicle availability to improve the efficiency of demand response trip schedules
7 Use of the system reduces the number of unauthorized trips Improve access to client eligibility to avoid scheduling unauthorized trips
8 Use of the system reduces number of in-service mechanical breakdowns Improve vehicle condition by improving access to information about vehicle mileage and age
9 Use of the system reduces the operating cost of transit services Improve funding agency and transit agency efficiency
10 Use of a Web-based system has minimized the time and cost of deployment, technical support, and maintenance Develop a system with minimal costs for deployment, technical support, and maintenance.
11 Transit providers and funding agencies perceive that the benefits of the system outweigh its costs Provide value for investment in the CRRAFT System
12 Use of a single system improves communication between diverse agencies Improve coordination between funding agencies and between funding agencies and transit providers


3.2 Determining Approach to Assess Hypotheses

The assessment of the hypotheses was done through Measures of Effectiveness (MOEs) assigned to each hypothesis (i.e., change in overall time saved preparing reports and invoices, time saved scheduling trips). For most of the hypotheses, the MOEs were assessed before and after the implementation of CRRAFT to understand the impact of the system. Three approaches were designed to collect and analyze the data necessary to assess the MOEs:

  1. Analysis of quantitative measures
  2. Analysis of surveys and interviews with transit providers
  3. Analysis of interviews with funding agencies and ATRI

3.2.1 Analysis of Quantitative Measures

This is an analysis of standard operating performance metrics typically used by transit providers, and changes in those measures before and after CRRAFT. It also included measurable aspects of the invoicing and reporting process before and after CRRAFT. The data for this analysis came primarily from system performance figures archived by either the transportation providers or the PTPB, and invoices and invoice submission logs archived by the PTPB.

Because CRRAFT was already in operation throughout New Mexico, before and after comparisons of these measures depended on the availability of archived data related to these performance metrics. The Evaluation Team noted that a lack of knowledge on the availability of archived data limited the extent to which the plans for the evaluation could be finalized. In order to remove this ambiguity, a preliminary assessment was conducted. The primary purpose of this assessment was to identify the types of archived data that were available to support this evaluation and to determine if sufficient quantitative data of usable quality were available for a before/after analysis of the CRRAFT system. Table 3-2 summarizes the results of this assessment. Note that not all of the hypotheses shown in Table 3-1 are included in this summary since the Preliminary Assessment focused only on hypotheses that required the evaluation of quantitative data elements.

Table 3-2. Summary of Preliminary Assessment Findings
No.
Hypothesis
Measure of Effectiveness
Data Elements
Availability
Notes
1
Use of CRRAFT saves transit providers time invoicing and reporting to the funding agencies
Change in overall time saved preparing reports and invoices
Before and after staff time to prepare reports, time to maintain data in system
Subjective only
Transit providers do not track, but can provide subjective assessment of time saved.
2
Use of the system results in funding agencies having faster access to reports
Change in time between end of reporting period and report submittal
Before and after days between end of reporting period and report submittal
Objective and Subjective
Data available in PTPB logs for FY2002. Should be available for current FY.
3
Reports created by CRRAFT are accurate and reliable and use of the system reduces the time funding agencies spend checking and correcting reports and reduces money incorrectly allocated or invoiced.
Change in percent of errors, time saved correcting or checking, money saved from accurate allocations
Before and after percent errors, staff time spent checking and correcting errors, dollars lost due to incorrect allocations
Some objective data to use as a sample
Hypothesis cannot be tested until verification functionality has been added to CRRAFT (early Spring 2004). Cannot verify that past data are complete - depends on program manager.
5
Use of the system reduces the overall time required for transit providers to schedule demand response trips
Time saved scheduling trips
Before and after staff time required (or assigned) to schedule trips
Subjective data only
Transit providers do not track, but can provide subjective assessment of time saved.
6
Use of the system results in more efficient schedules for demand response trips
Change in passengers per revenue mile or revenue hour
Before and after total passengers, revenue miles, revenue hours
Objective and Subjective
Data available for Section 5311 providers only.
7
Use of CRRAFT reduces the number of unauthorized trips
Change in number of unauthorized trips provided and dollar value of unauthorized trips
Before and after number of unauthorized trips, dollar value of unauthorized trips
Subjective data only
Audit files not complete or detailed enough to include data.
8
Use of the system reduces the number of in-service mechanical breakdowns
Change in miles between revenue service breakdowns
Before and after vehicle miles, in-service mechanical failures
Yes, for those using the Vehicle module
Past data available. Need to wait for CRRAFT to include mileage functionality (Summer 2004).
9
Use of CRRAFT reduces the operating cost of transit service
Change in operating cost per revenue mile or revenue hour
Before and after operating cost, revenue miles, revenue hours
Yes
Data available for Section 5311 providers only. Cost per passenger available for JARC. Significant variation from month to month - may need to use annual average.
10
Use of a Web-based system has minimized the time and cost of deployment, technical support, and maintenance.
Comparison of CRRAFT costs to those of similar commercially available products
One-time and on-going costs for CRRAFT and commercially available similar products
Possibly
Have not obtained from ATRI, but may be able to do our own research.


3.2.2 Analysis of Surveys and Interviews with Transit Providers Staff

To offset the limited amount of archived quantitative measures available, the national evaluator proposed to conduct an analysis of the processes used before and after CRRAFT in order to estimate the impact of CRRAFT. For example, CRRAFT provides a uniform and consistent set of reports to PTPB, which should decrease the amount of manual processing required to handle those reports. Both quantitative and qualitative subjective data were collected for this portion of the study, largely through interviews and surveys with operating agencies.

An attitudinal survey was used to obtain user opinions on the impact of CRRAFT on their operations. In order to facilitate analysis, the survey consisted primarily of questions whose responses are numbers in a linear scale (e.g., "What impact has CRRAFT had on the time spent preparing reports for PTPB?" with responses like "1 It takes a lot longer with CRRAFT; 2 It takes a little bit longer with CRRAFT; 3 The time required is about the same with and without CRRAFT; 4 It takes a little bit less time with CRRAFT; or 5 It takes a lot less time with CRRAFT").

3.2.3 Interviews with Funding Agencies and ATRI

Interviews were conducted with staff of the PTPB, NMDOT, and the ATRI to review and discuss lessons learned and best practices with respect to the implementation, operations and maintenance of the CRRAFT system that were not previously identified in the CRRAFT Case Study . Interviews with ATRI staff responsible for developing and maintaining CRRAFT provided costs of developing CRRAFT, plans for future enhancements to the system, and the expected costs for these enhancements. Because one of the benefits of CRRAFT is the creation of a uniform processing system for the 27 participating agencies, which facilitates future enhancements, this type of information is important in understanding the full benefits of CRRAFT.

3.2.4 Summary

The hypotheses and these analysis approaches for assessing them formed the basis for the evaluation. A summary of the evaluation approach including hypotheses, MOEs, data sources and evaluation method is presented in Table 3-3.

Table 3-3. The Evaluation Approach for the CRRAFT Evaluation
No.
Hypothesis
MOE
Data Sources
Evaluation Methods
1 Use of the system saves transit providers time invoicing and reporting to funding agencies Transit provider staff opinions on time requirements Surveys of transit provider staff Surveys of transit provider staff
Review of invoicing and reporting process, before and after CRRAFT Interviews with selected transit provider staff Analysis of processes to estimate time requirements
2 Use of the system results in funding agencies having faster access to reports Time lag between end of reporting period and report submission dates PTPB invoice submission logs Before and after comparison
Transit provider staff opinions on report timing Surveys of transit provider staff Analysis of survey results
Funding agency staff opinions on report timing Survey of funding agency staff Analysis of survey results
3 Reports created by the system are accurate and reliable. Use of the system reduces the time funding agencies spend checking and correcting reports and reduces money incorrectly allocated or invoiced Review of report error and resubmission logs Transit provider archives of resubmitted invoices Review of resubmitted reports
Transit provider staff opinions on report accuracy Surveys of transit provider staff Analysis of survey results
Funding agency staff opinions on report accuracy Survey of funding agency staff Analysis of survey results
Funding agency staff opinions on time spent checking and correcting reports Survey of funding agency staff Analysis of survey results
4 Use of the system reduces the time funding agencies spend researching and collecting information Funding agency staff opinions on research time Survey of funding agency staff Analysis of survey results
5 Use of the system reduces the overall time required for transit providers to schedule demand response trips Transit provider staff opinions on time requirements Surveys of transit provider staff Analysis of survey results
6 Use of the system results in more efficient schedules for demand response trips. Passengers per revenue mile (5311 subgrantees) Before data in monthly invoices Before/after comparison
Passengers per revenue mile (5311 subgrantees) After data maintained by CRRAFT Before/after comparison
Per passenger operating cost (5311 and 3037 subgrantees)   Before/after comparison
Passengers per trip   Before/after comparison
Transit provider staff opinions on efficiency of demand response schedules   Before/after comparison
7 Use of the system reduces the number of unauthorized trips HSD-ISD assessment of the extent of unauthorized trips HSD-ISD management evaluation Review of evaluation report
Transit provider staff opinions on the extent of unauthorized trips Surveys of transit provider staff Analysis of survey results
Funding agency staff opinions on the extent of unauthorized trips Survey of funding agency staff Analysis of survey results
8 Use of the system reduces number of in-service mechanical breakdowns Transit provider staff opinions on the frequency of in-service breakdowns Surveys of transit provider staff Analysis of survey results
9 Use of the system reduces the operating cost of transit services Operating cost per revenue hour (5311 subgrantees) Before data in monthly invoices Before/after comparison
Operating cost per revenue mile (5311 subgrantees) After data maintained by CRRAFT Before/after comparison
Operating cost per rider (5311 and 3037 subgrantees)   Before/after comparison
Transit provider staff opinions on changes in the operating cost   Before/after comparison
10 Use of a Web-based system has minimized the time and cost of deployment, technical support, and maintenance Cost comparison of CRRAFT and commercially available products ATRI report on relative costs* Review of report findings
CRRAFT development staff opinions on the time and cost of deployment, support, and maintenance Interviews with CRRAFT development staff Review of interview findings
11 Transit providers and funding agencies perceive that the benefits of the system outweigh its costs Transit provider staff opinions on the costs and benefits of CRRAFT Surveys of transit provider staff Analysis of survey results
Funding agency staff opinions on the costs and benefits of CRRAFT Surveys of funding agency staff Analysis of survey results
12 Use of a single system improves communication between diverse agencies Transit provider staff opinions on interagency communication Surveys of transit provider staff Analysis of survey results
Funding agency staff opinions on interagency communication Surveys of funding agency staff Analysis of survey results
Table Notes: *This report was not located. The Evaluation Team determined during the early stages of the project that if this report was not available, then doing independent research to reproduce those results was not a cost-effective alternative. Hence, the assessment of this MOE was abandoned.


3.3 Data Collection

In this phase of the evaluation, and based on the approaches previously determined, the Evaluation Team collected data from a number of sources, including relevant documents and archived data from the CRRAFT system. Also included in the data collection efforts were surveys and interviews with transit provider and funding agency staff. The following subsections describe the data collection efforts.

3.3.1 Data and Documents

The Evaluation Plan identified several electronic and physical documents that were needed to assist with the assessment of the hypotheses. These documents are also summarized in Table 3 3 above under the column called Data Sources. These documents and data were collected as follows.

PTPB Invoice Submission Logs

The PTPB files include a folder for each transit provider receiving Section 5311 and/or Section 3037 (JARC) funding. Separate files are kept for each fiscal year. Each of these files includes, among other things, a log of the invoice/payment process. These invoice submission logs for FY02 and FY04 were consulted by the Evaluation Team. One of these logs is presented as an example in Appendix A.

These invoice submission logs provided, among others, the date of initial invoice submission, any problems or errors with the invoice, the date of the final invoice submission had there been errors on the initial invoice, the date the invoice was entered into the PTPB database, and the date the invoice was given third level approval at PTPB (accepted for payment). These data provided the team with the ability to analyze the submission lag (days between the date at which invoices are actually submitted and the submission deadline) before (FY02) and after (FY04) the implementation of CRRAFT. With these data, the team was also able to determine how often errors were found in the invoices and re-submissions were required before and after CRRAFT. The time required to resolve erroneous invoices was also determined. Finally, the data also allowed the Team to calculate the time required by PTPB to approve the invoices, before and after CRRAFT.

The Evaluation Plan anticipated the review of invoice re-submittal records kept by the transit providers. However, not all the providers kept these records and the Evaluation Team decided to conduct the analysis based solely on the records in the Submission Logs kept at the PTPB. Yet, the issue of invoice re-submission was included in the surveys to the Providers.

Monthly Invoices for FY02 and FY04

The Evaluation Team collected the monthly invoices submitted by the transit providers to the PTPB before (FY02) and after (FY04) CRRAFT. Section 5311 providers include number of passengers, number of revenue miles, hours of service provided, and operating cost on those invoices. Section 3037 providers include number of passengers and operating costs. For FY02 the monthly invoices were Excel-based invoices, for FY04 the invoices were produced by CRRAFT. An example of these invoices is shown in Appendix B.

The data in the invoices were utilized to calculate commonly used operational metrics (i.e. ridership, cost per revenue hour) to compare the performance of transit providers before (FY02) and after (FY04) CRRAFT.

Some of the data found in CRRAFT for FY04 were found to be out of range. Specifically, Carlsbad, Hobbs, Las Vegas, Los Lunas, Taos, and Zuni had suspicious figures for several entries of monthly vehicle miles, and Navajo Nation, Taos, and Zia Therapy had out of range figures for a few entries of monthly vehicle hours. For example, the monthly vehicle hours for Zia Therapy range between 501 and 591 in all months in FY04 except for November 2003, in which the recorded vehicle hours are 85,580. The agencies were asked about these extremely high figures of vehicle hours and vehicle miles, and they cited errors in the CRRAFT system as the cause for these outliers in the data. Navajo Nation and Zia Therapy only had one month out of twelve with erroneous vehicle hours data. Thus, the outlier number was thrown out and replaced by the average of the remaining eleven months. This procedure could not be repeated with the other agencies because the number of months with suspicious figures was higher. Hence, Taos was not included in analyses including vehicle hours and no analyses were done with the vehicle miles metrics.

HSD-ISD Management Evaluation.

An HSD-ISD evaluation was conducted in June 2002, which included an audit of nine transit providers. The Evaluation Team collected a copy of this report because the section on quarterly fiscal reporting includes documentation of discrepancies between what providers billed NMSHTD and the amount they were reimbursed. These data will help assess Hypothesis No. 7 about the extent of unauthorized trips.

ATRI Report on Costs of Commercial Systems.

During the preliminary assessment, it was mentioned that this report was produced by ATRI; however during the data collection effort, the Team found out that although ATRI did conduct an informal review of available commercial products that could be used to provide the types of services included in CRRAFT, an official report on the topic was never written or could not be located. The Evaluation Team determined during the early stages of the project that if this report was not available, then doing independent research to reproduce those results was not a cost-effective alternative. Hence, the assessment of the MOE associated with this report was abandoned.

The CRRAFT Case Study.

A case study of CRRAFT that provides information on CRRAFT, its origins, its costs, and plans for its future was also collected and reviewed. The case study was mostly used to obtain background information as needed. This CRRAFT case study was one of the "best practices" analyzed by Multisystems (now part of TranSystems) for a report submitted in 2002.

3.3.2 Surveys of Transit Provider Staff

Surveys of transit provider staff were conducted by the Evaluation Team to obtain opinions on the impact of CRRAFT on transit operations. Derived from the expected outcomes and hypotheses, a survey was developed that explored user attitudes and perceptions of CRRAFT's impact on such day-to-day operations as preparing monthly invoices, scheduling demand responsive trips, and operational efficiency and cost. The survey consisted of four types of questions: multiple choice (where responses were selected from a list of six choices), fill-in questions on time estimation, ranking of CRRAFT features, and two open-ended (free text) questions. A copy of the survey questions are shown in Appendix C.

The survey was administered to CRRAFT users at 26 transit agencies (representing about 60 users). Prior to distributing the surveys, each transit agency supervisor was contacted via telephone. The telephone call provided an opportunity to present an overview of the evaluation and survey, obtain some background information from the transit agency, and enlist their participation. Afterwards, the surveys were distributed in late December 2004 and early January 2005 via E-mail, and were returned either by E-mail, fax, or U.S. mail. In some cases, follow-up phone calls were made to transit agencies to clarify responses or comments on completed surveys or to make a request for their survey(s). Forty surveys were returned representing 24 of the 26 transit providers (a return rate of about 92%). At some transit agencies, each CRRAFT user completed one survey. At others, multiple users completed a single survey. This difference was permitted because at some transit agencies CRRAFT responsibilities were distributed to multiple staff members (e.g., Person A responsible for the scheduling, Person B preparing the monthly invoices).

The survey data were manually entered into a database and descriptive statistics were computed using SPSS (Statistical Program for the Social Sciences) statistical software. In cases where multiple surveys were returned from the same transit agency, an average rating (or score) was computed for each question and used in the SPSS analysis to simplify the interpretation of the statistics. This data manipulation method reduced the bias that would result in over-weighting ratings from agencies submitting multiple surveys, especially when compared to surveys submitted from transit agencies that combined the responses from multiple users into one survey. The survey results are presented in Chapter 4 of this report.

3.3.3 Interviews with Funding Agencies, PTPB, ATRI and Transit Providers

The Evaluation Team interviewed the managers and staff at the NMHSD, NMDOT, ATRI, and several transit agencies. Two different interview guides were developed. The interview guide for funding agency managers/staff (see Appendix D) investigated what was working well with CRRAFT, what needed improvement, and what other functions would be useful additions to CRRAFT. The interview guide for Transit Agency Managers (see Appendix E) focused on gathering information about their experience with the CRRAFT application and the effect CRRAFT has had on their organization. Transit providers were split over time savings, efficiency, accuracy, operational impact, and overall opinion of CRRAFT.

NMDOT and ATRI interviews were held in face-to-face meetings that took place in early December 2004. NMHSD and most transit agency interviews were held over the telephone in December 2004 and January 2005. Most interviews were completed in 30 to 60 minutes.

Since the number of interviewees was relatively small, a statistical analysis of the responses was not conducted. The results of these interviews, which were primarily anecdotal in nature, were used to guide follow-up discussions and explore operational changes resulting from the use of CRRAFT.

In addition to the initial interviews, follow-up discussions were conducted with five transit agencies in April 2005 during the New Mexico Public Transport Association Conference in Albuquerque. These discussions allowed a more thorough investigation of issues that were raised when the data and survey results were analyzed. It also provided an opportunity for gaining a clearer picture of the performance and perceptions of CRRAFT.

Previous | Next