WEBVTT
Language: en-US

1
00:00:00.009 --> 00:00:06.239
<v Speaker 1>You know, why can't we have human-centric
AI models for automation and be dedicated

2
00:00:06.239 --> 00:00:12.930
<v Speaker 1>to creating an ecosystem with no losers,
benefiting everyone from executives and

3
00:00:12.930 --> 00:00:15.210
<v Speaker 1>shareholders to workers and consumers.

4
00:00:31.250 --> 00:00:36.130
<v Speaker 2>Welcome to a brand new episode of our
podcast, Human and AI Mind, Machines and the

5
00:00:36.130 --> 00:00:37.040
<v Speaker 2>Grave in the sand.

6
00:00:37.569 --> 00:00:42.130
<v Speaker 3>Thanks for tuning in again to geek out
with us over the fascinating field of AI and

7
00:00:42.130 --> 00:00:44.470
<v Speaker 3>machine learning and the role of humans in
it.

8
00:00:45.189 --> 00:00:49.200
<v Speaker 3>Today, we're super happy to have Mozen
Rezayed with us.

9
00:00:49.509 --> 00:00:54.830
<v Speaker 3>Mozen is the Chief Solutions architect at
Siemens Digital-Industries Software and an

10
00:00:54.830 --> 00:00:57.810
<v Speaker 3>adjunct professor at the University of
Cincinnati.

11
00:00:58.150 --> 00:01:03.229
<v Speaker 3>So Mosen, welcome to the show and thanks
so much for taking some time to join this

12
00:01:03.229 --> 00:01:04.010
<v Speaker 3>little podcast.

13
00:01:04.470 --> 00:01:06.510
<v Speaker 3>How are you and where do we catch you
today?

14
00:01:07.860 --> 00:01:12.660
<v Speaker 1>Hi, uh, uh, everyone, it's a pleasure to
be here with you.

15
00:01:12.739 --> 00:01:19.519
<v Speaker 1>Um, I, um, live in, uh, Cincinnati, Ohio
in the United States right now, but,

16
00:01:19.540 --> 00:01:26.059
<v Speaker 1>uh, my path to get here is, uh,
interesting in that I was born in Iran and came to

17
00:01:26.059 --> 00:01:28.470
<v Speaker 1>the States when I was, uh, 17.

18
00:01:28.660 --> 00:01:35.059
<v Speaker 1>I attended the University of California,
the Irvine campus, and then, uh, my studies

19
00:01:35.059 --> 00:01:40.360
<v Speaker 1>at the University of Kentucky with a PhD
in engineering mechanics.

20
00:01:40.809 --> 00:01:45.970
<v Speaker 1>I was then hired by a company called the
Structural Dynamics Research Corporation,

21
00:01:46.050 --> 00:01:50.050
<v Speaker 1>which was eventually acquired by Siemens.

22
00:01:50.180 --> 00:01:56.739
<v Speaker 1>So I've worked within the same
organization for over 36 years and now lead the

23
00:01:56.739 --> 00:02:03.730
<v Speaker 1>advanced Solutions Group with the mandate
of doing R&amp;D across the entire portfolio.

24
00:02:04.160 --> 00:02:09.110
<v Speaker 1>Of uh Siemens Joe Industry Software or the
IISW as we call it.

25
00:02:09.600 --> 00:02:13.960
<v Speaker 1>I'm also an adjunct full professor at the
University of Cincinnati, as you

26
00:02:13.960 --> 00:02:20.500
<v Speaker 1>mentioned, and started a nonprofit
organization called uh Omi USA about

27
00:02:20.649 --> 00:02:26.839
<v Speaker 1>12 years ago to raise the income level of
poor farmers by introducing affordable and

28
00:02:27.580 --> 00:02:29.139
<v Speaker 1>Sustainable solutions.

29
00:02:29.339 --> 00:02:36.300
<v Speaker 1>So that's sort of a brief version of how I
got here, and I truly believe that we

30
00:02:36.300 --> 00:02:41.259
<v Speaker 1>need more conversations about the role and
circumstances of humans in everything we

31
00:02:41.259 --> 00:02:42.699
<v Speaker 1>do, including.

32
00:02:43.179 --> 00:02:44.559
<v Speaker 1>So again, thanks for having me.

33
00:02:46.050 --> 00:02:46.399
<v Speaker 2>I do it.

34
00:02:46.910 --> 00:02:49.110
<v Speaker 2>That's, that's people, passion, purpose.

35
00:02:49.190 --> 00:02:50.240
<v Speaker 2>They're all in one.

36
00:02:50.470 --> 00:02:51.279
<v Speaker 2>I can't believe it, dude.

37
00:02:51.710 --> 00:02:53.350
<v Speaker 2>That's super awesome already, right?

38
00:02:53.429 --> 00:02:57.509
<v Speaker 2>And I guess we have in, in, in, in Germany
we have a saying called ein urgestein.

39
00:02:57.669 --> 00:03:01.809
<v Speaker 2>That's typical, but sounds harsh, but it
actually means an English institution,

40
00:03:01.990 --> 00:03:02.169
<v Speaker 2>right?

41
00:03:02.429 --> 00:03:02.869
<v Speaker 2>You are there.

42
00:03:02.960 --> 00:03:07.660
<v Speaker 2>In the PLM space, right, product life
cycle management space and also software space

43
00:03:07.800 --> 00:03:11.580
<v Speaker 2>and also innovation space for, for quite a
long, right?

44
00:03:11.960 --> 00:03:14.279
<v Speaker 2>How do you see if you reflect a bit on the
past, right?

45
00:03:14.360 --> 00:03:18.479
<v Speaker 2>And you know, in the past years, how, how
do you see the, the software business and

46
00:03:18.479 --> 00:03:19.100
<v Speaker 2>the industry?

47
00:03:19.399 --> 00:03:21.339
<v Speaker 2>How has that involved?

48
00:03:21.399 --> 00:03:25.880
<v Speaker 2>And are there, do you identify certain
major milestones, um, along this path?

49
00:03:27.050 --> 00:03:28.210
<v Speaker 1>Um, thanks, Ali.

50
00:03:28.369 --> 00:03:29.630
<v Speaker 1>You're, you're too kind.

51
00:03:30.369 --> 00:03:36.169
<v Speaker 1>One, observation I would like to share
with you in my journey with Siemens, uh, is

52
00:03:36.169 --> 00:03:40.869
<v Speaker 1>that the rate of change, which, uh,
historically was linear.

53
00:03:41.419 --> 00:03:44.059
<v Speaker 1>It is now exponential, uh, in my opinion.

54
00:03:44.619 --> 00:03:49.860
<v Speaker 1>Reasons for this include exponential
growth in the amount of computing power and

55
00:03:49.860 --> 00:03:56.570
<v Speaker 1>available data for creating amazing AI
models, doing complex simulations,

56
00:03:56.899 --> 00:04:03.649
<v Speaker 1>creating very large, realistic 3D models
called digital twins, and many more

57
00:04:03.649 --> 00:04:04.240
<v Speaker 1>examples.

58
00:04:04.869 --> 00:04:11.610
<v Speaker 1>Now, a couple of indicators for this in
our world today that would hopefully

59
00:04:11.610 --> 00:04:17.510
<v Speaker 1>make believers out of the listeners is
that it's sort of amazing to me to think that

60
00:04:17.510 --> 00:04:23.549
<v Speaker 1>China can identify any of their 1.4
billion citizens in about two

61
00:04:23.549 --> 00:04:27.390
<v Speaker 1>seconds using AI-based facial recognition.

62
00:04:28.019 --> 00:04:33.859
<v Speaker 1>Intel has more than 7 billion transistors
on a single chip.

63
00:04:34.459 --> 00:04:40.220
<v Speaker 1>You know, it took like 30 years to go from
2 transistors in the 1950s to

64
00:04:40.220 --> 00:04:44.859
<v Speaker 1>20,000 transistors, but then all of a
sudden we jumped to 7 billion.

