Modeling processes

Processes let you configure the duration and logic of installation and transit operations for each logistic, so your simulation accurately reflects real-world time frames. You can set up processes at the input library level (to reuse across cases) or at the case level (to apply to one specific case).

Processes are available on the following logistics:

Heavy lift vessel
Cable installation vessel
Towing vessel
Crane
Anchor handling vessel
Feeder
Component transfer vessel

Learn how to add and configure processes in our Processes guide.

Below, you can find details on how processes work, how to override them for specific tasks with process variations, and details on each step input.

How processes work

Note: Processes are not required for a simulation. You can skip processes by setting each process Duration value to 0 and deselecting any options.

Each logistic has a preset selection of processes, broken down into fully customisable steps. You can add and remove steps and complete the inputs as required.

Every task that uses a process runs this default, unless the task has been linked to a process variation instead — see Process variations below.

During the simulation, processes are carried out in the order shown in the app. When a logistic carries out a task, all the processes are scheduled together, in one continuous block, without additional time between steps. Mobilization starts on the hour, and subsequent processes begin immediately after the previous step has been completed.

Note: Once a case has been used to run a simulation, its process configuration is locked. You can't add, edit, or delete steps, parameters, or variations. Make all the changes you need before running the case.

Process variations

Every task that uses a given process type (e.g. 5.0 - Crane operation) runs the same default process, with the same steps, durations, and weather criteria, unless you tell it otherwise. A process variation lets you override this for one specific task — for example, if a particular component replacement realistically takes longer than the duration you've set on the default process.

How a task gets its process

If a task is linked to a variation, it uses that variation's steps, durations, and weather criteria for the simulation.
If a task isn't linked to any variation, it uses the default process instead.
A task can only be linked to one variation. Once a task is assigned, it no longer appears in the Select task dropdown for other variations of the same process type.
A variation with no task assigned isn't used in the simulation — its steps exist, but nothing triggers them.

For example, if your HLV's default 5.0 - Crane operation is set to a 5-hour duration, but one specific WTG's component replacement realistically takes 12 hours, create a variation, set its duration to 12 hours, and link it to that task using the Select task dropdown. Every other task that uses 5.0 - Crane operation keeps the 5-hour default.

Note: Variations of a Working with feeder process can only be linked to feeder tasks — they aren't offered your case's other maintenance or installation tasks.

What a new variation starts with

When you click + Add variation, Shoreline creates the variation from the platform's default step template for that process type — not from any changes you've already made to this case's or input library item's own process. If you want a variation that keeps your existing customisations as its starting point instead, use Create copy (via the three-dot menu on the process or on an existing variation) rather than + Add variation.

What's shared with the default process, and what isn't

Steps, durations, weather criteria, and time restrictions are fully independent per variation: editing them on one variation has no effect on the default process or on any other variation, and vice versa.

Learning curve settings are the exception. They're configured on the default process only — the Learning Curve button isn't available on variations — and apply to every variation of that process type as well.

Step inputs

Steps are where you can customise the logistic processes. The inputs you see will vary depending on the step you are editing. Below, you can find details on each input.

Define max allowed time to wait

This checkbox enables the Max time to wait before start input box in the Parameters section of the step.

How it works

It is often crucial to plan steps sequentially with little or no time between them. For example, you can only start step 1 if you know you can also complete steps 2 and 3 without interruption.

This option provides a way to define how long a logistic can wait to start the current step following completion of the previous step, i.e., the maximum weather downtime between steps.

Leaving this setting unchecked allows the logistic to remain idle indefinitely before starting the step, providing maximum flexibility.

Note: This setting is specific to the steps within a single process. It doesn't apply between separate processes or tasks.

Crane example

A simplified crane operation for a nacelle installation might consist of 3 steps — hooking up, hoisting, and connecting — that must be carried out in a single operation. This might require the following restrictions and max wait times:

Hooking up

Duration: 2 hours
Weather restrictions: None

Hoisting

Duration: 5 hours
Weather restrictions: Wind speed, 10 m/s
Max time to wait before start: 0

Connecting

Duration: 5 hours
Weather restrictions: Wind speed, 5 m/s
Max time to wait before start: 0

The three steps require three continuous weather windows totalling 12 hours where the weather limitation of each step is not exceeded. The hooking up step will not start until the simulation encounters such a weather window.

Flexibility examples

Scenario 1, no flexibility:

Step 1

Duration: 10 hours

Step 2

Duration: 10 hours
Max time to wait before start: 0 hours

To complete these 2 steps requires a continuous weather window of 20 hours, as the vessel cannot remain idle between the steps waiting for good weather.

Scenario 2: some flexibility

Step 1

Duration: 10 hours

Step 2

Duration: 10 hours
Max time to wait before start: 4 hours

Here, there is more flexibility for completing the steps. The weather criteria can be exceeded, i.e., there can be bad weather, for up to 4 hours following the completion of step 1 before a 10-hour weather window opens to complete step 2. You can create more flexibility, if required, by checking the Flexible option.

Repeat

If a step requires carrying out multiple times, e.g., loading out blades, you can check the Repeat box to model this repetition without having to create a step for each loadout procedure.

Note: Repeat is only available on steps within Loadout, Loadoff, and Working with feeder processes.

Inherit task duration

Note: Design O&M only.

When you check this box, the process step inherits its Duration value from the Replacement time value on the relevant corrective maintenance task.

Generally, this checkbox is used on 5.0 - Crane operation, as this is the replacement work itself.

Use this setting to define the work duration generally on the asset.

Flexible

Check this box to allow work on a step to pause and resume as weather conditions allow. On site, such pauses and restarts might occur during cable laying, due to increased wave height, or at the request of a marine warranty surveyor.

Checking Flexible replaces the step's Required weather window input with two new inputs:

Min. work duration: The minimum required weather window for a work period to begin.
Max wait between work periods: Acceptable weather downtime between work periods. If bad weather lasts longer than this, the step is reset, i.e., the step again requires the whole step Duration to complete.

Although the Flexible option might seem like it would cause more disruption, it can actually reduce total downtime by making use of smaller weather windows. For example, if two short weather windows occur within a 24-hour period — each too short on its own to complete the full step, but sufficient when combined — the Flexible option splits the step across both windows, avoiding a full 24-hour delay.

Parameters

There are 2 default parameter inputs:

Duration: The time required to complete the step.
Required weather window: The period of good weather (determined by the weather criteria) required to complete the step. This input is replaced by Min. work duration and Max wait between work periods when Flexible is checked (see above).

Speed and transit times

Transit processes have a Speed input instead of a Duration input, where you can define the cruising speed of the logistic. This value is used to determine the duration based on the distance travelled to complete the step.

You can view the average transit times to different assets given the Speed input by clicking the three-dot overflow menu icon, then clicking Transit times.

Weather criteria

Set the weather conditions under which work on this step can take place. These limits work together with the parameter inputs (Duration and Required weather window) to determine how long the step takes during the simulation.

You can choose which weather limitations are available by using the three-dot menu icon and clicking Manage limitations.

For information on the available weather limitations, see the Weather limitations article.