WEBVTT

1
00:00:00.440 --> 00:00:04.000
<v Speaker 1>Extension two twenty four. Give her a call. That number

2
00:00:04.000 --> 00:00:08.359
<v Speaker 1>again is nine oh nine eight A nine eight three

3
00:00:08.519 --> 00:00:11.279
<v Speaker 1>seven seven extension two twenty four.

4
00:00:13.039 --> 00:00:15.800
<v Speaker 2>You're listening to the Inland Talk Express ten fifty AM

5
00:00:15.839 --> 00:00:19.199
<v Speaker 2>and one oh six point five FM CACAA, Loma, Linda.

6
00:00:20.000 --> 00:00:23.600
<v Speaker 3>The information economy has a rid. The world is teeming

7
00:00:23.640 --> 00:00:27.839
<v Speaker 3>with innovation as new business models reinvent every industry industry.

8
00:00:27.920 --> 00:00:32.240
<v Speaker 3>Inside Analysis is your source of information and insight about

9
00:00:32.280 --> 00:00:34.799
<v Speaker 3>how to make the most of this exciting new era.

10
00:00:35.079 --> 00:00:39.320
<v Speaker 3>Learn more at inside analysis dot Comsideanalysis dot com. And

11
00:00:39.399 --> 00:00:42.200
<v Speaker 3>now here's your host, Eric Kavanaugh.

12
00:00:46.799 --> 00:00:49.439
<v Speaker 4>All Right, ladies and gentlemen, Hello and welcome back once

13
00:00:49.479 --> 00:00:51.840
<v Speaker 4>again to the only coast to coast radio show that's

14
00:00:51.840 --> 00:00:55.039
<v Speaker 4>all about the information economy. It's time for Inside Analysis.

15
00:00:55.159 --> 00:00:58.119
<v Speaker 4>You're truly Eric Kavanaugh here, and I'm so excited to

16
00:00:58.159 --> 00:01:02.159
<v Speaker 4>be talking about engineering these days, engineering for success. And

17
00:01:02.439 --> 00:01:05.200
<v Speaker 4>what's one of the hot topics that we have, especially

18
00:01:05.239 --> 00:01:08.040
<v Speaker 4>with all these electric vehicles and hybrid vehicles these days,

19
00:01:08.359 --> 00:01:12.079
<v Speaker 4>are the batteries. And batteries of course are expensive, they're heavy.

20
00:01:12.560 --> 00:01:14.799
<v Speaker 4>We want them to run as long as humanly possible.

21
00:01:14.920 --> 00:01:17.319
<v Speaker 4>No one likes charging their batteries up people like using

22
00:01:17.319 --> 00:01:21.120
<v Speaker 4>their batteries, and certainly in the electric vehicle world, they

23
00:01:21.159 --> 00:01:24.120
<v Speaker 4>are crucially important. I mean, with a hybrid, you got gas.

24
00:01:24.159 --> 00:01:26.680
<v Speaker 4>With an electric vehicle, all you have is the electricity

25
00:01:26.719 --> 00:01:29.840
<v Speaker 4>and that's in the battery. It's very heavy, it's very expensive.

26
00:01:30.200 --> 00:01:32.239
<v Speaker 4>So what can we do to improve the performance of

27
00:01:32.280 --> 00:01:35.359
<v Speaker 4>these batteries. Well, guess what we've got. Jovanni Rossi calling

28
00:01:35.439 --> 00:01:37.480
<v Speaker 4>it all the way from Milan, Italy, my favorite country

29
00:01:37.519 --> 00:01:40.040
<v Speaker 4>in the world. I love Italy, and he is with

30
00:01:40.120 --> 00:01:43.640
<v Speaker 4>a company called Electra. They are leaders and applied AI

31
00:01:43.799 --> 00:01:48.319
<v Speaker 4>for battery packs. I'm like, what explain this? So, Giovanni,

32
00:01:48.400 --> 00:01:50.519
<v Speaker 4>welcome to the show. Tell us a bit about what

33
00:01:50.560 --> 00:01:53.200
<v Speaker 4>you folks are doing and how you're able to use

34
00:01:53.239 --> 00:01:57.159
<v Speaker 4>a digital twin of batteries to improve the performance, and

35
00:01:57.239 --> 00:01:59.719
<v Speaker 4>not just in the design phase, like meaning for the

36
00:01:59.760 --> 00:02:02.519
<v Speaker 4>next set of batteries to come on the market, but

37
00:02:02.640 --> 00:02:04.760
<v Speaker 4>for batteries that are already out there being used. Tell

38
00:02:04.799 --> 00:02:06.760
<v Speaker 4>us what Electra is and how you're doing this stuff.

39
00:02:07.760 --> 00:02:08.360
<v Speaker 5>Thank you, Eric.

40
00:02:08.439 --> 00:02:12.080
<v Speaker 6>So, Electra is an AI clintech and B to B

41
00:02:12.199 --> 00:02:15.319
<v Speaker 6>software company that is like focused to unlock the full

42
00:02:15.319 --> 00:02:19.199
<v Speaker 6>potential of Barry technology. So basically as was mentioning. We

43
00:02:19.240 --> 00:02:22.000
<v Speaker 6>have two different type of products. The first one is

44
00:02:22.039 --> 00:02:24.800
<v Speaker 6>like a digital tween applications, so we study the barries,

45
00:02:24.879 --> 00:02:27.360
<v Speaker 6>we understand what is happening, you know, between the berry

46
00:02:27.479 --> 00:02:30.879
<v Speaker 6>with having a virtual replica of the battery where you

47
00:02:30.960 --> 00:02:34.960
<v Speaker 6>can thanks to our software capability and AI models, test

48
00:02:35.199 --> 00:02:37.960
<v Speaker 6>and innovate with the berry, so you can insert your

49
00:02:37.960 --> 00:02:42.080
<v Speaker 6>different parameters. You can test out new chemistries or new

50
00:02:42.120 --> 00:02:45.479
<v Speaker 6>models what you want to do, what is necessary to

51
00:02:45.520 --> 00:02:48.520
<v Speaker 6>make a new berries, and so you can get faster

52
00:02:48.639 --> 00:02:51.680
<v Speaker 6>to your results. Basically, you know, when you need to

53
00:02:51.800 --> 00:02:54.319
<v Speaker 6>produce a new berries, it can take up to ten

54
00:02:54.400 --> 00:02:57.639
<v Speaker 6>years and cost like up to one billion dollars, and

55
00:02:57.680 --> 00:03:01.199
<v Speaker 6>so of course you need technology as ours to decrease

56
00:03:01.240 --> 00:03:03.840
<v Speaker 6>of course your time and also your cost into making

57
00:03:03.879 --> 00:03:04.520
<v Speaker 6>new berries.

58
00:03:05.000 --> 00:03:07.080
<v Speaker 5>On the other side, we also have a set of

59
00:03:07.120 --> 00:03:07.800
<v Speaker 5>software for.

60
00:03:07.840 --> 00:03:12.560
<v Speaker 6>Like you know, managing, optimizing and controlling very capabilities and

61
00:03:12.599 --> 00:03:16.479
<v Speaker 6>so improving again the performance of the berries and providing

62
00:03:16.560 --> 00:03:19.520
<v Speaker 6>valuable insights for the different type of users and for

63
00:03:19.599 --> 00:03:22.960
<v Speaker 6>the business managing these barries so to make the battery

64
00:03:23.120 --> 00:03:26.479
<v Speaker 6>lasts longer and perform better and so maximizing of course

65
00:03:26.520 --> 00:03:28.680
<v Speaker 6>the reternal investment for the battery assets.

66
00:03:29.840 --> 00:03:33.240
<v Speaker 4>Yeah, that's really interesting. So and let's talk first about

67
00:03:33.400 --> 00:03:37.560
<v Speaker 4>the digital twin and that environment where you have built

68
00:03:37.560 --> 00:03:42.280
<v Speaker 4>out in a computing environment. Obviously the battery itself, what

69
00:03:42.439 --> 00:03:46.000
<v Speaker 4>goes into it, and then you're able to allow your

70
00:03:46.439 --> 00:03:50.199
<v Speaker 4>engineers to play around with different settings. Is it getting

71
00:03:50.240 --> 00:03:52.520
<v Speaker 4>into the material science? Like how much detail can you

72
00:03:52.560 --> 00:03:55.319
<v Speaker 4>give us on what's done in that environment and how

73
00:03:55.360 --> 00:03:58.719
<v Speaker 4>you're enabling more efficient battery designs.

74
00:03:59.639 --> 00:04:03.400
<v Speaker 6>Ye, can go into more than one hundred parameters, you know,

75
00:04:03.479 --> 00:04:06.719
<v Speaker 6>into the very spects, so it can be either at

76
00:04:06.759 --> 00:04:08.680
<v Speaker 6>a cell level and so like you know, into the

77
00:04:08.719 --> 00:04:12.520
<v Speaker 6>small great stuff in that sense, into until like the

78
00:04:12.680 --> 00:04:14.840
<v Speaker 6>very pack. So it depends of course of what we

79
00:04:14.919 --> 00:04:18.160
<v Speaker 6>want to do. But we have different applications, different modules

80
00:04:18.160 --> 00:04:20.600
<v Speaker 6>in the platform, and so you can go sell to

81
00:04:20.720 --> 00:04:24.040
<v Speaker 6>pack to pack levels so that you can test and

82
00:04:24.079 --> 00:04:26.959
<v Speaker 6>innovate whatever is like necessary for you. Of course you

83
00:04:27.000 --> 00:04:30.240
<v Speaker 6>can change parameters. There are already some pre built AI

84
00:04:30.399 --> 00:04:33.319
<v Speaker 6>model that you know, we have already designed and tested

85
00:04:33.680 --> 00:04:36.639
<v Speaker 6>with different customers and understanding of course the trends in

86
00:04:36.680 --> 00:04:39.800
<v Speaker 6>the market. But then of course we can also create

87
00:04:39.879 --> 00:04:44.519
<v Speaker 6>some additional customized AI models to do some very specific

88
00:04:44.560 --> 00:04:46.360
<v Speaker 6>operation that a customer may be doing.

89
00:04:48.319 --> 00:04:51.720
<v Speaker 4>That's interesting. So with all these parameters, you're allowing the

90
00:04:51.800 --> 00:04:54.839
<v Speaker 4>scientists basically to get in there and just play around

91
00:04:54.839 --> 00:04:57.839
<v Speaker 4>with things and see about whether it's the kind of

92
00:04:57.839 --> 00:05:00.879
<v Speaker 4>materials that are used, how much of them are used,

93
00:05:01.040 --> 00:05:04.959
<v Speaker 4>all these different aspects of the actual design process. And

94
00:05:05.000 --> 00:05:08.279
<v Speaker 4>then in this digital twin world you can kind of

95
00:05:08.279 --> 00:05:11.480
<v Speaker 4>play around. Can you talk a bit about the accuracy,

96
00:05:11.720 --> 00:05:16.040
<v Speaker 4>like what, you know, what's the range of efficacy with

97
00:05:16.240 --> 00:05:19.120
<v Speaker 4>these tests when you do them in the digital twin

98
00:05:19.160 --> 00:05:21.759
<v Speaker 4>world and then you see what happens in the real world.

99
00:05:21.839 --> 00:05:24.600
<v Speaker 4>Is that something that you're capturing and managing over time

100
00:05:24.639 --> 00:05:25.439
<v Speaker 4>the data around that.

101
00:05:26.519 --> 00:05:28.839
<v Speaker 6>Yeah, I mean like you can play around with whatever

102
00:05:28.879 --> 00:05:30.920
<v Speaker 6>it's like, you know, within the platform of course, and

103
00:05:30.959 --> 00:05:35.279
<v Speaker 6>also adding some additional bodiles and piece when it is necessary.

104
00:05:35.800 --> 00:05:37.839
<v Speaker 5>And I think that the main benefit.

105
00:05:37.519 --> 00:05:39.399
<v Speaker 6>Here is like you know, when you need to test

106
00:05:39.560 --> 00:05:41.519
<v Speaker 6>out some berries, you know, and you can have this

107
00:05:41.720 --> 00:05:44.519
<v Speaker 6>digital replica and you can play around with it, you

108
00:05:44.560 --> 00:05:47.160
<v Speaker 6>can decrease the testing time, so you know that that

109
00:05:47.240 --> 00:05:50.560
<v Speaker 6>seems like a real deal. And the game changer perspective

110
00:05:50.600 --> 00:05:52.959
<v Speaker 6>that is, like you know, you don't need to have

111
00:05:53.120 --> 00:05:55.920
<v Speaker 6>like a lot of you know, physical testing, but you

112
00:05:55.959 --> 00:05:59.759
<v Speaker 6>can do everything virtually and this can go up to

113
00:06:00.160 --> 00:06:03.480
<v Speaker 6>you know, ninety percent of the testing can be reduced,

114
00:06:04.199 --> 00:06:06.920
<v Speaker 6>of course in the best case scenario, but we have

115
00:06:07.000 --> 00:06:09.639
<v Speaker 6>seen that an average can be of like reduction in

116
00:06:09.720 --> 00:06:13.199
<v Speaker 6>test is like sixty to seventy percent, so meaning that

117
00:06:13.279 --> 00:06:15.160
<v Speaker 6>of course you're saving up a lot of time and

118
00:06:15.160 --> 00:06:17.279
<v Speaker 6>also a lot of money, and so the scientists can

119
00:06:17.319 --> 00:06:20.800
<v Speaker 6>also focus on some more interesting stuff. Let's say this

120
00:06:20.879 --> 00:06:24.360
<v Speaker 6>way than just replicate the test over and over again.

121
00:06:26.279 --> 00:06:28.839
<v Speaker 4>You know, I remember talking to a gentleman, a very

122
00:06:28.959 --> 00:06:32.040
<v Speaker 4>very interesting guy. He is an electric car racer, and

123
00:06:32.480 --> 00:06:35.040
<v Speaker 4>we were over in Belgium for an electric car race

124
00:06:35.079 --> 00:06:37.360
<v Speaker 4>a couple of years ago, and he was talking about

125
00:06:37.680 --> 00:06:43.720
<v Speaker 4>this this effect when you float you can actually slowly

126
00:06:43.759 --> 00:06:46.360
<v Speaker 4>you can actually increase the energy in the battery a

127
00:06:46.399 --> 00:06:47.920
<v Speaker 4>little bit. Do you know about this? Like when you

128
00:06:47.959 --> 00:06:51.360
<v Speaker 4>break our cost in an EV, the electric motor access

129
00:06:51.439 --> 00:06:54.879
<v Speaker 4>kind of a generator converting the energy back into electrical energy.

130
00:06:54.920 --> 00:06:56.720
<v Speaker 4>Is that right correct?

131
00:06:56.959 --> 00:06:59.639
<v Speaker 5>Yeah? And you can say up plum energy and refiel

132
00:06:59.680 --> 00:07:00.560
<v Speaker 5>that of the marry.

133
00:07:00.639 --> 00:07:03.319
<v Speaker 4>Yeah, that's pretty cool. That's pretty cool stuff. And then

134
00:07:03.480 --> 00:07:07.279
<v Speaker 4>talk about the battery management systems I'm getting spanked by

135
00:07:07.279 --> 00:07:09.160
<v Speaker 4>the sunlight here in my head, but try not to

136
00:07:09.160 --> 00:07:12.639
<v Speaker 4>worry about that. Talk about how you can also work

