Research field: Science
Title: The design of a dynamic emergency response management information system
Abstract: ABSTRACT This paper systematically develops a set of general and supporting design principles and specifications for a "Dynamic Emergency Response Management Information System" (DERMIS) by identifying design premises resulting from the use of the "Emergency Management Information System and Reference Index" (EMISARI) and design concepts resulting from a comprehensive literature review. Implicit in crises of varying scopes and proportions are communication and information needs that can be addressed by today's information and communication technologies. However, what is required is organizing the premises and concepts that can be mapped into a set of generic design principles in turn providing a framework for the sensible development of flexible and dynamic Emergency Response Information Systems. A framework is presented for the system design and development that addresses the communication and information needs of first responders as well as the decision making needs of command and control personnel. The framework also incorporates thinking about the value of insights and information from communities of geographically dispersed experts and suggests how that expertise can be brought to bear on crisis decision making. Historic experience is used to suggest nine design premises. These premises are complemented by a series of five design concepts based upon the review of pertinent and applicable research. The result is a set of eight general design principles and three supporting design considerations that are recommended to be woven into the detailed specifications of a DERMIS. The resulting DERMIS design model graphically indicates the heuristic taken by this paper and suggests that the result will be an emergency response system flexible, robust, and dynamic enough to support the communication and information needs of emergency and crisis personnel on all levels. In addition it permits the development of dynamic emergency response information systems with tailored flexibility to support and be integrated across different sizes and types of organizations. This paper provides guidelines for system analysts and designers, system engineers, first responders, communities of experts, emergency command and control personnel, and MIS/IT researchers. SECTIONS 1. Introduction 2. Historical Insights about EMISARI 3. The emergency Response Atmosphere of OEP 4. Resulting Requirements for Emergency Response and Conceptual Design Specifics 4.1 Metaphors 4.2 Roles 4.3 Notifications 4.4 Context Visibility 4.5 Hypertext 5. Generalized Design Principles 6. Supporting Design Considerations 6.1 Resource Databases and Community Collaboration 6.2 Collective Memory 6.3 Online Communities of Experts 7. Conclusions and Final Observations 8. References 1. INTRODUCTION There have been, since 9/11, considerable efforts to propose improvements in the ability to respond to emergencies. However, the vast majority of these efforts have concentrated on infrastructure improvements to aid in mitigation of the impacts of either a man-made or natural disaster. In the area of communication and information systems to support the actual ongoing reaction to a disaster situation, the vast majority of the efforts have focused on the underlying technology to reliably support survivability of the underlying networks and physical facilities (Kunreuther and LernerLam 2002; Mork 2002). The fact that there were major failures of the basic technology and loss of the command center for 48 hours in the 9/11 event has made this an understandable result. The very workable commercial paging and digital mail systems supplied immediately afterwards by commercial firms (Michaels 2001; Vatis 2002) to the emergency response workers demonstrated that the correction of underlying technology is largely a process of setting integration standards and deciding to spend the necessary funds to update antiquated systems. …
Extracted statement — Emergency Management Phase: Response