General MBTA Topics (Multi Modal, Budget, MassDOT)

Re: Driven By Customer 'Service' Parte Dos

It took me exactly 45 minutes to go from Lynn Station to the meetup at Beat Brasserie last night. I was rather impressed. Now if only we had some DMU's to make this possible more often.

You did
CR from Lynn to North Sta
CR from North Sta to Porter
RL from Porter to Harvard right?
 
Re: Driven By Customer 'Service' Parte Dos

It took me exactly 45 minutes to go from Lynn Station to the meetup at Beat Brasserie last night. I was rather impressed. Now if only we had some DMU's to make this possible more often.

I do North End - Lynn as a reverse commute every day. It's incredibly easy. It'd be even easier with the DMUs. Call me crazy, but if they could just get the trains running more frequently, Lynn is the new Chelsea, Chelsea is the new Somerville, etc. etc. etc.
 
Re: Driven By Customer 'Service' Parte Dos

I do North End - Lynn as a reverse commute every day. It's incredibly easy. It'd be even easier with the DMUs. Call me crazy, but if they could just get the trains running more frequently, Lynn is the new Chelsea, Chelsea is the new Somerville, etc. etc. etc.

DMU's not necessary to make something happen tomorrow strictly frequency-wise. Eastern Route service is already more frequent than any other commuter rail line at peak. Stiffen it up off-peak and in the reverse commute direction with and you can shortcut its transition to true-blue Indigo without waiting arms-folded for 7 years for new vehicles to get on the property or 5 years for them to shuffle paper doing an obligatory study on a route where obligatory studies haven't been formally done before.

Indigo is still the goal you're ultimately working towards, but unlike Fairmount where you have to beat the T into submission to start stepping up service with any useful starter frequencies...on the Eastern you're already 'born on first base' so-to-speak with a frequency-dense commuter mainline. It's less of a reach to dip toes in the deep end with more reverse-peak and off-peak frequencies when peak-direction frequencies are already more or less there. So given that the paper-pushing and wait for vehicles is frozen at a more or less static 5-7 years (if and only if they get started), the 'bridge era' route-priming possibilities using conventional commuter rail are a bit less daunting on sunk costs here.


About the only physical decision they'd need to hedge on is picking Salem and not Beverly as the short-turn destination.

-- 1) The single-track mainline platform pinch at Salem is going to be a constraint because they dumped all the money into that white elephant parking garage instead of more track capacity. So you're going to instead want to reinstate the Peabody Branch wye track out the tunnel onto the provisioned easement the new station leaves, and stick a 4-car platform on it to steer clear of the mainline platform. 3-track North St. freight yard a few hundred paces west of the station where Bridge St. parkers semi-legally park on the grass then makes for a quick-and-easy layover yard. It's just going to be cheaper that way vs. landscaping the hillside and shivving in an incredibly tight switch to get facing mainline platforms. The time for doing that within-cost passed when they went bonkers on the garage.

-- 2) Beverly swing bridge has a lot of summertime openings for boat traffic on the Danvers River. Coinciding more with the off-peak because that's when the rec and amateur fisherman traffic is highest. Not that you can't run Indigo frequencies around that ho-hum number of openings; we aren't talking the NEC in Connecticut here. I'm just not sure you'd want to trust the T and Keolis to not over- over- pad the schedule to absurdity around Beverly Draw and wind up with best-case frequencies way too choppy to resemble clock-facing. All of Beverly's buses hit Salem station, so they're not compromised on transit accessibility if frequencies--and all-day regularity of frequencies--is the rule.

^^Given the expense involved covering their mainline capacity brainfart at Salem and institutional ops reluctances that would need to be overcome re: the bridge, this is what not only ends up being most cost-effective and fastest-start way for all-day schedule increases...but also inoculates best against "the T being the T" re: trying new anythings.




