WEBVTT
Language: en-US

1
00:00:01.110 --> 00:00:07.949
<v Speaker 1>Uh, anymore around adoption of, um, I, I
now think it's

2
00:00:07.949 --> 00:00:12.189
<v Speaker 1>more a a reluctance of who to choose to go
with.

3
00:00:12.590 --> 00:00:19.069
<v Speaker 1>So I think the, the value is there, uh,
and, and I think that's well

4
00:00:19.069 --> 00:00:19.750
<v Speaker 1>articulated.

5
00:00:19.829 --> 00:00:26.350
<v Speaker 1>Everybody now can see, jeez, this is a, a
real game changer and it's, it's, uh, I

6
00:00:26.350 --> 00:00:27.059
<v Speaker 1>want to change.

7
00:00:27.149 --> 00:00:29.510
<v Speaker 1>I want to adopt, I want these benefits.

8
00:00:31.079 --> 00:00:36.250
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens, and now your host, Nel

9
00:00:36.250 --> 00:00:36.830
<v Speaker 2>Sullivan.

10
00:00:39.790 --> 00:00:44.439
<v Niall Sullivan>Hello and welcome to the latest episode of
the trend detection podcast.

11
00:00:45.000 --> 00:00:49.430
<v Niall Sullivan>Um, today I'm once again joined um by my
very esteemed colleague Richard Ella, all

12
00:00:49.430 --> 00:00:54.189
<v Niall Sullivan>the way in Australia, um, you know, he's
been on the podcast many, many times and he

13
00:00:54.189 --> 00:00:57.360
<v Niall Sullivan>keeps getting invited back cos we talk
about such interesting stuff.

14
00:00:57.880 --> 00:00:59.540
<v Niall Sullivan>Um, and today is no different.

15
00:00:59.599 --> 00:01:01.200
<v Niall Sullivan>Um, we're talking about data.

16
00:01:01.740 --> 00:01:07.459
<v Niall Sullivan>Um, and this, uh, let's say, issue where,
um, about having too much data and not

17
00:01:07.459 --> 00:01:07.940
<v Niall Sullivan>enough action.

18
00:01:08.019 --> 00:01:12.260
<v Niall Sullivan>So you're sitting on piles and piles and
piles of data but not actually getting the

19
00:01:12.260 --> 00:01:15.569
<v Niall Sullivan>insights from it that, that it deserves,
really, I guess.

20
00:01:16.099 --> 00:01:19.620
<v Niall Sullivan>But, um, I'm gonna sort of hand over to
Richard to get us started.

21
00:01:19.699 --> 00:01:21.910
<v Niall Sullivan>I think we all know who Richard is by now.

22
00:01:21.980 --> 00:01:25.410
<v Niall Sullivan>Maybe one sentence of who you are,
Richard, for new newcomers, and then maybe you

23
00:01:25.410 --> 00:01:26.819
<v Niall Sullivan>could just give a bit of background on the
topics.

24
00:01:26.860 --> 00:01:30.720
<v Niall Sullivan>I know you brought this to sort of brought
this to the table, so over to you.

25
00:01:32.069 --> 00:01:33.769
<v Speaker 1>Yeah, thank you Nia.

26
00:01:34.040 --> 00:01:40.709
<v Speaker 1>Um, again, just thank you for, for, for
doing these, um, these

27
00:01:40.970 --> 00:01:41.529
<v Speaker 1>podcasts.

28
00:01:41.610 --> 00:01:43.120
<v Speaker 1>I think they are absolutely brilliant.

29
00:01:43.129 --> 00:01:49.400
<v Speaker 1>It's really feeding into How we change,
um, learning, you know, we, we've, we've

30
00:01:49.400 --> 00:01:52.400
<v Speaker 1>become a micro-learning, um, kind of
community.

31
00:01:52.480 --> 00:01:57.279
<v Speaker 1>It's the only way we can stay relevant and
you really are feeding into this, this

32
00:01:57.279 --> 00:02:02.519
<v Speaker 1>micro-learning where you can listen to a
podcast on the, on the tub on your way to

33
00:02:02.519 --> 00:02:07.569
<v Speaker 1>work or you You, you know, you, you, you
have this gap where you just, uh,

34
00:02:07.620 --> 00:02:13.419
<v Speaker 1>incrementally, uh, improve, um, and, and,
um, this really feeds into that.

35
00:02:13.619 --> 00:02:15.809
<v Speaker 1>And, and thank you for the, the
opportunity.

36
00:02:16.259 --> 00:02:20.940
<v Speaker 1>Today's topic is something that I've been
very interested in, um, throughout my

37
00:02:20.940 --> 00:02:26.899
<v Speaker 1>career, um, and even on a, on a personal
note, you know, so, I know, you know, we

38
00:02:26.899 --> 00:02:29.679
<v Speaker 1>talk about Sensii and we talk about the
value.

39
00:02:30.100 --> 00:02:36.710
<v Speaker 1>Um, that, that what, what since I can
actually do with your data, but before that,

40
00:02:37.250 --> 00:02:43.289
<v Speaker 1>what we are seeing are quite prevalent in,
uh, when we talk about digitalization or

41
00:02:43.289 --> 00:02:45.110
<v Speaker 1>we talk about a digital adoption.

42
00:02:45.410 --> 00:02:48.009
<v Speaker 1>is how do you get started?

43
00:02:48.250 --> 00:02:52.630
<v Speaker 1>And this is not a customer, this is not an
industry.

44
00:02:52.970 --> 00:02:59.720
<v Speaker 1>This is, uh, really comes down to, um, you
know, personal beliefs and,

45
00:02:59.729 --> 00:03:06.729
<v Speaker 1>and how do you actually change and, um,
the, what we're going to talk about today is

46
00:03:06.729 --> 00:03:09.949
<v Speaker 1>basically too much data and not enough
action.

47
00:03:10.289 --> 00:03:16.179
<v Speaker 1>Um, and one of the phrases that I
absolutely love, and I picked it up very early on

48
00:03:16.179 --> 00:03:22.539
<v Speaker 1>in my career when I, when I, I bought my
first, uh, Fitbit, uh, uh, to track my

49
00:03:22.539 --> 00:03:25.699
<v Speaker 1>steps was paralysis in analysis.

50
00:03:25.820 --> 00:03:28.380
<v Speaker 1>And I was like, that's a bit of a geeky
word.

51
00:03:28.779 --> 00:03:30.279
<v Speaker 1>What does it actually mean?

52
00:03:30.570 --> 00:03:37.500
<v Speaker 1>Um, and, and what it actually meant at the
time for me was, Um, because I had this

53
00:03:37.500 --> 00:03:42.220
<v Speaker 1>Fitbit and it was technology and I was
counting my steps in my sleep and I was

54
00:03:42.220 --> 00:03:47.380
<v Speaker 1>studying, I was trying to get fitter, um,
and I'm always trying to look at, uh,

55
00:03:47.500 --> 00:03:53.160
<v Speaker 1>being healthier and, um, and being a data
guy, absolutely loved the data.

56
00:03:53.190 --> 00:03:59.860
<v Speaker 1>And, um, but what actually happens is you
get into a trap where the more information

57
00:03:59.860 --> 00:04:03.600
<v Speaker 1>you get, the more educated you get, the
more stuck you get.

58
00:04:03.940 --> 00:04:10.750
<v Speaker 1>Um, and Um, it's, it's only until somebody
comes along and actually breaks that

59
00:04:10.750 --> 00:04:16.959
<v Speaker 1>thinking and breaks that cycle of analysis
to say, listen, What are you're actually

60
00:04:16.959 --> 00:04:18.339
<v Speaker 1>trying to achieve here?

61
00:04:18.519 --> 00:04:24.820
<v Speaker 1>Are you, um, be that predictive
maintenance or be that better health.

62
00:04:25.160 --> 00:04:30.230
<v Speaker 1>Um, and so there's this, there's this
common phenomenon where we call it, um,

63
00:04:30.279 --> 00:04:36.250
<v Speaker 1>paralysis in analysis and, you know,
coming back to the UK it even goes back as far

64
00:04:36.250 --> 00:04:38.239
<v Speaker 1>as, uh, Winston Churchill.

