<!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 an Ontology-Driven Approach for Digital Twin Enabled Governed IT Management</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Henderik A. Proper</string-name>
          <email>e.proper@acm.org</email>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dominik Bork</string-name>
          <email>dominik.bork@tuwien.ac.at</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Geert Poels</string-name>
          <email>geert.poels@ugent.be</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Ghent University</institution>
          ,
          <addr-line>Ghent</addr-line>
          ,
          <country country="BE">Belgium</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Luxembourg Institute of Science and Technology</institution>
          ,
          <country country="LU">Luxembourg</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>TU Wien, Business Informatics Group</institution>
          ,
          <addr-line>Vienna</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>University of Luxembourg</institution>
          ,
          <country country="LU">Luxembourg</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The Digital Transformation of our society requires IT infrastructures to be more agile, more adaptive, and more connected than ever. At the same time, the owners of such infrastructures are confronted with an increase in regulatory pressure (e.g., the GDPR). These developments put a lot of stress on IT management and governance. To enable IT management and governance to better deal with these challenges, we propose to digitally transform IT governance and management itself by using a Digital Twin based approach. In line with this, we aim to create on ontology-driven Digital Twin for Governed IT Management (DT4GITM) framework. The goal of this framework is to act as a reference architecture for a Digital Twin based infrastructure that connects three interrelated systems: the IT governance processes, the governed IT management processes, and the managed organizational IT assets. The core of the framework involves a generic Governed IT Management (GITM) Domain Ontology, which is planned to be operationalized by a Knowledge Graph based approach that realizes an integrated view on the heterogenous data streams originating from the IT governance and management processes, and the managed IT assets. In this paper, we start by outlining the planned DT4GITM framework and the pivotal role of the GITM Domain Ontology within this. We then elaborate our incremental, and scenario-/case-driven strategy towards the development of the framework as a whole, and the GITM Domain Ontology in particular. This is followed by the elaboration of a speci c DT4GITM scenario which serves as a rst proof of principle.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>The Digital Transformation of our society puts extreme pressure on IT
infrastructures (i.e., the system of organizational IT assets ) and their associated
management processes. As a result, IT infrastructures need to be more agile,
more adaptive, and more connected than ever. At the same time, the owners of
Copyright © 2021 for this paper by its authors. Use permitted under Creative
Commons License Attribution 4.0 International (CC BY 4.0).
these infrastructures nd themselves confronted with an increase in regulatory
pressure (e.g., the GDPR).</p>
      <p>
        We conceptualize the IT governance and management system as being the