The big catch--and big likely letdown--is that there's no way forward on the Eastern Route without addressing the fare Zone layout. Not on real Indigo, and not even on improved conventional CR. Newburyport/Rockport is far and away the most skewed rise in fares from the terminal on the entire commuter rail system, and the most transit-dependent of North Shore riders get ripped off harder than anyone else in spite of their better frequencies. Riverworks and Lynn are the closest Zone 2's to Boston on any line. Swampscott is the system's closest Zone 3. Beverly is the only Zone 4 residing inside 128. And Montserrat and N. Beverly (which is technically at 128) are the closest Zone 5's to Boston...equivalent to Framingham, North Billerica, Norfolk, and Andover. That is nuts.

The T makes nicer peak-hour farebox recovery on the Eastern Route than any other line because of this skewed fare setup. So what's their motivation to change it? To have any way forward on Indigo here they have to be willing to take the risk of re-zoning all of Newburyport/Rockport top-to-bottom for much slower Zone rise inside of 128. Such that Riverworks and Lynn are 1A's like Chelsea, Swampscott no higher than a 1, and Salem absolutely no higher than a 2. Then Beverly set no higher than a 3 because Salem's a 2, and the first intra-Beverly stops on the branches probably no higher than a 4 because Beverly's a 3. Then leaving Hamilton-Wenham (5) to Newburyport (8) and Manchester (6) to Rockport (8) as-is.

This entails taking an intentional loss on that lucrative peak-hour farebox recovery for the 7-10 years it would take amidst a transition to full-blown Indigo frequencies to build the ridership to the point where farebox recovery builds back to par from total fare-paying bodies instead of premium per fare-paying body. And they have to be brave enough to stick to this plan for the long-haul without soiling their knickers and backtracking on it at the very first short-term budget shock. Like they have repeatedly backtracked on pinning the Fairmount rollout to a calendar.


Do you have confidence they'll be brave enough to do that? I very seriously doubt it. And that pessimism stares right back at you on the 2024 map they circulated stopping at Zone 2 Lynn. It doesn't even feign interest in the system's single busiest non-terminal station, Zone 3 Salem. Or the needs of every bus route flanking Swampscott and Salem stations en route to Lynn and Wonderland. The service is useless if it stops at Lynn, because the only folks who get "Wow!" levels of new transit convenience are those in walking distance to Central Square. That's not going to be enough to turn Lynn into Somerville. Lynn is even more of a bus town than Somerville...which is very, very much fueled by its buses and bus transfers. The entire 4xx division of the Yellow Line is anchored out of Lynn. No poor sap who's paid a bus fare for a long ride from Marblehead, Salem, Saugus, or the distended western parts of Lynn ringing Lynn Woods are going to get off the bus and board a Purple-shaded anything at Lynn when 5 more minutes in that seat gets them to the Blue Line, a subway fare with free transfers downtown, and subway frequencies.

Stopping at Swampscott and Salem with same frequencies and equitable fares? Way different story. Stratospherically different results. That would actually short-circuit the bus trips and distance traveled in a slow and uncomfortable bus, pool riders onto the trains, get riders willing to pay a Zone 1 or 2 fare with a double-dip onto the subway at North Station on the pure convenience of it all, and substantially increase the flexibility of the entire North Shore bus system by not having every route have to be predicated on a brittle schedule all the way to Wonderland and/or Haymarket. Lynn may be the main population center in-play, but the buses are the linchpin of any North Shore transit solution. BLX or this...BLX and this.



Their fear of altering the Zone fares makes Indigo-Lynn on the '24 map defective by design. Nobody changes their commute if Lynn is the arse-end of their rubber-tire trip because the same Wonderland funnel continues unabated. Walkup boardings at Central Square just aren't a big enough share of the pie vs. the further-flung Yellow Line routes. Then you get officials wondering why trains aren't filling up despite those wonderful increases in frequencies, conveniently forgetting everything every prior North Shore transit study told them about commute patterns. And it ends up becoming a self-fulfilling prophecy of service cuts waiting to happen

