LLM.co — Private AI & custom AI developmentCall +1 (206) 844-1326All inference local

LLM.co · Private AI & Custom AI DevelopmentPrivate AI for energy & utilities

Field procedure search, outage reporting and compliance documentation for operators whose critical systems must stay isolated.

FIG. — Control roomLLM.co

Utilities run critical infrastructure under strict separation rules. Private AI can work inside those boundaries, at the substation, the control room or the field truck, without new paths to the internet.

EnvironmentsControl centers, substations, field devices
ControlsNERC CIP-aligned access and change control
DeploymentOn-premises, edge or air-gapped
What we build

Common energy & utilities builds.

01NERC

Procedure search

Switching orders and field procedures answered on site.

02NERC

Outage reports

Event narratives drafted from logs and crew notes.

03NERC

Compliance evidence

CIP documentation assembled from existing records.

04NERC

Asset knowledge

Equipment histories and manuals searchable by crews.

AI for utilities that respects the electronic security perimeter

Utilities hold decades of operating knowledge in switching procedures, equipment manuals, relay settings files, inspection records, outage logs and crew notes. Much of it lives on networks that are deliberately cut off from the internet. AI for utilities has to work inside those boundaries, or it cannot touch the information that matters most.

LLM.co builds private AI on open-weight models that run on hardware the utility controls. A system can sit in the corporate data center, in a control center environment or on an air-gapped network. It opens no new paths to the internet and makes no calls to an outside model provider.

What NERC CIP AI has to account for

Any system that reaches BES Cyber Systems or their information falls under the NERC CIP standards. That brings requirements for electronic security perimeters, access management, configuration change management, information protection and logging. NERC CIP AI is a short name for building AI so it fits those requirements from day one.

In practice, we classify each use case by the networks and data it touches before any build starts. Corporate use cases run on the IT side. Use cases that need BES Cyber System Information run on hardware inside the right zone, with access tied to your existing authorization records. Model and software updates arrive as signed bundles that go through your change and baseline process. The system is built to support your CIP program, and your compliance team decides how it is classified.

Workflows for operations, field crews and compliance

The strongest first projects sit close to work crews and compliance staff already do by hand.

  • Procedure search. Operators and field crews ask plain-English questions and get the relevant switching or maintenance procedure, with the revision and section cited.
  • Outage and event reports. Narratives are drafted from SCADA event logs, OMS records and crew notes for an engineer to review.
  • Compliance evidence. Records for CIP and other audits are collected, matched to requirements and assembled into evidence packages with gaps listed.
  • Asset knowledge. Equipment histories, nameplate data, test results and manuals become searchable by asset ID.
  • Work package preparation. Job briefs and safety checklists are drafted from the work order, the asset history and the applicable procedures.

Deployment at the edge and in the field

Many utility use cases need answers where connectivity is poor. Smaller models can run on a ruggedized server in a substation or on a laptop in a truck, with a local copy of the approved procedures. Larger models run in the control center or data center on the OT network side. On-premises AI in each location follows the same identity, logging and update rules.

Systems in these environments read data and draft documents. They do not issue control commands to grid equipment. That boundary is set during scoping and enforced in the architecture.

What to pilot first and what to avoid

For most AI for utilities projects, procedure search for one operating area is a sound first pilot. The documents are controlled, operators can judge answers quickly, and the evaluation set comes from questions crews have already asked. Compliance evidence assembly is another good start because the output goes to people who check it carefully.

Avoid any tool that requires uploading CIP-protected information to a vendor cloud. Avoid connecting a model directly to SCADA or EMS write paths. Avoid starting with use cases where the source documents are out of date, since the model will repeat what it reads.

Why custom AI development fits utilities

Each utility has its own network zones, procedure formats and change process. Custom AI development lets the system match them. Work starts with a two-week discovery sprint, and a focused first system usually reaches production in eight to twelve weeks. You own the code, prompts, evaluation sets and any fine-tuned weights.

How it works

Four steps, each one reviewed.

01

Map boundaries

Identify which networks each use case may touch.

02

Build

Tested with operators on historical events.

03

Deploy isolated

Edge or air-gapped, inside the right zone.

04

Update by bundle

Signed updates through your change process.

Questions

Common questions.

Can AI for utilities run without internet access?

Yes. The models are open-weight and run entirely on hardware you control, including air-gapped networks and edge servers at substations. Updates arrive as signed bundles that pass through your change management process. Nothing calls an outside model API.

Is the system NERC CIP compliant?

Compliance belongs to the registered entity, so we build the system to support your CIP program. That means deployment inside the correct perimeter, access tied to your authorization records, baseline and change documentation, and full logging. Your compliance team decides how each component is classified.

Will the AI control grid equipment?

No. The systems we build read records and draft documents for people to review. They do not write to SCADA, EMS or protection systems. That boundary is set during scoping and enforced in the architecture, so the model has no path to issue control commands.

What data sources does it use?

Typical sources are controlled procedure libraries, equipment manuals, asset management and work order systems, OMS records, SCADA event exports, inspection reports and compliance records. We read through exports or existing interfaces approved by your security team.

Can field crews use it on a truck or at a substation?

Yes. Smaller models can run on a laptop or a ruggedized edge server with a local copy of approved documents. Crews get answers without a network connection. Usage logs sync back through your approved path when the device reconnects.

Is this useful for gas and water utilities too?

Yes. Procedure search, asset knowledge and compliance evidence apply to gas and water operations as well. The rules differ, such as pipeline safety or drinking water requirements, so we map the relevant obligations during scoping and build controls to support your program.

What does private AI cost compared with a cloud AI service?

There are no per-seat or per-token fees. Cost comes from the build, which is quoted per phase after a fixed-fee discovery sprint, and from hardware or a dedicated cloud environment. We model both options during discovery so you can compare them.

Start here

Submit a job card.

Tell us the workflow and where the data lives. An engineer, not a salesperson, replies within one business day with a first take on architecture and cost.

Job cardLLM.CO · FORM 704-A
Practice
Where should it run?
Do not fold, spindle or mutilate