{"id":46123,"date":"2026-07-24T16:30:54","date_gmt":"2026-07-24T11:00:54","guid":{"rendered":"https:\/\/www.verdantis.com\/?p=46123"},"modified":"2026-07-24T19:31:48","modified_gmt":"2026-07-24T14:01:48","slug":"manufacturing-asset-management","status":"publish","type":"post","link":"https:\/\/www.verdantis.com\/fr\/manufacturing-asset-management\/","title":{"rendered":"Manufacturing Asset Management: The Discipline Your EAM Software Executes"},"content":{"rendered":"
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

A production line can carry six figures of spare capacity in one bay and none at all in the next, and most asset registers do not know the difference. Asset management in manufacturing<\/strong> is the discipline that decides where that gap matters and by how much.<\/p>\n

EAM and CMMS software is simply the system that carries the decision out afterward. This piece treats asset management as a practice with its own hierarchy, performance mechanics, and failure modes, distinct from the tools used to run it.<\/p>\n

It is grounded in production equipment, the domain where the discipline is highest stakes and most measurable, and it stays there deliberately.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Why Asset Management in Manufacturing Keeps Getting Reduced to a Software Purchase<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Most guides to this topic collapse two different things into one. Asset management<\/strong> is the strategic practice of getting the most value out of physical assets across their working life. EAM and CMMS software<\/strong> is the system that records, schedules, and tracks the work that practice generates.<\/p>\n

The conflation is understandable. The software is visible every day. The discipline behind it, the classification logic, the maintenance strategy choices, the capital planning horizon, mostly lives in decisions that never touch a screen.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Asset management (discipline)<\/div>
Champ d'application<\/span>Which assets matter, how much, and why<\/div>
Ownership<\/span>Reliability, engineering, and plant leadership<\/div>
Horizon temporel<\/span>Asset lifecycle: years to decades<\/div>
Output<\/span>Criticality tiers, maintenance strategy, capital plans<\/div><\/div>
EAM \/ CMMS software<\/div>
Champ d'application<\/span>Recording and scheduling the work the practice generates<\/div>
Ownership<\/span>Maintenance planners and IT\/EAM administrators<\/div>
Horizon temporel<\/span>Work cycle: days to weeks<\/div>
Output<\/span>Work orders, notifications, spares consumption records<\/div><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Neither one works without the other. But a plant can own excellent EAM software and still manage its assets badly, because the classification decisions the software depends on were never made with rigor upstream. That upstream layer is what this article is actually about.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The software layer itself is not one thing either. It splits into three overlapping categories, worth naming once before moving past them.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Term<\/th>What it actually covers<\/th><\/tr>
GMAO<\/strong><\/td>Computerized Maintenance Management System. Schedules and records work orders. The narrowest of the three.<\/td><\/tr>
EAM<\/strong><\/td>Enterprise Asset Management. Everything a CMMS does, plus spares inventory, warranties, capital planning, and the full asset lifecycle.<\/td><\/tr>
APM<\/strong><\/td>Asset Performance Management. Adds predictive analytics and condition-based failure prediction on top of EAM data. The newest and most data-dependent of the three.<\/td><\/tr><\/table>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

This article stays one layer above all three, at the discipline that decides what any of them should be tracking in the first place. Feature-level evaluation of CMMS, EAM, and APM platforms is covered separately, linked at the end of this piece.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

What This Article Covers, and What It Deliberately Leaves Out<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

"Asset" means different things depending on who is using the word. Naming the boundary up front avoids the vague, everything and nothing treatment that dominates search results for this term.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Asset sense<\/th>Scope note<\/th>Couverture<\/th><\/tr>
Production equipment<\/strong><\/td>Machinery, process equipment, rotating assets on the plant floor<\/td>Covered here<\/span><\/td><\/tr>
Facilities \/ infrastructure<\/strong><\/td>Buildings, utilities, site services supporting production<\/td>Acknowledged, not developed<\/span><\/td><\/tr>
IT \/ technology assets<\/strong><\/td>Hardware, software licenses, digital infrastructure<\/td>Out of scope<\/span><\/td><\/tr>
Fixed \/ accounting assets<\/strong><\/td>Capitalization, depreciation, book value treatment<\/td>Deferred elsewhere<\/span><\/td><\/tr><\/table>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Production equipment is the focus throughout, because it is where the strategic, tactical, and execution layers connect most directly to spares, downtime, and cost. The accounting sense of "asset" is a real, separate discipline, covered on the [[NEEDS INPUT: internal URL for Fixed Asset Management Software page]] page rather than here.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Within production equipment specifically, the physical asset types this discipline governs span several distinct categories, each with its own failure behavior and maintenance strategy.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Cat\u00e9gorie<\/th>Exemples<\/th><\/tr>
Rotating equipment<\/td>Pumps, motors, compressors, turbines, fans<\/td><\/tr>
Static equipment<\/td>Tanks, pressure vessels, heat exchangers, piping<\/td><\/tr>
Material handling<\/td>Conveyors, forklifts, cranes, robotic arms<\/td><\/tr>
Process equipment<\/td>Reactors, boilers, extruders, mixers, furnaces<\/td><\/tr>
Instrumentation and electrical<\/td>Sensors, PLCs, switchgear, motor control centers<\/td><\/tr><\/table>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

The Strategic, Tactical, and Execution Hierarchy Behind Every Asset Decision<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

ISO 55000, the international standard for asset management, structures the discipline into tiers without naming them quite this way. In practice, most manufacturers run three layers, whether they have written them down or not.<\/p>\n

Strategic tier.<\/strong> Asset management policy, criticality classification, and the capital planning horizon live here. This is where a plant decides which equipment can least afford to fail.<\/p>\n

Tactical tier.<\/strong> Maintenance strategy selection sits here: the mix of preventive, predictive, and reactive maintenance, and the broader reliability planning that supports it.<\/p>\n

Execution tier.<\/strong> Day to day work order execution, spares consumption, and condition monitoring happen here. It is the tier every EAM system is built to run.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Strategic tier<\/div>
Criticality classification, capital planning<\/div><\/td><\/tr>
↓<\/td><\/tr>
Tactical tier<\/div>
Maintenance strategy mix, reliability planning<\/div><\/td><\/tr>
↓<\/td><\/tr>
Execution tier<\/div>
Work orders, spares consumption, condition data<\/div><\/td><\/tr><\/table>
↑ Feedback loop: execution-level failure data should reclassify strategic-tier criticality, and rarely does in practice<\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The mechanism that connects this article to the rest of the maintenance cluster sits in that feedback loop. Criticality classification decided at the strategic tier drives the maintenance strategy chosen at the tactical tier, which in turn drives how spares are stocked and reordered at the execution tier, a policy question covered in full in MRO inventory management.<\/p>\n

Very few plants route the arrow back upward: execution-level failure history rarely reclassifies strategic-tier criticality in practice, a gap covered further on.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

How OEE Turns Asset Management Practice Into a Single Measurable Number<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Overall Equipment Effectiveness is the manufacturing-specific lens that makes asset management practice visible in a metric, rather than just a policy document.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
OEE = Availability × Performance × Quality<\/div>
Availability: planned production time actually used, net of unplanned downtime. Performance: actual output rate vs. ideal rate. Quality: good units vs. total units produced.<\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Asset management practice shows up directly inside each component, not just conceptually. Poor spares availability lengthens unplanned downtime, which lowers Availability. Inadequate maintenance on aging or poorly classified assets increases scrap and rework, which lowers Quality.<\/p>\n

The 85% "world class" OEE benchmark traces back to Seiichi Nakajima's Total Productive Maintenance framework, built from three component targets multiplied together: roughly 90% availability, 95% performance, and 99.9% quality. Most discrete manufacturers operate well below it.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Composite OEE by performance band<\/div>
85%<\/span><\/div>
World-class<\/div>
Nakajima \/ TPM benchmark<\/div><\/td>
60%<\/span><\/div>
Typique<\/div>
Common discrete-manufacturing range<\/div><\/td>
<40%<\/span><\/div>
Poor<\/div>
Unaddressed downtime and quality loss<\/div><\/td><\/tr><\/table><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Composite OEE hides which lever actually moved it. The chart below breaks the same causal chain down by component, and it is a conceptual illustration rather than a benchmark figure.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
How asset management quality moves each OEE component (illustrative pattern, not a cited statistic)<\/div>
\u00c9lev\u00e9<\/span><\/div>
Availability<\/div>
Most exposed to spares stockouts<\/div><\/td>
Moderate<\/span><\/div>
Performance<\/div>
Degraded assets run below rated speed<\/div><\/td>
\u00c9lev\u00e9<\/span><\/div>
Quality<\/div>
Poor condition drives scrap and rework<\/div><\/td><\/tr><\/table><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Nakajima's TPM framework breaks the three OEE components down further into six specific loss categories, which is where corrective action actually starts.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Loss category<\/th>OEE component affected<\/th><\/tr>
Breakdowns<\/td>Availability<\/td><\/tr>
Setup and adjustment<\/td>Availability<\/td><\/tr>
Small stops<\/td>Performance<\/td><\/tr>
Reduced speed<\/td>Performance<\/td><\/tr>
Startup rejects<\/td>Quality<\/td><\/tr>
Production rejects<\/td>Quality<\/td><\/tr><\/table>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The asset register and criticality gaps described elsewhere in this article show up specifically as breakdowns and startup rejects, the two categories most directly tied to how well spares and condition data are managed.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

OEE measures effectiveness in the moment. Mean Time Between Failures and Mean Time To Repair measure reliability and maintainability over a longer window, and both depend on the same notification and downtime-code data that feeds the asset register.<\/p><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
MTBF = Total uptime ÷ Number of failures<\/div>
MTTR = Total repair time ÷ Number of repairs<\/div>
MTBF rising and MTTR falling together are the clearest sign that criticality classification and spares strategy are actually working.<\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\tSee what your own OEE and criticality data actually says<\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Run this hierarchy against your own functional location structure instead of a generic template.<\/p><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\n\t\t\t\n\t\t\t\n\n\t\t\t\t\t\t\t\n\t\t\t\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t