Anthony Hartke 29 min

Translating Workflows from Mega Jobs to Smaller Ones


There is no one-size-fits-all solution for every construction project... In this episode of Built Different, co-hosts Grant Hagen and Brian Vizarreta sit down with Anthony Hartke, VDC Manager at Turner Construction, to discuss how tech solutions from big projects can be translated to smaller ones, and why every project should use some form of reality capture.



0:00

A lot of folks, they come to the conferences like this.

0:02

They see a cool new toy, the shiny object on the shelf.

0:05

They want to have it.

0:06

They got to have it.

0:07

Or, or your senior manager comes in and says, Hey, our competitor is using this

0:11

We got to use this to stay competitive.

0:13

It's like, no, you just need a shiny toy to market, which is its own value.

0:18

But it's operation.

0:19

Everything should be focused on the field.

0:21

How do we become better builders?

0:22

Whatever we use needs to make us better builders and be better for our clients.

0:27

Welcome to build different podcast featuring teams, technology and trendsetters

0:36

We're changing the way that we build.

0:38

I'm Grant Hagen and I'm Brian Visoreda and we welcome you to join a community

0:43

obsessed with questioning the status quo, creating cultures of innovation and

0:47

equipping everyone

0:48

with powerful tools to quite simply build different.

0:51

Well, welcome back to the build different podcast.

0:53

Join with Brian Visoreda.

0:54

I am your host, Grant Hagen.

0:56

Thank you all again for joining in with us for episode six.

0:59

If you are wondering why we are wearing some fun Hawaiian gear, if you're

1:02

tuning in and watching us,

1:03

we have some really fun stuff that we're going to be talking about in this

1:06

episode that relates to that.

1:08

So just really fun to be able to talk about that.

1:10

Anthony with Turner is going to be joining on with us for this episode.

1:13

Brian, what excites you about this conversation that we got to have with the

1:16

Anthony?

1:16

We really just got into it, you know, on how large projects adopt technology

1:22

differently than smaller projects

1:24

and, you know, what you can learn from both and what translates and just kind

1:27

of prescribing.

1:28

You know, there's never like a one size fits all solution for every single

1:31

project.

1:32

So it was just great to hear his lesson blared along the way.

1:34

Yeah, for sure.

1:35

And we hear that all the time from folks is like, how do I translate this stuff

1:38

from other companies

1:39

and from big jobs, small jobs?

1:40

And so that is the exact topic for this episode.

1:43

And so we just want to thank you again for tuning in with us.

1:45

A great conversation ahead.

1:47

Thank you all again so much for the feedback that you've given us so far.

1:49

We hope you enjoy the episode and we will see you next time.

1:53

We are joined with Anthony from Turner.

1:55

This is going to be a great conversation and also a good power over there,

1:59

Brian V.

1:59

We are going to have a lot of fun talking about some great stuff that Anthony's

2:03

doing with Turner construction.

2:04

We'll have you kind of intro give a little bit about your background, what you

2:07

do at Turner.

2:07

And then we're going to give them some good stuff.

2:09

We're really going to focus on how large scale projects can ultimately really

2:14

help and provide a ton of value

2:16

to maybe some smaller projects.

2:17

We've been talking with a lot of different customers here about just the

2:21

differences and job types

2:22

and job sizes and job personnel.

2:25

But what's the common thread that can connect them?

2:28

And we're going to talk about a little lessons learned and some things along

2:30

the way kind of on that camp.

2:31

But this is going to be a really good episode.

2:32

I'm really excited to talk through some of this stuff.

2:34

Turner's been a great customer for Drone and Point for many years.

2:37

Big customer on the instruction side side.

2:39

We'll talk a little bit about that at the end.

2:41

But without further ado, Anthony would love to hear a little bit about your

2:44

background,

2:45

how you kind of got into construction, what you're doing over at the Turner

2:48

land these days.

2:49

And yeah, sort of a deal.

2:50

Well, I will say I've got a pretty non traditional background and yet

2:55

traditional in some senses.

2:56

As a young high school kid, my passion actually was to go into musical theater

3:00

as a major.

3:01

