Metadata for Long Term Preservation of Product Data

Author(s):  
Joshua Lubell

Product data can be usefully defined as structured information about objects that are produced by industrial and business processes. In terms of information types, data formats, usage, and lifespan, product data is both complex and diverse, encompassing 3D image modeling information, dimensions, tolerances, and other model annotations, supplementary material such as test analysis, videos, datasets, and human-readable documentation. Although the metadata issues in this problem space present some unique challenges, there are valuable lessons to be learned from the library metadata and packaging standards and how they relate to product metadata. Extending the library standards to represent subsets of information from emerging product lifecycle management standards could help tame the complexity of long-term archival of product data.

2009 ◽  
Vol 131 (03) ◽  
pp. 34-37
Author(s):  
Jean Thilmany

This review explores the prospects of using product lifecycle management (PLM) as an end-to-end solution. The components of PLM provide significant value, but there are no fully integrated offerings on the market that perfectly cover every aspect of product lifecycle, according to a report. In the absence of an end-to-end tracking system, one trend coming to prominence is the use of PLM as the complete system of record for all product data. Though a study concluded that PLM still has a way to go in terms of tracking product design from early inception right through sales to reclamation, it is becoming the main go-to source for a large amount of product data. Experts believe that PLM still has a way to go in terms of tracking product design from early inception right through sales to reclamation; however, it is becoming the main go-to source for a large amount of product data. Software developers are working to create tools that can incorporate ever more of the big picture and make it accessible to engineers.


2013 ◽  
Author(s):  
R. Sharma ◽  
Bo-ram Kim ◽  
Tae-wan Kim

In logic based product lifecycle management system (LBPLMS) for the shipbuilding industries, all the manufacturing and business processes are reflected in the structured bill of materials (BOM) and operated through structured BOM, Sharma et al. (2011) and Sharma and Kim (2010). The efficient representation of the product structured BOM and application of the manufacturing and business operations management techniques to adapt products to the high demands of quality and in-time delivery are pivotal to the successful operation in the world of shipbuilding. In this work, we study the data organization and management of structured BOM through various stages of manufacturing and business operations, propose a unified structured BOM skeleton model to achieve automatic conversion of structured BOM to ensure consistency, and provide a unified structured BOM method and technique for manufacturing management and business process integration.


Author(s):  
Anupam Ghosh ◽  
Jane Fedorowicz

E-collaboration, defined as “collaboration among individuals engaged in a common task using electronic technologies” (Kock, Davison, Ocker, & Wazlawick, 2001), is increasingly gaining relevance at the interorganizational level because of the growing practice of working with dispersed project teams across the globe. E-collaboration links together partners on projects and business processes that cross legal boundaries, as is the case, for example, in supply chains and in product lifecycle management (PLM) teams. General purpose computer-based collaboration tools like the Internet, e-mails, instant messaging, discussion boards, groupware, portals, blogs, and wikis are commonly used for e-collaboration (Fichter, 2005), while task-specific tools exist for many interorganizational activities such as PLM or collaborative planning, forecasting, and replenishment (CPFR).


2005 ◽  
Vol 5 (3) ◽  
pp. 227-237 ◽  
Author(s):  
Ravi M. Rangan ◽  
Steve M. Rohde ◽  
Russell Peak ◽  
Bipin Chadha ◽  
Plamen Bliznakov

The past three decades have seen phenomenal growth in investments in the area of product lifecycle management (PLM) as companies exploit opportunities in streamlining product lifecycle processes, and fully harnessing their data assets. These processes span all product lifecycle phases from requirements definition, systems design/ analysis, and simulation, detailed design, manufacturing planning, production planning, quality management, customer support, in-service management, and end-of-life recycling. Initiatives ranging from process re-engineering, enterprise-level change management, standardization, globalization and the like have moved PLM processes to mission-critical enterprise systems. Product data representations that encapsulate semantics to support product data exchange and PLM collaboration processes have driven several standards organizations, vendor product development efforts, real-world PLM implementations, and research initiatives. However, the process and deployment dimensions have attracted little attention: The need to optimize organization processes rather than individual benefits poses challenging “culture change management” issues and have derailed many enterprise-scale PLM efforts. Drawn from the authors’ field experiences as PLM system integrators, business process consultants, corporate executives, vendors, and academicians, this paper explores the broad scope of PLM, with an added focus on the implementation and deployment of PLM beyond the development of technology. We review the historical evolution of engineering information management/PLM systems and processes, characterize PLM implementations and solution contexts, and discuss case studies from multiple industries. We conclude with a discussion of research issues motivated by improving PLM adoption in industry.


2004 ◽  
Vol 126 (03) ◽  
pp. 43-45
Author(s):  
Alan S. Brown

This article focuses on the advantages of technology over manual intervention. Products are made to order in a process that spawns a stream of changes to CAD drawings, technical specifications, bills of materials, assembly instructions, and other documents. The secret of Swagelok’s success is workflow software, which helps automate and manage repetitive business processes, such as engineering change orders, document revision, review, and design release. It lets a computer automatically route drawings and documents to every person who needs them. Workflow software creates a single system for gathering all of the necessary history, measurements, and models. Swagelok and Evernham use workflow software to control and track the movement of information. Many larger companies, on the other hand, have used workflow software to move data automatically among applications. Such complex workflows are usually part of a larger product lifecycle management solution.


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.


2011 ◽  
Vol 133 (03) ◽  
pp. 42-43
Author(s):  
Alan F. Mendel

This article studies the role of product lifecycle management (PLM) in industrial engineering. The basic concepts of PLM—product data management, engineering change management, and product structure management—were also discussed. PLM provides data and management capabilities to reduce the non-value-added tasks required of engineers. It also increases engineering productivity, provides insight into engineering efforts, and improves product quality and customer satisfaction. Companies are receiving significant value and return from their PLM investments. Many companies begin implementing PLM by establishing a single source of product data, or product record. Most PLM solutions offer sophisticated interfaces to many design automation and office applications, which reduce the need to capture, store, and validate product data. Product designs are maintained as assemblies and parts in the PLM system, and that arrangement allows engineers easy searching when they are looking, for example, for legacy components, with software providing a critical control and value portion of the product. With PLM, disparate engineering teams work more collaboratively.


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