Tag Archives: 3D model

He’s just not that into you…or BIM

Today I’m going to introduce you to a new acronym.

That’s right. One more.

Just this last one, then we’re through. Done. Kaput. I promise.

You ready? Good.

JAT

There, that wasn’t so bad. Right?

It’s short for

Just a Tool

As in…

Well, you know.

The oft heard sentiment that

“BIM is just a tool”

Here, it’s the word “just” – not “tool” – that triggers my outrage.

And this rant.

So, fasten your seatbelts.

Not “just.”

BIM is not “just” anything.

This blog’s brand is more horse feathers than high horse, more horse sense than nonsense – so accept what I’m about to say as an exception to the rule.

My anger – and incredulousness (yes, it’s a word) – in online discussions and interviews.

The nonchalance of those who declare that

“That’s not a BIM problem.”

As in

“I have a hospital to design in a seismic zone and I have no time to do it. That’s not a BIM problem.”

 Or

“That’s not an issue brought about by BIM.”

That BIM is “just a tool” – like it’s just a can opener or a pair of pliers or a hammer.

If you only have a hammer, you tend to see every problem as a nail.

–          Abraham Maslow

“If we didn’t have it – we’d use something else.”

As in

“No Revit? No problem. I’ll use a stapler.”

At least until BIM becomes a staple in the industry.

These dismissives come from those who are immersed in the technology

Like fish who, it is said, cannot discover water – or like Madge in the 70’s Palmolive ads

You’re soaking in it

They swat away the insinuation that what they are using or doing is anything more than a revved-up 2H pencil with an off-handed dismissive sweep of the hand like they were swatting flies.

But a tool?!

The way that the iPhone is just a tool.

Or the GPS is just a tool.

Or the human brain…

Only that BIM is ALL of these in one.

And the add-ons are BIM’s apps.

App-like tools available for every part of the BIM process.

BIM is not a tool, authoring, analyzing or otherwise.

Apps are tools, I’ll concede you that.

BIM is…

BIM is a process

BIM is our saving grace

BIM is our ticket to ride

BIM is our pass out of here

BIM is our card that says pass GO

BIM is our last golden ticket

BIM is our salvation

BIM is the innards of an intricate clock

BIM is the white horse you rode in on

BIM is the deus ex machina – that arrives at the end of the play to save everything

BIM, the enabler

BIM, the balm

BIM makes IPD possible

And also likely, relevant, necessary and inevitable.

BIM is more than what’s happening on your desktop.

No one would say

BIM is just a process.

BIM is just a strategy.

BIM is not just a technology: software is.

BIM is a disruptive technology. And…

BIM requires that you just focus less on Revit, ArchiCAD and their add-ons and more on process and strategy

BIM is a product

BIM is an IT-enabled, open standards based deliverable and collaborative process

BIM is a facility life-cycle management requirement

BIM is a fundamentally different way of creating, using, and sharing building lifecycle data

BIM is just evolving and will continue to as the capabilities of user and technology improve

BIM can serve as a reliable basis for decision making

BIM is a rebirth of excitement and hope. (T/Y Alberto Palomino, master of the poetry and metaphysics of BIM)

No one asks “Can peanut butter exist without jelly?”

Yes, BIM can exist without IPD as IPD can work without BIM

Just as peanut butter can exist without jelly.

But

WHY ON EARTH WOULD ANYONE WANT TO DO THAT?!

And yes,

BIM is a pretty amazing, evolved, in-process of developing, still in-progress

Tool.

But a pretty amazing one at that. And…

Get on your high horses, people – the Age of Aquarius for design professionals is upon us.

Just as HAL – the fictional computer in Space Odyssey – plus one letter in the alphabet is IBM (H<I, A<B, L<M) so too CAD minus one letter is BIM*

*Except for the last two letters. Shucks.

Definitions of Just BIM

No one would ever say

BIM? It’s just a computable representation of the physical and functional characteristics of a facility.

or

BIM is just information use, reuse, and exchange just with integrated 3D-2D model-based technology. No big deal.

or

BIM is just a single repository including both graphical and non-graphical documents – that’s all.

or even

BIM is just a building design and documentation methodology characterized by the creation and use of coordinated, internally consistent computable information about a building project in design and construction. Nothing more, really.

Why qualify it?

So fuggedaboutit.

