WSX - LOADED DISTANCE CApture

The WSX Loaded Distance Capture function sources Odometer readings from Orbcomm, allowing for the calculation of the distance travelled from the Logging Gang to the Customer and assigmment of this distance to the TRP record. This distance data is then passed to Coillte's FMS with the completed TRP data. 

NOTE: As all Odometer readings for are sourced from Orbcomm data, Trimble cannot guarantee the availability or accuracy of any of the distance data captured in this process. Any issues with missing or inaccurate data need first investigated within the Orbcomm system to validate if data was available and accurate at the time the journey was completed.

1. Loaded Distance Capture Process

For each journey in WSX, where the require prerequisite conditions are met (as outlined below), odometer readings are sourced for the times at which the journey is recorded as 'Loaded' and 'At Customer', the difference between these two readings generates the Loaded Distance. 

The following are prerequisites for odometer data to be sourced from Orbcomm for a journey;

1. Truck must be Orbcomm equipped and operational, with tracking data available for the times recorded against the WSX journey for the 'Loaded' and 'At Customer' statuses*

2. Journey must have been completed with auto-status triggers for all three statuses of 'At Crew', 'Loaded, and 'At Customer'. No odometer data will be sourced if any of these three statues are manually set.

3. Journey must be complete, i.e. Empty or Staged**.

For those TRP's where the Loaded Distance has been successfully sourced, this data is passed to the Coillte FMS system once all other requirements for the sending of a TRP to FMS are met. If data is sourced post the TRP being sent to FMS, an update to the TRP is sent to FMS following the addition of the Loaded Distance data.

*Odometer data from Orbcomm is sourced every minute, returning any new data added to their Odometer table since our previous request. This data is added to a temporary table in WSX, with a rolling 2 weeks of odometer data retained. As Orbcomm's odometer data may not always be returned to the Orbcomm server in 'real time', i.e. when trucks are out of coverage, where this data cannot be located for a journey at the time it is completed, WSX will continue to search for this data over a period of 5 days and if located, add this to the journey record. If after 5 days the data cannot be sourced, WSX will cease searching for this record and record against the TRP that the distance was not available.

**Where journeys are Staged, if both journeys related to the Staging Journey have successfully sourced Loaded Distance data, the Loaded Distance assigned to the TRP sent to FMS is the combined distance for both journeys.

Docket List Report

Where the Loaded Distance is recorded against the journey, this displays within the WSX Docket List report. The Docket List report will present the Loaded Distance data in the 'Ld Dist (Odo)' column on the far right hand side of the report, with the following display options based on the results of the attempted data sourcing. Where, 

• Odometer data is available = Calculated Distance displayed (to 2dp)

• Odometer data is not available for Loaded status time = N/A (Loaded ODO missing)

• Odometer data is not available for At Customer status time = N/A (At Cust ODO missing) 

• Odometer data is not available for both Loaded and At Customer status time = N/A (Both ODOs missing)

• At Crew, Loaded or At Customer status are set manually = MS

UPDATE WITH BETTER EXAMPLE ONCE LIVE DATA FLOWING