Defining Equipment in Predictive Maintenance: A Practical Guide with ISO 14224 and Power-MI

CEO, Power-MI
eventAugust 28, 2025

In industrial maintenance, one of the most critical yet overlooked questions is defining an industrial asset. This definition directly impacts how organizations plan maintenance, monitor equipment, manage reliability programs, and even how PdM software licenses are calculated.

The international standard ISO 14224 provides a well-structured taxonomy for industrial equipment and reliability data collection. At its core, the standard organizes assets into hierarchical levels, culminating at level 6: the equipment unit. Power-MI adopts this level as the practical definition of an industrial asset. By focusing on level 6, we align our platform with global best practices, ensuring that reporting, monitoring, and management are consistent and comparable across plants, industries, and geographies.

Why is this delimitation essential? Because predictive maintenance is built on clarity. If engineers, reliability managers, and software tools operate with inconsistent definitions of what an asset is, confusion spreads into inspection reports, KPIs, and investment decisions. Conversely, when assets are defined objectively and consistently, data integrity improves, reliability analysis becomes meaningful, and licensing remains transparent and fair. This White Paper addresses precisely that challenge: providing a practical guide to defining industrial assets within the ISO 14224 framework.

Concept of Equipment

Defining equipment consistently is essential for predictive maintenance and reliability management. ISO 14224 provides a clear taxonomy that organizes the industrial environment into hierarchical levels, from the industry as a whole down to individual parts. Within this structure, Power-MI aligns with Level 6: Equipment Unit as the practical definition of equipment.

In the hierarchy, the upper levels (Company, Plant, Section) establish organizational and physical context, while lower levels (Subunit, Component, Part) describe subdivisions within equipment. The equipment unit (Level 6) is the pivot point: it represents the physical item to which condition monitoring and predictive maintenance activities are applied, and the level at which inspection reports are generated.

ISO 14224 hierarchy diagram mapped to Power-MI levels (illustrative).

The diagram above illustrates how Power-MI translates ISO 14224 taxonomy into a practical hierarchy:

  • Company → Plant → Section → Sub-Section → Equipment → Report

In Power-MI, we added the Sub-Section level because many clients require an extra layer to locate and organize equipment. This additional level provides flexibility for complex plants where sections alone are not sufficient. In the following sections, we will explore practical cases where this subdivision becomes essential.

This mapping highlights how organizational structure connects to technical structure. For example:

  • Plant/Unit (Level 4) corresponds to the physical facility.
  • Section/System (Level 5) groups related equipment.
  • Equipment Unit (Level 6) is the key reference point in Power-MI, the element to which predictive maintenance reports are assigned.

PdM perspective — the report defines the boundary. In predictive maintenance and condition monitoring, equipment is the object to which the inspection or monitoring report is issued. In practice, the report boundary sets the equipment boundary. For a motor–pump set (an electric motor coupled to a centrifugal pump), the common question is whether the motor and the pump are two pieces of equipment or one. The decisive test is: when you perform vibration, thermography, or visual inspections, do you issue one report for the motor and another for the pump, or a single report for the motor–pump set? In most plants, a single report is produced; therefore, the equipment is the motor–pump set—not the components separately.

By adopting Level 6 as “equipment,” Power-MI ensures that users define and manage units consistently, avoiding confusion between higher-level groupings and lower-level components. This clarity supports data integrity, reliability analysis, and transparent software licensing.

Delimitation Principles

