Why Clashes Exist in BIM At All with Rubens Lage Lopes

And I know you're passionate about coordination, and w- we know coordination is about, it's, it's about people, it's about software, but when you walk into a project, how can you tell whether the coordination proces- process is working or not?

Yeah.

I...

The first thing is, like if we have a process, you know?

Mm.

It's not just people jumping into the meeting and then throwing models, uh, on top of the other.

Like, I, I followed this, uh, follow process.

Like, first we need to define what good coordination means, like what well coordinated means.

And then to get to that, we need to, to understand, okay, uh, what kind of project is that? What are the priorities? Uh, what design phase are we? So if you're in the concept design, so of course you're not running clash detection all the time.

You're not like, uh...

You, you need to first care about the concepts with concept design.

And then, you know, um, so if I see the project, we have a process and everybody's clear what are the goals and targets and what the standard, what's acceptable and what's not acceptable at each design phase, yes, I think, okay, we are heading to a good process.

We are heading to good outcome.

But otherwise, like it's gonna be a mess and back and forth.

Yeah.

And, and sometimes, you know, like in projects, coordination is oft- often treated as a software problem.

Um, people fighting between which software should we use to-

Mm

... coordinate this specific project.

Uh, but, but probably feels like it's more like a people problem, right? People and maybe accountability problem.

Why do you think that people still confuse these two, like dif- prog- software versus people process?

Um, I, I, I think I, I, I used to do that as well, like, because I like the technology, so I want to solve everything with technology.

So, you know, like had a little piece of software.

There we go.

That's gonna solve my problem.