Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Asset hierarchy and equipment register clean-up
Failure history is only as useful as the equipment tags it hangs on, and most CMMS registers carry duplicate tags, orphaned motors and pumps logged against the wrong functional location. Agreeing a hierarchy from site down to maintainable item, in the spirit of the ISO 14224 taxonomy, and cleaning one unit against it, means every later Weibull plot and bad actor ranking counts the right failures.
First tasks
- Export the CMMS register for one process unit to a spreadsheet
- Draft the hierarchy levels and the naming rule for each level
- Walk the unit with the P&IDs and mark tags that are missing or wrong
- Send the correction list to the CMMS administrator with evidence
Equipment criticality ranking matrix
Engineering effort is scarce, and without a criticality ranking it goes to whichever machine made the most noise last week. A matrix that scores each asset on safety, environment, production and repair cost consequence, multiplied by a rough likelihood, gives a defensible A, B and C ranking that decides strategy, spares and monitoring for years.
First tasks
- Draft consequence scales for safety, environment, production and cost
- Book a half-day scoring session with an operator, a planner and HSE
- Score the unit's assets and record the reasoning for every A
- Revisit criticality scores after plant or process changes @recurring(yearly)
Failure mode and cause code library
Closed work orders that say "pump repaired" tell you nothing about why it failed. A short list of failure modes, mechanisms and causes per equipment class, drawn from ISO 14224 and trimmed to what technicians will actually pick, turns every breakdown into data you can trend.
First tasks
- List the five equipment classes with the most corrective work orders
- Draft failure mode and cause codes for each class from ISO 14224
- Test the codes on twenty recent work orders with a senior technician
- Agree with the CMMS administrator how to make the codes mandatory