Available online atonline

Available www.sciencedirect.com
at www.sciencedirect.com

ScienceDirect
ScienceDirect
Procedia CIRP 00 (2017)
Procedia 000–000
CIRP 96 (2021) 207–212
CIRPe 2020 – 8th CIRP Global Web Conference – Flexible Mass Customisation
www.elsevier.com/locate/procedia
CIRPe 2020 – 8th CIRP Global Web Conference – Flexible Mass Customisation
Process-Driven Approach
CIRPe 2020
CIRPe 2020 within
– 8th CIRP Global
– 8th CIRP Global the
Web
Web Engineering
Conference
Conference
– FlexibleDomain by Combining
Mass Customisation
– Flexible Mass Customisation
Process-Driven
Business Process Approach
Model within the Engineering
and Notation (BPMN) with Domain by Combining
Process Engines
Process-Driven
Business Process
Process-Driven Approach
Model
Approach within
and
within the
the Engineering
Notation (BPMN)
Engineering Domain
with
Domain by
Process
by Combining
Engines
Combining
28th CIRP Design Conference, May 2018, Nantes, France
Business
Business Process
Eike Schäffera, Model
*, Volker Stiehlband Notation
, Peter
Process Model and Notation K. Schwab(BPMN)
c with
, Andreas Mayra Process Engines
, Josef Lierhammera,
(BPMN) with Process Engines
A newEike Eike Schäffera,*, Volker Stiehlb, PeterJörg
methodology to analyze K. Schwab
Frankeac, Andreas Mayra, Josef Lierhammera,
the
Schäffera,a,*, Volker Stiehlbb, Peter K. functional
Jörg Schwab
Franke
and physical architecture of
ac, Andreas Mayra, Josef Lierhammera,
Eike Schäffer *,and
Volker Stiehl
Systems,,Friedrich-Alexander
Peter K. Schwab a , Andreas
c
MayraEgerlandstr.
, Josef Lierhammer ,
7, Erlangen 91058,aGermany
existing
Institute
products
for Factory Automation
for an
Production
assembly Jörgoriented
University
product 10, 85049family
Erlangen-Nuremberg,
identification
a

