WEBVTT

1
00:00:00.160 --> 00:00:04.200
<v Speaker 1>Private, discrete, Rise Airport runs, sight saying, proms, weddings and

2
00:00:04.320 --> 00:00:07.160
<v Speaker 1>romantic date nights are all ahead in your future with

3
00:00:07.240 --> 00:00:11.439
<v Speaker 1>Lux Transportation, karaoke, disability friendly and no problem. We're also

4
00:00:11.480 --> 00:00:14.279
<v Speaker 1>senior citizen friendly too. Call it text Mister Holland is

5
00:00:14.320 --> 00:00:16.160
<v Speaker 1>to take away the stress at nine five to one

6
00:00:16.280 --> 00:00:19.559
<v Speaker 1>three nine nine five four two five. That's nine five

7
00:00:19.679 --> 00:00:23.280
<v Speaker 1>one three nine nine five four two five Lux Transportation.

8
00:00:23.440 --> 00:00:25.120
<v Speaker 1>When you need the absolute.

9
00:00:24.600 --> 00:00:29.480
<v Speaker 2>Best, Killustina KCAA Low Melinda at one O six point

10
00:00:29.559 --> 00:00:32.320
<v Speaker 2>five FM K two ninety three c F Burrito Valley.

11
00:00:33.039 --> 00:00:36.600
<v Speaker 3>The information economy has a ride. The world is teeming

12
00:00:36.640 --> 00:00:40.880
<v Speaker 3>with innovation as new business models reinvent every industry industry.

13
00:00:40.960 --> 00:00:45.280
<v Speaker 3>Inside Analysis is your source of information and insights about

14
00:00:45.280 --> 00:00:47.840
<v Speaker 3>how to make the most of this exciting new era.

15
00:00:48.079 --> 00:00:52.240
<v Speaker 3>Learn more at inside analysis dot com, insideanalysis dot com.

16
00:00:52.280 --> 00:00:55.200
<v Speaker 3>And now here's your host, Eric Kavanaugh.

17
00:00:59.759 --> 00:01:02.320
<v Speaker 4>All right, ladies and gentlemen, Hello and welcome to the

18
00:01:02.359 --> 00:01:05.439
<v Speaker 4>only coast to coast radio show all about the information economy.

19
00:01:05.480 --> 00:01:08.239
<v Speaker 4>It's called Inside Analysis or True Layer Kavan. I hear

20
00:01:08.519 --> 00:01:12.239
<v Speaker 4>with my old buddy from ages ago. We haven't seen

21
00:01:12.280 --> 00:01:15.359
<v Speaker 4>each other in like fifteen years time fliers. We're having fun.

22
00:01:15.599 --> 00:01:20.480
<v Speaker 4>Mark Pico, he is quite the innovator. He's taught at TDWY,

23
00:01:20.560 --> 00:01:22.920
<v Speaker 4>He's taught all sorts of different classes, and he's a

24
00:01:22.920 --> 00:01:25.560
<v Speaker 4>real thinker. And so we were talking earlier about the

25
00:01:25.599 --> 00:01:29.480
<v Speaker 4>whole concept of value and what is value. People say,

26
00:01:29.519 --> 00:01:31.799
<v Speaker 4>when you're pushing a project, oh, there's no value? Well

27
00:01:31.920 --> 00:01:33.760
<v Speaker 4>what do you mean by that? So I'll just throw

28
00:01:33.799 --> 00:01:36.239
<v Speaker 4>it over to you to kind of dive in on that, Mark.

29
00:01:36.599 --> 00:01:40.239
<v Speaker 4>Value is this concept that everyone thinks they know, everyone

30
00:01:40.239 --> 00:01:42.719
<v Speaker 4>thinks they understand, but once you start kind of drilling down,

31
00:01:43.040 --> 00:01:44.439
<v Speaker 4>it could be hard to define. Right.

32
00:01:45.000 --> 00:01:48.079
<v Speaker 5>That's so true, Eric, I guess whatgind me thinking with

33
00:01:48.159 --> 00:01:51.000
<v Speaker 5>this over the last little while. As there's many themes

34
00:01:51.000 --> 00:01:54.719
<v Speaker 5>of blogs and webinars and presentations that say, we you know,

35
00:01:54.799 --> 00:01:58.359
<v Speaker 5>the failure rate of data related projects is pretty high.

36
00:01:58.519 --> 00:02:01.920
<v Speaker 5>Why value wasn't created? I think, what what does that

37
00:02:01.959 --> 00:02:05.519
<v Speaker 5>actually mean? Value? I'm not an economist, I'm not a

38
00:02:05.519 --> 00:02:08.520
<v Speaker 5>financial person. I started thinking, how can I think about

39
00:02:08.599 --> 00:02:12.319
<v Speaker 5>value in a way that unifies people's thinking? And I

40
00:02:12.319 --> 00:02:16.360
<v Speaker 5>started thinking value is something I care about. And when

41
00:02:16.400 --> 00:02:19.879
<v Speaker 5>I say I there's different types of people as stakeholders

42
00:02:19.919 --> 00:02:22.439
<v Speaker 5>that care about different things, So how do we think

43
00:02:22.479 --> 00:02:26.520
<v Speaker 5>about value from Department AD to Department B to Department C.

44
00:02:27.479 --> 00:02:32.879
<v Speaker 5>That unifies the flow and connection between these. So I've

45
00:02:32.919 --> 00:02:38.680
<v Speaker 5>started thinking about thinking about value as something created if

46
00:02:38.719 --> 00:02:42.240
<v Speaker 5>my objectives are meant it. Those objectives mean I personally

47
00:02:42.240 --> 00:02:45.319
<v Speaker 5>care about this happening, right, And I started to think

48
00:02:45.319 --> 00:02:47.319
<v Speaker 5>about what are the different things we care about in companies?

49
00:02:48.199 --> 00:02:51.840
<v Speaker 5>And I'm taking further from a data driven lens, you know,

50
00:02:51.879 --> 00:02:55.159
<v Speaker 5>because I've given talks before and you know about data governance.

51
00:02:55.159 --> 00:02:57.800
<v Speaker 5>So people say, well, where's the value of data governance?

52
00:02:57.840 --> 00:03:00.759
<v Speaker 5>I think, what are you really asking? What does that mean?

53
00:03:01.800 --> 00:03:06.599
<v Speaker 5>So I started thinking about conductivity and flow in companies,

54
00:03:06.759 --> 00:03:09.919
<v Speaker 5>and I started thinking about value as something has a

55
00:03:09.919 --> 00:03:12.520
<v Speaker 5>life cycle to it and it exists in different kinds

56
00:03:12.560 --> 00:03:16.120
<v Speaker 5>of stages. And I started thinking about how do I

57
00:03:16.240 --> 00:03:21.400
<v Speaker 5>organize this in a way that's simple and meaningful. So

58
00:03:21.439 --> 00:03:23.400
<v Speaker 5>I coined the term that I'm kind of building out

59
00:03:23.400 --> 00:03:27.479
<v Speaker 5>something called value literacy, right, And value literacy means literacy

60
00:03:27.520 --> 00:03:30.599
<v Speaker 5>if anything, means I can have a conversation with you

61
00:03:30.599 --> 00:03:33.560
<v Speaker 5>about it because I know the concepts, I know the vocabulary.

62
00:03:34.199 --> 00:03:36.719
<v Speaker 5>So this means if I know how to converse with

63
00:03:36.759 --> 00:03:39.360
<v Speaker 5>my stakeholders, we should have something in common to discuss.

64
00:03:40.520 --> 00:03:42.360
<v Speaker 5>And if we think about the different kinds of people

65
00:03:43.680 --> 00:03:47.199
<v Speaker 5>that work in the data field within a company, it's

66
00:03:47.319 --> 00:03:50.960
<v Speaker 5>very very broad and very very diverse. And I started

67
00:03:51.000 --> 00:03:52.919
<v Speaker 5>thinking about this. I don't know what organize this in

68
00:03:52.919 --> 00:03:55.759
<v Speaker 5>a way that's kind of simple yet meaningful, and I

69
00:03:55.759 --> 00:03:59.360
<v Speaker 5>started creating. My first thinking was, let's think about value,

70
00:03:59.439 --> 00:04:03.400
<v Speaker 5>like like energy, like charging a battery. When you charge

71
00:04:03.400 --> 00:04:07.400
<v Speaker 5>a battery, you're creating potential energy. But if that battery

72
00:04:07.400 --> 00:04:10.000
<v Speaker 5>is never been used for anything, it's there, but nobody's

73
00:04:10.080 --> 00:04:13.439
<v Speaker 5>using it. But when we use that battery in our

74
00:04:13.520 --> 00:04:17.480
<v Speaker 5>phone or in a device, maybe something's now coming on.

75
00:04:18.480 --> 00:04:20.759
<v Speaker 5>And so that's kinetic energy. You can now use your phone.

76
00:04:21.480 --> 00:04:25.439
<v Speaker 5>It's kinetic value because you're turning the potential into something actionable.

77
00:04:26.360 --> 00:04:28.480
<v Speaker 5>But people don't really care about having the phone turned on.

78
00:04:28.560 --> 00:04:31.439
<v Speaker 5>What they care about is booking an order on Amazon

79
00:04:31.480 --> 00:04:34.560
<v Speaker 5>with it, or communicating with their family or watching a video.

80
00:04:35.160 --> 00:04:37.079
<v Speaker 5>So what they really care about is the use you

81
00:04:37.160 --> 00:04:40.560
<v Speaker 5>have because the phone's on, And I call that realized value.

82
00:04:41.120 --> 00:04:46.519
<v Speaker 5>So you go from potential kinetic to realized. Now potential

83
00:04:46.639 --> 00:04:50.720
<v Speaker 5>is like raising data quality, building a data product, building

84
00:04:50.720 --> 00:04:55.079
<v Speaker 5>a report. Kinetic energy or kinetic value happens when you

85
00:04:55.240 --> 00:04:58.199
<v Speaker 5>use that to drive a process. So if I have

86
00:04:58.240 --> 00:05:00.920
<v Speaker 5>information to say, how do I scal do my salespeople,

87
00:05:01.720 --> 00:05:04.519
<v Speaker 5>or how to allocate my resources, I can now turn

88
00:05:04.560 --> 00:05:08.720
<v Speaker 5>that into a better process. The realized value happens because

89
00:05:08.759 --> 00:05:11.879
<v Speaker 5>you've done that. It's now you've got happier customers, you've

90
00:05:11.879 --> 00:05:14.839
<v Speaker 5>got more revenue, and you've turned this into that flow.

91
00:05:15.319 --> 00:05:18.600
<v Speaker 5>But there's two more building blocks of this. There's something

92
00:05:18.600 --> 00:05:22.360
<v Speaker 5>I'm calling structural value, which is really what data governance prepares.

93
00:05:22.959 --> 00:05:25.800
<v Speaker 5>And structural value is the creation of standards and policies

94
00:05:27.160 --> 00:05:30.319
<v Speaker 5>and they then enable you to then do data quality

95
00:05:30.360 --> 00:05:33.600
<v Speaker 5>to raise the potential value of potential value data. But

96
00:05:33.639 --> 00:05:35.240
<v Speaker 5>there's one other thing we care about its companies. That's

97
00:05:35.319 --> 00:05:39.720
<v Speaker 5>being revolui, dealing with risks, dealing with bad weather events

98
00:05:39.959 --> 00:05:45.879
<v Speaker 5>with you, technology failing or whatever, or safety issues. So

99
00:05:46.439 --> 00:05:50.360
<v Speaker 5>the fifth one I've called is resilient value. Now, each

100
00:05:50.399 --> 00:05:55.519
<v Speaker 5>of these things or value domains are created by something

101
00:05:55.560 --> 00:06:01.160
<v Speaker 5>called capabilities, but some value is also enabled other capabilities.

102
00:06:01.240 --> 00:06:04.959
<v Speaker 5>So if you think about the world of data, think

103
00:06:05.000 --> 00:06:08.800
<v Speaker 5>about data generation as a capability. I get data because

104
00:06:08.839 --> 00:06:12.319
<v Speaker 5>I acquire it. I enter it into my screens. I

105
00:06:12.480 --> 00:06:15.560
<v Speaker 5>measured it from my plant, but somehow I generate data.

106
00:06:16.560 --> 00:06:19.279
<v Speaker 5>Then I advocapability to manage that data. I've got a

107
00:06:19.360 --> 00:06:22.439
<v Speaker 5>store and provision it, integrate it, protect it, make it

108
00:06:22.480 --> 00:06:26.120
<v Speaker 5>all the stuff available for others to use. Those are

109
00:06:26.160 --> 00:06:29.399
<v Speaker 5>both enabled by data governance capabilities in others that I

110
00:06:29.680 --> 00:06:32.319
<v Speaker 5>can actually because I position data governance as abilit to

111
00:06:32.360 --> 00:06:36.000
<v Speaker 5>share data right now. If I can share data and

112
00:06:36.000 --> 00:06:39.879
<v Speaker 5>as provisioned, the next capability there is called data consumption.

113
00:06:40.480 --> 00:06:42.480
<v Speaker 5>I can use the data that was provisioned because it

114
00:06:42.519 --> 00:06:45.680
<v Speaker 5>followed the policies, and now I can consume it and

115
00:06:45.680 --> 00:06:47.759
<v Speaker 5>however form. I'm a data scientist or an analyst or

116
00:06:47.800 --> 00:06:50.199
<v Speaker 5>whatever I am, and I'm now interpreting the data. I'm

117
00:06:50.199 --> 00:06:52.839
<v Speaker 5>consuming it to make a recommendation to my boss or

118
00:06:52.839 --> 00:06:56.519
<v Speaker 5>a decision maker. The last piece, or not really the last,

119
00:06:56.560 --> 00:06:58.839
<v Speaker 5>but the second last piece, is something called data utilization.

120
00:06:59.560 --> 00:07:02.800
<v Speaker 5>It's the data and acting on it. So I've scheduled

121
00:07:02.839 --> 00:07:06.040
<v Speaker 5>my staff at my restaurant better, I've got my salespeople

122
00:07:06.120 --> 00:07:09.319
<v Speaker 5>more allocated, I've got my plant with more reliability, and

123
00:07:09.360 --> 00:07:13.199
<v Speaker 5>now my output of my company is better. That's the utilization.

124
00:07:13.279 --> 00:07:16.600
<v Speaker 5>It creates the realized value. The last piece of the puzzle,

125
00:07:16.639 --> 00:07:19.839
<v Speaker 5>I believe is something called data leadership capabilities. They're the

126
00:07:19.839 --> 00:07:22.879
<v Speaker 5>ones that set the tone for why this is so important.

127
00:07:23.199 --> 00:07:27.040
<v Speaker 5>So data leadership. Without that, these things won't connect. They're

128
00:07:27.120 --> 00:07:31.000
<v Speaker 5>isolated silos. But if you take a step back, just

129
00:07:31.000 --> 00:07:33.240
<v Speaker 5>like you're charging your battery so you can run your

130
00:07:33.240 --> 00:07:35.240
<v Speaker 5>phone so you can order off of Amazon and have

131
00:07:35.279 --> 00:07:38.439
<v Speaker 5>a nice book to read, that flow, in my view,

132
00:07:38.480 --> 00:07:42.519
<v Speaker 5>is what value can be modeled as. And so if

133
00:07:42.560 --> 00:07:45.240
<v Speaker 5>I'm working in it, or I'm working in marketing, I'm

134
00:07:45.240 --> 00:07:48.759
<v Speaker 5>working in HR, we all see this differently. But yet

135
00:07:48.800 --> 00:07:50.519
<v Speaker 5>if we all say we're failing because there's no value

136
00:07:50.519 --> 00:07:53.639
<v Speaker 5>being produced, we need to know which of those five

137
00:07:53.680 --> 00:07:56.399
<v Speaker 5>types of value are we talking about it? Because the

138
00:07:56.399 --> 00:08:00.399
<v Speaker 5>word value isn't precise enough, and we just come plane,

139
00:08:00.399 --> 00:08:02.839
<v Speaker 5>we whine about it, it's not working, and we point

140
00:08:02.839 --> 00:08:05.839
<v Speaker 5>fingers and we walk away. If we can talk about

141
00:08:05.879 --> 00:08:08.720
<v Speaker 5>it with a nice, simple picture about how it's connected,

142
00:08:09.120 --> 00:08:12.240
<v Speaker 5>we can realize it's breaking here because of that interesting

143
00:08:12.439 --> 00:08:15.199
<v Speaker 5>and that's my premise. And to take this one step further,

144
00:08:16.040 --> 00:08:18.879
<v Speaker 5>I'm working to models in a graph database. So I

145
00:08:18.959 --> 00:08:23.040
<v Speaker 5>have some nodes our value items and some nodes or

146
00:08:23.079 --> 00:08:25.720
<v Speaker 5>capability items, and if we can see how they're connected

147
00:08:26.240 --> 00:08:28.800
<v Speaker 5>and go to a workshop with our stakeholders, we can