Somewhere along the line, I got introduced to a construction management as a

3:05

degree in architecture.

3:06

I ended up going to the University of Cincinnati, Go Bearcats.

3:09

Come on.

3:09

When I got there, I was chasing the architectural engineering degree for a note

3:13

Found out that for an extra year of school, you can go for a dual major with

3:17

the construction management as well.

3:18

Oh, nice.

3:19

So co-ops and everything is part of that, which is fantastic.

3:22

Really encouraged co-op programs, paid internships while in college.

3:26

I joined the Army National Guard.

3:28

So spent 12 years in the guard background there was was IT signal systems,

3:33

military police.

3:34

So went through all that, kind of got deployed about three years into college,

3:38

spent two years over over in Germany.

3:40

NATO headquarters, seen back from my final three years, which is a good break

3:44

because I discovered some,

3:46

some good times in college this first three years.

3:48

Yeah. Yeah.

3:49

So kind of got my got my head back on my shoulders and kind of put myself back

3:52

on the on the right path.

3:53

This is my last three years.

3:54

Put the resume out there, got picked up by Turner and then as far as how it all

3:58

came together in college,

4:00

I had a degree certificate in geographic information systems, GIS.

4:04

So get to Turner.

4:05

They find out that, hey, this is a young field engineer for the college.

4:08

He knows how to use Revit.

4:10

Yeah.

4:10

Let's make him be this, this new BIM thing.

4:12

What's this?

4:13

Let's have him be the coordinator.

4:14

And this would have been what year?

4:15

2010.

4:16

So, so I became the BIM coordinator on the first BIM project within Humbus,

4:21

Ohio, which is where you're at.

4:22

Correct.

4:22

Correct. Correct. So we're still there.

4:23

Great, great place.

4:24

Lumb Ohio kind of took off from there.

4:26

Sorry to do in, through in BIM coordination.

4:28

They brought me out of the field and we back into the office, said, Hey, let's

4:32

put you in precon,

4:33

put you in estimating.

4:34

Let's figure how we can use models to help the estimating pre construction

4:37

process.

4:37

So did some sales support, did some quantity takeoff all super early before we

4:42

had all the,

4:42

all the bells and whistles and tools we have today, a lot of manual brute force

4:45

efforts.

4:46

And then kind of just slowly worked my way into the, the VDC manager role for

4:50

our higher

4:50

region and has been been sitting there ever since until about 2017.

4:54

That's when a big day center client came calling.

4:57

They wanted to push the envelope, wanted to go kind of full scale all out VDC

5:01

and BIM.

5:02

So they decided, Hey, who do we got in our office that can, that can really

5:06

take this on and run with it.

5:07

And they pulled me in.

5:08

We built the team, reality capture coordination, work in place tracking, kind

5:13

of building

5:13

what we've learned over the years and really built a really good team out there

5:17

Yeah.

5:17

Doing some really innovative stuff.

5:18

And you are selling your guys's team short, really good is very modest.

5:22

And it's an incredible team.

5:23

You guys, I've had a privilege to come out to the Columbus office and interact

5:27

with more of your guys's team.

5:29

Let's not forget to mention, I mean, to talk about fun, Brian's over here in

5:33

his Hawaiian shirt,

5:34

which, I mean, really, I'm so jealous.

5:36

That's why I keep bringing it up.

5:38

I got to go find one and steal one from it.

5:39

But I mean, you guys, your job office is called the beach house.

5:43

I mean, come on.

5:44

Like, how awesome is that?

5:46

Yeah, the culture on that project is really, it's second to none.

5:51

They've taken on of this one team approach, one team effort between the design

5:55

team, the client.

5:55

We have a co-located office space.

5:58

We decided we're going to be there for five, 10 years with all the work coming

6:01

through,

6:01

multiple builds, multiple data centers, about to break ground on another big

6:05

one.

6:05

So they decided why have a trailer complex.

6:07

Yeah.

6:08

We're going to be here for a while.

6:09

So they went ahead and designed a pre-instrumental building.

6:11

The client's got their section of the guitar section,

6:13

trade partners are in there as well, all working in the same space,

