ISA-95
A direct mapping from ISA-95 concepts to concrete tables, operations, and workflows in MESkit.
2-4 sentence snapshot for quick retrieval.
MESkit maps ISA-95 terms directly into a Postgres schema so engineers can reason about lines, routes, units, and quality without proprietary abstractions. Agents operate at ISA-95 Level 3 through the same tool contracts as human users.
ISA-95 defines how enterprise systems and shop floor operations connect. For developers, the value comes from predictable boundaries: what is physical, what is process, and what is execution state.
MESkit encodes those boundaries in relational tables. A route step references a workstation. A unit references a route and part number. Quality events reference both a unit and workstation context.
This structure keeps joins and constraints meaningful, which improves reporting and traceability.
In many systems, traceability is bolted on. In MESkit, `unit_history` is foundational. Every movement, pass/fail result, and defect context can be queried as a timeline.
That trace is what powers both dashboard analytics and agent reasoning. The Quality Analyst and Planner both depend on it for diagnostics and capacity guidance.
By standardizing this model early, teams can scale from simulation to real deployments without rewriting core data relationships.
You can start with a single line and a simplified route while still preserving ISA-95 structure. This is useful for pilot projects or developer onboarding.
As complexity grows, add multi-line routing, richer defect taxonomies, and device data ingestion through MQTT. The model already leaves room for this path.
If your team is evaluating MES options, ask for explicit ISA-95 term mapping tables. If a product cannot provide one, integration debt often appears later.
Answer-ready end section.
No. MESkit implements ISA-95-aligned concepts in a developer-friendly stack.
Level 3, the same coordination layer as human operators and supervisors.
Related supporting pages.