News

Media Statement: Summer '22 Service Cuts due to OCC Staffing Shortage

BOSTON, June 17, 2022 —  Today's announcement of service cuts for the Red, Orange, and Blue lines due to staffing shortages at the Operations Control Center is a painful example of how badly the MBTA has been failed by poor oversight and a lack of stable, dedicated funding. Contrary to the current narrative, the FTA’s directives are not about the age of the system. All of the identified issues are the result of a decades-long, bipartisan aversion to funding the T adequately. Billions of bond authorizations for capital projects have masked the need for more funding and stability for the T’s operating budget. The T has been in and out of a state of fiscal crisis for decades; this is not how one builds a reliable system free from safety concerns. 

For years the administration’s laudable focus on increasing capital spending has come at the expense of attention to day-to-day maintenance and safety needs. Earlier this year in a misguided decision, the T shifted hundreds of millions from the operating budget. The administration and legislature need to treat the employee shortage at the MBTA like an emergency, because it is one. We call on the T to promptly convene labor and workforce development partners, along with the FTA, to develop a comprehensive plan to staff up the MBTA. The administration and legislature should work with this team to provide them with the resources to give competitive salaries and streamline hiring.

This action would not pass an FTA equity analysis if it happened in a vacuum; this should be a wake-up call to a legislature that has made equity a priority. The burdens of this action will fall disproportionately on the most vulnerable people in our workforce, who cannot work remotely and depend on the T to get to work. This action also likely would not pass any environmental test, as it will very likely suppress ridership, increase VMT, emissions, and congestion. 

The irony of these cuts being announced as we await the joint House and Senate Climate bill should not be lost on anyone. The MBTA is one of the most important tools to help us reduce emissions from the transportation sector. The legislature must find a stable source of funding to address state of good repair and operating funding to ensure reliable, safe service. They should act decisively this year in the transportation bond bill and the budget.  

We await hearing the T’s plan to fast track new safety and operations hires and reverse these service cuts. We also await hearing the plans of legislative leaders to address the chronic funding shortfall issues, and set aside funding for the T to use as it responds to the FTA’s directives. We call on municipal, legislative, and business leaders to help the MBTA hire the staff it needs to run a modern, safe system that responds to our economic, environmental, and equity needs.  

For media inquiries, please e-mail media@transitmatters.org

###

Media Statement: MA Senate Climate Bill

Media Statement: MA Senate Climate Bill

TransitMatters is thrilled that the Massachusetts Senate passed a number of amendments to Senate Bill 2819, “An Act Driving Climate Policy Forward”, to make the bill more equitable and comprehensive.

Data Dashboard 3.0: Eyes on the Bus

In continued support of the TransitMatters mission to unite advocates and inform the public about the state of the MBTA system, TransitMatters Labs is pleased to announce that bus data is now available and ready for exploration in Data Dashboard 3.0.

The Data Dashboard carries a storied history. Our work on its first version began in 2019 with the objective of providing an easy-to-use web site to explore travel times, time between trains (headways), and time spent at stations (dwell times) for trips on the subway network. The dashboard’s update in 2021 began computing statistics on those metrics over time, allowing for analysis of longer-term system trends. We’re thrilled that updating the Data Dashboard to version 3.0 with support for MBTA buses means that both transit advocates and the public can scrutinize the bus network nearly as much as the subway. It is also incredibly significant for TransitMatters itself—it enables our campaigns and our partners to study the performance of bus routes to make better informed policy recommendations.

To view the new bus data in the Data Dashboard, head over to https://dashboard.transitmatters.org. There is a new slider to switch from Subway over to Bus in the top-left corner:

A slider toggle for bus and subway has been added in the top left corner

Switching the slider to “Bus” changes the Dashboard to a yellow theme—that’s how you know you’re ready to dive in. Select a route, an origin station, a destination station, and a date (or date range) to continue. Bus data is available from August 1, 2018 through November 30, 2021 on the following routes:

  • 1 - Harvard Sq to Nubian

  • 15 - Fields Corner / Kane Sq to Ruggles

  • 22 - Ashmont to Ruggles via Talbot Ave

  • 23 - Ashmont to Ruggles via Washington St

  • 28 - Mattapan to Ruggles

  • 32 - Wolcott/Cleary Sq to Forest Hills

  • 39 - Forest Hills to Back Bay

  • 57/57A - Watertown Yard / Oak Sq to Kenmore

  • 66 - Harvard Sq to Nubian

  • 71 - Watertown Sq - Harvard

  • 73 - Waverley Sq - Harvard

  • 77 - Arlington Heights - Harvard

  • 111 - Woodlawn - Haymarket

  • 114/116/117 - Wonderland - Maverick

The bus route selection bar looks similar to the subway bar

Unfortunately, buses don’t collect the information we need to compute dwell times (time spent at stop), so these are the three metrics available for bus:

  • Travel times

  • Time between buses (headways)

  • Travel times by hour - choice of weekdays or weekend/holidays

After selecting input parameters, the Data Dashboard then presents you charts for those metrics. Here is an example from Route 1:

You may notice the interquartile range is often larger than you would see for the subway. This is because buses are generally more variable, since they are more susceptible to factors like traffic, which changes throughout the day. To help dive into this phenomenon more closely, we added a new type of chart: 

This “Travel times by hour” visualization helps clarify the variability shown in travel times above: mid-day trips (especially during rush hour!) are much slower than early morning and late-night. We also added an option to view weekend averages here as well.

This data makes some bus network challenges incredibly clear, such as headway management and bunching. For example, here is evidence of bunching on Route 1 at Putnam Avenue, near its western terminus at Harvard Square. On this day, September 23, 2021, bus frequency fluctuated between 1 minute and almost 30 minutes, particularly in the middle of the day. This may be due to data collection issues (if a bus running on Route 1 had a faulty GPS locator, for example). However, in this case, the average is a bus every 12-15 minutes, giving credence to the bunching scenario over the “missing trips” hypothesis.

These charts also show how bus lane installation can greatly affect the rider experience. After the City of Boston’s installation of the center-running bus lane on Columbus Avenue, Route 22 travel times during the evening commute dropped from 14 minutes to 10 minutes.

Before bus lane installation (October 2021):

After bus lane installation (November 2021):

We’re incredibly thankful for MassDOT’s Office of Performance Management and Innovation (OPMI); they consistently publish bus departure data that we use for this feature in the Data Dashboard. This update would not be possible without the hard work of everyone there and at the MBTA.

TransitMatters is looking forward to seeing what the community finds in Data Dashboard 3.0. Check it out! We also continue to appreciate your questions and feedback, and heads up—we’re always looking for volunteers with skills in web programming, data wrangling, graphic design, and fun :-) The TransitMatters Labs team is reachable at labs@transitmatters.org. You can also follow or tweet at some of the team members who worked on this project on Twitter:

Austin Paul (@ajp5678)
Chris Schmidt (@crschmidt)
Preston Mueller (@mathcolo)
Nathan Weinberg (@Nathan_Weinberg)
Chris Friend (@friendchristoph)