What the Copilot works from
The Copilot reasons over the information already held against the job: the turbine technology, manufacturer, model and platform, the alarm code and its fault description, the incident, the work order, previous maintenance records, engineering documentation, knowledge articles and the findings and measurements the technician has recorded so far.
Because it works inside the session, its answers stay tied to the actual turbine and the actual job rather than to a generic description of the fault.
- Session-scoped context: turbine, technology, alarm and work order
- Diagnostic assistance with recorded steps, measurements and findings
- Engineering knowledge and document retrieval during diagnosis
- Guidance for reporting and knowledge capture after repair
Where its responsibility ends
The Copilot assists. It does not perform autonomous fault diagnosis, does not certify a repair and does not override approved procedures. Safety-critical work remains governed by approved procedures, OEM requirements and authorised personnel, and a session stage completes only when the technician confirms it.
That boundary is deliberate. Maintenance decisions in wind energy carry safety and contractual weight, and a tool that blurred the line between advice and authority would be a liability rather than an asset.
Two execution modes, one record
A session can run in Copilot mode, where AI guidance and generated diagnostic steps support the technician, or in manual mode, where the technician controls the process. Either way the outcome is the same record: phases, steps, measurements, photos, parts and conclusions.
That means the value of a Copilot session does not disappear when the Copilot is not in use, and manual sessions feed the same knowledge base the Copilot draws from.