Foundational Modules Roadmap
The Data Model Engine is on the roadmap: a Module you'd configure yourself. Today mode40 builds your plant model with you, and every Module reads it.
Plant hierarchy
Your plant is held as company, site, area, line and asset, set up by mode40 during implementation. A line always sits inside an area, and an asset always sits on a line, the way Line 3 sits inside Packaging.
Routing and recipes
Routing, product recipes and the bill of materials sit in the same fixed model as your plant, set up with mode40 during implementation. A plan reads both the path an order takes and the parts it needs.
Sites
A second site takes the same shape as the first: another branch of the same model. What differs at a site is configured at that site, kept out of the shared model.
Entity types
Sites, areas, lines, assets and orders are record types mode40 fixes for you, and you fill them in through site configuration. Add a custom field in Form Builder. Build a custom screen in Screen Configurator.
Data contract
Before the first tag arrives, you and mode40 agree the model for each machine type: the signals it must send, and the tag path each reading lands on. Every asset sends at minimum an in count, an out count, a reject count and a state. The readings are stored in the Historian.
Build status
You can’t switch on or configure a Data Model Engine yourself today. The plant model, routing and recipes, tag contract and one installation for every site all work today, set up by mode40. A Module your team runs directly is design intent, and its shape may change before it’s built.
Not as its own Module. Today mode40 sets up your plant model during implementation, and every Module reads it.
It’s part of one. The Singularity as a whole is the digital twin of your operation, and this is the model underneath it. Today it’s the fixed model mode40 sets up with you: the hierarchy, assets, routing and recipes, read by every Module.
No, the record types are fixed. Form Builder covers the fields you add, and Screen Configurator the screens.
An in count, an out count, a reject count and a state of running, idle or faulted. Everything else is agreed per machine type.
No. The model for each machine type is agreed during implementation, against the tags that machine actually publishes.
It's on the roadmap. Today mode40 builds your plant model with you during implementation.
We use cookies to understand how the site is used and to connect form submissions to earlier visits. No analytics or marketing cookies are set until you choose. Privacy Policy