Faculty of Computer
b
Science, Ingolstadt University Franke
of Technology, Esplanade Ingolstadt, Germany
a
Chair of Computer Science
c Jörg Franke
Institute for Factory Automation and Production Systems, Friedrich-Alexander a
University Erlangen-Nuremberg, Egerlandstr. 7, Erlangen 91058, Germany
6 (Data Management), Friedrich-Alexander University Erlangen-Nuremberg, Martensstraße 3, Erlangen 91058, Germany
a b
Faculty ofand
Institute for Factory Automation Computer Science,
Production Ingolstadt
Systems, University of Technology,
Friedrich-Alexander University Esplanade 10, 85049 Ingolstadt,
Erlangen-Nuremberg, Germany
Egerlandstr. 7, Erlangen 91058, Germany
a c
Chair for
Institute of Computer Science
Factory Automation
b
Paul Stief *, Jean-Yves Dantan, Alain Etienne, Ali Siadat
Faculty6of(Data
and Management),
Production
Computer Friedrich-Alexander
Systems,
Science, University
Friedrich-Alexander
Ingolstadt University of Erlangen-Nuremberg,
University
Technology, Martensstraße
Erlangen-Nuremberg,
Esplanade 10, 85049 3, Erlangen
Egerlandstr.
Ingolstadt, 91058,
7, Erlangen
Germany Germany
91058, Germany
c b
Faculty6of(Data
Chair of Computer Science Computer Science, Ingolstadt
Management), University of
Friedrich-Alexander Technology,
University Esplanade 10, 85049
Erlangen-Nuremberg, Ingolstadt, Germany
Martensstraße 3, Erlangen 91058, Germany
* Corresponding
Chair author. Tel.: +4969131
of Computer 85-28314; fax: +49 9131 302825; E-mail address:Erlangen-Nuremberg,
eike.schaeffer@faps.fau.de
NationaleScience (Data Management),
et Métiers,Friedrich-Alexander University Martensstraße 3, Erlangen 91058, Germany
c
École Supérieure d’Arts Arts et Métiers ParisTech, LCFC EA 4495, 4 Rue Augustin Fresnel, Metz 57078, France
* Corresponding author. Tel.: +49 9131 85-28314; fax: +49 9131 302825; E-mail address: eike.schaeffer@faps.fau.de
* Corresponding author. Tel.: +49 9131 85-28314; fax: +49 9131 302825; E-mail address: eike.schaeffer@faps.fau.de
* Corresponding
* Corresponding author. Tel.:Tel.:
author. +33+49
3 87 37 54
9131 30; E-mail
85-28314; +49 9131paul.stief@ensam.eu
fax: address: 302825; E-mail address: eike.schaeffer@faps.fau.de
Abstract
Abstract
Digitization
Abstract
within the framework of Industry 4.0 is considered the biggest and fastest driver of change in history of manufacturing
industry.
Abstract
Abstract While thethe
Digitization within sizeframework
of a company is becoming
of Industry less essential,
4.0 is considered the the ability
biggest andtofastest
adaptdriver
quickly
of to changing
change market
in history of conditions and
manufacturing
new technologies
industry. While
Digitization theisthe
within more
size ofimportant
framework of than
a company ever.4.0
Industry This
is becoming trendessential,
less particularly
is considered the the applies
ability
biggest to
andto the companies’
adapt
fastest quickly
driver of to software
changing
change landscapes,
market
in history where indi-
of conditions and
manufacturing
vidual
In today’s sub-processes
Digitization
business
new technologies
industry. within
While theistheand
environment,
more
size ofservices
frameworkathe must
of
trend
important
company isbebecoming
Industry
towards
than orchestrated,
ever. 4.0
more isproduct
This seamlessly
considered the and
variety
trendessential,
less particularlytheintegrated,
biggest andto
customization
applies
ability to and
the iteratively
fastest
adapt isdriver
unbroken.
companies’
quickly renewed
of to
change
Due to
software
changing according
inthis
history to the
development,
landscapes,
market whereever-in-
of conditions
manufacturing
theindi-
need
and of
creasing
agileindustry.
and
vidual
new user
While requirements.
reconfigurable
sub-processes
technologies the size of
production a
and services
is more However,
company
systems
importantmust inflexible,
is becoming
emerged
thanbeever. toclosed
less
cope
orchestrated, monolithic
essential,
with
This trendseamlesslyvarious software
the ability
products
particularlyintegrated, applications
to
and
applies toand adapt
product as
quickly well
to
families.
the iteratively
companies’renewed asToself-programmed
changing
design market
softwareaccording and stand-alone
conditions
optimize
landscapes, to the
where and
production
ever-in-
indi-
tools
new
systems
creasing
vidual that
well are
technologies
as as difficult
to is
choose
user requirements.
sub-processes more to integrate
important
the
and services optimal
However, are
than still
product
mustinflexible,predominant
ever. This
matches, trend in
product
closed monolithic
be orchestrated, the engineering
particularly
analysis
seamlesslysoftware applies
methods
integrated, domain.
toarethe A
needed.
applications complete
companies’
Indeed,
as well
and iteratively reimplementation
software
most of landscapes,
the
as self-programmed
renewed known
according to the of existing,
where
methods indi-
stand-alone aim to
ever-in-
proprietary
vidual
analyze a product
tools
creasingthat engineering
sub-processes
are
user ordifficult and
one product
requirements. tools
to and their
services
family
integrate
However, must
on the
are integration
still into monolithic
be orchestrated,
physical level.
predominant
inflexible, closed seamlessly
Different applications
in theproduct
monolithic integrated, of and
families,
engineering
software large
however,
domain.
applications software
iteratively
may
A complete
as well providers
renewed
differ largelyis often
according notto
in terms
asreimplementation
self-programmed economically
of the
of ever-in-and
number
existing,
stand-alone
feasible,
creasing
nature
proprietary
tools especially
thatuser
of components.
engineering
are for small
requirements.
This
difficult fact
tools
to and their
However,
impedes
and
integrate medium-sized
inflexible,
anintegration
are efficient machinery
closed
comparison inand
into monolithic
still predominant theplant
monolithic
and choice manufacturers.
software of largeIn
applications
of appropriate
applications
engineering domain. Athis
as context,
product
software well
family
complete the
providers so-called
asreimplementation
self-programmed
combinations
is often not Process-Driven
for stand-alone
theexisting,
production
economically
of
Approach
tools
system. that
feasible,
proprietary (PDA)
are
A newespecially offers
difficult
methodology
engineering to
is
for smalla sustainable
integrate
proposed
tools areand
to analyze
and their
and medium-sizedtool-neutral
still predominant
existing
integration opportunity
into products
machinery in the
andinplant
monolithic for
view process
engineering
of their ofand
domain. tool
functional
manufacturers.
applications largeIn Aorchestration,
complete
and context,
this
software physical enabling
reimplementation
architecture.
the so-called
providers an
is often noteasy
The integration
of
aim existing,
is to cluster
Process-Driven
economically
of individual
proprietary
theseApproach
products
feasible, in software
engineering
new
(PDA)
especially for applications
assembly
offers tools
small and
and their
oriented
a sustainable byand
productconsistent
integration
medium-sized families utilization
into monolithic
for the
tool-neutral
machinery of plant
the
optimization
opportunity
and separation
applications
for of of
existing
process ofassembly
and
manufacturers. concerns
large
toolsoftware
In principle.
lines providers
and
orchestration,
this context,thetheThe is PDA,
often
creation
enabling of
so-called originating
annot economically
future
easy from
reconfigurable
integration
Process-Driven
business
feasible,
assembly
of individual
Approach informatics,
especially
systems. Based
software
(PDA) onisapplications
for
offers amainly
small
Datum and based
Flow
sustainable byandon
medium-sized
Chain, the standardized
machinery
the physical
consistent
tool-neutral and
structure
utilization machine-executable
plant
of of
opportunity thethe manufacturers.
products
separation
for process and is visual
In
ofanalyzed.
concerns
tool modeling
thisFunctional
context, the
principle.
orchestration, language
subassemblies
The
enablingPDA, anBusiness
so-called Process
Process-Driven
are integration
identified,
originating
easy fromand
Model
Approach
a functional
business
of and
individual Notation
(PDA)
analysis
informatics,
software (BPMN).
isoffers
performed.amainly
isapplications Using
sustainable
Moreover,
basedthe
by and
onsemantic
hybrid
the
consistent enhancements
atool-neutral opportunity
functional
standardized
utilization and
and found
for
physical in architecture
version
process
machine-executable
of the separation of 2.0,
and toolBPMN
graph
visual
concerns is not justenabling
orchestration,
(HyFPAG)
modeling
principle. used
is the
language
The to model
an
output
PDA, easy the
which
Business
originatingbusiness
integration
depicts
from the
Process
processes
of individual
similarity
Model
businessbetween
and but also
software
product
Notation
informatics, to(BPMN).
model
is mainly and
applications
families execute
by
bybased
Usingproviding
theon the
consistentintegration
thedesign
semantic supportprocesses
utilization
enhancements
standardized toofboth,
and the
found between
separation
production different
in version
machine-executable of
system
2.0, systems.
concerns
planners
BPMN
visual After
principle.
and
is not
modeling the
The
product
just PDA
usedPDA,
language has
designers.
to model already
originating been
from
Anbusiness
the
Business illustrative
Process
successfully
business
processes
example
Modelof aand applied
informatics,
but also tois
nail-clipper
Notation tois
large-scale
model
used
(BPMN). mainly
toand projects
based
execute
explain
Using the
the in business
onsemantic
the
the standardized
integration
proposed informatics,
enhancements and An
processes
methodology. itindustrial
found is now
between being
machine-executable transferred
different
case
in version visual
study
2.0, systems.
on two
BPMN to the
modeling engineering
justlanguage
After
is product
not the
usedPDA
families domain.
has theAs
ofBusiness
already
steering
to model shown
Process
been of
columns
business
in this paper,
Model
thyssenkrupp
processes and
successfullyPresta
but PDA
Notation
applied
France
also allows
to(BPMN).
tomodel to orchestrate
islarge-scale
then Using
and the to
projects
carried out
execute thethe
indifferent
semantic
business
give a first processes
enhancements
informatics,
industrial
integration infound
engineering
in version
it between
is now
evaluation
processes ofbeing
the and to integrate
2.0, BPMN
transferred
proposed
different isthe
to
approach.
systems. not
the underlying
justtheusedPDA
engineering
After tosoftware
model
domain. tools,
theAs
has already such
business
shown
been
as e-mail
processes
in this
© 2017 Thepaper,or spreadsheet
but
Authors.
successfully also
PDA to model
allows
Published
applied applications,
to and
byorchestrate
to large-scale Elsevier engineering
execute
B.V.
projects the tools,
integration
theindifferent or
businessprocesses custom
processes
informatics, microservices,
between
in engineering
it is now being using
different
andtransferredstandardized
systems.
to integratetothe After interfaces
the
theunderlying PDA like
engineeringsoftware has REST
already
domain.tools, API.
As shown In
been
such
doing
as this
in e-mail
Peer-review so,
successfully engineering
applied
or spreadsheet
under
paper, toprocesses
large-scale
allowsapplications,
responsibility
PDA can be
projects
tooforchestrate made in
engineering
the scientific more
thecommittee transparent,
business
tools,
different monitored,
informatics,
or custom
of the
processes28thinCIRPit is now and
being
microservices, optimized
andusing
Design Conference
engineering by
transferred means
to the
standardized of appropriate
engineering
interfacessoftware
2018. the underlying
to integrate key
domain. figures.
like REST As
tools, The
shown
API. In
such
concept
in this
doing
as isor
so,
e-mail validated
paper,
engineering byprocesses
PDA allows
spreadsheet aapplications,
prototypical
to orchestrateimplementation
the different
can beengineering
made ofor
more tools, a minimum
processes
transparent, functional
in engineering
monitored,
custom PDA
and architecture
to integrate
and optimized
microservices, using the for
by means
standardized the engineering
underlying
ofinterfacessoftware
appropriate key
like domain.
tools,
figures.
REST API.such
The
In
as e-mail
concept
doing
Keywords: or
Assembly;spreadsheet
so,isengineering
validated
Designby applications,
a prototypical
processes
method; engineering
beimplementation
can identification
Family tools, or custom
of a minimum
made more transparent, microservices,
functional
monitored, using standardized
PDA architecture
and optimized by meansfor interfaces
of the like
engineering
appropriate REST API.
key domain.
figures. In
The
doing
© 2020
concept so,
The engineering
Authors,
is validated processes
Published
by by can be
Elsevier
a prototypical made
B.V. more
implementation transparent, monitored, and optimized by means of appropriate key
of a minimum functional PDA architecture for the engineering domain. figures. The
© 2021
This is an
concept The
isopenAuthors.
validated Published
accessPublished
article
by bytheElsevier
under
a prototypical B.V.
CCimplementation
BY-NC-ND license
of a(http://creativecommons.org/licenses/by-nc-nd/4.0/)
minimum functional PDA architecture for the engineering domain.
© 2020 The
Thisreview Authors,
is an open access by Elsevier
article underofthe CC B.V.
BY-NC-ND licensethe
(https://creativecommons.org/licenses/by-nc-nd/4.0)
Peer
This is an under
open the responsibility
access article under the
thethe scientific
CCscientific
BY-NC-ND committee
license of CIRPe 2020 Global Web Conference
(http://creativecommons.org/licenses/by-nc-nd/4.0/)
© 2020 The
Peer-review Authors,
under Published
responsibilityby of
Elsevier B.V. committee of the 8th CIRP Global Web Conference – Flexible Mass Customisation
© 2020
This The
1. Introduction
Peer is
review Authors,
under
an open Published by
the responsibility
access Elsevier
of the
article under the B.V.
CC scientific
BY-NC-ND committee
license of of the
the CIRPe 2020product
Global Web range and characteristics manufactured and/or
Conference
(http://creativecommons.org/licenses/by-nc-nd/4.0/)
Keywords:
This is Process-Driven
an open access Approach;
article underPDA;
the BPMN;
CC engineering;
BY-NC-ND process
license engine; architecture; orchestration; Industry 4.0
(http://creativecommons.org/licenses/by-nc-nd/4.0/)
Peer review under the responsibility of the scientific committee of the CIRPe 2020 Global
assembled Websystem.
in this ConferenceIn this context, the main challenge in
Peer reviewProcess-Driven
Keywords: under the responsibility of the
Approach; PDA; scientific
BPMN; committee
engineering; of the
process CIRPe
engine; 2020 Global
architecture; Web Conference
orchestration; Industry 4.0
Due to the fast development in the domain of modelling and analysis is now not only to cope with single
Keywords: Process-Driven Approach; PDA; BPMN; engineering; process engine; architecture; orchestration; Industry 4.0
communication and an Approach;
Keywords: Process-Driven ongoingPDA; trend
BPMN;ofengineering;
digitizationprocessand products, orchestration;
engine; architecture; a limited product range or existing product families,
Industry 4.0
1. Introduction
digitalization, manufacturing enterprises are facing important butcommunication
also to be able errors,
to analyze missing
and totransparency,
compare productsand thus to
to define
challenges in today’s market environments: a continuing
1. Introduction newhigh costs and
product families.
communication technical
errors, debt
It can for companies
be observed
missing [4].
that classical
transparency, and thus existing
to
Despite
1. Introduction
tendency towards the reduction
increasing of importance of data continuity
product development timesand and product
highContinuous
families
communication
costs and
are consistent
regrouped
errors,
and technical missingapproaches
in
debt for function applying
of
transparency,
companies andthe
clients
[4]. sepa-
orthus
features.
to
1. Introduction communication errors, missing transparency, andthethus
consistency
Despite
shortened product within
the Industry
increasing
lifecycles. In4.0,
importanceprocess
addition, modeling
ofthere
data and exe-
continuity
is an increasingand ration
high ofassembly
costs
Continuous
However, concerns
and principle
and technical
consistent
oriented while
debtproduct
for using
companies
approaches one single
[4].
applying
families are hardly toto
process
sepa-find.
cution high costsconcerns
and technical debt for companies [4].
ofiscustomization,
Despite
consistency
demand often
the still Industry
within realized
increasing beingusing
importance
4.0, different,
atprocess
the of data
same non-continuous
continuity
modeling
time inand and
exe-
a global modeling
OnContinuous
ration language
theofproduct which
andfamily
consistent
principle can also
approaches
while
level, be compiled,
using
products applying
one are
single
differ the rather
sepa-
process
mainly in two
Despite
modeling
consistency the increasing
languagues
within andimportance
still Industry implementation
4.0, processof data continuity
tools. From and
the Continuous
unknown, evenand consistent
in the emerging approaches
domain of applying
business the sepa-
informat-
cution
competition is with
often realized
competitors using
all over themodeling
different,
world. and exe-
non-continuous
This trend, ration
modeling
main of concerns
language
characteristics: principle
which
(i) while
can
the number alsousing one single
becomponents
of compiled, are process
and rather
(ii) the
consistency
management
cution
modeling is often within
and still
languagues Industry
process
realized 4.0,
andexpert
using process
view, modeling
process
different,
implementation and
non-continuous
tools. From exe-
specification, the ration
modeling
unknown, of concerns
ics [1,2]. language
Especially
even principle
in the which while
in engineering,
can domain
emerging using
also be one single
successfully
compiled,
of business are process
imple-
rather
informat-
which is inducing
cution is often the
still development
realized using from macro to micro type of components (e.g. mechanical, electrical, electronical).
development
modeling
management and
languagues
and documentation
process andexpert isdifferent,
implementation non-continuous
primarilytools.
pursuedFrom [1,2].
the modeling
mented
unknown, language
approaches
even in thewhich
for can domain
also beprocess
instandardized
emerging compiled,
of are
modeling
business rather
informat-and
markets,
modeling
From results
an IT in diminished
languagues
perspective, and lotview,
implementation sizesprocess
implementation and
specification,
duetools.
to augmenting
executionFrom is the
be-
ics [1,2].
Classical
unknown,
execution
Especially
methodologies
even
are in the
therefore
engineering,
considering
emerging
even lessdomain
known.
successfully
mainly
of single
business
imple-
products
informat-
management
development
product varieties[3].and
and process
(high-volume expert
documentation view,
toviewpoints,
low-volumeprocessproduction)
is primarily specification,
pursued [1,2].
[1]. or ics
mented[1,2].
solitary, Especially
approaches
already forinstandardized
existingengineering,
product successfully
process modeling
families imple-
analyze andthe
management
ing covered
development
From and
andThe
an IT perspective,process expert
different
documentation view, process
is primarily
implementation and specification,
modeling
pursued
execution and ex-
[1,2].
is be- ics
mented[1,2].
For
execution this Especially
purpose,
approaches
are thereforetheineven
for engineering,
so-called
standardized successfully
Process-Driven
less known. process imple-
Approach
modeling and
To cope with
development
ecution thisand augmenting
documentation variety as well
isefforts,
primarily as to be [1,2].
pursued able to product
mented structure
approacheson aa for
physical level (components
standardized level) and
process modeling which
From an result
ing covered [3].inThe
IT perspective,synchronization
implementation
different viewpoints, andcoordination
execution
modeling andis and
be-
ex- (PDA)
execution [5,6]
For this areoffers
therefore
purpose, sustainable
theeven lessand
so-called tool-neutral
known.
Process-Driven opportunity
Approach
identify
From possible
an result optimization
IT perspective, potentials
implementation and in the
execution existing
is and
be- causes
execution
for difficulties
are
a transparent regarding
therefore
and even an
lessand efficient
known. definition and
ing covered
ecution [3].inThe different
synchronization viewpoints,
efforts, modeling
coordination and ex- For
(PDA) this
[5,6] purpose,
offers theconsistent
so-called
a sustainable integration of engineering
Process-Driven
tool-neutral Approach
opportunity
production
ing system,
covered [3]. it
The is important
different to have
viewpoints,
ecution result in synchronization efforts, coordination and
a precise
modeling knowledge
and ex- comparison
For
(PDA) this of different
purpose,
[5,6] offersand
for a transparent the product
so-called
a sustainable
consistentand
families.
Process-Driven
tool-neutral
integration
Addressing
Approach
opportunity
of engineering
this
ecution result in synchronization efforts, coordination and (PDA)
for a [5,6] offersand
transparent a sustainable
consistent and tool-neutral
integration of opportunity
engineering
2212-8271
2212-8271 © 2021
© 2020The TheAuthors. Publishedbyby
Authors, Published Elsevier
Elsevier B.V.B.V.
ThisThis
is an open
is an openaccess
access article underthethe
article under CCCC BY-NC-ND
BY-NC-ND license
license
for a transparent and consistent
(https://creativecommons.org/licenses/by-nc-nd/4.0)
(http://creativecommons.org/licenses/by-nc-nd/4.0/)
integration of engineering
2212-8271 © 2017
2212-8271 TheThe
© 2020 Authors. Published
Authors, PublishedbybyElsevier
Elsevier B.V.
B.V.
Peer-review
Peer review
Peer-review under
under
under responsibility
responsibility of scientific
the responsibility
of the thethescientific
of scientific committee
committee
committee ofof the
the 8th CIRP
CIRPe Global
2020 Global Web
Web Conference – Flexible Mass Customisation
Conference
of the(http://creativecommons.org/licenses/by-nc-nd/4.0/)
28th CIRP Design Conference 2018.
This is an
2212-8271 open
© access
2020 Thearticle
10.1016/j.procir.2021.01.076 under
Authors, the CC
Published BY-NC-ND
by Elsevier license
B.V.
Peer review
2212-8271
This is ©under
2020
an open the
Theresponsibility
access Authors,
article of the
CC scientific
Published
under the committee
by Elsevier
BY-NC-ND B.V. of the CIRPe 2020 Global Web Conference
license (http://creativecommons.org/licenses/by-nc-nd/4.0/)
This
Peer is an open
review access
under article under the
the responsibility CC scientific
of the BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/)
committee of the CIRPe 2020 Global Web Conference
Peer review under the responsibility of the scientific committee of the CIRPe 2020 Global Web Conference
208 Eike Schäffer et al. / Procedia CIRP 96 (2021) 207–212
2 Eike Schäffer et al. / Procedia CIRP 00 (2019) 000–000
processes and tools based on the well-known Business Pro-
cess Model and Notation (BPMN) standard [7]. Based on
BPMN 2.0, processes can be executed directly in a process
engine [8]. Especially in the engineering of machines and
plants, a structured orchestration of different engineering
tools or custom microservices is necessary but not yet state
of the art [9–11]. Therefore, the PDA, originating from busi-
ness informatics, is introduced into the engineering domain
and extended accordingly.
2. Relevant basics and need for action
The Product Emergence Process (PEP) is generally di-
vided into three steps: 1) product development, 2) production
planning, and 3) production [12]. Within the PEP, the syn-
chronization of the individual disciplines (planning, mechan-
ics, electrics, and software) has always been a challenge [13].
Due to mechatronic products with cognitive functions, digi-
tal services, and more sophisticated machines and plants, the
volatility, uncertainty, complexity, and ambiguity – also
known by the acronym VUCA [14] – in engineering contin-
ues to increase [11,15]. Thereby, the coordination effort
grows exponentially with the size of the project [16]. Thus,
efficient and transparent engineering processes as well as an
integrated tool chain, though which individual processes can
even be executed automatically, are all the more important.
2.1. Views and knowledge elements for process automation
In order to automate engineering processes, domain ex-
pert knowledge about the respective processes and data ob-
jects (process input and output) is required, which is usually
developed and documented textually or graphically (Fig. 1,
2nd row). The specified processes can then be transferred by
the IT department into executable program code using appro-
priate software tools and databases. (Fig. 1, 3rd row). [2,3,17]
Knowledge element Process
View also known as workflow
Domain expert (e.g. business Process description (text)
or engineering knowledge) or model (graphical notation)
IT department Executable processes e.g.
(implementation knowledge) built hard-coded into software
Fig. 1. Roles and knowledge elements in traditional process automation
within business informatics [2,3,17]
2.2. Challenges in engineering due to inconsistent process
modeling, lacking tool integration, and missing automation
However, different terminologies, also known as lan-
guages, and tools for process modeling with the aim of doc-
umentation and execution create increased complexity and
effort due to the necessary synchronization (Fig. 2) [3]. Most
modeling terminologies have been developed for process
specification, design, and documentation [1,18] using mod-
eling tools like ARIS [3]. The Event-driven Process Chain
(EPC) was introduced in the 1992s with the aim of semanti-
cally modeling business processes by identifying and graph-
ically documenting business management interrelationships
in a company [1]. With the aim of graphical software speci-
fication, design, and documentation, the Object Management
Group (OMG) published UML 1.1 (1997), UML 1.4 (2001),
and UML 2.0 (2012) as major releases, standardized within
ISO/ IEC 19505-1 [18]. The 14 different UML diagram types
can be classified into seven structure and seven behavior (e.g.
activity or interaction) diagrams. While EPC is used for the
specification of business processes, UML is mainly used for
the initial specification of IT systems [2,3].
Fig. 2. Different tools for process modeling and execution
The Web Services Business Process Execution Language
(WS-BPEL), introduced in 2002, represents an XML-based
implementation-oriented standard to describe the interaction
of executable processes with web services, without providing
a graphical notation [19]. In contrast, for the automation of
engineering processes, Excel tools based on Visual Basic for
Applications (VBA) are often used because of their good us-
ability, availability and simple programming [20,21]. Never-
theless, poor processes in combination with isolated tools
lead to high costs, causing transfer and coordination errors.
According to the rule of ten (Fig. 3), in the case of a faulty
product development and re-design additional costs arise, in
particular with no defect prevention and a late defect discov-
ery [22]. In addition, a study by Reinema et al. [23] shows
the limitations of factory planning concepts and tools:
thereby, 60% of the automation projects failed to achieve
scheduled targets and 72% failed to be within budget. In fac-
tory planning, 52% of the deficits can be traced back to time
and information loss. In practice, factory planning achieves
correct solutions, but there is potential for improvement in
planning process efficiency [23].
Defect prevention Defect detection
Planning Procurement Testing
and development and production and delivery
100.000 €
10.000 €
Cost per defect
Data object for process input
and output also known as item 1.000 €
Data object description (text) 100 €
or model (graphical notation) 10 €
1€
Executable data handling
e.g. through databases
Planning Development Work preparation Production Testing Customer
Product development
Fig. 3. According to the rule of ten, costs increase by a factor of ten with
each phase in case of late or undiscovered defects [22]
2.3. Chances of a consistent process modeling and
automatic execution based on BPMN
Since 2004, the standard terminology BPMN is avaliable
for process modeling and execution, originating from
business informatics and defined by the OMG in ISO/
IEC 19510 [7]. Compared to EPC, the graphical notation
BPMN allows for the execution of modeled processes within
a process engine [2,7] (Fig. 4). The latter feature was
introduced in 2011 with BPMN 2.0 [24]. Despite the given
terminology and machine executability of BPMN, no
scalability of the software architecture is guaranteed by
default. For this purpose, the PDA represents a
superordinated BPMN software architecture, also usefull
within engineering.
 Eike Schäffer et al. / Procedia CIRP 96 (2021) 207–212 209
Eike Schäffer et al. / Procedia CIRP 00 (2019) 000–000 3

BPMN
Autom atic process execution and m onitoring
Process
4.2. Process consistency through executable process models
process m odel Process
models
Executable
processes
Task
list
engine

In order to create a clearer understanding for the PDA, it

Automatic synchronization
is necessary to compare non- and executable process
Fig. 4. Consistent process automation using BPMN with process engine approaches and models (before/ after BPMN) based on
generic process goals, roles, and modeling terminologies.
3. Research method Within process automation, four goals can be distinguished,
which are usually assigned to different roles: documentation,
Considering a case study on the PDA in the field of busi- analysis and optimization, implementation as well as
ness informatics at SAP [6], a sustainable strategy for the execution and monitoring (Fig. 6). As illustrated, the model-
PDA and a continuously executable architecture within en- ing of executable processes can be achieved by using BPMN.
gineering domain based on the PEP is introduced. The stra- In doing so, BPMN serves as a lingua franca (Fig. 6, right
tegic architecture and the continuously executable approach column) for all consumers of the underlying process models.
are elaborated based on literature analysis and synthesis. Different modeling terminologies
Based on our experience and various use cases within the re- Process goal Responsible role before BPMN after BPMN

search project ROBOTOP [25,26] as well as other projects, 1) Documentation Business expert EPC BPMN

we have introduced and enhanced the PDA for the engineer- 2) Analysis and optimization Business analyst Mediation BPMN
ing domain as shown in section 4. In section 5, a minimal
3) Implementation Computer scientist BPEL/ UML BPMN
functional architecture of the PDA within the engineering
domain is evaluated using a prototypical implementation. 4) Execution and monitoring Software Hard-coded Process engine

Fig. 6. Process goals, roles, and modeling terminologies alternatives

4. Sustainable strategy and architecture for the Process-
Driven Approach within the engineering domain The process model execution is performed within a pro-
cess engine, which orchestrates, monitors, compiles, reports,
The PDA has supported the project management and im- and manages all the tasks (Fig. 7) [8].
plementation of digitization projects as well as their process Executable 1 Modeling (BPMN)
sequences in a structured business informatics architecture process model
Service Monitoring and Human workflow
2 3 4
[6]. To introduce and adopt the PDA within the engineering orchestration reporting management
Model import

Process Monitoring of
domain based on the PEP, firstly, the strategic importance of engine the lead time
the PDA in process-based business strategies is outlined.
Automatic
Secondly, a distinction between non- and executable process Task service Automatic service Task
approaches is elaborated with regard to relevant sub-goals allocation call decision call allocation

and roles. Thirdly, a general PDA architecture for the engi- Process
participants
IT System
Process
participants
neering domain is introduced and, fourthly a minimum func- Fig. 7. Process model execution including phases (1-4) according to [8]
tional PDA architecture (MFPA) and its components are de-
rived. 4.3. General PDA architecture for the engineering domain

4.1. Sustainable strategy and significance of the PDA As shown in Fig. 8, the general PDA architecture is di-
vided into three process specific layers [5]; 1) the PDA Layer
Due to the global availability of information, the differen- (PDA-L), 2) the Service Contract Implementation Layer
tiation from the competition through products and services is (SCI-L), and 3) the Back-end Layer (B-L). These are ex-
becoming increasingly less important (Fig. 5). In contrast, ef- tended with a user interaction-specific x) Front-end Shell (F-
ficient internal processes provide a sustainable competitive S), which only communicates with the process engine and
advantage through higher quality services and products at thus with layer 1-3 as a whole. The division of the layers al-
lower costs and higher profit margins. In addition, infor- lows a transparent and explicit separation of the processes
mation on products and services is usually distributed trans- and the software-specific implementation. An explicit ser-
parently through advertising and marketing campaigns. In vice contract (SC) is created to express the input and output
contrast, internal company processes are usually secret, ra- needs for certain steps for general business or specific engi-
ther hidden from the competition, and therefore more diffi- neering processes. In order to fulfill those needs, the SCI-L
cult to imitate. Thus, the efficient, consistent automation of implements the necessary functionality by mediating be-
processes is of great importance, generating strategic ad- tween the PDA-L and the already existing software-specific
vantages to be more competitive in the long term. applications, services, or systems on the B-L.
In [5], the motivation for the separation of layers is ex-
Visible to competitors
plained in great detail. Without SCI-L, the resulting pro-
Focus of a sustainable

