Sahadev Roy. ISSN International Journal of Advanced Engineering and Management 3(1): 12-16, 2018 Product Lifecycle Management

Transcription

1 3(1): 12-16, 2018 Product Lifecycle Management Sahadev Roy Abstract The Product Lifecycle Management (PLM) idea grasps guarantee of incorporating all the necessary information generated all year round in any industry or manufacturing plant. All the managers and technical level worker related to each product with the main functions of a cycle and with the original suppliers, customers. The PLM system is a technique that implements the exact concept of lifestyle management including product information-modeling which may support the custom range or full range of data delivery. A behavioral-level conceptual model and corresponding hierarchic rendering relationship defines as a master model and functional model. Product domain-specific aspects- and two transitions, ideal models and mapping are called, master models and other are functional mode. The purpose of the structure: (1) Accrue products, design logic, gathering, and acceptance data from the first to the conceptual Design phase - where designers are involved in product function and performance - with whole life cycle; (2) Simplify simplicity Interaction of latest computer-aided design and drafting; And (3) captures the evolution of family of products and products. The structure in the proposed system is a structure that can access any material information directly from the product life system management. Keywords Design-analysis integration model; PLM system architecture; Product family evolution model (PFEM); Product lifecycle management; Reference product model. I. Introduction Product Lifecycle Management is usually a strategic business methodology for effective process management. PLM systems are being recognized for managing the information of a corporation's product throughout the whole life cycle of the products [1]. One of the main aims is to stimulate the development and production innovation of process. Strategic business processes are used for effective creation, management and use of corporate intellectual capital, from a productive initial idea of PLM concepts [2]. The target to developed products quickly in the market and reduce errors [3]. One of the major targets of any PML systems is the product information modeling architecture development. The traditional hierarchical methods are generally based on Product Data Management (PDM) systems [4]. A single PLM system support framework for manage all product related information across the entire product lifecycle. This structure and its components are presented after a brief discussion of PLM concepts and architecture and interaction related issues of the main PML system. PLM holds the promise of integrating and supplying together all the information produced at all stages of a product lifecycle of an organization with the original supplier and customers [5]. The manufacturers can shrink time during the introduction of new product models in a few ways. Product engineers can dramatically shorten the cycle of implementing and applying engineering changes across an extended design chain [6]. Buying agents can work more effectively with suppliers for reuse of parts. The Executive Council can take a high level of information of all important product information, part of the production line can fail to participate in the failure rate and the data collected from the information collected from the lost data field [7]. Since PLM systems have gone beyond the product design software, the company's management transmits PLM concepts to engineering executives, who traditionally manage their own technology rollout. To succeed PLM concept, to set up data standards and incorporate corporations-wide integration architecture design issues, it must be tackled so that the previously released information can be used for people [8]. In this way, people make important decisions in various departments-such as how to launch products or include a phase of design of a product-when they are most expensive, rather than growth at the stage of partnership or even during production. The objective of the paper is to provide an introduction to Product Lifecycle Management (PLM), providing the required information about PLM [9]. This will definitely assist those working with PLM those involved in a company s PLM object. Initiative, to realize the basics of requirement of PLM and its importance. It will allow them to participate more PLM activities and its importance in industry. The first part of the chapter gives definitions of PLM, a PLM Initiative, and the PLM Paradigm [10]. The second part of the chapter looks at the meaning of the letters P, L and M in the PLM acronym. The third part addresses the scope of PLM. It introduces the PLM Grid, describes Technical and Scientific Publication

