WEBVTT
Language: en-US

1
00:00:01.070 --> 00:00:02.930
<v Adam Poole>We never build anything in a bubble.

2
00:00:03.309 --> 00:00:06.949
<v Adam Poole>I think our biggest advantage is that we
build really quickly.

3
00:00:07.110 --> 00:00:10.739
<v Adam Poole>We've got, so in that software development
world you talk about agile development,

4
00:00:10.750 --> 00:00:15.670
<v Adam Poole>whereas you do things very quickly, you
respond to things that come up immediately

5
00:00:15.670 --> 00:00:18.610
<v Adam Poole>and fix things rather than planning it all
ahead of time.

6
00:00:19.959 --> 00:00:20.739
<v Adam Poole>Welcome to Eye

7
00:00:20.739 --> 00:00:22.600
<v Speaker 2>Opener, powered by Siemens.

8
00:00:22.829 --> 00:00:24.680
<v Speaker 2>And now your host, Gugan Sanga.

9
00:00:26.579 --> 00:00:29.159
<v Speaker 3>Welcome to trend detection powered by
Siemens.

10
00:00:29.500 --> 00:00:34.630
<v Speaker 3>In today's episode, we explore the
redesigned dashboard, reporting capabilities, and

11
00:00:34.630 --> 00:00:39.700
<v Speaker 3>new features such as knowledgeBuilder,
which has shaped the user interface over the

12
00:00:39.700 --> 00:00:41.000
<v Speaker 3>last 18 months.

13
00:00:41.720 --> 00:00:47.040
<v Speaker 3>On today's episode, I'm delighted to be
joined by Adam Paul, um, who is going to be

14
00:00:47.040 --> 00:00:49.020
<v Speaker 3>discussing this topic with me.

15
00:00:49.400 --> 00:00:53.060
<v Speaker 3>And if you could start off by introducing
yourself to our audience, that'd be great.

16
00:00:53.639 --> 00:00:54.439
<v Adam Poole>Yeah, I'm Adam Poole.

17
00:00:54.479 --> 00:00:56.139
<v Adam Poole>I'm product design manager at Sensai.

18
00:00:56.200 --> 00:00:58.619
<v Adam Poole>I've been here for nearly 8 years now.

19
00:00:58.880 --> 00:01:02.709
<v Adam Poole>Um, before that, I worked for 17 years in
aerospace.

20
00:01:02.919 --> 00:01:08.559
<v Adam Poole>So, it's quite a lot of experience of all
kinds of things now and um, Even in the

21
00:01:08.559 --> 00:01:12.669
<v Adam Poole>last year, I mean, things have changed in
the design world so much with all the G AI

22
00:01:12.669 --> 00:01:13.400
<v Adam Poole>stuff that's come on board.

23
00:01:13.459 --> 00:01:15.199
<v Adam Poole>So it's been an exciting time for us.

24
00:01:15.519 --> 00:01:16.160
<v Speaker 3>Amazing.

25
00:01:16.389 --> 00:01:19.580
<v Speaker 3>So thank you so much again for joining me
on today's episode.

26
00:01:19.919 --> 00:01:22.220
<v Speaker 3>And let's get straight into this topic.

27
00:01:22.360 --> 00:01:26.839
<v Speaker 3>So I know from a sense side predictive
maintenance perspective, there's been a lot

28
00:01:26.839 --> 00:01:32.160
<v Speaker 3>of changes which have been made, a lot of
advancements to the application, um.

29
00:01:32.750 --> 00:01:37.120
<v Speaker 3>And I guess the first question I have is
around the dashboard and the user

30
00:01:37.120 --> 00:01:37.949
<v Speaker 3>interface.

31
00:01:38.440 --> 00:01:39.870
<v Speaker 3>So how has that changed?

32
00:01:40.400 --> 00:01:44.080
<v Adam Poole>Well, it's, it's wouldn't be short to say
that in the last two years we've

33
00:01:44.080 --> 00:01:48.279
<v Adam Poole>completely redesigned the whole
application, like top to bottom, with the most

34
00:01:48.279 --> 00:01:51.120
<v Adam Poole>change happening in the last year,
actually, it's kind of, it's kind of crazy and

35
00:01:51.120 --> 00:01:53.419
<v Adam Poole>our pace of development is so fast.

36
00:01:53.720 --> 00:01:55.040
<v Adam Poole>Um, and a big part of that.

37
00:01:55.290 --> 00:02:00.569
<v Adam Poole>is having more users, more users across
many different industries across the whole

38
00:02:00.569 --> 00:02:03.739
<v Adam Poole>world, different nationalities, different
languages to support.

39
00:02:04.050 --> 00:02:07.669
<v Adam Poole>But there's always a common requirement
for what we call like reporting.

40
00:02:07.849 --> 00:02:11.889
<v Adam Poole>So you've got these management level
people, they want, they might use the

41
00:02:11.889 --> 00:02:16.169
<v Adam Poole>application only a few minutes a day, but
they want a quick place to see the top

42
00:02:16.169 --> 00:02:19.919
<v Adam Poole>level things that are of interest to them,
the machines that are going to break, uh,

43
00:02:19.929 --> 00:02:21.479
<v Adam Poole>imminently, that kind of stuff.

44
00:02:21.929 --> 00:02:24.009
<v Adam Poole>So we wanted to put something in front of
them.

45
00:02:24.520 --> 00:02:29.830
<v Adam Poole>So we put this new homepage, which is like
a top level dashboard, um, all of that

46
00:02:29.830 --> 00:02:33.960
<v Adam Poole>information's there for them,
customizable, um, and they can export it, schedule

47
00:02:33.960 --> 00:02:36.919
<v Adam Poole>email, all of that kind of stuff very
quickly, um.

48
00:02:37.470 --> 00:02:41.940
<v Adam Poole>And in terms of user experience, we had
elements of this within the app already, but

49
00:02:41.940 --> 00:02:43.039
<v Adam Poole>they were kind of buried.

50
00:02:43.660 --> 00:02:47.619
<v Adam Poole>And one key thing of like building a
better product is just like make it really

51
00:02:47.619 --> 00:02:48.410
<v Adam Poole>simple for people.

52
00:02:48.500 --> 00:02:51.839
<v Adam Poole>It's, it's no good having all the features
unless they're usable.

53
00:02:52.339 --> 00:02:57.339
<v Adam Poole>So if it's 3 clicks away, make it like 2
clicks away or 1 click away, make it really

54
00:02:57.339 --> 00:02:58.000
<v Adam Poole>straightforward.

55
00:02:58.380 --> 00:03:02.979
<v Adam Poole>Um, and really listen to people what, what
people want from you as well, is, is a

56
00:03:02.979 --> 00:03:03.699
<v Adam Poole>good thing to do.

57
00:03:04.100 --> 00:03:04.789
<v Speaker 3>OK, cool.

58
00:03:05.059 --> 00:03:09.389
<v Speaker 3>So you touched on um the topic of just
making it simple and making it easier.

59
00:03:09.789 --> 00:03:15.630
<v Speaker 3>So I can imagine you've taken into
account, you know, user feedback of the

60
00:03:15.630 --> 00:03:16.089
<v Speaker 3>application.

61
00:03:16.509 --> 00:03:22.289
<v Speaker 3>Um, just leading into my next question
focused around You know, can you give a bit

62
00:03:22.289 --> 00:03:25.619
<v Speaker 3>more information around what drove those
changes to be made?

63
00:03:25.820 --> 00:03:26.080
<v Speaker 3>Sure,

64
00:03:26.179 --> 00:03:28.720
<v Adam Poole>I mean, we never build anything in a
bubble.

65
00:03:29.059 --> 00:03:32.559
<v Adam Poole>I think our biggest advantage is that we
build really quickly.

66
00:03:32.860 --> 00:03:36.399
<v Adam Poole>We've got, so in that software development
world, you talk about agile development,

67
00:03:36.500 --> 00:03:39.229
<v Adam Poole>whereas You do things very quickly.

68
00:03:39.309 --> 00:03:43.309
<v Adam Poole>You respond to things that come up
immediately and fix things rather than planning

69
00:03:43.309 --> 00:03:44.410
<v Adam Poole>it all ahead of time.

70
00:03:45.190 --> 00:03:48.479
<v Adam Poole>In the old days it used to be called
Waterfall where you'd, we'll plan everything,

71
00:03:48.550 --> 00:03:51.899
<v Adam Poole>we'll design it, we'll make the whole
thing ahead of time and then we'll go and

72
00:03:51.899 --> 00:03:52.369
<v Adam Poole>build it.

73
00:03:52.669 --> 00:03:54.970
<v Adam Poole>And as soon as you do that, you'll find
you were wrong.

74
00:03:55.559 --> 00:03:57.990
<v Adam Poole>Or technology has changed with beneath
you.

75
00:03:58.059 --> 00:04:02.149
<v Adam Poole>If we'd made plans a year ago, they would
have all been wrong because this little

76
00:04:02.149 --> 00:04:04.660
<v Adam Poole>thing called Gen AI came along and changed
everything.

77
00:04:05.309 --> 00:04:07.600
<v Adam Poole>So We do it like incrementally.

78
00:04:07.779 --> 00:04:10.360
<v Adam Poole>We work in like 8 week um cycles.

79
00:04:10.660 --> 00:04:13.259
<v Adam Poole>And even within that kind of cycle, we
might change what we're doing.

80
00:04:13.460 --> 00:04:16.000
<v Adam Poole>So you can kind of pivot onto something
different.

81
00:04:16.339 --> 00:04:19.500
<v Adam Poole>Um, and a big part of that is listening to
what the users say.

82
00:04:19.640 --> 00:04:22.179
<v Adam Poole>So there's lots of mechanisms for people
to do that.

83
00:04:22.299 --> 00:04:26.459
<v Adam Poole>We have a teams on the ground who are
talking, you know, working in the factories

84
00:04:26.459 --> 00:04:31.820
<v Adam Poole>with people or going to visit them, um,
very closely and they'll be telling us

85
00:04:31.820 --> 00:04:34.220
<v Adam Poole>exactly what they like and what they don't
like.

86
00:04:34.649 --> 00:04:36.459
<v Adam Poole>And we capture every single thing.

87
00:04:36.619 --> 00:04:40.600
<v Adam Poole>So we've got like a register of like, it's
probably thousands of things now.

88
00:04:41.059 --> 00:04:46.380
<v Adam Poole>Um, every idea that comes in, we look at
and um that forms the shape of what we

89
00:04:46.380 --> 00:04:47.179
<v Adam Poole>build next.

90
00:04:48.100 --> 00:04:52.859
<v Adam Poole>And we, and also internally we have a
culture, we've always had this culture of like

91
00:04:52.859 --> 00:04:54.700
<v Adam Poole>encouraging product ideas.

92
00:04:54.779 --> 00:05:00.660
<v Adam Poole>We, we have a channel in our, um, Slack
called product ideas and anyone, anywhere

93
00:05:00.660 --> 00:05:01.760
<v Adam Poole>can put an idea in there.

94
00:05:01.989 --> 00:05:05.589
<v Adam Poole>And the first thing about doing that kind
of creative exercise is like, there are no

95
00:05:05.589 --> 00:05:06.410
<v Adam Poole>bad ideas.

96
00:05:06.670 --> 00:05:07.769
<v Adam Poole>So let's just put it down.

97
00:05:08.190 --> 00:05:12.950
<v Adam Poole>I mean, the truth is there are bad ideas,
but even within a bad idea, there's a germ

98
00:05:12.950 --> 00:05:13.739
<v Adam Poole>of a good idea.

99
00:05:14.109 --> 00:05:17.440
<v Adam Poole>So, and that you don't even know how that
might be used down the line.

100
00:05:17.790 --> 00:05:18.579
<v Adam Poole>So it's all there.

101
00:05:18.630 --> 00:05:23.589
<v Adam Poole>We read them all and we turn it into and
shape it into features that come along and

102
00:05:23.589 --> 00:05:26.709
<v Adam Poole>they might not come along for a year or
two, but they all get kind of integrated

103
00:05:26.709 --> 00:05:27.149
<v Adam Poole>somehow.

104
00:05:27.940 --> 00:05:28.609
<v Adam Poole>So we have that.

105
00:05:28.619 --> 00:05:33.040
<v Adam Poole>And also I think we're probably unusual as
a product team, we're kind of central.

106
00:05:33.709 --> 00:05:36.779
<v Adam Poole>So we, we get all the business
requirements and you get the customer requirements

107
00:05:36.779 --> 00:05:39.700
<v Adam Poole>and we do regular customer calls as well.

108
00:05:39.820 --> 00:05:44.059
<v Adam Poole>So we're talking directly to the people
who use the software every day, and having

109
00:05:44.059 --> 00:05:45.890
<v Adam Poole>an honest conversation about them.

110
00:05:46.299 --> 00:05:48.170
<v Adam Poole>And we never mind bad feedback.

111
00:05:48.500 --> 00:05:49.820
<v Adam Poole>It doesn't matter to us.

112
00:05:49.899 --> 00:05:51.660
<v Adam Poole>It's like, just tell us what you want.

113
00:05:52.339 --> 00:05:52.799
<v Adam Poole>Um.

114
00:05:53.190 --> 00:05:56.750
<v Adam Poole>And then you kind of look at the consensus
of where things are and you identify, ah,

115
00:05:56.790 --> 00:05:57.829
<v Adam Poole>we should really be doing this.

116
00:05:57.910 --> 00:06:01.950
<v Adam Poole>We're totally missing this thing here, we
need to switch over to that and make that

117
00:06:01.950 --> 00:06:02.970
<v Adam Poole>happen for people.

118
00:06:03.549 --> 00:06:07.709
<v Adam Poole>So I guess the biggest theme is about
being flexible, not being rigid in your

119
00:06:07.709 --> 00:06:08.049
<v Adam Poole>thinking.

120
00:06:08.630 --> 00:06:09.160
<v Adam Poole>Um.

121
00:06:09.839 --> 00:06:13.239
<v Adam Poole>I'm probably answering lots of different
questions here, but one key bit I think

122
00:06:13.239 --> 00:06:16.739
<v Adam Poole>it's sometimes we get people saying,
what's your 5 year roadmap?

123
00:06:17.359 --> 00:06:20.160
<v Adam Poole>And it's like, it's really hard to have a
5 year roadmap.

124
00:06:20.399 --> 00:06:23.119
<v Adam Poole>We might think in terms of like a 3 year
or a 1 year.

125
00:06:23.809 --> 00:06:27.589
<v Adam Poole>But again, you have to have that
flexibility to know that down the line something.

126
00:06:28.350 --> 00:06:31.149
<v Adam Poole>Something might, some technology might
come along that you don't know about and

127
00:06:31.149 --> 00:06:33.570
<v Adam Poole>you've got to be able to jump on that as
quickly as possible.

128
00:06:34.350 --> 00:06:36.890
<v Adam Poole>Because it could be, you know, the game
changer, basically.

129
00:06:37.000 --> 00:06:38.429
<v Speaker 3>That's what I was just going to mention.

130
00:06:38.549 --> 00:06:45.269
<v Speaker 3>So when it does come to this, we, we just
touched around, for example, generative AI

131
00:06:45.989 --> 00:06:48.220
<v Speaker 3>and this is a trend now.

132
00:06:48.429 --> 00:06:53.470
<v Speaker 3>I say it's a trend because it's part of
everyone's day to day activities, whether

133
00:06:53.470 --> 00:06:56.000
<v Speaker 3>that's work related or personal.

134
00:06:56.760 --> 00:07:01.630
<v Speaker 3>Um, so I'm just interested to know how
much of a role that played in when it came,

135
00:07:02.450 --> 00:07:06.429
<v Speaker 3>came to implementing some of these
features of

136
00:07:07.329 --> 00:07:08.369
<v Adam Poole>it, it's been huge.

137
00:07:08.450 --> 00:07:14.369
<v Adam Poole>It's been the biggest kind of
unanticipated change I, I've ever known, I'd imagine

138
00:07:14.369 --> 00:07:17.799
<v Adam Poole>in terms of revolutionary technology, you
know, it's huge.

139
00:07:18.130 --> 00:07:22.010
<v Adam Poole>Our research team, we have a like a small
research team internally who are always

140
00:07:22.010 --> 00:07:26.500
<v Adam Poole>looking at what's coming along and they
were on this very early and telling us.

141
00:07:27.010 --> 00:07:28.690
<v Adam Poole>We need to get on this, we need to get on
this.

142
00:07:29.420 --> 00:07:32.820
<v Adam Poole>So then as a product team, we'd say,
right, you go and, go and test some things, go

143
00:07:32.820 --> 00:07:33.880
<v Adam Poole>and prove it to us.

144
00:07:34.859 --> 00:07:38.899
<v Adam Poole>And then they go and prove it and make
little, little apps on the side to test

145
00:07:38.899 --> 00:07:39.220
<v Adam Poole>things out.

146
00:07:39.260 --> 00:07:43.260
<v Adam Poole>And then we start bringing those features
forward, one thing at a time.

147
00:07:43.700 --> 00:07:46.899
<v Adam Poole>And what you find is when you're on the
cutting edge of stuff like that, especially

148
00:07:46.899 --> 00:07:48.980
<v Adam Poole>in a big company, you're kind of paving
the way.

149
00:07:49.059 --> 00:07:51.640
<v Adam Poole>So you've got to jump through all the
legal hoops as well.

150
00:07:52.380 --> 00:07:55.850
<v Adam Poole>You've got to understand, anticipate how
people might be using it and do it really

151
00:07:55.850 --> 00:07:56.700
<v Adam Poole>incrementally.

152
00:07:57.049 --> 00:08:01.609
<v Adam Poole>Um, it's tempting to dive in and just do
everything, but I think we've done it the

153
00:08:01.609 --> 00:08:01.929
<v Adam Poole>right way.

154
00:08:01.970 --> 00:08:06.290
<v Adam Poole>We've done like one feature at a time and
they're slowly building it out toward this

155
00:08:06.290 --> 00:08:09.760
<v Adam Poole>kind of Where it's becoming even more
useful.

156
00:08:10.140 --> 00:08:13.359
<v Adam Poole>What we haven't done is made it the whole
product.

157
00:08:13.739 --> 00:08:18.579
<v Adam Poole>I think the mistake you could make, and
some people do is like, oh, I love chat GPT.

