top of page

Many practitioners get stuck on how to read the notation "PVsyst" when they first encounter it. Although the name appears in tasks such as solar power system design, evaluating generation output, reviewing simulation results, and preparing internal documents, meetings can proceed while it remains unclear how to read it, what it is used for, and at which stage it should be applied. This article organizes six items—from how to read PVsyst to its basic uses, input conditions, interpreting results, and points beginners should watch out for—so that practitioners are less likely to get confused in practice.


Table of Contents

How should one think about reading PVsyst?

PVsyst is analysis software used for evaluating photovoltaic power generation.

Understand the main scenarios in which PVsyst is used

Understand the basics of the input conditions for PVsyst

Key items to check in PVsyst results

Points beginners should be aware of before using PVsyst


How should PVsyst be interpreted?

The pronunciation of PVsyst is sometimes rendered as "pee-vee-sist" in domestic practice. PV is often used as an abbreviation referring to photovoltaic power generation, and "syst" is read as evoking "system," so explaining it as "pee-vee-sist" makes it easier to convey in conversation. However, there is not necessarily a widely standardized official Japanese reading, and some companies or individuals may use a pronunciation closer to "pee-vee-system" or pronounce the letters separately. Therefore, rather than asserting a single pronunciation, it is important to standardize the way it is referred to within your company or project.


What tends to cause trouble in practice is not the pronunciation itself but that a pronunciation is used ambiguously in documents and meetings. For example, even if the designer pronounces PVsyst as "Pee-Vee-Sist," if sales or construction staff use a different pronunciation, it can be hard to tell at a glance whether they are referring to the same software or the same analysis results. Especially in solar power projects, the same name appears across multiple documents — design documents, power generation forecasts, simulation reports, explanations of loss factors, and so on. Therefore, deciding up front on something like "In this document, PVsyst is pronounced 'Pee-Vee-Sist'" makes internal sharing and customer explanations smoother.


When explaining how to pronounce it, you don't need to overthink it. Understanding PVsyst as the name of simulation software used to study solar power generation systems is sufficient as an entry point for beginners. The purpose of learning the pronunciation is not only to pronounce the technical term accurately but to ensure that everyone involved can refer to the same thing when they talk. For staff handling it for the first time, explaining, "It's software used to study the power output and losses of solar power generation, and within our company the pronunciation is standardized as 'Pee-Vee-Syst'," will make it easier for them to understand both the pronunciation and the purpose at the same time.


Also, you need to pay attention to inconsistent notations in documents. If the capitalization or spacing of English letters varies — for example, PVSyst, PVsyst, PV syst — the terms become harder to find during searches or when organizing materials. Because the product name is written as PVsyst, standardize the notation to PVsyst in SEO articles and internal manuals, and it’s helpful to add the pronunciation at first appearance when appropriate. Readers who search for "PVsyst pronunciation" are likely at a stage where they want to know how to treat the name and its basic meaning more than the specialized calculation methods. Therefore, rather than jumping straight into detailed analysis settings, it’s easier for them to understand if you explain the pronunciation, what it’s used for, and how it appears in practical work in that order.


When sharing how terms should be read within the company, it's useful not to rely solely on oral explanations but to briefly note them at the beginning of documents or in a glossary. For example, if you write in a proposal or design review document, "PVsyst is simulation software used for forecasting power generation and checking losses of solar power generation systems," even someone reading it for the first time will find it easier to grasp the context. Standardizing how terms are read may seem like a small thing, but it proves surprisingly effective in document reviews, meetings, client explanations, and handovers. By aligning the entry point to terminology, subsequent technical explanations also become easier to proceed.


PVsyst is analysis software used for planning and studying solar power generation

PVsyst is simulation software used for design studies, capacity assessments, energy production forecasting, and checking loss factors for photovoltaic power generation systems. In solar power, you cannot judge how much electricity will actually be generated by looking at system capacity alone. Even systems with the same capacity can yield different amounts of electricity depending on the installation site, solar irradiance, azimuth, tilt angle, surrounding shading, temperature conditions, cable lengths, equipment configuration, and operational conditions. PVsyst is used to organize these factors and to review annual energy production, monthly trends, and the breakdown of losses.


