CADuzer

Change #1 Has Come…

Feb 24, 2010 BIM, Commentary, Revit

Hey All.  I wanted to let you all know of the first change that has happened, and now I shall.  As of this past Monday, February 22nd, I am the Regional Revit Specialist for the North-East region at Gensler.  I’m responsible for helping the offices of this region (as well as the firm as a whole) further their integration and implementation of Revit and build a library of resources that includes content, learning, support and more.  I’m very excited to get started and hope, as I go, to continue learning.

Change number two is…coming soon…

Revit – Things to Consider When Starting a Project

Dec 23, 2009 BIM, Commentary, Revit

Hey All.  I want to go through a few key things you should think about when starting a Revit-based project.  I have to say, first of all, let’s start referring to these projects as a “Revit-based Project” as opposed to a “Revit Project”.  I think it takes the emphasis off of what type of software is being used and puts it, more appropriately, on the fact that it’s an architectural project.  Anyway, here are five things that you should consider, and document, when starting a project:

1. Software Version and Build (internally and externally) – It’s important to make sure that not only are all of your internal Revit users using the same version (and build) of Revit, but also that all consultants are using the same version.  This will ensure that there is no loss of data when sending your model to a consultant.  It’s also import to note that even if your consultant is not working on the architectural aspects of the project (ie. they’re using Revit Structure or Revit MEP), they still must be using the same release of Revit (in this case, the build version can be ignored).
2. Working with Consultants – Be aware of what software (and versions of those applications) that your consultants are using.  Once this data is compiled, document the process by which your Revit model is exported to each piece of software.  For example, if a consultant is using AutoCAD, make sure that the text file which describes how Revit objects are translated into layers has been updated to conform to your office standards and that all team members are aware of its location.
3. Single or Multiple RVT Model Files – The process of sending data to a consultant differs when your project uses a single model file or multiple model files.  Therefore, document the names of the model files contained within the project as well as a description of what each model file contains.  Taking a step back from that, decide whether or not you actually want to use multiple model files.  If so, make sure all team members know how the project is organized, within which file they should be working (and modeling) and, more specifically, which model file should be printed from.
4. Worksets – On the same topic of organization, document the worksets being used in your project and what types of objects should be put on them.  It’s important to keep this list shorter rather than longer because, as similar as worksets might seem to layers in AutoCAD, they are not interchangeable and users should be able to keep the idea of them in the background.  Also, the Revit leaders on the team should have a process by which they can check to see if objects are on the correct workset and, if they’re not, how to correct the error.
5. Level of Detail Based on Project Phase – As I have mentioned in previous posts, the level of detail applied to a model should be based on the phase of the project.  For example, in earlier phases, such as Schematic Design, the detailed structure of walls should be left out and the types should be set to generic.  Material-wise, the walls should have the basic grey material or transparent blue material.  Be sure to document exactly how detailed object-types should be brought to.  For clarification purposes, document the levels of detail for objects for the upcoming phases.  This will allow users to keep in mind how the model will be developed over time.

While these are just five things to consider, there are many others as well.  At its heart, however, this is both a preparation-based as well as a future planning-based process.  Considering these things will eliminate confusion and will provide a road-map for working on a Revit-based project.

Revit 2010 – Great Parametric Forms Tutorial at HOK BIM Solutions

Dec 11, 2009 BIM, Revit

Hey All.  I just went through this tutorial over at the HOK BIM Solutions blog on how to create parametric forms within the conceptual mass environment of Revit Architecture 2010.  Take a look:

http://hokbimsolutions.blogspot.com/2009/07/creating-parametric-forms-using-revit.html

Tags: BIM, Revit

The Way Forward? The Way Forward!

Nov 15, 2009 BIM, Commentary, Revit

Hey All.  I know it’s been a while but, as I’m sure most of you can relate, things happen, one gets distracted, and suddenly it’s two or so months later.  I read a post on James Vandezande’s website (a co-worker of mine), All Things BIM, on October 2nd called, “BIM Manager or Architect,” and this crossroads that he has come across has most certainly been one I have thought about myself.  First of all, I have enjoyed my transition back to architect from Digital Design Manager, as it has allowed me to put a face to the name.  I am now within the environment of those who would ask for my help and I now better understand where their questions are coming from.  Additionally, I can now wholeheartedly say that going through a book (or five) or taking a class (or five) does not sufficiently prepare you for how any piece of software works in a real, live project environment.

When I was officially assigned to a project, I thought to myself, “OK, now you’re an architect again, put the digital design manager hat away.”  It didn’t take long for me to realize that that hat has been stapled to my head many years before.  That’s fine.  If anything, it’s the way I prefer it.  Here’s the thing, and there really is no way of getting around it, whatever strategies we employ, methods we put into practice, or seminars we give, people are going to do what they want.  I’ve realized that the diminished amount of time I have to spend on spreading the digital design gospel (which, in the case, is Revit-centric) is really no excuse.  No one cares.  This work is not necessarily tied to just the firm I, or you, work for.  It must be industry-wide.

