<!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>Demands on Virtual Representation of Physical Industrie 4.0 Components</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Kristofer Hell</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Robin Hillmann</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Arndt Lüder</string-name>
          <email>arndt.lueder@ovgu.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Hannes Röpke</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jacek Zawisza</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nicole Schmidt</string-name>
          <email>nicole.schmidt@ovgu.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ambra Calà</string-name>
          <email>ambra.cala@ovgu.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Volkswagen AG</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Germany</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>kristofer.hell</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>robin.serafin.hillmann</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>hannes.roepke</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>jacek.zawisza}@volkswagen.de</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Otto-von-Guericke University Magdeburg</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Production uMsaaignetenance Instance</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Value Stream Figure 2: Reference Architectural Model Industrie 4.</institution>
          <addr-line>0 (RAMI 4.0) [6]</addr-line>
        </aff>
      </contrib-group>
      <abstract>
        <p>- Industrie 4.0 as one of the leading research and Main starting point of Industrie 4.0 is the consideration of development initiatives for factory automation systems envisions all life cycle phases relevant for a production system. Beyond satrhuicetruarrechyanodf Inbdeuhsatrviieor4.0recloamtepdonetontsittshatuteixlihziabtiitona gwenitehriinc the production system life cycle there are the life cycles of production system life cycles. The components are equipped products, and product orders [5], and the identification of with an administration shell containing a virtual representation needs related to the optimized integration of the different life of the component. But up to now it is still unclear on which cycle phases and activities within them. Based on them a set layers of a production system Industrie 4.0 components can be of challenges especially regarding integration (e.g. horizontal ifnofuonrdmawtiiotnh towhbiechmogdrealnedulwariitthyinatnhde awdmhaitnisatrreatiothneshreellle.vTahnet integration) has been identified as depicted in Figure 1. System Engineering (SE) plays a significant role in the Industrie One of the most interesting results reached within the 4.0 scenario. In order to align SE modeling with the new smart Industrie 4.0 research area so far is the “Reference factory automation environment, this paper intends to Architecture Model Industrie 4.0” (RAMI 4.0). This model meaningful Industrie 4.0 components and identifies information combines the production system life cycle with the control raenldevcaonnttrforlo.m the viewpoint of production system engineering hierarchy and the value streams relevant for production (see Figure 2).</p>
      </abstract>
      <kwd-group>
        <kwd>- Industrie 4</kwd>
        <kwd>0 components</kwd>
        <kwd>virtual representation</kwd>
        <kwd>production systems</kwd>
        <kwd>automotive</kwd>
        <kwd>engineering</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>INTRODUCTION</p>
      <p>
        Industrie 4.0 has been introduced as a vision for an
advanced production system control architecture and
engineering methodology (see [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], and [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]). It is
accompanied by similar approaches in Europe, even
worldwide. There are similar activities in the US led by the
“Industrial Internet Consortium”, in France and the UK that
coined the term “Factory of the future”, and in China.
      </p>
      <p>All of these initiatives have the same background: the
production system stakeholder’s need for highly flexible
production systems that can be adapted to rapidly changing
customer demands, and empower increased capabilities of
information acquisition, exchange, and processing applicable
in the engineering and control of production systems.</p>
    </sec>
    <sec id="sec-2">
      <title>Layers</title>
      <sec id="sec-2-1">
        <title>Business</title>
      </sec>
      <sec id="sec-2-2">
        <title>Functional</title>
      </sec>
      <sec id="sec-2-3">
        <title>Information</title>
      </sec>
      <sec id="sec-2-4">
        <title>Communication</title>
      </sec>
      <sec id="sec-2-5">
        <title>Integration</title>
      </sec>
      <sec id="sec-2-6">
        <title>Asset</title>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Hierarchy</title>
    </sec>
    <sec id="sec-4">
      <title>Levels</title>
      <p>
        As one key element of RAMI 4.0 the Industrie 4.0 component
