The output report contains a breakdown of your simulation’s results. Data in the output report is aggregated for every month and year, and the following statistical values are displayed for each period:  

  • Average 
  • Percentiles (P10 to P90) 
  • Minimum 
  • Maximum 
  • Standard Deviation 
  • Confidence (minimum) 
  • Confidence (maximum) 

The O&M output report contains these sections: 

  • Summary 
  • Costs 
  • Logistics utilization 
  • Logistics transfer utilization 
  • Personnel utilization 
  • Personnel time spent 
  • Weather downtime 
  • Weather causes 
  • Scheduled completion 
  • Production-based availability 
  • Time-based availability 
  • Case logistics 

Summary 

General information about your case. 

TitleDescription
Project nameThe project folder name in which the case is located.
Case nameCase name.
Case IDA unique case ID. Found in the URL when accessing the case through Design web app.
Case createdDate and time when the case was first created.
Case started yearSimulation start year, set in the Simulate tab.
Case simulated yearsHow many years were simulated in the runs.
Simulation runsNumber of runs set in the Simulate tab.
Exported byUser who exported the report.
BasesNumber of bases in the case.
AssetsNumber of assets in the case. 
LogisticsNumber of logistics in the case.
Project size

Power output of the project. 

Calculation: Number of turbines * Rated power

Other tabs

TitleDescription
CostsAny costs associated with the case broken down by base, asset, logistic, and personnel.
Logistics utilization

Includes the following: 

  • Number of days a logistic was utilized per year and month. 
  • Percentage of available days the logistic was utilized. 
  • Number of flying hours per year and month (if there is a helicopter included in the case) 
Logistics transfer utilizationNumber of transfers (drop offs and pickups) conducted by each vessel on each asset.
Personnel utilizationNumber of days personnel were utilized per days available in a given month/year.
Personnel time spentHow efficiently personnel time is spent during work hours. Broken down by group, this output shows time spent working against time spent travelling, being picked up, dropped off, and sitting idle in bad weather.
Weather downtimeThe downtime percentage per logistic.
Weather causesContribution to vessel downtime by weather type as a percentage of the total weather downtime. See the weather causes section below for full details.
Scheduled completion

Completion details for work orders. Contains the following: 

  • Completed work orders (total number of work orders) 
  • Work hour completion rate (percentage) 
  • Work order completion rate (percentage) 
  • Unfinished work orders (total number of work orders) 
  • Work hours on completed work orders (total hours) 
  • Work hours on unfinished work orders (total hours) 
Production-based availabilityPBA per month and year.
Time-based availabilityTBA per month and year. 
PBA root causesThe underlying reason for (PBA) losses on a wind farm. See the PBA root causes section for dull details.
Case logisticsInformation on the logistics added to the case, including activity durations and processes.

Weather causes

Weather causes lets you see what types of weather contributed to vessel downtime 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 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).

PBA root causes

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

To establish a root cause for PBA loss, Shoreline first establishes which work order is responsible for the loss, then whether work is being carried out on the work order, and, if not, the reason why work is not being carried out. 

This process occurs in real time, so root causes reflect minute-to-minute changes in the simulation. 

Work order hierarchy 

Multiple work orders can potentially be responsible for PBA loss. Some examples: 

  • Multiple work orders carried out at the same time. 
  • A critical failure during scheduled work. 
  • An OSS suffering downtime at the same time as a WTG. 

Shoreline determines which work order is responsible for PBA loss using this prioritization: 

  1. Highest impact on power production. 
  2. WTG power loss over any OSS impact. 
  3. Work order with work currently ongoing over those queued. 
  4. Critical before non-critical work orders. 
  5. The downtime period that started first.

Root cause hierarchy 

Once the work order responsible for PBA loss is established, Shoreline checks the following: 

  • Is working being carried out on the work order? 
    • If yes, ongoing work is registered as the root cause. 
    • If not, Shoreline looks for why work is not being carried out on the work order. 

Root cause hierarchy (reason work is not being carried out on a work order): 

  1. No personnel available in calendar availability. 
    • E.g., Personnel are available March–June, but the work order is in February. 
  2. No logistic available in calendar availability. 
  3. No personnel available in the work shift. 
    • E.g., Personnel are available 07:00–19:00 but the work order was created at 20:30. 
  4. No logistic available in the work shift. 
  5. First scheduling: Time between work order creation and the first scheduling attempt. 
  6. Lead time: Time between work order creation and lead time expiry, when scheduling s first attempted. 
  7. All possible logistics are available but in lead time. 
  8. One of the required logistics is en route to carry out the work order. 
  9. Weather criteria exceeded on the work order. 
  10. Weather criteria exceeded on all available logistics. 
  11. One logistic required for the work order is in lead time. 
  12. Weather criteria exceeded on one of the logistics required for the work order. 

