Tracking Event Manager: Detail

This page is accessed via:

• Fleet Management > Visibility > Tracking Event. Click the Detail tab.
• Shipment Management > Visibility > Tracking Event. Click the Detail tab.

Tracking Events are almost exclusively received through integration because they are numerous and real-time. Hand entered events are for exceptions for “missing” critical events that are typically needed to close out cycles such as a delivery cycle. You would normally not “enter” events. The Tracking Event UI is there to view the event details of a single event and the Tracking Event (Finder/Results) are there for diagnostics and analytics since they display critical information for multiple events in an organized manner.

If you do need to enter an event or manually add content, the details are following:

Adding a Tracking Event Manually

1. Click the Detail tab.
2. Enter an External Data Source.
3. Enter an External Event Reference.
4. Enter a Related Tracking Event ID.
5. Select a Service Provider Alias Qualifier.
6. Enter a Service Provider Alias Value.
7. Enter a Tracking Number. A tracking number is a record for tracking a shipment, such as one that a carrier may give you to track a shipment online. Such tracking numbers are associated with reference numbers on shipments, order bases, and order releases. When entering a reference number on one of those business objects, choose a refnum qualifier called "TRACKING_NUMBER".
8. Enter a Contact Function Code.
9. Enter a Contact Name.
10. Enter a Description.
11. Enter a Weight.
12. Enter a Volume.
13. Enter a Temperature.

Vessel

1. Enter a Vessel ID.
2. Enter a Vessel Code Qualifier.
3. Enter a Vessel Code.
4. Enter a Country Code.
5. Enter a Flight or Voyage Number.
6. Enter a Ship or Sail Date.
7. Enter a Discharge or Completion Date.

Rail

Enter details for the rail car:

The time that is provided for an ETA is always qualified by the car destination location. It is highly recommended that the integration include that time zone element.  However, OTM does have the capability to deduce the time zone from the geo-elements that are found in the LOCATION or SPLC tables (SPLC checked first, then location). This is the concept of “local time” that is associated with the car destination location. If neither SPLC or location provide a time zone, the UTC time zone will be used.

1. Enter a Train JCT BO Code to provide a reason for a CLM message.
2. Enter a Railroad Reporting SCAC.
3. Indicate if the rail car is loaded by selecting the Car Loaded check box.
4. The Ahead/Late and Ahead/Late Time fields are read-only. The data is saved to the database when an event XML is received from the shipment status. With a saved condition and query in an agent, you can set the following possible values. These indicate a degree of lateness or stoppage.
   • • A - Ahead of Schedule
     • B - Bad Order
     • H - Held
     • L - Late
     • N - No Bill
     • O - On Time
     • T - Tardy (a degree of lateness).
     • Y - Constructive Placed
     • Z - Actual Placed
5. Enter the Car Destination details. The car destination is a mandatory field on all rail events. It is a critical element because it shows that the car is still headed to the correct city. If this changes, this is a red flag. Industry standards allow the location of the event and the car destination to be provided by a code or a text string. Most reliable is the SPLC code, which is a hierarchical geo-code that is owned by the National Motor Freight Traffic Association. OTM does provide other elements like city and state or the ERPC, which is a 3-3-3 abbreviation system. OTM also provides an agent action to find a LOCATION ID that is based on the SPLC code so that you can see a city name and not a SPLC number. This allows the input to be based on the un-translated raw data that is used by the carriers for accuracy and by familiar names for you to view it.
6. Select Interchange ETA Date. In a multi-carrier rail shipment, there are various carriers who move goods between two locations. Carriers will not serve in all locations. During the transit, at a particular junction carrier changes (because carrier is not serving beyond that junction).This carrier change can be tracked using Interchange ETA Date.
7. Enter Hours to Repair. This specifies number of hours spent on repair, when there is a breakdown between two locations.
8. Enter Next Junction SPLC. This SPLC code indicates the next junction.

Remarks

1. Enter Remarks Text.
2. Click Save for each remark you enter.