Assembly file version control

Assembly file version control

f_calebh
Advocate Advocate
776 Views
4 Replies
Message 1 of 5

Assembly file version control

f_calebh
Advocate
Advocate

If a user is referencing the assembly of a product that's produced by the company's development group.  (This assembly file is in an approved state (locked) for production.)

How does the user prevent this assembly from updating it's part versions until those part versions are released?

Potentially a user in the design group pulls a new lifecycle on a component being referenced in the approved and locked assembly.  Even if this design user doesn't change the state (unlocked state) of the assembly that's using it, the assembly reference will still show updated changes made to the component the designer is editing. 

 

Do I have settings I need to update? Or is there something I'm missing as it relates to controlling released 3D model references?  How do we keep approved assembly models from reflecting conceptual changes to parts/subassemblies before their ready?

 

0 Likes
Accepted solutions (1)
777 Views
4 Replies
Replies (4)
Message 2 of 5

ihayesjr
Community Manager
Community Manager

If I understand correctly, your assembly is Released but using parts that are still in Work in Progress. I am also assuming you are using either Vault Workgroup or Vault Professional.

 

If my understanding is correct, the parts that the assembly is using needs to be in the released state also. That way it can be pulled from Vault with the Released parts that it is referenced.

 

For example, the assembly and part are in Revision A. If another user needs to edit the parts, they change the state of the part to Work in Progress with will bump the revision to Revision B. The assembly can be pulled from Vault and only see Revision A until Revision B is Released. If you want the Assembly to use Revision B of the part, you need to put the assembly in Work in Progress which will change it to Revision B and you will need to pull and use Revision B of the part in the assembly.

 

Please correct me if I have the wrong understanding.




Irvin Hayes Jr
Principal Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
Message 3 of 5

f_calebh
Advocate
Advocate

Yes, that's what I would like, but I'm not seeing it work that way. I put an example together with some snapshots:

Here an example of a product assembly that’s in an approved and locked state:

f_calebh_0-1612897971902.png

 

It’s possible a designer may decide to work on some concepting in a particular part or subassembly file that’s being referenced:

f_calebh_1-1612897971904.png

 

 

 

At the same time, the Equipment group could be working on their equipment file that references the Product Design.iam but what I’m seeing, is that even though I’ve selected the approved version of the assembly:

f_calebh_3-1612897971911.png

 

The concepting modifications to that component are still updating:

 

f_calebh_4-1612897971918.png

 

 

 

0 Likes
Message 4 of 5

ihayesjr
Community Manager
Community Manager
Accepted solution

Click this drop-down menu and select Revision 0.

ihayesjr_0-1612971363224.png

 




Irvin Hayes Jr
Principal Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
0 Likes
Message 5 of 5

f_calebh
Advocate
Advocate

OK, that does the trick.  I'm guessing that once the approved assembly is updated, that reference will update, even though I didn't select "latest"?  

0 Likes