What beginners should first understand is that PVsyst is neither "software just for drawing plans" nor "a spreadsheet that simply multiplies generation." When evaluating a photovoltaic system, you need to consider multiple factors together: how much solar irradiance is available, how much of that irradiance reaches the panel surface, how much output is reduced by temperature, and how much loss occurs due to conversion and wiring. PVsyst is meant to take those factors as inputs and organize them into simulation results.


However, PVsyst’s results are highly dependent on the input conditions. The software does not automatically produce correct energy yields just by using it. If the site conditions are inaccurate, equipment specifications are entered incorrectly, or shading effects are overlooked, the results can easily diverge from reality. In other words, PVsyst is a useful analysis tool, but the reliability of its results rests on the validity of the input conditions and the verification work. Especially for beginners, it is important not to judge solely by the on‑screen numbers but to follow which assumptions produced those results.


In practical solar power work, power generation forecasts are relevant to a wide range of situations, including proposals, design, financial assessments, and post-construction verification. At the early stage of a project, they may be used to understand how much generation can be expected at a candidate site. In the design phase, they can be used to compare results when orientation, tilt, or equipment configuration are changed. In the operation phase, they are sometimes used as reference material to compare actual and simulated values and to help identify causes when generation is low.


When understanding PVsyst, it is important not to focus solely on the produced energy figures. Of course annual energy and monthly generation are important, but in practice it is essential to go further and check why that generation occurs, which losses are large, and whether the design conditions are reasonable. For example, if shading has a large impact, there may be room to reconsider the layout plan or installation location. If temperature-related losses stand out, you need to review the installation environment and ventilation conditions. If losses related to wiring or equipment configuration are large, it may be necessary to reorganize the design conditions.


In this way, PVsyst is not only a tool for calculating energy production, but also a tool for breaking down and checking the reasons why energy production varies. Beginners do not need to understand all of its functions from the start, but at a minimum, understanding that installation conditions, meteorological conditions, equipment conditions, and loss conditions affect the results will make it easier to read reports without getting confused.


Understand the main use cases of PVsyst

PVsyst is used across the entire scope of solar power projects. The most easily envisioned application is in predicting energy production. When planning a new solar power installation, project developers and designers need to understand how much generation can be expected at the proposed site. Because expected generation affects a system’s profitability and design strategy, it is not merely a reference value but an important piece of information for considering the overall plan.


In the initial feasibility study of a project, it is sometimes useful to check the estimated power generation based on the candidate site's conditions. At this stage, because the detailed design has not yet been finalized, installed capacity, orientation, tilt angle, and the surrounding environment are organized as provisional conditions, and multiple scenarios may be compared. Using analysis software such as PVsyst makes it easier to confirm the differences in generation caused by changes in those conditions. However, it is important to make clear that the results at this stage are for study purposes only and are figures before detailed on-site conditions and the final design have been reflected.


In the design stage, more specific conditions are considered. Reflecting panel layout, azimuth, tilt angle, equipment configuration, wiring conditions, and the effects of shading, we verify whether the design proposal is reasonable. In particular, shading has a large impact on photovoltaic power generation, so how shadows from surrounding buildings, terrain, structures, and between pieces of equipment are handled is important. PVsyst provides functions to assess losses caused by shading, which can also help in revising the layout plan.


Results from PVsyst are sometimes used in preparing proposal documents and explanatory materials. When explaining annual energy production, monthly production, main loss factors, performance indicators, and so on to customers and stakeholders, the simulation report serves as a reference. However, simply listing the figures from the report can be hard for beginners and non-specialist departments to understand. Therefore, when presenting internally or externally, it is important to supplement and communicate "under what conditions these figures were calculated," "which losses are large," and "what design precautions should be taken."


PVsyst results are useful even for pre-construction checks. By confirming that the azimuth, tilt, and layout conditions assumed in the design match the construction plan, you can reduce discrepancies between the simulation conditions and the actual installation. If the layout or angles are changed due to on-site circumstances, you should not continue to use the original simulation results as-is; you need to recheck how the changes will affect power generation. In actual solar PV practice, the design conditions and the construction conditions are not always exactly the same, so awareness of change management is indispensable.


