WEBVTT
Language: en-US

1
00:00:02.019 --> 00:00:05.489
<v Speaker 1>Welcome to the trend detection podcast
powered by Siemens.

2
00:00:09.239 --> 00:00:12.560
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens.

3
00:00:12.880 --> 00:00:17.760
<v Speaker 2>I'm your host Sia, and here in today's
episode we will be diving into one of the

4
00:00:17.760 --> 00:00:22.600
<v Speaker 2>most impactful, yet sometimes overlooked
aspects of digital transformation

5
00:00:22.600 --> 00:00:23.319
<v Speaker 2>integration.

6
00:00:23.870 --> 00:00:28.350
<v Speaker 2>And to help us explore this topic, I am
joined by a wonderful guest, Konstantin,

7
00:00:28.680 --> 00:00:33.340
<v Speaker 2>lead engineer for digitalization, who
brings deep expertise and hands-on experience

8
00:00:33.520 --> 00:00:37.279
<v Speaker 2>in making integration a reality for small
and medium enterprises.

9
00:00:37.759 --> 00:00:40.099
<v Speaker 2>So thank you very much for being here with
me today.

10
00:00:41.110 --> 00:00:41.909
<v Konstantin Kobel>Thank you for having me.

11
00:00:43.490 --> 00:00:46.849
<v Speaker 2>Would you like to first introduce yourself
to our audience?

12
00:00:47.409 --> 00:00:48.729
<v Konstantin Kobel>Yeah, sure, I would love to.

13
00:00:49.250 --> 00:00:53.250
<v Konstantin Kobel>Um, so as you already said, my name is
Constantin Kolber, and I'm a lead engineer

14
00:00:53.250 --> 00:00:55.060
<v Konstantin Kobel>for digitalization at Siemens.

15
00:00:55.650 --> 00:00:59.930
<v Konstantin Kobel>Um, for the past 8 years, I've been
working on various digitalization projects, all

16
00:00:59.930 --> 00:01:02.880
<v Konstantin Kobel>of them with a focus on cloud and edge
computing.

17
00:01:03.409 --> 00:01:08.389
<v Konstantin Kobel>And in all of these projects, the primary
goal is always to collect production data,

18
00:01:08.769 --> 00:01:12.889
<v Konstantin Kobel>to pre-process this data, and to then
extract some value from this data.

19
00:01:14.349 --> 00:01:19.169
<v Speaker 2>And that is exactly our today's topic, and
I'd say we just get started.

20
00:01:19.800 --> 00:01:26.040
<v Speaker 2>And my first question to you is, why
integration is so critical for SMEs today?

21
00:01:27.010 --> 00:01:32.050
<v Konstantin Kobel>Yeah, I mean, integration is essential
because it connects disparate systems, tools,

22
00:01:32.059 --> 00:01:36.720
<v Konstantin Kobel>and also data sources, and this enables a
unified access to your data.

23
00:01:37.349 --> 00:01:42.099
<v Konstantin Kobel>What we often see is that small and medium
sized enterprises, they have sometimes

24
00:01:42.099 --> 00:01:46.059
<v Konstantin Kobel>many different data silos with different
purposes that have all been created with

25
00:01:46.059 --> 00:01:47.440
<v Konstantin Kobel>different use case in mind.

26
00:01:48.080 --> 00:01:52.730
<v Konstantin Kobel>Um, so you can think of it like There has
been a, a data silo that has been created

27
00:01:52.730 --> 00:01:57.089
<v Konstantin Kobel>for artificial intelligence and then
somebody also wanted to extract some

28
00:01:57.089 --> 00:01:58.930
<v Konstantin Kobel>information from this aspect of
production.

29
00:01:59.290 --> 00:02:04.769
<v Konstantin Kobel>So these data silos have been built up
historically, and while their use cases might

30
00:02:04.769 --> 00:02:08.429
<v Konstantin Kobel>have been fulfilled, a bigger picture is
oftentimes missing.

31
00:02:08.809 --> 00:02:11.750
<v Konstantin Kobel>And this leads to, for example, data
duplicates.

32
00:02:11.800 --> 00:02:18.050
<v Konstantin Kobel>This also makes it a very time intensive
and general resource intensive process to,

33
00:02:18.130 --> 00:02:20.009
<v Konstantin Kobel>if you want to access specific data.

34
00:02:20.559 --> 00:02:25.479
<v Konstantin Kobel>So to summarize it, if you have
integration for small and medium enterprise

35
00:02:25.479 --> 00:02:28.039
<v Konstantin Kobel>customers, it means faster decision
making.

36
00:02:28.080 --> 00:02:34.000
<v Konstantin Kobel>It also means less manual work, and you
can use your resources more efficiently,

37
00:02:34.119 --> 00:02:37.399
<v Konstantin Kobel>which is all, I think, very crucial for
staying competitive.

38
00:02:37.759 --> 00:02:41.750
<v Konstantin Kobel>And of course one aspect that we'll also
talk about is cybersecurity and why

39
00:02:41.750 --> 00:02:44.199
<v Konstantin Kobel>integration is so important for
cybersecurity.

40
00:02:46.220 --> 00:02:50.059
<v Speaker 2>I totally agree with you, and I think it's
actually pretty surprising how many

41
00:02:50.059 --> 00:02:54.820
<v Speaker 2>companies still rely on manual processes
that can easily be automated with

42
00:02:54.820 --> 00:02:55.610
<v Speaker 2>integration.

43
00:02:55.990 --> 00:02:57.029
<v Speaker 2>Absolutely, yes.

44
00:02:57.929 --> 00:03:03.149
<v Speaker 2>Yeah, and you know, like it's not always
just about technology, sometimes it's also

45
00:03:03.809 --> 00:03:08.429
<v Speaker 2>about getting different departments to
talk to each other and align on their goals.

46
00:03:09.009 --> 00:03:13.130
<v Konstantin Kobel>Exactly, yeah, um, when we talk about
integration with our customers, we have a

47
00:03:13.130 --> 00:03:19.570
<v Konstantin Kobel>specialized approach that that tackles
exactly this problem, um, that, that the

48
00:03:19.570 --> 00:03:23.169
<v Konstantin Kobel>parties don't talk to each other and that
they have not aligned goals, yeah.

49
00:03:25.520 --> 00:03:28.660
<v Speaker 2>So this then brings me to my next
question.

50
00:03:28.919 --> 00:03:33.399
<v Speaker 2>How does Siemens approach integration
tailored to the needs of SMEs?

51
00:03:34.169 --> 00:03:37.970
<v Konstantin Kobel>Yeah, I mean, when we talk about
integration with our customers, we know that every

52
00:03:37.970 --> 00:03:39.539
<v Konstantin Kobel>customer and every setup is different.

53
00:03:40.130 --> 00:03:44.850
<v Konstantin Kobel>So it's always our priority um to deliver
a solution that is, first of all, of

54
00:03:44.850 --> 00:03:47.029
<v Konstantin Kobel>course, tech technically cutting edge.

55
00:03:47.449 --> 00:03:53.580
<v Konstantin Kobel>But we also have a heavy focus on
modularity, scalability, and we want to make a

56
00:03:53.580 --> 00:03:55.899
<v Konstantin Kobel>solution that fits into the existing
infrastructure.

57
00:03:56.179 --> 00:04:00.419
<v Konstantin Kobel>It's not always a goal to rethink the
whole process, but we want to do, we want to

58
00:04:00.419 --> 00:04:04.320
<v Konstantin Kobel>build something that really that where we
can take the customer from where they are.

59
00:04:04.779 --> 00:04:10.470
<v Konstantin Kobel>Um, so, what we try is to really evolve
with the customer instead of doing a full

60
00:04:10.470 --> 00:04:11.500
<v Konstantin Kobel>system replacement.

61
00:04:12.320 --> 00:04:17.130
<v Konstantin Kobel>And one step or the first step that we
usually do here is that we start talking to

62
00:04:17.130 --> 00:04:17.910
<v Konstantin Kobel>the customer.

63
00:04:18.450 --> 00:04:23.089
<v Konstantin Kobel>We usually start talking in an initial
workshop where we bring all the departments

64
00:04:23.089 --> 00:04:27.369
<v Konstantin Kobel>and all the parties inside a customer on
one table, and we talk about their needs

65
00:04:27.369 --> 00:04:30.570
<v Konstantin Kobel>and their goals, and also about their use
cases.

66
00:04:31.059 --> 00:04:36.869
<v Konstantin Kobel>And once we did this in a workshop, um,
then afterwards we take those needs and use

67
00:04:36.869 --> 00:04:43.589
<v Konstantin Kobel>cases and based on that, we do a concept
that fits this needs and use cases.

68
00:04:44.029 --> 00:04:49.510
<v Konstantin Kobel>And what we often see in these initial
workshops is that it's oftentimes the first

69
00:04:49.510 --> 00:04:52.670
<v Konstantin Kobel>time that all of these departments and all
of these parties are talking to each

70
00:04:52.670 --> 00:04:53.029
<v Konstantin Kobel>other.

71
00:04:53.730 --> 00:04:57.820
<v Konstantin Kobel>What happens really often is that one
department has a need or a use case and they

72
00:04:57.820 --> 00:05:02.540
<v Konstantin Kobel>try to solve it themselves, so they build
a data silo and then with some tools to

73
00:05:02.540 --> 00:05:04.239
<v Konstantin Kobel>analyze the data that's stored there.

74
00:05:04.660 --> 00:05:09.980
<v Konstantin Kobel>So this first workshop is really crucial
for, first of all, getting the individual

75
00:05:09.980 --> 00:05:11.179
<v Konstantin Kobel>parties to talk to each other.

76
00:05:12.019 --> 00:05:16.220
<v Konstantin Kobel>But also to figure out the needs and use
cases that are there for integration.

77
00:05:16.660 --> 00:05:22.489
<v Konstantin Kobel>Um, so it's really, this is the kickoff, I
would say, for this um transformation

78
00:05:22.489 --> 00:05:25.619
<v Konstantin Kobel>we're doing with the customer, where we
really take the customer by the hand and

79
00:05:25.619 --> 00:05:27.440
<v Konstantin Kobel>guide them through this transformation
process.

80
00:05:29.670 --> 00:05:30.829
<v Speaker 2>Totally, totally.

81
00:05:30.989 --> 00:05:35.489
<v Speaker 2>I think one thing we've learned so far
from working with SMEs across various

82
00:05:35.489 --> 00:05:41.779
<v Speaker 2>industries is that integration isn't like
one size fits all game and flexibility

83
00:05:41.779 --> 00:05:43.059
<v Speaker 2>here, it's actually everything.

84
00:05:43.269 --> 00:05:48.510
<v Speaker 2>So yeah, that's why the human element,
like understanding workflows, challenges, and

85
00:05:48.510 --> 00:05:52.769
<v Speaker 2>people, it is just as important as the
technical side of the game.

86
00:05:53.269 --> 00:05:54.690
<v Konstantin Kobel>Yeah, I couldn't agree more.

87
00:05:55.059 --> 00:05:59.179
<v Konstantin Kobel>I mean, I think that's also what we
learned during these workshops, exactly what you

88
00:05:59.179 --> 00:06:03.579
<v Konstantin Kobel>said, that while the technical side is of
course very important, the human side is

89
00:06:03.579 --> 00:06:04.540
<v Konstantin Kobel>just as important.

90
00:06:06.609 --> 00:06:11.790
<v Speaker 2>But now then, I'm really curious if you
can share an example with me where this kind

91
00:06:11.790 --> 00:06:15.750
<v Speaker 2>of integration really made a significant
difference for a company.

92
00:06:16.290 --> 00:06:17.230
<v Konstantin Kobel>Absolutely, yes.

93
00:06:17.690 --> 00:06:22.970
<v Konstantin Kobel>One very prominent case that we had was a
company from the electronics vertical who

94
00:06:22.970 --> 00:06:27.890
<v Konstantin Kobel>wanted to store the process data from
their production in one central place, and one

95
00:06:27.890 --> 00:06:32.290
<v Konstantin Kobel>issue they had was that in the case of
warranty claims, they had to manually collect

96
00:06:32.290 --> 00:06:33.929
<v Konstantin Kobel>the data from all of their machines.

97
00:06:34.269 --> 00:06:40.040
<v Konstantin Kobel>And then search through this data for what
aspects they were looking for, and for

98
00:06:40.040 --> 00:06:44.160
<v Konstantin Kobel>each warranty claim, this meant an effort
of around 9 man days.

99
00:06:44.440 --> 00:06:49.589
<v Konstantin Kobel>So 3 people were working for 3 days to
collect the data and to then look through the

100
00:06:49.589 --> 00:06:52.559
<v Konstantin Kobel>data to actually find what they were
looking for.

101
00:06:53.079 --> 00:06:58.220
<v Konstantin Kobel>And with this integration solution now in
place, the customer was able to reduce

