وب سرویس گرای سیستم مدیریت جریان کار برای یکپارچه سازی مهندسی تولید دیجیتال
|کد مقاله||سال انتشار||مقاله انگلیسی||ترجمه فارسی||تعداد کلمات|
|21863||2011||6 صفحه PDF||سفارش دهید||3241 کلمه|
Publisher : Elsevier - Science Direct (الزویر - ساینس دایرکت)
Journal : CIRP Journal of Manufacturing Science and Technology, Volume 4, Issue 3, 2011, Pages 290–295
Digital production engineering is a complex procedure, since distributed engineering teams, using heterogeneous IT tools, should be able to collaborate in order to design and implement a production system. This work presents the concept and its implementation of a workflow system for collaborative computer-aided production engineering. The workflow system supports the execution of production engineering activities in the Extended Enterprise (EE) and is built on the basis of web services and the BPEL (Business Process Execution Language). It also manages the electromechanical data exchange, using XML that conforms to the AutomationML format. An application of the tool, developed for an assembly engineering project in the automotive industry, is being presented.
Shorter product and production lifecycles, an increased number of product variants and the unrestrained global competition have led many industrial companies to improve their development process from product designing up to its production. Production engineering involves the design, control and continuous improvement of manufacturing systems in order for customers to be provided with high-quality products, in a timely and cost efficient manner. This work focuses in particular on the initial design and engineering of a production system. In this context, a production engineering project includes the mapping of the manufacturing system's variables such as the number and type of machines, the layout, the process parameters and the control logic to product parameters such as the bill of materials and the product's geometry in order to meet performance requirements such as production cost and rate, quality and flexibility . The production engineering projects are usually multidisciplinary and inter-organizational in nature. The current situation, in digital production engineering, is characterized by a large number of different IT tools, based both on PCs and on workstation applications. Integrated production engineering could be operated within the entire network of collaborating enterprises, defined as the Extended Enterprise (EE), with a long term agreement involving suppliers up to end-use customers. Typical examples of production engineering projects in the automotive and aerospace industries cover the entire process from rough product geometry to the ramp-up and start of production. Internet may provide the infrastructure by which information can become simultaneously available to all those involved in production engineering, such as designers, planners, production managers, and so forth. However, there are problems with the efficient integration of the production engineering activities in the EE: • The generation and the execution of a production engineering project may both take a long time and involve several organizations, with different roles and competencies, dispersed in different geographical locations. • Monitoring and improving the production engineering project plans may be complex, difficult to automate and manage changes. • The commercial Computer-aided Manufacturing/Engineering (CAM/CAE) systems, used by process designers and planners, may vary. The internet-based manufacturing needs to overcome this heterogeneous software environment. • Data inconsistency and data redundancy. These problems can be tackled by distributed, adaptable, open and intelligent process planning systems within a collaborative environment. 1.1. Collaborative production engineering In the field of production engineering, the literature presents different approaches in terms of functionalities, communication protocols, programming languages and data models. The following review focuses on systems that use technologies, such as web-services and workflow definition/management. Siller et al.  proposed a workflow model defined in the BPMN (Business Process Modeling Notation) and implemented it within a commercial PLM (Product Lifecycle Management) system for a collaborative process planning environment. They demonstrated the way that the workflow approach could be successfully applied for the integration of PLM by CAPP and CAD/CAM tools. However, the workflow is not extended to include equipment automation aspects, which add additional requirements to the interoperability ones within the extended enterprise and in their approach, there is not any service oriented architecture framework, integrated into the workflow engine, to support collaborative data storage/retrieval and communication issues. Kuk et al.  focus on the use of a service-oriented-architecture (SOA), namely web services, intelligent software agents and a workflow engine to support integrated engineering activities. The pilot case execution has indicated a significant man-hours saving, due to the coordination of engineering activities and automation. Nevertheless, their approach was to use a proprietary implementation to bind the workflow with the SOA architecture and not some standard approach, such as the BPEL (Business Process Execution Language). Other approaches that demonstrate the use of an agent based framework for the integration of heterogeneous software tools, even non-engineering application fields, can be found in the literature (e.g.  and ). In Butala and Ueda  the implementation of a multi-agent system in production engineering is discussed, aiming at an emergent behavior and an adequate structural and organizational model in the real-world system. Communication protocols can be autonomously generated, refined or adapted by the agents. This approach uses basic concepts of machine learning for integrated conflict management and open adaptive communication. By this, a highly complex communication structure emerges during the runtime. Jagdev and Wortmann  discussed the complexity of product data and models being integrated into the planning phase of the production facilities. The main issue is that the production partners are globally distributed, resulting in sub-models that are not possible to be integrated into a complete model. Therefore, a consistent digital representation of the production facility is improbable today. The authors have proposed an XML and a web-services based approach for managing the production engineering; however, it is applied to a rather simplistic scenario without being able to support the usage of heterogeneous tools in the process, thus requiring further enhancements in order for the complexity of the production engineering process to be managed. Kiefer et al.  present a framework for digital validation of production and they employ AutomationML for data interface reduction, because it wraps and integrates already standardized sub-standards for the different data types. However, it is mentioned that AutomationML is not fully supported by a typical production engineering software and it should be further disseminated as a standard of a different production planning software. The production engineering projects are typically multidisciplinary and inter-organizational. Although the backbone of engineering activities is typically a PLM, the current situation in digital production engineering is characterized by a large number of different IT tools, based both on PCs and main frame applications . There are tools in support of mechanical design operations, process design and simulation, electrical engineering, OLP (Offline Robots Programming) as well as PLC coding and automation. In a geographically dispersed production engineering environment, web-based tools for collaboration are highly relevant but they are not a panacea. They should be complemented by a framework that would enable the integration and coordination of engineering activities (product development, process planning, and commissioning) and the exchange of data among entities (Original Equipment Manufacturers – OEM, product designers, engineering service providers, system main integrator). In the case of an EE, different tier engineers collaborate within the common communication infrastructure, provided by the OEM. The engineering tasks are usually accomplished in the OEM, the main integrator for the complete system, and probably any additional engineering service providers. During a production engineering project, the main objective is that a sequence of the manufacturing and assembly processes be established and used in order for the raw materials to be converted from their initial form into the final products. In terms of the underlined data, involved in this activity, the objective is to link product, process, and resource data with each other by defining the type of component (product) that is to be manufactured with the use of production steps (process) on specific manufacturing equipment (resource). The aim of this paper is to describe a web-based workflow management approach and the corresponding tool that has been developed in order to support the coordination and integration of production engineering activities using different digital tools. The design and development of the proposed approach tries to cover holistically all the problems during collaborative production engineering.
نتیجه گیری انگلیسی
The paper dealt with the concept and its implementation of a web-based workflow management system for integrated production engineering along with a system that manages production engineering data, described in AutomationML. Modern information technologies were utilized for the implementation of the proposed concept. The potential application of this system, in an automotive scenario, has been presented. The workflow of a production engineering project may be easily configured within the BPEL Engine layer and deployed as a set of coordinated web services. The engineering data become available to the appropriate cooperating partners in a native or an AutomationML open format. Unlike many traditional PDM and PLM systems, the AutomationML Server approach does not need to be configured in-depth in order to match the current production engineering procedures. However, effort is required for interfacing with the legacy systems but this is expected to be achieved in a shorter time, due to the openness and the flexibility provided by the web-services API. Future work needs to apply the system and evaluate it in a more detailed application scenario. The main evaluation benchmark will be the saving of man-hours, due to an engineering activities coordination and automation through the system. The BPEL based services oriented workflow support maybe easily configured at the initial setup phase so as to include different actors and their interdependencies. However, changes that may occur in the enterprise workflow, during the lifetime of a production engineering project, may also require others in the workflow process definition or even a change in the workflow engine, both of which are cost intensive solutions. In order for such dynamic changes to be addressed, a mechanism on top of the workflow engine is required for the handling of events that the original workflow definition does not. The incorporation of such a mechanism will be the topic of future research and development. Moreover, the AutomationML is a relatively new initiative and thus, it is lacking in supporting tools that convert different data formats from and into this open format. This practically limits its use to specific data exchange occasions. On the other hand, it is expected that due to industry's support and interest in this initiative, individual stakeholders will develop and supply these data conversion tools.