Wind turbine service · Fictional example
Before maintenance, know
what is documented.
Use approved maintenance information, documented spare-part status and reviewed experience together. Knowledge held by individual colleagues can help the team once it has been reviewed and approved.
Fictional example
Mira prepares for the next service visit.
Mira works on a wind turbine manufacturer’s service team. A turbine is due for maintenance and has a recurring alert to investigate. She needs the applicable documents, the documented spare-part confirmation status and experience from colleagues who know comparable situations.
Tuesday · 06:40 · Fictional example
“What is approved for this turbine, how old is the spare-part status, and what do our colleagues know about it?”
Before the assignment
Retrieve approved documents and reviewed experience.
After the assignment
Record your own equipment-specific knowledge as a draft.
On the next assignment
After review and approval, reuse it for relevant assignments.
Two service situations
The specific equipment.
The relevant context.
01
Maintenance work
Mira asks for the approved maintenance information for the specific turbine. For the required spare part, she sees the documented status with its source and timestamp; missing current confirmation remains unresolved.
02
Fault incidents
Mira retrieves recorded fault reports and approved experience from comparable situations. She separates confirmed observations from assumptions and clarifies the remaining questions with the team.
The right knowledge
Sources, versions
and unresolved questions.
Manual knowledge and experience are shown with their applicable scope.
01
Maintenance documents
The turbine identifier, model series and configuration identify the approved maintenance manual and its version.
02
A dated spare-part status
The available record shows its timestamp. Without a newer confirmation, current availability remains unresolved.
03
Shared experience
An approved experience report identifies the equipment and conditions. A similar case does not establish the cause.
A conversation on site
Grounded answer.
Focused clarification.
Fictional example
“Is the spare part confirmed, and is there reviewed experience about this alert?”
Sources and scope
Asset record with turbine identifier and configuration; approved maintenance manual with version; spare-part confirmation with timestamp; a reviewed and approved experience report tied to specific equipment.
What remains unresolved
The answer describes available sources, not live stock levels or authorisation to repair or operate the turbine.
“The available spare-part record has a documented timestamp; no newer confirmation is available here. The approved experience report concerns a different configuration. Whether it applies to this turbine remains unresolved.”
“Which configuration is recorded for this turbine, and who can confirm the spare-part status?”
Mira takes the missing details to the named subject-matter and logistics owners. The responsible team assesses the cause and what happens next.
The knowledge cycle
Record experience.
Share reviewed knowledge.
Experience is captured as a draft. It supplements approved documents only after subject-matter review and approval.
01
Ask before the visit
Mira retrieves maintenance information supported by sources and clarifies which details are still missing.
02
Express tacit knowledge
After the visit, she records her observations and discusses with a colleague which experience shaped his assessment.
03
Review the experience
The draft names the equipment, conditions, evidence and uncertainties. The named subject-matter owner reviews it and defines where it applies.
04
Approve for the next visit
Only after approval can the next technician retrieve the versioned report and assess whether it fits their turbine.
Four elements of the VOP
Make knowledge accessible.
Keep experience in the team.
01
KSE
Links approved sources to the turbine, document version and spare-part timestamp.
02
Voice
Answers Mira’s questions from those sources and identifies unresolved status and limits.
03
TalkTo
Records which knowledge may be used and who reviews and approves new experience.
04
Frontend
Shows sources, document versions and status timestamps, and lets Mira add details to her experience draft.
The first pilot
One team. One scope.
A clear knowledge cycle.
Pilot objective
Wind turbines
One service team and one turbine model series. Agree source versions, status upkeep and subject-matter ownership; assess questions and experience drafts together.
Scope and effort
Manual preparation, approved access, integration and subject-matter upkeep are defined together for the pilot. The agreed scope becomes the basis for an offer.
Buyer FAQ
Questions before
your first pilot.
Which documents do we need?
Asset record with turbine identifier and configuration; approved maintenance manual with version; spare-part confirmation with timestamp; a reviewed and approved experience report tied to specific equipment.
How does experience become team knowledge?
A named subject-matter owner reviews the draft, requests clarification if necessary and defines its scope. Only the approved version becomes available to the team.
Is spare-part availability live?
Only when an approved current data source is connected. The answer shows its timestamp. Without current confirmation, availability remains unresolved.
Who decides what happens on site?
Mira takes the missing details to the named subject-matter and logistics owners. The responsible team assesses the cause and what happens next.
How do we start?
One service team and one turbine model series. Agree source versions, status upkeep and subject-matter ownership; assess questions and experience drafts together.
