Best practices
Aevy builds on the published best practice guidelines for renewable energy asset management. This page lists the guidelines Aevy works from, where each one shows up in the product, and how Aevy’s vocabulary maps to the ISO and EN standards behind it.
Aevy’s role at SolarPower Europe
Section titled “Aevy’s role at SolarPower Europe”Aevy is an active member of SolarPower Europe and contributes to its Asset Management and Digitalisation workstreams. SolarPower Europe’s Lifecycle Quality Workstream (running since 2015) publishes the reference guidelines for solar asset quality. They cover asset management, operation and maintenance, EPC, and technical due diligence, all free to read at solarbestpractices.com.
Aevy co-authored the workstream’s Technical Due Diligence Best Practice Guidelines for Hybrid Utility-Scale Solar PV and Battery Energy Storage Systems, published in February 2026.
The guidelines Aevy works from
Section titled “The guidelines Aevy works from”Five published references anchor how Aevy structures asset information: four SolarPower Europe guidelines and one IEC documentation standard.
SolarPower Europe publishes the Lifecycle Quality guidelines free to access, share, and use at solarbestpractices.com. The Technical Due Diligence Guidelines are on the SolarPower Europe site. The IEC webstore sells the IEC standards, and ISO and the national standards bodies sell the ISO and EN standards.
Wind assets follow their own inspection and documentation regimes. The mechanisms below (classification, obligations, inspections) work the same way for them.
The guidelines in the product
Section titled “The guidelines in the product”The clearest lines from guideline to screen:
- Contract and compliance management (Asset Management Guidelines). Aevy reads your contracts and extracts the obligations they create, then tracks each one on its own cadence: obligations, tasks, and events.
- Operational record keeping (O&M Guidelines). Findings and inspections are in one structured place instead of in contractor PDFs. See findings and systems and components, including statutory inspections rolled up from component to asset.
- Handover documentation (EPC Guidelines, Annex F; IEC 62446-1). Aevy classifies every document by type, subtype, and scope. That way, you can see what a data room contains against what a plant of that kind should hand over with. See how your data gets in.
- Technical due diligence (TDD Guidelines). When Aevy flags a deviation or a gap in a document set, the finding references the relevant guideline section rather than a reviewer’s own judgment. Every extracted value also links back to its source line: lineage.
Aevy maps its work to these guidelines. It doesn’t certify compliance with them.
Aevy’s vocabulary and the standards
Section titled “Aevy’s vocabulary and the standards”Aevy’s vocabulary follows the established asset management standards rather than software-tracker convention. The glossary shows the full Aevy definitions.
| Asset, system, component | ISO 14224:2016 defines the same three-level equipment taxonomy (equipment unit, system, maintainable item). |
| Event | ISO 14224 builds its data model on event records: failures and maintenance actions recorded against equipment at a point in time. IEC 61400-25 uses the same event model for wind SCADA. |
| Defect | ISO 9000:2015 defines a defect as a nonconformity related to intended use. EN 13306:2017, the European maintenance vocabulary, calls the state a fault. In Aevy a defect is one of the two finding types, tracked per component. |
| Obligation | ISO 37301:2021 and ISO 14001:2015 use compliance obligation for the requirements an organization must meet plus those it voluntarily commits to. It’s one word covering statutory duties, lender covenants, and O&M contract terms alike. |
| Activity log | ISO 15489-1:2016, the records management standard, calls this the audit trail: who changed what, and when, on the information itself. |
Aevy keeps one split the standards make: events describe what happened to the physical asset. The activity log describes what happened to the information about it. ISO 14224 governs the first world, ISO 15489 the second.