FS 314697 POD POC Formats

From Calidus HUB





Aptean Logo.png







Brett Martin

Brett Martin POD Formats

CALIDUS ePOD

14th January 2014 - 0.1
Reference: FS 314697 313776/2











































Functional Overview

Client Requirement

OBSL have agreed to develop the collection and delivery notes for Brett Martin. The two portions of the business (Brett Martin and Ariel) will use the same formats, differing only in Logo, Address and T&Cs.


Solution Overview

Note Note: The Collection process has not been discussed in detail. Documentation of this process must be provided to OBS Logistics. At this time, it is assumed that the collection process will be identifying products and quantities rather than DUs. However, it should be noted that the CALIDUS ePOD collection process is configured primarily based on the data received, so if the process requires collection of DUs, as long as the collection job received details the DUs and quantities to collect, the device process will work.


There are currently two POC and POD formats, one for Ariel, one for Martin. It has been agreed that the formats can be identical, with the exception of the Logo. This will be set against the produced POC/POD from the logo of the Job Group passed against the Job.


The mapped values will be: Page Header:

  • Ariel Plastics address and Logo - Will be set from the Job Group passed in.

Header:

  • Delivery Note - Job Code
  • Delivery Address - Customer or Job Address.
  • Customer Acc - Customer Code
  • Cust Order - Cust Ref
  • Customer Tele - Telephone #
  • Ship Date - Load Start Planned Date
  • Sales Order - SO Number
  • Requisition - External Ref.
  • Drop Number - Sequence.
  • Confirmed Ship Dt - Load Start Actual Date
  • Driver ID - User ID
  • Schedule ID - Load ID

Details - This information will come from the Products sent to CALIDUS ePOD.

  • For Deliveries:
    • Description - DU
    • Unit - Blank
    • Delivered - Actual DU Qty, as confirmed by the driver when delivering.

Footer:

  • Delivery Contact - Customer Contact
  • Delivery Contact Phone - This would be the same as Customer Telephone above.
  • "Received in Good order" - T&Cs or Fixed text.
  • Sign - Customer Signature
  • Print - Cust Signatory
  • Date - Actual End Date
  • Driver - Driver Name or Driver Signatory. Warning Warning: TBC
  • "All Shortages..." - T&Cs or fixed text.


The format will be changed slightly if the job is a collection:

  • The text 'Delivery' will be changed to 'Collection'.
  • The text 'Delivered' will be changed to 'Collected'.
  • For Collections:
    • Description - Product Code and Product Description
    • Unit - UOM passed in. Will be "Ea"
    • Delivered - Product Actual Qty, as confirmed by the driver when collecting.


It should be noted that the collection and delivery notes are largely to be produced through Microsoft AX based on the completion data passed back to there from CALIDUS ePOD, as the information received by the device is not sufficient at this time to produce an accurate note.


Scope

  • These changes will be made in the latest version of the CALIDUS ePOD product only.


Set-up

Pre-requisites

Menu Structure

Data

A Job Group record should be created for each side of the business. The settings should include:

  • Appropriate Terms and Conditions
  • Customer/Driver Signature requirements
  • The appropriate POD and POC format
  • A Logo for the POD/POC

The two Job Groups created should be 'MARTIN' and 'ARIEL'. Note Note: For customer implementation, the actual values of the Job Groups will be defined by the job group of the jobs received on the interface from AX. This will be agreed in advance, but will be whatever is easiest for the customer to produce.


A Customer should also be set up with a customer code set to the Job Group. This should be set up with the address information for the POD/POC header. For example, the information for Ariel is:

  • 'ARIEL' - EPL_CUSTOMER_CODE
  • 'Ariel Plastics Ltd' - EPL_CUSTOMER_NAME
  • 'Speedwell Ind. Est' - EPL_ADDRESS_1
  • 'Stavely' - EPL_ADDRESS_2
  • 'Derbyshire' - EPL_ADDRESS_3
  • '01246 281111|01246 561111' - EPL_TELEPHONE
  • '[email protected]' - EPL_EMAIL
  • 'GB 760 8975 85' - EPL_ADDRESS_4


Functional Description

Admin

The Job Group and Site screens (job_group.aspx and site_header.aspx respectively) will be modified to allow the system to be configured for the new Brett Martin report, by adding this as an option to the DDLs in the editing pop-up forms, for both POD and POC format. Additionally, the grid will be modified to display this correctly if selected. The name on the list will be 'Brett Martin', pointing to the new report below, martin.aspx.


Admin - POD/POC Formats

Note Note: These formats have been prototyped and are available on request for the developer to base the final formats.

