NextBus Recap – The story so far…

[UPDATE:] The proposal.

What would it take to build our own bus ETA notification and Internet hotspot system?

• Catch the NextBus VII – Stone knives and bear skins…

Twenty-four hours into blogging about the NextBus system, what have we learned? What’s the alternative? How large of an opportunity have we missed?

• Catch the NextBus VI – 24 Hours Later

What have other folk said about NextBus?

• Catch the NextBus V – Fairly Balanced

Why is the town concerned about cellphone charges? What kind of deal did we make?

• Catch the NextBus IV – New Hope?

Alameda California’s ACTransit signed a deal with NextBus is January, 2006. Did we get as good a deal?

• Catch the NextBus III – ACTransit’s Better Deal

May 8th I had an opportunity to speak with one of the folk from ACTransit who negotiated their great deal.

ACTransit got for their $1M:

• NEW: 54 signs, 125 vehicles, 13 routes
• EXISTING: 46 signs, 74 vehicles, 12 routes
• 7 years of support for their existing and new infrastructure.

Chapel Hill?

• 14 signs, 83 vehicles, 26 routes, unknown warrantee.

What does the Daily Tar Heel have to say?

• Catch the NextBus II

Why NextBus? What about the strange coincidence involving NextBus’ 2002 campaign contributions to Rep. Price?

• Catch the NextBus

[ UPDATE: ]

Bob Avery, the town’s IT director, came through this evening with additional documentation of the Real-Time Passenger Information System and Automatic Vehicle Location system for Chapel Hill Transit.

• Notice to Bidders RFP Real Time Passenger 9.1.05.pdf
• RFP Real Time Passenger Info System 9.14.05.pdf
• APPENDIX B-1 Real Time Passenger Info System.pdf
• APPENDIX B-2 Real Time Passenger Info Systems.pdf