Model-driven Enterprise Systems Configuration

Enterprise Systems potentially lead to significant efficiency gains but require a well-conducted configuration process. A promising idea to manage and simplify the configuration process is based on the premise of using reference models for this task. Our paper continues along this idea and delivers a two-fold contribution: first, we present a generic process for the task of model-driven Enterprise Systems configuration including the steps of (a) Specification of configurable reference models, (b) Configuration of configurable reference models, (c) Transformation of configured reference models to regular build time models, (d) Deployment of the generated build time models, (e) Controlling of implementation models to provide input to the configuration, and (f) Consolidation of implementation models to provide input to reference model specification. We discuss inputs and outputs as well as the involvement of different roles and validation mechanisms. Second, we present an instantiation case of this generic process for Enterprise Systems configuration based on Configurable EPCs

On the User Perception of Configurable Reference Process Models - Initial Insights

Enterprise Systems potentially lead to significant efficiency gains but require a well-conducted configuration process. A configurable reference modelling language based on the widely used EPC notation, which can be used to specify Configurable EPCs (C-EPCs), has been developed to support the task of Enterprise Systems configuration. This paper presents a laboratory experiment on C-EPCs and discusses empirical data on the comparison of C-EPCs to regular EPCs. Using the Method Adoption Model we report on modeller’s perceptions as to the usefulness and ease of use of C-EPCs, concluding that C-EPCs provide sufficient yet improvable conceptual support towards reference model configuration

Improving cross-functional communication about product architecture

Product architecture decisions, such as product modularity, component commonality, and design reuse, are important for balancing costs, responsiveness, quality, and other important business objectives. Firms are challenged with complex tradeoffs between competing design priorities, face the need to facilitate communication between functional silos, and to learn from past experiences. In this paper we present a qualitative approach for systematically evaluating the product architecture of an existing product or product family, linking the original architecture objectives and actual experiences. The intended contribution of our research is to present a framework that brings together a diverse set of product architecture-related decisions that are relevant from a business point of view (and not from a technical point of view) and a set of business performance elements. This framework can be used in workshop that improves cross-functional communication about the product architecture of an existing product family, and this results in practical improvement actions for future architecture design projects. Initial experiences with this approach have been obtained in pilots with Philips domestic appliances & personal care, and Philips consumer electronics

Using a Work System Perspective to Expand BPM Research Use Cases

Business process management (BPM) has developed as a research field primarily situated in the computer and information systems sciences. Recently, van der Aalst (2013) analyzed the results of these research efforts and identified a set of research topics in the form of a series of BPM research use cases. Those BPM research use cases emphasize technological and computational challenges and solutions. Ideally, however, BPM research should also address managerial and organizational challenges that the existing technically oriented research use cases do not fully reflect. We propose expanding the scope and impact of BPM research by drawing on work system theory (WST) to identify new BPM research use cases and directions. After comparing a WST perspective on basic BPM topics with the technically oriented BPM perspective expressed in van der Aalst (2013), we present new research topics that extend the technically oriented BPM research use cases in van der Aalst (2013). We also present new research directions that go beyond those use cases. Taken together, the extensions of the existing research use cases and the new use cases lead to a more balanced BPM research agenda that more fully blends technical and managerial challenges

Using a Work System Perspective to Expand BPM Use Cases for Research

Business Process Management (BPM) has developed as a research field centered within the computer and information systems sciences – but also touching other fields as well. Recently, van der Aalst (2013) analyzed the results of some of these research efforts and identified a set of research topics in the form of a series of BPM use cases that primarily emphasize technological and computational challenges and solutions in BPM academia. Ideally, however, BPM should also address managerial and organizational challenges that are not fully reflected in the existing use cases identified by van der Aalst (2013). We propose drawing on work system theory (WST) to expand van der Aalst’s use cases and to identify additional BPM use cases and new research directions. After comparing a WST perspective on basic BPM topics with the BPM perspective expressed in van der Aalst (2013), we present new research topics that extend existing BPM use cases. We also present new research directions that go beyond those use cases. Taken together, the extensions of the existing use cases and the new use cases lead to a more balanced BPM research agenda that blends technical and managerial challenges more fully

Modeling the role variability in the MAP process model

International audienceBusiness process modeling is a valuable technique helping organizations to specify their processes, to analyze their structure and to improve their performance. Conventional process modeling techniques are proven to be inefficient while dealing with non-repetitive, knowledge-intensive processes such as Case Management processes. In this work we use the MAP notation to model a Mortgage Approval Process as defined in Banking. To increase the navigability and practical value of map models, we extend the MAP notation with the concepts of Roles, Relations between roles, and Role Configuration Rules

Product portfolio management as part of product lifecycle management for configure-to-order products

Abstract. Product portfolio management (PPM) research has mainly focused on PPM practices by covering the early stage of the lifecycle and not the whole lifecycle of the product. In addition, lifecycle management has been applied to individual products rather than the entire product portfolio. In this thesis, PPM research focuses on both all lifecycle phases and the entire product portfolio rather than only individual products. The research aims to study how configurable products should be arranged in the case company’s future Product lifecycle management (PLM) system. The case company of the thesis is Valmet Flow Control Oy, which delivers flow control technologies and services for different industries. The current Product data management (PDM) system in use is no longer supported and it is seen that the PDM system does not support the company’s needs anymore. Therefore, a new PLM system is needed to cover future demands in the case company. The product portfolio is composed of a product series, which refers to a certain product type and model. This thesis focuses on configure-to-order (CTO) products, which are configured based on customers’ needs with pre-defined specifications. This thesis proposes, how to present product series level object in the PLM system and what kind of product data it contains. The main result of the research is the created product series object in the future PLM system and how to manage product series through their lifecycle in one centralized system with all internal stakeholders. The availability, traceability, and data use are also essential results. Appropriate exploitation of data allows to reveal the most critical information, enabling the management of the whole product portfolio from one PLM system. This kind of procedure creates transparency in the product portfolio.Tuoteportfolion hallinta osana tuotteen elinkaaren hallintaa tilauksesta määritettäville tuotteille. Tiivistelmä. Tuoteportfolion hallinnan (PPM) tutkimukset ovat pääasiassa keskittyneet PPM:n käytäntöihin elinkaaren alkuvaiheessa eikä tuotteen koko elinkaaren hallintaan (PLM). Lisäksi PLM:ää on sovellettu yksittäisten tuotteiden tasolla eikä niinkään koko tuoteportfolion tasolla. Tässä diplomityössä PPM:n tutkimus keskittyy sekä koko tuotteen elinkaaren vaiheisiin että koko tuoteportfolioon yksittäisten tuotteiden sijasta. Tutkimuksen tarkoituksena on tutkia kuinka konfiguroitavat tuotteet pitäisi järjestellä tulevaan PLM-järjestelmään tapausyrityksessä. Diplomityön tapausyrityksenä on Valmet Flow Control Oy, joka toimittaa virtauksensäätöratkaisuja ja -palveluja eri teollisuudenaloille. Nykyistä käytössä olevaa tuotetiedonhallinta järjestelmää (PDM) ei enää ylläpidetä eikä PDM-järjestelmä tue yrityksen tarpeita enää. Tästä johtuen PLM-järjestelmää tarvitaan, jotta voidaan kattaa tulevaisuuden tarpeet tapausyrityksessä. Tuoteportfolio koostuu tuotesarjoista, joilla viitataan tiettyyn tuotetyyppiin ja malliin. Tämä diplomityö keskittyy tilauksesta määritettäviin tuotteisiin eli konfiguroitaviin tuotteisiin, jossa tuote konfiguroidaan asiakkaan tarpeiden mukaisesti ennalta määrättyjen spesifikaatioiden avulla. Tässä työssä esitetään kuinka tuotesarjatason objekti kuvataan PLM-järjestelmässä ja mitä tuotetietoja sille tarvitaan. Tutkimuken päätuloksena luodaan tuotesarjaobjekti tulevaisuuden PLM-järjestelmään ja tehdään kehitysehdotus siitä, kuinka tuotesarjoja tulisi hallita niiden koko elinkaaren ajan yhdessä järjestelmässä, ja kaikkien sisäisten sidosryhmien kanssa. Tiedon saatavuus, jäljitettävyys sekä hyödyntäminen ovat myös pääasiallisia työn tuloksia. Tiedon oikeanlainen hyödyntäminen mahdollistaa kriittisimmän tiedon esittämisen ja siten mahdollistaa koko tuoteportfolion hallinnan yhdestä PLM-järjestelmästä