Practical Manual to Read After Implementing PVSyst | 5 Improvements to Design Accuracy

After introducing PVsyst, what commonly troubles practitioners is not advancing through the interface but deciding how thoroughly input conditions need to be specified to produce results that are usable for design decisions. Simulating a photovoltaic power system combines meteorological data, azimuth, tilt, module parameters, PCS (inverter) parameters, wiring, shading, various losses, operational conditions, and other factors, all of which affect the results. Even if the calculations themselves are completed, if the basis for the inputs remains unclear, it becomes difficult to explain the outcomes when making design changes, obtaining internal approvals, explaining to the client, or revising expected generation.

This article organizes checkpoints for practitioners who search for "PVSyst manual", aimed at improving design accuracy after implementation. Rather than merely providing operating procedures, it explains a practical workflow covering pre-input document checks, handling of meteorological data, alignment of equipment conditions, review of shading and layout, loss settings, interpretation of results, and management methods that can be reused within the company.

Table of Contents

• Practical prerequisites to establish first after introducing PVSyst

• Improve design accuracy by verifying meteorological data and site conditions

• Reduce calculation discrepancies by reviewing module and PCS settings

• Align shading, azimuth, tilt, and layout conditions with on-site information

• Ensure loss settings are managed with supporting rationale and can be clearly explained

• How to interpret simulation results for use in design decisions

• Operational rules to enhance reproducibility by formalizing internal manuals

• Summary: turning PVSyst utilization into improvements for subsequent projects

Practical prerequisites to establish first after implementing PVSyst

When PVsyst is first introduced, attention tends to be drawn to how to operate the interface and the meanings of the input fields. However, what matters in practice is clearly documenting which sources were used as the basis, which conditions were entered, and at what point in time those design values applied.

In solar power system design, even when the site, capacity, and equipment configuration appear identical, annual energy production and the breakdown of losses will change if the input meteorological data, installation azimuth, tilt angle, treatment of shading, wiring losses, soiling, temperature conditions, or operational conditions differ. Therefore, PVsyst should be treated not merely as software for calculating generation but as a practical tool for organizing design conditions and compiling them into a form that can be explained to stakeholders.

After implementation, the first thing to organize is a list of input documents for each project. Gather the candidate site's location information, survey results, layout drawings, single-line wiring diagrams, equipment specifications, construction conditions, information on surrounding obstacles, assumed interconnection conditions, expected start of operation, and the purpose of the power generation assessment. If you start calculations while this is still ambiguous, you'll later need to confirm things like "which drawing was this number based on?", "has this shadow been confirmed on site?", and "is this loss rate a company standard or decided per project?". When design, review, sales proposals, and construction planning are divided among multiple people, if the origin of input values isn't preserved, it becomes difficult to trace the validity of the results.

Next, think of the project in separate stages. The required accuracy and the information available differ between initial assessment, conceptual design, detailed design, pre-construction verification, and post-completion review. In the initial assessment, certain assumptions may be made to grasp the general layout and capacity direction. By contrast, in detailed design you need to make equipment specifications, string configuration, wiring distances, shading conditions, and loss settings as close to reality as possible. Sharing results without specifying which stage of simulation they represent can cause estimates to be treated as definitive values or lead to the overlooking of conditions that require detailed study.

When creating an internal PVSyst manual, it is more practical to include not only explanations of the operation screens, but also the materials to check before inputting data, how input values are determined, how assumed values are denoted, and the verification items to review when exporting results. For example, record which meteorological data candidates were compared, which drawings the installation azimuth and tilt are based on, whether module capacity is the nominal value or the design value, how the relationship with PCS capacity was assessed, and the extent of shadowing objects that were included. Such records are also useful if the simulation needs to be re-run later.

It is also important not to treat the results of PVsyst as the definitive "correct" answer. Simulations are estimates based on the input conditions. Therefore, the reliability of the results depends on how well the input conditions are organized. Improving design accuracy does not mean merely increasing the number of detailed settings. It means choosing conditions that are close to reality, avoiding unfounded overestimation, and ensuring that stakeholders can interpret the results under the same assumptions. If this way of thinking is shared early in the implementation, the use of PVSyst is less likely to become dependent on individual users.

Improving Design Accuracy by Verifying Meteorological Data and Site Conditions

To improve design accuracy in PVsyst, the first things to review are the meteorological data and the site conditions. The annual energy yield of a photovoltaic installation is influenced by solar irradiance, temperature, wind conditions, and seasonal variations. Because irradiance in particular has a strong impact on the calculation results, you need to check which location’s meteorological data is being used, whether it closely reflects the actual conditions of the target site, and—if there are multiple candidates—what reasons dictated the selection. Immediately after implementation, users tend to use the data available in the software as-is, but in practice you should also consider the candidate site’s latitude and longitude, elevation, surrounding topography, whether it is coastal or inland, and whether it is a snow-prone area.

When handling meteorological data, first confirm the target site's location information accurately. Relying on the address alone can lead to discrepancies between the listed and actual installation locations on large sites, in mountainous areas, or on planned development sites. In addition to the site's centroid, verify the area where panels will be installed, the location of power-receiving and transformer equipment, surrounding elevation differences, and the ground level after site development. Positional differences do not always produce large impacts, but in regions prone to mountain shadows, sea breezes, snow accumulation, fog, or where surrounding terrain has an effect, understanding site conditions influences design decisions.

Next, consider the types of meteorological data and their uses separately. Data based on representative years or long-term averages are convenient for general annual power generation forecasts, but they do not necessarily match the actual performance of a specific year. Even when using data that closely approximates measured values, if the observation point is distant from the site, it may not reflect the site's actual conditions. What matters is not deciding which data is absolutely correct, but choosing data that is appropriate for the project's objectives and being able to explain the reasons.

After selecting the meteorological data, check not only solar irradiance but also the temperature conditions. Because modules are affected by temperature, in regions with high temperatures you need to consider the impact of reduced output. Conversely, in cold regions temperature conditions alone may appear advantageous, but you should also examine snow accumulation, low solar elevation, winter daylight hours, and the requirements for snow removal and maintenance. The purpose of reviewing meteorological data is not to make the annual energy production figures look better, but to identify design assumptions and risks early.

When assessing site conditions, confirm orientation, slope, ground elevation, surrounding obstructions, future land development plans, and the use of adjacent land. In particular on reclaimed or developed sites, the initial topographic information may differ from the finished ground surface. If you input PVsyst using only old drawings or schematic maps, shading conditions and the area available for layout can change after actual construction. Cross-check on-site survey data, the latest layout drawings, development plans, and site photographs, and record which point in time the site conditions reflect; doing so makes it easier to reduce rework in later stages.

In practice, it is also important not to complete the verification of meteorological data and site conditions in a single pass. In the preliminary design stage, evaluate using approximate conditions, and update them to match the latest drawings and on-site information when proceeding to detailed design. Before construction, confirm there are no new nearby buildings, tree growth, changes in site grading, or alterations to racking layout. By making these updates, PVsyst results become not merely initial study documents but practical working documents that can keep pace with design changes.

Review module and PCS settings to reduce calculation discrepancies

To improve the design accuracy of PVsyst, it is necessary to carefully check the settings for the modules and PCS (inverters). In a photovoltaic power generation system, the modules' nominal power, temperature characteristics, voltage-current characteristics, number of modules, number in series, number in parallel, PCS capacity, input range, conversion efficiency, and operating conditions all affect the calculation of energy yield. In practice immediately after installation, people sometimes choose data with similar specifications and proceed with calculations, but when using it for detailed design or proposal documents, it is essential to confirm that the actual equipment specifications to be adopted and the input conditions match.

The first thing to check is the module's basic specifications. In addition to the nominal output, inspect the open-circuit voltage, short-circuit current, maximum power operating voltage, maximum power operating current, temperature coefficients, dimensions, and installation conditions. Even modules with similar nominal output can affect string configuration and compatibility with the PCS if their temperature characteristics or electrical characteristics differ. In particular, the relationship between voltage rise at low temperatures, voltage drop at high temperatures, and the PCS input range affects not only the annual energy yield but also safety-side design verification.

When setting up the PCS, it is important not to judge by capacity alone. Check the number of input circuits, the maximum input voltage, the operating voltage range, the maximum input current, conversion efficiency, the approach to oversizing, and the conditions for output limitations. The ratio of module capacity to PCS capacity affects energy output and the occurrence of peak shaving. Increasing oversizing can increase annual energy generation in some cases, but if it is set while ignoring peak-time limits, temperature conditions, interconnection conditions, and the facility’s overall operational policy, the calculated results are likely to differ from reality.

String configuration is one of the parts of PVsyst input that requires frequent practical checks. Confirm whether the number of modules in series meets the PCS input conditions, whether the number of parallel strings falls within the allowable range for each input, whether strings with different orientations or tilts have been grouped into the same input circuit, and whether circuits that are heavily affected by shading are mixed in. If the single-line wiring diagram or layout drawing does not match the settings in PVsyst, calculated losses or energy yield can deviate from actual conditions. Organizing the string configuration is particularly important for rooftop installations, multiple orientations, sites with elevation changes, and distributed-layout systems.

When configuring modules and PCS, it is necessary not only to enter the specification values but also to keep a record of design changes. If the module planned during the initial study is changed to a different specification, the PVsyst settings must also be updated. Common practical mistakes include changing the equipment name without updating the electrical characteristics, or only modifying the capacity while leaving the temperature coefficients or voltage conditions outdated. When changes are made, it is safer to establish a rule to verify the equipment specifications, quantity of modules, number of strings, PCS capacity, loss settings, and output results together.

Also, to improve design accuracy, it is necessary to manage equipment settings and on-site constraints separately. For example, even if the number of modules is theoretically deployable, in practice changes may be required due to access ways, spacing, maintenance clearances, snow shedding during snowfall, roof loads, ground conditions, and the distance to the electrical room. Verify whether the equipment configuration in PVsyst is constructible on site by checking both the drawings and the construction conditions. Even if the simulation results are good, a configuration that cannot be constructed cannot be said to have high practical design accuracy.

Match shading, orientation, slope, and placement conditions with on-site information.

What is easily overlooked in solar power system simulations is the consistency of shading, azimuth, tilt, and layout conditions. PVsyst can handle shading conditions such as far-field and near-field shading, but if the on-site information that serves as the input assumptions is coarse, the calculation results will also diverge from actual site conditions. In particular, the impact of shading affects not only annual energy yield but also monthly, time-of-day, and circuit-level generation trends. It is important to clearly define how far to consider shading sources — on-site buildings, trees, slopes, adjacent structures, utility poles, signs, fences, surrounding terrain, and so on.

Orientation and tilt should be checked against both the design drawings and the actual site conditions. Even if the plans show an arrangement that appears to face roughly south, the angle can change to match the actual site boundaries, roads, existing structures, and terrain. For rooftop installations, accurately confirm the orientation and tilt of the roof surfaces, and be careful not to treat multiple roof surfaces as having the same conditions. For ground-mounted installations, grading slopes, racking angles, row-to-row spacing, and the height of the panel surface affect shading and solar exposure conditions.

When configuring shadows, adding more detailed shadows is not necessarily better. The important point is to properly identify objects that could affect power generation and represent them in a way that matches the actual site conditions. If you include excessively small, distant obstacles, the work can become more complicated and harder to manage. Conversely, ignoring buildings that cast large shadows in the morning and evening, terrain that causes shading in winter, or trees that will grow can lead to an overestimation of power generation. Keeping a record of which shadows were included and which were treated as having negligible impact will be useful when explaining the results.

When planning layout conditions, checking row spacing and mutual shading is important. Especially for ground-mounted installations, during times when the solar altitude is low in winter, shadows from the front rows can fall on the rear rows. Consider layout not only to maximize power generation but also in terms of site utilization efficiency, constructability, maintainability, drainage, snow accumulation, grass cutting, and inspection walkways. Simply increasing the number of panels may increase total generation in simulations, but mutual shading and reduced maintainability can cause problems in actual operation.

