Skip NavigationDepartment of Transportation Logo  U.S. Department of Transportation Keyword Links | Contact Us | Español

Federal Motor Carrier Safety Administration

Home Rules & Regulations Registration & Licensing Forms Safety & Security Facts & Research Cross Border About FMCSA
  Home > Facts & Research > 4. Scenarios (Page 3 of 4)
 
Overview
Statistics & Facts
Safety Progress Report
Publications & Reports
Events Calendar
Webinars
Future Webinars
Past Webinars
Safety Technologies
Product Guides
CVISN
About ART
Analysis Division
Research Division
Technology Division
Contact ART
 
    
Esta página está solamente disponible en inglés

4. Scenarios (Page 3 of 4)

  Print this page Print    

4.4 Scenario 2: High Value

4.4.1 Technologies Tested

The following technologies were tested in this scenario:

UTT System

  • Terrestrial UTT terminal
  • Ultrasonic cargo sensor
  • Magnetic door sensor
  • Cellular and GPS stealth-mounted antennas
  • Tractor power connection

Tractor Mobile Communications System

  • Satellite mobile communications tractor terminal

Host

  • Tractor system host application
  • Trailer-tracking host application with geo-fencing capabilities associated with the trailer

4.4.2 Functionality Tested

The following functions were tested in this scenario:

Trailer Location and Status

  • Find empty versus loaded trailers
  • Find a specific trailer or all trailers at a specific customer site
  • Monitor door sensor activity
  • Monitor "unauthorized" usage of trailer by customer

Tractor Assignment

  • Assign tractor to empty/full trailer
  • Send a message to driver with trailer pickup location
  • Verify trailer is authorized for shipping
  • Monitor the load status of the trailer to verify it is consistent with the participant's manifest

Connection and Disconnection Monitoring

  • Verify that the driver connects the correct tractor to the correct trailer (empty or loaded)
  • Verify that drops are at an authorized location
  • Monitor for unauthorized drops

Tracking of Trailer

  • Monitor the route of the trip with hourly tractor positions and daily trailer positions
  • Monitor route deviations manually
  • Monitor risk areas with geo-fencing

4.4.3 Configuration

The configurations for Scenario 2 are shown in Table 5. For this scenario, the UTT system sends a status report every 24 hours. The status report includes three key pieces of information: the trailer's current location, and the cargo and door status.

Table 5: Scenario 2 – Trailer Terminal Configuration Settings
Parameter Value
Position reporting interval Once per day
Preset Wake interval 6 hours
Trailer ID, Type, SCAC User-defined
Connections and disconnections Enable
Cargo check interval 30 minutes
Cargo-event messaging Send immediately
Cargo validation interval 10 minutes
Cargo validation rechecks 3
Door close messaging Disabled
Door open messaging Send immediately if cargo = not empty
Door validation open time 5 seconds
Door validation close time 1 minute
Geo-fence messaging Send immediately
Geo-fence check interval 1 hour
Geo-fence size User-defined
Geo-fence center position User-defined

There are two types of configurable intervals: wakeup and validation. Wakeup intervals are defined as an interval that the UTT system wakes up and checks for a variety of events.

  • Preset Wakeup. The UTT system wakes up to check whether there are any new incoming messages to process. For this scenario, this interval is set to every 6 hours.
  • Cargo Check. The UTT system wakes up to check if the cargo status has changed. For this scenario, this interval is set to every 30 minutes.
  • Geo-fence Check. The UTT system wakes up to check whether a geo-fence has been breached. For this scenario, this interval is set to every hour.

Validation intervals are defined as an interval that the UTT system uses to ensure that a state change has actually occurred.

  • Cargo Validation Interval. If a cargo reading indicates that a state is not the same as the previous state, the UTT system will perform a recheck after waiting for the pre-defined interval. This is done to minimize false positive state changes. For this scenario, the pre-defined interval was set to 10 minutes.
  • Cargo Validation Rechecks. If a cargo reading indicates that a state is not the same as the previous state, the recheck may be configured to repeat a number of times before sending a message about the state change. For this scenario, the recheck was set to three times.
  • Door Validation Open/Close. If the door sensor indicates that a door has opened or closed, the UTT system will wait for a pre-defined interval to ensure that the state has really changed. For this scenario, the open validation time is set to 5 seconds and the close validation time is set to 1 minute.

For this scenario, the UTT system checked on the cargo status every 30 minutes with three validation rechecks every 10 minutes following the initial status check. The rechecks only occur when the initial status check indicates that a change of state has occurred.

If the door is closed, the cargo check is initiated after a 1-minute validation recheck of the door state. If a cargo state change is detected, then an OTA cargo status message will be sent, otherwise, no message will be sent.

If the door is opened and the trailer is "not empty," an alert will be immediately sent that the door is open with a "not empty" cargo status. The alert will be sent following a 5-second door validation check.

The UTT system also provides an on-board geo-fence with event-driven exception reporting. In this scenario, exception-driven reporting allows the UTT system to monitor trailer position and check for geo-fence breaks every hour, but send a message only if a geo-fence break is detected. Frequent checking for geo-fence breaks without sending frequent messages lowers messaging costs and increases battery life.

Connection and disconnection information does not include validation intervals. When the tractor-based mobile communications system detects that a trailer has a connection or disconnection, via the 7-way connector interface, it sends a message to the NOC. The NOC then forwards the event to the UTT system's TrailerTRACS Web application, alerting the dispatcher of the connection or disconnection. For disconnections, an alert will be generated. The dispatcher uses the TrailerTRACS Web application to determine if the disconnection was at a valid location, as well as to determine if the cargo status is "not empty" for the applicable trailer.

4.4.4 Logical Architecture and Operational Flow