6:16

very collaborative.

6:17

It really is.

6:18

It feels like walking into a job side office of the future.

6:20

I mean, when you talk about how it's being collaborative and it's its own

6:24

separate space,

6:25

I mean, you can just, I don't know, when you walk into some buildings and some

6:28

offices,

6:29

you can just tell, like, man, this is a different vibe and a different feel,

6:33

which, man, we can do a whole other episode on that.

6:36

We were talking in a later episode about the value of a job side culture

6:41

and just how much that plays into it and how do you put a ROI on that.

6:44

And that's a great topic in its own self.

6:47

But what I'm curious, Anthony, to kind of get involved in and kind of hear your

6:50

perspective is,

6:51

and we hear this a lot, especially at construction conferences,

6:54

even just in general about the idea of larger jobs, big jobs.

6:59

Let's call them mega jobs just for clarity sake.

7:01

And when I could say mega jobs, I'm going to put them in the category of 750

7:05

million plus,

7:06

billion dollar plus projects, multi-year, more than three, four, five year type

7:11

jobs.

7:12

Oftentimes, those are data centers, stadiums, big, big jobs that have a long

7:18

tenure,

7:19

that how do those jobs help the smaller jobs at Turner?

7:24

I mean, and again, let me clarify, smaller jobs, let's just say anywhere in

7:29

that realm of under 100

7:31

million, under 75 million, those aren't in small jobs by any means, but they

7:35

definitely have a

7:35

smaller feel to them in comparison.

7:38

I really want to dive into lessons learned that you guys have had on the mega

7:44

jobs,

7:44

how that's translated and applied down to smaller jobs, and what ways you've

7:50

kind of

7:51

found some really key lessons learned in that process.

7:54

Because that's a big gap between those two types of projects.

7:58

And oftentimes, it's a gap between companies as well.

8:00

Like we're at conferences and we hear all these presentations, we're like, man,

8:04

that's not my company, it's not my job, it's not my type of project that I'm

8:08

working on.

8:09

And there's kind of an immediacy of, I'm just, I think that can't translate,

8:13

but that's not true.

8:14

I mean, you guys have turned, have proved how that can be, where you can share

8:18

that value.

8:19

That's the premise.

8:20

That's what I'm really curious to know, Brian, anything you want to add to that

8:23

No, I think you're kind of hit it on the head where, how are you using these

8:26

larger jobs to

8:27

learn on what you're going to do for across the company, like standardization?

8:33

Like, what are you looking at the entire company?

8:36

So our office is dealing with everything from your very small, small jobs,

8:42

which could run by half a person, a quarter a person, kind of run the project,

8:45

all the way up to a project in the multiple billions, where you can just

8:49

be a staff of 75 to 100 people on that project to give it a take.

8:54

So really what this allows us to do is it's created a, a pseudo R&D sandbox to

9:00

try.

9:00

I think we've got a client who, who wants to push the boundaries, wants to push

9:04

things forward.

9:05

They're very open to the idea of technology and using technology to change the

9:09

industry.

9:09

They want to be seen as a, as a leader of construction, a leader technology and

9:14

construction.

9:14

So they, they've worked with us when we find something that we think has value.

9:18

We'll, we'll pitch it up there and say, Hey, we think we got to spend a little

9:20

bit of money up

9:20

front. Can I get that little seed fund in there, a sweeten that pot to help

9:24

offset that cost,

9:25

to get that, that big thing, that high dollar value thing in there.

9:29

So we can start testing it, start trying it. We've got a use case. We've got an

9:32

ROI identified.

9:33

We got to prove it out. And the key there really is selling that initial ROI. A

9:39

lot of folks,

9:40

they come to the conferences like this, they see a cool new toy, the shiny

9:44

object on the shelf,

9:45

they want to have it. They got a heaven or, or your, your senior manager comes

9:48

in and says, Hey,

9:49

our competitor is using this. We got to use this to stay competitive. It's like

9:52

, no,

9:53

you just need a shiny toy to, to market, which is its own value, but it's

9:58

operation.

9:58

Everything should be focused on the field. How do we, how do we become better

10:02

builders?

