Every site insists its codes fit the floor better. Six months later, one screw has six part numbers—transfers need crosswalks and group inventory is stitched together. The first constraint on multi-site coordination is master data, not which MES looks prettier. Local optimization can keep process parameters; it cannot keep a second identity. Once identity splinters, coordination becomes email and Excel.
Six local optima often sum to a global worst. Share one identity first, then compare takt.
Only One Identity
Materials, customers, suppliers, and org structures are published by HQ master-data stewards. Sites may request aliases and process extensions—not self-assigned primary codes. Reconciliation uses primary codes. New sites cleanse master data before transactions.
- Ban "temporary codes used forever"—temp codes must have a close date.
- Transfers, planning, and finance share the same code version.
- Local reports may slice data; they may not spawn a second dictionary.
Local Optimization Lives in Parameters
The XYN digital intelligence system keeps master data at group level and leaves process, shifts, and warehouse policy to site configuration. Coordination rides on one identity; efficiency rides on local parameters. Without identity, six optimization projects are six islands.
Pull ten cross-site transfer orders—see if crosswalk tables appear. If they do, fix master data before the next lean round.
