MESkit
View on GitHub

MESkit public website

Product overview

MESkit combines four operating modes with an always-available chat panel. Operators can work by clicking UI actions or issuing natural-language instructions that resolve to the same typed tool calls.

Last updated: March 3, 2026

Summary

How the product experience is structured.

Summary

MESkit is a simulation-first MES experience that keeps operational logic centralized in the tool layer. Build and configure the factory model, run production movement and quality events, then monitor execution metrics in real time. Chat commands act as a second interface, not a separate capability.

Four operating modes

The UI mirrors real manufacturing progression.

Build

Create lines, workstations, and machine assignments with live state sync.

Configure

Define part numbers, BOM entries, routes, and serial algorithms.

Run

Generate units, move WIP, and log quality events with manual or chat control.

Monitor

Track throughput, yield, and unit traceability from one dashboard.

Chat panel as a parallel interface

Same actions, different input style.

UI example

  • Click Move on unit SMX-00042.
  • UI calls move_unit with validated payload.
  • Realtime update pushes to all connected clients.
Chat equivalentOperator Assistant
User: Move SMX-00042 to the next station
ā†’ search_units(serial_number='SMX-00042')
ā†’ move_unit(unit_id=...)
Agent: SMX-00042 moved to Station 3.

MVP boundaries

Current scope and planned expansion.

In MVP

  • Discrete manufacturing flow with route-based unit progression.
  • Operator Assistant in chat.
  • Quality Analyst and Production Planner on roadmap milestones.
  • Realtime dashboards and event logs tied to tool outputs.

Planned after MVP

  • Full batch and continuous UX surfaces.
  • MQTT transport bridge and anomaly monitor.
  • Expanded planner scenarios and cross-line orchestration.

Who this is for

Practical fit by user type.

Manufacturing engineer

Validate ISA-95 concepts using concrete routes, unit history, and quality event timelines without enterprise license overhead.

Small manufacturer

Start with simulation and explicit shop-floor workflows, then expand toward machine-fed execution using MQTT-ready contracts.

Developer team

Use the reference stack to build programmable MES flows with typed tools and agent integration.

AI exploration team

Test agent workflows grounded in real MES operations, not chat-only demos disconnected from execution logic.

Key facts and FAQs

Answer-ready structure for technical discovery.

Key facts

  • The UI and chat panel are parallel interfaces to one tool layer.
  • MVP default production type is discrete manufacturing.
  • Batch and continuous models are schema-ready and roadmap-scoped.
  • All state-changing actions are explicit tool calls with validation.

Mini FAQ

Can I use MESkit without AI agents?

Yes. The full UI workflow works independently of chat commands.

What does "every button has a voice equivalent" mean?

Core UI operations map to the same function signatures exposed to agent tool-use.

Are batch and continuous flows fully available in MVP?

No. MVP focuses on discrete workflows while keeping data contracts ready for expansion.

Canonical links

Supporting pages for deeper detail.