Setting Up Projects\File Structure

[aardvarkdw]

Hey all,

I am reorganizing our file structure and was hoping to get some feedback on how others have their's organized. Currently we are FUBAR, we have three distinct divisions to our company and every one of them has a different method of dealing with this. Each group has their own folder on the network that contains all of their models and files. That being said, we also share many common parts amoungst three groups. Some parts are shared from a common library, some have been copied or recreated and saved elsewhere.

My plan is to consolidate all of our files into a central location, a single folder. My question is, how do you all handle the projects? Do you have a single project file that you work in or several, or one for every "project"(machine, job, etc...)? Do you have seperate folders for everything or just one or two where every file is stored?

Thanks in advance.

David

 

[DesignerMike]

That will be a challenge to say the least.

I'm a one-seat outfit, and I'm on my third configuration.
I'm also using the Vault.

I use the "single promject" method. Here is a link to the "white papers" by Brian

http://discussion.autodesk.com/thread.jspa?messageID=4001448

I don't use any "library" folders since I trust myself to not modify any parts that I shouldn't. You will probably want to use library folders to lock down the files to keep co-workers in different departments from editing a file they shouldn't. You should also consider using the Vault...If done properly it will make file management a little easier.

My project set up consists of folders for common components. I have a "pump" folder, "motor and drive" folder, "valve" folder..etc. Then I have a folder for each of our regular customers.
The files are stored locally on my machine, and they are "checked in" to the vault on our server when I decide it's a good idea. I allow the local copy to stay on my machine. If I need to work on a different computer (my laptop) I simply check out the main assembly file to the laptop and it automatically pulls all the associated files to the laptop. I do what I need to do at the customer site, and when I get back to the office I simply "check in" the assembly and everything is updated. This also means that I end up with a copies of the same assembly at three places. Laptop, desktop, and Vault server(but Vault keeps track of the latest and won't allow me to edit out of turn). If someone has checked the file out for editing it will allow other people to use the assembly, but only the person that checked the file out (or any associated files) to do any editing. You can imagine what kind of a mess it would be if this wasn't the case. The vault will also control access to different folders and give users different rights to edit or read only.
IMO it is the only way to keep control of the huge numbers of files you must have.

 

[aardvarkdw]

Thanks Mike,

Unfortunately, I can not implement vault...yet. Implementing vault would require changes to our other file managment systems and we are not able (read, other departments don't want to deal with it)to do that right now. So I am kinda stuck without it.



David

 

[DesignerMike]

You should be able to use the same project/file structure as outlined in the paper. You will just NO control over any of the files. You will also have no way of determining who screwed them up either.

You should probably set up a "library" folder for the parts that don't change, and I would keep any working folders locally on the machine where the guys are working on them....then at least they only have themselves to blame.

Good luck...you'll need it when everyone starts sharing a lot of files. You will probably also end up with endless "can not resolve" errors since no one will be using the same structure and there will be duplicates of parts everywhere.

I had enough trouble by myself (and I didn't have anyone else to blame)

 

[Adrian2]

Dear Dave;

In the company I am working for all the folders are located in one single project file on one drive. This allows multiple designers to work on several different contracts but still remain in the same project file.

We have an extensive set of library folders for fasteners and steel structurals where the iproperties have all been set with the necessary fields to talk to our Baan Inventory control system.

Where new parts are created, we often copy from an existing part to carry over the Baan information where necessary.

We still have duplicate parts but we do try to cull them into standard parts folders when we find them and havge the time to fix them.

One of the most elegant solutions to eliminating duplicate parts that I have used is the "Structured Bill of Material". It's not even a fancy software based solution. All the designers are regularly given an Updated Standard Bill of Material. In this all the standard parts are grouped into standard parts lists in a checklist format.

If the designer can use the standard parts he references them in the new BOM for his project. The Designer is typically left with only the custom assemblies to design, So his/her workload is reduced.

Over time, the Structured Bill grows to include more standard parts lists, RH and LH parts list, 3 foot, 6 foot, 12 foot parts lists, whatever you find important to standardize on.

The beauty of it is that it makes peoples work easier so they are encouraged to promote its further use.

Best Regards

Adrian Dunevein
AAA Drafting Services

http://www.aaadrafting.com

http://home.cogeco.ca/~adunevein/

SW2006 Office Pro. SP4.1

 

[aardvarkdw]

Thanks Adrian,

After discussing it with our VAR, we are going to attempt to consolidate and work from a single project file. This will be very painful to do, but I think it will be best for the company. I am estimating about 2 months worth of pack n go's and fixing lost constraints but hopefully it will mean that things are better afterward.

David