WEBVTT
Language: en-US

1
00:00:00.970 --> 00:00:05.840
<v Marco Saviano>But my, let's say personal take is that
would be definitely what should include a

2
00:00:05.840 --> 00:00:12.840
<v Marco Saviano>digital transformation of a company is to
shift culturally also towards the use

3
00:00:12.840 --> 00:00:17.420
<v Marco Saviano>of data, so leveraging the use of data,
getting all the information we can from them

4
00:00:17.639 --> 00:00:18.879
<v Marco Saviano>to create some business value.

5
00:00:19.079 --> 00:00:23.739
<v Marco Saviano>So it's not only I don't know, using Excel
instead of paper or something like that,

6
00:00:23.790 --> 00:00:29.469
<v Marco Saviano>that in my view is not really like a
digital company but is using the data to

7
00:00:29.469 --> 00:00:32.409
<v Marco Saviano>actually again get some benefit from it.

8
00:00:32.470 --> 00:00:38.630
<v Marco Saviano>Is it Less downtime on the shop floor or
is it just making a more efficient flow and

9
00:00:39.169 --> 00:00:42.060
<v Marco Saviano>let's say gaining time or money one way or
another?

10
00:00:42.569 --> 00:00:46.080
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens.

11
00:00:46.290 --> 00:00:48.250
<v Speaker 2>And now your host, Nel Sullivan.

12
00:00:49.560 --> 00:00:53.819
<v Niall Sullivan>Hello and welcome to the latest episode of
the trend detection podcast.

13
00:00:54.599 --> 00:00:58.040
<v Niall Sullivan>Uh, I'm really pleased to be joined today
uh by my colleague, Marco.

14
00:00:58.400 --> 00:01:02.560
<v Niall Sullivan>Um, I think it's his first time on the
podcast, Marco, so welcome, um, and I hope

15
00:01:02.560 --> 00:01:04.500
<v Niall Sullivan>you enjoy today's chat.

16
00:01:05.360 --> 00:01:06.239
<v Marco Saviano>Sure, thanks, Niall.

17
00:01:06.360 --> 00:01:07.599
<v Marco Saviano>Yeah, very happy to be here.

18
00:01:07.639 --> 00:01:08.559
<v Marco Saviano>Indeed, the first time.

19
00:01:08.750 --> 00:01:13.279
<v Marco Saviano>First time for me doing a podcast
actually, so, yeah, looking forward to, to see how

20
00:01:13.279 --> 00:01:15.279
<v Marco Saviano>I perform and how this goes on.

21
00:01:15.599 --> 00:01:18.599
<v Marco Saviano>I checked a couple of episodes, it's very
cool, so yeah, it's a privilege.

22
00:01:18.989 --> 00:01:20.750
<v Marco Saviano>And looking forward to share some
information.

23
00:01:21.550 --> 00:01:22.360
<v Niall Sullivan>Excellent, excellent.

24
00:01:22.389 --> 00:01:25.870
<v Niall Sullivan>And hopefully we don't scare you off from
doing future podcasts, um, we can only

25
00:01:25.870 --> 00:01:30.510
<v Niall Sullivan>hope, yeah, so no, no, welcome and thank
you, yeah, thank you for joining us, I

26
00:01:30.510 --> 00:01:30.910
<v Niall Sullivan>guess.

27
00:01:31.309 --> 00:01:35.050
<v Niall Sullivan>So today's episode, we're talking about,
um, again, a topic we haven't covered in

28
00:01:35.239 --> 00:01:40.790
<v Niall Sullivan>detail, um, but we're looking at sort of
SMEs and the challenges they face around

29
00:01:40.790 --> 00:01:44.309
<v Niall Sullivan>driving efficiency, which, of course, we
know is so important, um, you know,

30
00:01:44.510 --> 00:01:46.730
<v Niall Sullivan>especially when you think about resources
and.

31
00:01:47.190 --> 00:01:50.989
<v Niall Sullivan>You know, available to them, um, and we're
gonna talk about, you know, digital

32
00:01:50.989 --> 00:01:54.800
<v Niall Sullivan>transformation, how that can obviously
assist with that and some of the tools, and

33
00:01:54.800 --> 00:01:55.779
<v Niall Sullivan>that can assist around that.

34
00:01:55.949 --> 00:01:59.160
<v Niall Sullivan>But, um, but I guess before we get
started, Mark, it'd be great for the audience

35
00:01:59.160 --> 00:02:02.879
<v Niall Sullivan>just to understand who you are, a little
bit about your background and your current

36
00:02:02.879 --> 00:02:04.699
<v Niall Sullivan>role, um, in Siemens as well.

37
00:02:05.769 --> 00:02:06.529
<v Marco Saviano>Yeah, perfect.

38
00:02:06.690 --> 00:02:11.539
<v Marco Saviano>Then, yeah, probably how you already
guessed from my accent, if not from my name,

39
00:02:11.649 --> 00:02:15.720
<v Marco Saviano>I'm Italian, born and raised in Italy, in
Naples, so in the south of Italy.

40
00:02:16.250 --> 00:02:18.410
<v Marco Saviano>I also completed my study there.

41
00:02:18.490 --> 00:02:23.169
<v Marco Saviano>I'm an aerospace engineer, and yeah, after
that I started to move a bit around

42
00:02:23.169 --> 00:02:27.800
<v Marco Saviano>Europe, first being in the aerospace
field, then also shifting towards

43
00:02:27.800 --> 00:02:32.740
<v Marco Saviano>manufacturing, and now let's say in In
Siemens concretely taking over, let's say,

44
00:02:33.119 --> 00:02:37.960
<v Marco Saviano>predictive maintenance topics related to
our portfolio, so trying to support

45
00:02:37.960 --> 00:02:44.240
<v Marco Saviano>customers in deciding which tool is better
or better suited for which use case, and

46
00:02:44.240 --> 00:02:48.320
<v Marco Saviano>I'm based in Prague, so in the in the
middle of Europe, which is very good,

47
00:02:48.360 --> 00:02:53.160
<v Marco Saviano>I think, in terms of being able to reach
many customers easily because, yeah,

48
00:02:53.759 --> 00:02:58.759
<v Marco Saviano>everything is a couple of hours' flight
distance from here when we stay in the

49
00:02:58.759 --> 00:02:59.690
<v Marco Saviano>European, let's say.

50
00:03:00.089 --> 00:03:05.009
<v Marco Saviano>Background and of course we're supporting
also yeah outside of Europe when when it

51
00:03:05.009 --> 00:03:05.410
<v Marco Saviano>comes.

52
00:03:05.850 --> 00:03:09.509
<v Marco Saviano>So yeah, this is a bit of a of my
background.

53
00:03:09.809 --> 00:03:10.529
<v Marco Saviano>I speak Czech.

54
00:03:10.610 --> 00:03:14.929
<v Marco Saviano>That's a big advantage when based in
Prague because of course it's, it's a very

55
00:03:14.929 --> 00:03:19.929
<v Marco Saviano>difficult language, but my mother is from
here, so I have some, let's say, support

56
00:03:19.929 --> 00:03:22.710
<v Marco Saviano>already from when I was a child, and this
is helping me a lot.

57
00:03:23.369 --> 00:03:24.339
<v Marco Saviano>But yeah, this is.

58
00:03:24.839 --> 00:03:27.070
<v Marco Saviano>This is it in terms of uh Siemens's
career.

59
00:03:27.100 --> 00:03:31.360
<v Marco Saviano>I've been here for, for 2 years, more than
2 years now, and I think it's, uh, yeah,

60
00:03:31.440 --> 00:03:35.839
<v Marco Saviano>it's a very cool place to be, and I'm
loving this predictive maintenance topics,

61
00:03:35.919 --> 00:03:41.119
<v Marco Saviano>predictive like analytics, all the
supporting customers in driving their efficiency,

62
00:03:41.190 --> 00:03:43.240
<v Marco Saviano>optimizing their shop floor.

63
00:03:43.479 --> 00:03:47.279
<v Marco Saviano>So I hope, yeah, today we'll manage to, to
share some cool insights that will also

64
00:03:47.279 --> 00:03:50.839
<v Marco Saviano>help our customers or future customers to,
to get interested.

65
00:03:51.050 --> 00:03:53.000
<v Niall Sullivan>Yeah, no, fantastic, fantastic.

66
00:03:53.389 --> 00:03:56.710
<v Niall Sullivan>And, and because you, you mentioned, um,
your aerospace background, Marco, it might

67
00:03:56.710 --> 00:04:00.679
<v Niall Sullivan>be interesting, just as a side, you know,
as a side note, you know, so what, what

68
00:04:00.679 --> 00:04:04.360
<v Niall Sullivan>have you taken for that aerospace
background into your role today and, you know,

69
00:04:04.479 --> 00:04:05.320
<v Niall Sullivan>talking to customers?

70
00:04:05.399 --> 00:04:09.149
<v Niall Sullivan>What, you know, are there similarities or
are there, you know, big differences or

71
00:04:09.149 --> 00:04:12.320
<v Niall Sullivan>are there things that, you know, there's a
crossover between the two?

