YouSaid · the spoken record

Marcelo F. Garcia

lines on the record
68
first
2018-06-14
most recent
2018-06-14
sittings or episodes
1
sources
podcast

Every line below is reproduced as it was said and linked to the record it came from. Nothing here is summarised or generated. Directory · Search · Corrections

  1. DPR tries very hard to create a plane from the initial set of documents or at the very beginning of the project, but then to continuously execute on that plan has to be revised because the job site is so dynamic and there are changes coming down.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  2. So, you're saying that that initial fracture kind of happens at the very beginning because of plan versus execution. And then that ripples out in a million ways and makes it impossible to get feedback

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  3. I mean, just informal And certainly not on a project, not from week to week, not on projects, not across projects, not across the company, not one, whether it was on schedule, whether it was on performance, on quality. We could not find it. There was a lot of use of building information modeling. There was a lot of using construction management methods, but nobody actually really formally closed the loop to read. And that is actually much harder to do because of the scale and amount of nature. And that's where really the technology we're seeing now emerging will make it easier to create a plan that matches how you can collect data in the field.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  4. There is an attempt at feedback. Yes, we do have a quality assurance programs that are put in place, and we do have people doing visual checks, and we do have a lot of walks with the architect. We have things called rolling completion lists that are things that we need to complete that the architect would like to see happen. But there's a lot of human interaction there that doesn't always capture the true intent of the design. We have the saying of measure twice, a cut once, and then it's like Do quality check that twice after that

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  5. Well, let me ask you about when you say without any feedback, I mean, isn't the contractor standing there assessing, keeping track of things, even with a clipboard, there's an attempt at feedback, wouldn't you say? Or no?

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  6. Every step is different. Every step is different Time feedback An inch off. On the dependencies. So there are just some human limitations in assessment of quality and progress just because of the amount of stuff that's going on on a construction site.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  7. I know Limitations Hey Construction And they've got real time feedback. So if something doesn't go as planned, you can intervene in three minutes and fix the problem. Whereas in construction, you're building this massive thing once with different people and materials every time.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  8. You would think that a collaborative project, they would say we can do all of this great stuff. But it's not what I have experienced on projects. Then from there, it does grow into people then realize, oh, wait a minute, we could actually work together.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  9. This has been something that has been a bit of a surprise to me because I would say I have seen more initial adoption of advanced technologies in projects with little trust. Somebody says, ooh, this is a really good tool. I can defend myself if necessary. I can be on top of the food chain because I have all the information that the others don't have, et cetera.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  10. Definitely different contracting types that help with that, but the traditional design build atmosphere doesn't lend itself to that trust. But when you get towards integrative project delivery or design build type contracts, there's a lot more trust that has to be established with the design team and there's a lot more opportunity for subcontractors to be involved in the process earlier, which allows them to provide those details that are constructable, that they'd actually use in the field.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  11. That's true. It's like starting in a whole new environment So, this trust situation is really interesting. How variable is that? Are there different sites where there's a higher degree of trust or is there a general point of low trust across the board?

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  12. I mean, there's a whole concept of onboarding to a job site. It's hard for workers just to come out and start working that day. That's true. It's like starting in a whole new environment that came out and they're off to the races, but that's not really the case. They really have to dig into the information, find out what they need to look for, make sure there's not other details that have been created somewhere else. Make sure that the details they usually use are actually incorporated into the set of documents. And there's this issue of trust on a construction job site because like an engineer doesn't always trust that the subcontractors know what they're doing. And so they put in all these details that they think are the best details that work, but they've never installed anything in the field. Meanwhile, the field worker has to come through and look at those details and say, I can't actually build it this way. I have to do it this way, which means we have to put in requests for information and RFI and construction terms. And then that has to have more communication back and forth with the architect or the engineer, which adds more and more complexity onto this already complex work environment.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  13. What is the human result of that? Are there people sitting around waiting for deliveries? Are there people not coming up to their jobs and they're not ready for them? Like, how does that actually look on a human scale?

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  14. It's really, frankly, crazy if you think about it. You have a group of architects and engineers that create drawings or even 3D model information just in case, just so they can sort of show we did a lot. And then the reality, they have to go through there and filter out the information that is relevant to them. And then any uncertainty in the information that exists from the design phase gets multiplied in construction. It doesn't get simpler, right? Because then you have to figure out how to allocate resources, what sequence you were going to work, the site logistics. Imagine that now for 20, 30 trades coming together on any given day. And that's supposed to work like clockwork, but there's uncertainties for vagaries and everybody's variability and everybody's scheduled there. And then you compound that with uncertain design information. And that's why we end up with this kind of unproductive chaos that we often see.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  15. Right now we're basically giving an entire set of plans over to a construction worker in the field, and that could be thousands of pages of information that maybe only a handful, you know, 100 pages are useful for that one specific person.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  16. Sometimes, yes. It depends on what kind of information is in there. What we try and do is only give the information that's needed to do that specific task. The goal is to give location awareness, you know, role awareness, that kind of information to a specific worker on the job site.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  17. The 3D models, building information models, that kind of information, how do we make that information accessible into the field all the way down to RFIs, you know, written information to plans and specs from the architect and engineers. All that information is either dumbed down usually or put in a format that is not quite as rich or usable or has the dynamic state that say a data set would have within preconstruction.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source

  18. One of the biggest challenges we face right off the bat is trying to take the rich data sets that are already inefficient from preconstruction and migrate that into something that somebody on a construction job site can use or read or fabricate from.

    2018-06-14 · a16z Podcast · a16z Podcast: Construction Under Tech -- The Build · IDENTIFIED FROM THE TRANSCRIPT · source