【PVSyst Basic Operations Summary｜10 Key Points Beginners Should Learn First】

Table of Contents

• Understanding PVSyst's basic operations from an overall perspective reduces confusion

• Point 1 Create the project first

• Point 2 Finalize the site and meteorological data first

• Point 3 Plan to compare using variants

• Point 4 Set the azimuth and tilt

• Point 5 Enter system conditions

• Point 6 Don't overlook colored warnings

• Point 7 Run the first estimate quickly with standard values

• Point 8 Refine detailed losses in two stages

• Point 9 Treat shading separately for far-field and near-field

• Point 10 Read results using loss diagrams and performance ratio

• Practical tips to avoid mistakes in real-world use

• Summary

You're less likely to get confused if you understand PVSyst's basic operations in terms of the overall picture

When first exploring how to use PVSyst, there are many input fields and it can be difficult to know where to start. However, the actual structure is not that complicated. The official documentation also presents the basic flow of first creating a "Project" as the framework for detailed time-step simulations, assigning site information and meteorological data within it, and separating calculations with different conditions into "Variants" for comparison. It further specifies the order of defining azimuth and tilt for each variant, setting the system conditions, checking warning messages, and then proceeding to the simulation. Understanding this skeleton at the outset will let you master the software much faster than memorizing the operations on each screen.

A common reason beginners get stuck is that they jump straight into setting detailed losses and shadows. Even the official tutorial recommends creating an initial draft with the minimum parameters, running the calculation once and saving it, and then adding shadow and detailed loss settings while comparing results. In other words, rather than trying to produce a perfect case from the outset, it is more reproducible in practice to first establish a rough draft and then improve its accuracy step by step. This article, following that approach, organizes the ten points beginners should learn first, in order.

Point 1: Create the project first

The first thing to remember is that in PVSyst you create a project as a container for an entire case. The official documentation shows that when creating a project you define the file name and project name, and then proceed to location, meteorological file, project settings, and calculation variants. In other words, it is not software for entering only system conditions on their own; it is structured on the assumption of organizing information and comparing conditions at the project level. If you use it without understanding this, you will get confused when you later compare conditions or rerun calculations. Conversely, if you get into the habit of creating one project per case, keeping your estimates organized becomes much easier.

What matters for practitioners is not to take the initial naming lightly. Project names affect how things appear in reports, and file names influence later searchability and reusability. For example, if you make the location name, project category, and the broad outline of conditions clear, you are less likely to get confused when you look back a few weeks later. Official tutorials also show a workflow of assigning concise, easily identifiable names when saving, and subsequent related files are managed under the same naming scheme. Beginners tend to proceed with provisional names, but simply avoiding this greatly reduces work-related confusion.

Point 2: Finalize locations and weather data first

The foundation that determines PVSyst's calculation results is the site and meteorological data, which come before equipment conditions. The official documentation also defines procedures to set the site and meteorological files early in a project, explaining that a project is organized around geographic location and time-resolved meteorological data. Because power generation simulations heavily depend on inputs such as irradiance, the diffuse component, temperature, and wind speed, tightening only detailed equipment parameters while leaving these unclear will not increase the credibility of the results. For beginners, the first priority is to clarify "which site and which meteorological conditions are being assumed."

The official documentation outlines features such as creating and managing geographic sites, generating hourly weather files, visualizing and comparing weather data, and importing from default sources or custom files. In other words, PVSyst not only lets you arrange equipment, but also provides the foundation for handling meteorological assumptions. What beginners should keep in mind is not to treat weather data as a single absolute solution. In practice, even at the same location, differences can arise depending on the data year and source. Therefore, after creating the initial case, planning to compare scenarios under different weather conditions will improve the accuracy of internal and client explanations.

Also, you don't need to worry excessively from the outset about auxiliary conditions like ground reflection unless there are special circumstances. Official tutorials also suggest starting with the reflectance at its default value and revisiting it only when there is a clear reason, such as snow cover. Beginners tend to want to optimize every item on the first try, but it's easier to maintain the overall quality of the estimate if you first set reasonable assumptions for solar radiation and air temperature, and then dig into only the necessary conditions afterward.

Point 3: Assume comparisons are made across variants

A major strength of PVSyst is that it can hold multiple calculation conditions as variants within a single project. The official documentation also explains that you can create multiple variants per project as needed, and that after simulation each variant can be saved and compared. This is very important in practice, because in real projects comparisons such as "what happens if we change the tilt," "what happens if we change the azimuth," and "how much will it decrease if we revise the loss rate" occur routinely. PVSyst is designed from the outset with these comparative actions in mind.

