How a problem enters the system — governed alarm references and weather events, the service requests raised from them, the defects they become, the operational impact in lost or derated capacity, and the priority assessment that decides how fast to respond

The planned response — work orders and their child tasks, the people and organisations assigned, the dependencies that gate a start, the status history, and the maintenance templates work is generated from

The field record and the three separate acts of closure — inspections and their results, measurements, technician notes, evidence and tests, then return to service (equipment re-energised), verification (independently checked) and closeout (defect closed)

Making the work safe to start — isolation references (DC/LV/HV requested, applied, proved dead, released), access requirements, the safety documents accepted for a work order, and the competencies people hold

Lightweight materials and recovery — the parts catalogue, stock locations and holdings, parts required and used on a work order, components removed for repair or return, and warranty claims against the manufacturer

Vegetation as a specialist stream — the managed vegetation zones with target and intervention heights and firebreak rules, and the inspections against them — plus the site zones and asset locations they sit within

What is being maintained — the portfolio and solar farms, the asset types catalogue, the asset register with its parent-child structure and operational status, asset relationships, and the source systems feeding the hub

Parties and reference data — organisations and people, controlled documents, the defect category catalogue, and the inspection templates and their items