FS 336012 SCR-332569-3 GK PvA Add Time Windows
Greene King
Add Time Windows
CALIDUS EPOD
23rd August 2016 - 1.0
Reference: FS 336012/SCR-332569-3
Contents
Functional Overview
Client Requirement
In order to support the functionality required within the Planned Vs Actual report regarding time windows, the application will be modified to store the time windows information from the DiPS interface.
Solution Overview
These will be added as new table, at Job level, to account for potential multiple time windows. The data is assumed to be taken from OPENING/CLOSING TIME 2 at this time. There is no way of identifying or specifying multiple delivery windows or customer delivery windows in the way that Aurora and DiPS plan jobs at this time. A customer is expected to always have a delivery window configured against it, and that it may change (by configuration) for each day of the week if required.
Scope
Although this change will be made capable of storing multiple time windows against a job or against a customer, the interface here will only create job windows, and only one of them per job. Should Aurora and DiPS (or the interface between them) be modified to support multiple windows, or there is a product requirement to add multiple customer windows, this will generate additional cost. It is not expected that this will be required at this time.
The changes here are to support multiple time windows from the bespoke DiPS interface, and for use within the Planned Vs Actual report only - there is no mechanism of viewing or editing these through the ePOD Admin application. If this is required, this will generate additional cost. If the full CALIDUS ePOD solution is agreed, this time will be added part of the full solution defined in that project.
Note: Testing of this change will be part of the 336010/SCR-332569-2 DiPS-ePOD Interface for Load and Order Sequencing.
Set-up
Pre-requisites
This change is part of the 336010/SCR-332569-2 DiPS-ePOD Interface for Load and Order Sequencing. Set up for that change must be completed so that this may be tested.
Menu Structure
None
Data
None
Functional Description
Database/DAL
These will be added as new table, at Job level, to account for potential multiple time windows. The data is assumed to be taken from OPENING/CLOSING TIME 1/2 at this time. There is no way of identifying or specifying multiple delivery windows or customer delivery windows in the way that Aurora and DiPS plan jobs at this time. A customer is expected to always have a delivery window configured against it, and that it may change (by configuration) for each day of the week if required.
The new table will be called EPOD_TIME_WINDOW and will be structured as follows:
- ETW_ID - an auto-generated number.
- ETW_SITE_ID - nvarchar(10)
- ETW_TYPE - nvarchar(1)
- ETW_FK_ID - nvarchar(30)
- ETW_TIME_START - number
- ETW_TIME_END - number
There will be primary key added as follows:
- ETW_ID - an auto-generated number.
An index will be added called ETW_TYPE as follows:
- ETW_SITE_ID - nvarchar(10)
- ETW_TYPE - nvarchar(1)
- ETW_FK_ID - nvarchar(30)
A new DAL object will be created to access this data. Database procedures will be created
The table must support being linked to a job or to a customer. This is through the new index.
- For jobs, this is expected to be populated with the job's Site ID, the Type as "J" and the Foreign Key ID as the Job ID (EPL_JOB_ID of EPOD_JOB).
- For customers, this is expected to be populated with the customer's Site ID, the Type as "C" and the Foreign Key ID as the customer ID (EPL_CUSTOMER_CODE of EPOD_CUSTOMER).
The Archiving routines must be updated to delete these new records when deleting Customers or when deleting Jobs.
Appendix A: TEST PLAN
Note: Testing of this change will be part of the 336010/SCR-332569-2 DiPS-ePOD Interface for Load and Order Sequencing.
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.50 | 0.50 | 750 | £375.00 |
| Technical Specification | 0.50 | 0.50 | 750 | £375.00 |
| Development | 2.75 | 2.75 | 750 | £2,062.50 |
| Testing and Release | 0.50 | 0.50 | 750 | £375.00 |
| Implementation | 0.00 | 0.00 | 750 | £0.00 |
| Project Management | 0.25 | 0.25 | 750 | £187.50 |
| TOTAL | 4.50 | 4.50 | £3,375.00 | |
| Estimate excludes training, release to live and go live support. |
B.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | 336010/SCR-332569-2 DiPS-ePOD Interface for Load and Order Sequencing | 1.0 | 23/08/2016 |
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
Rob Carter | Greene King Representative | _____________________________ |
Matt Tipping | OBSL Representative | _____________________________ |
