Search productSearch post

News Center

Substation Temporary Modification Register: Test Changes, Restoration and Release Evidence

A substation temporary modification register connects approved test changes to their restoration evidence. During commissioning, several teams may work on protection, control, communications and equipment interfaces. A change that was valid for one test can become an unresolved release issue when the team moves to another bay or hands the work to the next shift.

The register should show what changed, why it was approved, who owns it and how the intended final configuration was verified. It is a project control record, not permission to bypass protection or alter a live circuit. Any modification and restoration must follow the authorized procedure, equipment instructions and site safety rules.

Substation temporary modification register supporting an authorized test review
Illustrative commissioning review: identify each authorized test change before work begins.

Define the scope of the substation temporary modification register

Agree the register boundary before testing starts. It may include approved temporary software configurations, test-specific signal substitutions and documented physical changes within an authorized work package. The precise scope depends on the station and its procedures. Do not use one vague entry such as “panel under test” to cover multiple changes with different restoration requirements.

Operational temporary earths, isolation points and locks belong to the applicable switching, permit and isolation control systems. Cross-reference those records where needed, but do not remove an earth or release an isolation because a spreadsheet row is marked closed. The responsible operating authority controls those actions through the appropriate procedure.

Similarly, a permanent design change is not a temporary change with a distant due date. Move it through formal engineering change control, revise the affected documents and obtain the required approval. Keep the link to the original temporary entry so the history remains traceable.

Minimum fields for a useful register

Field groupInformation to captureWhy it matters
IdentityUnique entry number, station, bay, panel and asset referencePrevents confusion between similar equipment
AuthorityApproved test procedure, permit interface and approving personConnects the change to authorized work
BaselineApproved drawing or configuration revision and original stateDefines the restoration target
Change descriptionSpecific affected function and scope, recorded by competent personnelAvoids broad or ambiguous entries
OwnershipImplementer, responsible owner and shift handover contactKeeps responsibility visible
Time and boundaryImplementation date, applicable test phase and planned restoration gatePrevents a test condition from drifting into operation
Restoration evidenceWork record, final revision, verification method and evidence referenceSupports an auditable closure decision
ReleaseReviewer, date, restrictions and system turnover referenceConnects closure to the release package

Use a controlled vocabulary for status. For example: proposed, approved, implemented, restoration pending, verification pending and closed. These are suggested project labels, not a universal standard. Define who may move an entry between states and retain the change history. A closed row should remain visible in the archive.

Record the baseline before the change

Restoration is difficult to prove if the original state was never identified. Reference the approved drawing, configuration file or relevant equipment record before implementation. Record the version and approval status, not simply the filename. A file called “final” may still be a working copy.

For configuration-related work, the responsible specialist should identify the approved baseline and the appropriate comparison evidence. A screenshot can show a displayed value, but it may not capture the full configuration or establish which file was loaded. Keep the supporting export and approval reference where the procedure requires them.

Coordinate the register with relay settings handover. The temporary-change record explains the test deviation; the settings package establishes the approved operating configuration. Neither record should silently overwrite the other.

Control implementation and shift handover

Before an authorized change is implemented, the owner should confirm that the entry describes the correct asset and work boundary. Record implementation separately from approval. An approved proposal may never have been applied, while a completed test may leave restoration work outstanding.

At shift handover, review open entries by bay and system. Identify which changes remain active, which have been restored but await verification, and which require an engineering decision. The incoming team needs access to the actual evidence and approved procedure, not only a verbal assurance that “everything is back to normal.”

Where several contractors work in the same panel or system, nominate one register custodian and retain individual technical ownership. The custodian manages completeness and status; the responsible specialists confirm the technical facts. Do not let a document-control signature stand in for an engineering verification.

Protection test review linked to temporary modification restoration evidence
Illustrative technical review: restoration and verification are separate recorded steps.

Restoration needs evidence, not a tick alone

The substation temporary modification register should identify the intended final state and the evidence used to confirm it. The approved procedure determines whether inspection, configuration comparison, functional verification or other checks are required. This article does not prescribe a test method or authorize changes to protection and control circuits.

Record who performed the restoration, when it occurred and which entry or work record it closes. Then record the required verification and reviewer. If the final state differs from the original baseline because an approved permanent change was introduced, reference that approval and its revised documents explicitly.

Situation at reviewEvidence neededRegister treatment
Change proposed but never implementedResponsible person’s confirmation and cancellation recordClose as not implemented, retaining history
Restored, verification incompleteRestoration record and outstanding verification scopeKeep verification pending
Final configuration differs from baselineApproved engineering change and revised referencesReconcile before closure
Unidentified change found during walkdownControlled discrepancy record and technical assessmentHold the affected release decision
Restoration and required checks acceptedLinked results, reviewer and applicable release referenceClose with an auditable record

Reconcile the register before system release

Do not rely solely on a filter showing zero open rows. Review the register against the work packages, outstanding test sheets, discrepancy lists and relevant configuration records. A missing entry will not appear in the open-item count. The release team should resolve mismatches between the records and the actual equipment state through the authorized process.

Use the project asset hierarchy to check coverage. An entry recorded against a panel may affect a wider protection or control function. The responsible engineers should identify the applicable system boundary and any dependent tests. Coordinate references with the substation asset register so that similar panel names do not conceal a mismatch.

Reconcile final changes with the as-built drawing package. A closed temporary entry cannot compensate for an unexplained difference between the field condition and the controlled drawings. Record the final document revision in the turnover index.

Where a change remains unresolved, the responsible authority must decide its effect on the release boundary under the project procedure. Do not treat a management comment or a future target date as technical clearance. Any approved restriction must be explicit, owned and visible to the operating team.

Prepare a handover package the operator can use

Deliver a controlled register export, linked restoration and verification records, the final configuration references and the approval trail. Make file paths usable outside the contractor’s personal drive. Include an index that maps each entry to its evidence and identifies any formally transferred outstanding work.

Keep the editable working register under controlled access and retain a dated handover snapshot. The snapshot shows the status accepted at turnover; later maintenance changes should follow the owner’s process. A subsequent update should not erase the historical release position.

Handover review of the substation temporary modification register and closure files
Illustrative handover: the operator needs the closure evidence as well as the register.

Frequently asked questions

Is a temporary modification register a work permit?

No. It records and tracks approved changes. Work authorization, isolation and safe execution remain within the applicable site procedures.

Can one entry cover a complete panel test?

Only if the agreed procedure and entry structure make every affected change and restoration requirement unambiguous. Separate entries are preferable when ownership, boundaries or closure evidence differ.

Is a photograph enough to close an entry?

Only if it forms part of the evidence accepted by the approved verification method. A photograph alone may not establish configuration, functionality or restoration completeness.

What if a change becomes permanent?

Use formal engineering change control and update the approved baseline and drawings. Retain the link to the temporary record and its disposition.

Should temporary earths be removed when the register is closed?

No. Their installation and removal remain controlled by the relevant switching and safety procedures. Register closure is not an instruction to remove safety measures.

Reference and project review

HSE’s working with electrical equipment guidance explains general principles of planning and safe electrical work. The register fields and workflow in this article are a proposed project-management structure, not a form mandated by that guidance.

Preparing a substation turnover package? Contact Zisheng with the equipment scope, document index and commissioning interfaces to discuss the records needed for a coordinated handover review.

The prev: The next:

Related recommendations

Expand more!