MES for Mid Size FMCG Plants: What to Start With and What to Skip

Key takeaways

• A mid size FMCG plant should start its MES with OEE and automatic downtime logging on the lines that make the most money.
• Changeovers, short stops and speed loss are where FMCG lines lose the most time.
• Skip detailed scheduling and batch records at the start unless a rule demands them.
• Price every lost minute in money, so the team works on the costliest loss first.

For a mid size FMCG plant, the best MES is the one that shows where each line loses time, live, and ranks those losses by cost. Start with OEE and downtime on your biggest lines; add the rest only when a real need appears.

This guide is for plant managers and operations directors in food, beverage, personal care and household plants with roughly 3 to 15 packaging lines. Fabrico, a light MES built around OEE and downtime, works with plants like these, and this is the order we see work.

Why is FMCG different from other industries?

FMCG lines are fast, linked and change format often. A filler, a labeller, a case packer and a palletiser run as one line, so a stop on one machine can starve or block the others. Many SKUs share one line, so changeovers happen every shift.

Downtime also costs more here than many plants think. Siemens, in its 2024 True Cost of Downtime report, put a lost hour at $36,000 in FMCG for large plants, and FMCG was the only sector whose downtime hours went up since 2019. A mid size plant will have its own number, lower or higher, but the direction is clear.

Which MES functions should a mid size FMCG plant start with?

The first five are the light MES core. They are what a mid size plant uses every day. Our guide to changeover standards in FMCG covers the third row in detail.

Where do FMCG lines lose the most time?

• Short stops. Jams, fallen bottles and label misfeeds cleared in under a minute. Paper logs miss most of them. See our guide to micro stops.
• Changeovers. Format and flavour changes, often longer than the standard.
• Speed loss. The line runs below rated speed after a restart or on a hard SKU.
• Starved and blocked time. A machine waits because its neighbour stopped.

What should a mid size plant skip at the start?

Skip anything that needs data you do not have yet. Detailed scheduling needs real run rates per SKU. Full genealogy needs clean material master data. A plant that starts there spends months on setup before the first loss is fixed.

Also skip the idea that you need an IT team to start. Many mid size plants have one or two IT people, busy with the ERP. A light MES that connects to machines through the PLC, an IoT device or a camera keeps the IT work small. Our guide on OEE monitoring without a PLC shows how older machines get connected.

A worked example on one FMCG line

Sample line (illustrative numbers, not a customer): a juice line rated at 300 bottles a minute, 450 minutes of planned time a shift, a contribution of $0.10 a bottle.

• Run time = 450 minus 55 stopped minutes = 395 minutes, so Availability = 395 / 450 = 87.8%.
• With speed loss equal to 10 minutes, Performance = 385 / 395 = 97.5%.
• With 1% rejects, Quality = 99%, and OEE = 87.8% x 97.5% x 99% = 84.7%.

On paper, this line reported only the breakdown and the changeover. The 20 minutes of short stops cost as much as the changeover overrun, and nobody had counted them. Over 2 shifts and 250 days, the short stops alone are $300,000 a year on this sample line.

How should a mid size plant roll out MES?

1. Pick the line with the highest contribution per minute.
2. Agree a baseline and a decision date before you start.
3. Keep the reason code list short and plain.
4. Review losses in money at the daily meeting.
5. Move to the next line only when the first one uses the data every day.

McKinsey found in 2018 that only 30% of manufacturers had moved digital programs from pilot to scale. A pilot with an exit date and a clear owner avoids that trap. For the next step, read scaling MES from pilot line to plant.

Where Fabrico fits

Fabrico is a computer vision enabled Manufacturing Performance Platform. OEE and light MES come first. A machine connects through its PLC, a Fabrico IoT device or an AI camera, so the machine itself needs no PLC. Fabrico works in the ISA 95 Level 2 to Level 3 space; it is not an ERP and does not replace Level 4.

• Automatic downtime logging, with OEE live by line and shift.
• The operator confirms the stop reason in one tap, and where a camera watches the machine, the clip stays as evidence.
• Losses priced in money and ranked, so the costliest stop rises to the top.
• One view across plants for groups with several sites.
• A work order with its cost to the right technician when a stop is a breakdown, as a side benefit.

Named results: at Ficosota, factory wide OEE went from 53.1% to 59.6% and good output rose 23.2% a month; ABB reports 20% less downtime. You start on one line, with a baseline and a decision date agreed in advance. There is no free plan and there are no tiers: each plant gets a quote.

See how it works on our computer vision OEE and MES page.

Frequently asked questions

Do mid size FMCG plants need an MES?

Most need the performance part of MES: downtime, OEE and changeovers. Fewer need batch records or detailed scheduling at the start.

What is the best MES for FMCG?

The one that logs stops automatically on fast linked lines, separates starved and blocked time, and ranks losses in money. Check those three in any demo.

Can an MES work with old FMCG machines?

Yes, if it can read signals from an IoT device or a camera when the machine has no usable PLC.

How do I justify MES in a mid size plant?

Price lost minutes at contribution per minute of line output, then count the minutes you expect to recover on one line. Agree the method with your controller.

Should MES replace our ERP production module?

No. ERP plans and books; MES shows what happens on the line minute by minute. They work side by side.

See your FMCG line in a demo

Bring one line and a week of shift reports. We will show the stops, changeovers and speed loss the reports miss, priced in money.

Request a demo · Contact us