Skip to content
RenoktaRenokta

Smart factory (MES)

Real-time monitoring of machine performance, production data and energy use.

Request a demo
A live process chart on the touch panel beside an injection moulding machine.

Measured point

OEE and availability

Renokta IoT Platform · Production line OEE

Live · --:--:--

Sample plant › Assembly lines

  • OEE

    76.5%

  • Availability

    85.5%

  • Output today

    6,533adet

  • Downtime today

    39dk

OEE and availability

OEEAvailability76.5 %

Target 85

OEE by line

  • Line 1 · Assembly83 %
  • Line 2 · Packing77 %
  • Line 3 · Press69 %
  • Line 4 · Paint82 %

Event feed

  • 0Critical
  • 1Major
  • 1Minor
  • 2Warning
  • Unplanned stop on Line 3 press: high vibrationOpen
  • Line 2 cycle time rose above targetOpen
  • Line 1 shift production counter was resetOpen

Sample screen. Values are simulated.

What is a smart factory (MES) system?

A smart factory (MES) system collects sensor and counter data from production machines and shows downtime, output and performance in real time. The goal is to see the state of the line without waiting for the end of the shift, and to calculate indicators such as OEE from data instead of manual notes.

MES software does not do the same job as ERP. ERP plans orders, stock and cost, while MES tracks what is happening on the shop floor right now. The two complement each other.

How does it work?

Sensors fitted to a machine or line send data to a gateway, and the gateway forwards it to the platform. The platform processes the data per machine and shift, shows it on a dashboard, raises an alarm when a threshold is crossed and writes it to a report.

  • Sensor: machine run state, temperature, vibration, counter pulse.
  • Gateway: collects data from field devices and passes it to the platform.
  • Platform: calculates downtime reasons, output and OEE.
  • Output: live dashboard, alarm notification and shift report.

Which quantities are measured?

  • Machine state (running, idle, faulted): to work out downtime and its frequency.
  • Production counter: for output and line speed.
  • Motor and bearing temperature: to catch overheating before a failure.
  • Vibration: to watch for imbalance and wear.
  • Energy use: to see consumption per machine and line.
  • Rejected units: for the quality part of OEE.

How is OEE tracked, and which method fits?

OEE is the product of availability, performance and quality. An OEE tracking system calculates these three from machine data. There are several ways to collect that data.

  • Manual logging: easy to start, but delayed and error-prone; downtime reasons are often forgotten.
  • Reading from the machine controller (PLC): rich data, but each machine needs connection and protocol work.
  • External sensors and counters: work on older machines without touching them; the data is limited to what the sensor sees.
  • Mixed setup: read the controller on new machines and use sensors on old ones.

Who is it for?

  • Plastics, metal and food plants running serial production.
  • Sites with machines of mixed ages that want to monitor them without replacing everything.
  • Production and maintenance managers who want to see downtime reasons and shift differences.
  • Plants that want to separate energy use by line.

How do alarms and notifications work?

Alarm thresholds are set for your process. When one is crossed, the platform notifies the right person through the chosen channel, the person acknowledges it and the event is logged. You can later see when a stop began, who saw it and how long it lasted.

If the network connection drops, device behaviour depends on the hardware used; the details are settled during the site survey.

Integration with existing systems

Data usually comes in over industrial protocols such as Modbus or OPC UA, over MQTT or through an API. Which interface is used is adapted to your machines, ERP software and needs. Pulling order and work-order information from ERP can be part of the same work.

Data privacy and security

The system collects machine and process data; collecting personal data about employees is not its default purpose. Access is limited through role-based permissions. If any use involves personal data, the data-protection assessment is made with your own privacy notice and legal counsel.

Installation and what we need for a quote

The process starts with a survey: we walk the line and agree on the machines to monitor and the indicators to track. A pilot follows on one line or a few machines, the data is verified, and then it is rolled out to other lines.

For a quote we need the number of machines, the quantities to monitor, the age and controller type of the machines, and your current ERP or software setup. You can reach us through the contact form.

Highlights

  • Live production dashboard

    Machine state, output and downtime are visible in one dashboard in real time.

  • OEE from data

    Availability, performance and quality are calculated from machine data, so manual logging is not needed.

  • Downtime reason log

    The start, duration and reason of each stop are recorded and compared by shift and machine.

  • Works with older machines

    Machines without a controller can be monitored with external sensors and counters.

  • Alarms and reports

    Threshold breaches are notified, events are logged and a shift report is produced.

Machine to dashboard: production

Counter, status and vibration inputs on the machines are collected over Modbus. The platform calculates OEE, logs downtime with its reason and sends alerts.

Machinecounter inputMachinestatus inputVibrationsensorCurrentsensorModbus fieldgatewayRenokta IoTplatformDowntimealertOEEdashboardShiftreport

An unplanned press stop

  1. The vibration sensor on the Line 3 press reads above normal and the status input reports that the machine has stopped.
  2. The platform logs the stop automatically; Line 3 OEE drops and stands out in the line comparison.
  3. A downtime alert goes to the maintenance team with the line, machine and vibration value.
  4. Once the fault is cleared, production resumes and the stop time and reason are added to the shift report.

The diagram shows the logic; names are examples.

Frequently asked questions

How does a smart factory (MES) system work?
Sensors and counters on the machines send data to the platform through a gateway. The platform calculates downtime, output and OEE, shows them on a dashboard and raises alarms when a threshold is crossed.
What is the difference between MES and ERP?
ERP manages planning data such as orders, stock and cost. MES tracks the live state of machines and production on the shop floor. The two systems can exchange data.
Which sensors and data are used?
Machine state, production counter, motor temperature, vibration and energy use can be monitored. The choice depends on the machine and the indicator you want to track.
Can older machines be monitored too?
Yes, machines without a controller can be monitored with external sensors and counters. Run state and output can be read without modifying the machine.
What determines the cost?
Cost depends on the number of machines and measurement points, the communication method and the need to integrate with existing ERP or PLC systems. A firm quote follows the survey.
Will it work with our existing ERP and automation?
Integration is adapted to your needs. Data can be exchanged through interfaces such as Modbus, MQTT and APIs; the right one is decided during the survey.
Who owns the production data and how is it protected?
The data is your own process data, and access is limited through role-based permissions. If personal data is involved, the privacy assessment is done with your own legal counsel.
How long does installation take?
It varies with the number of machines and the scope, and is settled during the survey. Typically a pilot starts on one line and the rollout continues after the results are verified.

Our solutions

Let's plan the right solution for you, together.

Request a demo