<!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>Challenges of Applying Adaptive Processes to Enable Variability in Sustainability Data Collection</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Gregor Grambow</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nicolas Mundbrod</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vivian Steller</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Manfred Reichert</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute of Databases and Information Systems Ulm University</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <fpage>74</fpage>
      <lpage>88</lpage>
      <abstract>
        <p>Nowadays, demanding legal regulations as well as sophisticated customer needs force companies in electronics and automotive industries to provide a multitude of di erent sustainability indicators. Since their products usually contain numerous components and subcomponents, companies must deal with complex, intransparent data collection processes along their supply chains in order to nally deliver valuable data. A myriad of di erent automatic and manual tasks, potentially long-running processes, and quickly changing situations result in great variability that is hard to handle. In the SustainHub project, a dedicated information system for supporting data collection processes is developed. Thereby, core challenges as well as state-of-the-art were systematically gathered, consolidated as well as assessed. The condensed results are presented in this paper.</p>
      </abstract>
      <kwd-group>
        <kwd>Business Process Variability</kwd>
        <kwd>Data Collection</kwd>
        <kwd>Sustainability</kwd>
        <kwd>Supply Chain</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>These days, companies of the electronics and automotive industry face steadily
growing demands for sustainability compliance triggered by authorities,
customers and public opinion. As products often consist of numerous individual
components, which, in turn, also comprise sub-components, heterogeneous
sustainability data need to be collected along intertwined and intransparent supply
chains. Thereby, highly complex, cross-organizational data collection processes
are required, featuring a high variability, e.g., through dynamically
integrating companies' employees and information systems (ISs). Further issues include
incompleteness and varying quality of provided data, heterogeneity of data
formats, or changing situations and requirements. Until today, there is no
dedicated IS supporting companies in creating, managing and optimizing such data
collection processes. Within the SustainHub1 project, such a dedicated
information system is being developed. In this context, use cases, delivered by industry
partners from the automotive and the electronics domain, have been intensively
studied in order to consolidate core challenges and essential requirements
regarding the IT-support of data collection processes. In relation, state-of-the-art
has also been deeply studied to assess whether existing approaches and solutions
satisfy the requirements. As a result, this paper systematically presents the
condensed core challenges and state-of-the-art considering complex sustainability
data collection process along today's supply chains. This domain is well suited
for eliciting such challenges because of the complexity of the supply chains on
the one hand and the requirements imposed by emerging laws and regulations
on the other. However, they can be transferred to many other domains as well.
Thus, this contribution identi es 7 core challenges for data exchange and
collection in complex distributed environments and also reviews approaches in place
to solve these challenges. Thereupon, future research in the area of adaptive
business process management can be aligned to extend existing approaches for
supporting more variability and dynamics in today's business processes.</p>
      <p>Therefore, the fundamentals and an illustrating example are introduced in
section 2. Subsequently, seven data collection challenges are unveiled in section
3, exposing concrete ndings, identi ed problems and derived requirements. In
section 4, the current state-of-the-art is presented based on its origin. Finally,
section 5 rounds out this paper giving a conclusion and an outlook.</p>
    </sec>
    <sec id="sec-2">
      <title>2 Sustainable Supply Chains</title>
      <p>This section elaborates on the domain of sustainable supply chains and gives
background information.</p>
      <sec id="sec-2-1">
        <title>2.1 Fundamentals</title>
        <p>
          In today's globalized industry, the development and production of many products
is based on intransparent, complex supply chains with dozens of interconnected
companies distributed around the globe. To ensure and extend competitiveness,
complex communication tasks must be managed properly for e ective and e
cient interorganizational processes. Generally, such cross-organizational
collaboration involves a variety of di erent manual and automated tasks. Involved
companies signi cantly di er in size and industry background, and they use
various di erent ISs, which are not able to intercommunicate easily. Due to this
heterogeneity, neither federated data schemes, unifying tools nor other concepts
can be realistically introduced without considerable e ort [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ].
        </p>
        <p>As sustainability is is an emerging trend, companies even face a new challenge
in their supply chains: sustainable development and production. The incentives
1 SustainHub (Project No.283130) is a collaborative project within the 7th Framework
Programme of the European Commission (Topic ENV.2011.3.1.9-1, Eco-innovation).
are given by two parties: On one hand, legal regulations, increasingly issued by
authorities, force companies to publish more and more sustainability indicators
(like greenhouse gas emissions in production or gender issues) on an obligatory
basis. On the other hand, public opinion and customers compel companies to
provide sustainability information (e.g., organic food) as an important base for
their purchase decisions.</p>
        <p>Examples include ISO 14000 standard for environmental factors in
production, GRI2 covering sustainability factors or regulations like REACH3 and
RoHS4. Overall, sustainability information involve a myriad of di erent
indicators. It relates to social issues (e.g., employment conditions or gender issues),
to environmental issues (e.g., hazardous substances or greenhouse gas (GHG)
emissions), or to managerial issues (e.g., compliance issues).</p>
        <p>There already exist tools at market providing support for the management
and transfer of sustainability data: IMDS5 (International Material Data
System), for instance, is used in the automotive industry and allows for material
declaration by creating and sharing bills of materials (BOM). A similar system
exists for the electronics industry (Environ BOMcheck6). Despite providing
useful support in basic data declaration and exchange tasks, these tools clearly fall
short in providing dedicated support for the sustainability data collection and
exchange along the supply chains.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2 Illustrating Example</title>
        <p>To illustrate the complexity of sustainability data collection processes in a
