<!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>Model based Configuration of Platforms for Managing Cross- Organizational (Business) Processes</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Thomas Knothe</string-name>
          <email>thomas.knothe@ipk.fraunhofer.de</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Patrick Gering</string-name>
          <email>patrick.gering@ipk.fraunhofer.de</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ilona Glodde</string-name>
          <email>ilona.glodde@ipk.fraunhofer.de</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ulrich Ahle</string-name>
          <email>ulrich.ahle@fiware.org</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jonas Böttger</string-name>
          <email>jonas.boettger@th-wildau.de</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Niklas Döberitz</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>FIWARE Foundation</institution>
          ,
          <addr-line>e.V. Franklinstrasse 13A, 10587 Berlin</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Fraunhofer Institute for Production Systems and Design Technology</institution>
          ,
          <addr-line>Pascalstraße 8-9, 10587 Berlin</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of Applied Science Wildau</institution>
          ,
          <addr-line>Hochschulring 1, 15745 Wildau</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this contribution interoperability is considered from the perspective of platforms, which have to manage cross-organisational business processes. A model-based approach for configuring a cloud platform for managing complex processes and their dependencies across different organisations is provided. The approach is applied on using FIWARE, which provides a framework of open source software platform components. The core concept is to extend the open source core data model of FIWARE by using the artefacts of an Enterprise model, describing the dependencies of processes, roles, object data and application interfaces. Based on a given use case the principal configuration was applied and validated.</p>
      </abstract>
      <kwd-group>
        <kwd>1 Cloud platforms</kwd>
        <kwd>model based configuration</kwd>
        <kwd>cross-organisational business processes</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>from different companies have to interact (e.g. the logistics service manager and production
control manager).</p>
      <p>For all cases the networked dependent processes are the base for interoperable business between
partners. Because of the frequent changes in our business environment, platforms can not rely on
stable process standards anymore. For that, PaaS – Solutions require suitable capabilities for
(automatic) configuration and adaptions of the underlying process network implementation. In the
following chapters a specific use case will be provided and a model-based configuration approach for
the open source Solution FIWARE proposed.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Example of cross-organizational processes in networks: Engineering of aircraft components</title>
      <p>In Figure 1, a partial view an Enterprise model based on the Integrated Enterprise Modelling
