WEBVTT
Language: en-US

1
00:00:01.110 --> 00:00:06.630
<v Nick Leeder>It just shows you the mentality of how we
think about selecting software.

2
00:00:07.400 --> 00:00:12.829
<v Nick Leeder>And actually they should be balanced
because if it can do 4000 things out of the

3
00:00:12.829 --> 00:00:17.840
<v Nick Leeder>box, but nobody uses it, it adds no value,
yeah.

4
00:00:18.399 --> 00:00:23.120
<v Nick Leeder>So, uh, you know, and I'm, I'm painting
that as a very, very extreme picture, but

5
00:00:23.120 --> 00:00:28.500
<v Nick Leeder>the usability is fundamentally driving the
adoption of these applications.

6
00:00:29.239 --> 00:00:34.380
<v Speaker 2>Welcome to the trend detection podcast
powered by Siemens, and now your host Nel

7
00:00:34.380 --> 00:00:34.919
<v Speaker 2>Sullivan.

8
00:00:36.880 --> 00:00:40.939
<v Speaker 3>Hello and welcome to the latest episode of
the Trend detection podcast.

9
00:00:41.650 --> 00:00:45.159
<v Speaker 3>Uh, really pleased to be joined by one of
our regulars, one of our favorite

10
00:00:45.159 --> 00:00:45.659
<v Speaker 3>regulars.

11
00:00:45.720 --> 00:00:49.799
<v Speaker 3>I'm gonna add to that, er, Nick Leader,
who you'll know from many podcasts, who

12
00:00:49.799 --> 00:00:53.779
<v Speaker 3>joined our live event a few months ago,
which was also published on here.

13
00:00:54.209 --> 00:00:56.259
<v Speaker 3>Um, but you're back again, Nick, so
welcome back.

14
00:00:56.459 --> 00:00:56.580
<v Speaker 3>How,

15
00:00:56.700 --> 00:00:57.299
<v Nick Leeder>how have

16
00:00:57.299 --> 00:00:57.500
<v Speaker 3>things

17
00:00:57.500 --> 00:00:58.360
<v Nick Leeder>been for having me.

18
00:00:59.659 --> 00:01:01.700
<v Nick Leeder>Good, uh, hopefully everybody had a good
summer as well.

19
00:01:01.779 --> 00:01:06.900
<v Nick Leeder>I mean, it's, uh, now's the time of rest
and recuperation really and back into the

20
00:01:06.900 --> 00:01:11.860
<v Nick Leeder>full swing of things, um, as we, as we hit
the final quarters or uh the final few

21
00:01:11.860 --> 00:01:12.599
<v Nick Leeder>months of the year.

22
00:01:13.930 --> 00:01:18.879
<v Speaker 3>Excellent, yeah, same here, same here, I
have to say, but today we're talking about,

23
00:01:19.089 --> 00:01:23.410
<v Speaker 3>um, a very important topic, and a topic
that sort of emerged over the past year, 18

24
00:01:23.410 --> 00:01:26.849
<v Speaker 3>months, I guess, around sort of skills
shortage, and, uh, you know, anyone

25
00:01:27.370 --> 00:01:31.769
<v Speaker 3>industrial manufacturing space will know
all about this, um, but we're, we're sort

26
00:01:31.769 --> 00:01:35.449
<v Speaker 3>of framing this episode a little bit
around, um, a blog you did for the World

27
00:01:35.449 --> 00:01:36.510
<v Speaker 3>Economic Forum.

28
00:01:36.919 --> 00:01:41.430
<v Speaker 3>Um, which we can of course link to in the
show notes as well afterwards, but maybe

29
00:01:41.430 --> 00:01:45.040
<v Speaker 3>you could sort of just open the
conversation, Nick, just explain sort of the

30
00:01:45.040 --> 00:01:48.160
<v Speaker 3>background to the post and the background
maybe to this episode as well, like what,

31
00:01:48.319 --> 00:01:49.660
<v Speaker 3>what are we're gonna sort of cover today.

32
00:01:50.970 --> 00:01:57.069
<v Nick Leeder>So, um, I, I think I guess the background
was I hear the word skills shortage a lot.

33
00:01:57.879 --> 00:02:03.819
<v Nick Leeder>And um and it's undeniable that the
workforce is aging in the manufacturing sector

34
00:02:03.959 --> 00:02:09.119
<v Nick Leeder>and more and more people are retiring or
coming up to retirement and there is a real

35
00:02:09.119 --> 00:02:14.960
<v Nick Leeder>challenge of attracting um the younger
generations into the industry.

36
00:02:15.860 --> 00:02:22.639
<v Nick Leeder>Um And a lot of it is focused around, oh
look, we don't have, people aren't

37
00:02:22.639 --> 00:02:27.029
<v Nick Leeder>interested in manufacturing, which I kind
of I kind of understand because there's a

38
00:02:27.029 --> 00:02:31.399
<v Nick Leeder>legacy of uh kind of being a bit of a
dirty or conceptually being a dirty industry

39
00:02:31.399 --> 00:02:33.460
<v Nick Leeder>which isn't, it's a false idea.

40
00:02:33.960 --> 00:02:39.759
<v Nick Leeder>But actually what I was also looking at
and grappling at is are we making it easy to

41
00:02:39.759 --> 00:02:41.000
<v Nick Leeder>attract the talent.

42
00:02:41.559 --> 00:02:46.289
<v Nick Leeder>And particularly when it comes to the
applications that we use within the

43
00:02:46.289 --> 00:02:51.490
<v Nick Leeder>manufacturing working environment, you
know, ERP systems, MES, predictive

44
00:02:51.490 --> 00:02:57.250
<v Nick Leeder>maintenance technologies, those sort of
things, and looking at that and going, well,

45
00:02:57.399 --> 00:03:03.089
<v Nick Leeder>are these actually helping attract talent
or actually are they a barrier for the uh

46
00:03:03.089 --> 00:03:05.639
<v Nick Leeder>bringing these skills or new skills into
it.

47
00:03:05.889 --> 00:03:08.550
<v Nick Leeder>So do we, do we have a skills shortage?

48
00:03:09.339 --> 00:03:12.029
<v Nick Leeder>Or do we have a usability crisis?

49
00:03:12.389 --> 00:03:17.820
<v Nick Leeder>um, and I, you know, I frame that question
in black and white because I think, um,

50
00:03:17.830 --> 00:03:21.229
<v Nick Leeder>having used many different applications
over the years, I don't think it is quite

51
00:03:21.229 --> 00:03:24.860
<v Nick Leeder>black and white and I'm sure we'll go into
that as we go through today's

52
00:03:24.860 --> 00:03:25.029
<v Nick Leeder>conversation.

53
00:03:27.169 --> 00:03:31.059
<v Speaker 3>Yeah, and it can, it attracting talent
because you'd, you'd, you'd imagine with all,

54
00:03:31.169 --> 00:03:35.940
<v Speaker 3>you know, this new technology, you know,
AI, we know about AI IoT automation.

55
00:03:36.009 --> 00:03:39.259
<v Speaker 3>It's, it's quite good in, on the face of
it, maybe a little bit of an outsider

56
00:03:39.259 --> 00:03:44.490
<v Speaker 3>perspective for me, it's a really cool
space to be in, but is that not reflected in,

57
00:03:44.559 --> 00:03:46.080
<v Speaker 3>in reality, let's say.

58
00:03:46.580 --> 00:03:50.970
<v Nick Leeder>Well, cool, cool and manufacturing kind of
go together when we talk about

59
00:03:50.970 --> 00:03:54.440
<v Nick Leeder>manufacturing technology as in the art of
producing things.

60
00:03:55.470 --> 00:04:01.460
<v Nick Leeder>But cool and manufacturing doesn't really
go always because I, I wrote a blog, a

61
00:04:01.460 --> 00:04:05.199
<v Nick Leeder>blog a while ago saying there's no fashion
in manufacturing.

62
00:04:06.610 --> 00:04:12.229
<v Nick Leeder>You know, there's a reason why we still
use PLCs from the 1980s on the shop floor

63
00:04:13.289 --> 00:04:15.669
<v Nick Leeder>because they work and they haven't broken.

64
00:04:15.889 --> 00:04:20.089
<v Nick Leeder>And until they break, nobody's actually
gonna do about it, you know, manufacturing

65
00:04:20.089 --> 00:04:24.730
<v Nick Leeder>is about producing things profitably,
safely, in the right quantity at the right

66
00:04:24.730 --> 00:04:31.149
<v Nick Leeder>time, and anything that affects risk
around those things, um, are, are, are kind of

67
00:04:32.130 --> 00:04:35.089
<v Nick Leeder>is generally not looked upon positively,
so.

68
00:04:35.649 --> 00:04:39.649
<v Nick Leeder>Um, when I look at these kind of cool, and
I have to do the air quotes, and I

69
00:04:39.649 --> 00:04:44.929
<v Nick Leeder>apologize for that, but cool technologies,
um, manufacturing is not always the

70
00:04:44.929 --> 00:04:46.589
<v Nick Leeder>fastest to adopt them.

71
00:04:46.959 --> 00:04:53.739
<v Nick Leeder>Um, and when they do, the applications I
see have typically been built around an

72
00:04:53.739 --> 00:04:56.269
<v Nick Leeder>engineer thinking about the engineer's
problem.

73
00:04:56.609 --> 00:04:58.010
<v Nick Leeder>So they're very complicated.

74
00:04:58.410 --> 00:05:00.649
<v Nick Leeder>Uh, and we see this in all sorts of
applications.

75
00:05:00.730 --> 00:05:03.640
<v Nick Leeder>I said, ERP is a great example of it.

76
00:05:04.130 --> 00:05:08.369
<v Nick Leeder>Sometimes MES, if you're an engineer in
computer aided design and product life cycle

