PegaWorld iNspire 2024: Rapid Delivery and Immediate Business Value – National Bank of Canada goes live with Pega Smart Investigate on the Cloud

All right. Welcome, everyone. Thank you for coming. Pretty good turnout, considering we're up against the Innovation Pavilion and AI. So thank you for for being here. Uh, we have a bit of a hybrid today. We are our partner. Our very good partner, Corey Sherry Santiago could not be here today from NBC, but he was very kind. To submit to a video recording.

So we recorded him in Montreal. And he's going to bring to you today all the comments he would have brought to you live. I do have these two fine gentlemen with me on the stage. I'm Jason Morrison, by the way. I'm your moderator. I was with Citi 20 years Pega just about seven and been with us for about a year and a half now. These these are our experts. Go ahead. Andy.

Good morning. Um, Andy Elliott, VP of product strategy at Ivantis. And before that I was 26 years at Pega including smart investigate product manager for many years. Hi. Good morning everyone. I'm Sam Pereira, a VP technology for evangelist. I've been with Pega ecosystem for 18 plus years. I lead the Pega delivery practice for North America region. Uh, I've been part of, uh, a couple of large, uh, smart investigate implementations at National Bank.

I played the role of a principal system architect for the project. Start to finish. Excellent. Okay. Thanks, guys. Now we're going to go to Cory. Hi. Good morning. My name is Cory.

I'm live from Montreal in Canada. Um, unfortunately, I wasn't able to be present today at PegaWorld, but I'm confident that with the story, I'll be sharing you today and my recent journey and experience with Pega Smart Investigate along with my partners at Advancis, we've prepared you an excellent hour of enriching content, and we hope that you all leave with insightful takeaways. A little bit more about me. So I'm the product owner of Pega Smart Investigate at National Bank. National Bank is one of the largest Canadian institutions amongst the top six in Canada. I've been in the banking industry for the last 15 years and specifically in the payments for the last four, but with the initiative and the project that we will be sharing you today. I've been leading a project team for the last two years in the implementation of Smart investigate across the organization. Now back to you, Jason. Thanks, Corey.

Okay. So we're going to turn to Andy. Now who's going to tell us a little bit about the future of the payments industry, as well as some of the challenges that are holding us back today. All right. So quickly, before we start talking about the future, let's take a step back in time and talk a little bit about the past. So by a show of hands quick, if you could put your hands up, if you've been in and around the payments industry for at least ten years. All right. Most of the people in the room. Keep your hands up if you've been in the payments industry for 20 years.

Anyone do? 30? Well done. I can put my hand up for 30 as well. We won't go beyond 30. Um. I started my payments career with Bank of America in London in 1985, and my first job was in the wire room. My job was taking the yellow look like ticker tape. You know, it has holes punched into the ticker tape.

Basically, it was tested telex information, and I used to take the ticker tape off of the telex machine, validate the test key, and then feed it into the payment system. I guess you could call me the human API. Um, so over the last 40 years, there has certainly been some level of change in payments, but I at least personally, I don't think there's been the level of change that we're seeing right now. It feels like in the last 5 or 6 years things have gone crazy. Certainly during my career in payments, there has been some level of change. Tested telex, I'm pleased to say, went away. I think, um, empty 100 became 100 threes. Every year Swift comes out with their standards release, and there's maybe a new code, perhaps in a field or a new a new field to go into an empty one or something like that. So there has been some level of change, but it's gone crazy.

As you all know, over the last 5 or 6 years. I'm not ashamed to say that I'm approaching the end of my career. There's many people in this, in this room who have got many years ahead of you in the payments business, and I think you're going to be very, very, very busy. So let's talk about some of the bullet points on this slide. Um, let's talk about the proliferation of new payment rails and real time payments to start with. So the first version of this slide had an alphabet of acronyms up on the slide. And for my own sanity, I removed those. Um, let's talk about payment rails, and in particular the payment rails that impact banks. To start with, uh, most most countries have been working on their payments infrastructure for many years now.