10:02

Whatever we use needs to make us better builders and be better for our clients.

10:07

And that's really where this specific project has allowed us to kind of shine.

10:11

Did you anticipate the kind of sandbox approach that this project was going to

10:17

help in or did you

10:18

kind of fall into it or does it, does that make sense? I kind of fell into it.

10:22

Yeah. Like I said,

10:22

they were looking for somebody who can, who can help fulfill this client's

10:25

request. They're robust

10:26

requirements. I don't think anybody in the office in the region really

10:30

understood what it was going

10:31

to take. I don't think the client understood what they were asking for. I got

10:34

out there in

10:35

it was October of 2017, I remember the month and they said, Hey, the client

10:40

wants us to, to

10:41

coordinate the underground utilities for this site. And I said, okay, what,

10:44

what are we looking

10:45

at? What's our timeframe? Well, we're, we're starting to dig dirt in it. You

10:49

want me to

10:49

install all the utilities for the entire site? Yeah. And you're starting to

10:51

install your first

10:52

piece of utility today. We're three month, we're three months behind already,

10:56

three months behind.

10:57

So it was, it was a slog, got to get out of the ground, got to get moving, got

11:00

to just keep

11:01

picking away at it. So it was just me on this project. And then the client said

11:05

, Hey, we want to do

11:06

reality capture. And I said, what do you mean you want to do reality capture?

11:09

What does that mean?

11:10

It's like, we don't really know, but we're willing to pay for a scanner for the

11:14

project. And we want

11:15

you to do reality capture and do virtual reality while you're in. And that's

11:18

what they thought

11:19

reality capture was at the time. Grab a scanner. Yeah. Okay.

11:23

Yeah. We talked a little bit about that with some other folks is like,

11:25

how do you describe what reality capture is? And yeah, you go.

11:30

And as we have learned, it is much more than just head go by a scanner. Yeah.

11:33

And involves multiple tools, multiple levels of scanners, multiple levels of

11:37

accuracy and precision

11:38

and software and, and a whole slew of things that it can be above and beyond

11:43

just get a scan.

11:44

Yeah, but you bring up a really good point, right? Like the best place to start

11:49

is with a problem

11:50

that you are trying to solve. And then you can prescribe what levels of

11:54

accuracy are going to

11:55

be necessary for that, right? Like, if you just want to communicate what an

11:59

above ceiling condition

12:00

looks like a photo could work. If you want to coordinate new mechanicals, you

12:05

're going to have

12:06

to scan, right? Yeah, it's, it's, it comes down to what level of information do

12:11

you need?

12:12

So in our case, we didn't really have a use case to, we didn't have a problem

12:16

to solve.

12:17

We had a, we had a technology and said, hey, go find a use for this.

12:21

And so we started looking at it and initially the client said, hey, we, we want

12:25

a digital

12:26

representation of our building, but we also want you to validate the accuracy

12:29

of the installation.

12:30

We want to make sure that, that all this money we're paying for coordination is

12:34

being

12:34

utilized to make use of, which is a change. It's a change to the industry. It's

12:40

a change by

12:40

trade contractors to understand what we're doing and to get them to buy into

12:45

the process. So we

12:47

kind of started working through some use cases and we're still to this day, we

12:50

're learning where

12:51

we now have, I think, three scanners on site in addition to the spot with a

12:55

scanner. But we've got,

12:57

we've got two total stations, we got GPS units. So we got a whole team of

12:59

people now, five,

13:01

five reality capture professionals working on our team up here.

13:04

I love how when I visited your guys's job, you had these like kind of almost

13:08

badges,

13:09

right above the different teams. And I love that the badge for your guys's team

13:13

was VDC

13:14

slash reality capture. Like, I think that just kind of speaks a lot to the

13:18

value that it is

13:19

with these other ideas of virtual designing construction. A question I asked

13:23

earlier to

13:24

some folks was, how do you, so client comes you, hey, we want to do reality

13:28

capture. We don't know

13:29

what it is. We don't know where it can be helpful. How do you educate them on

13:33

the different types of

13:34

reality? Like Brian mentioned it too, like, hey, based on accuracies and needs,