Clear delimitation of equipment is critical to ensure consistent reporting, accurate condition monitoring, and transparent software licensing. While ISO 14224 provides a structured hierarchy, in practice each organization must decide where to draw the boundary between one equipment unit and another. The following principles provide practical guidance:

  • Report-driven definition: Define equipment based on the scope of the monitoring or inspection report. If a single report covers a motor–pump set, the equipment is the set; if reports are separate, then each component is considered equipment.
  • Functional independence: Treat items as separate equipment if they can operate or be maintained independently (e.g., a compressor and its motor driver when monitored separately).
  • Criticality alignment: Delimit equipment according to its impact on operations. For example, two parallel pumps in a critical process line should each be defined as distinct equipment units for reliability tracking.
  • Consistency with taxonomy: Always align with ISO 14224 Level 6 for the base definition, while allowing practical flexibility with Sub-Section or other local structuring.
  • Avoid over-subdivision: Do not classify subunits, components, or parts (Levels 7–9) as standalone equipment unless they are monitored and reported independently.
  • Case-by-case analysis: Recognize there is no universal rule; equipment delimitation should be validated with maintenance engineers familiar with plant reporting practices.
  • Balance simplicity and detail: Strive for a level of granularity that supports actionable reporting without creating unnecessary complexity or inflated equipment counts.
  • Standardize across the organization: Apply the same delimitation rules across all plants and sections to ensure data comparability and consistent licensing.

Practical Examples

Motor–Pump Assembly

One of the most common questions in predictive maintenance is how to define a motor–pump assembly: should the motor and the pump be considered two separate pieces of equipment, or one? This example illustrates how reporting practices guide the definition of equipment in Power-MI.

From a predictive maintenance perspective, equipment is the entity for which a condition monitoring or inspection report is issued. The report boundary defines the equipment boundary. In other words, the practical test is simple: when you conduct vibration analysis, thermography, or visual inspections on a motor–pump set, do you prepare one report for the motor and another for the pump, or do you produce a single report for the motor–pump assembly?

In most plants, maintenance engineers prepare a single report covering the motor and pump together, since they are mechanically coupled and function as one operating unit. In such cases, the equipment is defined as the motor–pump assembly, not as two separate items. This aligns with ISO 14224 at Level 6 (equipment unit), where the monitored object of reliability data and maintenance reporting is established.

Motor–pump assembly treated as one equipment unit based on reporting practice.

This approach emphasizes clarity and consistency: equipment is defined not only by its physical boundaries, but also by how it is monitored, reported, and managed. For Power-MI users, adopting the “report-driven definition” ensures alignment with real maintenance practices and avoids artificial inflation of equipment counts.

Conveyor

Conveyors illustrate the challenge of defining equipment when multiple elements form part of a single operational line. A conveyor may include motors, gearboxes, pulleys, and rollers, often duplicated along its length. Each of these components can have distinct vibration measurement points, raising questions about whether they should be classified as individual pieces of equipment or as a single unit.

Conveyor line with multiple drives and rollers; equipment boundaries depend on reporting scope.

In Power-MI, the guiding principle remains: define equipment according to reporting practice. If the maintenance team issues a single condition monitoring report for the entire conveyor line, then the conveyor is considered one equipment unit. However, if separate reports are produced for each drive motor, gearbox, or pulley, then each monitored element can be defined as independent equipment.

This approach allows flexibility without losing consistency. Power-MI’s Sub-Section level can be used to organize large systems like conveyors into logical groups, while still keeping a clear definition of what constitutes equipment for reporting and licensing purposes. By mapping reports directly to equipment, reliability engineers can manage complex machinery without ambiguity and ensure comparability across different plants and sections.

Paper Machine Winder

A winder is a large and complex piece of machinery used to process and wind paper into rolls. Its main visible components are the roller, the motor and gearbox, and the supporting bearings. The common question is whether the motor and roller should be considered separate equipment. In practice, since vibration, thermography, and bearing monitoring are usually reported as one, the winder is treated as a single equipment unit that includes the roller, bearings, transmission system, motor, and gearbox.

Paper machine winder—roller, bearings, motor, gearbox monitored as one unit.

Cooling Tower

Cooling towers often raise the question of whether the tower should be considered one equipment unit or a subsystem with its internal components (fan, motor, gearbox, water pumps). In Power-MI, the prevailing practice is to define the cooling tower as a subsystem, and then treat each of its critical rotating elements—such as the fan motor or gear drive—as separate equipment. This approach supports precise condition monitoring, as these rotating components are monitored and reported independently, while the tower structure itself remains part of the subsystem.

