Manufacturing and machineryMuvia Industrial
The plant graph
Site, lines, machines and components become models and assets nested inside one another, with manuals and reports next to the machine. From the machine, the Project Map leads to the datasets and dashboards that use it, and Athena answers by reading its documents.
Illustrative scenario: it describes a typical case, not a customer project.
A machine's data is everywhere except next to the machine.
The signals are in the tags, the manual in a shared folder, the service reports in email, and every dashboard names the machine its own way. When an extruder stops, the first thing anyone does is search.
In Muvia Industrial the plant is a graph: types of machine are models, machines are assets in their place in the tree, and each one carries its variables and documents. From there you reach every dataset and dashboard that concerns it.
- Who it's for
- Maintenance and engineering managers, shop-floor technicians and anyone who has to give machine data its context.
In Muvia, step by step
Real product screens, recorded on a project with sample data.
The video · Site, lines, machines and components become models and assets nested inside one another, with manuals and reports next to the machine. From the machine, the Project Map leads to the datasets and dashboards that use it, and Athena answers by reading its documents.
What you get
- Every piece of data has its machine
- Signals, documents and dashboards are found starting from the machine, not from a tag name.
- The manual is a question away
- Athena answers from the machine's documents: nobody on the floor has to hunt for the right folder.
- One model, many machines
- A model's variables apply to every asset of that type: a new machine finds them ready.
- Changes without surprises
- The Project Map tells you which datasets and dashboards use a machine before you touch it.
For the technical team
How it is built in Muvia
- 1
Draw the models
In Plant you define the types of machine as models, nested inside one another: the site contains the lines, a line the extruders, an extruder its components. Each model declares its variables.
- 2
Put each machine in its place
Assets are the real machines, in the site's tree. Their variables link to the node's tags or to the fields of a certified dataset.
- 3
Attach the documents
The manual goes on the model, the service report on the asset. Athena reads them and answers questions such as “how do I clean the die on extruder 2?”.
- 4
Follow the data to the dashboard
From the asset, the Project Map shows the linked variables, datasets and dashboards: before you change a machine you know what depends on it.
- The data it needs
- Types of machine and their components: extruder, screw, die, chiller
- The site's machines, line by line, from an Excel file
- Manuals and service reports as PDFs
- The lines' signals, linked to each asset's variables
More cases in this line
All use cases- 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.
- The control chart that warns you firstWeighings from the checkweigher become an X̄-R chart with 3σ limits and the Western Electric rules, recalculated at every shift change. A worn nozzle shows up hours before the scrap does, and Cpk shift by shift tells you where to act.
- Connected machines for machine buildersEvery 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.
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.