65
00:04:38.279 --> 00:04:43.440
<v Speaker 1>I think he had a quote that was, uh,
perfection is actually better spelled

66
00:04:43.440 --> 00:04:44.160
<v Speaker 1>paralysis.

67
00:04:44.559 --> 00:04:51.480
<v Speaker 1>Um, and what that actually means is that,
um, we are, to get started, we've

68
00:04:51.480 --> 00:04:56.670
<v Speaker 1>got a lot of data, we've got a lot of
options, and we've got, we, we, we, we, we get

69
00:04:56.670 --> 00:04:57.350
<v Speaker 1>stuck there.

70
00:04:57.399 --> 00:05:04.179
<v Speaker 1>And so, Um, and since I in, in the
predictive maintenance space is

71
00:05:04.179 --> 00:05:10.619
<v Speaker 1>the, the most powerful tool I've seen
break that cycle of traditional condition

72
00:05:10.619 --> 00:05:16.279
<v Speaker 1>monitoring to, hey, let's, let's, what are
you actually trying to achieve here, um,

73
00:05:16.929 --> 00:05:18.549
<v Speaker 1>on your return on investment?

74
00:05:18.899 --> 00:05:22.380
<v Speaker 1>Are you looking at, um, improving your
schedule?

75
00:05:22.589 --> 00:05:24.390
<v Speaker 1>Maintenance or your downtime.

76
00:05:24.470 --> 00:05:30.510
<v Speaker 1>All of those things that everybody is
trying to do with the, with the traditional

77
00:05:30.510 --> 00:05:37.269
<v Speaker 1>condition monitoring and it requires a lot
of analysis and it requires a lot of

78
00:05:37.269 --> 00:05:37.679
<v Speaker 1>effort.

79
00:05:38.059 --> 00:05:42.730
<v Speaker 1>Um, and so now Sensai comes along and
says, listen, we can achieve the same thing,

80
00:05:42.989 --> 00:05:45.190
<v Speaker 1>but in a better way, in a smarter way.

81
00:05:45.230 --> 00:05:52.170
<v Speaker 1>And so, Um, so the first part of this para
paralysis in analysis

82
00:05:52.390 --> 00:05:54.730
<v Speaker 1>is understanding that our customers are
stuck in their data.

83
00:05:55.350 --> 00:06:02.269
<v Speaker 1>Um, and it's, um, and it's with all the
good intentions in the world, um, you know,

84
00:06:02.390 --> 00:06:06.589
<v Speaker 1>there, there's a reason why they got the
data is because they wanted to use the

85
00:06:06.589 --> 00:06:12.029
<v Speaker 1>data, but, um, with traditional condition
monitoring and traditional tools.

86
00:06:12.329 --> 00:06:17.700
<v Speaker 1>Um, it, it got stuck in the event, uh,
rules or the rules-based world.

87
00:06:18.000 --> 00:06:24.600
<v Speaker 1>And so, so that's really what we want to,
uh, to talk about today is, uh, how do we

88
00:06:24.600 --> 00:06:29.239
<v Speaker 1>break that cycle of, of, um, I've got all
this information, but how do I get

89
00:06:29.239 --> 00:06:29.549
<v Speaker 1>started?

90
00:06:29.760 --> 00:06:30.549
<v Speaker 1>Who do I choose?

91
00:06:30.799 --> 00:06:36.000
<v Speaker 1>Why do I choose them, um, and, um, getting
the tap on the shoulder and say, listen,

92
00:06:36.239 --> 00:06:40.739
<v Speaker 1>let's rethink this a little bit and, and
lay a roadmap of how to get started.

93
00:06:41.450 --> 00:06:42.480
<v Speaker 1>Um, now.

94
00:06:43.940 --> 00:06:47.420
<v Niall Sullivan>Yeah, so I guess first of all, um, I think
that's the first time Winston Churchill's

95
00:06:47.420 --> 00:06:48.700
<v Niall Sullivan>been quoted on the podcast.

96
00:06:48.790 --> 00:06:52.220
<v Niall Sullivan>Hopefully not the last, but, um, good,
nice, nice quote in there.

97
00:06:52.299 --> 00:06:56.940
<v Niall Sullivan>Um, but I, I guess the first point, um, to
make is you, you mentioned that it's not

98
00:06:56.940 --> 00:07:00.760
<v Niall Sullivan>like a recent phenomenon, so I guess
people would presume with technology and things

99
00:07:00.760 --> 00:07:04.540
<v Niall Sullivan>like that we're talking about, you know,
data analysis now, but obviously data

100
00:07:04.540 --> 00:07:06.779
<v Niall Sullivan>collection's been a thing for much longer,
right?

101
00:07:06.899 --> 00:07:09.700
<v Niall Sullivan>This is a, it's been going on for many
years.

102
00:07:11.989 --> 00:07:13.470
<v Speaker 1>Yeah, certainly.

103
00:07:13.609 --> 00:07:20.209
<v Speaker 1>And uh with the, this whole shift of
generative AI it's um

104
00:07:20.709 --> 00:07:24.600
<v Speaker 1>it's, it's breaking the way that we
interact with that data.

105
00:07:24.989 --> 00:07:25.230
<v Speaker 1>All right.

106
00:07:25.350 --> 00:07:32.029
<v Speaker 1>So if we look at what Sensai has adopted
with a generative AI into traditional

107
00:07:32.029 --> 00:07:35.369
<v Speaker 1>machine learning AI it's a completely new
experience.

108
00:07:35.769 --> 00:07:40.540
<v Speaker 1>Um, you don't have your traditional fault
code spitting out something that you've

109
00:07:40.540 --> 00:07:46.739
<v Speaker 1>got to go read the manual and it's not
conversational like and, um, and really hats

110
00:07:46.739 --> 00:07:49.940
<v Speaker 1>off to, to Sensai for, for leading the way
on this.

111
00:07:50.260 --> 00:07:56.239
<v Speaker 1>You know, there's a lot of, um, generative
AI talk about, uh, how we,

112
00:07:56.619 --> 00:08:03.540
<v Speaker 1>um, wrap this into, into products and, um,
and There are a lot of

113
00:08:03.540 --> 00:08:10.329
<v Speaker 1>products that wrap generative AI around
it, but not many, uh, solutions that

114
00:08:10.329 --> 00:08:16.980
<v Speaker 1>embedded in its, uh, offering to, um, to,
to not just be a chatbot, not just be

115
00:08:16.980 --> 00:08:20.220
<v Speaker 1>something that, um, is just an extension
of

116
00:08:20.220 --> 00:08:21.100
<v Speaker 1>chat GPT.

117
00:08:21.500 --> 00:08:27.119
<v Speaker 1>It's actually a built-in language learning
model so that you really derive um.

118
00:08:27.589 --> 00:08:32.270
<v Speaker 1>Insights into, into, into your data and
you're having that conversation, which look,

119
00:08:32.549 --> 00:08:38.830
<v Speaker 1>for me, um, um, it's just a breath of
fresh air because uh that's, that's what

120
00:08:38.830 --> 00:08:39.690
<v Speaker 1>customers want.

121
00:08:39.989 --> 00:08:45.099
<v Speaker 1>That we want to move beyond, um, just
spending time Reading manuals and those kind

122
00:08:45.099 --> 00:08:45.409
<v Speaker 1>of things.

123
00:08:45.659 --> 00:08:49.739
<v Speaker 1>We just want to get as close to the
diagnostic as soon as possible.

124
00:08:49.859 --> 00:08:52.780
<v Speaker 1>So this data problem is not new.

125
00:08:52.940 --> 00:08:57.640
<v Speaker 1>Um, I, I think people, we, we can, you can
call it overwhelming.

126
00:08:57.900 --> 00:09:00.320
<v Speaker 1>Um, people have it all the time.

127
00:09:01.000 --> 00:09:07.700
<v Speaker 1>But, um, in the industrial world, um, this
is very prevalent because,

128
00:09:08.000 --> 00:09:14.400
<v Speaker 1>um, a lot of sites are coming on board now
and connectivity is a

129
00:09:14.400 --> 00:09:15.119
<v Speaker 1>prerequisite.

130
00:09:15.479 --> 00:09:20.869
<v Speaker 1>So they've got all of this data without
any effort, um, because of edge capability,

