<!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>Flexible Multi-Aspect Model Integration for Cyber-Physical Production Systems Engineering</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Felix Rinker</string-name>
          <email>felix.rinker@tuwien.ac.at</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Christian Doppler Lab CDL-SQI Institute of Information Systems Engineering Technische Universitat Wien</institution>
          ,
          <addr-line>Vienna</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <fpage>31</fpage>
      <lpage>40</lpage>
      <abstract>
        <p>Background. Consistent cross-disciplinary engineering data models have become increasingly important for engineers and project managers to validate system designs or implement new features in existing systems. However, discipline-speci c designs (mechanical, electrical, automation engineering etc.) in isolated data models and proprietary software tools often create information silos. Similar to information systems, the challenges in Cyber-Physical Production System (CPPS) are a high amount of heterogeneous data that needs to be analysed and accessible for stakeholders and systems. Aim. The goal of the Flexible Multiaspect Model Integration project is to support the integration of local engineering views and artefacts using the de nition of common concepts across di erent disciplines. Therefore, the thesis project will provide capabilities to integrate and validate multi-aspect models more e ciently to increase the data quality. Method. The project will follow Design Science methodology to design and evaluate i) a method for collecting and de ning common concepts across engineering disciplines, ii) a modularised software system design that enables exible model integration processes in a CPPS context, and iii) an exemplary model integration process that supports data integration needs in the planning, operation, and analytics phase. The model integration processes are evaluated with real-world uses cases from industry. Conclusion. The information systems community will gain insight into the requirements in engineering and a method for agreeing on an inter-disciplinary common understanding from this research.</p>
      </abstract>
      <kwd-group>
        <kwd>Industry 4</kwd>
        <kwd>0</kwd>
        <kwd>Multi-Aspect Information System</kwd>
        <kwd>MultiDisciplinary Engineering</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Information System Engineering (ISE) for CPPS use cases, like digital
