1
00:00:00,126 --> 00:00:02,563
You wouldn't want move fast and 
break 
 things to be the motto 

2
00:00:02,563 --> 00:00:05,169
in a nuclear plant. 
Today's guests are David Ariens 

3
00:00:05,169 --> 00:00:07,756
and 
 Willem van Lammeren, 
co-authors of the IT/OT 

4
00:00:07,756 --> 00:00:10,990
Handbook, whose cooperation 
 
patterns built from 15 years in 

5
00:00:10,990 --> 00:00:13,138
industrial digitalization are 
among the 
 currently most 

6
00:00:13,138 --> 00:00:16,169
shared within the field. 
So tell us what's the main 
 

7
00:00:16,177 --> 00:00:20,264
difference of IT and OT? 
In the OT world, we are creating

8
00:00:20,264 --> 00:00:22,997
software 
 which has a direct 
physical impact. 

9
00:00:23,072 --> 00:00:26,166
We work for manufacturing 
process, 
 process plants, and 

10
00:00:26,166 --> 00:00:27,549
infrastructure or critical 
infrastructure. 

11
00:00:27,718 --> 00:00:31,274
For example, water, electricity,

 that type of plants where 

12
00:00:31,274 --> 00:00:32,879
safety is the most important 
thing. 

13
00:00:32,945 --> 00:00:36,020
And after safety comes the 
integrity, 
 making sure what we

14
00:00:36,020 --> 00:00:37,863
do is right. 
And finally, the confidentiality

15
00:00:37,863 --> 00:00:41,871

 of the stuff we are doing. 
Where in the IT world, typically

16
00:00:41,871 --> 00:00:44,112

 we're talking CIA, 
confidentiality, integrity, 

17
00:00:44,112 --> 00:00:45,967
availability. 
What do you think of AI? 

18
00:00:45,992 --> 00:00:48,196
What was the impact really 
 AI 
to your world actually? 

19
00:00:48,214 --> 00:00:51,052
In manufacturing, the LLM is 
 
not gonna make me chocolate. 

20
00:00:51,275 --> 00:00:54,730
The impact is not the same as it

 does for software engineering.

21
00:00:54,793 --> 00:00:57,221
I mean, in software 
 
engineering completely changed. 

22
00:00:57,318 --> 00:00:59,117
Maintenance engineering, not 
yet. 

23
00:00:59,140 --> 00:01:03,101
Most plants are not stuffed 
 
with highly contextualized 

24
00:01:03,150 --> 00:01:06,164
available data through APIs. 
The data is hidden. 

25
00:01:06,435 --> 00:01:08,795
It's hard to get to. 
Data quality is not always 

26
00:01:08,795 --> 00:01:10,442
there. 
It's inconsistent across plants.

27
00:01:10,442 --> 00:01:13,514
Hallucinations are also a big 
 
factor, especially in 

28
00:01:13,514 --> 00:01:14,872
manufacturing when it comes to 
trust. 

29
00:01:14,926 --> 00:01:17,865
Trust is really something that 
has 
 to be earned always with 

30
00:01:17,865 --> 00:01:19,820
users. 
Especially with AI, if they just

31
00:01:19,820 --> 00:01:22,409

 get a hint of any 
hallucination, you can quickly 

32
00:01:22,409 --> 00:01:39,794
lose trust. 
Hey, quick pause. 

33
00:01:39,974 --> 00:01:41,834
My goal with Tech Lead Journal 
is simple. 

34
00:01:42,344 --> 00:01:45,104
Learn from the best in tech 
 so
we can all grow together. 

35
00:01:45,344 --> 00:01:48,644
If this resonates with you, hit 
 subscribe to follow the 

36
00:01:48,644 --> 00:01:50,618
channel. 
It's the biggest way for you to 

37
00:01:50,618 --> 00:01:53,189
support 
 the show and help us 
keep bringing great guests and 

38
00:01:53,189 --> 00:01:55,484
insights to you. 
Thanks for being here, 
 and 

39
00:01:55,484 --> 00:01:58,153
let's get back to it. 
Hello, everyone. 

40
00:01:58,153 --> 00:02:00,453
Welcome back to another new 
episode 
 of the Tech Lead 

41
00:02:00,453 --> 00:02:02,585
Journal podcast. 
Today we have two guests, 

42
00:02:02,585 --> 00:02:07,528
co-authors 
 of this book from 
IT Revolution titled The IT/OT 

43
00:02:07,528 --> 00:02:11,865
Handbook. 
So if you don't know, IT/OT is 

44
00:02:11,865 --> 00:02:15,189
actually 
 standing f- stands 
for, information technology and 

45
00:02:15,189 --> 00:02:18,779
operation technology. 
I'll let them later on explain, 

46
00:02:18,779 --> 00:02:22,696
 why there's this IT and OT. 
It was a bit confusing to me 
 

47
00:02:22,704 --> 00:02:24,453
what is OT in the very 
beginning. 

48
00:02:24,903 --> 00:02:27,103
But yeah, looking forward to 
learning 
 from both of you 

49
00:02:27,103 --> 00:02:29,271
because I think these topics 
might be interesting, 

50
00:02:29,271 --> 00:02:32,163
especially, 
 for us to, you 
know, understand what's the 

51
00:02:32,173 --> 00:02:34,193
challenges when working with 
operations. 

52
00:02:34,343 --> 00:02:36,143
So welcome to the show, David, 
Willem. 

53
00:02:36,153 --> 00:02:38,533
Looking forward for, you 
 know,
this conversation. 

54
00:02:39,239 --> 00:02:41,007
Thanks for having me. 
Same. 

55
00:02:42,207 --> 00:02:44,659
Yeah. 
So I know both of you 
 also 

56
00:02:44,659 --> 00:02:47,339
have podcast, right? 
So maybe this is also an 

57
00:02:47,339 --> 00:02:50,399
interesting 
 time for you to be
guests of a podcast. 

58
00:02:50,629 --> 00:02:53,467
But let me start by inviting 
both of you 
 to share a little 

59
00:02:53,467 --> 00:02:55,919
bit more about, you know, the 
story behind the book, right? 

60
00:02:56,699 --> 00:02:59,443
And maybe also the story how you

 came up with the podcast, 

61
00:02:59,443 --> 00:03:01,329
because I think it's kind of 
related in a way. 

62
00:03:01,731 --> 00:03:04,455
So Willem, we need to be careful
to not 
 start asking questions 

63
00:03:04,455 --> 00:03:08,803
to Henry this time. 
It is a bit different to 
 be on

64
00:03:08,803 --> 00:03:11,191
the receiving side. 
Let me start. 

65
00:03:11,331 --> 00:03:15,821
So a quick introduction. 
So indeed, yes, I'm David. 

66
00:03:15,901 --> 00:03:18,051
My background is mathematical 
engineering. 

67
00:03:18,531 --> 00:03:21,981
I started working in the 
 
chemical industry, 15 years ago.

68
00:03:21,981 --> 00:03:26,523
So I always worked, let's say, 
between 
 all kinds of 

69
00:03:26,523 --> 00:03:29,321
fascinating chemicals, but 
always on the digital side. 

70
00:03:29,411 --> 00:03:33,667
So never really touching the 
actual 
 production of 

71
00:03:33,667 --> 00:03:38,940
chemicals, but always trying to,
yeah, find ways on how IT can 

72
00:03:38,940 --> 00:03:41,691
help 
 with the production of 
those chemicals. 

73
00:03:42,591 --> 00:03:48,329
And that's, yeah, where me and 
Willem met 10 or so years ago, 

74
00:03:48,329 --> 00:03:50,759
maybe more. 15 years ago, I 
think. 

75
00:03:51,459 --> 00:03:54,551
Something like that. 
Yeah, absolutely. 

76
00:03:55,521 --> 00:04:00,831
And so we, but I leave the 
 
introduction to Willem as well. 

77
00:04:00,831 --> 00:04:05,791
But, this is where I think we 
 
started working together on this

78
00:04:05,821 --> 00:04:07,981
industrial digitalization 
topics. 

79
00:04:08,321 --> 00:04:11,838
And this is where I think the, 
we can 
 already say that OT, it

80
00:04:11,838 --> 00:04:14,297
stands for, yes, as you said, 
operational technology, 
 I 

81
00:04:14,297 --> 00:04:16,817
think Willem, and that's maybe 
the perfect way for your 

82
00:04:16,817 --> 00:04:19,346
introduction as well. 
You always said, "David, 
 it's 

83
00:04:19,346 --> 00:04:22,557
just IT for factories." 
Yeah. 

84
00:04:22,557 --> 00:04:25,427
Yeah, that's the problem is, 
 
nobody knows what I do except 

85
00:04:25,427 --> 00:04:26,917
David and a couple of other 
people. 

86
00:04:28,437 --> 00:04:31,537
So I'm Willem, the other 
 half 
of the IT/OT Insider. 

87
00:04:32,417 --> 00:04:35,333
I'm a bit older than David, so 
I've 
 been doing for 20 years 

88
00:04:35,333 --> 00:04:38,167
working in manufacturing all my 
career. 

89
00:04:39,327 --> 00:04:43,457
Stumbled into IT. 
First, you know, the really 

90
00:04:43,457 --> 00:04:46,127
corporate 
 IT far away from 
production. 

91
00:04:46,137 --> 00:04:50,187
But when I started working with 
 David, it was like on a huge 

92
00:04:50,187 --> 00:04:53,985
site, plants, production sites, 
 pipelines, everything around 

93
00:04:53,985 --> 00:04:57,397
you. 
There was no denying we were in 

94
00:04:57,397 --> 00:05:00,677
production 
 doing IT for 
factories in essence, yeah. 

95
00:05:01,207 --> 00:05:02,757
My background is a chemical 
engineer. 

96
00:05:04,257 --> 00:05:08,644
But I mean, it's been so long 
 
ago that I can only pretend that

97
00:05:08,644 --> 00:05:14,700
I'm an engineer by now. 
So, you asked us where 
 did the

98
00:05:14,700 --> 00:05:16,887
podcast come from? 
Where did the book come from? 

99
00:05:18,197 --> 00:05:22,371
I think it started out me and 
David, of 
 course, working 

100
00:05:22,371 --> 00:05:26,437
closely together on really cool 
projects in that intersection 

101
00:05:26,437 --> 00:05:30,007
where, 
 you know, the digital 
meets reality. 

102
00:05:30,317 --> 00:05:34,631
Because you can talk about 
programming 
 and codes, but 

103
00:05:34,631 --> 00:05:38,603
there's also stuff like pumps 
the size of an apartment 

104
00:05:38,603 --> 00:05:41,417
building. 
And that's where we're working. 

105
00:05:42,567 --> 00:05:47,513
And as we both had different 
paths 
 in our careers, we still

106
00:05:47,513 --> 00:05:50,287
kept in touch because we're 
frustrated. 

107
00:05:50,587 --> 00:05:53,657
And I think frustration is the 

reason why we started writing. 

108
00:05:54,097 --> 00:05:56,627
It's like saying like, "Why 
don't 
 people do this this way?

109
00:05:56,627 --> 00:05:58,673
Why don't they understand it's 
working differently?" 

110
00:05:58,673 --> 00:06:02,725
And 
 that's why we started 
writing, because I think writing

111
00:06:02,725 --> 00:06:06,200
creates more understanding. 
Also there's a very good reason 

112
00:06:06,200 --> 00:06:07,523
to 
 just keep on meeting at 
Willem's. 

113
00:06:07,965 --> 00:06:12,141
Also, also, also. 
Plus nobody else would 

114
00:06:12,141 --> 00:06:13,505
understand 
 my frustrations 
anyway. 

115
00:06:14,389 --> 00:06:15,999
We had to share them to each 
other, Henry. 

116
00:06:17,857 --> 00:06:21,183
Yeah, so I think, David also 
shared 
 with me, before this 

117
00:06:21,183 --> 00:06:24,123
recording, right? 
So you guys started to write 

118
00:06:24,123 --> 00:06:26,457
simply 
 because of sharing this
frustration. 

119
00:06:26,467 --> 00:06:29,431
So it was like a therapy, you 
know, 
 for both of you to 

120
00:06:29,431 --> 00:06:31,165
actually kinda like share you 
frustrations… That's how it 

121
00:06:31,165 --> 00:06:32,627
started, yeah. … share it with 
the world. 

122
00:06:32,807 --> 00:06:35,457
But somow it got picked 
 up, 
right, by many readers. 

123
00:06:35,757 --> 00:06:39,100
And I think it became something 
 like good enough to write as a 

124
00:06:39,100 --> 00:06:40,977
book. 
So why do you think 
 maybe in 

125
00:06:40,977 --> 00:06:43,557
the first place? 
Because many of my listeners are

126
00:06:43,557 --> 00:06:46,731

 more from the software 
engineering IT side, right, what

127
00:06:46,731 --> 00:06:49,642
you call IT side. 
So tell us what's the main 
 

128
00:06:49,650 --> 00:06:52,462
difference of IT and OT? 
Actually, I'm quite interested 


129
00:06:52,470 --> 00:06:55,537
by your definition by saying OT 
is just IT for factory. 

130
00:06:55,537 --> 00:06:58,177
So tell us a little bit more 
because 
 we are probably not 

131
00:06:58,177 --> 00:07:02,647
familiar with this. 
I think it starts, and Willem 

132
00:07:02,647 --> 00:07:06,833
already 
 touched upon that, it 
starts with the fact that in our

133
00:07:06,833 --> 00:07:12,683
world, in the 
 OT world, we are
creating software which has a 

134
00:07:12,683 --> 00:07:17,083
direct physical impact. 
So there is physical asset. 

135
00:07:17,563 --> 00:07:21,560
And let's just give it first, a 
 couple of examples, like the 

136
00:07:21,560 --> 00:07:23,223
types of industries we're 
working in. 

137
00:07:23,223 --> 00:07:25,523
I think that makes sense 
 also 
for your audience. 

138
00:07:25,853 --> 00:07:31,613
We often say that we work for 
 
manufacturing process, process 

139
00:07:31,613 --> 00:07:35,513
plants, and infrastructure or 
critical infrastructure. 

140
00:07:35,653 --> 00:07:40,345
So for example, critical 
infrastructure: 
 water, 

141
00:07:40,345 --> 00:07:44,253
electricity, that type of 
plants. 

142
00:07:44,883 --> 00:07:47,871
It's very interesting, for 
example, 
 a water company, they

143
00:07:47,871 --> 00:07:52,193
have an obligation to provide 
clean and safe 
 water at any 

144
00:07:52,193 --> 00:07:56,453
time to their customers. 
You can't reboot the water 

