
The ISE Driver Messaging application consists of a
modular end-to-end software architecture. It’s primarily
made up of three components:
 |
Driver Interface—resides in the vehicle on a display or a handheld device |
 |
 |
Communications
Channel—exchanges information between the driver application and the
web application and is capable of interfacing with most existing
wireless communication mediums |
 |
Web
Interface—displays messages, allows dispatcher to see which messages
have been opened, and provides easy-to-use interface to send messages. |
| |

The
driver interacts with either a handheld device or a fixed display to
send and receive messages. The messages are sent back to the dispatcher
to report delivery status, alert the dispatcher of an unexpected delay,
event notifications, or various other types of messages.
Driver Benefits
 |
Simple, easy-to-use interface that resides on the in-vehicle display or handheld device |
 |
Receive critical information through a single interface |
 |
Easily view messages from dispatcher inbox/outbox message history |
 |
Pre-scripted messages or free-form |
 |
Customized keyboard for easy text messaging |
 |
Prioritized messaging |
 |
Status Tracking |
|
 |

The
web interface is a browser based application that enables the
dispatcher or other office personnel to send and receive both
pre-scripted and free-form text messages to fleet drivers. Dispatchers
are able to set a priority to specific messages to ensure delivery of
urgent messages.
Dispatcher Benefits
 |
Send a message to a single driver or a group of selected drivers |
 |
Track message status to verify that message has been received and / or read |
 |
Manage all messages received from fleet drivers in one standard interface |
 |
Tracks all communication between driver and dispatcher |
 |
Reduces cost as need for separate cellular service is diminished |
|
 |
|