72
00:04:14.029 --> 00:04:20.140
<v Marco Saviano>Yeah, I would say it's not like core
things that would look like immediately being

73
00:04:20.140 --> 00:04:23.899
<v Marco Saviano>the same, but there are definitely some
aspects that would translate.

74
00:04:24.019 --> 00:04:30.459
<v Marco Saviano>I was working, for example, for a really
small turbojet engine manufacturer, so very

75
00:04:30.459 --> 00:04:34.100
<v Marco Saviano>different set up than Siemens, which is
possibly one of the largest companies in its

76
00:04:34.100 --> 00:04:40.059
<v Marco Saviano>domain, but When it comes to
digitalization and to predictive, let's say, again,

77
00:04:40.130 --> 00:04:44.779
<v Marco Saviano>analytics, maintenance, driving
efficiency, getting data from customers, they're

78
00:04:44.779 --> 00:04:50.339
<v Marco Saviano>often a bit, uh, scared maybe or afraid
of, they don't know exactly what's, what to

79
00:04:50.339 --> 00:04:53.579
<v Marco Saviano>expect, what this data will do, what, uh,
how it's working.

80
00:04:53.899 --> 00:04:57.980
<v Marco Saviano>And this is a bit something that I also
encountered on a different level in my

81
00:04:57.980 --> 00:05:02.040
<v Marco Saviano>previous role because not really knowing
maybe my company, they were a bit afraid of

82
00:05:02.380 --> 00:05:07.149
<v Marco Saviano>delivering such an important Yeah, piece
of their, let's say, tools like the engine.

83
00:05:07.209 --> 00:05:11.709
<v Marco Saviano>So if it was a drone or something, it's
like very, very relevant, let's say

84
00:05:11.709 --> 00:05:12.369
<v Marco Saviano>component.

85
00:05:12.709 --> 00:05:19.549
<v Marco Saviano>And so trying to understand where this,
let's say skeptical approach comes

86
00:05:19.549 --> 00:05:24.470
<v Marco Saviano>from because of again being a new topic or
being a new company and trying to find

87
00:05:24.470 --> 00:05:29.910
<v Marco Saviano>the points to make it easy for the
customers to understand why actually it's all

88
00:05:29.910 --> 00:05:35.279
<v Marco Saviano>actually safe and very, very good and
let's say in Possibly is the best move they

89
00:05:35.279 --> 00:05:35.769
<v Marco Saviano>can do.

90
00:05:36.119 --> 00:05:41.079
<v Marco Saviano>So I would say this in the digitalization
field, especially for SMEs where in some

91
00:05:41.079 --> 00:05:46.510
<v Marco Saviano>regions, then of course more than in
others, the Data topic is a bit, uh, crucial.

92
00:05:46.630 --> 00:05:51.500
<v Marco Saviano>So I think in this, I can find a sort of
parallel from the aerospace world, and, uh,

93
00:05:51.510 --> 00:05:56.890
<v Marco Saviano>yeah, I'm trying to, to use my experience
there to, to, yeah, also in this field.

94
00:05:58.579 --> 00:06:03.380
<v Niall Sullivan>Yeah, so I have a feeling data may come
up, um, again in, in our conversation today.

95
00:06:03.420 --> 00:06:06.859
<v Niall Sullivan>I have a, I have a feeling, but I guess
before we, we go into sort of the, the

96
00:06:06.859 --> 00:06:10.820
<v Niall Sullivan>details of, of that, I mean, maybe we
should start, it's quite a broad question,

97
00:06:10.899 --> 00:06:12.739
<v Niall Sullivan>but, you know, what is digital
transformation?

98
00:06:12.779 --> 00:06:17.380
<v Niall Sullivan>I guess we're, and maybe it's slightly
different, um, from an SME point of view

99
00:06:17.380 --> 00:06:21.660
<v Niall Sullivan>versus, you know, a large, larger
enterprise, but, um, so what does it mean to

100
00:06:21.660 --> 00:06:23.160
<v Niall Sullivan>actually be digital for an SME?

101
00:06:24.130 --> 00:06:29.429
<v Marco Saviano>Yeah, so that's, I think, a very, very
good question that probably many companies,

102
00:06:29.649 --> 00:06:35.130
<v Marco Saviano>including many SMEs, have asked themselves
many times over the years.

103
00:06:35.410 --> 00:06:40.190
<v Marco Saviano>First, I think, I don't know, 20 years
ago, it started with being using technology

104
00:06:40.190 --> 00:06:41.549
<v Marco Saviano>or IoT and so on.

105
00:06:41.649 --> 00:06:43.489
<v Marco Saviano>Now we're talking about digital.

106
00:06:44.459 --> 00:06:49.899
<v Marco Saviano>It's all very my opinion is that it's all
a very subjective thing because asking if

107
00:06:49.899 --> 00:06:53.649
<v Marco Saviano>the company if they are digital is a bit
like asking someone, are you happy?

108
00:06:53.859 --> 00:06:59.660
<v Marco Saviano>That's like, you know, there's various
shades to the answer to how even we just

109
00:06:59.660 --> 00:07:00.750
<v Marco Saviano>perceive ourselves.

110
00:07:01.100 --> 00:07:06.450
<v Marco Saviano>So I think it's a very broad topic and
needs to be developed much more, let's say,

111
00:07:06.459 --> 00:07:10.420
<v Marco Saviano>with many more questions following are you
digital to understand, let's say where we

112
00:07:10.420 --> 00:07:11.820
<v Marco Saviano>are and where we want to go.

113
00:07:12.359 --> 00:07:17.239
<v Marco Saviano>But my, let's say personal take is that
would be definitely what should include a

114
00:07:17.239 --> 00:07:24.079
<v Marco Saviano>digital transformation of the company is
to shift culturally also towards the

115
00:07:24.079 --> 00:07:28.399
<v Marco Saviano>users' data, so leveraging the use of
data, getting all the information we can from

116
00:07:28.399 --> 00:07:30.279
<v Marco Saviano>them to create some business value.

117
00:07:30.480 --> 00:07:35.130
<v Marco Saviano>So it's not only I don't know, using Excel
instead of paper or something like that,

118
00:07:35.220 --> 00:07:40.880
<v Marco Saviano>that, in my view, is not really like a
digital company, but it's using the data to

119
00:07:40.880 --> 00:07:43.769
<v Marco Saviano>actually, again, get some benefit from it.

120
00:07:43.850 --> 00:07:49.589
<v Marco Saviano>Is it less downtime on the shop floor or
is it just making a more efficient flow

121
00:07:49.589 --> 00:07:53.369
<v Marco Saviano>and, let's say, gaining time or money one
way or another?

122
00:07:55.470 --> 00:08:00.269
<v Niall Sullivan>You mentioned about, um, you know, the
shift culturally and required for digital

123
00:08:00.269 --> 00:08:01.049
<v Niall Sullivan>transformation.

124
00:08:01.510 --> 00:08:05.429
<v Niall Sullivan>And from your perspective, Marco, uh, do
you feel that SMEs are ready for that shift

125
00:08:05.429 --> 00:08:05.940
<v Niall Sullivan>at the moment?

126
00:08:06.109 --> 00:08:09.660
<v Niall Sullivan>And I know it's a broad statement, some
will be, some won't be, but what's your sort

127
00:08:09.660 --> 00:08:11.649
<v Niall Sullivan>of general feeling on that?

128
00:08:12.549 --> 00:08:18.519
<v Marco Saviano>I think that in general, let's say this
cultural shift, uh, needs to, to happen.

129
00:08:18.709 --> 00:08:24.059
<v Marco Saviano>So I think the SMEs and all the
enterprises, also the bigger ones, larger ones.

130
00:08:24.549 --> 00:08:29.910
<v Marco Saviano>When they're not ready, when their
management is not ready, this might slow them

131
00:08:29.910 --> 00:08:31.609
<v Marco Saviano>down a lot, especially in the years to
come.

132
00:08:32.309 --> 00:08:36.190
<v Marco Saviano>So I don't know if all are ready now, if
all are like.

133
00:08:37.039 --> 00:08:41.119
<v Marco Saviano>keen to start this, uh, journey, let's say
with Siemens or with some other, let's

134
00:08:41.119 --> 00:08:45.960
<v Marco Saviano>say partner, but definitely the ones that
are not, are not in a good position in my

135
00:08:45.960 --> 00:08:47.119
<v Marco Saviano>opinion for the years to come.

136
00:08:47.239 --> 00:08:48.979
<v Marco Saviano>So I think we see.

137
00:08:49.630 --> 00:08:55.830
<v Marco Saviano>Let's say an improvement in terms of
willingness to to explore this world more and

138
00:08:55.830 --> 00:09:00.619
<v Marco Saviano>more because of the, I would say obvious,
but maybe not so obvious when you're

139
00:09:00.619 --> 00:09:03.419
<v Marco Saviano>external to this world, benefits that come
with it.

140
00:09:03.830 --> 00:09:07.729
<v Marco Saviano>So we're on the right track, I would say,
even though not everyone is on board yet,

141
00:09:08.030 --> 00:09:08.590
<v Marco Saviano>they will join.