For rooftop installations, check equipment, handrails, upstands, adjacent buildings, lightning protection, and changes in roof level. Shading can be concentrated on certain modules, and depending on the circuit configuration it can cause a larger-than-expected drop in power generation. When modeling shading in PVsyst, it is important not only to place obstacles but to interpret which times of day, which seasons, and which circuits the shadows will affect. Because viewing only annual values on the results screen can make short-duration shading effects difficult to see, also check monthly and hourly trends.

To improve alignment with on-site information, it is also effective to have a system in which decisions are not made solely by the simulation engineer. Surveyors, designers, construction personnel, and sales staff each possess different information. There are obstacles that cannot be understood from design drawings alone, boundary conditions that are not evident from site photos alone, and maintenance access routes that are difficult to notice unless you are part of the construction team. By gathering this information before configuring PVsyst, you can improve the accuracy of shadow and layout inputs.

Design to allow loss settings to be managed and explained with justification

In practical PVsyst work, managing loss settings is particularly important. In photovoltaic power systems, energy production is reduced by various factors such as temperature losses, wiring losses, mismatch losses, soiling losses, shading losses, PCS conversion losses, degradation, and downtime. PVsyst can handle multiple loss items, but if the numerical bases are ambiguous, it becomes difficult to explain the results. To improve design accuracy, loss rates should not be treated as mere input fields; it is necessary to record the rationale and judgments for each project.

First, understand that losses fall into two categories: those calculated from models and equipment characteristics, and those entered by the person in charge based on assumptions. Items related to temperature, wiring, mismatch, and equipment characteristics are calculated from input conditions and models. On the other hand, handling of soiling, snowfall, maintenance outages, and assumptions about future degradation require case-by-case judgments and operational assumptions. If these are not distinguished when set, you may double-count the same type of loss or, conversely, omit necessary losses.

For wiring losses, verify the wiring distance, cable cross-section, current, voltage, routing, and collection method. During the initial study phase, estimated distances may be entered, but in detailed design they must be reconciled with single-line diagrams and layout drawings. Changes in the distance to the PCS, the placement of junction boxes or combiner boxes, or the routing on the DC and AC sides will change the loss settings. If equipment layouts have changed due to design revisions yet wiring losses remain at their initial values, the reliability of the calculation results is reduced.

Soiling loss varies depending on the region and the installation environment. In locations with a lot of dust in the surroundings, near farmland or development sites, where bird damage is anticipated, where salinity has an effect, or on installations with slopes that are unlikely to be cleaned by rainfall, the impact of soiling should be assessed carefully. However, assuming an excessively large loss does not necessarily make the result safe. It is important to refer to the maintenance plan, cleaning frequency, surrounding environment, and the track record of past similar projects, and to document why that value was chosen.

Handling snow requires confirmation of regional characteristics and on-site conditions. Do not assume that PVsyst’s meteorological data alone can automatically reproduce snow adhesion and sliding behavior; instead, as needed, separately document monthly winter losses, mounting-structure height, tilt angle, space for snow shedding, whether snow removal is possible, and maintenance access. Underestimating snow accumulation can lead to large discrepancies with actual winter performance. Conversely, overestimating it can make project feasibility appear worse than necessary. It is important to state the assumptions for each project and keep them in a form that can be reviewed later.

How degradation is handled also requires a practical explanation. The perspective differs between first-year generation and long-term generation assessments. The way degradation is reflected changes depending on whether you are showing a single-year simulation result or considering the long-term trend in generation. When the matter involves contracts, financial planning, maintenance planning, or equipment replacement considerations, be explicit about how you will treat long-term output decline, not just the first year. If you use PVsyst output in proposal materials, it is important to phrase it so readers will not be confused about whether the values are first-year figures or represent an approach that includes long-term evaluation.

In managing loss settings, it is easier to operate if company standard values and project-specific adjustment values are separated. Deciding everything based on the individual staff member's judgment causes variability between projects. Conversely, making everything fixed values results in calculations that do not match site conditions. It is practical to hold a basic value as an internal standard and, when changing it due to site conditions, record the reason. This makes it easier to trace the decision flow even if the designer changes, and easier to verify during internal reviews.

How to Interpret Simulation Results for Design Decisions

