I guess that's where in my mind I started this thread....
Is it not possible (or shouldn't it be) that the architect starts things off
with one locked workset - then the MEPS guys each import the model and
create their discrete workset non-modifiable-by-others workset. In this way
the entire building model or BIM is on one file....ummm sort of how BIM was
meant to be.
It seems to me that the best way to allow this cross-discipline activity is
to sell the software packaged as an all-in-one. All-in-one packaging, I
believe, would make the process much less complicated ....ensuring
compatibility and use of tools etc. I would like to at least be able to
communicate, thru the 3D capabilities of Revit, proposed
work-arounds....i.e., be able create duct and piping runs flagged as
"proposed modification" to other's work. This would be a duct on my
architectural workset....not deleting or moving the run on the mechanical's
workset....having all the Revit tools is requisite to using Revit as true
BIM software, just as BIM software is requisite to streamlining the industry
and reducing E&O issues.
The corollary benefit to Autodesk is acceleration of Revit's acceptance and
use. Right now, it seems the majority of MEPS see little benefit or need to
change from ACAD-based systems. There would have to be some savings in
merging development teams to focus on an integrated, rather than three or
more discrete, software package.
IMH (and often misinformed) O
--
David Ford
"Patrick Porter"
wrote in message
news:5271933@discussion.autodesk.com...
Well the way we use revit systems is we create different worksets for the
different Engineering disciplines (architectural, mechanical, electrical,
etc) put objects on teh correct workset gives you a head start for locking
out accidental modifications.
wrote in message news:5270658@discussion.autodesk.com...
Do you guys really want to give architects the ability to changing your
ductwork?
"david" wrote in message
news:5267753@discussion.autodesk.com...
Forgive me for re-posting the issue....
As these forums serve the additional function of providing indirect feedback
to AutoDesk, I'm hoping to garner some support to influence how Revit is
packaged. As stated in the post "Revit Packaging Discussion," I believe that
the Revit revolution would be significantly furthered by offering Revit as a
single Revit Building/Systems/Structure/ACAD seat.
I believe this would accelerate wider cross-discipline use and acceptance of
this critical BIM software. Good for us, good for AutoDesk.
All issues raised regarding hardware requirements aside, please (if you care
to respond) start your response with YES or NO to the question: "Do you
think it would help simplify and promote wider cross-disciple use of Revit
in the industry, and some comments stating why you think so....or not.
Regards
--
David Ford
