Introduction

Industries with high variability products are in need of a simple way to define their portfolio that can cover all possible variations of their product offering.

ENOVIA Product Manager Role (PDM) is a role, available on cloud and on premise, that can be used by product and project managers to define such variability in a simplified manner.

This role drives the corporate product strategy with collaboration between cross-functional teams to achieve the product’s strategic intent. It helps companies manage the entire definition, planning and development of their product portfolio from the time new configurable products are introduced to the market to the time they are withdrawn from the market.

With this role, users can define and manage:

• Product evolution
• Market requirements
• The variability of products
• Constraints to ensure the configured product is valid
• 100% resolved Product Configurations representing order-able configurations

All these elements are defined on the level of a product evolution, and they ensure that the company proposed products are well adopted to the market needs.

Model Definition

The Model Definition is an ENOVIA application (widget) where these elements can be defined and managed as follows:

• The company portfolio of products:
  • Are defined using “Model Versions” representing evolution of a product, or other possible evolution (such as state evolution etc.)
  • A “Model Version” can evolve using revisions or branches representing different plan deliveries of the product

• The company variability dictionary:
  • Consists of variants and their values, option groups and their options

• Constraints that are applied during the product configuration:
  • Using two types of configuration rules, Matrix Rules and Rule Expressions, that help reduce the variant complexity explosion of a Model Version
  • To ensure the validity of the company product offering

• Product configurations:
  • Consist of the company proposed 100% resolved product valid configurations, that are order-able, and based on the company variability dictionary

• Requirements:
  • These requirements can be associated with the Model Version to drive the committed needs that drive the Model Version and variability definitions
• Manufacturing plans
  • These plans can be associated with a Model Version to represent precise “manufacturing sites” where the Model Version can be manufactured

The following video shows how this content is available in the app “Model Definition”.