Over the last 5 or 6 years, there's been a number of new real time payment implementations. The UK has got faster payments. I think Hong Kong's got faster payments. In Singapore, it's called fast. There's a theme here. Um, Australia breaks that theme, calls it NPP. But just about every country is working on or has implemented a real time payment, um, payment rule. Outside of the traditional banking payment rails, there are others that impact consumers like everybody in this room. Let's just talk about some of those.

So cryptocurrency payments, um, you know, the ability to make Bitcoin payments peer to peer without intermediaries, um, contactless payments. Um, everybody these days has a mobile phone with an NFC chip in it. Uh, that combined with the fact that the chip in the in the credit card, of course, allows you to go present your mobile phone to a, a terminal and pay for something. And that's given rise to services like Apple Pay, Google Pay, Samsung Pay, that kind of thing. QR code payments, uh, perhaps a little less well known, but they're out there, trust me. You know, this is the ability for a merchant to present a QR code at the point of payment for you to scan it and pay with your with your phone. Anyone who goes to Walmart every now and again, you know you and has a Walmart app on your phone. You get to check out the self-service. You scan all your items you want to pay.

There's a QR code that comes up, you can scan it and pay that way as well, and it charges the credit card linked to your Walmart account. And then lastly, um, everybody uses payment applications on their phone, whether it's PayPal or Venmo or Zelle. And there's also a growing number of these for international payments as well wise, um, Xoom, Remitly and so on. So lots of options when it comes to making payments. You know, the days are gone when banks had, uh, 100% market share when it comes to wire transfers and that kind of thing and all of that level of changes. Before you even mentioned the words ISO 20,022, Let's talk a little bit about the frequency of change. So there are many drivers behind the sort of the rapid pace of change. None of these are probably a surprise to anyone in this room. Increased competition, ongoing innovation brought about by new technologies, services, business strategies and so on.

Ongoing regulation. That's not going away anytime soon. Um, customer expectations and preferences. We have a lot of highly educated, uh, demanding consumers in the world who know what they want. And organizations and banks and fintechs are evolving to meet those needs as well. So it's probably no surprise to hear that this isn't going to let up anytime soon. Um, it's important that the organizations in this room and generally in this, in this um, conference, remain agile and adaptive to the emerging payments technologies of the future. The other bullet point I want to mention quickly on here is transparency, which is a topic that's close to my heart. Um, so as the person at Elevance is responsible for our payment, our product strategy.

I am pleased to announce that we are launching a new product here at PegaWorld. It's called the Advanced Payments Platform, or EPP for short, and it's designed to leverage the latest Swift capabilities to improve the transparency associated with cross-border payments. And another plug, if you don't mind, if you want to come see more about that Booth 16 in the Innovation Hub. Um, I don't know whether any of you have a need to send money abroad from time to time, but if you do, it's far from transparent. When you log in to a mobile phone or online banking and you want to send money abroad, generally speaking, you won't get told when it's going to get there, or at least the bank will say 5 to 10 days or something silly like that. You won't know how much the beneficiary is going to get. You don't know how many fees and charges you're going to get deducted. Um, so the FSB actually published an article at the end of last year that said less than 50% of payments have the level of transparency that consumers demand today. Next slide please, Jason.

So innovation is good, change is good. But the path and the journey towards some of those new payment rails we talked about earlier is not going to be full of unicorns and rainbows, shall we say. There's going to be challenges along the way. Um, I'm not going to talk about all of these bullet points, but let's pick pick out a few, uh, data quality. So, uh, another show of hands, please. Who's involved in an ISO 2002 two project that involves some kind of data transformation? Mm. To MT MT to. Mm.

Yeah, a few. Right. So I grew up with MT, I know them inside out. I'm learning mm messages and I understand the intent of mm messages. They're more verbose. They're content rich. The intent is that you can put lots of information in there. And if a beneficiary wants to get 100 invoice numbers associated with that payment, you can probably do that. And it will eliminate some of the unable to apply investigations and so on down the road.

But how is that data going to get into that verbose Swift message. Mm. Message. Someone can type it all by hand. Certainly the source systems that are, generally speaking, the ones that generate the messages, they don't contain that level of information. All right. So either you're taking what is essentially empty style data and putting it into larger mm fields, or if you're going the other way around, it's even worse if you're taking an mm message and you're trying to accommodate some legacy empty only systems internally, you're taking those more verbose messages and you're truncating them to put 70 characters into a 35 character field, that kind of thing. So there's going to be ongoing challenges associated with data quality for for some time. I was actually in Canada with a bank last week, uh, kicking off a project.