Not only does it HAVE to be Salem and a Zone recalibration, but if they stick to the 2024 map and Lynn verbatim I would think long and hard about outright taking that route off the map and substituting Reading (Zone 2) as the first northside route to roll out. That's how much cut-and-run risk the the systemwide Indigo effort incurs if they roll out a defective-by-design service like that. Just punt it until this proposal gets sent to finishing school. It's the slam-dunkiest of slam dunks if it's an affordable ticket all the way to Salem, but gerrymander it in pants-crapping fear of touching the Zones like that '24 map stubbing out at Lynn...and it risks taking the whole map down with it over penny-wise/pound-foolish shortsightedness.
 
Re: Driven By Customer 'Service' Parte Dos

The big catch--and big likely letdown--is that there's no way forward on the Eastern Route without addressing the fare Zone layout.

Yeah, down at Central Square every morning and evening, there's about 3x as many people waiting for the bus than the Commuter rail. And it's not because the bus ride is nicer. Especially in Lynn, the difference between a $70/month links pass and a $198/month zone 2 is huge.
 
Re: Driven By Customer 'Service' Parte Dos

^ Generally, Indogo service is for the "inner" part of these lines anyway: Serving stuff well inboard of the Salem tunnel, I would picture a train ping-ponging Lynn<->NS on some short interval to bolster the frequencies for Chelsea, Revere (infill) and Lynn (re-zoned to 1A) and let the outer stops keep their existing service.

Similar to how increased Lowell Line service hypothetically runs only Anderson Woburn <-> NS.
 
Re: Driven By Customer 'Service' Parte Dos

^ Generally, Indogo service is for the "inner" part of these lines anyway: Serving stuff well inboard of the Salem tunnel, I would picture a train ping-ponging Lynn<->NS on some short interval to bolster the frequencies for Chelsea, Revere (infill) and Lynn (re-zoned to 1A) and let the outer stops keep their existing service.

Similar to how increased Lowell Line service hypothetically runs only Anderson Woburn <-> NS.

It's not going to work that way because of the way the buses work. Everything that goes into Lynn terminal proceeds to Wonderland. Because BLX never came. Frequencies and fare structure ALWAYS rule rider decisions over the most convenient seat. They stay on the bus no matter how often Indigo runs, they pay a subway and not Zone 2 fare, they get higher Blue Line frequencies, and they get free inter-line transfers without a douple-dip. Nobody who takes a North Shore bus is going to make their rail transfer at Lynn commuter rail station regardless of what pulls into it. Nobody. Their asses may hurt from sitting in the same seat from Salem or Marblehead, but what's an extra 7 minutes of numbing buttocks when they don't need to give up that seat and get all of Blue's advantages when they disembark. Faster 3-stop trip to NS ain't gonna do it when the best-of-the-best frequencies won't match Blue and the fares won't be anywhere near as good as bus-to-Blue.

Walkup crowds to Central Square are the primary audience, because they haven't already boarded a bus. Walkup crowds at Central Square with Lynn at the end of the line are not anywhere near enough to sustain it. I would even venture that most of the ones who have to get to Chelsea--the one destination that Indigo terminating at Lynn does open up that was never easy to access by bus before--are also going to prefer Blue and a transfer to Silver Gateway in large numbers over the seemingly more direct Indigo route. Maybe not a huge majority, but slight...because they're conditioned to think that bus is cheapest, and don't want to do math in their head on interzone fares. It sets up a self-fulfilling prophecy.

Go to Salem and you're no longer talking buses that need to make 100% of their runs to get anywhere. Buses that make 100% of their runs to Lynn narrow the inconvenience of staying on 5-7 more minutes to Wonderland to point where the fare + frequency advantage outslugs it. Not so if you're coming from Peabody, Danvers, Beverly, or Salem and can take a really short trip to Salem instead of staying on another 45 minutes to Lynn. Not so if you're coming from Marblehead and can cut your trip short at Swampscott. And definitely not if the Zone fares are recalibrated so 1A goes out to Lynn or further and Salem has an absolute ceiling of 2. That even gets the Lynn<-->Chelsea link firmly established on Indigo instead of the less logical bus<-->Blue<-->Silver. This is maybe one of the best Indigo routes of all at Salem, with recalibrated fares. It is one of most tragic first-cuts in a budget shortfall if it's Lynn-only and all mainline stops out to Beverly stay this high off-scale for the commuter rail entire system on fare equitability.