After commissioning, there are occasions when actual generation performance is compared with simulation values. If the energy output is lower than expected, you need to check various factors such as differences in solar irradiance conditions, equipment outages, soiling, shading, temperature, and measurement conditions. PVsyst results can serve as one benchmark when evaluating actual performance, but a discrepancy with measured values does not automatically mean the simulation is wrong or that the equipment has a fault. Different meteorological or operating conditions will lead to differences in results. When making comparisons, it is important to confirm that you are using the same assumptions.


Thus, PVsyst is used in multiple situations—not only for energy yield forecasting but also for design studies, proposal documents, pre-construction checks, and post-operation comparisons. What beginners should understand is that PVsyst should not be seen as a "one-off calculation tool" but rather as a tool for producing documents that help organize conditions and support decision-making at each stage of a project. Because the purpose differs depending on the context in which it is used, the way results are interpreted also changes. In initial assessments it is used for rough comparisons; in the design phase for validating the reasonableness of conditions; in explanatory materials for clarity of communication; and after operation for checking differences from actual performance. Treating it with an awareness of the purpose makes it easier to understand.


Understand the basic conditions to input into PVsyst

When using PVsyst, the important thing is to properly organize the input conditions. Because the simulation results are calculated based on the input conditions, if the inputs remain ambiguous, the report may look polished but the results will be difficult to use for practical decision-making. For beginners, it is more important to understand not "what to input" but "why those conditions are necessary."


The first matters are the installation site and the meteorological conditions. Solar power output is strongly affected by the solar irradiance and ambient temperature at each location. Even with the same installed capacity, annual generation will differ between regions with good insolation and those without. Also, because solar cell output tends to decline in high-temperature environments, temperature conditions cannot be ignored. PVsyst uses such meteorological data to assess generation. What is important here is whether the meteorological conditions entered closely reflect the actual conditions at the target site. Even when using data from a nearby location, caution is required if elevation, surrounding environment, or meteorological characteristics differ significantly.


Next, enter the basic system conditions. In photovoltaic power generation systems, panel capacity, the number of panels, connection configuration, azimuth, tilt angle, mounting method, and so on affect the results. Azimuth and tilt angle determine the amount of solar radiation incident on the panel surface. In general, orientations and angles that receive more sunlight because of the sun’s movement tend to be advantageous for power generation, but in practice they are decided by a balance with site shape, roof shape, mounting-frame conditions, surrounding shading, constructability, and so on. When reviewing PVsyst results, you need to confirm that the azimuth and tilt angle match the actual plan.


Entering equipment specifications is also important. A photovoltaic power system consists of multiple elements, not only panels but also devices that convert DC power to AC power, wiring, protective devices, and measurement equipment. In PVsyst, panel and converter specifications, connection conditions, conversion efficiency, voltage and current ranges, and so on affect the results. Beginners should be careful not to treat model numbers or specifications as equivalent. Even if capacities are similar, temperature characteristics, efficiency, and electrical conditions may differ. If the specifications adopted in the actual design and the input conditions are misaligned, the reliability of the simulation results will decrease.


Setting loss conditions is also an easily overlooked point. In solar power generation, the solar irradiance received ideally does not all become electricity as-is. Losses occur due to various factors such as shading, reflection, temperature rise, wiring, conversion, soiling, equipment variability, and downtime. In PVsyst, these loss factors are treated as conditions and reflected in the results. Even if you use loss conditions at standard values, you need to confirm that they are appropriate for the project. In particular, because soiling, shading, and wiring losses can vary widely with site conditions, it is important to carefully check that they match the actual situation.


Shade conditions are a common stumbling block for beginners. Around a photovoltaic installation there may be elements that cast shadows, such as buildings, trees, hills, fences, equipment, and adjacent rows of panels. Because shading changes with the time of day and the seasons, it cannot be judged simply as "shaded" or "not shaded." When handling the effects of shading in PVsyst, you need to verify how comprehensively the surrounding conditions are reproduced, what range of shading is being considered, and whether the shapes you entered match the actual site. If shading inputs are insufficient, the energy yield may be overestimated.


