WEBVTT
Language: en-US

1
00:00:01.820 --> 00:00:06.480
<v Richard Ella>Look, when it comes to on-prem or cloud,
this is not black or white.

2
00:00:07.099 --> 00:00:07.409
<v Richard Ella>All right.

3
00:00:07.489 --> 00:00:11.050
<v Richard Ella>If, if, if, if you had to ask me what's
the best, it's actually the gray.

4
00:00:11.539 --> 00:00:18.110
<v Richard Ella>Because uh when you combine the power of
on-prem and it's um value

5
00:00:18.110 --> 00:00:22.799
<v Richard Ella>add and cloud, you end up with this really
powerful solution.

6
00:00:25.040 --> 00:00:30.209
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens, and now your host, Nel

7
00:00:30.209 --> 00:00:30.819
<v Speaker 2>Sullivan.

8
00:00:34.540 --> 00:00:39.209
<v Niall Sullivan>Hello and welcome to the latest episode of
the Trend detection podcast.

9
00:00:39.709 --> 00:00:44.669
<v Niall Sullivan>Um, today I'm joined by a very familiar
face and voice, um, Richard Ella, um, my

10
00:00:44.669 --> 00:00:46.009
<v Niall Sullivan>colleague all the way in Australia.

11
00:00:46.310 --> 00:00:47.110
<v Niall Sullivan>How are you, Richard?

12
00:00:48.709 --> 00:00:51.029
<v Richard Ella>Yeah, good day, Nia, uh, from Down Hunter.

13
00:00:51.150 --> 00:00:52.750
<v Richard Ella>Um, yeah, pretty good, pretty good.

14
00:00:53.110 --> 00:00:56.029
<v Richard Ella>Looks like you've, um, done some damage
here.

15
00:00:56.069 --> 00:00:56.810
<v Richard Ella>What's going on?

16
00:00:57.549 --> 00:01:02.470
<v Niall Sullivan>Yeah, yeah, yeah, that, well, people won't
be able to see this, but I have, um, hurt

17
00:01:02.470 --> 00:01:06.230
<v Niall Sullivan>my, well, no, I've had an operation on my
wrist, so, um, I'm doing podcasting

18
00:01:06.230 --> 00:01:09.150
<v Niall Sullivan>one-handed, which is easy as it happens to
do.

19
00:01:09.279 --> 00:01:12.870
<v Niall Sullivan>So not going to affect my presenting
hopefully today, um.

20
00:01:13.150 --> 00:01:17.750
<v Niall Sullivan>And, uh, and actually, well, today, um,
today's subjects, um, it's a slightly

21
00:01:17.750 --> 00:01:21.959
<v Niall Sullivan>different one because, uh, with, um,
Sensii and predictive maintenance, we're often

22
00:01:21.959 --> 00:01:26.319
<v Niall Sullivan>talking about cloud and the benefits of
clouds, and cloud's great and, and cloud's

23
00:01:26.319 --> 00:01:27.919
<v Niall Sullivan>the be all and end all, but actually, it's
not.

24
00:01:28.080 --> 00:01:31.910
<v Niall Sullivan>And we're gonna go into that today and
talk a little bit about on-premise and how it

25
00:01:31.910 --> 00:01:33.260
<v Niall Sullivan>doesn't have to be one or the other.

26
00:01:33.559 --> 00:01:37.120
<v Niall Sullivan>One can certainly benefit the other, and
you can use both in tandem to get the

27
00:01:37.120 --> 00:01:40.440
<v Niall Sullivan>results that you want at scale, to
unlocking the value at scale.

28
00:01:40.940 --> 00:01:44.180
<v Niall Sullivan>Um, so have I summarized that OK, Richard,
from your point of view, because I know

29
00:01:44.180 --> 00:01:45.870
<v Niall Sullivan>you sort of brought the topic to the
table.

30
00:01:45.980 --> 00:01:49.440
<v Niall Sullivan>So, you know, was there anything else in
there you wanted to add to that?

31
00:01:50.900 --> 00:01:54.379
<v Richard Ella>No, no, I think, I think you really hit
the nail on the head there.

32
00:01:54.500 --> 00:02:00.680
<v Richard Ella>Um, you know, when it comes to deployment
and when we talk about generating value,

33
00:02:00.980 --> 00:02:06.339
<v Richard Ella>um, it's, and, and we start talking about
introducing new products.

34
00:02:06.690 --> 00:02:12.259
<v Richard Ella>Customers, especially in the industrial
space, will always question, why should I do

35
00:02:12.259 --> 00:02:13.110
<v Richard Ella>something different?

36
00:02:13.300 --> 00:02:18.580
<v Richard Ella>Why should I Uh, move my data, um, into a
cloud platform.

37
00:02:19.020 --> 00:02:25.419
<v Richard Ella>Why can't I just leverage the large amount
of money, uh, I, I've spent on my plant

38
00:02:25.419 --> 00:02:27.960
<v Richard Ella>that's got very high speed processes in.

39
00:02:28.179 --> 00:02:29.259
<v Richard Ella>I've got my historians.

40
00:02:29.300 --> 00:02:31.919
<v Richard Ella>I've got my condition monitoring here.

41
00:02:32.539 --> 00:02:39.220
<v Richard Ella>What's the real value of, uh, pushing my
data out, um, and, and getting it analyzed

42
00:02:39.220 --> 00:02:41.809
<v Richard Ella>and reviewed in a different way.

43
00:02:41.820 --> 00:02:42.509
<v Richard Ella>And so.

44
00:02:42.880 --> 00:02:49.600
<v Richard Ella>Um, what I've seen, uh, I've been in
automation, um, now for

45
00:02:49.600 --> 00:02:56.100
<v Richard Ella>over 20 years, and I come from a coalface
PLC drive, uh, background,

46
00:02:56.429 --> 00:03:03.309
<v Richard Ella>and it is in, it is in your DNA to
challenge, uh, uh,

47
00:03:03.320 --> 00:03:08.399
<v Richard Ella>why we should do things differently when
these people that have been coding for a

48
00:03:08.399 --> 00:03:09.339
<v Richard Ella>long time.

49
00:03:09.809 --> 00:03:16.770
<v Richard Ella>Have, have spent a lot of uh amount of
energy, um, in, in design and

50
00:03:16.770 --> 00:03:22.850
<v Richard Ella>deployment and making and making sure that
they come up with a program that really

51
00:03:22.850 --> 00:03:24.919
<v Richard Ella>looks after the application.

52
00:03:25.320 --> 00:03:31.009
<v Richard Ella>And so, so now when we come along and say,
listen, we can see things that you

53
00:03:31.009 --> 00:03:34.990
<v Richard Ella>couldn't see before and that kind of
sometimes gets people on the back foot.

54
00:03:35.600 --> 00:03:39.880
<v Richard Ella>Because they were like, well, you know, I
know machine, machine very, very well.

55
00:03:40.360 --> 00:03:44.809
<v Richard Ella>What are you gonna do that's different to
what we do here on prem?

56
00:03:44.820 --> 00:03:50.960
<v Richard Ella>And so, that's the topic for today is, um,
what do we do on prem?

57
00:03:51.250 --> 00:03:58.119
<v Richard Ella>What do we do in cloud, and really what is
the best solution moving forward, uh, to

58
00:03:58.119 --> 00:04:00.160
<v Richard Ella>make sure that you're getting the most
value.

59
00:04:00.440 --> 00:04:02.839
<v Richard Ella>Now, that's essentially the topic today.

60
00:04:03.229 --> 00:04:08.750
<v Richard Ella>Um, I don't want to give my insights until
the, the very end as to what I feel is

61
00:04:08.750 --> 00:04:09.490
<v Richard Ella>the best.

62
00:04:09.789 --> 00:04:14.589
<v Richard Ella>Um, I'd love to just kind of go through
this journey of customers that I've spoken