137
00:07:12.680 --> 00:07:17.360
<v Speaker 4>with the management matteries I'm sorry, the battery management system

138
00:07:17.759 --> 00:07:19.600
<v Speaker 4>to improve performance there. What does that look like?

139
00:07:21.000 --> 00:07:24.959
<v Speaker 6>So basically, let's take the an electric vehicle as an example.

140
00:07:25.000 --> 00:07:28.319
<v Speaker 6>You know what you do right now, It's like you

141
00:07:28.439 --> 00:07:31.279
<v Speaker 6>have different information that are coming from the berries, coming

142
00:07:31.279 --> 00:07:34.120
<v Speaker 6>from the driving style, coming from the environments, and of

143
00:07:34.120 --> 00:07:36.800
<v Speaker 6>course all of these is like impacting the performance of

144
00:07:36.920 --> 00:07:37.360
<v Speaker 6>the battery.

145
00:07:37.480 --> 00:07:40.040
<v Speaker 5>So what we do is like we take all of.

146
00:07:39.920 --> 00:07:43.800
<v Speaker 6>These information together, so berries, environment, driving style, and we

147
00:07:43.879 --> 00:07:48.360
<v Speaker 6>put everything together, and thanks to our AI you know, algorithm,

148
00:07:48.600 --> 00:07:51.480
<v Speaker 6>we can provide an output to the users, to the

149
00:07:51.560 --> 00:07:55.279
<v Speaker 6>drivers in the sense that is like how you can optimize,

150
00:07:55.360 --> 00:07:58.959
<v Speaker 6>of course your range. You can so extend your range

151
00:07:59.600 --> 00:08:05.759
<v Speaker 6>in this sense we have been able to estimate that.

152
00:08:05.879 --> 00:08:11.240
<v Speaker 6>Of course, the reduction of sorry, the average error in

153
00:08:11.319 --> 00:08:14.040
<v Speaker 6>like you know, estimating the range is like twenty percent

154
00:08:14.560 --> 00:08:17.920
<v Speaker 6>fifteen to twenty percents depend on vehicles. And with our

155
00:08:18.000 --> 00:08:20.680
<v Speaker 6>model you can go down to less than one percent

156
00:08:20.879 --> 00:08:24.120
<v Speaker 6>error in estimating range. So this means that of course

157
00:08:24.279 --> 00:08:28.360
<v Speaker 6>you have much more precise information in that space, and

158
00:08:28.399 --> 00:08:31.399
<v Speaker 6>we also you know, and with additional insights and suggest

159
00:08:31.600 --> 00:08:34.399
<v Speaker 6>that we can provide, you can also extend the range

160
00:08:34.440 --> 00:08:38.480
<v Speaker 6>and the capabilities. We have actually been testing these very

161
00:08:38.519 --> 00:08:43.600
<v Speaker 6>recently in a cross country you know trip coming starting

162
00:08:43.600 --> 00:08:48.320
<v Speaker 6>from Boston to Vegas, because we were presenting our technology

163
00:08:48.320 --> 00:08:51.159
<v Speaker 6>at CS twenty thirty five, and we did it with

164
00:08:51.279 --> 00:08:54.720
<v Speaker 6>like a Tesla cybertruck. So our founder, a core founder

165
00:08:54.759 --> 00:08:58.600
<v Speaker 6>and CEO of Britain Martini, and one Copio drove all

166
00:08:58.600 --> 00:09:01.399
<v Speaker 6>the way down from Boston to Vegas to demonstrate the

167
00:09:01.440 --> 00:09:03.480
<v Speaker 6>capability for all our algorithms.

168
00:09:04.080 --> 00:09:04.799
<v Speaker 4>That's Alloyd.

169
00:09:05.240 --> 00:09:06.679
<v Speaker 5>Yeah, it's a very long drive.

170
00:09:06.840 --> 00:09:11.279
<v Speaker 6>They looked like seven days, so that's really intense sad

171
00:09:11.360 --> 00:09:13.639
<v Speaker 6>this way, and we have been able to you know,

172
00:09:13.679 --> 00:09:17.440
<v Speaker 6>showcase and demonstrate that we can extend the range of

173
00:09:17.519 --> 00:09:22.000
<v Speaker 6>twenty percent and reduce the charges of around thirty three percent.

174
00:09:22.759 --> 00:09:24.960
<v Speaker 5>That is pretty it's a pretty good number, we say.

175
00:09:25.519 --> 00:09:27.559
<v Speaker 6>And in all of these you know, also managing and

176
00:09:27.639 --> 00:09:31.320
<v Speaker 6>understanding all the data coming from the various environmental driving styles,

177
00:09:31.320 --> 00:09:35.240
<v Speaker 6>and of course we have also capability to predict failures

178
00:09:35.240 --> 00:09:37.519
<v Speaker 6>in advance, so we can have like in a product

179
00:09:37.519 --> 00:09:40.559
<v Speaker 6>that is like one hundred percent safe for of course

180
00:09:40.600 --> 00:09:44.320
<v Speaker 6>the driver and and for them of course vehicle producer

181
00:09:44.360 --> 00:09:47.080
<v Speaker 6>in that sense that is also very very interesting, and

182
00:09:47.360 --> 00:09:49.679
<v Speaker 6>all of these can be scaled when you think not

183
00:09:49.720 --> 00:09:52.879
<v Speaker 6>only you know individual drivers, but you have like fleets

184
00:09:53.000 --> 00:09:56.960
<v Speaker 6>of vehicles or flit of electric vehicles, you know, adding

185
00:09:57.000 --> 00:09:59.799
<v Speaker 6>all of these information and understanding what is happening within

186
00:09:59.840 --> 00:10:02.200
<v Speaker 6>the so of course, what is like the state of

187
00:10:02.240 --> 00:10:05.039
<v Speaker 6>hels of your battery, what is like the degradation of

188
00:10:05.120 --> 00:10:07.720
<v Speaker 6>your batteries, and so how much your btrier can stay

189
00:10:07.879 --> 00:10:10.879
<v Speaker 6>can last? You know, for what we define as the

190
00:10:10.879 --> 00:10:13.519
<v Speaker 6>remain a useful life of a battery, you can actually

191
00:10:13.600 --> 00:10:17.120
<v Speaker 6>increase the value of your asset up to forty percent.

192
00:10:18.080 --> 00:10:20.840
<v Speaker 6>So that is like a way for both the drivers,

193
00:10:21.120 --> 00:10:23.240
<v Speaker 6>the OEM or the battery producer. And then you know,

194
00:10:23.360 --> 00:10:28.279
<v Speaker 6>the fleet operators to have many information, many sites and

195
00:10:28.639 --> 00:10:33.559
<v Speaker 6>so have a much better capability to manage the operations

196
00:10:33.600 --> 00:10:36.240
<v Speaker 6>and so of course get the value out of it.

197
00:10:37.120 --> 00:10:39.720
<v Speaker 4>Yeah, well for sure. So I'm guessing what you're doing

198
00:10:39.879 --> 00:10:43.679
<v Speaker 4>here is in terms of being able to optimize the

199
00:10:43.679 --> 00:10:49.440
<v Speaker 4>battery life is you're you're analyzing the driving behavior. So

200
00:10:49.559 --> 00:10:52.559
<v Speaker 4>does this person accelerate very quickly the drive? It very

201
00:10:52.600 --> 00:10:55.080
<v Speaker 4>high speeds on a regular basis, do they go up

202
00:10:55.120 --> 00:10:57.679
<v Speaker 4>and down often in terms of speed. These sorts of

203
00:10:58.120 --> 00:11:01.480
<v Speaker 4>variations will have an impact on the battery life, and

204
00:11:01.559 --> 00:11:05.600
<v Speaker 4>so what you can probably do is detect those algorithmically,

205
00:11:05.720 --> 00:11:10.000
<v Speaker 4>understand what's really happening, and then give some recommendations to

206
00:11:10.039 --> 00:11:12.519
<v Speaker 4>the user to say, hey, maybe if you were to

207
00:11:12.519 --> 00:11:15.360
<v Speaker 4>not speed up and slow down so quickly, you would

208
00:11:15.360 --> 00:11:17.720
<v Speaker 4>extend I'm just guessing here that you know, if you

209
00:11:17.799 --> 00:11:21.159
<v Speaker 4>haven't even keel drive, you're going to get better use

210
00:11:21.240 --> 00:11:22.200
<v Speaker 4>of the battery.

211
00:11:21.879 --> 00:11:24.759
<v Speaker 6>Right, yes, and your mattery can last longer because it's

212
00:11:24.799 --> 00:11:28.159
<v Speaker 6>not allly about range and performance, but it's like you know,

213
00:11:28.240 --> 00:11:30.600
<v Speaker 6>if you drive better that sense, so if you use

214
00:11:30.639 --> 00:11:34.919
<v Speaker 6>it battery better, your barrier can last for longer. Of course,

215
00:11:35.000 --> 00:11:38.639
<v Speaker 6>we have some algorithms like optimizing how much the bettery

216
00:11:38.720 --> 00:11:41.039
<v Speaker 6>can last. But of course then in this case, of

217
00:11:41.120 --> 00:11:44.360
<v Speaker 6>course also the users like responsible of that. So you know,

218
00:11:44.519 --> 00:11:47.600
<v Speaker 6>the two things combined that is like what can make

219
00:11:47.639 --> 00:11:50.679
<v Speaker 6>you very lasts longer? And if you very lasts longer,

220
00:11:51.159 --> 00:11:53.080
<v Speaker 6>you know, it means that you are keeping your cart

221
00:11:53.159 --> 00:11:56.639
<v Speaker 6>longer in a way, and that's also saving money in

222
00:11:56.679 --> 00:12:00.039
<v Speaker 6>a sense, but also results of some environmental impact that

223
00:12:00.200 --> 00:12:03.360
<v Speaker 6>is definitely important in this sense. And of course you

224
00:12:03.360 --> 00:12:06.120
<v Speaker 6>can scale these not only to electric vehicles, but if

225
00:12:06.120 --> 00:12:09.320
<v Speaker 6>you think also stationary storage, that is like another application,

226
00:12:09.519 --> 00:12:11.720
<v Speaker 6>usually much more for B to B side, let's say

227
00:12:11.720 --> 00:12:14.360
<v Speaker 6>this way of leg for businesses, but it's also becoming

228
00:12:14.639 --> 00:12:20.080
<v Speaker 6>quite popular for homes, especially you know, mentioning you know

229
00:12:20.159 --> 00:12:22.039
<v Speaker 6>the B two B side, or like businesses, when you

230
00:12:22.039 --> 00:12:25.840
<v Speaker 6>have some solar farms or wind farms and you want

231
00:12:25.879 --> 00:12:28.399
<v Speaker 6>to store the excess of energy because you know, renewable

232
00:12:28.440 --> 00:12:31.639
<v Speaker 6>energy is very cool, but you know the shine and

233
00:12:32.120 --> 00:12:35.480
<v Speaker 6>the sun, sorry, it is not always shining and the

234
00:12:35.519 --> 00:12:38.399
<v Speaker 6>wind is not always ploying, so you need to you know,

235
00:12:38.480 --> 00:12:41.039
<v Speaker 6>to store the energy when when you have the excess

236
00:12:41.159 --> 00:12:44.399
<v Speaker 6>of energy and then release it into the grid. And

237
00:12:44.440 --> 00:12:49.279
<v Speaker 6>so having technological capabilities and aid I driven capability to

238
00:12:49.360 --> 00:12:52.600
<v Speaker 6>understand what is happening in these berries, to manage them

239
00:12:52.639 --> 00:12:55.480
<v Speaker 6>better and to optimize them, and also to predict falls

240
00:12:55.840 --> 00:12:58.600
<v Speaker 6>because you know, having all of these information and it

241
00:12:58.639 --> 00:13:01.759
<v Speaker 6>is one of the main game change capability about what

242
00:13:01.799 --> 00:13:04.320
<v Speaker 6>technology is that we can predict falls up to three

243
00:13:04.360 --> 00:13:07.120
<v Speaker 6>months in advance. So this means that we can understand

244
00:13:07.200 --> 00:13:09.399
<v Speaker 6>what is actually happening, and you know how your berry

245
00:13:09.440 --> 00:13:11.840
<v Speaker 6>is performing, and if you're going to have some critical faults,

246
00:13:11.919 --> 00:13:13.759
<v Speaker 6>and when I mean criptical faults is like you know

247
00:13:14.559 --> 00:13:17.799
<v Speaker 6>them a runaway or like fires or some other issue

248
00:13:17.799 --> 00:13:20.720
<v Speaker 6>with a very that's very very important to maintain safety

249
00:13:20.759 --> 00:13:22.279
<v Speaker 6>and reliability of that asset.

250
00:13:23.039 --> 00:13:24.960
<v Speaker 4>Yeah, no, that that's very interesting. And there are also

251
00:13:25.000 --> 00:13:28.519
<v Speaker 4>these power walls, right, doesn't Tesla don't they have a

252
00:13:28.559 --> 00:13:30.720
<v Speaker 4>power wall? So basically you can buy a car, but

253
00:13:30.759 --> 00:13:33.200
<v Speaker 4>you also buy this wall that is like in your house,

254
00:13:33.759 --> 00:13:36.759
<v Speaker 4>and it's it's it is a long term battery storage

255
00:13:36.840 --> 00:13:37.759
<v Speaker 4>is what it boils down to.

256
00:13:37.879 --> 00:13:38.039
<v Speaker 5>Right.

257
00:13:38.080 --> 00:13:40.000
<v Speaker 4>It allows you to I'm guessing to charge the car

258
00:13:40.120 --> 00:13:42.360
<v Speaker 4>faster and do things of this nature. Yeah, you also

259
00:13:42.440 --> 00:13:45.039
<v Speaker 4>just have a power source, like you mentioned, because I

260
00:13:45.639 --> 00:13:48.720
<v Speaker 4>looked into solar panels years ago when we were in Texas,

261
00:13:49.159 --> 00:13:51.039
<v Speaker 4>and you know, some of the key things you have

262
00:13:51.080 --> 00:13:54.440
<v Speaker 4>to keep in mind are being able to manage that

263
00:13:54.559 --> 00:13:56.759
<v Speaker 4>power that comes in and storage such that at a

264
00:13:56.840 --> 00:13:59.320
<v Speaker 4>certain point you can then pump it back into the grid, right,

265
00:13:59.360 --> 00:14:01.039
<v Speaker 4>which is you know, you have to be very delicate

266
00:14:01.080 --> 00:14:04.000
<v Speaker 4>about that obviously, because it's electrical energy. You don't want

267
00:14:04.039 --> 00:14:06.519
<v Speaker 4>to to get too much So what are you able

268
00:14:06.559 --> 00:14:10.279
<v Speaker 4>to do there in terms of understanding the sort of

269
00:14:10.360 --> 00:14:14.159
<v Speaker 4>dynamics of how battery usage works in these walls, and like,

270
00:14:14.279 --> 00:14:16.720
<v Speaker 4>can you I presume you can extend their life too, right.

271
00:14:17.360 --> 00:14:18.759
<v Speaker 5>Correct, we can extend the life.

272
00:14:18.759 --> 00:14:22.039
<v Speaker 6>You can monitor them of course better and especially understanding

273
00:14:22.360 --> 00:14:27.080
<v Speaker 6>how they are performing and increase their again performance and

274
00:14:27.159 --> 00:14:30.080
<v Speaker 6>optimizing them so that you can have like more energy

