FS 325463SCR HEW-005 5 New POD Formats

From Calidus HUB
Revision as of 17:37, 1 April 2015 by Anw (talk | contribs)





Aptean Logo.png







Hewicks Haulage

5 New POD Formats

CALIDUS EPOD

1st April 2015 - 0.2
Reference: FS 325463 SCR-HEW-005











































Functional Overview

Client Requirement

When an order is completed on the mobile device application, the POD note can be generated from the CALIDUS EPOD Admin console. There is also the option for an automatic email to be sent to the customer. Hewicks Haulage require this functionality with the option of sending the POD document to multiple recipients in PDF format

There are 5 POD/POC documents required to be developed to match the formats provided. The POD notes used will be determined by the Job Group that has been assigned to the orders at order entry.


Solution Overview

The CALIDUS EPOD system will be modified to:

  • Add new Hewicks Haulage POD and POC formats to the system
  • Allow configuration of Job Groups and Sites to allow them to be configured to use the new formats.

Note Note: There are data configuration and standing data requirements for the reports to function as required - these will also be detailed in the sections below.


Scope

The changes will be made to the latest version of the CALIDUS EPOD system.


Set-up

Pre-requisites

A valid CALIDUS EPOD system is required.


Menu Structure

None


Data

Site

FS 325463 Site Maint1.PNG FS 325463 Site Maint2.PNG
Site Maintenance

Site "HEW" created with the following minimum configuration enabled:

  • Capture Arrival Times
  • Driver Sign Collection
  • Link C & D on Job Code
  • User Notes
  • Send Full Address
  • Metrics Entry: Load Metrics at Load Start
  • Resequencing Options: Free to Resequence
  • Display Job Code on PDA: Job Code/Order No

The POD and POC notes may be set to any format, as the CALIDUS EPOD system will use the values against the Job Group to configure the application for the jobs.


Job Group

FS 325463 Job Group Maint1.PNG FS 325463 Job Group Maint2.PNG
Job Group Maintenance

Job Groups created for

  • HEWICKS
  • CAVE
  • HEWPODPOC

The following parameters should be set (unless there is specific configuration below).

  • Details:
    • POD Format: "Hewicks POD"
    • POC Format: "Hewicks POC"
  • Admin:
    • Auto Email
  • PDA
    • Driver Sign Collection
    • Customer Sign Collection
    • Customer Sign Delivery
    • User Notes
  • Terms & Conditions
    • "I (the customer) do hereby declare that the service contracted for has been carried out to my complete satisfaction."


Specific configuration for HEWPODPOC:

  • Details
    • POD Format: "Hewicks POD/POC"
    • POC Format: "Hewicks POD/POC"
  • PDA
    • Driver Sign Collection DISABLED
    • Customer Sign Collection may be enabled or disabled as required. It is recommended that this is left as Enabled.


Job UDF configuration for HEWICKS and CAVE job groups (as this is assumed this is not required for HEWPODPOC): A new EPOD_UDF_CONFIG record will be created for the job groups above by OBS Logistics' staff during implementation:

  • EPL_DESCRIPTION = "Job Details"
  • EPL_KEY_TYPE = "J"
  • EPL_KEY_VAL = "HEW|{EPL_JOB_GROUP}"
  • EPL_CONFIG_TYPE = "JOBDETS"
  • EPL_UDF_FIELDS - as below:
<FORM NAME="Job Details" REQUIRED="Y">
   <FIELD ID="WB_NUMBER">
       <TEXT>Weighbridge Number</TEXT>
       <FORMAT>T</FORMAT>
       <REQUIRED>Y</REQUIRED>
   </FIELD>
   <FIELD ID="DEMURRAGE">
       <TEXT>Demurrage</TEXT>
       <POST>Minutes</POST>
       <FORMAT>N</FORMAT>
       <REQUIRED>N</REQUIRED>
   </FIELD>
</FORM>


Customers

FS 325463 Customers Maint1.PNG
Customers Maintenance

Customers set up for

  • HEWICKS
    • Name: HEWICKS HAULAGE LTD
    • Address 1/2/3/4: "LOFT FARM", "COCKFIELD", "BURY ST EDMUNDS", "SUFFOLK"
    • Postcode: "IP30 0LJ"
    • Telephone Number: "01284 826020|01284 827614"
    • Contact: "www.hewickshaulage.co.uk"
    • Address 5: "TASCC No: XY161"
  • CAVE
    • Name: "CAVE LIQUID HAULAGE LTD"
    • Address 1/2/3/4: "MARAZION", "GREAT SHODDESDEN", "ANDOVER", "HAMPSHIRE"
    • Postcode: "SP11 9LP"
    • Telephone Number: "07860 562132"
    • Contact: "www.caveliquidhaulage.co.uk"
    • Address 5: Blank.
  • HEWPODPOC
    • As HEWICKS


