WEBVTT
Language: en-US

1
00:00:01.029 --> 00:00:05.429
<v Inger Eriksson>And the data is provided in an
understandable way to the customer without involving

2
00:00:05.429 --> 00:00:07.909
<v Inger Eriksson>expertise from an external consultants.

3
00:00:08.890 --> 00:00:14.569
<v Inger Eriksson>And talking ROI, the first year this
customer had the Al solution installed

4
00:00:14.569 --> 00:00:19.350
<v Inger Eriksson>prevented unforeseen events that would
have cost more than €100,000 in repairs.

5
00:00:20.260 --> 00:00:25.219
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens, and now your host.

6
00:00:26.389 --> 00:00:29.129
<v Speaker 3>Good morning, good afternoon and good
evening, everyone.

7
00:00:29.350 --> 00:00:31.420
<v Speaker 3>A very warm welcome from, from my side.

8
00:00:31.889 --> 00:00:33.909
<v Speaker 3>Uh, my name is Farizio Nizocantara.

9
00:00:33.950 --> 00:00:38.790
<v Speaker 3>I am a director of business development at
Siemens AG in Germany, and today I have

10
00:00:38.790 --> 00:00:42.450
<v Speaker 3>the pleasure to host and uh moderate this
webinar.

11
00:00:43.349 --> 00:00:46.970
<v Speaker 3>Insights from LWatch and Sensite
Predictive Maintenance.

12
00:00:48.009 --> 00:00:49.110
<v Speaker 3>I'm not alone today.

13
00:00:49.770 --> 00:00:51.849
<v Speaker 3>With me, I've brought three other
gentlemen.

14
00:00:51.930 --> 00:00:54.569
<v Speaker 3>I would also, uh, introduce yourself.

15
00:00:54.689 --> 00:00:57.549
<v Speaker 3>First of all, uh, I have Inger, Mr.

16
00:00:57.569 --> 00:01:01.090
<v Speaker 3>Inger Fredriksen, who is the chief
executive Officer at LWatch.

17
00:01:01.450 --> 00:01:01.889
<v Speaker 3>Inger.

18
00:01:02.740 --> 00:01:07.069
<v Inger Eriksson>Yeah, my name is Inger Eriksson, and I'm
an electronic engineer by education.

19
00:01:07.860 --> 00:01:12.580
<v Inger Eriksson>I worked with development of new
technology and introducing it to various markets

20
00:01:12.580 --> 00:01:14.040
<v Inger Eriksson>for more than 25 years.

21
00:01:14.830 --> 00:01:19.529
<v Inger Eriksson>Uh, as Fabio say, I'm the CEO of Elwch,
and we are a technology company from Norway

22
00:01:19.529 --> 00:01:24.230
<v Inger Eriksson>that provides a wireless, online, and
user-friendly sensor system, or in other

23
00:01:24.230 --> 00:01:26.330
<v Inger Eriksson>words, an IoT sensor system.

24
00:01:26.870 --> 00:01:30.870
<v Inger Eriksson>And we deliver this to industrial
customers for many different use cases, including

25
00:01:30.870 --> 00:01:34.290
<v Inger Eriksson>predictive maintenance, energy monitoring,
and process control.

26
00:01:36.150 --> 00:01:38.099
<v Speaker 3>With me, I've also Mr.

27
00:01:38.139 --> 00:01:42.639
<v Speaker 3>Naya Sullivan, who is the head of
marketing for Sensi Predictive maintenance.

28
00:01:45.800 --> 00:01:46.680
<v Niall Sullivan>Yes, hello everyone.

29
00:01:46.790 --> 00:01:48.190
<v Niall Sullivan>Um, I'll keep mine very short and sweet.

30
00:01:48.230 --> 00:01:52.160
<v Niall Sullivan>It's it's really all about Ingar and
Chris, um, who I'll be interviewing today, but

31
00:01:52.160 --> 00:01:55.959
<v Niall Sullivan>yes, I'm the head of marketing, um, since
I predicts maintenance, all the related,

32
00:01:56.000 --> 00:01:58.440
<v Niall Sullivan>um, portfolio as well.

33
00:01:58.639 --> 00:02:02.300
<v Niall Sullivan>Um, I've been in the position but for
around, um, 4.5 years now.

34
00:02:02.800 --> 00:02:06.879
<v Niall Sullivan>Um, and you may have hopefully maybe
listened to our trend detection podcast as

35
00:02:06.879 --> 00:02:07.190
<v Niall Sullivan>well.

36
00:02:07.400 --> 00:02:11.399
<v Niall Sullivan>Um, just a quick plug there, but yeah, we,
um, I'm really looking forward to today's

37
00:02:11.399 --> 00:02:11.759
<v Niall Sullivan>session.

38
00:02:13.190 --> 00:02:13.669
<v Speaker 3>Thank you.

39
00:02:13.919 --> 00:02:18.970
<v Speaker 3>Last but not least, uh, I have also with
me Doctor Chris uh Smith, who is the head

40
00:02:18.970 --> 00:02:21.809
<v Speaker 3>of delivery for SEMN Seitive maintenance.

41
00:02:23.050 --> 00:02:23.929
<v Speaker 5>Yeah, thank you very much.

42
00:02:24.050 --> 00:02:25.729
<v Speaker 5>So as I mentioned, my name's Chris.

43
00:02:26.250 --> 00:02:31.889
<v Speaker 5>Uh, my main role um in my day to day is
very much around how do we commoditize

44
00:02:31.889 --> 00:02:36.509
<v Speaker 5>predictive maintenance delivery to make
it, you know, faster, quicker to market.

45
00:02:37.520 --> 00:02:41.830
<v Speaker 5>Quicker to results for our end customers,
so that relates not only to our product,

46
00:02:42.279 --> 00:02:48.080
<v Speaker 5>which is er sun I predictive maintenance,
which uses AI and generative AI technology

47
00:02:48.080 --> 00:02:54.880
<v Speaker 5>to look at predicting potential issues in
your plant at scale, but

48
00:02:54.880 --> 00:03:01.000
<v Speaker 5>also looking at kind of portfolio that is
around it, such as connectivity, etc.

49
00:03:01.229 --> 00:03:04.679
<v Speaker 5>where you know, because at the end of the
day, if we don't have any data, we can't

50
00:03:04.679 --> 00:03:06.880
<v Speaker 5>tell you any interesting insights.

51
00:03:07.669 --> 00:03:12.559
<v Speaker 5>Uh, I've been working with, uh, Sunsai for
about 7 years now, um, and been in the

52
00:03:12.559 --> 00:03:16.529
<v Speaker 5>kind of reliability space for just over a
decade working in the rail sector, wind

53
00:03:16.529 --> 00:03:19.479
<v Speaker 5>sector, uh, before joining SunSai.

54
00:03:19.880 --> 00:03:20.830
<v Speaker 5>So thank you very much.

55
00:03:21.279 --> 00:03:22.039
<v Speaker 3>Thank you so much.

56
00:03:22.119 --> 00:03:28.000
<v Speaker 3>And, uh, yeah, before we kick off, I
would, uh, um, I would, uh, tell a bit kind of

57
00:03:28.000 --> 00:03:30.229
<v Speaker 3>housekeeping details for, uh, for today.

58
00:03:30.600 --> 00:03:34.729
<v Speaker 3>So, uh, all of your microsoft phones are
muted throughout the webinar.

59
00:03:35.130 --> 00:03:38.929
<v Speaker 3>Uh, this way we can ensure a smooth
presentation for, for everyone.

60
00:03:39.369 --> 00:03:43.610
<v Speaker 3>Uh, still, we want to also have this as an
interactive action, so please, uh, feel

61
00:03:43.610 --> 00:03:47.330
<v Speaker 3>free anytime to, uh, type your, uh, your
questions in the chat.

62
00:03:47.410 --> 00:03:50.330
<v Speaker 3>So on your, on the left, on the right side
of your screen, there is also a

63
00:03:50.330 --> 00:03:52.889
<v Speaker 3>possibility for you to answer your
questions.

64
00:03:52.970 --> 00:03:57.649
<v Speaker 3>I will be mod taking and moderating this
question at the very end of the, uh, of the

65
00:03:57.649 --> 00:03:58.330
<v Speaker 3>presentation.

66
00:03:59.600 --> 00:04:03.860
<v Speaker 3>Uh, please note that this webinar will be
recorded and will be also made available

67
00:04:04.119 --> 00:04:08.279
<v Speaker 3>on demand afterwards, uh, for you on the
Siemens Accelerator, uh, marketplace.

68
00:04:09.270 --> 00:04:14.470
<v Speaker 3>So, before we, uh, start with the
presentation and the interview uh to IWatch, I, I

69
00:04:14.470 --> 00:04:18.709
<v Speaker 3>want to give you a bit of background of
why we are also hosting this, this webinar.

70
00:04:19.149 --> 00:04:25.109
<v Speaker 3>Um, as you may know, uh, Siemens, uh,
since already 3 years, started a new, uh, way

71
00:04:25.109 --> 00:04:31.500
<v Speaker 3>of, uh, go to the going to the market, uh,
and we introduced the, um, um, Siemens

72
00:04:31.500 --> 00:04:33.929
<v Speaker 3>accelerator, uh, as a business platform.

73
00:04:34.859 --> 00:04:36.660
<v Speaker 3>That is actually three main components.

74
00:04:36.820 --> 00:04:38.619
<v Speaker 3>One is a creative portfolio.

75
00:04:39.079 --> 00:04:43.980
<v Speaker 3>The second one is, uh, um, having a
powerful ecosystem of third-party companies, and

76
00:04:43.980 --> 00:04:47.619
<v Speaker 3>the third one is, uh, the, uh, the Siemens
accelerator Marketplace.

77
00:04:48.100 --> 00:04:53.369
<v Speaker 3>So, uh, we believe that, uh, uh, you know,
we can go to the market best with our,

78
00:04:53.420 --> 00:04:55.119
<v Speaker 3>uh, with our partners.

79
00:04:55.420 --> 00:04:59.980
<v Speaker 3>Uh, we have, uh, a, a huge portfolio
spanning from automation, from software, from

80
00:04:59.980 --> 00:05:00.859
<v Speaker 3>building software.

81
00:05:01.209 --> 00:05:05.540
<v Speaker 3>Uh, but, uh, we also rely very strongly
also on third-party companies.

82
00:05:05.609 --> 00:05:09.929
<v Speaker 3>That's also the reason why today we have
also here, uh, IWatch, uh, together with

83
00:05:09.929 --> 00:05:15.480
<v Speaker 3>us, and, uh, um, they are, uh, one of our,
uh, many Siemens accelerator, uh,

84
00:05:15.489 --> 00:05:16.429
<v Speaker 3>marketplace sellers.

85
00:05:16.649 --> 00:05:21.429
<v Speaker 3>So I'm proud to have you, uh, also already
on board and also building a sustainable

86
00:05:21.809 --> 00:05:23.429
<v Speaker 3>business future, uh, together.

87
00:05:23.859 --> 00:05:27.899
<v Speaker 3>Uh, the, the third component of the
Siemens accelerator strategy.

88
00:05:28.839 --> 00:05:31.179
<v Speaker 3>Is the marketplace, marketplace by
definition.

