[Music] please do post your questions in the the q a or the chat and we will answer them when we see them or during the q a um at the end of today's presentation and so i'm also starting to think that we need to keep the full um hour today so maybe we should go ahead and get started all right i'm ready if you're ready yeah let's go all right thank you lisa and uh thank you all for for joining us today uh i am aaron calloway i'm joined by by chris hamrick uh chris do you want to do a quick intro sure good morning good afternoon everyone my name is chris hamrick and i'm a solution consultant here at servicenow awesome well thank you chris and as i mentioned this is aaron callaway i'm director of global risk and resiliency transformation and we're here to talk to you about all the awesome new capabilities coming out in the latest releasing in quebec so excited to walk you through that and also talking about some industry trends as well so here we are new stuff awesome capabilities being released in the store it's really great to be part of such an innovative team and and customers and and colleagues bringing all these things together and it really is because of not just our team but because of our customers it makes our products great uh we really value the input and the collaboration in the community that we have here with servicenow and within the servicenow bcm capabilities so here's what where we are today um kicking off some of the business continuity management and chris hamrick will take you through a live demonstration of the items to come and we also will be joined by uh ashwin to walk us through uh future capabilities as the bcm product manager in april first we'll be talking about the cyber security accelerator and then in april 8th awesome due to talk about the regulatory change management and all the additional capabilities that are released with that as well and then finally what we have on the roadmap right now is april 15th talking about audit policy and compliance so as i mentioned i want to talk about some industry trends so i think we've all been on zoom calls a zoom birthday party zoom happy hours we're probably all zoomed out um and you know everything still as it says still looks slightly different and the world is slightly different and i think there's some um you know i'm a silver lining type person i believe that there's a lot of lessons learned some good things that have come out of this um you know unfortunate pandemic and i think a lot of us are probably talking worried about are tired about talking about the pandemic and about things moving forward but some of the positive things that are coming out of it is that we've all been able to react and respond we've all been able to uh adjust and to keep businesses going and to be probably more empathetic towards our colleagues and and how people are are working through these things everyone has their different struggles and everyone has different ways of working through these these things but what i'm also seeing within the folks that i talk about and within some of the executive briefings that i've been been in is that companies are open for change right it's it's open right we want to figure this out where's the lessons learned coming out of this people are open um to do things differently and that's also really hard is change is hard and over the years being in the consulting world uh one of the books that i've read was the innovator's dilemma and really what that talks about is becoming change agents and some ways of becoming a change agent includes a crisis um or a pandemic who knew that a pandemic would would come around and and have it have it last uh you know it's a long during enduring situation but something that's wrong as they say it takes 30 days to change a habit well you know we're in this pandemic for for much longer than that and habits have been changed the other thing that happens is someone has come and gone in an organization someone gets fired someone gets hired that causes change and then finally system implementations and and the whole process of a system implementation really encourages change uh within organizations and so we want to look at these things and how can we take advantage of some of these difficult situations that we've all been into and and um you know move forward so you're all aren't alone i like to um provide some facts with some of the opinions and anecdotal information that i've seen and this coming out of gartner is that they're saying 69 of the board of directors indicate that they're going to accelerate their digital business well that to me sounds like a lot of change right moving from paper-based or informal processes to digital processes that help um build efficiencies and accountability within organizations well if you're doing that within your business doesn't it make sense to do that within you at the resiliency of your business how can we work together with these larger corporate initiatives to make change happen into building efficiencies and to build in continuity and resiliency within the fabric of your organization and that's what we do within servicenow we are a workflow tool we build we digitize processes another piece of fact that i like to bring the table is this is was completed by boston consulting group i've seen similar analyses by mckenzie and really talks about resilient organizations come out on top and this is probably not a surprise to you but the more resilient you are the more that you understand your business and what's critical the quicker you're going to be able to react and respond to a bad situation right you're going to have information coming in quicker you're going to be able to identify how that situation is affecting your business and what needs to be addressed first and because we plan for it we exercise for it and that will allow us to start the healing process or the the recovery speed that much quicker and then as we come out of it we're going to be able to innovate where other companies are just struggling to to get back to where they were and so that's the big difference between a resilient organization and an organization that may not have the emphasis on it and then i just have a couple more slides here and i'll pass it over over to chris but this is how we see it happening and how some of the innovations that we're bringing to the market within the servicenow business continuity management arena is that we embed resiliency into day-to-day operations so if you look on the side here's just a sample of some of the servicenow capabilities from it service management to security operations to customer service to financial operations management so the existing capabilities span it to operations to human resources and when one of those areas within the business kicks off a workflow we blend in risk and resiliency into those workflows so if someone wants to kick off a new application because it's the right for the business we insert a resiliency piece to that workflow to say hey does this application need a dr plan or how critical is it where what are the upstream and downstream effects of this application goes down so day one we're thinking and talking about resiliency similar if there's a new process that comes or go with within an organization you buy a new organization or a new entity you're trying to transition in all these workflows that the businesses run on today will have a little bit of resiliency built in which is really what we're talking about is it's part of the fabric and i'm just going to leave leave you with this and then have chris show you the nice bright new shining capabilities within the business continuing management capabilities but here's where you all can join us so there's a ton of information that's out there today within the risk business unit that business continuity falls up falls under look into our community section look into our ask the experts there's just a plethora of information that's generally available for or for organizations and people that just want to learn more or they want to figure out how they can automate and digitize their bcm processes on an enterprise-grade platform such as servicenow so i will be monitoring the chat while chris takes over so chris i'm going to hand the baton per se over to you just a few states away and if you could uh take us through the new bcm capabilities perfect excellent thank you aaron and good morning good afternoon everyone on the line with us so again my name is chris hamrick and i'm a solution consultant here at servicenow and as aaron mentioned you know we're really excited um to talk about the new features that were recently released as part of quebec and obviously you know business continuity is a very hot topic right now and you know all the recent events going on are are proving how critical it is to have uh tested resiliency plans in place so we're going to start off today by talking about what's new with our business impact analysis and the business impact analysis is is part of that that assessment process so it goes hand in hand um with our other risk assessments that are going on across the organization and the idea here is really to identify our most critical services uh processes assets so on and so forth and really start to understand how how an impact to those functions is going to impact the greater organization so with quebec we've added quite a new features um with within the bia and mainly around technical impact assessments so the first feature is really geared around understanding you know how critical data is to the organization so what we've done is we've built a recovery point objective also known as rpo or a data loss assessment and this is really going to be leveraged to ensure that the maximum total data loss for a particular function or asset is not exceeded and we generally are going to conduct these technical type assessments on our most critical uh technology assets or configuration items the next key feature is really the ability to also classify and select the impact on data confidentiality integrity and availability the third key key uh feature is uh additional flexibility within our dependency group so as we as we assess various dependencies on critical assets we've provided a very simple way to modify whether or not in an impact category needs to contribute to recovery time objectives or recovery point objectives and then last last but not least we've also provided some capabilities to archive your bia so as part of that bia life cycle you may archive legacy legacy bias as well so we provided some of that feature out of the box as well so now what i'm going to do is it will actually jump to the live system here and i'll walk you through what some of those new bia features look like so you all may remember our our new bcm workspace which was released uh earlier uh or last fall as part of paris so same great workspace uh user experience so i'm gonna jump right into a business impact analysis that is really focused around assessing a key application so in this case we're assessing our sap crm application now within this bia you'll notice we've added some additional metrics within our impact assessment result card here so when we choose to do a bia if we choose a template that is focused on a assessing in a technical asset we will now present some additional rpo assessment capabilities and as part of that we also will have an updated results where we can start to see what is that recovery point objective and then as an admin a bcm admin we may also need to adjust that rpm so traditionally your bia focused on business processes and business services that's really going to focus on your traditional impacts that you see that's that's following industry best practices so that's going to focus on things like revenue impacts reputational impacts legal impacts so on and so forth and what we're doing here and i'll just complete one of these is really identifying the disruption duration so at what point is it going to be a low impact minor impact high impact so we'll just go in and we'll select some options here so maybe we'll say 24 hours is a low impact but as the disruption goes on you know we're going to start to see greater impact so maybe at one week's time when we look at revenue impact for this particular application it's going to be a high impact on the organization so we still have the same rp rto impact questionnaire as part of the assessment you'll also notice we have the rpo impact assessment here so this is where again we're really going to focus in on those those key assessment questions um to evaluate um and ultimately determine the recovery point objective so how how critical is the data what's the value of this data so we've added this out of the box and it does come with some standard type questions out of the box as well but as an organization you can expand on those types of questions to meet your specific requirements so we may look at you know data value for example what is the value of this data and again we can go in and respond and we can say well for this particular application the value of this data is going to be pretty pretty high so we may say okay this is this is important data to the organization and we may complete that the second question that is commonly asked by organizations is how frequently does the data change for this asset and this is really going to kind of be leveraged by our it groups that way they can compare um you know what type of backup backup and recovery policies in place are we doing replication for the underlying infrastructure um hosting this particular application so all of this can be used by other teams as well so we can go in same type of response we'll say what's the data frequency change we might say you know that's medium it changes but it's not changing rapidly in our environment so again we'll say that now you'll notice as i've started completing some of these assessment questions it's started to populate our metrics so we have our recovery time objective that's based on that that maximum tolerable uh tolerable impact um and then we have our recovery point objective so in the background we have some logic that's that's calculating you know what that rpo should be based on our responses to the data value in the data change frequency question and again that can all be adjusted to meet any specific requirements now in addition to this as i mentioned before we're also going to capture those those key cia type type details as well so within our details you also notice down here we have our options so we can actually determine you know what is the data impact for confidentiality so again we can start to specify this and populate this as well integrity availability so on and so forth now again this type of information is going to be very critical not only to our business continuity and our disaster recovery teams but it's also going to be leveraged by our it support teams as well again understanding the value and how critical a system is and the data stored on that system is is is going to be very important to the organization and then last but not least within our dependency assessments as i mentioned before we've added the capability to go in and determine what types of dependencies are contributing to a recovery time objective or a recovery point of debt so essentially in the bia we want to understand our dependencies and we want to specify whether or not if we lose a particular vendor or we lose a particular server you know how quickly do we need that that item recovered it now for some areas like if we were to look at hardware you'll notice that we can also specify a required data backup so even though we're doing an rpo assessment on this particular application we may want to specify particular uh recovery point objective for our hardware as well so these are really the the key features within the bia now if i go ahead and we'll just continue this through the life cycle so i'm going to go ahead submit this for approval and we'll approve this you'll notice that my functional buttons are updating based on where we're at in the workflow so my state now is in an approved state and you'll notice now we have the option if we choose to do so to actually archive this bia so essentially we're not deleting it or removing it from the system we're going to archive it that way we have it for historical purposes or for audit purposes as well now how we manage this is quite quite simple and it can be done by our business continuity management admins so i'm going to quickly go in and show you where we would make some of these changes so we're going to do this into in primarily two areas so the first is when we look at our various templates um in in uh in context of the bia we may have an application technical impact assessment a business process assessment a workplace assessment so on and so forth so this is where we're going to be able to determine the types of impact categories the dependencies that we want to assess and then we can also go in and specify whether or not we want to include the ability to analyze you know confidentiality integrity and availability of information as part of the analysis you'll also notice that for each template we're going to specify the primary element that we're assessing so this is really what's going to drive whether or not we include the rpo assessment as part of the bia so if we look this is actually pointed to applications so if i go and look at where i manage that element definition in the system there's a simple field there that says does this require data backup yes or no and if it is yes then we will present that rpo assessment as part of the bia so pretty simple straightforward for our bcm admins to manage manage those features and functionality so now i'm going to jump back and now what i'd like to do is spend a little bit of time talking about some of the new planning features that were released so the first feature that that we've released is the ability to really focus in on how you want your plan to flow and we refer to this as kind of our plan authoring type and really the goal here is to be be scalable to meet different program requirements as well as work with work with programs that are are kind of just getting started in their journey or programs that are at a very mature level so the plan authoring gives you that flexibility without having to make a lot of configurations so basically what that means is may have a program that is is just getting started and they're not really ready to you know uh leverage leverage data on the platform or you know use a a relational database they may just want to document document their plans and what they're going to do at time of an event so we'll give them that option to simply say we just want documentation capability for a program that is you know more mature they may be focusing on how do we react and how do we recover during specific scenarios um so they've they've built out their program they understand what's critical and now they're focusing in on different scenarios so how do we recover if we have a pandemic scenario how do we how do we react and recover if we have a cyber event and so on and so forth so a mature organization is going to be planning planning in that way we've also added some ability to archive our plans so same type of feature you saw with the bia we can now archive archive our plans and store those [Music] store those in the system last but not least we've we've made some out of the box linkages um tighter alignment between what we're identifying as part of the bia and what gets ported over into our plans as well as a closer linkage between building out scenarios and strategies and then defining specific recovery tasks for those specific strategies so a lot of a lot of great planning features here as well so again we're going to jump into the system and i'll show you guys what that uh what that looks like so we've got a plan here this is again our sap this is a disaster recovery plan but keep in mind the features are going to be be able to be used regardless of the plan type um so whether it's a business continuity plan a supply chain continuity plan a crisis management plan so the first thing that you'll notice here um we'll go into the scope of our plan is that now when we add an application to our plan we're going to bring over some of the some of the key attributes that we identified as part of the bia so our recovery time objective and our recovery point objectives and you'll also see the record so what was the most recent bia that was completed and approved and that's what's going to drive what you see here and then obviously that information is going to be leveraged to prioritize your recovery effort so you may have a plan with with a scope that includes multiple services or multiple processes or applications and we're going to want to know that detail and information to help us prioritize our recovery so that's the first piece is bringing in that type of information the second key thing is looking at our lost scenarios so we rolled out this functionality with the paris release where you can build different scenarios and have various strategies so if we go in and we look at loss of business applications for example here you know one we can see all the related asset dependencies so within the scope of the plan you know when we talk about loss of a business application what are those dependencies or when we talk about loss of a location what are those locations that we physically depend upon so now we can build out our strategies so we had this capability before but we've expanded it so we may have a strategy that simply open up a open up an incident ticket or start the process to fail over or initiate a work from home strategy whatever the case may be now when we look at the particular strategy here we actually have the ability in addition to capturing all this detail and information that you see here we actually have the ability to create specific tasks so again a mature organization a mature program you know they may have you know those those standard tasks that are going to be executed regardless of what caused the event but you may have specific tasks that you execute for a particular scenario or a particular strategy so for example the business may have different tasks or a different way of responding if it was an i.t outage versus if it was a fire you know initiating a work from home is gonna is gonna have certain set of tasks that need to be performed versus if you lose access to your network so this gives you that ability to really kind of build out those strategies but then at the same time capture those specific recovery tasks so now if we actually look at this particular task it will actually default and assign the recovery strategy associated to that task and again this is going to be leveraged from a reporting perspective it's also going to be important when we actually activate the plans you know what scenario is causing this this invocation and what strategy are we going to execute now we can start to apply uh filters in a manual or automated fashion that says hey you know based on this scenario based on this strategy show me the task that i need to execute right now so that is really the key feature and functionality and again i'm going to go back here and i'm just going to kick this through kick this through the the workflow process so we'll go ahead and we will approve this and again you'll notice a couple things we have that option to archive archive our plan and store it for um you know historical purposes so that is um the planning capability and again i'll show you how we can manage some of those components from a bcm admin perspective so i mentioned before you know we added the capability to go in and determine you know the plan authoring type so this is where we would be able to say well again we're just starting off we just want to get some plans in place we have some word documents and we want to document that information in the system right now today and then we'll move we'll work towards you know continuous improvement so you may say we just want to leverage documentation so instead of having to configure the form in the layout it's simply a drop down option and you can pick that and that's going to dynamically change what you see when you build a new plan off of this template or you may say hey we we approach this from all hazards approach so regardless of what caused the cause the the incident where or the reason why we've activated a plan you know we're going to perform the same task so maybe we just want to document the scope what's critical to this plan any supporting details and then document our task or you may do you may just plan per scenario so again the idea is giving you that flexibility to really kind of hone in on how your organization plans and align with your level of maturity so going back the last area that we really want to kind of focus on and what is what is really important to organizations is you know the ability to exercise and the ability to have confidence in your plans at time of an event so when you activate activate in real time so now we'll look at you know what are some of the new features um that we're releasing as part of crisis management so one of the key key items in this release is uh giving you the ability that when you create an exercise or when you create an actual event the ability to identify and assign impacted items such as an it asset or a business process or a service and then let that drive the scope of the event so what you'll see here in a moment is the ability to say you know we know we have an incident and it's impacted this asset now the system is going to be able to look at that and determine what plans you need to activate and then we've we've changed the layout a little bit to present the data in kind of a hierarchy of impacted assets activated plans and then recovery tasks that you need to perform we've also we've also added the ability to create ad hoc tasks so during an exercise we may have tasks that were unplanned for so now we can create an ad hoc task we can associate it to the impacted dependency um or associated to the plan so that way during the heat of the event or during an exercise you know we're not losing track of any work that we had to do that we didn't we didn't account for previously we may also create remediation tasks so you know again we may be going through an exercise we're documenting any any issues areas for improvement and we may want to track those as ad-hoc event tasks and they may be classified as as remediation tasks as well so we've added some additional uh additional capability there as well so now we're excited to jump back into the demo here and we'll show you kind of how that looks so let's go ahead and for today we'll start an exercise so we've also added some additional ability here as well so when the users who are responsible for creating and managing these exercises when they create an exercise we actually will present them with this pop-up here where they can start to capture certain details pertaining to the event so we'll go ahead and say this is a new recovery exercise we can select our method here as well so we've expanded the options here also so um an exercise can can be any number of things so for business continuity we're doing a lot of walkthroughs and tabletops and simulations for dr exercises we're doing you know fully functional failover so we're actually failing over from a primary to secondary then we can go ahead and we can select what's the plan start date and then we can add any additional description here so as part of the exercise again we're still giving you the capability to capture all the key details that you need for an exercise so assigning it out completing all of your planning uh details so when are we planning to execute this exercise who's going to be approving this from a from a pre and post exercise so that's where we have kind of our result approvers come into play and then we can define our scope so it's already set to functional um that's that's based on our choice on the previous screen we can document all of our goals and objectives so this is really nice because within a single details tab we can really collect all the detail and information we need for our exercise scope and objectives document as well as our exercise results and for those organizations that need to provide this type of evidence for internal external audits you know we can really point point those those teams to uh the details or we'll be able to provide rich reporting and dashboarding that are showing us you know what was tested when it was tested what were the results what types of exercises are we doing so on and so forth so this is where we will document those those results here so in the paris release um we provided the ability to simply go in and say here are the plans that we need to activate and at time of a real event you know being able to quickly quickly do that you know was advantageous um now we've added the ability to say well let's think about this you know most of times it starts with within with an impact whether it's a location whether it's a business process or a service so now we can actually go in and we can say you know what's what's actually been impacted um you know there's opportunity to automate some of this as well and integrate with other areas on the platform like incident management for example but in the case of an exercise we may simply say what's been impacted and that's where we can go in and we can select and we can say okay you know we know we have applications that are being impacted now this is going to show me all of my applications so i can go in and i can do a quick search so maybe we want to look for those sap applications and maybe we want to say well we're having an issue with with our sap financials and then we can go ahead and save that and you'll notice that it's going to add that impacted application to my event now the second piece is what plans do we need to activate based on those impacts now i could have skipped that first step and i could have gone directly to adding a plan that would have given me the ability to simply click and say show me all the plans uh that that are in my in my organization and then i could just pick and choose now if i go back maybe i just want to see the plans uh associated to those impacted assets so now i could go in and i could say okay you know in this case we only have one impacted asset in real life you know we may have multiple impacted assets but for today we'll just pick our sap financials now what's going to happen is when i click next it's going to show me what is the plan associated with that impacted asset so again imagine we had 50 impacted assets we'd be able to see all of the related plans and then we can select the plan and we can add that to our event so what that does here is for each impacted asset we can now see what's the state of that of that asset so it's currently has not not been recovered and then we can show that hierarchy view so the impacted asset we have our sap disaster recovery plan that we've activated and then here are the tasks that we need to execute so it's a nice view and it's going to really allow you to focus in on recovering recovering the assets that have been impacted that led to the activation and then from here we can drill into we can drill into uh the task and we can work the task here so we can assign it out so it may be assigned to someone already we could assign it out to a servicenow support group so again maybe database team is going to work on this or a network team is going to work on this task we can track when did we start this task how long did it take us when did we end it and then we can describe any other details as well as attach any evidence so a lot of times and exercises we need we need that evidence for audit purposes whether it's a screenshot that we actually made the dns change and we're not just saying we did as part of the exercise so we can track all of our tasks as we start going through tasks and closing those out that could then roll up and tell us what's the state of the plan and then ultimately what's the state of the impacted asset and then we can track again how much time it's taking us to perform each of these tasks and ultimately recover the asset and then that's going to be critical critical metrics to be able to determine whether or not we are in compliance with our recovery time objective requirements so we're looking at what what our capabilities are what we can actually achieve and then last but not least the ability to add an ad hoc task so again during an exercise there's going to be things that come up that we're not accounted for and we don't want to lose track of that because business continuity management is always about continuous improvement and exercising your plans is a big part of that so we can document and track these event tasks and again we may want to add you know a task type to specify whether or not this is a truly an ad hoc task a remediation an after actions task or or even potentially an issue that we want to track as part of as part of our exercise um so that is uh some of the new capabilities with um with our crisis management [Music] application that just just was released so that takes us back to the powerpoint and um that really covers um all the new key features and functionality that came out as part of quebec just last week so now i'll turn it back to to aaron and i believe we may have uh ashwin on the line as well he is our business continuity uh management uh product manager who will also be able to walk us through some additional features and capabilities that tie into our overall crisis management strategy awesome thanks chris and uh so we don't have astronaut online yet but um we do have one question as came across and it was can the relationships in the dependency assessment of a bia be automatically populated from existing cmdb relationships um that's a that's a great question um and uh that is actually something that is currently in progress so if i understood the question correctly it's it's essentially can we reuse the cmdv dependencies um and that's really that's really one of the the the benefits of the platform and being able to leverage all of that data so um in our next release also part of quebec release scheduled for june of this year we will actually have that capability where where we can reuse and pull in those dependencies because really two things one we really are working towards the configuration management database or your cmdb being the gold source of of data as well as as various dependencies so we want to leverage as much of that data organizations doing service mapping we're going to be able to uh benefit from all that hard work as well and we're going to be able to pull those dependencies in in addition to that we still are going to provide the flexibility for business continuity teams or disaster recovery teams to manually add additional dependencies so that way you kind of have a business continuity view into uh your dependencies whether they are done manually or whether or not they're coming from coming from the cmdb or service mapping and the reason we do that is because you know with within our dependency view in the cmdb this is this is kind of you know it's showing it's showing anything in in everything related to the various assets um so it's it's kind of a uh day-to-day what what does the environment look like today whereas business continuity you know we're focused on you know what do we need at time of time of an event as well so there may be additional types of dependencies very specific to resiliency planning and the beauty again one of the key differentiators is that you know we could then leverage workflow capabilities so that way if we're defining additional types of relationships we may want we may want other teams to have visibility into that you know our change management teams that way they may correct or enhance uh the cmdb dependency view based on information coming out of the business impact analysis so it could almost be kind of a a two-way street as well awesome no thanks chris for that and uh we have another question that came in um it looks like each individual impacted asset from a plan gets their own separate activated plan for all the recovery tasks associated is there an approach to take if the plans aren't structured that uniformly for example where different tasks within a plan target different scoped assets um for that plan i can yeah if you'd like yeah so so no i i if i understand the question um you know i i think and and we hear this from a lot of organizations you know different types of tasks you know whether they're their task associated to a a particular scenario and strategy whether it's tasks that are associated to a particular asset so maybe those are asset specific tasks or kind of your general plan test so we see organizations uh creating and managing different types of tasks now the challenge is is you know how do we bring in all those tasks how do we categorize those tasks how do we prioritize those tasks so the answer would be yes we we can have some logic um you know or leverage you know workflows business rule capabilities on the platform to say you know you know if if all of these if all of these impacted assets are coming from the same plan and there is no you know differentiator between what tasks are applicable to what asset then we could have that we could have that logic in place that say okay you know roll this up um because they're we're we're dealing with the same activated plan and the same set of tasks um or um you know if we are if we are identifying a specific strategy per task we may want to also apply some logic that filters out our tasks based on based on the strategy based on a scenario for example or you know you have asset specific tasks as well so maybe we have some plan tasks and then those tasks that are associated specifically to to the asset that's that's been impacted so short answer is yes the the the capability is there um you know to meet different different requirements and how you want to uh build and manage and prioritize your your recovery tasks awesome thanks thanks chris um yeah so the uh the feedback was yeah that's exactly what i was wondering thank you so uh thanks for uh for answering that um any other questions and if not we'll probably uh close down all right we got one last one coming in um is rta still part of bcm in the new version so recovery time actual it is it is yes it is um so we're still we're still capturing um recovery time achievable that way you know we always have um insight into are we meeting our our business requirements so we're still tracking you know recovery time objectives recovery time achievable as well as rto gaps so that way from a a program management reporting perspective you know we have clear insight into not only the gaps in our ability to recover a particular asset but also insight into whether or not the rta from a dependency is going to impact our ability to recover a particular asset as well so we still do have that metric and that's a that's a key a key piece to being able to understand our our rto compliance as well awesome thank you chris um and uh thank you lisa and teresa for helping us coordinate this ask the experts call we will end it now as we've addressed all the questions and feel free to reach out to the community community and those additional links that teresa put into the the chat area and as as always open door policy if i can help address any questions as well but i want to thank you all for your time and uh look forward to seeing you again on the next ask the experts edition thank you all thank you chris