5 Steps to Create a Project Using the PVSyst Manual

Table of Contents

• What to know before learning how to create a project in the PVSyst manual

• Step 1: Clarify the project conditions and define the project's assumptions

• Step 2: Set location information and meteorological data

• Step 3: Enter the array azimuth, tilt angle, and installation conditions

• Step 4: Select modules and power conditioners

• Step 5: Verify the loss conditions and run the simulation

• Points where beginners tend to get confused when reading the PVSyst manual

• How to view the reports you should check after creating a project

• Checkpoints to avoid failure

• Summary

Key points to understand before learning how to create a project in the PVSyst manual

When proceeding with project creation while reading the PVSyst manual, the first thing to understand is that PVSyst is not simply software that automatically calculates energy production; it is a simulation tool for progressively organizing the assumptions of a photovoltaic system and checking the relationship between design conditions and energy production. You can move the calculations forward simply by filling in the input fields on the screen in order, but if you do not understand why you are entering those items and which values have a major impact on the results, you may end up with a report that looks polished but is impractical for actual use.

One thing beginners particularly tend to stumble over in the PVSyst manual is that the project creation process looks like a single linear workflow, whereas in reality multiple conditions interact with one another. Changing the site information alters the assumptions about solar irradiance and temperature; changing the azimuth or tilt angle changes the amount of incident radiation. Changing the combination of modules and power conditioners alters output limits, conversion efficiency, and the validity of voltage ranges. Furthermore, how you handle wiring losses, temperature losses, shading effects, mismatch, and soiling will change the final annual energy yield and how the performance ratio appears.

Therefore, when reading the PVSyst manual, it is important not merely to learn the screen operations, but to acquire the way of thinking for creating a project. Understanding in which order to enter data, at what stages to set provisional assumptions, and which items to review later will make it less likely to get confused in actual projects. This article organizes the five basic steps along the practical workflow for those creating a project for the first time while reading the PVSyst manual.

Projects created in PVSyst generally simulate a combination of weather data, installation angles, equipment configuration, and loss conditions based on the installation site, such as a power plant or a building roof. In other words, creating a project means correctly converting the project information into the software’s input fields. If you proceed with unclear site conditions, you may later be unable to determine the basis for the inputs, making it difficult to use the results for comparisons or explanatory materials. Conversely, if you organize the conditions from the outset, you can smoothly connect tasks from design comparisons and generation estimates to financial analysis, internal reviews, and customer explanations.

When using the PVSyst manual, it is important not to try to understand all the features at once. PVSyst has many detailed configuration items, and if you delve deeply into loss settings and advanced shading analysis at an early stage when you are not yet familiar with it, you are likely to lose sight of the overall picture. First, master the basic steps of creating a project and complete a simulation once under simple conditions — this is the shortcut. After that, it is practical to review the results, adjust the conditions, and deepen the detailed settings as needed.

Step 1: Clarify the project conditions and establish the project's assumptions

The first step in learning to create a project from the PVSyst manual is to clarify the project conditions before operating the software. Beginners tend to open the software and start entering data right away, but if you proceed while the project's assumptions are still ambiguous, you'll find yourself having to go back repeatedly. In particular, if you don't sort out the installation location, system capacity, installation method, intended use of the generated electricity, and the required level of accuracy for the study stage, it becomes difficult to determine which functions to use.

First, I would like to confirm what stage of study this project is in. Whether it is an initial rough-estimate stage, a stage close to basic design, or a stage for use in estimates and proposal documents will change how detailed the input conditions need to be. In the rough-estimate stage, the focus is on seeing the approximate power generation using standard loss conditions and simplified installation conditions. On the other hand, in the basic design or proposal stage, it is necessary to set more carefully the selection of meteorological data, equipment configuration, installation angle, shading, wiring losses, and so on.