89
00:05:31.640 --> 00:05:36.170
<v Speaker 3>Uh, we are building an e-commerce platform
for Siemens, uh, where, uh, we will make,

90
00:05:36.959 --> 00:05:42.429
<v Speaker 3>uh, our products, uh, our services, but
also, of course, uh, the same for

91
00:05:42.429 --> 00:05:46.859
<v Speaker 3>third-party, uh, sellers, uh, portfolio
available on this platform.

92
00:05:47.459 --> 00:05:52.679
<v Speaker 3>Um, and as we can see also in the second,
in the next, uh, part, it's also about

93
00:05:52.679 --> 00:05:56.339
<v Speaker 3>creating the right, um, you know, the, the
right portfolio.

94
00:05:57.049 --> 00:06:03.589
<v Speaker 3>And, uh, uh, last but not least, also the,
um, creating a, a place to attract,

95
00:06:03.970 --> 00:06:06.760
<v Speaker 3>uh, buyers, sellers, and developers.

96
00:06:07.250 --> 00:06:11.390
<v Speaker 3>This is also made available uh across uh
different solution journey.

97
00:06:11.690 --> 00:06:18.250
<v Speaker 3>Uh, solution journeys are including, uh,
our, um, industries specific solutions that

98
00:06:18.250 --> 00:06:22.329
<v Speaker 3>we tailor and we make available at the end
of the day over the Siemens accelerator

99
00:06:22.329 --> 00:06:22.970
<v Speaker 3>marketplace.

100
00:06:23.890 --> 00:06:29.600
<v Speaker 3>Another key components of the, uh, of our
marketplace is also, uh, communities.

101
00:06:30.010 --> 00:06:36.350
<v Speaker 3>Communities, as you may also have, uh,
heard, um, already, is, um, a really a place

102
00:06:36.350 --> 00:06:42.230
<v Speaker 3>where, uh, third-party companies can
really exchange, build up their ecosystem and

103
00:06:42.230 --> 00:06:47.750
<v Speaker 3>exchange your, uh, exchange their
experiences and so really building, uh, their own,

104
00:06:47.850 --> 00:06:49.850
<v Speaker 3>um, also capabilities forward.

105
00:06:50.549 --> 00:06:56.730
<v Speaker 3>Uh, the marketplace, uh, offers, uh, a 360
personalized omni-channel, uh,

106
00:06:56.829 --> 00:07:01.269
<v Speaker 3>experience, meaning that our customers out
there can really start the digital

107
00:07:01.269 --> 00:07:06.890
<v Speaker 3>journey over the marketplace, uh, but then
also maybe end up the journey offline,

108
00:07:07.230 --> 00:07:08.470
<v Speaker 3>uh, or vice versa.

109
00:07:08.589 --> 00:07:13.670
<v Speaker 3>So, um, it's of course something that we
are building up as we go together with our

110
00:07:13.670 --> 00:07:16.470
<v Speaker 3>sellers and EWatch is a very good example
for that.

111
00:07:17.440 --> 00:07:23.989
<v Speaker 3>Um, As you can also, um, so again, uh,
AirWatch has been on board in, uh, on our

112
00:07:23.989 --> 00:07:26.260
<v Speaker 3>marketplace already since a couple of
months.

113
00:07:26.390 --> 00:07:31.820
<v Speaker 3>Um, there are already established, uh,
connections, uh, with, with Siemens.

114
00:07:32.329 --> 00:07:36.989
<v Speaker 3>AirWatch, uh, specializes in developing
and manufacturing, uh, robust, easy to

115
00:07:36.989 --> 00:07:39.579
<v Speaker 3>deploy wireless industrial sensors.

116
00:07:39.829 --> 00:07:44.890
<v Speaker 3>So it's a great combination for our
portfolio of predictive maintenance.

117
00:07:44.989 --> 00:07:47.390
<v Speaker 3>We're really focusing on data acquisition.

118
00:07:47.899 --> 00:07:51.549
<v Speaker 3>Predictive maintenance software, data
analysis, and insights.

119
00:07:52.329 --> 00:07:59.320
<v Speaker 3>So this, uh, um, in essence, LWatch
provides, uh, the necessary framework to

120
00:07:59.320 --> 00:08:05.730
<v Speaker 3>gather data from the physical world and
the Sensi acts as the brain that processes

121
00:08:05.730 --> 00:08:10.109
<v Speaker 3>this information to deliver intelligence
forsight full maintenance strategies.

122
00:08:11.149 --> 00:08:16.390
<v Speaker 3>So with that, I would like to hand over
now to Nia, who is going to moderate this

123
00:08:16.390 --> 00:08:16.839
<v Speaker 3>conversation with that watch.

124
00:08:20.630 --> 00:08:21.140
<v Niall Sullivan>Brilliant.

125
00:08:21.390 --> 00:08:25.799
<v Niall Sullivan>Um, yes, thank you, um, Fabrizio for that
fantastic introduction.

126
00:08:25.980 --> 00:08:30.709
<v Niall Sullivan>Um, I think we've got around 30 minutes or
just under, um, for the discussion today,

127
00:08:30.809 --> 00:08:36.190
<v Niall Sullivan>but again, just to reinforce, please add
your questions to the chat, um, as, as we

128
00:08:36.190 --> 00:08:39.500
<v Niall Sullivan>speak, we'll, we'll answer those at the
end of Fabrizio, we'll manage that at the

129
00:08:39.500 --> 00:08:39.729
<v Niall Sullivan>end.

130
00:08:40.469 --> 00:08:44.869
<v Niall Sullivan>Um, but yes, today's discussion, um, as
you probably saw the title, so.

131
00:08:45.210 --> 00:08:50.210
<v Niall Sullivan>We're talking about scalable, um, IoT and
we're getting insights from, as Fabrizio

132
00:08:50.210 --> 00:08:54.190
<v Niall Sullivan>said, sort of both sides of the coin, both
sort of work together very, very closely.

133
00:08:54.859 --> 00:08:59.250
<v Niall Sullivan>Um, and I guess just to kick off the
discussion, this is probably a question, um,

134
00:08:59.260 --> 00:09:06.080
<v Niall Sullivan>for both of you, but, um, how have I Watch
and S I, um, seen industrial IOT directly

135
00:09:06.080 --> 00:09:07.919
<v Niall Sullivan>impact customer return on investment.

136
00:09:08.340 --> 00:09:09.809
<v Niall Sullivan>It's a nice positive one to open up.

137
00:09:09.969 --> 00:09:12.859
<v Niall Sullivan>So I'll start maybe with you, Inga, um,
let's go first.

138
00:09:13.179 --> 00:09:16.340
<v Inger Eriksson>Yeah, well, maybe, maybe I could start
with one example there.

139
00:09:16.460 --> 00:09:21.729
<v Inger Eriksson>So, so we have a customer that used to
monitor 20 of their most critical assets with

140
00:09:21.729 --> 00:09:23.799
<v Inger Eriksson>a handheld vibration monitoring device.

141
00:09:24.530 --> 00:09:28.969
<v Inger Eriksson>And they needed external consultant to to
analyze the data they collected with these

142
00:09:28.969 --> 00:09:29.489
<v Inger Eriksson>devices.

143
00:09:30.320 --> 00:09:35.010
<v Inger Eriksson>And now they monitor almost 200 assets
with LWatch IoT sensors.

144
00:09:35.789 --> 00:09:40.190
<v Inger Eriksson>And the measurements they get from the IOC
sensors are vibration and surface

145
00:09:40.190 --> 00:09:45.150
<v Inger Eriksson>temperature, and they are made
continuously, and the data is provided in an

146
00:09:45.150 --> 00:09:49.229
<v Inger Eriksson>understandable way to the customer without
involving expertise from an external

147
00:09:49.229 --> 00:09:49.969
<v Inger Eriksson>consultants.

148
00:09:50.979 --> 00:09:56.659
<v Inger Eriksson>And talking ROI, the first year this
customer had the Al solution installed

149
00:09:56.659 --> 00:10:01.419
<v Inger Eriksson>prevented unforeseen events that would
have cost more than €100,000 in repairs.

150
00:10:02.380 --> 00:10:06.719
<v Inger Eriksson>Uh, and the investment in IOT was around
€40,000 for 200 assets.

151
00:10:06.900 --> 00:10:11.419
<v Inger Eriksson>And that's pretty similar to the annual
cost for handle measurements and consultants

152
00:10:11.419 --> 00:10:14.619
<v Inger Eriksson>for analysis on the 20 assets they, they
did earlier.

153
00:10:15.429 --> 00:10:20.760
<v Inger Eriksson>So there are really big ROIs to, to
achieve uh when using IOT sensors for predictive

154
00:10:20.760 --> 00:10:21.219
<v Inger Eriksson>maintenance.

155
00:10:22.140 --> 00:10:25.739
<v Niall Sullivan>Right, fantastic example to kick us off
and hopefully Chris, you can follow with

156
00:10:25.739 --> 00:10:26.520
<v Niall Sullivan>another one from the sense.

157
00:10:26.900 --> 00:10:27.140
<v Niall Sullivan>Yeah,

158
00:10:27.299 --> 00:10:28.039
<v Speaker 5>yeah, sure.

159
00:10:28.539 --> 00:10:34.979
<v Speaker 5>I think, I think what we're releasing is
the two elements of scale for the same cost

160
00:10:35.049 --> 00:10:41.400
<v Speaker 5>and also an introduction to, I would say
kind of smaller players in markets where

161
00:10:41.619 --> 00:10:44.940
<v Speaker 5>this kind of technology was originally
just you, you couldn't get near it.

162
00:10:44.979 --> 00:10:47.280
<v Speaker 5>It was far too expensive for their use
cases, etc.

163
00:10:47.460 --> 00:10:47.820
<v Speaker 5>so you.

164
00:10:48.190 --> 00:10:52.250
<v Speaker 5>We're seeing kind of a, a divergence to a
much wider market.

165
00:10:52.549 --> 00:10:57.270
<v Speaker 5>So for example, um, you know, one of our
largest clients originally started doing

166
00:10:57.270 --> 00:11:03.229
<v Speaker 5>handheld monitoring for 100 critical
assets, for example, because that, that was all

167
00:11:03.229 --> 00:11:06.330
<v Speaker 5>that their, their team could manually
analyze at the time.

168
00:11:07.169 --> 00:11:12.890
<v Speaker 5>Uh, and very quickly that same team went
from 100 to being able to monitor 2000

169
00:11:12.890 --> 00:11:18.739
<v Speaker 5>assets, um, using that same team, using
our technology around, uh, using AI to do

170
00:11:18.739 --> 00:11:21.690
<v Speaker 5>that analysis for them and using that
connectivity.

171
00:11:22.599 --> 00:11:26.679
<v Speaker 5>On the, on the complete vice versa, and
actually one with our our watch is that one

172
00:11:26.679 --> 00:11:31.520
<v Speaker 5>customer who would traditionally never
have been able to do anything IOT was able to

173
00:11:31.520 --> 00:11:37.340
<v Speaker 5>have a kind of a low cost solution in that
scenario to be able to monitor their,

174
00:11:37.440 --> 00:11:38.229
<v Speaker 5>their equipment.

175
00:11:38.969 --> 00:11:44.820
<v Speaker 5>Um, which, you know, for them that the
their downtime didn't cost significant

