Muvia Industrial
How Muvia Industrial reads your machines.
An edge node on the shop floor reads your PLCs and line databases, processes close to the machine and sends the data into the same engine that holds orders, purchasing and quality. From there you watch it, join it, and build alarms and reports on it.
- Field protocols
- Siemens S7, OPC UA, Modbus TCP, SQL Server, SEW-Eurodrive.
- Ordinary hardware
- Debian or Ubuntu, amd64 or arm64, Raspberry Pi 4 included.
- One engine
- Machines next to orders, purchasing and quality.
Muvia Industrial
From the field to the cloud.
The edge node sits on the shop floor: it reads the machines, processes, keeps the data if the cloud is gone and brings it into Muvia.
Field
Edge node
Fleet and cloud
Protocols and drivers
Each driver runs on the node, reads the variables you pick and turns them into named tags. These are the protocols the node speaks today.
| Protocol | What it reads | Read or write | Notes |
|---|---|---|---|
| Siemens S7 | What it readsData blocks, inputs, outputs and markers, by address. | Read or writeRead and write | NotesAlso reads structures defined on the PLC. |
| OPC UA | What it readsThe nodes of an OPC UA server. | Read or writeRead and write | NotesAt regular intervals, or by subscription when a value changes. |
| Modbus TCP | What it readsRegisters and coils of PLCs, meters and instruments. | Read or writeRead | NotesOver TCP networks only, not serial lines. |
| Microsoft SQL Server | What it readsNew rows in a table of the line database. | Read or writeRead | NotesFor systems that already write to a database: SCADA, test benches, traceability. |
| SEW-Eurodrive | What it readsMonitoring data and parameters of the drives. | Read or writeRead | NotesReceived over HTTP from SEW's IoT Suite. |
| Simulator | What it readsTest signals generated on the node. | Read or writeRead | NotesTo build dashboards and alarms before the line is connected. |
A write to the PLC starts from a flow. In trial mode the flow really runs, but the command is recorded instead of sent: you see what it would do without touching the machine.
Your PLC is not in the table? Many controllers already expose an OPC UA server or a Modbus TCP interface. Ask an engineer before you start.
The edge node
The node is a computer on the shop floor, close to the machines. It needs no special hardware: an ordinary Linux machine will do.
What it runs on
- Operating system
- Debian or Ubuntu
- Architecture
- amd64 or arm64
- Boards
- Raspberry Pi 4 supported
- Software
- Docker containers: drivers, node agent, processing runtime
From the box to the line
- 1
Install
With one command on the machine, with a USB stick that installs on its own, or receive the node already prepared in the lab.
- 2
Enrol with a token
On first boot the node introduces itself to the cloud with your company's token and appears in your fleet. Nothing is configured by hand on site.
- 3
Configure drivers from the cloud
Pick protocol, addresses and tags in Muvia. The configuration reaches the node and data starts flowing.
Close to the line
The node does more than forward. It computes, holds data when the network drops, and can be managed without the cloud.
- Edge Functions
- Compose a graph of catalogue functions and Python functions you write: averages, filters, conversions, machine logic, even scikit-learn or ONNX models your team trained. It runs on the node, before the data leaves.
- Local console
- A password-protected web interface on the node: status, logs, driver configuration, latest values, start and stop, updates. It keeps working when the cloud is out of reach.
- Local buffer
- If the link to the cloud drops, the node keeps data in a local buffer and sends it when the network is back.
- Cellular links
- The node knows when it is on a 4G SIM: it keeps the connection alive through the carrier's NAT and reports how much the link is used.
The fleet, node by node.
Each node sends a heartbeat at an interval you choose, from 5 to 300 seconds. In Muvia you see which nodes answer, what state each driver is in, and when something stops.
- Node heartbeat
- Each node reports that it is alive, at the interval you set.
- State of every driver
- Connected, waiting for a connection or in error: driver by driver.
- Alarm when offline
- A node that stops answering raises an alarm.
- Explicit updates
- No node updates itself. You decide which one to update, and when.
For machine builders.
You sold the machines, but their data stays on your customers' shop floors. With a node on board, you follow them after delivery: how they run, which alarms they raise, when a node stops answering.
- Each customer, a separate company
- Each customer has its own users, permissions and database. One customer never sees another's data.
- One login for every customer
- Muvia links your service engineer to your customers' companies: they move from one to the next without signing out, with the permissions they hold in each.
- A space the customer recognises
- Each company can have its own logo and colours, and the dashboards you prepare for that customer.
And then, all of Muvia.
Field data does not end up in a separate system. It lands in the same engine as the company's data, under the same permissions and the same activity log, and joins it with a query.
- Shop-floor dashboards, on a wall screen in kiosk mode too
- Threshold alarms with a register: who took them on, how they were classified, the notes
- Scheduled PDF reports, at the end of a shift or on Monday morning, sent by email
- Athena answers questions about machine data and shows the query it ran
- Line data joined with orders, purchasing and quality
Example query
SELECT o.customer,
count() AS pieces,
avg(p.cycle_time_s) AS avg_cycle_s
FROM press_line2 AS p
JOIN erp_orders AS o ON o.batch = p.batch
WHERE p.ts >= today() - 7
GROUP BY o.customer
ORDER BY pieces DESCTell us which machines you run. We'll tell you how to read them.
PLC brand, protocol, how the floor is connected: with those three answers, in a demo with one of our engineers, we show you how Muvia Industrial puts line data next to the rest of the business.