• Journal of the Computational Structural Engineering Institute of Korea
• /
• v.21 no.6
• /
• pp.543-553
• /
• 2008

Shipbuilding is a kind of ETO(Engineering To Order) industry which designs and produces a product in accordance to various requirement of customers, rules and regulations. Recently, the number of ordered ships has been increased by up to two or three times in each domestic shipyards. Most shipyards have been adopted 3D ship CAD, ERP(Enterprise Resource Planning) and APS(Advanced Planning System) to get an efficient product development and manufacturing system. However, not only the effective operation of 3D ship CAD, ERP and APS but also the production efficiency can be achieved only if product information management which can manages the product data is implemented in an integrated environment. Present study has suggested a systematic approach to implement a PLM system to manage the product data in early design shipbuilding. Also, a prototype of PLM is implemented to manage the product data in a basic ship-design. In the prototype system, a product structure and architecture of PLM is considered.

• Korean Journal of Computational Design and Engineering
• /
• v.18 no.4
• /
• pp.267-274
• /
• 2013

This study focuses on the data schema and data content, which includes maintenance data, data structures and illustration data relevant with the maintenance process of ship and offshore structures. Product lifecycle management (PLM) is expected to encompass all the product data generated for the operation and maintenance information as well as the design and production. This paper introduces a data exchange schema in PLM of ship and offshore, serving as the basis for the role of standards required by the middle-of-life PLM. Also this paper identifies a typology of standards relevant to PLM that addresses the schema of evolving standards and identifies a XML schema supporting the exchange of data related with maintenance operations. Technical document based on standards in accordance with S1000D and Shipdex is explained. A case study illustrating the use of standard data exchange and technical document is presented.

• Journal of the Korea Society of Computer and Information
• /
• v.22 no.12
• /
• pp.131-136
• /
• 2017

PLM(Product Lifecycle Management) is an information management system that can integrate data, processes, business systems and human resources throughout the enterprise. BOM(Bills Of Material) is key data for designing, purchasing materials, manufacturing planning and management, which is basic for product development throughout the product life cycle. In this paper, we propose the efficient system to increase the data loading speed and the processing speed when using such large BOM data. We present the performance and usability of IMDG (In Memory Data Grid) for data processing when loading large amounts of data. In the UI, using the pure web grid of JavaScript instead of the existing data loading method can be improve performance of data managing.

• Korean Journal of Computational Design and Engineering
• /
• v.15 no.5
• /
• pp.362-374
• /
• 2010

Product Lifecycle Management (PLM) is an integrated business approach to manage the creation and distribution of product information throughout the product development process. From the product perspective, PLM encompasses a holistic approach to product development and product information management. It supports the integrated product information in conjunction with the efficient product structures and BOM (Bill Of Material), user interfaces, proper functions, design processes and enterprise integration. Therefore, PLM should not only satisfy required functions as an enterprise software but also offer a systematic method for the efficient application from the initial stage of its development. Recently, many shipyards have been considering the PLM as a strategic solution to get the efficient management of product information such as 3-D models, BOM, drawings, documents, and the other product data. Though many studies on PLM are performed, most of them are performed in a function-based approach adequate for mass productive assembly industries. It could not help having limitations on applying the proper PLM system to the shipbuilding business since the requirements of shipbuilding PLM are too diverse and huge to design the architecture. This study presents the PLM framework which effectively reflects the diverse requirements of shipbuilding PLM. In order to get the macroscopic architecture of shipbuilding PLM, authors suggest the four-tier architecture model which considers the various requirements collected from shipyards. Entities of ship design data are modeled BOM in terms of product structure and hierarchical class diagram. Applicable functions of shipbuilding PLM are also investigated by analysis of issues of ship design. Finally, by reflecting the design process of shipbuilding, To-Be ship design procedure cooperated with the suggested PLM framework has been summarized.

• CDE review
• /
• v.18 no.3
• /
• pp.14-16
• /
• 2012

• Korean Journal of Computational Design and Engineering
• /
• v.11 no.1
• /
• pp.11-19
• /
• 2006