131
00:09:21.119 --> 00:09:22.400
<v Speaker 1>IoT integration.

132
00:09:22.479 --> 00:09:26.960
<v Speaker 1>All of these things are coming, uh, kind
of really connected.

133
00:09:27.320 --> 00:09:31.400
<v Speaker 1>Um, and, um, how, how do you actually
convert that is important.

134
00:09:33.159 --> 00:09:37.520
<v Niall Sullivan>Yeah, and I guess, um, that what I was
thinking first of all is, you know, how, how

135
00:09:37.520 --> 00:09:40.940
<v Niall Sullivan>do, you know, if we talk about the
industrial setting, you know, how do

136
00:09:40.940 --> 00:09:45.679
<v Niall Sullivan>organizations end up with too much data,
you know, how, how does that happen, I

137
00:09:45.679 --> 00:09:49.719
<v Niall Sullivan>guess, um, and the, and I guess from my
point of view I've spoken, I've been at

138
00:09:49.719 --> 00:09:51.039
<v Niall Sullivan>events and spoken to people and.

139
00:09:51.619 --> 00:09:54.400
<v Niall Sullivan>Uh this was a few years ago now, but when
they were talking about, oh yeah, we've

140
00:09:54.400 --> 00:09:58.219
<v Niall Sullivan>gathered all this data, but we, we've no
idea what to do with it now.

141
00:09:58.340 --> 00:10:00.219
<v Niall Sullivan>And I guess that's part of what we're
talking about today.

142
00:10:00.299 --> 00:10:04.150
<v Niall Sullivan>But do you know how people sort of get,
got into that situation to start with, of

143
00:10:04.460 --> 00:10:05.719
<v Niall Sullivan>sitting on mounds of data.

144
00:10:07.750 --> 00:10:14.210
<v Speaker 1>Yeah, look, whenever a project goes to
work, um, or a project gets deployed,

145
00:10:14.469 --> 00:10:19.390
<v Speaker 1>um, there are minimum requirements that
get set up for communications.

146
00:10:19.830 --> 00:10:24.530
<v Speaker 1>Um, and this is now becoming, um, you
know, standard.

147
00:10:24.640 --> 00:10:31.159
<v Speaker 1>So if I put in a drive or a flow meter or
some kind of device, um, that

148
00:10:31.159 --> 00:10:33.440
<v Speaker 1>data is now becoming standard.

149
00:10:33.599 --> 00:10:40.034
<v Speaker 1>So, um, and usually during the project
onboarding, That information gets,

150
00:10:40.255 --> 00:10:45.835
<v Speaker 1>um, gets declared with all the best
intention, uh, in the world.

151
00:10:46.135 --> 00:10:51.804
<v Speaker 1>Every customer, um, thinks that when
they're on board, they'll bring this in, it'll

152
00:10:51.804 --> 00:10:56.414
<v Speaker 1>go into this magic box and, you know, it's
just going to tell, tell them everything.

153
00:10:56.820 --> 00:11:03.270
<v Speaker 1>And, um, and traditionally, uh, it
required data scientists, it

154
00:11:03.270 --> 00:11:09.710
<v Speaker 1>required subject matter experts, it
required coders, um, and all of them to study

155
00:11:09.710 --> 00:11:13.510
<v Speaker 1>the application and then derive uh value
out of that.

156
00:11:13.590 --> 00:11:19.830
<v Speaker 1>And so, Um, the reason why, um, our
customers are experiencing this is because

157
00:11:19.830 --> 00:11:20.840
<v Speaker 1>that's not scalable.

158
00:11:21.159 --> 00:11:27.440
<v Speaker 1>You, you just can't, um, deploy, you know,
these

159
00:11:27.440 --> 00:11:30.719
<v Speaker 1>people just to go and do individual
things.

160
00:11:30.760 --> 00:11:34.460
<v Speaker 1>You need to change the way that you look
at your data.

161
00:11:34.479 --> 00:11:38.520
<v Speaker 1>And, and so, Um, so when we look at mine
sites, this is massive.

162
00:11:38.809 --> 00:11:41.070
<v Speaker 1>So, uh, we've got lots of data.

163
00:11:41.489 --> 00:11:45.070
<v Speaker 1>We, we're commissioning new equipment, all
of it, uh, every day.

164
00:11:45.409 --> 00:11:51.549
<v Speaker 1>And, um, all of this information is just
going into the skater usually, uh, and then

165
00:11:51.549 --> 00:11:53.429
<v Speaker 1>usually kind of sits in a historian.

166
00:11:53.890 --> 00:11:59.409
<v Speaker 1>Um, and then unless something goes wrong
and they do a, you know, a, a lessons

167
00:11:59.409 --> 00:12:05.049
<v Speaker 1>learned or Five Wis or some kind of, uh,
investigation, the data never gets used.

168
00:12:05.130 --> 00:12:11.669
<v Speaker 1>And so, um, and this is, um, becoming more
and more prevalent.

169
00:12:11.719 --> 00:12:15.140
<v Speaker 1>And so, It's, it's not because customers
are doing anything wrong.

170
00:12:15.299 --> 00:12:21.440
<v Speaker 1>They, this is not a, a failing of, of, um,
of the industry.

171
00:12:21.630 --> 00:12:28.559
<v Speaker 1>It, it's, uh, I think it's more of a
failure to, um, to leverage that data

172
00:12:28.820 --> 00:12:29.400
<v Speaker 1>properly.

173
00:12:29.619 --> 00:12:36.099
<v Speaker 1>Um, and Up until um AI, um, it was really

174
00:12:36.099 --> 00:12:38.539
<v Speaker 1>hard to be able to scale that.

175
00:12:38.739 --> 00:12:45.380
<v Speaker 1>So, you can go to many different sites and
you will, uh, you can quickly see if

176
00:12:45.380 --> 00:12:49.880
<v Speaker 1>there is a data science team or there's a
reliability team.

177
00:12:50.380 --> 00:12:52.000
<v Speaker 1>They are usually quite energized.

178
00:12:52.140 --> 00:12:54.380
<v Speaker 1>They are usually, they know their data.

179
00:12:54.729 --> 00:13:01.619
<v Speaker 1>Um, and you will see wins at that site
because they're engaged, they basically, um,

180
00:13:01.780 --> 00:13:07.460
<v Speaker 1>but that's again, um, not scalable and is,
is very ad hoc.

181
00:13:07.859 --> 00:13:14.380
<v Speaker 1>Um, so what you want to do, I take those
pockets of um energy

182
00:13:14.380 --> 00:13:21.039
<v Speaker 1>of and focus and really leverage that
across many sites so that you can

183
00:13:21.039 --> 00:13:27.559
<v Speaker 1>actually gain those benefits, uh, rather
than it just being something that, um, an

184
00:13:27.559 --> 00:13:31.799
<v Speaker 1>engineering team did on one side and
they're looking at scaling it, but they need to

185
00:13:31.799 --> 00:13:32.190
<v Speaker 1>study it.

186
00:13:32.200 --> 00:13:34.919
<v Speaker 1>And so, so, so yeah, this, this.

187
00:13:35.559 --> 00:13:41.780
<v Speaker 1>Data issue is massive and it's getting
bigger, um, and we need to

188
00:13:42.679 --> 00:13:49.580
<v Speaker 1>maybe communicate better to our customers
as to why traditional tools, um,

189
00:13:50.479 --> 00:13:54.239
<v Speaker 1>get stuck and they're good for traditional
condition monitoring.

190
00:13:54.530 --> 00:14:01.219
<v Speaker 1>Um, and what the benefits are of, um,
machine learning, um, and, and

191
00:14:01.219 --> 00:14:02.619
<v Speaker 1>generative AI combined.

192
00:14:02.969 --> 00:14:07.539
<v Speaker 1>It's a, it's kind of a real game-changer
and can break that cycle for your data.

193
00:14:09.349 --> 00:14:13.510
<v Niall Sullivan>And I guess when we, we, we talk about
data as well, so, you know, uh, you know, we

194
00:14:13.510 --> 00:14:17.619
<v Niall Sullivan>Sens as an example, it's not just about
one plant or, or one production line, it's

