When a technology project still fails to create business value
A paradox is playing out across many industrial organizations. Digital transformation budgets are increasing. Enterprise Asset Management (EAM), Asset Performance Management (APM), IoT platforms, AI analytics and digital twins are being funded with the expectation of delivering a step change in operational performance. Dashboards look better, more data is available, reports are generated faster, and leadership meetings appear more “digital” than before.
Yet after some time, the same questions return. Downtime remains high. Maintenance cost does not decline as expected. Spare parts inventory continues to grow. Maintenance plans are still disrupted by urgent breakdowns. Operations teams still complain that system data does not reflect what is actually happening in the field. Leadership still lacks the trusted information needed to decide whether to repair, replace, improve or reinvest.
The familiar reaction is to look for another technology: a more powerful software platform, a better dashboard, a smarter AI model or a wider set of sensors. However, practical experience in asset management programs suggests that the root cause is often not a lack of technology. The real issue is that technology is deployed before the organization has matured its strategy, data, processes and operating capabilities.
In other words, companies do not fail because they choose the wrong software. They fail when they expect software to replace management thinking.
The common mistake: starting with “which software should we buy?”
In many projects, the first question is often: Which EAM platform should we select? How should we implement APM? Should we launch predictive maintenance? Can AI predict equipment failures? These questions are valid, but when they appear too early, they can pull an organization into a “technology first” mindset.
An EAM system can manage hundreds of thousands of asset records. An APM platform can aggregate data from multiple sources. AI can detect abnormal patterns in operating data. But no technology can independently answer more fundamental questions: What exactly is the business trying to optimize? Which assets create the highest risk? What level of availability is required? Which risks are acceptable? Is the current data trustworthy enough to support decisions?
If these questions remain unanswered, software becomes only a data-entry environment. Dashboards become a polished visual layer on top of an immature management system. AI becomes an analytical engine trained on unstructured or unreliable data.
A serious industrial digital transformation program should begin with the business problem, not the name of the software. Technology is an execution tool. Technology is not the strategy.
Maintenance is an activity; asset management is a management capability
A frequent misunderstanding is to treat maintenance management and asset management as the same thing. In practice, maintenance is an important part of asset management, but it does not represent the entire discipline.
Maintenance management focuses on maintenance planning, work order execution, repair, inspection, spare parts coordination and maintenance resource control. These activities are essential for keeping equipment operational.
Asset management is much broader. It considers the full asset lifecycle: investment concept, design, procurement, installation, operation, maintenance, improvement, replacement and disposal. The objective of asset management is not simply to “get the equipment running again.” It is to ensure that assets deliver the best possible value to the organization within an acceptable level of cost and risk.
An asset can be maintained on schedule and still be suboptimal if the original design is not fit for purpose. A production line can have high PM compliance and still experience downtime if the maintenance strategy is not based on failure modes and asset criticality. A plant can reduce short-term maintenance cost by cutting activities, while increasing the long-term probability of a major failure.
Mature asset management always balances performance, cost and risk. This is the fundamental difference between “doing maintenance” and “managing assets.”
When data is abundant but insight is scarce
One of the biggest pain points in industrial organizations is not the absence of data. It is the existence of large volumes of data that are not good enough to support decision-making.
It is common to see a CMMS or EAM system containing tens of thousands of work orders where the description field says only “fixed,” “completed,” “OK,” “replace part” or “machine running.” From a procedural standpoint, the job may be closed. From a reliability engineering perspective, the organization has lost an opportunity to learn from the event.
If the failure mode is not clearly recorded, if the failure cause is mixed with symptoms, if the failure mechanism is not distinguished, and if operating conditions at the time of the event are not captured, historical data will not be strong enough to support RCA, FMEA, RCM, bad actor analysis or predictive analytics.
MTBF is a good example. A report can calculate MTBF automatically. But if the definition of failure is inconsistent, if the start and end time of downtime are unclear, if the asset hierarchy is incorrect, or if an operating event is mistakenly recorded as an equipment failure, MTBF becomes a number that looks precise but cannot be trusted.
Bad data does not merely create bad reports. It drives bad decisions: the wrong equipment is prioritized, investment is directed to the wrong areas, maintenance strategies are optimized in the wrong way, and in some cases the organization develops a false sense of control.
ISO 55001 and ISO 14224: foundations, not slogans
In this context, ISO 55001 and ISO 14224 should be viewed as practical foundations for organizations seeking to improve their asset management capability.
ISO 55001 is the requirements standard for an asset management system. Its value is not in creating more paperwork or administrative procedures. Its value lies in management discipline: aligning asset management objectives with organizational objectives; defining leadership and governance; managing risk; planning; measuring performance; driving continual improvement; and supporting decision-making across the asset lifecycle.
ISO 14224 focuses on a very specific but critical foundation: the collection and exchange of reliability and maintenance data for equipment according to a structured approach, particularly in the petroleum, petrochemical and natural gas industries. It helps organizations establish a common data language around equipment hierarchy, equipment class, failure mode, failure mechanism, failure cause, failure consequence, maintenance event, work history and data quality.
If ISO 55001 answers the question “how should the organization manage assets to create value?”, ISO 14224 answers the question “what data should be collected and standardized to support those decisions?”
One is a management framework. The other is a technical data foundation. One provides strategic direction. The other provides the data discipline required to execute that strategy. When connected properly, these two standards create a meaningful foundation for EAM, APM, predictive maintenance and industrial AI.
AI cannot fix bad data
AI is creating significant expectations in maintenance and industrial operations. That expectation is not unreasonable. AI can support anomaly detection, cause suggestion, failure trend analysis, work prioritization and faster access to maintenance knowledge.
But AI is not a miracle. AI does not replace reliability engineering. AI cannot understand asset context correctly if the input data does not reflect operational reality. AI cannot convert a work order that says “fixed” into a complete technical lesson about failure mode, root cause, operating condition and preventive action.
If the asset register is not standardized, if the asset hierarchy is wrong, if failure codes are inconsistent, if sensor data is not calibrated, and if maintenance history lacks operational context, the AI model will learn from a distorted picture. In that case, the problem is not a weak algorithm. The problem is that the organization has not prepared a sufficiently reliable data foundation for AI to create trustworthy recommendations.
This is a point many organizations need to address honestly: before asking whether AI can predict failures, they should ask whether the current data is good enough for a reliability engineer to analyze with confidence. If people cannot trust the data, AI will also struggle to create trust.
Business Before Technology: a more practical approach
Business Before Technology does not mean undervaluing technology. On the contrary, it helps technology be deployed in the right place, at the right time and for the right purpose.
A practical approach should begin with very concrete questions. What is the plant’s business objective: higher production, lower downtime, optimized OPEX, improved safety, reduced spare parts inventory or extended asset life? Which assets are critical? Which failure modes create the highest risk? Does the current maintenance strategy distinguish between critical and non-critical equipment? Is work order data good enough to support RCA and RCM? Do operations, maintenance, engineering, supply chain and HSE share the same data language?
Once these questions are answered, the organization can decide what should come first: cleaning master data, standardizing the asset hierarchy, designing failure coding, assessing asset criticality, improving the work order process, defining the right KPIs, or deploying APM, PdM or AI for a selected group of critical assets.
The best roadmap is not necessarily the most technologically complex roadmap. The best roadmap is the one that creates the clearest value with the lowest implementation risk.
A consulting perspective: start with organizational capability
A successful EAM or APM project should not be treated as a pure IT project. It is a program that changes how an organization operates, records data, collaborates across functions and makes asset-related decisions.
If Operations is not involved, the data will lack operating context. If Maintenance focuses only on closing work orders, the system will contain a large quantity of low-quality records. If Reliability is not involved in failure code design and data analysis, the system will struggle to generate technical insight. If Supply Chain is disconnected from the maintenance strategy, spare parts inventory will be difficult to optimize. If HSE is not involved in criticality assessment, safety and environmental risks may be underestimated.
Therefore, consulting capability in asset management is not limited to configuring software. It is the ability to connect business strategy, operations, reliability engineering, data governance, maintenance processes, risk management and technology into an executable roadmap.
This is the approach Avenue should bring into client conversations: do not start with a demo, do not start with a dashboard, and do not start with AI. Start with the business problem, the operating reality, the maturity of data and the asset strategy. When the problem is clear, technology becomes a tool in the proper sense of the word.
Self-assessment questions for industrial organizations
Before investing further in EAM, APM, IoT or AI, an organization can ask itself five practical questions.
First, do we know which assets are truly critical to production, safety, environment and financial performance?
Second, is our current work order data detailed enough to analyze failure modes, root causes and failure trends?
Third, are MTBF, MTTR, availability, PM compliance and backlog calculated from data that can be trusted?
Fourth, is our maintenance strategy based on criticality and risk, or are we applying the same logic to too many assets?
Fifth, if we implemented AI today, would the current data be strong enough for the model to generate recommendations that engineers trust?
If most answers are unclear, the organization should not rush to conclude that it needs more software. The more urgent priority may be to build a stronger foundation for asset management and data governance.
Conclusion: technology creates value only when built on the right management foundation
In the digital era, competitive advantage does not come from owning more software, more dashboards or more sensors. The real advantage comes from the ability to turn data into the right decisions, at the right time, in a way that creates sustainable business value.
EAM can digitize processes. APM can connect asset data. IoT can provide operating signals. AI can support analysis and prediction. But all of these technologies create value only when they are placed on a strong asset management foundation: clear objectives, reliable data, defined processes, clear roles and an organization prepared to change.
Companies do not fail because they choose the wrong software. They fail when they expect software to replace strategy, data and management capability.
Business Before Technology is not a slogan. It is a practical principle: start with the business problem, understand the assets and risks, standardize the data, strengthen the processes, and then choose the right technology to scale the organization’s capability.
An excellent asset management system does not begin with buying software. It begins with the right strategy, the right data, the right process and the right people.
