Industrial equipment inspection turns an observable condition into a traceable decision with defined criteria, authority, and destination. A consistent route identifies the function being protected, the failure mode it may reveal, the observation method, the conditions that make data comparable, and the output opened when a deviation is found.
Generic lists of checked items often produce volume without actionability. Field personnel need the point, acceptable condition, method, mandatory evidence, and safety boundary. Maintenance planning needs enough context to prioritize and prepare work. Reliability engineering needs to determine whether the task can find the mechanism early enough to act.
Move from function to inspection point
Design begins with asset function and the consequence of losing it. The team then selects failure modes that have a detectable condition. Every task needs a technical ability to identify that condition within an interval that leaves time for confirmation, planning, and execution.
NASA's RCM guide organizes maintenance selection around functions, functional failures, failure modes, consequences, and applicable tasks. This logic prevents routes based only on habit. It also explains why visual inspection, process readings, functional testing, and instrumented condition techniques cannot be treated as equivalent methods.
Inspection types answer different questions
- Visual and sensory: looks for leakage, apparent looseness, contamination, corrosion, damage, noise, or odor under a safe procedure.
- Operating reading: records pressure, flow, current, temperature, or position already available in the process and connects the value to operating regime.
- Functional test: checks whether protection, alarm, valve, interlock, or standby equipment performs the defined function.
- Condition technique: applies thermography, vibration analysis, ultrasound, or oil analysis with its own parameters and competency requirements.
- Statutory or integrity inspection: follows applicable requirements, an inspection plan, and responsible authority and cannot be replaced by a routine maintenance route.
The right combination depends on the mechanism. A clean housing does not confirm alignment. A gauge within range does not establish mechanical integrity. Perceived noise may guide confirmation but needs a reproducible description. The task should state its limitation to avoid confidence beyond the evidence.
Minimum contract for an inspection task
| Element | Control question |
|---|---|
| Object | Which equipment, assembly, and point will be observed? |
| Function | Which performance does the task help preserve? |
| Failure mode | Which mechanism can produce the detectable condition? |
| Method | How will personnel observe, measure, or test without improperly changing the condition? |
| Operating state | Which load, speed, temperature, or state makes the data comparable? |
| Criterion | What is acceptable, anomalous, urgent, or inconclusive? |
| Evidence | Which value, image, catalog selection, or comment is mandatory? |
| Output | When should personnel notify, create an order, repeat, escalate, or close? |
| Safety | Which access, energy, and competency boundaries govern the task? |
Criteria may come from manufacturer specifications, engineering, applicable standards, acceptance tests, stable history, or internal analysis. A limit copied from another asset requires demonstrated compatibility. Where no limit exists, the route should establish baseline and context without inventing an alarm.
Set frequency according to available response time
The predictive maintenance strategy combines this route with other condition techniques. Periodicity responds to mechanism speed, detection capability, and the time needed to act. The P-F concept models the interval between the first detectable potential failure and functional failure. A route should provide more than one detection opportunity and enough room for the downstream process.
High criticality does not automatically require a daily visit. If the method cannot detect the failure mode or the interval is too short, increasing visits creates false assurance. Protection, strategy, method, or contingency may need redesign. The plan should record the interval assumption and review frequency from field results.
Completed teaching case: pump P-118
All case data are instructional. They do not represent a customer, benchmark, or PM Run performance. Centrifugal pump P-118 supplies cooling water to two heat exchangers. A standby pump is available, but transfer requires operator action and a weekly test. P-118 must deliver 36 m³/h with discharge pressure from 3.9 to 4.3 bar in the defined regime.
Context and assumptions
| Field | Case definition |
|---|---|
| Speed | 1,480 rpm |
| Route regime | Flow between 34 and 38 m³/h after 20 stable minutes |
| Electrical reference | Average current of 42 A in regime, internal observation range from 39 to 45 A |
| Discharge reference | 4.1 bar, approved operating range from 3.9 to 4.3 bar |
| Initial frequency | Weekly, based on the internal interval estimate and available redundancy |
| Anomaly output | Notification with priority set by the risk matrix |
| Review window | 90 days or 12 complete inspections |
The team reviewed failure history, function, technician experience, and access conditions. Six points were selected because each had a connection to a failure mode and a possible response. Measurements that the team could not reproduce or interpret were excluded.
Completed route
| Point | Case method and criterion | Expected output |
|---|---|---|
| Seal | Observe leakage pattern in regime. An intermittent film is accepted by the local criterion. Continuous flow requires a notification. | Permitted image, class, and notification |
| Base and anchors | Check witness marks, corrosion, and apparent looseness without contacting moving parts. | Notification for displacement or integrity loss |
| Coupling guard | Confirm attachment, integrity, and absence of contact. | Immediate escalation under the safety procedure |
| Discharge pressure | Record the identified gauge value together with flow and regime. | Notification outside 3.9 to 4.3 bar |
| Current | Record the reading available from the authorized electrical system and associate it with flow. | Repeat and notify outside the internal range |
| Sound condition | Select a standardized descriptor at a safe listening position. | Technical confirmation when a change is found |
Data found on August 18, 2026
The route took place after 25 stable minutes at 35.8 m³/h. Discharge pressure was 3.5 bar. Current was 50 A, approximately 19% above the 42 A reference. The seal showed continuous flow, and one anchor witness mark had moved 3 mm. The guard remained attached and intact. The technician selected the internal broad-band sound change descriptor without entering a diagnosis.
The combination of lower pressure, increased current, leakage, and base movement indicated a relevant degraded condition. Every observation was repeated within the permitted state. Operations confirmed stable flow and process conditions. Because the points belonged to the same asset and time window, they were grouped in one notification with separate evidence.
Triage and decision
The planner did not close the cause from the route. Engineering considered misalignment, seal damage, hydraulic restriction, and internal damage. History showed seal replacement 45 days earlier with no final alignment record. The standby pump was tested and made available.
The internal matrix assigned high priority, with controlled transfer to the standby unit and planned intervention within 24 hours. The operating authority approved the transfer after checking standby capacity and stability. These time rules belong to the teaching case and do not define universal limits.
SAP PM output
The notification captured P-118, functional location, date and time, operating state, values, units, affected points, descriptors, evidence, and the triage decision. Symptom fields contained observations. Cause and causing part remained pending until intrusive inspection.
The linked order included operating transfer, isolation, base and anchor assessment, coupling inspection, alignment, seal evaluation, hydraulic inspection, approved correction, and return-to-service testing. Operations, materials, labor, and confirmation points were planned. The work plan required the as-found condition before component replacement.
As-found condition, correction, and history
With the pump isolated, technicians found one anchor below the project torque criterion, misalignment outside the internal tolerance, and seal damage. The impeller and suction line showed no restriction. Engineering approved base correction, seal replacement, alignment, and tightening to the procedure.
History captured measured as-found values, components, material, time confirmations, alignment result, and test. The causal review linked the finding to the previous job, which lacked final alignment evidence. The task list was revised to require that record on future seal replacements.
Test and verification window
During the return test, flow reached 36.2 m³/h, pressure reached 4.0 bar, and current stabilized at 43 A. Seal condition met the local criterion, anchor marks remained aligned, and the sound descriptor returned to normal. The team repeated the route after 24 hours, weekly for four weeks, and then continued weekly until 90 days were complete.
Success required four conditions: no recurrence, discharge pressure from 3.9 to 4.3 bar in regime, current from 39 to 45 A, and 100% of inspections with flow, time, and mandatory evidence. A repeated condition would reopen the strategy instead of producing another identical order by default.
Turn deviation into executable work
A well-written anomaly separates fact, hypothesis, and decision. "Discharge pressure 3.5 bar at 35.8 m³/h" records a fact. "Possible misalignment" records a hypothesis. "Transfer to standby and inspect within 24 hours" records an authorized decision. This separation reduces premature closure and improves maintenance history.
SAP documentation describes maintenance notifications as records of problems and activities at technical objects. Relevant notification data can support creation or linkage of an order according to system configuration. The local process should define mandatory fields, catalogs, attachments, and accountabilities.
Inspection indicators
- Route compliance: tasks completed within the required time and operating state.
- Completeness: points with regime, value, unit, and mandatory evidence.
- Actionable conversion: anomalies that received a decision and destination within the rule.
- Delay: overdue notifications and orders relative to approved priority.
- Confirmation: anomalies confirmed during intervention or complementary testing.
- Recurrence: return of the same deviation after correction.
- Strategy review: tasks changed when they fail to detect or leave inadequate response time.
Completing every route does not establish effectiveness. A task can meet its schedule and still produce incomparable data. Governance should combine adherence, record quality, decision, confirmation, and intervention result.
PM Run's role over SAP PM
PM Run operates as a planning, mobility, and execution layer connected to SAP PM. A company can distribute routes and orders, collect permitted confirmations, and return results to the configured process. SAP remains the system of record. Strategy, method, limits, and priority belong to plant technical governance.
PM Run does not offer an inspection service, sensor, diagnosis, predictive AI, or ready-made condition dashboard. To connect fieldwork and planning to the corporate system, review PM Run's operational layer for SAP PM.
Limits and controls
- A route covers only failure modes compatible with its methods.
- A condition safe to observe can change with equipment state and process.
- Instruments and indicators require identification and applicable metrological control.
- Process data may require validation before supporting a maintenance decision.
- Low event frequency limits statistical inference.
- A routine inspection does not replace a statutory obligation or integrity plan.
- An inconclusive result should generate confirmation rather than convenient closure.
Route exception handling
A route needs an explicit response when the required operating state is absent. If P-118 were stopped, below minimum flow, or inaccessible under the approved boundary, the technician would mark the task as not performed with a reason rather than enter a normal value. Planning would reschedule the point or select an approved alternative method.
The same rule applies to questionable instruments. An unreadable gauge, broken identification tag, or overdue calibration status becomes its own notification. The field record preserves the attempted inspection and prevents a guessed value from contaminating trend data.
During the 90-day verification window, the supervisor sampled three completed routes against the physical points and source readings. The audit checked timestamps, operating regime, units, evidence, and downstream decisions. Any systematic gap would trigger route revision and focused coaching before the compliance percentage was accepted.
Technical references
- NASA Reliability-Centered Maintenance Guide, accessed August 23, 2026.
- SAP Help Portal, Maintenance Notification, accessed August 23, 2026.
- SAP Help Portal, Creating an Order from a Notification, accessed August 23, 2026.
Frequently asked questions
Are a checklist and a route the same?
A checklist is a format. A route also includes technical selection, frequency, execution state, competency, evidence, anomaly rules, and downstream workflow. A strong checklist materializes part of that design.
Should every anomaly create a work order?
The output may be repetition, confirmation, notification, order, immediate action, or justified closure. The rule should exist before collection and respect authority, risk, and process configuration.
How should a specialized technique be added?
Create a dedicated task with qualification, parameters, and limits. Infrared thermography in industrial maintenance shows how to preserve load, emissivity, reference, and verification without reducing the technique to an image.
