FS 343365 SCR-339867-01 Additional Premier Data Import
Marshalls Stone
Addition Premier Data Import
CALIDUS ePOD
14th June 2017 - 1.0
Reference: FS 343365 SCR-339876-01
Contents
Functional Overview
Client Requirement
Additional information is required to be sent to C-ePOD on the delivery job (in the job detail):
- Date/Time loaded.
- Loading point (plant).
- The loader (name).
- Sales Contact Telephone.
For Premier only, additional information is required to be sent to C-ePOD on the delivery product:
- Hopper.
- Depot Cone Test.
This will require modification of the data stored on the Jobs in C-ePOD.
Solution Overview
New fields will be added to the C-ePOD application to store:
- Job:
- Load Location.
- Loading Time (as Collection Time, Date is already present and will be used for the Loading Date).
- The name of the loader.
- The Sales Contact Telephone number.
- Product:
- Depot Cone Test.
- Hopper Number, held as Position in C-ePOD.
This information will be stored in the CALIDUS ePOD database and will be visible within the C-ePOD Admin system against the job and the products.
The information will be used in the Premier Mortars POD/POC report.
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.
In a change to the solution design document, the Hopper information will be sent to the mobile device application and will be displayed there.
Set-up
Pre-requisites
Menu Structure
Data
The UDF configuration for the "Product UDF" is as follows:
<FORM NAME="Product Details" REQUIRED="Y">
<FIELD ID="SITE_CONE_READING">
<TEXT>Site Cone Reading</TEXT>
<FORMAT>DDL</FORMAT>
<REQUIRED>Y</REQUIRED>
<ACTION>N</ACTION>
<ITEMS>
<ITEM CODE="12" DEFAULT="N" PHOTO_COUNT="0">12 or below</ITEM>
<ITEM CODE="13" DEFAULT="N" PHOTO_COUNT="0">13</ITEM>
<ITEM CODE="14" DEFAULT="N" PHOTO_COUNT="0">14</ITEM>
<ITEM CODE="15" DEFAULT="N" PHOTO_COUNT="0">15</ITEM>
<ITEM CODE="16" DEFAULT="N" PHOTO_COUNT="0">16</ITEM>
<ITEM CODE="17" DEFAULT="N" PHOTO_COUNT="0">17</ITEM>
<ITEM CODE="18" DEFAULT="N" PHOTO_COUNT="0">18 or above</ITEM>
</ITEMS>
</FIELD>
</FORM>
Note: The configuration is subject to changes relating to Product UDF for this project, specified elsewhere. The configuration will be made to MORTAR products for the Site only.
Functional Description
Database and Data Access Layer
The following fields will be added to the Product table EPOD_PRODUCT:
- EPL_POSITION - nvarchar(20) - Hopper for this implementation
- EPL_DEPOT_TEST - nvarchar(50)
These fields will be added to all stored procedures in the database that require them.
Only the EPL_POSITION field is required on the device.
These fields are required to be set on products imported through the standard XML import (flat file or webservice). The Import XSD will be modified to show these fields. None are required to be provided.
These fields are not required to be contained within the Export.
These fields are not required to be used when filtering data for selection.
The following fields will be added to the Job table EPOD_JOB:
- EPL_LOAD_LOCATION - nvarchar(40)
- EPL_COL_TIME - int
- EPL_LOADER - nvarchar(40)
- EPL_SALES_TEL - nvarchar(20)
These fields will be added to all stored procedures in the database that require them.
These fields are not required on the device.
These fields are required to be set on products imported through the standard XML import (flat file or webservice). The Import XSD will be modified to show these fields. None are required to be provided.
These fields are not required to be contained within the Export.
These fields are not required to be used when filtering data for selection.
Note: When this code is included in a build for release to a customer, the standard Import documentation must be created for this version including these new tags.
Admin
Job Screen
The Job screen (job_details.aspx) will be changed to show these new data elements.
Job Screen
The pop-up Edit screen (accessed by clicking Select against an existing job or clicking New to add a new job) will be changed to add these fields. The results table will not be modified. All fields will be added to the Details tab.
- Add Collection Date and Time, from fields EPL_COL_DATE and EPL_COL_TIME, labelled as "Collect Date/Time", after Arrival Date and Time. When editing or adding these values, standard Date calendars and date/time validation will be applied. These fields are not required and do not need to be entered by the user.
- Add Load Location and Loader, from fields EPL_LOAD_LOCATION and EPL_LOADER, after the new Collect Date/Time above, labelled as "Load Location/By". These are free text fields and require no additional validation. These fields are not required and do not need to be entered by the user.
- Add Sales Tel from field EPL_SALES_TEL, next to Sales Contact. Change the label to "Sales Contact/Tel". This is a free-text field and requires no additional validation. This field is not required and do not need to be entered by the user.
All new fields added will align with the existing fields on the pop-up.
Containers/Products Screen
The Containers/Products screen (product_containers.aspx) will be changed to show these new data elements.
Containers/Products Screen
The product pop-up Edit screen (accessed by clicking Select against an existing product or clicking New Product or New Loose Product to add a new product) will be changed to add these fields. The product results table will not be modified. All fields will be added to the Details tab.
- Add Position from field EPL_POSITION, to the right of "Case Qty", labelled as "Position". This is a free-text field and requires no additional validation. This field is not required and do not need to be entered by the user.
- Add Depot Cone Test from field EPL_DEPOT_TEST, to the right of "Unit VAT", under the new "Position" field, labelled as "Depot Test". This is a free-text field and requires no additional validation. This field is not required and do not need to be entered by the user.
All new fields added will align with the existing fields on the pop-up.
Mobile Device Changes
The following fields will be added to the Product table EPOD_PRODUCT:
- EPL_POSITION - nvarchar(20) - Hopper for this implementation
The Data Access Layer object PDA_PRODUCT will be modified to receive this field in the import from the server when requesting loads or receiving an update response. If not present, this should be defaulted to blank.
The Position field will be added to the Product List, with the label "Position" added before it. This will be translated as part of the style changes being done for the project, specified elsewhere.
The Position field will be added to the Product Info pop-up, with the label "Position" added before it. This will be translated as part of the style changes being done for the project, specified elsewhere. If there is no data in the Position field, do not add it to this pop-up.
Screen-shot samples:
Products List
Products Info Pop-up
Note that these screenshots are subject to the styling changes to be applied (specified elsewhere) and are for reference only.
Appendix A: TEST PLAN
| Test Script / Scenario Reference | Addition Premier Data Import | Call Number(s): 343365 SCR-339876-01 |
| Test Script / Scenario Description | Testing the new data requirements for Premier Mortars are met. | PASS / ISSUES / FAIL |
| Menu Access | Administration/Auto-Import | |
| Pre-requisites | A system configured as Marshalls. | Tested By: |
| Test Objective | To test: Auto-Import may import the new data through the XML format; webservice import may import the new data and; Admin displays and can maintain the new fields. | Date: |
| Step | Action | Result | Remarks | P/F |
| 1 | Import | |||
| Create a test XML file that contains all the new fields, compliant with the new XSD. Also create a file without all these field fields, for limit testing. | ||||
| 1.01 | Configure a file Auto-Import for Loads. Drop the file without the new fields into the specified directory and check the import log and jobs. | Loads, Jobs and Products created with no issues, but without the new data. | ||
| 1.02 | Drop the file with the new fields into the specified directory and check the import log and jobs. | Loads, Jobs and Products created with no issues, with the new data populated as expected. | ||
| 1.03 | Paste the contents of the file without the new fields into the webservice through a browser and check the import log and jobs. | Loads, Jobs and Products created with no issues, but without the new data. | ||
| 1.04 | Paste the contents of the file with the new fields into the webservice through a browser and check the import log and jobs. | Loads, Jobs and Products created with no issues, with the new data populated as expected. |
| Step | Action | Result | Remarks | P/F |
| 2 | Admin System | |||
| Ensure there are some jobs and products with the new data already added, as well as some jobs and products without the new data. | ||||
| 2.01 | In the jobs screen, add a new job, enter the new fields and save. Check the job. | The new fields are entered as expected, with validation as described. The data is saved, and redisplayed when the details are shown again. | ||
| 2.02 | In the jobs screen, find a job without any of the new data. Add the data, save and modify again. | The new fields are entered as expected, with validation as described. The data is saved, and redisplayed when the details are shown again. | ||
| 2.03 | In the Containers/Products screen, add a product (loose and within a container), enter the new fields and save. Check the product. | The new fields are entered as expected, with validation as described. The data is saved, and redisplayed when the details are shown again. | ||
| 2.04 | In the Containers/Products screen, find a product without the new data (loose and within a container). Add the data, save and modify again. | The new fields are entered as expected, with validation as described. The data is saved, and redisplayed when the details are shown again. |
| Step | Action | Result | Remarks | P/F |
| 3 | Mobile Device | |||
| Ensure there are some jobs and products with the new Position data. A style adding this Position field should be created. | ||||
| 3.01 | Log-in, download the load, start the job with the new Position (hopper) data and view the Products list. | The hopper should be displayed. | ||
| 3.02 | Select a product on this job and choose Product Info. | The hopper should be displayed. | ||
| 3.03 | Start a job without Hopper information. View the products list. | The hopper label will be displayed, but with no data. | ||
| 3.04 | Select a product and choose Product Info. | The hopper will not be displayed. |
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.75 | 1.00 | 750 | £750.00 |
| Technical Specification | 0.00 | 0.00 | 750 | £0.00 |
| Development | 3.50 | 4.50 | 750 | £3,375.00 |
| Testing and Release | 0.25 | 0.50 | 750 | £375.00 |
| Implementation | 0.25 | 0.25 | 750 | £187.50 |
| Project Management | 0.25 | 0.25 | 750 | £187.50 |
| TOTAL | 5.00 | 6.50 | £4,875.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 | _____________________________ |
