Adding inventory codes to parts.

Adding inventory codes to parts.

jaquesV8U9M
Explorer Explorer
267 Views
3 Replies
Message 1 of 4

Adding inventory codes to parts.

jaquesV8U9M
Explorer
Explorer

Hi Guys

 

I work for a company with over 4,000 part files (.ipt) and about 1,000 assembly files (.iam).

 

We recently got tasked with adding stock codes and linking price values to all parts.

 

Our current method is:

  • Opening the iProperties of each file and copying the part name.
  • Pasting this in a shared SharePoint spreadsheet, which then auto-generates a stock code.
  • Copying and pasting this stock code in the file's iProperties under "Stock Number."

 

With this method, there are all kinds of problems: duplicate codes being used, previous revisions of parts with the same codes, Content Center parts not updating, etc.

We think Vault is the way to go, but since none of us have used it before, we're not sure if it will be any help. Is there a way Vault can help us do this better/faster?

 

Hoping someone can point us in the right direction or give some advice. Thanks!

 

Using Inventor 2025, on the Product Design & Manufacturing package.

0 Likes
268 Views
3 Replies
Replies (3)
Message 2 of 4

Dev_rim
Advocate
Advocate

I dont know too much about vault. But we storing information on files we are using Attribute Sets. I don't know it it fits your expectations but its possible to filter files by using them and it also allows you to store every type of information. To view them you need to download attribute helper. I am sharing the articles about Attribute Sets.

 

You can download Attribute Helper from here:

https://modthemachine.typepad.com/my_weblog/2013/08/attribute-helper-update.html

 

Tutorial for it:

https://modthemachine.typepad.com/my_weblog/2009/07/introduction-to-attributes.html

 

I hope it meets your expectations.

 

Best

Dev

If my answer is solved your problem, please mark it as Solution

Freundliche Grüße / Kind Regards
0 Likes
Message 3 of 4

daltonNYAW9
Advocate
Advocate

I've used both vault and single project files. Personally I like the using a regular project file b/c it's more flexible if you know how to use it properly. But... inevitably... someone will mess it up, or file references get messed up, etc.

Advantages to vault:
1. Track revisions. Just from a documentation standpoint this is easy and useful.
2. Virtually no file reference errors. It can act as a fool-proof
3. Excuse to reform your file structure

2 and 3 are band-aid cures (as are most other vault functionalities imo). Vault doesn't fix all of inventors problems, just makes it easer to "manage".

 

As for your questions...
Vault can 'enforce unique filename' and generate custom naming schemes, but it doesn't affect the 'stock number'.

You could setup a rule that automatically checks an external excel file for the stock number info, creating it, and updating the price with the 'GoExcel' functionality . This may be difficult to keep up with.

This whole process of setting up unique stock numbers seems taxing for an engineering team. But I'm a lazy engineer so maybe thats just me haha.

0 Likes
Message 4 of 4

mgaunt3DSG
Enthusiast
Enthusiast

Probably not everything you're looking for, but you could create a temporary Assembly that you place the components you need to modify into and use the Bill of Materials to edit the Stock Number.  You can copy-paste values into the table like you would a spreadsheet, so should speed you up a bit.

It won't, however, work on Content Center Parts.

0 Likes