142
00:09:09.659 --> 00:09:13.780
<v Niall Sullivan>And how, I mean, if, if they're not sort
of in that mindset yet, and it's not an

143
00:09:13.780 --> 00:09:17.770
<v Niall Sullivan>easy, it's not, uh, you know, a simple
solution, it involves lots of different

144
00:09:17.770 --> 00:09:22.260
<v Niall Sullivan>things, but what, what, what should
organizations or SMEs sort of think about, you

145
00:09:22.260 --> 00:09:25.539
<v Niall Sullivan>know, if they want to, to make this shift,
but maybe there's some resistance

146
00:09:25.539 --> 00:09:29.539
<v Niall Sullivan>internally in various areas, different,
different departments.

147
00:09:30.169 --> 00:09:35.890
<v Marco Saviano>Yeah, that's definitely going to be the
case in many, in every organization, I would

148
00:09:35.890 --> 00:09:40.090
<v Marco Saviano>say again it can be large, small, if it's
small, even more because maybe there are

149
00:09:40.090 --> 00:09:40.469
<v Marco Saviano>more.

150
00:09:41.369 --> 00:09:46.729
<v Marco Saviano>Let's say people within a team that might
have just different experience coming from

151
00:09:46.729 --> 00:09:52.369
<v Marco Saviano>many years in the company knowing how to
do things and maybe being less prone to

152
00:09:52.369 --> 00:09:52.690
<v Marco Saviano>change.

153
00:09:52.729 --> 00:09:57.119
<v Marco Saviano>They might have leadership positions and
this might make it much harder for this

154
00:09:57.119 --> 00:10:02.510
<v Marco Saviano>cultural shift to happen, for example, and
I think this is A key element.

155
00:10:02.590 --> 00:10:08.469
<v Marco Saviano>So it's important, especially for an SME,
that even like leadership is very much

156
00:10:08.469 --> 00:10:13.630
<v Marco Saviano>engaged, very much involved to see how say
management puts emphasis, joining

157
00:10:13.630 --> 00:10:18.919
<v Marco Saviano>meetings, being present in decisions, so
that let's say the whole company is driven

158
00:10:18.919 --> 00:10:22.900
<v Marco Saviano>towards this shift which is again not
installing a software and hoping for the

159
00:10:22.900 --> 00:10:25.630
<v Marco Saviano>software to solve our problems or their
problems.

160
00:10:26.039 --> 00:10:32.359
<v Marco Saviano>is actually to, to be able to, to use the
insights that come from data and analytics

161
00:10:32.359 --> 00:10:37.349
<v Marco Saviano>to improve our daily life and our outcomes
in terms of products, services, whatever

162
00:10:37.349 --> 00:10:39.140
<v Marco Saviano>it is that we are delivering as a SME.

163
00:10:39.969 --> 00:10:44.359
<v Marco Saviano>So, I would say this is the key aspect,
you know, make it an IT project that there

164
00:10:44.359 --> 00:10:48.119
<v Marco Saviano>is a couple of enthusiasts that work on
it, and everyone else is just keeping their

165
00:10:48.119 --> 00:10:55.070
<v Marco Saviano>life as it is, while having management and
trainings and a whole series of Process

166
00:10:55.070 --> 00:11:00.950
<v Marco Saviano>changes basically that leverage the use of
these analytics and data that we let's

167
00:11:00.950 --> 00:11:01.489
<v Marco Saviano>say.

168
00:11:02.190 --> 00:11:08.719
<v Marco Saviano>Put into the system for everyone so that
the whole company can move further and go

169
00:11:08.719 --> 00:11:13.080
<v Marco Saviano>to the next level of efficiency
optimization and delivery of their outcome.

170
00:11:14.890 --> 00:11:19.559
<v Niall Sullivan>And so you, you mentioned that magic word
and data, which, um, we also referred to

171
00:11:19.559 --> 00:11:21.190
<v Niall Sullivan>at the, the start of the episode.

172
00:11:21.450 --> 00:11:25.690
<v Niall Sullivan>Um, and so, and, you know, I've, I've
spoken to many, you know, potential customers

173
00:11:25.690 --> 00:11:30.989
<v Niall Sullivan>and customers at events who talk about,
um, you know, collecting lots of data.

174
00:11:31.200 --> 00:11:34.849
<v Niall Sullivan>You know, no, you know, Industry 4.0 has
taught us that, you know, to collect lots

175
00:11:34.849 --> 00:11:37.340
<v Niall Sullivan>of data, but then they're not quite sure
what to do with it.

176
00:11:37.770 --> 00:11:41.809
<v Niall Sullivan>Um, so from an SME perspective, Mark,
where, where are they on this journey?

177
00:11:41.849 --> 00:11:43.190
<v Niall Sullivan>Are they collecting the data and.

178
00:11:43.809 --> 00:11:47.809
<v Niall Sullivan>Sort of trying to identify use cases or
are they not a lot of the time not

179
00:11:47.809 --> 00:11:52.200
<v Niall Sullivan>collecting the right data or the, the
amount of data required for digital

180
00:11:52.200 --> 00:11:52.890
<v Niall Sullivan>transformation?

181
00:11:53.690 --> 00:12:00.080
<v Marco Saviano>Yeah, so for SMEs, probably even exactly
even more, it's a very difficult topic to

182
00:12:00.080 --> 00:12:05.520
<v Marco Saviano>approach because the focus, the core
business they're focused on, it's possibly

183
00:12:05.520 --> 00:12:10.669
<v Marco Saviano>something completely different than data
evaluation or yeah, extrapolation, usage,

184
00:12:10.799 --> 00:12:11.380
<v Marco Saviano>whatever.

185
00:12:12.000 --> 00:12:15.159
<v Marco Saviano>So it's usually something completely new
they need to go through.

186
00:12:15.239 --> 00:12:20.229
<v Marco Saviano>They need to start, they need to find
expertise and possibly hire someone for that.

187
00:12:20.599 --> 00:12:26.309
<v Marco Saviano>So usually it's a very Difficult topic and
that's also why companies like Siemens

188
00:12:26.309 --> 00:12:31.280
<v Marco Saviano>Digital Enterprise Services and others are
there to, I would say.

189
00:12:32.140 --> 00:12:37.580
<v Marco Saviano>Help the customers start this journey,
understand where it should be pointing

190
00:12:37.580 --> 00:12:42.380
<v Marco Saviano>together so it's not just on our end, but
it's somehow understanding their

191
00:12:42.380 --> 00:12:46.940
<v Marco Saviano>processes, customer processes, and
including our expertise when it comes to digital

192
00:12:46.940 --> 00:12:51.049
<v Marco Saviano>transformation, trying to make the best
use of the data that they can get and

193
00:12:51.049 --> 00:12:56.219
<v Marco Saviano>possibly, of course, offering also the
best solutions that come because Again, one

194
00:12:56.219 --> 00:13:00.250
<v Marco Saviano>of the key points of leveraging this data
and having, say, the digital

195
00:13:00.250 --> 00:13:01.539
<v Marco Saviano>transformation and

196
00:13:01.539 --> 00:13:06.539
<v Marco Saviano>analytics is allowing customers to focus
even more on their core tasks.

197
00:13:06.700 --> 00:13:10.900
<v Marco Saviano>So in the moment they start focusing on
data, they are actually going in the

198
00:13:10.900 --> 00:13:11.700
<v Marco Saviano>opposite direction.

199
00:13:11.739 --> 00:13:16.409
<v Marco Saviano>They are not focusing on their core task,
and We found out that the best way for

200
00:13:16.409 --> 00:13:20.979
<v Marco Saviano>them to actually embrace the digital
transformation without getting lost is having

201
00:13:20.979 --> 00:13:26.200
<v Marco Saviano>an expert like Siemens supporting them
step by step together guiding towards the

202
00:13:26.200 --> 00:13:29.000
<v Marco Saviano>first outcome and then of course the next
outcome and so on.

203
00:13:29.049 --> 00:13:30.059
<v Marco Saviano>So it's always to be.

204
00:13:30.580 --> 00:13:34.049
<v Marco Saviano>Like the goal is always to be future
ready, in my opinion, because all the

205
00:13:34.049 --> 00:13:35.229
<v Marco Saviano>competitors will do the same.

206
00:13:35.349 --> 00:13:40.570
<v Marco Saviano>So the SMEs, as I said at the beginning,
that will not follow, will just like have a

207
00:13:40.570 --> 00:13:44.780
<v Marco Saviano>huge technology, let's say deficit at some
point that will be very, very hard to

208
00:13:44.780 --> 00:13:45.380
<v Marco Saviano>overcome.

209
00:13:45.820 --> 00:13:48.010
<v Marco Saviano>So the idea is to be always future ready.

210
00:13:48.099 --> 00:13:52.380
<v Marco Saviano>We never get there because, of course, the
future is always ahead, but that's a bit

211
00:13:52.380 --> 00:13:54.340
<v Marco Saviano>the mentality we should strive for.

212
00:13:55.940 --> 00:13:59.940
<v Niall Sullivan>And, and you mentioned sort of the support
on offer, and I guess support is, you

