A place for Revit updates, Revit news, and Revit information.
Starting with this inaugural post Revit Furniture will start posting interviews with some of the top bloggers of the world. Our first Q&A session is with Luke Johnson of "What Revit Wants" Luke hails from the down under, and his topic of preference is how a person "thinks" when using Revit. He has vast Revit knowledge, and is a systems Manager at Dimond Architects. As you will see below Luke is smart and has a lot of insights to offer.
More specifically, in this session you’ll find out about:
1) Luke could you tell us a little about your background? Where you went to school, where you work, and what your passion is?
I grew up on the Sunshine Coast in Queensland, Australia. It is a beautiful place, and I have enjoyed living here very much (now with my wife and two small children). I have been working at Dimond Architects for the past 8 years. It is a firm that punches far above its weight - by that I mean that it is a relatively small operation, but the Directors have strived to keep pace with current technology and practices, and we have been involved in a number of significant projects throughout Queensland. You should watch this space, however... I'm moving to Adelaide in June, and will be starting work in a new firm - more details on this later!
My passion is really my family - in the end, I enjoy working with Revit and 'collaborating' in the BIM sense of the word, but we all have to go home at the end of the day. For me, I love that moment when you get home and the kids are there waiting to give you a big hug. Its like, working hard and working full time is really worth it, if I can provide for my family properly.
2) When you are approaching creating a project in Revit, what sort of questions should you be asking yourself? What mindset should you be in?
You really do need to pause at that moment before hit 'New' to make a new project in Revit. What sort of project will this be? What is the timeline and project program? Are we under severe time pressure, or can we set this project up to be something that is 'solid as a rock' in terms of best-practice BIM? The right mindset is important.
Try not to stress too much about the software. Revit can seem daunting at times, but in the end, it is a tool for accomplishing work. You are in control of it, not vice versa. At various points in the project lifespan (including those formative moments when you are setting up a model), you will have to ask yourself "What is the best way to accomplish the project goal?" Do you need to model everything in 3D? Is it more important to set up smart parameters for scheduling and tagging - perhaps making the model super intelligent but not necessarily super detailed Will you be the only staff member on this project, or do you need to determine some way to logically divide the modelling tasks between users? Are you going to go through many sketch iterations and rapid changes early in the project, and do you need to track these (think Design Options)? Is the model ever going to be a deliverable, and does it need to comply with any particular standard - either an internal one, or perhaps a BIM standard enforced by some regulatory authority?
3) What mindset or thought process is counterproductive to working in Revit?
There a few that immediately come to mind. Some questions and thoughts are actually a waste of time and emotional energy, like:
You really need to commit to using Revit. Yes, it can be a difficult learning curve. The initial excitement quickly wears off, as you are faced with numerous choices you don't really understand, and this long list of "I don't know how to do this" tasks. But you will learn. You have to. Revit is not going away - it is becoming more widespread every day. Just be happy that you are sitting there using Revit - you have been given a great opportunity for learning and advancement. But you need to be open-minded, quick to listen and learn and ask questions, and slow to give up. Stick with it, you won't be disappointed. All the little bits and pieces will start to come together and 'click' in your mind, trust me.
4) If you were teaching someone Revit what outline would you give them? What would you tell them to learn first, second, and so on..
I think one of the best ideas is to take an existing set of CAD documents (preferably from a building that you have drafted), and redraw that building in Revit. You have the advantage of knowing what the building looks like and how it goes together - you just have to try to recreate that in the software. Don't be too stressed about making every little graphic element look the same between the drawings, but do try to use good modelling technique from the start. Model elements on the appropriate Category and using the appropriate tools. When you are starting out, at least make an effort to fit in with how the program is 'supposed' to function. You can start to bend and break these rules later, when you understand the pros and cons of what you are actually doing...
After doing some basic modelling, I would recommend spending some time doing some tagging and scheduling. Experiment with things - what can you tag, what can't you tag? How can you manipulate information in Schedules, total certain columns, export to Excel. I think its important to expose yourself to the fact that elements in Revit have 'intelligence'. Sure, you can see them in 3D. But the real beauty and power of Revit is that everything is linked together to the underlying data related to an element.
5) What is a Revit trick, shortcut, or way of doing something would you wish someone would have told you long ago?
I'll give you four:
6) What is the most common mistake you see in revit models or building revit content?
In the form of a rant - If something is a wall, use the Wall tool. If its a floor, use a Floor. If its a benchtop, use Casework. I may seem to be labouring the point, but one of the most frustrating things that I consistently see is the complete misuse of one Revit tool or category, when a better and more appropriate option already exists!
As far as content goes, I think the biggest mistake is over modelling or making super detailed models. Trust me, from time to time I am guilty of this. But it comes back to setting a content goal - what is purpose of this content? If it is just to fill up a schedule, use the most basic form you can get away with. If something is unnecessarily detailed, it can really slow a project down.
7) If you were passing by a student in a hallway and you could only impart 30 seconds of Revit wisdom on them, what would you say?
Revit geeks are generally better paid and more employable than those with a Phd in Architecture. If you want to succeed in Revit, take the time to get to know it properly. Spend time reading up on best practices. Subscribe to blogs and Twitter accounts of professional Revit users. And some student-specific wisdom - its fun to learn how to model crazy and organic forms in Revit, but in a real office, you might spend about 5% of your time doing that. Over 80% of your time will probably be spent using Revit on a real building. So try to learn how a building actually goes together. Go on site visits. Do some construction labouring. If you know how a building is built, and you know how Revit elements are related to real-world building elements, you will go far.
8) Where do you see the future of Revit, what is it's significance, and potential?
There is a lot of talk about 3D printing, CNC, direct to manufacture modelling. And I do think things will continue to head that way. I guess one of the big unknowns is "how much will Revit end up doing". I'll try to explain - Microsoft Word is a great tool. It has been around for many years, and has gone through many many versions with features added to each version. But in the end, it is still just a word processing tool. You need Excel for spreadsheets, Outlook for emails, Powerpoint for slideshows, and so it goes on. So where will Revit end up? AutoCAD is a great drafting tool - fast, accurate, powerful. Its 3D engine is very strong. And yet there was room for Revit to develop, grow, and now flourish. Will Revit become an 'all in one' building model management tool? I actually hope that it does. I would love if it became the vehicle for all building elements and systems to be created, integrated and linked together. I want things to become simpler - I want to deal with less pieces of software, not more.
A few things need to happen - cloud integration and Revit needs to become a reality. Something that is fast, user friendly, reliable. Is part of the solution to use hosted Revit in a Citrix type environment? Perhaps, but there are performance problems with that at the moment. Revit Server is good, but requires a certain commitment in terms of setup and maintenance.
I kind of have this dream that Revit and VEO somehow get smashed together - bringing VEO's awesome speed and cloud intelligence, and combining it with Revit's powerful parametric engine and content creation ability. Can you imagine the benefits to collaboration speed? A single BIM super-software. Bring it on!
9) Is the anything else you would like to add that we didn't cover?
I'd just like to thank all of the followers of What Revit Wants, those who have liked the Facebook page, and my Twitter followers. Sharing information about Revit is something I enjoy, but it really is a team effort. So many people have helped me over the years, and I hope that I have been able to pay some of that forward. Thanks!
If you enjoyed this post pleas share it with your friends by posting it on facebook, or tweeting it by clicking below. Thanks again for reading. If you haven't read our "What is Revit" article click here.