Blog
Practical writing on SECS/GEM, GEM300 and equipment connectivity. Written to be useful whether or not you ever talk to us.
Three interfaces, and the cost of picking the wrong one
REST, GraphQL and WebSocket solve different problems. Choosing by preference rather than by shape is what produces an integration that works in the lab and falls over on a real fleet.
Read the postSECS/GEM, explained for the people buying a fab
Your tools will not talk to your MES on their own. Here is the protocol stack that makes them, why it is not optional, and why the decision gets made earlier than most teams expect.
Read the postTwelve connectivity questions to ask before you sign the equipment PO
Every one of these is cheap to ask before purchase and expensive to discover afterwards. Take the list to your next equipment vendor meeting.
Read the postGEM300 in plain terms: E40, E87, E90, E94 and E116
Five standards that turn a tool that reports data into a tool a factory can actually orchestrate. What each one does, and what breaks without it.
Read the postAir-gapped, India-resident, or cloud: where should equipment data live?
A decision framework for fab telemetry, including what actually crosses the boundary in each option and which questions your security review will ask.
Read the postWhat a connectivity readiness assessment actually produces
What the deliverable contains, what it costs you in time, and how to judge whether one is worth buying — from anyone.
Read the postWorking through this on a real tool set?
A connectivity readiness assessment turns the questions in these posts into a tool-by-tool answer for your plant.