The formats created here should follow the standardised pagination code used in other formats.

The format will be created as martin.aspx, following this template:

FS 314697 POD.PNG


  • 'Ariel Plastics Ltd ... VAT Reg. No. GB 760 8975 85' - from EPOD_CUSTOMER from EPL_JOB_GROUP. If If there is no customer record for this Job Group, this shall be blank.
    • 'Ariel Plastics Ltd' - EPL_CUSTOMER_NAME
    • 'Speedwell Ind. Est' - EPL_ADDRESS_1
    • 'Stavely' - EPL_ADDRESS_2
    • 'Derbyshire' - EPL_ADDRESS_3
    • 'Tel' - EPL_TELEPHONE (1st segment, before '|'). If only one number is present, this is used here. If none are present, remove this and the label 'Tel'.
    • 'Fax' - EPL_TELEPHONE (2nd segment, after '|'). If less than 2 numbers are present, remove this and the label 'Fax'.
    • 'Email' - EPL_EMAIL. If the email is not present, remove the label as well.
    • 'VAT Reg. No.' - EPL_ADDRESS_4
  • Logo - EPL_LOGO of EPOD_JOB_GROUP from EPL_JOB_GROUP. If there is no logo, this section shall be left blank.
  • Delivery Note - EPL_JOB_CODE. The label will show 'COLLECTION NOTE' if this is a collection-type job.
  • Delivery Address - From EPOD_JOB_ADDRESS if present, else EPOD_CUSTOMER:
    • EPL_CUSTOMER_NAME (If customer address)
    • EPL_ADDRESS_1
    • EPL_ADDRESS_2
    • EPL_ADDRESS_3
    • EPL_ADDRESS_4
    • EPL_ADDRESS_5
    • EPL_POSTCODE - this should be preceded by two line-breaks.
    • Customer Acc - EPL_CUSTOMER_CODE
    • Cust Order - EPL_CUST_REF
    • Customer Tele - EPL_TELEPHONE - this should be split at any vertical bar characters, replacing with a forward slash (/) character.
  • Ship Date - EPL_LOAD_START_PLANNED_DATE of EPOD_LOAD
  • Sales Order - EPL_SO_NUMBER
  • Requisition - EPL_EXT_REF
  • Drop Number - EPL_SEQUENCE
  • Confirmed Ship Dt - EPL_LOAD_START_ACTUAL_DATE of EPOD_LOAD
  • Driver ID - EPL_USER_ID
  • Schedule ID - EPL_LOAD_ID
  • Details - This information will come from the Products sent to CALIDUS ePOD. Regardless of whether this is a collection or delivery, the information is taken from the EPOD_PRODUCTS table. There will be a maximum of 12 detail lines in this format, not including the title.
    • Description - EPL_PRODUCT_CODE, plus line break, plus EPL_DESCRIPTION
    • Unit - EPL_UNIT_TYPE
    • Delivered - EPL_PRODUCT_QTY_ACTUAL. The label will show 'Collected' if this is a collection-type job.
  • Delivery Contact - EPL_CONTACT, from EPOD_JOB_ADDRESS if present, else EPOD_CUSTOMER. The label will show 'Collection Contact' if this is a collection-type job.
  • Delivery Contact Phone - This would be the same as 'Customer Tele' above. The label will show 'Collection Contact Phone' if this is a collection-type job.
  • "Received in Good order" - from EPL_TNCS - see note below.
  • Sign - EPL_CUST_SIGNATORY, then a line break, then EPL_JOB_SIGNATURE, converted to image.
  • Driver Sign - EPL_ENG_SIGNATURE, converted to image. If this is not present or required for the Job Group, this whole block should be blank (i.e. the TD should be an unformatted empty cell).
  • Date - EPL_END_ACTUAL_DATE
  • Driver - EPL_USER_NAME of EPOD_USERS, linked to using EPL_USER_ID.
  • "All Shortages..." - Fixed text, except the telephone number, which will be taken from the first number in EPL_TELEPHONE. If this is not found or blank, the first sentence should be displayed as "All shortages and damages must be reported within 48 hours to customer services".

Note Note: All fields come from EPOD_JOB unless stated otherwise.

Note Note: The Terms and Conditions will be converted from the TEXT tag contained within this field, preserving formatting. Each INPUT tag specified will create an Input element in line below this, one line per input. Examples of this code can be found in the CDL format (CDL.aspx).


Appendix A: TEST PLAN

