Skip to content

Privacy and preparation

Energy safety exclusion dataset: separating operational data from safety instructions

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Separate them by what each record tells a person to do, not by which department wrote it. Billing, metering, tariff, contract and work order status records can train operational models; energy control procedures, switching steps, job briefing content and critical infrastructure details stay out or are reduced to a masked reference. An energy safety exclusion dataset records that decision for every record class, with a domain reviewer's sign-off.

Redaction

Energy safety exclusion

This page covers energy safety exclusion dataset: separating operational data from safety instructions.Illustrative

Key takeaways

  • Classify utility records by whether they state a fact or instruct someone to control energy; only facts belong in operational training data.
  • Lockout, switching, clearance and job briefing content are excluded or reduced to a masked reference that a procedure applied.
  • Critical energy infrastructure information and BES Cyber System Information are a second, separate boundary decided by compliance and security staff.
  • Administrative tasks depend on dated facts: reading revisions with quality codes, tariff effective dates, contract terms and status history.
  • Every include, transform or exclude decision needs a named reviewer and a versioned framework.

How do you separate operational AI training data from safety-critical instructions?

Classify every record by its function: does it describe an administrative fact, or does it instruct someone how to control energy, operate equipment or work near it? Facts can be licensed for training after review. Instructions are excluded, or kept only as a pointer that says a procedure existed without reproducing it.

This matters because utility and energy records are mixed. A single work order can hold a customer account number, a corrected meter reading, a tariff code and a step from a lockout procedure. A model trained on the whole order may learn to generate or paraphrase the safety step, which is the one thing no operational assistant should do without the qualified person and the current approved procedure.

The framework below gives each record class a zone (include, transform or exclude), the rule that places it there and the reviewer who confirms it. Tasks built from included records are bounded to administrative outcomes: which reading is final, which tariff applies, whether a work order closed, what a contract term says. No task asks the model to choose an operating step.

Which utility records count as safety-critical instructions?

A record is a safety-critical instruction when following it, or following a wrong version of it, could expose someone to hazardous energy. In U.S. general industry and electric power work, two OSHA standards describe the content that falls in this group.

At a glance

Which utility records count as safety-critical instructions

OSHA's lockout and tagout standard, 29 CFR 1910.147, requires written energy control procedures that set out the scope, purpose, authorization, rules and techniques for controlling hazardous energy, including steps for shutting down, isolating, blocking and securing machines, placing and removing lockout devices, and testing to verify the controls work. The electric power standard, 29 CFR 1910.269, requires a job briefing before each job that covers hazards, work procedures, special precautions, energy source controls and personal protective equipment, with additional briefings when significant changes that might affect safety occur.

  • Energy control and lockout procedures, including machine-specific steps and verification tests.
  • Switching orders, clearances, hold tags and the sequence for isolating or restoring a line or unit.
  • Job briefing content: the hazards, precautions and energy source controls discussed for a specific job.
  • Energized work methods, minimum approach distances applied to a job, and protective equipment selections.
  • Any free-text note that tells a crew what to do with equipment, even when it sits inside a billing or customer ticket.

Why is infrastructure confidentiality a separate boundary?

Some records are excluded not because they instruct anyone, but because they describe infrastructure in a way that could help someone attack it. That is a separate test with its own reviewers, and a record can fail it while being entirely administrative.

FERC's regulation at 18 CFR 388.113 defines critical energy infrastructure information as specific engineering, vulnerability or detailed design information about existing or proposed critical infrastructure that relates to energy production, generation, transportation, transmission or distribution, could be useful to a person planning an attack, and does more than give the general location of the infrastructure. For bulk electric system entities, NERC's CIP-011 standard requires a method to identify BES Cyber System Information and procedures to protect it in storage, transit and use.

In practice, keep one-line diagrams, network topology, protection settings, cyber asset inventories and vulnerability findings out of any training set, and coarsen asset identifiers and locations in the records you do include. Whether a specific record is CEII or BCSI is a determination for the utility's compliance and security staff, not the dataset team.

Which zone does each record class fall into under the reviewed framework?

The framework is a table every record class must pass through before export, versioned (for example v1.0, dated 2026-10-18) so that a later change in scope is visible. The zones are: include as is after privacy review; transform, meaning include with fields removed, masked or coarsened; and exclude.

