BIMserver paths and SugarSync

[Anonymous]

Our office is moving to a cloud data storage & back-up system called SugarSync(SS) for all non- Archicad files, and maybe eventually eliminating our server (how non-committal can you get!?). This behaves somewhat like Drop-box, where files are kept on the cloud, and users download them to their local machine and SS keeps the versions synced. The principal advantage I see is for users in the field can more readily/rapidly access documents. (Not sure how it benefits the people inside the office) The BIMserver remains in our office, and gets backed up with a clone hard drive/ RAID.

This raises several questions:

1. Our layouts reference lots of non-Archicad generated content: PDFs, DWGs, PNGs, etc. Where is the best place to keep these files? Teamwork files should reference these files directly, not to an individual user's machine, right? Can the files be stored on the BIM server machine? Seems like this would minimize network traffic. Is it better to keep them on a separate server machine? Why?
2. Our Template is a set of folders and files that are duplicated to turn into a project. The Archicad portion is a .PLN files that is renamed and then shared to the BIM server. (Other "master" files that all projects reference reside in a different location.) Is there a reason to make this file a TW file too?
3. We've always had a separate drive for the office Archicad library. This drive would have the office library (parts used for all projects. I don't want them embedded in the project template, because there might be a universal change that should be applied.) Additionally, I've kept attributes, favorites, hot fixes, schedule settings, etc. in this drive as well. Is there a reason to have the library and projects in separate drives? Needless to say, the BIM server mirrors these libraries anyway.

Thanks.

[NandoMogollon]

Hi Nathan,

Can the files be stored on the BIM server machine? Seems like this would minimize network traffic. Is it better to keep them on a separate server machine? Why?

Yes, you can use the same machine to store files, in that case you will use it as a typical File server. This so OK for regular work - ArchiCAD support files ( likns, xrefs and the sort), but is not recommendable if you are dealing with either large size projects, large teams, and/or constantly saving-copying files form that server. The more traffic you put to that machine, the slower it gets.

2. Our Template is a set of folders and files that are duplicated to turn into a project. The Archicad portion is a .PLN files that is renamed and then shared to the BIM server. (Other "master" files that all projects reference reside in a different location.) Is there a reason to make this file a TW file too?

Yep, it's a common thing nowadays: to use a "template" teamwork file to start with, rather than a TPL. It would be nicer if the BIM Server could host TPL files.

3. We've always had a separate drive for the office Archicad library. This drive would have the office library (parts used for all projects. I don't want them embedded in the project template, because there might be a universal change that should be applied.) Additionally, I've kept attributes, favorites, hot fixes, schedule settings, etc. in this drive as well. Is there a reason to have the library and projects in separate drives? Needless to say, the BIM server mirrors these libraries anyway.

You can keep the shared libraries in the BIM Server, and Project Specific within the project file. All other ArchiCAD managing files (AAT, XML, TPL, MOD, etc...) you don't really have to share them right?

Hope this helps