The problem
Every machine and every system needs custom glue.
Point-to-point code nobody owns, broken by the next upgrade. OpenCore MES connects through open contracts instead.
Solution
Machines, described as data.
With the Equipment integration suite: a tool type your screens read, and an interface that maps one vendor's codes onto it, approved like any design.
- SECS/GEM over HSMS. One connection per tool; nothing lost while the MES is busy.
- GEM300. Carriers checked at the load port (E87), control and process jobs at track in (E94, E40).
- Wafers and ports. Each wafer tracked through the tool (E90); load ports handed to the AMHS (E84).
- Cluster tools. Each chamber a machine with its own state and alarms.
- OPC UA and MQTT. Signed and encrypted; same screens, whatever a machine speaks.
- Same rules as people. Machine events go through the same checks and audit trail.
Solution
Systems call it the way people use it.
ERP, LIMS and label printers reach the same designs, with the same checks.
- Web services you design. Revocable tokens, described by OpenAPI.
- Transactions over HTTP. The ERP runs a transaction by its name, with every check a person's run has.
- Queries over HTTP. A BI tool reads named queries, read only, a page at a time.
- Label printers by contract. An adapter per printer language, checked by a conformance kit; with none, the label prints from the browser.
- Connections out. Each limited to the requests its design allows.
- Versioned, with notice. Nothing a caller relies on changes without warning.
- Every call counted. Who called, how long, why refused.
Solution
When a call fails, you see why.
One monitor for everything that runs: what it was given, what it answered, and where it went wrong.
- A tab for each kind. Schedules, record triggers, web calls in, connections out.
- Every run kept. Its input, its answer, each request it sent and how long it took.
- The line that failed. The script's line, with the lines around it.
- Kept as long as you choose. What worked and what failed, each for its own period.
- A copilot that explains. It reads the runs and the scripts and says what to change; the fix goes through a change, never around it.
Solution
Extended without forking.
Suites plug into the core's open contracts; a plant's differences are designs, not patches.
Available nowPlanned
- Side by side. Several suites, each adding designs, steps and screen blocks.
- Removable. Take a suite away and the core runs on; its data waits.
- Scripts run apart. Locked down, holding no credentials; walled in on Linux.
- Open source core. Apache 2.0, published with its first release.
- A versioned extension API, with a conformance kit for suites.