Skip to content
Engineering Change and Part Approval | Part 2 of 6

The Change Board: One Meeting, One Decision

How a weekly change board decides on complete evaluations, what the decision record contains and how to handle rush changes.

In many plants a change is decided several times: once in engineering, once when purchasing objects, once when production refuses the date. Each round costs a week. A change board ends this by making one place where a change is decided, with everyone who must act in the room.

Who sits at the table

The board of the pump plant meets every Wednesday for 45 minutes. The members are always the same, and each has a named deputy.

  • Change coordinator from engineering: chairs, brings the agenda and the complete evaluations.
  • Quality: approval scope, effect on control plan and inspection.
  • Production: tools, capacity, training, the date on the shop floor.
  • Purchasing: supplier lead times, tool cost, open orders.
  • Logistics and planning: stock of old parts, planning parameters.
  • Sales: customer notification, approval and service parts.

The agenda

The meeting has four fixed items.

Item Minutes
Key figures: open changes, oldest change, rush changes 5
New requests with complete evaluation 20
Changes within two weeks of their effective date 10
Changes due for closure 10

The board decides. It does not design. Solutions are prepared before the meeting, and evaluations are complete two days before it. What is not complete is not on the agenda.

Three possible decisions

  • Approved. The request becomes a change order with class, owner, effectivity rule and conditions.
  • Rejected. The change will not be made. The requester hears the reason within two days.
  • Returned. The evaluation is incomplete. The record names the open dimension, an owner and the date of the next board.

In the plant, 50 of the 96 changes of the last year were decided at the first presentation, 52 percent. Every returned request costs at least a week. The time from request to decision was 21 working days on average, with a target of 10. The deadline two days before the meeting is the lever: the coordinator sees the gaps while there is still time to close them.

The decision on EC-118

Change EC-118, the O-ring groove on pump P-300, reached the board on day 8 after the request with all six dimensions answered. The record took four lines:

  • Decision: approved, class A.
  • Effectivity: fixed date, day 48. All pumps built from this day have the new design.
  • Conditions: part approval of cover and housing and the written approval of one customer before day 48.
  • Owner: the design engineer of the P-300 family.

With a one-time cost of EUR 25,250, the change was above the plant’s threshold of EUR 20,000, so the plant manager signed as well.

Rush changes

Some changes cannot wait a week: a safety risk, a line stop, a customer who cannot build. Forbidding them does not work. Making them visible does.

  • A rush change needs the signature of the plant manager or a named deputy.
  • Stock of the old parts is counted and purchasing and planning are informed on the same day.
  • The full evaluation follows within ten working days and is presented to the board afterward.
  • Every rush change is marked in the register.

In the plant, 33 percent of all changes were rush changes. Most were normal changes that someone pushed past a slow process. The share falls when the normal path becomes fast: a decision within ten working days removes the reason for most shortcuts.

What makes the board work

Three habits decide whether the meeting lasts.

  • It takes place every week, also with a short agenda.
  • The record is written during the meeting and is visible to all departments on the same day.
  • The board looks forward. Changes that approach their effective date are checked two weeks ahead: are parts, approvals and documents ready?

The board gives the change a date. What that date means for the old parts is the subject of the next part.

Newsletter

One Lean idea.
Every two weeks.