Skip to main content
6月 19, 2025 1:17 下午 UTC
Acknowledged

configurations that can control shared models different

Related products:Creo Elements/Direct

1. Describe the Problem

Shared models are the same models. So it is impossible to display them in different configurations. 

Also if 2 shared assemblies are contained in a main assembly, it is impossible to display them in different configurations. 
Like displayed below: The main assembly "Layout" contains 2 shared assemblies: "Bgr_1" and "Bgr_1.1". Both shared models have 2 configurations.
Konfig_1_mitte:

PB_9460713_2-1750338370179.png

Konfig_2_oben_rechts:

PB_9460713_3-1750338419721.png

The main assembly cannot display "Bgr_1" and "Bgr_1.1" with different configurations. 

PB_9460713_0-1750336986185.png

By merging or activating configurations both sub assemblies "Bgr_1" and "Bgr_1.1" can be displayed either in configuration "Konfig_1_mitte" or "Konfig_2_oben_rechts". 

The product idea is the possibiliy to merge different configurations of shared assemblies. So you are able to display the main assembly "Layout" like:

PB_9460713_1-1750338032780.png

 


2. Are you using a workaround?
There is no workaround.

3. What is the use case for your organization?
We develop configurable machines with automations. Machines can be assembled different to the automation, but being the same machine. Therefore we use the configuration to display the different mounting positions a customer can choose from. If a customer wants 2 machines but mounted in 2 different ways to the automation system, the visualization can be controlled via the configuration option.

4. What impact does this problem currently have on your organization?
A lot of time needs to spent to place every part with the selective indepent feature. Otherwise we are not able to plan whole smart factories with mutlipe machines in different customer variations.

2回复

Community Manager
6月 19, 2025 2:57 下午 UTC
Status changed to: Acknowledged

Thank you @PB_9460713 for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.