77
00:05:08.369 --> 00:05:11.510
<v Nick Leeder>management solutions as well, they're
built for engineers.

78
00:05:11.929 --> 00:05:17.350
<v Nick Leeder>And that means that they, they create very
long learning curves to use them, um.

79
00:05:18.260 --> 00:05:25.040
<v Nick Leeder>And you know, many of the buyers actually
post purchasing these softwares kind of

80
00:05:25.390 --> 00:05:28.739
<v Nick Leeder>regret the software decisions because
they've, they've looked at the functionality

81
00:05:28.739 --> 00:05:32.640
<v Nick Leeder>tick box but not the usability tick boxes
hard enough.

82
00:05:32.940 --> 00:05:37.940
<v Nick Leeder>And that means that implicate the
implementations slow down, become difficult, and

83
00:05:37.940 --> 00:05:43.380
<v Nick Leeder>there becomes a usability debt that they
create within the organization cos people

84
00:05:43.380 --> 00:05:47.579
<v Nick Leeder>are actually unwilling to use the tools
because it, we make it difficult.

85
00:05:47.940 --> 00:05:49.950
<v Nick Leeder>For them to use the tools.

86
00:05:50.470 --> 00:05:56.619
<v Nick Leeder>So cool technology is great as long as the
way we interface with that cool

87
00:05:56.619 --> 00:05:58.910
<v Nick Leeder>technology is equally as great.

88
00:05:59.600 --> 00:06:05.049
<v Nick Leeder>But manufacturing is slow also to adopt
the cool technology.

89
00:06:06.619 --> 00:06:10.170
<v Speaker 3>It's, I've, I've heard that term before,
the, the software regret.

90
00:06:10.220 --> 00:06:14.209
<v Speaker 3>It might have even been in a conversation
with, was it Gartner or someone like that,

91
00:06:14.459 --> 00:06:18.089
<v Speaker 3>this term of software regret, so that's,
that's a real thing, right?

92
00:06:18.250 --> 00:06:22.299
<v Speaker 3>You know, where they purchase it for
whatever reason, and then the reality of the

93
00:06:22.299 --> 00:06:27.260
<v Speaker 3>situa, or they, they've overlooked certain
areas, which, um, which means in reality,

94
00:06:27.299 --> 00:06:29.920
<v Speaker 3>it's not quite what they thought it would
be.

95
00:06:30.429 --> 00:06:35.829
<v Nick Leeder>Yeah, well, it, it, you know, it's a great
example, um, you know, I, I, I've worked

96
00:06:35.829 --> 00:06:41.790
<v Nick Leeder>on an RFP recently for an ERP system, I, I
know, a, a full enterprise ERP system,

97
00:06:42.230 --> 00:06:47.559
<v Nick Leeder>and we are talking probably 4000
functional requirements.

98
00:06:47.670 --> 00:06:48.709
<v Nick Leeder>Can it do this?

99
00:06:48.989 --> 00:06:53.630
<v Nick Leeder>Can it do this, and less than 50
requirements on how it does it, how it interacts

100
00:06:53.630 --> 00:06:54.290
<v Nick Leeder>with people.

101
00:06:56.130 --> 00:06:58.250
<v Speaker 3>Yes, that's, that's really interesting,
Nick.

102
00:06:58.410 --> 00:07:02.119
<v Speaker 3>So you're also, yeah, so you're saying
usability is sort of at the core of the,

103
00:07:02.369 --> 00:07:05.869
<v Speaker 3>these adoption challenges at the heart,
you know, whether it's AI, whether it's IOT,

104
00:07:05.929 --> 00:07:10.329
<v Speaker 3>whether it's automation, it's, you, you
see it as overlooking the, the usability

105
00:07:10.329 --> 00:07:12.570
<v Speaker 3>element of this is core to this issue.

106
00:07:13.820 --> 00:07:20.200
<v Nick Leeder>Yeah, and and and that usability piece um
kind of is also emerging over time and

107
00:07:20.200 --> 00:07:22.600
<v Nick Leeder>different ways of interacting with the
software.

108
00:07:23.470 --> 00:07:30.369
<v Nick Leeder>Um, So I think first of all is making sure
that the software is intuitive, and now

109
00:07:30.369 --> 00:07:36.170
<v Nick Leeder>it's a very vague broad term intuitive,
and it means one thing to one person and

110
00:07:36.170 --> 00:07:37.600
<v Nick Leeder>another thing to another person.

111
00:07:38.170 --> 00:07:43.890
<v Nick Leeder>But actually we have to step back and say
what is the person trying to do with the

112
00:07:43.890 --> 00:07:44.350
<v Nick Leeder>job?

113
00:07:44.609 --> 00:07:50.089
<v Nick Leeder>Are they presented with all the
information that they can do the job effectively and

114
00:07:50.089 --> 00:07:54.049
<v Nick Leeder>in a way that they can interpret without
complex training.

115
00:07:54.410 --> 00:08:00.480
<v Nick Leeder>Uh, and knowledge And I think that's,
that's really, really important and that's

116
00:08:00.480 --> 00:08:03.470
<v Nick Leeder>where I see user interfaces and user
experience.

117
00:08:03.760 --> 00:08:09.309
<v Nick Leeder>Now I hear UI UX kind of statements fall
down massively and there's some really

118
00:08:09.309 --> 00:08:13.519
<v Nick Leeder>interesting examples where companies, by
the way, do it amazingly right, but at the

119
00:08:13.519 --> 00:08:18.239
<v Nick Leeder>same time, amaz, I've seen other examples
um where they've done it amazingly wrong

120
00:08:18.239 --> 00:08:23.359
<v Nick Leeder>as well, and I think taking that
perspective of the lens of the user rather than the

121
00:08:23.359 --> 00:08:25.399
<v Nick Leeder>engineer is really, really important.

122
00:08:26.029 --> 00:08:28.690
<v Nick Leeder>And then the second thing I, I think is.

123
00:08:29.670 --> 00:08:36.559
<v Nick Leeder>Generationally we are interacting with
computers and devices in different ways.

124
00:08:37.020 --> 00:08:42.219
<v Nick Leeder>Um, you know, if I look at me, I still
have a a laptop, a screen, a keyboard, a

125
00:08:42.219 --> 00:08:42.960
<v Nick Leeder>mouse.

126
00:08:43.619 --> 00:08:46.099
<v Nick Leeder>I actually have a telephone on my desk
with buttons.

127
00:08:46.750 --> 00:08:51.859
<v Nick Leeder>Um, not, not the circular dials that we
used to have that rotated around, but it's a

128
00:08:51.859 --> 00:08:53.390
<v Nick Leeder>voice over IP, but it's got buttons.

129
00:08:54.030 --> 00:09:00.030
<v Nick Leeder>Modern generation, you know, kind of live
in a social media environment with

130
00:09:00.030 --> 00:09:02.830
<v Nick Leeder>interactions through mobile devices, for
example.

131
00:09:03.659 --> 00:09:07.650
<v Nick Leeder>So I'm, I'm not saying this is the panacea
to the problem by the way, but what I am

132
00:09:07.650 --> 00:09:13.419
<v Nick Leeder>saying is generationally the way we
interact and process information is changing,

133
00:09:13.859 --> 00:09:19.619
<v Nick Leeder>yet we still seem to have user interfaces
which are essentially an evolution from

134
00:09:19.619 --> 00:09:20.440
<v Nick Leeder>green screens.

135
00:09:21.969 --> 00:09:25.700
<v Nick Leeder>And green screens, by the way, if you're
not of the generation, are how old

136
00:09:25.700 --> 00:09:31.340
<v Nick Leeder>mainframes used to, you've probably heard
the term mainframe, which is a pre, you

137
00:09:31.340 --> 00:09:36.859
<v Nick Leeder>know, goes after punch cards, um but
mainframes and the screens we used to have back

138
00:09:36.859 --> 00:09:42.299
<v Nick Leeder>in the 70s and 80s, uh that even that for
me is early, by the way, um, were kind of

139
00:09:42.299 --> 00:09:46.580
<v Nick Leeder>very green fluorescent, so you only have
one color, nom, no, and very poor

140
00:09:46.580 --> 00:09:49.799
<v Nick Leeder>resolution, but essentially a lot of what
we have today is.

141
00:09:50.669 --> 00:09:55.710
<v Nick Leeder>You know, an evolution of that rather than
completely rethinking about how modern

142
00:09:55.710 --> 00:10:00.369
<v Nick Leeder>generations are interacting, and that
comes back to the whole skills shortage versus

143
00:10:00.369 --> 00:10:01.590
<v Nick Leeder>usability crisis.

144
00:10:03.030 --> 00:10:06.340
<v Speaker 3>Yeah, and this, I guess the, the question
that's in my head, it might, it might seem

145
00:10:06.340 --> 00:10:09.229
<v Speaker 3>a bit of a strange question because we're
talking about how to, you know, the, the

146
00:10:09.229 --> 00:10:13.010
<v Speaker 3>skills, you know, skills shortage and
usability and people actually physically using

147
00:10:13.429 --> 00:10:14.770
<v Speaker 3>various apps.

148
00:10:15.109 --> 00:10:19.140
<v Speaker 3>But, um, one thing that's sort of come up
in various conversations I've had is

149
00:10:19.140 --> 00:10:23.030
<v Speaker 3>around this, this idea that the, the users
on the shop floor or whatever.

150
00:10:23.419 --> 00:10:26.780
<v Speaker 3>Aren't necessarily the people using the
app, but maybe they're looking more for

151
00:10:26.780 --> 00:10:31.900
<v Speaker 3>vendors like Siemens or others to sort of
manage the service for them.

152
00:10:32.020 --> 00:10:37.770
<v Speaker 3>Is that, is that something you're seeing
more and more that's, um, coming in