148
00:08:28.920 --> 00:08:33.360
<v Speaker 5>have conversations around why is it not flowing, where's the bottleneck,

149
00:08:33.399 --> 00:08:37.759
<v Speaker 5>where's the where's the where's the speed bumps? And that's

150
00:08:37.919 --> 00:08:40.120
<v Speaker 5>that's where I'm kind of at with this.

151
00:08:40.120 --> 00:08:42.320
<v Speaker 4>This is very interesting. I like the fact that you're

152
00:08:42.759 --> 00:08:46.679
<v Speaker 4>trying to dig into a better understanding of what value

153
00:08:46.759 --> 00:08:51.399
<v Speaker 4>really is because typically when people think value, they think, Okay, ROI,

154
00:08:51.879 --> 00:08:55.320
<v Speaker 4>what's the return on investment for this data governance project?

155
00:08:55.360 --> 00:08:57.759
<v Speaker 4>And the answer would be something like, well, our customer

156
00:08:57.840 --> 00:09:02.000
<v Speaker 4>satisfaction has gone on twenty percent. Our upsell capability has

157
00:09:02.039 --> 00:09:04.759
<v Speaker 4>gone up because the customers are more satisfied. So that's

158
00:09:04.759 --> 00:09:07.159
<v Speaker 4>the case where you can kind of track some monetary

159
00:09:07.240 --> 00:09:10.679
<v Speaker 4>value from the blocking and tackling work you did, which

160
00:09:10.720 --> 00:09:14.279
<v Speaker 4>is not very fun improving your data quality. That's true, ROI.

161
00:09:14.720 --> 00:09:17.960
<v Speaker 4>But to a deeper point, I think you are enabling

162
00:09:18.320 --> 00:09:22.799
<v Speaker 4>much more productive conversations about what to do next, because

163
00:09:22.799 --> 00:09:25.200
<v Speaker 4>that's really what every business person is trying to figure out,

164
00:09:25.360 --> 00:09:28.080
<v Speaker 4>what do I do next in order to get new

165
00:09:28.120 --> 00:09:31.200
<v Speaker 4>business satisfy the business I have. Whatever the case may be,

166
00:09:31.639 --> 00:09:35.200
<v Speaker 4>it's always pretty darn unwieldy, whether it is trying to

167
00:09:35.240 --> 00:09:37.720
<v Speaker 4>figure out a new market to approach, trying to figure

168
00:09:37.720 --> 00:09:39.480
<v Speaker 4>out a new product to roll out, a new service

169
00:09:39.519 --> 00:09:44.120
<v Speaker 4>to roll out. These are deep gritty questions that you

170
00:09:44.120 --> 00:09:46.799
<v Speaker 4>don't get answers to very easily, very quickly. And then

171
00:09:46.879 --> 00:09:49.279
<v Speaker 4>the other side of the equation is you kind of

172
00:09:49.320 --> 00:09:51.320
<v Speaker 4>never know. Like I remember what I learned the concept

173
00:09:51.320 --> 00:09:54.080
<v Speaker 4>of opportunity costs. I was like, oh, wow, yeah, that's

174
00:09:54.080 --> 00:09:56.000
<v Speaker 4>pretty interesting. So if I'm working on this, I'm not

175
00:09:56.039 --> 00:09:59.159
<v Speaker 4>working on that. There's a cost of not working on

176
00:09:59.200 --> 00:10:02.279
<v Speaker 4>something as opposed to cost of working on something. So

177
00:10:02.360 --> 00:10:05.000
<v Speaker 4>what is the opportunity cost? What are you missing? All

178
00:10:05.080 --> 00:10:07.320
<v Speaker 4>these things come out, and I'll give you an interesting example.

179
00:10:07.360 --> 00:10:10.480
<v Speaker 4>I learned a risk management conference years ago. I was

180
00:10:10.519 --> 00:10:13.240
<v Speaker 4>talking to these big bankers and they're all trying to

181
00:10:13.279 --> 00:10:16.440
<v Speaker 4>figure out how to hedge their bets, how to move

182
00:10:16.519 --> 00:10:20.080
<v Speaker 4>forward in a safe but effective manner in a very

183
00:10:20.559 --> 00:10:23.840
<v Speaker 4>dynamic world, which is financial services. And I said, you know,

184
00:10:23.919 --> 00:10:28.080
<v Speaker 4>don't you find that sometimes, like voting a certain way

185
00:10:28.759 --> 00:10:32.360
<v Speaker 4>will cause personal tension, Like people take things personally and

186
00:10:32.360 --> 00:10:34.879
<v Speaker 4>they get upset about stuff. And he goes guy said,

187
00:10:34.919 --> 00:10:37.039
<v Speaker 4>that's a very good point. That's why on our boards

188
00:10:37.279 --> 00:10:40.879
<v Speaker 4>we either concur or don't concur. So it's like we

189
00:10:40.919 --> 00:10:43.639
<v Speaker 4>don't even really say yes or no. We either concur

190
00:10:43.799 --> 00:10:46.240
<v Speaker 4>with the assessment that you've made, or we don't concur.

191
00:10:46.360 --> 00:10:49.039
<v Speaker 4>So it's a softer way of kind of getting around

192
00:10:49.320 --> 00:10:52.440
<v Speaker 4>the rough spots of conversations. And I kind of feel

193
00:10:52.440 --> 00:10:57.159
<v Speaker 4>like what you're building is that softening but clarifying structure,

194
00:10:57.200 --> 00:10:59.799
<v Speaker 4>almost like an emulsifier or something. What do you think?

195
00:11:00.080 --> 00:11:02.519
<v Speaker 5>I agree? I think it's stimular to have a conversation.

196
00:11:03.440 --> 00:11:05.399
<v Speaker 5>I think if you don't have literacy on a topic,

197
00:11:06.159 --> 00:11:08.919
<v Speaker 5>you can't converse about it. I'm a real basketball fan,

198
00:11:09.360 --> 00:11:11.799
<v Speaker 5>so if I'm talking to a person about basketball, or

199
00:11:11.840 --> 00:11:15.320
<v Speaker 5>they don't understand what's important in basketball, they may know

200
00:11:15.360 --> 00:11:17.360
<v Speaker 5>the words, but they don't have a conversation because they

201
00:11:17.399 --> 00:11:20.279
<v Speaker 5>don't know what's important. Right. And so you can literacy

202
00:11:20.320 --> 00:11:25.600
<v Speaker 5>on any topic, and you need concepts and vocabulary and

203
00:11:25.679 --> 00:11:27.879
<v Speaker 5>some sort of an underlying model that kind of connects them.

204
00:11:28.080 --> 00:11:31.639
<v Speaker 4>Right, that's cool. That's cool. So now you're building out

205
00:11:31.840 --> 00:11:35.759
<v Speaker 4>will this be something you'll give speeches about and consult

206
00:11:35.759 --> 00:11:37.799
<v Speaker 4>with organizations? Essentially? Is that the vision.

207
00:11:38.320 --> 00:11:40.440
<v Speaker 5>My goal is that I've been working on this now

208
00:11:40.480 --> 00:11:42.879
<v Speaker 5>on a part time basis, make you since late last year,

209
00:11:42.960 --> 00:11:45.159
<v Speaker 5>maybe around November I started. I've been thinking about it

210
00:11:45.159 --> 00:11:47.360
<v Speaker 5>for a long time, but I got kind of really

211
00:11:47.399 --> 00:11:49.279
<v Speaker 5>serious about it late last year. My goal is to

212
00:11:49.279 --> 00:11:53.879
<v Speaker 5>build maybe workshop content where we can assess and diagnose

213
00:11:54.360 --> 00:11:57.440
<v Speaker 5>your values trapped and why. So rather than complain about

214
00:11:57.480 --> 00:11:59.519
<v Speaker 5>values not happening, let's assess in the term of what

215
00:11:59.559 --> 00:12:01.679
<v Speaker 5>to do about it there. So I'd like to turn

216
00:12:01.679 --> 00:12:04.440
<v Speaker 5>it into workshop material. I've already given a presentation last

217
00:12:04.480 --> 00:12:08.519
<v Speaker 5>week to a group of CEOs to kind of position

218
00:12:08.639 --> 00:12:11.960
<v Speaker 5>the idea. So that's my goal is to build education

219
00:12:12.039 --> 00:12:15.480
<v Speaker 5>content right now. Maybe it's some consulting and definitely workshop

220
00:12:15.480 --> 00:12:18.200
<v Speaker 5>content kind of things right, But I also parallel one

221
00:12:18.200 --> 00:12:20.519
<v Speaker 5>more thing I think of I think of the word

222
00:12:20.600 --> 00:12:23.159
<v Speaker 5>data literacy is kind of too narrow. I think of

223
00:12:23.240 --> 00:12:25.639
<v Speaker 5>the word data storytelling was too narrow. I do a

224
00:12:25.639 --> 00:12:28.240
<v Speaker 5>lot of work in data storytelling, but I think it

225
00:12:28.279 --> 00:12:31.639
<v Speaker 5>is better talking about value storytelling because if we can

226
00:12:31.679 --> 00:12:34.360
<v Speaker 5>talk about value, we can have a conversation at a

227
00:12:34.399 --> 00:12:37.360
<v Speaker 5>higher level. Data is simply a component. It's not the

228
00:12:37.399 --> 00:12:39.960
<v Speaker 5>be all and end all. It's the value we're trying

229
00:12:39.960 --> 00:12:42.240
<v Speaker 5>to create by as it flows through the company. So

230
00:12:42.320 --> 00:12:44.840
<v Speaker 5>that's that's my premise is to visualize this in simple

231
00:12:44.879 --> 00:12:47.960
<v Speaker 5>diagrams that show where it's stuck, where it's broken, and

232
00:12:47.960 --> 00:12:50.080
<v Speaker 5>where it's not working, and ultimate where it does work,

233
00:12:50.080 --> 00:12:51.639
<v Speaker 5>and so we can kind of see how to, how to,

234
00:12:51.720 --> 00:12:52.559
<v Speaker 5>how to fix problems.

235
00:12:52.759 --> 00:12:56.279
<v Speaker 4>Yeah, I think it's absolutely fascinating. And you know, I'll

236
00:12:56.600 --> 00:13:00.159
<v Speaker 4>throw out another interesting tidbit here, which is, at the

237
00:13:00.240 --> 00:13:07.320
<v Speaker 4>end of the day, companies consist of people, processes, objects, assets,

238
00:13:07.960 --> 00:13:10.879
<v Speaker 4>and it's all driven by ideas. And you look at

239
00:13:10.879 --> 00:13:14.279
<v Speaker 4>some of the most successful companies, they pivoted hard at

240
00:13:14.279 --> 00:13:16.759
<v Speaker 4>some point in time. You look at Amazon, they were

241
00:13:16.799 --> 00:13:19.879
<v Speaker 4>all about being a book delivery service basically, and they

242
00:13:20.120 --> 00:13:23.320
<v Speaker 4>figured out, wow, we just built a fantastic supply chain

243
00:13:23.360 --> 00:13:26.360
<v Speaker 4>system essentially, or point as saler or everyone to describe it,

244
00:13:26.480 --> 00:13:28.919
<v Speaker 4>and they just pivoted to be selling whatever you want

245
00:13:28.919 --> 00:13:31.440
<v Speaker 4>to sell and creating an interface that anyone could come

246
00:13:31.480 --> 00:13:34.399
<v Speaker 4>along and sell. And that's because they obviously had a

247
00:13:34.440 --> 00:13:37.960
<v Speaker 4>culture where ideas could flourish. You could share an idea

248
00:13:38.000 --> 00:13:40.720
<v Speaker 4>and you can really get somewhere with it. And I

249
00:13:40.759 --> 00:13:46.320
<v Speaker 4>think your approach to understanding value can help organizations get

250
00:13:46.320 --> 00:13:49.600
<v Speaker 4>that kind of atmosphere in that kind of culture, because

251
00:13:49.600 --> 00:13:51.320
<v Speaker 4>that's when you succeed. I mean, if you've got a

252
00:13:51.360 --> 00:13:54.519
<v Speaker 4>company of even ten people, that's a whole lot of knowledge.

253
00:13:54.519 --> 00:13:57.600
<v Speaker 4>It's a whole lot of moxie and savoaf fare and

254
00:13:58.039 --> 00:14:01.039
<v Speaker 4>problems and issues and personnality whatever it is. There's a

255
00:14:01.080 --> 00:14:03.279
<v Speaker 4>lot of bad stuff, for sure, But if you can

256
00:14:03.360 --> 00:14:05.840
<v Speaker 4>work around the bad stuff and get to the good stuff,

257
00:14:06.159 --> 00:14:11.279
<v Speaker 4>that happens in honest conversations in the moment, referencing real assets,

258
00:14:11.360 --> 00:14:14.720
<v Speaker 4>real data, real ideas, real things that are needed. And

259
00:14:15.399 --> 00:14:19.480
<v Speaker 4>to do that in a collaborative way, in a collegial way,

260
00:14:19.799 --> 00:14:22.679
<v Speaker 4>that's the key. And I view your work in this

261
00:14:22.879 --> 00:14:28.200
<v Speaker 4>value matrix as being very facilitating to that goal.

262
00:14:28.240 --> 00:14:31.120
<v Speaker 5>What do you think, Absolutely, my whole point is to

263
00:14:31.240 --> 00:14:34.399
<v Speaker 5>enable communication, and you can't communicate if you don't have literacy.

264
00:14:34.840 --> 00:14:37.559
<v Speaker 5>So where do you start? What are the concepts, what's

265
00:14:37.600 --> 00:14:41.360
<v Speaker 5>the vocabulary? How are they connected? And now starting that

266
00:14:41.440 --> 00:14:43.480
<v Speaker 5>to have a conversation in the space, we have some

267
00:14:43.519 --> 00:14:46.240
<v Speaker 5>building blocks to work on. Now this is a work

268
00:14:46.240 --> 00:14:50.399
<v Speaker 5>in progress. It's early days, so it's not refined yet.

269
00:14:50.679 --> 00:14:53.360
<v Speaker 5>There's probably other kinds of value not considering right, But

270
00:14:53.399 --> 00:14:55.720
<v Speaker 5>again I'm not an economist, I'm not a financial analyst.

271
00:14:56.080 --> 00:14:59.720
<v Speaker 5>So some people say this is too simplistic, but I'm

272
00:14:59.720 --> 00:15:02.480
<v Speaker 5>thinking if it helps break the dead luck of conversation,

273
00:15:03.000 --> 00:15:05.759
<v Speaker 5>then it's got value using that word again, using it's

274
00:15:05.759 --> 00:15:08.480
<v Speaker 5>got value to people because you can now solve problems

275
00:15:08.879 --> 00:15:10.799
<v Speaker 5>without being an e communist or a financial analyst.

276
00:15:10.960 --> 00:15:13.159
<v Speaker 4>Right when I like to do do you do this

277
00:15:13.519 --> 00:15:16.919
<v Speaker 4>analogy to energy? Like I remember learning potential energy and

278
00:15:17.000 --> 00:15:21.000
<v Speaker 4>kinetic energy, So you've got potential value, you've got kinetic value,

279
00:15:21.000 --> 00:15:23.480
<v Speaker 4>and then you've got real life value. Right, then you

280
00:15:23.559 --> 00:15:27.440
<v Speaker 4>also had resilience value and leadership value. Is that right?

281
00:15:27.559 --> 00:15:29.360
<v Speaker 5>Structure structural the person.

282
00:15:29.240 --> 00:15:31.639
<v Speaker 4>Structural yet and go back on that again when it's that.

283
00:15:31.559 --> 00:15:36.639
<v Speaker 5>So, structural is laying the frameworks, the policies, the things

284
00:15:36.720 --> 00:15:38.759
<v Speaker 5>that kind of keep us structured.

285
00:15:38.759 --> 00:15:41.799
<v Speaker 4>In the company data governance program, the primary.

286
00:15:41.360 --> 00:15:44.960
<v Speaker 5>Output of governance to me is structural value. It then

287
00:15:45.080 --> 00:15:48.639
<v Speaker 5>enables data management to raise the quality based on that

288
00:15:48.679 --> 00:15:52.960
<v Speaker 5>structural policies and standards. And so when people say what's

289
00:15:53.000 --> 00:15:56.399
<v Speaker 5>the value of governance, it produces structural value. Right, And

290
00:15:56.399 --> 00:15:58.000
<v Speaker 5>if you know what that is, let's talk about it.

291
00:15:58.039 --> 00:16:01.960
<v Speaker 5>Because that's that that tell if it's successful, right, things

292
00:16:01.960 --> 00:16:03.440
<v Speaker 5>downstream of that will depend on it.

293
00:16:03.600 --> 00:16:06.679
<v Speaker 4>Right well, And that's you know, what's the old expression,

294
00:16:06.720 --> 00:16:09.360
<v Speaker 4>the car broughts from the head down right? So who

