<!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>On the Development of a Modelling Framework for Value Co-creation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Henderik A. Proper</string-name>
          <email>e.proper@acm.org</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marija Bjekovic´</string-name>
          <email>marija.bjekovic@list.lu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Christophe Feltus</string-name>
          <email>christophe.feltus@list.lu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Iva´n Razo-Zapata</string-name>
          <email>ivan.razo-zapata@list.lu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Luxembourg Institute of Science and Technology (LIST)</institution>
          ,
          <addr-line>Belval</addr-line>
          ,
          <country country="LU">Luxembourg</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Radboud University Nijmegen</institution>
          ,
          <addr-line>Nijmegen</addr-line>
          ,
          <country country="NL">the Netherlands</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of Luxembourg</institution>
          ,
          <country country="LU">Luxembourg</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Western countries have transitioned from a goods-oriented economy to a servicesoriented economy. Marketing literature suggests that the notion of economic exchange, core to the economy, has shifted from following a goods-dominant logic to a servicedominant logic. These sources also observe how this transition results in a growing awareness that value, and value co-creation in particular, should be taken as a (if not the) leading factor in the design of the service systems that drive the service economy. This results in the challenge of ensuring that the modelling frameworks used in designing different aspects of service systems, indeed also cater to the design of value co-creation aspects. In line with this, this paper reports on ongoing work towards the development of a modelling framework, called ValCoLa,4 that also caters to the design of value co-creation constellations. We start by further clarifying the need to include value co-creation aspects in the regular modelling frameworks used when designing / architecting service systems. We then continue by exploring the concept of value co-creation from the perspective of marketing literature. This also results in the observation that a stable definition of the underlying concepts has not yet been reached, while an understanding of the actual design challenges confronting enterprises in practice is also lacking. We finalise this paper by critically reflecting, from a design science perspective, on the best strategy to develop the envisaged language framework. In doing so, we will also include experiences in the development of the ArchiMate enterprise architecture modelling language. This results in some key strategic choices for the development of ValCoLa.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        Western countries have seen a transition from a goods-oriented economy to a
servicesoriented economy. Marketing literature [
        <xref ref-type="bibr" rid="ref12 ref24">42, 12, 24, 43</xref>
        ] suggests that the notion of
economic exchange, core to the economy, has shifted from following a goods-dominant
logic to a service-dominant logic. An important assertion underlying service-dominant
logic is the notion of resource integration [41, 42, 44], based on the view that value
results from a process of co-creation between actors, including the beneficiary.
      </p>
      <p>
        As a consequence, value, and value co-creation in particular, should be taken as a
(if not the) leading factor in the design of the service systems that drive the service
economy [
        <xref ref-type="bibr" rid="ref23">31, 32, 23, 33</xref>
        ]. Marketing literature [
        <xref ref-type="bibr" rid="ref12 ref24">42, 12, 24, 43</xref>
        ] also suggests that the
shift towards service as the fundamental basis of economic exchange has profound
implications on the way enterprises5 are operated and value is created.
      </p>
      <p>
        In designing and developing service systems, and enterprise in general, different
modelling frameworks are used that typically cover different aspects, while
maintaining coherence between the different aspects. Examples include ARIS [39] and
ArchiMate [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]. The shift from goods-dominant logic to service-dominant logic, and the
growing awareness of the role of value co-creation, results in a natural expectation for
such modelling frameworks to also caters for value co-creation considerations.
      </p>
      <p>In line with this, this paper is concerned with ongoing work towards the
development of a modelling framework, called ValCoLa,4 that supports value co-creation. As
such, the main contribution of this paper lies in summarising the motivation for
ValCoLa, and a reflection on the strategy that will / should be used in its development.</p>
      <p>The remainder of this paper is structured as follows. In Section 2, we start by further
clarifying the need to include a value co-creation perspective in the modelling
frameworks used when designing / architecting service systems. We then continue in Section
3 by exploring the concept of value co-creation from the perspective of marketing
literature. This will also lead to the observation that a stable definition of the underlying
concepts has not yet been reached, while an understanding of the actual design challenges
confronting enterprises in practice is also lacking. In Section 4 we will then critically
reflect on the best strategy to develop ValCoLa. In doing so, we will take a design science
perspective, while also including our experiences with the earlier development of such
a language framework (ArchiMate) in the context of enterprise architecture, as well as
reported experiences in the development of domain specific modelling languages. This
reflection results in some key strategic choices for the development of ValCoLa.
2</p>
    </sec>
    <sec id="sec-2">
      <title>The need to model value co-creation</title>
      <p>
        As mentioned in the introduction, marketing sciences [
        <xref ref-type="bibr" rid="ref12 ref24">42, 12, 24, 43</xref>
        ] suggests that the