176
00:11:44.820 --> 00:11:48.460
<v Speaker 5>amounts compared to say a large
corporation, but it's still, you know, impacting

177
00:11:48.460 --> 00:11:49.080
<v Speaker 5>their bottom line.

178
00:11:50.109 --> 00:11:53.750
<v Speaker 5>And being able to use something that was
quick, easy to install, and get data

179
00:11:53.750 --> 00:11:58.830
<v Speaker 5>flowing immediately meant that they could
start to turn that return on investment

180
00:11:58.830 --> 00:11:59.289
<v Speaker 5>quickly.

181
00:12:00.900 --> 00:12:02.900
<v Niall Sullivan>And that that's a really interesting
point, Chris.

182
00:12:03.000 --> 00:12:07.219
<v Niall Sullivan>I mean, how, how recent has that been in
your eyes, you know, this sort of shift to,

183
00:12:07.369 --> 00:12:10.820
<v Niall Sullivan>you know, the, let's say the smaller
customers being able to access these kind of

184
00:12:10.820 --> 00:12:11.299
<v Niall Sullivan>tools.

185
00:12:11.570 --> 00:12:15.609
<v Niall Sullivan>Now, is that in the past year or the past
2 years, or just get a gauge on the

186
00:12:15.609 --> 00:12:16.239
<v Niall Sullivan>timeline?

187
00:12:16.739 --> 00:12:16.820
<v Niall Sullivan>Yeah,

188
00:12:16.900 --> 00:12:21.419
<v Speaker 5>I think I would say probably in the past
couple of years and particularly with the

189
00:12:21.419 --> 00:12:24.419
<v Speaker 5>increase of standardization in the, in the
market as well.

190
00:12:24.580 --> 00:12:28.080
<v Speaker 5>Uh, you know, when I first started
deploying Sensai, it was very much.

191
00:12:28.719 --> 00:12:33.940
<v Speaker 5>There was a lot of unknowns around how do
we get masses of data from machines up to

192
00:12:34.080 --> 00:12:37.919
<v Speaker 5>the cloud, you know, there was lots like
small different methods and people having

193
00:12:37.919 --> 00:12:39.119
<v Speaker 5>to hack things together.

194
00:12:39.840 --> 00:12:44.159
<v Speaker 5>Now because the market's matured quite
significantly, we have, you know, there are

195
00:12:44.159 --> 00:12:49.190
<v Speaker 5>many options and standards available that
we can then effectively standardize on,

196
00:12:49.390 --> 00:12:52.400
<v Speaker 5>and that standardization can really drive
down those costs.

197
00:12:52.520 --> 00:12:57.359
<v Speaker 5>So I would very much say in the past 2-3
years we've started to see an increase in

198
00:12:57.359 --> 00:12:58.359
<v Speaker 5>those kind of customers.

199
00:12:59.969 --> 00:13:02.280
<v Niall Sullivan>And I guess another, another angle on this
as well.

200
00:13:02.359 --> 00:13:06.830
<v Niall Sullivan>So we're saying it's, um, it's adoption
from maybe a smaller end of the market, but

201
00:13:07.530 --> 00:13:10.590
<v Niall Sullivan>I'd also like to sort of explore which
industries are sort of, are we seeing

202
00:13:10.840 --> 00:13:11.969
<v Niall Sullivan>adoption sort of growing as well.

203
00:13:12.039 --> 00:13:14.809
<v Niall Sullivan>So maybe Ingal, you could lead us into
that from your experience, where, where are

204
00:13:14.809 --> 00:13:16.780
<v Niall Sullivan>we seeing sort of big growth in this sort
of technology?

205
00:13:17.250 --> 00:13:23.719
<v Inger Eriksson>Yeah, so at our end, uh, we don't see any
specific differences between industries

206
00:13:23.719 --> 00:13:24.409
<v Inger Eriksson>and segments.

207
00:13:25.049 --> 00:13:30.960
<v Inger Eriksson>However, what we do see is a higher
adoption rate when decision makers are younger.

208
00:13:31.380 --> 00:13:34.919
<v Inger Eriksson>And I think it's simply because younger
people have grown up with the internet and

209
00:13:34.919 --> 00:13:41.510
<v Inger Eriksson>smartphones, and they expect the day to
day tools at work to have Simplicity and use

210
00:13:41.510 --> 00:13:45.979
<v Inger Eriksson>the latest technology in a smart way,
using AI like Sensai is doing, that's what

211
00:13:47.010 --> 00:13:49.330
<v Inger Eriksson>People at a younger age will expect.

212
00:13:50.099 --> 00:13:54.179
<v Inger Eriksson>And then, a difference between, another
difference between companies where you

213
00:13:54.179 --> 00:14:00.260
<v Inger Eriksson>succeed and not succeed or you can scale
faster is the com the company culture need

214
00:14:00.260 --> 00:14:04.780
<v Inger Eriksson>to promote curiosity, innovation, and
reward people that really want to do things

215
00:14:04.780 --> 00:14:05.239
<v Inger Eriksson>better.

216
00:14:05.739 --> 00:14:10.690
<v Inger Eriksson>So, so that's very helpful to scale IOT
solutions, predictive maintenance more

217
00:14:10.690 --> 00:14:11.619
<v Inger Eriksson>rapidly.

218
00:14:12.849 --> 00:14:15.289
<v Niall Sullivan>Yeah, it's, it's an interesting point as
well, I guess from our point of view,

219
00:14:15.419 --> 00:14:18.320
<v Niall Sullivan>Chris, from a Sen our perspective, it's
sort of the, I mean, the, the platform's

220
00:14:18.320 --> 00:14:21.169
<v Niall Sullivan>always been built to be agnostic to any
particular industry.

221
00:14:21.219 --> 00:14:23.159
<v Niall Sullivan>That's sort of part of the point, right?

222
00:14:23.219 --> 00:14:26.380
<v Niall Sullivan>But is there any, any particular
industries that stand out to you from your

223
00:14:26.380 --> 00:14:26.760
<v Niall Sullivan>experience?

224
00:14:28.309 --> 00:14:34.789
<v Speaker 5>Well, what I, what I find interesting is
that, for example, heavy industry and

225
00:14:34.789 --> 00:14:39.549
<v Speaker 5>FMCG are two of our kind of more or bigger
markets, as it were.

226
00:14:40.030 --> 00:14:44.270
<v Speaker 5>But from a fundamental perspective, they
couldn't be, you know, they're quite

227
00:14:44.270 --> 00:14:48.609
<v Speaker 5>different in terms of the, the scale of
equipment that they're using, the cost of

228
00:14:48.609 --> 00:14:52.030
<v Speaker 5>downtime that they have, the type of labor
they have, etc.

229
00:14:52.409 --> 00:14:55.000
<v Speaker 5>That, you know, they're polar opposites in
many ways.

230
00:14:55.289 --> 00:14:59.150
<v Speaker 5>And yet we see quite a lot of adoption in
both of those markets.

231
00:14:59.650 --> 00:15:04.809
<v Speaker 5>And to Inga's point, I think a lot of that
is driven not by segment necessarily.

232
00:15:04.849 --> 00:15:10.369
<v Speaker 5>I think the segment may influence who you
find there, but it's, it's a lot about the

233
00:15:10.369 --> 00:15:14.239
<v Speaker 5>company culture and those, those who
you're speaking to, you know, those who are

234
00:15:14.239 --> 00:15:18.799
<v Speaker 5>willing to try, try new technology, and,
but also have the vision to be able to

235
00:15:18.799 --> 00:15:20.650
<v Speaker 5>scale that to, um.

236
00:15:21.719 --> 00:15:22.940
<v Speaker 5>You know, a wider audience.

237
00:15:23.479 --> 00:15:27.679
<v Speaker 5>Interestingly, one of our most successful
customers, um, the, the, the scale, you

238
00:15:27.679 --> 00:15:32.109
<v Speaker 5>know, the adoption and the scaling of that
was driven massively by, um, kind of

239
00:15:32.109 --> 00:15:37.000
<v Speaker 5>internal competition within between
factories of wanting to be the most advanced,

240
00:15:37.039 --> 00:15:40.280
<v Speaker 5>the most, uh, you know, getting those cost
savings.

241
00:15:40.359 --> 00:15:45.039
<v Speaker 5>So when, when one, when one site certainly
sees lots of success with IOT or, you

242
00:15:45.039 --> 00:15:46.940
<v Speaker 5>know, and Sensi specifically in this case.

243
00:15:47.840 --> 00:15:51.280
<v Speaker 5>The other sites very quickly go, no, I
want that and I want that now because

244
00:15:51.289 --> 00:15:54.239
<v Speaker 5>they're, you know, they're doing it, so we
need to get, we need to do it and we need

245
00:15:54.239 --> 00:15:56.520
<v Speaker 5>to do it bigger and better, so.

246
00:15:57.299 --> 00:16:00.280
<v Niall Sullivan>Nothing, nothing wrong with a bit of
internal competition, that's what we say.

247
00:16:00.950 --> 00:16:01.090
<v Niall Sullivan>So

248
00:16:01.330 --> 00:16:05.359
<v Speaker 5>as long as they're willing to share, that,
that's the, uh, oh, exactly, exactly,

249
00:16:05.900 --> 00:16:06.179
<v Niall Sullivan>exactly.

250
00:16:06.419 --> 00:16:09.619
<v Niall Sullivan>And, and I guess what's interesting about
that, that, that particular example as

251
00:16:09.619 --> 00:16:13.159
<v Niall Sullivan>well is they're clearly positioning
predictive maintenance as something that's

252
00:16:13.419 --> 00:16:18.539
<v Niall Sullivan>driving value within the organization
rather than what can quite often happen, or

253
00:16:18.539 --> 00:16:23.460
<v Niall Sullivan>maybe a, a, you know, in people's minds
is, oh, it's a, you know, it's a cost saving

254
00:16:23.460 --> 00:16:23.739
<v Niall Sullivan>tool.

255
00:16:23.859 --> 00:16:25.760
<v Niall Sullivan>I mean, would you go along with that as
well, Chris?

256
00:16:27.419 --> 00:16:34.049
<v Speaker 5>I would say in, in the initial scenarios
that, you know, that value is seen as kind

257
00:16:34.049 --> 00:16:35.159
<v Speaker 5>of cost saving.

258
00:16:36.270 --> 00:16:42.549
<v Speaker 5>Um, particularly a kind of pilot, pilot
phase where you know there's an uncertainty

259
00:16:42.549 --> 00:16:45.729
<v Speaker 5>from the customer's perspective, you know,
where, where are we gonna drive.

260
00:16:46.760 --> 00:16:48.359
<v Speaker 5>You know, value from this.

261
00:16:49.000 --> 00:16:52.929
<v Speaker 5>But actually the more our more mature
customers generally see it as much more kind

262
00:16:52.929 --> 00:16:57.789
<v Speaker 5>of a value add in terms of they can, you
know, that they go from having.

263
00:16:59.080 --> 00:17:03.489
<v Speaker 5>Machines that are quite, for lack of a
better word, dumb, you know, you have to go

264
00:17:03.489 --> 00:17:06.650
<v Speaker 5>keep asking them questions by going
measuring them manually, etc.

