News   Nov 25, 2024
 240     0 
News   Nov 25, 2024
 428     0 
News   Nov 25, 2024
 483     0 

GO Transit: Service thread (including extensions)

Hate to break it to you but they've already deprioritized safety in the name of on-time performance metrics. Trains no longer hold at a platform if someone presses the priority alarm, too many false alarms they say. So now they are to get going first and then only once they've left the station will the CSA go and check things out. Sorry, but your heart attack or assult can wait people need to get home but hey at least you can text 77777 for help now in case you forget to call 911 🤷
This isn't specifically true.

There are some schedules that are known to be more full or troublesome than others. And those trains get two CSAs.

By having the conductor in the body of the train. It would seem the plan is to have the engineer operate on his own at the front with the cndr in the body. This is actually how CP and CN did it at the end of their tenures.
CP did do this for the last several years before they handed over the operation to Bombardier. CN, however, did not.

But GO wanted a more customer friendly approach when 'the Bomb' took over hence why they created the CSA position. OOI's contract proposal doesn't indicate that the CSA is a guaranteed position like Alstoms did, so the writing is on the wall. But it doesn't seem like they'll make the switch right away it seems that'll happen only after the next generation of equipment arrives, presumably equipped with in cab signaling.
It's more than just that. The CSA is not a running trade - therefore, it pays less, the hours-of-service restrictions are less onerous, etc. Back in the before times, that position was staffed by a second conductor, who had to deal with all of the same regulations and restrictions that the other two guys at the head end had to deal with.

Dan
 
This isn't specifically true.

There are some schedules that are known to be more full or troublesome than others. And those trains get two CSAs.
That's only for extra event trains or Niagara service. The vast majority of trains still have just the one CSA.

CP did do this for the last several years before they handed over the operation to Bombardier. CN, however, did not.
Just what I heard when I was there, thank god I'm not anymore but many of my friends still are, but I wasn't there from the start so guess I heard wrong about the CN part.

It's more than just that. The CSA is not a running trade - therefore, it pays less, the hours-of-service restrictions are less onerous, etc. Back in the before times, that position was staffed by a second conductor, who had to deal with all of the same regulations and restrictions that the other two guys at the head end had to deal with.
It's how I was told they framed it. What you say is true, but since the CSA is tied to the crew by default their hours of service align with whatever the headend gets for every job, except for their spareboard or in mandatory manned-out situations. Does help there, but those situations are far in few between. But let's be honest here, it's really mostly about the cost-saving, should have mentioned that myself from the start.

One rumor I heard was they would all get standard 2 weeks in the first year, and then what they got before at alstom in year 2
Yup thats correct. Some 60% of employees didn’t get any vacation last year, and now no one will have vacation for the first four months of next year. Sounds like a recipe for burnout doesn’t it? Alstom’s argument was that since their vacation year runs from May to Aprilfor some strange reason it does), they weren’t in a position to award vacation during the final four months of the vacation year from January to April. But instead of evenly splitting the vacation reductions among everyone, they gave the top guys all their vacation ,up to six weeks in some cases, and the bottom two-thirds none. OOI wants all hands on deck to help with the transition, so even though they could allow vacation starting in January, they won’t, not until May. After that everyone will only get two weeks until Jan 2026. The union chair framed this agreement as a 'win' since technically as a new employees they wouldnt have been entitled to even 2 weeks. But if its a successorship, everyone wpuld get what they are entitled from the get go based on their time of service.
 
Last edited:
That's only for extra event trains or Niagara service. The vast majority of trains still have just the one CSA.
Not just event trains, although yes the Niagara Falls trains are all scheduled to get two CSAs.

It's how I was told the framed it. What you say is true, but since the CSA is tied to the crew by default their hours of service align with whatever the headend gets for every job, except for their spareboard or in mandatory manned-out situations. Does help there, but those situations are far in few between. But let's be honest here, it's really mostly about the cost-saving, should have mentioned that myself from the start.
But that's the thing, because the CSAs are not always tied to the rest of the operating crews it's gotten GO out of difficulty in those cases. Those additional CSAs are not tied to operating crews, for instance.

Dan
 
The Agenda for the Nov 28th, meeting of the Mx Board is up:


As usual not much is actually said in the GO/UP Operations Report.....

The ridership number given is for the period ending Q2.

1732285081816.png


I will reiterate that this number should be provided with context by showing the percentage of service currently being operated. It should also be shown by route/line and service period.

Over in the Marketing Report, we actually get some such breakdown, with the weekend numbers:

1732285307069.png


Peak (rush hour) recovery:

1732285370918.png


And

Overall Recovery:

1732285335688.png
 
I will reiterate that this number should be provided with context by showing the percentage of service currently being operated. It should also be shown by route/line and service period.

Over in the Marketing Report, we actually get some such breakdown, with the weekend numbers:

