Skip to main content

Project Background

The Wait Advisor was conceived during the #FatigueHACK, a hackathon organised by the Canberra Innovation Network (CBRIN) for the Australian Trucking Association (ATA) held in parallel with Trucking Australia 2018 at the National Convention Centre Canberra on the 18th to the 20th of April 2018. The hackathon challenge was simple: current fatigue management systems do not seem to work, the participants were asked to propose solutions that might.

There were at least 8 teams in the hackathon, and we were Team 5 (known as Team Comags). Click here for the hackathon website at CBRIN and to check out the other participants.



During the hackathon, we had access to mentors and resource persons such as truck drivers, operators and owner-drivers. What came out as a common theme in the conversations we had was that the delays at the point of loading and unloading whatever cargo the trucks are carrying were a pain to everyone. It has been happening but nothing has been done about it. Hauling companies do not complain because the businesses at each end will just simply move on to another contractor. It would then mean loss of livelihood for the driver.

A truck driver works long hours, particularly the long haul interstate ones. When a driver reports for work, he or she is primed to drive: he or she is ready. However, if the driver is subjected to long waits before starting the day, this readiness-- or fitness to drive --will start to wane. By the time the driver hits the road, the fitness to drive would have suffered already. Why, even ordinary drivers get annoyed and distracted by delays on the road! Compound this issue and we've got a very serious problem, one that has been there for a while but hasn't had the attention it needed for so long.

So we thought, what if we can provide data that will expose where these delays occur? Using data science, we will aggregate data from different trucks and create an abstraction that will make it difficult, if not impossible, for anyone to be able to identify a specific source. This will give comfort to drivers-- they will be anonymous, which prevents them from being subjected to retaliatory business practices. More importantly, data that exposes where the delays are will be available and stakeholders will have actionable information before them.

What could possibly happen?
  1. Trip planners and truck drivers can better plan trip routes and schedules, which can probably help ease congestion at loading and unloading points and cut short wait time.
  2. Industry associations can have better leverage to engage businesses to get them to cooperate in improving the processes at the start and end of each trip.
  3. Businesses can make better informed decisions and improve their processes, or face pressure from the industry association, from the general public, and if necessary, from the regulatory bodies.
  4. Regulators can persuade unscrupulous businesses  involved in the supply chain under new legislation on the Chain of Responsibility to get their acts together or face stiff penalties. 
Inspired by these possibilities, we then looked at what its potential impact is in the problem domain, which is driver fatigue. Immediately, we saw that cutting delays will definitely improve the fitness-to-drive of the driver such that he or she will be in a better shape when he or she hits the road. A driver with better levels of fitness-to-drive can mean a world of difference than a driver who is not. Ultimately, it will be a safer road for every Australian.

(Help us spread the word, please share this article. We are also in Patreon, support us by becoming a Patron. Click here to sign up).


Our #FatigueHACK Team, photo courtesy of CBRIN.

Comments

Popular posts from this blog

Project Overview

The Wait Advisor is an app which truck drivers can use to record wait times. A typical user story will be like this: Use of the app is as simple and straightforward as possible. When a truck is stuck in a queue, the truck driver can quickly activate the app and when the wait is over, the truck driver simply deactivates the app to signal that the truck is ready to move to its next destination. What happens in the background is that when the truck driver activates the app, it records the current time and location. When the app is deactivated, it records the time and location at the time of deactivation. The wait time is then calculated as the time that has elapsed between the time when recording was started to the time when it was stopped. The app then transmits this data to the server in the cloud. Data is gathered in this way. The more truck drivers use the app, the more data the server will receive. When there is sufficient number of users, data can then be aggregated to make

App Specification

General Requirement The general requirement is to develop an app which records the amount of time a user spends within the vicinity of a location. Data on the wait time and the location where the wait was made should be transmitted to a server. Starting and ending recording is user-initiated. Thus the app should enable the user to toggle between start recording and end recording. The app should be able to recover in case the user forgot to initiate end of recording. Thus the app should check for location change at fixed intervals and therefrom determine if circumstances suggest that the user has forgotten to initiate end of recording. The app should send data to the server, but in case there is no data connection, it should be able to queue the data for transmission and send it out once a data connection is established next time the app is activated. Assumptions The following assumptions are made and included as business rule: First, polling of location data is at

The Wait Advisor in Big Rigs

In the lead up to the Technology and Maintenance Conference in Melbourne, News Corporation Australia's Big Rigs published an article about the Wait Advisor. Our thanks to Bob Riley for writing this up.