2 activities within the scope of PLM; and identifies the resources managed in PLM. The fourth part of the chapter describes the PLM Paradigm, detailing concepts, consequences and corollaries. The fifth part looks at the potential benefits, strategic and operational, of PLM and a PLM Initiative. II. PLM System Architecture PLM system is a tool that helps a corporation to implement PLM concepts. The functionality of the full PLL system can be achieved by the specific part described here. These are: (1) an Information Technology (IT) Infrastructure; (2) a product information modeling architecture; (3) a development toolkit and environment; And (4) a set of business applications. IT infrastructure is the foundation, which is hardware, software and internet technology, underlying presentation and computing language and distribution and object and components. Product information Modeling architecture products include theoretical and interoperability standard Development Toolkit and Environment Provides a way to build commercial applications that provide basic functionality and increase the functionality of PLM concepts and extend the kernel (eg geometry, mathematics), visualization tools, data exchange standards and mechanisms and On the database Can include. Semantic philosophy defines restrictions on interpreting and using information; it is used when data infrastructure and tools are related to data encoding and structure [11]. Potentially applicable technologies are discussed in the draft of the work in the opinion of these two classes. Detection and traceability were inherent in aspect aspects of the main element and inherent in logical tolerance. PLM systems are formed in the top of the corporate software sequence and are frequently implemented so that they rely on detailed information capture and transmission methods. The PDM system may depend on the CAD system for managing product descriptions. The target PLM systems must create easily accessible product details and their design logic, without the intermediate level of software. PLM systems must communicate with product behavior information at late stage of life cycle PML systems are still very early stage and contain a fox. It can lead to the development of many proprietary systems and interfaces, which can lead to additional interoperability problems, therefore, the need for national and international efforts for quality development in order to overcome future interoperable problems for PLM systems. III. Reference Product Model Core Product Model's primary purpose (CPM) is to provide a base-level product model that is open, generic, extensible, and independent of any one product development process independent and completely in the engineering context. Partly, Artifact represents an individual entity in a product, whether that entity is one of the whole product or its subsystem, part or element [12]. The function represents what artifact is intended for. The independent representation of the function is the core product model and its extensions are able to support functioning arguments, which provide no information on the form of interference in absence, thus providing support for design conceptual stages [13]. The form can be seen as a proposed design solution for the specific problem by function, and Artifact's geometry (the shape and structure can be geometrical in some contexts) and it has been created. How the behavior represents the function of artifact in its function; Examples of other behavioral models such as cost, Manila, stability, etc. may be included. As mentioned above regarding functions, this extended presentation of behavior is the main product model and its extensions support the behavioral argument at all stages of the life cycle of the product [14]. The feature represents a subset of the form that has some functions given in it. The CPM does not treat the properties of pure form elements, it does not support the independent behavior of features. Figure 6 shows the relationship of CPM. All relationships are abstract class subcategories of Common Core Relationship and all UML associations classes. An association class between requirements specification and artifact core properties; Each of the requirements may apply to certain aspects of function, form, geometry, or artifact element that the requirements can only deal with functions, but the custom can be specified without specific functional arguments for several aspects of the form). Assessment of nature and information requirements for assembly information model parts and assembly relationships. The model includes both conventions as a concept and assembly as a data structure. The former class association is represented by and the next is modeled using part-off relationships [15]. Orientation is not physically connected and represents the relative location and orientation between the two or more accessories that describe the restriction on the relative position and orientation between them. When combined, there may be multiple features-level associations combined, one artifact association may have different assembly characteristics Sahadev Roy, Product Lifecycle Management,, 3(1): 13

