This article has explanations for what the different (sub) root causes in the Shoresim3 scheduling algorithm covers and the order in which they are checked, which is decisive for what is shown in the outputs.
The root causes can be seen when downloading the "PBA root causes" sheet:
There are four types of root causes in Shoresim:
- Weather – not scheduled because of bad weather
- Response – not scheduled because of something other than weather
- Work – the time where work is actually done on assets
- Towing – the time the asset is being towed (only for floating assets)
Root causes are split into general categories. The root cause types are measured for each category.
Categories are:
- Major – the task is a Component Replacement Task
- Special condition – response time is recorded as lead time
- Floating – the task is a Component Towing Task
- Minor – the task is a Repair task (regular task, but not Scheduled Maintenance)
- Scheduled Service Work – the task is a Scheduled Maintenance
- Special condition – only the root cause type Work is recorded
- External – downtime and lost production from a Substation being down that impact WTGs
Sub root causes for Regular tasks
These sub root causes are recorded for external root causes, where they come from the same places.
Sub root causes for the type Response are:
- No room on asset
- No available vessel
- No available personnel
- Emergency response limit
- No drop-off and pickup combination
- Waiting to be scheduled
The table below shows the order the reasons are checked when scheduling, and a short explanation on what it covers.
| Order | Root cause | Reason for not scheduling | Notes |
| 1 | Response - No room on asset | The asset does not allow the number of technicians needed to do the task | If this condition is met, the task can never be done |
| 2 | Response - No available vessel | No allowed vessels available in the schedule | None of the vessel in the case have a work schedule that covers the day |
| 3 | Response - No available personnel | No personnel with the right skills available in the schedule | |
| 4 | Weather | No vessel with good port weather within its work shift | |
| 5 | Response - Emergency response limit | No vessel that can do an extra port visit due to the emergency response limit | |
| 6 | Weather | No vessel with good offshore weather within its work shift | |
| 7 | Response - Emergency response limit | Not possible within HSE | |
| 8 | Weather | No weather window for the weather limitation of the task | Weather limitations is set on the Weather criteria tab of the asset |
| 9 | Response - No room on asset | Not room on the asset for more personnel | This is set by using the "Maximum number of technicians in asset" in the Parameters tab on an asset |
| 10 | Response - No available personnel | No personnel available (used for other tasks) | |
| 11 | Response - No available combinations OR Weather | No combination of vessel and personnel availability | If there is any vessel that is limited because of weather in this scheduling period, then the root cause will be registered as "weather". Otherwise, If the weather is good all day, it will be registered as "Response - No available combinations". |
| 12 | Response - No available combinations OR Weather | No general combination available | This is a combination of everything, so if it did not hit any of the other reasons, but it was still not possible to schedule, this is the error that will be printed If there is any vessel that is limited because of weather in this scheduling period, then the root cause will be registered as "weather". Otherwise, If the weather is good all day, it will be registered as "Response - No available combinations". |
Sub root causes for Component Replacement Tasks
The sub root causes for the component replacement task are the following:
- Waiting to be scheduled for support vessel
- Waiting to be scheduled for HLV
- No available support vessel
- No available HLV
NOTE The “No available [vessel type]” sub root cause is set when there is no vessel available when trying to schedule. For the HLV this is also true if the lead time is not completed yet.
NOTE Be aware that when we check for a time with something, e.g. good weather, we only check if there is a period matching the minimum required amount of work within the scheduling period; some of the time, these periods builds on the previous period found. E.g. the emergency response period has to be valid while there is good weather.
NOTE The “Waiting to be scheduled” sub cause is set from the time the task is created or work is last stopped on it until it is picked up in a new schedule event.