For owners and operators
Learn from the failures at other sites before they happen at yours.
Asset managers, HSE leads and O&M teams use the register to see what went wrong in commissioning, operation and maintenance elsewhere, which components failed, and what the lessons were.
The Energy Incident Register is a data contributor to the PV Fire Intelligence Network (PV-FIN), led by BRE, and has been reported by DatacenterDynamics (DCD).
The register's own rule: every entry cites its sources, and a correction is free for anyone.
How long assets were out, and what it cost. Every entry carries an estimate of the repair cost and the time out of service, or the figure a source states, so you can plan spares and cover against real events. How the estimates work.
Failure modes for your technology
The insights page maps recurring failure modes by asset type and category, each with the case studies and lessons behind it.
Supplier track record before you sign
The verified record names the OEM and integrator and the failed element, so procurement can ask the right questions.
A benchmark for your own fleet
Compare your availability and incident history against the register's recorded rates for the same technology and age.
Going to renewal or refinancing? A portfolio safety record shows each of your sites against the published record, with today's date, in one link for your broker or lender. Free.
Preparing a planning application? The planning evidence pack sets out every comparable incident in the register for your project: in your country, near the site and at sites of a similar size, with the lessons and sources. £295, by email in minutes. See an example.
How the data is made. Public reports are found daily, drafted into the register's format, reviewed against fixed rules, and published as confirmed or provisional with the sources listed. Provisional entries are rechecked automatically. The verified record behind each entry is built from the same sources and approved only when the figures are supported. Methodology. Accuracy disclaimer.