<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Towards a unified approach of interoperability to facilitate the transfer from research to industry: application to crisis management</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sébastien Truptil</string-name>
          <email>sebastien.truptil@cea.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Philippe Limousin</string-name>
          <email>philippe.limousin@cea.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Louis-Pierre Bergé</string-name>
          <email>louis-pierre.berge@cea.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Radhouene</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Azzabi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hubert</string-name>
          <email>Hubert.dubois@cea.fr</email>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>CEA, CEA Tech Occitanie</institution>
          ,
          <addr-line>51 rue de l'innovation, 31670 Labège</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2020</year>
      </pub-date>
      <volume>31</volume>
      <fpage>0000</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>This paper presents the objectives of the Criz'Innov French project. This project aims to fill the gap from the research to the stakeholders of crisis management. This gap is essentially due to a lack of maturity and an interoperability issue for the results of R&amp;D projects. Therefore, this paper presents the software architecture of CrizLABTM, a middleware based on EventDriven Architecture that proposes a unified approach of interoperability and helps to use the results of R&amp;D projects in relevant situations in order to increase their maturity and thus facilitate the demonstrations.</p>
      </abstract>
      <kwd-group>
        <kwd>Crisis management</kwd>
        <kwd>interoperability</kwd>
        <kwd>Event-Driven Architecture</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>The news is full of major events leading to numerous damages and losses (deaths, destruction of
habitats...). Examples could be found both at the international level (Tsunami of 2011 leading to the
disaster in Fukushima: about 20,000 deaths, €60 billion ...), and at the national level (fire, explosion
and atmospheric emissions of the company SEVESO Lubrizol in 2019: 240 firefighters mobilized, 13
municipalities have set up a crisis unit ...) and at the regional level (floods in Occitania in 2019:
cumulative rainfall of up to 200 mm in less than 6 hours, about €100 million of damage ...).</p>
      <p>These situations, called "calamity", "incident" or "major event" depending on the context and
sources, occur in a vulnerable environment (areas with high human stakes, industrial activity zones,
interconnected networks, etc.) and evolve according to an unfavorable outcome called a crisis according
to [1].</p>
      <p>Crisis management aims at solving problems (e.g. reducing effects and preventing the occurrence of
risks) in order to return to a stable situation. Crisis management could be divided into four main steps:
Nondations (2018 / 2021), ACRIMAS (2011 / 2012), CRISMAS (2015 / 2017), DRIVER+ (2014 /
2020), I-REACT (2016 / 2019) or the research communities like ISCRAM.</p>
      <p>Based on this context, we assume that there is a leak from the results of R&amp;D projects to the
stakeholders of crisis management and industry.</p>
      <p>This paper presents the proposal of the Criz’Innov French project, which aims at facilitating the
transfer from the results of R&amp;D projects to their demonstration in a representative situation. The first
section tries to explain why it is difficult to directly use the results of R&amp;D projects in a representative
situation. The second section presents the objectives of the Criz’Innov project. Finally, the last section
introduces the architecture of the CrizLABTM the Middleware used to provide interoperability.</p>
    </sec>
    <sec id="sec-2">
      <title>2. . Towards a need to unified the perception of the crisis situation</title>
      <p>This section aims to explain the possible reason for the difficulties in transferring the results of R&amp;D
projects to the stakeholders of crisis management and industry.
2.1.</p>
    </sec>
    <sec id="sec-3">
      <title>Needs to increase the maturity level of technologies</title>
      <p>Technological Readiness Level (TRL) is a framework that has been used to provide a measurement
of technology maturity from ideas on the paper to commercialization [2]. Regarding the computer
science field, the framework TRL could be divided into three main stages:</p>
      <p>From 1 to 3: Proof of concept.</p>
      <p>From 4 to 6: from Proof of concept to demonstrator usable in representative situation.</p>
      <p>From 7 to 9: from demonstrator to commercialization.</p>
      <p>R&amp;D activities are focused on Proof of Concept level whereas industries are interesting in
technology from the demonstrator level. Therefore, one reason for the difficulty to transfer R&amp;D results
to the industry is due to the maturity level. Based on this observation, we want to offer a solution able
to facilitate the increase in maturity. The increase in maturity is linked to the use of technology in a
representative situation with other technologies.
2.2.</p>
    </sec>
    <sec id="sec-4">
      <title>Needs to unified the perception of the situation</title>
      <p>In crisis management, especially during the crisis response, the main concerns of stakeholders are
