Introduction

Managing alternates is an important part of ensuring product flexibility throughout the release process. In many cases, an alternate part should not apply globally to every occurrence of a component but only to a specific usage within the product structure.

The Engineering Release application in ENOVIA now enables you to define an alternate that applies exclusively to a selected instance within an assembly.

Alternate Definition at the Instance Level

Instead of creating an alternate relationship that affects all occurrences of a component, you can select a specific instance and assign an alternate directly to that occurrence. This provides you a greater control over how part or product alternatives are proposed and qualified, particularly in complex assemblies where the same component may be used at multiple positions.

By associating the alternate with the selected instance, you can accurately reflect real-world requirements while avoiding unintended impacts on other occurrences of the same part or product.

                                                   Image1: An alternate for a specific instance

Control the Target Usage Domain

When defining an instance-specific alternate, you can also specify the target usage domain for which the alternate is valid:

• Manufacturing – the alternate is applicable only within manufacturing-related structures and processes. 
• Service – the alternate is applicable only within service and maintenance contexts. 
• Manufacturing and Service – the alternate is valid across both domains. 

This capability allows organizations to manage domain-specific requirements more effectively. For example, a manufacturing alternate may be used to support production constraints, while a different service alternate may be preferred for maintenance and spare parts operations.

Improved Precision and Traceability

By combining occurrence-level alternate management with domain-specific applicability, Engineering Release app provides a more precise way to manage interchangeability and its intent. Release engineers can ensure that alternates are defined exactly where they are needed and only for the relevant downstream consumers.

The result is greater consistency between engineering, manufacturing, and service teams, along with improved traceability and control throughout the product release process.

                                                                       Image2:  Occurrence paths of the same instance

The following video illustrates this concept: