【How to Create PDF Reports in PVSyst｜4 Foolproof Steps】

Table of Contents

• What should be conveyed in a PVSyst PDF report

• Input conditions to prepare before creating the PDF report

• Step 1: Finalize the simulation results

• Step 2: Confirm the items to include in the report

• Step 3: Check numbers and display settings before output

• Step 4: Save as PDF and prepare for submission

• Common mistakes in creating PDF reports and how to prevent them

• Tips for making PDF reports easy to read in practice

• Increase report credibility by improving the accuracy of site conditions

• Summary: The quality of a PDF report is determined by pre-output checks

What should be conveyed in a PVSyst PDF report

PVSyst's PDF report is not simply a document for printing annual energy generation. It is a document that compiles the PV system's design conditions, the meteorological data used, system capacity, azimuth, tilt, losses related to wiring and equipment, shading effects, monthly energy generation, annual energy generation, performance ratio, breakdown of losses, and so on, in a form that third parties can verify. In other words, the PDF report provides the supporting evidence to fulfill the accountability of “under these conditions, the calculated energy generation is this.”

In practice, the person looking at PVSyst’s result screen and the person reading the PDF report are not necessarily the same. Even if the designer is familiar with the detailed settings, owners, sales staff, construction managers, approvers, and financial stakeholders may make their decisions based only on the information contained in the PDF. Therefore, the PDF report must include not only the calculation results themselves but also information that allows readers to understand why those results were produced.

What is particularly important is not to overemphasize generation figures alone. Even if annual energy production appears large, the meaning of the assessment changes depending on whether the input installed capacity is large, the solar irradiance conditions are favorable, the loss settings are overly optimistic, or the effects of shading are not adequately reflected. The purpose of producing a PDF report is not to show convenient numbers but to present the input settings and calculation results together so that the reader can verify their validity.

Also, PVSyst PDF reports are also used to compare design proposals. For example, when comparing proposals with different tilt angles, different numbers of panels, different PCS capacities, or different methods of accounting for shading, you may place each PDF report side by side for review. In such cases, if the report condition names or case names are unclear, it becomes difficult to determine which proposal corresponds to which conditions. Before outputting the PDFs, it is important to organize the project name, variant name, and condition name so that readers of the report will not be confused.

When creating a PDF report with PVSyst, being aware of the four roles—"preserve calculation results," "use as a submission document," "use for comparative evaluation," and "explain to internal and external stakeholders"—clarifies which items should be checked. Rather than just memorizing the output operations, confirming that the report contains all the necessary information is the first step to creating a reliable PDF.

Input Conditions to Prepare Before Generating a PDF Report

The quality of a PDF report is largely determined by the input conditions before output, not by the output itself. No matter how neatly you create a PDF in PVSyst, if the meteorological data, design conditions, loss settings, shading settings, or equipment configuration are inadequate, the report’s reliability will be reduced. Before generating the PDF, you must first confirm that the simulation conditions are in a state that can be explained in practical terms.

The first things I want to check are the site settings and the meteorological data. In solar power generation simulations, solar irradiance and temperature have a large impact on power output. If the site is offset from the actual candidate location, or if data from a nearby site are used without explanation, readers of the report will find it difficult to judge the validity of the results. The site name, latitude, longitude, elevation, and the period and types of meteorological data displayed in the PDF report are items you should always verify.

Next, it is necessary to confirm the equipment configuration. Panel capacity, number of panels, string configuration, PCS capacity, azimuth, tilt angle, mounting method, and so on are assumptions for the estimated power generation. In particular, even if the annual generation is the same, evaluations will differ if the system capacity is different. Because PDF reports check not only annual generation but also generation per unit of system capacity and the performance ratio, any error in the system configuration will affect the credibility of the entire report.

Loss settings are also important. PVSyst simulates various factors such as temperature losses, wiring losses, mismatch losses, soiling, degradation, shading, and equipment efficiency. Even if you use these values as the default, in practice you should be able to explain why those values were used. In particular, in the PDF report for submission the loss diagram shows which factors are reducing the energy production, so settings that appear unnatural will immediately raise doubts.

When considering the effects of shading, also check the 3D scene and obstruction settings. If the terrain, surrounding buildings, trees, shading between mounting structures, or placement conditions in the east, west, south, and north differ significantly from reality, the shading losses shown in the PDF report can become inconsistent with on-site observations. In particular, at locations where shading occurs during periods of low solar elevation, results may differ between reports that omit shading settings and reports that take shading into account.