275
00:14:30.120 --> 00:14:34.480
<v Speaker 6>to use in that sense, and charging faster your car

276
00:14:34.519 --> 00:14:36.240
<v Speaker 6>if it is a car for application for a car,

277
00:14:36.480 --> 00:14:39.159
<v Speaker 6>or like you know, managing better d energy for your home.

278
00:14:39.840 --> 00:14:42.519
<v Speaker 6>Optimizing of course also the a flow of energy because

279
00:14:42.600 --> 00:14:44.399
<v Speaker 6>usually you have pav panels and so you want to

280
00:14:44.440 --> 00:14:47.639
<v Speaker 6>have everything that is working in a very optimized way.

281
00:14:48.960 --> 00:14:52.360
<v Speaker 4>That's very interesting. So do you get much traction in

282
00:14:52.360 --> 00:14:54.720
<v Speaker 4>that space, or maybe talk a bit about your clients

283
00:14:54.759 --> 00:14:57.159
<v Speaker 4>who's using this right now? To what effect?

284
00:14:57.159 --> 00:14:57.360
<v Speaker 5>I mean?

285
00:14:57.360 --> 00:15:00.679
<v Speaker 4>Obviously it's you're just extending the life of this asset,

286
00:15:01.159 --> 00:15:03.519
<v Speaker 4>and you're improving the use of this asset, which is

287
00:15:03.559 --> 00:15:08.639
<v Speaker 4>incredibly valuable and saves money and also saves you on trouble,

288
00:15:09.120 --> 00:15:12.000
<v Speaker 4>especially this part about being able to predict fires, because

289
00:15:12.039 --> 00:15:14.840
<v Speaker 4>that is the one real big downside, it seems to

290
00:15:14.879 --> 00:15:17.679
<v Speaker 4>me of this whole paradigm is that these things can

291
00:15:17.720 --> 00:15:19.919
<v Speaker 4>get too hot and just blow up and that there's

292
00:15:19.960 --> 00:15:24.080
<v Speaker 4>no bueno, right, so what can you do happen? Yeah, so.

293
00:15:26.000 --> 00:15:28.840
<v Speaker 6>We I mean like thanks to the technology that that

294
00:15:29.039 --> 00:15:32.600
<v Speaker 6>is like a new layer I would say about understanding

295
00:15:32.639 --> 00:15:35.720
<v Speaker 6>better these assets and using them better. I think that

296
00:15:35.799 --> 00:15:38.080
<v Speaker 6>you know right now that are the right technology and

297
00:15:38.120 --> 00:15:42.399
<v Speaker 6>also the artificial intelligence and machine learning capabilities to better

298
00:15:42.480 --> 00:15:46.320
<v Speaker 6>understand how to again manage and optimize these assets.

299
00:15:46.960 --> 00:15:48.600
<v Speaker 5>That will be also.

300
00:15:48.519 --> 00:15:51.360
<v Speaker 6>You know, well we'll have we will have so much

301
00:15:51.639 --> 00:15:54.600
<v Speaker 6>a broader adoption of these assets. And so this will

302
00:15:54.639 --> 00:15:58.639
<v Speaker 6>also change the paradigm of how we think at energy

303
00:15:58.759 --> 00:16:01.279
<v Speaker 6>in general and also the all the energy transition and

304
00:16:01.320 --> 00:16:04.200
<v Speaker 6>everything is based on this because of course it's not

305
00:16:04.240 --> 00:16:06.480
<v Speaker 6>only again the renewables, but you also need some other

306
00:16:06.840 --> 00:16:09.879
<v Speaker 6>components to make this happen and also to sustain a

307
00:16:10.000 --> 00:16:15.000
<v Speaker 6>much lower environmental impact, and so all of these will

308
00:16:15.000 --> 00:16:19.720
<v Speaker 6>be much more necessary, especially technological side, for like making

309
00:16:19.759 --> 00:16:23.240
<v Speaker 6>this transition you know, a reality. And if you think

310
00:16:23.799 --> 00:16:26.039
<v Speaker 6>out the grid right now is like you know configure

311
00:16:26.080 --> 00:16:28.720
<v Speaker 6>for instance, you know and you have like you know,

312
00:16:28.919 --> 00:16:32.080
<v Speaker 6>the traditional system in the western countries, like you have

313
00:16:32.200 --> 00:16:34.720
<v Speaker 6>big plants where you produce the energy and then it's

314
00:16:35.080 --> 00:16:38.519
<v Speaker 6>distributed to like you know, to the grid, to different facilities.

315
00:16:38.559 --> 00:16:42.240
<v Speaker 6>That is like off taking the energy right now with

316
00:16:42.480 --> 00:16:46.000
<v Speaker 6>having you know, solar farms, wind farms and also you

317
00:16:46.039 --> 00:16:50.440
<v Speaker 6>know BV panels in like domestic and business facility, so

318
00:16:50.519 --> 00:16:52.200
<v Speaker 6>like for reastance on your rooftop or like you know,

319
00:16:52.200 --> 00:16:55.720
<v Speaker 6>in some olar situations, you basically are changing this perspective

320
00:16:55.759 --> 00:16:58.720
<v Speaker 6>and changing the paradigm of how the energy flows are

321
00:16:58.759 --> 00:17:02.200
<v Speaker 6>actually you know, pumping in energy into the grid. And

322
00:17:02.240 --> 00:17:06.000
<v Speaker 6>so you need again capabilities technological capabilities to keep everything

323
00:17:06.200 --> 00:17:11.319
<v Speaker 6>working and running smoothly and also to have additional benefit

324
00:17:11.400 --> 00:17:12.960
<v Speaker 6>to all the users involved.

325
00:17:13.400 --> 00:17:15.119
<v Speaker 4>What's next? What are you guys working on now that

326
00:17:15.160 --> 00:17:16.759
<v Speaker 4>we can expect in like a year or so. What's

327
00:17:16.759 --> 00:17:19.240
<v Speaker 4>the next big push for you? Oh?

328
00:17:19.319 --> 00:17:21.680
<v Speaker 6>I cannot share that I would like to, but that's

329
00:17:21.680 --> 00:17:24.599
<v Speaker 6>a good Yeah, that's pretty funny.

330
00:17:25.880 --> 00:17:28.960
<v Speaker 5>It is like yeah, yeah, I mean I can share.

331
00:17:28.960 --> 00:17:31.119
<v Speaker 6>It's like, you know, we are implementing day after day

332
00:17:31.359 --> 00:17:34.559
<v Speaker 6>our models and you know, understanding what are the new

333
00:17:34.960 --> 00:17:38.480
<v Speaker 6>needs of the customer. And I think the most important

334
00:17:38.480 --> 00:17:40.480
<v Speaker 6>stuff this is also part of my job is like

335
00:17:40.559 --> 00:17:43.480
<v Speaker 6>getting ahead of the curve. So it's like what trends

336
00:17:43.599 --> 00:17:46.039
<v Speaker 6>are going to be there in the next six, twelve,

337
00:17:46.160 --> 00:17:49.279
<v Speaker 6>eighteen months and what we can do to address those

338
00:17:49.319 --> 00:17:51.759
<v Speaker 6>in advanced So one of the things that we've always

339
00:17:51.799 --> 00:17:54.799
<v Speaker 6>been able so is like understanding the trends before they

340
00:17:54.799 --> 00:17:58.039
<v Speaker 6>happen and you know, getting something out before that moment

341
00:17:58.079 --> 00:17:59.559
<v Speaker 6>so that we be leading.

342
00:18:01.680 --> 00:18:05.119
<v Speaker 4>Well, this is fantastic. And the company is Elektra. That

343
00:18:05.160 --> 00:18:07.160
<v Speaker 4>are you based in Italy or you're just in Italy?

344
00:18:07.200 --> 00:18:08.240
<v Speaker 4>It's a company based in Italy.

345
00:18:08.359 --> 00:18:11.839
<v Speaker 6>No, the company is based in Boston, Massachusetts, so the

346
00:18:11.880 --> 00:18:14.920
<v Speaker 6>main edportter is there and then we also second European

347
00:18:14.960 --> 00:18:16.599
<v Speaker 6>headquarter into in Italy.

348
00:18:17.480 --> 00:18:21.240
<v Speaker 4>Excellent, Well, that sounds going to be great, great, great,

349
00:18:21.599 --> 00:18:24.440
<v Speaker 4>great information, great content. I love what you guys are doing.

350
00:18:24.519 --> 00:18:26.799
<v Speaker 4>Very cool. Look these guys up, Giovanni Rossi of Elektra.

351
00:18:26.960 --> 00:18:34.839
<v Speaker 4>We'll be right back. You're listening to Inside Analysis.

352
00:18:37.359 --> 00:18:42.319
<v Speaker 3>Welcome back to Inside Analysis. Here's your host, Eric Tavanaugh.

353
00:18:45.039 --> 00:18:47.799
<v Speaker 4>All right, folks back here on Inside Analysis. Your host here,

354
00:18:47.880 --> 00:18:50.559
<v Speaker 4>Eric Kavanaugh, and I'm very pleased to have another guest

355
00:18:50.640 --> 00:18:53.319
<v Speaker 4>with us today. Timothy Baines is the founder of a

356
00:18:53.319 --> 00:18:57.519
<v Speaker 4>company called Compatio, doing really interesting stuff they've built a

357
00:18:57.559 --> 00:19:02.200
<v Speaker 4>whole platform for you could say configure price quote. Really

358
00:19:02.279 --> 00:19:07.079
<v Speaker 4>it's a platform for managing compatibility hence the name of

359
00:19:07.160 --> 00:19:11.519
<v Speaker 4>different products. So think electrical engineering or building materials, or

360
00:19:11.720 --> 00:19:14.079
<v Speaker 4>anytime you need to bring a bunch of big pieces

361
00:19:14.079 --> 00:19:17.559
<v Speaker 4>and parts together to create some whole like I think

362
00:19:17.599 --> 00:19:21.119
<v Speaker 4>a car, for example, or any kind of complex machinery.

363
00:19:21.519 --> 00:19:24.160
<v Speaker 4>You need to know are these parts compatible, do they

364
00:19:24.240 --> 00:19:28.039
<v Speaker 4>work together? And then understand pricing and be able to

365
00:19:28.079 --> 00:19:30.400
<v Speaker 4>figure out what to charge for these things. And they

366
00:19:30.400 --> 00:19:33.119
<v Speaker 4>have a whole platform that does that, and they're focused

367
00:19:33.160 --> 00:19:34.680
<v Speaker 4>on a couple of markets, but they can do all

368
00:19:34.759 --> 00:19:37.680
<v Speaker 4>kinds of different stuff. But Timothy, what really struck my

369
00:19:37.880 --> 00:19:42.400
<v Speaker 4>interest here is you mentioned this taxonomy, and if you would,

370
00:19:42.440 --> 00:19:44.519
<v Speaker 4>can you tell us what you mean by a taxonomy

371
00:19:44.519 --> 00:19:47.039
<v Speaker 4>and how does that fit into what Campatio does.

372
00:19:48.160 --> 00:19:51.480
<v Speaker 7>Yeah, sure, Eric, So, first of all, I think it's

373
00:19:51.920 --> 00:19:53.960
<v Speaker 7>important to understand that at the core, at the heart

374
00:19:53.960 --> 00:19:57.720
<v Speaker 7>of our system is essentially a knowledge graph, and that

375
00:19:57.799 --> 00:20:02.240
<v Speaker 7>knowledge graph sits on top of a decision taxonomy that

376
00:20:02.480 --> 00:20:06.440
<v Speaker 7>within a given industry, let's say electrical switch gear for example,

377
00:20:06.559 --> 00:20:11.799
<v Speaker 7>or industrial automation components, we have a very precise set

378
00:20:11.839 --> 00:20:16.319
<v Speaker 7>of categories as far as what components are what, along

379
00:20:16.400 --> 00:20:24.039
<v Speaker 7>with very high quality and very carefully engineered attributes on

380
00:20:24.200 --> 00:20:29.319
<v Speaker 7>the products as well as product catalogs for different manufacturers.

381
00:20:29.359 --> 00:20:32.799
<v Speaker 7>So together the taxonomy which is the categories and the attributes,

382
00:20:33.200 --> 00:20:35.359
<v Speaker 7>as well as the rules on what the attributes are

383
00:20:35.359 --> 00:20:37.759
<v Speaker 7>allowed to be, what data type, what is the range

384
00:20:37.960 --> 00:20:40.960
<v Speaker 7>or even what is the picklist of values, that comprises

385
00:20:41.000 --> 00:20:44.799
<v Speaker 7>the taxonomy, and then that gets hooked up to catalogs

386
00:20:44.839 --> 00:20:49.960
<v Speaker 7>of products, and together those feed into our larger sort

387
00:20:50.000 --> 00:20:52.759
<v Speaker 7>of layers of logic that is essentially a knowledge graph.

388
00:20:53.720 --> 00:20:53.960
<v Speaker 5>Yeah.

389
00:20:54.000 --> 00:20:56.839
<v Speaker 4>And the reason why that's important for our audience out

390
00:20:56.839 --> 00:21:00.480
<v Speaker 4>there listening is that when you have this graph and

391
00:21:00.519 --> 00:21:06.440
<v Speaker 4>you have this ontology, you are cataloging all these myriad

392
00:21:06.480 --> 00:21:09.319
<v Speaker 4>parts of which there can be millions of different ones,

393
00:21:09.799 --> 00:21:13.799
<v Speaker 4>in such a way as to facilitate the alignment over time.

394
00:21:14.160 --> 00:21:17.039
<v Speaker 4>Because if you were to try to manually put those

395
00:21:17.039 --> 00:21:20.720
<v Speaker 4>into a just traditional relational database or something, first of all,

396
00:21:20.759 --> 00:21:22.799
<v Speaker 4>it would take forever a day, and second of all,

397
00:21:22.839 --> 00:21:24.920
<v Speaker 4>it would not be performed at all, it would be

398
00:21:25.039 --> 00:21:28.319
<v Speaker 4>very very slow, very painful. So by going this route

399
00:21:28.319 --> 00:21:33.119
<v Speaker 4>of having a graph, a knowledge graph substrate with ontologies

400
00:21:33.160 --> 00:21:36.960
<v Speaker 4>for particular industries or disciplines, if you will, you're really

401
00:21:37.000 --> 00:21:41.759
<v Speaker 4>facilitating the end use of this whole system to allow

402
00:21:41.839 --> 00:21:44.799
<v Speaker 4>people to compare and contrast and figure out do these

403
00:21:44.799 --> 00:21:48.200
<v Speaker 4>parts work together or not. That's very very clever. And

404
00:21:48.279 --> 00:21:51.640
<v Speaker 4>you built the graph yourself, You popular this graph. Can

405
00:21:51.640 --> 00:21:54.319
<v Speaker 4>you talk about some examples of how the graph and

406
00:21:54.359 --> 00:21:57.200
<v Speaker 4>the ontologies facilitate what your end users want?

407
00:21:58.200 --> 00:22:01.759
<v Speaker 7>Yeah, absolutely, so if you think about well, if you

408
00:22:01.759 --> 00:22:05.279
<v Speaker 7>think about any type of product that's available at scale,

409
00:22:05.440 --> 00:22:07.720
<v Speaker 7>sort of on a large e commerce site, let's say

410
00:22:08.359 --> 00:22:13.599
<v Speaker 7>all products need to have effective attribution and descriptions to

411
00:22:13.720 --> 00:22:17.279
<v Speaker 7>power search. So that's kind of a fundamental use case.