153
00:10:37.770 --> 00:10:38.520
<v Speaker 3>conversations you're having?

154
00:10:39.169 --> 00:10:42.260
<v Nick Leeder>I, I'm gonna try, I'll need to unpick your
question a little bit and ask you some

155
00:10:42.260 --> 00:10:48.419
<v Nick Leeder>questions on the basis of that because
what, what I see in that is from an IT or an

156
00:10:48.419 --> 00:10:54.239
<v Nick Leeder>IT perspective at times, but mainly IT
perspective, there is a, An increasing desire

157
00:10:54.239 --> 00:10:58.059
<v Nick Leeder>to outsource, particularly as we evolve to
SAS or software as a service.

158
00:10:58.940 --> 00:11:00.830
<v Nick Leeder>So outsourcing all of that support
function.

159
00:11:02.409 --> 00:11:03.869
<v Nick Leeder>But um.

160
00:11:04.840 --> 00:11:11.719
<v Nick Leeder>There are a there is a bit of a trend in
the industry of um increasing engineering

161
00:11:11.719 --> 00:11:14.359
<v Nick Leeder>capabilities beyond that of just IT.

162
00:11:15.039 --> 00:11:19.440
<v Nick Leeder>Um, in fact I've, I've been watching with
great interest in Accenture's Industry X

163
00:11:19.440 --> 00:11:24.059
<v Nick Leeder>practice as that evolves and how the
businesses they've been acquiring.

164
00:11:24.890 --> 00:11:30.479
<v Nick Leeder>But actually, I, I, I think there is to a
degree that, and I'm assuming that's where

165
00:11:30.479 --> 00:11:32.309
<v Nick Leeder>your question was going, by the way.

166
00:11:32.650 --> 00:11:34.789
<v Speaker 3>Yeah, yeah, yeah, exactly, exactly.

167
00:11:35.000 --> 00:11:38.789
<v Nick Leeder>Um, I see that to a degree, but actually
if you think about it.

168
00:11:39.539 --> 00:11:46.390
<v Nick Leeder>The core of what a business does is
design, make and sell things in

169
00:11:46.390 --> 00:11:50.140
<v Nick Leeder>manufacturing, yeah, not all industries
work on that same premise, but certainly in

170
00:11:50.140 --> 00:11:55.090
<v Nick Leeder>manufacturing you, you have to design and
that involves creating unique IP.

171
00:11:56.030 --> 00:11:58.229
<v Nick Leeder>And solving a problem nobody else solves.

172
00:11:59.289 --> 00:12:03.049
<v Nick Leeder>Then you have a manufacturing piece which
you can do that you can make that solution

173
00:12:03.049 --> 00:12:07.489
<v Nick Leeder>in the most profitable, efficient way and
fulfill the demand of your customers

174
00:12:07.489 --> 00:12:08.229
<v Nick Leeder>effectively.

175
00:12:08.530 --> 00:12:11.570
<v Nick Leeder>And then you have the ability to sell that
and actually attract those customers in

176
00:12:11.570 --> 00:12:12.330
<v Nick Leeder>the first place.

177
00:12:13.070 --> 00:12:16.659
<v Nick Leeder>Now there are elements within those
processes which are always going to be non-value

178
00:12:16.659 --> 00:12:16.950
<v Nick Leeder>add.

179
00:12:18.169 --> 00:12:22.809
<v Nick Leeder>And I think those are the ones that are
ripe for AI or outsourcing to be done.

180
00:12:24.289 --> 00:12:28.169
<v Nick Leeder>Um, you know, looking at having actually
change analysts in the business, looking

181
00:12:28.169 --> 00:12:31.809
<v Nick Leeder>about the amount of engineering change
that they're going through, that's not hugely

182
00:12:31.809 --> 00:12:32.469
<v Nick Leeder>valuable.

183
00:12:32.849 --> 00:12:38.049
<v Nick Leeder>Executing those engineering changes,
finding solutions to those problems is, and I

184
00:12:38.049 --> 00:12:42.330
<v Nick Leeder>think that is the, the to me mentally
where the cutoff between outsourcing and in

185
00:12:42.489 --> 00:12:44.739
<v Nick Leeder>and keeping things inside of the business
sits.

186
00:12:46.429 --> 00:12:49.549
<v Speaker 3>Yeah, well, it's like, I guess it's like,
like anything really, you have to

187
00:12:49.549 --> 00:12:53.309
<v Speaker 3>consider, you know, balance what's, I
mean, I could talk about myself in a marketing

188
00:12:53.309 --> 00:12:58.229
<v Speaker 3>context, you know, what to outsource and
what to keep, um, you know, directly with,

189
00:12:58.510 --> 00:13:00.229
<v Speaker 3>you know, my team as an example as well.

190
00:13:00.309 --> 00:13:03.929
<v Speaker 3>So it's a, it's sort of a, a comparison to
make there as well.

191
00:13:04.619 --> 00:13:05.479
<v Nick Leeder>Yeah, absolutely.

192
00:13:07.219 --> 00:13:11.140
<v Speaker 3>Um, but, uh, switching back, so I, that
was a little bit of a tangent off because we

193
00:13:11.140 --> 00:13:13.020
<v Speaker 3>are talking about, you, you know, we.

194
00:13:14.869 --> 00:13:17.669
<v Speaker 3>Yeah, but it was just, it was just
something on my mind as I was thinking about this

195
00:13:17.669 --> 00:13:21.989
<v Speaker 3>is, because, of course, we still, you
know, you know, ideally, you know, in an ideal

196
00:13:21.989 --> 00:13:25.489
<v Speaker 3>world, you would want people using apps on
the shop floor and upskilling themselves,

197
00:13:25.549 --> 00:13:28.349
<v Speaker 3>you know, both for their benefit, vendor's
benefit, everyone's benefit, right?

198
00:13:28.390 --> 00:13:30.270
<v Speaker 3>I think it benefits a lot of people.

199
00:13:30.510 --> 00:13:35.140
<v Speaker 3>But I guess there's a responsibility with
vendors of, of software, whoever, whoever

200
00:13:35.140 --> 00:13:35.969
<v Speaker 3>it might be to.

201
00:13:36.479 --> 00:13:41.000
<v Speaker 3>Evolve their designs to think about the
human beings, the users at the end of it, so

202
00:13:41.000 --> 00:13:46.479
<v Speaker 3>maybe you could you talk a little bit
about that and how they can make these, um,

203
00:13:46.640 --> 00:13:50.340
<v Speaker 3>you know, their softwares and platforms
more, more intuitive to these users.

204
00:13:51.280 --> 00:13:57.909
<v Nick Leeder>Um, I, I think first of all, it's putting
themselves in, uh, the

205
00:13:57.909 --> 00:14:00.840
<v Nick Leeder>shoes of the user, um.

206
00:14:01.880 --> 00:14:06.159
<v Nick Leeder>I, you know, and I, I'm gonna be slightly
pokey and assumptional in some of these

207
00:14:06.159 --> 00:14:09.840
<v Nick Leeder>statements, but I, I can be shot down and
I'm happy always to be shot down when I'm

208
00:14:09.840 --> 00:14:13.500
<v Nick Leeder>incorrect, but it'd be interesting to look
at the major software vendors in the

209
00:14:13.500 --> 00:14:17.479
<v Nick Leeder>industrial space and actually look at
their product development teams and the guys

210
00:14:17.479 --> 00:14:21.599
<v Nick Leeder>that actually build or or the people that
produce the UIs and the UX's.

211
00:14:21.960 --> 00:14:26.299
<v Nick Leeder>How much time have they actually spent
with end users on the shop floor,

212
00:14:27.039 --> 00:14:30.039
<v Nick Leeder>understanding what they're doing and how
they're using it.

213
00:14:30.549 --> 00:14:35.450
<v Nick Leeder>I'm sure they've got the data in terms of
how they use the application from afar,

214
00:14:35.989 --> 00:14:37.609
<v Nick Leeder>but there is a gap between.

215
00:14:38.609 --> 00:14:43.299
<v Nick Leeder>Kind of movement of mouse, if you want to
call it that, whilst using the application

216
00:14:43.700 --> 00:14:49.900
<v Nick Leeder>and actually fundamentally understanding
what an operator is doing and the decisions

217
00:14:49.900 --> 00:14:55.500
<v Nick Leeder>that they need to make and the time frames
they need to make those decisions in.

218
00:14:56.520 --> 00:15:02.409
<v Nick Leeder>And I think that really fundamentally
changes the game because if you can switch

219
00:15:02.840 --> 00:15:09.840
<v Nick Leeder>from theoretical design to actually almost
going back to square one and

220
00:15:09.840 --> 00:15:11.700
<v Nick Leeder>saying what is it you're trying to do?

221
00:15:12.039 --> 00:15:18.479
<v Nick Leeder>I mean I, I, a really good example is uh
often with projects we replicate the

222
00:15:18.479 --> 00:15:20.119
<v Nick Leeder>reports that exist today.

223
00:15:21.969 --> 00:15:26.599
<v Nick Leeder>What we don't do is actually go back and
say what decisions are you looking to make

224
00:15:26.599 --> 00:15:28.080
<v Nick Leeder>from these reports and when.

225
00:15:29.200 --> 00:15:33.830
<v Nick Leeder>Then you'll actually find if you switch
that question, I guess 50% of the reports

226
00:15:33.830 --> 00:15:35.219
<v Nick Leeder>that are produced aren't actually used.

227
00:15:36.000 --> 00:15:40.090
<v Nick Leeder>And the remaining 50%, only kind of 10%
are actually fit for purpose.

228
00:15:40.809 --> 00:15:45.640
<v Nick Leeder>The other 40% are probably people having
to look at that and then reinterpret the

229
00:15:45.640 --> 00:15:46.950
<v Nick Leeder>data from those reports.

