--- title: "From Asset Hierarchies to Work Orders: Making SAP EAM Deliver Value" slug: making-sap-eam-deliver-value url: /topics/articles/making-sap-eam-deliver-value/index.md publishedAt: "2026-10-28T14:42:26" updatedAt: "2026-10-28T14:42:26" excerpt: "At the SAP for Asset & Service Management Conference in Seville on October 27, 2026, a roundtable on ISO 14224 quickly became a discussion about something much bigger than a reliability-data standard: whether our EAM systems are actually designed to support the business processes they are supposed to enable. The participants came from asset management, […]" authors: - Drew Troyer --- # From Asset Hierarchies to Work Orders: Making SAP EAM Deliver Value By [Drew Troyer](/authors/drewtroyer/index.md) At the SAP for Asset & Service Management Conference in Seville on October 27, 2026, a roundtable on ISO 14224 quickly became a discussion about something much bigger than a reliability-data standard: whether our EAM systems are actually designed to support the business processes they are supposed to enable. The participants came from asset management, SAP implementation, ports and logistics, maintenance, enterprise solutions and financial management. Their experiences were different, but their frustrations were remarkably consistent. Companies have spent considerable money implementing and customizing enterprise systems, yet too often struggle to identify what they own, understand how it fails, plan the right intervention, obtain the right parts or calculate the consequences of their decisions. The solution is not to implement ISO 14224 to the letter and declare victory. My central point in Seville was simpler: the standard offers two particularly valuable things - guidance for constructing a sensible equipment hierarchy and a disciplined way to organize information around failure modes. Those foundations give an EAM system a fighting chance of supporting a good business process. They do not create that process for us. ## What ISO 14224 Can—and Cannot—Do for SAP EAM ISO 14224 originated in the petroleum, petrochemical and natural gas industries. It provides a framework for collecting and exchanging three categories of information: equipment data, failure data and maintenance data. The vocabulary and organizing logic are useful well beyond those industries. A port, mine, power station or logistics operation still has motors, bearings, valves, pumps, gearboxes and other familiar asset classes. The physics of failure do not change when an asset crosses an industry boundary. That does not mean every organization should reproduce every category, code or level of detail. A standard designed to support comparable reliability data is not a universal template for SAP configuration. It does not prescribe a complete work-management process, a materials strategy, asset-accounting rules or a learning-management system. Nor does it tell us precisely which maintenance tasks to perform. Those decisions require engineering, commercial and organizational judgment. Use ISO 14224 in spirit and with discipline. Preserve consistent definitions and useful equipment boundaries. Tailor the depth of data collection to the decisions the business needs to make. If contractual or formal conformance is required, satisfy the applicable requirements. Otherwise, do not confuse a thick catalog of coded fields with a functioning asset-management system. ## Build Asset Hierarchies Around Equipment Function Several participants described the consequences of structuring SAP primarily around geography, buildings, rooms or financial reporting. Each of those perspectives may be legitimate, but none is sufficient by itself for managing physical assets. A geographic location tells us where something sits. It does not necessarily tell us what function it performs, which components are maintainable, how failures aggregate across a fleet or what history must remain with an asset when it moves or is replaced. Consider a port conveyor. A practical decomposition might run from terminal to conveyor system to equipment unit, drive assembly and maintainable components. We may need to report results by terminal and revenue stream, schedule work against a system or functional location, retain serial-specific history for a gearbox, and evaluate recurring bearing failures across multiple conveyors. Trying to force all four questions into one rigid hierarchy is a recipe for confusion. The technical structure needs to support functional and equipment relationships; complementary reporting attributes can support geography, accounting, asset ownership and the port business model. > Trying to force all four questions into one rigid hierarchy is a recipe for confusion. SAP already distinguishes functional locations from individual equipment records, and it can retain installation and removal history. A sensible model uses those capabilities deliberately. The goal is neither maximum hierarchy depth nor minimum data entry. It is the level of granularity needed to make decisions, identify parts, retain meaningful history and execute the work. One participant raised a particularly important point about ownership: if operations, maintenance and finance do not agree on what an asset is and how it should be represented, no amount of clever querying will solve the underlying problem. Enterprise comparability begins with shared definitions. ## Connect Failure Modes to Maintenance Actions A hierarchy tells us what we are managing. A failure-mode framework tells us what can go wrong. Those are necessary beginnings, not the endpoint. The business value emerges when we use that knowledge to choose actions that prevent, predict, detect or correct the failure. Take a mechanical seal on a process pump. “Pump problem” is not much of a diagnosis. Loss of containment at the seal is a useful failure description. Understanding whether the mechanism involves contamination, inadequate flush, dry running or some other condition changes what we inspect and what we prescribe. The action might be to verify the seal-support system, obtain additional condition evidence, correct an operating condition or carry out a planned replacement. The same logic applies to motor insulation, valve actuation, couplings and gearbox lubrication. ISO 14224 can help standardize what we call the equipment and the failure. FMEA, RCM, engineering standards, operating experience and sound judgment help us select the strategy. SAP EAM should then support the workflow - from observation and descriptive, prescriptive notification through prioritization, planning, scheduling, execution, quality verification and learning. > The business value emerges when we use that knowledge to choose actions that prevent, predict, detect or correct the failure. Not every observation justifies an immediate work order. Some findings warrant further assessment. Some permit an authorized fix-as-found action, provided the action is recorded. Others require an engineered corrective job plan. What matters is that the response is deliberate, traceable and proportionate to the risk. ## Integrate SAP EAM, Materials Management, and Finance An SAP practitioner in the roundtable described a familiar divide between Plant Maintenance and Materials Management specialists. One group configures maintenance processes; another manages material masters, bills of material, purchasing and inventory. Each can deliver a technically functioning module while the planners and craftspeople are left connecting the dots through phone calls, emails and spreadsheets. A failure-mode-driven job plan is not executable if the equipment BOM is unreliable, the replacement part exists under several material numbers, or the required item cannot be located when work is scheduled. The material master, equipment BOM, inventory and procurement rules are not peripheral to asset reliability. They are part of the execution system. With consistent identification and demand information, MRP and spares strategies have a credible basis for improving both readiness and working capital. Finance is equally important, but its requirements are not identical to those of maintenance. Replacing an engine or major subassembly may have accounting and valuation consequences, and country-specific requirements may differ. The correct approach is to reconcile the technical identity of the asset with financial mappings and capitalization rules - not distort the engineering hierarchy into an accounting tree. The same traceability matters for statutory inspections of pressure systems and other regulated equipment. ISO 14224 does not establish the accounting or statutory rules; it can help provide the technical consistency on which trustworthy reporting and compliance processes depend. Figure 1 illustrates the complementary systems that make this possible. ![Figure 1. ISO 14224 and the complementary SAP EAM ecosystem.](https://cms.reliamag.com/wp-content/uploads/2026/10/figure1.png) *Figure 1. ISO 14224 and the complementary SAP EAM ecosystem. The standard provides a foundation for equipment, failure and maintenance information; surrounding systems enable work management, materials, finance, analytics, skills and learning. Connections are conceptual, not mandated interfaces.* ## Clean Core Starts With Clean Decisions The discussion naturally turned to SAP S/4HANA and clean core. I support the principle: use standard capabilities where they fit, avoid unnecessary changes to the core, and govern extensions rather than accumulating them indiscriminately. Customization is sometimes warranted; customization without a clear business requirement becomes technical debt. Too many organizations use software changes to compensate for inconsistent process definitions, poor master data or unclear accountability. Then they add niche applications and shadow spreadsheets to bridge the gaps. Each local workaround may make sense in isolation. Collectively, they erode enterprise visibility. If leadership cannot get a trustworthy count of a major equipment fleet without reconciling multiple systems, the problem is not a shortage of dashboards. > If leadership cannot get a trustworthy count of a major equipment fleet without reconciling multiple systems, the problem is not a shortage of dashboards. A strong cross-functional Center of Excellence can preserve the common taxonomy, process rules, interfaces and data-quality expectations. But a CoE without decision authority will become another advisory committee. Operations, technical leadership, supply chain, finance and IT must own a common design and protect it through upgrades, acquisitions and organizational changes. ## Standard Job Plans Turn Strategy Into Repeatable Work A carefully structured hierarchy and failure taxonomy should ultimately lead to executable work. Standard job plans capture the task sequence, safety and isolation requirements, tools, materials, labor, inspection criteria and evidence of quality. They convert engineering knowledge into consistent field performance rather than leaving each planner to reinvent the job. For mature maintenance organizations, I favor ambitious planning-coverage targets: standard plans for essentially all recurring time- or usage-based maintenance, and for the substantial majority of repeatable corrective work. A practical benchmark is 100% for the former and at least 80% for the latter. Those are management targets I advocate, not obligations imposed by ISO 14224, and they must be adjusted to the work mix and risk. The benefits are particularly compelling for greenfield facilities and multi-site operators. Rather than building hundreds of plans from a blank page, start with a governed library for common equipment classes, then adapt to local operating context and statutory requirements. The plan should define what good execution looks like and how we will know it was achieved. This is also why skills and learning management belong in the SAP EAM ecosystem. A technically correct job plan does not guarantee competent execution. Role qualifications, learning paths, demonstrations of proficiency and refresher training help close the loop. Those systems are complementary to ISO 14224, not prescribed by it. ## Judge SAP EAM by Business Outcomes, Not Compliance Scores The strongest business cases begin with a business problem, not an implementation scorecard. A recurring failure that destroys throughput, raises safety exposure or consumes working capital provides a far more persuasive starting point than a target for populating master-data fields. Standardized failure information allows us to quantify patterns, compare sites, evaluate interventions and learn whether the strategy actually works. It does not, by itself, prove a return on investment. The roundtable emphasized joint ownership from operations, technology or engineering, and finance - in many organizations the COO, CTO and CFO. They must agree on the outcomes, the process, the decisions, the accountabilities and the measures. Useful indicators include maintenance-strategy compliance and effectiveness, quality of failure-mode capture, ready-to-schedule work, parts availability, repeat failures, execution rework, maintenance cost and MRO working capital. Each metric should support a decision, not merely fill a dashboard. > The strongest business cases begin with a business problem, not an implementation scorecard. My Data-to-Dollars logic begins with value and works backward through the actions, decisions, insights, information and data needed to create it. Only then should we ask which SAP objects, fields, integrations and controls are necessary. That is the opposite of installing a configuration and hoping the business will find a way to use it. ## A Fighting Chance Requires More Than Good Data Two questions from Seville are worth taking back to every SAP EAM design team. First, does the hierarchy make it possible to identify, compare and manage the equipment and components that matter? Second, does the failure-mode model lead to the right preventive, condition-based, investigative and corrective actions - with the materials, skills, job plans and feedback needed to execute them? If the answer to either question is no, the system may still process notifications, orders and invoices. But it is unlikely to deliver its full value as an asset-management system. ISO 14224 is not the be-all and end-all. It is valuable guidance that, properly interpreted, can make the design more coherent and the information more useful. Clean core and cross-functional integration can help preserve that coherence at scale. Neither replaces business-process design. The business process must determine the system, not the other way around. Form must follow function. **ABOUT THE ROUNDTABLE**  Based on notes from the SAP EAM conference discussion in Seville, October 27, 2026. Participant contributions are paraphrased and anonymized; technical examples are illustrative. **TECHNICAL REFERENCES ** ISO 14224:2016 ([iso.org/standard/64076.html](http://iso.org/standard/64076.html)); SAP Help Portal - Equipment, Bills of Material, Maintenance Task Lists and Clean Core.