whole of interrelated organizational governance assets (i.e., organizational
structures, processes, and relational mechanisms [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]) that purposefully combines and
integrates three systems: (1) the organizational IT assets, (2) the associated
management processes, and (3) the IT governance processes, in order to ensure
strategic alignment, risk management, and compliance [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>To enable IT governance and management to better deal with these
challenges, we propose to digitally transform IT governance and management itself
by using a Digital Twin approach. We posit that such digitalization and the
related cultural/organizational change, make IT governance and management
more apt to address the challenges that come with digital transformation and
the corresponding changes to the organizational IT assets (e.g., IT sta ,
applications, data, infrastructure, processes, projects) and their management processes.
To this end, we are working towards the creation of an ontology-driven Digital
Twin for Governed IT Management (DT4GITM) framework, with a Governed
IT Management (GITM) Domain Ontology at its core.</p>
      <p>The goal of the resulting DT4GITM framework is to serve as a reference
architecture for a Digital Twin based infrastructure that connects the earlier
mentioned interrelated systems, involving the organizational IT assets, the
associated management processes, and the IT governance processes. When
applying this framework in a speci c organizational context, the framework, and the
generic GITM Domain Ontology in particular, will need to be specialized to the
organization-speci c context and priorities.</p>
      <p>
        In developing the GITM Domain Ontology, we will mainly draw on ITIL 4 [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]
and COBIT 2019 [
        <xref ref-type="bibr" rid="ref12 ref4">4, 12</xref>
        ]. Where needed, this will be complemented with concepts
from other relevant standards. We found that the performance indicators as
provided by COBIT, and even ITIL, are de ned rather `loosely' and/or at a highly
aggregated level. This makes it di cult to directly relate them to data streams
that can be used to `feed' the IT governance Digital Twin. This means that,
for the purposes of the DT4GITM framework, these indicators need to be
operationalized further, both in terms of concepts in the GITM Domain Ontology,
as well as in terms of how these indicators can be quali ed/quanti ed (which
ultimately de nes the Digital Twin parameters, i.e., the data to be gathered to
materialize the Digital Twin). As will be elaborated in Section 5, we therefore,
plan to follow an incremental and scenario-/case-driven strategy to develop the
DT4GITM framework (and associated reference implementation toolset).
      </p>
      <p>
        As mentioned before, the GITM Domain Ontology forms the core of the
DT4GITM framework. To operationalize this domain ontology, we plan to use
Knowledge Graphs [
        <xref ref-type="bibr" rid="ref6 ref7">6, 7</xref>
        ]. The use of Knowledge Graphs enables an integrated
view on the heterogenous data streams originating from the IT governance and
management processes, as well as the managed IT assets.
      </p>
      <p>In the remainder of this paper, we will start by outlining the proposed
DT4GITM framework in Section 2. In Section 3 we then zoom in on rst steps
towards the development of the GITM Domain Ontology, in particular in terms
of concept maps for the COBIT 2019 and ITIL 4 frameworks. Section 4 then
discusses in more detail the planned operationalization of the GITM Domain
Ontology in terms of a Knowledge Graph based approach. This is followed, in
Section 5, by a discussion on the incremental, and scenario-/case-driven strategy
we will follow towards the overall development (and validation) of the DT4GITM
framework in general, and the GITM Domain Ontology in particular. Before
concluding, Section 6 presents a rst example scenario of the use of a Digital Twin
in the context of Governed IT Management.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Outline of the DT4GITM framework</title>
      <p>
        To guide the development of Digital Twins as data-driven and smart IT
governance systems, we propose the DT4GITM framework (see Fig. 1). An
earlier, and more COBIT-speci c, version of this framework was included in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ].
The DT4GITM framework aims at providing a reference architecture for an IT
governance Digital Twin based infrastructure. DT4GITM de nes the di erent
components of such infrastructures in terms of their purpose, function, and
relationships with other components or the system's environment. The detailed
design and implementation of the components is subject of future research.
      </p>
      <p>To provide the mirroring function (also called twinning function), the Digital
Twin should be able to represent (i.e., to model) the organizational IT assets,
as well as their management and governance processes. A rst key question here
is \what " needs to be represented (i.e., what should be the model's contents).
At the core, this question is answered by an organization-speci c ontology for
IT governance, for which the DT4GITM framework provides a domain ontology
(i.e., GITM Domain Ontology in Fig. 1). This domain ontology is envisioned to
cover the entire governance system, as well as its evolution over time (within
the organization). As discussed above, the governance system includes: (1) the
system of organizational IT assets, (2) the associated management processes,
and (3) the governance processes,</p>
      <p>A second key question is \how " the relevant data and knowledge about
organizational IT assets and their management and governance processes (i.e.,
the twinning parameters) needs to be represented. Here, we propose the use of
Knowledge Graphs as they have the ability to integrate and uniformly
represent heterogeneous data. The GITM Knowledge Graph (see Fig. 1) provides a
reference how to consistently and uniformly represent all relevant data for IT
governance, including particularly data streams from IT Governance Processes,
IT Management Processes and Organizational IT Assets, which can be further
related to Other Data.</p>
      <p>The basis for the virtual processing function is the Digital Twin based