13:38

but like,

13:38

there's a whole gamut of what reality capture is from a 360 photo to a scanner

13:43

and everything

13:43

in between ground air, all that. How do you kind of go about that education

13:48

piece, not only internally

13:50

for folks to see that value, but then also externally to clients that are maybe

13:54

interested in it.

13:55

So so one thing we learn throughout the process is scanners, not always the

13:59

solution is not the

14:00

end all be all and what you're trying to validate. It all comes down to

14:05

validation. What are you

14:06

trying to value? What kind of what's the end goal of what you're trying to? If

14:09

you're trying to

14:10

capture massive amount of information or an entire space, multiple systems,

14:15

scanner, it's

14:15

fantastic. If you're trying to capture where is this this sewage line going in

14:20

the ground out

14:21

in the site in the middle of the 330 acre site, do you really need to scan it?

14:25

Or do you really

14:25

need to capture points at locations? Because that that concrete pipe is not

14:30

going to move or bend

14:31

halfway through the run or from the air. That's like, hey, I want to do this

14:34

across the entire

14:35

side. Exactly. So it's kind of it's a point to point kind of thing. You just

14:39

got to capture the

14:40

key points, the key changes directions, whether that's from the air from a

14:43

total station GPS,

14:44

whatever, and it's faster to do that. But you got to make sure the process is

14:48

in place to be

14:48

able to support that. And so it's trying to find the right tool. It's really

14:52

about what's your

14:52

problem, what's your outcome you're trying to achieve? And then it's okay, let

14:57

's take a step back.

14:58

What tool is most cost effective? What tool is the quickest to capture the

15:03

information

15:04

and to what level of accuracy you need? If your duck bank or your storm pipe is

15:09

going to be,

15:09

if your trade partners can't install it within 12 inches or six inches or two

15:14

inches to one inch,

15:16

why why rely on a tool that's going to give you one 16th inch of accuracy? You

15:22

don't need that

15:23

misnocision. And the best part about that is that's translatable billion dollar

15:29

job,

15:29

10 million dollar job. That should be the process on anything. I'm curious. Are

15:34

there

15:35

two or three things that stand out that have been the most translatable down to

15:41

smaller jobs?

15:42

You know, we've been talking about this a little bit, but like, what are kind

15:45

of the things that

15:45

rise up that you can think of? So proper photo documentation, things like in

15:50

wall photos.

15:51

We started off with the need for, hey, we're going to scan the in wall stuff.

15:54

It's like, well,

15:55

why do you scan the in wall stuff? Well, we've got to compare it to the model.

15:59

Well,

15:59

we're not modeling the one inch conduit in the wall, but it's just too much and

16:02

too small.

16:03

So we've got nothing to compare it against. So if we can't use the scan to

16:06

compare it against the

16:07

model, why are we spending the time to scan it? We've got to know where it's at

16:11

. Okay, well, if

16:13

we have a photo of that conduit and everything in the wall, and you have

16:18

reference points where you

16:19

can take the photo and align it to that wall in the field and say, okay,

16:23

between this point

16:24

and this point. Now I know where all the studs are at. I know a cavity that

16:30

that conduit's in.

16:31

Right. Yes, finder beep beep. There's my cavity. This is where I got it cut.

16:35

Yeah,

16:36

that's as much as you need. So everybody's got camera. You don't need a 360

16:40

camera.

16:40

You just need to have a 2D camera and everybody's got one in their pocket in

16:43

their phone now.

16:44

So by using location based photos and having a plan of capturing those photos

16:50

on a very rigid

16:52

and regimented basis, you can produce a map of photos of everything in the wall

16:58

. And now if you

16:59

got to go back and do rework, it's a great turnover deliverable for the client.

17:03

It takes minimal

17:03

effort because as contractors, we should be documenting our construction

17:07

progress document in the work.

17:09

Takes five seconds out in the field. Take that photo. If you take it in the

17:12

right place and take

17:13

it meticulously, you have a product that the client's going to value whether

17:18

they're buying it from

17:19

you or not. If you already have the system in place, you have that platform in

17:21