195
00:14:17.619 --> 00:14:20.030
<v Niall Sullivan>across multiple sites as well.

196
00:14:20.109 --> 00:14:25.229
<v Niall Sullivan>And obviously if you add in multiple
sites, that's more, more data and stacking up.

197
00:14:25.309 --> 00:14:30.900
<v Niall Sullivan>I mean, what, so if we think about the,
the data paralysis issue across the

198
00:14:30.900 --> 00:14:34.500
<v Niall Sullivan>enterprise, how does that, uh, what's your
sort of thoughts on that, Richard?

199
00:14:34.549 --> 00:14:37.349
<v Niall Sullivan>How does that, how does that change what
we're talking about here?

200
00:14:38.669 --> 00:14:45.349
<v Speaker 1>So let's, let's just take for example,
where we've got, um, you know, 5 sites and uh

201
00:14:45.349 --> 00:14:48.380
<v Speaker 1>we've got exactly the same pump across 5
sites.

202
00:14:48.750 --> 00:14:50.809
<v Speaker 1>Those 5 sites don't communicate with each
other.

203
00:14:50.869 --> 00:14:57.750
<v Speaker 1>They are very siloed in traditional and
even across on each site, you might have

204
00:14:57.750 --> 00:14:59.340
<v Speaker 1>3 to 4 shifts.

205
00:14:59.710 --> 00:15:03.789
<v Speaker 1>Um, so even on one site, you've got 3 to 4
shifts.

206
00:15:04.229 --> 00:15:07.400
<v Speaker 1>Uh, where they don't get the full
communication with each other.

207
00:15:07.880 --> 00:15:10.320
<v Speaker 1>So, you get a lot of duplication in
effort.

208
00:15:10.760 --> 00:15:16.559
<v Speaker 1>Um, and what actually happens is, let's
say, um, you know, they've got one piece of

209
00:15:16.559 --> 00:15:16.979
<v Speaker 1>machine.

210
00:15:17.409 --> 00:15:23.090
<v Speaker 1>area that's known to, uh, for the pump to
get blocked, um, if they don't clean the

211
00:15:23.090 --> 00:15:23.409
<v Speaker 1>filter.

212
00:15:23.489 --> 00:15:25.729
<v Speaker 1>Let's just say that is a known issue.

213
00:15:26.010 --> 00:15:26.510
<v Speaker 1>All right.

214
00:15:26.770 --> 00:15:32.070
<v Speaker 1>That, that in isolation will become a
known issue at that one site.

215
00:15:32.369 --> 00:15:32.650
<v Speaker 1>All right.

216
00:15:32.750 --> 00:15:37.549
<v Speaker 1>And um yes, they can go put service
bulletins in place and do something for that,

217
00:15:37.609 --> 00:15:38.609
<v Speaker 1>that one site.

218
00:15:38.950 --> 00:15:42.849
<v Speaker 1>But let's say a brand new site comes with
the same piece of equipment.

219
00:15:43.150 --> 00:15:48.429
<v Speaker 1>For that next site to go through that same
pain is an absolute waste of time, but

220
00:15:48.429 --> 00:15:50.229
<v Speaker 1>happens all the time.

221
00:15:50.549 --> 00:15:56.349
<v Speaker 1>All right, it's because each site needs to
learn their machinery, they need to learn

222
00:15:56.349 --> 00:16:03.309
<v Speaker 1>the uh rosyncrasies that word um of

223
00:16:03.309 --> 00:16:03.849
<v Speaker 1>the machine.

224
00:16:04.530 --> 00:16:11.409
<v Speaker 1>And so what you actually need to do is
you, uh, what Sensi does is it's actually

225
00:16:11.409 --> 00:16:15.359
<v Speaker 1>taking the, what's happening within
existing site.

226
00:16:15.650 --> 00:16:19.979
<v Speaker 1>So when a new site comes on board, it's
taking those learnings across.

227
00:16:20.059 --> 00:16:20.580
<v Speaker 1>With it.

228
00:16:20.900 --> 00:16:26.460
<v Speaker 1>So that if that happens, uh, it
straightaway tells you, listen, we've had 10 cases

229
00:16:26.460 --> 00:16:32.969
<v Speaker 1>like this exactly and it was because of
this filter issue and straightaway, um,

230
00:16:32.979 --> 00:16:35.580
<v Speaker 1>the, the, the benefits are gained.

231
00:16:35.929 --> 00:16:39.250
<v Speaker 1>But this happens, um, all the time.

232
00:16:39.619 --> 00:16:42.599
<v Speaker 1>So, and, and I'm just talking about one
application.

233
00:16:42.739 --> 00:16:47.820
<v Speaker 1>So, you know, on, on a given mindsite or
be it, uh, in any application, you know,

234
00:16:47.900 --> 00:16:54.200
<v Speaker 1>we, we can have, you know, up to 300,
maybe 400 motors, all with their own unique

235
00:16:54.460 --> 00:16:55.020
<v Speaker 1>characters.

236
00:16:55.140 --> 00:17:02.049
<v Speaker 1>And so, um, we need to break that, um,
traditional way of This is a new site.

237
00:17:02.260 --> 00:17:07.660
<v Speaker 1>We will learn, uh, what, what this machine
does and adapt and accord.

238
00:17:07.939 --> 00:17:09.219
<v Speaker 1>We don't need to do that anymore.

239
00:17:09.300 --> 00:17:12.969
<v Speaker 1>We can hit the ground running within
existing data.

240
00:17:13.060 --> 00:17:19.880
<v Speaker 1>So, um, again, how do you break this
paralysis, um, in data is because

241
00:17:20.099 --> 00:17:24.939
<v Speaker 1>what, what every site will do on its own,
they will study it and then they will go

242
00:17:24.939 --> 00:17:29.749
<v Speaker 1>and I get stuck in this paralysis and
analysis, and then I'll go, all right, let's

243
00:17:29.749 --> 00:17:31.068
<v Speaker 1>go throw some more sensors in it.

244
00:17:31.129 --> 00:17:32.529
<v Speaker 1>Let's get some more data.

245
00:17:32.869 --> 00:17:35.668
<v Speaker 1>Uh, we still don't know exactly what the
problem is.

246
00:17:35.909 --> 00:17:41.188
<v Speaker 1>Let's call the OEM and let's, let's maybe
get a contractor in to maybe give us a

247
00:17:41.188 --> 00:17:41.968
<v Speaker 1>third party.

248
00:17:42.788 --> 00:17:49.540
<v Speaker 1>And so you can see how this really
snowballs, um, Into, uh, of no value.

249
00:17:49.819 --> 00:17:54.900
<v Speaker 1>You, you might eventually get on top of
the issue for that site, but where did all

250
00:17:54.900 --> 00:17:56.729
<v Speaker 1>that pain get gained?

251
00:17:57.020 --> 00:18:03.780
<v Speaker 1>And that's what we really want to, um,
lever is uh starting with a

252
00:18:03.780 --> 00:18:07.859
<v Speaker 1>with fresher data and a better way of
communicating with your machinery.

253
00:18:09.430 --> 00:18:14.109
<v Niall Sullivan>Yeah, so, because I know you sort of
shared some, um, sort of bullet points before

254
00:18:14.109 --> 00:18:17.229
<v Niall Sullivan>the court, you know, just to outline, um,
what, what we're gonna talk about, and

255
00:18:17.229 --> 00:18:21.060
<v Niall Sullivan>you, you, you have this phrase, the, the
overthinking trap, and that's exactly what

256
00:18:21.420 --> 00:18:27.420
<v Niall Sullivan>you're, you're describing there, right,
um, this, you know, too much, too much data,

257
00:18:27.550 --> 00:18:32.349
<v Niall Sullivan>you know, trying to find, trying to dig
dig into it and understand every last part

258
00:18:32.349 --> 00:18:34.209
<v Niall Sullivan>of it, but I guess that's.

259
00:18:34.680 --> 00:18:38.920
<v Niall Sullivan>The, you know, the key to it all really
isn't it, it's, it's, it's spending too much

260
00:18:38.920 --> 00:18:41.680
<v Niall Sullivan>time on the data and not putting it into
action.