And they had they have just started accepting inbound mm packs 008 and pack 009, and their SDP rates have gone down, not up. Right. So I think that's going to be a problem for the banks for the foreseeable future. The other topic I want to talk about on this slide here is is exceptions. Um, which, of course, we're here to talk about. Smile. Investigate. So that goes hand in hand. And ISO 2002 two is designed in part to reduce exceptions by making the payments more verbose, including more information.

Hopefully the beneficiary knows what the payments for. They don't have to ask, unable to apply inquiries. And then, of course, you've got things like GPI being run by Swift. Um, that brings transparency to payments that didn't exist before the the availability. The GPI tracker is great. It should eliminate a whole bunch of Benny claims non receipt investigations because you can simply log in and see the status of that payment. But right now about 80% adoption of GPI. So not every bank is is is contributing to the tracker. And there are still payment infrastructures in the world.

In the United States we've got uh fedwire, for example, that that um, break the payment chain as far as the Swift track is concerned. So you don't see that end to end picture. All right. So while I think over time ISO 2002 two and GPI will help from an exception standpoint in the near term. Um, those investigations are not going away. Thanks, Jason. Next slide. Excellent. So yeah.

So thank you Andy. That was a good industry view. Let's hear from Corey again. He'll tell us a little bit about some of the challenges at NBC specifically, and some of the factors that were motivating their need to transform and modernize. Well, some of the challenges that we were facing at National Bank, I think will resonate with a lot of the audience today, because in the payment space, we are experiencing a shift. There's a modernization, there's a lot of changes that are occurring. When we started preparing for ISO and looking at that, the impacts within the organization, whether it be from a from a payment processing perspective or even from a investigation resolution perspective, we had to ensure that within our operations and the organization, we had the technology to be able to support this new, you know, method of communicating with other financial institutions, but also being able to go through the transition phase of dealing with the old type of messaging and the new one. So knowing that that transition period was going to be taking place on several years, it was absolutely essential to find and identify what would be the solution so that we can ensure that we meet the requirements that are going to be set forward by the industry, but also knowing that it's going to be a slow evolution and a progression towards it. Some of the main challenges were that was being isalready, being ensured that we had our ecosystems ready, that we had our operations center ready, and at the same time, it was an opportunity to look at our process as a whole and looking at how we can improve the client experience and improve the employee experience throughout.

So those were the main challenges that we we saw back in 2021. And of course, since that moment of time, we've had the occasion to Don, you know, forward with the deployment and really begun living through this experience and this change and really adopting all these new practices. Excellent. Okay. So we've heard a lot about the challenges. Now let's talk about perhaps the solution. So I get I get to introduce smart investigate. So um, I uh I moved to the US in 2006 with Pega, and my first job at Pega was as the, um, was the product manager to to bring smart investigate to to market. So I do know it quite well, as does the rest of the advances.

We've worked on many of these projects, but by way of introduction, Smart Investigate is the industry leading solution used by banks to handle, um, high value investigations, cross-border payments, uh, investigations and so on. Um, it's deployed at about 25 of the largest banks in the world, um, used predominantly by back office people. Of course, the investigators to research and respond to inquiries and resolve the investigations. Um, and the value proposition I think is pretty clear. It's, uh, it takes a process that is highly manual without without smart investigate, um, and it streamlines it significantly puts in place business processes and business rules that become, um, become the basis of, of of levels of automation that wasn't otherwise possible. And generally speaking, it drives somewhere between a 30 and a 50% productivity improvement over a pre smart investigate implementation. So this is the basis of the solution that Corey's been talking about. And we'll be talking about as part of the rest of the implementation. Awesome.

Thanks again. Okay. So we're going to go back to Corey in a minute and hear about MBC. But before we do that, Sam, can you kind of run us through the experience and some of the achievements of the team, please? Sure. Tourism. When we started the project, we had two main objectives. The banks or legacy investigation platform was nearing its end of life, and the payments ecosystem at the bank was going through a major transformation to ISO 20,022. National Bank made a bold decision to choose Pega Cloud for their investigation platform implementation, becoming the first ever Smart investigate client to be live on with Pega Cloud.

