How to create the Use Case Preventive maintenance ?

How to facilitate your preventive maintenance?

The use of paper forms can represent an issue for the use of the data collected during your preventive maintenance. The Ermeo tool allows you to organize these maintenance rounds and to be able to collect data with ease.

With the help of Ermeo, your field operator will then have all the necessary information at his disposal to carry out his rounds with complete peace of mind. He can also tell you about any anomalies encountered during these rounds.

What is a preventive maintenance round?

Preventive maintenance is carried out by a field operator according to criteria predetermined by a supervisor. Using the Ermeo forms, you will be able to define these different criteria.

The objective of preventive maintenance is to reduce the probability of failure of a good or the degradation of a service provided. It should also make it possible to avoid equipment failures during use.

By facilitating the display of information on the Ermeo application, but also by allowing your operator to feed back the information easily, you will be able to reduce the downtime of your assets, and to anticipate your corrective actions.

 

How to set up preventive maintenance on Ermeo?

In this article, we will present the method to use to set up preventive maintenance rounds on Ermeo.

Our example: Let us imagine an operator having to carry out the preventive maintenance round of all the pumps of a site.

Here are the steps that the operator will perform on Ermeo during his round:

1. He will first choose the site in which he is located.

2. He will then obtain information on this site and its round. Then, the list of pumps for the chosen site will be displayed.

 

 

 

3. For each of the pumps, it will carry out different inspections and will be able to collect data.

 

4. If the operator detects an anomaly on the pump, he can declare it. The anomaly will then be directly attached to the pump using the parent / child system.

 

 

List of steps to be implemented on Ermeo to carry out preventive maintenance rounds:

1. Create a Sites database making it possible to list all the sites on which operators can intervene

2. Create a Pumps database making it possible to list all the pumps. Each of the pumps will have for parent resource, the site in which it is located.

3. Create an anomalies database making it possible to list all the anomalies declared on the pumps. Each anomaly will have as its parent asset the pump on which the default is located.

4. Create the form allowing the operator to carry out his maintenance rounds.

4.1 In the form, be able to load the data concerning the intervention, the site and the site pumps.

4.2 Allow the operator the possibility of declaring anomalies on the inspected pumps.

 

Step 1: Have a Sites database to identify the sites on which operators can work

In this step, it is necessary to create a database making it possible to list all the sites. Each of the sites will be described by the following attributes:

• Customer Contact (Text)
• GPS coordinates (GPS coordinates)
• Customer email (Email)
• Customer Name (Text)
• Photo (Image)
• Site Address (Text)
• Agency Location (Text)
• Site Access instructions (Text)
• Site Contact (Action)
• Customer's phone number (Phone number)

 

• 

Ermeo gives you the possibility to create resources in bulk in a database using imports.

The import file used to create the sites in our example is attached to this article.

Your database will therefore be made up of different sites. Here is the end result in our case:

 

Step 2: Create a Pumps database

In this step, we will create a new database named "Pumps". This database will be described by the attributes:

• Construction site / Site (Text)
• GPS coordinates (GPS coordinates)
• Date of commissioning (Date)
• Serial Number (Number)
• Photo (Image)
• Pressure (Number)
• Power (Number)
• Status (Multiple Choice)
• Type (Multiple Choice)
• Parent Asset -> Each pump will have a parent asset. This asset will be the site where the pump is located.

 

The import file used to create the pumps in our example is attached.

Here is the result obtained:

 

 

 

Step 3: Create an Anomalies database

In this step, we will create a new database named "Anomalies". This database will be described by the attributes:

• Construction site / Site (Text)
• GPS coordinates (GPS coordinates)
• Corrective (Text)
• Creation date of the Anomaly (Date)
• Pick up date (Date)
• Degree of urgency (Multiple Choice)
• Description of the Anomaly (Long Text)
• Identified by (Text)
• Continued operation (Yes / No)
• Photo of the anomaly (Image)
• Status of the anomaly (Multiple Choices)
• Type of anomaly (Multiple Choices)

Each anomaly declared will therefore be described by a creation date, a description, a status, a photo and a criticality.

Here is the result obtained:

 

Step 4: Create the form allowing you to recall all the pumps on a site and report anomalies

As a reminder, the form created will allow the operator to perform the following steps:

 

1. In the field form, at the start of the intervention / before starting the intervention, the operator will select a resource who will be the main resource for the intervention. This resource will be the site of the intervention.

2. The operator will then obtain information on this site and its job. Then, the list of pumps for the chosen site will be displayed.

3. For each of the pumps, it will carry out different inspections and will be able to collect data.

4. If the operator detects an anomaly on the pump, he can declare it. The declared anomaly will automatically have as parent the pump containing the anomaly and will be stored in the "Anomalies" database.

Step 4.1 Creation of the form and loading of intervention information

1. Create a new form and name it "Preventive Maintenance Round"

2. Before starting the job from the application, the operator will choose the site in which he will intervene. This site will be present in the "Sites" database

3. In the studio, drag and drop a Section widget and name it "Information on the intervention"

4. Inside this widget, drag and drop a Text widget

4.1 In the default value of this Text widget, place the User first name and User last name tags

4.2 Drag and drop a Text widget and link to the Customer Name database attribute

4.3 Drag and drop a GPS Coordinates widget and link this widget to the Site Coordinates attribute

4.4 Drag and drop a Text box and link to the Contact Site attribute

4.5 Drag and drop a Telephone widget and link to the Telephone number attribute

Step 4.2 Loading the site pumps

1. Drag and drop an Automatic Selection widget out of the "Intervention Information" section

1.1 Name this widget "Checking the Pumps". In the widget settings, choose Parent is asset_name.

1.2 Order by Number then choose the attribute N ° of the pump

2. 1 In the Automatic Selection widget, drag and drop a Date widget. Link to the attribute Date of commissioning.

2.2 Then drag and drop a Number widget. Link it to the serial number attribute of the pump.

2.3 Then drag and drop a Multiple Choice widget. Link it to the Status or Type attribute of the pump

2.4 Then drag and drop a Yes / No widget. Link it to the attribute "Is the equipment clean"

3. Within the Automatic Selection widget, drag and drop a Creation widget. Select the "Anomalies" database in the parameters of the Creation widget.

4.In the Creation widget, drag and drop a Text widget. Name this widget "Description of the declared anomaly". Link this widget with the attribute "Description of the anomaly"

5 Within the Creation widget, drag and drop a Date widget. Name this widget "Today's date". Link this widget with the attribute "Date of creation of the anomaly"

5.1 Check the "Today's date" option. By default, today's date will be entered.

 

6. Still, within the Creation brick, drag and drop a Multiple Choice brick. Name this brick "Status of the anomaly".

6.1 Link this widget with the "Anomaly status" attribute.

7. Publish the form

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

9. Choose the site you want to work on. Check the intervention information then select your pumps.

10. Declare your anomalies then finish the intervention. The declared anomaly is now visible in your Anomalies database! The parent of the anomaly is the pump on which the anomaly is located.

It is also possible to customthe name of the anomalies created.

 

Conclusion: After creating anomalies, you can follow the processing of these anomalies (article link) and update them directly from the field using the anomaly tracking (article link).