and easy to imitate

business strategy

Products Services
cesses lose their clarity, flexibility, and adaptability to
Competitive advantage change in the long run. Thus, the separation considers the
through internal processes Internal
not visible to competitors (business) long-term maintenance costs of software.
and thus difficult to imitate processes

Fig. 5. Relevance of internal processes for sustainable success

210 Eike Schäffer et al. / Procedia CIRP 96 (2021) 207–212
4 Eike Schäffer et al. / Procedia CIRP 00 (2019) 000–000

handled by a technical component called a connector. In or-

der to reduce the number of data transformations, it is rec-
ommended to agree on a neutral generic data format on the
PDA-L and SCI-L, also known a canonical data model [28].
As a consequence, data transformations happen from the
SCI-L to the B-L (and vice versa) only within the integration
software. This improves the maintenance of interfaces and
data mappings of process-driven applications. Excel is also a
frequently used exchange format in engineering; it can be
used on the F-S as well as in the PDA on the B-L. On the B-
L the usage of Excel is less problematic, wherease on the F-
S it should only be used in a restrictive manner, e.g. for early
prototypes and small projects, as it creates and hides depend-
encies, which should be avoided whenever possible.

4.4. Minium functional PDA architecture (MFPA) and its

Fig. 8. Three-layer PDA (1-3) architecture extended with the user interac- components for process automation
tion-specific human machine interfaces, x) the Front-end Shell (F-S)

