The bottom of the MDT unit displays the Status Bar. This area provides important status messages regarding connectivity to the IVU, operators see OTP updates, etc. Examples can include LOGGED ON, Late 4 Minutes, Wait X minutes to Depart, on-time, as well as other information
- Data connectivity status
- GPS signal status
- Data transmission activity (TX/RX)
- Wi‑Fi status
- Mail status (messages from dispatch)
- Vehicle GPS time (used by the system to determine schedule adherence)
Data Connectivity Signal Status Icon
When operators power up a vehicle (ignition engaged) and then login to the mobile data terminal (MDT), the vehicle becomes a data probe, collecting all data against the digital schedule and vehicle health, and stores the information in 'the cloud'. Data capture includes all revenue and non-revenue service data (vehicle health, scheduled miles and hours, ridership data, on-time performance data, deadhead, fare collection). Connection status is shown as a green checkmark on the Status Bar when the IVU is 'talking' to the MDT display/indicating it's fully connected. If data connectivity is lost after an operator logs on, a Bad Comms system event notifies maintenance/dispatch of the vehicle’s loss of data connectivity. The MDT Status Bar displays a red X icon to indicate no connection for the vehicle. In this case, the vehicle will not collect any data against the schedule or related attributes as listed above (revenue/non-revenue miles and hours, ridership, etc.). If noted by a vehicle operator, it should be reported to operations/dispatch/maintenance right away.
The system utilizes a Store and Forward mode if the vehicle loses data connectivity after operator logon. Even for extended periods, the vehicle system will continue operating and any data collected will be stored (in the cloud) and automatically sent in when connectivity resumes.
While in Store and Forward mode, the MDT Home screen will display the correct timepoints and stops, schedule adherence status messages will be correctly displayed, on the MDT, stops will be announced at the right time, the fare system will function correctly, and passenger counts will continue.
After data communications are restored, the MDT forwards all data captured while offline, including stop reports, APC reports, on-time performance, vehicle health messages, etc.
MDT Connectivity to IVU
| MDT has data channel connectivity with the central system. The MGR provides network status information to the MDT; the MDT will make repeated central system connection attempts if a network is available. The MDT requests this information from the MGR at startup, and the MGR provides the MDT with network status updates when the network status changes. |
|
| Indicates weak data signal. The system might not be able to send and receive data. | |
| Indicates no data signal/data capture will not occur (only collects undefined miles and hours). The system cannot send and receive data. |
If your agency's policy directs, you should notify dispatch about weak or lost signal incidences.
Avail VoIP Communication
Transit agencies utilizing Avail's Closed Mic VoIP Communication system will have an additional icon in the top right corner of their data connectivity icon to display the status of the VoIP system
| This icon shows that all systems are working. MDT has data channel connectivity with the central system. The blue dot represents that the VoIP system is connected and ready to receive or make calls | |
| MDT has data channel connectivity with the central system. The red triangle represents that the VoIP system is not connected to the backend, and the vehicle will not be able to make calls. In this situation, the operator can still share canned data messages with the dispatcher | |
| This icon shows the vehicle is in voice fallback mode. The lack of a green checkmark shows that the IVU does not have a data connection to the backend system, but the blue dot means the VoIP system is still connected. While in this state, an RTT or PRTT message cannot be transmitted to dispatch, but if the operator picks up the handset, the system will make a voice fallback call to the dispatch console, and they'll be able to communicate verbally. | |
|
Indicates no data signal or VoIP connection. The system cannot send or receive data or make voice calls. Tip: Operators might see this icon shortly after vehicle ignition while the system is booting up. If the issue persists, there may be a cellular issue with the vehicle. |
GPS Location Status Icon
The vehicle GPS uses several satellite signals to triangulate and identify vehicle location. When vehicles lose connection with GPS satellites for a configurable amount of time, the system notifies dispatch about the failure and reports the vehicle’s last known location until the signal is restored and the vehicle sends an updated location. One of these icons is always visible.
| Indicates a good GPS lock. Normal operation. | |
| Indicates weak or no GPS lock. The system might not be able to locate the vehicle. |
There are some cases when a vehicle may experience temporary loss of its GPS connection. Some geographic locations, specifically some urban areas (urban canyons - taller buildings, metal structures/roofing, etc.) and/or areas with limited access to satellite signals can experience loss temporarily, blocking connectivity.
If your agency's policy directs, you should notify dispatch about lost GPS signal incidences.
TX/RX Data Activity Icon
The Status Bar includes an icon area to indicate data transmission to (TX) and from (RX) the COMMS server. These icons are only visible during data transmission.
The RX and TX icons appear here for informational purposes and do not require any actions by the operator.
| TX and RX flash to indicate data Transmit and Receive activity. TX and RX may flash independently. A blank icon space indicates no current activity. |
WLAN Icons
The WLAN (Wireless Local Area Network) icons appear here for informational purposes and do not require any actions by the operator.
| The vehicle has connected to a known WLAN access point. | |
| The MDT has opened a communications channel to the central system through the WLAN network. | |
| The MDT is transferring data to/from the central system through the WLAN network, or processing data received through the WLAN network. |
Mail Icon
The MDT Status Bar includes an icon for the status of dispatch messages to the vehicle. These icons represent different 'read statuses' and are visible on the Status Bar.
For more information, see MSG Button.
Mail Icons for MDTs
| New or unread messages exist in the Inbox. | |
| There are no new messages in the Inbox. | |
| There is a message that has been read in the Inbox. |
MDT Depart Prompts
Vehicle operators should refer to the Status Bar when the vehicle is stationary at a timepoint stop, to confirm the performance status of their bus. The Status Bar provides OTP prompt at timepoint stop locations only, so the operator can refer to this to help achieve an on time departure. These 'prompts' display in sets of minutes. Pay particular attention to very late and early departures. When it's time to depart, a popup displays on the MDT for the operator so they know 'it's time to go.'
Below we see that the vehicle s in an on-time departure status, meaning it left its last timepoint stop on time:
Below we see that the vehicle should wait to depart for 8 minutes, or it will be running too early, meaning it will leave too soon. Sit tight! Find a safe place to dwell. Don't go just yet- when you see this prompt:
Below we see that the vehicle has been running late. Maybe it was stuck in traffic or experiencing issues that are preventing an on-time status.
Status Text Box
The Status Text Box in the lower left corner of the screen provides essential information to the operator. The Status Text Box will display, for example, the schedule adherence status, the myAvail in-vehicle system status, or the last system action, such as sending a message to dispatch. The following are a few of the common messages:
Status Value |
Description |
| BOOTING … | The vehicle operating system is doing the initial boot-up. |
| COLD BOOTING | A boot to the initial settings is being forced. This should not be seen during normal operations. This state is often done to correct problems, and, in that case, a second reboot is always done. |
| DATA SEARCH | The vehicle is performing the initial sync with the backend system. |
| IN SERVICE | The system has returned from an Out of Service state, but has not yet arrived or departed a stop. |
| LATE +#Min | The vehicle is at a timepoint and is running # minutes late. |
| LOGGED OFF | The operator has logged Off. |
| LOGGED ON | The logon verification is complete. |
| MANUAL ANNC | The operator has pressed the Manual Announce button. NOTE This should not be done unless directed by dispatch. The vehicle will NOT appear in myStop public information systems while in this mode. Dispatch is notified when in this mode. |
| MSG DELVD | The text message the operator sent to dispatch has been delivered. |
| OFF ROUTE | The vehicle is off the scheduled route. The default is 500 feet and is configurable. This calculation is adjusted for detours set up in the ITS system, to avoid 'off route' notices in Operations. |
| ON ROUTE | The vehicle is on its scheduled route. |
| ON-TIME |
OTP status updates at departure from timepoint stop locations. When a vehicle is at a timepoint and departs on-time, an 'on-time' status presents. How it works: Sets of minutes are built- in to scheduled depart times, like cushioning, to allow for day-to-day condition changes; this helps to more easily achieve an on-time status for normal 'on the road variances'. Consider weather, traffic, construction, etc., as day to day variances. |
| OUT OF SRVC | The operator has pressed the Out of Service button on the ODK |
| PRTT DELVRD | The PRTT (Priority Request To Talk) request was delivered to dispatch. |
| REG ATTEMPT | The vehicle has requested to register with the backend system but has not yet been acknowledged. |
| RTT DELVRD | The RTT (Request To Talk) request was delivered to dispatch. |
| SYSTEM OK | The vehicle system is operational. |
| VOICE FALLBK | In a closed-mic radio system or a VoIP system, either a coverage problem or equipment problem is preventing data communications with the backend system. This state allows the vehicle to communicate without using the RTT or PRTT function. |
| WAIT #Min | The vehicle is at a timepoint and is running # minutes ahead of schedule. If it can be done safely the operator should wait to depart. |
| WARM BOOTING | The normal boot-up process is running. |