Corrective maintenance and service orders

Corrective maintenance is a workflow for wind, solar and storage sites. A repair report answers three questions at once: what broke, what was done about it, and what was left. Aevy reads all three, closes the fault where the repair actually closed it, and keeps the parts consumed against the equipment they went into.

When to switch this on

When repairs and service orders arrive separately from the faults that triggered them, so nobody can say whether a defect raised three months ago was ever fixed. Ask your Aevy contact to switch it on and name the assets.

From a repair report to a closed fault

The second box is the one people forget. A repair that fixed the fault but noted a worn part alongside it has created work, and a report filed as “done” hides that.

Aevy keeps the parts consumed as part of the record, so the spares that went into a unit are visible against it rather than only in a stores ledger. Where the report gives a fault date and a completion date, both are kept, which is what lets you see how long a repair actually took.

Set it up

Step	What happens	Who
1 Systems and parts	The equipment exists as records, so a repair and its spares land on the unit they belong to.	Aevy
2 Documents	Repair reports and service orders reach Aevy, by sync from your source.	You
3 Agree the closing rule	What a repair has to say before it closes a finding rather than commenting on one. See below.	Together
4 Switch on	Aevy turns the workflow on for the assets you named and reads back to the date you agreed.	Aevy
5 Review	Proposed closures and new work wait under Suggestions, each naming the report behind it.	You

Decide before it runs

Decision	What it changes	Where portfolios land
What closes a finding	Whether a repair report closes the fault outright or proposes a closure for someone to confirm. Closing on the paperwork is faster; confirming is defensible.	Proposed rather than automatic, at least until the reports prove reliable. A finding closed in error is worse than one closed late.
Leftover work	Whether a note that the job was partly done raises new work, or is only recorded on the existing finding.	Raised as new work. A partial repair is the case most likely to be lost.
The start date	How far back Aevy reads. Reading back further than your findings go produces closures with nothing to close.	Matched to whatever date the fault side of your register starts, so repairs and faults cover the same period.

Work the repairs

Closures and new work both arrive as proposals against findings. Accepting a closure resolves the finding and leaves the repair report attached as the evidence, which is the answer to “prove this was fixed” at audit time.

The reading that matters is the pairing. A fault with no repair against it after months is either forgotten or fixed without paperwork, and both are worth knowing. Group by system and sort by age to find them.

Limits

Aevy pairs a repair to a fault from what the documents say. Where a service order names no fault, or names it only as a work order number you hold in another system, the repair is recorded but pairs with nothing.

Parts consumed are read as the report lists them. This is not a stock system: it tells you what went into a unit, not what is left on the shelf.

What’s next

• How workflows work: the set, and what each needs before it runs.
• Preventive maintenance: where most of the faults these repairs close come from.
• Findings: the record a fault and its closure live on.
• Events: the site timeline a repair visit appears on.