They have to prove they're brave enough to trade half-decade or more in cumulative farebox recovery losses with cheaper 9-5'ers by recalibrating the zones so they can achieve decade-plus cumulative farebox growth from backfilling with more all-day paying bodies period. And stick to that plan without getting skittish at the first budget shock. Because it is a 10-year plan. Not a commitment you can have high confidence in them keeping. It would be awesome if they did, because this would be such a transformative thing at the right distance with the right fares. It would encourage BLX buildout, encourage way better and more comprehensive bus coverage of the whole North Shore, and result in one of the more tangibly dramatic diversions from cars of any one region in the district.

But it takes some brass ones to enact the plan that intentionally incurs some farebox recovery losses and stick with it to the whole duration for paydirt. It's hard to do that with an agency that almost since inception has governed itself crisis-to-crisis. There's unfortunately no half-solutions here, no "Let's poke to Lynn and see what happens, then maybe other enhancements are negotiable." No, that's defective by design and makes it as likely or more that the plug gets pulled on the whole thing. Which is a senseless waste. This is jumping in the deep end, and not hesitating to make that jump.

--------------------------------------

As for "hypothetical" Lowell service, that's got some real caveats they're not taking into account.

1) GLX so completely and utterly changes the game that everything they think they know about Medford and Winchester demand is going to need a major re-examination after rapid transit opens. Even though those first 3 Lowell stops are not directly served by the Green Line.

West Medford has the 94 feeding it out of Davis, passing by College Ave. en route. The 80 Davis-College Ave.-West Med-Arlington Center is a block up the street from the commuter rail station. Both routes are very fast into Davis, but could stand to run a little more frequently. The second GLX College Ave. opens for business the ridership on these two routes EXPLODES out the wazoo being a two-line rapid transit link. And demands way higher frequencies. GLX is going to do that to a LOT of bus routes. Those are how big its coattails are. In Somerville and Medford.

If the Route 16 extension ever happens, make that 3 rapid transit transfers on a brisk on-the-clock trip from West Med (to go along with the close walking distance). If the bus frequencies post-GLX scale up to 10-15 minutes all-day to satiate demand, with those routes graduating into the upper division on ridership, the same frequency + fare portability > one-seat advantage rules over West Med commuter rail. You're going to see a major shift away from it, even at a Zone 1A, because of those golden-rule factors. It's a well-patronized commuter rail stop and will continue to have its place, but the mode share will shift in a major way away from it. And that's not a bad thing...that's "happy trails" for all involved who get exponentially better transit options in the aggregate.

Now, project that bus transformation out to the next 2 stops. Wedgemere and Winchester have the 134 out of Medford Square, and Wedgemere *sorta* has the 95 out of Med Sq. terminating in no-man's land between West Med and Wedgemere. They're left out of the College Ave.-Davis connector, though, which is probably a shortfall that needs correcting right now. But what happens when GLX starts and the bus routes go topsy-turvy? There's going to be tons of demand for a half-and-half variation of the 94 Davis-College Ave.-West Med and 95/134 continuing up Playstead Rd. and Main St. That neighborhood around Main is way, way too dense to send to Medford Sq. exclusively, and they are not in commuter rail walking distance because of a street grid broken up by the conservation land. They badly need a route to College Ave. and Davis with rapid transit connections. So you are going to most likely get a bus route up Main that hits Wedgemere. And a bus route that either continues and hangs a right on Church St. to Winch Ctr. or takes the 134's path up Mystic Valley Parkway to that station. Again, you'll be doing this whether there's Indigo or not because the Red-Green super-routes beckon way too hard to the CR-inaccessible neighborhood in between, and if you get that far the only reasonable place to tie it up in a bow for a turnback and idling spot is Winch Ctr. Which now means the same frequency + fare portability > one-seat golden rule is now in effect for the first THREE Lowell stops, not just West Med. Indigo's starting to look awfully duplicate here.



