A register built once a year describes the plant as it was. Projects and changes keep moving it. A new product adds a single source, a new machine creates a concentration, a layout change puts the parts store under a different roof, and a software release can stop shipping on a Monday morning.
One question at the decision
Every change gets one question before it is approved, and the answer goes into the register with its own id.
| Change | Question at the decision |
|---|---|
| New product or variant | Which single sources, tools and tests does it add? |
| New machine or line | What has no second route once we depend on it? |
| New supplier | Sources, replacement time, signals, concentration, share of spend? |
| Layout change | What moves under a weak roof, a crane or a water line? |
| Software or system change | What happens if this release fails on a Monday morning? |
| Site or capacity decision | Which concentration do we create, and for how long? |
The cost of asking is ten minutes. The cost of not asking shows up two years later, when the part is in every product you sell and the supplier is the only one qualified.
The launch in the example plant
The site for conveyor components used in this series launched a new roller series. Four risks were rated with the same scale as the plant register.
The housing fixture could be late and the ramp could slip twenty days: 35 percent per year, EUR 240,000, score 12. A second fixture was ordered and a four week buffer was planned into the ramp.
The new motor supplier could miss the quality release: 25 percent, EUR 160,000, score 9. A pilot lot was pulled twelve weeks forward and an audit was put before the order.
The CNC programs could be late, because one programmer writes all of them: 20 percent, EUR 180,000, score 9. A second programmer was trained and every program went under version control, which also closed a risk that had been in the plant register for a year.
The new coating could fail the salt spray test: 15 percent, EUR 95,000, score 6. Two suppliers were tested in parallel with a decision after week eight.
What stays when the project ends
Running a project belongs to project management, where risks are tracked against the project plan and closed with it. What this register takes over are the risks that outlive the project: the new single source, the new critical tool, the new concentration.
In the example plant three of the four project risks became permanent register entries at the end of the ramp. The fixture risk closed with the second fixture. The motor supplier moved into the supplier raster and scored above the critical threshold. The programmer risk stayed until the second programmer had run two launches alone.
The rule that makes it work
The register owner is on the distribution list of every change decision, and a change above an agreed size cannot be approved without an answer to its question. That is one line in the change process, and it is the difference between a register that ages and one that stays current.
The same rule applies in the other direction. When a measure from the register needs a change, such as a second route or a new cable path, it enters the project list with a date, so that it is planned rather than remembered. Projects create risks, and risks create projects, and both move through the same two lists.