Migrating Assets, Components, and Structures requires considering some differences between how information is organized in Consuman and in Consuman Evolution.
Before starting, it is recommended to consult:
These articles explain the main conceptual changes. The following section details only the criteria that must be considered during the migration.
To learn how to prepare and import the files, see the General Import Guide .
Assets
Assets registered in Consuman can be moved to Consuman Evolution while maintaining their core information and location within the structure.
Repeated names
In Consuman, assets can have the same description. In Consuman Evolution, the Name must be unique .
When there are repeated names, apply the following criteria:
- If the Key was not automatically generated by Consuman, combine the key with the asset description.
- If the Key was generated automatically, combine the description with the immediately higher location.
- If a repeated name persists, incorporate the necessary higher levels until a unique name is obtained.
- If duplicate records still exist and only the auto-generated key varies, migrate only one record.
Assets used as “General”
Assets with a description or type of General , commonly used to register requests that do not correspond to a specific asset, should be reviewed before migration.
In Consumer Evolution it is possible to register requests without selecting an asset, so it must be defined whether these registrations are still necessary.
Assets that match a location
There may also be equipment whose description matches a level of the Layout.
In these cases:
- If the asset has only one Part or no Parts, it can be migrated as a Location .
- If it has more than one Part in its structure, it is migrated as a Team , allowing the corresponding Component structure to be associated.
What information is being migrated?
- Clue
This corresponds to the asset key in Consumer.
- Name
This corresponds to the unique description of the asset.
- Guy
This corresponds to the type used to group the asset.
- Location
This refers only to the immediately higher location . It is not necessary to report the entire location tree in this field.
- Criticality
This corresponds to the priority used in Consumer.
- Cost center
This corresponds to the Cost Center associated with the asset.
- Accounting account
This corresponds to the accounting account associated with the asset.
Components
The parts used in Consuman are transferred as components in Consuman Evolution.
Which components should be migrated?
Before performing the migration, it is recommended to review the Parts currently in use.
Parts created solely to provide a minimal structure to the asset, such as those called General or similar, may no longer be necessary because Consuman Evolution allows planning tasks directly on the asset.
Repeated names
A component name must be unique.
If there are different Parts with the same description in Consuman, only one Component is migrated per name.
What information is being migrated?
- Name
This corresponds to the unique description of the Component.
- Guy
This corresponds to the Component Type and allows you to group them. This information is not required.
Structures
The structures also show differences between the two systems.
In Consuman, structures can be defined by Asset Type and specific structures for certain assets. In Consuman Evolution, structures are managed by Asset Type .
Which structures are being migrated?
Apply the following criteria:
- If a default structure is associated with an Asset Type , it is migrated to the corresponding type.
- If there is no default structure, but several assets of the same type use the same structure, it can be moved to the corresponding Asset Type .
- Components assigned only to some assets of the same type are not incorporated into the overall structure.