Crews stop digging for procedures.Your air gap stays closed.
Procedures, permits and standing orders, searchable inside your OT boundary, with clause and revision cited in every answer. You own the code.
There is no path out.
There is one signed path in.
Open-weight models on a server inside your fence: no outbound route, no telemetry, updates only as signed offline packages.
- 01
Documents indexed
Procedures, permits, standing orders, vendor manuals and shift logs, scanned paper and control-room audio included, indexed by clause and revision.
- 02
Answers cited
Every answer names the clause and revision it came from. When retrieval comes back thin, it declines instead of guessing.
- 03
Engineers verify
The source clauses are on screen with the answer, so the person on shift checks a citation, not the whole binder.
- 04
Signed updates only
New models and fixes cross as signed offline packages through your existing transfer process. On any signature or hash mismatch, nothing installs.
Each install records the bundle, signer, operator and time, so your auditor can tell which model answered on any given date.
The same approach, already running.
At a utility and an engineering firm.
Both run on the client's own hardware with open-weight models, and both answer with a citation back to the source document.
Of graded answers correct, with citations
Clause and revision cited, graded by the site's own engineers in the pilot's final two weeks, across 28,000 documents on an offline OT network.
Read the case~340,000Archive documents searchable
23 years of project archives, plus the DIN and Eurocode standards, searchable with source citations at a 200-employee German engineering firm.
Read the caseThirty minutes. You leave knowing whether the work is worth automating.
Three lookups your shifts do by hand.
It finds the clause, engineers decide.
It never operates plant or issues a permit. It finds and cites the source, and a person makes every switching call.
Permit checks
A permit checked against the current procedure revision, source clauses on screen. At the utility, a twenty-minute cross-check now takes under a minute.
Procedures and standards
Switching procedures, standing orders, vendor manuals and regulatory texts, searchable by question, with clause and revision under every answer.
See the Lumen workspaceShift logs and control-room audio
Decades of shift logs, much of it scanned paper, and transcribed control-room audio, searchable in the same place as the procedures.
What your security officer will ask.
Five answers, checkable inside the fence.
What crosses the boundary, how you know it works with nothing reporting out, who reads what, how updates run, and who owns it.
Only a signed offline package, through the transfer process you already run. The server has no outbound route, and telemetry is stripped at build time.
A question set your engineers write re-runs inside the fence after every model, prompt or index change and prints a diff. At the utility it holds 400 questions.
Login binds to your site directory and roles map to document libraries, so a contractor cannot retrieve restricted procedures through it.
Yes. Installs refuse on any signature or hash mismatch, and rollback is a previous image already on disk. The utility has run two update cycles on its own.
You do. Code, models and documentation are yours on delivery, and every model weight sits on your hardware for your team or auditor to inspect.
Start with one document library.
Or with two weeks of boundary review.
Fixed scope, fixed price, and the code is yours. We stay until your team runs the package transfer and rollback itself.
Make one library searchable
One set of procedures or permits, scored against a question set your engineers write. Access widens only when the build inside the fence scores as well.
A two-week boundary review
Document classes, the network diagram, the transfer path and hardware sizing, then a straight answer on what is worth building.
“Bring the lookup your crews do by hand most often. On the first call we tell you what would have to cross your boundary, and if it is too much, we say so.”
Sebastian Mondragon, Founder of Particula Tech