MES Without an IT Project: How Plants Start Small and Stay Safe

Key takeaways

• You can run the performance part of MES without a big IT project if you start with machine signals and OEE on one line.
• IT still signs off on network access, security and data ownership. Small is not the same as skipping IT.
• Older machines can be connected through an IoT device or a camera, so no PLC changes are needed.
• ERP integration can wait until the line data is trusted.

Yes, a plant can start MES without a big IT project. Begin with the performance layer: machine states, downtime reasons and OEE on one line, connected with devices that need no PLC changes and no ERP work on day one.

This guide is for plant and operations managers who want line data now but whose IT team is busy with the ERP. Fabrico, a light MES built around OEE and downtime, starts most plants this way. Below we show what stays small, what IT still needs to approve and where plants get stuck.

Why do MES projects turn into IT projects?

A full MES touches recipes, routings, materials, quality and the ERP. Each one needs master data, interfaces and testing. That scope is why MES has a reputation for long, costly projects. One industry survey asked 1,560 decision makers and found integration was the top buying requirement (44%) and security and compliance the second (43%).

The performance layer is different. It needs a signal from each machine, a list of reason codes and screens for operators and managers. None of that has to touch the ERP at the start.

What do you need to connect, and how?

Our guide to OEE monitoring without a PLC covers the second and third rows in detail.

What does IT still need to approve?

Small does not mean hidden. Bring IT in early with a short list, and the approval goes faster.

• Network access. Which devices join which network, and what traffic leaves the plant.
• Security standards. Ask the vendor how it handles IEC 62443 for its product and components.
• Data ownership. Who owns the line data and where it is stored.
• Users and logins. How operators and managers sign in, and who manages accounts.
• Cameras. In the EU, video at work has its own rules, and in Germany the works council has a say. Measure the process, never the person.

A worked example: one line, no ERP work

Sample line (illustrative numbers, not a customer): a bottling line with 5 machines. The filler and labeller have PLCs; the case packer and palletiser are older.

• Filler and labeller: states and counts read from the PLCs.
• Case packer and palletiser: an IoT device reads the signal light and a count sensor.
• Shrink wrapper: a camera watches the infeed, where most jams happen.
• Operators confirm each stop reason in one tap on a screen at the line end.
• ERP: no change. Orders are still planned and booked as before.

The first week shows 38 minutes of downtime a shift on paper and 70 minutes in the logged data. The plant manager now has a ranked list of losses without one ERP interface built. The next step, ERP integration, only starts once the line team trusts the numbers.

When do you need ERP integration?

When the line data is trusted and someone needs it in the ERP: for example, to book good counts against an order or to plan on real run rates. Start with a one way flow of a few fields. Our guide to OEE and ERP integration without heavy IT shows a simple first version, and our ERP vs MES guide covers who owns which data.

Mistakes plants make when they skip the IT project

• Hiding the project from IT, then getting blocked at the network approval.
• Connecting every line at once, so nobody owns the data on any of them.
• Building a custom spreadsheet or dashboard that only one person can maintain. See light MES vs spreadsheets.
• Starting ERP integration before the line data is trusted.

The status quo is the real competitor here: IoT Analytics reports that 54.4% of small and medium manufacturers still run on pen and paper or spreadsheets.

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.

Read more on our light MES page.

Frequently asked questions

Can I install MES without IT?

You can keep the IT work small, but not zero. IT should approve network access, security and data ownership before devices go on the line.

Do I need to change my PLCs to get MES data?

No. Where the PLC is hard to read or missing, an IoT device or a camera can provide the machine state.

Does MES need to connect to the ERP from day one?

No. Start with line data, then add a simple ERP link once the team trusts the numbers.

Is a cloud MES safe for a plant?

Ask the vendor about IEC 62443, where data is stored and what traffic leaves the plant. Your IT team should check the answers.

Who runs the MES if we have no IT team?

The operations team runs the daily use; the vendor supports devices and software. Name one owner per line.

Start on one line

Bring one line and your IT contact. We will show what connects, what IT approves and what the line data looks like.

Request a demo · Contact us