Changelog Shoreline Simulations 3.57.4
This release adds secondary-base support for helicopter scheduling and a relative wave direction weather criterion, alongside a set of fixes to visualization, dashboards, and case configuration.
Vessels & Scheduling
Secondary base support for helicopters
What's new
Helicopters can now be assigned a Secondary base in addition to their primary base. When a secondary base — typically an offshore base or an SOV — is set, the helicopter can pick up and drop off technicians there instead of always returning to its primary base.
You can also choose which location the helicopter idles at while waiting between jobs: it can return to its Primary base (e.g. its home airport) or wait at the Secondary base (the offshore base or SOV). This is controlled by a new Idle at secondary location setting.
Behind the scenes:
- A new combined offshore-location selection sets the vessel's secondary base and idle-location preference together.
- The scheduling engine adds a dedicated move-to-secondary-base activity, so crews based at the secondary location are correctly picked up and dropped off there rather than at the primary base.
- If no secondary base is configured, behaviour is unchanged — the helicopter continues to use only its primary base, exactly as before.
Where to find it
Vessels → helicopter availability entry / instance configuration → Primary base and Secondary base fields.
How to try it
Configure a helicopter with both a primary and a secondary base, set Idle at secondary location, and run a case. Confirm technicians based at the secondary location are picked up and dropped off there, and that the helicopter idles at the location you selected between jobs.
Note: The default configuration (no secondary base set) preserves the previous behaviour exactly — this is an opt-in feature and should not change results for existing cases.
More information: https://docs.shorelinewind.com/secondary-base-support-for-helicopters
Weather & Case Configuration
Relative wave direction restriction for weather matrixes
What's new
Weather-limit matrixes can now restrict operations based on relative wave direction — the direction waves hit a vessel or asset relative to its heading or access point — rather than only the absolute compass direction. This reflects that vessels typically tolerate larger waves from astern (following seas) than from the bow (head seas) or the side (beam seas).
At runtime, the simulation converts the absolute wave direction from the weather data into an angle relative to a reference direction:
- For a moving/route step, the reference is the stern (opposite the direction of travel).
- For a stationary step at an infrastructure asset (e.g. a turbine transfer), the reference is the configured access-point face.
- If no heading is known, or the restriction isn't set to relative mode, the criterion falls back to the absolute wave direction as before.
0° corresponds to following seas, 90° to beam seas, and 180° to head seas. If an asset exposes multiple access points, the simulation checks each candidate reference direction and treats the weather as workable if at least one access point complies.
Note: For a relative wave direction matrix, a cell value of 0 is a genuine limit of zero (no operation allowed at that relative angle) — unlike other weather matrixes, where 0 means "no limit."
Where to find it
Design → case configuration → weather matrix setup → wave direction restriction type.
How to try it
Set up a weather matrix using the relative wave direction restriction, configure a vessel heading or access-point face, and run a case. Confirm the simulation applies the limit based on the angle between the wave direction and the reference direction rather than the absolute compass direction.
More information: https://docs.shorelinewind.com/relative-wave-direction-restriction-for-weather-matrixes
Fixes
- Fixed an issue where variations in heavy-lift vessel (HLV) configuration could cause simulation runs to fail.
- Fixed the simulation visualisation clock showing UTC instead of the case's configured local time for non-UTC timezone cases (affecting the clock display and the map marker popup).
- Fixed the Work order task (dependent task) field appearing empty when re-opening an activity that already had a dependent task assigned.
- Fixed the Simulation usage tooltip remaining on screen and overlapping the top navigation after hovering and navigating away.
- Fixed a visual bug where inter-array cables (IAC) were not rendering correctly on the map.
- Fixed the case's Updated date not refreshing after saving a new configuration change.