shadows, require techniques for (i) automated aggregation and reduction of data,
(ii) data analysis methods, (iii) data accessibility to stakeholder and systems
and (iv) feedback for decision support and system controlling [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Therefore,
the integration and harmonisation of all this data is an essential task in CPPS
engineering to increase to overall data quality [
        <xref ref-type="bibr" rid="ref28">28</xref>
        ].
      </p>
      <p>
        To enable these CPPS aspects the discipline-speci c views, local data sources
and stakeholder concerns need to be successful integrated in a combined model
for further validation and veri cation of the system design [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ]. A major concern
for building such a combined interdisciplinary model is the interoperability of
software systems as a critical factor for increasing productivity and reducing
costs in the automation of production and manufacturing systems [
        <xref ref-type="bibr" rid="ref27 ref5">5, 27</xref>
        ].
      </p>
      <p>
        The real-world use case from our industry partner data exchange towards
production system simulation [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], illustrates a typical data exchange and model
integration process and key discipline-speci c views and is depicted in Figure 1:
Mechanical
      </p>
      <p>Engineer
Squirrel-Cage Motor</p>
      <p>Electrical
Engineer
Engineering
Data Exchange</p>
      <p>C1 Motor</p>
      <p>C2</p>
      <p>Plant Planner
Three-Phase
Induction Motor</p>
      <p>Updates</p>
      <p>Automation Engineer
Simulation
Data Delivery</p>
      <p>C3</p>
      <p>Simulation</p>
      <p>Engineer
Three-Phase
Induction Motor</p>
      <p>Control
Backflow</p>
      <p>Engineering
Data Artifact
Fig. 1: Data Exchange Towards Production System Simulation Use Case and
Challenges.</p>
      <p>The plant planner designs the initial CPPS functions and structure.
Subsequently, the mechanical engineer builds up the system tree based on the basic
plan with mechanical functions, system parts, properties, and location of parts.
Next, the electrical engineer adds electrical components with interfaces to the
mechanical parts and views (electrical system parameters, such as voltage or
energy supply). Finally, the automation engineer adds control code that automates
the previous engineered parts. At a later stage, the simulation expert integrates
the engineering artefacts from basic, mechanical, electrical and automation
engineering to design the simulation model.</p>
      <p>Ideally, these tasks would be completed sequentially. Yet, engineers design in
parallel regularly triggering follow-up changes across disciplines due to increased
competition and complex dependencies between hard- and software. Hence, they
need to synchronise engineering artefacts during the engineering phase. These
data are often synchronised and integrated manually or with poor tool
support that takes additional e ort and tends to be error-prone, inducing avoidable
project risks.</p>
      <p>
        Challenges to Data Integration in CPPS Engineering. Information
systems and computer-assisted engineering aim at supporting model integration
processes to achieve a common view on engineering objects and accessing the
combined model. However, we have identi ed the following challenges (depicted
in Figure 1) from the industrial use case and literature [
        <xref ref-type="bibr" rid="ref11 ref16 ref17">11, 16, 17</xref>
        ].
      </p>
      <p>
        C1 Information loss due to artefact-based data exchange. Data
exchange in a multi-disciplinary environment is usually based on artefact-based
transactions across several workgroups [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The use of proprietary or hierarchy
limited le formats, such as PDF, spreadsheets or drawings, can lead to
information loss [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. The reasons can be the unclear syntax of engineering data or
di culties with traceability of le updates leading to diverging work versions.
As a result, inconsistencies and di culties with data integration often arise.
      </p>
      <p>
        C2 High e ort of repetitive tasks and con guration of domain data.
Data integration in a multi-disciplinary process often requires repetitive tasks
that are usually performed manually or require high con guration e ort [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
This is because the engineering data exchange is not regarded as a value-creating
business process, and thus data providers send their data in discipline-speci c
formats and structures. Often data structures change during the project, bearing
the e ort for data extraction and integration on data consumers [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        C3 Insu cient common understanding of system boundaries. From
the engineers perspective, foreign views and data formats from other disciplines
are, in general, not visible [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. However, the general heterogeneity of existing
interfaces and system boundaries, views and process complicates the design of
common understanding (cf. Figure 2) and thus also error detection [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ].
Aim. The proposed doctoral thesis aims to address the factors that lead to
low data quality within industrial information systems. Low data quality and
the aforementioned issues with data integration hinder the system
transformation towards more complex use cases, such as digital twin, big data or adaptive
      </p>
      <p>CPPS architectures. We aim at proposing an information system design that
will improve the data exchange and integration in Multi-Disciplinary
Engineering (MDE) (see Figure 2).</p>
    </sec>
    <sec id="sec-2">
      <title>Integration</title>
    </sec>
    <sec id="sec-3">
      <title>Engineering Data Logistics</title>
      <p>Domain
Experts</p>
      <p>*.pdf Import
Engineers
*.csv Import</p>
      <p>
        The multi-aspect information system consists of three parts: (1) Data
integration will handle the import, transformation and integration to Common
Concepts (CCs) of engineering artefacts coming from data providers, such as
engineers or domain experts. (2) Engineering data logistics will handle the
common uni ed model. The data curator will be responsible for the management of
discipline-speci c concepts, their relations to CCs and semantic links between
engineering views. (3) Data delivery will handle speci c data consumer requests.
Data consumers will be able to request data deliveries (a) in their domain-speci c
hierarchy (e.g., a simulation view) or (b) as domain-agnostic networks (e.g., for
analysis tasks across several engineering views) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. New views, data integration
and data delivery work ows will be e ciently added by con guration.
      </p>
      <p>The advantage of this information system design will be the exible adaption
to di erent application environments and delivery needs. This will improve the
work process of multi-disciplinary environments and facilitate more e cient data
provision that will likely lead to better data quality for consumers.
2</p>
      <sec id="sec-3-1">
        <title>Related Work</title>
        <p>The challenges to data integration (cf. Section 1) lead to an error-prone and
ine cient knowledge creation and quality assurance in information system
engineering in Industry 4.0, and can lead to information loss or silos.</p>
        <p>
          System modelling in CPPS engineering is challenging due to
disciplinespeci c views, tools, languages and legacy system environments [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ]. For the
Industry 4.0 vision, domain-speci c modelling languages are a crucial part to
facilitate model-driven engineering for complex data-driven use cases [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ]. Several
initiatives, such as the Reference Architecture Model for Industry 4.0 (RAMI
4.0) and new standards and technologies, such as AutomationML (AML),
Systems Modeling Language (SysML) or OPC Uni ed Architecture (OPC UA), aim
at alleviating these limitations [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. A notable approach for enterprise integration
in the manufacturing domain is the Computer Integrated Manufacturing Open
System Architecture (CIMOSA) framework, especially object capability pro les
and collaboration view to organise collaborative organisation networks [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. On
the one hand, these solution designs have made fundamental contribution to
the conceptual key elements and abstraction layers of interoperability. However
the translation to the applied eld is still challenging due to the lack of
standardisation. Missing system interface and boundary object [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ] information are
impediments to consistent data integration. On the other hand, semantic web
technologies, like ontologies, seem promising as a solution approach for describing
and managing such integration knowledge, but their construction is still highly
complex and lacks adequate tool support [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ].
        </p>
        <p>
          Inconsistency management and consistency checking in systems
engineering is crucial to organise collaborative organisation networks. Egyed et al. [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]
use Object Constraint Language (OCL) expressions to maintain consistent
dependencies across engineering objects and views in UML/SysML multi-models.
Kattner et al. [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] investigate inconsistency management in heterogeneous
engineering models and propose an approach to identify model dependencies. Both
approaches require precise data and process knowledge of the organisation and
information system, which is often not well de ned in Multi-Disciplinary
Engineering Environment (MDEE).
        </p>
        <p>The thesis will explore methods that build on the strengths of these
modelling and inconsistency management approaches and mitigate the impact of
their shortcomings on the data exchange process.</p>
        <p>
          Engineering data logistics [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ] in Multi-Disciplinary Engineering is a
sociotechnical system ensuring that engineers receive the required data at the right
amount, quality, and point in time. The system realises an interdisciplinary
round-trip data exchange, transformation, integration, and selection [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. A major
concern for information modelling in an industrial context is the lack of adequate
multi-view modelling processes [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. Relevant groundwork is established by the
research around Multi-perspective Enterprise Modeling (MEMO) both from the
requirements and the meta-modelling perspective [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>
          Open challenges mentioned in this context are the lack of use case scenarios
and the need for an adaptable architecture to cover enterprise model evolution.
Tunjic et al. [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ] proposed the Single Underlying Model (SUM), as a method to
synchronise multiple model views, which is automatically populated with data
from single views, based on previously de ned mappings.
        </p>
        <p>In this work, we build on the SUM concept and engineering data logistics to
enable a common uni ed model with processes for distributed data integration
and model evolution.
3</p>
      </sec>
      <sec id="sec-3-2">
        <title>Research Questions</title>
        <p>To address the challenges to data integration introduced in Section 1, we raise
the following research questions (RQs).</p>
        <p>RQ1: What are requirements and capabilities to enable multi-view
model integration towards a common model view? RQ1 investigates the
multi-view capabilities needed to integrate di erent viewpoints in CPPS
engineering. We will elicit requirements from relevant industrial use cases for
integrating heterogeneous views. We will also explore di erent data integration
approaches and methods to nd common attributes and concepts among di erent
system contexts. We will elicit these capabilities from literature and industrial
use cases.</p>
        <p>RQ2: What methods can address the multi-aspect model integration in
CPPS engineering? This research question aims at developing and evaluating
methods for multi-aspect model integration to address the requirements coming
from RQ1. First, we will de ne a method for collecting engineering concepts and
for de ning common concepts, such as products, production processes, or
production resources, which link the discipline-speci c engineering views. Second,
we will develop a method for designing a data integration pipeline consisting
of multi-aspect model integration operations and process ow speci cation as
a foundation for exibly designing and con guring data transformation
capabilities for data integration and delivery (see Figure 2). Third, we will design
a method for operating pipelines for data integration and delivery based on
DevOps approaches.</p>
        <p>RQ3: What information system design can automate multi-aspect
model integration in CPPS engineering? RQ3 aims at designing and
evaluating a system that automates tasks for exible multi-aspect model
integration based on the methods coming from RQ2. We will develop a system design
that will include (a) tool support for common concept de nition; (b) a
Domainspeci c language (DSL) for data integration work ow speci cation considering
approaches such as DevOps and business process modelling; (c) data integration
operators that can be exible orchestrated to data integration pipelines. In this
context, we de ne exibility as the ease to adapt the system design to di erent
application environments, such as the number of engineering disciplines, data
sources and stakeholder perspective. We will conduct a workshop with domain
experts to evaluate the exibility of our approach concerning the e ort needed
to conduct adaption tasks.</p>
      </sec>
      <sec id="sec-3-3">
        <title>Methodology</title>
        <p>
          We follow the Design Science approach [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] and the Engineering Cycle based
on Wieringa [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ] to de ne the research methodology.
        </p>
        <p>In the problem investigation phase, we will conduct a domain analysis
to investigate what kind of data integration is required to support the CPPS
engineering process and data exchange. Speci cally, we will focus on the key
stakeholders' needs and processes and analyse their data models and existing
standards and solutions. Consequently, we will develop a conceptual problem
framework as a guiding use case for further system design and evaluation.</p>
        <p>In the treatment design phase we will derive requirements for data
integration needs from the conceptual problem framework. Candidate treatments
from model-driven engineering, semantic web, and software engineering will be
evaluated and investigated. Formal concepts from model-driven engineering, such
as the Meta Object Facility (MOF), will be explored to derive a DSL for
objectoriented meta-models. We will research semantic web-based methods on how to
construct and combine discipline-speci c taxonomies and other structures. Also,
linking and integrating these discipline-speci c taxonomies to a common model
will be a topic of interest. Further, we will explore software engineering design
patterns for modularising software system design.</p>
        <p>In the treatment validation phase we will derive typical use cases for
stakeholder goals. Typical aspects include (i) data integration during CPPS
engineering, operation, e.g., integration of sensor data, (ii) connection to open
interfaces, such as OPCUA, and (iii) query aspects of the CPPS for non-experts
in information systems methods to analyse the process or to perform data quality
tasks.</p>
        <p>In the treatment implementation phase we will develop a prototype that
realises the identi ed capabilities.
5</p>
      </sec>
      <sec id="sec-3-4">
        <title>Preliminary results</title>
        <p>
          We will build on recent research of the Christian Doppler Laboratory on Security
and Quality Improvement in the Production System Lifecycle [
          <xref ref-type="bibr" rid="ref15 ref18 ref19 ref28 ref3 ref4">3, 4, 15, 18, 19, 28</xref>
          ],
resulting from a technical debt analysis [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ], which highlighted the gaps between
established practices and state of the art.
        </p>
        <p>
          We have developed an engineering data exchange approach that focuses on
the data consumer's needs and requirements [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. The process is split into data
de nition and data operation phases separating the exchange model building
and the concrete data exchange tasks. These results provide the basis to build
an initial prototype for multi-aspect model integration using AML, as a CPPS
engineering standard, as modelling language and evaluated it with industry
partners [
          <xref ref-type="bibr" rid="ref15 ref4">4, 15</xref>
          ].
        </p>
        <p>
          To support domain experts in their analysis tasks, we have explored
graphbased visualisation methods that support domain experts to review multi-view
engineering data [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]. The developed prototype supports features, such as
dependency highlighting, easy graph node management and data search capabilities.
        </p>
        <p>
          We designed and prototypically evaluated an initial approach of a multi-view
model transformation pipeline using a common underlying model and automated
by a Continuous Integration (CI) server [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ].
6
        </p>
      </sec>
      <sec id="sec-3-5">
        <title>Conclusion</title>
        <p>
          This thesis' aim is to overcome gaps and challenges in engineering data
integration by combining semantic and model-based approaches to facilitate a lossless,
transparent and comprehensive data exchange and transformation. However,
major challenges of these techniques are a steep learning curve, high setup costs,
scarce expert knowledge required to gain the expected bene t [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] and limited
tool support. Thus, we consider novel approaches, such as low code [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ], to
provide an accessible way to implement multi-aspect model integration tool support,
which is needed to reduce technical debt in CPPS engineering [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ]. This research
will contribute to the information system community artefacts, knowledge and
insights on (a) requirements and capabilities for multi-aspect data integration;
(b) method for multi-aspect model integration; and (c) exible information
system design for multi-aspect model integration within the context of CPPS
engineering. At the current stage, we would like to ask the advisory committee: (1)
How to improve the understandability of the use case and challenges? (2) How
to improve the planned results for the research community? (3) What further
related work and research initiatives would you recommend? Thank you for your
valuable time and advice.
        </p>
      </sec>
      <sec id="sec-3-6">
        <title>Acknowledgment</title>
        <p>This doctoral thesis project is supervised by Stefan Bi . The nancial support
by the Christian Doppler Research Association, the Austrian Federal Ministry
for Digital &amp; Economic A airs and the National Foundation for Research,
Technology and Development is gratefully acknowledged.</p>
        <p>Rinker et al.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>S.</given-names>
            <surname>Bi</surname>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          . Luder, and D. Gerhard, editors.
          <source>Multi-Disciplinary Engineering for Cyber-Physical Production Systems, Data Models and Software Solutions for Handling Complex Engineering Projects</source>
          . Springer,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>S.</given-names>
            <surname>Bi</surname>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          . Luder,
          <string-name>
            <given-names>K.</given-names>
            <surname>Meixner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Rinker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Eckhart</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Winkler</surname>
          </string-name>
          .
          <article-title>MultiView-Model Risk Assessment in Cyber-Physical Production Systems Engineering</article-title>
          .
          <source>In 9th Int. Conf. on Model-Driven Eng. and Softw</source>
          . Dev.,
          <string-name>
            <surname>MODELSWARD</surname>
          </string-name>
          <year>2021</year>
          . SciTePress,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>S.</given-names>
            <surname>Bi</surname>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          . Luder,
          <string-name>
            <given-names>F.</given-names>
            <surname>Rinker</surname>
          </string-name>
          , and
          <string-name>
            <given-names>L.</given-names>
            <surname>Waltersdorfer</surname>
          </string-name>
          .
          <article-title>E cient Engineering Data Exchange in Multi-disciplinary Systems Engineering</article-title>
          . In
          <source>International Conference on Advanced Information Systems Engineering</source>
          , pages
          <volume>17</volume>
          {
          <fpage>31</fpage>
          . Springer,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>S.</given-names>
            <surname>Bi</surname>
          </string-name>
          ,
          <string-name>
            <surname>A</surname>
          </string-name>
          . Luder,
          <string-name>
            <given-names>F.</given-names>
            <surname>Rinker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Waltersdorfer</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Winkler</surname>
          </string-name>
          .
          <article-title>Engineering Data Logistics for Agile Automation Systems Engineering: Requirements and Solution Concepts with AutomationML, chapter 8</article-title>
          , page 37. Springer,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>R.</given-names>
            <surname>Drath</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Fay</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Barth</surname>
          </string-name>
          . Interoperabilitat von Engineering-Werkzeugen. Autom.,
          <volume>59</volume>
          (
          <issue>7</issue>
          ):
          <fpage>451</fpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>A.</given-names>
            <surname>Egyed</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Zeman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Hehenberger</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Demuth</surname>
          </string-name>
          .
          <article-title>Maintaining consistency across engineering artifacts</article-title>
          .
          <source>Computer</source>
          ,
          <volume>51</volume>
          (
          <issue>2</issue>
          ):
          <volume>28</volume>
          {
          <fpage>35</fpage>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>S.</given-names>
            <surname>Feldmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Kernschmidt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Wimmer</surname>
          </string-name>
          , and
          <string-name>
            <given-names>B.</given-names>
            <surname>Vogel-Heuser</surname>
          </string-name>
          .
          <article-title>Managing intermodel inconsistencies in model-based systems engineering: Application in automated production systems engineering</article-title>
          .
          <source>Journal of Systems and Software</source>
          ,
          <volume>153</volume>
          :
          <fpage>105</fpage>
          {
          <fpage>134</fpage>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>U.</given-names>
            <surname>Frank</surname>
          </string-name>
          <article-title>. Multi-perspective enterprise modeling: foundational concepts, prospects and future research challenges</article-title>
          .
          <source>Softw. Syst. Model.</source>
          ,
          <volume>13</volume>
          (
          <issue>3</issue>
          ):
          <volume>941</volume>
          {
          <fpage>962</fpage>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. I.
          <string-name>
            <surname>Grangel-Gonzalez</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Halilaj</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Auer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Lohmann</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Lange</surname>
            , and
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Collarana</surname>
          </string-name>
          .
          <article-title>An RDF-based approach for implementing industry 4.0 components with Administration Shells</article-title>
          .
          <source>In 2016 IEEE 21st International Conference on Emerging Technologies and Factory Automation (ETFA)</source>
          , pages
          <fpage>1</fpage>
          <issue>{8</issue>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>A. R. Hevner</surname>
            ,
            <given-names>S. T.</given-names>
          </string-name>
          <string-name>
            <surname>March</surname>
            , J. Park, and
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Ram</surname>
          </string-name>
          .
          <source>Design Science in Information Systems Research. Design Science in IS Research MIS Quarterly</source>
          ,
          <volume>28</volume>
          (
          <issue>1</issue>
          ):
          <volume>75</volume>
          {
          <fpage>105</fpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>C. Hildebrandt</surname>
            ,
            <given-names>A</given-names>
          </string-name>
          . Kocher, C. Kustner,
          <string-name>
            <given-names>C.</given-names>
            <surname>Lopez-Enr quez</surname>
          </string-name>
          , A. W. Muller,
          <string-name>
            <given-names>B.</given-names>
            <surname>Caesar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. S.</given-names>
            <surname>Gundlach</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Fay</surname>
          </string-name>
          .
          <article-title>Ontology Building for Cyber-Physical Systems: Application in the Manufacturing Domain</article-title>
          .
          <source>IEEE Trans Autom. Sci. Eng</source>
          .,
          <volume>17</volume>
          (
          <issue>3</issue>
          ):
          <volume>1266</volume>
          {
          <fpage>1282</fpage>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <given-names>N.</given-names>
            <surname>Kattner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Bauer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. R.</given-names>
            <surname>Basirati</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Zou</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Brandl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Vogel-Heuser</surname>
          </string-name>
          , M. Bohm, H. Krcmar, G. Reinhart, and
          <string-name>
            <given-names>U.</given-names>
            <surname>Lindemann</surname>
          </string-name>
          .
          <article-title>Inconsistency management in heterogeneous models</article-title>
          .
          <source>In Proc. Design Society: Int. Conf. Eng. Design</source>
          , pages
          <volume>3661</volume>
          {
          <fpage>3670</fpage>
          . Cambridge Univ.,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <given-names>K.</given-names>
            <surname>Kosanke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. B.</given-names>
            <surname>Vernadat</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Zelm</surname>
          </string-name>
          .
          <article-title>Means to enable enterprise interoperation: CIMOSA Object Capability Pro les and CIMOSA Collaboration View</article-title>
          .
          <source>Annu. Rev. Control.</source>
          ,
          <volume>39</volume>
          :
          <fpage>94</fpage>
          {
          <fpage>101</fpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <given-names>M.</given-names>
            <surname>Liebenberg</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Jarke</surname>
          </string-name>
          .
          <article-title>Information systems engineering with digital shadows: Concept and case studies</article-title>
          . In S. Dustdar,
          <string-name>
            <given-names>E.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Salinesi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Rieu</surname>
          </string-name>
          , and V. Pant, editors,
          <source>Advanced Information Systems Engineering</source>
          , pages
          <volume>70</volume>
          {
          <fpage>84</fpage>
          ,
          <string-name>
            <surname>Cham</surname>
          </string-name>
          ,
          <year>2020</year>
          . Springer International Publishing.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15. A. Luder,
          <string-name>
            <given-names>K.</given-names>
            <surname>Kirchheim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Pauly</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Bi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Rinker</surname>
          </string-name>
          , and
          <string-name>
            <given-names>L.</given-names>
            <surname>Waltersdorfer</surname>
          </string-name>
          .
          <article-title>Supporting the Data Model Integrator in an Engineering Network by Automating Data Integration</article-title>
          .
          <source>In 17th IEEE International Conference on Industrial Informatics, INDIN</source>
          <year>2019</year>
          , Helsinki, Finland,
          <source>July 22-25</source>
          ,
          <year>2019</year>
          , pages
          <fpage>1229</fpage>
          {
          <fpage>1234</fpage>
          . IEEE,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. G. Morel,
          <string-name>
            <given-names>C. E.</given-names>
            <surname>Pereira</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S. Y.</given-names>
            <surname>Nof</surname>
          </string-name>
          .
          <article-title>Historical survey and emerging challenges of manufacturing automation modeling and control: A systems architecting perspective</article-title>
          .
          <source>Annu. Rev. Control.</source>
          ,
          <volume>47</volume>
          :
          <fpage>21</fpage>
          {
          <fpage>34</fpage>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <given-names>J.</given-names>
            <surname>Oevermann</surname>
          </string-name>
          .
          <article-title>Semantic PDF Segmentation for Legacy Documents in Technical Documentation</article-title>
          .
          <source>In Proceedings of the 14th International Conference on Semantic Systems, SEMANTICS</source>
          <year>2018</year>
          , Vienna, Austria,
          <source>September 10-13</source>
          ,
          <year>2018</year>
          , volume
          <volume>137</volume>
          of Procedia Computer Science, pages
          <volume>55</volume>
          {
          <fpage>65</fpage>
          .
          <string-name>
            <surname>Elsevier</surname>
          </string-name>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <given-names>F.</given-names>
            <surname>Rinker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Waltersdorfer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Meixner</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Bi</surname>
          </string-name>
          .
          <article-title>Towards Support of Global Views on Common Concepts employing Local Views</article-title>
          .
          <source>In 24th IEEE International Conference on Emerging Technologies and Factory Automation</source>
          ,
          <string-name>
            <surname>ETFA</surname>
          </string-name>
          <year>2019</year>
          , Zaragoza, Spain,
          <source>September 10-13</source>
          ,
          <year>2019</year>
          , pages
          <fpage>1686</fpage>
          {
          <fpage>1689</fpage>
          . IEEE,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <given-names>F.</given-names>
            <surname>Rinker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Waltersdorfer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Meixner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Winkler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Lu</surname>
          </string-name>
          <article-title>der, and</article-title>
          <string-name>
            <given-names>S.</given-names>
            <surname>Bi</surname>
          </string-name>
          .
          <article-title>Continuous Integration in Multi-view Modeling: A Model Transformation Pipeline Architecture for Production Systems Engineering</article-title>
          .
          <source>In Proceedings of the 9th International Conference on Model-Driven Engineering and Software Development - Volume</source>
          <volume>1</volume>
          : MODELSWARD,, pages
          <fpage>286</fpage>
          {
          <fpage>293</fpage>
          . INSTICC, SciTePress,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <given-names>F.</given-names>
            <surname>Rinker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Waltersdorfer</surname>
          </string-name>
          , M. Schuller, S. Bi , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Winkler</surname>
          </string-name>
          .
          <article-title>A Multi-Model Reviewing Approach for Production Systems Engineering Models</article-title>
          .
          <source>In Model-Driven Engineering and Software Development - 8th International Conference, MODELSWARD</source>
          <year>2020</year>
          , Valletta, Malta,
          <source>February 25-27</source>
          ,
          <year>2020</year>
          , Revised Selected Papers, volume
          <volume>1361</volume>
          of Communications in Computer and Information Science, pages
          <volume>121</volume>
          {
          <fpage>146</fpage>
          . Springer,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <given-names>R.</given-names>
            <surname>Sanchis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Garc</surname>
          </string-name>
          a-Perales,
          <string-name>
            <given-names>F.</given-names>
            <surname>Fraile</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Poler</surname>
          </string-name>
          .
          <article-title>Low-code as enabler of digital transformation in manufacturing industry</article-title>
          .
          <source>Applied Sciences</source>
          ,
          <volume>10</volume>
          (
          <issue>1</issue>
          ):
          <fpage>12</fpage>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <given-names>S. L.</given-names>
            <surname>Star</surname>
          </string-name>
          .
          <article-title>The Structure of Ill-Structured Solutions: Boundary Objects and Heterogeneous Distributed Problem Solving</article-title>
          . In L. Gasser and
          <string-name>
            <given-names>M. N.</given-names>
            <surname>Huhns</surname>
          </string-name>
          , editors,
          <source>Distributed Arti cial Intelligence</source>
          , pages
          <fpage>37</fpage>
          {
          <fpage>54</fpage>
          .
          <string-name>
            <surname>Elsevier</surname>
          </string-name>
          ,
          <year>1989</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <given-names>A.</given-names>
            <surname>Strahilov</surname>
          </string-name>
          and
          <string-name>
            <given-names>H.</given-names>
            <surname>Ha</surname>
          </string-name>
          <article-title>mmerle. Engineering work ow and software tool chains of automated production systems</article-title>
          .
          <source>In Multi-Disciplinary Engineering for CyberPhysical Production Systems</source>
          , pages
          <fpage>207</fpage>
          {
          <fpage>234</fpage>
          . Springer,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <given-names>C.</given-names>
            <surname>Tunjic</surname>
          </string-name>
          and
          <string-name>
            <given-names>C.</given-names>
            <surname>Atkinson</surname>
          </string-name>
          .
          <article-title>Synchronization of projective views on a singleunderlying-model</article-title>
          .
          <source>In Proceedings of the 2015 Joint MORSE/VAO Workshop on Model-Driven Robot Software Engineering and View-based Software-Engineering</source>
          , pages
          <volume>55</volume>
          {
          <fpage>58</fpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25. B.
          <string-name>
            <surname>Vogel-Heuser</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Bauernhansl</surname>
            , and
            <given-names>M. Ten</given-names>
          </string-name>
          <string-name>
            <surname>Hompel</surname>
          </string-name>
          .
          <source>Handbuch Industrie 4.0 Bd. 4. Allgemeine Grundlagen</source>
          ,
          <volume>2</volume>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26. B.
          <string-name>
            <surname>Vogel-Heuser</surname>
            , M. Bohm,
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Brodeck</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Kugler</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Maasen</surname>
            , D. Pantforder, M. Zou,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Buchholz</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Bauer</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Brandl</surname>
          </string-name>
          , and et al.
          <article-title>Interdisciplinary engineering of cyber-physical production systems: highlighting the bene ts of a combined interdisciplinary modelling approach on the basis of an industrial case</article-title>
          .
          <source>Design Science</source>
          ,
          <volume>6</volume>
          :
          <fpage>e5</fpage>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27. B.
          <string-name>
            <surname>Vogel-Heuser</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Diedrich</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Fay</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Jeschke</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Kowalewski</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Wollschlaeger</surname>
          </string-name>
          , et al.
          <article-title>Challenges for software engineering in automation</article-title>
          .
          <source>Journal of Software Engineering and Applications</source>
          ,
          <year>2014</year>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28. L.
          <string-name>
            <surname>Waltersdorfer</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          <string-name>
            <surname>Rinker</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Kathrein</surname>
            , and
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Bi</surname>
          </string-name>
          .
          <article-title>Experiences with technical debt and management strategies in production systems engineering</article-title>
          .
          <source>In Proceedings of the 3rd International Conference on Technical Debt</source>
          , pages
          <volume>41</volume>
          {
          <fpage>50</fpage>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <given-names>R.</given-names>
            <surname>Wieringa</surname>
          </string-name>
          .
          <source>Design Science Methodology for Information Systems and Software Engineering</source>
          . Springer Berlin Heidelberg,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <given-names>A.</given-names>
            <surname>Wortmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Barais</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Combemale</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Wimmer</surname>
          </string-name>
          .
          <article-title>Modeling languages in Industry 4.0: an extended systematic mapping study</article-title>
          .
          <source>Software and Systems Modeling</source>
          ,
          <volume>19</volume>
          (
          <issue>1</issue>
          ):
          <volume>67</volume>
          {
          <fpage>94</fpage>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>