Traveline key service developments: NextBuses


Published on

Martyn Lewis at the Traveline Conference 2010

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Traveline key service developments: NextBuses

  1. 1. Martyn Lewis
  2. 2. NextBuses delivers next departures for that location Customer selects location Takes the Traveline SMS service and puts it onto mobile internet devices . . Works on all smart mobile phone operating systems What is NextBuses ?
  3. 3. What is NextBuses ? Includes Location search by various means, A map to help selection & search, Real Time Data where this is available Gives more departures. Avoids SMS charges . . NextBuses API
  4. 4. What is NextBuses API? NextBuses API delivers next departures for that location Third Party application determines and delivers bus stop location A platform from which third parties can develop information services . .
  5. 5. What is NextBuses API? Five new info services Four more pending Tend to have richer functionality e.g. Maps, Location Awareness . . But May be limited to individual Mobile Phone Operating system
  6. 6. Go to Mobile Phone Operators Home Page, Select Travel , then NextBuses. ( Orange 3, TMobile) Text “Traveline” to 84268 . . Where can I find NextBuses? Or Go to Iphone Apps Store – NextBuses and MyBus Go to Android Market – CatchthatBus and Transicast UK
  7. 7. Establishing NextBuses 2008 March – developing the idea reaching consensus October - Finalising the plan December - system into test 2009 January - NextBuses goes live May thru November – live on Orange, 3, and T Mobile December NextBuses API into test 2010 March - NextBuses API released April - first Iphone Apps to market
  8. 8. Why NextBuses? Smartphone Users <ul><li>2008 5.5m </li></ul><ul><li>2009 7.2m </li></ul><ul><li>2010 12.8m </li></ul>SMS Texts <ul><li>2004 64bn </li></ul><ul><li>2009 118bn </li></ul>Mobile Phone Minutes <ul><li>2004 27bn </li></ul><ul><li>2009 104bn </li></ul>
  9. 9. Why NextBuses? <ul><li>Target </li></ul><ul><ul><li>2m enquiries year 1, </li></ul></ul><ul><ul><li>4m enquiries year 2, </li></ul></ul><ul><ul><li>6m enquiries year 3. </li></ul></ul><ul><li>2009 - equates to 480,000 enquiries per year </li></ul><ul><ul><ul><li>now 1.4m in a full year </li></ul></ul></ul><ul><li>With Third Party Apps 6m per year </li></ul><ul><li>Telephone around 3m enquiries per year </li></ul><ul><li>Internet 17m enquiries per year </li></ul>
  10. 10. NextBuses Monthly Enquiries
  11. 11. NextBuses Monthly Enquiries
  12. 12. Growth on Mobile Channels
  13. 13. Growth on Mobile Channels
  14. 14. Growth of Mobile Channels
  15. 15. What Users Tell Us 46% of all feedback rated the service (78% of those commenting said they liked it) 48% Would like a richer user interface and suggested development options 24% identified some poor data or bus service
  16. 16. What Next ? <ul><li>Letting new contract October 2011 </li></ul><ul><li>Consider Journey Planning Service </li></ul><ul><li>Encourage cross platform development on API </li></ul><ul><li>Enhance our own offer ? </li></ul><ul><li>Reconsider Pricing </li></ul>
  17. 17. NextBuses Martyn Lewis Any Questions ?