Integrating risk and resilience approaches to catastrophe management in engineering systems

<?xml version="1.0" encoding="UTF-8"?><modsCollection xmlns="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-8.xsd">
<mods version="3.8">
<titleInfo>
<title>Integrating risk and resilience approaches to catastrophe management in engineering systems</title>
</titleInfo>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">periodical</genre>
<originInfo>
<place>
<placeTerm type="code" authority="marccountry">esp</placeTerm>
</place>
<dateIssued encoding="marc">2013</dateIssued>
<issuance>serial</issuance>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</language>
<physicalDescription>
<form authority="marcform">print</form>
</physicalDescription>
<abstract displayLabel="Summary">Recent natural and man-made catastrophes, such as the Fukushima nuclear power plant, flooding caused by Hurricane Katrina, the Deepwater Horizon oil spill, the Haiti earthquake, and the mortgage derivatives crisis, have renewed interest in the concept of resilience, especially as it relates to complex systems vulnerable to multiple or cascading failures. Although the meaning of resilience is contested in different contexts, in general resilience is understood to mean the capacity to adapt to changing conditions without catastrophic loss of form or function. In the context of engineering systems, this has sometimes been interpreted as the probability that system conditions might exceed an irrevocable tipping point. However, we argue that this approach improperly conflates resilience and risk perspectives by expressing resilience exclusively in risk terms. In contrast, we describe resilience as an emergent property of what an engineering system does, rather than a static property the system has. Therefore, resilience cannot be measured at the systems scale solely from examination of component parts. Instead, resilience is better understood as the outcome of a recursive process that includes: sensing, anticipation, learning, and adaptation. In this approach, resilience analysis can be understood as differentiable from, but complementary to, risk analysis, with important implications for the adaptive management of complex, coupled engineering systems. Management of the 2011 flooding in the Mississippi River Basin is discussed as an example of the successes and challenges of resilience-based management of complex natural systems that have been extensively altered by engineered structures.</abstract>
<note type="statement of responsibility">J. Park...[et.al]</note>
<note/>
<subject authority="lcshac" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080591182">
<topic>Gerencia de riesgos</topic>
</subject>
<subject authority="lcshac" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20110022860">
<topic>Ingeniería de la resiliencia</topic>
</subject>
<subject authority="lcshac" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080557508">
<topic>Catástrofes</topic>
</subject>
<subject authority="lcshac" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080626433">
<topic>Sistemas de gestión integrados</topic>
</subject>
<classification authority="">7</classification>
<relatedItem type="host">
<titleInfo>
<title>Risk analysis : an international journal</title>
</titleInfo>
<originInfo>
<publisher>McLean, Virginia : Society for Risk Analysis, 1987-2015</publisher>
</originInfo>
<identifier type="issn">0272-4332</identifier>
<identifier type="local">MAP20077000345</identifier>
<part>
<text>04/03/2013 Volumen 33 Número 3  - marzo 2013 , p. 356-367</text>
</part>
</relatedItem>
<recordInfo>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">130510</recordCreationDate>
<recordChangeDate encoding="iso8601">20130524105136.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20130014692</recordIdentifier>
<languageOfCataloging>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</languageOfCataloging>
</recordInfo>
</mods>
</modsCollection>