NOTE: The output described in this article is for the first simulation run only.
In the logistics log are all the movements of each transportation documented. In the following table are all the different columns with an explanation available.
| Column title | Description |
|---|---|
| Turbine ID | The turbine ID identifies the turbine on which the operation was done. |
| Work Order | The work order is an ID to identify a specific task. When a task couldn't be finished on one day, there are more operations for this task and so also more than one row. |
| Task | The task is a name, which includes the turbine name, turbine ID and the title of the scheduled maintenance/component. |
| Severity (failure) | The severity displays how urgent a task is, possible is e.g. "Scheduled Maintenance" or "Critical failure". |
| Vessel ID, drop-off | The Vessel ID for the drop-off is the name and ID of the vessel which did the transfer of the technicians to the asset. |
| Vessel ID, pick-up | The Vessel ID for the drop-off is the name and ID of the vessel which did the transfer of the technicians back from the asset. |
| Birth time (failure) | The birth time displays the time when the task was created, so e.g. when the failure appears or the scheduled maintenance was requested. |
| Team drop-off | The team drop-off is the time when the team was dropped-off to the asset. |
| Team start working | The team start working is the time when the team starts working (this is not identical with team drop-off e.g. because of breaks or preparation). |
| Team stop working | The team stop working is the time when the team stop working (this is not identical with team pick-up e.g. because of waiting for the transportation). |
| Team pick-up | The team pick-up is the time when the team was picked up from the asset. |
| Remaining hours (start) | The remaining hours (start) are the hours which are left for the task before the team started working. |
| Remaining hours (stop) | The remaining hours (stop) are the hours which are left for the task after the team finished working. |
| Average wind (drop-off - pick-up) | The average wind (drop-off - pick-up) is the average wind speed for the duration when the technicians were on the asset (so that the asset couldn't produce). |
| Weather Year | The weather year is the information about which year of the weather data was used for the calculation of the average wind. |
| Total Sub-contractor hours | The total sub-contractor hours are the number of hours which sub-contractors worked on the task. |
| Total Sub-contractor hours incl weather | The total sub-contractor hours are the sum of hours which sub-contractors worked on the task and were waiting to start the task due to the weather conditions. |
| Charter hours cumulative | The charter hours cumulative are the sum of charter hours which were necessary for the task. |
| Technician group | The last column has a specific, flexible name due to the requested qualification. It shows how many technicians with this role were working on the task. |
The remaining hours are the estimated working hours, which still needs to be done, not included are the transfer or other times.
When e.g. a task is estimated with 8 working hours and a team start working on the task for the first time, the remaining hours (start) are 8 h. When this team worked 6 h on this task until they were picked up, the remaining hours (stop) are 2 h.
Usually, this team would work on this task also on the next day. So then the remaining hours (start) would be 2 h, then the team would finish the task on the day and the remaining hours (stop) are the 0 h.
When e.g. a task is estimated with 8 working hours and a team start working on the task for the first time, the remaining hours (start) are 8 h. When this team worked 6 h on this task until they were picked up, the remaining hours (stop) are 2 h.
Usually, this team would work on this task also on the next day. So then the remaining hours (start) would be 2 h, then the team would finish the task on the day and the remaining hours (stop) are the 0 h.
The column with the technician group is flexible, that means, that the title depends on the name of the technician role. When there are two different roles defined, a second column for the second role will be added.
When for example for a turbine are two different scheduled maintenance defined, with the following required technician roles:
When for example for a turbine are two different scheduled maintenance defined, with the following required technician roles:
- Maintenance 1
- 2 x Electrician
- 1 x Mechanic
- Maintenance 2
- 3 x Electrician
Here is an example of how this file will look, the length of the file depends on the number of scheduled maintenances, components, available resources and the selected duration if found underneath.