The architecture and operational flow of information for the technologies used in Scenario 2 are shown in Figure 15.

Figure 15: Scenario 2: Logical Architecture and Operational Flow
Figure 15: Scenario 2 — Logical Architecture and Operational Flow

4.4.5 Daily Operations

This section describes the daily operational procedures that the participants were asked to perform as part of the pilot test.

Daily Operational Procedures

The dispatcher logs onto the trailer-tracking host application in preparation for dispatching drivers to pick up trailers and loads.

Finding Trailer(s)

The dispatcher clicks on the "Find Trailer" tab to search for desired data:

  1. Specific trailer location
  2. Trailers based on cargo status (empty/full)
  3. Trailers near a specific landmark
  4. All trailers

Assigning Trailer(s)

The dispatcher assigns a driver to a trailer pickup:

  1. The dispatcher creates a load assignment/pickup macro instructing the driver where to pick up the next trailer and load.
  2. The satellite-based mobile communications messaging system is used to send the message to the driver.

Connecting Trailer(s)

The driver arrives at trailer pickup location and attaches the tractor to the assigned trailer:

  1. 1. The satellite-based mobile communications terminal detects via the 7-way connector interface that there is an UTT terminal that is connected to the tractor.
  2. 2. The satellite-based mobile communications terminal sends a connect message to the NOC.
  3. 3. The NOC forwards the event to the trailer-tracking host application, alerting the dispatcher of the trailer connection event.
  4. 4. The dispatcher verifies that the trailer is connected to the assigned tractor.

Monitoring Trailer Doors

Upon completing the trailer loading, the trailer door is closed:

  1. The door sensor is automatically engaged when the doors are closed.

Monitoring Trailer(s) En Route

When ready to depart for the destination, the driver sends a "departing macro" to the dispatcher via the satellite-based mobile communications system.

Two mechanisms exist for monitoring the trailer while it is en route:

  1. Trailer positioning (default position interval is one position per day):
    1. If the trailer is pulled by a tractor not equipped with a satellite-based mobile communications terminal or the satellite-based mobile communications terminal is not functioning, the dispatcher monitors the trailer's location using the UTT system via the trailer-tracking host application.
    2. The dispatcher modifies the trailer terminal's positioning frequency to be more frequent than the default (once per hour or once per every 6 hrs) while en route.
      1. The dispatcher enters the setup configuration for a specific trailer to select the positioning frequency parameter.
      2. The trailer-tracking host application creates a message and sends it to the trailer terminal via the NOC and terrestrial network.
  2. Tractor positioning:
    1. If a tractor equipped with a functioning satellite-based communications terminal pulls the trailer, the dispatcher monitors the trailer's location using the satellite-based mobile communications system via the host application.
    2. The default positioning frequency is once per hour. If the dispatcher requires more frequent positioning, the MIPR parameter is modified on the tractor terminal.

Detecting and Disconnecting Trailer(s)

The driver arrives at the destination and disconnects the trailer from the tractor at the designated location:

  1. The satellite-based mobile communications terminal detects that the UTT terminal is no longer connected and sends a disconnection message to the NOC.
  2. The NOC forwards the disconnection event to the trailer-tracking host application and alerts the dispatcher regarding the trailer disconnection event.
  3. The dispatcher verifies that the trailer has been disconnected in an authorized drop location.

Geo-fencing Disconnected Trailer(s)

When the dispatcher receives an alert that a non-empty trailer has been dropped at an authorized location, the dispatcher creates a geo-fence to surround the disconnected trailer:

  1. The dispatcher uses the UTT system host application to create or edit a geo-fence.
  2. The dispatcher selects the center point for the geo-fence (self-centered, landmark, or latitude/longitude), the east/west and north/south lengths, the geo-fence start/stop time, the enable geo-fence flag, the geo-fence wakeup interval, and the type of geo-fence (exit/enter).
  3. The UTT system host application generates a message with the updated information and sends it to the trailer terminal via the NOC and the terrestrial network to the trailer terminal.
  4. An "electronic fence" is set around the trailer, which is monitored by the UTT terminal, based on its configuration.
  5. Using the UTT system host application, the dispatcher has the option to view the geo-fence on a map.

4.4.6 Alerts

The following security alerts were featured in this scenario:

  • Untethered trailer leaves or enters a geo-fenced area
  • Trailer disconnection with a "not empty" load
  • Trailer door opened with a "not empty" load

Untethered Trailer Geo-fence Alert

  • The driver disconnects the trailer in the consignee's yard and sets a valid geo-fence.
  • The trailer terminal wakes up based on the customer configurable setting, every hour, to determine if a geo-fence violation has occurred.
  • If the trailer has left the geo-fenced area, the trailer terminal sends a geo-fence violation alert to the dispatcher.

Disconnection with a "Not Empty" Load Alert

The driver disconnects the trailer in the consignee's yard with a load that is awaiting offload:

  1. The tractor terminal sends a disconnection message.
  2. The trailer-tracking host application receives a disconnection message and generates an alert to the dispatcher.
  3. The dispatcher uses the trailer-tracking host application to determine if the cargo status is "not empty" on the applicable trailer.

Door Opening Event with a "Not Empty" Load

The trailer door opens:

  1. The trailer terminal recognizes that a door opening event has occurred.
  2. The trailer terminal determines, based on the trailer configuration, if an alert is required.
  3. The trailer terminal generates an alert and sends it OTA to the trailer-tracking host application.
  4. The trailer-tracking host application forwards this alert to the dispatcher.

4.4.7 Physical Architecture

The physical architecture and message flow is shown below in Figure 16:

Figure 16: Scenario 2: Physical Architecture
Figure 16: Scenario 2 — Physical Architecture

Previous | Next


Go To Top of Page