3 associations at the same time [16]. That is, an artifact association assembly combines association. An assembly feature association is generally related to two or more assembly features. However, in particular cases where an artificial association only involves an artifact, the relevant artifact associations have only one artifact when it can only be involved in a assembly feature. Tolerance is an instant problem design of the autonomic assemblies. Tolerance includes both tolerance analysis and tolerance synthesis. In the context of electromagnetic assembly design, tolerance analysis refers to the effect of the effect on the different results or the effectiveness of the assembly in separate parts or sub-dimension levels [17]. Tolerance synthesis means tolerance for the separate part or conclusions based on tolerance or functional requirements in the rally. Tolerance design is a product specific to the specific set of products deriving a description of geometric tolerance details for a product. Current methods of tolerance analysis and synthesis provide a detailed understanding of geometry of assemblies and, in most cases, are applicable to advanced design levels, which are not less than the best designs [18]. During a assembly design, both assembly structure and related tolerance data constantly develop; It is possible to achieve significant profit by effectively utilizing this information to influence the design of this assembly. In the initial design phase, any active aspect of assembly or endorsement analysis will include decision-making with incomplete data models. In order to run initial tolerance synthesis and analysis at the design stage of the conceptual product, we include assembly model functions, tolerance, and behavior information; This will allow analysis and synthesis of tolerance even with incomplete data sets. To achieve this we define a class structure for the specification of tolerance and we figure out. However, the integration of professionals' efforts into two areas of spatial and functional design should not be complete, due to the limited interconnection of the tools of the two sets. Design-Analysis Integration Model (DMIM) is a conceptual data architecture that provides the technical foundation of solid-analysis integration with today's tools and data models. It is intended to be analyticaldriven design (often known as form-to-function logic) more practical [19]. Finally, it should support opportunistic analysis, where the system tracks the geometric design process and when designers have generated specific geometrical data to begin an effective analysis. The Product Family Evolution Model (PFEM) product represents a reasonable representation of the evolution of families and the changes involved. First, even if the structure is presented, a first step towards a complete product modeling architecture supporting PLM concepts. To identify other framework components, a search needs to be modeled and integrated. Secondly, PML is a centralized search of literature and current PML system products that can develop a conceptual application programming interface (API) to explain the data needs of all generations in all PML process, which can deliver products to all PLM processes. As part of a conceptual interface specification, it is necessary to give considerable attention to the possible interaction between the product data provided by the PLM system and the product data provided by the metadata [20]. Third, it is necessary that the information related to the products of the scope of the scope will be necessary for the modeling structure recognition, the single language, the need for research instead of the homogeneous method of single-seller, and if necessary development, information exchange values which can provide interaction degrees. Criterion Recently, the computer support for product development is prone to covering a narrow slide of a product's lifecycle, usually from the specifications of the product's engineering to its physical adoption segment. Plumber pledged support for the entire life cycle of the product, to settle its last instance from the first point of view of concept. Volumes, diversity, and product descriptions will increase the complexity of data complexity. This paper describes the guiding principles for such structures as a single palm system support framework for product information that makes it possible to access, store, serve and reuse all product information across whole lifecycle, and four such structures form a kernel Elements are described. More research need to identify and model other components of the structure for a conceptual API development between PLM systems and frameworks. For identify and evaluate standards for data exchange process. Proposed product information modeling architecture is thought to be a greater opportunity than simply being a product information server for PML systems [21]. Design and manufacturing process components interoperate by large volume exchange of product information, and the proposed product information modeling framework, such as 'horizontal' data exchange process components, 'Vertical' exchange between PML systems and any intermediate system is easily supported, such as PDM and Enterprise Resource plans (ERP) System. Inertia National Institute of Stander No commercial products are approved or approved by companies and technology. This type of identification Sahadev Roy, Product Lifecycle Management,, 3(1): 14

