I've already read a lot of post about new features in Revit 2009, so I'm sure you all have too. But I'd like to highlight some of the features that offer benefit to builders (and some things that I'm not so thrilled with!).
Mental Ray
Much higher quality rendering capability will help us communicate design intent to the field much better. I'll share some comparative renderings that we've done some other time, but if you haven't seen it, just trust me on this one. I also really love the new Materials interface; it is much more user friendly. That really needs to be applied to many other dialog boxes, especially with reference to family organization. Could Revit be moving towards helping us manage an object library!?
Sloped Pad & Curved Edges in Slopes Slabs
Anything that enables us to model more accurately is a good thing.
Dimension Overrides
Dimensions can be overridden with text (but not with another dimension value). Also, users can add text strings above, below, before and after the dimensions.
I am really concerned with this modification. I understand that there are occasions where architects need to add text to dimensions, but I really don't want this to be an excuse to model less accurately.
Phase Mapping Between Linked Projects
The interface for this is a little confusing, but this will be great for projects with multiple models (which all of Tocci's are) where the models were created by different sources that didn't coordinate project standards.
Foundation Improvements; Improvements to Concrete Modeling
Any improvements to controlling accuracy are good. I don't like when Revit automatically tries to do anything, though, so I'm concerned that concrete beams and columns will automatically join to slabs, walls and foundations when their geometries overlap. If I want something joined, I'll join it!
Warnings
I am so excited about being able to export warnings from the Review Warnings dialog. So excited. It will also be nice to show all warnings associated with a specific element.
Selection Count
Definitely one of those little things that makes Revit easier to use. The filter dialog lists the number of elements in each category as well as a total element count. There is also a little icon in the status area that counts the total number of elements selected. A good thing for when someone asks "how many of those windows are there in the project" - which happens.
View Navigation Tools
Okay, I really don't like ViewCube or SteeringWheel. I am probably not use to them, but I am not a fan. And why does SteeringWheel only work in perspective views. I want it to function like the 'feet' tool in NavisWorks (I think its actually called walk, but thats not what we call it), which I understand converts the view to perspective, but still. I don't like having to make a camera view to use SteeringWheel. I really like the 'feet' tool.
Recent Files Windows
Another new thing that I don't really like. It just bugs me. I want to customize it and get rid of the links to the Revit Web Library, etc.
File Navigation Dialogs
This is one of those things that I got used to in AutoCAD and then was really irritated by in Revit. You can add your 'current folder' to 'places', so that you don't have to navigate through tons and tons of folders to get your Revit file. Another one of those little things.
And most importantly.....
Phasing & Groups
The first thing I did is testing the functionality between phasing and groups. And it's fixed! It is only one of the several major issues that we were having with Revit, but it's actually fixed! I'm so relieved.
As soon as I get approval for the NavisWorks beta (soon please? I entered the codes in last week!), I will start playing with that.
2.19.2008
how we (collaboratively) VDC
One of the concepts that came out of ConsensunDocs BIM Addendum is the BEP: BIM Execution Plan.
The BEP basically outlines how a BIM/VDC-enabled project team can work together. However, the document doesn't actually define the content of the BEP; it only offers guidelines for the type of information that should be in a BEP.
I am currently working with a team at design firm, outlining our BEP. This won't actually serve as a legal document (I think); it is more like our plan for working together. The content of the BEP (at least this one in particular) is somewhat technical: you model this, I'll model that; these are our project phases, etc. etc. The actual content of the BEP doesn't actually deal with the 90% sociology (have you heard one of the latest quotes about BIM/VDC: it's 10% technology, 90% sociology?).
The amazing thing is that in developing the BEP together, we are taking care of the 90% sociology. To develop it, we are compromising on standards, file formats and methods. And by doing that, we have created an undocumented BEP. If we had to document it, it would probably say, "If something goes terribly wrong or we have a problem, pick up the phone."
We haven't started co-habitating in the model (yet! - more on that later), and I'm sure that when we do, we will encounter our share of issues that cannot be solved by referring to our documented BEP. But at least we will be able to lean our collaborative relationship and work it out. And I think that is the point of all of this, no?
The BEP basically outlines how a BIM/VDC-enabled project team can work together. However, the document doesn't actually define the content of the BEP; it only offers guidelines for the type of information that should be in a BEP.
I am currently working with a team at design firm, outlining our BEP. This won't actually serve as a legal document (I think); it is more like our plan for working together. The content of the BEP (at least this one in particular) is somewhat technical: you model this, I'll model that; these are our project phases, etc. etc. The actual content of the BEP doesn't actually deal with the 90% sociology (have you heard one of the latest quotes about BIM/VDC: it's 10% technology, 90% sociology?).
The amazing thing is that in developing the BEP together, we are taking care of the 90% sociology. To develop it, we are compromising on standards, file formats and methods. And by doing that, we have created an undocumented BEP. If we had to document it, it would probably say, "If something goes terribly wrong or we have a problem, pick up the phone."
We haven't started co-habitating in the model (yet! - more on that later), and I'm sure that when we do, we will encounter our share of issues that cannot be solved by referring to our documented BEP. But at least we will be able to lean our collaborative relationship and work it out. And I think that is the point of all of this, no?
2.13.2008
New at Autodesk...
I try not to post about Autodesk news, but here are some things that matter to me:
Additionally, Green Building Studio has announced that Autodesk is going to acquire GBS. Autodesk is also acquiring Carmel Software, which is a "developer of HVAC (heating, ventilation and air conditioning) mechanical engineering software that enables engineers and architects to analyze their mechanical designs and help ensure sustainability goals are achieved."
- Revit Architecture has Mental Ray, the rendering engine from 3DS Max. It's amazing..and really will be helpful for our field visualization program.
- Revit MEP supposedly has increased modeling functionality. I say supposedly because I haven't played with it yet, but I'm excited that it is getting better because we're going to be using it on our next project.
- Autodesk NavisWorks 2009 has also been described, but it sounds a lot like JetStream v5. I think I'll have to wait until I see to really understand new features and what the acquisition really means. The only difference that i can see is that they are changing the names of the products to NavisWorks Review (core functionality of aggregation), NavisWorks Simulate (previously Timeliner) and NavisWorks Manage (previously Clash Detective). And of course, Freedom is the free view (no change there).
Additionally, Green Building Studio has announced that Autodesk is going to acquire GBS. Autodesk is also acquiring Carmel Software, which is a "developer of HVAC (heating, ventilation and air conditioning) mechanical engineering software that enables engineers and architects to analyze their mechanical designs and help ensure sustainability goals are achieved."
2.11.2008
renderings (or communicating design intent)
One of the applications we have found for virtual construction is communicating design intent information to the field staff.
We are excited to have field staff understand the finished product, but less than excited about how much work it took to produce the renderings in Revit.
Since this was our first rendering project, we had to spend quite a bit of time learning! We learned the hard way to only keep the lights in visible rooms "on". Initially, it looked like the renderings would take days, at best (300 dpi, 30" x 20").
We ended compromising quality a little bit; we went down to 150 dpi which turned out to be okay for our purposes. The renderings took about 4 hours on our best machines, which wasn't too bad. Unfortunately we don't have machines dedicated to rendering, so we had to either run them overnight or on weekends - it was a little scary walking away from a computer for hours while it was rendering!
If we can reduce the amount of time we put into renderings, this will definitely be something that is incorporated into our field implementation program.
We are excited to have field staff understand the finished product, but less than excited about how much work it took to produce the renderings in Revit.
Since this was our first rendering project, we had to spend quite a bit of time learning! We learned the hard way to only keep the lights in visible rooms "on". Initially, it looked like the renderings would take days, at best (300 dpi, 30" x 20").
We ended compromising quality a little bit; we went down to 150 dpi which turned out to be okay for our purposes. The renderings took about 4 hours on our best machines, which wasn't too bad. Unfortunately we don't have machines dedicated to rendering, so we had to either run them overnight or on weekends - it was a little scary walking away from a computer for hours while it was rendering!
If we can reduce the amount of time we put into renderings, this will definitely be something that is incorporated into our field implementation program.
2.04.2008
5D..sort of
At Tocci, we use OST for our 2D quantity surveys and had planned on using Innovaya for 3D quantity surveys. The idea was that we would coordinate these independent quantity surveys and then compile them in Timberline.
Unfortunately, that workflow doesn't seem to be working for us (for a number of reasons).
Luckily, we are now playing with QTO which seems like it could eventually offer a solution. The concept is that QTO combines 2D & 3D quantity surveying in one tool. This information would not have a direct link to Timberline, but we can export to Excel. Better than nothing..
Unfortunately, that workflow doesn't seem to be working for us (for a number of reasons).
Luckily, we are now playing with QTO which seems like it could eventually offer a solution. The concept is that QTO combines 2D & 3D quantity surveying in one tool. This information would not have a direct link to Timberline, but we can export to Excel. Better than nothing..
Subscribe to:
Posts (Atom)