158
00:08:18.820 --> 00:08:20.079
<v Adam Poole>That's our product now.

159
00:08:20.940 --> 00:08:23.929
<v Adam Poole>But We've made it like a sub-feature.

160
00:08:24.049 --> 00:08:26.029
<v Adam Poole>It's just a feature of what we're already
doing.

161
00:08:26.250 --> 00:08:28.279
<v Adam Poole>It, it complements like predictive
maintenance.

162
00:08:28.329 --> 00:08:32.000
<v Adam Poole>There are things it can do, it's really
good at like analyzing data and looking for

163
00:08:32.000 --> 00:08:38.609
<v Adam Poole>patterns, analyzing what our users have
added and being able to extract useful kind

164
00:08:38.609 --> 00:08:42.359
<v Adam Poole>of human readable information out of it,
but it's not the whole product.

165
00:08:42.969 --> 00:08:46.789
<v Adam Poole>Um, one thing I always thought was like, A
prompt is not a product.

166
00:08:47.010 --> 00:08:50.770
<v Adam Poole>Like if you just see a prompt and you're
expecting people to ask you questions, it's

167
00:08:50.770 --> 00:08:52.049
<v Adam Poole>like you haven't really done any work.

168
00:08:52.130 --> 00:08:57.309
<v Adam Poole>You're just, you're kind of using Church
EBT and If chat GPT went away, you no

169
00:08:57.309 --> 00:08:58.130
<v Adam Poole>longer have a product.

170
00:08:58.469 --> 00:08:58.950
<v Adam Poole>You know what I mean?

171
00:08:59.030 --> 00:09:03.419
<v Adam Poole>Whereas if chat GPT went away for us, we'd
still have the product we established

172
00:09:03.419 --> 00:09:04.690
<v Adam Poole>over, you know, 10 years.

173
00:09:05.229 --> 00:09:11.750
<v Speaker 3>So if we look at chat GBT and Sensei as in
the application, I think it's

174
00:09:11.750 --> 00:09:17.789
<v Speaker 3>beneficial in ways where it can help to
support and track issues with machines and

175
00:09:17.789 --> 00:09:18.650
<v Speaker 3>assets.

176
00:09:19.190 --> 00:09:23.909
<v Speaker 3>Um, but as you mentioned, you know, it's
not something that we're heavily reliant

177
00:09:23.909 --> 00:09:24.349
<v Speaker 3>on.

178
00:09:24.830 --> 00:09:28.510
<v Speaker 3>Um, we can still have the sensor
application because you can still have human

179
00:09:28.510 --> 00:09:30.140
<v Speaker 3>interaction with that.

180
00:09:30.330 --> 00:09:30.549
<v Adam Poole>Yeah.

181
00:09:30.750 --> 00:09:34.109
<v Adam Poole>And we've always been based around, well,
it was always based on machine learning,

182
00:09:34.190 --> 00:09:37.020
<v Adam Poole>which was the old fashionable name for AI.

183
00:09:37.750 --> 00:09:39.969
<v Adam Poole>And then JennyI is kind of the next thing
that's come along.

184
00:09:40.239 --> 00:09:43.109
<v Adam Poole>But what it's really good at is, you know,
we, we're good at, we're good at

185
00:09:43.109 --> 00:09:44.219
<v Adam Poole>operating at scale.

186
00:09:44.710 --> 00:09:47.750
<v Adam Poole>So like you might have a small number of
users in a factory, but they're dealing

187
00:09:47.750 --> 00:09:51.500
<v Adam Poole>with so much data, like the amount of data
we deal with every day is just

188
00:09:51.500 --> 00:09:52.289
<v Adam Poole>unbelievable.

189
00:09:52.549 --> 00:09:54.960
<v Adam Poole>And you might only have a team of like 3
maintainers.

190
00:09:55.270 --> 00:09:57.989
<v Adam Poole>There's no way you could look at all of
that data manually.

191
00:09:58.479 --> 00:10:02.239
<v Adam Poole>So you've got the machine learning doing
the heavy lifting and then the general on

192
00:10:02.239 --> 00:10:06.440
<v Adam Poole>top of that analyzing all the historic
stuff and looking for patterns that we

193
00:10:06.440 --> 00:10:10.039
<v Adam Poole>previously couldn't have spotted and
saying, well, this is happening now and the

194
00:10:10.039 --> 00:10:13.059
<v Adam Poole>last time this happened, you did this and
the time before that you did this.

195
00:10:13.679 --> 00:10:19.330
<v Adam Poole>And then It's encouraging more human
input, which is what I've always wanted, is

196
00:10:19.330 --> 00:10:23.969
<v Adam Poole>because the more human feedback you get,
you know, you, because it's very good at

197
00:10:23.969 --> 00:10:28.169
<v Adam Poole>doing kind of sentiment analysis,
understanding the tone of what people add, you see

198
00:10:28.169 --> 00:10:29.950
<v Adam Poole>that coming back out of it again.

199
00:10:30.320 --> 00:10:34.739
<v Adam Poole>And once customers see that, I think you
want to add more and more.

200
00:10:35.010 --> 00:10:38.109
<v Adam Poole>And we're beginning to see it more and
more now with the um, the knowledge building

201
00:10:38.109 --> 00:10:38.630
<v Adam Poole>side of things.

202
00:10:38.929 --> 00:10:43.020
<v Adam Poole>So that's a term we've come up with is
like adding your own.

203
00:10:43.729 --> 00:10:48.099
<v Adam Poole>Knowledge and documents and files into the
system and then having them interpreted

204
00:10:48.099 --> 00:10:50.799
<v Adam Poole>by the generator to help you understand
the machines better.

205
00:10:51.140 --> 00:10:54.179
<v Adam Poole>And it's all, it's all about kind of
customize, it's like the ultimate customization

206
00:10:54.179 --> 00:10:55.080
<v Adam Poole>for them, really.

207
00:10:55.780 --> 00:10:58.059
<v Adam Poole>It's made us more of a platform, I guess,
really.

208
00:10:58.260 --> 00:11:00.159
<v Adam Poole>So all within the secure environment.

209
00:11:00.260 --> 00:11:05.080
<v Adam Poole>So we're thinking they might have
operational procedures that are common across like

210
00:11:05.080 --> 00:11:06.119
<v Adam Poole>the whole factory.

211
00:11:06.820 --> 00:11:10.789
<v Adam Poole>So in, within the app you can put those
documents in there and then it filters

212
00:11:10.789 --> 00:11:14.380
<v Adam Poole>through everything, and then when they're
looking at a particular machine, they

213
00:11:14.380 --> 00:11:18.380
<v Adam Poole>should say, how should I operate this, and
it will know that document's there and it

214
00:11:18.380 --> 00:11:20.299
<v Adam Poole>will give you a summary back from it.

215
00:11:21.159 --> 00:11:25.020
<v Adam Poole>And really importantly, it will always
like reference where it's come from, which is

216
00:11:25.020 --> 00:11:25.770
<v Adam Poole>a huge thing.

217
00:11:26.010 --> 00:11:30.909
<v Adam Poole>Um, you can see people coming reliant on a
chat GPT output without knowing.

218
00:11:31.580 --> 00:11:33.659
<v Adam Poole>It's provenance, like, where did this come
from?

219
00:11:33.780 --> 00:11:34.619
<v Adam Poole>They'll just believe it.

220
00:11:34.859 --> 00:11:39.940
<v Adam Poole>But we can't do that in an operational
world because there might be safe, you know,

221
00:11:40.010 --> 00:11:42.419
<v Adam Poole>we have to be very careful with like
safety and things like that.

222
00:11:42.500 --> 00:11:45.059
<v Adam Poole>We're not going to tell people to do
anything that might be dangerous.

223
00:11:45.140 --> 00:11:47.460
<v Adam Poole>We're incredibly careful about those
things.

224
00:11:47.820 --> 00:11:49.440
<v Adam Poole>So it'll always tell you where it's come
from.

225
00:11:50.020 --> 00:11:52.780
<v Adam Poole>So you've got the operational side, but
you've also got, you know, the individual

226
00:11:52.780 --> 00:11:56.780
<v Adam Poole>machines, this, you know, you add that
information in there rather than having to go

227
00:11:56.780 --> 00:11:58.080
<v Adam Poole>and look up the manual.

228
00:11:58.799 --> 00:12:02.719
<v Adam Poole>The manual manually, you can, you can just
ask it and it'll tell you what, what you

229
00:12:02.719 --> 00:12:03.520
<v Adam Poole>need to go and do.

230
00:12:04.000 --> 00:12:07.349
<v Adam Poole>So, and that's the real growth, I think
that's the next thing we're seeing.

231
00:12:07.429 --> 00:12:11.150
<v Adam Poole>And you're seeing these features in lots
of software now, it's becoming, these are

232
00:12:11.150 --> 00:12:13.979
<v Adam Poole>becoming kind of core feat standard
features.

233
00:12:14.640 --> 00:12:18.739
<v Adam Poole>It's not really a differentiator for some
people because it's just going to become

234
00:12:18.739 --> 00:12:19.380
<v Adam Poole>expected.

235
00:12:19.960 --> 00:12:24.840
<v Adam Poole>Even like normal day to day office users,
you're expected to be able to do these

236
00:12:24.840 --> 00:12:25.150
<v Adam Poole>things.

237
00:12:25.280 --> 00:12:27.460
<v Adam Poole>So we have to support those technologies
now.

238
00:12:27.799 --> 00:12:31.859
<v Adam Poole>Um, but then think about how it really
works for our product.

239
00:12:32.280 --> 00:12:37.080
<v Adam Poole>Um, and we've just come out with those
kind of features recently, so people will be

240
00:12:37.080 --> 00:12:38.099
<v Adam Poole>able to upload.

241
00:12:38.760 --> 00:12:43.539
<v Adam Poole>Whatever files they want and choose to add
it to the co-pilot effectively and make

242
00:12:43.539 --> 00:12:44.580
<v Adam Poole>it accessible.

243
00:12:44.880 --> 00:12:48.140
<v Adam Poole>So it's still in their power to choose
what they want to do.

244
00:12:48.460 --> 00:12:51.500
<v Adam Poole>Um, and now we're excited to see what they
actually go and do with it.

245
00:12:51.840 --> 00:12:52.799
<v Speaker 3>Yeah, exactly.

246
00:12:53.109 --> 00:12:53.609
<v Speaker 3>Well, this is it.

247
00:12:53.640 --> 00:12:59.669
<v Speaker 3>It's aligned with how, um, you know,
current trends are with AI and you, you

248
00:12:59.669 --> 00:13:03.340
<v Speaker 3>mentioned around the co-pilot, so within
Sensei and the application.

249
00:13:04.130 --> 00:13:09.859
<v Speaker 3>And it's interesting because, you know,
speaking to customers and users, they seem

250
00:13:09.859 --> 00:13:16.059
<v Speaker 3>to be more inclined by just asking, you
know, the, the co-pilot information about

251
00:13:16.059 --> 00:13:17.599
<v Speaker 3>what's going on with their assets.

252
00:13:17.979 --> 00:13:23.179
<v Speaker 3>And I think maybe 11 reason for that is
because it's so intrusive and it's so quick

253
00:13:23.179 --> 00:13:24.320
<v Speaker 3>to get a response.

254
00:13:25.099 --> 00:13:26.020
<v Speaker 3>So, yeah,

255
00:13:26.059 --> 00:13:29.960
<v Adam Poole>it's very quick and the interesting side
again is the human angle.

256
00:13:30.619 --> 00:13:35.960
<v Adam Poole>One reason we wanted to do this kind of
knowledge side of things was It's a very We

257
00:13:35.960 --> 00:13:39.960
<v Adam Poole>noticed a trend that there's aging
workforces within our customers.

258
00:13:40.080 --> 00:13:43.520
<v Adam Poole>You've got very experienced engineers kind
of aging out of the workforce, so they're

259
00:13:43.520 --> 00:13:44.200
<v Adam Poole>retiring.

260
00:13:44.919 --> 00:13:50.669
<v Adam Poole>And they've got 40, 50 years of knowledge
that we need to capture and pass on to the

261
00:13:50.669 --> 00:13:51.599
<v Adam Poole>younger generations.

262
00:13:51.719 --> 00:13:53.659
<v Adam Poole>And this is like an amazing way to do it.

263
00:13:54.919 --> 00:13:58.880
<v Adam Poole>But then the compliment to that is you've
got the younger workforce coming on board

264
00:13:58.880 --> 00:14:00.580
<v Adam Poole>who don't have that experience.

265
00:14:01.090 --> 00:14:02.940
<v Adam Poole>But they know about these technologies.

266
00:14:03.409 --> 00:14:07.969
<v Adam Poole>So they understand these new interfaces
better than the older workforces.

267
00:14:08.130 --> 00:14:12.570
<v Adam Poole>So they, they will start kind of educating
the people above them and, and how to use

268
00:14:12.570 --> 00:14:13.200
<v Adam Poole>these things.

269
00:14:13.650 --> 00:14:17.010
<v Adam Poole>So it's funny because you get that
sometimes that resistance when you put like a

270
00:14:17.010 --> 00:14:19.690
<v Adam Poole>prompt and you can ask your questions and
stuff and they're like, there's a bit of

271
00:14:19.690 --> 00:14:20.590
<v Adam Poole>grumpiness there.

272
00:14:21.750 --> 00:14:24.880
<v Adam Poole>And yet the younger people would be like,
oh yes, this is, I do this all the time,

273
00:14:24.960 --> 00:14:25.440
<v Adam Poole>it's fine.

274
00:14:25.520 --> 00:14:29.919
<v Adam Poole>And then they'll start passing that back
on and then it all starts to kind of cycle

275
00:14:29.919 --> 00:14:30.320
<v Adam Poole>around a bit.

276
00:14:30.359 --> 00:14:32.250
<v Adam Poole>And now they're asking like, can you do
video as well?

277
00:14:32.349 --> 00:14:34.820
<v Adam Poole>Can you extract transcripts from video?

278
00:14:34.919 --> 00:14:38.369
<v Adam Poole>Can you do um translation and all these
kind of things.

279
00:14:38.469 --> 00:14:40.419
<v Adam Poole>So it's amazing side of things.

280
00:14:40.469 --> 00:14:44.640
<v Adam Poole>And like that localization thing, I said,
we've got customers all over the world.

281
00:14:45.609 --> 00:14:49.909
<v Adam Poole>And we support, I think 12 languages in
the app now, which is a part you kind of

282
00:14:49.909 --> 00:14:51.000
<v Adam Poole>sometimes forget about.

283
00:14:51.659 --> 00:14:56.039
<v Adam Poole>So the way you write things it becomes
important, it needs to work in all those

284
00:14:56.299 --> 00:14:57.119
<v Adam Poole>languages.

285
00:14:57.700 --> 00:15:02.099
<v Adam Poole>And you almost get it for free with, with,
um, that chat GPT integration as well.

286
00:15:02.219 --> 00:15:06.570
<v Adam Poole>So it will automatically translate things
for you as well, which is a, it's kind of

287
00:15:06.570 --> 00:15:10.349
<v Adam Poole>a superpower, you know, it kind of Bridges
some barriers.

288
00:15:10.409 --> 00:15:13.510
<v Adam Poole>You know, we've got big multinational
companies where that can be an issue.

289
00:15:13.630 --> 00:15:15.950
<v Adam Poole>We, you know, we're still quite a small
team in some ways.

290
00:15:16.010 --> 00:15:20.349
<v Adam Poole>You can't necessarily expect to support
all those languages, but we can kind of

291
00:15:20.349 --> 00:15:21.510
<v Adam Poole>inherently do it now.

292
00:15:21.909 --> 00:15:22.150
<v Speaker 3>It's,

293
00:15:22.229 --> 00:15:24.729
<v Adam Poole>it's scaled us even more, I think.

294
00:15:25.109 --> 00:15:25.650
<v Speaker 3>Exactly.

295
00:15:25.909 --> 00:15:27.630
<v Speaker 3>I think that's a huge benefit as well.

296
00:15:27.950 --> 00:15:32.669
<v Speaker 3>If you think about, you know, all the
industries that we work in and, um, you know,

297
00:15:32.869 --> 00:15:35.330
<v Speaker 3>like Sensi is on a global scale.

298
00:15:35.809 --> 00:15:40.179
<v Speaker 3>Um, it's quite beneficial to have that
because we have to bear in mind that English

299
00:15:40.179 --> 00:15:42.419
<v Speaker 3>is not someone's first language.

300
00:15:42.820 --> 00:15:47.799
<v Speaker 3>So having that availability within the
application does make it easier because

301
00:15:47.799 --> 00:15:52.820
<v Speaker 3>you've got this, you know, flexibility,
going back to this flexibility and

302
00:15:52.820 --> 00:15:56.380
<v Speaker 3>understanding your machines and assets and
having it in different languages

303
00:15:56.380 --> 00:15:57.419
<v Speaker 3>definitely helps.

304
00:15:57.619 --> 00:16:00.489
<v Adam Poole>What's amazing is we got, you got like the
formal language which is in the

305
00:16:00.489 --> 00:16:01.309
<v Adam Poole>documents.

306
00:16:01.780 --> 00:16:05.520
<v Adam Poole>And then we've got the informal language
which is written by users.

307
00:16:06.049 --> 00:16:10.969
<v Adam Poole>And you know, that might be formal, but
sometimes you, I've seen like slang terms

308
00:16:10.969 --> 00:16:14.250
<v Adam Poole>for machines, um creep in because that's
what people use.

309
00:16:14.690 --> 00:16:19.130
<v Adam Poole>And then the uh co-pilot will use those to
learn that that's the term for that

310
00:16:19.130 --> 00:16:20.799
<v Adam Poole>machine and use it back to people.

311
00:16:21.010 --> 00:16:22.190
<v Adam Poole>And that's kind of fascinating.

312
00:16:22.929 --> 00:16:26.080
<v Adam Poole>So when users notice that they're like, oh
my God, it's using the term I use for

313
00:16:26.080 --> 00:16:26.830
<v Adam Poole>that machine.

314
00:16:27.090 --> 00:16:30.789
<v Adam Poole>And that's kind of an unanticipated like
bonus.

315
00:16:31.289 --> 00:16:37.679
<v Adam Poole>But again, it, it's all about encouraging
people to Use it as much as they can and