261
00:18:43.109 --> 00:18:44.050
<v Speaker 1>Yeah, that's right.

262
00:18:44.209 --> 00:18:51.170
<v Speaker 1>Um, you know, we are all very, very busy,
but We are, we, we, we've only got

263
00:18:51.170 --> 00:18:57.089
<v Speaker 1>a certain capacity and this is what um
Sensii brings to the predictive maintenance

264
00:18:57.089 --> 00:18:57.410
<v Speaker 1>phase.

265
00:18:57.780 --> 00:19:04.250
<v Speaker 1>It improves your capacity because you're
not focusing on all of the

266
00:19:04.250 --> 00:19:10.640
<v Speaker 1>different um things that are going on in
your, your plant, you, you now have

267
00:19:10.640 --> 00:19:13.969
<v Speaker 1>something to do that for you and now you
are focusing on the results.

268
00:19:14.319 --> 00:19:20.349
<v Speaker 1>So you, um, you don't have to worry about
trying to analyze everything and trying to

269
00:19:20.349 --> 00:19:21.819
<v Speaker 1>derive things.

270
00:19:22.064 --> 00:19:28.944
<v Speaker 1>You, you know, OK, uh, it, it, it takes a
while for you to convert your trust

271
00:19:28.944 --> 00:19:30.064
<v Speaker 1>over to Sensai.

272
00:19:30.305 --> 00:19:33.984
<v Speaker 1>This is a natural, uh, resistance that
people will have.

273
00:19:34.025 --> 00:19:35.064
<v Speaker 1>I see it every day.

274
00:19:35.785 --> 00:19:37.214
<v Speaker 1>I was exactly the same.

275
00:19:37.584 --> 00:19:43.920
<v Speaker 1>So, um, so when it comes to this, way, a
different way of doing things.

276
00:19:44.260 --> 00:19:50.939
<v Speaker 1>Um, this is what actually causes this
resistance is, what is a program going to tell

277
00:19:50.939 --> 00:19:53.010
<v Speaker 1>me that I don't already know.

278
00:19:53.339 --> 00:19:53.729
<v Speaker 1>All right.

279
00:19:53.859 --> 00:20:00.619
<v Speaker 1>And so only when you actually interact
with uh Sens and you actually see it's,

280
00:20:00.699 --> 00:20:05.834
<v Speaker 1>it's pulling things out that One you
already knew, but also things that you might

281
00:20:05.834 --> 00:20:06.635
<v Speaker 1>not have known.

282
00:20:06.994 --> 00:20:12.824
<v Speaker 1>And so once you have this trust in the
detection and it becomes an intuitive thing,

283
00:20:12.875 --> 00:20:18.704
<v Speaker 1>that's why we call it an attention index
is because what Sensii is all about is

284
00:20:18.704 --> 00:20:24.255
<v Speaker 1>grabbing your attention, uh, and providing
it and focusing it in a certain area.

285
00:20:24.660 --> 00:20:31.380
<v Speaker 1>Um, and so what, what it allows you to do,
uh, is get out of

286
00:20:31.380 --> 00:20:38.140
<v Speaker 1>this paralysis and analysis and focus on,
on results and value, um, and just

287
00:20:38.140 --> 00:20:45.099
<v Speaker 1>let, um, let Sensai run in the background,
um, and basically do a lot

288
00:20:45.099 --> 00:20:50.599
<v Speaker 1>of the things that you were trying to do
ad hoc and, uh, manually before.

289
00:20:52.790 --> 00:20:56.719
<v Niall Sullivan>And, and of course, um, the, you know,
there's, there's a lot to consider on the

290
00:20:56.719 --> 00:21:01.040
<v Niall Sullivan>customer side, but, um, if we sort of flip
it around and think about maybe from our

291
00:21:01.040 --> 00:21:04.920
<v Niall Sullivan>point of view, from a Siemens perspective
or just vendors in general, how can sort

292
00:21:04.920 --> 00:21:10.349
<v Niall Sullivan>of vendors, um, help customers sort of
overcome this sort of overthinking or falling

293
00:21:10.349 --> 00:21:13.280
<v Niall Sullivan>into this trap of like overanalyzing data
themselves.

294
00:21:15.020 --> 00:21:17.180
<v Speaker 1>Yeah, there, there's, there's a couple of
parts to it.

295
00:21:17.260 --> 00:21:24.099
<v Speaker 1>So, um, you know, when, when it comes to
value add, um, you know, I've been a, a

296
00:21:24.099 --> 00:21:28.000
<v Speaker 1>service engineer for a long time, 30
years.

297
00:21:28.339 --> 00:21:34.510
<v Speaker 1>Um, and if a, if a customer, uh, questions
what

298
00:21:35.739 --> 00:21:42.619
<v Speaker 1>value we are providing or uh if there's
any question around the value, I

299
00:21:42.619 --> 00:21:48.260
<v Speaker 1>will purely bring it down to a simple line
that if a customer asks, why should I

300
00:21:48.260 --> 00:21:51.680
<v Speaker 1>engage you or Siemens or a vendor?

301
00:21:52.060 --> 00:21:58.170
<v Speaker 1>And my simple answer to that is because I
want to call you before you call me.

302
00:21:58.420 --> 00:22:02.160
<v Speaker 1>I want to bring something to your
attention before you bring it to me.

303
00:22:02.560 --> 00:22:08.890
<v Speaker 1>If, if that is the relationship, I'm of
value to you, um, and it doesn't matter what

304
00:22:08.890 --> 00:22:09.810
<v Speaker 1>tools I use.

305
00:22:10.130 --> 00:22:10.400
<v Speaker 1>All right.

306
00:22:10.489 --> 00:22:15.530
<v Speaker 1>But uh this is one of the reasons why I'm
involved with Sensai is because it's one

307
00:22:15.530 --> 00:22:21.709
<v Speaker 1>of the strongest tools that we have to be
able to do that because our customers,

308
00:22:21.969 --> 00:22:28.420
<v Speaker 1>um, they, they, they basically Uh, want to
be contacted prior to a

309
00:22:28.420 --> 00:22:28.989
<v Speaker 1>failure.

310
00:22:29.300 --> 00:22:33.859
<v Speaker 1>And the last thing that they want to do is
contact the vendor or contact Siemens,

311
00:22:34.219 --> 00:22:38.780
<v Speaker 1>tell them, listen, something's failed, and
then go on to explain, uh, everything

312
00:22:38.780 --> 00:22:39.099
<v Speaker 1>about it.

313
00:22:39.729 --> 00:22:46.199
<v Speaker 1>That's, um, so what Sensii enables a
vendor to do to their customer

314
00:22:46.420 --> 00:22:48.910
<v Speaker 1>or whatever the relationship is.

315
00:22:49.229 --> 00:22:56.189
<v Speaker 1>It, um, it allows, uh, you to strengthen
your relationship with the customer to say,

316
00:22:56.270 --> 00:22:58.890
<v Speaker 1>listen, let me call you before you call
me.

317
00:22:59.290 --> 00:23:05.650
<v Speaker 1>And, um, as we move into this, everything
as a service, which I absolutely love, you

318
00:23:05.650 --> 00:23:11.369
<v Speaker 1>know, um, where everything's becoming
subscription-based, um, I can really see this

319
00:23:11.369 --> 00:23:12.390
<v Speaker 1>being the future.

320
00:23:12.609 --> 00:23:19.410
<v Speaker 1>If, if, honestly, if, um, if I had a new
plant, or if I had a plant and I didn't

321
00:23:19.410 --> 00:23:24.785
<v Speaker 1>have, a digital transformation team or I
didn't have a digital champion, but I

322
00:23:24.785 --> 00:23:26.295
<v Speaker 1>wanted to transform.

323
00:23:26.635 --> 00:23:30.425
<v Speaker 1>I would go to Siemens and say, listen, I
need this transformation.

324
00:23:30.704 --> 00:23:33.064
<v Speaker 1>I don't have these capabilities in-house.

325
00:23:33.405 --> 00:23:35.305
<v Speaker 1>Can you provide that as a service?

326
00:23:35.545 --> 00:23:37.625
<v Speaker 1>And you know, this is what Siemens does.

327
00:23:37.704 --> 00:23:43.680
<v Speaker 1>So we offer the products that you can, uh,
you know, Empower yourself and, and