213
00:13:59.940 --> 00:14:03.820
<v Niall Sullivan>know, you know, crucial to SMEs when there
isn't sort of big, big resources

214
00:14:03.820 --> 00:14:08.260
<v Niall Sullivan>internally and, and people power
internally to, to draw on.

215
00:14:08.340 --> 00:14:12.739
<v Niall Sullivan>So, maybe we could touch upon, you know,
the types of support Siemens, you know,

216
00:14:12.820 --> 00:14:16.380
<v Niall Sullivan>offers, and, and I'll look beyond, you
know, sort of technology and software, but

217
00:14:16.380 --> 00:14:20.580
<v Niall Sullivan>actually, you know, like, you know, some
of the maintenance, you know, contracts and

218
00:14:20.830 --> 00:14:23.950
<v Niall Sullivan>And things like that, which, you know, can
encompass technology and, you know,

219
00:14:24.070 --> 00:14:26.489
<v Niall Sullivan>Siemens expertise, people, I mean, as
well.

220
00:14:27.820 --> 00:14:34.309
<v Marco Saviano>Yeah, it's so basically when we as Siemens
are with an SME and try

221
00:14:34.309 --> 00:14:39.900
<v Marco Saviano>to define, develop their Digitalization
journey trying to understand let's say

222
00:14:39.900 --> 00:14:41.390
<v Marco Saviano>what's their key.

223
00:14:42.570 --> 00:14:49.369
<v Marco Saviano>KPIs or key drivers that is pushing them
into the start of this journey we basically

224
00:14:49.369 --> 00:14:56.080
<v Marco Saviano>as Siemen support mainly I would say with
I don't know, like shop floor assets,

225
00:14:56.090 --> 00:15:02.710
<v Marco Saviano>optimization, efficiency of the processes
when it comes to shop floor maintenance,

226
00:15:02.729 --> 00:15:06.289
<v Marco Saviano>running, and these are the main, let's
say, areas.

227
00:15:07.369 --> 00:15:10.330
<v Marco Saviano>This might mean, of course, for example,
some predictive analytics.

228
00:15:10.409 --> 00:15:15.219
<v Marco Saviano>So we have data, we understand how a
machine is doing, some condition monitoring,

229
00:15:15.530 --> 00:15:21.210
<v Marco Saviano>and then we can also define if actually
maintenance is needed in 2 days or in 2

230
00:15:21.210 --> 00:15:22.840
<v Marco Saviano>weeks, which might help in.

231
00:15:23.429 --> 00:15:27.799
<v Marco Saviano>Planning also the maintenance activity,
the downtime, and reducing possibilities

232
00:15:27.799 --> 00:15:31.679
<v Marco Saviano>downtime to a phase where the machine
would not be running anyway because of a

233
00:15:31.679 --> 00:15:36.840
<v Marco Saviano>production gap or something, and this will
help us and the customer basically not

234
00:15:36.840 --> 00:15:40.640
<v Marco Saviano>waste time and resources when the machine
should be running or not.

235
00:15:40.760 --> 00:15:47.335
<v Marco Saviano>So this would be a typical use case asset
base, so trying to improve the Asset usage

236
00:15:47.335 --> 00:15:53.215
<v Marco Saviano>and efficiency of the usage, but we can
have also other kinds of effects, like for

237
00:15:53.215 --> 00:15:59.195
<v Marco Saviano>example, tracking how a machine is being
operated during various shifts, understand

238
00:15:59.195 --> 00:16:03.775
<v Marco Saviano>possibly employees that might need some
sort of training to do something better or

239
00:16:03.775 --> 00:16:08.815
<v Marco Saviano>some bad behaviors that just not need to
be stopped that are damaging the machine

240
00:16:08.815 --> 00:16:10.414
<v Marco Saviano>and yeah,

241
00:16:10.554 --> 00:16:16.590
<v Marco Saviano>somehow creating troubles and This, of
course, it's again according to the to the

242
00:16:16.590 --> 00:16:21.469
<v Marco Saviano>company, to the SMEs, to the size, to the
size of the maintenance team or the

243
00:16:21.469 --> 00:16:26.150
<v Marco Saviano>location as well, because we are also
helping a lot when companies are in remote

244
00:16:26.150 --> 00:16:28.390
<v Marco Saviano>areas, which might happen when it's about
production.

245
00:16:28.469 --> 00:16:30.510
<v Marco Saviano>We don't have them usually in city
centers.

246
00:16:30.909 --> 00:16:36.289
<v Marco Saviano>So in this direction, let's say having
digital tools that support and can offer

247
00:16:36.669 --> 00:16:41.630
<v Marco Saviano>support without having always too much
expertise and experts willing to be living

248
00:16:41.630 --> 00:16:43.630
<v Marco Saviano>maybe in a small village to work there.

249
00:16:44.070 --> 00:16:49.859
<v Marco Saviano>It is crucial and in this direction I
think we can then split into two trends.

250
00:16:49.869 --> 00:16:54.349
<v Marco Saviano>You mentioned the service contracts,
that's one side, for example, where we as

251
00:16:54.349 --> 00:17:00.950
<v Marco Saviano>Siemens can take over completely,
basically the monitoring and maintenance planning

252
00:17:00.950 --> 00:17:04.349
<v Marco Saviano>of the customer or the customer can use
our tools.

253
00:17:04.619 --> 00:17:10.009
<v Marco Saviano>To get all these data, read them through
some dashboarding and alarm systems, and

254
00:17:10.009 --> 00:17:13.659
<v Marco Saviano>then be themselves, let's say, managing
the maintenance operations.

255
00:17:13.779 --> 00:17:16.389
<v Marco Saviano>So this is much about the customer.

256
00:17:16.698 --> 00:17:19.499
<v Marco Saviano>Often it's about also the vertical they
are they are from.

257
00:17:19.698 --> 00:17:25.630
<v Marco Saviano>I can give some examples for example, this
is a good idea to just Show the

258
00:17:25.630 --> 00:17:26.030
<v Marco Saviano>difference.

259
00:17:26.150 --> 00:17:31.030
<v Marco Saviano>For example, we mentioned aerospace to
stay close to, let's say what was also my, my

260
00:17:31.030 --> 00:17:31.770
<v Marco Saviano>background before.

261
00:17:31.790 --> 00:17:37.109
<v Marco Saviano>And of course there, as I mentioned, data
are very critical because of course

262
00:17:37.109 --> 00:17:41.130
<v Marco Saviano>everything can be also defense oriented, a
strategic thing for, for the country, if

263
00:17:41.130 --> 00:17:46.430
<v Marco Saviano>not even just for the company, and they
are, for example, not too keen to share the

264
00:17:46.430 --> 00:17:52.020
<v Marco Saviano>data externally, but they are of course
keen to use the data for their advantage to

265
00:17:52.020 --> 00:17:53.069
<v Marco Saviano>improve in their processes.

266
00:17:53.270 --> 00:17:57.619
<v Marco Saviano>So what usually happens if we have a
service contract with these companies, they,

267
00:17:57.660 --> 00:18:01.800
<v Marco Saviano>for example, use a tool we have Brownfield
Analytics, for example.

268
00:18:01.880 --> 00:18:08.170
<v Marco Saviano>This is a tool that is analyzing the CNC
machines, understanding, let's say, where,

269
00:18:08.319 --> 00:18:13.449
<v Marco Saviano>what is happening at what time, where
something is going wrong, and the customer is

270
00:18:14.030 --> 00:18:15.310
<v Marco Saviano>using this tool by themselves.

271
00:18:15.540 --> 00:18:18.709
<v Marco Saviano>They just monitor everything, check, get
the alarms.

272
00:18:19.010 --> 00:18:23.650
<v Marco Saviano>And once they get them, they call us, so
they have a service contract, not for us to

273
00:18:23.650 --> 00:18:27.569
<v Marco Saviano>be the one taking care of the maintenance,
but for us to be always available so that

274
00:18:27.569 --> 00:18:31.209
<v Marco Saviano>when they detect something thanks to our
tool, we are there to support in the first

275
00:18:31.209 --> 00:18:35.410
<v Marco Saviano>line with some prioritization scheme
because of the service contract, and this is

276
00:18:35.410 --> 00:18:40.709
<v Marco Saviano>helping them keep their data private
because it's a requirement even maybe from

277
00:18:41.099 --> 00:18:46.709
<v Marco Saviano>bigger companies that they are, let's say
tier one supplier for, or Just to

278
00:18:46.709 --> 00:18:48.910
<v Marco Saviano>basically not have anyone else

279
00:18:48.910 --> 00:18:54.229
<v Marco Saviano>looking into the data, but being there,
we, we are there to support in every step

280
00:18:54.229 --> 00:18:58.010
<v Marco Saviano>that our digitalal are showing that is
needed to support.

281
00:19:00.430 --> 00:19:02.849
<v Niall Sullivan>And that's, yeah, thank you for sort of
taking us through that.

282
00:19:02.969 --> 00:19:06.770
<v Niall Sullivan>I mean, it just shows sort of the breadth
of options, which actually maybe someone