Although the first implementation of the architecture To make the PDA more accessible for the engineering
might be costlier than putting everything in one process domain, we have composed the minimally functional PDA
model, it pays off in the long term. Initial implementation architecture (MFPA) and its components as depicted in
costs are incurred only once. Maintenance costs, however, Fig. 9. The goal is to show how to create an initial functional
accompany the software throughout the entire lifecycle. The and useful PDA application within existing solutions and
PDA is thus recommended for scenarios in which processes tools, even with Excel tools, which frequently occur in
extend across a wide variety of systems and in which changes industrial software landscapes. The composition of the
are foreseeable [5]. The user group-specific presentation of components in Fig. 9 should demonstrate that a first start to
the F-S can be implemented by using web technologies [27] utilize the PDA is quickly achievable.
or apps, communicating with the process engine through in-
Minimum functional PDA architecture (MFPA) and its components for process automation
terfaces such as Representational State Transfer (REST) I Necessary scope of components for process execution
based Application Programming Interfaces (API). The gen- 1) Process and 2) User 3) Task 4) Process and decision 5) Process
eral business and specific engineering processes are modeled decision rule modeling management management rule execution monitoring
BPMN/ DMN modeler Admin view Task list BPMN process engine and dashboard
using BPMN within the PDA-L.
The SCI-L is responsible for implementing the Ser- II Additional components

