Design Automation

I work with Inventor and one "automation" macro I set up has to do with file naming and BOM information.

I use a definitive file naming convention. It is always as follows:

Part_number Description text [size] (comments)

This information is parsed by some VBA code to automatically fill in the parts list or BOM.

The part number is always first and is delineated by the first space in the file name. If the part number has a space it is replaced by an underscore _. The VBA code replaces the _ with a space.

The description comes next. All text after the first space is considered part of the description unless it is enclosed in brackets [] or parenthesis ().

All text in brackets [] is considered the size information. Generally I only include the size information for purchased parts that will never change size. The size of a fabricated item is seldom known at the time of file creation and may change with future revisions so size is omitted in the file name. The size of fabricated items is filled in manually later using the macro user interface.

All text in parenthesis () is considered a note and is completely ignored. This is helpful for flexible parts like a timing belt where each version may have a different shape but exactly the same part number, description, and size information. Each version can have its own uniquely named file by changing the note text.

If the parent directory contains "\VENDORS\" then the part is considered a purchased item and the vendor name is parsed from the directory location. Depending upon whether there is a vendor called out will determine if the part is a Make or Buy.

An example might be something like this:

...\VENDORS\MECHANICAL\MK PROFILES\54.40_1800 LIGHT EXTRUSION [40mm x 40mm x 1800mm Long] (cut at 45°)

PART NUMBER = 54.40 1800

DESCRIPTION = LIGHT EXTRUSION

SIZE = 40mm x 40mm x 1800mm Long

VENDOR = MK PROFILES

Make_or_Buy = B

Using this file name format and the related VBA code results in very accurate and consistent BOM information. The user interface for the VBA code is set up such that the default information parsed from the file name is presented but it can be over-ridden or ignored as desired. I have been using this macro and file naming convention for about 15 years and in the long run it has saved a tremendous amount of time and trouble.

I would suggest others adopt a similar file naming convention even if they don't have macro system to take advantage of it.

The VBA code and my BOMs use a few custom iProperties. These custom iProperties are automatically created or deleted by the VBA code as required.

Be happy to share the VBA code if anybody is interested.

Thanks,, I have deleted