7 questions regarding configuration management using the Item Master in Autodesk Vault Professional

[antonm]

1. By default, the Item Master module is organized in a flat structure. When working with a large number of items, this can be inconvenient, as it does not clearly represent parent-child relationships. Currently, the hierarchical structure is only available in the BOM tab of the item window, which requires additional steps to view. Is it possible to display the hierarchical structure of items, with folder support, directly in the main Item Master window?

2. How is the relationship between file lifecycles and item lifecycles configured? Is it possible to use both file lifecycles and item lifecycles within the same project? Is it necessary to stop using file lifecycles and switch to item lifecycles? Because the transition of an item through its lifecycle affects the ability to edit the files linked with it.

3. For example, I add an additional file to an existing item using the «Insert File» command. Then I modify this file, but the item icon does not indicate any change. Are there any configuration settings to resolve this issue?

4. How can a relationship be created between manually created items? For example, there is a new item linked to an assembly file, and another new item linked to a part file (the part is a child component of the assembly). By default, no relationship exists between these two items. It is necessary to update every item by hand.

5. Are there implemented practices for using Items to manage product configurations?

6. Is it possible to control the transition of an item to the «Released» state only after all child items have been released?

7. When making changes to a project, should the Engineering Change Order be issued for the item or for the file? What is the correct sequence of implementation of this process?

[ihayesjr]

1. No, the item master doesn't have a folder structure, and the BOM is intended to display the hierarchy.
2. Item and File Lifecycle definitions work independently from each other. One does not trigger the other.
   It isn't recommended to have both the Item and File lifecycles control the security on files. They should remain separate. It is not necessary to stop using one to use the other.
3. Items are associated with a specific version of the file. If you create a new version, you need to perform an Update Item for the Item to use the latest version. There are other status indicators if the Item is out of date.
4. You update the assembly only. Items are created from the Inventor BoM. Therefore, the assembly's BoM will update the link automatically to show the association to the child.
5. You cannot use Items for product configurations; that is a PLM function, not a PDM function.
6. Yes, this is the transition settings in the lifecycle definition
7. The correct process is up to you. The software doesn't dictate this.

[ihayesjr]

Here are some AU classes that you should review.

All You Want to Know About Items in Vault Professional | Autodesk University

Item-Centered Vault: Best Practices and Tips for a Smooth Transition from a File-Centered Vault | Au...

Itemize Your Life with Autodesk® Vault Professional | Autodesk University