Reliability Engineering

A working reliability programme for a plant: a clean asset hierarchy, criticality and failure codes, bad actor reviews, Weibull and RCM done properly, condition monitoring follow-up and the KPIs that show it paying off.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Reliability Engineering, and click Install. It goes into your own files, and works offline from then on.

Before you start: this plan is general information to help you organise your own work. It does not replace your professional judgement, the rules of your regulator or professional body, your firm's policies, or advice from a qualified lawyer, accountant or other adviser. Where a law, code or standard applies, use the current official version for your country, and get qualified sign-off on regulated or safety-critical work.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🔧 Engineering Practice

Reliability Engineering

Improving equipment reliability: failure data, Weibull analysis, criticality ranking, reliability-centred maintenance and bad actor reviews.

  1. Asset hierarchy and equipment register clean-up
  2. Equipment criticality ranking matrix
  3. Failure mode and cause code library
  4. Reliability KPI baseline from the last two years
  5. Production loss accounting by equipment cause
  6. First bad actor list from work history
  7. Work order history data quality audit
  8. Reliability engineer role charter
  9. Twelve-month reliability improvement plan
  10. Monthly bad actor review meeting
  11. Weekly breakdown and failure review
  12. Monthly reliability KPI dashboard
  13. Condition monitoring exception follow-up
  14. Lubrication programme stewardship
  15. Preventive maintenance effectiveness review
  16. Repeat failure tracker and RCFA trigger
  17. Reliability action register and close-out
  18. Annual reliability programme review
  19. Defect elimination with frontline crews
  20. Weibull analysis on real failure data
  21. Suspensions and censored data in life analysis
  22. Reliability block diagrams for system availability
  23. Rotating equipment failure mechanisms
  24. P-F intervals and monitoring technique selection
  25. Vibration analysis basics for reliability engineers
  26. Reliability growth tracking with Crow-AMSAA
  27. RCM analysis on one critical system
  28. PM optimisation for one equipment class
  29. Run-to-failure rules for non-critical assets
  30. Repair or replace decision for a bad actor
  31. Insurance spares decision from failure data
  32. Choosing reliability analysis software
  33. Mechanical seal reliability improvement
  34. Precision alignment and balancing standards
  35. Reliability input to capital project specifications
  36. Teardown inspection of a failed critical machine
  37. Early-life failure watch after a major overhaul
  38. Annual reliability business case to management
  39. OEM reliability performance review
  40. One-day bad actor improvement workshop
  41. First 90 days as a site reliability engineer
  42. Moving into reliability from maintenance or planning
  43. Reliability at a small plant with poor records
  44. Leading a reliability team across sites
  45. Short reliability assignment as a contractor
  46. Mentoring a junior engineer in reliability methods
  47. RAM study for a new or expanded facility
  48. Monte Carlo availability simulation for a production train
  49. Life cycle cost analysis for equipment selection
  50. Predictive models from historian data

Where it starts.

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

Make it yours.

Install Reliability Engineering, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.