View source for EST 315766 K-2 Consolidation of Arrival Time

{{Template:Estimate
|Supimix_Client_Code=PART
|Supimix_Project_Code=DEV
|Supimix_Site_Code=PART
|Supimix_Client_Reference=K-2
|Supimix_Number=315766
|The_version_of_the_document=0.2
|Your_Name=A Walker
|Supimix_PO_Reference=Unknown
|Supimix_Priority=3
|Date_(DD/MM/YY)=27/02/2014
|Clients_Customer=N/A
|System_Version_being_changed=Latest
|Client_Request=Consolidation of Arrival time for same delivery points
|OBS_Solution={{#vardefine:System|''CALIDUS'' ePOD}}
{{#var:System}} will consolidate jobs when received from Partnerlink members through the Job Share interface under the following conditions:
* Delivery jobs on the same Load with the same Delivery address (i.e. Lines 1-5 and Postcode)
* Collection jobs on the same Load with the same Collection address (i.e. Lines 1-5 and Postcode)

Jobs that have been pre-consolidated in this way will be displayed as a single line on the Job List screen on the Android device. The layout of these rows will be modified slightly to make it clear that this row represents a consolidated group of jobs, and the number of jobs in that group.


The user will also be able to create a consolidated group of jobs manually, by long holding on a row, starting a 'Consolidation Mode', and selecting the jobs (or existing groups of jobs) to merge together. There will be some criteria that will be checked when selecting jobs, to ensure that only jobs that can be consolidated together are selected. When complete, these selected rows will be merged into one on the device, displaying just like a pre-consolidated group of jobs. It will also be possible to break these groups back down, in case of any mistakes.

This manual consolidation of jobs can be completed before leaving the depot, on all jobs that need it, or as the deliveries are being made, on demand. In either case, the device will remember any consolidations made on this load for the duration of the load, as long as the load is not taken away from the user, or reloaded onto the device from scratch.


Completing consolidated groups of jobs will be very similar to completing a single job. For example, the user will still be able to:
* Select the group to see the details
* Start and Arrive to the group of jobs
* Scan, enter or select the containers (parcels) to be delivered or collected on that group of jobs
* Obtain a customer signature for the group of jobs, showing the containers and any terms and conditions.
The differences in processing are to allow the user to see details of each of the jobs in the group. For example:
* When the group is selected, the Job Detail screen will allow the user to scroll through all the jobs in the group, so that they can see the details of all the individual jobs in the group, including:
** Contact details (Name, telephone)
** Job Address details
** Any special instructions for the group of jobs, all collected onto one scrollable page, for ease of use.
* When arrived at jobs and starting to complete the group of collections or deliveries, the user will also be able to scroll through these job details again, to help find the right contacts for the jobs.
* The list of pallets to be delivered will show all the pallets for all the grouped jobs together. The list will be grouped by the sequence {{#var:System}} received them, for deliveries, and the reverse order, for collections. The list of pallets will also show a little more information, allowing the user to see the Job that the item came from, to help in visually identifying items together.
* The user can break all the items from a job out of a consolidation from the list of all the pallets in one long-press from the list of pallets, in order to reflect where a user is refusing to sign for one or more of the jobs in the consolidation, but will sign for others. In that case, the jobs broken out (deconsolidated) will be put back on the Job List for completion as single jobs.


When all pallets have been collected or delivered, the device will move on to job confirmation. This will work as it does for single jobs, in that it will request only one customer signature. This screen will show all the collected or delivered items here, as well as the chosen terms and conditions from the first job. Collection from and deliveries to a depot (i.e. loading and unloading tasks) may be configured to not require a signature at all.


When complete, all the jobs will updated to the Partners' TMS systems with the same signature information for all the jobs that were consolidated together.


{{Note|
* This functionality will be developed in the Android application only.
* The scanning functionality for Containers/pallets depends on the IDs for these items being unique for all the packages for jobs within the network.
* No functionality will be added to the {{#var:System}} Admin screens to allow for jobs to be consolidated there before execution by the device.}}

|Requirements_Days=0
|Estimation_Days=0.25
|Functional_Specification_Days=1.0
|Technical_Specification_Days=0
|Development_Days=5.0
|Testing_and_Release_Days=2
|Implementation_Days=.25
|Project_Management_Days=1.0
|Year=2014}}