How to create the Use Case Anomalies Follow up ?

How to facilitate the management of anomalies?

The use of paper forms represents an obstacle for the management of anomalies. The Ermeo tool allows you to easily identify these anomalies but also to follow them until they are resolved. Ermeo thus automates the formatting of these anomalies to facilitate the visualization and monitoring of data on BI tools. Our tool will allow you to manage these anomalies in databases while allowing your operators to create or modify these same anomalies from the field.

What is Anomaly Management?

An anomaly is a singularity most often attached to a resource using a parent-child relationship.

This anomaly may be an equipment defect, a broken tool or a comment indicating a failure or any form of non-compliance.

The objective is to be able to quickly declare these anomalies but also to follow them over time in order to decide on corrective actions.

How to set up anomaly monitoring on Ermeo?

In this article, we will only see the method to allow the management and the follow-up of these anomalies.

The main steps for creating anomalies were as follows:

1. Have an existing database listing one or more types of assets.

2. Create an anomalies database to list all the anomalies declared

3. Create a form allowing you to recall anomalies from the field in order to modify them.

Contextualization: Below, we will see the steps to follow and resolve anomalies for an operator doing building maintenance.

The buildings inspected contain fire extinguishers, fire alarm boxes and BAES (Autonomous Safety Lighting Unit).

Anomalies have already been declared previously on this asset. Maintenance operators will have to correct these anomalies and report the corrections made to their administrators.

To do this, the steps are as follows:

1. Modify the Anomalies database in order to add a "Corrective" Status

2. Create a form to recall existing anomalies on the application, depending on the resource chosen at the start of the intervention

Step 1: Modify the Anomalies database in order to add a Corrective status

Previously, we had created an Anomalies database. An anomaly was then described by:

• A date of creation of the Anomaly (Date)
• A description of the Anomaly (Long Text)
• An Anomaly status (Multiple Choices)
• A photo of the anomaly (Photo)
• Criticality (Multiple Choices)

All these data are therefore attributes.

We are going to add a Corrective status (of type Text). If the operator in the field resolves the anomaly, he can then describe the corrective action. The description of this patch will then be retrieved from the Anomalies database.

Here are the sub-steps:

1. Click on the Platform's Databases menu and enter your "Anomalies" Database (this database may be called otherwise depending on your use case)

2. Click on the "Attributes" tab then on "Create a new attribute"

3. Enter the word "Fix" in the Name box. Choose the type "Text" and activate the option "Long Text".

4. Validate the creation by clicking on "Create attribute".

Step 2: Create a form allowing you to recall existing anomalies

In this step, we will create a form allowing an operator to recall anomalies from the field.

At the start of the intervention, the operator will choose a resource on which there could be potential anomalies. It is called the main resource of the intervention.

It is recalled that the anomalies are in fact child assets of an inspected assets. In our case, by choosing a resource at the start of the asset (also called the main asset), the operator will then call all the child resources of this main resource. It will then call all the anomalies of this main asset.

In the form you can choose what can be updated or not, by the operator in the field. In the event that the person dealing with the anomaly is different from the person reporting the anomaly, you can condition the display of certain bricks, in order to display only the essentials during your interventions.

Here are all the sub-steps in order to create the form allowing to recall the existing sub-anomalies:

1. Click on the Documents tab and click on New Document

2. Name your document "Anomalies follow-up" and choose the document type "Form"

3. Click on "Open in the studio" then drag and drop an Automatic Selection widget. Name this widget "List of existing anomalies".

4.1 Still in the brick parameters, click on Or paste the tag and enter the following tag ##asset_name##. Thus, only the anomalies of the resource chosen at the start of the intervention will be displayed.

4.2 In the widget parameters, choose the Anomalies value in the "Database" filter. You can choose another database name if your Anomalies database is called otherwise.

5. Within the Automatic Selection widget, drag and drop a Text widget. Name it "Description of the anomaly" and link this brick with the attribute "Description of the anomaly"

6. Within the Automatic Selection widget, drag and drop a Photo widget. Name it "Photo of the anomaly" and link this widget with the attribute "Photo of the anomaly"

7. Within the Automatic Selection widget, drag and drop a Text widget. Name it "Corrective action made in order to resolve the anomaly" and link this brick with the "Corrective" attribute created previously.

8. Still within the Automatic Selection widget, drag and drop a Multiple Choice widget. Name it "Anomaly Status" and link this widget with the "Anomaly Status" attribute.

9. Exit the form then publish it.

10. You can launch the form from the webapp or from the mobile application.

11. Choose the asset on which you have anomalies. Take note of the anomaly and fill in the corrective action, as well as the new status of the anomaly.

12. End the intervention and return to the web platform. The resolved anomaly is now visible with its fix in your Anomalies database!

Conclusion: You can see in more detail how to manage these anomalies for an operator on his mobile application.