Next, clarify the installation target. Whether it is ground-mounted, roof-mounted, or a special installation such as a carport or agrivoltaic system will change which conditions you need to consider. For ground-mounted installations, row spacing, terrain, surrounding obstacles, and the tilt angle of the mounting structure are important. For roof-mounted installations, the roof’s orientation, slope, usable area, and shading from nearby buildings and equipment are important. If you proceed with simulations while leaving the installation method ambiguous, you will likely need to revisit shading conditions and array configuration later.

How you think about equipment capacity is another point that should be clarified. In PVSyst you assemble the system by inputting the number of modules and the power conditioner (inverter) configuration, but before that you should confirm whether the target capacity is already decided, whether you will determine capacity from the available installation area, or whether you will size it based on grid interconnection and self-consumption. If you decide the target capacity first but it does not match the actual area or equipment configuration, the design will not be practical. Conversely, simply filling the area to its maximum can lead to problems with the ratio to the power conditioner or with handling the generation curve.

Project names and version control are surprisingly important. When comparing multiple proposals in PVSyst, variations such as different orientations, tilt angles, capacities, and equipment types will accumulate under the same project name. If naming is ambiguous, it becomes difficult to tell which proposal is the final one. If you organize from the outset so that the project name, study conditions, creation date, and differences between proposals are clear, you won’t get confused when reviewing reports later.

Also, before creating the project, you should confirm the basis for the input values. Are the azimuth and tilt angles taken from drawings, from on-site surveys, or are they assumed values? Is the installation area calculated from CAD drawings or is it an approximate on-site measurement? Will shading caused by obstacles be modeled in detail, or will it be omitted in the initial assessment? If you document these bases, it will be easier to explain the results later. When following the PVSyst manual during operation, it’s easy to focus on the inputs themselves, but what is evaluated in practice is not only the numerical results but also the clarity of the assumptions that support those numbers.

What matters in this procedure is not having perfect conditions from the start. Rather, it is important to separate confirmed conditions from provisional ones. For example, the installation site and roof orientation may be fixed while the equipment to be used is undecided. In that case, provisionally set the equipment to a standard candidate and proceed on the assumption that it will be replaced later when making the final equipment selection. By separating confirmed conditions from provisional ones, it becomes clear later which parts need to be updated.

Step 2: Set location information and weather data

What becomes important next in the PVSyst manual is the configuration of site information and meteorological data. In photovoltaic simulations, solar irradiance and ambient temperature have a large impact on power generation. If you proceed without confirming which region’s meteorological data you are using, whether you have selected data close to the installation site, and whether there are significant differences in elevation or the surrounding environment, then even if you carry out later detailed settings carefully, the assumptions underlying the basic energy-yield estimates will be off.

At the start of a project, first confirm the installation site’s latitude, longitude, and elevation. Rather than relying solely on the address, knowing coordinates close to the actual installation location increases confidence in the weather data and solar position settings. For large ground-mounted projects the site can be extensive, and the representative point of the address may be far from the actual installation area. Even for rooftop installations, when they span multiple buildings or are located within part of a factory site, assume a position as close as possible to the target area.

When selecting meteorological data, pay attention to the types of data and their representativeness. PVSyst can load available meteorological data or import external data, but beginners tend to assume “any selectable data will do.” However, solar irradiance data can be observational measurements, satellite-derived data, or standard-year data, and their characteristics differ depending on the data period and how they were created. In practice, which data were used may be checked in reports or explanatory materials, so it is important to record the reasons for your selection.

Also, selecting data simply because it is close to the installation site can be insufficient. For example, coastal and inland areas or mountainous and plain areas can have different solar radiation and temperature trends even within the same municipality. In regions with large elevation differences, temperature conditions affect power generation. In snowy regions, you also need to consider winter generation reductions and how to handle snow losses. When configuring meteorological data while consulting the PVSyst manual, it is important not merely to choose the nearest point on the map but to consider how well that data represents the project’s environment.

A common mistake when configuring weather data is proceeding with the default settings. If site information or weather data used in a previous project remain and you create a new project, you may end up simulating under the conditions of a completely different region. Because PVSyst often handles multiple projects, you should make a habit of always checking the site name, coordinates, weather file, time zone, and so on when creating a new project.

