Percentage of equipment coverage by CMMS/EAM from bikola's blog

In the process of implementing CMMS/EAM, many companies take the short cut and introduce only critical equipment into the system. This shortening of the path leaves the equipment of the second and third echelon without attention. Instead, the maintenance costs of equipment in this equipment tier are loaded into long-term and permanent orders, thus making the information practically unusable for data analysis, equipment troubleshooting, or equipment life cycle cost estimation. After all, all equipment, even if it is at the system level, must be entered into the CMMS/EAM.

This indicator is calculated by dividing the total number of equipment items loaded into the CMMS/EAM by the total number of equipment items identified in the plant or facility. While some equipment systems are structured at the component level, others (especially non-critical items) may be left unstructured at the system level. This choice in relation to a piece of equipment makes the data collection process too detailed. The alternative of not collecting all the data is unacceptable.
Advantages
This metric is a must for any company seeking to ensure complete service data accuracy and the ability to locate all costs and information related to the repair history of the respective equipment. This indicator is a valuable tool for evaluating equipment coverage.
Flaws
The weakness of this indicator is that it sometimes forces maintenance organizations to try to balance the numbers. Sometimes, an organization may open long-term or standing work orders as a way of hiding discrepancies in equipment accounting systems. Such action should not be taken. The real solution to the problem is to allocate sufficient time and resources during the implementation of the CMMS/EAM to populate the data. If we want the data in the CMMS/EAM to be accurate, then all items of equipment must be in the CMMS/EAM, even if they are not system-level critical items.

I am sure that a wider range of services of this company https://www.makini.io/ will interest you