FS 344274 SCR-343463-04 EBB Paper POD POC Format
EBB Paper
EBB Paper POD/POC Format
CALIDUS ePOD
10th August 2017 - 1.0
Reference: FS 344274 SCR-343463-04
Contents
Functional Overview
Client Requirement
SCR-343463-04: EBB Paper POD/POC Format
Once jobs are completed, then will be confirmed with the C-ePOD server. After this confirmation, a POD/POC report may be produced.
All photos taken by the driver during the execution of the job (i.e. at cancellation of product, change quantity of product, job photos) will be displayed in the C-ePOD Admin system for the administrative users to view.
The format attached to the job group is the format that will be produced from the Admin console and displayed for customers when requested through CALIDUS Portal.
Solution Overview
The format of the POD note has been prototyped to show capability. The format has been provided and the prototype is shown below:
Prototype EBB Papers POD Format
Page Header, expected to be displayed on every page:
- EBB Logo - It is expected that this will be the logo taken from the site.
- "ELLIOTT BAXTER & ..." - fixed text.
- "Delivery Note" - fixed text, displaying "Collection Note" if the job is a collection.
- Mr EBB Logo - Fixed image in the format
- Invoice to - The address of the job's customer.
- "Delivery to" - fixed text, displaying "Collection from" if the job is a collection.
- Delivery to - the job address if present, otherwise the customer address.
- "Delivery Instructions" - any job instructions provided.
- DATE -
Warning: the planned start date - BRANCH - the owner of the job
- DEL DATE - Warning: the actual start date
- DELIVERY TIME - Warning: the planned start time
- S TIME - the arrival time
- E TIME - the actual end time
- DEL NOTE NO - the INV number (Job Code)
Product Details, expected to be shown on every page, expected to show up to 10 products per page:
- ORDER NO - the order number against the product
- QTY - The actual quantity of the product delivered, as confirmed by the driver.
- UNITS - the unit type against the product
- QUALITY & DESCRIPTION - The description of the product, and the FSC number (if provided) from the Long Description.
- PACKS - the pack size, from the case quantity.
- KGS - the weight of the product
Footer, expected to be shown on all pages:
- Please be sure to check every..." - T&Cs from the job.
- Total Wgt - the sum of the weights of the delivered products.
- "Signature" - the customer signature if present.
- Print Name - the customer signatory, if present.
- Date - the actual end date.
- "Signed on behalf of" - based on the Unmanned Location process. If the driver signature is present, it will be displayed here.
- Print Name - the driver's name.
- Date - the actual end date.
- "NUMBER 1 FOR SERVICE" - fixed logo.
- "Only products identified ..." - fixed text.
Scope
This change will be applied to system version 4.X.
The definition of the exact fields used for this report are to be confirmed as part of this functional specification. These are dependent on the interface mapping. Specifically the data affected is:
- The Dates and Times displayed
- The Branch
Set-up
Pre-requisites
Menu Structure
Data
Each Job Group will be configured with the POD/POC format.
Job Groups Maintenance
Functional Description
Format "EBB Paper"
The report will be produced through the Configurable POD Report format (ConfigPOD.aspx).
A data report (on EPOD_CONFIG_REPORT) will be created matching the prototype format created.
The format created will have the name "EBB Paper" (in ECR_NAME) and will added to the list of POD/POC formats that can be selected from the Site and Job Group screens (being added to EPOD_LIST_ITEMS for the drop-down lists on these screens).
Settings for the configurable report are stored on EPOD_CONFIG_REPORT and are as follows:
| Data Field | Value | Description |
|---|---|---|
| ECR_NAME | "EBB Paper" | The name of the report. |
| ECR_ROWS_FIRST_PAGE | 10 | The number of detail rows on the first page of a multi-page report, including the title line. |
| ECR_MAX_ROWS_SINGLE_PAGE | 10 | The number of detail rows on a single page report, including the title line. |
| ECR_ROWS_CONTENT_PAGE | 10 | The number of detail rows on a (non-first or last) page of a multi-page report. |
| ECR_ROWS_LAST_PAGE | 10 | The number of detail rows on the last page of a multi-page report |
| ECR_ALT_ROWS_IND | 0 | Whether odd and even detail rows are formatted differently (1) or not (0). |
| ECR_INC_CANCELLED_IND | 0 | Whether to include cancelled details lines (containers or products) on the report (1) or not (0). |
| ECR_INC_IMAGES_IND | 1 | Whether to include images on the viewed report (1) or not (0). |
| ECR_EMAIL_IMAGES_IND | 0 | Whether to include images on the PDF report generated for emails (1) or not (0). |
| ECR_INC_PRODUCTS_IND | 1 | Whether Products are included on the report (1) or not (0). |
| ECR_PDF_ORIENT | P | The orientation of the report: (P)ortrait or (L)andscape. |
| ECR_CONTENT_SORT | NULL | The fields on which to sort detail (product or container) records, delimited by commas. |
| ECR_CONTENT_GROUP | NULL | The fields on which to group detail (product or container) records, delimited by commas. |
The format is populated as follows:
The Page Header will be defined in ECR_PAGE_HEADER and will be displayed on every page. The data will be populated as follows:
| Report Item | Data Fields | Description |
|---|---|---|
| Company Logo | EPOD_JOB_GROUPS.EPL_LOGO | The logo taken from the job group, if a logo exists, otherwise taken from the site. |
| "ELLIOTT BAXTER & COMPANY LIMITED" Delivery Note |
EPOD_JOB.EPL_JOB_TYPE | Fixed text, displaying Delivery or Collection depending on the Job Type. |
| Mr EBB Image | Base64-encoded image embedded in the header. | |
| Invoice To | EPOD_CUSTOMER | Taken from the customer address. Including Name, Address Lines and Postcode. |
| "Deliver To" | EPOD_JOB.EPL_JOB_TYPE | Fixed text, displaying Deliver or Collect depending on the Job Type. |
| Deliver To | EPOD_JOB_ADDRESS | Taken from the job address. Including Name, Address Lines and Postcode. |
| "Delivery Instructions" | EPOD_JOB.EPL_JOB_TYPE | Fixed text, displaying Delivery or Collection depending on the Job Type. |
| Delivery Instructions | EPOD_JOB.EPL_JOB_INSTRUCTION | The job instructions. |
| DATE | EPOD_JOB.EPL_START_PLANNED_DATE | The planned start date, in dd/mm/yyyy format. |
| BRANCH | EPOD_JOB.EPL_OWNER_NAME | The sales territory. |
| DEL DATE | EPOD_JOB.EPL_START_PLANNED_DATE | The planned start date, in dd/mm/yyyy format. |
| DELIVERY TIME | EPOD_JOB.EPL_START_PLANNED_TIME | The planned start time, in hh:mm format. |
| S TIME | EPOD_JOB.EPL_START_ACTUAL_TIME | The actual start time, in hh:mm format. |
| E TIME | EPOD_JOB.EPL_END_ACTUAL_TIME | The actual end time, in hh:mm format. |
| DEL NOTE NO | EPOD_JOB.EPL_JOB_CODE | The SO number. |
Product details will be shown on every page, showing up to 10 products per page, as defined by the report settings above.
The reported elements will be taken from EPOD_PRODUCT. Cancelled products (i.e. those with a status of "X" and a quantity of 0) will not be shown in this section.
The detail table header will be defined in ECR_CONTENT_TITLE as shown below.
Each page will fill the detail table to the maximum amount per page, defined by entering an empty row definition in ECR_CONTENT_EMPTY.
Each row will be defined in ECR_CONTENT_ROW as follows:
| Report Item | Data Fields | Description |
|---|---|---|
| ORDER NO | EPOD_PRODUCT.EPL_CUST_REF | The customer's order number. |
| QTY | EPOD_PRODUCT.EPL_PRODUCT_QTY_ACTUAL | The actual quantity of the product delivered, as confirmed by the driver. |
| UNITS | EPL_UNIT_TYPE | The UOFM, as stored from the interface |
| QUALITY & DESCRIPTION | EPOD_PRODUCT.EPL_DESCRIPTION_LONG | The full description and FSC text, as held in the Long Description field in C-ePOD. These will be displayed on two lines, substituting the CR/LF characters with an HTML Line Break tag. |
| PACKS | EPL_PRODUCT_QTY_ACTUAL / EPL_PRODUCT_QTY_CASE |
The number of packs. This is a calculated value (denoted by "CALC:") of the delivered quantity divided by the pack size, displayed with no decimal places. |
| KGS | EPOD_PRODUCT.EPL_PRODUCT_WEIGHT | The total weight of the delivered product. The weight will be sub-totalled. |
The Page Footer will be defined in ECR_PAGE_FOOTER and will be displayed on every page. The data will be populated as follows:
| Report Item | Data Fields | Description |
|---|---|---|
| "Please be sure to check..." | EPOD_JOB.EPL_TNCS | T&Cs as signed for by the customer at the point of signing for the job. These are configured against the Job Group and are expected to be "Please be sure to check every consignment before signing. All sales are subject to Conditions of Sale, a copy of which
is at the back of the EBB Price List and on our website http://www.ebbpaper.co.uk". Note that each job group may have different configured T&Cs. |
| Total Wgt | TOT0 | The KGS subtotal, formatted with no decimal places. |
| Signature | EPOD_JOB.EPL_JOB_SIGNATURE | The customer's signature. If not present, this should be a blank image rather than the standard "Image Not Available" text. |
| Print Name | EPOD_JOB.EPL_CUST_SIGNATORY | The signatory, captured by the driver on the device when the customer signs. |
| Date | EPOD_JOB.EPL_END_ACTUAL_DATE | The actual end date, when the signature was obtained, in dd/mm/yyyy format. |
| Signed on behalf of: | EPOD_JOB.EPL_JOB_SIGNATURE | The driver's signature, for unmanned locations. If not present, this should be a blank image rather than the standard "Image Not Available" text. |
| Print Name | EPOD_USER.EPL_USER_NAME | The driver's name, for unmanned locations |
| Date | EPOD_JOB.EPL_END_ACTUAL_DATE | The actual end date, when the signature was obtained, in dd/mm/yyyy format. |
| No 1 for Service Image | Base64-encoded image embedded in the footer. | |
| "Only products identified ..." | Fixed text. |
Appendix A: TEST PLAN
| Test Script / Scenario Reference | EBB Paper POD/POC Format | Call Number(s): 344274 SCR-343463-04 |
| Test Script / Scenario Description | Testing the new POD report format | PASS / ISSUES / FAIL |
| Menu Access | N/A | |
| Pre-requisites | A system configured as EBB Paper. | Tested By: |
| Test Objective | To test that the report format works as expected. | Date: |
| Step | Action | Result | Remarks | P/F |
| 1 | Admin | |||
| 1.01 | Check the Job Groups and Site screens that the new EBB Paper report format can be set. | The new EBB Paper report format can be set. |
| Step | Action | Result | Remarks | P/F |
| 2 | POD/POC Report | |||
| Ensure there is a completed job with Products, configured to the "EBB Paper" POD/POC format. | ||||
| 2.01 | Run the report on the completed job. | The report layout is as expected. |
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.75 | 0.75 | 750 | £562.50 |
| Technical Specification | 0.00 | 0.00 | 750 | £0.00 |
| Development | 2.50 | 2.50 | 750 | £1,875.00 |
| Testing and Release | 0.25 | 0.25 | 750 | £187.50 |
| Implementation | 0.25 | 0.25 | 750 | £187.50 |
| Project Management | 0.25 | 0.25 | 750 | £187.50 |
| TOTAL | 4.00 | 4.00 | £3,000.00 | |
| Estimate excludes training, release to live and go live support. |
B.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | REQ 343463 EBB Paper Solution Design | 2.0 | 01/08/2017 |
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
Matt Turner | OBSL Account Manager | _____________________________ |
Rebecca Elliott | Customer Representative | _____________________________ |
