Beat 01
Vendor-neutral by default
Where a tool speaks SECS-GEM/HSMS we speak it. Where it does not, we bridge over OPC-UA or REST rather than asking you to replace equipment.
Developers
Integrate the loop into a fab that already works
SECS-GEM/HSMS connectors, OPC-UA and REST bridges, an agent API and a fab-edge runtime you can run without outbound connectivity.
- SECS-GEM / HSMS
- OPC-UA
- REST
- Offline-capable
Built for OT engineers, not for greenfield stacks
Gen-8.6 OLED fabFlexible OLED module lineAutomotive display makermicroLED pilot lineAR/VR microdisplay groupLTPS array fab
Principles
How we integrate
Beat 02
Read before write
Every connector is commissioned read-only first. Write-back is enabled per path, explicitly, with a fail-safe stop attached.
Beat 03
Idempotent by construction
Agent steps can be replayed safely. A lost acknowledgement never results in a double recipe write.
Beat 04
Offline is the normal case
The fab edge runtime assumes the control plane can disappear and degrades autonomy rather than stalling the line.
# closed loop, one panel
perceive substrate → tft → emitter stack → sub-pixel
plan deposition · anneal · transfer · test/bin
act recipe write-back (SECS-GEM)
sense mura ΔL* · sub-pixel opens · particles
optimise yield · ramp · scrap
log immutable audit entry ✓ signed
retrain engineer correction → model
Integration
Commissioning a connector
The same sequence on every tool, so equipment engineering knows what to expect.
Step 1 of 6 · survey
Survey the interface
Protocol, message set, permissions and existing governance around the tool.
Step 2 of 6 · read
Enable read-only
Telemetry, metrology and event streams flow in; nothing flows back.
Step 3 of 6 · model
Map the model
Signals mapped to the panel model so agents reason in fab terms, not tool terms.
Step 4 of 6 · shadow
Run shadow
Predictions scored against real dispositions before any write-back exists.
Step 5 of 6 · arm
Arm write-back
One path at a time, with fail-safe stop and authorisation.
Step 6 of 6 · verify
Verify and audit
Post-action measurement plus a signed audit record.
Agent API
Query the loop from your own systems
The agent API exposes calls, evidence, decisions and audit records so your MES, yield system or internal tooling can consume them directly.
# fetch open calls for a line
GET /v1/calls?line=g6f-cell-01&state=open
# response (trimmed)
{
"id": "4821",
"class": "mura.large_area",
"delta_l": 1.7,
"evidence": ["uniformity_map", "overlay_delta"],
"proposed_action": "recipe.writeback",
"gate": "advisory",
"model": "v2.14.1"
}
Surfaces
What developers work with
Connectors
SECS-GEM/HSMS, OPC-UA, REST and MES adapters for the in-scope tools.
Agent API
Calls, evidence, proposed actions, approvals and outcomes.
Audit export
Signed decision records for your quality and yield systems.
Webhooks
Push calls and state changes into ticketing, alerting and shift handover.
Model management
Version pinning, staged rollout and rollback endpoints.
Edge runtime CLI
Health, autonomy state, queued writes and fail-safe status.
Integrations
Where the connectors land
Deposition, litho and encapsulation
Vacuum depositionInkjet/TFE encapsulationPhotolithographyOverlay metrologyChamber telemetry
Anneal and TFT process
Excimer laser annealThermal annealVth metrologyLTPS/oxide array
Inspection, metrology and test
Mura/AOI systemsOptical uniformityArray testCell testAging
Transfer, repair and handling
Mass-transfer headsLaser repairPanel roboticsCassette logistics
Fab systems
MESSECS-GEM / HSMSYield managementHistorian / OPC-UASSO and identity
Notification and workflow
TicketingShift handoverAlertingReporting surfaces
Reference
Protocol coverage
Coverage is commissioned per deployment against the tools actually in scope.
| Interface | Direction | Typical use |
|---|---|---|
| SECS-GEM / HSMS | Read and write | Tool telemetry, events and recipe write-back |
| OPC-UA | Read and write | Bridged tools, handling and facilities signals |
| REST | Read and write | Modern inspection and metrology systems |
| File / historian | Read | Historical process and inspection data for baselining |
| MES | Read and write | Lot context, routing and disposition |
| Webhook | Write | Notification and workflow systems |
Operations
What you run on site
The fab edge runtime is a single deployable that runs beside the tools, holds the models, executes agent steps and keeps the audit log durable even with no outbound network.
- Single deployable, versioned and signed
- Local model store with staged rollout and rollback
- Durable audit log with signed export
- Health, autonomy and fail-safe state exposed to your monitoring
# closed loop, one panel
perceive substrate → tft → emitter stack → sub-pixel
plan deposition · anneal · transfer · test/bin
act recipe write-back (SECS-GEM)
sense mura ΔL* · sub-pixel opens · particles
optimise yield · ramp · scrap
log immutable audit entry ✓ signed
retrain engineer correction → model
Voices from the line
What the fab floor tells us
“We do not lose panels because nobody is watching. We lose them because the signal that mattered was buried under a thousand nuisance calls.”
“Ramp is the whole game. If a new product takes two quarters of manual tuning, that is two quarters of margin we never get back.”
“Transfer yield is our ceiling on microLED. Every dead emitter is a repair cycle or a scrapped backplane.”
Quotes are illustrative composites drawn from discovery interviews with process-integration, yield and quality engineers. Named references are [PLACEHOLDER] pending design-partner consent.
The economics
What the loop is measured on
Emiteon is priced and evaluated on the numbers a fab already reports. These are design-partner targets for the first twelve months of deployment.
$26BDisplay-fab automation, process control, inspection, test and fab software market
~14%Annual growth in the segments Emiteon plays in
135%Net revenue retention target from land-and-expand
99.9%Uptime target for the fab edge runtime
Figures marked as targets are design-partner objectives, not audited results. Company operating status, customers and outcomes are [ASPIRATIONAL] until independently verified.
FAQ
Questions fabs ask first
Through three gates. Shadow mode observes and predicts with no write-back; advisory mode recommends recipe, transfer and binning moves that a process-integration or yield engineer approves; graduated autonomy releases low-risk deposition, anneal and transfer control once measured accuracy and twin validation clear the bar. High-impact decisions stay human-in-the-loop.
Reducing false calls is the wedge, not a side effect. The mura-and-defect agent is trained on true-versus-false-call labels from your own inspection history, so it separates genuine large-area non-uniformity, sub-pixel opens and shorts, particles and stains from nuisance signals, and every call is traceable to the evidence behind it.
Per-tenant isolation with recipes, panel designs and defect images scoped to your tenant, encryption in transit and at rest, SSO/RBAC, an immutable yield/quality-grade audit log and an on-prem or air-gapped option. Fleet learning shares model improvements, never your recipes.
Deposition, photolithography, encapsulation and anneal tools, Mura/AOI inspection and metrology, array and cell test, mass-transfer and repair stations, robotic handling and MES — vendor-neutral via SECS-GEM/HSMS where the tool supports it, with REST and OPC-UA bridges elsewhere.
Every pixel, perfectly uniform.
Commission the first connector
Read-only, on one tool, with your equipment engineering team in the room.