63
00:04:14.589 --> 00:04:20.910
<v Richard Ella>to, challenges that we've faced, and talk
about when, um, it was better to stay

64
00:04:20.910 --> 00:04:27.329
<v Richard Ella>on-prem and when it was, uh, best to only
go cloud or when there was a combination.

65
00:04:29.399 --> 00:04:32.970
<v Niall Sullivan>Yeah, so let's start with that then and
break and break this down a little bit.

66
00:04:33.130 --> 00:04:37.440
<v Niall Sullivan>You know, so if we start with on-premise
analytics, so, um, in the context of sort

67
00:04:37.440 --> 00:04:41.809
<v Niall Sullivan>of industrial um operations, you know,
what, what are the benefits of, you know,

68
00:04:41.890 --> 00:04:43.489
<v Niall Sullivan>on-premise analytics?

69
00:04:45.309 --> 00:04:50.420
<v Richard Ella>Yeah, so, um, essentially, this is why
factories get built.

70
00:04:50.720 --> 00:04:56.200
<v Richard Ella>All right, um, they are meeting the needs
of, um, whatever they in the food and beer

71
00:04:56.200 --> 00:05:03.190
<v Richard Ella>battery, pharmaceuticals, whatever, um,
vertical they're in, um, there are

72
00:05:03.190 --> 00:05:09.510
<v Richard Ella>products and PLCs and, and OEM equipment
specifically designed to do a function and

73
00:05:09.510 --> 00:05:11.929
<v Richard Ella>make the widgets that the customers need.

74
00:05:12.350 --> 00:05:19.320
<v Richard Ella>And, um, and automation has been
absolutely awesome, um, over the

75
00:05:19.320 --> 00:05:26.279
<v Richard Ella>last 20 years in, in how, how much easier
it has been to visualize

76
00:05:26.279 --> 00:05:32.619
<v Richard Ella>data as opposed to just having blinking
LEDs on a template or how, how much

77
00:05:33.359 --> 00:05:36.329
<v Richard Ella>easier it has been to actually automate.

78
00:05:36.809 --> 00:05:43.769
<v Richard Ella>Uh, code and you didn't have to write code
in C++ or CS SEL and,

79
00:05:44.010 --> 00:05:50.470
<v Richard Ella>um, it's really become easier at an
application level to, um,

80
00:05:50.700 --> 00:05:56.309
<v Richard Ella>basically derive process and, uh,
rules-based condition monitoring and so.

81
00:05:56.829 --> 00:06:02.309
<v Richard Ella>This is um what all of our um customers
are doing.

82
00:06:02.510 --> 00:06:03.549
<v Richard Ella>That's their focus.

83
00:06:03.859 --> 00:06:08.059
<v Richard Ella>Their focus is not to bring their data
into cloud to do something else.

84
00:06:08.350 --> 00:06:14.670
<v Richard Ella>Their focus is to manufacture widgets and,
um, and so this is what we talk about is

85
00:06:14.670 --> 00:06:21.390
<v Richard Ella>the evolution um of um Industry 4.0 and
especially in the condition monitoring

86
00:06:21.390 --> 00:06:21.609
<v Richard Ella>space.

87
00:06:22.250 --> 00:06:28.290
<v Richard Ella>So when we talk about on-prem, we are
really talking about the physical assets that

88
00:06:28.290 --> 00:06:35.290
<v Richard Ella>are on site, be it your motor, be it your,
um, you know, your, um,

89
00:06:36.459 --> 00:06:43.399
<v Richard Ella>Desal, be it your, um, uh, water cleaning
or whatever your application is, um,

90
00:06:43.859 --> 00:06:49.940
<v Richard Ella>that is actually where all of the, the,
the logic sits and that's, so now we have to

91
00:06:49.940 --> 00:06:51.359
<v Richard Ella>come and,

92
00:06:52.100 --> 00:06:57.899
<v Richard Ella>and talk about, you know, what can we
bring to the table that you're not doing on

93
00:06:57.899 --> 00:06:58.220
<v Richard Ella>prem.

94
00:06:58.700 --> 00:06:59.730
<v Richard Ella>And it's important.

95
00:07:00.309 --> 00:07:02.149
<v Richard Ella>So, what do we do on-prem?

96
00:07:02.630 --> 00:07:07.309
<v Richard Ella>Traditionally, you know, everything that's
rules-based condition monitoring, uh, if

97
00:07:07.309 --> 00:07:13.059
<v Richard Ella>this, when that, those, um, is
traditional, uh, edge processing.

98
00:07:13.390 --> 00:07:18.450
<v Richard Ella>We have seen the evolution of model-based
AI where they've taken.

99
00:07:18.850 --> 00:07:25.489
<v Richard Ella>Um, and OEM might know their machines so
well that they go and write model-based

100
00:07:25.489 --> 00:07:30.910
<v Richard Ella>AI that runs on-prem and is, uh, operating
at a high spectrum.

101
00:07:31.260 --> 00:07:37.829
<v Richard Ella>OK, so this is looking for, uh, anomalies
or deviations at a millisecond time slots,

102
00:07:37.859 --> 00:07:41.679
<v Richard Ella>very useful for, uh, monitoring grid.

103
00:07:41.950 --> 00:07:46.750
<v Richard Ella>You're looking at frequency or transience
in the grid, very handy if you're looking

104
00:07:46.750 --> 00:07:53.670
<v Richard Ella>for voltage deviations on drives or um
there is definitely use cases for

105
00:07:53.670 --> 00:08:00.630
<v Richard Ella>that high speed um AI on-prem and we can
kind of go through very, a lot of

106
00:08:00.630 --> 00:08:05.029
<v Richard Ella>examples there, but essentially when we
talk about and define on-prem.

107
00:08:05.410 --> 00:08:07.450
<v Richard Ella>This is what comes out of the box.

108
00:08:07.649 --> 00:08:13.929
<v Richard Ella>This is what makes the widgets, um, and we
then the next layer up is when you go

109
00:08:13.929 --> 00:08:14.989
<v Richard Ella>into the visualization.

110
00:08:15.769 --> 00:08:20.529
<v Richard Ella>So, the first layer for usually for
factories for visualization, they're going to

111
00:08:20.529 --> 00:08:25.329
<v Richard Ella>dashboards and then they'll go into OEE
where we're looking at, you know, the

112
00:08:25.329 --> 00:08:31.130
<v Richard Ella>optimum equipment efficiency where they
get very baseline data from the machines.

113
00:08:31.559 --> 00:08:36.500
<v Richard Ella>Um, and then they might go and implement
some rules-based condition monitoring

114
00:08:36.799 --> 00:08:42.909
<v Richard Ella>on-prem, which might be in a skater, it
might be in a In, in, in some kind of

115
00:08:43.250 --> 00:08:46.630
<v Richard Ella>overarching controller, but that stays
on-prem.

116
00:08:46.900 --> 00:08:53.729
<v Richard Ella>And now with, with the power of cloud and
the, um, and

117
00:08:53.729 --> 00:08:59.030
<v Richard Ella>all of the benefits that come from being
able to

118
00:09:00.250 --> 00:09:04.369
<v Richard Ella>adapt um and change and um.

119
00:09:04.729 --> 00:09:09.609
<v Richard Ella>And, and the way that you are actually
processing and monitoring data, cloud is now

120
00:09:09.609 --> 00:09:13.809
<v Richard Ella>a very much a big augmentor for what you
are doing on-prem.

121
00:09:15.130 --> 00:09:19.190
<v Niall Sullivan>Yeah, so, so I guess the question,
Richard, is, where does, you know, on-premise has

122
00:09:19.190 --> 00:09:22.010
<v Niall Sullivan>benefits up to a point and then maybe
cloud takes over.