265
00:17:06.810 --> 00:17:12.250
<v Speaker 5>what's going on or pulling them apart to
assets that are suddenly intelligent, you

266
00:17:12.250 --> 00:17:16.369
<v Speaker 5>know, we, we give those assets a voice,
and now they can start to say their

267
00:17:16.369 --> 00:17:17.949
<v Speaker 5>potential challenges much earlier.

268
00:17:19.088 --> 00:17:22.409
<v Speaker 5>And that can help, you know, not only does
that help in the short term, avoiding

269
00:17:22.409 --> 00:17:26.958
<v Speaker 5>downtime, but you can, it can start to
impact planning about new equipment.

270
00:17:27.328 --> 00:17:31.889
<v Speaker 5>It can indicate, you know, you have much
more view and vision of what your bad

271
00:17:31.889 --> 00:17:37.548
<v Speaker 5>actors in a, in a factory and and mitigate
that appropriately for future, you know,

272
00:17:37.928 --> 00:17:41.448
<v Speaker 5>say build a new line, you can, you have
much more information about what works well,

273
00:17:41.568 --> 00:17:45.048
<v Speaker 5>what doesn't, but also for, you know,
future retrofits, etc.

274
00:17:45.208 --> 00:17:46.249
<v Speaker 5>where you need to focus.

275
00:17:46.979 --> 00:17:51.119
<v Speaker 5>And that, you know, that information that
you're now listening to on machines is

276
00:17:51.219 --> 00:17:55.170
<v Speaker 5>where a lot of that value is driven,
particularly as you can do it across a plant,

277
00:17:55.579 --> 00:17:57.500
<v Speaker 5>across several factories.

278
00:17:58.920 --> 00:18:00.069
<v Niall Sullivan>And yeah, that's interesting.

279
00:18:00.099 --> 00:18:04.689
<v Niall Sullivan>You, you, it takes into that area across
plants and across, across factories because

280
00:18:05.510 --> 00:18:08.859
<v Niall Sullivan>The, the next question's really going into
sort of the technical challenges around

281
00:18:08.859 --> 00:18:11.750
<v Niall Sullivan>that, you know, and the, and the, the
clues in the title, we're talking about

282
00:18:11.750 --> 00:18:12.949
<v Niall Sullivan>scalable, um.

283
00:18:13.420 --> 00:18:16.900
<v Niall Sullivan>Deployments here, um, so I guess in our
first one, what, what, what are the

284
00:18:16.900 --> 00:18:19.680
<v Niall Sullivan>technical challenges of, you know, scaling
industrial IT?

285
00:18:20.180 --> 00:18:20.300
<v Niall Sullivan>So,

286
00:18:20.500 --> 00:18:24.540
<v Inger Eriksson>so I want to start by saying that we do
our best to minimize technical challenges,

287
00:18:24.579 --> 00:18:29.050
<v Inger Eriksson>and I, I think one of the biggest benefits
with wireless industrial IoT sensors is

288
00:18:29.050 --> 00:18:33.699
<v Inger Eriksson>that they are easier and less costly to
install than traditional cable sensors, and

289
00:18:33.699 --> 00:18:38.540
<v Inger Eriksson>they require less technical expertise both
during installation, commissioning, and

290
00:18:38.540 --> 00:18:42.699
<v Inger Eriksson>actual use and understanding of the
measured sensor data that they provide.

291
00:18:44.069 --> 00:18:48.489
<v Inger Eriksson>But when it comes to challenges, it's
more, I think one of the challenges we see

292
00:18:49.069 --> 00:18:53.329
<v Inger Eriksson>coming back is, is the corporate
guidelines that can be a challenge.

293
00:18:54.079 --> 00:19:00.489
<v Inger Eriksson>Um, and there can be guidelines that were
written 1015 years ago without IoT and

294
00:19:00.489 --> 00:19:01.900
<v Inger Eriksson>cloud solutions in mind.

295
00:19:02.329 --> 00:19:05.550
<v Inger Eriksson>So they give limitations that are not
really necessary.

296
00:19:06.089 --> 00:19:10.410
<v Inger Eriksson>And as, as an example, some companies
might have guidelines that prevent any data

297
00:19:10.410 --> 00:19:12.510
<v Inger Eriksson>from production being connected to the
internet.

298
00:19:13.400 --> 00:19:17.420
<v Inger Eriksson>And that makes a lot of sense when the
guidelines are written.

299
00:19:18.959 --> 00:19:22.920
<v Inger Eriksson>When the, the guidelines were written
because it was assumed that this would require

300
00:19:22.920 --> 00:19:25.849
<v Inger Eriksson>the entire production control system to be
connected to the internet.

301
00:19:26.229 --> 00:19:28.979
<v Inger Eriksson>But that's not what happens with an IoT
sensor.

302
00:19:29.160 --> 00:19:34.760
<v Inger Eriksson>Uh, you get internet connected only on the
sensors you install, and the data

303
00:19:34.760 --> 00:19:39.160
<v Inger Eriksson>collection system has no possibilities to
control, modify, or even see the data.

304
00:19:39.540 --> 00:19:43.060
<v Inger Eriksson>That can modify your production or collect
any sensitive production data.

305
00:19:43.410 --> 00:19:48.829
<v Inger Eriksson>So, that can be a hurdle uh with some
customers and, and they have to get through

306
00:19:48.829 --> 00:19:54.890
<v Inger Eriksson>that barrier and that understanding of
what this is when you send data to the cloud.

307
00:19:57.030 --> 00:20:01.400
<v Niall Sullivan>And I guess I, before I pass the question
over to Chris as well, just on the

308
00:20:01.400 --> 00:20:05.239
<v Niall Sullivan>security credential side, you know, how do
you overcome sort of those initial

309
00:20:05.239 --> 00:20:07.869
<v Niall Sullivan>questions about cloud and sending data to
the cloud, as you mentioned?

310
00:20:08.439 --> 00:20:14.260
<v Inger Eriksson>The most important thing is that our IoT
sensors are not going to connect into your

311
00:20:14.260 --> 00:20:15.209
<v Inger Eriksson>operational network.

312
00:20:15.560 --> 00:20:21.150
<v Inger Eriksson>So there's no path for any data you have
on your control system, on what you're

313
00:20:21.150 --> 00:20:25.000
<v Inger Eriksson>manufacturing, on any other data into the
IOT system.

314
00:20:25.079 --> 00:20:26.319
<v Inger Eriksson>So that's number one.

315
00:20:26.719 --> 00:20:32.040
<v Inger Eriksson>And then And the, the, the, the, the next
most important thing is that, yes, do we

316
00:20:32.040 --> 00:20:38.709
<v Inger Eriksson>have the security that is required to keep
Keep your data and, and

317
00:20:38.709 --> 00:20:40.729
<v Inger Eriksson>give only you access to your own data.

318
00:20:41.270 --> 00:20:44.250
<v Inger Eriksson>But that's really much less important than
the first step.

319
00:20:45.280 --> 00:20:49.920
<v Inger Eriksson>Because with that, with that first step,
there's no way an IoT sensor system can be

320
00:20:49.920 --> 00:20:51.390
<v Inger Eriksson>used to hack into your production line.

321
00:20:53.329 --> 00:20:55.500
<v Niall Sullivan>That's a, that's a good way to end that,
end that question.

322
00:20:55.739 --> 00:21:00.180
<v Niall Sullivan>And then, uh, on the predictive
maintenance side, Chris, what, what are those

323
00:21:00.180 --> 00:21:03.780
<v Niall Sullivan>challenges that you see when, when scaling
out and predicting maintenance

324
00:21:03.780 --> 00:21:04.420
<v Niall Sullivan>deployments?

325
00:21:05.300 --> 00:21:11.900
<v Speaker 5>Yeah, I think so because Sunai is a like
it's one platform you use one

326
00:21:12.130 --> 00:21:16.500
<v Speaker 5>tenant for your whole organization in
general, that's how we generally set it up

327
00:21:16.500 --> 00:21:21.810
<v Speaker 5>because then you can have cross learning
from different plants is that, uh, you,

328
00:21:21.900 --> 00:21:27.339
<v Speaker 5>you, you know, large multi-factory
organizations have standards.

329
00:21:28.369 --> 00:21:31.250
<v Speaker 5>Those standards indicate what kind of
equipment, etc.

330
00:21:31.479 --> 00:21:32.390
<v Speaker 5>that is used.

331
00:21:33.979 --> 00:21:38.849
<v Speaker 5>But what you tend to find is once you
start rolling out something like Sensai to

332
00:21:38.849 --> 00:21:42.530
<v Speaker 5>these standardized factories, you very
quickly find all the places where things are

333
00:21:42.530 --> 00:21:43.119
<v Speaker 5>non-standard.

334
00:21:43.449 --> 00:21:44.829
<v Speaker 5>It comes very quickly to light.

335
00:21:45.680 --> 00:21:49.839
<v Speaker 5>Uh, with the differences between, you
know, different plants, um.

336
00:21:50.599 --> 00:21:56.520
<v Speaker 5>And so being able to just kind of cookie
cut a solution from one place to another

337
00:21:56.520 --> 00:21:59.500
<v Speaker 5>is, is, is can be very challenging.

338
00:22:01.170 --> 00:22:04.900
<v Speaker 5>What, what we can do to mitigate that is,
well, first off, you have a platform that

339
00:22:04.900 --> 00:22:09.660
<v Speaker 5>is, that you can use anywhere, so OK, tick
that's the first part, and then it's

340
00:22:09.660 --> 00:22:10.839
<v Speaker 5>about looking for.

341
00:22:11.939 --> 00:22:16.680
<v Speaker 5>It's looking for the 80%, 20% rule where
you can find a sensing solution such as

342
00:22:16.959 --> 00:22:21.619
<v Speaker 5>AirWatch which can cover 80 to 90% of all
your use cases, you know, they have a wide

343
00:22:21.619 --> 00:22:24.699
<v Speaker 5>portfolio, so we could use this in most of
those cases.

344
00:22:25.880 --> 00:22:29.479
<v Speaker 5>Then maybe in those 5, 10% some way, maybe
you need to have a specialist equipment

345
00:22:29.479 --> 00:22:33.439
<v Speaker 5>or whatever it is because of what, but so
rather than throwing the baby out with the

346
00:22:33.439 --> 00:22:36.550
<v Speaker 5>bathwater and saying, oh, it's all
non-standard so we can never do anything

347
00:22:36.550 --> 00:22:36.949
<v Speaker 5>standard.

348
00:22:37.020 --> 00:22:39.540
<v Speaker 5>It's about going, OK, but we can bring.

349
00:22:40.579 --> 00:22:45.579
<v Speaker 5>A suite of products that can do the vast
majority of what you need to do and then,

350
00:22:45.699 --> 00:22:49.689
<v Speaker 5>and then we'll put the energy and the
focus into those few places we find where it

351
00:22:49.689 --> 00:22:51.219
<v Speaker 5>doesn't fit because of whatever reason.

352
00:22:52.660 --> 00:22:56.560
<v Niall Sullivan>And I guess what you're describing there,
Chris, is that sort of the key between

353
00:22:56.560 --> 00:23:00.849
<v Niall Sullivan>this interoperability between different
like legacy systems and diverse.

