Lew,
I understand your concept of using folders to store project files. Curious how you deal with 'common parts' or hardware. If you have a place for common hardware (ie, 3/8-16, Gr. 8 nut), do you just have the one file location or do you add that file to each zip folder, ending up with multiple copies of the file on the server?
Hi Paul -- Let us say that my
Project has the nominal identity of "
VT-1." I will create a
Directory titled
VT-1." "Beneath that
Directory I will create
Sub-Directories named:
Hardware, Common Parts, and
"Installation VT-1." All of the )if you will) "
common purchased hardware" (bolts, nuts, washers, bearings, etc) will be placed in the "
Hardware"
Sub-Directory. Let us say that I have "
Project Specific Parts & Assemblies" that will be used "across" the
Project they get placed into the "
Common Parts"
Sub-Directory. Now the
Installation Sub-Directory is where I place my "
Installation" (most would call it "
Top Assembly"
Model along with my (
spreadsheet based)
Parts List. Text File containing all my "
Function of Assembly" and "
Function of Parts" definition list, and the like for the
Project. "Beneath" my
Installation"
Sub-Directory I will create other
Sub-Sub-Directories for each of the (if you will)
Major Sub-Assemblies and (as required)
Sub-Sub-Assemblies (etc) until each
section of my
Project is properly identitied, and organized. and as necessary
Sub-Sub-Directories for things such as
FEA Data,
PDF's of Drawing Files, and the like. Thus I can create a
7-zip archive and call it (say)
VT-1 Project Rev New 20190808A and maintain a
complete dataset of the
Project.
Does this make sense to you? -- Lew