WEBVTT 00:00:00.000 --> 00:00:26.066 [Upbeat music] 00:00:26.066 --> 00:00:33.699 >>Speaker: Unit 4 Customized scenarios. Objectives: Create prevention 00:00:33.700 --> 00:00:36.233 planning scenarios. 00:00:37.200 --> 00:00:40.800 Customize a scenario by distributing prevention hours to 00:00:40.800 --> 00:00:41.300 actions. 00:00:41.933 --> 00:00:45.266 Generate, review, and edit prevention action sets. 00:00:49.900 --> 00:00:54.566 So again, just like the benchmark, once you create your 00:00:54.566 --> 00:00:59.966 scenario, you come to this table again, the worker hours, labor, 00:00:59.966 --> 00:01:05.199 funds, support dollars, and the total is what you generated in 00:01:05.200 --> 00:01:09.433 the previous step when you created a new scenario. 00:01:10.300 --> 00:01:14.666 Again, total fires prevented are the fires that are on top of the 00:01:14.666 --> 00:01:15.699 25-year average. 00:01:16.866 --> 00:01:21.332 And you have your general action action sets, your specific 00:01:21.333 --> 00:01:27.066 action sets, your load button to load the scenario to 00:01:27.066 --> 00:01:32.299 be able to see the prevention actions and to distribute those 00:01:32.300 --> 00:01:35.200 hours, your properties and your delete button if you no longer 00:01:35.200 --> 00:01:36.966 are using that scenario. 00:01:37.466 --> 00:01:42.466 Then lastly, your scenario completed generates when your GA 00:01:42.466 --> 00:01:45.532 and your SA are both checked off. 00:01:46.700 --> 00:01:50.400 Once again, your general actions is a zero out of one because 00:01:50.400 --> 00:01:52.833 there is one prevention management area. 00:01:53.266 --> 00:01:58.599 And then for this case, we have 3 prevention units and we will 00:01:58.600 --> 00:02:04.933 need to go in and manipulate and distribute prevention hours to 00:02:04.933 --> 00:02:08.533 the actions three different times, one time for each 00:02:08.533 --> 00:02:10.966 prevention unit that we have. 00:02:16.433 --> 00:02:21.533 OK, just like in the benchmark, we need to select our primary 00:02:21.533 --> 00:02:25.933 causes for both the general actions and the specific 00:02:25.933 --> 00:02:26.566 actions. 00:02:26.933 --> 00:02:29.033 So again, a quick review. 00:02:30.600 --> 00:02:34.900 You need to load your scenario, which is that first picture, and 00:02:34.900 --> 00:02:38.866 then you'll have your three buttons on the bottom that will 00:02:38.866 --> 00:02:43.066 populate your general actions, your specific actions, and then 00:02:43.066 --> 00:02:44.366 your primary causes. 00:02:45.333 --> 00:02:47.533 So again, click your general actions. 00:02:47.533 --> 00:02:54.099 It'll be blue if you have that clicked and if it's the specific 00:02:54.100 --> 00:02:59.400 that would be blue, a pop-up box will be generated. 00:02:59.533 --> 00:03:05.966 Again, you can select up to three causes to focus on and you 00:03:05.966 --> 00:03:12.499 cannot select natural such as lightning, volcanoes, etcetera. 00:03:12.500 --> 00:03:16.133 So just human caused fires is what we can prevent. 00:03:16.500 --> 00:03:20.233 Then after you select the three fires that you want to focus on, 00:03:20.233 --> 00:03:22.233 then you hit Generate Action Plan. 00:03:25.666 --> 00:03:31.766 Okay, now we get to finally customize our prevention action 00:03:31.766 --> 00:03:32.266 sets. 00:03:32.833 --> 00:03:41.766 So, the general action plan table will populate and the algorithm 00:03:41.766 --> 00:03:49.832 will distribute hours and units according to the most effective 00:03:49.833 --> 00:03:54.166 prevention actions for those causes that you indicated in the 00:03:54.166 --> 00:03:55.666 step before. 00:03:55.700 --> 00:04:03.000 So now your local knowledge must be applied because again, the 00:04:03.000 --> 00:04:11.133 the algorithm does not know if a prevention action is practical 00:04:11.133 --> 00:04:20.199 or if you can complete it or if it's even something you can do 00:04:20.200 --> 00:04:23.766 in that your area depending on different situations. 00:04:24.200 --> 00:04:28.400 So again, you got your category, this is administration in your 00:04:28.400 --> 00:04:28.866 action. 00:04:28.866 --> 00:04:35.899 The GA-41, a quick review that if a prevention action is 00:04:35.900 --> 00:04:41.533 highlighted a GA-41, a GA-42 in this case, these are actions 00:04:41.533 --> 00:04:46.866 that are typically in every prevention plan and are needed. 00:04:47.500 --> 00:04:49.433 Then you go to your effectiveness. 00:04:50.833 --> 00:04:53.233 That is a percentage of effectiveness. 00:04:53.700 --> 00:04:59.533 Green being the most effective and then you have your orange, 00:04:59.533 --> 00:05:07.866 yellow and red. Red being the lowest. And then you got your 00:05:07.866 --> 00:05:08.966 workload. 00:05:09.000 --> 00:05:14.600 Workload is the hours it takes to complete one prevention unit. 00:05:15.066 --> 00:05:24.299 So, for GA-41, one unit takes 24 hours on average to complete. 00:05:26.833 --> 00:05:34.799 Then if you go down again to GA-35 it says the algorithm said 18 00:05:34.800 --> 00:05:37.966 units at 16 hours a piece. 00:05:38.600 --> 00:05:45.833 So, 16 * 18 is 288 hours to be dedicated to this one action. 00:05:47.433 --> 00:05:50.299 OK, the fun things begin to happen now. 00:05:52.066 --> 00:06:01.099 So, customizing, you only have a set number of hours available 00:06:01.100 --> 00:06:03.733 based on the information that you provided when you set up 00:06:03.733 --> 00:06:05.066 your scenario. 00:06:07.400 --> 00:06:11.866 Hours are base hours only, not overtime. 00:06:12.300 --> 00:06:19.966 And these hours are dedicated to your prevention management area. 00:06:21.900 --> 00:06:27.433 And we're not counting base hours off district, off forest, 00:06:27.433 --> 00:06:28.699 off home unit. 00:06:28.800 --> 00:06:34.166 These are solely hours dedicated to do prevention work in your 00:06:34.166 --> 00:06:35.532 management unit. 00:06:37.033 --> 00:06:39.066 So, what is the process? 00:06:39.200 --> 00:06:42.733 Because the hours have already been allocated out. 00:06:43.400 --> 00:06:48.700 So, our general rules of thumb, the first thing that we want to 00:06:48.700 --> 00:06:55.300 do is to scroll down all of the through all of the general 00:06:55.300 --> 00:06:58.933 actions, taking a look at what we have, what's been assigned. 00:06:59.900 --> 00:07:05.566 So, we want to get rid of actions that don't make sense, 00:07:05.566 --> 00:07:09.699 impractical, unnecessary, or impossible. 00:07:09.900 --> 00:07:11.600 We want to set those to 0. 00:07:13.133 --> 00:07:18.166 Then reduce actions that were set too high by the program. 00:07:19.200 --> 00:07:23.500 For example, your GA-35 right there, that's too high, so I 00:07:23.500 --> 00:07:24.666 would reduce it. 00:07:25.866 --> 00:07:30.866 Then we want to add actions that originally were not included and 00:07:30.866 --> 00:07:33.666 that you want or need for your area. 00:07:34.733 --> 00:07:38.266 The fourth thing is increase actions that were set too low. 00:07:39.933 --> 00:07:45.766 Then we would like to, if needed, attach prevention 00:07:45.766 --> 00:07:48.666 actions to certain communities and we're going to go over this 00:07:48.666 --> 00:07:53.366 one in detail in a couple slides because it is a case by case 00:07:53.366 --> 00:07:54.032 scenario. 00:07:54.900 --> 00:07:56.633 Then lastly, hit save. 00:07:58.066 --> 00:08:00.199 So how do we adjust? 00:08:00.533 --> 00:08:06.566 Now that we have the process of how, let's go through the actual 00:08:06.566 --> 00:08:09.799 physical of adjusting some prevention units. 00:08:10.400 --> 00:08:16.900 So, click anywhere on the line item you wish to adjust, it will 00:08:16.900 --> 00:08:18.133 turn orange. 00:08:18.533 --> 00:08:24.266 So, for example in this picture we clicked anywhere on GA 35 it 00:08:24.266 --> 00:08:25.799 populated orange. 00:08:26.733 --> 00:08:29.566 Do not click the use community box. 00:08:29.700 --> 00:08:30.400 Not yet. 00:08:30.400 --> 00:08:34.133 OK so we just want to manipulate our hours here. 00:08:35.066 --> 00:08:40.266 Then it very subtly a sliding bar with a blue bubble will 00:08:40.266 --> 00:08:42.232 populate at the bottom. 00:08:44.133 --> 00:08:48.999 That bar is how many units you could do with that particular 00:08:49.000 --> 00:08:53.200 prevention action with how many hours that you have. 00:08:53.533 --> 00:08:58.399 Right, now that GA 35 is set at 18 units at 16 hours each. 00:08:59.433 --> 00:09:04.633 So, I could slide it up to 19 hours because I have that one 00:09:04.633 --> 00:09:10.366 extra bubble to the right, or I can slide that slider bar to the 00:09:10.366 --> 00:09:15.999 left and then I would get hours back to redistribute elsewhere. 00:09:16.833 --> 00:09:21.766 So if you'd notice in that red circle on the left hand side, 00:09:21.766 --> 00:09:26.466 and I circled that general action leftover hours, it says 00:09:26.466 --> 00:09:26.699 26. 00:09:27.200 --> 00:09:33.200 Now when I slide that bar to the left to add hours, in this case, 00:09:33.200 --> 00:09:36.366 it would be in 16 hour increments. 00:09:36.900 --> 00:09:41.033 I would get more leftover hours again that I could redistribute 00:09:41.033 --> 00:09:41.666 elsewhere. 00:09:43.500 --> 00:09:46.566 And again, you only have so many hours. 00:09:47.666 --> 00:09:50.532 So that's something to be cognitive of. 00:09:50.866 --> 00:09:53.866 When you start to go allocating hours, you want to do more 00:09:53.866 --> 00:09:56.632 actions, but you don't have any hours left to do that. 00:09:56.800 --> 00:09:58.866 You'll have to subtract from somewhere else. 00:10:01.500 --> 00:10:11.666 So let's see if you like all your general actions the way 00:10:11.666 --> 00:10:15.699 they are and you have leftover hours, let's say that 26 hours, 00:10:15.700 --> 00:10:19.566 if you click the specific actions, you can use those 00:10:19.566 --> 00:10:23.532 hours in specific actions, you don't lose them. 00:10:23.533 --> 00:10:25.999 You don't have to use them in general actions. 00:10:26.933 --> 00:10:29.733 But you said you wanted 50/50 split with the hours. 00:10:30.000 --> 00:10:34.100 But it's OK, you can use those in specific actions. 00:10:34.100 --> 00:10:36.933 You just click on specific actions and then they'll 00:10:36.933 --> 00:10:37.999 populate over there. 00:10:39.300 --> 00:10:41.933 And then you also have that primary cause reduction table. 00:10:42.600 --> 00:10:49.733 So as you manipulate the slider bar, there will be a quick box 00:10:49.733 --> 00:10:53.399 that populates above the slider bar that set that will show you 00:10:53.400 --> 00:10:58.133 like the change, the changes in the effectiveness and the 00:10:58.133 --> 00:11:00.499 fires reduced for each cause. 00:11:01.700 --> 00:11:04.600 But you could also do it with the primary cause reduction 00:11:04.600 --> 00:11:04.900 table. 00:11:05.066 --> 00:11:07.832 Then a pop up box will populate. 00:11:07.833 --> 00:11:12.033 That's that picture too there and it'll show you how for that 00:11:12.033 --> 00:11:16.133 general action or even the specific action, how those fires 00:11:16.133 --> 00:11:16.933 will change. 00:11:19.733 --> 00:11:23.499 And then once again, once you like where your hours are for 00:11:23.500 --> 00:11:26.100 the general actions, hit save action set. 00:11:28.666 --> 00:11:35.966 And once you do this, you should have a check above 00:11:35.966 --> 00:11:42.166 general action set because you saved it saying you 00:11:42.166 --> 00:11:44.466 like it and so it should be checked off. 00:11:47.233 --> 00:11:51.833 Now selecting primary causes for your specific actions. 00:11:52.133 --> 00:11:56.533 So as discussed before, you hit the specific action tab at the 00:11:56.533 --> 00:12:00.966 bottom and then you got to work through each of your prevention 00:12:00.966 --> 00:12:01.366 units. 00:12:01.500 --> 00:12:05.700 So that is why I have the three different pictures there because 00:12:05.700 --> 00:12:09.833 you will have to hit that down arrow, select a prevention unit, 00:12:09.833 --> 00:12:13.899 essentially turning it green, I mean orange, and then hit your 00:12:13.900 --> 00:12:17.033 primary causes and then the table will populate. 00:12:17.333 --> 00:12:23.766 Select your fire causes you want to start with, hit your general 00:12:23.766 --> 00:12:32.032 specific action plan and then proceed to change the hours the 00:12:32.033 --> 00:12:34.366 same exact way you did your general actions. 00:12:34.666 --> 00:12:38.466 But you'll have to do this for every prevention unit. 00:12:38.900 --> 00:12:44.666 So same flow and then we get to manipulate, change and customize 00:12:44.666 --> 00:12:46.866 those prevention actions. 00:12:50.433 --> 00:12:57.166 So, after you distribute your general actions and your 00:12:57.166 --> 00:13:04.399 specific actions, you might want to associate ours with a 00:13:04.400 --> 00:13:05.633 community. 00:13:06.700 --> 00:13:11.933 So the decision to assign any kind of prevention action to a 00:13:11.933 --> 00:13:16.799 community or communities should be carefully considered. 00:13:17.833 --> 00:13:23.033 And you should only do this if there is an important reason 00:13:23.033 --> 00:13:27.866 that you need to track this community with this action, 00:13:27.866 --> 00:13:31.499 either general action or specific action. 00:13:33.433 --> 00:13:35.799 So this is the why. 00:13:35.800 --> 00:13:38.833 This is the why we need to take in extra consideration. 00:13:39.700 --> 00:13:46.100 So if that community is covered by a general action that you are 00:13:46.100 --> 00:13:52.000 using throughout the entire management area, then why would 00:13:52.000 --> 00:13:57.333 you need to assign extra hours of that element to the 00:13:57.333 --> 00:13:58.299 community? 00:13:58.866 --> 00:14:01.766 It's covered already, it's under the umbrella. 00:14:03.733 --> 00:14:05.466 Same thing with a specific action. 00:14:05.866 --> 00:14:11.599 If a if you have a community in a prevention unit and the 00:14:11.600 --> 00:14:17.233 prevention unit utilizes a certain specific action, then 00:14:17.233 --> 00:14:20.966 the community is under that umbrella. 00:14:22.800 --> 00:14:29.266 Now, let's say you are working on a CWPP for a specific 00:14:29.266 --> 00:14:36.166 community, then yes, you would want that specific action to 00:14:36.166 --> 00:14:41.232 just be applied to that specific community. 00:14:41.533 --> 00:14:44.533 And I'm just using CWPPs as an example. 00:14:44.900 --> 00:14:46.800 You could do this with any kind of action. 00:14:48.233 --> 00:14:52.966 So that CWPP wildfire community wildfire prevention plan belongs 00:14:52.966 --> 00:14:54.266 to that community. 00:14:54.466 --> 00:14:57.632 So yeah, you want to account for those hours with that community 00:14:57.633 --> 00:14:58.799 and only that community. 00:14:59.633 --> 00:15:01.133 So how do we do this? 00:15:01.800 --> 00:15:09.366 This is where you click that box on the right-hand side, then you 00:15:09.366 --> 00:15:16.366 need to click the arrow on the left hand side and it'll drop 00:15:16.366 --> 00:15:16.932 down. 00:15:19.466 --> 00:15:22.999 Then you hit add community. 00:15:26.933 --> 00:15:32.833 Then a pop-up box will come forward and you can select the 00:15:32.833 --> 00:15:37.733 community or communities to go with this action. 00:15:37.733 --> 00:15:39.033 So you select one. 00:15:39.833 --> 00:15:43.499 In this case I only have one available for me. 00:15:43.500 --> 00:15:46.466 In this scenario, sometimes you have more than one community in 00:15:46.466 --> 00:15:47.299 a prevention unit. 00:15:48.833 --> 00:15:53.099 Select the community you want, add it, and then it'll populate 00:15:53.100 --> 00:15:54.300 in a little table. 00:15:55.300 --> 00:16:01.766 From there you add how many prevention units and the hours 00:16:01.766 --> 00:16:03.299 to that table. 00:16:03.733 --> 00:16:07.466 Then if you have another community, you just add another 00:16:07.466 --> 00:16:11.399 community with those same with that same prevention action. 00:16:11.400 --> 00:16:12.733 Let's say CWPP. 00:16:12.733 --> 00:16:15.833 Let's say you have two communities, 2 separate CWPPs 00:16:15.833 --> 00:16:19.466 That's why you need 2 separate communities shown in this table. 00:16:20.200 --> 00:16:24.333 And then you hit save again that adjusting slide bar at the 00:16:24.333 --> 00:16:26.033 bottom and then hit save. 00:16:28.000 --> 00:16:32.833 But again, if it is covered by general actions or specific 00:16:32.833 --> 00:16:37.833 actions under the umbrella, then you don't need to associate 00:16:37.833 --> 00:16:38.799 those hours. 00:16:39.233 --> 00:16:44.099 But if it's not and it's very specific and you need to track 00:16:44.100 --> 00:16:47.766 that, then add the community, check that box. 00:16:55.333 --> 00:16:59.033 So in addition to everything that we just talked about with 00:16:59.033 --> 00:17:02.633 adding communities, there are a few things that I need to 00:17:02.633 --> 00:17:05.033 mention that we need to watch out for. 00:17:06.100 --> 00:17:11.000 So #1 currently, if you select a community, all those hours that 00:17:11.000 --> 00:17:15.833 the action are now allocated to communities and not the overall 00:17:15.833 --> 00:17:20.499 management unit, which we talked about because we can't say X 00:17:20.500 --> 00:17:25.100 hours of this action is for communities and Y hours is for 00:17:25.100 --> 00:17:26.633 the management area. 00:17:26.633 --> 00:17:32.366 We've talked about that, but the second thing here is when the 00:17:32.366 --> 00:17:37.466 community box is checked, the units for that prevention 00:17:37.466 --> 00:17:42.932 action, actually they zero out and the hours go to leftover 00:17:42.933 --> 00:17:43.466 hours. 00:17:44.533 --> 00:17:49.266 And then when you go in and add the communities and add the 00:17:49.266 --> 00:17:54.199 units to the Community Action, now that it actually pulls from 00:17:54.200 --> 00:17:55.666 the leftover hours. 00:17:56.833 --> 00:17:59.499 So what does that mean? 00:18:00.700 --> 00:18:09.833 It means that if you decide, Nope, Nope, I don't want to add 00:18:09.833 --> 00:18:15.233 a community and you already checked the box and you uncheck 00:18:15.233 --> 00:18:19.499 it or delete the Community Association and then uncheck 00:18:19.500 --> 00:18:19.800 it. 00:18:20.400 --> 00:18:25.000 Those hours and units don't get repopulated back in. 00:18:25.400 --> 00:18:30.133 You'll have to manually go click the prevention action and 00:18:30.133 --> 00:18:32.533 move the bubble to add the unit. 00:18:32.533 --> 00:18:35.733 So just something to be cautious about that. 00:18:36.066 --> 00:18:39.866 Those don't automatically get populated back in. 00:18:39.866 --> 00:18:44.332 If you as soon as you hit that check box, those hours go to 00:18:44.333 --> 00:18:49.133 leftover and there's just no, we don't have a way to remember 00:18:49.133 --> 00:18:53.833 if it's unchecked to repopulate those hours, you have to do it 00:18:53.833 --> 00:18:54.433 by hand. 00:18:54.433 --> 00:18:56.666 So that was item number two and three there. 00:18:58.233 --> 00:19:02.333 And then the last thing only associate a community or 00:19:02.333 --> 00:19:06.866 communities if the action is only going to happen with the 00:19:06.866 --> 00:19:09.999 community and affect only the community. 00:19:10.000 --> 00:19:11.866 And we talked about that in detail. 00:19:12.200 --> 00:19:16.266 So just little things to be to be cautious about and to 00:19:16.266 --> 00:19:20.632 experiment with and, and, and see if that actually does 00:19:20.633 --> 00:19:22.133 happen and, and work. 00:19:22.133 --> 00:19:27.233 So, you get the full gamut of what a adding a community 00:19:27.233 --> 00:19:28.533 actually does. 00:19:35.466 --> 00:19:40.699 OK, so when all the GAs and the SAs your action plans are 00:19:40.700 --> 00:19:44.833 the way you like it and the way you want them. 00:19:44.833 --> 00:19:49.899 And you've, you're done saving and you decided that this is 00:19:49.900 --> 00:19:54.200 really what you want to do on that main page. 00:19:54.200 --> 00:20:00.200 Again, that main table, you're like, wow, I've created several 00:20:00.200 --> 00:20:03.933 different scenarios, customized a few. 00:20:03.933 --> 00:20:07.199 I have my benchmark to compare and contrast. 00:20:07.433 --> 00:20:09.433 Which one do I do? 00:20:10.400 --> 00:20:12.533 So how do you decide? 00:20:13.233 --> 00:20:17.033 Well, there's several ways to make this decision with 00:20:17.033 --> 00:20:20.699 different tables that are set up within WPSAPS. 00:20:21.100 --> 00:20:24.200 So again, develop a couple different scenarios and you can 00:20:24.200 --> 00:20:26.800 compare and contrast which is the most effective. 00:20:27.266 --> 00:20:32.266 The easiest way to compare the effectiveness of a scenario is 00:20:32.266 --> 00:20:37.266 to look at the number of fires, the total fires prevented and 00:20:37.266 --> 00:20:40.632 decide which one prevents the most fires. 00:20:44.466 --> 00:20:48.332 Because each of these scenarios you should have manipulated your 00:20:48.333 --> 00:20:50.866 actions differently to get the comparison. 00:20:52.466 --> 00:20:57.399 And then we also have the primary cause reduction table 00:20:57.400 --> 00:21:02.233 that you can also click on and and look at all the 00:21:02.233 --> 00:21:07.333 differences there percentage wise of what fires are being 00:21:07.333 --> 00:21:09.966 prevented and percent reduced. 00:21:12.033 --> 00:21:18.266 And then lastly, in the report section that we'll go over in in 00:21:18.266 --> 00:21:22.932 future units here in the course is the reports. 00:21:23.233 --> 00:21:27.033 And in the reports you have the annual prevention effectiveness 00:21:27.033 --> 00:21:27.499 summary. 00:21:27.866 --> 00:21:33.632 So you can go into reports and get a visual of that annual 00:21:33.633 --> 00:21:38.633 prevention effective summary results there and the 00:21:38.633 --> 00:21:42.199 suppression costs averted per year. 00:21:42.200 --> 00:21:45.400 That's the big tickler right there is per year. 00:21:46.833 --> 00:21:50.433 So you can pull those different tables up for the different 00:21:50.433 --> 00:21:54.033 scenarios and see which one has the biggest suppression 00:21:54.033 --> 00:21:54.866 costs averted. 00:21:57.066 --> 00:22:01.966 But most importantly, even though it a scenario might a 00:22:01.966 --> 00:22:07.399 customized scenario might have the highest fires reduced, you 00:22:07.400 --> 00:22:11.600 gotta ask yourself, is this scenario realistic? 00:22:12.666 --> 00:22:13.532 Does it fit the budget? 00:22:14.466 --> 00:22:18.566 Do I really have those hours that I said I had available to 00:22:18.566 --> 00:22:20.399 complete this plan in full? 00:22:21.733 --> 00:22:26.666 If your answer is no, then maybe you need to redo a scenario, 00:22:26.666 --> 00:22:30.999 change hours, change budget to make it realistic and 00:22:31.000 --> 00:22:33.566 ultimately you can accomplish it. 00:22:36.400 --> 00:22:42.200 So experiment with playing with the different prevention actions 00:22:42.200 --> 00:22:47.466 as prevention folks and those getting into prevention. 00:22:47.800 --> 00:22:52.200 There are so many different prevention actions that we can 00:22:52.200 --> 00:22:55.400 be doing and implementing in our programs. 00:22:55.600 --> 00:23:00.100 So take a look at that table, take a look in the student 00:23:00.100 --> 00:23:04.933 guide, look at all of those different prevention actions to, 00:23:04.933 --> 00:23:06.899 to see what's available. 00:23:06.900 --> 00:23:07.733 What can you do? 00:23:08.700 --> 00:23:12.400 It's, it's not just standard parades and, and, and patrols. 00:23:12.400 --> 00:23:15.033 There's so many more options you can choose from. 00:23:15.700 --> 00:23:16.966 Select those options. 00:23:17.200 --> 00:23:18.466 Try something new. 00:23:18.733 --> 00:23:19.833 What if I do this? 00:23:19.833 --> 00:23:20.866 What's the outcome? 00:23:21.600 --> 00:23:24.666 And it'll just make your prevention program a 00:23:24.666 --> 00:23:25.932 well-rounded program.