Connect to what you have. Run where you decide.
Ensign 14 sits on top of the data your fab already collects. It reaches your tools through the interface each one supports, and it runs on your own hardware or in your own cloud account.
Tested on real equipment data.
Four ways in.
Most fabs use a mix. We start with what is already there and add only what a tool is missing.
Existing FDC systems
If you already collect fault detection data, we read it. No second set of connections to the same tool.
SECS/GEM and OPC UA
The standard equipment interfaces. Most modern tools speak at least one, so this is often the fastest route.
Tool side datalogging
For tools that keep their own logs, we collect them at the tool, on the schedule that suits you.
Custom IoT
Where a tool exposes little or nothing, we add sensors for the signals that matter. Older equipment included.
One view across mixed sources.
A fab rarely has one data path. Ensign 14 brings the paths together so a tool is judged on its own history, whichever way its data arrives.
Each source is labeled, so you always know where a reading came from.
| Tool | Source | Status |
|---|---|---|
| Ion source 04 | SECS/GEM | Live |
| Etcher 11 | Existing FDC | Live |
| Deposition 02 | Tool side log | Live |
| Legacy implanter | Custom IoT | Calibrating |
Two ways to run it. You choose.
Both give you the same copilot. The difference is where it lives, and who looks after the machine it runs on.
On premises
Runs on hardware in your facility, on your network. Telemetry, logs and documents never leave the building.
In your AWS account
Runs in your own cloud account, in the region you choose. Your data stays in your account, under your controls.
| On premises | In your AWS account | |
|---|---|---|
| Where it runs | Your hardware, your facility | Your account, your region |
| Where data lives | Inside your network only | Inside your account only |
| Connectivity needed | None beyond your internal network | A secure link from the fab to your account |
| Who maintains it | Your IT, with our support | Managed with you, in your account |
| A good fit when | Policy keeps data on site | You want to scale without new hardware |
From signal to guidance.
The same four stages, wherever it runs.
Collect
Signals and logs arrive from your tools by the paths above.
Learn
Each tool’s normal range is learned from its own healthy runs.
Recognize
Departures are compared with the fault library and your incident history.
Guide
The technician gets a ranked, cited checklist, and the outcome is remembered.
Tell us what you run.
Share your tools and how they report. We will suggest the shortest path in.