MES for Mid-Size Food Plants: What You Need and What You Can Skip

The MESA model lists a long set of MES functions, and enterprise products implement most of them. In a single-site food plant with a few lines, the functions that get used every day are a much shorter list. These are the ones worth building first, because each one removes manual recording or re-keying that someone on site is doing today.

• Production order tracking: which order and SKU is on which line, when it started and finished, and quantity made against plan.
• Performance and downtime by order: OEE and stop reasons attributed to the order and SKU, not just a time window.
• Material and lot tracking: ingredient and packaging lots consumed and finished lots produced, so a trace runs both ways.
• Quality checks and holds: in-process checks recorded against the lot, with hold and release status visible to production.
• Cleaning and process records: CIP cycles and critical process data linked to the batch they cleaned or treated.
• Results back to ERP: produced quantity, consumption and scrap posted without re-keying.

For many mid-size plants the practical path is an MES-lite: the core functions above built on the SCADA platform and SQL database the site already runs or is adopting, with data models that follow ISA-95 so they can grow. Ignition suits this well because data collection, storage, screens and reporting share one platform and one open database, and MES modules can be added where they fit. An enterprise MES is the better answer when the requirements are genuinely enterprise-sized.

• Build when one site, a few lines and a limited SKU range need order tracking, downtime by order, lot records and ERP posting.
• Build when the plant already runs Ignition or a SQL historian, so the new functions extend screens operators already use.
• Buy when many sites must run one standard process, or when validated electronic batch records are a hard requirement.
• Buy when scheduling across shared, constrained equipment is complex enough to need a dedicated optimiser.
• Either way, the PLC and SCADA signal layer has to be right first, because every MES function depends on it.

An MES sits between the line and ERP, so its value depends on a clean handshake in both directions: orders and recipes released down, and output, consumption, scrap and batch results posted back. We design that boundary on the ISA-95 object models, with transaction rules for backflush timing, partial completions, duplicates and communication loss agreed before any code is written. The detail is on the ERP and SAP integration page.