Though we had experience in implementing multiple larger smart investigate solutions, the cloud implementation threw us some unique challenges, especially, uh, connecting uh, banks, uh uh, system of records. The messaging channels, uh, to the cloud, to a public cloud environment was was one of them. I want to give you a shout out to Corey and the National Bank, infrastructure team for, uh, for their proactive preparation and expertise to remove those impediments. And also a big thank you for Pega, uh, Cloud team, as well as the client team who supported us throughout our journey. So our implementation strategy started with a three day, uh, gap analysis workshop where we, uh, focused on finalizing the, uh, scope for MVP one, as well as the configuration changes that are required for MVP one. Uh, for MVP one, we connected the transaction system of record, uh, the customer information system of record, as well as inbound and outbound, uh, empty and messaging channels. The, uh, the MVP one implementation, uh, took around three months for its feature implementations and an additional month, uh, for connecting the upstream and downstream applications. This might be one of the fastest Smart investigate implementation that was ever done, if not the fastest. Uh, with the implementation, uh National Bank started seeing, uh, remarkable efficiency gains, uh, closer to 35%, uh, increase in the efficiencies with the investigation teams as well as, uh, a 50% reduction on their investigation processing time.

It was a fantastic experience working with National Bank. Uh, we are continuing to build on our success by implementing more straight through processing to further enhance the efficiencies as well as, uh, adopting new mm messaging standards. Great job. Good job to the team. Okay, let's hear from Cory in his own words about, uh, he's going to talk about the evaluation process, why NBC chose C, and then some of the benefits to today. So when we began looking at our alternatives and looking at solutions, we definitely wanted to choose and look at a at a vendor that definitely had a product that meet all of our business requirements, but also knew that there was a dedication to adopting all the new ISO regulations. And this was definitely one of our key triggering points because we were under a tight deadline. As the payment payment world is evolving and is quickly adapting, we quickly noticed that the reason for the leading industry in terms of their solution was the dedication to continuing to evolve the product, but also continuously adopting the Swift standards. So when we began in looking at solutions and alternatives, it was important for us to find a leader in the market, specifically the payment investigation space with Smart Investigate, because we all know today that, you know, the the biggest pain point that clients are experiencing is the investigation part.

So that's what we can consider. Maybe the unhappy path. Right. So being able to address this unhappy path and make the journey a lot more fruitful and much more enriching for our clients is our ultimate goal. So with Pega Smart Investigate, we were definitely able to streamline our processes. We were able to automate a lot of these different tasks and essentially allow our sectors and our our teams to benefit from these, uh, features and optimizations. Since the implementation of Pega Smart investigate, um, it has been a tremendous experience for all of our users and also our clients. We saw significant improvements in our processes and the efficiency with the fact that we're able to automate certain activities with the fact that there's a lot of user friendly features. You know, the ease of using the solution as well contributes to the overall experience of our employees.

So we definitely saw a shift and a significant improvement in our processing of investigations across the organization. Excellent. Okay. So we've heard about the industry. We've heard about why Pega why. See let's hear a little bit about why Sam's going to walk us through the next couple of slides. This is a global, global elite Pega partner providing its services across the globe via Pega. Go to partner for smart app implementation, which includes smart investigate and Smart Dispute advances. Our deep knowledge and expertise, uh, set us apart.

Uh, our founder CEO, Aaron, was once a Pega, uh, served as the product architect for Smart Investigate as well as Andy Elliot, who's here with me, was a long time product owner for smart investigator. Uh, there are many ways to implement a feature rich application like smart investigate, but advances. We bring the thought leadership that is required to build your solution, eliminating costly mistakes. This approach would ensure the application that you build would be easier to maintain, as well as flexible for future modernizations like this. Excellent. With our extensive knowledge advances, we have built, uh, accelerators and components that greatly reduces the implementation time as well as, uh, add value to the product. Smart Investigate Accelerator reduces the implementation time by 4 to 6 weeks. It generates the foundation application. Considering the all the line of businesses in scope as well as the majority of the configuration changes required for MCP one.

