Did Wheel Trans Botch A New System Implementation?

Recently, I received an email from a reader reporting a major problem in the implementation by Wheel Trans of a new booking system.  Here is the relevant part of the note:

On August 6th, Wheel-Trans took down its online booking system to install a “New and Improved’ reservation system. Two days later the new page was up and running — sort of. Wheel-Trans had cleansed half of our list of “preregistered addresses” and, in so doing, had forced us back upon the hugely overloaded and barely functional phone reservation system.

The consequences were devastating. Bus operators, contract minivan owners, taxi drivers, reservationists and customer service agents, and the customers, all felt the effects; customers arriving late to appointments or not able to book rides or make cancellations, drivers attempting to meet an impossible schedule while driving to cancelled or abandoned calls, and agents and reservationists facing a never-ending flood of calls from frustrated, desperate, and, in some cases, irate customers. Like a locomotive shunting cars, each missed or late call rippled down the whole system; drivers run further and further behind in their schedule, customers wait longer and longer for their ride which, increasingly, as the day wears on. are abandoned or never arrive at all. And the traffic on the phone system grows and grows.

Even those not directly involved with the system— customers’ employers, physicians and therapists, hospitals and labs, friends and families—are all dealing with missed or late appointments.

Everyone I’ve talked with over the past few weeks, customers, Wheel-Trans drivers and phone staff, and health care professionals has a story to tell. And not one has a happy ending. Although everyone has different tale to tell, they all want a return to the old setup. But no one knows how to make this happen.

This has all the earmarks of a botched IT project although the exact reason has not come out yet.  In my own IT experience, this could be a question of bad specifications, of the official client not understanding how their own system works, or a badly executed data/functional migration that wasn’t properly tested before the system went live.

I am not a Wheel Trans user, although I have heard enough horror stories about the service it provides.  It’s a vital service for users, and yet the TTC and City are entertaining a cutback to the amount of service or the eligibility of riders, not further enhancements as part of the 2012 budget.

This article is intended as a repository for comments about that service, and in particular about the effects of the recent changes to the trip booking system.

Service Changes for September 4, 2011

Many service changes are coming in September 2011 including additional service on routes that are now overcrowded.  However, the TTC will be considering lower standards for crowding (the “there’s still room on the roof” school of service planning), and many of these changes could be short lived.  (I will turn to budgetary issues in my next article.)

The service improvements are the upshot of the bargain trading little used periods of service on some routes effective May 2011 for better service where it is needed.  The budgetary headroom from the May cuts is not enough to pay for all the needed additions, and many improvements that would other be justified by current standards will not be implemented.  That justification may vanish if the standards are lowered. Continue reading

King/Bathurst Reconstruction Project (Update 8)

Update 8:  August 10, 2011 at 7:40 am:

Construction of the new safety islands has completed early, and the 511 is back to its normal routing.

Update 7:  July 26, 2011 at 8:00 am:

The TTC has revised dates for resumption of service through the intersection:

  • Wednesday July 27:  504 King and 508 Lake Shore routes return to King Street
  • Saturday July 30:  511 Bathurst route returns temporarily for Caribana
  • Tuesday August 2:  511 Bathurst route resumes diversion via Spadina
  • Monday August 15:  511 Bathurst route diversion ends

Update 6:  July 24, 2011 at 5:00 am:

An excellent overhead view of the completed intersection dated July 17 is available on Flickr.

Service on King Street through the intersection resumes on Monday, July 25.

Continue reading

Toronto’s Core Services Review Contemplates Transit Cuts

This morning, while TTC Chair Karen Stintz, Mayor Ford and other luminaries were dedicating the inaugural run in service of a Toronto Rocket subway train, the agenda for the July 28th Toronto Executive came out.  The city’s “core services review” has reached its agencies, including the TTC, and the consultant’s findings can be found starting on pdf page 161 of their report.

The premise of the city-wide review is that there is some sort of “standard” above or below which services are provided.  In some cases, reference is made to other cities, but in the case of the TTC, the “standards” appear to be pre- and post- David Miller’s mayoralty.  If something was done in the “Ridership Growth Strategy”, it is by definition “above standard” and up for elimination.

