Skip to main content
Version: Next

Using HCM Results

HCM results are structured around two ideas: that constraints should be described in terms of where they occur and how severe they are over time, and that uncertainty about the future is best handled by running multiple scenarios rather than a single forecast. This page explains how those ideas shape the result structure and what that means for how you use them.

How results are structured​

Measurement zones​

Results are organized by measurement zones - logical groupings of network assets running from key control points downstream to the next zone boundary. Zones never overlap, which means CECV and VCR value at risk metrics can be aggregated across the network without double-counting. For a full description, see Measurement Zones.

Constraint types​

The HCM tracks two categories of constraint: thermal (equipment operating beyond rated capacity - transformer overloads, conductor limits) and voltage (overvoltage from high solar generation, undervoltage from high load or long feeders, phase imbalance). Each constraint is tied to a specific measurement zone and carries temporal data showing when it occurs.

Network Performance Metrics Enhanced​

The main results table, network_performance_metrics_enhanced, has one row per measurement zone for each season and time of day, plus a whole-year row. Comparing hours and events outside limits with energy and peak metrics separates occasional edge cases from systematic problems: a constraint that appears for 10 hours a year at high magnitude is a different planning problem than one that appears for 200 hours at low magnitude, even if the peak severity is the same.

The optional duration_curves table (populateDurationCurves) gives each zone's power flow sorted into percentiles over the period.

Why scenarios matter for interpreting results​

A single HCM result is a snapshot of one possible future. Its value comes from comparison - against other scenarios, against a parent work package, against intervention alternatives.

Comparing scenarios reveals which measurement zones are sensitive to DER adoption assumptions. Zones with large differences between a high-DER and low-DER scenario are where planning uncertainty is greatest and where robust, flexible investment decisions matter most.

Diffing against a parent work package quantifies what changes when you add interventions or update the network model. Value at risk (CECV and VCR) differences at each zone show exactly how much constraint relief an intervention delivers, which makes cost-benefit comparisons objective rather than judgement-based. See How to evaluate an intervention's impact.

Model update validation is an often-overlooked use of diffs: when the network model is updated (corrected impedances, new assets, revised tap positions), diffing before and after confirms that changes are localised to expected areas and haven't introduced unintended constraint shifts elsewhere.

How HCM fits into the broader workflow​

HCM results are an input to other tools and processes, not a standalone output.

The Intervention Module takes parent work package results, identifies measurement zones exceeding constraint thresholds (candidate generation), deploys interventions to the highest-ranked candidates within yearly allocation limits, then re-runs work packages to measure effectiveness. Because the Intervention Module uses the same result framework as core HCM, before-and-after comparisons are direct.

The OpenDSS Exporter lets you export the OpenDSS model for a specific scenario, year and feeder for testing and debugging, such as inspecting how a flagged constraint arises. Exported models are not supported for stand-alone use; see OpenDSS Exporter.

The Feeder Load Analysis Tool works at a finer grain than HCM's measurement zones, revealing load distribution patterns and localized hot spots within a zone. Use HCM to identify which zones are constrained, then Feeder Load Analysis to understand what's driving it intra-zone.

Network model calibration compares a snapshot of modelled customer voltages with measured smart meter voltages to infer off-load tap positions and highlight impedance or connectivity errors. See Model Calibration Concepts. Results from a well-calibrated model carry more weight in connection assessments and regulatory submissions.

Validating results​

HCM results are only as reliable as the model and inputs behind them. Before acting on results:

  • Compare base year results against SCADA measurements at zone substations and AMI voltage data where available
  • Check that constraint locations and timing align with field experience - if a result surprises you, investigate rather than accept it
  • Review power flow convergence rates; feeders with low convergence reliability produce less trustworthy constraint data and may need model attention

Next Steps​