PV plant
Operator, location, system data, strings
What the demonstrator implements
The RETRIEVE DPP platform connects information about photovoltaic modules across their lifecycle. Explore how module types, passports, certificates, installations and service records relate.
How the records relate
A passport belongs to an individual module and uses information from its module type. A module can also be linked to a plant. Service records concern the module or plant, while certificates apply to a module-type version.
installed in
Serialized module
Serial number, owner, installer
built to
Module type · version
Specifications, material composition, data sheet
records
new version on publish
certified as
Lifetime events
Installation, observations, confirmed findings, with source and author
referenced by
Passport versions
Snapshot of the module record with a stored content hash
v1v2v3v4
referenced by
Certificate association
Issuer, validity, applicability to one module-type version
Technical specifications
A module type version provides the shared technical definition for its individual modules. It brings together design, dimensions, power ratings, circularity and material information. Once referenced, certification-relevant changes require a new type version.
- 1Shared definition: General characteristics apply to modules of this type version.
- 2Technical details: Design and electrical values describe the product.
- 3Type versions: Modules and certificates refer to a particular version.
- 4Material composition: The module type can describe its materials and components.
Structured, versioned DPP records
A passport belongs to one serialized module. Published versions bring together its identity, shared type information, applicable certificates and recorded events as snapshots that can be checked later.
- 1Passport history. Every version stays available.
- 2Validation: confirms this version matches its stored snapshot. It does not prove the original data is correct.
- 3Circularity information: Recyclability, recycled content, renewable share and expected degradation can help inform later decisions when values are available.
- 4Module information from the module type and the serialized module.
- 5Lifetime events: Recorded events build the history of an individual module, from manufacturing and installation to inspections and confirmed findings.
Certification and applicability workflows
A certification decision concerns a specific module-type version. The demonstrator checks which modules it covers and shows the passport updates before the decision is published.
- 1Decision: approve or reject, validity and reason.
- 2Applicability must be resolved before an approval can be sent.
- 3Module-type version receives the certificate association.
- 4Serialized modules covered by an approval can receive new passport versions. Later modules are covered when the certificate applies to the type version.
- 5Attribution: the platform publishes on behalf of the issuer. It is not the issuer.
Contributions from the field
Installation links a module to its location in a plant. Service work can turn a plant observation into a confirmed finding for an individual module. The demonstrator uses seeded source records for both workflows.
- 1Read-only source: a seeded as-built record or work order. External ingestion is not implemented.
- 2Contribution: the installer adds missing positions. A service provider identifies the affected module and records a diagnosis.
- 3Passport updates: commissioning or a confirmed module finding can publish a new version. An observation remains separate.
- 4Publishing happens only after confirmation.
Passport history
Passport history preserves earlier snapshots so a reader can compare what was recorded at different points in a module’s life. The current snapshot can be checked against the stored record.
- 1Version selector across all passport versions of the module.
- 2Validation: confirms whether the displayed version matches its stored snapshot.
Relationships between modules and installations
An installation places individual modules in a plant and records their positions. Plant and module events provide context for what happened at the installation and to its modules.
- 1Plant information: operator, system data, location.
- 2Modules installed in this plant, each with its passport.
- 3Lifetime events at plant and module level, marked by type.
How data gets in and out
Push performance data
A per-plant API key allows performance measurements to be sent to the plant record.
Performance file upload
Measurement files can be uploaded to a plant record for performance monitoring.
Data sheets
Data sheets can be uploaded and downloaded with a module type.
Download DPP
A passport version can be downloaded from its record.
Not part of the current application
These topics appear in our published research or in project scenarios. They are not implemented in the demonstrator.
Read about the research- Cross-platform federation of passports
- Blockchain or ledger anchoring
- Reuse and second-life workflows
- Recycling and recovery reporting
See it for yourself
Open the public example passport or sign in to the web application.