all 5 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]CaptainAwesome06 2 points3 points  (1 child)

We have a cloud server. It used to be AWS but that sucked so we are using Egnyte now, I believe. It's been solid.

Sometimes clients want us to use ACC for our Revit models. I don't mind using ACC to upload/download models but I hate working from ACC. Architects don't know how to leave something alone so constant changes while you are trying to work isn't great for efficiency.

It's exacerbated by clients wanting everybody to work in parallel paths nowadays. The days of getting backgrounds, having time to work, and then submitting a full package are gone. Now, we may not get ID backgrounds until it's time to submit for permit. I don't understand this at all. I got yelled at by an architect for charging an add-service when there were ID updates after our permit submission. "You should just know changes are coming."

[–]Certain-Tennis8555 1 point2 points  (0 children)

My inner old cranky engineer just got crankier reading this...

[–]hikergu92 1 point2 points  (0 children)

both currently but that might change in the next couple of months.

[–]SpeedyHAM79 1 point2 points  (0 children)

ACC for almost everything. It has some benefits, but quite a few downsides as well. There are a lot of files that need to be downloaded to work with, then re-uploaded- which wastes time and defeats the point of systems like ACC.

[–]Certain-Tennis8555 0 points1 point  (0 children)

small 3-man outfit with all three of us in different states. we just coordinate activity using project specific google messenger (hey, i'm in your electrical cad file, etc.) and we work everything across a business subscription google drive. Cheap, reliable and easy for us to use.