Revit isn't BIM - My epiphany of the day

This past Thursday morning, I stopped by the office of one of our largest Revit MEP clients. I went to see how Joe, our Revit MEP/Structure specialist was doing. He was there for a day of advanced implementation strategy.

Much to my surprise, an architect from a firm just barely starting to use Revit Architecture walked into the room. A little later I was having a conversation with him in the hallway when it hit me. Revit is not BIM. I never really felt it was, but this was different. BIM is a concept, not a piece of software. Revit is a piece of BIM.

So here we had a firm using Revit MEP and the architect came to learn from us how to coordinate Revit Architecture with Revit MEP. Now that's BIM! An architectural and engineering firm sharing the model early on in the design process and coordinating the project. For me, this will mark the day that Revit truly began to replace 2D and AutoCAD.

Now comes the scariest part. We've done the training for the Structural and MEP firms involved in this particular project. The architect chose our competitor to do their training. Only problem is, they don't do Revit Structure and Revit MEP training. They don't do coordination and collobartion between Revit Architecture, Revit Structure and Revit MEP. So there's the architect, furiously scribbling notes so he can glean as much information from Joe as possible and I'm glad they're tagging along on our technical specialists and can rely on us for Revit support.

So, as I'm standing there having my epiphany, I'm thrilled that we're getting architects and engineers using Revit they way it was meant to be used (together) and thrilled that our firm has become such an integral part of the use, growth and success of Revit A/S/MEP in Florida and nationally. I can only hope that you get to have this same feeling sooner than later, as it's really nice to know that you can make a difference in the world of architecture and construction.