How to Review DC, PCS and MV Interfaces in a BESS Booster Layout

A BESS booster substation layout review is most useful when it starts as a document-and-responsibility exercise. Before anyone treats a drawing as final, the battery-system team, PCS supplier, transformer or prefabricated-substation supplier, EPC, and owner should identify their electrical boundaries and the information each party must issue.

This guide helps a project team organize that review. It does not create a site arrangement, safety separation, fire strategy, cable route, protection setting, equipment rating, or approval decision. Those decisions require the approved project design, applicable requirements, and responsible engineers.

Part 1. Start with an interface review, not a layout promise

The word “layout” can conceal several different jobs: an electrical one-line, a civil drawing, an equipment-scope list, an operations plan, or a safety review. Do not merge them into one unchecked supplier assumption. First identify the exact drawing under review, its revision, and what the project wants the review to decide.

For a BESS block, a useful initial boundary is the DC side from the battery-system scope, the PCS AC interface, the transformer or integrated-station scope, and the MV collection interface. IEC 62271-202 is relevant as scope context for AC prefabricated substations; it does not supply a BESS arrangement or a project approval.

Important: A concept drawing is not an approved BESS layout. Record the drawing revision, the decision owner, and the unresolved assumptions before using it as an RFQ basis. (IEC 62271-202)

Part 2. Define the DC boundary and its document owner

The DC boundary should state where the battery-system supplier’s responsibility ends and where the PCS or EPC responsibility begins. The review should ask for the approved electrical interface documents, not assume cable routes, isolation arrangements, protection behavior, or operating limits from a generic battery-container description.

This table does not prescribe how equipment must be separated or connected. It keeps each party from silently adopting an assumption that another party owns.

Part 3. Reconcile PCS, transformer and MV information

The PCS, transformer, and MV collection interfaces are one review path, even where several suppliers contribute documents. Match the named equipment scope, connection point, document revision, operating basis, and design authority across the package. A transformer standards-family reference such as IEC 60076-1 is useful context for transformer documentation, but it cannot determine a BESS transformer duty or configuration from a layout sketch.

For related protection responsibility questions, see JUBANG’s BESS booster substation protection interfaces. That article does not replace this controlled drawing and scope review.

Part 4. Control the one-line diagram and drawing set

Issue one controlled set instead of collecting screenshots or supplier extracts in parallel. The register should identify the current one-line diagram, equipment schedule, civil drawing, interface documents, and the document that governs each item when records differ.

Use a short review meeting to make the handoff explicit:

1. confirm the drawing and document revisions in use;
2. identify every boundary that has an owner and every boundary that does not;
3. list missing supplier inputs without inventing them;
4. assign the party who will issue or accept each clarification; and
5. record whether a change needs owner, EPC, utility, or design-authority approval.

This process supports traceability. It is not a substitute for civil coordination, site safety review, electrical protection design, or construction approval.

Part 5. Maintain an interface register for open assumptions

An interface register makes uncertainty visible before it becomes a quotation exclusion or late change. Give every entry an evidence source, revision, owner, status, and acceptance path. Keep commercial scope questions separate from technical approval questions so neither is mistaken for the other.

The register can cover DC, PCS, transformer, MV, civil, controls, and documentation interfaces without claiming that any particular arrangement is suitable.

Part 6. Put the right evidence into the RFQ

Issue the RFQ with a responsibility matrix rather than an instruction to reproduce a prior project. Ask bidders to list missing inputs, exceptions, and documents that require the project design authority’s confirmation.

Do not use this table to request an unverified safety arrangement, HVAC result, performance commitment, or compliance statement. The approved design team must define those requirements.

Part 7. Move from a review package to a product enquiry

Once the project has controlled its interfaces, the team can review the JUBANG prefabricated substation range as a product-family starting point. Provide the one-line diagram, scope matrix, project documents, and unresolved-action register so the enquiry can be discussed against an actual project basis.

The page introduces a product family only. It does not establish a BESS layout, engineering fit, safety outcome, rating, local compliance, or project acceptance. Send the controlled package through JUBANG Contact Us for a project-specific discussion.

FAQs

Is this a BESS layout design?

No. It is a checklist for controlling interface ownership and project documents before a responsible engineer reviews the actual layout.

Who owns the DC, PCS and MV interfaces?

Ownership must be assigned in the project scope matrix. Battery, PCS, equipment, EPC, owner, and utility responsibilities can differ by contract and approved one-line diagram.

Which drawing should start the review?

Start with the current controlled one-line diagram, then link it to the scope matrix and the relevant supplier interface documents.

Can a product page determine the transformer configuration?

No. Product information can introduce a range, while project duty, studies, interfaces, and approval requirements determine the selected configuration.

How should open assumptions be controlled?

Record each assumption in an interface register with its evidence source, owner, status, and approval route.

What belongs in a BESS booster substation RFQ?

Include the controlled project basis, DC and PCS interface documents, transformer and MV evidence, civil coordination inputs, required documents, and a deviation register.

References

• IEC 62271-202: Prefabricated substations
• IEC 60076-1: Power transformers
• CIGRE