After visiting a chemical smart plant, a machining shop copied batch recipe models—work orders shredded, WIP harder to see. Reverse it: a process plant dispatching reactors by discrete labor hours makes operators interrupt continuous runs to "report work." Discrete vs process is not a maturity gap—it is different production objects: piece-by-piece through operations vs one batch changing properties in a unit. Paths cannot be copied.
Judge which you are—or which segment is which. Many plants are mixed; one template for all fails harder.
Discrete Tracks Work Orders; Process Tracks Batches and Parameters
Discrete core: work orders, operations, WIP location, changeover. Plan to machine and shift; quality follows piece or order. Process core: recipe version, material batch, parameter curves, tanks and pipes. Plan to unit and shift output; quality follows batch and sample points. Swapping MES screens makes the floor feel the system speaks a foreign language.
- Discrete priority: dispatch, kitting, operation transfer, equipment utilization.
- Process priority: locked recipes, material verification, parameter alarms, batch trace.
- Mixed plants: path by shop; shared layer is material and QC master data only.
Implementation Order Differs Too
Discrete often starts with kitting and operation progress—quickly reduces shortage stops. Process often starts with recipe versions and material records—blocks quality incidents first. The XYN digital intelligence system configures by shop form—neighbor success stories are not copy-paste menus. Right path makes modules worth buying; wrong path replays error at go-live.
Site visits teach principles—not menus. Menus were built for that production form.
