Working with and without vault

Working with and without vault

MikeKovacik4928
Advisor Advisor
4,201 Views
26 Replies
Message 1 of 27

Working with and without vault

MikeKovacik4928
Advisor
Advisor

Hi All

Opinions needed here.

I am now working in Vault for almost 4 months.

In my 10 years with Inventor this is only the 2nd time with vault, the first time about 7 years ago for a short 

period of less than a year.

 

It seems to have a lot of nice features, but it is very time consuming and sometimes very slow.

Where I am now, it is definitely here to stay, I am just wanting opinions of people who have worked 

in both scenarios, with and without vault.

 

What do you find have been the advantage and disadvantages of working with Vault.

Do the Advantages outweigh the disadvantages?

I am tending to think that they do.

 

Mike Kovacik

Inventor Pro 2020

Vault Pro 2020

South Africa

 

 

0 Likes
Accepted solutions (3)
4,202 Views
26 Replies
Replies (26)
Message 21 of 27

IgorMir
Mentor
Mentor

Hi Greg,

Thanks for asking. Here is a brief description on the file structure I use. This is a copy of the post I made some time ago.

 

"The first thing I can tell about file management is that it requires a strict discipline, exercised by everyone who is dealing with given set of files. And that's probably the hardest part to enforce!

As for the naming convention - I can offer you to look at a system I use for. It works for me very well for more than 20 years.

 

  1. Each and every client has its folder set up on my computer. And the folder is named after the client's business name - not some numbers such as the date, when the folder was created.

 

  1. 2. In that folder there are subfolders related to the client's projects. Again, named after              the project name - not any ambiguous numbers no one can explain at a glance.

 

  1. In each and every project folder there are always some folders, named "Ga" - for General    arrangement drawings, "Assembly" - for assembly files, "Details" - for individual parts drawings. Plus - some others, created by Inventor, when dealing with iParts.

 

  1.  Now, for the file naming. To start with - I have a spread sheet for each client, where I record the   projects, I have done for him. They are recorded in consecutive order, starting from 01. The files with 01 index are reserved for the standard parts, pertaining to this client only. These files can be used thought all of the projects for this client. They are, in effect - library parts for this particular client.  I can give more detailed explanation of it later, if needed. For the time being - let's continue to talk about the naming convention itself.
    Say, I have 45 entries for the client. Then all the files, related to his last project will have number 45 as a first digits for each and every drawing related to that protect, Assembly file will be named 45-ga, part files are named 45-01, 45-02 and so on. 

 

45-ga file - is a main assembly file. It usually contains sub-assemblies in it. The sub-assemblies are named 45-1ga, 45-2ga and so on. And the part numbers for each sub-assembly will be 45-1-1, 45-1-2, or 45-2-1, 45-2-2 for the second sub-assembly. And so on.

 

Some of the parts in assemblies (and sub-assemblies) can be iParts. Then their numbers will be 45-1-1-1, 45-1-1-2, 45-1-1-3 if the iFactory is a part 45-1-1.

 

Some of the projects can be fairly large and to keep all the parts files in one location could be inconvenient. Then I add some sub-assembly’s folders in main project folder and put all the files, related to that sub-assembly in there. The folder is named with meaningful name, of course. And that name is although shown on the title block of every drawing, related to that assembly.

 

To summarize:

The drawing name consist out of four groups of digits:

  1. General project number.
  2. Assembly number. Project number, following by "Ga" letters.
  3. Part number for the specific assembly. "Ga" letters are dropped from the part's name. If the part belongs to the main assembly - then it's number will be 45-01, 45-02....45-023. If the part belongs to a sub-assembly – than it will look like 45-1-…, 45-2-…, etc.
  4. iParts indicators.

 

I do avoid using idle numbers in file names as much as possible. What is the point to use 001 or 002 as a prefix to the file name? The first Zero will expire only after 99 projects you will get done. Until than - these digits will only take space in a title block without adding any valuable information.

 

The drawing number and the part number are the same. It is although true for the General arrangement drawings.

 

I always keep in mind that my drawing is used by a person, who doesn't have access to my file system. All he has - is a hard copy of my drawing in his hand. When he is on the phone with some queries regarding the drawing - he can only tell me the drawing number and the name of the project - as it's written in the title block. And with the system I use it is enough info for me to find that file on my computer almost instantly - no matter how many years are gone since that project."

 

Best Regards,

Igor.

Web: www.meqc.com.au
Message 22 of 27

cadman777
Advisor
Advisor

Igor,

 

I use a similar system.

Common sense that make sense.

 

The difference is, I use the creation date as the ProjectNumber, preceded by 2 letters to identify the customer.

Then I use a segmented number for Assembly.Subassembly.Detail-RevisionNumber. The Assembly.Subassembly.Detail is arranged by category and consecutive creation to keep from running out of numbers. No wasted place holders, no stupid numbers, no confusion.

 

