OEE monitoring for packaging lines, without touching the PLC

The data you need is already on the line. It's just locked in.

Your packaging machines already produce much of what you'd need to improve them: production speed, cycle counts, good and reject counts, run time, downtime and status. The trouble is that this data is often difficult to access outside the machine control, especially without changing a validated PLC program or commissioning a custom integration. So teams fall back on manual logging, patchy reports, or a PLC project nobody wants to touch.

Keep the machines. Connect the data.

Perinet leaves your machines and their controls exactly as they are. Single Pair Ethernet Smart Components capture the relevant signals from the packaging line and place them on an IP-native network, then carry them to a periMICA edge computer on site. There the signals become a live OEE view: availability, performance and quality, with reports for longer-term analysis.

Because the data is made available through open, standard interfaces, your existing IT and analytics tools can use it directly, with no proprietary middleware in between.

Packaging line filling and sealing chocolate trays

One network for the line, not an integration project per machine.

The usual assumption is that line-wide OEE means integrating every machine: a PLC project per asset, a protocol conversion per vendor, and a validation cycle for each one. On a mixed line with machines from four or five builders, that is where most OEE projects stall.

You don't need to network each machine to monitor the whole line. Perinet reads the signals the machines already produce, using periNODE adapters that sit alongside the equipment rather than inside its control logic. Each adapter puts its signals straight onto a shared Single Pair Ethernet network, so the line is covered by one network with one set of open interfaces, not by a separate integration for every asset.

The practical difference is what happens when you add the next machine. Connecting a filler from one builder and a case packer from another is the same job twice, not two different projects. Nothing on the PLC side changes, so nothing needs revalidating.

Older machines are covered the same way. If a signal is available at a terminal, a relay contact or a 4-20 mA loop, it can go on the network. Age and brand of the machine matter far less than whether the signal exists.

The basis

Perinet

Single Pair Ethernet Smart Components put machine signals directly on an IP-native network, and the periMICA edge computer handles local data and dashboards on site.

The realisation

Zentinel MDS

Our solution partner builds on that foundation, adding the firmware and customisation that tailor it to your line, which is what lets a deployment go in during normal operation, in hours.

Proven on a real line

A chocolate manufacturer wanted real-time OEE across its packaging lines. Working with solution partner Zentinel MDS on the Perinet platform, the relevant machine signals were connected and made available to an on-site OEE application. The system was installed in a few hours during normal operation, with no changes to the machine controls and no pause in production.

The connected signals (production speed, good and reject counts, run and downtime) were used to create a live view of availability, performance and quality, with reports for longer-term analysis. Production problems can be recognised and rectified as they happen, rather than surfacing in a report a week later.

Where it also fits

Assembly lines: efficiency of consumer-goods production, from electrical appliances to furniture.
Textile production: running times and quality on weaving and printing machines.
Logistics centres: availability of automated sorting systems.
Paper industry: efficiency in cardboard and packaging materials.
Plastics processing: OEE for injection moulding and extrusion.
Electronics production: performance of automated assembly systems.

How this compares with other ways of getting OEE data

There are several established routes to OEE data. The right one depends largely on what infrastructure you already have and how widely you want to use the data.

Integrating through the PLC. The most complete data, since everything the control system knows becomes available. It also means engineering work on a validated program, vendor involvement per machine, and usually a production stop. Good where you own the machine program and are already planning changes. Difficult as a retrofit across a mixed line.

Per-machine monitoring appliances. Self-contained units wired to a signal on each machine. Quick to deploy and well proven for single-asset visibility. The data tends to stay inside each vendor's own platform, so line-level analysis and getting the data into your own IT systems can require extra work.

OEE software platforms. Strong at dashboards, reporting and shop-floor workflow. They still need something underneath to capture the machine signals, which is the part this page is about. Many customers run a platform of their choice on top of a Perinet foundation.

Where Perinet fits. Perinet supplies the connectivity layer: signals from existing machines placed on an IP-native network and delivered over open interfaces such as MQTT and REST. The machines keep running as they are, installation happens during normal operation, and the data arrives in a form your own analytics and IT tools can read directly. Together with our solution partners, that becomes a working OEE deployment. Where you already have an OEE platform you like, we connect the data to it rather than replacing it.

When another approach may be better. If the data you need exists only inside the PLC program and is not available as a physical signal, PLC integration may still be the right approach. And if you only need to monitor one or two isolated machines with no requirement to integrate the data into wider IT systems, a standalone monitoring appliance may be simpler.

Dairy packaging line filling and capping milk bottles

Bottling line filling juice bottles on a conveyor

Frequently asked questions

The three OEE factors: availability (running versus downtime), performance (actual versus rated speed), and quality (good versus reject counts), captured live from the machines and combined into a single effectiveness score.

You can cover the whole line without an integration project per machine. Adapters read the signals each machine already produces and put them on one shared network, so no machine control is modified and no PLC program is touched. Adding another machine repeats the same step rather than starting a new project.

periNODE adapters read the existing machine signals (speed, unit counts, run and downtime) and put them straight on the network. Installation takes hours and doesn't touch the PLC or interrupt production.

Yes. Because the signals are read outside the control system, the machine's brand, age and protocol matter much less than whether the signal is physically available. Mixed lines are the common case.

Yes. The modular adapters extend to more machines or lines without interrupting operations, and the same approach applies to assembly, textiles, plastics, paper, logistics, and electronics production.

Captured data is stored centrally in an SQL database and shown as availability, performance and quality dashboards, with reports for detailed analysis.

No. Data is delivered over open standard interfaces, so it can go into your existing OEE platform, historian, or analytics stack. Our solution partners can also build the application layer if you would rather have it delivered as a whole.

Exploring OEE monitoring in packaging?

Tell us a little about your application. We’ll make sure your enquiry reaches the right Perinet contact or partner.