Hopefully as far as effort goes, this shouldn't be too bad.
In Vault Administration Settings, there's an option to 'restrict item lifecycle changes to change orders'.
I get this, it's useful, we don't want people changing Item lifecycles willy nilly.
However, when this is enabled, I'm forced to raise an ECO to release an Item for the first time at revision 0. Why? Well because it's a lifecycle change, so the settings impacts it. Yes but it shouldn't, not on this particular lifecycle change.
I can only summise that this is a mistake, someone implemented the functionality but didn't understand the engineering change process. Under no circumstances do you raise an ECO to release an Item that hasn't been made yet. It's revision 0, it's new, brand new, being forced to raise a 'change order' against it just so I can release it is... it's a mistake, an error, please change this. I'm sick of trying to explain why this needs to happen to hundreds of engineers who are as confused about it as I am, and I don't have an answer for them.
Items are rubbish. They're a necessary evil for linking to ERP but in general they're a hindrence.
I could write a Harry Potter sized novel on how to overhaul items, but primarily the main issue I'd like to see improved right now is:
Item version visibility.
Basically, there isn't any. I could create an Item right now, spend an hour building a BOM structure, save and close it. Someone else could then open then Item, trash my BOM completely, save and close the Item. I could then open the Item, do something else in there, and anything that has happened previous to me doing something is completely lost in time. There is no traceability as to what happened prior to me just saving the Item.
I'm annoyed because this has just happened. One of my users swears blind he included a part in an Item BOM a few weeks back, this was then released and auto-flung out to ERP world. The shop orders have been raised, and there is no mention of this part, and it's quite an important part. So I look at the Item, the part isn't there. Is this user error? Did he just not include it in the first place? Did someone else delete it? Was it there for a few days but then someone removed it? Who knows!
What's that someone within Autodesk once famously said and has plastered all over their blog site? The Vault knows all? Well then feel free to share this knowledge because when something like this happens it's a frustrating mystery.
Oh, wait, there's a calendar on the BOM tab! Ahhh that must show me what the BOM state was like on a specific date! Nope. Doesn't work.
Please fix all of the above, make Items more workable.
Re: Inventor 2014 It would be nice if the Vault file open dialog box included the preview picture like it used to in version 2013 (instead of the 'search')? The regular file open has it. An option to toggle one way or another would be great.
Using 'large icons' almost works but normally I've got a lot of files to look thru so I want to get in the area quickly (using 'list' view), then step thru the 3 or 4 candidates, figuring out which one I need.
Currently it takes 8-9 clicks to find and attach a file to another file, like pdf to idw.
Currently it takes 9-10 clicks to find and attach a file to an item, like pdf to item.
multiply this by 50 files and we have a few hours of work ahead of us
for ITEMS, I would like the option to automatically add any existing attachments from the ipt, iam, or idw upon item assignment.
For FILES & ITEMS I would like an "add attachments" command that opens to the find dialog box.
the command should also allow saved searches with filters & prompts like "filename contains" or "checked in by"
also, Both have different command locations. Items attachments is located in the right click menu, files have a paperclip located in the toolbar. They should be consistent in both the toolbar and right click menu.
The ability to save a "proposed" copy design prior to execution would be extremely useful.
For complex assemblies, setting up a Copy Design can be VERY time consuming. If that Copy Design fails, an error message is generated, but then the user has no choice but to start over again.
If you could set up the copy design, save the proposed changes, & then execute it, that would prevent this issue. If a failure occurred, you could simply could re-open the proposed Copy Design, troubleshoot, & then execute it again. This would be a tremendous time saver.
An alternate solution would be this: upon failure, an error message could be generated, & then the user could be returned to the Copy Design process (rather than get kicked out of it)
It is easy to do copy design on CAD files and get new items and BOM, but some of our customers use vault to manage their design with no CAD models or with non-structured CAD files, so it is impossible to use copy design function on their files and promote new items and BOMs.
The only feasible way we found is to export items to a csv file, change the file manually in excel, and then import items with the modified csv file. But I don't think this is a good idea because it is very easy to make some mistake and it is not easy work.
We think a copy design function for items is needed here, it should just like the copy design function on files, we can choose the new item number for the copied item, choose which items to be reused, replaced, or copied as well, together with their attachments.
We also think a SaveCopyAs function for item is very useful in such situation, a new item will be created immediately with the same BOM stucture and same properties, then we can modify the new item as needed.
Currently there is no method to assign the revision scheme duing item creation, including when assigning items to files.
We use two revision schemes... our default is numeric based starting at 0. We use "0" as the released to production revision. Our proposal scheme uses letters and starts at A. The way it is now I create a new item, which is assigned a revision of 0. I save the item and then adjust it to A. This consumes the 0 which cannot be used again. What I'd like to see is the option to select the revision scheme while both creating the item from the item master AND duing item assignment when assigning items to files