Functional Description

Admin Changes

Site Maintenance

FS 325463 Site Maint1.PNG
Site Maintenance

The CALIDUS EPOD Admin Site Maintenance screen will be modified to allow the user to select the new POD and POC formats being created as part of this specification:

  • Hewicks
  • Cave
  • Hewicks POD/POC


Job Group Maintenance

FS 325463 Job Group Maint1.PNG
Job Group Maintenance

The CALIDUS EPOD Admin Job Group Maintenance screen will be modified to allow the user to select the new POD and POC formats being created as part of this specification:

  • Hewicks
  • Cave
  • Hewicks POD/POC

The table on the screen will display these values if selected against the Job Group.


POC 1 format

A prototype of this format has been created:

FS 325463 HEW CAVE POC.PNG
Cave Liquid Haulage POC

The individual fields will be populated as follows:

  • Ticket No: Job ID - the unique id of this collection job.
  • Title and Address: The title name and other information will be gathered from a customer record created with the details against it, as follows:
    • Title: Customer Name
    • Address: From the first 4 lines of the customer address (comma delimited) and the postcode
    • Tel: Extracted from the telephone number. If a fax number is required, this may be entered in the same place, with a vertical bar (|) separating them.
    • Web: From the Contact.
  • Customer Name and Address: Invoice address (Address from the Customer selected against the job).
  • Collection Address: Alternate Job Address or, if this doesn't exist, the customer address above.
  • Product/Material Carried: The Product Description from the first Product found on the Collection job.
  • Date: Actual Arrival Date
  • Driver: Name of the POD user that completed the job on the load.
  • Vehicle Reg: Registration of the vehicle used to complete the load.
  • Trailer No: Trailer ID entered when starting the load.
  • Driver Signature: Signature captured from the driver when completing the job.
  • Time Arrived: Actual Arrival Time
  • Time Departed: Actual End Time
  • Demurrage: Taken from the details manually keyed by the Driver against the job when collecting it. If this is not entered, this will be blank on the report.
  • Weighbridge Ticket No: Taken from the details entered against the Job when collecting it.
  • Net Weight: The Product Quantity from the first Product found on the Collection job.
  • Driver Comments: Any notes entered against the job by the driver using the Notes tab, when completing the job.
  • Last Three Loads: Note Note: This is a new function, specified in SCR 325465/SCR-HEW-006 and referenced in Appendix A, the result of which will be the last three jobs that were completed using this trailer, along with the information from the first product found on those jobs. Although this function is not yet defined, this section will display the three product descriptions.
  • Delivery name and address: The delivery address from the delivery job that is linked to this one (i.e. on the same load with the same Job Code). The address used will be the Alternate Job Address if present, otherwise the address from the customer selected against the delivery job.
  • Delivery Ref No: The Job ID of the linked delivery job - this is the unique Job ID of the delivery on this load with the same Job Code as the collection job.
  • "I (the customer).. complete satisfaction.": This will be taken from the configured Terms and Conditions against the Job Group.
  • Signed: The Signature image from the customer that signed for the collection.
  • Print Name: The signatory entered by the driver when capturing the signature for the collection.

This format will be made available for selection under the Job Group as format "Hewicks POC". The Job Group should be configured with this format in the POC format field.


POC 2 Format

A prototype of this format has been created:

FS 325463 HEW HEW POC.PNG
Hewicks Haulage POC

As this format differs only slightly from the first POC format, this will be built into that format. The only changes are:

  • Title and Address: The title name and other information will be gathered from a customer record with a code equal to the Job Group it belongs to, created with the details against it, as follows:
    • Title: Customer Name
    • Address: From the first 4 lines of the customer address (comma delimited) and the postcode
    • Tel: Extracted from the telephone number.
    • Fax: The Fax title and value will only be displayed if the value in the telephone number has a vertical bar (|) separating a second number. In this case, the second number is printed here.
    • Web: From the Contact.
    • TASCC No: This line and value will only be printed if Address Line 5 has a value. This field is expected to contain both the label and the value (i.e. "TASCC No: XY161").


POD 1 Format

A prototype of this format has been created:

FS 325463 HEW CAVE POD.PNG
Cave Liquid Haulage POD