354
00:23:01.839 --> 00:23:05.560
<v Niall Sullivan>Systems not just used in in a plant or a
line or whatever, but, you know, across

355
00:23:05.560 --> 00:23:08.680
<v Niall Sullivan>plants as well in different sites, is that
what you're describing there sort of key

356
00:23:08.680 --> 00:23:09.020
<v Niall Sullivan>to that?

357
00:23:11.479 --> 00:23:12.599
<v Speaker 5>Yeah, I would say so.

358
00:23:12.750 --> 00:23:14.780
<v Speaker 5>And, you know, it's easy.

359
00:23:14.869 --> 00:23:19.750
<v Speaker 5>It's the ironic thing, it's easier with
new equipment to deal with that, but they're

360
00:23:19.750 --> 00:23:23.349
<v Speaker 5>also generally the equipment that doesn't
fail as often.

361
00:23:23.989 --> 00:23:27.849
<v Speaker 5>Um, and so when you're doing a, a, a pilot
deployment.

362
00:23:28.479 --> 00:23:32.560
<v Speaker 5>You can have the challenge of the easy
data to get may not be the most valuable data

363
00:23:32.560 --> 00:23:33.939
<v Speaker 5>to get because of more.

364
00:23:34.869 --> 00:23:36.640
<v Speaker 5>You know, all the legacy systems.

365
00:23:37.410 --> 00:23:42.130
<v Speaker 5>The way we get around that is we try and
use, you know, either we could, for

366
00:23:42.130 --> 00:23:48.209
<v Speaker 5>example, wireless sensors that kind of
completely bypass the, the need to go

367
00:23:48.209 --> 00:23:52.280
<v Speaker 5>connecting into the existing legacy
system, you know, if you put a sensor on, on a,

368
00:23:52.479 --> 00:23:53.550
<v Speaker 5>on a motor that is.

369
00:23:54.640 --> 00:23:58.160
<v Speaker 5>Completely isolated, then you don't have
the challenge of having to get into those

370
00:23:58.160 --> 00:23:59.180
<v Speaker 5>legacy systems.

371
00:24:00.199 --> 00:24:05.969
<v Speaker 5>And, and then for other scenarios where
you may need some of the, some other

372
00:24:05.969 --> 00:24:10.369
<v Speaker 5>operational data, then we, you know,
there's a, there's a suite of connectivity

373
00:24:10.369 --> 00:24:12.369
<v Speaker 5>products that are available that can
connect to those.

374
00:24:12.449 --> 00:24:17.270
<v Speaker 5>So whilst you come across legacy systems,
they generally have some sort of standard

375
00:24:17.530 --> 00:24:22.400
<v Speaker 5>somewhere that you can use like an OPCUA
or something along those lines.

376
00:24:22.770 --> 00:24:27.050
<v Speaker 5>It's about doing that exploration to find
those differences and then use what you

377
00:24:27.050 --> 00:24:28.530
<v Speaker 5>can that um.

378
00:24:29.109 --> 00:24:32.920
<v Speaker 5>That is already kind of scalable products,
scale what you can scale, I would

379
00:24:32.920 --> 00:24:33.260
<v Niall Sullivan>say.

380
00:24:34.699 --> 00:24:37.160
<v Niall Sullivan>Yeah, I was gonna bring it, yeah, and go,
sorry,

381
00:24:38.099 --> 00:24:40.520
<v Inger Eriksson>I just wanna add that, that, very often.

382
00:24:41.439 --> 00:24:45.880
<v Inger Eriksson>I think a lot of the listeners here
recognize that, that you have some production

383
00:24:45.880 --> 00:24:50.099
<v Inger Eriksson>lines that are very old, some equipment is
very old, you have some new equipment

384
00:24:50.969 --> 00:24:53.479
<v Inger Eriksson>that were, you did investment last year,
maybe.

385
00:24:54.760 --> 00:25:01.530
<v Inger Eriksson>And these production lines of these assets
have different capabilities, but IOT

386
00:25:01.530 --> 00:25:05.250
<v Inger Eriksson>sensors can help you standardize what
you're reading out of an old and a new

387
00:25:05.250 --> 00:25:05.930
<v Inger Eriksson>production line.

388
00:25:06.209 --> 00:25:11.849
<v Inger Eriksson>If you want to read current consumption or
vibration or temperature.

389
00:25:12.660 --> 00:25:16.089
<v Inger Eriksson>The IUT sensors don't care if it's a new
line or an old line.

390
00:25:16.140 --> 00:25:17.459
<v Inger Eriksson>It's, it's going to be the same thing.

391
00:25:17.699 --> 00:25:19.520
<v Inger Eriksson>So you get the same kind of data.

392
00:25:19.979 --> 00:25:25.890
<v Inger Eriksson>And then, On understanding the data is
true, as Chris, Chris says, there's probably

393
00:25:25.890 --> 00:25:31.160
<v Inger Eriksson>more stuff going on with older equipment,
even though all the new equipment, all the

394
00:25:31.160 --> 00:25:36.329
<v Inger Eriksson>new equipment has some, an introduction
phase where it can, where you can get uh

395
00:25:36.329 --> 00:25:37.150
<v Inger Eriksson>some failures.

396
00:25:38.819 --> 00:25:43.689
<v Niall Sullivan>Yeah, so, so you're saying, yeah, new, new
or old, in a way, in a way it's not, it's

397
00:25:43.689 --> 00:25:45.709
<v Niall Sullivan>maybe not the right thing to focus on too
much.

398
00:25:47.300 --> 00:25:52.479
<v Inger Eriksson>No So, I, I would say Sensori is much
bigger expert on this than me, but I, but

399
00:25:52.479 --> 00:25:57.270
<v Inger Eriksson>criticality analysis on where, what's your
equipment that you need to have up and

400
00:25:57.270 --> 00:26:00.900
<v Inger Eriksson>running and what are the consequences if
it fails.

401
00:26:01.160 --> 00:26:04.839
<v Inger Eriksson>That's number one, to decide where you
should go with predictive maintenance, not

402
00:26:05.160 --> 00:26:08.000
<v Inger Eriksson>the age of the equipment or what type of
equipment it is.

403
00:26:08.739 --> 00:26:12.250
<v Niall Sullivan>Yeah, I see Chris nodding here, but you
could.

404
00:26:14.150 --> 00:26:18.140
<v Speaker 5>Yes, there's no point if it's a brand new,
uh, let's say it's a, a piece of, not

405
00:26:18.140 --> 00:26:20.939
<v Speaker 5>even brand new equipment, equipment that's
been running for 30 years has never

406
00:26:20.939 --> 00:26:21.910
<v Speaker 5>caused you a single problem.

407
00:26:22.030 --> 00:26:24.020
<v Speaker 5>Oh, but the data is really easy to get out
of it.

408
00:26:24.390 --> 00:26:25.939
<v Speaker 5>It's like, well, that's great.

409
00:26:26.150 --> 00:26:29.949
<v Speaker 5>That's great for stage two when you're,
you know, you, you're trying to roll out a

410
00:26:29.949 --> 00:26:31.959
<v Speaker 5>predictive maintenance strategy.

411
00:26:32.030 --> 00:26:35.949
<v Speaker 5>But if you're in that initial value
creation, it's not ideal.

412
00:26:38.260 --> 00:26:41.859
<v Niall Sullivan>And maybe this is a good point actually,
because what we wanted to do is, you know,

413
00:26:41.979 --> 00:26:46.300
<v Niall Sullivan>we talked about a few different examples
and, um, you know, some insights in various

414
00:26:46.300 --> 00:26:50.099
<v Niall Sullivan>different areas, but if what I want to do
now is do sort of an act something a bit

415
00:26:50.099 --> 00:26:54.380
<v Niall Sullivan>more, a real world example of flowing and
you're Egar, you're on the left side of my

416
00:26:54.380 --> 00:26:57.520
<v Niall Sullivan>screen, how it flows to the sensei on the
right side of the screen.

417
00:26:57.979 --> 00:27:00.400
<v Niall Sullivan>Um, so if we start from your side.

418
00:27:01.239 --> 00:27:04.959
<v Niall Sullivan>In in terms of data collection, maybe even
installation of sensors, I mean, you

419
00:27:04.959 --> 00:27:07.489
<v Niall Sullivan>could even go to that point and then we'll
move over towards predictive maintenance,

420
00:27:07.569 --> 00:27:11.270
<v Niall Sullivan>just see how, how AirWatch and sensor
would work in a real world example.

421
00:27:12.089 --> 00:27:12.479
<v Inger Eriksson>Yeah.

422
00:27:12.689 --> 00:27:15.170
<v Inger Eriksson>So let me start, let me talk about the
data flow.

423
00:27:15.290 --> 00:27:19.599
<v Inger Eriksson>Uh, I think on the installation, it will
vary from sensor to sensor, and it's quite

424
00:27:19.599 --> 00:27:21.290
<v Inger Eriksson>obvious for most of them.

425
00:27:21.329 --> 00:27:25.390
<v Inger Eriksson>But all our IOT sensors, they will, they
will measure at regular intervals.

426
00:27:25.449 --> 00:27:27.770
<v Inger Eriksson>Um, and they have built-in smartness.

427
00:27:28.010 --> 00:27:31.449
<v Inger Eriksson>So they will transmit more data samples
when there are more interesting things

428
00:27:31.449 --> 00:27:33.819
<v Inger Eriksson>happening with the asset it's mounted on.

429
00:27:34.920 --> 00:27:41.890
<v Inger Eriksson>Um, and These data samples that it's
transmitting uh are transmitted wirelessly from

430
00:27:41.890 --> 00:27:44.069
<v Inger Eriksson>the sensor to a unit we call a gateway.

431
00:27:44.609 --> 00:27:47.199
<v Inger Eriksson>So the gateway is like a data collector.

432
00:27:48.119 --> 00:27:52.239
<v Inger Eriksson>It listens to all the sensors in its
surrounding and transmit these to the cloud.

433
00:27:52.650 --> 00:27:57.569
<v Inger Eriksson>And that will happen over a cellular or an
ethernet network.

434
00:27:58.489 --> 00:28:02.959
<v Inger Eriksson>And in the cloud, data is organized and
stored and available for any software to

435
00:28:02.959 --> 00:28:07.959
<v Inger Eriksson>use, and data communication is of course
encrypted and all data access requires

436
00:28:07.959 --> 00:28:10.609
<v Inger Eriksson>proper authentication to, to get access to
it.

437
00:28:11.410 --> 00:28:15.569
<v Inger Eriksson>And then other software can interact with
this data and consume this data in various

438
00:28:15.569 --> 00:28:17.530
<v Inger Eriksson>ways through API integration.

439
00:28:18.760 --> 00:28:22.569
<v Inger Eriksson>Of course, after it has been given the
right permissions by, by the user, by the

440
00:28:22.569 --> 00:28:28.250
<v Inger Eriksson>owner of the data, but, and we offer both
REST APIs with other software will get the

441
00:28:28.250 --> 00:28:33.579
<v Inger Eriksson>data set from, from one or more sensors
for, for the time frame requested, and webb

442
00:28:33.579 --> 00:28:38.209
<v Inger Eriksson>integration, where our cloud will provide
a data package to the users of the

443
00:28:38.209 --> 00:28:43.089
<v Inger Eriksson>software as soon as a, as a data, a new
measurement comes in to our cloud from, from

