 All right, well, it looks like the number of participants is stabilized at 46. So I'm going to call the meeting of the 911 advisory board into session. And the first item on the agenda is a roll call. So CHP Chief Chris Childs. Present. Good morning, sir. Brenda Brunner. Present. Good morning. Leanne Mugoski. Present. Arosa Ramos. Present. Sheriff Ingrid Braun. Sheriff Bill Ayub. Here. Good morning, sir. Juan Carlos Castillo. Present. Good morning, sir. Chief Rebecca Ramirez. Present. Chief Elise Warren. Here. Good morning. And Chief Andrew White. Present. Good morning. Good morning all. Well, welcome to the to the August 911 advisory board meeting. We do have a quorum. The next and Paul or somebody, can you bring up the slide presentation so we can go through the agenda? Well, we'll bring that up in just a second, Pat, because I've got it set up for a closed session right now. OK. Well, we do the first item, item number two on the agenda is approval of the previous minutes for May of 2021. Are there any corrections? Hearing no corrections, will entertain a motion to approve? Motion to approve. I'm sorry. Who was that? My brother, Bruce. And a second. We am a second. Thank you. Second by Leanne. OK, a roll call vote. Chief Childs. Chief Childs, there's always a mute button. Sorry, everybody, I'm here. I'm voting on approval of the minutes from for me. I vote move to approve. OK, approve. Brenda Brunner. Aye. Leanne Magoski. Aye. Rosa Ramos. Aye. Sheriff Inger Braun, have you joined us? No, Sheriff. Sheriff Ayub. Ayub. Aye. Juan Carlos Castillo, you cannot do it. Chief Elise Warren. Aye. And Chief Andrew White. Aye. OK, and before we move on, the I would like to welcome our new board members in Juan Carlos Castillo and Chief Rebecca Ramirez. I also believe Chief Andrew White was formally appointed by the governor's office and what was that? I'm sorry. Is that Chief Warren or Chief White? White, that's correct. OK, and then Sheriff Inger Braun is was approved also for a second term. So welcome to all of those. You know, I would like to to recognize Chris Herron for all of his his hard work, you know, on the on the advisory board, as well as, you know, in the the Long Range Planning Committee and also to our former chief. Like this lost his name from San Diego area, you know, who was represented from from the fire. Chief Hatfield, so Hatfield. Yeah, so thank you to both the both Chief Hatfield and to into Chris Herron. We really do appreciate the. Your effort, the next item on the agenda is a closed session. So for those board members, you've been sent a separate invitation and we will be stepping away from this meeting and rejoining is the end of the closed session for any nine moment advisory board member sent the Microsoft Teams link. Please log out of the Zoom meeting for the closed session and then log into the Teams link. Thank you. We'll give the board members another moment to to come back and then we will have to call roll again one more time. OK, I'm going to call roll one more time to to confirm that we do have a quorum chief Chris Childs. Present. Brenda Brunner. Present. Lea Mugoski. Present. Rosa Ramos. Present. Sheriff Brown is on vacation. Sheriff Bill Ayub. Present. Juan Carlos Castillo. Present. Chief Rebecca Ramirez. Present. Chief Elise Warren. Present. And Chief Andrew White. Present. OK, we have a quorum again, budge. As far as the the closed session, it was held pursuant to government code section one one one two six E and we have nothing to report out. OK, on to the legislative update. Unfortunately, Mr. Salvador is is busy fighting fires. So we're going to have Chris Hacker from his office. I'll provide the update. Chris, are you with us? I am here. Unfortunately, yeah, you guys get me. But here I am happy to be here. Thank you, Chris Hacker from the Cal OES Office of Legislative and External Affairs. We are tracking a number of pieces of legislation that relate to the 911 system getting to the end of session. So we expect things to get nutty here pretty soon. But here's where we're at. So AB 988 is in the Senate. It was referred to a couple of policy committees, Senate G.O. and Senate Health. And we're waiting a hearing day potentially. There isn't one second on that one. AB 1100 is in the Senate in appropriations on the suspense file currently. Chris, what is that piece of legislation regarding? OK, so AB 988 Mental Health. This is the crisis mobile support teams and the 988 crisis hotline. AB 1100 is related to infrastructure that's destroyed during disasters and telling the communications providers reporting information on rebuilding that infrastructure. AB 1403, that's the bill that would include a de-energized de-energization event as constituting a state of emergency. And that bill is in back in the Senate and it's ordered to its second reading. AB 1565 would authorize Cal OES to investigate the feasibility of establishing more than one toll free 800 hotline. That is in the Senate governmental organization and appropriations. SB 52, which would also include de-energization events as a constituting an emergency and would also define de-energization events. SB 341 would make requirements of telecommunication service providers to maintain information on its website of outage maps and would also require PUC and Cal OES to create rules and regulations regarding those maps. And that bill is in the Committee on Appropriations in the Assembly. On the federal side of things, we're monitoring HR 1250 Emergency Reporting Act. That is in the Senate and it's currently in the Committee on Commerce, Science and Transportation. HR 1848 would would make a number of investments in infrastructure, including next gen 9-1-1, and that is still in the House. HR 1859, which would work with some programs on response programs, that is in the House as well. Senate Bill 466 is currently in the House. It's in the other chamber and that has to do with mobile or internet voice service providers, disclosing location information pursuant to certain requests. Senate Bill 1175 categorized public safety telecommunicators as a protective service occupation that is in the Senate and it is still in Committee on Homeland Security and Governmental Affairs. That concludes my briefing and I'm available for any questions. Thank you, Chris. Board members have any questions of Mr. Hacker, hearing none, we'll move on to item number five, which is the Cal OES 9-1-1 branch update budge, Flora Sherks. All right, thank you. As you see, there's six standing items that we typically brief out on. And if you have any questions as I'm moving through these items, please feel free to just interrupt me and I'll answer the question right then. It'll probably be a lot easier because we'll we'll put it in context that way. So the first slide we talk about is our call stats. And this is a summary of 2020. We will, again, obviously at the end of this year, produce the stats. What we're seeing is an upward trend here. Each year, wireless is growing one or two percentage points over the rest. And usually we see a decline in wireline. That's been the general trend. And then the other interesting metric is the text to 9-1-1 last year. We had a little over 50 percent of our PSAPs were active. Now we have 100 percent minus one one PSAP taken text 9-1. So it'll be interesting to see what happens to those statistics in 2021. Our call processing equipment, CPE, this is the status of our installation. You see, we historically do about 60 systems a year. And you're probably wondering, OK, doing quick math. It's August. We should be way over 11. Why are we at 11? And the challenge we're having now is that the call processing equipment was required to be Nina I3 compliant. It's a standard on how they have to deliver calls in the next gen 9-1 network. And the call processing equipment vendors are having some challenges there that I'm going to talk about on the next slide. So what we're doing is if you have, as a PSAP, older CPE, reach out to your PSAP advisor. Every PSAP has a dedicated advisor. If you're not sure who that advisor is, then please reach out to us at Cal OES and we'll let you know who that person is. And we could talk to you about maintenance. And if you're in a condition now where your CPE is not performing or you're concerned that it's going to fail or have a catastrophic out is let us know. We do have the ability to, you know, on a case by case basis, see what we can do to shore that up. But in general, the problem has been that the call processing equipment is not compliant with the contract. So based on state procurement rules, we can't buy something that we know is out of compliance. It's a different story for everything that's already installed. So these bullets on this slide are kind of high level of where the problems are. Our entire network is IP version six. Most of the all of the CPE as it's installed today is IP version four and typically does not have a unique IP address. They use private addressing space, which means that you can't use it in a larger network. You need a public IP address for that. And then the transport layer security information that's needed to be exchanged across the network is not supported. So the unique IP address that I mentioned there, that ends up being very critical in the need I three call flow because you can't answer back to a specific location because it's not uniquely identified. The next bullet there, element state, Q state has to do with whether a dispatcher is or a call taker is on the phone, whether they are the phone is ringing and not being answered or whether it's busy or it returns all those values. And there's a certain way that you're supposed to do that in the I three standard and the call processing equipment can't do that. So it returns error codes and we know how to interpret those error codes, but it really should be communicating back using I three messaging it and it's not real time text. We've probably all heard of that buzzword. That's the ability to support rather than just standard SMS texting like you do today, but it can support photos and videos and other capabilities. The CPE does not do that. And there's this how you transfer a call using conferencing versus the method called refer refers the way it really should be done in the standard. So there's that gap. So what we've done and we've talked about this in this advisory board many times is we've asked our next gen 901 vendors to put as many workarounds as they can in place to shore up these gaps. And that's what we've been doing. We also are now to the point where we can actually test not only in our lab, which we've been doing the extensive testing our lab, but actually at the PSAP, the ability to answer a 911 call and have the location information display properly for the telecommunicator. And also then push downstream into computer aided dispatch and other downstream products that you're using to make sure that it follows the same format as today. And we're finding some gaps there. So until we get our CPE to the point that it can address all of this, we can't buy new CPE unless there's some dire circumstance that we're trying to accommodate. And that's where you'd reach out to us and we can work with you. So I want to pause there for a minute to see if there's any questions, because this is a pretty, a pretty important point. I want to make sure everybody understands what's going on. So any questions from the board members? Brenda Brunner, I have a question about the inability to support the real time text. There's an understanding there was a timeline that PSAPs were supposed to be able to support real time text. Is that something that's also being taken in consideration with the build out of being able to present those calls to the PSAP in meeting the timeline? Yeah, thanks for the question, Brenda. So it's really there's there's three parts of the system you have to think about for real time text versus the carrier has to be able to send you real time text messages, which means they have to connect to you. IP. It has to be an IP connection. It cannot be an analog or a camera or S of seven or one of the older technologies. Right now in the legacy nine one one system, there is no ability to ingress IP calls. So you absolutely have to have next gen nine one one. We're solving that with the build out of next gen nine one. We can receive real time text in next gen nine one route real time text and deliver real time text to the PSAP. So the middle piece will be addressed by next gen nine one and the carrier's ability to deliver IP. Most of them have told us they're ready, but until we can receive it, there's no sense in sending it. And the next the final step is once I have it in next gen nine one or the system has the next gen nine one, we've got to be able to display it once it gets to the PSAP. And without upgrading the call processing equipment, we can't display it. So it's all three of those things have to be in place in order to do this. And until we get next gen deployed, we can't support it. And then we'll start working with the carriers. But we still have the gap of the call processing equipment. So that's where we are in the interim to meet this requirement. The carriers are converting it over to TTY, which is another protocol that's analog based and then we push TTY through the network and deliver it to the PSAP and the PSAP can display the TTY message. So we're able to meet the requirement using TTY, even though we all know it's not the preferred method and not what we ultimately want to do. Yes. Thank you. OK. All right. So how do we Yeah, sorry. Go ahead. But sorry, I don't know if you can hear me. I have a question on that back on that other slide. So I completely respect and understand what we need to do. And yes, that all of that, especially the real time text and the unique IP address is absolutely important. But with those agencies that are in that pickle of on the case by case basis that are waiting, if we don't have systems at work, what is the case by case? That that you're suggesting that they do to keep their legacy equipment running since in some cases they've been waiting for so long, it's it's getting quite elderly. Yeah, no, no offense to anything elderly. But yes, we realize that that is a that is a problem. We have yet to have a PSAP talk to us that's in such dire condition that we need to approve the sale of more legacy equipment. But that's what we would have to do. We would just have to say, OK, you're not getting I3 compliant equipment. We realize that put the vendor on notice that they've got to get it up to that level once their solution is able. And then we would move forward from there. We have not had to do that. But until we get the cloud CPE approved through the lab and next to the 901 install, we really don't have another option. OK, I mean, we're not there anywhere right now. I want to make that clear. No one has contacted us saying they're at that place. And I don't know if this is farther along in your presentation, but I think my concern in representing the PSAPs is that they keep waiting. And I am concerned that eventually one of those systems is going to fail. Or by the time we get next generation, I'm a one rolled out. There's so many people waiting, they're going to have to stay on their legacy systems for longer because you just can't implement that many systems in a short period of time. Yeah, and and we had a meeting with the team this morning. I'll go back a couple slides. So you see the record here is the 92 systems in one year. So we just brought on a new supervisor to backfill Andrew's old position in the PSAP advisory unit. Our name is Janae and we told her, hey, guess what? You got to beat 92, so you're going to have to roll out about 120 in your first year. No pressure, welcome aboard. And that's literally what we know we're going to have to do to make up the backlog. And it is a heavy lift and we realize that that's coming. So, yes, good point in the end, we completely agree with you. And I really want to make it clear. This is not what we planned. We planned buying equipment from CP vendors who were compliant with the contract. So we just want to make sure that everybody realizes we is not what we wanted to do. So how do we get there with that 120 new systems in one year? Really, this new cloud based contract that was signed a year ago, believe it or not. And we're already in the process of testing or defining the test requirements and putting the circuits in place to test the systems that are shown in yellow on this screen. So Autos has a product called Gemma. It's a cloud based CPE. Carbine is a cloud based CPE product. Lumen resells a product called Omni 911. It's cloud based and NGA is a cloud based solution called A-C-E-C-H-S, which I can't remember the acronym. I think it's automated computing, equipment, call handling system or something like that. It's an acronym. And so those are the ones that we're starting with first. And we're making it very clear that we want to test with everybody that's on this list. And our goal is to get through the testing process for all of those that are shown in yellow at a minimum by the end of the year so we can start to roll those systems out as we roll out next to a 911 throughout the state. We've got a lab here when these systems are up and running. And if you want to see a demo, we can do that. I would anticipate the first of these will probably get through testing by the end of September if things go fast, but it could go into October before we get the first systems tested through the lab. So any questions on that? Yeah, I had a question. As far as the timeline on the previous slide, have they given an estimate on how long to remediate those issues, particularly the ones like the IP addressing issue, some of the things that seem like their barriers to even get moving? Yeah, so Chief White, the short answer is no, they have not given us a definitive timeline, and I want to be clear this little part of the definition with equipment installed at the PSAP today is very important, because when you reach out to your call processing equipment vendor, they may say, hey, we can do that. Then the very next question should be, can you do that with the equipment? I have installed in my background today and they're probably going to say no because they need a couple of pieces of equipment, a session border controller and a software upgrade and some other things. And so and some of them can't even do it then. So that's the challenge we have. They don't even have a timeline for this, which is why we suspended sales, because if they had a definitive timeline and we could test and validate in our lab, then we would just sell all we want is I3 compliant equipment. We just want to meet the needs of the PSAP and we're just not there. So moving forward, though, on the next slide, then the cloud based CPEs, I assume those theoretically meet, address those issues. Yes, all of these will address those issues. Exactly. There is a path in moving forward to keep us on track. Just delete of it. Thank you. Yeah, exactly. OK, so I figured that conversation would take a while. It's very important. We're obviously we were spending a lot of time dedicating resources to this and working with these various vendors. You see the number of the list of companies up there and you can imagine how complex it is to coordinate all this. And that's what we've really been focusing on. Text 9-1-1, I really want to give credit to Cherise Bartlett for her hard work on this effort. Just absolutely amazing, the work that she's done and really Cindy and Ella and and and Gail and others have been instrumental in this process. And then every single PSAP and your willingness to meet the state's timelines and work with us to deploy this solution. It's just, you know, really appreciate the support and and congratulations to Cherise on a job well done. This is a tremendous, tremendous effort that she undertook and completed. So we're compliant now minus one PSAP. And the reason why the one is not there, their internet connection is not stable enough to support the the text delivery. And so we're just going to integrate it when we go next gen 9-1-1. That way we'll solve it through that. And it's if you're wondering, it's Sonora PD. So, you know, their call volume is not substantial and they work really closely with Swallamy County Sheriff. So that the folks that live in Sonora PD are taking care of. There's no there's no gaps there. And we just want to let you know that's the one. So any any questions on text? OK, so I'll cover more on text 9-1-1 as we transition in a minute. These next couple of slides I've been using this graphic to kind of talk about how we've got to install equipment in all the PSAPs. We have to integrate the originating service providers or the carriers. We've got to do testing and integration where we got to do we got to do the transition so that these are all steps that are ongoing as we put this next gen 9-1-1 puzzle together. And one thing you'll notice, we've we've updated these dates. It seems like every time we have a meeting, we have to update the dates. And I'm going to talk about why and what our challenges are. But realistically, you know, it'll be December of 2022 before we're completed just because we know it's going to take over a year to complete the transition once we start and what's causing the delays? Well, the challenges of working with CPE and I'll talk about that in a minute. Obviously, COVID and just us learning how to improve the project, the process. You know, we've we've been learning a lot as well. It turned out that this is a rather large project. We're pretty sure this is the largest 9-1-1 system in the US and might be the largest 9-1-1 system in the world. And it's it's actually quite complicated. So anyway, no excuses, but the dates are changing. So we've used this graphic a lot and it still holds true. There's three lanes that we're coordinating. The first lane is what are the minimum updates that they call processing equipment vendor needs to do to support next-gen 9-1-1? And this is not we know the gaps. This is what do we need to do even with those gaps addressed by the next-gen 9-1-1 vendor? They have to install a firewall and program it. There's network connections that need to be made. They've got to do line appearances and program them for those for your 9-1-1 first responders, and then they've got to train and test those. We have to install all the equipment. That's the middle portion of this graphic for both Autos, which is our statewide vendor and the region provider. There's circuits, there's equipment, there's connections. And then we've got to make sure that all that works and can land calls with those line appearances that were programmed by the CP vendors. We call that DMARC testing to make sure that the connection between the two is there. And then along the bottom, we start working with carriers to land calls. I'm going to talk about some of the successes we've had. But once all that's in place, we did go live testing. The PSAP training is ready. The Network Operations Center piece is in place. And we can start going through the cutover process. So we have implemented up. So somebody has a question to go back one slide. So I don't know how that message came up. I thought we blocked chat, but all right. So, yeah, the end dates is December 2022. I saw that message flash. All right. So the validation that we're doing, what we want to do is make sure that for a period of two weeks, we can land calls on those newly programmed line appearances, transfer them. Annie Alley is working. Location can pass through the system, can integrate with CAD, validate alternate routes, processes, all your trainings completed. Trouble tickets can be entered if needed. You've got an interface with the Network Operations Center. And we know we can bring in calls from the carriers. So all this is what we want to do and what we've tried to do a number of times, and this is where we started to discover some problems. And I'll talk about those for a second. So everything up till now is process related. I want to pause here to see if there's any process related questions. So what have we done? So all the PSAP boundaries are in, which is a huge milestone because the way we're going to route calls is we'll look at the lat long or the civic address of the caller, we look at the PSAP boundary. And if you fall in that boundary, we route the call. So these boundaries are critical. Those are done, vetted, validated. We we've built four or five different next gen nine one Nina I3 compliant NG nine one core systems and they all work one to another. Autos, NGA, Lumen, Synergy. We've tested failover, we've tested circuits. You can literally go in the back room and unplug stuff mid call. And the call still goes through. So huge, huge milestones there that we vetted and validated. We've done carrier testing with T-Mobile and Verizon wireless all the way into a PSAP, all the way into the lab here at Cal OES. And we've successfully delivered handsets from a handset out in the field using geospatial routing with a completely Nina I3 compliant architecture all the way into the PSAP. We've done all that. And we've deployed equipment at over 80 percent of the PSAPs in California. So, you know, you're talking, I don't know, whatever 80 percent of 450 is. That's a big number. And then we've got system monitoring and trouble ticketing that we've got testing. We think we have a couple more tweaks to do to that. But but all of this is working today. So huge, huge progress. And we knew that it would take about 24 months to get this done. Guess what? I think tomorrow is the anniversary of when we signed the contracts. August 19th, Friday, August 20th. So August 20th will be the two year mark of when we signed contracts. You know, and once you sign contracts, there's always a lag to when you really start work and we've really only been actively working on this for a little over 18 months. So we're we're feeling pretty good about where we are. But we, we, you know, we do still have some challenges. There's some barriers. One of the main things we're running into is the the CPE and just the I3 functions. And I'll tell you what this looks like. We do testing. We discover a problem and we take two to three to four weeks to fix the problem. And that problem is masking the problem that exists after that step in the process. So it's not like you test and you see all the way down through the landscape and say, oh, here's the 10 problems we have to fix. Let's start addressing it at the current challenge you're seeing blocks your view of everything else that's not working. And so we've been working our way through taking down these barriers and trying to overcome this. And you can imagine when we run into feedback of, hey, we need to upgrade the software and the CPE. Well, that's 450 software upgrades that we have to go through. So I mean, it's just it's not possible to turn on a dime with that kind of schedule. So now we're working with the next gen one providers to develop new code and code changes and testing and and all of that. That's really what has been causing a lot of delay is that complication. And then this day to support, which is, you know, the ability to call the Network Operations Center and enter a trouble ticket and get a status and all that. We've been working on that. We certainly have been impacted in the supply chain and with resources due to covid. You know, what typically would be a three to four week turnaround on parts turned into three to four months turnaround. So that that's certainly had an impact. And this is the one that's that's really causing us the most delay right now. Delivery of location information. And we even had to go back to the Nina I3 working group that wrote the standard to make sure we're doing it the right way and to make sure that every next gen one service providers doing it the right way and that according to the standard and that the CP vendors are doing it the correct way. And once that information comes into the system, it has to flow to all your downstream systems that you already have at your PSAP without impacting them. And so that's the spill to CAD pushing the location information over to CAD. And that's the barrier we're trying to solve right now. Some of the CP out there can do it better than others, but there's gaps that exist everywhere. So that's what we're working on now. We obviously don't want to deploy next gen nine one and not be able to give you location information or you have location information over in your on your call processing screen screen, but not on your CAD screen. And then this other one, you know, this is a big project. It's massive, so it's never been attempted before. And it turns out that we're doing a lot of pioneering work in the space. So it's it's it's been an interesting process. So I want to see if there's any questions about these barriers and what these delays are budgets a lot to take in. So I wish we had we had a little more time than on this. But so is it it's a when when do we think with with all of this moving forward that that there's you're just going to keep us updated, basically, right, on these things? Yeah, I think it's the next slide. OK, I just I'm ahead of the slide on when it's about four slides down. OK, I'll keep quiet. So I think maybe your question to Leanne is how do we overcome these? That's what this slide is. So we're going to be doing testing this week to validate that the fixes that were that are being put in place for call delivery actually work. That's going on this week. And then we're working to with our service providers to figure out a way to remove these challenges and we recognize how difficult it is for these vendors to deploy a software upgrade. I think the largest supplier has equipment in over 300 PSAPs. I mean, you can't accomplish that in weeks or even a couple of months of time. It takes much longer than that just for a software upgrade. So and like I said, we went back to the standard and we've got a testing process to validate that all this work. So we're really going to ask for the help and support of the PSAPs with these, the DMARC testing and landing calls on your CPE. What we're learning is that I can test it here in the lab and it works. Beautiful shows. I don't have CAD, so I don't even know if it can be pushed to CAD. And I go out to the PSAP and I test it. It doesn't work at all because some little features not clicked or some little buttons not on or something's not working. So we fix that, then we try and push the CAD and it doesn't work. Well, it's the problem. We have to talk to the CAD vendor, we have to talk to the CPE vendor. We have to validate the next gen 911 is sending the location right. All of that work is what we're doing right now. And then obviously one of our key strategies is to get this cloud native CPE to be viable so we have another alternative if we continue to run into these barriers. And we we're not seeking a perfect solution. You know, five nines is availability is near perfect, but not exactly perfect. So don't think that we're sacrificing anything to make this work. But at the same time, we're not we haven't set such a lofty goal that it's not achievable and finding that balance is where we're at. We also are going to do a soft launch. So any anybody that's wanting to do like PR and public messaging and all that. This is kind of one of those things where you don't really want to be, you know, there, how many of you saw that really old Timex commercial where an elephant steps on a watch and it was live and they picked the watch up and was broken, they're like, well, I didn't work very good. You know, remember the Timex takes a licking and keeps on ticking. We don't want that. So we'll do a soft launch. Validate that everything's working. And then and we know that this is a huge, huge milestone for California and for the peace apps involved and the vendors involved and for the state. And obviously the support of the governor's office and the governor and the work that's been done to get to this place and the legislature and everybody else. But we'll do soft launch first and then we'll figure out what public messaging looks like later and that'll remove that complexity from the project. So those are the things we're working on now to try and fix and overcome these barriers. All right. And obviously the 911 first responders are critical to this. We've established test windows. We're going to be coming out and using those windows. So hopefully everyone has got the word. The test windows are Tuesday to Thursday from 10 to one. And on the day we do testing, we give you a call or a vendor will give you a call and say, hey, can we land some calls on your CPE? If you say no, fine, we'll reschedule. If you say yes, we'll put the calls in and we may ask you things like, what does the location look like? Does that look like what a normal call with wireless call would look like or a normal wireline call? Hey, can you transfer that over to CHP and then we'll ask CHP the same thing? It's that kind of effort that we're going to need to do to make sure that every piece up is ready and everything is configured properly. But I just have a question from the previous slide. Go ahead, Rosa. I know we've identified some possible possible barriers, wondering if we identified any barriers for secondary piece up. So the big challenge with secondary piece apps is you don't directly receive a call. So when we're doing our testing, the test numbers go into a primary first and then need to be transferred. So we have to remember that. But we have not seen any other barriers other than the testing involves one more step that when we want to test a secondary, we send a call into a primary, primary transfers it to you. Besides that, everything is configured the same. You've got your own boundaries, you have your own URIs, which is basically the the unique name we use to identify you. We treat a secondary piece up the exact same as any other piece up in the state. Same equipment, same resources, same focus. So we have not seen any barriers related to secondaries. Thank you. And then, Leanne, I think you had a question. Yeah, I had a question on the testing. I think that you guys have done a good job of rolling out that, hey, we're going to be testing from Tuesday through Thursday. If you need backfill, this is what we can do to help. But one of the things that just struck me was, hey, we're going to ask you. Did this call go through? What did it look like? Hey, CHP, you know, what did it look like? It sounds like you have some sort of acceptance test plan. Is there some questions that you plan on asking? Can you get those out to the PSAP so they know what they may be asked so someone doesn't get nervous and not understand how to answer what you're looking for? Yes, we do. And so I'm going to be at what we're tentatively planning to go to Tuolumne tomorrow. There's a lot going on in that part of the state right now. But we're tentatively planning to go out there and do some tests. We have a script that we've written. We're going to vet that with those PSAPs in that area. It's kind of just a baseline. It's not a lot. It's not detailed. It's more functionality. That would be what we're trying to minimize the impact on the on the on the call taker. So, yes, once we get that document together, we can share that with you. We also have asked our autos, who's our main vendor, to kind of give us a recipe. You know, we want to make sure, you know, the analogy I use, we're baking cookies and we want to make sure that when we put the cookies in the oven, they come out and they're good cookies and they're not, you know, defiled with, you know, walnuts and chocolate chip cookies, which is just a terrifying thing to me. You know, they actually come out the recipes vetted, validated, and you get the right thing that you expect when you're done. So we're having that meeting with them in conjunction with the data we're gathering from this testing that we're actually doing on the field, we being Cal OES ourselves. So, yes, long before we come to Monterey and subject you to this, we'll have this vetted sufficiently. It's these earlier ones that are helping us make sure we've got it dialed in. So so no raisins in the cookies might have been a better analogy, but but OK, well, that's no raisins either. No raisins, they're chocolate chip cookies. They're not no raisins in them. But but no, I just do think that, you know, as a lot of other peace apps are listening to this, they're going to be like, hey, you're going to take some test calls if and I know sometimes when we send forms out, people get overwhelmed because they don't understand the speak. So that's really what I'm advocating for for all, not just my agency. Yeah. And I was I gave a presentation at Nina talking about how challenging it is to coordinate a project of this scale and magnitude. And I said, no matter how much you do outreach, no matter how much messaging there is, there's always somebody that doesn't get the word and I'm not making this up and I hope she doesn't mind that I'm calling her out, but there was a county coordinator from California in the room who had not heard about our it was the telematics integration that we had done. And she raised her hands like, I'm from such and such in California. And this is the first I've heard of this project. And I'm like, well, there you go. There's the perfect example. We only have 58 county coordinators. They're very involved in what we do. And they were just busy and didn't engage with what the messaging was that we sent out and didn't know we got them immediately plugged in and up to speed. So that's the kind of thing that's going to happen. And we know that because you all are busy and you're not there hovering over your inbox, waiting to read an email from Cal OES might even be the opposite. You may have a filter on your inbox or you don't read emails from Cal OES. So and we understand that and that's that's going to have to be part of the messaging. OK, so we've gone over this slide. I'm not going to be labored this, but I left it in here because when we post this on our website, which I think is going to happen today or tomorrow, you'll have this slide on all the different testing that we're doing. We've talked through this a number of times, but there's, you know, our lab testing we've done. There's integrating and testing of CPE and then DMARC testing where you're testing next gen to connect to your PSAP and functionality and go live and carrier and all that a lot of work has to go in to making sure that this solution is vetted prior to you receiving your first 911 call. So I'll leave that in the slide deck for you to review. We got a lot of questions on where am I in the process? How are we doing? We developed a dashboard and I'm happy to give a quick demo on the dashboard. These links are on our website and the instructions are on our website. I'm going to try this. Let's see if it works. Live and hopefully everybody can see my current browser is not supported. What is Firefox, I think? Let's see. We'll see if it comes up here. No pressure. Yeah, it's not like everybody's watching. Oh, here we go. OK, so this dashboard is built to give you a status of where we are in the state. This is statewide. If you don't put anything over here and in the PSAP name, the stats default to statewide. And this is where I say we're over 80 percent installed. This is Autos installs after the region. So the region's installed Autos installed at 83 percent of the PSAPs. CPE upgrade, we're about 25 percent of our way through that. And in fairness to the CP vendors, as we work through some of these challenges, we realize that we're trying to validate the right version of software to install. So all you have to do up here in this search window is just pick your PSAP name. And I don't know, I can just choose one randomly. I'll go to Twallamy County Sheriff because that's where I'll be tomorrow. And when you pick that, the toggle boxes and everything change to that PSAP, you can put in more than one PSAP, you could put in 10, you could put in 20, and all the radio boxes and everything all update. And, you know, you've got the link there to the training and we made this public. It's available to everybody. We stripped out all the information that was that we consider to be confidential. So this tool is available to to those that need it. All right. And any feedback on the tool? I know it's been out there since the last advisory board. I don't want to see if anybody has any feedback for us on that. This is the date slide I was talking about every time I put dates up here, my team freaks out like, you know, are we going to meet those every time we show them they change? But based on what we know today, these are what we think could be realistic dates if we overcome the barriers that we know exist today. We could go live in September, maybe October with our first group of PSAPs. We know that November and December are challenging months for everybody to do a lot of work in the PSAP. So I put January for that next phase and then February, March. Once we get going and get stable on what we know is the solution, all the rest of the dates become much more firm and we could give you a much more definitive timeline. But until then, these are all just estimated. They're dependent on five or six factors that are outside of our direct control, but we're working together to overcome that. So that's what we're thinking today. Any questions on that? In the end, I think this goes to your question. It does. Thank you very much. OK, moving on. That's it on Next Gen. The last thing I'm going to mention is our location accuracy project. And what does Next Gen have to do with text and I'm one in the transition? So one thing we want to make clear is that all over the top tech solution. So if you're using Comtech today through a web browser, you will be migrated over to rapid deploy through their interface. And we will definitely begin that in November. And we might even start as soon as October, if the testing goes extremely well, but certainly by November. So if you are a Comtech user and your your team is not using rapid deploy today, you need to because it will dramatically shorten our training timeline for you to get over the top because rapid deploy is is who we're contract. I have a contract with to do over the top text. Well, it's with autos who subcontracted to rapid deploy. And we have this solution available to everybody. Many of you are using it for location accuracy through their radius plus product. There's an SMS text capability, meaning you can text from 911. And we also rolled out on star and integrated telematics into the solution. And I think there's been close to 300 different incidents of crash data being sent to PSAP, since a really good new story, instead of having to relay all that information manually manually over a phone line, it automatically populates on the rapid deploy screen and you directly see the crash data from on star. And that's available now today. If you have any questions or if you're that top bullet applies to you and you're not using rapid deploy today, reach out to Mel Bland. We have them create an inbox that was easy to remember OTT over the top. If you're wondering what OTT stands for at rapiddeploy.com, that'll get you directly into them and they can get you up and running on this solution. It's a really important part of our strategy for for everybody to be ready to use this product in this solution for over the top text. So any questions on that? All right. Almost done. This is our updated fund condition statement. You'll see 2021-2022 is on there. And the good news is if you if you've been around the advisory board for longer than two or three years, you can see my cursor down here. But these these positive numbers at the end of the year, they were all negative when when, you know, four years ago until we got the set in a fund restructured based on a flat rate on access lines. So the bottom line is we're healthy. We have the funding we need to accomplish the project. We've got the resources. We are putting in some requests to get some additional resource allocations for our GIS team and and to do that work. But but we have the funding that we need to do this and we are gathering the number of access lines right now, which is the next slide so that we can set the fee for a calendar year 2022. We anticipate it being very similar to the one that's in place now. The 30 cent mark, we wouldn't see, you know, any significant change to that and maybe no change. We're still crunching those numbers. They are due to the California Department of Tax and Fee Administration by October 1st. So by the next time we meet, I'll have these solid numbers for you based on our current fiscal year. These are what we set last year. So any question on the health of set note or on the funding that we've got of it? Or any other funding sources? OK, thank you very much, but any questions? Any further questions of budget? Then we will move on to the Long Range Planning Committee report out. Is that Chris Herron or somebody else? That's still me, Pat. Can't get away from this, can you? That's right. That is right. We talked about that yesterday. But good morning, everyone. Since the last advisory board meeting, the LRPC met just once. That was yesterday's meeting. And so just a few updates for you. We received the 911 branch strategic plan. And that is a document that is available on the website. And you just confirm that was sent to the advisory board members as well. Correct. Yes, it was sent to the advisory board members and it is on our website. Apologies, I thought that was mentioned yesterday, but so you should have all received that via email. It's also on the website. We discussed that, provided some feedback from our members. Our members have been directed to provide any additional feedback to the state in writing by the end of September. We then plan to review a final draft of that document at our October meeting. And the intent is to have have that ready, the state will have that ready for you at the November advisory board meeting. Our regional working groups met this summer and received updates from the next gen 911 vendors, including the project overview, as well as a migration plan that included a discussion about training and as well as what the service and maintenance of the new network will look like. Additionally, our GIS working group met for their meeting, they had an open forum where they discussed lessons learned so far in getting their GS data up to NENA standards, if you will. And that forum included a PSAP that did the work in-house with in-house staff, a PSAP that used a third party vendor to do the work. And then also one of the vendors sharing their perspective. Our last group to report to us was the County coordinators task force, the CCTF, as they're known. It's been resurrected, so to speak, after being dormant for a bit, at least as it relates to the state. They've now assigned coordinators for each of the regions that match the next gen regions that were created. So there's CCTF coordinators for the north, the central, the south and LA. They had some discussions about the role of the county coordinators in the next gen environment and wanted to share that it's been identified that during the transition to next gen, there actually will be a heavier workload on those county coordinators because they're going to have to maintain and keep up the databases, both for the legacy and next gen networks until the full transition. That is the end of the report from yesterday. I think the next item. You guys can tell me, do you want me to go ahead and introduce that? Butcher, Paul, or did you want to speak to it first? Item seven. So, Pat, I don't know if you want to get any feedback or questions from the board members on this item first. Sure. So, so, so are there any questions of the Longreach Planning Committee before we move to item seven? See, I foresaw that. Well, you answered everything very well. Thank you. OK, let's move to item number seven, but I'm going to let you take this. Yes. So, you know, Chris has has been serving as the chair of the Longreach Planning Committee for some time and we looked at the charter and what the charter says is that advisory board members are to review and assign Longreach Planning Committee members and with the new members that we have on the board, we want to put this as an agenda item. We can certainly put it on the agenda again next time so you have more time to think about it. You know, there's no requirement to replace who your corresponding Longreach Planning Committee member is or the person serving there. But the opportunity is there and that that's the way the charter is written even to replace the chair. No offense, Chris, you're doing a great job and I try to make any comments there, but this agenda item is here for that reason just so that you all know the process. And then, Chris, you want to cover the various agencies that are represented and the vacancies as per the charter? I think that would be helpful. If I could, please. Yeah. And so I think just that as a reminder, what Ledge just said, that our charter calls for the makeup of the group to be a representative from each organization that's on the advisory board. And so our current makeup, I'm serving as the chair. I work for North County Dispatch JPA in San Diego and I'm representing the Fire Chiefs Association and we have Jodi Pat, who works for the city of Escondido, representing police chiefs, Leanne Magosti, who works for the Monterey County and Rosa Ramos, who works for Alameda County or both the Kalmina reps. Desi Calzada, who's from Stanislaw Regional 9-1-1, is the APCO rep. And then Alicia Fuller from CHP, representing CHP, is our final member. We don't currently have a CSSA rep, so certainly that is open. And then the charter does allow flexibility. So if there are organizations that want a second rep or what we've done at times to help with succession planning, it's always nice to have a little bit of overlap so that it's not just one person's here today and gone tomorrow. So we the charter does allow us to have two members from an organization. And I think it's especially helpful in that regard. So I know for me personally, I've I reached out to the two new CFCA reps, and I'd certainly encourage all of the advisory board members to be in contact with your LRPC reps, if you're not already, and then you can communicate back to the state if any new nominations or changes or desire budget, just recommend we could do two things. One is I could send the current roster to you and the charter and then for distribution out to the advisory board members, unless there's other questions or comments. I do have a question. I I may have missed what the commitment is for that particular committee. If that could be included in the materials, that would be really helpful. Some of us have some pretty impacted schedules. Thanks. I'll include that. And actually, it's probably fair to answer here. So everyone knows we typically we meet the day prior to all the advisory board meetings, so four meetings. And then we have two off month meetings that are typically one in the spring, one in the fall, the last couple of years we've done those in April and October. So six meetings per year. Now, you know, the last 18 months, these have been remote. So the commitment's been fairly easy, typically, though, these are public meetings that are held in Sacramento. So and Sheriff, if you want to get a sense of sort of the view that this long range planning committee has, that strategic plan that we sent out, those are the exact things that we talk about. So that'll give you a good sense of kind of what is the conversation like. A couple of years ago, we started to get a lot more specific on operational questions, which we certainly can answer. But we've we've moved away into more of this long range planning. So it's not that we don't we cannot address operational issues because we do day to day stuff and, you know, as Chris as the chair brings it up, we certainly answer those questions, but it's more strategic in nature. And that strategic plan really highlights kind of what this group is trying to do. And we view them as a valuable resource to make sure that we're being compliant, not only with our statutory requirements, which we think are very clear, but also the operational needs of the PSAP and that we were keeping in mind basically our customers, you know, who we're serving as we develop our long range plans and and move nine one one and all of all of the other technologies that are in the PSAP forward. And that's really what this group is about. OK, well, I think, Chris, you raised a good point. If you can send out a list of that stuff and and, you know, some of the supporting documentation, I will make sure that we get it out to all the board members and thank you for your question. Sure, if I have a spot on. OK, let's move on to the next item, which is the strategic initiatives and budgets back to you again. Yes, we've mentioned Chris mentioned this at the meeting. You know, we're not going to I'm not going to go through this in detail today, but I am really asking for feedback from the board members. We were giving you over a month to do this because we realize that it's, you know, it's going to take some time. I want to say the documents less than 10 pages long. It's about eight pages, so it's not a long document. And what we do is we list the mission of the nine one branch. This is this is from our perspective, but we need your input. And then we've identified three high level goals. And then within the document, you'll see each goal has a number of objectives. And then each objective has a number of strategies that are used to achieve the objective. And then the bottom portion of the strategic plan lists the metrics that are used to measure the effectiveness of how well we are doing and achieving the goal. So you'll see a goal and then a metric and a number of metrics under it. So there's a measurement of how are we doing? That's the match, the metrics and then everything aligns. It's on our website. So it's a Word document. And if you have any feedback at all, we're asking you to email those responses back to Sophia. She'll coordinate all the data. We'll meet with the Long Range Planning Committee. We'll adjudicate all those responses. We'll come back to the advisory board in November with their recommendations on what they think should be in that plan. And hopefully we'll finalize that plan at the November 17th advisory board. It might be a little cumbersome to go through this publicly, but we're certainly willing to do that. I forgot a way to facilitate that. I've served on a number of strike forces and at the FCC level and large groups. So we'll figure out a way to share those comments and we'll really probably bring up the areas that the Long Range Planning Committee identifies that where there may be a need for a collaborative voice on. But generally, the way we'll present that at the advisory board is here's the points that we want to get additional clarity on and we'll finalize the document. OK, thank you, budge. Any questions from the board on this? All right, let's move on to agenda item number nine, which is future meetings. Next meeting, as Bud said, was November 17th, and we do have the meetings for 2022 shown here. Are there any items that the board would like to see on the agenda for the November 17th meeting? Pat, and I'm sure Budge is going to have this ongoing. But just that update of if there are any key saps that are having problems with their CPE or, you know, what's going on? Or as the I forget the new gals name, but as she gets implemented, the realistic ability to implement as we switch over to cloud and what's going on with the CPE in the meantime. OK, budge copy. So a copy will make sure it's on there. OK, any other comments or any other items that the board would like to see on the next agenda going once going twice? OK, next item is a public comment. So the floor is open. If you would be so kind as to raise your hand, then we will call on you for to pose your question. Any questions? All right, let's move to agenda item number 11, which is adjournment. Is there a motion to adjourn? Well, I don't make the motion to adjourn. You have a motion to adjourn by Liam Mugoski. We have a second second. I'm sorry, who was that? Rosa Rosa. OK, thank you, Rosa Ramos. Without objection, we will stand adjourned. Thank you all very much. We really appreciate your participation. Have a great afternoon. Thank you. Thank you very much.