One has to contrast ML's approach to transparency on ridership data to TTC's Ridership disclosure approach.

ML does have all sorts of readily available, competently prepared, appropriately granular tabulations of their ridership data, at the monthly or better level. I have been shown examples of the data that is circulated internally. I can see no commercial or political sensitivity to routinely sharing this data publicly. ML may want to highlight some selective stats, but trust requires verification.

- Paul
(still ranting)
 
One has to contrast ML's approach to transparency on ridership data to TTC's Ridership disclosure approach.

ML does have all sorts of readily available, competently prepared, appropriately granular tabulations of their ridership data, at the monthly or better level. I have been shown examples of the data that is circulated internally. I can see no commercial or political sensitivity to routinely sharing this data publicly. ML may want to highlight some selective stats, but trust requires verification.

- Paul
(still ranting)
Every transit agency in the province has this data, down to the boardings at stops. But very few actually publish the amount we want. Generally speaking, they do see it as something that can be used against them. Sometimes they are right; you can make some very critical observations of a transit agency with this in hand.

The few agencies that do post more robust data (monthly ridership, by route, etc.) are generally on the upper end of service quality in the province- the TTC is actually the only one I know of, but GRT, Brampton and Mississauga might as well.

Metrolinx should see themselves as ‘worthy’ of posting said numbers, as their service does not suffer from underfunding that would make them look bad. But, it’s hardly out of character for them to be more secretive than they need to be.

That means we got to wait…. Any day now…. for that damned 2021 TTS!
 
I asked for more detailed ridership data two months ago, by station, something that Metrolinx used to publish as a map and shared on their blog.

They told me I would have to file a FOI request. I’ve already done that twice for separate aspects of the Hurontario Line, I’m not in a hurry to do that again.
 
I asked for more detailed ridership data two months ago, by station, something that Metrolinx used to publish as a map and shared on their blog.

They told me I would have to file a FOI request. I’ve already done that twice for separate aspects of the Hurontario Line, I’m not in a hurry to do that again.

LOL. There may be people out there who may be willing to bend their NDA a little. You won't be able to divulge the data, but at least you will know, and it's a lot less frustrating that the FOI route....but may cost you some beer money. It's a shame to have to deal with ML this way, but you do what you have to.

- Paul
 
I asked for more detailed ridership data two months ago, by station, something that Metrolinx used to publish as a map and shared on their blog.

They are a Royal Pain......

They told me I would have to file a FOI request. I’ve already done that twice for separate aspects of the Hurontario Line, I’m not in a hurry to do that again.

I know how ya feel, LOL..........
 
I would be interested (if available) the number of Lakeshore West riders that are actually from Milton line station catchment area's). I did a lot of biking in Toronto this summer and I had to cart my bike down to Bronte and hope the train wasn't full from Burlington (it was on game days), and certainly was leaving Oakville or Port Credit. I would guess half the riders getting on at Port Credit would prefer Cooksville. I think if GO knew how many riders would use Milton, that surely a reduced peak service on weekends could work. It would certainly reduce congestion on Lakeshore West. Back in the 90's there was not only all day weekday service to Erindale, but inbound weekday peak service for Blue Jays games. Not much has changed since then (except CP leaving Kipling area) so a limited weekend service should be possible within the current infrastructre availability. They could even re-instate the third track that appears to be rusting out. It's quite visible when you cross Wolfdale road to Erindale station. Since I live in Milton between the CN line and the CP line, I can hear trains on both tracks. There are days less then 10 trains travel through MIlton on CP, compared to over 20 that go around Milton on CN. So I don't buy that there are no time slots for limited weekend service on Milton. It comes down to money, which no Ontario governemnt seems to want to spend on this line.
 
I would be interested (if available) the number of Lakeshore West riders that are actually from Milton line station catchment area's). I did a lot of biking in Toronto this summer and I had to cart my bike down to Bronte and hope the train wasn't full from Burlington (it was on game days), and certainly was leaving Oakville or Port Credit. I would guess half the riders getting on at Port Credit would prefer Cooksville. I think if GO knew how many riders would use Milton, that surely a reduced peak service on weekends could work. It would certainly reduce congestion on Lakeshore West. Back in the 90's there was not only all day weekday service to Erindale, but inbound weekday peak service for Blue Jays games. Not much has changed since then (except CP leaving Kipling area) so a limited weekend service should be possible within the current infrastructre availability. They could even re-instate the third track that appears to be rusting out. It's quite visible when you cross Wolfdale road to Erindale station. Since I live in Milton between the CN line and the CP line, I can hear trains on both tracks. There are days less then 10 trains travel through MIlton on CP, compared to over 20 that go around Milton on CN. So I don't buy that there are no time slots for limited weekend service on Milton. It comes down to money, which no Ontario governemnt seems to want to spend on this line.

Ever filed an FOI? Could be an learning experience per the comments above.
 

Back
Top