Use it as a starting point. A qualified energy operations reviewer and the utility's compliance owner should confirm each row for their own systems before any record leaves.

Which zone does each record class fall into under the reviewed framework?
Record classZoneRule appliedConfirming reviewer
Interval and billing readings with quality codesIncludeKeep reading value, period, quality code and revision history; remove customer identityMetering or billing lead plus privacy reviewer
Tariff and rate rider assignments with effective datesIncludeKeep tariff and rider codes with their dates; public tariffs need no maskingRates or regulatory affairs
Supply and service contract termsTransformKeep term types, dates and obligations; mask counterparties and pricingContracts owner and counsel
Work order headers and status historyTransformKeep type, status, timestamps, approvals; coarsen location and asset id; drop free-text crew notesOperations supervisor
Work order crew notes and attachmentsExclude by defaultRelease only notes a reviewer confirms contain no procedure, switching or hazard contentSafety professional
Energy control, switching and clearance recordsExcludeKeep only a masked reference that a procedure applied, with no stepsSafety professional
Job briefing recordsTransformKeep date, job type and completion flag; drop hazards, precautions and controls discussedSafety professional
Diagrams, topology, settings, cyber asset listsExcludeTreat as potential CEII or BCSI; never sampleCompliance and security owner

Which dated rule, reading or asset fact changes the permissible next step?

In administrative tasks, the next permissible step usually turns on a date or a revision: which reading is final, which tariff was in force, which contract term applied. Each included record must carry those dates, or the task becomes ambiguous.

Meter data is the clearest example. The NAESB REQ.21 Energy Services Provider Interface schema, as published in the Green Button Alliance's open-source implementation, lets each interval reading carry one or more reading quality codes. The codes distinguish, among others, data that passed all validation checks, data replaced or approved by a human, values estimated from historical data, values interpolated from neighboring readings, data that failed checks, and data validated and possibly edited or estimated under approved procedures. The same schema carries a tariff profile and a list of rate options applied to it. A task that asks which reading should drive a rebill is only answerable if those codes and their revision times survive the export.

Contracts and work orders follow the same logic. A supply or service agreement is often amended several times, and the amendment in force on the date of the event decides the obligation; a work order may be reopened after closure, and the reopening time decides which team owns the correction. Export the full revision trail with timestamps, then let the task state the date it is asking about, so a reviewer can check the answer against the record that applied on that day rather than the one that applies today.

Which dated rule, reading or asset fact changes the permissible next step?
Dated factWhy it changes the answerField to keepCommon export mistake
Reading revisionAn estimated value replaced by an actual read changes the billReading value per revision with quality code and timestampExporting only the latest value
Tariff effective dateA rate change mid-period splits the billTariff and rider codes with start and end datesApplying today's tariff to the whole history
Contract term dateRenewal or expiry changes the obligationTerm start, end and notice datesDropping amendments
Work order status timeClosure before or after a read affects who owns the correctionStatus history with timestampsKeeping only the final status
Approval recordAn adjustment above a limit needs a named roleApprover role and time, not nameRemoving approvals with personal data

How is an illustrative corrected meter read with a field work order scoped?

This example is illustrative; the utility, identifiers and counts are invented. A commercial account receives an estimated reading for one billing period because the meter could not be read. A field work order is opened to replace a failed meter. The crew notes on that order include the steps the crew followed to isolate the service before the swap.

The resulting training task asks: given the reading history, the work order status and the tariff assignment, which reading should the rebill use and what tariff applies? The answer depends on four dated facts: the estimated reading's quality code, the time the replacement meter's first actual read arrived with its own quality code, the work order closure time, and a tariff rider that started partway through the period.

Under the framework, the readings, tariff assignments and work order header go in. The crew notes are excluded, and the task packet carries only a masked reference stating that an energy control procedure applied to the order. The model learns how to settle a rebill. It never sees, and is never asked to produce, the isolation steps.

A second, harder variant of the same task adds a contract term: the account sits on a negotiated supply agreement whose amendment changed the rate basis during the period. The model has to find the amendment effective on each day and split the bill accordingly. Again, nothing in the packet concerns how the meter was made safe to replace.

