Well said.
Communication is the key, regardless of tools used!
--
Sean D Burke, Assoc AIA
Technical Consultant
Autodesk Consulting - Building Solutions
visit - www.autodesk.com/consulting
pkirill wrote:
> In our experience, at least with the latest build, the communication
> problems haven't been due to differences in the software - they've been due
> to the differences between architects and engineers. That's not a dig on
> architects, its just a fact that the two think differently and have
> different design goals. Thus the work process is different and they have a
> hard time understanding the issues we try to explain. While we have not
> conquered everything, we found that pushing for an early Revit meeting where
> we discussed and agreed on "all things Revit" was a huge step towards a
> successful project. From how the central files from all trades would be
> linked, who was going to post what where and in what order, how and who
> would be monitoring or copy/monitoring what objects and what impact that
> would have on the other trades, issues we ran into on other projects etc. -
> if it didn't solve anything it at least let the architect know what we are
> up against, that we are trying, and that with Revit we are all in it
> together...
>
>
> wrote in message news:5752895@discussion.autodesk.com...
> Are there fundamental differences in software code between Revit
> Architectural and Revit MEP? When I try to communicate certain problems,
> errors and glitches to architects, they don't seem to know what I'm talking
> about. They seem to be immune to the issues that are occuring on the MEP
> central file. What are the differences between the two versions? I would
> appreciate a reply from anyone at Autodesk. Thanks!