444
00:28:43.089 --> 00:28:43.869
<v Inger Eriksson>the sensors.

445
00:28:45.119 --> 00:28:50.060
<v Inger Eriksson>Um, and then sensor software that's using
the sensor data can in theory be anything.

446
00:28:50.199 --> 00:28:52.839
<v Inger Eriksson>Uh, you can write something new, some new
software to do it as well.

447
00:28:52.920 --> 00:28:57.920
<v Inger Eriksson>But most commonly, commonly, it will be
our app that gives you an overview of your

448
00:28:57.920 --> 00:28:59.890
<v Inger Eriksson>sensors and what they're measuring.

449
00:29:00.680 --> 00:29:05.219
<v Inger Eriksson>Uh, it can also be a data historian that
the customer already have and is using for

450
00:29:05.219 --> 00:29:11.119
<v Inger Eriksson>all this production data, or it can be a
software for further analysis like Sensai.

451
00:29:11.520 --> 00:29:15.800
<v Inger Eriksson>So maybe there, Chris, you can explain how
you did, what, what you're doing to deal

452
00:29:15.800 --> 00:29:18.079
<v Inger Eriksson>with the data and get actionable insight.

453
00:29:19.079 --> 00:29:19.420
<v Speaker 5>Hm.

454
00:29:20.550 --> 00:29:21.650
<v Speaker 5>So yeah, so.

455
00:29:23.280 --> 00:29:28.290
<v Speaker 5>So if we take the AirWatch cloud example,
um, it actually becomes relatively

456
00:29:28.290 --> 00:29:32.260
<v Speaker 5>straightforward for us because the data is
already, you know, left the shop shop

457
00:29:32.260 --> 00:29:35.930
<v Speaker 5>floor from the sensors, is in the cloud
available and as long as we have the right

458
00:29:35.930 --> 00:29:37.530
<v Speaker 5>credentials we can access it.

459
00:29:37.699 --> 00:29:39.729
<v Speaker 5>So there's a couple of ways that happens.

460
00:29:39.770 --> 00:29:45.890
<v Speaker 5>Either the data is pushed to our API from
the cloud, from the um neuron cloud, or we

461
00:29:45.890 --> 00:29:47.810
<v Speaker 5>go and pull that data from their API.

462
00:29:47.890 --> 00:29:48.849
<v Speaker 5>Both options are.

463
00:29:49.729 --> 00:29:50.500
<v Speaker 5>Available?

464
00:29:51.640 --> 00:29:55.880
<v Speaker 5>And at that point, we take that
information.

465
00:29:56.280 --> 00:29:58.719
<v Speaker 5>We may have other sources of information
as well.

466
00:29:59.119 --> 00:30:04.310
<v Speaker 5>So for example, maybe we have the, the
product that's being made at that given

467
00:30:04.310 --> 00:30:07.300
<v Speaker 5>point, and we don't need to know the exact
details of that product.

468
00:30:07.880 --> 00:30:10.239
<v Speaker 5>It could be just tell us it's bananas,
apples, oranges.

469
00:30:10.319 --> 00:30:12.910
<v Speaker 5>We don't really care from an analytics
perspective.

470
00:30:12.959 --> 00:30:14.020
<v Speaker 5>We just need to know it's different.

471
00:30:15.709 --> 00:30:22.670
<v Speaker 5>And we effectively build up a fingerprint
understanding of how that asset normally

472
00:30:22.670 --> 00:30:27.229
<v Speaker 5>operates, so we take into consideration
things like product type that it might be

473
00:30:27.229 --> 00:30:27.949
<v Speaker 5>manufacturing.

474
00:30:28.109 --> 00:30:32.300
<v Speaker 5>So you can think of a car press, for
example, if you're pressing different types of

475
00:30:32.300 --> 00:30:36.170
<v Speaker 5>body parts, that's going to impact the
vibration levels, etc.

476
00:30:37.599 --> 00:30:42.760
<v Speaker 5>Uh, we take the speed of the machine, we
can also take into account and you know

477
00:30:42.760 --> 00:30:46.719
<v Speaker 5>different off-state parameters as well, so
that we're, we're, you know, we don't

478
00:30:46.719 --> 00:30:49.760
<v Speaker 5>want to alert you just cos every time you
turn the machine off that's not

479
00:30:49.760 --> 00:30:50.459
<v Speaker 5>particularly helpful.

480
00:30:50.719 --> 00:30:52.939
<v Speaker 5>You know, so we take that into account in
our fingerprint.

481
00:30:54.180 --> 00:31:00.069
<v Speaker 5>And then we're effectively understanding
normal behavior automatically, so we

482
00:31:00.810 --> 00:31:06.530
<v Speaker 5>We get that data, we don't need any kind
of Input about what's good, what's bad, we

483
00:31:06.530 --> 00:31:12.130
<v Speaker 5>just understand what is normal at that
given point and then we look for changes from

484
00:31:12.130 --> 00:31:13.829
<v Speaker 5>that normal behavior going forward.

485
00:31:13.930 --> 00:31:16.479
<v Speaker 5>So rather than saying you're looking for a
threshold that we're going to breach,

486
00:31:16.609 --> 00:31:21.729
<v Speaker 5>we're much more like saying, oh this, this
current is trending up from 5 amps, and

487
00:31:21.729 --> 00:31:26.010
<v Speaker 5>it's been over the past 2 months, it's
gone up to about 89 amps, and here's the

488
00:31:26.010 --> 00:31:31.849
<v Speaker 5>trend and this, this, then what we do is
we take, use generative AI which has

489
00:31:31.849 --> 00:31:32.630
<v Speaker 5>knowledge of.

490
00:31:32.979 --> 00:31:36.130
<v Speaker 5>The asset that it's connected to, so maybe
a motor on a fan.

491
00:31:37.739 --> 00:31:40.780
<v Speaker 5>Uh, or the, the sensor on a motor on a fan
as it were.

492
00:31:41.800 --> 00:31:47.630
<v Speaker 5>So we have a generalized knowledge about
what that asset would be and we also read

493
00:31:47.630 --> 00:31:53.079
<v Speaker 5>previous cust kind of user feedback um
from the cases we generate, so our active

494
00:31:53.079 --> 00:31:53.859
<v Speaker 5>notification.

495
00:31:54.719 --> 00:31:57.520
<v Speaker 5>To hope to start to understand what that
problem might be.

496
00:31:57.719 --> 00:32:02.719
<v Speaker 5>So effectively what you'll see is a, we've
seen a, a rising current over the past

497
00:32:02.719 --> 00:32:06.160
<v Speaker 5>two months, uh, on this motor, on this
farm.

498
00:32:06.790 --> 00:32:11.800
<v Speaker 5>Based on previous experience you've found
that there's actually a looseness, uh, or

499
00:32:11.800 --> 00:32:15.359
<v Speaker 5>in fact a tight, probably more like
tightening of this current, but you know, there

500
00:32:15.359 --> 00:32:17.420
<v Speaker 5>seems to be something tightening in the
drive train.

501
00:32:18.260 --> 00:32:24.010
<v Speaker 5>You've seen this before on on a similar
bit of equipment, we suggest you go do and

502
00:32:24.010 --> 00:32:25.880
<v Speaker 5>then some suggestions of next steps.

503
00:32:27.849 --> 00:32:32.770
<v Niall Sullivan>And I, I guess, um, I see we're, we're
we're rapidly running out of time.

504
00:32:32.880 --> 00:32:36.689
<v Niall Sullivan>These things always go, always go so
quickly, so I wanna just, um, sort of wrap up

505
00:32:36.689 --> 00:32:37.449
<v Niall Sullivan>with a couple of questions.

506
00:32:37.530 --> 00:32:41.569
<v Niall Sullivan>But on the, you know, very well described
both ends of the process, I guess the

507
00:32:41.569 --> 00:32:46.050
<v Niall Sullivan>question for both of you is how you sort
of tailor the, the, you know, exactly what

508
00:32:46.050 --> 00:32:51.689
<v Niall Sullivan>you described to people on different sort
of stages of their sort of maturity, um,

509
00:32:51.890 --> 00:32:53.810
<v Niall Sullivan>as a customer, I guess, digital maturity.

510
00:32:53.859 --> 00:32:57.750
<v Niall Sullivan>So maybe Ingar, you could give, um, Bit of
insight from your perspective then,

511
00:32:57.839 --> 00:32:58.290
<v Niall Sullivan>Chris.

512
00:33:00.369 --> 00:33:07.079
<v Inger Eriksson>Yeah, maturity level for digital
transformation can be very different, um, but There

513
00:33:07.079 --> 00:33:12.119
<v Inger Eriksson>is, and there can be very different needs
in a processing plant that's running 24/7

514
00:33:12.119 --> 00:33:14.930
<v Inger Eriksson>and a local food producer with 10
employees.

515
00:33:15.439 --> 00:33:21.359
<v Inger Eriksson>But there's also a lot of common needs
between them in terms of IoT sensors that are

516
00:33:21.359 --> 00:33:23.500
<v Inger Eriksson>easy to install, use, and understand.

517
00:33:24.849 --> 00:33:27.040
<v Inger Eriksson>and software that can guide you.

518
00:33:27.369 --> 00:33:31.449
<v Inger Eriksson>Differences will be more, much more in
terms of what process needs to be in place to

519
00:33:31.449 --> 00:33:36.010
<v Inger Eriksson>get a larger maintenance team change their
work process compared to the smaller

520
00:33:36.010 --> 00:33:40.530
<v Inger Eriksson>companies we may, may only need one
technical responsible that needs to understand

521
00:33:40.770 --> 00:33:45.260
<v Inger Eriksson>how to act on the notifications from an IT
sensor or from a software.

522
00:33:46.060 --> 00:33:48.719
<v Inger Eriksson>So The tools are the same.

523
00:33:49.650 --> 00:33:54.010
<v Inger Eriksson>But predictive maintenance is more than
data and software.

524
00:33:54.050 --> 00:33:59.869
<v Inger Eriksson>It's also about changing process and
changing people behavior, and that is different

525
00:34:00.050 --> 00:34:04.310
<v Inger Eriksson>between the really big organizations and
the really small organizations.

526
00:34:05.890 --> 00:34:10.659
<v Niall Sullivan>Yeah, and, and from your perspective,
Chris, as well, would you sort of agree or

527
00:34:10.659 --> 00:34:12.810
<v Niall Sullivan>take, take on further what Ingall's
saying?

528
00:34:13.260 --> 00:34:17.790
<v Speaker 5>Yeah, so I would agree with what Ingall
says, and I would, what I would say in terms

529
00:34:17.790 --> 00:34:19.479
<v Speaker 5>of digital maturity is what.

530
00:34:20.330 --> 00:34:26.909
<v Speaker 5>Is the work you need to do around
architecture in terms of how mature they are.

531
00:34:27.799 --> 00:34:31.759
<v Speaker 5>Systems are in terms of where does that
data need to flow, what are their, I keep

532
00:34:31.759 --> 00:34:34.839
<v Speaker 5>saying standards today, I don't know if
that seems to be my flavor of today, but you

533
00:34:34.839 --> 00:34:39.799
<v Speaker 5>know, whatever their standard is for
connecting IOT equipment if they're, if they're