145
00:07:56,453 --> 00:08:00,411
system. 
The water needs to keeps 
 on 

146
00:08:00,411 --> 00:08:03,993
flowing, always. 
The same for manufacturing. 

147
00:08:04,623 --> 00:08:09,103
It can be cookies, it can be 
 
cars, it can be dishwashers. 

148
00:08:09,263 --> 00:08:11,903
So all these things, they 
 are 
getting manufactured. 

149
00:08:12,203 --> 00:08:16,413
And yes, there are people there,

 but the digital side, the way 

150
00:08:16,413 --> 00:08:20,598
these processes get optimized, 
automated, 
 it's becoming more 

151
00:08:20,598 --> 00:08:24,935
and more important. 
And then we, yeah, we also touch

152
00:08:24,935 --> 00:08:27,663

 upon the process plants, so we
both come from a process 

153
00:08:27,663 --> 00:08:29,793
background, 
 so chemical 
plants, oil and gas. 

154
00:08:30,133 --> 00:08:34,846
So these really, really huge, 
gigantic, 
 yeah, city-size 

155
00:08:34,846 --> 00:08:39,061
locations where you sometimes 
only have a handful of 
 

156
00:08:39,068 --> 00:08:42,609
operators, operating a plant, 
which is, yeah, which is the 

157
00:08:42,609 --> 00:08:47,225
size of a town, right? 
And this again, is where this 
 

158
00:08:47,233 --> 00:08:49,733
digital component comes into 
play. 

159
00:08:49,813 --> 00:08:52,925
So I think this is the most 
important 
 thing is that we're 

160
00:08:52,925 --> 00:08:57,399
dealing with a physical asset 
where safety 
 is the most 

161
00:08:57,399 --> 00:09:00,809
important thing. 
We always wanna, we always wanna

162
00:09:00,809 --> 00:09:03,333
make 
 sure that these plants, 
they run safely. 

163
00:09:04,567 --> 00:09:09,409
And after safety, comes the 
integrity, 
 making sure that 

164
00:09:09,409 --> 00:09:16,097
what we do is right is right, is
for, it's safe, 
 it doesn't 

165
00:09:16,097 --> 00:09:20,041
explode, or the products are 
safe to consume or et cetera. 

166
00:09:21,401 --> 00:09:24,253
And only then comes the, I would
say, the 
 availability of the 

167
00:09:24,253 --> 00:09:26,466
plant and finally the 
confidentiality of the stuff we 

168
00:09:26,466 --> 00:09:29,669
are doing. 
Where in the IT world, it's 

169
00:09:29,669 --> 00:09:34,349
often a 
 bit, I wouldn't say 
totally opposite, but typically,

170
00:09:34,349 --> 00:09:37,908
we're talking CIA 
 – 
Confidentiality, Integrity, 

171
00:09:37,908 --> 00:09:41,421
Availability. 
And we also have this 

172
00:09:41,421 --> 00:09:44,064
possibility to do, 
 yeah, 
easier integra- easier 

173
00:09:44,064 --> 00:09:46,211
iterations, easier tests, try 
something out. 

174
00:09:46,781 --> 00:09:50,571
Deploy a small, small change 
 
to a part of our users. 

175
00:09:51,181 --> 00:09:54,591
That's something, we 
 can't do 
in our world. 

176
00:09:56,211 --> 00:10:00,721
I think an easy way to get a gut

 feeling of this is that you 

177
00:10:00,721 --> 00:10:03,521
wouldn't want move fast and 
break things to 
 be the motto 

178
00:10:03,521 --> 00:10:08,083
in a nuclear plant. 
Or in a pharmaceutical company 

179
00:10:08,083 --> 00:10:11,551
where 
 they're making drugs 
that you're gonna take, and put 

180
00:10:11,551 --> 00:10:14,961
in your body. 
So it makes sense. 

181
00:10:15,261 --> 00:10:18,311
The problem is, of course, both 
are right. 

182
00:10:18,551 --> 00:10:23,171
I mean, it would be terrible IT 
to 
 work like you would in a 

183
00:10:23,171 --> 00:10:26,031
nuclear plant. 
I think we tried that in 
 the 

184
00:10:26,031 --> 00:10:28,021
years, in the 2000s. 
It was super slow. 

185
00:10:28,021 --> 00:10:31,061
It was frustrating, over 
 
budget, over time, nobody happy.

186
00:10:33,081 --> 00:10:34,641
And of course, operation is also
right. 

187
00:10:34,641 --> 00:10:38,134
You do need to operate the way 

that David mentions in 

188
00:10:38,134 --> 00:10:40,407
production. 
The problem is we need to 
 meet

189
00:10:40,407 --> 00:10:43,281
in the middle if we want to 
digitalize production. 

190
00:10:45,341 --> 00:10:49,261
And there's no solution. 
The solution is not gonna be 
 

191
00:10:49,269 --> 00:10:51,913
telling one to be different. 
We're not gonna tell IT to be 

192
00:10:51,913 --> 00:10:54,016
like 
 production, and we're not
gonna tell production, why don't

193
00:10:54,016 --> 00:10:57,766
you be more like IT? 
And that's, feel that tension, 


194
00:10:57,774 --> 00:11:01,509
that's where we operate in. 
And that's a very good, 
 that's

195
00:11:01,509 --> 00:11:05,131
a very good point. 
This is exactly also where the 

196
00:11:05,131 --> 00:11:09,695
book lives. 
The book doesn't try to 
 make 

197
00:11:09,695 --> 00:11:15,185
the other change. 
It also doesn't try to apply IT 

198
00:11:15,185 --> 00:11:19,957
 paradigms, I would say 100% to 
OT and OT paradigms 100% to IT. 

199
00:11:20,607 --> 00:11:23,657
It's really like, okay, how can 
 we change that middle ground? 

200
00:11:24,357 --> 00:11:27,693
And how can we do it in such a 
way 
 that we can really, yeah, 

201
00:11:27,693 --> 00:11:31,841
take these leapfrogs, these big 
steps which 
 our industry 

202
00:11:31,841 --> 00:11:35,456
really, really needs. 
So let's be honest, I think we 


203
00:11:35,464 --> 00:11:39,408
do need to take those steps. 
Yeah, so I think very 

204
00:11:39,408 --> 00:11:41,082
interesting to 
 understand 
these challenges, right? 

205
00:11:41,082 --> 00:11:43,962
So you mentioned safety is, I 
 
think, the most important thing.

206
00:11:44,602 --> 00:11:47,148
So obviously I come more from 
the 
 IT side, software 

207
00:11:47,148 --> 00:11:48,731
engineering. 
You know, we build digital 

208
00:11:48,731 --> 00:11:51,364
products. 
Not too many times we actually 

209
00:11:51,364 --> 00:11:53,942
care a 
 lot about safety, to be
honest, right? 

210
00:11:53,942 --> 00:11:56,150
It's more about, you know, 
building, 
 building features, 

211
00:11:56,150 --> 00:11:57,901
let's say. 
Physical safety. 

212
00:11:58,352 --> 00:12:00,472
Yeah, testing in production. 
Oh, there's a bug. 

213
00:12:00,472 --> 00:12:01,922
Okay, maybe we can fix that, 
right? 

214
00:12:01,922 --> 00:12:05,048
So it's very rare to actually 
put 
 security, like, you know, 

215
00:12:05,048 --> 00:12:08,440
like at the top, like really, 
really 
 top of priority of what

216
00:12:08,440 --> 00:12:11,378
we build. 
So I think looking at these 
 

217
00:12:11,386 --> 00:12:14,252
two different paradigm or maybe 
set of importance, right? 

218
00:12:14,262 --> 00:12:16,972
Do you think like skill 
 set 
might be different? 

219
00:12:17,132 --> 00:12:20,002
Like, don't know about the 
 JD 
of soft- maybe software 

220
00:12:20,002 --> 00:12:23,277
developer for operations, right?
When you build all this 

221
00:12:23,277 --> 00:12:26,738
machinery kind 
 of a software, 
do you think like the skill set 

222
00:12:26,738 --> 00:12:29,682
can be interchangeable or 
 it's
something completely different? 

223
00:12:31,003 --> 00:12:33,303
Willem, I think that's one 
 
perfectly for you because you're

224
00:12:33,633 --> 00:12:38,198
living more on the IT side now. 
I've always been living more 
 

225
00:12:38,206 --> 00:12:44,649
on the IT side than you, David. 
I think in essence, there is the

226
00:12:44,649 --> 00:12:48,479

 engineering part where you do 
find each other, which is about 

227
00:12:48,479 --> 00:12:51,133
trying 
 to understand systems 
and processes and how do they 

228
00:12:51,133 --> 00:12:54,816
work and interact. 
So I think that part, the 

229
00:12:54,816 --> 00:12:56,311
technical 
 part is very 
interchangeable. 

230
00:12:56,781 --> 00:13:02,789
I think one thing that's very 
different 
 between a normal IT 

231
00:13:02,789 --> 00:13:06,971
user relationship in a company, 
I'm not saying like a 
 SaaS 

232
00:13:06,971 --> 00:13:10,740
provider or something like that,
but like internal IT in a 

233
00:13:10,740 --> 00:13:13,881
company, is 
 that OT is also a 
technical department. 

234
00:13:14,201 --> 00:13:18,205
So unlike if you're talking to 
HR, you're 
 gonna talk to 

235
00:13:18,205 --> 00:13:21,771
engineers, and they love to geek
out too, and they want to 

236
00:13:21,771 --> 00:13:24,232
understand. 
They want to know how that 
 AI 

237
00:13:24,232 --> 00:13:28,413
classifier is working. 
And they would love to explain 

238
00:13:28,413 --> 00:13:31,931
to you 
 how pumps can fail in 
17 different ways. 

239
00:13:32,341 --> 00:13:35,867
I think if you bring that 
engineering 
 curiosity to try 

240
00:13:35,867 --> 00:13:38,935
to understand what's happening 
there, you do have 
 the basis 

241
00:13:38,935 --> 00:13:42,266
for a good relationship. 
It's important to acknowledge, 


242
00:13:42,274 --> 00:13:45,797
though, they're right in their 
technical expertise, but you're 

243
00:13:45,797 --> 00:13:48,371
also 
 right in your technical 
expertise. 

244
00:13:48,481 --> 00:13:52,801
I think very often IT is seen 
like 
 unicorn dust and just 

245
00:13:52,801 --> 00:13:57,606
program it. 
But if both sides have that 
 

246
00:13:57,614 --> 00:14:01,161
mutual request, respect, I think
you do have a lot of overlap. 

247
00:14:01,445 --> 00:14:04,461
It's an, yeah, it's a very, it… 
I, 
 I think, Henry, that the, 

248
00:14:04,461 --> 00:14:07,469
well, so the understanding that 
you are working with 
 two 

249
00:14:07,469 --> 00:14:09,305
technical domains is the first 
one. 

250
00:14:09,605 --> 00:14:14,457
I think a second one I'd like to

 add is that in a typical 

251
00:14:14,457 --> 00:14:19,779
setup, in a typical company, 
let's say in 95% of 
 the cases,

252
00:14:19,779 --> 00:14:26,487
IT has a reporting line to the 
CIO or a similar function, and 

253
00:14:26,487 --> 00:14:30,365
OT 
 is typically part of plant 
operations. 

254
00:14:30,465 --> 00:14:36,533
So they are part of the, yeah, 
they 
 report to a COO or 

255
00:14:36,533 --> 00:14:41,105
similar function. 
And that's a, it makes sense. 

256
00:14:41,165 --> 00:14:44,135
It makes sense that there is a 

centralized IT function and 

257
00:14:44,135 --> 00:14:46,425
typically a localized operation 
function. 

258
00:14:47,525 --> 00:14:52,925
But it makes collaboration also 
 really, really hard if the CEO 

259
00:14:52,925 --> 00:14:55,085
the company is the only common 
link. 

260
00:14:56,073 --> 00:14:59,353
Yeah, this is also something 
 
that is uniquely different, 

261
00:14:59,353 --> 00:15:03,873
right, in your world, right? 
Because the OT reports to COO. 

262
00:15:03,873 --> 00:15:07,273
This is also something that I 
 
just learned when I spoke to you

263
00:15:07,593 --> 00:15:11,493
before this recording, right? 
So I always thought that 

264
00:15:11,493 --> 00:15:14,103
technology 
 always goes to CIO,
CTO, and all that. 

265
00:15:14,443 --> 00:15:17,602
But maybe in the industrial 
world, 
 right, in the 

266
00:15:17,602 --> 00:15:21,013
manufacturing world, actually 
COO is the one who actually 
 

267
00:15:21,021 --> 00:15:22,913
governs all this technology, 
right? 

268
00:15:23,273 --> 00:15:26,430
Which brings to this kind of 
like 
 silo I think, right, 

269
00:15:26,430 --> 00:15:28,641
between these two team, 
especially if they have 
 to 

270
00:15:28,641 --> 00:15:31,403
collaborate with each other. 
Maybe, you know, you have this 


271
00:15:31,411 --> 00:15:34,270
manufacturing process and all 
that, but also has the digital 

272
00:15:34,270 --> 00:15:36,223
software 
 aspect that interacts
with each other. 

273
00:15:36,403 --> 00:15:39,203
So tell us what's the problem 
 
with this silo, right? 

274
00:15:40,743 --> 00:15:43,306
And do you really still see 
so-called 
 in like the DevOps 

275
00:15:43,306 --> 00:15:45,973
world, you know, throw over the 
wall kind of mentality? 

276
00:15:46,723 --> 00:15:50,173
Maybe a little bit on this. 
Yeah, yeah. 

277
00:15:50,173 --> 00:15:56,561
It's, you know, if-- I wanna 
take 
 a step back first because

278
00:15:56,561 --> 00:15:59,460
you already mentioned our book 
is 
 getting published by IT 

279
00:15:59,460 --> 00:16:03,519
Revolution. 
Like that's already a dream came

280
00:16:03,519 --> 00:16:06,303

 true for, for, for multiple 
reasons. 

281
00:16:09,503 --> 00:16:13,973
A, because they just wanna work 
 with these guys from operations

282
00:16:13,973 --> 00:16:20,419
that's already like, wow. 
But secondly, if we go back many

283
00:16:20,419 --> 00:16:26,577

 years in time, at a certain 
point, Willem advised me to read

284
00:16:26,577 --> 00:16:30,558
The Phoenix Project. 
And I think most people in IT, I

285
00:16:30,558 --> 00:16:33,753

 wouldn't say everybody, but 
most people in IT will have 

286
00:16:33,753 --> 00:16:36,103
read… I hope they did. 
Yeah, will have read… Or should 

