MESkit public website
MESkit follows ISA-95 terminology and boundaries so engineers can model physical assets, process definitions, execution traces, and quality operations without translation gaps.
Last updated: March 3, 2026
How standards alignment is applied in practice.
MESkit aligns to ISA-95 by mapping each concept to concrete database structures and tool contracts. This makes the model interoperable with established manufacturing language while staying developer-friendly in a modern web stack.
ISA-95 term to MESkit implementation.
| ISA-95 concept | MESkit implementation | Examples |
|---|---|---|
| Physical model | Asset hierarchy | lines → workstations → machines |
| Product model | What to build | part_numbers, items, bom_entries |
| Process model | How flow is defined | routes, route_steps |
| Production execution | Unit state and traceability | units, unit_history |
| Quality operations | Defect and event tracking | quality_events, defect_codes |
| Future device integration | Sensor ingestion | mqtt_messages |
Current and planned execution models.
MVP default. Unit-level tracking with serial algorithms, route steps, pass/fail gates, and execution history.
Data structures are ready for extension, but dedicated UI workflows are post-MVP roadmap items.
Same level as human operators and supervisors.
MESkit agents operate at ISA-95 Level 3 through the tool layer. They orchestrate execution and analysis but do not directly replace equipment-level control logic.
Citation-friendly context blocks.
No. MESkit keeps ISA-95 language explicit in schema and documentation.
No. Agents operate in Level 3 coordination through MES tools, with MQTT bridge planned for future ingestion.
Canonical internal references.