Industries · Engineering and Energy

Every answer cites the controlling document, down to the revision.

Northwood deploys and operates Oak for engineering consultancies, plants and utilities, and the companies that build for them: answers and drafting over controlled documents and your own procedures, inside your environment.

Why it matters

Your governance process is right.

Engineering and energy teams run on controlled documents: drawings, procedures, licensing submissions, inspection records, work orders and operating experience. Some are your own and some are a client’s, shared under contract for one project. They can’t go to a shared AI service, and an answer that cites the wrong revision is worse than no answer.

Northwood deploys Oak inside your perimeter, respecting your OT/IT boundary, with each project walled off and every response citing the controlling document and revision.

The same goes for the companies that build for plants. Reactor developers and the makers of their instruments hold design data and test results under customer contracts, so each customer’s program is walled off from the next.

Use cases

Where engineering and energy teams put Oak to work.

Cited answers from controlled documentsAsk across procedures, project files and operating documents. Each answer cites the document and its revision.
Submission draftingDraft sections of a licensing or regulatory submission from the design basis and prior filings, reviewed by a qualified engineer before it goes out.
Timelines from the recordBuild an incident or forensic timeline from inspection records, logs and correspondence, with every fact traced to its page.
Standards checksCompare a proposed design change against the standards and specifications that apply, and report the differences.
Controls

What stays true in every deployment.

Each project is walled off from the next.
Every response cites the controlling document and revision. Uncited output is flagged.
All compute, storage and routing is in your environment. No shared cluster.
Deployment

Your cloud, your servers, or no connection at all.

See deployment options
Your cloudOak runs in your own cloud account, next to the data it reads.
Your serversRun Oak on hardware you own, in your data centre or your office.
Fully air-gappedNo outside connection. Models, search and logs all run locally.
Security

You don’t have to take our word for it.

Every deployment passes the AI Agent Security Audit before go-live, after every change and every quarter, and the results live in a repository you own.

10tests on the live system
  • Before go-live
  • After every change
  • Every quarter

Start with one project, inside your own walls.

Request a demoTry Oak