ENOVIA Product Variant Management (PVM) provides functionality for product planners to define product models and option packages for each model. These marketing-oriented definitions are inserted early in the product development process to directly control the set of product variants that will be designed and built, bridging the market demand fulfilment process and product development process.
Functions are provided for defining a corporate dictionary of product options consisting of categories (e.g. transmission) and specifications (e.g. manual, automatic). After the dictionary is available, a product planner defines rules for product-model and option usage. For instance, rules may be defined to ensure that the millennium edition is available only during the year 2000 or that the US model should only be available with automatic transmission.
In this release V5R21 there are no new enhancements.
Ability to store both marketing and technical aspects of the product definition in a single system
Ability to allow marketing requirements to directly control product design specifications
Ability for product planners to define products, product models, the specifications of each model, and option packages for each model
Ability for product planners to define a corporate dictionary of product options (categories and specifications) and to regulate the usage of these options on products
Ability to validate product specifications during the configuration process to ensure that all predefined rules are respected
Product Key Customer Benefits
Link customer demand fulfillment process and product development process
A lot of manufacturing companies today rely on simple applications, such as a spreadsheet, to define and manage their product lines and sets of product option packages. This creates a disconnect between the "market demand fulfillment" process and the actual product development process resulting in products that are not built according to the initial specifications, thereby requiring a lot of reworks.
Early product variant management
Insert requirements from the market early in the product development process to control the set of product variants and option packages that will be designed and built. This ensures that products are built according to their original marketing-oriented plans
True rules-based variant management
The main benefit of this product is to be able to implement rules on option usage.For instance, ensure that the steering wheel will be on the left side for US market and the right side for UK market, etc.
Proper usage of product options according to planning
Apply effectivity criteria on product models and specifications. For instance, a product planner can apply date effectivity for an automobile model ensuring that it will not continue past a certain date. Similarly, specific variants of a particular automobile model can have their own date effectivities.For example, special millennium edition only available during the year 2000 or a special option package is only available starting the second model year.
Increased parts and components commonality between multiple products
Planner of various products are encouraged to use the same basic categories and specifications between the product lines because the dictionary of product specifications is centrally managed.For instance, a company that produces both commercial and passenger vehicles can share certain product specifications such as engines and batteries.This helps a company to satisfy market demand without increasing manufacturing complexity by using components across as many product variants as possible.
Easy BOM retrieval for each product variant
Validated product specifications are saved as persistent BOM filters.Product specifications are accessible directly under a product in the product class tree and can be used to directly launch the product variant to product editor or to DMU.