The Beta Test summary provides detailed information on the Beta Test that took place in July of 2003 at Qualcomm Headquarters in San Diego. The purpose of the Beta Test was to test the functionality of each technology individually as well as in concert with one another. In addition, it provided both the Deployment and Evaluation teams with a chance to view the data streams and adjust collection process accordingly. The Beta Test Addendum outlines those configuration changes that were identified during the Beta Test. The Beta Test of the FOT was performed on July 14-18, 2003 and utilized the Qualcomm technology truck and included members of the Deployment Team and the Independent Evaluation Team.
There were two primary Beta Test objectives. The first was to ensure that selected test technologies perform adequately in simulated scenario conditions. The second objective was to ensure that generated test data streams fulfilled requirements to allow for thorough Independent Evaluation analysis.
The Beta Test focused specifically on Scenario 1 - Bulk Fuel, and Scenario 4 - Truckload Explosives. These Scenarios were chosen as they represented the full continuum of FOT technologies and it was recognized that if their functionality met test conditions, it was generally unnecessary to pre-test the other scenarios. For the purpose of the Beta Test, Scenarios 2 and 3 were treated as subsets.
Scenario testing was broken into 3 functional components: (1) system configuration, (2) daily operations/processes, and (3) security breaches. A detailed script was developed for each scenario. The following are Scenario 1 and 4 overviews.
Each detailed Scenario script went through a "day in the life of" a driver and their possible route (Figure D-1). The technology truck was equipped with a switch box which allowed all technologies to be connected at once and, based on the scenario, the appropriate switches turned on. The Beta Test was operated from one of the vendor headquarters, so the shipper and consignee roles were simulated using a laptop computer and defining locations such as a rest area as the consignee.
Each segment of the detailed test script was tested and its performance documented. Throughout the Beta Test, the teams identified several possible configuration changes. Those will be noted in the Section D.3. Figure D-2 shows a screenshot depicting Global Login in which the driver has logged on/off.
The last day of the Beta Test, the Deployment and Evaluation Teams went through the data streams generated by the test to ensure that the data would be presented in a digestible format. Category headings were changed and some data fields were deleted.
Using the feedback and performance issues for each of the technologies during the Beta Test, several configuration improvements were identified.
A presentation was made to the Hazmat Working Group via WebEx of Beta Test process and the configuration changes. After the changes were agreed on by all, an Addendum to the Detailed Test Plans document was prepared and can be found in the next section.
*System design changes are highlighted throughout the table.
|Wireless Satellite Communications (w/ GPS and/or QASPER)||Utilizes satellites to link and log all system technologies from vehicle to the communications system.||X|| || |
|Wireless Terrestrial (w/ GPS and/or Cellular)||Utilizes cellular communications to link and log all system technologies from vehicle to the communications system.||X|| || |
|OmniOne Digital Phone||Host creates and sends a load assignment to driver w/ OmniOne phone.||X|| || |
|OmniOne Digital Phone||Driver and host exchange five different macros based on situation, i.e., unload/load, departing, stop.||X|| || |
|Dash Panic Button w/ Notification||Driver depresses the wired panic button and a "panic message" is sent to NMC from mobile unit.||X|| || |
|Dash Panic Button w/ Notification||NMC forwards "panic message" to carrier.||X|| || |
|Dash Panic Button w/ Notification||"Panic message" is copied to Law Enforcement via QMASS.||X|| || |
|Dash Panic Button w/ Notification||NMC personnel call to notify carrier of emergency situation. Call received w/ vehicle identification number.||X|| || |
|Wireless Panic Button w/ Notification ||Driver depresses red panic button on wireless panic button transmitter.|| || || |
|Wireless Panic Button w/ Notification ||Wireless panic button transmitter sends "panic message" signal to mobile unit, which in turn sends message to NMC. Host receives panic message.||X|| || |
|Wireless Panic Button w/ Notification ||NMC forwards message to carrier, as well as calls carrier and law enforcement (in some scenarios) with vehicle identification number.||X|| || |
|Wireless Panic Button w/ Notification ||Law enforcement account, QT/Web 3.1, is copied with panic messages and positions of truck.||X|| || |
|Wireless/Local Disabling||Attached to wireless panic button w/ notification, although driver disables vehicle by pressing separate Aux button on wireless panic button transmitter.||X|| || |
|Wireless/Local Disabling||Wireless panic button transmitter sends a command to disable vehicle; throttle is disabled.||X|| ||Long Term Consideration: Develop notification for local disabling|
|Wireless/Local Disabling||Driver depresses reset button on wireless panic button transmitter; throttle reverts to normal.||X|| || |
|Global Login||Logon||X|| || |
|Global Login||Logoff||X|| || |
|Global Login||Communications between NMC and MCT validating driver logon.||X|| || |
|Global Login||Driver hears audible warning and gets a message prompting him to logon every two minutes. ||X|| || |
|Global Login||Driver starts engine but does not logon. After five minutes of idling a Global Logon security breach is sent to the Carrier.||X|| || |
|Global Login||Driver starts engine and departs without logging on. After driving one mile a Global Login security breach is sent to the Carrier.||X|| || |
|Global Login||Driver logs into mobile three times unsuccessfully, and security breach is sent to the Carrier.||X|| || |
|Global Login||Host dispatcher logs off driver.||X|| || |
|Biometrics Login||Driver inserts smart card into slot on biometric device; driver places finger on scanner for verification; when verified green LED blinks.||X|| || |
|Biometrics Login||Message containing driver's global login user name and password to NMC for verification; NMC sends notification to carrier. Driver ID is displayed next to vehicle name.||X|| || |
|Biometrics Login||Driver starts engine and does not log on via biometrics. An audible beep is generated after two minutes to prompt driver to logon. After five minutes or one mile driven with no logon, a Global Login security breach is sent to the Carrier. ||X|| || |
|ESCM||Shipper logs onto ESCM w/ fingerprint and smart card and creates electronic manifest.||X|| || |
|ESCM||An e-mail is generated to inform the carrier and consignee of manifest ID; carrier notifies driver.||X|| || |
|ESCM||Driver departs for shipper; at shipper, driver logs on to ESCM system and logs on to accept responsibility for specific load/manifest. E-mail notifications sent to carrier and consignee.||X|| || |
|ESCM||Driver departs for consignee; at consignee, he logs on to ESCM system and transfers responsibility of load/manifest to consignee. E-mail notifications sent to carrier, consignee and shipper.||X|| || |
|OBC w/ Remote Vehicle Disabling||Carrier sends an over-the-air message to the OBC disabling the vehicle.||X|| || |
|OBC w/ Remote Vehicle Disabling||Verify that after message is sent, throttle is disabled.||X|| || |
|OBC w/ Remote Vehicle Disabling||Carrier sends over-the-air message to OBC enabling the vehicle.||X|| || |
|OBC w/ Remote Vehicle Disabling||Throttle is enabled.||X|| || |
|OBC w/ Loss of Signal Disabling||OBC monitors the communication system for a loss of signal; recognizes loss of signal.||X|| || |
|OBC w/ Loss of Signal Disabling||OBC identifies loss-of-signal for seven minutes while vehicle is driving >35 mph and activates throttle disable. Host sees Signal Loss Alert.|| || ||'OBC with loss of signal disabling' will be re-configured to activate throttle disable while vehicle is driving >20 mph. Seven minute threshold remains the same.|
|OBC w/ Trailer Door Lock System||Driver sends an over-the-air message to host requesting trailer door unlocked; host receives "unlock trailer macro."||X|| || |
|OBC w/ Trailer Door Lock System||Driver presses trailer door switch in cab and then has 20 seconds to walk back to open the door, or door will default to lock.|| || ||OBC w/ trailer door lock system will be re-configured to allow driver 60 seconds from time button is pushed to trailer door opening.|
|OBC w/ Trailer Door Lock System||If door lock is tampered with, an alert is sent to the mobile, which in turn sends an alert event to NMC and then Carrier.||X|| || |
|Electronic Cargo Seals||Driver logs onto the TSS system and uses mobile reader to collect the S/N of the e-seal in range; seals are bolted, and driver notes S/N of e-seal.||X|| || |
|Electronic Cargo Seals||Driver sends an over-the-air command to assign and seal each seal separately.|| || ||Extremely time consuming to assign and seal each separately. It may be possible for this to occur all at once. It is also very hard to view information on the handheld.|
|Electronic Cargo Seals||Carrier is able to view sealed locks on website.|| || ||Screen has to be constantly refreshed to see updates. New SAVI software will incorporate e-mail notification to carriers.|
|Electronic Cargo Seals||Driver enters mobile reader into surveillance mode for assigned seals.||X|| || |
|Electronic Cargo Seals||When a seal is tampered with, an alert is sent to the carrier, and an audible alarm sounds. || || ||Differentiation must be made between red and black type for events logged on the SAVI website.|
|Electronic Cargo Seals||If a seal becomes undetected, and alert is sent to the carrier and an audible alarm sounds.|| || ||Investigation must be made into the placement of seal on door in order for antennae to be read.|
|Geofenced Mapping||Carrier initiates a route-based geofence trip on a designated route.||X|| || |
|Geofenced Mapping||Once trip is initiated, 15 minute position requests are made to the unit by the host system.||X|| || |
|Geofenced Mapping||Carrier monitors vehicle for positions and is able to view on a route map.||X|| || |
|Geofenced Mapping||When driver deviates from the designated route over mile, the host system begins requesting positions every five minutes. ||X|| || |
|Geofenced Mapping||As driver enters geofenced area, the host system begins requesting positions every 3 minutes.||X|| || |
|Tethered Trailer Tracking||Driver hooks tractor to trailer, tethered trailer unit transmits the tethered trailer track ID over power bus to the mobile unit. Trailer ID displayed on unit.||X|| || |
|Tethered Trailer Tracking||Mobile unit sends and over-the-air message to carrier to notify them of connect event. Connect message is displayed on TT/Win.||X|| || |
|Tethered Trailer Tracking||Driver unhooks the tractor in consignees yard, mobile unit detects lack of trailer tracks ID and sends over-the-air disconnect event to carrier.||X|| || |
|Untethered Trailer Tracking||When trailer is disconnected the Carrier creates a rectangular geofence around trailer, and GT unit verifies hourly that it has not left that area.||X|| || |
|Untethered Trailer Tracking||If it is taken from geofenced area an alert is sent to carrier, and position reports can be configured to be sent frequently.||X|| || |
|QTRACS/400||Computer system/server for satellite and terrestrial communications.||X|| || |
|QTRACS/Web||Computer system/server for satellite and terrestrial communications.||X|| || |
|QTRACS/Win||Computer system/server for satellite and terrestrial communications.||X|| || |
|SAFlink Web||Computer system/server for biometrics and ESCM.||X|| || |
|SAVI Web||Computer system/server for electronic cargo seals.||X|| || |
|QT/Brazil||Computer system/server that controls remote vehicle shut down and trailer lock/unlock.||X|| || |
|GT/Web||Computer system/server that monitors untethered trailer status.||X|| || |
|TT/Win||Computer system/server that monitors tethered trailer status.||X|| || |