Gen318
Prepare the operator-side evidence
Telemetry, data quality, milestone status, exceptions, review, and immutable final reports.
Solutions · DARES developers
Know what is missing before the claim review.
Gen318 connects operating data, coverage checks and report preparation for participating mini-grid developers. Bring connection, consumption and quality records together for your compliance team to review and export to the Odyssey workflow.
Per site
Requirements
Reconcile applicable requirements before relying on automated milestone status.
Continuous
Quality control
Required signals, coverage, and data gaps checked throughout the evidence period.
CSV · JSON · PDF
Evidence export
Reviewable export formats for your compliance team to check.
01 · Claim-readiness workflow
From live telemetry to a reviewable claim package.
Prepare connection, consumption and quality records in one reviewable package. Before relying on automated milestone status, reconcile its legacy calculation with the current requirements and amounts for that site.
Programme evidence · illustrationOPERATOR REVIEW
Review records against the applicable programme requirements. This is not claim approval; automated milestone logic requires reconciliation before relying on current DARES terms.
CONNECTION EVIDENCEAttached
SOURCE RECORDS
DATA COMPLETENESSReview
PERIOD BASIS
Connection records attachedRECORDED
Consumption period recordedRECORDED
Site requirements need reviewRECORDED
Missing signal coverage needs reviewREVIEW
Site-specific programme requirements REVIEW
Review before export · finalisation preserves content
Odyssey
Remain the official programme platform
The site-specific application, document upload, claim submission, and programme workflow stay in Odyssey.
REA · IVA
Programme verification and decision
Required supporting documents and formal verification remain part of the programme process.
02 · Evidence quality
Find missing readings while there is time to investigate.
Use expected signals, source age and both coverage measures to locate gaps in the reporting period. Automatic submission requires enablement and quality gates, including exclusion of synthetic telemetry. Programme verification and acceptance remain with the programme process.
Integration health · portfolio
CheckBOTH AXES
DELIVERY Arrived?TRUST Usable?
Connection checks.
A gauge alone cannot establish evidence quality.
Checks · by adapter30-DAY WINDOW
Victron · VRMREVIEWOpen
Source age
Inspect freshness
Expected signals
Inspect mapping
Period quality
Delivery + trust
SparkMeter · KoiosREVIEWCheck
Huawei · FusionSolarREVIEWCheck
Growatt · ShineServerWATCH · API LAGCheck
03 · Beyond disbursement
Connect once. Keep the operating record working after the claim.
The same operating record can support monitoring, incident response, field work and performance review after a programme claim. Start from supported equipment and retain the programme platform and its formal review process.
Separately, preparation workflows for NERC 2026 operational and commercial reporting, loss evidence and interconnected settlement are distinct from programme reporting and from the Odyssey workflow. Review what each one needs and what still requires human review →
Claim readiness
Fleet operations
Field evidence
Portfolio review
Onboarding sequence · not a CLI or timed resultCONNECT
01→Review the site, vendor account and authorised access
02→Configure the supported adapter and equipment mapping
03→Identify expected signals and cadence
04→Commission local buffering if an edge node is needed
05→Inspect received telemetry, freshness and both coverage axes
06→Review evidence gaps before relying on a report
04 · The evidence
The basis for your review.
Site-specific
Review the applicable programme requirements before relying on automated milestone status.
Programme reviewQuality-gated
Automatic submission requires enablement and sufficient coverage; synthetic telemetry is excluded.
Submission controlsOdyssey
Gen318 prepares operator-side evidence; the programme submission and decision remain outside Gen318.
Complementary workflowFinalised
Finalisation preserves report content. It does not independently certify the underlying evidence.
Record integrityReview the evidence path across your DARES sites.
Start with the telemetry, connections, evidence gaps, and milestones your compliance team already manages.