Root cause naming conventions

Root causes in the chart and output report will have names such as PBA Major lead time - No available HLV. The naming convention follows this system: 

  • Internal or external
    • Internal: 
      • PBA loss resulting from a problem with the asset itself. 
      • Internal is not prefixed to the root cause name. 
    • External: PBA loss caused by something external to the asset, e.g., foundations or OSS. 
      • External is prefixed to the root cause name. 
  • Category 
    • Major 
      • A corrective maintenance task requiring an HLV. 
    • Minor 
      • A corrective maintenance task that requires personnel and uses a CTV, SOV, helicopter, or daughter craft. 
    • Floating: A towing task. 
    • Scheduled service work: A scheduled maintenance task. 
  • Type 
    • Weather delay
      • Work order not scheduled due to weather criteria being exceeded. 
    • Lead time 
      • Major corrective work order not scheduled for any reason other than weather. 
    • Response time 
      • Minor corrective work order not scheduled for any reason other than weather. 
    • Work 
      • Work order in progress. 
    • Towing time 
      • Asset is in the process of being towed to port or back to the wind farm. 
      • Only for floating assets. 
  • Subcause 
    • Applied to any Major root cause with the Lead time type and any Minor root cause with the Response time type. 
    • For major root causes: 
      • Waiting to be scheduled for support vessel  
      • Waiting to be scheduled for HLV  
      • No available support vessel  
      • No available HLV  
      • Other 
    • For minor root causes: 
      • No available vessel  
      • No available personnel  
      • No drop-off and pickup combination  
      • Waiting to be scheduled

Root causes

Root causeDescription
Lost production (PBA root causes)Total lost production (kWh).
Schedule service work WTG

Scheduled maintenance work is being conducted.

Only counts lost production between a team starting and finishing work and does not include waiting for pick-up. 

Major lead time

Time between HLV work order creation and the start of work or until it's necessary to wait for a weather window. Includes: 

  • HLV lead time. 
  • HLV mobilization time. 
  • HLV transit time. 
  • All time related to the support CTV works that do not overlap with the HLV task. 

It also represents the total for the following sub root causes: 

  • Waiting to be scheduled for the support vessel 
  • Waiting to be scheduled for HLV 
  • No available support vessel 
  • No available HLV 
Major lead time - Waiting to be scheduled for the support vessel

Work stopped while waiting for the next CTV scheduling.

This occurs when the CTV needs to be back at port before a work shift ends or to avoid bad weather.

Major lead time - Waiting to be scheduled for HLVWork stopped while waiting for the next HLV scheduling
Major lead time - No available support vesselNo support logistic available due to either calendar or shift time availability.
Major lead time - No available HLVNo HLV logistic available due to either calendar or shift time availability.
Major weather delayWaiting for weather windows to perform inspection, preparation, replacement and finalization work either with the support CTV or the HLV.
Major work WTGMajor corrective maintenance in progress.
Minor work WTGMinor corrective maintenance work in progress. Does not include the time waiting for pickup.
Minor weather delayWaiting for a weather window to conduct minor corrective maintenance.
Minor response time

Time between minor corrective maintenance work order creation and the start of work or until it's necessary to wait for a weather window. Includes: 

  • Transfer time. 
  • Waiting for transportation. 
  • Waiting for technicians.

It also represents the total for the following sub root causes: 

  • No room on asset 
  • No available vessel 
  • No available personnel 
  • Emergency response limit 
  • No dropoff and pickup combination 
  • Waiting to be scheduled
Minor response time - No room on asset
No team of technicians can perform work on the WTG as the asset is at capacity.
Minor response time - No available vessel
No logistic available due to either calendar or shift time availability.
Minor response time - No available personnel
No personnel available due to either calendar or shift time availability.
Minor response time - No dropoff and pickup combinationUnable to schedule the drop-offs or pickups with the combination of technicians and logistics available, the current weather windows, and other work orders.
Minor response time - Waiting to be scheduled
Time between work order creation and lead time expiration or the first scheduling attempt.
Floating work WTG
Repair work at port with cranes or the disconnection or hook-up durations offshore for a floating component failure.
Floating weather delay
Waiting for a weather window to perform operations on a floating asset at port or for towing operations.
Floating response time
Time between work order creation for a floating component failure and the start of the work.
Floating towing time
Towing in progress.
Root causes total
Sum of lost production for all root causes.
OSS at max capacity
OSS exceeded its power capacity.
Cable at max capacity
Cable exceeded its power capacity.
Other asset in string disconnected
An asset instance lost connection to shore as another asset instance in the cable string was disconnected.
PBATotal PBA.