Modern and legacy equipment alike
Current tools speak SECS/GEM over a network link. Older tools speak it over serial. Outpost handles both, so the age of a tool never decides whether it can be automated.
The product
A control plane for equipment automation. Outpost connects your tools, shows every running interface in one place, and records what happened, all from a single program on your own server.
Where it sits
Outpost supervises the interfaces that already talk to your tools. Your MES and host systems keep working the way they do today.
What it does
Current tools speak SECS/GEM over a network link. Older tools speak it over serial. Outpost handles both, so the age of a tool never decides whether it can be automated.
Outpost is built so you can see which tool interfaces are running, their state and their logs from a browser, without logging into a server or reading a terminal.
Outpost is built to append every event to a log that is never rewritten, so you can always answer what happened, when, and in what order.
Outpost is designed so every user signs in as themselves, with roles that separate what the fab floor can do from what administrators can do. Configuration is never open to everyone.
Example trace
A tool and its host exchange short, numbered messages. Outpost keeps every one of them, readable, in order.
| Time | Dir | Msg | Meaning |
|---|---|---|---|
| 08:14:02.117 | H→E | S1F13 | Establish communications |
| 08:14:02.131 | E→H | S1F14 | Communications established |
| 08:14:05.402 | E→H | S6F11 | Event report · lot started |
| 08:14:05.409 | H→E | S6F12 | Acknowledged |
| 08:31:47.866 | E→H | S5F1 | Alarm set · chamber pressure |
| 08:31:47.871 | H→E | S5F2 | Acknowledged |
Illustrative sequence. H = host, E = equipment.
Deployment