My 10 Golden Rules for working in Revit! 

It's a classic! I always liked this one too; encrypted-tbn0.gstatic.com/images?q=tbn%3AANd9GcScVm9hVU53gnvOYgj0fIP2o4zkzrZQ4_4Xl4nHxhoHqGyerZKK

You're welcome!

Thanks Jose, I'm glad you found it useful! Many of these rules I've had from my very first project so they've done some long yards for sure

You're welcome!

You're welcome!

You're welcome!

Thanks Saugata!

Thanks for the kind words!

Cheers Ali!

You're welcome. hope it goes smoothly!

Thanks!

You're welcome Dylan - glad to meet others of similar mindset born of the same challenge. Good point on container families - forgot about those!

Yes you could leave Revit open over lunch, I just find people still will fail to relinquish/sync in this sort of event as it encourages them to be a bit more absent minded/lax. If the model is slow to open back into it, it's likely a sign there is a bigger issue at hand to solve too.

That's the hard part! Maybe check out 'Guardian' for Revit - if they need tougher love; www.iconicbim.com/guardian

You're welcome Vlad!

Linework tool is OK in that case, but bad where filters, object styles or VG settings get the job done as they're manually controlled. I follow this process: - everyone leave central/locals - copy model and backup folder to archive - detach central copy, save as over top of old central with compact ticked on - sync, relinquish and close

You're welcome Mohamad!

Typically I'd try to use view filters where possible, finding commonality between elements cross category where possible. If hiding is required, it's OK - just avoid it where a more manageable approach is possible.

I use Filters too. Try to find a name convention. I name my filter to what I am filtering ( Category,Type Mark,Comments e.g. Walls_XX.00_1stFloor). Most common mistake is Hide in view and Apply hide to View (Never do so)

Indeed I do! I keep most of my family tutorials in a playlist on my channel. My later videos tend to be a bit more well produced but the older ones relate to family creation best practices; ru-vid.com/group/PLBKwx9iS-LulgrFUYhNddwYLdbG8fjJrt

@@AussieBIMGuru really appreciate your help 😊👌🏻❤️

Brilliant point! I actually do this on large projects also - I typically call them 'container' or 'link' files. So much easier than managing custom view settings view by view or template by template. It's brilliant to be able to call out the site plan at any level too.

Yep partial implementation is far too common these days. Many firms switched over to BIM to compete, but didnt bring an innovative mindset to the table to compliment it. My advice to grads in these types of firms is get some XP on your CV and hunt down the real deal from there. Don't try to teach new tricks to old dogs, waste of time generally in my experience.

Yes working view should only be for 3d working/sketches ideally. Documentation in documentation view, and if you need to work on annotations in those it is ok

Yes it's a shame, a lot of it comes down to Revit's limited degree of precision which causes all sorts of problems. I doubt Autodesk will ever change or address this problem unfortunately - it's deeply wired into Revit. I usually use visible in all views for linked CAD as it's easily lost in the model otherwise. I do a single view only if the CAD file is task specific and likely not to be retained for very long in the model. Ghosting is a method I use on large projects, in this case I usually call it a 'CAD rig', which can be used to set up various linked views to use in other models rather than customizing settings each time in the host model. It also means all the DWG garbage line patterns and materials (render materials) don't pollute the main working models.