316
00:16:37.679 --> 00:16:39.289
<v Adam Poole>really, really get the benefits of it.

317
00:16:39.409 --> 00:16:41.690
<v Adam Poole>So they kind of make bridge that gap in
their mind.

318
00:16:41.840 --> 00:16:42.640
<v Adam Poole>They like, oh this is.

319
00:16:42.979 --> 00:16:45.099
<v Adam Poole>This is really listening to me and
understanding what we're doing.

320
00:16:45.179 --> 00:16:45.570
<v Speaker 3>Well, that's it.

321
00:16:45.609 --> 00:16:49.739
<v Speaker 3>It's just that like you've mentioned, just
listening to me, so making it more of a

322
00:16:49.739 --> 00:16:51.340
<v Speaker 3>personalized experience.

323
00:16:51.659 --> 00:16:56.520
<v Speaker 3>I feel like, you know, like I said, chat
GBT just with anything has pros and cons.

324
00:16:56.969 --> 00:17:03.919
<v Speaker 3>Um, but within this application, you know,
referring to key terms or slang terms

325
00:17:04.219 --> 00:17:06.599
<v Speaker 3>and for the co-pilot to then pick that up.

326
00:17:07.130 --> 00:17:10.609
<v Speaker 3>You kind of think to yourself, oh, hang
on, it's actually listening to what I'm

327
00:17:10.609 --> 00:17:13.250
<v Speaker 3>saying and it's recording the information
that I've shared.

328
00:17:13.449 --> 00:17:17.810
<v Adam Poole>Yeah, and historically that that's really
complicated because you might have a

329
00:17:17.810 --> 00:17:22.369
<v Adam Poole>really strict like naming conventions for
your machines, which, you know, companies

330
00:17:22.369 --> 00:17:22.520
<v Adam Poole>do.

331
00:17:22.599 --> 00:17:27.050
<v Adam Poole>So you might have like a 20 digit
alphanumerical name plus something like this and

332
00:17:27.050 --> 00:17:29.739
<v Adam Poole>plus something on the end, but we also
call it this.

333
00:17:30.689 --> 00:17:31.930
<v Adam Poole>And it'll understand all of that.

334
00:17:32.329 --> 00:17:36.979
<v Adam Poole>And, but that's the kind of institutional
knowledge that you would have otherwise

335
00:17:36.979 --> 00:17:39.930
<v Adam Poole>lost, um, from those people aging out of
the workforce.

336
00:17:39.979 --> 00:17:45.060
<v Adam Poole>But if you kind of capture it in place,
you can, you can pass it on and understand

337
00:17:45.060 --> 00:17:45.219
<v Adam Poole>it.

338
00:17:45.380 --> 00:17:51.290
<v Adam Poole>So it's just, those are unanticipated
things, I think that's the real um benefits to

339
00:17:51.290 --> 00:17:51.520
<v Adam Poole>it.

340
00:17:52.489 --> 00:17:54.859
<v Adam Poole>But a key part is like it's not going to
do everything.

341
00:17:55.060 --> 00:18:00.020
<v Adam Poole>We're just doing like feature at a time
because the one thing you see is when you

342
00:18:00.020 --> 00:18:04.979
<v Adam Poole>see like a prompt, like if you could, I
could ask it anything, but that you can also

343
00:18:04.979 --> 00:18:05.939
<v Adam Poole>be paralyzed by that.

344
00:18:05.989 --> 00:18:08.260
<v Adam Poole>Like, I don't know what, what can I ask
her?

345
00:18:08.339 --> 00:18:09.479
<v Adam Poole>I don't know what to ask it.

346
00:18:09.900 --> 00:18:13.290
<v Adam Poole>So, and if you ask it something and then
it kind of can't answer it, then you've

347
00:18:13.290 --> 00:18:13.979
<v Adam Poole>lost them.

348
00:18:14.420 --> 00:18:18.530
<v Adam Poole>So in terms of user experience, we, we've
been very careful to manage that.

349
00:18:19.380 --> 00:18:23.979
<v Adam Poole>You know, the broader chat GPT will just
answer everything obviously, but within our

350
00:18:23.979 --> 00:18:29.979
<v Adam Poole>use case in protective maintenance,
obviously we, we've turned off the less relevant

351
00:18:29.979 --> 00:18:33.439
<v Adam Poole>things, um, and made it very specific to
the tasks in front of us.

352
00:18:33.540 --> 00:18:37.540
<v Adam Poole>We don't want people going off and doing
things they shouldn't do, but also mindful

353
00:18:37.540 --> 00:18:40.160
<v Adam Poole>of the secure environment we need to
operate in.

354
00:18:41.150 --> 00:18:44.630
<v Adam Poole>But again, they need to know what, what I
can ask it and what response I can get.

355
00:18:44.910 --> 00:18:48.199
<v Adam Poole>So that's what we're kind of managing and
then eventually build out all those

356
00:18:48.199 --> 00:18:53.369
<v Adam Poole>features to a We call it an app wide
co-pilot where it will know what you were

357
00:18:53.369 --> 00:18:57.410
<v Adam Poole>looking at, it will know everything you've
done and all that kind of stuff, but

358
00:18:57.650 --> 00:18:58.469
<v Adam Poole>it'll take a little while.

359
00:18:58.609 --> 00:18:58.729
<v Adam Poole>Yeah,

360
00:18:58.849 --> 00:19:03.000
<v Speaker 3>no, of course, um, I think in terms of
like technical terms, when it does come to

361
00:19:03.000 --> 00:19:07.130
<v Speaker 3>predictive maintenance and having that
co-pilot, like I said, it's, it's great

362
00:19:07.130 --> 00:19:12.400
<v Speaker 3>because it's essentially, you know,
providing information in simplistic terms.

363
00:19:12.849 --> 00:19:18.689
<v Speaker 3>So I feel like, you know, when it does
come to this whole topic, it is not as

364
00:19:18.689 --> 00:19:19.589
<v Speaker 3>straightforward.

365
00:19:20.180 --> 00:19:26.140
<v Speaker 3>So having the ability to ask a question
and I would say, you know, no question is a

366
00:19:26.140 --> 00:19:27.180
<v Speaker 3>stupid question.

367
00:19:27.800 --> 00:19:32.359
<v Speaker 3>Um, it's good to have that so they can
understand exactly what's going on with their

368
00:19:32.359 --> 00:19:38.099
<v Speaker 3>cases and assets and why is the machine
failing, you know, to have that education.

369
00:19:38.560 --> 00:19:42.400
<v Speaker 3>And I think ultimately it comes back to
this whole, you know, sense of predictive

370
00:19:42.400 --> 00:19:47.680
<v Speaker 3>maintenance as an application is this
knowledge builder, it's education, you know,

371
00:19:47.760 --> 00:19:51.560
<v Speaker 3>it's providing the knowledge to our
customers so they can understand what's going

372
00:19:51.560 --> 00:19:51.959
<v Speaker 3>on.

373
00:19:52.540 --> 00:19:57.000
<v Speaker 3>Um, and also having that, um, human
interaction, which is part of it as well.

374
00:19:57.180 --> 00:19:59.839
<v Adam Poole>Yeah, we've always pitched it as like
decision support.

375
00:20:00.739 --> 00:20:05.099
<v Adam Poole>So, you know, people worry about AI or
whatever taking over, but at the end of the

376
00:20:05.099 --> 00:20:07.479
<v Adam Poole>day, someone's going to go and manually
fix the machine.

377
00:20:07.729 --> 00:20:10.619
<v Adam Poole>They're going to change a gearbox, they're
going to swap this machine, this bit for

378
00:20:10.619 --> 00:20:12.140
<v Adam Poole>this bit, they're going to swap the oil.

379
00:20:12.540 --> 00:20:14.699
<v Adam Poole>Those manual tasks aren't going anywhere.

380
00:20:15.380 --> 00:20:19.339
<v Adam Poole>So the best we can do is guide them to do
that quickly and effectively and in the

381
00:20:19.339 --> 00:20:20.729
<v Adam Poole>right place at the right time.

382
00:20:21.280 --> 00:20:27.569
<v Adam Poole>Um, and this works well for that, so you
have to kind of Um, the decision remains

383
00:20:27.569 --> 00:20:28.430
<v Adam Poole>with the human.

384
00:20:29.010 --> 00:20:32.650
<v Adam Poole>Um, hopefully that, we want that to remain
for a long time, especially for us, but

385
00:20:32.650 --> 00:20:37.369
<v Adam Poole>in broader uses of, of that kind of
technology, I think that needs to stay in place

386
00:20:37.369 --> 00:20:38.150
<v Adam Poole>for a long time.

387
00:20:38.449 --> 00:20:42.349
<v Adam Poole>It's complimentary and then you decide
what to do with that information.

388
00:20:42.410 --> 00:20:47.050
<v Adam Poole>Um, and obviously that will all get better
over time, but that's the core thing that

389
00:20:47.050 --> 00:20:47.890
<v Adam Poole>people need to do.

390
00:20:48.130 --> 00:20:52.439
<v Adam Poole>And we always think about, you know, the
guys on the shop floor doing the jobs, um,

391
00:20:53.199 --> 00:20:54.839
<v Adam Poole>Limited numbers of people to do things.

392
00:20:54.920 --> 00:20:56.790
<v Adam Poole>You want to not waste their time in the
day.

393
00:20:57.020 --> 00:20:59.520
<v Adam Poole>We're always talking about, like, let's
just not waste their time.

394
00:21:00.000 --> 00:21:03.160
<v Adam Poole>So they might have half an hour in the
morning to use the application and then

395
00:21:03.160 --> 00:21:04.780
<v Adam Poole>they're done, but they know what they're
doing.

396
00:21:05.599 --> 00:21:07.800
<v Adam Poole>And we're not trying to make them use the
app more.

397
00:21:08.140 --> 00:21:12.540
<v Adam Poole>We're just trying to use that half an hour
window the most effectively they can.

398
00:21:12.880 --> 00:21:15.099
<v Adam Poole>If they get the most out of it, then,
then, then we're kind of winning.

399
00:21:15.280 --> 00:21:15.619
<v Adam Poole>So.

400
00:21:16.040 --> 00:21:17.390
<v Adam Poole>That's how we think about it.

401
00:21:17.800 --> 00:21:18.099
<v Adam Poole>Yeah,

402
00:21:18.439 --> 00:21:18.709
<v Speaker 3>exactly.

403
00:21:18.760 --> 00:21:21.380
<v Speaker 3>And you know, improving efficiency
essentially.

404
00:21:21.959 --> 00:21:25.640
<v Speaker 3>Um, you know, time is valuable, so we want
to make sure that they're utilizing the

405
00:21:25.640 --> 00:21:26.619
<v Speaker 3>time correctly.

406
00:21:26.920 --> 00:21:31.979
<v Speaker 3>And like you said, they can check on the
application, see what's going on, um,

407
00:21:32.040 --> 00:21:35.359
<v Speaker 3>understand the issues and, you know, get
on with the day.

408
00:21:35.900 --> 00:21:38.849
<v Adam Poole>And it's kind of funny, I was trying to
think about it like, because we have one

409
00:21:38.849 --> 00:21:43.180
<v Adam Poole>product and it's like people are like, is
it quite tricky working on one product all

410
00:21:43.180 --> 00:21:43.540
<v Adam Poole>the time?

411
00:21:43.550 --> 00:21:47.140
<v Adam Poole>And it can be sometimes because you think,
gosh, are we just going to make this one

412
00:21:47.140 --> 00:21:47.890
<v Adam Poole>thing forever.

413
00:21:48.150 --> 00:21:51.859
<v Adam Poole>But then you look back from where we came
from and it's a com it's a completely

414
00:21:51.859 --> 00:21:52.520
<v Adam Poole>different thing.

415
00:21:53.060 --> 00:21:58.119
<v Adam Poole>And because we're constantly iterating on
it, it's constantly evolving.

416
00:21:59.160 --> 00:22:01.000
<v Adam Poole>It's like a Porsche 911, I think.

417
00:22:01.130 --> 00:22:07.010
<v Adam Poole>It's like you could buy a Porsche 911 from
like the 60s and you can buy one now, but

418
00:22:07.010 --> 00:22:08.130
<v Adam Poole>you know, they're a very different thing.

419
00:22:08.250 --> 00:22:11.569
<v Adam Poole>But the core, the core thing still remains
and the core experience is still the

420
00:22:11.569 --> 00:22:14.290
<v Adam Poole>same, but they've built out so much on top
of it.

421
00:22:15.770 --> 00:22:19.099
<v Speaker 3>I think it's just that roadmap to um
efficiency.

422
00:22:19.569 --> 00:22:20.709
<v Speaker 3>You know, still the same product.

423
00:22:20.969 --> 00:22:24.250
<v Speaker 3>We're essentially making it easier, making
it more simpler.

424
00:22:24.369 --> 00:22:24.439
<v Speaker 3>Yeah,

425
00:22:24.489 --> 00:22:28.189
<v Adam Poole>efficiently and you know, some big
emphasis in terms of things we're working on now

426
00:22:28.189 --> 00:22:33.229
<v Adam Poole>and in the near future is um helping
people to scale.

427
00:22:34.079 --> 00:22:37.849
<v Adam Poole>Um, or giving them an easier way into the
app as well.

428
00:22:37.969 --> 00:22:41.890
<v Adam Poole>Maybe they don't even have data that maybe
they don't even have sensors yet.

429
00:22:42.189 --> 00:22:45.890
<v Adam Poole>It's like how can they get value out of
the app, which is where the knowledge side

430
00:22:45.890 --> 00:22:46.530
<v Adam Poole>of things works.

431
00:22:46.569 --> 00:22:49.810
<v Adam Poole>It's like, you might not have got to the
point where you've got a predictive

432
00:22:49.810 --> 00:22:51.810
<v Adam Poole>maintenance strategy in your factory.

433
00:22:52.680 --> 00:22:55.520
<v Adam Poole>But you're considering it, it's planned,
but it's not quite yet.

434
00:22:55.599 --> 00:23:00.650
<v Adam Poole>But you could still use the app, you can
still add your documents and start fleshing

435
00:23:00.650 --> 00:23:04.150
<v Adam Poole>out what it can look like for you and
still get some output from it.

436
00:23:04.650 --> 00:23:07.390
<v Adam Poole>You might not have even had those
documents in one place before.

437
00:23:07.890 --> 00:23:09.689
<v Adam Poole>You know, we know how companies work.

438
00:23:09.770 --> 00:23:12.420
<v Adam Poole>You might have some on OneDrive over here,
you might have them here.

439
00:23:12.530 --> 00:23:14.020
<v Adam Poole>Someone's kept stuff on their hard drive.

440
00:23:14.089 --> 00:23:18.290
<v Adam Poole>Just giving people one place for things
is, is an amazing thing.

441
00:23:19.109 --> 00:23:23.310
<v Adam Poole>When we first started, uh companies were
saying, I've never seen my data in one

442
00:23:23.310 --> 00:23:23.849
<v Adam Poole>place.

443
00:23:24.270 --> 00:23:26.180
<v Adam Poole>So just that alone is a huge thing.

444
00:23:26.589 --> 00:23:28.949
<v Adam Poole>I've, we've never looked at these charts
like this before.

445
00:23:29.030 --> 00:23:33.339
<v Adam Poole>We've never had all of these people in the
same place, looking at the same things at

446
00:23:33.339 --> 00:23:34.130
<v Adam Poole>the same time.

447
00:23:34.790 --> 00:23:38.630
<v Adam Poole>Um, regardless of what the software is
doing on top of that, it's like just having

448
00:23:38.630 --> 00:23:42.729
<v Adam Poole>the data and the documents there is like
a, a huge thing.

449
00:23:43.150 --> 00:23:46.069
<v Adam Poole>So we're looking at these different angles
for people to kind of get into it.

450
00:23:47.199 --> 00:23:50.099
<v Speaker 3>I think having it all in one place is
definitely the way forward.

451
00:23:50.579 --> 00:23:57.160
<v Speaker 3>Um, if we think from a perspective of us
as, you know, day to day individuals,

452
00:23:57.520 --> 00:24:02.079
<v Speaker 3>we use our smartphones and we've got
various different applications for different

453
00:24:02.079 --> 00:24:02.650
<v Speaker 3>purposes.

454
00:24:02.739 --> 00:24:07.880
<v Speaker 3>You've got one for banking, um, one for
shopping, you know, supermarkets.

455
00:24:08.319 --> 00:24:12.260
<v Speaker 3>So in the same, it's the same analogy for
the Sensite application.

456
00:24:13.030 --> 00:24:17.430
<v Speaker 3>Having that app on your phone to check
what's going on and having it all in one

457
00:24:17.430 --> 00:24:19.369
<v Speaker 3>place makes it so much easier.

458
00:24:19.829 --> 00:24:25.619
<v Speaker 3>Um, you know, from a user perspective,
people don't want to look in different

459
00:24:25.619 --> 00:24:25.949
<v Speaker 3>locations.

460
00:24:26.229 --> 00:24:30.030
<v Speaker 3>I need to open that and then I need to
open this and having it in one place just

461
00:24:30.030 --> 00:24:30.810
<v Speaker 3>helps.

462
00:24:31.300 --> 00:24:35.359
<v Adam Poole>Yeah, and the one thing that compliments
that is we find a lot of people are still

463
00:24:35.630 --> 00:24:38.349
<v Adam Poole>have a very email first workflow.

464
00:24:39.030 --> 00:24:42.750
<v Adam Poole>Probably because it's the one thing that's
constant for them, whatever they're

465
00:24:42.750 --> 00:24:47.109
<v Adam Poole>doing, regardless of the software that
comes and goes, they've always got reliable

466
00:24:47.109 --> 00:24:47.510
<v Adam Poole>email.

467
00:24:48.150 --> 00:24:52.349
<v Adam Poole>So when we going back to where we're
talking about that new homepage thing, you

468
00:24:52.349 --> 00:24:55.969
<v Adam Poole>know, building in kind of email reporting
is still a huge part of that as well.

469
00:24:56.109 --> 00:25:00.150
<v Adam Poole>So making it easy for people to configure
things the way they want and get emails

470
00:25:00.150 --> 00:25:03.770
<v Adam Poole>about it, probably every day or weekly,
whatever they want.

