Lanemark International

Lanemark eSERV Requirements

CALIDUS eSERV

11th June 2013 - 0.3
Reference: REQ 309371

Introduction

This document is the Lanemark eSERV Requirements.

Objective

The primary purpose of this document is to document the requirements gathered from Lanemark International during the sales process, and to present an overview of the process that will be followed in and the work required to the CALIDUS eSERV system.

This document has been written in a manner such that it can be approved by non-technical representatives of Lanemark International whilst also being of sufficient detail to allow the Functional or Technical Specification phase for this area to begin.

Scope and Limitations

This document is based on the documentation provided by the OBS Logistics Sales team.

This document reflects the work that will be required to the CALIDUS eSERV system - no provision is made here to any changes required regarding interfacing to and from the NAV system being used. Additional development may be required and should be specified separately.
The changes will be made in the latest version of the CALIDUS eSERV system.
The changes have been specified with the Android PDA client in mind.

Client Requirements

Overview

The customer requires a Service execution module, which will be provided by CALIDUS eSERV.

Service Jobs will be sent to CALIDUS eSERV from Microsoft Dynamics NAV (hereafter NAV).

Required Functionality:

Vehicle checks
Login
One job with multiple service items
One risk assessment per service item to be done at start of job
If risk assessment is passed then just engineer signs. If failed then engineer and customer sign and job is cancelled. Note: Lanemark have confirmed that has never happened.
Risk Assessment must be completed for all serviceable items before continuing.
3 types of work report paperwork – determined by the serviceable item
Additional check-boxes at end of job for "Revisit", "Follow Up" and "Burner safe for use".
Service Products list to show only what is on the engineer's Van, identified at login.
Service Products to be user-filtered by group.
Optional Job Photo functionality
Cancellation of a Service is allowed, requiring signatures.

Service PDA Process

All jobs will be assigned to an engineer, providing a Work-list or Load.

When an engineer logs on to a device (using their provided user name, password and vehicle), the assigned work-list will be downloaded onto the device, showing all the jobs in sequence on a Job List.

Selecting a job from the Job List will show the user the job report and customer contact details, allowing the user to contact the customer (through text or phone), or navigate to the customer's address.

The engineer can then choose to start the job, and when they arrive at the site, can being entering the details.

Note: All process up to and including the engineer starting and arriving at the job are generic and described in detail in the user guides, as referenced in the appendices.

The PDA will display the following tabs in order to process the service:

Job Details
Info
Products
Diagnosis

Job Details

This tab displays contact information and a summary of the instructions for the whole job (not the service items).

Job Details tab

A Cancel button will be added to the bottom of this screen. If for any reason the user wishes to cancel the service, they can click this button. This will prompt the user to enter the reason why the services are being cancelled (through a Picker) - these reasons are fully configurable, and is expected to contain a reason (Risk Assessment Failure). If cancelled this way, the user will be prompted to obtain a signature of the customer and for themselves.

Info

Info tab
Prework Checks pop-up

Info will show (in section 3):

Make
Model
S/No

All may potentially be pre-populated by the office staff, so proper fields against the Service.

The screen also would have navigation buttons left and right of the title (sections 1 and 2), to allow the user to switch between serviceable items. A label showing the record being processed (e.g. "1 or 6") would be shown, allowing the user to see how many there are. Switching between the serviceable items will change the displayed data on each of the tabs to the next service record. The same affect can be made by swiping left or right on the title label.

A Pre-Work Checks button will be shown in section 4 (for Risk Assessment) - this pops up the pre-work checks pop-up form:

All contents will be configured, entered like Vehicle Checks, through a scrolling frame. Save and Back buttons will be provided.

Warning: Some confirmation as to whether these checks have passed will be required from the user, on saving the checks, to ensure that they have been completed.

When complete and saved, user will be prompted, the title of the Pre-Work Checks button will be updated to show the status (Complete or Incomplete).

