Comparing traditional product revision to Configured evolution on the 3DExperience platform

Video demonstrates the ease of change to a product structure when it is configured on the 3D Experience platform compared to traditional clone and re-identifying techniques.
🔔Don’t forget to subscribe : / @dassaultsystemes
🔔Dassault Systèmes official website : www.3ds.com/
🔔Learn more about what Dassault Systèmes do : www.3ds.com/ab...
🤳 Follow us! 🤳
Linkedin: / dassaultsystemes
TikTok: / dassaultsystemes
Instagram: / dassaultsystemes
Twitter: / dassault3ds
Facebook: / dassaultsystemes
#productstructure #Configuration #Productevolution #150percentBOM #SuperBOM #Variantmanagement

[@chwak1601]

Really helpful, thanks! Could you maybe go into detail on how the variant dictionaries you mentioned are treated with regards to releasing certain configurations of a product? How do I maintain a 150% BOM and yet derive variants from it that I can then release?

[@zenjinc]

@chwak1601, The 3D Experience platform has a concept called design branching. You can create a branch from the current variant dictionary that goes along to live its own lifecycle. A typical use case is if you want to create a one time product specifically for certification. You can branch the root dictionary and add the pertinent details to the certification variant to include items like test rigs information, specific component designs appropriate for certification sought and the like.