infrastructure that synchronizes the organization-speci c ontology and the
modeled organizational IT assets and their management and governance processes
(i.e., virtual processing is driven by the data captured in the Digital Twin's
Knowledge Graph). The operation of this function follows the Sense-Think-Act</p>
      <p>
        Fig. 1. The Digital Twin for Governed IT Management (DT4GITM) Framework
paradigm of Control Theory [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ] and requires apart from analytical/simulation
capabilities for monitoring and actuation, also visualization capabilities for
human interpretation (i.e., Workforce in Fig. 1). Knowledge Graph technologies
provide formalization capabilities for the machine processing of the twinning
parameters and other internal and external data, to realize these virtual processing
capabilities. The Digital Twin for GITM component provides a reference
architecture for developing Digital Twin based infrastructures that o er the necessary
functionalities for our envisioned solution.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Towards the GITM</title>
    </sec>
    <sec id="sec-4">
      <title>Domain Ontology</title>
      <p>
        A foundational element in the realization of an IT governance Digital Twin is the
GITM Domain Ontology, as it de nes more precisely what the virtual entity will
be concerned with, in terms of the concepts in the domain, their relationships
and properties, as well as possible constraints. In general, within the eld of
Applied Ontology, a domain ontology enables one to de ne what (can) exist(s)
in a given domain [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. As such, the GITM Domain Ontology de nes not only
what the IT governance Digital Twin will be concerned with, but also the data
that needs to be gathered to monitor the status and performance and to track the
evolution of the organizational IT assets and their management and governance
processes (i.e., the IT governance twinning parameters).
      </p>
      <p>The DT4GITM framework thus o ers a domain ontology as a conceptual
basis for developing organization-speci c ontologies for GITM. When developing
an IT governance Digital Twin in the context of a speci c organization, the
generic domain ontology will need to be situated to the speci c concerns of that
organization (e.g., privacy, security, costs). A design process that is driven by
the GITM Domain Ontology, ensures that relevant IT governance concepts, and
their properties, relationships and constraints, are accurately represented in the
organization-speci c ontology. This design process also involves de ning which
twinning parameters are relevant given the speci c IT governance concerns of
an organization.</p>
      <p>To operationalize our vision of DT4GITM as a reference architecture for
developing IT governance Digital Twins, the GITM Domain Ontology should at
least cover the concepts of the COBIT 2019 and ITIL 4 frameworks. This can
later be complemented with more speci c concepts from relevant other
standards.</p>
      <p>In moving towards a rst version of such a GITM Domain Ontology, we
already produced concept maps of the COBIT 2019 (see Section 3.1) and ITIL 4
(see Section 3.2) frameworks. First considerations of relating these two concept
maps are also presented in Section 3.3 whereas a formal integration is on our
agenda for future research. The concept maps use an informal way to graphically
distinguish concepts (blue rectangles with rounded corners), concept properties
(yellow circles), and concept instances (green squares).
3.1</p>
      <sec id="sec-4-1">
        <title>COBIT 2019 Concept Map</title>
        <p>
          There have been some proposals for describing the ontology underlying previous
versions of COBIT [
          <xref ref-type="bibr" rid="ref13 ref14 ref2 ref8">2, 8, 13, 14</xref>
          ]. However, to the best of our knowledge, an IT
governance domain ontology that includes the concepts of COBIT 2019 has not
been de ned yet. Since the conceptual model underlying COBIT 2019 has been
purposefully designed [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ], this conceptual model can be used as a starting point
for the development of the governance aspects of the GITM Domain Ontology.
        </p>
        <p>Fig. 2 shows a concept map containing the concepts of COBIT's main
guidance towards IT governance practitioners. Key concepts include:
Governance Components { Factors that, individually or collectively,
contribute to the good operations of the enterprise's governance system over
Information Technology (IT).</p>
      </sec>
      <sec id="sec-4-2">
        <title>Governance and Management Objective { An objective that should be</title>
        <p>achieved for IT to contribute positively to enterprise goals. The objective
is either a governance objective or a management objective. There are ve
governance objectives and 35 management objectives described in the
COBIT 2019 Core Model (i.e., the main focus area of the COBIT 2019
framework). Such an objective always relates to one process and a collection of
governance components of other types to help achieve the objective.</p>
      </sec>
      <sec id="sec-4-3">
        <title>Governance and Management Domain { Grouping of governance and man</title>
        <p>agement objectives for areas of governance or management activity. There
is one governance domain and there are four management domains.
Focus Area { A governance topic, domain or issue that can be addressed by a
collection of governance and management objectives and their components
(e.g., COBIT 2019 Core Model, cybersecurity, privacy, SMEs, and DevOps).
Processes { Describe an organized set of practices and activities to achieve
certain objectives and produce a set of outputs that support achievement of
overall IT-related goals.</p>
      </sec>
      <sec id="sec-4-4">
        <title>Governance and Management Practice { Grouping of activities, as part</title>
        <p>of a particular process, with metrics to measure achievement of the practice.
Activity { Work to be performed, as part of a governance or management
practice, at a certain capability level.
3.2</p>
      </sec>
      <sec id="sec-4-5">
        <title>ITIL 4 Concept Map</title>
        <p>
          To obtain a more complete description of organizational IT assets and their
management processes we will (as already hinted at in the introduction) primarily
draw on concepts from the ITIL 4 framework for IT service management [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ].
        </p>
        <p>
          Fig. 3 shows a concept map for the key concepts as identi ed in the ITIL
4 framework [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. This concept map will be used in the further development of
the IT management related aspects of the GITM Domain Ontology. The main
identi ed concepts are:
        </p>
      </sec>
      <sec id="sec-4-6">
        <title>IT Service Management (ITSM) Practice { A set of organizational resour</title>
        <p>ces designed for performing work or accomplishing an objective. There are 34
ITSM practices in the ITIL 4 framework: 14 general management practices,
17 service management practices, and three technical management practices.
Generic Value Chain Activity { Steps that an organization takes in the
creation of value. There are six generic value chain activities in ITIL 4: plan,
improve, engage, design and transition, obtain/build, deliver and support.
Guiding Principle { A recommendation that guides an organization in all
circumstances, regardless of changes in its goals, strategies, types of work,
or management structure.</p>
        <p>Value Stream { A speci c combination of value chain activities and practices,
designed for a speci c scenario, that describes a series of steps an
organization undertakes to create and deliver products and services to consumers.
Provides a complete guide to the activities, practices, and roles involved to
realize an intended outcome.</p>
        <p>
          As we will discuss in Section 5, we will follow a (real world) case-driven approach
in the development of the DT4GITM framework in general, and the GITM
Domain Ontology in particular. In doing so, we also plan to include (relevant
parts of) existing ontologies for ITIL (see e.g. [
          <xref ref-type="bibr" rid="ref19 ref5">19, 5</xref>
          ]).
3.3
        </p>
      </sec>
      <sec id="sec-4-7">
        <title>Relating COBIT 2019 and ITIL 4</title>
        <p>In developing the GITM Domain Ontology, it will be necessary to integrate/
align the concepts from ITIL 4 and COBIT 2019.</p>
        <p>When comparing the concept maps of COBIT 2019 and ITIL 4, we already
see that the guidance provided in an ITIL 4 Value Stream is comparable in
terms of purpose and granularity to the guidance provided in a COBIT 2019
Governance and Management Practice, making ITIL 4 Value Stream steps
similar to COBIT 2019 activities. The guidance provided in ITIL 4 is, however, more
detailed and more situation-speci c. For instance, ITIL 4 describes responsible</p>
        <p>Fig. 3. Concept Map of the ITIL 4 Framework
roles, inputs/outputs, resources and operations to be performed at the level
of individual value stream steps, whereas COBIT 2019 describes responsible/
accountable roles and information items owing in and out at the more
aggregate level of practices. Further di erences are that ITIL 4 does not cover IT
governance responsibilities and activities, while COBIT 2019 also has a broader
view of IT management, extending beyond developing and improving the IT
service management capability. For instance, processes such as budget
management, innovation management, and data management are not covered in ITIL
4. On the other hand, an ITIL ITSM practice such as service catalogue
management, is present in COBIT 2019, but only at the activity level, so with much
less comprehensive guidance.
4</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>The Role of the GITM Knowledge Graph</title>
      <p>The GITM Domain Ontology, and its organization speci c re nement, also
denes the twinning parameters (i.e., data about organizational IT assets and their
management and governance processes) that are relevant to an organization and
its speci c IT governance concerns. As mentioned above, to represent these
twinning parameters and to integrate them with other relevant data and knowledge
representations, including data from external sources (see Fig. 1), we plan to use
a Knowledge Graph based approach.</p>
      <p>The GITM Knowledge Graph component of our framework provides a
reference of how such Knowledge Graphs can be constructed. Furthermore, it
describes the visualization and formalization capabilities that such Knowledge
Graphs should o er to allow for human interpretation of the information and
machine processing of the data, respectively. Operationally, the GITM
Knowledge Graph component consists of a set of tools that realize interactive
visualizations (e.g., Visual Analytics tools, Business Intelligence dashboards) and
e cient querying of the vast amounts of IT governance related data in order to
support decision making.</p>
      <p>Metrics for IT governance and management performance indicators can be
operationalized as prede ned queries which can be easily parameterized and
executed by business users. Moreover, powerful Knowledge Graph platforms like
Stardog1, fed with the data of the organization-speci c IT governance Digital
Twin's Knowledge Graph, enable the application of advanced AI algorithms to
also proactively respond to environmental or internal changes of the
organizational IT assets and their management processes.</p>
      <p>Consequently, the realization of the GITM Knowledge Graph will have to
cater for the fact that the Workforce (see Fig. 1) has diverse backgrounds and
roles with regards to IT governance and management. The DT4GITM
framework needs to make the data-driven and AI-enabled algorithms accessible and
comprehensible in adequate graphical user interfaces to be applicable.
5</p>
    </sec>
    <sec id="sec-6">
      <title>Strategy to Develop the GITM Domain Ontology</title>
      <p>
        Since the DT4GITM framework, and the GITM Domain Ontology that is part
of it, are artifacts designed as solutions for solving problems related to the
challenges posed by the Digital Transformation to IT governance, we will use a
Design Science Research methodology [
        <xref ref-type="bibr" rid="ref15 ref9">9, 15</xref>
        ]. The DT4GITM framework, as a
reference architecture, also needs to be complemented with heuristics to apply
(and re ne) the reference architecture in speci c situations. This is where we
will use Situational Method Engineering [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] as a research method. Using
example scenarios, and real-world cases, situational factors will be identi ed to
di erentiate the speci cities of the cases, as well as guidelines and heuristics to
tune the GITM Domain Ontology and/or DT4GITM reference architecture to
the situation at hand.
      </p>
      <p>As discussed before, the conceptual models of COBIT 2019 and ITIL 4 require
more elaboration in terms of their performance indicators such that sensors
and data streams can be de ned. Speci c concerns/qualities, such as security,
performance, costs, etc, are also likely to lead to a need to re ne the GITM
Domain Ontology. This process will also be driven by the needs of example
scenarios and real-world cases, which will also result in requirements on the
actual GITM Domain Ontology.</p>
      <p>
        For the GITM Domain Ontology, this leads to the situation as depicted in
Fig. 4. The triangle represents the ontology, involving di erent levels of
genericity. At the top, we nd a foundational ontology (e.g., UFO [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]). Using conceptual
models of the contributing frameworks and standards as a base, as exempli ed
by the concept maps discussed in Section 3, we will then de ne an IT generic
GITM Domain Ontology expressed in terms of the foundational ontology. This
part of the ontology is IT generic in the sense that it may refer to e.g., IT
assets, but does not yet refer to speci c information technologies, such as WiFi,
1 https://www.stardog.com/, last visited: 09.07.2021
DT4GITM
framework
      </p>
      <p>Foundational ontology
IT generic
IT &amp; concern specific
Organisation specific
scenarios &amp; cases
applications
Blockchain, Cloud solutions, etc. Driven by concrete scenarios and cases, this
IT generic ontology can then be re ned further (and iteratively validated and
improved) towards (1) considerations pertaining to speci c information
technologies, and (2) speci c concerns/qualities. This IT &amp; concern speci c part
of the ontology is still organization agnostic. In other words, for a speci c
organization, with its priorities, technology choices, etc., further re nements will
be necessary. For the DT4GITM framework, as a reference architecture, only
the three higher levels of the (strati ed) ontology will be included, where the
DT4GITM framework is also foreseen to include guidelines (designed using a
Situational Method Engineering approach) for specializing the generic core to
an organization speci c ontology.</p>
      <p>What is also hinted at in Fig. 4 is the further evolution of the ontology when
applying it in di erent organizations. Here, it is expected to see the strongest
evolution for the lower layers while the upper layers { especially the foundational
ontology { should remain stable.
6</p>
    </sec>
    <sec id="sec-7">
      <title>A Hardware Incident Management Scenario</title>
      <p>wireless access point would be represented in the organization's GITM
Knowledge Graph as an instance of an organization-speci c IT asset concept in the
GITM Domain Ontology (e.g., wireless communication device). The Knowledge
Graph would relate it to other relevant information such as its location (i.e., the
warehouse), its state, etc. Data streams from the access point logs and a sensor
would be in place to automatically detect failures, and such failure signals would
change the state of the device in the Knowledge Graph. A rule-based component
would automatically qualify the incident as a Priority 2 incident which would
directly trigger its resolution. The Knowledge Graph comprises information of the
workforce and their roles. A network support engineer would be contacted who
would then actuate the resolution procedure. Most likely, she would rst replace
the access point in order to immediately enable the forklift driver to resume
the standard way of working. The Knowledge Graph incorporates data from the
Con guration Management System (CMS) that describes the con guration of
the warehouse access points to properly function within the organization's
network. Moreover, the Knowledge Graph enables the network support engineer to
execute a query that would help her identifying similar access points that are
currently either not in use or dispensable.</p>
      <p>The data about the failure would also be available for further analysis. For
instance, accumulating failure data of wireless access points could be used for
developing a predictive maintenance model, in the hope that next time a
replacement is installed already before the device actually breaks. Moreover,
feedback gained from all involved persons of this value stream will be collected and
analyzed in the Knowledge Graph in order to learn about the quality of the
implemented resolution in particular as well as on the incident management in
general.</p>
      <p>As the example scenario illustrates the connectedness of IT assets and
governance/management processes realized through the Digital Twin based
infrastructure, allows for directed and timely reactive and proactive responses of the
IT governance/management system. But also, the ontology-driven approach
induces a certain robustness in the system (as suggested in Fig. 4), making the
system more adaptive and IT governance and management more agile. For instance,
further warehouse automation would replace forklift drivers by robots that are
actuated by the warehouse control system. The wireless access point would be
replaced by built-in IoT devices. This would only a ect the organization-speci c
GITM Domain Ontology, but not the IT &amp; concern speci c, IT generic, and
foundational layers of the GITM Domain Ontology of the DT4GITM
framework. In other words, it would be clear how to adapt the organization-speci c
Knowledge Graph to the new situation and to gure out the required changes
to the rule-based component.
7</p>
    </sec>
    <sec id="sec-8">
      <title>Conclusion</title>
      <p>The Digital Transformation of our society requires IT infrastructures to be more
agile, more adaptive, and more connected than ever. In the paper at hand we
argue for a digital transformation of IT governance and management itself by
proposing the Digital Twin for Governed IT Management (DT4GITM)
framework that applies the concept of Digital Twins to IT governance. The conceptual
backbone of DT4GITM is a domain ontology that aims to formally represent the
concepts, properties, and relationships of COBIT 2019 and ITIL 4 frameworks,
amongst other relevant standards and frameworks for IT governance and
management.</p>
      <p>The paper described the conceptual outline of the DT4GITM framework and
elaborated on our strategy for developing the GITM Domain Ontology. The
potential bene ts of using the framework were exempli ed by means of a hardware
incident management scenario from ITIL 4. We believe this paper establishes a
meaningful foundation for research in the direction of digital transformation of
IT governance and management. Our plans for the near future are to apply and
evolve the DT4GITM framework and the GITM Domain Ontology in real case
studies.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. Axelos: ITIL Foundation.
          <article-title>ITIL 4. The Stationery O ce</article-title>
          , London, UK (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Chergui</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sayouti</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Medromi</surname>
          </string-name>
          , H.:
          <article-title>It governance ontology building process: Example of developing audit ontology</article-title>
          .
          <source>International Journal of Computer Techniques</source>
          <volume>2</volume>
          (
          <issue>1</issue>
          ),
          <volume>134</volume>
          {
          <fpage>141</fpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>De Haes</surname>
          </string-name>
          , S.,
          <string-name>
            <surname>Van Grembergen</surname>
            ,
            <given-names>W.:</given-names>
          </string-name>
          <article-title>An exploratory study into it governance implementations and its impact on business/it alignment</article-title>
          .
          <source>Information Systems Management</source>
          <volume>26</volume>
          (
          <issue>2</issue>
          ),
          <volume>123</volume>
          {
          <fpage>137</fpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>De Haes</surname>
          </string-name>
          , S.,
          <string-name>
            <surname>Van Grembergen</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Joshi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Huygh</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Enterprise Governance of Information Technology</article-title>
          .
          <source>Achieving Alignment and Value in Digital Organizations</source>
          . Springer, Heidelberg, Germany, 3rd edn. (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>El</given-names>
            <surname>Yamami</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            ,
            <surname>Mansouri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Qbadou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Illoussamen</surname>
          </string-name>
          ,
          <string-name>
            <surname>E.</surname>
          </string-name>
          :
          <article-title>An ontological representation of itil framework service level management process</article-title>
          . In: Khoukhi,
          <string-name>
            <given-names>F.</given-names>
            ,
            <surname>Bahaj</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Ezziyyani</surname>
          </string-name>
          , M. (eds.)
          <source>Smart Data and Computational Intelligence</source>
          . pp.
          <volume>88</volume>
          {
          <fpage>94</fpage>
          . Springer International Publishing,
          <string-name>
            <surname>Cham</surname>
          </string-name>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Fensel</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Simsek</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Angele</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Huaman</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Elias</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Panasiuk</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Toma</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Umbrich</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wahler</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Knowledge Graphs { Methodology, Tools and</article-title>
          Selected Use Cases. Springer, Heidelberg, Germany (
          <year>2020</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Galkin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Scerri</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Enterprise knowledge graphs: A backbone of linked enterprise data</article-title>
          .
          <source>In: 2016 IEEE/WIC/ACM International Conference on Web Intelligence (WI)</source>
          . pp.
          <volume>497</volume>
          {
          <issue>502</issue>
          (
          <year>2016</year>
          ). https://doi.org/10.1109/WI.
          <year>2016</year>
          .0083
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Goeken</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Alter</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Representing it governance frameworks as metamodels</article-title>
          .
          <source>In: CSREA EEE</source>
          . pp.
          <volume>48</volume>
          {
          <issue>54</issue>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Gregor</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jones</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>The Anatomy of a Design Theory</article-title>
          .
          <source>Journal of the Association for Information Systems</source>
          <volume>8</volume>
          (
          <issue>5</issue>
          ),
          <volume>312</volume>
          {
          <fpage>335</fpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Guizzardi</surname>
          </string-name>
          , G.:
          <article-title>Ontological Foundations for Structural Conceptual Models</article-title>
          .
          <source>Ph.D. thesis</source>
          , University of Twente, Enschede, the
          <string-name>
            <surname>Netherlands</surname>
          </string-name>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Henderson-Sellers</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Ralyte</surname>
          </string-name>
          , J.:
          <article-title>Situational method engineering: state-of-theart review</article-title>
          .
          <source>Journal of Universal Computer Science</source>
          <volume>16</volume>
          (
          <issue>3</issue>
          ),
          <volume>424</volume>
          {
          <fpage>478</fpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <article-title>COBIT 2019 Framework: Governance and Management Objectives</article-title>
          . ISACA, Schaumberg, Illinois (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Moudoubah</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>El Yamami</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mansouri</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Qbadou</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Towards the implementation of an ontology based on COBIT Framework (CobitOntology)</article-title>
          .
          <source>In: Proceedings of the 1st International Conference on Smart Systems and Data Science</source>
          . pp.
          <volume>1</volume>
          {
          <issue>6</issue>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Nugroho</surname>
          </string-name>
          , H.:
          <article-title>Conceptual model of IT governance for higher education based on COBIT 5 framework</article-title>
          .
          <source>Journal of Theoretical and Applied Information Technology</source>
          <volume>60</volume>
          (
          <issue>2</issue>
          ),
          <volume>216</volume>
          {
          <fpage>221</fpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. Pe ers,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Rothenberger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Tuunanen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            ,
            <surname>Vaezi</surname>
          </string-name>
          , R.:
          <article-title>Design science research evaluation</article-title>
          . In: Pe ers,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Rothenberger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Kuechler</surname>
          </string-name>
          ,
          <string-name>
            <surname>B.</surname>
          </string-name>
          <source>(eds.) Design Science Research in Information Systems. Advances in Theory and Practice</source>
          . pp.
          <volume>398</volume>
          {
          <fpage>410</fpage>
          . Springer Berlin Heidelberg, Berlin, Heidelberg (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Poels</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Proper</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bork</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          : DT4GITM {
          <article-title>Towards a Digital Twin Framework for Enterprise Governance of Information Technology</article-title>
          .
          <source>In: Sumitted to the 55th Hawaii International Conference on System Sciences</source>
          . p.
          <source>under review</source>
          (
          <year>2022</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Siegel</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The sense-think-act paradigm revisited</article-title>
          .
          <source>In: Robotic Sensing</source>
          ,
          <year>2003</year>
          . ROSE'
          <volume>03</volume>
          . 1st International Workshop on. pp.
          <volume>5</volume>
          {
          <issue>10</issue>
          (
          <year>June 2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Steuperaert</surname>
            ,
            <given-names>D.: COBIT</given-names>
          </string-name>
          <year>2019</year>
          :
          <article-title>A signi cant update</article-title>
          .
          <source>EDPACS - The EDP Audit, Control, and Security Newsletter</source>
          <volume>59</volume>
          (
          <issue>1</issue>
          ),
          <volume>14</volume>
          {
          <fpage>18</fpage>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Valiente</surname>
            ,
            <given-names>M.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garcia-Barriocanal</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sicilia</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          :
          <article-title>Applying an ontology approach to it service management for business-it integration</article-title>
          .
          <source>Knowledge-Based Systems 28</source>
          ,
          <fpage>76</fpage>
          {
          <fpage>87</fpage>
          (
          <year>2012</year>
          ). https://doi.org/10.1016/j.knosys.
          <year>2011</year>
          .
          <volume>12</volume>
          .003
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>