471
00:25:04.430 --> 00:25:07.430
<v Adam Poole>And then that gives you a different kind
of way into the app, because the first

472
00:25:07.430 --> 00:25:09.989
<v Adam Poole>thing in the morning they might do is just
open their email.

473
00:25:10.349 --> 00:25:13.790
<v Adam Poole>They might not want to jump into the full
application, and yet it's still giving

474
00:25:13.790 --> 00:25:15.089
<v Adam Poole>them some value.

475
00:25:15.550 --> 00:25:19.709
<v Adam Poole>Um, so we're always asked about email
stuff and we do support that as much as we

476
00:25:19.709 --> 00:25:23.329
<v Adam Poole>can, we're trying to standardize that and
make it a kind of a, a broader experience.

477
00:25:24.069 --> 00:25:24.609
<v Adam Poole>Um.

478
00:25:25.150 --> 00:25:29.150
<v Adam Poole>You just got to understand how people do
stuff in the real world, you know, like,

479
00:25:29.189 --> 00:25:30.969
<v Adam Poole>well you, you can just open the app and do
this.

480
00:25:30.989 --> 00:25:32.229
<v Adam Poole>And they're like, no, I'm in the email.

481
00:25:32.349 --> 00:25:34.310
<v Adam Poole>So please can you help me with this thing?

482
00:25:34.589 --> 00:25:34.930
<v Adam Poole>Yeah,

483
00:25:35.229 --> 00:25:37.619
<v Speaker 3>I think it's just that it's, it's just a
natural way, isn't it?

484
00:25:37.709 --> 00:25:41.709
<v Speaker 3>In terms of emails, everyone seems to wake
up in the morning, first thing you do,

485
00:25:42.060 --> 00:25:45.770
<v Speaker 3>you might have a coffee, sit down in front
of your laptop and what, what do we do?

486
00:25:46.150 --> 00:25:47.750
<v Speaker 3>You know, check our emails first.

487
00:25:47.949 --> 00:25:54.550
<v Speaker 3>So it's nice that we have that reporting
available within um the application.

488
00:25:55.000 --> 00:25:59.739
<v Speaker 3>And this takes me on to my next question
around reporting capabilities.

489
00:26:00.319 --> 00:26:05.239
<v Speaker 3>Um, so it'd be really great for you just
to, to find what that is for our audience

490
00:26:05.239 --> 00:26:07.040
<v Speaker 3>who don't know too much about that.

491
00:26:07.239 --> 00:26:10.780
<v Speaker 3>But you know, um, advancements which have
been made to that.

492
00:26:11.319 --> 00:26:16.560
<v Adam Poole>Yeah, reporting where people have some
like top level KPIs they're interested in.

493
00:26:16.599 --> 00:26:20.439
<v Adam Poole>They want to know, so within our world,
they might want to know if they've just got

494
00:26:20.439 --> 00:26:24.079
<v Adam Poole>started on a project, like how many assets
are in the application.

495
00:26:24.599 --> 00:26:26.219
<v Adam Poole>How many sensors are there?

496
00:26:26.760 --> 00:26:28.219
<v Adam Poole>Are they all sending data?

497
00:26:28.439 --> 00:26:29.920
<v Adam Poole>How much data are they sending?

498
00:26:30.030 --> 00:26:31.349
<v Adam Poole>How many issues have we got?

499
00:26:31.560 --> 00:26:33.459
<v Adam Poole>How is this trending over the last few
months?

500
00:26:33.550 --> 00:26:35.219
<v Adam Poole>Are we responding to things?

501
00:26:35.719 --> 00:26:40.560
<v Adam Poole>You know, it's about 8 things and they
want to say each of them in a nice chart, um,

502
00:26:40.880 --> 00:26:42.780
<v Adam Poole>and be able to look at that maybe every
day.

503
00:26:43.810 --> 00:26:47.130
<v Adam Poole>Visually, so they want to do things
visually, but they also want to export all the

504
00:26:47.130 --> 00:26:51.229
<v Adam Poole>data and put it into other bits of
software and do other analysis on it.

505
00:26:51.689 --> 00:26:53.209
<v Adam Poole>So those are the core things.

506
00:26:53.609 --> 00:26:57.729
<v Adam Poole>And they might have even built their own
little side bits of um dashboarding

507
00:26:57.729 --> 00:26:58.239
<v Adam Poole>software.

508
00:26:58.569 --> 00:27:01.670
<v Adam Poole>So something like Power BI we do this
ourselves as well.

509
00:27:02.010 --> 00:27:05.380
<v Adam Poole>So Power BI, which A raft of things to
look at.

510
00:27:05.859 --> 00:27:09.739
<v Adam Poole>And that the goal for us now is to bring
all of those, understand which of those

511
00:27:09.739 --> 00:27:12.880
<v Adam Poole>things are important for everyone and
bring them into the application itself.

512
00:27:13.609 --> 00:27:15.439
<v Adam Poole>And then you can choose to put them in
front of you.

513
00:27:15.939 --> 00:27:21.819
<v Adam Poole>So it's being able to track trends over
time, uh, in how the project is going, how

514
00:27:21.819 --> 00:27:26.260
<v Adam Poole>the machines are going, and importantly,
the human angle is like how their teams are

515
00:27:26.260 --> 00:27:27.099
<v Adam Poole>working as well.

516
00:27:27.219 --> 00:27:29.020
<v Adam Poole>Like, are they using this app?

517
00:27:29.060 --> 00:27:30.640
<v Adam Poole>Is this app worth our money?

518
00:27:30.979 --> 00:27:33.750
<v Adam Poole>Are we getting enough um return on our
investment?

519
00:27:33.890 --> 00:27:35.390
<v Adam Poole>What's the benefits we're getting?

520
00:27:35.839 --> 00:27:40.199
<v Adam Poole>Um, they don't want long reports on it,
they just want a single page, all these

521
00:27:40.199 --> 00:27:45.050
<v Adam Poole>charts on it, and they can export the data
or they can configugure emails about

522
00:27:45.050 --> 00:27:45.390
<v Adam Poole>them.

523
00:27:45.969 --> 00:27:48.109
<v Adam Poole>So it's that kind of thing, that kind of
managerial level.

524
00:27:49.109 --> 00:27:52.910
<v Adam Poole>Just keeping an eye on things, but doing
it in a quite low maintenance way.

525
00:27:53.510 --> 00:27:56.209
<v Adam Poole>Um, and that's something we'll keep
building out basically by listening to people.

526
00:27:56.219 --> 00:27:56.229
<v Adam Poole>Yeah,

527
00:27:58.150 --> 00:28:01.510
<v Speaker 3>I was gonna say I think maybe the best way
to describe it, it's essentially an

528
00:28:01.510 --> 00:28:03.650
<v Speaker 3>overview of what's going on.

529
00:28:04.189 --> 00:28:07.459
<v Speaker 3>Um, and you mentioned around Power BI.

530
00:28:07.839 --> 00:28:11.359
<v Speaker 3>Is that something which is a plug-in to
the application?

531
00:28:11.459 --> 00:28:14.959
<v Adam Poole>No, it's a separate part of software, but
it highlights why we need this kind of

532
00:28:14.959 --> 00:28:15.660
<v Adam Poole>stuff in there.

533
00:28:16.239 --> 00:28:17.420
<v Adam Poole>You know, the licenses are expensive.

534
00:28:17.709 --> 00:28:21.540
<v Adam Poole>If we've got reports in Power BI, it's not
that easy to share them with other people

535
00:28:22.319 --> 00:28:23.199
<v Adam Poole>and vice versa.

536
00:28:23.280 --> 00:28:25.300
<v Adam Poole>They might be using platforms that don't
integrate.

537
00:28:26.329 --> 00:28:28.449
<v Adam Poole>But it's about identifying what the need
is.

538
00:28:28.670 --> 00:28:31.099
<v Adam Poole>It's like, I want to see this KPI.

539
00:28:31.109 --> 00:28:32.670
<v Adam Poole>I want to see it tracked over time.

540
00:28:33.089 --> 00:28:33.969
<v Adam Poole>And it's like, well, we can do that.

541
00:28:34.130 --> 00:28:37.719
<v Adam Poole>We've got all that information in the app,
so we will build that in.

542
00:28:38.209 --> 00:28:41.729
<v Adam Poole>So this new dashboard we've got, that's
what we're actively asking people now is

543
00:28:41.729 --> 00:28:43.130
<v Adam Poole>like, what kind of things do you want to
see?

544
00:28:43.140 --> 00:28:46.369
<v Adam Poole>And we'll go and make that, and then you
can choose to arrange, you know, it's fully

545
00:28:46.369 --> 00:28:47.390
<v Adam Poole>customizable.

546
00:28:47.810 --> 00:28:50.069
<v Adam Poole>You'll be able to put that on there and
see it.

547
00:28:50.170 --> 00:28:52.109
<v Adam Poole>And then you don't need this other bit of
software anymore.

548
00:28:52.810 --> 00:28:53.260
<v Adam Poole>Um.

549
00:28:53.930 --> 00:28:55.369
<v Adam Poole>So that's, that's the goal really.

550
00:28:55.489 --> 00:28:58.510
<v Adam Poole>User need is always the thing from my
perspective.

551
00:28:58.770 --> 00:29:02.770
<v Speaker 3>And in terms of um the data that we've got
on those reporting capabilities, so this

552
00:29:02.770 --> 00:29:06.349
<v Speaker 3>dashboard, um, is that data real time
data?

553
00:29:07.050 --> 00:29:07.800
<v Speaker 3>Um,

554
00:29:08.130 --> 00:29:12.719
<v Adam Poole>yeah, I mean we get data from, gosh, the
data is constant from, from all these

555
00:29:12.719 --> 00:29:18.530
<v Adam Poole>sensors that's coming in, you know, over
different time periods, but it's very Very

556
00:29:18.530 --> 00:29:24.089
<v Adam Poole>fast, basically, and then that enables us
to also look backwards and give you these,

557
00:29:24.369 --> 00:29:28.030
<v Adam Poole>the trend view over the last 12 months,
like our default view for things is like the

558
00:29:28.030 --> 00:29:31.560
<v Adam Poole>last 12 months, so you can see what's
going on, how much work's been done, all that

559
00:29:31.560 --> 00:29:34.069
<v Adam Poole>kind of thing, what kind of cost savings.

560
00:29:34.890 --> 00:29:36.420
<v Adam Poole>But it's a constant stream.

561
00:29:36.550 --> 00:29:39.650
<v Adam Poole>It's like 24/7 data basically.

562
00:29:40.229 --> 00:29:41.489
<v Speaker 3>Data's getting pumped through.

563
00:29:42.709 --> 00:29:49.609
<v Speaker 3>Um, and do you find any trends when it
does come, come to um users reviewing the,

564
00:29:49.949 --> 00:29:51.530
<v Speaker 3>you know, dashboards?

565
00:29:51.829 --> 00:29:57.390
<v Speaker 3>Um, I guess my question is more around how
frequently because if they've got access

566
00:29:57.390 --> 00:30:01.280
<v Speaker 3>to the application, then they can
essentially check that everyday.

567
00:30:01.880 --> 00:30:06.979
<v Speaker 3>Um, but do you, uh, you know, from your
perspective, are there checkpoints that you

568
00:30:06.979 --> 00:30:10.900
<v Speaker 3>have with customers who would maybe want
to have a look every quarter?

569
00:30:12.040 --> 00:30:16.670
<v Adam Poole>No, people use it constantly, I'd say you
have more of the management level people

570
00:30:16.670 --> 00:30:17.979
<v Adam Poole>and maybe use it kind of weekly.

571
00:30:18.719 --> 00:30:22.290
<v Adam Poole>But there's people using it every, every
day because they need to go and plan the

572
00:30:22.290 --> 00:30:23.550
<v Adam Poole>work they need to do today.

573
00:30:24.310 --> 00:30:26.969
<v Adam Poole>Um, so they're like the, the guys on the
ground.

574
00:30:27.530 --> 00:30:30.290
<v Adam Poole>Then you've got the management level and
maybe there's a level above that as well

575
00:30:30.290 --> 00:30:34.930
<v Adam Poole>who are, are looking at the longer term
trends, um, or interested in how their team

576
00:30:34.930 --> 00:30:39.050
<v Adam Poole>are using things, um, how much time
they're spending doing stuff and then kind of

577
00:30:39.050 --> 00:30:40.069
<v Adam Poole>balancing all that out.

578
00:30:40.290 --> 00:30:40.449
<v Adam Poole>Yeah,

579
00:30:41.130 --> 00:30:43.589
<v Speaker 3>I was going to say more focused around
long term trends.

580
00:30:43.989 --> 00:30:49.469
<v Speaker 3>And also, like I said, this topic probably
said it so many times, um, on this

581
00:30:49.469 --> 00:30:51.530
<v Speaker 3>episode around improving efficiency.

582
00:30:51.949 --> 00:30:56.150
<v Speaker 3>But you know, at least you've got more of
an understanding of what the team focus

583
00:30:56.150 --> 00:30:59.550
<v Speaker 3>is, you know, maybe where the time could
be pushed and spent.

584
00:30:59.670 --> 00:30:59.910
<v Speaker 3>Yeah, I

585
00:30:59.910 --> 00:31:03.430
<v Adam Poole>mean, efficiency is the core thing because
everyone's pushed, you know, everyone's

586
00:31:03.430 --> 00:31:06.430
<v Adam Poole>cut for time, especially in manufacturing
industries.

587
00:31:06.869 --> 00:31:08.069
<v Adam Poole>It's always complex.

588
00:31:08.150 --> 00:31:09.709
<v Adam Poole>It's always kind of an up and down.

589
00:31:09.790 --> 00:31:12.500
<v Adam Poole>You've got your high points where you've
got orders coming in and then you have the

590
00:31:12.930 --> 00:31:14.069
<v Adam Poole>The low periods.

591
00:31:14.489 --> 00:31:20.310
<v Adam Poole>So their workforce might be changeable and
we've got to support that kind of core

592
00:31:20.770 --> 00:31:22.810
<v Adam Poole>need to just make things better
constantly.

593
00:31:22.969 --> 00:31:24.469
<v Adam Poole>Um, that's never going to change.

594
00:31:24.609 --> 00:31:28.030
<v Adam Poole>I don't think, uh, all these companies are
looking for efficiencies.

595
00:31:28.699 --> 00:31:32.979
<v Adam Poole>And I'm quite shocked how small that some
of the teams are and quite what they can

596
00:31:32.979 --> 00:31:33.199
<v Adam Poole>achieve.

597
00:31:33.900 --> 00:31:37.640
<v Adam Poole>You know, they might be responsible for
thousands of machines all at, all at once,

598
00:31:37.890 --> 00:31:41.219
<v Adam Poole>which seems quite an overwhelming thing,
but hopefully it's something we help with.

599
00:31:41.579 --> 00:31:42.000
<v Speaker 3>Yeah.

600
00:31:42.380 --> 00:31:45.400
<v Speaker 3>Well, I definitely around the scaling
topic.

601
00:31:46.420 --> 00:31:50.530
<v Speaker 3>So that's, that's something where we've
seen obviously, you know, customers that

602
00:31:50.530 --> 00:31:51.359
<v Speaker 3>have come on board.

603
00:31:52.030 --> 00:31:56.589
<v Speaker 3>And they're looking at the next step or
next stage when it comes to scaling, and we

604
00:31:56.589 --> 00:31:57.859
<v Speaker 3>can definitely support with that.

605
00:31:57.979 --> 00:32:00.390
<v Adam Poole>Yeah, so you've got scaling within the
same factory.

606
00:32:00.550 --> 00:32:05.300
<v Adam Poole>So you might start in on one particular
line and then go to another one, or even a

607
00:32:05.300 --> 00:32:07.900
<v Adam Poole>different department that's got completely
different machines.

608
00:32:08.209 --> 00:32:10.290
<v Adam Poole>It's about establishing like the best
practice.

609
00:32:11.260 --> 00:32:15.410
<v Adam Poole>So if you get one factory established,
they've jumped through all the hoops, you've,

610
00:32:15.540 --> 00:32:18.819
<v Adam Poole>you've worked out well, you know, the best
sensors, you've got all the best data

611
00:32:18.819 --> 00:32:22.819
<v Adam Poole>coming through, we've got the best
analytics running on it, we've configured all of

612
00:32:22.819 --> 00:32:25.170
<v Adam Poole>that and everything's kind of, you reach
the status quo.

613
00:32:25.380 --> 00:32:27.520
<v Adam Poole>Once you've got that, that's your
template.

614
00:32:28.449 --> 00:32:31.849
<v Adam Poole>And if you've got those factories kind of
everywhere in the world, that means, you

615
00:32:31.849 --> 00:32:35.790
<v Adam Poole>know, it's lower friction to get those
factories up and running.

616
00:32:36.119 --> 00:32:38.170
<v Adam Poole>So that when we talk about scaling, that's
what, that's what we mean.

617
00:32:38.209 --> 00:32:39.670
<v Adam Poole>It's all of those levels.

618
00:32:40.089 --> 00:32:43.250
<v Adam Poole>Um, so these big multinational companies
with, you know, hundreds of factories all

619
00:32:43.250 --> 00:32:43.750
<v Adam Poole>over the place.

620
00:32:44.810 --> 00:32:48.589
<v Adam Poole>That's where the benefits come in because
you've, you put the cost into the first,

621
00:32:48.930 --> 00:32:53.209
<v Adam Poole>um, factory rollout and then the next ones
get easier to do.

622
00:32:53.489 --> 00:32:53.689
<v Adam Poole>Yeah,

623
00:32:53.969 --> 00:32:54.569
<v Speaker 3>well, that's it.

624
00:32:54.849 --> 00:32:58.119
<v Speaker 3>It's this, um, Around, you know, ROI.

625
00:32:58.739 --> 00:33:04.619
<v Speaker 3>So once individuals start to see that
return on investment, and you know, sometimes

626
00:33:04.619 --> 00:33:08.300
<v Speaker 3>people do want to see it very quickly, um,
when it does come to predictive

627
00:33:08.300 --> 00:33:12.420
<v Speaker 3>maintenance, it's, it is, it does take a
lot longer and it takes that time.

628
00:33:12.500 --> 00:33:18.699
<v Speaker 3>But once they start to see the results,
then it's looking at other locations where

