Subways

by

Yonge Subway Yard Study (Revised)

At its meeting on November 17, the TTC will consider a report on the yard needs for the Yonge-University-Spadina subway. 

Updated November 15 at 6:10 pm:

A reference to the replacement dates for the BD signal system and the T1 fleet has been corrected.  This triggers a discussion of whether the TTC will concoct an excuse to retire the T1’s early on the grounds that it is not worth installing ATO on them.

Updated November 15 at 4:30 pm:

The Subway Rail Yard Needs Study (aka SRYNS) proposes that future operations of the Yonge-University-Spadina line through 2030 be provided through a combination of various facilities:

  • Expansion of Wilson Yard
  • Storage of 6-8 trains at Davisville Yard
  • Consolidation of all non-revenue equipment (work trains) at Davisville Yard
  • Provision of online storage for additional trains at Richmond Hill
  • Sheppard Subway equipment (four 4-car T1 sets plus a spare) would be serviced at Greenwood

However, looking beyond 2030, staff foresee a need for additional storage and are asking the Commission for perimission to protect for a new yard on the Yonge line with purchase of property, should it become available.  This is a rather oddly worded request to which I will return.

The SRYNS was funded by York Region in recognition of the storage and servicing issues that a Richmond Hill subway extension would create for the YUS line.  The study explicitly does not look at requirements for the Bloor-Danforth line, but the report recognizes that this too must be examined.  The restructuring of the fleet and storage requirements for YUS trigger a move of all T1 subway cars to Greenwood, but that yard is not large enough to hold all of them.  In the short term, the TTC owns more T1s than would be required to operate both the BD and Sheppard subways, but this fleet will reach 30 years in 2026 and replacement with newer cars will occur within the timeframe of any projected yard requirements. Continue reading →

by

Metrolinx Publishes Full Richmond Hill Subway Study

The full version of the Benefits Case Analysis for the Yonge Subway extension to Richmond Hill is now available online.  I will comment on it at greater length when I have the time to do so.

Notable in this report is the acknowledgement of the effect of this extension on the existing subway system and especially Bloor-Yonge Station.  There are conflicting remerks in the BCA regarding the degree to which improved service on GO Transit to Richmond Hill can divert riding from the subway line.  A major issue here is that the implementation of very frequent all-day “Express Rail” GO service to Richmond Hill is not contemplated in the Metrolinx plan until 2031, long after a subway extension would open.

Detailed work on a number of related proposals will continue, and Metrolinx expects that a full evaluation will be available in late 2010.

by

TTC Capital Budget 2010-2019 (2): Subway Fleet and Service Plans

The TTC Capital Budget contains many projects related to subway fleet, capacity and future operations.  Collectively, these projects amount to billions of dollars and many of them are not yet funded.

There are two major problems faced by subway planners:

  • Everything has a very long lead time, and plans made today need to balance between overspending on capacity we might not need and underspending that could produce future constraints on service.
  • Everything costs a lot of money, and unexpected additions to the budget can crowd out other necessary projects.

Large organizations and projects share issues familiar to many:

  • Left hand, right hand.  One department plans on the assumption that another project will actually happen in the announced manner and on a definite timescale.  Plans change, but co-ordination is less than perfect, and plans go out of sync.
  • In for a penny, in for a pound.  A project is “sold” politically on the basis of improvements it can bring.  However, actually achieving these improvements triggers the need for many follow-on works that are not budgeted.  Proponents of the first project in this chain innocently claim that they were simply creating the ability for some future enhancement.  Privately the attitude may be that the politicians would never approve something if they knew how much it would actually cost.  In a robust economy, the extra funding is always found somewhere, but when times are tight, budget surprises are unwelcome.

Both of these effects can be seen in the TTC’s subway fleet and service plans. Continue reading →

by

Will the RT become LRT? (Update 3)

Updated October 2 at 11:15 pm:

In the comments thread, a question has come up about the originally proposed alignment of the SLRT.  This dates back to the Metropolitan Toronto Transportation Plan Review (MTTPR) and a study of alternatives to the Scarborough Expressway.  One of these was an LRT line starting at roughly Queen & McCaul running east to the CNR Kingston Sub at Degrassi St., then northeast via the CN to Morningside Avenue.  A branch would run north from Scarborough Junction following mainly existing and abandoned rail corridors to the Scarborough Town Centre.

