Anw: v0.1 - Initial Draft

2017-08-15T13:51:11Z

v0.1 - Initial Draft

New page

{{Template:Estimate
|Supimix_Client_Code=MARS
|Supimix_Project_Code=DEV
|Supimix_Site_Code=.
|Supimix_Client_Reference= 
|Supimix_Number=344239
|The_version_of_the_document=0.1
|Your_Name=A N Walker
|Supimix_PO_Reference= 
|Supimix_Priority=3
|Date_(DD/MM/YY)=15/08/17
|Clients_Customer=Marshalls (Internal)
|System_Version_being_changed=4.X
|Client_Request=If a draw-bar driver has a front end drop as part of a two drop Journey, would it be possible to show this in a linked drop down on the app?
it would be a split drop on some or they may need to trans-ship if the same delivery but only the front end will go in, but for either scenario they would need to drop the trailer at a trailer drop location.

Example Paperwork provided.

Additional discussions with the customer have also drawn out the following requirements:
* We agreed that AX outputs these trailer drop jobs as one job with a single signature for the total qty of goods. The trailer drop instruction is held in the job special instructions read by the driver
* Because of this, we will display these jobs like any other delivery in ePOD, because that’s how they will have been received by us through the interface. Driver notes can be used on the device for the driver to explain any job activity, but essentially these jobs will done the same way as other deliveries in terms of work-flow.
* However, you asked for the functionality accessed from the top right drop down on the ePOD load (manifest list) screen on the device, to have an option for the device to access a table of trailer drop locations, maintained within ePOD Admin, use the device GPS, and suggest the closest to the driver and offer the Nav button (using the TomTom Nav intent). This will try to make sure the driver is going to the optimum nearest trailer drop location.

|OBS_Solution=The supplied examples show that a particular single job was split into two, the first delivery being 10 @10:55, the second delivery being 10 @ 13:45. It is assumed that these jobs will be split into two jobs, both planned onto the same load.

Driver notes will be used to indicate that the second delivery is a Draw-bar delivery.

{{Note}} There will be two jobs, and therefore two POD notes, one for the first trailer (from the drop-bar) then from the second (main) trailer.

It is assumed that the whole load would look similar to the following:

Assuming the fixed trailer is "1" and the drop-bar trailer is "2":
# Go to A and drop something from trailer "2"
# Go to B and drop something from trailer "2" - drop-bar is now empty.
# Go to C and drop something from trailer "1"
# Go back to A and drop something from trailer "1"
# Return to depot.

It is asumed that the functionality required is an ad-hoc step between steps 2 and 3:
# Go to A and drop something from trailer "2"
# Go to B and drop something from trailer "2" - drop-bar is now empty.
## '''''Select "nearest" trailer drop location from drop-down list.'''''
## '''''Navigate to location'''''
## '''''Drop off trailer "2"'''''
# Go to C and drop something from trailer "1"
# Go back to A and drop something from trailer "1"
# Return to depot.

To achieve this, the system will be modified as follows:
* Trailer drop locations will be entered within the ''CALIDUS'' ePOD Admin system and identified as such. Each must have a Lat/Long, although it is noted that this can be calculated through Geolocation request webservices.
* An option will be added to the mobile device application to allow the driver to select an option "Trailer Drop-Off" from the menu on the Job List screen.
* This will allow the driver to find the closest trailer drop-off location and generate a job to drop off the trailer.
* This will be fully visible within ''CALIDUS'' ePOD Admin, as the jobs generated in this way will be displayed against the load.

The process would then be as follows:
* Assuming a load of ID "MAR-00001"
* All jobs identified with the trailer being used for that job's product (in this example, "1" or "2").
* Go to A and drop something from trailer "2"
* Go to B and drop something from trailer "2" - drop-bar is now empty - instructions on the job show this.
* Select "Trailer Drop Off" from the menu on the Job List.
* Select the Trailer Drop-Off location from the list, sorted in "as the crow flies" nearest distance to the last known location of the mobile device.
* Create a "TDO_MAR-00001_01" delivery job to this location and start it.
* The driver can click the navigation button to navigate to this location. As this is determined to be an Ad Hoc job, we can navigate directly to the job. That means that, even if Premier activate WEBFLEET jobs through reach in the future, these Ad Hoc TDO jobs ALWAYS navigate directly, not displaying the WEBFLEET orders list.
* Driver arrives and completes the job. Note that this job type is expected to be a simple job that requires only a Complete button to be pressed. However, if this job requires some additional data entering at the drop-off location, this can be configured through the standard UDF configuration in C-ePOD. The same is true as to whether any signatures or images are captured after dropping off the trailer.
* Go to C and drop something from trailer "1"
* Go back to A and drop something from trailer "1"
* Return to depot

This Ad Hoc TDO job will be explicitly tracked in the C-ePOD Admin system and returned in the export interface, should this be enabled at a later date.

|Requirements_Days=0
|Estimation_Days=0.0
|Functional_Specification_Days=2.5
|Technical_Specification_Days=0
|Development_Days=11
|Testing_and_Release_Days=2.0
|Implementation_Days=0.25
|Project_Management_Days=0.75
|Year=2017
|Free_Of_Charge=N
}}

EST 344239 Trailer Drop Functionality - Revision history

Anw: v0.1 - Initial Draft