Anne Marie Barthe, Matthieu Lauras, & Frédérick Benaben. (2011). Improving the design of interoperable platform through a structured case study description approach: Application to a nuclear crisis. In E. Portela L. S. M.A. Santos (Ed.), 8th International Conference on Information Systems for Crisis Response and Management: From Early-Warning Systems to Preparedness and Training, ISCRAM 2011. Lisbon: Information Systems for Crisis Response and Management, ISCRAM.
Abstract: In this article, we briefly describe a crisis management case that has been chosen (in the European funded project PLAY) to test the federated-open-trusted platform for event-driven interaction between services. A description of such complex use case in natural language is obviously limited and should be completed with a formal description methodology to gather the necessary knowledge. Considering our technical requirements we suggest to combine the S-Cube approach with the model driven architecture approach to propose a complete and structured case study description framework. Then this article presents a nuclear crisis case modeled according to these guidelines.
|
Claudio Arbib, Davide Arcelli, Julie Dugdale, Mahyar Tourchi Moghaddam, & Henry Muccini. (2019). Real-time Emergency Response through Performant IoT Architectures. In Z. Franco, J. J. González, & J. H. Canós (Eds.), Proceedings of the 16th International Conference on Information Systems for Crisis Response And Management. Valencia, Spain: Iscram.
Abstract: This paper describes the design of an Internet of Things (IoT) system for building evacuation. There are two main
design decisions for such systems: i) specifying the platform on which the IoT intelligent components should be
located; and ii) establishing the level of collaboration among the components. For safety-critical systems, such as
evacuation, real-time performance and evacuation time are critical. The approach aims to minimize computational
and evacuation delays and uses Queuing Network (QN) models. The approach was tested, by computer simulation,
on a real exhibition venue in Alan Turing Building, Italy, that has 34 sets of IoT sensors and actuators. Experiments
were performed that tested the effect of segmenting the physical space into different sized virtual cubes. Experiments
were also conducted concerning the distribution of the software architecture. The results show that using centralized
architectural pattern with a segmentation of the space into large cubes is the only feasible solution.
|
Therese Friberg, Benedikt Birkhäuser, Jens Pottebaum, & Rainer Koch. (2010). Using scenarios for the identification of real-world events in an event-based system. In C. Zobel B. T. S. French (Ed.), ISCRAM 2010 – 7th International Conference on Information Systems for Crisis Response and Management: Defining Crisis Management 3.0, Proceedings. Seattle, WA: Information Systems for Crisis Response and Management, ISCRAM.
Abstract: This work focuses on the requirements engineering process of an event-based system in the domain of emergency management. The goal is to identify events which occur and have an effect on the actions and decision making during an operation. We outline a case study to apply scenario-based requirements engineering processes to describe and identify events. Under the special circumstances of the case study one important result is the need of integrating multiple sources into the scenario generation activities due to the singular characteristics of many operations.
|
Tim J. Grant. (2008). Checklist for comparing emergency management information systems. In B. V. de W. F. Fiedrich (Ed.), Proceedings of ISCRAM 2008 – 5th International Conference on Information Systems for Crisis Response and Management (pp. 752–763). Washington, DC: Information Systems for Crisis Response and Management, ISCRAM.
Abstract: This paper describes a checklist that has been developed for comparing the functionality of emergency management control centres and their information systems. The intention is to interest the ISCRAM community in using the checklist in various applications and pooling experiences. The Control Centre Visit Checklist has evolved through four iterations. It has been used to study two military C2 systems and one non-military control system, and has been applied by students for course assignments. The paper focuses on the part of the checklist that evaluates the information system from the systems viewpoint. It describes the underlying applications architecture and process model. The Royal Netherlands Army's Battlefield Management System illustrates the application of the checklist. The results show that the checklist aids in identifying where C2 systems can be developed further. The next step is to perform a set of substantial pilot studies for diverse domains, including civilian emergency management systems.
|