534
00:34:39.799 --> 00:34:44.948
<v Speaker 5>at that mature level and linking into
their existing systems, whereas for newer

535
00:34:44.948 --> 00:34:48.438
<v Speaker 5>customers on that journey, it's, it's more
about supporting them and understanding

536
00:34:48.438 --> 00:34:49.299
<v Speaker 5>what will be.

537
00:34:49.969 --> 00:34:54.330
<v Speaker 5>The scalable way to do that in the future
without, without losing the agility to get

538
00:34:54.330 --> 00:34:55.870
<v Speaker 5>to that value as soon as possible.

539
00:34:57.510 --> 00:35:01.429
<v Inger Eriksson>And I just want to add one thing, the only
companies we see that don't have enough

540
00:35:01.429 --> 00:35:05.479
<v Inger Eriksson>maturity to start to predictive
maintenance are companies that don't know what their

541
00:35:05.479 --> 00:35:06.459
<v Inger Eriksson>existing issues are.

542
00:35:06.840 --> 00:35:12.199
<v Inger Eriksson>So, so for this, we can help them
understand their up time and they need to analyze

543
00:35:12.199 --> 00:35:15.600
<v Inger Eriksson>the criticality of assets and production
lines before they can get started.

544
00:35:15.679 --> 00:35:19.860
<v Inger Eriksson>But with that knowledge, they can start a
route to predict amendments.

545
00:35:20.739 --> 00:35:22.320
<v Niall Sullivan>Yeah, and that, that's what I was about to
say as well.

546
00:35:22.379 --> 00:35:25.810
<v Niall Sullivan>So if you got, whatever stage you are at,
you know, you've got two fantastic

547
00:35:25.810 --> 00:35:29.620
<v Niall Sullivan>companies here, Siemens and Airwatch, who
can help guide you on that, on that

548
00:35:29.620 --> 00:35:32.719
<v Niall Sullivan>journey to wherever you, you know, where,
where you want to go as well.

549
00:35:33.060 --> 00:35:36.020
<v Niall Sullivan>Um, but I will end with one final question
because I know we've got some questions

550
00:35:36.020 --> 00:35:37.260
<v Niall Sullivan>we'd like to answer from the audience.

551
00:35:37.784 --> 00:35:42.304
<v Niall Sullivan>Um, it's really, it's to Ewing, guys, um,
um, looking from the, uh, you know, cos

552
00:35:42.304 --> 00:35:45.745
<v Niall Sullivan>we're from the Siemens side, but from your
perspective, just from your perspective

553
00:35:45.745 --> 00:35:49.544
<v Niall Sullivan>on the, um, on the Siemens Accelerator
platform, so your, your, you know, your

554
00:35:49.544 --> 00:35:53.504
<v Niall Sullivan>thoughts on it and just any advice for any
companies maybe watching or listening

555
00:35:53.504 --> 00:35:58.064
<v Niall Sullivan>today, um, who are thinking about joining
or wanting to join the accelerator

556
00:35:58.064 --> 00:35:58.344
<v Niall Sullivan>program.

557
00:35:59.110 --> 00:36:02.699
<v Inger Eriksson>Yeah, first, I want to say it's uh being
listed on the Siemens accelerator.

558
00:36:02.709 --> 00:36:06.820
<v Inger Eriksson>It's a great recognition of EldWatch, um,
and our industrial IT offering.

559
00:36:07.510 --> 00:36:12.090
<v Inger Eriksson>Uh, what it gives us is better exposure to
potential customers around the world.

560
00:36:12.469 --> 00:36:17.719
<v Inger Eriksson>And for industrial companies finding a
watch on the Siemens accelerators, it really

561
00:36:17.719 --> 00:36:23.189
<v Inger Eriksson>de-risks their implementation and
accelerate their decision makers, their decision

562
00:36:23.189 --> 00:36:27.550
<v Inger Eriksson>making, because basically, if Siemens says
it's good, I can trust it.

563
00:36:27.620 --> 00:36:31.290
<v Inger Eriksson>That's how we hope customers look at this.

564
00:36:32.290 --> 00:36:38.500
<v Inger Eriksson>And for other suppliers that want to go on
that platform or, or be listed there, be

565
00:36:38.500 --> 00:36:42.729
<v Inger Eriksson>aware this is not the Siemens accelerator
is not a pure marketing channel where you

566
00:36:42.729 --> 00:36:43.939
<v Inger Eriksson>can state whatever you want.

567
00:36:44.300 --> 00:36:48.209
<v Inger Eriksson>Siemens will review your product, make
sure documentation and support is available.

568
00:36:48.659 --> 00:36:53.919
<v Inger Eriksson>They will review thoroughly your data
security and the routines for updating

569
00:36:53.919 --> 00:36:54.899
<v Inger Eriksson>products and stuff like that.

570
00:36:55.020 --> 00:36:58.060
<v Inger Eriksson>So, so you must have this under control to
become listed.

571
00:36:59.639 --> 00:37:00.310
<v Niall Sullivan>Fantastic.

572
00:37:00.560 --> 00:37:03.080
<v Niall Sullivan>Fantastic, and a nice way to round off.

573
00:37:03.159 --> 00:37:07.399
<v Niall Sullivan>So, um, I'd like to thank you both, um,
for such a great interview and a really

574
00:37:07.399 --> 00:37:09.830
<v Niall Sullivan>interesting discussion, but I'm gonna hand
back to Fabrizio.

575
00:37:09.879 --> 00:37:13.300
<v Niall Sullivan>I know we've got some questions that have
come in, so over to you, Fabrizio.

576
00:37:14.040 --> 00:37:16.189
<v Speaker 3>Thanks so much, gentlemen, for the
insights.

577
00:37:16.639 --> 00:37:17.810
<v Speaker 3>And, uh, yeah.

578
00:37:18.199 --> 00:37:22.739
<v Speaker 3>So now, I have seen that there are a
couple of questions here in the, in the chat.

579
00:37:22.959 --> 00:37:27.760
<v Speaker 3>So I'm going to, to guide you through it
and, you know, feel free to pick up as you,

580
00:37:28.040 --> 00:37:29.120
<v Speaker 3>as you see also the fit.

581
00:37:29.580 --> 00:37:35.439
<v Speaker 3>So the very first one is, um, how long is
a typical sales cycle for joint sales

582
00:37:35.439 --> 00:37:37.459
<v Speaker 3>opportunities AirWatch and Siemens?

583
00:37:40.770 --> 00:37:41.050
<v Speaker 3>Whatever.

584
00:37:47.899 --> 00:37:54.729
<v Inger Eriksson>As a CEO of a, of a company scaling up, I
always think it goes,

585
00:37:54.780 --> 00:37:55.800
<v Inger Eriksson>it's too slow.

586
00:37:56.100 --> 00:37:59.649
<v Inger Eriksson>Uh, but it's really, it's, it's the
customer process that's slow.

587
00:37:59.699 --> 00:38:04.100
<v Inger Eriksson>I think that, the, the tools, both on the
software side and sensor side are

588
00:38:04.100 --> 00:38:04.340
<v Inger Eriksson>available.

589
00:38:04.419 --> 00:38:05.979
<v Inger Eriksson>It's getting the decisions done.

590
00:38:06.300 --> 00:38:11.100
<v Inger Eriksson>I think that's Consuming most of the time
in these processes.

591
00:38:12.570 --> 00:38:13.000
<v Inger Eriksson>Mhm.

592
00:38:13.330 --> 00:38:13.510
<v Inger Eriksson>Chris,

593
00:38:14.120 --> 00:38:15.949
<v Speaker 3>is that from your side, from your
perspective?

594
00:38:17.110 --> 00:38:24.070
<v Speaker 5>Yeah, so I think From my perspective, It,
it, it's not

595
00:38:24.070 --> 00:38:27.489
<v Speaker 5>like going and buying something off
Amazon, as it were.

596
00:38:28.330 --> 00:38:32.600
<v Speaker 5>As much as we, you know, we would love it
to be like that because so much of it is.

597
00:38:34.439 --> 00:38:40.219
<v Speaker 5>You're selling predictive maintenance is
much more about selling a vision about

598
00:38:40.719 --> 00:38:42.419
<v Speaker 5>change within an organization.

599
00:38:43.199 --> 00:38:49.120
<v Speaker 5>And it impacts so many different parties
such as IT, OT, maintenance, plant

600
00:38:49.120 --> 00:38:49.580
<v Speaker 5>management.

601
00:38:50.370 --> 00:38:53.810
<v Speaker 5>That actually that is a lot of people who
need to make decisions in order to go

602
00:38:53.810 --> 00:38:54.189
<v Speaker 5>ahead.

603
00:38:55.080 --> 00:38:57.300
<v Speaker 5>And so that does.

604
00:38:58.479 --> 00:39:02.729
<v Speaker 5>Add you know kind of add significant time,
as I said to the sales cycle.

605
00:39:03.080 --> 00:39:07.159
<v Speaker 5>So to give a straight answer, you know, it
can be we're talking in the months rather

606
00:39:07.159 --> 00:39:09.860
<v Speaker 5>than the weeks kind of scenario.

607
00:39:10.600 --> 00:39:14.560
<v Speaker 5>And I, I, as a, as someone who works in
delivery day in and day out, I'm always

608
00:39:14.560 --> 00:39:16.000
<v Speaker 5>looking for ways to speed things up.

609
00:39:16.239 --> 00:39:19.560
<v Speaker 5>Um, and so, you know, sometimes when I
look over the fence at the sales cycle, it's

610
00:39:19.560 --> 00:39:22.600
<v Speaker 5>always like, oh, if only we could do this
faster and that faster and change this,

611
00:39:22.679 --> 00:39:25.919
<v Speaker 5>but I haven't been given that job yet, uh.

612
00:39:26.939 --> 00:39:30.209
<v Speaker 5>Yeah, there's there's always that, but I
think with all these things.

613
00:39:31.290 --> 00:39:35.600
<v Speaker 5>The sales cycle, like any of this process,
can always be improved and sped up.

614
00:39:35.850 --> 00:39:38.909
<v Speaker 5>One day maybe we get to the point where
you just buy it with the click of a button,

615
00:39:39.750 --> 00:39:43.919
<v Speaker 5>um, because people are so confident that
they will, they will see that value, but

616
00:39:43.919 --> 00:39:45.350
<v Speaker 5>you know, it will take time.

617
00:39:46.209 --> 00:39:49.149
<v Inger Eriksson>And I want to add on IOT sensors,
predictive maintenance.

618
00:39:50.439 --> 00:39:56.989
<v Inger Eriksson>It is very rewarding, but maybe the longer
cycles to decide and get it operative at

619
00:39:56.989 --> 00:40:03.080
<v Inger Eriksson>the level you want compared to other IOT
use cases like monitoring energy

620
00:40:03.080 --> 00:40:08.479
<v Inger Eriksson>consumption or temperature or yeah, there
are simpler use cases with IOT than

621
00:40:08.479 --> 00:40:11.560
<v Inger Eriksson>predictive maintenance, but predictive
maintenance is very rewarding when you get it

622
00:40:11.560 --> 00:40:11.879
<v Inger Eriksson>right.

623
00:40:12.610 --> 00:40:13.169
<v Speaker 3>Mhm.