287
00:16:36,103 --> 00:16:38,263
read. 
Or should read The Phoenix 

288
00:16:38,263 --> 00:16:42,287
Project 
 because it's still 
like the, for me, it's the 

289
00:16:42,287 --> 00:16:47,873
starting point of DevOps. 
So I remember, I still 
 

290
00:16:47,881 --> 00:16:51,067
remember me reading it. 
I actually read it already a 

291
00:16:51,067 --> 00:16:53,654
couple 
 of times just to get 
acquainted with the content as 

292
00:16:53,654 --> 00:16:58,142
good as possible. 
But I know I read it, and I 

293
00:16:58,142 --> 00:17:02,715
became nervous 
 while reading 
it because I was going through 

294
00:17:02,715 --> 00:17:05,371
at a… it's also, you know, the 

background is also a 

295
00:17:05,371 --> 00:17:07,866
manufacturing plant. 
It's car, it's a car parts 

296
00:17:07,866 --> 00:17:11,021
plant. 
But I was reading it and I went 

297
00:17:11,021 --> 00:17:14,678
like, 
 "But yeah, but we, like,
we face the same type of 

298
00:17:14,678 --> 00:17:18,711
problems." 
And then a 
 little bit later, I

299
00:17:18,711 --> 00:17:22,813
also read, again, or I think 
Willem, you pointed me 
 to it, 

300
00:17:22,813 --> 00:17:28,483
it's, that's Team Topologies. 
And you also go like, "Yeah, but

301
00:17:28,483 --> 00:17:30,133

 this, like, really makes 
sense." 

302
00:17:30,133 --> 00:17:33,415
But then, and this is the 
interesting 
 thing, then we 

303
00:17:33,415 --> 00:17:38,618
started talking about can we 
actually apply DevOps 
 

304
00:17:38,626 --> 00:17:40,833
principles to those siloed 
worlds? 

305
00:17:41,813 --> 00:17:48,561
And if so, how? 
I think that's where we started 

306
00:17:48,561 --> 00:17:51,139
to 
 experiment, David, because 
just for context, when we were 

307
00:17:51,139 --> 00:17:54,363
working together, 
 it wasn't 
just me and you, David. 

308
00:17:54,793 --> 00:18:00,263
We had like a bunch of people 
 
working in that domain with us. 

309
00:18:02,043 --> 00:18:06,993
So our job was how do we make 
sure that 
 these group of 

310
00:18:06,993 --> 00:18:10,658
people who are working with 
servers every day, patching, 

311
00:18:10,658 --> 00:18:14,683
doing 
 code, working with 
database, I mean, they were 

312
00:18:14,683 --> 00:18:18,283
doing IT work for those 
factories. 

313
00:18:18,613 --> 00:18:23,963
And the ideas from DevOps about 
how 
 development and operations

314
00:18:23,963 --> 00:18:29,255
in IT could work together, we 
tried to 
 apply them between IT

315
00:18:29,255 --> 00:18:33,173
and production environments who 
were our internal users. 

316
00:18:33,733 --> 00:18:37,913
And we found that given a few 
 
tweaks, actually those were very

317
00:18:38,203 --> 00:18:41,153
translatable in terms of 
concepts. 

318
00:18:41,153 --> 00:18:44,523
So we managed to get those same 
 ideas and concepts working. 

319
00:18:45,433 --> 00:18:49,283
It changed also a bit how 
 we 
see how you run teams. 

320
00:18:51,113 --> 00:18:54,255
And again, adding those tweaks 
for 
 operations specifically is

321
00:18:54,255 --> 00:18:57,453
a bit the basis of the book, I'd
say. 

322
00:18:57,985 --> 00:18:59,465
Yeah, yeah, yeah. 
Yeah. 

323
00:18:59,655 --> 00:19:04,475
And then we stopped thinking 
about 
 it for a couple of 

324
00:19:04,475 --> 00:19:07,497
years. 
And then like, and I think 

325
00:19:07,497 --> 00:19:10,865
that's, 
 that was perfectly 
fine because, you know, you're 

326
00:19:10,865 --> 00:19:13,625
just trying 
 stuff and you're 
experimenting. 

327
00:19:13,625 --> 00:19:17,253
And then I went to take another 
 job, and Willem took another 

328
00:19:17,253 --> 00:19:21,473
job. 
And so when we restarted that 

329
00:19:21,473 --> 00:19:25,883
endeavor, 
 we said like, "So, 
I've seen now other companies 

330
00:19:25,883 --> 00:19:27,700
and you've seen other 
 
companies. 

331
00:19:27,700 --> 00:19:31,813
And the base, the base 
principles, they are always the 

332
00:19:31,813 --> 00:19:35,026
base 
 problems, they are always
the same." 

333
00:19:35,026 --> 00:19:39,959
So we started translating those 
concepts 
 into what we then 

334
00:19:39,959 --> 00:19:43,987
started calling our IT/OT 
cooperation patterns, which we 


335
00:19:43,995 --> 00:19:48,543
published already three years or
so ago… Years, yeah. 

336
00:19:48,835 --> 00:19:51,745
…on our blog, became one of the 
 most read, most shared content.

337
00:19:52,625 --> 00:19:55,770
Why? 
Because, and that's the strength

338
00:19:55,770 --> 00:19:59,895

 of DevOps, team topologies. 
It's like it's very visual. 

339
00:19:59,905 --> 00:20:04,126
You, you're drawing circles, and

 you're explaining like, okay, 

340
00:20:04,126 --> 00:20:06,555
you are an IT team, you're an OT
team. 

341
00:20:07,625 --> 00:20:09,035
This is the type of problem you 
have. 

342
00:20:09,695 --> 00:20:12,685
Are you looking for 
 small type
interactions? 

343
00:20:12,915 --> 00:20:17,227
Are you looking for first steps,
versus, 
 and maybe we shouldn't

344
00:20:17,227 --> 00:20:22,155
go over all the patterns because
the book is, more than 
 a third

345
00:20:22,155 --> 00:20:26,704
is on those patterns, versus the
more complex projects, where you

346
00:20:26,704 --> 00:20:30,225

 have a higher change velocity,
where you have higher dependency

347
00:20:30,225 --> 00:20:34,260
on each other. 
And that then became originally 

348
00:20:34,260 --> 00:20:38,970
eight, but 
 we boiled it down 
to seven patterns from very 

349
00:20:38,970 --> 00:20:41,995
simple ones to very advanced 
ones. 

350
00:20:42,145 --> 00:20:50,429
And I think the most important, 
yeah, main idea almost we took 

351
00:20:50,429 --> 00:20:56,095
is that 
 we believe at this 
point in time for most 

352
00:20:56,095 --> 00:20:59,445
companies, we are too 
 early to
really break the silos. 

353
00:20:59,565 --> 00:21:02,260
So it's too early to say like, 
"You 
 know what? 

354
00:21:02,260 --> 00:21:04,641
We're gonna remove the OT 
function from operations and 

355
00:21:04,641 --> 00:21:08,042
we're 
 gonna move it into IT, 
or we're gonna remove IT and 

356
00:21:08,042 --> 00:21:12,697
all, IT in its entirety 
 and 
move that to oper- to move that 

357
00:21:12,697 --> 00:21:15,105
to operations." 
That's, it's too early. 

358
00:21:15,685 --> 00:21:18,255
It's probably not gonna 
 work 
in most environments. 

359
00:21:18,985 --> 00:21:23,929
So this is where the patterns, 
they acknowledge the silos, but 

360
00:21:23,929 --> 00:21:29,435
they 
 give you a language to 
cooperate given those silos and 

361
00:21:29,435 --> 00:21:33,125
make those 
 silos less, yeah, 
less of a problem. 

362
00:21:33,505 --> 00:21:36,773
And then hopefully after a 
while, you, you 
 don't feel as 

363
00:21:36,773 --> 00:21:40,079
being in a silo any longer. 
You feel like we are just 

364
00:21:40,079 --> 00:21:43,381
colleagues 
 amongst each other 
trying to collaborate on a, 

365
00:21:43,381 --> 00:21:47,719
yeah, on a digital project. 
I also think silos are not 
 

366
00:21:47,727 --> 00:21:51,743
always necessarily bad. 
I mean, if you work in a company

367
00:21:51,743 --> 00:21:54,611
and 
 I want a laptop, I want a 
laptop. 

368
00:21:54,661 --> 00:21:57,586
I don't want to start a 
multidisciplinary 
 team that 

369
00:21:57,586 --> 00:22:01,541
comes together to examine how we
can… I just want this thing 

370
00:22:01,541 --> 00:22:04,891
fixed, and 
 it's a contract, 
and next day it's there. 

371
00:22:04,891 --> 00:22:10,749
So silos are great, but we're 
adding a bit 
 more nuance to 

372
00:22:10,749 --> 00:22:15,374
the concept of cooperation 
within this context of IT and 

373
00:22:15,374 --> 00:22:18,829
OT. 
Again, based a lot of on team 

374
00:22:18,829 --> 00:22:22,089
topologies. 
And we take them, like David 

375
00:22:22,089 --> 00:22:25,809
said, from 
 observations in the
field from talking to hundreds 

376
00:22:25,809 --> 00:22:29,907
of people in manufacturing. 
We distilled ways that you 
 can

377
00:22:29,907 --> 00:22:33,005
break down the silos. 
And it's not always make a 

378
00:22:33,005 --> 00:22:36,116
product team. 
There's like steps in between 
 

379
00:22:36,124 --> 00:22:43,229
and each step has its place. 
Yeah, so before we actually dive

380
00:22:43,229 --> 00:22:45,929
deeper 
 into the collaboration,
the cooperation patterns that 

381
00:22:45,929 --> 00:22:47,903
you mentioned, right? 
Because very interesting that 

382
00:22:47,903 --> 00:22:50,353
you 
 mentioned about these 
silos, but for us maybe to kind 

383
00:22:50,353 --> 00:22:52,701
of like relate 
 a little bit, 
since you have been working in 

384
00:22:52,701 --> 00:22:55,240
the industries for quite 
 some 
time, maybe seeing a few 

385
00:22:55,240 --> 00:22:57,677
different companies, talking to 
different peoples, 
 are there 

386
00:22:57,677 --> 00:23:01,383
kind of like war stories that 
can kind of like illustrate 
 

387
00:23:01,391 --> 00:23:03,483
this challenge between IT and 
OT? 

388
00:23:04,457 --> 00:23:07,899
War stories. 
Oh, so… I have the one from the 

389
00:23:07,899 --> 00:23:09,303
book 
 where we open the book 
with. 

390
00:23:09,493 --> 00:23:11,963
Oh yeah, why not? 
And it's a true story. 

391
00:23:12,043 --> 00:23:15,473
Yeah, I remember that one. 
It's a true story. 

392
00:23:16,853 --> 00:23:22,045
So factories make stuff. 
Stuff needs to leave the 

393
00:23:22,045 --> 00:23:23,833
factory, 
 otherwise you have a 
problem. 

394
00:23:25,343 --> 00:23:27,503
Very simple. 
Trucks come in, trucks come out.

395
00:23:27,913 --> 00:23:31,063
Now, there's regulations. 
Trucks cannot leave without the 

396
00:23:31,063 --> 00:23:33,338
 correct papers and correct 
paperwork and all, everything 

397
00:23:33,338 --> 00:23:37,533
comes on top. 
So I get a phone call around 8-9

398
00:23:37,533 --> 00:23:40,727
o'clock, 
 and they're telling 
me, "Willem, the trucks are not 

399
00:23:40,727 --> 00:23:43,079
getting their papers." 
 
And we had just automated 

400
00:23:43,079 --> 00:23:45,113
everything. 
I mean, everything was 

401
00:23:45,113 --> 00:23:47,205
automatic. 
They would scan stuff, 
 things 

402
00:23:47,205 --> 00:23:52,047
would come out. 
I log in remotely, I see 
 

403
00:23:52,055 --> 00:23:54,593
everything is generated and 
like, I fucking hate printers. 

404
00:23:54,633 --> 00:23:56,223
Why don't they fucking print 
this thing? 

405
00:23:57,285 --> 00:24:00,065
Yeah. 
If the trucks cannot leave or 
 

406
00:24:00,073 --> 00:24:04,163
enter the site, David, at the 
size of that site, we would have

407
00:24:04,163 --> 00:24:10,143
like huge, huge traffic jams. 
They would be on the news. 

408
00:24:10,383 --> 00:24:12,953
I mean, it's like hundreds of 
 
trucks blocking the highway. 

409
00:24:13,243 --> 00:24:17,583
So off I go to the site. 
People from logistics were there

410
00:24:17,583 --> 00:24:20,659
already 
 on site, and we're 
like, "Why the hell does this 

411
00:24:20,659 --> 00:24:24,629
thing not want to work?" 
So we go through everything, 
 

412
00:24:24,637 --> 00:24:28,767
every possible little piece in 
the pipeline that could fail or 

413
00:24:28,767 --> 00:24:30,113
not. 
Does the printer work? 

414
00:24:30,113 --> 00:24:33,433
Yes, the printer does work. 
Does the software to print work?

415
00:24:33,433 --> 00:24:35,783
Yes, it works. 
The servers, everything works. 

416
00:24:37,513 --> 00:24:41,423
We start a major incident, 
 so 
we get everybody on board to 

417
00:24:41,423 --> 00:24:45,903
find out what's happening. 
And I think it's like 2:00, and 

418
00:24:45,903 --> 00:24:50,863
 we're like, "Okay, did anything
change in our ERP system? 

419
00:24:50,903 --> 00:24:54,143
Anything in the world? 
Like whatever. 

420
00:24:54,463 --> 00:24:55,863
We have no clue. 
Anything." 

421
00:24:55,863 --> 00:24:59,053
It was like 2:00 
 in the 
morning at that time. 

422
00:24:59,213 --> 00:25:03,427
And they said, "Yeah, we did a 

small patch in China." 

423
00:25:03,427 --> 00:25:05,383
It's like, "Okay, but we're on 
the other side. 

424
00:25:05,393 --> 00:25:07,788
Whatever. 
Can we reverse that change?" 

425
00:25:07,788 --> 00:25:09,993
Because we're 
 like completely 
out of options by then. 

426
00:25:10,063 --> 00:25:12,013
Everything should work. 
It doesn't work. 

427
00:25:14,873 --> 00:25:19,494
They reverse that change. 
By then it's 2:30, 3:00 in the 

428
00:25:19,494 --> 00:25:22,103
morning, 
 and it suddenly all 
works again. 

429
00:25:22,803 --> 00:25:32,523
So a small change in a form for 
 Chinese customs changed some 

