Plant data, all the way to the business system.
Every equipment vendor offers a different interface and the MES accepts one format. We put a single layer in between: per-equipment drivers isolated as adapters, one standard schema exposed upwards.
When integration is the bottleneck.
- 01
Every machine speaks differently
Vendor specifics are absorbed by adapters, and the MES receives one schema.
- 02
Production is posted by hand
IDs read from barcode or QR are posted to ERP automatically. This is running on an automotive electronics assembly line.
- 03
Traceability breaks
LOT, CARRIER and PANEL IDs are reconciled at each process step so the history joins up.
- 04
Process conditions go unrecorded
An OPC UA gateway records recipes and process conditions automatically. Built for a PCB plating line.
What you get.
Scope is fixed after the site survey. These are the items an MES/ERP integration normally includes.
- Interfaces
- SECS/GEM (HSMS · SECS-I · SECS-II · GEM300), OPC UA · DA, Modbus
- Adapters
- Per-equipment drivers isolated, with a route for adding machines
- Standard schema
- The single upward schema and its tag map
- Failure behaviour
- Disconnection, retry and duplicate-suppression rules
- Traceability
- LOT · CARRIER · PANEL ID reconciliation and history
- Verification
- Virtual-M3 and simulators, so the line keeps running
What we are asked most, before a quote.
We already have an MES. Can you just integrate?
That is the usual case. The MES accepts one format and every equipment vendor offers a different interface, so what we build is the layer in between. We treat the MES itself as something not to touch.
Does new equipment mean rewriting everything?
No. Per-equipment drivers are isolated as adapters and only one standard schema is exposed upwards, so when a machine changes the MES-side code usually stays as it is. You add an adapter.
Do you support SECS/GEM?
HSMS, SECS-I, SECS-II and GEM300 scenarios. We have built GEM300-based equipment integration with live yield reporting on a semiconductor back-end line.
Our protocol is not on your list.
Send the specification and we will tell you whether we can handle it before you commit to anything. OPC UA and DA, Modbus TCP/RTU, REST and SOAP, CSV/XML file interfaces and direct database links are the baseline.
How long does it take?
Four stages — site survey, design, build and simulation, commissioning — usually six to ten weeks. It moves with the number of machines and the variety of interfaces, so send an equipment list and the protocols and we will scope it first.
Tell us your equipment and protocol.
A first reply within one working day; the scope itself takes a few conversations.
Start with what you have. We’ll work out the rest.
Equipment list, protocol, and what the data has to reach. That’s enough for a first answer — usually within a working day.
- kyoungilsystem@gmail.com
- Telephone
- +82 31 267 4759
- Office
- 47-13 Yunggeon-ro, Hwaseong-si,
Gyeonggi-do 18343, South Korea - Hours
- Mon–Fri 08:30–17:30 KST