Test Script / Scenario ReferenceBrett Martin POD FormatsCall Number(s): 314697 313776/2
Test Script / Scenario DescriptionTo show that the POD reports created can be usedPASS / ISSUES / FAIL
Menu AccessTasks/Jobs 
Pre-requisitesTwo Job Groups must be set up:
  • Ariel
    • T&Cs
    • Both Signatures
    • Address with 2 telephone numbers.
  • Brett Martin
    • No T&Cs
    • Customer Signature only
    • Address with 1 telephone number.

Collection and Delivery Jobs should be set up and completed as follows:

  • Job 1 - Delivery for ARIEL - Customer only with 1 Telephone Number
  • Job 2 - Collection for ARIEL - Job Address with 2 Telephone Numbers
  • Job 3 - Delivery for MARTIN - Customer only with no Telephone Numbers
  • Job 4 - Collection for MARTIN - Customer and Job Address with 1 Telephone Number
Tested By:
 
Test ObjectiveTo test that: The POD and POC formats can be configured correctly and; the formats produce correctly under all circumstances.Date:
 


Step Action Result Remarks P/F
1 Admin - Configuration      
       
1.01 In the Site maintenance screen, edit the site and set the POD and POC to 'Brett Martin'. Save. The values are available in the drop-down lists for both POC and POD. The values are saved and displayed in the grid.    
1.02 In the Job Group maintenance screen, edit a Job Group and set the POD and POC to 'Brett Martin'. Save. The values are available in the drop-down lists for both POC and POD. The values are saved and displayed in the grid.    
1.03 Add a new Job Group and set the POD and POC to 'Brett Martin'. Save. The values are available in the drop-down lists for both POC and POD. The values are saved and displayed in the grid.    


Step Action Result Remarks P/F
2 Admin - POD Formats      
       
2.01 In Job Details, find Job 1 and click the Report button. The report should display in the ARIEL format, showing as a Delivery in all labels. ARIEL T&Cs should be present. Final T&Cs should show the ARIEL contact number. Next to the ARIEL logo, the system should show the ARIEL address, displaying both phone and fax numbers. The Customer Address should be shown in the delivery address. A single Telephone number should be shown. The Details section section should display all non-cancelled DUs delivered. Both signatures should be displayed.    
2.02 In Job Details, find Job 2 and click the Report button. The report should display in the ARIEL format, showing as a Collection in all labels. ARIEL T&Cs should be present. Final T&Cs should show the ARIEL contact number. Next to the ARIEL logo, the system should show the ARIEL address, displaying both phone and fax numbers. The Job Address should be shown in the delivery address. All Telephone numbers should be shown, delimited by a slash. The Details section section should display all non-cancelled products collected. Both signatures should be displayed.    
2.03 In Job Details, find Job 3 and click the Report button. The report should display in the MARTIN format, showing as a Delivery in all labels. No T&Cs should be present. Final T&Cs should show the MARTIN contact number. Next to the MARTIN logo, the system should show the MARTIN address, displaying only the phone number. The Customer Address should be shown in the delivery and invoice addresses. No telephone numbers should be shown. The Details section section should display all non-cancelled DUs delivered. Only the customer signature should be displayed.    
2.04 In Job Details, find Job 4 and click the Report button. The report should display in the MARTIN format, showing as a Collection in all labels. No T&Cs should be present. Final T&Cs should show the MARTIN contact number. Next to the MARTIN logo, the system should show the MARTIN address, displaying only the phone number. The Job Address should be shown in the Delivery Address. 1 telephone number should be shown in both. The Details section section should display all non-cancelled products collected. Both signatures should be displayed.    



Appendix B: Quote & Document References

Cost Details
Activity No. of Days Rate per Day (£) Cost (£ Exc. VAT)
Requirements 0.00 0 £0.00
Change Request Evaluation 0.00 0 £0.00
Functional Specification 0.50 0 £0.00
Technical Specification 0.00 0 £0.00
Development 4.50 0 £0.00
Testing and Release 1.00 0 £0.00
Implementation 0.00 0 £0.00
Project Management First argument to "number_format" must be a number. 0 £First argument to "number_format" must be a number.
 
TOTAL First argument to "number_format" must be a number.   £First argument to "number_format" must be a number.
Estimate excludes training, release to live and go live support.

B.1 References

Ref NoDocument Title & IDVersionDate
1UG 291094 EPOD Admin User Guide2.04/4/2012
2UG 291097 EPOD Client User Guide3.023/4/2013
3REQ 313776 Brett Martin ePOD Requirements0.212/12/2013


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


Julie Scott
OBS Project Manager		_____________________________

Jack Bradin
Client Representative		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=FS_314697_POD_POC_Formats&oldid=1355’