Three Laws - Family Content

This is repost of a post that I wrote in September 2008. I thought of it as I was working through some content tasks.

Not to be confused with Isaac Asimov's "Three Laws of Robotics", I first heard of the so called "three laws or rules" of software development from my father who spent many years working at IBM. These so called laws simply represented a philosophy about how to get something accomplished as efficiently as possible for the least cost (not always in terms of cash either). When I read Code Complete by Steve McConnell he mentioned the "Buy-vs-Build Decision" that developers should consider as they design/develop an application. It might seem radical to buy a solution when you are focused on making something yourself.

I've personally kept these in mind when thinking about content for Revit and even AutoCAD/ADT/Microstation before that.

Law One - Borrow
Law Two - Buy
Law Three - Build

Law One - Borrow
I can hear the cynic saying, "you mean steal". I'm sure that has happened too often. However the idea of borrowing what has been shared made the early adopters of Revit very special to me. Their willingness to make something that took them several, many hours in some cases, and make it available to others was and remains refreshing, altruistic. Guys like Chris Yearick (Yman), Scott Brown (sbrown) and Chris Zoog (czoog) to name just a few, their AUGI usernames in ().

Have you used the "All Windows" families found at Revit City? Chris Yearick (Living Places part of The Pilari Group) made those many years ago now and posted them freely at RUGIE (no longer in existence) and they found their way into the Revit City content as well as AUGI's Exchange and other places I'm sure.

Scott Brown (now with Beck Group) shared his office template as well as many standard office/product detail components and views which short circuited the time someone need to spend on their office template substantially.

Chris Zoog (now with HOK) started Zoogdesign and created a vibrant community resource for Revit discussion. It eventually merged into the Revit community forum at AUGI.

More recently an AUGI member known as CadKiller has made an ftp site available to share templates in the same spirit.

Law Two - Buy
There is something to be said for the education of making something yourself but if you can't perform billable work during that time it may not make economic sense to do it yourself. It may not make sense to have anyone in your employ do it either for the same reason. Worse yet all too often I find that a firm's different offices have made the same content themselves without realizing that someone in their own organization already made it or bought it. So communicating what is available is pretty important too...and another topic entirely.

Law Three - Make it yourself
Like I wrote above there is nothing quite like making something yourself for both satisfaction and reaching a fuller understanding of the Family Editor. At times this is the best solution or perhaps the only "affordable" way to get precisely what you want. Just be prepared to apply these same "laws" to how you acquire any knowledge you lack, maybe in a different order?

Here's to being "Law" Abiding!

Edit: Realized that the people mentioned are with new firms now, revised.

BlueBryk and Content

I recently spoke with Bruce Madsen. I had the pleasure of sharing a dinner table with him and his wife at RTC in Auckland. One of the things he's struggled with (we've all struggled with) in his work at HOK is finding and keeping up with all the places that we can find content. He's been quietly compiling his own lists and keeping track of this stuff and finally decided it was time to do this in a more formal way, organized and in a way that allows for broader participation.

This is where BlueBryk comes in.

I should take a quick step back and explain that until now Bruce has been working quietly in what he called a private beta. I asked him if he was worried about word leaking out... Since I'm the leak, he's really hoping to get more feedback about what he's built so far, to see how well it fits and meets our needs. I really need to remember to ask him about the inspiration for the name but I'll ignore that for later.

The site is not a place to find and examine a specific cabinet or pipe fitting, at least not at the moment. It is a place to find recommended places to find content. It is a compilation of all the places that he's documented as providing content, not the specific content that is available.

If you visit the BlueBryk site you'll find a clean organized place (a bit of expected blue here and there too). At the very top is a button called "Why Register". That was my first question too, with a cynic's mindset, "Why do I care?". The first reason offered is access to advance searching criteria, which is certainly valid. I think the biggest reason is to give me access to voting on content providers. After all if I really want to make the site work we all need to give feedback into the quality of the content we find. Autodesk's Seek, the more or less obvious "competing" resource, doesn't really deliver on real user rating systems (we can submit feedback), at least not in a "social" way.

After submitting the info as shown above the results are organized alphabetically and the BlueBryk rating appears on the far right.

Links provide access to the websites for each provider, which belong to any one of these categories: Content Exchange, Consolidator, Content Building, Content Store or Manufacturer. In this way the site is a much more elegant delivery of the kind of information my own Revit Inside blog has been doing for companies that use Revit.

The goal of the site is to do a great job of keeping this information current, relevant and reliable...useful. At the moment Bruce reports over 1200 resources are to be found within BlueBryk. If I'm hunting for the perfect supply grill for Revit MEP there are a lot of manufacturers, the question is who provides Revit content? Ideally BlueBryk will make it easier to see which companies or sites provide a matching range of content AND see which ones are highly rated by BlueBryk AND us.

Now that I've mentioned his site, Bruce hopes you'll check it out and help him make it a very valuable resource for all of the Revit (and the broader BIM) community. Have a look for yourself and click the Contact Us button to offer up your thoughts. He's incorporated a blog into the site too so he can provide timely information. Look for him to write posts that help explain what his vision is and where he hopes we will help him take BlueBryk.

Fwiw, another product called Unifi also takes on this problem with at least one big difference, its integration into Revit as an application. BlueBryk is solely a web resource. I don't know if that is a negative or a positive for either but my gut instinct is that not being an app makes it a bit simpler to use it as intended, as a resource, instead of adding yet another thing to manage during deployment for Revit.

Family Naming - Don't Worry

Jose Fandos of Andekan posted again in his continuing theme of content related posts. He suggests that worrying about a family naming standard, an all-encompassing one at least, isn't our biggest priority. I agree, I've always preached consistency instead of specifics. Every firm I've met over the years has their own position about file and folder naming for every kind of software they use.

He (Jose) predicts that how we find content in and out of Revit will only get better as we move forward so the actual name of a Revit family may become less important as a means to find one. For example, the add-in Family Browser allows us to organize content logically and the name isn't really the focus (while it, a standard, does help organize the folder the content is in perhaps).

If by some chance everybody could agree on a standard strategy it wouldn't hurt us. I don't think it is a fundamental or major priority over actually having content created. If it gets made with a "bad" name, I can always rename it when it hits "my" library anyway. ;)