Business use cases#

Start with a decision, inspect a worked example, then qualify your own inputs. Energy Data Insights connects source acquisition, reusable scientific methods and reproducible analysis. Its outputs can support investigation, comparison and scenario planning; their stated assumptions determine what can be concluded.

The repository welcomes public review and contributions. The existing license allows noncommercial use; internal business use, paid services and commercial products require separate written permission. See About, evidence and licensing and contact ASVA Consulting to discuss permission.

Choose a decision and an output#

From business question to reproducible evidence#

Business question

Starting inputs

Reviewable output

Start here

Which markets and projects deserve further research?

Dated project/equipment records and field-level sources

Coverage maps, capacity-basis comparisons and missing-data checks

Project databases

Where should an asset team investigate performance?

Qualified generation, weather and site metadata

Actual-versus-expected energy, coverage and operational screens

Fleet dashboard quickstart

Which forecast is useful at the required horizon?

Time-aligned observations, forecast origins and held-out periods

Baseline-relative error, uncertainty and model comparisons

Forecasting examples

How could climate affect yield and asset life?

Weather/climate grids, site measurements and explicit calibration

Exposure maps, degradation scenarios and lifetime sensitivity

Climate and degradation

What maintenance evidence is available?

Published failure records and qualified fleet histories

Updated rates, predictive intervals and repair/availability scenarios

Equipment reliability

What changes under a storage or investment scenario?

Explicit energy, cost, dispatch and financing assumptions

Scenario comparisons, constraints and sensitivity results

Hybrid dispatch

Project development and market research#

Use the PV, wind, BESS, hydro, gas and data-center viewers to inspect source evidence, dates, geographic coverage and unresolved fields. Compare equipment through the PV tables and BESS OEM viewer.

For BESS grid-access tender sizing, start with the Portugal storage auction guide and the runnable gallery case. Apparent-power connection rights are not installed battery MW.nnUse the claim-audit example to see how a reported project claim is checked against explicit benchmarks. Catalogue coverage is incomplete; historical/nameplate MW, current operating capacity, storage MWh and data-center IT load are different quantities.

Operations, forecasting and asset management#

Start with the synthetic fleet dashboard, then follow the analysis package guide to supply real measurements and preserve chronological validation. Compare models using the forecast benchmark.

The failure-prediction walkthrough shows the path from published evidence to a forecast using an explicitly synthetic fleet. The repowering example compares keep, repair and replacement scenarios using illustrative inputs. Neither screening states nor illustrative cash flows establish confirmed damage, recoverable losses or a project investment recommendation.

Climate risk, engineering and resilience#

Explore climate maps, soiling and snow exposure, and mechanism-specific Canary scenarios. The site-imagery examples produce reviewable inspection outputs with resolution and inventory limits.

For infrastructure scenarios, inspect offshore wind economics, grid resilience and hybrid dispatch. Read each scenario’s time basis, assumptions and exclusions before transferring the workflow to another asset or geography.

Take an example into your own workflow#

  1. Choose a business question and the measurable output needed to answer it.

  2. Reproduce the example with its supplied inputs and inspect the source evidence.

  3. Confirm access and usage rights for the software and each data source.

  4. Replace fixtures with qualified measurements; document units, dates and gaps.

  5. Validate on independent observations and review uncertainty and exclusions.

  6. Save configuration, source snapshots, checksums and the repository revision alongside the outputs so another reviewer can reproduce the conclusion.

Use Guides by task for detailed contracts, API reference for integration and Contribute and develop to contribute a connector, method, correction or new use case.