230
00:15:48.210 --> 00:15:53.210
<v Nick Leeder>And user interfaces are no different, so I
think, you know, we really need to look

231
00:15:53.210 --> 00:15:57.780
<v Nick Leeder>at this critically and say what are the
decisions people are making and how do they

232
00:15:57.780 --> 00:15:58.309
<v Nick Leeder>make it.

233
00:15:58.619 --> 00:16:04.219
<v Nick Leeder>And with the advent of things like AI we
can actually use this predictive position

234
00:16:04.500 --> 00:16:11.140
<v Nick Leeder>to provide much more contextualized and
intuitive information to the user rather

235
00:16:11.140 --> 00:16:15.039
<v Nick Leeder>than having that linked behind tables and
complex screens.

236
00:16:16.119 --> 00:16:21.359
<v Speaker 3>Yeah, yeah, and that's, I don't, we've
mentioned AI already a few times, but G AI as

237
00:16:21.359 --> 00:16:23.039
<v Speaker 3>well, because I completely take that point
on board.

238
00:16:23.080 --> 00:16:27.039
<v Speaker 3>And I think, you know, as the example with
Sensai, how, and I think of it from my

239
00:16:27.039 --> 00:16:30.520
<v Speaker 3>point of view is like, I'm not, not
someone who works in industrial manufacturing

240
00:16:30.520 --> 00:16:32.359
<v Speaker 3>environment, but when I see the evolution.

241
00:16:32.664 --> 00:16:37.544
<v Speaker 3>of the app from, you know, you log in,
cases are raised, you can see graphs and, and

242
00:16:37.544 --> 00:16:41.364
<v Speaker 3>plot, you know, what's happening, what
trends are happening and, and, and why.

243
00:16:41.424 --> 00:16:46.224
<v Speaker 3>But now we've got Gen AI where it's
actually providing that contextual information.

244
00:16:46.304 --> 00:16:50.465
<v Speaker 3>Do you see, it's a long way of asking, do
you see, you know, this sort of in written

245
00:16:50.465 --> 00:16:54.145
<v Speaker 3>form and easy to understand natural
language is bridge going to help bridge this

246
00:16:54.145 --> 00:16:57.325
<v Speaker 3>gap, you know, that we're talking about
today.

247
00:16:57.705 --> 00:17:04.430
<v Nick Leeder>Yeah, potentially, because, um, I, I, I'm
a, I'm a visual learner, so you know, you,

248
00:17:04.520 --> 00:17:09.900
<v Nick Leeder>you give, you give me four kind of
extremes, one being a written report, one being,

249
00:17:10.119 --> 00:17:16.150
<v Nick Leeder>uh, a, a chart, one being simple red,
amber, green, and something where I'm able to

250
00:17:16.150 --> 00:17:16.880
<v Nick Leeder>ask a question.

251
00:17:16.959 --> 00:17:23.229
<v Nick Leeder>There's a sliding scale of capability
there and the way that I can

252
00:17:23.229 --> 00:17:24.800
<v Nick Leeder>interpret information.

253
00:17:25.550 --> 00:17:31.619
<v Nick Leeder>Um, But interestingly Gen AI unless it
produces the chart, cos visually you can see

254
00:17:31.619 --> 00:17:36.459
<v Nick Leeder>and understand chart data very, very well,
which you could probably never see in a

255
00:17:36.459 --> 00:17:36.920
<v Nick Leeder>table.

256
00:17:37.839 --> 00:17:42.520
<v Nick Leeder>So whether Gen AI gives you the answer is,
you know, how are things trending over

257
00:17:42.520 --> 00:17:42.900
<v Nick Leeder>time.

258
00:17:43.819 --> 00:17:47.459
<v Nick Leeder>Now, the, the best one is red, amber and
green and then that allows you to go deeper

259
00:17:47.459 --> 00:17:48.500
<v Nick Leeder>into the analysis.

260
00:17:49.310 --> 00:17:55.709
<v Nick Leeder>Um So the Gen AI piece is very, could be
potentially very, very powerful, but all

261
00:17:55.709 --> 00:17:59.550
<v Nick Leeder>those statements rely on a trust in data.

262
00:18:00.810 --> 00:18:04.630
<v Nick Leeder>And What we still I think have
fundamentally.

263
00:18:05.810 --> 00:18:12.689
<v Nick Leeder>Is that reports, let's face it, Excel,
yeah, we tend to trust that more than what AI

264
00:18:12.689 --> 00:18:13.530
<v Nick Leeder>is telling us.

265
00:18:14.719 --> 00:18:19.400
<v Nick Leeder>So I think fundamentally is, and you know
this is a interesting conversations I do

266
00:18:19.400 --> 00:18:24.119
<v Nick Leeder>have with manufacturers currently is
they're looking at at AI they're not looking at

267
00:18:24.119 --> 00:18:30.560
<v Nick Leeder>creating a solid data uh and
contextualized data um component before jumping into

268
00:18:30.560 --> 00:18:31.699
<v Nick Leeder>the AI question.

269
00:18:32.239 --> 00:18:36.040
<v Nick Leeder>And actually what you're gonna have is a
um the classical sewage pipe problem is

270
00:18:36.040 --> 00:18:38.050
<v Nick Leeder>depending on what you put in, you get out.

271
00:18:38.560 --> 00:18:39.599
<v Nick Leeder>So, um.

272
00:18:40.589 --> 00:18:43.569
<v Nick Leeder>I think there's huge potential.

273
00:18:44.270 --> 00:18:49.380
<v Nick Leeder>But in manufacturing I believe still we
have that data question to solve and

274
00:18:49.380 --> 00:18:54.219
<v Nick Leeder>contextualize data because sometimes the
data without that context, you know,

275
00:18:54.469 --> 00:18:58.869
<v Nick Leeder>looking at the energy usage of a motor
without actually knowing what you were

276
00:18:58.869 --> 00:19:05.079
<v Nick Leeder>producing at that time can be very false
data, yeah, vibration, yeah, using that, so

277
00:19:05.349 --> 00:19:09.430
<v Nick Leeder>that the data points and relevancy coming
together and that's where AI could be

278
00:19:09.430 --> 00:19:12.449
<v Nick Leeder>incredibly powerful, but we need to get
that contextualized.

279
00:19:14.069 --> 00:19:17.380
<v Speaker 3>Yeah, it, it's some, it's something we
often say, I mean, it's interesting you

280
00:19:17.380 --> 00:19:22.150
<v Speaker 3>mention Excel because it is amazing how,
you know, probably still amazing because

281
00:19:22.150 --> 00:19:27.030
<v Speaker 3>you can't make presumptions about, you
know, what tools or whatever people use, but

282
00:19:27.030 --> 00:19:30.209
<v Speaker 3>there is still quite a large majority
still use Excel, right?

283
00:19:30.630 --> 00:19:33.890
<v Speaker 3>And is that due to a lack of trust in, not
just AI, if we're just talking about

284
00:19:34.589 --> 00:19:39.130
<v Speaker 3>pre-AI software, you know, systems
themselves, and this is a tried and trusted way.

285
00:19:39.270 --> 00:19:43.540
<v Speaker 3>Is that sort of the mindset that's maybe
holding Back and embracing some of these

286
00:19:43.540 --> 00:19:44.439
<v Speaker 3>technologies.

287
00:19:44.939 --> 00:19:45.339
<v Speaker 3>Um,

288
00:19:45.660 --> 00:19:50.099
<v Nick Leeder>so number one is where I see Excel being
used is because there's a gap in the

289
00:19:50.099 --> 00:19:51.560
<v Nick Leeder>information they need to make decisions.

290
00:19:52.500 --> 00:19:54.329
<v Nick Leeder>So we go all the way back to what I talked
about.

291
00:19:54.579 --> 00:19:59.099
<v Nick Leeder>Do we understand the decisions people need
to make, and that's genuinely why they

292
00:19:59.099 --> 00:20:01.040
<v Nick Leeder>use people, a lot of people use Excel.

293
00:20:01.380 --> 00:20:05.890
<v Nick Leeder>It's, it's actually bizarrely, whilst
being quite a complex user interface,

294
00:20:05.969 --> 00:20:07.839
<v Nick Leeder>something we've all grown familiar with.

295
00:20:08.250 --> 00:20:12.969
<v Nick Leeder>And we all know that in every business
there are people who can just basically do

296
00:20:12.969 --> 00:20:15.160
<v Nick Leeder>mathematics in in Excel.

297
00:20:15.530 --> 00:20:20.770
<v Nick Leeder>There are slightly what we let's call them
advanced users that can use V lookups and

298
00:20:20.770 --> 00:20:21.589
<v Nick Leeder>things like that.

299
00:20:21.890 --> 00:20:24.209
<v Nick Leeder>But then you get these other people who
are amazing.

300
00:20:24.310 --> 00:20:26.989
<v Nick Leeder>They pivot table, they do pivot table
calculations.

301
00:20:27.410 --> 00:20:32.930
<v Nick Leeder>They're, and they are able to answer
questions that nothing else is answering.

302
00:20:34.030 --> 00:20:35.920
<v Nick Leeder>And they can uniquely play for it.

303
00:20:36.229 --> 00:20:41.979
<v Nick Leeder>This is the, I, I guess where Excel
probably, no pun intended, where Excel excels

304
00:20:42.680 --> 00:20:49.430
<v Nick Leeder>is, um, I, I used to work with, um, uh,
somebody, a VP of markets, um, in a

305
00:20:49.430 --> 00:20:52.280
<v Nick Leeder>company, and they used to talk about the
sniff test.

306
00:20:52.510 --> 00:20:54.339
<v Nick Leeder>Does it pass the sniff test?

307
00:20:54.880 --> 00:21:01.199
<v Nick Leeder>And with things like, um, Excel, you can
go and drill, interrogate the data so that