There’s no need for the acronym JAT.

BIM isn’t “just” any thing.

So stop saying it.

BIM just is.

Advertisements

10 Comments

Filed under BIM, defining BIM, process, workflow

27 Reasons to read Mastering Autodesk Revit Architecture 2011 now, before it comes out

What are you doing on August 2, 2010?

That’s the day* Mastering Autodesk Revit Architecture 2011 – or MARA2011 for short – written by the authorial triumvirate of Eddy Krygiel, Phil Read and the inestimable James Vandezande comes out.

I may not know where I’ll be on August 2nd – but I can tell you this.

On August 1st I’ll be waiting in line at the Winnetka Book Coop awaiting the 12 midnight book release.

Winnetka – with its trophy kids and designer dogs – hasn’t seen anything like this since the last Harry Potter book launch.

There’s been not a little online and offline buzz about the meaning and significance of the launch date.

August 2, 2010 is a Monday. Except in leap years, no other month starts on the same day of the week as August. That’s significant.

Also, the book is being released while the Sturgis Motorcycle Rally is being held. That’s too bad for the bikers but gives everyone else an edge.

No Book, No Review, No Business

But if the book hasn’t been released yet – how can I reliably review the book without having read it?

The same way that the book’s authors are giving book signings without the book.

For more on this see Book signing – without the book!

It is apparently possible to not only sign books that haven’t  been published but also to talk about books you haven’t read – a practice encouraged in places of higher learning and France.

The French masterpiece How to Talk About Books You Haven’t Read is considered a work of inspired nonsense that answers the question:

What are we supposed to do in these awkward months before books are released in which we’re inclined to talk about a book we haven’t read?

In other words:

How to talk about How to Talk About Books You Haven’t Read if you haven’t in fact read it?

You want to know how I am able to share with you the contents of Mastering Autodesk Revit Architecture 2011 before its publication date?

It’s one helluva story. Here goes.

You may or may not recall that an entire truckload of copies of the new Mastering Autodesk Revit Architecture 2011 book, both weighing and costing an estimated one million pounds, had been stolen just months before the eagerly awaited BIM book was due to appear in bookstores.

The good news is that all of the yet-to-be-sold books have been recovered unscathed – with the sole exception of one copy that had not been accounted for until it became apparent that the “invaluable” (attorneys) prototype was left in a Silicon Valley bar by a disgruntled, as yet unidentified 2D CAD manager and later purchased for an undisclosed sum ($37.78) by Bimodo.com who proceeded to take the book apart page by page to study its substantial innards, dissecting it and posting embarrassing pictures and revealing video detailing its impressive features.

I’d link to the videos but I have to consider this blog’s family-oriented audience.

The authors, who closely guard details about their unreleased books, were too busy disclosing the most minute details of their top-secret book in their blogs to be reached for comment.

As chance would have it I happened to be writing this very post at an adjacent table to the 2D CAD manager in the Silicon Valley bar prior to his call to Bimodo.com –  

a call incidentally, shamelessly and stupidly made on the non-functioning prototype of the next generation iPhone that had also been inadvertently left in the same bar

– and was able to observe the following information about the book while he proceeded to make the dastardly, ill-advised call to Bimodo.com on a wall-hung pay phone.

For those who would like to appear knowledgeable about Mastering Autodesk Revit Architecture 2011 prior to its well-anticipated release, read on.

Mastering Autodesk Revit Architecture 2011 Factoids

Due to state laws forbidding the transfer of smuggled books over state lines I can only share with you a small sampling of what’s in store.

This much we know to be true:

The book runs 976 pages**

Each author wrote the equivalent of a 325 page book (Eddy no doubt one-upped with a 326th page)

The book is written in English, unless you are unfamiliar with Revit.

27 Reasons to read the book now, before it comes out

REASON 1: Reading the book now, before it comes out, will give you a competitive advantage over your competition.

When your competition returns in September they won’t know what hit them.

REASON 2: Aug 2 is a good book launch date.

Your competition is on the beach relaxing, sipping margaritas while you’re sailing by on your inflatable-of-choice reading away.

So clear your calendar. Leave August – the hottest month of the year – wide open.

You may want to keep in mind that August is the month therapists are on vacation. I’m only saying.