distributed supply chain, we provide an example. The latter was composed with the
problems and requirements provided by SustainHub's partner companies for the
automotive and electronics industry by formal and informal surveys and
interviews. Please mind that data collection in such a complex environment does not
have the characteristics of a simple query. It is rather a varying, long-running
process incorporating various activities and involving di erent participants.</p>
        <p>The example illustrated in Fig. 1, depicts the following situation: Imposed by
regulations, an automotive manufacturer (requester) has to provide
sustainability data considering its production. This data is captured by two sustainability
indicators, one dealing with the greenhouse gas emissions relating to the
production of a certain product, the other addressing the REACH regulation. The
latter concerns the whole company as companies usually declare compliance to
that regulation on a company basis.</p>
        <p>To provide data regarding these two indicators, the manufacturer has to
gather related information from his suppliers (answerer). Hence, it requests a
2 Global Reporting Initiative: https://www.globalreporting.org
3 Regulation (EC) No 1907/2006: Registration, Evaluation, Authorisation and
Restriction of Chemicals
4 Directive 2002/95/EC: Restriction of (the use of certain) Hazardous Substances
5 http://www.mdsystem.com
6 https://www.bomcheck.net
Process: Request 1
Process Parameters
Requester
Preferences:
Completeness
Quality
Validity
Process: Request 2
Integrate Data
Check for
available Data</p>
        <p>Find / Select
Right Contact</p>
        <p>Submit Data
Request</p>
        <p>Approve Data</p>
        <p>Request</p>
        <p>Sign Data
Available Data
Completeness
Quality
Validity period</p>
        <p>Answerer 1
Approval
Processes
Systems
Platforms
Formats</p>
        <p>Answerer 2
Approval
Processes
Systems
Platforms
Formats</p>
        <p>Indicator: GHG Reference: BoM
Emissions – 2 Positions
Validity date: 1 Standard: ISO
year 14064</p>
        <p>Request 1</p>
        <p>IndCicoamtoprl:iaRnetach CRoemfepreanncyeX:
Due date: 2 Verification:
months in future Legal statement</p>
        <p>Request 2
Answerer 3
Approval
Processes
Systems
Platforms</p>
        <p>Formats
Check for
available Data</p>
        <p>Approve Data</p>
        <p>Request
Approve Data</p>
        <p>Request
Check for
available Data</p>
        <p>Find / Select
Right Contact</p>
        <p>Submit Data
Request</p>
        <p>External
Assessment</p>
        <p>Convert Data</p>
        <p>Col ect
Rrequested</p>
        <p>Data
Start Event</p>
        <p>EndEvent</p>
        <p>ANDGate</p>
        <p>XOR Gate</p>
        <p>Activity</p>
        <p>Subprocess
REACH compliance statement from one of its suppliers. To get the information,
the activities shown in the process Request 1 have to be executed. Furthermore,
the product for which the greenhouse gas emissions shall be indicated has a BoM
with two positions coming from external suppliers. Thus, the request, depicted by
the second work ow, has to be split up into two requests, one for each supplier.</p>
        <p>Hence, the basic scenario involves a set of activities as part of the data
collection processes. Some of these are common for the requests, e.g., on the requester
side, checking available data that might satisfy the request, selecting the
company and contact person, and the submitting the request. On the answerer side,
data must be collected and provided. The other process activities are speci cally
selected for each case. Thereby, the selection of the right activities is strongly
driven by data (process parameters) coming from the requester, the answerer,
the requests and indicators, and possible already available data.</p>
        <p>For example, Request 1 implies a legally binding statement considering
REACH compliance. Therefore, a designated representative (e.g., the CEO) must
sign the data. In many cases, companies have special authorization procedures
for releasing of such data, e.g., that one or more responsible persons have to
approve the request (cf. two parallel approval activities (Approve Data Request )
at Request 2, four-eyes-principle). In some cases, data may be already
available in a company and does not have to be manually gathered (cf. Request 2,
Check of available Data). However, every time the company-internal format of
the answerer does not match the requester's one, a conversion must be applied.
Further, some indicators and requests also directly relate to a given standard
(e.g., ISO 14064 for greenhouse gases) where this can directly trigger an
assessment of the answerer if he cannot exhibit the ful llment of the standard (cf.
Request 2, External Assessment ).</p>
        <p>Finally, another important aspect for often long-running data collection
processes is that process parameters might change over time and, hence, exceptional
situations could occur. Even in this very simple example, many variations and
deviations might occur: for example, if the CEO was not available, activity Sign
Data could be delayed. In turn, this might become a problem if there are de ned
deadlines for the query answer.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3 Data Collection Challenges</title>
      <p>Following rst insights provided in Section 2, this section presents seven concrete
challenges for an information system supporting sustainability data collection
processes along a supply chain (IS-DCP). The results are based on ndings from
case studies conducted with industrial partners in the SustainHub project. Three
gures serve for illustration purposes: Fig. 2 illustrates data collection challenges
(DCC) 1 and 2, Fig. 3 illustrates DCC 3 and 4, and Fig. 4 illustrates DCC 5-7.</p>
      <sec id="sec-3-1">
        <title>Challenge 1: Selection</title>
      </sec>
      <sec id="sec-3-2">
        <title>Challenge 2: Access</title>
        <p>Requester
Answerer
Service Provider
Human
Data Storage
Application</p>
        <sec id="sec-3-2-1">
          <title>3.1 DCC 1: Dynamic Selection of Involved Parties</title>
          <p>Findings Sustainability data collection in a supply chain involves various
parties. A single request may depend on the timely delivery of data from di erent
companies. For manual tasks, this mostly has to be done by a speci c person with
sustainability knowledge or authority. In big companies, it can be even di cult
to nd the right contact person to answer a speci c request. In relation, contact
persons may change from time to time. Furthermore, as the requested data is
often complex, has to be computed, or relates to legal requirements, external
service providers may be involved in the data collection request as well. Finally,
regarding the timely answering of a request, many requests are adjusted and
forwarded to further suppliers (cf. Fig. 2) { thus answering times can multiply.
Problems The contemporary approach to such requests heavily relies on
individuals conducting manual tasks and interacting individually. There are tools
(e.g., email) which can provide support for some of these and partly automate
them. However, much work is still coordinated manually. As a request can be
forwarded down the supply chain, it is quite di cult to predict, who exactly will
be involved in its processing. Resulting from that, answering times of requests
can be hardly estimated in a reliable manner as well.</p>
          <p>Requirements An IS-DCP need to enable companies to centrally create and
manage data collection requests. Thereby, it must be possible to simplify the
dynamic selection process of involved parties and contact persons regarding the
request answerers as well as potentially needed service providers. This is a
basic requirement for enabling e cient request answering, data management, and
monitoring.</p>
        </sec>
        <sec id="sec-3-2-2">
          <title>3.2 DCC 2: Access to Requested Data</title>
          <p>Findings In a supply chain di erent parties follow di erent approaches to data
management. Big companies mostly have implemented a higher level of
automation while SMEs heavily rely on the work of individual persons. Furthermore,
sustainability reporting is a relatively new area and a uni ed reporting method
is not implemented along supply chains. This implies great variability when
it comes to accessing companies' internal data. Some companies have advanced
software solutions for their data management, some manage their data in generic
databases, some store it in speci c les (e.g., Excel), and some have even not
started to manage sustainability data yet.</p>
          <p>Problems The contemporary approach to sustainability reporting is managed
manually to a large extend. This involves manual requests from one party to
another and di erent data collection tasks on the answerer side. This can impose
large delays in data collection processes as sustainability data must be manually
gathered from systems, databases or speci c les before it can be compiled,
prepared and authorized in preparation to the delivery to the requester.
Requirements An IS-DCP must accelerate and facilitate the access to
requested sustainability data. On the one hand, this includes guiding users in
manual data collection as well as automizing data-related activities (e.g., data
approval, data transformation) as far as possible. On the other hand, automatic
data collection should be enabled whenever possible. This involves accessing the
systems containing the data automatically (e.g., via the provision of appropriate
interfaces) and including such activities with manual approval activities when
needed. Finally, data conversion between di erent formats ought to be supported
as a basis for data aggregation.</p>
        </sec>
        <sec id="sec-3-2-3">
          <title>3.3 DCC 3: Meta Data Management</title>
          <p>Findings The management and con guration of sustainability data requests
in a supply chain relies on a myriad of di erent data sets. As aforementioned,
this data comes from various sources. Examples of such parameters include the
preferences of the requester as well as the answerers (including approval processes
and data formats) or the properties of the sustainability indicators (e.g., relations
to standards) (cf. Fig. 3). As a result, potentially matching data might be already
available in some cases but exposing di erent properties as requested.
Problems As requests rely on heterogeneous data, they are di cult to
manage. Requirements are partially presumed by the requester and often implicit.
Hence, answerers might be unaware of all requirements and deliver data not
matching them. Moreover, it is di cult to determine whether data, which has
been collected before, ts the requirements of a new request. Finally, as a supply
chain might involve a large number of requesters and answerers, this problem
multiplies as crucial request data is scattered along the entire supply chain.
Requirements To be able to consistently and e ectively manage data collection
processes, an IS-DCP must centrally implement, manage and provide an
understandable meta data schema addressing relevant request parameters. Thereby,
instanced data based on the uniform meta data schema can be e ectively used
to directly derive and adjust variants of data collection processes.</p>
          <p>Challenge 3: Meta Data</p>
          <p>ReQqQuueeurseytr1y11
Meta Data
Requester Data
Meta Data
Answerer Data</p>
          <p>ReQquueersytVVaarriiaanntt11</p>
          <p>ReQquueersytVVaarriiaanntt22
Challenge 4: Request</p>
          <p>Variants</p>
        </sec>
        <sec id="sec-3-2-4">
          <title>3.4 DCC 4: Request Variants</title>
          <p>Findings As mentioned, sustainability data exchange in a supply chain
involves a considerable number of di erent manual and automated tasks aligned to
the current data request. Hence, execution di ers greatly among di erent data
requests, highly in uenced by parameters and data and distributed on many
sources (cf. DCC 3 and Fig. 3). Moreover, the reuse of provided data is
problematic as well as the reuse of knowledge about conducted data requests: persons
in charge, managing a data collection, might not be aware of which approach
matches the current parameter set.</p>
          <p>Problems This makes the whole data collection procedure tedious and error
prone. Based on the gained insights, to each data request a data collection
process is manually de ned initially, and evolves stepwise afterwards. Relying on
the various in uencing parameters, every request has to be treated
individually { there is no applicable uniform approach to a data request, instead a high
number of variants of data collection processes exist. So far, there is no
system or approach in place that allows structuring or even governing such varying
processes along a supply chain.</p>
          <p>Requirements An IS-DCP needs not only to be capable of explicitly de ning
the process of data collection. Due to the great variability in this domain, it must
also be capable of managing numerous variants of each data request relating
to a given parameter set. This includes the e ective and e cient modeling,
management, storage and executing of data collection request processes.</p>
        </sec>
        <sec id="sec-3-2-5">
          <title>3.5 DCC 5: Incompleteness and Quality</title>
          <p>Findings Sustainability data requests are demanding and their complex data
collection processes evolve based on delivered data and forwarded requests to
other parties (i.e., suppliers of the suppliers) (cf. Fig. 4). Furthermore, they
are often tied to regulative requirements and laws as well as involve mandatory
deadlines. Therefore, situations might occur, in which not all needed data is
present, but the request answer must still be delivered due to a deadline. As
another case, needed data might be available, but on di erent quality levels
and/or in di erent formats.</p>
          <p>Problems Contemporary sustainability data collection in supply chains is
plagued by quality problems relating to the delivered data. Not only that
requests are incompletely answered, the requester also has no awareness of the
completeness and quality of the data stemming from multiple answerers.
Moreover, answerers have no approach to data delivery in place when being unable
to provide the requested data entirely, or their data does not match the
request's quality requirements. Missing a uni ed approach, de nitive assertions or
statements to the quality of the data of one request can often not be made and
requests might even fail due to that fact.</p>
          <p>Requirements An IS-DCP must be able to deal with incomplete data and
quality problems. It must be possible that a request can be answered despite
missing or low quality data. Furthermore, such a system must be able to make
assumptions about the quality of the data that answers a request.</p>
          <p>Challenge 6: Monitoring
Requester Feedback</p>
          <p>Feedback</p>
          <p>Challenge 5: Quality
Request 1</p>
          <p>Feedback Sub-Request 1-1
Feedback</p>
          <p>Feedback</p>
          <p>Request 2</p>
          <p>Feedback</p>
          <p>Sub-Request 1-2</p>
          <p>Deviation 3</p>
        </sec>
        <sec id="sec-3-2-6">
          <title>3.6 DCC 6: Monitoring</title>
          <p>Findings Sustainability data collection along the supply chain involves many
parties and logically may take a long time. The requests exist in many variants
and the quality and completeness of the provided data di er greatly (cf. DCC 5).
The contemporary approach to such requests does not provide any information
about the state of the request to requesters before the latter is answered (cf.
Fig. 4). This includes missing statements about delivered data as well as the
intermediate requests along the supply chain. If request processing is delayed
at the side of one or more answerers, the initial requester cannot access such
information without huge e ort.</p>
          <p>Problems As a requester has no information about the state and potential
data delivery problems of his requests, problems only become apparent when
deadlines are approaching. However, at that time, it is mostly too late to apply
countermeasures to low quality, incomplete data, or answerers that simple deliver
no data at all.</p>
          <p>Requirements An IS-DCP must be capable of monitoring complex requests
spanning multiple answerers as well as various di erent manual and automatic
activities. A requester must have the option to get actively or passively informed
about the state of the activities along the data collection process as well as the
state of the delivered data.</p>
        </sec>
        <sec id="sec-3-2-7">
          <title>3.7 DCC 7: Run Time Variability</title>
          <p>Findings Data collection requests can take a long time to answer as they
dynamically involve a great number of di erent parties. Further, they expose manual
and automatic activities, di erent kinds of data and data formats, and various
unforeseen in uences on the data collection process. This implies that
parameters, applied at the beginning of the request in uencing data collection, may
change during the run time of a data collection process. Exceptional situation
handling occurs as a result of expiring deadlines or answerers not delivering data.
Problems The variability relating to sustainability data collection processes
constitute a great challenge for companies. Running requests might become
invalidated due to the aforementioned issues. However, there is no common sense
or standard approach to this. Instead, requesters and answerers must manually
nd solutions to still get requests answered in time. This includes much
additional e ort and delays. Another issue are external assessments: they could not
only be delayed but also completely fail, leaving the answerer without a required
certi cation. The nal problem touched by this example concerns mostly
longrunning data collection processes: data, that was available at the beginning of
the query, could get invalid during the long-term process (e.g., if it has a de ned
validity period).</p>
          <p>Requirements An IS-DCP must cope with run-time variability occurring in
today's sophisticated sustainability data collection processes. As soon as issues
are detected, data collection processes must be timely adapted to the changing
situation in order to keep the impact of these issues as considerable as possible.
This requests a system which is able to dynamically adapt already running data
collection processes without invalidating or breaking the existing process ow.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4 State of the art</title>
      <p>This section gives insights on the state of the art in scienti c approaches relating
to the issues shown in this paper. It starts with a broader overview and proceeds
with more closely related work including three subsections.</p>
      <p>Section 3 underlines that exchanging data between di erent companies along
a supply chain in an e cient and e ective way has always been a challenge.
Nonetheless, this exchange is not only necessary|it is now a crucial success
factor and a competitive advantage, these days. However, many in uencing factors
hamper the realization of a data exchange being automated and homogeneous.
In particular for those companies aiming to address holistic sustainability
management, the inability to implement automated and consistent data exchange is
a big obstacle. Please remind that these companies need to take into account
existing and even emerging laws as well as regulations requesting to gather and
distribute information about their produced goods. Furthermore, that requested
information need be gathered from their their suppliers as well. Hence, complex
data collection processes, involving a multitude of di erent companies and
systems, have to be designed, conducted, and monitored to ensure compliance. So
far, we could not locate any related work that completely addresses the
aforementioned challenges (cf. Section 3).</p>
      <p>
        For complex data collection processes, IS support in the supply chain is
desirable supporting communication and enabling automated data collection. The
importance and impact of an IS for supply chain communication has already
been highlighted in literature various times. In [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], for instance, a literature
review is conducted showing a tremendous in uence of ISs on achieving e ective
SCM. The authors also propose a theoretical framework for implementing ISs
in the supply chain. Therefore, they identify the following core areas:
strategic planning, virtual enterprise, e-commerce, infrastructure, knowledge
management, and implementation. However, their ndings also include that great
exibility in the IS and the companies is necessary and that IS-enabled SCM often
requires major changes in the way companies deal with SCM. As another
example, [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] presents an empirical study to evaluate alternative technical approaches
to support collaboration in SCM. These alternatives are a centralized web
platform, classical electronic data interchange (EDI) approaches, and a decentralized,
web service based solution. The author assesses the suitability of the di erent
approaches with regard to the complexity of the processes and the exchanged
information. Concluding, the relating work in this area shows or evaluates novel
approaches to SCM management, which are, however, mostly theoretic, very
general, and not applicable to the speci c topic of sustainability data collection
processes.
      </p>
      <p>
        As automation can be a way to deal with various issues for sustainability
data collection, various approaches addressing that topic can be found in
literature. However, none of them applies to the domain and speci c requirements of
sustainable supply chain communication. For example, [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] presents an approach
to semi-automatic data collection, analysis, and model generation for
performance analysis of computer networks. The approach incorporates a graphical
user interface and a data pipeline for transforming network data into organized
hash tables and spread sheets for usage in simulation tools. As it primarily deals
with a speci c type of data transformation, it is not suitable in our context.
Such approaches deal with automated data collection; yet they are not related
to sustainability or SCM and the problems arising in this setting.
      </p>
      <p>
        There also exist approaches addressing sustainability reporting (e.g., [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ],
[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ],[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], and [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]). However, they do not suggest technical solutions for automatic
data collection. They rather address the topic theoretically by analyzing the
importance of corporate sustainability reporting, evaluating sustainability
indicators or the process of sustainability reporting as a whole, or aiming at building
a sustainability model by analyzing case studies.
      </p>
      <p>Besides approaches targeting generic sustainability, SCM and data collection
issues, there are three closer areas that are mainly related to our problem
statement and issues. As discussed, sustainability data collection processes involve
numerous tasks to be orchestrated. Data requests may exist in many di erent
variants based on a myriad of di erent data sources and may be subjected to
dynamic changes during run-time (cf. DCC 7). This sub-section reviews approaches
for process con guration (Section 4.1), data- and user-driven processes (Section
4.2), and dynamic processes (Section 4.3).</p>
      <sec id="sec-4-1">
        <title>4.1 Process Con guration</title>
        <p>
          Behaviour-based con guration approaches enable the process modeler to specify
pre-de ned adaptations to the process behaviour. One option for realizing this
is hiding and blocking as described by [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. By blocking, this approach allows
disabling the occurrence of a single activity/event. The other option enabled by
this approach is hiding enabling a single activity to be hidden. That activity is
then executed silently but succeeding activities in that path are still accessible.
        </p>
        <p>
          Another way to enable process model con guration for di erent situations is
to incorporate con gurable elements into the process models as described in [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]
or [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. An example of this approach is a con gurable activity, which may be
integrated, omitted, or optionally integrated surrounded by XOR gateways.
Another approach enabling process model con guration is ADOM [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] that builds
on software engineering principles and allows for the speci cation of guidelines
and constraints with the process model. A di erent approach to process con
guration is taken by structural con guration, which is based on the observation
that process variants are often created by users by simply copying a process
model and then applying situational adaptations to it. A sophisticated approach
dealing with such cases is Provop [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ], which enables process variants by storing
a base process models and pre-con gured adaptations to it. The later can also
be related to context variables to enable the application of changes matching to
di erent situations. Finally, [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ] provides a comprehensive overview of existing
approaches targeting process variability.
        </p>
        <p>Process con guration approaches are a promising option to the problem
presented in this paper. Nevertheless, that approaches do not completely match
the requirements for exible data collection work ows in such a dynamic and
heterogeneous environment, as many di erent data sources must be considered
and request can be subjected to change even while they are running.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2 Data- and User-driven Processes</title>
        <p>
          In contrast to classical process management approaches focusing on the
sequencing of activities, the case handling paradigm [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] focuses on the objective of the
process that is called case. In relation, the product-based work ow approach
focuses on the interconnection between product speci cation and derived
workows [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ]. The Business Artifacts approach [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ] is a data driven methodology
that focuses on business artifacts rather than activities. These artifacts hold the
information about the current situation and thus determine how the process shall
be executed. In particular, all executed activities are tied to the life-cycle of the
business artifacts. Another data-driven process approach is provided by
CorePro [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ]. It enables process coordination based on objects and their relations.
In particular, it provides a means for generating process structures out of the
object life cycles of connected objects and their interactions. The creation of
concepts, methods, and tools for object- and process-aware applications is the goal
of the PHILharmonic Flows framework [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]. Thus, exible integration of
business data and business processes shall be achieved and the limitations known
from activity-centered Work ow Management Systems shall be overcome.
        </p>
        <p>The approaches shown in this sub-section facilitate processes that are more
user- or data-centric and aware. The creation of processes from certain objects
could be interesting for SustainHub, however in the dynamic supply chain
environment processes rather rely on context parameters than objects and are also
continuously in uenced by their changes while executing.</p>
      </sec>
      <sec id="sec-4-3">
        <title>4.3 Dynamic Processes</title>
        <p>In current literature, there are two main options for making the automatically
supported execution of work ows dynamic: Normal, imperative work ows that
are dynamic or adaptive or constraint based declarative work ows that are less
rigid by design. This sub-section brie y reviews both kinds of approaches starting
with adaptive imperative work ows.</p>
        <p>
          Adaptive PAIS have been developed that incorporate the ability to change a
running process instance to conform to a changing situation. Examples of such
systems are ADEPT2 [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ], Breeze [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ], WASA [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ], and SPADE [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ]. All of
these only permit manual adaptation carried out by a user. An important issue
in this case is that the exceptional situations leading to the adaptation can occur
more than once. In that case, knowledge about the previous changes should be
exploited to extend e ectiveness and e ciency of the current change [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ][
          <xref ref-type="bibr" rid="ref25">25</xref>
          ].
        </p>
        <p>
          In case a human shall apply the adaptations, approaches like ProCycle [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ]
or CAKE2 [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ] aim at supporting him with that knowledge. In the situation
described in this paper, these approaches are not suitable since the creation
and adaptation of process instances has to incorporate various potentially new
information and has to be applied before humans are involved or incorporate
knowledge the issuer of a work ow does not possess. Automated creation and
adaptation of the data collection work ows will be favourable. In this area,
only a small number of contemporary approaches exist, like AgentWork [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ]
and SmartPM [
          <xref ref-type="bibr" rid="ref29">29</xref>
          ] Unfortunately, these are limited to rule based detection of
exceptions and application of countermeasures.
        </p>
        <p>
          As mentioned before, another way to enables exibility into work ows is
by specifying them in a declaring way. By such speci cation, a strict activity
sequencing is not rigidly prescribed. Instead of this, a number of di erent
constraints can be used to specify certain facts that the work ow execution must
conform to. This could be the mutual exclusion of two activities or a sequencing
relation between two distinct activities. Based on this, all activities speci ed can
be executed at any time as long as no constraint is violated. Examples for such
approaches are DECLARE [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ] and ALASKA [
          <xref ref-type="bibr" rid="ref31">31</xref>
          ]. However, such approaches
have speci c shortcomings relating to understandability. Furthermore and even
more important in our context, if no clear activity sequencing is speci ed, all
activities relating to monitoring are di cult to satisfy and monitoring is a crucial
requirement for the industry in this case.
        </p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5 Conclusion</title>
      <p>This paper motivated the topic of sustainability data exchange along supply
chains to subsequently present core challenges as well as state of the art in this
area. We have clearly identi ed seven core challenges for today's data collection
processes based on intensive interaction with our SustainHub partners most of
them relating to variability issues. Especially, design time as well as run time
exibility are clear requirements for any approach supporting companies
aiming at sustainable development and production. The presented challenges can
serve as starting point for applications developed to support today's
complicated supply chain communication. The challenges are expressed in terms of
sustainability data collection, however they describe generic problems that may
occur in many domains. Thus the results can be easily transferred and be used
for other domains. There exists a substantial amount of related work in di
erent areas touching these topics. Yet, none of these approaches or tools succeeds
in providing holistic support for the process of sustainability data exchange in
a supply chain. The support of data collection requests and processes along
today's complex supply chains is a challenge in the literal sense. Nonetheless,
SustainHub is actively working on a process-based solution to deal with, and
successfully manage the high variability occurring during design and run time.
Future work will describe the exact approach, combination of technologies, and
the architecture of the system to cope with the aforementioned challenges.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgement</title>
      <p>The project SustainHub (Project No.283130) is sponsored by the EU in the 7th
Framework Programme of the European Commission (Topic ENV.2011.3.1.9-1,
Eco-innovation).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Fawcett</surname>
            ,
            <given-names>S.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Osterhaus</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Magnan</surname>
            ,
            <given-names>G.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brau</surname>
            ,
            <given-names>J.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McCarter</surname>
            ,
            <given-names>M.W.</given-names>
          </string-name>
          :
          <article-title>Information sharing and supply chain performance: the role of connectivity and willingness</article-title>
          .
          <source>Supply Chain Management: An International Journal</source>
          <volume>12</volume>
          (
          <issue>5</issue>
          ) (
          <year>2007</year>
          )
          <volume>358</volume>
          {
          <fpage>368</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Gunasekaran</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ngai</surname>
          </string-name>
          , E.W.T.:
          <article-title>Information systems in supply chain integration and management</article-title>
          .
          <source>European Journal of Operational Research</source>
          <volume>159</volume>
          (
          <issue>2</issue>
          ) (
          <year>2004</year>
          )
          <volume>269</volume>
          {
          <fpage>295</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Pramatari</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Collaborative supply chain practices and evolving technological approaches</article-title>
          .
          <source>Supply Chain Management: An International Journal</source>
          <volume>12</volume>
          (
          <issue>3</issue>
          ) (
          <year>2007</year>
          )
          <volume>210</volume>
          {
          <fpage>220</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Barnett</surname>
          </string-name>
          , P.T.,
          <string-name>
            <surname>Braddock</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clarke</surname>
            ,
            <given-names>A.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>DuPre</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gimarc</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lehr</surname>
            ,
            <given-names>T.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Palmer</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ramachandran</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Renyolds</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Spellman</surname>
            ,
            <given-names>A.C.</given-names>
          </string-name>
          :
          <article-title>Method of semiautomatic data collection, data analysis, and model generation for the performance analysis of enterprise applications (</article-title>
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Singh</surname>
            ,
            <given-names>R.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Murty</surname>
            ,
            <given-names>H.R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gupta</surname>
            ,
            <given-names>S.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dikshit</surname>
            ,
            <given-names>A.K.</given-names>
          </string-name>
          :
          <article-title>An overview of sustainability assessment methodologies</article-title>
          .
          <source>Ecological indicators 9(2)</source>
          (
          <year>2009</year>
          )
          <volume>189</volume>
          {
          <fpage>212</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Ballou</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heitger</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Landes</surname>
            ,
            <given-names>C.E.</given-names>
          </string-name>
          :
          <article-title>The Future of Corporate Sustainability Reporting: A Rapidly Growing Assurance Opportunity</article-title>
          .
          <source>Journal of Accountancy</source>
          <volume>202</volume>
          (
          <issue>6</issue>
          ) (
          <year>2006</year>
          )
          <volume>65</volume>
          {
          <fpage>74</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Adams</surname>
            ,
            <given-names>C.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McNicholas</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Making a di erence: Sustainability reporting, accountability and organisational change</article-title>
          .
          <source>Accounting, Auditing &amp; Accountability Journal</source>
          <volume>20</volume>
          (
          <issue>3</issue>
          ) (
          <year>2007</year>
          )
          <volume>382</volume>
          {
          <fpage>402</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Pagell</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wu</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          :
          <article-title>Building a more complete theory of sustainable supply chain management using case studies of 10 exemplars</article-title>
          .
          <source>Journal of Supply Chain Management</source>
          <volume>45</volume>
          (
          <issue>2</issue>
          ) (
          <year>2009</year>
          )
          <volume>37</volume>
          {
          <fpage>56</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Gottschalk</surname>
          </string-name>
          , F.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jansen-Vullers</surname>
            ,
            <given-names>M.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>La</surname>
            <given-names>Rosa</given-names>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          :
          <article-title>Congurable work ow models</article-title>
          .
          <source>Int. J. Cooperative Inf. Syst</source>
          .
          <volume>17</volume>
          (
          <issue>2</issue>
          ) (
          <year>2008</year>
          )
          <volume>177</volume>
          {
          <fpage>221</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Rosemann</surname>
          </string-name>
          , M.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.:</given-names>
          </string-name>
          <article-title>A con gurable reference modelling language</article-title>
          .
          <source>Information Systems</source>
          <volume>32</volume>
          (
          <issue>1</issue>
          ) (
          <year>2005</year>
          )
          <volume>1</volume>
          {
          <fpage>23</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <given-names>La</given-names>
            <surname>Rosa</surname>
          </string-name>
          , M.,
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dumas</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>ter Hofstede</surname>
            ,
            <given-names>A.H.M.</given-names>
          </string-name>
          :
          <article-title>Questionnaire-based variability modeling for system con guration</article-title>
          .
          <source>Software and System Modeling</source>
          <volume>8</volume>
          (
          <issue>2</issue>
          ) (
          <year>2009</year>
          )
          <volume>251</volume>
          {
          <fpage>274</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Reinhartz-Berger</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          , So er, P.,
          <string-name>
            <surname>Sturm</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Extending the adaptability of reference models</article-title>
          .
          <source>IEEE Transactions on Systems, Man, and Cybernetics</source>
          , Part A
          <volume>40</volume>
          (
          <issue>5</issue>
          ) (
          <year>2010</year>
          )
          <volume>1045</volume>
          {
          <fpage>1056</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Hallerbach</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bauer</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Con guration and management of process variants</article-title>
          .
          <source>In: Int'l Handbook on Business Process Management I</source>
          . Springer (
          <year>2010</year>
          )
          <volume>237</volume>
          {
          <fpage>255</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Torres</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zugal</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ayora</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pelechano</surname>
          </string-name>
          , V.:
          <article-title>A qualitative comparison of approaches supporting business process variability</article-title>
          .
          <source>In: 3rd Int'l Workshop on Reuse in Business Process Management (rBPM</source>
          <year>2012</year>
          ).
          <source>BPM'12 Workshops. LNBIP</source>
          , Springer (
          <year>September 2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>van der Aalst</surname>
            ,
            <given-names>W.M.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , Grunbauer, D.:
          <article-title>Case handling: A new paradigm for business process support</article-title>
          .
          <source>Data &amp; Knowledge Engineering</source>
          <volume>53</volume>
          (
          <issue>2</issue>
          ) (
          <year>2004</year>
          )
          <volume>129</volume>
          {
          <fpage>162</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Reijers</surname>
            .,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liman</surname>
            , S., van der Aalst,
            <given-names>W.M.P.</given-names>
          </string-name>
          :
          <article-title>Product-based work ow design</article-title>
          .
          <source>Management Information Systems</source>
          <volume>20</volume>
          (
          <issue>1</issue>
          ) (
          <year>2003</year>
          )
          <volume>229</volume>
          {
          <fpage>262</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Bhattacharya</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hull</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Su</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>A data-centric design methodology for business processes</article-title>
          .
          <source>In: Handbook of Research on Business Process Management. IGI</source>
          (
          <year>2009</year>
          )
          <volume>503</volume>
          {
          <fpage>531</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18. Muller,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Reichert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Herbst</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.:</surname>
          </string-name>
          <article-title>A new paradigm for the enactment and dynamic adaptation of data-driven process structures</article-title>
          .
          <source>In: CAiSE'08</source>
          . Volume 5074 of LNCS., Springer (
          <year>2008</year>
          )
          <volume>48</volume>
          {
          <fpage>63</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19. Kunzle, V.,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>PHILharmonicFlows: towards a framework for objectaware process management</article-title>
          .
          <source>Journal of Software Maintenance and Evolution: Research and Practice</source>
          <volume>23</volume>
          (
          <issue>4</issue>
          ) (
          <year>June 2011</year>
          )
          <volume>205</volume>
          {
          <fpage>244</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Dadam</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The ADEPT project: A decade of research and development for robust and exible process support - challenges and achievements</article-title>
          .
          <source>Computer Science - Research and Development</source>
          <volume>23</volume>
          (
          <issue>2</issue>
          ) (
          <year>2009</year>
          )
          <volume>81</volume>
          {
          <fpage>97</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Sadiq</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marjanovic</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Orlowska</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Managing change and time in dynamic work ow processes</article-title>
          .
          <source>Int. J Cooperative Information Systems</source>
          <volume>9</volume>
          (
          <issue>1</issue>
          &amp;2) (
          <year>2000</year>
          )
          <volume>93</volume>
          {
          <fpage>116</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Formal foundation and conceptual design of dynamic adaptations in a work ow management system</article-title>
          .
          <source>In: Proc. Hawaii Int'l Conf on System Sciences (HICSS-34)</source>
          . (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Bandinelli</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fugetta</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghezzi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Software process model evolution in the SPADE environment</article-title>
          .
          <source>IEEE Transactions on Software Engineering</source>
          <volume>19</volume>
          (
          <issue>12</issue>
          ) (
          <year>December 1993</year>
          )
          <volume>1128</volume>
          {
          <fpage>1144</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Lenz</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>IT support for healthcare processes - premises, challenges, perspectives</article-title>
          .
          <source>Data and Knowledge Engineering</source>
          <volume>61</volume>
          (
          <issue>1</issue>
          ) (
          <year>2007</year>
          )
          <volume>39</volume>
          {
          <fpage>58</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Minor</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tartakovski</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bergmann</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          :
          <article-title>Representation and structure-based similarity assessment for agile work ows</article-title>
          .
          <source>In: Proc. ICCBR'07</source>
          . (
          <year>2007</year>
          )
          <volume>224</volume>
          {
          <fpage>238</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reichert</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wild</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          , Rinderle-Ma, S.:
          <article-title>Providing integrated life cycle support in process-aware information systems</article-title>
          .
          <source>Int'l Journal of Cooperative Information Systems</source>
          <volume>18</volume>
          (
          <issue>1</issue>
          ) (
          <year>2009</year>
          )
          <volume>115</volume>
          {
          <fpage>165</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Minor</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tartakovski</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schmalen</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bergmann</surname>
          </string-name>
          , R.:
          <article-title>Agile work ow technology and case-based change reuse for long-term processes</article-title>
          .
          <source>Int'l J. of Intelligent Information Technologies</source>
          <volume>4</volume>
          (
          <issue>1</issue>
          ) (
          <year>2008</year>
          )
          <volume>80</volume>
          {
          <fpage>98</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28. Muller, R.,
          <string-name>
            <surname>Greiner</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rahm</surname>
          </string-name>
          , E.:
          <article-title>AgentWork: A work ow system supporting rule{based work ow adaptation</article-title>
          .
          <source>Data &amp; Knowledge Engineering</source>
          <volume>51</volume>
          (
          <issue>2</issue>
          ) (
          <year>2004</year>
          )
          <volume>223</volume>
          {
          <fpage>256</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Lerner</surname>
            ,
            <given-names>B.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Christov</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Osterweil</surname>
            ,
            <given-names>L.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bendraou</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kannengiesser</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wise</surname>
            ,
            <given-names>A.E.</given-names>
          </string-name>
          :
          <article-title>Exception handling patterns for process modeling</article-title>
          .
          <source>IEEE Trans. Software Eng</source>
          .
          <volume>36</volume>
          (
          <issue>2</issue>
          ) (
          <year>2010</year>
          )
          <volume>162</volume>
          {
          <fpage>183</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>Pesic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schonenberg</surname>
          </string-name>
          , H., van der Aalst, W.M.: Declare:
          <article-title>Full support for looselystructured processes</article-title>
          .
          <source>In: Enterprise Distributed Object Computing Conference</source>
          ,
          <year>2007</year>
          .
          <source>EDOC</source>
          <year>2007</year>
          . 11th IEEE International, IEEE (
          <year>2007</year>
          )
          <volume>287</volume>
          {
          <fpage>287</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pinggera</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zugal</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wild</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Alaska simulator toolset for conducting controlled experiments on process exibility</article-title>
          .
          <source>In: Information Systems Evolution</source>
          . Springer (
          <year>2011</year>
          )
          <volume>205</volume>
          {
          <fpage>221</fpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>