Too bad it doesn't also cover bus routes parallel to MAX lines, there was a situation today that would've been wonderful for this type of thing (assuming someone w/ a cell phone was using the service).
I was headed out towards Beaverton earlier today, since I'm coming out from SE Portland as usual so I hit Columbia and Jefferson Streets first, and lo and behold here's a 58, so I figure I'll stay above ground heading out there for a change.
Instead, just as the bus pulls onto the Sunset Hwy. onramp, the lights go out, and the operator announces the bus just lost alternator power, so turning the lights off will try to get us there. No dice, he give us a running play by play of various engine warning lights going crazy, and we barely make it up the Sylvan onramp. I dumbly ask the operator how far it is to the Washington Park MAX station... the answer: "too far to walk."
The next 58 reached Beaverton TC just in time for me to watch the last 53 (which went to exactly where I needed to go) leave the transit center. So, my wonderful substitute itinerary included a ride on the 78, complete with people talking loudly about their personal lives; and another transfer to the 56, sitting behind a woman applying her eye drops (yup, on the bus, while in motion). Not to mention a decent walk afterwards.
So, a sarcastic "thanks" to whoever scheduled the 1833 on line 58 today!

I'll tell ya what needs to happen here:

GET THIS HOOKED IN WITH TRIMET COMM CENTER so when there are delays and/or accidents this information can come directly from the main conduit, the comm center!

GET THIS HOOKED IN WITH TRIMET COMM CENTER

That's a very good idea. TriMet already has an outbound rider alerts system which people can subscribe to (which could stand to have better notification times), but TriMet could also monitor the emails from the Clever Commute system for early warnings of trouble that don't come in from other channels. All they'd need is a computer with Internet access, web-based email, and of course make it part of someone's job description to monitor the new messages if/when they come in.

I made a point of letting TriMet know we were going to do this.

They could use the system two ways:

1) Monitor it for info there own sources have not picked up yet.

2) Use it in addition to their own alert mechanism to get information out.

"All they'd need is a computer with Internet access, web-based email, and of course make it part of someone's job description to monitor the new messages if/when they come in."

They have all of that right there! The thing is they don't report the info they have to even the drivers!

How can we get them to actually report the info?

Of course what we will get is:

"we are already overworked and overburdened so we can't possibly do any other tasks"

Lot's folks sitting behind desks attending meetings filing reports but not enough people to do actual productive work, like this program could be with just a little clerical help.

The transit tracker is excellent, with one HUGE hole;

IT DOES NOT REPORT ACCIDENTS/BROKEN DOWN/ MISC DELAYS.

The customer service potential of the CLEVER COMMUTE concept is HUGE, because basically it will make the whole transit tracker, LIVE, with updates.

GAWD, would that be great or what!

The ability to "see" what's going on on any particular route. In real time!

All of us that are regular users of TRIMET have experienced the following when using the transit tracker:

"ARRIVING IN-----8 MINUTES"

"ARRIVING IN-----"4 MINUTES"

So your standing at your stop and six minutes have gone by so you call again and you get:

"ARRIVING IN------"30 MINUTES"

What the hell happened? You stand there fuming hating the transit system!

This is a very common event when using the transit tracker.

The CLEVER COMMUTE could eliminate that! Or at least give you an explanation!

That would be so great that it is too good to believe therefore it won't happen.

I can't find the link right now, but I recall a comment from someone suggesting that TriMet will roll out an upgrade to Transit Tracker which will report vehicle position/distance when the timing predictions become unreliable. That way, users will know how far a vehicle is from their location, and (assuming they're using a real-time display) how fast it is moving, if at all...

"TriMet will roll out an upgrade to Transit Tracker which will report vehicle position/distance when the timing predictions become unreliable."

I haven't heard anything about that but it would be WONDERFUL!

That way, users will know how far a vehicle is from their location, and (assuming they're using a real-time display) how fast it is moving, if at all...

It'd be really nice if they'd make an open system to work with Google to make a Google Maps tie in as well, like the way Google uses ODOT's data to show traffic speeds on freeways.

I have it on my phone, and I'm surprised how often I'll change dinner plans because of an unexpected backup getting into Portland for example. I'd rather stay in Vancouver, have a leisurely dinner, and watch the traffic die down on my phone before driving home.

If TriMet could offer something similar, it would tip the scales for some trips that I currently choose to drive.

I obsessively call Transit Tracker when waiting for the bus - and frequently downtown (although at 4th & Hall at the south end or 2nd & Burnside [I take the 12, 19 or 20 every day] at the north end) where the times are said to be the least reliable.

But I rarely find that i hear about 'phantom' buses, or buses which never arrive.

But I rarely find that i hear about 'phantom' buses, or buses which never arrive.

I'd say in the last six months it's happened at least a half-dozen times to me. It's more likely for a bus not to appear on Transit Tracker (because it's GPS receiver is non-functional, so Transit Tracker has no idea of its location; or it's a relief bus and therefore isn't programmed with the route), or the bus simply to not be there at all (and Transit Tracker does not even display a "scheduled" arrival for it because it knows the bus is late).

Just a note from the founder of Clever Commute:
I'm really glad to see all the great ideas and lots of positive energy.
There are lots of great points in these comments...and I'd reiterate that Clever Commute is meant to complement (not replace) any of the other services / sources of info out there (e.g., "NextBus" or official communications from the transit providers.
We're always looking for new partnership opportunities...and if it makes sense for us to integrate our data with services like "Transit Tracker", we'd love to have that conversation.

We're making progress on rolling out Clever Commute for the buses...and would welcome any additional comments from people on which ones would be the most valuable. (beyond #12...which is currently the highest priority)

Thanks!

--Josh

Our IT team had a very productive day...so I am pleased to announce that Clever Commute has
started service on the TriMet Bus!

We have started with the #12 Bus lines (Barbur and
Sandy)...and will listen to your feedback as we
explore adding additional routes.

You can sign up by going to
www.clevercommute.com ... and clicking on "Find Your
Line"
After you select "Portland"...click on "Commuter Bus" to see the new coverage.

[Moderator: Link made clickable.]

I've had it go both ways.

I have ghost buses all the time, but the #19 Glisan frequently will appear out of nowhere even when Transit Tracker - in the middle of the day - says the next one is coming in 30 minutes (this when scheduled every 15 mins).