Latest revision as of 17:30, 29 April 2013

Air Link Services

Air Link EPOD Development

CALIDUS eSERV

25th April 2013 - 0.3
Reference: FS 308231

Functional Overview

Client Requirement

As described in the Requirements document, referenced in the Appendices.

Solution Overview

All changes required are broken down as follows:

SCR#	System	Area	Description	Estimate (Days)	Notes
1	eSERV	Admin	Add new Configuration Options to Job Group and Site.	N/A
2	eSERV	Admin	Custom style to change labels and hide unwanted elements.	N/A
3	eSERV	Admin	Add new elements to Job Details and Service Details screens.	N/A
5	eSERV	PDA	Add System Type to Info tab.	N/A
6	eSERV	PDA	Add Job Status to Diagnosis tab.	N/A
7	eSERV	PDA	Custom style the client to change labels and hide unwanted elements.	N/A
8	eSERV	PDA	Allow Back-out of Customer signature only in Service jobs.	N/A
9	eSERV	PDA	Allow optional Photo on finishing Job.	N/A
10	eSERV	Server	On Job Suspension, create an unassigned copy of the job.	N/A
11	eSERV	Admin	New Service Report format.	N/A

Scope

The changes will be made in the latest version of the CALIDUS eSERV system.
Although the document describes all changes discussed with the client, subsequent meetings have marked several changes as out of scope. Although these are referred to in several places throughout the document to identify the ideal process, if the initial change is marked out of scope, all references to it are also out of scope.
- SLA display (RAG Colouration)
- Maintenance Jobs
- Linked Product to System Type
- Reports
Images used in this document a representative of the final look and feel, although this may differ in the final delivered application.
Emailing of documents requires that the server has access to the customer's email server - to be provided by the customer is required.

Set-up

Pre-requisites

An installed and connected CALIDUS eSERV system.

Menu Structure

As normal

Data

Warning: Emailing of documents requires that the server has access to the customer's email server - to be provided by the customer if required.

The system will be configured as follows:

EPOD_SITE of "ALS":

Service format: ALS.
Logo: with the ALS logo.
Arrival Times - Enabled
Display Job Code on PDA - Enabled
Document Photo - Optional
Resequencing Options ("Y" - Free to Resequence)
Scan Errors Intrusive - Enabled
PODs PDF - Enabled
Service will be configured as follows:
- Info - Enabled (ALS)
- Diagnosis - Enabled (ALS)
- Products - Enabled
- Job Status - Enabled

EPOD_JOB_GROUP of "ALS":

Service format: ALS.
Document Photo - Optional
Service will be configured as follows:
- Info - Enabled (ALS)
- Diagnosis - Enabled (ALS)
- Products - Enabled
- Job Status - Enabled

EPOD_CUSTOMER of "ALS":

Set up the customer with this name, with the ALS address and contact information entered against it.

Functional Description

Database and DAL Changes

Table EPOD_SITE

EPL_JOB_STATUS - a flag to control whether EPL_JOB_STATUS will be prompted (initially for Services only). nvarchar(1), NOT NULL DEFAULT 'N', values 'Y' or 'N'.

Existing packages will be modified to allow the creating, editing and selecting of the new flag, including but not limited to:

EPOD_SITE_INSERT
EPOD_SITE_SELECT
EPOD_SITE_SELECT_UPDATED_DATA
EPOD_SITE_UPDATE

The existing EPOD_SITE DAL object will be changed to:

Export the new flag in XML requests
Read the new flag

Note: It is not necessary to add this flag as a searchable item. However, if allowing this keeps the packages and DAL objects standard in design, then this can also be done, within the DAL and the packages.

Table EPOD_JOB_GROUP

EPL_JOB_STATUS - a flag to control whether EPL_JOB_STATUS will be prompted (initially for Services only). nvarchar(1), NOT NULL DEFAULT 'N', values 'Y' or 'N'.

Existing packages will be modified to allow the creating, editing and selecting of the new flag, including but not limited to:

EPOD_JOB_GROUP_INSERT
EPOD_JOB_GROUP_SEARCH
EPOD_JOB_GROUP_SELECT
EPOD_JOB_GROUP_SELECT_UPDATED_DATA
EPOD_JOB_GROUP_UPDATE

The existing EPOD_JOB_GROUP DAL object will be changed to:

Export the new flag in XML requests
Read the new flag