629
00:33:18.699 --> 00:33:21.829
<v Speaker 3>they can scale their current deployments.

630
00:33:21.959 --> 00:33:21.969
<v Speaker 3>Yeah.

631
00:33:22.540 --> 00:33:25.680
<v Adam Poole>And again, we talk about the knowledge,
it's all about sharing that knowledge.

632
00:33:26.260 --> 00:33:29.959
<v Adam Poole>And again, adding knowledge into the
system is huge and then sharing that across.

633
00:33:30.890 --> 00:33:32.400
<v Adam Poole>Um, all of those sites as well.

634
00:33:32.489 --> 00:33:36.589
<v Adam Poole>If you've got a best practice, you can
then share it, you know, globally.

635
00:33:37.170 --> 00:33:42.109
<v Adam Poole>Um, and that's the two benefits of scale
and they'd say that's return on investment.

636
00:33:42.449 --> 00:33:45.160
<v Adam Poole>I would hope if I, if I was them, that's
what I'd be looking for.

637
00:33:45.319 --> 00:33:47.650
<v Adam Poole>It's like we don't want to just do it
different every single time.

638
00:33:47.729 --> 00:33:49.760
<v Adam Poole>We want, we need to know what sensors to
use.

639
00:33:49.810 --> 00:33:51.670
<v Adam Poole>We need to know how this is all going to
work.

640
00:33:52.670 --> 00:33:54.959
<v Adam Poole>And you know, we've got a lot of
experience in doing that now.

641
00:33:55.319 --> 00:33:55.560
<v Adam Poole>Yeah,

642
00:33:55.839 --> 00:33:56.520
<v Speaker 3>no, exactly.

643
00:33:56.800 --> 00:33:59.939
<v Speaker 3>Key trends, assets and understanding the
data.

644
00:34:00.400 --> 00:34:01.359
<v Speaker 3>I think that's what it is.

645
00:34:01.469 --> 00:34:07.719
<v Speaker 3>And then, you know, Looking forward into
how that can be implemented across other

646
00:34:07.719 --> 00:34:08.340
<v Speaker 3>plants.

647
00:34:09.239 --> 00:34:13.719
<v Speaker 3>Um, so that takes me to my next question
around this knowledge builder.

648
00:34:14.169 --> 00:34:20.919
<v Speaker 3>And um, I'm really excited to ask
questions around what that means exactly, um, the

649
00:34:20.919 --> 00:34:26.189
<v Speaker 3>current kind of advancements to the
feature that we have within that, um, within the

650
00:34:26.189 --> 00:34:26.560
<v Speaker 3>application.

651
00:34:27.040 --> 00:34:30.360
<v Adam Poole>Yeah, well, a lot of it's about just
supporting the kind of files that people went

652
00:34:30.360 --> 00:34:31.580
<v Adam Poole>up to, to upload.

653
00:34:32.060 --> 00:34:35.379
<v Adam Poole>Which seems, you know, relatively
straightforward, but there's some complexity

654
00:34:35.379 --> 00:34:35.729
<v Adam Poole>there.

655
00:34:36.179 --> 00:34:40.860
<v Adam Poole>So we're just building out support for
base like office files, you know, like Word

656
00:34:40.860 --> 00:34:42.100
<v Adam Poole>documents and that kind of thing.

657
00:34:42.219 --> 00:34:44.040
<v Adam Poole>We've done PDFs historically.

658
00:34:44.340 --> 00:34:49.020
<v Adam Poole>But you have to bear in mind that when you
upload it, the co-pilot's analyzing it

659
00:34:49.020 --> 00:34:53.260
<v Adam Poole>and they get understanding everything
that's in those files, and some are easier

660
00:34:53.260 --> 00:34:53.739
<v Adam Poole>than others.

661
00:34:53.899 --> 00:34:58.689
<v Adam Poole>The trickiest one strangely is Excel,
which is, you know, most companies run on an

662
00:34:58.689 --> 00:35:00.439
<v Adam Poole>Excel, so it's something you need to
support.

663
00:35:00.780 --> 00:35:03.540
<v Adam Poole>But an Excel file can contain all kinds of
stuff.

664
00:35:03.620 --> 00:35:07.260
<v Adam Poole>It could just be a simple table, could
have images, someone could have put some kind

665
00:35:07.260 --> 00:35:09.820
<v Adam Poole>of programming in there, could have all
kinds of stuff in there.

666
00:35:10.139 --> 00:35:11.760
<v Adam Poole>So that's like the harder nut to crack.

667
00:35:12.179 --> 00:35:14.239
<v Adam Poole>But gradually building out support for all
of those.

668
00:35:14.679 --> 00:35:18.040
<v Adam Poole>So you can just be able to interpret
anything that's been updated.

669
00:35:18.320 --> 00:35:24.250
<v Adam Poole>Um, and alongside that, even like things
like text files, so even if you've got

670
00:35:24.250 --> 00:35:27.479
<v Adam Poole>information that's kind of in weird
places, you could combine it and just dump it

671
00:35:27.479 --> 00:35:30.590
<v Adam Poole>all into a text file and say, go and learn
from this.

672
00:35:31.040 --> 00:35:32.719
<v Adam Poole>Then you can put that file anywhere as
well.

673
00:35:32.760 --> 00:35:38.199
<v Adam Poole>And so that, that might contain Like a
useful thing, like a glossary of terms, like

674
00:35:38.199 --> 00:35:42.360
<v Adam Poole>we said about those machines having these
long names officially, but we call it

675
00:35:42.360 --> 00:35:42.719
<v Adam Poole>this.

676
00:35:43.040 --> 00:35:48.750
<v Adam Poole>You could put that in there and you can
train your own kind of co-pilot and how to

677
00:35:48.750 --> 00:35:49.750
<v Adam Poole>understand what's what.

678
00:35:49.800 --> 00:35:53.120
<v Adam Poole>He goes, yes, it's called this, but we
call it this, this is called this, we call it

679
00:35:53.120 --> 00:35:55.350
<v Adam Poole>this, and you'll see those answers come
through.

680
00:35:55.520 --> 00:35:56.959
<v Adam Poole>So there's, there's a lot to do there.

681
00:35:57.250 --> 00:35:57.739
<v Adam Poole>Yeah.

682
00:35:58.159 --> 00:36:05.110
<v Speaker 3>And do you feel so when it comes to um
driving this feature essentially and You

683
00:36:05.110 --> 00:36:08.659
<v Speaker 3>know, making it happen as such in terms of
this.

684
00:36:08.830 --> 00:36:10.459
<v Speaker 3>Now we have this knowledge builder.

685
00:36:11.020 --> 00:36:17.070
<v Speaker 3>Do you feel a lot of that was kind of
taken from um user feedback that we had?

686
00:36:17.229 --> 00:36:18.699
<v Adam Poole>Oh, there's definitely a need for it.

687
00:36:18.750 --> 00:36:19.010
<v Adam Poole>Yeah.

688
00:36:19.239 --> 00:36:23.389
<v Adam Poole>You, you see this with like previously we
added like app mentions, you know, which

689
00:36:23.389 --> 00:36:26.989
<v Adam Poole>is quite a common feature for a lot of
software, like people wanted to talk to each

690
00:36:26.989 --> 00:36:28.010
<v Adam Poole>other in the app.

691
00:36:28.429 --> 00:36:31.030
<v Adam Poole>And we saw that by them just adding names
in.

692
00:36:31.540 --> 00:36:33.219
<v Adam Poole>And expecting it to do something.

693
00:36:33.379 --> 00:36:35.399
<v Adam Poole>So they were trying to use it before it
existed.

694
00:36:35.739 --> 00:36:37.050
<v Adam Poole>And that tells you what to do.

695
00:36:37.620 --> 00:36:38.540
<v Adam Poole>But yeah, we definitely had it.

696
00:36:38.580 --> 00:36:42.300
<v Adam Poole>People would say, oh, really good if I
could put a machine manual in here and then

697
00:36:42.300 --> 00:36:43.060
<v Adam Poole>ask it about.

698
00:36:44.169 --> 00:36:44.800
<v Adam Poole>What I can do.

699
00:36:44.889 --> 00:36:46.209
<v Adam Poole>He goes, oh, that would be so good.

700
00:36:46.290 --> 00:36:49.649
<v Adam Poole>That'd be a no, as soon as we talked about
co-pilot stuff, people were asking for

701
00:36:49.649 --> 00:36:50.350
<v Adam Poole>stuff like that.

702
00:36:51.129 --> 00:36:52.590
<v Adam Poole>So it's a natural response.

703
00:36:53.169 --> 00:36:56.399
<v Adam Poole>And then they're going, oh, I could do
this with it, I could do this with it.

704
00:36:56.449 --> 00:36:58.639
<v Adam Poole>I've got these uh documents ready.

705
00:36:59.209 --> 00:37:00.729
<v Adam Poole>I've been testing, can you test this for
us?

706
00:37:00.770 --> 00:37:05.010
<v Adam Poole>You know, then, then the feedback starts
coming in and you know you've kind of,

707
00:37:05.090 --> 00:37:06.149
<v Adam Poole>you're on the right tracks.

708
00:37:06.449 --> 00:37:07.070
<v Speaker 3>OK.

709
00:37:07.689 --> 00:37:09.370
<v Speaker 3>So yeah, it's a, it's a mix.

710
00:37:09.449 --> 00:37:12.729
<v Speaker 3>I think it's, it maybe, you know, the
natural step.

711
00:37:13.500 --> 00:37:18.820
<v Speaker 3>In terms of developing what we currently
have and you know, making it easier and

712
00:37:18.820 --> 00:37:19.360
<v Speaker 3>simple.

713
00:37:19.810 --> 00:37:23.300
<v Adam Poole>And we'll see these use cases emerge that
we're just providing a way for people to

714
00:37:23.300 --> 00:37:27.540
<v Adam Poole>upload things and then we'll see the types
of things they upload and how they use

715
00:37:27.540 --> 00:37:29.300
<v Adam Poole>the kind of conversations they've had.

716
00:37:29.820 --> 00:37:34.139
<v Adam Poole>And again, you've got that, you'll start
establish a best practice, because we don't

717
00:37:34.139 --> 00:37:34.449
<v Adam Poole>know yet.

718
00:37:34.500 --> 00:37:35.820
<v Adam Poole>This technology is so new.

719
00:37:36.780 --> 00:37:38.729
<v Adam Poole>These use cases are still emerging.

720
00:37:38.909 --> 00:37:40.219
<v Adam Poole>We don't know what's going to come.

721
00:37:40.629 --> 00:37:44.550
<v Adam Poole>So we just have to put the things in place
and then track what's been done with it.

722
00:37:44.590 --> 00:37:46.489
<v Adam Poole>And that shapes the features that come
along.

723
00:37:46.989 --> 00:37:50.520
<v Adam Poole>And you see it everywhere, you know,
there's a lot of stuff that's In other products

724
00:37:50.520 --> 00:37:51.590
<v Adam Poole>is not particularly good.

725
00:37:51.669 --> 00:37:56.639
<v Adam Poole>And then these, um, the winning ways of
doing things will emerge and then people

726
00:37:56.639 --> 00:37:57.919
<v Adam Poole>will build products around that.

727
00:37:58.239 --> 00:38:02.159
<v Adam Poole>We haven't seen any good like hardware
products with uh Gen AI in them yet, but

728
00:38:02.159 --> 00:38:03.469
<v Adam Poole>they'll be coming down the line.

729
00:38:04.169 --> 00:38:05.820
<v Adam Poole>People are thinking about this constantly.

730
00:38:06.120 --> 00:38:06.639
<v Adam Poole>Um.

731
00:38:07.280 --> 00:38:10.760
<v Adam Poole>And that that will solve problems we
didn't even know needed solving.

732
00:38:11.310 --> 00:38:13.060
<v Adam Poole>It's probably going to be the exciting
products

733
00:38:13.060 --> 00:38:13.580
<v Speaker 3>I'd say.

734
00:38:13.899 --> 00:38:16.459
<v Speaker 3>Yeah, which is, it, it's just development,
isn't it?

735
00:38:16.620 --> 00:38:16.919
<v Speaker 3>So

736
00:38:17.290 --> 00:38:18.580
<v Adam Poole>I mean you can't do it in a bubble.

737
00:38:18.770 --> 00:38:21.899
<v Adam Poole>There's the stuff you have to constantly
listen.

738
00:38:22.219 --> 00:38:29.219
<v Speaker 3>Yeah, I feel like, you know, until a
problem, um, occurs, that's when you

739
00:38:29.219 --> 00:38:32.250
<v Speaker 3>maybe think about a solution and how that
fits in.

740
00:38:32.679 --> 00:38:37.659
<v Speaker 3>But the natural step within the
application, it's just key developments.

741
00:38:37.989 --> 00:38:43.590
<v Speaker 3>And I think the good thing about, you
know, the development of this, um, product

742
00:38:43.870 --> 00:38:49.070
<v Speaker 3>would be that we really do listen to our
users and take into account, um, you know,

743
00:38:49.149 --> 00:38:51.020
<v Speaker 3>what's going to make it easier for them.

744
00:38:51.429 --> 00:38:51.540
<v Speaker 3>Yeah,

745
00:38:51.590 --> 00:38:54.149
<v Adam Poole>I always say the worst, the worst feedback
is no feedback.

746
00:38:54.350 --> 00:38:57.830
<v Adam Poole>So if you, if you release something and
you think, oh, we've worked on this for

747
00:38:57.830 --> 00:39:01.790
<v Adam Poole>ages, it's really good and we've done the
big marketing campaign, it's brilliant.

748
00:39:02.110 --> 00:39:04.290
<v Adam Poole>And you just get crickets.

749
00:39:04.679 --> 00:39:06.600
<v Adam Poole>That's just like the worst possible
outcome.

750
00:39:06.679 --> 00:39:10.500
<v Adam Poole>I'd rather release something and you've
got people going, this doesn't work.

751
00:39:11.000 --> 00:39:14.100
<v Adam Poole>This is rubbish, because then you know
what to go and build.

752
00:39:14.959 --> 00:39:15.600
<v Adam Poole>You get nothing.

753
00:39:15.820 --> 00:39:17.469
<v Adam Poole>You, you don't know what to build anymore.

754
00:39:17.560 --> 00:39:18.959
<v Adam Poole>You just got it completely wrong.

755
00:39:19.300 --> 00:39:22.320
<v Speaker 3>And it's everyone's um opinions are
valued.

756
00:39:22.979 --> 00:39:26.620
<v Speaker 3>So for example, you know, I might see
something that you haven't seen.

757
00:39:27.540 --> 00:39:32.169
<v Speaker 3>And you know, looking at it from a
different perspective definitely helps.

758
00:39:32.620 --> 00:39:35.590
<v Adam Poole>Yeah, I love it when we have new starters,
we're like, here's the app, here's how

759
00:39:35.590 --> 00:39:36.020
<v Adam Poole>you use it.

760
00:39:36.100 --> 00:39:38.820
<v Adam Poole>Can you please go and tear it, tear it
apart for us.

761
00:39:39.100 --> 00:39:43.419
<v Adam Poole>It's like, that's your 1st, 1st job
because we look at it every day and we don't, we

762
00:39:43.419 --> 00:39:46.899
<v Adam Poole>got, we're blind to things, completely
blind to stuff, and they'll go, why does that

763
00:39:46.899 --> 00:39:47.179
<v Adam Poole>do that?

764
00:39:47.300 --> 00:39:48.899
<v Adam Poole>And you're like, yeah, that's a good
point.

765
00:39:49.320 --> 00:39:51.159
<v Adam Poole>It's been there for 10 years, but yeah,
you're right.

766
00:39:51.320 --> 00:39:51.909
<v Adam Poole>It shouldn't do that.

767
00:39:51.959 --> 00:39:52.429
<v Adam Poole>We'll do something else.

768
00:39:53.570 --> 00:39:54.040
<v Adam Poole>It's brilliant.

769
00:39:54.520 --> 00:39:57.179
<v Speaker 3>It just helps you just to understand it
just from a different.

770
00:39:57.280 --> 00:39:59.070
<v Adam Poole>Yeah, you can't, there's no ego in it.

771
00:39:59.479 --> 00:40:01.300
<v Speaker 3>And there's no kind of right or wrong
answer.

772
00:40:01.399 --> 00:40:01.959
<v Speaker 3>It's fine.

773
00:40:02.030 --> 00:40:05.159
<v Speaker 3>You know, just like, just, just with
anything, you have to test it.

774
00:40:05.280 --> 00:40:10.439
<v Speaker 3>We have to go through this process of
testing, um, getting feedback, you know, going

775
00:40:10.439 --> 00:40:15.520
<v Speaker 3>through the process of what we need to
prioritize, um, what should be done first.

776
00:40:15.929 --> 00:40:20.550
<v Speaker 3>That whole implementation process and then
also like post implementing, it's still

777
00:40:20.850 --> 00:40:22.270
<v Speaker 3>that user feedback.

778
00:40:22.649 --> 00:40:25.929
<v Speaker 3>You know, if something can be better, and
that's fine.

779
00:40:26.250 --> 00:40:28.350
<v Speaker 3>You know, it's not there's there's nothing
wrong with that.

780
00:40:29.340 --> 00:40:29.889
<v Speaker 3>Um,

781
00:40:31.139 --> 00:40:31.659
<v Adam Poole>Can't live it.

782
00:40:31.729 --> 00:40:32.879
<v Adam Poole>Yeah, you can't live in a bubble.

783
00:40:33.770 --> 00:40:38.699
<v Adam Poole>It has to be, um, has to be out there and
it goes beyond the product team.

784
00:40:38.739 --> 00:40:42.489
<v Adam Poole>It goes from everyone, you know, everyone
feeds in all the teams from all

785
00:40:42.489 --> 00:40:43.379
<v Adam Poole>nationalities.

786
00:40:43.459 --> 00:40:47.739
<v Adam Poole>Um, and they say you'll get international
requests that you hadn't even considered

787
00:40:47.739 --> 00:40:51.479
<v Adam Poole>or issues come up, you hadn't even thought
about that you need to jump through,

788
00:40:51.979 --> 00:40:56.100
<v Adam Poole>whether it's legal side of things like
certain countries will let you do certain

789
00:40:56.100 --> 00:40:57.090
<v Adam Poole>things, other countries don't.

