Skip to main content

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 it difficult (if not impossible) for anyone to identify a driver. This is very important because we want to protect the identity of the truck driver. Thus, if in a particular distribution centre there are 10 trucks everyday, we will provide information only on what the average wait time is for those trucks over a period of days. This will be plotted in a map and shown as a heat map.

A heat map will look like this.

It will be possible to zoom in and see specific sites in a heat map. Information will be available on how long wait times are in each site, in addition to the visual aid provided by the coloured heat. Red, for instance, means long wait and yellow just average. The darker the colour, the higher the wait time.

Of course, a user story may not always be typical. Sometimes, a truck driver who has activated the app may totally forget to deactivate it. Sometimes the user will remember to deactivate wait recording only when the truck is already at cruising speed. Other issues could be that location service may be turned off, or data connection is not available and the app cannot transmit to the server. All these are addressed in the technical design of the app.

The Wait Advisor requires the following components:
  1. The mobile app, which truck drivers will use to record wait times. This app will be provided for FREE and should be available in both IOS (Apple) and Android devices.
  2. The server which will receive the data from the app. There are plenty of options of where to host this, such as Google's Firebase, Amazon's AWS, Microsoft's Azure, and IBM Cloud. For now, the only requirement of this server is its ability to receive data from the app in terms of the SourceID (to distinguish between data points), GPS location, Start Time and End Time.
  3. The data analytics platform where the app data can be processed, cleansed, and presented. Currently, options are to use an API with Google Maps or use third party systems such as Power BI or Tableau.
(Help us build this system. Support us by becoming a Patron. Click here to sign up and share information about this project to your network. Check out our website at waitadvisor.in2teq.com).

Comments

Post a Comment

Popular posts from this blog

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 ...

App UI Design

The UI design for the app has to be kept simple, straight-forward, intuitive and easy to use. This is in consideration of the fact that the end-user, the truck driver, should not be bothered too much. In addition, the demographics of Australian truck drivers show the majority to be 40's and above. Being true to this, the following are the suggested screens: This is the screen when the app is started. It is quite simple to use: there is only a toggle switch to turn wait recording on or off. Once the wait recording is turn on, the screen is updated to reflect the current state of the app. It will just remain as simple as this one until the app is closed. This screen is a notification screen, as when the user is being prompted to confirm whether the location change noted means that the wait has been terminated and the truck is ready to hit the road OR that the wait continues, the noted location change is just due to a huge enough area that speeding up to driving sp...