{"id":4129,"date":"2026-10-09T07:00:00","date_gmt":"2026-10-09T07:00:00","guid":{"rendered":"https:\/\/lbajiele.com\/?p=4129"},"modified":"2026-10-09T12:36:17","modified_gmt":"2026-10-09T12:36:17","slug":"electrical-distribution-construction-package-guide","status":"publish","type":"post","link":"https:\/\/lbajiele.com\/fr\/blog\/electrical-distribution-construction-package-guide\/","title":{"rendered":"Electrical Distribution Construction Package: Document Checklist"},"content":{"rendered":"

An electrical distribution construction package is the controlled set of drawings, specifications, schedules and approved supplier information used to install and verify a distribution system. It should connect the design intent to the actual equipment, cables, controls and acceptance process. A single-line diagram is an important part, but it is not the whole package. This guide explains what buyers and project teams should request, how to check consistency and how to manage the transition from issued-for-construction documents to as-built records. It is a document coordination guide, not permission to install, test or energize electrical equipment.<\/p>\n

Define the package boundary and document status<\/h2>\n

State which system and contract the package covers. A distribution room package might include incoming equipment, transformers, a main lineup and outgoing feeder interfaces, while downstream branch circuits are covered elsewhere. List those boundaries and responsible parties. Without them, two contractors may each assume the other supplies a cable, relay interface or termination detail.<\/p>\n

Assign a drawing and document register with identifiers, revision numbers, issue purpose and approval status. Tender, review and construction documents should be distinguishable. The latest date does not necessarily mean the document is approved for installation. A controlled register allows the site team to locate the correct version and identify superseded information. Define who can issue revisions and how affected users receive them.<\/p>\n

\"GGD
Product-based illustration of GGD Low-Voltage Switchgear. Exterior appearance does not establish project ratings, internal configuration or certification.<\/figcaption><\/figure>

Use the single-line as the system map<\/h2>\n

The single-line should identify sources, major equipment, bus sections, protective devices and load destinations within the package boundary. Match its equipment and feeder identifiers with schedules and supplier drawings. Show the intended normal source arrangement and refer to the operating narrative for alternate states. Where information is incomplete, record the outstanding design input rather than presenting an assumption as a final requirement.<\/p>\n

The one-line supports system understanding, but it generally does not provide every terminal or physical cable route. Keep detailed construction information in the appropriate drawings and schedules. If the supplier changes a bay arrangement or device identifier, reconcile the system map and affected documents. A one-line that no longer matches the ordered equipment can confuse both commissioning and later operations.<\/p>\n

Include the equipment schedule and technical specification<\/h2>\n

The equipment schedule should identify each assembly, location, function and relevant design requirements. Link it to the technical specification and approved data. Separate system nominal values from complete equipment ratings and verification evidence. Continuous current, insulation requirements, interrupting duty and assembly withstand are distinct questions; a short label on a drawing cannot establish all of them.<\/p>\n

For an LBAJI GGD-based procurement discussion, request the exact proposed lineup, component configuration and documentation. The product illustration establishes a category reference, not compliance with an unidentified construction specification. The package should also define what is included in the supplier\u2019s scope, including auxiliary devices, accessories, labels, shipping sections and manuals. Keep accepted deviations together with the final approved proposal.<\/p>\n

Coordinate general arrangements and access<\/h2>\n

Layout drawings should show equipment positions, orientation, installation interfaces and required access. Review them with the approved supplier general arrangement, not a generic catalogue outline. Include relevant shipping-section dimensions, handling provisions, mounting details and connection locations. A cabinet that fits the final floor space may still be impossible to move through the building access route.<\/p>\n

Coordinate cable entry, maintenance access and future replacement needs before construction. Confirm that ducts, pipes or architectural features do not conflict with the approved equipment arrangement. The applicable clearances and safety provisions require competent project review; do not invent a universal spacing from an internet diagram. Record layout decisions and update drawings when an approved equipment change affects the room.<\/p>\n

\"GGD
Product-based illustration of GGD Low-Voltage Switchgear. Exterior appearance does not establish project ratings, internal configuration or certification.<\/figcaption><\/figure>

Build a complete cable and termination schedule<\/h2>\n

A cable schedule links each circuit to its source, destination and approved cable specification. It should use identifiers that agree with the one-line and equipment labels. Include the information needed by the project, such as route reference, conductor arrangement and termination responsibility. Avoid treating a simple feeder current label as a complete cable design.<\/p>\n

Termination drawings should identify the actual interface at each end, including control terminals where applicable. Define who supplies connectors, glands, supporting hardware and any interconnection between shipping sections. If a supplier uses a different terminal convention, reconcile it before installation. The installer should not need to infer a critical connection from similar-looking equipment or an informal message sent after the drawings were approved.<\/p>\n

Add control schematics and operating narratives<\/h2>\n

Control documentation explains trip and close circuits, interlocks, auxiliary supplies, indications and external contacts. Match device and terminal identifiers across all sheets. Define the auxiliary supply requirements and how equipment behaves if that supply is unavailable. A note saying \u201cautomatic transfer\u201d is insufficient without an approved sequence and interface definition.<\/p>\n

Use an operating narrative for multi-source and transfer functions. Describe normal states, failure detection, permitted switching combinations and restoration. Distinguish the design narrative from an authorized site switching procedure. Where several suppliers share a function, identify each interface owner and test responsibility. This makes it possible to verify the whole sequence instead of receiving separate cabinet tests that leave the connections between them unexamined.<\/p>\n

Keep studies and protection settings connected<\/h2>\n

The package should identify the system studies required by the project and the owner of each deliverable. Fault-duty assessment, coordination and other analyses support equipment and protection decisions. The construction team needs to know which assumptions are final and which must be confirmed before commissioning. A report created before a source or breaker change may need review even if its filename has not changed.<\/p>\n

Record relay and device settings through the approved process. Identify whether settings are supplied by the manufacturer, consultant or owner, and who authorizes their use. Retain final configuration files with appropriate version control. A relay model on the bill of materials does not establish accepted settings. Site tests should connect the installed configuration to the approved study and report any differences before energization approval.<\/p>\n

\"GGD
Product-based illustration of GGD Low-Voltage Switchgear. Exterior appearance does not establish project ratings, internal configuration or certification.<\/figcaption><\/figure>

Reconcile approved supplier submittals<\/h2>\n

Supplier drawings, data and test procedures become part of the construction information only through the agreed review process. Track comments and their closure. If the supplier proposes a substitute component or arrangement, require a change record that identifies effects on ratings, controls, dimensions and acceptance evidence. A new parts list should not silently override the contract requirement.<\/p>\n

Review the final documents as a set. Check that the approved arrangement, one-line, schematics, terminal drawings and equipment schedule describe the same configuration. Identify hold points for unresolved interfaces. UL\u2019s information on customized equipment and field evaluation is useful when a project needs that acceptance route; it does not make every modification automatically acceptable. Keep the responsible engineering and jurisdictional decisions documented.<\/p>\n

Define inspection, testing and energization records<\/h2>\n

Specify the factory and site acceptance scopes, witness requirements and closure process for findings. Test records should identify equipment, drawings, configuration and conditions. Separate design verification evidence from production checks and installed-system testing. A general certificate should not replace the particular evidence required by the construction specification.<\/p>\n

Before energization, assemble the approved records and outstanding-item list through the site\u2019s authorization process. Safety procedures and qualified work practices remain separate controlled requirements. OSHA provides relevant U.S. electrical work-practice guidance, but document completeness alone does not establish that physical equipment is safe to energize. The responsible team must verify installation, testing and operating readiness using the applicable project requirements.<\/p>\n

Produce a usable as-built and operations handover<\/h2>\n

The as-built package should reflect accepted changes and the actual installed configuration. Collect redlines through a controlled process and verify them against final equipment identities and interfaces. Remove obsolete alternatives from the operating set while retaining the revision history. A marked-up construction drawing is useful evidence, but it should not be confused with a formally accepted final record.<\/p>\n

Include operation and maintenance manuals, approved settings, test reports, spare-parts information and interface ownership. Make the register searchable by equipment and feeder identifiers. The operations team should be able to find the correct drawing without interpreting the construction contractor\u2019s folder structure. Establish how future alterations update the records. A handover package stays valuable when it follows the system throughout its service life.<\/p>\n

Construction package completeness table<\/h2>\n
\n
Document<\/th>Main question it answers<\/th>Cross-check<\/th><\/tr><\/thead>
Single-line<\/td>How does power flow between sources and loads?<\/td>Equipment identifiers and feeder destinations<\/td><\/tr>\n
Layout and arrangement<\/td>Where and how is equipment installed?<\/td>Cable entry, access and supplier dimensions<\/td><\/tr>\n
Cable schedule<\/td>What connects each interface?<\/td>Circuit tags and termination responsibility<\/td><\/tr>\n
Control drawings<\/td>How do commands, protection and interlocks operate?<\/td>Logic narrative and external interfaces<\/td><\/tr>\n
Studies and settings<\/td>What supports ratings and protection decisions?<\/td>Final sources, devices and configurations<\/td><\/tr>\n
Test and as-built records<\/td>What was supplied, installed and accepted?<\/td>Equipment identity, revisions and closure evidence<\/td><\/tr>\n<\/tbody><\/table><\/div>\n

Foire aux questions<\/h2>\n
\n
\n
\n

Is a single-line diagram a complete construction package?<\/h3>\n
\n\n

No. It maps the system, but construction normally needs layouts, cable schedules, terminal details, control drawings, specifications and approved equipment data. The exact scope depends on the project. Use a document register to identify required records and owners. Avoid letting an attractive one-page diagram conceal missing information at installation interfaces.<\/p>\n\n<\/div>\n<\/div>\n

\n

Does the newest drawing always replace the older one?<\/h3>\n
\n\n

Not automatically. Check its revision, issue purpose and approval status. A newer review draft may not be authorized for construction. The document controller should identify the current approved version and distribute revisions through the agreed process. Keep superseded records in the history while preventing accidental use at the site.<\/p>\n\n<\/div>\n<\/div>\n

\n

Who owns the final as-built package?<\/h3>\n
\n\n

The contract should define preparation, verification, approval and delivery responsibilities. Installers and suppliers may contribute different records, while the owner receives the accepted operating set. Name a coordinator who reconciles them. A complete handover requires more than collecting files; identifiers, revisions and installed configuration must agree across the package.<\/p>\n\n<\/div>\n<\/div>\n

\n

Can supplier drawings replace the consultant\u2019s design without review?<\/h3>\n
\n\n

No. Submittals should pass through the agreed approval and change-control process. A proposed arrangement may affect system interfaces, protection or installation. Record accepted deviations and update related documents. The construction package should show one coherent approved configuration rather than rely on conflicting supplier and designer drawings.<\/p>\n\n<\/div>\n<\/div>\n

\n

What makes a handover package useful after construction?<\/h3>\n
\n\n

It should be organized by equipment and circuit identifiers, contain accepted as-built information and connect drawings with tests, settings and manuals. Include responsibility for future updates. Operations staff need to find the correct records quickly and understand their status. A large folder of unreviewed files is less useful than a controlled, consistent set.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>

Related LBAJI resources<\/h2>

LBAJI GGD Low-Voltage Switchgear<\/a>. switchgear fundamentals<\/a>. Guide de test des \u00e9quipements de commande<\/a>. switchgear maintenance checklist<\/a>.<\/p>

Technical sources<\/h2>

Use these references for the relevant equipment and work-practice scope. Confirm the edition and project requirements with the responsible engineer.<\/p>