always to know what is going on. This is the aim of Situational Awareness. In [3], the authors remind
that even there are numerous definitions of Situational Awareness; Situational Awareness could be seen
The first level is to perceive the status, attributes, and dynamics of relevant elements in the






EMAIL: sebastien.truptil@cea.fr (A. 1); philippe.limousin@cea.fr (A. 2); louis-pierre.berge@cea.fr (A. 3), radhouene.azzabi@cea.fr (A. 4);
Hubert.dubois@cea.fr (A. 5).</p>
      <p>2020 Copyright for this paper by its authors.
in three levels:
environment</p>
      <p>Level 1: Perception of the situation.</p>
      <sec id="sec-4-1">
        <title>Level 2: Comprehension of the situation.</title>
      </sec>
      <sec id="sec-4-2">
        <title>Level 3: projection of future status.</title>
        <p>Based on level 1, this level aims to go beyond simply being aware of the elements that are present.
It aims to help decision-makers by making advice based on the treatment of knowledge.</p>
        <p>This level aims to project the future status of the elements in the environment or to predict the results
of actions in order to help the decision-makers.</p>
        <p>
          Regarding the results of R&amp;D projects in crisis management, we assume that the results are more
focused on the comprehension and the projection level of Situational Awareness. Moreover, each R&amp;D
result is focused on a specific aspect of crisis management or on specific kinds of crisis situations
(flooding, forest fire, …). Thus, there are numerous proposals to describe the perception of the situation
due to the fact that each project proposes is own perception model or ontology [4] [
          <xref ref-type="bibr" rid="ref1">5</xref>
          ] [6] [7] [8].
Furthermore, these proposals do not include or are not based on the standard established for crisis
management exchange as the ISO standard: CAP (Common Alerting Protocol) message [9] or the
EDXL (Emergency Data Exchange Language) [10].
        </p>
        <p>In conclusion, we can assume that a constellation of technologies is needed in crisis management
because one technology could not manage at the same time the whole possible situations and the three
levels of Situational Awareness. We assume also that a unified perception of the situation is needed to
facilitate the transfer from the results of R&amp;D projects to industry.
3. CrizLABTM: middleware to support a unified approach of interoperability for</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Crisis Management</title>
      <p>


data.</p>
      <p>It is obvious that digital solutions will be useful for crisis management due to the amount of data to
manage and share in a hurry. Thus lots of R&amp;D projects proposed solutions to help the stakeholders.
Nevertheless, as highlighted in previous sections, the transfer from the results of R&amp;D projects to
stakeholders is difficult due to mainly the maturity of the solutions and the lack of a unified perception
of the situation. This lack is due to the fact that a constellation of solutions is needed in crisis
management.</p>
      <p>Based on these observations, we want to propose a middleware, named CrizLABTM, which aims to
facilitate the transfer from the results of R&amp;D projects to stakeholders or industries. Therefore, the
middleware allows to:
tests the results in various crisis scenarios
facilitate the interactions between results and existing solutions in crisis cells
support for demonstration</p>
      <p>
        To achieve these objectives, CrizLABTM needs to be able to support a unified approach of
interoperability. As defined by [
        <xref ref-type="bibr" rid="ref2">11</xref>
        ], the unified approach of interoperability is based on a common
vocabulary, taxonomy. Thus, each result keeps its own way to structure the data and a gateway is used
to transform the exchanged data from the specific model to the unified and shared way to describe the
      </p>
      <p>Based on previous experiences, it seems that the unified approach of interoperability is relevant only
regarding the exchange of data between applications. Furthermore, crisis management is mainly based
on the occurrence of events. Therefore, CrizLABTM is based on EDA (Event-Driven Architecture),
illustrated in Figure 1. Indeed, event-driven systems or architectures are designed to process events as
they occur, allowing the system to observe, react dynamically, and issue personalized data depending
on the recipient and situation [12]</p>
      <sec id="sec-5-1">
        <title>Moreover, CrizLABTM proposes the following functionality:</title>
        <p></p>
        <p>Manage the COP (Common Operational Picture): COP is an overview of the situation,
generally showing on a map. This COP is modified on each received event.
EMAIL: sebastien.truptil@cea.fr (A. 1); philippe.limousin@cea.fr (A. 2); louis-pierre.berge@cea.fr (A. 3), radhouene.azzabi@cea.fr (A. 4);
Hubert.dubois@cea.fr (A. 5).</p>
        <p>2020 Copyright for this paper by its authors.



</p>
        <p>Manage the history of the situation: the history of the situation is saved and accessible for