Note: It is not necessary to add this flag as a searchable item. However, if allowing this keeps the packages and DAL objects standard in design, then this can also be done, within the DAL and the packages.

Existing package EPOD_SETUP will be modified to ensure that the new flags are defaulted appropriately.

Table EPOD_JOB

EPL_JOB_STATUS - Suspended or Complete (initially for Services only). nvarchar(2), NOT NULL DEFAULT ' ', values 'C' or 'S'.

Existing packages will be modified to allow the creating, editing and selecting of the new field, including but not limited to:

EPOD_JOB_INSERT
EPOD_JOB_SEARCH
EPOD_JOB_SELECT
EPOD_JOB_SELECT_DATE_RANGE
EPOD_JOB_UPDATE

The existing EPOD_JOB DAL object will be changed to:

Export the new field in XML requests
Read the new field
Add as a parameter and searchable item

Table EPOD_SERVICE_PRODUCT_MASTER

EPL_MODEL - The model of the system the product (part) is for. nvarchar(30).

Existing packages will be modified to allow the creating, editing and selecting of the new field, including but not limited to:

EPOD_SERVICE_PRODUCT_M_INSERT
EPOD_SERVICE_PRODUCT_M_SEARCH
EPOD_SERVICE_PRODUCT_M_SELECT
EPOD_SERVICE_PRODUCT_M_SELECT_UPDATED_DATA
EPOD_SERVICE_PRODUCT_M_UPDATE

The existing EPOD_SERVICE_PRODUCT_MASTER DAL object will be changed to:

Export the new field in XML requests
Read the new field
Add as a parameter and searchable item

Note: A new package and DAL method will be created to allow the retrieval of DISTINCT EPL_PRODUCT_GROUP of EPOD_SERVICE_PRODUCT_MASTER, for EPL_SERVICE_GROUP DDL values. This will accept parameters of EPL_SITE_ID only. Exclude Blank values of EPL_PRODUCT_GROUP.

Table EPOD_SERVICE

EPL_SERVICE_GROUP - The system type (e.g. Checkout, Cashtube, etc). nvarchar(10).
EPL_SYSTEM_TYPE - The model of the system the product (part) is for. nvarchar(30).

Existing packages will be modified to allow the creating, editing and selecting of the new field, including but not limited to:

EPOD_SERVICE_INSERT
EPOD_SERVICE_JOB_SEARCH
EPOD_SERVICE_JOB_SELECT
EPOD_SERVICE_SELECT
EPOD_SERVICE_UPDATE

The existing EPOD_SERVICE/SERVICE_JOB DAL object will be changed to:

Export the new fields in XML requests
Read the new fields
Add as parameters and searchable items

Note: A new package and DAL method will be created to iterate a value of EPL_SERVICE_ID to a new version. this procedure will:

Retrieve all EPL_SERVICE_ID values matching the start of the text value within the first and last underscores (_) of the field, if found, or all of the field.
If one found, trim, encapsulate in underscores and add an "A" to the end of the string.
If more than one found:
- Extract the highest string value after the final underscore for records where the ID starts with an underscore, contains two underscores and has trailing characters (the iteration string).
- Add 1 to the iteration string (i.e. A becomes B, X becomes Y, Z becomes AA, etc) and replace at the end of the string.

Examples:

EPL_SERVICE_ID = "1223" and is postponed. EPL_SERVICE_ID will become "_1223_A".
EPL_SERVICE_ID = "_1223_A" and is postponed again. EPL_SERVICE_ID will become "_1223_B".
EPL_SERVICE_ID = "1223_A" and is postponed. EPL_SERVICE_ID will become "_1223_A_A".
EPL_SERVICE_ID = "_1223_A_A" and is postponed again. EPL_SERVICE_ID will become "_1223_A_B".
EPL_SERVICE_ID = "_1223" and is postponed. EPL_SERVICE_ID will become "__1223_A".
EPL_SERVICE_ID = "__1223_A" and is postponed. EPL_SERVICE_ID will become "__1223_B".

Import/Export Changes

Other than those specified in the DAL changes above, there are no required changes to any generic or bespoke exports at this time.

Admin Changes

The CALIDUS eSERV system is configured and administered through a web Admin system. This is fully documented elsewhere and referenced in this document appendices. Certain elements will be modified as part of these changes to ensure that the system can be configured correctly for the customer's use.