place,

17:22

you come out the hero the first time that fact, you're going to find something.

17:26

You're the hero

17:26

for your company when you find a leak and you're going to find that bite. Pre

17:30

ach that. That

17:30

is, couldn't be more true. So progress documentation, let's bucket that as like

17:34

, hey, easily transferable,

17:36

big job or small job. What other ones kind of come to mind? I would say that

17:39

drone

17:39

drone photography is fantastic because you can quickly capture information

17:43

about the site.

17:44

The frequency of it is the question mark about what you got to do. But on a lot

17:51

of projects,

17:52

even if you're doing a grading and paving of a parking lot, we used it for

17:58

documenting the

17:59

grading of a soccer field that we were doing kind of as a pro bono thing for a

18:03

client versus

18:04

having to go in and try to survey the topography, getting just enough

18:08

information.

18:09

Don't go way overboard. Don't go get your 16th inch of tolerance, but enough to

18:14

be to show

18:15

what that grade is going to be. And because you're doing that, you're already

18:19

capturing

18:19

weekly work in place. We fly once a week. So it's like, we're not reinventing

18:23

the wheel.

18:23

We're taking a process we've had before using a new technology that gives you

18:28

better,

18:29

more consistent, more accurate results. So drone photography to me in replacing

18:34

the construction progress photos, aerials. It's a slam dump on any project.

18:39

What are your thoughts? Your personal opinions, nothing representative

18:46

Turner's thoughts as a whole, on the drone deployment structure, say the

18:49

acquisition.

18:50

Where does that kind of go in your mental space? Where do you think there's

18:56

opportunity there?

18:57

It's funny. We were down here four weeks ago at another big industry conference

19:02

And I was chatting with some folks and we were talking about, I believed at

19:07

that time that

19:09

that the whole 360 photo documentation steer the whole

19:13

sphere. Like what you did there.

19:15

There you go. No pun intended. But pun well received.

19:18

It's right. It's at that inflection point where they're starting to get

19:24

industry adoption.

19:26

We're starting to see that plateau, that value proposition really being hit.

19:30

And

19:31

that's when the big companies come in and they start acquiring.

19:34

And I mentioned it to the instruction site reps that hey, you've got a really

19:38

good

19:39

terrestrial floor plan based platform that people just intuitively will use.

19:46

But we're doing

19:46

these other things. We're doing scans. We're doing a VR. We're doing aerials

19:50

stuff. It would

19:50

be great to be able to tie this stuff together. At the same time we were

19:53

talking drone deploy

19:54

and saying hey, you guys got a great aerial platform. But you're getting into

20:00

that

20:00

terrestrial photo realm and your interface just isn't that good for that kind

20:05

of stuff.

20:06

You're doing video walks but not static. I prefer the static over the video

20:09

walks,

20:10

higher quality imagery. I can get people to do the same thing very repetitively

20:14

. So

20:14

it'd be great if you just partnered up with somebody and then trying to

20:19

overhaul your entire

20:20

system. And lo and behold, I was not aware. But the conversation was happening

20:25

right in the back

20:25

end. It's as if you predicted this merge of these two companies.

20:32

Yeah. So it was it was kind of by surprise when the announcement was made. It

20:36

was not the

20:37

partnership I thought that was going to happen. But it's a really good

20:41

partnership,

20:41

especially around some of the more innovative developments that are happening.

20:45

Talk about that. Surprise in not the one that you thought was going to happen.

20:49

Curious to hear your thoughts on that. Honestly, I thought that RDS was going

20:53

to make the first

20:53

move. Wow. Okay. Cool. Just because they're moving into that space.

20:57

With recap and other reality capture platform. Exactly. They bought the wild,

21:03

brought VR integration into their BIMP 360 platform, the cloud based

21:08

documentation.

21:09

It just feels like there'd be it'd be a good space to have some kind of photo

21:13

documentation

21:14

much more to tie into it. Sure. No, that's great. I thought you were going to

21:17

answer that very

21:17

differently. So no, and yeah, I agree. I think that that is something which is

21:22

really interesting

21:22

to see for sure on the Procore and for sure on the Autodesk and of these two

