FS 336013 SCR-332569-4 GK PvA Automatically Set Loads In Progress

From Calidus HUB





Aptean Logo.png







Greene King

Automatically Set Loads In Progress

CALIDUS EPOD

23rd August 2016 - 1.0
Reference: FS 336013 SCR-332569-4











































Functional Overview

Client Requirement

Once the DiPS import is complete, the drivers will require the ability to execute the jobs through TomTom WEBFLEET. In order to achieve that, CALIDUS ePOD must generate the orders on to TomTom WEBFLEET. A process already exists to complete that, when loads are set to In Progress. The setting of loads to this status is normally achieved through the CALIDUS ePOD devices requesting a load. As CALIDUS ePOD will not be in use at this time, a process will be required to automatically set the status of the earliest loads for a vehicle to In Progress.


Solution Overview

The process will be capable of being configured by Site (Depot). Any loads at status In Progress or Pending will be checked and the earliest load for that vehicle will be marked in progress. This will then automatically trigger a requirement to send this load to TomTom WEBFLEET. If there was already a load in progress for the vehicle, this load will be changed back to Pending and TomTom WEBFLEET will be informed to remove any jobs associated to this load from the worklist.

Notes:

  • Only vehicles configured with a TomTom External ID within CALIDUS ePOD will have orders sent to them.
  • Only jobs that are not yet complete will be sent to TomTom WEBFLEET.
  • Only Loads In Progress will be sent to TomTom WEBFLEET.


Scope

Note Note: Parts of the testing of this change will be completed with 336010/SCR-332569-2 DiPS-ePOD Interface for Load and Order Sequencing. 


Set-up

Pre-requisites

Menu Structure

Data

Functional Description

Database/DAL

A new EPOD_SITE flag will be added to control automatically setting loads in progress.

  • EPL_AUTO_IN_PROGRESS_LOAD_IND - numeric flag, defaulting to 0.

This should be added to all database procedures and DAL objects. It is not necessary to add this as a searchable item.


Admin

A new value to the existing Site-level flag System Type will be added to control PvA-specific functionality.

The new value will be "PVA", description "Planned vs Actual".


System

Whenever a load has the status updated to Complete or Cancelled, or has the vehicle changed, or has the start planned date or time changed, the process will check the following:

  • That the vehicle has an external ID (i.e. is enabled for WEBFLEET).
  • That automatic status change to In Progress is required (through the new value of the system flag)
  • That this is the earliest planned load for that vehicle.

If this is the case, the Load Status should be set to In Progress and then call the following two existing procedures: 

   // Update other loads for this user or vehicle but if only if the load has successfully been updated
   EPOD_LOAD.LoadUserOrVehicleChanged();
   // Create EPOD_XF_CONTROL record if the load has successfully been updated
   EPOD_LOAD.CreateXFControlRecord();

These will have the following effect:

  • Check the load for changes of vehicle/user
  • Create the record to process the sending of the Load and all jobs to WEBFLEET if required.
  • Change any prior Loads in progress to Pending.

This new check should be created as a new method of the EPOD_LOAD object.


The Load Status may be updated from the following procedures:

  • The Load Assignment screen (load_assignment.aspx)
  • The Load Header admin screen (load_header.aspx)
  • When Loads are updated through the Upload process (Upload.aspx)
  • When Flat File Uploads are processed automatically (EPOD_DATAPROCESS.cs)
  • When External Webservices update loads (EPOD_DATASERVICE.cs and MessageProcess.cs)
  • When a device updates loads (MessageProcess.cs)

Note Note: This is not a complete list - ALL areas should be modified.

The new procedure for processing DiPS files (in EPOD_DATAPROCESS.cs, specified in 336010/SCR-332569-2 DiPS-ePOD Interface for Load and Order Sequencing) should also be changed for this purpose.



Appendix A: TEST PLAN

Test Script / Scenario ReferenceAutomatically Set Loads In ProgressCall Number(s): 336013 SCR-332569-4
Test Script / Scenario DescriptionTest loads automatically set to in progress.PASS / ISSUES / FAIL
Menu AccessN/A 
Pre-requisitesN/ATested By:
 