102
00:06:58.220 --> 00:07:02.839
<v Konstantin Kobel>this effort to 1 query, which now takes a
few seconds to run.

103
00:07:03.399 --> 00:07:07.519
<v Konstantin Kobel>So for this customer, um integration is
already really making a change today.

104
00:07:10.160 --> 00:07:15.309
<v Speaker 2>Yeah, I think it's a really impressive
example of how integration, you know, it's

105
00:07:15.309 --> 00:07:20.019
<v Speaker 2>not just an IT upgrade, but rather a
transformation that can ripple through

106
00:07:20.019 --> 00:07:24.910
<v Speaker 2>operations and customer service alike, and
you know we can just imagine saving 9

107
00:07:24.910 --> 00:07:27.630
<v Speaker 2>main days per warranty case for any SME.

108
00:07:27.670 --> 00:07:29.589
<v Speaker 2>It's going to be a huge case, a huge deal.

109
00:07:30.589 --> 00:07:36.040
<v Konstantin Kobel>Yeah, absolutely, and again, this is one
of the benefits of integration that you

110
00:07:36.040 --> 00:07:39.279
<v Konstantin Kobel>don't have to do this data handling, for
example, anymore.

111
00:07:39.839 --> 00:07:43.980
<v Konstantin Kobel>You can really focus your resources, also
well experienced resources.

112
00:07:44.399 --> 00:07:49.500
<v Konstantin Kobel>They can focus on key business and to
focus on actually bringing your USP forward,

113
00:07:50.390 --> 00:07:53.640
<v Konstantin Kobel>instead of just dealing with data handling
tasks and finding the right data.

114
00:07:53.920 --> 00:07:59.119
<v Konstantin Kobel>And I think especially for small and
medium sized enterprises, this can really be a

115
00:07:59.119 --> 00:07:59.880
<v Konstantin Kobel>huge benefit.

116
00:08:01.309 --> 00:08:01.910
<v Speaker 2>Totally.

117
00:08:02.839 --> 00:08:06.799
<v Speaker 2>Good, but now maybe let's talk about the
roadblocks.

118
00:08:07.160 --> 00:08:12.200
<v Speaker 2>What are the most common challenges that
SMEs face when starting their integration

119
00:08:12.200 --> 00:08:12.739
<v Speaker 2>journey?

120
00:08:13.589 --> 00:08:17.119
<v Konstantin Kobel>Yeah, I mean, since I'm the one
responsible for implementing these projects, um, I

121
00:08:17.119 --> 00:08:22.209
<v Konstantin Kobel>can tell you about lots of challenges, but
I think many challenges that we often

122
00:08:22.209 --> 00:08:26.100
<v Konstantin Kobel>face are, for example, legacy systems that
are still in place.

123
00:08:26.440 --> 00:08:29.880
<v Konstantin Kobel>We have a siloed data that needs to be
connected somehow.

124
00:08:30.230 --> 00:08:34.710
<v Konstantin Kobel>Um, and there's also often lacking
concepts, for example, in the production network

125
00:08:34.710 --> 00:08:39.830
<v Konstantin Kobel>of the customer, which not only poses
risks to their security, but also makes it

126
00:08:39.830 --> 00:08:43.869
<v Konstantin Kobel>harder to actually connect all the systems
that the customer wants to be connected.

127
00:08:44.729 --> 00:08:50.090
<v Konstantin Kobel>And I think one very interesting aspect is
also the fact that oftentimes we're faced

128
00:08:50.090 --> 00:08:51.479
<v Konstantin Kobel>with social challenges.

129
00:08:51.849 --> 00:08:56.250
<v Konstantin Kobel>We've seen it in many companies and I
already said in the beginning that we have

130
00:08:56.250 --> 00:09:00.690
<v Konstantin Kobel>different departments within companies and
they have of course different use cases,

131
00:09:00.770 --> 00:09:04.809
<v Konstantin Kobel>different needs, but they don't always
talk to each other and especially when we're

132
00:09:04.809 --> 00:09:10.549
<v Konstantin Kobel>talking about data integration, getting
data, utilizing data, we see it very often

133
00:09:10.549 --> 00:09:13.390
<v Konstantin Kobel>that Um, there's no aligned goal.

134
00:09:13.679 --> 00:09:15.809
<v Konstantin Kobel>There's no aligned way forward.

135
00:09:16.119 --> 00:09:21.099
<v Konstantin Kobel>So each department does their own thing
and we again end up having data silos.

136
00:09:21.479 --> 00:09:25.159
<v Konstantin Kobel>Um, so as I said in the beginning, this is
really one reason why we have this

137
00:09:25.159 --> 00:09:29.960
<v Konstantin Kobel>workshop in the beginning to basically
catch up with everyone who's involved, who

138
00:09:29.960 --> 00:09:36.000
<v Konstantin Kobel>has something to say, um, in regards to
integration and to really bring all the

139
00:09:36.000 --> 00:09:39.520
<v Konstantin Kobel>stakeholders to the table, consider all
the needs, and then to create, create a

140
00:09:39.520 --> 00:09:40.919
<v Konstantin Kobel>final concept based on that.

141
00:09:43.099 --> 00:09:47.179
<v Speaker 2>Yeah, I think it's, you know, always
really interesting to see how much of the

142
00:09:47.179 --> 00:09:51.820
<v Speaker 2>challenge is actually internal, like silo
thinking or misaligned goals between

143
00:09:51.820 --> 00:09:52.650
<v Speaker 2>departments.

144
00:09:53.020 --> 00:09:57.239
<v Speaker 2>But um, would you also consider costs to
be another challenge for SMEs?

145
00:09:57.739 --> 00:10:02.900
<v Konstantin Kobel>Yeah, I mean, I think costs and especially
also complexity in general, always

146
00:10:02.900 --> 00:10:05.859
<v Konstantin Kobel>something that you might worry about when
you talk about integration.

147
00:10:06.409 --> 00:10:11.859
<v Konstantin Kobel>And I think one aspect here is that if you
have this fear or if you, if you're

148
00:10:11.859 --> 00:10:16.219
<v Konstantin Kobel>afraid of the cost or the complexity,
having really an experienced partner like

149
00:10:16.219 --> 00:10:19.299
<v Konstantin Kobel>Siemens that can take you by the hand,
that can guide you through this

150
00:10:19.299 --> 00:10:22.489
<v Konstantin Kobel>transformation process is key, I think.

151
00:10:22.900 --> 00:10:28.059
<v Konstantin Kobel>Um, and also our approach considers every
customer's possibilities and also their