295
00:16:09.440 --> 00:16:12.039
<v Speaker 4>is ever at the top they're if they're bad, if

296
00:16:12.080 --> 00:16:14.240
<v Speaker 4>they're doing bad things and bad decisions, that's going to

297
00:16:14.320 --> 00:16:16.559
<v Speaker 4>reflect all the way through the organization, and that's going

298
00:16:16.600 --> 00:16:19.720
<v Speaker 4>to lead you to an unpleasant place. But the key,

299
00:16:19.759 --> 00:16:24.200
<v Speaker 4>I think is for extant organizations to leverage this kind

300
00:16:24.240 --> 00:16:27.360
<v Speaker 4>of thinking to understand where are we, where can we

301
00:16:27.440 --> 00:16:31.679
<v Speaker 4>go next? Realistically? What's plausible with our assets, with our people,

302
00:16:31.759 --> 00:16:35.399
<v Speaker 4>with our resources, what can we realistically hope to accomplish.

303
00:16:35.799 --> 00:16:38.600
<v Speaker 4>That's a big question these days, and especially it's a

304
00:16:38.639 --> 00:16:41.879
<v Speaker 4>big question because now with AI and all these technologies

305
00:16:41.879 --> 00:16:44.039
<v Speaker 4>and all the data that's available to us, you can

306
00:16:44.120 --> 00:16:46.919
<v Speaker 4>spin up a business model quickly. And the cloud used

307
00:16:46.960 --> 00:16:48.639
<v Speaker 4>to be that you had to hit ten twelve people.

308
00:16:48.639 --> 00:16:50.559
<v Speaker 4>That they can do with two people. So you can

309
00:16:50.559 --> 00:16:53.039
<v Speaker 4>spin up ideas quickly, but how do they scale?

310
00:16:53.519 --> 00:16:53.720
<v Speaker 6>Well?

311
00:16:53.720 --> 00:16:56.799
<v Speaker 4>In order to scale, you need that structural value right correct.

312
00:16:58.279 --> 00:17:00.480
<v Speaker 5>You know, if you're building anything, you need in structure

313
00:17:00.519 --> 00:17:03.080
<v Speaker 5>to connect things, to have standard ways of doing things,

314
00:17:03.200 --> 00:17:06.240
<v Speaker 5>and if you don't standardize, you can't scale, right. You know,

315
00:17:07.880 --> 00:17:09.880
<v Speaker 5>that enables the scaling to have some way you're doing

316
00:17:09.920 --> 00:17:11.000
<v Speaker 5>things in a standard way.

317
00:17:10.960 --> 00:17:16.400
<v Speaker 4>Right, standard processes, standard procedures, standard file formats. I mean,

318
00:17:16.440 --> 00:17:18.200
<v Speaker 4>if you get all the way down to where rubber

319
00:17:18.240 --> 00:17:22.160
<v Speaker 4>meets the road, standard nomenclature for columns and things of

320
00:17:22.200 --> 00:17:25.039
<v Speaker 4>this nature. If you do things properly, it's easier down

321
00:17:25.119 --> 00:17:27.200
<v Speaker 4>the road to integrate into mix and match, right.

322
00:17:27.759 --> 00:17:29.440
<v Speaker 5>And I think one of my big goals here is

323
00:17:29.440 --> 00:17:32.480
<v Speaker 5>also to get people out of their silos. Yeah, I

324
00:17:32.480 --> 00:17:35.000
<v Speaker 5>think one of the biggest barriers, and I kind of

325
00:17:35.039 --> 00:17:38.200
<v Speaker 5>attribute why we have these problems is, I mean this

326
00:17:38.240 --> 00:17:41.039
<v Speaker 5>is not new to anybody, but siloed thinking. Right, one

327
00:17:41.079 --> 00:17:43.359
<v Speaker 5>department things are successful and the next one down the

328
00:17:43.400 --> 00:17:46.599
<v Speaker 5>hall doesn't. Right, And well, then are we one company

329
00:17:46.680 --> 00:17:47.400
<v Speaker 5>or we two companies?

330
00:17:47.480 --> 00:17:47.680
<v Speaker 7>Right?

331
00:17:47.880 --> 00:17:48.079
<v Speaker 4>Right?

332
00:17:48.160 --> 00:17:50.039
<v Speaker 5>And that's the whole goal here, is to connect the dots,

333
00:17:50.519 --> 00:17:53.799
<v Speaker 5>get rid of silos, and understand that how things flow

334
00:17:54.319 --> 00:17:56.920
<v Speaker 5>should flow right independent of your org structure, because that

335
00:17:56.920 --> 00:17:57.440
<v Speaker 5>can change.

336
00:17:57.559 --> 00:18:00.000
<v Speaker 4>That's right. Well, And I'm reminded of something I learned

337
00:18:00.079 --> 00:18:02.799
<v Speaker 4>a long time ago by moreen Clary and Kelly Gilmore

338
00:18:02.839 --> 00:18:05.359
<v Speaker 4>of connect the knowledge network. They used to teach here

339
00:18:05.400 --> 00:18:08.279
<v Speaker 4>at TDWY all the time, and she taught me a

340
00:18:08.279 --> 00:18:13.039
<v Speaker 4>lot about organizational hierarchies and structures and talking to each other.

341
00:18:13.440 --> 00:18:15.640
<v Speaker 4>And what you want are all the managers talking to

342
00:18:15.680 --> 00:18:20.079
<v Speaker 4>each other across divisions. This sort of top down communications

343
00:18:20.119 --> 00:18:23.000
<v Speaker 4>structure that we've all become aftimated to. Its kind of

344
00:18:23.000 --> 00:18:25.079
<v Speaker 4>going out the window. And you're gonna need to be

345
00:18:25.160 --> 00:18:27.599
<v Speaker 4>talking left and talking right to people near you and

346
00:18:27.640 --> 00:18:30.160
<v Speaker 4>around you. In addition to understanding what your boss wants,

347
00:18:30.200 --> 00:18:32.759
<v Speaker 4>what your customers need, you really want to get that

348
00:18:32.880 --> 00:18:36.240
<v Speaker 4>context from around you. That's in the structural value, it's

349
00:18:36.279 --> 00:18:38.960
<v Speaker 4>in the systemic value. Well, look this gentleman up online,

350
00:18:38.960 --> 00:18:42.359
<v Speaker 4>Mark peakel Peco. He is a twy instructor. Will be

351
00:18:42.400 --> 00:18:44.240
<v Speaker 4>right back. You're listening to Inside and OUTSIM.

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

353
00:18:58.279 --> 00:19:00.279
<v Speaker 4>All right, folks back here on Inside and olicis. And

354
00:19:00.319 --> 00:19:02.400
<v Speaker 4>now I've got Josh Hicks with me from a cool

355
00:19:02.440 --> 00:19:05.240
<v Speaker 4>company called Jumpmine. They're right down the street from me.

356
00:19:05.279 --> 00:19:08.759
<v Speaker 4>I'm in Pittsburgh. They're in Columbus, Ohio, doing really innovative stuff.

357
00:19:08.759 --> 00:19:11.440
<v Speaker 4>They're as old as a DM radio too. Seventeen years old,

358
00:19:11.720 --> 00:19:14.160
<v Speaker 4>and they do a lot of data replication. It's just

359
00:19:14.200 --> 00:19:18.400
<v Speaker 4>one thing they do, but they do data replication extremely well.

360
00:19:18.440 --> 00:19:20.680
<v Speaker 4>We're not going to mention any company names. We're talking

361
00:19:20.839 --> 00:19:24.960
<v Speaker 4>thousands of stores, real time updates. And Josh, you were

362
00:19:24.960 --> 00:19:27.839
<v Speaker 4>telling me one of the real challenges with data replication

363
00:19:28.000 --> 00:19:31.279
<v Speaker 4>is when things go wrong, like a network goes down,

364
00:19:31.440 --> 00:19:34.839
<v Speaker 4>a store closes because of a hurricane. Well, these are

365
00:19:34.880 --> 00:19:38.240
<v Speaker 4>all real serious issues. When you're trying to track thousands

366
00:19:38.240 --> 00:19:41.000
<v Speaker 4>of data points and get them information about all their

367
00:19:41.039 --> 00:19:43.920
<v Speaker 4>products like updates and pricing or whatever. To be able

368
00:19:43.920 --> 00:19:46.880
<v Speaker 4>to do that seamlessly, that is a real magic bullet

369
00:19:46.960 --> 00:19:48.720
<v Speaker 4>tell us about jump mine on what you guys are

370
00:19:48.720 --> 00:19:49.000
<v Speaker 4>working on.

371
00:19:49.319 --> 00:19:53.559
<v Speaker 6>Yeah, so yeah, Eric, Like Eric said, specializing data replication

372
00:19:53.720 --> 00:19:56.680
<v Speaker 6>a lot of different endpoints, a lot of different platforms now,

373
00:19:56.759 --> 00:19:59.559
<v Speaker 6>but it started with a lot of retailers having the

374
00:19:59.599 --> 00:20:02.240
<v Speaker 6>problem of being able to move this data between all

375
00:20:02.240 --> 00:20:06.799
<v Speaker 6>these locations and dealing with things that happen network issues

376
00:20:06.839 --> 00:20:12.279
<v Speaker 6>and communication problems and low bandwidths and bad networks and

377
00:20:12.319 --> 00:20:15.119
<v Speaker 6>things like that. And so the happy path of replication

378
00:20:15.240 --> 00:20:17.680
<v Speaker 6>can be pretty straightforward and a lot of people can

379
00:20:17.680 --> 00:20:20.880
<v Speaker 6>probably work through it. Basically, on their own with a

380
00:20:20.880 --> 00:20:23.599
<v Speaker 6>little bit of tech experience, but when you're dealing with

381
00:20:23.640 --> 00:20:28.279
<v Speaker 6>a lot of the thing unexpected outages, and when you

382
00:20:28.319 --> 00:20:31.359
<v Speaker 6>have a note offline, you could have conflicts. So dealing

383
00:20:31.359 --> 00:20:35.200
<v Speaker 6>with conflicts and not causing backlogs in the replication and

384
00:20:35.880 --> 00:20:39.200
<v Speaker 6>being able to be resilient to networks that are down

385
00:20:39.279 --> 00:20:41.880
<v Speaker 6>and stores that are offline, or sites that are offline,

386
00:20:41.920 --> 00:20:44.680
<v Speaker 6>or databases that are offline. Because you're not really focused

387
00:20:44.680 --> 00:20:48.839
<v Speaker 6>anymore on just the retail platform. It's pretty much used

388
00:20:48.839 --> 00:20:52.759
<v Speaker 6>everywhere data is needed and moved and migrated, and with

389
00:20:52.799 --> 00:20:56.839
<v Speaker 6>so many platforms out there now, it's not just relational

390
00:20:56.880 --> 00:20:59.759
<v Speaker 6>databases we're dealing with anymore. It's a lot of different

391
00:20:59.759 --> 00:21:02.400
<v Speaker 6>plays platforms with the nose sequels in the righthouses and

392
00:21:02.440 --> 00:21:05.279
<v Speaker 6>the cloud came along, right, So there's a lot of

393
00:21:05.400 --> 00:21:10.400
<v Speaker 6>benefits to utilizing lots of these data sources for different reasons,

394
00:21:10.720 --> 00:21:12.759
<v Speaker 6>and so moving that data between them is kind of

395
00:21:12.759 --> 00:21:13.400
<v Speaker 6>where we come.

396
00:21:13.279 --> 00:21:15.720
<v Speaker 4>In well, right, And we were talking about the history

397
00:21:15.720 --> 00:21:19.000
<v Speaker 4>of the database industry and how you know, twenty years

398
00:21:19.039 --> 00:21:21.920
<v Speaker 4>ago there were like five choices you could make. Now

399
00:21:22.000 --> 00:21:25.079
<v Speaker 4>there are four hundred and twenty five choices you can make.

400
00:21:25.119 --> 00:21:28.680
<v Speaker 4>I mean, it is that diverse out there, and let's

401
00:21:28.680 --> 00:21:32.119
<v Speaker 4>face it, individual companies can have any number of technologies

402
00:21:32.160 --> 00:21:35.640
<v Speaker 4>in play. But one thing I've always loved about effective

403
00:21:35.680 --> 00:21:40.480
<v Speaker 4>information architectures is that companies figure out where we're going

404
00:21:40.559 --> 00:21:42.680
<v Speaker 4>to keep data, how we're going to move data, how

405
00:21:42.720 --> 00:21:44.799
<v Speaker 4>we're going to use data. And you have these layers

406
00:21:44.799 --> 00:21:48.440
<v Speaker 4>of abstraction where something in the middle can handle any

407
00:21:48.480 --> 00:21:51.240
<v Speaker 4>source and handle any target. And that's the idea. That's

408
00:21:51.240 --> 00:21:53.880
<v Speaker 4>where you are. You're the intermediate almost like the middleware

409
00:21:53.920 --> 00:21:56.039
<v Speaker 4>as we've called it over the years, where you got

410
00:21:56.039 --> 00:21:58.119
<v Speaker 4>all these source systems. I got an Oracle database, I

411
00:21:58.160 --> 00:22:01.079
<v Speaker 4>got a Postgrass database, I got a Cybe database, and

412
00:22:01.119 --> 00:22:03.680
<v Speaker 4>then I have all these point solutions, all these targets

413
00:22:03.680 --> 00:22:06.319
<v Speaker 4>where I want to get information to the stores, to

414
00:22:06.359 --> 00:22:09.839
<v Speaker 4>the manufacturers, whatever. If you try to do point to

415
00:22:09.920 --> 00:22:12.440
<v Speaker 4>point for every one of those, you're going to jump

416
00:22:12.480 --> 00:22:14.200
<v Speaker 4>off a cliff, like you are not going to be

417
00:22:14.279 --> 00:22:17.039
<v Speaker 4>that's the unhappy path. Yeah you talk about.

418
00:22:16.799 --> 00:22:19.599
<v Speaker 6>Right, yeah, And I mean and being able to merge

419
00:22:19.599 --> 00:22:21.920
<v Speaker 6>all that together and not be vendor locked into a

420
00:22:21.960 --> 00:22:24.880
<v Speaker 6>specific product. Right, You're having a tool that has the

421
00:22:24.920 --> 00:22:28.480
<v Speaker 6>cross platform flexibility like we do. We don't really care

422
00:22:28.519 --> 00:22:30.640
<v Speaker 6>what platforms you're using. We just want to be an

423
00:22:30.640 --> 00:22:32.880
<v Speaker 6>option and we want to work with all those options

424
00:22:32.960 --> 00:22:35.839
<v Speaker 6>that you define how your data should move, where it

425
00:22:35.839 --> 00:22:39.519
<v Speaker 6>should move to what platforms you choose. Right, and that

426
00:22:39.680 --> 00:22:41.839
<v Speaker 6>is that that becomes a big deal of keeping more

427
00:22:41.880 --> 00:22:43.880
<v Speaker 6>than one or two of them in sync, because now

428
00:22:43.880 --> 00:22:47.599
<v Speaker 6>you have to keep the order of how those transactions

429
00:22:47.599 --> 00:22:50.960
<v Speaker 6>occurs very important, and some might not be available when

430
00:22:51.000 --> 00:22:53.839
<v Speaker 6>others are. So keep being all that status ying and

431
00:22:53.960 --> 00:22:56.799
<v Speaker 6>history of what data has moved and what hasn't moved,

432
00:22:56.839 --> 00:22:59.480
<v Speaker 6>and then might be performant it because.

433
00:23:00.720 --> 00:23:04.039
<v Speaker 4>Exactly right managing state, say, I try to explain state

434
00:23:04.079 --> 00:23:07.480
<v Speaker 4>to people. It's a very interesting concept. The easy example

435
00:23:07.559 --> 00:23:11.079
<v Speaker 4>I give is when you are online. Let's see on Amazon,

436
00:23:11.119 --> 00:23:14.079
<v Speaker 4>you're shopping for stuff and you're searching around, and then

437
00:23:14.160 --> 00:23:16.160
<v Speaker 4>you do the magical thing, which is I want to

438
00:23:16.200 --> 00:23:18.200
<v Speaker 4>go ahead and buy this stuff, and so you hit

439
00:23:18.480 --> 00:23:21.279
<v Speaker 4>go to Kart, and now the state is okay, I'm

440
00:23:21.279 --> 00:23:24.440
<v Speaker 4>in the state of getting ready to take the money. Right,

441
00:23:24.480 --> 00:23:25.880
<v Speaker 4>and if you say, oh no, wait, I want to

442
00:23:25.920 --> 00:23:27.759
<v Speaker 4>go find something, you're getting out of that state. Now

443
00:23:27.759 --> 00:23:30.079
<v Speaker 4>you're going back into your searching state to find things

444
00:23:30.160 --> 00:23:32.400
<v Speaker 4>to build your cart. But the point is when you

445
00:23:32.440 --> 00:23:35.400
<v Speaker 4>are in that cart and about to hit the purchase button,

