Muvia Industrial · Industrial IoT
Your machines tell the business what they are doing.
An edge node connects to the PLCs you already have, reads the machines’ signals and brings them to the cloud: stops, energy use, states and alarms. If the network drops, it holds them and sends them when it returns.
- Siemens S7
- OPC UA
- Modbus TCP
- Also on Raspberry Pi 4
What changes on the plant floor.
Scenes that happen every week, with the same cause: the machines know what happened, the business does not.
The stop found at shift change
Today the line stops at night and you find out in the morning, rebuilding the cause from memory.
With Muvia Industrial the PLC reads the stop, with start and end. An alarm tells whoever needs to know, and the register keeps who took it over.
The energy bill nobody can split
Today one bill arrives for the whole plant. What each line uses stays an estimate.
With Muvia Industrial meters and network analysers are read line by line: energy use split by shift and by part.
The batch the customer sends back
Today to understand how it was made, you cross-check logbooks, sheets and memories.
With Muvia Industrial every batch has its process history: temperatures, pressures, times. You answer with data.
The service call with no data
Today the technician leaves without knowing how the machine ran and which alarms it raised.
With Muvia Industrial the machine carries an edge node: service sees what it did and which alarms it raised before even setting off.
From the PLC to the dashboard, in three steps.
- 01
Install the node
With one command, from a USB stick, or pre-staged. It runs on Debian or Ubuntu, on an industrial PC or a Raspberry Pi 4.
- 02
Connect the machines
Pick the driver and the signals to read. Signals can be declared before the machine is even installed.
- Siemens S7
- OPC UA
- Modbus TCP
- SQL Server
- SEW-Eurodrive
- 03
Use the data
Wall dashboards on the floor, alarms with a register and ownership, shift reports. Calculations can run on the node, in Python too.
If the network drops, the node keeps going.
On a plant floor the connection is not always good. The node is built for that.
- It holds the data
- When the cloud is unreachable, the node keeps the data and sends it when the network returns.
- A console on site
- The technician sees and configures the node from the floor, even without the cloud.
- Cellular networks too
- The node recognises cellular links.
- The fleet under control
- The state of every node and driver, and an alert when a node goes offline.
For those who run plants and those who build them.
Plant and maintenance
Know what is happening on the line, as it happens.
- Stops read from the PLC with start and end, the cause classified in the register
- Alarms with ownership and classification
- Energy use by line, by shift, by part
Machine builders
Every machine sold, connected.
- A node on board every machine
- Each customer has their own company, separate from the others
- Service follows the whole fleet with a single login
Frequently asked questions
Siemens S7 and OPC UA, read and write; OPC UA also by subscription. Then Modbus TCP, SQL Server tables read at intervals, and SEW-Eurodrive drives. A simulator lets you try it without machines.
The node keeps the data in a local buffer and sends it when the connection returns. The local console keeps working without the cloud.
Debian or Ubuntu, on amd64 or arm64 processors including Raspberry Pi 4, with Docker. It enrols with a token: one command, a USB stick or a pre-staged node.
Yes. The node runs catalogue functions and Python functions, including ones that use an ONNX or joblib model, before sending data to the cloud.
Machine data lands in the same engine: stops and energy use cross with orders, batches and quality in one query.
Let’s start from one machine.
Tell us which PLC you have and what you would like to know. In the demo we read the signals you need.