308
00:21:01.199 --> 00:21:03.560
<v Nick Leeder>you get a confidence, yeah.

309
00:21:04.040 --> 00:21:05.579
<v Nick Leeder>That it's passing the sniff test.

310
00:21:06.160 --> 00:21:09.819
<v Nick Leeder>So I think also that you kind of.

311
00:21:10.829 --> 00:21:14.010
<v Nick Leeder>That's I think is why it's used, it, it
can answer questions that aren't being

312
00:21:14.010 --> 00:21:17.260
<v Nick Leeder>answered, which goes all the way back to
the usability question at the beginning.

313
00:21:18.109 --> 00:21:22.959
<v Nick Leeder>But also it allows you to interrogate the
data to make sure that your confidence

314
00:21:23.280 --> 00:21:27.040
<v Nick Leeder>gets high enough, and again that, let's
call that the sniff test for want of a

315
00:21:27.040 --> 00:21:27.939
<v Nick Leeder>better description.

316
00:21:28.560 --> 00:21:32.640
<v Nick Leeder>That I think is the fundamental, another
fundamental component is trust.

317
00:21:35.189 --> 00:21:39.989
<v Speaker 3>Um, yeah, I mean, it, it, my next question
was really gonna be around, you know, how

318
00:21:39.989 --> 00:21:43.319
<v Speaker 3>do you build trust in, in, in these
systems?

319
00:21:43.550 --> 00:21:47.390
<v Speaker 3>Yeah, that, that's the, I mean, that's,
that's the key, isn't it, to all, all of

320
00:21:47.390 --> 00:21:51.229
<v Speaker 3>this we're talking about, as well as
usability, making it easy to use and intuitive

321
00:21:51.229 --> 00:21:54.229
<v Speaker 3>and all that kind of thing, but ultimately
you can find something really intuitive,

322
00:21:54.290 --> 00:21:59.250
<v Speaker 3>but if you don't believe what's there and
it's telling you the right things, then

323
00:21:59.520 --> 00:22:01.890
<v Speaker 3>again, it's not gonna do anything right in
that respect.

324
00:22:02.469 --> 00:22:04.530
<v Nick Leeder>Yeah, so I, I guess.

325
00:22:05.839 --> 00:22:11.800
<v Nick Leeder>There's an interesting scenario when you
look at kind of IT organizations, um.

326
00:22:12.510 --> 00:22:18.569
<v Nick Leeder>And A huge amount of effort is placed into
enterprise architecture.

327
00:22:19.619 --> 00:22:24.420
<v Nick Leeder>Um, and you know, that is looking at how
all the applications sit together,

328
00:22:24.540 --> 00:22:25.280
<v Nick Leeder>integrate.

329
00:22:26.719 --> 00:22:30.160
<v Nick Leeder>But then if you look at all of that level
and then drop it down to something which I

330
00:22:30.160 --> 00:22:35.119
<v Nick Leeder>call information architecture, which is
almost agnostic of the applications.

331
00:22:36.800 --> 00:22:42.119
<v Nick Leeder>There isn't probably as much effort, in
fact anywhere near as much effort, actually

332
00:22:42.119 --> 00:22:49.109
<v Nick Leeder>spent looking at what defines the product,
what defines a machine, what defines

333
00:22:49.109 --> 00:22:53.229
<v Nick Leeder>a good vibration, you know, what what sets
the parameters around those things.

334
00:22:53.560 --> 00:22:57.560
<v Nick Leeder>How does this all plumb together and
relate to each other?

335
00:22:57.760 --> 00:23:00.199
<v Nick Leeder>Again, forget about the applications.

336
00:23:01.579 --> 00:23:07.959
<v Nick Leeder>Um, and there's not much done there, and
actually that kind of that data

337
00:23:07.959 --> 00:23:12.300
<v Nick Leeder>architecture, that information
architecture, I don't like using data cos that's very

338
00:23:12.300 --> 00:23:13.699
<v Nick Leeder>technical, but information.

339
00:23:14.520 --> 00:23:16.800
<v Nick Leeder>How does that all fit together, how does
it work together?

340
00:23:17.089 --> 00:23:20.900
<v Nick Leeder>How is it plumbed, and then how does it
reside in the application, which

341
00:23:20.900 --> 00:23:22.479
<v Nick Leeder>applications own which, which fleet.

342
00:23:23.550 --> 00:23:29.099
<v Nick Leeder>I think that is the part of the problem is
that that kind of plumbing isn't thought

343
00:23:29.099 --> 00:23:31.420
<v Nick Leeder>through enough on an information level.

344
00:23:31.750 --> 00:23:35.670
<v Nick Leeder>Certainly is thought through on an
application level, but not on an information

345
00:23:35.670 --> 00:23:36.050
<v Nick Leeder>level.

346
00:23:36.589 --> 00:23:41.030
<v Nick Leeder>And that will surface also these little
islands and silos of data.

347
00:23:42.010 --> 00:23:46.650
<v Nick Leeder>You know, and manufacturing is fantastic
for this, yeah, there will be sources of

348
00:23:46.650 --> 00:23:51.089
<v Nick Leeder>record in quality, there will be sources
of record in maintenance, there will be

349
00:23:51.089 --> 00:23:53.469
<v Nick Leeder>source of um records in planning.

350
00:23:54.310 --> 00:24:00.270
<v Nick Leeder>And this all stuff isn't coming together,
you know, and you know, the panacea of AI,

351
00:24:00.280 --> 00:24:03.430
<v Nick Leeder>I, I'm quite frankly, we're decades from
that yet.

352
00:24:03.750 --> 00:24:07.109
<v Nick Leeder>So we've gotta kind of think how we pull
this stuff together properly.

353
00:24:07.829 --> 00:24:12.770
<v Speaker 3>And again, I, I put it back to a
conversation, it was a few years ago at an in, um,

354
00:24:12.969 --> 00:24:17.760
<v Speaker 3>sort of an industry 4.0 manufacturing
event when I was speaking to someone from

355
00:24:17.760 --> 00:24:22.479
<v Speaker 3>manufacturing, large global manufacturer,
and they were, at that point, they were

356
00:24:22.479 --> 00:24:24.199
<v Speaker 3>talking about, this is before I.

357
00:24:24.344 --> 00:24:29.135
<v Speaker 3>AI became the topic everywhere, but having
all these little pockets of data, but now

358
00:24:29.135 --> 00:24:30.464
<v Speaker 3>they don't know what to do with it.

359
00:24:30.505 --> 00:24:33.385
<v Speaker 3>And it's not just what to do with the
individual data, but how to bring it together

360
00:24:33.385 --> 00:24:38.505
<v Speaker 3>and get the insights for, you know, either
individually or by bringing it together,

361
00:24:38.785 --> 00:24:38.905
<v Speaker 3>right?

362
00:24:39.025 --> 00:24:43.665
<v Speaker 3>So, the, it's almost like being advised
to, you need to collect data, you need to

363
00:24:43.665 --> 00:24:47.385
<v Speaker 3>install sensors, get the data, and then
you can know everything.

364
00:24:47.584 --> 00:24:52.290
<v Speaker 3>But then, That point, at that point
anyway, I know we've moved on, we know how far

365
00:24:52.290 --> 00:24:56.959
<v Speaker 3>things have moved in a couple of 2 or 3
years, but, um, but yeah, I just thought

366
00:24:56.959 --> 00:25:00.579
<v Speaker 3>that that was an interesting, yeah, thing
what you were saying.

367
00:25:01.040 --> 00:25:05.709
<v Nick Leeder>And, and, and absolute manufacturing has
never suffered from a lack of data, yeah.

368
00:25:06.880 --> 00:25:11.709
<v Nick Leeder>Um, you can, you can analyze whatever you
want, but is it the important thing?

369
00:25:11.800 --> 00:25:13.030
<v Nick Leeder>What are the important things?

370
00:25:13.109 --> 00:25:16.030
<v Nick Leeder>Again, back to that point which I raised
around usability.

371
00:25:16.640 --> 00:25:18.880
<v Nick Leeder>What are the important decisions that need
to be made?

372
00:25:19.000 --> 00:25:21.150
<v Nick Leeder>What is the information that supports
those decisions?

373
00:25:21.560 --> 00:25:23.709
<v Nick Leeder>That's not, we don't often ask that.

374
00:25:23.949 --> 00:25:28.400
<v Nick Leeder>We'd go straight into analyzing all the
data coming off the sensors, um, which

375
00:25:28.400 --> 00:25:31.829
<v Nick Leeder>unfortunately leads to a lot, you know,
particularly when AI starts coming in, leads

376
00:25:31.829 --> 00:25:36.599
<v Nick Leeder>to a lot of false positives, which then
again destroys the whole trust basis.

377
00:25:37.109 --> 00:25:41.270
<v Nick Leeder>So I think you know stepping back and
saying what decisions do I need to make and

378
00:25:41.270 --> 00:25:47.180
<v Nick Leeder>how do I present those decisions in a way
that is so simple for everybody to

379
00:25:47.180 --> 00:25:52.430
<v Nick Leeder>interpret, whether that be on a HMI or on
a big screen or on a mobile device you're

380
00:25:52.430 --> 00:25:53.310
<v Nick Leeder>walking around with.

381
00:25:54.680 --> 00:25:58.290
<v Speaker 3>But is it, uh, if we talk about this, I
know we've probably covered siloed and

382
00:25:58.290 --> 00:26:02.010
<v Speaker 3>siloed data quite a lot in this book, on
this podcast, but I'm almost thinking it's

383
00:26:02.010 --> 00:26:06.709
<v Speaker 3>even a, an issue in, it's not just a, cos
I mean, from a sense type perspective, we

384
00:26:06.709 --> 00:26:10.869
<v Speaker 3>could look at it from a lot of different
ways, you know, a plant being siloed, you

