The output tab of your cases displays graphs of simulation data and provides output report and project plan downloads.

This page details the metrics and key functionality of the output tab.


All data on the output page is displayed for the percentile value you select at the top of the page. If you require average values across all simulation runs, you can either select the P50 value or download the output report and refer to the average calculations found there.

Metrics

Key metrics

High-level figures for your case. These provide an at-a-glance overview of your outputs.

Summary

  • TBA loss: The percentage of time assets spent inoperative. See the TBA section for more details.
  • PBA loss: The percentage of potential production lost. See the PBA section for more details.
  • Total actual production:
    • The total amount of energy produced during operation across the entire simulation period.
    • Calculation: Potential production - Lost production
    • Note: Potential production is calculated using the WTG power curve multiplied by the wind speed multiplied by the number of turbines. Therefore, the calculation occurs at the WTG level rather than at the wind farm level and does not account for any power loss between turbines and the substation.
  • Lost production: The total energy that was not produced due to inoperative asset instances but would have been produced if they had been operational. These is calculated across the entire simulation period.
  • Downtime: Total time all asset instances spent inoperative across the entire simulation period.
  • Gross capacity factor: Gross capacity factor: How much of the rated capacity you would use if you assume zero asset downtime.
    • Calculation: 
      • potential production [kWh] / SUM over assets(wtg rated capacity [kWh]*simulationDuration) 


        (AggregateOfRuns(TotalOfYears(ActualProduction)) / (1000 * TotalGrossCapacityFactor * simulationDuration)) 


        (AggregateOfRuns(TotalOfYears(ActualProduction)) / 1000) / {TotalGrossCapacityFactor}` 

  • Net capacity factor: How much of the rated capacity you used when accounting for downtime.
    • Calculation:
      • actual production [kWh] / SUM over assets(wtg rated capacity [kWh]*simulationDuration)

        SumOfCaseWtgConfigurations(NumberOfWtgInstances * RatedPowers * 8766)

Wind farms

PBA, PBA loss, TBA, and TBA loss broken down by wind farm. See the PBA and TBA section for further details.

Personnel utilization

The aggregated yearly personnel utilization per team. See the personnel utilization section for full details.

Logistics utilization

The aggregated yearly operation days and aggregated yearly utilization per logistic.

Aggregated yearly values are calculated by summing and dividing by all the operation days and available days throughout the entire simulation period, not from summing the yearly values and dividing by the number of years. 

See the logistics utilization section for full details.

Production-based availability

Production-based availability (PBA) measures the percentage of potential production that is produced in actuality. The calculation considers the energy made as a fraction of the amount that would ideally be expected based on actual wind speeds and site conditions.

PBA calculation: 

PBA [%] = [Actual production [MWh] / Potential production [MWh]] * 100 = [Energy actually produced [MWh] / Energy potentially expected [MWh]] * 100 

Key terms: 

  • Actual production: The amount of energy an asset produces when operational. It is the difference between potential production and lost production.
  • Potential production: The amount of energy an asset would produce if it were always operational (i.e., never failed or shut down). Calculated using the power curve of the asset and the wind speed at hub height.
  • Lost production: The energy that is not produced when an asset is non-operational but would be produced if it was operational.

Example for a single asset instance over one month:

  • Lost production: 85 MWh
  • Actual production: 4,165 MWh
  • Potential production = 4,165 MWh + 85 MWh = 4,250 MWh
  • PBA = 4,165 MWh / 4,250 MWh = 0.98 = 98%

PBA loss per root cause

Root causes display the underlying reason for production-based availability (PBA) losses on a wind farm.

See the PBA root causes section of the output report page for a detailed explanation.

Time-based availability

The time-based availability (TBA) is a measurement of an asset's availability or the fraction of time the asset is operational. It is calculated as the ratio of hours available as a fraction of the full period and is defined as:

TBA [%] = [(Possible uptime [h] - Downtime [h]) / Possible uptime [h]] * 100= [Time available [h] / Total time in consideration [h]] * 100 

Key terms:

  • Downtime: Measured in hours per asset. Working being carried out on the asset and critical component failures are examples of downtime among other causes.
  • Possible uptime: The total time being considered regardless of asset availability. It is the number of hours from the start until the end of the simulation multiplied by the number of assets (simulated years * 8,760[h] * the number of assets).

An example of one asset instance over one year:

  • Possible uptime (hours in the year): 8,760
  • Downtime: 215 hours
    • Weather: 90
    • Errors and repairs: 85
    • Scheduled maintenance: 40
  • Uptime: 8,545 hours
  • Time-based availability loss: 215 h / 8,760 h = 0.0245 = 2.45 %
  • Time-based availability: 8,545 h / 8,760 h = 0.9755 = 97.55 %

Scheduled maintenance completion per year

Work order completion rate on scheduled maintenance tasks per asset.

Personnel time spent

How efficiently personnel time is spent during work hours. Broken down by personnel group, this output shows the percentage of time spent working against time spent travelling, being picked up, and being dropped off.

  • Work ongoing
  • Drop off at turbine
  • Pick up at turbine
  • Travelling on vessel

Personnel utilization

Number of days personnel were utilized per days available in a given month or year.

Aggregated values are derived by adding together the values from all the relevant days in the simulation and dividing by the number of days the personnel were available.

Example

For a given year of the simulation, we have these values:

  • Personnel in a group: 15
  • Personnel used per day: 5
  • Number of possible workdays: 300
  • Number of non-workdays with weather that would’ve allowed work: 12

Personnel utilization is derived with the following calculations:

  • 5*300 = 1500 working personnel
  • 15*(300+12) = 4680 total personnel available
  • 1500/4680 = 0.3205 = 32.05 percent personnel utilization in the given year of the simulation

Logistic transfer utilization

The number of team transfers (drop off or pickup) conducted by a logistic on each asset.

Logistics utilization: operation days

The number of days the logistic was in operation.

A day is counted when the logistic operates in it all. For example, if a logistic operates from 08:00 Monday to 00:01 Tuesday, that is 2 operational days.

Logistics utilization

The percentage of available days that the logistic was in operation.

An available day is any day where the logistic is available for operations.

Calculation: Operation days (total) / Available days.

Weather downtime per logistics unit

The percentage of time a logistic was available for operations but spent idle due to bad weather.

Transfer logistics (CTVs, SOVs, DCs, and helicopters) register weather downtime on all applicable days they are available for work, regardless of whether they are scheduled to work or not.

Large logistics (HLVs, CIVs, towing vessels, cranes, AHVs, feeders, and CoTVs), i.e., those with processes, only register weather downtime when a weather restriction prevents the logistic from performing a step in a process.

Calculation: Bad weather hours / Available hours

Weather downtime causes

Contribution to vessel downtime by weather type as a percentage of the total weather downtime. 

Use these calculations to establish where vessels with greater environmental tolerance can improve project efficiency.

Weather types include the following:

  • Wind speed
  • Significant wave height
  • Swell wave height
  • Wave period
  • Zero up crossing period
  • Limited by daylight
  • Minimum tide
  • Minimum visibility
  • Current speed
  • Limited by lightning
  • Time restrictions
Weather limitations apply to vessel process steps. You won’t see weather downtime causes for CTVs, SOVs, or helicopters, which do not feature processes.

How weather causes are calculated

The percentage value you see for each weather type is the vessel downtime in this period caused by the relevant process, step, and weather type divided by the total weather downtime for the vessel throughout the entire simulation.

A period can be any of the following:

  • Month
  • Year
  • Aggregated month
  • Full simulation

For example, if there's a 20-percent occurrence of wind speed exceeding the weather limitation during step 1 of process A on vessel X, this contributes to the overall weather-related downtime for that vessel over the entire 10-year simulation period if the simulation years = 10.

If the criteria for multiple weather types are exceeded, downtime is registered for all applicable causes. This is why the total weather cause percentages might exceed 100 percent. In this case, weather types will have overlapped at some points, e.g., there were periods where windspeed and minimum visibility both exceeded the criteria threshold for operations.

Time restrictions

Any time restrictions you have created on your case are counted as a weather type in the weather causes output report tab. If your case includes multiple time restrictions, they are grouped together in the report as a single weather type (TIME_RESTRICTION).

Reports and logs

From the output page, you can download the following reports: 

  • Output report (XLSX)

There are also several raw logs available for download:

  • Milestones log
  • Process cycles log
  • Transfer work order log
  • Visualization log
  • Work order status change timestamp

Logs will always be generated for the first run of the simulation.

Log filenames follow this structure: projectID_caseID_fileName_SimulationRunStartTime_RunID.csv (e.g., 232_3090_SomeLog_2024-04-15-0653_d29f9118-664a-45b3-abcf-a983711336e3-1.csv).

If a log is not available, the tooltip will tell you if your need to rerun your simulations or whether your case configuration doesn't allow for this log output.