Product Development Class using Product Data Management Software and 3D Printing

2018 ◽  
Vol 21 (6) ◽  
pp. 90-98
Author(s):  
NamchulDo
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.


Author(s):  
Sharad Sheth

Abstract Global competition challenges engineering and manufacturing enterprises to shorten product development cycles, while meeting more stringent quality and cost objectives. In addition, product design and manufacturing methodologies are more complex, encompassing a complicated integration of electronic, mechanical, optical, and other subsystems.


Author(s):  
Daniel Svensson ◽  
Johan Malmqvist

Abstract Various database systems are used during the product development process to store and retrieve data about products. For example product data management (PDM), enterprise resource planning (ERP) and requirement management (RM) systems. All those might be needed to support the product development process. Earlier research has investigated the co-existence of PDM and ERP systems. This paper extends this question and takes a look on how requirement management systems fit into the picture and how these systems can be used together in order to support the product development process. A comparison of functionality and product models of RM and PDM systems is made. A requirements driven product model of a car cockpit implemented in a RM tool is used as a theoretical reference. The actual situation at the company developing the cockpit is then described. Based on the comparison of the functionality and the product models, three strategies for how the systems could cooperate are presented. The strategies are discussed from both a theoretical and a practical point of view. The conclusions are that RM systems has functionalities for requirements management that do not exist in a PDM system, which calls for the use of both systems. This results in problems with traceability and duplicate data. A certain degree of requirements traceability can be achieved between the systems by applying the strategies presented, but this is not a trivial task.


2002 ◽  
Vol 10 (3) ◽  
pp. 203-211 ◽  
Author(s):  
Fu Qian ◽  
Zhang Shensheng

Product data management (PDM) systems are enabling tool of concurrent engineering (CE). Although the PDM system provides good support for product data, particularly at the early stages of design, it is seldom used beyond the design process. Furthermore, it provides few facilities for activity definition and no facilities for the enactment of production activities. In order to manage the whole lifecycle of motorcycle development, this paper presents a product development process management system that integrates the workflow management system (WFMS) with the PDM. On one hand we can use the powerful product data management functionality of PDM systems, on the other hand we can use the effective process management and control functionalities of WFMS. For the sake of guiding and constraining the workflow modeling, we provide an integrated product development workflow model named P_PROCE model. It is made up of five views that are the process view(P), the product view(P), the resource view(R), and the organization view(O), the control & evaluation view(CE). Based on this model, the architecture and implementation of the product development process management system is presented. It consists of the workflow modeling module, the workflow enactment module and the PDM system. The first module includes process modeling, system sustain and API. The second module includes the personal desktop and the workflow engine. The PDM system is regarded as a workflow-enabled application. The workflow engine invokes it by the Tool Agent.


2010 ◽  
Vol 118-120 ◽  
pp. 944-947
Author(s):  
You Jun Zhang ◽  
Shi Jie Wang ◽  
Han Li

Product Data Management (PDM) enables the management of the entire product lifecycle and related information about its design and its manufacturing. The key of implement PDM technology is realization of the structure and configuration management about the product. The main functions of PDM and the product development process based on PDM are detailed in this paper. An implementation method is proposed and it is applied for a system by means of an example, which achieves a good result.


Sign in / Sign up

Export Citation Format

Share Document