<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="client.xsl" type="text/xsl"?>
<article article-type="other">
<front>
<journal-meta>
<journal-id/>
<issn/>
<banner>
<href>banner.jpg</href>
<size width="100%"/>
</banner>
</journal-meta>
<doi>072-cd</doi>
<article-meta>
<title-group>
<article-title>Risk Register Database to Improve Organizational Resilience and Knowledge Management</article-title>
</title-group>

<author>Arto Niemi<sup>a</sup>, Tobias H&#246;bbel and Frank Sill Torres  </author>

<aff>Department for Resilience of Maritime Systems, Institute for the Protection of Maritime Infrastructures, German Aerospace Center (DLR), Germany. </aff>

<email><a href="mailto:arto.niemi@dlr.de "><sup>a</sup>arto.niemi@dlr.de </a></email>

</article-meta></front>
<body>
<abstract>
<title>ABSTRACT</title>
<p>Risk monitoring is a fundamental part of risk management that allows detecting changes that might affect the risk consequences and their likelihood. To be effective, the process requires storing the risk information into a so-called risk register. This paper presents an implementation that is realized in form of a relational database. We present the complete table schema of the database and discuss what motivated the different features. We believe that certain aspects of our schema improve its application in comparison to related works. A noteworthy characteristic is the separation of the risk scenarios and risk analyses in different tables. This feature relates to the fact that the same scenario can be assessed within multiple analyses, in which individual circumstances may result in different risk levels. Moreover, different analyses can apply distinct risk criteria. Thus, the analysis-specific criterion must be stored in the database as a risk matrix. A risk scenario includes an entity or item that is the subject being considered in that scenario. This subject can be a system or organization or a subpart of a system or organization. Due to this reason, the schema allows a hierarchical categorization of entities. The developed schema also employs ideas from the object-oriented programming approach, which allows entities to inherit already defined risk scenarios. This paper further presents a browser based user interface to access the database.  </p><p><italic>Keywords: </italic>Risk register, Relational database, Table schema, Knowledge management, Web application. </p>
</abstract>
<fpdf>
<href>pdflogo.jpg</href>
<hpdf>072</hpdf>
</fpdf>
</body>
</article>
