Incident Reporting

We recently released (and improved) a new version of our incident tracking system for our fleet. It designed to be used across business units, from member services to fleet to management to loss control. It radically improves control and accountability for 'things that happen' in a carshare service - and believe me, things happen a lot

We've integrated locations, vehicles and members into sensible workflows that make it easier for workers to complete the work (our fleet and loss control team) - for reporters (such as our call center) to prioritise and allocate work - and for managers to understand where the problems are coming from.

This level of detail has enabled better tracking (and improved management) of 'negative' member events, such as when a member is unfortunate enough to have multiple bad things happen to them (through no fault of their own - such as a flat battery, a late return by another member, or a dirty car). We also integrated the incident system into our 'Driver Multivew' plugin, which means we've 'pooled' all these events into every other driver events that happen.

"Now I can see what happened to a specific driver, or what happened at a specific location, or what happened at a specific car. The level of detail is excellent." said Brian Giang, head of the fleet team at GoGet. "I can be a bit more proactive and see if a particular location or car has patterns that I need to be aware of - and I can delegate work to my team based on location as well as by car".

Quite a few carshare organisations we know track their fleet incidents via Google Docs. While thats great when you've got fairly small fleet, it gets quite cumbersome when you fleet grows to more than 10 vehicles - and linking the data together can be a complete nightmare! Sensible reporting requires a properly structured data model - which is why we created our incident reporting system.

We know at least on of our customers have integrated this into their Key Performance Indicators, using it to create a monthly 'Defect Rate' report which measure how far from perfect everything is, by incident type.

We think there is further scope to use this data to improve organisation performance and will be looking at other incident tracking improvements over the coming months.

Last Updated ( Wednesday, 07 March 2012 )
< Prev   Next >
Our Software Testing Process - every 6 hours!

Ok folks - a boring, yet vital topic. Software testing methodology!

The most important requirements for our platform is reliability - we have over 25,000 people relying on our engine on a daily basis. For our main client, GoGet, a single days outage can mean losses in the tens of thousands of dollars. It's enough to give you gray hair!

Workload Plugin

Today we released a couple of 'workload' dashboards which allow our fleet and member services teams to see, at a glance, how much work they've got in the pipeline. This means they'll know instantly if they're chronically understaffed and or whether they can sit back and relax. Each team leader can give tasks (of any type) a time budget, then see in a second how many hours of work they've got ahead to clear the task queue.