1. Open311
Workshop
Philip Ashlock | Open311.org | October 2011

2. Open311
A collaborative model & open standard
for civic issue tracking

3. 911 for Emergency Action
311 for Emergent Action

4. Wedding Open Source to Government
Service Delivery
http://eaves.ca/2009/02/25/wedding-open-source-to-government-service-delivery/

5. Public bug trackers for real world problems

23. Reinventing the Wheel
Does every city need its
own app?
Boston NYC Portland Pittsburgh

25. API
Distributed innovation
API
API

26. Benefits of the Open Standard
Interoperability
Shareability
Consistency
Ubiquity
Efficiency

31. Vancouver
Seattle Edmonton
Portland Southampton
Toronto Barnet
Grand Rapids Boston
New Haven
San Francisco New York City
Chicago
Bloomington Philadelphia
Baltimore
St Louis Washington D.C.
Tuscon
New Orleans
Miami
Dominican
See http://wiki.open311.org/GeoReport_v2/Servers
Republic

32. Open311
Open Source
wiki.open311.org/Open_Source

33. Open311 Dashboard

34. Open311 Facebook App

35. Open311 on Joget

41. The Civic Network?

42. A National 311 API?

44. Telephone & SMS Accessibility from a web API?

46. Open311 GeoReport v2
Stats
~35 city endpoints
~10 independent implementations
~ 8 vendor supported products
~ 5 open source servers
~ 4 open source clients
~ 5 client libraries

48. Needs
• Improved docs (eg iodocs)
• Validator

49. Future
• GeoReport 2.x & 3
• Other APIs

50. Inquiry API

54. Asynchronous Inquiry
with Status?

57. What if anyone could answer?

59. Patterns of Interaction
Issue Report: Request / Report
Inquiry: Ask / Search
Ideation: Answer / Suggest
wiki.civiccommons.org/Collaboration_Platforms

67. Unify these interactions?

70. Thanks!

71. Open311
www.open311.org
Philip Ashlock phil@civiccommons.org