shift towards service as the fundamental basis of economic exchange has profound
implications on the way enterprises are operated and value is created, and that as a
consequence, value co-creation should be taken as a (if not the) leading factor in architecting
and designing service systems [
        <xref ref-type="bibr" rid="ref23">31, 32, 23, 33</xref>
        ].
      </p>
      <p>When enterprises start to develop their service systems, e.g. with the aim to
support value co-creation, they will also need to do infrastructural investments, to
prepare themselves for the actual co-creation of value between the involved partners. Such
infrastructural investments could e.g. include cultural / knowledge assets, such as
institutions in terms of rules, norms, meanings, symbols, practices, and similar aides to
5Be they commercial enterprises (i.e. businesses / companies, governmental bodies,
not-forprofit organisations, temporary organisations such as large-scale construction projects, etc.)
collaboration [43], social / contractual assets in terms of defined institutional
arrangements [43], contracts with partners in the value web, etc, as well as technological assets
such as shared technology platforms, etc.</p>
      <p>
        To ensure that such investments remain controllable, manage coherence [45],
ascertain if key quality concerns (e.g. sustainability, security, privacy, flexibility) are met,
etc., one generally suggests to use an design / architecture oriented approach [28, 36],
enabling informed design [
        <xref ref-type="bibr" rid="ref25">25, 34</xref>
        ].
      </p>
      <p>For value co-creation, it is important to not only architect one enterprise / service
system in isolation, but rather consider the entire value co-creation context. Concerns,
such as sustainability, equity between partners, etc, can only be considered sensibly at
the level of such co-creation networks. Behind all of this, is the core driver of
servicedominant logic [43] to integrate resources between partners.</p>
      <p>
        As already mentioned in the introduction, when architecting service systems, and
enterprise in general, different modelling frameworks are used that typically cover
different aspects, while maintaining coherence between the different aspects. Examples
include ARIS [39] and ArchiMate [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]. The shift from goods-dominant logic to
servicedominant logic, and the growing awareness of the value co-creation aspects, results in
a natural need to also be able to include value co-creation aspects.
      </p>
      <p>This triggered the start of the ValCoLa project, aiming to develop such a modelling
framework. It is important to note that in the development of the ValCoLa language
framework, no a-priori stance is taken with regard to the question if a new language
should be developed, or if (fragments of) existing languages can be “re-used”.
3</p>
    </sec>
    <sec id="sec-3">
      <title>Value co-creation</title>
      <p>
        A major challenge in the context of value co-creation is the fact that the notion of
value itself is inherently a subjective and situational matter. For a given person, the
value of e.g. a fifty Euro bill and a bottle of water will change depending on wether the
person is sitting on the terrace of a restaurant, or is wandering thirstily through a desert.
When designing, and running, value co-creation constellations it seems beneficial to at
least have some “approximation” of the potential / attributed value by a consumer to
a service / product. However, one should remain aware of the fact that this is only an
approximation of the actual value (in use) as ascribed [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] by a user / consumer (in a
specific situation). Furthermore, it is known that customers not only focus on economic
or functional benefits but also on emotional, social, ethical dimensions [
        <xref ref-type="bibr" rid="ref2">26, 2, 27</xref>
        ].
      </p>
      <p>
        Management literature [
        <xref ref-type="bibr" rid="ref12 ref24">42, 12, 24, 43</xref>
        ] motivates the shift from goods-dominant
logic to service-dominant logic by observing that it is ultimately the customer who
attributes value to a good or a service. Goods and services, “at rest”, only have a potential
value to a customer. The actual value is “experienced” when the resources / goods are
actually used by the customer to some purpose.
      </p>
      <p>For example, in the airline industry, jet turbine manufacturers used to follow a
classical goods-dominant logic by selling turbines to airlines. However, since airlines are
not interested in owning turbines, but rather in the realisation of airtime, manufacturers
nowadays sell airtime to airlines instead of jet turbines.</p>
      <p>
        Management literature [
        <xref ref-type="bibr" rid="ref12 ref24">42, 12, 24, 43</xref>
        ], therefore, also suggests that one should shift
from considering the value in exchange of a good or service, to its actual value in use.
The concept of using goods or services, should then specifically also be seen to include:
experiencing a work of art, enjoying a massage, impressing other people by wearing a
fancy watch, enjoying the ownership of an old timer car, watching a movie, savouring
a well cooked dinner, reading a book, listening to music, etc.
      </p>
      <p>In each case, the “-ing” ending also indicates a need for the consumer to
participate in the value creation. An important assertion underlying service-dominant logic
is therefore the notion of resource integration [41, 42, 44], where resources (goods,
competencies, processes, etc) of a supplier are integrated with the resources of the
consumer.</p>
      <p>Combined, value co-creation and resource integration, do lead to interesting