Note: These configurable Pre-Work Checks are not searchable, exportable or reportable, but can be displayable in the Admin client or on the Service Report.

Initially, the user will not be able to select any tab except Job Details and Info. Only when all pre-work checks are complete will the user be able to select any other tabs.

Products

Products tab

Products will be modified to:

pre-filter the list to show only products that are available to the engineer's vehicle (entered at log in)
show the Product Group selection above the Product selection, if configured.

If so, the user selects a product group, then the product list will be filtered to show only products that belong to this group. If none is selected, all products will be shown.

Diagnosis

Diagnosis tab
Post-work Checks pop-up

The Diagnosis tab is used for entry of Report of Visit.

Additional check-boxes will be added for "Revisit", "Follow Up" and "Burner safe for use". These will be prompted for if configured this way from the Admin system.

If Test Results are required, a Post-Work Checks button will appear here. This shows a post-work checks pop-up to enter the details, which are configurable ( Warning: different for each product group? What is Product Group used for?), entered like Vehicle Checks, through a scrolling frame.

Note: These configurable Post-Work Checks are not searchable, exportable or reportable, but can be displayable in the Admin client or on the Service Report.

Job Completion

When the user clicks the Done button, once all information entered (validated) on all the tabs, the engineer will be prompted for signature, as will the customer. These signatures would only be prompted once, and used on both the Service Report and Risk Assessment pages (if required) of the Service report, per serviceable item.

After Signatures have been entered, the user will have the opportunity to take a photo against the job (not the serviceable items).

Service Report

There is 1 Risk Assessment format and 3 Service Report formats.