A common mistake beginners make is repeatedly overwriting a single condition, which makes it unclear which settings corresponded to which results at which point. The official tutorial recommends saving the initial standard simulation and then creating subsequent variants that add things like shadows or losses. It also advises using Save As instead of overwriting when saving so that previous conditions are preserved. In practice, the basic rule is to change only one variable at a time when comparing. Simply following this makes it easier to explain in meetings or reports why a difference occurred.

Another thing to remember is that comparing different weather files also pairs well with variant management. The official documentation explains that the behavior prompting you to save differs when you change a weather file, and that you can compare weather data from different years, for example. Therefore, it can be used not only to compare equipment conditions but also to examine variability in the assumptions. If, from the beginner stage, you adopt the mindset of “not trying to get the one correct answer in a single shot” but rather “grasping the reasonable range by comparing differences in conditions,” you'll be able to get more value out of PVSyst.

Point 4: Set the azimuth and tilt

Once you have created variants, the next important aspect is the orientation of the receiving surface. The official documentation presents defining the orientation of the receiving surface for each variant as a basic procedure, and for fixed installations the simplest method—expressing it with the tilt angle and the azimuth angle—is provided. These settings affect the amount of solar radiation incident on the receiving surface, and therefore directly determine power generation. For beginners, it is important to understand tilt and azimuth not merely as input fields, but as a model of “which direction the equipment faces and how much it is tilted.”

According to the official documentation, on the fixed-mount screen you can drag a red dot while viewing a visual diagram to adjust tilt and azimuth, and a simple optimization tool is also provided to quickly check the relationship between energy yield and tilt and azimuth. However, this is intended only for rough judgment. For beginners, it is safer to use this optimization display not as "the answer" but as a guideline to grasp which direction to move to increase yield. In practice, roof conditions and site constraints are often determined beforehand, so you should prioritize inputs that reflect actual installation conditions rather than pursuing maximum power output alone.

Also, the orientation setting will affect how shadows and losses appear later. Even for the same equipment, changing the direction alters how solar radiation enters, and thus the times when shadows occur and the tendency for temperature rise. Therefore, beginners should first fix orientation and tilt to reasonable values before getting into details. If this remains unclear, no matter how carefully you set the losses afterward, it will be difficult to achieve overall consistency.

Point 5 Enter system conditions

Once the orientation is set, proceed to enter the system conditions. The official documentation explains here a mechanism for selecting the equipment configuration and assisting array design, such as the number of series and parallels. What beginners should first understand is that PVSyst is not simply a tool for entering capacity; it is a tool for assembling a configuration while also checking its electrical validity. Therefore, merely matching the system capacity figures does not immediately produce a valid model. It is important to use this screen with the mindset that it is for checking the consistency of the entire configuration.

The official documentation describes graphs that display the system sizing conditions, a function to revert to the automatically proposed values, and warning displays for condition inconsistencies. In other words, beginners do not need to determine everything by hand calculations from the start; it is realistic to use the software's assistance and keep things within a reasonable scope. What is important here is not to blindly trust the automatic proposals, but also not to overwrite everything manually all at once. First confirm that a viable configuration can be achieved with the proposed values, and then make fine adjustments to match the project's conditions; doing so will greatly reduce configuration mistakes.

Also, beginners should cultivate the habit of reading what warnings mean, not just judging the setup by appearance. The official documentation explains that unacceptable conditions are shown with red warnings, while advisory-level issues are shown with orange warnings. Even if a configuration looks plausible visually, it may not be valid internally. After finishing your input, consider the process complete not when the numbers are filled in, but when you have checked what the warnings are pointing to — this is the quickest way to move beyond being a beginner.

Point 6: Don't overlook color-coded warnings

For beginners in PVSyst, it is extremely important to read the colored warning indicators. In the official tutorial, red is described as an undefined or unacceptable condition, orange as a condition that can be calculated but is not ideal, and green as a defined and correct state. Also, if red remains, the simulation will not be enabled. In other words, when you cannot proceed, rather than searching for "which button to press," it is closer to correct to first check what the red indicator is showing.

This way of thinking can be applied directly in practice. For example, if a calculation has run but some orange warnings remain, that doesn't mean "we're safe because we have results"; it means "you need to pay attention to the assumptions." Beginners tend to look only at the annual generation figures, but the warning colors are also a sign that tells you how to treat those results. First reduce red to zero, then judge the validity of the orange warnings, and finally save in a green state — making this sequence a habit stabilizes the reliability of the output figures.

