We are pleased to announce the launch of the Enhanced Feeder Modeling feature in our Design Construction software. This update introduces the ability for feeders to remain offshore for extended periods, delivering multiple assets sequentially to installation vessels with limited space. The new capabilities aim to enhance operational planning, improve installation workflow, and optimize feeder/barge usage in offshore wind projects.

Key Benefits:

1. Feeders now have the ability to carry multiple components simultaneously and deliver them one at a time as installation vessel deck space becomes available in the case.
2. Feeders can stay offshore longer, reducing the need for frequent returns to port, which lowers fuel costs and increases efficiency in the simulation model.

Technical Overview:

• We’ve added a "Maximum capacity per transfer to HLV" field to define how many components a feeder can deliver in one trip. If more tasks remain, the feeder will automatically move to the next location and await further transfers.
  
  
  
  
  
• A new "Transit to Next Asset" process has been introduced to handle feeder movement between locations. By default, the speed for this step is set to 0, following standard configuration rules.
  
  
  
  

User Action for Existing Cases:

Key Features - Advanced options

1. Model various routes tailored to different logistic types, such as vessels and helicopters.
2. Choose the destination of each route from the base.
3.  Define the logistic load conditions for each route.

For more details: Refer to this guide
This feature is available for all users of Design Con, O&M.

Practical application

• 10 Knot Speed Restriction: Model the 10-knot speed restriction for the first 30 nautical miles outside the US coast, meeting US developers' requirements.
• Helicopter Routing: Differentiate helicopter routes from sailing routes, addressing longstanding industry demands.
• Heavy Lift Vessels (HLVs): Plan different routes for HLVs entering and exiting harbors to minimize delays.
• Onshore Transportation: Enhance modeling for specialized trucks, such as those transporting nacelles and blades.
• Floating Wind: Distinguish between towing routes for semisub tows and regular sailing routes.
• Long Voyages: Plan distinct routes to ports and fabrication yards, considering cost-effective options like avoiding the Suez Canal.

 Start exploring the advanced modeling capabilities with Shoreline Design!

• Shoresim, the simulation engine, will allow a logistics charter period to cover multiple work orders without needing a lead time reset after each trip. Once a vessel is chartered and available, it remains ready for subsequent tasks until all assigned work orders are completed.
• Previously, each roundtrip triggered a new lead time before the vessel could begin the next task. With this implementation, lead time is only applied once at the start of the charter period, enabling continuous, uninterrupted operations.

• Reduced Operational Downtime: By eliminating unnecessary lead time resets, vessels can now operate continuously, minimizing delays between tasks.

• Lead time labels have been updated to include a prefix based on the application input settings context. They will now be prefixed with either "Logistics" or "Task" to provide clearer context and improve usability.

• Tooltips: Users can now find tooltips explaining spot chartered and Dedicated tasks inputs labels

Slight changes can be expected in PBA loss per root cause categorization, Logistics routing to wind farm

• The New Output Dashboard has been set as the default main dashboard for all users.

PBA loss per root cause chart is now available in the new output dashboard with improved user experience and design.

The new "Type" column is introduced across all output report sheets with the following values:

• Non-aggregated Monthly
• Aggregated Monthly
• Yearly
• Aggregated Yearly 

This will help users filter and visualize data more easily and quickly, providing a better user experience. 

• When a user selects a year range for ERA 5 weather data the simulation will consider weather from the selected period only.
• When a user clicks download file, then the file will only contain the data from the selected time range

• All dedicated Crew Transfer Vessels (CTVs) accompanying the Heavy Lift Vessel (MCR HLV) will now follow the designated CTV logistics route as set in the route planner feature.
• Previously, sometimes logistics entered the wind farm from the south side. With this release, all logistics will directly approach the wind turbine for operations and maintenance.