Do you want to know what finally lead me to this conclusion?  I found that the encounters I would have with people changed from me presenting the benefits of BIM, to me defending BIM, to me battling a die hard resistance who fought the change simply for the sake of not wanting to learn something new.  But then something else happened, those fighting me turned, and left.  I started to ask myself, “Where did everybody go?”  The answer was right in front of my face.  The answer was the same reason that my title was now, “architect,” and not, “digital design manager.”  The recession.  The recession has put everyone in an understandable panic that they have become so used to being in, they don’t know how to get out.  They’re in a mode best described as, “get the project, do the project, send the project out the door, get the project…”  Certainly, I don’t ascribe this to every single architect, but what it has caused is a slowing of progress in the use of digital design tools within an industry that was slow to adapt already.  The question comes back, however, to this, “how do you fight an enemy that has decided not to show up?”  And then it hits you, “why are you fighting?” and, “why is there an enemy?”

As a huge Yankee fan, after they won the World Series, I went with several friends to the ticker-tape parade down (or more accurately, up) the Canyon of Heroes in lower Manhattan.  Afterwords, one of my friends and I, an architect and urban designer, walked to get some lunch.  He said to me, “If you want to make Revit more appealing, make it easy to use and make everything that comes out of it look like something that we’re all used to.”

Here is my suggestion to everyone, let us take a page out of the history of what we learned from 25+ years of AutoCAD.  Let’s design a framework for the use of Revit within the architecture industry.  I know many of you will tell me that this already exists but the way I see it is that it is too fragmented.  Bits and pieces are strewn all over the Internet.  We need to organize it in a single document or database.  One thing I’ve learned from being on a project teetering between Revit and AutoCAD is that there are still many areas that we haven’t quite developed usable, and easily explainable, procedural standards for.  I don’t mean to say that my firm, or your firm or any other single firm has this problem alone.  Nor do I mean to say that it is the responsibility of one single organization to solve it.

To be clear, I’m not looking for a How-To guide that will explain how to create walls or add keynotes.  I’m looking for a Revit-Based Project Procedures database.  I’m looking for a Revit-Based Project Best Practices guide.  Certainly at this point in the history of AutoCAD, no two firms use it the same way, but that’s because we didn’t have the methods of sharing knowledge and methods back then.  We do now and should take advantage of it.

Here are some suggestions that I would give for some of the top-level topics that should be included (these are in no particular order and are simply being typed as they come into my head):

• Project Folder Structure
• Staff and Task Assignment
• Project Phase-based Level of Detail
• Naming Conventions for:
  • Worksets
  • Groups
  • Materials
  • Object Types
  • Object Instances
• Revit-AutoCAD Integration
• Revit-Rhino Integration
• Revit-3ds Max Integration

As I said, these are just some topics that have come to my mind.  I’ve created a Google form where I would encourage you to add your ideas for topics and, once we have a good list, we can each take one or two of them and begin to break them down into sub-topics and descriptions.

If those who will use this, and other, software on a daily basis are looking for a framework for the use of Revit on projects within the Architectural industry, let’s gather as a global community, create it and give it to them.  Please let me know what you think and feel free to add your topics using the link below:

http://spreadsheets.google.com/viewform?formkey=dDVuMjZUbFd0VFBIeElhazN3Sl93Z0E6MA

Revit: Do You Proofread Your Prints Before You Show Them to Anyone? You should!

Sep 8, 2009 BIM, Revit

I’ve been doing something recently on my Revit project that I shouldn’t be doing. The fact that I do it actually reminded me of something I would do when I was in elementary school. I would have to write reports on various topics (two of which I have particularly fond memories were, “A Biography of Reggie Jackson,” and, “How the Television Works”) throughout the years and when I would finish writing, my parents would ask if I had proofread it. While my answer would be, “yes,” it was clearly not true.

Why am I telling you this, you might ask. Well, I have repeated this lack of proofreading when cutting sections of my Revit model. I’d cut it, quickly glance it over, fix any glaring errors, print them and show them to my project manager. While there were too many comments to list here, the majority of those comments were graphic-related. It wasn’t that I didn’t know that I was supposed to include those particular things in the drawing, it was that I was a little too anxious to get the it out.

Here’s the thing, while Revit might take your drawings 75% of the way, you still need to look them over. For example, when cutting a section, Revit will thicken the lines that represent the objects it touches. Often times, graphically, it looks better to fully fill those objects (ex. walls, floors, roofs, etc.) with black.

