My understanding is that simulated service began on November 1, which would be 11 months this coming Sunday.To my understanding, only 10 months and a bit have passed since early-mid November 2022 when the simulated testing began on the Medford Branch.
Btw, fixing a problem like this should take an about hour for a well trained crew.
Source rail is all pretty generic and bulk-supplied. The only differences is that RR rail comes in 1/4 mile ribbons to be welded together, while rapid transit rail comes in 800 ft. (or .15 mile) ribbons to be welded together...the shorter lengths so that the rail drop can navigate tighter rapid transit turning radii. Commuter rail generally uses 136 lb./yd. weight rail (sometimes as low as 100 lb./yd. on turnouts, but the T sticks with the 136 lb. mainline & freight 'superset' weight for bulk ordering purposes). Rapid transit standardizes on 100 lb. rail pretty much everywhere worldwide. Bulk rail usually ships at a RR wheel profile (because that's the majority of worldwide volume for rail, and thus fetches the best bulk rate), and for rapid transit installs they simply run a rail grinder over it to change the profile to rapid transit wheels. That ends up easier than buying specialty-ground bulk rail, so most rapid transit systems apply the re-grinding post-install. The specialized Loram rail grinders were very busy on the GLX corridor in 2021 and early-'22 working over the track before the first test trains went on the corridor.
F-Line, sorry this upsets you so much. The situation is dire and you don’t seem to get it.
The reason why Eng's promise to provide a timeline on slow zones failed to deliver was addressed here:The latest episode of the Horse Race podcast has a discussion about the T’s problems prompted by the GLX storm. In it they mention Eng’s promise at his introduction to publish details about the slow zones and plans to fix them. Somehow that has also been memory holed in the ensuing months.
Despite Eng’s buoyant optimism, some of his plans have already been thwarted. On his first day as general manager, he announced the T would soon publish dates of when each speed restriction on the subway system would be lifted.
Soon turned into never.
Each shutdown for track repairs, he said, requires discussions with elected officials and local business owners, and compliance with new federal directives to keep T workers safe, which means his original vision for radical transparency on slow zones is impossible. New slow zones are now cropping up faster than the T is eliminating them, and sometimes crews are discovering more work is required than originally anticipated.
The reason why Eng's promise to provide a timeline on slow zones failed to deliver was addressed here:
Why is Eng getting permission from LOCAL BUSINESS OWNERS to do track work? What the fuck kind of logic is that?The reason why Eng's promise to provide a timeline on slow zones failed to deliver was addressed here:
Because shutdowns are disruptive and affect everyone in the area impacted, both residents + businesses? Having discussions with them and trying to time them for the least problematic period for them is....how any responsible entity would (or should) act?Why is Eng getting permission from LOCAL BUSINESS OWNERS to do track work? What the fuck kind of logic is that?
None of that really explains why they can't provide a timeline for fixing slow zones. I mean, they can't give a timeline because they have to follow safety protocols? That makes no sense.The reason why Eng's promise to provide a timeline on slow zones failed to deliver was addressed here:
That makes sense - they wrapped up this latest round of Braintree branch work two weeks ago and last couple weekend closures have been more about prep work for the Ashmont surge. I’m curious to see how much of the current Ashmont slow zones actually end up being fixed during the surge - there’s about 16.5 minutes of current slow zones there, hopefully most of those go away.Slow zones have plateaued on the RL, at a higher level than the July 2023 low point.
"We have to fix the train. WHEN IS BEST FOR YOU!?"Because shutdowns are disruptive and affect everyone in the area impacted, both residents + businesses? Having discussions with them and trying to time them for the least problematic period for them is....how any responsible entity would (or should) act?
Yes, that's pretty much exactly how the concept of scheduling works."We have to fix the train. WHEN IS BEST FOR YOU!?"
Because they don't want to guarantee (At least in the eyes of the public) that work will be done several months in advance. Prematurely announcing closures could cause any number of problems from unneeded external pressure to meet targets, frustration and anger from local communities if they have not had time to take into account local events, and general annoyance if some unforeseen circumstances cause schedules to change. If they were to announce work between Forest Hills and Ruggles 3 months in advance for example, but then more urgent repairs needed to take place between Alewife and Porter requiring the scheduled work to be canceled, now you have local politics getting involved, and people start accusing the MBTA of putting wealthy Cambridge in front of poorer Roxbury for improvement works, regardless of the importance of the work. This can all be avoided by playing it safe and announcing works only for the near future.None of that really explains why they can't provide a timeline for fixing slow zones. I mean, they can't give a timeline because they have to follow safety protocols? That makes no sense.
The T does actually have an internal schedule for when work will be done. They could make that public.
Absolutely, those are the downsides of publishing a track work schedule. But then why did Eng promise to publish a schedule of when track work would get done? And why did he change his mind? He knew everything you're saying when he made the promise and nothing really changed between then and his reneging.Because they don't want to guarantee (At least in the eyes of the public) that work will be done several months in advance. Prematurely announcing closures could cause any number of problems from unneeded external pressure to meet targets, frustration and anger from local communities if they have not had time to take into account local events, and general annoyance if some unforeseen circumstances cause schedules to change. If they were to announce work between Forest Hills and Ruggles 3 months in advance for example, but then more urgent repairs needed to take place between Alewife and Porter requiring the scheduled work to be canceled, now you have local politics getting involved, and people start accusing the MBTA of putting wealthy Cambridge in front of poorer Roxbury for improvement works, regardless of the importance of the work. This can all be avoided by playing it safe and announcing works only for the near future.