Last night was the open house for the City’s new Leveraging Technical Expertise Locally (LTEL) initiative (you can read my previous coverage here). The event was meant to provide more details to the community, and to introduce the people behind the scenes. David Faber from the Deputy City Managers Office, Kamren Farr from TEC Edmonton, Keith Chorley from CoE IT, Bruce Beecher from CoE IT/Transit, and Cam Linke were all on hand to introduce the idea and answer questions. Roughly 25 people attended.
David began by giving the pitch, essentially providing the same information he shared with me last week. He stressed that this is a pilot program, and that it’s okay to fail. The City of Edmonton is hoping to learn from the experience, and will be reporting back to Executive Committee with the results. David highlighted the intent of LTEL:
- To communicate the services that the City of Edmonton provides.
- To build bridges with the local community, to enable small tech companies to use the City of Edmonton as a sandbox.
Next up was Bruce, who provided some information on the challenge – creating a replacement for Edmonton Transit’s Lost & Found system. The current database was built with Access 97, and the IT branch is keen to replace it with something more modern. A few details on the system:
- Roughly 1700 items are tracked per month
- Items are stored for 30 days, and if not retrieved are then donated, auctioned, or otherwise disposed of. Passports, for example, are returned to the government, and cell phones are returned to the carrier.
- Items are stored tagged in bins in a storage room that is roughly 20 feet x 20 feet.
- Most wallets, cell phones, backpacks, and purses are collected within 2 days.
The basic business processes are:
- Enter articles – start tracking lost items
- Search articles – when someone calls with a description
- Claim articles – individual signs the tag upon retrieving the item
- Purge articles – items removed from database after retrieval or 30 days
Some of the opportunities identified include:
- Improved security and access control
- Multiple item search (currently you can only search one item at a time)
- Track people inquiring about items
- Enhance reporting
- Potentially something generic enough that other CoE departments could use it
Kamren was up next, to provide the preliminary market assessment. He talked about the “lost and found” industry, and highlighted solutions at TransLink and the New York transit authority as best-of-breed. There are four existing types of lost and found systems:
- Public – transit, etc.
- Private – hotels, etc.
- Return service – you pay for tags or some incentive to return
- Online classifieds – lost and found posters, basically
He went on to talk about market segments, and highlighted some of the market drivers, opportunities, and challenges.
The challenge was eventually described as:
Use technology to reduce costs for the customer (City of Edmonton) and increase recovery rates for users (people who have lost things).
All of this information will be made available on the LTEL page. The only other pertinent detail is that the upper limit for the budget is $75,000. Technical requirements and other details will also be posted on the website.
I talked with a number of people after the session to get their perspective. Most folks seemed excited about the idea. Andrew from dub5, in particular, said he was impressed that the City of Edmonton took the time to get this pilot started, and suggested that it was a big step in the right direction. Bruce Winter echoed that sentiment, but like me, was hoping for something a little more visual.
Here are my thoughts on the open house:
- The City needs to do a much better job of spreading the word. I realize they wanted to manage expectations, but I don’t think enough people knew about last night’s event.
- I would have loved to have seen the format of the event mimic DemoCamp. Instead of slides full of bullet points, why not demo what they currently have?
- I get that a lost and found database isn’t particularly exciting, but that doesn’t mean that the presentation can’t be. Instead of telling us there’s a 20×20 room packed with items, why not show a photo?
- This is going to sound harsh, but Kamren’s presentation wasn’t much more than a Google search. Very basic business concepts (competition, market segments, opportunities, challenges) and nothing more than the names of some other lost and found systems. I’m still wondering what exactly TEC Edmonton and EEDC bring to the table, besides a couple more names?
My biggest concern however, is related to the very first question I asked. I wanted to know if there were any technical requirements, and specifically, if the application had to be on-premise (meaning the City of Edmonton hosts and manages it). Keith answered yes, tech requirements would be provided, and that yes, the solution needs to run in the City of Edmonton’s existing infrastructure. One of the stated goals of LTEL is to expose the City of Edmonton to some of the innovative ideas of the local tech community, so this seems like a big step in the wrong direction. Maybe there’s a good reason for this particular solution, but if so it was not made clear. I think putting up big restrictions like that right from the start limits the potential solutions the City could learn about. (Also, I was under the impression the City wanted to get out of the tech business, by not doing custom development and reducing the burden of hosting and managing systems.)
This criticism is meant to be constructive. Overall I think LTEL is a good thing, and I want to see it succeed. I look forward to the rest of the process!
Stay tuned to the website for updates and an application form. Companies interested in developing a solution have until December 15 to express interest.
4 thoughts on “Recap: Leveraging Technical Expertise Locally Open House”
“Keith answered yes, tech requirements would be provided, and that yes, the solution needs to run in the City of Edmonton’s existing infrastructure.”
Does this mean it has to run on windows server related platforms?
Not necessarily. I’m sure they have Linux and other stuff running in their infrastructure. Best bet is to check the site for the technical requirements update.