Muvia IndustrialModel
One place that says where each value comes from
An asset is one real entity as the Lab knows it: it follows a model, fills in its fixed values and says, for each variable, the tag it is read from. Everything downstream reads by meaning, so a renamed tag is dealt with here, once.
- Plant North
- Line 2
| Variable | Tag |
|---|---|
| net_revenue | sales.net_revenue |
| orders_total | sales.orders |
| discount_pct | sales.discount |
| returns_pct | Not bound |
Bind 1 unbound variable
Illustrative example
What an asset gives you
Built on a published model
The asset takes its variables and fixed values from a published version of a model. Give it a name, a parent, labels and links to a dashboard, another asset or a web address.
Tags bound once
Muvia proposes a tag for each variable among those the project has received. You keep, change or empty each one, choose the node it comes from and bind. A tag that never sent data is saved anyway, with a warning.
Rename a tag, keep the history
When the source starts sending a variable under a new name, record the rename with its date. The variable reads the old tag up to then and the new one after, and every query that reads it follows without being edited.
What reads it, derived
The Datasets and Dashboards tabs list what reads the asset, worked out by Muvia and never typed by hand. Deleting it shows what reads it first.
How you use it
- 01
Create the asset
Lab › Assets › New asset, or Create asset on a published model. Choose the model, the parent and fill in the fixed values.
- 02
Bind the variables
The asset opens on Variables with the bind panel ready. Check each proposed tag and node, then Bind. The header counts the variables bound out of the total.
- 03
Read it by meaning
Queries and notebooks read the variable, not the tag. When a tag changes name, use Rename tag with the date it took over.
In detail
- Fields
- Name unique in the project, model, description, parent, labels, links, and the model's fixed values.
- Variables tab
- Category (dynamic or event), unit, tag or not bound, node, former tags with their end date, limits, Rename tag.
- Other tabs
- Datasets, Dashboards, Documents (its own and its model's, with whether Athena has indexed them) and Athena.
- Components
- An asset can have components. It cannot become its own parent, and is not deleted while it has components.
- Permission
- Assets use the Datasets permissions: Editor › Datasets › Read to read, Write to create, change and delete. Choosing a model also needs Data Model › Data Model › Read.
- What it is bound to
- The tags the project has received, with their node. An asset is a place or unit of the model, not a record that carries its own data.
Frequently asked questions
Yes. An asset is built on a published version of a model, and only published versions are offered when you create one.
Record the rename on the variable with the date it started. History stays whole, and queries that read the variable need no edit. A rename dated in the past may leave saved tables to recompute, which the panel lists.
Delete first shows what reads the asset, queries, datasets and what lies downstream. It is refused while the asset has components; the data its tags sent stays stored.
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.