412
00:22:18.440 --> 00:22:22.559
<v Speaker 7>But when we get into more complex verticals, more complex

413
00:22:22.599 --> 00:22:28.759
<v Speaker 7>product domains, where the attributes the specifications of the products

414
00:22:28.799 --> 00:22:31.759
<v Speaker 7>need to be very very precise, you need an entirely

415
00:22:31.799 --> 00:22:36.559
<v Speaker 7>different level of quality and accuracy on those attributes. And

416
00:22:36.640 --> 00:22:40.680
<v Speaker 7>the use cases that that powers are things like search.

417
00:22:40.960 --> 00:22:44.160
<v Speaker 7>But you know search, including parametric search, right, so you

418
00:22:44.160 --> 00:22:47.079
<v Speaker 7>can filter down and find exactly what you want, so

419
00:22:47.839 --> 00:22:51.400
<v Speaker 7>any kind of discovery. But then the higher order logic

420
00:22:51.599 --> 00:22:56.559
<v Speaker 7>that also that that enables in the domains where we

421
00:22:56.680 --> 00:23:03.599
<v Speaker 7>operate the products are complicated. Finding the right product for

422
00:23:03.720 --> 00:23:07.680
<v Speaker 7>your specific application. Even just a single component can be

423
00:23:07.799 --> 00:23:11.720
<v Speaker 7>non trivial, and oftentimes you may need to talk with

424
00:23:11.759 --> 00:23:13.759
<v Speaker 7>an expert, let's say, that can help you figure out

425
00:23:13.799 --> 00:23:16.559
<v Speaker 7>what the right product is. And then if you think

426
00:23:16.559 --> 00:23:19.160
<v Speaker 7>about a product that is part of a larger system,

427
00:23:19.240 --> 00:23:22.759
<v Speaker 7>an industrial automation system with a motor and a motor

428
00:23:22.799 --> 00:23:25.440
<v Speaker 7>controller and a relay and so forth, at all need

429
00:23:25.519 --> 00:23:29.720
<v Speaker 7>to go together to be able to identify those components

430
00:23:29.960 --> 00:23:32.359
<v Speaker 7>number one that fit your application and the number two

431
00:23:32.519 --> 00:23:39.519
<v Speaker 7>go together. That's non trivial, and historically that task has

432
00:23:39.559 --> 00:23:43.000
<v Speaker 7>been handled by experts, folks with ten twenty thirty forty

433
00:23:43.079 --> 00:23:45.960
<v Speaker 7>years of experience in that industry, and you'd walk to

434
00:23:46.039 --> 00:23:49.720
<v Speaker 7>the counter and a distributor, a dealer, a store, or

435
00:23:49.759 --> 00:23:51.839
<v Speaker 7>they'd come to your plant and they'd have all the

436
00:23:51.880 --> 00:23:54.039
<v Speaker 7>expertise that's needed to help you speck it out. But

437
00:23:54.119 --> 00:23:59.279
<v Speaker 7>things are going online. Obviously, digital commerce is expanding, and

438
00:23:59.359 --> 00:24:03.519
<v Speaker 7>we also are seeing some fairly significant turnover in the

439
00:24:03.519 --> 00:24:06.119
<v Speaker 7>industry in terms of the labor force, where a lot

440
00:24:06.160 --> 00:24:08.720
<v Speaker 7>of the folks that came in twenty thirty forty years ago,

441
00:24:08.920 --> 00:24:12.599
<v Speaker 7>they're retiring their baby boomers and they're rolling out and

442
00:24:12.599 --> 00:24:15.799
<v Speaker 7>it's what our the companies that we're working with are

443
00:24:15.799 --> 00:24:18.160
<v Speaker 7>telling is it's hard to find the right people, and

444
00:24:18.200 --> 00:24:20.440
<v Speaker 7>it's hard to train them, and it's hard to retain them.

445
00:24:20.759 --> 00:24:25.599
<v Speaker 7>So we see really an emerging and a massive knowledge

446
00:24:25.680 --> 00:24:31.119
<v Speaker 7>gap coming into as digital commresce becomes more more prominent.

447
00:24:32.039 --> 00:24:36.440
<v Speaker 7>Combined with this problem of expertise, it makes it very

448
00:24:36.480 --> 00:24:39.319
<v Speaker 7>difficult to do these kinds of things to find the

449
00:24:39.400 --> 00:24:43.039
<v Speaker 7>right product fit your application, make sure they go together,

450
00:24:43.519 --> 00:24:45.160
<v Speaker 7>and then price them and quote them and get them

451
00:24:45.160 --> 00:24:47.839
<v Speaker 7>out the door. So we're addressing all of those use cases.

452
00:24:48.200 --> 00:24:51.640
<v Speaker 4>Yeah, it's really impressive. And when you talk about industrial

453
00:24:51.839 --> 00:24:57.119
<v Speaker 4>engineering the machines that make machines, basically you have years

454
00:24:57.160 --> 00:25:00.000
<v Speaker 4>on these things. Different models and things change your over year.

455
00:25:00.000 --> 00:25:03.119
<v Speaker 4>I mean, I'll use the metaphor of an automobile just

456
00:25:03.160 --> 00:25:05.319
<v Speaker 4>because most people have an automobile or at least know

457
00:25:05.400 --> 00:25:08.079
<v Speaker 4>someone who has an automobile, and depending upon the year

458
00:25:08.200 --> 00:25:12.359
<v Speaker 4>of that make, you'll get different parts for different functions,

459
00:25:12.400 --> 00:25:15.000
<v Speaker 4>like whether it's to run something in the engine or

460
00:25:15.000 --> 00:25:17.799
<v Speaker 4>in the electrical system or whatever, and it really matters

461
00:25:17.839 --> 00:25:19.680
<v Speaker 4>to get the right thing. I've been one of those

462
00:25:19.759 --> 00:25:21.839
<v Speaker 4>do it yourselfer as I've bought some products I think

463
00:25:21.880 --> 00:25:23.759
<v Speaker 4>it was going to fix, and it didn't fit the car.

464
00:25:23.839 --> 00:25:25.920
<v Speaker 4>I was like, oh man, because it was the wrong year.

465
00:25:26.359 --> 00:25:29.279
<v Speaker 4>So it's really important to have the year right to

466
00:25:29.440 --> 00:25:32.119
<v Speaker 4>make the model. And then all those attributes you talk

467
00:25:32.160 --> 00:25:36.279
<v Speaker 4>about are basically edges on the graph, right, So you're

468
00:25:36.319 --> 00:25:39.599
<v Speaker 4>able to capture all that and then maintain some history

469
00:25:39.640 --> 00:25:42.599
<v Speaker 4>and thus facilitate finding that one specific part that you

470
00:25:42.640 --> 00:25:43.839
<v Speaker 4>need to fix this machine.

471
00:25:43.920 --> 00:25:45.400
<v Speaker 5>Right, Yeah, that's right.

472
00:25:45.480 --> 00:25:50.720
<v Speaker 7>And you know, taking in a car and automobile as

473
00:25:50.759 --> 00:25:55.480
<v Speaker 7>an example, I mean that data is generally very carefully

474
00:25:55.519 --> 00:25:58.519
<v Speaker 7>maintained and curated by the manufacturer of that car. I

475
00:25:58.519 --> 00:26:01.640
<v Speaker 7>mean even some of the legally required that they maintain

476
00:26:01.920 --> 00:26:06.359
<v Speaker 7>that data for many types of things, for example liability

477
00:26:06.440 --> 00:26:09.519
<v Speaker 7>reasons and so forth. But where it gets really interesting

478
00:26:09.680 --> 00:26:12.640
<v Speaker 7>is where you, let's say, again keeping our focus on

479
00:26:12.680 --> 00:26:15.559
<v Speaker 7>a car, you get out to what goes on the

480
00:26:15.640 --> 00:26:18.200
<v Speaker 7>car or around the car, or attaches to the car,

481
00:26:18.319 --> 00:26:21.839
<v Speaker 7>or accessorizes the car. That data is not maintained by

482
00:26:21.839 --> 00:26:26.319
<v Speaker 7>the manufacturer. So when you get into these multi brand situations,

483
00:26:26.359 --> 00:26:30.000
<v Speaker 7>something that goes on or with something else, you're in

484
00:26:30.039 --> 00:26:33.519
<v Speaker 7>a space that really nobody owns. Right now, where nobody

485
00:26:33.559 --> 00:26:37.359
<v Speaker 7>owns that data what goes with what? Across brands, and

486
00:26:37.720 --> 00:26:42.079
<v Speaker 7>in the industries where we operate electrical automation, building materials,

487
00:26:42.119 --> 00:26:46.240
<v Speaker 7>and so forth, those problems are everywhere. Everywhere, folks are

488
00:26:46.240 --> 00:26:49.160
<v Speaker 7>trying to figure out what goes with what, especially when

489
00:26:49.160 --> 00:26:53.039
<v Speaker 7>it's cross brand, but even within a brand, it's still challenging. So, yeah,

490
00:26:53.079 --> 00:26:55.440
<v Speaker 7>the problem is huge, and the markets are huge. The

491
00:26:55.519 --> 00:26:59.079
<v Speaker 7>companies in the industries that have these kinds of issues

492
00:26:59.119 --> 00:27:02.720
<v Speaker 7>are huge. We're talking trillions of dollars worth of annual

493
00:27:02.759 --> 00:27:06.119
<v Speaker 7>revenues in these industries and they all suffer from these problems.

494
00:27:07.000 --> 00:27:09.319
<v Speaker 4>Yeah, well you can just imagine. I mean, I've studied

495
00:27:09.400 --> 00:27:13.319
<v Speaker 4>supply chain through SAP and some other companies, and it

496
00:27:13.319 --> 00:27:16.440
<v Speaker 4>gets incredibly complicated because some of these companies will have

497
00:27:16.920 --> 00:27:21.039
<v Speaker 4>hundreds of thousands, even millions of SKUs and so you know,

498
00:27:21.160 --> 00:27:25.519
<v Speaker 4>just from a data management and storage perspective, that's difficult.

499
00:27:25.720 --> 00:27:29.839
<v Speaker 4>Then enabling search is difficult. Then enabling search for your

500
00:27:29.880 --> 00:27:33.519
<v Speaker 4>partners and for your clients, which is also very important

501
00:27:33.559 --> 00:27:35.400
<v Speaker 4>because you want them to be able to find the

502
00:27:35.440 --> 00:27:38.359
<v Speaker 4>bits and pieces, the products, the component parts they need,

503
00:27:38.839 --> 00:27:42.960
<v Speaker 4>and all of that is facilitated by this compatible platform right.

504
00:27:43.440 --> 00:27:43.839
<v Speaker 5>That's right.

505
00:27:43.960 --> 00:27:48.559
<v Speaker 7>Yeah, Search and discovery, search discovery, compatibility and configuration.

506
00:27:49.559 --> 00:27:53.440
<v Speaker 4>And then right once you can search and align and

507
00:27:53.880 --> 00:27:58.519
<v Speaker 4>determine compatibility, then you get into things like pricing and

508
00:27:58.599 --> 00:28:01.680
<v Speaker 4>configure price quote, which is another huge part of the industry.

509
00:28:01.799 --> 00:28:04.960
<v Speaker 4>Knowing what you can charge for something, Knowing what the

510
00:28:05.000 --> 00:28:09.119
<v Speaker 4>margins are that your competitors are putting out in the marketplace,

511
00:28:09.160 --> 00:28:12.119
<v Speaker 4>that you're putting out there, finding the balance amongst all

512
00:28:12.160 --> 00:28:14.440
<v Speaker 4>those things. I mean, that's a full time job for people.

513
00:28:14.839 --> 00:28:17.160
<v Speaker 4>And you still have to take guesses, right, I mean,

514
00:28:17.359 --> 00:28:19.799
<v Speaker 4>you're going to figure out all your prices, You're going

515
00:28:19.839 --> 00:28:21.680
<v Speaker 4>to configure and figure out Okay, I think I can

516
00:28:21.759 --> 00:28:23.799
<v Speaker 4>get this price, and you send it out there and

517
00:28:23.880 --> 00:28:26.519
<v Speaker 4>hopefully they bite, and then you go ahead and go

518
00:28:26.559 --> 00:28:27.720
<v Speaker 4>through this, and you have to be able to go

519
00:28:27.759 --> 00:28:29.680
<v Speaker 4>back and audit that and report on it and figure

520
00:28:29.680 --> 00:28:32.079
<v Speaker 4>out where's the margin because you've got to make money, right,

521
00:28:32.119 --> 00:28:33.680
<v Speaker 4>Everyone has to make money at the end of the day.

522
00:28:34.160 --> 00:28:39.000
<v Speaker 4>So you're helping facilitate these transactions. You're helping make sure

523
00:28:39.079 --> 00:28:41.599
<v Speaker 4>that companies are getting the parts that they need to get,

524
00:28:41.799 --> 00:28:45.680
<v Speaker 4>and you're also I think enabling more of that sharpening

525
00:28:45.759 --> 00:28:48.279
<v Speaker 4>of the pencil basically, because once you know what the

526
00:28:48.279 --> 00:28:53.319
<v Speaker 4>margins are, and once you know what the reliability of

527
00:28:53.359 --> 00:28:56.119
<v Speaker 4>the providers are as well, then you can make these

528
00:28:56.160 --> 00:28:59.000
<v Speaker 4>informed decisions. Then you can kind of understand where the

529
00:28:59.039 --> 00:29:01.640
<v Speaker 4>margin is and that's kind of how you grow your business.

530
00:29:01.720 --> 00:29:04.680
<v Speaker 4>But folks, so Compatio co O m P A t

531
00:29:04.920 --> 00:29:09.920
<v Speaker 4>io is Acompatio dot com. Is that right, Ai, Compatio

532
00:29:10.000 --> 00:29:14.240
<v Speaker 4>dot Ai. Well, Timothy, congratulations on building this platform. This

533
00:29:14.279 --> 00:29:17.359
<v Speaker 4>is a pretty seriously big deal and you're really greasing

534
00:29:17.400 --> 00:29:20.000
<v Speaker 4>the tracks that I love that you've got a taxonomy

535
00:29:20.279 --> 00:29:25.000
<v Speaker 4>or taxonomies ontologies basically and a knowledge graph. That's the

536
00:29:25.000 --> 00:29:26.599
<v Speaker 4>way to do it. That's what our audience loves to

537
00:29:26.599 --> 00:29:28.640
<v Speaker 4>hear about. So thanks for your time today. Look you

538
00:29:28.680 --> 00:29:32.440
<v Speaker 4>spokes up online ladies and gentlemen. Compatio dot ai and

539
00:29:32.480 --> 00:29:34.279
<v Speaker 4>Timothy Bains will talk to you next time. You've been

540
00:29:34.279 --> 00:29:48.599
<v Speaker 4>listening to Inside Analysis.

541
00:29:44.119 --> 00:29:49.079
<v Speaker 3>Welcome back to Inside Analysis. Here's your host, Eric Tavanaugh.

542
00:29:51.720 --> 00:29:54.400
<v Speaker 4>All right, folks back here on Inside Analysis. Your host here,

543
00:29:54.480 --> 00:29:57.359
<v Speaker 4>Eric Haavadaugh, And today I'm with Abby Rass of a

544
00:29:57.359 --> 00:30:02.640
<v Speaker 4>company called Hydraulics. It's hyd Elix, and Hydraulics is a