When managing input conditions, it is also important to leave a record of the rationale. Record which meteorological data were used, from which drawings the azimuth and tilt angles were confirmed, which documents the equipment specifications were based on, and according to what rationale the loss conditions were set, as this makes it easier to check the results later.


When you are not yet familiar with PVsyst operation, you tend to focus on memorizing the screen operations, but what really matters in practice is being able to explain the basis for the input conditions. If questions arise about the results, having records of the input conditions will make it easier to determine what to review.


Main items to check in PVsyst results

When reviewing PVsyst results, it is important not to focus only on the annual energy production. The total energy production is certainly important, but in practice you need to check under what conditions that figure was produced, how it varies month by month, which losses are significant, and whether there are any anomalies in the performance indicators. For beginners, it is easier to understand if, before reading the entire report in detail, they go through the key checkpoints in order.


The first things I want to check are the annual energy generation and the monthly energy generation. Annual energy generation is a basic figure for grasping the overall scale of the project. On the other hand, looking at monthly generation reveals seasonal variations. Solar power generation varies month to month due to factors such as solar irradiance, temperature, and shading. Even if the annual total looks fine, if there is a significant drop in a particular month, it is necessary to check for the effects of shading, meteorological conditions, or design conditions. Understanding monthly trends makes it easier to explain the energy generation.


Next, what you should check is the breakdown of losses. In PVsyst results, you can see at which stages and how much loss occurs in the process from solar irradiance to the final output. By examining the loss breakdown, you can identify the main factors causing a reduction in energy production. For example, if losses due to shading are large, you need to check the layout and surrounding environment. If temperature-related losses are large, you need to consider installation conditions and the effects of ventilation. If conversion or wiring losses are large, you need to verify the appropriateness of the equipment configuration and wiring plan.


Performance indicators are also items you should check. In solar power generation, indicators are sometimes used to show how effectively a system converts the solar irradiance it receives into electrical power. For example, indicators such as the performance ratio can be useful when comparing projects under similar conditions or when assessing the impact of design changes. However, you cannot simply judge the quality of a design by the indicator values alone. Beginners should avoid evaluating indicator values in isolation and should consider them together with the breakdown of losses and the input conditions.


When reading a report, always check the assumptions page and the summary section. Verify that the installation location, meteorological data, system capacity, orientation, tilt angle, equipment specifications, loss settings, and so on match the project you have in mind. In practice, you may duplicate files from past projects when working, and in such cases old conditions can remain. If the site name, capacity, equipment specifications, orientation, tilt angle, etc., remain as they were in the previous project, the entire result will be based on incorrect assumptions. Especially for beginners, it is important to make a habit of confirming the assumptions before looking at the numerical results.


PVsyst results may be used as materials when explaining to customers and stakeholders. In such cases, rather than simply listing technical terms, you should make an effort to explain in an easy-to-understand way what the numbers mean. For example, when explaining the breakdown of losses, describing it as "a representation that divides the factors that reduce power generation into stages" makes it easier for non-experts to understand. For annual generation as well, adding the note "a predicted value based on the input conditions and subject to variation depending on actual weather and operating conditions" helps avoid making overly definitive statements.


When reviewing results, it is important to pay attention to the consistency of the numbers. If the energy generation is excessively large or small relative to the installed capacity, there may be errors in the input conditions or loss settings. If the monthly generation trends look unnatural, you should also review shading, weather conditions, azimuth, tilt angle, and so on. PVsyst reports look well formatted and can tempt you to treat them as correct as-is, but in practice, verification against reasonable ranges is indispensable.


Points Beginners Should Be Aware of Before Using PVsyst

What beginners should be most aware of before using PVsyst is that learning how to operate the software and producing results that are usable in practice are not the same thing. If you follow the on-screen prompts and enter the data, you can obtain simulation results. However, if the basis for input conditions is vague, there are discrepancies with actual site conditions, or you do not understand the meaning of the loss settings, you will have trouble when it comes time to explain the results. The purpose of using PVsyst is not merely to produce a report, but to organize the power generation and losses of a photovoltaic system under reasonable assumptions.