• The internal function related to the calculation of PBA (Production-Based Availability) loss root causes has been updated. However, there will be no changes to the calculation results.
• Prior to this release, there were instances where, apart from the work shift, the simulation categorized loss per root cause as part of the full-day in-route logistics instead of weather delays. This primarily occurred when moving from inspection to preparation stages.
• After this release, these losses will now be correctly categorized under major weather delays, rather than major response time delays.

Detailed steps for Wind farm reliability modeling is available here

1. Duration of Campaign
2. Campaign end date

1. PBA total for each wind farm
2. TBA total for each wind farm
   
   
3. Logistics utilization total for each vessel
   
   
4. Personnel utilization total for each personnel group
   
5. Total Production (MW/GW)
6. TBA loss
7. 100% - TBA for full simulation (all years and all wind farms)
8. PBA loss
9. 100% - PBA for full simulation (all years and all wind farms)
10. Lost production for full simulation (all years and all wind farms)
11. Downtime hours for full simulation (all years and all wind farms)
12. Gross capacity factor
13. Net capacity factor

Added the ability to download simulation logs on the new output page.

Log Naming and Structure:

• Logistics Log: Renamed as "Transfer task log" for Con 3 and "Transfer work order log" for O&M.
• Raw Log: Renamed as "Task status change timestamp log" for Con 3 and "Work order status change timestamp log" for O&M.
• Visualization Log: The "Visualization log" remains for both Con 3 and O&M.
• 
  
  
• File Naming  Format: projectID_caseID_fileName_SimulationRunStartTime_RunID.csv (e.g., 232_3090_SomeLog_2024-04-15-0653_d29f9118-664a-45b3-abcf-a983711336e3-1.csv).
  
  

Run Selection:

1. O&M: Logs will always be generated for the first run of the simulation.
2. Con 3: Logs will correspond to the P-run for the selected P-value.

Process Cycle Download on S-Curve: Made available as a separate download button, similar to other reports.

Compressed CSV Logs: Due to large file sizes, the system now compresses CSV logs into zip format to optimize storage and performance.

 Updated all new graphs to consistently use the actual year instead of a mix between the simulation year and the actual year, aligning with the PBA sheet in the OM output report.

Tooltip Messages for Missing Logs: Tooltips will inform users when an output log file is not generated in the simulation engine, with guidance on configuring the case to generate the file.

Key Metrics Section Redesign: The "Summary" section has been renamed "Key metrics" and made collapsible. Each metric section now has its name and value and is collapsible for easier access to key data.

Logistic Types Label: The label "Logistic types" will now display "None" when no logistic types are selected instead of showing no data.

Enhanced Drop-down Display: Collapsed drop-downs under advanced options will now expand in width or hold more lines to show all selected logistics types and wind farm selections instead of using "…".

Loading Indicator during data processing: Implemented a loading indicator for multiple routes to provide users with visual feedback that data is being fetched

Daughter Craft Base Location 

Feature: Automatically use the SOV base location as the default daughter craft base location to save time and reduce confusion. This change makes the process more efficient and user-friendly.

Additional Check:  a case checker is implemented to verify that all logistic instances have a valid port.

Simulations failed when a Daughter Craft with unlimited availability had an SOV with limited availability specified as the mother vessel. This issue has been resolved, and after the release, simulations will not fail for such scenarios.

Fixed an issue where simulations froze if a personnel group was not removed from a deleted SOV. The system now checks if personnel are attached to a valid home base or mother vessel.

1. Model multiple routes suitable for each logistic type
2. Specify wait times and speed limitation criteria for each waypoint on each route
3. Choose the destination of each route from the base
4. Set the Logistic load condition

Develop scripts to automatically create and run sensitivity cases, drastically reducing the time and effort associated with manual workflows.

To enhance efficiency, users can schedule batch processing within your scripts to execute case simulations and run multiple sensitivity cases concurrently. 

Easily extract output files from sensitivity analyses through the API.

Directly pipe output data into BI tools for enhanced visualization and reporting.

We've finalized the Case Inputs feature by adding Bases, Assets, Personnel, and the strategy output. Now, users can access all parameters inputted in their case building for comparison with outputs.

