why architects model

Before explaining "why architects model", I need to clarify what "model" means:

Mo-del verb To insert a 3d object into a file (i.e. a RFA into a Revit model)

It does not refer to any drafting that is done in the file or any of the sheets in the file.

An architect models for 1 of 4 reasons:

• To develop the design
• To communicate the design
• To make decisions
• To document decisions

Except...when they are working with a contractor who could use 3d information...right?

Tocci VC Roles

A quick elaboration on the virtual construction roles at Tocci:

Virtual Construction Planner

• preconstruction-based position, but involved throughout construction
• assess new projects & specific VC needs of new projects
• issue RFPs for creation of BM types
• review DCRs, QAQC issues & deliverables relating to 2d conversions
• push models through middleware for 4d and 5d
• review, assess and provide ongoing VC needs for projects
• manage object library and templates
• manage & coordinate R&D efforts
• manage & coordinate software/hardware needs
  

Virtual Construction Modeler

• preconstruction-based position
• create or manage creation of BM types
• QAQC internally and externally developed models
• create DCR reports

Virtual Construction Coordinator

• operations-based position
• create visual schedules
• update visual schedule
• assist project management and site staff in utilizing model
• update BM types, based on as-built conditions
  

my (new) title

After much discussion and debate, the issues relating to Tocci BIM titles have been resolved!

We have switched from BIM to VC - virtual construction. We have created 3 roles: Virtual Construction Planner, Virtual Construction Coordinator and Virtual Construction Modeler.

I am now a Virtual Construction Planner!

6 Phases of a Revit User

I don't usually like to post on Revit specifically, but when I saw this on Revit Zone, I knew I had to post it. Others may have seen this, but if you haven't enjoy.

I think that the 6 phases can definitely be applied to implementing BIM as a contractor.

Phase 1 - Initial Excitement
Wow! Look at what BIM can do: clash detection, estimating, scheduling! Does it get any better?

Phase 2 - First Bump
Wait - I actually have to model design documents because the architects I work with aren't using it?

Phase 3 - Ignorance is Bliss Stage
This isn't so bad. Creating models isn't too much work. Model a wall, phase it, export a schedule to Excel, clash in Navis. This is nice.

Phase 4 - WTF Stage
I have to change my process!?!

Phase 5 - Enlightenment
Things are starting to make sense. You have begun to develop and implement a process. You aren't completely out of the woods, but you know that you can get through implementation. You are starting to find other BIM-savvy partners: owners, designers, subcontractors and even other builders

Phase 6 - Zen of VDC
You no longer say BIM; you understand that BIM is just a buzz word for something called virtual design & construction. You easily collaborate with owners, designers and subcontractors, without a thought about legal implications. Superintendents and project executives alike reference the model when discussing potential issues.

I think that we're in phase 5.