446
00:23:35.400 --> 00:23:37.920
<v Speaker 4>that is a certain state. And what you talk about

447
00:23:38.000 --> 00:23:40.400
<v Speaker 4>makes a lot of sense of when things go down.

448
00:23:40.799 --> 00:23:43.119
<v Speaker 4>So if I'm logged in, I'm about to hit purchase

449
00:23:43.240 --> 00:23:46.319
<v Speaker 4>and the system goes down, my power goes out, or whatever,

450
00:23:46.839 --> 00:23:49.720
<v Speaker 4>where is that state captured and persistent such that I

451
00:23:49.720 --> 00:23:52.640
<v Speaker 4>can log back in and get to where I was. Right,

452
00:23:52.680 --> 00:23:55.119
<v Speaker 4>And that's what you're talking about. Right, when things go down,

453
00:23:55.480 --> 00:24:00.519
<v Speaker 4>you need some ledger basically or matrix that's monitoring where

454
00:24:00.599 --> 00:24:02.880
<v Speaker 4>things were at the time of the failure so you

455
00:24:02.920 --> 00:24:05.200
<v Speaker 4>can pick back up and not miss a beat and

456
00:24:05.200 --> 00:24:06.440
<v Speaker 4>not miss something right.

457
00:24:06.519 --> 00:24:09.480
<v Speaker 6>Yeah, The nature the nature of how the product fundamentally

458
00:24:09.519 --> 00:24:13.279
<v Speaker 6>works is it will retain changes until they're committed at

459
00:24:13.279 --> 00:24:16.440
<v Speaker 6>their target I see, and now obviously commit being more

460
00:24:16.440 --> 00:24:18.559
<v Speaker 6>of a database term, but we deal with some other

461
00:24:19.240 --> 00:24:22.359
<v Speaker 6>platforms like the kafkas and things like that. But being

462
00:24:22.400 --> 00:24:24.839
<v Speaker 6>able to make sure that that is committed before you

463
00:24:24.920 --> 00:24:28.880
<v Speaker 6>move on, and that's very important because we must retain

464
00:24:29.000 --> 00:24:31.640
<v Speaker 6>that and keep that state and know that where that

465
00:24:31.680 --> 00:24:35.160
<v Speaker 6>state of that information is until we've gotten a full

466
00:24:35.160 --> 00:24:38.480
<v Speaker 6>acknowledgement that it's committed. Right, and we have processes that

467
00:24:38.519 --> 00:24:42.079
<v Speaker 6>purge that stuff out. Then once that state is that's resolved,

468
00:24:42.079 --> 00:24:44.839
<v Speaker 6>and there's all kinds of bells and whistles to turn,

469
00:24:44.880 --> 00:24:48.279
<v Speaker 6>and you can set different retention periods for how long

470
00:24:48.319 --> 00:24:51.720
<v Speaker 6>you keep history of that. But in a happy path,

471
00:24:51.799 --> 00:24:53.519
<v Speaker 6>you know, keep it. You don't need to necessarily keep

472
00:24:53.519 --> 00:24:55.920
<v Speaker 6>it around real long. If things are moving but something

473
00:24:55.960 --> 00:24:58.279
<v Speaker 6>comes offline, you need to be able to maintain that

474
00:24:58.359 --> 00:25:00.960
<v Speaker 6>state and playback hours potentially.

475
00:25:01.440 --> 00:25:04.839
<v Speaker 4>Rice right right, the unhappy path. Now, that's such a

476
00:25:04.839 --> 00:25:07.119
<v Speaker 4>good that's such a good point. And you know, I'm

477
00:25:07.119 --> 00:25:11.799
<v Speaker 4>reminded again that if you have a good architecture and

478
00:25:11.839 --> 00:25:14.839
<v Speaker 4>you know where your marshaling area is for moving things around,

479
00:25:15.240 --> 00:25:18.279
<v Speaker 4>that allows you the flexibility to bring on different source

480
00:25:18.279 --> 00:25:20.839
<v Speaker 4>systems and different target systems. And I did want to

481
00:25:20.880 --> 00:25:24.160
<v Speaker 4>explain the commit, like a two phase commit is something

482
00:25:24.160 --> 00:25:25.799
<v Speaker 4>I think a lot of people can understand. In the

483
00:25:25.839 --> 00:25:29.160
<v Speaker 4>banking world. Because I send you one hundred dollars through Venmo,

484
00:25:29.960 --> 00:25:33.000
<v Speaker 4>that the request goes through, take one hundred dollars out

485
00:25:33.000 --> 00:25:35.160
<v Speaker 4>of my account, put it in his account. I need

486
00:25:35.160 --> 00:25:37.640
<v Speaker 4>to get a message back that says, Okay, we got it.

487
00:25:37.640 --> 00:25:39.759
<v Speaker 4>It's now in his account. That is a two phase

488
00:25:39.799 --> 00:25:40.839
<v Speaker 4>commit right.

489
00:25:40.680 --> 00:25:43.400
<v Speaker 6>Yeah, very very common that EF.

490
00:25:43.440 --> 00:25:45.880
<v Speaker 4>We're gonna understand, I now have the money, and you

491
00:25:46.039 --> 00:25:49.200
<v Speaker 4>know that I have the money, right, as opposed to, well,

492
00:25:49.240 --> 00:25:50.759
<v Speaker 4>the money's out of my account, but it's not in

493
00:25:50.799 --> 00:25:54.319
<v Speaker 4>your account. That's a problem. That's the unhappy path for

494
00:25:54.400 --> 00:25:54.799
<v Speaker 4>money man.

495
00:25:55.000 --> 00:25:59.160
<v Speaker 6>With relational databases, yeah, we are an asynchronous because a

496
00:25:59.240 --> 00:26:02.279
<v Speaker 6>lot of people say, you know, I want a synchronous solution,

497
00:26:02.480 --> 00:26:05.079
<v Speaker 6>but didn't really know what that means. Because you don't

498
00:26:05.119 --> 00:26:07.680
<v Speaker 6>necessarily want to open a connection on your source and

499
00:26:07.880 --> 00:26:11.039
<v Speaker 6>wait until it's committed on the target. That could hold

500
00:26:11.079 --> 00:26:14.799
<v Speaker 6>up your user experience. So making that asynchronous is a

501
00:26:14.799 --> 00:26:17.599
<v Speaker 6>big difference, and it's actually more performance for the user

502
00:26:17.680 --> 00:26:21.680
<v Speaker 6>because it allows them to finish the user experience on

503
00:26:21.720 --> 00:26:26.680
<v Speaker 6>the source, gather the data asynchronously, processes right target. Now,

504
00:26:26.680 --> 00:26:30.720
<v Speaker 6>those it could be very fast and feel like it's synchronous,

505
00:26:30.759 --> 00:26:33.559
<v Speaker 6>but it's important that if there is any failure along

506
00:26:33.599 --> 00:26:36.160
<v Speaker 6>that pipeline, you're not holding up the user experience, right,

507
00:26:36.160 --> 00:26:40.200
<v Speaker 6>And that's a big deal. It comes to data application right,

508
00:26:40.279 --> 00:26:42.319
<v Speaker 6>not to affect the user. That's a lot of times

509
00:26:42.319 --> 00:26:44.480
<v Speaker 6>what the first question is, how is this going to

510
00:26:44.480 --> 00:26:45.480
<v Speaker 6>affect my users.

511
00:26:45.880 --> 00:26:49.079
<v Speaker 4>Well right, well, I mean everyone has experienced either in

512
00:26:49.200 --> 00:26:53.039
<v Speaker 4>the store or they're on the phone and customer service center.

513
00:26:53.119 --> 00:26:55.279
<v Speaker 4>And what does the person say, Oh, our systems are

514
00:26:55.359 --> 00:26:58.680
<v Speaker 4>running slow today? Well, why is that? It Could be

515
00:26:58.799 --> 00:27:02.039
<v Speaker 4>the database, It could be netwight, could be data replication,

516
00:27:02.119 --> 00:27:04.680
<v Speaker 4>it could be any number of things. And boy, the

517
00:27:05.039 --> 00:27:08.240
<v Speaker 4>more interconnected we get in the cloud, the more things

518
00:27:08.279 --> 00:27:09.880
<v Speaker 4>that are that can go wrong. I mean there are

519
00:27:09.920 --> 00:27:11.279
<v Speaker 4>all sorts of things in between.

520
00:27:12.039 --> 00:27:15.720
<v Speaker 6>As we've evolved in our experience with replication, we've we've

521
00:27:15.759 --> 00:27:18.480
<v Speaker 6>gathered more and more information and stats along the way,

522
00:27:18.599 --> 00:27:22.880
<v Speaker 6>which is really beneficial for pinpointing when there's a problem.

523
00:27:22.960 --> 00:27:24.240
<v Speaker 6>Where is the bottleneck is?

524
00:27:24.720 --> 00:27:24.880
<v Speaker 4>You know?

525
00:27:25.000 --> 00:27:27.480
<v Speaker 6>Is it the extraction? Is it the transfers at the load?

526
00:27:28.079 --> 00:27:29.279
<v Speaker 6>Is it somewhere in between?

527
00:27:29.440 --> 00:27:30.039
<v Speaker 5>Is it? You know?

528
00:27:30.079 --> 00:27:33.319
<v Speaker 6>What failure points? What retries? Did we have ryan gathering

529
00:27:33.920 --> 00:27:36.920
<v Speaker 6>all of those statistic points, which helped put the bigger

530
00:27:36.960 --> 00:27:39.839
<v Speaker 6>picture now and again back to the happy path. Those

531
00:27:39.880 --> 00:27:42.960
<v Speaker 6>may look real inear and be real smooth, but when

532
00:27:43.000 --> 00:27:47.720
<v Speaker 6>you start to have h maybe you add more bandwidth,

533
00:27:47.759 --> 00:27:49.839
<v Speaker 6>you have more stores, you have more offices, you have

534
00:27:50.000 --> 00:27:52.880
<v Speaker 6>more data, and you start pushing more through the pipe.

535
00:27:53.160 --> 00:27:56.839
<v Speaker 6>You'll start to expose where the bottlenecks are. Maybe there

536
00:27:56.839 --> 00:28:01.079
<v Speaker 6>weren't bottlenecks first quarter, right second quarter, helping the amount

537
00:28:01.119 --> 00:28:04.039
<v Speaker 6>of users, you've added customers, you've added more data through

538
00:28:04.079 --> 00:28:08.359
<v Speaker 6>your pipeline, and being able to quickly analyze where those

539
00:28:09.079 --> 00:28:11.920
<v Speaker 6>fragments are and where those performance breakdowns are allows you

540
00:28:11.960 --> 00:28:14.000
<v Speaker 6>to get in and make adjustments well.

541
00:28:14.039 --> 00:28:17.759
<v Speaker 4>And you bring up an excellent point about the history

542
00:28:18.119 --> 00:28:21.680
<v Speaker 4>and the tenure that jump Mind has because over time

543
00:28:21.759 --> 00:28:25.160
<v Speaker 4>you do gather data, and so you'll understand when this

544
00:28:25.200 --> 00:28:27.799
<v Speaker 4>system connects to that system, we've had some problems. When

545
00:28:27.799 --> 00:28:30.599
<v Speaker 4>that system connects over here, we've had some problems. I mean,

546
00:28:31.000 --> 00:28:36.599
<v Speaker 4>there was the whole disastrous CrowdStrike crash a few months ago,

547
00:28:37.200 --> 00:28:40.559
<v Speaker 4>which was apparently because there was an update pushed and

548
00:28:40.599 --> 00:28:43.319
<v Speaker 4>they hadn't done a full null scan and there was

549
00:28:43.359 --> 00:28:46.160
<v Speaker 4>one of those little formula in there that just zapped

550
00:28:46.200 --> 00:28:48.799
<v Speaker 4>the systems and brought it crashing down. I mean, that's

551
00:28:48.839 --> 00:28:50.960
<v Speaker 4>the kind of thing that should not have happened to

552
00:28:51.200 --> 00:28:53.279
<v Speaker 4>be blunted me. I still haven't gone to the bottom

553
00:28:53.279 --> 00:28:56.279
<v Speaker 4>of what really happened there, but the point is that

554
00:28:56.400 --> 00:28:58.160
<v Speaker 4>if you have been around for a while, as you

555
00:28:58.240 --> 00:29:02.440
<v Speaker 4>guys have you can capture lots of metadata and understand

556
00:29:02.519 --> 00:29:04.920
<v Speaker 4>what is a reasonable amount of time for this process

557
00:29:05.079 --> 00:29:05.920
<v Speaker 4>to execute.

558
00:29:05.960 --> 00:29:10.079
<v Speaker 6>And actually a feature that's kind of interesting that we've

559
00:29:10.079 --> 00:29:11.960
<v Speaker 6>added to the product and about the last year and

560
00:29:12.000 --> 00:29:15.359
<v Speaker 6>a half. We call them insights, and what it's doing

561
00:29:15.440 --> 00:29:17.200
<v Speaker 6>is there's several of these that are running in the

562
00:29:17.200 --> 00:29:20.400
<v Speaker 6>background and they're watching trends. They're watching those. So we

563
00:29:20.440 --> 00:29:23.640
<v Speaker 6>started by capturing the metrics because that's the first paint point,

564
00:29:23.839 --> 00:29:26.680
<v Speaker 6>is to be able to gather certain metrics along the way.

565
00:29:26.839 --> 00:29:29.119
<v Speaker 6>But now these insights are running and trying to fire

566
00:29:29.359 --> 00:29:32.160
<v Speaker 6>and do a kind of like an AI analysis. Hey,

567
00:29:32.240 --> 00:29:35.079
<v Speaker 6>we noticed this normally takes this much time to push

568
00:29:35.119 --> 00:29:38.319
<v Speaker 6>this much data. You're up one hundred and fifty percent.

569
00:29:38.119 --> 00:29:39.200
<v Speaker 4>Right, what's going on?

570
00:29:39.279 --> 00:29:43.319
<v Speaker 6>Yeah, it can bring it to your forefront and say

571
00:29:43.359 --> 00:29:47.279
<v Speaker 6>these trends are happening, and then in some of these insights,

572
00:29:47.319 --> 00:29:50.200
<v Speaker 6>we actually can provide you and approof. But it might

573
00:29:50.279 --> 00:29:53.279
<v Speaker 6>be we want to durn a nile during a dial

574
00:29:53.400 --> 00:29:55.480
<v Speaker 6>behind the scenes, we want to up some time out,

575
00:29:55.519 --> 00:29:58.160
<v Speaker 6>we want to up a threshold, increase your connection pool.

576
00:29:58.519 --> 00:30:02.000
<v Speaker 6>Maybe you've involved class and there's so some of those

577
00:30:02.039 --> 00:30:05.680
<v Speaker 6>metrics we have settings, but we you know, it might

578
00:30:05.799 --> 00:30:08.519
<v Speaker 6>involve in the past, that might involve consulting, right, go

579
00:30:08.599 --> 00:30:11.680
<v Speaker 6>in and analyze this right now with these insights, they're

580
00:30:11.759 --> 00:30:15.079
<v Speaker 6>kind of bringing it to your attention. Here, we noticed

581
00:30:15.079 --> 00:30:20.039
<v Speaker 6>something that's abnormal. Improve We're going to tweak this dial

582
00:30:20.119 --> 00:30:22.200
<v Speaker 6>for you and adjust it. You know, maybe you appreci

583
00:30:22.160 --> 00:30:23.160
<v Speaker 6>your connection.

584
00:30:22.839 --> 00:30:24.000
<v Speaker 4>Pool right now.

585
00:30:24.920 --> 00:30:26.960
<v Speaker 6>Some people may or may not know what that means,

586
00:30:27.000 --> 00:30:28.640
<v Speaker 6>but you know, at least it puts it in front

587
00:30:28.680 --> 00:30:30.640
<v Speaker 6>of them to say, hey, this is what we'd like

588
00:30:30.720 --> 00:30:30.920
<v Speaker 6>to do.

589
00:30:31.160 --> 00:30:34.240
<v Speaker 4>Well, you know the old expression what gets measured gets

590
00:30:34.279 --> 00:30:38.079
<v Speaker 4>managed exactly and what I love, especially because these systems

591
00:30:38.079 --> 00:30:41.319
<v Speaker 4>are so complex and so interdependent. Now, yes, and there

592
00:30:41.319 --> 00:30:43.839
<v Speaker 4>are so many things that can go wrong, and you're

593
00:30:43.839 --> 00:30:46.480
<v Speaker 4>always like, is it my network? Is it me? I'm

594
00:30:46.519 --> 00:30:48.519
<v Speaker 4>the one who's doing the speed test, Like, maybe it's

595
00:30:48.559 --> 00:30:51.519
<v Speaker 4>me the other team. Right, it's like playing the tool, right,

596
00:30:51.519 --> 00:30:53.759
<v Speaker 4>that's the old pickers playing the tool. But when you

597
00:30:53.799 --> 00:30:56.400
<v Speaker 4>can see and you and guess what, that also educates

598
00:30:56.400 --> 00:30:58.640
<v Speaker 4>the user, so now they know a little bit more

599
00:30:58.839 --> 00:31:01.480
<v Speaker 4>about what's actually happening. And it's like I found that

600
00:31:01.920 --> 00:31:04.720
<v Speaker 4>people will be very reasonable as long as they know

601
00:31:05.240 --> 00:31:08.559
<v Speaker 4>what's happening. It's when you don't know what's happening that

602
00:31:08.640 --> 00:31:10.279
<v Speaker 4>it gets very dicey.

603
00:31:09.720 --> 00:31:13.119
<v Speaker 6>And one of the key features we've always and the

604
00:31:13.160 --> 00:31:15.359
<v Speaker 6>owners have always brought to the table when they formed

605
00:31:15.400 --> 00:31:19.200
<v Speaker 6>jump Line was the support we've worked hard to We

606
00:31:19.240 --> 00:31:22.039
<v Speaker 6>don't outsource any support. It's all the engineers that have

607
00:31:22.079 --> 00:31:23.000
<v Speaker 6>worked on the product.

608
00:31:23.200 --> 00:31:23.519
<v Speaker 4>Wow.

609
00:31:24.039 --> 00:31:26.319
<v Speaker 6>We typically try to get through about a six month

610
00:31:26.440 --> 00:31:29.160
<v Speaker 6>learning curve where they if they hire new that we

611
00:31:29.680 --> 00:31:32.279
<v Speaker 6>bring them on because the support is everything we want

612
00:31:32.400 --> 00:31:35.480
<v Speaker 6>to be able. We've all worked in it. As an engineer.

613
00:31:35.920 --> 00:31:38.240
<v Speaker 6>I'm still on call at times, and we've all been

614
00:31:38.279 --> 00:31:42.720
<v Speaker 6>in crisis situations and there's nothing worse than having not

615
00:31:42.880 --> 00:31:45.279
<v Speaker 6>having the proper support change yeah yeah, yeah yeah. And

616
00:31:45.359 --> 00:31:48.920
<v Speaker 6>like you mentioned earlier, it might involve multiple teams, so

617
00:31:49.599 --> 00:31:52.880
<v Speaker 6>we want the data side of things in the replication

618
00:31:53.039 --> 00:31:55.400
<v Speaker 6>to always have the metrics and stuff that we can

619
00:31:55.440 --> 00:31:58.559
<v Speaker 6>provide is best support we can for it, because we

620
00:31:58.599 --> 00:32:00.119
<v Speaker 6>know what it's like to have an auditgen in the

621
00:32:00.119 --> 00:32:03.079
<v Speaker 6>middle of the right right and oftentime we're dealing with

622
00:32:03.119 --> 00:32:07.319
<v Speaker 6>an outage, could increase increase a backlog very quickly because

623
00:32:07.400 --> 00:32:11.599
<v Speaker 6>it is replication, right, so immediately a small problem becomes

624
00:32:11.599 --> 00:32:15.200
<v Speaker 6>a big one and thinks backlog while so the support

625
00:32:15.240 --> 00:32:17.759
<v Speaker 6>has been a huge model. And quite frankly, I think

626
00:32:17.759 --> 00:32:21.200
<v Speaker 6>people are just moving a lot more data. We didn't

627
00:32:21.240 --> 00:32:23.920
<v Speaker 6>have to ty years ago. It wasn't as it was

628
00:32:23.960 --> 00:32:26.839
<v Speaker 6>a big deal and what your storage was. Storage was expensive,

629
00:32:27.359 --> 00:32:32.039
<v Speaker 6>data was expensive. Now we run into groups and I'm like,

630
00:32:32.240 --> 00:32:34.559
<v Speaker 6>do you even know what these tables are, right, because

631
00:32:34.559 --> 00:32:38.880
<v Speaker 6>they just have copies of everything, right, So that's it's

632
00:32:39.039 --> 00:32:41.759
<v Speaker 6>kind of fascinating seeing the progression of how much data

633
00:32:41.839 --> 00:32:42.480
<v Speaker 6>is moving now.

634
00:32:42.799 --> 00:32:44.759
<v Speaker 4>Right, Well, and you actually just hit on one of

635
00:32:44.799 --> 00:32:47.519
<v Speaker 4>my classic talking points. And folks who've listened to these

636
00:32:47.559 --> 00:32:50.039
<v Speaker 4>shows multiple times have heard me say this multiple times.

637
00:32:50.400 --> 00:32:52.920
<v Speaker 4>But the dynamics have changed so much. I mean, I'm

638
00:32:52.960 --> 00:32:56.599
<v Speaker 4>a big fan of constraint based design because your constraints

639
00:32:56.640 --> 00:33:00.119
<v Speaker 4>are reality and you have to either address them or

640
00:33:00.000 --> 00:33:03.319
<v Speaker 4>work within them. Right, And back in the day, processors

641
00:33:03.319 --> 00:33:07.240
<v Speaker 4>were slow, storage was expensive. Networks speed was.

642
00:33:07.200 --> 00:33:09.200
<v Speaker 6>Slow on the forefront of everybody's mind.

643
00:33:09.400 --> 00:33:12.519
<v Speaker 4>Right Now, processors are fast and you could do multi core,

644
00:33:12.680 --> 00:33:17.039
<v Speaker 4>you could do GPU versus CPU, the the pipes are fat,

645
00:33:17.279 --> 00:33:20.720
<v Speaker 4>storage is cheap, So all those dynamics that that drove

646
00:33:20.880 --> 00:33:23.960
<v Speaker 4>the design of old systems are different now yeah, and

647
00:33:24.000 --> 00:33:26.160
<v Speaker 4>are gone. So what do we do now?

648
00:33:26.440 --> 00:33:26.599
<v Speaker 8>Now?

649
00:33:26.599 --> 00:33:29.160
<v Speaker 4>There is this concept of code bloat remember learning now

650
00:33:29.160 --> 00:33:31.119
<v Speaker 4>we got about a minute left, and like code bload

651
00:33:31.160 --> 00:33:33.920
<v Speaker 4>is when the processors got fast that the developers got lazy. Yeah,

652
00:33:33.960 --> 00:33:36.920
<v Speaker 4>who cares? Just go write more script to get it done.

653
00:33:36.920 --> 00:33:37.640
<v Speaker 6>It seems like it's.

654
00:33:37.519 --> 00:33:39.440
<v Speaker 4>Kind of a wave right right, right, it goes up

655
00:33:40.079 --> 00:33:42.799
<v Speaker 4>right and we're going back down again. Well, closing thoughts,

656
00:33:43.039 --> 00:33:45.319
<v Speaker 4>where can someone learn more about jump mind? And we

657
00:33:45.359 --> 00:33:48.920
<v Speaker 4>didn't talk too much about It's called symmetric.

658
00:33:48.359 --> 00:33:53.039
<v Speaker 6>Das Yeah, for symmetric data synchronization. Right, you can find

659
00:33:53.079 --> 00:33:55.880
<v Speaker 6>us on jumpline dot com and it's under our data.

660
00:33:56.240 --> 00:33:59.720
<v Speaker 6>There's a data menu, right, and there's a trial. It's

661
00:33:59.720 --> 00:34:02.160
<v Speaker 6>a look at it. And then obviously if you email

662
00:34:02.279 --> 00:34:04.799
<v Speaker 6>us myself for one of the other engineers, are happy

663
00:34:04.839 --> 00:34:06.440
<v Speaker 6>to kind of walk it through and give a demo.

664
00:34:06.920 --> 00:34:07.359
<v Speaker 4>I love it.

665
00:34:07.359 --> 00:34:10.039
<v Speaker 6>We're very big on making sure we're not maybe the

666
00:34:10.079 --> 00:34:12.239
<v Speaker 6>right fit for every use case, So we love to

667
00:34:12.280 --> 00:34:14.159
<v Speaker 6>talk to people. Hear what their story is, what their

668
00:34:14.239 --> 00:34:16.119
<v Speaker 6>use case is. We want to find a good fit.

669
00:34:16.400 --> 00:34:18.000
<v Speaker 6>It's not a good fit, it's a waste of both

670
00:34:18.039 --> 00:34:21.079
<v Speaker 6>their time. Yeah, yeah, yeah, that's that's been a key.

671
00:34:21.239 --> 00:34:24.239
<v Speaker 4>Well, that's that's a great signed folks. I can tell

672
00:34:24.239 --> 00:34:26.880
<v Speaker 4>you that's a look up jump mind. And I remember

673
00:34:26.880 --> 00:34:29.880
<v Speaker 4>one of the coolest companies I knew. In the same sentence,

674
00:34:30.079 --> 00:34:32.360
<v Speaker 4>a guy would say, well, here's what we do and

675
00:34:32.400 --> 00:34:34.960
<v Speaker 4>here's what we don't do, right, and it's really important

676
00:34:34.960 --> 00:34:37.039
<v Speaker 4>to understand that. Well, folks, don't touch it out with

677
00:34:37.199 --> 00:34:42.840
<v Speaker 4>right back, you're listening to Inside Analysis.

678
00:34:45.320 --> 00:34:50.239
<v Speaker 3>Welcome back to Inside Analysis. Here's your host, Eric Tavanaugh.

679
00:34:52.880 --> 00:34:55.559
<v Speaker 4>All right, folks, back here on Inside Analysis at TDWY

680
00:34:55.719 --> 00:34:58.280
<v Speaker 4>in Las Vegas, my old haunt. I'm hanging out with

681
00:34:58.320 --> 00:35:00.199
<v Speaker 4>some of my old buddies, and I'm here now with

682
00:35:00.199 --> 00:35:03.599
<v Speaker 4>Patrick O'Halleran. He is with the company called wear Escape.

683
00:35:03.639 --> 00:35:06.400
<v Speaker 4>I've known wear Escape for about fifteen years or so.

684
00:35:06.840 --> 00:35:09.440
<v Speaker 4>Old Michael Whitehead he launched it and sold it to

685
00:35:09.639 --> 00:35:11.679
<v Speaker 4>a Idea a long time ago, or a number of

686
00:35:11.760 --> 00:35:15.119
<v Speaker 4>years ago, I guess. But they're great for data warehouse

687
00:35:15.239 --> 00:35:18.079
<v Speaker 4>documentation because guess what, you know, how many developers like

688
00:35:18.119 --> 00:35:21.719
<v Speaker 4>to do documentation? None, No, developers like to do documentation.

689
00:35:21.920 --> 00:35:24.760
<v Speaker 4>Slightly less than one, slightly less than one, somewhere between

690
00:35:24.840 --> 00:35:27.800
<v Speaker 4>zero and one. Of the developers out there like to

691
00:35:27.840 --> 00:35:29.679
<v Speaker 4>do documentation. That's important, but they do a lot of

692
00:35:29.679 --> 00:35:33.480
<v Speaker 4>other stuff too, and it's an excellent tool for being

693
00:35:33.519 --> 00:35:36.360
<v Speaker 4>able to leverage the power of a snowflake for example,

694
00:35:36.519 --> 00:35:39.159
<v Speaker 4>or I guess at data bricks or any of these guys. Right,

695
00:35:39.239 --> 00:35:41.199
<v Speaker 4>So tell us a bit about what you're working on

696
00:35:41.280 --> 00:35:43.559
<v Speaker 4>with wear Escape red these days. Sure, for sure.

697
00:35:43.760 --> 00:35:45.320
<v Speaker 9>So as you say, wear Escape's been around for quite

698
00:35:45.320 --> 00:35:48.360
<v Speaker 9>a while, and we started twenty five years ago in

699
00:35:48.440 --> 00:35:51.639
<v Speaker 9>New Zealand as a consulting company building data warehouses.

700
00:35:52.440 --> 00:35:53.199
<v Speaker 5>We're doing a lot of.

701
00:35:53.119 --> 00:35:55.679
<v Speaker 9>Repetitive tasks and rise that those could be automated with

702
00:35:56.360 --> 00:35:57.239
<v Speaker 9>technical tools.

703
00:35:57.360 --> 00:35:57.599
<v Speaker 4>Right.

704
00:35:58.360 --> 00:36:01.119
<v Speaker 9>Those tools became very powerful and very popular, and some

705
00:36:01.159 --> 00:36:03.440
<v Speaker 9>people started asking if they could start buying those tools.

706
00:36:03.960 --> 00:36:06.840
<v Speaker 9>So at that point Whereescape stopped as a consulting company

707
00:36:06.920 --> 00:36:09.880
<v Speaker 9>began as a software company. We've got a few thousand

708
00:36:09.880 --> 00:36:13.840
<v Speaker 9>customers around the world. Wow, in Asia, US, North America,

709
00:36:13.920 --> 00:36:16.599
<v Speaker 9>South America, Europe, Middle East Africa.

710
00:36:17.119 --> 00:36:20.039
<v Speaker 4>Wow. And if you still in New Zealand, right, Well,

711
00:36:20.079 --> 00:36:24.159
<v Speaker 4>that's a cool path to start as a consultancy, figure

712
00:36:24.199 --> 00:36:26.800
<v Speaker 4>something out and then build the software. I see that

713
00:36:26.960 --> 00:36:30.960
<v Speaker 4>quite often because as a consultant you're on the front lines,

714
00:36:31.000 --> 00:36:33.280
<v Speaker 4>you're trying to solve things, and to your point, you

715
00:36:33.360 --> 00:36:35.880
<v Speaker 4>keep running into these repetitive tasks and you're like, wait

716
00:36:35.880 --> 00:36:38.159
<v Speaker 4>a minute, why don't we just automate this task or

717
00:36:38.159 --> 00:36:41.559
<v Speaker 4>that task? Documentation being one of those things to say, okay,

718
00:36:41.599 --> 00:36:43.280
<v Speaker 4>what do we do? And that's one thing I love

719
00:36:43.280 --> 00:36:45.360
<v Speaker 4>about the cloud is that I think a lot of

720
00:36:45.440 --> 00:36:49.639
<v Speaker 4>the best practices around things like log in, things like

721
00:36:50.119 --> 00:36:52.639
<v Speaker 4>tracking what's been done, are just sort of baked into

722
00:36:52.719 --> 00:36:55.360
<v Speaker 4>the architecture of cloud. And now we see that with

723
00:36:55.360 --> 00:36:57.599
<v Speaker 4>a lot of these products too, right to bake in

724
00:36:57.760 --> 00:37:02.119
<v Speaker 4>things like documentation and testing. I mean, automated testing is

725
00:37:02.159 --> 00:37:03.360
<v Speaker 4>one of the real keys.

726
00:37:03.119 --> 00:37:06.760
<v Speaker 9>Right, Yeah, So let's talk about documentation first. I'm a programmer,

727
00:37:06.960 --> 00:37:09.119
<v Speaker 9>you know, one of those guys that started coding on

728
00:37:09.320 --> 00:37:12.840
<v Speaker 9>IBM PCs at twelve years old, Neucurabo, Pascal and eighty

729
00:37:12.840 --> 00:37:16.159
<v Speaker 9>eighty six assembly and all that stuff. And like you said,

730
00:37:16.199 --> 00:37:18.360
<v Speaker 9>documentation is one of those phases. I describe it as

731
00:37:18.360 --> 00:37:20.559
<v Speaker 9>the phase of a project at the end where someone

732
00:37:20.639 --> 00:37:23.119
<v Speaker 9>runs around and grabs all the posted notes and types

733
00:37:23.159 --> 00:37:24.920
<v Speaker 9>it into word and as soon as the.

734
00:37:24.960 --> 00:37:26.840
<v Speaker 5>Hit file save, it's obsolete. That's fun.

735
00:37:27.159 --> 00:37:31.480
<v Speaker 9>So The thing about Wearscape and automation tools, the Warscape specifically,

736
00:37:31.559 --> 00:37:33.920
<v Speaker 9>is that we're capturing what you're doing as you're doing it.

737
00:37:34.320 --> 00:37:35.800
<v Speaker 9>So it's not like you're writing a bunch of code

738
00:37:35.840 --> 00:37:37.480
<v Speaker 9>then we have to go figure out what that code means.

739
00:37:37.760 --> 00:37:42.880
<v Speaker 9>But through Wizards, through other automated procedures, intelligence built into it,

740
00:37:42.920 --> 00:37:45.840
<v Speaker 9>not just in code generation, but in design and architecture

741
00:37:45.840 --> 00:37:48.440
<v Speaker 9>as well. We captured the key points where you're doing things.

742
00:37:48.480 --> 00:37:51.559
<v Speaker 9>Something as simple as data lineage, you've got to say

743
00:37:51.679 --> 00:37:54.199
<v Speaker 9>a factor, a dimension at the end of a long

744
00:37:54.320 --> 00:37:57.719
<v Speaker 9>chain of transformations, and a data analyst looks at it

745
00:37:57.760 --> 00:38:00.920
<v Speaker 9>and says, where does this number come from? Anytime you've

