[ Industry pack · Energy & Utilities ]

Energy & UtilitiesEvery change checked against its assets and zones.

The Energy & Utilities pack runs an advisor workflow that connects safety functions, OT zones and conduits, grid cyber assets, requirements, configuration changes, tests, approvals, maintenance and evidence in Azure DevOps. It prepares the impact and the evidence. Utility engineers and operators decide.

No card required. Your data stays in your Azure DevOps tenant.

Energy & Utilities engineeringDevOps Engineer Agent avatar
  • IEC 61508
  • IEC 62443
  • NERC CIP
  • NIS2
  • ISO 55001
[ The engineering reality ]

Changes touch assets, zones and critical functions.

Utility engineering brings together safety, grid reliability, OT cybersecurity, asset lifecycle, field configuration, maintenance, vendor systems and regulatory evidence. A configuration change is never only a code change. It has to be judged against the asset it runs on, the zone and conduit it sits in, the critical function it supports, the operating constraints around it, and the maintenance or outage window it is allowed to use. Those facts are held by different teams in different systems, so the impact picture is put together by hand each time.

  • 01

    Impact is assembled by hand.

    Finding the assets, zones, safety functions and procedures a configuration change touches means asking several teams. Something is usually missed.

  • 02

    OT findings pile up.

    Security findings arrive faster than they can be ranked by asset criticality, exposure and maintenance constraints, so the queue is worked in arrival order.

  • 03

    Field readiness is checked late.

    Procedures, test cases, dependencies and approvals are confirmed just before commissioning, when a gap costs an outage window.

  • 04

    Runbooks lag the change.

    After an approved change, maintenance and recovery procedures are updated weeks later, if at all, and the evidence trail breaks.

[ What the pack configures ]

Four layers tuned to grid and OT work.

The advisor works with the classifications, relationships, frameworks and gates that utility change is reviewed against. You edit each layer in plain English and add your own procedures.

  1. 01 Classification

    Safety, grid and OT classes.

    Safety integrity relevance, grid and BES cyber-system context, OT zone and conduit, asset criticality, service and customer impact, environmental and operational risk, and change criticality.

  2. 02 Traceability model

    Asset need to maintenance evidence.

    Operational or asset need, requirement or control, safety or security function, design or configuration, implementation or change, test and commissioning, approval, then operational and maintenance evidence.

  3. 03 Standards & frameworks

    The standards your programme cites.

    IEC 61508, IEC 62443, NERC CIP where applicable, NIS2 where applicable, ISO 55001 asset-management context, and your own grid, safety, OT and change-control procedures.

  4. 04 Lifecycle gates & evidence

    From hazard review to field evidence.

    Hazard and risk review, OT security review, configuration and change approval, factory and site acceptance, commissioning, outage and maintenance readiness, and evidence completion.

[ Traceability model ]

The Energy & Utilities chain, kept intact.

A configuration change without a linked safety or security function is caught, and the link is restored before field work.

  1. Asset need
  2. Requirement
  3. Safety / security
  4. Design / config
  5. Change
  6. Commissioning
  7. Approval
  8. O&M evidence
[ Priority workflows ]

Where the advisor does the work.

Six workflows configured for utility change. Each starts from a trigger your team set, reads only the scope you allow, and stops where your procedures need an authorised person.

  • Requirement and control mapping

    Map safety, grid, OT security and asset obligations to their implementation and evidence, and report obligations with no link.

    Requirements Engineer Agent
  • Configuration change impact

    Identify the assets, zones and conduits, safety functions, interfaces, procedures, tests and operations a proposed change affects.

    DevOps Engineer Agent
  • OT security finding triage

    Rank findings by asset criticality, exposure, operational impact, compensating controls and maintenance constraints, and prepare the remediation work.

    Compliance Officer Agent
  • Test and commissioning readiness

    Check configuration, procedures, test cases, dependencies, approvals and evidence before any field activity is scheduled.

    QA Engineer Agent
  • Maintenance and runbook updates

    After an approved change, prepare the procedure, owner, safety, security and recovery updates for review.

    Release Manager Agent
  • Evidence and audit readiness

    Audit links, approvals, baselines, tests, exceptions and current evidence, and hand a clean package to qualified reviewers.

    Compliance Officer Agent
[ Agent roles ]

An advisor, plus energy persona agents.

The supplied catalog represents energy and utilities as a broad industry advisor. The Agent Library also has an Oil & Gas / Energy persona section with 13 role-based agents for process control and safety instrumented systems, mapped to your process template with Compatibility Alignment.

Energy & Utilities roles in the catalog

  • Energy Utilities Advisor
[ Example run ]

An OT configuration change is proposed.

An engineer raises a change for an OT configuration, and a conditional trigger on the new change item starts the advisor. It reads the change and its links, then identifies the affected assets, zones and conduits, safety or grid functions, cybersecurity controls, test and commissioning requirements, outage constraints, procedures and approvals. It prepares the impact summary and the evidence tasks, and posts a finding where an approval or test is missing. The run pauses on an Open Task for the named OT security reviewer. After the change is carried out, the advisor verifies the record, and the full history stays in Job Explorer.

dev.azure.com/contoso · Boards · CHANGE 618

run started · CHANGE 618 created

class: OT zone 3 · asset critical

tracing: 4 assets · 2 conduits · 1 SIF

finding: no site acceptance test

checkpoint · OT security review

record · impact on change item

ApproveEditReject
  • ✓ Assets and conduits traced
  • ✓ Safety and grid functions
  • ! Site acceptance test linked
  • ✓ Outage window confirmed
  • ! OT security approval
ILLUSTRATIVE RUN · EVERY RUN LANDS IN YOUR JOB LOG
[ Human responsibility ]

The advisor prepares. Authorised people act.

The advisor maps, traces, checks and prepares evidence within the scope you configure. Utility engineering, operations, safety, OT security, asset, reliability, maintenance and regulatory authorities keep responsibility for classification, risk, field execution, operational acceptance and compliance. Required Approval holds the run until the named person decides.

[ Trusted by Microsoft and industry leaders ]

  • Info-Tech Research Group Top Rated 2025
  • Info-Tech Research Group Emotional Footprint Champion 2025
  • SoftwareReviews Champion 2025, Requirements Management
[ FAQ ]

Energy & Utilities questions.

The supplied catalog represents this industry as a broad advisor rather than a multi-role pack. The Agent Library adds an Oil & Gas / Energy persona section with 13 role-based agents for process control and safety instrumented systems.

Not by default. Any connection would need verified integrations and an approved security architecture. The advisor works on the engineering record in Azure DevOps.

No. It can support the configured analysis, but qualified functional-safety personnel make and approve the determination.

Yes. Attach them as knowledge, or turn on Bring Your Own Data so the advisor retrieves from your documents, Azure DevOps queries and wiki pages during the run.

No. Agents run inside your Azure DevOps environment and read only the context their workflow is scoped to. Your project data is not used to train models.

Credits are $0.01 each, pooled across your organization, with no per-user fees. A rule-shaped readiness check can run as an Execution Agent for a flat 4 credits. Agents pause at zero.

Check one change against its assets this week.

Start a free trial with 2,000 credits, no card required. Or bring a real configuration change, OT finding or evidence gap to a 30-minute demo and watch the impact, the approval and the record live.