tradeoffs. For instance, in the context of the smart energy grid,6 an often used example of
(value) co-creation is the use of solar panels on houses, as well as the use of local
batteries (e.g. in house batteries, or the ones in an electric vehicle) to store excess energy
from the grid. Most of these examples assume that the owners of the house also own
the solar panels and batteries. However, are house owners really willing to own and
maintain the solar panels and the batteries? Conversely, are the energy companies /
“smart grid provider” keen to own and maintain these resources? An alternative would
be a situation in which the producers of the solar panels and the batteries would rent
these to the smart grid provider, while the owners of family houses would rent out roof
space and garage space to accomodate the solar panels and batteries respectively. Of
course, the owners of the house would then have to pay for electricity that may be
generated on the roof of their own house.</p>
      <p>A critical reader might wonder if value co-creation is really new in the first place.</p>
      <p>Was / is the work done by e.g. consultancy firms, not already a form of value
cocreation? We certainly would not want to claim that value co-creation did not occur
in “the past”. In our understanding, the definitions of value co-creation and
servicedominance, as provided by marketing literature, would not necessarily exclude such
examples from fitting the definition of service-dominant logic. Given the fact that
resource integration and value in use are key elements in defining value co-creation, one
could indeed argue that delivering consultancy services has always been a form of value
co-creation. A good consultant should integrate their resources with the resources of the
client, in order co-create value for the latter.</p>
      <p>Nevertheless, what we do observe as being new, is that the shift from goods-dominant
logic to service-dominant logic oriented towards value co-creation, would imply a
dramatic servitisation and mass customisation of existing products and services. These
latter developments also pose the bigger design challenges to existing (and startup)
enterprises, further fuelling the need to ensure that the modelling frameworks used are
indeed able to capture value co-creation considerations.</p>
      <p>In [43], eleven foundational premises defining service-dominant logic and value
cocreation have been provided, based on their earlier work reported in [41, 42, 44]. In
Figure 1, we have listed these foundational premises.</p>
      <p>6https://www.smartgrid.gov/the_smart_grid/smart_grid.html
FP01 Service is the fundamental basis of exchange.</p>
      <p>FP02 Indirect exchange masks the fundamental basis of exchange.</p>
      <p>FP03 Goods are distribution mechanisms for service provision.</p>
      <p>FP04 Operant resources are the fundamental source of strategic benefit.</p>
      <p>FP05 All economies are service economies.</p>
      <p>FP06 Value is co-created by multiple actors always including the beneficiary.</p>
      <p>FP07 Actors cannot deliver value but can participate in the creation and offering of value proposition.</p>
      <p>FP08 A service-centered view is inherently beneficiary oriented and relational.</p>
      <p>FP09 All social and economic actors are resource integrators.</p>
      <p>FP10 Value is uniquely and phenomenologically determined by the beneficiary.</p>
      <p>FP11 Value co-creation is coordinated through actor-generated institutions and institutional arrangements.</p>
      <p>
        In [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], the authors introduce spheres for value co-creation, while identifying
different roles that may be played by the actors involved in a value co-creation process
(see Figure 2). The critical aspect that needs to be highlighted from this work is that the
only “real” value creation occurs in the joint sphere, where customer and supplier are
co-creator and co-producer respectively, and in the customer sphere, where the roles are
creator and facilitator respectively. An important point to stress is that the role of the
supplier in the provider sphere is not one of value-creator but of value-facilitator, i.e.,
J. of the Acad. Mark. Sci. (201t3h) e41e:1n3t3i–r1e5i0nternal process of the provider does not create any value per-se. 141
instance, [43] reports on fundamental differences between the views of these authors,
and the work reported by Gro¨nroos, et al, in [
        <xref ref-type="bibr" rid="ref11 ref13 ref15">11, 15, 13</xref>
        ]. This indicates that there are
strongly opposing views regarding core notions in the context of service-dominant logic
(or service logic, as coined by [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]) and value co-creation.
      </p>
      <p>What is also interesting to note is the fact that the key (in terms of citations) papers
within the field of service-dominant logic, do not include many (let alone real world)
case studies involving actual value co-creation. Involving (real world) studies, could
possibly have improved the clarification of different views / opinions regarding core
concepts. In addition, in our view, the development of a modelling framework for the
architecting / design of service systems, while taking value co-creation aspects into
consideration, such cases certainly become essential. These cases, in particular the
underlying design challenges, should provide the use cases of the modelling framework.
4</p>
    </sec>
    <sec id="sec-4">
      <title>A participatory, case-driven, and fact-based, approach</title>
      <p>
        In line with [
        <xref ref-type="bibr" rid="ref16 ref17 ref18 ref7 ref8">16, 17, 18, 8, 7</xref>
        ], we argue that a modelling language, and designed
languages in general, should reflect the actual (intended) use of the language. As discussed
in Section 2, the intended use of the ValCoLa modelling framework is to be able to
express value co-creation constellations, including the needed infrastructural elements,
such as assumed institutions (in terms of rules, norms, meanings, symbols, practices,
and similar aides to collaboration), institutional arrangements, contracts, (information)
technological assets, etc, in support of the design / architecting of service systems.
      </p>
      <p>
        A purposely developed language (framework) is fundamentally an artefact in a
design science research [30] sense. As such, it would be appropriate to use the design
science research process as suggested in e.g. [30]. This process follows a traditional
(iterative) design process in the sense of requirements elicitation, design and
development, and then some form of testing / evaluation. In line with most design processes,
it also involves possible iterations. The process for the development of domain specific
modelling languages as suggested by [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] follows a similar pattern.
      </p>
      <p>
        The development of the ArchiMate [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ] language also followed such a design
process. The creation of the (original version of the) language, involved three Netherlands
based industrial partners7 with a rich experience in doing enterprise architecture, and
with a rather compatible understanding of enterprise architecture in terms of the
purpose, core concepts, layers, etc. Within the Netherlands, there was already a tradition
of exchanging views on, and experiences with, enterprise architecture.8 As a result, the
ArchiMate project partners had a similar understanding of the scope and purpose of the
language, the underlying core concepts, access to ample real-world cases, as well as
experienced enterprise architects.
      </p>
      <p>
        This enabled the ArchiMate project to establish a set of initial requirements [
        <xref ref-type="bibr" rid="ref20 ref4">4, 20</xref>
        ],
while the availability of real world cases from the partners, and the active involvement
of enterprise architects from these partners, allowed for an immediate inclusion of their
7The ABN-Amro bank, the ABP pension fund, and the Belastingdienst (Dutch Tax
Administration).
      </p>
      <p>
        8Amongst others resulting in a national platform such as the Netherlands Architecture Forum
(www.naf.nl).
experiences into the architecture of the language [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ], which then finally resulted in its
final detailed design [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]. Based on the broad acceptance in industry, the language was
consequently adopted as an industry standard [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ].
      </p>
      <p>For value co-creation the initial situation is quite different. As observed in the
previous Section, definitions of key concepts defining value co-creation are still debated,
while there is also no well documented body of cases that could potentially use cases
for the development of a modelling language. Furthermore, such cases could also be
beneficial to illustrate the definition of value co-creation in terms of positive and
negative examples of value co-creation. While the lack of cases might be seen as a signal
that such a language would not (yet) be called for, the discussion in Section 2 suggests
differently. We rather see it as a signal that, given the further servitisation of the
economy, real world cases of the development of value co-creation constellation, and the
development of the needed language framework, should go hand-in-hand. Having (first
versions of) a language framework, will also enable organisations to actually design
value co-creation constellations.</p>
      <p>
        In our view, the traditional design science research process falls short for the
development of ValCoLa. In [40], the authors suggest a variation of the design science
process, replacing the traditional build-evaluate pattern by a more finer grained
evaluation pattern that accommodates the emerging nature of artefacts. This would indeed
be more in line with the approach needed for language engineering, given the context
in which ValCoLa is to be developed. Therefore, for the development of ValCoLa, we
plan to use an iterative approach, where real world use cases are used for experiments
with different variations of the language. In doing so, we also plan to use a participative
approach involving language engineers and designers / architects. At the Luxembourg
Institute for Science and Technology, one of the two partners in the ValCoLa project,
this will involve real world cases in the context of compliance and risk management,
security and privacy management, the smart energy grid, as well as the use of open data
in the context of tourism and smart cities. Some of the initial experiments have already
been reported on in [
        <xref ref-type="bibr" rid="ref5 ref6">37, 5, 6, 38</xref>
        ].
      </p>
      <p>
        In future case studies, and experimentation, we will use the roles as identified in [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]
(see Figure 2) as a reference model, while using the foundational premises as articulated
in [43] as design / architecture principles [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], that will guide the design of service
systems for value co-creation.
      </p>
      <p>
        We consider it to be key to keep an open mind about which modelling constructs are
actually needed in the language, i.e. requiring explicit concepts in the abstract syntax,
as well as symbols / icons in the concrete syntax. To enable this, we will use a
factbased modelling approach [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] to express the value co-creation constellations in terms
of “flat” conceptual models first. By “flat”, we refer to the fact that such models will
be stated in terms of fact types involving roles and object types only, based directly on
the facts / statements used in the design dialogue involving designers / architects. These
flat conceptual models, will therefore not (yet) involve compound modelling constructs
(such as e.g. activity type, value object, business object, etc). In [35], it is discussed how,
e.g. ArchiMate models can be underpinned / grounded, in terms of a flat conceptual
model, using the verbalisations as used in the actual design dialogue.
      </p>
      <p>Based on the flat conceptual models from different value co-creation cases, we then
gain an evidence-based insight into what concepts needs to be embedded in the
language, and why this is needed. From this, we can then infer what compound modelling
constructs would be useful to indeed include in the language in terms of concepts in the
abstract syntax, and symbols in the concrete syntax.</p>
      <p>
        As mentioned in Section 2, in the development of the ValCoLa language
framework, no a-priori stance is taken with regard to the question if a new language should
be developed, or if (fragments of) existing modelling languages can be “re-used”. We
will therefore also use relevant language constructs / concepts from e.g. e3value [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ],
the notion of Value Encounters [46], the value stream concept introduced in the
latest version of ArchiMate [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], as well e.g. the business model canvas [29]. Using the
flat conceptual models taken from different cases involving value co-creation, we can
make evidence-based selection of the compound modelling constructs that are actually
needed for ValCoLa.
5
      </p>
    </sec>
    <sec id="sec-5">
      <title>Conclusion</title>
      <p>The primary focus of this paper was on a strategy for the development of ValCoLa, a
modelling framework for value co-creation constellations. This strategy has been
motivated in terms of a discussion of the concept of value co-creation from the perspective
of marketing literature.</p>
      <p>This also resulted in the observations that (1) a stable definition of the underlying
concepts has not been reached yet, while (2) an understanding of the actual design
challenges confronting enterprises in practice is also lacking, and even more importantly,
(3) reports on real-world cases involving the design of value co-creation constellations
are scant. As a result, the initial situation for the development of ValCoLa differs quite
substantially from the situation at the start of e.g. the ArchiMate project, thus also
requiring a different strategy.</p>
      <p>Based on this situational analysis, we plan to take a participatory, case-driven, and
fact-based, approach towards further experimentation and case studies in the further
development of the ValCoLa modelling framework.
26. F. Nordin and C. Kowalkowski. Solutions offerings: a critical review and reconceptualisation.</p>
      <p>Journal of Service Man., 21(4), 2010.
27. W. Norman and C. MacDonald. Getting the bottom of ’triple bottom line’. Business Ethics</p>
      <p>Quarterly, 14(2), 2004.
28. M. Op ’t Land, H. A. Proper, M. Waage, J. Cloo, and C. Steghuis. Enterprise Architecture –</p>
      <p>Creating Value by Informed Governance. Enterprise Engineering Series. Springer, 2008.
29. A. Osterwalder and Y. Pigneur. Business Model Generation: A Handbook for Visionaries,</p>
      <p>Game Changers, and Challengers. Self Published, Amsterdam, the Netherlands, 2009.
30. K. Peffers, T. Tuunanen, M. A. Rothenberger, and S. Chatterjee. A Design Science Research
Methodology for Information Systems Research. Journal of Management Information
Systems, 24(3):45–77, 2007.
31. C. K. Prahalad and V. Ramaswamy. Co-opting customer competence. Harvard Business</p>
      <p>Review, 78(1):79–87, 2000.
32. R. L. Priem. A consumer perspective on value creation. Academy of Management Review,
32(1):219–235, 2007.
33. R. L. Priem, J. E. Butler, and Li. S. Toward reimagining strategy research: restrospection
and prospection on the 2011 AMR decade award article. Academy of Management Review,
38(4):471–489, 2013.
34. H. A. Proper. Enterprise Architecture – Informed steering of enterprises in motion. In Proc.
of the 15th Int. Conf. (ICEIS 2013), Angers, France – Revised Selected Papers, volume 190
of LNBIP, pages 16–34. Springer, 2014.
35. H. A. Proper, M Bjekovic´, B. van Gils, and S. J. B. A. Hoppenbrouwers. Towards Grounded
Enterprise Modelling. In Proc. of the Fact-based Modelling Workshop (FBM 2017), held at
the On The Move (OTM) conference. Springer, 2017. Post-proceedings, to appear.
36. H. A. Proper, R. Winter, S. Aier, and S. de Kinderen, editors. Architectural Coordination of</p>
      <p>Enterprise Transformation . Enterprise Engineering Series. Springer, To appear 2018.
37. I. S. Razo-Zapata, E. Chew, and H. A. Proper. Visual Modeling for Value (Co-)Creation. In</p>
      <p>Proc. of the 10th Int. Workshop on Value Modelling and Business Ontologies (VMBO), 2016.
38. I. S. Razo-Zapata, E. Chew, and H. A. Proper. Towards VIVA: A VIsual Language to Model</p>
      <p>VAlue Co-creation. In The 5th Int. Conf. on Serviceology,, 2017.
39. A.-W. Scheer. ARIS – Business Process Modeling. Springer, 2000.
40. C. Sonnenberg and J. vom Brocke. Evaluations in the Science of the Artificial –
Reconsidering the Build-Evaluate Pattern in Design Science Research. In K. Peffers, M. Rothenberger,
and B. Kuechler, editors, Proc. of the 7th Int. Conf. on Design Science Research in
Information Systems and Technology (DESRIST 2012), Las Vegas, Nevada, volume 7286 of LNCS,
pages 381–397. Springer, 2012.
41. S. L. Vargo and R. F. Lusch. Evolving to a New Dominant Logic for Marketing. Journal of</p>
      <p>Marketing, 68:1–17, 2004.
42. S. L. Vargo and R. F. Lusch. Service-dominant logic: continuing the evolution. Journal of
the Academy of marketing Science, 36:1–10, 2008.
43. S. L. Vargo and R. F. Lusch. Institutions and axioms: an extension and update of
servicedominant logic. Journal of the Academy of Marketing Science, 44(1), January 2016.
44. S. L. Vargo, P. P. Maglio, and M. A. Akaka. On value and value co-creation: A service
systems and service logic perspective. European Management Journal, 26(3):145–152, 2008.
45. R. Wagter, H. A. Proper, and D. Witte. A Theory for Enterprise Coherence Governance. In</p>
      <p>A Systematic Perspective to Managing Complexity with EA. IGI Publishing, 2013.
46. H. Weigand. Value Encounters – Modeling and Analyzing Co-creation of Value. In C.
Godart, N. Gronau, S. Sharma, and G. Canals, editors, Software Services for e-Business and
e-Society, pages 51–64. Springer, 2009.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>I.</given-names>
            <surname>Band</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Ellefsen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Estrem</surname>
          </string-name>
          , M.-E. Iacob,
          <string-name>
            <given-names>H.</given-names>
            <surname>Jonkers</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. M. Lankhorst</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Nilsen</surname>
            ,
            <given-names>H. A.</given-names>
          </string-name>
          <string-name>
            <surname>Proper</surname>
            ,
            <given-names>D. A. C.</given-names>
          </string-name>
          <string-name>
            <surname>Quartel</surname>
            , and
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Thorn</surname>
          </string-name>
          .
          <source>ArchiMate 3</source>
          .0 Specification. The Open Group,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>J. G</given-names>
            <surname>Barnes</surname>
          </string-name>
          .
          <article-title>Establishing meaningful customer relationships: why some companies and brands mean more to their customers</article-title>
          .
          <source>Man. Service Quality: An Int. Journal</source>
          ,
          <volume>13</volume>
          (
          <issue>3</issue>
          ),
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>A.</given-names>
            <surname>Birger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Guarino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Johannesson</surname>
          </string-name>
          , and
          <string-name>
            <given-names>B.</given-names>
            <surname>Livieri</surname>
          </string-name>
          .
          <article-title>Towards an Ontology of Value Ascription</article-title>
          . In R. Ferrario and W. Kuhn, editors,
          <source>Formal Ontology in Information Systems, number 283 in Frontiers in Artificial Intelligence and Applications</source>
          , pages
          <fpage>331</fpage>
          -
          <lpage>344</lpage>
          . IOS Press,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>H.</given-names>
            <surname>Bosma</surname>
          </string-name>
          , H. W. L. ter
          <string-name>
            <surname>Doest</surname>
            , and
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Vos</surname>
          </string-name>
          . Requirements.
          <source>Technical Report ArchiMate Deliverabe D4</source>
          .1, TI/RS/
          <year>2002</year>
          /112,
          <string-name>
            <surname>Telematica</surname>
            <given-names>Instituut</given-names>
          </string-name>
          ,
          <year>December 2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>C.</given-names>
            <surname>Feltus</surname>
          </string-name>
          and
          <string-name>
            <given-names>H. A.</given-names>
            <surname>Proper</surname>
          </string-name>
          .
          <article-title>Conceptualization of an Abstract Language to Support Value Co-Creation</article-title>
          .
          <source>In 12th Conf. on Information Systems Management (ISM'17)</source>
          ,
          <source>Federated Conferences on Computer Science and Information Systems</source>
          , Prague, Czech Republic,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>C.</given-names>
            <surname>Feltus</surname>
          </string-name>
          and
          <string-name>
            <given-names>H. A.</given-names>
            <surname>Proper</surname>
          </string-name>
          .
          <article-title>Towards a Security and Privacy Co-Creation Method</article-title>
          .
          <source>In IEEE Int. Conf. for Internet Technology and Secured Transactions (ICITST-2017)</source>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>U.</given-names>
            <surname>Frank</surname>
          </string-name>
          .
          <article-title>Some Guidelines for the Conception of Domain-Specific Modelling Languages</article-title>
          . In M. Nu¨ ttgens, O. Thomas, and B. Weber, editors,
          <source>Proc. of the 4th Int. Workshop on Enterprise Modelling and Information Systems Architectures (EMISA</source>
          <year>2011</year>
          ), number 190 in LNI, pages
          <fpage>93</fpage>
          -
          <lpage>106</lpage>
          . Gesellschaft fu¨r Informatiek,
          <year>September 2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>U.</given-names>
            <surname>Frank</surname>
          </string-name>
          .
          <article-title>Domain-Specific Modeling Languages: Requirements Analysis and Design Guidelines</article-title>
          . In I.
          <string-name>
            <surname>Reinhartz-Berger</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Sturm</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Clark</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Cohen</surname>
          </string-name>
          , and J. Bettin, editors, Domain Engineering - Product
          <string-name>
            <surname>Lines</surname>
          </string-name>
          ,
          <source>Languages, and Conceptual Models</source>
          . Springer,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>J.</given-names>
            <surname>Gordijn</surname>
          </string-name>
          and
          <string-name>
            <given-names>H.</given-names>
            <surname>Akkermans</surname>
          </string-name>
          .
          <article-title>Value based requirements engineering: Exploring innovative e-commerce ideas</article-title>
          .
          <source>Requirements Engineering Journal</source>
          ,
          <volume>8</volume>
          (
          <issue>2</issue>
          ):
          <fpage>114</fpage>
          -
          <lpage>134</lpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <given-names>D.</given-names>
            <surname>Greefhorst</surname>
          </string-name>
          and
          <string-name>
            <given-names>H. A.</given-names>
            <surname>Proper</surname>
          </string-name>
          .
          <source>Architecture Principles - The Cornerstones of Enterprise Architecture. Enterprise Engineering Series</source>
          . Springer,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>C.</surname>
          </string-name>
          <article-title>Gro¨ nroos</article-title>
          .
          <source>Service Logic Revisited: Who Creates Value? And Who Co-creates? European Business Review</source>
          ,
          <volume>20</volume>
          (
          <issue>4</issue>
          ):
          <fpage>298</fpage>
          -
          <lpage>314</lpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>C.</surname>
          </string-name>
          <article-title>Gro¨ nroos and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Ravald</surname>
          </string-name>
          .
          <article-title>Service as Business Logic: Implications for Value Creation and Marketing</article-title>
          .
          <source>Journal of Service Man.</source>
          ,
          <volume>22</volume>
          (
          <issue>1</issue>
          ):
          <fpage>5</fpage>
          -
          <lpage>22</lpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>C.</surname>
          </string-name>
          <article-title>Gro¨ nroos and</article-title>
          <string-name>
            <given-names>P. J.</given-names>
            <surname>Voima</surname>
          </string-name>
          .
          <article-title>Critical service logic: making sense of value creation and co-creation</article-title>
          .
          <source>Journal of the Academy of Marketing Science</source>
          ,
          <volume>41</volume>
          (
          <issue>2</issue>
          ):
          <fpage>133</fpage>
          -
          <lpage>150</lpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <given-names>T. A.</given-names>
            <surname>Halpin</surname>
          </string-name>
          and
          <string-name>
            <given-names>T.</given-names>
            <surname>Morgan</surname>
          </string-name>
          . Information Modeling and
          <string-name>
            <given-names>Relational</given-names>
            <surname>Databases</surname>
          </string-name>
          .
          <article-title>Data Management Systems</article-title>
          . Morgan Kaufman, 2nd edition,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <given-names>K.</given-names>
            <surname>Heinonen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Strandvik</surname>
          </string-name>
          ,
          <string-name>
            <surname>K.-J. Mickelsson</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Edvardsson</surname>
            , E. Sundstro¨ m, and
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Andersson</surname>
          </string-name>
          .
          <article-title>A customer-dominant logic of service</article-title>
          .
          <source>Journal of Service Man.</source>
          ,
          <volume>21</volume>
          (
          <issue>4</issue>
          ):
          <fpage>531</fpage>
          -
          <lpage>548</lpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <given-names>S. J. B. A.</given-names>
            <surname>Hoppenbrouwers</surname>
          </string-name>
          .
          <article-title>A Functionalist Approach to Conceptualisation</article-title>
          .
          <source>In Proc. of the Fourth Int. Workshop on the Language Action Perspective on Communication Modelling (LAP</source>
          <year>2000</year>
          ), Aachener Informatik-Berichte, Aachen, Germany,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <given-names>S. J. B. A.</given-names>
            <surname>Hoppenbrouwers</surname>
          </string-name>
          . Freezing Language;
          <article-title>Conceptualisation processes in ICT supported organisations</article-title>
          .
          <source>PhD thesis</source>
          , University of Nijmegen, Nijmegen, the Netherlands,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <given-names>S. J. B. A.</given-names>
            <surname>Hoppenbrouwers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. A.</given-names>
            <surname>Proper</surname>
          </string-name>
          , and
          <string-name>
            <surname>Th</surname>
          </string-name>
          . P. van der Weide.
          <source>Understanding the Requirements on Modelling Techniques. In O. Pastor and J</source>
          . Falcao e Cunha, editors,
          <source>17th Int. Conf. on Advanced Information Systems Engineering, CAiSE</source>
          <year>2005</year>
          , Porto, Portugal, volume
          <volume>3520</volume>
          <source>of LNCS</source>
          , pages
          <fpage>262</fpage>
          -
          <lpage>276</lpage>
          . Springer,
          <year>June 2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>M.-E. Iacob</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Jonkers</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. M. Lankhorst</surname>
            , and
            <given-names>H. A.</given-names>
          </string-name>
          <string-name>
            <surname>Proper</surname>
          </string-name>
          .
          <source>ArchiMate 1</source>
          .0 Specification. The Open Group,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20. H.
          <string-name>
            <surname>Jonkers</surname>
            ,
            <given-names>G. E.</given-names>
          </string-name>
          <string-name>
            <surname>Veldhuijzen van Zanten</surname>
            ,
            <given-names>F. van Buuren</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            and
            <surname>Arbab</surname>
          </string-name>
          , F. de Boer,
          <string-name>
            <given-names>M.</given-names>
            <surname>Bonsangue</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Bosma</surname>
          </string-name>
          , H. ter
          <string-name>
            <surname>Doest</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Groenewegen</surname>
            ,
            <given-names>J. Guillen</given-names>
          </string-name>
          <string-name>
            <surname>Scholten</surname>
            ,
            <given-names>S. J. B. A.</given-names>
          </string-name>
          <string-name>
            <surname>Hoppenbrouwers</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.-E. Iacob</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          <string-name>
            <surname>Janssen</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. M. Lankhorst</surname>
            , D. van Leeuwen,
            <given-names>H. A.</given-names>
          </string-name>
          <string-name>
            <surname>Proper</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Stam</surname>
            , and
            <given-names>L. van der</given-names>
          </string-name>
          <string-name>
            <surname>Torre</surname>
          </string-name>
          .
          <article-title>Towards a Language for Coherent Enterprise Architecture Descriptions</article-title>
          . In M. Steen and
          <string-name>
            <surname>B. R</surname>
          </string-name>
          . Bryant, editors,
          <source>Proc. of the 7th IEEE Int. Enterprise Distributed Object Computing Conf. (EDOC</source>
          <year>2003</year>
          ), , pages
          <fpage>28</fpage>
          -
          <lpage>39</lpage>
          , Los Alamitos, California,
          <year>September 2003</year>
          . IEEE Explore.
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>M. M. Lankhorst</surname>
            ,
            <given-names>H. A.</given-names>
          </string-name>
          <string-name>
            <surname>Proper</surname>
            , and
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Jonkers</surname>
          </string-name>
          .
          <article-title>The Anatomy of the ArchiMate Language</article-title>
          .
          <source>Int. Journal of Information System Modeling and Design</source>
          ,
          <volume>1</volume>
          (
          <issue>1</issue>
          ):
          <fpage>1</fpage>
          -
          <lpage>32</lpage>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>M. M. Lankhorst</surname>
          </string-name>
          , et al.
          <source>Enterprise Architecture at Work: Modelling, Communication and Analysis</source>
          . Springer,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <given-names>D. P.</given-names>
            <surname>Lepak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K. G.</given-names>
            <surname>Smith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>and M. S.</given-names>
            <surname>Taylor</surname>
          </string-name>
          .
          <article-title>Value creation and value capture: a multilevel perspective</article-title>
          .
          <source>Academy of Management Review</source>
          ,
          <volume>32</volume>
          (
          <issue>1</issue>
          ):
          <fpage>180</fpage>
          -
          <lpage>194</lpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <given-names>R. F.</given-names>
            <surname>Lusch</surname>
          </string-name>
          and
          <string-name>
            <given-names>S.</given-names>
            <surname>Nambisan. Service Innovation</surname>
          </string-name>
          :
          <article-title>A Service-Dominant Logic Perspective</article-title>
          .
          <source>MIS Quarterly</source>
          ,
          <volume>39</volume>
          (
          <issue>1</issue>
          ):
          <fpage>155</fpage>
          -
          <lpage>175</lpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <given-names>R.</given-names>
            <surname>Magalha</surname>
          </string-name>
          <article-title>˜es and</article-title>
          <string-name>
            <given-names>H. A.</given-names>
            <surname>Proper</surname>
          </string-name>
          .
          <article-title>Model-enabled Design and Engineering of Organisations</article-title>
          .
          <source>Organisational Design and Enterprise Engineeering</source>
          ,
          <volume>1</volume>
          (
          <issue>1</issue>
          ):
          <fpage>1</fpage>
          -
          <lpage>12</lpage>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>