430
00:25:32,523 --> 00:25:35,999
symbol, which meant that on the 
other side 
 of the world, 

431
00:25:35,999 --> 00:25:39,579
trucks could not leave. 
And that has a physical impact 

432
00:25:39,579 --> 00:25:43,907
because, 
 and it's, I would say
this is a, this could be any IT 

433
00:25:43,907 --> 00:25:47,263
incidents, Henry. 
So that it's like, it's not that

434
00:25:47,263 --> 00:25:50,413
our IT 
 is different from like 
your IT, right? 

435
00:25:53,330 --> 00:25:58,933
The big difference here is that 
if these 
 trucks can't move in 

436
00:25:58,933 --> 00:26:03,687
a certain pace, silos on the 
plant itself starts filling up. 

437
00:26:03,727 --> 00:26:06,714
And we're, in this case, we were

 talking about hundreds of 

438
00:26:06,714 --> 00:26:09,581
trucks a day. 
So silos would start filling up,

439
00:26:09,581 --> 00:26:12,315

 and at a certain point in 
time, silos would be full, 

440
00:26:12,315 --> 00:26:14,107
meaning that 
 you have to shut 
down production. 

441
00:26:14,717 --> 00:26:18,857
So this is where this physical 
link 
 suddenly becomes 

442
00:26:18,857 --> 00:26:23,659
extremely important, where we 
often only have a very 
 limited

443
00:26:23,659 --> 00:26:28,176
amount of time to either fix the
problem or implement a 

444
00:26:28,176 --> 00:26:31,332
workaround. 
And that's the problem also we 

445
00:26:31,332 --> 00:26:34,917
know from 
 IT, is the more we 
start automating, which we 

446
00:26:34,917 --> 00:26:39,207
should, the harder it becomes 
 
to fall back to a manual 

447
00:26:39,207 --> 00:26:41,137
workaround. 
Because you need to have the 
 

448
00:26:41,145 --> 00:26:42,857
knowledge to do for the 
workaround, you need to have the

449
00:26:42,857 --> 00:26:46,565
procedures, you 
 need to have 
people to be able to execute 

450
00:26:46,565 --> 00:26:49,531
upon the workaround. 
So it simply becomes more and 

451
00:26:49,531 --> 00:26:53,045
more 
 and more tricky to do so 
while there still is that 

452
00:26:53,045 --> 00:26:56,886
physical impact. 
And in, I think in Willem's 

453
00:26:56,886 --> 00:27:02,775
story, 
 and are many, many, 
many others, it's always the, I 

454
00:27:02,775 --> 00:27:07,247
think the big 
 difference here 
is, problems occur, yes. 

455
00:27:08,337 --> 00:27:14,871
But once you come together in a 
team 
 of people who have one 

456
00:27:14,871 --> 00:27:19,411
goal, and that is to fix the 
problem across the silos, 
 then

457
00:27:19,411 --> 00:27:24,497
we are always able to do that. 
But it becomes so much 
 easier 

458
00:27:24,497 --> 00:27:27,907
as if the other side understands
that physical impact. 

459
00:27:29,027 --> 00:27:32,293
And that's hard when there is, 
for 
 example, distance or IT is

460
00:27:32,293 --> 00:27:34,203
outsourced to another country, 
et cetera, et cetera. 

461
00:27:34,243 --> 00:27:37,329
I had to send pictures. 
They said like, "Is this really 

462
00:27:37,329 --> 00:27:39,549
a 
 major incident?" 
I'm like, "I'm gonna take a 

463
00:27:39,549 --> 00:27:43,245
picture of the trucks waiting. 
Like I'll show you the traffic 

464
00:27:43,245 --> 00:27:45,658
jam 
 outside and then maybe 
you'll believe me." 

465
00:27:45,658 --> 00:27:48,733
And then they believed me. 
Another really good example that

466
00:27:48,733 --> 00:27:51,468
a lot 
 of people in our 
industry will recognize, David, 

467
00:27:51,468 --> 00:27:53,221
is the PC you cannot patch. 
Yeah. 

468
00:27:53,643 --> 00:27:58,579
Or the Windows 95 PC. 
Like Windows, yeah, whatever old

469
00:27:58,579 --> 00:28:05,321
version, 
 Windows XP, also 95, 
but Windows XP is still a very, 

470
00:28:05,321 --> 00:28:09,321
very common operating 
 system 
to be found on factory floors. 

471
00:28:09,681 --> 00:28:12,051
Why? 
Because the thing was bought at 

472
00:28:12,051 --> 00:28:15,593
a 
 certain point in time as 
part of a very expensive, very 

473
00:28:15,593 --> 00:28:18,911
complex, very highly… 
Multimillion. 

474
00:28:18,911 --> 00:28:22,831
Huge. customized asset, and it's
sitting there. 

475
00:28:23,961 --> 00:28:25,961
And it's, and it'll keep on 
sitting there. 

476
00:28:25,981 --> 00:28:29,811
And we have examples of 
controllers 
 being decades old,

477
00:28:29,811 --> 00:28:31,761
but we still need to support 
them. 

478
00:28:32,611 --> 00:28:34,121
And that's also really 
interesting. 

479
00:28:34,121 --> 00:28:37,367
Like, how do you deal with that?
How do you inter- how do you 

480
00:28:37,367 --> 00:28:39,771
make 
 sure that from a 
cybersecurity point of view, 

481
00:28:39,771 --> 00:28:47,290
yes, of course, Windows XP is 
quite cumbersome, to put it that

482
00:28:47,290 --> 00:28:50,195
way. 
But still we need to be able to 

483
00:28:50,195 --> 00:28:52,911
 be, we need to deal with that. 
So there are ways of course to 

484
00:28:52,911 --> 00:28:55,393
secure it. 
There are ways to connect 
 to 

485
00:28:55,393 --> 00:28:58,837
that type of machines. 
It is something which is again, 

486
00:28:58,837 --> 00:29:00,241
 also really typical for our 
world. 

487
00:29:01,221 --> 00:29:05,869
But also very typical response 
of 
 IT is like, "That's not 

488
00:29:05,869 --> 00:29:08,648
allowed. 
You should now get a new PC." 

489
00:29:08,648 --> 00:29:12,971
And if 
 that's the approach 
you're gonna take to the part of

490
00:29:12,971 --> 00:29:15,771
the company that's actually 
 
making the money and say like, 

491
00:29:15,771 --> 00:29:18,294
"You should get a new OS, ask 
your vendor." 

492
00:29:18,294 --> 00:29:20,521
They're 
 like, "From what 
planet do you come? 

493
00:29:20,521 --> 00:29:22,803
This vendor doesn't exist 
anymore," or 
 whatever. 

494
00:29:22,803 --> 00:29:25,829
They don't care about… They'll 
say, "You want a new Windows 

495
00:29:25,829 --> 00:29:27,101
version? 
Sure, buy a new pub." 

496
00:29:27,413 --> 00:29:30,543
And I had that point. 
I had that discussion 
 multiple

497
00:29:30,543 --> 00:29:32,860
times, obviously. 
And at a certain point 
 in 

498
00:29:32,860 --> 00:29:36,801
time, again, yes. 
So this is like, this is not 
 a

499
00:29:36,801 --> 00:29:40,255
red security risk anymore. 
This is a black security risk, 


500
00:29:40,263 --> 00:29:45,048
like the worst you can get. 
So IT comes in, tells 

501
00:29:45,048 --> 00:29:47,885
operations, "You 
 will have to 
shut it down." 

502
00:29:47,885 --> 00:29:50,183
And then operations said like, 
"Okay, fine. 

503
00:29:50,553 --> 00:29:54,768
Like if you pay for the new 
machine, 
 we'll do so." 

504
00:29:54,768 --> 00:29:59,189
Okay, we're gonna do that. 
So how much would that 

505
00:29:59,189 --> 00:30:01,523
investment be? 
So many million euro. 

506
00:30:01,563 --> 00:30:03,267
Why? 
Because it's not about 
 

507
00:30:03,275 --> 00:30:06,931
replacing the machine. 
It's about the entirety of the 

508
00:30:06,931 --> 00:30:08,103
assets. 
Sometimes with customized 

509
00:30:08,103 --> 00:30:11,557
hardware, 
 all you… And I know 
that that was a discussion where

510
00:30:11,557 --> 00:30:15,872
IT said, "But that's 
 our 
running budget for the next 

511
00:30:15,872 --> 00:30:18,528
year." 
And operations said like, "Yeah,

512
00:30:18,528 --> 00:30:20,655
sure. 
If you want to replace the 

513
00:30:20,655 --> 00:30:22,759
machine 
 with your entire 
running operation, or your 

514
00:30:22,759 --> 00:30:27,470
running budget, please do so. 
We're all good with that, but we

515
00:30:27,470 --> 00:30:30,333
don't 
 have it budgeted, and we
will do so in the next 

516
00:30:30,333 --> 00:30:32,633
turnaround," which might be a 
 
turnaround means where if you 

517
00:30:32,633 --> 00:30:35,798
shut down the plant and you re- 
yeah, you replace 
 some, you do

518
00:30:35,798 --> 00:30:37,693
critical maintenance and you 
replace critical equipment, 

519
00:30:37,693 --> 00:30:40,543
which 
 might be in five or six 
or seven years. 

520
00:30:42,031 --> 00:30:44,699
Wow, this is such a fascinating 
problem 
 that you're dealing 

521
00:30:44,699 --> 00:30:47,854
with, right? 
So I could imagine, you know, 

522
00:30:47,854 --> 00:30:50,020
working with legacy 
 
technologies, right, that 

523
00:30:50,020 --> 00:30:52,191
probably is already out of 
support. 

524
00:30:52,651 --> 00:30:56,191
It's end of life, right? 
And probably, yeah, Beyond end 

525
00:30:56,191 --> 00:30:59,441
of life. and some security 
vulnerabilities that 
 

526
00:30:59,449 --> 00:31:01,111
potentially could be there, 
right? 

527
00:31:01,351 --> 00:31:03,161
But definitely this is 
 quite a
challenge, right? 

528
00:31:03,241 --> 00:31:05,921
So let's probably dive deep 
 
into some of the collaboration 

529
00:31:05,921 --> 00:31:07,001
patterns that you mentioned, 
right? 

530
00:31:07,021 --> 00:31:11,453
Maybe some of the common ones 
that 
 you think, are, you know,

531
00:31:11,453 --> 00:31:13,701
probably can solve some of these
challenges, right? 

532
00:31:13,701 --> 00:31:16,911
When IT and OT works together 
 
rather than, you know, always 

533
00:31:16,981 --> 00:31:19,762
having this tension because we 

don't understand each other 

534
00:31:19,762 --> 00:31:23,361
better. 
Well, David, I'm gonna start 

535
00:31:23,361 --> 00:31:26,593
with 
 maybe the more 
controversial ones because 

536
00:31:26,593 --> 00:31:30,105
everybody knows, well, let's do 
 cross-functional product teams,

537
00:31:30,105 --> 00:31:32,973
let's put them together and it's
gonna be great. 

538
00:31:32,983 --> 00:31:36,270
I mean, sure, you're gonna do 
that 
 for the high value, high 

539
00:31:36,270 --> 00:31:38,540
visibility stuff, but there's 
like tons of 
 other work that 

540
00:31:38,540 --> 00:31:43,179
needs to happen. 
David and I say that good shadow

541
00:31:43,179 --> 00:31:48,199

 IT is actually a good thing. 
Yeah, please don't, please don't

542
00:31:48,199 --> 00:31:52,489
shoot us. 
It's a shadow IT. 

543
00:31:52,869 --> 00:31:54,099
It's actually one of my 
favorites. 

544
00:31:55,739 --> 00:32:00,029
But I'm gonna explain it here. 
So Willem already mentioned that

545
00:32:00,029 --> 00:32:04,129
we 
 are working here with two 
technical functions, highly 

546
00:32:04,129 --> 00:32:08,841
technical functions. 
OT people are very, very used to

547
00:32:08,841 --> 00:32:12,063

 work with servers and 
networks, and patching and 

548
00:32:12,063 --> 00:32:15,639
security, and data 
 transfers 
and all the good stuff. 

549
00:32:15,639 --> 00:32:20,039
So yes, they might use other 
software 
 or they might use 

550
00:32:20,039 --> 00:32:22,301
other systems or other ways of 
thinking, but 
 they are very 

551
00:32:22,301 --> 00:32:25,429
used to that world. 
So for them to buy one 

552
00:32:25,429 --> 00:32:30,423
additional 
 server in a server 
park of a couple of hundreds , 

553
00:32:30,423 --> 00:32:36,323
or more, it's no big deal. 
So, we actually say that if 

554
00:32:36,323 --> 00:32:39,672
there is no 
 cooperation 
possible because the silos are 

555
00:32:39,672 --> 00:32:43,443
just too far away from each 
other, 
 let's just start with 

556
00:32:43,443 --> 00:32:47,179
some simple, good shadow IT, for
example, where… You 
 can also 

557
00:32:47,179 --> 00:32:50,899
have it the other way, a shadow 
OT, but that's, let's keep it 

558
00:32:50,899 --> 00:32:53,765
with 
 shadow IT, where these 
people, where experienced OT 

559
00:32:53,765 --> 00:32:56,532
people, they install an 
 extra 
application, et cetera, et 

560
00:32:56,532 --> 00:32:58,099
cetera. 
Why is that good, Henry? 

561
00:32:58,469 --> 00:33:01,759
It's good because they learn new
skills. 

562
00:33:01,869 --> 00:33:07,605
They learn what it takes to 
administer a 
 database or to, I

563
00:33:07,605 --> 00:33:12,562
don't know, integrate in some 
middleware application or… To 

564
00:33:12,562 --> 00:33:16,503
manage the application 
lifecycle, 
 to do support, to 

565
00:33:16,503 --> 00:33:20,849
do security work. 
I think good shadow IT also 

566
00:33:20,849 --> 00:33:24,169
means 
 doing it within the 
correct boundaries. 

567
00:33:24,339 --> 00:33:27,777
So it doesn't mean you give 
admin 
 rights to everybody and 

568
00:33:27,777 --> 00:33:30,330
install what the hell you want 
and just open 
 the firewall to 

569
00:33:30,330 --> 00:33:36,277
the outside world. 
It is doing good enough IT with 

570
00:33:36,277 --> 00:33:39,709
a lower 
 complexity, solving 
local problems. 

571
00:33:40,249 --> 00:33:44,303
Which brings us automatically to

 facilitation because obviously

572
00:33:44,303 --> 00:33:47,359
that shadow OT is only gonna get
you that far. 

573
00:33:47,649 --> 00:33:50,502
There will always be a point 
where you 
 need to open it to 

