Skip to main content

InfraRisk Index and red flags

Purpose​

The InfraRisk Index gives one score for selected risks of an asset, so that you can rank assets. The benchmark percentile ranks that score in a cohort. Red flags show specific issues that the active rules find.

Inputs: five risk families​

FamilyWhat it covers
Natural HazardsExpected and severe physical-damage losses.
EnvironmentalHabitat and floodplain constraints.
BuildabilityLand, soil and slope constraints.
InterconnectionTransmission connection cost and distance estimates.
Revenue RiskYear-to-year revenue variation.

Method​

  1. Each family gets a score.
  2. A risk profile sets the weight of each family. The weighted scores give the index, from 0 to 100.
  3. The benchmark percentile compares the index with the selected cohort: Continental US or ISO Region.
  4. Separately, the active red-flag rules check for specific issues.

For the weights of each profile and the list of red-flag rules, see Risk profiles and red flags.

Outputs​

Index score (0–100)​

A lower score means lower modeled risk under the selected weights.

Benchmark percentile (0–100)​

A higher percentile means higher risk than the cohort. For example, the 90th percentile means a higher score than about nine in ten assets in the cohort. The score and the percentile are different quantities.

Red flags​

Red flags are separate from the weighted score. Active pass-or-fail rules flag issues such as extreme hail tail loss or critical habitat. Red flags stay visible even when the weighted score is moderate.

Assumptions​

  • A weight of zero removes a family from the score. It does not mean that the risk is absent.
  • Each profile activates a different set of red-flag rules.

Limitations​

  • The score is not a loss probability.
  • Compare scores only with the same profile and cohort.
  • A red-flag count of zero does not mean that every possible issue was checked. Check which rules are active.

For all limitations, see Limitations.

Validation​

Version​

Applies to methodology version 1.0, September 2026.