283
00:19:06.770 --> 00:19:09.109
<v Niall Sullivan>listening to this will think, oh wow, God,
that's overwhelming.

284
00:19:09.209 --> 00:19:13.369
<v Niall Sullivan>But the, the, but, but it is, you know, in
terms of the amount of options.

285
00:19:13.439 --> 00:19:15.930
<v Niall Sullivan>But I think the, the other key thing we've
been talking about, and it's been

286
00:19:15.930 --> 00:19:19.469
<v Niall Sullivan>mentioned in, in a few of your answers,
Marco, is about, you know, it's about

287
00:19:19.729 --> 00:19:22.229
<v Niall Sullivan>sitting down with the customer and
identifying what's right for them.

288
00:19:22.329 --> 00:19:26.170
<v Niall Sullivan>It's not about showing, here's all the
options, choose one, Mr.

289
00:19:26.180 --> 00:19:28.229
<v Niall Sullivan>Customer, but, you know, it's really
sitting down.

290
00:19:28.810 --> 00:19:32.280
<v Niall Sullivan>With them and understanding what's their
current situation, what are the current

291
00:19:32.280 --> 00:19:33.260
<v Niall Sullivan>problems they're addressing.

292
00:19:33.359 --> 00:19:36.709
<v Niall Sullivan>So, maybe you could talk about that sort
of initial stage, where it's like a

293
00:19:36.709 --> 00:19:39.680
<v Niall Sullivan>workshop stage, I don't, maybe you call it
something different, but, you know, that

294
00:19:39.680 --> 00:19:42.619
<v Niall Sullivan>kind of initial sit down with the customer
stage.

295
00:19:43.500 --> 00:19:48.500
<v Marco Saviano>Yeah, yeah, I know that that can be
definitely that's the key to success because I

296
00:19:48.500 --> 00:19:54.420
<v Marco Saviano>said at the beginning, often we see or
hear about digital transformation projects at

297
00:19:54.420 --> 00:20:00.540
<v Marco Saviano>any level, enterprises, more companies
failing or becoming, you know, a successful

298
00:20:00.540 --> 00:20:07.140
<v Marco Saviano>pilot that never gets implemented because
often we or our customers when they

299
00:20:07.140 --> 00:20:12.069
<v Marco Saviano>approach this thing, it's a completely new
thing, would go for the Easier place to

300
00:20:12.069 --> 00:20:13.430
<v Marco Saviano>implement adigi project,

301
00:20:13.510 --> 00:20:17.949
<v Marco Saviano>maybe something that is really
disconnected from the rest of the company processes

302
00:20:17.949 --> 00:20:23.189
<v Marco Saviano>so that even if it doesn't work perfectly,
the normal production is not affected and

303
00:20:23.189 --> 00:20:23.599
<v Marco Saviano>so on.

304
00:20:23.869 --> 00:20:25.849
<v Marco Saviano>And this of course is a bad start.

305
00:20:25.910 --> 00:20:30.449
<v Marco Saviano>It's already the start of roads to failure
because we are basically using

306
00:20:31.270 --> 00:20:34.160
<v Marco Saviano>Digitalization as the exact opposite of
what it should be.

307
00:20:34.239 --> 00:20:38.140
<v Marco Saviano>We try to relegate it to some corner that
we don't really look at.

308
00:20:38.400 --> 00:20:43.319
<v Marco Saviano>We don't see the benefits because it's not
key to our success, what we are

309
00:20:43.319 --> 00:20:44.130
<v Marco Saviano>monitoring.

310
00:20:44.560 --> 00:20:50.439
<v Marco Saviano>And so it is very, very crucial to, from
customer's side and from our side as

311
00:20:50.439 --> 00:20:57.079
<v Marco Saviano>Siemens to sit down, uh, again,
involvement involving as many leadership positions

312
00:20:57.079 --> 00:20:57.640
<v Marco Saviano>as needed.

313
00:20:58.000 --> 00:21:02.599
<v Marco Saviano>And I would say involving IT as soon as
possible because of course when we talk for

314
00:21:02.599 --> 00:21:06.599
<v Marco Saviano>example about maintenance, the first
contact would be a maintenance manager that

315
00:21:06.599 --> 00:21:11.520
<v Marco Saviano>might see the benefits of the tool, but we
need to have, I think, already at that

316
00:21:11.520 --> 00:21:16.290
<v Marco Saviano>point on board IT responsible to
understand the infrastructure the company already

317
00:21:16.290 --> 00:21:18.670
<v Marco Saviano>has, how Siemens tools can fit.

318
00:21:18.800 --> 00:21:24.040
<v Marco Saviano>Maybe some tools fit better than others if
it's cloud oriented, for example, or not,

319
00:21:24.310 --> 00:21:27.140
<v Marco Saviano>and again how they want to share data as I
shared, so.

320
00:21:27.699 --> 00:21:33.180
<v Marco Saviano>This initial stage is the key to lie down
what are the options, what are the

321
00:21:33.180 --> 00:21:37.939
<v Marco Saviano>available options for the customers based
also on the IT infrastructure they want to

322
00:21:37.939 --> 00:21:42.619
<v Marco Saviano>use or they're familiar with, or they're
just more allowed to use for some other

323
00:21:42.619 --> 00:21:43.229
<v Marco Saviano>reason.

324
00:21:43.540 --> 00:21:49.699
<v Marco Saviano>And of course then the, even if we want to
start with a pilot, which is of course, I

325
00:21:49.699 --> 00:21:54.260
<v Marco Saviano>mean a reasonable approach to see how
things work in some area and then develop

326
00:21:54.260 --> 00:21:54.640
<v Marco Saviano>further.

327
00:21:55.099 --> 00:22:01.500
<v Marco Saviano>It doesn't need to be done on an easier
setup base, but on a

328
00:22:01.500 --> 00:22:06.319
<v Marco Saviano>higher impact expected, so track the
asset, the department.

329
00:22:07.199 --> 00:22:12.680
<v Marco Saviano>The area of the shop floor that would, if
tracked properly, would give us the

330
00:22:12.680 --> 00:22:17.550
<v Marco Saviano>biggest benefits in terms of efficiency,
optimization, less downtimes.

331
00:22:18.000 --> 00:22:21.680
<v Marco Saviano>So I don't know if we have a machine that
is critical and we want to see if we can

332
00:22:21.680 --> 00:22:24.900
<v Marco Saviano>run it at a higher speed to have more
outputs, throughput.

333
00:22:25.680 --> 00:22:29.239
<v Marco Saviano>This would be, for example, a good example
rather than the one machine that we have

334
00:22:29.239 --> 00:22:33.979
<v Marco Saviano>as a backup that we actually don't care if
it even runs or not.

335
00:22:34.300 --> 00:22:39.729
<v Marco Saviano>So I think this is the crucial part at the
beginning defining infrastructure already

336
00:22:39.729 --> 00:22:45.530
<v Marco Saviano>early in the stage in the setup and
defining the key processes that can benefit from

337
00:22:45.530 --> 00:22:46.369
<v Marco Saviano>digitalization.

338
00:22:48.489 --> 00:22:53.050
<v Niall Sullivan>No, and that's, yeah, and you, you, you're
100% correct, that, that's crucial.

339
00:22:53.130 --> 00:22:57.589
<v Niall Sullivan>Um, and I guess the, the, the piece I'll
take out of that as well, there's often,

340
00:22:57.770 --> 00:23:01.089
<v Niall Sullivan>and maybe it's overlooked, you know, you
said the IT team as well.

341
00:23:01.209 --> 00:23:05.530
<v Niall Sullivan>I mean, it must be quite common for, um,
when you're talking to customers for lots

342
00:23:05.530 --> 00:23:08.479
<v Niall Sullivan>of discussions with maintenance teams and
everyone's excited and stuff, and all of a

343
00:23:08.479 --> 00:23:08.890
<v Niall Sullivan>sudden.

344
00:23:09.319 --> 00:23:13.589
<v Niall Sullivan>The IT team are brought in a little too
late into the conversation, cos that's,

345
00:23:13.760 --> 00:23:18.119
<v Niall Sullivan>that's another thing as well, it's the
timing of when to bring IT teams in, right?

346
00:23:18.170 --> 00:23:22.079
<v Niall Sullivan>It's not just about bringing them in, but
at the right time, not when it's gone so

347
00:23:22.079 --> 00:23:25.439
<v Niall Sullivan>far down the line, discussions have gone
on for a little while, wouldn't, wouldn't

348
00:23:25.439 --> 00:23:25.880
<v Niall Sullivan>you say?

349
00:23:26.569 --> 00:23:28.650
<v Marco Saviano>Yeah, I would definitely agree.

350
00:23:29.530 --> 00:23:36.530
<v Marco Saviano>I think there are 3 key stakeholders on
customer sides for when it comes to digital

351
00:23:36.530 --> 00:23:41.729
<v Marco Saviano>transformation projects that involve some
sort of optimization, especially in SMEs

352
00:23:41.729 --> 00:23:47.920
<v Marco Saviano>where maybe teams are also smaller in
terms of key experts being involved, so it's