123
00:09:22.090 --> 00:09:24.270
<v Niall Sullivan>So what is that sort of tipping point
where.

124
00:09:25.020 --> 00:09:29.500
<v Niall Sullivan>Maybe on premises does enough, but it
can't do that next bit, maybe the scale part

125
00:09:29.500 --> 00:09:30.239
<v Niall Sullivan>as an example.

126
00:09:32.099 --> 00:09:38.150
<v Richard Ella>Yeah, you see this a lot with, um, you
know, global organizations.

127
00:09:38.429 --> 00:09:45.390
<v Richard Ella>All right, so it's very important that
large companies that have companies in many

128
00:09:45.390 --> 00:09:50.479
<v Richard Ella>regions in different countries, they now
need to see insights across the board.

129
00:09:50.789 --> 00:09:54.789
<v Richard Ella>All right, so they, they need to actually
bring their data out of the OTE

130
00:09:54.789 --> 00:09:58.570
<v Richard Ella>environment and start bringing it into IT
infrastructure.

131
00:09:59.030 --> 00:10:05.229
<v Richard Ella>So, this trigger to get out of OT to IT is
a huge decision for customers.

132
00:10:05.469 --> 00:10:09.700
<v Richard Ella>I can't underestimate or I can't.

133
00:10:10.070 --> 00:10:15.109
<v Richard Ella>This is a real challenge for customers as
to why should I go into the IT

134
00:10:15.109 --> 00:10:15.549
<v Richard Ella>environment?

135
00:10:15.750 --> 00:10:17.669
<v Richard Ella>What value are you going to bring there?

136
00:10:17.710 --> 00:10:21.489
<v Richard Ella>But to your question is what is the
tipping point?

137
00:10:21.820 --> 00:10:28.429
<v Richard Ella>The tipping point is when you have run out
of value in what you can do on prem.

138
00:10:28.700 --> 00:10:32.640
<v Richard Ella>And this is happening now, um, quite a
lot.

139
00:10:32.750 --> 00:10:39.070
<v Richard Ella>OK, so new machines are coming on board
and we've got a lot more data, um, and but

140
00:10:39.070 --> 00:10:45.710
<v Richard Ella>to, to really leverage that data on prem
is difficult to leverage that

141
00:10:45.710 --> 00:10:52.650
<v Richard Ella>data to um really look at uh at different
sites and compare and,

142
00:10:52.659 --> 00:10:54.510
<v Richard Ella>and really leverage big data.

143
00:10:54.849 --> 00:10:58.049
<v Richard Ella>You have to get out of the edge, uh,
environment.

144
00:10:58.090 --> 00:11:04.650
<v Richard Ella>So the trigger is usually, uh, when a
customer is uh getting frustrated because

145
00:11:04.650 --> 00:11:11.570
<v Richard Ella>they've got the data, but they're not
leveraging um the, the value of it and this

146
00:11:11.570 --> 00:11:14.169
<v Richard Ella>is when we step in and we say listen
let's.

147
00:11:14.630 --> 00:11:17.510
<v Richard Ella>Let's keep doing what you are doing, all
right.

148
00:11:17.750 --> 00:11:20.700
<v Richard Ella>Um, and supplement it with this.

149
00:11:21.070 --> 00:11:21.400
<v Richard Ella>OK.

150
00:11:21.510 --> 00:11:28.429
<v Richard Ella>And, and, and this is very much part of a,
uh, kind of an industry 4.0

151
00:11:28.429 --> 00:11:28.950
<v Richard Ella>roadmap.

152
00:11:29.229 --> 00:11:31.469
<v Richard Ella>You can't go to cloud before you've done
Edge.

153
00:11:31.549 --> 00:11:32.789
<v Richard Ella>There's, there's no doubt about that.

154
00:11:33.469 --> 00:11:38.580
<v Richard Ella>This is, um, you, you don't just want to
push all your data to, to a cloud

155
00:11:38.580 --> 00:11:44.140
<v Richard Ella>environment and you, you, you haven't, um,
pre-process your data.

156
00:11:44.270 --> 00:11:47.419
<v Richard Ella>You, you, you're not deriving what you
need to on-prem.

157
00:11:47.750 --> 00:11:54.349
<v Richard Ella>So firstly, The first thing that keeps
everything on-prem is when you've got,

158
00:11:54.849 --> 00:11:57.000
<v Richard Ella>you know, mission critical control.

159
00:11:57.250 --> 00:12:03.890
<v Richard Ella>You know, if, if that, um, if that motor
trips, people's lives and people's lives

160
00:12:03.890 --> 00:12:07.789
<v Richard Ella>are going to be at risk within the next 2
minutes, you've got to keep that on prem.

161
00:12:08.190 --> 00:12:08.940
<v Richard Ella>You have to.

162
00:12:09.229 --> 00:12:15.280
<v Richard Ella>You can't rely on a, you know, a
cloud-based system to monitor it, um,

163
00:12:15.630 --> 00:12:17.390
<v Richard Ella>and push back.

164
00:12:17.869 --> 00:12:22.869
<v Richard Ella>So you, you, unless you've got many
different redundancies in there, which we do in

165
00:12:22.869 --> 00:12:29.109
<v Richard Ella>cloud, but I always say if you've got a
mission critical application, um, and,

166
00:12:29.510 --> 00:12:33.169
<v Richard Ella>um, the last, for example, you don't want
an emergency stop.

167
00:12:33.710 --> 00:12:39.320
<v Richard Ella>Um, going to a machine via the cloud, you
know, that's, that's the last thing you

168
00:12:39.320 --> 00:12:39.669
<v Richard Ella>want.

169
00:12:40.000 --> 00:12:44.080
<v Richard Ella>You, you can, you can have it as a, as a,
as a secondary, but, um, you've got these

170
00:12:44.080 --> 00:12:50.789
<v Richard Ella>raw protections that sit on-prem, and
that's, um, um, that we must never deviate

171
00:12:50.789 --> 00:12:52.750
<v Richard Ella>from, and that's the power on-prem.

172
00:12:53.039 --> 00:12:58.659
<v Richard Ella>We use the controllers for what they do,
the PLC controllers, the drives, um.

173
00:12:59.179 --> 00:13:03.940
<v Richard Ella>And the logic and we kind of step up from
there into, into the space.

174
00:13:04.140 --> 00:13:09.179
<v Richard Ella>But to answer your question, now, what's
the trigger is when you've saturated the

175
00:13:09.179 --> 00:13:13.520
<v Richard Ella>value, um, and you now either need to go
and higher.

176
00:13:14.539 --> 00:13:20.520
<v Richard Ella>20 reliability engineers and data analysts
to derive the insights that you feel you

177
00:13:20.520 --> 00:13:25.580
<v Richard Ella>should get or you use the power of cloud
and Sensei and its AI.

178
00:13:27.450 --> 00:13:28.679
<v Niall Sullivan>Yeah, no, that's interesting.

179
00:13:28.770 --> 00:13:33.929
<v Niall Sullivan>And, yeah, we talked, you talked about
that, we'll put very, um, so very well, you

180
00:13:33.929 --> 00:13:35.450
<v Niall Sullivan>know, what's the tipping point.

181
00:13:35.489 --> 00:13:40.770
<v Niall Sullivan>But I guess the next question really is
how can the two work in tandem together to

182
00:13:40.770 --> 00:13:45.010
<v Niall Sullivan>produce the results that ultimately we
want is scale, high return on investment and

183
00:13:45.010 --> 00:13:45.950
<v Niall Sullivan>quick return on investment.

184
00:13:46.289 --> 00:13:47.950
<v Niall Sullivan>How can, yeah, how does that sort of work?

185
00:13:50.419 --> 00:13:56.859
<v Richard Ella>I think the, the first starting point is,
um, is understanding what the