Don't overlook ambient temperature data. Solar panels generally see their output decrease as cell temperature increases. Therefore, even under the same solar irradiance, hotter regions tend to experience larger temperature-related losses, which can change the apparent energy production. For high-temperature regions, installations close to the roof surface, or poorly ventilated installations, you need to pay closer attention to temperature conditions. When creating a project in PVSyst, checking not only solar irradiance but also how ambient temperature affects annual energy production and the breakdown of losses will deepen your interpretation of the results.

When you set the site information and meteorological data, do not proceed immediately; first verify that the configured region and project conditions match. Even just reviewing whether the project name, site name, meteorological data name, and coordinates are consistent can prevent many basic mistakes. Rather than simply following the screen descriptions in the PVSyst manual, checking them against your own project information is the foundation for creating an accurate project.

Step 3: Enter array azimuth, tilt angle, and installation conditions

After setting the site information and meteorological data, the next step is to enter the installation conditions for the solar panels. The central elements here are the array azimuth, tilt angle, and mounting configuration. The PVSyst manual shows the screens for entering azimuth and tilt relatively clearly, but in practice how those values are determined is what matters. Even if the inputs themselves are straightforward, if they do not correctly reflect the drawings and on-site conditions, the reliability of the simulation results will be reduced.

Orientation is a fundamental parameter that indicates which direction solar panels face. In many projects in Japan, a south-facing orientation is considered advantageous; however, in practice roof shape, site layout, the timing of power demand, and grid conditions can lead to east‑west or multi‑orientation designs being chosen. When creating a project in PVSyst, it is important not merely to look for the orientation that yields the highest energy production, but to consider the orientation that best matches the project’s objectives.

The tilt angle also has a large impact on power generation. Increasing the tilt makes it easier to receive winter solar radiation, but it also changes the required installation area, wind loading, racking costs, and interrow shading conditions. Reducing the tilt can make installation easier, but it can also affect soiling, drainage, snow accumulation, and maintainability. When entering the tilt angle while consulting the PVSyst manual, you need to base it on practical conditions that include not only energy production but also constructability and maintainability.

When installing on a roof, the orientation and tilt can differ for each roof surface. If you consider the south, east, and west faces separately, you need to decide whether to treat them as a single array or as multiple sub-arrays. If you combine surfaces with greatly different orientations or tilts under one condition, the actual power generation characteristics may deviate. This is especially true for roofs with multiple orientations, since it also affects the generation balance in the morning and evening and the input configuration of the power conditioner, so it is important to organize the design approach before entering the inputs.

For ground-mounted installations, in addition to azimuth and tilt, be mindful of row spacing and shadow effects. During seasons when the solar altitude is low, front-row panels can cast shadows on rear-row panels. In preliminary assessments they may be modeled as a simple inclined plane, but in detailed studies it is important to check the impact of inter-row shading. PVSyst has features to handle near shading and 3D scenes, but beginners should first prioritize entering the basic installation condition values correctly.

In the installation conditions, confirm whether the system is fixed or tracking. For fixed systems, azimuth and tilt are the basics, but for tracking systems you need to consider the change in panel angle that follows the sun’s movement. While tracking systems can potentially increase power generation, their design conditions and loss conditions differ from those of fixed systems. When progressing through project creation while reading the PVSyst manual, it is important to first clarify which installation method applies to your case before configuring settings.

What beginners should watch out for in this procedure is the definition of azimuth. Depending on the software or documentation, expressions that use south as the reference, those that use north as the reference, and the sign convention for east/west may differ. Even if you think you have entered the azimuth from the drawing as-is, misinterpreting the reference can reverse east and west or cause a surface intended to face south to be treated as facing a different direction. It is important to check the azimuth conventions in the PVSyst manual and to make a habit of verifying from the screen display and results after input that the orientation is correct.