353
00:23:47.920 --> 00:23:52.640
<v Marco Saviano>possibly easier to bring them to the
table, and it's crucial to do it and Again,

354
00:23:52.680 --> 00:23:56.280
<v Marco Saviano>it's leadership teams because we need to
have the commitment from the company

355
00:23:56.280 --> 00:23:59.349
<v Marco Saviano>because we are requiring the customer, at
least

356
00:23:59.349 --> 00:24:05.199
<v Marco Saviano>in some areas, to really start shifting
culturally on how they do some sort of tasks

357
00:24:05.199 --> 00:24:08.569
<v Marco Saviano>leveraging data and insights from
technology now.

358
00:24:09.199 --> 00:24:14.560
<v Marco Saviano>We need IT because It's crucial that we
often, very often hear also from our sales

359
00:24:14.560 --> 00:24:20.239
<v Marco Saviano>that just happen to be talking to one
person and get to the IT stage too late that

360
00:24:20.239 --> 00:24:22.420
<v Marco Saviano>we find, you know, the best solution.

361
00:24:22.489 --> 00:24:27.520
<v Marco Saviano>We monitor the right KPIs, the maintenance
managers, see the benefits that this

362
00:24:27.520 --> 00:24:32.760
<v Marco Saviano>whole solution would bring to them having
easier shifts and possibly or even not

363
00:24:32.760 --> 00:24:36.199
<v Marco Saviano>having to be present on the shop floor
during night hours or something like that.

364
00:24:36.550 --> 00:24:41.719
<v Marco Saviano>And then we switched to the IT part and
there is a complete like roadblock or

365
00:24:41.719 --> 00:24:46.709
<v Marco Saviano>stopper because of complete
incompatibility between the specific tool that was

366
00:24:46.709 --> 00:24:51.750
<v Marco Saviano>thought about and the IT infrastructure of
the company or again, requirements that

367
00:24:51.750 --> 00:24:55.869
<v Marco Saviano>might be coming also from regulations in
the country or so on.

368
00:24:55.949 --> 00:24:58.400
<v Marco Saviano>There are many aspects to be, let's say,
checked.

369
00:24:58.469 --> 00:25:05.290
<v Marco Saviano>So 100% IT is, I think, the main reason
why the project fails, and this is why, uh,

370
00:25:05.780 --> 00:25:11.339
<v Marco Saviano>IT should be involved in a digitalization
project, in a data-related project as soon

371
00:25:11.339 --> 00:25:12.040
<v Marco Saviano>as possible.

372
00:25:13.689 --> 00:25:15.780
<v Niall Sullivan>And, you know, and that's great.

373
00:25:15.859 --> 00:25:19.030
<v Niall Sullivan>Thank you for the sort of listing out
those, um, key stakeholder groups.

374
00:25:19.170 --> 00:25:21.739
<v Niall Sullivan>I mean, is it difficult, because everyone,
they all have sort of different

375
00:25:21.739 --> 00:25:22.060
<v Niall Sullivan>priorities.

376
00:25:22.099 --> 00:25:27.819
<v Niall Sullivan>Obviously, the one priority is a
successful growing business, but the, I guess, indi

377
00:25:27.819 --> 00:25:32.979
<v Niall Sullivan>individually in depart in per department,
they have their own sort of, um, Uh,

378
00:25:32.989 --> 00:25:36.790
<v Niall Sullivan>motivations, I guess, or, or viewpoints,
is it hard to sort of align those with the

379
00:25:36.790 --> 00:25:39.910
<v Niall Sullivan>overall sort of project goal for
digitalization?

380
00:25:40.719 --> 00:25:46.089
<v Marco Saviano>I think it's not hard to, let's say,
coordinate all of them.

381
00:25:46.130 --> 00:25:52.290
<v Marco Saviano>It's key again to, to have it clear from
the beginning which those points are and

382
00:25:52.290 --> 00:25:58.709
<v Marco Saviano>how to tackle them, let's say, define this
together, because often we, if we only

383
00:25:58.849 --> 00:26:03.699
<v Marco Saviano>check one side of the story, it's, uh,
it's easy to, it's obvious almost to neglect

384
00:26:03.699 --> 00:26:05.050
<v Marco Saviano>many others, so.

385
00:26:05.530 --> 00:26:12.410
<v Marco Saviano>Once again, the involvement of managers or
like leadership teams from

386
00:26:12.410 --> 00:26:18.800
<v Marco Saviano>um an SME especially that it might be even
a bit easier for this sort of, let's say,

387
00:26:18.810 --> 00:26:23.689
<v Marco Saviano>group of people to, to have a whole
understanding of how the whole company is

388
00:26:23.689 --> 00:26:28.750
<v Marco Saviano>working and uh let's say the various
departments' interests is, uh, makes it pretty,

389
00:26:28.930 --> 00:26:33.130
<v Marco Saviano>I would say, feasible or easy to, to
define the right steps.

390
00:26:33.500 --> 00:26:37.839
<v Marco Saviano>And again, when this is missing, this can
go wrong, but there is nothing

391
00:26:38.410 --> 00:26:44.060
<v Marco Saviano>incompatible between a team looking at
saving energy consumption because of some

392
00:26:44.060 --> 00:26:49.339
<v Marco Saviano>sustainability goal or regulations again
that the company needs to fit in in terms

393
00:26:49.339 --> 00:26:56.020
<v Marco Saviano>of emissions, for example, and trying to
have a more consistent operational

394
00:26:56.020 --> 00:26:58.979
<v Marco Saviano>mode between manpower or different shifts.

395
00:26:59.439 --> 00:27:02.489
<v Marco Saviano>Uh, reducing downtimes, this all goes hand
in hand.

396
00:27:02.650 --> 00:27:08.609
<v Marco Saviano>And of course, if we know from the start
of the discussions that we want to achieve

397
00:27:08.609 --> 00:27:12.930
<v Marco Saviano>all these topics, all these goals, uh,
it's easier to think about solutions that

398
00:27:12.930 --> 00:27:19.569
<v Marco Saviano>would mutually or just even one bigger
solution that could tackle all of this sort

399
00:27:19.569 --> 00:27:23.810
<v Marco Saviano>of problem rather than starting with just
one of them addressing and then see that

400
00:27:23.810 --> 00:27:26.670
<v Marco Saviano>maybe some of the solutions we implemented
are lacking.

401
00:27:27.180 --> 00:27:32.020
<v Marco Saviano>The right data, let's say analytics to, to
also take on some other points.

402
00:27:32.099 --> 00:27:36.560
<v Marco Saviano>So it's again crucial to have people in
SMEs.

403
00:27:36.579 --> 00:27:41.979
<v Marco Saviano>It's easier than in enterprises that are
really responsible for the whole company so

404
00:27:41.979 --> 00:27:44.180
<v Marco Saviano>that the projects benefit.

405
00:27:44.810 --> 00:27:49.689
<v Marco Saviano>A whole series of processes that are
critical for the company rather than just a

406
00:27:49.689 --> 00:27:50.390
<v Marco Saviano>small area.

407
00:27:51.849 --> 00:27:55.609
<v Marco Saviano>Already if we start with a pilot in a
small area, it's, it's fine, but if we have

408
00:27:55.609 --> 00:28:00.410
<v Marco Saviano>already the idea that if we expand we
touch many other points together with IT

409
00:28:00.410 --> 00:28:05.770
<v Marco Saviano>again, I cannot stress this enough, we,
yeah, we are on a good start, let's say, to

410
00:28:05.770 --> 00:28:06.329
<v Marco Saviano>succeed.

411
00:28:07.500 --> 00:28:08.800
<v Niall Sullivan>Excellent, excellent.

412
00:28:09.300 --> 00:28:12.739
<v Niall Sullivan>Um, and I, I wanted to sort of bring the
conversation around to, of course,

413
00:28:12.859 --> 00:28:17.619
<v Niall Sullivan>predictive maintenance and predictive
analytics, you know, which are a term you'd

414
00:28:17.619 --> 00:28:22.880
<v Niall Sullivan>like to use and, and sort of the adoption
of predictive maintenance within SMEs

415
00:28:23.459 --> 00:28:27.859
<v Niall Sullivan>because I guess from the outside in, some
may feel that, you know, oh no, it's for,

416
00:28:27.920 --> 00:28:32.339
<v Niall Sullivan>you know, big, big deployments, you know,
big scalable deployments for enterprises,

417
00:28:32.420 --> 00:28:36.530
<v Niall Sullivan>but of course, Um, and maybe it'd be good
for you to just sort of explain, Marco,

418
00:28:36.589 --> 00:28:38.979
<v Niall Sullivan>how SMEs could benefit from a sort of
predictive

419
00:28:38.979 --> 00:28:39.910
<v Niall Sullivan>maintenance approach.

420
00:28:41.510 --> 00:28:47.930
<v Marco Saviano>Yeah, so basically I mean it's definitely
a horizontal topic

421
00:28:47.930 --> 00:28:52.890
<v Marco Saviano>digitalization and predictive maintenance,
so it's not something that touches only,

422
00:28:52.930 --> 00:28:57.569
<v Marco Saviano>I don't know, specific verticals or
specific company sizes because what we are

423
00:28:57.569 --> 00:29:04.089
<v Marco Saviano>trying to achieve is always some
optimization efficiency in the core processes, and

424
00:29:04.089 --> 00:29:05.050
<v Marco Saviano>those can be.

425
00:29:05.640 --> 00:29:08.469
<v Marco Saviano>I mean, different and always relevant.

426
00:29:08.569 --> 00:29:14.400
<v Marco Saviano>This like optimizing a process is critical
in any sort of company, any size it is.

427
00:29:14.449 --> 00:29:20.770
<v Marco Saviano>So SMEs are definitely impacted and as for
bigger enterprises, but even more in

428
00:29:20.770 --> 00:29:27.410
<v Marco Saviano>SMEs, the Right digital and predictive
maintenance strategy might

429
00:29:27.410 --> 00:29:33.890
<v Marco Saviano>be a key differentiator compared to a a
competitor and bring, let's say, lead to the

430
00:29:33.890 --> 00:29:36.689
<v Marco Saviano>success to cut costs, improve throughput.

431
00:29:36.770 --> 00:29:42.849
<v Marco Saviano>So it's very, very, very important, and I
think they said it's not only about

432
00:29:43.819 --> 00:29:46.979
<v Marco Saviano>Strictly reducing the downtime, right,
that's like the idea of predictive

433
00:29:46.979 --> 00:29:47.410
<v Marco Saviano>maintenance.

434
00:29:47.459 --> 00:29:53.780
<v Marco Saviano>So instead of waiting for some problem to
materialize and reacting on that or

435
00:29:53.780 --> 00:29:59.380
<v Marco Saviano>preventively changing the oil every 5000
kilometers like on a car because we just

436
00:29:59.380 --> 00:30:06.339
<v Marco Saviano>know it's better, it's to actually Have an
idea at every moment in time of

437
00:30:06.339 --> 00:30:11.219
<v Marco Saviano>how the machine, the asset, the shop floor
in general is doing, what the health

438
00:30:11.219 --> 00:30:16.060
<v Marco Saviano>status, what are the next maintenance
tasks that will be demanded, at what point

439
00:30:16.060 --> 00:30:17.160
<v Marco Saviano>they might be demanded,

440
00:30:17.339 --> 00:30:23.219
<v Marco Saviano>and thanks to that plan on how to schedule
everything to save time, so.

441
00:30:24.219 --> 00:30:27.900
<v Marco Saviano>This is critical for a small company,
especially again if we imagine that the

442
00:30:27.900 --> 00:30:32.250
<v Marco Saviano>company is producing something in a remote
area and so on.

443
00:30:32.410 --> 00:30:39.260
<v Marco Saviano>We possibly don't always have also just an
easy support from the OEM of the machine

444
00:30:39.260 --> 00:30:43.510
<v Marco Saviano>or the The even from Siemens, let's say
that needs to drive to this place.

445
00:30:43.609 --> 00:30:48.089
<v Marco Saviano>Let's imagine, of course, if we imagine
small countries, this is less relevant, for

446
00:30:48.089 --> 00:30:51.569
<v Marco Saviano>example, can be a parameter, but if you
imagine a country like Brazil, you know,

447
00:30:51.729 --> 00:30:54.390
<v Marco Saviano>very, very big with a great forest in
between.

448
00:30:54.979 --> 00:30:59.910
<v Marco Saviano>If a small company has assets that are
critical to their production and the closest,

449
00:31:00.010 --> 00:31:05.979
<v Marco Saviano>let's say, repair shop or support engineer
service, field service engineer is 600

450
00:31:05.979 --> 00:31:11.420
<v Marco Saviano>kilometers away, we risk to have a
standstill for many hours, while with data and

451
00:31:11.420 --> 00:31:16.380
<v Marco Saviano>predictive maintenance we can first of all
Reduce the downtime to the minimum if it

452
00:31:16.380 --> 00:31:20.160
<v Marco Saviano>occurs because we have all the data to
know in advance what is needed for the

453
00:31:20.160 --> 00:31:20.630
<v Marco Saviano>maintenance.

454
00:31:20.680 --> 00:31:24.640
<v Marco Saviano>The person that comes to perform the task
is equipped with all the information and

455
00:31:24.640 --> 00:31:27.939
<v Marco Saviano>tools that are needed to solve the
problem, so one visit might be enough.

456
00:31:28.280 --> 00:31:32.800
<v Marco Saviano>And even better, in a better scenario when
the data flow is shared also with

457
00:31:32.800 --> 00:31:37.069
<v Marco Saviano>Siemens, for example, in advance, we can
actually prevent it completely because we

458
00:31:37.069 --> 00:31:41.989
<v Marco Saviano>just know that it is going to happen and
we send our expert even before the, the

459
00:31:41.989 --> 00:31:42.599
<v Marco Saviano>damage occurs.

460
00:31:42.719 --> 00:31:47.520
<v Marco Saviano>So, There is a huge benefit for the
customer again they learn if there is a

461
00:31:47.520 --> 00:31:53.890
<v Marco Saviano>misconduct from a, from an employer,
employee, so possibly they just Teach their,

462
00:31:54.010 --> 00:31:58.729
<v Marco Saviano>let's say, operators to change something
in their habits to prevent the machine

463
00:31:58.729 --> 00:32:04.569
<v Marco Saviano>getting into a more critical state, or
it's simply just there and where I mean time

464
00:32:04.569 --> 00:32:11.089
<v Marco Saviano>that comes to basically damaging some
parts, and if we know it in advance, we, our,

465
00:32:11.170 --> 00:32:12.329
<v Marco Saviano>our output is better, our

466
00:32:12.329 --> 00:32:13.530
<v Marco Saviano>quality output is better.

467
00:32:13.609 --> 00:32:19.250
<v Marco Saviano>I mean there is very, very many parameters
KPIs that we can track and that we can

468
00:32:19.250 --> 00:32:21.729
<v Marco Saviano>have an impact on with predictive
analytics.

469
00:32:23.540 --> 00:32:26.510
<v Niall Sullivan>And it, and it's interesting because you,
you, of course, mentioned the, you know,

470
00:32:26.589 --> 00:32:31.369
<v Niall Sullivan>the number one use case for predict
maintenance is reducing unplanned downtime.

471
00:32:31.670 --> 00:32:37.390
<v Niall Sullivan>And I, and I was just wondering whether,
um, whether SMEs sort of, I mean, it's not

472
00:32:37.390 --> 00:32:40.430
<v Niall Sullivan>just an SME thing actually, but whether
they consider the benefits of predict

473
00:32:40.430 --> 00:32:43.229
<v Niall Sullivan>maintenance beyond, um, unplanned
downtime.

474
00:32:43.349 --> 00:32:47.290
<v Niall Sullivan>You know, if we talk about, you know,
sustainability metrics or, you know, reducing.

475
00:32:47.880 --> 00:32:51.880
<v Niall Sullivan>Maintenance costs, allowing maintenance
teams to work more efficiently and, you

476
00:32:51.880 --> 00:32:56.079
<v Niall Sullivan>know, and so on and so on, and knowledge,
um, sharing and things like this, is that

477
00:32:56.079 --> 00:32:59.959
<v Niall Sullivan>something that they're aware of or is
downtime really the big, the big focus for

478
00:32:59.959 --> 00:33:00.839
<v Niall Sullivan>SMEs?

479
00:33:01.719 --> 00:33:08.420
<v Marco Saviano>I think the nice or the magnific thing
about data is that once we have them, we can

480
00:33:08.800 --> 00:33:12.670
<v Marco Saviano>use them for a whole sort of analysis that
we want.

481
00:33:13.119 --> 00:33:20.099
<v Marco Saviano>So using data to predict failure, so
tracking, I don't know, the torque of a machine

482
00:33:20.719 --> 00:33:24.520
<v Marco Saviano>to see if it's increasing regard and the
operation is still the same, maybe there is

483
00:33:24.520 --> 00:33:28.760
<v Marco Saviano>something wrong, there is more friction,
there is some bearing problem, and similar.

484
00:33:28.959 --> 00:33:35.290
<v Marco Saviano>So this is a use case for the maintenance,
but the same data that we get from Torque

485
00:33:35.290 --> 00:33:42.000
<v Marco Saviano>usage might also help us to understand if
this specific machine asset can run maybe

486
00:33:42.000 --> 00:33:47.670
<v Marco Saviano>at a higher speed because we are at 50% of
the consumption, let's say that we that

487
00:33:47.670 --> 00:33:48.209
<v Marco Saviano>we have.

488
00:33:48.520 --> 00:33:53.160
<v Marco Saviano>And then maybe if we have this
information, it's easier for us if we want to improve

489
00:33:53.160 --> 00:33:54.359
<v Marco Saviano>production or throughput.

490
00:33:54.829 --> 00:34:01.150
<v Marco Saviano>To decide if we buy a new machine and have
two lines in parallel running or more, or

491
00:34:01.150 --> 00:34:05.390
<v Marco Saviano>if we actually can use the one machine we
have we have at a higher speed without