For example, if you were my customer, the top level DrawingNumber/FileName for a project that started today would be: IM.2021.11.11-00.00.00-00

 

But sometimes I've had to use the customer's numbering system, which can be a PITA.

But when it's required, I use it.

 

Cheers...

... Chris
Win 7 Pro 64 bit + IV 2010 Suite
ASUS X79 Deluxe
Intel i7 3820 4.4 O/C
64 Gig ADATA RAM
Nvidia Quadro M5000 8 Gig
3d Connexion Space Navigator
0 Likes
Message 23 of 27

IgorMir
Mentor
Mentor

Hi Chris,

That's what it boiling down to - a common sense.

BTW - I did use the idea of naming client's folder after the date it was created. In couple of months time that very client called me up and asked, if I can refresh his memory on some details for the project I have done for him. He was telling me - it was for Armadale Hospital. He just needed to check some measurements while being on site. He didn't have any drawings with him, but he knew - the drawings were for the Armadale Hospital!  And I couldn't find that very folder on a spot. I didn't remember - when the project started. After that incident I had immediately renamed all the folders of his to meaningful names. So, next time I didn't have to ask him - when the project had started! Now I have "Armadale Hospital" folder as a subfolder in his directory. 

If I want to see the date a project began - I can always look it up in a corresponding spread sheet. 

 

If you were a client of mine - the first top assembly file name would be 02-ga.iam. And the drawing for that assembly would be named 02-ga.idw. I might have tens of files in the system named 02-ga.iam. But they never get confused or mixed up. Because each of them belongs to a specific client. So, you won't get a file 02-ga.idw from me, which belongs to Rio Tinto, for example. 🙂 You will get a file 02-ga.idw which belongs to you!

Looking at some mile long files names, which I come across every now and then - I can't help but to miss the DOS days. When the file name was limited to 8 characters only.  That sure thing made people think how to name the files properly. Nowadays - new generation of drafters put a personal biography in the file's name. Well, almost. Because they can. 

 

Cheers,

Igor. 


@cadman777 wrote:

Igor,

 

I use a similar system.

Common sense that make sense.

 

The difference is, I use the creation date as the ProjectNumber, preceded by 2 letters to identify the customer.

Then I use a segmented number for Assembly.Subassembly.Detail-RevisionNumber. The Assembly.Subassembly.Detail is arranged by category and consecutive creation to keep from running out of numbers. No wasted place holders, no stupid numbers, no confusion.

 

For example, if you were my customer, the top level DrawingNumber/FileName for a project that started today would be: IM.2021.11.11-00.00.00-00

 

But sometimes I've had to use the customer's numbering system, which can be a PITA.

But when it's required, I use it.

 

Cheers...

Web: www.meqc.com.au
0 Likes
Message 24 of 27

greg.youngCXLLN
Advocate
Advocate

Hi Chris, thanks for sharing. 15 years ago, I worked in an office without Vault, we had 27 Design Drafters... There were a few times where people saved over each others work, and it almost came to fisticuffs. Common Sense is good to have, and most of the guys were pretty good, but it only takes 1 or 2, to make a bit of a mess.

They have a pretty good naming convention here, and have a lot of work done in AutoCad and their Lead Drafty is old school and very strict on naming.  The challenges I see is library & Content Centre and Copy Design. I have used Design assistant previously but that doesn't come close to Vault's Copy Design. 

Message 25 of 27

BDCollett
Advisor
Advisor

@greg.youngCXLLN wrote:

Hi Chris, thanks for sharing. 15 years ago, I worked in an office without Vault, we had 27 Design Drafters... There were a few times where people saved over each others work, and it almost came to fisticuffs. Common Sense is good to have, and most of the guys were pretty good, but it only takes 1 or 2, to make a bit of a mess.

They have a pretty good naming convention here, and have a lot of work done in AutoCad and their Lead Drafty is old school and very strict on naming.  The challenges I see is library & Content Centre and Copy Design. I have used Design assistant previously but that doesn't come close to Vault's Copy Design. 


If 2 of those 27 can make a mess with Vault, I could only imagine the possible mess they could make when the system was just spreadsheets and folders managing the data. At least with Vault it's not too painful to go back and recover older versions if what you said happened.

It's often a lack of good administration that leads to problems.

0 Likes
Message 26 of 27

greg.youngCXLLN
Advocate
Advocate

I said that was "without" Vault... they had to use Old Versions to recover work. I am a fan of Vault and it would definitely be my choice, if the choice was mint to make

0 Likes
Message 27 of 27

BDCollett
Advisor
Advisor

@greg.youngCXLLN wrote:

I said that was "without" Vault... they had to use Old Versions to recover work. I am a fan of Vault and it would definitely be my choice, if the choice was mint to make


Sorry I missed that part! Completely agree.