574
00:33:50,502 --> 00:33:52,417
the corporate network, where you
want cloud connectivity, 
 where

575
00:33:52,417 --> 00:33:54,760
you have a vendor sitting on the
internet somewhere who wants 

576
00:33:54,760 --> 00:33:56,519
some 
 data, you know, et 
cetera, et cetera. 

577
00:33:56,749 --> 00:33:59,842
Where the CISO comes in and says

 like, "We have to do a 

578
00:33:59,842 --> 00:34:01,309
security audit." 
You know, all the good stuff. 

579
00:34:02,209 --> 00:34:04,288
So that brings us to 
facilitation, 
 which is our 

580
00:34:04,288 --> 00:34:07,075
next pattern. 
Facilitation means that 
 we're 

581
00:34:07,075 --> 00:34:11,166
gonna work together. 
We are desig- we are, I would 
 

582
00:34:11,174 --> 00:34:14,589
say selecting, designating an OT
architect and an IT architect. 

583
00:34:15,029 --> 00:34:17,699
We don't ask them to change 
jobs. 

584
00:34:17,739 --> 00:34:21,058
We don't ask them to change, you

 know, reporting lines or 

585
00:34:21,058 --> 00:34:23,418
whatever. 
You just have two assigned 

586
00:34:23,418 --> 00:34:27,781
architects 
 who have to come 
together and solve, I would say 

587
00:34:27,781 --> 00:34:30,322
the rather smaller, easier 
 
problems, where someone, 

588
00:34:30,322 --> 00:34:32,875
somebody needs access to 
something, a system needs 
 

589
00:34:32,882 --> 00:34:34,679
access over the firewall to 
whatever. 

590
00:34:35,498 --> 00:34:38,768
There is a valid security 
 
concern raised by such and such,

591
00:34:38,768 --> 00:34:42,359
and we need to solve that. 
Let's just make sure that you 

592
00:34:42,359 --> 00:34:45,072
have 
 two colleague, two 
colleagues, two coworkers, both 

593
00:34:45,072 --> 00:34:48,728
having the 
 task to just fix 
those problems. 

594
00:34:49,228 --> 00:34:52,909
Very simple pattern, extremely 
powerful. 

595
00:34:54,079 --> 00:34:57,079
If that all works well, you 
know, if 
 there is some shadow 

596
00:34:57,079 --> 00:35:00,108
OT and they have some experience
what it takes to do 
 whatever 

597
00:35:00,108 --> 00:35:03,732
they wanna do, if there is some 
facilitation where you know 

598
00:35:03,732 --> 00:35:08,449
people, they 
 come together, 
where the, both the CIO and COO 

599
00:35:08,449 --> 00:35:11,474
understands like, you know, if 

we come together actually we can

600
00:35:11,474 --> 00:35:16,397
take steps, that's when we can 
step into the 
 more advanced, 

601
00:35:16,397 --> 00:35:21,939
the more advanced models. 
And this is where you typically,

602
00:35:21,939 --> 00:35:25,236
you 
 know, especially for the 
larger projects, the larger, 

603
00:35:25,236 --> 00:35:27,873
yeah, requests, the larger 
 
projects, you would start a 

604
00:35:27,873 --> 00:35:32,267
project team. 
But the project… I think also 

605
00:35:32,267 --> 00:35:35,655
it's good to 
 understand within
manufacturing companies, 

606
00:35:35,655 --> 00:35:40,158
everything is a project. 
I mean, it's the way they become

607
00:35:40,158 --> 00:35:42,408
big. 
If you build a plant, 
 I mean, 

608
00:35:42,408 --> 00:35:44,429
it's a project. 
It takes years. 

609
00:35:45,212 --> 00:35:47,162
It's in their DNA. 
It's how stuff gets funded. 

610
00:35:47,192 --> 00:35:51,452
It's how stuff gets done. 
Getting real product teams 
 

611
00:35:51,460 --> 00:35:55,612
more focusing on continuous 
improvement, it's much harder. 

612
00:35:55,852 --> 00:35:58,983
They're really capex driven, and
that's 
 something you need to 

613
00:35:58,983 --> 00:36:01,687
take into account. 
So just going there and say, 

614
00:36:01,687 --> 00:36:04,810
"Let's 
 make cross-functional 
product teams," nice, but that's

615
00:36:04,810 --> 00:36:07,492
not how funding happens 
 in 
those manufacturing companies. 

616
00:36:07,952 --> 00:36:11,812
So we did add the project team 
as one of 
 the patterns and a 

617
00:36:11,812 --> 00:36:16,230
great pattern to start. 
So if you have the focus, you 

618
00:36:16,230 --> 00:36:21,390
have 
 operations and IT 
focusing together on a specific 

619
00:36:21,390 --> 00:36:25,102
mission, a cross-functional 
 
project team is definitely the 

620
00:36:25,102 --> 00:36:27,288
way to go to get things started.
Yeah. 

621
00:36:27,718 --> 00:36:29,698
It's a way to start, not a way 
to end. 

622
00:36:29,878 --> 00:36:32,614
And it's also something we 
describe 
 in the book is that 

623
00:36:32,614 --> 00:36:40,722
one of the biggest anti-patterns
when starting 
 a project is not

624
00:36:40,722 --> 00:36:43,858
discussing what's gonna happen 
after the project. 

625
00:36:45,408 --> 00:36:47,919
Because again, if you're just in

 this capex world and you say 

626
00:36:47,919 --> 00:36:50,922
like, you know, I've now 
allocated 500,000 
 euro or 

627
00:36:50,922 --> 00:36:54,008
whatever to this project, you 
know we're gonna execute it. 

628
00:36:54,018 --> 00:36:56,188
In the beginning, typically 
 
everything goes really well. 

629
00:36:56,458 --> 00:36:59,268
Like, yeah, two things can 
happen. 

630
00:36:59,308 --> 00:37:03,653
So either the project team just 
dissolves 
 at a certain point 

631
00:37:03,653 --> 00:37:06,348
because people are, you know, 
pulled in other directions. 

632
00:37:07,026 --> 00:37:10,337
And then your, the thing you 
delivered, 
 like version one is

633
00:37:10,337 --> 00:37:12,857
there, but what's gonna happen 
now in the years to come? 

634
00:37:12,857 --> 00:37:14,997
It's, there's gonna be one big 
void. 

635
00:37:15,117 --> 00:37:17,667
It' a very common 
 anti-pattern
unfortunately. 

636
00:37:18,037 --> 00:37:22,247
Or other problem is like, if you

 then go like, "Oh, we 

637
00:37:22,247 --> 00:37:26,755
shouldn't dissolve." 
So now the project team 
 

638
00:37:26,763 --> 00:37:31,167
becomes permanent by accident, 
and it actually becomes a third 

639
00:37:31,167 --> 00:37:34,448
silo now. 
So now you have the IT silo, the

640
00:37:34,448 --> 00:37:38,839
OT 
 silo, and then the project 
silo… The innovation silo or… 

641
00:37:38,907 --> 00:37:41,227
The Industry 4.0 silo, 
 
whatever you wanna call it. 

642
00:37:41,717 --> 00:37:45,626
And it also happens quite often.
So we say when you start a 

643
00:37:45,626 --> 00:37:48,630
project, 
 and that's perfect 
because operations know how to 

644
00:37:48,630 --> 00:37:52,100
do projects, you need 
 to 
discuss the end in the 

645
00:37:52,100 --> 00:37:54,162
beginning. 
Like we're gonna start, but 
 

646
00:37:54,170 --> 00:37:57,890
how is this gonna evolve? 
And this brings us, of course, 

647
00:37:57,890 --> 00:38:01,463
then to 
 the product team, 
which is really known in the IT 

648
00:38:01,463 --> 00:38:05,515
world and where we believe 
 
there is a big value also in the

649
00:38:05,515 --> 00:38:10,377
OT or the IT/OT world to have 
those product 
 teams, but not 

650
00:38:10,377 --> 00:38:13,251
for everything, yeah. 
Again, as Willem said, we don't 

651
00:38:13,251 --> 00:38:15,237
need 
 a product team to order a
laptop. 

652
00:38:15,477 --> 00:38:20,832
The same is true for an average 
 digitalization project where, 

653
00:38:20,832 --> 00:38:23,646
you know, you can say like, 
"Okay, we 
 have an existing OT 

654
00:38:23,646 --> 00:38:26,409
team, and they can just, you 
know, they can deal 
 with 

655
00:38:26,409 --> 00:38:29,812
whatever is being built." 
But there are pro- there are 

656
00:38:29,812 --> 00:38:32,085
several 
 products where we 
really want that permanent 

657
00:38:32,085 --> 00:38:34,539
product team as well. 
And that's, I think, the final 


658
00:38:34,547 --> 00:38:38,443
pattern we describe in the book.
It's a hard pattern to get to 

659
00:38:38,443 --> 00:38:41,781
though. 
Again, using that manufacturing 

660
00:38:41,781 --> 00:38:47,409
 context in mind, a lot of money
and effort goes into building 

661
00:38:47,409 --> 00:38:50,409
that thing. 
And once it's there, okay, you 


662
00:38:50,417 --> 00:38:53,285
do the minimal maintenance. 
But it's doing its function. 

663
00:38:53,535 --> 00:38:57,129
Software is not like that. 
It evolves, it grows, and it 

664
00:38:57,129 --> 00:39:00,467
moves 
 much faster than, you 
know, than a physical asset does

665
00:39:00,467 --> 00:39:02,399
in a plant. 
And there are so many great 

666
00:39:02,399 --> 00:39:05,265
books 
 in the, yeah, in the 
world, but also in the IT 

667
00:39:05,265 --> 00:39:07,751
Revolution family. 
And they all talk about 
 the 

668
00:39:07,751 --> 00:39:11,105
same type of problem. 
They talk about the fact that, 

669
00:39:11,105 --> 00:39:14,754
you 
 know, if we take years to 
describe the perfect digital 

670
00:39:14,754 --> 00:39:18,121
product, chances 
 are it will 
never be delivered. 

671
00:39:18,421 --> 00:39:21,896
Because by the time we start 
building, 
 you know, the idea, 

672
00:39:21,896 --> 00:39:24,471
the specs, the things we want, 
they already changed. 

673
00:39:25,621 --> 00:39:27,966
And that's of course also a 
common pitfall 
 we have in our 

674
00:39:27,966 --> 00:39:31,551
world, but we need to marry, 
yeah, both sides a bit better. 

675
00:39:32,101 --> 00:39:34,931
Otherwise, you know, these 
 
people from IT, they will see, 

676
00:39:34,971 --> 00:39:39,317
they will be seen as aliens. 
So you need to be sure that 
 

677
00:39:39,325 --> 00:39:42,141
those two ideas, those two ways 
of working, they come together. 

678
00:39:43,725 --> 00:39:45,947
Yeah. 
I can really see the progression

679
00:39:45,947 --> 00:39:48,345

 that is required between, you 
know, the IT/OT, right? 

680
00:39:48,345 --> 00:39:51,945
And especially I think it might 
 differ based on the kind of 

681
00:39:51,945 --> 00:39:55,255
like types of industries, right?
Maybe when mentioning about, you

682
00:39:55,255 --> 00:39:58,705

 know, water plants versus 
maybe, you know, car parts 

683
00:39:58,705 --> 00:40:01,341
manufacturing 
 and all that, 
probably they kind of like have 

684
00:40:01,341 --> 00:40:03,505
different complexity. 
But I'm also guessing like 

685
00:40:03,505 --> 00:40:06,025
product 
 team will be 
something-- Like the one I'm 

686
00:40:06,025 --> 00:40:09,315
really familiar with because 
 I
really have limited knowledge is

687
00:40:09,565 --> 00:40:12,195
like we always see Tesla, right?
Producing Tesla. 

688
00:40:12,675 --> 00:40:16,854
It's such an advanced, you know,
I 
 don't know how they do the 

689
00:40:16,854 --> 00:40:18,095
machinery. 
They can push updates. 

690
00:40:18,095 --> 00:40:20,385
They can even have a 
 factory 
working by itself. 

691
00:40:20,595 --> 00:40:24,385
So is it like the probably good 
 reference as a product team? 

692
00:40:24,405 --> 00:40:28,171
Or like what does Tesla do 
differently 
 that make them 

693
00:40:28,171 --> 00:40:31,425
such an advanced, you know, kind
of like operation technology? 

694
00:40:31,549 --> 00:40:34,841
Yeah, so, so Tesla is an IT 
company 
 who happen to make 

695
00:40:34,841 --> 00:40:39,679
physical assets. 
It's the way they are wired. 

696
00:40:39,679 --> 00:40:42,593
And I'm not saying physical 
wiring, but 
 the way they are 

697
00:40:42,593 --> 00:40:45,163
wired in their mind. 
And I had many interactions 
 

698
00:40:45,171 --> 00:40:47,143
with Tesla employees. 
It's extremely, extremely, 

699
00:40:47,143 --> 00:40:49,549
extremely 
 interesting on what 
they do. 

700
00:40:49,911 --> 00:40:55,930
But still they come from this IT

 product first mindset and they

701
00:40:55,930 --> 00:41:00,139
try to apply, yeah, yeah, 
convert it into 
 the 

702
00:41:00,139 --> 00:41:01,991
manufacturing, the physical 
world. 

703
00:41:02,271 --> 00:41:08,493
And it's extremely interesting. 
Having said that, it is just, 
 

704
00:41:08,501 --> 00:41:13,779
it's impossible to change 
existing manufacturing 

705
00:41:13,779 --> 00:41:15,817
companies. 
They've been around for… And 

706
00:41:15,817 --> 00:41:17,875
that's 
 also their Achilles 
heel, obviously, yeah. 

707
00:41:18,065 --> 00:41:22,093
But if you come from a, what we 
call 
 a brownfield plant, so 

708
00:41:22,093 --> 00:41:25,631
the majority, well, the 
majority, almost every 
 

709
00:41:25,639 --> 00:41:27,261
manufacturing company already 
exists. 

710
00:41:27,391 --> 00:41:30,536
The ones who are built new, that

 is actually, yeah, it's, 

711
00:41:30,536 --> 00:41:32,401
that's a very, very, very small 
part. 

712
00:41:33,481 --> 00:41:36,827
They exist. 
Changing their entire 

713
00:41:36,827 --> 00:41:42,025
philosophy, 
 mentality, way of 
working, way they approach their

714
00:41:42,025 --> 00:41:45,501
production lines, et 
 cetera, 
et cetera, is almost impossible.

715
00:41:45,761 --> 00:41:50,446
And it's, there's is an example 
from 
 Tesla where they, I 