186
00:13:56.859 --> 00:13:59.150
<v Richard Ella>customer's pain points are, OK?

187
00:13:59.859 --> 00:14:06.159
<v Richard Ella>Before you come with a solution, it's very
important that, that you listen, um, and

188
00:14:06.340 --> 00:14:07.820
<v Richard Ella>you look for that tipping point.

189
00:14:08.020 --> 00:14:13.000
<v Richard Ella>There's no point in pushing a customer to
cloud if they can still do everything

190
00:14:13.210 --> 00:14:14.059
<v Richard Ella>on-prem.

191
00:14:14.500 --> 00:14:19.340
<v Richard Ella>They might just need a smaller, uh, edge
application or they might need something

192
00:14:19.340 --> 00:14:19.619
<v Richard Ella>smaller.

193
00:14:19.700 --> 00:14:25.330
<v Richard Ella>So, The first thing that we need to do is
sit down with the customer and listen to

194
00:14:25.549 --> 00:14:32.219
<v Richard Ella>what those pain points are and then, um,
articulate the value of bringing

195
00:14:32.219 --> 00:14:39.090
<v Richard Ella>something else to the table that augments
what you are doing on prem and makes it

196
00:14:39.179 --> 00:14:40.830
<v Richard Ella>a more efficient on-prem.

197
00:14:41.109 --> 00:14:45.669
<v Richard Ella>So if we look, here's a, um, if we look at
what Sensai does at scale, so.

198
00:14:46.020 --> 00:14:52.289
<v Richard Ella>Um, I know we talk about a lot about what
Sensi am and how it works, but let's just,

199
00:14:52.340 --> 00:14:58.309
<v Richard Ella>uh, define Sensii in this use case today
as a digital reliability engineer.

200
00:14:58.630 --> 00:15:01.390
<v Richard Ella>If that's its function in this role.

201
00:15:01.710 --> 00:15:07.989
<v Richard Ella>All right, so here you have a digital
reliability engineer monitoring your assets 24

202
00:15:07.989 --> 00:15:12.229
<v Richard Ella>hours a day, can move from 500 to 5000
assets.

203
00:15:12.669 --> 00:15:17.500
<v Richard Ella>Um, with a very simple graphical user
interface.

204
00:15:17.880 --> 00:15:24.159
<v Richard Ella>So now, what actually happens is you have
not changed what you're doing on-prem, but

205
00:15:24.159 --> 00:15:29.640
<v Richard Ella>you've gotten the data into Sensii to
derive insights that normally the on-prem

206
00:15:29.640 --> 00:15:35.320
<v Richard Ella>person would have to do, uh, to go and
manually analyze all of this stuff and

207
00:15:35.320 --> 00:15:40.739
<v Richard Ella>they'll have to actually, um, they'll
actually have to go and, um.

208
00:15:41.440 --> 00:15:47.359
<v Richard Ella>You know, look at Excels and look at the
on-site historians and derive it what, but

209
00:15:47.679 --> 00:15:54.400
<v Richard Ella>as you bring, say Sensai to this picture,
to this example, Sensai now tells and

210
00:15:54.400 --> 00:15:58.539
<v Richard Ella>suggests to the reliability engineer what
to focus on.

211
00:15:59.299 --> 00:16:01.469
<v Richard Ella>Uh, OK, and uh what to do.

212
00:16:01.880 --> 00:16:08.830
<v Richard Ella>So, the person on site moves away from Um,
trying to work out what's

213
00:16:08.830 --> 00:16:14.270
<v Richard Ella>wrong to working out to, uh, addressing
the actual problems.

214
00:16:14.309 --> 00:16:18.710
<v Richard Ella>And so, maybe I can just use another
simpler example.

215
00:16:18.830 --> 00:16:25.690
<v Richard Ella>This, this we see all the time is, um, for
many of our customers, they do vibration,

216
00:16:25.799 --> 00:16:27.330
<v Richard Ella>um, analytics.

217
00:16:27.789 --> 00:16:31.229
<v Richard Ella>So, for permanent hardwired vibration.

218
00:16:31.570 --> 00:16:34.090
<v Richard Ella>Analytics on site, it's very expensive.

219
00:16:34.179 --> 00:16:40.809
<v Richard Ella>So, most of our customers only have the
hardwired, um, high-speed vibration

220
00:16:40.809 --> 00:16:43.469
<v Richard Ella>analytics on their critical assets.

221
00:16:43.760 --> 00:16:48.210
<v Richard Ella>Um, and that's usually only about maybe 5
to 10% of their assets at the most.

222
00:16:48.630 --> 00:16:55.130
<v Richard Ella>But there's a large amount of assets where
they, they can see the value of doing

223
00:16:55.390 --> 00:17:00.070
<v Richard Ella>vibration and analytics on it, but, you
know, they don't have the budget to go and

224
00:17:00.070 --> 00:17:00.900
<v Richard Ella>hardwire everything.

225
00:17:00.989 --> 00:17:07.709
<v Richard Ella>So, what they will usually do is either go
for every 2 months, they'll go do

226
00:17:07.709 --> 00:17:09.270
<v Richard Ella>a manual reading.

227
00:17:09.619 --> 00:17:16.339
<v Richard Ella>And they will go and save that data and
it'll give them a red or green light,

228
00:17:16.589 --> 00:17:23.430
<v Richard Ella>but they'll do a snapshot every 23, maybe
6 months, um, and, and then

229
00:17:23.430 --> 00:17:27.329
<v Richard Ella>they'll work off that data, but that's
still very reactive.

230
00:17:28.020 --> 00:17:34.739
<v Richard Ella>So, what a customer might do then on-prem
is that they might go and install some IoT

231
00:17:34.739 --> 00:17:41.619
<v Richard Ella>sensors um that can send them alarms when
it's over a certain point, but all

232
00:17:41.619 --> 00:17:43.920
<v Richard Ella>of that is still reactive.

233
00:17:44.219 --> 00:17:44.770
<v Richard Ella>OK.

234
00:17:45.099 --> 00:17:51.839
<v Richard Ella>So, if we look at the role of one
vibration engineer on site, imagine

235
00:17:52.060 --> 00:17:59.040
<v Richard Ella>going to work and having to go and Um,
manually test 50 assets, um, the value

236
00:17:59.040 --> 00:18:03.199
<v Richard Ella>that you can actually derive out of your
own value is very limited.

237
00:18:03.319 --> 00:18:09.739
<v Richard Ella>So what, what we suggest is for those
critical assets, still stick to

238
00:18:10.000 --> 00:18:12.030
<v Richard Ella>on-prem high-speed analytics.

239
00:18:12.270 --> 00:18:12.760
<v Richard Ella>Stick to that.

240
00:18:12.839 --> 00:18:13.869
<v Richard Ella>We, we, we won't.

241
00:18:14.474 --> 00:18:20.645
<v Richard Ella>Uh, we'll always suggest you that, but for
the 80% rule, let's go put in an IOT

242
00:18:20.645 --> 00:18:24.204
<v Richard Ella>sensor that's not gonna give you your
spectrum analysis.

243
00:18:24.364 --> 00:18:29.635
<v Richard Ella>It's just gonna give you your average
acceleration over a short period of time

244
00:18:30.045 --> 00:18:35.805
<v Richard Ella>because all that we really care about is
the deviation um from what it has been

245
00:18:35.805 --> 00:18:37.925
<v Richard Ella>doing over the last couple of days or
weeks.

246
00:18:38.324 --> 00:18:41.864
<v Richard Ella>And so, here we have a situation of where.

247
00:18:42.189 --> 00:18:48.410
<v Richard Ella>Um, on-prem, we can do this high-speed
analytics, um, and we can using spectrum

248
00:18:48.410 --> 00:18:54.219
<v Richard Ella>analysis and FFT we can go and work out,
is it the bolt, is it a loose flange, do I