The individual fields will be populated as follows:

  • Ticket No: Job ID - the unique id of this delivery job.
  • Title and Address: The title name and other information will be gathered from a customer record created with the details against it, as follows:
    • Title: Customer Name
    • Address: From the first 4 lines of the customer address (comma delimited) and the postcode
    • Tel: Extracted from the telephone number. If a fax number is required, this may be entered in the same place, with a vertical bar (|) separating them.
    • Web: From the Contact.
  • Date: Actual Arrival Date
  • Driver: Name of the POD user that completed the job on the load.
  • Vehicle Reg: Registration of the vehicle used to complete the load.
  • Trailer No: Trailer ID entered when starting the load.
  • Delivery Name and Address: Alternate Job Address or, if this doesn't exist, the customer address (Address from the Customer selected against the job).
  • Time Arrived: Actual Arrival Time
  • Product: The Product Description from the first Product found on the Delivery job.
  • Weight: The Product Quantity from the first Product found on the Delivery job. Amendments will be carried over to the delivery from the collection and confirmed at delivery by the driver.
  • Time Departed: Actual End Time
  • Customer Signature: The Signature image from the customer that signed for the delivery. Note Note: It is advised that the customer signatory also be added here (i.e. Print Name).

This format will be made available for selection under the Job Group as format "Hewicks POD". The Job Group should be configured with this format in the POD format field.


POD 2 Format

A prototype of this format has been created:

FS 325463 HEW HEW POD.PNG
Hewicks Haulage POD

As this format differs only slightly from the first POC format, this will be built into that format. The only changes are:

  • Title and Address: The title name and other information will be gathered from a customer record with a code equal to the Job Group it belongs to, created with the details against it, as follows:
    • Title: Customer Name
    • Address: From the first 4 lines of the customer address (comma delimited) and the postcode
    • Tel: Extracted from the telephone number.
    • Fax: The Fax title and value will only be displayed if the value in the telephone number has a vertical bar (|) separating a second number. In this case, the second number is printed here.
    • Web: From the Contact.


POC/POC Format

A prototype of this format has been created:

FS 325463 HEW HEW PODPOC.PNG
Hewicks Haulage PODPOC

The individual fields will be populated as follows:

  • Ticket No: Job ID - the unique id of the delivery job that is part of this collection/delivery pair of jobs.
  • Title and Address: The title name and other information will be gathered from a customer record created with the details against it, as follows:
    • Title: Customer Name
    • Address: From the first 4 lines of the customer address (comma delimited) and the postcode
    • Tel: Extracted from the telephone number. If a fax number is required, this may be entered in the same place, with a vertical bar (|) separating them.
    • Web: From the Contact.
  • Date: Actual Arrival Date
  • Driver: Name of the POD user that completed the job on the load.
  • Vehicle Reg: Registration of the vehicle used to complete the load.
  • Trailer No: Trailer ID entered when starting the load.
  • Customer Name and Address: From the Collection job: Alternate Job Address or, if this doesn't exist, the customer address (Address from the Customer selected against the job).
  • Product: The Product Description from the first Product found on the Delivery job.
  • Delivered To: From the Delivery job: Alternate Job Address or, if this doesn't exist, the customer address (Address from the Customer selected against the job).
  • Customer Signature: The Signature image from the customer that signed for the delivery.
  • Print Name: The signatory entered by the driver when capturing the signature for the delivery.
  • Date: Actual End time from the Delivery job.

This format will be made available for selection under the Job Group as format "Hewicks POD/POC". The Job Group should be configured with this format in both POD and POC format fields.


Appendix A: 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 1.25 1.25 750 £937.50
Technical Specification 1.25 1.25 750 £937.50
Development 6.50 5.50 750 £4,125.00
Testing and Release 1.25 1.00 750 £750.00
Implementation 0.00 0.00 750 £0.00
Project Management 0.00 0.00 750 £0.00
 
TOTAL 10.25 9.00   £6,750.00
Estimate excludes training, release to live and go live support.

A.1 References

Ref NoDocument Title & IDVersionDate
1322793 - REQ-Hewicks Haulage3.012/03/2015
2325465 SCR-HEW-006 Last 3 Loads Retrieval  


A.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.


A.3 Authorised By


Matt Tipping
OBS Logistics Representative		_____________________________

Christopher Hewick
Hewicks Haulage Representative		_____________________________

Carl Brinkley
Hewicks Haulage Representative		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=FS_325463SCR_HEW-005_5_New_POD_Formats&oldid=1813’