The Job Group and Site screens (job_group.aspx and site_header.aspx respectively) will be modified to allow the system to be configured for:

Job Status - add field EPL_JOB_STATUS to the PDA tab as a check-box.
Optional Document Photo
- The existing maintenance of Document Photo will be re-labelled as Job Photo.
- The maintenance of the EPL_DOCUMENT_PHOTO field will change to allow values Y - Enabled, D - Disabled or O - Optional - this can either be modified to a DDL (and moved with the 'Resequencing Options' DDL to maintain a clear layout) and a tri-state check box can be implemented. Ensure that pop-up tool-tips adequately describe the value in the field if the tri-state check-box is used.
Configuration of new Service Report format - Add the new value/key "ALS" to the drop-down for EPL_SERVICE_POD_FORMAT.
Configuration of customer-specific Info entry:
- Change the Info check-box on the Services tab (field EPL_SERVICE_INFO) to a DDL and move to a different area away from the check-boxes.
- Allow the values N - Disabled, Y - Enabled (SM Fleet), A - Enabled (ALS). Note: This can use the new LIST features in Admin for these values or can be hard-coded.
Configuration of customer-specific Diagnosis entry:
- Change the Diagnosis check-box on the Services tab (field EPL_SERVICE_DIAGNOSIS) to a DDL and move to a different area away from the check-boxes.
- Allow the values N - Disabled, Y - Enabled (SM Fleet), A - Enabled (ALS). Note: This can use the new LIST features in Admin for these values or can be hard-coded.
Note: Ensure as part of this change that the existing check-boxes line up.

The existing Add and Edit pop-ups will be modified to allow these new fields and values. The grid will be modified to show the new values allowed on the Service Report format.

Note: The existing 'Resequencing Options' DDL shall be extended over the pan of two columns in this screen, rather than the one it currently takes, to allow for the greater width. If this requires restructuring the table in which these flags are displayed, then ensure this is completed - the layout will be cleaned up as part of this change.

The Job Details screen (job_details.aspx) will be modified to allow the user to:

Create Service jobs
- Add 'Service' to Job Type
- Add a new section (split the existing Instructions area in half, allowing Service information on the left-hand-side) if the job type is "Service" to include:
  - Service ID (unique entry required, default to EPL_JOB_CODE if entered or EPL_JOB_ID.
  - Service Type (values IS - Installation, S - Service, DS - Deinstallation). Default to "Service".
  - Service Group (e.g. Checkout, Cash Tube, Stamp M/C). The values in this field should be all results from DISTINCT EPL_PRODUCT_GROUP of EPOD_SERVICE_PRODUCT_MASTER, using the new DDL method created for the purpose. A default value ("Enter a Group") should be displayed if one has not been chosen.
- Validate when saving that the Service ID is unique.

Note: In the event of choosing to create a Service type job, the screen will need to create both a Job and Service record. There is a Job Service DAL object that may be helpful here, although using a separate Service DAL object may be better, given the way the screen currently works.

The Service Details screen (service_detail.aspx) will be modified to:

Change labels and remove unwanted items (e.g. VNOS)
- The Diagnosis field (EPL_DIAGNOSIS_NARRATIVE) is always displayed.
- If the SITE/JOB_GROUP EPL_SERVICE_DIAGNOSIS flag is set to Y, the two check-boxes will be displayed as now.
- If the SITE/JOB_GROUP EPL_SERVICE_DIAGNOSIS flag is set to A, the VNOS check-box will be removed, and the label of the Customer Damage check-box will become 'Misuse'.
Add Service Group, System Type and Job Status to the Information section:
- If the SITE/JOB_GROUP EPL_SERVICE_INFO flag is set to Y, display the exiting fields in the section.
- If the SITE/JOB_GROUP EPL_SERVICE_INFO flag is set to A, do not display the existing fields, but display only the new fields EPL_SERVICE_GROUP and EPL_SYSTEM_TYPE.
- If the new SITE/JOB_GROUP EPL_JOB_STATUS flag is set to "Y", add the value of the JOB_STATUS to this section at the bottom. This is in addition to the fields shown above.
Change the title to 'Service Details' in the header and the title of the browser as is standard in the rest of the system.

The Service Product Master screen (product_maintanance.aspx) will be modified to:

Add the new Model field (EPL_MODEL) when adding new service products (optional entry).
Add/change the new Model field when editing existing products (optional).
Add the new Model field to the grid.

A new Service Report format will be written for the operation, based on the existing Breakdown Report. The format has been prototyped and available in P:\EPOD\Correspondence\Air Link\AirLinkReport.html and is shown below:

Note: The printing of the report is browser-dependent and can differ in small ways from the sample above.

From top to bottom and left to right, the fields will be mapped as follows:

ALS Logo - EPL_LOGO of EPOD_SITE of EPL_SITE_ID of EPOD_JOB
ALS Address - Taken from the EPOD_CUSTOMER details for EPL_SITE_ID of EPOD_JOB: EPL_CUSTOMER_NAME, EPL_ADDRESS_1/2/3/4, EPL_POSTCODE, EPL_TELEPHONE.
Customer: and Address: - Taken from the EPOD_CUSTOMER details for EPL_CUSTOMER_CODE of EPOD_JOB, or EPOD_JOB_ADDRESS if exists: EPL_CUSTOMER_NAME, EPL_ADDRESS_1/2/3/4, EPL_POSTCODE.
Date: - EPL_START_ACTUAL_DATE of EPOD_JOB
Job No: - EPL_JOB_CODE of EPOD_JOB Note: This will be the same as the Service ID.
System Type: - EPL_SERVICE_GROUP and EPL_SYSTEM_TYPE of EPOD_SERVICE
System Fault - EPL_JOB_INSTRUCTION of EPOD_JOB
Rectification Required - EPL_DIAGNOSIS_NARRATIVE of EPOD_SERVICE
Job Suspended/Job Complete check-boxes - Set based on value of new field EPL_JOB_STATUS of EPOD_JOB.
Job Chargeable check-box - set based on whether the existing field EPL_CUSTOMER_DAMAGE = "Y"
Misuse check-box - set based on whether the existing field EPL_CUSTOMER_DAMAGE = "Y"
Materials Used section:
- Note: The customer agreed that the "NO" label (if no products were used) can be omitted from the design.
- Note: Only records of materials used should be shown on this list i.e. EPL_DIRECTION of EPOD_SERVICE_PRODUCTS = "U"
- Quantity - EPL_QUANTITY of EPOD_SERVICE_PRODUCT
- Description - EPL_DESCRIPTION of EPOD_SERVICE_PRODUCT_MASTER
- Part No. - EPL_PRODUCT_CODE of EPOD_SERVICE_PRODUCT
Time On Site: - EPL_ARRIVAL_TIME of EPOD_JOB
Time Off Site: - EPL_END_ACTUAL_TIME of EPOD_JOB
Customer Signature - EPL_JOB_SIGNATURE of EPOD_JOB (Base64-decoded image)
Print Name - EPL_SIGNATORY of EPOD_JOB
Engineer Name: - EPL_USER_NAME of EPOD_USER (from EPL_USER_ID of EPOD_LOAD)
Engineer Signature - EPL_ENG_SIGNATURE of EPOD_JOB (Base64-decoded image)
Date: - EPL_END_ACTUAL_DATE of EPOD_JOB

The report will be called 'Reports\ALS.aspx'. The code will be structured similarly to the existing report 'GenContnr.aspx'.

Android PDA Changes

Database and DAL Changes

Table EPOD_SITE

EPL_JOB_STATUS - a flag to control whether EPL_JOB_STATUS will be prompted (initially for Services only). text, NOT NULL DEFAULT 'N', values 'Y' or 'N'.

The existing PDA_SITE DAL object will be changed to:

Read the new flag
Import the flag from XML requests

Table EPOD_JOB_GROUP

EPL_JOB_STATUS - a flag to control whether EPL_JOB_STATUS will be prompted (initially for Services only). text, NOT NULL DEFAULT 'N', values 'Y' or 'N'.

The existing PDA_JOB_GROUP DAL object will be changed to:

Read the new flag
Import the flag from XML requests

Table EPOD_JOB

EPL_JOB_STATUS - Suspended or Complete (initially for Services only). text(2), NOT NULL DEFAULT ' ', values 'C' or 'S'.

The existing PDA_JOB DAL object will be changed to:

Export the new field in XML responses (after EPL_AMENDED_FLAG)
Read the new field
Update the new field

Table EPOD_SERVICE_PRODUCT_MASTER

EPL_MODEL - The model of the system the product (part) is for. text(30).

The existing PDA_SERVICE_PRODUCT_MASTER DAL object will be changed to:

Read the new field

Note: A new DAL method "SelectAllSystemTypes" will be created to allow the retrieval of DISTINCT EPL_MODEL of EPOD_SERVICE_PRODUCT_MASTER, for EPL_SYSTEM_TYPE DDL values. This will accept parameters of EPL_SITE_ID and EPL_SERVICE_GROUP only. If EPL_PRODUCT_GROUP is blank, all values of EPL_MODEL will be selected. Exclude Blank values of EPL_MODEL.

Table EPOD_SERVICE

EPL_SERVICE_GROUP - The system type (e.g. Checkout, Cashtube, etc). text(10).
EPL_SYSTEM_TYPE - The model of the system the product (part) is for. text(30).

The existing PDA_SERVICE DAL object will be changed to:

Export the new fields in XML requests (after EPL_SPEC_REQUIRED in the INFO section)
Read the new fields

Note: As the database structure is changing with this version, the default values must be carefully set and the database creation script modified to ensure that the standing data is re-downloaded from the server after the changes have been made. This is achieved by setting the "last version changed" variable (lngLastVersionDB) in DBConnection to the latest version number.

Services Info Tab

This tab currently contains the job-level information required for the Service.

This screen will be modified as follows:

The form will be changed into a scrolling vertical layout view, similar to the Diagnosis tab.
The module will ensure that this tab is displayed if the flag EPL_SERVICE_INFO is not "N"
If the flag EPL_SERVICE_INFO = "Y", the existing 4 fields will be displayed.
If the flag EPL_SERVICE_INFO = "A", a picker will be added for the new field EPL_SYSTEM_TYPE. This will be pre-populated with the values from the new PDA_SERVICE_PRODUCT_MASTER DAL method "SelectAllSystemTypes" described above, along with a default value ("Select a System Type").
Validation for completion will be changed to ensure that this field has had a value chosen, if configured this way.
Saving values will be changed to ensure that the configured fields are saved correctly.

Services Diagnosis Tab

This tab allows the user to enter Problem Diagnosis information.

This screen will be modified as follows:

The module will ensure that this tab is displayed if the flag EPL_SERVICE_DIAGNOSIS is not "N"
If the flag EPL_SERVICE_DIAGNOSIS is not "N", the Diagnosis field will always be present (EPL_DIAGNOSIS_NARRATIVE).
If the flag EPL_SERVICE_DIAGNOSIS = "Y", the VNOS and Customer Damage flags will be displayed as now.
If the flag EPL_SERVICE_DIAGNOSIS = "A":
- VNOS will be removed.
- 'Customer Damage' will be relabelled 'Misuse'.
If the new flag EPL_JOB_STATUS = "Y", a picker will be added with the following values:
- ' ' - 'Select the Job Status' (Default Value)
- 'C' - 'Complete'
- 'S' - 'Suspended'.
- Validation for completion will be changed to ensure that this field has had a value chosen, if configured this way.

Service Call Confirmation

Once all the information has been entered and the engineer clicks the Complete button, the PDA will prompt for the customer's signature.

This Signature screen will be modified so that the user can back out to the Services screen if:

The Job type is Service ONLY and;
The Signature Type is Customer ONLY.

Note: Once entered, the PDA will require the entry of Engineer signature. The user will not be able to back out of this signature.

The Document Photo process will be changed as follows:

The label and all references to the process will be re-labelled as 'Job Photo' - this will not be a customer style option, but a generic change.
The process will be called if the flag EPL_DOCUMENT_PHOTO is not "N". Note: This affects Collection, Delivery and Service processing.
If the value of the flag is "Y", the process will start immediately and will operate as now, in that back-out will not be allowed.
If the value of the flag is "O", the process will request the user whether they want to take a photo through a pop-up dialogue.
- If 'No' is selected, the process will return to job completion, where the job will be completed as normal and the user returned to the Job List to complete another call.
- If 'Yes' is selected, the process will start as now, allowing the user to take an image and enter a comment before confirming. In this case, however, back-out (through the Android Back button) will be allowed, discarding any image taken or comment entered, and completing the job as if no photo was requested.

Server PDA Message Processing

A service job will now be returned with details of Job Status, System Type and Service Group on it. These will be included in the SERVICE section of the JOB_UPDATE message, which will be in the following format:

<EPL_SITE_ID></EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_USER_ID></EPL_USER_ID>
<EPL_VEHICLE_ID></EPL_VEHICLE_ID>
<EPL_START_DATE_TIME></EPL_START_DATE_TIME>
<EPL_ARRIVAL_DATE_TIME></EPL_ARRIVAL_DATE_TIME>
<EPL_END_DATE_TIME></EPL_END_DATE_TIME>
<EPL_STATUS></EPL_STATUS>
<EPL_CONTACT></EPL_CONTACT>
<EPL_INVOICED></EPL_INVOICED>
<EPL_SIGNED_UNCHECKED></EPL_SIGNED_UNCHECKED>
<EPL_USER_NOTES></EPL_USER_NOTES>
<EPL_TNCS></EPL_TNCS>
<EPL_AMENDED_FLAG></EPL_AMENDED_FLAG>
<EPL_JOB_STATUS></EPL_JOB_STATUS>
<CONFIRMATION>
  <EPL_ENG_SIGNATURE></EPL_ENG_SIGNATURE>
  <EPL_JOB_SIGNATURE></EPL_JOB_SIGNATURE>
</CONFIRMATION>
<EXCEPTION type="job">
  <EPL_REASON_CODE></EPL_REASON_CODE>
</EXCEPTION>
<SERVICE>
  <PREWORK>
    <EPL_PREWORK_INTERIOR>OK</EPL_PREWORK_INTERIOR>
    <EPL_PREWORK_EXTERIOR>OK</EPL_PREWORK_EXTERIOR>
    <EPL_PREWORK_ELECTRIC>OK</EPL_PREWORK_ELECTRIC>
  </PREWORK>
  <POSTWORK>
    <EPL_POSTWORK_INTERIOR>OK</EPL_POSTWORK_INTERIOR>
    <EPL_POSTWORK_EXTERIOR>OK</EPL_POSTWORK_EXTERIOR>
    <EPL_POSTWORK_ELECTRIC>OK</EPL_POSTWORK_ELECTRIC>
  </POSTWORK>
  <INFO>
    <EPL_UNIT_TYPE>TR</EPL_UNIT_TYPE>
    <EPL_REG_NUMBER>REG ID</EPL_REG_NUMBER>
    <EPL_VIN_NUMBER>VIN NO</EPL_VIN_NUMBER>
    <EPL_MILEAGE>777</EPL_MILEAGE>
    <EPL_SIM_NUMBER></EPL_SIM_NUMBER>
    <EPL_SPEC_REQUIRED></EPL_SPEC_REQUIRED>
    <EPL_SERVICE_GROUP></EPL_SERVICE_GROUP>
    <EPL_SYSTEM_TYPE></EPL_SYSTEM_TYPE>
  </INFO>
  <MC_REF>
    <EPL_MC_REF_1>ref1</EPL_MC_REF_1>
    <EPL_MC_REF_2>ref2</EPL_MC_REF_2>
    <EPL_MC_REF_3>ref3</EPL_MC_REF_3>
    <EPL_MC_REF_4>ref4</EPL_MC_REF_4>
    <EPL_MC_REF_NARRATIVE>ref narrative</EPL_MC_REF_NARRATIVE>
  </MC_REF>
  <DIAGNOSIS>
    <EPL_DIAGNOSIS_NARRATIVE>diagnosis</EPL_DIAGNOSIS_NARRATIVE>
    <EPL_CUSTOMER_DAMAGE>Y</EPL_CUSTOMER_DAMAGE>
    <EPL_VNOS>Y</EPL_VNOS>
  </DIAGNOSIS>
  <PRODUCT>
    <EPL_PRODUCT_ID>MGF019</EPL_PRODUCT_ID>
    <EPL_QUANTITY>3</EPL_QUANTITY>
    <EPL_DIRECTION>U</EPL_DIRECTION>
    <EPL_RETURN></EPL_RETURN>
  </PRODUCT>
</SERVICE>

In the event that a job has been completed with a status of postponed (EPL_JOB_STATUS of EPOD_JOB = "P" on the inbound JOB_UPDATE message from a PDA into web service 'Calidus_epod.asmx'), the system will be modified to create a new copy of the job, with a new ID. The following lists show the tables that need to be copied and the fields to copy or of which to set the value.

EPOD_JOB

EPL_SITE_ID - Copy
EPL_JOB_ID - Generate a new ID
EPL_LOAD_ID - Blank
EPL_JOB_TYPE - Copy
EPL_JOB_GROUP - Copy
EPL_JOB_INSTRUCTION - Copy
EPL_JOB_SIGNATURE - Blank
EPL_REASON_CODE - Blank
EPL_STATUS - "P"
EPL_CUSTOMER_CODE - Copy
EPL_PHOTO_ID - Blank
EPL_ENG_SIGNATURE - Blank
EPL_SEQUENCE - Blank
EPL_START_PLANNED_DATE - Today
EPL_START_PLANNED_TIME - Now
EPL_END_PLANNED_DATE - Blank
EPL_END_PLANNED_TIME - Blank
EPL_START_ACTUAL_DATE - Blank
EPL_START_ACTUAL_TIME - Blank
EPL_END_ACTUAL_DATE - Blank
EPL_END_ACTUAL_TIME - Blank
EPL_DISTANCE_PLANNED - Copy
EPL_DISTANCE_ACTUAL - Blank
EPL_DRIVING_TIME - Blank
EPL_INVOICED - Blank
EPL_LAST_CHANGED_DATE - Today
EPL_LAST_CHANGED_TIME - Now
EPL_JOB_CODE - Copy
EPL_CUST_SIGNATORY - Blank
EPL_CUST_REF - Copy
EPL_OFFICE_INSTRUCTION - Copy
EPL_XFER_FLAG - Blank
EPL_EMAIL_FLAG - Blank
EPL_SIGNED_UNCHECKED - Blank
EPL_SO_NUMBER - Copy
EPL_ORDER_DATE - Copy
EPL_SALES_CONTACT - Copy
EPL_USER_NOTES - Blank
EPL_OWNER_NAME - Copy
EPL_TNCS - Blank
EPL_LINKED_REASON - Blank
EPL_SERVICE_LEVEL - Copy
EPL_XFER_TTM_FLAG - Blank
EPL_AMENDED_FLAG - "N"
EPL_ARRIVAL_DATE - Blank
EPL_ARRIVAL_TIME - Blank
EPL_XF_VALUES - Blank
EPL_EXT_REF - Copy
EPL_TRAILER_ID - Blank
EPL_PF_DEPOT - Blank
EPL_PF_TRACKING_NO - Copy
EPL_JOB_STATUS - Blank

EPOD_JOB_ADDRESS

Copy the whole record to the new EPL_JOB_ID if present.

EPOD_SERVICE

EPL_SITE_ID - Copy
EPL_JOB_ID - Copy from EPOD_JOB record created
EPL_SERVICE_ID - Iterate to a new version using the new DAL procedure for this purpose.
EPL_SERVICE_TYPE - Copy
EPL_PREWORK_INTERIOR - Blank
EPL_PREWORK_EXTERIOR - Blank
EPL_PREWORK_ELECTRIC - Blank
EPL_POSTWORK_INTERIOR - Blank
EPL_POSTWORK_EXTERIOR - Blank
EPL_POSTWORK_ELECTRIC - Blank
EPL_UNIT_TYPE - Copy
EPL_REG_NUMBER - Copy
EPL_VIN_NUMBER - Copy
EPL_MILEAGE - Copy
EPL_SIM_NUMBER - Copy
EPL_MC_REF_1 - Blank
EPL_MC_REF_2 - Blank
EPL_MC_REF_3 - Blank
EPL_MC_REF_4 - Blank
EPL_MC_REF_NARRATIVE - Blank
EPL_DIAGNOSIS_NARRATIVE - Blank
EPL_SPEC_REQUIRED - Blank
EPL_FAULT - Blank
EPL_CUSTOMER_DAMAGE - Copy
EPL_VNOS - Blank
EPL_LAST_CHANGED_DATE - Today
EPL_LAST_CHANGED_TIME - Now
EPL_SERVICE_GROUP - Copy
EPL_SYSTEM_TYPE - Copy

Appendix A: TEST PLAN

Test Script / Scenario Reference	Air Link EPOD Development	Call Number(s): 308231
Test Script / Scenario Description	To test all added functionality	PASS / ISSUES / FAIL
Menu Access	Various
Pre-requisites	Set up as per the specification	Tested By:
Test Objective	To test the additions to the services functionality for ALS.	Date:

Step	Action	Result	Remarks	P/F
1	Admin (1)

1.01	Site: Ensure new fields can be added and maintained in the Site screen	New fields can be set, changed and saved: Job Status check-box Optional Document Photo DDL New Service Report format can be chosen, changed, saved and displayed in the grid. Customer-specific Service Info flag can be set, changed and saved. Customer-specific Service Diagnosis flag can be set, changed and saved. The tabs are well organised, making good use of space.
1.02	Job Groups: Ensure new fields can be added and maintained in the Job Group screen	New fields can be set, changed and saved: Job Status check-box Optional Document Photo DDL New Service Report format can be chosen, changed, saved and displayed in the grid. Customer-specific Service Info flag can be set, changed and saved. Customer-specific Service Diagnosis flag can be set, changed and saved.
1.03	Job Details: Ensure that standard Collection and Delivery jobs can be added, edited and saved through the screen.	As expected
1.04	Create a Service call	The Service Call Info box should be displayed.
1.05	Do not enter any required fields - click Save	Validation errors should be displayed for all missing fields
1.06	Create a service with no Service ID or Job Code. Save.	Service ID should default to the Job ID
1.07	Create a service with no Service ID but has a Job Code. Save.	Service ID should default to the Job Code.
1.08	Create a service with a duplicate Service ID. Save.	An error should be displayed.
1.09	Ensure Service Group allows the required values.	The DDL should allow entry of any Product Groups entered against the Service Products, as well as a default value ("Enter a Group").
1.10	Find a service job and click Details.	The Service Details screen is displayed.
1.11	Service Product Master: Enter a new product without a Model.	This is allowed, the record is saved and can be retrieved and seen in the grid.
1.12	Enter a new product with a Model.	This is allowed, the record is saved and can be retrieved and seen in the grid.
1.13	Find any product and edit it.	The Model can be changed and saved.

Step	Action	Result	Remarks	P/F
2	PDA Tests
	First, set up normal services under one job group (i.e. not ALS configuration), enabling all tabs, setting Document Photo to Enabled.
2.01	Test a service through to Signature.	* All tabs should show as normal All original fields should show with original labels. Validation should pass without checking new fields
2.02	Back out of signature	Allowed
2.03	Complete call and Enter customer signature. Back out of engineer signature.	Not allowed
2.04	Complete Signature.	Document Photo should start and not allow backout.
	Second, set up as ALS required above under a new Job Group. Ensure Site changes are made. Log out and log back in. Ensure all jobs completed from this point onwards and for the second Job Group.
2.05	Test a service through to Signature (ensuring job status "Complete").	* Only required tabs should show All new fields should show with new labels. Validation should check new fields, while ignoring old fields.
2.06	Back out of signature	Allowed
2.07	Complete call and Enter customer signature. Back out of engineer signature.	Not allowed
2.08	Complete Signature.	Unit should prompt whether document photo required.
2.09	Say Yes	Document Photo should start.
2.10	Backout	Returned to job list. Job Complete.
2.11	Complete another service call (ensuring job status "Postpone"). At Document Photo prompt say No.	Returned to job list. Job Complete.
2.12	Complete another service call (ensuring job status "Complete"). At Document Photo prompt say Yes.	Prompted to enter a photo.
2.13	Take an image, give a comment and complete.	Returned to job list. Job Complete.

Step	Action	Result	Remarks	P/F
3	Admin (2)

3.01	Search for the postponed job	A copy should have been created (Pending), with all the correct fields copied. The original should be closed with Job Status "Postponed".
3.02	Search for all completed jobs. Check the Service Details screens for these jobs.	Ensure that all required sections are shown in the screen (based on the job selected and the assigned Job Group) and that the entered details are present.
3.03	Check the Service Report for the completed call, in both Job Groups.	The format for each job group is displayed correctly.

Appendix B: Document References

B.1 References

Ref No	Document Title & ID	Version	Date
1	REQ 308231 Airlink Requirements	1.0	17/04/2013
2	UG 291094 EPOD Admin User Guide	2.0	4/04/2012
3	UG 291097 EPOD Client User Guide	3.0	23/04/2013

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

Jamie Foster

OBS Project Manager

_____________________________

Anonymous

Search

FS 308231 Air Link EPOD Development: Difference between revisions

Namespaces

More

Page actions

Latest revision as of 17:30, 29 April 2013

Contents

Functional Overview

Client Requirement

Solution Overview

Scope

Set-up

Pre-requisites

Menu Structure

Data

Functional Description

Database and DAL Changes

Import/Export Changes

Admin Changes