After running calculations in PVsyst, it is important not to look only at the annual energy production figure but to interpret the breakdown of the results. Initially people tend to focus on the final energy output and performance indicators, but in practice you check "why the result turned out that way," "which losses are conspicuous," and "where there is room for improvement through design changes." As your ability to read the results improves, PVsyst becomes not just a calculation tool but a basis for making design-improvement decisions.

First, check whether the input conditions and the results are not in major contradiction. Review whether the installed capacity, PCS capacity, azimuth, tilt, meteorological data, and loss settings match the intended values. If the generation is higher than expected, verify that shading, soiling, wiring losses, output limits, treatment of snow, degradation, and so on are properly reflected. If it is lower than expected, check for input errors in azimuth or tilt, inconsistencies in equipment settings, double-counting of losses, or overestimation of shading.

Next, we look at monthly power generation. Annual figures alone make it difficult to see seasonal issues. We check whether temperature-related losses are large in summer, whether insufficient solar irradiance or snowfall affects winter, or whether spring and autumn are relatively stable. Looking at monthly trends makes the data easier to use for maintenance planning and for explaining generation performance. For example, if winter generation is low, you can separately explain whether that is reasonable as a regional characteristic or whether shading or snowfall settings are having an impact.

The breakdown of losses is also important. Depending on whether the cause of low power generation is temperature, shading, wiring, or PCS limitations, the corrective measures differ. If shading is significant, review the layout, row spacing, and how obstacles are treated. If wiring losses are large, consider equipment placement and cable planning. If limitations in the PCS are prominent, check the capacity ratio, circuit configuration, and output conditions. Examining the loss breakdown makes it easier to determine the priority of design changes.

Also, simulation results need to be presented differently depending on the context in which they are used, such as sales proposals, internal approval requests, design reviews, construction planning, and maintenance planning. In sales proposals, avoid excessive technical jargon and clearly present the assumptions and the approach to annual energy production. In design reviews, check in detail the input values, loss settings, consistency with drawings, and points of concern. In construction planning, emphasize the relationships among layout, shading, wiring, and maintenance access routes. Even with the same PVsyst results, the information required varies depending on the reader.

For design decision-making, comparing multiple options is also effective. For example, comparing cases such as changing the tilt angle, widening the row spacing, changing the PCS capacity, or reducing the number of modules to avoid shading makes it easier to evaluate not only power generation but also constructability and maintainability. However, when making comparisons, clearly specify which conditions were changed and which were kept fixed. If multiple conditions are changed at the same time, it becomes difficult to determine which factor influenced the results.

When documenting PVsyst results, it is important to include not only the final values but also the assumptions and caveats. In particular, clearly state if the results are at a preliminary/rough-estimate stage, if shading conditions have not been verified on site, if equipment specifications are not yet finalized, or if loss settings include assumed values. Doing so prevents readers from placing undue confidence in the results and makes it easier to share what should be checked next. The design accuracy required in practice is not just about producing detailed numbers but also about presenting assumptions and limitations in a form usable for decision-making.

Operational Rules for Enhancing Reproducibility by Creating Internal Manuals

After introducing PVsyst, if each staff member uses it differently, the way results are interpreted can vary even for similar projects. To prevent this, it is important to develop an in-house manual and implement reproducible operations. The in-house manual should not be a mere operation guide; it should compile the decision-making rules from receiving a project to submitting the results. It should clarify which documents to check, which values to treat as standards, which conditions should be judged on a case-by-case basis, and at what stages reviews should be conducted.

First, standardize the checklist items at the start of a project. Confirm location information, installed capacity, equipment candidates, layout drawings, site maps, survey results, surrounding obstacles, meteorological conditions, interconnection conditions, construction conditions, and the planned start of operations. If documentation is insufficient, distinguish whether to proceed using assumed values or whether additional confirmation is required. In practice, it is not always possible to begin the assessment after all information has been gathered. Therefore, establish notation rules for assumed values to reduce the likelihood of misunderstandings later.

Next, decide the naming and storage rules for input values. Organize file names and the management ledger so that the project name, review stage, creation date, author, equipment configuration, and differences between design proposals are clear. If you continue overwriting files with old conditions, you will not be able to track past review results. Save each stage—initial proposal, revised proposal, final proposal, pre-construction confirmation proposal, etc.—and keep a simple record of changes; this will help with internal reviews and client explanations.

