<!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>Configuration Lifecycle Management - An Assessment of the Benefits Based on Maturity</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Anna Myrodia</string-name>
          <email>amyrodia@configit.com</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Thomas Randrup</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Lars Hvam</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>1To handle the increasing product complexity manufacturing companies of configurable products tend to utilize configurators to cover more lifecycle phases of their products. This is described as configuration lifecycle management (CLM) and it is concerned with the management of all configuration models across a product's lifecycle. However, to connect and align all configurators and IT systems to each other remains a challenging task. Apart from the technical perspective, on an operational level the integration and alignment of the IT systems also requires a structured approach and is highly related to the maturity of the organization. Therefore, this research focuses on studying the relation between the maturity level and the expected benefits from implementing CLM. It is expected that the more advanced an organization is in using product configurators in different lifecycle phases and integrating and aligning them to each other and to other IT systems, the realized benefits would be significantly higher than the sum of benefits from applying standalone configurators to support each life cycle phase. Empirical evidence from seven case studies demonstrate that there is a relation between the maturity and the realized benefits with regards to the utilization of product configurators.</p>
      </abstract>
      <kwd-group>
        <kwd>configuration benefits</kwd>
        <kwd>product configuration</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>INTRODUCTION</title>
      <p>Configuration lifecycle management (CLM) describes the
management of all configuration models and related data across all
lifecycle phases of a product [1]. A CLM solution is highly
relevant for manufacturing companies of configurable products, as
its purpose is to provide one valid source of configuration data and
models that is shared among different business units within an
organization.</p>
      <p>The utilization of product configurators comes along with
various benefits. During the last decades, several researchers have
performed studies to identify and measure the realized benefits of
the use of a product configurator [2–4]. The identified benefits
cover a wide range of aspects, from process improvements to
impact on products’ profitability. However, the majority of these
studies are concerned with configurators that are implemented in
the sales phase and some in the engineering phase [2,3] .</p>
      <p>Therefore, the focus of this research is to identify possible gains
when the utilization of a product configurator is not limited only to
the sales phases, but it includes all lifecycle phases of a
configurable product, such as engineering, sales, manufacturing
and service. It is expected that the realized benefits would be
similar but not identical in the remaining lifecycle phases and that
the accumulated impact would be significantly higher than the
gains on each individual lifecycle phase.</p>
      <p>For an organization, to be able to implement and connect
product configurators across all lifecycle phases and business
processes is considered a rather challenging task. When it comes to
the utilization of a configurator in the sales phase, there are
numerous challenges identified not only by the literature but also
from industrial user cases [5,6]. Resistance to change, difficulties
in data acquisition and verification, valid product modeling and
maintenance of the models, accurate documentation are some of
the most commonly reported challenges in the utilization of
product configurators in the sales phases [7,8] .</p>
      <p>It could be assumed that similar challenges are expected to be
experienced in the other lifecycle phases during the
implementation and utilization of a product configurator. However,
this research claims that even though some of the challenges would
be faced in all lifecycle phases, there several aspects that are not
addressed in them. For instance, developing a universal product
model to be used by several configurators across all lifecycle
phases, business units, even external organizations (e.g. suppliers,
resellers, vendors) requires input from various sources and is
highly related to numerous dimensions of the organization [9].</p>
      <p>
        In particular, the integration of product configurators with other
IT systems for data exchange, as input and/or output of each
configuration step, is considered a rather challenging task,
especially when it comes to IT systems that are used by several
departments [
        <xref ref-type="bibr" rid="ref10 ref12 ref18 ref21 ref23 ref26 ref29 ref3 ref5 ref7">10</xref>
        ]. Apart from the technical challenge of
connecting, aligning and integrating IT systems with product
configurators, the operational perspective is of high importance and
it should not be discarded. At an operational level, the process
standardization, resources allocation, knowledge sharing and
support, established ways of cross-departmental collaboration are
some of the factors that are highly related to the success of
utilization a CLM solution [
        <xref ref-type="bibr" rid="ref10 ref12 ref18 ref21 ref23 ref26 ref29 ref3 ref5 ref7">6,7,10,11</xref>
        ]. Additionally, on a strategic
level a clear mission and vision for CLM deployment,
communication to all stakeholders and engagement with specific
goals for each involved department are of great importance and
highly related to the level of success of the CLM solution.
      </p>
      <p>All these aspects mentioned before that influence the success of
a CLM solution are related to the maturity of an organization.
Maturity in this context does not only describe the development of
the IT systems and the possibilities of seamless integration of a
universal product model for a CLM solution. Maturity also
describes the process and the organizational development, from an
operational, strategic and cultural point of view [12,13]. The
readiness of an organization to implement and utilize a CLM
solution, and the support and involvement of the stakeholders are
crucial success factors for a CLM solution.</p>
      <p>As a result, it is expected that the more mature an organization
is, the higher the realized benefits would be. Therefore, this
research relates the expected benefits to the maturity of the
organization. The maturity is evaluated in terms of years of
implementation of product configurators and the spam of lifecycle
phases they cover. The expected benefits of a CLM solution are
estimated to be higher than these of standalone configurators in the
different lifecycle phases. Exploratory case studies are conducted
to examine this proposition.</p>
      <p>Proposition 1 The size of realized benefits when implementing
a CLM solution is related to the maturity of the organization.</p>
      <p>The remainder of the paper is structured as follows. Section 2
includes a literature review on the expected benefits from the use
of product configurators in different lifecycle phases and the
characteristics of maturity of an organization. Section 3 presents
the empirical evidence from the case study research and discusses
the results. Section 4 provides some overall conclusions regarding
the connection of realized benefits and the maturity of an
organization when implementing a CLM solution.</p>
    </sec>
    <sec id="sec-2">
      <title>LITERATURE REVIEW 2 2.1</title>
    </sec>
    <sec id="sec-3">
      <title>Benefits from implementing product configurators</title>
      <p>This section discusses the findings from the literature regarding the
expected benefits from implementing and utilizing product
configurators. As this field has been examined in detail, we refer to
previous work [2,3,11,14–16] and their lists of references.
However, to provide an overview we present a short list of realized
benefits for the different lifecycle phases (Table 1).</p>
      <p>The benefits are grouped under each lifecycle phase to provide a
better overview when it comes to implementing a CLM solution,
and they address three main factors: time, quality and cost [17].
However, it should be mentioned that that are some common
benefits reported across all lifecycle phases, such as improved
process efficiency, reduction of hours spent due to iterations,
improved data validity, improved quality due to reduction in the
number of errors.
2.2</p>
    </sec>
    <sec id="sec-4">
      <title>Maturity</title>
      <p>The maturity assessment of an organization includes several
dimensions and maturity models are the tools used to perform the
evaluation. Strategy, processes, IT, organizational structure,
knowledge sharing and support activities are among the most
widely discussed dimensions in the literature that describe most
accurately all functions of an organization [12,18]. The maturity is
measured in each of these dimensions; however, the maturity level
does not have necessarily to be the same across all of them. This
could explain why companies implementing state of the art
configurators are still not able to experience all the expected
benefits. This is aligned to the findings of [19] that business
processes and IT alignment should fit into the organization.</p>
      <p>The improvement of configuration management policies and
tools, and the establishment of requirement engineering processes
are considered top priorities of organization maturity. Seamless
integration, knowledge management, monitoring, support and
training activities for the users are additional aspects related to the
maturity and affect the success of implementing a configuration
solution [20]. Empirical studies also indicate that the maturity of IT
processes is connected to the gap between organizational targets
and processes’ aims [21].</p>
      <p>Challenges in realizing expected benefits are identified in the
sales and planning process [22–24] and are connected to the need
of horizontal reorganizational of the structure to include customer
and supply chain stakeholders [25]. The current vertical
organization structure is a source of delays, increased costs and
challenges of managing subcontractors [20]. This is also supported
by [26] who claim that when the manufacturing company is in
control of the entire supply chain and it is able to coordinate
internal and external processes, then it is more mature and can gain
a competitive advantage [27,28].</p>
      <p>One aspect of knowledge management related to the maturity of
an organization is the lack of overview of the product portfolio,
which is due to increased complexity. Keeping external variety
high to satisfy personalized customer needs to be induced by
controlled internal variety and product standardization to avoid
increasing costs and complexity [28].</p>
      <p>According to [12], the maturity of an organization is increasing
based on the level of standardization. That includes both
standardization of products and processes. Consequently, this
would have direct impact of the realized benefits by utilizing a
product configurator, even more when it comes to CLM. However,
this alignment and standardization is a task that requires time as it
comes along with numerous changes in the organization [6,29]. It
is expected that the higher the maturity of an organization is, the
higher the gains form the realized benefits would be by the use of
product configurators, especially across all lifecycle phases. This is
identified as an area not explored by the existing literature.</p>
      <p>Even though the research from [12] focuses on the ETO
companies, the underlying principles can be extrapolated and used
for manufacturers of standard but complex products too, such as
the examined case studies. Therefore, this research aims at
contributing to this field by providing some empirical evidence to
test the developed proposition.
3</p>
    </sec>
    <sec id="sec-5">
      <title>EMPIRICAL EVIDENCE</title>
      <p>To examine the suggested proposition, case research is selected as
the research method. The main reason for selecting case research is
that allows for comparison of the results across different case
companies, where the analysis has been conducted under the same
settings and followed a research protocol. In this study, 7
companies are used as cases. Through the case research the under
examination phenomenon is studied in its natural settings and it
allows for deeper understanding of phenomena that are not fully
examined [30–32]. In this research, the under investigation
phenomenon is the one described in the proposition; the relation
between the size of realized benefits and the maturity of an
organization with regards to the implementation of CLM. The
following section provides an introduction to the companies and
the set-up of the research, presents and
analyzes the results.
3.1</p>
    </sec>
    <sec id="sec-6">
      <title>Background</title>
      <p>For this study 7 manufacturing companies (A – G) were contacted.
All of them are designing, selling, producing and servicing highly
engineered and complex products. All the companies have been
utilizing product configurators to support at least one lifecycle
phase of their products. Furthermore, all 7 companies are large
organizations, employing more than 1000 people, and they are
operating globally, in terms of market, production facilities and
suppliers. They have been utilizing product configurators for at
least 2 years before the research was conducted. Table 2 provides
an overview of the selected cases regarding their main
characteristics and the lifecycle phases they are utilizing a product
configurator.
In each of the case companies’ data collection included interviews
with managers and head of departments that have been using a
product configurator. The form of the interviews was
semistructured, to ensure that the relevant data were collected and to
allow for some discussions regarding future directions and
initiatives towards a CLM solution. All managers were asked the
same set of questions to provide information regarding the use of
configurators, the lifecycle phases they cover, and the realized
benefits they have been experiencing or measuring. The benefits
were predefined, based on the results of the literature review. To
ensure the validity of the results, two persons from each company
we interviewed separately.</p>
      <p>During the interviews, the different maturity dimensions were
discussed. Since this is an exploratory study, the focus was given
A
B
C
D
E
F
G</p>
      <p>IE&amp;M
(Mechanical)</p>
      <p>IE&amp;M
(Mechanical)</p>
      <p>IE&amp;M
(Medical)</p>
      <p>IE&amp;M
(Mechanical)
Automotive</p>
      <p>IE&amp;M
(Agriculture)
IE&amp;M (Electrical)</p>
      <p>Lifecycle phase</p>
      <p>Sales
Sales
Sales
Sales</p>
      <p>Sales,
Engineering</p>
      <p>Sales,
Engineering</p>
      <p>Sales,
Engineering</p>
      <p>No. of years
utilizing product
configurators
3
2
5
6
7
7
3
on process standardization and cross-organizational collaboration.
Process standardization is assessed based on the following two
criteria; the number of manual tasks that need to be performed on
top of the use of the product configurator, and the generated
documentation following the actual configuration process.
Crossorganizational collaboration is assessed based on the number of
teams from different departments that are using the product
configurator or providing input when setting up the configuration
models. In addition to these findings, the research team took into
account the number of years that each company has been using
configurators and the number lifecycle phase they cover, to assess
the maturity of each case company. The assigned maturity level
varies among low-medium-high. Table 3 presents the results of the
analysis.</p>
      <p>As it can be seen from Table 3, the number of realized benefits
is increasing along with the maturity of the organization. In detail,
case companies E, F and G are ranked with medium maturity level
due to the fact that they have cross-organizational implementation
of product configurators. Even though case company G has been
using product configurators for 3 years, which is relatively lower
than cases C and D, its level of maturity is still considered to be
medium, due to the fact that it has fully standardized and
automated processes, and minimum manual work required on top
of the use of the configurators across the sales and the engineering
teams. In all these three cases, when setting up the product models
in the configurator teams from both the sales and the engineering
departments were involved. Teams from these two departments
also undertake the maintenance and the update of product related
data in the configurator, while at the same time product related data
for the sales and the engineering phases are handled via the
configurator. The realized benefits reported are related to the
process standardization, control of complexity, knowledge
management and data validity.</p>
      <p>Case companies A, B, C and D are utilizing a configurator in
the sales phase, therefore the reported benefits are related to cost
estimation, quotation and sales efficiency. It should also be
mentioned that case company C was the only one able to provide
quantitative data regarding the realized benefits. Company C
reported that it has managed to reduce the hours used for preparing
quotations by 50% (from days to hours). Due to the reduction of
errors in the specifications in the sales phase, they have managed to
reduce the costs of poor quality in production with 80% due to
more accurate production specification.</p>
      <p>By summarizing the results can be concluded that there is a
relation to the maturity level of an organization and the size of
realized benefits. This confirms the under investigation proposition
in this study.
3.3</p>
    </sec>
    <sec id="sec-7">
      <title>Discussion</title>
      <p>The benefits identified in the case studies are aligned to the
findings from the literature. On a high level it can be concluded
that all the benefits can be grouped under the three categories
suggested in the literature; time, quality and cost [17]. This
conclusion can be used for assigning key performance indicators
(KPIs) to monitor and measure the performance of different factors
that have a direct impact on these three categories. The KPIs
should both cover the lifecycle management aspects of the
configurable products and the configuration process itself (detailed
examples of KPIs can be found at [33]). By providing quantitative
data the companies would have a more accurate assessment of the
improvements they have established due to the use of the product
configuration.</p>
      <p>Furthermore, the results from the case studies indicate that
process standardization is a cornerstone for a successful
implementation of configurators. Case company G is such an
example; even though the implementation of the configurator s
relatively new (3 years) by standardizing the sales and the
engineering processes, they managed to achieve the highest
number of benefits across the examined cases. This is because by
standardizing the processes, the management of configuration
models can be improved [34], and the knowledge encapsulated
within these models can be used in different lifecycle phase by
different users [35]. In the sales phase, the utilization of the
configurator is more mature and is usually where the companies
are starting. This can be explained by [6] as sales configurators are
proven tools and the most popular solutions both in the industry
and in academic research.</p>
      <p>However, the findings show that several gains can be
experienced in the engineering phase. These benefits might be
identical to the ones from the sales phase, such as improved
efficiency, quality and lead time, but are also phase specific, such
as scalability of product models, product platform design and BOM
validation.</p>
      <p>Nevertheless, the results cannot be generalized to all lifecycle
phases based on this case study, as none of there were no empirical
evidence from the manufacturing and service phase in these cases.
It can be argued, that in a similar way as in the sales and
engineering phase, benefits can be gained across all lifecycle phase
of a configurable product. It can also be assumed that the more
phases the configurators cover, the higher the degree of process
standardization and knowledge sharing across the organization.
4</p>
    </sec>
    <sec id="sec-8">
      <title>CONCLUSION</title>
      <p>The scope of this study is to examine the relationship between the
realized benefits from the use of product configurators across all
lifecycle phase of a product and the maturity level of the
organization. The developed proposition is tested in 7 case
companies and the study reveals a direct relation between these
two variables.</p>
      <p>This is an exploratory study. The main limitation of this
research is the generalizability of the results, which can be
improved by having a more in depth investigation of the
phenomenon.</p>
      <p>Future research will include more cases that are using product
configurators in the manufacturing and service phase. This will be
examined in relation to the maturity of the organization, not only in
terms of product and process standardization, but also strategic
initiatives, knowledge sharing and support, degree of integration of
IT systems. Finally, another factor that should be examined is the
complexity of the configuration process, regarding the size of the
models, the number of features, rules, and the number of users.
This could also provide some insight regarding the implementation
strategy that would improve the user-friendliness and the
acceptance rate of the new system by its users.</p>
      <p>Configit</p>
      <p>A/S,</p>
      <p>CLM</p>
      <p>L. Hvam, M. Malis, B. Hansen, J. Riis, Reengineering of the
quotation process: application of knowledge based systems, Bus.
Process Manag. J. 10 (2004) 200–213.
doi:10.1108/14637150410530262.</p>
      <p>M.M. Ahmad, N. Dhafr, Establishing and improving
manufacturing performance measures, Robot. Comput. Integr.
Manuf. 18 (2002) 171–176.</p>
      <p>M. Niknam, P. Bonnal, J. Ovtcharova, Configuration
management maturity in scientific facilities, Int. J. Adv. Robot.
Syst. 10 (2013) 1–14. doi:10.5772/56853.</p>
      <p>R. Batenburg, R.W. Helms, J. Versendaal, PLM roadmap:
stepwise PLM implementation based on the concepts of maturity
and alignment, Int. J. Prod. Lifecycle Manag. 1 (2006) 333.
doi:10.1504/IJPLM.2006.011053.</p>
      <p>G. Cugola, L. Lavazza, V. Nart, S. Manca, M.R. Pagone, An
experience in setting-up a configuration management
environment, in: Proc. Eighth IEEE Int. Work. Softw. Technol.
Eng. Pract. Inc. Comput. Aided Softw. Eng., IEEE Comput. Soc,
1997: pp. 251–262. doi:10.1109/STEP.1997.615501.</p>
      <p>M.A. Vitoriano Vieira, J.S. Neto, INFORMATION
TECHNOLOGY SERVICE MANAGEMENT PROCESSES
MATURITY IN THE BRAZILIAN FEDERAL DIRECT
ADMINISTRATION, J. Inf. Syst. Technol. Manag. 12 (2015)
663–686.</p>
      <p>P. Bower, 12 most common threats to sales and operations
planning process, J. Bus. Forecast. 24 (2005) 4–14.</p>
      <p>L. Lapide, Sales and operations planning part I: The process, J.
Bus. Forecast. 23 (2004) 17–19.</p>
      <p>J. Piechule, Implementing a sales and operations planning process
at Sartomer company: a grass-roots approach, J. Bus. Forecast. 27
(2008) 13–18.</p>
      <p>N. Tuomikangas, R. Kaipia, A coordination framework for sales
and operations planning (S&amp;OP)_ Synthesis from the literature,
Intern. J. Prod. Econ. 154 (2014) 243–262.
doi:10.1016/j.ijpe.2014.04.026.</p>
      <p>P.E. Stavrulaki, P.M. Davis, Aligning products with supply chain
processes and strategy, Int. J. Logist. Manag. 21 (2010) 127–151.
doi:10.1108/95740931080001326.</p>
      <p>C. Hicks, T. McGovern, C.F. Earl, A Typology of UK
Engineerto-Order Companies, Int. J. Logist. Res. Appl. 4 (2001) 43–56.
doi:10.1080/13675560110038068.</p>
      <p>M.H. Mello, J.O. Strandhagen, E. Alfnes, Analyzing the factors
affecting coordination in engineer-to-order supply chain, Int. J.
Oper. Prod. Manag. J. Manuf. Technol. Manag. Iss Int. J. Oper.
&amp;amp; Prod. Manag. 35 (2015) 1005–1031.
https://doi.org/10.1108/IJOPM-12-2013-0545.</p>
      <p>T. De Bruin, Business Process Management: Theory on
Progression and Maturity, Queensland University of Technology,
2009.</p>
      <p>J. Meredith, Building operations management theory through case
and field research, J. Oper. Manag. 16 (1998) 441–454.
doi:10.1016/S0272-6963(98)00023-0.</p>
      <p>C. Voss, N. Tsikriktsis, M. Frohlich, Case research in operations
management, Int. J. Oper. Prod. Manag. 22 (2002) 198–219.
doi:10.1108/01443570210414329.
[32]
[33]
[34]
[35]
Engineering</p>
      <p>Improve efficiency and scalability of product modeling
Bill of material validation
Component optimization
Improve quality - Reduction of number of errors
Improved technology management
Increase productivity
Increased sales
Improve competitiveness
Reduction in printing costs and distribution of catalogues
Improve process efficiency
Reduce cost of IT systems and maintenance
Improve functionality of integrated IT systems
Reduction of complexity
Reduced quotation time
X
X
X
X
X</p>
      <p>D
L
X
X
X
No. of benefits per case
X
X
X
X
X
X
X
X
X
X
X
X</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          https://configit.com/configit_wordpress/wpcontent/uploads/2015/10/CLM-Declaration-
          <year>2015</year>
          .pdf (
          <issue>accessed January 8</issue>
          ,
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <given-names>A.</given-names>
            <surname>Myrodia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Kristjansdottir</surname>
          </string-name>
          , L. Hvam,
          <article-title>Impact of product configuration systems on product profitability and costing accuracy</article-title>
          ,
          <source>Comput. Ind. Ind</source>
          .
          <volume>88</volume>
          (
          <year>2017</year>
          )
          <fpage>12</fpage>
          -
          <lpage>18</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <source>doi:10</source>
          .1016/j.compind.
          <year>2017</year>
          .
          <volume>03</volume>
          .001.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <given-names>K.</given-names>
            <surname>Kristjansdottir</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Shafiee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Hvam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Bonev</surname>
          </string-name>
          ,
          <string-name>
            <surname>A. Myrodia,</surname>
          </string-name>
          <article-title>Return on investment from the use of product configuration systems - A case study</article-title>
          ,
          <source>Comput. Ind</source>
          .
          <volume>100</volume>
          (
          <year>2018</year>
          )
          <fpage>57</fpage>
          -
          <lpage>69</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <source>doi:10</source>
          .1016/j.compind.
          <year>2018</year>
          .
          <volume>04</volume>
          .003.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <given-names>A.</given-names>
            <surname>Haug</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Hvam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.H.</given-names>
            <surname>Mortensen</surname>
          </string-name>
          ,
          <article-title>The impact of product configurators on lead times in engineering-oriented companies</article-title>
          ,
          <source>Artif. Intell. Eng. Des. Anal. Manuf</source>
          .
          <volume>25</volume>
          (
          <year>2011</year>
          )
          <fpage>197</fpage>
          -
          <lpage>206</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <source>doi:10</source>
          .1017/S0890060410000636.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <source>(MCSEAI</source>
          <year>2004</year>
          ),
          <year>2004</year>
          : pp.
          <fpage>25</fpage>
          -
          <lpage>36</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <string-name>
            <given-names>C.</given-names>
            <surname>Forza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Salvador</surname>
          </string-name>
          ,
          <article-title>Managing for variety in the order acquisition and fulfilment process: The contribution of product configuration systems</article-title>
          ,
          <source>Int. J. Prod. Econ</source>
          .
          <volume>76</volume>
          (
          <year>2002</year>
          )
          <fpage>87</fpage>
          -
          <lpage>98</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          <source>doi:10</source>
          .1016/S0925-
          <volume>5273</volume>
          (
          <issue>01</issue>
          )
          <fpage>00157</fpage>
          -
          <lpage>8</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          <string-name>
            <surname>Environ</surname>
          </string-name>
          . Integr. Hum. Factors, IGI Global,
          <year>2009</year>
          : pp.
          <fpage>75</fpage>
          -
          <lpage>106</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          <source>doi:10.4018/978-1-60566-260-2</source>
          .
          <year>ch006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <string-name>
            <given-names>M.</given-names>
            <surname>Heiskala</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.-S.</given-names>
            <surname>Paloheimo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Tiihonen</surname>
          </string-name>
          , Mass Customisation of Services: Benefits and Challenges of Configurable Services, Tampere, Finland,
          <year>2005</year>
          ..
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          <string-name>
            <surname>Mater</surname>
          </string-name>
          . Manag.
          <volume>19</volume>
          (
          <year>1989</year>
          )
          <fpage>3</fpage>
          -
          <lpage>8</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          <string-name>
            <given-names>C.</given-names>
            <surname>Forza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Salvador</surname>
          </string-name>
          ,
          <article-title>Product information management for mass customization: connecting customer, front-office and back-office for fast and efficient customization</article-title>
          ,
          <source>Palgrave Macmillan</source>
          , New York,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          <string-name>
            <given-names>C.</given-names>
            <surname>Forza</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Salvador</surname>
          </string-name>
          ,
          <article-title>Product configuration and inter-firm coordination: an innovative solution from a small manufacturing enterprise</article-title>
          ,
          <source>Comput. Ind</source>
          .
          <volume>49</volume>
          (
          <year>2002</year>
          )
          <fpage>37</fpage>
          -
          <lpage>41</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          <string-name>
            <given-names>O.</given-names>
            <surname>Willner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Gosling</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Schönsleben</surname>
          </string-name>
          ,
          <article-title>Establishing a maturity model for design automation in sales-delivery processes of ETO products</article-title>
          ,
          <source>Comput. Ind</source>
          .
          <volume>82</volume>
          (
          <year>2016</year>
          )
          <fpage>57</fpage>
          -
          <lpage>68</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          <source>doi:10</source>
          .1016/j.compind.
          <year>2016</year>
          .
          <volume>05</volume>
          .003.
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          <string-name>
            <given-names>Challenges</given-names>
            <surname>Glob</surname>
          </string-name>
          .
          <source>Networked Enterp</source>
          . (
          <year>2005</year>
          )
          <fpage>436</fpage>
          -
          <lpage>450</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          <string-name>
            <given-names>A.</given-names>
            <surname>Myrodia</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Kristjansdottir</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Shafiee</surname>
          </string-name>
          , L. Hvam,
          <article-title>Product configuration system and its impact on product's life cycle complexity</article-title>
          ,
          <source>in: IEEE Int. Conf. Ind. Eng. Eng. Manag.</source>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          <source>doi:10</source>
          .1109/IEEM.
          <year>2016</year>
          .
          <volume>7797960</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          <string-name>
            <surname>L.L. Zhang,</surname>
          </string-name>
          <article-title>Product configuration: a review of the state-of-the-art and future research</article-title>
          ,
          <source>Int. J. Prod. Res</source>
          .
          <volume>52</volume>
          (
          <year>2014</year>
          )
          <fpage>6381</fpage>
          -
          <lpage>6398</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          <source>doi:10.1080/00207543</source>
          .
          <year>2014</year>
          .
          <volume>942012</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          <string-name>
            <surname>R.K. Yin</surname>
          </string-name>
          ,
          <source>Case study research: design and methods</source>
          , Sage Publications, Thousand Oaks,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          <string-name>
            <given-names>S.</given-names>
            <surname>Tornincasa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Vezzetti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Grimaldi</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. Alemanni,</surname>
          </string-name>
          <article-title>Key performance indicators for PLM benefits evaluation: The Alcatel Alenia Space case study</article-title>
          ,
          <source>Comput. Ind</source>
          .
          <volume>59</volume>
          (
          <year>2008</year>
          )
          <fpage>833</fpage>
          -
          <lpage>841</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          <source>doi:10</source>
          .1016/J.COMPIND.
          <year>2008</year>
          .
          <volume>06</volume>
          .003.
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          <string-name>
            <given-names>Aberdeen</given-names>
            <surname>Group</surname>
          </string-name>
          ,
          <source>The Configuration Management Benchmark Report</source>
          , (
          <year>2007</year>
          )
          <fpage>27</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          <string-name>
            <given-names>D.</given-names>
            <surname>Monticolo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Badin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Gomes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Bonjour</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Chamoret</surname>
          </string-name>
          ,
          <article-title>A meta-model for knowledge configuration management to support collaborative engineering</article-title>
          ,
          <source>Comput. Ind</source>
          .
          <volume>66</volume>
          (
          <year>2015</year>
          )
          <fpage>11</fpage>
          -
          <lpage>20</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          <source>doi:10</source>
          .1016/j.compind.
          <year>2014</year>
          .
          <volume>08</volume>
          .001.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>