The industrial monitoring software that connects machines and systems
Talk to your plants. Meddle reads the data from your machines’ PLCs and sensors and combines it with the data from your ERP and MES. Then you ask in plain language how much a line consumed or why OEE dropped, and you get the number, the chart and the action to take. With your approval, Meddle also writes the parameters to the machines.
Example questions and answers about plant data
- Which machine consumed the most energy this week?
- The GP800 extruder is the most energy-hungry machine of the week. GP800 consumption: 4,812kWh. of the total: 34%. vs 7 days ago: +18%. kWh per machine · this week: GP800 4,812, GP600 3,120, Oven 2 2,740, Compr. 1,980, Packag. 1,290. Set an alert above this threshold
- Why did Line 2’s OEE drop yesterday?
- The drop is concentrated in the early afternoon: micro-stops on the filler. OEE yesterday: 63%. vs average: −12pt. micro-stops: 41min. OEE % · by time slot: 08 79, 10 74, 12 58, 14 62, 16 71. Open the micro-stop analysis
- How much did the last unplanned stop cost?
- The last stop on Line 3 cost around € 2,140. estimated cost: € 2,140. duration: 47min. plant: Line 3. € · cost breakdown: Output 1,520, Energy 380, Restart 240. See the downtime history
- Which plants are stopped right now?
- Right now 2 plants out of 14 are stopped. The most critical one is Line 3. plants stopped: 2 / 14. Line 3, stopped for: 47min. Oven 2, stopped for: 6min. minutes of downtime · now: Line 3 47, Oven 2 6. Notify me when it restarts
- ‹ 20 minfrom connection to first answer
- 0 dashboardsto build or maintain
- 1 platformfor OT and IT, no lock-in
The analyses you redo every week, already done.
Any question can become a worksheet: it refreshes itself, runs on every plant and stays shared with your team.
Anomalies find you, not the other way round.
Thresholds, drifts and downtime detected automatically on every tag, with the context to decide and the action to step in.
Ask a question. The plant answers.
Energy, downtime, OEE: ask in plain English and get a number, a chart and a suggested action. Without building anything.
From numbers to charts. In an instant.
Every answer becomes a chart you can read at a glance: trends, comparisons and consumption, always up to date and ready to share.
Where time gets lost today
The data already comes out of the machines. To turn it into a readable number, someone exports the CSV, pastes it into Excel and rebuilds the shift by hand. The Monday report tells you about last week, and you found out about Thursday’s downtime on Monday.
Downtime gets added up by hand
| tag | value | time |
|---|---|---|
| TT-104 | 82.4 °C | 06:14 |
| GP800_kWh | 4812.0 | 06:14 |
| MTR-07_rpm | 1450 | 06:15 |
| L2_state | STOP | 06:21 |
Four thousand rows per shift. Someone adds up the downtime by hand, on Monday morning.
The question and the answer
How much did the last stop cost?
The last stop on Line 3 cost around € 2,140, in 47 minutes. Production 1,520, energy 380, restart 240.
Same question, same data, no export. The answer arrives while the line is still down.
How Meddle works
- 01
Connect
The connector is set up once, during onboarding: OPC-UA, Modbus, S7, MQTT, databases, ERP. From then on the data comes in on its own, with no intervention.
- 02
Understand
Raw values become OEE per line, consumption in euros and automatically detected anomalies.
- AI
Ask
Ask your question in plain language and get the number, the chart and the action to take.
- ACTIONS
Act
With your approval, Meddle writes the new parameters straight to the machines.
A different number for every role
Production
How long yesterday’s downtime lasted and how much OEE it cost.
Micro-stops counted by time slot, without waiting for the report.
DiscoverEnergy manager
How much each machine consumes, in kWh and in euros.
Consumption by department and by shift, with an alert when a machine goes past its threshold.
DiscoverIT and OT
Standard protocols and data in Europe. No lock-in.
No hardware to install, no changes to the plant network.
Discover
Meddle also works for quality, with records filled in automatically, and for anyone who looks at downtime costs across the whole plant.
What Meddle connects and where the data lives
- Any machine (OT) and IT system, no lock-in
- Data in Europe
- NIS-2 ready
44 documented connectors, from field protocols to databases, ERP and message queues. The data stays in Europe, and it stays yours.
All the technical power beneath the surface. You just see the conversation.
Where Meddle is already at work
- 7%
less energy
At a water utility: Meddle switches the pumps on by reading hourly energy prices.
- 20%
shorter lead time
On a manufacturing line, with an alert on the bottleneck as it forms.
- +90%
higher chance of catching a failure
In a chemical plant, with the process state read in real time.
Three plants in production. We publish their names once our customers give us the go-ahead.
Frequently asked questions
Everything you need to know before connecting your first machine.
Talk to the teamMeddle is software that connects to factory machines, collects production data in real time and combines it with the data from your business systems. The connection to the PLCs is made in software, with no additional hardware.
No. Meddle connects to PLCs and industrial systems through software protocols such as OPC-UA, Modbus and MQTT. No physical gateways or additional sensors are needed: the Ethernet connection you already have on the shop floor is enough.
Yes. Most PLCs built in the last fifteen or twenty years support at least Modbus, which is enough for data collection. For machines without digital interfaces, a serial-to-Ethernet adapter bridges the gap.
The first machines are connected and their data is visible within hours. A pilot on five machines, with dashboards and alerts, is done in two or three weeks.
Yes. Meddle connects the machine to your ERP and documents the data exchanged, which is the technical requirement interconnection hinges on. The application is handled by your consultant or accountant: Meddle provides the connection and the documentation, it does not file the application.
Pricing depends on scope: number of plants, sources and users. You never pay per tag or per data point. You start with one line, not the whole plant, and a two-to-four-week pilot always comes before any commitment.
Ideas from the connected factory
IoT Energy Monitoring for Factories: Cut Costs and Meet Sustainability Goals
Learn how IoT energy monitoring reduces factory energy costs by 15-30% with peak demand management and idle detection.
Read the article
OT/IT Convergence: A Practical Guide for Manufacturing Teams
Learn how to bridge Operational Technology and IT systems in your factory with a practical 4-step roadmap.
Read the article
Industrial IoT for Small Manufacturers: Start Smart, Scale Fast
Learn how small manufacturers can start with IIoT in 2 weeks with a 5-machine pilot and see 3-5x ROI in year one.
Read the articleBook a free demo
Thirty minutes. We show you Meddle on a plant similar to yours and answer your IT team’s technical questions.