good afternoon thank you for joining us today Carol technology would like to welcome you to our service now Federal Tech talk assist with Erp Cloud migration and modernization using service now low code apps joining us today with service now we have Parker Lee senior solution sales executive and Daniel bowling senior solution consultant while I go over a few housekeeping items please take a moment to answer the polling question questions on your screen please note that all lines have been muted to reduce any kind of background noise during the presentation if you have any questions throughout the webinar please feel free to use the Q&A feature on the bottom of your screen and we will do our best to answer by the end of the presentation or we'll follow up with you offline following the webinar this webinar is being recorded and a copy will be emailed to you just to tell you a little bit about koft we are a trusted government it Solutions provider supporting public sector organizations across federal state and local government agencies including education and Healthcare markets at this time I'd like to hand the floor over to our speakers Parker the floor is all yours excellent thank you very much um really appreciate everyone joining us today uh Parker Lee Senior Solutions executive here at service now I specialize in helping health and finance related agencies modernized Legacy applications um automate manual processes and centralize all their important information for decision making today we're going to be talking about clean Core enterprise resource planning with app engine um specifically through the lens of sap migration um but this also applies to any kind of enterprise resource planning that you might think of um so I'm actually not as familiar with zoom let me see if I can see the results of the Q&A looks like I can um excellent well thank you all for answering this this really helps us um uh understand the typee of conversation we need to have some people may or may not be as familiar with Erp um looks like we've got some folks who've been users of of service now uh we have one Advanced user but some folks who have some experience as a developer and it looks like we actually do have a couple of folks that have actually used an enterprise resource planning tool before as a user or as a developer admin um that's very very helpful for us to know so to kind of get things started um we will go ahead and uh talk a little bit about what enterprise resource planning is um it is a very very broad term uh what I like to describe it is anything within what we would call the back office um so in a commercial organization you have the front office which is where your customer relationship management or your CRM lives so that's sales and marketing and customer service and those different organizations back office are all the underlying process that make up sort of the logistics financials of your agency so this can include supply chain you're managing um any kind of asset moving through warehouses or manufacturing or um any you know facilities or asset management but it could also include your financials so your balance sheet your general ledger your income statement your budget preparation um some people would consider HR to be part of Erp because people are another resource human capital um but Erp it's everything that sort of handles those back office functions of tracking any person place or thing that mov moves through your organization that needs to be tracked um and so sap or excuse me Erp systems tend to be very very big lots and lots of data and extremely complex very very complex over time um as people uh take their existing saap or existing Erp or existing Oracle systems um and they customize um it's also often very very expensive to update uh which means that most Erp systems are usually pretty old they could be 10 20 30 or even 40 years old um and so one of the biggest challenges we see specifically from an sap perspective is that the current sap Suite 7 software uh will actually no longer be supported by mainstream maintenance in 2027 and then uh optional extended maintenance of 2030 um and so 2024 is next year we're only about three years away from that um the actual migration to the modern sap 4 Hana could actually take several years and several millions and millions and millions of dollars um and so this natural upgrade cycle kind of represents a clip for anyone that's on sap um so some of the folks on this call are probably familiar with some of the challenging realities of managing sap um because usually sap is procured and then it gets customized and these organizations write lots and lots and lots of custom code um to handle things like bills of materials or warehousing or changing their income statements or Finance statements or things of that nature um and they tend to be this very very sort of Legacy experience and so the biggest challenge uh is the difficulty in innovating the difficulty in actually updating these customizations or even just modifying you know you need to have someone that is a pro developer that can write custom code against your sap um but the problem is if that person leaves then you have this sort of technical debt that's kind of sitting there and eventually this sort of continues to snowball and snowball a lot of times this technology is fairly inefficient or fairly Legacy um modern ARP processes require connections between all kinds of different system of Records but Legacy technology doesn't tend to keep up with these Demands a lot of pieces of in sap um were actually Acquired and so they don't necessarily sit on the same code base or the same data model um and they're all storing data kind of in these silos which results in lots and lots of manual effort to rectify the data unite it or manage it um so you don't have that situational awareness of um all of the information being in a single place to kind of see uh what it is that you need to learn to make these big decisions and then finally poor experiences a lot of the sap screens are not meant to be customized at all which is very very different than modern technology especially low code technology like service now where modifying a service now user experience is a simple drag and drop process um with sap there tends to be sort of one way to do things one kind of experience and there's a lot of headache involved in trying to change that experience fit your specific use case and so modern Erp operations require a single layer of action and engagement um so we tend to see that you're not necessarily ever going to rip out your Erp and replace it with a low code platform but what you can do is actually extend it using a low code platform to improve all of the three things that we're talking about in this slide so why is it so difficult so with sap and with Oracle and with really any Erp we tend to have these core modules and the core modules are things like bill of materials warehousing general ledger things that are best practices within the industry um but as we know business processes and business requirements tend to be bigger than just these small core modules or not these small core modules these individual core modules and so we tend to see either Point tools crop up to address the missing pieces of those core modules or we see an overloaded Erp core that's full of customizations where I needed to write a custom script to modify my bill of materials or I need to create a new custom screen in HTML because now we have a different group of people that needs a different experience or different buttons um I'm creating new data fields new data models and eventually it creates a great deal of clutter the challenge is these customizations don't go with sap when you move to the cloud and when you move to bana and so they have to be replaced with something to unwind and refactor all this custom code dependencies and migrations would take literally thousands of M days and hundreds of thousands of people hours so we have this goal of we have to get into the cloud we have to move to Modern sap we have to move to Modern Oracle and we have to adhere to this clean Erp core because everything else is not going to go with us so how do we how do we get all these customizations out of sap in a way that doesn't denigrate our functionality and a way that's future proof and so that's really where service now comes in so service now specifically with sap has a way to scan your sap instance and identify the customizations that would be best suited to actually go to service now um so just to back up a little bit what exactly is service now service now is a single low code platform for workflow automation so you may actually know us from our it service management you may have heard of our HR capabilities but everything we do is on a single Gartner quadrant leading low code no code platform our most our second most common solution within the federal space is actually our local code platform being used to customize and configure custom applications um so across my organization we have groups that do investigative case management using our loow code platform we have people that do travel requests we even have scientists that do tissue request samples um on service now so any kind of custom workflow that you could think of government organizations are probably doing it on service now and so what service now can contribute is instead of refactoring all those heavy customizations by writing more code you can leverage a low code no code platform hook into the data that already lives in sap and remove those customizations from sap and put them into service now in a in the form of a low code application so you're actually retiring those customizations replacing them with lightweight low code applications that are scalable and secure and then leaving sap to do what it does best which is those core modules general ledger things of that nature um so you're not ripping out sap you're actually sort of cleaning it out and replacing it with service now um one other really cool thing you can do with service now is diagnose sap so it will actually run a scan of your sap instance and it will provide a stack ranking of the best customizations the best candidates to be migrated to service now so you could go into service now and have this sort of updated low code user experience uh build out your workflows using low code no code very very quickly and rapidly modify and create applications as needed and then just hook the data model back into sap so you might actually drive users to say a time and Reporting application that lives within service now but the data is going back into sap the clean cor module because we have to pay those people based on their time so we have to do payroll and things like that um the user may not actually know they're accessing sap data all they're necessarily seeing is service now and so once you have looked into your diagnosis we will give you this sort of Stack ranking of the customizations if there's no out of the-box solution you could digitize it using service now so our greater workflows our catchall term to build low code applications on service now but if you have a best a breed Erp that would be met out of the box you could simply migrate over there so you might be using you know might move to ADP for payroll or workday for something with nhr um or you might just be using those clean Core um sap modules for what they're intended to be done so you kind of uh Branch all these customizations out based on what they are and what they fit into so how does this actual uh diagnosis work um it'll identify and prioritize your custom code targets it'll actually look into the processes so it'll look into the logs and check uh process deficiencies what might not be automated where the most manual processes might live um and then you can actually track those sap modernizations uh with you know data driven insights So Daniel will show you a little bit of it but this is an example we call it customization mining um you can actually see the movement of actions and the movement of data through the system um so you may not be aware that you know sometimes a start and then an order goes directly to purchase order rather than going through delivery Goods movement finish interner company invoice things of that nature so this will give you the how the how things actually run within sap versus the how they should be you know what what would be your ideal process is this something that we want so you can actually start to look at um the transaction codes the business process steps and then figure out how you can sort of refine those processes um so then when you transform to that lean Erp start to look at those non-core customizations replace with your best de breed Solutions when possible rep platform the rest with low code and then leave the core Erp modules within sap where they are much much easier to migrate um so this reduces the effort it will take to move to Modern sap because all these customizations you don't have to worry about them coming with them they now live in service now they live in another Erp solution and all that's left are those core modules that you then live shift into for and so um this is the build tools we'll talk a little bit about that today um app benine studio is our main way of building low code no code applications um so when you're moving these customizations in the service now platform you're likely going to leverage app engine studio and so it's an app development experience that walks you through the four steps of creating an application the data the user experience the workflow and the security and so you can build from scratch you can use some of our pre-built templates for things like travel requests so on and so forth and Studies have shown that you can actually build these applications around four times as fast as custom code and I've actually worked with developers uh in the past uh many of them have actually confirm this four times faster um they said we built this app in half a day with service now it probably would have taken me two days to build withinn net um so you know if you'd like to talk a little bit more about why um why that actually is possible and and how that actually looks we're happy to uh take any questions now or take that offline as well so to give you a couple of examples of other organizations using these capabilities today um this is a branch of military uh you know the specifics are a little bit confidential um but they essentially use app engine and service now to help track a lot of their assets and so this is taking data not only from their Erp system but also from a few other Legacy systems that do asset tracking but centralizing all of that into a single experience so you have this Fleet Service management offer that is actually optimized for mobile so when people are in the field when they need to request vehicles or aircraft or spacecraft or they need to request Parts they have a realtime situational awareness of where everything that they own is located in the world this is obviously sample data this is not where our actual Naval uh resources are shown um and so once again instead of writing custom code or trying to customize sap to do this they used our low code no platform where it's very easy and flexible to change any workflow or change that user experience and then they're using sap for what it's intended to be this sort of system of record um with service now being the system of Engagement and Automation and this you know really would take probably five times as long to do with custom code as you could probably do it within service now another example U this is a government Defense Agency working with uh one of our partners um they created a agile layer engagement that they call sort of wrapped SAP with app engine um and so they not only connected sap into app engine they also used robotic process automation um and have uh created a g invoice so they created a central invoicing system so it sounds like you know their uh specific sap instance wasn't handling invoicing the way that they wanted to maybe it didn't follow their process maybe it wasn't centralized or automated so the invoicing system lives within service now app engine but it's still pushing that data back into AP uh where necessary the last one we'll talk about is a supplier journal entry um so once again another back office type of uh application that you probably see within the Erp they probably had to connect uh collect specific information about their suppliers that once again may not come out of the box within sap so you end up writing all these custom workflows or customizations within the data so that you adhere to far regulations government regulations about suppliers things of that nature um and instead let's put all that configuration within app engine and once again move that you know journal entry app into a cloud-based low code platform while pushing that data back into sap and making their life a little bit easier so far um so with that I'll go ahead and hand it off to Daniel thank you Parker uh good afternoon everyone my name is Daniel bowling I'm a solution consultant here at service now um and I specialize in our low code no code capabilities for building apps on service now I've worked in the low code space for the US federal government for about seven years now uh before service now I was actually a federal employee at Customs and Border Protection helping uh manage a team uh that delivered low code applications um so I'm excited to talk about service now's low code capabilities and specifically about um what all of this looks like in action what Parker was describing of um our Erp modernization assistance how we help uh connect to your Erp environment scan it identify potential candidates for um customization to bring into service now and how those get built out I'll share my screen I gra just a couple slides I'm going to spend most of the time um in the actual platform uh doing the demo uh but just to kind of Orient us we have our external Erp system in this case what I'm going to demo today is of a connection to an sap system um but you know it could be any general Erp system so Erp canvas is our terminology U for like our product where we um kind of organize all of the Erp models and create those relationships Erp customization mining is where we scan those existing customizations in your Erp environment and identify the best candidates that could be brought over into um service now to be built in app engine over here so I will pull up My Demo instance here uh in the Erp canvas so this is the Erp canvas workspace uh and we've got four different tabs over here on the left hand side uh so the first tab that I in right now is showing me all the Erp models so almost all of these were ported over automatically from an sa environment so I know we had a few um Erp uh admins or former admins or developers on the call so if you were working in sap some of these excuse me some of these model names might look very familiar uh brought over from from an sap environment uh I can open up one of these models I'll open up uh sap material stock for for example I can see some information about that model uh in in these different tabs up here I'll click over to the model tables so I can see we've got three different tables um that were pulled over as part of this model uh these names are their names in that sap environment uh so you can see that these aren't um super inuitive names uh so that's part of when we bring it over we can um actually give them more common language names easily interpretable uh by developers we can see the fields um in these in these tables so here's a good example here's what the field names are in their parent environment or the environment that we're pulling from uh but because these are default fields in sap we've renamed them over here to something a little bit more intuitive and then we can also see how the tables in this model are joined together in any join conditions that might exist for them uh those are um a lot of the models that come ported over automatically depending on which type of Erp environment you're connected to um we can create our own models from scratch where we identify which tables should be part of it and create those joints between them um or probably more frequently easier to clone an existing model and then edit it by adding more tables removing tables editing the joins um to create um create the data models here in service now uh so the data models are essentially just made up of tables and relationships between those tables to see more information specifically on the tables brought over um we have two types of tables remote tables and extraction tables uh I'll show Extra tables first because I'll save remote tables because I think they're super cool um extraction tables here um are tables that we scanned in sap and actually brought over into the service now instance um so all of these tables exist in service now we go through a little transform map that's like service now L go basically for an ETL process extract transform load where we take the data as it exists and as it's formatted in sap and then map it to an to to a table that we created in uh service now so that that data ports over um smoothly and seamlessly uh so I can open up one of those tables that sap material stock uh table and I can see all of the fields uh that rep ported over um and this is going to be refreshed on some sort of schedule uh that we want to set for how um how often that data is ported over from the sap environment into service now so these are all of our extraction tables now remote tables uh this is not us bringing over all of the data and migrating it into service now but actually just establishing a live connection between service now and in this case the sap environment uh so the actual data lives in sap but we've created kind of like a dummy virtual table within service now that mirrors that actual table living in sap but then once we have that kind of I call a virtual table in service now the remote table um we're able to actually build off of it as if it was a real table in service now um and so I'll show a little bit more about how that can really play out but I it's a super cool um concept it's a table that sits in sap but we're building we can build visualizations off of it we can build automations off of it um we can build off of it in service now as if it was actual service now data so that's what all of these tables are these are all Erp remote tables uh that are actually sitting in uh service now we have a link to actually view any of the tables that we want to uh which model they're part of uh so I can open any of these up and again I see the table Fields um that are sitting in sap but we're connected to um via direct connection here and then finally my fourth tab this is just a check of all the Erp systems so you can connect multiple different Erp systems I just have the one sap um system connected we can see that it is successfully connected latest heartbeat was earlier today uh just to check on the status of those uh Erp systems uh so this is kind of um like a just kind of documentation around the data models and the data tables that have been identified in the sap instance and either ported over into service now or a remote table has been set up um and how those tables are related to each other that's what the Erp canvas is all about so it's kind of like the foundational building block of connecting service now um to that Erp environment I'm seeing a question from Matthew in the Q&A what are customers using to integrate back to sap and other Erp platforms how is governance handled with existing ipas platforms and standards um we'll make sure we come back to that at the end of the uh demo here I have a slide that goes into a little bit more technical detail about how that's accomplished good very good question uh so that was Erp canvas the next and this is where it gets a little bit cooler in my opinion my opinion is the Erp customization mining uh so I have a little bit of an example kind of like process diagram of how this might flow um we have a an SI and Ellen who's like at the you know within the organization is managing uh the SA sap migration has to move from sap ECC to S4 Hana um but you know like Parker was mentioning some of those customizations built on sap ECC won't migrate to s4hana automatically so we need she needs help identifying where what those custom customizations are and where they exist within the sap environment um and then you know determine whether or not using a different platform or new capabilities is suitable uh to help bring those customizations out of sap and into a new platform uh so that's where uh we scan the instance we get the sa the um the Erp canvas set up um and then identify customization candidates to build out in service now um to assist with that sap upgrade and that's where I'll hop into Erp customization mining dashboard uh so this happens automatically based off of the connection with your in this case sap environment and the scan um that has been done of all the custom code within that sap environment we can see we have uh different candidates different customization candidates that can be reviewed um to potentially be brought out of sap and into service now uh so grouped into some different modules um by those Erp modules so these might look again familiar to some of our sap efficient autos on the left hand side I'm going to click on this candidates view to just see all of the um individual customization candidates that we're going to be evaluating here and importantly we have the potential level uh so potential level high means it is it looks like a very good fit to bring into service now and that's primarily based on the uh data that is required to build out this customization that was identified in sap ECC um so in this case I can click on this uh this candidate and I see uh the description of what it does it reads the bill of materials item um a few different um it just just kind of reads a few different uh modules within or tables within um the sap environment within the production module I can see the scan results of which um tables are required to build out this functionality the similar functionality and service now I also have usage information which can be really important especially like for prioritizing which customization candidates you want to build out first so in this case we have got 22 users of 10 of them are active or have used the application recently and 12 not recently we can see maybe if we pick this candidate to uh bring out of sap first we can see some other similar candidates but then what I think is probably the coolest part of this is the actual recommendations so uh we can see it's recommending use a remote table to read the bill of materials data and then build an app to view the bill of materials through app engine as our two recommended actions um to bring this uh bring this customization out of sap and into service now uh so that it really just tries to make it as easy as possible for you right like um potential level so high so we've got potentially really good fit um to bring into service now with a pretty low level of effort so you can select this as a potential candidate then on the home screen again we'll see that appear in our selected potential candidates so we kind of identify a short list of candidates to potentially bring over into service now and if you're familiar with um sap you probably see how valuable this could be um it's kind of difficult to scan an sap environment and understand where those customizations are um and then much more difficult to understand what they do and if their requirements map well to a thirdparty system like service now uh so that's what this tool is all designed to do for you so the final part of the demo here let's say Ellen has selected some candidates to move outside of sap has received approval um from her manager and so she has presented those uh there um customization candidates to bring into service now uh and then a selected one to actually bring over so now we move into the actual modernization portion everything up to this point has just been um identifying what the customizations are and what are a good fit for moving into service now then when it comes to actually building out those customizations in service now that's where we pivot into what Parker was describing earlier app engine studio um and those really intuitive low code no code build tools to put that functionality into service now uh so I won't bother like walking through this whole um process flow but basically it's describing Ellen building the application that was described from the customization in um showing it to John John approving it the app getting deployed in service now and of course everyone happy at the end uh so I want to show an example um of one of these apps that was created in this in my demo instance here um based off of the recommendations from the customization mining so here we have our manufacturing operations Das board so this was a dashboard that used to live in sap um but we've got the data available to us in service now so we built that um dashboard here in in service now uh So within app engine Studio I'll just kind of really briefly go over this we've got uh four pillars of every application we have the data the actual underlying data that's powering the app experience any uh any form or screen that a user is actually interacting with like a dashboard logic and automation uh this is where the actual kind of automated process is described and then performed and security so data we have one extra table that we're that we're using here but for the most part we're using the actual um uh remote tables from sap uh for this dashboard I'm going to show an experience in a second I do want to just open up a logic and automation example in case you haven't seen I saw we had a couple people not um familiar with service now uh this screen is called flow designer and this is where this is like our no code low code way of building automations uh so every flow consists of a trigger and then Associated actions so this trigger um just run this flow uh just runs daily at noon it could be triggered by an actual event uh within the platform or external to the platform uh but what we do here um is we update disruption alert data so we we look at all of our disruption alerts um and then go through here we actually go through the um materials the stock material in our sap instance to update them with any subsequent information about A disruption alert so maybe uh we There's A disruption alert about a plant being down for two hours last night due to some emergency event that happened uh this flow would run and then update the bill of materials uh for all of those stock items that would have been impacted uh by that plant going down uh so that's just an example of a flow and how we can kind of loop through some traditional development Logic for each if then statements how that comes together fourth and final pillar of our apps are security so this is where we Define uh the different types of users that will interact with the application and then what permission each type of user should have within the application uh that is all I will kind of go into about what it's like to actually build but I'll show an example of this um example here's our manufacturing operations and alerts dashboard uh used to be an sap we brought over into service now uh so the idea here is we can Surface to the user alerts um in this case we're bringing in alerts from the National Weather Service or gdac about events that have taken place that might impact our manufacturing operations uh and we have our of course a map view showing our International uh manufacturing operations and what what's going on where uh so we can see this first one here a volcanic eruption is ongoing in Germany France Poland I can click on that and here I see uh where that event took place it's categorized as severe in the potential impact area which would be like kind of a huge volcano I feel like if a volcano erupted that actually impacted this much area we'd probably be like heading into another Ice Age or something um but customer first so uh in terms of how that would impact manufacturing operations at our hypothetical company um what we can do here is we can see more information see the source latitude longitude of the location um some Cate categorization and a description of what's Happening uh but then more importantly for us we can see which assets of ours are at risk based off of you know we have a directory of all of our um all of our assets and the where they where they live so I can click on this to see the three different plants um that could be impacted by this uh volcanic eruption and then some more information about them I can open any one of them up uh to see kind of more information about them here which product they make for example so I'll jump back to the dashboard and here are those three plants uh in our map view and then based off of the impact area so we've identified these three plants as potentially impacted so we've got suggested actions down here so we can notify uh stakeholders if I want to click notify this will automatically select the owners whoever is marked as like an owner of all of those assets so in this case these are plant three plants so it would be like the plant administrator um and then we can manually add any additional users um if we know we want to notify any additional people click next and we can actually send an email from uh service now here the subject is automatically populated with the um emergency information type what we want the email body to be and actually send this notification um to those users and we also have a another suggested action to declare a crisis event um so there's a separate workflow uh that that we developed here for what it means to declare a crisis event so that action could be triggered here um from within service now to um Mark all of these plant locations in crisis mode and then the associated like flow that happens as part of that uh one thing I think is pretty convenient uh we can edit the impact area as well so right now this is like kind of a huge impact area in my opinion for volcanic eruption uh so if we want to customize the radius there we can just shrink this impact area down save that now we only have one plant location that's actually being uh impacted by this event for pausing here uh next I'm going to jump over into the operations View so our operations view is another version of this um another view within this dashboard here we have a bunch of like visualizations um based off of the data that's actually living in sap so uh we can see our production orders by region um and then some of our production actual scheduling by day week and month here and then special orders and production plan by status year to date we also have a calendar view so we can see all of the production activities happening within any given um within any given month or week and see information about them over here uh so really the key here I mean I'm just I'm kind of showing a few different types of [Music] um types of uh artifacts that can be built out in service now um based on the data in sap but the key idea here is that you can do that you can have data living in sap or automatically ported over into service now from sap and build very nice very intuitive user experiences in service now using service now's low code no code cap capabilities against that actual really really valuable organizational data that's sitting in sap or whatever other Erp system you might be you might be modernizing um and so with that I will leave off with this slide here um again reviewing we've got that external system the Erp system canvas is kind of creates that directory I've been looking for that word the whole time is that is a directory of the Erp models and tables um that have been read in from that Erp environment customization mining is where we actually scan four customizations that exist in that Erp environment today we rate them based off of how easily they could be brought over into service now then app engine is what we build um those customizations could map to one of service Nows out ofthe boox offerings um which is great uh but if they don't if it is still kind of a custom use case uh those can be built out uh using App engine which is what I was just um demoing was a a dashboard kind of solution that was built out using App engine on service now so I think we can open it back up for questions um and while while everyone's thinking if they have any questions or anything to um to go into further I'm going to pull up this a little bit more of a technical architecture slide um but this was a there was a question earlier um that I think this this might help answer um kind of how we connect to uh in this case sap ECC and then eventually sap for Hana um because the key thing here is right we're all about enabling the modernization enabling this migration from ECC to foran um we make that connection to ECC from service now using that Erp canvas um initially through this mid server and some of the additional protocols that are used here uh so we're R into those models living in sap ECC um but then we're when that migration happens to s4a uh we're still read into those same models through a mid server um but now those where the customizations got Stripped Away um that's why we build the customization out an app engine so they're they're like front front end kind of versions and the automations associated with that customization built out and app engine are initially rooing from sap ECC um but then are switched over to s4a once that migration occurs um so that's kind of the idea is that you the data is continuing to live in sap but those customizations are built out on app engine so they're not affected by that migration got the chat up there I'll stop sharing now um we can go into Q&A mode I see some more activity in the chat and questions uh workshops that we offer uh to actually get any uh open to anyone in federal government uh employees or Partners um to actually get handson and build applications live with us we do that in the Vienna office I'll look for a a registration link to put that in the chat all right well if that um if that wraps up our content um I will hand it back to our uh host from kousol thank you team I'd like to thank all of our participants as well as our speakers for being with us today we hope this information that you received during this webinar has been helpful if you have any further questions or like to request more information please don't hesitate to reach out thank you again and have a great day thanks everyone thank you