WSX Mobile - LOader PDT Integration

The WSX Mobile - Crew (Loader) app (referred to here as the 'Loader PDT') can be utilised by Loader Operators and Crew Supervisors at the Logging site to,

View trucks planned to uplift from the site, including proximity notifications
Confirm the load being loaded out or to notify despatch of a discrepancy
View and update log stocks in WSX,
View a history of loads uplifted (for up to 3 months prior) and,
Send and receive text messages to WSX.

This user guide outlines how to establish a Loader PDT within WSX and the interactions that occur between WSX and the Loader PDT application. This guide should be read in conjunction with the Crew (Loader) PDT User Guide on the Trimble Support website, which outlines the key features and functionality of the Loader PDT application.

1. Establishing Voiceless Integration for a cREW LOADER in WSX

The provision of journey data to a Loader PDT(s) is based on associating a Voiceless Activated Loader with either the Gang, or the Gang Location, or both. Each gang can only have one default loader associated with it, however, if multiple loaders (or Loader PDT's) are to be used, those in addition to the Gang Default loader can be assigned at a Gang Location level.

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

Note: The setting 'NotifyLoaderPDT' must be activated for voiceless loaders to operate within a database and to facilitate the return of Stock Calls from the PDT, the setting 'AllowLoaderStockCalls_LogOrg' must also be activated.

1.1Loader Set-Up in WSX (Gang)

A loader for the gang must be established in the WSX Database as per the standard loader set-up, including assigning a Registration, (see the Database Admin User Guide on the Trimble Support website for further details on establishing a Loader). Notes,

As loaders at gangs are unlikely to have a genuine registration number, this should be established in line with the gang code, e.g. if the Loader is set-up with the code 66 BML, the Registration should be 66BML. It is critical the Loader has a unique registration when activating for voiceless.
When creating or adding the Registration, the 'Voiceless' field must be ticked.

1.2 Voiceless Loader Activation

To activate a Loader for voiceless, the associated Loader Owner (in general, the Logging Contractor) must be provisioned in the WSX Security Suite as a "Voiceless Fleet", following which the Registration must also be provisioned against this fleet.

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

1.3 WSX Mobile - Loader Login

A WSX Mobile login must also be established for loader 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 Loader, or contact Trimble Forestry Support if you are unsure.

1.4 WSX Mobile - Loader PDT App Install & Set-Up

To download and install the WSX Mobile app onto a device and to activate this for a specific Gang 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 Gang

To assign a loader to a Gang, from the Gangs screen in Database Admin, select the drop down arrow beside the 'Default Loader' field and select the required loader.

1.6 Assigning a Loader(s) to a Gang Location

To assign a loader(s) to a Gang Location, from the Gang Location screen (accessed from either the Stock Calls or View - Gang Locations screens), within the Loaders area select the ‘Add’ and choose from the available loaders. Repeat this for all required loaders for the Gang Location.

Notes,

The list of available loaders is filtered by default to show only those assigned to a Loader Owner with a code matching that of the Logging Contractor code. You can use the 'Show All Loaders' option to view and add loaders associated to a different Loader Owner.
The Gang Default loader does not need to be added the to the Gang Location; this loader (if voiceless activated) will receive voiceless data for all activities for all locations for the gang.

2. JoURNEY DAta INTEGRATION WITH GANG LOADER PDT

Where voiceless activated loaders are associated with the gang and/or gang location for a journey, journey data will be sent to these when a journey is initially created, and throughout the course of the journey up to the point the the journey status reaching 'Loaded' (when specific changes trigger an automated resend). Journeys can also be sent manually to the loader at any stage of the journey up to the Loaded status.

2.1 Initial Journey Send

When a journey is created in WSX where voiceless activated loaders are associated, you will be prompt with a ‘Send message to all PDT’s’ notification with the following options,

Send – Instigates the send of the journey to the truck (if voiceless activated) and all associated voiceless loaders.
Hold – Does not send the job message to the truck or loaders. When held, a job can only be sent to the PDT manually by right-clicking on the journey and selecting the required ‘Send To...’ option from the drop down, i.e. select ‘Send To Loader PDT’ if you wish the job only to be sent to the loader.
Planned - Does not send the job to truck or loader PDT’s. Journeys set as Planned may be manually sent using a right-click option on the journey or alternatively, are automatically sent to the associated truck and loader(s) PDT’s if a previous job for the truck reaches the 'At Customer' or 'Empty' status.

Note that unlike the Truck PDT, Loader PDT’s do not return an acknowledgement of receipt of the job at the PDT.

2.2 Automated Journey Updates/Resends

Throughout the journey up to the point it reaches the 'Loaded' status, the following events will initiate an automated resend of the journey to the Loader PDT,

Journey & Uplift Changes - Any uplift changes that occur within WSX, including changes to Delivery Dates/Times, Truck/Trailer, Gang & Gang Location, Uplift/Delivery Log Grade, Customer, Docket No., Weights, PDkt, Pieces, Fell Date, etc., will trigger an automatic resend of the journey to the Loader PDT. Note also that if you open the Update Journey screen and click OK to close, with or without making changes, you will be prompt with the option to resend the journey.
Journey status reaches 'Despatched' in WSX - The journey is automatically re-sent to the Loader when it reaches the 'Despatched' status in WSX. It is resent at this time to notify the Loader the truck is on route and also to update the trucks estimated time of arrival at the crew (as the 'Start Time' of the journey in WSX is reset which in turn recalculates the 'At Gang' time)

Journey status reaches 'At Gang Proximity' in WSX - The journey is automatically re-sent when it reaches the 'At Gang Proximity' status in WSX. It is resent at this time to notify the Loader the truck is nearing the loading site along with a Proximity Notification Message (as shown in screenshot to the right).
Journey status reaches 'At Gang' in WSX - The journey is automatically re-sent when it reaches the 'At Gang' status in WSX. It is resent at this time to notify the Loader the truck has reached the site.

2.3 Manual Journey Resends

Journeys can be manually resent either by individual journey, or for all jobs for all loaders assigned to a gang location.

By Individual Journey - Individual journeys can be sent to the Loader using the right click ‘Send to Loader PDT’ option within the Journey screen. Note this option will only resend journeys that are in a status of ‘At Gang’ or earlier.
Send All Journeys for a Gang Location - All journeys for all loaders assigned to the selected Gang and Gang Location, that are in a status of 'At Gang' or earlier, can be resent from within the Stock Calls screen by right-clicking on any stock line and selecting the ‘Resend all jobs to Loader PDT(s)?’ option.

2.4 Journey Removal

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

You can also manually clear all jobs from a single Loader PDT, or all jobs from all Loader’s assigned to a Crew Location, by using the following options,

Stocks Calls Screen - By right-clicking on a stock line item and selecting ‘Delete all jobs from Loader PDT(s)’, all jobs for all loaders associated with the Gang and Gang Location will be cleared.
Loader Association Screen (from ‘View’ menu) - By right clicking on the required Gang Location & Loader combination line item and selecting ‘Delete All Jobs on Loader PDT’, all journeys are cleared for the selected Loader PDT (that have a Log Org matching that of the logged in WSX users associated Log Orgs).
DBAdmin - Loaders Screen - By right clicking on the required Loader and selecting the ‘Delete All Jobs on Loader PDT’ option, all jobs are cleared from the selected Loader PDT, irrespective of Log Org association.

2.5 Journey Status Updates

Gangs using the Loader PDT can also update the status of a journey from ‘At Gang' to ‘Loaded'. The behaviour in WSX from the return of this status is controlled by a WSX Database Setting (StatusTimeOverwriteLoaded_LogOrg), allowing for one of the following options,

An update to the WSX journey to Loaded/X-Loaded with the time set as that returned. This time may then be overwritten by the return of the 'Loaded' status from a voiceless activated truck, or
An update to the WSX journey status to Loaded/X-Loaded and only set the time as that returned where the associated truck is non-voiceless, or
Do not update the journey status and time.

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

2.6 Data Integration Records

Journey notes are recorded against the journey whenever the following interactions occur with the Loader PDT, including identifying the Loader the message was sent from or to,

Each time a journey is sent or removed
Any status updates returned
Load Confirmation (see below)

A record of the Loader PDT login and logout activity is maintained and can be viewed within the Loader Association screen. To view this data select the gang location line that displays with the required Gang, Loader and date; the Login/Logout records will display in the right-hand panel in this screen.

2.7 Text Messages

Text messages can be sent from WSX to the Loader PDT either from,

The New Msg option from within the CPS screen. Note you can filter the list of available Loaders to show only those for Gangs using the filter option below the list of Loader Codes, or
The right-click Send message to Loader PDT option within the Loader Association screen.

Text Messages received from the Loader PDT will display in both the messages area of the CPS screen, and also create an Event Log against the Loader of origin.

3. Load Confirmation

The Loader PDT allows for the ability for the Loader at the gang to acknowledge confirmation of loading the load, or to notify WSX of a discrepancy with the load (in relation to the data presented on the app). Additional to this is the ability to require the capture and return to WSX of other load data by the crew at the time of loading, e.g. Piece Count or Fell Date.

Note: This is not the ability for the Loader/Gang to edit the load details in WSX, or to reject loading a truck

3.1 Defining Load Confirmation by Gang in WSX

The requirement for a Gang to confirm load-out on the Loader PDT can be controlled within WSX, whereby it can be optional either by Gang within a Log Org, or excluded for an entire Log Org. Load Confirmation requirement is established within WSX in two ways,

By Log Org - The Database Setting CrewLoadConfirmReq_LogOrg, must be activated for Load Confirmation to operate for the assigned Log Org.
By Gang - Within the Database Admin - Gangs screen, the Load Confirmation area allows you to establish,
1. - If Load Confirmation is required and,
  - Any additional data required to be captured in the Load Confirmation process, i.e., Piece Count, or Fell Date

Note: The By Gang settings only apply to those Log Orgs activated for Load Confirmation with the above Setting, i.e. if the Log Org is not activated for Load Confirmation these settings are ignored.

Where Load Confirmation is required, WSX will not automatically send a delete job to the Loader PDT(s) on the job reaching the 'Loaded' status unless Load Confirmation has been completed.

3.2 Load Confirmation on the Loader PDT

Where the requirement for Load Confirmation has been assigned to a job sent to the Loader PDT, the user will be required to complete the confirmation either by,

Selecting the CONFIRM button against the job in the Jobs screen, or
Setting the job status as 'Loaded’, where the Load Confirmation has not previously been completed.

When completing load confirmation on the app the user is presented with a screen showing the details of each uplift (docket) with the options to either,

Confirm - Selected where the details of the load on the Loader PDT match that being loaded-out, or
Notify - Send Message - Selected where the load being loaded-out may differ from that shown in the Loader PDT. When selected the user is then prompted to return 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 Load Confirmation settings against the Gang 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.3 Load Confirmation in WSX

When the Load Confirmation process is completed on a Loader PDT, a Load Confirmation Message (Confirmation Message) is returned to WSX. When a Confirmation Message is received by WSX the following occurs,

1. A Journey Note is recorded for each uplift including the Load Confirmation Status, Loader Code, any text message content, the details of the uplift (as they were on the Loader PDT at the time) and any additional data captured by the Loader.

2. An Event Log is created against the Loader which contains the full details of the Load Confirmation. This event will be saved with the status as CLOSED.

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,

Source = WSX Mobile
Driver = Loader Code (of origin for the Confirmation)
Load Details = Exact match to the uplift data as it was on the Loader PDT at the time of return, plus any additional data returned.
Comment = Selected Confirmation option, i.e. 'Confirmed' or 'Notify - Message'.

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.

4. Loadout Records

Contained within the Loader PDT is also the ability for users to view historical job data for loadouts made from the Gang for the previous 3 months.

Once a journey has reached the 'Loaded' status in WSX it is removed from the active jobs on the PDT, and a 'Loadout Record' is generated and passed to the Loader PDT. Loadout Records then comprise History Data on the app, which is used to generate a number of Summary Loadout Graphs.

Notes,

Any critical updates to the journey post the initial send of the Loadout Record to the Loader PDT, will trigger an updated Loadout Record to be sent.
Each Loadout Record sent to the Loader app is recorded in the Journey Notes.
The Loadout history on the Loader PDT will only comprise those loads for which the Loader was associated at the time the load was created and completed.

Page updated

Report abuse