These formats are not based on configuration against the Job Group (other than to choose Lanemark's format) - they are based on the serviceable product type, which should be entered against the service records.

Once risk assessment form and one service report will be printed per service record on the job, the format of the pages being based on the Product Group or Model. ( Warning: The details of what data items will be mapped where has not at this early stage been decided. This will be firmed up when NAV mapping of the data occurs.)

Note: With all these formats, "Sheet X of Y" is no longer necessary.

All service report formats will be presented in Landscape format.

All service report formats feature the sections containing the same data, detailed here:

Service Job number - Job code or Service ID.
Customer Name and Site Address - from the Customer/Job Address information
Customer Reference No - Any one of our existing references
Site Name - Warning: Unknown
Site Reference Number - Warning: Unknown
Customer Order No - Any one of our existing references (EPL_SO_NUMBER)
Site Contact Name - from the Customer/Job Address information
Site Contact Tel. Number - from the Customer/Job Address information
Site Contact Mobile Number - Warning: Unknown
Burner Model - Warning: Unknown. Entered by Admin rather than Engineer?
Burner Serial No - Warning: Unknown. Entered by Admin rather than Engineer?
Lanemark Service Item Number - Warning: Unknown. Entered by Admin rather than Engineer?
Application - Warning: Unknown. Entered by Engineer?
Location On Site - Warning: Unknown. Entered by Admin rather than Engineer?
Reason For Site Visit - Warning: Possibly Service Type? Job Instructions?
Office Instruction - Office Instructions
Details of Parts/Materials Used During Visit:
- Part Number - Service Product identified by user
- Description - Service Product Description
- Quantity - Quantity entered by user.
Engineer Visit Comments - Diagnosis Narrative entered by user
Revisit Required - New flag for entry against Service
Follow Up Required - New flag for entry against Service
Site Contact Name - Signatory entered by Engineer (defaulted from Customer Contact)
Site Contact Signature - Customer Signature
Service Engineer Name - User Name from Log-on
Service Engineer Signature - Engineer Signature.
Is Burner System Safe For Use - New flag for entry against Service.
Travel Time
- Day - Warning: Mon, Tue, etc?
- Date - Arrival Date
- Start Time - Arrival Time
- Finish Time - Actual End Time

Warning: As only the Test Results section varies, perhaps one consolidated format should be used fpr the electronic format?

The Test Results section of the various forms differ - this data will be taken from the configurable fields data against the different product groups, of which there will be 6:

TX
TRX
MTX
DB
FD
FDB

Each will be configurable with the post-work tests that are required.

Warning:

The only check that appears difficult to achieve would be on the TX format, where this appears to require a graphic. Could this be a DDL instead, with options Fully Open/Fully Closed/Set?

Warning:

"Comp. Air: Yes" on all formats - Should this be displayed on the device for the user to see? Should it be on the form instead?

Warning:

Test 8 on TX - label error - should this be "Air Pressure Switch Setting at Test Point"?

Warning:

Test 12 on DB - label error - should this be °C/Min/Max? or does this belong to Spray/Bake/Economy?

Warning:

DB range format - as this is different to the others, should this be consolidated into the same format?

Warning:

All formats - strike-through choices (e.g. Yes/No, 1ph/3ph) - would you just like the value chosen by the engineer to be displayed?

Service Report - TX/TRX/MTX

Service Report - DB

Service Report - FD/FDB

Engineer Site Risk Assessment

This form will be printed one per Serviceable item. This report will be printed in Portrait format, matching closely the following format:

The information on this report will be taken directly from the data entered by the user, and configured in the definable fields, other than the following:

By: - User Name Warning: Is this fixed text or part of what the engineer must enter?
Date: Job Actual Start Date Warning: Is this fixed text or part of what the engineer must enter?
Site - Warning: Unknown
Service Job - The Service ID Warning: This means that, if there were 6 items to be serviced, there would be 6 Risk Assessments, but they would all have the same (Job-level) service ID? What then is the Lanemark Service Item Number, and why wouldn't this be the item on the Service Risk Assessment form?
Date - Job Actual Start Date
Engineer Print - User Name
Engineer Sign - Engineer Signature.
Customer Print - EPL_SIGNATORY
Customer Sign - Customer Signature

The definable fields will not be manipulated in any other way than to format it for the report. Note that this means that, if the items are not present in the configuration for the report, this could break the layout of the report and make reports not work. This will affect only jobs completed after the configuration is changed.

The signatures on this screen will be taken from the standard Job signatures. If the Risk Assessment passes, only the Engineer signature will be populated.

Appendix A: Table of SCRs

SCR#	System	Area	Description	Estimate (Days)	Notes
1	eSERV	All	Significant UDF field modifications	5.75
2	eSERV	All	Multiple Serviceable Items Per Service Job	10.75
3	eSERV	PDA	New Info tab fields required	2.75
4	eSERV	PDA	Configurable Pre-work Checks (for Risk Assessment)	5.75
5	eSERV	PDA	Complete Prework checks before any other data entry	1.75
6	eSERV	PDA	Products filtered based on available Vehicle stock	1.50
7	eSERV	PDA	User-filterable Products based on Group/Model	2.50
8	eSERV	PDA	Configurable Postwork Checks (for Test Results)	3.25
9	eSERV	PDA	Display Status of Prework and Postwork checks on form	0.75
10	eSERV	PDA	Diagnosis to be modified for additional check fields	1.75
11	eSERV	PDA	Diagnosis narrative to become unrestricted field	0.75
12	eSERV	PDA	Allow Cancellation of Service Job	1.50
13	eSERV	Admin	New Service Report formats	5.00

Notes:

All ballpark costs in this document are provided as-is, are legally non-binding and subject to raising a formal change request with OBS Logistics.

Appendix B: Document References

B.1 References

Ref No	Document Title & ID	Version	Date
1	UG 291094 EPOD Admin User Guide	2.0	4/4/2012
2	UG 291097 EPOD Client User Guide	3.0	23/4/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

REQ 309371 Lanemark eSERV Requirements

Namespaces

More

Page actions

Contents

Introduction

Objective

Scope and Limitations

Client Requirements

Overview