152
00:10:28.059 --> 00:10:31.669
<v Konstantin Kobel>resources, and based on that, we define a
way forward together.

153
00:10:32.369 --> 00:10:36.760
<v Konstantin Kobel>Because, you know, integration doesn't
always have to be a huge project that changes

154
00:10:36.760 --> 00:10:41.090
<v Konstantin Kobel>everything within a company, um, it can
really start with just one machine and then

155
00:10:41.090 --> 00:10:42.869
<v Konstantin Kobel>we go from there step by step.

156
00:10:43.369 --> 00:10:48.429
<v Konstantin Kobel>So integration can really be a year-long
change process in your company, where you,

157
00:10:48.650 --> 00:10:53.570
<v Konstantin Kobel>because that's also the nice thing, um,
when you go along over years, you find new

158
00:10:53.570 --> 00:10:54.280
<v Konstantin Kobel>use cases.

159
00:10:54.609 --> 00:10:57.890
<v Konstantin Kobel>Maybe the use cases you defined in the
beginning, they're not relevant anymore

160
00:10:57.890 --> 00:10:59.690
<v Konstantin Kobel>because you already figured out another
way to do it.

161
00:11:00.210 --> 00:11:03.989
<v Konstantin Kobel>Um, but you find new use cases and they
can also be integrated here.

162
00:11:04.650 --> 00:11:06.849
<v Konstantin Kobel>So I think that's also a big part here.

163
00:11:07.590 --> 00:11:13.150
<v Konstantin Kobel>It sure is complex, but having the right
partner and taking the time to change is

164
00:11:13.150 --> 00:11:14.510
<v Konstantin Kobel>also very important here, I think.

165
00:11:16.229 --> 00:11:19.210
<v Speaker 2>Yeah, totally, I agree with you here.

166
00:11:20.080 --> 00:11:25.520
<v Speaker 2>Good, but now maybe let's shift focus a
bit and look inside the organization.

167
00:11:25.919 --> 00:11:29.080
<v Speaker 2>So what happens to collaboration when data
silos break down?

168
00:11:29.900 --> 00:11:33.700
<v Konstantin Kobel>Yeah, I mean, what we all know and I guess
also the audience that's listening to us

169
00:11:33.700 --> 00:11:35.700
<v Konstantin Kobel>right now, that data is the new gold.

170
00:11:35.820 --> 00:11:40.419
<v Konstantin Kobel>Um, however, just data is not enough, you
really need to utilize this data

171
00:11:40.419 --> 00:11:42.789
<v Konstantin Kobel>efficiently and extract its real value.

172
00:11:43.400 --> 00:11:48.080
<v Konstantin Kobel>And what happens quite often, or also what
we see quite often is that um as I said,

173
00:11:48.159 --> 00:11:53.280
<v Konstantin Kobel>different groups and different
departments, they collect their data and they look at

174
00:11:53.280 --> 00:11:57.640
<v Konstantin Kobel>this data from one angle, and they might
have even done this for years, so you

175
00:11:57.640 --> 00:12:04.400
<v Konstantin Kobel>really have years and centuries of
expertise in looking at exactly this data, but

176
00:12:04.599 --> 00:12:09.799
<v Konstantin Kobel>I think the true value is really derived
from data when we look at it from different

177
00:12:09.799 --> 00:12:10.280
<v Konstantin Kobel>angles.

178
00:12:10.940 --> 00:12:15.750
<v Konstantin Kobel>And integration is a great way to do this
because when you have all your data from

179
00:12:15.750 --> 00:12:20.390
<v Konstantin Kobel>your production integrated in one system,
you have it in one place and all of the

180
00:12:20.390 --> 00:12:24.500
<v Konstantin Kobel>tools are connected to this data in one
place, you get, you can, you find new

181
00:12:24.500 --> 00:12:29.469
<v Konstantin Kobel>aspects, you get new insights, and you can
really find also new value in your data.

182
00:12:29.969 --> 00:12:35.500
<v Konstantin Kobel>And also integration allows you to not
only have real-time data of your machines,

183
00:12:35.570 --> 00:12:36.799
<v Konstantin Kobel>but also historical ones.

184
00:12:37.109 --> 00:12:41.570
<v Konstantin Kobel>So you can compare, for example, your
production right now with the production of

185
00:12:41.570 --> 00:12:47.760
<v Konstantin Kobel>how it was 5 years ago, and then see what
maybe what what improved, but maybe also

186
00:12:47.760 --> 00:12:50.090
<v Konstantin Kobel>what didn't improve and where you can
still have a look at.

187
00:12:50.919 --> 00:12:56.520
<v Konstantin Kobel>So integration really allows you to look
at data from different angles and also to

188
00:12:56.520 --> 00:12:57.770
<v Konstantin Kobel>look at it with different people.

189
00:12:58.119 --> 00:13:02.320
<v Konstantin Kobel>As I said in the beginning, um,
departments oftentimes work on their own, and I

190
00:13:02.320 --> 00:13:06.599
<v Konstantin Kobel>think if we share this data and we can
also have another department look at the data

191
00:13:06.599 --> 00:13:11.320
<v Konstantin Kobel>and have them have their own
interpretation and then also ask some questions.

192
00:13:11.679 --> 00:13:13.190
<v Konstantin Kobel>That's where real value comes up.

193
00:13:13.440 --> 00:13:15.020
<v Konstantin Kobel>It's also something we see quite often.

194
00:13:15.299 --> 00:13:21.299
<v Konstantin Kobel>Um, when we just ask very, very objective
questions, even without domain knowledge,

195
00:13:21.820 --> 00:13:27.659
<v Konstantin Kobel>sometimes these questions are real
kickoffs for the actual domain experts to rethink

196
00:13:27.659 --> 00:13:30.130
<v Konstantin Kobel>the process, to rethink how to do things.

197
00:13:33.140 --> 00:13:33.650
<v Speaker 2>Exactly.

198
00:13:33.849 --> 00:13:38.049
<v Speaker 2>So I think when people from different
functions can actually access the same data,

199
00:13:38.210 --> 00:13:43.000
<v Speaker 2>then you finally get the synergy, and you
know, suddenly all the teams are working

200
00:13:43.000 --> 00:13:46.109
<v Speaker 2>off the same playbook, and this is really
powerful.

201
00:13:46.570 --> 00:13:49.619
<v Konstantin Kobel>Yeah, it's really what I said in the
beginning with the workshop.

202
00:13:50.000 --> 00:13:54.010
<v Konstantin Kobel>Um, the first thing we really want to do
is to bring all the stakeholders to one

