<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Managing Competing Design Variants in Vault Forum</title>
    <link>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10198999#M16598</link>
    <description>&lt;P&gt;&lt;a href="https://forums.autodesk.com/t5/user/viewprofilepage/user-id/113378"&gt;@swalton&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I became the Vault admin, that was the first setting I enforced.&amp;nbsp; The situation I described had occurred years earlier, in the infancy of Vault.&amp;nbsp; At the time it was being used as a simple check in/check out system.&amp;nbsp; I don't think those who were doing these prototypes could foresee the problems it would create down the road.&amp;nbsp; It was discovered when a designer opened a part from the assembly to make a simple change, and then opened the part drawing to add the revision... only to notice his change was not there.&amp;nbsp; The part file inserted into the assembly was not the same one from which the drawing was created.&amp;nbsp; Looking deeper it was found that the same part file, with the same name existed in six different locations.&amp;nbsp; Once the rabbit hole was discovered, it took months to get everything straightened out.&amp;nbsp; Since those days, unique filenames and copy design became our good friends.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 30 Mar 2021 13:37:15 GMT</pubDate>
    <dc:creator>CGBenner</dc:creator>
    <dc:date>2021-03-30T13:37:15Z</dc:date>
    <item>
      <title>Managing Competing Design Variants</title>
      <link>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10189673#M16594</link>
      <description>&lt;P&gt;Hi all,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm curious to know what others are doing to manage projects with multiple competing design variants in Vault. The product that I'm actively developing has reached a point where two competing variants are being actively developed at the same time. Only one of the two versions will ultimately go to manufacture. Is the best way to deal with this just to create a copy of the part file for each variant that is being actively developed and then shelve all unused variants once one is chosen for manufacture? Ideally I would use a branch like git has, however that feature isn't supported in Vault right now. I'm curious to know how others with more experience than me handle this sort of situation in Vault.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Dylan&lt;/P&gt;</description>
      <pubDate>Fri, 26 Mar 2021 15:29:10 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10189673#M16594</guid>
      <dc:creator>dylanTEV9W</dc:creator>
      <dc:date>2021-03-26T15:29:10Z</dc:date>
    </item>
    <item>
      <title>Re: Managing Competing Design Variants</title>
      <link>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10197162#M16595</link>
      <description>&lt;P&gt;We use independent top-level assemblies for each design.&amp;nbsp; Any parts or sub-assemblies that have the same-form-fit-function can be reused.&amp;nbsp; Anything that needs to be different is Copy-Designed with Vault and then replaced in the proper top-level assembly.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Some folks use a method like different part numbers/filenames or Lifecycle states to identify the in-production version at the end of the development process.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I suspect it would take a complete re-design/new program to make Vault understand and merge design variants.&amp;nbsp; Inventor might have to be re-written too.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Mar 2021 20:30:18 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10197162#M16595</guid>
      <dc:creator>swalton</dc:creator>
      <dc:date>2021-03-29T20:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: Managing Competing Design Variants</title>
      <link>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10198593#M16596</link>
      <description>&lt;P&gt;&lt;a href="https://forums.autodesk.com/t5/user/viewprofilepage/user-id/6661176"&gt;@dylanTEV9W&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I like the copy design method as well, and one thing I would caution (because I ran into it at an old job), is to keep the competing part files in separate locations, with different file names, and make sure everyone knows the system.&amp;nbsp; In an old job, we ran into a situation very similar, where they simply copied the part over and over and used the same file name.&amp;nbsp; Some of the parts didn't actually end up changing geometry.&amp;nbsp; So,... in the final design assembly, sometimes the correct part was not used, and to make it worse... the part which was used for the final fabrication drawings was not the one used in the final assembly!&amp;nbsp; So years later when we went to change a shaft, for example, those chnages were NOT in either the assembly or the shaft drawing that went out to the vendor!&amp;nbsp; Only then did we figure out that the shaft part lived in six different locations.&amp;nbsp; It took a day to figure out which of those was used in the drawing, and which was in the assembly.... opening that can of worms ed to nearly three months of cleaning up these prototype folders and designs, and archiving dozens of unused copies!&amp;nbsp; My head is spinning just thinking about it.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Mar 2021 10:46:31 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10198593#M16596</guid>
      <dc:creator>CGBenner</dc:creator>
      <dc:date>2021-03-30T10:46:31Z</dc:date>
    </item>
    <item>
      <title>Re: Managing Competing Design Variants</title>
      <link>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10198976#M16597</link>
      <description>&lt;P&gt;&lt;a href="https://forums.autodesk.com/t5/user/viewprofilepage/user-id/9248770"&gt;@CGBenner&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One of the great joys of Vault is the "Enforce Unique Filenames" setting.&amp;nbsp; Add the Numbering Schemes in the paid versions of Vault, and one never has to double-entry part numbers/filenames in Inventor and an external database.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As I'm sure you know, enabling that prevents the issue you describe with the same filename used for different geometry.&amp;nbsp; I suspect that your former company had disabled that setting.&amp;nbsp; What kind of workflows did you have where it was helpful to allow duplicate filenames?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Mar 2021 13:27:57 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10198976#M16597</guid>
      <dc:creator>swalton</dc:creator>
      <dc:date>2021-03-30T13:27:57Z</dc:date>
    </item>
    <item>
      <title>Re: Managing Competing Design Variants</title>
      <link>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10198999#M16598</link>
      <description>&lt;P&gt;&lt;a href="https://forums.autodesk.com/t5/user/viewprofilepage/user-id/113378"&gt;@swalton&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I became the Vault admin, that was the first setting I enforced.&amp;nbsp; The situation I described had occurred years earlier, in the infancy of Vault.&amp;nbsp; At the time it was being used as a simple check in/check out system.&amp;nbsp; I don't think those who were doing these prototypes could foresee the problems it would create down the road.&amp;nbsp; It was discovered when a designer opened a part from the assembly to make a simple change, and then opened the part drawing to add the revision... only to notice his change was not there.&amp;nbsp; The part file inserted into the assembly was not the same one from which the drawing was created.&amp;nbsp; Looking deeper it was found that the same part file, with the same name existed in six different locations.&amp;nbsp; Once the rabbit hole was discovered, it took months to get everything straightened out.&amp;nbsp; Since those days, unique filenames and copy design became our good friends.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Mar 2021 13:37:15 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10198999#M16598</guid>
      <dc:creator>CGBenner</dc:creator>
      <dc:date>2021-03-30T13:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: Managing Competing Design Variants</title>
      <link>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10203065#M16599</link>
      <description>&lt;P&gt;Thanks for sharing, I like the idea of independent top level assemblies. I still wish I could have separate branches for different design variants of parts but I understand that this is a technical limitation of how the Vault was written. I'm holding out hope that Autodesk could add this feature at some point in the future.&lt;/P&gt;</description>
      <pubDate>Wed, 31 Mar 2021 21:03:24 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vault-forum/managing-competing-design-variants/m-p/10203065#M16599</guid>
      <dc:creator>dylanTEV9W</dc:creator>
      <dc:date>2021-03-31T21:03:24Z</dc:date>
    </item>
  </channel>
</rss>

