O&M providers manage assets they didn't commission, with data they didn't create, in formats they didn't choose. DERpass gives them a single canonical file per asset — event log, component data, maintenance schedule, and reporting inputs — from day one.
Each managed system has its own spreadsheet, built by whoever onboarded it — partially from the installer's handover, partially reconstructed from portal exports. Data quality is inconsistent across the portfolio.
Service tickets live in a helpdesk system. Asset data lives in a different tool. Linking them requires manual cross-referencing. When an asset changes operator, the ticket history stays behind.
Producing a monthly owner report requires pulling yield data from the monitoring platform, contract details from the CRM, and maintenance records from the ticket system — then assembling them manually in a template.
Taking on a new portfolio means collecting data from each installer, chasing missing certificates, building a new spreadsheet per asset, and normalizing all of it into the operator's own system before any productive work can begin.
Every maintenance visit, repair, curtailment, and firmware update should be logged in the same file as the asset data — timestamped, with technician attribution, and linked to the asset it describes.
Due dates and service intervals should be structured fields that a scheduler or monitoring dashboard can consume directly — not free text in a PDF that someone has to read and re-enter.
Owner reports should be generatable from one canonical file, not assembled from exports across three systems. The file should contain everything an owner needs: components, yield, contracts, and history.
A file format that any installer can produce and any O&M platform can consume without custom integration work — validated by a public schema, not negotiated per project.
Every maintenance visit, fault, curtailment event, firmware update, and ownership change is appended to the events chapter — timestamped, typed, and optionally signed. When the asset moves to a new operator, the history moves with it.
The maintenance chapter carries O&M contract terms, inspection intervals, and next-due dates as structured fields — feed them directly into any scheduler, monitoring dashboard, or alerting system without manual extraction.
The .derpass contains components, generation data, compensation terms, maintenance history, and insurance — everything needed for an owner report. Generate it from the file instead of assembling it from multiple system exports.
Accept a .derpass as the standard handover format from any installer. Validate it against the public schema in seconds. If it passes, you have everything you need to import the asset — no chasing, no normalization.