After entering the array conditions, reviewing not only the magnitude of the energy production but also the seasonal trends will deepen your understanding. Changing the tilt angle can alter the balance between summer and winter generation even if the annual total does not change significantly. For self-consumption projects, the temporal overlap between demand and generation can be important, not just the annual generation. When creating a project in PVSyst, avoiding design decisions based solely on a single annual generation figure leads to more practical use.

Step 4: Select Modules and Power Conditioners

Next, select the modules and power conditioners that form the core of the photovoltaic system. The PVSyst manual shows the workflow of choosing modules and power conditioners from the equipment database and setting the string configuration and number of inputs. This is the part of project creation that is particularly closely related to practical work. If the choice or combination of equipment is inappropriate, it will affect not only power generation but also the validity of the electrical design.

First, in module selection, check rated output, temperature coefficient, voltage, current, size, degradation conditions, and so on. In PVSyst you may be able to select from the equipment database, but you need to verify that the model you plan to use exactly matches and that the specifications are not outdated. Even if model numbers are similar, output and electrical characteristics can differ. In practice, cross-check the manufacturer's datasheets and design documents to ensure that the data registered in PVSyst is consistent with the equipment to be used for the project.

When selecting a power conditioner, rated output, input voltage range, maximum input current, number of MPPTs, conversion efficiency, and the approach to oversizing are important. If the capacity of the solar panels is made too large, output curtailment is more likely to occur at generation peaks. On the other hand, designing with a certain amount of oversizing in mind can increase the operating rate during mornings, evenings, and low-irradiance periods. In PVSyst, these configuration differences are reflected in the simulation results, so it is important not just to match capacities but to combine components with a clear design intent.

In a string configuration, you determine the number of modules in series and the number in parallel. If the number of modules in series is too low, the string may have difficulty entering the inverter’s operating voltage range. If the number of modules in series is too high, the open-circuit voltage at low temperatures may exceed the upper limit. PVSyst may display warnings or checklist items regarding such voltage conditions, but beginners tend to proceed without closely reading what the warnings mean. If a warning appears, you should not simply dismiss it; instead, check why the warning was issued and reconsider the string module count and equipment configuration.

When dealing with multiple orientations or multiple roof surfaces, it is also important which array is connected to which power conditioner. Combining strings with different orientations or tilts into the same input can increase losses due to differences in power generation characteristics. If conditions can be separated per MPPT, the basic rule is to group strings with the same orientation, the same tilt, and the same shading conditions as much as possible. When learning equipment settings from the PVSyst manual, it is important to understand the on‑screen inputs in conjunction with the actual electrical design approach.

Once you decide on the combination of modules and power conditioners, check the ratio of DC capacity to AC capacity. DC capacity refers to the capacity on the solar panel side, and AC capacity refers to the output capacity of the power conditioner. This ratio affects how clipping losses and output limits appear in simulation results. It's not simply that a high ratio is bad or a low ratio is good; you need to make a judgment based on installation conditions, solar irradiation conditions, the purpose of selling electricity or self-consumption, equipment costs, and operational policy.

A common mistake in equipment selection is becoming complacent simply because you selected a candidate within PVSyst. Even if a device is registered in the database, it may differ from the specifications actually adopted. Model changes or switches to successor models can also occur. It is practical to consider provisional equipment at the project creation stage and update to the official specifications at the final proposal or design stage. Even then, noting that the equipment is provisional will make it easier to review later.

Reading the PVSyst manual lets you understand how to operate the equipment settings, but in practice it is important to be able to explain why a particular combination is chosen. Organizing your thinking about the number of modules, string configuration, power conditioner capacity, and MPPT allocation will make it easier to respond when stakeholders who review the report ask questions. In project creation, equipment selection is a key process that links energy production simulation and design decisions.

Step 5: Verify the loss conditions and run the simulation

When the project's basic conditions, site information, installation conditions, and equipment configuration are in place, finally check the loss conditions and run the simulation. For beginners following the PVSyst manual, these loss conditions tend to be the most difficult part. This is because there are many types of losses, each affecting energy production, and setting them all precisely requires specialized knowledge and on-site information.