328
00:23:43.680 --> 00:23:49.000
<v Speaker 1>Sensai will go along the journey with you
because it is software as a service and we

329
00:23:49.000 --> 00:23:54.319
<v Speaker 1>are constantly engaged with the customer
to make sure that they're getting value.

330
00:23:54.550 --> 00:24:00.285
<v Speaker 1>Um, but the, the biggest thing Uh, when it
comes to this

331
00:24:00.285 --> 00:24:06.555
<v Speaker 1>vendor-customer relationship or what, what
does Sensai bring to the table is this

332
00:24:06.555 --> 00:24:10.114
<v Speaker 1>ability to speak to a customer before they
speak to you.

333
00:24:10.314 --> 00:24:16.155
<v Speaker 1>Because if you have that relationship, um,
it, it's, it's a win-win.

334
00:24:16.474 --> 00:24:22.265
<v Speaker 1>They are paying for value, you're
providing value and, um, and Sensai is the tool to

335
00:24:22.265 --> 00:24:22.915
<v Speaker 1>achieve that.

336
00:24:24.550 --> 00:24:31.010
<v Niall Sullivan>Yeah, slightly biased, but I 100% agree,
of course, but, um, but no, absolutely,

337
00:24:31.310 --> 00:24:31.770
<v Niall Sullivan>absolutely.

338
00:24:32.189 --> 00:24:36.349
<v Niall Sullivan>So, um, I, I think, you know, we've got a
couple of, got a couple of questions left.

339
00:24:36.430 --> 00:24:41.219
<v Niall Sullivan>One which is sort of our usual when we tie
things together and give, um, our

340
00:24:41.219 --> 00:24:45.790
<v Niall Sullivan>listeners some, some takeaways to sort of
leave with, but before, before we do that,

341
00:24:45.829 --> 00:24:48.739
<v Niall Sullivan>I just wanted to touch on sort of adoption
of tech cos.

342
00:24:49.449 --> 00:24:52.949
<v Niall Sullivan>We know customers have a lot of data and,
you know, we've talked about sort of

343
00:24:52.949 --> 00:24:57.420
<v Niall Sullivan>overthinking and overanalyzing and what do
we do with it and stuff, but, um, we've,

344
00:24:57.500 --> 00:25:02.569
<v Niall Sullivan>you know, we know AIgen AI is a big, huge
topic and if you're not aware of it, you

345
00:25:02.569 --> 00:25:04.459
<v Niall Sullivan>must be living under a rock somewhere, I
guess.

346
00:25:04.540 --> 00:25:08.979
<v Niall Sullivan>So is there a reason why there's a, I
don't know if there is a reluctance, you know,

347
00:25:09.219 --> 00:25:11.930
<v Niall Sullivan>is there a reluctance to adopt this new
technology?

348
00:25:11.969 --> 00:25:13.579
<v Niall Sullivan>Is there some reticence there?

349
00:25:13.780 --> 00:25:16.180
<v Niall Sullivan>And if there is, you know, what, why might
that be?

350
00:25:16.510 --> 00:25:19.920
<v Niall Sullivan>And obviously it's a very broad statement
because not everyone's, there's a lot of

351
00:25:19.920 --> 00:25:24.109
<v Niall Sullivan>people doing great things with AI tools,
but where there is a reluctance, can you

352
00:25:24.109 --> 00:25:27.739
<v Niall Sullivan>put your finger on why that might be,
knowing they've got all this data that can be,

353
00:25:28.189 --> 00:25:30.680
<v Niall Sullivan>that AI can really get, draw the value
from.

354
00:25:31.709 --> 00:25:35.160
<v Speaker 1>Yeah, it's, it's amazing actually how fast
things change.

355
00:25:35.239 --> 00:25:38.939
<v Speaker 1>I remember one of our first podcasts was
around adoption.

356
00:25:39.280 --> 00:25:44.959
<v Speaker 1>And that conversation will be completely
different to how I feel today because I

357
00:25:44.959 --> 00:25:51.380
<v Speaker 1>don't feel there's a reluctance, uh,
anymore around adoption of

358
00:25:51.709 --> 00:25:58.609
<v Speaker 1>Um, I, I now think it's more a reluctance
of who to choose to go with.

359
00:25:58.989 --> 00:26:05.469
<v Speaker 1>So I think the, the value is there, uh,
and, and I think that's well

360
00:26:05.469 --> 00:26:06.150
<v Speaker 1>articulated.

361
00:26:06.229 --> 00:26:12.750
<v Speaker 1>Everybody now can see, jeez, this is a, a
real game-changer and it's, it's, uh, I

362
00:26:12.750 --> 00:26:13.469
<v Speaker 1>want to change.

363
00:26:13.550 --> 00:26:14.430
<v Speaker 1>I want to adopt.

364
00:26:14.510 --> 00:26:15.869
<v Speaker 1>I want these benefits.

365
00:26:16.469 --> 00:26:21.630
<v Speaker 1>But the reluctance now is who do I go with
and why do I go with them.

366
00:26:22.020 --> 00:26:26.030
<v Speaker 1>Um, and so, again, this is part of that
paralysis and analysis.

367
00:26:26.500 --> 00:26:27.609
<v Speaker 1>You've now made a decision.

368
00:26:27.989 --> 00:26:31.489
<v Speaker 1>I want to eat better or I want better
maintenance.

369
00:26:31.670 --> 00:26:32.099
<v Speaker 1>OK.

370
00:26:32.270 --> 00:26:34.670
<v Speaker 1>But now you've got to choose an action.

371
00:26:35.030 --> 00:26:40.109
<v Speaker 1>So, um, I feel this is, uh, how you break
the cycle.

372
00:26:40.219 --> 00:26:47.189
<v Speaker 1>So, firstly, um, if anybody is listening
to this, um, what I would suggest you

373
00:26:47.189 --> 00:26:52.724
<v Speaker 1>do is this, There's a couple of key things
that you, that you want to know when

374
00:26:53.064 --> 00:26:54.545
<v Speaker 1>adopting any technology.

375
00:26:54.704 --> 00:27:00.244
<v Speaker 1>So, um, but, but firstly, do your homework
on, um, on your top three.

376
00:27:00.755 --> 00:27:05.344
<v Speaker 1>Choose your, whatever your application is,
but go do your homework on the top 3 and

377
00:27:05.344 --> 00:27:12.175
<v Speaker 1>base that on, um, experience, base that
on, on, um,

378
00:27:12.385 --> 00:27:14.545
<v Speaker 1>use cases demonstrated.

379
00:27:15.010 --> 00:27:20.699
<v Speaker 1>Because the only thing that's gonna break
the cycle for you is if you visually see

380
00:27:21.000 --> 00:27:25.839
<v Speaker 1>something, um, that was done in the past,
that is being done now that you need.

381
00:27:26.160 --> 00:27:26.479
<v Speaker 1>All right.

382
00:27:26.560 --> 00:27:33.359
<v Speaker 1>And so, whoever you choose, make sure that
they can demonstrate, um, that this has

383
00:27:33.359 --> 00:27:33.939
<v Speaker 1>been done.

384
00:27:34.449 --> 00:27:41.380
<v Speaker 1>Um, and, um, and basically, and, and once
we did it, be able to have a, a

385
00:27:41.380 --> 00:27:46.170
<v Speaker 1>fifteen-minute conversation as to how you
achieve that without getting lost.

386
00:27:46.500 --> 00:27:51.290
<v Speaker 1>That's the important component, uh, to
adopting new technologies.

387
00:27:51.339 --> 00:27:53.420
<v Speaker 1>You know what you need to do, OK.

388
00:27:53.540 --> 00:27:59.849
<v Speaker 1>You talk about how it's done, you usually
know the why, um, but Choose a,

389
00:28:00.260 --> 00:28:05.729
<v Speaker 1>choose somebody that is able to
demonstrate, uh, use cases, uh, is able to

390
00:28:05.729 --> 00:28:11.010
<v Speaker 1>articulate to you quite clearly without
trying to pull the wool over your eyes as to

391
00:28:11.010 --> 00:28:12.349
<v Speaker 1>how it achieves that.