That branch eventually became the SRT, but was moved to follow the Uxbridge Subdivision because the old right-of-way used in the first proposal was very narrow.  As you will see from the maps, this is not the very wide Hydro corridor that crosses the SRT line, but a much tighter route.

To orient yourself, the Uxbridge Subdivision runs just below the top edge of these maps which have north to the right.

South Part
North Part

Updated September 30 at 4:50 pm:

Item SC 28.30, which requests the TTC and Metrolinx to report in November 2009 on an LRT implementation for the SRT, was passed today by Council.

Item SC28.20 was ruled out of order and withdrawn.

Updated September 30 at 12:45 pm:

This morning, in discussion of another Transit City matter on the Council Agenda, Councillor Thompson asked TTC Chief General Manager Gary Webster about the status of the Scarborough project.  Among other things, Webster replied that:

  • TTC now feels that LRT is the appropriate technology for the route and is working with Metrolinx to define the technology and scope for the Transit City projects generally.
  • The funding announced by Queen’s Park is not sufficient to carry the SRT north from Sheppard to Malvern.

The debate will continue this afternoon, but I suspect the items listed in my original post below will not be dealt with until tomorrow given their place on the agenda.

Original post:

Toronto Council’s agenda today, September 30, includes items of interest regarding the Scarborough RT (SRT) line.

Continue reading →

by

More Follies With Station Signage

The Cumberland Street entrance of Bay Station re-opened recently at long last.  Construction had been delayed by unexpected conflicting structures when the old entrance was demolished.

It’s a nice entrance, as TTC buildings go, but something very odd shows up in the decor.  At the bottom of the entrance stairway, we find not a beautiful mural, not an historic account of Yorkville, not even ad advertising frame, but a copy of TTC Bylaw No. 1 at very large scale.  This is no cardboard throwaway, but a metal sign built to last the ages.

IMG_0358C

There’s only one tiny problem:  the date.

IMG_0358C2

In fact, the TTC Bylaw was updated in 2009 as we can see by visiting the Bellair Street entrance.

IMG_0362C

Here, we have the same info as on the Cumberland panel (the Human Rights statement and the Bylaw), plus a “here’s the bylaw stuff you really need” sign.  However, this is the new bylaw from January 2009.

IMG_0363C

I have been advised that the Cumberland panel will be replaced.  Why did this happen in the first place?  What is so important about the bylaw that it deserves pride of place on a wall that could have held a decoration appropriate to the neighbourhood?  Why was a sign installed with text that was replaced 8 months earlier by a new and substantially revised bylaw?

There is a move afoot to set up a website where people can report signage foul-ups.  It may be hosted here, or maybe elsewhere.  Once this is in place, I will publish the details.

by

Landmarks Vanish! Tourists Mystified!! (Update 2)

Updated September 22 at 9:50 pm:  According to this evening’s Global news, the TTC will pull the offending maps tonight from all stations.  Now may be your last chance to photograph your favourite blunder.  Mind you, considering how fast the TTC is at taking down out-of-date notices, I suspect the “bad” maps will be around for awhile.

It will also be intriguing to see if, when the new maps are installed, they actually do update all of them in every station.  I found four of elderly vintage without looking very hard yesterday.

Meanwhile, the Star managed to publish an annotated version of the St. Andrew map which shows City Hall where Osgoode Hall actually is, and the CN Tower at the corner of John and Front, north of the rail corridor.  I suppose a paper with its offices in the 905 can’t be expected to know much about downtown Toronto any more.

Finally, I strongly urge that the TTC circulate the new maps for comment to ward Councillors’ offices who might actually know where things are in their respective neighbourhoods.  Even better, as some have suggested in the comments here, put them online so that the vastly better-informed transit amateurs can help out with the project.

Continue reading →

by

Sometimes Repairs Take Longer Than Expected

This morning, I was happily working away when what should I hear, but the familiar blast of the horn on the work train that maintains the Prince Edward Viaduct.  One small problem.  It’s 9:50 am and the subway should be running by now.

Was there a service interruption notice?  No.

Memo to Brad Ross at the TTC:  We keep hearing about the new staff and all the wonderful things that will happen with notices regarding service.  When?

IMG_0037E1V3CC

by

Why Do We Need Another Bus Terminal?

From time to time, discussions here about Union Station turn to the question of a bus terminal.  A bigger terminal.  A better terminal.  A terminal with seamless connections to the trains.

