Greater Cleveland Regional Transit Authority (GCRTA) Radio/ITS Project Final Report

Mishra, Santosh · 2016 · ROSA P / United States. Federal Transit Administration. Office of Research, Demonstration, and Innovation

archive: archived pipeline: cataloged verified

Get this paper ↗ (full text — opens at the source; we link to it, we don't host it)

Summary

This report evaluates the deployment of radio and Intelligent Transportation System (ITS) technologies at the Greater Cleveland Regional Transit Authority (GCRTA). The project, initiated in 1998 and accepted in 2012, aimed to replace obsolete communication infrastructure and enhance operational efficiency, safety, and service reliability. GCRTA implemented an Enhanced Digital Access Communication System (EDACS) for voice and data, alongside Computer-Aided Dispatch/Automatic Vehicle Location (CAD/AVL), Automated Vehicle Announcements (AVA), Automated Passenger Counters (APCs), and Vehicle Component Monitoring (VCM). The final installation covered 470 fixed-route buses, 84 paratransit vehicles, and rail cars, supported by four radio towers. The evaluation, conducted by TranSystems Corporation for the Federal Transit Administration, sought to assess the impact of these technologies against specific goals, including reduced operational costs, improved on-time performance, and accurate data reporting. The methodology relied on a hypothesis-testing framework using archived ITS data and staff interviews. However, the evaluation team found that quantitative analyses were largely inconclusive due to significant limitations in archived data quality. Issues included missing Automatic Vehicle Location (AVL) data and discrepancies in Automated Passenger Counter (APC) records, which prevented rigorous statistical testing of hypotheses regarding operational costs, emissions, and customer satisfaction. Consequently, the findings are based primarily on qualitative assessments, including staff interviews and reviews of historical project documentation. Qualitative findings indicate that the overall impact of the deployed technologies was positive, with staff reporting improved operational capabilities. However, the deployment process was fraught with challenges that delayed system acceptance by approximately ten years. Key issues included ambiguous requirements language regarding CAD/AVL functions, frequent changes in vendor management (from Rockwell to Siemens, Continental AG, and finally Trapeze ITS), and inadequate contract milestone management, where the majority of funds were paid before software testing. Additionally, the lack of a formal systems engineering approach, insufficient staffing, limited training, and poor interdepartmental communication hindered system adoption and integration. The rail mode integration was particularly problematic, as the CAD/AVL system lacked necessary functions for rail operations and suffered from GPS coverage issues. The report concludes that while the technologies offer benefits, successful implementation requires rigorous planning, clear requirements, and effective project management. GCRTA has since taken steps to improve data quality, but the evaluation highlights the critical need for robust data management practices to support future quantitative assessments. The findings serve as a case study for other transit agencies, emphasizing the importance of aligning procurement processes with technical realities, ensuring adequate staffing and training, and maintaining institutional knowledge throughout long-term deployments.

Key finding

Quantitative hypothesis testing was inconclusive due to inadequate archived data quality, leading to conclusions based on staff interviews that determined the overall impact of the deployed technologies was positive.

Methodology

mixed_methods

Provenance

The full processing record for this entry. Every stage of this paper's journey through the pipeline is logged — what ran, with which tool and model, how many attempts it took, and when it last completed. Discovered via bulk_ingest_rosap on 2026-05-23 (6 acquisition events logged).

Summary generated by qwen3.6-27b-prismaquant on 2026-06-10; verification: verified.

Topics

Ranked by relevance to this paper. Hover a topic for its definition.

• dms validation