Connected machines for machine builders
Every machine you sell carries a Muvia node, and every customer gets a company of its own, kept apart from the others. Your service team follows the whole fleet with one login, and each customer gets dashboards and reports on their machine.
Illustrative scenario: it describes a typical case, not a customer project.
The machine leaves your plant, and its data stays with the customer.
Machine builders know exactly how a machine behaves at acceptance testing, and much less about how it runs after delivery. Every service call starts with a phone call and a photo of the operator panel.
With a node on board, the machine talks to you: you see whether it is on, whether the drivers are reading, how it is being used. And the customer gets more than the machine: their own data, already organised, in a dashboard and a report you hand over.
Each customer lives in a separate company, with its own database and credentials, so one customer's data never mixes with another's.
- Who it's for
- Machine and equipment builders: service and after-sales, engineering, product management.
What you get
- Service that starts from data
- Before leaving, the technician knows whether the node is online, which drivers are reading and what the machine did in the last few hours.
- One more service to sell
- Dashboards and reports on the machine, in the customer's logo and colours, become part of what you offer alongside it.
- Separate customers, one login
- Each customer sees only their own data; your team follows all of them without juggling accounts and passwords.
- The next machine is shaped by real use
- How machines actually run in the field reaches your engineers as data, not as stories from a site visit.
For the technical team
How it is built in Muvia
- 1
Prepare the node in your workshop
The node is pre-staged in the lab with an enrolment token, or installed from a USB stick, and reaches the customer ready to connect. It runs on Debian or Ubuntu, amd64 or arm64, Raspberry Pi 4 included, and works over a 4G SIM too.
- 2
A company for each customer
Muvia opens a company for each customer, with its own database and credentials, its logo and its colours, and links your service team to each one. Your service team then switches from one customer to the next with the same login, without signing out.
- 3
Watch the fleet
A heartbeat every 5 to 300 seconds, the state of every driver, and an alarm when a node goes offline. On site, the technician opens the node's password-protected local console and sees logs and latest values even without the cloud.
- 4
Hand dashboards and reports to the customer
In the customer's company you build the machine dashboard and the report notebook, which becomes a PDF emailed to their users every month. The customer sees only their own data.
- 5
Use the data to improve the machine
Running hours, cycles, recurring alarms: with saved queries and dashboards your engineers see how each machine is really used and, within what you agreed with the customer, pull the data into their own tools through the read-only REST API.
SQL query
SELECT toDate(ts) AS day,
countIf(state = 'RUNNING') / count() AS running_share,
max(cycle_count) - min(cycle_count) AS cycles
FROM machine_tags
WHERE ts >= toStartOfMonth(today())
GROUP BY day
ORDER BY day- The data it needs
- Process variables and states from the on-board Siemens S7 PLC or OPC UA server
- Status and parameters of the SEW-Eurodrive drives
- Energy readings from an analyser on Modbus TCP
- Node heartbeat and the state of every driver
More cases in this line
All use cases- Anomalies and predictive maintenanceVibration, temperature and current read from the PLC become a deviation from normal, a health index and, if you want, a score from a model of your own, in the cloud or on the node next to the machine. When a signal drifts, an alarm goes off and maintenance hears about it.
- Energy use per line and per pieceMeters and power analysers read over Modbus TCP, joined with the pieces produced and the orders in the ERP: how much energy each line, each shift and each piece takes, with an alarm when consumption looks out of the ordinary.
- Process quality and traceabilityProcess parameters from the PLC, lots from the line database, orders and scrap from the ERP, all in the same engine. Every lot has its process history, and an alarm goes off when a parameter leaves its window while the lot is being made.
Tell 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.