249
00:18:54.219 --> 00:18:56.880
<v Richard Ella>have a broken rotor bar?

250
00:18:57.219 --> 00:19:00.160
<v Richard Ella>We can do that, um, but.

251
00:19:01.390 --> 00:19:03.199
<v Richard Ella>That should not be all that we do.

252
00:19:03.319 --> 00:19:04.459
<v Richard Ella>We need to do both.

253
00:19:04.760 --> 00:19:10.579
<v Richard Ella>We now need to go, OK, that's important,
but let's bring 80% of the data into cloud

254
00:19:10.839 --> 00:19:17.400
<v Richard Ella>and let cloud go and tell, let Sensai tell
me when to go and do those inspections as

255
00:19:17.400 --> 00:19:24.199
<v Richard Ella>opposed to a blind 2 month, 3 month
snapshot in time as to how that machine is

256
00:19:24.199 --> 00:19:24.719
<v Richard Ella>performing.

257
00:19:25.130 --> 00:19:31.010
<v Richard Ella>So, um, so this is a very good example,
but it can be vibration, can be current,

258
00:19:31.170 --> 00:19:33.829
<v Richard Ella>voltage, it can be anything.

259
00:19:33.890 --> 00:19:37.130
<v Richard Ella>It depends what you are trying to
identify.

260
00:19:37.449 --> 00:19:44.030
<v Richard Ella>If you need high-speed, um, analytics,
that happens on prem.

261
00:19:44.369 --> 00:19:48.510
<v Richard Ella>So, as I said, if it's vibration spectrum
analysis, keep that on prem.

262
00:19:48.920 --> 00:19:55.750
<v Richard Ella>If you, if you want to look for a monitor,
a large drive or uh some

263
00:19:55.750 --> 00:20:00.040
<v Richard Ella>application that you need to know in a
millisecond range when there's a deviation

264
00:20:00.199 --> 00:20:06.300
<v Richard Ella>and then there's an anomaly, keep that
on-prem, but that usually is only 8 to 10% of

265
00:20:06.390 --> 00:20:08.079
<v Richard Ella>assets, critical assets of the customers.

266
00:20:08.369 --> 00:20:09.930
<v Richard Ella>We need to take care of that rest.

267
00:20:10.000 --> 00:20:14.599
<v Richard Ella>So, um, so when you bring the data into
cloud now this is lower resolution.

268
00:20:15.180 --> 00:20:22.099
<v Richard Ella>This is not gonna be your millisecond
times since I can do um VA in cloud,

269
00:20:22.219 --> 00:20:29.180
<v Richard Ella>uh, it's kind of a new feature, but um by
default, I still strongly

270
00:20:29.180 --> 00:20:35.219
<v Richard Ella>recommend get a vib uh an IoT vibration
sensor in, get a deviation from the norm,

271
00:20:35.489 --> 00:20:38.119
<v Richard Ella>let that be your trigger to when to go and
interfere.

272
00:20:38.500 --> 00:20:43.619
<v Richard Ella>And uh what Sensii is looking at is it's
looking at the average deviation over an

273
00:20:43.619 --> 00:20:44.359
<v Richard Ella>hour period.

274
00:20:44.930 --> 00:20:48.839
<v Richard Ella>Over and then puts that into um its
measurements.

275
00:20:48.930 --> 00:20:52.390
<v Richard Ella>So, it's really looking for long-term
forecasting.

276
00:20:52.930 --> 00:20:59.449
<v Richard Ella>On-prem, you're not going to forecast six
weeks into the future with 10 milliseconds

277
00:20:59.449 --> 00:21:00.369
<v Richard Ella>time slots of data.

278
00:21:00.650 --> 00:21:07.349
<v Richard Ella>You know, that, that's, you know, uh, the
on-prem analytics is more around immediate

279
00:21:07.349 --> 00:21:08.890
<v Richard Ella>uh mission critical stuff.

280
00:21:09.319 --> 00:21:16.109
<v Richard Ella>Uh, but, but with Sensai, we look at the,
the long, uh, the long term, longer, uh,

281
00:21:16.119 --> 00:21:16.699
<v Richard Ella>picture.

282
00:21:17.079 --> 00:21:23.760
<v Richard Ella>And when you combine these two, so, so my
takeaway here is, um, I will always

283
00:21:23.760 --> 00:21:29.819
<v Richard Ella>exhaust everything that a customer is
doing on-prem, leverage the, all of the,

284
00:21:30.439 --> 00:21:34.719
<v Richard Ella>um, the power of what they've done, and
then using some data aggregation, let's get

285
00:21:34.719 --> 00:21:35.819
<v Richard Ella>that into Sensai.

286
00:21:36.310 --> 00:21:40.140
<v Richard Ella>And then let's um let the two complement
each other.

287
00:21:40.430 --> 00:21:45.319
<v Richard Ella>And when you bring these two together,
when you, uh, and you don't try and, you

288
00:21:45.319 --> 00:21:52.040
<v Richard Ella>don't think that um on-prem processing is
better or worse, it's just, um, it, it's

289
00:21:52.040 --> 00:21:56.300
<v Richard Ella>the combination of these two that you end
up with a real powerful synergy there.

290
00:21:58.160 --> 00:22:02.520
<v Niall Sullivan>Yeah, and it, yeah, it's interesting
because in, and thanks for giving those sort of

291
00:22:02.520 --> 00:22:06.520
<v Niall Sullivan>examples of when best used on-premise
versus clouds.

292
00:22:06.680 --> 00:22:10.829
<v Niall Sullivan>So, what I was wondering is, you know,
when you, when you're sort of speaking to

293
00:22:10.829 --> 00:22:15.119
<v Niall Sullivan>different customers and different
organizations, is it, does it become a bit more

294
00:22:15.119 --> 00:22:15.920
<v Niall Sullivan>tribal than that?

295
00:22:16.000 --> 00:22:19.079
<v Niall Sullivan>You know, they're not thinking of the
nuances of this use case is best for this,

296
00:22:19.199 --> 00:22:20.150
<v Niall Sullivan>whereas this one's best for this.

297
00:22:20.199 --> 00:22:26.000
<v Niall Sullivan>It's a black and white on-premise, uh, you
know, or cloud, and that's the, that, and

298
00:22:26.000 --> 00:22:27.079
<v Niall Sullivan>that's the decision.

299
00:22:27.689 --> 00:22:31.329
<v Niall Sullivan>Um, I'm just wondering whether it become,
generally it start or maybe starts off

300
00:22:31.329 --> 00:22:36.540
<v Niall Sullivan>being a very black and white type
conversation, and I guess to link to that as well,

301
00:22:36.810 --> 00:22:40.489
<v Niall Sullivan>when basically when security and data
ownership and things like that come into play

302
00:22:40.489 --> 00:22:44.550
<v Niall Sullivan>at the same time, which adds the
complexity to those conversations, I'd imagine.

303
00:22:46.280 --> 00:22:47.479
<v Richard Ella>Yeah, definitely.

304
00:22:47.640 --> 00:22:49.939
<v Richard Ella>So, um, and these two go hand in hand.

305
00:22:50.040 --> 00:22:56.479
<v Richard Ella>So, um, firstly, you, you need to talk
about the value, you know, so any customer

306
00:22:56.479 --> 00:22:58.579
<v Richard Ella>that wants to take the data out of the.

307
00:22:59.040 --> 00:23:05.369
<v Richard Ella>OTE environment, you know, definitely, um,
needs to be, uh, rest

308
00:23:05.369 --> 00:23:11.729
<v Richard Ella>assured that, you know, their data is
going to be uh treated safely, securely, um,

309
00:23:11.859 --> 00:23:18.660
<v Richard Ella>and, um, and Sensi does a very good job in
demonstrating their security um

