Scoped & quoted before you pay

Your systems, understood — at every depth

Every scope includes grounded extraction, a coverage disclosure — what was analysed, what was not, and the open unknowns — an interactive model, and exports you own; the reviewed grades add a named engineer's sign-off. Each assessment is scoped and priced before you pay — you see the figure after the scoping preview, and nothing starts until you confirm.

Orientation

A high-level map of one system.

Priced per system at scoping

Review: Map-level engineer review — structure and risk calls checked and signed by a named engineer (not claim-by-claim). Machine-only grade on request.

✓System map & main components
✓Overall structure & data flow
✓The most visible risks
✓Coverage & unknowns disclosed
✓Interactive model + document exports

Request an Orientation

Grade × depth, explicitly

Two independent axes: how deep the assessment goes, and who has reviewed it. Any depth is available machine-only at machine price — same grounding discipline, honest label. Verified is Full model plus the adversarial column.

Depth	Machine-generated	Engineer-reviewed	+ Adversarial pass
Orientation	Structure & visible risks, honest label	Map-level review, named sign-off	Rarely warranted
Full model	Grounded, identified behaviours	Claim-by-claim evidence review, named sign-off within scope	= Verified: evidence support, contradictions, obsolescence challenged across the model
Advanced	Replacement comparison, runtime data	Scoped engineering attestation	Independent verification programme

⚖️

Two lanes, one discipline

Every deliverable carries its grade — machine-generated or engineer-reviewed — and the label is never blurred. The scopes above are the engineer-reviewed lane: a named reviewer signs off and stands behind the result. A fast, AI-only lane covers breadth and everyday questions at machine speed and machine price, always labelled machine-generated; during early access it is available on request as part of a scoped engagement.

What each grade asserts, in writing — the Assessment Standard →

🏭

Assessing a whole line, not one controller?

A system assessment composes multiple units into one model and adds an Interface Control Document (ICD) covering every connection inside the system and outward to SCADA, field I/O, and neighbouring systems. Each unit is scoped at the depth it needs — a full model where it matters, a lighter map where it doesn't.

🔒

Optional IP protection

For sensitive systems, an automated obfuscation layer replaces your proprietary tag and equipment names with neutral identifiers before anyone reviews the code, then restores them in the delivered model — your logic is verified, your names never leave your environment. You preview and approve exactly what is exposed — in a searchable diff view, with AI suggestions — before anything reaches a reviewer. Obfuscate the code alone, or the code and its documentation together so the cross-references stay intact. Available on Verified and Advanced; because it makes the human review more demanding, it carries a premium.

Every scope includes the model, not just the report

A consultancy report is finished the day it arrives. What you buy here keeps working — at every scope, including the smallest.

Ask it questions

Ask about an alarm, an interlock, a mode nobody recognises — answers come from your assessed system and cite the evidence behind them, scoped to that machine.

See what changed

Each assessment is kept as a baseline. Re-ingest after a modification and you get a diff: which findings still hold, which were invalidated, and what needs re-review — scoped to what moved.

Read it from your own tools

An authenticated read API, and MCP so an AI copilot can query the verified model directly — read-only, scoped to your organisation by your own key.

Take it with you

Markdown, Word, PDF, and a structured export of the model in an open format. No licensing restrictions, and it stays readable without us.

Common questions

What platforms do you support?

Vendor-neutral — we read the logic itself across controller families, IEC 61131-3 languages, and embedded control code. We prioritise vendor-neutral formats like PLCopen XML and add vendor formats on demand. Support depth varies by format, and every assessment states what was fully parsed and what was read at reduced depth — disclosed, never assumed.

What if the answer isn’t in the code?

Then we ask. Where the sources cannot settle a behaviour, the assessment raises it as an open question — the line that prompted it, and who is likely to know — for you and your team to answer, instead of filling the gap with a guess. Answers are recorded against the claim they explain, attributed to who said it and when, and kept as testimony rather than merged into what the code proves. Anything still unanswered ships as a stated unknown.

Can I go deeper later?

Yes — each scope builds on the one below. Start with an Orientation or Full model and deepen, or add more systems, whenever you like.

Do I own the output?

Fully. You receive the interactive model, document exports, and a structured export in an open, documented format — no licensing restrictions.

Is my code confidential?

Yes. Your code and data are never shared, and we sign NDAs on request. For maximum protection, the optional obfuscation add-on replaces your proprietary names before review and restores them in the delivered model.

Not sure which scope fits? Talk to us first.

Get a free scoping consultation

Or see the output before you spend anything — try the Apollo 11 demo on real public-domain flight code, every citation checkable.