Our O&M Output report undergoes a significant makeover, providing a renewed format for easy processing. Users will find the data more accessible for post-processing and reporting via third-party tools.

Improvements in the new report 

1. Removal of empty columns/rows

2. Uniform structure

3. Compatible data layout

4. Data accessibility

In the new beta output dashboard, only the newly formatted O&M output report is available.

Both existing and new O&M output reports are available in the existing output dashboard.

1. Weather-downtime-causes report
2. Logistics transfer utilization: count – Asset drop off /pick up 
3. Personnel time spent outputs
4. Case inputs – logistics and more

 1) Operation days: Sailing days / Flying days graph

2) Personnel time spent

Importing Scheduled or Corrective maintenance tasks from CSV to an asset on an O&M case should persist in new logistics type Daughter craft selection.

A new dashboard view displays the average task duration for each task group, offering quick insights into project timelines

We've finalized the Case Inputs feature by adding the strategy output. Now, users can access all parameters inputted in their case building for comparison with outputs.

We've introduced a new chart displaying the top ten major root causes affecting vessels and their processes during simulations. This helps users understand which weather criteria impact specific process steps, aiding in operational planning and identifying potential bottlenecks.
 

• We've increased the size of plotted dots on task end-time graphs for better visibility. 
• We've also standardized color schemes across charts for a more intuitive user experience.

Recognizing the critical role of daughter crafts in offshore wind farm operations and maintenance, we understand their importance for high-speed and efficient transfers between the main SOV and the turbines. Daughter crafts often operate continuously, shuttling personnel and equipment without returning to port, maximizing wind farm availability and efficiency. We believe this addition will enable our users to model industry-accurate scenarios and benefit significantly from our platform effectively.

The asset access limitations settings can now be modeled for Crew transfer vessels to improve case accuracy.

• Wind speed access limit values in m/s (similar to SOV)

• Wind speed limitation reference height in m (similar to SOV)

•The weather causes report explains how various weather conditions affect the total downtime of a vessel during a simulation period or campaign duration in the case.

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

1. S-Curve
2. Inventory Management
3. Vessel Utilization
4. Personnel Utilization
5. Weather downtime per logistics unit

1. Output report
2. Project Plan

1. Time-based availability (TBA)
2. Production-based availability (PBA)
3. Vessel Utilization
4. Personnel Utilization
5. Scheduled maintenance completion per year
6. Weather downtime per logistics unit

1. Output report

General technical improvements

Construction 3 & O&M 

We have added the ability to set speed limits (Max speed) at bases and the wait times (‘Time delay’) at each waypoint. This is an excellent addition for those wishing to model wait times at locks and other local restrictions on speed and movement, and it improves the overall accuracy of process cycle completion times within the product.

We have increased Shoreline Design's performance! Previously, we have been continually validating cases as users build them; now, we only validate them when the user clicks the ‘Check Case’ button and selects ’ Run Simulation.’ 

You may also have observed that we have improved the hints and warnings given to users so that they don’t always appear and only notify when you actively select the ‘Check Case’ button. We have intended to make these more helpful so that you are prompted when a change may cause the case to fail. For example, a standard user error is not to change other inputs when the loadout or load-off base has been changed. Now, users will be warned of how this change will impact the rest of their case.

1. Tasks will now be completed if the Inspection, Preparation, Replacement, and Finalisation fields are empty or have a default value of 0. Note that these fields are only shown under corrective maintenance if the vessel is a HLV. 
2. Scheduled Maintenance recurrence should be based on the number of operational years.

1. In cases involving feeder vessels for installation tasks, there was a minor bug causing them to go unreported in the process cycle log. We have successfully addressed this issue in the latest update, ensuring that feeder vessels' processes/steps are now accurately reflected in the log.
2. Fixed the bug around cable installation vessel (CIV) capacity. The project timeline now accurately reflects CIV capacity

We have fixed a minor bug around vessel selection not replicated on copied case.

Design Construction: Inventory Management feature release

• Inventory Management