65
00:04:45.649 --> 00:04:51.540
<v Speaker 1>What is equally amazing to me is that the
rate of adoption of technology is also

66
00:04:51.540 --> 00:04:51.959
<v Speaker 1>changing.

67
00:04:52.679 --> 00:04:59.399
<v Speaker 1>You probably know that televisions were
invented in 1925, but it

68
00:04:59.399 --> 00:05:04.820
<v Speaker 1>took 25 years or 25% of Americans to own a
TV.

69
00:05:05.910 --> 00:05:12.149
<v Speaker 1>Now, compare that to smartphones that were
invented in 2007, and it only took 2

70
00:05:12.149 --> 00:05:17.170
<v Speaker 1>years for 25% of Americans to own a
smartphone.

71
00:05:17.600 --> 00:05:23.369
<v Speaker 1>So this exponential rate of change and the
rate of adoption of technology tells us

72
00:05:23.369 --> 00:05:28.869
<v Speaker 1>that our development, operation, and
business models.

73
00:05:29.480 --> 00:05:35.880
<v Speaker 1>Need to evolve as well because customers
now expect rapid change, and that extends

74
00:05:35.880 --> 00:05:38.279
<v Speaker 1>to the use of software in industry.

75
00:05:39.079 --> 00:05:44.380
<v Speaker 1>For example, our customers are demanding
even larger scale visualization,

76
00:05:44.510 --> 00:05:49.779
<v Speaker 1>collaboration, and simulation that's given
to them seamlessly across multiple

77
00:05:50.000 --> 00:05:52.279
<v Speaker 1>geographic sites and applications.

78
00:05:52.839 --> 00:05:56.459
<v Speaker 1>We also see that software as a service.

79
00:05:56.700 --> 00:06:03.410
<v Speaker 1>The so-called SASS is becoming the
delivery method mainly for ease of access,

80
00:06:03.739 --> 00:06:06.769
<v Speaker 1>scalability, and integration reasons.

81
00:06:07.140 --> 00:06:14.059
<v Speaker 1>These trends of rapid change in
development, operation, and business models must

82
00:06:14.059 --> 00:06:20.410
<v Speaker 1>continue in order for us, Siemens in
general and Siemens, the IISW in particular, to

83
00:06:20.410 --> 00:06:22.940
<v Speaker 1>successfully answer the demands of the
market.

84
00:06:24.380 --> 00:06:24.890
<v Speaker 2>Very well

85
00:06:24.890 --> 00:06:25.250
<v Speaker 3>put.

86
00:06:25.660 --> 00:06:30.440
<v Speaker 3>Yeah, super interesting and impressive
facts and yeah, and valid points.

87
00:06:30.850 --> 00:06:35.609
<v Speaker 3>Most of you, you have to know about me, I,
I love quotes and there's a very nice

88
00:06:35.609 --> 00:06:36.730
<v Speaker 3>quote from Peter F.

89
00:06:36.890 --> 00:06:41.709
<v Speaker 3>Drucker who said, if you want something
new, you have to stop doing something old.

90
00:06:42.260 --> 00:06:47.220
<v Speaker 3>So challenging the status quo and
exploring the new is something I personally really

91
00:06:47.220 --> 00:06:47.720
<v Speaker 3>love.

92
00:06:47.940 --> 00:06:52.839
<v Speaker 3>And I would be super curious to know, is
there any quote that you are in particular

93
00:06:53.100 --> 00:06:56.359
<v Speaker 3>interested in or that, and that you would
like to share with the audience?

94
00:06:57.140 --> 00:06:59.239
<v Speaker 1>Yeah, this, this answer is, is easy.

95
00:06:59.420 --> 00:07:05.339
<v Speaker 1>Um, my uh idol is Albert Einstein, and he
has many quotes.

96
00:07:05.380 --> 00:07:07.380
<v Speaker 1>I actually, I can show you around my
office.

97
00:07:07.459 --> 00:07:12.980
<v Speaker 1>I have them on the walls, uh, the quotes
from him that I, I really like many of

98
00:07:12.980 --> 00:07:19.480
<v Speaker 1>those, but the one that always stays with
me is, if you can't explain it simply,

99
00:07:20.059 --> 00:07:22.040
<v Speaker 1>you don't understand it well enough.

100
00:07:22.820 --> 00:07:27.980
<v Speaker 1>So, whether I'm teaching my students at
the university or when I try to explain

101
00:07:27.980 --> 00:07:28.959
<v Speaker 1>something new.

102
00:07:29.380 --> 00:07:35.179
<v Speaker 1>And exciting to colleagues, I try my best
to explain it as simply and plainly as I

103
00:07:35.179 --> 00:07:40.130
<v Speaker 1>can without using, you know, complex
concepts and big words.

104
00:07:40.459 --> 00:07:44.010
<v Speaker 1>By the way, I also like the code of go
something like this.

105
00:07:44.529 --> 00:07:46.040
<v Speaker 1>If we knew what we were doing.

106
00:07:46.429 --> 00:07:48.209
<v Speaker 1>It wouldn't be called research.

107
00:07:50.769 --> 00:07:55.790
<v Speaker 1>Quite often to the people around me
because they always want me to define everything

108
00:07:55.790 --> 00:07:59.630
<v Speaker 1>for them, and I always quote this from
Einstein to them.

109
00:08:00.809 --> 00:08:04.190
<v Speaker 2>Yeah, I will use it directly tomorrow if
somebody's questioning again to research

110
00:08:05.910 --> 00:08:06.279
<v Speaker 2>and apply to research.

111
00:08:07.649 --> 00:08:11.290
<v Speaker 2>But speaking of software, right, software
in current times, you know, I love this,

112
00:08:11.450 --> 00:08:17.049
<v Speaker 2>this, it has this open source movement
actually, entire young, young generation is

113
00:08:17.049 --> 00:08:20.609
<v Speaker 2>pushing their ideas, you know, as fast as
something want to.

114
00:08:20.869 --> 00:08:22.760
<v Speaker 2>Hub on Archive X, right?

115
00:08:23.190 --> 00:08:27.399
<v Speaker 2>If even before conferences, even if you
thought like conferencing, you know,

116
00:08:27.630 --> 00:08:31.320
<v Speaker 2>research and a lot of research
conferencing, you know, they already uploaded this

117
00:08:31.320 --> 00:08:35.679
<v Speaker 2>stuff along with code, along with, you
know, it's beauty of, of sharing, and this

118
00:08:35.679 --> 00:08:40.159
<v Speaker 2>sharing fueled from my perspective,
significantly also the, the progress in machine

119
00:08:40.159 --> 00:08:40.679
<v Speaker 2>learning.

120
00:08:41.320 --> 00:08:46.719
<v Speaker 2>How do you see the role of open source
within a corporation and maybe also along the

121
00:08:46.719 --> 00:08:50.280
<v Speaker 2>line of the, the PM and in DI software
industry?

122
00:08:51.719 --> 00:08:57.609
<v Speaker 1>I really, truly believe that one of the
drivers for the exponential rate of change I

123
00:08:57.609 --> 00:09:02.619
<v Speaker 1>was talking about in the last two decades
is the open source software.

124
00:09:03.090 --> 00:09:07.929
<v Speaker 1>You know, my own team couldn't do the
amount of feasibility studies that we have

125
00:09:07.929 --> 00:09:14.289
<v Speaker 1>done in the last 3 years if open source AI
NML software like Tensorflow and

126
00:09:14.289 --> 00:09:17.020
<v Speaker 1>PyTorch were not available to us.

127
00:09:17.489 --> 00:09:22.690
<v Speaker 1>Now, at Siemens, we have practiced this
open source concept, but we need to do more,

128
00:09:22.929 --> 00:09:29.929
<v Speaker 1>especially with our PLM software at the
ISW, if and when it could benefit us as

129
00:09:29.929 --> 00:09:31.239
<v Speaker 1>well as our customers.

