In Consuman Evolution, the Preventives, Events and Checklists used in Consuman are moved within the concept of Programs .
Before starting, it is recommended to consult Programs: unification of scheduled maintenance .
During the migration, it is necessary to review mainly the existing names and the way the current planning is configured.
To learn how to prepare and import the files, see the General Import Guide .
Repeated names
Before performing the migration, it must be verified that there are no identical descriptions between Preventives, Events and Checklist.
If records with the same name exist, two alternatives can be applied:
- Migrate them as separate programs , adding a reference to the name that allows them to be differentiated, for example:
- PREVENTIVE
- EVENT
- CHECKLIST
- Migrate them as a single program , using the necessary triggers according to the corresponding configuration.
The alternative to be used must be defined during the migration according to the way in which each planning method is currently used.
Program Activators
In Consumer Evolution, program planning is defined by triggers .
During migration, the maintenance types currently configured in Consuman must be linked to the corresponding trigger in Consuman Evolution.
Preventive measures by frequency
Preventives configured by frequency require special consideration.
In Consuman Evolution, this type of planning uses a Base Read to calculate the next run, instead of directly using the Base Date of the Preventative.
To determine the baseline reading during migration:
- The reading corresponding to the base date configured in Consuman is being sought.
- If there is no reading recorded on that exact date, the immediately preceding reading is used.
- If the asset has no reading history, or the Base Date is earlier than the first recorded reading, Base Reading = 0 is used.
In order for the Preventative Maintenance by Frequency to correctly maintain its planning, it may be necessary to also migrate the corresponding Reading history.