 So, welcome. My name is Budge Currier. I'm with the 9-1-1 branch with Cal OES. And we hope you're all here to talk about NextGen 9-1-1, because that's what primarily we're going to talk about today. So, the agenda is on the screen as I talk through some of these agenda items. If you want a copy of the presentation, send an email to Andrew. His email is up on the screen, and he'll send it to you right now. We don't have this posted on our website yet. This is version 13 of the slides, lucky number 13, hopefully, maybe the last version. And in order for us to post it on the website for the state, it has to stabilize and we have to run it through ADA compliance, which takes some time. So, to get around that, if you need a copy of the presentation, send us off an email and we'll get it to you while you're sitting right here. So, we're going to be talking about NextGen 9-1-1. I'll walk you through our RFP process that we used to select our vendors, give you an overview of what we're doing in California. Talk a lot about how this will impact your PSAP in hopefully all good ways, but some of the ways you're going to want to ask some questions. I want this to be interactive. It will take us till 3 o'clock to get through this. We have a break built in, so if you're thinking we were kidding, we weren't. That's about how long it's been taking. And if you have a question at any time, just interrupt, raise your hand. What we're doing today is we're going to tape this session, which is why you see the cameras and the microphone, and make it available as a YouTube video so that anybody who couldn't be here, or if you want to remember what was said, you'll be able to go back and watch it. So, in a couple weeks, we'll finish our editing and get this posted up on the website. So, as I go through the presentation, I'll introduce different people from the Cal OES team that are here. There are many in the room, and I'll let you know the role they play in the project. Alright, so before we get going, any questions? Alright, so we may, Andrew, we may want to think about some more chairs. Yeah, looks like we're getting pretty full. I only see about 5 or 6 open. Alright, so I want to start with this graphic. I've used this many times. It focuses on how all these technologies are connected in your PSAP. And we'll talk briefly about what each one of these is as we go through the presentation. So, Next Gen 901 obviously is what we've all been talking about for about 10 years or more. Believe it or not, it's here, and it's coming, and it's coming probably faster than you thought it would. So, we're going to go through those timelines today. The other piece of the equation is land mobile radio. So, while we can't fund land mobile radio out of 911 funds, alright, that's an FCC rule. We can't do it. We do help coordinate some of your land mobile radio activities. So, we have some guidance documents. I have a whole part of my team that help coordinate this type of your land mobile radio statewide. So, if you have any questions on available, grant funding, policies, procedures, and how to integrate it, let us know. We can certainly meet with you. We're going to talk a lot about alert and warnings today and how we've leveraged the Next Gen 901 system as a delivery platform for alert and warnings. And I've got 4 or 5 slides dedicated to that. And then we'll talk briefly about broadband services. So, that's that piece that's carrying data from your PSAP out to the mobile data terminals, mobile data computers that are out in the field, and some of the other applications that are being run across those broadband services. Obviously, FirstNet is a piece of that, and so are some of the other providers, and we'll talk through that. I put this graphic up so that as you're talking to your police chiefs, your sheriffs, fire chiefs, city managers, boards of supervisors, whoever you're interacting with at the decision level, they understand the importance of what we're doing and what this is going to bring for your PSAP. So, I've got this list up here on the board. We're going to, it's definitely going to help to harden our system so we can survive some of the disasters that we see. Right now, you've got camera trunks coming into your PSAP. They're a single point of failure. When any of those go down, you lose your PSAP. How many of you have had an outage in the last month or two, either with your 911 network or your Annie Alley? So, I see some hands go up. If this system was built, if the system was hardened the way it should be, no hands should go up. Certainly not in the last month. And that's what we're moving toward. We're going to talk a little bit about how the system will allow you to reroute 911 calls anywhere, literally anywhere in the state. So, just for fun, we could send all the calls down to LAPD if we want, right? And so, we'll talk a lot about that. It's going to reduce our system downtime. You saw the hands that went up in the room of how many have had an Annie Alley outage or a network outage in the last month or two. It'll allow us to leverage Next Gen 911 as a common delivery system for alert warnings. Again, I'll talk about that later on. We're going to make sure that the calls are delivered quickly and accurately. We're seeing that in general, in the existing legacy network, it's five to seven seconds in a perfect situation of when a call gets delivered. Next Gen 911 is probably closer to three seconds and maybe faster. So we'll talk through that and we'll increase our location accuracy. And I'll talk a little bit about, later on, the presentation, our rapid deploy project and what we're doing with that project. And you'll be able to ask some questions. Really, this last bullet is really important to think about. Once we deliver a secure IP connection to your PSAP, we can leverage that connection to do all kinds of other things that are important to 911. And it's really helping us to think through what those possibilities are and how we deliver them. So when your leadership comes to you and asks you, why is this important? Why do we need to do this? Feel free to use this list as a starting point and then talk about how it's going to be beneficial to you at the local level. So we're here today because we've made some huge progress on what we're doing for Next Gen 911 in California. We announced on August 20th our vendor partners that are going to help us build out this solution. So you see on this map, this is a breakdown of the regions in California. That purple region to the north is the northern region. The section in the center in yellow is the central region. LA is its own region just by call volume and number of PSAPs. And then down in the south is that region in the green. In order to make sure that this network doesn't go down and has the reliability we need, we selected a prime vendor. The name of that company is Autos. They will be connected to every single PSAP in California. So that way if one of the regions has an issue, then it will be able to route those calls to the prime and the prime could deliver that call. They also serve as a way to make sure that the system is standardized so that everybody is delivering based on the same set of standards. So we've got a representative from Autos here if you want to introduce yourself. Sure. Good afternoon everyone. Thorotherum from Autos. I'm our global head of product strategy. And as of two days ago, an officially self-appointed coffee bringer for these sessions. Yeah. Thank you. You're welcome. And the home baked cookies were made by me in case you don't like them. They're actually my wife's. I am local to the area. I've lived in either Roosevelt or Folsom for the last 21 years and actually been active in public safety for the last 27 years almost. Excited about this project working with the state, with the regional network service providers that are here today as well. So thanks for that. All right. And then our project manager on the state side is Ann if you want to stand up and introduce everybody. So our single point of contact for everything related to the prime is Ann. So if you have any questions, go through her with regard to that, with regard to the prime. Now where we are today is in the northern region. And so the company that was selected to deliver services there is Cinergem. So Danny, I know you're here if you want to introduce yourself. Good morning everyone. My name is Danny McGinnis. I am at the Cinergem. I have been in Cinergem for some years, mostly deploying NG-91, like NG-91 around the country. All right. And then our project manager on the state side is Angela if you want to stand up and introduce yourself. So she'll be your point of contact in everything related to Cinergem and how that deployment is moving forward. We know there may be some from the central region here. So the central region we awarded to NGA-91. If you guys want to introduce your team. I know Donna, if you want to do that. Darryl? Hi, Darryl Lippert, senior vice president of strategic relationships for in Toronto. And I am the executive liaison to power the S4 this project. All right. And with us is Don Ferguson, who is our CEO. And Michelle Bland, who I'm sure many of you know is our senior vice president of operation. All right. So moving down through the state, the LA region was also awarded to NGA-91, the same team, a different project manager from their team. And then on the state side, Cherise is our project manager. I don't know. I haven't seen her in the room. She's not here today. We had to leave somebody back in the office. So Cherise is the project manager for that region. And then down in the south, we selected CenturyLink. And CenturyLink, they don't have any representative here today, but they will at subsequent meetings. And Kurt Galat is the project manager from the state side. And I know he's here somewhere standing up in the back there. So these are the partners that we've selected to deliver these services. And I want to talk through a little bit about how we arrived there just so that you understand how we selected these vendors through the state process. So we used the competitive bid process. How many of you have participated in procurements and RFBs? What a fun, lovely process, right? We're all, yeah. So we went through a process. I'm going to walk you through some of the steps at a high level just so you understand how these bidders were chosen. A total of eight bidders started in the process. And in the end, we ended up awarding to the four that you saw. We established there is a requirement in California that 911 services have to be tariffed. So what that means is that each of these vendors that we selected, they have to file with the California Public Utilities Commission a tariff that defines their service and the price for that service. So once that's done, and for three of the four companies that's done, as a matter of fact, all the companies in the room have finished that process, what we were able to do in the contract is we've defined the service. And if we figure out that we need 12 of something instead of 10, we don't need to do a change order and go back and modify the contract and everything. We simply reach out to tariff and get two more of that service that's already defined at that price. So that gives us a lot of flexibility in how we deliver the service. And then obviously we have the regulatory oversight of the PUC on our side to make sure that they're willing and able to deliver the service that's defined there. So it took a lot of coordination, but once we get it in place, it's really going to save a lot of time in the project. We also established not to exceed pricing. Sometimes in procurements, you have to throw out the high bidder or the low bidder. And we don't want to do that because you could inadvertently throw out a bidder that either misunderstood something or has a good delivery and just missed the price. So we did a lot of market research to figure out what next gen 91 services should cost and everyone had to comply with those not to exceed costs. We listed a bunch of functional requirements. There were about 100 or so of them and they simply had to answer, each vendor had to answer yes or no. If they answered no, then during, we would talk to them and if they couldn't get to yes, then they were gone. And then we took those things that were important to California. There were about 30 of them and we asked each vendor to write a narrative description on how they would meet that requirement. So we picked those things that were unique to California that we wanted to make sure that they could deliver on. They wrote a narrative and we evaluated those scores. The top scores are the ones that we ended up selecting. And we also took another step if there were those who asked for changes to our contract or they couldn't agree to our standard SLAs that were in the contract or they wanted to modify the statement of work, those bidders didn't make it through the process either. So that's how we got to where we are. All four regions have a qualified bidder. Don't think you got last place. Everyone is qualified, able to deliver the services in California. So any questions on that before I go on? All right. So I put this slide up here so you can see our timeline. We started last February in this process. When we released the original RFP to when we awarded, not one date changed. We didn't miss anything, which is quite a miracle in and of itself. Matter of fact, a couple of them we even were ahead of. Like it says up there, all contracts signed by August 30th. ATOS's contract was signed on August 20th, the day we announced. And the other two vendors that are in the room were signed a couple days later. So that's not just signed by them. That's signed by the state as well. Like completely executed contract within two to four days of when we made announcements. So we're moving pretty fast through this process. And you see our goals have tariffs filed by the end of November. Three or four have already finished their tariff filings as well. And the fourth one is well on their way to getting that done. So we've got a pretty aggressive timeline. We've met all of these dates and we're pushing forward. We want to make sure you understand what these bidders are doing for the state of California. So I put this graphic up here. I'm not going to talk through each of these points, but we're making sure that the service delivered matches your need, which is why we're here today. We want to tell you kind of where we are today, so you can give us feedback on things that we may have either overlooked or haven't emphasized or haven't outlined. So this is really the first step of that conversation. This slide you can't read. I know that. I can't read it. I'm standing right here. But the reason why it's in the deck is so that when you ask for it, you've got the name, email and phone number of everybody in every region and on the state side the project manager so that you have the ability to reach out and contact these folks directly. So ask us for a copy of the presentation. We'll keep this current on our website and if it changes, we'll immediately let you know if something's changed. We don't anticipate any changes, but we'll make sure that this information is available. We're going to spend a few minutes on this graphic and this is where I hope you start asking questions because this is really what Next Gen 9.1 is all about. So this graphic here shows what the network is going to look like and how it's going to be used to deliver 9.1 calls to your PSAP. So I'm going to talk through this at kind of a high level. Over there on the left-hand side where it says legacy and wireless OSP, those are your originating service providers. So that's your AT&T wire line, frontier, consolidated communications, all the small Lex that are in the state, all the voice over IP providers and all the wireless providers, AT&T Mobility, Verizon Wireless, T-Mobile Sprint, and anyone else that's out there. So once you make a 9.1 call from any one of those vendors or any one of those originating service providers, it's going to come into what we call a point of interface or a POI. If that call is already an IP packet, it's already in SIP format, then we'll just route it on. If it's not, it'll be converted. What that does is it helps us with some of the rules that are in place with the California Public Utilities Commission statewide. So we'll convert that into an IP packet and then it goes down to one of these two aggregation centers. I have a pointer but once you put it on the screen, it doesn't work. So those aggregation centers, what they're there for is to make sure that if the region is active and able to deliver a call, then it goes to the region. If the region's not available and active and able to deliver a call, then it would deliver it to the prime and the prime would do that. That's how we back ourselves up. So this entire network that you see here on the right is duplicated down here in each one of these region ESI nets that you see. So you'll have to imagine in your mind, the chart would get ridiculously complicated if we put that one in there. But all that infrastructure you see there is duplicated and managed separately and independently for each of the regions. So as we move through the network, you see this thing that's called 9-1-1 access kind of in the center there. That's a segmented IP network that's intended to connect all the regions together, the data centers that are in each region, the data centers that are managed by the prime, by ATOS as they're processing calls. The next network segmentation is the PSAP MPLS or the PSAP network layer, which runs from those data centers that you see over to the PSAPs. The primary purpose of that network is to make sure we can bring a call to your PSAP from any data center that's used to support this solution. And you'll notice there's two lines going into the PSAP there. There's like two lines that run up into your PSAP. We've already begun to work with the providers we selected, and they've given us a list of IP or wholesale IP providers. We want two logically and physically diverse paths into each PSAP from each vendor. So that means ATOS will be bringing two connections into your PSAP and your region provider. So if most of you are probably in the north, Cinergym will be bringing those two connections into your PSAP. That way we get a system that has the reliability we need in order to support 9-1-1. And just to make sure that it's reliable, just because this IP connection is going to be extremely important, we're building out over on the far side, you see a little bubble there called CapsNet. That's a statewide microwave network that's on 300-plus sites that we will extend into the PSAPs throughout the state. So if you have, the only exception with that is if you have a county or city-owned microwave or fiber network that you want us to interface with, we'll interface with that network. The idea is we want to do a connection into your PSAP that's completely independent of the commercial providers. That way if there's something that happens on the commercial side, we still have another path into your PSAP. So for CHP and CalFire, I know you're both in the room. At almost every CHP site and almost every CalFire site, there's already an existing microwave link. We'll be looking to convert that over to a digital path with the ability to bring 9-1-1 calls across that link. So if you have a microwave network in your county or city, let us know. If you don't, then we'll be coming to talk to you about, okay, is there room for us to put a dish on your tower? Is there room in your back room for us to put the equipment to put a microwave link in your PSAP to add another level of redundancy into the system? And then we went one step farther and you see there, you see a little bubble in it that says LTE. That LTE will be a cradle point router with dual sims in it and we will pick the carrier that has the best throughput to support your PSAP. So it could be an AT&T connection using FirstNet, could be Verizon, it could be T-Mobile. We'll come onsite and do a test and figure out which one of those is the best and we'll put that in. All of these are managed by our vendors with the oversight of Cal OES. None of this touches your IT infrastructure at your PSAP. Nothing. We're going to be completely independent. We'll talk about that a little bit. All right. And then you'll see a couple other pieces up there. Text to 9-1-1 is a cloud-based service that's integrated with this as well as alert and warning and we're going to talk about those quite a bit. All right. Questions. Somebody has to have a question, I'm sure. Yes. For the microwave. So question was if you've got a microwave connection into your PSAP, is it required that we use it now? We could do either or talk to us and we'll figure out what makes the most sense. If we couldn't find space on your tower, space in your back room or a frequency to bring that to you, we might talk to you a little bit more about using something you have. But we've included that as part of our plan to extend our microwave network all the way to your PSAP. Yes. Yes. So it's even easier than that. So if a call comes into your PSAP, a question was if a call came in to where, what PSAP were you? Calaveras County for, and they want to be transferred to Pasadena. So way down in the south through, I guess. I think it's, yeah, the south. So what would happen is you would just simply transfer that call and then the system would know, okay, that's not connected to me as a region. It would route that call to Prime to Atoast and Atoast would deliver that call to Pasadena. Absolutely. It's exactly the way it works. Yep. That's exactly how it's going to work. Yeah. All right. Yes, in the back. As far as with the microwaves, where I'm at, we're right on a scenic highway and so we have a lot of restrictions on what can be installed where. Is there going to be allowances for this type of situation to kind of bypass that or work with that or anything along those lines? Okay. So the question is, if you're in a location where there's some pretty severe restrictions on what can be mounted to a tower, can we bypass that? No. But we will, we work in those conditions as well and we can apply for the permits and see if we can get it approved and put in. If we can do it, we will because obviously it's adding another layer of resiliency to the network, which is what we ultimately want. So we'll work with you and see what's possible. All right. Maybe we try and bring a much smaller dish into your location. Usually those are approved a little bit easier. We've even done things where we've put in an RF transparent, you know, interface that looks like, maybe it looks like an old wooden water tower or something and then the dishes behind that. We've done that in a few places too. So we'll see what's possible. Each one of these is going to be kind of unique. All right. Other questions? Yes? Are there bases also with the locations that are looking for the router take place? No. We are not, there's no need for selective routers in this scenario. None. No. We're not connected. Are there any questions between the legacy and the transition yet? And are these actually being all already in our industry network? Right. So the question is, when we're, let's say that a region comes on first, right? Pick one. Say the north comes online first. Danny and Senator Jim are just out in front of everybody and they're fully deployed and then they need to transfer to a PSAP that is not on next-gen 9-1-1 yet, meaning they're connected to a legacy selective router. In that case, we may, may, and we haven't built this into our plan, have a connection into a legacy selective router. The far better way to do this would be to say, autos, you're the prime. You're connected to every PSAP. You've been selected because you're the leader and you're going to go first. So any transfer then, if autos can be up running and connected to every PSAP, we don't need a legacy selective router transfer. That's how we want to make this transition. Otherwise, the network paths get very complicated for interconnecting with those legacy selective routers. We have 45 of them. I think it's 45. Is that the number in the back? How many legacy selective routers are there? 45. And you can imagine the spaghetti point-to-point connection that would be needed to support that, which is why we're not doing it that way. So we're encouraging autos to go fast and correct, and that's how we would accommodate that. Far better way to do it. We're encouraging, so the question was, will every PSAP be on the prime before we go live? With a region. With a region. That's the goal, right? Now some of the regions are going to beg to differ because they're going to be going just as fast as the prime. That's the goal, right? Because then that solves a lot of these problems. The other thing to keep in mind is both these networks are up at the same time. So the legacy network and the way you're receiving calls today is going to remain in place until this network is up-tested, functioning, and integrated for the very reason that you just said. Otherwise, the point-to-point connections we need to make to do transfers through a legacy selective router is going to be extremely complicated, which we did not want to do. Yeah. That's a good question. All right. Other questions? Okay. So let's start getting into some of the details. We want to make sure you understand that the region vendors are not subcontractors to the prime. The region vendors are delivering a fully compliant, fully capable Next Gen 9-1-1 solution. The data that's shared between them, but in the absence of being able to share that data, the region can still deliver the call the way it's supposed to be delivered. So sometimes you use the term prime, and you think, oh, they're the prime contractor and everybody else is a sub. That's not the way that this works. The prime does have some unique functions. They're going to be the ones that develop the interface standards that you see up there on the left-hand side to make sure that everybody can work together. They're also going to be responsible for having one deployment, an alert and warning, and some of the other system-wide monitoring and decisions that need to be made in the network to make sure this works the way that it has to. And there's very clear and specific requirements for collaboration throughout the process. And they've already begun collaborating, which is great news. And there's some pretty big incentives for them if they don't collaborate. So we want to make that clarity. Where we are right now, we had our initialization meetings with all the vendors the 4th through the 11th of September, and on the 11th we had all the vendors in the same room. Had some great dialogue on roles, responsibilities, how this collaboration would happen, priorities, meeting schedules, and all that has begun to happen. So think about how fast that is, right? We awarded contract on the August 20th. Contracts were signed by the 26th, and less than what, two weeks later, we're already meeting with the project teams for each of the vendors. So we've been moving pretty quick through this process. Our project managers will be your main point of contact, but we know you also are very familiar with your PSAP advisors. So if you want to reach out to your PSAP advisor, then please continue to do that. I think we have some of the advisors in the room. But I have the advisor-supervisor who will make sure that gets done. So that's Andrew. Andrew is the supervisor over the four PSAP advisors. So hopefully you know who your PSAP advisor is, and you've talked to them recently. All right? We're going to be sending out, obviously we're doing these town halls. We've got six more to go, five more after today. So at the halfway point today when we take our break, I'll be half done. And then we'll send out an email by the 18th with all the coordinating instructions. And then tomorrow we're waiting a little bit longer to send that out, because we've been getting some good questions in these meetings. And we want to make sure we address those questions in that email. And then after we send that email, that's when we'll start the engagement with the PSAP surveys. So you could be expected to be contacted by your region provider, Synergym, and the prime, somebody from Autos. Because they're both going to need to come to that. Those surveys should happen in November-December this year. Well, they will happen in November-December this year. This is a look at our schedule and where we are. So early on we formed our project teams. We're done with that step. We are going to schedule site surveys. That's kind of the next big thing coming. We'll finish that up by the end of the year. The next thing we're going to do is begin to order circuits. As a matter of fact, that's already started. What we did is we asked each vendor to give us a list of who they're going to use to bring that IP connection to your PSAP. And then we took a look at what the region provider sent us. We'll take a look at what the prime, Autos, is going to deliver. So we can make sure that everybody's not using the same provider. Remember we want logical and physical diversity on those connections. It might be that you're in a really rural area and you know there's only one provider. Like only one IP connection can reach your PSAP. In that case, we will still bring two. One that's managed by your region provider and one that's managed by the prime provider. That way we at least get logical separation between those two networks. And then we will start working with other providers to see if we can find another path into that piece, into your PSAP. So obviously these circuits are going to come across probably companies you're familiar with. We've started a project with Comcast to bring fiber to every PSAP in the state. And they're working with Charter and Cox depending on what company you're in or what county you're in. And we also know that AT&T with their telephone network is going to be a big part of this project. So we're working with them and other providers that have large networks will probably be involved in this as well. All right. The SD-WAN that's a software defined wide area network. What that does is it enables us to take a look at all these IP connections and see what paths are available. Like how can we reach your PSAP? So that if one IP connection goes down, this SD-WAN controller will know, okay there's another path to PSAP going this route and it will route the call that way. It's not a point to point network like you're used to today where if you cut one point, you're down. This network doesn't work that way. Each of them are going to build their own network operations center and then they'll be we have in the contract the requirement for that system monitoring to be linked together and we'll be able to provide some interface to you at the PSAP of what this next Gen 911 network is doing, the health of it and what it looks like. Each of them are already starting to build their engine core services. The intelligence that's used to route the calls and do everything we need in next Gen 911. They're already starting to build these as a matter of fact, NGA 911 has a cloud solution and I think it's ready to go now, right? I mean this is done, ready. And others are coming online soon so that's part of this deployment that's happening. Once we get a connection into your PSAP it's tested, vetted, validated and the interface equipment's there is what we do is to make sure that we can connect to your CPE. So we're building a lab, matter of fact the contractors were there yesterday doing their, or was it today? Today, doing their walkthrough. We're going to put two positions of Viper, two positions of Vesta and then two more positions in there for testing. We're going to bring all four vendors in. So the interface from the next Gen 911 network to your CPE will be tested and validated in a lab before we even come to your PSAP. But, we still have to come to your PSAP and do the testing and that will happen in a perfect world toward the end of 2020 is when we'll start that testing. Alright, any questions on that timeline? I'm going to talk about some details here in just a second. Alright, now what can mess that timeline up? Because that was an optimistic timeline. There's some hurdles we have to get over. We know that, right? The first one is just availability of network connectivity. I need to be able to bring an IP connection into your PSAP more than one in order for this to really have the reliability we need. So we're going to work with you to figure out what that is and our vendors are already scrubbing that list. We'll have a pretty good idea within a month or two where the gotchas are for that one. We need available space in your back room. How much space? Well, hopefully before all of you came here, you knew you had a question. I had one meeting. So you went in your back room and you put a piece of tape on the floor and you extended out a nice full rack space, 19 inch rack with a twist lock, 20 amp dedicated circuit and grounding. And you labeled it with Cal OES because you knew, you just knew. How many did that? Okay, well, that's really what we need, right? We need about an entire space for the equipment. Probably is only going to take about three quarters of a rack but that's really what we need and we know that's just not possible in every single piece. Which is the reason why we have to do site surveys and come talk to you and make sure we can work through that. So we have to coordinate with you. So when we reach out to you to schedule these meetings and you come back and you say, okay we can't this week doesn't work but couple weeks from now is going to be fine. Okay, we could probably do that. If you come back to us and say this isn't going to work we'll come back in March. No, no, no, we're not waiting until March. So we need to find somewhere between now and the end of the year we can come into your PSAP with both of these vendors and get these surveys done. Right? And so we have to work with you. So if there's something you know, you've already got a planned event some other install, something else that's going to impact your PSAP reach out to our project manager and let us know so we can block out that in our schedule we'll communicate that back to the vendors and they'll know, okay we can't go to this PSAP during this two week block. All right. Obviously your local IT people may be a little bit excited about what's going on here. How many IT people are in the room? All right, we have a few. You're probably like, it's a lot of scary stuff. Well this week we promise this we're not touching your network because we don't trust you and it's mutual, right? And you don't trust us. But if you think about it from a security posture that's the way it should be. We're not going to use anything, any existing IT infrastructure at your facilities with maybe a couple of exceptions if you tell us, look there's this conduit that you can pull fiber through okay those are the kind of conversations we need to have or I've got this segment of dark fibers sitting here we're not using, you could use it that kind of stuff. We also want to be very clear that this equipment doesn't need to physically be in the same room as your CPE. So your call process and equipment could be in another closet or another room or something as long as there's a path between the two. It doesn't need to physically be located in the same exact spot. So really the coordination with IT is just to make sure you know what we're doing you know where these cable runs are. We have from you how to mark, label them and everything and then you're confident that we're not going to touch your network and you're not going to touch our network then I think everything is going to be fine but there's a requirement there's going to be some when you go back, if they're not in the room and you tell them what we're doing, trust me this is the reaction they're going to have as we see all the IT people here and then the connections to the Originating Service Providers. We have to work with all those and be able to be able to ingress bring those 901 calls into the network and that's really on us but if we run into some challenges there it could certainly impact the timeline. So now we want to talk about what we're going to do at your PSAP in the near term. Any questions on this before we go on? So in the near term how is this going to affect your PSAP? Well you can anticipate, like I said, about a rack of equipment. The vendors that come are going to identify where this equipment would go please don't install other equipment in there after we've been there and once we start installs don't rip it out and throw it away. We've had that happen before too. Hey what's this stuff? I don't know. So we'll coordinate with you, we'll clearly market, label it. When the vendors come they'll label. We're doing a form a survey form. It's very lengthy and we're going to highlight in yellow all the stuff that we need input on from the PSAP and then it's about eight pages long. There will be other things in there that you don't have to fill out. So just the stuff in yellow so don't think, oh it's eight pages I got, no it's just the stuff in yellow. We're also going to work with Andrew and his team and anything we know about your PSAP will pre-populate in that form. So that you don't have to go through all that work alright. If we haven't visited you in four or five years then maybe there might be less information that we know for sure but we'll put what we know in there. The first vendor who shows up will fill the form out then they'll take that filled out form and share it with the next vendor so that they don't have to do the same work again and they can just validate it. We would like to schedule ATOS as the prime and your region provider on the same day. It may not happen there's a lot of moving parts there. They're using folks to do their surveys very difficult to coordinate those schedules but where we can we will but that's how the process will work. So we'll send you that form it's going to be long like I said there's a lot of stuff on there that we need to know and we want to let you know what we're looking at as we plan this project. The goal is a standard rack configuration at each PSAP like a dedicated rack at each PSAP. It just helps us as we move into the future. It may not always be possible. You might tell us you can have this half rack here and this half rack over there. Let us know when we get there and we'll work through those challenges. We know that you may not all have the space so you might have your equipment mounted in a broom closet and there's just no space at all. We need to know that. We have the ability to go out to a state contract, CMAS, get a vendor on board and come in and make space for this equipment. We can mount it on a wall. There's a whole bunch of things we can do to get this equipment in your PSAP. But at the end of the day we need a 20 amp dedicated circuit with a twist lock grounded set of equipment and we'll bring UPS for that rack. That's what we need. If you have a grounding system in your back room that you want us to integrate with let us know when we get there. We could probably do that as well for backup power grounding and whatever you've got at your facility. Questions on this because I know somebody has a question about back room. No, we're not going to build you a new PSAP. If you're thinking, alright we're going to get a new PSAP. No. Any questions on that and how we're going to do the surveys? Concerns. All we need is we will provide the rack. Yeah. And if you don't have the twist lock plug or whatever, we can do that too. That's part of what we need to know when we come to the survey. We want to make this clear. This is not an unfunded state mandate. This is not what this is. We're going to do our best to accommodate what needs to be done at every PSAP. Any other questions? Yes. When should we have to state the survey to go out to the center? Well, for Cal Fire we'll coordinate with Bubba because we've learned he's got to be in the loop. But we will send the initial email from Cal OES will be before the middle of October. So you'll have all this and in there we'll put here's the standard rack configuration requirements and all that. And then following from that you'll get another individual email introducing representative that's going to be on site. Here's target dates and all that and then we'll start that coordination process. That'll come from a project managers and Cal OES initially. So if you're deleting Cal OES emails not that anybody does that you're going to probably want to remember these names up here because when they come in from them you might want to read those because they're going to have some important information in them. But it'll come from that project manager that's a good question. All in the same rack. Everything we need power distribution everything will all be in one rack. Unless you split us among different racks then we're going to have to talk and see what that looks like. That becomes a little harder. Bubba. Then there's no need for the rack kind of UPS to sort of be your prime entity. Right. So the question is about if you have house UPS that exists. Yes we can integrate with that if you want us to. Just let us know. Again that's part of the survey. Part of what we're going to be looking at. All right. The other piece of the survey that's pretty important is where those IP connections terminate in your building might not be in the same room. Right. So wherever your MPO or your DMARC point is where you bring in circuits from the outside we need to know where that is. Because in a perfect world we're bringing in four of those. If we can find four logically and physically diverse connections then we'll bring in four. And then we need to get that signaling from that location to wherever this rack is going to be that does the next N911 stuff that we have to integrate with your CPE. So all of that we have to talk through when we come to your PSAP. So you're probably going to want when we come to this survey obviously your center manager or someone who knows that piece of it probably an IT person will be involved just so that we iron out cable runs and all that and maybe somebody on the facility side who's doing things related to power and power distribution and physical space requirements in the PSAP. Those are probably the people that we'll have to engage with at every PSAP. So these IP connections that we're delivering they're used to delivering your N911 calls. So if your IT manager says that stuff's not coming in my back room then your response to them is okay I'll go tell the chief we could no longer be a PSAP. That's the conversation. Now we don't think it'll get to that but I mean that's like at the layman term that's literally what this means. So we have to find a way to make this work right. The existing N911 trunks you have coming in now those are going to stay for a long time until we get all the way through the cut over. 6 to 12 months maybe more. So eventually those will go away and we'll use exclusively these IP connections but I mean that's really what this is about. So whoever has questions or that's how you can break it down for. Because if we can't bring the IP network to you, you can't be a PSAP because we have no way to deliver a call. Yes? For the ultimate routing like for as this is our feeding back and we have a shared solution so when we have our trunks replaced will we still be able to share one another's trunks or if we have to go to their center, it goes down and we have to go to their center will that affect how our dispatchers on the floor are receiving the calls and they're logging in or is there a visit seamless to that? So the question has to do with right now the way we bring calls to your PSAP is we bring it in on trunks. And then some of you have inter-tandem transfers and other connections that you're leveraging when you want to route a call to somebody else. How will next gen impact that essentially, right? It's going to completely replace it. So today let's say you've got four trunks coming into your PSAP. You have four simultaneous calls, right? I'm going to be able to give you a hundred at one time, no problem. But the point is that limitation goes away and once the call arrives and you determine this needs to go somewhere else you can send it anywhere else. It doesn't matter. So we're going to talk through this. We've got a couple slides on it. It's called policy-based routing. And we'll talk about the conversations we need to have in order to get that dialed in. But yeah, it's way more capabilities coming. In the back. What about sending to another state? I even added. Yes, so the question is can we send calls to another state? Yes, we will have the ability to transfer to neighboring states. We know right now to the 27 million we get a year where that happens. But yes, we will build in that capability. We're already talking to Oregon, Nevada and Arizona to make sure that we've got those relationships in place. Both, yeah, obviously, bi-directional. Absolutely, yes. Okay, so the question is two-fold. What happens to PSAPs who are self-funded? That's a whole other meeting. And we'll see, okay? But the same thing applies in a phone call from this 911 network on an IP connection. We're not sure how that's going to work. So are we willing to deliver bring this connection to an unfunded PSAP? Depends. We're already talking to the military. We had a meeting with the Marine Corps. Of course, they're the most organized going first. I'm just saying. If you know my background, retired Marine. And we've already talked to Air Force and the Army and the Navy as well. So we're starting those conversations. That's the biggest piece of these. So we're engaging with them first. The other question you asked was if you have an EOC with backup and alt-answers. So, or backup center. So maybe. And when we have our CPE discussion after the break, I'll talk through that a little bit more. Okay? So, obviously a representative from each company is going to come to your PSAP. Center Gym is going to send somebody and Autos will send somebody and we'll coordinate that schedule. They're going to do some work and then they're going to have these four different IP providers that will have to come to your PSAP. Then we'll have to come test those connections. We'll have to install equipment on the end of those connections, test them and then we'll have to come back again when we go and integrate your CPE into this solution. Right? When we do that integration we'll contact your CPE vendor, whoever they are. We'll pay them to come out and do this interface. Obviously that interface will be tested and embedded in our lab long before it shows up at your PSAP. When we get this thing going and up and running, we'll probably be cutting two or three PSAPs a day. That's what we, other states have been able to do once this thing starts rolling out. And usually those cut-overs are very boring. When we cut, nothing happened. That's the idea. That's exactly what we want. So there's multiple times we're going to be in your PSAP. We will do our best to make sure this is not disruptive to your operations. But there's just no other way to get this done without that level of coordination. Which is why we're talking to you today. So if you have concerns, requirements hey, you've got to do this in order to get into my back room. We know because there's various and clets requirements this person that comes will have to be escorted. We understand that. If there's any other additional requirements you have, let us know. Any concerns let us know and we'll vet it. If you're wondering is it always going to be the same person? No. It'll be the same company representing behind that person, but it could be somebody different each time just because of the way the crews are going to be rotating going around the state. So any questions? Yes. So the question is whose responsibility is to coordinate with the CP vetter? Calla, we ask will start that conversation obviously. We will coordinate with the tech. We'll have them on site. We'll coordinate that. Your role in that is to make sure if you've done anything unique not that CHP ever does or you have a one-off or a special consideration or something that you let us know so that we don't have a gotcha when we arrive. You know that's the one thing that we would ask. But we will make that coordination and we will test with whatever CPE you've got there. We'll try and get the same version and everything to test against. But no, we will do that. If it comes to this we'll figure out what the source of the problem is and we'll just work together collaboratively to solve it. Good question. Alright, so obviously the goal is to make sure we don't disrupt your operations. Well, that's really what all this is focused about. That's why we're doing these outreach meetings, why we're talking to you today. And we know that communication between us, the vendors and what you're doing is absolutely critical. Let us know if you have any concerns about these site surveys and these initial steps in the process. As we move through the project, start to think about what do you want to see in a system monitoring display or some type of interface? What's something you wanted to see? If you're worried about e-cats, we're going to keep e-cats, you're going to have that so we're not replacing what you see through e-cats in the near future. We will be able to provide a lot more information than what you're getting today. And so we have a vision of what that system monitoring looks like and if you have some ideas share those thoughts with us. Obviously, we want to identify trouble ticket reporting and all that will be part of the training but we need feedback from you. How's that working? What functionality do you want it to have in it? How can we make it better for you? And then as we get through the deployment we need feedback from you on how it's going. Hey, this changed after cut over. We know that you, that the dispatchers are the best at just making stuff work. It's what you do. It's like, oh, this didn't work the way I thought it would but let's do this stuff and the other thing. Okay, it's working out. Tell us what it is you want to see and give us some feedback. We may be able to make it easier for you. So we're not asking you to just kind of deal with it. We really, really want your input. And along those lines one of the things we think we need your input on first is this whole idea of policy based routing. So, anybody never heard that term before? Policy based body? It literally means we can dynamically route that call anywhere. Anywhere in the state. Like I said, just for fun we can send them all to LAPD. We're not gonna. We wouldn't do that. You're limited now by the number of trucks that come into your PSAP. That limitation goes away. So we're going to need to know things like during this time of day I have four dispatchers and I want to see when those four have calls I want this action to happen when the fifth call comes in. That's what this means. And that action could be I've got a great relationship with the PD next door and so when that fifth call comes in they've got my CAD, they've got access to my radio so I want that call to go over to them and they're going to dispatch for me. We could do that dynamically. There could be an incident that comes up and you just draw a polygon on a map and in this area right here I've set up incident dispatch. Any wireless call that comes in from this incident area I want to go to that incident dispatch. We can do that. Literally, anywhere, anytime, we can send that call under any condition. But you have to help us build those conditions. So initially, yes? This system will have the ability to accommodate that. No. We can do that in order to interface with the system. But we need to know what those are. So initially we need to know this is how we want the system to behave when you first roll it out. And it's not like I had one stop I didn't tell you on day one so now I can't make a change. You could change. And so the initial how we designed this could be the same as what it works now. I have four trunks in my PSAP and when the fifth call comes in and we have all the scenarios that exist down at the local level let us know and communicate to us so we can start building the policy routing now. And then that policy routing is ultimately maintained by the prime ATOS and then shared with each region. So that no matter where that call goes in the state it's routed to your PSAP in the same policy routing through the same policy routing store that everybody is sharing. So that's the idea of this. So in this condition we can do routing. All right. So I guess I didn't have that slide up. I could see it but you couldn't. So what happens on a 10 digit transfer say a 9-1-1 call comes in and you transfer it on a 10 digit or a 7 digit transfer what happens to that call? Exactly. It's not going to have location it's going to route out to some 10 digit number so we need to know those conditions. We know there's a reason why you might be doing that today but in the new system the reason for doing that goes away. So we don't want to route 9-1-1 calls to 10 digit lines. There's no sense in doing all this work to get this really rich robust packet built with all this good information in it and then rout it over to a phone that can't accept it. So any 10 digit, 7 digit transfers you have and that kind of stuff we want to talk through those so we can see how we can accommodate them in the policy routing. Right? And then how will all the answer work? So you all have a chicken switch in your back room somewhere everybody has one. So you know when you're bugging out and you want the calls to go somewhere else and hit the switch over to the other piece or not, I've ever used that or it might be programmed for an agency that you don't work with all the time and you might want to change that you may want to do it in different scenarios it might be under this condition when I go all to answer I want it to go there but under this condition I want it to go there we can do that with the system and you will physically have a switch we think that's important because whatever you're trained to now we don't want to change it'll just really be just a like a figurative it'll have IP and dynamic capability on the backside but the interface will be the same to you so think through all to answer who's your alternate answer where do I want these calls to go there are no limitations on county boundaries or wait they're in a different region none of that matters oh they're on a different selective router that doesn't matter either you can validate any all to answer scenario that you need we just need you to communicate that to us yes yes yep you can have multiple all to answer scenarios for the same jurisdictions no problem we just need to know what those are any other questions on that so moving forward our role is to make sure that obviously the vendors we've selected are delivering the service needed we're going to have a conduit between you and them to make sure that this is rolling out properly we have several things in place to do this obviously we need your feedback I'm going to talk about a couple of the mechanisms we've already put in place obviously these meetings are a big part of that we'll continue to work with the 911 advisory board the long range planning committee and the regional task force that we've got set up to help facilitate the conversations that have to go on we'll establish best practices policies, procedures, all of that and we'll define it in our operations manual just like we do today we'll manage the relationship between the region and the prime vendors and we'll coordinate GIS data I've got a couple slides on GIS here after the break that we'll go through and we're obviously going to do our take every effort to align what we're doing in California with some of the best practices that we've heard from other states so anyone who's deploying next to a 911 we are talking to them we're talking to Nina the national emergency number association we're involved obviously with the local app code chapters and anyone else who's active in this space to try and learn here's what works best or here's something you might want to think about before you roll this out so that's the role we're playing but you guys have a big part in this so what we've done is we've set up these regional task force how many regional task force members do we have in the room there's a couple 1, 2, 3 and so we know down here at the PSAP level you're busy maybe due to staffing and other things you just can't participate all the time in these meetings so we set up these regional task force where you have a representative that can bring your concerns to Cal OES and they have a direct path to our advisory board because if we're the source of the problem and we're not willing to change so that's really what this is all about and these groups are really focused on building these relationships and the coordination that needs to happen between you guys and us in order to make this solution a reality we need your input on what's going on in the region and statewide because we know the technology but there's some operational impacts that we just might not have the insight of so we need your feedback and what we've done is we've set up these regional task force they meet quarterly throughout the state and if you want to know who's on your task force this is a list of the task force members so you'll see in the north region up there in the upper left those are the folks that are on that committee the next northern region task force meeting is November 5th so if you're interested in participating contact Andrew and he will link you up with whatever region that you're interested in and there's no commitment if you want to come to one and say okay I'm good they've got my interest I'm fine that works but if you want to become a member or come more frequently then like I said Andrew can get you on the meeting schedule he'll let you know where those meeting locations are and you can begin to be part of this process alright any questions on regional task force alright so we're up to the break we'll take 15 minutes but before we do are there any other questions about next gen because when we come back we're going to transition to these other topics text alert and warning location accuracy CPE that kind of stuff so any questions yes so the question was what background have the employees for the companies been through we can't do a background check on them for you because of sieges and cluts requirements you'd have to do that so even if we did that we wouldn't be able to now we've asked them please don't bring convicted felons into the back room we've had that conversation so they know and they've communicated with the subcontractors that they're using to do this work you're coming into a police department there's rules and regulations and requirements so they know all of those baseline requirements yeah okay so we'll take 15 minutes I've got 110 so we'll be back at one was that 125 let's move on to the next topic everyone take their seats please we're going to get going so this next part has been taken about an hour depending on questions so that if you're wondering about can I make it to the end hang in about an hour we'll be done alright hey Andrew you want to get them in from the hallway okay let's quickly get through text to 911 before they get back it'll be easier for all of us alright so a lot of excitement a lot of questions obviously if you don't get a chance to ask your question today send it to us there'll be more opportunities to engage with us on what we're doing so the next topic I want to talk about is text to 911 so some of you how many of you are taking text right now you're already taking text okay anybody not can we call you out okay well this this law just passed and so if you were wondering am I going to take text yes you are and this law clarified that so AB 1168 essentially says that by January 1st 2021 every PSAP and it's pretty specific every PSAP we'll take text to 911 so we're the good news is next to 911 is the platform that's going to facilitate text to 911 delivery to your PSAP and ATOS is the one that's going to be coordinating that statewide they're working with a subcontractor agent 511 you see them up on the slide so how's this going to work we have text today we will transition you from either West or Comtec one of the two text control centers right now so if you have integrated you're using West and if you have over the top you're using Comtec so we will transition you from those two TCCs over to this new delivery platform through agent 511 that's going to leverage the next to 911 system and the new IP connection to deliver that into your PSAP and so in a perfect world like we say on the bottom of this slide current PSAPs that are currently accepting text will be transitioned first and whatever delivery method that you have today we will facilitate that during the transition okay what could possibly go wrong we've got between now and January 1st 2021 so there are some conversations and contracts and agreements that have to be signed between autos and each of those two TCCs so West and Comtec and those conversations have begun and so far we don't see any gotchas but we're early in on the conversations remember we're about 30 days in the contract signing if anything goes sideways and for some reason we can't comply with the law which if we see anything that jeopardizes the schedule that says there's going to be a slip and we can't meet the requirements under the law then we may need to regroup and figure a faster deployment method out and whatever barriers in the way we'll have to find a way through it the fastest deployment method is a web over the top solution it's just the fastest method so at some point in the process March or April or something of 2020 we may say okay the projects are in jeopardy we may not meet the requirements of the law we have to pivot and you can't do integrated you can only do over the top and it'll be delivered through agent 511 across an IP trunk that we bring to your PSAP that might be what we have to do that's not our intent not where we want to go but we can't change the fact that we've got to have everybody on board by the deadline required in the law we will know more over the next couple of months as we start to begin those vendor negotiations between Autos and Comtec and West as soon as we have anything definitive we'll communicate that back out with you including our transition plan and what that's going to look like so questions concerns so the question is if you don't have text to 911 today should you continue the process of working with us yes and continue to work with Cherise on my team and she'll keep you up to date on everything that's going on absolutely we don't want to slow down the progress we're making because ultimately we still need to integrate with those two CCCs to deliver that text and get it into your PSAP so yes continue to work directly with them yes the question is does it matter after we get this fully deployed if your neighbors on a different TCC no Autos working with Agent 511 will directly connect with both TCCs and so some of those limitations that exist now like if you receive the call from one you receive the text from one TCC and you're integrated and you want to transfer it to the other TCC whose web you can't do that today the new solution will solve that problem yep so it won't matter what TCC alright other questions on text okay Cherise will be shocked alright so next alert and warning we've had a lot of interaction on this as we've gone out to the town halls we took a look at alert and warning what was going on in California some of the challenges and opportunities and capabilities and we went to the FCC and we said look can we spend 9-1-1 funds on alert and warning and they said yes just reverse 9-1-1 uses the same technology no problem so then we went to the legislature and to the Department of Finance and we asked can we get the statutory authority to fund this system and they said yes and then we had to change the revenue and tax code and we were able to do that through SB 96 this past year and then we went to our vendor partners that were bidding on the contract and we said if we include alert and warning with next gen 9-1-1 can you support it and they said yes so after all those very simple steps here we are with an integrated alert and warning solution statewide and ATOS has selected Everbridge as a partner and Everbridge solution statewide so those of you that are using Nixle or Code Red or Everbridge or some other solution there's no requirement to use this system we want to make that clear but what we've built into this is the capabilities to take every advantage of what Everbridge can bring to this solution so it will be integrated with iPause but remember iPause, EAS, WEA all those require authority to get the certification to use that so even though the system is capable of doing it there's steps you have to do at the local level in order to get certified and trained in order to send out an iPause message so that requirement still stays it will be fully integrated with earthquake early warning that Cal OES is deploying so we built that into the solution and we're going to leverage everything that's available in the 9-1-1 system so for those of you who have alert morning today you probably have to do a refresh of all the phone numbers and addresses, the landlines that goes away because we will always have the most current list of phone numbers and addresses in the 9-1-1 system so that eliminates that step it's going to leverage the delivery platform and the IP connections that we have coming into your PSAP which is good news for you it will help us as we meet the requirements under SB 833 which required Cal OES to develop best practices and provide training for alert mornings so much easier to train to a common technology platform than to 5, 10, 20 different disparate systems that are out there so it's also going to be able to support the ability for you if you have an existing system to import your local data so if you've got emails and cell phones and all those it will import that keep in mind since cell phones move around unless you self register there's really no way to send a local alert when I send an iPause or a Wea there's very specific rules by FEMA of when you can send a Wea wireless emergency alert and there are local conditions that don't meet that criteria sometimes when you want to send a local message to cell phone users so we will provide the ability to import all that local alerting that you have even local alerting within your agency and all those detailed phone trees that you have existing will incorporate into the system and this is delivered at no cost to local agencies so any questions before I go on yes yes so the question was if you have Everbridge today will the new system support all that functionality yes but we want to make sure you tell us what Everbridge is doing for you now so that we can work with Everbridge to ensure that we've included in the solution what you're doing locally and we've had some feedback already and I've pushed that up to Phil with Autos who's helping to coordinate this but yes that's the intent so the question was will cell phone users register with Cal OES or with the local agency we will see there will be the ability to self register how we coordinate that is yet to be determined we're still in the initial well we're well into the conversations between Autos and Everbridge to define those requirements it seems to make sense that since you are the local authority and the local alerting authority you should probably maintain that list I don't need to validate anything I'm just providing the technology solution so it seems like that's probably the best way to do it because local you maintain that authority which is something I have on the next one anything we're doing that third of the bottom bullet there does not supersede your local alerting authority or that's not what this is this is a common delivery platform only yes so Everbridge there's a bunch of different functionalities social media integration you know weather alerts and stuff that are optional add-on that some jurisdictions may have now some jurisdictions may not have so the current setup there's different ways to set it up there's a lot of different things out there so what's the best way for local jurisdictions to communicate what their current setups are requirements are and how they are used in the system so the question is Everbridge has the capability to support a whole bunch of additional features add-ons and capabilities how do you make sure that what you've purchased locally and are using can be built into the statewide system tell us your needs we'll push that to Autos who will talk to Everbridge to see if we can build that into the system statewide we will make every effort to accommodate all of that but we'll find out what those capabilities are once we see the list and we haven't gotten the list yet whoever is an alerting authority and using Everbridge if you want to send that to let's see probably Ann sorry Ann I think this is a prime project manager thing you're it so send it to Ann send those requests to Ann obviously if you send them through your PSAP advisor if you already know who they are and you don't want to worry about getting Ann's email send it to them and she'll get it to Ann but send it to us we will coordinate that data and send it to Phil and Phil is actually the project manager over this part of the solution and him and I have already been talking and this is not the first set of questions we've had related to this as I said I've been requested by my son to leave this effort he's a firefighter paramedic for his film and they use Everbridge all the time and he's like dad you're going to fix all the issues we have today so it's not the bud it's my son that's saying Daniel you're going to fix it so we've already had outreach from Placer Yolo and Sacramento County tons of emails flying back and forth already on it so please go through Ann and she will put you up with me you can grab a part from me afterwards if you'd like but certainly the questions of so we have those add-on features I would love to just comment that everything is included but yeah we'll get to the details of some of these add-on packages that they have and see exactly what they are so coordinate with us and give it to them some of the things we've asked for are on this slide which we think are really important so one of the challenges right now with iPaws is you can only give alerting authority down to the county level because at the federal level they don't know of anything more granular in shape file than a county so what that means is Roseville I know you're in the room you could have the alerting authority to send it to all of Placer County but Placer County would probably only want you to be able to alert City of Roseville we can solve that because we're going to have PSAP boundaries and so we could do that level of check to make sure that okay you are an alerting authority been through the training and are authorized to do this and the message and alert you're sending out correlates to the boundary file for your jurisdiction so we can add that level of let layer into this solution the other thing we can do is when there's an alert and warning sent out I mean let's say we issued an alert and warning for Auburn where do you think they're going they're just going to come down 80 and they'll be here in a minute right I mean if they evacuate that's the direction they're coming so this will provide the awareness to know that a neighboring jurisdiction has sent out an alert and warning some capability that may not exist today so that's another thing we've asked about yes so currently we have the capability of doing an alert and warning the county does it for us so will this give us the capability to do it within our city jurisdiction yes this will so the question was right now they don't have alerting authority but the county does yes but remember if you wanted to send out an iPaws alert you as an agency still need to get certified before you could do that so local alerting features this would support your ability to do that so there are certain requirements for the reason to send the alert to justify an iPaws right so you can't send an iPaws alert for I don't know you couldn't send it for some local event going what's that yeah for like a red flag a red flag warning you can't use iPaws right but if there was an evacuation you could use iPaws that kind of stuff and there's a bunch and the training has you know lots more detail than that but there's just certain things that you might want to alert locally that don't propagate up to the level that FEMA has said you can use this system for that's probably the big difference alright so obviously we're not trying to supersede any of the local alerting authority so we have to figure out a way to solve that process and that's some of the things we're working with ATOS on and it mitigates the problem of all these disparate systems out there and we want to make sure it's clear this is at no cost to you I will mention this though if you're using grant funding like EMPG or something else to fund your local system once this is 100% up and running vetted functioning working probably going to need to take a close look because if the state is providing a service and a technology capability might be challenging to then ask the state for grants to support something locally when we're already providing it to you for free so those of you who are engaged in this space we want to work with you over the next we think it's probably going to be 18 to 24 months to get the solution fully deployed and then at that point you know we think with systems fully up and running and meets all those needs it's at that point that that grant funding goes not much sense to do with two systems any other questions on that yes right so the question was never bridged today to say notify employees that there's overtime available or any other kind of employee notifications this system would support that as well absolutely we were very clear in the functional requirements there absolutely alright GIS the next easy topic to get through okay so we have a GIS task force and they meet periodically and talk through this in a ton of detail so for this crowd I just want to let you know where we are today and what we're doing so we hired this company called DDTI digital data technologies incorporated they're based out of Ohio to come in and take our Annie Alley data our Emsag data road center lines that we could pull from locals and address points we got about 80% that sent in their data and they took all that data together and combined it together with a commercially available data set called tiger data it's the census data which is the most valid publicly available data set we could get that really exists out there we took all that together and we're running it through a process in order to develop the GIS data set that we need to route a 911 call this is not the GIS data set we need to dispatch somebody this is completely different although related so I'll walk you through how this works in today's world when you call 911 from a landline it goes out to the Annie Alley database and then says okay this telephone number equates to this emergency services number which means this call needs to be routed to that PSAP and the selective router is hardwired to send the call to that PSAP that's how it works today in the new world the way this is going to work is that address has been validated to be inside the shape file for your PSAP so when that call comes in it turns into a lot long compares it to the shape file says that goes to this PSAP builds the header of the SIP packet says it goes to that location and sends the call to the PSAP how many county coordinators do we have in here a few of you oh wow really good so for county coordinators that's essentially what this new process looks like where today you get an address that comes in and you make sure it's msec valid it's in the valid set of address ranges the company that autos is working with is called geocom and they're going to establish a process and training so that you can do just that new address comes in it will plot to a lot long you'll see that lot long shows up in this shape file that shape file is in fact the PSAP it's supposed to go to and now the 911 system would be we'll be able to function as it's supposed keep in mind that the current anialy system today costs about 20 million dollars a year to do relatively little and I say relatively little because it's only there for non-wireless calls 80% of your calls are wireless so while it uses parts of that system deliver that wireless call it's really focused on wireline and voiceover IP so we need to take those addresses get them into this new space so we can turn off anialy and msag replace it with this new system so that we can continue to route 911 calls then we take that money we've saved and we're rolling into the project that everybody really wants to do which is a coordinated statewide GIS addressing space that we can get to do all the other things we want to do in GIS if we try to get to that step today like we try to get from where we are with GIS today all the way to that coordinated GIS validated address valid wonderful dataset we all want it would be 2050 before we finish that effort literally so we will get there this is step one we know that there are many things that we need to interact with you on for this GIS dataset so what we've done is we've replaced the old GIS funding model so how many of you are taking wireless calls everybody's hand goes up the purpose of the previous GIS funding model we had out there was so you could take wireless calls it was one time funding it was in place for 17 years anybody who contacted me and said we didn't get a chance to use our GIS funding for wireless calls that was 17 years 17 years I mean that's a pretty slow moving boat when it was going by the dock 17 years and so we I mean we know there were a few that didn't get to use it but it's gone and this is the new one right here so what we've done is we looked at really PSAPs and number of positions and all that is not the important factor when we're calculating this new GIS model really has to do with any address points do you have in your account so we took a look at the number of address points that are in California which is a publicly available number because I needed a budget for this I need to go to Pat my boss is in the back I think I've been doing pretty good so far he hasn't thrown anything at me so we needed to be able to budget for this so we took the number of address points and if you calculated out at 44 cents an address point that's the statutory amount that I can spend on this project this year so if you're a county with multiple cities in that county and you have those address points that you maintain then we want you to work with the cities to validate those addresses and the number of address points don't change so say there's a city say Roseville you want to do your own addressing which you probably do you would work with Placer County who's got this allocation of 44 cents for the entire county and then you get a portion of those addresses that you're responsible for and then we would direct reimburse you for any time to do this work that's needed for GIS so that's how the funding policy is set up Andrew do you remember the number of address points or well Natasha do you remember total number of address points in California I don't remember it was in the millions I don't remember the number but I have it I just don't know where I've got 14 million is that right I don't know there you go so I think it was like 14 and a half million or something is the number that comes to mind so that's how we came up with the funding policy this is the first version of it we have a GIS task force how many are on the task force in the room one two so there's a couple that are on that task force we'll relook at this funding policy for next year we'll start in July of 2020 and we may find that that 44 cents number needs to go up or down or get adjusted based on the level of effort that's required so what can you get reimbursed these are the activities that we'll support through this funding model road center lines address points and peace at boundary and that's to reimburse the time you need to do at the local level in order to support this or if you want to go out and get a subcontractor or a contractor to help you at that work we would be able to direct pay them direct pay them provided they're on CMASS which is the state contract but if you do work with a contractor make sure you talk with us because we want to make sure your statement of work includes only things we'll support so you don't get left holding the bill for something that's not on this list so the data set that DDTI is building will be transitioned in December and January over to geocom and then autos working with geocom will maintain that data set and then they're working with another company called 9-1-1 Data Master which will build a LDB a location database which is essentially like an alley but in the next gen 9-1-1 world so that's what we're doing with GIS so questions yeah so your the question was will a local GIS analyst be involved in this probably so one of the challenges we're coming up with is when we got the address points and we run them through our system remember we're focusing on it to make sure is it a valid address point and does it have what we need to be able to route the 9-1-1 call when we find an error or we find a change we would like to push that back to your local analyst to make that correction that's what this project is focused on but if you don't make the change we still will we are still going to correct the data so we can route 9-1-1 calls correctly but at some point we want this data set to align with what you have locally and we know those workflows are going to take time to work out because as a PSAP you may not have authority to make changes to the GIS that could be the city manager or the police chief or someone at the county level or somebody in another county department that you have to coordinate with and so those are the workflows long term we need to work out with this process so there was a question here so the question was how do we handle non address locations like the highway so we'll have a PSAP boundary file for the highway and so when a mobile call comes in that boundary it will route to CHP most if there's any other address that's on a highway that shouldn't go to CHP we would need to know about that to be able to program it into the system yes so the question is two fold for a state highway that has a boundary let's say you live on a state highway your address is the state highway because that's your landline address but when you call 9-1-1 CHP is not the one that would respond to your sheriff or something like that yes we will accommodate that in the routing policy to be able to do that properly even if the address point physically falls in a CHP boundary but we know it's a wire line call it's very easy to make the policy routing update to say that call goes to the sheriff or to the PSAP same thing applies for the capital if there are wireless calls that are generated from inside the capital and you want those CHP and not Sacramento PD that can be built into the system as well absolutely so don't think that if this is not all 100% figured out on day one that the call is lost there's always a default routing policy to get this call to a PSAP and that's part of that policy routing discussion that we need to have every county might be a little different in some counties it might be to figure out where to send this call then it goes to the SO others may say if this call needs a default route it's CHP others might be if you need a default route it's that PD we can build all that into the system so no matter what the call will get to the right place and here's the good news we will have the analytics to figure out where the call should have been and we will be able to correct the policy routing so that it doesn't happen again so that it goes to the right PSAP and there was one other question back here what if like for problems like calls that are routed wrong or like how do you think that like right now on the inside file you're thinking about the corrections and how's that going to come in so the question is how do we make corrections there will be an interface that's developed by GEOCOM we will train the county coordinators on how to work with that interface to make those corrections to the routing we'll also have a feedback mechanism that will go that way because this system will say look this call arrived here what was transferred there why are we transferring this let's send it to that PSAP so the system will say this is the recommended destination for that call reach back out to you do you agree do you agree that this call should not go here it should go there and then we can update the policy routing for that all those are built into this process that we're talking about absolutely the PSAPs are going to be involved in that just like today the way we do our wireless routing project for those that don't know we go through the state there's roughly 400,000 cell sectors in the state of California and we take a look at where that call gets routed and then if it's transferred above a certain rate from one cell sector to another then we work with CHP in the local PSAP to make sure it routes same kind of process will be built into this yep yes be exactly the same the 512 bytes that spill in your Annie Ellie spill from CPE to CAD will be exactly the same in the new system with the exception it will be more accurate exactly yep all that will still be in there in the back so the question is what about elevation we have begun to talk about Z axis and how we can incorporate it if we receive it we can deliver it but again we're limited to that 512 bytes in the Annie Ellie spill and some other challenges we have there so the system the NG911 system can handle it probably the bigger conversation is how do we deliver that data to PSAP in a way that you can ingest it so that's a follow on discussion okay there was another question so the question is can we change the 512 Annie Ellie spill we want more data because you want more data yes we can but we're going to make a lot of people mad so that's part of the conversation we're starting to have right now we have this limitation we get all this rich data so I'm going to talk about that in the next few slides so hold that thought we'll get to there yes so the question is what kind of accuracies do you mean with wireless yeah with wireless yep so let me answer that question in about 5 slides on accuracy or 6 because we'll talk about the rapid deploy project and some of the work we're doing there on location accuracy alright so other updates we've made in addition to the GIS funding model we made an update and we've increased your training allotment from $3,000 per PSAP per year to $10,000 per PSAP for you we know there's a lot of technology coming and we want to support the training that you need in order to meet this kind of here's what's coming so that went into effect in July so it'll be $10,000 per fiscal year per PSAP this supports training like NENA training APCO training, POST training and any other 911 training that you coordinate with our office so reach out to Paul Troxel on my team who will work with you so if you come up with some 911 training and you want to get it pre-approved it's got to be pre-approved and it's not NENA APCO or POST then we may still be able to authorize it depending on what that training is it's got to be 911 training so you can't do like bake sale training or yeah that's important I know we have to be really careful what we fund here we've also updated the approved list of authorized use of residual funds so take a look at that updated list to see what's on it and the idea is that we're trying to identify those critical elements you need in PSAP in order to support 911 so look at our residual funding list we want feedback on this yesterday at the long range planning committee on what should be on that residual funding list alright so we've added back in furniture if you're wondering what the big change was so but there may be other things that should be on that list we want to know about that right so take a look at what's on there and if there's something you need to support your PSAP for 911 calls let us know the last one is just a reminder this project's getting a lot of visibility so the legislature's watching some of you probably saw the announcement recently where Governor Newsom went to San Francisco to the PSAP there not sure how long it's been where a governor actually went into a PSAP but I think it's been a little while so one of the things that they've started to ask us at the 911 branch is hey what are the call answer times for this PSAP because once they start looking at the 911 system they want data when they ask me for that data I have to give it to them there's a public record act the data's available I have to provide it for them so just a heads up make sure you're really looking closely at what you're doing operationally because the spokes might start coming around asking questions about the possibility alright let's talk about technology and we'll finish up on this topic really I think I've got about six or seven more slides so there's a lot of technology that you have in your PSAP and we're going to talk about some of the trends we are seeing and where we see the path forward and then we want to get your reaction right now about 50% of the calls that come into your PSAP your location is just not good or not at all in some cases we know that we know that this 512 bytes of data that goes between CPE and CAD is a huge limiting factor we're going to have to find a way to break through that barrier in the near future we also know that there's a lack of ability to integrate new technology we get a really good idea and we come to the PSAP and we say no you can't unless we do a forklift upgrade or some other type of infrastructure overhaul in order to integrate that new technology there's a slow deployment and refresh cycle every five to seven years we buy new equipment and if you want something outside of that cycle that requires new equipment we just have to wait this is basically what we have to do which is a huge problem lack of reliability we're seeing even most of your CPE on average statewide is only three nines reliability so what that means is the standard is five nines which is about six seconds of downtime per month we're seeing 10,000 hours of downtime per month the three nines that's the difference there's just orders of magnitude difference in reliability and we want to increase that we want to make your systems available we want to be able to integrate these new technologies from the emergency management space and then the 9-1-1 space and there's limited security so or no security most of you your security is a moat that's around your PSAP so in the 1300s that was pretty cool not so much anymore this is a lot different big difference of what security requirements we need today there are probably some in this room who have probably had a T-DOS or ransomware attack in the last year I won't ask you to raise your hand because that's kind of scary but we actually want to do real security like to secure these systems the way that they should be so we started thinking through this and we asked ourselves how do we get there cloud is probably where we're headed not probably it is where we're headed alright and it's actually here of the four vendors that we selected for this project for next in 9-1-1 one of them has a 100% cloud solution NGA 9-1 and we know that ATOS has cloud as part of their delivery and CenturyLink has cloud as part of their delivery and Synergym is working on cloud as well this is where we're headed and for those of you who are thinking ah cloud are you out of your mind how many of you have used your mobile phone to access your bank account so it's okay for that right so clearly there's a way to get it right there's a right way to do cloud computing and we in 9-1-1 I think we really have a choice we can sit back and wait and see what industry is going to deliver for us as they tell us what they think is best or we can say you know what we're going to embrace this let's figure out the functional requirements we need from a 9-1-1 community from a public safety community and let's drive industry to give us the solution we want so that's the role we're taking for the reasons that you see up here on this slide we want to get out of this technology refresh cycle that limits our ability to really deliver the services that we need to in the PSAP so that's really where we're headed so what does that mean well there's some things that are important when you consider cloud based technology you want to make sure that you're using a bona fide cloud provider and not just Bill and Ted with two servers in their garage right I mean you just so these are some of the things to look for so if you're trying to get into this technology and you're in the IT field and your decision maker here this is the things we looked at as we start to think about cloud based solutions first of all FedRAMP certified so this is a way to validate that this is a true cloud provider so services like Amazon Web Service Microsoft Azure Cloud Google Cloud those cloud providers like that have FedRAMP certified so that's the first step that means that the platform can support the reliability you need in 911 you also want to make sure that whoever you're working with as a vendor has a cloud engineer who actually understands this stuff because it'll be up to that provider to interface with this FedRAMP solution in order to deliver what you need you want to make sure that it's high availability the way you do that there's a thing called an instance so you can think of you know that rack of equipment you've got in your back room that's the instance you have multiple of those in the cloud active at the same time both capable of carrying 100% of the load that's impacted in one it doesn't affect the other and you still continue to get your service and it's got to be dedicated space for your solution right so that's really what this is all about and that's what we're focused on with this solution you've also got to have secure network connections in place because now your connection to the cloud becomes absolutely critical which is why we're going to bring six different connections into your PSAP where possible that's how we get to this level of reliability and it's got to be dedicated and secure so you want a private closed network that meets the solution you're deploying and it's got to be secure it's got to follow all of the security requirements that are out there and it's kind of a difficult space to wander through so the IT people that are in the room can you say is there a definitive security requirement that I've met this I've done everything now there's a whole bunch of different sources there's some guidelines and tools and stuff that are out there but you've got to be able to be following those in order to make sure that this is compliant so what are we going to do with this like I said we're already using this for next day at 911 I'm going to talk about another project but the next thing we see coming is CPE we want to move CPE from on-prem into the cloud or a data center model right so we're going to move to this evergreen type solution so that it's always available always updated meets the current standards and can integrate any technology so we're working on an RFP right now we'll release it in the winter it's probably November December timeframe we'll release a draft or a pre-solicitation we call it it will be the full RFP and we want you guys to give us some feedback okay there's going to be a couple of unique features with it one of them is we're moving away from this per position cost model right now it's everything's per position right so when you come to me and you say hey budge I want a couple more positions for training I say no I need a couple more positions for a backup center no the reason is I pay per position we have roughly 3,000 positions in California so if I told everybody yes to backup those 3,000 positions turn into 5,000 positions and I break the budget and I can't afford to support the system that's why we tell you no today we want to go to a model where I price it based on your call volume you all know your call volumes we've known them for a decade or more and they don't change very much so we want to establish these tiers that says from like 0 to 1200 calls it's this cost because that's how big the instance needs to be in the cloud to support your needs at peace out so it's a fundamental shift yes coming from the center that roughly 40% of our call in came on 10 digit because of the all the medical warm companies, fire warm companies how is this going to translate into that because these are still calls that we have to process so the question is how do we accommodate in this model your incoming 10 digit calls that are actually 9 on 1 calls that's good feedback so we'll figure out a way to count those but don't try and plus up your numbers by a bunch of 10 digit stuff that's not really 9 on 1 to get a bigger pot of money so I'm going to have to find the balance there but that's a good point if there's something coming into the system that is a 9 on 1 call we want to accommodate that remember we're going to establish ranges and it's quite unlikely that you have enough to bump you to the next range if those numbers come out in the winter take a look and give us some feedback on it and that's this next bullet really we want your input on this when we post this we want you to tell us what you think and focus in on it from a functional requirement so don't tell me I need 6 buttons and I want that one yellow and I want that one blue that's not the kind of feedback we need I need programmable buttons that helps me that kind of feedback really helps to make sure that this contract that we eventually put in place meets your needs our goal is to have the contract in place in the summer of 2020 will extend the current CPE contract probably a year to give us a little overlap where both contracts are there and then at some point once this is in place, embedded in everything this will be the path forward and then we will take and that's what we'll pay for your positions for right so that's a one time it's not tied to the maintenance of the system so that's the vision, yes I'm looking at this in terms of like a money thing for the center so will there be any way that the manager could look and see like well how much would I get if I decided to do the current position while you're still doing it while you're looking at transitioning to the hall volume is there going to be which one you will right so the question is is there a way to look at what the funding model is going to look like in this new scenario with a cloud based or data center CPE versus the on-prem that we have now yes you will be able to see that but remember we cost that based on that master services agreement so the per position cost actually based on the responses that come back to us so I think it might actually went down this last year by a little bit because the price of the systems that we negotiated were cheaper in the new model though probably the bigger question along funding is what do you do about those reoccurring costs that come up because this will be an evergreen solution which goes back to that please help me have a conversation on these incidentals that you want me to that I need to fund in PSAP so we can develop a regular routine for that as well I don't know logging recorders or whatever the 9-1-1 piece of equipment is that won't be part of this that still needs to be funded at the PSAP headsets the thin client interface that's receiving the 9-1-1 call we need a regular equipment cycle refresh cycle on those that will be part of this new funding model as well we've already begun talking to the long-range planning committee which is part of the 9-1 advisory board on this and we'd like to get some input from you and again all that you'll see that in the full RFP that's released yes so the question is what do we do if I'm ordering in the process right now of ordering equipment depending on where you are in your existing maintenance how happy you are with the solution you are negotiating right now would probably answer that question and more than likely probably makes sense for you to keep going but talk to us and we'll see we'll have a one-on-one conversation to figure that out probably the bigger question for planning is what do I do if I'm in year 4 right now which means next year I would come up definitely going to want to take a look at this new model because we're probably going to be able to deliver more services to you than what's currently available on the contract alright and this is what started this conversation really was this next project I'm going to talk about we needed a way to display in PSAP this location information that's being sent by Google and Apple or Android devices and Apple devices through a clearing house that's managed by RapidSOS so you could see this device-based data right so we went looking for a company that could deploy a solution well first we started and said we'd love to integrate this with all the equipment you've got at your PSAP nobody could integrate or very few could integrate it maybe 10% could integrate so we had to figure out a way to deliver this into every single PSAP so we went looking for a company that could do that for us that's when we found RapidDeploy so RapidDeploy was selected to bring this location accuracy project into every PSAP so how many have RapidDeploy in your PSAP today alright what are your thoughts give us some feedback good what do you like about it alright so that's the feedback we've heard you can tell exactly where somebody is on every single 911 call every single wireless 911 call which is 80% of your call by that's so I'll show you a graphic on that in a second but essentially with this RapidDeploy solution it automatically rebits and plots the breadcrumb trail as the caller's moving so I wanted to give you feedback before I introduce somebody from RapidDeploy who's actually here so you could feel free to say whatever you want so Samantha do you want to introduce yourself hello everyone we have a location accuracy and validation project so right now we've installed in PSAPs Kurt from CaloES who's the project manager on the CaloES side he's sent out a project package for you all to sign so far we've received 168 back as part of our next deployment phase I sent out 168 emails yesterday to all of those PSAPs so if you have signed your project packages you cannot get an email from me please find me after and we'll touch base and connect and figure out why you didn't get that email but I'm really excited about this project and moving ahead with the next phase alright so thank you so I'm going to show you kind of what the interface looks like so if you can look up on the screen here when that wireless call comes in that big blue circle you see there or maybe triple the size of it in other cases would be phase one what comes into the piece out essentially you know there's a caller somewhere it's not very helpful and then if you do a re-bid in a best case scenario you get that smaller blue circle you see like I said I can't point but anyway the smaller blue circle and then if you look close you might be able to see a little small red circle around that number two that's on the screen that's what it's going to look like for the call that comes through from the Rapid SOS Clearinghouse into this display that you see here and the next graphic kind of shows the breadcrumbs we were talking about so when the initial call comes in it's that number 11 you see up there that would be the wireless Annie Alley spill that's coming and then as the caller moves you actually get a bread trail crumb a real time of where that caller is so when we deployed this in Roseville we did a call there was somebody in a vehicle and the phase two came in and then they drove two miles and literally okay I'm crossing this street and you'd look and boop the pin drop would drop exactly where they were as they were moving we even did an Annie Alley re-bid in the middle and it didn't change and it still plotted them back at their original location two miles away and many of you have probably seen that challenge with the existing system so this is what this project is all about there are a couple of challenges like I said if you have CAD that can integrate this directly we'll do that we absolutely will most of you probably don't probably none of you do so we will bring in I'll walk through kind of at a high level what it looks like but this is some feedback we got from Kings County should we read through this story essentially what happens driver crashes goes into a ditch cars filling up with water pre-diabetic not sure where they are can't provide their location of course phase two can't exactly locate a car off a ditch not visible from the road so through the rapid deploy data they were able to pinpoint within five meters where that car was and dispatch resources and save this guy's life this is the kind of data that's coming through and these kind of success stories we're hearing statewide so how do we get there how does this get into your PSAP if you're one of the not one of the 48 that already has it so what we will do we will connect up a Y connector working with your CPE vendor to your CPE so it takes that anti alley spill that's going into CAD and plugs it into this edge device that rapid deploy will supply the edge device will be installed by an AT&T technician at all PSAPs right and then Cal OES will come and install a cradle point router to bring that secure connection up to the Azure cloud the purpose of that is we're getting any alley from your PSAP into this Azure cloud solution alright that cradle point router we will come into your back room and do a test and whatever signal strength is the best that's what we will use right so we'll test T-Mobile FirstNet and Verizon whoever has the best throughput that's the one we're going to use some of you your back room is a concrete bunker buried three stories underground when we find those situations we may need an antenna and so we'll talk to you about what that looks like and how we do an antenna the goal is to avoid that though we know touch and infrastructure at the PSAP can get tough and then the other thing we're doing for this secure connection is we're working with Comcast they've already completed install at two locations or four and they've done surveys at over a hundred I think almost okay so eventually there will be another connection at PSAP to support this alright not just LTE once it goes up into the cloud that's where you have access to the data it's a Chrome browser interface where you have this mapping analytics tool that displays those graphics that I showed you in addition to other information that's available other information that might be available from RapidSOS which is the company that manages the clearinghouse or from RapidDeploy and that RapidDeploy can bring things like live traffic whether other and other feeds if there's something you want to integrate into your map talk to them and they'll see if there's an API that they can support in order to bring that data into the map we leave that up to you our focus is on getting the location and then what we're doing in addition to this this is a big part of this project we're trying to overcome the limitation that a cell sector has to be sent to only one PSAP we talked about that earlier so I'm trying to validate this location that's coming from the device so we can actually route on that location alright then I can get the call to the right PSAP every single time which is the goal so we've got some analytics that we're running in the back which is why we need that device installed in every PSAP even if you're going to integrate it or even if you don't want to use the RapidDeploy mapping solution so that's what we're doing in the background we're running some analytics and what we're seeing is roughly 80% of the wireless calls that come in have this RapidSOS data and in general it arrives faster and is much more accurate so that's the project so as Samantha said any questions before I go on with the deployment strategy yes I just want to make sure you just said last so eventually then your graduate school is to use the RapidSOS data to determine which PSAP throughout the calls do instead of the current wireless data that we're using so the question is how are we going to route calls in the next N911 environment yes so we've talked at the FCC and there's no regulatory restrictions from doing that we have to work with RapidSOS and Google and Apple to make sure that there's no contractual limitations we're in those conversations now but before we get there we want to make sure we vet the data and validate it that it's worth routing on other than just obviously what we're already seeing in the interface we want to actually do some testing for a couple months and then yes that would be the intent yeah we hope we can get there yes Alicia I think there's one more over here how are you validating that the data that you're receiving from RapidDeploy is so the question was how are you validating the data from RapidDeploy is the correct dispatchable location we're not nor will we ever because dispatchable location is ridiculous I can tell you the location of the N911 is way smaller which is way different than the dispatchable location we want to make that very clear if I'm driving down the freeway and I call N911 the dispatchable location is not my car but that's a really important distinction because there's a lot out there that are confused on this topic the dispatchable location is where you need to dispatch which is not to the location of the caller every time but I'm going to validate the location of the caller that I can do so I will take a device where I know the GPS location of the device place a N911 call and then validate what Annie Alley says is the location of that caller and then validate what RapidDeploy is saying is the location of that caller absolutely it's the only way to do it with all four carriers indeed but I really want to make sure we understand dispatchable location is a different conversation and it's going on out there it can cloud things up there was a question over here yes I think there would be one important difference with RapidLight it's a manual lookup very simple yes it's really just equipment being installed versus us going to their web site well I don't know are you beta testing with RapidSOS we're in the beta testing where we no longer have to deal with the caller I don't know about that program on this project so that's completely separate to this one it might be the situation between RapidDeploy and RapidSOS so is that going to be a police department so it would be RapidLight yeah so after this we'll get together and we'll see what might what changes if any would happen for you that's a good question and then there was another yes so we might get a number one that we have transfered to PHP because a lot of our is it going to show that transfer is it going to show that so if it comes in as a 9-1-1 call yes you will get the data even if it's transferred in as a 9-1-1 call show you that that transferred on a 9-1-1 and then will that data record back to you that that might be routed to PHP that's okay because that call came into R to PHP because it hit that cell tower so it'll show you the exact location of that caller and then when you answer that call if it's still intended for PHP you would still have to transfer it no it doesn't mess up the data no so looking at the deployment schedule like we said we've already deployed at 48 locations we're validating this information which is the purpose of that edge device that's in there Comcast is working on that 10 meg fiber connection into every PSAP and they're working with a few partners including Charter Cox and in some locations they may have to leverage the connections through the telephone companies like AT&T and others there's only a few of those less than 20 where they have to do that all the remaining PSAPs will be scheduled to be deployed by the end of this year these technicians will be installing the cradle point routers and then your CPE technician will install the Y connector into your CPE if it's not already in there and an AT&T tech will install the cradle point router we've noticed that there was a lot of feedback on how do we get the call record data if I get called into court or something that I need these records so there's a process built into the system where you get a request in less than 24 hours you get that data and it's usually much, much less than that 2 to 6 hours I don't know if anybody has done a request in the room yet so we have a couple others that other PSAPs are saying it happened very quickly this is where we are we've sent the email Samantha gave a great update on that so I don't have to read through most of this information but when you get that slide if you have any questions you can send an email to him his email is just curtduckalot at caloes.ca.gov if you deleted his email you can either go check your deleted box and get it because there's some good stuff in there or reach out to him and he'll get you that back also you'll expect an email from Samantha, same process if you didn't get it or it went to your spam or something reach out to her directly we also provide training and when we deployed this at Palo Alto in less than, just to give you an idea how fast this is in the power of cloud computing the Y cable was already connected when we got there so we got on scene within 15 minutes edge box was installed LTE router was synced up and we were receiving live data at the dispatch positions in the dispatch center interface with the system no problem so is that kind of those in the room pretty similar to your experience I mean this is pretty cool how fast this rolls out, I don't know how many of you have done a new technology integration in less than 45 minutes but probably not too many of you so that's really it's a pretty powerful tool and we're pretty excited about continuing this roll out so I want to end talking about this sometimes we'll reach out to you and ask hey give us a success story give us some feedback you obviously can tell us no you can tell the vendor no no problem with that we at OES can't endorse a single vendor so we are very mindful of that but if you can share these success stories success stories about rapid deploy success stories about next-gen 9.1 and some of the other things we're doing there's just a sense of what these companies are doing with that data so everyone that's in the room whether it's rapid deploy or Synergym or NGA 9.1 or Autos or I don't know there's probably other vendors in the room too Frontier, AT&T all these companies they sit on these national boards committees standards bodies and they need a reason to justify their existence to their executives who are sponsoring their time, energy and resources on our behalf in order to participate in all this work that's where these good news stories go so if you have some good news stories share them because that's the work that they're doing at the national level that some of you just may not be aware of again if you can't share the data then say no that's simple but that's the reason why we ask I've even been told in our executive leadership in Cal OES you need to do a better job budge of telling the good news story of all the great things that are happening in 9.1.1 and we lose sight of that this is just what we do right why am I going to toot my own horns just what we do every day but it's important to help us get visibility on some of the things that we're doing for 9.1.1 so with that we have six more and in LA in the central region I think we have one more as well so if you had someone who couldn't be at this meeting take a look at the schedule it's very similar not exactly the same everywhere we go but very similar and see if they can participate this one today was recorded and we will make it available on our website so obviously there will be a YouTube session that you can refer back to at least to get it posted maybe longer so you've got that opportunity as well if you want the slide deck send an email to Andrew Mattson on my team and we'll make sure we get a copy of that slide deck to you so any last questions yes right here so the question is are we going to merge together all these over the top you're doing text over the top through a web interface you've got rapid deploy and then you've got the southern location and I think it's important to with this progress making sure that they're filled in with a person putting those pieces together right now we're logging in now over the top that solution making sure that that's actually intended to merge at some point interface, and then you've got this other location that's coming through Annie Alley. Yes. Next Gen 901 is going to merge all that together, so the best location will come through Next Gen 901 and be integrated with what you have at PSAP. The only caveat to that is some of your CPE or some of your CAD may not be able to support that. So I will bring a standards-based delivery as far down that process as I can. Right? Yes. That's exactly the idea. And where we find barriers, what we've done is we know that in order to interface with the CPE at every PSAP, not all of you can support NINA i3. We know that. So that's one of the requirements on our Prime Vendor Autos is develop a PSAP interface device that will be able to interface with all the CPE we have in California, transition it over to CAMA, and then support all the flow of information that we need to validate the call arrived, the location is there and it's been anchored and answered and all that. And then when you transfer that call to package it all back up into a SIP packet that Next Gen 901 can route to the right PSAP again. So yes, all that's being designed into the solution. Yeah. Oh, there was one other question I thought. We'll put the link on our website, probably easiest to find, and we'll put it right on our splash page. So it's caloes.ca.gov slash 9-1-1, we'll get you right to our website and we'll put it right there. Okay. So Pat, you want to? Yeah. I just want to take a quick minute and ask you to extend to your police chiefs, your fire chiefs, your city council, your city managers, you know, are gratitude for supporting us in our effort to get a Senate bill 9096 to pass, which re-did the center fund. I think you can see from the effort that 9-1-1 branches is going to, is really phenomenal. It's going to really bring California into the next generation for the 9-1-1 services. At 8 pre-posts, the Senate fund, as it was existing under the legislation, it was passed probably back when I was a baby, which was before 9-1-1. We didn't have telephones. The revenue stream was going down, down, down, and last year we tried to get legislation pass which modernized the revenue stream and it fell one vote short. This year with the support of the cities, the counties, the police chiefs, the fire chiefs, the fire chiefs association, the sheriff's association, chiefs police, you can help you with the name of Walt. They really, really did a great job in pushing and getting the legislation passed, which models the revenue stream based on any device that can contact 9-1-1 as opposed to the landlines that the old system was based on. So had it not been for passage of that legislation, this would not have happened. They were ready to go a year ago, 9-1-1 Ranch was ready to go a year ago, and they had to put everything back onto the shelf. This year it was a lot different, and I think you can see we've got some pretty exciting stuff coming up. So thank you all for your support. Thank you for your interest. And next year at 9-1-1, thank you for the support of the 9-1-1 Ranch. Great. Thank you everybody. Appreciate your time.