7 Basic Guides to Understand What PVSyst Is Without Diagrams

Many practitioners who search for "What is PVSyst" may know the name but remain unclear about what decisions the software is intended to support, how much they can trust it, and how it should be linked to on-site judgment. In particular, for those involved in the planning, design, or feasibility assessment of solar power projects, treating it merely as a power-generation calculation tool will lead to misapplication.

The essence of this keyword is not to memorize detailed operational procedures. What is needed first is to grasp what assumptions this type of simulation software is based on, what kinds of results it returns, and how those results should be interpreted. According to official information, the software is positioned as a PC-based tool for examining entire photovoltaic power generation systems, capacity design, and data analysis; it supports multiple system configurations such as grid-connected, off-grid, and pumped storage; and it is described as being able to handle meteorological data and component databases, simulations at hourly and finer time steps, and profitability evaluations.

Put simply, this is not a "box" that outputs a single number for power generation; rather, it is a foundation for organizing design conditions, breaking down losses, and comparing the validity of proposed plans. In this article, without using diagrams, we organize its role and how to interpret it from a practical perspective. We summarize it so readers can grasp it one level deeper—from merely knowing the name without understanding the contents, to an understanding they can use for initial project assessments and internal explanations.

Table of Contents

• What this software is for

• Design philosophy to understand first

• How to create input conditions

• Scope of cases that can be examined

• How to interpret the output results

• Common points of misunderstanding

• How to apply it in practice

• Summary

What is this software for?

First of all, it should be noted that this software is not a "viewer tool for looking at the performance of solar power generation facilities after completion," but a simulation platform for examining the entire system from the planning stage through the design stage. According to the official help, it is PC software for studying photovoltaic power systems, capacity design, and data analysis, and is said to be capable of handling multiple modes such as grid-connected, stand‑alone, pumped storage, and DC systems. Furthermore, it is equipped with meteorological data and a component equipment database, and is structured with an eye toward comparing design proposals and analyzing results.

This matters greatly in practice. For example, whether it's a rooftop project or a ground-mounted installation, what the person in charge really wants to know is not just "how much power will be generated annually." You need to consider, in one continuous flow, how to set orientation and tilt, how large the shading effects are, whether the equipment configuration is adequate, where losses increase, how monthly output is biased, and how much this will affect project profitability. This software plays a role in linking that series of decisions.

It is also important that a simple preliminary design for initial studies and a detailed analysis that approaches actual operational conditions can be handled within the same methodology. The official help indicates that in preliminary design you can quickly evaluate on a monthly basis using only a small number of general conditions, whereas in detailed analysis you incorporate the actual configuration conditions to examine losses and behavior precisely. In other words, you can progressively deepen the granularity of the study from the project's initial stages through to detailed design.

Without this understanding, the person responsible will end up looking only at the annual power generation figure shown on the results screen. However, the real value lies not in the result itself but in how the assumptions that lead to that result are set and how the losses are broken down. Even with the same generation output, the countermeasures you should take differ depending on whether the design is one in which shading has a large impact, temperature losses are dominant, or wiring losses are excessive. The essence of this software is to make it easier to put design decisions into words.

Design philosophy to understand first

The initial mindset to have when understanding this software is that it is not a tool that automatically produces the "correct answer", but a tool for building up assumptions to create a coherent prediction. The official documentation also explains that meteorological data are the starting point for project assessment and, at the same time, a primary source of uncertainty. Furthermore, regarding loss parameters, although initial values can begin with reasonable defaults, it is recommended that, after the first simulation, each loss factor be carefully redefined to match the actual system.

The important point here is that the more advanced the software, the more the ambiguity in the input is reflected directly in the results. If the person responsible sets conditions with a mindset like "use weather data from a nearby location for now," "use a rough general value for soiling losses," or "shadows don't seem significant so simplify them," the output will have only that level of justification. Conversely, the clearer someone can make the assumptions, the more effectively they can use this software.

