Line 60: |
Line 60: |
| | | |
| Estimated Time of Arrival Protocol: | | Estimated Time of Arrival Protocol: |
− | * Dispatcher/office can request the ETA of the current stop/job in progress. | + | * Dispatcher/office can request the ETA of the current stop/job in progress; |
| * Garmin can notify about the actual time of arrival as well as the distance remaining to a stop. | | * Garmin can notify about the actual time of arrival as well as the distance remaining to a stop. |
| | | |
| Auto-Arrival at Stop Protocol: | | Auto-Arrival at Stop Protocol: |
− | * This feature is used to tell Garmin PND to automatically detect that it has arrived at a Stop and then to prompt the driver if one would like to mark the Stop as done and begin navigating to a next Stop on the list. | + | * This feature is used to tell Garmin PND to automatically detect that it has arrived at a Stop and then to prompt the driver if one would like to mark the Stop as done and begin navigating to a next Stop on the list; |
| * Auto-arrival can be determined by how long the unit is stopped close to the destination (in the case driver has to park and walk) or by how close the unit needs to be to the destination before the Auto-arrival feature is activated. | | * Auto-arrival can be determined by how long the unit is stopped close to the destination (in the case driver has to park and walk) or by how close the unit needs to be to the destination before the Auto-arrival feature is activated. |
| | | |
| Data Deletion Protocol: | | Data Deletion Protocol: |
− | * Dispatcher/office has the ability to wipe clean the data on Garmin PND. | + | * Dispatcher/office has the ability to wipe clean the data on Garmin PND; |
| * It allows to clean messages in inbox and remove stops. | | * It allows to clean messages in inbox and remove stops. |
| | | |
Line 74: |
Line 74: |
| | | |
| Canned Responses/Messages: | | Canned Responses/Messages: |
− | * Fleet managers can communicate by sending up to 200 "canned" responses from server to be stored directly on Garmin devices. | + | * Fleet managers can communicate by sending up to 200 "canned" responses from the server to be stored directly on Garmin devices; |
− | * Up to 50 of these canned responses can be utilized for any given scenarios. | + | * Up to 50 of these canned responses can be utilized for any given scenarios; |
− | * Drivers can store up to 120 canned messages, eliminating the need to type while driving | + | * Drivers can store up to 120 canned messages, eliminating the need to type while driving. |
| | | |
| Status Protocol: | | Status Protocol: |
− | * Up-to-the-minute communications that allow drivers to automatically send status updates. | + | * Up-to-the-minute communications that allow drivers to automatically send status updates; |
− | * Driver's units can store up to sixteen status indicators such as start/stop shift, on/off break, etc. | + | * Driver's units can store up to 16 status indicators such as start/stop shift, on/off break etc. |
| | | |
| ===Supported features on TAVL client application=== | | ===Supported features on TAVL client application=== |
− | TAVL client application lets user to use the following features of GARMIN FMI: | + | TAVL client application lets user use the following features of Garmin FMI: |
− | # Text messaging;
| + | * Text messaging; |
− | # Destination message;
| + | * Destination message; |
− | # ETA request.
| + | * ETA request. |
| | | |
| ===Text messaging=== | | ===Text messaging=== |
− | Text messaging feature lets user to communicate with driver (user that uses Garmin device) by sending text messages via GPRS. | + | Text messaging feature lets user communicate with the driver (user that operates Garmin device) by sending text messages via GPRS. |
| | | |
| ===Destination message=== | | ===Destination message=== |
− | Destination message is used to inform a driver of a new destination. When Garmin device receives a destination message from server it displays it as “Stop” to the driver and also gives the driver ability to start navigating to the “Stop” location. New destination in Tavl client is represented as Geozone so new Geozone (as destination) has to be created first. | + | Destination message is used to inform the driver of a new destination. When Garmin device receives a destination message from the server it displays it as a "Stop" to the driver and also gives the driver an ability to start navigating to the "Stop" location. New destination in TAVL client is represented as a Geozone so a new Geozone (as destination) has to be created first. |
| | | |
| ===ETA request message=== | | ===ETA request message=== |
− | ETA (Estimated Time of Arrival) request message is used when user wants to know expected arrival time to currently active destination and distance (in meters) from current object location to currently active destination.
| + | ''Estimated Time of Arrival'' request message is used when user wants to know an expected arrival time to currently active destination and the distance (in meters) from current object location to the destination. |