DHTMLX Prototype Screenschots

8/2/2019 DHTMLX Prototype Screenschots

1/14

Maintenance inspection processing using a

DHTMLX mobile application prototype

screenschots:

Introduction

This document shows screen shots of an inspection processing prototype system which was

developed using DHTMLX Touch mobile development framework in a SAP PM environment using an

IIS web server as middleware between the mobile client and SAP back-end.

Login:

Login using personnel number

Define selection dates to pull data from the server and Download


2/14

Select data for inspection processing


3/14

Show Inspection location(s) on the map, for the inspection as a whole and individually for inspection

points. Protected substation inspections will not need mapping for inspection points.


4/14

Ensure that the work crew is defined (this may change, dependent on assistants available). This is

done under Time worked. Note that Pool indicates an unassigned resource. The system will

perform middleware validation for duplicate inclusion of pool resources as team members on more

than one time segment.


5/14

At arrival on site, start the stopwatch. If an inspection is not selected the stopwatch will not start.


6/14

Close the Time worked window and proceed with the physical inspection . Click on the magnifying

glass next to the inspection to open up inspection points. For each inspection, inspection

characteristics will be results recorded and technical feedback given.


7/14


8/14

Proceed with results recording as follows:

Clicking OK and saving will highlight a line with a green tick mark and skip to the next line. When

clicking Not OK the user will have to provide long text to give a reason for a defect:


9/14


10/14

After saving a defect, the line will be marked with a red cross and defect text will be shown in the

right hand column. Quantitative inspection characteristics will be automatically validated based on


11/14

the LTL and UTL inspection limits.

When all inspection points have been processed, a condition rating has to be supplied for the

inspection point as follows:


12/14

Prior to completing the inspection and stopping the stopwatch, a progress report or validation

should be performed to check if mandatory inspection characteristics were left unfilled. A report or

validation should not stop the inspector from completing the inspection because master data

inaccuracies may result in mandatory inspection characteristics not being filled. It is however crucial

that these inspection characteristics and master data deficiencies are highlighted in the middleware

server. It should also be possible for an inspector to add inspection points which may be found in the

field, labelled or not, and capture results against these inspection points.


13/14

After an inspector is satisfied that an inspection is complete, the inspection is completed by stopping

the stopwatch and saving the time worked on the inspection as follows:


14/14

After all inspections have been closed, inspection data can be loaded to middleware. Middleware to

be used for more than shuttling data form and to SAP core tables, including the following:

Keep inspections in a logical packet posting to SAP updates individual inspection lots but SAP does

not store a logical definition of the inspection (i.e. group of inspection points/lots and time

confirmed for these inspection points as a group).

Not all inspection points captured on the mobile device will have inspection lots in SAP. In some

cases the master may have been missing which means the inspection lot would not have beenavailable prior to inspection. These inspection points and associated result will not be posted to SAP

but will be available in middleware to ensure that master data fixes are applied . Conversely,

inspection lot not captured because of erroneous master data will remain as incomplete in SAP. By

looking at SAP only, it will not be clear if an inspection, with all its inspection lots were skipped or if

individual lot were left as incomplete because of master data errors. Middleware reporting will

have to highlight incompletes because of master data errors.

Documents

DHTMLX Prototype Screenschots