Resilience principles for engineered systems
Scott Jackson and
Timothy L. J. Ferris
Systems Engineering, 2013, vol. 16, issue 2, 152-164
Abstract:
This paper examines a set of abstract, top‐level principles and subprinciples collected from the literature to determine their usefulness in enabling the avoidance, survival, and recovery from disruptions caused by threats of various sources. The principles are compared to concrete solutions recommended by domain experts in various case studies and to the actual events in those case studies. Also examined are the limitations, conflicts, and vulnerabilities that may be apparent when concrete solutions are created from these principles. The systems considered are physical, organizational, and procedural systems. Examples include cases from fire protection, aviation, railways, and power distribution domains. Threats examined include terrorist attacks, natural disasters, and human and design error. Each principle is found to apply to different phases of the disruption cycle surrounding an encounter with a threat. It is found that principles, in general, cannot be applied singly to a system but must be combined with other principles to enable resilience. System developers in various domains can use the principles to create concrete solutions to characterize a particular system, model that solution, and determine the degree of recovery of the system from a specified threat. ©2012 Wiley Periodicals, Inc. Syst Eng 16
Date: 2013
References: View complete reference list from CitEc
Citations: View citations in EconPapers (4)
Downloads: (external link)
https://doi.org/10.1002/sys.21228
Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.
Export reference: BibTeX
RIS (EndNote, ProCite, RefMan)
HTML/Text
Persistent link: https://EconPapers.repec.org/RePEc:wly:syseng:v:16:y:2013:i:2:p:152-164
Access Statistics for this article
More articles in Systems Engineering from John Wiley & Sons
Bibliographic data for series maintained by Wiley Content Delivery ().