130
00:09:31.369 --> 00:09:38.369
<v Speaker 1>For instance, let's look at JT, which is
the de facto industry 3D model format

131
00:09:38.369 --> 00:09:41.609
<v Speaker 1>we created, got through the ISOL
certification.

132
00:09:42.219 --> 00:09:45.119
<v Speaker 1>And then offered to the entire CATD
industry.

133
00:09:45.500 --> 00:09:45.849
<v Speaker 1>That was great.

134
00:09:46.849 --> 00:09:53.700
<v Speaker 1>However, I, I think it would have been
even greater if we had also open sourced the

135
00:09:53.700 --> 00:09:54.760
<v Speaker 1>JT toolkit.

136
00:09:55.049 --> 00:10:01.460
<v Speaker 1>This is the C+ API library that enables
read-write access to all data within the

137
00:10:01.460 --> 00:10:02.099
<v Speaker 1>JT.

138
00:10:02.739 --> 00:10:08.700
<v Speaker 1>Open source and offered it for free,
similar to what other formats like UST have

139
00:10:08.700 --> 00:10:08.979
<v Speaker 1>done.

140
00:10:09.710 --> 00:10:15.250
<v Speaker 1>The result would have been a much larger
adoption of this format beyond our

141
00:10:15.750 --> 00:10:20.489
<v Speaker 1>immediate industry, such as in game
engines like Unity 3D.

142
00:10:20.809 --> 00:10:26.729
<v Speaker 1>This would have opened many more doors, in
my opinion, to us and to our customers.

143
00:10:27.109 --> 00:10:33.710
<v Speaker 1>We now, I believe, need to do the same
with the industrial AI related tools we

144
00:10:33.710 --> 00:10:38.090
<v Speaker 1>created, similar to what Fallo and Pytorch
have done.

145
00:10:38.580 --> 00:10:44.500
<v Speaker 1>Because at the end, Siemens will win since
we understand better than anyone else the

146
00:10:44.500 --> 00:10:45.539
<v Speaker 1>needs of the industry.

147
00:10:46.510 --> 00:10:51.919
<v Speaker 1>Of course, shouldn't and won't open
everything up because intellectual property

148
00:10:51.919 --> 00:10:52.760
<v Speaker 1>needs to be protected.

149
00:10:52.840 --> 00:10:53.640
<v Speaker 1>I understand that.

150
00:10:54.260 --> 00:10:59.679
<v Speaker 1>But I'm certain we can figure out a
strategic way of accomplishing a win-win

151
00:10:59.729 --> 00:11:00.059
<v Speaker 1>situation.

152
00:11:00.539 --> 00:11:07.419
<v Speaker 1>You know, if Google and Facebook can
figure out in a B2C context, how to open

153
00:11:07.419 --> 00:11:13.960
<v Speaker 1>source what is central to their
environment and AI environment, I'm sure we at

154
00:11:13.960 --> 00:11:20.020
<v Speaker 1>Siemens at the IISW can do it in a B2B
context for the PLM community.

155
00:11:21.719 --> 00:11:22.919
<v Speaker 2>That's, that's nicely put.

156
00:11:23.080 --> 00:11:25.039
<v Speaker 2>That's actually, you know, that's nicely
put.

157
00:11:25.119 --> 00:11:28.000
<v Speaker 2>I think we have a long, a bit of a journey
still ahead, isn't it?

158
00:11:28.380 --> 00:11:28.940
<v Speaker 2>We're going there, yeah,

159
00:11:29.469 --> 00:11:29.549
<v Speaker 1>absolutely.

160
00:11:30.679 --> 00:11:33.659
<v Speaker 3>There's so many potentials for synergies
actually.

161
00:11:34.000 --> 00:11:39.080
<v Speaker 3>But speaking of, uh, potentials, where do
you see the role of AI and machine

162
00:11:39.080 --> 00:11:41.919
<v Speaker 3>learning in the Siemens software and PLM?

163
00:11:42.239 --> 00:11:48.080
<v Speaker 3>Can you maybe share some use cases there,
maybe even 3 or more that you are

164
00:11:48.080 --> 00:11:49.780
<v Speaker 3>particularly passionate about.

165
00:11:50.309 --> 00:11:54.690
<v Speaker 1>I think this goes to really the topic of
this podcast.

166
00:11:55.229 --> 00:12:01.669
<v Speaker 1>I think generally speaking, in, in PLM AI
enabled machines and software are

167
00:12:01.669 --> 00:12:04.590
<v Speaker 1>augmenting human workers' capabilities.

168
00:12:04.909 --> 00:12:11.909
<v Speaker 1>AI enabled systems do what they can do
best, which includes like analyzing huge data

169
00:12:11.909 --> 00:12:15.330
<v Speaker 1>sets, generating lots of design
alternatives.

170
00:12:15.750 --> 00:12:21.150
<v Speaker 1>Answering questions about those designs,
performing repetitive tasks, handling

171
00:12:21.150 --> 00:12:22.520
<v Speaker 1>routine cases.

172
00:12:23.229 --> 00:12:29.890
<v Speaker 1>On the other hand, humans do what they do
best, which includes resolving ambiguous

173
00:12:29.989 --> 00:12:35.150
<v Speaker 1>information, performing delicate tasks,
and we'll talk about this hopefully later.

174
00:12:35.669 --> 00:12:42.450
<v Speaker 1>Choosing among many alternatives based on
aesthetics and or marketing goals,

175
00:12:42.940 --> 00:12:47.719
<v Speaker 1>selling what is created and dealing with
dissatisfied customers.

176
00:12:48.809 --> 00:12:55.280
<v Speaker 1>Now, specific to DISW, we actually have
many examples of such AI

177
00:12:55.280 --> 00:13:02.179
<v Speaker 1>enabled software from Mendix and
MindSphere applications to Team Center and X

178
00:13:02.179 --> 00:13:02.710
<v Speaker 1>products.

179
00:13:03.109 --> 00:13:09.320
<v Speaker 1>To calibrate, to process, simulate, and MM
software, and I'm sure I'm

180
00:13:09.320 --> 00:13:15.809
<v Speaker 1>forgetting other products that have some
sort of AI capability at the ISW,

181
00:13:16.960 --> 00:13:22.820
<v Speaker 1>but I want to give you more details about
3 capabilities in these products that I'm

182
00:13:23.599 --> 00:13:24.979
<v Speaker 1>personally familiar with.

183
00:13:25.719 --> 00:13:29.659
<v Speaker 1>The first one, which is actually in the
hands of our customers today.

184
00:13:30.309 --> 00:13:33.510
<v Speaker 1>It's called adaptive UI in our NX
products.

185
00:13:33.590 --> 00:13:37.109
<v Speaker 1>This is our modeling system, 3D modeling
system.

186
00:13:37.969 --> 00:13:44.119
<v Speaker 1>Very complicated product, many hundreds if
not thousands of menus and submenus,

187
00:13:44.650 --> 00:13:50.809
<v Speaker 1>and what we have been able to accomplish
is with a high degree of accuracy, be able

188
00:13:50.809 --> 00:13:57.599
<v Speaker 1>to predict what the next command that the
user is going to need and bring it to them

189
00:13:57.599 --> 00:14:00.450
<v Speaker 1>rather than making them go and try to find
it.

190
00:14:00.979 --> 00:14:07.659
<v Speaker 1>And again, the customers just love this
capability, and we use Markov chains, and

191
00:14:07.659 --> 00:14:12.630
<v Speaker 1>now we're kind of thinking about even
evolving that perhaps to a deep learning model

192
00:14:12.630 --> 00:14:18.940
<v Speaker 1>for this, but the point is that even
something that seems very rudimentary could

193
00:14:18.940 --> 00:14:20.820
<v Speaker 1>become a huge success.

194
00:14:21.630 --> 00:14:27.989
<v Speaker 1>The next one that we are working on right
now is anomaly detection and repair using