Also, making a habit of opening the help for anything you don’t understand on the spot will speed up your progress. The official beginner’s page explains that you can open context-sensitive help with F1 from almost anywhere, and that you can access individual explanations via the small question-mark buttons. Because PVSyst has many screens, it’s more reliable to proceed while checking definitions as you go rather than relying on vague recollections. This is especially true for sizing and losses, where similarly worded items are listed; instead of deciding based on your own assumptions, it’s effective to solidify your understanding by using the help.

Point 7: Run the initial estimate quickly using standard values

A practical tip that beginners should learn first is to run the calculation once using the standard settings before entering all the detailed conditions. The official documentation recommends a workflow in which you create a rough variant using default values at the start of each project, and then perform necessary refinements afterward. Also, reasonable default values are set for loss parameters initially, and you are advised to carefully review them after the first simulation. In other words, the purpose of the initial calculation is not to produce perfect numbers but to get the overall model to run and to grasp the skeleton of the results.

The reason this approach is effective is that it lets you quickly discern which factor is the primary cause. By checking the power output and loss diagrams in the initial baseline model, you can get a sense of whether orientation, shading, temperature, or soiling has the greatest impact on that project. From there, it is more efficient to prioritize refining the elements with the largest effect rather than trying to include every loss in detail from the start. What beginners most want to avoid is spending time on fine details only to be left with inconsistencies overall. Creating a calculation that works once, even if rough, will ultimately be the shortest route.

Also, saving the baseline model makes later explanations easier. For example, you can show how much things dropped after adding shadows or what changed when applying dirt month by month, as differences from the reference case. The official documentation also strongly recommends saving and comparing each variant. Beginners tend to keep only the "final version," but it's actually more valuable later to properly preserve the intermediate stages.

Point 8: Finalize the detailed loss in two stages

In PVSyst you can handle many detailed losses such as incidence-angle loss, soiling, irradiance dependence, temperature, wiring, quality differences, mismatch, and downtime rate. The official documentation also shows that these losses are organized in the order of the array loss diagram and can be visualized as results on an hourly, daily, and monthly basis. What beginners should remember here is that setting losses to “include everything” is not the correct approach; in practice, adding items in order of those supported by evidence increases the explainability of the results.

The idea of refining in two stages is effective. In the first stage, grasp the overall picture using default values. In the second stage, overwrite only those items for which project-specific conditions are clear. For example, regarding the effects of soiling, the official documentation explains that there is a large dependence on the environment and rainfall conditions, that it can be set on a monthly basis, and that it is treated as irradiance loss in the calculations. In other words, rather than simply entering a uniform fixed value for soiling, it makes more sense to consider it on a monthly basis taking the site's environment into account. The same applies to temperature conditions and wiring losses. The goal is not merely to enter numbers, but to reflect the site conditions as accurately as possible.

Also, detailed losses are useful when reviewing results. The official documentation states that the effects of each loss can be visualized in a loss diagram, allowing you to understand which factors have the largest impact. Beginners should not stop at looking only at annual energy production; by training themselves to "read which losses are dominant," they will improve the accuracy of their settings in the next project. For example, if temperature losses are large, review the installation conditions and ventilation assumptions; if soiling losses are large, check the maintenance conditions—this way you can turn the results into the next decision.

Point 9 Shadows should be handled separately for distant and nearby

Shadow setup is one of the areas that beginners find most confusing. The official documentation is structured to treat distant shadows and near-field shadows separately: near-field shadows are defined as the visible shadows cast by nearby objects onto receiving surfaces, while distant shadows are handled as large-scale occlusion such as the horizon or distant scene blockers. Furthermore, the documentation explicitly states that near-field shadows are one of the most difficult parts within the software and require detailed 3D description. Therefore, if beginners dive too deeply into this from the start, their understanding often lags behind the amount of input required.

First, it is important to distinguish whether distant shading will suffice or whether near-field shading is necessary. The official tutorial indicates that the horizon profile used for distant shading is effective for sufficiently distant obstacles, and that when the sun moves behind them the direct component is lost. By contrast, near-field shading requires treating the effects on direct, diffuse, and reflected components separately in the hourly shading calculation, and it also involves electrical mismatch losses. In other words, shadows from mountain ranges or distant buildings and shadows between rows or from nearby structures differ in both difficulty and implications. Simply separating and understanding these makes the outlook for shading configuration much clearer.

Furthermore, the official documentation states that handling detailed electrical shading requires the exact positions of each receiving element and their assignment to the wiring. This means that to thoroughly refine near-field shading, simple shape input is not enough—you need to be aware of which parts belong to which circuit. Beginners should first assess in order whether there is far-field shading, whether there is near-field shading, and whether it is truly necessary to handle near-field shading precisely. If you move on to advanced electrical shading before confirming the validity of the base model, you will only increase the input effort and make the results harder to explain.