Brilliant question, I was hoping a keen set of eyes might spot my example! Whilst I have been forced to work with a myriad of systems at various companies, when I have the chance to 'invent' my default is always to the most tried/tested and proven formula. To me BS/PAS1192 is the best I've seen. I've only been able to use it with an advanced BIM team on a transport project, the builder was from the UK and encouraged its use (as well as other PAS1192 terminology like MIDP/EIR). I would always justify it on merit of usage and future proofing for inevitable mandation. History shows us in Australia that we typically adopt the UK or most proven system in many cases when it comes to law and regulations. Until we have mandation (at least from a systematic perspective) on BIM in Australia it will be a pretty mixed bag, but the major contractors (CIMIC, Laing O'Rourke etc.) are definitely working on forcing ISO 19650 into the market before then if not.

@@AussieBIMGuru OK thanks, that's good to know, if a little daunting! I miss the creature comforts of everyone being on the same page! I've entered a survey company here and was hoping to build a standard "one-size-fits-all" sort of template, though now I'm thinking I may just have to broaden the variety of things within it and delete/adjust accordingly based on client demands as they pop up... its a rather sizeable amount of work to be doing when survey tends to deal with dozens, if not hundreds of projects a year, if all clients are wanting it their own special way! How the end deliverables' file naming formats then fit into a methodology that suits our own internal system is just a quandary I'll have to have a long think about...!

@@christopherhorner6602 yes it can be quite onerous. If you're in a bind always draw on whatever system is in already in place I'd say, then over time guide it to a more futureproof position if it suits. Only so many hours in the working day! Don't be afraid to query client methodology also, sometimes even they don't know which system they should or are using!

@@AussieBIMGuru Hahah, yes, I've already had a poke at one or two clients in my pursuit of understanding the methods (or madness) over here!... I obviously have a bias towards the system back home and would be keen to advocate it, but I'm cautious to appearing stereotypically colonial and imposing Britishness in these foreign lands! It does not help that where survey fits in the chain of events is typically an after-thought to the design process, and often will have little to no input to how projects are first planned out. Alas, 'such is life' as Aussie icon Mr Kelly once said...

@@christopherhorner6602 haha when it comes to BIM we could probably use another re-colonization down under!

I would add criteria to the filters that results in only your elements matching the filter rules. An example would be checking for a parameter value or naming rule that only applies to your floors.

Thank you

Hi Jorg, I mostly relate to cleaning DWG for Revit in these videos: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-scKWMmJjkks.html ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-1_F6YRgY6aI.html

@@AussieBIMGuru thank you very much , sir. you are doing an incredible job. I have never used autocad. thought, maybe there might have been a different solution. Have a great day, and thanks for your engagement.

@@jorgbo3909 you're welcome! There are other programs out there that can read and process DWG files I think, although the key is to clean it somewhere before it reaches Revit itself and messes the model up.

Great advice - I recommend this to anyone using software in AEC, context is key. Column 'move with grids' is probably OK to use, I just suggest reducing reliance on constraintd where possible due to performance and the fact users can't see them.

Every now and then the evil of the linework becomes necessary, I'd say thats one of them! Thanks, I'm in Adelaide these days but hope Sydney is going well.

The easiest way to make links off by default is to put them on worksets with the 'visible' property disabled. Unfortunately it isn't possible to load links in as 'off' in all views or templates.

Hi Mahefa, many BIM consultants sell their content (including myself) to their own bespoke systems. Some examples of companies include BIM Guru (mine), Xrev and Parallax. Some websites out there provide free manufaturer content as well but it's usually not a consistent system. For reference I sell a template and content in packages over here: courses.bimguru.education/ It can be used for projects and education, but not resold by other vendors.

It depends on whether it will assist the design and coordination process,as well as achieve the deliverables that have been commited to. With the right client, putting extra effort in sometimes pays off, but sometimes not - need to read them to see if they will care.

@@AussieBIMGuru I suppose it really depends on the project. Most of projects I have been worked on arent required to that details nor data information. But for sure the more you do the better you get. Thanks.

I prefer to at least keep link worksets broken down by discipline - loading many linked files can be quite timely and sometimes unnecessary. It's up to the team if they prefer one workset I guess; the only major benefit is that people don't have the 'Oh I had the workset closed' excuse I guess!

@@AussieBIMGuru we have broken down our Worksets per discipline as well for the same purpose. I am just thinking 💭 😅

@@sujanmaharjan9182 great minds think alike!

@Pierre Venter precisely, although they are a handy way to quickly turn on/off links as opposed to unload for me i find.

@Pierre Venter i guess... most users I tend to see/use worksets like layers in my experience. Old habits die hard!

Haha yeah my partners to the side trying her hardest not to exist!

Yes there is certainly exceptions to the rules! I know its often much easier to draw up connections as arcs and symbols cant always be in families.

As for any rule there will always be exceptions, I just use it as a last resort instead of a first/lazy way out when there may be a more cover-all approach like view filters. I actually use it religiously when I show roof lines overhead.

@@AussieBIMGuru Sure, shouldn't be the first choice when something can be solved elsehow.

You're welcome!

I'm sure we all learnt the hard way :)

Nice one! Yep these habits definitely transcend culture, borders and languages.

You're welcome!