Multi-Site Tool Control That Plants Will Use

by a.huynh | 20th Jul 2026

A manufacturing group rarely has a tooling problem on only one site. It has a version of the same problem in every plant, solved locally, with different item codes, different limits and a different story about why the crib works the way it does. Group purchasing sees three prices for what might be one glove. Quality sees three ways of recording a gauge. A new plant manager inherits a process that lives in someone’s head. When the board asks which site is consuming cutting tools heavily, the honest answer is that the question cannot be asked in a common language.

Standardising tool control across sites is less about identical cabinets and more about identical meaning. The same item should have the same identity. The same class of risk should follow the same rule. Local work should still be allowed to shape the hardware, the quantities and the location. Groups that reverse those priorities, imposing a common cupboard and leaving the data messy, buy uniformity that nobody can report on. Groups that do it the other way round get a standard people will run.

Start with the item, not the cabinet

Two sites cannot be compared if they describe the same insert, the same glove or the same torque wrench in different words. The first project is a short, governed item master for the products you intend to control, not for every SKU in the business. Identity, description, unit of issue, a plain-English family, whether the item is consumable or returnable, whether it has a calibration or shelf life, and the risk class that determines the rule. Supplier part numbers can differ. The internal identity should not.

This is slower than ordering cabinets, and it is the work that makes the cabinets worth ordering. Involve a setter, a nurse or safety adviser where PPE is in scope, and a buyer. The people who will argue about descriptions are the people who will have to live with them. A family structure matters more than a perfect taxonomy. “Cut-resistant glove, level C, size 9” is a description a night shift can trust. A 40-character supplier string is not.

Once the master exists, local additions need a front door. A site that quietly creates a duplicate code has broken the standard, usually for a good local reason. Give them a fast way to request a new item and a person who will answer in days, not in the next quarterly meeting. Standards die when the official path is slower than invention.

One rule set, expressed locally

Decide at group level which classes of item carry which rule. Returnable, calibrated gauges might require a named holder, a due-back date and a lock when the certificate expires. High-value cutting tools might require a work order or a machine identity. PPE might require a role and a fair limit, with no charge to the worker. Low-value bulk might require only an identity and a replenishment trigger. Write those rules in a page that a supervisor can explain.

Then let the site decide the quantity, the location and the hardware. A heavy industry plant and a precision cell will not hold the same number of gloves or the same mix of inserts. A transport and maintenance depot may need kit on a vehicle route rather than at a single crib. The rule “a calibrated gauge has a named holder” can be true in all three places while the cupboard looks different. SupplySystem is useful here because the management of the rule and the replenishment can sit above the particular cabinet, locker or weigh bin the site actually needs.

Local variation should be visible. If one plant switches off a limit, that should be a recorded exception with an owner and a review date, not a quiet configuration change. Group standards fail in the settings screen more often than they fail in the policy document.

Replenishment that respects the way each site buys

Some groups buy centrally and deliver to sites. Some let sites buy inside a framework agreement. Some are midway through an argument about which of those they are. Tool control does not have to settle that argument before it starts, but it does have to stop each site reordering from a different view of stock.

The minimum viable picture is a site-level on-hand figure that group supply can see, built from issues rather than from a monthly stocktake. Who raises the purchase order can stay where the commercial model says it should stay. What should not stay local and invisible is the fact that three sites are about to run out of the same item while a fourth is overstocked. Transfers become possible only when the identity and the quantity mean the same thing in each place.

Lead times differ. A plant in a remote location cannot run the same minimum as a plant next to the supplier. Encode that in the replenishment parameter, and resist the urge to “simplify” it into one number that makes the remote plant fragile and the nearby plant fat. The standard is the method of setting the minimum, not the minimum itself.

How to roll it out without a revolt

Pick a lead site that is respected and that is not so unusual that others can dismiss it. Prove the item master and the rule set there, on a narrow range. Publish the before and after in operational language: stockouts on the controlled list, time to issue, overdue gauges, PPE sizes that no longer run dry. Other plants should visit. A standard that arrives only as a slide will be interpreted as head office tidiness. A standard that a sister plant is already running will be interpreted as a way to make the shift easier.

The second and third sites should join the same item master rather than copy it into a fresh database and “tidy it later”. Later is when the codes diverge. Hardware can be phased. Data should be common from the first additional site.

Train the owner, not the crowd. Each site needs a named person for the item master, a named person for exceptions, and a replenishment routine that survives holidays. Users need a short demonstration and a cabinet that works on the first morning. If the first morning fails, the old drawer returns by lunchtime, and the group story becomes “we tried that”.

Measure a little, and measure the same thing everywhere. Five indicators are enough. Issues on the controlled list, stockouts on that list, overdue returns, items with no movement, and the percentage of issues carrying the required reference. A league table of consumption per head is a good way to start a fight and a poor way to run a standard. Different sites make different things. Compare each site with its own baseline, and compare practices where the work really is alike.

What head office should stop doing

Head office should stop collecting spreadsheet extracts that each site builds differently, and should stop announcing a common cabinet before the common language exists. It should also stop treating local resistance as nostalgia. Resistance usually points at a real constraint: a shift pattern, a product the master does not contain, a lead time the minimum ignores, a contractor flow the rule did not mention. Fold that constraint into the standard or record it as an exception. Ignoring it produces a shadow process, and shadow processes are how multi-site control quietly returns to single-site folklore.

Calibration, PPE and the standards that must not drift

Two categories deserve group rules even when everything else is allowed to flex. Calibrated equipment is one. If a gauge can approve a part that will be shipped from more than one plant, the customer will not accept a different idea of “in date” at each address. The standard should say when an item locks, who may extend it, and how a certificate is stored against the same identity the cabinet uses. Local labs can still do the work. They should not invent a local definition of expiry.

PPE is the other. A glove standard, a hearing-protection standard or a harness inspection interval that differs by site for no reason connected to the task is how a group fails an audit in the plant it visits least. Where the task truly differs, the risk assessment should say so and the item master should carry both standards as different items, not as a vague “glove”. Where the task is the same, the issue rule should be the same, including the rule that workers are not charged.

A monthly half-hour call between the site owners is enough governance once the master exists. The agenda is exceptions granted, items requested, non-movers, and any rule a site wants to change. Decisions are written back into the master that week. A quarterly look at the five indicators, with operations rather than a slide team, keeps the standard attached to the work. Groups that replace this with an annual policy refresh discover, every January, that the sites have been improving locally in incompatible directions.

The prize is modest and valuable. A buyer who can see one glove, not four. A quality manager who can ask where a gauge is and get the same kind of answer in any plant. A new starter who meets the same issue method they met at the sister site. A capital request for the next cabinet that is based on use, not on whichever site shouted last. Identical buildings are unnecessary. Identical meaning is the whole job.