Cooling tower with independently monitored fan drive; treated as subsystem with distinct equipment.

Boiler

For boilers, confusion sometimes arises over whether to treat the boiler as one equipment unit or as a subsystem with its own components (burners, pumps, heat exchangers, valves). The standard practice is to define the boiler itself as an equipment unit. Although its components are monitored with different techniques (temperature, pressure, vibration, ultrasonic thickness), they all contribute to the operational reliability of the boiler as a single entity. By considering the boiler as equipment, reliability engineers maintain clarity in reporting and avoid unnecessary subdivision.

Industrial boiler considered a single equipment unit; multiple monitored components.

Power Substation

Substations are often recorded as a single equipment item, but they consist of multiple critical assets such as transformers, oil tanks, heat exchangers, and pumps. The practical guideline is to register the substation as a subsystem and define each transformer or critical rotating element as separate equipment, especially when independent reports are generated for them.

Power substation treated as a subsystem, with transformers and other critical components.

Electrical Transmission Lines

Transmission lines present a unique challenge. If defined as a single equipment unit covering long distances, reporting becomes imprecise—failures could be anywhere along the line, including multiple towers, insulators, or conductors. The best practice is to divide lines into manageable segments, either by kilometers or by operational regions. This ensures that reports specify failure locations clearly, while avoiding excessive fragmentation into very short segments.

Segmented electrical transmission lines to improve fault localization in reports.

Electrical Switchboards (Panels)

Confusion with switchboards arises when they contain multiple circuits or assemblies. The guiding criterion is whether a circuit is functionally tied to a specific mechanical or electrical equipment item. In most cases, the best practice is to treat the switchboard as a standalone equipment unit. When multiple switchboards are grouped physically but serve different functions, they should be divided according to their physical and functional boundaries, ensuring clarity in monitoring and reporting.

Electrical switchboard treated as standalone equipment; divided by physical and functional boundaries.

STS Crane (Ship-to-Shore Crane)

A ship-to-shore (STS) crane is a large and complex structure typically found in port terminals. It should be defined as a system or subsystem, since it contains multiple equipment items that are monitored and reported independently. Within an STS crane, common equipment units include the hoisting motor and gearbox, trolley drive motors, boom hoist, slewing mechanism, hydraulic pumps, and electrical switchgear. Each of these items can be treated as distinct equipment in Power-MI, while the crane as a whole is best considered a subsystem to maintain clarity.

Ship-to-shore crane with multiple independently monitored units; treated as subsystem.

Dump Truck

Similar to cranes, dump trucks combine multiple critical components that can be monitored separately. While the dump truck as a whole can be seen as a subsystem, its individual equipment units include the diesel engine, transmission system, hydraulic lifting system, cooling system, alternator, and wheel motors (in electric-drive trucks). Reliability engineers often issue separate reports for these subsystems, particularly the engine and hydraulics. This makes the dump truck best treated as a subsystem grouping, with condition monitoring tied to its individual equipment.

Mining dump truck treated as subsystem; engine, hydraulics, driveline reported independently.

Piping Systems

Piping networks are among the most challenging cases for equipment delimitation. For long, linear stretches—such as water pipelines or oil transportation lines—the recommended practice is to divide them into segments, similar to electrical transmission lines. This segmentation ensures that monitoring reports can pinpoint failure locations without including excessively long distances under a single equipment entry. Inside industrial plants, however, pipes often converge and interconnect. In such cases, they are better defined by plant area or sector. Another important decision is whether to include accessories such as valves, flow meters, and regulators within the same equipment boundary. The choice depends on their criticality: if an accessory significantly affects the process or requires separate condition monitoring, it should be registered as standalone equipment. Otherwise, it can remain part of the piping system definition.

Plant piping segmented by area; critical accessories registered separately when needed.

Challenges in Equipment Delimitation