790
00:40:57.500 --> 00:41:00.909
<v Adam Poole>So we have to Make sure we're doing the
right things legally as well.

791
00:41:01.100 --> 00:41:03.389
<v Speaker 3>So I think that's the other, the other
part of it actually.

792
00:41:03.540 --> 00:41:05.659
<v Speaker 3>So, you know, regulation and compliance.

793
00:41:06.060 --> 00:41:09.780
<v Adam Poole>Oh yeah, and like some companies are some
countries are further ahead than others in

794
00:41:09.780 --> 00:41:13.620
<v Adam Poole>terms of especially with the GI stuff,
which is just It's all new, they don't

795
00:41:13.620 --> 00:41:14.639
<v Adam Poole>necessarily have the policies there.

796
00:41:15.909 --> 00:41:18.469
<v Adam Poole>So they'll be like, no, no, you can't do
that, so you have to.

797
00:41:19.250 --> 00:41:22.770
<v Adam Poole>Anticipate, you have to prepare that some
places won't be able to use all the

798
00:41:22.770 --> 00:41:24.929
<v Adam Poole>features, but you kind of want them to.

799
00:41:25.050 --> 00:41:29.169
<v Adam Poole>So you, you know, have it ready and
waiting for them when when they are ready to do

800
00:41:29.169 --> 00:41:29.550
<v Adam Poole>stuff.

801
00:41:30.290 --> 00:41:30.770
<v Adam Poole>Um.

802
00:41:31.429 --> 00:41:34.510
<v Adam Poole>But that's the benefits of being within a
big company when you've got a big legal

803
00:41:34.510 --> 00:41:35.350
<v Adam Poole>department who know.

804
00:41:36.149 --> 00:41:40.149
<v Adam Poole>Who deal with all these countries all the
time and know what we need to do to get

805
00:41:40.149 --> 00:41:40.629
<v Adam Poole>those features out.

806
00:41:40.780 --> 00:41:43.570
<v Adam Poole>There's no point developing anything if if
legally you can't release them.

807
00:41:44.510 --> 00:41:49.629
<v Adam Poole>Um, that's a really interesting angle that
I Didn't quite anticipate and it's quite

808
00:41:49.629 --> 00:41:52.030
<v Adam Poole>nuanced as well, what you can do and can't
do.

809
00:41:52.310 --> 00:41:52.689
<v Adam Poole>Yeah.

810
00:41:53.070 --> 00:41:58.610
<v Speaker 3>Well, it goes back to development of of
the application, like you mentioned around

811
00:41:58.820 --> 00:42:01.010
<v Speaker 3>translations that we have in different
languages.

812
00:42:01.310 --> 00:42:05.409
<v Speaker 3>With that, we do have, you know, a very
global customer base.

813
00:42:05.830 --> 00:42:09.949
<v Speaker 3>And it's interesting actually, you know,
when we go into this topic around

814
00:42:09.949 --> 00:42:14.139
<v Speaker 3>compliance and regulation, sometimes you
don't You're oblivious to it.

815
00:42:14.260 --> 00:42:17.620
<v Speaker 3>You don't really think about it because
you're just focused on the application

816
00:42:17.620 --> 00:42:18.239
<v Speaker 3>itself.

817
00:42:18.669 --> 00:42:22.419
<v Speaker 3>Um, but at the same time, you kind of want
everyone to be able to,

818
00:42:22.860 --> 00:42:24.899
<v Adam Poole>we're kind of oblivious until someone
says, no, you can't do that.

819
00:42:26.860 --> 00:42:29.500
<v Adam Poole>There doesn't seem to be much between it
and then you're like, oh, we need to find a

820
00:42:29.500 --> 00:42:34.600
<v Adam Poole>way through this and develop new policies
to, to get us in these places.

821
00:42:34.780 --> 00:42:34.899
<v Adam Poole>Yeah,

822
00:42:35.100 --> 00:42:35.610
<v Speaker 3>exactly.

823
00:42:35.979 --> 00:42:40.149
<v Speaker 3>Um, and I just wanted to just touch into
the get help.

824
00:42:40.659 --> 00:42:43.219
<v Speaker 3>Element that we have within the sense of
application.

825
00:42:43.780 --> 00:42:48.199
<v Speaker 3>So, You know, how does that link into the
knowledge builder?

826
00:42:48.679 --> 00:42:51.560
<v Adam Poole>Well, yeah, the new thing we've done now,
so on that homepage where there's a little

827
00:42:51.560 --> 00:42:55.100
<v Adam Poole>help thing is we've integrated with our
help center.

828
00:42:55.600 --> 00:42:58.699
<v Adam Poole>Um, so that's all manually written.

829
00:42:58.800 --> 00:43:03.040
<v Adam Poole>I, I write all the help articles, which is
a nice kind of end to end thing.

830
00:43:03.070 --> 00:43:05.639
<v Adam Poole>It's like make the thing and then tell
people how to use the thing.

831
00:43:05.699 --> 00:43:08.419
<v Adam Poole>It's a nice kind of story to tell to
people.

832
00:43:08.840 --> 00:43:11.429
<v Adam Poole>Um, but that's like hosted in a separate
application.

833
00:43:11.719 --> 00:43:14.530
<v Adam Poole>So as soon as you, within the app, as soon
as you go to help, you're, you've gone

834
00:43:14.530 --> 00:43:15.120
<v Adam Poole>somewhere else.

835
00:43:15.409 --> 00:43:16.879
<v Adam Poole>We've kind of, you don't really want that.

836
00:43:16.929 --> 00:43:19.530
<v Adam Poole>You want people, you want to get the
answer there and then.

837
00:43:19.850 --> 00:43:23.189
<v Adam Poole>So that, that help feature is something
we'll be expanding across the whole app.

838
00:43:23.370 --> 00:43:28.330
<v Adam Poole>So you'll just go into the copilot and ask
it some questions like, what is this and

839
00:43:28.330 --> 00:43:32.989
<v Adam Poole>what, what's an asset and like all the
fundamental stuff and it will Be able to

840
00:43:32.989 --> 00:43:37.419
<v Adam Poole>search through the um help content,
summarize it for you, give you a quick response

841
00:43:37.419 --> 00:43:39.340
<v Adam Poole>there and then, you know, a quick
immediate response.

842
00:43:39.959 --> 00:43:43.000
<v Adam Poole>But also, as we said, it will refer to
where it's come from as well.

843
00:43:43.189 --> 00:43:46.199
<v Adam Poole>So you'll have links to the articles that
it's got the information from.

844
00:43:46.959 --> 00:43:48.179
<v Adam Poole>So it's all about expanding.

845
00:43:48.520 --> 00:43:49.590
<v Adam Poole>Again, that's knowledge as well.

846
00:43:49.639 --> 00:43:53.389
<v Adam Poole>When we talk about knowledge, it's like
institutional knowledge from the customers.

847
00:43:53.550 --> 00:43:56.979
<v Adam Poole>It's, it's our knowledge, it's everything
we've ever known about building the app,

848
00:43:57.080 --> 00:44:02.560
<v Adam Poole>but not just building the app, but also
how to have a successful um implementation

849
00:44:02.560 --> 00:44:02.979
<v Adam Poole>of it.

850
00:44:03.239 --> 00:44:06.159
<v Adam Poole>You know, we've got a whole kind of
knowledge base for that kind of thing which is

851
00:44:06.159 --> 00:44:08.679
<v Adam Poole>now accessible through that copilot.

852
00:44:09.489 --> 00:44:14.419
<v Adam Poole>So all, all the projects that failed, all
the hard lessons we've learned are kind of

853
00:44:14.419 --> 00:44:15.790
<v Adam Poole>encoded in there now.

854
00:44:16.489 --> 00:44:17.010
<v Adam Poole>Um.

855
00:44:17.790 --> 00:44:21.310
<v Adam Poole>Because it's hugely important, you know,
you can, you can, a project can live or die

856
00:44:21.310 --> 00:44:23.949
<v Adam Poole>in the first couple of months, so you want
some really good responses.

857
00:44:23.989 --> 00:44:29.239
<v Adam Poole>You want people to Understand how to use
things immediately, as quickly as possible,

858
00:44:29.280 --> 00:44:33.399
<v Adam Poole>which is not easy, even not easy when, you
know, behind the scenes there's a lot of

859
00:44:33.399 --> 00:44:33.959
<v Adam Poole>complexity.

860
00:44:34.800 --> 00:44:38.439
<v Adam Poole>Setting up the data coming in is, is the
biggest part, getting that, the right data,

861
00:44:38.510 --> 00:44:39.780
<v Adam Poole>the right analytics set up.

862
00:44:40.590 --> 00:44:44.969
<v Adam Poole>So anything that smooths that is um is, is
a good thing.

863
00:44:45.030 --> 00:44:50.229
<v Adam Poole>Um, and that big story of connected
knowledge, you know, our knowledge, your

864
00:44:50.229 --> 00:44:51.409
<v Adam Poole>knowledge, all in one place.

865
00:44:52.429 --> 00:44:54.389
<v Adam Poole>Um, it's great, Backs up everything

866
00:44:54.389 --> 00:44:54.709
<v Speaker 3>really.

867
00:44:54.909 --> 00:44:55.669
<v Speaker 3>Yeah, exactly.

868
00:44:55.870 --> 00:44:58.290
<v Speaker 3>I think the knowledge builder is
fantastic.

869
00:44:58.790 --> 00:45:00.810
<v Speaker 3>Really, really great resource to have.

870
00:45:01.310 --> 00:45:06.610
<v Speaker 3>And you know, like I said, with that
working with the co-pilot itself.

871
00:45:07.635 --> 00:45:14.254
<v Speaker 3>are more in control of their data, so they
have more of an understanding, but also

872
00:45:14.254 --> 00:45:17.415
<v Speaker 3>they have this resource available where
it's easy for them to

873
00:45:17.415 --> 00:45:17.804
<v Adam Poole>check.

874
00:45:18.175 --> 00:45:21.455
<v Adam Poole>Yeah, and it's the most important part is,
is their data.

875
00:45:22.254 --> 00:45:27.455
<v Adam Poole>So each instance, like each customer
instance is, is its own separate entity.

876
00:45:27.574 --> 00:45:30.610
<v Adam Poole>So there's no Bleed of information between
accounts.

877
00:45:30.649 --> 00:45:32.080
<v Adam Poole>It's all separate.

878
00:45:32.290 --> 00:45:33.889
<v Adam Poole>Same for the co-pilot instance as well.

879
00:45:33.929 --> 00:45:35.350
<v Adam Poole>There's nothing going out to the internet.

880
00:45:35.649 --> 00:45:37.449
<v Adam Poole>There's nothing shared between accounts.

881
00:45:38.129 --> 00:45:41.989
<v Adam Poole>So anything that is uploaded is, can be
trusted and goes nowhere else.

882
00:45:42.409 --> 00:45:46.530
<v Adam Poole>Um, it's the first thing people ask and
it's, it's the first thing we can answer as

883
00:45:46.530 --> 00:45:48.389
<v Adam Poole>well, because it's incredibly important.

884
00:45:49.020 --> 00:45:52.469
<v Adam Poole>And something that's probably a bit more
neglected in the, in the commercial world

885
00:45:52.469 --> 00:45:56.909
<v Adam Poole>of Gen where it's a bit fast and loose
with copyright and things like that.

886
00:45:57.379 --> 00:45:59.260
<v Adam Poole>So we are not doing that.

887
00:45:59.510 --> 00:46:00.139
<v Speaker 3>No, exactly.

888
00:46:00.219 --> 00:46:00.860
<v Speaker 3>I think that's it.

889
00:46:00.939 --> 00:46:07.899
<v Speaker 3>Just one, key point that you mentioned
actually just around having

890
00:46:07.899 --> 00:46:09.760
<v Speaker 3>it private and confidential.

891
00:46:10.020 --> 00:46:16.419
<v Speaker 3>That data is just for you and Your assets
and your

892
00:46:16.419 --> 00:46:18.280
<v Speaker 3>deployments which are taking place.

893
00:46:18.979 --> 00:46:19.699
<v Speaker 3>So I think we

894
00:46:19.699 --> 00:46:24.090
<v Adam Poole>do an awful lot, even if, if users try
adding their own personal information, it

895
00:46:24.090 --> 00:46:27.260
<v Adam Poole>will automatically get stripped out
because it's like, yeah, we have to protect all

896
00:46:27.260 --> 00:46:28.060
<v Adam Poole>of that kind of thing.

897
00:46:28.620 --> 00:46:29.840
<v Adam Poole>So we do a lot of stuff.

898
00:46:31.399 --> 00:46:34.239
<v Speaker 3>There's a lot of like behind the scenes
of, yeah, that needs to be done.

899
00:46:35.439 --> 00:46:36.239
<v Adam Poole>Data protection comes first,

900
00:46:36.550 --> 00:46:37.219
<v Speaker 3>of course, yeah.

901
00:46:38.179 --> 00:46:43.699
<v Speaker 3>Um, and then leading on to one of the
other features, Adam, so we've touched on

902
00:46:43.699 --> 00:46:46.139
<v Speaker 3>quite a few advancements on the
application.

903
00:46:46.540 --> 00:46:50.840
<v Speaker 3>Um, just wanted to get some more
information around the smart auto components.

904
00:46:51.489 --> 00:46:55.760
<v Speaker 3>Number one, what is that and how has that
developed?

905
00:46:56.010 --> 00:46:58.919
<v Adam Poole>Yeah, it's probably something people see
in our screenshots and things we put out,

906
00:46:58.969 --> 00:47:01.310
<v Adam Poole>but that's, this is our demo account that
we have.

907
00:47:02.050 --> 00:47:07.489
<v Adam Poole>So when people get the first look at what,
what the product is, whether it's on our

908
00:47:07.489 --> 00:47:12.030
<v Adam Poole>website or in person demos, that's the,
the account we use to show everyone.

909
00:47:12.409 --> 00:47:17.840
<v Adam Poole>And we flesh that out with kind of all of
the um different industries we deal with.

910
00:47:17.929 --> 00:47:20.209
<v Adam Poole>It's got all the features represented in
there.

911
00:47:20.709 --> 00:47:23.060
<v Adam Poole>Um, and can be used internationally.

912
00:47:23.280 --> 00:47:25.040
<v Adam Poole>Like I say, we've got all the translation
in there.

913
00:47:25.360 --> 00:47:29.070
<v Adam Poole>So it's like your 1st, 1st stop in what
the product is.

914
00:47:29.639 --> 00:47:32.409
<v Adam Poole>So I know we've done interactive demos
now, haven't we?

915
00:47:33.100 --> 00:47:35.060
<v Adam Poole>And that will be showing that account on
there.

916
00:47:35.320 --> 00:47:40.669
<v Adam Poole>So it gives representative assets, it
gives you an idea of how the whole thing works

917
00:47:40.669 --> 00:47:41.919
<v Adam Poole>and what all the features are.

918
00:47:42.159 --> 00:47:45.929
<v Adam Poole>So it's like a It's kind of our safe place
to show everything really.

919
00:47:46.370 --> 00:47:47.959
<v Adam Poole>And we've always liked to show the
products.

920
00:47:48.330 --> 00:47:53.030
<v Adam Poole>We do obviously like, uh, analyze our
competitors and things and you'll often find

921
00:47:53.580 --> 00:47:54.870
<v Adam Poole>you can't see the product.

922
00:47:54.939 --> 00:47:58.729
<v Adam Poole>And we've always said, just, we need to
show the product, you know, we're confident,

923
00:47:58.810 --> 00:48:01.669
<v Adam Poole>we know it works, and like, here it is out
there in the wild.

924
00:48:02.449 --> 00:48:03.370
<v Adam Poole>These aren't mockups.

925
00:48:03.409 --> 00:48:04.570
<v Adam Poole>This is the actual thing.

926
00:48:05.429 --> 00:48:08.209
<v Adam Poole>Um, and that's, that should be a
differentiator, I think.

927
00:48:09.050 --> 00:48:10.550
<v Adam Poole>Um, it's quite shocking.

928
00:48:10.770 --> 00:48:14.429
<v Adam Poole>You, you can honestly not find things and
they're like, oh, we do all this kind of

929
00:48:14.429 --> 00:48:17.699
<v Adam Poole>stuff and you're just like, please, can I
just see it and like and use it.

930
00:48:18.149 --> 00:48:18.790
<v Speaker 3>I think this is it.

931
00:48:18.830 --> 00:48:23.699
<v Speaker 3>It's exciting because, you know, working
with, from my perspective, working with

932
00:48:23.699 --> 00:48:25.090
<v Speaker 3>various different regions.

933
00:48:25.564 --> 00:48:29.084
<v Speaker 3>Um, we touched around the Sensei demo that
we have.

934
00:48:29.405 --> 00:48:33.004
<v Speaker 3>But this also links to the Novatic demo
that we have, for example.

935
00:48:33.524 --> 00:48:38.715
<v Speaker 3>So it's, it's really great because I feel
like from a sales perspective, you know,

936
00:48:38.844 --> 00:48:44.284
<v Speaker 3>talking to the business development teams,
having that demonstration essentially

937
00:48:44.284 --> 00:48:45.385
<v Speaker 3>helps to qualify.

938
00:48:46.570 --> 00:48:53.030
<v Speaker 3>The customer, you know, so it's more of a,
I want to say a teaser into showing

939
00:48:53.699 --> 00:48:57.810
<v Speaker 3>Sensi predictive maintenance and this is
the dashboard and this is how you can check

940
00:48:57.810 --> 00:49:01.469
<v Speaker 3>your use cases and this is how you can
look into your assets.

941
00:49:01.850 --> 00:49:04.770
<v Speaker 3>Um, but having that benefit is amazing.

942
00:49:05.169 --> 00:49:08.129
<v Adam Poole>Yeah, and the good thing is there won't be
a jump when they actually use the real

943
00:49:08.129 --> 00:49:08.310
<v Adam Poole>product.

944
00:49:08.679 --> 00:49:09.889
<v Adam Poole>It's it's the same

945
00:49:09.889 --> 00:49:10.120
<v Speaker 3>thing.

946
00:49:10.889 --> 00:49:12.370
<v Adam Poole>There's no kind of smoke and mirrors
there.

