«

»

Jul 17 2014

The Importance of Validation

You see BIM software vendors using the terms validation and checking interchangeably.  When in fact they are really don’t complete the same function.  There is a great difference in the actual level of accuracy between the two methodologies with validation the only way to ensure your data is truly accurate and really correct.

Validation goes hand In hand with BIM! Or so you may think. Truth is there are many, many sides to the validation notion.

Validation is not simply checking if an item of FF&E is in a room, Revit will indeed create an equipment schedule giving a count of what items are located in which particular space. Validation requires more than this however, what good is validation if you have nothing to validate that information against?

That Chair-CHA004 may well be in the on call room… but is it supposed to be?

  • Was it swapped out for a different unit?
  • Did the client decide that a different item be used for cost savings?
  • At what stage of mark-up’s was this item removed?
  • Who did this?
  • When did they do it?
  • What was it swapped for?

This of course scales up when dealing with multiple FF&E models in Revit

  • How do you produce a validated report across multiple models with all of this information?
  • How deep does the rabbit hole go?

The truth is, currently it’s not possible to do this using “just” Revit!

And that’s where CodeBook Pro comes in finding solutions to problems you never knew you were going to have…yet.

These are not new issues to BIM these are historic issues to the industry. With BIM now – it’s becoming a contractual responsibility to be able to audit and document this information.   In a world of federated working this becomes even more important as knowing who changed what is almost as important as why and when.

CodeBook Pro’s Validation Solution

I’m going to try and avoid getting to “techy” with this but there are a number of ways this can be easily dealt with by CodeBook Pro.

1)      Image databases – often overlooked in CodeBook but at its core, it allows a snapshot of a project to be compared to any other snapshot, any changes are reported on whether it’s an item which has been moved, been omitted or even a wall finish that has been changed. CodeBook Pro provides an audit which can report on this information as well as date of change, and who performed this.

Summary:

a

Designed Equipment:

2

 

2)      Required Equipment List – There is more to this list than meets the eye, clicking “Show Properties” it loads a sub form in which audit information can be entered such as reason for update, notes, omit option, dates, as well as condition, size and asset data.

3

 

3)      Multiple Required Equipment Lists – This is a relatively new feature which you may not be aware of.  CodeBook Pro now has the ability to store multiple required equipment lists. This makes it possible to have a brief equipment list and a multiple stages of mark-up lists and switch and report against the difference at any point in time.

5

 

 

4)      Multiple Model Reporting – Because all data is linked back to a central database even if you have FF&E and Rooms spaced across multiple models, CodeBook Pro can validate, and report all of the above using the reporting tool. This is even true if the FF&E does not exist in the same model as the Room.

5)      MEP – Here we can get a little clever, because CodeBook stores the room boundary in the database and checks against the model rather than simply reading the Revit schedule we can use Navisworks as an intermediary between none Revit platforms. As long as the models are aligned CodeBook Pro can read in the “as is” equipment and perform a comparison against the requirement for that room/space.

If you have any questions or would like clarification or a demo of the above, please contact Support@CodeBookInternational.com

Thanks for reading

Sam Oliver, VP Global Operations

 

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>