Systems and records
Energy contractor handoff data: what must survive the operator-contractor seam
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
Six threads should survive every operator-to-contractor handoff: the asset's identity, the energy state it was handed over in, the authority the contractor worked under, the agreed scope, readings before and after with every correction, and the return-to-service decision. Link them per job across the work order, permit log, qualification files and historian, record who owns each piece, and screen out infrastructure detail before any reuse.
License terms
Energy contractor handoff
Key takeaways
- A handoff dataset links six threads per job: asset identity, energy state, authority, scope, readings with corrections and the return-to-service decision.
- Lockout, power-line, process safety and pipeline qualification rules already force records at the operator-contractor seam.
- Holding a contractor's report does not mean you may license it; the service agreement decides.
- Every label needs the procedure version, qualification status and reading revision in force on the job date.
- Protection settings, network diagrams, security details and open vulnerabilities stay out; the workflow and outcome usually survive the screen.
What evidence should survive a handoff between operator and maintenance contractor?
Energy contractor handoff data is only useful if six threads survive the seam: the asset's identity, the energy state it was handed over in, the authority under which the contractor worked, the agreed scope and terms, the readings before and after the job with every correction, and the return-to-service decision. If any one of them is missing, nobody can replay what the operator knew, what the contractor was told and why the equipment went back into service.
Most plants and utilities already hold these records, but in different systems owned by different parties. The work order sits in the operator's maintenance system, the isolation record in a permit log or lockbox register, the qualification evidence in the contractor's training files, and the readings in a historian that may have been corrected after the fact. A handoff dataset is the set of links between them, not any single export.
This page gives a matrix for building those links, the dated rules that change what a contractor may do next, and the confidentiality line that keeps infrastructure detail out. It is written for operations leaders at generators, utilities, pipelines and processing plants who are deciding whether their operator-contractor records can become a licensed dataset, and what must happen first.
Why the closed work order is the weakest record of the handoff
A closed work order tells you a job was finished, not how responsibility moved. Status fields in maintenance systems are set for workflow reasons: a planner closes the order when the invoice is approved, a supervisor closes a batch at month end, or the contractor's own system closes its copy days before the operator's. None of that records who held the energy isolation at each moment or what condition the asset was in when the contractor left.
The handoff lives in the surrounding records. Permit and lockout logs show when control of the energy state changed hands. Job briefings and hazard notices show what each party told the other. Contractor field reports carry findings the operator may never have entered into its own system, and historian data shows whether the equipment behaved as expected once it returned to service.
For an AI developer, that surrounding evidence is the point. A model that drafts a work package, checks a permit or flags an incomplete closeout needs to see the decision and the evidence that justified it. A dataset of closed orders alone teaches a model to predict that work orders get closed.
Which safety rules already force a record at the seam?
Several U.S. safety rules require the operator and the contractor to exchange information or keep records at exactly the points where work changes hands, which makes them a reliable backbone for a handoff dataset. The table summarizes what each rule requires and the record it tends to leave. Confirm the current text for your sites, because the applicable rule depends on the facility and the work.
| Rule | What it requires at the seam | Record it usually leaves | Use in a handoff dataset |
|---|---|---|---|
| OSHA 1910.147(f)(2), outside personnel | The on-site employer and the outside employer inform each other of their lockout or tagout procedures | Procedure exchange record, contractor orientation sign-off | Shows which energy control program governed the job |
| OSHA 1910.147(f)(4), shift or personnel changes | Specific procedures keep lockout or tagout protection continuous during shift or personnel changes | Lock transfer entries, job-lock or master tag sign-on and sign-off | Timestamps the moment control of the energy state moved |
| OSHA 1910.147(c)(6)(ii), periodic inspection | Certification naming the machine, the inspection date, the employees included and the inspector | Annual inspection certificate per procedure | Links a procedure version to an inspection date |
| OSHA 1910.269(a)(3), host and contract employers | The host informs contractors of known installation characteristics and conditions; contractors report unanticipated hazards within 2 working days | Pre-job information transfer, contractor hazard reports | Captures what each side knew and when |
| OSHA 1910.119(h), process safety contractors | The host informs contractors of known fire, explosion or toxic release hazards and keeps a contract employee injury and illness log | Contractor evaluation, hazard briefing, injury and illness log | Hazard briefing is usable; the injury log stays out |
| 49 CFR 192.807, pipeline operator qualification | Records identify the individual, covered tasks, dates of current qualification and the qualification method; prior records kept five years | Qualification records per individual and covered task | Proves the person was qualified for the task on the job date |
The multi-party rights and workflow evidence matrix
The matrix below is the asset: one row per evidence element, with who holds it, what it proves, the rights question to answer before reuse and the default treatment in a licensed dataset. Use it as a column checklist when you assemble a sample of handoff cases, and record a treatment for every row even when the answer is exclude.
Equipment identity works best when it follows a published vocabulary. ISO 14224 defines equipment, failure and maintenance data categories, including equipment taxonomy, failure cause and maintenance action, for petroleum, petrochemical and natural gas facilities; power and utility teams can borrow its structure even where the standard does not formally apply.
| Evidence element | Usually held by | What it proves | Rights question before reuse | Default treatment |
|---|---|---|---|---|
| Asset ID, class and location tag | Operator maintenance system | Which equipment the job touched | Does the tag reveal protected infrastructure detail? | Keep class; replace site and tag with stable pseudonyms |
| Work order, scope and priority | Operator | What was asked and why | Operator-owned; check confidentiality clauses with the contractor | Keep |
| Contract or purchase order terms | Operator procurement and contractor | Agreed scope, exclusions and acceptance criteria | Both parties' confidential terms | Keep scope and acceptance fields; drop rates and commercial terms |
| Energy isolation and permit record | Operator permit log, sometimes contractor | Who held control of the energy state and when | Joint record; names are personal data | Keep events and roles; pseudonymize people |
| Contractor qualification evidence | Contractor | The person was qualified for the task on the date | Contractor-owned personal records | Keep as a yes, no or unknown flag with a date |
| Readings before and after, with revisions | Operator historian | Condition at handoff and after return to service | Operator-owned; may disclose design limits | Keep values and every revision with its timestamp; generalize limits if sensitive |
| Hazard notices exchanged | Both | What each side was told | Joint; may name hazards at specific sites | Keep the hazard type; remove precise location detail |
| Contractor findings report | Contractor | What was found that the order did not expect | Contractor may own its report; check the service agreement | Keep only with the contractor's written permission or a clear contract grant |
| Return-to-service approval | Operator | Who accepted the work and on what evidence | Operator-owned | Keep role, time and acceptance basis |
| Injury, illness or medical records | Operator and contractor | Safety outcomes for individuals | Sensitive personal data | Exclude |
Whose record is it: separating access, ownership and the right to license
Holding a copy of a record does not give you the right to license it. In a two-party job, four different questions apply to each row of the matrix: who can access it today, whether privacy rules allow it to be reused for a new purpose, who owns it, and whether any contract grants or restricts the right to license it. The answers often differ for the same document.
A contractor's field report is the common trap. The operator may store it in its own system and have every right to use it for running the plant, while the service agreement says the report remains the contractor's work product or is confidential to the job. Read the master service agreement and the order terms before treating any contractor document as licensable, and get written permission where the contract is silent.
Technician names, badge numbers, qualification histories and timesheets are personal data whoever holds them. Pseudonymizing them keeps the sequence of who did what without identifying anyone, but de-identification alone does not create a right to license. It reduces privacy risk on records you are otherwise entitled to share.
Which dated rule, reading revision or safety boundary changes the next step?
The rule that governs a handoff is the one in force at the time of the job, so every label in the dataset must carry the date and version it was judged against. A model trained on today's procedure applied to last year's job will learn the wrong answer.
Steps
Which dated rule, reading revision or safety boundary changes the next step
Four kinds of dated fact change the permitted next step, and each needs its own field rather than a note in free text.
Checklist · 4 items
- Procedure version: the energy control procedure, permit form or job plan revision in effect on the job date, with its last periodic inspection date.
- Qualification status: whether the individual was qualified for that covered task on that date, and by which method, rather than whether they are qualified now.
- Reading revision: the reading as recorded at handoff, every later correction, who made it and why. If a corrected reading would have blocked return to service, the case becomes an exception, not a clean success.
- Safety boundary: any hold, abnormal operating condition or reported hazard that stopped or narrowed the work, with the time it was raised and the time it was cleared.
0 of 4 ticked. Tick each item as you go.
Drawing the confidentiality line around infrastructure detail
Keep anything that would help someone attack the facility out of the dataset, even when it sits inside an ordinary maintenance record. Federal rules give a working definition: critical energy infrastructure information is specific engineering, vulnerability or detailed design information that relates to producing or delivering energy, could be useful in planning an attack, is exempt from FOIA disclosure and goes beyond the general location of the infrastructure.
Electric entities subject to NERC CIP-011 must already identify BES Cyber System Information and protect it in storage, transit and use. Records that touch protection systems, control networks or cyber assets should be screened by whoever owns that program before they reach any sample.
In practice the screen removes or generalizes a short list of fields: network and control diagrams, setpoints and protection settings, security system details, exact coordinates and single-line references, and vulnerability findings that remain open. The workflow, the roles, the timing and the outcome usually survive the screen, and those carry most of the training value.
Worked scenario (illustrative): a feed pump seal job that crossed a shift change
This example is illustrative; the counts and timings are invented to show how the matrix works and describe no real facility. A generating station brings in a mechanical contractor to replace a seal on a boiler feed pump. The job runs across one shift change and returns to service the next morning.
Assembled as a handoff case, it produces 11 linked events: the work order, the pre-job hazard briefing, two isolation entries by the operator, one contractor lock application, a lock transfer at shift change, a contractor findings note reporting shaft wear beyond what the order expected, a scope change approved by the operator, the contractor lock removal, a vibration reading after restart and the return-to-service approval.
Two of those events need special handling. The vibration reading was corrected about 40 minutes after it was first recorded because a sensor channel had been mapped to the wrong pump; the case keeps both values with timestamps and labels the outcome uncertain until the corrected value is confirmed against the next scheduled reading. The findings note is the contractor's document, so the case includes it only because the service agreement grants the operator a license to use job reports for internal and data purposes, which counsel confirmed.
What leaves the case: technician names (replaced with role pseudonyms), the hourly rates on the purchase order, the pump's location tag and the protection settings quoted in the job plan. What stays: the sequence, the roles, the hazard type, the scope change and its reason, both readings and the acceptance basis. A model trained on such cases can learn to flag a return to service that rests on an unconfirmed reading.
Preparing operator and contractor records for a licensing review
Records like these are a natural fit for licensing when the operator can show it holds the rights to every included row and has applied the confidentiality screen. For operators that go ahead, SourceX turns the selected records into a licensed AI dataset through rights review, contracting, preparation and delivery, starting with a short company assessment that asks for no data.
No data leaves the operator until it has signed off on the scope and terms and executed the agreement. Large historian exports or multi-year maintenance archives do not need to be copied to a new host: they can stay in the operator's own storage or ship on encrypted drives. Before an assessment, it helps to have one sample of ten to twenty handoff cases assembled with the matrix, the contractor agreements that cover them and a note of which systems hold each row.
Frequently asked questions
Who owns maintenance records created by a contractor at an operator's site?
It depends on the service agreement. Operators usually own their own work orders, permits and historian data, while a contractor's field reports, photos and test sheets may remain the contractor's work product or be confidential to the job. Read the agreement and get written permission where it is silent before licensing contractor documents.
Can lockout and tagout records be used in an AI dataset?
Usually yes once people are pseudonymized and site detail is generalized. The events, roles and timings are what make them useful, because they show when control of the energy state changed hands. Keep the procedure version and inspection date with each case so the record can be judged against the rule in force.
Do corrected sensor readings need to be kept, or only the final value?
Keep both. The value recorded at handoff is what people acted on, and the correction explains whether that decision was sound. A dataset that only keeps the final value hides the cases where equipment went back into service on a wrong reading.
What counts as critical energy infrastructure information in maintenance records?
Under the FERC definition, it is specific engineering, vulnerability or detailed design information that could help plan an attack and goes beyond general location. In maintenance records that often means protection settings, control and network diagrams, security details and open vulnerability findings. Remove or generalize them before sampling.
Is a single work order export enough for a handoff dataset?
No. A work order shows the request and the closure, but the handoff lives in permit logs, hazard notices, contractor reports, qualification records and historian readings. The dataset is the set of links between those records for each job.
Sources
- OSHA 1910.147 requires on-site and outside employers to exchange lockout or tagout procedures, continuity procedures at shift changes and certified periodic inspections naming machine, date, employees and inspector. Source
- OSHA's lockout/tagout inspection directive describes job-locks and master tag sign-on and sign-off as ways to keep isolation continuous across shifts. Source
- OSHA 1910.269(a)(3) requires host employers to inform contract employers of known installation characteristics and conditions, and contract employers to report unanticipated hazards within 2 working days. Source
- OSHA 1910.119(h) requires the host employer to inform contractors of known fire, explosion or toxic release hazards and to keep a contract employee injury and illness log. Source
- 49 CFR 192.807 requires operator qualification records identifying the individual, covered tasks, dates of current qualification and method, with prior records kept for five years. Source
- ISO 14224:2016 sets equipment, failure and maintenance data categories for collecting reliability and maintenance data in petroleum, petrochemical and natural gas industries. Source
- 18 CFR 388.113 defines critical energy infrastructure information as specific engineering, vulnerability or detailed design information meeting a four-part test. Source
- NERC CIP-011 requires responsible entities to identify BES Cyber System Information and protect it in storage, transit and use. Source
See if your company qualifies
A short company assessment. No data uploads are needed.