WSX Mobile - Customer PDT Integration

The WSX Mobile - Customer app (referred to here as the 'Customer PDT' as this is the more commonly known name) can be utilised by Loader Operators and Yard Foreman at the Customer site to 

• View planned deliveries and receive proximity notifications,

• Confirm receival of loads, 

• View delivery history, and 

• Message Despatch (WSX). 

This User Guide outlines how to establish a Customer PDT within WSX and the interactions that occur between WSX and the Customer PDT application.

Note: This user guide should be viewed in conjunction with the Customer (Loader) PDT User Guide on the Trimble Support website, which outlines the key features and functionality of the Customer PDT application.

1. Establishing Voiceless Integration for a customer in WSX

The provision of delivery data to the Customer PDT is based on associating Voiceless Activated Loaders with the Customer. Each customer may have one or more voiceless activated loaders assigned to them, which will be provided with job data from WSX for deliveries to their associated customers.

The following steps must be taken to establish a loader as voiceless active in WSX, and to then assign that loader to the customer.

Note: The setting 'NotifyLoaderPDT' must be activated for voiceless loaders to operate within a database.

1.2 Voiceless Loader Activation

To activate a Loader for voiceless, its associated Registration must be enabled for voiceless. This requires the associated Loader Owner (in this case, the Customer) to be provisioned in the WSX Security Suite as a Fleet for voiceless, and the Registration also to be provisioned.

Please use this link to request a voiceless loader activation or contact Trimble Forestry Support if you are unsure.  

1.3 WSX Mobile - Customer Login

A WSX Mobile login must also be established for the operator(s) wishing to login to the app (if this was not requested at the time the voiceless loader was established). 

Please use this link to request a WSX Mobile login for the customer, or contact Trimble Forestry Support if you are unsure.

1.4 WSX Mobile - Customer App Install & Set-Up

To download and install the WSX Mobile app onto a device and to activate this for a specific Customer Loader, please click on this link and follow the steps in order. 

If you encounter any issues when setting up the WSX Mobile app please first refer to the Troubleshooting items on the Trimble Support website and if following this you are still unable to resolve the issue, please contact Trimble Support.

1.5 Assigning a Loader to a Customer

To assign a loader(s) to a customer, from the Customers screen in the Database Admin, within the Loaders area select the ‘Add’ option and choose from the available loaders. Repeat this for all required loaders for the Customer. Notes,

• The list of available loaders is filtered by default to show only those set as a 'Customer Loader'. 

• The loaders displayed are not filtered to show only those for the selected customer and will display all loaders set as ‘Customer Loaders’ in the database with an associated Log Org matching one or more of the Log Orgs associated with the customer.

2. JoURNEY DAta INTEGRATION WITH WSX Mobile - Customer

Journeys created in WSX to customers with voiceless active loaders are automatically integrated with the Customer PDT, and may also be manually sent or removed if required.

2.2 Journey Removal

A journey is automatically removed from the Customer PDT when the journey reaches the Unloaded or Empty status in WSX, where 'Delivery Confirmation has either been received, or is not required (see section below on Delivery Confirmation).

The ability to delete all jobs from the Customer PDT (for Log Orgs to which the user has access) exists as a right-click, "Delete all jobs from Loader PDT" option within the Loader Association screen.

The option to fully clear a Loader PDT of all jobs, irrespective of Log Org, exists as a right-click option in the  Database Admin - Loaders screen.

2.3 Journey Status Updates

Customers using the Customer PDT can also update the status of a journey from ‘At Customer’ to ‘Empty'/'X-Empty’ (displayed as 'Unloaded' on the PDT). The behaviour in WSX from the return of this status is controlled by a WSX Database Setting (StatusTimeOverwriteEmpty_LogOrg), allowing for one of the following options,

1. An update to the WSX journey to Empty/X-Empty with the Empty time set as that returned. This time may then be overwritten by the time the Empty/Unloaded status is returned from the WSX Mobile - Truck app, or