Defining equipment consistently is rarely straightforward. Engineers and reliability professionals often face complex situations where the boundary between one equipment unit and another is blurred. Some of the most common challenges include:

  • Boundary decisions: Large or interconnected systems (e.g., piping, conveyors, power substations) raise the question of whether they should be defined as one equipment item or subdivided into smaller units. Overly broad boundaries reduce clarity in reporting, while excessive subdivision inflates equipment counts.
  • Handling assemblies: For assemblies such as motor–pump sets or gear-driven fans, it is not always obvious whether each component should be defined separately or treated as a single equipment unit. The decision often depends on reporting practices, but inconsistency among teams creates confusion.
  • Twin or redundant components: Equipment that operates in parallel, such as twin pumps or compressors, presents challenges in delimitation. Defining them as one unit obscures individual performance data, while splitting them into two units may complicate reporting if they share instrumentation.
  • Subsystem versus equipment confusion: Large structures like cranes, cooling towers, or dump trucks often contain multiple equipment items within them. Some organizations define the whole structure as a single equipment item, while others treat it as a subsystem containing several distinct equipment units. The lack of standardization can cause misalignment across plants.
  • Data collection inconsistencies: Inconsistent definitions across teams or plants lead to fragmented datasets. Reliability analysis, failure statistics, and benchmarking become less reliable if equipment boundaries are not defined in the same way.

Overall, the greatest challenge is balancing precision with practicality. Without clear and consistent delimitation rules, predictive maintenance programs risk confusion, unreliable data, and inefficient use of software resources.

Best Practices & Recommendations

To overcome the challenges of equipment delimitation, organizations should adopt clear, practical, and standardized approaches. The following best practices provide a roadmap:

  • Use the report-driven definition: Define equipment according to the scope of the inspection or monitoring report. This ensures consistency with actual maintenance practice.
  • Adopt ISO 14224 Level 6 as the baseline: Always anchor equipment definitions to the equipment unit level, which aligns with international standards and ensures comparability across industries.
  • Leverage Power-MI’s Sub-Section functionality: Use the Sub-Section level to provide extra flexibility where plants require finer localization of equipment. This avoids forcing artificial definitions while maintaining clarity in reporting.
  • Avoid over-subdivision: Only create separate equipment units when they are independently monitored or reported. This prevents unnecessary complexity and inflated equipment counts.
  • Document taxonomies properly: Maintain clear and organized documentation of how equipment is defined. This ensures continuity across teams and facilitates onboarding of new personnel.
  • Involve maintenance engineers in delimitation: Engage the professionals who prepare and review reports, as they best understand the practical boundaries of equipment. Their insights prevent theoretical definitions from clashing with real-world practices.
  • Standardize across the organization: Apply the same delimitation criteria across plants and business units. Consistency allows for reliable benchmarking, cross-site analytics, and fair licensing.

By following these practices, companies can align equipment definitions with reporting realities, reduce confusion, and maximize the value of predictive maintenance programs.

Conclusion

Defining equipment is not an abstract exercise—it is the foundation for reliability engineering, predictive maintenance, and effective use of Power-MI. Clear definitions ensure that reports are accurate, monitoring is consistent, and reliability data is meaningful. They also guarantee transparency in software licensing, allowing companies to scale their predictive maintenance initiatives fairly and sustainably.

In predictive maintenance, clarity is power. By adopting consistent equipment delimitation, organizations enable accurate monitoring, trustworthy data, and confident decision-making. For Power-MI users, this discipline ensures that every report aligns with global standards and that every license reflects true operational needs. In short, precise definitions of equipment are the key to reliable operations and fair, scalable digital transformation in maintenance.

Publications

What is Power-MI?

Power-MI is a cloud based solution that allows you to design & manage your condition-based maintenance plan integrating all techniques into one platform. Easy reporting, automatic work orders and CMMS integration.

Read more

Subscribe to the Power-MI Blog

rss_feedSubscribe