 So, I think the best would be that we move on with the next presentation, which is on user testing, because some of your questions that are ticking in, I'm sure Bobby and Bamini will answer those in a minute. So just, you know, hold on. I know you're anxious, hold on. It will be coming. So, Bobby, I want to hand over to you and I want to thank Flora. And I hope Flora stays with us. And then we want to hand over to Bobby first and then Bamini for the next presentation on user testing. So, Bobby, over to you. Hi, everyone. My name is Bobby Bashford. I'm a lead on this work stream of user testing and migration for the ECMS. And thank you very much, everyone, for participating. We have quite a lot of information for you in the next two sets of slides. First of all, Bamini will go through the user testing and then Anaisa will go through the migration. And these are really the important points. We are, you know, as George said, we are in our community testing now. We are trying to open up as much of the functionality as we can for you. And that is what we will go through now in these slides. So first, if we look at the planning slide, you can see here, Flora already went through it. We can look at it in a little bit of depth. If you see, we are in the community testing phase 2C. You can see here that CLM and T2S are connected to ECMS in our pre-production environment, the environment that the counterparties are testing in. What's very important is coming up is that we will, at the end of January, we will open up further functionality to you. Bamini is going to go through it piece by piece. The important point here is that today we are still working on how much of the functionality we can open and that this will be made clear in the testing conditions document. We are going to speak to you about documentation for the testing. Your Bible, if you like, is the testing conditions document. And this is the one that you will need to. It's on the ECB site. It's constantly being updated. And this is the one that you will need to look at. So Bamini will go through what is currently can be tested, what is going to be opened up at the end of January, what is going to be opened up at the end of February. She will go through the restrictions. Note this is only on a high level. You will need to go back onto the ECB site and look in the constantly updated testing conditions document to see if there are any restrictions to the functionality that we will open up. We're looking to open up as much as we can. The 4CBR are working very hard delivering fixes to our environment. So this is the current planning. Another very important point is the non-repudiation of origin. The Assertia Go Sign Desktop, Bamini will speak to you about that. It's very important that you have installed the correct version before we open up this functionality to you. We are currently testing it internally. And we will let you know about the date that we plan to open it up. It will be inserted in the testing conditions document. Your NCB, your National Central Bank, your National Service Desk will also make you aware. NCB is your main point of contact at all times throughout this process. So these are the two in the plan. If you look, these are the two milestones, if you like, end of January and the February where we're going to open up further functionality. You can see in mid-April that we disconnect from CLM and T2S. This is because our T2S colleagues need to be able to test in a production-like manner for the June release. So during April and May, the T2S community and the T2 community are testing CLM and testing T2S in the manner in which it will be in June, which is not connected to the ECMS service. And for that reason, that's why we disconnect. And that is why we will reconnect then in June after the go live of the release 2024 in T2, after the go live of release 2024 in T2S. So then in June, we will reconnect. What you need to look at in June is a very important testing phase or testing activity, which is the business day testing. This is where we will run a live timing schedule. So it will be the same schedule as is run in production. As you know now in the test environment, we don't run the operational day or the business day in a production manner. We run it with a different, the end of day process takes place a little bit earlier in the day. This will not be the case during this business day testing. So please be aware that you will have production like conditions in terms of the schedule here during July and August. And this is a very important point. And then later, Anaisa will speak to you about the upcoming tests. These are very important, the migration tests. We have a pre-test. We have the migration weekend dress rehearsal where we carry out the activities of the weekend in the same manner as it will be carried out on the go live date. These are important tests for us. And Anaisa will explain why. But this is really what you need to know. Everything about the the upcoming functionality that we're going to open. I'll hand you over to Bamani now and she will go through it. Thank you, Bobby. Thank you. And good morning. So here, thanks. I think that was a good overview of all the testing phases on the community testing phase. So with that overview, I would actually go now to the next few slides here. We will discuss about in detail about the scope that is currently being open for testing and then the scope function of mind scope that would be opened in the future in the next couple of months for testing. Yeah. So with that one, then the first slide here, what you see here, this keeps an overview of the functionalities that have already been opened for testing. Yeah. So with that one, the first thing is on the reference data. So here you see the reference data, marketable assets, testing, and then the global credit and collateral positions, cash is collateral. And here, all these four domains have been opened fully. When then, when come to credit claims, we still, and the monetary policy operations, all the full scope is not yet opened for testing of the counterparties. Nevertheless, we have opened partially the domain, yeah, the credit claims where we have opened for registration and update functionality. And then for the monetary policy operations, the marginal ending on request and the automatic marginal ending, it's open for testing. So this is where we stand as of now. So regardless of what we communicate here, we always request you to discuss with your NCP counterparts and then check with them for the green light before you come in with the testing. Yeah. That's the main, another message that we would also like to pass here. So that's all I have to say here on the slide, okay? That's the one that we have opened. So now moving on to the next couple of months. So there, the first functionality, which we are planning to open soon, yeah, which will be next week already, that would be the corporate action testing. So here again, the scope, we would still open partially starting from the 29th of January, you will be able to start testing the corporate action functionality, but then partially, yeah. So here, this is what you see in the scope to the left-hand side of this slide. So you see the scope that's going to be opened as from 29th of January. So we opened the basic mandatory corporate action testing, which has been tested by the NCPs here in the internal environment. So and hence, if they are all successful, the NCP, you know, at your side will also give the green light for this testing scope, yeah. So when I go detailed into the scope, so first part, you see the events, five events, so the basic ones, so interest payments, redemption, partial redemption, early, yeah, early redemption, and things like this, so are going to be opened. And then with respect to the scenarios, again, we have given here the reception, so notification, basically, it's a corporate action notification announcement, corporate action advice, and then corporate action confirmation, yeah. So those three scenarios are what we have focused in the last couple of months on testing for the corporate action, and that's something that we would like to now also open to the community, okay. So this is the plan for the 29th of January. And when the remaining functional domain on the corporate action will be opened, so here this is currently planned to be opened on the 26th of February, that's next month, yeah. The testing is still ongoing here, so we wanted to stabilize it and then would like to open it to the community as from 29, 26th of February. Again, as I stated in the previous slide, so for all the domains, the details, the restrictions, if there is any, there are any open issues, known issues, all these information, they are there in the testing conditions document, yeah. And we also request advice you to allow us with your NCB counterpart to get the green light before you start the testing on this functional area, yeah. That's all I have to say on the corporate action, thank you. Then if we go to the next domain, which we are also critical functional domain, which we are also focusing now is the monetary policy operation testing. So here, as I said in the first slide on the user testing, so on the marginal ending on request and the automatic marginal ending, they are opened, yeah, ready. But then we still have open market operations that are to be opened for testing for the community. So here, what is the plan? Currently the testing is ongoing and the plan is to open the monetary policy, so open market operations testing, yeah, with the dental operations module. Yeah, this is planned to be from 20th of February 2024. That's again next month. And here again, I would like to mention that not all the open market operations are planned to be opened as from 20th of February. But the ones that we have successfully tested and it's quite stable, then those are all the operations that we will be opening to the community for the testing as from 20th of February. And the details of these operations that we will be opening, yeah, we will bring these information in the testing conditions document, yeah, like how we will, like how we set for the corporate action in the previous slide. Similarly, we will go into the details of the scope that's going to be open and from when you can test this and what you can test and what are all the restrictions, if there are limitations, all these information we will bring in the testing conditions document that's going to be, that's being published on a fortnightly basis, okay. So this is what on this slide. Okay, so now that we have focused on the corporate action, the monetary policy of patients, we still have other domains, yeah, sub-domains or domains, functional domains to be opened to the counterparties, to the community. So where do we stand there? So if you see here in this slide, so we still have marketable assets and the credit claims, a big portion of credit claim, it's still yet to come for testing for the community and then the tri-party agent functionality, pool position and projections and provision of reference data to the T2S and the TPA statements and reports, yeah. So those domains, functional domains are also currently being actively tested and the objective is also to open these domains, yeah, what I stated here up until statements and reports, so the plan is to open this as from 26th of February, 2024, yeah, of course, I repeat this again and again, so please wait also for the green light from your NCBs before you start the testing on these domains, okay. So that's the date or the plan for the domains, up until statements and reports for billing and then for the testing of the multiple distinguish names. So here the planning is still ongoing and we will come back to you through the testing conditions document, we will come back to you with the timeline on when the billing and the DNS, yeah, this functionality could be tested, okay. And then the last point, which was also mentioned by Poppy in the introduction, it's right for the UT's on the GSD, associate co-sign desktop. So here, yeah, we really advise the community to install the latest software, yeah, so this is a new version and then the client is basically available also for you to download and the link is also there in the testing relations document for you to download. So here we advise now the community to install this, yeah, new version and then the testing as such, the testing plan is to start this NRO, so non-repudiation of origin NRO, the testing is planned to be start from 18th of March, yeah, so 24. So this is the plan for the, you know, the front domains, the remaining domains and the dates, yeah, this is the plan too. This is the full, with this slide, we have covered all the functional domains and the plan of when this will be available for the counterparties testing. And here in this last slide on the UT, for the UT, so here we have given the current status of the different testing and the migration documents, yeah. So the documents that are published normally they are available in the SAP website under the link for professional use. So you can go in there and check for the latest published version. And then recently we've published also the info pack strategy to all these and then the user testing terms of reference or the pre-production environment to all these fundamental test cases, yeah. These documents were updated and then published recently and the testing conditions document as you know that this is a document that is constantly updated and published on a full likely basis in the ACB website. Clearly highlighting the limitations, restrictions and the focus and the scope that's available for the counterparties testing, yeah. So this is it. So that's it. That's all I have to say from my side on the user testing aspects. So now over to you, Ellie. Thank you, Vamini, excellent. Thanks for this. So we're having a lot of questions come in for you, but I think a lot of them are actually already answered, but maybe we just need to reiterate a few of them, Bobby. So there's a few questions again, but I mean, you just said it now, but can you say it again on the testing condition document? People asking, will this continuously be updated all the way through the testing phase? I guess the answer is yes, Bobby. But, you know, can you please stress this? Yeah, yeah, the answer is yes, Elaine. And the answer is very regularly. So it really is, like I said, it's the Bible. It's very important. It will also be and it will also include the the the various the version of the NRO that you need, the version of the assertive or go-sign desktop. The most important thing here is to keep an eye on the we have not opened it up yet. When we open it up, the current version that we're talking about is the six dot nine zero dot twenty. This, of course, is not updated yet from our side. But before we open it up, we will be we will be updating this. Yeah, we're working on this. The colleagues are testing this internally already. So you can be sure that when we open it up, it will be all of the documentation will be ready for you. So the key here exactly as Balmany said, if you look on the the ECB website, these documents will be constantly updated. The most important ones really for the testing is the the testing conditions document and for our migration, which Anaisa will discuss, is the info pack and these these will these will continuously be updated. Yeah, so that's the that's the main questions. I think that we've had related to NRO, the main questions that we've had related to the update of the documents. So maybe what we could do and I don't know that there have been some messages related to messaging. I think maybe Flora could take the floor on that one. If is that OK, Flora? Sure, yes, yes, thank you. So there were there was one question related to seven zero zero two when the structure is available. And then I would like to confirm that it is already in the software. And it was also published in the catalog of messages so you can check. And we also have checked whether our change request that we have implemented, which follows the ISO upgrades, whether it impacts this. And then it seems it's not so. So please rely on what is available. And there was another question, whether the counter parties, whether the counter parties will use the corporate action message score corporate action messaging. And then here here, the answer is that we have implemented scores. So ECMS is aligned to score and then it's reflected in our messages as published in the message catalog in the catalog of messages. And then, of course, there is a difference if you are a two or a two or a counter parties, you two or a two way. But like, yes, if if somebody would like to communicate a two way and using these messages, we are score compliant and so should be the counter party. Thank you. Thank you, Flora. So I think that covered a few of them. Bobby, do you want to stress a deadline again? There was somebody asking about the what is the deadline for completing all the the user tests? If that I think maybe the participant there who asked that might have been talking about our our mandatory test cases or, you know, something like that. So this is not I think they mentioned it was April. This is certainly not the case. So you must liaise with your NCB. You must ask them exactly what the deadline is. But of course, we have rescheduled. So there is no compunction on anyone to have the test cases done. By by April, yeah. Now, the only thing here is the other question that we had about the NRO, which was an important one. They wanted to know, is there different versions on the target services, different target services, but of course not. It will be a uniform. It will be a uniform version across the target services. Nobody needs to have one version of the go sign desktop to run one service and not to run another. It will be it will, of course, be the uniform version across the target services, but please pay attention to the qualified configurations documents. Please pay attention to the testing conditions document. These will both include the updates on the NRO.