 Good afternoon everyone. I'm going to do a quick audio check online if somebody online can come off mute and make sure you can hear me. Sound good, but okay. Thank you. All right. Well, we would if I leave my mic on, we will call the meeting to order. I have 102 and this is the 911 advisory board. My name is budge courier. I'm with public safety communications. I'm the chair of the board. You'll notice that in person. Those of you in person, the the table is rather vacant, but we do have some folks participating online. So the first topic is a call to order and roll call. So I'll go through the roll. Rodney Ellison with CHP. Kurt Wallace. Here. Thank you. Mark Chase. Present. Chair Fingert Braun. Here. Thank you. Rebecca Ramirez. Here. Thank you. Jennifer Gonzalez. Here. Thank you, Chief. And Chief Andrew White. All right. So we have we have six, so we do have a quorum. There are a few vacant positions. If you're wondering, the CFCA position is vacant. There's a Kalnina position vacant. And a CSSA position vacant. So I definitely want to take time to welcome Chief Gonzalez. So welcome to the advisory board. And we appreciate being here. If I'm not mistaken, you were appointed yesterday at 5pm. Close. Yes. So talk about a quick turnaround. So welcome aboard. Thank you. All right. Okay. Next topic on the agenda is approval of the previous minutes. So obviously those that weren't in person at that meeting, we understand that you won't be able to vote on this, but the meeting was held in person and Sacramento. So do we have any discussion for edits to the minutes for many of the board members? All right. Do we have a motion to approve? I move. Thank you, Mark. Do we have a second? I'll second. All right. Was that Kurt? No. Chief White. Chief White, thank you. I don't have a screen in front of me to see which little name is blinking. So all right. So we'll do a roll call vote of the minutes. Chief Ellison's not present. So Kurt Wallace. Yes. All right. Mark Chase. Yes. Sheriff Braun. Yes. Rebecca Ramirez. Yes. All right. Chief Gonzalez. I'm staying. All right. And Chief White. Approved. All right. So the meeting minutes are approved. Move on to agenda item number three. And I probably want to go into this one a little bit since we have a new board member for close session. There are some very specific criteria that need to be met. And under the statute, the board members can solicit the board to enter into closed session before we even meet due to certain things that cause us to go into closed session under government code section 11126. And so we have not received any notification. And I don't think we have any pending items for closed session, but I'll bring it up to any of the board members if they have a reason for us to go into closed session to discuss anything. This is Chief Ellison. I am I am present. Oh, thank you, Chief Ellison. All right. So make sure we'll make sure we update the role. So we are at 100%. Wow. This is a very thank you all for participating. Appreciate that. All right. So do any of the board members have anything for closed session? All right. Hearing none. We'll move on to agenda item number four. This is our legislative update. So we will have Chris Hacker from Cal OES give us an update on any legislation that's related to 911 or just things that this board might want to be tracking. So Chris, are you online and available? I am here. You tried to throw me another curve ball with that no closed session thing, but I was ready for it this time. Well, we're a little dynamic here. It's the way we roll. So take it away, sir. All right. All right. So hello, everybody. My name is Chris Hacker. I'm from Cal OES legislative and external affairs. I'm going to give you a rundown of some bills that that passed recently and the federal bills were tracking. There is no between sessions right now. So there's no pending legislation to really talk about. So with that, let me get into it. A couple of bills that passed that have been signed by the governor. We've got AB 44. That's the CLETS system bill involving tribal police. This bill requires CHP to grant access to the CLETS system to a law enforcement agency or tribal court of a federally recognized Indian tribe that meets certain qualifications. This bill was signed by the governor on October 10th, and we'll go into effect on January 1st. Next up, we got AB 988, the Miles Hall Lifeline and Suicide Prevention Act Veteran and Military Data Reporting. This bill requires an entity seeking monies from the fund to also include a number of individuals who use the service and identified as veterans or active military personnel. So that's more of an on the 988 side, but still we'd like to give you guys updates on that kind of stuff. That was signed by the governor on October 8th. All right. On the federal side of things, as most of you know, federal bills kind of move differently than state bills. Sometimes they don't move at all forever. Sometimes they move in like three days if it's a funding bill. So it's a little different. There might not be a lot of changes here compared to state bills. All right. HR 369, that's the NIST Wildland Fire Communications and Information Dissemination Act. This bill requires research on public safety communication coordination standards related to wildfire wildland firefighting. This bill is still in the house of first chamber. Next bill, HR 1353, Advanced Local Emergency Response Telecommunications Parity Act. This bill requires the FCC to facilitate the provision of emergency communication services in unserved areas. So that includes 911 and emergency alerts. That bill is in the Senate at this point, so second house, second chamber. HR 4851, 988 Implementation Act 2023. This bill provides for improvements in the implementation of the National Suicide Prevention Lifeline. This bill is still in the house, so first chamber. And finally, another 988 bill, HR 498. This bill requires the Substance Abuse and Mental Health Services Administration to undertake efforts to protect the 988 suicide and crisis lifeline from cybersecurity threats. And this bill is still in the first chamber. And that's it. That's all I got for you all this time. Happy to take any questions. All right. Thank you, Chris. Any questions from the board on any of the legislative items that Chris briefed out? All right. Any bills that he didn't discuss that you want to add to the list? All right. Any questions from the public on the legislative briefing? All right. Seeing, hearing none. Anything online? All right. We'll move on to agenda item number five. So this is the time in our brief where we ask the 911 branch to come up and give us an overview of what's going on in the branch. Obviously, there is a significant amount of activity. So Mr. Troxell is going to go through that for us. There's a lot of information. So as he goes through each item, we'll have him just pause and answer questions from the board as we go along and then we get to the end. We'll entertain any comments from the public. So Mr. Troxell, take it away, sir. All right. Thank you. Good afternoon, everybody. Paul Troxell, 911 branch manager. Here are the topics that we're going to be briefing out today. As Budge had mentioned, we've got a lot of information to share with you. I believe total, we've got about another 34 slides seriously of data. So Chief Gonzalez, welcome to the advisory board. We're going to start with 911 outage. And I just want to say for any of the board members, as we're going through any of this data, if you have questions, please feel free to stop us and ask. The first slide here on 911 outage is our legacy 911 system. This is, this graphic depicts our ecosystem in the legacy side. So for network outages, what these outage minutes are showing is a community member was not able to get into 911, either at a specific area or a general area due to outage, network disruption or PSAP being offline. The second graphic here is customer premise equipment or call processing equipment. This is the equipment that the dispatchers used to answer 911. These outage minutes show that CPE is offline at the PSAP. So the 911 network worked, all of the community dial tone was there, the capability to dial into 911 was there. However, the PSAP was out because their CPE was not online. And this last graphic here shows legacy location outage. So in this particular outage, we're able to deliver voice, but the Annie alley, the automatic location, automatic number information is not able to get displayed to the dispatcher. So the challenge there for the dispatcher, the dispatchers are very used to when you answer 911, they get Annie alley up and you see my callers calling from 123 Main Street, they can confirm what the caller when location is out, they don't have that and they may not receive the caller's telephone number. If that call is lost, they might not be able to call that person back. So now you have to interrogate that caller to determine exactly where are you. So for the benefit of Chief Gonzalez being the newest board member with under 48 hours of a board member experience, I just really wanted to kind of go in depth. I'll pause quickly if anybody has any questions on the legacy side. My only question would be text 911 is in this under wireless or is it going to be separate? It's going to be under the next gen slide. Thank you. So specific to your question, Chief, text to 911 is now delivered under our NG 911 services agreement. So it's no longer represented in the legacy slide. Thank you. So here this graphic depicts our next generation 911 ecosystem. Paul, I think Mark had a question. Oh, I'm sorry. Yeah, Paul, can you just explain for July? Is that a typo or was there a significant difference between the other months? I don't believe that is a discrepancy. I believe that is an accurate depiction for CPE outages. Okay. And do you have any idea why it was so much greater in July? Was it just like a cluster of PSAPs that were out or? I don't have that answer, Mark. I can definitely get with the team and we could drill down on that. Yeah, if we could just follow up, it just seems like it's so significantly greater. It would be good to know. Thanks. Yep, absolutely. Just taking a quick note. Okay. So our next generation 911 ecosystem here, our first area is aggregation. So in the next generation 911 system, the carrier hands off a 911 call into our NG 911 service providers network at aggregation. For the last quarter, we had zero minutes of downtime. And I do want to point out we are defining downtime as service disruption. We have built redundancy into our network to where we could have a component go down and another component can pick it up or another vendor can pick it up and deliver that call to the PSAP. So we could have an aggregation site go offline. But there's another aggregation site somewhere else that picks up all of that traffic and gets the call to the PSAP. Our NG 911 core service, this is the brains, the intelligence behind NG 911. Again, the way our network is designed, we've got our regional service providers, they have redundant core services. And in the event that their systems fail, they automatically fail over to Autos, the prime network service provider, who has redundant core services to where that call can then be delivered. So again, we can experience failure, but the calls are still being routed and answered at the PSAP. Location outage, I do want to point out historically in next gen 911, we have not had location disruption. In about June, we started really in good honest effort deploying our alley emulation service. And the Tiger team we'll talk about in a few minutes. Part of that responsibility, the Tiger team was to get the alley emulation boxes installed in that service turned up, transitioning from legacy anti alley over to NG 911 location service. Through that process, we did experience some outage. As you see July 900, August 51, and then September 616 minutes. When you aggregate that across the state, that is minimal disruption in the big picture. And it was similar to legacy 911, when that location service is offline, the dispatchers are still able to get voice, they just don't get location or number. So all they have to do is interrogate the caller, get that information, you could still get a call for service enter. Then we have network outage. And again, here we've got multiple network connections through the region, multiple network connections through the prime network service provider. We can have one of those network connections go offline. However, redundancy is built into the network. So there's no service disrupting outages there. And then with cloud CPE, the difference here is in the previous slide, that was our legacy CPE. In this slide, this is showing our cloud CPE. In August, we did have 150 minutes of outage, and it was identified immediately and the vendor was able to get on it and get that rectified and get that PSAP term backed up. So I'll pause here for any questions. And then the last graphic here is our text to 911. In July, we did have a network event that did cause text to 911 to go offline only for those PSAPs that have integrated text to 911 service. And just for the audience, there's a difference. We have integrated where text to 911 comes through your existing customer premise equipment or can be delivered on what we call an over the top solution or a third party application outside of your customer premise equipment, your Motorola Vesta, your Viper, Intrada, whatever telephone solution you have. So for this service disruption, it was only the integrated PSAPs that had that disruption. The provider identified it immediately, communicated with the PSAPs immediately, and as soon as they were able to bring that back online, they got to turn back up. And there was a lot of really good follow up with Cal OES and all the PSAPs that had suffered that disruption. So I'll pause for any quick questions about outages. Okay. So this is our placeholder slide. Again, just representing our statistics. As we come into the end of the year, we'll be looking at getting this refreshed to see how we performed in 2023. 26 million calls were the largest call volume state in the nation. I believe Texas is now up to 19 million calls. I believe is their most recent. They're the number two state in the nation. So we're very busy. Hence the importance for us to get next gen 911 deployed and get on an improved technology network. Okay. Jumping into the Tiger team. Tiger team was formed to focus on the AT&T maintain PSAPs. We've got 375 AT&T maintain PSAPs throughout the state of our 441. So what we wanted to do is AT&T had agreed to partner with our engine 911 service providers to go conduct operational readiness testing and deploy alley emulation service. And that was going to get CPE configured, make sure transfers happen, calls can land, location could land and get that PSAP ready for the next phase of engine 911 transition. So our OES team did a fabulous job coordinating a schedule. We had some of our OES folks were in charge of scheduling. Some were in charge of notifying. Some were in charge of actually managing the bridge and leading these efforts and they did a fabulous job. We had 60 working days and we had about 320 PSAPs that were hit during that 60 working days. Of those 248 passed, all of the operational readiness testing and are ready for the next steps. Those that didn't pass of that 320 were identified. What needs to happen in the appropriate vendors going back to fix it or the PSAPs been identified to get their IT or facility folks in there to make whatever readiness needs to happen for the next step. Those remaining PSAPs that AT&T maintains, the engine 911 service providers are working with AT&T to get those ready for the next phase. And we expect all of this work to be done about February of 2024 and have at least these 375 PSAPs ready for the next phase. The remaining PSAPs, those maintained by Frontier, Carousel, Motorolla, Direct, so on and so forth, we're working with those vendors directly to do the same operational readiness testing. We have a large group of PSAPs that will be finished before the end of this calendar year and the rest of them will be finished in probably quarter one of 24. So as I close out Tiger team, I do want to give a huge shout out to AT&T, our engine 911 service providers, both the regions in the prime and the Cal OES team. They did a fabulous job coordinating, orchestrating the first couple of PSAPs. They went in and they trained, they worked through how to do this. And by the end, they were literally doing it in their sleep. It was flawless and extremely proud of the hard work that everybody did. So I'll jump into our employment update. And this is really where the meat of our meeting is going to be today. So this graphic depicts all of the regions that we have identified. The purple region is our northern region. That gold in the middle is our central region. L.A. is white. L.A. County is white. And then southern region is green. And if you see Imperial County, Tuolumne County, El Dorado County are also white. Those are counties that have live engine 911 traffic deployed today. Los Angeles is its own region because they are taking about the same workload as the other regions themselves. And we tried to balance it out to where each region was about equal workload. So we've got those four counties. We've got 19 PSAPs that are either taking live traffic or direct engine 911 transfers today with a plan to work through to get a few more by the end of this year. And starting in 2024, we'll be walking through our pre-migration plan to get prepared to continue to deploy engine 911 across the state. So our next steps, we have to do what's called pre-migration testing. And in Tiger Team, the focus there was getting CPE ready. Now CPE is ready. Now we can focus on getting the network ready. So with our network design, we've got a region provider and a prime provider with failover capability. So in pre-migration, we want to test that failover. We want to test the ability to alternate route a few times. And why I say that is if we go through this exercise with each provider 10 or 15 times, we'll build in that workflow. And after that, that workflow is there. We can randomly test it to make sure that that alternate route is still, the workflow is still in place and people know what they're doing, but we don't need to do it at each and every PSAP. Transfers, PSAP transfers. This part of testing is not about transfer testing, but we do need to test transfers on a limited scope. So we might only be at your PSAP testing five or 10 or maybe the top five or 10 transfers that your PSAP may have. As an example, the city of Sacramento, their top two transfers are going to be Sacramento County and Sacramento Regional Fire as an example. So we would want to test those in this pre-migration testing, but we're not going to go all the way down to find that one transfer that you do one time a year because that's just so time intensive. We will make sure that everybody has that ability to test. That's at bottom bullet there. We do have test numbers available and we'll make sure that the PSAPs have that instruction on how to conduct their own testing so they can go through all of that detailed transfer test. So what the branch is working on now is we will be building a pre-migration testing plan in a schedule and what we want to do is create kind of a wave and I'm using generic dates here. So in mid-January we want to start pre-migration testing and in mid-February we want to have migration of carriers happening. So the first couple of weeks we're going to be testing PSAPs and if they're successful about four weeks later we're going to come in with a carrier and start migrating traffic. So we have this wave going throughout the state all next year. If our math is accurate now this slide shows that we're starting about February and that will take us through November for testing and then if we start migration in March that will take us through about December for migration. We hope to be able to speed some of that up. Hopefully we'll get through some of these PSAPs with the pre-migration testing and be able to get carriers in place to be able to migrate faster so we can get a little closer to a completion date of November. And then the the branch we're going to manage is like we did the Tiger teams. We're going to have a team set to do PSAP notifications. We're going to have a team set to do all the scheduling and coordination with the PSAP and the vendors and the OES team and whomever else may be needed and we're going to do all of that tracking and we're going to be driving that schedule as we move forward. And then we recognize we as we analyzed our Tiger team we felt we did a pretty good job communicating and in the beginning we got some feedback that we we could have done a better job. So what we're doing is we're building a communication plan. So first thing that we're working on I've got a team who's developing an information sheet to outline what all of this is. Outline what's that testing process? What are you going to expect when that team comes in? In identifying we're probably only going to be able to test the top five or top 10 percent of your transfers. We're not going to be able to test them all. But here's how you can test them and make sure that the folks have everything that they need to do that. We're also going to identify escalation points. We understand this is new. This is scary. This is different. Change is different. Change is difficult. Somebody talked to me this morning and gave me an analogy I'd like to share. In your PSAP you have new telephone equipment today. It may be three years old, five years old, but it's new. It's newer, right? In reality what's sitting behind it is 40 or 50 years old. The GUI you're looking at is new. The technology is not. So what we're doing is we're taking that old rotary dialed telephone and we're moving that aside and we're bringing you a new Apple or Android smartphone with the newest operating system that's going to give you so much more capability. That's what this plan is about. So we want to develop those talking points on an FAQ to talk through the fears and concerns that some of these PSAP folks have, especially for the line level dispatcher. What's going to be different? We've heard it for years. When I answer next gen 911 call, I'm getting pictures and video and sound and this and everything else. It's not true. We want to put out the facts and give the folks the information that they need in order for them to be successful, reduce stress and help this project be successful. So we're working on developing some FAQs. We're doing some outreach now. So anybody in the PSAP community and for the board members, if you know folks who have questions and concerns, please have them contact us. We want to identify those. In the beginning of COVID, Budge and I did some town hall, virtual town halls and we had great success there. We were asked to bring those back. So in January, we're going to start queuing up some virtual town halls and talk through steps. We don't want to talk through the entire plan. We want to build this and answer questions. We want folks to come with questions and facilitate discussion because they think from what we're hearing, there are folks who are scared and there are folks who are concerned and there's folks who are excited. So we want to answer all of their questions and demystify all of this. So I'll pause here for any quick questions. So that's a good segue for the board. That's our next steps if you're wondering where Cal OES as a branch is headed next, pre-migration testing and then bringing carriers live into the network as to what's coming next. So we're going to do a lot of communication and outreach on this, but come mid to late January and then certainly into February, we will be at pace with this process as well. So I want to make sure the board members, if you have questions, things you want us to specifically address, include in the communication feedback you're hearing. We'd love to hear from you either today or tell us later. Get the information to us so we can make sure that we build this frequently asked questions and when we get the communication plan to align with the questions that are out there. So any of the board members have any questions or feedback on that? It's Mark. I have some questions. Okay, Mark, go ahead. Question number one of 80. Go ahead. Got a couple. So looking at the success rate of the Tiger team, so you're saying basically 77% of PSAPs passed and you're saying that 23% of PSAPs failed. If I did my math correctly, right? We've got 92 PSAPs with an issue. Yeah, it's about correct. Yes. Okay. So as far as the carriers, are there any penalties or punitive measures that would be employed because they're being paid to ensure this equipment is operational, but basically a quarter of the PSAPs are not operational in some capacity. So some of that failure is not equipment. It could be not enough network coming in. We don't have enough network redundancy. We're working with the NG Nemo Month Service Provider to bring that in. Some of it is older equipment where we have an LPG that needs to be deployed. And then some of it is CPE configuration. So the CPE is working, but for some reason we couldn't transfer a particular call. So there's still a little bit configuration work there. Okay. And then my other question was, so when you talk about migrating traffic, are you saying if we can just dump it down to my level potentially? So would it be like a region goes, like you're saying say like a few counties would go live with T-Mobile to start and then T-Mobile wireless and then Verizon wireless next or and you're saying it would be sort of like a bifurcated thing where part of the traffic is migrated over to next gen, but part is not. So I'll break it down for you and let's focus wireless only because I think that's easiest for this example, Mark. So we've got our four major wireless carriers. We've got T-Mobile, AT&T, Verizon and US Cellular. So in our migration plan, what we would like to do is take everybody on a PSAP transfer cluster. And I'm going to use Placer County as the example. We have five PSAPs in Placer County proper and then Placer County likely transfers to El Dorado, Sierra County, Nevada County, Sacramento County as a part of a transfer cluster. So anybody that those Placer County agencies would transfer to also need to be ready in the next gen world. Their PSAP has to be ready because they need to be able to accept a next gen 901 transfer if we want that transfer to be on net if we don't want a 10-digit transfer. So to your question, Mark, what we would like to do is take that entire Placer County group of PSAPs and cut all five PSAPs on the same day with T-Mobile and then maybe come back a couple of weeks later and do Verizon. A couple of weeks later come back and do US Cellular and then AT&T. And then those PSAPs that can accept transfers, we'll be getting transferred next gen 901 calls and then we will be scheduling their PSAP cluster in kind of a week or two later to give them direct calls. Does that make sense, Mark? Yeah. So you're going to basically, if I'm hearing it correctly, it's going to be a regional approach and you will, like you said, do one carrier at a time basically and then give it a few weeks and then move on with the next carriers. So in order to meet the end of the year schedule, the most efficient way to do it is to do that regional approach. There may be times where we can't because you have a PSAP that isn't ready to accept the next gen 901 transfer. So we may have to come in, give everybody else around them an NG901 cut, and then we do a 10-digit transfer to that other PSAP until we can get them ready. We have to take that as a case-by-case basis, depending on where they are in the schedule and how close we are to the end of the year. And why would they not be able to take the transfer? Is it outdated equipment or they don't have the box installed or? So it could be a CPE, it could be not enough network and it could be a configuration on the CPE. There's quite a few different variables there as why they wouldn't be ready. But again, what we're trying to do is we build this plan. We want to get everybody who is ready at the beginning of the year. So those who aren't ready, he gives us time to get those PSAPs ready. So as we move throughout the year, everybody should be in the green and ready to go. Okay. Thank you. All right. Any further discussion on this from the board on this? All right. So we're about midway through his update. So pause for the public as well just because you may forget as we get farther along. All right. Not seeing her here in any comments. Okay. Continue on. Sorry. So we're going to shift gears now and talk about CPE. Go ahead. Yeah. So Cloud CPE. We've got some good news here. We've got Motorola, Carbon, and Intrado currently in the lab. The manufacturers are in the lab and we've got AT&T in the lab with Motorola and Intrado together. So as Motorola and Intrado direct move through approvals, AT&T is going to be right in there with them. We are very close. We're expecting by the end of the year we should have a good majority of testing completed and then we have set some time in mid-January aside to get dedicated resources for everybody, all the NG providers, all the CPE providers, everybody to get all of this testing complete and get these folks through lab and available to sell. We still currently have Lumen, Autos, and NGA are available for sale in the state and our goal is by the next advisory board meeting in February we'll have these three manufacturers through with some resellers through the lab and available to go in California. I'll pause here real quick for any CPE questions. Anything from the board? I have a question. Sorry I don't think you can see the hand raised. I think I heard you correct but I want to clarify because it was mentioned at the last meeting. So with respect to AT&T and Motorola they're now joined going through because I think at the last meeting you mentioned that not only does the vendor have to go through but the reseller does at least that was my understanding at the last meeting but now they're all in sync. So they still have to go through separately Chief so Motorola Direct as a manufacturer is moving their product through. In parallel AT&T is also in the lab they have their own equipment set up their own team is doing the configuration and running through the same test script. So yes they do have to go through separately but they're doing a parallel process. Thank you. And Paul I've got one more question. I may be jumping ahead but I think the issue so far has been in deployment right with NGA some of the some of the carriers has been the connections issue right getting connections run into the PSAPs. Do we have any update on that? I think the last update I had Budge is we were looking at the end of this month to have everything in place. Yeah we've we started this conversation with the next-gen providers on connectivity and there was confusion which we were confused about the confusion but the the current timelines we have we've given them till December 15th to finish all connections. You can imagine the number of connections that are involved because we have four different next-gen providers and we have 19 different well I guess we're down a little bit we're probably down to 17 different CPE providers and they all have to be connected to each other so you start doing that number of spider web connections. That's the process we're working on right now and we should have that completed by we want it completed by the end of this month. It may trickle a little bit into December that will clear the roadblock that exists now on actually deploying the ones in green out to the field. So NGA, Autos and Lumen will now be able to fully deploy so all of you that are working with Janae's team on those deployment cycles we're going to clear that barrier so beginning of the year you can expect full speed ahead on all those. And that's your question. Yeah that'll be statewide. Yep. Okay great thank you. Yeah it's going to be a very busy year for Janae and her team. Team of one right now but we're getting there some more resources as well but yeah that's where we are. Okay so this is our current CPE installation state we've got one that was the cloud CPE solution that was deployed so far this calendar year. A lot of this is back to that network discussion that we just had as soon as all of the network is in and everything's validated these numbers should start to soar. This is the slide I really want to bring attention to. The reason cloud CPE is so important to us this has to be our number one strategy next year and Janae and her team are going to be working hard. We have 206 CPE solutions that are year seven or older. So in year seven year eight arguably we're fine. Close it's not ideal but we're fine. You know think of it as an old car. Eight-year-old car you're okay. Start to get into an 11-year-old car with a couple hundred thousand miles on it. You might not want to take a cross-country trip. So we're really targeting these PSAPs who are in year nine, 10, and 11. That's Janae's team's focus. They're doing a communication plan. They're working with them. They're looking at the cloud CPE providers that are available and that are currently in the lab and we're coming up with a strategy on how we can get those systems replaced and get that total number reduced and eventually that total number annihilated. Once we're on cloud the maintenance of these systems becomes much easier. So I'll pause for any quick questions on the age any questions about the CPE on this graphic from the board. Okay fiscal and operational review. This is what Janae's team does on a regular basis. They go out they do an analysis of a PSAP. They take a look at the PSAP folder. When were they funded? What telephone system do they have? What network do they have? What's their performance? Who are their points of contact? How many positions? Everything. They put all of that information together and then they make an appointment with whoever the PSAP manager or whoever's in charge of that PSAP. They go out and they meet with them and they do a fiscal and operational review where they take a look at okay you've been funded this amount of money. Is your equipment there? Is it serviceable? Is it working? Did you get what you want? You had extra money? Residual money? You bought purchased monitors or chairs or you know a mapping system or whatever. Is that working for you? Is there anything else that you need? And here's what to expect the next time you get funded. During COVID we suspended the fiscal and operational review mainly because these work best when we're able to sit and go face to face. We tried to do some virtual fiscal and operational reviews but they're just it's not the same. That feel wasn't there. We started to pick them back up. The team did 22 for this year then we started the Tiger team and we needed the resources of Jenae's team to support Tiger team so we suspended the four process throughout the summer. Now that the Tiger team is done we're going to be kicking these back off and then as we look at our pre-migration and migration plan in 24 we're looking at other resources that we can bring in to support so we can keep Jenae's team focused on fiscal and operational reviews and CPE deployment. Ideally we want to do about 30 of these a quarter when we're when we're at full staffing and at pace that's about the mark we should be hitting. And then I do want to give Jenae's team a plug. She has increased her staffing level by 100% with a hiring of one. She's now up to two. She's got a total of five. We are working to get a third vacancy filled. We're working through the HR process now and the other two positions are hopefully going to be posted soon. So if anybody ever wanted to be a PSAP advisor, Jenae's a really great manager to work for. Please follow the Cal OES jobs link but we are hoping to get this team fully outfitted, fully staffed probably by March or April. But her current team they're working together. They're doing a lot of training. They're getting set. They've got the running shoes on and they're ready to hit the ground in 24. So that was my last slide on any CPE related issues. If anybody from the board has any questions. Any questions from the board? Go ahead. Perhaps education or clarification. Back to sorry maybe slide 13-14 when you were talking about the frequently asked questions and education, YouTube videos, that type of thing. Who is the facilitator for that to ensure that the actual end users, the dispatchers, call takers, operators, whatever their title. Their questions could be meant to reduce anxiety because I know when you say test and check things instantly there's anxiety. So just and having been involved in changing systems or updating systems, there's a freak out period right when they think they're being questioned on the quality of service because they're giving their best. Right. So if folks in your PSAP have questions or concerns, there's a few avenues, they could work with their county 9-1-1 coordinator. We have regional task force members. Gus is familiar with those task force members. They can reach out to the 9-1-1 branch direct, Andrew Mattson or myself. They can send their questions, concerns. What we are going to do is we're going to start collecting and the way I envision this is we get like five concerns or questions and we put out a video. I don't want to overload it. I want to do like 15-minute video snippets and we have a team member who came from the PIO's office and she's capable of doing all of this and helping get everything set for us and then on our website we want to post the YouTube link and then here's the five questions this YouTube video covers and then we want to make those links available so if you or somebody in your PSAP hears that there's concerns then you can go, hey OES has these videos. See if that answers your questions. If not, reach out to us and then we can get them identified. Great thank you. All right. So a couple of years ago the Long Range Planning Committee, which is a subcommittee of the advisory board, in a meeting they were talking about anecdotal shortages at PSAPs across the state and the more and more the conversation started the more and more everybody started to realize well I'm sure you're sure we all have these challenges we can't recruit, we can't retain, we can't train. So somebody on the LRPC asked for Budge and I to look is there's something that the 911 branch could do. So we sat down and we thought well let's conduct a study to validate what's happening. Once we have valid data then we can turn that back over to the PSAPs and say here's our findings this may help solve your problem. So in June of this year this contract was executed. 911 authority was awarded the study portion of this contract. They put the links out at the end of September and through the time that their data collection link was available they received 571 surveys from line level dispatchers or dispatchers who were not in a manager position. There were two surveys. One was we wanted to hear from the line level dispatcher what's happening and then the other survey was what's happening from the manager level. How many folks do you have? What's your budget? What's your overtime? How long are you retaining people? Questions like that. That manager survey we had 25 surveys completed and about another 50 that were partially completed or almost fully completed. So the 911 authority team is going back to those 50 PSAPs trying to get enough data collected to where they can use it and we think that 75ish survey result for the PSAP managers will be enough data for us to analyze. They did give us a high level briefing on the line level information that they've collected and everything that we have felt and thought has been validated in these surveys and they did do a wellness component and I think from a wellness perspective as a PSAP manager we're going to see data where our folks in the PSAP I think we're going to need to really focus on some wellness. You know our folks are dealing with with stressors outside of the workplace you know whether it's kids or divorce or finances or personal health family health issues and bringing those stressors into a stressful environment which is creating a larger cumulative effect. So we're very excited about this. The key action dates our milestone dates are identified there. We're hoping by the February board meeting we're going to have a good draft to be able to present the advisory board members and then by May we're going to have that final study completed and ready to go public to all of the PSAPs. So we've got a lot of data. One of the folks on this team is out of Chicago and she does a lot of nationwide work and has worked in the 911 industry for many many years and what she is seeing is consistent data across the nation especially when it comes to wellness. So we're very happy with the results so far. Any questions about the study from the board members? Paul I would just say there's some feedback from the managers that I've talked to I guess the surveys take about two to three hours to complete on average and that's part of the issue of why you're not getting more responses is it's it's a significant time commitment. They have to pull a lot of statistics and facts and things like that. So just for the future surveys if there's somebody either streamline that or pull people together in person maybe to have them completed together you know on a like a half-day training day or something that might get you more success. Right right that did thank you for validating that. We have heard that a few times we know that that survey 120 some questions I think that survey was. We knew it was going to be a large bite but we felt it was and that was actually trimmed down. Don did a lot of work with the 911 authority team. Don Jones from the OES team he's the project manager on this and he worked a lot to trim that survey down to what it ended up to be in the final product. So thank you Mark that is valuable. Okay next up we have funding so this is our current fund condition statement. You really can't see it on the slide. We as a result of the fee restructure a couple of years ago SETNA is in a good position. So we if the board members remember like five years ago there was a lot of concerns about how were we going to fund next gen how are we going to fund continued CPE support and maintenance and everything. All of that's been corrected and as we look at the performance of 2023 and we look at the calendar year 2024 we will continue to have our rate set at 30 cents. So here's the example of the calculations. We take what were authorized in budget what our carryover from last year's budget was with the total number of access lines and that will generate how much revenue is needed and then we use that formula to recommend what the surcharge is and then in September we send a letter to the California Department of Tax and Fee Administration making the recommendation of what that rate should be. They verify all of our calculations and then they move forward with that rate. So for calendar year 24 we will be at 30 cents again. It's Chief White, I had a question for you on the previous slide. Okay there you go. I believe it was at the last meeting they had discovered there was a carryover issue with some of the things. Can you highlight how that's addressed on here or did we get what it works out to now? So I looked yesterday chief on the Department of Finance website the fund condition statement has not been corrected for that carryover but yes you are you are accurate in the 23-24 top column up here. So actually I had another meeting Paul while you were out last week. Yeah. This fund condition statement is accurate. This is the fund. This is what's in the fund. All right. So we're good. We're good. Yep. So we went back and asked and we the good news is and and I think the board will remember back in like the 20 was a 2017 timeframe when we were actively working to redo our fee structure. It was successful. We have the funding we need and there was a lot of hard work from all of the associations that participate on the board to get the legislature to move us in this direction. So we're we're in a very very healthy spot which is good. Nice. Thank you for that. Yep. So that concludes my 911 branch update. If anybody has anybody from the board has any questions? Any questions for Paul on the branch updates? Right. Any questions from the public on the branch update part? Yes. One question from the public. Go ahead. My name's Candice Nguyen. I'm with NBC Bay Area News and this is about the financial and operational reviews. And I know that was an update given that during COVID they suspended the reviews but it sounds like they're being worked on again. On that slide that was shown Cali West said it reviews every 911 PSAP at least once every three to five years and the agency also tells the FCC it does these reviews every other year. You know we just saw that slide where the board says only did 22 reviews so far this year, two last year, zero the year before out of 450 PSAP. So my question is is the FCC aware that Cal OES is so behind on these reviews? Why are these reviews still so seriously behind and what exactly is being done about it? Yeah so these reviews are not tied to any FCC requirement and historically the branch has done them just as a way to ensure that the PSAPs are operating within what's required under the Warren Act in government code. Obviously during COVID when we were unable to visit the PSAPs because they couldn't take any visitors the dramatically impacted our ability to go complete these reviews. As soon as we were able to get back into the PSAPs our team of four went down to a team of one and that we didn't have the staff to complete them. So we are in the process of rectifying that. One thing we have done though is we continually monitor all of the statistics on call answer times answer rates transfer rates all of those statistics we continue to monitor. So we have that data we have a statewide statistics platform that that information is automatically gathered by us and we watch and track that information and then any PSAP that is requesting a review we can comply with. So once we get back up to staffing levels to actually do the work we'll continue the outreach as we showed on that slide. But there's no requirement for the FCC. This is simply an estate process. All right. Any further questions from the public on the branch updates? Yes. Go ahead. Have a mic. Yeah absolutely. Thanks everyone. Casey Link with Carbine. I just want to introduce myself and thank Paul, Budge and your team for the efforts that you've been putting in as we get through the lab. We look forward to working with you. But if there's anything you need from us, I'm the California representative for Carbine here in California. So I look forward to working with you guys. Yeah thanks. We're probably going to make you pretty busy here in the near future once you get through the lab. Let's get after it. All right. Thank you. Okay. Any other comments from the public on the branch updates? Another one online? Go ahead. Go ahead online. We're not hearing you. You want to come off mute and ask your question? Okay. There's a hand raised. So if you want to put your hand down. Budge, that's a thank you, Ramirez. I'm chiming in. Okay. Go ahead. Sorry. I'm having some technical difficulties on this end. I actually was trying to comment on the previous topic of this study that was brought up. I just couldn't get my technology working in time. I understand that I just wanted to make a comment as board member of the necessary timeframe or due diligence that we need to do with this study that I actually feel a little bit opposite about the amount of time that it's taking up of our dispatchers and our dispatch centers to complete the study. I think it's a mentality of we do need to slow down and we need to be really thorough about this study. That's precisely why we're trying to do it is to really gain an understanding of what the depth and the breadth of the problem is so that we can solve it. And our dispatch agencies have spread and spread so thin for so long and it's taking a toll on them and so changing that mindset perhaps and to be able to slow down and make the time to give this study it's due is what I would be more supportive of. Yeah, thank you, Chief Ramirez. And we've even said to those PSAPs that don't have time to do the entire survey, fill out what you can. If they want to reach out to us directly and we can help get the information from them, what's important to us is that we get an informed data set so that when we make a decision, it's just not the state running off in a direction that they think is best. We've all seen how poorly that can work out if the information is not accurate. So we agree and that's why we opted for the longer survey to really get the data we needed to make an informed decision. We understand the PSAPs are busy. Two to three hours is a huge commitment. We've got the data open and accessible through the end of December if I'm not mistaken. So any PSAPs that you're hearing of, please have them reach out to us. We will try and streamline this as much as we can but we do need the information. Thank you. Okay, any other comments? Any other hands online? Someone in the room? Go ahead. Yeah, you have to use a mic. Thank you. No problem. Thank you. With regard to that survey, I would agree that this information is incredibly important. It's the first step to making real change in California and potentially nationwide. If there's any opportunity to collect additional data from the dispatchers because it is very time-intensive for them as well, I would highly encourage us putting that back out on the street and the associations and anybody else who are active stakeholders can help reach out. If that does go back on the street to try and garner more data collection because I agree that this is mission critical for our survival. Yeah, and so I'll just go back and see how long we can possibly leave the survey open and still meet the milestones in the contract. So we'll take a close look at that. Absolutely. And we'll leave it open as long as possible. And then what we might do is even leave it open longer than what the contractor wanted. We'll develop the draft report with the data we have and if more data comes in, we might ask them to do a refresh on that because you're right, Melissa. We want to get as much information as possible. Yeah, thank you. Okay, so that's it on agenda item number seven. I think that was, I'm sorry, number five. Moving on to agenda item number six. This is a standing agenda item on alert morning. And so we've got the stats up on the slide and we're happy to see the usage of the system. As to date, we're not hearing any negative feedback. We're actually hearing the exact opposite of the success of the program, the use of the tool, those that are using this tool have been very supportive of the work that OES is doing and obviously the vendor partner that's to point it. So the stats are shown on the slide. I just want to see if anybody has any questions or comments from the board. I do have one update on alert morning. So the California early earthquake warning folks had reached out to me about a month and a half ago and in the NG911 alert warning functional requirements, we have a requirement for the NG911 alert warning to integrate with our earthquake early warning EEW system. So what they're asking is their EEW today can alert the community very effectively and efficiently. What they want to do is integrate to alert public safety. So any current NG911 alert warning user rave is the vendor providing this solution. We've engaged them. They're going to engage the EEW team. And the thought is if an EEW alert comes into network, it will go through rave and go to the PSAP. And anybody in the PSAP or that agency, whether it's your local emergency manager, alerting authority or PSAP team or law enforcement administrator, they'll get that alert just like the public would get that alert. And they're looking at this as another way to provide early alerting and then provide the location of a potential workway. So we're working that now and we're quite excited about the integration. But to budge's point, Michael, who is our project manager on this project, has worked very hard with rave. They've been out there. The campaign sent, we're up to almost 30 million campaigns sent in the total life of this system, which is huge for us. That's a lot of messaging. So we're very happy with the solution. We're very happy with the partners using this. So if anybody has any questions, Michael's contact is on here. And then the vendor contact, Earl, his information is there as well. All right. Any questions from the board on item number six? Any questions from the public? All right. Moving on to agenda item number seven. So there's been discussion recently about location accuracy in 901 and text to 901. So we wanted to take this opportunity to help educate the 901 advisory board members what OES has done to solve some of these location accuracy challenges. In legacy 901, the calls are routed in a wireless environment through a wireless tower using the cell sector. And the accuracy in legacy might not be as accurate as current technologies can map. So a couple of years ago, the 901 branch entered into contract with Rapid Deploy to provide supplemental location accuracy to all the PSAPs. And it was an optional service. We put it in all the PSAPs. And if the dispatchers wanted to use it, it was there. And what we found, I think Chief Gonzalez said it earlier, a lot of dispatchers don't like change. When we started to deploy this, a lot of dispatchers were like, I don't want this. A day after using it, they were like, I can't live without this. This gave us pinpoint accuracy of 901 calls coming in. And what we found is we deployed text to 901 through the next generation 901 network. We're using Rapid Deploy is that over the top third party platform when agencies do not use an integrated text to 901 solution. So in current environment, if your agency receives a text to 901, whether it's integrated or over the top, they get location. Location is as accurate as a voice call. If that location is available from the from the text or is coming through. And what we're finding is the supplemental application that we're using the tool using Rapid Deploy will be available on the NG901 network when we're fully deployed and we have cloud CPE fully deployed throughout the state. This is an over the top tool to assist the dispatchers in giving more data and more capability. So we wanted to take this opportunity to fully explain that if somebody in your community is texting your dispatcher should be getting that address. It's coming in. We validated it. And we know that location is as rich as it is for a voice call. So I'll take a quick pause if any of the board members have any questions. Any questions from the board on this agenda item agenda item number seven. Any questions from the public? Yeah, two quick questions. The over the top technology that helps that PSAP have accurate location when it comes to text 911. I think you mentioned this. This isn't not every PSAP uses or is required to use that Rapid Deploy or Rapid SOS that would help to make the accuracy as accurate as voice calls. Is that correct though? Every PSAP must accept text to 911 and they have the choice to integrate it into their call handling solution. There's about 130, 140 that have chosen to integrate it into their existing call handling. The remainder all must use this over the top solution. So they have a choice between the two, but they have to accept text. And regardless of whether it's integrated into their call handling or whether it's over the top, the accuracy of the text is as accurate as a 911 call. However, the over the top solution provides some additional functionality above and beyond what you get in an integrated solution. I know that was a long answer to your question, but that that's that's how it is. And just to be clear for the public and people in the deaf community, people who rely on texting, if they text 911 in California to a PSAP that takes then that them texting the location accuracy is as accurate as a voice call. Correct. Then why does California still well the issue was brought up by many in the deaf community when I was looking into this issue of the call if you can text if you can't campaign and thoughts that that campaign was out there because there was concern. Hey, we need you to say your location if just in case the in case the technology wasn't keeping up. So so is that not the case is there is there is there should be no location concern with text to 911. That's correct. The call if you can text if you can't is mainly related to the fact that SMS as a technology, which is what is used to send text is not a guaranteed delivery technology. All of us in this room have probably sent a text to someone and they never got it. And you're like, Hey, didn't you get my text? And you're like, I didn't get your text. And you pull up your phone and lo and behold, there's no text at all because SMS is not a guaranteed delivery. The 911 call is plus the delay in just the exchange of information between text and voice for the general public. It's generally much more efficient for both the 911 dispatcher and the person seeking help and 911 to call. And so it's mainly related to the workflow as to why that's there. But text if you can, I'm sorry, call if you can text if you can't. Well, from deaf or hard of hearing, I can't call. So of course I will text. Similarly, domestic violence situations, things like that would fall into that category of where I can't call. So they're form texting. And then probably one of the bigger use cases we see is with cellular technology, you can be in a place where you can't make a call, but you can make a text. And so in that case, the same, you know, public messaging applies. Call if you can and text if you can. And just last question for clarification. If there can be any explanation about some mixed messaging the public has gotten from the communications department about, yes, text 911 isn't as accurate with location, but we're working on it and sort of the messaging we're hearing today, maybe just some explanation around sort of the discrepancy or the differences in messaging we've been hearing the last handful of months. Yeah, that's one of the reasons why we have this on the agenda today because the board members reached out to us and said, we're hearing some missed messages. Can you please put this on the agenda so we can set the record straight? So I appreciate the feedback. Thank you. All right. Any other questions from the public on that? Yes, sir. Go ahead. Hi, it's Rob Bennett, technology consultant from WorkVantage. So as I understand it, Paul, the data you're getting from RapidDeploy is latitude, longitude, altitude, right? Before, in a path parallel to that of the data that's provided by the carriers. Yeah, go ahead. Technically not coming from the carrier. It's device based location that is sent from either Apple or Google from the handset and then sent through and displayed on the RapidDeploy platform. But yes, it is lat long and it's a pin drop and it updates automatically every two seconds during the first 30 seconds. And I think it's every what 15 seconds after that. Or anyway, there's like a constant update of the information. Yes, sir. So has there been any effort to compare the data that you're getting from RapidDeploy to that data that you're getting from the carriers, specifically the data that carriers use to actually route the text to 911 calls? Because for the record, you can't route a text to 911 call without location from the handset. So yes, we have done the comparison and now it's you'd be run into a timing issue of and it gets a little complicated because the texts are managed through a text control center and then that text is then routed through their routing mechanism to us. So the routing happens upstream to us. Obviously, whatever they give to us for location, that's what we route up. Whatever information is available at the time the text is received into the system, we route. So there could be obviously more granular, better location accuracy as that call proceeds. We will update it all the time, but we have done the comparison and it is, like we said, it's the same accuracy as the 911 call. Okay. So you're not seeing a huge discrepancy as there might have been in the past between the data you get from RapidDeploy and the data you get from a carrier. There is, it is much closer. Absolutely. Yeah. And it's a timing issue. Correct. So if you ask me when in the time flow, we would probably have a different discussion, but yes. Okay. Because three years ago, if you asked us that question, we would have given you a different answer. Absolutely. All right, budge. Thank you very much. Yep. Okay. We figured that would be an important discussion. So thank you, everybody, for the feedback there. Next up, we're going to move on to agenda item number eight. And for this one, I think we're going to have Don come up and give us an overview of our data sharing project. As he's making his way up here, this is an ongoing effort to do CAD to CAD and information sharing statewide. And it's been an ongoing project, so we're really excited about the progress that we've made. So, Don, I'll turn it over to you, sir. Good afternoon. Good afternoon. Don Jones, contract compliance manager. And actually, we have an update for the survey, the PSAP survey. We actually had a meeting during this meeting, which I wasn't able to attend, but luckily my partner in crime, part of the pun, Jeanette Dabrowski, was. And they are going to keep the dispatcher survey now open until December 3rd. It may or may not be open now, but it will be open. So for your dispatchers, you can send them that link and they'll be available till December 3rd. And now we have updated our 25 PSAPs up to 32. With the goal, as Paul mentioned, at least twice as many to make sure we get enough data there to collectively form and have an informed opinion. So December 3rd, for those of you who are looking for that information, and that's it on that. Any questions on the survey? Okay. So moving on to the data sharing project. So one of the things with the NG91 network is the ability to share calls across the state, which is a great thought. But when it comes to sharing telephone calls, having the ability to actually enter those calls for service in their agency is a problem. So that's how this data sharing project was born. We currently have three agencies that are in the early stages, Hawthorne PD, San Francisco DEM, and San Diego County Sheriff, all in different phases. San Diego County Sheriff is in the phase where they're taking the workbook from the vendor, which is RAVE, an association with Rapid DePoly, taking a workbook and entering in all their details from their CAD system so that they can share that on the platform. San Francisco DEM is ready. They're in a holding pattern. They're truly excited about this project, but they have a couple issues tied up with their legal department. Hawthorne PD was really early on in this process. They have the data early on up on to the RAVE platform, and we're getting more and more early adopters. We have a couple more that are kind of hiding in the wings there. So the goal really is within the Rapid Deploy platform, which most agencies have, is looking at other agencies' CAD data, even if they're on a different CAD system. And what we have for you is we have different stages, the ultimate stage being Stage 4, where I can enter in a call for service into my CAD and have it show up on your CAD, even if it's a different vendor. But what we have now so far is Stage 3, and I'll walk through the different ways that we display this in Rapid Deploy for your purview. We have a bunch of different test agencies on here. You're going to see Berkeley PD and other agencies listed. These are not early adopter agencies. We just picked these agencies because they were all close together. So in this event that you see on the screen there is Berkeley PD Fire and Law. So what this shows is that you can have this data displayed on the Rapid Deploy platform without sharing with anybody else. So if you don't want to share it, but you want to show it on your Rapid Deploy system for whatever reason, you could have that. And you can see those little icons there, those upside down triangles that show you what the events that you have going on within your jurisdiction. From there, this is really kind of hard to read, but I believe that probably says vicious animal on the bottom. I kind of thank you, Chief, for her enough away from the screen to have my cheaters on. That what you can do is you can click on that icon and you can see what the event is. You can see some information about it. You can see the address. You can see other things. And you can also see those little black icons and those are unit icons. So as your units are driving around through your city, you can see which units are there and who may or may not be available for your disposal. So this is turning off and on the icon. So here's an icon where you see, I believe it's Berkeley Police Department. Their icons are showing on the screen, but not the Berkeley Fire icons. A lot of times, depending on the dispatcher, you'd maybe want to turn fire off and on just due to the amount of apparatuses that they have parked throughout various parts of the city. It would fill up your map. You would be able to use it. So you have the ability to toggle that information on and off. And these are what those icons look like. Here's a legend. So depending on what the icon is, it says an EMS unit, a law unit, a fire unit, or other, you could have maybe probation units or what other units you're monitoring within your department. Here is an example of agency tours sharing multiple different agencies. So you can see there's a little legend on the side that you can toggle units on and off. But again, you can see what events they have and where their units are in relation to you and your city. Just more turning off and on, as you can see, as we add units or add departments, you can see more units pop up on your screen. It looks like we're clicking on a unit, seeing what the unit ID is, where they currently are located. What this doesn't prevent, though, is this truly is just for situational awareness. You do not have the ability of grabbing this unit for your agency. But if you wanted to, let's say, you needed a canine, and you could see if another agency has another canine on duty, you could easily see that through this platform. And then you could call them and say, hey, is your canine available? We need them for a search or whatnot, and you could have that ability to do that. Ultimately, on stage four, what we want to have the ability is to send a request to that agency, hey, can we borrow your canine? And that would all happen through this platform. You would still have to create your own call in your own CAD system, but that would be one way for the dispatchers to communicate back and forth. Because, as you know, dispatchers are really good at multitasking. Instead of picking up the phone, they could handle a CAD message very a lot quicker than they could with picking up the phone and going through that process. That is my email. My formal name is Donald, but please call me Don. There's my email and my phone number. If you have any questions or would like to reach out about this project, I'd be happy to answer that for you. A lot of agencies are really excited about this project. There's a lot of use cases for it. I would say even if you don't want to share with another agency, having this first situation awareness throughout other members of your city is very useful and very user-friendly for those personnel. Any questions from the board? This is probably the first view the board's had of the situational awareness, mutual aid overview of this data sharing project. Obviously, like we said, the next step, actually being able to assign units one to another and facilitate the communication. We wanted to give you an overview of where the project is now. I want to see if there's any questions from the board on this. Go ahead, Chief. If I can just add to my new education. You're saying this is if they're logged in, right? Hypothetically, I'm up at Napa, but I'm down in one of these agencies just for the map purposes Hayward. I'm in training, but I pop on just to see what's going on in my own community. Log into my computer. That would activate it, but I might not be ready to be deployed in that region. If I'm at a training facility, I don't have all the same gear that I would normally have. Yes. At the risk. Let's just say you are down in Hayward. Your agency would have to already have an agreement with them that you're best share. If you're down in LA, let's say for example, you don't have an agreement with them, you're not going to show up on their screen. It's only with the agencies that you're actively sharing with that you're going to have that agreement. Great question. Well, thank you. One thing we are seeing with this obviously with our law enforcement mutual aid has increased dramatically with wildfires and some of the large scale events. Right now there's really no good way for a law enforcement mutual aid to communicate with one another track resources. If you get a mutual aid, a law enforcement mutual aid team that comes and say support of a variety or a plan to ban or evacuation, this tool could do that because you could temporarily assign two or three officers from your unit to this other agency that's coordinating mutual aid response and they would see that information. So that's kind of the vision of it, but we were very careful to build into it that you as the owning agency are the only one that can give up authority to who sees your data and who modifies your units. And we thought that was a really critical part of it. So yes, to Don's point, the capability is there, but you as the owning agency would have to share that with them. Okay. And is there any future plan of color coding it for, you know, typical red fire, blue law enforcement, that type of thing, because those images are really tiny. Oh, yeah. Yeah. Thanks. I mean, I'm not trying to make it look like CAD, but trying to have a big Cadlight in a sense where it needs to be what the users are used to using. And there is kind of a standard, I agree, blue for a law, red for fire, that kind of thing. So absolutely. So what do we do with the yellow fire truck? Do we want to get into that today? Is this a dad joke? I don't know. Well, there's or are they green or Oh, you mean the Calloway? Yes. We probably want to talk about that. All right. Okay. Any other questions from the public on this? Yeah, there's one online. Go ahead online with your question. Yeah, this cheap fight. I had a couple of questions. One is, is there any work going on with CAD vendors right now with respect to integrating this? Because obviously I've worked at two agencies that have had CAD to CAD interfaces, and they can work really well. But being sort of a standalone, you know, that's I see it's showing it all on a map, but the true value would be is actually having CAD to CAD. Are you working with any vendors currently? Yes, absolutely chief. We're working very, we need their help as well in getting this system doing the CAD, the true CAD to CAD connection, but even taking their data from their current platform and just showing it up on the screen, we need the vendors help. So for example, down in San Diego, we're working with that vendor. They do X and Y and their CAD a little bit different, which seems kind of simple. It's a Latin long, but we're having to work with that vendor to kind of see how they process Latin long too, so that we can properly implement it into the system. I will say that what we have seen is, if an agency is already using an API connection to throw up their CAD events up into a public platform, that we can usually use that data from an API initially into throwing information up onto your rapid deploy. But for the full integration, we need this workbook. It's a pretty thick workbook completed by the agency with the help of their CAD vendor to really do a complete connection. Okay, the second question is the test agencies seem like they're not agencies that would actually talk to each other. So like when you say, for example, San Diego Sheriff, are there other actual local agencies as part of that testbed? In other words, I think from a testing perspective, you'd want to get several agencies within a geographic area who naturally would be exchanging data and then try to validate if this works or what needs to be done to enhance it. Can you talk to that? I agree, Chief. And we do have in the wings is alcohol, which they're working closely with San Diego. But yeah, the ultimate goal will be to have agencies who truly do use this kind of technology today and have them be the test platform. Okay. And then my last question, I think might be for Budge. And that is, obviously, I think our number one priority needs to be getting the NG core system up and running, getting agencies connecting, getting all the dispatchers transformed over. This, as I understand, would be like the, if it's all built out, would potentially be like the largest data sharing project in the world. I think that's what the first press release said. Is this taking away resources from those other projects, especially hearing that like, you know, there's one person that's filling a role in a team. Can you talk to that? Yeah. So if you've probably noticed the progress on the data sharing project has been rather slow. And the reason why is because we've asked Don to do a whole bunch of other things and not this. And that has slowed this project down. So we absolutely are not moving as fast on this project as we originally intended because of the other work that we're prioritizing. Yeah. So if it seems like we're going slow, we are. We agree. Because Don is only able to do one thing at a time, unfortunately. Understood. And I would just say from being one member of the board that I fully support that, I think we have to prioritize the other projects. And so I understand that it's being delayed or, you know, it's not moving quite as quickly. So thank you. Yeah. Absolutely, Chief. And right now, as Paul briefed out in the branch report, our top priority as a branch is the cloud CPE deployment. And that's really because of the age of that equipment that's out there. Our second priority is next and I'm a one deployment. And then, you know, the third are these other data sources that we have going on like this data sharing piece. And that's always been sort of the focus of the branch. So absolutely. Unless the board has any comments, that's our priority. So if you think we should adjust, let us know. We will. Okay. Thank you, Don. We appreciate it. All right. Moving on to, if you want to bring me that clicker, Don, that'd be great. Moving on to item number nine, we just think we just had our 98 advisory board meeting this morning. This one slide is attempting to summarize three hours of data. So it's probably doing rather poorly at that. I really would encourage you, if you want additional information on the 98 work that we're doing in that effort, we will post the slides this week. And we will get the YouTube video up on the on the board that has the full meeting, certainly within the next couple of weeks with Thanksgiving might be a little delayed. Needless to say, the technology for 98 to deploy the call handling solution and the customer relationship management software, we've tested initially in the lab and Kurt Galat, who's our project manager there is going 98 centered and 98 center there are 12 of them to validate that what we wrote in the technical requirements actually meets their needs as an agency. And so we he is doing that work to make sure that that minimally viable product is there. This is a new system. We are unaware of anybody else that's building anything out like this. So we're kind of paving the way and it will solve some of the interoperability problems between 91 and 98. We were on track to meet the dates that you see in the bottom of this slide, but we're on a hold right now waiting for an MOU to be signed between us and vibrant. Vibrant is a vendor that SAMHSA the national the agency at the federal level responsible for this has selected to administer the program. And so we're in this transitional state of them managing individual centers in the state versus dealing with a state entity. And as you can imagine, there's there's a learning curve there. Once we get that MOU in place, roll this technology out. We're optimistic that we can still meet our July 2024 deadline for rolling out this technology, but all that hinges on that MOU. So lots of interaction between 91 98 we have boards going on and conversations. And I think if you're really tracking this initiative, you'll want to listen in to the February 98 advisory board because we'll have our initial kind of straw man of of how the transfers would move from 98 to 91 to 98. We're started to engage in earnest in those conversations. So that'll be in February with probably some kind of guidelines put out by May so that just so you're tracking and we do have 91 representation on that board as well as 98. So that's kind of a quick update of where we are with 98. Happy to answer any specific questions or concerns from the board. Any questions from the public? Okay. Long range planning committee. So we oh yes, we're fully owned that we were not able to get our public agenda posted 10 days prior to the meeting. And we had to cancel the meeting. So we will certainly schedule this again. So long range planning committee has not met since the last time this board met. However, we're more than happy to entertain any work that the advisory board might have for that committee and also on the next agenda item, we'll get to any appointees to that board. So any board members have any discussion for topics for the LRPC? This is a group that's looking strategically at kind of what's next. Any questions from the public on that? I see Alicia stepped out. She's our chair. So she won't have any comments because she's not in the room, but that's fine. All right. And then this slide agenda item number 11. We really want to talk about appointees to the LRPC or recommended future assignments and tasks. So is there anything you're hearing that you already see what work on as a branch that we aren't thinking about that you'd like us to start engaging on? This is pretty much the first step to do that. I would just say I think some of the information just presented about the data sharing project. I think that that's right for having the LRPC take a look at that, see how agencies envision cooperating together regionally. Moving forward in the next couple of years and getting buy-in from the agencies, getting test agencies, I would say that that's one project that they could start taking a look at. Okay. And that fits in nicely, Mark, with the alternate answer policy store conversation that we will bring that functionality as part of Next Gen 901. So to Don's point, we can move the call there with Next Gen 901, but once you move the call there, okay, now you got to be able to actually provide the help to that person at that neighboring PSAP. And so I think you're right. These two things go hand in hand. Absolutely. All right. Any other items you'd like to the LRPC to take a look at? Any questions or comments from the public on agenda item number 11? Yes, sir. Go ahead. Right. In other states and during COVID, we saw some agencies that deployed call takers at home. And I know that there's a lot of talk, at least in staffing and things like that. So I wonder if they might consider an examination or a discussion of what that looks like in California as we deploy Next Gen CPE and what that would look like if we had to deploy call takers at home. I know in Europe, there's a lot of talk, at least for medical call takers. I think it's in Austria, but they're allowed to work from home as a call taker. And that's predicated upon their EMD performance remaining highly compliant. So just maybe talk about that, about what that looks like and in what capacity that might be deployed for during future crises in California. Okay. All right, Mark, you got another good idea for us. You're on a roll. That's all for now. Okay. All right. Any other items? Okay. All right. Item, agenda item number, I think we're on 12. So this is items for future meetings. So we have the standing agenda that you saw today. And we really try and do as we try and put a lot of thought into everything we're hearing from the entire PSAP community, all of the chiefs, the sheriffs, the fire chiefs, the EMS community that we're hearing from to kind of build these agendas. But if there's something we're missing, we certainly want to get it on an agenda. We'll tell you that it takes us about 30 days to get an agenda through our approval process. So if you wanted something in the February meeting, you'd need to tell us, the board members would need to tell us by certain middle of January. But today is obviously way far enough in advance. If you wanted us to add something to agenda, we can certainly do that. So any agenda items from the board for future meetings. All right. So the good idea for that expires mid-January. Just remember. So if you give me an idea in early February, it'll be on May's agenda. It's just the way it is. These dates are set. And unless, like we did this time, we miss an approval process, they're set. We'll try and keep them in stone. And so we look forward to everybody. One other thing we will mention, I've mentioned this before. We don't always have to have these meetings in Sacramento. Given a lot of advance notice, we can certainly do this somewhere else. We've done it in the past. We haven't done it anywhere else but here in probably four years. But just keep that in mind. If you'd like to see that, our staff would love the challenge of putting this on in another part of the state. So keep that in mind. All right. Any comments from the public on agenda? I know number 12, I think this is. All right. Next one. Public comment. So this is anything from the board that we didn't cover already that you want to talk about? Now's the time for board members. Anything we didn't, that we didn't address on the agenda? But anybody? Board members online? Yeah, it's Mark again. Surprise. Hey, Mark. Long time. You haven't heard from me in a while. I just wanted to circle back to Wallamy. We talked to the last board meeting and I should have brought it up earlier. I apologize about the final cut right of the first landline and have a PSAP completely on next gen. Is there any update on Tuolumne or other centers that might be close to completely cutting to next gen? So I think probably Imperial is farther ahead than Tuolumne right now. We have in Tuolumne County, we have Verizon Wireless has cut I-3 connectivity, which is pretty exciting. T-Mobile is cut over, AT&T Mobility is cut over, Frontier Wireline is cut over, and I believe the remaining one is a small LEC that's not cut in Tuolumne. Is that correct? And so there's one small local exchange carrier in Tuolumne that needs to be cut. In Imperial County, we've got Verizon Wireless, T-Mobile, AT&T Mobility, and I think they were going to cut AT&T Wireline in the next two weeks. And then they have a small LEC down there, Winter Haven, Telco that they would have to cut. So we're pretty close in a couple of areas, Mark. No PSAP yet is 100% cut over to next gen. My guess would be the Imperial County area would be the farthest along, because not only have they cut over the Imperial County Sheriff, but they're on a host remote system, so Brawley, PD, Kalexico, and the CHP and Elst Central are cut over there. So that's probably where you're going to see our first complete selective router. Everything cut over 100%. That would be my prediction in the state and we're hoping that happens early 2024. Okay, so your anticipation is by June of next year, either Tuolumne or Imperial, will be completely cut? Oh, that'd be way before that, or there's going to be some problems. Okay, thank you. Yes, that would be my anticipation, is the proper way to answer that question. Sounds great. Thanks, Mark. All right, any other comment? Any public comment for items not on the agenda or anything on the agenda? Any public comment? Seeing anything online? Okay, here's everyone's favorite agenda item, adjourned. Any of the board members have a motion to adjourn? All right, thank you, Chief. All right, do we have a second? Sheriff Brown. All right, thank you, Sheriff. Okay, we are adjourned. My time is 245. Thank you, everybody, for your attendance. We look forward to talking to you all in February. Thank you. Thank you.