947
00:49:12.439 --> 00:49:13.149
<v Adam Poole>It's um.

948
00:49:13.709 --> 00:49:18.370
<v Adam Poole>It's a very natural path towards them, uh,
populating with all their data.

949
00:49:18.560 --> 00:49:18.889
<v Speaker 3>Yeah.

950
00:49:19.229 --> 00:49:24.120
<v Speaker 3>And also having, um, you know, you've,
you've probably seen the videos of the, um,

951
00:49:24.409 --> 00:49:26.610
<v Speaker 3>Sensei or the co-pilot in action.

952
00:49:27.110 --> 00:49:31.070
<v Speaker 3>So for a customer to see that live in
action, it's just like, wow.

953
00:49:31.389 --> 00:49:34.699
<v Adam Poole>Yeah, there's always some skepticism, I
think, isn't there, uh, that you're kind of

954
00:49:34.699 --> 00:49:35.760
<v Adam Poole>faking it or something.

955
00:49:36.100 --> 00:49:40.510
<v Adam Poole>But we've always put it out there for real
and do the live demos on live videos.

956
00:49:40.590 --> 00:49:45.600
<v Adam Poole>I think the first use of it was a live
demo in the Uh, Siemens event and it was all,

957
00:49:45.800 --> 00:49:49.219
<v Adam Poole>it all, it all works, but we've always
been prepared to do that kind of thing.

958
00:49:50.159 --> 00:49:51.030
<v Adam Poole>Nothing scripted.

959
00:49:51.399 --> 00:49:51.560
<v Adam Poole>Yeah,

960
00:49:51.840 --> 00:49:52.260
<v Speaker 3>exactly.

961
00:49:52.560 --> 00:49:57.600
<v Speaker 3>Like I said, it's, it's, it's always
amazing just to see how it works and to

962
00:49:57.600 --> 00:50:03.189
<v Speaker 3>understand, you know, the essentially
asking a question and receiving a response,

963
00:50:03.320 --> 00:50:07.840
<v Speaker 3>but not just any response, it's You know,
simplifying and understanding the

964
00:50:07.840 --> 00:50:09.949
<v Speaker 3>technical terms of what's going on.

965
00:50:10.489 --> 00:50:14.969
<v Speaker 3>So, I think that's the beauty of it and
having that feature within the application

966
00:50:14.969 --> 00:50:20.370
<v Speaker 3>is just great because it's aligned with
current trends and you know, like I said,

967
00:50:20.729 --> 00:50:27.689
<v Speaker 3>generative AI is a part of the
application, but we're not focused on that to

968
00:50:27.689 --> 00:50:32.010
<v Speaker 3>be the, the most important function within
the application.

969
00:50:32.489 --> 00:50:35.149
<v Speaker 3>So, like I said again, improving
efficiency.

970
00:50:35.790 --> 00:50:36.689
<v Adam Poole>That's the theme I think.

971
00:50:37.110 --> 00:50:37.899
<v Speaker 3>Yeah, exactly.

972
00:50:38.179 --> 00:50:45.100
<v Speaker 3>And um how, how do you kind of think this
really fits in with the

973
00:50:45.100 --> 00:50:46.810
<v Speaker 3>predictive maintenance strategy?

974
00:50:47.350 --> 00:50:51.149
<v Speaker 3>So the smart auto components of the
demonstration.

975
00:50:51.959 --> 00:50:54.229
<v Adam Poole>Well, we talk about scale, but also the
flexibility.

976
00:50:54.310 --> 00:50:58.209
<v Adam Poole>I think we've become more of a platform
when I said about all the industries.

977
00:50:59.010 --> 00:51:01.729
<v Adam Poole>There's like so many different industries
that we've kind of tried to represent in

978
00:51:01.729 --> 00:51:02.570
<v Adam Poole>that demo account.

979
00:51:02.850 --> 00:51:06.810
<v Adam Poole>And I know we, we have customers in many
different industries where, we've always

980
00:51:06.810 --> 00:51:13.209
<v Adam Poole>been quite agnostic to what the industry
is and what the machines are, because the

981
00:51:13.209 --> 00:51:18.129
<v Adam Poole>way we've constructed the technology is
that it applies to like all machines, which

982
00:51:18.129 --> 00:51:22.489
<v Adam Poole>has been a huge, huge part of it, makes it
more sellable and makes it more scalable.

983
00:51:22.610 --> 00:51:24.649
<v Adam Poole>So it's like we don't have any
preconfigured.

984
00:51:25.409 --> 00:51:29.459
<v Adam Poole>Uh, models of what the machines are, we,
we learn from the data it receives.

985
00:51:30.129 --> 00:51:31.639
<v Adam Poole>And that's, that's like a core point of
it.

986
00:51:31.689 --> 00:51:35.870
<v Adam Poole>So it doesn't matter if you've got
gearboxes or motors or robot arms or whatever,

987
00:51:36.489 --> 00:51:37.750
<v Adam Poole>it'll just learn on the go.

988
00:51:38.370 --> 00:51:40.350
<v Adam Poole>We have no preconception of what they are.

989
00:51:41.209 --> 00:51:43.610
<v Adam Poole>Um, it will just purely be based on the,
on the data.

990
00:51:43.729 --> 00:51:47.850
<v Adam Poole>So all of those industries, obviously some
are more suitable for others depending,

991
00:51:47.929 --> 00:51:50.330
<v Adam Poole>and it's entirely depending on the type of
data that comes through.

992
00:51:50.959 --> 00:51:54.300
<v Adam Poole>Um, but that, um, hopefully puts us in
good stead.

993
00:51:54.649 --> 00:51:57.919
<v Adam Poole>And from the redesign work we've done,
it's definitely more platform based.

994
00:51:57.969 --> 00:52:01.790
<v Adam Poole>It's more consistent, uh, experience
across the whole app now.

995
00:52:02.610 --> 00:52:04.229
<v Speaker 3>Yeah, OK, cool.

996
00:52:04.600 --> 00:52:05.120
<v Speaker 3>That sounds good.

997
00:52:05.169 --> 00:52:10.649
<v Speaker 3>I think it's a, it's, it's nice to
understand that from a strategy perspective of,

998
00:52:10.760 --> 00:52:17.010
<v Speaker 3>you know, what the, the key benefits are
and how it's actually supporting processes.

999
00:52:17.530 --> 00:52:20.919
<v Speaker 3>Um, around different industries, different
assets.

1000
00:52:21.340 --> 00:52:26.479
<v Speaker 3>And you mentioned around assets, you know,
it can that there's no kind of, we can't

1001
00:52:26.739 --> 00:52:29.159
<v Speaker 3>do this for the asset, I want to say.

1002
00:52:29.510 --> 00:52:33.800
<v Speaker 3>Um, like I said, in different locations,
different plants, different factories,

1003
00:52:34.260 --> 00:52:38.620
<v Speaker 3>there will, there will always be different
assets which need to be monitored and

1004
00:52:38.620 --> 00:52:41.439
<v Speaker 3>different issues which need to be
resolved.

1005
00:52:42.399 --> 00:52:45.800
<v Adam Poole>Yeah, and, and some are more successful
than others, like, but the biggest thing is

1006
00:52:45.800 --> 00:52:49.360
<v Adam Poole>if you've got a fleet of the kind of same
type of asset, you'll get the best

1007
00:52:49.360 --> 00:52:49.600
<v Adam Poole>results.

1008
00:52:49.639 --> 00:52:52.399
<v Adam Poole>Like if you've got all these types of
motors, you've got hundreds of motors,

1009
00:52:52.439 --> 00:52:53.699
<v Adam Poole>hundreds of gearboxes.

1010
00:52:54.790 --> 00:52:56.149
<v Adam Poole>Drop lifters, whatever they are.

1011
00:52:56.189 --> 00:53:00.229
<v Adam Poole>If you've got lots of them, we get the,
you'll get the best results because the

1012
00:53:00.229 --> 00:53:04.510
<v Adam Poole>system will learn from what happened over
here, might be happening over here, and

1013
00:53:04.510 --> 00:53:07.870
<v Adam Poole>you get this kind of, again, the knowledge
base that builds up, that can be shared

1014
00:53:07.870 --> 00:53:09.129
<v Adam Poole>across all those machines.

1015
00:53:09.659 --> 00:53:14.100
<v Adam Poole>Uh, so, and again, if you've got multiple
factories, that knowledge can be shared

1016
00:53:14.100 --> 00:53:15.129
<v Adam Poole>across all of those as well.

1017
00:53:15.389 --> 00:53:18.939
<v Adam Poole>So you just, you just kind of constantly
learning, keep learning and learning.

1018
00:53:19.270 --> 00:53:19.379
<v Adam Poole>Well,

1019
00:53:19.429 --> 00:53:21.229
<v Speaker 3>it links to scaling, doesn't it?

1020
00:53:21.350 --> 00:53:22.489
<v Speaker 3>So it's the

1021
00:53:22.489 --> 00:53:23.620
<v Adam Poole>benefits of scaling.

1022
00:53:24.439 --> 00:53:26.959
<v Adam Poole>And you, you, you almost need failures as
well.

1023
00:53:27.070 --> 00:53:32.800
<v Adam Poole>It's you get, we, we need stuff to, to
break in, in, in order to learn, if you know

1024
00:53:32.800 --> 00:53:34.360
<v Adam Poole>what I mean, or to anticipate them
breaking.

1025
00:53:34.439 --> 00:53:38.570
<v Adam Poole>So If you've got a factory where
everything's amazingly maintained and there's no

1026
00:53:38.570 --> 00:53:40.639
<v Adam Poole>failures, people go, your software doesn't
do anything.

1027
00:53:40.659 --> 00:53:44.350
<v Adam Poole>And it's like, no, you're just doing a
really good job, but we're still monitoring

1028
00:53:44.350 --> 00:53:47.820
<v Adam Poole>and everything and something still could
fail, um.

1029
00:53:48.729 --> 00:53:53.979
<v Adam Poole>But we almost need to see, people need to
see a failure to understand how it works,

1030
00:53:54.139 --> 00:53:55.840
<v Adam Poole>which is quite an interesting concept.

1031
00:53:56.179 --> 00:53:58.739
<v Adam Poole>Whereas we're going out of our way to
avoid failure.

1032
00:53:59.080 --> 00:54:00.489
<v Adam Poole>It's like we don't want new machines to
fail.

1033
00:54:00.570 --> 00:54:03.780
<v Adam Poole>We want to anticipate everything that's
going to happen so that never happens for

1034
00:54:03.780 --> 00:54:04.080
<v Adam Poole>you.

1035
00:54:04.699 --> 00:54:07.439
<v Adam Poole>So you've got, that's like your insurance
policy, I guess.

1036
00:54:08.020 --> 00:54:10.540
<v Speaker 3>Yeah, I like the way that, that's good.

1037
00:54:11.149 --> 00:54:15.770
<v Speaker 3>Um, so what measurable, um, benefits.

1038
00:54:17.629 --> 00:54:23.750
<v Speaker 3>You know, have users experienced and this
could be, you know, really high level.

1039
00:54:23.870 --> 00:54:27.729
<v Speaker 3>So maybe, you know, if you've got a couple
that you could just maybe share.

1040
00:54:28.229 --> 00:54:33.770
<v Adam Poole>Well, a lot of customers, they, they
always talk about downtime, scheduled avoiding

1041
00:54:34.229 --> 00:54:37.830
<v Adam Poole>downtime is, was the thing we always
started with, and that's still a big thing.

1042
00:54:38.669 --> 00:54:44.830
<v Adam Poole>So we have these success cases like we
spotted this thing and that saved 16 hours of

1043
00:54:44.830 --> 00:54:45.510
<v Adam Poole>downtime.

1044
00:54:46.320 --> 00:54:48.800
<v Adam Poole>Which means they didn't have to stop
production.

1045
00:54:49.199 --> 00:54:51.719
<v Adam Poole>It means they didn't have to go do
emergency maintenance.

1046
00:54:51.959 --> 00:54:53.100
<v Adam Poole>None of that had to happen.

1047
00:54:53.959 --> 00:54:57.399
<v Adam Poole>And each hour of that downtime, they'll,
they'll have their own cost associated,

1048
00:54:57.760 --> 00:54:59.550
<v Adam Poole>which is likely in the thousands.

1049
00:54:59.919 --> 00:55:05.620
<v Adam Poole>So one single instance could pay for the
whole application for the, for the year,

1050
00:55:05.679 --> 00:55:06.340
<v Adam Poole>basically.

1051
00:55:06.760 --> 00:55:08.919
<v Adam Poole>So that's the kind of measurable success.

1052
00:55:09.469 --> 00:55:10.870
<v Adam Poole>And sometimes that happens very quickly.

1053
00:55:11.030 --> 00:55:15.469
<v Adam Poole>I think we had a customer recently had
that within the 1st 2 weeks of using the

1054
00:55:15.469 --> 00:55:15.750
<v Adam Poole>product.

1055
00:55:16.030 --> 00:55:18.810
<v Adam Poole>So you've effectively paid for it
immediately.

1056
00:55:19.389 --> 00:55:25.030
<v Adam Poole>That's the whole cost saved because You
know what's the work that needs doing, but

1057
00:55:25.030 --> 00:55:29.649
<v Adam Poole>instead of having to stop production, you
know the scale of the issue, so you can do

1058
00:55:29.649 --> 00:55:31.620
<v Adam Poole>the maintenance in a time that you'd
already planned.

1059
00:55:31.709 --> 00:55:34.909
<v Adam Poole>Like, we're going to shut down at the
weekend, so we'll just go in and change that

1060
00:55:34.909 --> 00:55:38.949
<v Adam Poole>gearbox rather than we need to do that
right now because that bearing is going to

1061
00:55:38.949 --> 00:55:42.389
<v Adam Poole>explode, you know, that, that's the
measurable difference.

1062
00:55:42.810 --> 00:55:44.889
<v Adam Poole>Those are the successes we're always
looking for.

1063
00:55:45.709 --> 00:55:47.530
<v Adam Poole>Basically it's entirely measurable.

1064
00:55:47.870 --> 00:55:54.189
<v Adam Poole>Um, but also in terms of, yeah, hours
saved in labor as well is a big one, but also

1065
00:55:54.189 --> 00:55:58.830
<v Adam Poole>in kind of scaling the maintenance team,
you know, their work, there might be a lot

1066
00:55:58.830 --> 00:56:02.449
<v Adam Poole>of stuff that they, they no longer have to
do, they might decide that their

1067
00:56:02.909 --> 00:56:04.149
<v Adam Poole>maintenance intervals.

1068
00:56:04.669 --> 00:56:08.360
<v Adam Poole>Um, they can extend them now because
they've got this constant monitoring going on

1069
00:56:08.360 --> 00:56:09.719
<v Adam Poole>and they previously didn't.

1070
00:56:09.800 --> 00:56:14.040
<v Adam Poole>They might have done weekly inspections
before, you know, moving into this

1071
00:56:14.040 --> 00:56:18.929
<v Adam Poole>predictive way rather than a kind of
preventative way of doing things or reactive.

1072
00:56:19.040 --> 00:56:22.760
<v Adam Poole>You're not just reacting to things
happening all the time, you can plan it better.

1073
00:56:23.530 --> 00:56:26.909
<v Adam Poole>And that saves time, that saves money, so
all of that's measurable.

1074
00:56:27.870 --> 00:56:31.770
<v Adam Poole>Related to ROI but also any important KPIs
they've got.

1075
00:56:31.989 --> 00:56:37.709
<v Speaker 3>Yeah, I think the other thing as well just
to, just to mention just around um

1076
00:56:38.149 --> 00:56:43.229
<v Speaker 3>workforce and when it comes to travel
costs as well.

1077
00:56:43.550 --> 00:56:46.790
<v Speaker 3>So I think across like different
industries, different customers that we have,

1078
00:56:46.870 --> 00:56:51.979
<v Speaker 3>they've saved so much money on travel
costs alone because they don't have to go to

1079
00:56:51.979 --> 00:56:52.469
<v Speaker 3>the factory.

1080
00:56:52.580 --> 00:56:52.639
<v Speaker 3>Yeah,

1081
00:56:52.709 --> 00:56:53.780
<v Adam Poole>you can monitor it from anywhere.

1082
00:56:53.949 --> 00:56:57.169
<v Adam Poole>You might have had to send in specialist
people to monitor things.

1083
00:56:57.614 --> 00:56:59.864
<v Adam Poole>But that can all be done remotely now.

1084
00:57:00.104 --> 00:57:00.344
<v Adam Poole>Yeah,

1085
00:57:00.504 --> 00:57:01.104
<v Speaker 3>no, exactly.

1086
00:57:01.385 --> 00:57:06.254
<v Speaker 3>Well, like we, we said earlier about
having it all in one place, um, this is the

1087
00:57:06.254 --> 00:57:12.094
<v Speaker 3>real benefit of the application because
you can track and see what's going on, um,

1088
00:57:12.104 --> 00:57:16.635
<v Speaker 3>in real time and it's just very quick to
have on your smartphone.

1089
00:57:17.225 --> 00:57:17.334
<v Speaker 3>Yeah,

1090
00:57:17.385 --> 00:57:21.625
<v Adam Poole>and the way we tend to set things up is
like one customer, all their account, all

1091
00:57:21.625 --> 00:57:23.725
<v Adam Poole>their factories will be in the same
account.

1092
00:57:24.639 --> 00:57:29.699
<v Adam Poole>So you could share stuff like globally or
spot something in someone else's account

1093
00:57:30.120 --> 00:57:33.580
<v Adam Poole>that you're also responsible for and and
begin to highlight things globally.

1094
00:57:34.280 --> 00:57:38.469
<v Adam Poole>Or you might identify an issue in one
place, other particular, I always use

1095
00:57:38.469 --> 00:57:39.639
<v Adam Poole>gearboxes for some reason.

1096
00:57:40.120 --> 00:57:43.840
<v Adam Poole>This type of gearbox might have a
manufacturing issue and you know where you've got

1097
00:57:43.840 --> 00:57:46.870
<v Adam Poole>them, and you can head up that kind of
quality issue as well.

1098
00:57:47.320 --> 00:57:50.679
<v Adam Poole>So that's another side of it, the quality
side of things, which you might not spot

1099
00:57:50.679 --> 00:57:51.300
<v Adam Poole>any other way.

