RedHub AI
How the gate works
How the PM Deferral & Pencil-Whip Tripwire works
This tool grades one asset's PM execution against pencil-whipping and repeat deferrals. It scores 3 weighted controls into a 0–100 number — then a gate that can only make the verdict worse.
The 3 weighted controls
On a criticality-A asset (line-down / safety on failure), a PM deferred twice or an implausible completion time — logged minutes far below the standard the work should take — forces RUN-TO-FAILURE regardless of the execution score. For that asset the compliance percentage is a lie; a signature is not a maintenance event, and the gate only ever holds an asset back.
Why: This criticality-A asset shows 100% completion and a clean deferral record — the execution score is 78, which alone reads RELIABLE. But the plausibility signal is 0.13: a 40-minute standard PM logged in about 5 minutes. Logged time can't cover the work, so the pencil-whip gate forces RUN-TO-FAILURE. The compliance number is a lie for this asset.
A high score didn’t save it. The score is context; the gate is the answer — and it names the one thing to fix first. Scores an asset's maintenance execution, never a person; a flag points at a record to check. Deterministic and offline on your own CMMS data, with no benchmark multiplier. Not a safety-compliance certification and not engineering advice.