REASON 3: The authors – likened elsewhere to Ruth, DiMaggio and Mantle (Yankees) and Luciano Pavarotti, Plácido Domingo and José Carreras (Mets) – held nothing back and pulled no punches – in the scribing of their tome.

On August 2nd, you will hold in your hands everything these guys know. Period.

Having given their all, the authors themselves have been reduced to empty shells, mere husks of their former selves. You’re now the keepers of their content – they’re barely haircuts in suits. Enjoy.

REASON 4: For the same reason you work in BIM and Integrated Design – without everything all perfectly worked out.

For the same reason you work in BIM without the assurances of complete interoperability.

For the same reason you work in Integrated Design without signing a right of reliance (you don’t?!)

You find coping mechanisms and plug-ins.

Patches and workarounds.

Patience, faith, hope and confidence that everything will be worked out in time.

Besides, design professionals for a living envision what is not there.

It is one of our core attributes and competencies.

That is what we do.

We don’t need a book to read it any more than we need a building to design it.

Don’t let the pesky detail that the book does not yet exist stand in your way of reading it.

REASON 5: Get a jump start, before the book comes out, and form a study group. In advance – upon return from summer vacation each employee prepares to present a different topic at a lunchtime lunch and learn. Each employee picks a chapter and runs with it. Does the double duty of providing much-needed presentation experience for emerging employees. Until the release date – you can do some prep work – some of the heavy lifting – prepare a work plan, a study plan, look online here at the table of contents to decide where you will focus first. Or read on.

27 Even Better Reasons + 3 Bonus Reasons

Here are all the reasons you need to read this outstanding as yet-to-be-published book – the best book I haven’t read in ages.

Here are all 27 of them from the book’s table of contents

Part I: Fundamentals provides discussions of key BIM and Revit concepts before giving readers a hands-on look at the Revit interface.

1 Beyond Basic Documentation.

2 The Principles of Revit: Tools and UI.

3 The Basics of the Revit Toolbox.

Part II: The Revit Workflow, explores today’s Revit workflows and introduces readers to templates, worksharing, and managing Revit projects.

4 Configuring Templates and Standards.

5 Managing a Revit Project.

6 Understanding Worksharing.

7 Working with Consultants.

8 Interoperability: Working Multiplatform.

Part III: Modeling and Massing for Design dives into modeling and massing and offers detailed information on the crucial Family Editor as well as visualization techniques for various industries.

9 Advanced Modeling and Massing.

10 Conceptual Design and Sustainability.

11 Phasing, Groups, and Design Options.

12 Visualization.

Part IV: Extended Modeling Techniques covers documentation, including annotation and detailing, and explains how to work with complex walls, roofs and floors as well as curtain walls and advanced stair and railings.

13 Walls and Curtain Walls.

14 Roofs and Floors.

15 Family Editor.

16 Stairs and Railings.

Part V: Documentation.

17 Detailing Your Design.

18 Documenting Your Design.

19 Annotating Your Design.

20 Presenting Your Design.

Part VI: Construction and Beyond, the final portion of the book, discusses Revit for contractors and facility managers, working with Revit in the classroom (high school through graduate), virtualization, working with the API, fabrication for film and stage, and advanced, time-saving tips and tricks

21 Revit in Construction.

22 Revit in the Classroom.

23 Revit and Virtualization.

24 Under the Hood.

25 Direct to Fabrication.

26 Revit for Film and Stage.

27 Revit in the Cloud.

There you have it. 27 great reasons to read Mastering Autodesk Revit Architecture 2011 now, before it comes out.

Want three more reasons to make it an even 30? Here are 3 more bonus reasons:

28 Mastering Autodesk Revit Architecture 2011’s focused discussions, detailed exercises, and compelling real-world examples are organized by how users learn and implement Revit, an approach that will resonate with Revit users of all skill levels.

29 The expert authors developed this practical reference and tutorial based on years of experience using the program and training others to do so.

30 Unlike the competition, Mastering Revit Architecture is organized by real-world workflows and features detailed explanations, interesting real-world examples, and practical tutorials to help readers understand Revit and BIM concepts so that they can quickly start accomplishing vital Revit tasks. 

DON’T WAIT

For the same reason that many professionals should avoid waiting until things are perfect and all worked-out with their technology before jumping-in, there is no better time than now – before the book is published and distributed – to read this insightful guide.

The release date will come sooner than you think – the future is nearer than you think – so act now.