203
00:13:54.010 --> 00:13:57.929
<v Konstantin Kobel>table, to talk about their needs and use
cases, to talk about what we want to

204
00:13:57.929 --> 00:13:58.609
<v Konstantin Kobel>implement here.

205
00:13:59.150 --> 00:14:03.909
<v Konstantin Kobel>And usually when you have this data
collection, when you have all this production

206
00:14:03.909 --> 00:14:08.070
<v Konstantin Kobel>data, they start talking to each other and
you really find these benefits and also

207
00:14:08.070 --> 00:14:09.909
<v Konstantin Kobel>this collaboration based on the data.

208
00:14:13.739 --> 00:14:18.109
<v Speaker 2>OK, and then speaking of the shared
systems actually, what about security?

209
00:14:18.390 --> 00:14:21.030
<v Speaker 2>How does integration affect cybersecurity?

210
00:14:21.820 --> 00:14:26.640
<v Konstantin Kobel>Yeah, I mean for everything in technology,
cybersecurity is the basis and it also is

211
00:14:26.640 --> 00:14:27.679
<v Konstantin Kobel>for integration.

212
00:14:28.119 --> 00:14:32.559
<v Konstantin Kobel>And I think in the whole integration
process, cybersecurity is always considered

213
00:14:32.559 --> 00:14:33.179
<v Konstantin Kobel>heavily.

214
00:14:33.510 --> 00:14:38.679
<v Konstantin Kobel>And what we see quite often is that the
integration actually improves cybersecurity.

215
00:14:39.400 --> 00:14:42.760
<v Konstantin Kobel>We've talked a lot about data silos and
silo data.

216
00:14:43.179 --> 00:14:49.349
<v Konstantin Kobel>And this is also one thing that happens
during these initial workshops that um we

217
00:14:49.650 --> 00:14:50.880
<v Konstantin Kobel>find new data silos.

218
00:14:51.039 --> 00:14:56.869
<v Konstantin Kobel>Oftentimes, um, departments or parties,
they start talking about new data silos,

219
00:14:57.010 --> 00:15:02.289
<v Konstantin Kobel>they set up once and forgot about it or
are still using it, however, IT for example,

220
00:15:02.369 --> 00:15:03.239
<v Konstantin Kobel>doesn't know about it.

221
00:15:03.609 --> 00:15:06.010
<v Konstantin Kobel>So IT cannot govern them, cannot protect
them.

222
00:15:06.630 --> 00:15:12.710
<v Konstantin Kobel>So if you have this one central
integration solution in place, you can really easily

223
00:15:12.710 --> 00:15:18.609
<v Konstantin Kobel>secure this solution, and you can also
centralize government governance as well as

224
00:15:18.609 --> 00:15:20.450
<v Konstantin Kobel>of course also access control.

225
00:15:20.909 --> 00:15:25.469
<v Konstantin Kobel>So instead of multiple points of
vulnerability, you have one coordinated defense

226
00:15:25.469 --> 00:15:26.070
<v Konstantin Kobel>strategy.

227
00:15:26.770 --> 00:15:33.239
<v Konstantin Kobel>Um Yeah, and as I said, this really
uncovering the data silos and connecting them

228
00:15:33.419 --> 00:15:37.619
<v Konstantin Kobel>into one solution is also a huge benefit
to cybersecurity in a company.

229
00:15:39.179 --> 00:15:43.440
<v Speaker 2>Yeah, and I think it's counterintuitive to
some people, but integration actually

230
00:15:43.440 --> 00:15:44.880
<v Speaker 2>often improves security.

231
00:15:45.099 --> 00:15:49.940
<v Speaker 2>And once you are being able to centralize
and harmonize all of your access, then you

232
00:15:49.940 --> 00:15:52.669
<v Speaker 2>reduce the risk from rogue systems or from
shadow IT.

233
00:15:53.380 --> 00:15:55.849
<v Konstantin Kobel>Absolutely, yeah, that's what we see in
these workshops.

234
00:15:56.260 --> 00:16:01.659
<v Konstantin Kobel>So in this sense, really, I think
cybersecurity is very important to integration,

235
00:16:02.020 --> 00:16:05.780
<v Konstantin Kobel>but I also think that integration is very
important to a company's cybersecurity.

236
00:16:08.159 --> 00:16:13.320
<v Speaker 2>And as you know, one of the key factors
for SMEs is scalability.

237
00:16:13.479 --> 00:16:18.349
<v Speaker 2>So can you share with me how integration
can actually contribute to a company's

238
00:16:18.349 --> 00:16:18.979
<v Speaker 2>growth potential?

239
00:16:19.849 --> 00:16:24.570
<v Konstantin Kobel>Yeah, I mean, in our industrialized world,
margins have become very slim, and I

240
00:16:24.570 --> 00:16:26.469
<v Konstantin Kobel>think we all know it here in this podcast.

241
00:16:26.729 --> 00:16:28.630
<v Konstantin Kobel>I think also our audience knows it.

242
00:16:28.969 --> 00:16:35.409
<v Konstantin Kobel>If you really want to improve your
processes or also your product quality, the

243
00:16:35.409 --> 00:16:37.289
<v Konstantin Kobel>improvements are not found that easily
anymore.

244
00:16:37.400 --> 00:16:42.289
<v Konstantin Kobel>We really need to look at things, we
really need to dig into the data to find some

245
00:16:42.289 --> 00:16:43.059
<v Konstantin Kobel>improvements.

246
00:16:43.369 --> 00:16:47.650
<v Konstantin Kobel>And especially here, data has become the
main decision making basis for improvements

247
00:16:47.650 --> 00:16:48.229
<v Konstantin Kobel>of any kind.

248
00:16:49.039 --> 00:16:54.280
<v Konstantin Kobel>So, um, integration can really be the
foundation for these improvements, be it in

249
00:16:54.280 --> 00:17:00.969
<v Konstantin Kobel>the production process or in the product
and, um, at all, so, Yeah, this is

250
00:17:00.969 --> 00:17:06.599
<v Konstantin Kobel>one aspect where integration can really be
a benefit, and also in addition, as a

251
00:17:06.599 --> 00:17:12.010
<v Konstantin Kobel>company grows, new systems and tools can
be added into an integrated landscape way

252
00:17:12.010 --> 00:17:14.290
<v Konstantin Kobel>more easily without disrupting operations.

253
00:17:14.890 --> 00:17:17.130
<v Konstantin Kobel>We have it right now with large language
models.

254
00:17:17.209 --> 00:17:19.560
<v Konstantin Kobel>We had it a few years ago with artificial
intelligence.