vice Contract, fulfilling a required domain driven function- 6) User

interface
7) External user
communication
8) Data
exchange
9) Integrated
logic
10) Complex logic and
expert knowledge
ality by communicating with existing systems. The SCI-L is Web Additional Web interfaces Process engine Engineering
browser application e.g. REST API integrated scripts tool integration
separated in a stateless (mandatory) and a stateful (optional) e.g. e.g. e-mail, app, combined with and logic e.g. e.g. complex Excel tools
Chrome website JSON based on Java or simulation tools
part. The stateful part is needed if a wait state occures. This
is typically the case if a message is sent to a back-end system Fig. 9. MFPA and its components for the engineering domain
and a response is expected. Fig. 8 gives an example for that I) Necessary scope of components: For BPMN
use case: The Simulation microservice is triggered by a mes- modeling, different solutions are avaliable, e.g. from
sage and the process is waiting for the simulation result. Ag- Signavio (signavio.com), Camunda (bpmn.io), or ARIS
gregation is another example for a stateful process on the (ariscloud.com). For process and rule execution, different
SCI-Layer: The stateful process is waiting (wait state) for process engines can be used, e.g. the open source engine
several messages before one package of messages is sent to Activiti (activiti.org) or the freemium engine Camunda
its final destination in one go. However, not every integration (camunda.com). These engines support user and task
scenario requires stateful handling. If it is just about handing management as well as process execution and monitoring.
over a message from PDA-L to one or several backend sys- Decision Model and Notation (DMN) [29] can be utilized for
tems, no state is involved. Hence, the stateful part is obsolete. integrated, structured decision rules within process engines.
The stateful part can be handled either by BPMN processes
(recommended to increase transparency) or specialized inte- II) Additional components: Web browsers can be used
gration software, e.g. Camel (camel.apache.org). Only in as a user interface into the PDA, e.g. for task management,
high-performance scenarios, a specialized integration soft- monitoring as well as administration. For external user com-
ware should be used for better throughput reasons or high munication as well as data acquisition, processing, and dis-
performance integration needs. The stateless part covers the tribution, further applications can be integrated, e.g. using e-
three main aspects of every integration scenario: data trans- mails or user-centered websites and apps. The data exchange
formation, message routing to the right receiving back-end with third-party applications is performed using for example
systems, and technical connectivity such as REST (HTTP- REST API with a pre-defined JSON or XML structure. Be-
Protocoll with JSON) or Simple Object Access Protocol sides DMN for decision tables, further logic and scripts can
(SOAP) communication or connecting via proprietary proto- be directly integrated into process engines using Java code.
cols. The technical connectivity to the systems is typically
 Eike Schäffer et al. / Procedia CIRP 96 (2021) 207–212