195
00:14:27.989 --> 00:14:31.869
<v Speaker 1>knowledge graphs, which I hope you guys
ask me a question about that because I want

196
00:14:31.869 --> 00:14:37.349
<v Speaker 1>to explain it more, but we use knowledge
graphs to integrate our Teamcenter

197
00:14:37.349 --> 00:14:44.070
<v Speaker 1>MindSphere and an ERP system from a
partner together, and we actually can

198
00:14:44.070 --> 00:14:47.109
<v Speaker 1>now in a single environment in a browser.

199
00:14:47.510 --> 00:14:50.440
<v Speaker 1>Allow a user to monitor an entire factory.

200
00:14:50.789 --> 00:14:55.739
<v Speaker 1>Detect when there are a broken part or a
machine that's not behaving properly.

201
00:14:56.140 --> 00:15:00.539
<v Speaker 1>Get from the sensors the part that is
causing the problem.

202
00:15:00.909 --> 00:15:03.450
<v Speaker 1>Get information and metadata about that
part.

203
00:15:03.950 --> 00:15:05.750
<v Speaker 1>Order that part.

204
00:15:05.989 --> 00:15:12.130
<v Speaker 1>Then once it's delivered through that same
browser, get instructions for disassembly

205
00:15:12.549 --> 00:15:14.669
<v Speaker 1>and assembly of the part.

206
00:15:15.030 --> 00:15:17.510
<v Speaker 1>And then continue monitoring.

207
00:15:18.030 --> 00:15:24.789
<v Speaker 1>So this is really tremendous, and it's all
enabled by AI and knowledge

208
00:15:24.789 --> 00:15:25.309
<v Speaker 1>graphs.

209
00:15:25.830 --> 00:15:31.030
<v Speaker 1>And the third example is uh digital
assistants, you know, these are now in a lot of

210
00:15:31.030 --> 00:15:35.669
<v Speaker 1>our products being, being developed, but
the, the one that I'm actually directly

211
00:15:35.669 --> 00:15:41.369
<v Speaker 1>involved in is with our mentor graphics
colleagues in a product called Capital where

212
00:15:41.700 --> 00:15:48.190
<v Speaker 1>harness manufacturing is complex products
and for the foreseeable future, it's not

213
00:15:48.190 --> 00:15:52.349
<v Speaker 1>going to be automated because putting
these wires into these small pins.

214
00:15:53.190 --> 00:15:58.599
<v Speaker 1>At least for as long as we could see it
needs to be done by humans, and humans, of

215
00:15:58.599 --> 00:16:05.200
<v Speaker 1>course, make mistakes, and mistakes are
very costly to try to find out a

216
00:16:05.200 --> 00:16:11.599
<v Speaker 1>mistake in a harness which is bundles of
wires in your cars or planes or ships

217
00:16:11.900 --> 00:16:18.020
<v Speaker 1>after the fact is a daunting task, and we
were told that if we could even save

218
00:16:18.320 --> 00:16:21.960
<v Speaker 1>1%, reduce the number of errors by 1%.

219
00:16:23.590 --> 00:16:25.679
<v Speaker 1>That would save companies up to $10
million.

220
00:16:26.090 --> 00:16:31.219
<v Speaker 1>So we are now using head-mounted devices.

221
00:16:31.570 --> 00:16:37.090
<v Speaker 1>It could be a Google Glass or HoloLens,
and we are using the camera to not only

222
00:16:37.090 --> 00:16:41.969
<v Speaker 1>bring the work instructions to the users,
but also monitor them as they follow those

223
00:16:41.969 --> 00:16:42.950
<v Speaker 1>work instructions.

224
00:16:43.049 --> 00:16:46.650
<v Speaker 1>And if they make any mistakes or they
forget a step.

225
00:16:47.119 --> 00:16:52.349
<v Speaker 1>We can point it out to them in real time
and let them make the correction without

226
00:16:52.570 --> 00:16:56.849
<v Speaker 1>trying to figure it out after the fact,
which I say is more like finding a needle in

227
00:16:56.849 --> 00:16:57.609
<v Speaker 1>the haystack.

228
00:16:58.210 --> 00:17:04.729
<v Speaker 1>So, these are all exciting capabilities
that we are, we are developing and all of

229
00:17:04.729 --> 00:17:06.729
<v Speaker 1>them are being enabled because of AI.

230
00:17:08.459 --> 00:17:09.339
<v Speaker 2>Love it, right?

231
00:17:09.579 --> 00:17:12.170
<v Speaker 2>Po, part and super challenging for certain
pieces, right?

232
00:17:12.380 --> 00:17:12.959
<v Speaker 2>But love it.

233
00:17:13.339 --> 00:17:17.380
<v Speaker 2>But I also poke you directly with the
knowledge raft question, no question, right?

234
00:17:17.449 --> 00:17:22.449
<v Speaker 2>We, because obviously a natural reflects
in some, some kindness or, or actually

235
00:17:22.449 --> 00:17:24.339
<v Speaker 2>complexity is bombs, right?

236
00:17:24.500 --> 00:17:28.819
<v Speaker 2>This is something like bill of materials
that say that the management of, of the

237
00:17:28.819 --> 00:17:30.829
<v Speaker 2>product structure, right, for the
manufacturing stuff.

238
00:17:31.020 --> 00:17:34.979
<v Speaker 2>And, and they, these bombs like this bill
of materials can be super large, right?

239
00:17:35.060 --> 00:17:35.959
<v Speaker 2>Super complex.

240
00:17:36.625 --> 00:17:41.094
<v Speaker 2>You know, mentalities, you have, I don't
know, images, taxonomies, or, uh, you know,

241
00:17:41.224 --> 00:17:42.405
<v Speaker 2>documents attached to that.

242
00:17:42.734 --> 00:17:46.535
<v Speaker 2>How do you envision a bit going further
than maybe you can elaborate a bit on the

243
00:17:46.535 --> 00:17:49.765
<v Speaker 2>role of knowledge graphs for DII software,
right?

244
00:17:50.015 --> 00:17:53.405
<v Speaker 2>That you untangle a bit this complexity,
right?

245
00:17:53.685 --> 00:17:57.494
<v Speaker 2>Or you think it's just a hype, uh, or will
it play a role?

246
00:17:57.734 --> 00:17:59.005
<v Speaker 2>What, what's your view on that?

247
00:17:59.415 --> 00:18:00.155
<v Speaker 1>Uh, absolutely.

248
00:18:00.295 --> 00:18:03.854
<v Speaker 1>I'm so glad that you asked me about
knowledge graphs again because I want to

249
00:18:03.854 --> 00:18:04.074
<v Speaker 1>explain.

250
00:18:04.660 --> 00:18:08.640
<v Speaker 1>What I have said before and perhaps answer
this question as well.

251
00:18:09.060 --> 00:18:15.079
<v Speaker 1>You know, generally speaking, knowledge
graphs or KGs are a critical tool for

252
00:18:15.339 --> 00:18:18.880
<v Speaker 1>incorporating complex knowledge into
intelligence systems.

253
00:18:19.900 --> 00:18:25.839
<v Speaker 1>Using these KGs, knowledge is encoded in a
sort of a graph-based structure where

254
00:18:26.290 --> 00:18:32.760
<v Speaker 1>nodes represent real world entities while
edges define multiple

255
00:18:32.760 --> 00:18:34.839
<v Speaker 1>relations between these entities.

256
00:18:35.579 --> 00:18:42.420
<v Speaker 1>And in fact, KGs provide a flexible way to
capture, organize, and

257
00:18:42.420 --> 00:18:47.180
<v Speaker 1>query a large amount of multi-relational
data.

258
00:18:47.569 --> 00:18:52.390
<v Speaker 1>The type you mentioned for management of
product structure in, in manufacturing in,

259
00:18:52.400 --> 00:18:53.209
<v Speaker 1>in your question.

260
00:18:54.040 --> 00:19:00.300
<v Speaker 1>But KGs also provide a semantic-based
perspective, which is

