Part State/Version management for Wire use in flexible assembly

Hello,

In a CAD-centric configuration (Windchill 12.0.2.8+SolidWorks), to handle “wire” and similar component with multiple representation, we use the Flexible Assembly method and its fine...until we need to Released this Part in order to Released a Product (EBOM) while other CAD Team also use this Part to work on the design of other products (EBOM)…

As soon as we need to do a Change notice, I fear that the problems will start :

• Who across the different CAD Team is responsible of this Change notice is not clear.

• The Change notice will be open during a longue periode.

• Change request coming for released product or on the document of this Part will leads to the need to modify and Released this Part while other new CAD linked to this Part for new product are still not approved.

How to manage properly the lifecycle and change management of the “Wire” Part (EBOM) using the Flexible Assembly method?
(We have MBOM with no CAD, visualization for MBOM is based on the BOM structure and the occurrence link to the EBOM)

For example:

• Customization to be able to add or remove on a Released Part new (or just new non-approved) CAD with image association without versioning the Part or change the State.
  Change during the assembly after a CAD is approved will result, in the history of the Wire Part, of a mix of change coming from definition of the wire and its integration in their multiple Parents. Existing CAD maybe deleted by mistake.
  => Quality and PLM Administrator will not like.
• Leave the Flexible Assembly method, instead, each “path” (Occurrence) of the wire have a distinct CAD assembly owner of a gathering Part, containing :
  - The same child CAD linked in owner to the Part of the “Straight” Wire but without volume.
  - An another child CAD, representing the wire folded to the “path” of this occurrence, with a image link to the Gathering Part of the assembly.
  Change on the Wire and change of the Path of the Wire in the assembly are dissociated.
  => Designer will not like (Big assembly), but manufacturing will enjoy to not have to repair occurrence link resulting of multiple split of usage link!

Can we have a CAD contributing to the structure of his Parent Part sharing a visualization for his owner Part but not sharing a volume in the visualization of the Parent Part structure in Windchill ?

Thanks !