Wednesday, November 2, 2011

The Psychological BIM Block

I've been thinking a lot lately about many people's reaction to the BIM movement within the AEC industry.  I've found that the word 'BIM' usually evokes one of three very different reactions.

The first reaction is one of extreme enthusiasm and optimism.  We'll call them "The BIM Believers".  This group really sees BIM for its potential and wants to everyone else in the world to become "One with the BIM".  I find a lot of these people border on BIM fanaticism & what it can/will/should do.  This is great but it often doesn't come across to people in the other two groups in a good, or even rationally sane, way.  Not surprisingly, I find I usually fit into this category.

The second reaction is one of extreme pessimism and cynicism.  We'll call them "The Anti-BIMs".  This group of people get really irritated really fast when anyone mentions BIM.  I used to be an Anti-BIM, before I started to understand what all the BIM Believers were rattling on about.  The reason for this response is usually twofold.  First, they hold they "If it ain't broke, don't fix it" mindset.  They've been working in CAD for XX number of years and they've had no problems with it, thank you very much.  Secondly - and they often won't admit it, this group is actually quite scared of BIM.  I know I was.  BIM presents an entirely new way which projects are going to be run - legally, logistically, technically, etc, etc, etc.

The third reaction is one of complete ignorance.  Let's call these the "BIM Huh?" group.  These people have never heard of BIM and have no idea what you're talking about.  End of.

What I'm trying to brainstorm these days is this...  What's the best way to educate and train the 'Anti-BIMs' in a way which would be engaging and effective? How can this be done in an entire organization or project?  We'll leave the 'BIM Huh?'s out of it because I found it to be less of a problem to 'convert' people who haven't had a chance to form a negative opinion yet.  People that are turned off or threatened by an idea will revert back to their CAD comfort zone the moment no one is watching.  Many of us have struggled through organizations or management which aren't committed to jumping into a BIM transition with both feet.  From my experience, having one foot in and one foot out of BIM world for a project is bad news, and requires vigilance, air-tight QAQC controls, and substantially more hands-on management of information.

My father is an organizational psychologist with the US government's mining safety program.  You can probably guess who gave me the idea to start thinking about BIM implementation from an organizational psychology perspective.  He co-wrote this article on on-the-job training, which I think is very relevant.  I'm in the process of reading it now, and I will update with further comments/ideas once I've had a chance to give it a thorough reading.

What experiences have you had with BIM implementation within your organization?  Was it difficult (dumb question)?  What methods, techniques, tips or ideas did you come across which helped the process?


Friday, September 23, 2011

Linking BIM to Field: An Introduction to Artra

This week, my team and I attended an webinar which introduced Artra's BIM-to-Field software suite, arranged by Motion Computing.  At my first meeting with the Motion Computing sales rep, I was very impressed with the tablets and the software options available to the contractor to go paperless with many site-based CM functions.  However, I'm a BIM manager and not part of the contractor's commissioning team, so I was going to need another solution if these were going to be of any use to me and my client.

I was introduced to Artra through a conversation I'd had with my project's MEP BIM manager, who had heard great things from some of his colleagues in the UK (which is where Artra came from).  A little research quickly told me this might be exactly what I was looking for - a light program able to run on a tablet using a BIM-external database system to allow the contractor to input information relevant to the project as it's being built.  The premise is quite straightforward & creates a very logical extension of BIM's application.  After all, BIM is Building Information Modeling, which to me means not just the Revit/Tekla/Bently/Archicad/etc files themselves, but a digital conglomeration of all relevant building data linked in a dynamic environment.  Many people still think 'BIM' is just the authoring software, which is something I really feel is a misconception and have a responsibility to help change.

But anyhow, getting back to the subject at hand, my greatest challenge as a BIM manager is to make sure that the right people (1) are updating this digital conglomeration in the right way (2) at the right time (3) using the right tools (4).  Is Artra the right tool to get my contractor linked into my BIM?  Here are my thoughts...