261
00:19:00.959 --> 00:19:03.790
<v Speaker 1>essential for performing deductive
reasoning.

262
00:19:04.319 --> 00:19:10.859
<v Speaker 1>At TISW we have used KGs to integrate
several applications together and then

263
00:19:11.359 --> 00:19:15.780
<v Speaker 1>use deductive reasoning for semantic
search across these applications.

264
00:19:16.500 --> 00:19:20.900
<v Speaker 1>Or to identify anomalies and take action.

265
00:19:21.349 --> 00:19:27.040
<v Speaker 1>The example I just gave before on anomaly
detection and repair is a good indicator

266
00:19:27.040 --> 00:19:33.589
<v Speaker 1>of how KGs can help connect data from
disparate systems together and quickly

267
00:19:33.589 --> 00:19:39.069
<v Speaker 1>extract intelligence from their conceptual
relationships and mappings.

268
00:19:54.540 --> 00:20:00.319
<v Speaker 3>So, shaping AI and machine learning in
industry also demands different approaches

269
00:20:00.859 --> 00:20:02.660
<v Speaker 3>towards industrial grade, right?

270
00:20:03.020 --> 00:20:04.770
<v Speaker 3>So, what is it for you?

271
00:20:04.859 --> 00:20:10.060
<v Speaker 3>So what is industrial grade from your
perspective and how do you picture trustworthy

272
00:20:10.060 --> 00:20:10.500
<v Speaker 3>AI?

273
00:20:11.459 --> 00:20:12.300
<v Speaker 1>Well, um.

274
00:20:12.930 --> 00:20:18.359
<v Speaker 1>Now you're in my wheelhouse because I can
talk about this topic for, uh, for hours,

275
00:20:18.449 --> 00:20:20.400
<v Speaker 1>but I try not to do that.

276
00:20:21.089 --> 00:20:26.969
<v Speaker 1>I'll, I'll try my best to be brief, but,
you know, uh I, I actually did a podcast

277
00:20:26.969 --> 00:20:33.849
<v Speaker 1>with a colleague from Google about this
topic, but trustworthy AI for industrial

278
00:20:33.849 --> 00:20:40.270
<v Speaker 1>applications must be functionally robust,
abide by legal mandates and follow ethical

279
00:20:40.849 --> 00:20:41.729
<v Speaker 1>principles.

280
00:20:42.209 --> 00:20:47.630
<v Speaker 1>I, I talked about these bias issues
before, and those could have legal, ethical, and

281
00:20:47.969 --> 00:20:50.030
<v Speaker 1>robustness, ramifications.

282
00:20:50.449 --> 00:20:56.250
<v Speaker 1>And now, here, I'd just like to touch on
another sensitive topic in the short time I

283
00:20:56.250 --> 00:20:58.949
<v Speaker 1>have to focus on the ethics issues.

284
00:20:59.410 --> 00:21:06.250
<v Speaker 1>Historically, the question of ethics is
not raised in computer science

285
00:21:06.250 --> 00:21:12.869
<v Speaker 1>and software development as much as It
does in medicine, biology, psychology,

286
00:21:12.949 --> 00:21:14.430
<v Speaker 1>anthropology, etc.

287
00:21:15.390 --> 00:21:21.689
<v Speaker 1>The main reason is that up to now, human
subjects were not viewed as much affected

288
00:21:21.689 --> 00:21:25.109
<v Speaker 1>by software as these other traits.

289
00:21:25.390 --> 00:21:31.670
<v Speaker 1>However, With the advent of AI models that
we've been talking about, especially we

290
00:21:31.670 --> 00:21:38.339
<v Speaker 1>at the IISW need to pay attention to
Ethical issues because first,

291
00:21:38.660 --> 00:21:42.380
<v Speaker 1>AI models could create harmful bias.

292
00:21:42.619 --> 00:21:44.500
<v Speaker 1>We covered this before.

293
00:21:45.300 --> 00:21:48.180
<v Speaker 1>Second, AI models could be weaponized.

294
00:21:48.699 --> 00:21:53.260
<v Speaker 1>Third, AI models could allow creation of
alternate reality.

295
00:21:53.339 --> 00:21:58.859
<v Speaker 1>And fourth, AI models can replace masses
of humans as part of automation.

296
00:22:00.380 --> 00:22:07.209
<v Speaker 1>This attention to ethics is a huge change,
and in my view, software developers

297
00:22:07.209 --> 00:22:10.709
<v Speaker 1>are not ready to deal with it on their
own.

298
00:22:11.420 --> 00:22:14.410
<v Speaker 1>Um, I can give you a perfect example of
Joe Redman.

299
00:22:14.650 --> 00:22:21.369
<v Speaker 1>He was a tremendous researcher that when
he was a graduate student in 2016,

300
00:22:21.410 --> 00:22:25.650
<v Speaker 1>he developed and pioneered object
recognition algorithm that's called YOLO.

301
00:22:25.810 --> 00:22:27.270
<v Speaker 1>You only look once.

302
00:22:28.300 --> 00:22:32.619
<v Speaker 1>He revealed not too long ago that he has
stopped doing computer vision research

303
00:22:32.619 --> 00:22:37.880
<v Speaker 1>altogether because of its military and
surveillance applications.

304
00:22:38.619 --> 00:22:39.459
<v Speaker 1>That's a shame.

305
00:22:40.060 --> 00:22:46.760
<v Speaker 1>Now, some people may protest the intrusion
of ideology into

306
00:22:46.760 --> 00:22:51.959
<v Speaker 1>engineering and software development when
we talk about industrial AI ethics.

307
00:22:52.650 --> 00:22:58.780
<v Speaker 1>But we don't want our developers to deal
with these issues as a sort of personal

308
00:22:58.780 --> 00:23:02.719
<v Speaker 1>moral crisis that they need to deal with
on their own.

309
00:23:03.300 --> 00:23:10.189
<v Speaker 1>I think a more organized ethics process is
needed, and I bring this up constantly

310
00:23:10.189 --> 00:23:14.170
<v Speaker 1>during the AIS AI console meetings.

311
00:23:14.260 --> 00:23:16.579
<v Speaker 1>I'm, I'm a member of that group.

312
00:23:16.849 --> 00:23:22.709
<v Speaker 1>And we will see what happens, but I truly
believe that more attention needs to be

313
00:23:22.729 --> 00:23:24.390
<v Speaker 1>paid to ethics.

314
00:23:25.209 --> 00:23:31.569
<v Speaker 1>Of course, we want to be ethical, but also
to remove this burden from developers and

315
00:23:31.569 --> 00:23:37.239
<v Speaker 1>engineers that we have so that they know
what they should do and how they need to

316
00:23:37.239 --> 00:23:42.229
<v Speaker 1>behave to match the best practices that we
have.

317
00:23:43.579 --> 00:23:45.369
<v Speaker 2>Yeah, a humongous challenge.

318
00:23:45.530 --> 00:23:50.219
<v Speaker 2>And actually YOLO, right, you know, every,
every, I guess, PhD, you know, or at

319
00:23:50.219 --> 00:23:55.339
<v Speaker 2>least interested ML geek in Kubidivision,
right, has fine tuned some kind of YOLO,

320
00:23:55.420 --> 00:23:55.579
<v Speaker 2>right?

321
00:23:55.650 --> 00:23:56.709
<v Speaker 2>At least used it, right?

322
00:23:56.979 --> 00:24:01.579
<v Speaker 2>And I found it also quite straight and,
and very honest to say, OK, he will not

323
00:24:01.579 --> 00:24:05.020
<v Speaker 2>continue and pursue this, you know,
because of its implication.

324
00:24:05.219 --> 00:24:09.380
<v Speaker 2>And this resonates also, I don't know if
you have seen the keynote on, on laws.

325
00:24:09.564 --> 00:24:16.165
<v Speaker 2>Nips um conference, uh, December of
Charles Isbel, he gave this key, keynote on, you

