Artwork for podcast The Business of LoRaWAN
The Economics of IIoT - Britt Antley - Wika
Episode 5329th April 2026 • The Business of LoRaWAN • MeteoScientific
00:00:00 00:19:42

Share Episode

Shownotes

Britt Antley, Industrial IoT specialist at WIKA and former Chevron operator, talks about what actually drives adoption of IIoT in the real world—and why the shift from control systems to monitoring is one of the most important changes happening in industrial environments today.

With nearly two decades at Chevron, Britt brings a grounded perspective on how large-scale operations think about technology. He explains how his work evolved from traditional IT and process control into industrial IoT, and why LoRaWAN-style deployments fundamentally change the equation. Instead of months-long installs and expensive hardwired sensors, companies can now deploy low-cost devices in minutes, dramatically lowering the barrier to entry for instrumentation.

The conversation explores how IIoT creates value beyond simple cost savings, especially in brownfield environments where the goal is to “put eyes” on systems that were previously manual. From monitoring tank levels to reducing unnecessary operator rounds, Britt breaks down how better visibility leads to improved efficiency, safety, and decision-making.

Britt also shares how he approaches new customer environments—starting with understanding operations, identifying manual processes, and uncovering high-impact opportunities for instrumentation. The discussion highlights a key insight: many systems don’t need high-frequency control, just reliable, periodic data.

The episode closes with a deep dive into WIKA’s Sentinel sensor, including how combining vibration and ultrasound enables earlier detection of equipment failures and extends predictive maintenance timelines from weeks to months.

Britt on LinkedIn

WIKA

Transcripts

Speaker:

Today's guest on

2

:

MeteoScientific's

The Business of LoRaWAN is Britt Antley,

3

:

an industrial IoT practitioner

who spent nearly two decades at Chevron

4

:

and now helps companies deploy real world

IoT solutions at Wika.

5

:

His perspective matters

because it comes from field

6

:

working inside large scale operations,

then translating that experience

7

:

in a practical deployments for companies

that are just getting started.

8

:

In this episode,

we walk through his path from traditional

9

:

IT and process control into industrial IoT

and what actually changes

10

:

when you move from controlling systems

to simply observing them.

11

:

We get into the economics

and speed of LoRaWAN style deployments,

12

:

where a $10,000 hard wired sensor becomes

a $500 device you can install in minutes,

13

:

and how that shift enables entirely

new use cases.

14

:

We also dig into how companies

uncover opportunities for IoT,

15

:

especially in brownfield environments,

and what it really means

16

:

to put eyes on systems

that were previously manual.

17

:

We finish up by covering workers

sentinel sensor, including how adding

18

:

ultrasound extends predictive maintenance

from weeks out to potentially months out.

19

:

This episode is sponsored

by the Helium Foundation

20

:

and is dedicated

to spreading knowledge about LoRaWAN.

21

:

If you'd like to try helium

publicly available global LoRaWAN for free

22

:

and support this show, sign up at Meat

Sideshow Slash console.

23

:

Now let's dig into the

conversation with Brittany.

24

:

Brett,

thanks so much for coming on the show.

25

:

Super psyched to have here. Awesome.

26

:

Nick, thanks for having me.

27

:

Excited to talk to you about LoRaWAN.

Yeah.

28

:

I'm psyched.

29

:

So you were at Chevron for geez,

almost 20 years, 17, 17.

30

:

Okay, three short of two decades.

31

:

Would you walk me through

kind of how long you've been in IoT?

32

:

Was that IIoT industrial IoT?

33

:

Was that there the entire time,

or was that something fairly recent?

34

:

Kind of. Why did you get into it?

35

:

So Chevron I kind of bounced around

within the general IoT space.

36

:

My first experience kind of on the

37

:

OT operational technology side,

I was in IT audit.

38

:

So while I was in audit

I worked on auditing PCN systems.

39

:

From there,

I moved into a role as a PCN administrator

40

:

at a chemical plant

outside of New Orleans.

41

:

I was there for four years,

got more familiar with kind of the OT

42

:

side of things, and then I guess in 21

43

:

I moved over to the industrial IoT space.

44

:

Chevron big company.

45

:

Obviously they have a pretty big team

dedicated to working on your IoT.

46

:

So while I was there,

I got to kind of touch every aspect

47

:

of industrial IoT

within a large multinational.

48

:

Obviously, your oil and gas company.

49

:

Yeah.

50

:

Was there anything that

when you got over there

51

:

that was a surprise to you

or that you felt like,

52

:

oh, this is something super cool

that like, I wish more people knew about?

53

:

I would say one of the

one of the big kind of eye

54

:

opening things for me was there's

kind of this difference between

55

:

your traditional operation technology,

your process control systems.

56

:

You got your hard wired,

everything is very tightly controlled.

57

:

Then moving into the IoT space,

first of all, at Chevron

58

:

and kind of in general on the industry,

you don't see much control in IoT.

59

:

It's more just monitoring.

60

:

So for me,

it was kind of a mindset change moving

61

:

from the process control side over to IoT.

62

:

Well, at the same time, IoT

allows you to be so flexible,

63

:

so agile compared

to your traditional process control.

64

:

You're able to much more quickly, easily

and cheaply

65

:

deploy these IoT solutions.

66

:

For me,

67

:

that was a huge eye opener compared

to the more traditional side of things.

68

:

Oh, interesting.

69

:

Just because they are pretty easy

to deploy and especially with LoRaWAN.

70

:

Although across all of the IoT

technologies,

71

:

you're just putting a thing in there,

kind of slapping it on and walking away

72

:

versus figuring out how to control stuff

and make sure you don't screw it up.

73

:

Absolutely.

74

:

Like deploying a traditional sensor

in a control system, obviously you're

75

:

you're running power out there,

you're running Ethernet out there.

76

:

You have to go through

this huge management of change process,

77

:

which takes months.

78

:

All this equipment is very expensive.

79

:

One sensor, it can be $10,000.

80

:

Now you go to like a lower win

IoT situation.

81

:

That sensor is going to cost 500 to $1000.

82

:

And assuming

you already have your network in place,

83

:

literally,

you walk up to a piece of equipment,

84

:

you slap that sensor on there and within

a couple of minutes you've got data.

85

:

So just the ease and quickness

and the cheapness with

86

:

which you can deploy

IoT is really a game changer in my mind.

87

:

Was there a sense in Chevron

88

:

that IoT kind of wasn't

something they should do?

89

:

It seems like one of the things

the biggest retardants to IoT

90

:

adoption is people are just like,

I don't know about that stuff.

91

:

I don't know if we really need it.

92

:

And it seems like it's super valuable,

but it's like making the case

93

:

that it's useful, as is probably

just as difficult as figuring out,

94

:

if not more, is figuring out the RF

and the rest of the,

95

:

you know, frequency hopping stuff.

96

:

Yeah, while I would say there was,

you definitely ran to some resistance

97

:

in deploying IoT solutions

at the end of the day,

98

:

Chevron and I would say oil and gas

in general, they're pretty early adopters

99

:

into the IoT LoRaWAN space,

especially within the US market.

100

:

I know you do.

101

:

You know the European markets a little bit

ahead of us, but in the US market.

102

:

Oil and gas

was pretty early on the adoption phase.

103

:

So the fact that Chevron had built out

this huge

104

:

team,

you put this huge investment into it.

105

:

With that,

they were able to kind of create their own

106

:

ecosystem in very quickly.

107

:

You start to realize value out of IoT.

108

:

And that's something that they were quick

on a lot of other companies are very kind

109

:

of just starting to dip their toes

in, starting to figure out what is IoT.

110

:

Honestly, that's

what I'm doing it like to figure out

111

:

these smaller to medium sized companies

who may not necessarily know IoT.

112

:

Irwin.

113

:

What these technologies are,

I'm trying to I'm here

114

:

to help them figure out

how they can create value out of that.

115

:

Okay.

116

:

That leads really nicely

into the next question, which is, is there

117

:

anything beyond just saving money

that you use when you're talking to small

118

:

and medium sized companies as a reason

for them to adopt industrial IoT?

119

:

Yeah, absolutely.

120

:

I think the biggest thing

adopting industrial IoT

121

:

is giving you eyes

where you currently don't have eyes.

122

:

So a lot of the adoptions we're seeing are

123

:

mostly

in the kind of the brownfield space,

124

:

these established facilities

or plants, whatever it might be.

125

:

So it's already there.

126

:

And it's saying

with your current infrastructure,

127

:

your current layout,

how can you get more value out of this?

128

:

How can you get more efficiencies?

129

:

How can you put eyes on something

that currently doesn't have eyes?

130

:

Currently,

an operator has to go walk around

131

:

to 60 tanks a day and visually