716
00:41:50,446 --> 00:41:54,981
forgot the name of the town, but
so they took over 
 an existing 

717
00:41:54,981 --> 00:41:59,306
production hall of a car company
which went, yeah, stopped 
 or 

718
00:41:59,306 --> 00:42:05,442
went bankrupt, I don't know. 
But they had to remove all the 

719
00:42:05,442 --> 00:42:10,065
assets 
 from the production 
line and start all over again 

720
00:42:10,065 --> 00:42:13,101
because they weren't 
 able to 
apply, you know, their 

721
00:42:13,101 --> 00:42:15,571
philosophy to the existing 
assets. 

722
00:42:15,631 --> 00:42:18,910
And I think that's probably the 
most 
 important learning here 

723
00:42:18,910 --> 00:42:21,701
is that it's just a different, a
different world. 

724
00:42:22,331 --> 00:42:25,158
And then of course, there are 
also 
 many companies who are 

725
00:42:25,158 --> 00:42:27,211
just regulated. 
Like the regulation states, 
 

726
00:42:27,219 --> 00:42:30,417
"You shall do it this way." 
Yeah. 

727
00:42:31,747 --> 00:42:33,557
Pharmaceuticals is really known 
for that. 

728
00:42:33,697 --> 00:42:37,211
If you want to change one small 
little 
 thing, the amount of 

729
00:42:37,211 --> 00:42:39,987
paperwork very often costs more 
than the benefit you would get. 

730
00:42:40,609 --> 00:42:41,649
Yeah. 
Yeah. 

731
00:42:41,935 --> 00:42:44,553
Right. 
I really hope people who listen 

732
00:42:44,553 --> 00:42:46,753
 to this conversation, really 
open up their perspective, 

733
00:42:46,753 --> 00:42:48,663
right? 
Because we are so used 
 to 

734
00:42:48,663 --> 00:42:50,315
digital products. 
It's so easy to build. 

735
00:42:50,315 --> 00:42:52,915
You know, we can iterate, 
 you 
know, CI/CD and deploy to 

736
00:42:52,915 --> 00:42:56,501
production multiple times a day.
But I think when looking at this

737
00:42:56,501 --> 00:42:59,496
world, 
 right, things are not 
that kind of like smooth and 

738
00:42:59,496 --> 00:43:02,185
always easy, right? 
Which, yep. 

739
00:43:02,463 --> 00:43:08,833
But, but one of the things we 
really 
 advocate for is we have

740
00:43:08,833 --> 00:43:12,113
to step into that way of working
as well. 

741
00:43:12,313 --> 00:43:16,947
We also need to do CI/CD, maybe 
not 
 to the extent of 1,000 

742
00:43:16,947 --> 00:43:20,073
deployments a day, but to 
multiple a day. 

743
00:43:21,093 --> 00:43:26,477
And the reason… Oh, no, not the 
reason, 
 but one of the ways we

744
00:43:26,477 --> 00:43:31,121
can get there is making sure we 
have an abstraction between 
 

745
00:43:31,129 --> 00:43:35,421
the physical assets and the 
physic- and the control of that 

746
00:43:35,421 --> 00:43:41,701
physical assets. 
And then yeah, we refer to as a 

747
00:43:41,701 --> 00:43:43,091
data platform. 
You could also say a 
 

748
00:43:43,099 --> 00:43:47,499
middleware layer or whatever. 
But decouple that from the very,

749
00:43:47,499 --> 00:43:52,325
very 
 fast changing IT world 
with something in between where 

750
00:43:52,325 --> 00:43:55,883
you can add that speed, 
 where 
you can add that flexibility, 

751
00:43:55,883 --> 00:43:58,943
that new way of working, that, 
you know, 
 config by code and 

752
00:43:58,943 --> 00:44:03,338
all the good stuff. 
And then step by step, we also 


753
00:44:03,346 --> 00:44:07,323
see, but that's gonna take years
and maybe even decades. 

754
00:44:07,703 --> 00:44:12,356
Step by step, we also see that 

the way these control systems 

755
00:44:12,356 --> 00:44:15,719
are being programmed because 
that's 
 also just, yeah, codes 

756
00:44:15,719 --> 00:44:19,221
of course. 
We also see that very slowly, 
 

757
00:44:19,229 --> 00:44:22,713
they're also adapting to new 
principles in the IT world. 

758
00:44:22,713 --> 00:44:27,347
And for example, using Git, 
using 
 version control and that

759
00:44:27,347 --> 00:44:29,993
type of things, doing more 
config by code. 

760
00:44:30,293 --> 00:44:33,093
It is something which we now 
also see 
 very slowly though, 

761
00:44:33,093 --> 00:44:36,403
but we see it also happening on 
the, on this lowest level. 

762
00:44:37,388 --> 00:44:38,988
Yep, thanks for the addition, 
right? 

763
00:44:38,988 --> 00:44:42,556
So I think, definitely very 
exciting, 
 which I think one of

764
00:44:42,556 --> 00:44:45,310
the big question these days, 
especially happening in 
 the IT

765
00:44:45,310 --> 00:44:48,595
world, is the AI part, right? 
Like we all seem to think AI 

766
00:44:48,595 --> 00:44:51,722
will 
 kind of like solve a lot 
of things, including building 

767
00:44:51,722 --> 00:44:54,385
software. 
So my question for you, both of 

768
00:44:54,385 --> 00:44:56,908
you 
 who have been in this OT 
world, right? 

769
00:44:57,158 --> 00:44:59,922
What do you think of AI? 
What was the impact really 
 AI 

770
00:44:59,922 --> 00:45:02,676
to your world actually? 
Is it gonna be the same, like 
 

771
00:45:02,684 --> 00:45:06,018
replacing a lot of kind of like,
you know, writing software, 
 

772
00:45:06,026 --> 00:45:07,378
software developers and all 
that? 

773
00:45:07,868 --> 00:45:11,280
Or is it something that is kind 
 of like will take some time to 

774
00:45:11,280 --> 00:45:15,577
actually get more traction? 
It already starts by defining 

775
00:45:15,577 --> 00:45:19,397
what is AI 
 because AI is more 
than generative AI. 

776
00:45:19,817 --> 00:45:22,337
Most people now know it from, 
you 
 know, I mean, we're using 

777
00:45:22,337 --> 00:45:23,987
natural language to communicate 
with whatever. 

778
00:45:24,527 --> 00:45:27,027
But AI has been around in 
 the 
industry for decades. 

779
00:45:28,027 --> 00:45:34,267
And machine learning, is front 
and center 
 in so many 

780
00:45:34,267 --> 00:45:37,785
applications to optimize 
processes in vision systems, and

781
00:45:37,785 --> 00:45:40,417
you name 
 it, in vibration 
monitoring, you know. 

782
00:45:41,297 --> 00:45:44,387
So many examples where AI 
 is 
already front and center. 

783
00:45:45,317 --> 00:45:49,727
But I think what we now see is 
there is this 
 new wave of, 

784
00:45:49,727 --> 00:45:57,545
yeah, generative AI, and I do 
believe that there 
 is gonna be

785
00:45:57,545 --> 00:46:01,303
an impact. 
It's just gonna take some time, 

786
00:46:01,303 --> 00:46:07,071
and it's 
 gonna be slower and 
more, yeah… May- slower is maybe

787
00:46:07,071 --> 00:46:10,129
the wrong word, but I 
 think 
we, it's the applications are 

788
00:46:10,129 --> 00:46:13,977
going to be more defined than 
just, you know, 
 we're gonna 

789
00:46:13,977 --> 00:46:17,705
try something and Willem, you're
trying it right now, and I don't

790
00:46:17,705 --> 00:46:21,167

 think you're building a next 
chatbot to, you know, interact 

791
00:46:21,167 --> 00:46:25,381
with the plant. 
Well, I think there, 
 there's a

792
00:46:25,381 --> 00:46:29,855
couple of things. 
First of all, a very big factor 

793
00:46:29,855 --> 00:46:34,529
that 
 determines how AI is 
impacting coding is that when 

794
00:46:34,529 --> 00:46:39,219
all the information that 
 you 
have, need, use, your processes,

795
00:46:39,279 --> 00:46:45,619
everything is already digitized.
It's pipelines, it's your 

796
00:46:45,619 --> 00:46:49,899
repositories. 
David, I don't know about you, 


797
00:46:49,907 --> 00:46:54,408
but most plants are not stuffed 
with highly contextualized 
 

798
00:46:54,416 --> 00:46:59,899
available data through APIs. 
So that-- The data is hidden. 

799
00:47:00,009 --> 00:47:03,006
It's hard to get to. 
Data quality is not always 

800
00:47:03,006 --> 00:47:05,059
there. 
It's inconsistent across plants.

801
00:47:05,059 --> 00:47:08,299
So I think first of all, there's

 a big aspect of data 

802
00:47:08,299 --> 00:47:09,849
availability that makes a big 
difference. 

803
00:47:10,195 --> 00:47:14,965
Yes, and you need that data. 
Also, Henry, because like almost

804
00:47:14,965 --> 00:47:20,571
every 
 plant is unique, which 
means that, it's like you can't 

805
00:47:20,571 --> 00:47:25,292
start training a 
 general model
on some general internet scraped

806
00:47:25,292 --> 00:47:31,605
data from Reddit whatever 
 you…
So you do need that plant data. 

807
00:47:33,419 --> 00:47:35,149
Yeah. 
I always tell people in projects

808
00:47:35,149 --> 00:47:38,787
like AI 
 can do cool stuff with
or without data, but if you want

809
00:47:38,787 --> 00:47:41,688
to make it useful, you'll 
 need
your own data to make it 

810
00:47:41,688 --> 00:47:46,491
relevant. 
Even if you get that data part 

811
00:47:46,491 --> 00:47:50,990
solved, 
 there is still a lot 
of work that needs to happen to 

812
00:47:50,990 --> 00:47:54,803
make that AI useful because 
 
the outputs that your AI gives 

813
00:47:54,803 --> 00:47:57,959
when you're coding is the 
artifact you need. 

814
00:47:58,729 --> 00:48:03,409
In manufacturing, the LLM is 
 
not gonna make me chocolates. 

815
00:48:03,629 --> 00:48:07,700
I mean, so you need to find ways
to 
 integrate it into your 

816
00:48:07,700 --> 00:48:10,459
processes to find out how it can
improve those processes. 

817
00:48:10,749 --> 00:48:16,292
So it's not that…, the impact is
not the 
 same as it does for 

818
00:48:16,292 --> 00:48:18,956
software engineering. 
I mean, in software 
 

819
00:48:18,964 --> 00:48:24,065
engineering completely changed. 
Maintenance engineering, not 

820
00:48:24,065 --> 00:48:27,173
yet. 
We need to get the data, and 
 

821
00:48:27,181 --> 00:48:31,312
if it does, it's gonna be more 
of a support to the process. 

822
00:48:31,682 --> 00:48:34,302
And even then, getting the data 
 is not going to be so easy. 

823
00:48:34,302 --> 00:48:37,452
We might have sensor data, but 
we 
 will also need 

824
00:48:37,452 --> 00:48:39,542
transactional data. 
We will need world models. 

825
00:48:39,542 --> 00:48:42,242
We will need to combine that 
knowledge. 

826
00:48:43,132 --> 00:48:47,000
Nothing of that, what I'm saying
is 
 like impossible, but those 

827
00:48:47,000 --> 00:48:50,938
are not artifacts that we have 
ready-made, 
 ready to use, plug

828
00:48:50,938 --> 00:48:53,272
and play. 
We need to build those. 

829
00:48:53,314 --> 00:48:57,145
Which means that I think if we 
lean 
 upon what we see in the 

830
00:48:57,145 --> 00:49:00,828
IT world today, what are the… 
When we, especially 
 when we 

831
00:49:00,828 --> 00:49:03,844
talk about GenAI obviously, what
are the things we see today? 

832
00:49:04,164 --> 00:49:06,764
That's configuration assistance,
yeah. 

833
00:49:06,934 --> 00:49:10,838
So, making it, so what we know 
from 
 the IT world, we see that

834
00:49:10,838 --> 00:49:13,474
more and more companies today, 
more and more 
 software co- 

835
00:49:13,474 --> 00:49:16,473
sorry, software companies and 
not the end users, but the 
 

836
00:49:16,481 --> 00:49:19,165
software companies, they are 
obviously making their software 

837
00:49:19,165 --> 00:49:22,149
easier to use. 
So instead of you programming 
 

838
00:49:22,157 --> 00:49:24,884
whatever control loop, whatever 
data integration pipeline, 

839
00:49:24,884 --> 00:49:27,670
whatever, yeah. 
Yes, obviously we see many 

840
00:49:27,670 --> 00:49:31,262
companies 
 now having some way 
to, with natural language, say 

841
00:49:31,262 --> 00:49:34,684
like, I want to do this, 
 and 
then the code just comes out. 

842
00:49:34,804 --> 00:49:37,382
So that's happening. 
It's happening again at a little

843
00:49:37,382 --> 00:49:39,854

 slower pace, and there is some
difference between companies. 

844
00:49:40,484 --> 00:49:45,234
But that's a very big aid, 
 
especially because we actually 

845
00:49:45,234 --> 00:49:48,906
don't have enough engineers in 
the 
 manufacturing world 

846
00:49:48,906 --> 00:49:52,323
globally, yeah. 
So everything we can do to make 

847
00:49:52,323 --> 00:49:56,849
their 
 job faster is not gonna…
I would say there won't be any 

848
00:49:56,849 --> 00:50:00,554
layoffs in our 
 world anytime 
soon, because there is just a 

849
00:50:00,554 --> 00:50:02,834
shortage in skilled people. 
So that's brilliant. 

850
00:50:03,804 --> 00:50:07,200
And something which we also see 
now 
 popping up is making it 

851
00:50:07,200 --> 00:50:09,824
easier to search through 
documents, you know. 

852
00:50:10,715 --> 00:50:12,834
Willem already mentioned 
 
pharmaceutical industry. 

853
00:50:13,004 --> 00:50:15,918
We see, for example, in the 
pharmaceutical 
 industry, 

854
00:50:15,918 --> 00:50:21,159
generative AI being used to make
the legal processes, so the 
 

855
00:50:21,167 --> 00:50:26,504
creation of all these documents,
around changes to make that 

856
00:50:26,504 --> 00:50:29,304
easier. 
So those are things we do see. 

857
00:50:30,284 --> 00:50:33,486
But you see it's a bit more on 
the, 
 you know, the document 

858
00:50:33,486 --> 00:50:36,212
side of things. 
It's a bit more on the end, 