746
00:38:00.920 --> 00:38:04.320
<v Speaker 9>got a new dashboard, a new report, the question is

747
00:38:04.360 --> 00:38:06.960
<v Speaker 9>always do you trust these numbers? So the nice thing

748
00:38:06.960 --> 00:38:09.559
<v Speaker 9>about that kind of documentation is I can very very

749
00:38:09.639 --> 00:38:12.880
<v Speaker 9>quickly go back online and see exactly where that number

750
00:38:12.920 --> 00:38:15.679
<v Speaker 9>came from, what transforms it went through, what calculations it

751
00:38:15.719 --> 00:38:18.960
<v Speaker 9>went through. Maybe it came from data combined from three

752
00:38:19.039 --> 00:38:22.199
<v Speaker 9>or four different source systems. That's something that's virtually impossible

753
00:38:22.480 --> 00:38:26.360
<v Speaker 9>to do manually. Track back diagrams be able to present

754
00:38:26.400 --> 00:38:31.119
<v Speaker 9>documentations that the users. Something as simple as when we're

755
00:38:31.159 --> 00:38:34.320
<v Speaker 9>profiling a source system to pull data in. If there's

756
00:38:34.440 --> 00:38:37.280
<v Speaker 9>extended attributes like in SQL server, if there's any kind

757
00:38:37.280 --> 00:38:40.039
<v Speaker 9>of extra information, they get a data catalog. If there's

758
00:38:40.079 --> 00:38:43.599
<v Speaker 9>things we can feed in from the data governance tool

759
00:38:43.639 --> 00:38:48.320
<v Speaker 9>or data cataloging tool, purview or whatever it is, that

760
00:38:48.360 --> 00:38:50.400
<v Speaker 9>can work its way all the way downstream into the

761
00:38:50.400 --> 00:38:53.679
<v Speaker 9>documentation as well. Wow, the documentation is literally a couple

762
00:38:53.679 --> 00:38:55.440
<v Speaker 9>of clicks of the button. And if you're in a

763
00:38:55.440 --> 00:38:59.119
<v Speaker 9>dev environment at QA environment, every morning you can create

764
00:38:59.159 --> 00:39:02.920
<v Speaker 9>this large p has all the necessary documentation in it

765
00:39:03.119 --> 00:39:04.880
<v Speaker 9>and then push that out to a shared drive or

766
00:39:04.880 --> 00:39:06.719
<v Speaker 9>someplace we can get to it. So it's not just

767
00:39:07.119 --> 00:39:09.239
<v Speaker 9>having a docutation that's having to get accessible as.

768
00:39:09.360 --> 00:39:12.159
<v Speaker 4>Rights right, having it accessible. And you know, when I

769
00:39:12.199 --> 00:39:16.800
<v Speaker 4>think about documentation, I think about automatic documentation log files,

770
00:39:16.960 --> 00:39:19.760
<v Speaker 4>and log files are baked into many of these enterprise

771
00:39:19.800 --> 00:39:22.760
<v Speaker 4>systems as a way of knowing what happened, as a

772
00:39:22.800 --> 00:39:25.000
<v Speaker 4>way of knowing what the system did and thus being

773
00:39:25.039 --> 00:39:27.039
<v Speaker 4>able to go back and trace it. But there are

774
00:39:27.079 --> 00:39:28.440
<v Speaker 4>so many of them that you need to have a

775
00:39:28.519 --> 00:39:31.559
<v Speaker 4>process around analyzing the log files, and that's been a

776
00:39:31.559 --> 00:39:33.880
<v Speaker 4>whole thing over I don't know the last twelve fifteen years,

777
00:39:33.920 --> 00:39:36.480
<v Speaker 4>I've seen as companies figure out, hey, that log file

778
00:39:36.559 --> 00:39:39.039
<v Speaker 4>is a source of truths. Let's pay attention to that

779
00:39:39.320 --> 00:39:42.159
<v Speaker 4>and watch for changes and patterns in the log files.

780
00:39:42.360 --> 00:39:44.719
<v Speaker 4>And that's how you can understand what happened, what went wrong,

781
00:39:44.880 --> 00:39:46.840
<v Speaker 4>and then go back and remediate something. Right.

782
00:39:46.920 --> 00:39:49.559
<v Speaker 9>Yes, Spunk is a good example thought, right, So that's

783
00:39:49.559 --> 00:39:53.239
<v Speaker 9>what they do, right, Yeah, they've read in parcelog files.

784
00:39:53.519 --> 00:39:56.840
<v Speaker 9>We're even a step beyond that because pretty much everything

785
00:39:56.880 --> 00:39:58.920
<v Speaker 9>that's going into the log files is already in our

786
00:39:58.960 --> 00:40:02.079
<v Speaker 9>bedded data. So if you're running jobs to work your

787
00:40:02.159 --> 00:40:04.599
<v Speaker 9>data from the source system through all the transforms, through

788
00:40:04.639 --> 00:40:08.719
<v Speaker 9>your data foundation layer into you know, if you're doing bronze, silver,

789
00:40:08.800 --> 00:40:12.320
<v Speaker 9>gold layers or presentation layer or semantic layer, whatever it is,

790
00:40:13.079 --> 00:40:16.880
<v Speaker 9>all that data, all that processing is already on our metadata. Okay,

791
00:40:17.119 --> 00:40:19.679
<v Speaker 9>it's wide open, worse kept to a wide open product.

792
00:40:20.320 --> 00:40:23.280
<v Speaker 9>We don't publish a format of the metadata. But we've

793
00:40:23.280 --> 00:40:25.719
<v Speaker 9>got plenty of customers, plenty of service partners that have

794
00:40:25.719 --> 00:40:28.760
<v Speaker 9>built scripts queries to go look at it. Maybe they've

795
00:40:28.800 --> 00:40:31.800
<v Speaker 9>got jobs that are processing more data or less data

796
00:40:31.800 --> 00:40:34.280
<v Speaker 9>than they used to. Maybe you've got jobs that are

797
00:40:34.320 --> 00:40:38.280
<v Speaker 9>taking longer, and you've got to measure throughput those kinds

798
00:40:38.320 --> 00:40:40.239
<v Speaker 9>of troubleshooting things which you used to have to go

799
00:40:40.280 --> 00:40:42.400
<v Speaker 9>through and look through, and logs you can pull directly

800
00:40:42.440 --> 00:40:46.280
<v Speaker 9>from our metadata. We've got a sister company called yellowfin.

801
00:40:46.039 --> 00:40:47.880
<v Speaker 4>I know phone Yeah, yeah, I know, guys.

802
00:40:47.920 --> 00:40:51.840
<v Speaker 9>Okay, we're adding an analytics package to to our tool itself,

803
00:40:51.840 --> 00:40:54.400
<v Speaker 9>our scheduler that's going to be built into the tool

804
00:40:54.599 --> 00:40:58.400
<v Speaker 9>using their technology, so that you can see the operations

805
00:40:58.400 --> 00:41:00.440
<v Speaker 9>of your data warehouse and how things are working and

806
00:41:00.440 --> 00:41:03.239
<v Speaker 9>when they're slowing down, when they're speeding up, where things work,

807
00:41:03.280 --> 00:41:05.679
<v Speaker 9>where things don't work, to help you not just identify

808
00:41:05.719 --> 00:41:07.719
<v Speaker 9>as a it's a problem, but to identify exactly where

809
00:41:07.760 --> 00:41:09.280
<v Speaker 9>that problem is to help you fix it faster.

810
00:41:09.480 --> 00:41:11.039
<v Speaker 4>Well, and you just picked up on one of the

811
00:41:11.039 --> 00:41:15.440
<v Speaker 4>hottest topics in the world of data today, which is finops, right,

812
00:41:15.480 --> 00:41:18.159
<v Speaker 4>because if you can understand what's happening in there, you

813
00:41:18.199 --> 00:41:22.039
<v Speaker 4>can understand what it costs you. Right, So running certain reports,

814
00:41:22.639 --> 00:41:25.119
<v Speaker 4>doing certain projects, what does it really cost? I mean

815
00:41:25.119 --> 00:41:27.239
<v Speaker 4>a lot of times it's very nebulous. I Mean, you

816
00:41:27.280 --> 00:41:29.079
<v Speaker 4>can see what the line item is on your budget

817
00:41:29.079 --> 00:41:31.000
<v Speaker 4>when it comes through, when the bill comes in but

818
00:41:31.079 --> 00:41:34.599
<v Speaker 4>actually being able to have fine grain views into which

819
00:41:34.880 --> 00:41:37.519
<v Speaker 4>which query cost how much? All that kind of stuff

820
00:41:37.599 --> 00:41:38.599
<v Speaker 4>is extremely valuable.

821
00:41:38.679 --> 00:41:41.800
<v Speaker 9>Right, Yeah, I'm sure with you know, cod based consumption

822
00:41:41.880 --> 00:41:44.960
<v Speaker 9>costs being the big cost for everybody. I won't mention

823
00:41:45.039 --> 00:41:47.360
<v Speaker 9>a specific cloud vendor, but there's a certain one, certain

824
00:41:47.400 --> 00:41:53.159
<v Speaker 9>one that's getting a cold shoulder sometimes, right, because a

825
00:41:53.199 --> 00:41:56.079
<v Speaker 9>lot of them cussion costs are unexpected. Right, So when

826
00:41:56.119 --> 00:41:59.440
<v Speaker 9>you can use analytics, I'm sure it can be added

827
00:41:59.440 --> 00:42:03.159
<v Speaker 9>tooryally package to go query the cloud vendor and find

828
00:42:03.159 --> 00:42:04.119
<v Speaker 9>out what is it costing?

829
00:42:04.480 --> 00:42:05.840
<v Speaker 5>What does it costing me to do this? Right?

830
00:42:06.239 --> 00:42:08.519
<v Speaker 9>And it's it's I used to be in big an

831
00:42:08.559 --> 00:42:12.320
<v Speaker 9>application performance management, and the ninety percent of doing a

832
00:42:12.320 --> 00:42:15.320
<v Speaker 9>good job is knowing where to focus. You can take

833
00:42:15.360 --> 00:42:18.840
<v Speaker 9>something that's very slow but doesn't run very often and

834
00:42:18.920 --> 00:42:20.599
<v Speaker 9>improving it doesn't really give you much of a much

835
00:42:20.599 --> 00:42:22.599
<v Speaker 9>of an improvement. Where you can take something that's just

836
00:42:22.639 --> 00:42:24.760
<v Speaker 9>a little bit slow but runs a lot more frequently

837
00:42:25.559 --> 00:42:27.440
<v Speaker 9>and work on that and get a bigger improvement. So

838
00:42:27.679 --> 00:42:30.679
<v Speaker 9>maybe you've got one particular sequel statement that's incredibly costly

839
00:42:30.840 --> 00:42:33.840
<v Speaker 9>but it runs once a week that may pop to

840
00:42:33.840 --> 00:42:35.679
<v Speaker 9>the top of some list saying, hey, pay attention to me.

841
00:42:35.840 --> 00:42:38.519
<v Speaker 9>Need I need, I need some attention. But really what

842
00:42:38.559 --> 00:42:40.679
<v Speaker 9>you want to pay attention to is the total cost.

843
00:42:41.320 --> 00:42:44.159
<v Speaker 9>So yeah, having analytics packages to be able to slice

844
00:42:44.199 --> 00:42:46.039
<v Speaker 9>and dice that for you and give you, like I said,

845
00:42:46.119 --> 00:42:48.760
<v Speaker 9>someplace to focus so you can you can you can

846
00:42:49.280 --> 00:42:50.800
<v Speaker 9>get more bang for your buck.

847
00:42:50.800 --> 00:42:53.880
<v Speaker 4>Right well, and to understand the inner workings of these things,

848
00:42:53.920 --> 00:42:57.000
<v Speaker 4>how they've come together, what value you're getting from them.

849
00:42:57.000 --> 00:42:59.880
<v Speaker 4>We just talk to a gentleman, Mark Pico, all about value,

850
00:43:00.119 --> 00:43:03.000
<v Speaker 4>understanding what value is. He's got some really interesting concepts there.

851
00:43:03.360 --> 00:43:08.159
<v Speaker 4>But you know, in the data warehouse automation world, let's

852
00:43:08.199 --> 00:43:11.239
<v Speaker 4>face it, there are lots of tedious tasks that come

853
00:43:11.280 --> 00:43:13.559
<v Speaker 4>together to create a data warehouse and then to use

854
00:43:13.559 --> 00:43:16.320
<v Speaker 4>the data warehouse and a wear escape. You are really

855
00:43:16.440 --> 00:43:19.039
<v Speaker 4>the first that I came across to start focusing on

856
00:43:19.400 --> 00:43:21.880
<v Speaker 4>automating some of these tasks. Right, people just think of it,

857
00:43:22.000 --> 00:43:24.079
<v Speaker 4>get the data in and do the analysis and get

858
00:43:24.079 --> 00:43:26.199
<v Speaker 4>the analysis out. There's a lot of other stuff that

859
00:43:26.239 --> 00:43:29.280
<v Speaker 4>happens in between to make that all take place. And

860
00:43:29.320 --> 00:43:31.320
<v Speaker 4>you guys will sit on top of any environment, right

861
00:43:31.360 --> 00:43:34.039
<v Speaker 4>like data bricks or snowflake or whatever, right.

862
00:43:33.920 --> 00:43:36.719
<v Speaker 9>Yeah, there's about say seventeen eighteen different targets we support.

863
00:43:37.039 --> 00:43:39.800
<v Speaker 9>So we talked about this earlier today, you and I

864
00:43:39.840 --> 00:43:42.960
<v Speaker 9>did about how Wearescape over the years has evolved from

865
00:43:42.960 --> 00:43:45.480
<v Speaker 9>a very specific product that works for SQL server and

866
00:43:45.559 --> 00:43:45.920
<v Speaker 9>works for.

867
00:43:45.920 --> 00:43:47.199
<v Speaker 5>Work and works for serio data.

868
00:43:47.559 --> 00:43:50.239
<v Speaker 9>And as the tool grew and use and grew an expansion,

869
00:43:50.559 --> 00:43:52.599
<v Speaker 9>it's become what I would call framework.

870
00:43:53.920 --> 00:43:56.000
<v Speaker 4>This is very interesting, it's a very interesting concept.

871
00:43:56.519 --> 00:43:59.000
<v Speaker 9>I said to my Unix backgrounds, and I told you

872
00:43:59.039 --> 00:44:00.559
<v Speaker 9>it's been long enough ago that I still call it

873
00:44:00.639 --> 00:44:04.280
<v Speaker 9>Unix not Linux. That the best program is the program

874
00:44:04.280 --> 00:44:08.400
<v Speaker 9>that doesn't do anything. It's everything's been externalized into scripts

875
00:44:08.440 --> 00:44:11.440
<v Speaker 9>and to configurations and things like that. Warescape has really

876
00:44:11.480 --> 00:44:14.880
<v Speaker 9>been turned into a framework where you apply packages what

877
00:44:14.880 --> 00:44:17.880
<v Speaker 9>we call enablement packs or rules or other things to

878
00:44:17.960 --> 00:44:19.800
<v Speaker 9>really configure it and how you need to use it.

879
00:44:20.159 --> 00:44:22.000
<v Speaker 9>And I gave you the example of data bricks. We

880
00:44:22.039 --> 00:44:24.960
<v Speaker 9>had about two years ago. We had several prospects come

881
00:44:25.000 --> 00:44:27.519
<v Speaker 9>to us asking about whether wear escape supports data bricks,

882
00:44:27.880 --> 00:44:30.400
<v Speaker 9>and the first three times we said no, and the

883
00:44:30.440 --> 00:44:33.199
<v Speaker 9>fourth time we said, we need a different answer. So

884
00:44:33.440 --> 00:44:36.480
<v Speaker 9>one of our engineers took the Snowflate and Snowflake enablement pack,

885
00:44:36.519 --> 00:44:38.840
<v Speaker 9>which we had and in about two or three weeks

886
00:44:39.159 --> 00:44:43.039
<v Speaker 9>had it working for data bricks. So now we technically

887
00:44:43.079 --> 00:44:45.280
<v Speaker 9>support data bricks. But then we went through some beta

888
00:44:45.320 --> 00:44:48.280
<v Speaker 9>testing and refined it because the enablement packs are geared

889
00:44:48.320 --> 00:44:51.559
<v Speaker 9>towards a specific technology, and within about four months we

890
00:44:51.559 --> 00:44:54.159
<v Speaker 9>had a productized release of supported data bricks. So we

891
00:44:54.199 --> 00:44:56.039
<v Speaker 9>went from zero to sixty in four months.

892
00:44:56.280 --> 00:44:58.440
<v Speaker 4>Maybe that's not something to brag about. Yeah, No, zero

893
00:44:58.559 --> 00:45:00.639
<v Speaker 4>sixty in a few seconds is good. That's not too bad.

