After one decade in the AEC space, Revit continues to be unique in its holistic “whole-building
BIM” approach to design integration. Sure, there are other BIM-ish tools that allow you to design
in 3D. And 10 years ago, 3D might have been a differentiator, but today 3D is a commodity!
Whole-building BIM is the ability to design, manage, and document your project information
from within a single file, something that no other BIM tool will allow you to do. In a non-Revit
workflow, you’d have to design your project across multiple files—not just across disciplines but
within the same discipline! Imagine the dysfunctional workflow of having separate files for the
building shell, roof, and each interior level for a modest 50-story building. That means you’ll be
managing at least 50 files just for the architecture. Count on another 50 files for the MEP and structural
design, and now your team has to juggle more than 150 separate files that have to be manually
linked together. Then you would have to export your files to separate sheets and views for
documentation.
So, now your building has been smashed up into 2D information. And when you have changes,
expect to go back to the model and repeat the process, because you can’t risk making changes in
2D when they’re not bidirectionally associative. No thanks!
How would you complete the same project in Revit? Well, worst case is that you’re probably
looking at three files for the same building (architecture, structure, and MEP), because design
is a team sport, and you’re not all in the same office or geography. So, everyone does their work
and links each other’s projects. Three files!
And as for documentation, it’s all in the same file as the respective project. No exporting
required. It’s a completely bidirectional, multiuser working environment, so if you’re trying to
compare Revit to what you’re used to in other 2D CAD or 3D BIM tools, stop now.
As for the UI, well, there have been some much needed changes in Revit Architecture 2011.
Last year’s introduction of the Ribbon introduced us all to what one well-respected Revit
expert succinctly referred to as “drunken leprechaun mode” because the tools were not only
highly contextual, but they kept moving around in subjective ways. We’re glad to tell you the
Ribbon UI has evolved into what we like to call “sober leprechaun mode”! Yes, the UI is still
contextual because the now-sober leprechaun keeps contextually hiding commands and panels
the moment you put them down. But at least he’s learned to put the commands and panels
in the same place the moment you start to do something else. And we think this is a terrific
improvement.
In this chapter, you’ll learn to:
Understand Revit
•u project organization
•u Understand Revit interface organization
BIM” approach to design integration. Sure, there are other BIM-ish tools that allow you to design
in 3D. And 10 years ago, 3D might have been a differentiator, but today 3D is a commodity!
Whole-building BIM is the ability to design, manage, and document your project information
from within a single file, something that no other BIM tool will allow you to do. In a non-Revit
workflow, you’d have to design your project across multiple files—not just across disciplines but
within the same discipline! Imagine the dysfunctional workflow of having separate files for the
building shell, roof, and each interior level for a modest 50-story building. That means you’ll be
managing at least 50 files just for the architecture. Count on another 50 files for the MEP and structural
design, and now your team has to juggle more than 150 separate files that have to be manually
linked together. Then you would have to export your files to separate sheets and views for
documentation.
So, now your building has been smashed up into 2D information. And when you have changes,
expect to go back to the model and repeat the process, because you can’t risk making changes in
2D when they’re not bidirectionally associative. No thanks!
How would you complete the same project in Revit? Well, worst case is that you’re probably
looking at three files for the same building (architecture, structure, and MEP), because design
is a team sport, and you’re not all in the same office or geography. So, everyone does their work
and links each other’s projects. Three files!
And as for documentation, it’s all in the same file as the respective project. No exporting
required. It’s a completely bidirectional, multiuser working environment, so if you’re trying to
compare Revit to what you’re used to in other 2D CAD or 3D BIM tools, stop now.
As for the UI, well, there have been some much needed changes in Revit Architecture 2011.
Last year’s introduction of the Ribbon introduced us all to what one well-respected Revit
expert succinctly referred to as “drunken leprechaun mode” because the tools were not only
highly contextual, but they kept moving around in subjective ways. We’re glad to tell you the
Ribbon UI has evolved into what we like to call “sober leprechaun mode”! Yes, the UI is still
contextual because the now-sober leprechaun keeps contextually hiding commands and panels
the moment you put them down. But at least he’s learned to put the commands and panels
in the same place the moment you start to do something else. And we think this is a terrific
improvement.
In this chapter, you’ll learn to:
Understand Revit
•u project organization
•u Understand Revit interface organization
No comments:
Post a Comment