Learning Objectives

By the end of this lesson, the technician will be able to:

• Objective 1 (Cognitive/Understanding): Explain the CMMS's role as the plant's maintenance memory — asset hierarchy, work orders, parts records, and history — and how asset numbers link the digital record to physical equipment tags and the drawing set.
• Objective 2 (Diagnostic/Analytical): Mine equipment history as a diagnostic instrument: repeat-failure patterns, what-changed timelines, and prior technicians' findings — and recognize when bad correlation (wrong asset, vague entries) has poisoned the record.
• Objective 3 (Field/Practical): Write work-order documentation that compounds in value: complete, specific, correlated entries — asset verified, documents referenced with revisions, values recorded with provenance — that turn every job into the next job's head start.

Field Scenario

The Pump With Two Histories: A technician is dispatched on "WO-88412: P-104 — excessive vibration." Before walking out, she pulls the asset's CMMS history — the habit this lesson installs — and finds something strange: P-104's record shows a bearing replacement eight weeks ago, then vibration complaints at six weeks, four weeks, and now. Three visits, three different technicians, and the prior entries read, in their entirety: "replaced bearing, ran fine" and "checked pump, vibration normal at this time."

At the machine, the 10.1 verification habit cracks the case before a wrench moves: the pump in front of her is tagged P-104B — and twenty feet away sits P-104A. The plant duplexed this service years ago (the same Rev F change from Lesson 10.1's scenario), but the CMMS still carries a single asset, "P-104." Three technicians have been writing two physical machines' events into one digital history: the bearing was replaced on the A pump; the vibration complaints are on the B pump — which, its own (unrecorded) story turns out to show, has been running degraded for months while its paper twin looked freshly serviced. The repeat-visit pattern wasn't a mystery; it was a correlation failure: the digital record and the physical plant disagreed about how many machines exist.

The fix is two-layer, like every documentation fix in this module: the immediate repair (B-pump's failing bearing, found by Module 4's methods), and the systemic one — an asset-record correction request splitting P-104 into A and B with history annotated, routed through the site's CMMS administration (the 10.9 redline doctrine, applied to the database). A CMMS is only as truthful as its correlation to steel — and every technician either maintains that correlation or erodes it, one entry at a time.

Concept Overview

What the CMMS Is

The Computerized Maintenance Management System (SAP PM, Maximo, eMaint, Fiix, MaintainX, and kin — the concepts transfer across all of them) is the plant's maintenance memory and dispatcher:

• Asset hierarchy: plant → area/system → equipment → sub-component, each level carrying an asset number. The hierarchy mirrors (or should mirror) the physical tag system and the drawing set's equipment tags — the same P-104/E-301 identities from Lesson 10.2. The asset record carries the nameplate data (model, serial — Lesson 10.7's anchor), specifications, and document links.
• Work orders (WOs): the unit of work — problem description, asset, priority, planned parts/labor, and (the part technicians own) the completion record: what was found, what was done, what was measured, what remains.
• PM schedules: recurring work generated against assets — the routes of Lesson 2.5, with their task lists and intervals.
• Parts/inventory linkage: parts charged to WOs build the asset's consumption history (which is itself diagnostic — "this machine eats seal kits" is a queryable fact when parts are charged correctly, and folklore when they aren't — Lesson 8.6's subscription detector).
• History: the accumulated record — the asset's medical chart.

The Correlation Triangle

Three identity systems must agree for documentation to work, and the technician stands where they meet:

1. The physical tag on the machine (the stamped plate, the stenciled number),
2. The drawing set's tag (P&IDs, schematics, layouts — Lessons 10.2/10.5),
3. The CMMS asset number.

