Commissioning Documentation Handover: What Owners Should Receive
Send your test requirement — get a tailored solution and a quote within one working day.
A commissioning handover that transfers test results has transferred a fraction of what the owner needs. Substation commissioning documentation is valuable when it transfers evidence: the conditions, the instruments, the raw data and the as-installed configuration that will make every future measurement comparable. The difference between the two is usually discovered years later, when an asset behaves unexpectedly and the baseline cannot be reconstructed.
The handover package has one purpose that outranks the others. It establishes the reference condition of the asset at the moment it entered service, and it does so in enough detail that a measurement taken in ten years can be compared against it.
What owners should receive at handover
The package should contain the test results for every stage of commissioning, each with the conditions under which it was obtained and the standard applied. It should contain the as-installed settings and configurations for every device whose behaviour depends on them.
It should contain the evidence behind the results: raw traces, timed readings and instrument exports, stored in a format the owner can open. It should contain the deviations accepted during construction, with their justification and authorisation.
Finally, it should contain the operational material: the maintenance intervals with their basis, the identification of the instruments and methods for the periodic tests, and the as-built single line diagrams and layout drawings that the test results refer to.
Test results versus test evidence
| Item | What a result-only file contains | What evidence adds |
|---|---|---|
| Measured value | The number and the verdict | The conditions, and the reason the verdict was reached |
| Instruments | Sometimes the model | Model, serial number, calibration status and the chain components |
| Connection arrangement | Usually absent | The arrangement used, which determines what the value describes |
| Raw data | Absent, or a printed trace only | The underlying data, re-analysable with different processing |
| Standard applied | A name, sometimes without edition | The designation, part and edition used for the verdict |
| Deviations | Absent | What departed from the plan, why, and who authorised it |
The table describes the difference between a document that can be reviewed and one that can be audited. The second is what allows a future engineer to answer a question the commissioning team never anticipated.
As-built settings and configurations
Settings define the state the equipment is in for the rest of its life. Protection relay setting groups, charger float and boost voltages, alarm thresholds, tap changer control parameters and communication addresses all determine behaviour in service.
Recording them as installed, rather than as designed, is the requirement. Construction frequently produces a configuration that differs from the design in small ways, and a difference that is not recorded becomes an unexplained discrepancy the first time the equipment is tested.
Where a device stores its configuration in a file, the file itself belongs in the package. A settings list in a document is useful; the configuration file is what can be reloaded, compared and version-tracked.
Asset register linkage
Each record should be linked to the asset it describes in the owner’s asset register. That link is what allows a maintenance engineer to find the commissioning data for a specific transformer, breaker or battery years later without searching by project name.
The linkage should be by asset identifier rather than by location, because assets move during their life and locations are renumbered. Where the asset register uses a hierarchy of substation, bay and equipment, the commissioning record should identify its position in that hierarchy.
Where the owner’s register does not yet exist at handover, the commissioning package should propose the identifiers and the structure, rather than leaving the linkage to be reconstructed from drawings later.
Warranty and defect liability documents
The warranty and defect liability terms determine what the owner can require if a defect appears in the first period of operation, and the commissioning record is the evidence that the equipment was in a defined state when the period began.
The package should therefore include the warranty terms, the defect notification procedure and the period, and it should connect them to the commissioning results. Where a commissioning result was marginal and accepted, the acceptance should be recorded with its justification, because a marginal result that was accepted knowingly is a different situation from one that was overlooked.
The same applies to deviations. A deviation that was accepted in writing is part of the agreed condition of the equipment; one that was accepted informally tends to resurface as a defect claim.
Digital versus paper retention
Digital records are the practical choice for long retention, provided the format remains readable. Documents should be stored in a format that does not depend on the contractor’s software, and data files should be exported in open formats alongside any proprietary ones.
The structure matters as much as the format. A directory organised by asset, with subdirectories for the stages of commissioning, is usable ten years later; one organised by project meeting date is not.
Paper copies still have a place for the documents that will be consulted in the field, such as the as-built diagrams and the settings lists. The two sets should be consistent, and where a document is revised, the revision should be reflected in both.
What is usually missing and why it matters
The commonly missing items are the ones produced informally during the work: the configuration files, the raw data, the deviation records and the witnessing records. Each was available at the time and each was not captured.
The consequence appears at the first diagnostic comparison. A frequency response trace with no recorded lead arrangement cannot be compared with a later trace. A protection setting with no as-installed record cannot be verified. A test result with no instrument identification cannot be supported if it is questioned.
The second consequence appears in the defect liability period, when the owner and the contractor disagree about the state the equipment was in. The handover package is the evidence, and a package that records results without conditions supports neither party clearly.
Where the handover meets the maintenance programme
The handover package is the input to the maintenance programme, and the two should be designed together. The maintenance intervals, the instruments and the measurements each interval requires are all decided in the first years of operation, and they are far easier to decide from a complete commissioning record than from a drawing set and a memory of what was tested.
Where the handover identifies the measurements that will be repeated, it also identifies the conditions that have to be reproduced for the comparison to work. The lead arrangement for a frequency response sweep, the reference temperature for a resistance measurement and the sampling point for an oil sample are all commissioning decisions that become maintenance requirements.
Where that link is missing, the maintenance programme is assembled separately, and the first maintenance measurement is then compared against a commissioning value taken under conditions that are different in ways nobody recorded. The comparison looks like a change in the asset, and the investigation that follows is spent establishing that it is not.
A handover checklist
A workable checklist groups the items by purpose rather than by document type. The first group establishes what was tested: the scope, the results, the conditions and the standards applied. The second establishes the state of the equipment: the settings, the configurations and the as-built drawings.
The third group establishes the evidence: the raw data, the instrument identification and calibration status, and the deviation and witnessing records. The fourth establishes what happens next: the maintenance intervals, the instruments and methods for periodic testing, and the warranty and defect terms.
Reviewing the package against those four groups before handover identifies the gaps while they can still be filled. Once the commissioning team has demobilised, the items that are missing become permanent gaps. The framework for what the installation has to achieve is set out in IEC 61936-1 for high-voltage installations, and the transformer-specific evidence that a commissioning record normally contains is defined in IEC 60076-1. Independent acceptance practice is published by NETA, the field test framework that governs the test voltages is published as IEC 60060-3, and the traceability requirements that the instrument records have to satisfy are described in the NIST handbooks and by the accreditation bodies such as ILAC. Downloadable product documentation of the kind that accompanies a delivered equipment package is listed under product documents for download, the support arrangements are described under testing services and OEM/ODM solutions, and reference projects are listed under typical achievements.
A handover package is complete when a measurement taken ten years later can be compared against it.
Send your handover index to our engineering team and we will mark the items that are usually missing. Product documentation of the kind a package should contain is listed under product documents for download.
FAQ
What is the difference between test results and test evidence?
A result is a value with a verdict; evidence is everything needed to reproduce that value. Evidence includes the conditions, the instruments and their calibration status, the connection arrangement, the raw data and the standard applied. A file of results can be reviewed and accepted; a file of evidence can be audited, re-analysed and used as a reference for future measurements.
Why are as-built settings more important than the test results?
Because the settings define the state the equipment is in for the rest of its life, while the test results describe one moment. A relay setting group, a charger float voltage or a protection threshold that is not recorded as installed cannot be verified later, and a maintenance team testing against the design value will be testing something other than the equipment’s actual configuration.
What is usually missing from a handover package?
The items that were produced informally: the deviations accepted during construction, the configuration files as installed, the raw data behind derived results, and the record of which tests were witnessed and by whom. Each of them was available at the time and was not captured, and each of them is difficult or impossible to reconstruct afterwards.
How should digital records be handed over?
In formats the owner can open without the contractor’s software, organised so they can be found by asset rather than by project folder, and with enough metadata to identify what each file contains. A folder of files named by date is technically a handover and practically unusable.
How long should commissioning records be retained?
For the life of the asset, because the commissioning record is the baseline against which every subsequent measurement is compared. Retention through the defect liability period alone is not enough; the first diagnostic comparison years later depends on the commissioning values being available.