Another important point is to treat design and forecasting separately. Design is the act of creating the plan itself—module orientation, inter-row spacing, equipment configuration, how circuits are arranged, and how shading is handled. Forecasting is the act of estimating how much power generation and what kind of loss structure that plan will have. Although this software is a forecasting tool, it also makes the quality of a design visible through comparisons of design conditions. For that reason, it should be used not as a mere table of numbers, but to organize design philosophy.

What tends to confuse practitioners is the belief that “the finer the results, the higher the accuracy.” In reality, producing fine-grained results and having valid assumptions are separate issues. Being able to handle results on an hourly basis, or in some cases at finer time steps, is a strength, but it only becomes meaningful when supported by the quality of the inputs. The official site also emphasizes the ability to perform optimization and simulation at hourly or finer time steps, but this should be understood not as a claim of universal applicability, but as a powerful analytical capability for those who set their conditions properly.

How to Create Input Conditions

When considering input conditions, you should not mechanically enter the information obtained on site as-is, but organize it at a level of detail necessary for design decision-making. The official help states that meteorological data are the starting point for evaluation, and management functions are provided such as geographic site information, weather files, comparison functions, importing known formats, importing custom-format CSVs, synthesizing from monthly values, and creating representative years from multiple years. In other words, the first step of input is to decide "which location's, which period's, and which quality of meteorological conditions to adopt."

In practice, if you handle this carelessly the whole outcome can drift later. Whether you have on-site observations, use nearby data, look at a representative year, or compare multiple years greatly affects the confidence of your decisions. Especially when explaining to internal stakeholders or to financial institutions, being able to explain why you adopted those assumptions is more important than the annual energy production figure itself. This software will perform the calculations, but it will not shoulder the responsibility of explaining the adopted assumptions.

Next to consider are geometric conditions such as orientation, tilt, mounting configuration, row spacing, and surrounding obstructions. Among these, near shading is regarded as one of the most difficult parts even in the official tutorials, which present the idea of creating a 3D scene to evaluate its impact. This means that shading issues cannot be dismissed as mere impressions like “there’s a little shade in the morning,” but should be examined to include the relative positions of objects, temporal changes, and the electrical effects of partial shading.

However, a common pitfall here is trying to reproduce the on-site geometry in excessive detail. Official guidance also notes that the complexity of shadowing scenarios directly increases computation time, and importing overly detailed 3D data is not recommended. In practice, it is important to keep only the shapes that affect power generation and discard irrelevant details. What is required is not precision but the ability to distill and extract the elements that influence power output and losses.

Furthermore, how loss conditions are set is also important. The official help states that various losses—such as angle of incidence, soiling, temperature, module quality, mismatch, wiring, auxiliary equipment, and downtime—can be handled in detail. The point here is not to view losses as “let’s just lump them together as a certain percentage,” but to separate which losses can be improved through design changes and which depend on site operation and maintenance. Simply distinguishing losses reducible by design from those expected as an operational assumption will raise the quality of the analysis.

Scope of Projects That Can Be Considered

Some people assume this software is "exclusively for large-scale grid-connected systems," but the official help states that it can handle not only grid connection but also islanded (standalone) operation, pumped storage, and DC systems. The product overview likewise indicates support for configuration selection and capacity design for the grid-connected, islanded, and pumped-storage modes. In other words, its scope is not limited to simple power-selling projects; it also provides a framework for projects that include self-consumption, projects with strict grid conditions, and projects where load-side considerations are significant.

If you understand this point, it becomes easier to clarify early in a project "what to evaluate." For example, in grid-connected projects the main concerns are annual power generation, monthly output characteristics, losses due to shading and temperature, and assessing business viability. By contrast, for stand‑alone systems a major issue is how stably energy can be delivered relative to the load. For pumped‑storage systems, the question is how extensive a configuration is required to meet water demand and head conditions.