My point is, proofread your drawings before you show them to anyone. You’ll save yourself a lot of aggravation.

Can you think of any other examples of graphical techniques that Revit doesn’t quite do?

– Posted to CADuzer.com From My iPod Touch

Tags: BIM, Commentary, Revit

Have a Cup of Morning Revit…and don’t share it with anyone else!!

Sep 4, 2009 BIM, Customization, Revit

Hey All. As we prepare for the long Labor Day weekend, I had a thought: let’s stop selling Revit. I’ll be more specific: let’s stop “preaching” Revit. The different groups have been established and have pretty much dug their feet in. First we have the, “Early Adopters”. They’ve been using Revit since the Hoover Administration and bleed Revit purple (or dashed blue). Next, we have the, “Whatevers”. Their motto is, “You want us to use software package B now instead of software package A? OK. Whatever!” After them we have, “The Tryers”. These people recognize the benefits of it and are willing to try it. If they like it, they’ll not only continue to use it, but they’ll insist on using it for all of their projects. Finally, we have the, “Nay Sayers”. They don’t want to be bothered. They aren’t interested. To put it bluntly, they don’t care. From these people you’ll hear phrases like, “I don’t have the time,” or, “I’ve heard it takes too long to learn and use,” or, the one that gets my blood boiling the most, “I know Revit is a cool tool, but…”

As Ayn Rand once said, and I’m paraphrasing here, “I’m not here to convince you that this philosophy is the best one or is the one you must adopt. It is logical.” As James T. Kirk once said, “People can be very frightened of change.” (He also said, “What does God need with a starship,” but we won’t hold that against him because he also said, “FIRE!!” and “KHAN!!”). Anyway, the point is, do you think there’s anyone left who doesn’t know what Revit does or how perfectly suited for Architecture it is? Let’s move on to what it took us a long time to realize that AutoCAD needed: standards and best practices. Basically, what Revit needs to be pushed ahead is a better architecture firm framework within which to work and excel. Now, here’s the stimulus package-sized dollar amount question: Which of the previously mentioned groups are the best to do this? The answer is, “the Tryers”. They’re the ones who will adopt the software as time goes by and will tell the BIM Managers (who came out of the Early Adoptets group…you know who I am…I mean, you know who you are!), what features and standards they need. Their the ones who will develop the best practices simply by using the software everyday and participating in round tables and user group meetings. Also, they’re the ones who already work with the Nay Sayers, and know how to communicate with them best. Let’s face it, as Early Adopters (of which I am one), we tend to say phrases that sound to the Nay Sayers as, “You absolutely must use this! It’s the greatest thing since sliced bread! It can do anything and everything.” Clearly that’s not what we mean, but that is most definitely what they hear. Let’s try this phrase on for size, “You know what Revit does, I’m not going to try to sell you on it. Use it or don’t use it. And, if you decide you want to use it, I’m here to help.”

What do you think about this? Let me know.

– Posted to CADuzer.com From My iPod Touch (proof-read on my PC)

Tags: BIM, Commentary, Revit

Revit 2010: Think Long and Hard Before Linking Multiple Files Together

Sep 3, 2009 BIM, Commentary, Revit

Hey all. Here’s an update on my project. Within the first few hours of starting the project, I decided that since the were multiple parts to it (a site, four buildings, and walkways and courtyards which connect them all), I would separate them into 5 distinct Revit files. Specifically, the four building files would be linked into the site file. I actually started with a single file but thought that since not all of the levels were the same (ie. level 01 for one building was 110.5 meters while level 01 for another was 113 meters) it would be easier to keep them all separate. Well, that was a good idea for about two and a half weeks, which was when I had to do some serious printing of sheets. Trying to get the right things to show up on the right sheets was a bigger pain than I had originally anticipated. For example, I had to employ many work-arounds to get objects from a linked file to show as solid black where it was being cut by a section (and, yes, I did go into the “Visibility/Graphics” dialog box, overrode the, “by host view,” setting and set the cut pattern for those objects to black). Sometimes it worked, other times it didn’t. When it didn’t, I met my new best friend: Filled Region.

Another time I had to employ manual, almost AutoCAD-like, methods (oh yeah, I went there) was with grid lines and their associated bubbles. If the grid lines either didn’t show up or showed up on the wrong side of a linked file, I literally drew lines (with the “centerline” line style) and circles. I also created extra levels in the view so they would show up as I wanted them to. And, worst of all, all sheets were NOT in the main file (the site file), as I had originally intended. It was just easier to create them in each of the separate building files and link in, as overlays, the other building files (or even the site file in some cases) when they needed to show up. Of course the problem here would be that if I had over one hundred drawings (and it this case I didn’t), I’d have to open up each file individually to print the sheets located within it (which inevitably meant I had to keep an Excel chart of where each sheet was located).

