90 days at a new plant: notes on rolling out an equipment management system from scratch

During the build phase the equipment arrived one after another while management was a blank sheet: no register, no operating procedures, no maintenance plan. The project team copied a set of system documents from a peer company — four hundred pages thick, and nobody could read to the end of it.

My first decision was to talk them out of that document set: the value of a system lies in being executed, not in its thickness.

The 90 days split into three stages: the first 30 days build the ledger and a one-machine-one-file record, filing each piece of equipment at acceptance and collecting the nameplate, accompanying documents and acceptance data in one go; the middle 30 days write the operating procedures and inspection standards for key equipment, keeping only items operators will actually use, each no longer than one line; the last 30 days get it running: inspections go live, maintenance is scheduled, and the first monthly equipment meeting is held.

The most effective move in the rollout was writing the standards together with the shift leaders rather than writing them and handing them over. People do not resist a standard they wrote themselves.

The first reader of a system document is the operator, not the auditor. A thin document that gets executed beats a thick one that gets enshrined.

The window for building the system during start-up closes fast: original material such as acceptance data and accompanying documents cannot be fully recovered once missed.

The start-up period of a new plant is the golden window for an equipment-management system: the equipment is new, the records are empty and the staff are a blank slate, so building the system meets the least resistance at the lowest cost. Build it three years after start-up instead, and you are wrestling with entrenched bad habits and muddled accounts. What is most worth remembering from this 90-day rollout note is not the schedule but the lesson of "writing the standards together with the shift leaders": standards people help write are not resisted when carried out. Whether a system lives depends on whether the front line accepts it.