Quick answer
Comparison of alternative solar configurations using declared shared assumptions, changed parameters, metric boundaries and customer priorities; rankings support decisions but do not establish technical approval.
Answer: Design variant comparison evaluates alternative solar configurations against a defined baseline and the customer’s priorities. Variants may change equipment, layout, storage or financing, but results are comparable only when shared site, weather, loss and financial assumptions are controlled. Record every change, metric boundary and revision. A ranking can support a decision; it does not make subjective priorities objective or establish technical approval, savings or sales conversion.
Four useful comparison categories
Equipment variants explore exact module and inverter combinations. Layout variants compare roof areas, orientations or arrangements. Financial variants compare payment or ownership structures for a defined system. Storage variants consider the additional functions, costs and dispatch constraints of a battery.
Change one parameter category when the question is what caused a difference. Multiple changes can be appropriate for complete packages, but then describe the package trade-off rather than attributing the result to one component. More battery energy does not automatically establish whole-home or off-grid capability.
PVsyst’s current variants-management documentation describes copying and managing calculation variants. Its system-definitions guidance explains that variants contain system definitions and parameters. These are documented vendor examples, not proof of cloning or comparison capabilities in every product.
Keep the shared assumptions visible
| Comparison record | What to retain |
|---|---|
| Identity | Base design, variant ID, revision, creator and date |
| Shared inputs | Site model, weather, time boundaries, load, tariff and declared losses |
| Changes | Exact equipment, quantities, orientation, storage or financing changes |
| Results | DC/AC capacity, annual energy boundary, included cost and financial measure |
| Constraints | Geometry, compatibility, reserve, export and customer requirements |
| Decision | Trade-offs, uncertainty, reviewer and selected revision |
Check inherited inputs after copying. If a geometry or orientation change affects shading or electrical behavior, update the relevant model rather than keeping an old result because the design was cloned. Link the selected scenario to its design review record.
Equipment capacity is not an energy forecast
Using the original illustrative quantities, 19 modules rated 400 W sum to 7.60 kW DC; 18 modules rated 430 W sum to 7.74 kW DC. The difference is 0.14 kW DC, or 1.84% of the first capacity, rounded. This does not establish annual generation or the effect of module technology.
If module dimensions differ, the same panel arrangement may not fit. Exact inverter ratings, string constraints, temperatures and losses also need checking. Performance simulation should use consistent inputs while reflecting the actual configuration changes. Do not insert invented production, tax credits or lifetime savings into a comparison table.
Weighted scoring is a declared preference model
Normalize unlike metrics before combining them. Define how higher or lower values map to scores, keep the raw results visible and agree weights with the customer. Cost and ROI can overlap, so a weighted model can unintentionally count the same financial preference twice. Aesthetics scores are judgments, not measured engineering performance.
For a hypothetical scoring exercise, use weights 0.30 production, 0.25 cost, 0.30 financial outcome and 0.15 aesthetics, summing to 1. The following normalized scores are explicitly assigned for illustration, not derived from a real site or price table.
| Variant | Production | Cost | Financial outcome | Aesthetics | Weighted score |
|---|---|---|---|---|---|
| A | 72 | 95 | 92 | 70 | 83.45 |
| B | 88 | 78 | 84 | 90 | 84.60 |
| C | 88 | 42 | 58 | 90 | 67.80 |
For A: 0.30×72 + 0.25×95 + 0.30×92 + 0.15×70 = 83.45. B ranks highest under these assigned scores and weights. Different priorities or normalization can change the ranking. Hard requirements, such as an approved equipment configuration or a budget ceiling, should be screened before a preference score; a high score cannot waive them.
Present meaningful choices
Use enough variants to answer the customer’s actual decision, without creating near-identical options. Explain what changes, what stays shared and which assumptions remain unresolved. A single suitable configuration can be enough; there is no universal number of options or verified conversion uplift from presenting three.
Show raw cost, energy and relevant uncertainties beside any ranking. Keep equipment, financing and storage value boundaries explicit in the financial model. Preserve the accepted revision and refresh affected calculations after later changes. Customer selection does not replace engineering, authority or utility acceptance.
For a software evaluation, request a demonstration with one equipment variant and one storage or payment variant. Check copied assumptions, rerun behavior, comparison outputs and revision tracking before relying on supported product functions.
Common questions
Must every proposal contain three variants?
No. Choose alternatives that answer the actual decision rather than following a fixed sales template.
Does a weighted score remove subjectivity?
No. Weights, normalization and preference judgments need to be stated and reviewed.
Can more module watts prove higher annual yield?
No. The complete equipment, layout, weather and losses determine the modeled energy result.
Does selecting a variant make it approved for installation?
No. Technical review and applicable external acceptance remain separate steps.
Related Glossary Terms
About the Contributors
CEO & Co-Founder · SurgePV
Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.
Editorial contributor · SurgePV
Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.