545
00:30:02.759 --> 00:30:06.720
<v Speaker 4>very interesting company that is filling a significant gap that

546
00:30:06.839 --> 00:30:12.200
<v Speaker 4>is enabling really powerful cloud content delivery networks and other

547
00:30:12.240 --> 00:30:17.119
<v Speaker 4>companies to do real time analysis of observability at scale.

548
00:30:17.519 --> 00:30:19.160
<v Speaker 4>And why does that matter. It matters for a lot

549
00:30:19.160 --> 00:30:23.160
<v Speaker 4>of different reasons. It matters because these systems are very

550
00:30:23.200 --> 00:30:26.720
<v Speaker 4>complex these days. You can imagine Netflix, for example, the

551
00:30:26.720 --> 00:30:31.119
<v Speaker 4>amount of data that's flying out all these various sources,

552
00:30:31.160 --> 00:30:33.519
<v Speaker 4>all these various data centers to get to your TV

553
00:30:33.640 --> 00:30:35.440
<v Speaker 4>so you can watch all these movies. That's a lot

554
00:30:35.480 --> 00:30:38.599
<v Speaker 4>of data. So when you're trying to maintain these systems,

555
00:30:38.640 --> 00:30:41.119
<v Speaker 4>you're looking for all kinds of things. And when you're

556
00:30:41.160 --> 00:30:44.839
<v Speaker 4>trying to do that sort of industrial grade analytics on

557
00:30:45.039 --> 00:30:48.119
<v Speaker 4>systems performance and management, well there are lots and lots

558
00:30:48.119 --> 00:30:49.920
<v Speaker 4>of metrics that you can look for these days. And

559
00:30:50.440 --> 00:30:54.960
<v Speaker 4>obviously the Kubernetes movement has played deep into this whole

560
00:30:55.000 --> 00:30:59.920
<v Speaker 4>space now spinning up amazing amounts of compute, federating compute basic,

561
00:31:00.359 --> 00:31:05.319
<v Speaker 4>so really enabling this tremendous scalability of information systems of

562
00:31:05.480 --> 00:31:08.720
<v Speaker 4>enterprise create information systems. But also it opened all sorts

563
00:31:08.759 --> 00:31:12.160
<v Speaker 4>of Pandora's boxes on data and on what's actually happening

564
00:31:12.240 --> 00:31:15.319
<v Speaker 4>under the covers, so to monitor that and to watch

565
00:31:15.400 --> 00:31:18.279
<v Speaker 4>not just for bad guys, but also for performance issues,

566
00:31:18.680 --> 00:31:22.440
<v Speaker 4>anything that stumbles and starts causing trouble to users. You

567
00:31:22.559 --> 00:31:25.359
<v Speaker 4>need to absorb tons and tons of data from a

568
00:31:25.400 --> 00:31:28.480
<v Speaker 4>lot of different systems and be able to coalesce that

569
00:31:28.519 --> 00:31:32.519
<v Speaker 4>and analyze it in fair fairly real time. And that's

570
00:31:32.559 --> 00:31:34.680
<v Speaker 4>the kind of stuff that Hydraulics does. So they call

571
00:31:34.720 --> 00:31:37.640
<v Speaker 4>themselves a bit of a streaming data lake company, but

572
00:31:37.720 --> 00:31:42.319
<v Speaker 4>also headless observability. And I love this headless concept. I'm

573
00:31:42.319 --> 00:31:45.160
<v Speaker 4>hearing this more and more and I really like it

574
00:31:45.200 --> 00:31:48.079
<v Speaker 4>because what it kind of implies is, look, we're giving

575
00:31:48.079 --> 00:31:50.960
<v Speaker 4>you an engine and you can put whatever covering you

576
00:31:51.000 --> 00:31:53.400
<v Speaker 4>want on it that suits your particular needs or your

577
00:31:53.519 --> 00:31:56.720
<v Speaker 4>environment to use this powerful engine to get stuff done.

578
00:31:56.799 --> 00:31:56.920
<v Speaker 8>Right.

579
00:31:56.960 --> 00:31:57.480
<v Speaker 4>What do you think?

580
00:31:58.000 --> 00:31:59.759
<v Speaker 9>Yeah, I mean it's like mister potato head.

581
00:32:00.039 --> 00:32:01.920
<v Speaker 10>You can flip THEMP you can, you know, put on

582
00:32:01.960 --> 00:32:05.200
<v Speaker 10>different hats, put on different eyes. It's whatever you want

583
00:32:05.200 --> 00:32:08.559
<v Speaker 10>in the top. But you know the bum right, But no,

584
00:32:08.640 --> 00:32:10.279
<v Speaker 10>it's it's essentially the same thing.

585
00:32:10.359 --> 00:32:10.519
<v Speaker 5>Right.

586
00:32:10.519 --> 00:32:14.880
<v Speaker 10>So with Hydraulics our software, anyone can plug in any

587
00:32:14.880 --> 00:32:15.680
<v Speaker 10>type of dashboard.

588
00:32:15.680 --> 00:32:17.839
<v Speaker 9>It comes with pre built Graffona dashboards.

589
00:32:18.200 --> 00:32:20.680
<v Speaker 10>However, if somebody wants to keep their splunk instance, if

590
00:32:20.720 --> 00:32:22.640
<v Speaker 10>somebody wants to keep any kind of front end dashboard

591
00:32:22.680 --> 00:32:25.400
<v Speaker 10>that they have, that's totally fine. We have connectors so

592
00:32:25.440 --> 00:32:28.000
<v Speaker 10>you can put any front end analytics dashboard on top

593
00:32:28.039 --> 00:32:30.960
<v Speaker 10>of our back end and still get the benefits of

594
00:32:31.680 --> 00:32:36.319
<v Speaker 10>less money, especially for storage, longer data retention, always hot data,

595
00:32:36.400 --> 00:32:39.680
<v Speaker 10>for rapid queering and ingesting massive amounts of data at

596
00:32:39.720 --> 00:32:41.720
<v Speaker 10>least to terabyte a month in real time.

597
00:32:42.319 --> 00:32:46.519
<v Speaker 4>Well yeah, and that real time nature is crucial. You

598
00:32:46.519 --> 00:32:48.920
<v Speaker 4>were telling us a story before we hit the record

599
00:32:48.960 --> 00:32:52.200
<v Speaker 4>button about a particular use case where a Black Friday

600
00:32:52.680 --> 00:32:56.519
<v Speaker 4>real retailer was able to discover a problem as it

601
00:32:56.599 --> 00:32:58.640
<v Speaker 4>was happening. Some kind of a hack was going on,

602
00:32:59.160 --> 00:33:02.200
<v Speaker 4>found it, discover it, nullified it. Nobody even noticed on

603
00:33:02.319 --> 00:33:03.480
<v Speaker 4>the front end, right.

604
00:33:04.000 --> 00:33:06.440
<v Speaker 10>Yeah, this was a large retailer global, It was during

605
00:33:06.480 --> 00:33:10.200
<v Speaker 10>Black Friday week and there was a massive DDoS attack

606
00:33:10.839 --> 00:33:14.079
<v Speaker 10>and it spanned eighty countries and three thousand IP addresses.

607
00:33:14.480 --> 00:33:14.920
<v Speaker 4>Wow.

608
00:33:15.079 --> 00:33:19.279
<v Speaker 10>Graphic Peak, the manager observability service that akama I built

609
00:33:19.359 --> 00:33:24.440
<v Speaker 10>using our software at Hydraulics pinpointed this attack instantly, so

610
00:33:24.519 --> 00:33:27.279
<v Speaker 10>the company was able to mitigate it in real time

611
00:33:27.599 --> 00:33:31.039
<v Speaker 10>before any of their customers even noticed anything. Wow, So

612
00:33:31.640 --> 00:33:36.000
<v Speaker 10>it really was instrumental for them to maintain business.

613
00:33:36.400 --> 00:33:40.200
<v Speaker 4>Yeah, that's amazing. And you think about what it takes

614
00:33:40.559 --> 00:33:42.759
<v Speaker 4>to be able to ingest all that data, and that's

615
00:33:42.759 --> 00:33:45.839
<v Speaker 4>a big key to what you're offering, right is number one,

616
00:33:46.440 --> 00:33:49.279
<v Speaker 4>hyper scale ingestion of data. So you can tap into

617
00:33:49.279 --> 00:33:53.480
<v Speaker 4>any number of systems, industrial grade systems, cloud infrastructure basically,

618
00:33:53.960 --> 00:33:57.000
<v Speaker 4>and you are very good at pulling in data very quickly,

619
00:33:57.200 --> 00:34:00.240
<v Speaker 4>but then also enabling the analysis of that data. And

620
00:34:00.279 --> 00:34:03.319
<v Speaker 4>that's all in hydraulics, right though you do also, as

621
00:34:03.359 --> 00:34:06.759
<v Speaker 4>you suggest, you're headless, so you can work in conjunction

622
00:34:06.839 --> 00:34:08.280
<v Speaker 4>with any number of analytics tools.

623
00:34:08.360 --> 00:34:10.840
<v Speaker 9>Right, that's absolutely true.

624
00:34:10.920 --> 00:34:14.559
<v Speaker 10>We actually just ran one of the largest sporting events

625
00:34:15.480 --> 00:34:19.519
<v Speaker 10>in the country and at the peak viewing time, we

626
00:34:19.599 --> 00:34:24.119
<v Speaker 10>were ingesting more than a petabyte of data an hour.

627
00:34:24.760 --> 00:34:27.360
<v Speaker 9>Wow, I'm sorry, not an hour, more than a petabyte.

628
00:34:27.480 --> 00:34:30.599
<v Speaker 10>We let me repeat that, at peak viewing time, we

629
00:34:30.599 --> 00:34:34.199
<v Speaker 10>were ingesting more than a petabyte of data a day, Okay,

630
00:34:34.239 --> 00:34:38.079
<v Speaker 10>which is an enormous I mean that's monster data, right,

631
00:34:38.159 --> 00:34:40.760
<v Speaker 10>and a lot of a lot of times these legacy systems,

632
00:34:40.760 --> 00:34:43.920
<v Speaker 10>because they were not built for the modern architecture of

633
00:34:44.000 --> 00:34:46.159
<v Speaker 10>today will crash or slow.

634
00:34:45.920 --> 00:34:48.320
<v Speaker 9>Down when ingesting that amount of data.

635
00:34:48.400 --> 00:34:52.760
<v Speaker 10>But for us a petabite a day, nothing crashed, nothing

636
00:34:52.800 --> 00:34:53.360
<v Speaker 10>slowed down.

637
00:34:53.719 --> 00:34:56.440
<v Speaker 9>We take it in in real time. We alert on.

638
00:34:56.639 --> 00:34:59.360
<v Speaker 10>Ingests, so we can show incidents in real time. You

639
00:34:59.360 --> 00:35:04.199
<v Speaker 10>can query in three seconds, six seconds, super super fast,

640
00:35:04.519 --> 00:35:07.519
<v Speaker 10>and then you can go fix the problem before anyone notices.

641
00:35:08.239 --> 00:35:10.960
<v Speaker 4>Yeah. Well, and you also you do some clever things

642
00:35:11.000 --> 00:35:15.360
<v Speaker 4>on the storage side and some clever things on data reduction. Basically,

643
00:35:15.480 --> 00:35:18.960
<v Speaker 4>so you really were purpose built for this kind of

644
00:35:19.039 --> 00:35:23.039
<v Speaker 4>use case, right, I mean your executive suite they saw

645
00:35:23.079 --> 00:35:25.199
<v Speaker 4>this coming, they saw a need for this, and then

646
00:35:25.280 --> 00:35:27.880
<v Speaker 4>purpose built this engine to be able to fill this

647
00:35:27.880 --> 00:35:29.079
<v Speaker 4>particular use case.

648
00:35:29.159 --> 00:35:29.360
<v Speaker 5>Right.

649
00:35:29.840 --> 00:35:33.119
<v Speaker 10>Yes, I mean it's two problems, right. It's the fact

650
00:35:33.159 --> 00:35:36.079
<v Speaker 10>that the amount of data is growing so much each

651
00:35:36.159 --> 00:35:38.480
<v Speaker 10>year it's supposed to increase by forty percent, that's when

652
00:35:38.480 --> 00:35:42.360
<v Speaker 10>an analyst recently told us year over year. And also

653
00:35:42.920 --> 00:35:45.480
<v Speaker 10>it's the cost. I mean, keeping data like this.

654
00:35:45.559 --> 00:35:48.960
<v Speaker 9>Costs a fortune. So we wanted to solve both of

655
00:35:49.000 --> 00:35:49.719
<v Speaker 9>those problems.

656
00:35:49.840 --> 00:35:52.119
<v Speaker 10>The ability to keep all your data no matter how

657
00:35:52.199 --> 00:35:54.920
<v Speaker 10>large the data set, and also make it affordable.

658
00:35:55.320 --> 00:35:56.159
<v Speaker 9>So that's what we're doing.

659
00:35:56.159 --> 00:35:58.119
<v Speaker 10>And the reason why, one of the biggest reasons with

660
00:35:58.239 --> 00:36:00.079
<v Speaker 10>especially data retention, that we can make it affordable, well

661
00:36:00.440 --> 00:36:03.159
<v Speaker 10>is that we have a twenty five to fifty compression ratio,

662
00:36:04.000 --> 00:36:06.400
<v Speaker 10>so we make that huge data set very very small

663
00:36:07.079 --> 00:36:08.559
<v Speaker 10>and easy to keep and managed.

664
00:36:09.159 --> 00:36:12.400
<v Speaker 4>Yeah, now that's clever. What's interesting is there are lots

665
00:36:12.400 --> 00:36:14.719
<v Speaker 4>of different things that you can do from an architectural

666
00:36:14.760 --> 00:36:20.400
<v Speaker 4>perspective to optimize for certain goals, for certain objectives, and

667
00:36:20.800 --> 00:36:24.639
<v Speaker 4>this compression capability you have, that's why you're able to

668
00:36:24.800 --> 00:36:27.960
<v Speaker 4>enable a much more cost effective storage layer, right.

669
00:36:28.199 --> 00:36:32.079
<v Speaker 10>Correct, And we have decoupled architecture, so compute and storage

670
00:36:32.079 --> 00:36:35.239
<v Speaker 10>can be scaled up or scaled down separately.

671
00:36:35.239 --> 00:36:37.760
<v Speaker 4>Right, which is exactly what Snowflake did, right. I mean,

672
00:36:38.480 --> 00:36:40.800
<v Speaker 4>I think they were the poster children for separating compute

673
00:36:40.800 --> 00:36:43.159
<v Speaker 4>from storage. And everyone's like, oh, that's a pretty good idea.

674
00:36:43.519 --> 00:36:45.000
<v Speaker 4>Let's go ahead and run with that, right.

675
00:36:45.400 --> 00:36:45.719
<v Speaker 5>Yeah.

676
00:36:45.960 --> 00:36:47.760
<v Speaker 10>In fact, in that largest football game, we were able

677
00:36:47.840 --> 00:36:51.360
<v Speaker 10>to save the customer compute power because they didn't you know,

678
00:36:51.400 --> 00:36:53.920
<v Speaker 10>when the peak viewing time dropped, they didn't need all

679
00:36:53.960 --> 00:36:57.199
<v Speaker 10>that infrastructure, right, It scaled down really easily while still

680
00:36:57.239 --> 00:36:57.559
<v Speaker 10>keeping the.

