FS 340071 PROD-69 C-ePOD Navigate by GPS Coordinates
OBS Logistics
C-ePOD Navigate by GPS Coordinates
CALIDUS EPOD
14th December 2016 - 0.1
Reference: FS 340071 PROD-69
Contents
Functional Overview
Client Requirement
Navigate by Lat/Long provided by external system or gathered from server-side geo-coder, in preference to using Address/Postcode on device.
Solution Overview
The application will accept entry of lat/longs against customer and job addresses entered through the OBS XML Import format (webservice or flat file), and maintained through the Admin system.
The Admin screens allow entry of Lat/Long and will be modified to show this point on a map through a button click.
The address sent on a job to the device will be modified so that it contains the provided lat/longs, or null if not present.
The mobile application device will use the stored Lat/Longs against the address for navigation in preference to current method (for direct navigation only, not WEBFLEET).
Scope
Set-up
Pre-requisites
N/A
Menu Structure
N/A
Data
EPOD_CUSTOMER already has the Lat/Long stored against it.
EPOD_JOB_ADDRESS already has the Lat/Long stored against it.
Functional Description
Webservices
Webservices receive Lat/Long against customers and job addresses.
The XML interface already supports this, as follows:
- Customers interfaced separately through the EPOD_CUSTOMER top-level tag. In this case, lat/longs will be updated on the customer record.
- Customers interfaced through the EPOD_CUSTOMER EPOD_JOB-level tag. In this case, lat/longs will be updated on the customer record.
- Job Addresses interfaced through the EPOD_JOB_ADDRESS EPOD_JOB-level tag, and through the standard address. In this case, if the address is identical in all aspects to the original customer address (Name, Address Lines, Postcode, contact information), the customer address and lat/longs will be used. If not identical, a job address will be created with the provided lat/longs.
Within the webservice Calidus_ePOD.asmx currently, on LOAD_REQUEST and AUTO_UPDATE_REQUEST, the webservice responds with the whole load and jobs, and on JOB_LOCK_REQUEST and JOB_ARRIVAL_REQUEST, responds with the whole job. This does not include the Lat/Long of the address. This must be modified.
- The Lat/Long of the address selected to be sent to the device must be included.
- This is NOT required on additional job addresses, just the main address.
Note: The interface currently sends through the following fields. These are not required on the device and must be removed.
- EPL_APPROVED_IND
- EPL_APPROVED_EMAIL_IND
- EPL_ETA_DATE
- EPL_ETA_TIME
- EPL_TRAVEL_PLANNED
- EPL_WORK_PLANNED
- EPL_WORK_ACTUAL
- EPL_ODO_START
- EPL_ODO_END
Admin
The Customers screen (customer_maint.aspx) will be modified to add a View button next to the Lat/Long when viewing or creating a new customer. This should only be available if the customer has a lat/long.
This should call the standard Google Map code from the User Audit screen (user_tracking.aspx).
The Job Details screen (customer_maint.aspx) will be modified to add a View button next to the Lat/Long when viewing or creating a new job. This should only be available if the address has a lat/long.
This should call the standard Google Map code from the User Audit screen (user_tracking.aspx).
Developer Note: The Mapping function is controlled entirely though JQuery and a Google Maps javascript library. The function OpenMap opens a window, and the load function loads the map.
Mobile Device Application
The database table EPOD_JOB will be modified to add the fields EPL_LAT and EPL_LONG. These will be added as numeric fields, supporting decimal points, allowing NULLs.
The DAL object PDA_JOB will be modified to add these fields to all methods and functions. If the fields are not present, this should save NULL.
The Map navigate button (in JobDetail.js) will be modified to use the provided Lat/Long values, if both are non-null values, only in the case where this is not a WEBFLEET configuration.
Appendix A: TEST PLAN
| Test Script / Scenario Reference | C-ePOD Navigate by GPS Coordinates | Call Number(s): 340071 PROD-69 |
| Test Script / Scenario Description | Navigation using provided Lat/Long coordinates on the mobile device. | PASS / ISSUES / FAIL |
| Menu Access | N/A | |
| Pre-requisites | N/A | Tested By: |
| Test Objective | To test that: Admin can view lat/longs in a map and; the mobile device application uses these in preference to the address if provided. | Date: |
| Step | Action | Result | Remarks | P/F |
| 1 | Admin | |||
| 1.01 | Find a customer with Lat/Longs | The View button is present. The location is shown on a popup map if View is clicked. | ||
| 1.02 | Find a customer without Lat/Longs | The View button is not present or disabled. | ||
| 1.03 | Find a job with a customer address with Lat/Longs | The View button is present. The location is shown on a popup map if View is clicked. | ||
| 1.04 | Find a job with a customer address without Lat/Longs | The View button is not present or disabled. | ||
| 1.05 | Find a job with a job address with Lat/Longs | The View button is present. The location is shown on a popup map if View is clicked. | ||
| 1.06 | Find a job with a job address without Lat/Longs | The View button is not present or disabled. |
| Step | Action | Result | Remarks | P/F |
| 2 | Mobile Device Application | |||
| Ensure that there are jobs on a load with and without job addresses, with and without lat/longs. Ensure the lat/longs point to a different location than the text address, for easy confirmation. | ||||
| 2.01 | Select a job with a job address with lat/longs. Click the Map button on Job Details (starting the job first if necessary). | The navigation application shows the navigation point as the LatLong, not the address. | ||
| 2.02 | Select a job without a job address, but with a customer address with lat/longs. Click the Map button on Job Details (starting the job first if necessary). | The navigation application shows the navigation point as the LatLong, not the address. | ||
| 0.00 | Select a job with a job address without lat/longs. Click the Map button on Job Details (starting the job first if necessary). | The navigation application shows the navigation point as the address. | ||
| 2.03 | Select a job without a job address, but with a customer address without lat/longs. Click the Map button on Job Details (starting the job first if necessary). | The navigation application shows the navigation point as the address. | ||
| 2.04 | Repeat the above tests for TomTom PRO devices without WEBFLEET configured on the system. | As above. | ||
| 2.05 | Repeat the above tests for TomTom PRO devices with WEBFLEET configured on the system. | The TomTom NavApp will be shown without pointing to an address at all. |
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 | 0 | £0.00 |
| Change Request Evaluation | 0.00 | 0.00 | 0 | £0.00 |
| Functional Specification | 0.50 | 0.50 | 0 | £0.00 |
| Technical Specification | 0.00 | 0.00 | 0 | £0.00 |
| Development | 2.50 | 2.50 | 0 | £0.00 |
| Testing and Release | 0.50 | 0.50 | 0 | £0.00 |
| Implementation | 0.25 | 0.25 | 0 | £0.00 |
| Project Management | 0.25 | 0.25 | 0 | £0.00 |
| TOTAL | 4.00 | 4.00 | £0.00 | |
| 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
Barry Preece | OBSL Project Manager | _____________________________ |
Murray Middleton | OBSL Development Manager | _____________________________ |