392
00:28:12.849 --> 00:28:19.640
<v Speaker 1>And, um, and then, um, do a bit of a deep
dive into, um, their

393
00:28:19.640 --> 00:28:21.890
<v Speaker 1>experience in this deployment.

394
00:28:22.420 --> 00:28:28.939
<v Speaker 1>So, um, what you, when you, whenever you
are adopting a new technology or you're

395
00:28:28.939 --> 00:28:32.699
<v Speaker 1>changing the way you do, doing something,
you need a roadmap.

396
00:28:33.170 --> 00:28:38.420
<v Speaker 1>So ask that company, whoever and whatever
technology you're going with, what is your

397
00:28:38.420 --> 00:28:39.020
<v Speaker 1>roadmap?

398
00:28:39.300 --> 00:28:43.689
<v Speaker 1>What have you previously identified as
issues?

399
00:28:43.859 --> 00:28:45.319
<v Speaker 1>What are your Lessons learned.

400
00:28:45.680 --> 00:28:52.400
<v Speaker 1>Why should I go with you, um, to make sure
that I, I, I'm not at the bleeding edge

401
00:28:52.400 --> 00:28:53.260
<v Speaker 1>of technology.

402
00:28:53.640 --> 00:28:54.030
<v Speaker 1>All right.

403
00:28:54.119 --> 00:28:59.839
<v Speaker 1>I want somebody to show me that, uh, you
have a clear plan.

404
00:29:00.160 --> 00:29:06.329
<v Speaker 1>This is the lessons that you've learned
and, uh, and also possibly challenge you on

405
00:29:06.500 --> 00:29:08.219
<v Speaker 1>Your, uh, intention.

406
00:29:08.300 --> 00:29:14.520
<v Speaker 1>You know, I could, I could own a factory
and I say, listen, I want to reduce my, um,

407
00:29:15.060 --> 00:29:17.280
<v Speaker 1>my downtime by 50%.

408
00:29:17.619 --> 00:29:23.339
<v Speaker 1>And, you know, I want it by next week, and
I've got a budget of $10,000.

409
00:29:24.010 --> 00:29:29.300
<v Speaker 1>And, and so you need some, uh, somebody to
challenge you and say, look, That's not

410
00:29:29.300 --> 00:29:33.579
<v Speaker 1>gonna happen because of things like
cultural adoption.

411
00:29:33.900 --> 00:29:40.339
<v Speaker 1>You know, we, we, we understand that your
maintenance team are used to fixing broken

412
00:29:40.339 --> 00:29:42.219
<v Speaker 1>things and being reactive.

413
00:29:42.300 --> 00:29:43.180
<v Speaker 1>That's their mindset.

414
00:29:43.260 --> 00:29:46.949
<v Speaker 1>That's how they have worked up until now.

415
00:29:47.229 --> 00:29:51.790
<v Speaker 1>And so to change the way that people do
things takes a little bit of time.

416
00:29:52.150 --> 00:29:57.189
<v Speaker 1>So, that's maybe what I would just suggest
is, um, when we talk about this

417
00:29:57.189 --> 00:30:01.209
<v Speaker 1>reluctance, I don't think there's any more
reluctance on adopting technology.

418
00:30:01.359 --> 00:30:03.310
<v Speaker 1>It's choosing who to go with.

419
00:30:03.670 --> 00:30:09.770
<v Speaker 1>Um, and look, I see this all the time too,
is a customer will ask you,

420
00:30:10.550 --> 00:30:13.569
<v Speaker 1>well, um, why should I go with you and not
with them?

421
00:30:14.040 --> 00:30:20.760
<v Speaker 1>And you should also be able to, uh,
articulate that, OK, because every

422
00:30:20.760 --> 00:30:23.619
<v Speaker 1>customer is different and every solution
is different.

423
00:30:24.000 --> 00:30:30.760
<v Speaker 1>Um, and, um, there are, you know, There's
no one product that fits

424
00:30:30.760 --> 00:30:31.609
<v Speaker 1>every customer.

425
00:30:32.010 --> 00:30:37.000
<v Speaker 1>Um, but what you want to do is choose
something that you can start small on,

426
00:30:37.369 --> 00:30:40.510
<v Speaker 1>demonstrate wins on very, very quickly.

427
00:30:40.900 --> 00:30:47.310
<v Speaker 1>Um, so that you, because the winds are
what breed, uh, success and drive the next

428
00:30:47.310 --> 00:30:54.050
<v Speaker 1>thing, and you can scale up and it's not
restricted by things like connectivity,

429
00:30:54.310 --> 00:30:56.939
<v Speaker 1>um, and, and OEM restrictions.

430
00:30:57.310 --> 00:31:03.239
<v Speaker 1>So, a couple of things there around the
reluctance, but I think, um, just

431
00:31:03.989 --> 00:31:10.189
<v Speaker 1>Uh, choosing who to start with, um, is, is
what we need to do better at, at this

432
00:31:10.189 --> 00:31:10.339
<v Speaker 1>stage.

433
00:31:10.390 --> 00:31:16.829
<v Speaker 1>And I think Sensai and now this kind of
platform, um, is brilliant because customers

434
00:31:16.829 --> 00:31:19.410
<v Speaker 1>want these bite-size information.

435
00:31:19.670 --> 00:31:23.719
<v Speaker 1>Um, they, they don't want the PowerPoint
presentations, and they don't want, they,

436
00:31:23.829 --> 00:31:27.489
<v Speaker 1>they literally want to, uh, see how it's
done.

437
00:31:27.739 --> 00:31:34.500
<v Speaker 1>Um, because they know their why, um, and,
and yeah, just getting that started and

438
00:31:34.500 --> 00:31:36.020
<v Speaker 1>articulated is the important part.

439
00:31:37.329 --> 00:31:41.439
<v Niall Sullivan>Oh excellent, and I think, I think you've,
you, you've probably summarized, um,

440
00:31:41.449 --> 00:31:45.329
<v Niall Sullivan>really well, well you have sorry,
summarized really well and sort of close out the

441
00:31:45.329 --> 00:31:49.890
<v Niall Sullivan>episode, but maybe if we, if we circle
back quickly to the, you know, to the

442
00:31:49.890 --> 00:31:51.410
<v Niall Sullivan>original topic which is around.

443
00:31:52.119 --> 00:31:56.680
<v Niall Sullivan>You know, too much data, so what would you
say are three punchy takeaways for people

444
00:31:56.680 --> 00:32:02.400
<v Niall Sullivan>to, to think about when it comes to the
topic of, of data and taking action with it?

445
00:32:03.859 --> 00:32:05.959
<v Speaker 1>Yes, um, look, ask for help.

446
00:32:06.140 --> 00:32:11.540
<v Speaker 1>Um, as I said, people get stuck in their
own world, companies get stuck in their own

447
00:32:11.540 --> 00:32:12.000
<v Speaker 1>world.

448
00:32:13.130 --> 00:32:18.569
<v Speaker 1>Sometimes it's better to just ask for
help, let somebody else come in and look at it

449
00:32:18.569 --> 00:32:20.030
<v Speaker 1>from a bird's-eye point of view.

450
00:32:20.329 --> 00:32:27.109
<v Speaker 1>Um, and, you know, with Sensai, um, we,
we, we do this all the time where we come in

451
00:32:27.280 --> 00:32:32.520
<v Speaker 1>and we give you a bird's-eye point of
view, where we talk about, um, uh, and

452
00:32:32.520 --> 00:32:33.709
<v Speaker 1>understand what your problems are.

453
00:32:33.849 --> 00:32:37.930
<v Speaker 1>But most importantly, we Give you a return
on investment time.

454
00:32:38.109 --> 00:32:43.670
<v Speaker 1>And then that's uh the first little job
that you can get to get to break the cycle.

455
00:32:43.989 --> 00:32:46.729
<v Speaker 1>So the first thing is ask for help.

456
00:32:47.109 --> 00:32:53.800
<v Speaker 1>Um, and then the second thing is um Unders
um and

457
00:32:53.800 --> 00:32:57.869
<v Speaker 1>make sure that It, it depending on which
level you are at.

458
00:32:57.949 --> 00:33:02.819
<v Speaker 1>So, we've, we've got CEOs, we've got, you
know, shift supervisors.