2. Do not update the journey status or Empty time from the status return.

In all cases, a Journey Note will be recorded showing the Empty status was received from the Customer PDT, with associated details.

3. Delivery Confirmation

The Customer PDT allows for the ability for the customer to confirm receival of a load, or to notify despatch of a discrepancy with the load (in relation to the data presented on the app).

Note: This is not the ability for the Customer to edit the load details in WSX, or to reject a load

3.1 Defining Delivery Confirmation by Customer in WSX

The requirement for a customer to confirm load receival on the Customer PDT can be controlled within WSX, whereby it can be optional either by Customer within a Log Org, or excluded for an entire Log Org.

Delivery Confirmation requirement is established within WSX in two ways,

1. By Log Org - The Database Setting CustomerDelvConfirmReq_LogOrg, must be activated for Delivery Confirmation to operate for the assigned Log Org.

2. By Customer - Within the Database Admin - Customers screen (see screenshot below), the Delivery Confirmation area allows you to establish,

   • • If Delivery Confirmation is required and,

     • Any additional data required to be captured in the Delivery Confirmation process, i.e., Piece Count, Fell Date, Volume, Reference (PDkt) and Net Weight

Note: The By Customer settings only apply to those Log Orgs activated for Delivery Confirmation, i.e. if the Log Org is not activated for Delivery Confirmation these settings are ignored.

Where Delivery Confirmation is required for the combination of Log Org and Customer, WSX will not delete the job from the Customer PDT when the job reaches the Empty/Unloaded status unless Delivery Confirmation has been received.

1. Confirm - Selected where the details of the load on the Customer PDT match that being delivered, or

2. Notify - Selected where the load being delivered may differ from that shown in the Customer PDT. When selected the user is then prompted to select a notification reason, with options to select either,

   1. • Log Grade - when selected this prompts the user to select a new Log Grade. The available Log Grades to select from are those associated to the customer with a Log Org matching that of the uplift Log Org.  Following selection of the new Log Grade the user can also add a text message - this is optional.

Note: This does not change the Log Grade against the uplift in WSX. It is a notification of a discrepancy, NOT a job edit (see below)

2. 1. • Other - when selected this requires the user to complete a free-form text message outlining the discrepancy with the load - completing the message is mandatory for this option.

In addition to the Confirm or Notify options the user will be able to add Additional Data to the confirmation message, as specified by the Customer Delivery Confirmation settings against the customer in WSX.

Once all the selections above are made a ‘Confirmation Message’ is then sent to WSX including the ‘Confirm’ or ‘Notify’ status, any text message added, all details associated with the uplift and any additional data recorded. 

3. An External Data Record is created and displayed against the docket record in the Electronic Validation screen (see screenshot below). This line presents as follows,

1. • • Source = WSX Mobile

     • Driver = Loader Code (of origin for the Confirmation)

     • Load Details = Where the confirmation returned is,

       • • Confirmed - Details are an exact match to the uplift data as it was on the Customer PDT at the time, plus any additional data returned. 

         • Notify - Log Grade Change - Exact match to the uplift data as it was on the Customer PDT at the time with the exception being the ‘Sold As’ grade displays as that returned in the confirmation message, plus any additional data returned. Note,

         • Notify - Message - Exact match to the uplift data as it was on the Customer PDT at the time, plus any additional data returned. Note, 

       • Comment = Selected Confirmation option, i.e. 'Confirmed', 'Notify - Message' or 'Notify - Log Grade Change'

Notes: 

• The WSX uplift (docket) record is not updated by any data from the Confirmation Message. 

• Additional Data returned in this process will not be added to the WSX record, it will only display in the External Data Record as a reference.

  • When a ‘Notify’ is returned the docket will be set as ‘E-Error’, thereby alerting the requirement to review the record as part of the docket validation process.