Test ObjectiveTo test that; the Site flag may be properly configured by the Admin system; any mechanism of changing the load status, date or vehicle results in the load being set to In Progress, any previous load being reset, and the new load being sent to WEBFLEET.Date:
 



Step Action Result Remarks P/F
1 Admin Maintenance      
       
1.01 Edit the new flag so that this is set to the new value, and save the changes. The flag may be edited and changed to the new value.    


Step Action Result Remarks P/F
2 Auto Load In Progress      
  Ensure the Site System flag is set to PvA initially.

Ensure that there are at least 2 vehicles, one with an external ID and one without. Ensure that there is are at least 2 loads per vehicle.

Ensure WEBFLEET interfaces are enabled for this site.		      
2.01 Add a new load for a WEBFLEET-enabled vehicle through the Webservices. Ensure this is the earliest planned date. The load should be set to In Progress. A message for this load should be set on the XF Control. Messages should be sent to WEBFLEET for the jobs on this load.    
2.02 Amend another load for the same Vehicle to be an earlier planned date/time in the Load screen. The load should be set to In Progress. A message for this load should be set on the XF Control. Messages should be sent to WEBFLEET for the jobs on this load. The original In Progress load should be reset to Pending.    
2.03 Update the original load to an earlier date using a Flat File format. The load should be set to In Progress. A message for this load should be set on the XF Control. Messages should be sent to WEBFLEET for the jobs on this load. The original In Progress load should be reset to Pending.    
2.04 Update the load to a later date using the Load screen. The load should be set to status Pending. The earlier load should be set to status In Progress. A message for this load should be set on the XF Control. Messages should be sent to WEBFLEET for the jobs on this load.    
2.05 Deallocate the In Progress load from this vehicle. The load should be set to status Pending. The earlier load should be set to status In Progress. A message for this load should be set on the XF Control. Messages should be sent to WEBFLEET for the jobs on this load.    
2.06 Allocate the load to a vehicle without WEBFLEET integration. Nothing.    
2.07 Allocate the load to a WEBFLEET vehicle. Complete all jobs on the Load (through ePOD or WEBFLEET). The load should be completed. The next load for that vehicle should be set to status In Progress. A message for this load should be set on the XF Control. Messages should be sent to WEBFLEET for the jobs on this load.    
2.08 Cancel the next load through the Admin screen. The load should be cancelled. The next load for that vehicle should be set to status In Progress. A message for this load should be set on the XF Control. Messages should be sent to WEBFLEET for the jobs on this load.    
2.09 Set the System flag back to Generic. Add an earlier load for the WEBFLEET enabled vehicle through Webservices. The load should be created but not automatically set in progress.    


Appendix B: Quote & Document References

Cost Details
Activity Estimate
No. of Days		 No. of Days Rate per Day (£) Cost (£ Exc. VAT)
Requirements 0.00 0.00 750 £0.00
Change Request Evaluation 0.00 0.00 750 £0.00
Functional Specification 0.25 0.25 750 £187.50
Technical Specification 0.25 0.25 750 £187.50
Development 1.75 1.75 750 £1,312.50
Testing and Release 0.25 0.25 750 £187.50
Implementation 0.00 0.00 750 £0.00
Project Management 0.25 0.25 750 £187.50
 
TOTAL 2.75 2.75   £2,062.50
Estimate excludes training, release to live and go live support.

B.1 References

Ref NoDocument Title & IDVersionDate
1336010/SCR-332569-2 DiPS-ePOD Interface for Load and Order Sequencing1.023/08/2016


B.2 Glossary

Term Definition
EPOD Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD.
CALIDUS eSERV The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system.
PDA The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android.
DAL Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it.
GPS Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device.
GPRS, 3G, HSDPA, Data Service All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet.


B.3 Authorised By


Rob Carter
Greene King Representative		_____________________________

Matt Tipping
OBSL Representative		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=FS_336013_SCR-332569-4_GK_PvA_Automatically_Set_Loads_In_Progress&oldid=3508’