The packet records the outcome as well: the corrected bill that was issued and whether the customer disputed it, read from the billing system after the fact.

What if a safety record is also an administrative fact?

Some safety records are also administrative facts that a model may legitimately need, such as whether a job briefing happened or whether a periodic procedure inspection is overdue. Keep the fact and drop the content.

OSHA requires the lockout standard's energy control procedures to be inspected at least annually, and its electric power eTool says the standard does not specifically require a written record of job briefings, though keeping one is a best practice. A scheduling or compliance-tracking task can use a due date, a completion flag and a job type without any of the hazards, steps or controls that were discussed.

The limit of this exception: a task built on these facts must not ask the model whether work may proceed. That question belongs to the qualified person on site and the approved procedure in force that day.

Who signs off, and when should the scope shrink?

Each zone decision needs a named role, and some situations call for narrowing the dataset rather than reviewing harder.

  • A qualified energy operations or safety professional confirms the exclude and transform rows and spot-checks released free text.
  • The compliance or security owner decides CEII and BCSI questions; the dataset team does not.
  • Counsel reviews contracts, regulatory confidentiality and any obligations to customers or regulators that limit sharing.
  • A privacy reviewer confirms customer identifiers are removed or coded.
  • Narrow the scope to one record class, such as reading revisions and rebills, when free text cannot be reliably screened.
  • Pause the export if a sample turns up a procedure step, a diagram or an asset vulnerability in a class marked include.

Can administrative energy records be offered under license?

Reading revisions, tariff assignments and work order status histories can be useful training material for billing, customer service and operations assistants, but rights come first. Access to the systems, customer privacy permissions, ownership of the records and contract terms with vendors or partners are four separate questions, and de-identification does not by itself create a right to license.

Once the exclusion framework has done its work, SourceX can take the remaining administrative classes, such as reading revisions, tariff assignments and work order headers, through rights review, contracting, preparation and delivery as a licensed AI dataset. The utility signs off on scope and terms first; customer identifiers are de-identified by SourceX through approved processing routes; and large interval-data exports are never hosted by SourceX but stay on the utility's storage or travel on encrypted drives.

Frequently asked questions

What is an energy safety exclusion dataset?

It is a training or evaluation dataset built from energy or utility records with a documented rule for every record class: include, transform or exclude. Safety-critical instructions and critical infrastructure details are excluded or reduced to masked references, and each decision carries a reviewer's sign-off and a version date.

Can lockout or switching procedures ever be used to train an AI model?

Not in an operational dataset of this kind. Those procedures are machine-specific, change over time and must be applied by qualified people under the approved current version. A dataset can record that a procedure applied to a job, without reproducing its steps.

Is every utility record that mentions an asset CEII?

No. FERC's definition covers specific engineering, vulnerability or detailed design information that could help plan an attack, not general location. But the call belongs to the utility's compliance and security staff, so coarsen asset references and ask them before export.

Why keep estimated and replaced meter readings instead of only final values?

Because the training task is about the decision, and the decision depends on which value was estimated, which was actual and when each arrived. Quality codes such as estimated, interpolated or replaced by a person are what make a rebill answerable.

Who should review the scope and exclusion framework?

A qualified energy operations or safety professional for instruction content, the compliance or security owner for infrastructure information, a privacy reviewer for customer data and counsel for contracts and regulatory confidentiality.

Sources

  • OSHA's lockout and tagout standard requires written energy control procedures covering shutdown, isolation, lockout devices and verification, with periodic inspection at least annually. Source
  • OSHA's electric power standard requires a job briefing before each job covering hazards, work procedures, special precautions, energy source controls and protective equipment. Source
  • OSHA's electric power eTool says a written record of job briefings is not specifically required by the standard but is a best practice. Source
  • FERC's regulation defines critical energy infrastructure information as specific engineering, vulnerability or detailed design information useful to planning an attack, beyond general location. Source
  • NERC's CIP-011 standard requires entities to identify BES Cyber System Information and protect it in storage, transit and use. Source
  • The NAESB REQ.21 ESPI schema lets interval readings carry quality codes such as validated, human-replaced, estimated or interpolated, and carries tariff profiles with rate riders. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies