Variety Management in Assemble-to-Order Supply Chains

Assemble-to-order refers to a supply chain strategy in which products are not assembled until customer order arrives. It is based on the so-called form postponement that is to hold components at a generic form and to delay the point of product differentiation. The performance of an assem-ble-to-order supply chain depends on two main dimensions, which are responsiveness and achievement level of scale economies. Responsiveness refers to the capability of fulfilling customer requirements in a fast-paced manner, whereas the achievement of scale economies reflects the degree of operations efficiency. Assemble-to-order supply chains induce high product variety, which has adverse effects on performance. We use demand volumes as a proxy for scale economies and lead times as a proxy for responsiveness. A matrix that consists of both dimensions can be defined, in which we distinguish between short/long lead times and low/high demand volumes. This matrix is called performance matrix. On the other hand, the consequence that results from product variety is a high demand variability of end products, which also affects the demand variability of components. An analysis of component demand variability enables one to identify the components with low/high demand variability. These components can further be classified into supplied and in-house made components. Thus, a second matrix (called component matrix) with two dimensions, namely variability (low/high) and supply source (in-house/supplier) can be defined. Due to the supply source dimension in the component matrix, the supply chain perspective is also taken into ac-count. The combination of both matrixes into a single one provides the performance/component matrix for assemble-to-order supply chains. To use the final matrix, it is necessary to compute lead times, demand volumes and demand variability of the supplied and in-house made components. By plotting the components in the matrix, one can determine the problems induced by variety. In order to improve the performance of the assemble-to-order supply chain, the implementation of variety management strategies is necessary. The identified strategies are: commonality, component families, modularity, and platforms. Based on the performance/component matrix, we discuss how these strategies or a combination of them can contribute to derive recommendations that aim to alleviate variety impacts on the as-semble-to-order supply chain.Assemble-to-order; Supply Chain Management; Variety Management

Knowing A Few Rules Doesn’t Mean You Can Play the Game : The Limits of “Best Practice” in Enterprise Systems.

We examine the common claim that "best practices" are encompassed and represented in Enterprise Systems (ES). We suggest that an ES can at best only represent the ostensive and not the performative elements of work tasks. Thus, representation of best practice in an ES does not take practical action into account. This has two important implications. First, ostensive abstractions of best practice in an ES are a sparse and superficial representation of a "good" business process, at a specific moment in time. Second, the practical understanding required for performance is often ignored in the ostensive representation of best practice in the implementation of an ES. This constrains user and business adaptability. Inflexible coding of ostensive business tasks furthermore leads to rigidity where flexibility should be sought, to keep on top of the competition. Implications and directions for further research are discussed

Development of an Extended Product Lifecycle Management through Service Oriented Architecture.

Organised by: Cranfield UniversityThe aim of this work is to define new business opportunities through the concept of Extended Product Lifecycle Management (ExtPLM), analysing its potential implementation within a Service Oriented Architecture. ExtPLM merges the concepts of Extended Product, Avatar and PLM. It aims at allowing a closer interaction between enterprises and their customers, who are integrated in all phases of the life cycle, creating new technical functionalities and services, improving both the practical (e.g. improving usage, improving safety, allowing predictive maintenance) and the emotional side (e.g. extreme customization) of the product.Mori Seiki – The Machine Tool Company; BAE Systems; S4T – Support Service Solutions: Strategy and Transitio

Multi-Dimensional Customization Modelling Based On Metagraph For Saas Multi-Tenant Applications

Software as a Service (SaaS) is a new software delivery model in which pre-built applications are delivered to customers as a service. SaaS providers aim to attract a large number of tenants (users) with minimal system modifications to meet economics of scale. To achieve this aim, SaaS applications have to be customizable to meet requirements of each tenant. However, due to the rapid growing of the SaaS, SaaS applications could have thousands of tenants with a huge number of ways to customize applications. Modularizing such customizations still is a highly complex task. Additionally, due to the big variation of requirements for tenants, no single customization model is appropriate for all tenants. In this paper, we propose a multi-dimensional customization model based on metagraph. The proposed mode addresses the modelling variability among tenants, describes customizations and their relationships, and guarantees the correctness of SaaS customizations made by tenants.Comment: 10 pages, 8 figure

A Generic method for assembling software product line components

Software product lines (SPL) facilitate the industrialization of software development. The main goal is to create a set of reusable software components for the rapid production of a software systems family. Many authors propose different approaches to implement and assemble the reusable components of an SPL. However, the construction and assembly of these components continue to be a complex and time-consuming process. This thesis analyzes the advantages and disadvantages of the current approaches to implement and assemble the reusable components of an SPL. Taking advantage of these elements and with the goal of developing a generic method (which can be applied to several software components developed in different software languages), we develop Fragment-oriented programming (FragOP), a framework to design, implement and reuse SPL domain components. FragOP is based on: (i) domain components, (ii) domain files, (iii) fragmentation points, (iv) fragments, (v) customization points, and (vi) customization files. FragOP was implemented in an open-source tool called VariaMos, and we also carried out three evaluations: (i) we created a clothing stores SPL, derived five different products, and discussed the results. (ii) We developed a discussion about the comparison between FragOP and other approaches. And (iii) we designed and executed a usability test of VariaMos to support the FragOP approach. The results show preliminary evidence that the use of FragOP reduces the manual intervention when assembling SPL domain components and it can be used as a generic method for assembling assets and SPL components developed in different software languages.Las líneas de productos de software (LPS) promueven la industrialización del desarrollo de software mediante la definición y ensamblaje de componentes reutilizables de software. Actualmente existen diferentes propuestas para implementar y ensamblar estos componentes. Sin embargo, su construcción y ensamblaje continúa siendo un proceso complejo y que requiere mucho tiempo. Esta tesis analiza las ventajas y desventajas de las diferentes estrategias actuales para implementación y ensamblaje de componentes de LPS. Con base en esto y con el objetivo de desarrollar un método genérico (el cual se pueda aplicar a múltiples componentes de software desarrollados en diferentes lenguajes), esta tesis desarrolla la programación orientada a fragmentos (FragOP), la cual define un marco de trabajo para diseñar, implementar y reutilizar componentes de dominio de LPS. FragOP se basa en: (i) componentes de dominio, (ii) archivos de dominio, (iii) puntos de fragmentación, (iv) fragmentos, (v) puntos de personalización, y (vi) archivos de personalización. Además, se realizó una implementación de FragOP en una herramienta llamada VariaMos, y se llevaron a cabo tres evaluaciones: (i) se creó una LPS de tiendas de ropa, se derivaron cinco productos y se discutieron los resultados. (ii) Se realizó una discusión acerca de la comparación de FragOP y otras propuestas actuales. Y (iii) se diseñó una prueba de usabilidad acerca del soporte de VariaMos para FragOP. Los resultados muestran evidencia preliminar de que el uso de FragOP reduce la intervención manual cuando se ensamblan componentes, y que FragOP puede usarse como un método genérico para el ensamblaje de componentes.Doctorad