First, it's important not to aim for a perfect analysis from the outset. PVsyst has many input and check items, and it's not easy for beginners to understand everything at once. At first, it's best to start by reliably covering the basic items: installation site, meteorological conditions, system capacity, azimuth, tilt angle, equipment specifications, and main losses. After that, delving deeper into only the necessary parts for each project—such as detailed shading settings and minor loss conditions—will make it easier for the work to become established in practice.


Next, it is useful to prepare a checklist of input conditions. Many errors in PVsyst results are not caused by the software itself but by omissions or mix-ups in the input conditions. Decide in advance which items to check—location, meteorological data, capacity, azimuth, tilt angle, equipment specifications, connection conditions, loss settings, shading conditions, the report date, and the project name—to reduce oversights. Especially when multiple people are working, quality can vary if each person focuses on different check points. Creating a common verification procedure also makes internal reviews easier.


Also, it is important not to treat PVsyst results as definitive. Simulations are predictions based on input conditions and do not guarantee actual power generation. Actual generation can vary due to weather, temperature, snowfall, soiling, equipment outages, maintenance condition, changes in the surrounding environment, and other factors. In proposals and explanatory materials, avoid expressions such as "this amount of generation will definitely occur" and instead present figures as "assumed values based on input conditions" or "predicted values for design consideration." This applies not only to customer-facing explanations but also to internal documents.


File management also requires attention. In PVsyst studies, you may create multiple cases by changing conditions. When similar files pile up—initial draft, revised draft, after reflecting shading conditions, after equipment changes, final submission, etc.—it can become unclear which one is the latest. If you do not organize file names, project names, and condition notes, there is a risk of accidentally submitting results based on outdated conditions. Beginners tend to take management of working files lightly, but in actual practice it is a very important quality-control item.


When sharing information internally, it's effective to explain both how to pronounce PVsyst and what it's used for together. Simply saying, "We will standardize the pronunciation as 'pee-vee-syst,'" does not deepen practical understanding. By also explaining that "it is simulation software used to forecast photovoltaic power output and to verify losses," stakeholders will more easily understand the context of the materials. In particular, when sales, design, construction, and maintenance personnel are involved in the same project, it's important to share which process stages the PVsyst results are used in and under what assumptions they were generated.


Furthermore, it is important not to separate PVsyst results from on-site realities. Even if tidy figures appear on the screen, the actual site may include obstacles that are hard to represent on drawings, changes in the surrounding environment, construction constraints, and factors such as ease of maintenance. Simulations are an important basis for decision-making, but by considering them together with site inspections, design documents, and construction conditions, you can reach judgments that are closer to practical reality. Beginners should avoid treating the software’s results as absolute and instead regard them as material to help explain site conditions.


Finally, to master PVsyst you need to gradually improve your ability to interpret the results. There are stages: starting from learning how to read the outputs, understanding the basic uses, organizing input conditions, checking the breakdown of losses, and reaching the point where you can explain them both internally and externally. You don’t need to memorize all the advanced settings from the start, but developing the habit in each project of checking "which conditions are affecting the results," "which figures to use in explanations," and "where the uncertainties lie" will lead to better practical skills.


Once you move beyond uncertainty about how to read PVsyst, it becomes clearer how to apply solar power generation forecasts and loss verification to practical work. While keeping reading conventions consistent within your company and projects, do not stop at merely understanding labels; it is important to understand installation conditions, meteorological conditions, equipment specifications, loss factors, and how to interpret results as a unified whole. Simulation results can be powerful support for design and proposals, but they only become reliable documents when input conditions and verification procedures are well established. When confirming generation or carrying out design studies in the field of photovoltaic systems, in addition to a basic understanding of PVsyst, it is important to carefully check site conditions, record the rationale for inputs, and ensure assumptions are shared among stakeholders.


Next Steps:
Explore LRTK Products & Workflows

LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.

LRTK supercharges field accuracy and efficiency

The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.

bottom of page