Why import interventions ?
As a supervisor, you may have to define a multitude of interventions for your operators.
The import of interventions is useful in the case of several interventions planning.
So what is this functionality ?
Using Ermeo, you can plan a lot of interventions quickly.
The import of interventions is done using an Excel file.
Excel Template of Interventions Import
You will find the import template for your interventions attached to this article.
The following columns must be present in the import file.
|Column||Presence of the value||Further information|
|code||Mandatory if intervention update / Optional if intervention creation||How do I get existing codes?
Export the interventions that you want to update to retrieve their code (intervention tab, select by checking the interventions to update, click on action, click on export, click on download) the 1st column of the XLS table contains the codes of your interventions
|name||Mandatory||The title of your intervention|
|status||Mandatory||Type "todo" for a planned intervention|
|planned_start_date||Mandatory||Accepted format: DD/MM/YYYY hh:mm|
|planned_end_date||Optional||Accepted format: DD/MM/YYYY hh:mm|
|planned_duration||Optional||Must be empty|
|asset||Optional||Enter the code of the resource on which you want the intervention to be carried out. To obtain this code, you can export your assets|
|document||Mandatory||Enter the code of the document with which you want the intervention to be carried out. To obtain this code, you can export your documents|
|users||Mandatory||Enter the username of the user to whom you want to assign the intervention. The username is the login with which the user logs in. If there are several users, separate the usernames with ";"|
You can also specify intervention attributes. These attributes are defined by yourself and therefore allow you to enter data for each intervention.
In practice, how to import interventions ?
Context : A supervisor wants to plan several interventions using imports.
First of all, to have an Excel file template, it is better to plan a first intervention manually. Then, you must export this intervention to obtain the excel template
1. Plan an intervention manually.
2. Return to the interventions tab, and select the intervention planned and then export it.
3. Fill in the different rows and columns of your Excel file. The columns should remain in the order stated earlier in this article. Column names should not be changed.
4. After the users column, you can add the columns corresponding to your intervention attributes.
5. Once your file is configured, return to the platform in the "Interventions" tab. Click into "Import"
6. Choose your file.
7. You can view the different attributes of your file and the correspondence with the existing attributes on the Ermeo platform.
The message "column 'code' empty" appears in order to warn you that you are going to create new interventions.
8. Click on Next. You can check the status of the import. Your interventions are imported into the platform.
Warning: If your file contains errors, an error file will be generated by Ermeo. Within this file, are the interventions that could not be imported. The error source columns appear in red on the file. You can also hover your mouse over the error source column to see the error message in detail.
To go further
You can therefore import new interventions or update existing interventions.
The difference is in the code column of your import file :
- For the creation of new interventions, the code column must remain empty.
- For updating existing interventions, the code column will contain the codes of the interventions that you want to modify.
During an import (equipment or interventions), using an Excel file, the import is made from the top of the file to the bottom of the file. First, line 1 of the file is imported, then line 2 is imported, then line 3 etc.
The error file is generated only if your import file contains errors. You can make your changes to this file, then use it directly as a new import file. Interventions will not be created in double