The MES your engineers design, and your auditors can follow.
open-mes is a manufacturing execution system for regulated discrete manufacturing. Your process and quality engineers design its objects, rules, screens and transactions themselves, with an AI that drafts what they describe, and every change is reviewed and approved by people before it reaches the plant.
The demo is a public sandbox: sign in as any of its people, no account needed. It resets every night, and runs without the AI.
Quality asked that a lot can be put on hold when contamination is suspected, with the reason recorded.
Built by your engineers, not around them.
Most MES projects wait on a vendor for every new field, rule and screen. In open-mes, the people who know the process model it, and the platform carries out the rest.
Everything is a design
Lots, machines, work orders, their states and who may do what in each; the rules that check them; the screens and the transactions that move a lot onto a machine. Designed in the browser, not written into the product.
Controlled by default
No change reaches the plant until it has been reviewed and approved by the departments it touches, and every change to a record is in the audit trail: who, what, when and why.
Live on the floor
Lists, forms and boards follow every change as it happens. People see who else is on a record, why they cannot do something, and what waits for them to sign.
AI drafts. People decide.
Describe what the plant needs, and the AI drafts it as a change: the fields, the states, the rules with their test cases, the screens. It works inside the same lifecycle as everyone else, so nothing it writes reaches the plant without people reviewing and approving it.
- A copilot beside the designAsk in plain words; it reads the design, drafts the change, runs its checks and tests, and says what it did and why.
- Claude, or your own modelClaude, or any model your company runs on its own servers. Outside AI agents work through the same API, with tokens a designer issues and can revoke.
- Every AI edit on the recordWhat the AI drafted is marked on the change, for its reviewers and in the audit trail.
- Never the one who signsAn AI drafts as the designer who asked; it never reviews, never approves, never makes anything live.
- a field
hold_reasonon Lot, required when it is put on hold - the rule
lot_hold_needs_reason.js, with 3 test cases (all pass) - Hold for Quality and Production supervisors
One path for every change.
A new field, a rule, a screen, a department's approvers: they all go the same way, and the platform keeps the record of it.
Design
An engineer drafts it, alone, with co-designers or with the AI, and says why. The platform checks it as they type and tests its rules.
Review
Someone who did not design it reviews the draft, now frozen, with the evidence beside it.
Approval
Each department whose part it touches signs, in its own steps. Never the people who designed or reviewed it.
Execution
The platform makes it live, exactly as approved, and records every step.
Made for plants that answer to auditors.
open-mes is designed around the practices regulated discrete manufacturing works by: medical devices, automotive and aerospace suppliers.
- Approved changes only. Design, review, approval and execution for every change to the system, with segregation of duties enforced by the platform.
- An audit trail that cannot be rewritten. Every write, refusal and signature, chained so that a change to history shows.
- Changes to records that need approval. Your design says which edits wait for the people responsible, and the form says so before anything is sent.
- Rules with their evidence. Every rule carries test cases, run before a change can be submitted.
- "Why can't I?" Anything a person cannot see or do is explained from the same rules that decided it.
- Traceability. Lots, work orders, machines and deviations, linked, with the history of each.
Open at the core.
The platform is for the community. Suites add what particular plants need, and are sold separately.
Community edition
The whole platform, to be released as open source.
- The designer: objects, states, roles, rules, screens, transactions
- The change lifecycle, approvals and the audit trail
- Records, live screens, analytics, queries, Excel import and export
- Services and connections to the systems around it
Suites
Built on the community edition, licensed separately.
- Import & Export: any file from your ERP or legacy systems, mapped onto your models, with approved scripts
- More to follow: industry packs and integrations
See it for yourself.
Sign in as an operator, a designer or an approver, and follow a change from design to the plant floor.