310
00:23:18.900 --> 00:23:19.800
<v Richard Ella>out of the box.

311
00:23:20.250 --> 00:23:24.079
<v Richard Ella>It's very much a part of the onboarding
and.

312
00:23:24.989 --> 00:23:30.859
<v Richard Ella>That um is certainly one of the biggest
challenges customers have is breaking

313
00:23:30.859 --> 00:23:37.069
<v Richard Ella>through from OT to IT um is feeling that
they, that the data is going and they're

314
00:23:37.069 --> 00:23:40.170
<v Richard Ella>losing their IP, uh, there's data
sovereignty.

315
00:23:40.459 --> 00:23:44.459
<v Richard Ella>There are many factors around
cybersecurity.

316
00:23:44.859 --> 00:23:50.079
<v Richard Ella>So, um, the only way you get a customer to
look at.

317
00:23:51.650 --> 00:23:58.209
<v Richard Ella>The benefits of getting the data into the
IT environment is by the value, is by

318
00:23:58.209 --> 00:24:04.400
<v Richard Ella>demonstrating what we can actually do, um,
you know, uh, it's,

319
00:24:04.770 --> 00:24:08.800
<v Richard Ella>it's, it's the same thing that kind of um
killed CDs.

320
00:24:09.089 --> 00:24:14.829
<v Richard Ella>Um, if we, if we look at uh what iTunes
did in the very early days where.

321
00:24:15.189 --> 00:24:20.550
<v Richard Ella>Um, where they released a digital single
where you could just buy one song and you

322
00:24:20.550 --> 00:24:26.349
<v Richard Ella>didn't have to buy the whole, the whole CD
anymore where you had 15 songs that you

323
00:24:26.349 --> 00:24:27.349
<v Richard Ella>didn't really want.

324
00:24:27.750 --> 00:24:32.939
<v Richard Ella>Um, and Uh, and, and this is a very good
example of where

325
00:24:34.859 --> 00:24:41.349
<v Richard Ella>that value far outweighed, um, the, you
know, what, what we were doing previously.

326
00:24:41.599 --> 00:24:43.109
<v Richard Ella>It's the same in banking.

327
00:24:43.319 --> 00:24:48.390
<v Richard Ella>If we look at how we bank today and you
look at, you know, how much money you

328
00:24:48.390 --> 00:24:50.099
<v Richard Ella>actually have, it's all digital.

329
00:24:50.439 --> 00:24:56.689
<v Richard Ella>And um it's because You know, the, the
banking sector have basically,

330
00:24:57.010 --> 00:25:02.400
<v Richard Ella>um, shown us a better way, an easier way
of handling our money.

331
00:25:02.650 --> 00:25:06.810
<v Richard Ella>Imagine if we were still trying to keep
our money on-prem, you know, keeping it

332
00:25:06.810 --> 00:25:11.729
<v Richard Ella>under the, under the bed and, and, and,
and doing cash, uh, uh, maybe that, that,

333
00:25:11.770 --> 00:25:18.130
<v Richard Ella>that works for some, but, um, when it
comes to industrial, we face the same

334
00:25:18.130 --> 00:25:18.760
<v Richard Ella>challenges.

335
00:25:19.050 --> 00:25:21.630
<v Richard Ella>We, um, and, and, but it's not just about.

336
00:25:22.060 --> 00:25:25.420
<v Richard Ella>Um, the data, it's about an intellectual,
uh, property.

337
00:25:25.780 --> 00:25:28.810
<v Richard Ella>We must never forget that our customers
are doing amazing things.

338
00:25:29.530 --> 00:25:36.300
<v Richard Ella>They are spending a lot of time coming up
with things, um, that, um, that humanity

339
00:25:36.300 --> 00:25:42.079
<v Richard Ella>needs and there's a lot of intellectual
property in that we need to respect that and

340
00:25:42.260 --> 00:25:49.150
<v Richard Ella>you need to, um, Uh, really understand
the, the, the, like the customers, um,

341
00:25:49.219 --> 00:25:49.890
<v Richard Ella>pain points there.

342
00:25:50.010 --> 00:25:54.030
<v Richard Ella>So, we have many ways of, of getting the
data out.

343
00:25:54.369 --> 00:26:00.209
<v Richard Ella>Um, but firstly is, um, from a Sensai
point of view, we, we demonstrate our

344
00:26:00.209 --> 00:26:07.050
<v Richard Ella>certification, um, and, and, and
definitely, uh, show that the, the, the

345
00:26:07.050 --> 00:26:13.329
<v Richard Ella>data is safe and secure, but But the next
part about it is the why behind it.

346
00:26:13.630 --> 00:26:20.500
<v Richard Ella>Um, and usually the people that can see
the value in, uh,

347
00:26:20.510 --> 00:26:25.689
<v Richard Ella>in a cloud application are not so much the
people that are doing the.

348
00:26:26.150 --> 00:26:30.119
<v Richard Ella>Uh, the, the processing, uh, and the, and
the coding on-prem.

349
00:26:30.430 --> 00:26:31.959
<v Richard Ella>They are usually different people.

350
00:26:32.030 --> 00:26:33.660
<v Richard Ella>It's the whole ITOT thing.

351
00:26:33.959 --> 00:26:39.359
<v Richard Ella>If you look at a, you know, a PLC engineer
versus a computer programmer, they do the

352
00:26:39.359 --> 00:26:43.459
<v Richard Ella>same thing in a different way, but they
think completely different.

353
00:26:43.760 --> 00:26:49.849
<v Richard Ella>Um, if you, and it, I find this amazing,
um, just when, when it comes to these

354
00:26:49.849 --> 00:26:56.739
<v Richard Ella>different approaches, but just, just back
to the point of Um, you know, what is the,

355
00:26:56.859 --> 00:27:00.170
<v Richard Ella>the, the best, um, there isn't one.

356
00:27:00.449 --> 00:27:05.579
<v Richard Ella>It's really understanding what works for
the customer for, um, and then bringing

357
00:27:05.579 --> 00:27:12.119
<v Richard Ella>that back to, um, what, what we need to do
at high speed and what we can do at

358
00:27:12.459 --> 00:27:13.939
<v Richard Ella>long term forecasting.

359
00:27:16.050 --> 00:27:18.329
<v Niall Sullivan>That's, it's really, yeah, really
interesting.

360
00:27:18.410 --> 00:27:23.729
<v Niall Sullivan>I mean, I guess my, um, my question is,
because, like I said before, you know, at

361
00:27:23.729 --> 00:27:27.829
<v Niall Sullivan>the start of the question, it was, um, it
can be very tribal cloud or on-premises,

362
00:27:28.329 --> 00:27:31.329
<v Niall Sullivan>you know, it can sometimes not be a
discussion about a hybrid approach, but do you

363
00:27:31.329 --> 00:27:36.010
<v Niall Sullivan>see this sort of hybrid architecture
you've described today, Richard becoming more

364
00:27:36.010 --> 00:27:40.319
<v Niall Sullivan>of the norm, you know, versus it being,
has to be one or the other.

365
00:27:40.489 --> 00:27:44.329
<v Niall Sullivan>But do you see it, uh, uh, you know, maybe
the mentality shifting?

366
00:27:44.760 --> 00:27:48.569
<v Niall Sullivan>A way to something a more hybrid approach,
or does it have to go that way, I guess

367
00:27:48.569 --> 00:27:50.489
<v Niall Sullivan>is another way to ask the question.

368
00:27:51.739 --> 00:27:53.900
<v Richard Ella>You know, Noel, I would love to say yes.

369
00:27:54.060 --> 00:27:57.280
<v Richard Ella>OK, I would love to say to you, yes, um.

370
00:27:58.310 --> 00:28:05.310
<v Richard Ella>Industry is really picking up on the
importance of um on

371
00:28:05.310 --> 00:28:09.969
<v Richard Ella>the value of what cloud uh brings to the
analytics.

