We have put together a list of the concepts most commonly used in Methode´s ENOVIA PLM Training.
PLM stands for Product Lifecycle Management. PLM is the process of managing the entire lifecycle of a product from its conception, through design and manufacture, to service and disposal.
PLM integrates people, data, processes and business systems and provides a product information backbone for our product development operations.
Methode’s PLM system. Enovia is the PLM software brand of Dassault Systemes (DS). Enovia is used for many things, like:
- Bill of Materials (BOM) Management
- Project management
- RFQ – Quoting for new business
- Change Management
- Search parts, BOMs and documents
- Run data reports
- Manage and store documents
PLM Object is a database element that contains metadata. It is simply a place to store data. Mostly everything you can see or work within the PLM system is an object.
PLM Object type: Database objects can be Documents, RFQs, Projects, Customers, Variants, Products, Change Orders…
PLM Lifecycle: Each object goes through defined states that determine the work that can be done on the object, who can do it, and the execution of automated processes.
A Concept Bill of Materials (CBOM): When a salesperson receives a request for quotation, the need to conceptualise how the requested product will look like is created for the customer. This type of BOM will outline configurations and dependencies and will contain information about possible strategies for manufacturing and outsourcing.
An Engineering Bill Of Materials (EBOM) is a type of Bill Of Materials (BOM) reflecting the product as designed by engineering, referred to as the “as-designed” bill of materials.
A Manufacturing Bill of Materials (MBOM) represents how the product is manufactured. It collects material requirements and manufacturing processes. This kind of bill of materials is used for production planning in the PLM system.
Change Reference (CRef): The change reference process in PLM provides a consolidated process to manage the creation of minor drawing iterations. These minor drawing iterations cater for changes that do not affect the product’s Form, Fit or Function, and generally do not have any cost associated with the change.
Change Request (CR): It is a database object that collects the required changes and describes the reason for the change. An Engineering CR contains Parts that need to be modified. Those parts will be linked to a Change Action. The parts connected to a CR can be grouped and linked to different CAs.
Change Action (CA): It represents the exact tasks or actions that need to be completed or performed in order to apply the requested changes for a certain Part or Group of Parts.
Change Order (CO): If the changes have been approved, the CR will be promoted to state “In process CO”, a new CO will be created and Change Actions Responsible persons will proceed to work on the changes. Once the modifications are done, CAs and CO will be promoted to state “Complete”.
Part Profile Search Tool (PPST): is an in-house developed tool that allows non-PLM users access to a profile of part information. The information available in the PPST is coming from multiple databases, PLM, CMS and others. The primary purpose of the PPST is to provide users with a consolidated view of part information.
Product Development and Program Launch System (PDPLS): has been developed to enable Methode to improve business profitability and exceed Customer expectations by ensuring activities are better planned, coordinated and more tightly integrated.
- Potential issues (“potholes”) revealed early on
- Which issues to control based on impact/risk
- Issue tracking and management
