I just read through Volker's post on Navis 2010 and found it very informative, but of course, I have comments of my own! I enjoyed particpiating in the 2010 beta, and was thrilled to see some of my requests come to fruition (probably because everyone else was requesting them too!).
The updates to the interface (ViewCube & Steering Wheel) are helpful. Although I initially hated ViewCube, I really like it now and am happy to see it in Navisworks (and I love that we can actually turn it off, too!).
And yes, as Volker mentioned, there are improvements to the measure tool, sectioning and visualization (finally - a horizon in Navisworks).
But I think that the most important improvements weren't included (or weren't covered in great enough detail) there.
First and foremost, shared coordinates are finally recognized from Revit. So now, we don't have to worry about 'Override Transform' just because someone set up the various models out of allignment. I see this fix as a huge benefit to collaboration. Often times, we have no control over where other parties place their model (in reference to 0,0,0). (The next step will be to recognize 'New UCS' in the AutoCAD export, right Richard?)
Yes, viewpoints are exported from Revit, but graphic overrides aren't maintained. We're a little frustrated with that.
The improvements to clash detection are really exciting. Clash reports are normally so cumbersome, with hundreds or thousands of clashes in a list. The ability to organize things by folders is helpful; the automated "group clases involving item" is even better. New graphic abilities in clash detection are really helpful: the animated transition from clash to clash, the ability to view a clash in context and the transparent dimming will be really helpful during coordination meetings. Oh, and we appreciate the additional clash status of "reviewed", but why can't we make custom statuses?
We love this release - in fact, we've already upgraded to it (still using beta of course) for current projects because the new features are worth it.
3.26.2009
Modeling for FM
We haven't seen a lot of demand for facilities management models from owners. Despite that, we're trying to push baby steps. Some contractors have developed far more sophisticated FM deliverables - Holder specifically comes to mind. Since the demand is low, we are taking very simple approaches, just to demonstrate to owners just a little bit of the value. One example uses hyperlinks to cut sheets for specific components and views of areas.
We implemented this concept for a hotel project - aloft, a new brand for Starwood. We created what we refer to a 'maintenance documents' (we have to make up a name for everything, right?).
We also included walk-throughs of each unit on a CD, with the walls set to transparent. This has enabled maintenance staff to understand the exact location of system components, without having to learn any software.
Very simple, but for this situation, it made sense. And hopefully, we'll have an opportunity to implement a more comprehensive solution for an owner who really wants it.
We implemented this concept for a hotel project - aloft, a new brand for Starwood. We created what we refer to a 'maintenance documents' (we have to make up a name for everything, right?).
We also included walk-throughs of each unit on a CD, with the walls set to transparent. This has enabled maintenance staff to understand the exact location of system components, without having to learn any software.
Very simple, but for this situation, it made sense. And hopefully, we'll have an opportunity to implement a more comprehensive solution for an owner who really wants it.
ROI of VDC
Ken Stowe (Autodesk) organized and moderated a session at AU last year on ROI of Utilizing BIMs for Builders. Builders from several companies shared how they are using BIMs, some of the challenges they've encountered, the benefits, and then some metrics associated with that use. The information was great, so the company has been watching the recording of it. It has gotten me thinking about our own metrics.
With regard to our VDC adoption, we are in an interesting place right now. We are wrapping up our involvement in our first VDC projects (Gen I & Gen II projects) while we are working Gen III projects, all of which include a model sharing component and several of which contractually require virtual construction. It almost hurts to look at earlier projects - we are more efficient now and the tools have come so far in just 2 (almost 3!) years.
There is one exciting thing about wrapping up these Gen I & II projects - we finalize our ROI for VDC on the project (and then with much fanfare, we present to John Tocci, other Tocci execs and the project owner).
Calculating ROI is difficult and is definitely up for interpretation. Our take on it: document everything we used the BIM for on the project (in a ridiculous spreadsheet that includes 20 different tabs, hyperlinks and formulas that I always manage to 'break' - although I always fix them before the VC Coordinator on the project notices) and then figure out what would have happened if we hadn't used the model for that (working with subcontractors, supers, etc.).
Here are two examples from one of our projects - you'll probably have to click on the image to actually read the text (I couldn't get it any larger and was too lazy to retype):
From there, we add up the totals and do a little math to figure out total ROI; for the project referenced above, it turned out to be:
Of course, anyone can come in and say that issues could have/would have been found without VDC, but it does give us a sense of what VDC has contributed project. And at least it starts the discussion. How is everyone else calculating VDC? Any comments/criticism on the examples I shared? Any feedback is great, as we want keep improving as much as possible.
With regard to our VDC adoption, we are in an interesting place right now. We are wrapping up our involvement in our first VDC projects (Gen I & Gen II projects) while we are working Gen III projects, all of which include a model sharing component and several of which contractually require virtual construction. It almost hurts to look at earlier projects - we are more efficient now and the tools have come so far in just 2 (almost 3!) years.
There is one exciting thing about wrapping up these Gen I & II projects - we finalize our ROI for VDC on the project (and then with much fanfare, we present to John Tocci, other Tocci execs and the project owner).
Calculating ROI is difficult and is definitely up for interpretation. Our take on it: document everything we used the BIM for on the project (in a ridiculous spreadsheet that includes 20 different tabs, hyperlinks and formulas that I always manage to 'break' - although I always fix them before the VC Coordinator on the project notices) and then figure out what would have happened if we hadn't used the model for that (working with subcontractors, supers, etc.).
Here are two examples from one of our projects - you'll probably have to click on the image to actually read the text (I couldn't get it any larger and was too lazy to retype):
From there, we add up the totals and do a little math to figure out total ROI; for the project referenced above, it turned out to be:
Of course, anyone can come in and say that issues could have/would have been found without VDC, but it does give us a sense of what VDC has contributed project. And at least it starts the discussion. How is everyone else calculating VDC? Any comments/criticism on the examples I shared? Any feedback is great, as we want keep improving as much as possible.
Steel Fab
A while ago, several of us (myself, PM & APM) went to SteelFab's facility in Charlotte, NC for a meeting with the owner's rep, architect, engineer, steel fabricator and detailer for the Crate&Barrel project. We all met there to review outstanding issues regarding steel, so that we could release it for fabrication. In the morning, we reviewed those issues, using both drawings & model (the design team is all Revit; the fabricator is using Tekla).
After that, we were able to tour SteelFab's fabrication facility. Since they use Tekla, they are able to take advantage of a model direct to CNC workflow for fabrication. We've heard a lot about this workflow, but it was very informative to see it in action, along with their coding system, to
keep track of each piece of steel for a project.
And we are finally able to leverage data from the design model by sharing it with the fabricator (I didn't feel like finding all the images; I just grabbed the marketing-esque images from our PPT).
After that, we were able to tour SteelFab's fabrication facility. Since they use Tekla, they are able to take advantage of a model direct to CNC workflow for fabrication. We've heard a lot about this workflow, but it was very informative to see it in action, along with their coding system, to
keep track of each piece of steel for a project.
And we are finally able to leverage data from the design model by sharing it with the fabricator (I didn't feel like finding all the images; I just grabbed the marketing-esque images from our PPT).
3.19.2009
IPD at Trapelo Road
I always feel odd posting things like this, but I guess I've gotten over it.
Autodesk, KlingStubbins and Tocci didn't just integrate for design/construction; we have also integrated on PR for the project. (It's amazing that even after Autodesk has occupied the space, we're still all speaking, respecting each other and having fun, huh?)
I refer to one of the pieces as "The Autodesk Movie" and it was recently upload to youtube for everyone's enjoyment (although I always feel uncomfortable watching it....).
Autodesk, KlingStubbins and Tocci didn't just integrate for design/construction; we have also integrated on PR for the project. (It's amazing that even after Autodesk has occupied the space, we're still all speaking, respecting each other and having fun, huh?)
I refer to one of the pieces as "The Autodesk Movie" and it was recently upload to youtube for everyone's enjoyment (although I always feel uncomfortable watching it....).
Subscribe to:
Posts (Atom)
