FOR GUIDANCE ON THE CONSTRUCTION 3 OUTPUT REPORT, PLEASE SEE HERE.
After running a successful simulation, you can download the following reports, and read more about each report below:
- Output report
- Contains the aggregation of P-values (How we calculate percentiles article)
- Master schedule and Company report - general information
- Master schedule in MS Project
- Master schedule in Primavera P6
- Pxx Excel output data - Company report
- Outputs one of the simulation runs which has the closest final installation date of an asset as the selected P-value
Difference between Output report vs Master schedule and Company report:
Aggregated data (Output report and the output dashboard) for P50 says the final installation date of an asset was on the 15.05.2022. The Company report for P50 would then download the simulation which had the closes end-date to 15.05.2022, which could be the same date, 12.05.2022 or even 25.05.2022.
Output report
The percentile calculation method for probability-weighted statistics in the ConDesign output sheet is changed from a normal distribution to an interpolation method.
| Tab | Description |
|---|---|
| Summary | It reflects p-value aggregation of all simulation runs as they are for installation time and average cycle time |
| Asset Times | It reflects p-value aggregation of all simulation runs as they are for installation time and average cycle time of the different assets |
| Asset Cycle | It reflects p-value aggregation of all simulation runs as they are for various events. Events include loadout, transit to wind farm, jacking up, installation, jacking down, transit to next location, and transit to port |
| Vessel Cycle | It reflects p-value aggregation of all simulation runs as they are for installation time and average cycle time |
| Asset Downtime Causes | It reflects aggregated weather downtime per p-value as it relates to specific weather downtime. Wind speed, wave height, and tide are the root causes that are represented by the aggregated p-value |
| Downtime | It reflects the aggregation of weather downtime period that is represented as a duration in hours per each p-value per month. aggregation is represented per vessel |
| Utilization | It reflects aggregated p-value of utilization as represented per vessel per month |
| Technician utilization | Reflects the aggregated p-value of utilization of technicians per month |
| Waiting on weather in workshift | Reflects the aggregated p-value downtimes per vessel while the vessel was working |
| Waiting on weather | Reflects the aggregated p-value downtimes per vessel in- and out-side of the work shift |
| Transit times | Reflects the transit times of each vessel by hours per month |
| Master timeline | The Master timeline shows the start- and end-times for all cycles in the different p-values If the simulation has a complex setup, the Master timeline might be blank or not show all the information you expect - this is because the order of each asset changes in the different runs, causing the master timeline to be split up, and thus, we are referring you to the Pxx Excel output data. |
| Installed Assets | It reflects aggregated p-value represented for installed assets |
| Completed Assets | It reflects aggregated p-value represented for completed assets |
| Commissioned Assets | It reflects aggregated p-value represented for commissioned assets |
Master schedule and Company report - General information
The outputs in the project Master schedule and Compnay output does not have the same outputs as the Output reports Master timeline, as they are processed differently.
Imagine you have a bunch of runs. For the MS Project and Primavera Outputs (as well as the Single Run Output Report), these runs are organized by Simulation Length/Completion Time. When it looks for a p-value, it looks at the run as a whole. If you want P10, it finds the run that corresponds to that p-value (the shortest, usually), and then we use that run’s data for that p-value. This method of selecting the run as a whole relies on the assumption that runs with a shorter completion times have less delays, and longer completion times have more delays, with the most likely scenarios happening in the middle.
This is for the most part true, but as we’ve seen, there are instances where individual tasks or processes do not follow that trend. The master timeline was created to help provide a more fine-grain look at how the processes and tasks themselves change across all runs. That processes and tasks data is fed into p-value probability weighting calculations to get the outputs you see in the master timeline.
The data in the master timeline is not direct output from those runs.
Below is an example:
You can see that for the P50 value, that output did not exist in the Run Data, but was calculated as the mid-point between the entire distribution of the dataset. Despite not have a “3” in the Run Data, there exists a “3” in the outputs.
Note: that the Master Timeline also has the assumption that all tasks and processes are done in the same way each run, and we’ve seen in the past that is not always the case.
Master schedule in MS Project
You can download the Master schedule timeline and import these files to MS Project.
Please read the General information about the Master schedules for more information.
Master schedule in Primavera P6
You can download the Master schedule timeline and import these files to Primavera P6.
When running imports, you need to go into Admin - Admin preferences - Time Periods, and change these to 24/7 all year to make sure the import is correct.
Please read the General information about the Master schedules for more information.
Pxx Excel output data
When changing the P-value on the dashboard, you can notice that the P-value also changes for the file you can download under Company reports - this file is called " [P-value] Excel output data". When downloading this file, please note that you are viewing a single simulation, and not the aggregated results for all simulations in the case; please use the "Output report" for this.
| Tab | Description |
|---|---|
| Installation timeline | Displays the operations done in a linear timeline with start- and end-dates, and with the duration for each operation displayed in hours. |
| Installed turbines | Displays all asset installations with the date and time the asset was installed. |
| Economics table | Displays the costs related to the single run, based on the inputs you have done in the case. |
| Vessel utilisation | The vessel utilisation shows the percentage of days the vessel has been sailing per month. |
| WoW per month | Displays the total number of hours (and %) waiting on weather per vessel. |
| WoW per month (avg all runs) | Displays the total number of hours waiting on weather per month per vessel, aggregate average across all runs. |
| WoW per month (monthly P-value) | Displays the average number of hours waiting on weather per month per vessel, aggregate across all runs. |
| WoW per year | Displays how many hours a vessel had to wait for good weather to continue operations per year. |
| WoW summary | NOTE: this sheet is deprecated, and will be removed in the future. No data is visible in this sheet. |
| Completed assets | Displays the date and time when an asset was completed. |
| Commissioned assets | Displays the date and time when an asset was commissioned. |
| Vessel timeline | Displays the date and time when each vessel does a single operation in a linear timeline. |