Deliverables
The functional exercise 2 aims to test and to validate the whole IOPES prototype B in a simulated, not hazardous scenario. The exercise took place in TCRH Mosbach (Germany). In this report we present the performance of the IOPES prototype B and we assess the degree of compliance provided by the IOPES system with the CPE needs in an emergency scenario; identify IOPES prototype B limitations and features to be improved in a new release of the system.
The functional exercise 1 aims to test and to validate the whole IOPES prototype A in a simulated, not hazardous scenario. The exercise took place in Catalonia (Spain), more precisely in CATUAV’s premises (Barcelona Drone Centre, Collsuspina). In this report we present the performance of the IOPES prototype A and we assess the degree of compliance provided by the IOPES system with the CPE needs in an emergency scenario; identify IOPES prototype A limitations and features to be improved in the IOPES prototype B.
This document is a quick user guide describing how to operate the IOPES system. Details about how to pilot an RPAS (Remotely Piloted Aircraft System) or how to be trained to do it are not included here, since such activities are scheduled to happen after the completion of the project.
This document sets the objectives of the functional exercise of the IOPES project, describes the exercise preparation design, and defines the evaluation strategy. Two functional exercises are planned to test and validate the innovative technologies developed in IOPES, one in Collsuspina (Spain), in May 2021, and another in Mosbach (Germany), in October 2021. Each exercise will be deployed as small-scale field emergency scenarios that will deploy a series of realistic emergency scenarios under controlled conditions. Finally, end-user feedback sessions will be conducted with all emergency services attending the exercise to validate and improve the IOPES technology.
This document describes the mechanism that must be used to exchange data between an IOPES wearable device and an EMS (Emergency Management System).
The task of the IOPES wearable devices is to compute the positions of their users in real-time, no matter they are indoors or outdoors. Additionally, the said position must be delivered to the EMS, so the members of the emergency teams may be always tracked by the staff managing the emergency.
Therefore, and besides the need of a communication channel to make possible the remote exchange of information – such as 3G, 4G or 5G –, it is necessary to describe how such information will be transmitted between the wearable device and the EMS and vice versa. That is, a protocol must be stated to avoid misunderstanding between these two endpoints and to
guarantee that information is correctly exchanged.
The task of this report is describing such protocol, implemented as a REST API (Application Programming Interface), protocol that any application – including the one driving the IOPES wearable device – must implement to make possible such communication with a target EMS.
