Booster Substation Equipment Tag Register: What to Align Before Handover

Before handover, an EPC should align every booster-substation equipment tag with its description, scope boundary, physical-label reference, controlled drawings, document-index revision, discrepancy action, and responsible owner. The register supports a traceable handoff; it does not certify as-built status or configure any data system.

Part 1. Define the tag-register boundary

An equipment tag can refer to a transformer, switchgear panel, relay, breaker, enclosure item, or package interface. Start by recording which equipment packages the register covers and which document controls the boundary. A label seen in a photograph is not evidence that a tag register is complete.

Important: Treat the tag register as a controlled alignment record. The project authority must decide whether any issue becomes an as-built record or acceptance evidence. (IEC 62271-202)

Part 2. Record core identity fields

Every row should provide enough evidence to connect a tag to the named equipment and current document set. Keep the identity fields factual and point back to controlled project records.

Part 3. Align labels and controlled documents

Compare the physical-label record, drawing references, and document index against the current scope matrix. Where a record differs, log the discrepancy; do not overwrite one source with another without controlled project approval.

For related handover context, see JUBANG’s PV booster station site record handover article. It does not validate a tag or certify an as-built record.

Part 4. Assign scope and approval owners

Name who prepares the register, who controls drawings, who supplies label evidence, who reviews discrepancies, and who approves a controlled update. This prevents a supplier comment, an EPC note, or an operations request from silently changing the register.

The responsibility list should identify:

1. the tag-register owner and current revision;
2. the design authority for drawings and schematics;
3. the package owner for equipment identity evidence;
4. the EPC or owner reviewer for scope questions; and
5. the authority for controlled closure of a discrepancy.

Part 5. Log discrepancies and revisions

Give each mismatch a unique reference and state the tag, document, factual difference, owner, required evidence, and closure route. Keep an open action distinct from a corrected revision. A revised register does not by itself establish physical verification or acceptance.

For revision-control context, see JUBANG’s prefabricated substation drawing revision control article. It does not replace the project register.

Part 6. Build the tag-register handover pack

Issue the register with one controlled revision index and ask recipients to identify missing evidence and discrepancies explicitly.

Part 7. Use the controlled record for a product enquiry

After the tag register, scope matrix, and action log are controlled, the EPC can discuss the equipment scope with the JUBANG prefabricated substation range.

The product-family page does not validate labels, tags, as-built status, integrations, or project acceptance. For an equipment-specific discussion, provide the controlled tag package using JUBANG Contact Us.

FAQs

What is included in an equipment tag register?

Include the equipment tag, description, scope boundary, label reference, controlled document reference, revision, discrepancy action, and owner.

Who owns an equipment tag register?

The project document-control plan should name the register owner, the reviewers, and the approval route for controlled revisions.

Should a tag register match drawings?

Yes. Compare it with the current controlled drawings and log any mismatch as an assigned project action.

Is an equipment tag register an as-built record?

Not automatically. It is an alignment record unless the responsible project authority formally designates and approves it as an as-built record.

How should a tag discrepancy be recorded?

Use a unique action reference with the affected tag, factual evidence, responsible owner, required record, and controlled closure route.

What should an EPC send with a tag-register handover request?

Send the scope matrix, equipment list, controlled drawings, document index, label evidence references, action log, and revision register.

References

• Industry record-management context: CIGRE technical knowledge community
• Prefabricated-substation scope context: IEC 62271-202 source page