The Governance domain allows companies to launch enterprise-wide new product introductions on-time and on-budget. Within Governance are these sub-processes: Requirements Management, Portfolio Configuration, Program Management, Decision Support Business Intelligence, and Compliancy.
ENOVIA Variant Configuration Central
System engineers and product planners use ENOVIA® Variant Configuration Central™ to tackle product diversity during the “idea” or concept phase of the product development process.
As products become increasingly complex with costly mechanical, electrical, and software capabilities, customers are demanding products that fulfill their unique needs at the lowest possible cost. To stay ahead of the latest innovations and market trends, companies must transition from traditional design processes to an approach that supports the definition of conceptual product architectures for highly variable configurations.
Unfortunately, many companies today have no simple mechanism for designing products that provide high market variation with technical modularity while controlling costs. With ENOVIA Variant Configuration Central, companies can define conceptual product definitions that can be reused across a multiple series of products, satisfy market specifications, and provide many possible optional capabilities. These conceptual product definitions serve as a framework for defining variant products that are configurable and drive the generation of engineering bills-of-material (EBOMs). As a result, companies can expedite the design process and lower costs while meeting customer demands still.
ENOVIA Variant Configuration Central enables companies to manage the conceptual and commercial aspects of their products. System engineers and product planners are able to define a portfolio of products and features with configuration options based on specific customer and market requirements. Companies can improve their product introduction process and increase reuse by:
- Bridging the gap between marketing requirements and engineering
- Utilizing common modules across multiple product lines
- Delivering the right products to market as quickly and efficiently as possible
ENOVIA Variant Configuration Central effectively implements system engineering standards throughout the product development process, allowing companies to:
- Connect product marketing, system engineering, design engineering, and manufacturing
- Manage products that meet market, customer, and product launch criteria
- Define product features based on customer needs, market shifts, and technology innovation
- Improve part reuse and minimize feature proliferation with modular product definitions
- Improve profit by managing a family of variant products as bundled offerings
- Rapidly introduce a family of variant products to market using a logical product structure that allows the reduction in product diversity while still fulfilling market demands
- Maximize the number of valid configurations available to the market
- Increase customer acceptance by eliminating invalid product configurations early in the sales process
- Optimize the design process of highly variant products by allowing design engineers to quickly create an EBOM
- Maximize part reuse by controlling feature proliferation
Product Portfolio DefinitionENOVIA Variant Configuration Central organizes and manages a company’s portfolio of products. Product lines and model hierarchies organize a company’s family of products. Product lines manage a library of mandatory features and rules without compromising organization security. Models and products inherit mandatory features and rules defined and managed by product marketing at the product line level.
Product PlanningBefore development starts, product managers plan product releases (“product revisions”) that meet market demands and introduce new technologies that provide competitive advantages. With ENOVIA Variant Configuration Central, product managers innovate during the product planning activities by indentifying the list of candidate features that need to be committed, planned, and developed in a product release. A logical product structure for each product release is defined containing all possible variations. A product release is used as a platform to introduce new variant products with specific capabilities that downstream product sales can configure using marketing options (e.g., color, country of sale, etc.).
Product Architecture/Product DecompositionSystem engineering can define a logical product structure based on a hierarchical (skeleton) structure used to combine solutions that derive a family of variant products. By applying marketing variation and rule-based conditions to the logical features, system engineers can increase the usage of common parts between products. At the same time, system engineers are given advanced productivity tools to help minimize feature proliferation. Conceptual design activities allow system engineers to relate physical parts that fulfill each feature’s technical and marketing requirements. Companies can now streamline the design process, maximize part reuse, and minimize feature proliferation.
Mandatory Compatibility Rules (Global Rules)Marketing and system engineering can define and manage feature compatibility rules at any level of the product structure. System engineers can define a single compatibility rule at the product line level and force it to be used by lower level products. This capability is known as a mandatory compatibility rule. Product line mandatory rules are visible by lower level products. This information allows system engineers to make informed decisions when defining compatibility rules within their products.
Product VariantsThe logical product structure is used as a framework to introduce a family of related variant products with specific technical and marketing options. Product sales can then further configure the variant product with customers. Product variants allow companies to reduce diversity by controlling the variations of products that are available for configuration. System engineering controls product variant content and options by selecting the specific technical and marketing features available for configuration that meet specific requirements( e.g., target sales price, target region, or targeted consumers). During the product variant definition, system engineers use the Product Compatibility Matrix to select features and define their usage criteria as “Mandatory (M),” “Standard (S),” or “Optional (O)”.
Product ConfiguratorENOVIA Variant Configuration Central helps companies with highly configurable products meet market diversity requirements. Sales engineers can meet the unique needs of their business customers using the configurator to define new products. For a build-to-market business model, system engineers can pre-define product configurations published in a company’s product catalog. In addition, system engineers can create partial configurations for the products they are responsible for that are available to cross functional groups to define further. In order to maximize the re-use of configured accessories and service parts, engineers can create product configurations at any level of the feature hierarchy. When product configurations are created at the sub-feature level, an EBOM can be generated and submitted to engineering for verification and release. The newly generated top-level part assigned to the feature’s configuration is back-annotated and re-used with the feature’s part table.
BOM GenerationENOVIA Variant Configuration Central enables system engineers to define a feature architecture that is used as a framework for generating an EBOM for Engineering to Order (ETO) business models or a precise bill of material (PBOM) for build-to-order business models. A BOM Preview dialog provides users the ability to preview selected parts based on the selected marketing features and evaluated part inclusion rules. When used with ENOVIA® X-BOM Unit Tracking, the unit numbers (builds) can be associated to Manufacturing Plans for as-manufactured traceability.
Build ManagementAs product configurations are ordered, product planners and manufacturing planners need the ability to plan, manage, and structure the builds, also known as units, which are to be delivered to specific customers. The product planner can assign serial numbers, unit numbers, and manufacturing sequence numbers to each build that needs to be manufactured for each product configuration. The manufacturing planner can then define the composition of the manufactured serialized units that are installed on the unit.
Issue Resolution and Change ManagementAs products enter into the development phase of their project, changes are inevitable but too many changes are cost prohibitive. A cross-functional change process helps system engineers manage and respond to feature changes systematically. ENOVIA Variant Configuration Central provides a choice of change management processes that provide immediate visibility to change requests while maintaining integrity of the original reported problem to the internal resolution.
Configuration Planning for Virtual ManufacturingWith highly configurable products, engineering must consider design alternatives for all product offerings and manufacturing engineers must ensure that product options can easily be manufactured at all manufacturing facilities available to them. Manufacturing planners can now define “Manufacturing Plans” as placeholders in ENOVIA to reference unique alternative process definitions in DELMIA®. Each ENOVIA ‘Manufacturing Plan’ represents a unique way to produce a product or a sub-system in DELMIA. Manufacturing planners can then apply configuration rules to logically select the proper DELMIA process plan based on configuration criteria.
The Role of ENOVIA V6 and PLM 2.0ENOVIA Variant Configuration Central supports PLM 2.0, product lifecycle management online for everyone, and the ENOVIA V6 values: global collaborative innovation, single PLM platform for intellectual property (IP) management, online creation and collaboration, ready to use PLM business processes, and lower cost of ownership.