385
00:26:10.869 --> 00:26:12.589
<v Speaker 3>know, in their own, doing their own thing.

386
00:26:12.770 --> 00:26:16.329
<v Speaker 3>But I think within a plant, there's
probably a line over there, a line over there, a

387
00:26:16.329 --> 00:26:21.010
<v Speaker 3>line, all collecting data or collecting
data in different ways, um, and not bringing

388
00:26:21.010 --> 00:26:23.369
<v Speaker 3>it together from even that perspective,
right?

389
00:26:23.739 --> 00:26:24.099
<v Speaker 3>Is what we're

390
00:26:24.099 --> 00:26:24.280
<v Nick Leeder>talking about.

391
00:26:24.329 --> 00:26:24.410
<v Speaker 3>Yeah,

392
00:26:24.420 --> 00:26:26.300
<v Nick Leeder>I mean it's like it's like a Russian doll,
isn't it?

393
00:26:26.459 --> 00:26:32.349
<v Nick Leeder>You kind of keep opening up and there's
another silo within the silo, um, and even

394
00:26:32.349 --> 00:26:36.500
<v Nick Leeder>down to the fact that an operator will
either have their own Excel sheet or some

395
00:26:36.500 --> 00:26:39.770
<v Nick Leeder>notes that they walk around with in their
pocket that tell them how the machine

396
00:26:39.770 --> 00:26:44.780
<v Nick Leeder>works, you know, it, it's that, it is that
level and it's not a unique thing to

397
00:26:44.780 --> 00:26:45.579
<v Nick Leeder>manufacturing.

398
00:26:46.310 --> 00:26:50.089
<v Nick Leeder>Um, but I just think we're particularly
good at it, um, so.

399
00:26:50.910 --> 00:26:57.750
<v Nick Leeder>You know, I, I think What, what is, I, I
guess I I what I'm trying to say here

400
00:26:57.750 --> 00:26:58.010
<v Nick Leeder>is.

401
00:26:58.839 --> 00:27:03.420
<v Nick Leeder>Maybe there's 100% of information that's
needed within a silo to make a decision.

402
00:27:04.430 --> 00:27:05.369
<v Nick Leeder>Apologies, hold on.

403
00:27:09.250 --> 00:27:14.849
<v Nick Leeder>I'll look, I'll work out how to turn that
phone off, so maybe there's 100% of data

404
00:27:14.849 --> 00:27:17.430
<v Nick Leeder>that's needed to make a decision within a
silo.

405
00:27:18.180 --> 00:27:22.489
<v Nick Leeder>But when you take that Sao or that Russian
doll up to the bigger Russian doll it

406
00:27:22.489 --> 00:27:26.160
<v Nick Leeder>sits within, maybe only 10% of that data
needs to be passed across.

407
00:27:27.010 --> 00:27:27.020
<v Nick Leeder>Hm.

408
00:27:28.010 --> 00:27:32.300
<v Nick Leeder>And then maybe only that aggregated 10%
needs to be put across.

409
00:27:32.849 --> 00:27:37.569
<v Nick Leeder>So actually rather than keep lifting up
100%, 100%, it's actually understanding

410
00:27:37.569 --> 00:27:41.569
<v Nick Leeder>what's important and maybe, you know,
it's, it's the classical example of do you

411
00:27:41.569 --> 00:27:46.569
<v Nick Leeder>pull all the data from a sensor through to
the cloud, or do you process on the edge

412
00:27:46.569 --> 00:27:48.709
<v Nick Leeder>and just pass the results across.

413
00:27:50.099 --> 00:27:54.380
<v Nick Leeder>Just think of it in that way, might change
some of the thinking in that silo and

414
00:27:54.380 --> 00:27:59.640
<v Nick Leeder>actually maybe make people more
comfortable in sharing different information across,

415
00:27:59.939 --> 00:28:04.060
<v Nick Leeder>but at the same time, as I go back to my
previous points, that information

416
00:28:04.060 --> 00:28:09.079
<v Nick Leeder>architecture needs to be designed and
needs to be understood how it flows.

417
00:28:10.709 --> 00:28:13.349
<v Speaker 3>Yeah, I like, I like we've sort of gone
down a more technical route.

418
00:28:13.510 --> 00:28:17.310
<v Speaker 3>Um, it's amazing how these conversations
sort of flow into, um, sort of different

419
00:28:17.310 --> 00:28:17.819
<v Speaker 3>areas.

420
00:28:18.410 --> 00:28:18.420
<v Speaker 3>I,

421
00:28:18.469 --> 00:28:21.310
<v Nick Leeder>I was gonna go back to institutional
education at some point.

422
00:28:23.349 --> 00:28:23.550
<v Speaker 3>Exactly.

423
00:28:23.619 --> 00:28:24.589
<v Speaker 3>It's, it's so much.

424
00:28:24.709 --> 00:28:29.589
<v Speaker 3>I mean, but I think it's, uh, in a way, it
just shows how, um, broad the topic is,

425
00:28:29.630 --> 00:28:31.979
<v Speaker 3>and it encompasses lots of different
areas, right?

426
00:28:32.030 --> 00:28:33.910
<v Speaker 3>What we're talking about today is skills
shortage.

427
00:28:33.949 --> 00:28:37.760
<v Speaker 3>It's, it, you know, you can drill it down
to the data side of things, right?

428
00:28:37.829 --> 00:28:39.310
<v Speaker 3>It's, it's all interconnected.

429
00:28:39.689 --> 00:28:40.489
<v Speaker 3>In a way it it it,

430
00:28:40.510 --> 00:28:45.719
<v Nick Leeder>it, it kind of is, it kind of is, but it's
about how, you know, ultimately, you know

431
00:28:45.719 --> 00:28:47.770
<v Nick Leeder>we kind of almost rewind all the way back.

432
00:28:48.780 --> 00:28:54.939
<v Nick Leeder>Information is information, but without
providing that to the person that needs it

433
00:28:55.180 --> 00:28:57.760
<v Nick Leeder>contextualized in a simple way, it's
useless.

434
00:28:58.500 --> 00:28:59.020
<v Nick Leeder>Yeah.

435
00:28:59.380 --> 00:29:03.699
<v Nick Leeder>There's there's, there's, there's no point
in having money in the bank if you can't

436
00:29:03.699 --> 00:29:04.880
<v Nick Leeder>access that money to spend it.

437
00:29:05.589 --> 00:29:10.930
<v Nick Leeder>And spending on the important things, and
I'm, I'm hopefully that analogy works, but

438
00:29:11.270 --> 00:29:11.689
<v Nick Leeder>um.

439
00:29:12.550 --> 00:29:15.819
<v Nick Leeder>So you know, if we think about all the
information we have is all the money we've

440
00:29:15.819 --> 00:29:20.770
<v Nick Leeder>got in the bank, you know, you need to
make it available to the people that need to

441
00:29:20.770 --> 00:29:21.839
<v Nick Leeder>make those decisions.

442
00:29:22.660 --> 00:29:26.750
<v Nick Leeder>Um, you know, and there's a time element
to this because often some decisions need

443
00:29:26.750 --> 00:29:31.630
<v Nick Leeder>to be made, um, in real time or as close
to real time cos that statement is always

444
00:29:31.630 --> 00:29:36.030
<v Nick Leeder>slightly misleading, so as close to real
time as possible in the operating

445
00:29:36.030 --> 00:29:41.560
<v Nick Leeder>environment and probably needs to be
presented in almost a boolean type way.

446
00:29:41.900 --> 00:29:46.430
<v Nick Leeder>Do this, do this, or you know, something
is, this is going wrong, so they don't have

447
00:29:46.430 --> 00:29:50.349
<v Nick Leeder>to get the data and interpret it because
the time horizon for the decisions is, is

448
00:29:50.349 --> 00:29:50.729
<v Nick Leeder>low.

449
00:29:52.270 --> 00:29:57.089
<v Nick Leeder>All the way through to monthly performance
reporting, and that data is running on a

450
00:29:57.089 --> 00:29:59.510
<v Nick Leeder>different cadence but is summarized up.

451
00:30:00.310 --> 00:30:06.130
<v Nick Leeder>So it's the way it's presented, how it's
presented, and the time frame in which

452
00:30:06.130 --> 00:30:07.689
<v Nick Leeder>those decisions need to be made.

453
00:30:08.189 --> 00:30:12.310
<v Nick Leeder>That's, that's, you know, a lot more
thinking I think needs to be done in user

454
00:30:12.310 --> 00:30:13.339
<v Nick Leeder>interfaces.

455
00:30:13.630 --> 00:30:17.989
<v Nick Leeder>And when I've seen things done really
well, that stuff's been taken, you know,

456
00:30:18.550 --> 00:30:23.829
<v Nick Leeder>several layers in, you know, it it it's
presenting that information in a very, very

457
00:30:23.829 --> 00:30:28.109
<v Nick Leeder>intuitive way, so you don't have to go
through complex training.

458
00:30:28.599 --> 00:30:31.449
<v Nick Leeder>To understand what you need to do with
that information.

459
00:30:33.099 --> 00:30:38.150
<v Nick Leeder>But secondly, I've seen a lot of companies
do wrapping gamification which drives

460
00:30:38.150 --> 00:30:43.469
<v Nick Leeder>interaction, which drives performance
around these things um and actually drives

461
00:30:43.469 --> 00:30:46.349
<v Nick Leeder>visibility of how people are using this
information.

462
00:30:47.099 --> 00:30:51.020
<v Nick Leeder>So I, you know, as I'm looking at this,
you know, the way that user interfaces

463
00:30:51.020 --> 00:30:54.280
<v Nick Leeder>evolve is there's a massive road we've
still got to go down.

464
00:30:55.719 --> 00:30:59.900
<v Speaker 3>And, you know, like you said, if they, you
know, in that ideal scenario you just