459
00:33:02.949 --> 00:33:07.430
<v Speaker 1>Everybody's got a, a, a different level
and a different perspective.

460
00:33:07.750 --> 00:33:14.199
<v Speaker 1>Um, and it's very important that, um, that
you, Engage your team

461
00:33:15.119 --> 00:33:18.819
<v Speaker 1>um at the different layers to, to make the
change that you see.

462
00:33:19.140 --> 00:33:19.339
<v Speaker 1>All right.

463
00:33:19.439 --> 00:33:25.989
<v Speaker 1>I know that this can be hard because
usually when it comes to Sensai, uh, the shop

464
00:33:25.989 --> 00:33:30.819
<v Speaker 1>floor and the operators and the
reliability engineers, they clearly see the value.

465
00:33:31.089 --> 00:33:34.219
<v Speaker 1>Um, they can quickly say, yeah, let's go
ahead with this.

466
00:33:34.719 --> 00:33:37.650
<v Speaker 1>But they aren't the decision-makers, they
aren't the budget makers.

467
00:33:37.920 --> 00:33:44.459
<v Speaker 1>And they, um, so, um, it's, it's very
important that, um, that you

468
00:33:44.719 --> 00:33:50.489
<v Speaker 1>go internal, go speak to your manager and
say, listen, we want to do this better.

469
00:33:50.839 --> 00:33:51.260
<v Speaker 1>All right.

470
00:33:51.560 --> 00:33:58.089
<v Speaker 1>Because, uh, the higher the engagement
with In your organization, the, the more, the

471
00:33:58.089 --> 00:33:59.589
<v Speaker 1>better results that you're going to get.

472
00:33:59.729 --> 00:34:03.750
<v Speaker 1>So, and Siemens are there to also help you
with that.

473
00:34:04.050 --> 00:34:08.919
<v Speaker 1>Um, and we can kind of articulate those
benefits at the different levels.

474
00:34:08.969 --> 00:34:10.750
<v Speaker 1>That's kind of what, what, what we do.

475
00:34:10.850 --> 00:34:15.399
<v Speaker 1>So, ask for help, um, but go internally
within your organization.

476
00:34:16.120 --> 00:34:22.129
<v Speaker 1>Um, and, and see what you can actually do
there, get the internal buy-in.

477
00:34:22.669 --> 00:34:28.729
<v Speaker 1>No, here in Australia, this is a culture
that's very much encouraged in all

478
00:34:29.580 --> 00:34:32.320
<v Speaker 1>organizations is, is process improvement.

479
00:34:32.664 --> 00:34:33.214
<v Speaker 1>Improvement.

480
00:34:33.513 --> 00:34:36.954
<v Speaker 1>Um, and there's lots of, uh, rewards
around this.

481
00:34:37.073 --> 00:34:41.313
<v Speaker 1>So, um, this, this is something that you
should be encouraged.

482
00:34:41.354 --> 00:34:43.474
<v Speaker 1>Go speak to your manager, go speak to your
supervisor.

483
00:34:43.753 --> 00:34:49.510
<v Speaker 1>We want to do something different, um,
because, you know, um, and, and so, That

484
00:34:49.510 --> 00:34:50.189
<v Speaker 1>internal change.

485
00:34:50.229 --> 00:34:55.530
<v Speaker 1>And then maybe, I know this is not punchy,
but, uh, ask for help, derive it inside.

486
00:34:55.870 --> 00:35:02.590
<v Speaker 1>And then maybe the, the third thing that
I, I, I would just, um, say is start small.

487
00:35:02.669 --> 00:35:06.790
<v Speaker 1>Don't try and tackle, um, the entire
plant.

488
00:35:07.179 --> 00:35:08.300
<v Speaker 1>Start with one line.

489
00:35:08.610 --> 00:35:14.270
<v Speaker 1>Start with a known problem and, um, and
And start small.

490
00:35:14.489 --> 00:35:20.969
<v Speaker 1>And as soon as you do that, um, you,
you're actually scaling up is, um, very, very

491
00:35:20.969 --> 00:35:23.439
<v Speaker 1>easy within, within Sensi.

492
00:35:23.479 --> 00:35:29.250
<v Speaker 1>So, those are my three kind of takeaways
there is ask for support, reach out to

493
00:35:29.250 --> 00:35:35.070
<v Speaker 1>OEMs, compare them, make sure, um, they
can articulate the benefits to you.

494
00:35:35.909 --> 00:35:38.709
<v Speaker 1>Drive, try and do something internal
before reaching out.

495
00:35:39.040 --> 00:35:45.870
<v Speaker 1>Um, and then also, uh, go and see, um,
what, what, what, what, what else we, we can

496
00:35:45.870 --> 00:35:46.270
<v Speaker 1>do there.

497
00:35:46.389 --> 00:35:46.610
<v Speaker 1>Yeah.

498
00:35:47.969 --> 00:35:51.370
<v Niall Sullivan>Excellent, really great takeaways as well,
and it is difficult to be punched with

499
00:35:51.370 --> 00:35:54.399
<v Niall Sullivan>such a, you know, there's a, you know, a
lot to talk about with this topic, isn't

500
00:35:54.399 --> 00:35:57.729
<v Niall Sullivan>it, so maybe I was a bit unfair with that,
that request, but no, really great,

501
00:35:57.889 --> 00:35:59.409
<v Niall Sullivan>really great summary there, Richard.

502
00:36:00.040 --> 00:36:02.510
<v Niall Sullivan>Um, but yeah, for today, um, we've covered
everything.

503
00:36:02.610 --> 00:36:04.600
<v Niall Sullivan>I think it was a really good episode once
again.

504
00:36:04.699 --> 00:36:04.889
<v Niall Sullivan>Thank

505
00:36:04.889 --> 00:36:05.310
<v Speaker 1>you

506
00:36:05.729 --> 00:36:07.830
<v Niall Sullivan>for returning, Richard, and sharing your
insights once again.

507
00:36:08.080 --> 00:36:08.889
<v Niall Sullivan>It's great to have you on.

508
00:36:10.100 --> 00:36:14.500
<v Speaker 1>Uh, thank you very much, Noel, and, um,
yeah, looking forward to, uh, a lot of your

509
00:36:14.500 --> 00:36:14.780
<v Speaker 1>others.

510
00:36:14.820 --> 00:36:18.860
<v Speaker 1>I've been keeping a close eye on them and,
um, I heard you actually recently caught

511
00:36:18.860 --> 00:36:21.879
<v Speaker 1>up with, uh, Keith Ritchie here in
Australia.

512
00:36:22.139 --> 00:36:27.500
<v Speaker 1>Uh, we've got a big, big initiative
around, um, beyond 1%, which is very much a

513
00:36:27.500 --> 00:36:28.620
<v Speaker 1>sustainability.

514
00:36:28.860 --> 00:36:30.399
<v Speaker 1>I think you recently caught up with him.

515
00:36:31.340 --> 00:36:32.189
<v Niall Sullivan>Yeah, we did.

516
00:36:32.350 --> 00:36:34.070
<v Niall Sullivan>Yeah, literally yesterday as well.

517
00:36:34.189 --> 00:36:38.629
<v Niall Sullivan>So, um, so that, that episode will be
coming soon and a really fascinating sort of

518
00:36:38.629 --> 00:36:42.580
<v Niall Sullivan>insight and lots of, of great, great work
with that initiative, but I won't, I won't

519
00:36:42.580 --> 00:36:45.560
<v Niall Sullivan>spoil the episode too much, but yeah, it
was really interesting talking to Keith,

520
00:36:45.709 --> 00:36:46.030
<v Niall Sullivan>um.

521
00:36:46.739 --> 00:36:52.020
<v Niall Sullivan>From my side, but um, but yeah, but for
today, um, thank you again Richard and thank

522
00:36:52.020 --> 00:36:57.060
<v Niall Sullivan>you everyone um for joining um and
listening and we'll see you on the next episode.

523
00:36:57.300 --> 00:36:58.199
<v Niall Sullivan>Thank you very much.

524
00:37:01.429 --> 00:37:06.389
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

525
00:37:06.389 --> 00:37:09.909
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.