132

:

look at something

visually take a level on a team.

133

:

How can you make better use of their time?

134

:

Instead of walking those rounds every day,

135

:

they can look at a screen that's

going to give them the same information.

136

:

They can get alerts that are going

to give them the same information.

137

:

So it's kind of more of a proactive

approach.

138

:

Right.

139

:

And I bet that makes sense

140

:

to a lot of a lot of business owners

who are saying, hey, I'm paying for this

141

:

like expensive engineer.

142

:

I can use their time to help design stuff

and create new things, rather than have

143

:

to walk around and

144

:

look at a button.

145

:

Is there a bunch of conversion

of analog devices into smart sensors

146

:

with what you're doing?

Or is it more like,

147

:

hey, let's put something new on here,

walk me through that.

148

:

So what we're mostly seeing now is

let's put something new on here.

149

:

We have some type of equipment

that's currently not instrumented.

150

:

So how can we get some data out of that?

151

:

Essentially I do see slowly

and probably more so in the future.

152

:

Going forward,

there will be more replacing

153

:

those kind of hard wired with IoT devices.

154

:

So I know, in the process control

industry, a lot of the life cycles on

155

:

these systems are ten, 20,

maybe even 30 years.

156

:

As they start to age, they're looking

to upgrade them, replace them.

157

:

Well, you can replace a system

some five, $10,000 sensors.

158

:

You can go

the same route, do the same thing, or for

159

:

ten, maybe 20% of the cost,

160

:

you can make those IoT as long as you're

not controlling anything.

161

:

If you're just looking to monitor

it, have eyes on it.

162

:

IoT is a perfect solution

in that situation.

163

:

Interesting that there's such a point of

differentiation with this control piece.

164

:

I haven't heard

165

:

folks talk about that as much,

and that sounds like that's

166

:

just coming from the background.

167

:

Like, hey, I used to control everything,

and now I'm seeing that there's value

168

:

in a lot of just observing

what's going on.

169

:

Yeah, absolutely.

170

:

And a lot of current process

control systems.

171

:

Yeah. Everything is hard wired.

172

:

It's super industrial, super heavy duty.

173

:

I mean, you're getting millisecond

readings.

174

:

Yeah. And that's good for some situations.

175

:

But a lot of times

if you get a reading every 20,

176

:

30 minutes,

even every hour, that's perfect.

177

:

I mean, how often is a tank

changing level?

178

:

They're doing draws

maybe once or twice a day.

179

:

Well, you don't need readings

every second on that.

180

:

You put a $500 thousand dollars

sensor on there.

181

:

You take readings every 30 minute,

every hour.

182

:

You're getting the same quality of data

for a way cheaper.

183

:

Yep, that makes a ton of sense

184

:

when you're coming into a new organization

and a potential customer.

185

:

What are the ways that you think

about uncovering or discovering

186

:

opportunities for them to use IoT?

187

:

I think a big part of that

is just understanding their operation,

188

:

understanding their business,

understanding their value

189

:

chain, understanding their key processes.

190

:

And as you start to look at those,

you can see,

191

:

hey, you've got this process here

that's hugely automated

192

:

and you got a lot of people involved there

manually touching things,

193

:

manually looking at things.

194

:

Not only is at a time

where it can also be a big safety issue,

195

:

especially in the oil

196

:

and gas space, they're huge on safety,

so that's always a big concern.

197

:

But yeah, looking at those kind of

198

:

what are their important systems,

what is currently manual,

199

:

what could we easily go in and instrument

and get them data,

200

:

get them actionable insights

and let them really have

201

:

a great vision of this system

where essentially turning manual processes

202

:

into more automated processes

now makes sense.

203

:

So you go and understand the system

and then sit and kind of look

204

:

for these key points of like, hey,

we're obviously where can we save money?

205

:

Where can we make you more efficient,

where can we make you more safe?

206

:

And maybe there's like 2 or 3

207

:

more kind of columns that you,

that you hit or pillars that you hit.

208

:

But that sounds about right.

209

:

Yeah. Cool.

210

:

So walk me through this sentinel thing

that we CA or Waka has just brought in.

211

:

What is this thing?

212

:

Yeah.

213

:

So Sentinel,

it's lead by a company called a system.

214

:

A system is a company that Wyck

recently became the majority owner of.

215

:

So the Sentinel is a sensor.

216

:

The most traditional way to think about it

217

:

is it is a machinery health