372
00:28:10.310 --> 00:28:13.819
<v Richard Ella>Um, but we've, we've got a long way to go.

373
00:28:13.989 --> 00:28:14.229
<v Richard Ella>OK.

374
00:28:14.349 --> 00:28:20.689
<v Richard Ella>They, uh, we're in a very, um, when we,
when, when you talk about

375
00:28:21.030 --> 00:28:24.010
<v Richard Ella>um security and we, we talk about.

376
00:28:24.390 --> 00:28:29.489
<v Richard Ella>Um, this data, there's a lot of
apprehension in making this step.

377
00:28:29.750 --> 00:28:35.869
<v Richard Ella>It's not so much a challenge for our
bigger customers that really, uh, that already

378
00:28:35.869 --> 00:28:40.619
<v Richard Ella>have an IT, uh, infrastructure networking
across their sites.

379
00:28:40.949 --> 00:28:41.869
<v Richard Ella>All right, so.

380
00:28:42.400 --> 00:28:46.540
<v Richard Ella>For, for them it's, it's not so much of a
challenge because they've already put

381
00:28:47.040 --> 00:28:49.930
<v Richard Ella>safeguards in place to protect their data.

382
00:28:50.119 --> 00:28:55.680
<v Richard Ella>It's usually when we are talking to a new
customer that um is not networked to other

383
00:28:55.680 --> 00:28:59.260
<v Richard Ella>sites that's usually when the, when the
challenge comes in.

384
00:28:59.280 --> 00:29:06.270
<v Richard Ella>But um to, to your, to your question, I
don't know if it's tribal um it

385
00:29:06.359 --> 00:29:08.619
<v Richard Ella>it it's, it's more a.

386
00:29:08.989 --> 00:29:15.959
<v Richard Ella>Um, a human nature thing about why should
I do something different, uh, and the only

387
00:29:15.959 --> 00:29:22.729
<v Richard Ella>way that we, uh, change our behavior is
until we see the value and, um,

388
00:29:23.079 --> 00:29:29.380
<v Richard Ella>I, I, I've seen a lot of change, uh, in
the possibility.

389
00:29:30.280 --> 00:29:33.000
<v Richard Ella>Of, of, of moving your data into cloud.

390
00:29:33.199 --> 00:29:40.010
<v Richard Ella>Um, and, but, um, we're not seeing that
in, in a, in a, in a physical

391
00:29:40.680 --> 00:29:41.959
<v Richard Ella>metric that I can measure.

392
00:29:42.079 --> 00:29:48.130
<v Richard Ella>Most customers, um, we, we really have to
talk around the, um.

393
00:29:48.579 --> 00:29:53.510
<v Richard Ella>The importance of security and then the
value that you get out of um Sensor and

394
00:29:54.380 --> 00:29:59.439
<v Richard Ella>maybe I just need to spend just two
minutes and maybe I didn't articulate this one

395
00:29:59.439 --> 00:30:06.020
<v Richard Ella>very well is when we talk about the power
of cloud is uh versus

396
00:30:06.020 --> 00:30:12.920
<v Richard Ella>on-prem, what we see um um every day is
that on-prem we come up with solutions,

397
00:30:12.939 --> 00:30:18.260
<v Richard Ella>we code and everybody goes home and and 6
months later, it's outdated.

398
00:30:18.650 --> 00:30:25.640
<v Richard Ella>Um, so, the whole thing about firmware
updates, code, patching, all

399
00:30:25.640 --> 00:30:32.050
<v Richard Ella>of this is becoming a nightmare on-prem,
um, because, uh, you can go and implement a

400
00:30:32.050 --> 00:30:38.890
<v Richard Ella>solution today on-prem, um, but yeah, it,
it, it becomes obsolete very, very

401
00:30:38.890 --> 00:30:45.170
<v Richard Ella>quickly, um, and it takes a lot of effort,
uh, to maintain an edge

402
00:30:45.170 --> 00:30:47.770
<v Richard Ella>platform as opposed to a cloud solution.

403
00:30:48.260 --> 00:30:55.250
<v Richard Ella>So, if, if I just take Sensai for example,
if I look at how fast um

404
00:30:55.420 --> 00:31:02.290
<v Richard Ella>and how quick Sensii has developed its
application in the last 6 months, if you just

405
00:31:02.290 --> 00:31:03.849
<v Richard Ella>have to look at the release notes.

406
00:31:04.260 --> 00:31:11.000
<v Richard Ella>If we, if you look at how much more
features have been added and how much more value

407
00:31:11.140 --> 00:31:14.280
<v Richard Ella>was created using the same platform.

408
00:31:14.790 --> 00:31:20.550
<v Richard Ella>Unbeknown to um a customer because they
don't have to go to a firmware update, it's

409
00:31:20.550 --> 00:31:21.949
<v Richard Ella>all part of the package.

410
00:31:22.430 --> 00:31:28.109
<v Richard Ella>So, this is what happens when you go into
cloud, you get this uh high speed

411
00:31:28.109 --> 00:31:34.770
<v Richard Ella>deployment, you get um you are able to
pivot very, very quickly and you are able to

412
00:31:35.030 --> 00:31:39.410
<v Richard Ella>um basically um provide.

413
00:31:40.380 --> 00:31:45.069
<v Richard Ella>Um, um, different versions and upgrades a
lot quicker.

414
00:31:45.390 --> 00:31:51.030
<v Richard Ella>Um, and one of the things I actually love
about Sensai is how they engage their

415
00:31:51.030 --> 00:31:57.454
<v Richard Ella>customers on product update calls, you
know, so, um, It's quite normal for Sensai to

416
00:31:57.454 --> 00:32:04.375
<v Richard Ella>sit down with particular customers, um,
and talk about, uh, product updates and also

417
00:32:04.375 --> 00:32:11.035
<v Richard Ella>listen to the customer as to what, um,
they want to provide as feedback and so.

418
00:32:11.869 --> 00:32:18.189
<v Richard Ella>That closed loop of functionality to
execution can only be done at cloud and that's

419
00:32:18.189 --> 00:32:19.400
<v Richard Ella>the real power of it.

420
00:32:19.510 --> 00:32:26.180
<v Richard Ella>So, in, I, I think we've all seen how fast
AI is moving, um, and, you know,

421
00:32:26.469 --> 00:32:28.829
<v Richard Ella>who knows what tomorrow brings.

422
00:32:29.150 --> 00:32:31.949
<v Richard Ella>And so, this is all about futureproofing
yourself.

423
00:32:32.270 --> 00:32:33.510
<v Richard Ella>You can stay on-prem.

424
00:32:33.660 --> 00:32:34.310
<v Richard Ella>That's OK.

425
00:32:34.939 --> 00:32:38.979
<v Richard Ella>But you are going to limit yourself in
functionality.

426
00:32:39.020 --> 00:32:45.219
<v Richard Ella>You're going to limit yourself in um the
being agile and being able to pivot.

427
00:32:45.579 --> 00:32:51.739
<v Richard Ella>So, keep some stuff on-prem, keep some
stuff on cloud, and the power sits in the

428
00:32:51.739 --> 00:32:53.719
<v Richard Ella>middle and the value sits in the middle
now.

429
00:32:55.150 --> 00:32:58.390
<v Niall Sullivan>Yeah, and that's really interesting
because I was, um, so, you know, as we come

430
00:32:58.390 --> 00:33:02.290
<v Niall Sullivan>towards the end, I was gonna, as I
normally do, as you know, on these podcasts, just

431
00:33:02.550 --> 00:33:05.790
<v Niall Sullivan>ask you to summarize some sort of key
takeaways, you know, for companies, you know,

432
00:33:05.869 --> 00:33:09.729
<v Niall Sullivan>looking to maybe approach this, you know,
this hybrid approach.