Speaking of opening each file, often times there are problems with your model you might not notice until you cut a section or create an elevation. Therefore, I’d have to open each file each time I noticed a modeling problem in a section view where that particular file was not the actual one I was working in. You also get a bunch of errors when trying to open local files with linked in central files which might not be in their latest form because their local file counterparts hadn’t been saved to central (I’m sorry, synchronized to central) recently.

Anyway, yesterday I decided I had had enough and began the process of re-combining the separate files into a single file. I tried using the “Bind” feature to merge in all of the building files into the site file. For some reason this didn’t work (it appeared to bring in the file, but no actual objects showed up). So, instead, I very simply copied and pasted all of the objects in. I definitely ran into problems of the heights of things (ie. walls, columns, etc.), however, as I’ve been working it was easy enough to change their top constraints to the appropriate levels. Speaking of levels, specifically the fact that there would be multiple “level 01’s”, I made the names of those levels more specific. For example, I might have “Level 01 – BLDG A,” “Level 01 – BLDG B” and “Level 01 – BLDGs C, D & E”.

It should be noted that even after copying and pasting all of the files back into the site file, the entire model was only between 25 and 30 megabytes. Another project I know of, however, has 4 buildings and a site and is contained within a single file and is somewhere between 250 and 300 megabytes.

I think the practice of linking multiple Revit files into a single one is a very good idea. I also think, however, that careful consideration has to be made before doing it and a set of “Best Practices” needs to b established in order to avoid some of the pitfalls that I encountered

Id like to hear some of your stories regarding this topic.  Let me know some of your Revit, linked model war stories.

– Posted to CADuzer.com From My iPod Touch (proof-read on my PC)

Tags: BIM, Commentary, Revit

First iPod Touch Post and a Revit 2010 Tip

Aug 25, 2009 BIM, Commentary, Revit

Hey All. I finally got the iPod Touch app, “Blogpress” working and I thought I’d post a little tip from my current Revit 2010-based project. Keep in mind that you don’t need to model every single possible thing. I came to a point where I was searching all over the Internet for a very specific toilet. I wasn’t going to be doing any renderings nor were there any elevations that would feature the toilet. I ended up making an in-place model, drew the 2D plan of the toilet with model lines, and then copied it all over the bathroom. I could even add parameters like manufacturer or anything else later on. Try it out!

– Posted to CADuzer.com From My iPod Touch

Tags: Commentary, Revit

UPDATE: Revit and 3D Connexion’s 3D Mice

Aug 23, 2009 Commentary, Revit

Hey All.  A few days ago I posted about my desire for 3D Connexion’s 3D mice to work with Revit.  The creator of  Revit3D.com – BIMBoom Revitlution, Gregory Arkin responded with and update on this very issue:

On th3 3D Connexion issue, I’ve spoken to the Revit Project Manager and 3D Connexion directly.  Below are my two blog posts and actions I’ve tried.  I found out at AU last year that over 300 emails were sent to Autodesk and 3D Connexion demanding action.  Bottom line from what I understand, the ball is in Autodesk’s court to do what’s needed for the mouse driver.  I was hoping that 2010 would have solved the issue, but still no dice.  Last year, the answer was that due to budgeting and resources, the mouse driver wasn’t a priority.

http://bimboom.blogspot.com/2008/06/i-dont-know-whos-to-blame-for-this-but.html

If anyone knows anything else or an Autodesk rep (or 3D Connexion) rep would like to comment, please let me know!

Tags: Commentary, Revit

A New Project…and a Revit 2010 Did You Know?!

Aug 14, 2009 BIM, Revit

Hey All.  I’ve been assigned to a new project at my full time job (at SOM) and the decision about which software platform to use was left up to me.  Needless to say, I chose Revit.  The thought of doing a phase of a project (any phase for that matter) in AutoCAD gives me a headache.  Anyway, without getting into any of the specifics of the project, it’s several small buildings on a university campus with a courtyard that runs, more or less, from one end to the other.  I mention this to you because as I’m using Revit, and more specifically Revit Architecture 2010 (64-bit), I thought I would pass on some things I pick up as I ago.  The first one is pretty simple and some of you might already know about it:

• If you want to orbit around a 3D view in Revit, you hold down the Shift key, push the middle-mouse button and move your mouse around.  This causes the view to move around without anything in particular at its center.  Well, did you know that if you select an object first and then go through the orbiting process above, Revit will orbit using that selected object as its center?

Speaking of orbiting in Revit, it would be really nice if the 3D mice from a company called 3D Connexion would support Revit.  Truth be told, I think I heard that Autodesk wouldn’t release the Revit code to make this possible.  Don’t quote me on that, but if anyone knows for sure, please let me know.

Tags: BIM, Revit