Semiconductor back-end
GEM300 equipment integration with real-time yield reporting
Monitoring and control, data collection and reporting, MES and ERP integration. Take one layer or all three — and we supply the equipment that goes with it.
The layer that watches and drives the equipment. Screen design, tag structure, alarm strategy and commissioning on site.
We use Autobase alongside software we write ourselves, so whatever the package cannot do, we build. Screens follow how the line is run, not how it is drawn.
We collect and store what the equipment produces, then turn it into figures a person can read.
Uptime, downtime reasons, quality. Designing the schema so it stays fast as years of history accumulate matters as much as drawing the report.
Every vendor has a different interface, and the MES accepts only one format. The moment a person bridges that gap with a spreadsheet, the data arrives a day late and is wrong at least once.
Per-machine drivers stay isolated behind adapters, and a single standard schema is exposed upward. Replace a machine and the MES-side code usually does not change.
We confirm the equipment list, the interface specifications and the existing MES schema.
We define the tag map and the standard schema, and decide what happens when something fails.
Verified against Virtual-M3 and simulators before the line is touched; cutover may need a short window.
Connected to the line, run in parallel, then handed to your operations team.
If yours is not on this list, send the specification and we will tell you whether we can work with it.
Autobase SCADA, the package we build on, ships drivers for the major Korean and overseas manufacturers as well as the open standards; anything missing we write ourselves. Over 28 years we have worked with many of the names below, and recent projects are mostly Yokogawa, Mitsubishi and LS ELECTRIC.
GEM300 equipment integration with real-time yield reporting
OPC UA gateway with automatic process-condition history
Barcode traceability with automatic ERP posting
A first reply within one working day; the scope itself takes a few conversations.
Equipment list, protocol, and what the data has to reach. That’s enough for a first answer — usually within a working day.