465
00:30:59.910 --> 00:31:04.719
<v Speaker 3>described, and there's a key word you
mentioned as well, um, you know, change, which

466
00:31:04.719 --> 00:31:09.079
<v Speaker 3>is ultimately what we're, you know, change
of mindset, change of process, change of

467
00:31:09.079 --> 00:31:09.900
<v Speaker 3>workflow.

468
00:31:10.040 --> 00:31:14.439
<v Speaker 3>But does that really enable, I mean, it's
only one element of it, I guess, of the

469
00:31:14.439 --> 00:31:17.420
<v Speaker 3>change required, but it's obviously a key
element, right?

470
00:31:18.689 --> 00:31:23.219
<v Nick Leeder>Yeah, I mean I, I've spoken in, in
webinars and in uh before around change and

471
00:31:23.219 --> 00:31:26.040
<v Nick Leeder>making sure that change is relevant to the
person.

472
00:31:26.579 --> 00:31:31.660
<v Nick Leeder>Um, you know, I I see change often coming
down as this is, we need to change this

473
00:31:31.660 --> 00:31:36.339
<v Nick Leeder>because it'll help us improve our
operating margin by 3%.

474
00:31:36.420 --> 00:31:38.699
<v Nick Leeder>That means nothing to nobody on the shop
floor, yeah?

475
00:31:40.050 --> 00:31:44.530
<v Nick Leeder>So when we talk about change, we make it
relevant to the person the change is being

476
00:31:44.530 --> 00:31:45.170
<v Nick Leeder>impacted in.

477
00:31:45.489 --> 00:31:51.900
<v Nick Leeder>We speak to them in their language so that
they understand how it will benefit them,

478
00:31:52.520 --> 00:31:55.069
<v Nick Leeder>which in consequently will benefit the
company.

479
00:31:55.489 --> 00:32:00.089
<v Nick Leeder>So with all these things about user
interfaces, new applications and stuff, these,

480
00:32:00.209 --> 00:32:06.530
<v Nick Leeder>if it's done right, that benefits them and
why they want to use it.

481
00:32:06.900 --> 00:32:09.839
<v Nick Leeder>Is actually that you start reducing the
barrier to that.

482
00:32:10.760 --> 00:32:15.930
<v Nick Leeder>And you start making it easier for them to
adopt what you're trying to deliver.

483
00:32:18.589 --> 00:32:19.510
<v Speaker 3>No, really good.

484
00:32:19.670 --> 00:32:22.150
<v Speaker 3>No, that, that, and that makes a lot of
sense.

485
00:32:22.329 --> 00:32:25.969
<v Speaker 3>Again, based on a lot of conversations I,
I have as well.

486
00:32:26.229 --> 00:32:28.790
<v Speaker 3>Um, again, another key phrase, removing
barriers, right?

487
00:32:28.900 --> 00:32:32.969
<v Speaker 3>That's what ultimately we're doing it what
whatever stage of that process from

488
00:32:33.290 --> 00:32:33.849
<v Speaker 3>initial.

489
00:32:34.619 --> 00:32:38.420
<v Speaker 3>Vendor selection to, you know,
implementation and hopefully success, it's so, you

490
00:32:38.420 --> 00:32:40.319
<v Speaker 3>know, you want to remove those barriers
along the way.

491
00:32:41.500 --> 00:32:45.150
<v Nick Leeder>And I think there's a fundamentalist part
of that, there's a design philosophy that

492
00:32:45.150 --> 00:32:46.030
<v Nick Leeder>needs to change.

493
00:32:46.430 --> 00:32:51.270
<v Nick Leeder>You know, currently user interfaces and
user experiences are engineer first,

494
00:32:51.349 --> 00:32:52.250
<v Nick Leeder>operator second.

495
00:32:53.260 --> 00:32:57.520
<v Nick Leeder>Even if that interface is geared at an
operator, it's been designed by an engineer.

496
00:32:58.750 --> 00:33:04.089
<v Nick Leeder>So let's switch that equation for the
interfaces, it should be led by the people

497
00:33:04.229 --> 00:33:05.319
<v Nick Leeder>needing to use that.

498
00:33:05.579 --> 00:33:11.229
<v Nick Leeder>That could result in quite complex or
sorry, not complex but quite different user

499
00:33:11.229 --> 00:33:12.130
<v Nick Leeder>experiences.

500
00:33:12.589 --> 00:33:17.910
<v Nick Leeder>So if we took an operator first
perspective on the information and the screens that

501
00:33:17.910 --> 00:33:23.229
<v Nick Leeder>the operator needs to work at, that
undoubtedly would look very different to the

502
00:33:23.229 --> 00:33:25.949
<v Nick Leeder>screen that the engineer needs to use to
do their work.

503
00:33:26.500 --> 00:33:31.390
<v Nick Leeder>Or the planner needs to do, to do their
work, or the maintenance uh manager needs to

504
00:33:31.390 --> 00:33:35.910
<v Nick Leeder>do to do their work, but it's been thought
through through the lens and um because

505
00:33:35.910 --> 00:33:40.030
<v Nick Leeder>you've sat, or the the ends of the end
user because you've sat in their shoes and

506
00:33:40.030 --> 00:33:41.069
<v Nick Leeder>understood what they did.

507
00:33:42.640 --> 00:33:46.329
<v Nick Leeder>The downside, by the way, for a software
vendor is that's probably adding cost on

508
00:33:46.329 --> 00:33:46.849
<v Nick Leeder>their side.

509
00:33:47.459 --> 00:33:51.670
<v Speaker 3>Yeah, I mean something for, for everyone
to consider there.

510
00:33:51.770 --> 00:33:52.199
<v Speaker 3>Um,

511
00:33:52.819 --> 00:33:54.170
<v Nick Leeder>that's why I'm saying it's not a panacea.

512
00:33:55.300 --> 00:33:57.380
<v Speaker 3>No, no, no, no, absolutely not, absolutely
not.

513
00:33:57.540 --> 00:34:02.540
<v Speaker 3>But, um, but yeah, I guess as we, as we
come towards the end, um, yeah, people who

514
00:34:02.540 --> 00:34:06.180
<v Speaker 3>listen regularly will know I always say
one final question, then another free pop

515
00:34:06.180 --> 00:34:06.339
<v Speaker 3>up.

516
00:34:06.459 --> 00:34:08.419
<v Speaker 3>I'm gonna try and make this a final
question.

517
00:34:08.500 --> 00:34:13.100
<v Speaker 3>It's quite, um, an, it's an interesting
one because it's sort of put you a little

518
00:34:13.100 --> 00:34:17.300
<v Speaker 3>bit on the spot and looking into the
future as we, as we like to do, um.

519
00:34:18.409 --> 00:34:21.969
<v Speaker 3>But it's how, you know, how can
manufacturers, we've talked a lot about, you know,

520
00:34:22.189 --> 00:34:25.110
<v Speaker 3>what, we've talked a lot about what
vendors can do in terms of design.

521
00:34:25.449 --> 00:34:29.409
<v Speaker 3>We've talked a little bit, you know, and
balance that with what, um, you know,

522
00:34:29.649 --> 00:34:33.610
<v Speaker 3>manufacturing leaders can do, but how can
they futureproof their workforce, you

523
00:34:33.610 --> 00:34:37.590
<v Speaker 3>know, to, you know, to enable this
technology and use it, you know, to really drive

524
00:34:37.590 --> 00:34:39.370
<v Speaker 3>success within their organizations.

525
00:34:39.649 --> 00:34:40.389
<v Speaker 3>It's a big question.

526
00:34:41.199 --> 00:34:45.739
<v Nick Leeder>It's a big, it's a big question which I'll
try ultimately to, to distill down.

527
00:34:45.840 --> 00:34:52.239
<v Nick Leeder>So first of all, make sure the voice of
the worker, the operator, the people, and

528
00:34:52.239 --> 00:34:54.989
<v Nick Leeder>I'm putting it in the operator's context,
but actually there are many, as I

529
00:34:54.989 --> 00:34:59.370
<v Nick Leeder>mentioned, many different roles here, but
make sure that they have a voice.

530
00:35:00.010 --> 00:35:03.389
<v Nick Leeder>And when you're selecting and building and
designing.

531
00:35:04.270 --> 00:35:06.760
<v Nick Leeder>How these tools are gonna work, um.

532
00:35:07.459 --> 00:35:11.010
<v Nick Leeder>And I, I guess to start with, let's start
with a practicality.

533
00:35:11.429 --> 00:35:16.500
<v Nick Leeder>Let's design not for the workforce uh for
the workforce you have today and the

534
00:35:16.500 --> 00:35:21.229
<v Nick Leeder>workforce you will have in the future and
not the workforce you used to have, which

535
00:35:21.229 --> 00:35:27.350
<v Nick Leeder>is obviously UI is kind of a little bit
historical, so, um, and you know, try and

536
00:35:27.350 --> 00:35:30.310
<v Nick Leeder>get it so that if you change things, they
can use it this quarter.

537
00:35:31.570 --> 00:35:35.620
<v Nick Leeder>Not in a year's time, so there's a rapid,
there's a speed piece where you can start

538
00:35:35.620 --> 00:35:38.149
<v Nick Leeder>making um big improvements.

539
00:35:38.939 --> 00:35:45.500
<v Nick Leeder>Um And then once you get that usability
and um you know,

540
00:35:45.800 --> 00:35:50.860
<v Nick Leeder>think about well do I need to train people
or is it that intuitive?

541
00:35:51.810 --> 00:35:58.209
<v Nick Leeder>Uh, that they get, you know, um, looking
at FFT charts and trying to put runs, run

542
00:35:58.209 --> 00:36:02.139
<v Nick Leeder>speeds in there and all that stuff, that
ain't, that ain't, that is not an intuitive

