Dataset Factory★ EST. 2026 · BEST AT 800×600 ★
★ WELCOME TO THE DATASET FACTORY ★ PUBLIC DATA → CHECKED BUILDS → HONEST BASELINES ★ NO POP-UPS ★ NO COOKIES ★ NO TRACKERS ★ HAND-MADE HTML ★ UNDER CONSTRUCTION SINCE THE NINETIES ★
Release notes · 2026-11-13 · announcement

EIA861 Reliability Deterioration

Suitability and evaluation

Evaluation setting: retrospective research. Read the prediction setting and limitations below. Public validation is development data; downloadable holdout labels must stay outside the evaluated agent workspace.

Given three years of published distribution-reliability history and utility attributes, will a U.S. electric distribution utility's day-to-day outage duration (SAIDI excluding major event days) jump by at least 50% above its own recent norm in the next calendar year?

Population: U.S. electric distribution utilities identified by EIA utility number that report a non-missing SAIDI excluding major event days in CY Y-3, Y-2 and Y-1 under one consistent reporting standard, report at least 1,000 customers in CY Y-1, carry an ownership code among investor-owned, municipal, cooperative, political subdivision, federal or state, appear with exactly one reliability record in each of those years, and report a SAIDI excluding major event days for CY Y+1. Utilities filing multiple state rows or changing utility number are dropped for that cohort. Missing CY Y+1 outcomes are dropped, never coded negative. No CY Y or later value enters features.

Target: Binary y=1 if the utility's reported SAIDI excluding major event days for calendar year Y+1 is greater than or equal to 1.5 times the median of its three reported SAIDI-excluding-major-event-day values for CY Y-3, Y-2 and Y-1; y=0 otherwise. Utilities with a missing CY Y+1 SAIDI-excluding-MED value are dropped, never coded 0.

Prediction time: 31 December of forecast year Y, using only Form EIA-861 reliability and utility attribute filings for calendar years Y-3, Y-2 and Y-1. Exact historical publication dates are assumed rather than verified. No CY Y or later value enters features.

Splits: Cohorts are forecast years Y = 2016, 2017, ..., 2024 (labels in CY 2017 ... 2025). Fixed chronological boundaries: train = Y 2016-2019, eval = Y 2020-2021, holdout = Y 2022-2024. No random reassignment and no re-splitting after measurement. Purge rule enforced in code: every feature year is <= Y-1, so the newest training feature year is 2018 while the earliest scored label year is 2021; therefore no training row's feature vector contains a year used to compute any eval or holdout label. Rows whose four-year window (Y-3 ... Y+1) spans a utility-number change or a change of reporting standard are dropped rather than carried across splits.

Outcome horizon: Calendar year Y+1, i.e. the twelve months beginning immediately after the decision instant; the outcome is observed when the CY Y+1 EIA-861 reliability file is published (roughly 9-12 months later).

Inputs: saidi_nomed_lag1: SAIDI excluding major event days for CY Y-1: minutes of non-momentary interruption the average customer experienced.; saidi_nomed_lag2: SAIDI excluding major event days for CY Y-2.; saidi_nomed_lag3: SAIDI excluding major event days for CY Y-3.; saidi_nomed_trend: Ratio of lag1 minus lag3 to lag3, a three-year level trend in non-storm outage duration. Missing when lag3 is zero; no interpolation.; saidi_with_med_lag1: SAIDI including major event days for CY Y-1, showing how much recent duration came from storm-scale days.; saifi_nomed_lag1: SAIFI excluding major event days for CY Y-1: non-momentary interruptions per customer-year.; saifi_with_med_lag1: SAIFI including major event days for CY Y-1.; caidi_nomed_lag1: CAIDI excluding major event days for CY Y-1: average minutes to restore an interruption. Derived from SAIDI divided by SAIFI when the reported CAIDI is absent and SAIFI is positive.; customers_lag1: Customer or meter count reported with the CY Y-1 Reliability schedule, used as a scale control.; reporting_standard: Whether the utility reported under IEEE 1366 or an internally defined other method in CY Y-1, normalized to IEEE or OTHER. A utility must carry one consistent value across the four filings used by a cohort.; ownership_code: Utility ownership type among investor-owned, municipal, cooperative, political subdivision, federal or state, from the CY Y-1 Reliability filing or the annual utility data file.; state: Utility reported state, used for calendar and regulatory-regime controls.

→ Open the dataset page for numbers, files and checksums

★ THANKS FOR VISITING · BOOKMARK THIS PAGE · TELL A FRIEND ABOUT THE DATASET FACTORY · SIGN THE GUESTBOOK BEFORE YOU LEAVE ★