Reliability Simplified Work
Three plants, three starting points: a new build with no ranking, a running plant with records nobody trusted, and a vibration route about to stop. What we did and what came of it.
Pre-startup criticality for a new renewable diesel plant
Biodiesel and renewable diesel plants →The plant was months from first product with a vendor equipment list, an SAP object list that did not match it, and no ranking of what mattered. The maintenance and spares plans were about to be built on a register nobody had checked.
Built the scored equipment register on the RS 7-factor criticality model before startup, working from the P&IDs and the vendor data. Reconciled every item to the SAP object list so the ranking lives in the system the planners use, not in a spreadsheet. Documented the rule set and the method so the site can re-score when it changes equipment.
993 items scored: 131 Category A, 275 Category B, 587 Category C. The PM and critical spares effort landed on the 13 percent of equipment that can stop the plant, before the first year of failures taught the site where that was.
If you are building, converting or expanding, the criticality ranking is cheapest before startup. Everything after it, PMs, spares, inspection priorities, is sized by it.
Asset data rebuild, ten-asset pilot and root cause work at an ethanol plant
Ethanol plants →Records were scattered across two downloads and about 11,000 files. The CMMS held PMs nobody trusted, an older CMMS nobody had opened still held the real history, and the site had one maintenance manager and no reliability engineer.
Built the master tag list from the P&IDs: 3,410 tags across 47 drawings, every sheet reviewed, and checked against 67 other site lists. Rebuilt the master PM list, 10,921 lines tied to 2,497 equipment tags, from the CMMS export, the inspection programme, the area templates and the checklists. Recovered 14,568 work orders of history from the old system. Sorted the files by system, area and tag so a planner can find a drawing. Then carried ten assets, chosen by the site, through the full sequence, register, criticality, failure modes, PM tasks and spares, so the site could see the finished product before funding the rest.
Two root cause analyses are underway with the site team: a pair of compressor motors that failed within months of a like-for-like swap, and an incline auger whose coupling bolts had sheared nine times in seventeen years without anyone asking why. Both run on the RS cause map method, every cause backed by a work order, photo or trend. One finding is already closed: the dryer beds, where changing both beds in the same outage with wet media cost the plant off-spec product, now change one bed at a time on test results.
63 findings on the ten pilot assets, including relief valves with no test record for more than a decade. 40 plant-wide issues logged, 22 fixed. Onsite maintenance support, storeroom organisation and turnaround scope review alongside.
Thin data is a reason to start, not a reason to wait. The register gets built while the first findings are being fixed.
Route-based vibration program at an oilseed crush plant
Oilseed crush plants →The plant’s vibration contractor stepped away part way through the contract year. The monthly route, the trending and the report the site had learned to read were about to stop.
Took over the route the following month. Kept the report format the site already used so nothing had to be relearned, and kept the historical trends intact so the alarms still mean what they meant.
No gap in condition data. One flat monthly fee, the same every month, which is how the Reliability Support Plan works.
Condition monitoring only pays if it is continuous. If your route has stopped, or never started, this is the smallest first step we offer.
Client names withheld. Ask us about any of these on a call.
Start with an assessment.
Tell us which of these sounds like your plant. The assessment is one fixed price, travel included, and it tells you where to start.