REQ 354567 JB Global POD Note Changes: Difference between revisions

From Calidus HUB
VisualWikitext
(v1.0 - Initial version)
(v1.1 - Initial release to client)
Line 4: Line 4:
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|JB Global POD Note Changes}}
{{#vardefine:Doc_Title|JB Global POD Note Changes}}
{{#vardefine:Version|1.0}}
{{#vardefine:Version|1.1}}
{{#vardefine:Date|2nd January 2019}}
{{#vardefine:Date|18th February 2019}}
{{#vardefine:Reference|354567}}
{{#vardefine:Reference|354567}}
{{#vardefine:Year|2019}}
{{#vardefine:Year|2019}}
Line 23: Line 23:
= Introduction  =
= Introduction  =
<!-- The introduction will detail the initial requirements supplied by the client -->
<!-- The introduction will detail the initial requirements supplied by the client -->
This document is the {{#var:Doc_Title}}.
This document relates to {{#var:Doc_Title}}.




== Objective  ==
== Objective  ==
The primary purpose of this document is to document the requirements gathered from {{#var:ClientName}} regarding changes required to the POD note.
The primary purpose of this document is to describe the requirements gathered from {{#var:ClientName}} regarding changes required to the POD note.




Line 34: Line 34:


== Scope and Limitations ==
== Scope and Limitations ==
This document is based on the documentation provided by {{#var:ClientName}}, as well as information gleaned from site visits and workshops with {{#var:ClientName}}.
This document is based on the documentation provided by {{#var:ClientName}} and additional points clarified and confirmed by {{#var:ClientName}} in subsequent discussions and emails.


<!-- ANY scope or limitations, bulleted. -->
<!-- ANY scope or limitations, bulleted. -->
Line 46: Line 46:
I have attached the new POD to this email. Please generate an estimate for the changes required and let me know when you can make them. Just to note, any config changes will need to be applied to all ePod sites, as we'd need these changes to be applied system wide.
I have attached the new POD to this email. Please generate an estimate for the changes required and let me know when you can make them. Just to note, any config changes will need to be applied to all ePod sites, as we'd need these changes to be applied system wide.


Points confirmed:
== Additional points confirmed ==
* Print images on a following page as with the current delivery note.
* Print images on a following page as with the current delivery note.
* ePOD has no telephone number 3 so will be blank.
* ePOD has no telephone number 3 so this will be blank.
* Print the name and signature side by side to allow more vertical room for the signature.
* Print the name and signature side by side to allow more vertical room for the signature.
* If the delivery has more than 14 lines then the report will throw a page after the 14th line (the footer area will be blank). The next page will include the header again, the rest of the lines and the footer. The third page will then be the disclaimer.
* If the delivery has more than 14 lines then the report will throw a page after the 14th line (the footer area will be blank). The next page will include the header again, the rest of the lines and the footer. The third page will then be the disclaimer.
* Using multiple fonts for the T&Cs is not necessary if this requires the text to be hard-coded. It is more important that the T&Cs can be edited in future.
* Using multiple fonts for the T&Cs is not necessary if this requires the text to be hard-coded. It is more important that the T&Cs can be edited in future.
* To support the new POD design, corresponding changes will be required to the configuration of the User-defined Field (UDF) forms currently in use:
** The "Difficult Delivery" information dialogue will be on a new UDF form for "Arrivals Terms and Conditions for Deliveries".
*** This will include capture of the driver's Q&A and the customer's signature. The driver will answer the questions then hand the PDA to the customer to sign.
*** The difficult delivery disclaimer will appear as the terms & conditions below the signature box and the driver's Q&A below that (so the customer will sign against both the disclaimer and the driver's answers, which also both appear on the disclaimer page of the POD).
*** If there isn’t a problem with access then the driver can skip the form.
** The existing form for capturing the "Difficult Delivery" information is no longer required and will be removed. This is the "Job Details - When Amended" UDF form.
** The Returns disclaimer will be on a new UDF form for "Arrivals Terms and Conditions for Collections". This will include capture of the customer's signature with the disclaimer text below the signature box.
** The failure reason, return no. and card no. are entered on a "Job Cancellation" UDF form, which will remain in use.
* Collection jobs will show alternative text to delivery notes in these places:
** The document title will change from "DELIVERY NOTE" to "COLLECTION NOTE".
** The text against the customer signature will change from "I, the customer, acknowledge receipt of goods" to "I, the customer, acknowledge collection of goods".
** The text "FAILED DELIVERY CHECKLIST TO BE COMPLETED BY DRIVER" will become "FAILED COLLECTION CHECKLIST TO BE COMPLETED BY DRIVER"
[[File:JBG POD page 1.jpg|border|600px]]
[[File:JBG POD page 1.jpg|border|600px]]


Revision as of 16:30, 18 February 2019





Aptean Logo.png







JB Global

JB Global POD Note Changes

CALIDUS ePOD

18th February 2019 - 1.1
Reference: REQ 354567











































Introduction

This document relates to JB Global POD Note Changes.


Objective

The primary purpose of this document is to describe the requirements gathered from JB Global regarding changes required to the POD note.


This document has been written in a manner such that it can be approved by non-technical representatives of JB Global whilst also being of sufficient detail to allow the Functional or Technical Specification phase for this area to begin.


Scope and Limitations

This document is based on the documentation provided by JB Global and additional points clarified and confirmed by JB Global in subsequent discussions and emails.

  • The changes will be made in the latest version of the CALIDUS ePOD system, operating the Android version of the C-ePOD Client application.


Client Requirements

I have attached the new POD to this email. Please generate an estimate for the changes required and let me know when you can make them. Just to note, any config changes will need to be applied to all ePod sites, as we'd need these changes to be applied system wide.

Additional points confirmed

  • Print images on a following page as with the current delivery note.
  • ePOD has no telephone number 3 so this will be blank.
  • Print the name and signature side by side to allow more vertical room for the signature.
  • If the delivery has more than 14 lines then the report will throw a page after the 14th line (the footer area will be blank). The next page will include the header again, the rest of the lines and the footer. The third page will then be the disclaimer.
  • Using multiple fonts for the T&Cs is not necessary if this requires the text to be hard-coded. It is more important that the T&Cs can be edited in future.
  • To support the new POD design, corresponding changes will be required to the configuration of the User-defined Field (UDF) forms currently in use:
    • The "Difficult Delivery" information dialogue will be on a new UDF form for "Arrivals Terms and Conditions for Deliveries".
      • This will include capture of the driver's Q&A and the customer's signature. The driver will answer the questions then hand the PDA to the customer to sign.
      • The difficult delivery disclaimer will appear as the terms & conditions below the signature box and the driver's Q&A below that (so the customer will sign against both the disclaimer and the driver's answers, which also both appear on the disclaimer page of the POD).
      • If there isn’t a problem with access then the driver can skip the form.
    • The existing form for capturing the "Difficult Delivery" information is no longer required and will be removed. This is the "Job Details - When Amended" UDF form.
    • The Returns disclaimer will be on a new UDF form for "Arrivals Terms and Conditions for Collections". This will include capture of the customer's signature with the disclaimer text below the signature box.
    • The failure reason, return no. and card no. are entered on a "Job Cancellation" UDF form, which will remain in use.
  • Collection jobs will show alternative text to delivery notes in these places:
    • The document title will change from "DELIVERY NOTE" to "COLLECTION NOTE".
    • The text against the customer signature will change from "I, the customer, acknowledge receipt of goods" to "I, the customer, acknowledge collection of goods".
    • The text "FAILED DELIVERY CHECKLIST TO BE COMPLETED BY DRIVER" will become "FAILED COLLECTION CHECKLIST TO BE COMPLETED BY DRIVER"

JBG POD page 1.jpg

JBG POD page 2.jpg


Appendix A: Document References

A.1 References

Ref NoDocument Title & IDVersionDate
1   


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


Barry Preece
OBS Project Manager		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=REQ_354567_JB_Global_POD_Note_Changes&oldid=6995’