News   Nov 12, 2024
 397     0 
News   Nov 12, 2024
 448     0 
News   Nov 12, 2024
 513     0 

GO Transit: Construction Projects (Metrolinx, various)

Screenshot_2024-08-30_150121.jpg
 
A good and interesting myth disspelled.

Not to stir the pot, but my (quick) take is West Harbour should be the future of GO train service in Hamilton from an efficiency perspective. It is the direct line to/from Niagara. Someday, if we ever get serious about achieving common goals of passenger and freight in this country, the Hamilton sub should be abandoned below the brow in favour of a bypass right adjacent to Hamilton Airport (to enable direct or indirect rail-to-air freight). The lower Hamilton sub can then be used as a light rail line between some appropriate point east in the city and Bayview Junction / Aldershot.
When you say "below the brow" can you be more specific for those of us less familiar? The topography in that area is pretty challenging, and the sprawl severs a lot of potential options. Also, how does CP access Hamilton's industrial area and where does its intermodal yard near McMaster go?

1725128716675.png
 
Hmm toronto sun coming out with a useful article? colour me suprised


This is actually interesting, though, query in what time frame those 12 trains exist? 12 more at once? 12 more trains per hour?
Speaking with Niko Warbanoff, the CEO of Deutsche Bahn’s international operations, the promise is clear. He says that by applying new IT, built around industry standards, there will be 12 more trains available to service commuters without actually adding any cars to the rolling stock of the Go Train system.



“So, one result will be, and we know that already today, that by using the new IT, that we will be able to have 12 additional trains per day, more on the network than today, and this increase in capacity is without any changes in the infrastructure or anything else,” Warbanoff said during an interview in Toronto last month.
 
This is actually interesting, though, query in what time frame those 12 trains exist? 12 more at once? 12 more trains per hour?

It is usually hard to decipher jounalists' explanations, but I read this to say that DB believes the planned system can be operated with 12 fewer trainsets than ML would have used, once certain improvements are made. That frees up an awful lot of equipment for further service additions.

- Paul
 
It is usually hard to decipher jounalists' explanations, but I read this to say that DB believes the planned system can be operated with 12 fewer trainsets than ML would have used, once certain improvements are made. That frees up an awful lot of equipment for further service additions.

- Paul
I know it is customary on here to assume Metrolinx (and VIA, and Transport Canada…) are a parcel of idiot know nothings, but is this actually plausible?
 
I know it is customary on here to assume Metrolinx (and VIA, and Transport Canada…) are a parcel of idiot know nothings, but is this actually plausible?

LOL Assumption, or consensus ?

I was amused at how the often strident Lilley walked a fine line, so as to not to throw shade at ML in a way that could be blamed on Ford.

The biggest IT enabled efficiency gain I can think of would be the number of trainsets out of service at any time for maintenance, rather than the number moving on the network. There may be maintenance practices that could reduce that (eg not taking a trainset out of service because one car needs work, or having to bring trainsets from layover yards to Willowbrook instead of doing things in the field locations, or changing service intervals based on better recordkeeping and attention to failure rates, or having to sideline a trainset until parts or workers are available ......)

Wait until the cab car enthusiasts find out that DB doesn't see any need to rush those recently refurbished cab cars into service after all.... ;-)

I do wonder about the number of trainsets that sit in layover yards at mid-day. Perhaps different scheduling processes could keep more in service, or change the deployment somehow..

- Paul
 
Last edited:
I do wonder about the number of trainsets that sit in layover yards at mid-day. Perhaps different scheduling processes could keep more in service, or change the deployment somehow..

- Paul
This is what my first thought was about crew scheduling and dispatching services perhaps on in-house built IT systems

I though of it because of recent issues with airlines and their systems developed in-house long ago which were considered a money saver at the time (90's/00's), but in recent years those systems have plagued some airlines that admitted they can never "catch up" to problems because the systems of booking crews and changing flights are so old, so slow and rely on so many manual inputs that even minor incidents cause cascading delays.

More importantly, the software cannot be upgraded because the code is old with so many different people's work added on to it over 20+ years that it requires weeks of work to make sense of to process even a minor change that won't have unintended consequences, or cause the system to stop working entirely, so they simply stop updating it all together.

So maybe DB just has more modern software that can have the scheduling of both crews and trains ported over easily.

 
Last edited:
i feel like this transition will have a ton of delays and disruptions which will be forgiven because DB is new and German, but if Metrolinx had tried to introduce the same software and practices with the same result but also the same benefits after the few weeks of pain, it would end up as the “hello, Human Resources?!” meme
 
i feel like this transition will have a ton of delays and disruptions which will be forgiven because DB is new and German, but if Metrolinx had tried to introduce the same software and practices with the same result but also the same benefits after the few weeks of pain, it would end up as the “hello, Human Resources?!” meme

There's often benefit in bringing in fresh eyes.... while I agree with Lilley that ML's operational performance is already pretty good, there are always things that become ingrained habit that become difficult for the old guard to challenge or move away from ( cough TTC cough).

New management generally is given a bit more leeway to act - they've been given the keys to the truck, so the top of the house has to let them take their best shot. That may be frustrating to the old guard (who may have wanted to make improvements, but weren't allowed to, or weren't given the same funding) but that's just how corporate life works I guess.

The measure of whether OnExpress does things better won't be taken for several years - any newcomer to a job or business will blow their own horn about how they walked in and things got better.... more likely there will indeed be a period of discovery and things that may work badly for a time before they are adjusted to work well.

I share the skepticism about IT based "solutions"..... too many experiences with software that was bought because it was working perfectly somewhere else.... but there were just enough differences and imperatives in the new environment that led to the software not meeting expectations, or requiring costly software revisions before it fit the new context. IT implementation is seldom a silver bullet, but maybe DB have some processes that are worth adopting.. It will be interesting to watch.

- Paul
 
This is what my first thought was about crew scheduling and dispatching services perhaps on in-house built IT systems

I though of it because of recent issues with airlines and their systems developed in-house long ago which were considered a money saver at the time (90's/00's), but in recent years those systems have plagued some airlines that admitted they can never "catch up" to problems because the systems of booking crews and changing flights are so old, so slow and rely on so many manual inputs that even minor incidents cause cascading delays.

More importantly, the software cannot be upgraded because the code is old with so many different people's work added on to it over 20+ years that it requires weeks of work to make sense of to process even a minor change that won't have unintended consequences, or cause the system to stop working entirely, so they simply stop updating it all together.

So maybe DB just has more modern software that can have the scheduling of both crews and trains ported over easily.

The term you are looking for is "brownfield" vs "greenfield"

Granted metrolinx probably built their systems in 2012/2013 so it's not that bad but for an org of that size, I'd bet there are legacy things they would love to be able to replace.
 

Back
Top