21:27

platforms really

21:28

supporting reality capture in a way of like, hey, we obviously can iframe into

21:34

Procore,

21:35

we can do different things with Autodesk build in that platform to our

21:38

construction cloud.

21:39

Yeah. It is interesting to see some of that. I'm really curious to hear from

21:44

you on

21:45

you guys that have the benefit of being a drone employee customer and being a

21:50

instruction site customer. What would you want to tell a

21:54

instruction site customer about drone deploy? And then I would flip it off.

21:58

What do you want to

21:58

tell a drone deploy customer about instruction site? Because you guys have the

22:03

very unique

22:05

situation that you're in that you're very heavily invested in both platforms.

22:09

But we know that

22:09

that may not be the norm with other customers that may be coming at it from

22:13

just a instruction

22:13

site end of like drones. Why do I need that or drone deploy and saying, and I

22:18

don't know why

22:18

that's important. Give me some of your perspective around those types of

22:23

customers and the questions

22:25

that they should be encouraged by with you having usable platforms. Sure. I

22:31

would say that from the

22:32

drone deploy customer looking at instruction site and saying what is that for?

22:38

It is the

22:40

excitement of the current platform is the static 360 stationary 360 stationary

22:48

2D

22:49

in comparison to the model. I think those features is what really provides the

22:54

backbone

22:54

of instruction site as a as a platform. Yeah, that's great. And then

22:58

instruction site,

22:59

you should get excited about using drone deploy because you're already in the

23:04

world of 360 and

23:05

2D photos. And this allows you to get that high in the sky of the entire site.

23:09

To me,

23:09

it's a lot easier to tell to sell instruction site users on drone deploy

23:14

because she's taking

23:15

what they already know about the interior space and taking it out to the site

23:18

out of the air.

23:19

With a big interesting and we could not miss on this point, but I don't want to

23:26

use drones.

23:27

I don't want to own a drone. I don't want to start a drone program. Why should

23:31

I be excited

23:32

about driving a boy? So we to turn does not fly our own drones. It's a company

23:36

policy.

23:37

It comes down to a risk issue. The drone falls out of the sky for for no no

23:42

reason of our own.

23:43

It happens. Batteries can die. Falcons love punching drones out of the sky. It

23:48

happens.

23:48

I've seen it happen. Throw the clip of the Falcon video. Exactly. If you're

23:52

flying over top

23:52

and active work, which we shouldn't be, but if if a drone falls and hits

23:56

something, our insurance,

23:57

we are not aircraft operators. Our construction insurance policies don't cover

24:03

air strikes.

24:04

They don't cover aircraft crashing. If you hit a person, that's a bad day for

24:10

everybody,

24:10

including that person because I don't care. They're not coming after the

24:13

individual.

24:14

They're coming after the company. Insulating us. We've got big pockets, which

24:18

means we're a big

24:19

payout of that. So are you telling me that Turner doesn't fly a single drone

24:23

but uses drone deploy?

24:24

Correct. The way we do we get about that is we do have a drone policy and an

24:30

agreement with

24:30

drone deploy where we can request a flight and drone deploy will actually work

24:35

through their

24:35

network of drone pilots to provide that flight for us. This is what I want

24:41

people to hear.

24:41

I obviously know and have seen this, but this is where I think there's going to

24:48

be a big caveat

24:49

for folks of some instruction site users being, "I don't want to get into that

24:52

space." Or,

24:53

"I want to," but you're telling me I got to go get certified. You're telling me

24:58

I got to go get

24:58

equipment? You're telling me I got to go warn this other world that I'm so busy

25:03

on the inside?

25:04

Tell me about the excitement that you see for instruction site users and being

25:09

to tap into the

25:10

data on demand that Turner massively uses. Yeah, and again, this goes from big

25:15

projects to

25:16

small projects. On the big project, we've got a third-party pilot that we

25:19

contract with directly.

25:20

There are guys that fly week and week out. We hold their contract directly.

25:24

On a smaller project, you don't got the budget to do that, but we've got a set

25:28

fee structure of

25:29