492
00:34:05.390 --> 00:34:11.510
<v Marco Saviano>overloading it and basically save costs
because we don't buy a new line, not setting

493
00:34:11.510 --> 00:34:16.459
<v Marco Saviano>up a new line, and actually using more
efficiently what we already have.

494
00:34:16.830 --> 00:34:23.070
<v Marco Saviano>So it definitely goes hand in hand with
Energy consumption, circularity,

495
00:34:23.169 --> 00:34:28.770
<v Marco Saviano>sustainability topics, because once we
know exactly how we're running our assets, we

496
00:34:28.770 --> 00:34:33.889
<v Marco Saviano>know also how we can run them better,
basically, or if we can run them better, and

497
00:34:33.889 --> 00:34:39.909
<v Marco Saviano>this can impact also really decisions
about if we buy some more, if we need to

498
00:34:40.449 --> 00:34:45.649
<v Marco Saviano>change a spare part, it's if we know it in
advance, we possibly prevent bigger

499
00:34:45.649 --> 00:34:46.209
<v Marco Saviano>damages.

500
00:34:46.638 --> 00:34:50.519
<v Marco Saviano>And this will result in an extended
lifetime of the old machines that we are

501
00:34:50.519 --> 00:34:54.918
<v Marco Saviano>operating, which means again not having to
buy a new one and not having to throw

502
00:34:54.918 --> 00:34:55.718
<v Marco Saviano>away the old one.

503
00:34:55.839 --> 00:35:00.678
<v Marco Saviano>So also this is having a huge impact on
sustainability topics and circular circular

504
00:35:00.678 --> 00:35:01.039
<v Marco Saviano>economy.

505
00:35:02.850 --> 00:35:03.489
<v Niall Sullivan>No, absolutely.

506
00:35:03.610 --> 00:35:07.320
<v Niall Sullivan>I think, no, I think it's clear that, um,
and hopefully it's clear, clearer now more

507
00:35:07.320 --> 00:35:10.850
<v Niall Sullivan>than ever that the benefits of predictive
maintenance extend way beyond, um,

508
00:35:11.050 --> 00:35:13.860
<v Niall Sullivan>unplanned downtime, even though that's
such an important metric.

509
00:35:13.969 --> 00:35:18.350
<v Niall Sullivan>So I think that you spelled out that very
well, Marco.

510
00:35:18.429 --> 00:35:23.969
<v Niall Sullivan>Um, but, um, but I guess as we, as we come
towards the end of our chat, um, we

511
00:35:23.969 --> 00:35:28.209
<v Niall Sullivan>usually like to end on a sort of a, some
takeaways for the audience, I guess, in

512
00:35:28.209 --> 00:35:29.840
<v Niall Sullivan>terms of, um, sort of next steps.

513
00:35:29.929 --> 00:35:34.689
<v Niall Sullivan>So, I guess the question I'd ask you,
Marco, is about, you know, if, if an SMEs

514
00:35:34.689 --> 00:35:39.020
<v Niall Sullivan>looking to digitalize and get started, you
know, they've got the buy-in internally

515
00:35:39.020 --> 00:35:44.750
<v Niall Sullivan>from the various stakeholder groups, um,
what should their next steps be in terms of

516
00:35:44.750 --> 00:35:48.300
<v Niall Sullivan>their own sort of planning and thought
process, but also when speaking to vendors

517
00:35:48.300 --> 00:35:49.260
<v Niall Sullivan>like Siemens.

518
00:35:50.330 --> 00:35:56.290
<v Marco Saviano>Yeah, first of all, the takeaway would be
for me if it's not something you're used

519
00:35:56.290 --> 00:36:02.530
<v Marco Saviano>to work on, it's maybe much more
beneficial to engage with a partner like Siemens

520
00:36:02.530 --> 00:36:09.050
<v Marco Saviano>rather than starting some internal
initiative relegated to a smaller group of

521
00:36:09.050 --> 00:36:14.969
<v Marco Saviano>enthusiasts that then it's hard to, let's
say, implement what they find out in a

522
00:36:14.969 --> 00:36:17.469
<v Marco Saviano>company general, let's say, processes.

523
00:36:18.120 --> 00:36:24.530
<v Marco Saviano>The reason being for that is that to
implement a strong and valid digital

524
00:36:24.530 --> 00:36:31.370
<v Marco Saviano>transformation strategy in the predictive
analytics as well field is to have, as we

525
00:36:31.370 --> 00:36:33.110
<v Marco Saviano>said at the beginning, a cultural shift.

526
00:36:33.169 --> 00:36:38.209
<v Marco Saviano>So we don't only want to implement a new
software, we want people to change their

527
00:36:38.209 --> 00:36:43.570
<v Marco Saviano>habit and the process to be improved by
the idea of having the use of data.

528
00:36:43.889 --> 00:36:47.129
<v Marco Saviano>So use an expert expertise from Siemens
for that.

529
00:36:47.770 --> 00:36:54.229
<v Marco Saviano>And Last but not least, once again,
involve IT personnel as soon as

530
00:36:54.229 --> 00:37:00.969
<v Marco Saviano>possible because Digitalization is not an
IT problem only, as again it's a

531
00:37:00.969 --> 00:37:07.510
<v Marco Saviano>whole company mind shift, but the
infrastructure we need to deliver the change

532
00:37:07.810 --> 00:37:13.969
<v Marco Saviano>is based on IT and you risk wasting a lot
of time and resources if we start

533
00:37:13.969 --> 00:37:17.489
<v Marco Saviano>discussing something without having the IT
people involved.

534
00:37:17.699 --> 00:37:18.610
<v Marco Saviano>So I would say again.

535
00:37:19.959 --> 00:37:25.370
<v Marco Saviano>Cultural shift including leadership and
including IT personnel from the earliest

536
00:37:25.370 --> 00:37:31.729
<v Marco Saviano>stage to have clear all the steps that are
needed to improve a process thanks to

537
00:37:31.729 --> 00:37:36.969
<v Marco Saviano>digital transformation and predictive
analytics is the key and it's almost

538
00:37:36.969 --> 00:37:40.010
<v Marco Saviano>guaranteed success afterwards if we start
in this way.

539
00:37:40.899 --> 00:37:41.699
<v Niall Sullivan>Guarantee success.

540
00:37:41.780 --> 00:37:42.879
<v Niall Sullivan>That's what I like to hear.

541
00:37:43.020 --> 00:37:48.580
<v Niall Sullivan>Um, but, and the point about IT, um,
hopefully will resonate with, with everyone,

542
00:37:48.620 --> 00:37:50.399
<v Niall Sullivan>the importance of that, um, as well.

543
00:37:50.580 --> 00:37:52.939
<v Niall Sullivan>So yeah, fantastic tips, um, there, Marco.

544
00:37:53.010 --> 00:37:53.879
<v Niall Sullivan>Thank you very much.

545
00:37:54.500 --> 00:37:57.679
<v Niall Sullivan>But, um, but yes, for today, I think we've
come towards the end.

546
00:37:57.979 --> 00:38:02.040
<v Niall Sullivan>Um, hopefully, um, everyone's got, um, a
lot of value from the episode.

547
00:38:02.300 --> 00:38:03.100
<v Niall Sullivan>Um, I certainly have.

548
00:38:03.219 --> 00:38:04.739
<v Niall Sullivan>I learned a lot from these episodes too.

549
00:38:05.370 --> 00:38:09.489
<v Niall Sullivan>But I guess for now, thank you Marco for
your time and sharing your expertise, it's

550
00:38:09.489 --> 00:38:10.669
<v Niall Sullivan>been great to have you on the podcast.

551
00:38:11.750 --> 00:38:12.639
<v Marco Saviano>Thank you very much, Nel.

552
00:38:12.679 --> 00:38:13.320
<v Marco Saviano>It was a pleasure.

553
00:38:13.439 --> 00:38:18.840
<v Marco Saviano>I hope, uh, yeah, my first podcast went,
uh, went well, and yeah, looking forward

554
00:38:18.840 --> 00:38:24.159
<v Marco Saviano>hopefully to some information about how
this hall was received by our audience, and

555
00:38:24.439 --> 00:38:27.959
<v Marco Saviano>if I will be invited again, I will be, uh,
delighted to, to join.

556
00:38:28.570 --> 00:38:29.350
<v Marco Saviano>It's a fantastic.

557
00:38:30.010 --> 00:38:32.530
<v Niall Sullivan>Yeah, that's what I wanted to hear is that
you'd like to come back and we'd love to

558
00:38:32.530 --> 00:38:35.429
<v Niall Sullivan>have you back, so we, we certainly will
plan something for the future.

559
00:38:35.969 --> 00:38:40.209
<v Niall Sullivan>But, um, but yeah, for now, thank you, um,
Marco, and thank you everyone out there

560
00:38:40.209 --> 00:38:43.229
<v Niall Sullivan>for listening, wherever you are and see
you on the next episode.

561
00:38:45.699 --> 00:38:50.739
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

562
00:38:50.739 --> 00:38:54.040
<v Speaker 2>Sensi Predictive maintenance at
Siemens.com.