681
00:36:57.559 --> 00:37:01.239
<v Speaker 4>Storage well, you know, to myself here you talk about

682
00:37:01.280 --> 00:37:03.159
<v Speaker 4>traffic Peak, which is a cool name, by the way,

683
00:37:03.199 --> 00:37:07.360
<v Speaker 4>and that's that's the solution which Akamai built using your technology, right,

684
00:37:07.360 --> 00:37:09.320
<v Speaker 4>which they're now selling to their clients as well. Is

685
00:37:09.320 --> 00:37:09.880
<v Speaker 4>that correct?

686
00:37:10.199 --> 00:37:14.199
<v Speaker 10>Yes, we have so I leave partner marketing for Hydraulics,

687
00:37:14.480 --> 00:37:17.480
<v Speaker 10>and we have very strong partnerships with Akamai and AWS

688
00:37:17.920 --> 00:37:21.280
<v Speaker 10>and others, but our software can run on any cloud platform.

689
00:37:21.599 --> 00:37:22.960
<v Speaker 9>Akima is a huge.

690
00:37:22.679 --> 00:37:25.719
<v Speaker 10>Success story for us because they have been so supportive

691
00:37:25.840 --> 00:37:29.599
<v Speaker 10>of the partnership from every level, from product sales to marketing.

692
00:37:30.000 --> 00:37:32.719
<v Speaker 10>So when we launched in twenty twenty three traffic Peak,

693
00:37:32.760 --> 00:37:36.280
<v Speaker 10>which is the manager observability service that Akamai built using

694
00:37:36.400 --> 00:37:39.559
<v Speaker 10>our software, we had thirty three customers in the beginning.

695
00:37:39.840 --> 00:37:41.679
<v Speaker 9>In one year, that number shot up to more than

696
00:37:41.719 --> 00:37:43.159
<v Speaker 9>three hundred and seventy customers.

697
00:37:43.639 --> 00:37:46.599
<v Speaker 10>That's great, and you know, it's a lot because the

698
00:37:46.599 --> 00:37:49.599
<v Speaker 10>product speaks for itself, but also because we have such

699
00:37:49.599 --> 00:37:52.960
<v Speaker 10>a collaborative relationship with Akamai and they're so supportive on

700
00:37:53.000 --> 00:37:56.079
<v Speaker 10>all ends, and we're so supportive of them on all ends.

701
00:37:56.280 --> 00:37:58.800
<v Speaker 10>So it's really been a successful partnership. And they just

702
00:37:58.880 --> 00:38:01.800
<v Speaker 10>named us the North of America Qualified Compute Partner of

703
00:38:01.840 --> 00:38:04.039
<v Speaker 10>the Year because it's great well.

704
00:38:04.079 --> 00:38:07.480
<v Speaker 4>And the thing to understand for from a broader business

705
00:38:08.000 --> 00:38:12.440
<v Speaker 4>audience perspective is that we are seeing tremendous advances in

706
00:38:12.480 --> 00:38:15.159
<v Speaker 4>all sorts of different spaces, and companies can come along

707
00:38:15.400 --> 00:38:18.880
<v Speaker 4>like Hydraulics and build this engine purpose, build this engine

708
00:38:19.000 --> 00:38:23.599
<v Speaker 4>for massive and jest for real time analysis. And when

709
00:38:23.639 --> 00:38:25.920
<v Speaker 4>you do that, you're head and shoulders above some of

710
00:38:26.000 --> 00:38:28.719
<v Speaker 4>the older legacy systems that just weren't designed to do

711
00:38:28.760 --> 00:38:30.519
<v Speaker 4>that kind of thing. And you know there are a lot,

712
00:38:30.559 --> 00:38:34.039
<v Speaker 4>you know, so years ago I had doctor Michael Stonebreaker

713
00:38:34.119 --> 00:38:36.039
<v Speaker 4>on the show. I don't know if you recognize the name,

714
00:38:36.079 --> 00:38:38.239
<v Speaker 4>but he's the godfather of the modern database. Basically, he

715
00:38:38.280 --> 00:38:41.320
<v Speaker 4>wrote the Postgress database like fifty years ago and has

716
00:38:41.719 --> 00:38:44.880
<v Speaker 4>spun up several companies, including Vertica, which in its time

717
00:38:44.960 --> 00:38:48.079
<v Speaker 4>in two thousand and five was all about real time analytics,

718
00:38:48.199 --> 00:38:50.760
<v Speaker 4>was all about column oriented analytics. It was a new

719
00:38:50.800 --> 00:38:53.440
<v Speaker 4>crazy thing back then. But he had this one fun

720
00:38:53.519 --> 00:38:55.599
<v Speaker 4>quote on a show one day where he said, the

721
00:38:55.639 --> 00:38:58.679
<v Speaker 4>funny thing is that people should realize eighty percent of

722
00:38:58.719 --> 00:39:02.079
<v Speaker 4>the code that's been written in the world should just

723
00:39:02.159 --> 00:39:05.679
<v Speaker 4>be thrown away at this point was that it was

724
00:39:05.719 --> 00:39:09.199
<v Speaker 4>written for older systems. And so if you think about

725
00:39:09.320 --> 00:39:12.480
<v Speaker 4>spinning disc for example, versus solid state drive, well, it's

726
00:39:12.519 --> 00:39:16.039
<v Speaker 4>a very different world if you're using SSDs in terms

727
00:39:16.039 --> 00:39:18.679
<v Speaker 4>of that architecture and how fast you can move things.

728
00:39:19.079 --> 00:39:21.039
<v Speaker 4>And now there are all sorts of companies using the

729
00:39:21.159 --> 00:39:24.599
<v Speaker 4>NVMe protocol to move data much more fast than it's

730
00:39:24.639 --> 00:39:27.320
<v Speaker 4>ever been done before. And so I'm saying all this

731
00:39:27.679 --> 00:39:29.280
<v Speaker 4>Abbey as a way to kind of tee you up,

732
00:39:29.280 --> 00:39:32.280
<v Speaker 4>to explain to the audience, like this is you can't

733
00:39:32.320 --> 00:39:36.239
<v Speaker 4>just upgrade your existing SQL server instance to get this

734
00:39:36.360 --> 00:39:38.280
<v Speaker 4>kind of performance. I mean, this is a whole new

735
00:39:38.280 --> 00:39:40.760
<v Speaker 4>engine that's been built for that specific purpose.

736
00:39:40.480 --> 00:39:43.599
<v Speaker 10>Right yeah, I mean that would be like creating mister

737
00:39:43.639 --> 00:39:44.679
<v Speaker 10>potato Head out of wood.

738
00:39:45.079 --> 00:39:48.400
<v Speaker 4>I mean it's like mister potato head.

739
00:39:50.159 --> 00:39:52.480
<v Speaker 9>I forgot this can cancel culture.

740
00:39:53.800 --> 00:39:57.280
<v Speaker 10>But anyway, you know, these legacy systems were built in

741
00:39:57.320 --> 00:40:00.280
<v Speaker 10>a certain way to handle data in a certain way,

742
00:40:00.840 --> 00:40:03.519
<v Speaker 10>and what they didn't expect was for that data to

743
00:40:03.559 --> 00:40:06.639
<v Speaker 10>get so big that it's literally like busting the seams.

744
00:40:06.360 --> 00:40:08.360
<v Speaker 9>Right right of these legacy systems.

745
00:40:08.559 --> 00:40:12.199
<v Speaker 10>And so that's why we need new observability services that

746
00:40:12.239 --> 00:40:17.079
<v Speaker 10>can handle this modern architecture of all these micro services dispersed.

747
00:40:16.639 --> 00:40:19.280
<v Speaker 9>Everywhere that produce so much data.

748
00:40:19.280 --> 00:40:22.360
<v Speaker 10>I mean, just one application produces so much data because

749
00:40:22.400 --> 00:40:23.119
<v Speaker 10>all of those.

750
00:40:22.960 --> 00:40:24.480
<v Speaker 9>Components that go into that app.

751
00:40:24.840 --> 00:40:28.519
<v Speaker 10>And so that's exactly why hydraulics exists today to solve

752
00:40:28.519 --> 00:40:28.719
<v Speaker 10>for that.

753
00:40:29.440 --> 00:40:32.440
<v Speaker 4>Well, look these folks up online, folks, Abby Ross of Hydraulics.

754
00:40:32.599 --> 00:40:35.840
<v Speaker 4>Very cool technology. You are listening to Inside Analysis.

755
00:40:36.159 --> 00:40:37.239
<v Speaker 1>We expected.

756
00:40:39.599 --> 00:40:41.880
<v Speaker 4>All right, folks back on the show here and now

757
00:40:41.920 --> 00:40:44.800
<v Speaker 4>we're talking to Kenneth Stott. He is the field CTO

758
00:40:44.920 --> 00:40:47.679
<v Speaker 4>from a company called Hasura, and they have a very

759
00:40:47.719 --> 00:40:52.960
<v Speaker 4>interesting play for reporting, specifically for regulatory reporting, and they

760
00:40:53.000 --> 00:40:55.400
<v Speaker 4>have a graph like approach to things. They use graph

761
00:40:55.519 --> 00:40:58.239
<v Speaker 4>q well and it's sort of the last mile of data.

762
00:40:58.280 --> 00:41:00.320
<v Speaker 4>And I really liked that concept and I that you

763
00:41:00.400 --> 00:41:02.760
<v Speaker 4>threw out there that it's the last mile of data.

764
00:41:02.840 --> 00:41:06.400
<v Speaker 4>And you can understand why that's important, especially for regulatory reporting,

765
00:41:06.440 --> 00:41:08.679
<v Speaker 4>because you give all these different information systems that people

766
00:41:08.719 --> 00:41:12.360
<v Speaker 4>are using, whether you're in financial services or healthcare, and

767
00:41:12.480 --> 00:41:14.159
<v Speaker 4>at the end of the day, you have to deliver

768
00:41:14.199 --> 00:41:16.400
<v Speaker 4>these reports to people and if the numbers don't line up,

769
00:41:16.719 --> 00:41:19.159
<v Speaker 4>that doesn't look good. That's when the auditor to say

770
00:41:19.360 --> 00:41:22.119
<v Speaker 4>no bueno, you have to go back to the drawing board.

771
00:41:22.559 --> 00:41:25.199
<v Speaker 4>So the question is where do you where do you

772
00:41:25.239 --> 00:41:28.519
<v Speaker 4>sort of reconcile all these different reports? And that's what

773
00:41:28.599 --> 00:41:31.480
<v Speaker 4>Hisora does in this sort of supergraph layer. Right, tell

774
00:41:31.519 --> 00:41:32.679
<v Speaker 4>us about that and how it works.

775
00:41:33.800 --> 00:41:38.840
<v Speaker 2>Sure, so I would describe it as a semantic layer.

776
00:41:40.880 --> 00:41:44.119
<v Speaker 2>What that would What I mean by that is the

777
00:41:44.360 --> 00:41:49.400
<v Speaker 2>individual teams that to create the data and own that

778
00:41:49.519 --> 00:41:56.119
<v Speaker 2>data publish it in semantic terms into a data access layer,

779
00:41:57.199 --> 00:42:00.440
<v Speaker 2>and then that data access layer validates all of the

780
00:42:00.559 --> 00:42:05.639
<v Speaker 2>relationships that they that they've described within the information that

781
00:42:05.679 --> 00:42:08.920
<v Speaker 2>they're publishing, so that you can get across all the

782
00:42:09.000 --> 00:42:13.719
<v Speaker 2>teams one consistent view of your data in business terms.

783
00:42:15.159 --> 00:42:17.760
<v Speaker 2>And then that that same data access layer has a

784
00:42:17.840 --> 00:42:22.000
<v Speaker 2>rich set of services to kind of discourage building new

785
00:42:22.119 --> 00:42:26.840
<v Speaker 2>capabilities downstream, because oftentimes those new capabilities that they build

786
00:42:26.880 --> 00:42:31.960
<v Speaker 2>downstream is where these problems start to arise, right sore,

787
00:42:32.320 --> 00:42:37.159
<v Speaker 2>If they're cleaning data downstream, if they're making additional transformations,

788
00:42:37.559 --> 00:42:40.639
<v Speaker 2>this is often where it starts to go wrong. And

789
00:42:40.679 --> 00:42:42.400
<v Speaker 2>the other thing I want to say about this last

790
00:42:42.440 --> 00:42:47.320
<v Speaker 2>mile of data is this is the most consequential part, right,

791
00:42:47.840 --> 00:42:51.199
<v Speaker 2>This is where people in the c suite make key

792
00:42:51.280 --> 00:42:55.519
<v Speaker 2>decisions that have big impact on an organization, or where

793
00:42:55.599 --> 00:43:00.760
<v Speaker 2>regulators pick up really meaningful differences that can drive you know,

794
00:43:00.960 --> 00:43:05.079
<v Speaker 2>a lot of pain for an organization. Putting focus on

795
00:43:05.119 --> 00:43:06.480
<v Speaker 2>this really pays off.

796
00:43:07.679 --> 00:43:09.719
<v Speaker 4>Yeah, that makes a lot of sense. And you know,

797
00:43:10.000 --> 00:43:13.239
<v Speaker 4>I'm from the whole world of business intelligence and analytics

798
00:43:13.239 --> 00:43:15.239
<v Speaker 4>and reporting, and you know, we came up with the

799
00:43:15.320 --> 00:43:18.000
<v Speaker 4>data warehouse concept as a way of marshaling all the

800
00:43:18.079 --> 00:43:21.320
<v Speaker 4>key data points into one relational database which we can

801
00:43:21.360 --> 00:43:24.599
<v Speaker 4>then report from. So I get that. But to your point,

802
00:43:24.880 --> 00:43:27.440
<v Speaker 4>a data warehouse isn't the only system of record. You

803
00:43:27.480 --> 00:43:30.000
<v Speaker 4>have lots of other systems of record that these organizations

804
00:43:30.039 --> 00:43:33.480
<v Speaker 4>are focused on to shepherd through. And if you have

805
00:43:33.599 --> 00:43:37.440
<v Speaker 4>this last mile, this semantic layer, or you're tracking these things,

806
00:43:37.760 --> 00:43:39.559
<v Speaker 4>you can get a much better handle on it. And

807
00:43:39.599 --> 00:43:42.239
<v Speaker 4>I like the way you say it's got some built

808
00:43:42.280 --> 00:43:47.639
<v Speaker 4>in capability to discourage downstream modifications, right, Yeah.

809
00:43:47.559 --> 00:43:52.880
<v Speaker 2>Yeah, absolutely, data warehouses, you know, absolutely have to be

810
00:43:52.960 --> 00:43:57.400
<v Speaker 2>part of the landscape going forward. There's a need to

811
00:43:58.000 --> 00:44:02.440
<v Speaker 2>take data in and develop different analytics from it. But

812
00:44:03.559 --> 00:44:09.920
<v Speaker 2>centralization has limits, and analytical data isn't the only thing

813
00:44:10.000 --> 00:44:14.320
<v Speaker 2>that's required for these sorts of dashboards and reports. In

814
00:44:14.360 --> 00:44:17.480
<v Speaker 2>this last mile of data, you need both operational data,

815
00:44:17.840 --> 00:44:22.159
<v Speaker 2>you need analytical data, and so all of these things

816
00:44:22.400 --> 00:44:27.039
<v Speaker 2>ultimately become the data products that flow into this smantic layer.

817
00:44:27.639 --> 00:44:30.400
<v Speaker 2>There are some amazing things you can do once you

