What SEIB is building.
SEIB is an industrial foundation model in training, together with the agents and engineering solutions built on top of it. This page describes the programme and what it is being built to do.
Pre-launch · in training · no released version
Three things, built as one intelligence.
Each of the three is only worth building because of the other two: the model has no reach without agents, and the agents have no judgement without the model.
Industrial foundation models
One model that understands industrial engineering as a domain — requirements, geometry, process, control and the plant itself — rather than four tools that each understand a slice of it and none of the joins.
Industrial & Physical AI agents
Agents that act inside the engineering toolchain and, further out, on the floor: reading factory context, proposing changes and carrying work between stages that today is carried by people re-entering it.
Intelligent engineering & commissioning
The layer that turns a product change into the engineering work the factory needs — process, automation, tooling, and the commissioning that follows — as one continuous piece of work instead of a relay.
Purpose-trained on verified engineering work.
Industrial engineering formats are low-resource for general-purpose models, which is why those models produce output that reads correctly and fails against a real toolchain. The fix is not a better prompt; it is training against the toolchain.
- The corpus
- Verified industrial engineering work
- Not manuals and support tickets. The training data is engineering work that was actually built and actually ran, with the artefacts that prove it.
- The loop
- Verification inside training
- Compilers, runtimes and simulators are part of the training signal rather than a filter bolted on afterwards. A draft that does not clear a real toolchain is not a good answer that needs checking; it is a wrong answer.
- What we do not publish
- Architecture and parameter counts
- SEIB does not state a parameter count, an architecture family or a base model. Those numbers move while a model is in training, and a figure published today would be wrong by launch.
Engineering goes in. Engineering comes out.
The target scope on both sides. SEIB is being built to read the formats engineering already works in and to answer in the format the plant's own toolchain expects — not in prose about them.
What it reads
- Requirements, specifications and change requests
- CAD geometry, BOMs, variants and tolerances
- Process plans, operations and cycle-time targets
- Existing control projects, tags and naming conventions
- Live factory context — machines, cells, constraints
What it produces
- Control code in the IEC 61131-3 languages
- Robot and machine-vision routines
- Tooling and simulation configuration
- Process and commissioning documentation
- Reviewable diffs against what is already running
A person approves every change. Approved changes go through your own CI to the machine. SEIB is designed to be hard-blocked from writing to safety-related program units, and from deploying anything itself.
“Add a 5-second startup delay and an E-stop interlock to the mixer motor on Line 3.”
IF NOT E_Stop AND StartCmd THEN StartTimer(IN := TRUE, PT := T#5s); IF StartTimer.Q THEN MotorRun := TRUE; END_IF; ELSE StartTimer(IN := FALSE); MotorRun := FALSE; END_IF;
The three gates above are what SEIB is being built to require of its own drafts. They are design commitments, not a record of a run — there is no released version of the model.
Nothing here will touch your plant on its own.
The question every plant asks first. SEIB is pre-launch, so what follows is the posture being designed for — stated now so you can hold us to it.
Your data stays on your site
SEIB is being built to run inside your own network, on your own hardware. The design goal is that engineering project files never have to leave the building for the model to read them.
A human commits every change
SEIB is designed to propose a reviewable diff and nothing more — no writes to a live machine, and hard-blocked from safety-related program units, in every deployment mode.
Built for zone-and-conduit thinking
Being architected in alignment with IEC 61508 lifecycle practice and IEC 62443 network segmentation, so it can sit cleanly inside an OT security model your team already runs.
SEIB is pre-certification. “Aligned with” and “architected for” describe design intent, not a claim of formal certification against IEC 61508 or IEC 62443 by an accredited body.