Fabrication CADmep™ > CADmep™ Users

Centralized Database or Multiple Instances?

(1/2) > >>

ductman:
For a small contractor, is it generally better to work from a single, centralized instance of the Fabrication database or to create new clones/instances of the main the database for each new project?  We typically run two to four detailers using Revit, plus a single CAM operator for sheet metal fabrication (No EST).  One user is remote with a solid VPN connection.  

I've been out of the CAD/Revit side of things for years now, but my previous understanding was that in most cases for a smaller team the best practice was to work from a single database with shared access, limiting permissions, and ideally a single administrator.  Changes are made and tested to a local sandbox copy of the database before being deployed to the main database.  This seemed he best, simplest way to ensure that all the database content is consistent for the team.  

One of our detailers comes from a larger mechanical contractor where he said they create a new copy of the database for each project.  They have hundreds of detailers working in various locations across the country.  His understanding is that this was their preferred method of ensuring changes made for one project or on the CAM side of things wouldn't inadvertently cause problems across multiple projects.  Also, he mentioned this was their way of controlling services & specifications particular to each project, especially for jobs with unique requirements (I'm a Revit novice but I've been told that Fabrication Profiles is a good option there).  

Any guidance for a smaller team is much appreciated.

bobcat09:
There's pros and cons to profiles but I wouldn't live without them. We have been using profiles for quite some time now and they have done very well with how we have them setup. Revit, ESTmep and CAMduct. One issue you'll have with either option, profile or copy of the DB, making sure you lock down user rights unless database modifications aren't an issue for you.

PipeFitter72:
Profiles are the way to go. Especially if you need to customize specs or services for a project.  Remember once you start a Revit model in a profile you are stuck in that profile.

cnash:
Third the profile sentiment.
Using profiles makes it much easier, having separate databases for everything will be a bear to manage I imagine.

WilliamNY:
I'll provide a contrary opinion.

Centralized databases with profiles are great if you have everyone sitting in an office with a robust network and steady bandwidth. But if you have people scattered all over the US, with scant (and sometimes NO) internet connection, and they're relying on a networked database, they're SOL.

That's why we have ours organized into a main database kept on a master server, with local, project-specific clones on users' computers. They're locked down with only one administrator, which forces everyone to stay on the same page. Yes, there is an extra step involved if we need to update anything but, in our opinion, that's far, far better than having guys out in the field who can't work.

Navigation

[0] Message Index

[#] Next page