255
00:17:19.900 --> 00:17:22.530
<v Konstantin Kobel>All of these new technologies are coming
very fast to us.

256
00:17:23.198 --> 00:17:28.678
<v Konstantin Kobel>And if you have a landscape that's already
integrated, that's ready for these new

257
00:17:28.678 --> 00:17:32.938
<v Konstantin Kobel>tools, of course it's way easier for you
to adapt these new technologies and really

258
00:17:33.239 --> 00:17:36.918
<v Konstantin Kobel>use their benefits than when you have to
first search for all your data and then

259
00:17:36.918 --> 00:17:40.519
<v Konstantin Kobel>connect it somehow and yeah, to try to
make it work.

260
00:17:41.500 --> 00:17:45.300
<v Konstantin Kobel>So really when you have an integration
solution in place, it's really like a plug

261
00:17:45.300 --> 00:17:49.180
<v Konstantin Kobel>and play infrastructure where you can just
add pieces and remove pieces as you need

262
00:17:49.180 --> 00:17:49.420
<v Konstantin Kobel>it.

263
00:17:51.089 --> 00:17:56.260
<v Speaker 2>For sure, I think this scalability piece
is really important and you know, SMEs

264
00:17:56.260 --> 00:18:01.250
<v Speaker 2>often they grow fast, but their systems
don't always keep up, and with the right

265
00:18:01.250 --> 00:18:06.729
<v Speaker 2>integration, finally they can avoid the
growing pains and can just focus on scaling

266
00:18:06.729 --> 00:18:08.640
<v Speaker 2>value and not the complexity.

267
00:18:09.180 --> 00:18:13.979
<v Konstantin Kobel>Yeah, so really integration builds the
basis for scalability and growth, in my

268
00:18:13.979 --> 00:18:14.339
<v Konstantin Kobel>opinion.

269
00:18:15.770 --> 00:18:19.640
<v Speaker 2>But growth also depends on staying ahead
of trends.

270
00:18:19.800 --> 00:18:25.140
<v Speaker 2>So how does integration futureproof SMEs
for emerging technologies?

271
00:18:25.869 --> 00:18:30.560
<v Konstantin Kobel>Yeah, I mean, as I just said, I think once
systems are integrated, it's really way

272
00:18:30.560 --> 00:18:32.989
<v Konstantin Kobel>easier to adopt new technologies.

273
00:18:33.829 --> 00:18:37.630
<v Konstantin Kobel>I said already, artificial intelligence,
we also have, for example, cloud-based

274
00:18:37.630 --> 00:18:42.030
<v Konstantin Kobel>analytics, all of these technologies that
are already available today and that have

275
00:18:42.030 --> 00:18:43.300
<v Konstantin Kobel>already proven their benefit.

276
00:18:43.900 --> 00:18:48.020
<v Konstantin Kobel>You can really use them way more easily if
you have an integration solution in

277
00:18:48.020 --> 00:18:48.359
<v Konstantin Kobel>place.

278
00:18:49.109 --> 00:18:53.589
<v Konstantin Kobel>So integration is not only about
connecting today's tools and about connecting

279
00:18:53.589 --> 00:18:57.560
<v Konstantin Kobel>today's machinery, but it's also about
being ready for tomorrow's possibility.

280
00:18:58.030 --> 00:19:02.109
<v Konstantin Kobel>And also one thing, when, especially when
talking about artificial intelligence, one

281
00:19:02.109 --> 00:19:05.589
<v Konstantin Kobel>thing that we have to consider is that
when we talk about artificial intelligence,

282
00:19:05.790 --> 00:19:10.550
<v Konstantin Kobel>you not only need current data, but the
more data you can get, the better the

283
00:19:10.550 --> 00:19:12.310
<v Konstantin Kobel>artificial intelligence is in the end.

284
00:19:12.790 --> 00:19:18.719
<v Konstantin Kobel>So, What we're also trying to say here is
that um historical data can be very, very

285
00:19:18.719 --> 00:19:22.719
<v Konstantin Kobel>valuable for training in artificial
intelligence and it's actually essential.

286
00:19:23.319 --> 00:19:27.920
<v Konstantin Kobel>So um if you really want to use these
technologies like artificial intelligence to

287
00:19:27.920 --> 00:19:30.719
<v Konstantin Kobel>its fullest, you need all the data you can
get.

288
00:19:31.160 --> 00:19:36.109
<v Konstantin Kobel>And therefore, having this extensive data
collection, this extensive data pool in an

289
00:19:36.109 --> 00:19:40.800
<v Konstantin Kobel>integration solution can really leverage
this potential um to another level.

290
00:19:43.119 --> 00:19:48.540
<v Speaker 2>Do you have an example use case where AI
utilizes data from an integration solution?

291
00:19:49.160 --> 00:19:49.859
<v Konstantin Kobel>Yes, of course.

292
00:19:50.680 --> 00:19:53.339
<v Konstantin Kobel>So one solution that we have at Siemens,
it's called Sensi.

293
00:19:53.959 --> 00:19:57.219
<v Konstantin Kobel>It's an application that focuses on
predictive maintenance.

294
00:19:57.510 --> 00:20:01.760
<v Konstantin Kobel>This means that based on the machine data,
a baseline is being created for that

295
00:20:01.760 --> 00:20:06.760
<v Konstantin Kobel>machine or also for the whole process, and
once parameters from the machine deviate

296
00:20:06.760 --> 00:20:10.920
<v Konstantin Kobel>from the baseline, and ably has been
detected and the customer is being notified

297
00:20:10.920 --> 00:20:11.280
<v Konstantin Kobel>about it.

298
00:20:11.800 --> 00:20:18.060
<v Konstantin Kobel>So what, what Sensi does is that just by
looking at the machine data, it's able to

299
00:20:18.060 --> 00:20:23.280
<v Konstantin Kobel>predict anomalies, meaning, first of all,
of course you can avoid downtimes, but

300
00:20:23.280 --> 00:20:28.479
<v Konstantin Kobel>anomalies can also be some things that are
starting to slowly fall apart, like for

301
00:20:28.479 --> 00:20:33.079
<v Konstantin Kobel>example, some machine part that's maybe
running out of bounds.

302
00:20:33.500 --> 00:20:37.270
<v Konstantin Kobel>So this is exactly where Sensai steps in
and where Sensai is able to detect these

303
00:20:37.270 --> 00:20:42.550
<v Konstantin Kobel>faults before they actually happen, before
they, for example, um cause a downtime in

