4.02 Asset Information Standards

In a long career implementing and improving SAP SCM business processes in Oil & Gas, Pipelines, Utilities and Transportation companies, the number one consistently observed problem is poorly identified MRO material masters. Material master identity consists of the item descriptions, the manufacturer and manufacturer part number fields and classification data that support material identification. This presentation is meant to raise the profile of the topic without going into detailed solutions. It is aimed at a general level to all practitioners that make use of maintenance or SCM business processes that use materials. The presentation is software agnostic. These challenges are found in shops running SAP, Oracle, JDE, Maximo…Topics: • Introduction (discussion applies to asset intensive industry and the MRO materials records used in their supporting business processes)  • Generalized view of the current state and how we arrived here. • Structured identification taxonomy – standards and why coherence in the structure is important. • Material master lifecycles are often not considered- beginning, middle, end. • Conclusions: This is not an insolvable problem or one that necessarily demands another $$$ system implementation. It exists only because it has been invisible  Originally Presented at AB Chapter Online Symposium (Part 1 of 7)  05/28/2020  as "The Story of My Journey With MRO Material Master Identities."  Presented MainTrain 2020  09/15/2020

Not all asset information is equal. Asset owning organizations benefit from having the right information at the right time. Asset knowledge primacy, an imperative to deliver operational excellence throughout the asset lifecycle. What is asset knowledge primacy? As the asset is developed and matures, stakeholders must calibrate data collection and exchange while curating fit-for-purpose asset information. Consistent thought-in-action leads to precision timing, relevance, and accuracy of information delivery. Successful asset knowledge capture is rarely accomplished efficiently or effectively. This doesn’t have to be so. In this presentation Chris Murphy will share an approach to provide asynchronous asset information delivery to best serve the life of the asset and support the organization to deliver value from the assets.

The asset hierarchy is often thought of as a way to organize assets so they’re easy to find in the CMMS. While a well-structured asset hierarchy does make work management easier, it’s much more than that. The asset hierarchy, when well conceived and utilized, will ensure the right reliability and costing data can be extracted from the CMMS. This enables more than just micro improvements in reliability involving a single asset; instead, it enables macro views of reliability and cost trends across the entire organization. Setting up an asset hierarchy to support these types of activities requires forethought and planning, but by following some guidelines, any organization can be set up for success. First, the asset hierarchy must have a standard that identifies how all assets will be categorized and described, and the specific data required for each asset class. This is vital, as not all assets warrant the collection of specific data, reducing the burden of the setting of the hierarchy. As assets are categorized, the failure code library can be developed and linked to the specific asset classes. This ensures only relevant failure codes are displayed for the assets, improving the adoption of failure data collection. With the asset hierarchy built and relevant failure data collected, trends can be established across asset classes, similar processes, etc. The trends enable reliability improvements to be implemented across larger swaths of assets, providing rapid improvements in reliability. This presentation will provide guidance in how to develop an effective asset hierarchy based on ISO 14224, how to implement the changes in the CMMS, and finally how to leverage the asset hierarchy to identify macro trends. Without a proper asset hierarchy, any organization will struggle to get meaningful and actionable data from their CMMS to drive reliability.

Previous presentations regarding the City of Toronto’s journey in Enterprise Work Management Solution deployment discussed the requirements gathering process and methodology for ensuring alignment within the service delivery group as well as across the municipality with other project partners. This presentation outlines the project’s current progress on moving from the program layer towards more specific divisional needs and the “readiness tasks,” which are required to ensure the meeting of critical milestones to realize deployment. Strategies focus on leveraging requirements documents for OCM and integration planning, with particular attention to engaging end users.

Metrics, best practices, more than 40 key elements to implement, challenges, and opportunities all combine to make a successful implementation difficult. Where do you start, and how do you know how to work on what matters? Once you understand how it’s all related, you can focus on the vital few to leverage the maximum ROI. This presentation will clarify the importance of culture and employee engagement, along with other key plant floor performance indicators that will be clarified with data. We'll look at the current state of R&M; what’s working and what's not; survival skills for the next decade; impacts of connected technologies (edge computing, big data, machine learning, AI, 3D printing, augmented reality); the importance of getting your data ready for what's coming next; and relationships between R&M and safety, people engagement, quality, throughput/uptime, and cost.