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.
Today's guest on
2
00:00:09,042 --> 00:00:12,245
MeteoScientific's
The Business of LoRaWAN is Britt Antley,
3
00:00:12,479 --> 00:00:16,116
an industrial IoT practitioner
who spent nearly two decades at Chevron
4
00:00:16,316 --> 00:00:20,320
and now helps companies deploy real world
IoT solutions at Wika.
5
00:00:20,920 --> 00:00:23,123
His perspective matters
because it comes from field
6
00:00:23,123 --> 00:00:26,459
working inside large scale operations,
then translating that experience
7
00:00:26,459 --> 00:00:29,462
in a practical deployments for companies
that are just getting started.
8
00:00:29,929 --> 00:00:32,332
In this episode,
we walk through his path from traditional
9
00:00:32,332 --> 00:00:36,603
IT and process control into industrial IoT
and what actually changes
10
00:00:36,603 --> 00:00:39,606
when you move from controlling systems
to simply observing them.
11
00:00:39,773 --> 00:00:42,542
We get into the economics
and speed of LoRaWAN style deployments,
12
00:00:42,542 --> 00:00:46,780
where a $10,000 hard wired sensor becomes
a $500 device you can install in minutes,
13
00:00:47,213 --> 00:00:49,949
and how that shift enables entirely
new use cases.
14
00:00:49,949 --> 00:00:52,819
We also dig into how companies
uncover opportunities for IoT,
15
00:00:52,819 --> 00:00:55,422
especially in brownfield environments,
and what it really means
16
00:00:55,422 --> 00:00:58,425
to put eyes on systems
that were previously manual.
17
00:00:58,425 --> 00:01:01,428
We finish up by covering workers
sentinel sensor, including how adding
18
00:01:01,428 --> 00:01:05,131
ultrasound extends predictive maintenance
from weeks out to potentially months out.
19
00:01:05,598 --> 00:01:07,400
This episode is sponsored
by the Helium Foundation
20
00:01:07,400 --> 00:01:09,969
and is dedicated
to spreading knowledge about LoRaWAN.
21
00:01:09,969 --> 00:01:13,973
If you'd like to try helium
publicly available global LoRaWAN for free
22
00:01:13,973 --> 00:01:18,611
and support this show, sign up at Meat
Sideshow Slash console.
23
00:01:19,112 --> 00:01:21,481
Now let's dig into the
conversation with Brittany.
24
00:01:23,516 --> 00:01:24,984
Brett,
thanks so much for coming on the show.
25
00:01:24,984 --> 00:01:26,453
Super psyched to have here. Awesome.
26
00:01:26,453 --> 00:01:27,620
Nick, thanks for having me.
27
00:01:27,620 --> 00:01:30,457
Excited to talk to you about LoRaWAN.
Yeah.
28
00:01:30,457 --> 00:01:30,924
I'm psyched.
29
00:01:30,924 --> 00:01:36,062
So you were at Chevron for geez,
almost 20 years, 17, 17.
30
00:01:36,062 --> 00:01:38,665
Okay, three short of two decades.
31
00:01:38,665 --> 00:01:41,668
Would you walk me through
kind of how long you've been in IoT?
32
00:01:41,768 --> 00:01:43,536
Was that IIoT industrial IoT?
33
00:01:43,536 --> 00:01:46,439
Was that there the entire time,
or was that something fairly recent?
34
00:01:46,439 --> 00:01:48,007
Kind of. Why did you get into it?
35
00:01:48,007 --> 00:01:52,212
So Chevron I kind of bounced around
within the general IoT space.
36
00:01:52,278 --> 00:01:54,481
My first experience kind of on the
37
00:01:54,481 --> 00:01:58,051
OT operational technology side,
I was in IT audit.
38
00:01:58,384 --> 00:02:02,255
So while I was in audit
I worked on auditing PCN systems.
39
00:02:02,288 --> 00:02:06,059
From there,
I moved into a role as a PCN administrator
40
00:02:06,192 --> 00:02:08,928
at a chemical plant
outside of New Orleans.
41
00:02:08,928 --> 00:02:12,899
I was there for four years,
got more familiar with kind of the OT
42
00:02:13,066 --> 00:02:16,035
side of things, and then I guess in 21
43
00:02:16,035 --> 00:02:19,639
I moved over to the industrial IoT space.
44
00:02:20,006 --> 00:02:21,808
Chevron big company.
45
00:02:21,808 --> 00:02:26,045
Obviously they have a pretty big team
dedicated to working on your IoT.
46
00:02:26,613 --> 00:02:30,250
So while I was there,
I got to kind of touch every aspect
47
00:02:30,250 --> 00:02:34,287
of industrial IoT
within a large multinational.
48
00:02:34,320 --> 00:02:36,623
Obviously, your oil and gas company.
49
00:02:36,623 --> 00:02:36,856
Yeah.
50
00:02:36,856 --> 00:02:38,892
Was there anything that
when you got over there
51
00:02:38,892 --> 00:02:40,860
that was a surprise to you
or that you felt like,
52
00:02:40,860 --> 00:02:44,063
oh, this is something super cool
that like, I wish more people knew about?
53
00:02:44,697 --> 00:02:47,700
I would say one of the
one of the big kind of eye
54
00:02:47,700 --> 00:02:51,037
opening things for me was there's
kind of this difference between
55
00:02:51,037 --> 00:02:55,441
your traditional operation technology,
your process control systems.
56
00:02:55,441 --> 00:02:59,012
You got your hard wired,
everything is very tightly controlled.
57
00:02:59,312 --> 00:03:03,316
Then moving into the IoT space,
first of all, at Chevron
58
00:03:03,316 --> 00:03:07,687
and kind of in general on the industry,
you don't see much control in IoT.
59
00:03:07,954 --> 00:03:09,656
It's more just monitoring.
60
00:03:09,656 --> 00:03:12,392
So for me,
it was kind of a mindset change moving
61
00:03:12,392 --> 00:03:15,361
from the process control side over to IoT.
62
00:03:15,628 --> 00:03:20,366
Well, at the same time, IoT
allows you to be so flexible,
63
00:03:20,366 --> 00:03:23,870
so agile compared
to your traditional process control.
64
00:03:24,137 --> 00:03:28,942
You're able to much more quickly, easily
and cheaply
65
00:03:29,242 --> 00:03:31,144
deploy these IoT solutions.
66
00:03:31,144 --> 00:03:31,477
For me,
67
00:03:31,477 --> 00:03:35,782
that was a huge eye opener compared
to the more traditional side of things.
68
00:03:36,316 --> 00:03:37,150
Oh, interesting.
69
00:03:37,150 --> 00:03:40,119
Just because they are pretty easy
to deploy and especially with LoRaWAN.
70
00:03:40,119 --> 00:03:42,155
Although across all of the IoT
technologies,
71
00:03:42,155 --> 00:03:45,158
you're just putting a thing in there,
kind of slapping it on and walking away
72
00:03:45,158 --> 00:03:48,161
versus figuring out how to control stuff
and make sure you don't screw it up.
73
00:03:48,595 --> 00:03:49,362
Absolutely.
74
00:03:49,362 --> 00:03:53,900
Like deploying a traditional sensor
in a control system, obviously you're
75
00:03:54,300 --> 00:03:58,371
you're running power out there,
you're running Ethernet out there.
76
00:03:58,371 --> 00:04:01,674
You have to go through
this huge management of change process,
77
00:04:01,741 --> 00:04:03,409
which takes months.
78
00:04:03,409 --> 00:04:05,245
All this equipment is very expensive.
79
00:04:05,245 --> 00:04:07,780
One sensor, it can be $10,000.
80
00:04:07,780 --> 00:04:11,384
Now you go to like a lower win
IoT situation.
81
00:04:11,651 --> 00:04:14,821
That sensor is going to cost 500 to $1000.
82
00:04:14,821 --> 00:04:17,790
And assuming
you already have your network in place,
83
00:04:17,824 --> 00:04:20,159
literally,
you walk up to a piece of equipment,
84
00:04:20,159 --> 00:04:24,197
you slap that sensor on there and within
a couple of minutes you've got data.
85
00:04:24,631 --> 00:04:28,001
So just the ease and quickness
and the cheapness with
86
00:04:28,134 --> 00:04:32,071
which you can deploy
IoT is really a game changer in my mind.
87
00:04:32,438 --> 00:04:35,508
Was there a sense in Chevron
88
00:04:35,842 --> 00:04:39,445
that IoT kind of wasn't
something they should do?
89
00:04:39,812 --> 00:04:43,116
It seems like one of the things
the biggest retardants to IoT
90
00:04:43,316 --> 00:04:45,485
adoption is people are just like,
I don't know about that stuff.
91
00:04:45,485 --> 00:04:46,653
I don't know if we really need it.
92
00:04:46,653 --> 00:04:49,989
And it seems like it's super valuable,
but it's like making the case
93
00:04:49,989 --> 00:04:53,626
that it's useful, as is probably
just as difficult as figuring out,
94
00:04:53,726 --> 00:04:55,928
if not more, is figuring out the RF
and the rest of the,
95
00:04:55,928 --> 00:04:57,530
you know, frequency hopping stuff.
96
00:04:57,530 --> 00:05:01,901
Yeah, while I would say there was,
you definitely ran to some resistance
97
00:05:01,901 --> 00:05:05,738
in deploying IoT solutions
at the end of the day,
98
00:05:06,172 --> 00:05:11,477
Chevron and I would say oil and gas
in general, they're pretty early adopters
99
00:05:11,477 --> 00:05:14,914
into the IoT LoRaWAN space,
especially within the US market.
100
00:05:14,914 --> 00:05:15,515
I know you do.
101
00:05:15,515 --> 00:05:19,285
You know the European markets a little bit
ahead of us, but in the US market.
102
00:05:19,319 --> 00:05:22,522
Oil and gas
was pretty early on the adoption phase.
103
00:05:22,922 --> 00:05:25,525
So the fact that Chevron had built out
this huge
104
00:05:25,525 --> 00:05:28,328
team,
you put this huge investment into it.
105
00:05:28,328 --> 00:05:32,765
With that,
they were able to kind of create their own
106
00:05:32,765 --> 00:05:34,600
ecosystem in very quickly.
107
00:05:34,600 --> 00:05:37,603
You start to realize value out of IoT.
108
00:05:37,603 --> 00:05:42,775
And that's something that they were quick
on a lot of other companies are very kind
109
00:05:42,775 --> 00:05:46,779
of just starting to dip their toes
in, starting to figure out what is IoT.
110
00:05:47,347 --> 00:05:50,917
Honestly, that's
what I'm doing it like to figure out
111
00:05:50,917 --> 00:05:55,054
these smaller to medium sized companies
who may not necessarily know IoT.
112
00:05:55,188 --> 00:05:55,822
Irwin.
113
00:05:55,822 --> 00:05:58,825
What these technologies are,
I'm trying to I'm here
114
00:05:58,825 --> 00:06:01,828
to help them figure out
how they can create value out of that.
115
00:06:02,061 --> 00:06:02,628
Okay.
116
00:06:02,628 --> 00:06:05,365
That leads really nicely
into the next question, which is, is there
117
00:06:05,365 --> 00:06:10,002
anything beyond just saving money
that you use when you're talking to small
118
00:06:10,002 --> 00:06:13,940
and medium sized companies as a reason
for them to adopt industrial IoT?
119
00:06:14,240 --> 00:06:15,241
Yeah, absolutely.
120
00:06:15,241 --> 00:06:18,378
I think the biggest thing
adopting industrial IoT
121
00:06:19,112 --> 00:06:22,548
is giving you eyes
where you currently don't have eyes.
122
00:06:22,949 --> 00:06:25,685
So a lot of the adoptions we're seeing are
123
00:06:25,685 --> 00:06:29,155
mostly
in the kind of the brownfield space,
124
00:06:29,155 --> 00:06:33,860
these established facilities
or plants, whatever it might be.
125
00:06:33,860 --> 00:06:35,395
So it's already there.
126
00:06:35,395 --> 00:06:38,931
And it's saying
with your current infrastructure,
127
00:06:38,998 --> 00:06:42,535
your current layout,
how can you get more value out of this?
128
00:06:42,535 --> 00:06:44,637
How can you get more efficiencies?
129
00:06:44,637 --> 00:06:49,308
How can you put eyes on something
that currently doesn't have eyes?
130
00:06:49,308 --> 00:06:52,645
Currently,
an operator has to go walk around
131
00:06:52,645 --> 00:06:56,582
to 60 tanks a day and visually
132
00:06:57,049 --> 00:07:01,220
look at something
visually take a level on a team.
133
00:07:01,554 --> 00:07:04,590
How can you make better use of their time?
134
00:07:05,024 --> 00:07:08,027
Instead of walking those rounds every day,
135
00:07:08,027 --> 00:07:11,130
they can look at a screen that's
going to give them the same information.
136
00:07:11,130 --> 00:07:14,867
They can get alerts that are going
to give them the same information.
137
00:07:14,867 --> 00:07:17,870
So it's kind of more of a proactive
approach.
138
00:07:18,104 --> 00:07:18,337
Right.
139
00:07:18,337 --> 00:07:19,439
And I bet that makes sense
140
00:07:19,439 --> 00:07:22,442
to a lot of a lot of business owners
who are saying, hey, I'm paying for this
141
00:07:22,975 --> 00:07:24,177
like expensive engineer.
142
00:07:24,177 --> 00:07:27,680
I can use their time to help design stuff
and create new things, rather than have
143
00:07:27,747 --> 00:07:28,381
to walk around and
144
00:07:29,348 --> 00:07:30,450
look at a button.
145
00:07:30,450 --> 00:07:34,887
Is there a bunch of conversion
of analog devices into smart sensors
146
00:07:34,887 --> 00:07:36,722
with what you're doing?
Or is it more like,
147
00:07:36,722 --> 00:07:39,692
hey, let's put something new on here,
walk me through that.
148
00:07:39,759 --> 00:07:43,029
So what we're mostly seeing now is
let's put something new on here.
149
00:07:43,062 --> 00:07:46,866
We have some type of equipment
that's currently not instrumented.
150
00:07:46,866 --> 00:07:50,470
So how can we get some data out of that?
151
00:07:50,470 --> 00:07:55,708
Essentially I do see slowly
and probably more so in the future.
152
00:07:55,708 --> 00:07:59,912
Going forward,
there will be more replacing
153
00:07:59,912 --> 00:08:03,282
those kind of hard wired with IoT devices.
154
00:08:03,616 --> 00:08:08,688
So I know, in the process control
industry, a lot of the life cycles on
155
00:08:08,688 --> 00:08:12,024
these systems are ten, 20,
maybe even 30 years.
156
00:08:12,525 --> 00:08:17,063
As they start to age, they're looking
to upgrade them, replace them.
157
00:08:17,530 --> 00:08:22,802
Well, you can replace a system
some five, $10,000 sensors.
158
00:08:23,069 --> 00:08:26,372
You can go
the same route, do the same thing, or for
159
00:08:26,572 --> 00:08:29,375
ten, maybe 20% of the cost,
160
00:08:29,375 --> 00:08:33,513
you can make those IoT as long as you're
not controlling anything.
161
00:08:33,513 --> 00:08:36,883
If you're just looking to monitor
it, have eyes on it.
162
00:08:37,216 --> 00:08:40,219
IoT is a perfect solution
in that situation.
163
00:08:40,586 --> 00:08:44,991
Interesting that there's such a point of
differentiation with this control piece.
164
00:08:44,991 --> 00:08:46,292
I haven't heard
165
00:08:46,292 --> 00:08:48,828
folks talk about that as much,
and that sounds like that's
166
00:08:48,828 --> 00:08:49,829
just coming from the background.
167
00:08:49,829 --> 00:08:52,665
Like, hey, I used to control everything,
and now I'm seeing that there's value
168
00:08:52,665 --> 00:08:55,601
in a lot of just observing
what's going on.
169
00:08:55,601 --> 00:08:56,769
Yeah, absolutely.
170
00:08:56,769 --> 00:09:00,039
And a lot of current process
control systems.
171
00:09:00,673 --> 00:09:03,509
Yeah. Everything is hard wired.
172
00:09:03,509 --> 00:09:06,445
It's super industrial, super heavy duty.
173
00:09:06,445 --> 00:09:09,982
I mean, you're getting millisecond
readings.
174
00:09:09,982 --> 00:09:12,685
Yeah. And that's good for some situations.
175
00:09:12,685 --> 00:09:15,721
But a lot of times
if you get a reading every 20,
176
00:09:15,755 --> 00:09:19,125
30 minutes,
even every hour, that's perfect.
177
00:09:19,125 --> 00:09:22,161
I mean, how often is a tank
changing level?
178
00:09:22,161 --> 00:09:24,797
They're doing draws
maybe once or twice a day.
179
00:09:24,797 --> 00:09:27,800
Well, you don't need readings
every second on that.
180
00:09:27,833 --> 00:09:31,771
You put a $500 thousand dollars
sensor on there.
181
00:09:31,771 --> 00:09:34,440
You take readings every 30 minute,
every hour.
182
00:09:34,440 --> 00:09:38,077
You're getting the same quality of data
for a way cheaper.
183
00:09:38,311 --> 00:09:40,146
Yep, that makes a ton of sense
184
00:09:40,146 --> 00:09:44,050
when you're coming into a new organization
and a potential customer.
185
00:09:44,450 --> 00:09:47,954
What are the ways that you think
about uncovering or discovering
186
00:09:48,054 --> 00:09:51,057
opportunities for them to use IoT?
187
00:09:51,123 --> 00:09:54,226
I think a big part of that
is just understanding their operation,
188
00:09:54,894 --> 00:09:57,563
understanding their business,
understanding their value
189
00:09:57,563 --> 00:10:00,566
chain, understanding their key processes.
190
00:10:00,700 --> 00:10:04,136
And as you start to look at those,
you can see,
191
00:10:04,337 --> 00:10:08,641
hey, you've got this process here
that's hugely automated
192
00:10:09,175 --> 00:10:12,812
and you got a lot of people involved there
manually touching things,
193
00:10:12,812 --> 00:10:14,246
manually looking at things.
194
00:10:14,246 --> 00:10:17,283
Not only is at a time
where it can also be a big safety issue,
195
00:10:17,416 --> 00:10:18,217
especially in the oil
196
00:10:18,217 --> 00:10:22,655
and gas space, they're huge on safety,
so that's always a big concern.
197
00:10:22,655 --> 00:10:25,658
But yeah, looking at those kind of
198
00:10:25,891 --> 00:10:29,128
what are their important systems,
what is currently manual,
199
00:10:29,395 --> 00:10:34,233
what could we easily go in and instrument
and get them data,
200
00:10:34,266 --> 00:10:39,305
get them actionable insights
and let them really have
201
00:10:39,872 --> 00:10:44,777
a great vision of this system
where essentially turning manual processes
202
00:10:44,777 --> 00:10:47,847
into more automated processes
now makes sense.
203
00:10:47,847 --> 00:10:50,282
So you go and understand the system
and then sit and kind of look
204
00:10:50,282 --> 00:10:53,419
for these key points of like, hey,
we're obviously where can we save money?
205
00:10:53,853 --> 00:10:56,689
Where can we make you more efficient,
where can we make you more safe?
206
00:10:56,689 --> 00:10:58,190
And maybe there's like 2 or 3
207
00:10:58,190 --> 00:11:00,459
more kind of columns that you,
that you hit or pillars that you hit.
208
00:11:00,459 --> 00:11:02,061
But that sounds about right.
209
00:11:02,061 --> 00:11:02,528
Yeah. Cool.
210
00:11:02,528 --> 00:11:07,133
So walk me through this sentinel thing
that we CA or Waka has just brought in.
211
00:11:07,133 --> 00:11:07,967
What is this thing?
212
00:11:07,967 --> 00:11:08,367
Yeah.
213
00:11:08,367 --> 00:11:11,404
So Sentinel,
it's lead by a company called a system.
214
00:11:11,404 --> 00:11:17,043
A system is a company that Wyck
recently became the majority owner of.
215
00:11:17,543 --> 00:11:20,212
So the Sentinel is a sensor.
216
00:11:20,212 --> 00:11:22,148
The most traditional way to think about it
217
00:11:22,148 --> 00:11:25,918
is it is a machinery health
monitoring sensor.
218
00:11:26,252 --> 00:11:29,588
So within this one sensor
there is temperature.
219
00:11:30,322 --> 00:11:34,493
It is also measuring the vibration
tri axial vibration.
220
00:11:34,927 --> 00:11:36,962
And I think the real secret sauce within
221
00:11:36,962 --> 00:11:39,965
it is
we also have ultrasound measurements.
222
00:11:40,232 --> 00:11:43,569
So the vibrations pretty typical.
223
00:11:43,569 --> 00:11:46,972
We see that a lot of different companies
have their version of vibration sensors.
224
00:11:47,273 --> 00:11:51,210
But bringing that extra level
of ultrasound into the sentinel sensor,
225
00:11:51,544 --> 00:11:56,382
what that allows us to do is get a whole
nother level of analysis.
226
00:11:56,816 --> 00:12:00,853
So your traditional vibration sensor,
you can go to
227
00:12:01,721 --> 00:12:05,091
five,
maybe ten kilohertz, a vibration detection
228
00:12:05,091 --> 00:12:08,994
with the ultrasound, you're able
to take that up to 60 to 70kHz.
229
00:12:09,328 --> 00:12:14,800
Now what this ultimately allows you to do
is to get a further look into the future.
230
00:12:15,134 --> 00:12:17,970
So you put this sensor on
231
00:12:17,970 --> 00:12:22,174
any type of rotating machinery,
whether that's a pump, a motor,
232
00:12:22,508 --> 00:12:27,446
a compressor, you put it on there
and it's able to perform analysis.
233
00:12:27,446 --> 00:12:31,150
A big part of this sentinel
is also a machine learning aspect
234
00:12:31,484 --> 00:12:33,552
that we're able to do on our platform.
235
00:12:33,552 --> 00:12:37,590
So yeah, you take in all this data,
you kind of determine what's baseline.
236
00:12:38,023 --> 00:12:40,826
And then off of that you're able to say,
237
00:12:40,826 --> 00:12:46,265
hey, I'm detecting some weird sound
and the machine learning
238
00:12:46,265 --> 00:12:49,502
is able to actually say, hey,
I detected this type of sound.
239
00:12:49,502 --> 00:12:52,471
This can mean
that you have a bearing going bad.
240
00:12:52,872 --> 00:12:57,710
And once you have that level of analysis,
then you can have one of your engineers
241
00:12:57,710 --> 00:13:01,013
go and say, hey,
something's going wrong with this motor.
242
00:13:01,180 --> 00:13:03,048
Let me go out and check it.
243
00:13:03,048 --> 00:13:06,218
Whereas your traditional
kind of processes,
244
00:13:06,786 --> 00:13:09,989
maybe once every week, every month
245
00:13:10,356 --> 00:13:14,693
at best, you have a mobile sensor
that you put on a piece of equipment.
246
00:13:14,727 --> 00:13:17,429
You kind of listen,
I mean, even more traditional,
247
00:13:17,429 --> 00:13:21,500
you have engineers out there
who will literally tap on something,
248
00:13:21,500 --> 00:13:24,036
or they'll put their ears up to it
and listen.
249
00:13:24,036 --> 00:13:26,372
And these are
professionals are very good at their job.
250
00:13:26,372 --> 00:13:30,543
But when you can put a sensor on there
that's doing that 24 over seven
251
00:13:30,543 --> 00:13:35,247
and is able to do it at, a deeper level,
I think that's a real game changer.
252
00:13:35,848 --> 00:13:38,417
What's the performance difference
when you add
253
00:13:38,417 --> 00:13:41,654
an ultrasound versus
just the vibration sensors?
254
00:13:41,720 --> 00:13:42,688
There's a
255
00:13:42,688 --> 00:13:45,090
maybe not a metric ton of those
in the market, but there's a lot of
256
00:13:45,090 --> 00:13:47,660
a lot of kind of machinery
listening sensors on the market.
257
00:13:47,660 --> 00:13:50,462
There's ultrasound
sounds like it's pretty fancy and special.
258
00:13:50,462 --> 00:13:52,298
Like how much better is it?
259
00:13:52,298 --> 00:13:54,033
I guess the question. Yeah.
260
00:13:54,033 --> 00:13:59,638
So the best way I know to quantify that
from data I've seen is that, vibration.
261
00:13:59,638 --> 00:14:03,108
And typically they can see issues
262
00:14:03,108 --> 00:14:06,645
that are maybe a couple weeks
or a month out.
263
00:14:06,645 --> 00:14:09,148
So we're starting to tuck this vibration.
264
00:14:09,148 --> 00:14:11,083
Something's going on.
265
00:14:11,083 --> 00:14:13,452
Maybe in a couple weeks
it could become a real issue.
266
00:14:13,452 --> 00:14:16,989
So I had to do something about it
with the ultrasound capability.
267
00:14:17,623 --> 00:14:20,159
From what I've seen,
were able to detect issues
268
00:14:20,159 --> 00:14:23,462
that are like three,
maybe even four months out year.
269
00:14:23,462 --> 00:14:23,729
Okay.
270
00:14:23,729 --> 00:14:27,066
So it's less severe
that what the vibrations able to detect.
271
00:14:27,299 --> 00:14:30,302
So you have this little thing
that's starting to go wrong.
272
00:14:30,302 --> 00:14:33,272
Not an issue now but keep an eye on it.
273
00:14:33,272 --> 00:14:36,842
Maybe go ahead and order that back up part
so you can have it ready.
274
00:14:36,842 --> 00:14:38,410
Yeah. So that's that's kind of the beauty.
275
00:14:38,410 --> 00:14:40,012
It allows you to see kind of
276
00:14:40,012 --> 00:14:43,515
further into the future
to do your predictive maintenance.
277
00:14:44,917 --> 00:14:46,752
Oh that's that's rad.
278
00:14:46,752 --> 00:14:47,753
Super cool.
279
00:14:47,753 --> 00:14:48,420
Let's see.
280
00:14:48,420 --> 00:14:50,122
Let's wrap this up a little bit.
281
00:14:50,122 --> 00:14:53,525
On a slightly more personal note,
you're way into beer.
282
00:14:53,559 --> 00:14:55,160
We were talking a little bit
about building
283
00:14:55,160 --> 00:14:59,064
breweries and sensing or sunsetting
whatever it is, instrumenting breweries
284
00:14:59,198 --> 00:15:01,100
before we recorded.
285
00:15:01,100 --> 00:15:05,971
Maybe we start with this idea
of kind of consumer versus industrial IoT,
286
00:15:06,272 --> 00:15:09,975
and what the big differences are and walk
you through kind of what that looks like.
287
00:15:09,975 --> 00:15:12,978
And is there a difference
or is it kind of IoT as IoT?
288
00:15:13,545 --> 00:15:15,948
Yeah,
there's definitely a difference there.
289
00:15:15,948 --> 00:15:16,315
I think it's
290
00:15:16,315 --> 00:15:19,518
kind of important to understand
and there's also different levels to it.
291
00:15:19,518 --> 00:15:23,455
One example recently I was at one of
my favorite breweries here in Denver.
292
00:15:23,756 --> 00:15:25,658
I was talking to the owner.
293
00:15:25,658 --> 00:15:28,260
He was mentioning
they had a temperature sensor
294
00:15:28,260 --> 00:15:32,965
in their cold box that had been kind of
iffy, wasn't giving them great data.
295
00:15:32,965 --> 00:15:34,600
I'm like, oh, interesting.
296
00:15:34,600 --> 00:15:37,303
Well, my company I worked for, white Guy.
297
00:15:37,303 --> 00:15:40,606
We actually have a solution
that could solve that, but
298
00:15:41,006 --> 00:15:44,009
they're using kind of a
more consumer grade IoT.
299
00:15:44,143 --> 00:15:46,278
It was probably like $50 sensor.
300
00:15:46,278 --> 00:15:48,781
And for the most part, it worked
well for them.
301
00:15:48,781 --> 00:15:53,252
And also at this cold box, if
the sensor went bad, the cold box was hot.
302
00:15:53,552 --> 00:15:54,386
They had other ways,
303
00:15:54,386 --> 00:15:57,823
kind of secondary ways to look at it
and see what the temperature was.
304
00:15:58,157 --> 00:16:00,292
So your industrial grade IoT,
305
00:16:00,292 --> 00:16:03,228
it's not going to be as cheap
as your consumer grade,
306
00:16:03,228 --> 00:16:08,334
but it's going to be much more reliable,
much more durable.
307
00:16:08,367 --> 00:16:11,170
It's designed to be in more extreme
environments.
308
00:16:11,170 --> 00:16:14,940
When you say industrial IoT,
you're deploying at various sites,
309
00:16:14,940 --> 00:16:18,477
chemical plants, manufacturing facilities,
a lot of times
310
00:16:18,477 --> 00:16:21,347
there are hazardous gases,
so you don't want anything
311
00:16:21,347 --> 00:16:24,550
that could potentially cause
a spark in an explosion.
312
00:16:24,550 --> 00:16:26,852
And we don't want things to blow up.
313
00:16:26,852 --> 00:16:27,252
So yeah.
314
00:16:27,252 --> 00:16:31,256
Industrial non-optimal
yeah yeah yeah yeah.
315
00:16:31,256 --> 00:16:33,092
And not looking for that in general. Okay.
316
00:16:33,092 --> 00:16:33,993
And then
317
00:16:33,993 --> 00:16:38,964
just as an example of what you might do
if you had to go in today and today is
318
00:16:38,964 --> 00:16:40,966
I think we're recording on Wednesday,
by the end of the week,
319
00:16:40,966 --> 00:16:44,103
you had to close a brewery
on a sensor somewhere.
320
00:16:44,103 --> 00:16:49,041
And what are Denver, what would you target
as a as the kind of pitch?
321
00:16:49,041 --> 00:16:51,143
Because that seems like an industry
you're pretty familiar with.
322
00:16:51,143 --> 00:16:53,712
So you wouldn't
have to learn that much about it.
323
00:16:53,712 --> 00:16:55,381
What would you kind of walk into
any given brewery and be like,
324
00:16:55,381 --> 00:16:57,349
I know they're going to need this.
325
00:16:57,349 --> 00:17:02,087
So, I mean, temperatures as you age one,
you got all types of mass of equipment
326
00:17:02,087 --> 00:17:06,425
that's cheating product, cooling it down.
327
00:17:06,425 --> 00:17:12,031
So being able to monitor that
and keep an eye on it is a huge space.
328
00:17:12,031 --> 00:17:15,100
I will say that most of the modern
brewing equipment
329
00:17:15,567 --> 00:17:19,071
usually has all this sensing
kind of already built in.
330
00:17:19,338 --> 00:17:22,374
If you're buying
one of the new state of the art systems.
331
00:17:22,374 --> 00:17:26,478
All of this is kind of built
in, which is cool to see, but let's say
332
00:17:26,478 --> 00:17:31,650
tomorrow, cures here nearby in Golden,
they call me up.
333
00:17:31,650 --> 00:17:35,521
Hey, we're having some issues
with our instrumentation here.
334
00:17:35,521 --> 00:17:36,922
What can you offer?
335
00:17:36,922 --> 00:17:37,423
I'm a go.
336
00:17:37,423 --> 00:17:40,959
And number one,
what's your temperature look like?
337
00:17:40,959 --> 00:17:43,695
Number two, what is pressure look like?
338
00:17:43,695 --> 00:17:46,832
You're moving around a lot of liquid,
a lot of volume.
339
00:17:46,832 --> 00:17:48,534
Sometimes it's pressurized.
340
00:17:48,534 --> 00:17:52,871
So being able to monitor that,
keep an eye on it is another huge system.
341
00:17:53,305 --> 00:17:53,972
Super cool.
342
00:17:53,972 --> 00:17:56,175
And I can see with certainly
with the bigger breweries, with Coors,
343
00:17:56,175 --> 00:17:59,311
or even a kind of midsize brewery
that they're going to be willing to pay
344
00:17:59,645 --> 00:18:03,115
the industrial IoT prices versus like,
hey, I'll just order this thing
345
00:18:03,115 --> 00:18:05,284
off the internet,
have it here tomorrow. Absolutely.
346
00:18:05,284 --> 00:18:07,753
I mean, it
obviously depends on the type of system.
347
00:18:07,753 --> 00:18:09,888
And industrial IoT isn't for everything.
348
00:18:09,888 --> 00:18:13,692
But in these big manufacturing facilities,
which breweries are
349
00:18:13,692 --> 00:18:17,096
I mean, they're just
they're manufacturing a delicious product
350
00:18:17,096 --> 00:18:19,565
that we like to drink,
but that's all it is.
351
00:18:19,565 --> 00:18:20,899
It's a manufacturing facility.
352
00:18:20,899 --> 00:18:22,134
So, yeah, and something like that,
353
00:18:22,134 --> 00:18:25,204
when you have the huge scale industrial
IoT makes sense.
354
00:18:25,637 --> 00:18:26,071
Ripping.
355
00:18:26,071 --> 00:18:27,606
Well, thanks so much for making time today
356
00:18:27,606 --> 00:18:29,808
and coming on
and talking to us a little bit about IoT.
357
00:18:29,808 --> 00:18:32,811
We want to hit on the lower end stuff,
but I think for this audience,
358
00:18:33,078 --> 00:18:34,713
they've got a pretty good understanding
of how it works.
359
00:18:34,713 --> 00:18:35,414
So it's super cool
360
00:18:35,414 --> 00:18:38,517
to see really the perspective
that you bring to the industry.
361
00:18:38,517 --> 00:18:39,918
Thanks. Thanks. Coming on.
362
00:18:39,918 --> 00:18:40,519
Awesome.
363
00:18:40,519 --> 00:18:42,788
Great talking to you, Nik,
and thanks for having me on.
364
00:18:45,457 --> 00:18:48,460
That's it for
this episode of The Business of LoRaWAN.
365
00:18:48,660 --> 00:18:51,430
If you want to go deeper
and actually deploy devices,
366
00:18:51,430 --> 00:18:54,533
the MeteoScientific
Console is the fastest way to do that,
367
00:18:54,833 --> 00:18:57,870
and honestly, it's
also the best way to support the show.
368
00:18:58,670 --> 00:19:02,007
When you use the console, you're not just
listening, you're participating
369
00:19:02,007 --> 00:19:05,577
in the same real world LoRaWAN work
we talk about here every week.
370
00:19:06,044 --> 00:19:09,581
You can get started with the free trial
at Medio scientific.com.
371
00:19:10,315 --> 00:19:13,152
Huge thanks to the sponsor of the show,
the Helium Foundation,
372
00:19:13,152 --> 00:19:16,155
for supporting open LoRaWAN
infrastructure worldwide.
373
00:19:16,588 --> 00:19:20,359
Check them out at helium Dot Foundation
and if the show has been
374
00:19:20,359 --> 00:19:23,428
useful, a quick rating or review
on Apple Podcasts or wherever you listen.
375
00:19:23,462 --> 00:19:24,396
This really helps
376
00:19:24,396 --> 00:19:27,399
people find it and helps the show grow
so we can help more people.
377
00:19:27,733 --> 00:19:29,701
I'm Nik Hawks with MeteoScientific.
378
00:19:29,701 --> 00:19:30,769
I'll catch you on the next episode.