Functional Overview
Client Requirement
Development is required to the CALIDUS ePOD system in order to provide the functionality required by CDL. The requirements have been set out by Matthew Turner from visits to the client as follows:
Computer Disposals collect used computer equipment from companies to recycle at their head office in Warrington.
They are currently implementing a back office solution to handle all job processing. The system will export basic job detail. We need to provide xml/csv schema detail so they can design an import function to pass job detail onto us. They will provide a example of their standard output in November, so we can tell them how to change it.
They have a 2 part delivery note that is largely based on a fixed template created in Word.
Coll Note Part 1 is attached.
Coll Note Part 2 is attached.
I have marked the detail that comes from the CDL back job office import on the 2 part form with a tick.
I have marked the detail that the driver needs to complete with an X.
In the current process, the driver does not generally know the exact quantity of goods he is collecting from a site. A general idea of the number of items to be collected is usually entered in the driver instructions part of the collection note. We refer to driver instructions in ePOD as ‘job instructions’.
On Product QTY Count, you will see that the driver does a manual count of equipment collected. He then does an estimation of weight based on multiplication of set weight per item. The result is entered on the QTY KG boxes on both parts on the collection note.
Example:
(qty count of product) x ( set weight per product ) = QTY (KG)
On Coll Note Part 1 the following rules apply:
In box CRT Monitor QTY (KG), the KG total number is based on:
(qty count of monitors) x ( set weight per monitor ) = QTY (KG)
In box Flat Screen Displays QTY KG, the KG total number is based on:
(qty count of TFT’s) x ( set weight per TFT) + (qty count of laptops) x ( set weight per laptops) = QTY (KG)
In box Waste Refrigerants QTY KG, the KG total number is based on:
(qty count of waste refrigerants) x ( set weight per waste refrigerants ) = QTY (KG)
On Coll Note Part 2 which is the 2nd part of the collection note, the following rules apply:
In box IT Equipment, the KG total number is based on:
Total QTY KG of all collected products except Monitors, TFT’s, Laptops, Waste Refrigerants
Set Weights Info
- 1 x Monitor = 12 Kg
- 1 x TFT = 8 Kg
- 1 x Base = 8 Kg
- 1 x General = 2 Kg
- 1 x Printer = 5 Kg
- 1 x Server = 12 Kg
- 1 x Laptop = 8 Kg
- 1 x Refrigeration Unit = 50 Kg
Anticipated Process On PDA:
- Driver opens collection job from manifest
- Driver accesses product confirmation
- Driver does QTY count of product
- Result of calculation for QTY KG does not necessarily have to be shown on PDA just electronic collection note back in system.
- Driver signs PDA.
- Customer (Consignor) signs PDA
General Info:
Consignor is ‘Customer‘.
Part E (Disposer of Waste) on both parts of the collection note needs to be replicated on the electronic collection note, but is not interacted with in any way by our system.
Automatic email POD is required on this contract.
General Questions:
Can date and time be automatically provided by the system on the electronic collection note?
Can driver print name and vehicle registration automatically be provided by the system on the electronic collection note?
Solution Overview
The functionality required is:
- Bespoke Job Import function
- Bespoke Multi-part Proof of Collection
- Multiple Signatures at Delivery/Collection
- Ad Hoc Collection process
- Product Weights
- Automatic email of POD/POC
- Office Instructions
- Modifiable customer contact.
Scope
Modifications will be made to version 1.1 of CALIDUS ePOD system.
Set-up
Pre-requisites
None
None
Data
The standard products must be created with standard weights.
Functional Description
Database Modifications
The EPOD_JOB table will be modified to include a new Office Instructions field. This will be in the same format as the current Instructions field.
The EPOD_JOB table will be modified to include a new Customer Name field. This will be in the same format as the current EPOD_CUSTOMERS Contact field .
The EPOD_PRODUCTS table will be modified to include a new Weight field. This will be a floating point field.
The EPOD_SERVICE_PRODUCT_MASTER table will be modified to include a new Weight field. This will be a floating point field.
Office Instructions
Bespoke Job Import function
Ad Hoc Collection process
Multiple Signatures at Delivery/Collection
Modifiable customer contact
Product Weights
The Service Product Maintenance screen (product_maintanance.aspx) will be modified to add a Weight column to the grid when data is found.
This will come from the new field on EPOD_SERVICE_PRODUCTS_MASTER.
When adding a new product from this screen (pressing the New button), the screen will prompt for the Weight. This will be positioned under the Product Status field, in line with it.
Clicking Create will save the new product with the weight. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.
When editing a product on the grid (by clicking Select, the Edit), the screen will allow the user to edit the weight in position here, like the Status and Quantity.
Clicking Update will save the product with any amendments. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.
Bespoke Multi-part Proof of Collection
As Appendix A
Note: CSS to remove Email block when printing.
Automatic email of POD/POC
on completion of job to complete status from PDA:
- Get customer email info.
- If found,
- Render correct format of POD/POC page
- remove email block
- Send email through standard mechanism
Appendix A: POC Document Formats
Appendix B: Quote & Document References
 Warning: | Unknown costs for client/year (CDL/2011) |
| 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.00 |
0 |
£0.00 |
| Technical Specification |
0.00 |
0 |
£0.00 |
| Development |
0.00 |
0 |
£0.00 |
| Testing and Release |
0.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 No | Document Title & ID | Version | Date |
| 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
Steve McCartney |
OBS Representative | _____________________________ |
Matthew Turner |
OBS Representative | _____________________________ |
