The big untapped potential in my mind is the possibility of the commuter rail route offering a faster alternative than the R-Line. During the morning rush, Pawtucket Station -> Kennedy Plaza takes 22 minutes on the R Line. The commuter rail should (see below) take 6 minutes, and then add a 7 minute walk from the train station to Kennedy Plaza (though note that an increasing number of bus routes through-run to the station, potentially eliminating the need for the walk), which comes out to 13 minutes.
Particularly with the Downtown Transit Connector in place (providing modestly high frequency cumulative service between Providence Station, downtown, and the Hospital District), that seems like there's real potential for faster journeys. You would need a significant increase in rail service to make it competitive, but the route is short enough that you might be able to achieve 20-min headways with a single trainset and a slightly compressed turnaround time. (Assuming you could get Amtrak to agree to the dispatching impact, which would be non-trivial.)
Looking at the schedule, I am confused. Northbound journeys are pretty consistently timed at 6 minutes. Southbound journeys -- even on weekends -- are timed at anywhere from 12 to 15 minutes, which is 200-250% as long as northbound. Is there any public explanation for this?
Of course they do...TransitMatters takes the T to task over the Widett Circle layover yard proposal. https://commonwealthmagazine.org/opinion/mbtas-widett-plans-dont-make-sense/
I'm glad that Transit Matters exists, and I admire a bunch of what they do. Someone needs to hold the T accountable. Because of that, I'm hesitant to criticize. But whenever the discussion topic involves maintenance facilities, layover yards, platforms and sidings, it becomes obvious that while they are good at abstract analysis (data plots of slow zones, high-level calculations of capacity, etc.) they would really benefit from a deeper understanding of how rail ops work in the real world - and by that I mean not just janky USA networks, but also the Euro networks that Transit Matters adores and frequently cites superficially as examples.
We can all agree that the T should have more "off-peak" services and that the T's plans shouldn't be built around having a huge proportion of the fleet idle at midday. But that doesn't mean that you don't need layover yards or (especially) maintenance facilities. Newsflash: trains, even shiny new EMUs in world class systems, often break down. It rarely makes economic sense to run systems 24/7, and it also doesn’t make sense to have all of your layover capacity OR your maintenance capacity at the far fringes of the network, limiting the ability to deploy resources quickly in the event of a breakdown or outage.
Any sober analysis of the T would conclude that it’s short on both the maintenance AND layover capacity required even to cover its near-term ambitions, and the T’s facilities are woefully short of what would be required to support a network as extensive and visionary as the one that Transit Matters proposes. So where is that capability going to go, boys? If not Widett, where? Widett may not be a perfect location, but in the real world, there are a limited number of possible locations close to key nodes of the rail network with sufficient size and in an appropriately industrial zone buffered from NIMBYs.
Transit Matters frequently makes reference to Europe, but I’ve never seen any evidence that they actually understand how a range of benchmark European systems are configured. Let’s take Munich: Munich’s S-Bahn is a pretty decent analogue to the electrified commuter rail network that we’d dream of having if/when North-South Link is built. As Munich’s population and commuter rail network has expanded, they’ve repeatedly needed to increase their maintenance facilities and storage capacity. The main maintenance facility is a whopping 6 kilometers (4 miles) from the center of the City (Marienplatz). They are short of capacity again, so they are planning another facility almost as close. A huge percentage of the sidings where trains are idled are also relatively close to the center of the network, on either side of the tunnel that runs under the center of the City. This is not by accident. They also have additional platforms at main stations (Hauptbahnhof and Ostbahnhof) that aren’t used for routine service but which come into play when things don’t go according to plan. Munich’s system is configured like this to promote reliability and resiliency, and ours should be, too.
Nor is Munich an outlier. Hamburg’s S-Bahn maintenance facility is only 8 km from Hamburg HBF. Zurich’s is even closer to city center. (For what it’s worth, Zurich also uses bi-level coaches to good effect … Transit Matters is intransigently dead-set against bi-levels because their spreadsheets tell them they require longer and less predictable dwell times, but the precise-to-the-millisecond Swiss seem to manage the tradeoffs just fine).
The Transit Matters team doesn’t seem to understand that even if a perfect-world calcuation suggests that if x units of rolling stock move every y minutes, a network can exist without extra platforms (no love for South Station expansion) or layover yards (no love for Widett), it doesn’t mean that would ever work in the real world, where oily parts and electrical bits fail unpredictably, weather periodically intrudes on ops, human labor isn’t infallible, and operators are obliged to wrangle with mixed fleets during long periods of transition that never really end. Any good system has a contingency plan for virtually every type of failure in any point of the network. My sense is that if the folks at TM actually spent a year working in the bowels of one of the complex European networks with the clock-facing schedules that they so admire as tourists, they’d return with a much greater appreciation for redundancy and an understanding of why investment can’t be limited to stringing up wires and buying some electrified rolling stock.
At the very least, Transit Matters would benefit from having someone like F-Line edit their copy and explain to them which of their assumptions are naïve and why some of their Pollyanna estimates are oversimplified. The frustrating reality is that they unwittingly undercut some of the good that they do in holding the often brain-dead and untrustworthy MBTA accountable and pointing the way toward a better future. Sure, 95% of the public will have no idea how to assess their proposals. But they make it too easy for MBTA brass and engineering geeks who understand a bit more about ops to dismiss them as a bunch of young armchair quarterbacks blogging from mom’s basement.
I struggle to understand why the Widett purchase is an issue worth burning advocacy time and ink to address – shouldn’t Transit Matters instead be hammering away much harder at the MBTA’s vaporware battery trains? I believe TM is on record stating that proven technology is “preferable,” which seems like the understatement of the century - I believe TM has subjected bi-level trains to much harsher assessment than vaporware trains. Is there an Elon Musk fanboi on the Board preventing you from taking a stronger stand? Or is the topic too technical for you to handle? This issue is far more important to your goal of short-term electrification than is Widett.
The great irony here, is that Tallguy is precisely that crazy guy who wants that cross-harbor RR tunnel.To set the record straight on a few other points: where did I suggest something that would cost BILLIONS? You must have me confused with that crazy guy in the North-South Link thread who suggested a second rail tunnel tube for the Eastern Route (which really would cost billions without providing essential redundancy).
The great irony here, is that Tallguy is precisely that crazy guy who wants that cross-harbor RR tunnel.
| 500 | 504 | 552 | 584 | |
---|---|---|---|---|---|
Worcester | 4:15 | 6:00 | 6:30 | -- | |
| all stops | all stops | express | -- | |
Framingham | 4:55 | 6:40 | 6:56 | 7:05 | |
West Natick | 5:00 | 6:45 | -- | 7:10 | |
| all stops | express | express | all stops | |
Boston Landing | 5:34 | 7:07 | -- | 7:45 | |
Lansdowne | 6:12 | 7:12 | 7:24 | 7:50 | |
South Station | 5:50 | 7:23 | 7:35 | 8:01 | |
| | | | | |
WOR-FRAM | 40 min | 40 min | 26 min | -- | 65% |
WNAT-BLND | 34 min | 22 min | -- | 35 min | 63% |
FRAM-BOS | 55 min | [43 min] | 39 min | 56 min | 70% |
WOR-BOS | 95 min | [83 min] | 65 min | -- | 68% |
| | | | | |
I was walking across the West Fourth Street bridge (looking south), so I'm guessing it was just part of an equipment move towards one of the maintenance facilities there, but it was interesting to see!