MES Modules You Actually Need: A Short List for Real Plants

Key takeaways

• Most plants use four MES modules every day: data collection, downtime and OEE, shift reporting and changeover tracking.
• Scheduling, batch records and genealogy matter only when your products or rules need them.
• Choose modules by the losses on your lines, not by a vendor feature list.
• A module nobody opens after go live is a cost, not a feature.

The MES modules most plants actually need are data collection, downtime and OEE tracking, shift reporting and changeover tracking. Everything else is useful only when a specific rule, customer or product demands it.

This guide is for plant managers and engineers writing an MES shortlist. Fabrico, a light MES built around OEE and downtime, covers the daily core; we list the other modules honestly so you can see where each one belongs.

What MES modules exist?

The MESA model, now with ISA, defined 11 MES functions in 1997, among them data collection, performance analysis and maintenance management. ISA 95 Part 3 groups Level 3 work into four areas: production, quality, inventory and maintenance. Vendors package these into modules with their own names, but the list is similar everywhere.

Which modules do plants use every day?

The first three are where the daily value sits. They turn machine signals into a list of losses that a team can act on before the next shift.

Why start with downtime and OEE?

Because it is where the lost money is easiest to find. OEE multiplies Availability, Performance and Quality, so it shows stops, slow running and rejects in one number. Most plants score closer to 60% than to the 85% that Nakajima (1984) called world class, and short stops and speed loss hide inside Performance. A downtime module that logs each stop makes that hidden time visible. Our guide to operator friendly reason codes covers the part that makes the data usable.

Which modules sit idle after go live?

• Scheduling in plants with few products and stable runs. Planners keep their spreadsheet.
• Labour tracking where it duplicates the time and attendance system.
• Document control when the quality system already does it.
• Advanced analytics that nobody has time to open.

One industry survey found that 43% of manufacturers do not effectively use the data they collect. Buying fewer modules and using all of them beats buying many and using two.

A worked example: choosing modules by loss

Sample plant (illustrative numbers, not a customer): a household products plant with 3 lines, 450 minutes of planned time a shift, 2 shifts.

Short stops and changeovers make up 33 of the 49 lost minutes, or 67%. The plant starts with downtime, OEE and changeover tracking. Line quality checks come next. Scheduling, at 2 minutes, is not worth a module yet.

Who should own each module in the plant?

A module works only when one person owns it. Give each one a named owner before go live, and write down what that person checks every day.

• Downtime and OEE: the production manager, who runs the daily loss review.
• Changeover tracking: the line lead or process engineer, who keeps the standard time per format pair.
• Shift reports: the shift supervisor, who signs off the report before handover.
• Line quality checks: the quality lead, who sets the limits and reviews holds.
• Reason codes: one person for the whole plant, so the list stays short and the same on every line.

If you cannot name an owner for a module, that is a strong sign the plant does not need it yet. Leave it out and revisit it at the next review.

How do you check a module list in a demo?

1. Ask the vendor to show each module on a real line, not slides.
2. Ask who uses it every day and for what decision.
3. Ask what data it needs and who keeps that data clean.
4. Drop any module that has no daily user in your plant.

Our guide to light MES vs OEE software helps if you are comparing tools of different sizes, and MES implementation cost, time and team covers the effort behind each module.

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 the daily core on our light MES page.

Frequently asked questions

What are the core modules of an MES?

Data collection, downtime and OEE tracking, and reporting. Changeover tracking and line quality checks are close behind in most plants.

Is scheduling a must have MES module?

Only in plants with many routings or constant resequencing. Stable plants often plan well in the ERP or a spreadsheet.

Which MES modules can wait?

Anything no current loss calls for. Many plants add a maintenance link later, so a breakdown becomes a work order with its cost, tied to the downtime data.

How many MES modules should I buy at the start?

As few as your losses require. Start with the core, then add modules when a loss or a rule calls for one.

What is the MESA 11 model?

A 1997 list of 11 MES functions from MESA, now with ISA. It is a useful checklist, not a list you must buy.

Check your module list in a demo

Bring one line and your shortlist. We will show which modules your losses actually need.

Request a demo · Contact us