One Measures. One Just Gets In The Way!

Speed cameras and speed bumps exist to solve the same problem. Drivers going too fast on roads where that creates danger. Both are attempts to manage human behaviour in a system where the consequences of getting it wrong can be severe.

They’re not, however, the same solution.

A speed bump doesn’t measure anything. It doesn’t tell you how fast someone was going. It doesn’t record whether the road is generally safe or systematically dangerous. It doesn’t identify patterns. It simply forces every vehicle – ambulance, school bus, family car, delivery van – to slow down regardless of whether slowing down is necessary, at a cost in time, fuel, comfort, and wear that is paid by absolutely everyone, not just those who would have been speeding.

A speed camera, by contrast, measures. It captures data. It records speed, time, location, and vehicle identity. It allows genuine analysis of where problems are concentrated, when they occur, and how serious they are. It intervenes precisely and proportionately – and it generates a body of evidence that can be used to make systemic improvements to road safety over time.

The sad truth, that we have to face is that scheduled maintenance inspection in a process facility is, in most cases, a speed bump.

Every three months – or six months, or twelve months, depending on the programme – a maintenance engineer visits every critical connection on the plant. They check, re-torque if necessary, record the outcome, and move on. The schedule is the same for every fitting regardless of whether that fitting has been perfectly stable for five years or has been showing subtle signs of load change for the past six weeks.

The compliant fitting and the concerning fitting receive identical attention. No data is generated to distinguish between them. No trend can be identified. No early warning is possible. The process generates documentation, but not intelligence.

Real-time connection monitoring is the speed camera. It measures continuously, records everything, and intervenes – alerts the maintenance team – only when something actually changes. The connection that’s been holding steady at 87 kN for eighteen months receives no unnecessary attention. The connection that’s dropped from 87 kN to 81 kN over the past three weeks is flagged immediately, with a full data record showing exactly when the change began, at what rate it progressed, and what the current load is.

The question this raises isn’t “should we monitor or inspect?” – it’s “what are we actually trying to achieve?” If the goal is documentation that something was checked, scheduled inspection delivers that. If the goal is genuine assurance that critical connections are maintaining their integrity, that early warning of deterioration is available, and that the data trail satisfies ALCOA++ requirements – then continuous monitoring is not a luxury upgrade. It is the appropriate tool.

The hidden cost of speed bumps is rarely calculated accurately. Every vehicle, every journey, every day – the friction adds up. In a process facility, the hidden cost of scheduled inspection follows the same logic: technician hours spent on connections that needed no attention, maintenance windows opened unnecessarily, process interruptions that could have been avoided if the data had been available to say “this one is fine, that one needs attention.”

Speed bumps made sense before speed cameras existed. They were the best available tool for a problem that needed addressing. Nobody would design a road safety system around them today if they had the choice. And yet, much of the process engineering industry is still designing maintenance programmes around the equivalent – not because it is the best approach, but because it is the familiar one.