818
00:44:30.480 --> 00:44:34.039
<v Speaker 2>have visibility to all your data as it's in motion

819
00:44:34.920 --> 00:44:40.480
<v Speaker 2>at this last mile. Another I've studied. I've studied then

820
00:44:40.519 --> 00:44:44.639
<v Speaker 2>a lot of quantitative studies around where things go wrong.

821
00:44:46.679 --> 00:44:52.920
<v Speaker 2>Oftentimes anomalies have to do with people combining data across

822
00:44:53.039 --> 00:44:57.639
<v Speaker 2>disparate domains, and you can do things like anomaly detection

823
00:44:57.760 --> 00:45:01.280
<v Speaker 2>at that level, right, and you can say, this really

824
00:45:01.320 --> 00:45:04.159
<v Speaker 2>doesn't make sense the way you're combining this data to

825
00:45:04.280 --> 00:45:05.599
<v Speaker 2>produce some output.

826
00:45:07.280 --> 00:45:09.280
<v Speaker 4>Yeah, that makes a whole heck of a lot of sense.

827
00:45:09.480 --> 00:45:14.639
<v Speaker 4>And it is the reconciliation layer. It's the final proof really,

828
00:45:15.119 --> 00:45:18.000
<v Speaker 4>and again you've sort of baked in here some of

829
00:45:18.039 --> 00:45:21.360
<v Speaker 4>the formulae to be able to identify I mean, I

830
00:45:21.400 --> 00:45:24.679
<v Speaker 4>won't it's not exactly like Master Data Management, but there

831
00:45:24.840 --> 00:45:29.159
<v Speaker 4>is a flavor of MDN. There's a flavor of reconciling

832
00:45:29.400 --> 00:45:32.079
<v Speaker 4>dispirit information systems. And I like too that you're not

833
00:45:32.199 --> 00:45:35.039
<v Speaker 4>just looking at analytical data from a warehouse, you're actually

834
00:45:35.119 --> 00:45:38.920
<v Speaker 4>pulling in operational data. As a sort of reality check, right.

835
00:45:39.440 --> 00:45:45.039
<v Speaker 2>Yeah, yeah, absolutely, there are also upstream benefits, right, because

836
00:45:45.079 --> 00:45:49.679
<v Speaker 2>what often happens in those data warehouses, those analytical environments

837
00:45:49.719 --> 00:45:54.119
<v Speaker 2>is they start trying to serve a lot of different

838
00:45:54.159 --> 00:45:57.960
<v Speaker 2>stakeholders and they start pulling in data from their peers,

839
00:45:58.360 --> 00:46:01.440
<v Speaker 2>and you end up with a lot of cross sharing

840
00:46:01.480 --> 00:46:05.880
<v Speaker 2>of data in ways that become problematic. So I've also

841
00:46:05.920 --> 00:46:11.039
<v Speaker 2>studied the cost of this sort of sort of ball

842
00:46:11.079 --> 00:46:15.039
<v Speaker 2>of yarn that we generally create in these environments, and

843
00:46:18.119 --> 00:46:21.480
<v Speaker 2>my take on it is about two thirds of data

844
00:46:21.519 --> 00:46:26.039
<v Speaker 2>movement and data storage is wasted. If you could optimize,

845
00:46:26.719 --> 00:46:28.960
<v Speaker 2>you could get rid of two thirds of that cost.

846
00:46:29.039 --> 00:46:31.480
<v Speaker 2>And by the way, costs have been going up ten

847
00:46:31.519 --> 00:46:34.360
<v Speaker 2>percent per year for the last three years, they're projected

848
00:46:34.400 --> 00:46:37.039
<v Speaker 2>to go up again. And if you look at data

849
00:46:37.079 --> 00:46:42.960
<v Speaker 2>maturity statistics, they're flat. So we're spending all this money, right,

850
00:46:43.320 --> 00:46:44.800
<v Speaker 2>but it's not getting that much better.

851
00:46:45.599 --> 00:46:47.360
<v Speaker 4>You hit the nail on the head. And it's funny

852
00:46:47.360 --> 00:46:51.599
<v Speaker 4>you would say that because quite literally, DM Radio. Let's see,

853
00:46:51.639 --> 00:46:55.159
<v Speaker 4>we turned seventeen years old yesterday. That's how long we've

854
00:46:55.199 --> 00:46:58.719
<v Speaker 4>been doing these shows, and in the earliest days in

855
00:46:58.760 --> 00:47:01.320
<v Speaker 4>the first year, I was trying to wrap my head

856
00:47:01.360 --> 00:47:03.480
<v Speaker 4>around all the ETL that's being done to fill the

857
00:47:03.559 --> 00:47:06.840
<v Speaker 4>data warehouse and thinking to myself, this is crazy. You

858
00:47:06.880 --> 00:47:09.800
<v Speaker 4>guys are clearly moving the same data multiple times. You're

859
00:47:09.800 --> 00:47:11.800
<v Speaker 4>probably not even using eighty percent of the data that

860
00:47:11.840 --> 00:47:14.320
<v Speaker 4>you're moving. Why are you moving it all? And it's

861
00:47:14.360 --> 00:47:17.760
<v Speaker 4>because of how we got here. It's because way back

862
00:47:18.039 --> 00:47:20.800
<v Speaker 4>thirty years ago, when we were beginning to really mature

863
00:47:20.880 --> 00:47:24.840
<v Speaker 4>data warehousing architectures, people were just catching on and you're like, oh, well,

864
00:47:24.880 --> 00:47:26.280
<v Speaker 4>I want this data in the warehouse. I want that

865
00:47:26.360 --> 00:47:28.079
<v Speaker 4>data in the warehouse. So you get these batch windows

866
00:47:28.079 --> 00:47:31.639
<v Speaker 4>that stack up and it's almost like an archaeological dig now, right,

867
00:47:31.679 --> 00:47:34.280
<v Speaker 4>you have just layers and layers and layers of data movement,

868
00:47:34.519 --> 00:47:36.800
<v Speaker 4>and the question becomes, what do we really need to do?

869
00:47:37.360 --> 00:47:40.119
<v Speaker 4>And what you're saying is that with this supergraph layer

870
00:47:40.159 --> 00:47:44.480
<v Speaker 4>that you've got managing semantics, if people work with you appropriately,

871
00:47:44.880 --> 00:47:47.559
<v Speaker 4>you can solve problems upstream, meaning you don't have to

872
00:47:47.599 --> 00:47:49.840
<v Speaker 4>move as much data now, and you can also solve

873
00:47:49.880 --> 00:47:52.440
<v Speaker 4>a lot of problems downstream. And that's what goes to

874
00:47:52.519 --> 00:47:54.400
<v Speaker 4>the executives to make the big decisions, right.

875
00:47:54.880 --> 00:48:00.079
<v Speaker 2>Yeah, So the idea is that the upstreams focus i

876
00:48:00.119 --> 00:48:04.679
<v Speaker 2>would say, on core data sets. These aren't this is

877
00:48:04.960 --> 00:48:08.920
<v Speaker 2>information I own. I own the definition combine. You know,

878
00:48:09.079 --> 00:48:12.679
<v Speaker 2>both the tech and the business teams together. They don't

879
00:48:12.679 --> 00:48:17.920
<v Speaker 2>get into serving sort of ad hoc requests because somebody

880
00:48:18.280 --> 00:48:19.920
<v Speaker 2>randomly connected with them.

881
00:48:20.039 --> 00:48:20.280
<v Speaker 9>Right.

882
00:48:21.360 --> 00:48:24.000
<v Speaker 2>What happens then is the supergraph layer is sort of

883
00:48:24.039 --> 00:48:28.440
<v Speaker 2>the place where those ad hoc requests get satisfied. And

884
00:48:28.480 --> 00:48:32.880
<v Speaker 2>that's why the upstreams stop all this sort of duplicate,

885
00:48:33.320 --> 00:48:35.880
<v Speaker 2>you know, sharing of data because they're very focused on

886
00:48:36.039 --> 00:48:41.440
<v Speaker 2>just what they need to do and the downstreams. The

887
00:48:41.480 --> 00:48:45.400
<v Speaker 2>downstreams get their needs satisfied more quickly because they're able

888
00:48:45.440 --> 00:48:48.599
<v Speaker 2>to see the data, they're able to composite it into

889
00:48:48.639 --> 00:48:50.960
<v Speaker 2>their narrow use cases for their needs.

890
00:48:51.599 --> 00:48:52.079
<v Speaker 5>Mm hmm.

891
00:48:52.719 --> 00:48:55.039
<v Speaker 4>We got about two minutes, a little over two minutes

892
00:48:55.079 --> 00:48:57.559
<v Speaker 4>left here. You had mentioned before the call that you

893
00:48:57.719 --> 00:49:01.639
<v Speaker 4>are containerized, right, like, so you run in a Kubernetes environment.

894
00:49:01.679 --> 00:49:02.239
<v Speaker 4>Is that correct?

895
00:49:03.400 --> 00:49:08.840
<v Speaker 2>Yeah? So our particular product works in all the major

896
00:49:08.960 --> 00:49:10.840
<v Speaker 2>cloud vendors of course, and you can do it as

897
00:49:10.880 --> 00:49:14.800
<v Speaker 2>a SaaS offering, but it also works in a Kubernetes cluster,

898
00:49:14.920 --> 00:49:17.519
<v Speaker 2>you can do it on prem and particularly think about

899
00:49:17.519 --> 00:49:21.119
<v Speaker 2>healthcare and finance. There's a lot of consternation around public

900
00:49:21.119 --> 00:49:23.880
<v Speaker 2>cloud and so forth, very important that you can do

901
00:49:23.960 --> 00:49:28.079
<v Speaker 2>on prem when people have serious security concerns.

902
00:49:28.400 --> 00:49:30.239
<v Speaker 4>Yeah. Well, I mean I have to say I think

903
00:49:30.280 --> 00:49:33.719
<v Speaker 4>that this focus on the last mile is really crucial,

904
00:49:34.159 --> 00:49:38.480
<v Speaker 4>and I love that you're also helping upstream by satisfying

905
00:49:38.480 --> 00:49:40.880
<v Speaker 4>a lot of these ad hoc style queries. I mean,

906
00:49:41.199 --> 00:49:43.000
<v Speaker 4>the bottom line is that once you get analytics in

907
00:49:43.039 --> 00:49:44.639
<v Speaker 4>an organization, people are going to want to know things,

908
00:49:44.639 --> 00:49:46.159
<v Speaker 4>and they're going to want to run queries and they're

909
00:49:46.199 --> 00:49:48.639
<v Speaker 4>going to want to play with stuff. And the better

910
00:49:48.679 --> 00:49:51.840
<v Speaker 4>you can shepherd those processes, the more governance you get,

911
00:49:52.079 --> 00:49:54.519
<v Speaker 4>the more quality you get at the end of the day,

912
00:49:54.800 --> 00:49:56.960
<v Speaker 4>and the low and you manage the cost as well.

913
00:49:57.039 --> 00:49:58.599
<v Speaker 4>Right closing thoughts from you, go ahead?

914
00:50:00.239 --> 00:50:06.400
<v Speaker 2>Yeah, absolutely, I mean I couldn't agree more. The benefits

915
00:50:06.440 --> 00:50:09.800
<v Speaker 2>are amazing. I'll say one last thing. I don't think

916
00:50:09.800 --> 00:50:12.039
<v Speaker 2>it's the last thing you do. You don't get your

917
00:50:12.039 --> 00:50:14.639
<v Speaker 2>house in order and then put this layer on top.

918
00:50:15.119 --> 00:50:18.440
<v Speaker 2>Put this layer on top for current states so you

919
00:50:18.480 --> 00:50:21.639
<v Speaker 2>can see what the heck is going on then fix

920
00:50:21.719 --> 00:50:22.559
<v Speaker 2>it surgically.

921
00:50:23.599 --> 00:50:26.079
<v Speaker 4>Yeah, that's an excellent point as well. I mean it's

922
00:50:26.159 --> 00:50:30.679
<v Speaker 4>you're talking about data observability, right. Everyone's into observability these days,

923
00:50:30.719 --> 00:50:34.199
<v Speaker 4>into systems and you know, and tracers and logs and

924
00:50:34.239 --> 00:50:36.400
<v Speaker 4>all these things. And I think communities is a part

925
00:50:36.400 --> 00:50:38.159
<v Speaker 4>of that too, because it just opened up this whole

926
00:50:38.159 --> 00:50:42.000
<v Speaker 4>can of worms about how to distribute process and everyone's like, whoa, now,

927
00:50:42.039 --> 00:50:43.760
<v Speaker 4>hold on, how do we manage that? We how do

928
00:50:43.800 --> 00:50:47.159
<v Speaker 4>we understand what it's doing because it's doing things very

929
00:50:47.239 --> 00:50:50.880
<v Speaker 4>very quickly. So but this is a great focus area

930
00:50:51.000 --> 00:50:53.320
<v Speaker 4>and it's a layer of abstraction, as you suggest, the

931
00:50:53.400 --> 00:50:57.119
<v Speaker 4>last mile, and I like that we say, understand what's

932
00:50:57.119 --> 00:50:59.840
<v Speaker 4>happening now and then come up with the plant if

933
00:51:00.159 --> 00:51:02.599
<v Speaker 4>things both upstream and downstream. But look this, gentleman up

934
00:51:02.599 --> 00:51:05.960
<v Speaker 4>online Kenneth dot of Hasura h A s U r

935
00:51:06.039 --> 00:51:11.079
<v Speaker 4>A correct. All right, folks, you are listening to Inside Analysis.

936
00:51:11.719 --> 00:51:11.960
<v Speaker 11>Now.

937
00:51:12.039 --> 00:51:15.159
<v Speaker 12>You can listen to k c AA radio anytime on

938
00:51:15.199 --> 00:51:18.639
<v Speaker 12>your smartphone device call seven two oh A three five

939
00:51:18.800 --> 00:51:22.159
<v Speaker 12>three oh nine nine seven two oh a three five

940
00:51:22.320 --> 00:51:26.679
<v Speaker 12>three oh nine nine k c A eight.

941
00:51:26.840 --> 00:51:29.599
<v Speaker 11>Peur Life's much better, So download the app in your

942
00:51:29.639 --> 00:51:33.000
<v Speaker 11>smart device today. Listen everywhere and anywhere, whether you're in

943
00:51:33.119 --> 00:51:37.119
<v Speaker 11>southern California, Texas for sailing on the Gulf of Mexico.

944
00:51:37.440 --> 00:51:41.880
<v Speaker 11>Life Sabreeze with KCAA download the app in your smart

945
00:51:41.880 --> 00:51:42.880
<v Speaker 11>device today.

946
00:51:43.440 --> 00:51:44.000
<v Speaker 10>Ah B.

947
00:51:46.559 --> 00:51:51.559
<v Speaker 13>Yesterday in the basic.

948
00:51:57.960 --> 00:51:59.039
<v Speaker 10>K c A eight.

949
00:52:01.400 --> 00:52:04.840
<v Speaker 14>What is your plan for your beneficiaries to manage your

950
00:52:04.920 --> 00:52:10.519
<v Speaker 14>final expenses when you pass away life? Insurance annuities, bank accounts,

951
00:52:10.599 --> 00:52:16.480
<v Speaker 14>destment accounts all required defertivity which takes ten days based

952
00:52:16.519 --> 00:52:20.480
<v Speaker 14>on the national average, which means no money's immediately available