326
00:24:16.165 --> 00:24:19.005
<v Speaker 2>can't escape hyperparametters and latent
variables, right?

327
00:24:19.354 --> 00:24:23.545
<v Speaker 2>So from a software engineering and argued
a bit, uh, really nicely done video,

328
00:24:24.015 --> 00:24:29.045
<v Speaker 2>actually, also that, you know, researchers
just need to have broad broadened their

329
00:24:29.045 --> 00:24:34.405
<v Speaker 2>scope and also their view on the
implications their grounding and their contribution

330
00:24:34.405 --> 00:24:35.405
<v Speaker 2>have in their application.

331
00:24:35.880 --> 00:24:39.619
<v Speaker 2>ations because the most, most researchers
are like, I, I just did the glossifier,

332
00:24:39.670 --> 00:24:39.839
<v Speaker 2>right?

333
00:24:39.910 --> 00:24:43.229
<v Speaker 2>I don't know what they're doing, the bad
guys or the good guys, right, with that.

334
00:24:43.540 --> 00:24:49.310
<v Speaker 2>But, um, as, you know, these technology
come more pervasive and important, it's

335
00:24:49.310 --> 00:24:54.069
<v Speaker 2>also, you know, inevitable, you know, that
you also consider that something will go

336
00:24:54.069 --> 00:24:55.510
<v Speaker 2>wrong or may go wrong, right?

337
00:24:55.739 --> 00:24:59.630
<v Speaker 2>And that you need to design for these
kinds of aspects and need to, when you

338
00:24:59.630 --> 00:25:01.430
<v Speaker 2>contribute um to this field.

339
00:25:01.614 --> 00:25:06.275
<v Speaker 2>Also being aware of, you know, this, this
application scenarios that's going on.

340
00:25:06.655 --> 00:25:11.375
<v Speaker 1>Yeah, Julie, this is, as I said, we can
talk about this for hours.

341
00:25:12.035 --> 00:25:14.114
<v Speaker 1>I actually struggle with something myself.

342
00:25:14.175 --> 00:25:20.175
<v Speaker 1>Um, I mentioned to you that we are
developing a solution where AI assistants can

343
00:25:20.175 --> 00:25:24.135
<v Speaker 1>sort of look over the shoulder because
they use the cameras of Google Glass or

344
00:25:24.135 --> 00:25:30.430
<v Speaker 1>HoloLens to monitor what they're doing and
Identify any errors, but we could use

345
00:25:30.430 --> 00:25:36.150
<v Speaker 1>that same camera with a little bit of
tweaking to also get a better understanding of

346
00:25:36.150 --> 00:25:38.109
<v Speaker 1>the emotional state of the worker, right?

347
00:25:39.229 --> 00:25:42.790
<v Speaker 1>He or she is tired or, you know, making
too many mistakes.

348
00:25:42.900 --> 00:25:46.390
<v Speaker 1>So maybe you need a break or you need to
go and get some water or maybe monitor

349
00:25:46.390 --> 00:25:50.910
<v Speaker 1>their vital signs and be able to be
helpful with that.

350
00:25:51.020 --> 00:25:56.930
<v Speaker 1>But what stops me from even suggesting
something like that is because I believe that

351
00:25:56.930 --> 00:25:58.069
<v Speaker 1>could be abused.

352
00:25:58.209 --> 00:26:04.520
<v Speaker 1>For instance, if supervisors could monitor
their workers and their emotional state,

353
00:26:04.969 --> 00:26:11.290
<v Speaker 1>they could look and say, oh, when I went
by this certain worker, his blood pressure

354
00:26:11.290 --> 00:26:16.449
<v Speaker 1>went up, or when he was reading or she was
reading an email that I sent to him at

355
00:26:16.449 --> 00:26:21.770
<v Speaker 1>that time, I could see that the emotional
state showed me that that person doesn't

356
00:26:21.770 --> 00:26:23.430
<v Speaker 1>like me or is upset or whatever.

357
00:26:24.109 --> 00:26:28.469
<v Speaker 1>And, and this can be abused, uh, so we are
in this quandary, right?

358
00:26:28.589 --> 00:26:31.989
<v Speaker 1>We can use this technology for doing great
things.

359
00:26:32.069 --> 00:26:36.310
<v Speaker 1>I mean, it would be wonderful to
understand that a person is tired, they need to

360
00:26:36.310 --> 00:26:42.130
<v Speaker 1>take a break, they need to go get some
water, but if that same data could be abused.

361
00:26:42.530 --> 00:26:49.329
<v Speaker 1>To retaliate against a worker because I
can now recognize how people feel

362
00:26:49.329 --> 00:26:53.800
<v Speaker 1>about me even if they don't say anything
at all, that is not a good thing.

363
00:26:54.089 --> 00:26:56.609
<v Speaker 1>So I guess what I'm saying is, yes, you're
right.

364
00:26:56.760 --> 00:27:02.650
<v Speaker 1>I mean this is a very tough problem, and
we're always struggling with how far should

365
00:27:02.650 --> 00:27:06.900
<v Speaker 1>we push this and have those values that
you were talking about.

366
00:27:07.280 --> 00:27:11.699
<v Speaker 1>To stop us from doing that, but all of us
need to abide by those because otherwise,

367
00:27:11.959 --> 00:27:15.520
<v Speaker 1>again, there are those people that are
going to abuse it, even though we didn't

368
00:27:15.520 --> 00:27:16.640
<v Speaker 1>create it for that purpose.

369
00:27:16.760 --> 00:27:18.920
<v Speaker 1>So that's, that's the problem.

370
00:27:33.890 --> 00:27:40.609
<v Speaker 3>Mosen, you mentioned before or you
elaborated quite a bit on ethics in AI and

371
00:27:40.609 --> 00:27:46.310
<v Speaker 3>also Siemens, like in October, they set
the four key strategic pillars and one of

372
00:27:46.310 --> 00:27:48.189
<v Speaker 3>them was technology with purpose.

373
00:27:48.569 --> 00:27:53.989
<v Speaker 3>And maybe you can elaborate a bit on what
does technology with purpose mean to you?

374
00:27:54.939 --> 00:27:59.969
<v Speaker 1>This is an excellent question, and I hope
my answer wouldn't surprise you.

375
00:28:00.339 --> 00:28:07.219
<v Speaker 1>You know, being at this business unit of
Siemens for over 36 years has

376
00:28:07.859 --> 00:28:14.119
<v Speaker 1>conditioned me to always think about how
what I do could help not only our

377
00:28:14.300 --> 00:28:17.040
<v Speaker 1>customers, but also humanity in general.

378
00:28:17.489 --> 00:28:23.530
<v Speaker 1>I, I really believe this is the result of
technology with purpose culture at Siemens

379
00:28:23.530 --> 00:28:24.959
<v Speaker 1>that you were just talking about.

380
00:28:25.329 --> 00:28:30.609
<v Speaker 1>You can't be someplace for 36 years and
not get gain that, uh, that culture that it

381
00:28:30.609 --> 00:28:30.930
<v Speaker 1>has.

382
00:28:31.050 --> 00:28:37.459
<v Speaker 1>Uh, for instance, I've pledged to myself
to put uh front and center, the

383
00:28:37.589 --> 00:28:43.449
<v Speaker 1>intended and unintended consequences of
digital transformation on humanity.

384
00:28:43.910 --> 00:28:50.750
<v Speaker 1>And to lead innovative initiatives to
counter negative effects that automation might

385
00:28:50.750 --> 00:28:51.180
<v Speaker 1>have.

386
00:28:51.589 --> 00:28:57.750
<v Speaker 1>You know, why can't we have human-centric
AI models for automation and be dedicated

387
00:28:57.750 --> 00:29:04.430
<v Speaker 1>to creating an ecosystem with no losers,
benefiting everyone from executives and

388
00:29:04.430 --> 00:29:08.630
<v Speaker 1>shareholders to workers and consumers,
because there's always people say, oh, there

