Archive Central: How to keep the data you need

Good day, everyone. And, everyone, welcome to you all. Thank you so much for taking the time to join us on this webinar today. So I'm Sonele, and we'll be showing you a practical view of our archiving solution called Archive Central. The session is gonna be kind of split into two parts. So I'll do the overview session, and then my colleague, Frederick, will show you guys the demo. So for those of you that don't know me, my name is Sanele, and I'm an account manager here at EPI's Labs. And I help manage and support clients across the Middle East and African region. And I have been with EPI-USE for about seven years or so now. I won't get into my boring history and tell you where I went to high school. And, yeah, and I have my colleague, Frederic, here with me. Frederic, you can introduce yourself quickly. Yes,. Yeah. Welcome, everyone. My name is Frederic. I'm one of the product managers specifically regarding Archive Central, what we will be showing today. I'm based in Germany and also work with EPI-USE Labs for over ten years now. So thanks, Anita. So as I already mentioned, today, we're gonna be giving you an overview of our archiving platform called Archive Central. And I think this is really key, you know, just to put a lens on because as we're all planning for our SAP future, as we're all turning to our future state, whether that's moving to S4HANA, adapting new cloud solutions, or just modernizing your landscape. We often have a strong focus on what comes next, what the future state look like. But we believe an equally important question is what happens to your historical data. And we can all agree that without a well defined archiving and legacy data strategy, you cannot risk all the unnecessary complexity and cost for your future state environment. So just briefly, Archive Central is a cloud based archiving software as a service solution. And what this then means for you as the client or a customer is that there's no really an infrastructure for you to manage. So there's no need for provision... To provision and maintain servers, databases, storage, or any underlying archiving infrastructure. And that obviously directly then translates into lower IT overhead. So you don't need an internal or maybe a SAP basis team or an infrastructure resource dedicated to operating the archiving platform. So it really does reduce the operational burden. And thinking of how the data is extracted from your SAP system and then ingested into Archive Central. When the data is extracted into Archive Central, the data model will be extracted along with the data. So this means that this allows you to see your data on Archive Central, how you generally see it on your SAP system. So you kinda get a familiar view, of a familiar UI. It's not gonna be the same user interface as from your SAP, screen or the SAP GUI, but it's gonna be very similar and it can be replicated into archive central so that you can interpret the data similarly how you would to your SAP system. And just to mention very key data privacy, Archive Central also supports data privacy compliance, including regional data privacy laws and regulations such as your GDPR, Papia, DPA, just to mention a few. It also enables configurable data retention policies, allowing archived data to be automatically deleted after a defined retention period. So you might have, retention policies in place in terms of how long you can keep data archived, and we can configure those into the system so that the data can be automatically removed or or even removed just on request. It's also certified to I... ISO standards, ISO standards, and SOC two as well, ensuring very high levels of security, governance, and compliance. And you'll see in the bottom left corner here some of the tabs and icons of that certification. So data rights, the hidden cost driver. For any IT landscape or for even any transformation project at large, the hidden cost driver is data. And most programs try to carry decades of history if you're migrating into S4HANA and carrying decades of data, decades of history, every record migrated, cleansed, tested, and reconciled. The thinking is often, okay. We might need this data, so let's just bring it all along. But that decision has a big price tag to it, because data migration is often the largest or riskiest work stream in the whole program, typically about 40 to 60% of total project costs. That means half your budget can go into moving the data before you even deploy or even deliver a single new capability or a new functionality. So to sum this slide up, large volumes of data drive risk, complexity, and cost as well. So what what could your challenges be? What are your challenges? Or maybe a better way to put it, what would your business drivers be for you to need a solution at Archive Central? What are the business drivers that we often see for Archive Central? So you might just wanna wanna be reducing your system footprints where you're sunsetting legacy systems. You might need to retire those legacy systems. Maybe you're facing high operational costs when maintaining legacy systems, which can be expensive to support because of outdated hardware, maybe limited vendor support, could be out of maintenance, so no upgrades or updates happening on that system, which obviously then leads to security vulnerabilities. So you could be susceptible to breaches of some sorts. And then having a good business divestitures where maybe the buying or selling party might just require display only access of their data on some way that's secure and safe where they just need that data for reference. They're not really transacting on that data. And Archive Central is actually an ideal place to store that data. Or perhaps you might be going in a full business transformation, you know, as you mentioned already, you might be moving to s four HANA, and you just wanna sort of minimize your footprint on your target system as well. Or system transformation where you're just rightsizing your ERP system, and you just wanna continuously keep a lean ERP system. Because we all know as businesses grow, the ERP systems accumulate vast amounts of data as well, which often leads to performance degradation and increase in storage costs as well and all the other complexities that come with managing large volumes of data. So you really do need a solution to control and limit data growth, ensuring that your ERP environment remains agile and cost effective. So we've... I've kind of spoken about SAP a lot. I've kind of mentioned SAP data specifically. But just to call this out, archive central is not strictly SAP system. It's not limited to SAP data. It is not a SAP system at all. However, it just does work a bit more seamlessly with SAP just because of our tooling that we use for for extractions. So over the years, we have replicated over 3,750 SAP standard business objects across different modules and industries. And EPI-USE Labs has thirty five plus years. I think it's actually closer to forty, but we'll just stick to thirty five for now. Thirty five plus years of SAP expertise with deep understanding of the SAP Data Model. And what this thing gives us is that the solution actually preserve... Preserves business context and relationships. So by extracting not only database tables, but also the underlying SAP data model. So when the data is extracted from your subsystem and then ingested into archive central, excuse me, you actually get to see your data how you would see it, in your subscreen. So the data is loaded into our SAP Central while the the data integrity is maintained so that you can be able to still report on the data and still use it as reference and for whatever legal audit requirements you need it for. And then just a bit of numbers or stats rather around our tooling. So we have about eight hundred eight hundred plus clients using the business objects work workbench in over 49 countries. So the main engine for our tool is quite similar to Data Sync Manager, which is one of our flagship products, which is used across the globe. And we have about 5,500 licenses, sold, of these products that are based on the Business Objects Workbench. So you can see already how many clients across the globe rely on this tooling, and you can see how it understands the SAP structure and how it understands the data model of SAP as well, which is why it's able to almost seamlessly just ingest your data, giving you automatically a similar view to what you'd often see on your SAP screen. And then as mentioned before, archive central isn't limited to SAP data. Right? That's very important to call out. We can support archiving from any IT system, whether your data resides on non SAP applications, Oracle databases, custom built software, or even just decades of old legacy platforms. Archive Central can very well handle those diverse data types and formats. And you can see at the bottom here some of the familiar names, your Workdays, your Conquer, Ascender Payroll. So we can extract data from those systems as well. And for any custom built applications or custom built systems, our custom development team actually builds a dedicated extractor for your specific legacy system so that we can also extract data from there and ingest it into archive central. So it's not a manual, effort if it's... We're extracting from a non SAP system. Right? Or you can just bring your own data, and this is what we like to call client led exports. So your teams might provide data exports in the form of CSV maybe according to any specifications that we'd map out in our workshopping phases. Right? So then Archive Central does offer the flexibility to import and manage your own extracted data regardless of the source system. And we then, obviously, through the implementation, we are system structuring your data effectively within Archive Central, catering to both the upload and the visualization process. And once that config or that configuration is in place, from there on, it just becomes very easy. It's it's almost a simple drag and drop process of the files to kick off that that process. So, yeah, just before we get into the demo, I hope that gives you a high level overview of what Archive Central is, what it is generally used for in the market, and, hopefully, you can already begin to identify where it might be a good fit for your business. And without taking up more time, I'd like to hand over to Frederic for the practical demo. Thanks a lot, Seneva. Sharing quickly. In general, just to, start off with, I just opened a demo system of Archive Central, using a web browser such as, in this example, I'm using Firefox, but you can use any web browser to get access to Archive Central. And while Archive Central itself is accessible through the browser, it integrates to your system landscape like any other system. Meaning, if you have a single sign on solution, that is in use in your, system landscape, you can connect the single sign on solution as well. If you have an identity management system, you can connect it as well. And, typically, Archive Central is configured so that it's only accessible from within your own network or VPN, for example, just to add this extra layer of security on top. And remember, as an earlier described earlier, Archive Central is not just a solution for SAP. It is also a solution for any kind of system, whether it is a Microsoft dynamic system, whether it's something custom developed. And, specifically, you can use one and the same Archive Central instance to retain data that came from multiple different source systems. So one of the examples could be that you use archive central to retain all the data from your SAP r three world before the, system got, migrated to SAP S4HANA, or, you might have, connected systems such as maybe a Salesforce system, a Microsoft Dynamics system, and so on. So you can use and reuse Aka Central as a target, for multiple, source environments and just separate the data by, for example, authorization objects. But, one of the concepts I want to highlight up first is, in the top or or or center section of the screen, is the concept of diff... Different workspaces. A workspace, we can use it depending on the on the customer's requirement. It can either be a workspace for a specific functional module. So in in this system, we have a separated workspace for all our finance data across different source systems. The same goes for our HCM or human capital management data, but a workspace is more oftenly used to separate data coming from different source systems. So if we have works workspaces for data coming from SuccessFactors or from an IFS system, or on the very right, we see, a system which, in the SAP world was called e d two and the client number 800. So it is very flexible depending on, what your actual requirement is. And just to explain how you can see the data, I will use the finance workspace as an example. And if we scroll down, on the right hand side, we see the list of collections that we have available here. So a collection is effectively our definition of a business object of a data model from a specific source system. And, as Senele also mentioned earlier, the main or or the most important part when you decide on such a solution is always how intuitive is the system, how familiar is the user interface to what your end users are used to, for the past ten or twenty years where they used the original source environment, for example. So our main goal must always be to bring it as close as possible to the situation that you had on, the originating system. So within one of these collections, we are combining all the database tables that the system used on your source system to, display the data in a meaningful way, which means, this would... If we bring data from an SAP system, it will have all the database tables as they existed on your source environment. So that does not only include every SAP standard tables, but it could also include your custom developed tables or maybe custom fields that you added to standard tables. And we, the collections that we see here also have the transaction codes, from the SAP world, because we know that some of our users that are using SAP for a very long time, they might rather start the transaction trial, start the report or a view by using the the short transaction code instead of navigating through, the the folders to get to the actual report that they are interested in. So this is effectively how we or why we try to build collections to replicate what your users have used in the SAP environment. The very first collection that we see on this one is f b zero three to view accounting documents no matter what type of accounting document it might have been. But we also have master data in the similar fashion, so our customer master or vendor master transactions. And, if you take a look at the name, you can already see that in the brackets, you are seeing the, at least the way it was set up here that those sets of data were coming from different SAP environments. The one was system e d one. The other one is e d two. But if they are connected to each other, we can bring them and archive them in the same place and make the reference. And so you can drill into a specific subset and jump to the related data even if in the... In your system landscape before, those were on different systems and you had to open different systems at once. On here, we can simply connect them together if this is a requirement. And on the bottom left hand side, we also have saved views. I will, showcase this later on in a second, but saved views is basically very basic or simple reports that we can build on top of, one of these collections, to replicate also specific reporting capabilities that your users might need, and are used to from the source environment. And, just to make the point how we try to, make the user interface as familiar as possible, I just want to start with a side by side comparison. So in my SAP system on the right hand side, let's just start with the transaction called XT03 to view a customer master record, and, I can do the same on the left hand side on archive central if I just click on my collections. And as in this example, I'm just also again typing the transaction code. It tells me, alright. In this workspace, I only have customer master records, from ED2, system ED2Client 800. So if I click on this one, and let's just jump to the SAP world. And, one of the examples that I like to use often is the customer with the number 1000And1. So if I just enter this and let's just execute it on the SAP side. Right. So I've... I have it open on SAP side. And, on the left hand side, I can, again, just enter the object key that I'm interested in, click in. And now, the main point here is on the SAP side, you see that SAP is grouping the data in different tabs. We are starting off with all the address related data in the first and initial tab, then we have, for example, our bank details, our payment transaction in a separate tab and so on. And we are literally replicating the same behavior on, the left hand side on archive central. So we are starting in the, tab to replicate all address related data. But if we click on payment transaction on both sides, we can see the related, bank account number. And yeah. So, we could navigate through the different tabs, but it is, literally trying to replicate it the same way as your users are used to interacting with your system for the past ten or twenty years. And this would work the same even if you have custom extensions, custom fields, in the screen on on your SAP environment. We, later on, I will just show you how easy and how flexible, Archive Central was designed and how we can or could add it if this is needed. Alright. So this was an easy, customer master example. Let's just pick a more complex example from the transactional world. If we take a look at accounting documents, first of all, we will have a lot of data in accounting documents typically, but I can use the filters on the very left hand side, and it already suggests me different fields that I can search on. And, on here, I literally have, all fields available that, were part of, the data model on the source environment. So if I want to filter on something like the company code, even though I I don't need technical knowledge to know where it is stored, I can just type in the field company code, and it will suggest me all the different places where it would be stored in the data. And I could also use the same depending on, whatever con... Language I'm used to. So for me, coming from Germany, if this data where the system was coming from was also configured using the German language, I could set up archive central and just switch to the German language and use the German word to search for this field, for example. And if I just filter down, let's say, I want company code 1,000 and maybe just company codes one and five. Let's take these. I can now filter down the views of all of the... All of those accounting documents for a start in company code 1,000. Let's pick a different selection. Okay. I I assume all the goods receipt were really start in company code 1,000. So let's go back to the selection. But for example, I can also now, if I further want to narrow down, the selection, I could search for the fiscal year. And let's say I want data from... I don't know. Let's say 2010 and maybe 2011. Alright. And if I now drill into one of these accounting documents in one of these good receipts, it is again we try to, make the user interface as similar as possible. I think here, the interesting part is always the the items tab, all the, different line items, that go, with this accounting document. And, as we can see here, for example, the column for GL accounts or profit centers, you can see that these, numbers are highlighted in blue, meaning, I can now click on this GL account number, for example, and it would open the, transaction similar to FS00 on the SAP world. And now I'm viewing the GL account, simply by drilling into and clicking on the on the number of, on the ID of the GL account. And now, over here again, we have a very familiar user interface to how the data was displayed in the SAP environment. Alright. And this is... What I've showed here is possible no matter if the data is coming from SAP or non SAP. And I can just, show you one more example from the saved views requirement that I mentioned earlier. So specifically in our HCM demo, workspace here, we can see different reports, different saved views that were built. One is, for example, a sample report that is simply filtering employees by their country of birth. So I could now... If I'm searching for specific employees, I could drill and click into the section of the graph to, for example, if I click on IT, it would filter down and display all the employees that were born in Italy as in this requirement or maybe another, example and requirement that I've seen in a couple of projects is, this report, where effectively it is filtering by action type, and action type could be an employee that is joining the company in a specific year or leaving the company in a specific year. So I can I can be very flexible of how I define these these basic queries or reports to basically provide you with the most important reporting capabilities that you might need for historical data? Alright. Now everything that I've shown so far, was with data coming from the SAP world. But just to highlight, if you have data coming from maybe a Microsoft system or something custom developed or as Seneva mentioned, if, the idea is that you have the technology and have the the the people to do the data extraction yourself, I will just showcase, how easy it can be to bring data to Archive Central. So, just as a disclaimer, typically, in most of the projects, the client rather prefers that we are doing everything from end to end, the entire data extraction, data transfer, replicating the familiar user interface. But in some special cases, there might be, the the ask, the requirement, especially for larger corporations, this could be a requirement that they have a dedicated team that could do the project themselves. So while it was also mentioned earlier that we are currently growing our standard capabilities for all other, system vendors, not just SAP, I'm... I've just prepared one example steps, just to visualize how it would look under the hood without going going too much into the technical detail, but so in the folder that I'm showing here now, there are multiple files. I'll just, walk you through the full step, but effectively there's one file which has the name data definition. The data definition is basically how we bring the structure across. Meaning, in the data definition, we are, basically storing, what tables and in what structure did they exist in your system, including all your custom tables, custom extensions, and so on. What do we need to replicate on Archive Central? There's a ZIP file with, data contents. If I just open this one, this is just raw. I used in this example CSV files if it opens up, and this is just... So this is all demo data, obviously, but, this could then store effectively, the data that you need to replicate and store on Archive Central. And as a as a consultant or a super user that has these, the required authorization to be able to bring data to archive central and modify all the user interface, I can start an import task and just call it, I think it's it's a customer master example that I prepared again. Simple customer example. And if I'm simply sharing the screen and so on. So if I'm just transferring over the data definition and the data content and, kick off the import, it will now, first of all, create the structure then import all the data to the structure. And as a follow-up example, what I will show you is also, there's another ZIP file. I can maybe just open it. Archive Central can not only be used, to store all the database records that you have, but in most cases, you will have attachments, maybe to your accounting documents, to your, you know, to to a specific purchase order or something. You will most likely have an attachment linked to it maybe in a PDF format, maybe as a as a, like, as a scanned in image or maybe an Excel file or something. You can store these attachments also on an archive central in line with these records. So in this, zip file, I just have a a bunch of different attachments such as, the ones that I just mentioned, but also, for example, a text file. It could be literally anything. And, so if I go back to archive central, everything is imported. I can just show you what it done on the first screen. So, it now created a new collection a minute ago. If I drill in, it currently just by default generated some kind of view or filter criteria. So as a super user or what we as our consultants would do is is now just aligning the user interface to make it easier to use. I will just show you the the most important bits. So opening the the customer, with the customer number 10 in this example currently would not display me anything. But if I am a super user, I can switch on the edit mode and can now, decide, alright. Maybe if we stay... Stick to the example that I had earlier from the SAP world, it started with address data in the first tab, and I know there is also address data in the demo data that are uploaded. I can now decide, alright. I need the street name. I need the name of the town and maybe the district, that I want to display in my first screen. And now let's just play around and make it a bit wider. We can see the address for this very specific customer is from from France, from Paris. And I'm also interested in the search term so that it's easier to access and find the correct customer master record that I'm interested in. And let's just create a separate tab again for my bank details. And I can also display the data as a... In a table format. Let's just call it bank details again. I want to display 10 records at a time if possible. I'll just speed it a bit up. But as as you can see, there's a lot of stability. Meaning, no matter how customized your system might be, we can display this, as close as possible. Right? So now my newly imported, record or collection has some address data, has display some bank details that were exported. And if I now want to display, like, my file attachment I mentioned earlier, again, something that a super user can only do, I will just go into some of the technical settings here and to the, leading table that we... That this collection is using. And what I can do in a quick format is just I can create a new column to say, this is a field where I want to store and load all my attachments against. I'll give it a technical name of, just file, but the description, should be attachment. And if I just save it as such and again start a new import, I can just take all the documents that I showed to you earlier and start a new import, but this time an import for documents. What I need to do is select the the location that I just created where I need to load the attachments against. Just call it simple. Customer attachments. And, again, just drag and drop the... All the attachments that I want to link to them. And, while this is importing, I think this should be fairly quick as well. Let's just refresh and see what it what it estimates. I think it's, yeah. It would take another minute. But while it is importing, what I now would need to do is, if I drill into my example again, I would now need to, again, decide how how do I want to display the attachments. Right? But, what we are doing or or what is in general possible is we have a standard set of how the data should be displayed from a variety of different, systems. So I can just, use, my configuration file that I had prepared from earlier. And, if my computer is loading... Yeah. Now it is reacting, so I can just drag it in... On top, trigger the import. And even though the attachments might not yet be all imported, we can just take a look at the example record here. And, now the the screen layout changed a bit. I now also have a tab for my contact person details. I have a separate tab for the attachments, and we can see that for this specific customer master record, there was apparently an Excel file linked again. If the attachments would be, for example, an image file, a text file, or or, like, a PDF file. If I would click on this, on this link, it would display the the file in line in archive central. In the example of an Excel file. It would simply download the file to my front end, and I can open it with Microsoft Excel. But, you can also imagine, if we pick an example from the HCM world, for example, and let's pick the employee data from system e d one. For an employee, it might be relevant to store all the payslips for a specific payment, period. So in this example here, you can see for each, individual, period, there was a PDF uploaded against. And if we can just click on the PDF file here, it will just load the, PDF file and display it in line the way, or in a similar fashion as SAP in this example would generate these PDF files, if there's a need to. Alright. So in short, we have a, ever growing, set of standard extractors and the standard data models, on the slide earlier. So I know they highlighted from the SAP world. Have over, I think it was 3,750 of those already prepared, but we are expanding to build out the standard for non SAP systems in general. But even if you have some kind of custom developed system, We are very flexible in adjusting this to your specific requirements. And just to highlight since I'm currently in this specific payroll period for this, employee where I just displayed the the PDF file, the payslip. One important part to to highlight, our extractors in the SAP world are not only able to extract all the data from the transparent database tables, but what we can see here, for example, the results table, r t, the CRT table, and so on. Those are tables that SAP would typically store in a clustered format... In a clustered and compressed format. So it's not really easy to access these type of tables or this, this data within your SAP environment. But since we have this, the business object workbench, the business object workbench knows how to open and decompress and decluster all, these tables as well and bring it into a readable format so that we can use it on archive central as well... Itself. So especially when you have SAP system, it is... We typically always want to use our extractors because, they can extract all the, data from clustered or compressed tables, that you would otherwise miss. But for example, on the one hand side, in this example, from the HCM world, but also in the finance world that I showed earlier, a lot of the data is actually stored within, cluster tables because SAP optimized it this way, for the areas where, SAP knows you will have, a load of of of... Like, a huge amount of of of data and records. So both the accounting data, the accounting document example I gave earlier, and this one for HCM data, those are typically areas where on the SAP or on the source environment, you have high amounts of of records, which is why SAP is storing the data in, clustered tables. And, but this makes it more difficult to extract the data, but, yeah, the business object workbench and archive extractor know how to open these examples and bring it into a format that you can access it on on archive central again. And, yeah. So, this is, everything that I wanted to show in this demo. There's maybe a small topic that I forgot to highlight earlier, but what was also on the slide, if I go to this section of HCM data, data retention reports. So if you have requirements such as maybe your employee data, as in this example, needs to be deleted after ten years, or maybe, something... A a similar requirement for for customer, data and and and so on. Depending on what country the data is coming out, what data privacy law we need to apply, we can also use these saved views to build data retention, reports. And in this way, we, what our best practice is to provide you, first of all, with a report so that you can, for example, not just see, alright, based on the criteria that I've given in the data retention report, these three employee records were marked as, that they meet all the criteria so that it needs to be deleted from the system. You can still click on, the individual item and take a look at the specific employee to verify if, if this is correct, if this should be deleted, and then sign off on the deletion request so that this set of data can either be permanently deleted or maybe just redacted so that you remove and redact the the PII data, the personal identifiable information from the system so that you can keep the rest of the data. There are multiple ways and depending on what, data privacy law and what requirement you might have, we are again, very flexible and and can provide you with, these capabilities to either provide you with a report to identify what needs to be removed, to do the removal itself and or redaction if you don't want to remove the entire dataset. Alright. And, then I think I've I've covered everything, in this short amount of time. And if there are more use cases that you are interested to see or different specific systems that you might have where you want to figure out, if it's possible to archive it with Arcade Central or not. I would suggest, we can reach out after the webinar and go into very specific detail. But, now I would, hand it over for Amy if there were any questions that we should cover. Great. Thank you so much, Frederic, and thank you, Sunil, as well for that intro. We have received a few questions. So I just wanna kick off with the first one, and this obviously is posed to both of you. The first question is, how long does the implementation process for Archive Central typically take from start to finish? Alright. I can respond on this one. So it's it heavily depends on the on the exact requirement. So I think in the in the archiving world, oftentimes, we only get involved when, when clients have a very strict timeline. Let's say, they need to decommission a system in three months' time. So if there's, a requirement such as this, we need to, plan accordingly to to meet the requirement. But in general, I would say most most projects would take somewhere between three months and six months, but, it can be as fast as, let's say, two weeks or something. So... Yeah. I mean, also the the entire data volumes, take into consideration the the way or or, like, the the type of system that we need to extract from and and... Yeah. I think there are a lot of factors, but in general, it can be as fast as two weeks. Most... But most of the projects are somewhere between three and and six months, I would say. Great. Thank you so much for that. And, everyone, please feel free to pop any any additional questions that you do have. We have also received an additional one here. Once the legacy system is shut down and moved to Archive Central, how does the user access work? Typically, once data is moved from... No matter if it's coming from a production system or maybe already a legacy system to an archive. There are more often... On the customer side, only very selected key users that should have access to archive data, but then the access is is working in a way of... We have a separate user management system on Archive Central. And as I mentioned earlier, so this this user management system can be connected to, for example, the single sign on solution or the identity management system so that users can easily, interact with it. But, primarily, users would open, the URL of of Archive Central in whatever browser they they prefer to use and, could, this way, access the data stored. And just to add there, Amy, that there are role based permissions as well. So it's not a case of... If all those users go on to archive central, they'll be able to see everything that's been archived. You will only be able to see data that you've been given permission, to see. We could even replicate the roles and authorization that you had in your SAP system as well just to make sure that you don't expose to other sensitive data that you're not supposed to be seeing. Great. Same. Thank you so much for for that. There's a lot of conversation around data privacy at the moment with a whole bunch of laws sort of being put into place. How does Archive Central handle those specific data privacy requests? Specifically, for example, GDPR's right to be forgotten or some of the retention policy guidelines on historical data specifically. Alright. So one one of the one of the requirements is, what I what I showed earlier, like the the right to remove or request the removal of data and and so on. I think this this can be replicated by using these basic, say, views, these basic reports that I showed at the end. But, one of the other requirements, could be, to either extract and get the data in a machinable, readable format out of the system again. I'm not sure if I... I mean, there are multiple ways I can I can quickly, go into the the system again if if I have the time, but there are multiple different formats of how you could, retrieve the data from Archive Central again and and provide it to whoever requested, to to see their data? So, yeah, I can... Maybe just just quickly open something up. So just if I'm if I'm going back to this this list, you know, there is, always, where it makes sense on the top right, a button to export data. And depending on the the environment, there might be different ways of how the data should be, presented. So, for example, the auditors of the company might require a specific format, and they always want to have the data presented in a specific format. So we can we can adjust it, but, this is how we could, comply with with this requirement. There might be requirements such as if if the if the company stores Indian financial data, there's a requirement to host and store the, that type of data physically on Indian soil. So, for those type of requirements, we could simply spin up the archive central instance using a data center on Indian soil. And, you know, for for clients where they might have, like, larger corporations where they might have multiple of such requirements to store data in multiple countries or have a combination of different data privacy laws, we could do the same for for each and every requirement, I would I would say. Great. Thank you so much for for sharing that. The one question that we've received, and it's such it's such a simple one, but it's so important to ask is, where is the archived data actually stored? Alright. Okay. So I will also just jump in here again. Currently, we are primarily leveraging a hyperscaler to to to host the data, and and this way, we can be flexible and and host it in the in the country, where it is required to be at. And, therefore, we can, yeah, pretty quickly spin up an instance, especially if, a client is approaching us and they need to have everything archived in maybe four weeks' time or so. We are pretty flexible just let... Since we are leveraging these hyperscalers, but the the client has always the option to to decide where it should be hosted. And we are currently also, basically enabling the solution so that we can host it in private cloud environments as well to, have, yeah, this this extra option for for the client to choose from if we want to go, with one of the hyperscalers for the public cloud or rather private cloud deployment. Yeah. But it was... It is always a software as a service offering. Yeah. Great. Thank you for for that. I I think we've received the the questions that we... We've got already. But, yeah, thank you so much, Frederic and Sunele, for diving into the details this morning. For everyone attending, thank you so much for joining us this morning. Keep an eye on your email inbox. We will be sharing the full webinar and demo recording. If you are interested in continuing the conversation as well, you're more than welcome to get in touch with Sunilia as well. I'll also pass his details along. But other than that, have a lovely Wednesday. Thank you again, Sunilia and Frederic, and I'm sure we'll all chat soon. Thank you so much, everyone. Thanks, everyone. Have a lovely day further. Cheers. Cheers. Thank you.