Additionally, we have also introduced Correspondence Accelerator, which helps the business users to create their own Swift are fed and email correspondences, so this reduces the need of having development team working on correspondences. Also these become these. These templates become promptly available in production. Uh we have also uh enhanced the email functionality that comes with smart investigate uh, to make it more like an outlook functionality by improving its, uh, user experience. Uh, service excellence is an API driven component that connects your, uh, front office customer service applications seamlessly to a back office smart application. Uh, Considering the chat and email channels. Um, as you all know, uh, one key factor of, uh, rapid software development is, uh, automated testing, uh, advances. We offer a testing tool called ETAs, which comes with a full fledged, uh, test suite for smart investigate. How do you do this?

We'll talk about implementation best practices. We'll take it up as the Q okay. Perfect. All right. So we're going to go back to Cory. He's going to close for us. And then we're right on time for about 15 minutes of Q&A. And make sure you hit Sam about implementation best practices please. So the reason why we chose Ivantis was um, there was a demonstrated knowledge and strong expertise about the product.

And having known that one of the lead architects and developers of the solution is now the founder of Ivantis definitely contributed into knowing that we were entering in a partnership that we would be, uh, in good hands, knowing that they had the expertise, knowing that they would allow us to achieve the objectives that we have as an organization. And one of the reasons we went forward working with Ivantis was that genuine connection in terms of the human aspect, but also our cultures within the organization. It was definitely an important factor, uh, working with Ivantis, knowing that our cultures and our vision of things are definitely aligned. Our experience with Ivantis has been phenomenal. I mean, honestly, it has been a very truthful partnership, and I think we can collectively say that we we we mutually felt that throughout the entire journey that we've been living together. So when it came to come in delivering the project, we had that agility. We had that human aspect. We definitely had that collaboration and we truly felt that partnership throughout and having been able to deploy Pega smart investigate on the cloud, probably in a record time frame. Yes, we faced hurdles.

We had to overcome obstacles, but there was never a moment that we felt that these obstacles were showstoppers. So again, thank you and looking forward to to working on other initiatives together that could collectively, you know, build a better future for for the payment space. All right. And thanks again to Cory for the partnership during the implementation, as well as allowing himself to be recorded. So we can go into Q&A now. Uh, anything you like. Maybe Finbarr wants to start with a question about out of the box. I have a question about. That.

So. So the question was how close to out of the box was the implementation and. The implementation for National Bank was very much closer to the out of the box. So we generates the the implementation layer using our accelerator. So it was uh, the initially went live with uh the correspondence functionality for payments line of business. So they had one line of business that went live. So that was like the, uh, workflows for all investigations where they were all out of the box. They had the first level of, uh, automation, which is the, uh, auto acknowledgment that was built. And we didn't we built a couple of other automation for Bcns and, uh, you, uh, unable to apply.

So those were, like, out of the box. One extended off course. Awesome. Any other questions? Arun? At the edge of your seat. There's always this question about what does it take? All of. You have done so.

Thanks. Um, as far as, um, there are three of the most important things about, uh, including the spending time up front in the design and the planning, because it's all about the infrastructure. It's easy to go to cloud, but you're basically connecting to the infrastructure from, uh, from a Pega Cloud, you know, connecting to your endpoint. So I promise I'll keep my mouth shut. But since you guys are all most of you have worked with me, you know how difficult it is to keep my mouth shut. I felt for you when Alan said he was going to remove whiteboards. I thought you might be crying. That's the other thing. So I'm sorry.

We might have missed the beginning. Are you talking about where the fundamental differences between a cloud and an on prem are? Oh, that is right. It's. So, uh, even from the infrastructure perspective. Right. Um, cloud works on a completely a different app server. A completely a different app stack, right. So the database server is different from your, you know, from from what you currently have from an on prem database, but also from a bank's perspective.

You should also look from overall payment modernization journey because you need to be connecting via APIs, uh, to the bank, which means the bank basically needs to provide those microservices that can actually be consumed, um, from an application that's actually sitting in Pega Cloud. Of course, there are security protocols involved. Of course. Uh, those those are going to be followed. But again, uh, just from an overall architecture perspective, That's that's completely different because traditionally banks would end up connecting to the to a database. Right. So transaction servers typically is a database right. All of that is is on prem. It's easy to access.

