WEBVTT 1 00:00:03.919 --> 00:00:08.839 The information economy as a rod. The world is teeming with innovation as new 2 00:00:08.880 --> 00:00:14.880 business models reinvent every in every industry. Inside Analysis is your source of information 3 00:00:14.960 --> 00:00:19.239 and insight about how to make the most of this exciting new era. Learn 4 00:00:19.320 --> 00:00:24.679 more and Inside Analysis dot Comside Analysis dot com. And now here's your host, 5 00:00:24.719 --> 00:00:35.840 thro Eric Kavanaugh. Yes, all right, folks, welcome to the 6 00:00:35.920 --> 00:00:39.280 future. Indeed, your host here, Eric Kavanaugh, the only coast to 7 00:00:39.320 --> 00:00:43.640 coast radio show that's all about the information economy. It's time for Inside Analysis, 8 00:00:44.000 --> 00:00:47.679 and folks, I'm pretty excited to be digging into the wayback machine today 9 00:00:47.679 --> 00:00:51.079 and stretching it all the way to modern times and beyond. Quite Frankie, 10 00:00:51.119 --> 00:00:54.439 we're to talk about the mainframe. That's right, they're still out there. 11 00:00:54.479 --> 00:00:59.200 IBM still sells mainframes, the ZO assets still a very active part of our 12 00:00:59.520 --> 00:01:03.040 commercial world today. Lots of business processes run on mainframes all day, every 13 00:01:03.120 --> 00:01:07.079 day and have been doing so for years, sometimes ten twenty thirty years. 14 00:01:07.480 --> 00:01:11.519 Mainframes are alive and well, we've got an expert with us to kind of 15 00:01:11.519 --> 00:01:15.280 walk through what's going on in that space. Doug Johnson is from Rocket Software 16 00:01:15.400 --> 00:01:19.560 actually used to be asg got purchased by Rocket Software. I just learned that 17 00:01:19.599 --> 00:01:22.640 today. So these shows always teach you something, and we're going to talk 18 00:01:22.680 --> 00:01:26.519 about what's happening and why it matters. So mainframes, like I say, 19 00:01:26.599 --> 00:01:30.560 have been a robust part of our economy for forty plus years, probably almost 20 00:01:30.599 --> 00:01:34.680 fifty years now. A lot of companies have been trying to modernize. But 21 00:01:34.719 --> 00:01:36.959 you know, if it ain't broke, don't fix it. There are a 22 00:01:36.959 --> 00:01:38.799 lot of things that work very well on the main frame, but the question 23 00:01:38.840 --> 00:01:44.200 becomes, how do you integrate mainframe technology with the rest of your stack? 24 00:01:44.239 --> 00:01:48.599 And what is this whole thing the cloud about? What about containers and Kubernetes 25 00:01:48.599 --> 00:01:51.319 and all that fun stuff we've talked about before. That's what we're going to 26 00:01:51.400 --> 00:01:55.400 discuss with our friend Doug Johnson. First of all, tell us a bit 27 00:01:55.400 --> 00:01:59.680 about yourself and what you do in your job as you try to educate and 28 00:01:59.719 --> 00:02:04.640 do product roadmap stuff. Thanks Eric, and I really appreciate the time to 29 00:02:05.079 --> 00:02:07.680 share a little bit about what's going on that way back machine. I like 30 00:02:07.760 --> 00:02:12.080 that, so good stuff. Yeah. So I'm Doug Johnson. I run 31 00:02:12.680 --> 00:02:17.599 product management in our data modernization business unit here at Rocket Software, and my 32 00:02:17.759 --> 00:02:27.759 job really entails working with customers, our account teams and also the industry as 33 00:02:27.879 --> 00:02:34.120 large in terms of the future of what's happening with data and how it's being 34 00:02:34.159 --> 00:02:38.000 modernized in many different areas, including the mainframe. And so my team works 35 00:02:38.000 --> 00:02:40.639 on the roadmaps and works with engineering and customers. It's it's a pretty exciting 36 00:02:40.680 --> 00:02:44.520 place. Yeah, that's good stuff. And you know, when you're in 37 00:02:44.520 --> 00:02:49.400 product management, your main job is to really understand the technology, what does 38 00:02:49.439 --> 00:02:52.400 it do, how does it work, where does it apply? And when 39 00:02:52.400 --> 00:02:55.159 you start talking about the roadmap, obviously you're trying to take care of customer 40 00:02:55.240 --> 00:03:01.199 needs. You're trying to augment what has already been built to handle new capabilities, 41 00:03:01.240 --> 00:03:06.800 for example, and of course in the data modernization space, and you 42 00:03:06.800 --> 00:03:09.800 know, there are a thousand reasons for that. I'm sure one big data 43 00:03:09.840 --> 00:03:15.439 we saw fifteen to five years ago just dominate the conversations in our industry. 44 00:03:15.840 --> 00:03:20.400 Now there's more emphasis on AI and machine learning and things of that nature, 45 00:03:20.400 --> 00:03:23.360 but big data is everywhere now. It's not that it went away, it's 46 00:03:23.360 --> 00:03:24.879 just that we all take it for granted now. And that was one of 47 00:03:24.879 --> 00:03:29.599 the main drivers for this whole modernization concept, right, It's the fact that 48 00:03:29.680 --> 00:03:36.400 we went from relatively small amounts of transactional data to very large amounts of really 49 00:03:36.439 --> 00:03:40.360 machine data, like machines talking to machines, exhaust data, some people call 50 00:03:40.400 --> 00:03:45.240 it. But all these new systems that Google and Facebook and LinkedIn and these 51 00:03:45.280 --> 00:03:49.080 other companies have built, well, they spin out tremendous amounts of data. 52 00:03:49.080 --> 00:03:52.759 And if you can capture that data marry it with other data, you can 53 00:03:52.759 --> 00:03:55.080 start understanding what's happening in your environment, why are things going slow, why 54 00:03:55.080 --> 00:04:00.000 are things working, etc. But that whole big data revolution really drove what 55 00:04:00.080 --> 00:04:03.680 it is now called data monetization. What do you think, Well, it's 56 00:04:03.719 --> 00:04:06.400 a great, great summary of allow some of the big trends that have been 57 00:04:06.400 --> 00:04:12.280 happening in the last several years. And with that, when it comes to 58 00:04:12.280 --> 00:04:15.879 topics around the mainframe, it's very interesting because what we really have experienced is 59 00:04:15.959 --> 00:04:21.360 a lot of customers have gone through. Even though the mainframe has remained the 60 00:04:21.439 --> 00:04:25.800 same over the years, the people who have been working with it in those 61 00:04:25.800 --> 00:04:30.040 systems and understanding what's even there and how it impacts the rest of the business 62 00:04:30.240 --> 00:04:34.199 is just not known. And so this idea of being able to see what 63 00:04:34.399 --> 00:04:39.519 is going on in your environment, but also tying it to other business processes 64 00:04:39.519 --> 00:04:44.600 that you have and the data flows throughout the organization is a key problem customers 65 00:04:44.639 --> 00:04:46.439 have, and so that's one of the some of the things that we do 66 00:04:46.480 --> 00:04:50.439 in our roadmaps is look at tools that can look at the code, look 67 00:04:50.439 --> 00:04:55.240 at the data in those systems, and then stitch it together to see the 68 00:04:55.279 --> 00:04:58.439 connections that are hard to see today. And it really helps, you know, 69 00:04:58.839 --> 00:05:01.120 as part of that modern zation journey, go left, go right, 70 00:05:01.319 --> 00:05:04.439 tweak a little bit here or there, and if someone's looking for some key 71 00:05:04.439 --> 00:05:09.399 information, we can help you find it in terms of bringing it into those 72 00:05:09.439 --> 00:05:13.720 analytics stacks and other things. So again, the mainframe plays a very big 73 00:05:13.839 --> 00:05:16.079 role, and that part of it is just really around having that visibility. 74 00:05:17.319 --> 00:05:20.560 Yeah, and coball, right, a lot of mainframe applications were written in 75 00:05:20.600 --> 00:05:25.480 coball and that was a problem for quite a long while, like the last 76 00:05:25.519 --> 00:05:29.319 five or six years or so. There are so many jobs for coball developers 77 00:05:29.319 --> 00:05:31.680 because guess what, the old apps were written in coball. And even though 78 00:05:32.079 --> 00:05:36.959 that's still the case, something called chat GPT came along and may have helped 79 00:05:38.000 --> 00:05:40.480 out a little bit. I'm curious to hear your thoughts on that, because 80 00:05:40.800 --> 00:05:43.680 a lot of people don't know chat GPT cannot can write poems. It can 81 00:05:43.720 --> 00:05:46.079 also write code. You can write in all sorts of different coding languages, 82 00:05:46.160 --> 00:05:50.600 not just human languages. Right, yeah, it can do that sort of 83 00:05:50.600 --> 00:05:55.040 thing. The interesting thing is when you're talking about the mainframe and that some 84 00:05:55.079 --> 00:05:59.439 of the critical systems that are existing in those environments. You don't want to 85 00:06:00.120 --> 00:06:03.560 enter a three letter prompt or just burning through your code converter and go I 86 00:06:03.600 --> 00:06:08.519 think it'll be good enough for my customer critical transactions. So we haven't seen 87 00:06:08.639 --> 00:06:13.040 in this particular environment, we haven't seen the big push for that, although 88 00:06:13.079 --> 00:06:15.319 we're always watching that space in terms of things that we can offer customers. 89 00:06:15.720 --> 00:06:21.360 But the visibility around, for instance, running some tools against your coball program, 90 00:06:21.680 --> 00:06:25.920 understanding what those connections are, and then maybe where you want to put 91 00:06:25.959 --> 00:06:29.600 investments to make a change. So whether it be used some tools to help 92 00:06:29.639 --> 00:06:33.720 you migrate code or data in those environments, which I'm sure we will talk 93 00:06:33.759 --> 00:06:39.279 more about the data challenges around that, but also just kind of connections is 94 00:06:39.319 --> 00:06:42.839 a first step that we've been focusing on recently. Give you an example is 95 00:06:43.399 --> 00:06:46.839 for instance, around someone trying to run a report against some critical information and 96 00:06:47.079 --> 00:06:53.720 maybe the information exists, maybe in the source from somewhere and they don't know 97 00:06:53.759 --> 00:06:58.480 where, but ultimately it ends up in a bi cube or something where they're 98 00:06:58.480 --> 00:07:00.800 trying to run some reports. But when they do that, they find that 99 00:07:00.839 --> 00:07:05.360 the timeliness of that data is a good twenty forty eight hours behind what a 100 00:07:05.439 --> 00:07:09.959 business needs, and they want to see what is the source of this data 101 00:07:10.000 --> 00:07:13.519 and can I get that data faster? And so that's some of the things 102 00:07:13.560 --> 00:07:16.279 that we do. We help you buy back that time by getting visibility into 103 00:07:16.399 --> 00:07:21.040 where information might exist in the organization, including the mainframe baked into that coball 104 00:07:21.120 --> 00:07:26.160 somewhere, and so then you can go and look at some open standards to 105 00:07:26.480 --> 00:07:30.160 get that data in a more timely fashion. Yeah, that's very interesting because 106 00:07:30.199 --> 00:07:34.079 to your point, there is an immediacy to business these days. You want 107 00:07:34.079 --> 00:07:38.680 to know what's happening right now. Knowing what happened forty eight hours ago could 108 00:07:38.759 --> 00:07:41.600 be useful, but it's not very good for customer experience, it's not very 109 00:07:41.639 --> 00:07:45.160 good for putting out fires. So the question that becomes, how do you 110 00:07:45.240 --> 00:07:47.000 do that? And I guess what you're saying is you've got some tools and 111 00:07:47.040 --> 00:07:53.279 technologies and methods to help companies look into the main frame that they have and 112 00:07:53.360 --> 00:07:56.399 kind of understand where the data is going in, how it's going out, 113 00:07:56.399 --> 00:08:00.279 when it's coming out, and you have other ways of accessing and improvision it. 114 00:08:00.519 --> 00:08:03.079 I mean, there are lots of ways that data is moved around. 115 00:08:03.079 --> 00:08:07.639 ETL was the bread and butter still is for many organizations. Extract transform load, 116 00:08:07.000 --> 00:08:11.959 then you're doing ELT, extract transform, etc. There's data virtualization. 117 00:08:13.079 --> 00:08:16.800 A number of vendors have been that space for a while, and what I'm 118 00:08:16.839 --> 00:08:20.800 hearing from you is that you're able to find ways to see into the environment 119 00:08:20.879 --> 00:08:24.759 and help the business understand where the data is coming from and then how they 120 00:08:24.800 --> 00:08:30.680 can expedite that process. Right. That's exactly right, and it's what I 121 00:08:30.680 --> 00:08:33.480 really like about what you said earlier about the ecosystem and the mainframe is really 122 00:08:33.519 --> 00:08:39.639 important because obviously the world isn't just one technology today, it's a whole series 123 00:08:39.679 --> 00:08:43.519 of technologies. And one of the things that we've really focused on is making 124 00:08:43.559 --> 00:08:48.120 the data that's permeating the entire organization being able to see it and manage it 125 00:08:48.600 --> 00:08:52.799 both for those use cases I was mentioning around, for instance, reporting, 126 00:08:52.960 --> 00:08:58.759 but also very critically things like compliance or doing business change as an example, 127 00:08:58.840 --> 00:09:01.399 So if you consider, hey, there's a project we're considering where we want 128 00:09:01.399 --> 00:09:07.879 to change a system, maybe change a user experience, what impact would that 129 00:09:07.960 --> 00:09:11.240 have to other parts of my organization, including those critical information that exists on 130 00:09:11.240 --> 00:09:15.399 the mainframe and has managed in those environments. And that's some of the things 131 00:09:15.440 --> 00:09:20.200 that are technologies and some of the investments we've been making help customers really gain 132 00:09:20.240 --> 00:09:24.799 those insights to make a choice again on where to put those investments and what 133 00:09:24.919 --> 00:09:28.879 kind of impact of analysis it might have in terms of that decisioning. Yeah, 134 00:09:28.919 --> 00:09:33.039 and the impact analysis is huge, right, because when you transform the 135 00:09:33.120 --> 00:09:37.000 business, that means you change something. These days, that means you're either 136 00:09:37.159 --> 00:09:41.080 changing code, or you're adding code, or you're changing an architecture. You're 137 00:09:41.120 --> 00:09:43.559 doing something new. And let's face it, there are lots and lots of 138 00:09:43.600 --> 00:09:46.519 shining new objects these days. There are lots of new ways to get data. 139 00:09:46.559 --> 00:09:52.919 There's streaming with technologies like Kafka or Pulsar. You've got snowflakes of the 140 00:09:52.919 --> 00:09:56.960 world and data bricks and all these other amazing technologies that have come along to 141 00:09:58.039 --> 00:10:01.000 at people that analyze data, but that doesn't change the fact that a lot 142 00:10:01.039 --> 00:10:05.759 of the data and the systems are still running on the mainframe. So coming 143 00:10:05.840 --> 00:10:09.840 up with that information architecture that's the real key to success these days and being 144 00:10:09.879 --> 00:10:13.879 able to see into these environments. Do the impact analysis, as you suggest, 145 00:10:13.320 --> 00:10:18.039 is crucial to be able to understand what you can change and how you 146 00:10:18.080 --> 00:10:24.559 can change it without breaking something right done absolutely and there are millions and millions 147 00:10:24.559 --> 00:10:28.960 of dollars and then lots and lots of armies of people working at this and 148 00:10:30.000 --> 00:10:33.759 so if you get it right or get it wrong, it's huge impact to 149 00:10:33.799 --> 00:10:37.679 a business. It can really make the difference between are you competitive compared to 150 00:10:37.679 --> 00:10:43.360 what others are doing, or you actually behind if you make the wrong choices. 151 00:10:43.399 --> 00:10:46.480 And that's what we really try to help organizations is buy back that time 152 00:10:46.799 --> 00:10:52.000 and reduce that risk of that critical decision making and along the way in terms 153 00:10:52.039 --> 00:10:56.240 of that decision to make what we also find it knowing the strategy that people 154 00:10:56.279 --> 00:11:01.360 have with the mainframe is really important some organization and say hey, we have 155 00:11:01.440 --> 00:11:05.200 these critical systems, we've had them forever, We're going to keep building an 156 00:11:05.240 --> 00:11:09.519 ecosystem around it, or some other customers say, we really want to have 157 00:11:09.559 --> 00:11:13.799 a strategy where we can take some systems as part of that and have a 158 00:11:13.879 --> 00:11:18.080 hybrid approach where we start moving some of that to the cloud. And then 159 00:11:18.080 --> 00:11:22.240 some customers are all in where they in a five or ten year, fifteen 160 00:11:22.279 --> 00:11:24.759 year time frame even in some cases, they want to have that trail map 161 00:11:26.120 --> 00:11:31.080 to perhaps move from what they have today to some future goodness that they have. 162 00:11:31.200 --> 00:11:33.960 And so that's a key area also in terms of that visibility that it's 163 00:11:35.000 --> 00:11:39.279 critical to the overall corporate strategy and investment portfolio that happens. Yeah, right, 164 00:11:39.320 --> 00:11:43.519 well, and so we should appreciate the fact that mainframes work. And 165 00:11:43.559 --> 00:11:48.399 I can tell you in the operations world, if something isn't broken, they 166 00:11:48.399 --> 00:11:50.399 don't want you to fix it. I mean just generally speaking, leave it 167 00:11:50.399 --> 00:11:56.480 alone is their main message, because they're the ones responsible for you know, 168 00:11:56.519 --> 00:12:00.279 that's where this whole business it divide, I think came from was because the 169 00:12:00.279 --> 00:12:01.960 business wanted to change something. It is like, guys, what are you 170 00:12:01.960 --> 00:12:05.759 talking about? We're ubbing trouble keeping this running as it is. Don't complicate 171 00:12:05.840 --> 00:12:09.240 things, right, But then the cloud comes along and machine learning comes along, 172 00:12:09.240 --> 00:12:13.159 and AI matures and all these things develop, so there's increased pressure on 173 00:12:13.200 --> 00:12:16.919 the business to change something. The key is what do you change? And 174 00:12:16.960 --> 00:12:22.200 it sounds to me like you're offering a very positive surface for being able to 175 00:12:22.240 --> 00:12:26.879 assess what is the current state, how are these applications running, if we 176 00:12:26.039 --> 00:12:28.759 change this, if we change that, how is that going to impact us 177 00:12:28.840 --> 00:12:31.960 down the line? And you know, no doubt about it, Rushing to 178 00:12:33.039 --> 00:12:35.879 the cloud is not something anyone should do. You really want to understand what 179 00:12:35.960 --> 00:12:41.279 are are these business processes, what can we modernize? Where can we modernize 180 00:12:41.279 --> 00:12:43.360 them? And you wind up usually having a sort of layer of abstraction right 181 00:12:43.679 --> 00:12:48.559 above the main frame, but below the cloud or below the on prem data 182 00:12:48.600 --> 00:12:52.080 center director of the data center. You want these layers of abstraction where you 183 00:12:52.080 --> 00:12:56.720 can kind of understand what's moving where and then make your changes in those environments 184 00:12:56.759 --> 00:13:03.720 that affect either upstream or downstream. Right absolutely, and as part of those 185 00:13:03.759 --> 00:13:07.440 that layered approach that you were talking about, trying to really deal with a 186 00:13:07.519 --> 00:13:13.399 lot of the unstructured data that also exists elsewhere in the organization, including the 187 00:13:13.440 --> 00:13:18.480 mainframe, is really important. Things like customer statements or building information. You 188 00:13:18.519 --> 00:13:22.440 know things that aren't very important to customers, right, and so you as 189 00:13:22.480 --> 00:13:26.679 you go to look and modernize how you're doing that, you just really want 190 00:13:26.679 --> 00:13:31.200 to be very thoughtful and you want to you want to make investments that as 191 00:13:31.240 --> 00:13:37.840 you, for instance, build out a new customer portal or build out a 192 00:13:37.879 --> 00:13:41.480 mobile app experience as part of that. When you have that API, that 193 00:13:41.519 --> 00:13:43.080 abstraction that you were talking about, you want to make sure it can get 194 00:13:43.159 --> 00:13:48.240 information wherever it may exist in the enterprise, and of course that also includes 195 00:13:48.279 --> 00:13:52.399 the mainframe. But you don't want to put the burden on, for instance, 196 00:13:52.440 --> 00:13:58.200 an individual app application developer to have to know about arcane formats like AFP 197 00:13:58.519 --> 00:14:01.159 or whatnot. And so that's also what some of our technologies do, is 198 00:14:01.200 --> 00:14:05.279 we help you access that unstructured information and we put it in a modern format 199 00:14:05.320 --> 00:14:11.279 on the fly so that your application developers don't have to know anything. Matter 200 00:14:11.320 --> 00:14:13.879 of fact, what's interesting is people using our technology in many cases, they 201 00:14:13.879 --> 00:14:18.519 don't even know what's on the back end from an end user perspective or an 202 00:14:18.559 --> 00:14:22.799 API perspective. And that fits very much into that kind of middle layer that 203 00:14:22.799 --> 00:14:26.000 you were talking about to really help with that abstraction where you don't have to 204 00:14:26.080 --> 00:14:31.919 force on a developer or an end user person to really have to know about 205 00:14:31.919 --> 00:14:35.799 that endpoint of where it comes from that data right. And you know, 206 00:14:35.960 --> 00:14:39.039 I'll throughout an interesting point here, just kind of an analogy. I just 207 00:14:39.080 --> 00:14:41.720 came back from Clickworld last week and they were talking about how they're moving to 208 00:14:41.720 --> 00:14:46.519 the cloud click Cloud. But they also were very careful to say time and 209 00:14:46.559 --> 00:14:50.519 again, we are not going to forget about all the on prem installations that 210 00:14:50.559 --> 00:14:52.000 we have. So we're still going to be taking care of these technologies. 211 00:14:52.039 --> 00:14:56.679 We're still going to make sure everything works fine in that world as we encourage 212 00:14:56.679 --> 00:14:58.879 people to go to the cloud. And one of the key considerations is that, 213 00:15:00.200 --> 00:15:03.039 but with any sort of applications you've been using and gotten used to, 214 00:15:03.480 --> 00:15:07.240 if you port that to the cloud, usually what happens is you only port 215 00:15:07.279 --> 00:15:11.039 the bare bone stuff first, and then over time you start adding features that 216 00:15:11.120 --> 00:15:13.279 were on prem. And that's for a whole variety of reasons. One dev 217 00:15:13.360 --> 00:15:18.080 time just that takes time to do stuff right. But the point being, 218 00:15:18.080 --> 00:15:22.480 if you were to go straight to a cloud instantiation of some data warehouse, 219 00:15:22.519 --> 00:15:26.600 for example, you'll lose a whole lot of context. You lose functionality, 220 00:15:26.600 --> 00:15:28.759 you lose things, and that's why you want to be careful about what you 221 00:15:28.840 --> 00:15:33.840 do here, because number one, to be able to replatform or sort of 222 00:15:33.840 --> 00:15:39.799 re architect refactor a whole existing environment and the cloud is going to be really 223 00:15:39.799 --> 00:15:43.960 expensive. It's going to be painful to do it. Even cloud natively for 224 00:15:43.000 --> 00:15:46.200 example, it sounds good, but it's very difficult to pull that off. 225 00:15:46.279 --> 00:15:52.200 So I like that you use this term thoughtful to describe how your team should 226 00:15:52.240 --> 00:15:54.639 be as you look at your environment and figure out ways to go forward. 227 00:15:54.720 --> 00:15:58.000 Right, you want to take time to do that, really document everything and 228 00:15:58.039 --> 00:16:03.919 test all along the way, right, Yeah, absolutely, And what's interesting 229 00:16:03.039 --> 00:16:08.200 is organizations definitely going to take a very measured approach, but some organizations also 230 00:16:08.320 --> 00:16:12.240 say we want to take a measured approach, but there's some footprint that we 231 00:16:12.320 --> 00:16:18.159 want to move faster, perhaps even away from the mainframe in some cases. 232 00:16:18.480 --> 00:16:22.039 And so the technologies that we've been working on really help you be able to 233 00:16:22.080 --> 00:16:29.080 move the data without reprocessing it to popular endpoints like for instance S three, 234 00:16:29.120 --> 00:16:33.240 And you can even do hybrid models where where your processing still has done on 235 00:16:33.279 --> 00:16:37.840 the mainframe, but your storage is actually done in a modern fashion. Like 236 00:16:37.919 --> 00:16:41.320 for instance, like with the S three or something like this. And so 237 00:16:41.440 --> 00:16:48.879 what we find is it's really about the the applications before and after the data 238 00:16:48.879 --> 00:16:53.960 that are super important. If you disrupt those thousands millions of lines of code 239 00:16:53.960 --> 00:16:57.919 in many cases that are sitting before and after that data, that's where the 240 00:16:59.000 --> 00:17:02.360 real disruption that happen. And so we've worked on a lot of tools that 241 00:17:02.399 --> 00:17:07.160 can help you mix and match a lot of these hybrid use cases with clouds. 242 00:17:07.200 --> 00:17:10.519 So it doesn't have to be an all or nothing. If your organization 243 00:17:10.599 --> 00:17:15.720 is saying we must move faster, we must do some digital change to change 244 00:17:15.720 --> 00:17:21.559 and experience or bring some data to a customer in a fresh way. Yeah, 245 00:17:21.599 --> 00:17:25.359 that makes a lot of sense because there are pressures to move to the 246 00:17:25.400 --> 00:17:27.319 cloud. There are lots of good reasons to move to the cloud. It's 247 00:17:27.359 --> 00:17:33.160 a fantastic marshaling area for functionality. It's a good marshaling area even for data, 248 00:17:33.200 --> 00:17:37.000 at least data that's born in the cloud. Now taking a whole mountain 249 00:17:37.000 --> 00:17:40.160 of data from on prem and pushing it up into the cloud. There are 250 00:17:40.160 --> 00:17:42.160 companies doing that. You have to be careful about how you do that because 251 00:17:42.240 --> 00:17:45.279 you really want to understand your access patterns. You want to understand what people 252 00:17:45.279 --> 00:17:48.359 are doing with that data, how does it interact with your applications. All 253 00:17:48.359 --> 00:17:52.400 that stuff can be mapped out, and really should be mapped out before you 254 00:17:52.440 --> 00:17:55.319 ever try to pull something like that, because if you go too quickly, 255 00:17:55.519 --> 00:17:57.960 you're gonna have a very unpleasant route awakening when it arrives. But both don't 256 00:17:57.960 --> 00:18:00.599 touch up, that will be right back. You're listening to inside analysis. 257 00:18:03.839 --> 00:18:07.279 What if you could own a piece of the future. What if you could 258 00:18:07.319 --> 00:18:11.200 build your next castle not on sand, but on the bedrock of a modern 259 00:18:11.240 --> 00:18:15.720 blockchain ecosystem. The first Internet gold rush made millionaires, The second wave is 260 00:18:15.759 --> 00:18:22.160 minting billionaires, but the third wave is just gathering now and anyone can get 261 00:18:22.200 --> 00:18:26.680 in on the action. Hop online to crowdpointech dot com to learn how you 262 00:18:26.720 --> 00:18:30.920 can secure a foothold in the blockchain revolution. Whatever your passion, wherever you 263 00:18:30.960 --> 00:18:36.160 want to go in life, there's an opportunity awaiting you right now. Go 264 00:18:36.279 --> 00:18:41.440 to crowdpointech dot com to learn how the blockchain will fuel the next generation of 265 00:18:41.559 --> 00:18:47.839 innovation in this globally connected world. That's crowdpointtech dot com, your trusted agent 266 00:18:48.000 --> 00:18:52.920 in an untrusted world. What's the longest running radio show in the world focused 267 00:18:52.920 --> 00:18:56.640 on data, DM Radio. Want to be a guest sometime, send an 268 00:18:56.680 --> 00:19:02.559 email to Info at dmradio dot biz. That's info at DM radio dot biz. 269 00:19:02.880 --> 00:19:07.599 Can your IRA stand up to the next financial crisis that our top economists 270 00:19:07.599 --> 00:19:11.319 are saying is at our doorsteps? By allocating a percentage of your IRA into 271 00:19:11.440 --> 00:19:17.519 physical gold and silver with a tax free rollover, you can diversify in safeguard 272 00:19:17.559 --> 00:19:22.279 your holdings from turbulent markets and economic downturns by putting your IRA back on the 273 00:19:22.359 --> 00:19:27.200 gold standard. Find out how to safeguard your STS with a tax free rollover 274 00:19:27.319 --> 00:19:33.640 with a Genesis Gold IRA, the only IRA that can hold physical precious metals. 275 00:19:33.799 --> 00:19:37.319 Call now for your free gold and silver report. Protect your IRA today 276 00:19:37.480 --> 00:19:42.160 with one simple phone call and learn how to qualify for up to ten thousand 277 00:19:42.200 --> 00:19:48.279 dollars in free silver called Genesis Gold Group Empowering Faith Driven Stewardship. Eight hundred 278 00:19:48.440 --> 00:19:55.160 six four four eight six one one eight hundred six four four eight six one 279 00:19:55.319 --> 00:20:00.279 one eight hundred six four four eight six one one. That's eight hundre rich 280 00:20:00.359 --> 00:20:06.240 six four four eighty six eleven. Do you have an old car sitting around 281 00:20:06.279 --> 00:20:10.079 your house. Maybe you're even paying insurance on it. Well, if you 282 00:20:10.119 --> 00:20:14.599 don't need that car anymore, donate it running or not to the United Breastcancer 283 00:20:14.640 --> 00:20:18.200 Foundation. They will even come and pick it up for free and give you 284 00:20:18.240 --> 00:20:22.640 a receipt for a tax donation. Breastcancer screening could save the life of someone 285 00:20:22.680 --> 00:20:26.400 you love, and right now they need your help. They want to save 286 00:20:26.480 --> 00:20:32.079 more lives through early detection by offering women free or low cost breasts screening exams, 287 00:20:32.240 --> 00:20:34.519 and that's what your old car helps to pay for. So get your 288 00:20:34.519 --> 00:20:40.000 phone out and call right now to donate your car to the United Breastcancer Foundation. 289 00:20:40.519 --> 00:20:42.400 Remember, they will come pick it up for free and give you a 290 00:20:42.440 --> 00:20:48.680 tax donation receipt. Call right now at eight hundred two four five one three 291 00:20:48.759 --> 00:20:52.920 seven five eight hundred two four five one three seven five. That's eight hundred 292 00:20:53.039 --> 00:20:59.119 two four five one three seven five eight hundred two four five one three seven 293 00:20:59.240 --> 00:21:04.680 five. Do you have an old car sitting around your house, Maybe you're 294 00:21:04.720 --> 00:21:08.480 even paying insurance on it. Well, if you don't need that car anymore, 295 00:21:08.759 --> 00:21:14.319 donate it running or not to the United Breastcancer Foundation. They will even 296 00:21:14.359 --> 00:21:17.279 come and pick it up for free and give you a receipt for a tax 297 00:21:17.319 --> 00:21:21.960 donation. Breastcancer screening could save the life of someone you love, and right 298 00:21:22.000 --> 00:21:26.359 now they need your help. They want to save more lives through early detection 299 00:21:26.559 --> 00:21:30.079 by offering women free or low cost breast screening exams. And that's what your 300 00:21:30.079 --> 00:21:33.799 old car helps to pay for. So get your phone out and call right 301 00:21:33.839 --> 00:21:38.559 now to donate your car to the United Breastcancer Foundation. Remember, they will 302 00:21:38.559 --> 00:21:42.359 come pick it up for free and give you a tax donation receipt. Call 303 00:21:42.519 --> 00:21:48.799 right now at eight hundred two four five one three seven five eight hundred two 304 00:21:48.839 --> 00:21:52.559 four five one three seven five. That's eight hundred two four five one three 305 00:21:52.640 --> 00:22:07.359 seven five, eight hundred two four five one three seven five. Welcome back 306 00:22:07.400 --> 00:22:15.440 to Inside Analysis. Here's your host, Eric Cavanaugh. All right, folks, 307 00:22:15.519 --> 00:22:18.400 tickets to the future. Indeed, I want to go to the future 308 00:22:18.440 --> 00:22:22.279 where the systems are always running quickly. I never I'm on the phone with 309 00:22:22.400 --> 00:22:26.720 some customer service represolve. I'm sorry, systems are running kind of slow today. 310 00:22:26.920 --> 00:22:30.440 I don't want that. Nobody wants that. You want stuff to work, 311 00:22:30.799 --> 00:22:32.839 right, that's what you want. You want to go to Amazon buy 312 00:22:32.880 --> 00:22:34.279 stuff, go to some other side buy stuff. And have it work and 313 00:22:34.279 --> 00:22:38.440 have it be seamless and quick and fast and secure. That's what we want. 314 00:22:38.759 --> 00:22:41.519 That's the good stuff. You got to modernize to get that. You're 315 00:22:41.519 --> 00:22:45.400 not going to get that with some of these older architectures. And so I'm 316 00:22:45.400 --> 00:22:48.559 talking today with Doug Johnson, who is an expert in this space with Rocket 317 00:22:48.640 --> 00:22:51.599 software these days, a little bit name by the way, how can you 318 00:22:51.640 --> 00:22:55.440 go wrong with Rocket software? But we were talking about containers in the break 319 00:22:55.440 --> 00:22:57.599 there, and I'll just explain quickly to the audience for those of you who 320 00:22:57.640 --> 00:23:03.359 haven't heard before. Google came up with this project called kubernets. If you 321 00:23:03.359 --> 00:23:07.279 ever see kh s K eight, that's a sort of abbreviation for it. 322 00:23:07.839 --> 00:23:14.240 It's a container orchestration system. But basically it's sort of like a de facto 323 00:23:14.359 --> 00:23:18.319 operating system for the cloud. Now, Kubernets does run on Linux, so 324 00:23:18.359 --> 00:23:22.680 that's the operating system that it uses, but it kind of operates like a 325 00:23:22.759 --> 00:23:26.480 de facto OS. And the best way I heard it describe was by a 326 00:23:26.519 --> 00:23:30.119 girl in the open source world who said, look at containers as little boxes 327 00:23:30.119 --> 00:23:34.359 for system processes, so little things that your computer has to do, like 328 00:23:34.480 --> 00:23:38.200 open and application or a lot of times. I'll use a spell check as 329 00:23:38.240 --> 00:23:41.480 an example, Right, you could use a spell check in Word, or 330 00:23:41.480 --> 00:23:45.720 you could use a spell check in Excel in other applications, that's a service. 331 00:23:45.720 --> 00:23:48.880 The spell check is like a service. And way back in the days 332 00:23:48.880 --> 00:23:52.519 of service oriented architecture, we had course grain services and fine grain services. 333 00:23:52.599 --> 00:23:56.559 It was the same general vision. But then Kuberneti came along and really kind 334 00:23:56.559 --> 00:24:00.480 of revolutionize how that stuff gets done. A lot of the new apps that 335 00:24:00.559 --> 00:24:03.400 you see out there, a lot of the cool new stuff that's happening in 336 00:24:03.440 --> 00:24:07.640 the world of technology, is running on Kuberneties. It's everywhere now. They've 337 00:24:07.680 --> 00:24:11.799 basically won this whole shebang, and it's an open source technology, so you 338 00:24:11.799 --> 00:24:14.319 don't have to pay to use Kuberneties, but you do have to get people 339 00:24:14.319 --> 00:24:17.359 who know how to do it. It's not the easiest thing in the world 340 00:24:17.359 --> 00:24:19.920 to figure out, so there is obviously a cost to it in terms of 341 00:24:19.960 --> 00:24:23.799 deployment and management, etc. But it really has one to day and containerization 342 00:24:23.880 --> 00:24:26.799 is a new way to do things. And the last thing I'll say about 343 00:24:26.839 --> 00:24:30.640 it is that what's nice is that because you've broken it into lots of little, 344 00:24:30.680 --> 00:24:34.440 teeny tiny pieces, the big stuff doesn't break as much. Right, 345 00:24:34.559 --> 00:24:37.519 used to get sites that just crash and didn't work. You don't get that 346 00:24:37.559 --> 00:24:41.440 as much in these new environments. What you'll get is one little piece of 347 00:24:41.440 --> 00:24:44.079 it that doesn't work. And then what they do is they kill that pod. 348 00:24:44.160 --> 00:24:45.680 Basically the pod just say up, kill that guy will start again. 349 00:24:47.200 --> 00:24:49.720 But with that, I'll throw it over to Doug Johnson. Kubernatis is changing 350 00:24:49.799 --> 00:24:53.519 the world, but it's not the main frame, and we have to find 351 00:24:53.519 --> 00:24:56.440 a way to get these two systems to talk together and to work together. 352 00:24:56.480 --> 00:25:00.240 And that's kind of what you guys are working on right Yes, absolutely, 353 00:25:00.279 --> 00:25:06.000 And with that, there's a number of areas that our customers and we've seen 354 00:25:06.000 --> 00:25:10.160 in the industry in terms of leveraging the mainframe with kubernets. So you know, 355 00:25:10.160 --> 00:25:12.920 at the base level is we were talking before the break, we were 356 00:25:12.920 --> 00:25:18.160 talking about this kind of abstraction layer where you can access data. And so 357 00:25:18.200 --> 00:25:21.000 what we do is we create some of these pods that you were talking about 358 00:25:21.039 --> 00:25:25.480 that run in that Kubernets layer and put a front end essentially in front of 359 00:25:25.480 --> 00:25:29.880 that mainframe and then provide all sorts of data services to that. So everything 360 00:25:29.880 --> 00:25:33.480 from just raw access like we were talking about before, where it can convert 361 00:25:33.920 --> 00:25:37.440 formats. For a developer or an end user, we can get access to 362 00:25:37.440 --> 00:25:41.240 information. But also if you need greater scalability, it can just create another 363 00:25:41.240 --> 00:25:45.319 pod and have that kind of level of scalability. But then there's also other 364 00:25:45.599 --> 00:25:49.400 things that happen along that same vein. Is within that layer is also where 365 00:25:49.400 --> 00:25:56.400 we put some protective services. So it's the mainframe or really any critical enterprise 366 00:25:56.480 --> 00:26:00.400 information, you really want to make sure it's thoroughly protected, and so we 367 00:26:00.519 --> 00:26:03.880 do everything from having a very strong access control layer that can even look at 368 00:26:03.920 --> 00:26:07.599 where you are in the world and determine whether you can access something, or 369 00:26:07.640 --> 00:26:11.680 even do things like redact information on the fly for you, so if you 370 00:26:11.720 --> 00:26:17.240 go to access some sensitive information, it can make sure that you can see 371 00:26:17.279 --> 00:26:21.960 certain information and then other persons see other information. And so those are some 372 00:26:22.000 --> 00:26:25.799 of the things we've been working on and customers are really enjoying. Yeah, 373 00:26:25.839 --> 00:26:30.000 that's a very interesting comment you just made. There are new technologies that are 374 00:26:30.039 --> 00:26:33.119 coming out, technologies like go Kira, and there's one called Immuta, and 375 00:26:33.160 --> 00:26:37.680 there's one called Previous Era, and there's a few others that have come along 376 00:26:37.680 --> 00:26:44.960 that are all about trying to protect PII personally identifiable information as it gets accessed 377 00:26:45.160 --> 00:26:48.519 by analytic applications right and or even AI. Right. So you've got all 378 00:26:48.519 --> 00:26:52.519 these powerful technologies now, analytics technologies, but what data am I supposed to 379 00:26:52.559 --> 00:26:56.680 have access to? Well, I mean you in the old days, you 380 00:26:56.680 --> 00:27:00.799 could control that a couple different ways. You could control it at access at 381 00:27:00.799 --> 00:27:03.720 the database level, which is something you can do, but it's hard to 382 00:27:03.759 --> 00:27:07.759 manage at scale. That's the problem. Where you could govern it at the 383 00:27:07.000 --> 00:27:11.279 consumption layer in the app somewhere, but there was nothing in the middle, 384 00:27:11.359 --> 00:27:14.640 or nothing meaningful in the middle. And that's all changing now, which is 385 00:27:14.680 --> 00:27:17.720 good because what you want and we're seeing more of this or these sort of 386 00:27:17.799 --> 00:27:22.720 dynamic technologies for in the moment determining well should this person really get access to 387 00:27:22.759 --> 00:27:26.480 this information or not? And so you can see this with sort of ephemeral 388 00:27:26.519 --> 00:27:30.839 access, right, like you get access for thirty minutes or for an hour 389 00:27:30.000 --> 00:27:33.599 or fifteen minutes or something like that. These are all designed to protect the 390 00:27:33.640 --> 00:27:38.200 systems and protect the information because we've seen i mean, look at the Colonial 391 00:27:38.240 --> 00:27:42.000 pipeline hack and how that took down the East Coast of people not being able 392 00:27:42.039 --> 00:27:45.759 to drive because they shut down the pipeline that delivers the gas. Right, 393 00:27:45.839 --> 00:27:49.720 So these hacks are very very serious ransomwhere as serious there are all these different 394 00:27:49.720 --> 00:27:53.079 threads, and you guys are taking a pretty clever approach, it seems, 395 00:27:53.079 --> 00:28:00.359 to protecting that critical information which is on the mainframe right absolutely, from crypting 396 00:28:00.400 --> 00:28:03.640 it at rest to making sure and transit it's encrypted, but also going beyond 397 00:28:03.799 --> 00:28:07.440 and making sure, as we were saying, that dynamic way in which you 398 00:28:07.480 --> 00:28:11.839 access information, this particular user can see that this particular user see this other 399 00:28:11.880 --> 00:28:15.400 thing, including things that protect information and pi on the fly. And what's 400 00:28:15.400 --> 00:28:21.640 also interesting is we also do that with unstructured data as well. So it's 401 00:28:22.519 --> 00:28:26.319 when you kind of look at a system that already knows your data dictionary and 402 00:28:26.359 --> 00:28:27.880 you can see everything, Oh, you know this is a so security number. 403 00:28:27.960 --> 00:28:32.319 You know this is that. That's one problem to solve, but it's 404 00:28:32.359 --> 00:28:36.359 another when you have unstructured information in a reponsitory. You need to kind of 405 00:28:36.400 --> 00:28:40.599 call through that, make some policies and then dynamically apply them. Those are 406 00:28:40.640 --> 00:28:42.880 some of the things that we already have in market, and those are continued 407 00:28:42.920 --> 00:28:48.279 investments we're making. So it's a pretty exciting area and it really helps make 408 00:28:48.319 --> 00:28:55.119 sure that an individual application development team or an individual user or department doesn't have 409 00:28:55.160 --> 00:28:57.480 to really take then the burden of figuring this all out that can actually be 410 00:28:57.519 --> 00:29:03.720 done at a corporate policy And that's why customers really use our technologies is as 411 00:29:03.759 --> 00:29:08.079 it really helps them really I use data more as a service internally and not 412 00:29:08.200 --> 00:29:11.599 be afraid to use it some of the times. What we've also seen is 413 00:29:11.799 --> 00:29:17.200 customers have lots of useful information, but they know it has some I'm not 414 00:29:17.240 --> 00:29:21.279 sure what it has. This is the problem, So there's this kind of 415 00:29:21.319 --> 00:29:23.920 trepidation. So it kind of comes back to those themes earlier about knowing what 416 00:29:25.079 --> 00:29:26.720 you can, you know where the information is, what those flows are, 417 00:29:26.799 --> 00:29:30.400 and then ultimately be able to put it into action even with unstructured information, 418 00:29:30.519 --> 00:29:34.359 which is again an area where we've been investing for years on. Pretty exciting. 419 00:29:34.559 --> 00:29:37.440 Well, that is really cool, and you know, one thing that 420 00:29:37.480 --> 00:29:41.880 gets me very excited about the modern information landscape is what you just mentioned that 421 00:29:41.960 --> 00:29:45.880 you can do this policy management now fifteen years ago, even ten years ago, 422 00:29:47.000 --> 00:29:51.720 and someone saving five years ago policy was just something written in a document 423 00:29:51.759 --> 00:29:53.359 that set on a shelf and you had to hope that the employee you read 424 00:29:53.400 --> 00:29:56.400 it and knew it and adhered to it because there was very little bit you 425 00:29:56.440 --> 00:30:00.240 could do in terms of dynamic policy enforcement. But now we can do that 426 00:30:00.240 --> 00:30:07.160 stuff. There are machine readable policies that can be implemented and protect dynamically against 427 00:30:07.240 --> 00:30:11.440 all sorts of things, even accidents, even someone accidentally accessing information they weren't 428 00:30:11.480 --> 00:30:15.799 supposed to. It protects us in all these different ways. That is a 429 00:30:15.000 --> 00:30:18.880 much different world than we grew up with. Like in the early days of 430 00:30:18.880 --> 00:30:22.880 the mainframe, you didn't have these sort of dynamic policies that you could define, 431 00:30:22.440 --> 00:30:26.119 manage, execute and in monitor over time. Now we do and that 432 00:30:26.240 --> 00:30:30.599 is a very very big deal, right don Yeah, absolutely, And it 433 00:30:32.200 --> 00:30:36.960 ties back to both protecting that critical information you have on the mainframe, but 434 00:30:37.039 --> 00:30:41.119 also it extends beyond. So the way we've we've implemented this technology is it 435 00:30:41.160 --> 00:30:45.480 works with your critical systems, with your mainframe, and that's the bread and 436 00:30:45.519 --> 00:30:48.559 butter of what we focused on. But we also made adapters that top into 437 00:30:48.640 --> 00:30:53.079 other systems, including other unstructured systems. So for instance, whether it be 438 00:30:53.279 --> 00:30:59.400 maybe a SharePoint where pository or where information might exist in other repositories in your 439 00:30:59.480 --> 00:31:03.000 enterprise, and we even have an ability for you to be able to customize 440 00:31:03.000 --> 00:31:07.480 it. Because what we've also run into is we have large enterprises that they 441 00:31:07.519 --> 00:31:11.880 have some custom content system that was created years ago. And speaking of afraid 442 00:31:11.920 --> 00:31:15.599 of change, is someone's like, Bob built the system, Bob isn't hereing 443 00:31:15.640 --> 00:31:18.599 anymore, and you know what do we do now? Right, So what 444 00:31:18.599 --> 00:31:22.480 we've been able to do is kind of put abstractions in front that allow you 445 00:31:22.519 --> 00:31:27.400 to get access to that information. But that policy, unified policy layer applies 446 00:31:27.440 --> 00:31:30.480 to whether it to be the mainframe or beyond, and so that can be 447 00:31:30.640 --> 00:31:37.480 really powerful because again what can happen is end users or developers just need one 448 00:31:37.519 --> 00:31:41.200 API or one user experience to access this information and so they don't have to 449 00:31:41.200 --> 00:31:45.680 worry about, you know, where it's coming from or what format it's in. 450 00:31:45.880 --> 00:31:48.960 It's automatically protected from them on the fly. And so that's some of 451 00:31:48.960 --> 00:31:52.119 the things that our customers have really enjoyed. Yeah, that's a really good 452 00:31:52.160 --> 00:31:55.240 point. You mentioned this a couple of times, so I want to explain 453 00:31:55.279 --> 00:32:00.160 to the audience why why you're doing that. The ability to make change in 454 00:32:00.200 --> 00:32:02.599 your organization requires lots of different stuff, right. You need people who develop, 455 00:32:02.680 --> 00:32:06.920 you need people who understand the systems, You need to know what you 456 00:32:06.920 --> 00:32:09.240 want to change, get that from the business, etc. But the speed 457 00:32:09.279 --> 00:32:15.079 at which you can try things is really really important for reasons of morale, 458 00:32:15.160 --> 00:32:17.119 for reasons of business acumen, and so on and so forth, for reasons 459 00:32:17.119 --> 00:32:21.359 of survival in some cases. And so what had to happen in the old 460 00:32:21.440 --> 00:32:24.640 days is there was a very long, what they call waterfall process that had 461 00:32:24.680 --> 00:32:28.599 to be followed to change anything. And we want to wasting lots and lots 462 00:32:28.599 --> 00:32:32.599 of time because people weren't communicating properly and it's just not a very efficient way 463 00:32:32.599 --> 00:32:37.160 to do. But now we can have this much more agile approach. And 464 00:32:37.319 --> 00:32:42.880 what Doug is describing here is empowering your application development team to really focus on 465 00:32:42.960 --> 00:32:46.119 business problems and not worry about the security, the compliance, all these other 466 00:32:46.200 --> 00:32:52.319 characteristics that need to be handled that can be handled through the platform or through 467 00:32:52.359 --> 00:32:55.680 some of these policies, and that liberates the developers to try new things. 468 00:32:55.680 --> 00:33:00.599 It liberates the business to talk to the developers to try to things. That 469 00:33:00.759 --> 00:33:06.680 is absolutely crucial for digital transformation, right absolutely, And what we've also seen 470 00:33:06.960 --> 00:33:12.640 is this becomes even more important when the stakes are very high. Consider for 471 00:33:12.680 --> 00:33:17.079 instance, emergent acquisition type scenario. Sometimes whether or not to do the deal 472 00:33:17.359 --> 00:33:22.319 is all dependent on how fast can we integrate our organizations. And you know, 473 00:33:22.920 --> 00:33:29.519 many organizations have these critical systems where they have years and years of data 474 00:33:29.519 --> 00:33:31.720 in the mainframe and they need to integrate it into the rest of their ecosystem 475 00:33:31.799 --> 00:33:37.599 again to use that word. And so if you're trying to bring developers together 476 00:33:37.640 --> 00:33:42.440 to bring a unified experience to customers, the ability to do this very quickly 477 00:33:43.079 --> 00:33:46.400 can be the difference of Wow, that acquisition was really worth it. Our 478 00:33:46.440 --> 00:33:51.920 customers really see us as one company. Now we're able to integrate business processes 479 00:33:51.920 --> 00:33:55.000 and be fluid or sorry, boss, it's going to be another six or 480 00:33:55.039 --> 00:33:59.799 twelve months until that's finished, which well, isn't a really a fun conversation 481 00:34:00.160 --> 00:34:02.519 right now. You have to be able to move quickly, and that's really 482 00:34:02.559 --> 00:34:07.720 what we're talking about, is empowering your team to be able to make changes. 483 00:34:07.759 --> 00:34:09.239 First of all, understand what's there. I mean, that's one of 484 00:34:09.239 --> 00:34:13.519 the biggest challenges I think, And we want to talk to about AI and 485 00:34:13.559 --> 00:34:16.039 how AI can come into this equation here, and the bottom line is you 486 00:34:16.159 --> 00:34:20.159 better be careful. I mean, one of the downsides, at least in 487 00:34:20.199 --> 00:34:23.840 the early days of chat GPT, is that if you type in some of 488 00:34:23.880 --> 00:34:28.679 your proprietary code or some of your proprietary recipes or whatever that's going into the 489 00:34:28.719 --> 00:34:31.039 machine and it could become out some other side, to some other place and 490 00:34:31.079 --> 00:34:35.320 you won't even know. There's gonna be some really interesting conversations that be had 491 00:34:35.360 --> 00:34:37.599 around that in the near term. But the point is you have to know 492 00:34:37.679 --> 00:34:40.960 what's out there, know the steady state, and then be able to do 493 00:34:42.000 --> 00:34:45.280 that impact analysis you've talked about to try new things. You try it and 494 00:34:45.320 --> 00:34:47.199 fail, fail fast forward is what they say, right, That's what you've 495 00:34:47.199 --> 00:34:51.320 got to do to be able to solve these real mission critical problems is have 496 00:34:51.480 --> 00:34:54.440 the agility and have the confidence to be able to make some change and know 497 00:34:54.840 --> 00:34:59.559 that you can either undo it or at least fix what you've created right a 498 00:35:00.079 --> 00:35:04.039 lutely. And you started off this segment by kind of talking about the cloud 499 00:35:04.119 --> 00:35:07.679 and Kubernetes and different technologies around that. And what we've also seen is a 500 00:35:07.719 --> 00:35:15.519 lot of customers have really seen this kind of rise to microservice style architectures where 501 00:35:15.840 --> 00:35:19.679 it's very works very well with kubernets because it allows you to manage these different 502 00:35:19.719 --> 00:35:22.400 pods that you were saying, and you might have dozens, hundreds, even 503 00:35:22.480 --> 00:35:27.599 thousands of them depending on what happens, and what we've seen with a lot 504 00:35:27.599 --> 00:35:31.000 of customers is they really like these style architectures where you have these little piece 505 00:35:31.039 --> 00:35:35.880 parts like you were saying. Part of it is because it allows you architectural 506 00:35:35.920 --> 00:35:38.679 purity of scalability and such, and that's a good thing. But the real 507 00:35:38.760 --> 00:35:43.880 reason is it allows the business to scale at a people level. And so 508 00:35:43.920 --> 00:35:51.320 it allows different developers to work independently of each other and build new business logic, 509 00:35:51.360 --> 00:35:54.280 create new business functions, and ultimately let the business go faster. But 510 00:35:54.360 --> 00:35:59.119 then you have two problems or now you've introduced a new problem by doing that 511 00:35:59.599 --> 00:36:05.079 isn't any cases. What happens is you proliferate the access of data. So 512 00:36:05.119 --> 00:36:08.239 in many cases a development team will create their own database or their own store 513 00:36:08.280 --> 00:36:13.760 of where they're putting even unstructured data. And now what can happen is in 514 00:36:13.840 --> 00:36:17.400 from critical information can get out of sync with other systems through these kind of 515 00:36:17.480 --> 00:36:23.079 architectures, and so to remediate this kind of problem, we've looked at technologies 516 00:36:23.119 --> 00:36:28.320 that allow you to look at data quality across those landscapes, and so particularly 517 00:36:28.719 --> 00:36:31.400 considering, for instance, the mainframe is maybe a little bit the source of 518 00:36:31.480 --> 00:36:36.519 truth for many applications. It allows you to look into what's on the mainframe 519 00:36:36.719 --> 00:36:39.760 and then what's in other systems and does everything match up? And this is 520 00:36:39.920 --> 00:36:45.320 very important in like, for instance, reconciliation or financial use cases. And 521 00:36:45.480 --> 00:36:51.800 what we have is customers have used our technologies to make sure everything matches in 522 00:36:51.920 --> 00:36:57.440 real time as they're creating these micro services, and so it really allows this 523 00:36:57.559 --> 00:37:00.000 teams to kind of move very quickly. But at the same time, the 524 00:37:00.159 --> 00:37:07.559 quality teams and the infrastructure teams that want to make sure both quality is intact 525 00:37:07.639 --> 00:37:14.039 but also compliance is intact, really can enforce these rules. So it kind 526 00:37:14.039 --> 00:37:16.519 of gives you the best of both worlds through that approach. M Yeah, 527 00:37:16.559 --> 00:37:20.880 and what Doug is talking about here is the fact that these larger organizations, 528 00:37:20.880 --> 00:37:23.079 you're going to have whole separate teams that are all important. They have to 529 00:37:23.119 --> 00:37:27.440 work together, but you can't have everyone in the same room all the time, 530 00:37:27.519 --> 00:37:30.840 so you have to come up with policies procedures, technology stacks to enable 531 00:37:30.960 --> 00:37:35.960 this kind of collaboration. And then to his point, you want to make 532 00:37:36.000 --> 00:37:38.039 sure that you're getting the latest data, the freshest data, the data that 533 00:37:38.119 --> 00:37:44.400 is accurate because things change, and so that requires What really amounts to an 534 00:37:44.440 --> 00:37:47.639 information architecture is what it boils down to and kind of understanding where and when 535 00:37:47.719 --> 00:37:51.880 you can build in your checks and balances, where and when you can kind 536 00:37:51.920 --> 00:37:54.519 of bring in that last security check, if you will, to make sure 537 00:37:54.559 --> 00:37:57.880 it is secure, a last little bit, but don't touch out. That 538 00:37:57.920 --> 00:38:02.639 will be right back. You are listening to inside analysis. Do you own 539 00:38:02.639 --> 00:38:07.119 an annuity either fixed rate, index or variable? Are you paying high fees 540 00:38:07.119 --> 00:38:12.079 and getting low returns? If so, Annuity General would like you to have 541 00:38:12.159 --> 00:38:15.960 this free book to learn the pitfalls and mistakes of buying an annuity. The 542 00:38:15.000 --> 00:38:20.400 Annuity Dues and Don'ts for Baby Boomers contains the little known truths about annuities, 543 00:38:20.719 --> 00:38:23.800 like how to help reduce your fees and increase retirement income. And it's free, 544 00:38:23.960 --> 00:38:28.679 that's right free. As a bonus, we'll also throw in a free 545 00:38:28.679 --> 00:38:34.079 annuity rate report just for calling. We researched over one thousand annuities and summarized 546 00:38:34.199 --> 00:38:37.880 rates and benefits from financially strong insurers. You get annuity dues and don'ts for 547 00:38:37.920 --> 00:38:44.119 baby boomers and the Annuity Rate Report, both absolutely free for calling Annuity General 548 00:38:44.159 --> 00:38:49.159 Today. Hurry supplies are limited. Call now eight hundred two four or five 549 00:38:49.440 --> 00:38:53.719 one six nine seven, eight hundred two four five one six nine seven, 550 00:38:54.000 --> 00:39:00.480 eight hundred two four or five one six nine seven. That's eight hundred four 551 00:39:00.559 --> 00:39:05.639 or five sixteen ninety seven. Do you own a timeshare? We'll face the 552 00:39:05.679 --> 00:39:08.840 facts. You made a mistake, You made a bad purchase. A timeshare 553 00:39:08.960 --> 00:39:14.440 is not an investment. It's a money pit that continues forever. If you 554 00:39:14.559 --> 00:39:17.360 use your time share, that's great. But if you don't and you want 555 00:39:17.360 --> 00:39:22.519 illegally get out of your contract, call my friends right now at the Timeshare 556 00:39:22.559 --> 00:39:28.119 Exit Hotline. They're an experienced team of lawyers who help good people like you 557 00:39:28.480 --> 00:39:31.719 get out of a time share contract that they just don't want. Don't throw 558 00:39:31.719 --> 00:39:36.320 away your money on maintenance fees, use it for things you really want. 559 00:39:36.559 --> 00:39:40.679 We can help you end your time share contract and stop the money drain immediately. 560 00:39:40.960 --> 00:39:45.159 If you are ready to move on with your time share, call our 561 00:39:45.239 --> 00:39:50.159 team right now. Cancel your time share now with a free call eight hundred 562 00:39:50.159 --> 00:39:54.800 two nine zero six seven O five eight hundred two ninezero six seven O five 563 00:39:55.079 --> 00:40:00.880 eight hundred two nine zero six seven O five. That's eight hundred two nine 564 00:40:00.960 --> 00:40:06.960 zero sixty seven O five. Do you own an annuity either fixed, rate, 565 00:40:07.079 --> 00:40:09.719 indexed or variable? Are you paying high fees and getting low returns? 566 00:40:10.079 --> 00:40:14.559 If so, Annuity General would like you to have this free book to learn 567 00:40:14.599 --> 00:40:17.639 the pitfalls and mistakes if buying an annuity. The Annuity Dues and Don'ts for 568 00:40:17.679 --> 00:40:22.880 Baby Boomers contains the little known truths about annuities, like how to help reduce 569 00:40:22.880 --> 00:40:27.440 your fees and increase retirement income. And it's free. That's right free. 570 00:40:27.760 --> 00:40:30.039 As a bonus, we'll also throw in a free Annuity rate Report just for 571 00:40:30.119 --> 00:40:36.719 calling. We researched over one thousand annuities and summarized rates and benefits from financially 572 00:40:36.760 --> 00:40:40.280 strong insurers. You get Annuity Dues and Don'ts for Baby Boomers and the Annuity 573 00:40:40.400 --> 00:40:45.679 Rate Report, both absolutely free for calling Annuity General Today. Hurry supplies are 574 00:40:45.679 --> 00:40:52.360 limited. Call now eight hundred four nine five three six five two eight hundred 575 00:40:52.400 --> 00:40:58.119 four nine five three six five two eight hundred four nine five three six five 576 00:40:58.239 --> 00:41:02.920 two. That's eight hundred four nine five thirty six fifty two. Attention seniors 577 00:41:02.920 --> 00:41:07.719 on Medicare and Medicaid or receiving extra help for your prescription drugs. We have 578 00:41:07.840 --> 00:41:13.440 great news. You can change or enroll into a Medicare plan every three months 579 00:41:13.519 --> 00:41:16.639 if you qualify all from the comfort and safety of your own home over the 580 00:41:16.719 --> 00:41:21.159 phone. No one even needs to come to your home, and in minutes 581 00:41:21.239 --> 00:41:24.599 we'll tell you all about some additional new Medicare benefits for you, like dental, 582 00:41:24.840 --> 00:41:30.400 vision, hearing, transportation and more. Call us we'll explain all your 583 00:41:30.400 --> 00:41:34.559 new Medicare benefits. Premiums are as low as zero dollars per month, even 584 00:41:34.599 --> 00:41:37.119 if you're not paying anything for your coverage. Now you need to call our 585 00:41:37.199 --> 00:41:42.280 license st agents to review your plan. There are zero cost plans available in 586 00:41:42.320 --> 00:41:45.800 some areas. Don't wait till next year get all the Medicare benefits you deserve. 587 00:41:46.039 --> 00:41:50.880 Call a license st agent today. Eight hundred two five three eight one 588 00:41:50.960 --> 00:41:54.559 two six, eight hundred two five three eight one two six. That's eight 589 00:41:54.639 --> 00:42:05.800 hundred two five three eighty one twenty six paid for by sixty five plus Medicare 590 00:42:06.280 --> 00:42:17.119 Welcome back to Inside Analysis. Here's your host, Eric Kabanat All right, 591 00:42:17.239 --> 00:42:22.119 folks, back here on Inside Analysis, talking with Doug Johnson of Rocket Software, 592 00:42:22.480 --> 00:42:28.639 all about modernizing the mainframe and really being able to weave it into this 593 00:42:28.719 --> 00:42:32.159 new, very dynamic world of cloud computing. We've talked about the analytics that 594 00:42:32.199 --> 00:42:36.280 you can do. We've talked about data provisioning, which is really important. 595 00:42:36.800 --> 00:42:40.440 There's some other risk management aspects to this as well. I spent a past 596 00:42:40.519 --> 00:42:46.559 life moderating webinars for the Global Association of Risk Professionals or GARP dot org. 597 00:42:46.599 --> 00:42:52.079 I joke that they are the de facto Illuminati, because they're chief risk officers 598 00:42:52.079 --> 00:42:54.119 at central banks all around the world. Of course, there are some banking 599 00:42:54.119 --> 00:42:59.880 issues these days. Silicon Valley Bank collapsed. First Republic just collapse over the 600 00:43:00.039 --> 00:43:04.800 weekend. These are very strange times. A lot of people don't understand that 601 00:43:05.320 --> 00:43:08.239 all it takes is a psychological event for there to be some run on the 602 00:43:08.239 --> 00:43:13.000 bank, and that's what happened with SBB, that's apparently what's happening with First 603 00:43:13.000 --> 00:43:16.320 Republic. People just pulling out massive amounts of money and that creates systemic risk. 604 00:43:16.679 --> 00:43:21.599 So being able to kind of understand that, and especially in this global 605 00:43:21.840 --> 00:43:24.440 world where you've got to all these different countries involved, you have all these 606 00:43:24.440 --> 00:43:29.239 different central banks. Of course it's all electronic now, so you can access 607 00:43:29.239 --> 00:43:30.280 and move money around. A lot of stuff has changed. I mean, 608 00:43:30.320 --> 00:43:35.559 the fintech innovation has been absolutely stupendous, and a lot of these banks all 609 00:43:35.599 --> 00:43:37.960 have mainframes. They've had mainframes for years doing all this stuff. So I'm 610 00:43:38.000 --> 00:43:44.000 curious to know your approach to the risk management side. I can kind of 611 00:43:44.039 --> 00:43:49.360 guess just to being able to look into unstructured data, identify entities, you 612 00:43:49.400 --> 00:43:52.199 know, basically provide a risk score of some contin You tell us a bit 613 00:43:52.199 --> 00:43:55.760 about what you do in the risk management space. Yeah, well, there's 614 00:43:55.800 --> 00:44:00.480 no shortage of opportunities, but also there's with all opportunities, there's also risks 615 00:44:00.480 --> 00:44:04.440 that go along with it. And a lot of the organizations that we serve 616 00:44:04.920 --> 00:44:10.840 are very highly regulated too, and so they have certain regulation regulatory obligations that 617 00:44:10.880 --> 00:44:16.280 they have around how long they have to keep information when it's notifications, if 618 00:44:16.280 --> 00:44:21.679 a customer asks for certain information that it can be expunged in a timely manner, 619 00:44:21.960 --> 00:44:25.960 and many other things that happen from a process and procedure perspective, and 620 00:44:27.000 --> 00:44:30.960 so what happens in that domain is being able to make sure you keep information 621 00:44:30.239 --> 00:44:34.599 just as long as you need it, but no longer. And that sounds 622 00:44:34.599 --> 00:44:37.480 like it's such an easy thing to say, but it's remarkably hard to do, 623 00:44:37.639 --> 00:44:44.159 especially when different classes of information require kind of different retention policies. In 624 00:44:44.199 --> 00:44:49.599 with that, and then in addition to that, though certainly retention management is 625 00:44:49.679 --> 00:44:53.199 a key thing that our customers think about, but also as they look to 626 00:44:53.360 --> 00:44:58.920 change business processes use information in different parts of the organization, they need to 627 00:44:58.920 --> 00:45:02.039 make sure they have custom over that information wherever it might go. And so 628 00:45:02.039 --> 00:45:06.480 what we're seeing more and more as customers are saying, hey, can you 629 00:45:06.519 --> 00:45:12.440 make this data available to maybe some business partner or perhaps some internal process, 630 00:45:12.840 --> 00:45:15.000 but we need to make sure we have the controls that can see the flow 631 00:45:15.039 --> 00:45:19.719 of that information throughout a cycle, who touched it, when, if it 632 00:45:19.760 --> 00:45:22.639 integrated with another system, Do we have an actual audit trail of the data 633 00:45:22.639 --> 00:45:28.840 and time and the proofpoint that some interaction actually happened. And so that closed 634 00:45:28.880 --> 00:45:35.960 loop reporting on that auditing piece is just super important to making sure that organizations 635 00:45:35.960 --> 00:45:39.400 are compliant so that when a regulator comes to you and says, you know, 636 00:45:39.519 --> 00:45:44.039 hey, can you show me that paperwork that shows X or Y. 637 00:45:44.480 --> 00:45:47.239 The answer is, of course, it's right here. Yeah, that's a 638 00:45:47.280 --> 00:45:51.679 big deal. And you know, when regulators come calling, you want to 639 00:45:51.719 --> 00:45:53.760 have several things in place. It seems to me you want to have your 640 00:45:53.760 --> 00:45:57.280 plan, you want to have your architecture documents, and then you want to 641 00:45:57.280 --> 00:45:59.440 be able to show their receipts. Right. You want to say, well, 642 00:45:59.440 --> 00:46:04.199 here's our for how we detect breaches, here's our plan for when we've 643 00:46:04.199 --> 00:46:07.000 detected a breach, what we do, Here's what happened in this particular instance, 644 00:46:07.199 --> 00:46:09.719 X y Z process is fired off. And then you want to be 645 00:46:09.760 --> 00:46:15.079 able to show them in the production system. And here's where rubber meets road. 646 00:46:15.400 --> 00:46:16.639 And if you could do all that, you're going to get a lot 647 00:46:16.679 --> 00:46:20.360 of leeway. I mean, and you know there's always going to be pressure 648 00:46:20.400 --> 00:46:24.440 to improve security, to improve governance, to improve auditibility, etc. But 649 00:46:24.480 --> 00:46:29.000 as long as you have your plan and you're acting on your plan, and 650 00:46:29.039 --> 00:46:31.039 you're listening to the regulators and what they ask you for nine times at a 651 00:46:31.079 --> 00:46:34.880 tenant that you're going to be just fine. What do you think well, 652 00:46:34.920 --> 00:46:38.119 absolutely, and what's really important is the full life cycle managed around this. 653 00:46:38.280 --> 00:46:43.239 So everything from like we were talking about the very beginning, we were saying, 654 00:46:43.280 --> 00:46:45.599 hey, this idea of can you actually go look at the code and 655 00:46:45.639 --> 00:46:51.440 see where data is moving throughout your organization, that's actually proving that the systems 656 00:46:51.760 --> 00:46:54.000 literally are doing what they say they do all the way to what happens at 657 00:46:54.079 --> 00:46:59.239 runtime, where hey, this transaction happened on this date, and here's the 658 00:46:59.280 --> 00:47:04.599 proofpoint that happened, and it's logged in our mutable storage mechanism. To be 659 00:47:04.639 --> 00:47:08.079 able to have that proofpoint across the data but also the processes, the people, 660 00:47:08.119 --> 00:47:13.280 and the systems that it interacted with, that's what's really required by many 661 00:47:13.320 --> 00:47:16.840 of these highly regulated organizations, and so they look at technologies like ours to 662 00:47:16.920 --> 00:47:21.159 help. Yeah, that's very interesting that you mentioned this a couple of times. 663 00:47:21.159 --> 00:47:25.360 So with your software, you're able to look at the code that is 664 00:47:25.440 --> 00:47:30.880 instanting it in a particular environment and basically process it. And do you actually 665 00:47:31.039 --> 00:47:35.159 run the code or is it that you just know what it's going to do 666 00:47:35.519 --> 00:47:37.920 based upon the functions that you see. And therefore you can look to the 667 00:47:38.000 --> 00:47:40.840 log file and kind of triangulate things. Can you explain that a bit more? 668 00:47:42.199 --> 00:47:45.920 Yeah, absolutely, And so what we have or we have these scanners 669 00:47:45.960 --> 00:47:50.840 that look at the code that developers have actually in their system, you know, 670 00:47:50.840 --> 00:47:54.800 in the version control systems, and the actual code itself, and from 671 00:47:54.840 --> 00:48:00.840 that it determined what kind of data is interacted with that one system. And 672 00:48:00.920 --> 00:48:02.960 that can be on the mainframe for instance, as we said with like Cobalt. 673 00:48:04.440 --> 00:48:07.000 But what's also interesting is you use then you throughout your organization, you 674 00:48:07.039 --> 00:48:10.519 go to other systems and run that same procedure. It might be a C 675 00:48:10.679 --> 00:48:15.760 plus plus or Java or something other system. And then the interesting thing is 676 00:48:15.760 --> 00:48:20.119 it looks at that parses that code itself and those entities that are involved, 677 00:48:20.400 --> 00:48:24.280 and it sees the connection where one system calls another and it stitches it together. 678 00:48:24.360 --> 00:48:28.199 So you can see not just the data and one system and the data 679 00:48:28.199 --> 00:48:31.480 and other systems, but you can follow that lineage, that flow of information 680 00:48:31.599 --> 00:48:37.079 from one place to another. And again it becomes an auditor's dream because when 681 00:48:37.079 --> 00:48:40.559 you go when that compliance team says, hey, we want to prove that 682 00:48:40.639 --> 00:48:46.039 something happened, you can actually from a system's perspective prove or where data is 683 00:48:46.079 --> 00:48:50.519 touching another system and as we said, if you want to make business change. 684 00:48:50.880 --> 00:48:53.760 Again, the compliance officer loves it as well, because you can confidently 685 00:48:53.800 --> 00:48:59.400 make changes and because you can see the entire data landscape, so it becomes 686 00:48:59.440 --> 00:49:05.320 a very powerful visualization around the entire organization. Yeah, that's really cool stuff. 687 00:49:05.360 --> 00:49:09.239 And obviously you can understand why banks want that level of certainty because you're 688 00:49:09.280 --> 00:49:14.400 moving money around, right, the classic two face commit Right, it's okay, 689 00:49:14.480 --> 00:49:15.400 I'm sending money over here. Yes, I've sent it. Did you 690 00:49:15.440 --> 00:49:17.320 get the money back? Yes, we got the money back. Okay, 691 00:49:17.320 --> 00:49:21.039 good, Like, now we know we can move on and do something else. 692 00:49:21.119 --> 00:49:23.760 And wow, you think about the innovation and fintech and how much easier 693 00:49:23.800 --> 00:49:28.239 it is to move money around in just seconds and moments. And that took 694 00:49:28.280 --> 00:49:32.239 a tremendous amount of back end work to be able to engage these different systems 695 00:49:32.280 --> 00:49:37.360 to move the money, to categorize, to categorize it essentially do all that 696 00:49:37.400 --> 00:49:39.360 stuff. That's a big deal, right, and so Rocket Software, I'm 697 00:49:39.400 --> 00:49:45.159 guessing, is a significant player in that whole evolution, right, Yes, 698 00:49:45.239 --> 00:49:49.760 And with that, what we've also seen is the ability to scale in terms 699 00:49:49.800 --> 00:49:54.760 of looking at these systems automatically and really scaling, compliance and other things is 700 00:49:54.800 --> 00:49:59.800 super important to be able to get that visibility. But also we found that 701 00:50:00.280 --> 00:50:04.679 scaling from a people perspective is super important. And what do we mean by 702 00:50:04.679 --> 00:50:07.440 that, Well, if you have that data and it's available to two or 703 00:50:07.480 --> 00:50:13.119 three magicians at your organization that know how to run the magic incantations to tell 704 00:50:13.159 --> 00:50:16.400 you what those connections are, that that isn't as effective as what if the 705 00:50:16.519 --> 00:50:21.320 user experience could be more of a consumer type experience where anyone could go in 706 00:50:21.679 --> 00:50:25.360 see those connections. Obviously anyone who's authorized obviously right, but you know at 707 00:50:25.360 --> 00:50:30.000 the departmental level, or if you're looking to make a business change as a 708 00:50:30.000 --> 00:50:34.280 as an enterprise architect at an organization, you don't have to be that magician 709 00:50:34.400 --> 00:50:37.199 to know all of the details of the tool. It really allows you to 710 00:50:37.239 --> 00:50:43.760 see those connections that otherwise you would just spend mountains and mountains of time in 711 00:50:43.920 --> 00:50:49.320 meetings and manual work to try to get achieve the same thing. Yeah, 712 00:50:49.360 --> 00:50:52.079 and not even get to the answer. Perhaps, I mean it sounds a 713 00:50:52.079 --> 00:50:54.079 lot like process mining. Maybe we can talk about that in the in the 714 00:50:54.119 --> 00:50:59.400 podcast bonus segment. But that ability to get down to the code level as 715 00:50:59.400 --> 00:51:02.000 you suggest to run time and be able to do the playback say okay, 716 00:51:02.000 --> 00:51:06.480 well here's what happened. This system connected to that system. This data came 717 00:51:06.519 --> 00:51:08.559 across the trans and went over here. We can verify that it landed, 718 00:51:08.599 --> 00:51:15.000 etc. That is tremendously useful information for any kind of trouble shooting, for 719 00:51:15.079 --> 00:51:17.239 any kind of improvements, you know, because then you can look at that 720 00:51:17.360 --> 00:51:21.000 a certain skill and say, okay, we need to change x, Y 721 00:51:21.079 --> 00:51:23.719 and z to be able to supercharge this one process. You know, you 722 00:51:23.760 --> 00:51:29.079 went into the classic impedance mismatch with some of these systems right where it's like 723 00:51:29.639 --> 00:51:30.800 this one is spending at a certain rate, that one is spending at a 724 00:51:30.840 --> 00:51:34.840 slower rate. How do you how do you get those two to jibe? 725 00:51:35.119 --> 00:51:37.920 Basically, that's not a small problem, right. You want to be able 726 00:51:37.960 --> 00:51:40.480 to see all that, And your point is that you're able to see into 727 00:51:40.480 --> 00:51:45.239 the mainframe and see into these other systems and give a very clear cut view 728 00:51:45.679 --> 00:51:49.360 of which code is enacting at one point in time, which data goes in 729 00:51:49.400 --> 00:51:52.920 there. That is the audit trail, right, that is and really allows 730 00:51:52.960 --> 00:52:00.480 you to make change with confidence. Many organizations they have the meetings, they 731 00:52:00.519 --> 00:52:05.239 have the budget, they have the desire to change, but they really don't 732 00:52:05.280 --> 00:52:09.199 know in the end, is the thing I've created my VISEO diagram that we 733 00:52:09.239 --> 00:52:14.119 had meetings about, is that really how my organization operates? And you just 734 00:52:14.159 --> 00:52:16.800 don't have that confidence, and so we help you kind of buyback that confidence 735 00:52:16.800 --> 00:52:22.159 in those change both from a regulation perspective, but then also just making sure 736 00:52:22.159 --> 00:52:25.440 you're effective your project's going to be successful. Yeah, this is wonderful stuff, 737 00:52:25.639 --> 00:52:30.199 folks. Look these these folks up online Rocket Software at Doug Johnson has 738 00:52:30.239 --> 00:52:34.400 been our guest today. We are booking the second half of the year right 739 00:52:34.400 --> 00:52:36.039 now, So if you want to be on the show, send me an 740 00:52:36.079 --> 00:52:39.199 email. Info at inside Analysis dot com that comes straight to yours truly or 741 00:52:39.239 --> 00:52:44.039 info at dm radio dot biz. We're trying to understand what's happening in the 742 00:52:44.039 --> 00:52:46.360 information economy. We'll talk to you next time. Folks, you've been listening 743 00:52:46.440 --> 00:53:01.719 to Inside Analysis Express one o six point five FEV talk radio station leur KCAA, 744 00:53:01.840 --> 00:53:07.960 the station that leaves no listener behind Express one oh six point five FM. 745 00:53:13.559 --> 00:53:16.679 This segment sponsored by the generous support of the dream Team looking for the 746 00:53:16.760 --> 00:53:22.719 Keys to something bigger and better downsizing or relocating to the perfect spot. Oscar 747 00:53:22.840 --> 00:53:28.760 Ramirez from Century twenty one Lowislower real Estate and Matt Flores from Secure Choice Lending 748 00:53:28.840 --> 00:53:32.320 are here to help you sell or buy with their trusted and experienced knowledge and 749 00:53:32.440 --> 00:53:37.679 advice. People are calling Oscar and Matt at nine five one seventy five, 750 00:53:37.800 --> 00:53:40.559 one three two four nine. That's nine five, one seven five, one 751 00:53:40.719 --> 00:53:45.599 thirty two forty nine real estate and loan advisors. Oscar and Matt can give 752 00:53:45.639 --> 00:53:50.719 you a no cost consultation. You don't have to buy anything. Matt and 753 00:53:50.760 --> 00:53:53.960 Oscar can help you figure your way through the complicated real estate market. Email 754 00:53:54.000 --> 00:54:00.480 Oscar at Loislower dot com or on Instagram at Oscar Ramiras Garcia and Matt Flores 755 00:54:00.800 --> 00:54:07.119 at Secure Choice Lending dot Com. Don't let today's real estate pitfalls stop you 756 00:54:07.199 --> 00:54:12.400 from dreaming. Make your new home dreams come true. Dri number zero two 757 00:54:12.559 --> 00:54:21.079 zero seven zero three four four Zehabla espanol tihebo Te Club's original pure Poudi Arco 758 00:54:21.199 --> 00:54:23.719 superta comes from the only tree in the world that fungus does not grow on. 759 00:54:24.039 --> 00:54:29.079 As a result, it naturally has antifungal, anti infection, anti viral 760 00:54:29.119 --> 00:54:34.119 antibacterial, anti inflammation, and anti parasite properties, so that tea is great 761 00:54:34.119 --> 00:54:37.760 for healthy people because it helps build the immune system, and it can truly 762 00:54:37.800 --> 00:54:42.320 be miraculous for someone fighting a potentially life threatening disease due to an infection, 763 00:54:42.400 --> 00:54:46.280 diabetes, or cancer. The tea is also organic and naturally caffeine free. 764 00:54:46.320 --> 00:54:51.079 A one pound package if T is forty nine ninety five which includes shipping. 765 00:54:51.280 --> 00:54:54.840 To order, please visit tehebot club dot com. Tihibo is spelled T like 766 00:54:55.000 --> 00:54:59.920 tom, A H, E, B like boy. Oh, then can 767 00:55:00.039 --> 00:55:02.880 tinue with the word T and then the word club. The complete website is 768 00:55:02.880 --> 00:55:07.159 to eubot club dot com or call us at eight one eight six one zero 769 00:55:07.280 --> 00:55:13.039 eight zero eight eight Monday through Saturday nine am to five pm California time. 770 00:55:13.199 --> 00:55:16.719 That's eight one eight six one zero eight zero eight eight to ebot club dot 771 00:55:16.760 --> 00:55:24.559 com. With sixty years of fascinating facts. This is the man from yesterday 772 00:55:25.239 --> 00:55:30.920 and back in time we go to this time in nineteen seventy. NBCTV is 773 00:55:30.960 --> 00:55:35.400 giving Don Knots his own variety show, so it'll begin this fall on NBC. 774 00:55:35.920 --> 00:55:39.719 Don Knots is best known as Deputy Barney Fife on Andy Griffith, Well, 775 00:55:40.000 --> 00:55:45.000 boy, just once, I'd like to have them sideburns come out even 776 00:55:45.119 --> 00:55:47.280 one inch from the lobe. What's the matter with you on them? Sideburns 777 00:55:47.320 --> 00:55:51.840 is short? Well, maybe that's because one of your loaves is longer than 778 00:55:51.880 --> 00:55:54.199 he. And back in time we go to this time. In nineteen ninety 779 00:55:54.199 --> 00:55:58.960 seven, after twenty years, Joe London says that she will step down as 780 00:55:59.039 --> 00:56:04.079 co host of ab CTVS Good Morning America in September. Joan London will remain 781 00:56:04.119 --> 00:56:07.159 with ABCTV to work on some primetime projects. Now you will continue to see 782 00:56:07.239 --> 00:56:09.960 Joan on television. But I want to make the argument here that in this 783 00:56:10.159 --> 00:56:14.599 job for the past seventeen years, she has been one of the most significant 784 00:56:14.639 --> 00:56:19.559 figures in women's changing role on television and thus in society. And from this 785 00:56:19.639 --> 00:56:23.440 time. In nineteen fifty seven, Ricky Nelson of the ABC TV Azzie and 786 00:56:23.599 --> 00:56:29.440 Harriet Show scores his first hit record with m Walking. It all began when 787 00:56:29.559 --> 00:56:34.800 Rickey Nelson imitated Elvis on a recent Azzie and Harriet TV show, what you 788 00:56:34.880 --> 00:56:38.559 gonna do when well run straight, You're gonna run away and time I'm gonna 789 00:56:38.599 --> 00:56:45.559 run right by your son be burn to Bland. I'm walk with Moore at 790 00:56:45.639 --> 00:56:52.239 Man from yesterday dot Com. It's time to make the Tri City Center in 791 00:56:52.360 --> 00:56:58.039 Redlands a regular part of your weekly shopping experience. Tri's City is home to 792 00:56:58.119 --> 00:57:01.639 a wide assortment of quality business is, including the all new Ocean Aquatics. 793 00:57:02.840 --> 00:57:07.960 Check out the variety of exotic tropical fish along with fish food accessories and tanks 794 00:57:07.960 --> 00:57:13.039 of all shapes and sizes. The Tri City Center is located just off of 795 00:57:13.079 --> 00:57:16.960 Alabama and the Tennessee exits tin Redlands. Visit the Tri City Center today and 796 00:57:17.039 --> 00:57:22.440 find out why it's called the Mall with a Heart. CACAA Radio has openings 797 00:57:22.440 --> 00:57:25.519 for one hour talk shows. If you want to host a radio show, 798 00:57:25.679 --> 00:57:30.400 now is the time make CACAA your flagship station. Our rates are affordable and 799 00:57:30.440 --> 00:57:36.119 our services are second to nine. We broadcast to a population of five million 800 00:57:36.159 --> 00:57:39.679 people plus. We stream and podcast on all major online audio and video systems. 801 00:57:39.800 --> 00:57:45.800 If you've been thinking about broadcasting a weekly radio program on real radio plus 802 00:57:45.840 --> 00:57:51.079 the internet, contact our CEO at two eight one five nine nine eight hundred 803 00:57:51.280 --> 00:57:54.519 two eight one five ninety eight hundred. You could skype your show from your 804 00:57:54.519 --> 00:58:00.320 home to our Redlands, California studio where our live producers and engineers are ready 805 00:58:00.320 --> 00:58:05.000 to work with you personally. A radio program on Caseyaa is the perfect work 806 00:58:05.079 --> 00:58:09.360 from home avocation in these stressful times. Just HIKSEAA radio dot com into your 807 00:58:09.400 --> 00:58:14.199 browser to learn more about hosting a show on the best station in the nation, 808 00:58:14.440 --> 00:58:17.760 or call our CEO for details. Two eight one five nine nine ninety 809 00:58:17.800 --> 00:58:23.239 eight hundred. It's that time of year again, No, not the holidays. 810 00:58:23.559 --> 00:58:29.119 Medicare open enrollment and if you have questions about Medicare, you should talk 811 00:58:29.159 --> 00:58:32.760 to the local experts. Paul Barretchen Associate. Paul and his agents are certified 812 00:58:32.840 --> 00:58:37.320 with plans that are accepted by most of the medical groups in our area. 813 00:58:37.519 --> 00:58:40.960 Call nine O nine seven nine three O three eight five. Their services are 814 00:58:40.960 --> 00:58:45.599 free and after forty one years in the business, their agents are trained to 815 00:58:45.639 --> 00:58:51.800 help you pick the plan that's right for you. Hi, I'm food critic 816 00:58:51.800 --> 00:58:55.440 Gallenborgan, and I'm excited to tell you about Rage Shanghai Bistro, located next 817 00:58:55.480 --> 00:59:01.199 to Redlands DMB on Laconia in Redlands, Ray Shanghai Bistro offers the largest, 818 00:59:01.280 --> 00:59:07.199 him most delicious array of traditional and original Chinese dishes available in Ulum Empire. 819 00:59:08.079 --> 00:59:13.159 Some of my favorite dishes are the house spain hot stickers, the crisp pork 820 00:59:13.239 --> 00:59:17.360 sparrabs with garlic, their unique spicy lamb with bamboo, the sweet and tangy 821 00:59:17.559 --> 00:59:22.960 deep fried orange peel beef, and the savory basil spicy shrimp, plus lots 822 00:59:22.960 --> 00:59:27.960 of vegetarian dishes. Whether you dine in, pick up the food, or 823 00:59:28.000 --> 00:59:30.920 have them cater your next party or special occasions, you will see why ray 824 00:59:31.119 --> 00:59:37.000 spelled r Ui of postrophes. Shanghai Bistro is truly the best Chinese restaurant in 825 00:59:37.079 --> 00:59:43.280 the Ulum Empire. Their website is raised Shanghai Bistro dot net. That's raised 826 00:59:43.480 --> 00:59:50.239 Shanghai Bistro dot net. Ruis Shanghai Bistro dot net. Happy eating, you 827 00:59:50.360 --> 00:59:58.519 won't be disappointed. Kilistina KCAA Lomolinda at one six point five FM, K 828 00:59:58.679 --> 01:00:04.840 two ninety three CF You know Valley, NBC News Radio. I'm Chris Garagio. 829 01:00:04.880 --> 01:00:07.440 Authorities in Texas are still searching for a motive in Saturday's mass shooting and 830 01:00:07.480 --> 01:00:08.559 a shopping mall near down