For several years, a research about the simulation for shipyard and shipbuilding has been performed. This research is based on the concept of PLM (Product Lifecycle Management) and DM (Digital Manufacturing). Global leading companies and research center are trying to get a good position of PLM, especially M&S field. Digital shipbuilding is to computerize shipyard facilities and shipbuilding processes, and to simulate expected scenarios of shipbuilding processes using a computer model in order to resolve a potential problem such as a bottleneck processes, and over loaded resources. In this paper, simulation methodology for shipbuilding is described. In addition, a local and global strategy for the use of simulation methodology is suggested. Finally, case studies about an indoor shop and an outdoor shop are described.

• The Journal of Information Systems
• /
• v.31 no.1
• /
• pp.239-269
• /
• 2022

Purpose This paper attempts to identify items for improving the usage of PLM(Product Lifecycle Management) systems and suggests ways to prioritize improvement items on the basis of importance. It also tries to find out differences in the importance of improvement items due to the company size, the industry, the job, or the PLM solution. Design/methodology/approach Through a survey from participants to a PLM System Conference, data were collected from a sample of 181 users who had the previous experience in using a PLM system. In order to figure out the differences in the importance among user groups, the F-test with the Scheffe test as a post-hoc analysis was used in case of equal variances and the Welch test with the Dunnett T3 test was used in case of unequal variances. Findings This study sorted out 25 improvement ideas according to their importance assessed by the PLM system users. The top five ideas are improving data consistency, error minimization, fast system response time, enhancing user recognition, and business process improvement. The support group puts higher importance than the general user group in data consistency, fast system response time, enhancing user recognition, business process improvement, dedicated team for data consistency, continuous support from management, hardware performance upgrade, output linkage to other systems, and shortening problem solving duration. The largest company group attaches significantly higher weights than the smallest company group to data consistency, error minimization, fast system response time, business process improvement, dedicated team for data consistency, security with proper access management, output linkage to other systems, and better user interface.

• Korean Journal of Computational Design and Engineering
• /
• v.13 no.3
• /
• pp.163-174
• /
• 2008

In this paper, for integrating of data on car parts we model information of parts that PDM system manages. Ontology of car parts applies existing ontology mapping research to integrate into car ontology. We propose a method for semantic integration of PLM object of MEMPHIS based on the integrated ontology. Through our method, we introduce C# ontology model to apply existing C# applications with ontology. We also classify ontology integration into three through examples and explain them. While semantically integrating PLM objects based on the integrated ontology, we explain the need for change of PLM object type and describe the process of change for PLM object type by examples.

• Current Industrial and Technological Trends in Aerospace
• /
• v.7 no.1
• /
• pp.105-112
• /
• 2009

Aerospace and Defense(A&D) industry is the representative extended enterprise that develops products by collaborating among suppliers operating individual information system(IS). Efficient collaborative working environments are essential component to achieve successful business and collaboration environments based on IS have been applied to support coherent process usage and securely share the information through the entire product lifecycle phases. This paper describes the status of information system management of the leading A&D enterprises and their information management processes. It also introduces the case studies of enterprises implementing product lifecycle management(PLM) solution to realize stable collaborative tools between customer and supplier.

• Journal of the Korean Society for Precision Engineering
• /
• v.23 no.3 s.180
• /
• pp.22-31
• /
• 2006

This paper introduces an approach to an ontology-based knowledge framework for product life cycle management (PLM). Participants in a product life cycle want to share comprehensive product knowledge without any ambiguity and heterogeneity. However, previous knowledge management approaches are limited in providing those aspects. Therefore, we suggest an ontology-based knowledge framework including knowledge maps, axioms and specific knowledge far domain. The bottom level, the axiom, specifies the semantics of concepts and relations of knowledge so that ambiguity of the semantics can be alleviated. The middle level is a product development knowledge map; it defines the concepts and the relations of the product domain common knowledge and guides engineers to process their engineering decisions. The middle level is then classified further into more detailed levels, such as generic product level, specific product level, product version level, and product item level for PLM. The top level is specialized knowledge fer a specific domain that gives the solution of a specific task or problem. It is classified into three knowledge types: expert knowledge, engineering function knowledge, and data-analysis-based knowledge. This proposed framework is based on ontology to accommodate a comprehensive range of unambiguous knowledge for PLM and is represented with first-order logic to maintain a uniform representation.