These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Wind Farm Management
- Features
- Maintenance work
Maintenance work
Assigned tasks from approval to completion.
OverviewMy maintenance tasks×
Wind Farm Management · Maintenance work
New
My maintenance tasks
Maintenance tasks
| Id | Task | Site | Due date | Status | |
|---|---|---|---|---|---|
| IDD-186 | TSK-797 | STS-9503 | 07 Oct | Open | |
| IDD-438 | TSK-793 | STS-2184 | 12 Oct | Approved | |
| IDD-899 | TSK-661 | STS-9883 | 14 Oct | In progress | |
| IDD-919 | TSK-911 | STS-9189 | 19 Oct | Completed | |
| IDD-226 | TSK-218 | STS-5925 | 21 Oct | Open |
6 of 6 records
IDD-186Maintenance tasks · MT-44136
OpenTaskTSK-797
SiteSTS-9503
Due date07 Oct
What you can do
Approve the work before anyone climbs a tower
Maintenance tasks are recorded against a site with a description of the task, the person assigned, a due date and, once done, the completion date. A task moves through four states: open when raised, approved when the site manager agrees the work, in progress while the technician is on it, and completed when it is done. Tasks come from operational events that need a response, and from planned work the site manager schedules.
The approval step exists because maintenance on a wind farm means people at height, turbines taken out of production and sometimes contractors on site. The site manager approves each task before it starts. The person assigned can see exactly which tasks are approved and waiting for them.
How the work is organized
The site manager approves; the maintenance technician does the work and records it.
- Raised with context. A task raised from an event is on the same site as the event, so the reason for the work stays attached.
- Approved before started. Only approved tasks move to in progress.
- Completed with a date. Completing a task records when it was done, so due and completed dates can be compared.
What to agree during setup
Agree who can raise tasks and who approves them, including cover when the site manager is away. Agree how contractors are recorded: as people with user accounts, or as notes on the task. Decide how far ahead planned work is entered and how overdue tasks are followed up. Prepare examples of a corrective task raised from a fault, a planned service, a task that is cancelled before approval and a task that runs past its due date.
Check the handoff on an actual case
A blade inspection is due on three turbines at one site next week. The site manager raises the tasks, assigns them to the technician, and approves them once the weather window and crane are confirmed. On the day, the technician starts each task, completes it and records the completion date. The tasks drop off the maintenance in progress list and appear in the completion report against their due dates.
If the weather window closes before the work starts, the tasks are changed or cancelled while they are still in the future. Work that was already accepted keeps its history instead of being rewritten.
What your team sees
- Maintenance tasks awaiting approval — Open tasks waiting for the site manager.
- My maintenance tasks — The technician’s own tasks and due dates.
- Maintenance in progress — Approved and in-progress work by site.
Follow the work through
- Maintenance approval and completion: From a raised task to completed work.
- Event to resolution: How tasks raised from events fit into resolving them.
Check permissions before inviting contractors.
What it keeps track of
Data model- Maintenance tasks
- Assigned maintenance work with due dates and completion state.
- Sites
- Wind generation sites and their operating status.
- People
- Wind farm staff and their platform user accounts.
Who uses it
Permissions- Maintenance Technician
- , Site Manager.
- The site manager approves tasks; the technician carries them out and records completion.
Set up Wind Farm Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.