has been identified. In [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] a set of structural, functional, and
information-related requirements to the Industrie 4.0
component is collected. Main characteristics of an Industrie
4.0 component is the combination of objects of the physical
world and the virtual world, targeting to provide dedicated
functionalities within both worlds as a holistic approach.
Therefore, it is identifiable, is able to communicate
appropriately, contains an administration shell, provides
Industrie 4.0 conform services, is able to control its own
state, and can be hierarchically structured (see Figure 3). For
more details see [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>The System Engineering is a multi-disciplinary approach
that has the potential to describe such components of large
complex systems, such as cyber physical systems and smart
factories, through special tools and languages.</p>
      <p>However, as the complexity is defined with the number of
components and their connections, several challenges are now
addressed to System Engineering for the development of
smart production systems with highly interconnected
components within the context of Industrie 4.0. One of the
key challenges is the virtual representation of these smart and
complex physical objects within a system.</p>
      <p>
        The virtual representation of the Industrie 4.0 component
shall contain all relevant information related to the physical,
functional, and behavioral properties of the represented
physical object. One part of the virtual representation is the
Manifest covering characteristic properties, dependencies
between these properties, product, and process related
characteristics, and a formal representation of the function,
and behavior of the component. For more information on
relevant data within the virtual representation see examples
[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>Industrie 4.0 component</p>
      <p>Administration shell
With: virtual representation
With: technical functionality</p>
      <sec id="sec-4-1">
        <title>Things</title>
      </sec>
      <sec id="sec-4-2">
        <title>Thing</title>
      </sec>
      <sec id="sec-4-3">
        <title>Thing</title>
        <p>
          Even if there are strong activities within the Industrie 4.0
initiative to define model structures for the virtual
representation, up to now it is neither clear on which layers of
the production systems Industrie 4.0 components are
meaningful nor which information is relevant within their
virtual representation. Within this paper an attempt is made
towards the identification of relevant component layers and to
assign meaningful information to them required within the
life cycle of a production system. As it is very challenging to
characterize a production system structure that applies to
various industries, considerations, made in this paper, will be
related to manufacturing systems. In addition, the paper will
mainly address information relevant within the engineering
phase of the production system life cycle. The information
relevant within the use phase of the production system life
cycle will be considered in [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. Thus, the paper will follow
two main research questions:
        </p>
        <p>Research question 1: What are relevant layers of
components within a production
system and which are their
identifying characteristics?
Research question 2: What information is relevant on and
characterizing for the different layers
of production system components to
be virtually represented in the
administration shell?</p>
        <p>Therefore, the paper is structured as follows. In Section II
the approach answering the research questions is described.
Section III reflects the analysis of different production system
hierarchies in literature and practice and gives the relevant
layers of the production system hierarchy. Section IV
identifies engineering artifacts usually applied within
production system engineering and assigns them to the layers
of the production system hierarchy. With a summary the
paper ends.</p>
        <p>II.</p>
        <p>APPROACH</p>
        <p>To answer the research questions two main research
activities were performed.</p>
        <p>At first, structures of production systems were considered.
Therefore, a detailed literature survey was conducted
resulting in a set of existing production system structure
representations. In addition, existing production systems
within the automotive industry were reviewed. Based on both
considerations an initial production system component
hierarchy was developed. Afterwards, this hierarchy was
validated by considering production systems of different
manufacturing related domains.</p>
        <p>
          Secondly, the early life cycle phases of production systems
were investigated covering the engineering, and use phase of
a production system. Different engineering areas of expertise
involved in the execution of these phases were analyzed using
the 4D method presented in [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. As a result the engineering
processes have been modeled as a network of engineering
activities executed by humans, creating and exchanging
engineering artifacts, and exploiting engineering tools.
        </p>
        <p>Based on that evaluation, the assignment of engineering
artifacts and the information modeled within them to the
identified component layers was possible. This has led to an
identification of engineering artifacts relevant for the
different layers of Industrie 4.0 components.</p>
        <p>III.</p>
        <p>GENERIC PRODUCTION SYSTEM ARCHITECTURE</p>
        <p>
          One of the main tasks in System Engineering is the
definition of the system architecture. Usually, three main
layers are considered: environment of the system, system of
interest, and system element [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. However, modeling
complex system, it is not easy to understand what level of
detail is needed to define each system element and their
interrelations. Moreover, it should be taken into account that
every system has much more than just one internal structure
and the same elements can be connected to each other in
different ways [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ].
        </p>
        <p>
          As stated in [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ], the response to this challenge will be
domain specific, and within the context of Industrie 4.0,
understanding the relationships among the smart components
and their combined behaviors can be very challenging.
        </p>
        <p>To answer the first research question a literature survey and
an analysis of existing production systems within the
automotive domain was conducted. Following, a hierarchical
structure model was developed and validated to support
system engineering modeling.</p>
        <p>A. Literature Survey</p>
        <p>Production systems have been investigated by various
researchers. Depending on the layers of interest the different
researchers have developed different layer structures. But all
of them have considered only parts of the overall set of
meaningful production system layers possibly of interest to
host Industrie 4.0 components. Within this paper it was
impossible to review all identified structures. Hence, only
classes of structures are named here with only a few
representatives of these structures.</p>
        <p>
          Within literature sets of researchers have considered the
production systems from a company or factory planning
viewpoint. Using this viewpoint the production system is
structured in hierarchy layers like Network, Company, Site,
Segment, System, Cell, and Station focusing on the
manufacturing resource structure of the production system.
Two representatives of this viewpoint are [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] and [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
        </p>
        <p>
          Another set of researchers has taken a production function
oriented view. They considered elements of the hierarchy
providing technological manufacturing functions to the
overall system required to produce a defined product and,
therefore, to execute manufacturing steps. They discuss
hierarchy layers like Cell, Main Function Group, Function
group, and Sub-function Group. Three representatives of this
viewpoint are [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ], [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ], and [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ].
        </p>
        <p>
          A third set of researchers has considered the individual
components of a production system applied to execute the
physical behavior of the production system and its
integration. They address a rather device and mechatronic
oriented perspective discussing layers like Function Units,
Devices and Device Functions. Three representatives of this
viewpoint are [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ], [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ], and [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ].
        </p>
        <p>Summarizing the identified approaches, layers, to be
considered, range from the complete company down to
individual automation devices and mechanical parts. But all
layers are based on a function oriented consideration of the
manufacturing process to be executed.</p>
        <p>
          Especially for automotive industry, the layer structure
needs to address the different sections of automobile
production, i.e. press shop, body shop, paint shop and final
assembly. Similar or equal objects in different sections have
to be located on the same layer within the production system
structure. Also it has to be possible to assign mechanical
objects to hierarchy layers in order to virtually represent
them. As the hierarchy layers in the RAMI 4.0 model are
related to IEC 62264 [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ] /IEC 61512 [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ], the lowest layers
belong to automation domain exclusively, i.e. control and
field devices. Thus, mechanical objects, like safety fences or
mechanical clamps, cannot be assigned to the current layers.
Therefore, a new layer structure is presented in this paper
which suits automotive production system’s needs by
considering its sections as well as its objects and equipment.
        </p>
        <p>B. Hierarchy Layers</p>
        <p>Based on the literature survey, a set of layers was
preliminary identified. For the identification of the different
layers of objects in a production system different criteria were
exploited. The most important criterion is the technical
functionality of the considered objects following the
definition of the technical functionality given in Industrie 4.0.
It refers to the functional part an object is providing to the
overall function of a production system regardless of whether
this function is a value adding function or a support function
for value adding, or even a function required to supervise,
control, diagnose or maintain the production system or parts
of it. Additional criteria are the hardware modularity and
hierarchy of the production system, the control architectures
and control information identified, the relations to human
labor, the relevance within engineering phases and
engineering activities, and the relation to the product
complexity. The initial set of layers identified is given in
Table 1.</p>
        <p>9
8
7
6
5
4
3
2
1</p>
        <p>Layer
Production network
Factory
Production Line
Production Line
Segment
Work Unit
Work Station
Function Group
Component
Construction Element</p>
        <p>Example
VW cooperation
Golf 7 production system
body shop line
vehicle body line
vehicle body plant
welding cell
welding group (robot,
controls, welding
equipment)
welding gun
welding cap</p>
        <p>Here the functional criterion is sketched. In the following
the different identified layers are described in more detail.
functions and the kind of manufactured products, i.e. a
defined variety of related products which can be produced.
1. Construction Element (Layer 1)</p>
        <p>A Construction Element is essential for functionality of
components. It ranges from passive elements like a wire or a
cast metal machine bed to active components like drives,
proximity switches, or welding caps. It may have different
states related to the execution of functionality like a drive
might be switched on and off.
2. Component (Layer 2)</p>
        <p>A Component fulfills a manufacturing method or a support
function. The process is not alterable, but its parameters are
configurable. There are two classes of Components. A
Process Component has influence on product quality and
creates product features. Its parameters like electric current,
holding force, and holding time are configurable. In contrast,
a Control Component processes and transmits data.
3. Function Group (Layer 3)</p>
        <p>A Function Group includes all components to fulfill one
function of a production system, e.g. reshaping, inclusive all
necessary support functions. Several different manufacturing
methods can be integrated in one process, e.g. deep-drawing
and cutting. The different manufacturing methods will not be
applied independently but every time in a fixed combination.
Thus, the function is not reasonable separable. A Function
Group executes a value-added manufacturing process or/and
handling functions.
4. Work Station (Layer 4)</p>
        <p>A Work Station includes one or more value-added
functions and support functions. It provides product quality
by combination of manufacturing process functions and
support functions. Summarized, a Work Station can be seen
as a combination of manufacturing and logistical processes.
5. Work Unit (Layer 5)</p>
        <p>A Work Unit combines Work Stations, i.e. includes several
value-added and support functions. The amount of functions
united in a Work Unit can be reasonable separated from other
processes or Work Units in the surrounding based on its
necessity for product or product part creation. Different
manufacturing processes are involved or only one
manufacturing process with support processes.
6. Production Line Segment (Layer 6)</p>
        <p>The Production Line Segment is characterized by linked
manufacturing functions, support processes and buffers, i.e.
combines Work Units and buffers. The elements of this layer
are used in resource planning. A Production Line Segment
contains all related functions needed to produce a certain
amount of a whole product.
7. Production Line (Layer 7)</p>
        <p>A Production Line is a separation between different
disciplines, e.g. press shop, body shop, and assembly line.
Additional criteria are the production method, e.g. defined
mix or batch production, the type of functions, i.e. related
8. Factory and Production Network (Layers 8 &amp; 9)</p>
        <p>The Factory and the Production Network are characterized
by the combination of all manufacturing, logistical, support
and other functions required for manufacturing a given
number of products by integration of one, a few, or several
input elements. Depending on the emergence of the input
elements, the involved locations, and the ownership of
production systems, we distinguish between Factories and
Production Networks.</p>
        <p>C. Validation</p>
        <p>The developed hierarchy has been validated based on
different student research activities by considering different
practical use cases covering different industries. These use
cases include press shops, body shops, paint shops, final
assembly, and logistics in automotive industry, a hot-rolled
stripe production system of steel industry, a stone cracker
used in mining industry applications, a production system for
roof trusses within wood industry, a micro cuvette production
system within medical device industry, a logistics centre, a
solar park and a gas turbine production system within energy
generation industries. In the case of automotive industry,
physical production objects and equipment were identified
and assigned to the defined layers. Two compulsory
requirements for validation are: 1) all assigned physical
objects comply with the layers’ definitions and 2) same or
similar objects, concerning their functions, found in different
production sections, e.g. robots in press shops and robots in
body shop, have be assigned to the same layer. All assigned
objects in this use case have met all requirements. In other
use cases, a similar validation process was conducted.</p>
        <p>
          For more details on the assignment of different industries’
production equipment to the defined hierarchy see [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ] and
[
          <xref ref-type="bibr" rid="ref25">25</xref>
          ].
        </p>
        <p>Based on these validations the authors are convenient, that
the developed hierarchy can get a broad application.</p>
        <p>
          To support the conceptual modeling of a complex system
the system engineer need to establish a framework that
facilitates understanding of the problem and to define the
relevant information needed for the process analysis [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ]. In
SE these “boundary objects” [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ] are defined as artifacts that
support the system analysis generally including requirements,
system information, use cases, logical scenarios, functional
models, simulation tests and trade studies [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ][
          <xref ref-type="bibr" rid="ref24">24</xref>
          ].
        </p>
        <p>To answer the second research question the relevant
engineering artifacts have to be assigned to the different
layers of the production system hierarchy.</p>
        <p>A. Artifact Identification</p>
        <p>
          To identify the necessary information relevant for the
different layers of the production system hierarchy detailed
process analysis of the engineering processes of the technical
systems used for hierarchy validation following the analysis
methods described in [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] have been executed. As a result the
following engineering artifacts have been identified as
relevant for the Industrie 4.0 components within
manufacturing industries (and especially within the
automotive industry). As there are myriad of different
detailed engineering artifacts only major artifact types will be
named here.
1. Requirements
        </p>
        <p>The set of requirements covers initial requirements coming
from the product design like production process
specifications, e.g. a welding spot list, coming from
economical departments like maximal cost values, and
coming from legal authorities.</p>
        <p>Block layouts define the set of manufacturing resources and
functional units within a production system and put them in a
logical interrelation.</p>
        <p>2D layouts represent the construction of the production
system in more detail following a “paper work” strategy.
There are concept layouts, rough layouts and other 2D layouts
for more detailed information like a transport system related
2D conveyor system layout.</p>
        <p>3D layouts provide a more detailed representation of the
general concept of the production system. They remain in a
conceptual state covering the identification of production
system components and functional units and their
geographical locations. There are for example 3D rough
layouts, 3D layouts including electronics.
2. Basic Specifications</p>
        <p>The basic specifications contain general definitions of
production system components. They cover for example the
component quantity structures, general interrelation structures
between product defined processes and resource structures
like clamping concept and specifications.
3. Behavior Models</p>
        <p>Special types of specifications are behavior models. They
describe the production system behavior ranging from very
abstract models like Gantt charts to more detailed models like
Impulse diagrams down to simulation based decision models.
4. CAD Construction</p>
        <p>The CAD construction covers the detailed mechanical
construction of the production system often named MCAD.</p>
        <p>The electrical construction covers the detailed electrical
engineering of the production system often named ECAD.</p>
        <p>The part list covers the detailed definition of all parts of the
production system which have to be purchased.</p>
        <p>Simulation models are usually developed for the validation
of special production system properties related to production
system behavior. For example virtual commissioning or
accessibility models are often developed and applied.</p>
        <p>Control programs subsume the complete set of software
developed to control the production system. Within this
artifact set there are especially the HMI, PLC, and robot
programs.</p>
        <p>The power supply concept represents the detailed
engineering of the supply of necessary energy to all elements
of the production system.</p>
        <p>The fluidic plans cover the engineering of the hydraulic
and pneumatic systems within the production system.</p>
        <p>The safety concept contains the detailed engineering of all
safety related features.</p>
        <p>All the named artifact types are not independent from each
other. Figure 5 provides an overview of the dependencies
between different artifact types as identified within
automotive industry.</p>
        <p>B. Artifact Assignment</p>
        <p>The different identified engineering artifacts can be
mapped to the different layers of the production system
hierarchy by considering the engineering activities within the
engineering life cycles they are involved in and the hierarchy
levels they address. As a result the mapping presented in
Figure 6 can be concluded.</p>
        <p>At the Construction Element layer the most detailed
engineering information are relevant. They include part lists,
mechanical and electrical specification, CAD construction,
and electrical construction.</p>
        <p>Similar to Construction Element layer at Component layer
detailed engineering information is covered. Here basic
specifications and behavior models like joint locations and
clamping concepts, 3D layouts, part lists, mechanical and
electrical specification, CAD construction, control programs,
powers supply concepts, safety concept, electrical
construction, detailed behavior models, and simulation
models can be found.</p>
        <p>At Function Group layer the engineering information are a
bit more abstract, e.g. basic behavior models, 3D layouts,
mechanical and electrical specifications, control programs,
fluidic plans, powers supply concepts, safety concept,
electrical construction, detailed behavior models, and
simulation models.</p>
        <p>At Work Station layer also rough and detailed engineering
information can be found. Here basic behavior models, 3D
plans, 3D layouts, mechanical and electrical specifications,
control programs, fluidic plans, powers supply concepts,
safety concept, electrical construction, detailed behavior
models, and simulation models are relevant.</p>
        <p>At Work Unit layer the level of detail of engineering
information gets reduced. Here we can find basic behavior
models, 2D layouts, mechanical and electrical specifications,
3D layouts, and safety concepts.</p>
        <p>At Production Line Segment layer only 2D layouts are still
relevant. Finally, at Production Line layer requirements and
2D layouts are considered.</p>
        <p>For Factory and Production Network layers the analysis has
not provided engineering information of interest. But
following usual engineering processes only requirements and
economical and technical constraints (so called propositions)
might be relevant on these layers.</p>
        <p>In order to enhance the System Engineering approach to
model the new generation of production system and their
smart components, within this paper an attempt has been
made towards the identification of relevant component layers
and assignment of meaningful information to them required
during the life cycle of a production system within the
Industrie 4.0 context.</p>
        <p>It was possible to identify relevant layers of components
within a production system as well as to answer the question
which information is relevant on the different layers of
manufacturing components to be virtually represented in the
management shell. Within future work the authors will extend
and improve the identification properties as well as the
information relevant for Industrie 4.0 component
management shell for example related to component reuse
and will try to model this information on a prototypical level.
ACKNOWLEDGMENT
The authors express their gratitude to all students directly or
indirectly involved within the validation of the developed
hierarchy of components within a production system.
7</p>
        <p>Production Line
m6
e
t
s
y
S
n 5
o
i
t
c
u
d
ro 4
P
f
o
s
r 3
e
y
a
L
2
1</p>
        <p>Production Line
Segment
Work Unit
Work Station
Function Group
Component
 Process
 Control
Construction
Element
.)
c
s te
iisn tee
o
t im
op l</p>
        <p>c
rop (cy
y
d
o
b
rca )ts
f e
o eh
iilcyub isong
it f</p>
        <p>t
d s
rop (en
tyo isn
iiiltsb ltcaoo
s n
e t
cca ijo</p>
        <p>t
lltcykauoob ltccyaeuoonp</p>
        <p>D
2</p>
        <p>e
fo iuq
n hn
ig c
s e
lraed rtyo
e ve
n n
eg co
fto tso
en sp
m gn
n i
issag ledw
lrtyauuoogh3D )(rrssceeuo iiilttzauon ilssyaan rtttcaahnG
ilcapngm tcceonp
t
n
e
m
ith iup
w eq
tu l</p>
        <p>a
yo i
c
rc
la t
3D lee
t
u
o
y
a
l
h
g
u
o
r
D
2
e
u
q
i
n
h
rtc
e
o
y
e
v
n
o
tc
u
o
y
a
l
D
2
e
rtc
u
rtsu
itty rts
n a
a p
uq fo
so
n
i
iiftcc
a
e
p
s
l
a
c
i
n
a
h
c
e
m
Engineering Life Cycle
illlrcyaaaudpnh lrtsccyeeuoonppppw fttsccyaeeonp illlrtccaaeepn ilfssyaaon iiilrtssccyaeb
g
n
i
m
m
ng rag
im r</p>
        <p>o
ram IpM
og H
r
p
ing LPC
rts ilrtscaeuhpm ilrrff-aeoopngmm
a
p
ilfts
o
g
n
i
n
o
ii
s
s
m
m
o
c
l
a
u
irtv</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>H.</given-names>
            <surname>Kagermann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Wahlster</surname>
          </string-name>
          , J. Helbig (Editors):
          <article-title>Recommendations for implementing the strategic initiative INDUSTRIE 4.0 - Securing the future of German manufacturing industry</article-title>
          ,
          <source>Final report of the Industrie 4</source>
          .0 Working Group,
          <year>April 2013</year>
          , http://www.acatech.de/fileadmin/user_upload/Baumstruktur_nach_We bsite/Acatech/root/de/Material_fuer_Sonderseiten/Industrie_4.0/Final_ report__
          <source>Industrie_4</source>
          .0_accessible.pdf,
          <source>last access</source>
          <year>2016</year>
          -
          <volume>02</volume>
          -01.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <source>[2] Arbeitsgruppen der Plattform Industrie 4.0: Umsetzungsstrategie Industrie 4.0 - Ergebnisbericht der Plattform Industrie</source>
          <volume>4</volume>
          .0,
          <string-name>
            <surname>April</surname>
            <given-names>2015</given-names>
          </string-name>
          , https://www.bmwi.de/BMWi/Redaktion/PDF/I/industrie-40
          <string-name>
            <surname>-</surname>
          </string-name>
          verbaendeplattform-bericht,property=pdf,bereich=bmwi2012, sprache=de,rwb=true.pdf,
          <source>last access</source>
          <year>2016</year>
          -
          <volume>02</volume>
          -01 (in German).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>T.</given-names>
            <surname>Bauernhansl</surname>
          </string-name>
          , M. ten
          <string-name>
            <surname>Hompel</surname>
          </string-name>
          , B. Vogel-Heuser (Editors):
          <source>Industrie 4</source>
          .0 in Produktion, Automatisierung und Logistik: Anwendung, Technologien, Migration. Wiesbaden, Springer Vieweg,
          <year>2014</year>
          (in German).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>C.</given-names>
            <surname>Manzei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Schleupner</surname>
          </string-name>
          ,
          <string-name>
            <surname>R.</surname>
          </string-name>
          <article-title>Heinze: Industrie 4.0 im internationalen Kontext</article-title>
          , VDE Verlag,
          <year>2016</year>
          (in German).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <source>[5] VDI/VDE - GMA Fachausschuss 7.21 „Industrie 4.0“: VDIStatusreport Industrie 4</source>
          .
          <fpage>0</fpage>
          - Wertschöpfungsketten, VDI, Frankfurt/Main, April
          <year>2014</year>
          , http://www.vdi.de/fileadmin/vdi_de/redakteur_dateien/gma_dateien/V DI_
          <article-title>Industrie_4.0_Wertschoepfungsketten_2014.pdf (in German)</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6] VDI/
          <string-name>
            <surname>VDE-Gesellschaft</surname>
            <given-names>Mess</given-names>
          </string-name>
          - und
          <source>Automatisierungstechnik - Fachausschuss 7.21 „Industrie 4.0“: Status Report: Reference Architecture Model Industrie 4</source>
          .0 (
          <issue>RAMI4</issue>
          .0)
          <issue>,</issue>
          <year>July 2015</year>
          , http://www.zvei.org/Publikationen/GMA-Status
          <source>-Report-RAMI-40- July-2015</source>
          .pdf.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>J.</given-names>
            <surname>Kiefer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Baer</surname>
          </string-name>
          , and H. Bley:
          <article-title>Mechatronic-oriented Engineering of Production systems Taking the Example of the Body Shop</article-title>
          , 13th CIRP International Conference on Life Cycle Engineering, Leuven, Belgium, Proceedings,
          <year>June 2006</year>
          , http://www.mech.kuleuven.be /lce2006/064.pdf,
          <source>last access</source>
          <year>2016</year>
          -
          <volume>02</volume>
          -01.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>L.</given-names>
            <surname>Hundt</surname>
          </string-name>
          <article-title>: Durchgängiger Austausch von Daten zur Verhaltensbeschreibung von Automatisierungssystemen</article-title>
          ,
          <source>PhD Thesis</source>
          , Faculty of Mechanical Engineering,
          <string-name>
            <surname>Otto-</surname>
          </string-name>
          von-Guericke University Magdeburg,
          <year>April 2012</year>
          (in German).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>J.</given-names>
            <surname>Pfrommer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Stogl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Aleksandrov</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Schubert</surname>
          </string-name>
          ,
          <string-name>
            <surname>B.</surname>
          </string-name>
          <article-title>Hein: Modelling and Orchestration of Service-Based Production systems via Skills</article-title>
          ,
          <source>IEEE 19th Conference on Emerging Technologies and Factory Automation (ETFA</source>
          <year>2014</year>
          ), Barcelona, Spain, Proceedings,
          <year>September 2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M.</given-names>
            <surname>Bartelt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Schyja</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Kuhlenkötter</surname>
          </string-name>
          :
          <article-title>More than a Mockup - SmartComponents: reusable fully functional virtual components from scratch, within Production Engineering (</article-title>
          <year>2014</year>
          -12), Volume
          <volume>8</volume>
          , Issue 6, pp
          <fpage>727</fpage>
          -
          <lpage>735</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>J.</given-names>
            <surname>Zawisza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Hell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Röpke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Lüder</surname>
          </string-name>
          ,
          <string-name>
            <surname>N.</surname>
          </string-name>
          <article-title>Schmidt: Generische Strukturierung von Produktionssystemen der Fertigungsindustrie, 17</article-title>
          . Branchentreff der Mess- und
          <string-name>
            <surname>Automatisierungstechnik</surname>
          </string-name>
          (
          <year>Automation 2016</year>
          ), Baden-Baden, Proceedings, VDI-Verlag, June (in German).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>T.</given-names>
            <surname>Schäffler</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Foehr</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Lüder</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.</surname>
          </string-name>
          <article-title>Supke: Engineering Process Evaluation - Evaluation of the impact of internationalisation decisions on the efficiency and quality of engineering processes</article-title>
          ,
          <source>22nd IEEE International Symposium on Industrial Electronics (ISIE) Taipei</source>
          , Taiwan, Proceedings, May
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13] ISO/IEC/IEEE 15288:
          <year>2015</year>
          ,
          <string-name>
            <given-names>System</given-names>
            <surname>Engineering - System Life</surname>
          </string-name>
          Cycle Processes,
          <source>International Standards Organizaton</source>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <article-title>SE^2 Telescope Modeling Challenge Team: Cookbook for MBSE with SysML, issue 1</article-title>
          , http://www.omgwiki.org/MBSE/doku.php?id=mbse:telescope,
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <article-title>INCOSE: Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities, version 4.0</article-title>
          . Hoboken, NJ, USA: John Wiley and Sons, Inc,
          <source>ISBN: 978-1-118-99940-0</source>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <surname>H.-P. Wiendahl</surname>
          </string-name>
          et al:
          <article-title>Changeable Manufacturing - Classification, Design and Operation. Annals of the CIRP (</article-title>
          <year>2007</year>
          ), Volume
          <volume>56</volume>
          /2, pp.
          <fpage>783</fpage>
          -
          <lpage>809</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>B.</given-names>
            <surname>Scholten</surname>
          </string-name>
          :
          <article-title>The Road to Integration - A guide to applying ISA-95 standard in manufacturing</article-title>
          ,
          <source>ISA - Instrumentation, Systems, and Automation Society</source>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <given-names>J.</given-names>
            <surname>Kiefer</surname>
          </string-name>
          <article-title>: Mechatronikorientierte Planung automatisierter Fertigungszellen im Bereich Karosseriebau</article-title>
          ,
          <source>PhD Thesis</source>
          , Universität des Saarlandes,
          <source>Schriftenreihe Produktionstechnik, Band</source>
          <volume>43</volume>
          ,
          <year>2007</year>
          (in German).
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>F.</given-names>
            <surname>Meling</surname>
          </string-name>
          <article-title>: Methodik für die Rekombination von Anlagentechnik</article-title>
          ,
          <source>PhD Thesis</source>
          , TU München,
          <year>2012</year>
          (in German).
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>M.</given-names>
            <surname>Weyrich</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Steden</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Wolf</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>Scharf: Identification of Mechatronics Units based on an Example of a Flexible Customized Multi Lathe Machine Tool</article-title>
          ,
          <source>IEEE International Conference on Emerging Technologies and Factory Automation (EFTA</source>
          <year>2011</year>
          ),
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>J.</given-names>
            <surname>Sitte</surname>
          </string-name>
          , P. Winzer:
          <article-title>Demand-Compliant Design</article-title>
          .
          <source>IEEE Transactions on Systems, Man, and Cybernetics - Part A: Systems and Humans</source>
          <volume>41</volume>
          (
          <year>2011</year>
          ),
          <source>No. 3</source>
          , pp.
          <fpage>434</fpage>
          -
          <lpage>448</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>U.</given-names>
            <surname>Lindemann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Maurer</surname>
          </string-name>
          , T. Braun:
          <article-title>Structural complexity management: An approach for the field of product design</article-title>
          . Berlin: Springer,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>J. S.</given-names>
            <surname>Topper</surname>
          </string-name>
          and
          <string-name>
            <given-names>N. C.</given-names>
            <surname>Horner</surname>
          </string-name>
          ,
          <article-title>Model-Based System Engineering in Support of Complex Systems Development</article-title>
          ,
          <source>John Hopkins APL Technical Digest</source>
          , volume
          <volume>32</volume>
          , number 1,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>J.</given-names>
            <surname>Dahmann</surname>
          </string-name>
          , G. Rebovich,
          <string-name>
            <given-names>J. A.</given-names>
            <surname>Lane</surname>
          </string-name>
          and
          <string-name>
            <given-names>R.</given-names>
            <surname>Lowry</surname>
          </string-name>
          , System Engineering Artifacts for Sos,
          <source>IEEE Aerospace and Electronic Systems Magazine</source>
          ,
          <volume>26</volume>
          (
          <issue>1</issue>
          ):
          <fpage>22</fpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>H.</given-names>
            <surname>Röpke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Hell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Zawisza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Lüder</surname>
          </string-name>
          ,
          <source>N. Schmidt: Identification of “Industrie 4</source>
          .0”
          <string-name>
            <given-names>Component</given-names>
            <surname>Hierarchy Layers</surname>
          </string-name>
          ,
          <source>2016 IEEE 21th Conference on Emerging Technologies and Factory Automation (ETFA)</source>
          , Berlin,
          <year>September 2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <article-title>IEC 62264-1: Enterprise-control system integration - Part 1: Models and terminology</article-title>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          <source>[27] IEC 61512-1: Batch Control - Part 1: Models and terminology</source>
          ,
          <year>1997</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>