304
00:20:42.550 --> 00:20:43.189
<v Konstantin Kobel>your production.

305
00:20:46.219 --> 00:20:52.540
<v Speaker 2>And how do you typically see integration
pay off for SMEs both in numbers and in

306
00:20:52.540 --> 00:20:52.780
<v Speaker 2>impact?

307
00:20:52.900 --> 00:20:57.540
<v Speaker 2>What is the return on investment that
companies can expect from integration?

308
00:20:58.479 --> 00:21:03.410
<v Konstantin Kobel>Um, I think the return of investment that
you can expect from integration includes,

309
00:21:03.510 --> 00:21:08.949
<v Konstantin Kobel>first of all, operating costs, because um
you have easier data handling and the use

310
00:21:08.949 --> 00:21:12.829
<v Konstantin Kobel>case I talked about in the beginning,
where it takes 9 man days to collect some data

311
00:21:12.829 --> 00:21:14.709
<v Konstantin Kobel>and to extract some information from it.

312
00:21:15.069 --> 00:21:20.109
<v Konstantin Kobel>You don't have that anymore, so you have
easier data handling, here you are less

313
00:21:20.109 --> 00:21:25.349
<v Konstantin Kobel>resource intensive, um, you have less
systems that you need to operate and also

314
00:21:25.349 --> 00:21:27.709
<v Konstantin Kobel>worry about in the sense of cybersecurity.

315
00:21:28.250 --> 00:21:33.660
<v Konstantin Kobel>Um, you can expect fewer downtimes because
of cases like I said with Sensa, where

316
00:21:33.660 --> 00:21:39.959
<v Konstantin Kobel>you really analyze your machines, you
understand your machines better, and thanks to

317
00:21:40.140 --> 00:21:45.260
<v Konstantin Kobel>data transparency, uh, you also have the
potential for analytics, which can again

318
00:21:45.260 --> 00:21:49.260
<v Konstantin Kobel>find problems not only in the machine, but
also in the in the process and in the

319
00:21:49.260 --> 00:21:53.410
<v Konstantin Kobel>production, and therefore you can also
improve productivity thanks to a better

320
00:21:53.410 --> 00:21:55.780
<v Konstantin Kobel>understanding of your machines and of your
whole process.

321
00:21:57.180 --> 00:22:04.150
<v Konstantin Kobel>Um, so I think this optimization potential
and also the, the the resources you

322
00:22:04.150 --> 00:22:06.910
<v Konstantin Kobel>save with integration are one return on
investment.

323
00:22:07.560 --> 00:22:12.920
<v Konstantin Kobel>Um, some key phrases that we often use
here are reliability and availability.

324
00:22:13.739 --> 00:22:19.260
<v Konstantin Kobel>Um, but apart from this, another aspect
that you gain is that you, and I think also

325
00:22:19.260 --> 00:22:24.260
<v Konstantin Kobel>it's hard to put into numbers, but I think
you also gain innovation because, um, as

326
00:22:24.260 --> 00:22:28.410
<v Konstantin Kobel>I said in the beginning already, um,
integration and also the data behind you get

327
00:22:29.449 --> 00:22:33.770
<v Konstantin Kobel>really helps you to better understand your
product and to find all the improvements.

328
00:22:34.180 --> 00:22:37.780
<v Konstantin Kobel>So you find improvements in your
production process, in the product itself, also in

329
00:22:37.780 --> 00:22:39.180
<v Konstantin Kobel>the product quality, for example.

330
00:22:39.569 --> 00:22:44.130
<v Konstantin Kobel>And there's also another return of
investment that you can gain from integration.

331
00:22:45.270 --> 00:22:50.550
<v Konstantin Kobel>Um, but in general, also beyond numbers,
the return of investment also comes in

332
00:22:50.550 --> 00:22:53.099
<v Konstantin Kobel>terms of agility and also resilience.

333
00:22:53.550 --> 00:22:57.530
<v Konstantin Kobel>So for, as you said in the beginning,
small and medium enterprises, they can pivot

334
00:22:57.530 --> 00:23:01.829
<v Konstantin Kobel>faster in response to market changes, for
example, and they can also make better and

335
00:23:01.829 --> 00:23:06.670
<v Konstantin Kobel>more informed decisions based on data and
are less prone also to cybersecurity

336
00:23:06.670 --> 00:23:07.329
<v Konstantin Kobel>threats, for example.

337
00:23:10.790 --> 00:23:15.699
<v Speaker 2>Yeah, and let's not forget that in today's
market, being agile is actually its own

338
00:23:15.699 --> 00:23:20.900
<v Speaker 2>RI, so the faster you respond to change,
the more resilient your business becomes.

339
00:23:25.140 --> 00:23:28.609
<v Speaker 2>OK, so maybe let's end with something more
fun.

340
00:23:29.489 --> 00:23:32.930
<v Speaker 2>Uh, maybe you can share with me what was
the coolest project that you did lately.

341
00:23:33.510 --> 00:23:37.479
<v Konstantin Kobel>Yeah, um, one project that is really stuck
in my mind is a project from Austria.

342
00:23:37.939 --> 00:23:42.770
<v Konstantin Kobel>Um, this project included, first of all,
collecting data from multiple drive systems

343
00:23:42.869 --> 00:23:45.050
<v Konstantin Kobel>and collected in one central place.

344
00:23:45.510 --> 00:23:48.780
<v Konstantin Kobel>Then we also wanted to analyze this data
with our solution for predictive

345
00:23:48.780 --> 00:23:49.189
<v Konstantin Kobel>maintenance.

346
00:23:49.270 --> 00:23:50.949
<v Konstantin Kobel>I already talked about it, it's called
Sensa.

347
00:23:51.569 --> 00:23:56.160
<v Konstantin Kobel>And then we also wanted to proactively
support the customer in the case of detected

348
00:23:56.160 --> 00:23:59.790
<v Konstantin Kobel>anomalies, and for this we use a service
solution called Shopppla monitoring

349
00:23:59.790 --> 00:24:00.250
<v Konstantin Kobel>services.

350
00:24:01.010 --> 00:24:06.020
<v Konstantin Kobel>So as a result, what we did is we first of
all collected the data from the drive

351
00:24:06.020 --> 00:24:10.979
<v Konstantin Kobel>systems, then we provided this data to
this predictive maintenance solution, Sensor,

352
00:24:11.670 --> 00:24:16.469
<v Konstantin Kobel>and Sensori built a baseline and once this
data or the parameters for the machine