859
00:50:36,212 --> 00:50:40,428
yeah, 
 the pure coding side of 
things, what you expect, to be 

860
00:50:40,428 --> 00:50:43,992
honest. 
But its real impact on the 

861
00:50:43,992 --> 00:50:46,704
process 
 itself, that's gonna 
take a while. 

862
00:50:47,574 --> 00:50:48,948
Yeah. 
Yeah. 

863
00:50:49,198 --> 00:50:51,532
I think you mentioned about a 
very 
 interesting example just 

864
00:50:51,532 --> 00:50:53,750
now, right? 
Using GenAI to produce like 
 

865
00:50:53,758 --> 00:50:57,293
maybe chocolate, right? 
So maybe, I don't know, because 

866
00:50:57,293 --> 00:50:59,638
of the 
 unpredictability of AI 
output, right? 

867
00:50:59,678 --> 00:51:02,654
Maybe sometimes you can get a, 
like a mix 
 of chocolate, which

868
00:51:02,654 --> 00:51:06,510
makes it interesting. 
But I dare you to ask, you can 


869
00:51:06,518 --> 00:51:08,494
ask ChatGPT, "Please make me a 
chocolate." 

870
00:51:08,494 --> 00:51:11,992
You'll get a nice piece 
 of 
text explaining you how to make 

871
00:51:11,992 --> 00:51:14,512
chocolate, but you still have to
go 
 out and make the chocolate 

872
00:51:14,512 --> 00:51:17,064
yourself. 
Yeah, which brings to the 
 as- 

873
00:51:17,064 --> 00:51:20,053
the safety aspect, right? 
I don't know also how safety it 

874
00:51:20,053 --> 00:51:22,506
is, you know, using GenAI to 
 
produce the chocolate. 

875
00:51:22,556 --> 00:51:26,196
Hallucinations are also big, 
 a
big factor, especially in 

876
00:51:26,216 --> 00:51:27,916
manufacturing when it comes to 
trust. 

877
00:51:29,486 --> 00:51:33,804
Trust is really something that 
has 
 to be earned, always with 

878
00:51:33,804 --> 00:51:36,121
users. 
But engineers are like a bit 
 

879
00:51:36,129 --> 00:51:39,356
difficult in terms of users. 
Like they want to know exactly 

880
00:51:39,356 --> 00:51:43,181
why did you 
 propose this and 
how did you come up with the 

881
00:51:43,181 --> 00:51:44,756
solution and what data did you 
get. 

882
00:51:45,816 --> 00:51:47,586
If you can do it, you'll gain 
their trust. 

883
00:51:47,596 --> 00:51:51,446
But especially with AI, if they 
just 
 get a hint of any 

884
00:51:51,446 --> 00:51:53,956
hallucination, you can quickly 
lose trust. 

885
00:51:54,972 --> 00:51:57,112
Right. 
Also another interesting that 

886
00:51:57,112 --> 00:52:00,848
David 
 mentioned is about, you 
know, the lack of engineers in 

887
00:52:00,848 --> 00:52:04,317
the OT world, right? 
Maybe one funny thing is like, 


888
00:52:04,325 --> 00:52:06,837
maybe all the software engineers
who feel threatened, maybe you 


889
00:52:06,845 --> 00:52:10,164
can now explore the OT side. 
You're welcome! 

890
00:52:11,948 --> 00:52:14,072
But I think it's very 
interesting. 

891
00:52:14,072 --> 00:52:17,296
Why is it such a lack of, you 
know, 
 software eng- like, what

892
00:52:17,296 --> 00:52:18,932
do you- do you call it software 
engineers? 

893
00:52:19,322 --> 00:52:21,728
Like, why is it the lack of… 
Automation engineers. 

894
00:52:21,902 --> 00:52:26,782
We call it automation engineers.
Like so it's an education 

895
00:52:26,782 --> 00:52:28,848
problem, Henry. 
It's really an education 

896
00:52:28,848 --> 00:52:31,260
problem. 
It's not because there is no job

897
00:52:31,260 --> 00:52:34,248

 certainty or it doesn't pay 
well or, you know, whatever, or 

898
00:52:34,248 --> 00:52:37,106
it's not 
 cool because it's 
like, you know, how cool is it 

899
00:52:37,106 --> 00:52:39,758
that you're writing 
 code and 
you see things move like up. 

900
00:52:41,176 --> 00:52:44,888
It's like your Raspberry Pi 
project 
 at home, but like at a

901
00:52:44,888 --> 00:52:47,592
massive scale. 
But it's an education problem. 

902
00:52:48,342 --> 00:52:51,760
So actually I had, but it's 
already 
 a while ago, two years

903
00:52:51,760 --> 00:52:55,523
or so ago actually, I had 
somebody from the 
 US on our 

904
00:52:55,523 --> 00:52:58,112
podcast talking about education 
as well in the US then. 

905
00:52:58,232 --> 00:53:02,680
I can only talk about Europe. 
But automation engineering is 

906
00:53:02,680 --> 00:53:08,023
something 
 like you, there are 
exceptions, but in most 

907
00:53:08,023 --> 00:53:11,925
universities or most 
 high 
schools, that's typically not 

908
00:53:11,925 --> 00:53:16,069
really a path you can choose. 
Like computer science, 
 that's 

909
00:53:16,069 --> 00:53:17,992
a path everywhere. 
You know? 

910
00:53:17,992 --> 00:53:22,576
It, like, there is not a single 
 educa- high school and 

911
00:53:22,576 --> 00:53:26,888
university type of, which 
doesn't get, yeah, 
 where you 

912
00:53:26,888 --> 00:53:31,112
can't do something around, you 
know, AI or computer science. 

913
00:53:31,462 --> 00:53:35,908
But automation engineering is 
 
typically more part of a 

914
00:53:35,908 --> 00:53:39,868
technical educational program 
which is 
 in my opinion, 

915
00:53:39,868 --> 00:53:43,511
totally wrong. 
Like that's, it's like, it 
 

916
00:53:43,519 --> 00:53:45,996
should be more broadly 
available. 

917
00:53:46,866 --> 00:53:50,336
But that's the most important 
thing, 
 is that you, the 

918
00:53:50,336 --> 00:53:54,450
choices people make, and it's 
often also seen, and what 
 I'm 

919
00:53:54,450 --> 00:54:00,323
gonna say right now is maybe, 
it's, I mean it in the best 

920
00:54:00,323 --> 00:54:04,900
possible 
 way, but people often
see going for a technical 

921
00:54:04,900 --> 00:54:10,966
education as less interesting 
 
for their future career, right? 

922
00:54:11,876 --> 00:54:16,308
Where, you know, they wanna be 
the, they 
 wanna have a 

923
00:54:16,308 --> 00:54:21,721
master's degree in whatnot. 
Whereas these technical jobs are

924
00:54:21,721 --> 00:54:26,920

 what, you know, our society is
running on, on electricians and 

925
00:54:26,920 --> 00:54:29,916
automation 
 people and plumbers
and, you know. 

926
00:54:31,716 --> 00:54:35,236
And that's a bit of the problem,
yeah, 
 there is that there is 

927
00:54:35,236 --> 00:54:39,342
this split and there are, there 
is thus just not enough 
 people

928
00:54:39,342 --> 00:54:42,346
coming from that education. 
And I know it's a problem in 

929
00:54:42,346 --> 00:54:44,356
Europe. 
I know it's a problem in the US 

930
00:54:44,356 --> 00:54:45,496
 as well, although it is 
changing. 

931
00:54:46,526 --> 00:54:49,810
And I, yeah, I don't know about 
Asia, 
 but that's the most 

932
00:54:49,810 --> 00:54:51,562
important one. 
Yeah. 

933
00:54:51,612 --> 00:54:54,670
How about robotics? 
I think we can see the 
 trend 

934
00:54:54,670 --> 00:54:57,362
is picking up, right? 
People also talk about robotics 

935
00:54:57,362 --> 00:55:00,655
 replacing humans and all that. 
So is it also something that you

936
00:55:00,655 --> 00:55:03,366
see 
 picking up traction, you 
know, with this IT/OT work 

937
00:55:03,366 --> 00:55:05,308
merging together? 
Yeah, since the '70s. 

938
00:55:05,548 --> 00:55:09,336
Since the '70s, I mean, robots 
have 
 been in manufacturing 

939
00:55:09,336 --> 00:55:15,173
since a long time. 
I think David recently you just 

940
00:55:15,173 --> 00:55:19,092
 went into a warouse, humongous,
like one or two guys, they just 

941
00:55:19,092 --> 00:55:20,628
 walk around and they fix 
problems. 

942
00:55:21,952 --> 00:55:23,892
Yeah. 
And then it's… football pitches 

943
00:55:23,892 --> 00:55:28,622
like in 
 size, and you only 
have an operator who is dealing 

944
00:55:28,622 --> 00:55:32,422
with the errors, basically. 
And everything else is 
 purely,

945
00:55:32,422 --> 00:55:36,552
purely robots. 
But I think Willem, as you 
 

946
00:55:36,560 --> 00:55:41,108
mentioned, for us, robot is 
something we've been done since 

947
00:55:41,108 --> 00:55:44,812
decades. 
Like the fact that we are now 

948
00:55:44,812 --> 00:55:48,328
talking 
 about humanoids, 
honestly, that is not changing 

949
00:55:48,328 --> 00:55:53,047
a- anything, right? 
Like humanoids, it's very fun, 


950
00:55:53,055 --> 00:55:57,312
but the manufacturing industry 
does not require humanoids. 

951
00:55:57,352 --> 00:56:02,258
Let's be really honest. 
I think also most plants and, 

952
00:56:02,258 --> 00:56:06,416
and 
 processes are not 
necessarily made to fit very 

953
00:56:06,416 --> 00:56:11,446
well to humanoids. 
Like I said, there's already a 

954
00:56:11,446 --> 00:56:15,184
lack of 
 data in many cases 
just to get a normal AI model 

955
00:56:15,184 --> 00:56:18,439
working, let alone having 
 a 
humanoid walking in an 

956
00:56:18,439 --> 00:56:20,480
environment where safety could 
be impacted. 

957
00:56:20,840 --> 00:56:25,223
Now, are there no applications? 
I mean, stuff will come up, but 

958
00:56:25,223 --> 00:56:28,610
automation 
 is-- has a lot to 
do with that part. 

959
00:56:28,610 --> 00:56:35,336
Like just imagine, David, you 
need to 
 engineer that pitches 

960
00:56:35,336 --> 00:56:39,274
sized warehouse, fully 
automated, trucks come in, stuff

961
00:56:39,274 --> 00:56:40,910

 gets unloaded, sorted 
everywhere. 

962
00:56:41,220 --> 00:56:44,393
I mean, it's a huge engineering 
 puzzle that already exists 

963
00:56:44,393 --> 00:56:46,110
today. 
It's lights out. 

964
00:56:47,390 --> 00:56:50,212
And it's not just because of 
humanoid 
 robots which get all 

965
00:56:50,212 --> 00:56:53,618
the attention now. 
No, because a humanoid is 
 

966
00:56:53,626 --> 00:56:57,883
basically a generalistic robot. 
So the, a humanoid is where for 

967
00:56:57,883 --> 00:57:02,568
some 
 reason we thought it was 
an idea to mimic how a human 

968
00:57:02,568 --> 00:57:08,678
looks like in a 
 robot form, 
which means that they might be, 

969
00:57:08,678 --> 00:57:15,116
the, it might be possible 
 to 
make them do generalistic tasks 

970
00:57:15,456 --> 00:57:20,192
at a certain pace, we want that,

 we really want that to turn 

971
00:57:20,192 --> 00:57:22,394
around. 
We need extremely performant 

972
00:57:22,394 --> 00:57:28,243
robots 
 to do one or a set of 
specific tasks very well, 

973
00:57:28,243 --> 00:57:31,886
clearly defined. 
And we also see that 
 changing 

974
00:57:31,886 --> 00:57:34,191
obviously, yeah. 
So the robot world is changing a

975
00:57:34,191 --> 00:57:35,946
lot. 
We see more applications. 

976
00:57:35,956 --> 00:57:39,906
We see, for example, programming
robots becomes much, much, much 

977
00:57:39,906 --> 00:57:42,966
easier 
 today than it was some 
years ago, yeah. 

978
00:57:43,086 --> 00:57:46,036
Generative AI, again, is 
 a 
very, very big help. 

979
00:57:48,016 --> 00:57:53,426
But having said that, like in 
 
my opinion, it's an evolution. 

980
00:57:53,566 --> 00:57:55,636
It's already started, and 
 it 
will keep on going. 

981
00:57:55,916 --> 00:57:59,188
It's not really like this big 
revolution 
 where all of a 

982
00:57:59,188 --> 00:58:04,711
sudden, I always say the joke I 
sometimes make is when I see 
 

983
00:58:04,719 --> 00:58:06,866
this robo-dog walking around 
somewhere. 

984
00:58:07,466 --> 00:58:10,342
It's not because you buy an 
expensive 
 robo-dog who walks 

985
00:58:10,342 --> 00:58:13,616
around in your plant, that all 
of a sudden 
 your plant becomes

986
00:58:13,616 --> 00:58:17,864
more optimal. 
Like, b- b- b- it's a fun… 
 It 

987
00:58:17,864 --> 00:58:21,436
could make sense, yeah. 
It could make sense, for 

988
00:58:21,436 --> 00:58:25,106
example, to have 
 a robo-dog 
walk around a very hazardous 

989
00:58:25,106 --> 00:58:27,644
place, where you don't wanna 
send people, 
 and there are 

990
00:58:27,644 --> 00:58:31,772
brilliant examples for that. 
But that's not gonna change the 

991
00:58:31,772 --> 00:58:35,814
 output dramatically of our, or 
even at all, of our 

992
00:58:35,814 --> 00:58:40,237
manufacturing process. 
Another thing to keep in mind is

993
00:58:40,237 --> 00:58:45,161
the 
 amount of manual labor in 
most big industries is actually 

994
00:58:45,161 --> 00:58:49,562
already quite low. 
Most of the cost is 
 actually 

995
00:58:49,562 --> 00:58:52,811
in the assets. 
I mean, just drive by a plant, 

996
00:58:52,811 --> 00:58:55,292
just 
 think about all the 
machines in there, etc. 

997
00:58:55,292 --> 00:59:00,789
The IP that they have, 
 the 
real manual labor is most of the

998
00:59:00,789 --> 00:59:03,616
time a fraction of the cost. 
So the business case to, let's 

999
00:59:03,616 --> 00:59:07,305
say, I'm 
 gonna replace people 
with robots to save on labor 

1000
00:59:07,305 --> 00:59:12,177
cost, I think if you're gonna 
 