Eike Schäffer et al. / Procedia CIRP 00 (2019) 000–000
To integrate more complex logic and expert knowledge, ad-
ditional applications can be connected via REST API as well.
This is especially important in the engineering domain, since
the re-implementation effort of e.g. existing complex Excel
tools or complete simulation environments would not be eco-
nomically reasonable.
5. Prototypical implementation and validation
The following validatation is based on a specific use case
and a corresponding prototypical implementation.
5.1. Presentation of the validation use case
As validation use case, the risk assessment phase within
an automation project has been selected. The process has
been simplified to make the general idea behind the MFPA
more accessible and comprehensible. According to Fig. 10,
a new automation project is launched by a project manager.
In this example, the next process step is a risk assessment.
The PDA-L is not interested in the details of the evaluation
as it is not relevant from the pure functional view of this
layer. Hence, the process step has been separated. The engi-
neer assigned to the project receives an automatic order by e-
mail to perform a risk assessment. The risk assessment is per-
formed using an Excel tool developed internally by the com-
pany for such kind of automation projects. The engineer en-
ters the project ID into the Excel tool, also received in the
first e-mail. Based on the ID, the Excel tool imports the pro-
ject-specific information via a REST API call from the B-L
reusing an already existing project database. Then the engi-
neer performs the risk assessment in the Excel tool. After
completion of the evaluation, the essential results and key
performance indicators are sent back to the PDA-L via REST
API (step ‘Send confirmation’ in the SCI-L process) and the
SCI-L process is completed. Within the PDA-L, the project
manager is automatically notified to check and release the
results or in case of insufficient risk assessment to adapt the
requirements for a re-evaluation of the risk.
Fig. 10. Excerpt from PDA architecture exemplified by the use case
5.2. Validation through prototypical implementation
The validation through prototypical implementation of
the general PDA architecture for the engineering domain
(Fig. 8) and the MFPA (Fig. 9) is accomplished using the
Camunda Community Platform process engine as well as
211
5
BPMN and DMN modeling tools (Camunda modeler). The
web browser Chrome was used as front-end. The main test
project and integrated logic based on Java was built within
the programming environment Eclipse for Java JDK using
Maven archetype (Camunda-bpm) for direct build integra-
tion into Camunda. As a ready-to-run e-mail server, a Gmail
account was used for external communication based on a pre-
defined e-mail template. To demonstrate the integration and
communication of external engineering services with the
process engine through REST API calls, we used an exem-
plary Excel tool as well as the Postman API communication
testing tool (postman.com). The logic in the Excel tool and
the REST API connection (method: msxml2.ServerXMLhttp)
was built based on the programming language VBA.
In doing so, we demonstrated the easy integration and
communication of existing and newly created engineering
tools into the PDA (Fig. 10). In order to demonstrate the
MFPA within the engineering domain in a comprehensible
way, relatively simple and available software tools were
used, as described in the previous paragraph. These should
be replaced depending on the scope of the project through
more powerful alternatives. The replacement of tools has no
effects on the engineering process of the PDA due to the pro-
cess-driven architecture shown in Fig. 8, applying the sepa-
ration of concerns principle. This ensures high flexibility in
case of applying valuable engineering processes on top of
different back-ends and tools. The advantages of the PDA
became obvious during implementation, having transparent
BPMN-based process overviews and running process moni-
toring. In addition, it is possible to adjust and extend the pro-
cess or exchange services to simplify an agile development.
From a first Postman-based communication test service we
extended the prototpye to an Excel tool based service as input
provider, for the BPMN process engine.
5.3. General concept validation through expert discussions
To validate the general concept of PDA within engineer-
ing, we discussed it with three experts from the IT domain
and four experts from the engineering domain, i.e. end users.
The IT experts were asked if they know about PDA ap-
proaches within engineering and how they evaluate the tech-
nical feasibility. None of the interviewed experts knew PDA
attempts related to engineering. The technical feasibility was
rated medium to high. The use of Excel tools was considered
appropriate as an initial solution and for small applications,
but in the long run, the tools should be redesigned for scala-
bility reasons into web services, e.g. microservices.
Engineering experts, i.e. end users, were asked to evaluate
the potential for automation of project management tasks and
tool orchestration. In addition, they also tested the prototype.
The PDA approach was unknown to all interviewees, but af-
ter a detailed explanation, great potential was seen, espe-
cially because of the graphical process description and the
potential for engineering tool orchestration. In particular, the
manual transfer of data from one tool to another causes high
workloads and many potential errors. This problem could be
addressed successively and in a structured way using the
PDA within the engineering domain. However, without the
212 Eike Schäffer et al. / Procedia CIRP 96 (2021) 207–212
6 Eike Schäffer et al. / Procedia CIRP 00 (2019) 000–000
concrete engineering example, most experts had problems
imagining the transferability from the business to the engi-
neering domain. It is therefore necessary to provide further
guidance for the use of the PDA and to elaborate additional
examples in future projects.
6. Conclusion and outlook on future research activities
Encouraged by the challenges in project management and
engineering tool integration, we have introduced the PDA
into the engineering domain. The PDA is based on BPMN,
which is directly executable using process engines. For a
transparent and explicit separation, the PDA is divided into
three layers: 1) the PDA Layer, 2) the Service Contract Im-
plementation Layer and 3) the Back-end Layer. Additionally,
the x) Front-end Shell for user interaction can be realized via
different approaches such as web technologies, apps, e-mail,
or even Excel. These can be optimized via user-centred ap-
proaches as shown using the example of a web-based robot
configurator [27]. Based on the PDA, a MFPA is derived and
prototypically implemented using an exemplary engineering
use case. To be able to transfer the concept to other use cases,
an easily accessible software setup for concrete implementa-
tion is derived. Thus, we demonstrated the integration and
communication of existing and newly created engineering
tools into the PDA based on the MFPA, with the goal to cre-
ate a first basis for a transparent and automatic process inte-
gration. A more flexible orchestration and coupling of soft-
ware tools contributes to the aim of flexible mass customiza-
tion through more consistent and adaptable engineering pro-
cesses.
For future research, process bottlenecks could be visual-
ized and optimized using a heat map provided by the Ca-
munda Enterprise Edition. In addition, consistent data mod-
els for the PDA as well as methods for their consistent devel-
opment should be established, optionally combined with Au-
tomationML for the engineering domain [30]. Supplemen-
tary, the use of the PDA is conceivable in the area of manu-
facturing as well, e.g. for connecting, scheduling or routing
manufacturing operations as a service.
Acknowledgements
The research project ROBOTOP (01MA17009E) is
funded by the German Federal Ministry of Economic Affairs
and Energy (BMWi). ROBOTOP is part of the technology
program “PAiCE Digitale Technologien für die Wirtschaft”
and is guided by the DLR Project Management Agency in
Cologne.
References
[1] Keller G, Nüttgens M, Scheer A.-W. Semantische Prozeßmodellier-
ung auf der Grundlage „Ereignisgesteuerter Prozeßketten (EPK)“.
Veröffentlichungen des IWi 1992.
[2] Gadatsch A. Grundkurs Geschäftsprozess-Management: Analyse,
Modellierung, Optimierung und Controlling von Prozessen. 8th ed.
Wiesbaden: Springer; 2017.
[3] Scheer A-W. ARIS - vom Geschäftsprozess zum Anwendungs-
system. 4th ed. Berlin: Springer; 2002.
[4] Walter A. Leitfaden zur Erstellung eines unternehmensspezifischen
PLM-Konzeptes: Product lifecycle Management; transparente
Prozesse und konsistente Informationen im Produktlebenszyklus.
Frankfurt, M.: VDMA-Verl; 2008.
[5] Stiehl V. Process-driven applications with BPMN. Springer; 2014.
[6] Stiehl V, Danei M, Elliott J, Heiler M. Effectively and Efficiently
Implementing Complex Business Processes: A Case Study. In:
Lübke D, Pautasso C, editors. Empirical Studies on the Development
of Executable Business Processes. Springer; 2019, p. 33–57.
[7] Object Management Group. ISO/IEC 19510: Information technology
- Business Process Model and Notation (BPMN);ICS: 35.020; 2013.
[8] Freund J, Rücker B. Real-life BPMN: Using BPMN 2.0 to analyze,
improve and automate processes in your company; 2012.
[9] Schäffer E, Mayr A, Fuchs J, Sjarov M, Vorndran J, Franke J. Mi-
croservice-based architecture for engineering tools enabling a collab-
orative multi-user configuration of robot-based automation solutions.
Procedia CIRP 2019;86:86–91.
[10] Schäffer E, Pownuk T, Walberer J, Fischer A, Schulz J-P, Klein-
schnitz M et al. System architecture and conception of a standardized
robot configurator based on microservices. Tagungsband des 3. Kon-
gresses Montage Handhabung Industrieroboter 2018:159–66.
[11] Schäffer E, Leibinger H, Stamm A, Brossog M, Franke J. Configu-
ration based process and knowledge management by structuring the
software landscape of global operating industrial enterprises with
Microservices. Procedia Manufacturing 2018;24:86–93.
[12] Steinwasser P. Modulares Informationsmanagement in der in-
tegrierten Produkt- und Prozeßplanung. Meisenbach; 1996.
[13] Lechler T, Fischer E, Metzner M, Mayr A, Franke J. Virtual Com-
missioning – Scientific review and exploratory use cases in advanced
production systems. Procedia CIRP 2019;81:1125–30.
[14] Bennett N, Lemoine J. What a Difference a Word Makes: Under-
standing Threats to Performance in a VUCA World. Business Hori-
zons 2014(57):311–7.
[15] Schäffer E, Bartelt M, Pownuk T, Schulz J-P, Kuhlenkötter B,
Franke J. Configurators as the basis for the transfer of knowledge and
standardized communication in the context of robotics. Procedia
CIRP 2018;72:310–5.
[16] Livesey PV. Insights of project managers into the problems in project
management. CEB 2016;16(1):90–103.
[17] Puppe F. Einführung in Expertensysteme. Springer; 1991.
[18] Object Management Group. ISO/IEC 19505-1: Unified Modeling
Language (UML), Infrastructure; 2012.
[19] OASIS Committee Specification. WS-BPEL Extension for People
(BPEL4People) V 1.1; 2010; Available from: www.docs.oasis-
open.org/bpel4people/bpel4people-1.1-spec-cs-01.pdf.
[20] Schäffer E, Mayr A, Huber T, Höflinger T, Einecke M, Franke J.
Gradual tool-based optimization of engineering processes aiming at
a knowledge-based configuration of robot-based automation solu-
tions. Procedia CIRP 2019;81:736–41.
[21] Fricke A, Schoneberger JC. Industrie 4.0 with MS-Excel? Chemical
Engineering Transactions 2015;43:1303–8.
[22] Clark KB, Fujimoto T. Product development performance: Strategy,
organization, and management in the world auto industry. Boston,
Mass.: Harvard Business School Press; 1991.
[23] Reinema C, Pompe A, Nyhuis P. Agiles Projektmanagement. ZWF
2013;108(3):113–7.
[24] Silver B, Fischli S. BPMN, Methode und Stil. 2nd ed. Aptos, Calif.:
Cody-Cassidy Pr; 2012.
[25] Schäffer E, Schulz J-P, Franke J. Robotiklösungen im Baukasten-
prinzip für den Mittelstand; (2019); In: bigdata-insider; Available
from: www.bigdata-insider.de/robotikloesungen-im-baukastenprin-
zip-fuer-den-mittelstand-a-882401.
[26] Schäffer E, Thi K, Franke J. Bedarf und Konzeptvorstellung des For-
schungsprojekts ROBOTOP für einen webbasierten Konfigurator für
den Massenmarkt 2020.
[27] Schäffer E, Shafiee S, Frühwald T, Franke. A development approach
towards user-centered front-ends for knowledge-based engineering
configurators: a study within planning of robot-based automation so-
lutions. In: Proceedings of the 22st ConfWS'20; 2020, "not yet pub-
lished".
[28] Hohpe G, Woolf B, Brown K. Enterprise integration patterns: De-
signing, building, and deploying messaging solutions. 16th ed. Bos-
ton, Mass.: Addison-Wesley; 2012.
[29] Object Management Group. Decision Model and Notation (DMN).
1st ed; 2016; Available from: www.omg.org/spec/DMN/1.1.
[30] Schäffer E, Penczek L, Mayr A, Bakakeu J, Franke J, Kuhlenkötter
B. Digitalisierung im Engineering: Ein Ansatz für ein Vorgehen-
smodell zur durchgehenden, arbeitsteiligen Modellierung am
Beispiel von AutomationML. I40M 2019;2019(1):61–6.