Furthermore, case names and variant names should not be overlooked. When you review a PDF report later, names like "final version," "revised version," or "comparison 1" can make it difficult to understand the contents. In practice, using names that indicate the tilt angle, PCS capacity, whether shading is considered, equipment capacity, etc., can reduce misunderstandings among stakeholders. Before exporting the PDF, organizing report names so that the conditions can be judged to some extent from the name alone will make post-submission checks smoother.

Step 1: Finalize the simulation results

The first step in creating a PDF report in PVSyst is to determine which simulation results will be included in the output. If you generate a report while testing multiple cases, you may accidentally submit outdated conditions or conditions that are still under review. Before exporting to PDF, you need to clarify which variant is the final version and which results will be shared with stakeholders.

When finalizing simulation results, first check whether multiple variants exist within the project. When initial studies, modified proposals, shaded and unshaded versions, capacity-change proposals, etc. are listed, it can be difficult to judge by name alone. Because a PDF report, once generated, is treated as an independent document, outputting the wrong case will require later replacement or explanation. For the conditions to be used as the final version, give them clear, descriptive names and make sure they are not confused with unnecessary interim proposals.

Next, confirm whether the simulation has completed successfully. If warnings appeared during the calculations or there are unset items in the input conditions, creating the PDF as-is may result in documentation that is insufficient for submission. In PVSyst, warnings and cautions may be displayed depending on the design conditions, but they are not all necessarily critical errors. However, you should avoid exporting outputs without first checking the meaning of the warnings. For example, cautions regarding equipment configuration combinations, voltage ranges, capacity ratios, missing data, or shading settings could affect the validity of the results.

Check not only the annual generation but also the monthly generation. Even if the annual value is close to expectations, if the monthly variations are unnatural, there may be problems with the meteorological data or the installation conditions. For example, seasonal variations that do not match regional characteristics, extremely low generation in a particular month, or shading impacts being larger than expected are items you want to review before outputting the PDF. Monthly values are important information for readers to understand generation trends, so they should be included among the checks before preparing the report.

We also check PR. PR is an indicator of how efficiently the system generates power relative to solar irradiance conditions. If PR is extremely high or low, you need to review loss settings, temperature conditions, equipment settings, shading settings, and so on. Because PR is often presented prominently in PDF reports, it is an item that readers are likely to ask about. It is important not just to look at the number but to be able to explain why that value occurred.

The loss diagram is also an item you should always check before finalizing simulation results. By looking at the loss diagram, you can understand where and to what extent losses occur from the point sunlight reaches the panel surface to the final AC output. Confirming whether temperature loss, wiring loss, shading effects, or equipment efficiency have the greatest impact makes it easier to explain the results. For readers of the PDF report, the loss diagram is also an important part for understanding the flow of the calculations.

At the stage of finalizing simulation results, review them from the perspective of “would I be able to explain the conditions and the figures if I submitted this report as-is?” Even if the system technically allows PDF output, it may not yet be finalized in practical terms. Spending time on checks before output is the quickest way to reduce rework.

Step 2: Confirm the items to include in the report

The next step is to review the items to include in the PDF report. PVSyst reports contain a variety of information, including a project overview, system configuration, meteorological conditions, simulation results, loss diagrams, monthly values, and more. In practice, because the items prioritized differ depending on the report’s audience, it is important to ensure that no necessary information is missing.

For internal technical verification, the details of input conditions, loss settings, and equipment configuration are important. During design reviews, points such as why that capacity was chosen, why that tilt angle was selected, and how the effects of shading were accounted for are checked. On the other hand, for owner briefings, it is important that annual energy production, monthly energy production, generation trends, and the main loss factors are presented clearly. How the PDF report is presented will vary depending on whether the recipient is a technical or non-technical audience.

However, overly simplifying a PVSyst PDF report can make it impossible to verify the conditions later. While prioritizing readability is important, if the supporting conditions are omitted the energy yield can end up standing alone without context. In particular, it is desirable to ensure that weather data, system capacity, azimuth, tilt angle, loss assumptions, and whether shading is accounted for can be verified on the PDF.

When checking report items, first review the cover and opening sections. Verify that the project name, location, variant name, creation date, and summary are displayed appropriately. If names are ambiguous here, it will cause confusion when comparing multiple proposals. For example, if the same project includes a "south-facing proposal" and an "east–west proposal," it is important to ensure that not only the PDF file names but also the names within the report are distinguishable.