A review process is also important. Because PVsyst has many input items, it is not easy for the creator alone to find all errors. In reviews, check the meteorological data, site conditions, azimuth, tilt, shading, equipment specifications, string configuration, loss settings, and the plausibility of the results. Reviewers should not only look at the numerical results but also verify that the basis for the inputs is consistent with the drawings. Defining internal check items makes it easier to maintain verification quality even when the person in charge changes.

The internal manual also documents common mistakes. For example: failing to update settings after equipment changes, entering the azimuth in the wrong direction, treating roof inclinations uniformly, overlooking objects that cast shadows, leaving wiring losses as estimated values, double-counting losses, and submitting estimated results as if they were final values. Accumulating such cases can also be used to train new staff. Sharing not only familiarity with PVsyst operations but also where mistakes are likely to occur in practice helps improve design accuracy.

Also, a manual is not finished once it has been created. As projects accumulate, it is updated to reflect comparisons with on-site performance, post-construction power generation, issues identified during maintenance inspections, and the history of design changes. When there is a discrepancy between actual results and simulations, rather than immediately attributing it to a single cause, we separate and check factors such as weather conditions, downtime, soiling, shading, equipment malfunctions, output control, and measurement conditions. Feeding the insights gained back into the in-house manual improves the input accuracy and explanatory ability for the next project.

In internal operations, it is also important not to isolate the person in charge of PVsyst. Create a system in which the design, construction, maintenance, sales, and management departments understand how the results will be used and share the necessary information. If the PVsyst person organizes the input values, the construction staff supplements site conditions, the sales staff confirms points to note in explanations, and the maintenance staff feeds back actual performance after operation, the simulation becomes a foundation for improving the design quality across the company.

Summary: Leveraging PVSyst to Drive the Next On-site Improvements

After introducing PVsyst, improving design accuracy requires more than simply learning how to operate it. You need to put in order, one by one, the meteorological data, site conditions, equipment specifications, shading, azimuth, tilt, loss settings, how to interpret results, and the internal review workflow. The reliability of the simulation is not determined solely by making the input items more detailed. By clarifying which information was used as the basis, which conditions are assumptions, what stage of design it is, and how the results will be used in decision-making, the documents become practical and easy to use in actual work.

What is particularly important is not to let the numerical results be taken in isolation. Annual energy yield, loss breakdown, monthly energy yield, shading effects, PCS limitations, wiring losses, and so on must all be read together with the input conditions. Even when the results look good, confirm that the underlying assumptions are reasonable. When the results are poor, distinguish between elements that can be improved through design changes and those that should be accepted as regional characteristics. Once you can interpret the output this way, PVsyst becomes not just a tool for producing generation figures but a practical manual for comparing design proposals and finding directions for improvement.

Also, it is important that the use of PVsyst not depend on the individual experience of the person in charge. By recording the rationale for inputs for each project, loss settings, consistency with drawings, review results, and change history, and making them reusable within the company, design quality will stabilize. Ensuring that the reasons for past project decisions can be traced will also help train new staff. Furthermore, reflecting post-construction performance and maintenance inspection information when revising simulation conditions will lead to improved accuracy in subsequent projects.

When you are just starting to implement PVsyst, you do not need to get everything in order at once. Begin by documenting the reasons for selecting the meteorological data, cross-checking equipment specifications against input values, recording assumptions about shading and layout, providing a rationale for loss settings, and verifying results on a monthly basis and down to the loss breakdown; by doing so you will more easily embed the practice into your workflow and, over time, be able to produce simulation materials that are easy to explain at each stage—proposal, design, construction, and maintenance.

In the design of solar power generation facilities, it is important to bring desk-based calculations as close as possible to actual site conditions. By linking the conditions organized in PVsyst with on-site surveys, layout studies, pre-construction checks, and post-operation performance verification, you can more easily improve not only design accuracy but also the overall accuracy of on-site decision-making. To make simulation results useful in practice, it is effective to continuously tie together documents, drawings, site verifications, and operational data, rather than treating software settings and on-site information separately.