OpenCore MES Try the demo
Low-code manufacturing platform · small plants to 300 mm fabs

The platform your plant's suites run on, changed the same day, with controls and traceability.

An open core that hosts the plant's suites, from tool integration to yield, on one sign-in, one way to change anything and one audit trail. No vendor ticket, no release to wait for: your engineers design fields, rules, screens and routes in the browser, with an AI that drafts. Each change is tested in a sandbox and approved by the departments it affects, then put live when the line is ready and checked there by whoever did.

Public demo: no sign-in, every role, reset each night.

  • Tested in a sandbox
  • Approved by those it affects
  • Part 11 practices built in
  • Open source core, with its first release

The problems it solves.

Each one has its own page: what goes wrong, and how OpenCore MES fixes it.

Every field, rule and screen waits on a vendor.

Your engineers design it

Objects, rules, screens, routes, OEE, QMS and SPC are designs, not code. An AI drafts them.

Design
Changes reach the plant untested and untraced.

Every change approved, every record proved

Design, review, approval, execution, verification; every version kept; database edits found.

Control
Operators work from stale screens and paper.

A live floor, a step at a time

Screens that update themselves, the line from above, instructions step by step; scans routed by their label, labels printed by the transaction, a kiosk of picture buttons.

Floor
A real flow is a customisation: segments run twice, queue times, splits, holds.

Complex flows, drawn and proved

A segment run at room and again hot, a queue time between two steps, a split that follows its parent, a lot moved to another route; every move proved through the screens.

Flow
An answer about the floor takes a week.

Ask, and get a report

Plain words in, a report out, from live data and only what the asker may read.

AI
Every machine and system needs custom glue.

Open contracts at every seam

SECS/GEM, GEM300, OPC UA, MQTT; web services, transactions and queries over HTTP.

Connect
Growth means downtime and a bigger server.

No restarts. Scales out.

Changes go live while it runs; add servers, not size. 200 lot moves a second on one.

Scale
Screens in one language, for a mouse and perfect sight.

Every operator, in their own language

Each person picks their language, Arabic read right to left; your designs translated and approved; forms a screen reader and a keyboard can follow.

Everyone

One platform. The suites on it.

The core gives every suite the same people, the same way to change anything and the same audit trail. A suite brings the designs for a job; your engineers take them in as one approved change, own them from then on, and the core runs on if the suite comes off.

The plant

What every plant runs around its lines.

  • Quality management
  • Maintenance
  • Material management
  • Vendor management
  • OEE and downtime
  • Shift Calendar
  • Document control and training New
  • Gate passes New

The fab

A 300 mm front end and the apps around it.

  • Wafer fab
  • Real-time dispatch New
  • Material handling New
  • Fab planning New
  • SPC and sampling New
  • Run-to-run control New
  • Equipment data and fault detection New
  • Yield and wafer maps New

Assembly and test

The back end, from the tester to the shipping box.

  • Semiconductor assembly and test
  • Load board management
  • Assembly and test planner New

Gateways

What speaks to the world outside.

  • Equipment integration
  • Import & Export
  • ERP integration New
  • Sales channels
  • Payments New
  • Website New

New built and tested end to end, ready for a first case study; the rest are in the suites store. What every suite shares · Editions and prices

Not only a fab

Same parts, another trade.

Built to show how far the platform reaches: a cabinet shop and a cooperative, from the same objects, states, rules and screens as a wafer lot. Neither adds code to the platform.

A cabinet shopThe Carpentry suite

Jobs and their cabinets on a route whose steps are pages of a build book: lumber checked for moisture, glue-ups square within the grade, finish batches traced, each machine run only by someone certified on it.

objectsrouteguidescertificationsscreens

A cooperativeA worked example

A plant's employee coop: share capital paid in, loans approved by its credit committee, a store that sells on credit up to a limit, a statement for every member each month, and the month's and the year's reports.

objectsapproval flowtransactionsqueriesmail

A performance reviewA worked example

Goals agreed with the manager, a rating sealed until it is calibrated, and an acknowledgement the employee signs.

statespoliciessignature

Each is run end to end by the test pipeline; the coop and the review in a browser too. The review, designed

200 lot moves a secondon one server, a move one lot through one step: four transactions, p50 16 ms
1,000,000 lotsa move still takes 22 ms; any lot found by its label in 1 ms
3,000 station screens, liveeach on a machine of its own, on four servers: a move still takes 30 ms

Measured on one laptop. How, and the rest

Tools for whoever runs it.

Built in, each for those given its role in People & departments; whatever they change is in the audit trail.

The database, seen

Every statement the platform sends, counted: calls, time, rows, and which screen or service sent it. Its plan read without running it; the tables and indexes, the unused marked. An AI proposes indexes; an administrator builds them.

SQL over your objects

A query console, SQL or JSON for those who do not write it, over a view of each object, with a schema explorer. Each reader sees only what their policies allow.

Every call counted

Each service, transaction and query: how it was called, by whom, how long it took, and why a call was refused.

The integration monitor

Schedules, triggers, web calls and connections; every run kept, the line that failed, a copilot that explains. More

Data integrity

Opt in, and every record is sealed: an edit made in the database around the platform is found, named, and closed with a signed report. More

Sign-ins and retention

A lost phone, a lock lifted, a one-time password link; password spraying flagged. How long each kind of data is kept, and a person's data erased from a record.

No more satellite apps, just new screens.

With rule-based access, of course.

See it for yourself.

Be an operator, a designer or an approver, and follow a change from design to the floor.