Search

This document is the final report of T6.6 Legacy systems. D6.9 contains the final updates on the collected information, properties and characteristics, as well as taxonomy approaches of the chosen legacy systems. EU legacy systems, such as PAGER, have been used in the project and more specifically in the use cases where the emergency was an earthquake. In addition, valuable knowledge coming from another legacy system (e.g SUMMA’s medical service) were extracted, in order to design and implement COncORDE’s patient management system & triage. D6.9 lists the final legacy systems and analyze their usage during SnR Operations (Use Cases - Pilot Scenarios).

The current document demonstrates the second version of the Technical implementation of SOT DSS. More specifically, it reports the additions in each Service that have been implemented, the process of the back-end requests for the necessary data, the back-end responses of SOT DSS, and the SOT DSS responses in COncORDE’s SOT DSS screen. Additionally, the present document shows the Use Cases that the DSS that will be tested and which Services per Use Case. Moreover, the SOT DSS dependencies of data from the other components and actors are presented. The document is structured as follows: Section 1 presents the scope of SOT DSS (Technical level) and the related Deliverables. Section 2 shows the additions in each Service, the back-end and front-end process. Finally, Section 3 describes the Use Cases in which the SOT DSS and its Services will be tested and the dependencies in order for SOT DSS to work properly.

This current document is produced in the scope of WP6’s D6.6 “Report on legacy systems and their connection to the S&R related technical characteristics”. The aim of this deliverable is to collect information, properties, and characteristics related to the Legacy Systems, as well as to find databases and retrieve Legacy Data. The collection of this information was implemented by sending questionnaires to international and global first responder organisations as well as at the end-users of the S&R. Furthermore, research regarding the existing EU Legacy Systems for crisis management has been implemented and information about CECIS, GDACS, and PAGER platforms has been collected. As a part of data collection PAGER’S public API has been utilised to retrieve and extract historical data. The data collected concern earthquake incidents and their magnitude, the date, the consequences (tsunami), and the location where they took place. More specifically, the first section of the current document presents general information about Legacy Systems as well as their usage in crisis management. The second part analyzes the overall approach of the procedure and develops an extensive analysis of the aforementioned EU Legacy System. The fourth section describes the process of collection, filtering, and integration of legacy data that have been collected from the PAGER API and their interaction with other components of the platform. It describes from a technical perspective the progressive procedure of legacy data via PAGER public API, the storage in the Data Lake Ecosystem, and hereinafter the transformation to Python objects according to the object-oriented model. In conclusion, after the mapping according to the SnR data model, the rest of the components can fetch and use the data appropriately through the WebHDFS tool.

The current document reports the development of the mechanism responsible for assisting the end-user in decision support by providing a set of recommendations based on the current status of the system under study and by implementing a SOT DSS engine. The stream, historical, and legacy data, originating from sensors, web services, and other relational databases, constitute the main source of information and inputs for the Decision Support Systems in S&R. The SOT DSS Engine uses Linear Programming techniques and produces recommendations by combining all the above types of data. D4.5 “Development of SOT DSS components” follows the design of D4.3 “Design of DSS components” in order to develop an efficient Decision Support System. In the second version of this deliverable, the technical implementation details of the extensions of the SOT DSS will be presented. Service 1 to 4 will be improved and be adapted to the ongoing changes of the needs of the S&R project.

This document aims to identify and design the SOT decision support tool. This DSS module will be used in the S&R operations for real-time resource allocation following the strategic, operational, and tactical level of decision making in crisis situations.The DSS component is designed in order to address the following services: • Recommended (optimal) allocation of available EMS units to incidents, depending on estimated needs • Recommended (optimal) allocation of patients to transport vehicles and first receivers (hospitals), based on given order of evacuation and triage results for present injuries • Recommended (optimal) allocation of tasks to available actors on the field, given demand pre-defined by the field commander. • Estimation of expected casualties and demanded resources (EMS units), given historical data on emergency incident recordings As an outcome, “D4.3 Design of SOT DSS components” provides: • The design specifications of the Decision Support System in strategic, operational and tactical levels • The services of DSS and the implementation methodology • The overall technical approach for the design of SOT DSS services A second attempt will be held in “D4.9 Design of SOT DSS component, V2” at M22, in order to enhance and fulfil the design of the SOT DSS component that will guarantee the smooth management of resources in a real crisis situation and help the First Responders to make fast and accurate decisions during the disaster responses.

This deliverable is produced in the scope of WP3’s D3.7 “Requirements to Situation Awareness and SA Model v.2”. D3.7 describes methods for finding the necessary knowledge for first responders in order to achieve a level of situation awareness and to develop disaster emergencies. Situation Awareness (SA) is the accuracy with which people perceive, recognize and anticipate modifications in their environment that are relevant to achieving operational goals. Initially, in order to capture, develop, share and use organizational knowledge to finally enable SA, a Knowledge Management System is required. The Knowledge Management System requires components, both human and hardware, that must follow a variety of operational goals (time of response, time of deployment, rescue victims etc.). The goal of the deliverable, is the further extension of requirements to D3.1, the definition of the requirements of the Knowledge Management functionality in order to enable the situation awareness, a more efficient context-aware data sharing and presentation to the emergency responding actors, and subsequently more efficient decision-making support. The requirements to be collected should address different aspects of the S&R system functionality such as: knowledge models and information elements required to represent various types of resources used in S&R operations the support required for various types of decision making and decision points during S&R operations the requirements to the overall knowledge management infrastructure to support the achieving of situation awareness. These needs will support the risk awareness in decision-making, related to both victims as well as staff on the field.