Click here and free yourself.

If you are an instructor, you may request an evaluation copy for this title.

In the meantime, come August 2 – you will have the immaculate door-stopper and show stopper.

Follow the book on Facebook by checking the book out on the Mastering Autodesk Revit Architecture 2011 Facebook page

And while at it, follow them on Twitter http://twitter.com/masteringrevit

Don’t wait. BIM operators are standing by.

* Important Update: Now you really can read Mastering Autodesk Revit Architecture 2011 before it comes out! I just learned from a very reliable source (the publisher) that this post identified the official announced publication date (when they pop the champagne) as August 2 – which remains accurate – but in fact failed to mention that you can get Mastering Autodesk Revit Architecture 2011 from the Wiley website as early as July 12, and from Amazon very shortly thereafter and at most stores where books are sold by July 26. See comment below for more on this. Do not drink and read.

** The final official tally is 1080 pages – the equivalent of each author having written a 360 page book!

16 Comments

Filed under BIM, education, Integrated Design, Integrated Project Delivery, IPD, modeling, workflow

BIM and the Elephant Problem

“With notoriously bad eyesight, forest elephants tend to follow their trunks, using the appendage as a blind person might use fingertips on a stranger’s face-to identify, visualize, gather clues, communicate.”    John Godfrey Saxe (1816-1887) on the famous Indian legend

“Over the last couple of years, the term ‘Building Information Model’ or ‘BIM’ has gained widespread popularity. It has not, however, gained a widespread consistent definition—it’s like the blind men describing the elephant. But there’s a lot of fuss being generated over this particular elephant.”    Jim Bedrick AIA, Director of Systems Integration, Webcor Builders

No matter your stripe, architect, we’ve been hearing and reading a lot about BIM of late. This blog is no exception. (Those of you who are reading this and are heavily engaged in it can skip the rest of this sentence. All others read on.)

BIM is many things to many people. Short for Building Information Model (the thing) or Modeling (the activity,) depending on whom you ask or where you look, BIM is the process of generating and managing building data during its life cycle. Or, if you prefer, BIM is the 3D, real-time, dynamic building modeling software used to increase productivity in building design and construction. Oh, did I mention BIM is a common name for a digital representation of the building process to facilitate exchange and interoperability of information in digital format. Got that? And that’s just three of several dozen descriptions and definitions .

One complaint I’ve been starting to hear is that BIM is something else to everyone who uses the term. Forget interoperability, the logic goes, we can’t even agree on what it is or what it means. As one plucky architect put it the other day, BIM is like Obama: it’s whatever you want it to be.

Two analogies might help clarify. One, the story of six blind men that try to describe an elephant. The second comes from Italo Calvino’s ethereal fiction, Invisible Cities – a favorite among architects everywhere.

From a familiar (and rhyming) version of the legend of the blind men trying to describe an elephant

It was six men of Indostan
To learning much inclined,
Who went to see the Elephant
(Though all of them were blind),
That each by observation
Might satisfy his mind.

The First approach’d the Elephant,
And happening to fall
Against his broad and sturdy side,
At once began to bawl:
“God bless me! but the Elephant
Is very like a wall!”…

The others go on to describe the elephant as a spear, snake, tree depending on which part of the 3D model, or elephant, they happened to grab hold of. The message for those of us wrestling with BIM is clear: like the blind men, it is all in how you approach it. (And, like BIM, there are Jainist, Discordian, Buddhist, African, Sufi and Hindu versions of this tale.)

Charles Darwin used elephants to illustrate the point that organisms produce more offspring than can survive in the world. He called this The Elephant Problem. Analogically, BIM has produced more definitions than can possibly survive. Something must be done about it. But what?

In Italo Calvino’s resplendent fiction, Invisible Cities, as Marco Polo describes the cities visited on his expeditions to Kublai Kahn – about the city of Armilla, which “has nothing that makes it seem a city, except the water pipes that rise vertically where the houses should be and spread out horizontally where the floors should be,” or the spider-web city of Octavia and many other marvelous cities – he is actually describing details (and different takes) of his native Venice. Kahn believes he is learning about many cities when in actuality there is only one.

One city. Many descriptions.

And so there you have it: Many definitions, but only one BIM: a mercurial and multivalent wonder!

1 Comment

Filed under BIM, defining BIM