A review of restoration experience from historical blackouts and a decision support framework for parallel restoration with a case study
Bibliographic record
Abstract
A power system restoration after a blackout is expected within 8-12 hours, but historical data suggest that it can take up to several days in some occasions. While extensive research has focused on causes of blackouts, there has been insufficient attention on why restoration efforts taking longer time and what regulatory measures are taken during restoration planning. This review investigates ten notable blackouts during 2000-2024. The identified key issues include load coordination (24%), monitoring and control (24%), restoration plans (19%), and protection (14%). This review focuses on five steady state restoration issues including forming islands, black start capability, reactive power capability, over-voltage control and the block load pickup. The industry practice of system operators in the USA, Australia, Ireland and Canada and the restoration strategies based on network topology and blackout pre-conditions are reviewed considering over thirty industrial reports and seventy research papers. To address the restoration issues, a comprehensive decision support framework is proposed. Additionally, this framework is applied to a modified IEEE 9 bus and IEEE 39 bus test system. The restoration curve is developed, offering insights to visualize the gradual restoration of load over time. This review work underscores the need for continuous improvement in restoration guidelines, enhancing overall improvement in the restoration time. Further, how the framework can be modified for future grid with renewable based generation and the possible research directions are also proposed.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.004 | 0.009 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.007 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".