Next, check the system configuration display. Verify that the panel capacity, number of panels, total capacity, PCS configuration, number of strings, and other items match the design documents. If there have been design changes, sometimes only the parameters in PVSyst are updated, causing discrepancies with figures in other documents. Because the PDF report is treated as the submitted document, confirming its consistency with the other design documents will reduce questions in later stages.

Displaying meteorological conditions is also important. Check whether solar irradiance, temperature, and location information can be confirmed on the report. In photovoltaic simulations, meteorological conditions have a large impact on the results, so reports that do not indicate which location data were used or what the solar irradiance conditions were are difficult to explain. Even if the conditions reflect the surroundings of the candidate site, it is important to make those assumptions understandable to the reader.

In the results section, the items to check are annual generation, monthly generation, PR, and the loss diagram. Rather than looking only at annual generation, examine monthly fluctuations and the breakdown of losses as well. Readers of the PDF report may want to know not only the overall amount of generation but also where losses are occurring and where there is room for improvement. Therefore, check whether the loss diagram is displayed in a readable way and whether key figures are missing.

In this step, be mindful of "who will read this PDF" and "what that person wants to decide." A PVSyst PDF report is not complete simply because it has been generated; it only becomes a document usable in practice once it contains all the information the reader needs to make a decision.

Step 3: Check numbers and display conditions before output

Before saving as a PDF, check the numbers and display conditions. If you skip this step, you may notice errors after output and have to recreate the PDF. Although PVSyst results can be reviewed across multiple screens, the PDF is what will ultimately be submitted. Therefore, you need to verify that the numbers you saw on the screen are the ones that appear in the PDF under the intended conditions.

First, check the value of annual energy production. In PVSyst, results can change even with slight adjustments to design or loss parameters. If you have run multiple simulations during the study, verify that the number you last viewed truly corresponds to the final conditions. In particular, after toggling shadow settings, changing equipment configuration, modifying loss rates, or replacing meteorological data, be careful to ensure the recalculation has been correctly reflected.

Next, check the relationship between installed capacity and annual generation. While a larger installed capacity will lead to greater annual generation, you should verify whether the generation per unit of capacity is reasonable. If you look only at generation, it is easy to overlook the impact of differences in capacity. When creating a PDF for comparison, you need to make clear whether each option has a different installed capacity or whether the same capacity is used with only the conditions changed.

We also check the PR value. PR is an indicator used to evaluate system performance based on meteorological and equipment conditions. If the value is too high, it may indicate that loss settings are insufficient, while if it is too low, factors such as shading, temperature, equipment configuration, and wiring losses may be having a large impact. Of course, the acceptable range varies depending on project conditions, but you should avoid putting unexplained figures into a PDF.

Check the balance of monthly power generation as well. Even if the annual value appears reasonable, if the monthly values show an unnatural bias there may be issues with the site configuration or meteorological data. Also, if shading has a large effect in specific seasons, reviewing the monthly values can help identify that tendency. Since the reviewer may ask "Why is this month particularly low?", it's reassuring to organize the reasons before generating the PDF.

In the loss diagram, check the magnitude of each loss. Verify whether values such as temperature loss, wiring loss, shading loss, and equipment loss are too large or too small when compared with site conditions and design conditions. For example, if there are obstructions nearby but shading loss is almost nonexistent, the shading settings may not have been sufficiently reflected. Conversely, if shading loss is large in a location that should have little shading, you need to review the 3D scene and the placement conditions.

We also check display conditions such as units, decimal points, language, report orientation, and page layout. For internal review, including somewhat detailed information is acceptable, but for submission readability is required. If a PDF has too many pages, readers will find it harder to locate the important parts. Conversely, if you remove too much necessary information, the supporting evidence will be insufficient. Before output, we confirm the balance between readability and explanatory detail.

Also, PDF file names are important in practical work. If a file name is abstract, such as "report" or "simulation", you may not be able to identify the project name or conditions later. Using a file name that includes the project name, date, variant name, and key conditions makes internal sharing and post-submission management easier. PDF reports are stored by the recipient once sent, so the file name should be considered part of the document quality.

Step 4: Save as a PDF and prepare for submission

After checking the numerical values and display settings, save it as a PDF and prepare it for submission. Create the report in PVSyst and save it using the PDF output or print function. The operation itself is not difficult, but in practice it is important to verify the file after saving. Once you have created the PDF, be sure to open the file and check for missing pages, garbled text, missing numbers, or corrupted figures.

After saving the PDF, first check the front page. Verify that the project name, location, variant name, and creation date are as intended. If there is an error here, it will undermine confidence in the document even if the numerical values in the main text are correct. In particular, be careful when creating a new project by reusing files from past projects, as names and locations may remain outdated.

