Aras Variant Management is Getting Better and Better

A while ago, I wrote a blog on why Variant Management should be considered before 150% BOM (Bill of Materials) is reached for an already-designed product that becomes available. The key is reusing the variant logic on distinctive design representations, including validation and comparison, which is the exact architecture of Aras’ Variant Management solution. The separation between the variability logic and breakdown structure data models enables the use of both in any combination and at any phase of a product’s lifecycle.

These features result from collaboration with the application’s users and their various underlying use cases. Let’s take a quick look at each of the new capabilities.

Reusable selection sets

The new selection set capability allows users to save selected features and options under a unique name and reuse them later to support different use cases. This reduces the underlying 150% breakdown structures to a specific 100% variant in which the breakdown structure can be a physical BOM, a functional breakdown, document content, or a complex set of requirements:

• A modified variability logic and/or breakdown structure
• A new variability logic and/or breakdown structure, or
• Any combination of the above

A selection set is automatically validated against the variability logic and breakdown structure it applies when reusing. Any conflicts are automatically identified, and the user receives interactive guidance on resolving them. With an appropriate configuration of the Aras platform, selection sets’ use and change history can be traced via the product’s digital thread throughout the product lifecycle

Fig. 1: Validating a named selection set in a new context

The ability to reuse a specific configuration of the variability logic offers significant value to the product teams. It reduces errors, improves productivity, and encourages collaboration. This is because once variability logic is defined and validated, multiple users can leverage it in different contexts by selecting any combination of the related features and options when exploring a family of variants.

Reusable usage conditions

The new usage conditions capability allows you to save each condition under a unique name so that we can use and reuse it later on any applicable assets within any breakdown structure. This allows the individual conditions to be defined and validated once and used repeatedly in configurations with other usage conditions.

Since usage conditions identify valid conditions when an asset (such as a part) can be used, the ability to identify them by name enables management and differentiation of global vs. local circumstances. This offers significant benefits when managing supply chain issues or market differentiation. The global condition can now be managed on an enterprise-wide basis, while the local conditions may be specific to a manufacturing plant or a geographically narrow market opportunity.

Fig. 2: Identifying structures affected by a named usage condition

Named usage conditions make change management easier because they are versionable and traceable via the product’s digital thread. A good example is the where-used analysis service in the Aras platform, which allows you to identify every configuration affected by a specific version of a condition or every configuration affected by a change in an existing condition.

Variant Matrix

Maintaining and debugging variability features, options, and rules for a product family is not easy. This is especially true when the separation of the variability logic and breakdown structures affects multiple representations of the product.

Fig. 3: Dynamically generated variant matrix

The variant matrix capability allows you to review, validate, and compare multiple variants of multiple breakdown structures in bulk via a single UI (user interface). Since the number of valid combinations can be high, the user can control the scope of their analysis by selecting specific features and options related to the analysis. This improves productivity and significantly reduces the time needed to analyze multiple combinations of resolved or proposed variants.

Closing thoughts

The release of the variant management application improves users’ productivity and ease of use. This helps manage the increasing complexity of today’s products by maintaining its focus on the various representations throughout the lifecycle of the product’s platform and its variants instead of limiting it to BOM only. To see a demonstration of the application and new capabilities, click here.

As with all Aras solutions, upgrading to the latest releases is risk-free because Aras guarantees upward compatibility via no-cost upgrade services for subscribers. This is true for on-premise and cloud (Aras Enterprise SaaS) deployments.