FS 327764 SCR-324746-5 Vehicle Checks at End of Load
Cooper Callas
Vehicle Checks at End of Load
CALIDUS ePOD
22nd July 2015 - 1.0
Reference: FS 327764 SCR-324746-5
Contents
Functional Overview
Client Requirement
SCR-324746-5: Vehicle Checks at End of Load SCR-324746-2: Customer Styling of the PDA device application.
Solution Overview
- Customer Styling of the PDA device application.
The application will haver a customised style created for Cooper Callas, which will include:
- An appropriate colour scheme
- The logo on the login page.
- All Text entry fields forcing upper-case text.
- Additionally, the layout of certain on the tables and test labels may be modified if required, and confirmed before development begins on the project work.
- Vehicle Checks at End of Load
Once all Jobs have been completed, the Load will be marked as completed when the user returns to the Job List screen.
At this time, if configured to do so, the device will be changed to prompt the user to enter vehicle checks again.
The vehicle checks prompted for will be the same checks as were prompted at the start of the load. The system will always prompt for the load end vehicle checks, regardless of how frequently the vehicle checks have been completed. The driver will be forced to enter the vehicle checks before continuing.
Once complete, the device will attempt to download a new load for the user and/or vehicle. If one has not been provided, the device will confirm this and allow the user to check again or log off the system.
Scope
- The changes will be made to the latest version of the CALIDUS ePOD system.
- This specification combines the changes for the following two SCRs only:
- SCR-324746-5: Vehicle Checks at End of Load
- SCR-324746-2: Customer Styling of the PDA device application.
Set-up
Pre-requisites
A valid CALIDUS ePOD system is required.
Menu Structure
None
Data
Site
Site/Vehicle Checks Maintenance
Site "COO" must be created and Vehicle Checks must be configured for the site, and the new flag "Vehicle Checks at Load End" should be Enabled
The expected checks to be configured are:
- Under Bonnet Checks - all required entry
- Engine Oil / Water top up as required - Pass/Fail/NA
- Brake Fluid / Screen wash levels top up as required - Pass/Fail/NA
- Visible leaks report - Pass/Fail/NA
- Oil installed - Pass/Fail/NA
- External Checks - all required entry
- Lights, Indicators, Stop lamps Operations / Conditions - Pass/Fail/NA
- Reflectors, Emergency Beacons Operations / Conditions - Pass/Fail/NA
- Windscreen Wipers, Number Plates Condition / Security - Pass/Fail/NA
- Wheels Condition / Security - Pass/Fail/NA
- Tyres Inflation / Damage / Wear - Pass/Fail/NA
- Doors Locks / Operation of catches, etc - Pass/Fail/NA
- Screen, Side windows, Mirrors Cracks / Security - Pass/Fail/NA
- Body work Dents / Scrapes - Pass/Fail/NA
- Trailer Couplings, Airlines, Marker plates As applicable - Pass/Fail/NA
- Ancillary equipment Taillift / On board generator, etc - Pass/Fail/NA
- Interior Checks - all required entry
- O License, Tax disc Present / Valid - Pass/Fail/NA
- Brakes Pedal pressure / Condition / Operation - Pass/Fail/NA
- Parking brake Operation - Pass/Fail/NA
- Driving controls Wear / Freedom of operation - Pass/Fail/NA
- Horn, Heater, Demister Operation - Pass/Fail/NA
- Instruments, Warning lights Operation - Pass/Fail/NA
- Seats, Seat belts Wear / Damage / Operation - Pass/Fail/NA
- On road checks - all required entry
- Speedo, Tachograph Operation - Pass/Fail/NA
- Exhaust Noise / Smoke - Pass/Fail/NA
- Defect Number Raised: - Optional Text Entry
Note: This configuration may be changed during implementation.
Mobile Device
The mobile device should be configured to use site COO and style Cooper Callas.
Functional Description
Admin Changes
Vehicle Checks Maintenance
Vehicle Checks Maintenance
A new flag should be added to the header on this screen (on a new line between "Check Freq Days" and "Total Questions") labelled as "Required at Load End: ". This should be a checkbox, defaulting to unchecked.
When saved, this should be saved as an attribute to the Vehicle Checks main tag, called AT_END. If checked, the value of this should be "Y", otherwise "N".
Mobile Device Modifications
Style
A new style labelled as "Cooper Callas" will be added to the preferences screen.
The Cooper Callas logo will be added to the project, labelled as altLogo14.png. This will be taken from the official Cooper Callas logo documentation provided to OBS Logistics.
The style of the buttons will stay in the standard blue style.
The Cooper Callas style created will have all general text fields defaulting the device keyboard into upper case characters.
Signature screen, with keyboard in Upper case
Note: Developer Note: For reference, this is the following classes:
- UDFEntry
- generalText
- generalNotes
Additionally, the following fields will have the class generalText added to them:
- Cancellation.imageTB
- DocumentPhoto.imageTB
- Signature.sigNameTB
Login Screen
For the Cooper Callas style only, the Login screen will use the Cooper Callas logo added above.
Login screen, with keyboard in Upper case
Job List
For the Cooper Callas style only, the job list will be modified to display as follows:
- Job Reference
- Job Type
- Customer Name
- Planned Date/Time
- Post Code
Job List screen
The Job List screen will be modified to call the vehicle checks screen on completion of the Load, after Load Metrics have been completed. Note that this is not dependent on load metrics being completed to be run (i.e. if load metrics is disabled for the end of the load, the vehicle checks process should still be called if configured to do so).
Only on successful return from vehicle checks will the device attempt to retrieve another load.
Vehicle Checks
The vehicle checks process will be modified to have an additional parameter p_blnEnd, to define at what time the vehicle checks have been called (i.e. at the start - false - or at the end - true - of the load). If this has not been passed, the process should assume this to be false i.e. vehicle checks have been called at load start.
The Vehicle Checks configuration will now contain another attribute AT_END, which may be set to "Y" or "N".
If the new function parameter b_blnEnd is true, the Vehicle Checks process should check if this attribute and store the value - if the attribute does not exist, this should default to "N". If the value is "N", the process should exit, calling the callback function specified in the process call.
If the value of this attribute is "Y", the process should ignore all checks on date - the vehicle checks must be completed.
If the value of this attribute is "Y", the back-out processing (triggered when the back button if pressed on the device) should change:
- If postponement is allowed, the Exit button should be removed from the alert dialogue.
- If postponement is not allowed, the alert should change to a message of "You must complete the Vehicle Checks", with only the option "OK" to clear the alert. The screen should not exit but return to the Vehicle Checks screen.
Note: The fields displayed in the Vehicle Checks screen will be as configured in the Admin system. They are displayed on a vertically scrolling screen, with check boxes to enter the details of Pass (a green tick box), Fail (a red cross) or N/A (not applicable).
Vehicle Checks Sample
Collection/Delivery
For the Cooper Callas style only, the Collection/Delivery Products table will be modified to display as follows:
- Product Code
- Long Description
- Reference
- Planned Quantity
Products screen
All other possible elements will not display.
Note: The length of the long description will be such that the table rows may be very large. The row will grow or shrink depending on the data length, to always show the full description.
Appendix A: TEST PLAN
| Test Script / Scenario Reference | Vehicle Checks at End of Load | Call Number(s): 327764 SCR-324746-5 |
| Test Script / Scenario Description | To show device can be configured for the customer style, vehicle checks are configurable and can be prompted for at Load End. | PASS / ISSUES / FAIL |
| Menu Access | Administration/Site/Vehicle Checks | |
| Pre-requisites | Vehicle Checks are configured with the suggested questions, on a once-per-day basis. | Tested By: |
| Test Objective | To test that: device can be configured for the customer style; Vehicle Checks can be configured for Load End and; Vehicle Checks are prompted as expected. | Date: |
| Step | Action | Result | Remarks | P/F |
| 1 | Admin - Configuration | |||
| 1.01 | In the Site maintenance screen, click Vehicle Checks. | The new configuration check box "Required at Load End" is present and unchecked. | ||
| 1.02 | Edit the settings and check the box. Click Update. | The vehicle checks are saved with the new check box enabled. The screen displays this. | ||
| 1.03 | Edit the settings and uncheck the new configuration parameter. Click Update. | The vehicle checks are saved with the new check box enabled. The screen displays this. |
| Step | Action | Result | Remarks | P/F |
| 2 | Mobile Device | |||
| Ensure the new configuration flag "Required at Load End" is unchecked. Ensure Load End Metrics are not enabled. Ensure checks are Required for a frequency of 1 day. Ensure that there are several loads created with 1 job on each. | ||||
| 2.01 | Log on to the device for a vehicle. | Vehicle Checks should be prompted for. | ||
| 2.02 | Attempt to back out of vehicle checks (using the device's back button) | This should not be allowed - a dialogue should display requesting the user to log out or complete vehicle checks. | ||
| 2.03 | Log out and log back in. Complete vehicle checks. | The load should display. | ||
| 2.04 | Log out and log back in. | Vehicle Checks should not be prompted for. The load should display. | ||
| 2.05 | Complete the load | No vehicle checks should be prompted for - the device should prompt for retrieving another load. | ||
| 2.06 | Change the configuration of Vehicle Checks to Require at Load End. Log off and back on to the device using the same vehicle. | No start vehicle checks should be prompted for (as the last check completed was less than 1 day previous). | ||
| 2.07 | Complete the load. | Vehicle checks should be prompted for after completion of the job. | ||
| 2.08 | Attempt to back out of vehicle checks (using the device's back button) | This should not be allowed - a dialogue should display requiring the user to complete vehicle checks. | ||
| 2.09 | Complete the vehicle checks. | Another load should be displayed. | ||
| 2.10 | Change the configuration of the site to require Load End Metrics (any metrics at all may be configured). Log off and back onto the devie using the same driver but a different vehicle. | Vehicle Checks should be prompted for. | ||
| 2.11 | Complete the load. | Load Metrics should be prompted for after completion of the job. | ||
| 2.12 | Complete the Load Metrics. | Vehicle checks should be prompted for after completion of the metrics. | ||
| 2.13 | Complete the Vehicle Checks. | Another load should be displayed. |
| Step | Action | Result | Remarks | P/F |
| 3 | Mobile Device - Customer Style | |||
| Ensure the device is configured to the Cooper Callas style. Ensure there is a load ready with one job, with products. | ||||
| 3.01 | Start the application and enter user and password. | The login screen should show the Cooper Callas logo. The username and password should default the keyboard to uppercase. | ||
| 3.02 | Enter Vehicle Checks | Any text entry boxes should default the keyboard to uppercase. | ||
| 3.03 | Start a job and enter a product in the Enter Products text box. | The keyboard should default to uppercase. | ||
| 3.04 | Cancel a product. Take an image. Enter a description. | The keyboard should default to uppercase. | ||
| 3.05 | Complete all products on the job. Enter a signatory. | The keyboard should default to uppercase. | ||
| 3.06 | Complete the signature and take a job photo. Enter a description. | The keyboard should default to uppercase. |
Appendix B: Quote & Document References
| Cost Details | |||
| Activity | No. of Days | Rate per Day (£) | Cost (£ Exc. VAT) |
| Requirements | 0.00 | 750 | £0.00 |
| Change Request Evaluation | 0.00 | 750 | £0.00 |
| Functional Specification | 0.75 | 750 | £562.50 |
| Technical Specification | 0.75 | 750 | £562.50 |
| Development | 2.75 | 750 | £2,062.50 |
| Testing and Release | 0.50 | 750 | £375.00 |
| Implementation | 0.25 | 750 | £187.50 |
| Project Management | 0.50 | 750 | £375.00 |
| TOTAL | 5.50 | £4,125.00 | |
| Estimate excludes training, release to live and go live support. |
B.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | UG 291094 EPOD Admin User Guide | 3.0 | 16/10/2014 |
| 2 | UG 291097 EPOD Client User Guide | 4.0 | 16/10/2014 |
| 3 | REQ 324746 Cooper Callas ePOD Requirements | 1.1 | 29/06/2015 |
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
Matthew Tipping | OBS Logistics Project Manager | _____________________________ |
Philip Carr | Client Representative | _____________________________ |
