Asset Maintenance Data, a crucial component in the industry, is used to collect and exchange reliability and maintenance data for equipment. Understanding the significance of an Asset Management Data Standard (AMDS) is key, as it provides guidance on the data required for analysis (MTBF, MTTR, bad actor, etc.) and benchmarking against industry peers.
Asset Management Data governance is essential to any successful asset management data strategy. AMDS should be part of a company's overall data framework. Ideally, executives and other representatives of an organization's business operations, as well as IT and data management teams, should all be involved in AMDS governance efforts.
A monster challenge in today's world is the enormous amount of data collected, modified, and stored daily. An Asset Management Data Standard provides guidelines on what data needs to be collected. However, a structured approach is required to understand how the data will be collected, consumed, analyzed, and sustained to drive decisions. The intent is to provide a simplified process to drive decision-making. The six key areas are:
An Inconsistent asset hierarchy makes it difficult to understand the location of the physical asset in the facility as well as its relationship to other equipment within the process. ISO14224 provides guidelines for what the asset hierarchy should look like. Impacts from a consistent hierarchy will provide potential impacts as mentioned below:
Develop a standardized list of minimum equipment characteristics required for each specific asset class. This will ensure that:
For example - centrifugal pumps within the rotating equipment class have the highest maintenance repair costs.
ISO14224 provides excellent guidelines on the categories of maintenance work and related activities. By enforcing a process and monitoring it on a frequent basis, maintenance work coming through the CMMS can be categorized. This categorization of maintenance work provides the foundation of what data will be analyzed from a reliability perspective. Some key definitions include breakdown repairs, failures, operator basic care, etc. This is essential because:
4. Define maintainable item codes, failure codes, and cause codes
Defining a set of maintainable item codes, failure codes, and causes codes in a structured hierarchy will provide end users with a small set of relevant codes. For e.g., Centrifugal Pump, Seal, Leaking, and installation. By having this information over a period of time, reliability improvement efforts can be targeted, and maintenance cost optimization can be achieved. Defining these codes in a methodical way will:
As part of the implementation, a set of business processes need to be defined to understand how information and data flow, how the maintenance work will be identified, planned, scheduled, executed, and closed out, as well as, how reliability will consume the data, analyze it, validate it and provide recommendations. I must emphasize that Maintenance and Reliability (and, for that matter, operations) are joined at the hip. One cannot function without the other.
"Many organizations are just beginning to take a fresh look at master data from WHAT-to-do to HOW-to-do perspective. Nexus Global can help you get started on your journey of HOW-to-do with our master data services and Data Optimizer software, which are designed to address these needs and more across industries like oil and gas, power generation and distribution, automotive, pharmaceutical, metals, food, beverage, ports, manufacturing; and more." Say goodbye to data discrepancies/silos and hello to a unified, accurate view of your critical business information. Partner with us to elevate your master data to the next level!"