humans as well as other applications.
order to make advice or provide an added value information</p>
        <p>Manage the link between applications. Several applications have to be executed in sequence in
In order to ensure these functionalities, the unified model used for CrizLABTM is based on three
taxonomies of events:</p>
        <p>Situational event: this kind of event is used to maintain the COP and share data between
stakeholders. At the moment, this kind of event is based on CAP message.</p>
        <p>Workflow event: this kind of event is used to manage the interaction between applications.</p>
        <p>Historical event: this kind of event is used to manage the history of the situation and thus the
history of the COP. Thanks to this kind of event, CrizLABTM could provide a “main courante” (in
French, it stand for a log of all the events and it is used after the crisis for return of experience).</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>4. Conclusion and Future works</title>
      <p>This paper presents the aims of the Criz’Innov French project. This project aims to fill the gap
between the research and the stakeholders of crisis management. This gap is mainly due to the maturity
level of the results of R&amp;D research whereas stakeholders want demonstrations to be convinced to use
the results. This observation implies a problem of interoperability. The aims of CrizLABTM is to provide
an Event-Driven Architecture that aims to support a unified approach of interoperability as well as
added-value services. The added value services are used to unify the perception of the situation and
thus facilitate the sharing of a COP.</p>
      <p>For the two next years, CrizLABTM is going to be used to demonstrate and increase the maturity
level of six research projects thanks to three crisis exercises: one simulate exercise and two real
exercises.</p>
    </sec>
    <sec id="sec-7">
      <title>5. References</title>
      <p>[1] E.S Devlin, Crisis management planning and execution, Auerbach Publications, 2006
[2] H. Nakamura, Y. Kajikawa, S. Suzuki, Multi-level perspectives with technology readiness
measures for aviation innovation, Sustainability science, 2013, vol. 8, no 1, pp. 87-101
[3] M. Lauras, S. Truptil, F. Bénaben, Towards a better management of complex emergencies through
crisis management meta‐modelling. Disasters, 2015, vol. 39, no 4, pp. 687-714
EMAIL: sebastien.truptil@cea.fr (A. 1); philippe.limousin@cea.fr (A. 2); louis-pierre.berge@cea.fr (A. 3), radhouene.azzabi@cea.fr (A. 4);
Hubert.dubois@cea.fr (A. 5).</p>
      <p>2020 Copyright for this paper by its authors.
[4] Y. Han, W. Xu, An ontology-oriented decision support system for emergency management based
on information fusion. In: Proceedings of the 1st ACM SIGSPATIAL International Workshop on
the Use of GIS in Emergency Management. 2015.</p>
      <p>metamodel-based knowledge sharing system for disaster
management. Expert Systems with Applications, 2016, vol. 63, pp. 49-65
resolution of episodic problems based on ontology and case bases reasoning: application to
terrorism attacks. In: 2017 IEEE/ACS 14th International Conference on Computer Systems and
Applications (AICCSA). IEEE, 2017. pp. 1502-1509.
management: case study of an Indonesia volcano eruption. International journal of disaster risk</p>
      <sec id="sec-7-1">
        <title>Common</title>
      </sec>
      <sec id="sec-7-2">
        <title>Alerting</title>
      </sec>
      <sec id="sec-7-3">
        <title>Protocol</title>
      </sec>
      <sec id="sec-7-4">
        <title>Version</title>
        <p>1.2,
2010.
URL:
️©</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>S. H.</given-names>
            <surname>Othman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Beydoun</surname>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          [6]
          <string-name>
            <given-names>S.</given-names>
            <surname>Bennani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Maalel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.B.</given-names>
            <surname>Ghézala</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Abed</surname>
          </string-name>
          ,
          <article-title>Towards a decision support model for the [9] OASIS, Emergency Data Exchange Language (EDXL) Distribution Element Version 2</article-title>
          .0,
          <year>2013</year>
          . URL: http://docs.oasis-open.org/emergency/edxl-de/
          <year>v2</year>
          .0/edxl-de-v2.
          <article-title>0</article-title>
          .html [10]
          <string-name>
            <given-names>D.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Doumeingts</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Vernadat</surname>
          </string-name>
          ,
          <article-title>Architectures for enterprise integration and interoperability: Past, present and future</article-title>
          . Computers in industry,
          <year>2008</year>
          , vol.
          <volume>59</volume>
          , no 7, p.
          <fpage>647</fpage>
          -
          <lpage>659</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>O.</given-names>
            <surname>Etzion</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Niblett</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Luckham</surname>
          </string-name>
          , Event processing in action.
          <source>Greenwich: Manning</source>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>