Point 10 Read results from the loss plot and performance ratios

After the calculations are complete, beginners should first look at the report and the loss diagram. The official documentation explains that simulation results are summarized in a printable report that consolidates not only the main results but also the parameters used. Also, on the results screen a large number of variables are stored on a monthly basis, and graphs can be displayed on a daily or hourly basis, allowing you to check the loss diagram, normalized indicators, performance ratio, input/output diagrams, and so on. In other words, PVSyst is not just a tool that outputs a single annual energy yield, but also a tool for reading the breakdown of results.

Among these, what beginners should prioritize first is the loss diagram. The official documentation also explicitly states that loss diagrams are particularly useful for identifying weaknesses in system design. Looking only at the annual energy production figure does not tell you why that value was obtained. However, by looking at the loss diagram you can see where losses occur — solar irradiation conversion, optical losses, temperature, wiring, soiling, mismatch, shading, and so on. In practice, whether you can read it determines whether you remain merely an estimator or can be involved in design decision-making.

What you should learn next is the performance ratio. The official documentation explains that the performance ratio is a metric that includes optical losses, array losses, and system losses, and unlike energy yield metrics, it does not directly depend on meteorological conditions or the orientation of the receiving surface, making it easy to use for comparing equipment quality at different sites or orientations. What is important for beginners is that a project with a high annual energy yield does not necessarily have a high performance ratio. Good site conditions can increase energy yield, but the performance ratio is useful for assessing the quality of the design and the nature of losses. When reviewing results, make a habit of considering energy yield and performance ratio together to avoid misinterpretation.

Additionally, on the results screen you can call up other variants for comparison, and you can also compare reports with each other. For beginners, understanding progresses if they view results as differences from the baseline case rather than as individual points for each run. What changed when you altered the tilt? Which losses increased when you added shading? How did the performance ratio change when you applied monthly soiling? By reading the differences in this way, PVSyst’s results transform from a mere string of numbers into material for decision-making.

Tips to Avoid Failure in Practical Use

Summarizing the 10 points so far for practical use, the correct way to view PVSyst is not as a tool to "finish everything in one go" but as a tool to "improve accuracy by breaking conditions down and comparing them." First create the project, select the site and meteorological data, and set fixed assumptions; then deepen the model in the order of orientation, system conditions, losses, and shading. Simply following this order will allow even beginners to produce fairly stable estimates. The official documentation as a whole is also structured to create a rough variant first and then layer in the necessary details, and this way of proceeding aligns with the philosophy of the software.

Also, as a rule you should change only one condition at a time. If you change tilt, azimuth, and losses all at once, you won't be able to tell which factor caused the differences. That's why variant preservation is important. If you keep them in stages—baseline case, azimuth-change case, added-shading case, loss-revision case—you'll have strong materials for both internal reviews and client presentations. When interpreting results, not only look at annual energy production but also check loss diagrams, performance ratio, and hourly behavior to make an evaluation that goes beyond mere numerical comparison.

On the operational side, basic actions such as opening the help immediately when you’re unsure, remembering that the red dots on graphical screens can be moved, and exporting tables or graphs for reuse in internal documents as needed are also useful. The official beginner page explains context-sensitive help via F1, dragging the red dots on graphical screens, and exporting result tables and graphs. The more complex the software appears, the more understanding these small operations will greatly affect the time required for tasks. Beginners often feel there are many features they don’t know, but it is sufficient to first reliably learn only the operations you use on a daily basis.

Summary

What matters for a beginner learning the basic operations of PVSyst is not memorizing individual functions in a fragmented way. Create a project, choose the site and weather, compare variants, determine orientation and tilt, set the system conditions, clear warnings, run the standard model first, refine detailed losses in two stages, separate shading into distant and near, and interpret the results using loss diagrams and the performance ratio. If you can understand this flow as a single workflow, even beginners can more easily reach a level usable in practice.

To further improve the accuracy of desk-based simulations, acquiring and cross-checking on-site information is also indispensable. If you take into account site conditions, obstacles, as-built geometry, and post-construction position verification, combining design software with a system that can capture high-precision positions on-site will improve the quality of decisions more than closing the workflow within the design software alone. For example, using an iPhone-mounted GNSS high-precision positioning device like LRTK makes on-site position checks and point cloud acquisition easier, and makes it simpler to identify differences between the conditions assumed during the design stage and the actual site situation at an early stage. For practitioners who want to take power-generation simulations beyond desk-based numbers and link them to on-site verification, this workflow is very well suited.