953
00:52:20.639 --> 00:52:26.119
<v Speaker 14>and this causes stress and arguments. Simple solution the beneficiary

954
00:52:26.159 --> 00:52:30.159
<v Speaker 14>liquidity clan use money you already have no need to

955
00:52:30.159 --> 00:52:33.440
<v Speaker 14>come up with additional funds. The funds grow tax defer

956
00:52:34.079 --> 00:52:37.480
<v Speaker 14>and pass tax free to your name beneficiaries. The death

957
00:52:37.519 --> 00:52:41.639
<v Speaker 14>benefit is paid out in twenty four to forty eight

958
00:52:41.679 --> 00:52:44.480
<v Speaker 14>hours out a deficitary.

959
00:52:43.880 --> 00:52:45.719
<v Speaker 6>Nerdy money without.

960
00:52:45.320 --> 00:52:49.199
<v Speaker 14>A definitive call us at one eight hundred three zero

961
00:52:49.360 --> 00:52:51.599
<v Speaker 14>six fifty eighty six.

962
00:52:51.599 --> 00:52:54.800
<v Speaker 15>To Hebo T Club's original pure powder to RCO super

963
00:52:54.840 --> 00:52:56.960
<v Speaker 15>Ta comes from the only tree in the world that

964
00:52:57.000 --> 00:52:59.719
<v Speaker 15>fungus does not grow on. As a result, it naturally

965
00:52:59.760 --> 00:53:05.920
<v Speaker 15>has antifungal anti infection, anti viral, antibacterial, anti inflammation, and

966
00:53:06.159 --> 00:53:08.920
<v Speaker 15>anti parasite properties. So the tea is great for healthy

967
00:53:08.920 --> 00:53:11.679
<v Speaker 15>people because it helps build the immune system, and it

968
00:53:11.679 --> 00:53:15.079
<v Speaker 15>can be truly miraculous for someone fighting a potentially life

969
00:53:15.079 --> 00:53:18.639
<v Speaker 15>threatening disease due to an infection, diabetes, or cancer. The

970
00:53:18.679 --> 00:53:21.920
<v Speaker 15>tea is also organic and naturally caffeine free. A one

971
00:53:21.960 --> 00:53:24.239
<v Speaker 15>pound package of tea is forty nine to ninety five,

972
00:53:24.280 --> 00:53:27.519
<v Speaker 15>which includes shipping. To order, please visit to Hebotea Club

973
00:53:27.559 --> 00:53:30.239
<v Speaker 15>dot com. T hebo is spelled tea like tom, a,

974
00:53:30.800 --> 00:53:34.239
<v Speaker 15>h ee b like boy o. They continue with the

975
00:53:34.239 --> 00:53:37.199
<v Speaker 15>word t and then the word club. The complete website

976
00:53:37.320 --> 00:53:39.960
<v Speaker 15>is to hebot club dot com or call us at

977
00:53:39.960 --> 00:53:43.039
<v Speaker 15>eight one eight six one zero eight zero eight eight

978
00:53:43.280 --> 00:53:46.760
<v Speaker 15>Monday through Saturday nine am to five pm California time.

979
00:53:46.880 --> 00:53:49.800
<v Speaker 15>That's eight one eight six one zero eight zero eight

980
00:53:49.920 --> 00:53:52.800
<v Speaker 15>eight to Hebot club dot com.

981
00:53:53.239 --> 00:53:56.159
<v Speaker 16>Tune into the Faran Doozier show us you Mark the

982
00:53:56.199 --> 00:53:59.519
<v Speaker 16>Place in Time the soundtrack to Life Sunday nights at

983
00:53:59.559 --> 00:54:03.519
<v Speaker 16>eight pm on KCAA Radio, playing the hottest hits and

984
00:54:03.639 --> 00:54:07.559
<v Speaker 16>the coolest conversations. Sunday nights at apm on the ferand

985
00:54:07.559 --> 00:54:12.679
<v Speaker 16>Dozier Show with an array of music, talk, sports, community outreach,

986
00:54:12.960 --> 00:54:19.000
<v Speaker 16>and veteran resources. With the hits from the sixties, seventies, eighties, nineties,

987
00:54:19.159 --> 00:54:23.360
<v Speaker 16>and today's hits. The Farran Dozier Show on KCAA Radio

988
00:54:24.119 --> 00:54:28.280
<v Speaker 16>on all available streaming platforms and on a six point

989
00:54:28.280 --> 00:54:32.239
<v Speaker 16>five m and ten fifty Am The ferand Dozier Show

990
00:54:32.519 --> 00:54:46.119
<v Speaker 16>on KCAA Radio.

991
00:54:49.079 --> 00:54:52.360
<v Speaker 11>This important, time sensitive message is brought to you by

992
00:54:52.559 --> 00:54:56.760
<v Speaker 11>this station's generous sponsor, George Let's Field Associates, who has

993
00:54:56.800 --> 00:55:01.519
<v Speaker 11>important Medicare information for all current and future Medicare recipients

994
00:55:01.800 --> 00:55:06.639
<v Speaker 11>about some big changes happening. Medicare Clarified. Medicare is a

995
00:55:06.679 --> 00:55:08.840
<v Speaker 11>nonprofit consumer service organization.

996
00:55:09.320 --> 00:55:12.480
<v Speaker 13>It's more important than ever to review your Medicare plan

997
00:55:12.599 --> 00:55:16.440
<v Speaker 13>for twenty twenty five from October fifteenth through December seventh

998
00:55:16.480 --> 00:55:18.639
<v Speaker 13>to find out if you're in the right plan for you.

999
00:55:18.920 --> 00:55:22.800
<v Speaker 13>People are calling nine five one seven six nine zero

1000
00:55:23.119 --> 00:55:27.440
<v Speaker 13>zero zero five nine five one seven six nine zero

1001
00:55:27.760 --> 00:55:32.360
<v Speaker 13>zero zero five. A popular and local Medicare plan is improving.

1002
00:55:32.559 --> 00:55:36.679
<v Speaker 13>Others are raising copays and adding deductibles, biggest changes in

1003
00:55:36.719 --> 00:55:40.039
<v Speaker 13>the Medicare drug program in fifteen years.

1004
00:55:40.599 --> 00:55:43.599
<v Speaker 11>We thank George Letzfield and lets Field Insurance for their

1005
00:55:43.719 --> 00:55:45.800
<v Speaker 11>generous support of this radio station.

1006
00:55:55.800 --> 00:56:00.920
<v Speaker 17>Here's the KCAA community calendar for March. On most Friday nights,

1007
00:56:00.960 --> 00:56:04.960
<v Speaker 17>it's open mic and karaoke in Riverside at Urrel Brewing Company,

1008
00:56:05.039 --> 00:56:08.639
<v Speaker 17>located on Chicago Avenue beginning at seven pm, So grab

1009
00:56:08.719 --> 00:56:11.480
<v Speaker 17>the mic and have some fun. In downtown Redlands on

1010
00:56:11.519 --> 00:56:14.719
<v Speaker 17>Saturday mornings from nine to one pm, it's the Downtown

1011
00:56:14.800 --> 00:56:19.320
<v Speaker 17>Morning Market located between six and eighth Street. On Saturday mornings,

1012
00:56:19.360 --> 00:56:22.599
<v Speaker 17>in the Riverside Main Library on Mission Avenue, it's Family

1013
00:56:22.679 --> 00:56:27.519
<v Speaker 17>Storytime every Saturday morning at nine thirty. For car enthusiasts,

1014
00:56:27.599 --> 00:56:30.280
<v Speaker 17>here are a couple of options to enjoy cars and

1015
00:56:30.360 --> 00:56:33.639
<v Speaker 17>coffee in downtown Clarmat on the first Saturday of the month,

1016
00:56:33.920 --> 00:56:36.920
<v Speaker 17>the Claremont Car Guys and Gals. They meet in the

1017
00:56:37.000 --> 00:56:40.440
<v Speaker 17>village for coffee and cars at six thirty am. I

1018
00:56:40.480 --> 00:56:43.639
<v Speaker 17>hope you're an early riser. In Corona, it's more cars

1019
00:56:43.639 --> 00:56:46.800
<v Speaker 17>and coffee on Saturday mornings from seven am to nine

1020
00:56:46.800 --> 00:56:50.639
<v Speaker 17>am at the IHOP on Ward Low Road. All years

1021
00:56:50.679 --> 00:56:53.840
<v Speaker 17>makes and models are welcome. This weekly meetup allows you

1022
00:56:53.920 --> 00:56:58.000
<v Speaker 17>to enjoy some beautiful cars. Looking to do some household

1023
00:56:58.039 --> 00:57:01.599
<v Speaker 17>hazardous clean up in Royale, so they offer a hazardous

1024
00:57:01.599 --> 00:57:05.880
<v Speaker 17>waste drop off on March first, March fourteenth, fifteenth, and

1025
00:57:06.000 --> 00:57:09.559
<v Speaker 17>June thirteenth from eight am till noon. The drop off

1026
00:57:09.599 --> 00:57:13.400
<v Speaker 17>site is located at two forty six South Willow And

1027
00:57:13.519 --> 00:57:16.760
<v Speaker 17>for those of you who love Pokemon in Redlands, there

1028
00:57:16.920 --> 00:57:20.159
<v Speaker 17>is a board game Teradise. Every Friday night at six

1029
00:57:20.280 --> 00:57:24.519
<v Speaker 17>thirty pm is their weekly Pokemon tournament. All skill levels

1030
00:57:24.519 --> 00:57:26.880
<v Speaker 17>are welcome, but you do need to have a full

1031
00:57:26.960 --> 00:57:30.440
<v Speaker 17>understanding of the rules and how to play. Located at

1032
00:57:30.519 --> 00:57:34.440
<v Speaker 17>one oh nine East State Street in Suite A in Redlands,

1033
00:57:34.840 --> 00:57:38.679
<v Speaker 17>and that's the latest for the KCAA community calendar. I'm

1034
00:57:38.719 --> 00:57:42.800
<v Speaker 17>Lillian Vasquez on KCAA ten fifty am and one oh

1035
00:57:42.880 --> 00:57:46.400
<v Speaker 17>six point five FM.

1036
00:57:46.880 --> 00:57:50.800
<v Speaker 1>Located in the heart of San Bernardino, California, the Teamsters

1037
00:57:50.880 --> 00:57:54.719
<v Speaker 1>Local nineteen thirty two Training Center is designed to train

1038
00:57:54.840 --> 00:57:59.079
<v Speaker 1>workers for high demand, good paying jobs and various industries

1039
00:57:59.119 --> 00:58:02.559
<v Speaker 1>throughout the lane An Empire. If you want a pathway

1040
00:58:02.599 --> 00:58:05.440
<v Speaker 1>to a high paying job and the respect that comes

1041
00:58:05.440 --> 00:58:10.000
<v Speaker 1>with a union contract, visit nineteen thirty two Trainingcenter dot

1042
00:58:10.119 --> 00:58:15.519
<v Speaker 1>org to enroll today. That's nineteen thirty two Trainingcenter dot Org.

1043
00:58:21.320 --> 00:58:24.920
<v Speaker 8>NBC News Radio. I'm Chris Ragio. House Republicans are unveiling

1044
00:58:24.960 --> 00:58:27.559
<v Speaker 8>a short term funding bill to keep the government running

1045
00:58:27.599 --> 00:58:28.400
<v Speaker 8>through September.

1046
00:58:28.519 --> 00:58:29.960
<v Speaker 4>Details now from Lisa Carton.

1047
00:58:30.079 --> 00:58:33.239
<v Speaker 18>The six month plan includes cuts to non defense programs

1048
00:58:33.280 --> 00:58:35.920
<v Speaker 18>and the IRS. The ninety nine page bill is in

1049
00:58:35.960 --> 00:58:38.840
<v Speaker 18>the form of a continuing resolution known as a CR,

1050
00:58:38.960 --> 00:58:42.639
<v Speaker 18>which Democrats strongly oppose. House leaders say the bill has

1051
00:58:42.679 --> 00:58:46.519
<v Speaker 18>White House support ahead of Friday shutdown deadline. Speaker Mike

1052
00:58:46.639 --> 00:58:49.639
<v Speaker 18>Johnson said this week he thinks Republicans will be able

1053
00:58:49.679 --> 00:58:52.400
<v Speaker 18>to pass it along party lines, with a floor vote

1054
00:58:52.440 --> 00:58:54.320
<v Speaker 18>expected as soon as Tuesday.

1055
00:58:54.440 --> 00:58:57.039
<v Speaker 8>The Trump administration is cutting four hundred million dollars in

1056
00:58:57.079 --> 00:59:01.039
<v Speaker 8>grants for Columbia University over pro Palestinian pro tests. Education

1057
00:59:01.159 --> 00:59:04.960
<v Speaker 8>Secretary Linda McMahon defended the move, citing anti semitism at

1058
00:59:04.960 --> 00:59:07.960
<v Speaker 8>New York City's Ivy League University. She said Jewish students

1059
00:59:07.960 --> 00:59:11.800
<v Speaker 8>have faced relentless violence, intimidation, and harassment following the deadly

1060
00:59:11.840 --> 00:59:15.079
<v Speaker 8>Hamas October seventh, twenty twenty three attack on Israel. Since

1061
00:59:15.199 --> 00:59:17.519
<v Speaker 8>last spring, the school has been a hotbed of pro

1062
00:59:17.559 --> 00:59:22.119
<v Speaker 8>Palestinian protests, which have often turned violent. An unusual standoff

1063
00:59:22.119 --> 00:59:24.760
<v Speaker 8>in London today as a man carrying a Palestinian flag

1064
00:59:25.079 --> 00:59:28.400
<v Speaker 8>has been perched on a ledge on Big Ben's Elizabeth.

1065
00:59:27.920 --> 00:59:29.159
<v Speaker 1>Tower for over ten hours.

1066
00:59:29.280 --> 00:59:32.639
<v Speaker 8>Metropolitan Police say they've received a report about the unidentified

1067
00:59:32.679 --> 00:59:36.079
<v Speaker 8>man this morning, shortly before seven thirty London time. The

1068
00:59:36.119 --> 00:59:38.880
<v Speaker 8>BBC reports the man posted a video of his climb

1069
00:59:38.920 --> 00:59:42.519
<v Speaker 8>up and said he's protesting against police repression and state violence.

1070
00:59:42.760 --> 00:59:45.440
<v Speaker 8>Area roads and tours of Parliament have been canceled as

1071
00:59:45.480 --> 00:59:48.679
<v Speaker 8>emergency crews and police negotiators try to talk them down.

1072
00:59:48.840 --> 00:59:51.239
<v Speaker 8>It's unclear if the climber is directly connected with pro

1073
00:59:51.280 --> 00:59:54.559
<v Speaker 8>Palestinian protesters who were in the vicinity for u planned rally.

1074
00:59:54.679 --> 00:59:57.639
<v Speaker 8>The Vatican says Pope Francis has shown a gradual slight

1075
00:59:57.679 --> 01:00:00.039
<v Speaker 8>improvement over the last few days. Over the weekend, the

1076
01:00:00.079 --> 01:00:04.000
<v Speaker 8>Vatican said the Pope's oxygen exchange has improved, he doesn't

1077
01:00:04.000 --> 01:00:07.119
<v Speaker 8>have a fever, and blood contests remained stable. The eighty

1078
01:00:07.119 --> 01:00:09.239
<v Speaker 8>eight year old went into a Rome hospital with