389
00:29:08.630 --> 00:29:10.670
<v Speaker 1>are winners and losers, and I'm saying,
why?

390
00:29:11.339 --> 00:29:17.329
<v Speaker 1>You know, this, this kind of thinking and
culture carries over to my

391
00:29:17.329 --> 00:29:24.219
<v Speaker 1>nonprofit organization where we are
changing the game by placing sustainable

392
00:29:24.219 --> 00:29:29.900
<v Speaker 1>and affordable technologies in the hands
of subsistence farmers to lift themselves

393
00:29:29.900 --> 00:29:31.839
<v Speaker 1>up for a hopeful life.

394
00:29:32.319 --> 00:29:35.239
<v Speaker 1>I mentioned to you the name is Omid USA.

395
00:29:35.800 --> 00:29:42.500
<v Speaker 1>Omid in my mother tongue, Farsi means
hope, and really that's the basis for human

396
00:29:42.500 --> 00:29:43.369
<v Speaker 1>survival, right?

397
00:29:43.459 --> 00:29:45.280
<v Speaker 1>It's, it's hope.

398
00:29:45.800 --> 00:29:52.160
<v Speaker 1>You know, we dare to imagine renewable
energy solutions so well engineered that they

399
00:29:52.160 --> 00:29:57.300
<v Speaker 1>can be delivered at the lowest cost for
the highest yield.

400
00:29:57.839 --> 00:30:02.099
<v Speaker 1>We also dare to imagine an innovative
infrastructure.

401
00:30:02.670 --> 00:30:09.270
<v Speaker 1>Leading to an economic model where
community members doing the work are rewarded

402
00:30:09.270 --> 00:30:14.790
<v Speaker 1>instead of the middlemen, which
unfortunately are the winners today in these poor

403
00:30:14.790 --> 00:30:15.349
<v Speaker 1>regions.

404
00:30:16.319 --> 00:30:18.800
<v Speaker 1>So, uh, I hope that, that you think that's
cool, right?

405
00:30:18.920 --> 00:30:24.560
<v Speaker 1>Uh, and good indicator of this technology
with purpose concept that's immense.

406
00:30:25.630 --> 00:30:29.910
<v Speaker 2>I mean this, this goes along right with
the saying I think it was even uh Jim

407
00:30:29.910 --> 00:30:35.510
<v Speaker 2>Hackermansnave said like the future
belongs to those companies that generate profits

408
00:30:35.510 --> 00:30:38.430
<v Speaker 2>because of responsible conduct, right?

409
00:30:38.760 --> 00:30:45.290
<v Speaker 2>And there's a lot, a lot of stream to, you
know, the role of technology for tackling

410
00:30:45.670 --> 00:30:49.165
<v Speaker 2>urgent challenge out there and you, you
know, you have to only You're also on your

411
00:30:49.165 --> 00:30:51.704
<v Speaker 2>profit side, right, your contributions
like this is what you want to do.

412
00:30:52.025 --> 00:30:58.435
<v Speaker 2>But obviously in, in, in, in a world of uh
stakeholder capitalism somehow, right?

413
00:30:59.035 --> 00:31:03.415
<v Speaker 2>Uh, can we attach also great business
models on the sustainability channels?

414
00:31:03.505 --> 00:31:07.895
<v Speaker 2>What's, what's your view on the role of
software maybe also on circular economy and,

415
00:31:08.025 --> 00:31:11.545
<v Speaker 2>and these kinds of concepts which seem to
be a natural fit.

416
00:31:12.650 --> 00:31:18.609
<v Speaker 1>You know, a, a circular economy ensures
that resources which, which enter the

417
00:31:18.609 --> 00:31:21.969
<v Speaker 1>economy can remain a part of it for as
long as possible.

418
00:31:23.300 --> 00:31:30.260
<v Speaker 1>It is a popular idea among champions of
sustainability that, you know, emphasis

419
00:31:30.260 --> 00:31:36.660
<v Speaker 1>should be placed on designing out waste
and pollution, therefore, you know, keeping

420
00:31:36.670 --> 00:31:42.729
<v Speaker 1>products in use for longer and
facilitating the regeneration of natural systems.

421
00:31:43.260 --> 00:31:49.699
<v Speaker 1>I think we must get away from our current
throwaway culture which unfortunately

422
00:31:49.699 --> 00:31:51.469
<v Speaker 1>exists, especially in the US.

423
00:31:51.949 --> 00:31:58.250
<v Speaker 1>And instead, Give priority to the
principles of reduce,

424
00:31:58.449 --> 00:32:03.729
<v Speaker 1>reuse, and recycle rather than take, make,
and dispose.

425
00:32:04.449 --> 00:32:10.719
<v Speaker 1>One of the, you know, key adoption
challenges is that for the circular economy to

426
00:32:10.719 --> 00:32:17.369
<v Speaker 1>have a significant impact, it's not enough
for just one or two companies to

427
00:32:17.369 --> 00:32:21.489
<v Speaker 1>change how they manufacture one product.

428
00:32:21.890 --> 00:32:27.609
<v Speaker 1>Every organization that forms our
infrastructure and economy needs to embrace this

429
00:32:27.609 --> 00:32:29.270
<v Speaker 1>new way of doing business.

430
00:32:29.329 --> 00:32:35.250
<v Speaker 1>It's going again back to that conversation
we had about shared values that can't

431
00:32:35.250 --> 00:32:36.369
<v Speaker 1>just be one company.

432
00:32:36.449 --> 00:32:40.550
<v Speaker 1>It needs to go across the board, and
that's really the, the challenge.

433
00:32:41.010 --> 00:32:47.030
<v Speaker 1>And I think we are uniquely positioned for
this circular economy because You know,

434
00:32:47.439 --> 00:32:54.359
<v Speaker 1>DISW is the number one PLM vendor in the
world, and the software that

435
00:32:54.359 --> 00:33:00.189
<v Speaker 1>we create from DISW with its vast customer
base can, can help here.

436
00:33:00.439 --> 00:33:06.660
<v Speaker 1>As an example, we need to do more to
enable reduction by design in our

437
00:33:07.400 --> 00:33:11.420
<v Speaker 1>ecosystem, meaning that our software
should help customers.

438
00:33:11.939 --> 00:33:18.660
<v Speaker 1>Design their products with the end goal of
disassembly and regeneration from the

439
00:33:18.660 --> 00:33:22.650
<v Speaker 1>very outset, and we are doing some work,
of course, in this area, but I think we

440
00:33:22.650 --> 00:33:24.420
<v Speaker 1>need to do more, in my opinion.

441
00:33:26.050 --> 00:33:30.469
<v Speaker 3>I agree and I also believe that the future
will look like that we generate business

442
00:33:30.469 --> 00:33:34.369
<v Speaker 3>value through social value, so value for
the environment and society.

443
00:33:34.670 --> 00:33:37.300
<v Speaker 1>Absolutely, I totally agree with that.

444
00:33:37.540 --> 00:33:38.369
<v Speaker 1>No question.

445
00:33:39.640 --> 00:33:44.420
<v Speaker 3>Mosen, we are already at the last question
and this one is quite a personal one

446
00:33:44.420 --> 00:33:50.030
<v Speaker 3>because you've worked so many years for
the company and you've pushed and seen so

447
00:33:50.030 --> 00:33:55.479
<v Speaker 3>many fascinating challenges and
initiatives and you have that nonprofit where you're

448
00:33:55.479 --> 00:33:56.160
<v Speaker 3>working.

449
00:33:56.560 --> 00:34:02.119
<v Speaker 3>So, I would be super curious to know what
were some key lessons that you picked up

450
00:34:02.119 --> 00:34:05.180
<v Speaker 3>along your journey and that you would like
to share with the audience.

451
00:34:06.250 --> 00:34:10.489
<v Speaker 1>Yeah, we kind of have talked about some of
this already.

452
00:34:10.610 --> 00:34:16.159
<v Speaker 1>I think number one is dare to imagine big
and be bold.