2) Anderson. The state's trying way too hard to make Anderson "REGIONAL TRANSPORTATION CENTER" a thing. A destination unto itself. Anderson's never going to be a destination or TOD paradise. It's surrounded by trucking, light industry, and raw materials (stone, etc.) processing plants. Because there is no more valuable place in Metro Boston to be situated for truck shipping and aggregates distribution than 128 @ I-93. Same thing for Mishawum, which they have been trying to make a 'thing' for 30 years now. To the point where it's time to stage an intervention about their trying to make Mishawum a 'thing'. It's a big-box Mall. 128 @ 93 is a fine place for a big-box Mall. For maximum revenue there's few better places.

It's not Westwood. It's not the Woburn equivalent of Assembly-in-the-making. Anderson is a parking sink. Some locations a parking sink is the best use of a site, and parking sink is probably the best possible thing you should have here. Suck up the 9-5'ers from both Exit 35 on 128 and 37C on 93, keep them the hell away from the Reading interchange, put them on nice free-flowing Commerce Way where the traffic doesn't bother anyone, feed them one of commuter rail's fastest and most frequent schedules, throw in a well-patronized Downeaster stop, and throw in a Logan Express location. That's what Anderson does; it pools suburbanites and 9-5'ers. It's not a development narnia. It's not an all-day destination. It's going to be quiet with a full lot in the afternoon. The only thing it really needs is to have the missing west entrance to New Boston St. finally completed, and convenient commute-hour bus service to Burlington and the office parks that ring 128.

Indigo here is going to disappoint on the off-peak, because it tries too hard to make Anderson into the all-day 'thing' that it's not, which the land use doesn't support, which the land use doesn't need to support because the existing land use is probably the best land use. For whatever reason the "Transportation Center" branding and 30 years of trying to make lemonade from lemons at Mishawum has reinforced some fruitless stubbornness. "MUST...make...Woburn...parking...sinks...a...thing!"


What does that leave if not West Med/Wedgemere/Winch Ctr where buses and GLX change the game, and Mishawum/Anderson which are so heavily skewed to 9-5'ers? That badly-needed infill for Woburn at Montvale Ave.? Sure...but I don't think you can hang a full Indigo service plan on that one alone when the buses to rapid transit are taking their share of the first three stops and all-day demand craters past here. Backstopping the buses and the 9-5'ers with some extra service for pure convenience. I guess...but there are many worthy Indigo candidate routes, so is that the best use of one of only a handful of bullets in the chamber?




How about just making a trade? The Haverhill Line CR schedule goes back to its pre-1979 routing via the NH Main, and Reading becomes an exclusively Indigo route. It has the neighborhood walkup density. It has decent amount of pre-existing duplicate bus density paralleling it 1-2 blocks away on Main St. all the way from Malden Ctr. to Reading; that's a strong hint at under-served demand when none of it is hitting any non-CR destinations like that post-GLX world in Medford. It has a prime 128 site at Quannapowitt Pkwy. for an infill park-and-ride with lots of existing and potential mixed-use adjacent development: today with corporate business parks, shopping center, medical center, hotel, and walkup residential with bus access ringing the whole south half of the lake....tomorrow with something nicer adjacent to the would-be stop than Subaru of Wakefield.

THERE'S your 128 stop that can anchor itself with a mixture of 'destination' development and varied all-day demand. Leave Anderson to fill up with 9-5'ers. Certainly if you run full-blast and ever-escalating Lowell and Haverhill peak-hour trains that sprawling lot in Woburn is going to fill up to the max and leave little room for the off-peakers. So direct the off-peakers to Quannapowitt, and run those Burlington buses to ping here too where the off-peak travel times on 128 aren't that bad.

Is that a better use of valuable Indigo bullets in the chamber than backstopping Lowell just because? You still get best-of-both-worlds 128 access. You still enhance both sets of the inner-burbs' transit access to very significant degree between bus-to-rapid transit and Indigo rail, instead of picking one corridor as winners and one corridor as losers. And you still stiffen up NH Main frequencies by a lot with Haverhill trains that now make a tolerable hour to Haverhill and stimulate a lot more native ridership. Plus Lowell (along with Worcester and Providence) is the one line capable of serving moderate off-peak conventional schedules as a regional intercity destination, so that's not going to be a dead midday by any stretch.

