11.23.2009
Digital Mock-Up: Window Detail
Lately, we've been using digital mock-ups more and more. Here is an example of one at a window detail:
11.20.2009
Commentary on You're the Boss
One of the many non-BIM blogs that I read/skim is "You're the Boss", a NY Times blog about running a small business. Specifically, the author, Bruce Buschel, is starting a restaurant, which I have found fascinating.
Yesterday, he wrote a post about the progress of construction on his new restaurant and had a few interesting things to say, which I think reflect the state of our industry. The overall theme of his post is truly about planning and expresses the need for the transformation we are working to make, through VDC. A few great quotes:
I think this is a struggle for so many, who cannot visualize the end space. Once they finally see it,
I would have loved to show Buschel a BIM of his project, sometime during design. As a contractor, we suffer from indecision, late decision, or change of mind. All three are costly and time-consuming, and as Buschel points out, test the paitence of the team. We don't like to see owners struggle to make decisions, and honestly, much of the indecision comes from lack of information. What do the options look like? Cost? What is their impact of schedule?
VDC clearly cannot solve all of these issues, but can help good teams extract and position information to move forward with design and construction.
Yesterday, he wrote a post about the progress of construction on his new restaurant and had a few interesting things to say, which I think reflect the state of our industry. The overall theme of his post is truly about planning and expresses the need for the transformation we are working to make, through VDC. A few great quotes:
Buschel is impressed with the ability of architects to visualize and understand design using 2D plans, because he has no ability to do so - like so many other people in the industry. Only as he stands in the partially completed space, he starts to see "this materialization of a thousand decisions made so long ago in the abstract".
"...So the plumber is at work, playing Twister with the HVAC guy as the electricians dance around the carpenters..."
"...There are drawings upon drawings, and then changes upon changes upon those drawings. Everywhere you look, rubber bands contain the drawings, 24 inches by 35 inches, rolled up like parchment-paper communiqués between Jefferson and Adams..."
I think this is a struggle for so many, who cannot visualize the end space. Once they finally see it,
I would have loved to show Buschel a BIM of his project, sometime during design. As a contractor, we suffer from indecision, late decision, or change of mind. All three are costly and time-consuming, and as Buschel points out, test the paitence of the team. We don't like to see owners struggle to make decisions, and honestly, much of the indecision comes from lack of information. What do the options look like? Cost? What is their impact of schedule?
VDC clearly cannot solve all of these issues, but can help good teams extract and position information to move forward with design and construction.
11.19.2009
The Platinum Issue
The Platinum Issue of Tocci Today came out today. This one focuses on the final outcomes of the Autodesk HQ:
LEED Platinum Award
The Final Judgement, when an independent judge analyzed our project against our goals to see how well we did (and therefore part of our shared profit!)
Metrics from the Project - the ROI of IPD
Enjoy!
LEED Platinum Award
The Final Judgement, when an independent judge analyzed our project against our goals to see how well we did (and therefore part of our shared profit!)
Metrics from the Project - the ROI of IPD
Enjoy!
11.16.2009
No Pipe Slope?
Jeremy, one of Tocic's VDC Modelers brought this to my attention this morning. We played with it for a little bit, but couldn't figure it out. I obviously forwarded the issue to Autodesk, but figured I should share with all of you - in the event that we are missing something simple (or there is a less than simple fix!).
The Goal: Slope pipe: 1/4" every 10'
Usually to slope, we just select the entire area that needs to slope and type the required slope. Works like a charm - locating each fitting and pipe at the correct elevation. We did the same thing in this case, but apparently, it is too small of a slope for Revit. Geometry didn't change; slope on pipe reads 0"/12".
No, this slope isn't huge, but the main runs 200', which is a change in elevation of 5". That clearly will affect coordination.
We found a workaround, but it isn't realistic to do this on the entire system, so we've decided just to do it on the main (which has about 5 bends in X/Y). If you change the elevation of one end of the pipe to the manually calculated value, it will slope it (although the elevation still reads 0"/12"). So for each bend on the main, we have to calculate the elevation based on the slope and manually type. (I hope the layout doesn't change too much!) We have decided to ignore the slope on branch lines for now, which run about 50' - only because we don't have to have to do so much work if things change.
This really shouldn't be a problem. Are we missing something or can Revit really not recognize slopes below a certain amount? Is there a better workaround?
The Goal: Slope pipe: 1/4" every 10'
Usually to slope, we just select the entire area that needs to slope and type the required slope. Works like a charm - locating each fitting and pipe at the correct elevation. We did the same thing in this case, but apparently, it is too small of a slope for Revit. Geometry didn't change; slope on pipe reads 0"/12".
No, this slope isn't huge, but the main runs 200', which is a change in elevation of 5". That clearly will affect coordination.
We found a workaround, but it isn't realistic to do this on the entire system, so we've decided just to do it on the main (which has about 5 bends in X/Y). If you change the elevation of one end of the pipe to the manually calculated value, it will slope it (although the elevation still reads 0"/12"). So for each bend on the main, we have to calculate the elevation based on the slope and manually type. (I hope the layout doesn't change too much!) We have decided to ignore the slope on branch lines for now, which run about 50' - only because we don't have to have to do so much work if things change.
This really shouldn't be a problem. Are we missing something or can Revit really not recognize slopes below a certain amount? Is there a better workaround?
11.10.2009
Structural Workflow - Semi-Social BIM
LA Fuess, who hosted the BRUG meeting, also presented on one of their projects
.
On this project they were only design team member to work utilize VDC (although now they are working with Revit-enabled architects on about 20% of their projects). The contractor, a JV between Austin and Walsh, utilizes BIM, but initially wasn't sure if they could trust the accuracy of LA Fuess' model.
In the end, LA Fuess proved that their model was accurate and detailed enough for use in coordination and fabrication-assistance. They actually added geometry (like gusset plates) at the request of the contractor (a lesson to all of us: ask and you shall receive).
The model was transfered to the fabricator for detailing, and the information was so beneficial to the fabricator that it cut down the detailing schedule by 2 months.
.On this project they were only design team member to work utilize VDC (although now they are working with Revit-enabled architects on about 20% of their projects). The contractor, a JV between Austin and Walsh, utilizes BIM, but initially wasn't sure if they could trust the accuracy of LA Fuess' model.
In the end, LA Fuess proved that their model was accurate and detailed enough for use in coordination and fabrication-assistance. They actually added geometry (like gusset plates) at the request of the contractor (a lesson to all of us: ask and you shall receive).
The model was transfered to the fabricator for detailing, and the information was so beneficial to the fabricator that it cut down the detailing schedule by 2 months.
11.09.2009
Structural Workflow - Modeling Wood Framing
Another presentation at the BRUG meeting was a wood frame project from SGH. The building is an existing church, originally constructed in 1955. A fire destroyed much of the roof and second floor, so SGH is working on the new structure.
I was really impressed with the level of modeling that SGH did - every stud, framing, etc. I know from first hand experience that wood frame modeling is somewhat painful. Some of the issues that were brought up related to the documentation of the information after it had been modeled (tagging, line weights, etc.), but we definiately ran into some of the modeling issues - there aren't a lot of families and everything has to be modeled manually.
Hopefully life will improve with either the 2010 enhancement tool or the latest version of MWF (which I've heard is quite nice!).
I was really impressed with the level of modeling that SGH did - every stud, framing, etc. I know from first hand experience that wood frame modeling is somewhat painful. Some of the issues that were brought up related to the documentation of the information after it had been modeled (tagging, line weights, etc.), but we definiately ran into some of the modeling issues - there aren't a lot of families and everything has to be modeled manually.
Hopefully life will improve with either the 2010 enhancement tool or the latest version of MWF (which I've heard is quite nice!).
Structural Workflow - Revit to ASD
Last week's BRUG meeting focused on structural workflow, from design to fabrication. One of the three presenters was Derek Gilbert, a Technical Specialists from Microdesk, who presented on Revit Structure and AutoCAD Structural Detailing (ASD). ASD comes with the Revit Structure Suite.
It looks like Revit exports direct to ASD and then users can use detailing macros to add connections, piece marks and create shops. I don't believe there is a bi-directional workflow, but it seemed like updates can be sent from Revit to ASD.
I noticed a "formwork" button, but Derk told me that functionality is not quite ready. Hopefully soon, as we have a massive CIP project we are starting! We have been looking at Tekla for this and more, so it will be interesting to compare the two platforms. Although functionality is key, we're also interested in going with the product that most fabricators use. Collaboration is a huge driver of our software decisions.
It looks like Revit exports direct to ASD and then users can use detailing macros to add connections, piece marks and create shops. I don't believe there is a bi-directional workflow, but it seemed like updates can be sent from Revit to ASD.
I noticed a "formwork" button, but Derk told me that functionality is not quite ready. Hopefully soon, as we have a massive CIP project we are starting! We have been looking at Tekla for this and more, so it will be interesting to compare the two platforms. Although functionality is key, we're also interested in going with the product that most fabricators use. Collaboration is a huge driver of our software decisions.
11.06.2009
Subscribe to:
Posts (Atom)
