Maintenance that lives with the asset.

The problem

The CMMS knows about the work order. The CMS knows about the vibration spike. The inspection contractor's portal has the blade images. The OEM service report is a PDF in someone's inbox. Reconstructing what actually happened to a turbine over a year takes hours, and the data needed to plan the next intervention is scattered across four systems.

How WindTwin solves it

• Work orders on the twin — every ticket lives on the turbine (or component) it concerns, with the SCADA context that triggered it.
• Reusable inspection templates — tower bolt torque, blade tip-to-tower clearance, drive-train torque, gearbox oil sample, electrical cabinet thermography. Build once, run forever.
• Recurring schedules — monthly, quarterly, by operating hours, by component-lifetime. Misses get flagged.
• Mobile capture — crews record findings on phone or tablet, photos and timestamps attach to the work order automatically.
• Drone & UAV survey integration — blade-image sets attach to the blade twin, with defect tagging that feeds the inspection schedule.
• From alarm to job in one click — a fired alarm turns into a dispatched ticket; the closing report attaches to the alarm and the asset.

How it works

1. An alarm, schedule, or operator action opens a work order against the relevant twin.
2. The work order is dispatched with the asset's full context — model, location, recent telemetry, prior work.
3. The crew completes the checks on mobile. Photos, notes, and findings stream back in real time.
4. The closing report attaches to the asset; the component lifetime ticks; the next scheduled inspection is rebased.

What you can do with it

• Plan a maintenance campaign by querying live component-lifetime data, not last quarter’s spreadsheet.
• Show the OEM, the regulator, or the auditor a complete, time-stamped history of every intervention on a turbine.
• Catch the slow-to-emerge blade defect across a campaign by querying tagged drone imagery.