Next, check the results page. Verify that the annual generation, PR, monthly values, and loss diagram are displayed as expected. If figures or tables are cut off during PDF conversion, or become hard to read midway through a page, it will be difficult for the recipient to review. Even if everything looks fine on screen, when viewed as a PDF you may find the text is too small, the figures are cramped, or the page breaks are poorly placed. Always perform a visual check after saving.

When necessary, explanatory materials separate from the PDF report may be prepared. Because PVSyst PDF contains a lot of technical information, some readers may need time to understand its contents. When explaining to internal and external stakeholders, it is easier to convey the message if you attach a short explanatory text summarizing the key points while using the PDF report itself as the supporting document. However, even when creating separate materials, it is a prerequisite that the figures in the PDF report and the figures in the explanatory text match.

When preparing files for submission, file version management is also important. If PDFs from before and after revisions are mixed together, it becomes unclear which is the latest version. Including the date and version number in the file name and clearly marking the final version can prevent sending the wrong file. This is especially important when multiple people are working on a project, since multiple PDFs with the same project name tend to accumulate, so establishing saving rules improves efficiency.

Once you have confirmed that there are no problems with the PDF content, review it once more before submission to ensure it matches the submission’s intended purpose. The supplementary information required will vary depending on whether it is for comparison, final design, internal review, or client presentation. PVSyst’s PDF report is useful as a detailed technical document, but being mindful of whether it answers what the reader wants to know will make it a more practical document for use in practice.

Common mistakes when creating PDF reports and how to prevent them

One common mistake when creating PVSyst PDF reports is outputting old simulation results. During design studies, you often replace weather data, change the number of panels, adjust PCS capacity, or revise loss rates multiple times. In that process, you can accidentally output a variant that is not the final configuration. To prevent this, clearly designate the case name to be used as the final version and make it a habit to check the conditions and results before outputting.

Another common problem is that the names used within reports are hard to understand. A name that only you recognize in PVSyst may not convey meaning when shared as a PDF with others. Labels such as "Plan 1", "Revised", or "Latest" lose their meaning over time. Using names that clearly indicate the project name, capacity, whether shading is considered, and the main conditions can prevent PDF mix-ups.

Insufficient explanation of meteorological data is also a common problem. Simulation results for solar power generation depend heavily on the meteorological data used. If the location is distant from the candidate site, or if data from a representative location are being used, you need to be able to explain that assumption. Determine whether the site information displayed in the PDF report is sufficient, or whether supplementary explanation is necessary.

Not verifying loss settings can also lead to failures. If you create a PDF without sufficiently checking the loss settings, the PR may look unnatural and the loss diagram may seem off. In particular, the effects of shading, soiling, wiring losses, and temperature losses vary depending on site conditions and design policy. Even if you use the initial settings as-is, confirm that you can explain why those values are acceptable.

Insufficient checking after PDF output is also a point to be careful about. If you send the exported PDF without opening it, you may not notice page layout issues or display defects. Materials converted to PDF are judged by the reader in that state. After saving, check the beginning, main results, monthly tables, loss charts, and the final page to ensure the document is readable.

Also, there are failures in comparison reports where conditions are not aligned. When comparing multiple proposals, if, for example, only one has different weather data, only one considers shading, or only one has different loss conditions, you cannot determine the reasons for differences in power generation. When creating a PDF for comparison, make the conditions other than the elements you want to compare as consistent as possible. If there are differences in conditions, it is important to clearly indicate which conditions differ.

Tips for Making PDF Reports Readable in Professional Practice

To make a PDF report easy to read in practical work, it is important to be mindful of the information the reader wants to know first. In many cases, the reader will first check which project the document pertains to, under what conditions the calculations were made, what the annual power generation is, the monthly trends, and what the main loss factors are. Therefore, when sharing a PDF report, it is helpful to be able to briefly guide readers on where in the text they should look.

PVSystのPDFレポートは技術情報が多いため、非技術者には難しく見えることがあります。だからこそ、レポートの読み方を説明できる担当者側の準備が重要です。たとえば、年間発電量は設備全体の見込み発電量であり、月別発電量は季節変動を見るためのもの、PRはシステム全体の効率を見るためのもの、損失図は発電量が減少する要因を段階的に示すものだと説明できると、読み手の理解が進みます。

File names and version control are also part of readability. If the recipient of a PDF can determine the project and conditions from the file name alone, it makes the file easier to find in emails and shared folders. In particular, when comparing multiple proposals for the same project, standardize how you name files. Including the date, project name, condition name, version number, and so on in a consistent order will make it less confusing when you look back later.

