Proposed static MDP aid for a small joint review. Not a validated coding standard or an instruction to change a live CMMS record. Use approved local handling for actual records.
Bring the technician, reliability engineer and coding-rule owner together. Each person proposes a classification before comparing answers. Use the site's definitions and record evidence, including contradictions and unknowns.
Scroll the table sideways to see all columns.
| Prompt | Fictional July example | Your record |
|---|---|---|
| Record and equipment | July repair event, P-210 | |
| Original codes, preserved | Problem: Breakdown. Cause: Wear. | |
| Original note | Leakage at shaft seal. Visible scoring on removed seal face. Seal replaced. | |
| Symptom and supporting words | Leakage at shaft seal, explicitly in note | |
| Observed finding and supporting words | Visible scoring on removed seal face, explicitly in note | |
| Action, kept separate | Seal replaced | |
| Established cause and evidence | None supplied. Scoring doesn't establish why it occurred or whether it caused the leak. | |
| Proposed classification | Retain leakage as documented symptom; map to an available local code only after checking its definition. Record cause as not established using the agreed local mechanism. | |
| Disagreement or missing evidence | Why scoring occurred; whether it explains leakage. Seal ages and running hours absent. | |
| Who checks and accepts? | Technician checks observations; reliability engineer checks interpretation; designated coding-rule owner accepts classification under local rules. No actual acceptance recorded. | |
| Follow-up and decision owner | Reliability engineer considers investigation of repeat leakage; authorised strategy owner decides any task change after sufficient evidence. | |
| Correction and review date | Preserve original entry; log approved changes through site process. Agree an actual review date. |
Inputs: original note, equipment/event identity, existing codes, coding definitions and any linked evidence. Outputs: proposed classification with traceable support, unresolved questions and named acceptance/follow-up owners. Assumes the people reviewing can access the underlying evidence; absence from the sheet isn't proof that evidence doesn't exist.
Smallest useful version: copy this table into an approved working document and discuss three remembered jobs. Check a subsequent sample together; no success rate or reduced failure claim is implied. No electronic form, app, automated recoding or integration has been built.