 So maybe we could move now to the migration side. So basically, I'll give a very short introduction because Ana Issa is our expert here on the migration, and she would give you the full rundown. But just from my side, really, the important thing here is the documentation is, of course, the info pack. There will also be information in the testing conditions document. What's very important is, you know, we prepare so much with this documentation. Please read it. Please, you know, don't think because you've come to this webinar that you've prepared your testers, your migration experts, your operations people must be familiar with our documentation. Please read it. Another very important point that Ana Issa will make is that during our migration tests, there are some periods where we will ask you not to test anything else, only migration. We cannot police this. We cannot block you. We want you to please pay attention during this period that it's for migration test only and that you would only do the activities which have been prescribed for you during this period. But Ana Issa will go into that, but it's a very important take away from this one. So maybe Ana Issa, I'll hand over to you. Hello. Good morning. I hope you can hear me. So good morning to everyone. I'm Ana Issa. I'm part of the team that is dealing with the migration aspects for the ECMS. So what we will go through now is indeed the steps, the next steps in view of the migration, what is to come forward and also a bit of the impacts of this new planning. So I think we can start indeed. So what, as Flora has explained in the planning presentation that you saw before, the new go live means that we would have new milestones for the migration to production. But also there was an update or an adaptation of the migration testing plan in order to provide us a better strategy for preparing the migration into production. And this ends up being that we will have additional tests. Specifically here we are focusing on the tests for the pre-production environment or the U-test environment. We will have three more tests in which one of them is optional. So we have test 9, 11 and 12. This first test, test 9 is pre-migration rehearsal, a preparation week, dress rehearsal, and the migration week and dress rehearsal. So it's a longer test. And then test 11 and test 12, they are both what we call the preparation week dress rehearsals and migration week and dress rehearsals. You see the acronyms there. So this information is already part of the info pack under user testing and migration that is published on the ECB website. So I will not go too much on it, but what we can say and remind again, I think we discussed this previously, but the dress rehearsals mean that we would like to test as much as possible in prod-like conditions, and that would also reflect in terms of timing. The rehearsals however are adapted versions of these tests and of the phase, and in this case it's for the pre-migration rehearsal because of course in production we have a phase that is 7 weeks and here we will have a phase that is only actually 5 weeks long or 6 weeks, but there are other preparations we need to do that we will not need to do in the production environment because we don't have previous testing in the environment. So this is the direct consequences on the planning for the testing, for the migration milestones into production. You saw this in the first presentation, so I think if we then think about what this actually means in terms of the counterparty involvement. So if we can go to there, thank you. So what it actually means, these migration tests and the counterparty involvement. So the participation of the counterparties in the tests is the same, or is based in the activities that are expected in production. So if in this case for the migration to production, besides the connectivity phase where the counterparties will try the access via U2A and A2A when applicable, the counterparties are only forced into participating the pre-migration phase by setting up their own users and checking the data that was set up by the NCBs. So this being said, if this is the expectation then for when we apply this into the next upcoming migration tests, this would mean that the counterparty participation is expected only in test 9. In the part of the test that is a pre-migration rehearsal, which we saw it's from April to 7th of June, the schedule. However, as I explained, because this test will be a short version of the test, we are still investigating at your system level which activities will need to be executed. Because we have a smaller timeframe, we will have to have also a shorter version of the test. So we are checking currently which activities will actually need to be re-executed. And in that sense, since the only activity for the counterparties is the setup of their own users, this has still to be confirmed if it's needed. And so the actual confirmation of this participation by the counterparties is expected at the end of the quarter of this first quarter. So by end of March, we should have a clarity if the counterparty participation will actually be required for test 9 or not. Still, if it's confirmed that the execution of counterparty activities would be planned for the test, then this would be no earlier than the 27th of May. So as I explained, test 9 starts on the 29th of April. But counterparty activities would only start on the 27th of May if we would have these activities. So for the other tests that you saw, so test 9 for the preparation weekend, migration weekend dress rehearsals and test 11 and test 12, there would be no counterparty participation expected. Unless, however, as you know, the NCBs at national level, they can request the counterparties to execute some other activities necessary. This is catered at national level. It depends on some national particularities. So if this is the case, if they request you these activities, whatever the phase they are requested for in production, then it would mean that probably you would need to participate also in the tests. But this will then be communicated directly to you by your NCBs. Okay, so just to clarify that in conclusion, only test 9. Then this part here of the involvement of the counterparties as well in the test, which is important, I think Bobby made a reference to it at the start is or in the introduction to this presentation is indeed, it's really important that the test is, the migration test is respected in its execution by the counterparties. And what do we mean by this? First of all, you should only execute the activities that you have been assigned to. So unless it's a planned activity, unless you receive the request from your NCB and it's in the in the plan that you receive that's part of the activities, then you should not you should not execute any other activity, but it's also important that you respect the time. So for example, when we had the connectivity testing in pre-prod, there was several delays by some of the counterparties. So it's important that you keep to the timings of the activities. And also then respecting the environment availability by not carrying out non migration tasks in the environment during the migration test, but even accessing the environment. The same would be expected in prods that you are not in the environment unless you have an activity to perform. And so you should practice the same in the migration tests. The fact is that unwanted activity will create disruptions or unnecessary effects on the migration test that we cannot then reverse or filter out. So it's important that we respect this in order to have let's say valuable migration tests that are then fundamental for the validation of the migration strategy for the ECMS to production. So we would like to reiterate here because we saw some activities in the past in some of the tests that were not supposed to be carried out some even not partaking to migration, there were normal user testing. So I would really ask you to pay attention even though you are not involved in the test as it will be for the majority of the migration tests in the pre-prod environment, it is still requested the view that you take into account the dates of these tests and do not execute any other tests during this moment in the environment as it could affect the migration tests on go. So now moving a bit more into the production timeline and here is a recall of the migration journey in terms of production on how do we get ready for the go live. So we would start by the registration form submission to the NCBs and then the connectivity to ECMS via ESMIG of course based on the green light of the NCBs and then we have the migration of data that is mostly done by the NCBs and CSDs and then the counterparty would set up their own reference data also upon a green light of the NCB, we will have the preparation week and then the migration week and it's all in charge of the NCB and then we have the go live. So we had previously started this journey, the last time we had this focus session we had already highlighted to the start of the journey that it would be in September and it did eventually start so if we go to the next slide what we know is that we were before the decision of the new go live date we were already in this ECMS connectivity setup in the execution phase which was already ongoing for production so we were actually in the step two of the migration journey and then the phase was put on hold because it was the discussions and the decisions of the new go live date so with this new go live date as mentioned by Flora the connectivity phase was also replanned and so the phase will start now again on the 2nd of April 2024 and is it expected that the counterparties would start around 6th of May 2024? Of course this is a tentative date because it is essential that you only start upon a green light of your NCBs of your relevant NCB but it is expected that it would be around 6th of May this is provided for CB will have the start of their own activities then it will be the NCB setting up the data only then can the counterparties start so it's necessary that your NCB finalizes setting you up as a party in ECMS and therefore this is an expectation date so we will resume now with the connectivity in April so it's close enough and the counterparties will then have until the 21st of June to finalize their connectivity testing so if we go to the next slide it's a kind of a reminder of what are the steps then for this connectivity to ECMS via ESMIC so as mentioned the goal or the scope is to ensure that there is full end-to-end connectivity to the ECMS via ESMIC and this is valid for all actors and we want to check if it is working in A2A so meaning correct inbound and outbound message transmission but also U2A so meaning via the ECMS the A2A is applicable only to some counterparties so not all so it's not mandatory it's only mandatory if you plan to have an A2A connectivity same as we had in the connectivity in the pre-production environment that happened last year 2023 in the beginning of the year so when is it planned as mentioned the phase will be from 2nd of April to 21st of June but the first 2 weeks will be dedicated to 4CB activities for the preparation of the environment then we will have the NCBS, CSTs and TPAs connectivity that will start and then the NCBS will also set up the counterparties as parties in the ECMS based on the registration forms received by the NCBS and so once this activity is concluded your NCBS will provide you a green light to say that you can start the connectivity testing it is foreseen as I mentioned that this would be 6th of May 2024 this phase will involve all of the actors then who is the first level of support it depends a bit on the nature of the problem so it can be your NSP support team depending on which NSP you selected can be the ECMS National Service Desk especially for counterparties you would liaise with these two supports and in case of need the NSP team supports and the ECMS National Service Desk can cooperate in joint teleconferences so this is to speed up some of the problems so this is just repeating in production the phase we have already done in pre-production so the key documents for these that you should follow because they describe the steps perfectly would be the target services connectivity guide which is available on the ECB web page and of course then there are the selected NSP documents and guides this depends on your NSP they will have documents on their website as well so this is the next phase in production what we will do but to prepare for this and as I mentioned this is the second step in the journey but there was a step before which is the submission of the registration forms and also in preparation for the connectivity there are certain activities you need to do with your NSP specifically so in preparation for this phase and we know that this phase had already started and then was put on hold so we know that for many of the counterparties you have probably already executed these activities so you would not need to re-execute them again in principle but it's still important for you to validate that you have performed all of the necessary steps so don't wait until you know 6th of May to check that you have all of the necessary prerequisites to start the connectivity take care of it now so that you can start on the 6th of May as expected so for these you have this kind of a checklist here with these two tasks so the first one is all of the necessary steps at NSP at the network service provider level so like selecting the NSP you should have the contract the e-ordering the request for the close group of users subscription all of these it's important steps that you should do they are specified in the target services connectivity guide but you can also check them with your NSP specifically if there is something that you should do and then there is of course the sending of the migration registration form to your NCB if you haven't done it yet you should do it regarding the registration forms it may be necessary that by your NCB that they may request you to resubmit the form or request additional data or confirmation of data this also has to do with the evolution of the system and some additional data that might be required for the NCBs to ask you so this is something that it will be based on your NCB request but please do check if you have sent it already or not and as I mentioned the target services connectivity guide or the NSP should be consulted for further information on this pre-checks that you should do so that would be the next step for us in production in the testing site please do expect to know more about your participation or not in test 9 by the end of the first quarter and please do pay attention that if there is a migration test on going to not do other activities in the environment so I think that's it from my side but probably there will be some questions thank you Anisa super good so we're being bombarded here with questions so I think things are coming in a little bit of a delay so if I can ask you to stay on Anisa then there may be questions that we will come to you but we're having now a lot of questions come in on on the testing Bobby if I can bring Bobby back that would be great yeah we've had a lot so I'll try and group them together in the different areas if you like so firstly in terms of connectivity so what's very important is the specifications for ESMIG these are on our shared documentation page in the ECB they're not on the ECMS dedicated page but we will share all of these in any case but just to let you know that the ESMIG documents are over there now there was a question from one participant about a distinguished name issue and they say that this issue looks like an incident that you need to raise with your service desk and this for me is kind of a a general thing that your national service desk is your point of contact and for something related to distinguished names first of all you must consult the connectivity guide and then if you are not getting results that are as expected then that's when you liaise with your national service desk so that particular one that was posted on the DN I think it's for the national service desk but it's the wider point so then we have also there was a question about 4I you know the use of the 4I functionality now from our side it should be there may be some restrictions to this but this is definitely also one for those of you it's very important of course that you would work in operations maybe while we're testing we test in 2Is at the start and then we progress to the 4Is when we're doing some user acceptance testing or whatever but for those of you who of course will always use it in production if you're having any issues with the 4I functionality at the moment please raise an incident with your service desk please discuss it with them and there may be some restrictions I think there are one or two open incidents related to this functionality but the national service desk will let you know then in relation to ECONS 2 there were some questions about ECONS 2 of course how ECMS will interact with ECONS 2 this is a very important part it may be that it may have to interact with ECONS 2 it will definitely be that we will have to test this we will bring you more information on this if not in a future session we will bring it in a maybe in a dedicated session so let's table ECONS 2 but it is very very important and it will be tested before we go live the interaction of ECONS 2 and how it works or how it would work were we to have where ECONS 2 would have to be brought up the testing conditions document the next one will be released on the 26th of January so in two days time what's very important for everyone is that in the testing conditions document there is always a notice to say when the next one will be coming so for those of you who want to know when the next one is coming it will always be in the current edition so this is a very important one for all of you as well and this is why this document is your bible you will see the updates and you will see when the next set of updates are coming there was a question about testing I think what's very important here what Anaisa was speaking to you about in the connectivity testing there was we're talking about connecting to production so this has nothing to do with what you will test in the pre-production environment you know we will open as Bamanee rightly stated we will open all of this functionality to you we open it in stages we will make it clear in the testing conditions and likewise also for the migration testing there if there are any restrictions in the migration testing we will also include this in the testing conditions document so this is very important for you to consult this as we say you know read the manual this is the most important one the info pack is important but the testing conditions both from a testing and from migration perspective is very important another very important document is the fundamental test cases this shows the fundamental the test cases that you will need to pass in order to access the platform that your NCB will certify you is ready to access the platform but it also gives the overview of the fundamental functionality of ECMS so I think I've gone through everything there was also a mention about the planning of our bill module the testing of the bill module we're not there yet we have still some we have still some changes being made to the bill module we're still working on that but it will be opened up it will there will be invoicing and we will we will let you all know when the time comes this will also be in the testing conditions document so you can see how important this document is I think I have answered all of the yes I think I've answered everything that I thought was open there super thank you Bobby there's there's a question about about maybe for you Anissa about the if there's specific documentation about the migration testing and if so where they can be found you want to bring a word on that yes can you still see it yeah we see it in you good so now for the migration testing we as I mentioned before or the migration in particularly in particular sorry there could be some national particularities of the NCB of different NCB so the documentation if it's shared is shared directly by the NCBs with the counterparties so whatever documentation is available for the tests they are made available through or even the migration in production they are made available directly through the NCB now what you can find published on the website is of course as mentioned is the dates for the migration tests and even in the info pack you have more details on the division of the test let's say so by actor when would they be expected to participate in a specific test so this information is included in the info pack and then specific documentation saying which step you need to do when then this is provided by the NCB even case there is counterparty activity expected in that test so as you may see only up to now only test for have the participation of the counterparties because it was a pre-migration dress rehearsal and besides that the connective the different connectivity phases in in this case in the new test environment so that's why also you might only have received information once about migration test because this was the only test and it was in I think April or May 2023 so it has been a while but now of course if test line the counterparty participation is confirmed then your NCB should provide you more information on when your activity is expected we had a few questions about a specific slide you want to say a few words on this one so it's about the production migration so I think they are referring to this slide right Anisa Yes so this slide it's so the previous slide to this is the journey to production so to clarify this is the migration journey in production so it's not about the migration test it's about the steps that you that we will take in order to reach the go live in the production environment so based on these and we are on step 2 or we will start step 2 soon we were in step 2 and we will restart so it's important that you check that you have executed step 1 which means we lost we lost your voice Anisa we lost you still okay while she's gone we move to Bopi and then we bring you back okay Bopi over to you yeah yeah so basically what's important here there was a question in the chat about will we be able to test during the migration phase so I think for me there's two points Anisa made the point during our migration testing there will be restrictions to your testing and Anisa will make that clear but during migration in production which Anisa is going through with you now our test environment will be open and while we have a formal end of testing in the planning you know for the end of September or whatever the test environment will be open you will have access you will be able to test in October you will be able to test right up to the you will be able to test right up to the go live and even after because of course you know when we when we move to production we will then be testing the new releases in the test environment so there is no plan to close the test environment for those of you the only restriction as I said in the test environment may be brought about by as Anisa explained the migration test and then we would ask you not to test other things that are non-migration related during that period and then when we move to production you will still be on the lower level able to test as much as you want all functionalities but no restriction while this pre-migration that Anisa is describing here is taking place and then for the step two as Anisa said you know the connectivity this was the point that some of you have already reached and those of you who have not we ask you to catch up and those of you who have you know you are now already ready we had a little bit of a halt because of the rescheduling but now we can start to progress again follow the timetable that's being set for you by the relevant documentation and those of you who were who had not reached it to that time now is the time to catch up I think that's the summary of Anisa's points and also the questions that we had and then the fundamental test cases there was another question in the chat is there a link between the functionality and the fundamental test cases so this is the fundamental test case documentation in that documentation is literally the section of the UDFS the section of the documentation the description of the functionality and everything is in this so that is very very important indeed for you to know all right super I don't know if sorry there was one more Elin and it was important as well it was a question Elin about our period of disconnecting where we disconnect from T2S and from CLM and of course there will be restrictions you know there will be the point is that you could at the moment you know the messaging flow between ECMS and the other services is cut off but nonetheless there are numerous functionalities and there are lots of things that you will be able to test testing is not halting we will be concentrating on we will be concentrating on functionalities and certain things where we personally be taking the opportunity to do a volume test for example during this period and certain things like that in order to keep the testing continued but to be able to do it and also there is the simulator which will be reconnected so it's not as good sadly as the T2S as good as the CLM but nonetheless the simulator is there to bring further value and it has been used before so we will try to make it as good as we possibly can but of course as you know as you all know the best is when we are fully connected and I explain to you the reason why we must disconnect in order to give the T2S community and the T2S community production like conditions during that period thank you Bobby so I think we covered a lot there I just want to see if we can bring Anisa back do we have sound on you again or I think so yes we do, apologies for that no worries so is there another question that you would like me to address Eileen so it's a bit of KO taking the chat I don't know if Bobby confirmed this but there was a question about the connectivity in phase that we would have and if the other functionalities would be available but I think Bobby replied that only the connectivity is for prods environment not for the user testing environment so I think that one was covered and as I mentioned the info pack on the user testing and migration contains the dates for the migration test so it should be available there but I think also the testing conditions I think Bobby mentioned before also usually cover any unavailability of the environment so you could also check there is there other questions Eileen that you would like me to I think this covers it you are bombarding us here so thanks a lot for that but I think we are covered on most of it we are just double checking here is there anything more we want to go back to now Bobby Flora is there anything that we are missing I think we have managed to cover most of the questions in here so then I just want to thank Anisa as well and thanks for coming back for picking up questions and also Bobby to jumping in here thanks there is one thing that I have been referring to mandatory test cases this is from my old T2 days here in the ECMS they are called the fundamental test cases so just to everyone in the terminology it is definitely the fundamental test cases here in ECMS yeah exactly super thanks for that Bobby