But now they've got to think about how do they go about deploying it. How. Um, especially from a connectivity perspective. So the code code that is available in Smart investigate, um, if you are changing the database, of course, you need to convert from your oracle to say, you know, your plsql, right. But, um, those are the changes that you have to do. But at the same time, make sure that we are able to provide or build, um, rest based services out of the Smart Investor app. Wrap. All of that that can actually be consumed from is typically how you want to think about it. Excellent.

Great. Yeah, I think it's always interesting with this, even though it's a out of the box and a common process. The the two gating factors we often seen are the quality of the discovery in the beginning, and then lining up the right teams for the march of the implementation. If you think back even to what Alan talked about today, with the future of software development, it's not going to be about the code anymore, right? It's really about capturing and expressing those requirements, uh, you know, deeply in the proper way. So you see that manifest itself, I think, in C and that's I think why Corey talked about and Sam as well, the, the strength of the collaboration. And that was a enabler of the implementation. Please know about that. You start with a process of design and the National Bank of Canada up to you with like a process design.

Um, or did you, uh, come together and design the process together? Did they start with something? Did you start with something? Yeah. So basically, um, so we would, uh, as part of our gap analysis workshop that we do, uh, so we they would have they had their business processes all laid out. So as part of the analysis, we'll walk through the, uh, out of the box, uh, implementation of Smart, investigate all the processes, the functionalities available, how what are the, uh, the additional automations that you could use. So we will identify those gaps as part of the workshop. And we would start creating a backlog for the MEP one using that alongside with what they have provided. So the Sprint zero approach.

Uh, yes. It's an Sprint zero. The difference between. Did you identify like through that process, additional layers of of automation opportunities. And then I want to ask like, were you able to get to a certain level of straight through processing, through all of that. Straight through processing. Was the MEP uh 1.5? We started with MEP one. It was mostly the out of the box automations which which yes, of course you would have straight through processing which comes with the auto acknowledgment feature that comes with the product and connecting the transaction system of records for that.

But additional automations that are on top of your different investigation types were built as part of this subsequent, uh, MVP. And so did I hear you. So you deployed out of the box and then you added the straight through processing action. Okay. Yeah. And to your question about the innovations, you know, we we try to capture the as is and then as part of the gap analysis when we're showing, you know, Pega see we we show it and talk about it with all the innovations and try to sort of seed the, the minds in the room with, with some innovations we might put in later pieces of the roadmap. So usually it's a, you know, phase three maybe or release three that we're. But the general approach to implement smart investigate is rather more prescriptive than perhaps a traditional Pega, Infinity, Platform based implementation, where it's more discovery, it's more what would you like the system to do for you? The approach, the right approach, we think, to implementing Smart investigate is a this is what it does.

Let's talk about how we're going to change that function to meet your particular needs. Or if there's no changes required, that's great. So it's a more as I say, it's a more prescriptive led approach. And it's a best practice to challenge as well. What needs to be this way. Well why does it need to be that way? But is it just that it's always been that way or because that's not really a justification, right. So and again, that's another tenet is having the right executive sponsorship when one of those friction points comes up about what's needed and what's not needed. Right.

Take it. How long did this did the initial discovery phase to get to. The gap analysis itself was three days, and the Sprint zero also was for a week altogether. So gap analysis we take outside Sprint zero. So that's three days plus a week of Sprint zero. But I would mention that National Bank was well prepared with the with their requirements and also the infrastructure. That's where you spend most of the time. Uh, they got their security clearances for getting those data into public cloud. And all those APIs were ready by then.

So that was one of the, uh, the success factors from that. And I think they had a good handle on the process. Sometimes we we receive a, you know, a user manual. And then when we get on site, what they're doing is nothing, nothing like what's in the manual. So I think they had a really good handle on the processes that were going on. And, and they had some innovations in mind. Right. They were, they were kind of hamstrung or, uh, you know, handcuffed in terms of what they could implement, but they had a good idea of where they wanted to go, which was great. Right?

