What is PVSyst? Explaining its role and use cases for beginners

When you become responsible for feasibility studies of photovoltaic power generation, you will increasingly face situations where you are unsure how to estimate energy production, how far to account for the effects of shading, and how to organize design conditions to explain them internally. PVSyst is a representative practical software for systematically conducting such studies on the desk. However, for beginners its many functions can seem overwhelming, and it is often hard at first to grasp whether it is simply a generation-estimation tool, a design-support tool, or a report-preparation tool for evaluations. Therefore, this article organizes what PVSyst is for practitioners and, step by step, provides a clear explanation of its roles, capabilities, use cases, and the concepts beginners should grasp.

Table of Contents

• What kind of software is PVSyst?

• PVSyst's role is not limited to energy yield prediction

• Main tasks that can be performed with PVSyst

• In what situations is it used?

• Basic screens and concepts beginners should understand first

• Why results change with input conditions

• How to approach shading analysis

• How to read the results report

• Common misunderstandings beginners are prone to

• How to proceed when using it in practice

• Considerations when connecting with on-site information

• Summary

What kind of software is PVSyst?

PVSyst is PC software for studying, sizing, simulating, and analyzing entire solar power generation systems. The official documentation describes it as comprehensive software that handles not only grid-connected systems but also stand-alone systems, pump applications, and DC-system applications, and it includes a meteorological database, component databases, and various solar energy–related tools. In other words, rather than being a calculator that simply outputs single values, it is more accurate to regard PVSyst as a design and analysis platform for evaluating the feasibility and performance of an entire solar power generation system while organizing the project's assumptions. When practitioners search "PVSyst とは," their intent is not only to estimate energy output but also to understand how closely real-world conditions can be modeled and how to use the analysis results as a basis for decision-making. PVSyst is exactly the kind of software that addresses both of those needs.

PVSyst is also officially recommended for educational use, and is suitable as an entry point for beginners to learn the thinking behind solar power system design. This is because the large number of input items naturally teaches that energy yield is not determined by irradiance alone, but by many factors such as orientation, tilt, wiring, temperature, soiling, shading, and system configuration. If you think of it not just as software that produces an energy figure but as software that helps you structurally understand how energy yield is determined, PVSyst’s value becomes easier to see. Beginners can be overwhelmed by the number of screens at first, but in practice the essence is not that complicated if you follow the flow of location and weather, system configuration, loss conditions, shading conditions, and result verification. Rather, the ability to organize and compare complex projects is exactly the reason to use PVSyst in professional work.

PVSyst's role is not limited to forecasting energy production

If I had to summarize PVSyst’s role in one sentence, it is to organize the conditions of a photovoltaic power generation system and visualize how differences in those conditions are reflected in the results. Many beginners tend to understand PVSyst as “software that outputs how many kilowatt-hours are generated per year.” Of course that function is central, but the official documentation makes clear that, within detailed time-series simulations, it can handle fine elements such as azimuth, equipment configuration, temperature behavior, wiring resistance, module quality differences, mismatch, angle-of-incidence effects, distant shading, and nearby shading. This means it serves not only to provide an answer for energy production but also to verify the assumptions on which that answer is based. In practice, this “clarification of assumptions” is extremely important, because showing only the energy production figure is difficult to use for internal explanations or decision-making if the conditions are ambiguous.

Furthermore, PVSyst has a built‑in approach from the outset for comparing multiple simulation scenarios. The official tutorial also recommends first creating an initial scenario under minimal conditions, then progressively creating alternative scenarios by adding distant shading, nearby shading, detailed losses, etc., and comparing them. What this reveals is that PVSyst’s role is not to produce a single correct answer but to structurally capture how results differ depending on changes in conditions. For example, you can organize which aspects and to what extent change when you slightly alter the tilt angle, change obstacle conditions, or adopt conservative loss assumptions. What is highly valuable to practitioners is precisely this comparability. Since it can be used at any stage—initial project assessment, internal review, design adjustments, and preparation of explanatory materials—it is more accurate to understand PVSyst as software that supports the study process rather than merely as power‑yield calculation software.

Primary tasks that can be performed with PVSyst

Work that can be done with PVSyst can broadly be divided into preliminary assessment, detailed design, evaluation of shading and losses, result analysis, and comparison with actual performance. The official documentation first presents, as a preliminary assessment stage, a function that allows quick monthly evaluations using only a few general conditions. This is effective in the early stages when you want to get a sense of scale or narrow down candidate sites and layout conditions. On the other hand, the mode that is closer to practical work is the detailed design mode, where, within the framework of a project, you can define the location and meteorological data, choose surface orientations and components, and run detailed time-step simulations. What beginners should know first is that PVSyst has both an "entry point for rough overviews" and a "main body for thorough refinement." You can start using it without entering everything precisely at once, while being able to proceed to fairly deep investigations as needed.

In detailed design, in addition to inputs for the system configuration, you can handle various detailed losses such as temperature behavior, wiring resistance, soiling, mismatch, angle-of-incidence losses, and losses equivalent to downtime. Moreover, these are not considered individually but are evaluated in combination within a single project model. This helps prevent common biases on site, such as overestimating the impact of shading while downplaying temperature or wiring effects. Because energy production is determined by the accumulation of many small losses, a structure like PVSyst that allows you to check each element one by one is very practical. The results can also be reviewed at multiple granularities—monthly, daily, and hourly—and are intended to be output in forms that can be passed to other software. In other words, PVSyst is not limited to input and calculation; it is software designed with analysis and explanation in mind.

Additionally, a capability is provided to import measured data from operating equipment and compare it with simulation results. The official documentation explains that you can import measurement data from monitored real equipment and compare actual performance with simulation variables in a closely matched way. This may seem like a somewhat advanced use case for beginners, but it is extremely important in practice. That is because it allows you to see how closely the conditions assumed at the design stage match actual operational performance. Since it contributes not only to evaluating new projects but also to reviewing existing installations and identifying trends in faults, PVSyst is not software limited to the planning phase. The fact that it can bridge analysis, design, and operational evaluation is a major strength for practitioners.

In what situations can it be utilized?

One of the primary situations in which PVSyst is used is the initial assessment of new projects. Once a potential installation site has been chosen, when you want to see roughly how large a system can fit, how much generation can be expected, and how much difference slope and orientation make, PVSyst becomes a very easy-to-use tool. The official documentation also emphasizes the workflow of creating multiple simulation scenarios within a project and comparing them, and this approach can be applied directly to early comparisons of actual projects. In practice, it is rare to decide on a single final plan from the outset; it is common to deepen the examination by lining up candidate plans and comparing them. PVSyst naturally provides the framework needed for those comparisons.

Next, it is used in the detailed design and internal briefing stages. In photovoltaic system design, you often need to explain why you chose that configuration, why the expected energy yield is what it is, and which losses are dominant. PVSyst provides reports summarizing the key parameters and results and lets you view loss diagrams, making it easy to externalize the judgments in the designer’s mind. Rather than simply saying “it will generate this much,” you can explain “under these conditions these losses occur, and as a result it becomes this much,” which lends credibility to design decisions. Especially when stakeholders are not necessarily photovoltaic specialists, structural presentations like loss diagrams become a powerful tool.

Furthermore, it can also be used for verification after the start of operation. Officially, a feature is provided to import measured data and compare it with simulation variables, which makes it easier to review where the factors causing lower-than-expected power generation lie and whether the set conditions deviate from actual field conditions. For example, when identifying possibilities that soiling, temperature conditions, or shading—factors that were underestimated at the design stage—actually had an effect, PVSyst serves as the basis for re-evaluation. In this way, PVSyst is a software that is meaningful not only for considering new installations but also for downstream processes such as improvement, verification, and explanation. When practitioners learn PVSyst, it becomes easier to find appropriate uses if they position it not only as a tool for design but as a tool to raise the overall quality of project evaluation.

Basic screens and concepts that beginners should understand first

What beginners should first understand is that PVSyst treats "projects" and "simulation scenarios" separately. The official tutorial explains the flow of first defining a project and then creating multiple scenario variants with different conditions within it. A project is mainly a foundation that holds the location and weather data, and you place different calculation scenarios on top of that foundation to compare them. If you grasp this idea early, the overall operation of PVSyst becomes much easier to understand. Beginners often try to cram everything into a single screen and get confused, but in reality you create the foundation, add scenarios on top of it, and compare them. In other words, PVSyst is not software that performs a one-shot calculation from a single file; it is a project-management style tool designed around comparison and iterative improvement.

The next thing to understand is that the initial proposal can be created with minimal conditions. The official tutorial recommends making the first model with only the minimum parameters, leaving the rest to reasonable default values for the simulation, and then adding far shading, near shading, and detailed losses afterward. This is a very important concept for beginners. If you try to fill in every detail from the start, you won’t be able to tell which setting produced which result. First look at the raw results, and then add conditions one by one so you can separate elements with large impacts from those with small impacts. What matters in learning PVSyst is not memorizing all the detailed features, but getting used to the mindset of incrementally adding conditions and reading the differences in the results.

Also, PVSyst has a mechanism to check parameter consistency, and it is officially noted that it will display warnings or "calculation impossible" messages depending on the severity of the issue. This can be reassuring for beginners, but it is also a point of caution. The absence of warnings does not mean everything is perfect. Even if the software deems a calculation feasible, whether it matches actual on-site conditions is a separate matter. For example, inputs may be internally consistent yet not reflect the actual layout or operating conditions. Therefore, do not treat the disappearance of on-screen errors as the goal; always re-examine whether the assumptions you set match the site and project conditions. Beginners tend to focus on the correctness of their operations, but in practice the validity of the assumptions is far more important.

Why Results Change Depending on Input Conditions

The reason PVSyst results change significantly with input conditions is that a photovoltaic system's performance is not determined by a single factor. The official documentation also shows that detailed simulations handle many factors, such as surface orientation, system components, temperature behavior, wiring, module quality differences, mismatch, incidence-angle losses, distant shading, and nearby shading. Conversely, this means that coarse inputs produce coarse results, and higher-quality inputs increase the results' explanatory power. What beginners should first be aware of is that PVSyst is not a magic box. It is excellent software, but it cannot reproduce reality beyond the conditions entered. Therefore, to trust the results you must understand what was entered and clarify which parts are provisional and which parts have been confirmed on site.

Particularly important are the location and weather data. The official tutorial clearly shows the flow for setting location and weather data within the project definition, and the official help treats the creation, management, comparison, and import of weather data as major topics. This means photovoltaic simulations strongly depend on solar radiation and weather conditions. Whether you use data from a point close to the site, standard time-series data, or data that closely matches measured values will change how you interpret the results. Beginners tend to focus on component model numbers and capacities, but in practice the weather assumptions determine the foundation of the results. First check that the location and weather are correct, and then refine the configuration parameters—that order is important.

Also, the detailed loss settings should not be overlooked. The official documentation lists soiling, temperature, wiring resistance, mismatch, angle of incidence, and so on as detailed losses. Each of these may seem small when considered individually, but when accumulated they create non-negligible differences in energy production. A common mistake beginners make is leaving all losses at their default values and relying solely on the resulting numbers. That can be meaningful for initial comparisons, of course, but at the stage where you are accountable in practice, it is important to specify which losses were reviewed and adjusted for the project. PVSyst is valuable precisely because it allows those reviews to be conducted systematically. Rather than looking only at the numbers, tracking the step-by-step build-up of loss assumptions is the shortest route to improving the reliability of the results.

How should we approach shadow analysis?

Shading analysis is what beginners tend to find most difficult in PVSyst. The official documentation also states that near shading is the most challenging part of PVSyst. Shading can be broadly divided into far-field shading and near-field shading: far-field shading is the type that affects the entire installation at once, like a horizon obstruction, while near-field shading is the type where nearby objects cast visible shadows onto the installation surface. Far-field shading is relatively simple to think about, whereas near-field shading requires recreating the surrounding conditions in 3D space and the way shadows fall over time is more complex. If you lump all shadows together as “just shadows” without understanding this difference, you are likely to misread the results. When using PVSyst, it is important to first distinguish whether you are dealing with horizon-level obstruction or partial shading caused by nearby obstacles.

Furthermore, for near shading you need to consider not only the simple loss of irradiance but also losses due to electrical mismatch. The official documentation states that for the direct component of near shading you should separately account not only for losses from reduced irradiance but also for losses caused by electrical imbalance within series- and parallel-connected strings. This is a very important point for beginners. Even if only part of a module is shaded, it can affect the behavior of the entire interconnected system, not just slightly reduce that shaded portion. Many practical cases where people feel "the shading impact is larger than expected" are caused by overlooking this electrical aspect. In PVSyst, both an approximate treatment and a more detailed module-layout-based treatment are provided, so you need to choose between them depending on the accuracy requirements of the project.

If you want to examine detailed electrical shading effects more accurately, a feature to explicitly specify module layout and connections is also officially provided. With this mechanism, by defining each module's position and which series string or system it belongs to, you can evaluate electrical losses due to shading in greater detail. This is somewhat advanced for beginners, but very effective in the final stages of design. In particular, when obstacles cast irregular shadows or partial shading is a concern in complex layouts, a detailed model is more useful for design decisions than a simple estimate. However, the important point here is that using precise shading analysis itself is not the objective. The objective is to understand the impact of shading with the accuracy required for design decisions, without overestimating or underestimating it. In practice, it is more sensible to use a level of modeling appropriate to the project's issues than to make the model heavier than necessary.

How to Read the Results Report

When reviewing PVSyst results, the first thing you should check is not the annual energy production number itself but the consistency between the loss diagram and the key assumptions. The official documentation explains that the loss diagram is particularly useful for identifying weaknesses in system design. In practice, people sometimes document only the final expected energy output, but that masks opportunities for improvement. For example, whether shading losses are large, temperature losses are large, or wiring and mismatch are having an effect will call for completely different design measures. Because PVSyst’s loss diagram breaks the results down into components, it makes it easier to trace why a given value was produced. At the beginner stage, making a habit of looking here first to grasp “where the losses are being incurred” will help you move from merely a recipient of numbers to a person capable of evaluating the results.

What you should look at next are the monthly, daily, and hourly trends. The official documentation shows that many variables can be displayed by month, day, and hour as an output. This means that even if the annual totals are the same, the seasonal dips and time-of-day biases can differ greatly. In practice, characteristics that are not visible from annual totals—such as summer temperature effects, low irradiance and shading in winter, and output declines in the mornings and evenings—can become important. For example, in projects focused on self-consumption, the way generation is distributed by time of day can be more important than the annual total, and shading effects can be obscured by annual averages, causing the real situation to be lost. If you use PVSyst, don’t be satisfied with annual totals alone; it is important to pay attention to behavior along the time axis. Doing so makes it easier to connect design intent with operational reality.

Also, result reports should not be read as a mechanical judgment of “good or bad,” but as explanatory materials that link the assumptions to the outcomes. Officially, you are told that a technical report can be produced that includes the parameters used in each simulation and the main results. This also means you can compare results while preserving the conditions behind them. Beginners tend to focus only on the numbers, but even with the same energy yield, the evaluation changes if the underlying assumptions differ. If you do not distinguish whether a figure was produced by conservative loss settings or by optimistic shading conditions, the report will not be usable in practice. When reading PVSyst reports, look at the assumptions first, then the loss structure, and only then translate the findings into project decisions—being mindful of that order makes their use far more practical.

Common Misconceptions That Beginners Are Prone To

A common misconception among beginners is believing that PVSyst will automatically produce the optimal solution. In fact, the official tutorial recommends first creating a minimal configuration and then adding conditions while comparing multiple scenarios. This shows that PVSyst is not automatic decision-making software but a tool for study and comparison. In other words, PVSyst does not replace the judgment of the person in charge; it structures the information needed for making that judgment. If the project's assumptions remain ambiguous, no amount of calculation will make the results more convincing. Rather, an important benefit of using PVSyst is that it clarifies what is undecided, what is provisional, and what has been confirmed. Beginners, especially, should resist being swayed by the numerical results and develop the habit of checking how well those numbers are supported by solid assumptions.

The second misconception is assuming a design is realistic simply because there are no errors or warnings. Officially, it is explained that the parameter consistency checks will display warnings about whether a calculation is possible. However, being calculable in the software is different from being appropriate for actual site conditions. For example, the calculation may still run even if the positions or heights of obstacles are left coarse, and you can generate a report while leaving loss values at their default settings. Whether those results can be used as-is for project decisions is a different matter. When using PVSyst in practice, you should not make resolving errors the goal; instead, you need to focus on how thoroughly the assumptions have been validated against site conditions. If you misunderstand this, you end up with a simulation that looks tidy on the surface but is thin in substance.

The third misconception is believing that entering shadows will automatically increase accuracy. In reality, handling shadows is very difficult: there are many things to understand, such as distinguishing distant shadows from near-field shadows, the accuracy of 3D representations, and how to consider electrical effects. Even the official documentation states that near-field shadows are the most difficult part and that a separate beginner tutorial is provided. In other words, shadow handling itself is advanced, and simply placing 3D shapes roughly does not make the results highly accurate. What matters is judging which level of shadowing should be addressed for the current project. For initial comparisons, simple distant shadows may be sufficient, whereas for detailed design you may need to delve into near-field shadows and electrical losses. The value of PVSyst lies not in being feature-rich, but in being able to apply those advanced features appropriately according to the issues of the project.

How to proceed when using it in practice

When using PVSyst in practice, it is important not to try to have all conditions perfect from the start. As recommended in the official tutorial, first create a project with the site and meteorological data, create the initial design with minimal conditions, and save it. After that, add far shading, near shading, detailed losses, and, if necessary, a detailed electrical shading assessment one by one, saving each as a separate scenario. The order matters a great deal: if you add all conditions at once, you cannot track why the results changed. Conversely, by adding conditions one at a time and reviewing the results each time, it becomes clear what is influencing performance and by how much. For practitioners, what matters is not only the final numbers but also being able to explain the analysis history that led to them. PVSyst is very well suited to this way of working.

In practice, it is very helpful to keep the initial proposal as the "baseline case" because it makes subsequent comparisons much easier. For example, you might run the baseline case with standard loss assumptions and conditions close to no shading, then add distant shading in the next scenario, add nearby shading in the following scenario, and then review detailed losses in the next step. That way you can understand step by step how much the output dropped due to shading alone and how much changed when you tightened the loss assumptions. This approach is also powerful when explaining results internally. Rather than simply saying "this is the final number," it's better to show "from the baseline case it dropped this much under the shading conditions and changed this much more under the loss assumptions, so we adopt this level," which increases transparency of the decision. The more proficient people are with PVSyst, the more they use it as a comparative design tool instead of for one-off calculations.

Also, it is important to use detailed features only at the end. Even in the official documentation on module layout, detailed electrical shading assessment is positioned as the final stage to be addressed after 3D shading conditions and system definitions have been firmly established. If beginners move on to advanced layout definitions from the start, they end up with nothing but an increased operational burden and the core issue—design decision making—becomes blurred. First grasp the general direction with coarse accuracy, and then only refine the projects that need it. This is a workflow that is less likely to fail in practice. There is no need to create models of the same depth for every project. What matters is deciding how far to refine things based on the project’s scale, surrounding conditions, and the level of accountability required. PVSyst may appear to be all-purpose, but precisely because it is, users must adopt a staged-design mindset.

Considerations when connecting to on-site information

Integration with site information is indispensable for improving PVSyst’s accuracy and credibility. The official documentation also outlines how the quality of input assumptions—meteorological data, horizon information, 3D representation of nearby shading, module layout, and so on—has a major impact on results. In other words, however carefully you calculate in theory, if the site’s spatial relationships and obstacle conditions are unclear, the reliability of the results will hit a ceiling. In practice, site-side information such as the orientation and height of the surface where equipment will be installed, the positional relationships of surrounding objects, the method of establishing reference points, and the consistency of coordinates used within the site determine simulation quality. To truly master PVSyst, you must do more than memorize the on-screen settings; you need to consider which site information to collect and how to collect it to improve input accuracy.

When refining shading and layout conditions in particular, understanding positions on site is important. If the locations of obstacles are vague or the coordinates of candidate installation positions are uncertain, desk-based shading analysis may appear detailed but is effectively based on coarse assumptions. An effective practice is to quickly identify and record reference points and obstacle positions on site, and link them to the design conditions. PVSyst is not a field measurement tool, but its value increases significantly when you input accurate position information obtained on site. In that sense, desk studies using PVSyst and on-site position verification and coordinate acquisition are not separate matters; their coordination is what improves practical accuracy. Rather than relying solely on desk work or solely on field work, adopting a perspective that connects both is the key to progressing from a beginner to a more advanced practitioner.

When you need to efficiently organize site information, it is natural to consider combining an iPhone-mounted high-precision GNSS positioning device such as LRTK. In solar power generation studies, because candidate installation locations, obstacle positions, reference points, and coordinate alignment within the site often become important later on, having a means to capture positions on-site with high accuracy makes it easier to improve the quality of the data fed into PVSyst. The quality of simulations is greatly affected by the quality of input conditions. For that reason, rather than advancing only desktop studies in PVSyst, considering tools that ensure reliable on-site location information will tend to increase the reproducibility and explanatory power of the design.

Summary

PVSyst is a practical software package that enables a complete workflow for photovoltaic power generation systems: feasibility studies, capacity design, detailed simulation, and result analysis. It is not merely a power output calculation tool; its essence lies in supporting design decisions by organizing location and weather as starting points, azimuth, tilt, system configuration, detailed losses, far shading, and near shading, and by comparing multiple proposals. It may appear feature-rich to beginners, but if you first create a baseline case with minimal conditions and then add conditions one by one while reading the differences in results, its role and use cases become quite clear. What practitioners should understand is that PVSyst is not software that automatically decides the correct answer, but software for making assumptions explicit and structurally comparing results.

To truly make PVSyst useful in practice, it is important not to confine it to desk-based settings but to link it with on-site location information and obstruction conditions. If you want the estimated power generation figures to be convincing, you need to increase the accuracy of the input conditions. If you plan operations to include on-site coordinate acquisition and organization of reference points, it can be effective to utilize an iPhone-mounted high-precision GNSS positioning device such as LRTK to make the assumptions used in PVSyst analyses more reliable. By combining desk-based simulations with high-precision on-site positioning, solar power assessment work becomes more practical and reproducible.