894
00:45:00.719 --> 00:45:02.719
<v Speaker 4>That's not too bad. Well, folks, we've got a podcast

895
00:45:02.719 --> 00:45:05.519
<v Speaker 4>bonus segment coming up here. Next, we're talking with Patrick

896
00:45:05.679 --> 00:45:08.760
<v Speaker 4>O'Halleran from wear Escape, the guys who really kind of

897
00:45:08.760 --> 00:45:11.559
<v Speaker 4>invented data warehouse automation way back when. And now I

898
00:45:11.599 --> 00:45:13.559
<v Speaker 4>got seventeen different targets, a lot of stuff going on.

899
00:45:13.719 --> 00:45:15.119
<v Speaker 4>We'll be right back. Don't touch that down.

900
00:45:21.119 --> 00:45:26.039
<v Speaker 3>Welcome back to Inside Analysis. Here's your host, Eric Tabanaugh.

901
00:45:28.679 --> 00:45:31.159
<v Speaker 4>All right, folks, back here on Inside Analysis, talking to

902
00:45:31.239 --> 00:45:35.039
<v Speaker 4>Patrick O'Halleran of war Escape. And you just mentioned in

903
00:45:35.039 --> 00:45:37.519
<v Speaker 4>the break there the design side, you're not just the

904
00:45:37.559 --> 00:45:40.920
<v Speaker 4>code generator, but you're helping in the design of the

905
00:45:41.000 --> 00:45:44.360
<v Speaker 4>data warehouse and helping organizations know how to get the

906
00:45:44.400 --> 00:45:47.159
<v Speaker 4>most of whichever their target system is. Right, let's say

907
00:45:47.159 --> 00:45:50.960
<v Speaker 4>it's Snowflake, which, let's face it was. I watched the

908
00:45:51.000 --> 00:45:53.320
<v Speaker 4>whole had dup Era come and go, and I was

909
00:45:53.320 --> 00:45:55.480
<v Speaker 4>one of the ones scratching my heads about thinking, oh,

910
00:45:56.159 --> 00:45:57.679
<v Speaker 4>I don't think you guys are missing something here. I

911
00:45:57.679 --> 00:45:59.480
<v Speaker 4>don't think it's going to solve all the world's problems.

912
00:45:59.800 --> 00:46:02.599
<v Speaker 4>Then what happened. Snowflake comes out, figures out how to

913
00:46:02.599 --> 00:46:04.519
<v Speaker 4>separate compute from storage. And the other thing they did

914
00:46:04.679 --> 00:46:07.000
<v Speaker 4>was very clever, is they figured out that you know what,

915
00:46:07.039 --> 00:46:09.480
<v Speaker 4>in the old world at data warehousing, the sign of

916
00:46:09.519 --> 00:46:14.599
<v Speaker 4>the schema was really important and really constraining because once

917
00:46:14.639 --> 00:46:16.559
<v Speaker 4>you had it, you weren't going to go changeing. I

918
00:46:16.559 --> 00:46:18.239
<v Speaker 4>want to change the skin, like what are you crazy?

919
00:46:18.440 --> 00:46:21.079
<v Speaker 4>Don't even sales words to me again? And they figure

920
00:46:21.119 --> 00:46:24.280
<v Speaker 4>out how, look, just tear it down, change the schema

921
00:46:24.360 --> 00:46:26.480
<v Speaker 4>and build it back up. Right, wasn't that one of

922
00:46:26.519 --> 00:46:29.880
<v Speaker 4>their big that's a pretty big innovation. But you guys

923
00:46:29.960 --> 00:46:31.559
<v Speaker 4>can help in that process, right, sure?

924
00:46:31.639 --> 00:46:34.039
<v Speaker 9>Sure, I'd say a lot of our customers have come

925
00:46:34.079 --> 00:46:35.920
<v Speaker 9>to us a lot of people aren't familiar with what

926
00:46:36.000 --> 00:46:39.039
<v Speaker 9>their data warehouse automation is or just data automation, so

927
00:46:39.079 --> 00:46:40.960
<v Speaker 9>we wind up doing a lot of education on that,

928
00:46:41.039 --> 00:46:44.079
<v Speaker 9>explaining where the benefits are, where the time savings comes in,

929
00:46:44.119 --> 00:46:47.239
<v Speaker 9>and where their performance improvements come from. And it's not

930
00:46:47.280 --> 00:46:50.679
<v Speaker 9>just code generation. That's one level of automation. I did

931
00:46:50.679 --> 00:46:52.960
<v Speaker 9>a webinar with Ken Graziano.

932
00:46:53.239 --> 00:46:54.599
<v Speaker 4>Yeah, not too old, the data Warrior.

933
00:46:54.840 --> 00:47:00.519
<v Speaker 9>Yeah, about different levels of automation. And think about cruise

934
00:47:00.519 --> 00:47:03.639
<v Speaker 9>control in your car. Okay, my motorcycle, it's cruise control.

935
00:47:03.679 --> 00:47:04.320
<v Speaker 4>Was a throttle lock.

936
00:47:05.320 --> 00:47:06.519
<v Speaker 9>That's that's automation.

937
00:47:06.719 --> 00:47:07.280
<v Speaker 4>That's funny.

938
00:47:07.559 --> 00:47:11.920
<v Speaker 9>Then you've got cruise control, which keeps a constant speed. Okay,

939
00:47:11.960 --> 00:47:14.519
<v Speaker 9>that's maybe another level of automation. Then you've got adaptive

940
00:47:14.519 --> 00:47:16.880
<v Speaker 9>cruise control, which is keeping a space between you and

941
00:47:16.880 --> 00:47:20.199
<v Speaker 9>the front of you and it's suggesting it's it's speed

942
00:47:20.239 --> 00:47:23.199
<v Speaker 9>that way. Those are all levels of automation. Well, Wearescape

943
00:47:23.199 --> 00:47:26.239
<v Speaker 9>has and data warehouse automation has different levels of automation.

944
00:47:26.639 --> 00:47:30.039
<v Speaker 9>So beyond just generating code, beyond just you know, generating

945
00:47:30.159 --> 00:47:32.960
<v Speaker 9>physical Python scripts and DDL and email and all that

946
00:47:33.039 --> 00:47:36.000
<v Speaker 9>kind of stuff, Warescape helps with the design as well,

947
00:47:37.159 --> 00:47:40.960
<v Speaker 9>so I can create a conceptual model of my sources

948
00:47:41.039 --> 00:47:44.199
<v Speaker 9>of my data warehouse, either pull one in if I've

949
00:47:44.199 --> 00:47:46.679
<v Speaker 9>already got one created, or created one for tratch. And

950
00:47:46.719 --> 00:47:50.400
<v Speaker 9>we also always tell people that's a business process. Creating

951
00:47:50.440 --> 00:47:53.599
<v Speaker 9>your data warehouse is a business process, not an IT process. Yeah,

952
00:47:53.719 --> 00:47:56.480
<v Speaker 9>there's certainly technology involved in it, but it solves a

953
00:47:56.519 --> 00:48:00.320
<v Speaker 9>business problem. Okay, So you create your large conceptual model

954
00:48:00.360 --> 00:48:04.800
<v Speaker 9>independent of your source systems, addressing business issues and business

955
00:48:04.800 --> 00:48:08.079
<v Speaker 9>objects and xsts. You define all the attributes of all

956
00:48:08.079 --> 00:48:09.880
<v Speaker 9>those entities that you want to.

957
00:48:09.800 --> 00:48:10.679
<v Speaker 5>Track and report on.

958
00:48:11.039 --> 00:48:13.599
<v Speaker 9>Then you can go and you can profile all your

959
00:48:13.639 --> 00:48:16.920
<v Speaker 9>source systems, find out what data you have, assign attributes

960
00:48:16.920 --> 00:48:21.199
<v Speaker 9>to those attribute types, run profiles not just about the structures,

961
00:48:21.199 --> 00:48:24.960
<v Speaker 9>but the data itself, and then our rules engine can

962
00:48:25.000 --> 00:48:28.800
<v Speaker 9>do that. Sounds kind of silly about anything with that,

963
00:48:29.360 --> 00:48:31.960
<v Speaker 9>So PI, for example, you can bring in data, flag

964
00:48:31.960 --> 00:48:35.079
<v Speaker 9>it as PII. Our rules engine can then do something

965
00:48:35.079 --> 00:48:36.559
<v Speaker 9>with it. What do you want to do? Do you

966
00:48:36.599 --> 00:48:38.159
<v Speaker 9>want to mask it? Do you want to drop it?

967
00:48:38.239 --> 00:48:39.880
<v Speaker 9>Do you want to encrypt it? Do you want to

968
00:48:39.880 --> 00:48:42.079
<v Speaker 9>put it into a separate object and then shut that

969
00:48:42.119 --> 00:48:44.960
<v Speaker 9>off to a separate schema. That's lockdown, You decide what

970
00:48:45.000 --> 00:48:47.239
<v Speaker 9>you want to do, you create the rules, and you

971
00:48:47.280 --> 00:48:50.159
<v Speaker 9>can be sure that anything you've defined as PII in

972
00:48:50.199 --> 00:48:55.039
<v Speaker 9>your source system is handled appropriately. Data quality checks, data

973
00:48:55.079 --> 00:48:58.239
<v Speaker 9>governance checks, things like that being able to grab an

974
00:48:58.280 --> 00:49:00.280
<v Speaker 9>object and say I want this to be a I

975
00:49:00.360 --> 00:49:03.119
<v Speaker 9>want this to be a type two dimension data vault

976
00:49:03.159 --> 00:49:06.480
<v Speaker 9>is built for automation. If you're familiar with data vaults

977
00:49:06.519 --> 00:49:10.000
<v Speaker 9>the whole concept, it's a very pattern based structure for

978
00:49:10.639 --> 00:49:16.559
<v Speaker 9>creating what is an abstract, complicated foundation with ub satellites

979
00:49:16.599 --> 00:49:18.679
<v Speaker 9>and links where things are broken apart in strange ways,

980
00:49:18.880 --> 00:49:23.039
<v Speaker 9>linked and strange ways. Can you build a data vault

981
00:49:23.039 --> 00:49:24.599
<v Speaker 9>with without automation?

982
00:49:24.920 --> 00:49:26.400
<v Speaker 5>I've never seen one.

983
00:49:26.559 --> 00:49:29.000
<v Speaker 9>I would say two thirds of our databault customers have

984
00:49:29.039 --> 00:49:30.800
<v Speaker 9>come to us because they've tried that and failed.

985
00:49:30.920 --> 00:49:31.159
<v Speaker 4>Wow.

986
00:49:32.119 --> 00:49:35.079
<v Speaker 9>But the idea that I can create my conceptual model

987
00:49:35.239 --> 00:49:39.079
<v Speaker 9>and my logical model independent of my physical model, bed

988
00:49:39.119 --> 00:49:42.280
<v Speaker 9>all that within wear escape, attach my source systems to it,

989
00:49:42.719 --> 00:49:45.079
<v Speaker 9>and then push that all out to our builder tool

990
00:49:45.440 --> 00:49:47.320
<v Speaker 9>that will then create all like I said, the DDL,

991
00:49:47.400 --> 00:49:50.880
<v Speaker 9>the DML, the Python scripts and everything else I can build.

992
00:49:51.840 --> 00:49:53.360
<v Speaker 9>I do it in demos all the time. I can

993
00:49:53.400 --> 00:49:55.320
<v Speaker 9>build a star scheme leable effect in a couple of

994
00:49:55.320 --> 00:49:58.400
<v Speaker 9>dimensions from two or three different source systems, and have

995
00:49:58.559 --> 00:50:00.880
<v Speaker 9>a physical model up in snow Lake or data bricks

996
00:50:00.920 --> 00:50:02.679
<v Speaker 9>or a SEQL server or whatever, and I can do

997
00:50:02.760 --> 00:50:05.320
<v Speaker 9>all that in twenty thirty minutes and have the documentation.

998
00:50:05.559 --> 00:50:09.440
<v Speaker 4>Wow, that's crazy. Yeah, Well, it's like it's almost like

999
00:50:09.599 --> 00:50:14.440
<v Speaker 4>you've got to make an analogy to painting. You've got

1000
00:50:15.639 --> 00:50:18.440
<v Speaker 4>a tool that allows someone to imagine what they want

1001
00:50:18.519 --> 00:50:20.400
<v Speaker 4>that painting to look like, and then you hit the

1002
00:50:20.480 --> 00:50:22.199
<v Speaker 4>nentwer button and it goes b let it sprays it

1003
00:50:22.280 --> 00:50:24.679
<v Speaker 4>all on the screen. So the original tool we had

1004
00:50:24.840 --> 00:50:27.079
<v Speaker 4>was our builder tool. It's a bottom up approach. You

1005
00:50:27.280 --> 00:50:29.280
<v Speaker 4>defined load tables and stage tables, and then all the

1006
00:50:29.320 --> 00:50:31.519
<v Speaker 4>objects you want to have in your warehouse. I always

1007
00:50:31.519 --> 00:50:33.480
<v Speaker 4>describe that as you've got a bunch of legos and

1008
00:50:33.519 --> 00:50:35.559
<v Speaker 4>then you've built your dinosaur or your spaceship or whatever

1009
00:50:35.599 --> 00:50:35.920
<v Speaker 4>it is.

1010
00:50:36.639 --> 00:50:39.079
<v Speaker 5>The design tool on top of that is top down.

1011
00:50:40.760 --> 00:50:42.280
<v Speaker 9>Do you tell it what you want to build. I

1012
00:50:42.360 --> 00:50:45.079
<v Speaker 9>want to build a spaceship, a dinosaur, a castle or

1013
00:50:45.079 --> 00:50:47.280
<v Speaker 9>whatever it is, and it then figures out all the

1014
00:50:47.360 --> 00:50:50.079
<v Speaker 9>individual legos that has to produce to build that interesting

1015
00:50:50.199 --> 00:50:52.320
<v Speaker 9>and we have customers that do both and do both successfully.

1016
00:50:52.639 --> 00:50:54.360
<v Speaker 4>So you can do top down and bottom up at

1017
00:50:54.360 --> 00:50:56.679
<v Speaker 4>the same time. And yeah, yeah, don't see how they

1018
00:50:56.719 --> 00:50:57.199
<v Speaker 4>meet together.

1019
00:50:57.400 --> 00:50:59.719
<v Speaker 9>I talk about the design tool as being like a

1020
00:51:00.039 --> 00:51:02.880
<v Speaker 9>an architect for a new house. They've got a blueprint

1021
00:51:03.559 --> 00:51:05.559
<v Speaker 9>to hand that blueprint off to the general contractor who's

1022
00:51:05.599 --> 00:51:08.119
<v Speaker 9>going to build the house. Great, Now, what happens in

1023
00:51:08.159 --> 00:51:11.519
<v Speaker 9>the real world is the architect didn't understand a certain

1024
00:51:11.599 --> 00:51:15.000
<v Speaker 9>zoning rule, or there's a big rock that they can't move,

1025
00:51:15.599 --> 00:51:18.199
<v Speaker 9>or the homeowner decides they want the staircase moved. The

1026
00:51:18.280 --> 00:51:20.199
<v Speaker 9>GC will just go ahead and do those things right.

1027
00:51:20.280 --> 00:51:22.119
<v Speaker 9>The nice thing about our tool is that you can

1028
00:51:22.159 --> 00:51:24.559
<v Speaker 9>do both. You can build the blueprint, you can have

1029
00:51:25.159 --> 00:51:27.559
<v Speaker 9>the builder tool building things, but then you you can

1030
00:51:27.639 --> 00:51:31.119
<v Speaker 9>communicate information back so your design never goes out a date.

1031
00:51:31.199 --> 00:51:32.800
<v Speaker 5>Your mind is always up to date, which is a

1032
00:51:32.880 --> 00:51:34.079
<v Speaker 5>huge feature. That's interesting.

1033
00:51:34.400 --> 00:51:37.159
<v Speaker 4>Yeah, So, I mean people can go buy snowflake and

1034
00:51:37.199 --> 00:51:39.440
<v Speaker 4>they don't have to use something like wear escape. But

1035
00:51:39.519 --> 00:51:42.000
<v Speaker 4>it makes a lot of sense to do that because

1036
00:51:42.360 --> 00:51:43.960
<v Speaker 4>any I was talking about this today with a couple

1037
00:51:43.960 --> 00:51:49.079
<v Speaker 4>other people. Because you've abstracted out the design and build

1038
00:51:49.400 --> 00:51:53.199
<v Speaker 4>layer from the actual management of the warehouse. And one

1039
00:51:53.239 --> 00:51:55.360
<v Speaker 4>thing I love about Snowflake is how they'd say, you know,

1040
00:51:55.480 --> 00:51:57.559
<v Speaker 4>we're going to control your data, you'll do everything around

1041
00:51:57.599 --> 00:52:00.280
<v Speaker 4>it basically, and they have a very clean line of

1042
00:52:00.360 --> 00:52:02.960
<v Speaker 4>demarcation between what they're doing what the partners are doing,