433
00:33:09.829 --> 00:33:13.030
<v Niall Sullivan>But actually, I think in your answer
there, you've probably summarized it quite

434
00:33:13.030 --> 00:33:13.150
<v Niall Sullivan>well.

435
00:33:13.229 --> 00:33:16.790
<v Niall Sullivan>But is there anything else you'd like to
add, you know, on top of that, you might,

436
00:33:16.869 --> 00:33:19.819
<v Niall Sullivan>you, you may have missed just for people
to start thinking about today, if this is

437
00:33:19.819 --> 00:33:23.140
<v Niall Sullivan>something that really interests them and
they want to pursue.

438
00:33:23.349 --> 00:33:23.719
<v Richard Ella>Yeah.

439
00:33:24.530 --> 00:33:29.170
<v Richard Ella>Look, when it comes to on-prem or cloud,
this is not black or white.

440
00:33:29.489 --> 00:33:30.130
<v Richard Ella>All right.

441
00:33:30.209 --> 00:33:35.089
<v Richard Ella>If, if, if, if you had to ask me what's
the best, it's actually the gray because uh

442
00:33:35.089 --> 00:33:41.969
<v Richard Ella>when you combine the power of on-prem and
it's um value add and

443
00:33:41.969 --> 00:33:45.750
<v Richard Ella>cloud, you end up with this really
powerful solution.

444
00:33:46.050 --> 00:33:52.729
<v Richard Ella>And all I ask is that, um, that when you
are looking, when a customer is looking for

445
00:33:52.729 --> 00:33:53.310
<v Richard Ella>something.

446
00:33:53.770 --> 00:34:00.650
<v Richard Ella>Um, Keep an open mind and um entertain the
value and

447
00:34:00.650 --> 00:34:02.489
<v Richard Ella>the power of both.

448
00:34:02.810 --> 00:34:03.250
<v Richard Ella>OK.

449
00:34:03.369 --> 00:34:09.239
<v Richard Ella>Um, and it's very hard for traditional
automation and control engineers because they

450
00:34:09.239 --> 00:34:16.010
<v Richard Ella>have to relinquish a lot of the logic and
um brainpower that they've put

451
00:34:16.010 --> 00:34:16.770
<v Richard Ella>into.

452
00:34:17.080 --> 00:34:21.989
<v Richard Ella>Uh, making something safe, secure, and
predicted, uh, at a, at an edge level.

453
00:34:22.439 --> 00:34:25.399
<v Richard Ella>So, um, there's a lot of value in both.

454
00:34:25.520 --> 00:34:32.260
<v Richard Ella>So, all I wanted to maybe finish with was
open mind, um, leverage the power of both,

455
00:34:32.760 --> 00:34:35.639
<v Richard Ella>and, uh, you will see great value.

456
00:34:35.879 --> 00:34:42.840
<v Richard Ella>Um, if you stick to one, you, you, you're
gonna be restricted, um, and you,

457
00:34:43.199 --> 00:34:45.889
<v Richard Ella>your, your roadmap is, is, is gonna.

458
00:34:46.610 --> 00:34:47.449
<v Richard Ella>Hit a dead end.

459
00:34:47.729 --> 00:34:53.169
<v Richard Ella>When you combine both, you, you really
are, have got a roadmap to be flexible as

460
00:34:53.169 --> 00:34:53.879
<v Richard Ella>things change.

461
00:34:54.090 --> 00:34:58.929
<v Richard Ella>That's what we want to set ourselves up
for is what's coming, um, and leverage

462
00:34:58.929 --> 00:34:59.750
<v Richard Ella>today's power.

463
00:35:00.610 --> 00:35:00.979
<v Niall Sullivan>Yeah.

464
00:35:01.330 --> 00:35:02.209
<v Niall Sullivan>No, that makes a lot of sense.

465
00:35:02.280 --> 00:35:07.840
<v Niall Sullivan>Yeah, don't, don't make decisions today
which may, um, delay things in future if you

466
00:35:07.840 --> 00:35:09.409
<v Niall Sullivan>do want to sort of scale.

467
00:35:09.810 --> 00:35:12.570
<v Niall Sullivan>Well, yeah, and that should, that should
be the pathway they're looking to do.

468
00:35:12.729 --> 00:35:14.850
<v Niall Sullivan>So yeah, really good advice there, um.

469
00:35:15.479 --> 00:35:18.520
<v Niall Sullivan>But yeah, no, for today, a really
interesting conversation, Richard.

470
00:35:18.679 --> 00:35:22.590
<v Niall Sullivan>Like I said, uh, to my knowledge, it's the
first time we've sort of covered the two,

471
00:35:22.750 --> 00:35:25.879
<v Niall Sullivan>you know, how we can cloud an on-premise,
and I think you've articulated that really

472
00:35:25.879 --> 00:35:27.879
<v Niall Sullivan>well, um, for the audience as well.

473
00:35:28.280 --> 00:35:30.580
<v Niall Sullivan>So, um, yeah, thank you for sharing your
expertise with us.

474
00:35:32.590 --> 00:35:33.300
<v Richard Ella>No problem, Noel.

475
00:35:33.389 --> 00:35:33.989
<v Richard Ella>Thank you very much.

476
00:35:34.070 --> 00:35:35.729
<v Richard Ella>I'd actually, I'd love to.

477
00:35:37.179 --> 00:35:41.760
<v Richard Ella>I don't know if it's possible to put some
kind of survey out there and, and see

478
00:35:42.020 --> 00:35:48.699
<v Richard Ella>what, um, what actually our customers,
what they feel, um, is best for them, you

479
00:35:48.699 --> 00:35:51.439
<v Richard Ella>know, on-prem, cloud, or both.

480
00:35:51.659 --> 00:35:55.780
<v Richard Ella>Um, I, I might do something with our
customers here in Australia and feed it back to

481
00:35:55.780 --> 00:36:00.040
<v Richard Ella>you and, and, um, thank you very much for
your time today now and look after

482
00:36:00.040 --> 00:36:00.399
<v Richard Ella>yourself.

483
00:36:01.300 --> 00:36:02.260
<v Niall Sullivan>Yeah, no, thank you.

484
00:36:02.379 --> 00:36:05.620
<v Niall Sullivan>And maybe, you know, to your point about
that, maybe we can put something in the

485
00:36:05.620 --> 00:36:06.300
<v Niall Sullivan>show notes.

486
00:36:06.699 --> 00:36:11.820
<v Niall Sullivan>You know, just to, um, even if you send us
a quick email of one line saying, you

487
00:36:11.820 --> 00:36:14.979
<v Niall Sullivan>know, one sentence summarizing your sort
of thoughts on the episode, that'd be

488
00:36:14.979 --> 00:36:15.379
<v Niall Sullivan>really cool.

489
00:36:15.500 --> 00:36:19.199
<v Niall Sullivan>And we can share, share our notes on a, on
a future episode, I hope, as well.

490
00:36:19.340 --> 00:36:19.919
<v Niall Sullivan>That'd be cool.

491
00:36:20.060 --> 00:36:20.459
<v Niall Sullivan>Um.

492
00:36:21.229 --> 00:36:26.580
<v Niall Sullivan>But yeah, for today, um thank you Richard
again, um, hope to have you back on soon

493
00:36:26.760 --> 00:36:30.959
<v Niall Sullivan>and thank you everyone out there for
listening, wherever you are in the world and

494
00:36:30.959 --> 00:36:32.100
<v Niall Sullivan>we'll see you on the next episode.

495
00:36:32.719 --> 00:36:33.659
<v Niall Sullivan>Thank you very much.

496
00:36:37.610 --> 00:36:42.570
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

497
00:36:42.570 --> 00:36:45.949
<v Speaker 2>Sensi predictive maintenance at
Siemens.com.
