morning uh good afternoon good evening to everyone um welcome to the what's new in business continuity management webinar I am your host Ros Norville and I am joined by Oswin Kumar who will talk you through um I'm sure you guys are very familiar with aswin so just to get started we can um start to roll through the content so as I said thank you for joining us and Oswin is the principle product manager for both BCM and Ops resz which means that he is spanning both products and introducing some really interesting enhancements for those folks who are interested in operational resilience um he is also the primary uh product owner for BCM and that's what we're focusing on mainly today um I'm the senior manager of product marketing and I cover BCM Ops res and um it says vendor risk because it's an old slide but uh third party risk management um so and a lot of the features that we're going to start to introduce um do talk to some of those Better Together stories between uh third party risk management and operation resilience based on some of the regulations that we have going on uh in the EU so I think this and the third party management uh session that are coming up later this month may be interesting for a variety of people so thanks for joining us just on housekeeping as I said everybody's automatically placed on mute use the Q&A feature to ask questions throughout the session because that part is safe for us and we can follow up as needed um if necessary um happy to have you folks uh chat talk to each other tell you where you're from um and and just uh hopefully offer off some encouragement in the chat uh because the features that we're introducing today are great after the session ends you might be prompted to fill out a short survey and we appreciate any feedback that you give us because they use that to create future sessions so as noted the uh new risk applications and updates are now available in the service now store whereas um the family releases are zanadoo which is due out in September uh the risk applications and products bring our features to Market a little bit early um so everything that we're going to talk about today is indeed available in the store today so I'm going to walk you quickly through a few of these obviously today we're going through business continuity manag on August 13th we have risk management we'll talk about those enhancements in a separate webinar again um the 15th we'll talk about thirdparty risk management and you can see the rest of the webinars that we have um and I will uh find the link but later in the presentation there's a QR code so get your phone ready um and there will be a direct link to all of these where you can sign up for each individual uh webinar we hope that you do so as I said um we do have some new enhancements that we want to talk about today and these are the specific ones that we're focusing on today um we can't talk about any futures um on this call but definitely make sure that you sign up for our roadmap sessions so that you can go over this but today we're going to talk about some of the enhancements that were brought to uh the Bia and plans um some task um automation around um your uh track and tracking your RTO your rpos um your recovery tiers and your dependencies um you know as I said Expediting those itdr plan ex executions and updates of plans with dependencies from the cmdb and looking towards minimizing the impact of a crisis event by providing greater visibility into your task execution um and multiple level of nested recovery plans which enable you to uh execute plans um across multiple levels within your organization so osn's going to go through all this in detail I will check over to the chat and the Q&A and aw if I could pass this to you for the demo there are slides that follow this will click quickly so they will be in the recording but definitely pay attention to the demo because Osa moves fairly quickly uh because there's a lot to cover um but really exciting stuff coming so a if I could pass yeah thank you um so let me share my screen and we can get started with the demo all right I hope you guys can see my screen I can okay and let me also bring up and in PowerPoint so this the backup slides we can share it with you guys after the webinar this is going to have all the screens that we are going to go over today but I'll just use some of them as uh starting point and then we can look at the application directly right so the first set of um features that we want to look at in today's webinar is the enhancements that we have done for business impact analysis and the dependency Assessments in specific under business impact analysis right so when you're doing a business impact analysis there are two major outcomes that we're looking for one is your recovery objectives right so you're looking at understanding what is your business process or your business services uh recovery time objective recovery Point objective what is the recovery tier of this item right if it is an IT asset then you would be doing it for RTO RPO and then whether it's a crownal asset or not not and then the second part of the assessment is going to be focused on understanding what are the dependencies it could be it dependencies it could be facilities it could be vendors it could be people it could be data any of this right uh the list doesn't stop there but some examples yeah so we are going to look at what are the enhancements that we did in dependency assessment so when a business process owner logs in to the system and they doing this dependency assessment for example when I'm saying these are the applications that are needed by by process then you would be able to add those applications into a category called applications itself right and uh once you add that you can build this kind of dependency with it and non-it dependencies so this feature was existing there are some enhancements that we brought to this particular functionality based on the feedback that we got from users like you guys so that's the one we are going to start with the first one is making this configurable right and then the second one is comparing the values between what is the business need and the related items committed recovery objectives uh and we can look at how this uh values get updated as well automatically as well as whether it has to be done after a manual review these are the functions functionalities let me quickly go into and instance to show you guys this part so if you see here this is an impact analysis that I have opened under the impact analysis like I said there are two different sections right so this is a business process related uh assessment so there is a recovery time objective and dependency assessment right uh RPO is not here because I decided it doesn't make sense for me to calculate the RPO for a process let's say right so I deci Ed not to do that in this particular template so the enhancements are independency assessments if I open this one you can see there are different kinds of categories that I have configured basically there are facilities vendors and then some it related ones and for applications if you see I have added some um fields that is description of use how am I going to use this application the user can fill this in um and then the user can see who is owning this particular application if it is already there in the application record which department owns this who's the business unit responsible for this Etc but if I go into a vendor fee a vendor category you're not seeing those owned by department and so on right so that is the configurations that we brought in so these fields that you add here as columns is going to be configured for every category and this can be something that is an readon field that is pulled in from this particular record or it can be something that the user has to key in here right so this is the first one that we did because many of our customers and users have said um it doesn't make sense for me to have an uh owner field for a vendor right but then I would like to have an SLA here that comes from the vendor record or if it is a location I want to have the number of users or number of uh work sheets that are needed in that location so what we have done here is we have added the ability for you to configure what our columns are needed and that can be edited from within this particular view or the list View and we have also done is we have made sure these are all reference Fields so you can go in and you can look at the dependent item and you can go into awalk and you can get the details of what are the additional details that you want to pull in right so we can look at uh the details of that particular asset that we are looking at and based on the asset that we are looking at you will be able to pull in any of these right supported by or it can be uh any of these values right so I can add that and that will get added into my record basically so we have made sure that is per category that's the first functionality the second one is when I add add a particular application the business owner who is doing this assessment can mention this is my required recovery time frame right and uh as soon as you pull in the asset what we have done here is we will also pull in uh give me a minute let me just rearrange this [Music] columns for better readability right so when I rearrange I mean when I add that asset into the dependency the user can mention what is the required recovery time frame or RTO for this particular asset that I have added here that is your Adobe Acrobat right so I'm mentioning this is 72 hours that is the business requirement but the committed RTO from that owner of that asset is uh more than that right so this difference is getting compared here basically this value is coming from the late latest Bia done on that application that is this one so we added the capability to pull in the latest business impact analysis and you can add the filter whether it has to be only the approved once or it can be inflight once as well so some of our customers said doesn't matter if it's still in Flight uh the workflow it should get pulled in some of our customers said it has to be approved V that needs to be considered so we have added that part you can it's flexible you can Define what that is and then that will get pulled in here and you can see that uh the business requirement is 72 hours but then the committed RTO from the asset owner is 1 month so there is a gap between what the business expects and what in this case the it owner or the application owner is committing and you can also see that uh this is the uh ranking or this is how the recovery tier of that particular application has been uh determined by the application owner right or the person who did this analysis so that is going to be pulled in all these values are getting pulled in from the related Bia of that uh application right so you can compare this with your own uh recovery tier and you can see whether they are in line not in line very similar to your RTO and you can also look at the other ones like um this is the required data backup let's say in case you want to determine this not many of our customers do this part but in case the business wants to dictate this or business wants to specify what this is right you can specify that during your Bia and you'll start seeing what is the committed RPO from the uh application owner or the IT team so You' be able to compare that as well even if you don't want to mention what the required data backup is you can simply add this for reference so when you're are looking at the dependencies you're not only looking at the items that you depend on but really you are looking at the uh committed values of the recovery uh the recovery tier the recovery time objective and Recovery Point objective from the owner of that particular dependent item so this has been added and similar to adding other columns for related item vaa as well this is getting added as an um related item viia uh we are we have added it as an reference column so you would be able to go in and say if there is an adjusted rtu I want to consider that instead of the system calculated value right you'll be able to pull in any of this information from the related Bia of your dependencies so that is getting taken care as well so the idea was to provide an user interface for the user where you can see what is the business requirement and what is the commitment from the dependent items owner so you would be able to do a comparison right what we have not done in this release is highlighting these gaps in maybe a red font or flag that come out as a visualization in the next release but in this release you will start seeing those committed RTO rpos and Recovery objectives getting pulled into the same screen here um so that is the first set of uh enhancements right and a couple of more points around this so whenever there is an update to the Bia around these dependencies they will get pulled in as well right that will be the latest value all the time and um you'll be able to configure a workflow where you want to send an email to the business owner saying there is a new Bia there's a new recovery time objective or committed recovery time objective for the dependencies that you have so they are kept informed of whatever changes are happening and they'll be able to do any adjustments in their plan phase based on what is changing in the uh recovery time objective recovery Point objective commitments and so on and uh when you say update dependencies this would pull in the dependencies from the cmdb as well as the updates from your related bis so that has been taken care as well uh it can be either automated or via a manual UI button so when you click on this that will pull in the latest information for the dependencies so this is the dependency assessment enhancements that we have done and we have made sure these values can also be configured in your uh PDF output right so that's been taken care as well so that's the first set of enhancements on business impact analysis uh so these are the screens that we went through uh this was really taken for backup but we be able to see all the enhancements that we spoke about here and before I go into the plans let me see if there there are any questions Ross uh or do you want to take it up a there are two there's one that says is there the visual representation of the dependency mapping for an asset slci so is there a visual representation yeah I'm I can answer that and then the next one is is the list columns set by the logged user or done at a template level so it shows for every okay uh those are the two questions so basically if you see uh in the dependency assessment there are two views right uh so you can look at uh the 360 degree view this is the view we added for showing all the dependencies uh this is part of the business impact analysis this is not the Mind map kind of view that you're looking at but you can look at all the different items that it is dependent on you can go into the related list and you'll be able to see what those items are so I can see what are those four applications that we are related to and what is the RTO of that right for example and I can also look at the vendor that it is related to uh this is a chart that we have configured but you would be able to pull it up basically based on Source or you can draw the chart that shows any of these things right um and you'll be able to see the entire set of dependencies as well the application the servers the uh that is nothing but all of these different categories there's a full list and then there that's a curated list or filtered list based on the capsule that you look at so that's the visualization that we have added uh in next year we plan to release an dependency tree kind of a visualization where you would be able to see all the dependencies in a tree view uh and that will include the it and non it dependencies right currently the cmdb dependency map shows you only the relationships between the CIS right we' be enhancing that to show the non it dependencies as well but that's not in this release that's coming up next year uh next year's release that's the first one the second one is of course the columns while while you're there for just one second someone asked if they can customize the columns for each dependency yeah so you'd be able to customize the columns for each dependency category so you'll be able to configure this it's not going to be a customization anymore right like I was showing you here so for applications Ive just configured some of these columns called owned by Department business unit Etc if they go to vendors it's completely different right synchronized on uh status Etc right so you'll be you'll be able to configure these columns this can be done by an administrator and that will be available for all the users okay so that is the enhancements on business impact analysis if there are further questions we can take it along the way the second uh enhancement is around the business continuity planning right so in the business continuity plans there are a bunch of enhancements the first one we will look at is the related items and the scope of the plan right let's look at what this is how are the things that have changed and then we can discuss the uh other features as we finish this so the first enhancement is about the items that are related to a plan so earlier we had an UI where you be able to see the scope of the plan basically these are the assets or these are the processes that are related to this particular plan and when they get impacted you can invoke this plan right that's what scope meant for us earlier we keeping that same but the change really comes up is in the related assets right so when you add an item as an scope into the plan it will get added as a primary scope item that's the type of this particular addition that I have done and then as I add this the related assets of that particular item are pulled in it can be pulled in from multiple sources right so if you see here this is getting pulled in from a particular Bia it's a downstream Bia that I'm getting pulled in from so in one of the Bas these two were related for example and that's why this is getting pulled in same way for these applications as well right in this list view where we have it as scope you will start seeing the all the assets that is the primary item that I added into the plan as well as all the related items and their latest Bia with what is their recovery time objective recovery Point objective recovery tier and so on right it'll get pulled in and uh you would be also be able to see that uh there is a new tab that we have introduced this is called the asset dependency St right here we have introduced multiple views right so the Gap in this particular view was that when I look at multiple items that are primary and there are two related items right so I don't know which one is related to these or if both are related to both of them right so we just have a list of all the items we don't know the connection between these related items and the primary items same thing goes with applications I don't which process is this particular application related to is it related to only one app one process or is it getting related to two processes that are part of this plan or services that are part of this plan to address that we introduced this view called asset dependencies and the first view we are calling it The hierarchical View right so basically I added one item as the primary item in this particular plan which has related items there are 36 six related items to this and there is an red flag here uh which says this is U there is some uh warning there right so I can look at the dependencies by expanding this and I can see that there is an application that my process is dependent on and that has an Bia done on it and it has a commitment of RTO of 1 month so I have an RTO which is very aggressive from the business and the application I depend on has a gap in what they have committed similarly I'm looking at an recovery tier of mission critical for my business process but the application I am dependent on has uh marked that asset as a non-essential asset or not a crown jeel asset right so I'll be able to see these details uh based on the latest uh values that is coming in from a Downstream dependency uh so I can look at where is this getting pulled in oops sorry um you'll be able to start seeing where is this getting pulled in this would be from a downstream dependency of a Bia which Bia that is similarly you would be able to see for all of these as in when there are recovery time objectives or commitments filled for these assets that are dependencies you would start seeing those here and based on a comparison we will flag this as you know there's a Gap or no gap between the dependencies and the business process and this can be replaced with a service or a service offering you would be able to see all the dependencies and the business requirement that's the primary item of the plan and you'll be able to see if there's a gap that getting flaged off so that is the hierarchical view that we introduced right now some of our customers and users said this is a great view but we really want it into an uh table right not in a hierarchy IC view very similar to an Excel Microsoft Excel table so for that we introduced what we call as the list view the same data has been expanded into this it's not a hierarchical view but you'll start seeing accounts pay receivable as the first primary asset and this is the latest Bia of that it is repeating because I have only one in this case we'll look at adding one more you'll see what's the recovery time objective what is the recovery tier and this is these are the related assets right and if they have an uh let me see if I have just give me a second okay this one so I can look that uh this is the application that I'm dependent on the application has a recovery time objective of one month recovery point is here um what is the required recovery time frame uh and then where is this getting pulled in from right this is coming in from one of the downstream dependencies of a Bia that is why this asset is getting pulled in as a related asset uh for my particular process because it is connected in this particular Bia somewhere in the downstream so that that is the Bia for that and you'll be able to do walk based on any of these Bas or the related asset or the primary asset and add more values or columns to this particular view right so we have made sure that is available as well so that is the view where you can see the primary item and the dependent item and the commitments around the dependent item in one single view so that is your list view if you would like to see per uh primary item you can look at this view as well so the second set of functionality is the primary scope and the related scope so if I add another primary scope this is how it will look like so I can add that and you'll see that uh payable got added as another primary item right it's going to take some time uh behind the scene to pull in all the related items to this account's payable once we have all of those getting pulled in you'll start seeing those get updated here and when I go to the asset dependencies I think still taking time you should start seeing two things right just give me a second let me see why this is taking a bit of time you'll start seeing two primary items and everything under those comes up uh in in there right so that is how you will be adding and uh multiple primary items uh we will look at it in some time as in when uh all the related items are pulled in right so that is how you will be adding two primary items into the uh into the scope of the plan just give second it is still getting pulled up okay so adding a related asset uh the the experience has been changed as well so when you add a related asset you will have to pick a primary item from this plan that is already existing so in this case let me fake accounts payable right and I can add any of these related items uh into the plan so that's how you will add it so in essence what is happening here is you cannot have and related item without it being tagged to one of the existing primary items in scope right so we made sure that is uh the condition here so that will be a change going forward for all of those data that you have already created in your plans that will get migrated into the latest version we have made sure of the migrating migrating the existing data you will not be losing any of that the linking will happen with the existing primary items and all the related items are getting moved and you will be able to start using this new view so here if you see there are 24 items added under accounts payable that's the second one that we just added right you'll be able to see the related items under that like this so you'll be able to see all the primary items as level one and wherever you need to expand and view the dependencies you'll be able to view it in the hierarchical view or you can go into the list View and see what is the related items you can sort by any of the columns which are like uh the normal functionality on any list view so you'll be able to do any of this in the asset dependencies so that is the second enhancement in the plan uh I mean in the business continuity management this is specific to plan scope and how this is handled and one more thing before I move out of this one so when we delete a particular item from the scope uh it will remove all of those things that are related only to this if there is an application that is related to two of the primary items that will still be there and the entry for whatever is remaining will be there in your um in your asset dependencies and here you can see what are those 24 relationships that will go with this primary item right because these also got created and that's why it was taking some time for us to look at that so once it's removed you will start seeing that the primary item is gone all the relationships that it got created because of adding that is also gone so this is how we have handled the primary scope and related items in the uh business continuity planning phase I think a couple of the questions we'll help clarify a couple things for the audience if you could take to look at those uh the related asset could have a different R than the primary related ass that war stop no we are just doing it as an informational purpose so this warning doesn't stop you from uh moving forward with the planning phas right it's only an a flag that is raised because in most of the cases it has to be aligned we understand in some cases it can be completely different as well so that is exactly why we have also introduced what is called as a required recovery time frame right so your RTO may be immediate for your business process but when you're doing your Bia you can specify something different so in this case what I have done is I've have done this a 72 hours it's not like 15 minutes right for this particular asset what is the requirement from the business and that will be compared so uh this is one of the features we added to address that point but even otherwise because of this flag it doesn't mean that I cannot complete my plan creation or go with an exercise that will go ahead uh if a primary asset a is impacted for plan PA the primary asset has related as which is not impact sy so so that create so the related assets and the related plans the way that get used in the recovery tasks is and how that will get pulled into the events is if the plans are getting involved by any of the tasks right so if you look at this I have a related plan here and if I want to invoke that task in one of my uh recovery tasks here let's say uh activate a related plan and I'll be able to say this is the plan that I want to activate right so I'll be able to add that and if there are no validation errors it will get added as a task right so when we are pulling in this particular plan this is my master plan there are related plans here the the way that it gets sequenced is based on the task that I create and if I have a task that invokes a related plan then the task from one which is the task sequence that I am ordering here that as well as the related task will get pulled in uh into the event basically right and as far as the assets are concerned it will pull it in both ways it's not always only one way and what you can also do is in the events right in the events you would be able to mention what is the kind of asset relationship that you want to consider so if I go into just give me a second um dependence yeah so if you see here I'd be able to look at the sources and I'd be able to mention what kind of uh dependency should I be considering so if you look at it I have said uh I need to pull in the Upstream dependencies as well as Downstream dependencies from the Bas right in this case both will get pulled in if I remove the Upstream dependencies for example only the downstream dependent assets will get pulled in from the B as well as the plants so it really we introduced this as a flexible configuration for you guys to Define you can Define during my event which assets needs to be pulled in and based on the assets that get pulled in what are the plans that needs to be added I hope that answers that question um so adding it for a loss scenario is very similar to what you just added here there's no change in that part uh we have the LW scenarios where you can go into a loss scenario and then you'll be able to add it as one of the related assets right so you'll be able to add the related Assets in this model window you'll be able to add whatever that is so basically here this is loss of business applications when you create a loss scenario it is tied to a record type in this case it application so when you click on add all the applications are Avail available for you to add it into that particular loss scenario so that has been retained as it is yeah so here the are the related items based on the cmdb or can we at a add it at a plan level right so like the um like the dependency configuration I have that I showing for events there's one for plans also in plans I'll be able to mention what are the sources from where I need to pull these dependencies right I can pull it from let's say for example the cmdb or from Bia so I do a Bia I Define what are my Downstream dependencies or I have the cmdb I need a super set of all of this right I can Define this as the sources from where I need to pull in this related assets into my plans that is number one number two is when I go into the plan uh I'll be able to see this buttons here right so what I can do here is also I can build those related items or relationships during the planning phase let's say for some reason my cmdb doesn't have all these related assets and dependencies captured or I'm not doing a Bia on all my assets right I I directly go to a planning stage where I have an common uh recovery objective for all my critical applications and processes let's say it's 8 hours right so I'm going to start with planning which is the minimum stock that is needed uh so when you start off something like that you'll be able to go in you will be able to add the primary items to the plan and then once you have added the primary item or primary scope you can click on related items you can pick what is the primary item and you can say what are the related items that I want to add for this right and here I'm building that relationships in the plan itself directly so I'm not picking it up from a Bia or from the cmdb so I'll be add able to add it here and if I look at the asset dependencies right and here there are columns that would mention what is the primary source right and for whatever I added manually you'll start seeing it in the plan right so these got pulled in from the cmdb some of them got pulled in from the downstream B this I added now so if you have that added manually this is where you'll be able to see where did you guys add that and if it is coming from a Bia or from the cmdb record from which record is it coming from where are these two things connected right the related asset to your primary asset so you're seeing a lot of columns here because this was the minimum set that was required by most of the customers you would be able to manipulate or configure these things right so you would be able to delete the ones that you don't need you can keep the minimum ones you can add additional ones Etc so that is the view all right so that was the enhancements in asset scope so the next one is the recovery tasks in the recovery tasks we introduced automated tasks right so the Dr task can be automated uh not all of them but some of them you might be able to do this uh in an automated fashion so what happens in an typical task creation before this releases it would be tagged as a manual task uh this field you wouldn't have seen we have introduced it now because we introduced automated also by default when you create a task it will be manual and uh you will be able to assign it to a particular user right so I can go in and I can say this is manual right and I'll be able to say task uh whatever the details are for the task I can fill that in and I can also assign it to a particular owner right so I'll be able to add one of the users as the owner and create the task now what we have done in this release is there is an ability to automate the task inst stop assigning it to a user when I say this is an automated task I'll be able to pick up what is the flow that needs to get activated so these flows can be designed from your flow designer once you have added these uh flows right and you save them you will start seeing what is called as variables so these are the variables that are expected by the flow so for every flow the variables will be different right let's say for example if the flow that you want to invoke is to basically uh you know update a record in the system then you can add that so you need uh whether what is the status that needs to be updated for the task and what is the work notes that needs to be added to that event task right that you want to update if it is an task that is to check one of the Azure servers health for example then you might want to give the uh details of the Azure server like IP address or admin or credentials Etc so the variables will change per flow and uh based on the asset that you are trying to link with the flow once you have provided that you will be able to see this particular section here that says uh assignment details and the owner field has changed to backup assigning and backup assigning group right the reason we have added this is when we activate the plan this is an automated task it will not get assigned to any user it will activate this particular flow using these variables and if the task fails right we will send an email notification to the backup assign that automated task has failed do you want to go and check the task manually they will be able to intervene they'll be able to go into the task and finish it manually so the the entire exercise doesn't come to a stop so they can still complete it and the exercise can continue and later they would be able to make any corrections to the automation or the flow that has been tagged here or the variables whatever was the cost and make sure that in the next cycle or the next exercise it is automated task and it is not getting assigned to a user and they don't have to log in so that is the functionality that got added for automated tasks the next one is the planned duration right so if you see here uh earlier we had something called as completion uh deadline which was uh a drop down field right and the user was able to select only a set of predefined time frames so like 30 minutes 1 Hour 1 hour 30 minutes 2 hours Etc but customers had also um got back to us with requests on we want to specify specific time frames like one hour 30 minute 30 seconds or 1 hour 35 minutes right so what we have done is we have uh made sure that the completion deadline has got changed to planned duration and this is the format in which you can mention for every task there can be a different uh duration that you can mention here and this is going to be used in your comparison when you execute the task in an exercise so this is the expected time frame when which uh this task has to be completed what is the actual time frame and what is the gap or the delay if there's a delay right and when you capture the actual value for the completion of the task also it will be in the same format and we'll be comparing this and those reports will be available in your exercise so this is the enhancement on the recovery tasks specific to automated tasks uh the backup uh team and then the planed duration the next one is the tagging of the task to the assets right so earlier all the tasks in a plan were tagged to all the assets in the plan so basically if I have three tasks all these three tasks will tag to all the Assets in the plan as well so that is what we have addressed here so when you go into a task you'll be able to see a a flag here that says tag assets to none of the assets so this task let's say is a prerequisite task right so it should not account for uh time taken into any of the recovery of any particular asset so I can say this is none if I want to treat it like that if I want this to be counted for all the assets right if that is the uh logic with which I need to go I can say tag this task to all the assets let's say if this takes 60 Minutes to complete this task in the recovery time frame for every asset that 60 Minute will get added or I could say specific assets and I can pick which ones am I uh creating this task bar one or multiple of them and if it takes takes 1 hour it will add 1 hour to both these asset recovery time frame the actual time frame that is needed to recover them during the exercise so that is how you can tag the task to specific assets or none of them in which case if the time taken to complete that task will not be counted in the exercise or you can tag it to all the Assets in that case it will get added for all of them that is how the tasks are tagged to these different assets um going forward from this release so those are the enhancements in business continuity planning see if there are any questions otherwise we will move on to the exercise part so these are the screens that we went through yeah uh just give me a second related for a l scenar to just primary assets uh so so the loss scenarios adding the loss scenarios uh assets to the loss scenarios is been restricted to the dependency type it is not restricted to just the primary or the related assets so what we will be doing going forward is if you add an asset in the loss scenario that will get added to the uh scope as well so it will reflect in back in the scope but we will not be restricting it based on the feedback from you guys uh but if this is an requirement we can work it out as an configuration going forward yeah so just give me a second let me go into the UI and sorry uh what we meant by that is when you go and add a particular asset into the Lost scenario which is not there already right so as an application if I add um let's say one of these right uh and if this gets added here that will get pulled in as an primary scope item into the scope itself we will be adding that here uh we will not but restrict it as one of the it has to be one of the assets from here this is what we have planned uh in the upcoming release but if you guys need it the other way so that it has to be restricted from the uh primary scope then we can add it as a configuration for you guys I hope that answers that [Music] question awesome I think that's most of the questions that have come in so far that is the ones okay all right so now that brings us to the last uh enhancement set that is your exercise part right uh what are the enhancements in the plan exercise let's look at those as well so let pull up an exercise all right so during an exercise you'll be able to add an asset or a set of assets part of it and you will be able to see the plans related to those assets getting pulled in right and if you look at uh I mean we touched upon this briefly so if you go into the configuration you'll be able to see say what are the kind of related assets that we want to pull into the exercise and I have selected everything here right Upstream Downstream all of that but you'll really be able to select those and then you can say which ones I want to include which ones I don't want to include um am I going to add only the related assets uh from the plan that I select or am I going to add only the primary assets or is it also going to pick up all the related assets from a related plan right and I'll be able to pull that information from all of these so you can uh configure that and on top of it you'll be able to add it manually as well you can add individual assets into this once you have added the related plans are pulled in uh this is one way of adding and scoping the exercise the other way to do it is to add the plan and the related assets get pulled in and the tasks also get pulled up right so either you can start with the assets and the plan and tasks are getting added automatically or if you know the plan that you want to exercise just add that in and the scope of the plan and the tasks in it will get added into this automatically so those are two ways to get this added that is the uh that is the configuration to see which related items should get pulled in and then there is an update dependencies before we start off the exercise or a set of tasks you'll be able to update and get the latest assets as well so let's say I created an exercise I parked it in a draft stage right it is not started yet uh I created it today and uh tomorrow Somebody went and changed the relationships in the b or in the plans or in the cmdb they added something new as a dependent item they removed something which was already there right so when I start this event I want to make sure sure that I have the latest of these relationships considered and that is what is the scope of the exercise right so I'll be able to uh set it up as an automated update or I can say this is going to be via manual action that is update dependencies that will update these related plans the assets and the tasks and then I can start this particular event so that is the first enhancements on on this one the second set is we discussed that the task can be uh tagged to the assets right so that is the impacted assets that you see here based on the tasks being tagged to the assets the total time taken for the asset will be calculated so each task has an time calculated for completion of the task right and then you would be able to see what is the total time taken for one particular asset uh at a given point in time so I can pull up any of this and I'll be able to see I'll just give it a second this is my asset these are the plans related to it and this plan let's say has multiple tasks and I can see what are the tasks related to my asset and how am I calculating that particular time taken for this so if this has multiple tasks in this case it's related to many assets right based on this tagging only the tasks that are related to my asset here that is accounts receivable process will get accounted for in the rollup and that will be the required time uh actual or the achievable that is going to be calculated for this particular actual time taken for the plan as well as uh the asset that we are looking at so that is the rollup part the second one that we did is uh on bringing in a new status for the tasks so when we are executing the task we earlier had work in progress that's when this this task will get assigned to a particular user and then the user can say I have completed the task successfully right that means this task will get completed and the next task in line will fire the user can also say the task is incomplete I want to close it as in complete so there are some uh errors or there are some uh problems in completing the task fully but then I don't want to stop the exercise right the next next task should uh get fired and the exercise should go on so that is why we kept this particular status and the third one that we introduced was because many of our customers and users had got back to us saying if a task is failed and move to a failed status the entire exercise should come to a stop I should not proceed with any further steps in the exercise unless this is cleared right so this is getting parked as closed failed and what this will do is the next task in line will not be assigned to the user that will be held right as a predefined task it is not going to be assigned to the user once this moves into a failed status the use user can go and verify this and they'll be able to look at the recovery team they'll be able to see whatever is the state Etc and then they can retrigger this for an execution again if something has to be set right some properties in the server or some kind some configuration has to be changed you'll be able to change it and you'll be able to say retrigger this as a manual task this will again move into um work in progress status right and that team can pick it up again they can finish this and then they can say I have completed it as closed and the next task in line will get opened up for Activation right so uh if you see this became closed complete and this became open so once this moves into a failed status the next one in line will be still in pending it will not become opened and it will not be assigned to that particular user so that is the closed pH status that we have introduced the task can be completed successfully then the next one will start the task can be closed as incomplete then also the next one will start the incomplete task number of hours added to that will not be rolled up to the asset uh if it becomes failed it completely stops the further execution of all these uh steps in that exercise that is the new status and new uh workflow that's been added to the event task in an exercise I think there are some questions we can take that off can BCM light role engage in completing a recovery task yes we will be able to uh add an light user as an uh recovery team member basically the recovery team members are users who can update the task records right they'll not be able to edit the entire event record but individual tasks that are assigned for example this user they'll be able to edit only this particular record they'll be uh pulled in as an uh if they do only this right they will be added as an BCM light user so those are the main enhancements in uh event tasks so if there are further questions we can take it up uh okay there's a requirement for adding the link to the community I think we can add the link uh for the recording and and yeah Ross can work on adding that PowerPoint as well which has all these yeah if you don't mind just sending shooting me a private message with your email um I can send it over to you but it will be in the community uh which is the service now community and it will be under our on demand webinars in the GRC section so we always keep those in our uh um events blog post that I believe I linked to before but I link to um if it's not at the end of this session but I think it is I believe two slides down one more question there's uh there's one more question on that and then we can just take that up so basically if this is an open task right so the first thing is one of the recovery team members assigns it themselves and they can post complete or if for some reason we want to proceed with the exercise but this task is not complete you'll close it as incomplete right if you do that this would still uh trigger the next one basically if you see this becomes open right but if I go in and say uh sorry there is update on this so but if I go in and say this is a failed closed then the next task that is pending will not be opened up basically it will stop that so this is that interim stage where you want to fail this particular task but want to proceed with the next one that's the closed incomplete one closed fail will stop the rest of the flu I hope that answers that question ni uh okay I think uh those were the major enhancements that we wanted to discuss with you guys today and to just go back to the the slides where you have the QR code and then the links these are the ones y so I'll just let you know that um the community um is the links there um that is the risk area of our website in number one to watch any of our record and demos you can go to our YouTube channel and then to register for more Community webinars you can see that um in that QR code there um I also put in the chat the direct link to the overall community and then the pathway to what I would consider and if you move to the next slide osin I would consider that probably one of the best places that you can find for risk in ESG events we try to keep that updated on a regular basis it's updated I think every Friday by one of my colleagues and you will see as many webinars or in-person events um or any s sort of opportunity that you can get to see risk or ESG commentary um whether it's as I said live or in person so if you want to bookmark that that's probably a good bookmark to have because that's where we try and promote things and I think there's only um in slide is that right last one if you want to just move over okay great yes and this is the interactive Series in the webinar so if you want to um sign up for that QR code too but otherwise um as I said the the links in the uh probably the best if you have any further questions please reach out to us um couple of thank yous in the chat um and there is one more question that I will get answer after the call so thank you so much for your time Oswin uh very much appreciate your time today and thank you everyone for joining