(IEM) methodology is given for describing the engineering lifecycle of aircraft components.
• Number of different organizations interacting along the different networked processes: 6
Modelling and executing of processes using standard workflow design and execution systems
would lead to a lot of effort and delay, whenever a change has to be considered.</p>
    </sec>
    <sec id="sec-3">
      <title>3. FIWARE platform</title>
      <p>
        FIWARE provides a framework of open source software platform components [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The key asset
is the context broker. It enables to manage context information in a partly decentralized and
largescale manner by gather, publish, notify and consume context information. For implementing the
context broker, FIWARE provides alternative implementations based on the ETSI NGSI-LD (Next
Generation Service Interface Linked Data) specification [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        The specification contains the data model and the API (Application Programming Interface). The
core elements of the NGSI-LD are derived from the concept of resource definition framework (RDF)
[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. It consists of interlinked Entity, Relationship, Property (as subclasses of rdfs.Resource) and
Value. These are interlinked with the type elements “hasObject and “hasValue” (as subtypes of
rdfs:Property).Based on this model cross-domain and domain specific data models can be derived. By
using a domain specific data model, such processes like the mentioned ones in chapter 1 can be
realized. ETSI provides fundamental concepts for security issues or tools for testing and validation as
well [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>In the next chapter it is described how such a data model can be extended to reflect complex
processes and data standards as indicated in chapter 2 by utilizing an Enterprise Model.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Model based platform configuration</title>
      <p>Enterprise Models are used to develop, operate and maintain complex enterprise architectures from
structural and behavioral perspectives. The major objectives of enterprise models are the
multidisciplinary application for stakeholder with different professional background and at the same time
to describe target or real systems as formal as possible.</p>
      <p>
        For the applicability in a wide range of disciplines and professional backgrounds enterprise
modelling methodologies aim to be expressiveness, whilst data models like RDF are suitable mostly
for computer scientist. The Integrated Enterprise Modelling Methodology (IEM) [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] is one of the
comprehensive approaches with a background in manufacturing and industrial services. As indicated
in Figure 1, the processes, responsible roles, data objects, documents and even the software
applications and its interfaces of complex cross-organisational process-networks can be described by
using IEM in a way, that all stakeholders can become familiar with. This ensures completeness,
economically feasibility, business consistency and at the same time formality of the specification. The
approach to configure platforms based on FIWARE technologies is extending the basic NGSI LD data
model with the specific cross domain ontology coming from the enterprise model (
      </p>
      <p>Figure ). The FIWARE context broker management services are then just managing application
data according to the extended data model.</p>
      <p>The aim is to perform the extension of the data model based on the IEM model automatically. For
that purpose, a mapping between the IEM Modelling Constructs and its matching the NGSI LD
representation was performed (Table 1).</p>
      <p>In the first validation step, the modelling data were transformed into its respective NGSI-LD
representation manually as well as tested the accuracy of results. All relevant elements of the IEM
model could have been transferred to the NGSI-LD model and the data integration was shown to be
possible. By validating the first data sets we did not find any mismatches. The first trial was limited
by less amount of data, just three involved roles and their responsibilities and permissions, by less
complexity of data structure and the fact, that no business applications from different locations were
involved.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusion and outlook</title>
      <p>Model based configuration is an opportunity for fast and consistent realization of cloud platforms
for managing and operating complex cross-organizational process networks. The approach to
configure a platform through the extension of the underlying platform data model. The FIWARE
platform seems to be suitable, because business and data logic are separated from platform
management functions. The potential benefits are promising. With model-based configuration, such
platforms can be adapted, even with complex process handling. The evolvement and change can be
discussed with all stakeholders. So, flexibility and agility according to our changing business
environment can be increased. In this trial, the IEM methodology was used for the model-based
configuration. Because IEM is compliant to ISO 19440 “Constructs for Enterprise Modelling”, it
seems to be wise to create a mapping between ISO 19440, so that other enterprise modelling
methodologies and tools can be used for cloud platform configuration as well.</p>
      <p>
        In future work, automatic testing capability has to be explored. Further on, data mappings
regarding complex business object definitions like CCTS (core components technical specification)
have to be integrated [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. After the experiences of the manual trial to perform the mapping between
the enterprise model to the platform data model we see not too much complexity to realize automatic
testing.
      </p>
    </sec>
    <sec id="sec-6">
      <title>6. References</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>European</given-names>
            <surname>Commission</surname>
          </string-name>
          , Corporate Sustainability Due Diligence:
          <article-title>Fostering sustainability in corporate governance</article-title>
          and
          <source>management systems</source>
          ,
          <year>2022</year>
          . URL: https://ec.europa.eu/info/businesseconomy-euro/
          <article-title>doing-business-eu/corporate-sustainability-due-diligence_en.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>H.</given-names>
            <surname>Weinaug</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Rabe</surname>
          </string-name>
          ,
          <article-title>Models and Methods for Web-support of a Multi-disciplinary B2(B2B) Network</article-title>
          , in: K. Mertins,
          <string-name>
            <given-names>R.</given-names>
            <surname>Ruggaber</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Popplewell</surname>
          </string-name>
          , X. Xu (Eds.),
          <source>Enterprise Interoperability</source>
          , Springer, London,
          <year>2008</year>
          , pp.
          <fpage>113</fpage>
          -
          <lpage>123</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <article-title>[3] FIWARE, FIWARE: The Open Source Platform for Our Smart Digital Future</article-title>
          ,
          <year>2021</year>
          . URL: https://www.fiware.org/.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>ETSI</given-names>
            ,
            <surname>Context Information Management (CIM); NGSI-LD</surname>
          </string-name>
          <string-name>
            <surname>API</surname>
          </string-name>
          ,
          <year>2021</year>
          . URL: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.05.01_60/gs_CIM009v010501p.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <issue>W3C</issue>
          ,
          <source>RDF Schema 1.1</source>
          ,
          <year>2014</year>
          . URL: https://www.w3.org/TR/rdf-schema/.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>G.</given-names>
            <surname>Spur</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Mertins</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Jochem</surname>
          </string-name>
          , Integrierte Unternehmensmodellierung,
          <source>Entwicklungen zur Normung von CIM Beuth</source>
          , Berlin,
          <year>1993</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>UNECE</surname>
          </string-name>
          ,
          <source>Core Components Technical Specification CCTS, version 3.0</source>
          ,
          <year>2009</year>
          . URL: https://unece.org/trade/uncefact/ccts.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>