I was fortunate enough today to chat with Bruce Beecher and Dennis Nowicki from Edmonton Transit (ETS). Bruce is the IT Strategic Advisor for the Transportation department, and Dennis is the Director of Community Relations for ETS. Though we talked about a variety of things, the focus was technology.
I think there was some educating happening on both sides. I learned more about their situation and perspectives, and I hope they soaked up some technical stuff from me. I think it went really well!
What I’d like to share in this post is an overview of what we discussed. There’s nothing confidential here, but some of this information may still be new to you. They’re aware they need to improve on the communication side of things!
ETS has been evaluating potential technologies to deploy to the fleet for quite a while now (I wrote about some at last year’s Community Conference). These technologies include:
- Automatic Vehicle Locator (AVL) – This is essentially a GPS module that would be installed on each bus.
- Automated Traveler Information Systems (ATIS) – This is essentially giving riders access to that GPS information. That is, where is my bus right now?
- Mobile Data Terminals (MDT)
- Automated Stop Announcement (ASA) – No more peering out into the darkness to see if you’re at the right stop. Also important for accessibility.
- Automatic Passenger Counter (APC)
- Automated Fare Booth (Smart Cards)
- Automatic Vehicle Monitor (AVM) – This would gather information about the engine, fuel consumption, etc. It’s like a black box for the bus.
Those are listed roughly in order of priority, though nothing is set in stone. In fact, the AVM might get bumped to the front of the list simply because it offers the best ROI for ETS. The ability to know what’s wrong with a bus on the fly would have a huge impact on the bottom line. Same goes for being able to determine if a bus is getting poor fuel consumption for some reason. Makes sense to me.
There are a few problems with all of this technology, mostly related to cost:
- Edmonton has bumpy roads and extremely cold temperatures in the winter. On-board equipment needs to be hardened and reliable. We often can’t use the same stuff that San Francisco uses, for example.
- Rough estimates place the cost per bus at $15,000. There are currently 903 buses in service.
- By 2012, the number of buses will be closer to 1300, so it won’t get any cheaper to deploy.
Another issue is maintainability. Ideally, each bus would have one computer with a LAN of some kind that everything else just connects to, so that it’s all integrated. Otherwise you end up with many potentially disparate systems.
What I took away from all of this is essentially that ETS is keen to deploy GPS technologies and to make that information available to riders. The challenge is finding a way to make it happen.
Next we shifted gears and talked about the ETS website, Google Transit and my API idea (though I’m definitely not the only one with the idea…dub5 is another interested group). There are improvements to the ETS Trip Planner in the works, so watch for something during the summer. They’re also looking to improve the main ETS website, now that everyone has had time to digest the edmonton.ca redesign.
Unfortunately I can’t talk as much about Google Transit as I’d like to just yet, but I can tell you that a major announcement is coming in the next week or so. I plan to cover it here, and you’ll no doubt see it in the mainstream media. Bottom line: ETS is fully behind Google Transit, and that’s a good thing for Edmontonians.
Is that going to happen – are they going to make the data available? No guarantees, but they will definitely consider it. Obviously an API would be better for accessing real-time data, but even a recent snapshot would be a step in the right direction. I think this is very encouraging!
If they do go down the data sharing route, I think we should organize an API building weekend!
The final thing I want to mention is that we talked briefly about RSS. My goal is to get every City of Edmonton department publishing as many RSS feeds as possible! It’s horribly underutilized at the moment. I think Bruce and Dennis definitely understand the benefit of RSS, and I hope to see some ETS feeds published soon!
Thanks to both Bruce and Dennis for a great conversation – I learned a lot, and I look forward to keeping the dialogue going.