I'd honestly prioritize Reading first and split the difference on multi-modal resource allocations. Only one corridor gets Indigo trainsets, but both get the super-sizing they deserve.
 
Re: Driven By Customer 'Service' Parte Dos

where-is-essex-street.jpg


Despair.
 
Re: Driven By Customer 'Service' Parte Dos

I saw that, too. Un-fucking-believable. How did that not know where that was?
 
Re: Driven By Customer 'Service' Parte Dos

I have trouble remembering names, but I would just look up Google maps to grab the name and intersection rather than ask. Of course, that assumes the Twitter guy recognizes the street at all.
 
Re: Driven By Customer 'Service' Parte Dos

That's what happens when you have the Citizens Connect front line run by college interns who have been in Boston for about 2 days.
 
Re: Driven By Customer 'Service' Parte Dos

That bus lane is a complete joke. I work around the corner and am constantly angered by the site of silver buses stuck behind cars backing up the lane.
 
Re: Driven By Customer 'Service' Parte Dos

They should also have BTD properly enforce the (lack of) parking and loading zones on the south side of this street. Cars will often avoid the right lane and just ride the line of the bus lane enough to obstruct buses.

The average width of Essex Street is about 15m according to my rough measurements in Google Earth. I'd love to see a physically separated bus lane with cycle track:
QlPmivQ.png
 
Re: Driven By Customer 'Service' Parte Dos

Yeah I tested it for real in Kenmore today -- Transit App showed a B coming, and voila, it showed up right on the dot.

Although now with the D power problems it's showing like 7 trains backed up around Kenmore for the B... they were re-routing stuff in Kenmore, a big mess.
 
Re: Driven By Customer 'Service' Parte Dos

<pigsflyingoverfrozenhell.gif>

Happy day at last, yet anticlimactic that it's just turned been on without any dignitary ribbon-cutting to speak of. Also, I wonder if the work that was required in the Central Subway to activate tracking explains why Kenmore's next-train signs and announcements have been blank and silent, respectively, for months now.
 
Re: Driven By Customer 'Service' Parte Dos

I agree, they ought to make some noise about it, it's hugely helpful.

Ah well, I'm happy to have it online, I really like having this app on my phone.
 
Re: Driven By Customer 'Service' Parte Dos

It's probably not ready to go on the big screens so they won't announce it yet.

They sent a "heads up, something's coming" email to the developers list but that's it.
 
Re: Driven By Customer 'Service' Parte Dos

The area around Boylston and Park isn't fully done yet, because of the four-tracking and the loop making things difficult. I suspect we'll get an announcement when that's completely done.
 
Re: Driven By Customer 'Service' Parte Dos

The area around Boylston and Park isn't fully done yet, because of the four-tracking and the loop making things difficult. I suspect we'll get an announcement when that's completely done.
Over on Railroad.net, Stefan W offers more details on his latest theory for a Park-to-Arlington blind spot:
I've figured out that the MBTA's live tracking isn't online yet between Arlington and Park Street. I've observed eastbound trains "piling up" at Arlington, and westbound trains "piling up" just before Park Street. In both cases the trains will jump across that route section and appear with live position data on the other side. This tells me that the AVI sites and/or tie-in to the signal blocks isn't quite done yet.
 
Re: Driven By Customer 'Service' Parte Dos

Congratulations to the MBTA and Metro Boston: Boston among the metros with the largest decline in auto commuting between 2006 and 2013 (I some other significant share of the credit goes to the increase in bike commuting in that time too, but as discussed in the Biking in Boston thread, bikes and transit work together, and the T's increasing ridership shows it)
CMYTvaZVEAAZfl2.png:large

Car commuting fell from 78.9 to 75.6 percent of all commuting (a loss of 3.3% in share represents a 4.2% shrinkage in car-use).
 

Back
Top