Skip to main content
Version: Next

How to access HCM results

Where results are written​

Each work package writes results to the destination set by writerType in the Result Processor Config:

Inputs such as scenario_configuration, the value tables and intervention_candidates are in the input schema. See Input Tables and Output Tables.

Database access, credentials and the supported writer types depend on your deployment. Contact your administrator or Zepben.

Which tables are written​

Most tables, including network_performance_metrics_enhanced, are written for every work package. Others are only written when enabled in the config, for example duration_curves (populateDurationCurves) and the asset level summaries (assetLevelSummaries). Intrinsic and HV node headroom work packages write the Intrinsic Hosting Capacity tables.

Querying results​

  • Filter on work_package_id, the ID returned when the work package was submitted. All work packages share the same tables.
  • Start with the whole-year rows (season = 'yearly', time_of_day = 'all').
  • Use link_to_input for the forecast year. timestamp is in UTC.
  • Check the rules for adding metrics across zones before summing.

To compare two work packages, see How to evaluate an intervention's impact.

-- Example: total value at risk per feeder, whole year, summed across transformer zones
SELECT scenario,
       feeder,
       timestamp,
       SUM(load_exceeding_normal_thermal_voltage_vcr
         + gen_exceeding_normal_thermal_voltage_cecv
         + COALESCE(gen_exceeding_normal_thermal_voltage_co2, 0)) AS total_value_at_risk
FROM network_performance_metrics_enhanced
WHERE work_package_id = 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'
  AND season = 'yearly'
  AND time_of_day = 'all'
  AND mz_type = 'TRANSFORMER'
GROUP BY scenario, feeder, timestamp
ORDER BY total_value_at_risk DESC;

See Value at Risk for what these metrics mean.