FS 315080 AUNZ-027 LFS Vehicle Checks Export
LFS
LFS Vehicle Checks Export
CALIDUS ePOD
24th February 2014 - 0.1
Reference: FS 315080 AUNZ-027
Contents
Functional Overview
Client Requirement
As part of the PDA’s configuration, drivers can be prompted to enter a number of mandatory and optional vehicle checks. These checks can be set on the frequency that the operation requires; for example, every 24 hours or weekly. It has been determined that the LFS drivers must perform a vehicle check once a day. These questions are fully configurable by system administrators within the EPOD admin system and include a combination of Check Box, Free Text, Boolean (Yes/No) and Number entry answers.
The driver must not be allowed to postpone the vehicle checks they must be performed
A new export will be created to extract all vehicle check data based on a date range, driver and or vehicle. This will be in csv format.
Solution Overview
As part of the PDA’s configuration, drivers can be prompted to enter a number of mandatory and optional vehicle checks. These checks can be set on the frequency that the operation requires; for example, every 24 hours or weekly. It has been determined that the LFS drivers must perform a vehicle check once a day. These questions are fully configurable by system administrators within the EPOD admin system and include a combination of Check Box, Free Text, Boolean (Yes/No) and Number entry answers.
The existing Vehicle Checks screen (accessible from the CALIDUS ePOD Admin system through Administration/Vehicle Checks Responses menu item) allows users to enter search criteria to find completed vehicle checks, as follows:
- Vehicle ID - optionally, the vehicle checked can be selected.
- User ID - optionally, the driver who performed the checks can be selected.
- Date From/To - a date range must always be entered, and will default to a one month period back from the current date.
Once the criteria has been entered, the user can either:
- Cancel - Do not perform the search.
- Search - Perform the search and display the results in a grid below.
- Extract to CSV - Perform the search and generate a CSV.
If extracting to CSV, the system will attempt to open the generated file automatically for the user. Depending on general browser type, settings and installed software, the file may open directly in the browser window, or through an external program, typically Microsoft Excel. However the file is opened, it may be saved locally at that time.
The CSV data will include the following and have the following restrictions:
- Fields included:
- Date/Time - the date and time the check took place, in YYYYMMDD and HHMM formats respectively
- Driver - Driver ID and Driver Name
- Vehicle - Vehicle ID and Vehicle Name
- Site - Site ID only
- All the questions and answers that were responded to by the driver will be added to the end of the CSV, in sequence, 2 columns for each (question text, followed by driver's response).
- All CSV data will be quote-encapsulated.
Scope
- This functionality will be developed in the latest version of CALIDUS ePOD only.
Set-up
Pre-requisites
- A working CALIDUS ePOD system.
Menu Structure
None
Data
None
Functional Description
Admin Changes
The existing Vehicle Checks screen Vehicle_check_response.aspx (accessible from the CALIDUS ePOD Admin system through Administration/Vehicle Checks Responses menu item) allows users to enter search criteria to find completed vehicle checks.
This criteria entry validation will be modified as follows:
- Vehicle ID - optionally entered
- User ID - optionally entered
- Date From/To - a date range must always be entered, and will default to a one month period back from the current date.
A new button will be added to the Search Criteria section:
- Extract to CSV
This button will perform the search as per the standard Search button, but will extract this to a CSV file rather than display the results in the grid.
The process will retrieve all the data through the standard DAL objects (along with any descriptions required for Vehicles and Users).
When retrieved, the resulting data should be exported directly back to the browser, setting various HTTP headers as follows:
- ContentType = "text/csv"
- Content-Disposition - "attachment;filename=export.csv"
The CSV data will include the following and have the following restrictions:
- Fields included:
- Date/Time - EPL_VEHICLE_CHECK_DATE and EPL_VEHICLE_CHECK_TIME
- Driver - EPL_USER_ID and EPOD_USER.EPL_USER_NAME
- Vehicle - EPL_VEHICLE_ID and EPOD_VEHICLE.EPL_VEHICLE_REG
- Site - EPL_SITE_ID
- All the questions and answers that were responded to by the driver will be added to the end of the CSV, in sequence, 2 columns for each (question text, followed by driver's response). This will be extracted from the XML content of EPL_VEHICLE_CHECK_DATA - examples below.
- All CSV data will be quote-encapsulated.
Note: All fields are sourced from EPOD_VEHICLE_CHECK, unless otherwise specified.
For example, if the data for a single vehicle check is as follows:
- EPL_SITE_ID:TEST
- EPL_VEHICLE_ID:ADM
- EPL_VEHICLE_CHECK_DATE:20130821
- EPL_VEHICLE_CHECK_TIME:13220000
- EPL_USER_ID:nhill
- EPL_VEHICLE_CHECK_DATA: <EPL_SITE_ID>TEST</EPL_SITE_ID> <EPL_VEHICLE_ID>ADM</EPL_VEHICLE_ID> <EPL_USER_ID>nhill</EPL_USER_ID> <DATE_TIME>2013-08-21T13:22:38</DATE_TIME> <VEHICLE_CHECK> <QUESTION ID="001"> <TEXT>Please enter your trailer number</TEXT> <FORMAT>T</FORMAT> <SKIPABLE>N</SKIPABLE> <ANSWER>123</ANSWER> </QUESTION> <QUESTION ID="002"> <TEXT>Please check the following items:</TEXT> <FORMAT>X</FORMAT> <SKIPABLE>N</SKIPABLE> <ITEMS> <ITEM ANSWER="Y">Oil Level</ITEM> <ITEM ANSWER="Y">Tyres</ITEM> <ITEM ANSWER="Y">Brakes</ITEM> <ITEM ANSWER="Y">Water</ITEM> <ITEM ANSWER="Y">Lights</ITEM> </ITEMS> </QUESTION> <QUESTION ID="003"> <TEXT>Please enter any comments</TEXT> <FORMAT>T</FORMAT> <SKIPABLE>Y</SKIPABLE> <ANSWER></ANSWER> </QUESTION> <QUESTION ID="004"> <TEXT>What is the current Mileage?</TEXT> <FORMAT>N</FORMAT> <SKIPABLE>N</SKIPABLE> <ANSWER>123</ANSWER> </QUESTION> </VEHICLE_CHECK> <REQUEST_TIME_DATE>2013-08-21T13:22:38</REQUEST_TIME_DATE>
The resulting CSV would look like this:
- "TEST", "ADM", "ADM 12BC", "20130821", "1322", "nhill", "Nick Hill", "Please enter your trailer number", "123", "Oil Level", "Y", "Tyres", "Y", "Brakes", "Y", "Water", "Y", "Lights", "Y", "Please enter any comments", "", "What is the current Mileage?","123"
If extracting to CSV, the system will attempt to open the generated file automatically for the user. Depending on general browser type, settings and installed software, the file may open directly in the browser window, or through an external program, typically Microsoft Excel. However the file is opened, it may be saved locally at that time.
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.00 | 0.50 | 0 | £0.00 |
| Technical Specification | 0.00 | 0.00 | 0 | £0.00 |
| Development | 0.00 | 2.50 | 0 | £0.00 |
| Testing and Release | 0.00 | 0.25 | 0 | £0.00 |
| Implementation | 0.00 | 0.25 | 0 | £0.00 |
| Project Management | First argument to "number_format" must be a number. | 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. | £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
Matt Tipping | Project Manager | _____________________________ |
____________________(PRINT) | Client Representative | _____________________________ |