When all three agree, every record enriches every other: the WO links the drawing, the drawing locates the machine, the machine's tag confirms the WO. When any pair disagrees — renamed equipment, duplexed services (the Field Scenario), assets created from purchase orders instead of P&IDs — history fragments, parts charge to phantoms, and PMs service machines that don't exist while real ones run untended. Verification of the triangle is step one of every job (10.1's habit, now with three corners), and triangle breaks are reportable findings, not shrugs.

History as a Diagnostic Instrument

The asset history answers the questions Modules 4–8 and 11 keep asking:

• "What changed?" — the recurring diagnostic question (the repipe of 7.5, the winter oil of 8.3, the weekend VFD install of 6.9) is queryable when history is honest: recent WOs on this asset and its neighbors are the change log.
• Repeat patterns: the same failure at intervals is a root-cause flag (Lesson 11.2's raw material) — visible only if prior entries say what actually failed and why, not "fixed, runs fine."
• Baselines: prior recorded values (vibration readings, case-drain flows from 8.3, stall pressures from 8.1, as-found calibrations from 6.10) convert this visit's measurement into a trend — the difference between "4 GPM case drain" meaning nothing and meaning "doubled in a year, schedule the rebuild."
• Prior findings and warnings: the last technician's "rod shows early scoring, will need attention" is gold — if it was written.

Why Entries Rot — and the Antidote

The failure modes are human and universal: entries written at shift end from memory ("replaced bearing, ran fine"), wrong-asset charging (close enough!), values observed but not recorded, findings noticed but not written, documents used but not cited. The antidote is a standard of entry — Section 4 — applied like torque spec: not optional, not stylistic, the actual deliverable. The work order is a controlled document; Lesson 0.5's engineering-notebook discipline graduates here into the system of record.

How the Principle Works: The Two Bookends of Every Job

Bookend One — the Pull (Before Walking Out)

1. Read the WO completely — problem statement, asset, safety notes, planned parts.
2. Verify the triangle on paper: the WO's asset vs. the drawing set's tag (and pull those drawings, current rev — 10.1/10.2/10.5 as the job requires).
3. Mine the history: this asset's last 6–12 months (open + closed WOs), repeat patterns, recent changes on it and its system neighbors, recorded baselines relevant to today's symptom, parts consumption.
4. Arrive informed: the history's questions ("third vibration complaint — what did the last two visits actually find?") shape the diagnosis before the toolbag opens. Then verify the triangle's third corner in the field: physical tag vs. WO asset — the Field Scenario's thirty-second save.

Bookend Two — the Entry (Before the Job Is "Done")

The completion record carries five elements, every time:

1. As-found: the observed condition and measured values with units ("axial play 0.018 in. vs. 0.005 max per Manual 88-1020 Rev C Table 4-1" — provenance per 10.7).
2. Work performed: specific actions, parts with part numbers (charged to the right asset), torque/settings applied with their sources.
3. As-left: post-work measurements and verification performed ("test ran 30 min, vibration 0.08 in/s vs. 0.31 as-found") — the baseline the next technician inherits.
4. Root cause / findings: what actually caused it (or the honest "cause not confirmed — monitoring recommended"), plus anything noticed for the future ("coupling guard fastener missing — corrected"; "B-pump rod scoring early — flag for next PM").
5. Correlation maintenance: documents used cited with revisions; triangle breaks, drawing discrepancies, and asset-record errors reported through the proper channels (10.9 for drawings, CMMS administration for asset data) — referenced in the entry so the report and the history cross-link.

The compounding effect is the point: entries written to this standard make every future pull (Bookend One) more powerful — failure patterns surface, baselines trend, and the plant's collective diagnostic memory grows. Entries written as "fixed" make the CMMS an expensive calendar.

CMMS Correlation Reference Matrix

Field Application Checklist: The Documented Job, End to End

1. Pull before walking (Bookend One): WO read, triangle verified on paper, drawings pulled at current rev, history mined — patterns, changes, baselines noted into the job plan.
2. Verify in the field: physical tag vs. WO asset before diagnosis begins. Mismatch = stop; work the right machine, and report the record error. (All physical work under its own boundaries — Module 1, and the discipline lessons the job involves.)
3. Interview operations and annotate the problem statement with what's actually observed — the WO's words steer everyone downstream; make them true.
4. Record as you go, not at shift end: measurements at the moment of measuring (photo of the gauge/indicator with the job notes), part numbers as installed, document citations as used. Memory is a lossy instrument; the 0.5 notebook habit feeds the entry.
5. Write the five-element completion record (Section 4, Bookend Two) before the WO closes. The test: could the next technician, starting from only this entry, know what was found, what was done, what the numbers were, and what to watch?
6. Charge parts to the verified asset with real part numbers (10.3's chain) — consumption history is diagnosis-grade data only when it's true.
7. Route the systemic findings: drawing discrepancies → redline channel (10.9); asset/hierarchy errors → CMMS administration; PM task-list gaps → planner/supervisor — each referenced in the WO entry so the threads cross-link.
8. Feed the asset record's permanent layer when the job produced durable knowledge: verified specs with provenance (10.7), new baselines, corrected nameplate data — the six-minute lookup becoming the six-second one.

Knowledge Check

Source List

• SMRP (Society for Maintenance & Reliability Professionals) best-practice guidance — work order documentation and asset hierarchy standards
• ISO 14224 — equipment reliability and maintenance data collection (taxonomy and failure-data structure, adapted from its origin industry into general practice)
• CMMS vendor documentation conventions (Maximo/SAP PM/eMaint class) — asset, WO, and history structures
• Lessons 0.5, 2.5, 10.1–10.7, 10.9 cross-references — field notebook discipline, PM routing, the documentation chain, and the correction channels
• Reliability engineering literature (Mobius Institute class references) — history-driven failure analysis context (with Module 11)