System design input
Begin with array purpose, nominal power, DC configuration, location, and the boundary between module selection and the broader system design. These inputs help prevent an incomplete comparison from becoming a specification.
Project lifecycle support
Use the same project brief from first selection through documentation review, installation preparation, and the questions that appear after commissioning.
Begin with array purpose, nominal power, DC configuration, location, and the boundary between module selection and the broader system design. These inputs help prevent an incomplete comparison from becoming a specification.
Before installation, align module handling, mounting interface, cable routing, and the inspection records expected by the project owner. Site conditions can change the practical sequence even where a drawing is unchanged.
Maintain a route for cleaning access, visual inspection, monitoring alerts, and escalation contacts. A module warranty conversation is more useful when retained records and site responsibilities are identified.
Describe the use case and energy objective.
List electrical and mounting dependencies.
Specify the standards and files being requested.
Name the review and handover contacts.
A useful handover record separates verified information from open questions. It records the product family under discussion, the declared electrical limits, the installation guidance used, and the local party responsible for final design approval. This approach also makes later troubleshooting more reproducible: a reviewer can see which site conditions, test references, and maintenance assumptions were known at the time.
IEC 61215 and IEC 61730 can be part of a compliance discussion, but applicability is confirmed against the actual product, market, contract, and document issue.
Compare declared nominal power and module efficiency with the stated test conditions. Do not use a single nameplate value as a forecast of field yield.
Log installation guidance, inspection actions, and project contacts so an issue can be investigated with context rather than recollection.
Send a concise brief with location, array type, target power range, delivery timing, and the technical documents your stakeholders need. The conversation can then focus on an appropriate decision path instead of generic claims.