Cascading failure in electric power systems is a complicated problem for which a variety of models, software tools, and analytical tools have been proposed but are difficult to verify. Benchmarking and validation are necessary to understand how closely a particular modeling method corresponds to reality, what engineering conclusions may be drawn from a particular tool, and what improvements need to be made to the tool in order to reach valid conclusions. The community needs to develop the test cases tailored to cascading that are central to practical benchmarking and validation. In this paper, the IEEE PES working group on cascading failure reviews and synthesizes how benchmarking and validation can be done for cascading failure analysis, summarizes and reviews the cascading test cases that are available to the international community, and makes recommendations for improving the state of the art.

We address the problem of increasing the impact of formal methods in the practice of industrial computer applications. We summarize the reasons why formal methods so far did not gain widespread use within the industrial environment despite several promising experiences. We suggest an evolutionary rather than revolutionary attitude in the introduction of formal methods in the practice of industrial applications and we report on our long-standing experience which involves an academic institution, Politecnico di Milano, two main industrial partners, ENEL and CISE, and occasionally a few other industries. Our approach aims at augmenting an existing and fairly deeply rooted informal industrial methodology with our original formalism, the logic specification language TRIO. On the basis of the experiences we gained we argue that our incremental attitude towards the introduction of formal methods within the industry could be effective largely independently from the chosen formalism.

In-depth security analyses of power systems (PSs) require to consider the vulnerabilities to natural and human-related threats, which may cause multiple dependent contingencies. On the other hand, such events often lead to high impact on the system, so that decision-making aimed to enhance security may become difficult. Introducing the uncertainty, the risk associated to each contingency can be evaluated, thus allowing to perform effective contingency ranking. This paper describes an in-depth security assessment methodology, based on an ``extended'' definition of risk (including threats, vulnerability, contingency, and impact) aimed to perform the risk assessment of the integrated power and Information and Communication Technology (ICT) systems. The results of the application to test cases and realistic PSs show the added value of the proposed approach with respect to conventional security analyses in dealing with uncertainty of threats, vulnerabilities, and system response

Various methodologies exist for assessing the risk of cascading outage in power systems, differing in the cascading mechanisms considered and in the way they are modeled. These methodologies can be classified in three groups: static computation (QSS methodologies), dynamic computation (dynamic methodologies), or a combination of both (hybrid methodologies). The objective of this paper is to benchmark the performance of several widely used QSS cascading outage methodologies. For that purpose, they are applied on a unique system, the RTS-96, and the results are compared. Several metrics and indicators are used for that comparison: expected demand loss, distribution of demand loss, distribution of lines outaged and critical lines. Results show common trends but also discrepancies between methodologies. It implies that there is not yet a standardized way to analyze the risk of cascading outage in power systems, and that the specific tool used by a power system engineer can impact the recommendations. KeywordsCascading outage, Blackout, Power system security, Power system reliability, Risk analysis RightsPersonal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works. Authors

Formal methods have proved to be highly beneficial in the requirements specification phase of software production and are particularly valuable in the development of real-time applications (the most critical software systems). Unfortunately, most common specification languages are inadequate for real-time applications because they lack a quantitative representation of time. In this paper, we define a logical language to specify the temporal constraints of the wide-ranging class of real-time systems whose components have dynamic behaviours regulated by very different time constants. We motivate the need for allowing the consistent treatment of different time scales in formal specifications of these systems with the purpose of enhancing the naturalness and practical usability of the notation. The logical specification language is based on a revised version of the specification language TRIO. We first present the features of the basic logical language; then, we semantically and axiomatically define its granularity extension in a topological logic framework. Finally, we show some examples of its application