Sunday, June 19, 2011

Comment Tracking Using Noteblock Scheduling


A long time ago, I came across a very talented young man named Justin Rumley who was working for a facade manufacturer in the Mid-west on the Sprint Center.  He was giving me a model of all the facade embeds and parts and pieces.  The model was very good, very accurate, but i asked him why he had done it all in Sketchup when there were so many other more sophisticated tools around.  His comment was very straightforward and i have always remembered it:

"Sometimes SMART is DUMB, and DUMB is SMART"

This statement alone could be the basis of a lengthy discourse....for another day.


I recently had a brief email discussion with some other voices from the blog-o-sphere about the various strengths and weakness of the many available 3d and online collaboration tools.  How some of them don't yet play well REVIT....tracking documents, comments and changes is still a bit of a hassel...etc. holy grail yet exists...


The builder/client for my current project is very dedicated to using Revit and has trained up a crew to both review our models for coordination and manipulate the models for their own use.  A coordination reporting work flow was developed where they would:
  1. Create a model called COMMENTS.RVT
  2. Link our submitted design models into their COMMENTS.RVT
  3. Create a series of sheets with plans, sections and 3D views to illustrate the coordination errors.
  4. Print and send us PDFs of these sheets.  Just PDFs, nothing more.
A rather simplistic method to communicate errors, but effective for certain...yet one problem existed.  Their comments were all made as simple text with leaders on the sheets, thus couldn't be tracked without a ton of additional, separate effort.  I watched the guy on the architectural team struggle as he spent more than 2/3 of his time organizing the comments into an excel spreadsheet so we could respond/act appropriately.  A similar amount of time is wasted finding a view in our own models to examine the problem

We spent far more time organizing the data and finding the problems than correcting the errors.  Effective system? Yes. Efficient system?  HELL NO!

BIMTroublemaker to the rescue!

Trying to get the team to start using navis to review and generate comments isn't really an option.  Additionally, the documents they were sending us were extremely effective at describing the problems.  The problem lay in how comments are generated, tracked and resolved.

I recently found the NOTEBLOCK schedule in Revit's bevy of scheduling tools and realized that a solution could be found there:

This schedule will track pieces of annotation and their parameters.
 Sooooo....I made a simple generic annotation that would graphically show a comment and a number:
 I loaded additional text parameters in the family like this:
 unfortunately, i couldn't automate either the sheet/view reference or the errant condition locational parameters....maybe on the next job.

but now, i can schedule generate my note-block schedule and i get:

 But wait, there's more!

Because I have taken the FUZZY MATH ESSENTIALS course at AU, I was able to figure out a slick way to make the comment change color according to its status!  The trick with this is controlling status through a series of fixed check boxes.  There is even an error message that comes up when more than one box is checked, or no boxes are checked!

This is the programming if anyone is interested:

Sure, navis and tekla bimsight and horizontal glue are really great programs.  I like them.  But this tool works in a very simple and DUMB work flow:

  1. Client sends me his COMMENTS.RVT (sans links its less than 5mb) along with a PDF print out showing what they want to illustrate
  2. We open the COMMENTS.RVT, link in our current design models, which will then show up in all the preset views.
  3. Address the comments accordingly and version the COMMENTS.RVT model
  4. Send COMMENTS.RVT back and forth until all comments are resolved

Yahtzee!  The architect is really happy.  The client guy is really happy.  Dumb is Smart, Smart is Dumb.  And i feel like i did something useful...rather than the other monkey-business i spend my time screwing around with.

Download a sample of the block here:

Trackable Comment Annotation.RFA

BTW, if anyone knows the whereabouts of Justin Rumley, I'd love to hear from him.


Friday, June 3, 2011

Complex Rigging pt.3 - and now for something completely useless

Once i saw Phil Read's crazy star.  I tried to build it and succeeded.  but this was long before i figured out how to use surface patterns and nodes.  This is going to be a little variation on the star things, with a bit of David Light's ideas about helixes thrown in.

Make 3 reference circles with parameter-driven radii.  Connect them and suck in the waist line.

divide the surface so that there are only 2 panels vertically. 

Go to the SURFACE REPRESENTATION and pick NODE.  Place Reference Points on the appropriate nodes.  Pick them 3 at a time and hit the CONNECT POINTS WITH LINES button.  Once you have gone all the way around, you should have something like this

 I placed a reference point on each leg which hosts a circle to make some bones.  I dunno why but i had to do this individually for each leg....and i got this:

I brought the assembly into a project environment, copied it and rotated it a bit and got this:

see...absolutley worthless...