The official help also presents the approach of estimating, at the preliminary design stage: for stand-alone systems, the required generation capacity and storage elements; and for pumped-storage systems, the pump power and the generation-side capacity based on the required water volume and head. In other words, this software is not merely a tool for deciding "how many solar panels to install", but also an evaluation tool that links demand conditions and supply conditions.

For practitioners, the important thing is not to begin an evaluation without correctly selecting the project type. If the type differs, the metrics to consider, the meaning of losses, and the interpretation of results all change. For example, even for a single indicator such as the performance ratio, the way “effectively used energy” is understood differs between grid-connected systems, standalone systems, and pumped-storage systems. Official documentation also explains that the definition of effective energy for the performance ratio varies by system type. Comparing projects while leaving their categories ambiguous makes it easy to draw incorrect conclusions based solely on the appearance of the numbers.

How to Read the Output

The value of this software lies not in the sheer quantity of results, but in the way it organizes "what to look at and what design insights can be obtained." According to the official help, results are compiled into a printable report that lists the parameters used and the key results, and it retains many variables on a monthly basis so they can be reviewed in tables, custom tables, graphs, hourly and daily displays, loss diagrams, and the like.

What you should look at first is not just the annual generation but the monthly distribution. Even if the annual figure looks good, the implications of the project change depending on whether there are large temperature losses in summer, strong winter effects, or poor compatibility with self-consumption. Looking at monthly output reveals how the design aligns with weather conditions. If you explain internally using only annual figures without checking this, discrepancies such as "seasonal variation is larger than expected" or "doesn't match peak demand" are likely to appear later.

Next to look at is the loss diagram. The official documentation states that the loss diagram helps quickly grasp the design quality and is intended to identify the main sources of loss. It also clearly notes that each loss is expressed as a proportion of the energy at the previous stage, so they should not be simply added together. This is very important in practice; for example, the interpretation “soiling loss 2%, wiring loss 2%, shading loss 3% therefore total 7%” is not strictly correct. The loss diagram is a tool for reading, in sequence, where the largest drops occur.

Furthermore, you should also understand how to interpret the performance ratio. The official help describes the performance ratio as an indicator that compares the energy actually and effectively obtained with the energy that should be obtainable under ideal conditions, and it encompasses optical losses, array losses, system losses, and so on. Also, unlike specific yield, it is an indicator that makes it easier to compare system quality from a perspective separate from weather or module orientation itself. In practice, rather than interpreting it simplistically as “more annual generation means better” or “a higher performance ratio is absolutely good,” it is more realistic to use it as an auxiliary indicator to see how healthy the system is relative to the design conditions.

When assessing business viability, the treatment of economic evaluation is also important. The official help states that, based on simulation results, you can estimate long-term profitability using initial costs, annual costs, pricing conditions, and financial terms, and check results such as payback and net present value. What matters here as well is not to treat the profitability figures as a single definitive value, but to interpret them while looking at sensitivity to the underlying assumptions. A few percent difference in power generation can make a large difference in a project evaluation, but sometimes pricing conditions or assumed capacity factors have a greater impact.

Common Misunderstandings

What first-time users are most likely to misunderstand is that, because the results look precise, they will directly reflect reality. In fact, results are always an aggregation of assumptions. Outputs vary depending on the choice of weather data, the degree of shadow simplification, the loss settings, and how equipment performance is specified. Even the official help states that weather data are the starting point for evaluation and the main source of uncertainty. Therefore, the numbers from this software should be treated not as reality itself but as structured predictions that show “what it would look like under these assumptions.”

Another common misconception is to keep using default values as-is. The official documentation states that loss parameters can reasonably be started with default values, but that they should be redefined to match the actual system after the first simulation. In other words, defaults are a convenient starting point but not the final answer. If you ignore project-specific soiling, temperature conditions, wiring length, shading, and stopping factors, the numbers may look tidy, but their explanatory power on site will remain weak.

