Introduction
The Phoenix Real-Time Monitor Page (PRMP) uses both static and real-time General Transit Feed Specification (GTFS) data in order to gauge and report on the current level of bus services operated by the different agencies of Valley Metro. This is open data that is provided by the City of Phoenix on behalf of the entire system.
Service availability
The PRMP is available between 4AM and 12 midnight, seven days a week. Even though a small number of buses operate after midnight, we will shut off tracking. If service after midnight is substantially expanded in the future, we will look at software modifications to support later buses.
About the data
The real time data is obtained through the Vehicle Management System (VMS) that is maintained by City of Phoenix and used throughout the various contractors that operate the bus service. The static schedule data is derived through a feed from the GIRO HASTUS system that is operated by the City of Phoenix on behalf of the entire system.
Known limitations
Not all buses are equipped with VMS. This includes the buses operated by Dunn Transportation to support the three Scottsdale Trolley routes. In addition, there is no VMS equipment on the Tempe Orbit, Glendale GUS buses as well as the Route 685 rural service buses.
There are some known issues in the static GTFS data which we are currently addressing with the RPTA and City of Phoenix:
- Sunnyslope SMART (SSCR) does not show all timepoints in the current GTFS feeds. This limits our ability to display the entire route.
- Mesa BUZZ is missing the final portion of the loop and therefore is not displaying correctly.
- Route 685 data is vintage and does not show a complete route.
- PHX Sky Harbor SkyTrain service is no longer shown.
While we have static data for light rail, we do not yet have a realtime feed for it. The data is available from the RPTA but are having issues with receiving the data.
Main Dashboard
The main dashboard page shows an estimate of the average delay on a route based on the estimated deviation of each bus providing VMS data at the time. Any average delay of less than 3 minutes is considered "Good Service". Even if "Good Service" is reported, there may be a bus on the route reporting a delay of more than 3 minutes.
Delayed buses will may show a range of times where the higher number is the longest delay reported.
Routes showing as "No VMS Data" are routes that can't be reported because no bus has an active VMS. This can happen if a VMS unit is not working correctly, the bus operator forgets to update their VMS to a new route if the bus is interlined, the bus is in a layover zone waiting to start its run or the bus is "deadheading" (operating out of service) after completing one route and starting a new route.
Clicking on the route number link will bring up a Route information display with bus specific details.
On the bottom of the screen is the percentage of the buses that currently have a working VMS feed. The figures below the green line break down the percentage by the 4 major operating contracts. Remember, buses in layover zones and deadheading buses are not counted.
