Agile Manufacturing Data Management

2009 ◽  
Vol 407-408 ◽  
pp. 189-193
Author(s):  
Li Hong Qiao ◽  
Wei Liu

An agile data service framework was proposed in the paper to meet the requirement of agile manufacturing data management in product lifecycle management. The framework was comprised of four layers: core object and ontology layer, meta-data and meta-mode layer, service component layer and implementation layer. The realization of agile manufacturing data management was investigated through the analysis of the unified manufacturing data modeling and the implementation based on services. The descriptive structure and the main content of the manufacturing data model was given. The architecture of the manufacturing data management system based on services was addressed to conduct service implementation of the framework. The proposed approach of agile data services brought forward a new feasible solution to agile data management throughout product lifecycle.

Computers ◽  
2021 ◽  
Vol 10 (7) ◽  
pp. 84
Author(s):  
Andreas Deuter ◽  
Sebastian Imort

Product lifecycle management (PLM) as a holistic process encompasses the idea generation for a product, its conception, and its production, as well as its operating phase. Numerous tools and data models are used throughout this process. In recent years, industry and academia have developed integration concepts to realize efficient PLM across all domains and phases. However, the solutions available in practice need specific interfaces and tend to be vendor dependent. The Asset Administration Shell (AAS) aims to be a standardized digital representation of an asset (e.g., a product). In accordance with its objective, it has the potential to integrate all data generated during the PLM process into one data model and to provide a universally valid interface for all PLM phases. However, to date, there is no holistic concept that demonstrates this potential. The goal of this research work is to develop and validate such an AAS-based concept. This article demonstrates the application of the AAS in an order-controlled production process, including the semi-automatic generation of PLM-related AAS data. Furthermore, it discusses the potential of the AAS as a standard interface providing a smooth data integration throughout the PLM process.


2015 ◽  
Vol 752-753 ◽  
pp. 1283-1287
Author(s):  
Sari Laitinen ◽  
Merja Huhtala ◽  
Mika Lohtander ◽  
Tuomo Kässi ◽  
Juha Varis

Changes taking place in project-based manufacturing emphasize the importance of agile manufacturing, product knowledge management and product lifecycle information. The paper describes dependencies between product definition and production strategy covering also other potential areas of research i.e. growth of industrial service business and development of manufacturing and supply networks. As an outcome it can be argued that more research is needed to align product lifecycle management in project-based manufacturing, as well as to cover the evolving information needs of internal and external stakeholders. Due to the increase of industrial services, also services should be included as a part of product definition; the extended product description introduces a new set of requirements that need to be taken into account as a part of product and production strategy definition.


Author(s):  
Xun Xu

Companies that have been practicing CAD, CAPP, CAM, and CNC integration have now realized that there is a need to operate in a much broader scope with wider boundaries and more functionality. To foster innovation in a product development lifecycle, change in the early stage is good, and, in fact, should be encouraged. The more iteration a product design can experience at this stage when change is inexpensive, the lower cost our final product will become. At a later stage when hardware set-up is committed against a design, change becomes expensive and should be discouraged. Therefore, there is a need for an effective way of managing product-related information as well as the product development action flow, which captures actions that need to be done, have been done, and what other parts are affected. Engineers that subscribe to a portion of a design also need to be working with other collaborators and then automatically be notified when changes occur. This leads to increased implementation of Product Data Management (PDM) and Product Lifecycle Management (PLM). PDM systems are used to control information, files, documents, and work processes required to design, build, support, distribute, and maintain products. Using PDM, people can contribute at the early stages of product design and development. In addition, PDM can be seen as an integration tool connecting many different areas, which ensures that the right information is available to the right person at the right time and in the right form throughout the enterprise. In this way, PDM improves communication and cooperation be tween diverse groups in an organization, and between organizations and clients (Peltonen, Pitkanen & Sulonen, 1996, Liu & Xu, 2001). PDM is strongly rooted in the world of CAD, CAPP, CAM, and CNC in a more specific sense as well as in the world of engineering and design in a more general sense. In recent years, more focus has also been on the improvement of the entire product lifecycles. The major concern here is time-to-market, as it reflects the competitiveness of a company. In response to the new area of focus, new generation PDM systems are developed to support the entire product lifecycle; from the initial concept to the finishing product. This has subsequently led to the birth to PLM systems. From the information context, PLM should cater for the management of the information throughout the lifecycle of a product, including multiple domain views, different business processes scattered across enterprises and different representations of a multitude of native product-, resource- and process-models (Stark, 2004, Rosén, 2006). This chapter starts with introduction to and discussions about product data management systems. Topics covered include PDM’s capabilities, its benefits, Web-based PDM and PDM standardization. The concept of integrated and extended PDM is also introduced. This is followed by discussions on product lifecycle management, for example definitions of PLM, its solution model, benefits, and implementation are among the topics covered. Like PDM, issues regarding PLM standardisation are also addressed. Share-A-space™ is a practical case of PLM. The core features and its architecture are discussed. Toward the end, the concept and some of the techniques of “grand” integration are introduced.


