FS 336014 SCR-332569-5 GK PvA ePOD-WEBFLEET Mods

From Calidus HUB





Aptean Logo.png







Greene King

ePOD-WEBFLEET Interface Modifications

CALIDUS EPOD

23rd August 2016 - 1.0
Reference: FS 336014 SCR-332569-5











































Functional Overview

Client Requirement

Some slight modifications to the way that data is sent to TomTom WEBFLEET for orders will be undertaken

Solution Overview

  • Job Instructions will include the order reference to be displayed.
  • The Planned Date and Time will be amended to be the Expected Arrival Date and Time (Planned Start Date/Time within CALIDUS ePOD).


Scope

Set-up

Pre-requisites

Menu Structure

Data

Functional Description

Auto-Export

Some slight modifications to the way that data is sent to TomTom WEBFLEET for orders will be undertaken:

  • Job Instructions will include the order reference to be displayed.
  • The Planned Date and Time will be amended to be the Expected Arrival Date and Time (Planned Start Date/Time within CALIDUS ePOD).

Currently the Order Text sent to WEBFLEET is the Job Instructions only. This will be modified so that the Job Code is inserted before the Instructions, so that it can be visible on the device when completing the job. Where jobs are consolidated, the Job Code of all the jobs should be present, concatenated with a slash ("/") character. The Job Code is expected to be populated with the ORDER OR SHIPMENT IDENT from the DiPS interface (example "3031298"). The Job Instructions is expected to be populated with ORDER SPECIAL DELIVERY INST (example "pls call 30m b4 del 07970884489 Kul"), and the concatenated weight and quantity (example "179 KILOGRAM, 6 D-RB, 33 W+S").

The final instructions sent to WEBFLEET will then be as follows: 

   "3031298 pls call 30m b4 del 07970884489 Kul 179 KILOGRAM, 6 D-RB, 33 W+S"
   "6030158/6029870 pls call 30m b4 del 07970884489 Kul 179 KILOGRAM, 6 D-RB, 33 W+S"


Currently the End Planned date and time are sent to WEBFLEET as the Scheduled Completion Date and Time. This will be modified to be the Start Planned Date and Time. This will be populated in the interface from DiPS as EAT AT CALL.


Developer Notes:


The data is populated in method EPODServer.EPOD_SYS_EXPORT.TomTomOrdersGetRequestXML.

strOrderText will now be populated with: 

   drData["EPL_JOB_CODE"].ToString()).Trim() concatenated with (drData["EPL_JOB_INSTRUCTION"].ToString()).Trim()

Dates will now be populated with: 

   iDate = (int)drData["EPL_END_PLANNED_DATE"];
   iTime = (int)drData["EPL_END_PLANNED_TIME"];

Given the nature of the way that data is populated in the interface, there is no need to control this data population with flags in the system.


Appendix A: TEST PLAN

Test Script / Scenario ReferenceePOD-WEBFLEET Interface ModificationsCall Number(s): 336014 SCR-332569-5
Test Script / Scenario DescriptionTest modifications to the WEBFLEET interface.PASS / ISSUES / FAIL
Menu AccessN/A 
Pre-requisitesAn active WEBFLEET orders interface.Tested By:
 
Test ObjectiveTo test that orders are created in WEBFLEET with the new details.Date:
 



Step Action Result Remarks P/F
1 WEBFLEET Export      
  Ensure an active WEBFLEET interface is created.      
1.01 Create a load with jobs - ensure the Start and End Planned Dates and Times are different, that the Job Codes are set and different, and that the Instructions are populated. Assign the load to a WEBFLEET-enabled vehicle. In WEBFLEET, the orders should be created on that vehicle with Dates/Times as per the Planned End Date, and the Instructions are populated with the Job Code as well as the instructions.    
1.02 Create a load with consolidated jobs - ensure the Start and End Planned Dates and Times are different, that the Job Codes are set and different, and that the Instructions are populated. Assign the load to a WEBFLEET-enabled vehicle. As the prior test, but the consolidated jobs should have all of the Job Codes listed on the instructions.    


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.00 0.00 750 £0.00
Development 0.50 0.50 750 £375.00
Testing and Release 0.25 0.25 750 £187.50
Implementation 0.00 0.00 750 £0.00
Project Management 0.00 0.00 750 £0.00
 
TOTAL 1.00 1.00   £750.00
Estimate excludes training, release to live and go live support.

B.1 References

Ref NoDocument Title & IDVersionDate
1   


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_336014_SCR-332569-5_GK_PvA_ePOD-WEBFLEET_Mods&oldid=3509’