This is a strange way to evaluate services especially in the North American city lauded for the quality of its transit system and the economic benefits this brings.  Never does the consultant address the value of good service, only its cost.

The consultant, KPMG, show their colours on the title page with the double-entendre corporate motto “cutting through complexity”. Continue reading

Service Changes in July 2011

In a previous post, I described the diversions that will begin on July 11 around the reconstruction of the King/Bathurst grand union.

Beginning July 18 and continuing until early September, the 506 Carlton diversion around the Gerrard Street bridge, originally announced for June 19, will actually get underway.  Trackwork on the bridge has been in rough shape with slow orders for some time.  The planned date for return of streetcars to Gerrard Street is September 11.

Westbound service will run via Broadview, Dundas and Parliament.  Eastbound service will run via Parliament, Queen and Broadview.  Cars have been added to the schedule to compensate for the added mileage.

Effective July 31:

192 Airport Rocket: On the northbound trip, buses will serve the upper level bus stop at Jetliner first, then the arrival level at Terminal 1 and the arrival level at Terminal 3.  On the southbound trip, buses will exit the Airport via the ramp to southbound Hwy 427.  These changes are intended to free up running time to improve service reliability.

504 King: Streetcar service will return to Roncesvalles Avenue, although King cars will continue their diversion around the track and overhead work in Parkdale via Shaw and Queen.  There are only minor changes to some off-peak headways so that the running times work out.  However, I suspect with the traffic congestion on Queen and the inevitable streetcar short turns, service on Roncesvalles will not be as good as what is now provided by a dedicated bus shuttle.

Runnymede Station: The construction at Runnymede Station is supposed to be officially completed now, and 71 Runnymede, 77 Swansea and 79 Scarlett Road will return to their normal routings.

512 St. Clair: Overhead between St. Clair and St. Clair West stations will be retrofitted for pantograph compatibility.  Buses will replace streetcars on this section of the route after 10:00 pm weekdays, and all day on weekends.  The TTC claims that there will be timed transfers at St. Clair West.  Regular service resumes on September 4.

Service Changes Effective June 19, 2011

Many service changes will come into effect on June 19 thanks to the two common factors influencing summer schedules:  seasonal riding changes and construction.

The service changes are detailed in the usual spreadsheet form.  This will be a point of comparison in the fall when we see when and if these changes are reversed, what improvements are funded from the May service “reallocation”, or if budget problems start Toronto into a downward spiral.

Construction Diversions

The 504 King diversion in Parkdale for track and overhead reconstruction between Roncesvalles and Close will continue until the end of the summer.  The operation of streetcars on Roncesvalles itself should resume at the end of July.

The 506 Carlton car will divert around the Gerrard Street bridge over the Don River during reconstruction until the end of the summer.  Westbound service will run via Broadview, Dundas and Parliament.  Eastbound service will run via Parliament, Queen and Broadview.  Cars will be added to the schedule to compensate for the added mileage.

The 505 Dundas diversion around street reconstruction west of Spadina will continue through the summer.

The 502/503 services on Kingston Road will be converted to bus operation until late November for watermain construction.

Rapid Transit Service

On the Yonge Subway, the only service change will be the withdrawal of one standby train and one of three scheduled gap trains.  The scheduled headways are not changed.

Service on the Yonge subway has been lower than budgeted because of the late arrival of the Toronto Rocket trains.  The first of these is expected to enter service in June.  There is no word yet on when this will trigger headway improvements.

On the Bloor-Danforth subway, peak period service will be reduced by 12-15%.

On the Scarborough RT, running times will be increased to reduce top speeds during hot weather.

Details are shown in the spreadsheet.

2011.06.19 Service Changes

In Case You Haven’t Noticed

With the recent emphasis on Customer Service as the TTC’s new mantra, I am rather harder on them for certain types of issue than I might otherwise be.

One important part of CS is accurate information.  Not only is it useful to riders, it gives some indication that the organization cares to make their journey more comfortable with alerts about unusual conditions.

Sunday, May 15 is the date of the Goodlife marathon, and the TTC helpfully tells us about delays and diversions with posters and e-alerts.  Here is one I just received:

SUNDAY: Rolling road closures for GoodLife Toronto Marathon impacts TTC routes: 5, 14, 33, 65, 72A, 94, 97-320, 127, 504. Expect delays.

Last updated May 14, 2011 18:59:30

Route 33 Forest Hill no longer operates on weekends.  “Expect delays” is something of an understatement.

Meanwhile in another part of the world, the service change notice and revised schedule have finally appeared at Broadview Station for route 8 Broadview.  The TTC appears to be slowly catching up with the backlog from service changes implemented a week ago.

At times, I feel like I’m just kvetching, but one would hope that the TTC folks responsible for maps and service notices paid attention to timeliness and accuracy.

Secret Service Cuts

Today, the money-saving service cuts went into effect on many routes.  At this point, the TTC’s magnificent customer service efforts have not seen fit to post notices at stops on the affected routes, nor to change the posted schedules.  They have managed to place small yellow stickers saying “hey, no service”, but left the old schedules in place.  I don’t know if the yellow stickers are up system wide because checking that out is lots of work.

So far, the TTC’s effort consists of:

  • A “good news” press release and media event stressed the service additions (almost all of which were routine seasonal changes) while omitting any mention of the service cuts.
  • Updated schedule info is online, but not on schedules posted at stops.
  • There are “no service” stickers on affected stops, but I don’t know how extensive this work is, especially where routes with different hours of service share the same stop.
  • System maps have not been updated to show route segments with limited hours of operation.

At Broadview Station, there is no indication that 62 Mortimer and 8 Broadview no longer operate after 10pm Sundays.

On a related topic, the TTC must dust off its Service Standards and address issues on which they were silent earlier this year:

  • Will the screenline of 10 riders per hour continue to be applied for future service cuts?
  • Will walking distances to service be considered both as they apply to future cuts, and to reviews of the cuts that have been implemented?
  • What mechanism will be used to monitor and, if justified, to reintroduce service, and what standard will apply?

Please use comments on this post to help track the degree to which missing or incorrect information about the service cuts is a system-wide problem.

And remember to tell all your friends that this is “for the greater good”.

TTC Fouls up Variety Village Service Plan (Updated)

Updated April 26 at 2:30 pm:

I received a note from the TTC castigating me for the “gotcha” nature of this article.  In effect, in my zeal to show this as a staff error, I left out information that would have painted a different picture.

The background for this is that at the December 2010 meeting (the first of the new Commission), there was a presentation on the options for serving Variety Village.  This presentation is not available online, but was sent to me with the complaint.  Given its size, I have excerpted the portion relating to the proposed 12 Kingston Road split in which it is clear that (a) service would be removed from Kingston Road at some hours and (b) staff do not support this option.

2010.12 Variety Village Route 12

The December report accompanying the presentation includes an earlier report on Variety Village which mentions the split 12 Kingston Road service as an option, but recommends against it.  There is no mention in the 2004 report that a split service would remove buses from Kingston Road completely during some periods of operation.

The loss of service with this option is not mentioned in the April report or recommendation approved by the Commission, nor in the “Commission Highlights” posted after the meeting.  It is quite clear that this was seen as a “good news” story, and that the Commission did not understand (or if they did, care to acknowledge) that a service cut was involved.

The original post from April 25 follows below.

Continue reading

NextBus Data Feed Change Breaks Apps & Bookmarks

On April 6, NextBus introduced a new data feed structure.  The major change in this version is that the stop nomenclature used internally by the application has been revised to match the stop numbers used for the TTC’s vehicle arrival text message system.  Other updates include some schedule related information in the data feed (run, crew and trip numbers) that will probably be of more use to an internal app that “knows” about the schedules.

This change has side-effects both for users of the NextBus site, and for 3rd-party applications based on the data feed.

Any NextBus user who has bookmarked a stop for easy retrieval will find that the bookmark does not work.  The reason is that the bookmark includes the old stop identification, and this does not exist any more.  You will need to recreate the bookmark.

Users of Whereismystreetcar will find that it is working, sort of, while the author adapts his code to the new data feeds.  There is a similar problem with old bookmarks on this app, and any you have created must be redone.

I don’t know about other apps based on the NextBus feed, but if users could let me know what’s working and what’s not, I can maintain status info here.