scholarly journals Software to Report Product and Manufacturing Information in QIF Files

Author(s):  
Robert R. Lipman

The QIF PMI Report (QPR) software generates a spreadsheet from a Quality Information Framework (QIF) file containing Product and Manufacturing Information (PMI). QIF is a unified XML framework standard for computer-aided quality QIF systems, available free to all implementers. QIF enables the capture, use, and re-use of metrology-related information throughout the Product Lifecycle Management (PLM) and Product Data Management (PDM) domains. PMI consists of annotations and attributes that define product geometry and product specifications. PMI includes annotations to specify Geometric Dimensioning and Tolerancing (GD&T), as well as non-geometric data such as surface texture specifications, finish requirements, process notes, material specifications, and welding symbols.

Author(s):  
Omar Msaaf ◽  
Roland Maranzana ◽  
Louis Rivest

Difficulty in locating existing information in order to reuse it constitutes a major challenge to productivity. The use of PLM systems (Product Lifecycle Management) aims in particular to reduce the time and cost of developing a product by facilitating the re-use of existing parts or related information (process plans, tools, FEM, estimates, etc.). When information is alphanumerical, using search engines, such as those made popular on the internet, is efficient. However, a significant portion of information used in engineering rests within CAD (Computer Aided Design) models, making such search tools irrelevant. To aid in the re-use of information, two problems must be resolved: it is first necessary to be able to locate similar parts in the electronic database of the company, and then be able to systematically identify their differences. This article presents some of the results from our work on part, product and process data mining (P3DM). It focuses on tools developed to search similar 3D geometric models and to identify their differences. The PartFinder application locates similar parts by comparing signatures extracted from their solid representations. The 3DComparator aims to identify the differences in terms of Form and Fit between the identified parts. In both cases, the recommended approach is independent of the CAD system, and can also deal with parts represented by IGES or STEP files. Moreover, the approach does not require that the parts occupy the same position and have the same orientation in space. These two points, CAD and position independence, are the main benefits of our approach compared to other existing applications. Lastly, if the comparison takes place between two evolutions of the same geometrical representation of a part, a third tool allows the comparison of the specification trees. The SpecComparator is also presented briefly. An example based on industrial data illustrates the benefit that could be generated.


Author(s):  
Manas Bajaj ◽  
Christian J. J. Paredis ◽  
Tarun Rathnam ◽  
Russell Peak

Across product lifecycle processes, engineers continually analyze product behavior and refine product specifications. Owing to the collaborative and multi-disciplinary nature of product realization, engineers work on subsets of a product’s specification, also known as a product view, and use their expertise to analyze domain-specific (e.g., electrical, structural, thermal) product behavior. In this paper, we present the notion of a product view federation that embodies engineering processes related to the creation, enrichment and reuse of a particular product view. We make the first step towards answering the following question — Can one formalize the process of creating a product view federation from component federates to enable knowledge reuse? We describe and exemplify one particular graph-based inference approach for creating the product view federation.


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.


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