Set Your Triggers, Stick to the Process


Why do things break, and how do you make sure they don’t break the same way twice?
Peter Horsburgh came to reliability engineering through mining, where everyone is trying to get the most out of their physical assets. Over more than 20 years across mining, power generation and smelting he has worked on new plants that didn’t work from day one and on day-to-day breakdowns. He has even been hired as a production manager because the production process was the thing failing. He now teaches structured, evidence-based problem solving with Sologic.
In this conversation with Phil and Ed, Peter explains why engineers jump to conclusions, why the five whys has limits, and why every failure is an equation: a set of causes that must all be present at the same time. He shows how cheap IIoT sensors fill the gaps that control systems leave, and he walks through the trigger points and team process that turned an unreliable plant into one with too much stock.
Peter Horsburgh — Sologic. Peter is an industrial reliability engineer with more than 20 years of experience across mining, power generation and smelting, in corporate and consulting roles. He trained in aeronautical engineering before moving into mechanical engineering, holds an MBA and has sat on boards. He now works with Sologic, teaching structured, evidence-based problem solving and root cause analysis. Outside work he is a pilot and is currently learning aerobatics.
This episode is brought to you by Cirrus Link Solutions and Canary Labs.
Cirrus Link Solutions — MQTT and Sparkplug software that connects OT to IT and cloud systems. Learn more: unpluggediiot.com/go/cirrus-link
Canary Labs — The industrial historian platform that captures your plant and process data the moment it is generated and makes it instantly accessible across your entire operation. Learn more: unpluggediiot.com/go/canary-labs