2004 ◽  
Vol 4 (4) ◽  
pp. 305-315 ◽  
Author(s):  
Duc T. Pham ◽  
Stefan S. Dimov , ◽  
Rossitza M. Setchi , ◽  
Bernard Peat , ◽  
Anthony J. Soroka , ◽  
...  

This paper shows how product lifecycle information can be utilized to assist people engaged in product lifecycle tasks, in particular those concerned with product support. A progression of product data management methods based on knowledge engineering techniques is presented to allow the creation and delivery of effective, personalized performance support information. The product data management methods discussed include semantic hypermedia authoring, automated construction of product documentation, automated diagnostic module construction, and adaptive product support generation. These methods are utilized to improve the performance of product lifecycle actors, while reducing the time, knowledge, and input required from them, through increased task support and automation.


2021 ◽  
Author(s):  
Muhammad Anwary

This thesis presents a complete set of user requirements and high-level architecture for [a] product lifecycle management (PLM) system for small and medium-sized enterprises (SMEs). Engineering activities such as engineering change management (ECM) and product data management (PDM) are emphasized. The system is designed to be developed in [an] open source environment. Therefore the system is called Open Product Lifecycle Management (OPLM) system. The thesis begins with a presentation of the motivation for the work and description of products and literature in the areas of PLM, SME and open source. An industry survey is conducted to elicit requirements of OPLM. Engineering change management (ECM) process is described and a modified framework for ECM in OPLM is presented. The proposed model is expected to make ECM faster, reusable and accurate. Four OPLM subsystems, namely, product data management, engineering change management, process management and business intelligence are defined. For each of the subsystems, subsystem components are identified and defined.


2011 ◽  
Vol 55-57 ◽  
pp. 37-40
Author(s):  
Su Mei Zhang

The purpose of this study was to provide a unified modelling framework of Product Lifecycle Management (PLM). Firstly, the paper presented a Total Object Unified Model(TOUM) method which was used to abstract the concepts of manufacturing domain, format the meta-model of manufacturing data, construct the data model of PLM; Secondly, this paper presented three kinds of architectures based on TOUM to unify and simplify model, which are development architecture, deployment architecture and application architecture. At last, a model instance applied in a PLM product-CAXA V5 was shown based on the method of TOUM to confirm the validity of this method. This paper has provided a reference operation model and method for Product Lifecycle Management.


2021 ◽  
Author(s):  
Muhammad Anwary

This thesis presents a complete set of user requirements and high-level architecture for [a] product lifecycle management (PLM) system for small and medium-sized enterprises (SMEs). Engineering activities such as engineering change management (ECM) and product data management (PDM) are emphasized. The system is designed to be developed in [an] open source environment. Therefore the system is called Open Product Lifecycle Management (OPLM) system. The thesis begins with a presentation of the motivation for the work and description of products and literature in the areas of PLM, SME and open source. An industry survey is conducted to elicit requirements of OPLM. Engineering change management (ECM) process is described and a modified framework for ECM in OPLM is presented. The proposed model is expected to make ECM faster, reusable and accurate. Four OPLM subsystems, namely, product data management, engineering change management, process management and business intelligence are defined. For each of the subsystems, subsystem components are identified and defined.


Sign in / Sign up

Export Citation Format

Share Document