Prepare asset data
A clear starting point before bringing data into CMMS.
Start with a usable list.
A good asset catalog helps users find the right equipment and understand its place in operations. Before entering data, agree on the priority equipment group, the focal point in charge, and the information needed for maintenance work.
Unified coding rules.
The code needs to be short enough to use but not confusing. Avoid including too much changeable information in the code, such as the current person in charge. Specify what to do when equipment is moved or replaced.
Unique
Each asset needs a separate code within the agreed scope.
Consistent
Same rules for shared managed data groups.
There is a clue
Determine who gets to create and test new code.
Collect enough information.
Start with name, team, position and person in charge. Add parameters, technical documents and relationships with the system when they serve actual work. No need to wait for a perfect set of documents to try the process.
Review before converting.
Find duplicate records, inconsistent names, and unknown locations. Compare a sample of data with users in the field. Keep a conversion table between old and new codes if you need to look up the history.
Try small, then expand.
Select an area, try to find the device and create a job from the prepared data. Note missing information and adjust rules before importing the entire category.
Select range
An area with a clear person in charge.
Check
Compare records with users.
Test run
Walk through a common maintenance situation.
Starting from your needs.
A specific situation is the starting point for a productive conversation.
Discuss your situation