"Because," he said, "it tells you what the machine will do when everything else is lying to you."

But Peter knew the hesitation had not come from the sensor alone. It was a symptom — a conversation between components, an argument between old design and new demands. He went home at dawn with the manual in his jacket.

Peter proposed a phased rebuild. Management balked at downtime; finance saw cost, not risk. So Peter started small. He tuned. He swapped a valve here, changed a spool there, added bleed orifices like surgical stitches. At night he poured over Rohner’s descriptions of stability margins and loop interactions, cross-referencing with the plant’s original schematics. He began drawing his own schematics — the real ones — overlaying control responses with actual load traces.

One afternoon, a junior engineer asked why he still kept that old book when the factory’s servers were packed with digital libraries and vendor app notes. Peter smiled without looking up from a schematic he was tracing on the whiteboard.

Peter, who managed controls and liked his machines like he liked his whiskey — straightforward and no surprises — took the night shift. He walked the press like a doctor examines a patient, palms searching for heat, ears tuned to the rhythm of ancient pumps and modern valves. Nothing obvious. The PLC logs showed a spike, then a drop: a control valve hesitated.

He drafted a plan: add a digital anti-windup scheme in the PLC, reintroduce a damping stage upstream, and, where possible, slightly oversize the accumulators to handle the peak demand. He presented it as a single-page risk assessment with bullet points and a cost estimate. Management read it at lunch. They read it again in the afternoon. They authorized a pilot: one line, one weekend, full stop.