353
00:24:16.890 --> 00:24:19.770
<v Konstantin Kobel>are running out of bounds, Sensai detected
an anomaly.

354
00:24:20.239 --> 00:24:25.719
<v Konstantin Kobel>But we didn't want to stop there and just
point the customer towards some something

355
00:24:25.719 --> 00:24:26.910
<v Konstantin Kobel>wrong in their production.

356
00:24:27.199 --> 00:24:30.109
<v Konstantin Kobel>We also wanted to actually support them in
the case of something wrong.

357
00:24:30.479 --> 00:24:34.550
<v Konstantin Kobel>This is where Shuffle monitoring services
comes into play, because what we can do

358
00:24:34.550 --> 00:24:39.270
<v Konstantin Kobel>with this is, first of all, you can get
customized notifications when something is

359
00:24:39.270 --> 00:24:44.939
<v Konstantin Kobel>being detected, but you also have the
possibility to request support from Siemens

360
00:24:45.119 --> 00:24:46.079
<v Konstantin Kobel>with the click of a button.

361
00:24:46.609 --> 00:24:50.170
<v Konstantin Kobel>So whenever something occurs in your
production process and you're not quite sure

362
00:24:50.170 --> 00:24:54.650
<v Konstantin Kobel>how to handle it, you can just click a
button and the Siemens service engineer will

363
00:24:54.650 --> 00:24:55.329
<v Konstantin Kobel>be notified.

364
00:24:55.609 --> 00:25:00.689
<v Konstantin Kobel>They will get a ticket and they will come
help you as soon as possible and we'll

365
00:25:00.689 --> 00:25:02.160
<v Konstantin Kobel>resolve the issue with you.

366
00:25:02.569 --> 00:25:07.209
<v Konstantin Kobel>So you can really utilize also Siemens
service engineers in your maintenance process

367
00:25:07.209 --> 00:25:07.410
<v Konstantin Kobel>here.

368
00:25:09.439 --> 00:25:14.760
<v Speaker 2>Wow, yeah, I mean, this is integration in
action from data collection to real-time

369
00:25:14.760 --> 00:25:20.530
<v Speaker 2>insights to proactive service, and I think
it's a great reminder of what is possible

370
00:25:20.530 --> 00:25:23.859
<v Speaker 2>when you actually combine technology with
the right mindset.

371
00:25:24.319 --> 00:25:28.140
<v Konstantin Kobel>Yeah, I mean, that's exactly why this
project came into my head when you asked me

372
00:25:28.140 --> 00:25:32.359
<v Konstantin Kobel>this question because um it's, I like this
product so much because it really

373
00:25:32.359 --> 00:25:35.680
<v Konstantin Kobel>includes all of the latest technology that
we always talk about at Siemens.

374
00:25:35.930 --> 00:25:40.329
<v Konstantin Kobel>And it shows how you can combine this
technology to really provide a great benefit

375
00:25:40.329 --> 00:25:41.099
<v Konstantin Kobel>to the customer.

376
00:25:41.609 --> 00:25:45.290
<v Konstantin Kobel>And I think it also shows that, you know,
integration doesn't always have to be the

377
00:25:45.290 --> 00:25:48.469
<v Konstantin Kobel>whole company, it doesn't always have to
be a huge project.

378
00:25:48.729 --> 00:25:53.209
<v Konstantin Kobel>It can really provide a benefit for every
company, even starting with just a few

379
00:25:53.209 --> 00:25:59.329
<v Konstantin Kobel>machines, and no matter which way you
choose, Siemens has the right sized portfolio,

380
00:25:59.410 --> 00:26:00.930
<v Konstantin Kobel>the right sized solution for you.

381
00:26:02.229 --> 00:26:04.069
<v Speaker 2>Absolutely, absolutely.

382
00:26:04.510 --> 00:26:08.670
<v Speaker 2>Uh, would you like to close the topic of
integration with some final words from your

383
00:26:08.670 --> 00:26:09.170
<v Speaker 2>side?

384
00:26:09.550 --> 00:26:10.689
<v Konstantin Kobel>Yeah, I would love to.

385
00:26:11.189 --> 00:26:16.329
<v Konstantin Kobel>Um, I mean, digital transformation, as I
just said it, it always sounds huge.

386
00:26:16.390 --> 00:26:20.099
<v Konstantin Kobel>It always sounds like you're changing your
whole company, like your whole production

387
00:26:20.099 --> 00:26:24.150
<v Konstantin Kobel>process is going to be different after
your project is finished, but I really think

388
00:26:24.150 --> 00:26:29.430
<v Konstantin Kobel>that small steps can really provide
already huge benefit, as I already talked about

389
00:26:29.430 --> 00:26:31.050
<v Konstantin Kobel>in the, in the questions before.

390
00:26:31.589 --> 00:26:37.989
<v Konstantin Kobel>Um, so I know integration is oftentimes
not the number one priority in companies,

391
00:26:38.449 --> 00:26:42.849
<v Konstantin Kobel>but especially when you have daily
business running, you need to keep the machinery

392
00:26:42.849 --> 00:26:43.469
<v Konstantin Kobel>alive.

393
00:26:43.920 --> 00:26:48.589
<v Konstantin Kobel>Um, but really, even small steps,
connecting a few machines to a centralized

394
00:26:48.589 --> 00:26:51.729
<v Konstantin Kobel>integration solution can already provide
huge benefits.

395
00:26:52.089 --> 00:26:55.449
<v Konstantin Kobel>And yeah, that's kind of the final message
I would give.

396
00:26:55.959 --> 00:27:01.160
<v Konstantin Kobel>Um, please really think about the
integration and um even small steps can really

397
00:27:01.160 --> 00:27:01.569
<v Konstantin Kobel>help here.

398
00:27:03.380 --> 00:27:08.410
<v Speaker 2>Well, thank you very much, Konstantin, for
joining us today and for our listeners,

399
00:27:08.489 --> 00:27:12.530
<v Speaker 2>if you have any questions or want to dive
deep, deeper into your specific use case,

400
00:27:12.689 --> 00:27:14.969
<v Speaker 2>please don't hesitate to reach out to us.

401
00:27:15.290 --> 00:27:16.709
<v Speaker 2>We would love to hear from you.

402
00:27:17.270 --> 00:27:19.969
<v Speaker 2>Until next time, take care and keep
innovating.

403
00:27:22.160 --> 00:27:27.119
<v Speaker 1>Please like and subscribe on all major
podcast channels and find out more about

404
00:27:27.119 --> 00:27:30.500
<v Speaker 1>Sensi predictive maintenance at
Siemens.com.