624
00:40:13.409 --> 00:40:13.889
<v Speaker 3>Perfect.

625
00:40:14.139 --> 00:40:15.050
<v Speaker 3>Thank you very much.

626
00:40:15.610 --> 00:40:20.530
<v Speaker 3>Uh, then we got another question on the,
um, on the role of the Siemens Accelerator

627
00:40:20.530 --> 00:40:21.949
<v Speaker 3>marketplace way forward.

628
00:40:22.489 --> 00:40:27.929
<v Speaker 3>So gentlemen, how do you think that, uh,
you know, especially our end customers will

629
00:40:27.929 --> 00:40:33.129
<v Speaker 3>leverage the, the newly established
Siemens accelerator marketplace?

630
00:40:35.290 --> 00:40:38.800
<v Speaker 5>I think from our perspective there's a,
there's a near term and a longer term

631
00:40:39.229 --> 00:40:39.699
<v Speaker 5>vision.

632
00:40:39.979 --> 00:40:44.219
<v Speaker 5>So that the nearer term is, as I mentioned
earlier, is very much about having that

633
00:40:44.219 --> 00:40:49.300
<v Speaker 5>visibility of who works with who, you
know, who, you know, which, which equipment or

634
00:40:49.300 --> 00:40:50.520
<v Speaker 5>in which sensors, etc.

635
00:40:50.659 --> 00:40:51.040
<v Speaker 5>have been.

636
00:40:52.270 --> 00:40:57.629
<v Speaker 5>Vetted as being high, you know, good
quality and can connect into our ecosystem.

637
00:40:57.750 --> 00:41:01.820
<v Speaker 5>So that gives you a much clearer vision
of, you know, whereas before it's very much

638
00:41:01.820 --> 00:41:04.100
<v Speaker 5>a case of, oh, which sensors can you
connect to?

639
00:41:04.110 --> 00:41:08.310
<v Speaker 5>And then, you know, that, that's all, you
know, that might be hidden in a in a

640
00:41:08.310 --> 00:41:11.989
<v Speaker 5>spreadsheet somewhere, but someone in
sales has to go look it up every time, you

641
00:41:11.989 --> 00:41:14.530
<v Speaker 5>know, there's much bigger visibility.

642
00:41:15.189 --> 00:41:20.030
<v Speaker 5>In the longer term, we're, we're always
exploring ways to improve the, the ability

643
00:41:20.030 --> 00:41:21.669
<v Speaker 5>to um transact.

644
00:41:21.989 --> 00:41:26.370
<v Speaker 5>So the, you know, the easier it is to
transact, the, the better it is for everybody.

645
00:41:26.909 --> 00:41:31.159
<v Speaker 5>You know, you can, you, you can take your
initial excitement with an organ in an

646
00:41:31.159 --> 00:41:34.709
<v Speaker 5>organization about doing something big
like predictive maintenance and get the ball

647
00:41:34.709 --> 00:41:35.989
<v Speaker 5>rolling as soon as possible.

648
00:41:36.199 --> 00:41:39.830
<v Speaker 5>So we have a, a longer term vision of
looking at how we make that more and more

649
00:41:39.830 --> 00:41:42.719
<v Speaker 5>seamless through something like the
accelerator marketplace.

650
00:41:43.729 --> 00:41:44.449
<v Speaker 3>Yeah, makes sense.

651
00:41:44.610 --> 00:41:44.939
<v Speaker 3>Inger.

652
00:41:45.010 --> 00:41:46.010
<v Speaker 3>What is your vision?

653
00:41:46.050 --> 00:41:48.969
<v Speaker 3>Do you want to share anything on the, on
the role of the Siemens accelerator

654
00:41:48.969 --> 00:41:49.530
<v Speaker 3>marketplace

655
00:41:49.530 --> 00:41:50.320
<v Inger Eriksson>for AirWatch?

656
00:41:50.449 --> 00:41:54.409
<v Inger Eriksson>I think I, I share many of the same views
as Chris Chris had there.

657
00:41:56.090 --> 00:41:56.870
<v Inger Eriksson>Yeah, perfect.

658
00:41:57.810 --> 00:41:58.389
<v Speaker 3>Good.

659
00:41:58.719 --> 00:42:05.419
<v Speaker 3>So, um, I see another, another great
question around,

660
00:42:05.439 --> 00:42:11.330
<v Speaker 3>uh, the role of, uh, SMEs, so small and
medium enterprises versus big enterprises.

661
00:42:12.179 --> 00:42:16.949
<v Speaker 3>So which customer groups do Sensai and
LWatch target?

662
00:42:19.969 --> 00:42:21.919
<v Speaker 3>I would say typically I would maybe add.

663
00:42:23.500 --> 00:42:26.489
<v Inger Eriksson>Edward targets both clear, clearly.

664
00:42:26.580 --> 00:42:33.439
<v Inger Eriksson>It's a clear strategy that If you're a
3-man operation, or if you're a large

665
00:42:33.439 --> 00:42:37.540
<v Inger Eriksson>international corporation, you should be
able to use our IUT sensors as tools.

666
00:42:38.870 --> 00:42:40.760
<v Inger Eriksson>Um, yeah.

667
00:42:41.649 --> 00:42:44.969
<v Inger Eriksson>They, they, they fit both and everything
in between.

668
00:42:45.750 --> 00:42:46.060
<v Speaker 3>Mhm.

669
00:42:48.110 --> 00:42:51.870
<v Speaker 3>Chris, from your perspective, what is your
experience or what would you say is the

670
00:42:51.870 --> 00:42:53.620
<v Speaker 3>trend from Sensi?

671
00:42:54.709 --> 00:43:01.629
<v Speaker 5>So I, I, I would say we have more of a
steer towards big enterprise simply

672
00:43:01.629 --> 00:43:06.270
<v Speaker 5>because our application is of a large
scalable nature, you know, we're, we're

673
00:43:06.270 --> 00:43:08.770
<v Speaker 5>talking tens of thousands of machines in
a, in a.

674
00:43:09.199 --> 00:43:12.939
<v Speaker 5>Organizations, so you're looking at
multiple sites in that scenario.

675
00:43:13.250 --> 00:43:17.610
<v Speaker 5>That doesn't mean that we neglect SMEs in
terms of, you know, we, we have some

676
00:43:17.610 --> 00:43:23.010
<v Speaker 5>customers where they are only one or two
sites, um, globally, um, and relatively

677
00:43:23.010 --> 00:43:23.870
<v Speaker 5>small sites.

678
00:43:24.639 --> 00:43:30.040
<v Speaker 5>And that's 2, well, 11 is my own personal
opinion, one is probably more the

679
00:43:30.040 --> 00:43:30.560
<v Speaker 5>corporate one.

680
00:43:30.600 --> 00:43:34.479
<v Speaker 5>In terms of personal opinion, you know,
people don't stay in jobs the same way they

681
00:43:34.479 --> 00:43:34.959
<v Speaker 5>used to.

682
00:43:35.320 --> 00:43:36.120
<v Speaker 5>So we should.

683
00:43:36.729 --> 00:43:40.969
<v Speaker 5>You know, people move between SMEs and
large corporations and vice versa, and we've

684
00:43:40.969 --> 00:43:45.550
<v Speaker 5>actually seen people leave big enterprise,
move to an SME and actually.

685
00:43:46.899 --> 00:43:50.780
<v Speaker 5>Take, you know, they said they were so
impressed with it at sense I there they

686
00:43:50.780 --> 00:43:55.780
<v Speaker 5>wanted to bring it into the small
organization and vice versa, people move from

687
00:43:55.780 --> 00:43:57.520
<v Speaker 5>small organizations to big, so.

688
00:43:58.719 --> 00:44:04.919
<v Speaker 5>We We, I would say that it would be
foolish of us from a personal perspective to

689
00:44:04.919 --> 00:44:07.080
<v Speaker 5>ignore those markets, um.

690
00:44:07.810 --> 00:44:12.850
<v Speaker 5>And also our technology is agnostic so we
can do at any scale as it were.

691
00:44:13.050 --> 00:44:18.649
<v Speaker 5>It just does tend to happen that because
of the nature of it, it fits better with

692
00:44:18.649 --> 00:44:19.389
<v Speaker 5>big enterprise.

693
00:44:21.120 --> 00:44:22.879
<v Speaker 3>Yeah, thank you so much.

694
00:44:23.280 --> 00:44:30.040
<v Speaker 3>Um, I just got the other question is
around, can you provide or share examples

695
00:44:30.040 --> 00:44:35.659
<v Speaker 3>of how generated alert looks like in
combination with Sensa AI reports.

696
00:44:39.889 --> 00:44:41.629
<v Speaker 3>Not sure, Chris, if it's um

697
00:44:42.260 --> 00:44:49.260
<v Speaker 5>uh that is a Probably not right now, um,
given the time, but I, we'd

698
00:44:49.260 --> 00:44:53.989
<v Speaker 5>be happy to do a demonstration of that in
a, in a follow-up call, um, if that person

699
00:44:53.989 --> 00:44:57.600
<v Speaker 5>wanted to reach out, be more than, you
know, it would take a little bit longer than

700
00:44:57.820 --> 00:44:58.959
<v Speaker 5>we have at this point.

701
00:44:59.479 --> 00:44:59.699
<v Speaker 3>Mhm.

702
00:45:00.260 --> 00:45:00.739
<v Speaker 3>Perfect.

703
00:45:01.919 --> 00:45:02.310
<v Speaker 3>Good.

704
00:45:02.689 --> 00:45:07.270
<v Speaker 3>Dan, I, uh, from my side, I would like to
thank, uh, thank you for the great

705
00:45:07.270 --> 00:45:09.399
<v Speaker 3>insights, Inger, Nia, and Chris.

706
00:45:09.479 --> 00:45:11.580
<v Speaker 3>Uh, it has been a pleasure to be your host
today.

707
00:45:11.959 --> 00:45:15.959
<v Speaker 3>And thank you very much also to the great
audience for participating live with us.

708
00:45:16.129 --> 00:45:21.639
<v Speaker 3>Um, if you have any further questions,
please feel free to post them here on the QA

709
00:45:21.639 --> 00:45:25.179
<v Speaker 3>tab, uh, and then, uh, we will get back to
you.

710
00:45:25.639 --> 00:45:30.699
<v Speaker 3>You can also always contact us and find
more information at Siemens.com.

711
00:45:31.209 --> 00:45:37.770
<v Speaker 3>And then, uh, please also take your time
now to also uh fill out, uh, a short, um, a

712
00:45:37.770 --> 00:45:43.330
<v Speaker 3>short survey, and, uh, yes, with that, I
hope you had a great time, uh, with us.

713
00:45:43.489 --> 00:45:44.489
<v Speaker 3>Uh, talk to you soon.

714
00:45:44.729 --> 00:45:46.020
<v Speaker 3>Goodbye and thank you much.

715
00:45:47.379 --> 00:45:47.939
<v Niall Sullivan>Thank you everyone.

716
00:45:50.290 --> 00:45:50.320
<v Speaker 3>Bye bye.

717
00:45:50.330 --> 00:45:50.699
<v Speaker 3>Thank you.

718
00:45:53.010 --> 00:45:57.969
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

719
00:45:57.969 --> 00:46:01.350
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.