monitoring sensor.

218

:

So within this one sensor

there is temperature.

219

:

It is also measuring the vibration

tri axial vibration.

220

:

And I think the real secret sauce within

221

:

it is

we also have ultrasound measurements.

222

:

So the vibrations pretty typical.

223

:

We see that a lot of different companies

have their version of vibration sensors.

224

:

But bringing that extra level

of ultrasound into the sentinel sensor,

225

:

what that allows us to do is get a whole

nother level of analysis.

226

:

So your traditional vibration sensor,

you can go to

227

:

five,

maybe ten kilohertz, a vibration detection

228

:

with the ultrasound, you're able

to take that up to 60 to 70kHz.

229

:

Now what this ultimately allows you to do

is to get a further look into the future.

230

:

So you put this sensor on

231

:

any type of rotating machinery,

whether that's a pump, a motor,

232

:

a compressor, you put it on there

and it's able to perform analysis.

233

:

A big part of this sentinel

is also a machine learning aspect

234

:

that we're able to do on our platform.

235

:

So yeah, you take in all this data,

you kind of determine what's baseline.

236

:

And then off of that you're able to say,

237

:

hey, I'm detecting some weird sound

and the machine learning

238

:

is able to actually say, hey,

I detected this type of sound.

239

:

This can mean

that you have a bearing going bad.

240

:

And once you have that level of analysis,

then you can have one of your engineers

241

:

go and say, hey,

something's going wrong with this motor.

242

:

Let me go out and check it.

243

:

Whereas your traditional

kind of processes,

244

:

maybe once every week, every month

245

:

at best, you have a mobile sensor

that you put on a piece of equipment.

246

:

You kind of listen,

I mean, even more traditional,

247

:

you have engineers out there

who will literally tap on something,

248

:

or they'll put their ears up to it

and listen.

249

:

And these are

professionals are very good at their job.

250

:

But when you can put a sensor on there

that's doing that 24 over seven

251

:

and is able to do it at, a deeper level,

I think that's a real game changer.

252

:

What's the performance difference

when you add

253

:

an ultrasound versus

just the vibration sensors?

254

:

There's a

255

:

maybe not a metric ton of those

in the market, but there's a lot of

256

:

a lot of kind of machinery

listening sensors on the market.

257

:

There's ultrasound

sounds like it's pretty fancy and special.

258

:

Like how much better is it?

259

:

I guess the question. Yeah.

260

:

So the best way I know to quantify that

from data I've seen is that, vibration.

261

:

And typically they can see issues

262

:

that are maybe a couple weeks

or a month out.

263

:

So we're starting to tuck this vibration.

264

:

Something's going on.

265

:

Maybe in a couple weeks

it could become a real issue.

266

:

So I had to do something about it

with the ultrasound capability.

267

:

From what I've seen,

were able to detect issues

268

:

that are like three,

maybe even four months out year.

269

:

Okay.

270

:

So it's less severe

that what the vibrations able to detect.

271

:

So you have this little thing

that's starting to go wrong.

272

:

Not an issue now but keep an eye on it.

273

:

Maybe go ahead and order that back up part

so you can have it ready.

274

:

Yeah. So that's that's kind of the beauty.

275

:

It allows you to see kind of

276

:

further into the future

to do your predictive maintenance.

277

:

Oh that's that's rad.

278

:

Super cool.

279

:

Let's see.

280

:

Let's wrap this up a little bit.

281

:

On a slightly more personal note,

you're way into beer.

282

:

We were talking a little bit

about building

283

:

breweries and sensing or sunsetting

whatever it is, instrumenting breweries

284

:

before we recorded.

285

:

Maybe we start with this idea

of kind of consumer versus industrial IoT,

286

:

and what the big differences are and walk

you through kind of what that looks like.

287

:

And is there a difference

or is it kind of IoT as IoT?

288

:

Yeah,

there's definitely a difference there.

289

:

I think it's

290

:

kind of important to understand

and there's also different levels to it.

291

:

One example recently I was at one of

my favorite breweries here in Denver.

292

:

I was talking to the owner.

293

:

He was mentioning

they had a temperature sensor

294

:

in their cold box that had been kind of

iffy, wasn't giving them great data.

295

:

I'm like, oh, interesting.

296

:

Well, my company I worked for, white Guy.

297

:

We actually have a solution

that could solve that, but

298

:

they're using kind of a

more consumer grade IoT.

299

:

It was probably like $50 sensor.

300

:

And for the most part, it worked

well for them.

301

:

And also at this cold box, if

the sensor went bad, the cold box was hot.

302

:

They had other ways,

303

:

kind of secondary ways to look at it

and see what the temperature was.

304

:

So your industrial grade IoT,

305

:

it's not going to be as cheap

as your consumer grade,

306

:

but it's going to be much more reliable,

much more durable.

307

:

It's designed to be in more extreme

environments.

308

:

When you say industrial IoT,

you're deploying at various sites,

309

:

chemical plants, manufacturing facilities,

a lot of times

310

:

there are hazardous gases,

so you don't want anything

311

:

that could potentially cause

a spark in an explosion.

312

:

And we don't want things to blow up.

313

:

So yeah.

314

:

Industrial non-optimal

yeah yeah yeah yeah.

315

:

And not looking for that in general. Okay.

316

:

And then

317

:

just as an example of what you might do

if you had to go in today and today is

318

:

I think we're recording on Wednesday,

by the end of the week,

319

:

you had to close a brewery

on a sensor somewhere.

320

:

And what are Denver, what would you target

as a as the kind of pitch?

321

:

Because that seems like an industry

you're pretty familiar with.

322

:

So you wouldn't

have to learn that much about it.

323

:

What would you kind of walk into

any given brewery and be like,

324

:

I know they're going to need this.

325

:

So, I mean, temperatures as you age one,

you got all types of mass of equipment

326

:

that's cheating product, cooling it down.

327

:

So being able to monitor that

and keep an eye on it is a huge space.

328

:

I will say that most of the modern

brewing equipment

329

:

usually has all this sensing

kind of already built in.

330

:

If you're buying

one of the new state of the art systems.

331

:

All of this is kind of built

in, which is cool to see, but let's say

332

:

tomorrow, cures here nearby in Golden,

they call me up.

333

:

Hey, we're having some issues

with our instrumentation here.

334

:

What can you offer?

335

:

I'm a go.

336

:

And number one,

what's your temperature look like?

337

:

Number two, what is pressure look like?

338

:

You're moving around a lot of liquid,

a lot of volume.

339

:

Sometimes it's pressurized.

340

:

So being able to monitor that,

keep an eye on it is another huge system.

341

:

Super cool.

342

:

And I can see with certainly

with the bigger breweries, with Coors,

343

:

or even a kind of midsize brewery

that they're going to be willing to pay

344

:

the industrial IoT prices versus like,

hey, I'll just order this thing

345

:

off the internet,

have it here tomorrow. Absolutely.

346

:

I mean, it

obviously depends on the type of system.

347

:

And industrial IoT isn't for everything.

348

:

But in these big manufacturing facilities,

which breweries are

349

:

I mean, they're just

they're manufacturing a delicious product

350

:

that we like to drink,

but that's all it is.

351

:

It's a manufacturing facility.

352

:

So, yeah, and something like that,

353

:

when you have the huge scale industrial

IoT makes sense.

354

:

Ripping.

355

:

Well, thanks so much for making time today

356

:

and coming on

and talking to us a little bit about IoT.

357

:

We want to hit on the lower end stuff,

but I think for this audience,

358

:

they've got a pretty good understanding

of how it works.

359

:

So it's super cool

360

:

to see really the perspective

that you bring to the industry.

361

:

Thanks. Thanks. Coming on.

362

:

Awesome.

363

:

Great talking to you, Nik,

and thanks for having me on.

364

:

That's it for

this episode of The Business of LoRaWAN.

365

:

If you want to go deeper

and actually deploy devices,

366

:

the MeteoScientific

Console is the fastest way to do that,

367

:

and honestly, it's

also the best way to support the show.

368

:

When you use the console, you're not just

listening, you're participating

369

:

in the same real world LoRaWAN work

we talk about here every week.

370

:

You can get started with the free trial

at Medio scientific.com.

371

:

Huge thanks to the sponsor of the show,

the Helium Foundation,

372

:

for supporting open LoRaWAN

infrastructure worldwide.

373

:

Check them out at helium Dot Foundation

and if the show has been

374

:

useful, a quick rating or review

on Apple Podcasts or wherever you listen.

375

:

This really helps

376

:

people find it and helps the show grow

so we can help more people.

377

:

I'm Nik Hawks with MeteoScientific.

378

:

I'll catch you on the next episode.

Links

Chapters

Video

More from YouTube