today we're going to talk about what's new in business continuity management and we have aswan who's going to detail some of the features and give a demo um and we'll just get started right now everybody's ready so just a couple of things to get started on um we do have a lot of future webinars coming up that are great and this session specifically is part of our live on servicenow which is a curated event series that is connecting you with servicenow experts and your peers and this can help you uh with your deployments of your products and help you achieve value faster we hope that you can join us again for another webinar or meetup and you'll see the schedule by scanning the qr code or using the link that you'll be finding in today's chat additionally we have quite a few risk events coming up specifically for our area of business and we've got some um great topics that will talk about what's new across the entire risk portfolio so today we're talking specifically as i said about business continuity management but we're also going to have a series of events over the next few weeks to talk about other developments that we've made so we really hope that you can join us for those um and you can sign up for those in the community there also will be a code at the end of this session to help you facilitate sign up so i do want to introduce you to today's speakers my name is rosalind morville and i'm the product marketing manager for bcm operational resilience and our vendor risk management product oswin is the principal product manager for bcm and operational resilience and with that he's and an execution of everything related to these products so welcome austin hey hello everyone so we've got and i would have said three but otherwise sneaking in a fourth feature to highlight today we're going to talk about auto populating related items we're going to talk about how you activate tasks based upon a predefined sequence and we're going to talk about how you uh track the execution of some of those results the fourth feature we're going to detail a little bit about is bcm light and so we're going to talk about that that user role and how you can uh use that within your offering so specifically about auto populating related items this is a way that you can repurpose data across systems programs and it helps you reduce the amount of re-keying or re-entering information when you're planning or conducting your business continuity exercises we've introduced ways of auto-populating we have ways of manually adding if you need to if it's something that's not currently within servicenow uh copying and relating those items throughout your bc processes and plans along with that there are also notifications and us when we'll talk about a little bit about that so just to give a clarification on how the data flows through the bcm workflow um oswan will go into details about how you bring that data from the cmbd into your bias how you can bring that into other related plans and how that flows through to the exercises that you're planning our second feature where we're talking about activating tasks on a predefined suite sequence it's where you're sequencing tasks based on your bc plan and you're automating one task that can be activated from a proceeding task so you can set up these tasks or sub tasks to make some complex needs and goals that you have with your business continuity plans um and it enhances the user experience for you so we're really excited to bring this feature to you and then finally i will touch a little bit on tracking the execution results so you want to look at the execution of your or your plans um any deviation in delivery time and we want to talk about those successes that you achieve by being able to uh filter all this information through your bcm so we've really brought you some real great i think user experience enhancements and oswin's to detail uh what those are in a demo so if you want to take it away thanks ross yep definitely um let me share my screen and i hope you guys can see my screen now all right all right so uh let's look at how the cmdb data gets reused in the bis and then subsequently in the plans and then how that gets transferred into the exercises and crisis events right that's the first uh important functionality that we have introduced let's go over the details now right you guys might have seen already for previous releases that we have this capability for you to identify the dependencies that are already there in the cmdb and bring it into business impact analysis right this is an existing functionality but this is one of the key links in this whole data reuse value right the functionality itself so i'm going to touch up on this for a little bit and then we can move on to the next one so i am doing an application technical impact analysis for an application called let's say in this case servicenow right this is one of the applications that your team manages i'm taking an example of an it recovery today right so in this case uh i'm the application owner am doing a business impact analysis for this i can see how many business processes that i support etc and then the next piece is to do the uh dependency mapping right so if i have already identified the dependencies of the application and underlying infrastructure using auto discovery or service mapping and stored in the cmdb what we could do is the user can simply click on add dependencies if there are any new dependencies that will get pulled into the application automatically here's an example for that right so there are three hardware dependencies that i had mapped in the cmdb when i clicked on add dependency it would put it in and you would see that the relationship source is updated as cmdb here because it's already done in the cmdb and it's getting reused right this was something that we already had released in the previous release same way it can go across different categories of dependencies in this case it's not coming from the cmdb but then the user has manually mapped it inside the bcm application that's what this is about right and so on so you can have some things coming from the cmdb some more data enrichment happening within the bcm application um yeah like uh um ross mentioned uh if you guys have any questions please add it in the chat and or the q a we would be able to pick that up thank you so these are the different elements coming from the cmdb itself now there was a question from some of our customers for for answering that for the larger audience let me show you how you can control what dependencies from the cmdb matters for your business continuity planning program right you don't want to bring in all the individual items that have been identified in the cmdb because the tables in the cmdb are huge and it can hold n number of relationships right and when it comes to business continuity management you might not be interested to pull in everything from there you are only interested in critical applications critical you know um servers or infrastructure etc right so you would be able to go in to the business continuity management application as an administrator go into the element definitions and you can define what are those elements that are critical for me when it comes to business continuity management planning and execution of the program you can ignore the rest of the items and tables or classes the ci classes in other terms from the cmdb that will not get pulled into your bcm application right so that is the this is the this is the place where you would be able to mention what is the source table and for each of the source table you would also be able to mention what is the filter condition if you were to add a filter condition you would be able to say i want to add a filter condition and you can choose a type of filter right you would be able to choose any of this and provide the value to that and only those ci's that are from this table and satisfies this condition will get pulled into bcm so this is the setup part now the reason we have done this is one is you don't want to pull in all the ci's or ci classes from the cmdb that would already be taken care by this table that you select here and classify it as computer rooms for example but then probably not all computer rooms are going to be significant when it comes to business continuity and itd are planning right let's say there are some critical servers stored some of the things are hosted there which are critical etcetera you can classify those computer rooms with a flag and you can mention what that flag is and then pull that in um with the right set of let's say uh critical uh ci right only these only those computer rooms which are flagged off as critical ci's will get pulled into bcm so you can only get the filtered list and that will be available in your bia here right once your bia is done uh this is the new functionality that we are we have released right so let me start creating a plan i already have created one and placed it here in case things do not work we can go look at that but let me start creating one for now critical application right this is an application recovery plan that i am creating let me say this is an application recovery plan template i have chosen the template i can choose the department and i can say submit right now the plan we have added two new tabs or functionality that you would be able to see which is a delta from the previous release right that is called related assets initially it will be empty as well as the related plans now when i add the scope um we were talking about servicenow as an application right we said this is an application related plan so we could add that so let me add a rest service now one second there we go so i have added this particular service now as an application the system already identifies the um the recovery time objective the recent recovery point objective and the bia this is because we can see that uh sorry about that this is the most recently you know approved and published bia once this gets identified the application automatically understands what are the related assets right and it gets pulled in uh very similar to this one so once i add this you would be able to see these are the related items so all the related items here will get pulled in from the corresponding bia so when i say the corresponding bia that is this one right so irrespective of whether that's coming in from the cmdb into bia or someone has enriched it manually in the bia itself right this will get pulled into the next level of planning that is your business continuity plans once it gets pulled into the business continuity plans you would be able to see that the related plans also gets pulled in so to the related items right in this case there is a data center recovery plan there is a hardware recovery plan and alternate supplier plan so the related plans are maintained by three different teams right these are are maintained by the vendor team this is by the hardware team it team and then the data center team who is responsible for the operations of this data center and these individual plans are covering these different elements but then for me to have my application called servicenow up and running we have identified these as the dependencies these assets and they have a corresponding recovery plan for themselves so when i'm creating a master plan for my application uh the system tells me these are the underlying plans that also have to be executed when you're doing your exercise right so this is the first step once we have pulled in these plans the enhancement that we have done next is we're in the recovery tasks we had the capability to do the recovery tasks already right let me see if i have an example there just give me a second uh okay so uh i can go into the recovery tasks and i can say uh three requested task one right i can assign it to an owner and i can say what is the scope of this particular uh task and i can say create it gets created here once the prerequisite tasks are done i would be able to say let's say for example activate uh hardware recovery right i can assign it to an owner who is responsible for activating this i can say which is the scope of this item right it could be a hardware data center zone and the dependency for starting this is i have to ensure that the task num prerequisite tasks are completed once it is done i can say refer to a different plan here so i will be able to click on this and i would be able to select the i'm sorry one second right i'd be able to select the hardware recovery plan that is an pre-related plan to this right so we would pull in all the related plans and you can create this branching off of the tasks within this master plan right activate data center plan i can assign it to a different user right and i can say uh this is the dependency so once the hardware recovery plan is completed then you have to activate the data center recovery plan next right so that is defined as a dependency from one plan to the other the tasks can be dependent as well from one plan to the other right and we can also add more items in this where we can say activate you know alternate vendor plan and we can assign it to an user who's supposed to be working on that right so i can also add that i can say this doesn't have to wait for the previous plan to complete but this is a parallel task that can be started right so i can add that and create it so like this you would be able to create the tasks when you're creating the tasks you can mention that one of the tasks is actually not an individual item but then it has to branch off into an entirely new plan itself so each plan in this case can have let's say 10 or 20 tasks so the way that it will get executed is what we will see next so during this creation you can also mention for example uh let's say post recovery task one right and you can assign it to an owner here you can mention the assets or ci's that need it and once the last task is completed let's say you want to kick off the task back in so this one is an individual task as well right so this is how you would be able to pull in the related assets that is from the cmdb it gets pulled into bis from the bis it gets to pull into related assets right if we have completed the bis for each one of this item and if we have a recovery time objective and a recovery tier those would get pulled in as well and if these items have related plans already created and stored in the system right they will get pulled in as related plans for example we have data center hardware recovery and alternate supplier right let's see those ones here those should be here in this right so each one of these are already published plan in the system so the user would be able to go in and see that these are the plants that have got created and they are related to assets which support my application so these gets pulled in as related plans and you can sequence them in the order that you want them to be executed so this is the um the plan getting the data from the bia and bia getting the data from the cmdb and you can of course set the sequence and also mention what is the order in which they should get executed you can establish dependency between a task in one plan to a task in other plan that is data center plan can be activated only one when the last task of this particular plan is getting completed right so you can set that earlier we did not have this capability as well so this is the first enhancement the second one is when it comes to recovery do you actually have one question just about dependencies yeah so i didn't know um does this include service mapping and if not is that planned uh as long as this is going to be captured in the cmdb we will pull it in no matter from where or which methodology you are adding the dependencies ensure that this is getting recorded in the cmdb as dependencies we would pull that in so what i mean by that is so if i go into applications right business applications let me just uh business applications and we were looking at service now right so this is the cmdb view of the business applications as long as these are established within this we will get it in so it doesn't matter if you're uploading this from an external system or you're opening this as a gui and then updating it manually or you're getting it uh captured via any of the other components right so if it is in the cmdb we read it from the golden source we treat gold the cmdb as the foundational layer for this data records and the interdependencies between them so this is the key element as long as it's there it it'll get pulled into your bis and like i said uh you don't have to pull in everything right so if you see here the application called service now this is the application we were working on right so it has a lot of different items that it depends on but we did not pull in all of this because you had not configured the critical elements for your bcm program right so these are the ones that we have configured so only those gets pulled in if they are already identified in the cmdb but there's no cap limit on this um you would be able to configure n number of classes ci classes right if you want the let's say for example the mass storage devices you just have to configure that as an user i mean administrator and that will get added as one more category here and those will get pulled in as well so you can decide which one of these uh the classes is critical for my bi bcm application and team and only those will get pulled in right so that's the key so all of that points back to the cmdb tables so that is one of the items and if you want to capture the items that are outside the cmdb that you can also configure here for example vendors vendors does not come from the cmdb tables in this case right if you are managing it outside in servicenow's platform there's a table called company table or core company table these are records that are there but we said we need that to be part of bcm because we want to plan for alternate vendors and in case of supply chain resiliency kind of plans right so you'd be able to pull in that information and tag it to your application or your business process right if it is a business continuity plan it will be of course a business process or a service um or a location right when it comes to iddr it's going to be an application or a data center uh dependency so you'd be able to add that it's a combination of what is there in the cmdb already and then enriched manually during the bi phase that gets pulled into your plans uh eventually right so if you see once i have this data inside the bia right that is the cmdb data as well as the manually entered data both of them this is the company information this is the hardware information right if i go into the plan that we were working on uh i said my application is servicenow i want to create a plan for that right if you go into the related assets it pulls in the same company items from the bia right uh and it would have also pulled in the hardware that we were looking at hardware entries right this also comes from the bia because from the cmdb it went into the bia and from there we are pulling it in if there is any change in the underlying cmdb records you can subscribe to the changes as an owner or someone who wants to wants to be on the watch list right you would be able to get that email and then if there is any changes you can make that changes in the bia as well as your plans that's how we trickle down the changes and notifications to the owners of these elements um any other questions before i move on to the next item there are a couple um so can um can you remove a dependency for exam um yes for example i don't have a linux server i have windows service instead of a complete blank can i remove it from my plan so if you don't want these three let's say or if you don't want any of this or this you just select that you will see a remove button that pops up once you made the selection till then i think it's going to be heated right so or disabled for example it automatically pulls in everything uh the first level of check is what you can decide what needs to get into my bia right like i said not everything gets pulled in it's based on what you want to to get into the bia in most of the cases it's going to be if it's in the bia i want to reuse this right so it will also come up in the plan from the bi it will get pulled in here but at this point in time if you decide i don't want to handle it in this plan but maybe i want to do it as a separate plan you can very well go ahead select it and then say i will maintain a hardware thing as a separate item i don't want to include it here you can remove it this will get removed great um and can you um if you're using mapped application services will that be pulled in like i said not everything will get pulled in it can be configured by the administrator right so these are the categories that i have configured the place where you will configure this is as an administrator you would be able to go into yeah so the business continuity and then there is an administrative capability where you can go and say these are the elements that i want to use in my vcm process right and by that team for example i don't want end user computers so i've not added it here if i want that i can simply say add and define it as one of the elements that needs to be used in the bcm application then it will get pulled in until that is done this is not going to be pulled great now further question on dependency assessments yeah on the bias uh for in-scope items that gets pulled in uh i didn't get that ross can you just add no this person said chris christopher said so all the dependency assessments on the bias for the scope items get pulled into the plan that is correct so and then this is not like only the downstream dependencies right if i create a plan for and downstream item the upstream item will get pulled in as well so let's let's talk about this for a minute and then we can move on so here i am creating an plan for an application right so it pulled in all the infrastructure under that or whatever items that it depends on as the related items right so this is one way of looking at it so if i have to recover this particular application i want to first finish recovering all of this right that's one way of looking at it if i also want to do the other way around right so let's look at the approved plans let me go into that for a second let's look at hardware recovery plan right so i have created this plan for these two hardware servers when i say these are the items that i'm trying to recover what this does is it automatically pulls in the upstream element right it has related assets this is one of the enhancements that we have planned for next release currently it pulls in both upstream and downstream we will add a column here that flags it off saying whether this is an upstream dependency or a downstream dependency so that will give you more clarity but today it actually pulls in both so you will get both of this into the plan as a related items and the same will get pulled into the recovery uh events as well we will see that next question and this one may be specific to this person so um please guide me on that um with the source cm db we had originally set this up so the bia dependencies link to the cmdb today however it shows as the source bcm when users selected bia dependencies they were able to select from assets from our cmdb does this seem like a problem moving forward for us with the new one no uh no it wouldn't be so the assets that you select within so i think there's a slight country there right let me show you uh let me edit this for a second and this should make it clear just give me a second okay here right so these are my uh hardware dependencies right i'm going to delete or remove this for a minute and then let's see uh if i click on add dependencies this would say three things are added basically because these were already established in the cmdb and it got pulled in automatically right i didn't add one by one so that's why this is saying it is coming from the cmdb now if i want to add it manually here let's say somebody missed adding one more item in the cmdb right but i want to proceed with my bcm program or process so i can go click on this i'll see everything from the cmdb listed here and then i can select let's say one or two of them and say add now when this gets added that is i have added it within the bcm application this is not getting added directly in the cmdb right that is when this will get flagged off as bcm right this was identified in the bcm process so um one of the easiest ways for you to handle that kind of a situation now this is not in the cmdb right this is created only in bcm so if you want to have a report created that says how many of such outliers are there which were identified outside our cmdb there can be a report that is easily created and that can be used for you to populate the cmdb with such identified items outside your actual cmdb team so this is something that we are planning in the future as a separate report that calls out these items that got added outside our purview right for the cmdb owner they would be able to pull that in and say yes this makes sense let's update the cmdb with these records but today it's this information is made available inside the bcm application the next time if this gets added in the cmdb and when you're refreshing your bia this also will start reading as cmdb as the source that's the idea behind this functionality um so it shouldn't impact how you guys are using this today because this is an existing functionality and we have not changed anything here okay i think there are some more questions uh let me take up that as well yeah there's in the chat uh yeah so we can take a couple of more questions and then we can get back to you guys um on the rest of the ones later the upstream and downstream dependencies are the ones that you support and then that are supporting you right so that is the upstream dependencies upstream dependencies are the ones that you support downstream dependencies are the ones you are dependent on that will be captured in your relationship type in the cmdb we base it on that and then those will be classified as upstream and downstream dependencies do you have the other ones or uh yeah i'm just reading i want to rush you what was the component that the bia done on that all pulled off in automatically yeah so it is the uh when you say component basically it is the item that i am starting the um bia on we select what the bia applies to basically right when i say this is service now is the application for which i'm creating the bia it will go look for the service now as an item in this particular table basically it is coming from the application table right so it will go into application table look for service now it will look for everything that is related to service now and it will pull in only the items for which you have set the filters in this case hardware data centers and so on we discussed this right so it is based on this particular applies to item so to what does this bi apply based on this it will pull in everything it doesn't have to be an application always it can be a business process in which case you can pull in the facilities people department functions applications suppliers all of those right so i'm just using this as an example for today but the same construct can be applied across any of the items that are sitting in our platform basically if it's related to one another and if you want that to be pulled in you just have to identify one of them and the others or the rest will get pulled into the dependencies uh automatically and from here it will get passed on to the plans um this relationship source uh on the yes so the relationship source is on the bi bia analysis table um this is not passed back to the cmdb like i said but that's a report that you guys can create or if you guys are ready to wait for it we will be releasing it in the next release of bcm right so we can definitely add the technical services right in fact i think i had an example in one of the demos we did earlier where we had instead of the hardware dependencies and others you can also have technical services or application services that can get pulled in as well the network services any of these that it doesn't have any limit on what you can define as the dependency here right as long as it's there in our platform we can define it as a dependency and if you have established that in the in the cmdb it gets pulled in automatically if you want to add manually and enrich it within bcm you can do it as well like i did you can click on add new you can select from it and then you can pull that in the only thing is that min has to say that these technical services has to be captured as one of the categories here right as long as that is done it will start working and for that there's a gui right so uh like i was showing you guys this one i just have to go here and say technical services and i just have pointed to the technical services table so it will just get added as a category and it will start working okay one last question and then we will move on to the next one um uh all right uh service offering yeah so like i said there's no cap size on that so that should work service offering uh application services technical services any of this right all of that will work with this able to opt to link any of our plans together manually yes so if you want to link the plans together manually i was talking about this getting pulled in automatically right so this says the sources bia based on that is what these plants got pulled in here also you'd be able to go in and say these are the other plants that i want to add right so let's say continuity of operations plan so here you would say that this got added manually this is the source from where it got pulled in automatically right so this will do that differentiation if you don't want to have all the plans pulled in automatically from the bia you can turn it off and then you can go identify the next next plants manually as well in case you want to manage these plants as a master plan and then the sub plants remember each one of this is a plan and by itself and each one can be maintained by a different team the advantage is you are just referencing that here and if this plan changes tomorrow um you don't have to do anything like it's already linked to the plan and the changes will automatically get kicked in we will see that next how that gets added right if this has today 20 tasks uh you just tag the plan tomorrow somebody changes five of the tasks and adds 30 more it's anyways already tagged when you activate this plan this will get implicitly activated and the new set of tasks is what will get fired right so the plans are maintained by individual teams it's more like a federated governance model and you're just referring to those relevant items that's the area here yeah so the way that the plants get pulled into related plants automatically is because these plants are tagged to these data center zones right i'll just take this as an example ny 15 a data center data center zone l y and things like this right now during our technical impact analysis we said there is data center zones that my application is dependent on right if i go into this these are the data center zones i am dependent on right this came from the cmdb now this data center zones have their own plans create been created by the data center zone team right they are already stored in the application now when i said this is the scope of my planning it pulled in the related data center zones it looks for whether there is a recovery plan for these zones already created by that respective team and it identifies there is one plan that is related to that and that's how that gets pulled in here once i have all of this pulled in the plants also are getting pulled in based on the relationship between the assets and the primary item that you're trying to create the plan for once i have the plants pulled in i can go and sequence it based on my requirement how they should get executed this is currently just getting pulled in all the plants are getting pulled in right then i can go and say the order in which it should activate the plants is first do a prerequisite task or it can be 10 tasks right and then you activate the hardware recovery plan once it's done activate the data center recovery plan once that is done activate that alternate vendor plan once all of these are done do some post exercise checks and all of this is successful then the exercise is successful and i would have recovered my primary goal that is my application that i was supposed to recover this is how you can pull in all the information that's already stored and then sequence your recovery strategy or the procedures right so that's how this will be you know used in the recovery as well yeah so if the rto rpo gets updated this will already be pulled in because this is coming from the bia right like here so this will be the latest rto rpo of the scope and as well as these items right the related items this will get pulled in from the latest approved bis right so if i start again another bia for one of these items unless it is approved this will not reflect that once it's approved and it gets it gets moved into the state called approved so initially it will be in draft and review pending approval during all of this it will not be pulled in the moment it gets into the approved state we will pull that into the plan that's how that works okay so let me quickly touch upon two more topics right one is uh pulling all of the same information into the recovery right uh let's look at the exercise part now let me go and and again i also already have one of those lined up but then let's see quarterly application right so let's just do that and then i'll say functional and uh i can say a planned date and during this coping earlier you have to select everything that you wanted to put through the test right or the exercise now currently what we are doing is we are using the same concept so as soon as uh that is this one that we were discussing as soon as i select one item it will pull in everything that has to be recovered along with that right that is the idea so we will use the same thing like applications and let's say i think we used an application called service now so when i pull in the assets called uh service now um because there are these plans are under um edit mode now right that's why it's not getting pulled in like i said it should be published once it gets published it will get automatically pulled in but for the demo sake i already parked it part one of them under this so basically as soon as you add the service now as one of the items that you need to do the exercise on all of these other items that you see here that is the data center zones computer rooms all of this will get automatically populated in this view not only this ones it will also automatically pull in your uh plans basically this is the master plan right so we said there are some prerequisite tasks and these are the ones that has to branch out to separate plans as well and then some checks so the related plans will be be here so as and when you move on from task one is completed then task two will get triggered when it comes to task number three it will know that this has to execute a hardware recovery plan separately it will go into that and it will finish these four tasks once this is done it will go back to this one it will look at the next one that is the data center recovery plan will go into this finish these three then it will start triggering the supplier tasks right so it will go into this finish these three and finally you will be able to see that these tasks get triggered as well are filed uh the the owners would be responsible for updating the status once all of this is done you'd be able to see that total time taken uh and which ones were recovered and so on and finally you can make your um summary for the exercise and close the exercise currently this is work in progress right so this is the next level of automation with the same data so that's how this gets pulled in so from cmdb to bia bia to plan and from there to the exercises and along with the related items all the related plans and the sequence in which they should be executed will get folded this is basically the task that we created right and we said this is the dependency sequence based on the sequencing these tasks will be fired one after the other and once everything is completed you will be able to get the result so this doesn't have to be always based on applications and its dependencies right you can also use the same concept for departments or locations let's say you want to do it per department as long as the department is related to everything under that department right um using your bia if you have able to achieve that and you're interlinking all of the elements under that when you're doing your exercise you just have to select your department and everything under that will get pulled in as part of your scope so this is an enhancement on the scoping and then activating the plan in the right sequence and tracking the exercises this is the uh this is the next functionality that we have enhanced here so when you upgrade the plans will get created but the sequencing will not be updated right so you won't be able to see the sequencing so basically you will have to click on the edit button and this should get populated with the latest data but the sequencing of the tasks uh basically will have to be redone because that will not know the related plans right so that is something that you will have to do this was answering the question on the chat there is another question from scott if during completion of a task list an issue is encountered where do we need to either roll back or use a different task list is that supported yeah so if there is an uh if there is an task that is not getting executed and if you are facing an issue what we simply do is you can either say skip this task right and move on to the next one even though there's a dependency it will move on to the next item or you can say this is closed as incomplete so if i say this is under work in progress right i can say closed has completed for example if it is successfully done if i have tried everything and then it's not getting completed as expected right but there's nothing more to do i can say it's closed incomplete right i can put in my reasons for that and then i can send it back to the crisis manager who is coordinating everything and that person can take a call on how the next sets and steps should proceed that's how we handle that um okay so that was the functional enhancements there's one more thing that we wanted to touch upon today that is business continuity management user lite this is one of the important functionality that we have released uh in terms of licensing and roles so let's look at this and if you have any questions again please do ping us on the q a or on the chat right so earlier we had this concept of bcm operator and bcm the business users right so bcm operators are the users who have the role that allows them to edit anything in the system uh that is bis bcps events uh recovery tasks etc all of them right they are the heavy users so we have got this request from you guys that all of our customers that there is an user role and a necessity that doesn't have to eventually do all of this heavy lifting but then they have to participate in bcm process so we have introduced something called as bcm light operator so let's see what this user can do this user with this role can do and how this will be metered for licensing right so so the bcm operator uh light light operator right these are the different activities that they can perform in the application basically business impact analysis whatever has been published in their department they would be able to read it right and if that is a questionnaire that is sent to them for answers let's say for example there's someone from the legal department who needs to provide some answers and contribute to your bia you'd be able to send it to them and they will be able to respond or update the answers let me show you how that is done so in the business impact analysis the user who owns this right the owner is an operator but the owner can already go in and say i want to get input from let's say sean in this case right so they get added as a contributor here they would be able to go and provide answers in this particular bia where they are tagged right they won't be able to start a new bia by themselves but if they are tagged as a contributor they'll be able to go provide the answers right and they will get countered as a light operator not as an operator not as a heavy user but as a light user similarly business continuity plans they can download and read continuity exercises also same way crisis events and recovery tasks also they can read and they can update the status right where that is when i am creating my plans when we were creating the plans we added some of these owners for each task right so these people might not be heavy users they are only responsible for the task that they are assigned so these users also will be able to receive the tasks they will be able to finish the task and say i am done add evidences add the comments and then submit it back to the crisis manager so these users also will be treated as light operators that is this one but apart from this we also had an a requirement or an enhancement request from our customers that we have business managers from each business unit or the head of business units who want to be notified and approved will be involved in review and approval process of these things so they will be able to review and approve all of these records but they won't be able to make any edits in the record they can simply say it's approved and they can make a comment why it was approved or they can say it's rejected and why it got rejected right so they would be able to do that and these users who are participating in the approval process as well will be counted as light operators so there is going to be a difference in licensing the light operators are not going to be licensed as equal as the operator users there will be that will be this will be lesser than that of course this is a subset of things that these users can do in the system right these are the operations that they can do this is what will be available for these users but for enabling the bcm light operators you will have to have either bcm standard or bcm professional applications installed so this will be like an add-on you have some operators and then you have some light operators in other terms right people who are the heavy users and we have a subset of activities assigned to some light users that is the only precondition for this and this is also generally available from um 4th of august this month this is the enhancement on light operators let me see if there are any questions otherwise i can show you more details on this okay is the light uh user role assigned dynamically as you add a contributor no you will have to add that as one of the roles for the users and then you can select them here uh is there capability today or thought for the future to be able to restrict access to only the plans basic vis that they own contribute yeah currently when we say uh they will be able to participate in the bis they will be able to participate only in the once they are added as a contributor unless you're a heavy user of course the heavy users will be able to look at everything the assumption made was these are your vcm managers the the subject matter experts who are who want to look at the plans across the teams right but we will be working on acls there are some enhancements in the roadmap coming up not just for bcm but across the risk products uh that's right the next question is is the light user role assigned dynamically yeah it's not assigned dynamically you will have to assign it and then select that user they will be able to participate in bis that's the prerequisite for this right there are some more details that i can share with you guys here on this one uh we can go deeper as time permits so how does the light operator get um identified right the right operator will be identified if the user has any of these roles it can be all these roles or a combination of these right so there is a contributor there is a viewer there's a recovery team member there's a viewer again and then you'll see some more contributors and viewers these are the ones that will be counted as a light user if the user has only these roles or some of these roles right if the user has let me quickly go into the next one if the user has any of these roles ident assigned right they will be counted as operators basically that is if you assign any of these roles these users would be able to create a new bia for example they will be able to set up admin administrative activities right those roles are those users who have these will automatically get counted as operators so it's important for you to segregate this we have made this available in documentation as well what are the rules to be assigned to operators what are the roles to be assigned to light operators the moment you add this to a light operator any of one of these roles they will get counted as operator from the next cycle so that is this one and we will share this powerpoint as well so this tells you um how this is getting you know tracked basically you can see each role this is in the previous slides and how that is classified in the system and you would be able to see how they are getting tracked uh on every cycle right whether that is a bcm operator or a light operator these are the user names based on the roles assigned this is the reason why they are tagged as this and then you would be able to see let me quickly go into this the screenshots and where they can participate in the cycle that is the green ones that you see here are the areas where they would be able to participate that is the light users and what they can do has been called out i'll share this powerpoint this is in bia these are the screens and they would be able to access their tasks from assignments they can make changes and they can submit it basically right ad dependencies um this is the approvers you can select the approvers here then they would be able to open the record and then say approve or reject once they open the record and they can review or they can provide the comments but if you see for the light user who's the approver they won't be able to change the name of the bia or any of the fields they can only review that add comments and then they can say approved or rejected this is the same functionality for bcp exercise etc right these are the next steps basically the same thing for plants and then this will continue on for exercises as well i'll stop with the presentation here there are a couple of questions on the chat we can take that up and then we can address your rest of the questions over email and there's also one question in the actual q a um which was are there uh any roles that can leverage a group in servicenow or do we always have to specifically call out individuals uh you can call it individuals uh so yeah it is individuals and the the roles that you need to tag say user role combination now what is the user role uh bcm lite uh i hope i addressed uh that in the powerpoint that i was presenting just give me a second that was actually before you went through in detail so um if there's additional questions then we can but um i think that was before you uh detailed a lot of rules um so you don't need the planner role for changing um there's another question in the chat that says currently you need the planner role to change access almost anything in the system you don't need to be a planner but you need to be a plan viewer right so that's what i was explaining earlier so these are the roles that you would need for uh your um light user basically plan viewer be a viewer contributor member viewer this is the one right so there are granular roles that we have created and then there are the top level roads right so these are the granular roles that will classify as your bcm light operator and these roles if you have any of this for example the planner that you are asking about this role will get classified as your operator license right so that is the next enhancement like i said we will be sharing these questions with you guys i mean questions answers and the powerpoint and the recording um thanks for joining guys we are on top of the rl stop here