Unified Manufacturing Data Architecture
Tools
Hands-on tools for working with the framework: design your namespace, data model, and AI agents right in the browser, translate between the standards, and learn the architecture by playing.
Design & reference tools
Standalone workbenches that follow the framework's own order — Model → Name → Map → Govern → Act. The Common Data Model defines what things mean, the Unified Namespace gives those entities governed addresses, the Edge Node Planner maps the plant's real tags into those contracts and topics, the UDL and FDL guides plan storage, lineage, and evidence, and the Agent Designer defines the intelligence that consumes the governed foundation. The crosswalk and the reference pages keep the standards at hand while you work.
Common Data Model Designer
Define the canonical entities and contracts everything else builds on: give the shared entities of a site typed attributes and ISA-95/88 lineage, and connect them with relationships that read as sentences. Export JSON Schema, SQL DDL, Cypher, an RDF ontology, a data dictionary, or an entity catalog for the Agent Designer.
Open the designer → Step 2 · NameUnified Namespace Designer
Give the model's entities governed addresses: design an ISA-95-aligned Unified Namespace, build your enterprise → site → area → line hierarchy, validate the naming against the standard, and export a naming convention your teams can build to.
Open the designer → Step 3 · MapEdge Node Planner
Map the real plant into the governed design: paste the raw PLC tags and OPC paths a line actually exposes, bind each one to its UNS topic and data contract with validation and scaling rules, and export the node config, commissioning sheet, and runbook. Starting brownfield? Run it first as a discovery pass — the tag inventory it produces suggests candidate entities and mappings for the model and namespace, not the final governed design.
Open the planner →UDL & FDL Planning
Plan where governed data comes to rest and how reality reports back: storage, serving, and lineage in the Unified Data Layer, and the Feedback Data Layer's evidence trail of claims, decisions, and outcomes. The layer guides walk through the design decisions a dedicated tool would automate.
UDL guide →·FDL guide →Agent Designer
Define the intelligence that consumes the governed foundation: domain-specific AI agents that exchange canonical objects instead of free text, coordinated by a centralized LLM Router. Import the canonical model from the CDM Designer, scope each agent to the entities it owns, and map how requests route to the right domain.
Open the designer →Standards Crosswalk
Map UMDA concepts across the manufacturing standards: ISA-95/88, OPC UA, MQTT/Sparkplug B, B2MML and more. Search a standard or a concept, switch the context lens for discrete, batch, or continuous process, and see how the pieces translate.
Open the crosswalk →Plain-Language Standards Notes
The ISA-95 object model and the ISA-88 batch model, defined the way practitioners use them: equipment, lots, work orders, batches, recipes, phases. Each page opens with a relationship map, and every object has a stable anchor that the designers' exports link back to.
ISA-95 objects →·ISA-88 objects →Reference Library
Key terms, acronyms, and the industry standards (ISA-95/88, OPC UA, MQTT, NIST, ISO) the Unified Manufacturing Data Architecture is built on.
Browse the reference →Learn by doing
The two interactive ways into UMDA, also one click away in the top navigation: play the transformation end to end, then score where your own plant stands.
Built to Scale
A manufacturing tycoon simulation: modernize the plant floor and build the UMDA stack one layer at a time, learning first-hand why the data foundation has to come before the AI.
Play the simulation →Maturity Self-Assessment
Score your data and operational-AI readiness on the two-axis maturity quadrant, then get a tailored, layer-by-layer plan for what to build next.
Assess your maturity →