When using this for internal review, record any points of concern while looking at the PDF report, as this will help with revisions next time. For example, if you standardize the checkpoints to confirm things like the validity of meteorological data, the accuracy of shading settings, the basis for loss rates, the reasonableness of capacity ratios, and the monthly variations in power generation, the quality of reviews will be more consistent. Rather than reviewing based on the feeling of the moment each time, deciding in advance which items to check will reduce oversights.

For submitted reports, consistency between the conditions and the numerical values is more important than excessive decoration. While it is necessary to tidy up the appearance, the most important thing is that the reader can trace the basis for the numbers. The PVSyst PDF report is a technical document intended to show the rationale behind the power generation figures. Be mindful of readability, but take care not to omit too much of the necessary condition information.

Enhance the accuracy of site conditions to strengthen the persuasiveness of the report

PVSyst PDF reports are generated based on the input conditions entered into the software. Therefore, if the understanding of on-site conditions is unclear, no matter how carefully the PDF is prepared, discrepancies with the actual site will remain. In the design of photovoltaic power systems, the candidate site's location, topography, surrounding obstructions, existing structures, elevation differences, and construction scope all influence energy yield and design decisions. To increase the credibility of the PDF report, it is important to ascertain on-site data as accurately as possible before running the simulation.

Especially, the effects of terrain and obstructions are difficult to assess from desk-based conditions alone. If there are nearby buildings, trees, slopes, equipment, or changes in site shaping, they can affect shadowing and layout planning. If on-site location data or elevation information are insufficient, the conditions set in PVSyst will also be approximate, leaving uncertainty when explaining the results in the PDF report.

What becomes effective in that context is the approach of utilizing high-precision positional information and point cloud data acquired on site for design studies. For example, if you record with high accuracy the candidate site's boundaries, the positions of existing structures, ground undulations, the planned area for mounting frames, and the locations of surrounding obstructions, you can make the basis for simulation conditions clearer. Even if the power generation simulation itself is performed with PVSyst, improving the accuracy of the underlying site conditions will also enhance the explanatory power of the PDF report.

LRTK is a GNSS high-precision positioning device that can be attached to an iPhone. By obtaining high-precision location information on site and combining it with point clouds and photographic records, it can be used for candidate site surveys for solar power installations, understanding current conditions, layout planning, and pre- and post-construction verification. When creating PDF reports in PVSyst, accurately grasping the site’s location and terrain also makes it easier to explain the basis for the input conditions.

Learning how to use PVSyst is important in the practical work of power generation simulations. However, to produce highly accurate reports, it is essential not only to operate the software but also to acquire and organize on-site data. By combining the PDF report generated by PVSyst with accurate location information and records gathered on site, the link between desk studies and actual field conditions is strengthened, resulting in materials that are easier to present to stakeholders.

Summary: Verifying PDF reports before output determines their quality

Creating a PDF report in PVSyst is easier to understand if you think of the process as four steps: finalizing the simulation results, confirming the items to include in the report, checking the numerical values and display settings before output, and finally saving as a PDF and preparing it for submission. While the PDF output itself is not difficult if you only look at the操作, what matters in practice is whether the generated documents are ready to be used as-is for explanations.

In a PDF report, it is necessary to comprehensively check not only the annual power generation but also meteorological conditions, system configuration, monthly generation, PR, loss diagrams, and the effects of shading. Even if the figures are correct, the credibility of the submitted materials is reduced if condition names are unclear, comparison targets are mixed, outdated variants are output, or the rationale for loss settings cannot be explained.

PVSyst's PDF report is an important document for conveying the results of design studies to stakeholders. For that reason, it is essential to carefully organize the input conditions before creating the report, verify items during creation, and perform a thorough PDF check afterward. The outcomes of power generation simulations are determined by the cumulative effect of site conditions, design conditions, and loss conditions. Arranging the report so that readers can understand that progression is the foundation of producing PDF reports that are practical for use in the field.

Furthermore, to increase the credibility of the report, it is important not only to set parameters in PVSyst but also to accurately capture local positional and topographic information. By utilizing an iPhone-mounted high-precision GNSS positioning device such as LRTK, you can record a candidate site's current conditions, boundaries, elevations, and locations of structures with high precision, making them easier to organize as the basis for simulation conditions. By calculating power generation in PVSyst and accurately capturing on-site conditions with LRTK, you can bridge desk-based simulations and real-world site conditions, enabling the development of more persuasive solar power generation plans.