453
00:34:16.610 --> 00:34:21.800
<v Speaker 1>I don't think we at Siemens, uh, at least
I can tell you it's certain that I've

454
00:34:21.800 --> 00:34:27.570
<v Speaker 1>never been limited in what I can imagine
and what I can propose, and I think that

455
00:34:27.570 --> 00:34:29.530
<v Speaker 1>would be my advice to, to everyone.

456
00:34:30.310 --> 00:34:37.080
<v Speaker 1>The second one is to not be afraid of
failure, and the 3rd 1 is to

457
00:34:37.090 --> 00:34:41.010
<v Speaker 1>continue to learn your entire career, you
know, um.

458
00:34:42.709 --> 00:34:49.709
<v Speaker 1>After 36 years in the industry, I still
think that a day that goes by without me

459
00:34:49.709 --> 00:34:51.969
<v Speaker 1>learning something new was wasted.

460
00:34:52.739 --> 00:34:59.628
<v Speaker 1>And the more I learn, the more I realize
how much I don't know and how uninformed

461
00:34:59.628 --> 00:35:06.128
<v Speaker 1>I am, which is kind of disappointing, but
also gives me more fuel to want to learn

462
00:35:06.128 --> 00:35:06.489
<v Speaker 1>more.

463
00:35:07.229 --> 00:35:13.840
<v Speaker 1>And at least in my case, I've learned more
from my failures than from my successes.

464
00:35:14.040 --> 00:35:20.080
<v Speaker 1>So, I take risks and try my best to make
it a successful venture when I get down a

465
00:35:20.080 --> 00:35:23.919
<v Speaker 1>path, but if it fails, I don't panic.

466
00:35:24.040 --> 00:35:30.959
<v Speaker 1>Instead, I do a postmortem and I try to
figure out what happened so that I can do

467
00:35:30.959 --> 00:35:32.199
<v Speaker 1>things better next time.

468
00:35:32.889 --> 00:35:39.250
<v Speaker 1>And I think that's really something that I
believe if every one of our young talent

469
00:35:39.250 --> 00:35:43.189
<v Speaker 1>keeps those three things in mind, they
would have a successful career, at Siemens.

470
00:35:44.199 --> 00:35:46.250
<v Speaker 3>Beautiful and so inspiring.

471
00:35:46.679 --> 00:35:47.919
<v Speaker 3>Mosen, thanks so much.

472
00:35:48.080 --> 00:35:53.120
<v Speaker 3>You're truly a gifted writer and it was um
so much fun like having this conversation

473
00:35:53.120 --> 00:35:55.459
<v Speaker 3>with you and listening to you and learning
from you.

474
00:35:55.919 --> 00:35:59.239
<v Speaker 3>Uh, but before we finish off, we play my
favorite game.

475
00:35:59.280 --> 00:36:01.100
<v Speaker 3>It's called Authentic Autocomplete.

476
00:36:01.320 --> 00:36:03.989
<v Speaker 3>And today you, you will be our special
guest.

477
00:36:04.320 --> 00:36:08.000
<v Speaker 3>So I will give you for the closing a
couple of sentence starters and you will just

478
00:36:08.000 --> 00:36:08.500
<v Speaker 3>finish.

479
00:36:08.800 --> 00:36:10.040
<v Speaker 3>Mosen, are you ready?

480
00:36:11.129 --> 00:36:12.510
<v Speaker 1>I'll try my best.

481
00:36:13.090 --> 00:36:13.649
<v Speaker 1>Go ahead.

482
00:36:14.050 --> 00:36:16.679
<v Speaker 3>OK, we start out with an easy one, OK?

483
00:36:17.010 --> 00:36:18.260
<v Speaker 3>So Siemens is

484
00:36:19.500 --> 00:36:23.340
<v Speaker 1>A great place to innovate responsibly.

485
00:36:24.260 --> 00:36:24.959
<v Speaker 3>Perfect.

486
00:36:25.379 --> 00:36:26.439
<v Speaker 3>Innovation is.

487
00:36:27.510 --> 00:36:30.570
<v Speaker 1>Practical implementation of ideas.

488
00:36:31.840 --> 00:36:32.969
<v Speaker 2>I haven't heard that before.

489
00:36:33.050 --> 00:36:33.909
<v Speaker 2>I haven't heard that before.

490
00:36:33.969 --> 00:36:34.750
<v Speaker 2>I love it.

491
00:36:35.370 --> 00:36:38.229
<v Speaker 3>The COVID pandemic has taught me,

492
00:36:38.739 --> 00:36:43.850
<v Speaker 1>it's taught me to be patient and
appreciate freedom of movement.

493
00:36:45.080 --> 00:36:45.620
<v Speaker 3>Beautiful.

494
00:36:46.040 --> 00:36:49.270
<v Speaker 3>And the last one, it's quite a tough one,
but Mos and I believe in you.

495
00:36:49.560 --> 00:36:54.260
<v Speaker 3>So if I could invent a rule for everyone
in the world to follow, it would be.

496
00:36:55.250 --> 00:37:01.729
<v Speaker 1>It's actually a combination of rules, uh,
be tolerant of our

497
00:37:01.729 --> 00:37:02.669
<v Speaker 1>differences.

498
00:37:03.639 --> 00:37:05.169
<v Speaker 1>Help the needy.

499
00:37:06.000 --> 00:37:10.060
<v Speaker 1>And above all, live and let live in peace.

500
00:37:11.760 --> 00:37:12.429
<v Speaker 2>Oh, I love that.

501
00:37:12.860 --> 00:37:16.409
<v Speaker 2>If this, these are 3 if and else rules,
then we have an AI system, isn't it?

502
00:37:18.709 --> 00:37:19.159
<v Speaker 2>Just kidding.

503
00:37:19.659 --> 00:37:20.780
<v Speaker 2>Well, thanks so much.

504
00:37:20.860 --> 00:37:26.159
<v Speaker 2>It was such a pleasure, and I, I'm sure
we, we need to continue that discussion on,

505
00:37:26.199 --> 00:37:31.300
<v Speaker 2>not only on a glass of wine, but maybe on
the 2nd or 3rd, and the 4th episode of, of

506
00:37:31.300 --> 00:37:32.510
<v Speaker 2>the Human in The Eye podcast.

507
00:37:32.649 --> 00:37:35.620
<v Speaker 2>Thanks so much for spending this time with
us and sharing your thoughts.

508
00:37:35.820 --> 00:37:36.340
<v Speaker 2>Marvelous.

509
00:37:36.500 --> 00:37:41.379
<v Speaker 1>Truly, it was my pleasure and thank you
for inviting me and spending this time, uh.

510
00:37:41.919 --> 00:37:45.280
<v Speaker 1>Together and I actually look forward to
future conversations.

511
00:37:45.669 --> 00:37:50.270
<v Speaker 1>Uli, you're, uh, you're not gonna be far
away, so we're gonna have these kind of

512
00:37:50.270 --> 00:37:50.719
<v Speaker 1>conversations a lot,

513
00:37:50.800 --> 00:37:51.110
<v Speaker 2>I hope.

514
00:37:51.850 --> 00:37:52.340
<v Speaker 2>Uh, here we go.

515
00:37:52.439 --> 00:37:53.830
<v Speaker 2>I love that, folks out there.

516
00:37:54.080 --> 00:37:55.159
<v Speaker 2>You stay tuned, right?

517
00:37:55.270 --> 00:37:56.739
<v Speaker 2>There's, I don't know, a lot of more to
come.

518
00:37:56.850 --> 00:37:58.080
<v Speaker 2>You have heard it already, right?

519
00:37:58.139 --> 00:38:03.010
<v Speaker 2>It will be stay bold and open-minded and
committed, obviously as well, and we hear

520
00:38:03.010 --> 00:38:04.800
<v Speaker 2>us at the next St andALA podcast.

521
00:38:04.959 --> 00:38:05.360
<v Speaker 2>Cheers.