4 does not mean recommendation or approval by the National Human Rights and Technology Institute, and it does not mean that the object or equipment is identified as the best available. CONCLUSION Changing business environment, the company is looking for new ways to provide maximum value to customers and to achieve competitive advantage. As a result, product design and complete PML have emerged as a strong focus on variou7s critical areas for modern art success. Intermediate finishing production at the design level and at the life level may focused on improving the cost of maintenance products, quality and market time. Nowadays, they are not enough to gain competitive advantage. On innovation it must ensure overall satisfaction from the customer product which goes beyond the traditional definition of product quality and cost, such as the problem. Environment, risk, life cycle costs and quality of service are also important. For the production of revenue, but a complex system, the real core was formed and a series of continuous resources such as customer service delivery. However, to enable the power of the industry as well Holistic products and supporting services are currently limited by information gap. REFERENCES [1] Sudarsan, R., Fenves, S. J., Sriram, R. D., & Wang, F. (2005). A product information modeling framework for 37(13), [2] Ameri, F., & Dutta, D. (2005). Product lifecycle management: closing the knowledge loops. Computer- Aided Design and Applications, 2(5), [3] Kang, L., Chung, B. G., Langer, R., & Khademhosseini, A. (2008). Microfluidics for drug discovery and development: from target selection to product lifecycle management. Drug discovery today, 13(1-2), [4] Lee, S. G., Ma, Y. S., Thimm, G. L., & Verstraeten, J. (2008). Product lifecycle management in aviation maintenance, repair and overhaul. Computers in industry, 59(2-3), [5] Terzi, S., Bouras, A., Dutta, D., Garetti, M., & Kiritsis, D. (2010). Product lifecycle management from its history to its new role. International Journal of Product Lifecycle Management, 4(4), [6] Hines, P., Francis, M., & Found, P. (2006). Towards lean product lifecycle management: a framework for new product development. Journal of Manufacturing Technology Management, 17(7), [7] Hines, P., Francis, M., & Found, P. (2006). Towards lean product lifecycle management: a framework for new product development. Journal of Manufacturing Technology Management, 17(7), [8] Alemanni, M., Destefanis, F., & Vezzetti, E. (2011). Model-based definition design in the product lifecycle management scenario. The International Journal of Advanced Manufacturing Technology, 52(1-4), [9] Ming, X. G., Yan, J. Q., Wang, X. H., Li, S. N., Lu, W. F., Peng, Q. J., & Ma, Y. S. (2008). Collaborative process planning and manufacturing in product lifecycle management. Computers in Industry, 59(2-3), [10] Alemanni, M., Destefanis, F., & Vezzetti, E. (2011). Model-based definition design in the product lifecycle management scenario. The International Journal of Advanced Manufacturing Technology, 52(1-4), [11] Ming, X. G., Yan, J. Q., Lu, W. F., & Ma, D. Z. (2005). Technology solutions for collaborative product lifecycle management status review and future trend. Concurrent Engineering, 13(4), [12] Ming, X. G., Yan, J. Q., Lu, W. F., & Ma, D. Z. (2005). Technology solutions for collaborative product lifecycle management status review and future trend. Concurrent Engineering, 13(4), [13] Li, J., Tao, F., Cheng, Y., & Zhao, L. (2015). Big data in product lifecycle management. The International Journal of Advanced Manufacturing Technology, 81(1-4), [14] Subrahmanian, E., Rachuri, S., Fenves, S. J., Foufou, S., & Sriram, R. D. (2005). Product lifecycle management support: a challenge in supporting product design and manufacturing in a networked economy. International Journal of Product Lifecycle Managemen. [15] Srinivasan, V. (2011). An integration framework for 43(5), [16] Huang, S. X., & FAN, Y. S. (2004). Overview of product lifecycle management. Computer Integrated Manufacturing Systems-Beijing-, 10(1), 1-9. [17] Srinivasan, V. (2011). An integration framework for Sahadev Roy, Product Lifecycle Management,, 3(1): 15

5 43(5), [18] Venkatasubramanian, V. (2005). Prognostic and diagnostic monitoring of complex systems for product lifecycle management: Challenges and opportunities. Computers & chemical engineering, 29(6), [19] Chiang, T. A., & Trappey, A. J. (2007). Development of value chain collaborative model for product lifecycle management and its LCD industry adoption. International Journal of Production Economics, 109(1-2), [20] Thomas, V., Neckel, W., & Wagner, S. (1999). Information Technology and product lifecycle management. In Electronics and the Environment, ISEE Proceedings of the 1999 IEEE International Symposium on (pp ). IEEE. [21] Zheng, L. Y., McMahon, C. A., Li, L., Ding, L., & Jamshidi, J. (2008). Key characteristics management in product lifecycle management: a survey of methodologies and practices. Proceedings of the Institution of Mechanical Engineers, Part B: Journal of Engineering Manufacture, 222(8), Sahadev Roy Dept. of ECE, NIT Arunachal Pradesh sdr.ece@nitap.in Sahadev Roy, Product Lifecycle Management,, 3(1): 16