Optimisation

1)We have now added more Statistical selector Percentile values such as Min, Max, 25, 50, 75 with the existing ones P10, P20, P30, P40, P50, P60, P70, P80, P90 are available in the project plan report the output report, Statistical p-Selector in the output dashboard.

2) Users can now validate their cases using Check Case button. This triggers case checkers run on demand and notify all the errors and warnings under Notifications.

3) We've integrated a permanent link within the Design application, allowing users to conveniently access release notes whenever they prefer.

1. We have removed MS Project and Primavera format Milestones and Process cycle Log from S-Curve download section.

1. The users can export the assets without any error messages in O&M
2. The users can upload a corrective maintenance task without any errors in O&M
3. The user can save changes by clicking the newly added Save button at the bottom section of the Scheduled Maintenance task page in O&M.

Design O&M
In a wind farm with Operations start year X+2 (X being the simulation start year), we have had a bug where failure rates were not started X+2 but X. This has been fixed in this release.

Addressing Location Mismatches between Personnel and Vessels (CTVs and Helicopters Without Mother Vessels)

In our previous tool version, a discrepancy between personnel and vessel locations allowed the simulation to proceed, marking tasks as completed inaccurately. This occurred ONLY with CTVs and helicopters lacking a mother vessel. We've rectified this problem by implementing a fix, ensuring tasks progress only when the site/location matches. The simulation now correctly fails when there is a mismatch.

1. When multiple cranes work on the same assembly tasks, the simulation will run successfully without failing.
2. We have also improved our scheduling algorithm to handle the interaction between the daylight restriction of the helicopter and the personnel work shift.
3. Users can delete projects without any issues

Design O&M can now have major Vessels(with Processes) for Offshore Substation Corrective maintenance Task.
Available major vessels : Heavy Lift Vessel ( Jack-up vessel) , Towing Vessel

Date and Time Restrictions

1. You can now bulk select and apply date and time restrictions in multiple process' steps by using the Bulk Manage Limitation option on the three-dot menu.
   
   
2. If the user did not save the rule by clicking apply, a warning message will notify the user that the rule is not saved

How to use: Date and Time Restrictions document

Project Plan Report

- Managing wind farm simulation projects is now simpler and more insightful with the Project Plan Report.

- Get a comprehensive view of your entire project timeline in one report.

- Tasks are organized hierarchically and can be expanded or collapsed as needed using software like MS Project, Primavera P6(Oracle)

- Visualize task hierarchies and dependencies effortlessly.

- Make informed decisions and streamline project management.

Date and Time Restrictions

- You can now specify certain timeframes during which logistics are unavailable for use on a project at a task's Process and Step level of logistics.

- This feature empowers you to accurately represent real-world constraints within your projects.

- Constraints may include Local Laws, Environmental restrictions, Cost reduction and financial planning, Authority body rules, and more.

- Enhance your project modeling experience with unparalleled flexibility and realism

How to use: Date and Time Restrictions document

The feeder vessels can be assigned different feeder task combinations as long as all the feeder tasks main task is assigned to the same HLV. However there was an edge case scenario of a feeder task combination on the same feeder vessels, that broke the HLVs work flow.
The scenarios we could handle without problems:

• Same feeder task type, but for different main tasks (on the feeder vessel would be:)

  • Feeder task type A for installation task 1

  • Feeder task type A for installation task 2

• Different feeder task types, but for the same main task (on the feeder vessel would be:)

  • Feeder task type A for installation task 1

  • Feeder task type B for installation task 1

The scenario we could not handle before, but we can now

• Different feeder task types, and different main task (on the feeder vessel would be:)

  • Feeder task type A for installation task 1

  • Feeder task type B for installation task 2

1. Addressing variations for multiple feeder tasks under Logistics - process

2. Removed invalid warning for Construction 1 - When you add assets with tasks from input library 

Adding related instances on the asset

1. Modelling cases with multiple feeder vessels
2. Adding steps for anchor Handling vessel - Processes