Why?

GO/Metrolinx has major service expansion plans for its rail network including all-day service to cities now with, at best, peak hour, peak direction trains.  As service frequencies increase and good, all-day service is the norm on GO rail corridors, what do we need the bus routes (and their terminal) for?

A review of the list of all GO scheduled services shows us the future, such as it is, of GO bus operations downtown.

Timetables 01, 09, and 12 are all Lakeshore rail services whose bus components connect with rail terminals at all hours.

Timetable 16 is the Hamiton QEW bus service.  When GO reaches the point of having all day, 30 minute rail service to Hamilton, why run a parallel bus service?

Timetables 21 and 31 are the Milton and Georgetown services, both of which will receive frequent rail service that, like the Lakeshore routes, should be fed by buses at the outer, all-day terminals.

Timetable 32 is the Brampton to Union via Thornhill bus service.  Although this route connects today with the Yonge Subway at Finch and Sheppard Stations, it will eventually connect with the Richmond Hill subway extension.  The  buses do not need to come into downtown.  Updated August 29, 2008.

Timetable 61 is the Richmond Hill service.  Like the other rail corridors, this is scheduled to receive frequent all-day service, as well as a subway extension.

Timetables 65 and 71 are the Barrie and Stouffville services.  All-day train service over part of these lines is included in the 15-year Regional Plan.  Off-peak buses services beyond would feed the trains as on other all-day corridors.  In the same timeframe, the subway will be extended to Vaughan.  Even without all-day train service to Bradford, Vaughan Centre (or York U) is a much more appropriate connection for the bus service than bringing trips all the way into downtown.

Timetables 19, 20, 22, 27, 29, 32, 34, 37, 38, 40, 46, 50, 52, 60, 62, 64, 66, 69, 81, 88, 93, 94, 95 and 96 are all bus services that do not come into downtown.  They either connect with the subway at suburban stations, or they are between points in the GO network outside of Toronto.

Planned expansion of rail service in the Niagara peninsula and northwest from Georgetown will compete with and may replace private bus operations to these areas.

Land near Union Station for bus operations is difficult to find, and the last thing we need is an oversized bus terminal that will have no buses operating from it in less than 20 years.

Metrolinx is studying possibilities for such a terminal, but they need to step back and ask whether such a terminal is even required.  The rail networks of both GO and TTC are expanding at very substantial cost well into the GTAH.  Why spend all this money only to perpetuate limited capacity bus operations running all the way to Union?

Overall, operation of intercity bus routes into downtown Toronto will decline substantially over the next decade and beyond. If we are to have a new bus terminal, it should be planned for the services that will exist, that will survive into the future, not for today’s routes that are soon to be replaced with rail.

by

What Shall We Do With Don Mills (2)?

When I talk about taking a Downtown Relief Line north to Eglinton, some people, including some at the TTC, look at me as if I had at least two heads.  That’s a shame, considering that the TTC itself did a preliminary design for this 35 years ago.

I offer these tidbits from my archives not to reignite a discussion we have had here extensively before, but to put to rest any claims that this line was only ever intended to stop at the Danforth.

DRLAlignment19740112cBack in October 1974, the TTC was considering various proposals for new rapid transit lines, one of which was the Queen Street subway. This line would have run from Roncesvalles and Queen east to somewhere beyond Broadview, then turned north past Greenwood yard and continued via Donlands to O’Connor. At that point, the line would cross the Don River to serve Thorncliffe and Flemingdon Parks winding up at the CPR crossing north of Eglinton. The map linked here is a bit fuzzy in places because the original is not clear, but it shows the alignment (including an alternative via the CNR corridor) quite clearly.

 

DRLBrochureCovercTen years later, the TTC was working on the Downtown Rapid Transit Study, and the route had morphed into an ICTS line to Union Station. 

 

 

 

DRLBrochure1cA brochure advertised this study and explained the growing problem of central area subway congestion complete with a suggestion that passengers transfer at St. George rather than Bloor-Yonge.

 

 

 

DRLBrochure2cThe DRL was never built because politics of the day favoured suburban projects, and instead we got the Sheppard Subway.

by

Metrolinx Reviews the Richmond Hill Subway Extension

On August 7, Metrolinx released the Executive Summary of an Interim Benefits Case Analysis for the Richmond Hill extension of the Yonge Subway.  The most important text appears on the introductory page:

This interim BCA appraisal of the project raised a number of key network related considerations.  Considering this, Metrolinx, in close collaboration with the City of Toronto, TTC and York Region, will undertake additional analysis to more comprehensively understand these matters and how they impact the network and project scope. The analysis will include:

  • Possible adjustments in project scope, timing or phasing;
  • Consideration of the extent to which improved service levels on the parallel GO Richmond Hill rail corridor to off-load some of the demand on Yonge Subway corridor (existing and proposed extension); and
  • The cost impacts of the various options on the subway yards strategy, Yonge-Bloor subway station improvements; and a future Downtown Relief Line to bypass the Yonge-Bloor congestion pinchpoint.

The BCA process for this project has identified a range of development and congestion pressures along the Yonge Subway corridor. In partnership with York Region, TTC and the City of Toronto, Metrolinx will be carrying out the work above and report back to the Metrolinx Board on the resolution of key project issues in late 2009.

This statement is the first official recognition outside of Toronto Council that the Richmond Hill subway must be reviewed in the larger context of network performance and the stress that additional loads will put on the system.  When Toronto gave guarded approval to the subway extension, but with a long list of pre- and co-requisites, many complained that this was just Toronto being obstructionist, the sort of behaviour that led to politicians being kicked off of the Metrolinx board.  Things have changed.

The Benefits Case Analysis clearly had its origin in simpler times when Metrolinx projects were considered in isolation.  Page 1 of the BCA lists only three alternatives for consideration:  two subway versions (differing only in the number of stations) and a BRT scheme.  There is no mention of alternatives such as GO improvements or LRT, but at least the potential for overloading the existing subway system is acknowledged.  Later, the report acknowledges that it is part of a larger collection of studies (as noted in the introductory text above), but this is not reflected in the options that were evaluated.

In a bit of accounting sleight-of-hand, only part of the cost of Bloor-Yonge Station improvements are charged to the extension project on the ground that other factors will increase demand and the cost should not all be charged to the extension.  This misses the basic point that the extension would be the trigger, and indeed has already been used to justify upgrading capacity on the existing subway system.

The options shown on page 2 show that demand in the corridor between Finch and Richmond Hill would place roughly 9,000 peak hour passengers on the subway, about 3/4 of the total travel in this corridor.  Most of the rest would be on an infrequent GO service (every 30 minutes) in this scheme, even though Metrolinx’ own plans call for substantial improvement in service to Richmond Hill.

BRT is rejected as an option because its capacity is only 3,000 per hour, and the demand is well above this level.

Footnote 2 of this table states the obvious, that demand peaks before implementation of Richmond Hill Express Rail service currently planned for the 2021-2031 timeframe.  Why would we spend a fortune on expanding capacity of the existing subway system if the demand will be siphoned off by another future project?

Page 3 tells us that the benefit-cost ratio for the subway options is 0.7.  We have to take this with a grain of salt given the underlying methodology.  The lion’s share of the benefit comes from reduced auto commuting (“Transportation User Benefits” on page 4), but this would also occur with improved GO service.  The benefit of those redirected trips would no longer be available as an offset to the cost of the subway extension, and the benefit-cost ratio for the subway proposals would be much lower.  This is masked by the absence of an option which includes significantly improved GO service to which much of the “user benefits” would be assigned.

One major flaw in the Metrolinx BCA methodology is the inclusion of “economic impacts during construction”, in other words, the job creation of building the line.  This “benefit” can only be assigned to a specific project if the money would not otherwise be spent elsewhere.

However, in any evaluation of network alternatives, we can reasonably assume that we have “X” billion dollars to spend on something, and the real question is where we get the best return for the investment.  Claiming an economic benefit from construction skews the evaluation of projects to those that cost the most and therefore provide the greatest short-term job stimulus.  One could argue in the extreme that not spending billions on public transit would be beneficial because the money would be available for other uses such as reduction of provincial debt or tax relief.

This “analysis” is a farce.  Clearly, Metrolinx sees that an isolated review of the Yonge Subway extension misses the bigger picture.  Oddly enough, they didn’t bother to publish the full analysis, only the summary.  I suspect that the complete report would be far too embarrassing given the superficial work visible here.

We must now await the outcome of several other studies, notably those for improved GO service and for the subway options into downtown.  This work should have been underway long ago, but at least, finally, it is started.  Is the era of “I want a subway” planning finally over?