Describe how file version and revision history is used to maintain design history.
Transcript
00:00
As a product moves from conception, through development, to completion,
00:07
it is important to maintain a history of all the files and any engineering-related documents.
00:14
Autodesk Vault automatically manages this, using file versions.
00:18
When you initially add a file to the Vault, it is added as Version 1.
00:23
When the file is next checked out, it is temporarily assigned the next version number,
00:28
and the previous version remains unchanged.
00:31
A permanent version number is not assigned to the file until the modified file is officially checked back in.
00:38
If the file is unchanged when it's checked back in, it is not assigned a new version number.
00:43
So, the key thing to remember here is that with each file modification and check-in,
00:48
a new file version is created, and all older versions also remain in Vault.
00:54
In Vault, you can use the History tab to review the recorded history of all the files.
00:60
At any time, you can retrieve any older version of a file.
01:04
This means that if the current design fails, you can go back to a previous design.
01:09
You can also view file properties such as comments about the version,
01:13
who checked it out, when it was modified, and so on.
01:17
The Users tab is also an excellent tool for you to know which version of files are being used in the parent file.
01:25
For example, in the Users tab shown here, the version of the assembly is three, whereas the part file used is Version 6.
01:34
One final term to understand is revisions.
01:38
A revision of a file is a collection of versions with a common label such as A or B.
01:44
It often represents a significant milestone in the design.
01:48
For example, revision A of a new component may consist of 12 versions to get to a point where significant progress has been made,
01:56
and it will be released for 3D printing and testing.
01:59
A new revision B is started, becomes a work in progress again,
02:04
and the file version will keep incrementing.
02:07
Depending on how your administrator has set up and implemented Vault,
02:11
revisions can be done manually, or they can be automatically generated through a lifecycle change.
00:00
As a product moves from conception, through development, to completion,
00:07
it is important to maintain a history of all the files and any engineering-related documents.
00:14
Autodesk Vault automatically manages this, using file versions.
00:18
When you initially add a file to the Vault, it is added as Version 1.
00:23
When the file is next checked out, it is temporarily assigned the next version number,
00:28
and the previous version remains unchanged.
00:31
A permanent version number is not assigned to the file until the modified file is officially checked back in.
00:38
If the file is unchanged when it's checked back in, it is not assigned a new version number.
00:43
So, the key thing to remember here is that with each file modification and check-in,
00:48
a new file version is created, and all older versions also remain in Vault.
00:54
In Vault, you can use the History tab to review the recorded history of all the files.
00:60
At any time, you can retrieve any older version of a file.
01:04
This means that if the current design fails, you can go back to a previous design.
01:09
You can also view file properties such as comments about the version,
01:13
who checked it out, when it was modified, and so on.
01:17
The Users tab is also an excellent tool for you to know which version of files are being used in the parent file.
01:25
For example, in the Users tab shown here, the version of the assembly is three, whereas the part file used is Version 6.
01:34
One final term to understand is revisions.
01:38
A revision of a file is a collection of versions with a common label such as A or B.
01:44
It often represents a significant milestone in the design.
01:48
For example, revision A of a new component may consist of 12 versions to get to a point where significant progress has been made,
01:56
and it will be released for 3D printing and testing.
01:59
A new revision B is started, becomes a work in progress again,
02:04
and the file version will keep incrementing.
02:07
Depending on how your administrator has set up and implemented Vault,
02:11
revisions can be done manually, or they can be automatically generated through a lifecycle change.