Loss conditions include various items such as temperature loss, wiring loss, module mismatch, soiling, shading, power conditioner loss, degradation, and availability. While each of these may seem small when viewed individually, together they can have a large impact on annual energy production. In particular, when using initial/default values as-is, you need to confirm whether those values are appropriate for the specific project. Initial values are merely general assumptions and are not necessarily optimal for every project.

Temperature losses refer to the reduction in output caused by an increase in module temperature. Installations mounted flush to the roof can suffer from poor ventilation, making module temperatures more likely to rise. Ground-mounted installations tend to have relatively better ventilation, but conditions vary depending on local air temperature and mounting height. When handling temperature conditions in PVSyst, it is important to consider both the installation method and the meteorological conditions.

Wiring losses vary depending on cable length, cross-sectional area, and current conditions. In preliminary assessments it is sometimes acceptable to proceed with standard values, but the closer you get to detailed design, the more you need to review them based on the actual wiring routes and cable specifications. In large ground-mounted installations, losses change depending on the distance to the power conditioner and the placement of combiner boxes. Even for rooftop installations, conditions change because of internal building routing and panel placement, so they cannot be overlooked.

Soiling losses depend on the local environment and maintenance schedule. Some environments are easily washed by rain, while others are prone to the accumulation of dirt from dust, pollen, salt spray, bird droppings, and dust from nearby farmland. When setting parameters while consulting the PVSyst manual, you may not know the specific cleaning frequency or site conditions. In that case, it is practical to treat them as assumed values and revise them later once the maintenance plan and site conditions become clear.

Shading effects are also important. Shadows from surrounding buildings, trees, utility poles, fences, rooftop equipment, and adjacent rows affect not only energy production but also reductions in output at the string level. In initial assessments shadows may be handled roughly, but for projects with significant shading a detailed inspection is necessary. PVSyst has functions for shadow analysis, but for beginners it is easier to start by determining whether shading is present and which time periods are likely to be most affected, rather than insisting on complex 3D models from the outset.

After setting the loss conditions, run the simulation. The important thing here is not to stop at looking only at the annual energy production in the results. PVSyst's results contain a lot of information, including monthly energy production, solar irradiation, breakdown of losses, performance ratio, inverter limits, and system efficiency. It is important to check not only whether the annual energy production is close to the expected value, but also which losses are large and whether there are any anomalies in the monthly production trends.

After the simulation, what you should check is the consistency between the input conditions and the results. For example, if the system is south-facing and the tilt angle is typical but the energy production is extremely low, there may be an unnatural setting in the weather data, orientation settings, shading, equipment configuration, or loss assumptions. Conversely, if the energy production is too high you should also be cautious: you may have underestimated losses, ignored shading, or the installation conditions may be more favorable than reality.

When using the PVSyst manual to create a project for the first time, it is important not to try to achieve perfect results in one go. First complete a simulation with the basic conditions, then change the azimuth, tilt, capacity, and loss conditions one by one to observe the differences in results; this makes it easier to understand how much each input influences the outcome. Project creation does not end with data entry—it is a process of reading the results, reviewing the conditions, and comparing them to improve accuracy.

Common points where beginners get confused when reading the PVSyst manual

Beginners creating a project while reading the PVSyst manual tend to be confused less by the number of screens than by the meaning and priority of each item. You may feel you must understand every item perfectly before using it, but in practice it is realistic to first set the basic conditions correctly and then refine the detailed settings while reviewing the results.

The first thing that tends to cause confusion is which mode or screen to start from. PVSyst offers various analysis functions, but when running a power generation simulation for a typical solar power project, the basic approach is to organize the location, weather, orientation, equipment, and losses in that order according to the detailed project settings. Beginners tend to jump back and forth between multiple menus, but if you first aim to create a single project all the way through and produce a report, it becomes easier to understand the overall picture.

Another common point of confusion is how far one should rely on initial values. PVSyst may provide standard values and initial settings, but using them as-is is not always incorrect. In early-stage estimates it can be useful to use standard values to observe general trends. However, when standard values are used, it is important to understand the underlying assumptions and to review them at the appropriate stage. In particular, loss conditions and equipment data tend to vary between projects, so always verify them before making a final decision.

You also need to pay attention to differences in units. PVSyst handles many numerical values such as capacity, voltage, current, area, angle, and loss rates. When entering values in input fields, you must check that the units match what you expect. For example, if you mix up decimals and percentages in a field for entering a proportion, the results can change significantly. After entering numbers, it is important to check the results screen and any warning messages to confirm that values fall within a reasonable range.

Handling warning messages is another area where beginners can get confused. In PVSyst, warnings or cautions may appear when there are problems with the equipment configuration, voltage ranges, or input conditions. A warning does not necessarily mean that a simulation cannot be run, but it is dangerous to proceed without understanding what it means. Warnings are important clues that indicate design inconsistencies or insufficient checks. Check the relevant items in the PVSyst manual and, if necessary, modify the equipment configuration or input conditions.

Another area where beginners often get confused is judging whether the results are reasonable. PVSyst can produce detailed reports, but because there are so many numbers it can be hard to know where to look. At first, it is good to focus on annual energy production, monthly energy production, the performance ratio, and the main breakdown of losses. By checking these, you can grasp how efficiently the system as a whole is generating power, which losses are significant, and whether the seasonal generation trends look natural.

How to View Reports You Want to Check After Creating a Project

After creating a project in PVSyst and running the simulation, carefully review the report. The purpose of creating a project is not simply to produce a report. The objective is to interpret the relationship between the input conditions and the results, and to make them usable for design decisions and explanations. Therefore, when using the PVSyst manual, you need to understand not only the input screens but also how to read the reports.

The first thing to check is an overview of the project conditions. The report displays site information, weather data, system capacity, modules, power conditioners, array azimuth, tilt angle, and so on. Here you confirm whether the input conditions match the project. If you look only at the power generation results, you may not notice if the site or azimuth is incorrect. Confirming the conditions at the beginning of the report is especially important when creating multiple proposals.

Next, check the annual and monthly energy production. The annual production figure tends to attract the most attention in proposals and comparisons, but examining monthly trends lets you assess whether the results are plausible. Look to see whether regions with high summer solar irradiation show higher summer generation, and whether regions where shading or snow is expected in winter show lower winter generation—i.e., whether the results match the local characteristics. If the monthly generation appears extremely unnatural, review the meteorological data, shading conditions, and orientation settings.

Performance ratio is also an important metric. The performance ratio is used as an indicator to assess how efficiently an actual system produces power compared to ideal generation. However, care must be taken when judging good or bad based solely on the performance ratio. It is not simply the case that a higher value is always better or a lower value is always worse; it varies depending on installation conditions, weather conditions, loss settings, and equipment configuration. The performance ratio is useful when comparing multiple options under the same conditions or when verifying the validity of loss settings.

The breakdown of losses is particularly important in a PVSyst report. If the energy production is lower than expected, you can check where the losses are largest. You examine whether temperature losses are large, whether shading effects are significant, whether power conditioner limitations are substantial, or whether wiring losses or mismatch are at play. Once you identify which items have large losses, the directions for design improvement become clear. For example, if shading losses are large, you can reconsider the layout or inter-row spacing; if output limitations are large, you can consider reviewing the DC/AC ratio or the power conditioner capacity.

When reviewing a report, consider not only the numbers but also whether they can be used to explain the results. In internal reviews and client briefings, you need to clearly convey why this power generation was obtained, what assumptions were made, and which losses are significant. Because PVSyst reports contain a large amount of information, handing them over as-is can make them difficult for others to understand. Organizing the key assumptions and results and preparing supplementary materials as needed makes it easier to apply the simulation results in practice.

Checkpoints to avoid failure