1100
00:57:52.389 --> 00:57:57.290
<v Adam Poole>Um, and other things we've spotted are
things like even environmental issues like

1101
00:57:58.149 --> 00:58:01.840
<v Adam Poole>certain factories are in like quite, you
know, changeable climates.

1102
00:58:02.669 --> 00:58:06.429
<v Adam Poole>You might have unexpected events like a,
we had one place we had a like a power

1103
00:58:06.429 --> 00:58:06.750
<v Adam Poole>surge.

1104
00:58:06.790 --> 00:58:11.790
<v Adam Poole>It was like a lightning strike on a, on a,
um, transformer outside, shut down the

1105
00:58:11.790 --> 00:58:12.090
<v Adam Poole>line.

1106
00:58:12.469 --> 00:58:16.030
<v Adam Poole>They didn't really know what had happened,
but then they can go in and see where it

1107
00:58:16.030 --> 00:58:20.050
<v Adam Poole>affects and understand the impact of it
like very quickly.

1108
00:58:20.699 --> 00:58:22.659
<v Adam Poole>And that's the kind of things we never
really anticipated.

1109
00:58:23.620 --> 00:58:28.060
<v Adam Poole>Um, ambient temperature changes, you might
have a heat wave that affects everything,

1110
00:58:28.159 --> 00:58:32.540
<v Adam Poole>but you can see a shift in how all the
machines are operating all at once, all in

1111
00:58:32.540 --> 00:58:33.340
<v Adam Poole>that one location.

1112
00:58:33.500 --> 00:58:36.800
<v Adam Poole>So that's kind of exposing things we never
expected.

1113
00:58:37.219 --> 00:58:42.570
<v Adam Poole>But it's also saved people, um, we've
prevented like We've got case studies of

1114
00:58:42.570 --> 00:58:46.370
<v Adam Poole>preventing issues from occurring like a
leakage, for which the company would be

1115
00:58:46.370 --> 00:58:50.969
<v Adam Poole>liable to environmental fines, all that
kind of thing, so it helps on that side as

1116
00:58:50.969 --> 00:58:51.350
<v Adam Poole>well.

1117
00:58:52.389 --> 00:58:55.260
<v Adam Poole>So these are kind of secondary things that
You can benefit from.

1118
00:58:56.159 --> 00:59:00.959
<v Speaker 3>Yeah, I mean, it's also kind of thinking
from a perspective of, like you said about,

1119
00:59:01.040 --> 00:59:05.409
<v Speaker 3>you know, anticipating changes is when it
comes to environmental.

1120
00:59:05.879 --> 00:59:09.739
<v Speaker 3>These are kind of issues that we probably
never imagined

1121
00:59:09.739 --> 00:59:12.239
<v Adam Poole>there are some unanticipated changes.

1122
00:59:12.320 --> 00:59:12.739
<v Adam Poole>Yeah.

1123
00:59:13.590 --> 00:59:18.280
<v Adam Poole>Um, events you, you might not even see
coming, but if you've got this network of

1124
00:59:18.280 --> 00:59:23.429
<v Adam Poole>connected devices and the whole internet
of things, there's all kinds of benefits.

1125
00:59:25.129 --> 00:59:25.729
<v Speaker 3>OK.

1126
00:59:26.750 --> 00:59:33.439
<v Speaker 3>OK, Adam, so we're coming towards the end
of this topic, um, and episode, and I

1127
00:59:33.439 --> 00:59:38.669
<v Speaker 3>think it's been so great to share a lot of
the advancements to the Sensor

1128
00:59:38.669 --> 00:59:44.419
<v Speaker 3>application, um, and understanding how
some of these, um, features work.

1129
00:59:44.820 --> 00:59:50.679
<v Speaker 3>Um, and what I wanted to do was just ask
you if you had any final takeaways just to

1130
00:59:50.679 --> 00:59:52.020
<v Speaker 3>share with our audience today.

1131
00:59:52.699 --> 00:59:57.260
<v Adam Poole>Yeah, well, we, we talked a lot about the
knowledge side of things and um I don't

1132
00:59:57.260 --> 01:00:01.020
<v Adam Poole>know, as the more we talked about it, the
more I realized how important a theme that

1133
01:00:01.020 --> 01:00:01.340
<v Adam Poole>is.

1134
01:00:02.060 --> 01:00:05.719
<v Adam Poole>And I think we always like to think of the
human angle.

1135
01:00:06.179 --> 01:00:11.550
<v Adam Poole>Um, people are worried about technology
replacing people, but As we've seen, you

1136
01:00:11.550 --> 01:00:15.070
<v Adam Poole>know, with an aging workfforce, it's not
about replacing people.

1137
01:00:15.110 --> 01:00:19.560
<v Adam Poole>It's actually just kind of continuing
their kind of legacy in the workforce in a

1138
01:00:19.560 --> 01:00:19.669
<v Adam Poole>way.

1139
01:00:19.709 --> 01:00:21.909
<v Adam Poole>I've seen it myself from when I was in
aerospace.

1140
01:00:21.949 --> 01:00:27.100
<v Adam Poole>I saw like engineers, like amazing
engineers who could do stuff firsthand with a

1141
01:00:27.100 --> 01:00:31.909
<v Adam Poole>piece of paper could like work out amazing
things about aircraft and that knowledge

1142
01:00:31.909 --> 01:00:35.209
<v Adam Poole>is as soon as they retire, that's
completely gone and you'll never get it back.

1143
01:00:35.570 --> 01:00:38.050
<v Adam Poole>And I think that's quite a tragic thing to
happen.

1144
01:00:38.649 --> 01:00:41.780
<v Adam Poole>So to think that, you know, we could help
that would be really cool.

1145
01:00:42.050 --> 01:00:46.830
<v Adam Poole>And I think there's a lot of um Pathways
that can go down that are really

1146
01:00:46.830 --> 01:00:51.149
<v Adam Poole>interesting if you get the right
engagement, um, and the right new people coming

1147
01:00:51.149 --> 01:00:55.010
<v Adam Poole>into the workforce with new ideas based on
these new technologies.

1148
01:00:55.590 --> 01:01:00.629
<v Adam Poole>There's a lot of directions that can go in
where, you know, knowledge isn't a

1149
01:01:00.629 --> 01:01:04.229
<v Adam Poole>threat, it's really helpful, um.

1150
01:01:04.949 --> 01:01:08.429
<v Adam Poole>And a lot of the industries, you know, we
work with are quite threatened, you know,

1151
01:01:08.550 --> 01:01:13.350
<v Adam Poole>we, we're always hearing about like, um,
steel manufacturers needing support or, you

1152
01:01:13.350 --> 01:01:14.979
<v Adam Poole>know, we still need these products.

1153
01:01:15.429 --> 01:01:20.510
<v Adam Poole>So we need to support these industries as
much as we can, um, with that knowledge

1154
01:01:20.510 --> 01:01:26.270
<v Adam Poole>and making sure those machines, which
could be decades old, still can continue to

1155
01:01:26.270 --> 01:01:26.679
<v Adam Poole>operate.

1156
01:01:27.189 --> 01:01:31.290
<v Adam Poole>So I think that's quite a nice human story
for this technology.

1157
01:01:31.629 --> 01:01:38.560
<v Adam Poole>Um, and You know, scale is always the huge
thing we, we talk about coming from a,

1158
01:01:38.709 --> 01:01:41.500
<v Adam Poole>you know, relatively small company and now
into Siemens.

1159
01:01:42.449 --> 01:01:44.469
<v Adam Poole>Seeing the benefits of the technology at
scale is.

1160
01:01:45.229 --> 01:01:48.659
<v Adam Poole>Where you can see real efficiencies and
we've talked about, we touched on the

1161
01:01:48.659 --> 01:01:51.909
<v Adam Poole>environmental side, which, you know, will
only become more important in the next

1162
01:01:51.909 --> 01:01:52.750
<v Adam Poole>decade or so.

1163
01:01:53.310 --> 01:01:58.719
<v Adam Poole>But also, um, You know, some of these
factories, you know, we're moving to like dark

1164
01:01:58.719 --> 01:02:01.139
<v Adam Poole>factories where there's not many people
operating them.

1165
01:02:01.600 --> 01:02:06.679
<v Adam Poole>And um, you want machines just operating
efficiently all the time and making the

1166
01:02:06.679 --> 01:02:08.959
<v Adam Poole>most use of their energy consumption as
well.

1167
01:02:09.360 --> 01:02:12.300
<v Adam Poole>So it's all, all of these factors coming,
coming into it.

1168
01:02:12.790 --> 01:02:13.300
<v Adam Poole>Um.

1169
01:02:14.070 --> 01:02:18.989
<v Adam Poole>So just understanding that Sensai as a
platform, you know, is really working to

1170
01:02:18.989 --> 01:02:23.629
<v Adam Poole>support those things and it's flexible,
and we're so flexible in the way that we

1171
01:02:23.629 --> 01:02:27.899
<v Adam Poole>develop things that even if another
amazing technology comes around in the next few

1172
01:02:27.899 --> 01:02:33.669
<v Adam Poole>months, you can guarantee we'd be all over
it and we'd be incorporating it as, well,

1173
01:02:33.790 --> 01:02:37.870
<v Adam Poole>proving it first is the important part,
but you know, moving to incorporate that as

1174
01:02:37.870 --> 01:02:38.310
<v Adam Poole>we go.

1175
01:02:38.760 --> 01:02:42.040
<v Adam Poole>And the things we've been working on, all
the co-pilot stuff we talked about that,

1176
01:02:42.330 --> 01:02:43.850
<v Adam Poole>that's not going to go away anytime soon.

1177
01:02:43.929 --> 01:02:48.489
<v Adam Poole>We're going to keep adding features and
working out the best use cases for it that

1178
01:02:48.489 --> 01:02:50.340
<v Adam Poole>really support users.

1179
01:02:50.610 --> 01:02:56.489
<v Adam Poole>And we talked about feedback, you know,
keep, keep that loop, really make stuff, um,

1180
01:02:57.469 --> 01:02:59.020
<v Adam Poole>To support what people would need.

1181
01:02:59.659 --> 01:03:00.739
<v Adam Poole>It's like, what are you missing?

1182
01:03:00.870 --> 01:03:02.639
<v Adam Poole>It's like, you know, what questions are
you asking?

1183
01:03:02.760 --> 01:03:06.520
<v Adam Poole>Like, what do you, one good question is
always like, what are you trying to do that

1184
01:03:06.520 --> 01:03:07.270
<v Adam Poole>you can't do?

1185
01:03:07.439 --> 01:03:11.239
<v Adam Poole>It's like, it's to find out where those
pinch points are and then put something in

1186
01:03:11.239 --> 01:03:13.020
<v Adam Poole>place where that just kind of goes away.

1187
01:03:13.800 --> 01:03:17.439
<v Adam Poole>And then, then they'll have another set
and another set and another set, but all the

1188
01:03:17.439 --> 01:03:18.620
<v Adam Poole>while we're improving things.

1189
01:03:19.739 --> 01:03:21.300
<v Adam Poole>So I think those are the key things I
think.

1190
01:03:21.419 --> 01:03:22.919
<v Adam Poole>Hopefully that's helpful for people.

1191
01:03:23.149 --> 01:03:24.280
<v Speaker 3>Yeah, very helpful.

1192
01:03:24.739 --> 01:03:29.879
<v Speaker 3>And just on your final point around users,
users are very integral to this process.

1193
01:03:30.340 --> 01:03:37.100
<v Speaker 3>Um, you know, like I said, from where
Sensei application was maybe a couple of

1194
01:03:37.100 --> 01:03:41.850
<v Speaker 3>years ago to now, it's incredible because
it's definitely, like I said, we've

1195
01:03:41.850 --> 01:03:45.189
<v Speaker 3>touched on these two words, flexibility
and efficiency.

1196
01:03:45.689 --> 01:03:50.770
<v Speaker 3>And I think that's what we will continue
to do aligned with trends and taking into

1197
01:03:50.770 --> 01:03:54.389
<v Speaker 3>account what users want and how we can
support them.

1198
01:03:55.260 --> 01:04:02.139
<v Adam Poole>Yeah, supporting their needs globally as
well, and I said, understanding the nuances

1199
01:04:02.139 --> 01:04:06.860
<v Adam Poole>of language, uh, understanding what's
needed kind of internationally as well is a

1200
01:04:06.860 --> 01:04:07.500
<v Adam Poole>big part of that.

1201
01:04:07.699 --> 01:04:09.239
<v Speaker 3>Yeah, perfect.

1202
01:04:09.510 --> 01:04:12.469
<v Speaker 3>Well, thank you so much for joining me on
today's episode.

1203
01:04:12.780 --> 01:04:18.899
<v Speaker 3>Um, it's been very insightful learning
about the evolution of Sensei and how it's

1204
01:04:18.899 --> 01:04:24.580
<v Speaker 3>developed and I'm looking forward to new,
um, advancements to the application.

1205
01:04:25.590 --> 01:04:32.429
<v Speaker 3>So actually, Adam, one final, final
question, and it's an interesting one and it's

1206
01:04:32.429 --> 01:04:37.669
<v Speaker 3>just taken into account previous episodes
that I've done with various guests and

1207
01:04:37.989 --> 01:04:39.870
<v Speaker 3>this question never seems to come up.

1208
01:04:39.959 --> 01:04:45.610
<v Speaker 3>So I'm gonna ask you myself, um, and it's
around what is your favorite color?

1209
01:04:47.780 --> 01:04:48.379
<v Adam Poole>That was unexpected.

1210
01:04:48.500 --> 01:04:50.379
<v Adam Poole>Um, I thought we were going to talk about
machines or something.

1211
01:04:51.909 --> 01:04:53.850
<v Adam Poole>Um, that's a funny one, isn't it?

1212
01:04:54.429 --> 01:05:00.030
<v Adam Poole>Weirdly, I'd say, um, yellow, but not
because I'm like wearing it.

1213
01:05:00.080 --> 01:05:02.989
<v Adam Poole>It's not a color I actually use, but I
really like it.

1214
01:05:03.030 --> 01:05:07.909
<v Adam Poole>I do a bit of landscape photography and
I'm also um a little bit color blind.

1215
01:05:08.540 --> 01:05:11.540
<v Adam Poole>So reds and greens kind of blend together
and greens and browns.

1216
01:05:11.659 --> 01:05:14.370
<v Adam Poole>So certain things aren't that meaningful
to me.

1217
01:05:14.719 --> 01:05:19.020
<v Adam Poole>Like I was like in a big field of poppies
and I'm like, that's all right.

1218
01:05:19.139 --> 01:05:21.840
<v Adam Poole>I can't, I can't really tell the red that
well.

1219
01:05:22.179 --> 01:05:24.500
<v Adam Poole>And people are like, why can't this place
is amazing.

1220
01:05:24.860 --> 01:05:27.439
<v Adam Poole>But then the other day I was in a field of
sunflowers.

1221
01:05:27.850 --> 01:05:29.250
<v Adam Poole>I'm like, this is the best place ever.

1222
01:05:29.300 --> 01:05:30.280
<v Adam Poole>This is amazing.

1223
01:05:30.620 --> 01:05:33.070
<v Adam Poole>And it's because of My perception of
color.

1224
01:05:33.189 --> 01:05:34.169
<v Adam Poole>So it's quite interesting.

1225
01:05:34.350 --> 01:05:35.870
<v Adam Poole>And I look back at a lot of photos I've
taken.

1226
01:05:35.909 --> 01:05:36.659
<v Adam Poole>I always like yellow.

1227
01:05:36.689 --> 01:05:37.810
<v Adam Poole>I like gorse flowers.

1228
01:05:37.870 --> 01:05:41.449
<v Adam Poole>I like daffodils and sunflowers and things
like that.

1229
01:05:41.870 --> 01:05:43.350
<v Adam Poole>And I like contrast as well.

1230
01:05:43.510 --> 01:05:44.250
<v Adam Poole>So I'm gonna say.

1231
01:05:45.040 --> 01:05:47.090
<v Adam Poole>Yellow for very personal reasons.

1232
01:05:47.239 --> 01:05:48.820
<v Speaker 3>I was going to mention daffodils.

1233
01:05:50.120 --> 01:05:50.550
<v Adam Poole>It's funny.

1234
01:05:50.600 --> 01:05:51.169
<v Adam Poole>It's funny.

1235
01:05:51.239 --> 01:05:54.659
<v Adam Poole>Um, and there's kind of colors I will
avoid as well.

1236
01:05:55.199 --> 01:05:58.590
<v Adam Poole>And it like, you know, the product we make
is not a particularly colorful one, but

1237
01:05:58.590 --> 01:05:59.610
<v Adam Poole>there is some yellow in there.

1238
01:06:00.129 --> 01:06:00.280
<v Speaker 3>A little bit.

1239
01:06:00.360 --> 01:06:01.060
<v Speaker 3>There's a little bit.

1240
01:06:01.239 --> 01:06:03.030
<v Speaker 3>Well, they say yellow is positivity.

1241
01:06:03.239 --> 01:06:03.750
<v Speaker 3>Yeah, exactly.

1242
01:06:04.000 --> 01:06:07.830
<v Adam Poole>Well, I associate with obviously spring
and summer, which are the best times of the

1243
01:06:07.830 --> 01:06:08.020
<v Adam Poole>year.

1244
01:06:08.120 --> 01:06:09.840
<v Adam Poole>So lots of good things.

1245
01:06:10.159 --> 01:06:10.899
<v Speaker 3>Oh, well, perfect.

1246
01:06:11.070 --> 01:06:12.179
<v Speaker 3>Thank you for sharing that.

1247
01:06:13.199 --> 01:06:17.399
<v Speaker 3>Thank you for watching this episode, and
please like and subscribe to all major

1248
01:06:17.399 --> 01:06:18.669
<v Speaker 3>podcast channels.

1249
01:06:19.000 --> 01:06:22.020
<v Speaker 3>To find out more information, please visit
Siemens.com.

1250
01:06:22.399 --> 01:06:22.959
<v Speaker 3>Thank you.

1251
01:06:25.290 --> 01:06:30.250
<v Speaker 2>Please like and subscribe on all major
podcast channels and find out more about

1252
01:06:30.250 --> 01:06:33.629
<v Speaker 2>Sensei predictive maintenance at
Siemens.com.
