During the migration, assets that currently record measurements or readings require prior configuration of Meters in Consumer Evolution.
Before starting, it is recommended to check @ Readings and measurements are now managed from a single place.
It is also possible to transfer the necessary Read history to preserve certain schedules and replicate the currently used Request Categories.
To learn how to prepare and import the files, see the General Import Guide .
Meters
For assets that record measurement values in Consuman, whether through Work Order tasks, IoT or Readings, it is necessary to create the corresponding Meters in Consuman Evolution beforehand.
Meters are created manually before importing readings.
What should be taken into account when creating Meters?
To define them, consider the following criteria:
- Use a single Unit of Measurement or Frequency Code .
- Enable the Accumulated option for Readings and leave it disabled for measurement values.
- Maintain unique values for lower, middle, and upper limits when they correspond to a Unit of Measurement.
- The same meter can be used for multiple asset types.
- The Meter Name must be unique .
Readings
Migrating the history of readings is especially important when there are frequency-based preventative maintenance , as Consuman Evolution uses those readings to calculate the next scheduling run.
In these cases, the necessary history must be migrated from the oldest base date used by the Preventative measures.
Before importing Readings, the corresponding Meters must be created and associated with the assets.
What information is being migrated?
- Asset
This corresponds to the name of the team to which the reading belongs.
- Meter
This corresponds to the meter previously configured for the asset.
- Date
This corresponds to the date on which the reading was recorded.
- Worth
This corresponds to the accumulated value recorded on that date.
Restart
Indicate Yes when the reading corresponds to an odometer reset.
Application categories
The Request Categories used in Consuman can be replicated in Consuman Evolution, maintaining their names and existing hierarchical relationships.
Unlike other entities, Request Categories are not migrated via an Excel file . Their configuration must be done manually in Consumer Evolution.