Please. So I. Just bought an old SEC Cloud. Um, so I was a bit shocked to see like, how we did integrations with them, but then he just explained that all the APIs were, you know, what the reason. So you mean to say like the overall preparation for the interfaces to be ready? Yeah. I mean, what we have. Um. So how do you go from that is things that.

Yeah. MQ is supported in Cloud. We went with MQ for integration. To be honest. It's the same same same same application. So it was MQ. We didn't convert it. We didn't have to convert that into an API. So for empty and both message types we chose MQ.

Yeah. There were some challenges because uh, some uh issues with the security uh, setup at the back. So we yeah, we, we that was one of the delays that happened. But, uh, the bank's infrastructure team was capable to handle it like they were, uh, they had the expertise with them. So, yeah, it was a good experience working with them. You guys started with me excited about that? Correct. It was a it was a fresh implementation. So.

It was the transaction history. MQ as well I'm sorry. The transaction history query was that MQ as well. No that's that's on rest API. They had a Rest API before the transaction system of record that you connect to. So that's all any smart investigate application would connect to transaction system of record. Most of the on prem implementations it would be a JDBC call that you would make. But in Pega Cloud just of course JDBC would support it. But not none of the banks would need a public cloud infrastructure to connect directly to JDBC connection to a database.

Uh, within the bank's premises. So they had a API layer which was readily built. Fortunately for us. I think that. Yeah. Um, and we also did a data migration that is already running. Yeah. Were there lessons learned from the data migration? Is there a room?

Well, I think the data migration, we were both Pega Cloud, so we were looking at smaller companies like. AWS AWS migration tool. So we went from Oracle to Postgres. Um, I think the biggest learning, but that's maybe a logical one. You have to test this with production data. So we had a Cloud production life and and we just started testing, um, the migration between on prem and cloud. We did it like 4 or 5 times to just also get the performance, to be able to do that in, in a reasonable time. I think they took in total 25 hours in the in the implementation weekend and about 70 hours, uh, before the weekend in preparations. Yeah.

But did you work your old history on the old system? Work it to result, or did you move that over? Um, we basically. Well, we had some issues with archiving. It was a total different method, but we just removed that and then. Yeah. So what I was surprised with we didn't have to clean up a lot. That is what I know from other data migrations that you get all kinds of old cases that just don't are not complete, so will not be accepted or not work anymore in your new environment. But that worked.

Yeah. That's interesting. Excellent. Yeah, that's it's interesting. It almost varies client by client, whether we work the history down or whether we move it over. There's a, you know, an effort involved with moving it over. So I guess it's really the size. And if you're up against an end of life or some sort of system retirement, that's going to motivate you to move it. Okay.

Ten after any anything else from anybody. We have plenty of time. Please. Was it kind of the, you know, Benny unable to apply kind of investigations, or did you know you could have investigations stemming from like, fraud screening, um, sanction screening, things like that. Did it cover that whole gamut or was it more focused in on like the maybe the more external type of investigations? So for the MEP one, it was the the out of the box investigation types that's available. But they didn't want to go live with the sanctions, uh, case type specifically because the process was a little different. So they wanted to introduce a compliance case type for that. But other than that, it was all the, uh, the standard investigation types that comes with smart investigations.

Focused on external users. So Swift in from a correspondent bank, create the case Swift out to the correspondent bank. That was the predominant use case. So did you say there was a compliance element that you. You had a compliance because there's another investigation type called compliance. But Smart investigate has another additional two investigators are case types called sanctions RFI so that follows a different process than the regular one. So they wanted to kind of like remove them from the MEP one. But we introduced that back in MPP two. So I guess it's not it's not necessarily outbound sanctions.

It's requests for information from another. Right. And I suppose that's what I was kind of thinking. Yeah. You know we've got we haven't got enough information. You need to go out for that RFI kind of process. There. Is that module okay. So yeah.

And that was a second MVP you said correct okay. Gotcha okay. Thank you. Okay. If nothing else then thank you for your time. Appreciate it. You're welcome to come find any of us during the event here. And Corey offered if any of you have questions for him, just let us know and we'll hook you two up. So thanks again.

Appreciate your time. Thank you.