FS 343619 SCR-339867-10 Create TTM Stop Number
Marshalls Stone
Create TTM Stop Number
CALIDUS ePOD
15th June 2017 - 1.0
Reference: FS 343619 SCR-339867-10
Contents
Functional Overview
Client Requirement
SCR-339867-10 Create TTM Stop Number
Premier Mortar and Screed trips may be single- or multi-drop:
- Go to Delivery drop 1
- Go to Delivery drop 2
- Go to Delivery drop 3
- Go to Delivery drop 4
- Go to Delivery drop 5
In-between the drops, the vehicle may come back to the depot. In this case, they will use the TomTom unit to manually navigate, using the Favourites menu.
Note: Premier Mortars typically require the first job of the day to be completed first, then all subsequent jobs can be completed in any sequence. With the current process, morning and afternoon deliveries are planned onto separate loads. In the future, it is possible that these may be planned onto the same load. In this case, Morning orders should be enforced to be completed before afternoon orders.
Due to the nature of the orders on the trips being predominantly un-sequenced, this then requires a change to the interface to CALIDUS Portal from CALIDUS ePOD. This change will generate an expected drop sequence of the orders on the trip, to maintain consistency of data in Portal.
Solution Overview
A new Site-level configuration flag will be created to control the generation of CALIDUS Portal TTM stop numbers.
When sending Trip details to CALIDUS Portal TTM, the process will order the jobs on the load in the same sequence as on the mobile device, namely:
- Sequence ascending (non-numbers and zeroes at end)
- Planned Date and Time ascending
- Job Type (order D|S|C)
- Vehicle Swap (Delivery swap after delivery, collection swap before collection)
- Link ID
At this time, the process will check the configuration of the new Site-level flag.
If not enabled, the process will work as now, i.e. sending through the value in the sequence to TTM as the drop number.
If the new flag is enabled, the process will check whether drop numbers have been generated for the jobs on this load. If any jobs do not have a drop number, all of the drop numbers will be recalculated for the load.
A drop number will be assigned to each distinct job, in sequence, in the order in which the jobs are retrieved (as above).
If the job has a linked ID (i.e. is consolidated with another job), the process will check jobs with that link ID on that trip and assign the same stop ID to each job with that linked ID.
Scope
Changes will be made to latest version of CALIDUS ePOD only, and will require an update to all application components and full system and user acceptance testing.
Set-up
Pre-requisites
Menu Structure
Data
The Site configuration may be set as follows:
- The new Site-level flag "Create TTM Stops" will be checked.
Site Screen
Functional Description
Database and Data Access Layer
The following field will be added to the Site table EPOD_SITE:
- EPL_CREATE_TTM_STOPS_IND - int - default 0.
This field will be added to all stored procedures in the database that require it.
This field is required to be exported to the device.
This field is not required to be used when filtering data for selection.
The following field will be added to the Site table EPOD_SITE:
- EPL_TTM_STOP_NUMBER - int - default 0.
This field will be added to all stored procedures in the database that require it.
This field is not required to be exported at any time.
This field is not required to be used when filtering data for selection.
When creating EPOD_LOAD objects from the EPOD_LOAD_XFCONFIG object, the jobs must be sequenced on the load in the same sequence as on the mobile device, namely:
- Sequence ascending (non-numbers and zeroes at end)
- Planned Date and Time ascending
- Job Type (order D|S|C)
- Vehicle Swap (Delivery swap after delivery, collection swap before collection)
- Link ID
This will require a modification (or overloading) of the EPOD_JOB_SELECT method of EPOD_JOB.
The EPOD_LOAD and EPOD_LOAD_XFCONFIG DAL objects will be modified to ensure that the jobs are created in this sequence on the device.
Admin
Site Screen
The Site screen (site.aspx) will be changed.
Site Screen
A check flag will be added under the "Export Load Photos" flag (and under any other new flags - see the above image where the new flag is under "Jobs with Notes Amended"). This will be based on the new field EPL_CREATE_TTM_STOPS_IND. This flag will be labelled as "Create TTM Stops", with the pop-up help text "If checked, Stop Numbers will be generated for all jobs on a load when exported to TTM". The flag should default to unchecked (value 0). If checked, the value is considered "1".
Export Process
The Auto-Export process (EPOD_SYS_EXPORT.cs, function ExportTTM) will be modified for this purpose.
When sending Trip details to CALIDUS Portal TTM (function GenerateTRPContent from ExportTRP), the process will order the jobs on the load in the same sequence as on the mobile device, namely:
- Sequence ascending (non-numbers and zeroes at end)
- Planned Date and Time ascending
- Job Type (order D|S|C)
- Vehicle Swap (Delivery swap after delivery, collection swap before collection)
- Link ID
This will be achieved through the DAL object changes specified above.
At this time, the process will check the configuration of the new Site-level flag EPL_CREATE_TTM_STOPS_IND.
If not enabled (i.e. value 0), the process will work as now, i.e. sending through the value in the sequence to TTM as the stop number.
If the new flag is enabled (i.e. value 1), the process will check whether drop numbers have been generated for the jobs on this load. If any jobs do not have a drop number, all of the drop numbers will be recalculated for the load.
A drop number will be assigned to each distinct job, in sequence, in the order in which the jobs are retrieved (as above).
If the job has a linked ID (i.e. is consolidated with another job), the process will check jobs with that link ID on that trip and assign the same stop ID to each job with that linked ID.
Once this process is complete, the process will use the new EPOD_TTM_STOP_NUMBER field in preference to the EPL_SEQUENCE field.
Note: Alternatively, the EPL_TTM_STOP_NUMBER field can be pre-set to the value of the EPL_SEQUENCE field if this new Site flag EPL_CREATE_TTM_STOPS_IND is value 0 (i.e. the standard mechanism). In this case, the stop number should be converted from the character sequence. If there are non-numeric values in the trimmed EPL_SEQUENCE field, these should be set to 0.
Appendix A: TEST PLAN
| Test Script / Scenario Reference | Create TTM Stop Number | Call Number(s): 343619 SCR-339867-10 |
| Test Script / Scenario Description | Testing export of stops to TTM | PASS / ISSUES / FAIL |
| Menu Access | ||
| Pre-requisites | A system configured as Marshalls. | Tested By: |
| Test Objective | To test that: Jobs are sent to TTM with stops generated by the export process. | Date: |
| Step | Action | Result | Remarks | P/F |
| 1 | Admin System | |||
| 1.01 | In Admin, enter the Sites screen and check the changes to the Admin tab. | The new Create TTM Stops flag is present as a check box. Changing this flag and saving correctly saves the values. |
| Step | Action | Result | Remarks | P/F |
| 2 | Export | |||
| 2.01 | Set the new Site-level flag "Create TTM Stops" to unchecked. Import a new load with sequenced jobs with values in the EPL_SEQUENCE job field, one with an alphabetic value in the field and one with spaces. | The value in the EPL_SEQUENCE field is sent to TTM, converted to 0 for the non-numeric values | ||
| 2.02 | Set the new Site-level flag "Create TTM Stops" to checked. Import a new load with sequenced jobs with values in the EPL_SEQUENCE job field, one with an alphabetic value in the field and one with spaces. Ensure that the jobs are in unordered sequence on the load. Ensure one job is linked (consolidated) with another. | The TTM Stop number is set based on the described order of the jobs rather than the value in EPL_SEQUENCE. |
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 | 1.00 | 1.00 | 750 | £750.00 |
| Technical Specification | 0.00 | 0.00 | 750 | £0.00 |
| Development | 5.00 | 5.00 | 750 | £3,750.00 |
| Testing and Release | 0.50 | 0.50 | 750 | £375.00 |
| Implementation | 0.25 | 0.25 | 750 | £187.50 |
| Project Management | 0.25 | 0.25 | 750 | £187.50 |
| TOTAL | 7.00 | 7.00 | £5,250.00 | |
| Estimate excludes training, release to live and go live support. |
B.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | REQ 339867 Marshalls Premier Mortars Solution Design | 1.3 | 25/05/2017 |
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 Turner | OBSL Account Manager | _____________________________ |
Simon Martin | Customer Representative | _____________________________ |
Debbie Linley | Customer Representative | _____________________________ |