1043
00:52:03.000 --> 00:52:05.039
<v Speaker 4>which I thought it like it's central to their success,

1044
00:52:05.119 --> 00:52:05.760
<v Speaker 4>but what do you think?

1045
00:52:06.280 --> 00:52:06.440
<v Speaker 5>Yeah.

1046
00:52:06.639 --> 00:52:08.360
<v Speaker 9>The other nice thing is because you're working at an

1047
00:52:08.400 --> 00:52:11.239
<v Speaker 9>abstract level, at a conceptual and logical level, you can

1048
00:52:11.280 --> 00:52:14.079
<v Speaker 9>switch targets very very quickly. We had a customer, i'll

1049
00:52:14.159 --> 00:52:16.400
<v Speaker 9>just call them, a large insurance company in the Midwest

1050
00:52:17.400 --> 00:52:19.239
<v Speaker 9>that had been using wear Escape in Terra Data for

1051
00:52:19.480 --> 00:52:22.400
<v Speaker 9>years and they decided they wanted to move have up

1052
00:52:22.719 --> 00:52:25.559
<v Speaker 9>a pilot project in Snowflake. Okay, so they said, what's

1053
00:52:25.559 --> 00:52:28.199
<v Speaker 9>it going to take to recreate our data warehouse and Snowflake. Well,

1054
00:52:28.239 --> 00:52:30.360
<v Speaker 9>we already had all the metadata, we had everything the

1055
00:52:30.440 --> 00:52:33.559
<v Speaker 9>information we needed to generate it because they've been using Wearescape.

1056
00:52:33.920 --> 00:52:35.639
<v Speaker 9>So we went to our offshore team and said, what's

1057
00:52:35.679 --> 00:52:38.280
<v Speaker 9>it going to take to convert this data from Terra

1058
00:52:38.400 --> 00:52:41.039
<v Speaker 9>Data to Snowflake and then create data warehouse And they

1059
00:52:41.079 --> 00:52:43.840
<v Speaker 9>gave me a number, and since I was the manager

1060
00:52:43.840 --> 00:52:46.159
<v Speaker 9>of professional services. I bumped it up ten percent. I

1061
00:52:46.239 --> 00:52:48.800
<v Speaker 9>bumped it up to forty hours, all right, forty hours

1062
00:52:49.039 --> 00:52:51.400
<v Speaker 9>and in a week, in a week, they had their

1063
00:52:51.440 --> 00:52:55.199
<v Speaker 9>physical data warehouse replicated from Terra Data to Snowflake.

1064
00:52:55.400 --> 00:52:58.159
<v Speaker 5>Why, including all the objects, all the procedures and everything else.

1065
00:52:58.280 --> 00:52:58.960
<v Speaker 4>That's crazy.

1066
00:52:59.280 --> 00:53:01.760
<v Speaker 5>That's an exception. But that's that's a real case.

1067
00:53:02.000 --> 00:53:04.199
<v Speaker 4>Well, it's because you had the recipe in wear Escape,

1068
00:53:04.239 --> 00:53:06.679
<v Speaker 4>you had the metaday, you already knew what the structure

1069
00:53:06.679 --> 00:53:08.519
<v Speaker 4>would look like, you had the sort of matrix, the

1070
00:53:08.599 --> 00:53:11.119
<v Speaker 4>blueprint to use your term, and then you could just

1071
00:53:11.199 --> 00:53:13.880
<v Speaker 4>go connect snow flicking build it up.

1072
00:53:14.880 --> 00:53:17.559
<v Speaker 9>Yeah, and if they had customizations and things, that might

1073
00:53:17.599 --> 00:53:19.519
<v Speaker 9>have slowed down. But you know, even if you get

1074
00:53:19.519 --> 00:53:21.599
<v Speaker 9>eighty percent of the way there, right, push up a button.

1075
00:53:21.719 --> 00:53:25.079
<v Speaker 4>Right, great, Wow, this is fantastic. Well look this gentleman

1076
00:53:25.159 --> 00:53:28.320
<v Speaker 4>up online folks, Patrick o'hallerin. So it's a good Polish name,

1077
00:53:28.320 --> 00:53:31.880
<v Speaker 4>of kidding, it's an Irish name. So yeah, look up

1078
00:53:32.199 --> 00:53:35.159
<v Speaker 4>wear Escape, w H E R E Escape. They're part

1079
00:53:35.159 --> 00:53:37.599
<v Speaker 4>of Idea these days. I D E R A and

1080
00:53:37.800 --> 00:53:39.079
<v Speaker 4>we'll talk to you next time. You've been listening to

1081
00:53:39.119 --> 00:53:40.320
<v Speaker 4>Inside Analysis.

1082
00:53:40.280 --> 00:53:42.760
<v Speaker 10>Get all the facts all you need to know on

1083
00:53:43.039 --> 00:53:44.760
<v Speaker 10>KCAA Radio.

1084
00:53:44.880 --> 00:53:48.840
<v Speaker 7>KCAA where Life's much better. So download the app in

1085
00:53:48.880 --> 00:53:52.360
<v Speaker 7>your smart device today. Listen everywhere and anywhere, whether you're

1086
00:53:52.360 --> 00:53:56.559
<v Speaker 7>in southern California, Texas or sailing on the Gulf of Mexico.

1087
00:53:56.880 --> 00:54:01.000
<v Speaker 7>Life s abreeze with KCAA. Download the app in your

1088
00:54:01.039 --> 00:54:02.000
<v Speaker 7>smart device today.

1089
00:54:02.880 --> 00:54:09.199
<v Speaker 3>I'm being yesterday in the dove.

1090
00:54:17.400 --> 00:54:18.480
<v Speaker 4>Casey eight eight.

1091
00:54:20.880 --> 00:54:24.280
<v Speaker 8>What is your plan for your beneficiary to manage your

1092
00:54:24.360 --> 00:54:26.400
<v Speaker 8>final expenses when you pass away?

1093
00:54:27.360 --> 00:54:27.639
<v Speaker 4>Life?

1094
00:54:27.679 --> 00:54:33.440
<v Speaker 8>Insurance annuities, bank accounts, investment accounts all require death activity

1095
00:54:34.360 --> 00:54:38.199
<v Speaker 8>for sakes ten days based on the national average, which

1096
00:54:38.280 --> 00:54:42.360
<v Speaker 8>means no money's immediately available. This causes stress and arguments.

1097
00:54:43.360 --> 00:54:48.239
<v Speaker 8>Simple solution the beneficiary liquidity claim. Use money you already

1098
00:54:48.320 --> 00:54:51.320
<v Speaker 8>have no need to come up with additional funds. The

1099
00:54:51.440 --> 00:54:54.840
<v Speaker 8>funds grow tax deferred and pass tax free to your

1100
00:54:54.920 --> 00:54:59.360
<v Speaker 8>name beneficiaries. The death benefit is paid out in twenty

1101
00:54:59.559 --> 00:55:06.920
<v Speaker 8>four for forty eight hours, out out a deficit as

1102
00:55:06.920 --> 00:55:10.679
<v Speaker 8>a one hundred three zero six fifty eighty.

1103
00:55:10.480 --> 00:55:13.880
<v Speaker 10>Six to Hebot Club's original pure powdy Arco super Ta

1104
00:55:14.000 --> 00:55:17.000
<v Speaker 10>helps build red corpuscles in the blood which carry oxygen

1105
00:55:17.079 --> 00:55:19.960
<v Speaker 10>to our organs and cells. Our organs them cells need

1106
00:55:20.039 --> 00:55:24.320
<v Speaker 10>oxygen to regenerate themselves. The immune system needs oxygen to develop,

1107
00:55:24.360 --> 00:55:27.360
<v Speaker 10>and cancer dies in oxygen. So the tea is great

1108
00:55:27.400 --> 00:55:30.159
<v Speaker 10>for healthy people because it helps build the immune system,

1109
00:55:30.360 --> 00:55:32.800
<v Speaker 10>and it can truly be miraculous for someone fighting a

1110
00:55:32.840 --> 00:55:37.199
<v Speaker 10>potentially life threatening disease due to an infection, diabetes, or cancer.

1111
00:55:37.480 --> 00:55:40.440
<v Speaker 10>The T is also organic and naturally caffeine free. A

1112
00:55:40.519 --> 00:55:42.960
<v Speaker 10>one pound package of T is forty nine ninety five,

1113
00:55:43.039 --> 00:55:46.320
<v Speaker 10>which includes shipping. To order, please visit to Hebot club

1114
00:55:46.400 --> 00:55:49.440
<v Speaker 10>dot com. To hebo is spelled T like tom, a

1115
00:55:50.000 --> 00:55:53.239
<v Speaker 10>h ee b like boy oh. Then continue with the

1116
00:55:53.280 --> 00:55:56.400
<v Speaker 10>word T and then the word club. The complete website

1117
00:55:56.480 --> 00:55:59.119
<v Speaker 10>is to Hebot club dot com or call us at

1118
00:55:59.199 --> 00:56:01.960
<v Speaker 10>eight one eights six one zero eight zero eight eight

1119
00:56:02.159 --> 00:56:05.480
<v Speaker 10>Monday through Saturday, nine am to five pm California time.

1120
00:56:05.679 --> 00:56:08.320
<v Speaker 10>That's eight one eight six one zero eight zero eight

1121
00:56:08.400 --> 00:56:10.320
<v Speaker 10>eight t ebot club dot com.

1122
00:56:11.400 --> 00:56:16.719
<v Speaker 2>Now here's a new concept, digital network advertising for businesses.

1123
00:56:16.840 --> 00:56:21.039
<v Speaker 2>Display your ad inside their building. If a picture's worth

1124
00:56:21.039 --> 00:56:23.320
<v Speaker 2>of a thousand words, your company is going to thrive

1125
00:56:23.400 --> 00:56:28.119
<v Speaker 2>with digital network advertising. Choose your marketing sites or jump

1126
00:56:28.199 --> 00:56:32.519
<v Speaker 2>on the DNA system and advertise with all participants. Your

1127
00:56:32.599 --> 00:56:35.880
<v Speaker 2>business ad or logo is rotated multiple times an hour

1128
00:56:36.400 --> 00:56:41.360
<v Speaker 2>inside local businesses where people will discover your company. Digital

1129
00:56:41.639 --> 00:56:46.920
<v Speaker 2>Network Advertising DNA novel way to be seen and remembered.

1130
00:56:47.320 --> 00:56:51.719
<v Speaker 2>Digital network advertising with networks in Redlands and YUKAIPA call

1131
00:56:51.840 --> 00:56:54.239
<v Speaker 2>in the nine to nine area two two two nine

1132
00:56:54.360 --> 00:56:58.440
<v Speaker 2>two nine three for introductory pricing. That's nine oh nine

1133
00:56:58.599 --> 00:57:02.880
<v Speaker 2>two two two nine U nine three for Digital network

1134
00:57:03.119 --> 00:57:08.280
<v Speaker 2>advertising one last time Digital network Advertising nine oh nine

1135
00:57:08.360 --> 00:57:13.159
<v Speaker 2>two two two nine two nine three. Gillstina KCAA Lomolinda

1136
00:57:13.239 --> 00:57:15.760
<v Speaker 2>at one oh six point five FM, K two ninety

1137
00:57:15.800 --> 00:57:17.039
<v Speaker 2>three c F Burrito.

1138
00:57:16.800 --> 00:57:21.159
<v Speaker 10>Valley, located in the heart of San Bernardino, California. The

1139
00:57:21.280 --> 00:57:25.360
<v Speaker 10>Teamsters Local nineteen thirty two Training Center is designed to

1140
00:57:25.480 --> 00:57:29.400
<v Speaker 10>train workers for high demand, good paying jobs and various

1141
00:57:29.480 --> 00:57:33.519
<v Speaker 10>industries throughout the Inland Empire. If you want a pathway

1142
00:57:33.599 --> 00:57:36.400
<v Speaker 10>to a high paying job and the respect that comes

1143
00:57:36.440 --> 00:57:40.559
<v Speaker 10>with a union contract, visit nineteen thirty two Training Center

1144
00:57:40.719 --> 00:57:46.199
<v Speaker 10>dot org to enroll today. That's nineteen thirty two Trainingcenter dot.

1145
00:57:46.239 --> 00:57:57.719
<v Speaker 11>Org for KCAA ten fifty AM, NBC News Radio and

1146
00:57:57.840 --> 00:58:00.880
<v Speaker 11>Express one of six point five FM consumers in the

1147
00:58:00.960 --> 00:58:03.719
<v Speaker 11>Inland Empire may be filling the bite of inflation more

1148
00:58:03.760 --> 00:58:07.239
<v Speaker 11>than any other metro Area's wallet Hub analyzed the Consumer

1149
00:58:07.320 --> 00:58:10.039
<v Speaker 11>Price Index to determine how inflation has changed in the

1150
00:58:10.159 --> 00:58:14.519
<v Speaker 11>short and longer term. The Riverside Samernardino, Ontario area posted

1151
00:58:14.599 --> 00:58:17.679
<v Speaker 11>the fifth highest change of the twenty three metro areas

1152
00:58:17.719 --> 00:58:21.199
<v Speaker 11>that were studied. Still higher where San Diego, Honolulu, Boston,

1153
00:58:21.280 --> 00:58:24.840
<v Speaker 11>New York, and Chicago. The lowest were Denver, Phoenix and Tampa.

1154
00:58:25.440 --> 00:58:28.960
<v Speaker 11>The San Bernardino County Department of Behavioral Health has partnered

1155
00:58:29.000 --> 00:58:33.159
<v Speaker 11>with various key agencies to create Coast Community Outreach and

1156
00:58:33.199 --> 00:58:36.960
<v Speaker 11>Support Team. The team launched in Fontana in twenty twenty one.

1157
00:58:37.079 --> 00:58:40.719
<v Speaker 11>Twenty twenty three, the City of Ontario implemented the program

1158
00:58:41.039 --> 00:58:45.559
<v Speaker 11>victeam consists of a behavioral health professional, firefighter, law enforcement,

1159
00:58:45.719 --> 00:58:48.599
<v Speaker 11>and a therapy canine. The purpose of the Coast model

1160
00:58:48.840 --> 00:58:52.679
<v Speaker 11>is to provide residence with rapid access to crisis triage

1161
00:58:52.800 --> 00:58:56.480
<v Speaker 11>in a non threatening manner. Beauty industry leaders unite to

1162
00:58:56.519 --> 00:59:01.480
<v Speaker 11>support wildfire evacuees with free services. The CEO of Willpower

1163
00:59:01.599 --> 00:59:06.159
<v Speaker 11>Integrated Marketing is spearheading an initiative to support families displaced

1164
00:59:06.159 --> 00:59:09.519
<v Speaker 11>by the recent fires. A network of beauty professionals will

1165
00:59:09.519 --> 00:59:13.320
<v Speaker 11>provide grooming services and essential personal care items on Monday,

1166
00:59:13.360 --> 00:59:17.000
<v Speaker 11>March tenth at Burners Barber College in Pasadena. The owner

1167
00:59:17.039 --> 00:59:19.639
<v Speaker 11>of the barber college lost his home in the wildfires,

1168
00:59:19.719 --> 00:59:22.719
<v Speaker 11>but believes in the spirit of resilience and has offered

1169
00:59:22.760 --> 00:59:26.199
<v Speaker 11>his facility as a hub to support the community whether

1170
00:59:26.320 --> 00:59:28.880
<v Speaker 11>in the Illan Empire. Highs in the mid seventies with

1171
00:59:29.039 --> 00:59:32.159
<v Speaker 11>lows in the low fifties weekends, Sunday on Saturday with

1172
00:59:32.280 --> 00:59:34.599
<v Speaker 11>highs in the mid sixties and a chance of rain

1173
00:59:34.719 --> 00:59:38.719
<v Speaker 11>on Sunday. For NBC News Radio CASECAA ten fifty AM

1174
00:59:38.920 --> 00:59:41.800
<v Speaker 11>and Express one O six point five FM. I'm Lillian

1175
00:59:41.840 --> 00:59:42.960
<v Speaker 11>Vosquiez and you're.

1176
00:59:42.920 --> 00:59:43.559
<v Speaker 7>Up to date.

1177
00:59:49.280 --> 00:59:53.880
<v Speaker 2>NBC News on KCAA Lomelinda sponsored by Teamsters Local nineteen

1178
00:59:53.960 --> 00:59:57.840
<v Speaker 2>thirty two, protecting the Future of Working Families, Teamsters nineteen

1179
00:59:57.920 --> 00:59:58.559
<v Speaker 2>thirty two.

1180
00:59:58.519 --> 01:00:00.559
<v Speaker 5>Dot org UMMM.

1181
01:00:04.880 --> 01:00:08.519
<v Speaker 11>Welcome to the Fabulous Lifestyle Radio Show. Tune in for

1182
01:00:08.639 --> 01:00:09.199
<v Speaker 11>a vibrant
