Automated support for versioning compliance checking between workflow management and product lifecycle management (in Chinese)

With the development of enterprise informatisation, Product Lifecycle Management (PLM) systems have been widely deployed and applied in enterprises. This paper analyzes the requirement that conducting version operations on business objects as specified in process models should be compliant with the versioning policies imposed by product lifecycles. This leads to the introduction of the concept of versioning compliance, and the approach of compliance checking that we proposed in our earlier work, which comprises both syntactical compatibility and behavioural compatibility checking. The paper then focuses on the tool implementation for providing automated support to the versioning compliance checking. An empirical evaluation of the tool was also performed with industrial partners using the well-known questionnaire-based method. The evaluation and feedback from practitioners further evidence the practical significance of this research question in the PLM field and demonstrate that the proposed solution with its automated tool support possesses a high application potential.

Globally unique product identifiers - Requirements and solutions to product lifecycle management

Managing product information for product items during their whole lifetime is challenging, especially during their usage and end-of-life phases. A major challenge is how to keep a link between the product item and its associated information, which may be stored in backend systems of different organisations. In this paper, we analyse and compare three approaches for addressing this task, i.e. the EPC Network, DIALOG and WWAI. Copyright © 2006 IFAC.

Globally Unique Product Identifiers - Requirements and Solutions to Product Lifecycle Management

Managing product information for product items during their whole lifetime is challenging, especially during their usage and end-of-life phases. A major challenge is how to keep a link between the product item and its associated information that may be stored in backend systems of different organizations. This chapter analyses and compares three approaches for addressing this task-that is, the electronic product code (EPC) Network, DIALOG, and World Wide Article Information (WWAI). The EPC network has three key strengths with respect to Product lifecycle management (PLM): First, it is an internationally accepted standard that is supported by a world-wide standards body (GSI). Second, the lookup mechanism helps to insulate the data on the tag from change. Third, because it is becoming widespread and that this tag can also be used for PLM. WWAI is more technically sophisticated than the other approaches. The DIALOG approach might be the most general purpose one of the three because it places few restrictions on the format of the data on the tag. © 2006 Copyright © 2006 Elsevier Ltd. All rights reserved.

Current trends in product lifecycle management

Efficient and effective Product Lifecycle Management, as an evolution and enhancement of Product Data Management, is of strategic importance for virtually any company. Hence, it is crucial for companies to analyze and evaluate recent trends in information technology (IT) and their implications on Product Lifecycle Management. In this paper, the results of an interdisciplinary study conducted by Siemens AG, a major international technologies firm, and two universities are presented. The study identifies four current trends in IT and then evaluates their potential implications on Product Lifecycle Management. Finally, the IT trends are ranked according to their short and medium term effects on Product Lifecycle Management.

An architecture design with data model for product recovery management systems

Due to concerns about environmental protection and resource utilization, product lifecycle management for end-of-life (EOL) has received increasing attention in many industrial sectors including manufacturing, maintenance/repair, and recycling/refurbishing of the product. To support these functions, crucial issues are studied to realize a product recovery management system (PRMS), including: (1) an architecture design for EOL services, such as remanufacturing and recycling; (2) a product data model required for EOL activity based on international standards; and (3) an infrastructure for information acquisition and mapping to product lifecycle information. The presented works are illustrated via a realistic scenario. © 2008 Elsevier B.V. All rights reserved.

Controlled flexibility and lifecycle management of business processes through extensibility

Vendors provide reference process models as consolidated, off-the-shelf solutions to capture best practices in a given industry domain. Customers can then adapt these models to suit their specific requirements. Traditional process flexibility approaches facilitate this operation, but do not fully address it as they do not sufficiently take controlled change guided by vendors' reference models into account. This tension between the customer's freedom of adapting reference models, and the ability to incorporate with relatively low effort vendor-initiated reference model changes, thus needs to be carefully balanced. This paper introduces process extensibility as a new paradigm for customizing reference processes and managing their evolution over time. Process extensibility mandates a clear recognition of the different responsibilities and interests of reference model vendors and consumers, and is concerned with keeping the effort of customer-side reference model adaptations low while allowing sufficient room for model change.

Business and software service lifecycle management

Although the service-oriented paradigm has been well established in the technical domain for quite some time now, service governance is still considered a research gap. To ensure adequate governance, there is a necessity to manage services as first-class assets throughout the lifecycle. Now that the concept of ser-vice-orientation is also increasingly applied on the business level to structure an organisation’s capabili-ties, the problem has become an even bigger chal-lenge. This paper presents a generic business and software service lifecycle and aligns it with the com-mon management layers in organisations. Using ser-vice analysis as an example, it moreover illustrates how activities in the service lifecycle may vary on lower levels of granularity depending on the focus on business or software services.

Co-creation in business service lifecycle management

Co-creation between customers and providers has recently gained more attention by business service providers as a promising endeavour. The different perspectives of co-creation - innovation, sourcing and marketing - are well deployed. From a provider’s point of view, the question of how to manage business services with respect to co-creation is vitally important. However, service engineering and service lifecycle management typically take a mostly internal, closed-loop approach, although a logical implication of acknowledging the value co-creation perspective on “service” would be to leverage customer and other stakeholder competences to the full extent. This paper aims at reconciling the perspectives of co-creation and makes a contribution by analysing where and how co-creation can be effectively utilised throughout the various stages of a generic business service lifecycle. The result will be a framework guiding companies in using co-creation when managing their business services.

Applying social technology to Business Process Lifecycle Management

In recent years social technologies such as wikis, blogs or microblogging have seen an exponential growth in the uptake of their user base making this type of technology one of the most significant networking and knowledge sharing platforms for potentially hundreds of millions of users. However, the adoption of these technologies has been so far mostly for private purposes. First attempts have been made to embed features of social technologies in the corporate IT landscape, and Business Process Management is no exception. This paper aims to consolidate the opportunities for integrating social technologies into the different stages of the business process lifecycle. Thus, it contributes to a conceptualization of this fast growing domain, and can help to categorize academic and corporate development activities.

Beyond MOF constraints : multiple constraint set metamodelling for lifecycle management

The management of models over time in many domains requires different constraints to apply to some parts of the model as it evolves. Using EMF and its meta-language Ecore, the development of model management code and tools usually relies on the meta- model having some constraints, such as attribute and reference cardinalities and changeability, set in the least constrained way that any model user will require. Stronger versions of these constraints can then be enforced in code, or by attaching additional constraint expressions, and their evaluations engines, to the generated model code. We propose a mechanism that allows for variations to the constraining meta-attributes of metamodels, to allow enforcement of different constraints at different lifecycle stages of a model. We then discuss the implementation choices within EMF to support the validation of a state-specific metamodel on model graphs when changing states, as well as the enforcement of state-specific constraints when executing model change operations.