Also, the evaluation of near shadows is an area particularly prone to misunderstanding. Official tutorials regard near shadows as one of the most difficult parts, and other official guidance shows that over-detailing shadow scenes can greatly increase computation time. What this indicates is that in shadow evaluation, "too coarse is no good, and too fine is no good." Practitioners should adopt an approach of modeling only the objects affected by shadows at an appropriate level of granularity.

Furthermore, care is needed when interpreting the performance ratio. The performance ratio is a useful metric, but it serves a different role than annual energy production. The official help indicates that the performance ratio is effective for comparing system quality and should not be read as directly equivalent to specific yield. Therefore, whether to adopt a design with a higher performance ratio or one with higher annual energy production depends on the project's objectives. The evaluation criteria change depending on whether you prioritize selling electricity, prioritize self-consumption, or face tight space constraints.

How to Implement in Practice

To make practical use of this software in real-world work, it is important not to try to create a perfect model from the outset. First, adopting a preliminary design mindset, set the azimuth, tilt, installed capacity, estimated losses, and weather conditions to grasp the direction of the project. From there, concretize the installation conditions, shading conditions, loss settings, tariff conditions, and so on, and transition to a detailed model — this workflow is realistic. The official help also distinguishes between a stage for quickly performing monthly evaluations with a small number of conditions and a stage for fleshing out the system in detail.

What is also effective is not to stop at a single case but to have comparison cases. By laying out multiple cases side by side—if you slightly increase the spacing between columns, change the tilt, adopt stricter assumptions about shading, or make the loss conditions more conservative—you can see which assumptions are affecting the results. The official help also shows that you can compare reports and compare variants within a project. In practice, these comparisons are what support decision making, because it is more powerful to understand how much the results change under different conditions than to look for a single correct answer.

Furthermore, it is necessary to adopt a perspective for converting the results into explanatory materials for internal and external audiences. Designers can understand by looking at detailed loss diagrams, but decision-makers and project owners do not necessarily do so. Therefore, you need to organize annual power generation, monthly trends, major losses, assumptions, highly sensitive factors, and the outlook for profitability to match the audience. This software produces many outputs, but what practitioners should do is select the key points necessary for decision-making from among them.

Finally, the idea of connecting this software’s predictions with on-site information is indispensable. Even if desk-based conditions are ideal, if the site’s dimensions, orientation, obstacle locations, or interfaces with existing structures are off, the value of the evaluation is reduced. That is why simulations should not be completed in isolation but treated together with surveying, on-site verification, construction planning, and operational assumptions. The deeper the understanding of power generation prediction software becomes, the more clearly the importance of site coordinates and grasping actual site conditions emerges.

Summary

The essence you need to know about this keyword is straightforward. The software in the title is not merely a tool for roughly estimating the energy output of solar power projects. It is a practical tool for organizing meteorological conditions, installation conditions, loss factors, system configuration, and revenue assumptions while comparing a project's feasibility and presenting it in an explainable form. Official information also shows that it can handle the entire workflow—from whole-system assessment and loss analysis to reporting, time-based (hourly) analysis, and profitability evaluation.

What you should understand even without the figures is that designing the assumptions that produce the results is more important than the results themselves. Meteorological data is the starting point and is also at the center of uncertainty. Shading assessment is powerful, but it is a difficult area to handle. Loss diagrams and performance ratios are useful, but misreading them leads to incorrect decisions. If you keep these points in mind, this software will change from a "difficult specialist tool" into a "common language for organizing practical decision-making."

And to take your understanding one step further, you should consider linking desk-based simulations with on-site information. In solar projects, site location information—such as installation positions, obstacle locations, distances to existing equipment, and the shape after development—determines the quality of the design. In such cases, having a system that can quickly capture coordinates in the field and consistently manage photos and point locations greatly increases the accuracy of desk-based assessments. For example, using an iPhone-mounted GNSS high-precision positioning device like LRTK makes it easier to acquire site location data more nimbly. As the next step after understanding power generation simulations, preparing measures to improve the accuracy of on-site surveys will strengthen the flow from planning through construction and explanation.