60-minute flight costs X, say, 120-minute flight costs X. Within drone deploy.

25:34

So the whole ordering

25:35

system, ordering the flight, mapping out what the flight coverage area needs to

25:40

be, that's all done

25:40

by our users in the system. We hit the requests to get that drone demand

25:44

feature, and drone deploy

25:46

will get the pilot out there. They will get that flight going. The pilot takes

25:49

care of all that

25:50

information. We don't got to worry about it as a contractor. Our engineer, our

25:53

superintendent,

25:54

doesn't need to be a pilot. It doesn't need to have a license. The theme of

25:58

this episode is

26:00

big job, the small job. That translates, and you can do that same type of

26:05

experience that you

26:05

were used to on a big job down to a small job. We could throw up some

26:09

statistics and talk through

26:11

the amount of flights that Turner does on data on demand through drone deploy.

26:16

It's incredible.

26:17

I mean, you've obviously got to experience that. Tell me a little bit about

26:22

your thoughts.

26:22

So the growth, the ability to remove that roadblock of Turner, you can't fly a

26:29

drone. And we can say,

26:31

all right, you can't fly a drone, but here's the resource to go and get that

26:34

drone flight,

26:35

and having that standard pricing rate so we can plan in budget. There's nothing

26:40

worse than

26:41

seeing, I want to use a tool, but there's no money in the budget for it. So we

26:45

can have that

26:45

conversation in front of the budget for it. You've got so many flights to do,

26:48

and we'll push it out

26:49

there. In fact, I don't need to be the one to do all the work. It's just, hey,

26:55

here's the tool,

26:56

here's the platform. You want to flight? Here's what it comes to.

26:59

And it's almost, well, it's not almost, there's some data that could show it's

27:03

almost safer.

27:03

I mean, whereas almost more efficient, I mean, you could line up and name

27:08

anything along those

27:10

lines of why data on demand could be a really exciting thing for instruction

27:15

site users

27:16

to get excited about within a drone deploy. I just think the education piece

27:19

around it may not be

27:20

there. And I think that's why we're wanting to continue to promote talk, put

27:24

your voice out there

27:25

more than ours, which I mean, what you guys are the end user of the value that

27:29

it brings.

27:29

If a company is open to flying their own drones, they've got that option too.

27:34

So you kind of got

27:34

two three options. You can fly your own. You can bring your own contract to fly

27:39

for you,

27:39

or you can go through that drone deploy network. Yeah.

27:42

Get three options. Yeah. And at the end of the day, the unified reality capture

27:46

idea is still alive.

27:48

Big job, small job, doesn't matter. Man, really great stuff. We are in between

27:53

you and some drinks,

27:54

and you and having some fun here on the Expo Hall 4, but Anthony, super fun.

27:59

This is just, I think,

28:00

one of those opportunities to talk through relating big job to small job,

28:05

getting people excited about

28:06

the lessons learned that can be applied, Brian, anything you'd want to add as

28:10

we before we close up.

28:11

No, I'm just grateful that we can share this knowledge because very frequently

28:18

we hear from

28:19

people at smaller companies saying, I can't do this because I don't have those

28:22

type of budgets,

28:23

and they don't get to kind of get those first-hand lessons learned directly in

28:28

a scenario like this.

28:30

So thank you very much for doing that. No worries. We're happy to share what

28:34

the rising tide raises

28:35

all ships. So whatever we can do to push the industry forward, we're always

28:38

happy to step out

28:40

there, have those conversations. Anthony, this is super fun. Always enjoy

28:43

getting to spend time

28:44

with you guys, the Turner team talking through some of these things. And two,

28:48

to the listeners,

28:48

I hope this has become a helpful resource for you. I appreciate how open you

28:52

guys are about just

28:53

some of these challenges, the topic, just in general. Because I think, again,

28:57

you said it well,

28:57

rising tide brings all the ships up, and we really do want to help promote that

29:01

. Anthony,

29:02

great talking with you. Built different. We will see you on our next episode.

29:07

Make sure to subscribe to build different on Apple Podcasts, Spotify, and

29:11

anywhere you

29:11

listen to podcasts. Let's build this community together.