Industry Vocabulary Reference

Energy & Utilities

Energy and utilities fields cover grid assets, outages, demand response, markets, maintenance, and emissions workflows. They describe recorded activity without authorizing changes to operational systems.

Back to industry coverage library

This page shows selected examples and categories. Download the JSON for the complete vocabulary, including every field, permitted value, and policy pattern in this catalog.

How to use this reference

1. Start with the core file if you need the cross-industry governance baseline.
2. Choose an industry file for its workflow fields and permitted values.
3. Match the OTel attributes to the policy paths your rules use, then verify the recorded fields in a test session.

Catalog context

Start with a bounded workflow such as outage review or maintenance planning. Record the requested action, responsible operator, and confirmed result.

Risk note: Preserve operational safety and access controls outside the tracing system. Assess critical-infrastructure requirements against the affected assets and intended use of the AI system.

Vocabulary file

• Download filename: 08_vertical_energy_utilities.json
• Kind: vertical

OTel namespaces

Referenced standards

These references explain the catalog's context. A listed standard does not establish that a configured application meets its requirements.

• IEC 61968, Application Integration at Electric Utilities, System Interfaces for Distribution Management
• IEC 61970, Energy Management System Application Program Interface (EMS-API), Common Information Model (CIM)
• IEC 61850, Communication Networks and Systems for Power Utility Automation
• IEC 61400-25, Wind Turbines, Communications for Monitoring and Control
• IEC 62351, Power Systems Management and Associated Information Exchange, Data and Communications Security
• NERC CIP v7, Critical Infrastructure Protection Standards (CIP-002 through CIP-014)
• NERC FAC-001/FAC-002, Facility Connection and Planning Standards
• NERC EOP-004, Event Reporting
• OpenADR 2.0b, Open Automated Demand Response (OpenADR Alliance)
• IEEE 1547-2018, Standard for Interconnection and Interoperability of DERs with Electric Power Systems
• FERC Order 2222, Participation of Distributed Energy Resource Aggregations in Organized Energy Markets (2020)
• FERC Order 881, Managing Transmission Line Ratings (2021)
• FERC Order 3052, Cybersecurity Incentives (2024)
• ENTSO-E Network Codes, EU transmission network operational standards
• EU Electricity Directive 2019/944, Internal market for electricity
• EU Renewable Energy Directive III (RED III) 2023/2413, 42.5% renewable target by 2030
• EU ETS (Emissions Trading System), EU Allowance Registry under EU ETS Directive 2003/87/EC (as amended)
• EPA 40 CFR Part 75, Continuous Emissions Monitoring Systems (CEMS)
• EPA Clean Power Plan / Good Neighbor Rule (2024 revisions)
• API RP 1173, Pipeline Safety Management Systems
• PHMSA 49 CFR Part 192/195, Pipeline Safety Regulations
• AWWA Cybersecurity Guidance, Water sector OT security
• EPA EPCRA Section 313, Toxic Release Inventory reporting

Source references

• https://cimug.ucaiug.org/ 
• https://www.nerc.com/pa/Stand/Pages/CIPStandards.aspx 
• https://www.openadr.org/ 
• https://www.ferc.gov/ 
• https://www.entsoe.eu/network_codes/ 
• https://www.epa.gov/airmarkets 
• https://www.phmsa.dot.gov/pipeline 

Subdomains

Implementation examples

• Grid Asset & Outage Management (IEC CIM): Grid Asset Operational Status. AI energy management agent monitors all BES asset statuses via CIM. 'Forced_outage' on a high-impact asset triggers automatic NERC EOP-004 assessment, initiates restoration workflow, and escalates to grid operations HITL. AI agent may not autonomously re-energise a 'de_energized' asset, crew clearance confirmation required. (Nerc Eop 004: NERC EOP-004, Disturbance reporting: 'forced_outage' on BES elements meeting reporting thresholds must be reported to NERC and regional entity)
• Grid Asset & Outage Management (IEC CIM): Switching Equipment State. AI distribution management agent executes fault isolation switching sequences. Each switching step is logged with the pre- and post-state. OPA policy blocks AI from closing a 'grounded' switch, crew clearance confirmation from safety system is required first. (Nerc Cip 010: NERC CIP-010, Configuration change management: autonomous AI switching on BES Cyber Systems requires approved change documentation)
• Grid Asset & Outage Management (IEC CIM): Outage Lifecycle State. AI outage management agent receives outage reports from AMI (Advanced Metering Infrastructure), customer calls, and SCADA alarms. Agent correlates reports, confirms outage boundary, and dispatches crew. OPA policy enforces that 'fully_restored' state requires meter-verified restoration confirmation, not just switch state change.
• Grid Asset & Outage Management (IEC CIM): Protection Relay Operation Status. AI grid monitoring agent detects relay operation from SCADA and classifies status. 'Reclose_failed_lockout' triggers immediate crew dispatch. 'Protection_inhibited_ai_action' is a critical flag indicating an AI agent has interfered with protection, requires immediate HITL escalation and is a NERC compliance event. (Nerc Prc 023: NERC PRC-023, Transmission relay loadability: relay settings affected by AI optimisation must comply with NERC PRC-023 loadability criteria)

Control ideas

These patterns describe possible controls, not active rules. Confirm applicability, implement the control, and test its effect on the application.

Enforce before the action

Pass the request and your business action to this function. The core SDK checks policy before the action runs and again before its result is released. A deny or review decision means the action never runs.

import { Veriproof } from '@veriproof/sdk-core';
import type { GovernedResult, IndustryFact, JsonValue } from '@veriproof/sdk-core';

const veriproof = Veriproof.fromEnv();

export async function runProtectedAction<TInput extends JsonValue, TValue>(
  request: TInput,
  action: (input: TInput, signal: AbortSignal) => Promise<TValue>,
): Promise<GovernedResult<TValue, TInput>> {
  // Catalog values for this vertical. Replace them with facts from the current workflow.
  const industry: IndustryFact[] = [
    { attribute: "energy.asset.operational_status", policyInput: "energy_asset_operational_status", value: "in_service" },
    { attribute: "energy.switching.state", policyInput: "energy_switching_state", value: "closed" },
    { attribute: "energy.outage.lifecycle_state", policyInput: "energy_outage_lifecycle_state", value: "reported" },
  ];

  // Policy runs before action() and again before the result is released.
  // A deny or review decision means action() never runs.
  return veriproof.govern(
    "energy.utilities.evaluate",
    request,
    ({ input, signal }) => action(input, signal),
    { industry },
  );
}

• Replace the sample values with facts from the current workflow. Rules read them under input.snapshot.industry.
• Test both permitted and blocked actions. Confirm that a blocked action never reaches your business function.
• Only completed, completed_with_warning, and transformed results carry a released value.

For review decisions, follow the Human Review guide to configure continuation. Observe remains available when you need to record activity without enforcing a decision.

Set up the Energy & Utilities example. See the API reference for TypeScript, Python, or .NET.

Selected vocabulary categories

This page uses the vocabulary JSON distributed with the documentation. Check its version when comparing it with an installed SDK.

Download the vocabulary JSON for offline review or automated comparisons.

Use the SDK reference for configuration and supported APIs. Keep vocabulary selection separate from the compliance team's assessment of applicable requirements.