The UTT System Pilot Prototype Test Checklist describes the tests performed to verify the functionality as it was defined in the System Design Document – Untethered Trailer Tracking and Control System.
The Prototype Test Checklist document is divided into three separate scripts, one for each of the scenarios tested. Each script contains the following:
| No. | Scenario Test Description — Configuration | Methodology | Expected Result | Data Fields | Requirement | Status | FR | Comments |
|---|
| 1 | | | | | | | | Date/Time:
MCT # :
Trailer #:
Driver:
Dispatcher: |
| 2 | Setup trailer with the following config: | | | | | | | |
| 3 | | 1035 - Position Reporting Interval
(Status Report Interval) | 1 per 24 hours
(86400 secs) | | 2.2.1.1
2.2.3.1
2.2.3.2
2.2.3.3
2.2.3.4 | | | |
| 4 | | 1052 - Terminal preset wake interval (unpowered: wakeup every) | every 6 hours
(21600 secs)
(1 hour for testing)? | | 2.2.1.2
2.2.1.3
2.2.2.3
2.2.3.1 | | | |
| 5 | | 1053 - Preset Wake Duration | 1 min | | | | | |
| 6 | | 1126 - Stay Wake Time | 3 min
(10800) | | | | | |
| 7 | | 1121 - Send ID over Power Bus for Connect/ Disconnects | 1=Yes
Enabled | | 2.2.2.1
2.2.2.2
2.2.2.3 | | | |
| 8 | | 1133 - Cargo sensor installed | 1=installed | | | | | |
| 9 | | 1108 - Cargo sensor check interval | 30 min
(1800 secs) | | 2.2.6.1
2.2.6.2
2.2.6.9 | | | |
| 10 | | 1109 - The cargo sensor validation interval | 5 minutes
(300 secs) | | 2.2.6.5
2.2.6.6
2.2.6.9 | | | |
| 11 | | 1110 - The cargo sensor validation rechecks | 1 | | 2.2.6.5
2.2.6.6
2.2.6.9 | | | |
| 12 | | 1119 - Send Cargo empty event | 2 = send immed upon validation | | 2.2.6.3
2.2.6.4
2.2.6.9 | | | |
| 13 | | 1120 - Send cargo loaded event | 2 = send immed upon validation | | 2.2.6.3
2.2.6.4
2.2.6.9 | | | |
| 14 | | 1041 - Sensor Label 3 (door sensor) | Door | | | | | |
| 15 | | 1129 - Sensor 3 Installed | 1=installed | | | | | |
| 16 | | 1111 - Door Validation open time
(Verified open after) | 5 secs | | | | | |
| 17 | | 1112 - Door Validation closed time
(Verified closed after) | 1 min | | | | | |
| 18 | | 1116 - Door closed event messaging
(On close) | 0=Ignore (disabled) | | 2.2.7.2
2.2.7.4
2.2.7.10 | | | |
| 19 | | 1115 - Door open events messaging
(On open) | 4=Send immediately if cargo = not empty | | 2.2.7.1
2.2.7.3
2.2.7.5
2.2.7.6
2.2.7.7
2.2.7.10 | | | |
| 20 | | 1130 - Sensor 4 Installed (Aux sensor) | 0=not installed | | | | | |
| 21 | | 1124 - Send Status Reports When engine on | 1=Yes - For test purposes | | 2.2.3.5 | | | |
| 23 | TTRACS Company Settings System Preferences: | | | | | | | |
| 24 | | The connect/ disconnect event | sent immediately upon validation | | | | | |
| 25 | | Trailer position proximity | to the nearest custom landmark | | | | | |
| 26 | | Self-centered geo-fence default size (North/south length) | 0.5 miles | | 2.2.4.9 | | | |
| 27 | | (East/west length) | 0.5 miles | | | | | |
| 28 | | T2 geo-fence monitor interval
(Unpowered: check every) | 1/hour | | 2.2.4.3
2.2.4.4 | | | |
| 29 | | If trailer Enters geo-fence | send alerts immediately | | 2.2.4.1
2.2.4.2 | | | |
| 30 | | If trailer Exits
geo-fence | send alerts immediately | | 2.2.4.5
2.2.4.6 | | | |
| 31 | Setup Monitoring Plan: | | | | 2.2.8.9 | | | |
| 32 | | Monitoring plan ID | HZMT | | | | | |
| 33 | | Description | Hazardous Materials | | | | | |
| 34 | | Consider trailers lost after | 30 | | | | | |
| 35 | Conditions to Monitor | Cargo loaded | Medium | | | | | |
| 36 | | Cargo unloaded | High | | | | | |
| 37 | | Door open | High | | | | | |
| 38 | | Door closed | None | | | | | |
| 39 | | Aux Open | None | | | | | |
| 40 | | Aux Closed | None | | | | | |
| 41 | | Omni connect | Medium | | | | | |
| 42 | | Omni disconnect | Low | | | | | |
| 43 | | Omni disconnect at unknown disconnect point | High | | | | | |
| 44 | | Non-Omni movement | High | | | | | |
| 45 | | Entered geo-fence | None | | | | | |
| 46 | | Exited geo-fence | High | | | | | |
| 47 | | Battery needs charge | Medium | | | | | |
| 48 | | Battery needs replacement | Medium | | | | | |
| 49 | Alert notification | Setup alert notification for high, medium and low priority alerts. | Flash icon on desktop
Send e-mail
Send to pager | | 2.2.8.1
2.2.8.2 | | | |
| 50 | Setup Trailer Types: | | | | | | | |
| 51 | | Trailer type | DRV | | | | | |
| 52 | | Description | Dry van | | | | | |
| 53 | | Default monitoring plan | HZMT | | | | | |
| 54 | | Auto-stop monitoring plan | HZMT | | | | | |
| 55 | | Multi unit capable | Y | | | | | |
| 56 | Setup Trailer Landmarks: | | | | | | | |
| 57 | | Landmark configuration | Create Landmarks for Shipper, and Consignee locations. | | 2.2.3.10 | | | |
| 58 | Mobile Unit Setup: | | | | | | | |
| 59 | | MIPR rate | 1/ hour | | | | | |
| 60 | | TTRACS | enabled | | | | | |
| 61 | | Time Zone | PDT | | | | | |
| 62 | | Power down timer | 5 | | | | | |
| 63 | | Wakeup timer interval | 0 | | | | | |
| 64 | | Total wakeup power time | 5 | | | | | |
| 65 | | | | | | | | |
| 66 | QTRACS/Web Setup: | | | | | | | |
| 67 | | FWD macro creation | 01 Load Assignment
02 Unauthorized Disconnect Warning | | | | | |
| 68 | | Return macro creation | 01 Arrived at Shipper
02 Loaded and Leaving
03 Arrived Stop/Final
04 E-Call
05 Accept Load
06 Fuel Requested | | | | | |
| 69 | | Landmark configuration | Create Landmarks for
Shipper location
Consignee location
Carrier location | | | | | |
| 70 | | Create Route | Alisio Creek | | | | | |
| 71 | | Create Geo-fenced Risk Area | Nuclear Power Plant | | | | | |
| No. | Scenario Test Description — Daily Operations | Methodology | Expected Result | Data Fields | Requirement | Status | FR | Comments |
|---|
| 0 | Test Setup/Start | Driver disconnects trailer, verify cargo simulator is down, makes sure door is closed and sends message "Ready to start test".
Drive tractor to carrier location. | | | | | | |
| 1 | Dispatch Login | Dispatcher logs into the TTRACS/Web application in preparation for dispatching drivers to pickup trailers and loads.
Dispatcher logs into the QTRACS/Web application in preparation for sending messages to the driver. (optional) | Verify the dispatcher can login to TrailerTRACS/Web.
Verify the dispatcher can login to QTRACS/Web. | | | | | |
| 2 | Request status report | Dispatcher wants updated status on two trailers that appear to be closest to location of interest. Dispatcher selects trailers and does a 'Request Latest Status'. | Verify that a status report is returned for the UTT terminal in the timeframe configured. | Timestamp,
Lat/Lon,
Trailer Id,
SCAC | 2.2.1.1
2.2.1.2
2.2.1.3
2.2.6.8
2.2.6.9 | | | |
| 3 | Find Trailer | Dispatcher clicks on the "Find Trailers" tab to search for desired trailer.
a. Specific trailer location
b. Trailers based on cargo status (empty/full)
c. Trailers near a specific landmark
d. All trailers | Verify when dispatcher enters specific trailer ID that the correct trailer detail is displayed.
Verify when dispatcher selects Current Trailer Status and enters empty in Cargo list, only empty trailers are listed.
Verify when dispatcher selects Trailers Near a Landmark link and enters 10 miles that the correct trailers display.
Verify when dispatcher selects Current Trailer Status he sees all trailers in the account. | | 2.2.3.10
2.2.3.11
2.2.3.12 | | | |
| 4 | Driver Login | Driver arrives at truck, starts ignition and sends message to dispatch that he is ready for assignment. | Verify message is received and read.
Verify message is from Carrier location. | | | | | Freeform message "Ready for Assignment ". |
| 5 | Assign Trailer(s)
(optional) | The dispatcher creates a load assignment/pickup macro instructing the driver where to pickup the next trailer and load.
The OmniTRACS messaging system (via QT/Web) is used to send the message to the driver. | Verify the dispatcher can create a forward load assignment macro with return receipt and that it gets sent. | Timestamp,
Forward macro#,
Tractor ID,
Lat/Lon,
msg length,
type (text/binary),
user fields | | | | . |
| 6 | Accept assignment (optional) | The driver reads the load assignment macro. | Verify the load assignment can be read and that dispatcher gets notification of the receipt. | | | | | |
| 7 | Accept assignment (optional) | The driver sends a load accepted macro. | Verify the load accepted macro is sent and received at host system. | Timestamp,
return macro#,
Tractor ID,
Lat/Lon,
msg length,
type (text/binary),
user fields | | | | |
| 8 | Connecting a Trailer | The driver arrives at trailer pickup location and attaches to the assigned trailer.
The OmniTRACS terminal detects via the 7-way an untethered trailer terminal connected to the tractor. | Verify the driver can see the correct trailer UA is connected on the MCT display. | | | | |
|
| 9 | Connecting a Trailer | The OmniTRACS terminal sends a connect message to the NOC. The NOC forwards the event to the TrailerTRACS/Web application. | Verify the connect message is generated by the Untethered TrailerTRACS device and is displayed in TTRACS/Web | Timestamp,
Origin (Vehicle),
Lat/Lon,
Trailer Id,
Event
(connect) | 2.2.2.1
2.2.2.2 | | | |
| 10 | Connecting a Trailer | Dispatcher gets an alert for the connect.
Dispatcher validates that the trailer is connected to the assigned tractor. He acknowledges alert and the acknowledgement is logged. | Verify the dispatcher receives a notification (email, page, system tray alert) that there has been a connect to the proper trailer.
Verify when the alert is viewed (description = Omni connect) and that the dispatcher name is logged. | | 2.2.2.1
2.2.2.2 | | | |
| 11 | Stage load | Driver covers the cargo sensor to simulate full load. | Verify that the dispatcher gets a cargo loaded event following this activity. | Timestamp,
Lat/Lon,
Trailer Id,
Event
(Not empty) | 2.2.6.1
2.2.6.2
2.2.6.3
2.2.6.4
2.2.6.5
2.2.6.7 | | | |
| 12 | Stage load | Dispatcher gets an alert for the cargo loaded status.
Dispatcher acknowledges
alert and the acknowledgement is logged. | Verify dispatcher receives an alert with priority specified.
Verify that the alert is acknowledged when read and the dispatcher id is logged. | | 2.2.8.1
2.2.8.2
2.2.8.3 | | | |
| 13 | Monitor Trailer Door Activity | Upon completing the trailer loading, the trailer door is closed. Due to the configuration Door Closed event is not sent. | Verify that the dispatcher does not get a Door Closed event following this activity. | | 2.2.7.4 | | | NO Door Closed Event |
| 14 | Monitor the Trailer en-route (optional) | The driver departs for the destination.
The driver sends a "departing macro" to the dispatcher via the OmniTRACS satellite system (optional). | Verify the driver is able to send a departing macro.
Verify the dispatcher receives the departing macro. | Timestamp,
return macro#,
Tractor ID,
Lat/Lon,
msg length,
type (text/binary),
user fields | | | | Truck waits to leave until above events are received. |
| 15 | Host Based Route Monitoring (optional) | The carrier initiates a trip by assigning a tractor to a pre-defined route using the QTRACS/Web application. | Verify that on QTRACS/Web dispatcher is able to start the vehicle on a trip on the assigned route. | Timestamp,
Tractor ID,
Lat/Lon,
Trip ID,
Event
(Start Trip) | 2.2.4.10
2.2.4.11
2.2.4.12
2.2.4.13
2.2.4.14
2.2.4.15
2.2.4.16
2.2.4.17 | | | Start Trip
Route:
Tolerance: 0.5
On Route ping: 15
Off Route ping: 5
Trip name: Day of week abbreviation and date, i.e., Mon062104 |
| 16 | Host Based Route Monitoring (optional) | The QTRACS/Web application will commence the monitoring of the tractor's trip by scheduling the "on route" positioning interval (e.g. every 15 minutes). | Verify the system starts 15-minute position ping while the unit is on route. | Timestamp,
Tractor ID
Lat/Lon,
Proximity | | | | Position |
| 17 | Host Based Route Monitoring (optional) | The QTRACS/Web application monitors the vehicle for positions and route progress. | Verify the vehicle displays positions on the route map. | | 2.2.3.6
2.2.4.15 | | | |
| 18 | Host Based Route Monitoring (optional) | The QTRACS/Web application monitors for any route deviation and alerts the dispatcher if a deviation occurs.
The Driver deviates from his predefined route.
The Driver sends Return Macro # 6 "Fuel Requested". | Verify out of route alert is sent to dispatcher via email or pager identifying information related to the violation. Verify popup alert is displayed on QTRACS/Web.
Verify the ping rate increases to the value identified for out of route. | Timestamp,
Origin (Vehicle),
Lat/Lon,
Geo-fence ID,
Event
(Off Route) | 2.2.4.17 | | | Tractor Out of Route Alert
|
| 19 | Host Based Route Monitoring (optional) | Driver enters keep out risk area that he has been told to avoid. | Verify a "violating geo-fence" alert is sent to dispatcher via email or pager identifying information related to the violation. Verify popup alert is displayed on QTRACS/Web.
Verify the ping rate increases to the value identified for entering a risk area. | Timestamp,
Origin (Vehicle),
Lat/Lon,
Geo-fence ID,
Event
(Violated Geo-fence) | 2.2.4.17 | | | Tractor Entered Risk Area Alert
|
| 20 | Monitoring for unauthorized disconnect | Driver does a disconnect in risk area, which is considered an unauthorized disconnect | Verify that an unauthorized disconnect alert is sent to dispatcher. | Timestamp,
Origin (Vehicle),
Lat/Lon,
Trailer Id,
Event
(disconnect) | 2.2.8.6 | | | Disconnect Event
Disconnect Alert
Unauthorized Disconnect Alert |
| 21 | Monitoring for unauthorized disconnect | Driver opens the door.
The trailer terminal recognized that an open door event has occurred. The trailer terminal determines based on the trailer configuration if an alert is required.
The Trailer terminal generates an alert and send sit OTA to the TrailerTRACS/Web application. | Verify the open door event occurs and is displayed on TTRACS/Web | Timestamp,
Lat/Lon,
Trailer Id,
Event
(Door Open) | 2.2.7.1
2.2.7.2
2.2.7.3
2.2.7.4
2.2.7.5
2.2.7.6
2.2.7.8
2.2.7.9
2.2.7.10 | | | Open Door/ Cargo not Empty Event |
| 22 | Monitoring for unauthorized disconnect | The Dispatcher receives an alert that a door has been opened on a non-empty trailer. | Verify the Open door alert occurs and is displayed on TTRACS/Web | | 2.2.8.8 | | | Open Door/ Cargo not Empty Alert
|
| 23 | Monitoring for unauthorized disconnect (optional) | Dispatcher sends message to driver to reconnect and return to route. | Verify message is received and read. | Timestamp,
Forward macro#,
Tractor ID,
Lat/Lon,
msg length,
type (text/binary),
user fields | | | | |
| 24 | Monitoring for unauthorized disconnect (optional) | Driver reconnects trailer to tractor | Verify connect message is received. | | | | | Connect event
Connect alert |
| 25 | Host Based Route Monitoring (optional) | Driver exits keep out risk area. | Verify an "exited geo-fence" alert is sent to dispatcher via email or pager identifying relevant information. Verify popup alert is displayed on QTRACS/Web. | Timestamp,
Tractor ID,
Lat/Lon,
Geo-fence ID,
Event
(Exiting Geo-fence) | | | | Tractor Exit Risk Area Alert |
| 26 | Host Based Route Monitoring (optional) | Driver returns to predefined route. | Verify a "back in route" alert is sent to dispatcher via email or pager identifying relevant information. Verify popup alert is displayed on QTRACS/Web. | Timestamp,
Tractor ID,
Lat/Lon,
Geo-fence ID,
Event
(On Route) | | | | Tractor Back in Route |
| 27 | Host Based Route Monitoring (optional) | The driver arrives at the consignee.
The driver sends an arrived at consignee macro. | Verify driver can send the arrived at stop/final macro.
Verify the dispatcher can view the arrived at stop/final macro on host system. | Timestamp,
return macro#,
Tractor ID,
Lat/Lon,
msg length,
type (text/binary),
user fields | | | | Arrived at Stop/Final Macro |
| 28 | Host Based Route Monitoring (optional) | The dispatcher initiates a trip end when a tractor arrives at the pre-defined route destination. | Verify the dispatcher is able to identify that the truck has arrived at the proper location and is able to end the trip. | Timestamp,
Tractor ID,
Lat/Lon,
Trip ID,
Event
(End Trip) | | | | Trip End |
| 29 | Trailer arrives at destination | The driver disconnects the trailer at the designated location. | Verify the trailer ID no longer displays on the OmniTRACS terminal display. | | | | | |
| 30 | Trailer arrives at destination | The OmniTRACS terminal detects that the untethered trailer terminal is no longer connected and sends a disconnect message to the NOC. The NOC forwards the event to the TrailerTRACS/Web application, alerting the dispatcher of the trailer disconnect. | Verify the disconnect message is displayed on TrailerTRACS/Web application. (non-empty trailer disconnect alert).
| Timestamp,
Origin (Vehicle),
Lat/Lon,
Trailer Id,
Event
(Disconnect) | 2.2.2.1
2.2.2.2
2.2.2.3 | | | Disconnect Event
|
| 31 | Trailer arrives at destination | The dispatcher receives an alert that a non-empty trailer has been disconnected at an authorized location.
The dispatcher validates that the trailer is disconnected in an authorized disconnect location. | Verify the dispatcher gets a disconnect alert.
Verify the dispatcher can identify that the Trailer is in an authorized location by identifying the position of the disconnect on the map or confirming the landmark. (Trailer position history with map).
Verify the dispatcher can validate the last cargo status is 'not empty'. | | | | | Disconnect Alert (at consignee landmark, last cargo status = not empty)
Authorized Disconnect at Consignee |
| 32 | Geo-fencing the Disconnected Trailer | The dispatcher can choose to create a geo-fence surrounding this disconnected trailer. | Verify the dispatcher can create a self-centered geo-fence around the trailer with 1 mile east/west and north/south coordinates, and 1 day start and stop time. The wakeup interval should be every 5 minutes and the type of geo-fence is alert on exit. | | 2.2.4.1
2.2.4.2
2.2.4.3
2.2.4.4
2.2.4.5
2.2.4.6
2.2.4.7
2.2.4.9
2.2.5.1
2.2.5.2
2.2.5.3
2.2.5.4
2.2.5.5
2.2.5.6
2.2.5.7 | | | Create Trailer Geo-fence
|
| 33 | Geo-fencing the Disconnected Trailer | The TrailerTRACS/ Web application generates a message with the updated information and sends it to the trailer terminal via the NOC, Terrestrial Network to the trailer terminal. | Verify the TTRACS/Web identifies a geo-fence has been sent to the trailer. | | | | | |
| 34 | Geo-fencing the Disconnected Trailer | An "electronic fence" is set around the trailer, which the trailer terminal will monitor based on its configuration.
The dispatcher using TTRACS/ Web has the option to view the geo-fence on the map. | Verify the dispatcher, using TrailerTRACS/Web has the option to view the geo-fence on a map. Check the Positions Details. | | 2.2.3.7
2.2.4.8 | | | |
| 35 | Cargo Tracking: E-Call (optional) | The driver sends a message to the carrier indicating that he has disconnected the load at the consignee. | Verify driver can send the e-call macro.
Verify the dispatcher can view the e-call macro on host system. | Timestamp,
return macro#,
Origin (Vehicle),
Lat/Lon,
msg length,
type (text/binary),
user fields | | | | E-Call Macro #4 |
| 36 | Cargo Tracking: New Load Assignment (optional) | The dispatcher sends message to driver to return to Shipper location.
The driver leaves the consignee and heads back. | Verify message is sent, received and read by driver. | Timestamp,
forward macro#,
Origin (Vehicle),
Lat/Lon,
msg length,
type (text/binary),
user fields | | | | Freeform message "Return to Shipper". |
| 37 | Untethered trailer geo-fence alert | Driver turns off the engine and lets the MCT power down timer elapse. Then he connects the trailer back to the tractor. No connect event is sent from the OmniTRACS system since it is shutdown. | Verify no tractor positions are received on return trip. | | | | | |
| 38 | Untethered trailer geo-fence alert | The Trailer terminal will wake up based on the customer configurable setting (e.g. every hour) to determine if the geo-fence violation has occurred.
Move the trailer outside of the geo-fence.
If the trailer has left the geo-fenced area, the trailer terminal will send a geo-fence violation alert to the carrier. | Verify the dispatcher receives an exited geo-fence alert notification.
Verify that when alert message is acknowledged the user is logged. | Timestamp,
Lat/Lon,
Trailer Id,
Event
(Exiting Geo-fence) | 2.2.4.3
2.2.8.5
2.2.8.3 | | | Trailer Exited Geo-fence Alert |
| 39 | Untethered trailer geo-fence alert | When trailer exits the geo-fence, the dispatch changes the Status Report interval to 15 minutes and tracks the trailer. | Verify positions for the trailer are received every 15 minutes. | Timestamp,
Lat/Lon,
Trailer Id,
SCAC | 2.2.31
2.2.3.2
2.2.3.2
2.2.3.4 | | | Status report interval 15 minutes |
| 40 | Trailer monitoring | When tractor returns to Shipper, driver needs to disconnect the trailer, turn on the MCT and let it power up, then do a connect. | Verify that when a connect is received the TrailerTRACS application identifies that the trailer has moved from its last disconnected location. | | 2.2.8.5 | | | Non Omni Movement Alert.
|
| 41 | Test End | Driver sends message "Test End" when tasks are complete.
Dispatcher sends message "Test End" when tasks are complete.
Dispatcher runs Event History report to gather information on trailer. | Verify the Event History report runs properly with correct information.
Verify data collection against Web UI's. | | 2.4.1.1 | | | Request Data collection process is performed.
Reset the status report parameter. |