When learning how to create projects with the PVSyst manual, it is important to check at three stages—before input, during input, and after simulation—to prevent mistakes. Before input, confirm that the project conditions have been organized. If the installation site, installation method, system capacity, orientation, tilt, selected equipment, and study objectives remain unclear, you are likely to become confused during project creation.

During data entry, check the consistency of each item. Confirm that the site information and meteorological data are correct, that the azimuth and tilt match the drawings, that the module and power conditioner models correspond to the assumptions, and that the string configuration is feasible. In particular, when duplicating a previous project, be careful not to leave old conditions in place. Duplication is an efficient method, but forgetting to update the site and meteorological data, equipment, or loss conditions can lead to incorrect results.

After the simulation, we verify the validity of the results. We look not only at the annual energy production but also at the monthly production, loss breakdown, performance ratio, and warning indications. If the results show extremely high or low energy production, we do not adopt them as-is and instead review the input conditions. Because PVSyst calculates based on the entered conditions, it can produce a plausible-looking report even if the inputs are incorrect. For that reason, the ability to interpret the results is important.

When comparing multiple proposals, it is important to keep the comparison conditions consistent. If you want to compare only orientations but the equipment or loss conditions are also different, you will not be able to determine what is causing the difference in power output. When comparing capacity differences, angle differences, equipment differences, etc., avoid changing too many conditions at once and keep everything other than the element you want to compare as similar as possible. This makes it easier to interpret the effects of design changes.

Don't forget file management. In PVSyst, data accumulates for each project and for each design option. Make project names and version names clear, and distinguish the final plan, comparison plans, and provisional plans so they are easier to check later. When exporting reports, use names that indicate the creation date and differing conditions to prevent misunderstandings among stakeholders.

Finally, when learning from the PVSyst manual, the most effective approach is to carry a single project through to the end. While it is important to understand individual configuration items along the way, experiencing the entire process—from project creation to simulation, report review, and revising conditions—helps you understand how each item connects. At the beginner stage, prioritize reliably mastering the basic procedures rather than trying to fully master advanced settings from the start.

Summary

When learning how to create a project in the PVSyst manual, it is important not just to memorize screen operations but to understand how to translate project conditions into simulation parameters. The basics of project creation are: organizing the project conditions, setting the site information and meteorological data, entering the array azimuth and tilt angle, selecting the module and power conditioner, checking the loss conditions, and running the simulation. By mastering these five steps, even those using PVSyst for the first time will find it easier to grasp the overall picture of power generation simulation.

What is particularly important is to make the basis for input values clear. Organizing which meteorological data were used, which sources the azimuth and tilt angles are based on, whether the equipment are officially adopted items or provisional settings, and whether the loss conditions are standard values or adjusted for the specific project will enhance the explanatory power of the report. While PVSyst can perform detailed calculations, if the input conditions remain ambiguous, the reliability of the results will also be ambiguous.

When viewing simulation results, it's important not to judge only by the annual energy production. Check the monthly energy production, the performance ratio, the loss breakdown, and any warnings, and confirm that the input conditions and the results connect logically. Instead of simply concluding that high production is good and low production is bad, being able to explain why the results occurred is essential for using PVSyst in practice.

The PVSyst manual is useful as a reference for checking operating procedures, but to produce results in practice you need to read the manual in conjunction with the specific project conditions. Start by completing a project once using basic conditions, then change the orientation, tilt, capacity, equipment, and loss conditions and compare the results to internalize PVSyst’s approach. Creating a project is not a one‑time task but an iterative process of checking conditions, interpreting results, and making improvements as needed.

If you are just starting to use PVSyst, I recommend first taking a single project as an example and creating the project following the five steps introduced here. By working through organizing the project conditions, selecting meteorological data, entering installation conditions, configuring the equipment setup, and checking losses and running the simulation, you will come to understand each item in the PVSyst manual not as mere explanations but as practical inputs for decision-making. The first step to improving the accuracy of power generation simulations is not to memorize all the complex functions, but to accurately build up the basic procedures.