auto numbering, folder structure & finding things

[Winks87]

I am looking for feedback from current auto numbering users for how you implemented a simple numbering scheme but still are able to find parts and assemblies easily in Vault.  Do most of you have a complex folder structure or do you use the search functions in Vault?  When searching, you have to rely on all of the information to be present in the files.  Data Standard for that?  If you are looking specifically for a part such as a C8 channel that is part of a large weldment, do you rely on trhe search functions?  I am a little OCD about standardizing info and really want to have all bases covered before implementing auto numbering.  We currently have a complex manual scheme that is not reliable, much less used correctly across the board.  This needs updated.  So if I create a simplified scheme that does not relay the part info via filename, I need to make sure folks can find what they are looking for.  Sorry for the long explanation, just looking for feedback.  By the way, we have several product lines, various cost codes in file naming, shop fabrications and field assembly/installations... alot to organize.  Any ideas and or help would be...helpful.

[PaulMunford]

my preference would be to use autonumbering out of the box and use search folders to find your parts. I'm a big fan of keeping folder structures to a minimum!

This relies on your team filling out all the key fields in your part files. This can be made easier with pre-filled out templates and iLogic.

You could use concentated fields to give you human readable part numbers.

You can go a step further by using Vault data standard or iPropWiz if you don't want to code it all yourself.

I'd be curious to know what everyone else thinks!

[Winks87]

Yes, that is what I was thinking.  I was considering the folder structure -vs- Data Standard.  I am illiterate with iLogic so I was leaning towards the Data Standard to provide necessary iproperty information.  Thanks for the reply sir!  I too would also like to hear what folks have to say...

[swalton]

We use "smart" part numbers with Vault's Number Schemes.  We enforce unique filenames, filename=partnumber and one part number per idw file.

The numbers are formatted as follows:

AAABB-CXXXX

AAA= Three letter code for each machine type

BB= Two Digit code for each machine built.  01 for the first one, 10 for the 10th, and so on.

C=1 digit code for the model type: Assembly, Weldment, Hydraulic Component, Part, Purchased Part, etc

XXXX=4 digit sequential code.  Starts at 0000, goes to 9999.  We usually don't get beyond 2500 or so.

We build a new Number Scheme for each AAA machine.  We use a drop-down for BB and C.  Vault pulls the next XXXX number as required.

The folder structure looks like this

AAA

   AAABB

     10000

       Component Files

     20000

       Component FIles

     30000

       Component Files

     ....

It repeats for each combination of AAABB that we have created.  The folder structure does not go too deep and we don't see more than 5-6k files in the lowest sub-directory.

Descriptions are added as the design goes from concept to final assembly. 

Manufacturing data is stored in flat directories by file type.  One directory for .stp files, one for .pdfs, etc.

I usually search by part number, sometimes by description.  It depends on what I know about what I am trying to find.

[brendan.henderson]

As an 'engineer to order/job shop' business we don't use Vault numbering schemes for the parts we make, but we do use them for CC and FG and Bolted Connections and the like.

Our file structure is XXXXX-YYYYY. XXXXX = the project number e.g. 38095 which is the container for all of the project details, the purchase orders, the cists, etc... YYYYY is the CAD file structure.

We make a folder called 38095-DEBTOR where debtor is the customer code from our accounting package. Inside that folder are all of the CAD files in the same 10 digit format, so 38095-00000 is the top level assy file, 38095-01000 is the 1st child assy of -00000, -01001 is the first child part of -01000. 38095-02000 would be the 2nd child assy of -00000, -02100 would be the first sub-assy of -02000, -02101 would be the first child of -02100. This gives us plenty of room for even very large projects. We have never yet run out of numbers even on 30000 part top level assy files.

The folder structure looks like this :-

38095-DEBTOR

   38095-CC

   38095-00000.iam

   38095-00000.idw

   38095-01000.iam

   38095-01000.idw

   38095-02000.iam

   38095-02000.idw

   38095-02100.iam

   38095-02100.idw

   39085-02101.ipt

   38095-02101.idw

The 38095-CC folder is a container for all CC anf FG and Bolted Connections and Design Accelerator files, as do phantom parts and FG sketches and the like, most of which use a Vault numbering scheme which directs these files to a lifecycle scheme. This folder/file structure keeps the project folder looking lean and mean as we only see the important data, the stuff we make. All FG member sand CC parts are saved as Custom and put into the -CC folder to keep them out of 'general population' as they rrely need to be seen.

Each iam or ipt file in the Project folder gets an idw file of the same name as the iam or ipt.

We do similar for all bought parts (bolts, bearings, steel members, sprockets) where we also use a 10 digit scheme of AAAAA-BBBBB. AAAAA=the type of part as we have them sorted into groups e.g. 00100 is TRANSMISSIONS (motors, gearboxes, PTO shafts), and BBBBB is the individual part e.g. -20103. AAAAA is further divided into smaller groups so 00111 is bearings, 00112 is bearing housings, 00117 is gears, etc. BBBBB just starts at 00001 and increments by 1 at a time. Bolts are 00401, decals are 00823.

The 2 similar file naming schemes allows us to seperate BOUGHT from MADE. If the first 5 numbers are 01000 or higher we make it. If its 00999 or less we buy it. We use this with a series of code driven spreadsheets we produce to go with the drawing set which really makes ordereing and part verification and counting easy.

We heavily customised the CC so that all of the bolts, washers, bearings, steel members, circlips, etc. all have STOCK CODES (iProperty Stock Number) and these match with or ERP system. Basically evertyhing in the standard CC that we use we copied to a Read/Write library and changed as we needed, and we also published a tonne of our own equipment into the CC.

Finding things in Vault is a breeze. As each project gets a specific folder the data for that project is in that folder. We then search by Title and Description for what we are looking for. We also have several Custom Views in Vault to simplify things such as a Sheet Metal part filter than only shows all of the parts created with the Sheet Metal.ipt template (whicis 60% of our business so very important).