543
00:36:02.139 --> 00:36:03.850
<v Nick Leeder>world for an operator.

544
00:36:03.929 --> 00:36:08.639
<v Nick Leeder>It might be very intuitive though for a
VA, you know, vibration analyst.

545
00:36:08.729 --> 00:36:13.510
<v Nick Leeder>So, you know, again, that word intuitive
is subjective to the user that's using it.

546
00:36:13.810 --> 00:36:18.010
<v Nick Leeder>But then think about it from a learning
point of view and that.

547
00:36:18.429 --> 00:36:23.429
<v Nick Leeder>I trying to bring this full circle, if
that starts becoming intuitive and can be

548
00:36:23.429 --> 00:36:27.729
<v Nick Leeder>delivered in multiple ways, let's think of
a handheld device.

549
00:36:28.030 --> 00:36:31.629
<v Nick Leeder>I'll say mobile phones, we've got a, you
know, we've already got always got a safety

550
00:36:31.629 --> 00:36:35.669
<v Nick Leeder>component here that we've gotta consider,
you know, and I hear the word wearables a

551
00:36:35.669 --> 00:36:41.350
<v Nick Leeder>lot, by the way, um, I'm still, I'm, I,
I'm, I believe wearables can be massively

552
00:36:41.350 --> 00:36:44.949
<v Nick Leeder>impactful, but I haven't seen it in scale
and I haven't seen it in a manufacturing

553
00:36:44.949 --> 00:36:46.330
<v Nick Leeder>environment yet at scale.

554
00:36:47.169 --> 00:36:50.830
<v Nick Leeder>I I I would love to be standing corrected
and invited to go and see that stuff, but

555
00:36:51.209 --> 00:36:51.689
<v Nick Leeder>um.

556
00:36:53.050 --> 00:36:57.850
<v Nick Leeder>If you can think about how it gets
delivered and it starts to be intuitive and it

557
00:36:57.850 --> 00:37:01.649
<v Nick Leeder>starts to become, you know, gamification,
starts to engage people in a different

558
00:37:01.649 --> 00:37:02.070
<v Nick Leeder>way.

559
00:37:02.850 --> 00:37:06.810
<v Nick Leeder>Then I think we start addressing perhaps
the start of that skills crisis as well,

560
00:37:07.219 --> 00:37:10.659
<v Nick Leeder>because more people get attracted to
working in those industries, it becomes more

561
00:37:10.659 --> 00:37:11.560
<v Nick Leeder>familiar.

562
00:37:12.060 --> 00:37:16.419
<v Nick Leeder>And you shorten the time from bringing
them on board to the point they start adding

563
00:37:16.419 --> 00:37:16.979
<v Nick Leeder>value.

564
00:37:17.500 --> 00:37:21.520
<v Nick Leeder>And that is, you know, a metric which a
business will see very important.

565
00:37:21.780 --> 00:37:26.419
<v Nick Leeder>But for an individual and their morale, if
they can quickly get up to speed and add

566
00:37:26.419 --> 00:37:26.919
<v Nick Leeder>value.

567
00:37:27.479 --> 00:37:31.370
<v Nick Leeder>Um, that's actually really, really
important for them because they feel like they're

568
00:37:31.370 --> 00:37:33.110
<v Nick Leeder>doing something productive.

569
00:37:33.610 --> 00:37:37.969
<v Nick Leeder>And they may not see it, they may not
notice it, but from a psychological point of

570
00:37:37.969 --> 00:37:42.330
<v Nick Leeder>view, you're doing something without
having somebody hanging over your shoulder all

571
00:37:42.330 --> 00:37:42.850
<v Nick Leeder>the time.

572
00:37:43.250 --> 00:37:48.729
<v Nick Leeder>And that's a massively important thing to
retain the new talent you bring in as

573
00:37:48.729 --> 00:37:49.010
<v Nick Leeder>well.

574
00:37:49.850 --> 00:37:51.129
<v Speaker 3>Yeah, I sort of like that.

575
00:37:51.209 --> 00:37:55.639
<v Speaker 3>The way I positioned it in my mind, sort
of shortening the, the time to value as

576
00:37:55.639 --> 00:37:56.010
<v Speaker 3>well.

577
00:37:56.290 --> 00:37:59.919
<v Speaker 3>So maybe that's something else that, I
mean, you'd, yeah, maybe it's a question,

578
00:38:00.090 --> 00:38:00.649
<v Speaker 3>more of a question.

579
00:38:00.709 --> 00:38:04.770
<v Speaker 3>I told you there'd be a follow-up
question, but, um, yeah, the, you know, the issue,

580
00:38:04.850 --> 00:38:07.540
<v Speaker 3>you know, sometimes you look at technology
and like, oh God, it's gonna, you know,

581
00:38:07.729 --> 00:38:11.560
<v Speaker 3>I've got these other projects and like,
you know, is it gonna take a while to roll

582
00:38:11.560 --> 00:38:14.610
<v Speaker 3>out and stuff, or, you know, how long is
it gonna take before you see return on

583
00:38:14.610 --> 00:38:14.850
<v Speaker 3>investment?

584
00:38:14.919 --> 00:38:17.030
<v Speaker 3>These are the kind of questions that
sometimes go around.

585
00:38:17.709 --> 00:38:20.310
<v Speaker 3>Yeah, maybe sort of great hesitancy.

586
00:38:22.120 --> 00:38:27.000
<v Nick Leeder>Let's face it, R ROI models are written
during the project creation, uh, are

587
00:38:27.000 --> 00:38:33.520
<v Nick Leeder>theoretical, and they are incredibly,
incredibly different, difficult to prove,

588
00:38:33.629 --> 00:38:37.679
<v Nick Leeder>often financially, abso you know, and
absolutely, because there's assumptions, a lot

589
00:38:37.679 --> 00:38:41.919
<v Nick Leeder>of ROIs are avoidance of cost rather than
reduction of cost.

590
00:38:42.689 --> 00:38:46.850
<v Nick Leeder>Um, particularly in the world of
maintenance, yeah, you're, it's, it's a, it's an

591
00:38:46.850 --> 00:38:50.959
<v Nick Leeder>insurance liability you're running rather
than any, um, a policy, sorry, that you're

592
00:38:50.959 --> 00:38:54.570
<v Nick Leeder>running, not liability, but an insurance
policy you're running, um.

593
00:38:55.340 --> 00:39:00.979
<v Nick Leeder>So I, I, I, I get the ROI, but we can
measure ROI in many different ways, you know,

594
00:39:01.340 --> 00:39:05.939
<v Nick Leeder>we can measure our ROI in actually people
using the system, engaging, interacting

595
00:39:05.939 --> 00:39:11.459
<v Nick Leeder>with it, and that data becoming richer, so
the next set of data that we have is, is,

596
00:39:11.540 --> 00:39:13.199
<v Nick Leeder>is more contextualized, it's more
complete.

597
00:39:13.899 --> 00:39:15.419
<v Nick Leeder>More importantly, it's trusted.

598
00:39:17.459 --> 00:39:18.969
<v Speaker 3>And there's that word again, trust.

599
00:39:19.100 --> 00:39:23.959
<v Speaker 3>And what, um, a good, good way to end on
that very, very strong, um, statement.

600
00:39:24.300 --> 00:39:26.699
<v Speaker 3>Um, but yeah, so we've, we've covered a
lot.

601
00:39:26.780 --> 00:39:29.489
<v Speaker 3>Like I said, it's a topic that goes into
lots of different areas.

602
00:39:29.620 --> 00:39:33.250
<v Speaker 3>It's even probably creating spin-off areas
for us to dive into at a later date as

603
00:39:33.250 --> 00:39:33.979
<v Speaker 3>well, Nick.

604
00:39:34.100 --> 00:39:38.530
<v Speaker 3>But, um, but for today, thank you, um, for
your time and sharing your expertise.

605
00:39:38.899 --> 00:39:44.060
<v Speaker 3>Again, we'll share, um, the World Economic
Forum blog in the show notes.

606
00:39:44.580 --> 00:39:47.989
<v Speaker 3>Um, is there any other resources that, you
know, on this topic, I mean, if there

607
00:39:47.989 --> 00:39:52.100
<v Speaker 3>are, we can link to them as well, of
course, cause, yeah, there's, like I said, it's

608
00:39:52.100 --> 00:39:54.399
<v Speaker 3>quite a broad topic, lots to cover as
well.

609
00:39:54.469 --> 00:39:58.469
<v Nick Leeder>Um, yeah, and, and you know, it always go
to, go to my website and beyond the

610
00:39:58.469 --> 00:40:04.330
<v Nick Leeder>Buzzwords blog, there is tons of stuff for
mid-market mid-size manufacturing

611
00:40:04.419 --> 00:40:08.189
<v Nick Leeder>businesses, particularly when it comes to
things like AI and actually how do you

612
00:40:08.189 --> 00:40:11.389
<v Nick Leeder>actually start interpreting it, it, it
probably pulls on.

613
00:40:11.899 --> 00:40:15.199
<v Nick Leeder>A lot of the thread and a lot of the
points I've talked about today as well.

614
00:40:15.899 --> 00:40:16.479
<v Speaker 3>Fantastic.

615
00:40:16.739 --> 00:40:22.540
<v Speaker 3>Well, thank you again, Nick, um for your
time and thank you everyone for joining us

616
00:40:22.540 --> 00:40:25.040
<v Speaker 3>for this episode um and we'll see you on
the next one.

617
00:40:25.219 --> 00:40:26.159
<v Speaker 3>Thank you very much.

618
00:40:26.459 --> 00:40:26.820
<v Speaker 3>Thank you.

619
00:40:30.770 --> 00:40:35.729
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

620
00:40:35.729 --> 00:40:39.110
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.
