A conceptual model of disasters encompassing multiple stakeholder domains Online publication date: Fri, 15-Aug-2008
by Philippe Kruchten, Carson Woo, Kafui Monu, Mandana Sotoodeh
International Journal of Emergency Management (IJEM), Vol. 5, No. 1/2, 2008
Abstract: Understanding the interdependencies of critical infrastructures (power, transport, communication, etc.) is essential in emergency preparedness and response in the face of disasters. Unfortunately, many factors (e.g., the unwillingness to disclose or share critical data) prohibited the complete development of such an understanding. As an alternative solution, this paper presents a conceptual model – an ontology – of disasters affecting critical infrastructures. We bring humans into the loop and distinguish between the physical and social interdependencies between infrastructures, where the social layer deals with communication and coordination among the representatives (either humans or intelligent agents) of the various critical infrastructures. We validated our conceptual model with the people responsible for disaster management from several different critical infrastructures and through a case study. We also derived tools from the model to provide decision support. We expect that this conceptual model can later be used by people as a common language to communicate, analyse and simulate their interdependencies without having to disclose all critical and confidential data.
Online publication date: Fri, 15-Aug-2008
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of Emergency Management (IJEM):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable). See our Orders page to subscribe.
If you still need assistance, please email email@example.com