Solar Detailed Engineering Design: How to Coordinate PVsyst, Layout, Electrical and Civil Design

Solar detailed engineering design works when every discipline uses the same frozen inputs and every change is traced to the documents it affects. The yield model, layout, electrical design, structural design, civil design, SLD and BOQ are one system. A change in one place, such as a different inverter or a new row pitch, ripples through the others. The practical answer is a design-freeze workflow, clear responsibilities and routine reconciliation.

How the disciplines depend on each other

PVsyst and the layout. The yield model must use the geometry and equipment that will be built: tilt or tracker settings, row pitch, shading scene, module count, string configuration and inverter loading. If the layout changes after the model is run, losses change, and the energy estimate no longer describes the plant.

Module and inverter selection and the electrical design. Module voltage, current and temperature coefficients decide string length. Inverter MPPT range and input limits decide how many strings connect and how they are grouped. Changing either product after stringing is done means redoing stringing, cable sizing and the SLD.

Inverter and transformer locations and the roads and cables. Equipment position drives DC cable length and therefore voltage drop, road alignment, trench routes and pad locations. Moving a block changes civil and electrical documents at once.

Topography and the layout, grading and drainage. Slopes limit row spacing, structure geometry and tracker feasibility. Cut and fill, drainage paths and flood levels determine where rows and equipment can sit. A layout fixed before the drainage design often needs rework.

Mounting structure geometry and foundations. Table dimensions, tilt, ground clearance and wind exposure determine member forces and pile reactions. Pile type and embedment depend on those reactions and on the geotechnical data, which in turn affect construction method and sequence.

Everything and the SLD and BOQ. The SLD must reflect the equipment and cable schedule. The BOQ must reflect the released drawings, not the feasibility estimate.

A design-freeze workflow

Use staged freezes so later work builds on stable inputs.

1.          Freeze the design basis. Capacity basis, codes, climate data, grid requirements, module and inverter shortlist, mounting concept and responsibilities.

2.          Freeze the equipment. Module, inverter and transformer models confirmed, with datasheets on file.

3.          Freeze the layout. Boundary, exclusions, row geometry, block positions, roads and drainage concept agreed, and the PVsyst model updated to match.

4.          Freeze the electrical design. Stringing, cable sizes, SLD, protection philosophy and grid connection design agreed.

5.          Freeze the structural and foundation design. Structural report issued, reactions agreed and pile design confirmed against geotechnical data.

6.          Freeze civil design. Grading, drainage, roads and equipment foundations tied to final equipment dimensions.

7.          Release IFC and BOQ. All documents reconciled, reviewed, numbered and issued together or in agreed packages.

After each freeze, changes follow a change-control process: a request, an impact assessment across disciplines, an approval and an updated set of documents.

Responsibility discussion: who does what

The table below is an example of RACI-style roles (Responsible, Accountable, Consulted, Informed) for key tasks. Adapt it to your organization and contract.

The point is not the letters but the clarity. Every artefact needs one accountable owner, and every shared interface needs a named person on each side.

Clash and reconciliation checklist

•             ☐ PVsyst module count, tilt, pitch and shading scene match the issued layout.

•             ☐ PVsyst inverter, transformer and loss assumptions match the SLD and equipment datasheets.

•             ☐ String lengths and counts per inverter agree across stringing drawings, SLD and cable schedule.

•             ☐ Cable lengths in the schedule match routed lengths on drawings.

•             ☐ Equipment dimensions on layout match vendor drawings, with clearances respected.

•             ☐ Pile locations and heights match structural drawings and PV layout coordinates.

•             ☐ Structural model loads and geometry match the module datasheet and layout.

•             ☐ Foundation reactions match the geotechnical design assumptions.

•             ☐ Finished levels, drainage and trench levels are consistent.

•             ☐ Roads reach every block and meet vehicle requirements.

•             ☐ Earthing and lightning layouts connect to structures and equipment as designed.

•             ☐ BOQ quantities derive from the current IFC revision.

•             ☐ Drawing register shows consistent revisions across disciplines.

Common coordination failures (generic examples)

These are typical patterns, not reports of specific projects.

•             Model and layout drift. The layout is tightened after the yield run, and the loss estimate no longer reflects the plant.

•             Late equipment change. An inverter substitution changes MPPT limits, forcing a stringing revision after cable orders.

•             Pad size mismatch. A transformer is delivered with different dimensions to those on the foundation drawing.

•             Drainage conflict. A trench or pile line crosses a drainage path that was added later.

•             Reaction mismatch. A foundation is designed for loads from an earlier structural revision.

•             Schedule drift. The cable schedule is updated, but the SLD or routing drawing is not.

•             BOQ from the wrong stage. Quantities are taken from the feasibility layout and do not match IFC.

Routines that keep coordination working

•             A weekly cross-discipline review with overlays in a shared coordinate system.

•             A single master register of documents with revision and status.

•             An interface register listing each cross-discipline dependency, owner and due date.

•             Clear rules for who can change a frozen input and how the change is communicated.

•             A final reconciliation review before IFC release, ideally by someone who did not produce the drawings.

When to involve a specialist

Bring in an independent specialist when the project is large, the schedule is tight or multiple contractors share design responsibility. Solyug Energy supports EPCs and developers with solar design consultancy and MW-scale project management consultancy, and shares further guides in the resource center.

Standards and references

•             IEC 62548: PV array design requirements.

•             IEC 62446-1: documentation and commissioning of grid-connected PV systems.

•             IEC 61724 series: performance monitoring, relevant to comparing modelled and measured performance.

•             PVsyst documentation for model inputs and loss assumptions.

•             Project execution plan and change-control procedure.

Frequently Asked Questions

Why does PVsyst need to match the layout?

Because shading, geometry and equipment loading determine losses. A model based on an earlier layout may overstate or understate energy.

When should a solar design be frozen?

In stages, with the design basis and equipment frozen first, then layout, electrical, structural and civil, before IFC release.

Who is responsible for design coordination?

Usually, the design manager or lead engineer, with discipline leads accountable for their own interfaces. Define this in the execution plan.

What is the most common coordination failure?

A change in one discipline that is not carried through to the others, such as an equipment change that does not update stringing, cable schedules or foundations.

How do you manage design changes after IFC?

Through change control with cross-discipline impact assessment, approval, and updated drawings, schedules and BOQ.

Do small projects need the same process?

The steps can be lighter, but the principle holds: one frozen set of inputs and a final reconciliation check.