11.2 CMMS/EAM Systems & Industrial Information Technology

11.2 CMMS/EAM and Industrial Information Technology

Quick Answer: Information technology creates reliability value only when asset identity, work history, condition data, and decisions remain traceable. Build trustworthy master data first, then integrate systems through controlled interfaces and security zones.

CMMS and EAM purpose

A computerized maintenance management system (CMMS) supports work orders, preventive tasks, labor, materials, scheduling, failure history, and reporting. Enterprise asset management (EAM) platforms often extend that scope into asset lifecycle, procurement, contracts, finance, and portfolio governance. Product labels overlap, so assess required functions and data flows rather than the name alone.

Core records include:

• functional locations and equipment;
• asset criticality and ownership;
• bills of material and interchangeable spares;
• preventive and predictive task plans;
• work requests, work orders, job plans, and schedules;
• failure, cause, mechanism, and remedy codes;
• labor, material, contractor, and downtime transactions;
• meter, condition, inspection, and test results;
• drawings, procedures, certificates, and revision references.

Each field needs a definition, owner, validation rule, and lifecycle status. Free text adds useful context but cannot replace structured fields needed for analysis.

ISO 14224 hierarchy

ISO 14224 addresses collection and exchange of reliability and maintenance data for equipment in petroleum, petrochemical, and natural-gas industries. Its nine taxonomy levels are:

1. Industry
2. Business category
3. Installation
4. Plant or unit
5. Section or system
6. Equipment unit
7. Subunit
8. Component or maintainable item
9. Part

The first five levels describe use and location; the last four describe equipment subdivision. The standard can inform other sectors, but users should state that adaptation and define their own data rules rather than claim universal conformance outside the document's scope.

A practical plant hierarchy might be enterprise, site, area, system, functional location, equipment, assembly, component, and part. Its labels need not mimic ISO terminology if the business has another controlled model, but parent-child relationships must support work assignment, cost rollup, and reliability analysis.

Functional location versus serialized equipment

A functional location represents the place where a required function occurs, such as Cooling Water / Train A / Pump Position 2. A serialized equipment record represents the physical pump installed there.

When pumps are exchanged:

1. remove the failed serialized pump from the functional location;
2. retain its operating and repair history;
3. route it to the shop or another status;
4. install and associate the replacement serial number;
5. record commissioning checks and current meter position;
6. preserve location history and equipment history separately.

Without that distinction, failure counts follow the tag rather than the physical item, warranty history becomes unreliable, and repairs cannot be compared across a rotating pool.

Failure and work data

A useful failure record distinguishes:

• failure mode: how the required function was lost or degraded;
• failure mechanism: the physical process, such as fatigue, wear, corrosion, or electrical insulation breakdown;
• cause: the underlying design, operating, maintenance, material, or human factor;
• remedy: the action taken to restore or prevent recurrence.

Do not force a final cause at work initiation. The requester can capture symptom and operating context; technicians can update condition and mode; an analysis can establish cause after evidence exists.

A completed work order should show the actual asset/location, problem, scope, labor, parts, downtime, test results, restored condition, failure fields where applicable, and follow-up needs. Required fields should be proportional to work type. Excessive mandatory coding encourages guessed values.

Historians, process control, and condition monitoring

A process historian stores time-series operating data such as pressure, temperature, flow, speed, load, and valve position. Condition-monitoring systems may store vibration spectra, ultrasound, oil results, thermography, or motor-current features. The CMMS/EAM stores work and asset context.

Integration can create a closed loop:

1. a monitored condition crosses an asset-specific rule;
2. the analytics service validates persistence and context;
3. an approved interface creates a notification or candidate work request;
4. a qualified person screens the finding and assigns priority;
5. the work order carries a link to trends and diagnostic evidence;
6. post-work results return to the analysis history.

Avoid creating high-priority work automatically from every transient alert. Use hysteresis, persistence, operating-state filters, duplicate suppression, and human review according to consequence.

For rotating machinery, current general guidance is found in ISO 20816-1, with equipment-specific parts such as ISO 20816-3 where applicable. Measurement location, machine class, operating state, baseline, OEM limits, and risk determine action criteria. An old reference to ISO 10816 should be reviewed because relevant parts have been superseded by ISO 20816 publications.

OT/IT architecture and cybersecurity

ISA-95 describes interfaces between enterprise and control activities and commonly uses levels 0 through 4:

• Levels 0-2: physical process, sensing/actuation, and control or supervision;
• Level 3: manufacturing operations management;
• Level 4: enterprise planning and logistics.

The Purdue-model security architecture often inserts an industrial demilitarized zone called Level 3.5 between site operations and enterprise networks. Level 3.5 is a common architecture convention, not a formal ISA-95 activity level.

A secure design may use brokered data replication, API gateways, jump services, firewalls, allowlisted flows, strong identity, certificate management, logging, and monitored remote access. The appropriate route depends on architecture and risk; avoid direct uncontrolled connections from enterprise applications to controllers.

Mobile execution and data quality

Mobile tools can improve identification and closeout when they support:

• barcode or QR verification at the physical asset;
• current controlled procedures and drawings;
• safety and permit prompts;
• actual labor and parts capture;
• photographs and measurement attachments;
• offline control and later conflict-safe synchronization;
• digital signoff with user identity and time.

A scan is evidence of an identifier, not proof that work was performed correctly. Acceptance measurements and accountable signoff remain necessary.

Implementation and governance

A disciplined implementation sequence is:

1. define decisions and required data;
2. clean asset and location hierarchy;
3. assign master-data ownership;
4. standardize work types, statuses, priorities, and codes;
5. configure role-based workflows;
6. migrate and reconcile controlled data;
7. validate integrations and security;
8. train users in the business process;
9. audit completeness, accuracy, timeliness, and use;
10. improve based on decision quality, not screen-count activity.

Track quality measures such as valid asset assignment, failure-code completeness for applicable work, BOM accuracy, duplicate records, and timely closeout. Data quality is an operational control, not a one-time migration task.