look at the total picture, you 

1001
00:59:12,177 --> 00:59:14,693
would need to replace that human
with robots. 

1002
00:59:15,153 --> 00:59:17,267
It's gonna be a hard 
 project 
to sell for now. 

1003
00:59:17,307 --> 00:59:19,747
And again, we're talking about 

the manufacturing plants, the 

1004
00:59:19,747 --> 00:59:25,079
process plants, et cetera. 
Obviously in the supply chain 
 

1005
00:59:25,087 --> 00:59:29,069
world, that's different. 
Yeah. 

1006
00:59:29,379 --> 00:59:32,258
So I think the keyword I picked 
 is the generalist aspect, 

1007
00:59:32,258 --> 00:59:35,156
right? 
So we are seeing a lot of buzz 

1008
00:59:35,156 --> 00:59:38,493
and 
 hype, you know, talking 
about, you know, more generalist

1009
00:59:38,493 --> 00:59:41,977
robots where 
 maybe I can see 
like robots folding your 

1010
00:59:41,977 --> 00:59:44,995
clothes, you know, sending 
 
delivery, you know, supply 

1011
00:59:44,995 --> 00:59:47,889
chain, you know, driverless cars
and all that. 

1012
00:59:47,969 --> 00:59:51,689
So definitely it's a new, 
probably a new 
 kind of a 

1013
00:59:51,689 --> 00:59:55,094
industrial thing that maybe one 
day can be more interesting, you

1014
00:59:55,094 --> 00:59:56,939
know. 
But obviously what you shared 

1015
00:59:56,939 --> 01:00:00,629
today, 
 it, I hope it opened up
the kind of like perspective for

1016
01:00:00,629 --> 01:00:02,929
many of us that, 
 you know, 
there's this world as well, 

1017
01:00:02,949 --> 01:00:04,769
right, that we have to 
collaborate. 

1018
01:00:04,779 --> 01:00:07,455
That's the first thing, right? 
Because you come up with seven 


1019
01:00:07,463 --> 01:00:08,679
different collaboration 
patterns, right? 

1020
01:00:08,979 --> 01:00:11,109
And how we can optimize working 
together. 

1021
01:00:11,489 --> 01:00:14,155
And also not to mention that we 
have 
 to empathize with each 

1022
01:00:14,155 --> 01:00:16,682
other, right? 
So like IT might have its own 

1023
01:00:16,682 --> 01:00:19,638
practice, 
 best practices, but 
at the same time, OT also has 

1024
01:00:19,638 --> 01:00:22,617
its own best practices. 
I think we have covered 
 quite 

1025
01:00:22,617 --> 01:00:25,729
a fair bit of topics. 
Is there anything that you think

1026
01:00:25,729 --> 01:00:29,219
might 
 be worth to also mention
here before we wrap up for our 

1027
01:00:29,219 --> 01:00:30,709
last question? 
Buy the book. 

1028
01:00:34,199 --> 01:00:40,433
Nice one. 
Yeah, I think the book gave us a

1029
01:00:40,433 --> 01:00:43,603

 chance to like really dig 
deeper on the topics we 

1030
01:00:43,603 --> 01:00:46,487
discussed here. 
Like really go a bit and take 
 

1031
01:00:46,495 --> 01:00:49,735
our time to find out what's 
really behind those things. 

1032
01:00:50,275 --> 01:00:52,635
How do those cooperation 
 
patterns look like? 

1033
01:00:52,645 --> 01:00:56,161
How do you get started? 
How do you decouple the two 

1034
01:00:56,161 --> 01:00:59,115
worlds so you 
 can start to 
move at different speeds? 

1035
01:00:59,125 --> 01:01:01,805
I think that's all things 
 you 
can find in our book. 

1036
01:01:01,895 --> 01:01:04,465
You see, and that's also how 
 
our, we, how we work together. 

1037
01:01:04,605 --> 01:01:07,234
So I just give the stupid 
answers and then 
 Willem, you 

1038
01:01:07,234 --> 01:01:13,309
know, he smooths things out. 
Actually, I kill half of 
 his 

1039
01:01:13,309 --> 01:01:18,871
ideas, if not more. 
But maybe that's why the, you 

1040
01:01:18,871 --> 01:01:20,437
know, 
 the collaboration 
actually works. 

1041
01:01:20,531 --> 01:01:25,315
Yeah. 
So yeah, thank you so 
 much for

1042
01:01:25,315 --> 01:01:27,467
sharing this. 
I think, for people who are 

1043
01:01:27,467 --> 01:01:29,985
interested, 
 maybe you live in 
both of these worlds or maybe 

1044
01:01:29,985 --> 01:01:32,444
one world who are interested, 
 
you know, on the other world, 

1045
01:01:32,444 --> 01:01:35,731
please check out the book, 
right, it's 
 published under IT

1046
01:01:35,731 --> 01:01:38,645
Revolution, right? 
So definitely, I mean, I assume 

1047
01:01:38,645 --> 01:01:42,642
by, 
 picked up by IT Revolution
means this book potentially can 

1048
01:01:42,642 --> 01:01:45,327
change the industry. 
Because we have seen so many 

1049
01:01:45,327 --> 01:01:47,901
examples 
 where books from IT 
Revolution change the industry, 

1050
01:01:47,901 --> 01:01:50,050
like Team Topologies 
 you 
mentioned, Phoenix Project, 

1051
01:01:50,050 --> 01:01:52,467
right, DevOps Handbook, so many 
of those, right? 

1052
01:01:52,777 --> 01:01:56,287
So I have one last question 
 
for both of you, right? 

1053
01:01:56,307 --> 01:01:58,337
I call this the three 
 
technical leadership wisdom. 

1054
01:01:58,357 --> 01:02:00,652
It's like a tradition in my 
podcast to 
 ask my guests to 

1055
01:02:00,652 --> 01:02:02,885
share about this so that 
listeners can learn from both of

1056
01:02:02,885 --> 01:02:05,193
you. 
So maybe I'll leave it up to you

1057
01:02:05,193 --> 01:02:07,467

 how you wanna structure it, 
but if you can leave some wisdom

1058
01:02:07,467 --> 01:02:09,677
for us to 
 learn, I think that 
would be great. 

1059
01:02:10,685 --> 01:02:12,295
Who goes first, Willem? 
Me or you? 

1060
01:02:13,667 --> 01:02:19,225
You go first. 
So, my first one is I… So 
 the 

1061
01:02:19,225 --> 01:02:24,475
title is, Be Like James. 
And w- so, in this case, 
 I 

1062
01:02:24,475 --> 01:02:29,599
mean James Bond 007. 
So, you know, so for some reason

1063
01:02:29,599 --> 01:02:33,875

 I love the movie, the movies. 
So for some reason, Henry, like 

1064
01:02:33,875 --> 01:02:38,795
 James Bond always has a dinner 
or lunch with his enemy, which 

1065
01:02:38,795 --> 01:02:41,565
like 
 is super strange in my 
opinion. 

1066
01:02:42,695 --> 01:02:46,637
But when we are talking here 
 
about, you know, the IT/OT 

1067
01:02:46,637 --> 01:02:50,965
divide, unfortunately, tensions 
often rise in 
 those 

1068
01:02:50,965 --> 01:02:54,884
discussions, and unfortunately 
we often treat each other as the

1069
01:02:54,884 --> 01:02:57,970
enemy. 
So my advice is like, be like 

1070
01:02:57,970 --> 01:03:00,379
James. 
Step over the differences and 

1071
01:03:00,379 --> 01:03:03,515
have 
 lunch or have dinner with
your enemy. 

1072
01:03:03,795 --> 01:03:05,885
But then just doesn't, 
 don't 
kill them, you know? 

1073
01:03:06,135 --> 01:03:09,845
Just start working on 
 a 
collaboration model. 

1074
01:03:10,035 --> 01:03:13,595
So mine is Be Like James. 
Willem, which one did you bring?

1075
01:03:15,459 --> 01:03:18,319
And that is actually true. 
He is like James in that aspect.

1076
01:03:19,799 --> 01:03:24,904
Mine is know how to be a 
gardener 
 and a carpenter and 

1077
01:03:24,904 --> 01:03:29,455
when to switch. 
So we've managed decently 
 

1078
01:03:29,463 --> 01:03:35,009
sized teams and groups. 
And there's two ways to do work.

1079
01:03:35,399 --> 01:03:36,839
The first one is like the 
carpenter. 

1080
01:03:36,849 --> 01:03:41,813
You go in, you try to fix 
things, 
 which is great, except

1081
01:03:41,813 --> 01:03:44,529
it's absolutely horrendous when 
you need to scale. 

1082
01:03:45,399 --> 01:03:47,019
You can only solve that many 
problems. 

1083
01:03:47,329 --> 01:03:52,559
So instead, try to be a gardener

 and look at your teams like 

1084
01:03:52,569 --> 01:03:55,756
your garden, and let them grow. 
And you need to find out what 

1085
01:03:55,756 --> 01:03:58,128
they need 
 to grow, and that 
means working on their context, 

1086
01:03:58,128 --> 01:03:59,739
finding out what makes them 
work. 

1087
01:04:00,229 --> 01:04:03,377
And if all goes well, David, you

 can just sit back and relax 

1088
01:04:03,377 --> 01:04:05,339
just long enough to enjoy the 
garden. 

1089
01:04:06,101 --> 01:04:07,331
No, no, but that's a really good
one. 

1090
01:04:07,631 --> 01:04:12,151
And let's finish with a, with 
 
just maybe with a more normal 

1091
01:04:12,181 --> 01:04:18,085
one, more normal one, Henry. 
I think the most important like 

1092
01:04:18,085 --> 01:04:21,331
takeaway 
 when we're talking 
about, yeah, projects, 

1093
01:04:21,331 --> 01:04:26,319
cooperation, et cetera, et 
cetera, is 
 always like in, as 

1094
01:04:26,319 --> 01:04:31,097
I already said, always know when
you're starting a project, when 

1095
01:04:31,097 --> 01:04:34,728
 you're starting a new idea, 
understand what is gonna happen 

1096
01:04:34,728 --> 01:04:37,844
after the project. 
And that means that when you are

1097
01:04:37,844 --> 01:04:41,527
in 
 a meeting, when you are a 
manager or when you are an 

1098
01:04:41,527 --> 01:04:44,598
individual contributor, 
 and 
you feel that everybody is 

1099
01:04:44,598 --> 01:04:47,019
talking about big ideas and, 
"Oh, we're gonna 
 do this and 

1100
01:04:47,019 --> 01:04:51,771
we're gonna do that," be that 
one who says, "Ho, stop. 

1101
01:04:52,371 --> 01:04:55,440
Stop for a moment. 
Like this is a brilliant idea, 


1102
01:04:55,448 --> 01:04:59,129
but how are we going to act? 
How are we going to, yeah, 
 

1103
01:04:59,137 --> 01:05:02,496
behave as a group, as a company?
How are we going to be 

1104
01:05:02,496 --> 01:05:05,581
organized? 
How are we going to be budgeted 

1105
01:05:05,581 --> 01:05:08,861
after 
 this brilliant idea is, 
yeah, is live?" 

1106
01:05:11,011 --> 01:05:12,874
Wow. 
I think this is very unique, 

1107
01:05:12,874 --> 01:05:14,674
right? 
First is be like James, James 

1108
01:05:14,674 --> 01:05:17,516
Bond. 
Second is be a gardener 
 rather

1109
01:05:17,516 --> 01:05:20,595
than a carpenter. 
The third I would summarize like

1110
01:05:20,595 --> 01:05:23,119
be 
 like an oracle, you know, 
kind of like predict what will 

1111
01:05:23,119 --> 01:05:25,187
happen next. 
I'm gonna remember that one. 

1112
01:05:25,597 --> 01:05:30,063
I'm gonna use a Be an Oracle. 
It sounds better than be that 
 

1113
01:05:30,071 --> 01:05:32,946
annoying guy who asks the 
annoying questions during the 

1114
01:05:32,946 --> 01:05:33,973
steerco. 
Be like a gardener, be like 
 

1115
01:05:33,981 --> 01:05:35,343
James, and be an oracle. 
Willem, I'm gonna write it 
 

1116
01:05:35,351 --> 01:05:38,773
down in my mind and in the next 
podcast, those are the three. 

1117
01:05:40,019 --> 01:05:42,047
Right. 
So really appreciate your 

1118
01:05:42,047 --> 01:05:44,509
sharing today. 
I really learned, you know, 
 

1119
01:05:44,517 --> 01:05:47,389
new things, new paradigm. 
So not only just software 
 

1120
01:05:47,397 --> 01:05:49,629
engineering, you know, IT world,
digital products and all that. 

1121
01:05:49,629 --> 01:05:51,459
So I really appreciate your 
sharing today. 

1122
01:05:51,749 --> 01:05:54,725
And hopefully, yeah, people can 
learn 
 a thing or two as well 

1123
01:05:54,725 --> 01:05:57,039
from your world. 
And also, for example, like 
 

1124
01:05:57,047 --> 01:06:00,234
put safety in front, right? 
Rather than always, you know, 
 

1125
01:06:00,242 --> 01:06:02,079
releasing fast, break things, 
right? 

1126
01:06:02,349 --> 01:06:05,709
So I think we have to understand

 and empathize different world.

1127
01:06:06,019 --> 01:06:09,496
And thanks so much as well for, 
 you know, sharing the impact of

1128
01:06:09,496 --> 01:06:13,058
AI on your world, right? 
So probably it's also something 

1129
01:06:13,058 --> 01:06:16,299
that 
 kind of like refreshing 
because all in the news that we 

1130
01:06:16,299 --> 01:06:17,809
see is like, 
 you know, we are 
doomed, right? 

1131
01:06:17,809 --> 01:06:19,649
Software engineers is 
 gonna be
gone and all that. 

1132
01:06:19,719 --> 01:06:20,815
We're gonna be replaced. 
But it's okay. 

1133
01:06:21,705 --> 01:06:23,697
We're gonna be fine. 
There's more engineers. 

1134
01:06:24,689 --> 01:06:26,459
There's more eng- there's 
 more
engineers, yeah. 

1135
01:06:26,459 --> 01:06:28,409
So, okay. 
So yeah, thank you so much. 

1136
01:06:28,439 --> 01:06:31,090
I hope, you know, many people 
will 
 read the book, and I hope

1137
01:06:31,090 --> 01:06:33,641
it can also change the industry 
just like any 
 other IT 

1138
01:06:33,641 --> 01:06:36,101
Revolution books as well. 
Thank you so much. 

1139
01:06:37,005 --> 01:06:37,325
Thank you.