Artra Pros
  1. The Contractor would not require editable access to the native BIM file to input their data.

    This is huge.  Huge, huge, huge.  The task of ensuring and maintaining data integrity is something that could drive me to drink at times and is one of the most dangerous parts when dealing with BIM.  I have enough of a challenge making sure that my BIM modeling staff, trained and experienced using the various software authoring packages we use, are modeling accurately and then not accidentally messing it up afterwards.  The idea of granting anyone editing access to the native models in the field is just inconceivable, let alone completely impractical.  No tablet - regardless of how awesome - will run Revit in any practical way.  With no guarantee of 3G or wireless access on site, the models would   become frozen in the field.  And imagine trying to train someone up to edit native models?  The other solution could be Navisworks - which is substantially lighter, easily run on the tablets.  But it's not made for this purpose and would be difficult to use practically.  In fact, Artra is Navisworks-driven, meaning that it IS Navisworks (See point 3), framed nicely with custom made tools and a very useful external SQL database. Artra sidesteps all of my data integrity issues and allows me to maintain my current level of confidence in our models.

  2. The software seamlessly transitions from a construction management to facilities management tool.

    The contractor will actually be creating - with no additional effort, time or cost on their part - the information database the FM team will need to have the BIM be at all useful to them.  One of the many problems in BIM specs I see is that owners have been sold the idea that BIM - along with a bunch of really cool looking screenshots, fly-throughs, and renderings - will solve all of the FM needs.  Owners then buy this from the contractor, but have no actual plan of how the FM will use the BIM their provided.  It's like buying a lightbulb, but having no lamp.  What's the point of buying it if you don't have a tool in mind to actually put it to use?  Effectively, Artra is the 'lamp' and it seems like a bright idea (yes, pun intended).  The FM will have the BIM delivered to them with all O&M documentation, commissioning information, MSDS, original IFC drawings, sketches, RFI's - you name it - at their fingertips in this interface.  And the contractor would have already done this because it's useful for them as well.  Very cool.

  3. Navisworks-Driven BIM link

    I've really come to like Navisworks, though I had my frustrations with it at first.  It's a great platform to bring together all kinds of BIM in their native authoring formats, which is the best way, in my humble opinion.  It can fall back to the IFC if required, but usually it is not.  Building Artra around Navisworks is a huge plus, in my mind, because you can have a good level of confidence that all of the information in your BIM will find its way to the 'other side' in Artra.  On top of that, there's no new complicated viewing software to struggle with learn.
Artra Cons
  1. The Interface

    This is pretty much the only con I can think of right now.  The Artra data entry and access interface is a bit too techy for the average field guy to ever be comfortable with.   This problem would be compounded exponentially for me, as language barriers and less-than-cutting-edge construction mindsets in the Middle East would make this just... difficult. If I was in the US or Eurozone, I would perhaps suspend my doubt and try to train up some of the more computer-comfortable field staff on this.  But in the Middle East?  Hmmm...

    Snagging and tagging go well together.  No?

    This could be best solved by actually allowing the field guys to input the required tagging data by doing what they're used to already doing - filling out forms.  Create a report sheets on the tablet identical to the ones they'd need to print out when they got back to the office anyhow, similar to snagging tools already developed for the tablets.  Let them check, tick, write and snag away.  Then, create a little piece of programming which allows a more tech-savvy CM to map the field entries on the digital sheets to the Artra SQL database.  Perfect, yeah?  And I'd create an interface which removes about 90% of the buttons on the screen.  All they'd need is a list of their forms to fill out and the librarian, which allows (again) a more tech-savvy CM to link all digital documentation to the BIM elements for quick reference.  Bingo presto.

    To give Artra the benefit of the doubt, though, they do seem very keen and able to write programs to allow Artra to interface with other software.  Maybe they could whip something up to do this.
So, thoughts?  Have you used Artra in the field?  How did it go?  Is there any other packages which do this same thing which you would recommend?  I'm all ears.

Tuesday, September 20, 2011

Statement of Purpose

Well, here I go again starting another blog. This is the first professional blog I have ever attempted, and as I have a clear purpose for doing so, I think this one will work out a bit better than my last attempts at writing one.

The purpose of this blog is to provide a forum to explore everything* that is out there in BIM world. I am the structural BIM department head/de-facto project director at a small (but quickly growing) BIM consulting firm called iTech, headquartered in Abu Dhabi, UAE. I worked as a structural design engineer out of NYC for several years before relocating abroad to the Middle East to find something a bit different and to escape the depressing aftermath of the 2008 recession in the NYC AEC industry.

Joining me will be several of my colleagues, who are BIM managers of their own respective disciplines.  I'll let them introduce themselves once they are up and running here.

I have learned oodles about what's going on in BIM world through my professional experiences. One of the things I've learned is that the learning never stops in a field where the technology is ever changing & some of the brightest minds in the AEC industry, academia, software & computing worlds are quickly developing many tools to improve how we all get things built. In fact, there are so many things going on that I can't wrap my head around them, and I don't know where to start. So, with this blog, I am going to be exploring what I can in terms of what is out there, whether what's out there works, and whether what works is out there. I'm sure I'll slip a few anecdotes along the way (or anecdon'ts, if you will).

By writing about this, I hope to encourage myself to continue in this pursuit of BIM understanding and make myself a more knowledgeable BIM professional. I hope that I can also help a few other people out along the way, and hopefully also have those same people help me out where they can. I'm sure to have a lot of questions.

Cheers!

(*everything = as much as I possibly can)