 Secretary of Natural Resource Agency. I believe we saw Ms. Suleyir. I'm sorry. Sorry about that. Secretary of Natural Resources. Sorry, Brian. Brian Dash here for Wade Grofler. Excellent. Apologize. Secretary of California Health and Human Services. Hi there, Julie Suleyir, Assistant Secretary with Kelly Chutas and for Secretary Mark Valley. Excellent. Thank you so much, Julie. Secretary of Transportation. Lori Pepper here for Secretary of Michigan. Thank you. Secretary of the Natural Resource Agency. Sorry, excuse me, Brian. Secretary of Business, Consumer Services, and Housing. Hi, Erica Gonzalez here on behalf of Secretary Castro Ramirez. Thank you. Speaker of the Assembly appointee representing the interests of private businesses. I do believe I saw Lupita on the call. Okay, Lupita will be joining us back after a prior engagement. Governors appointee representing the utilities industry. This is Adam Wright, President. Welcome to the board. Thank you. Send a committee on rules appointee representing county governments. Afternoon, Jeff Tony, County of San Diego for Holly Porter. Thank you. Chancellor of the California State University, President of the University of California. This is Amina Asafa representing President Michael Drake. Excellent. Thank you all. We do have a quorum. Chief Deputy Director Curry, would you like to provide any opening remarks? Nice to see all of you on our new world of hybrid environment. It extends to this, so we appreciate participation in the important project. Director Gillarducci apologizes, was unexpectedly unable to attend today, so he asked me to fill in. I'm happy to do. Just in opening, we have not met since October, so it's been a little while, so we've got a full agenda of updates for you, of positive progress on a lot of fronts, so we're really excited to get into the dialogue, and welcome to Adam, who's a new member representing the utilities industry for PG&E, so maybe he can say a few words at some point in the meeting to welcome you to this group. Contributions, as I mentioned, we've got updates across the board with system ops, exciting news on the buildout that has progressed tremendously in California research and development, and 50-thumb alerts now have been issued in California, so a lot of this is being in real events, so our public is getting more used to this, and I just want to thank all the partners who when you harken back to when we started this, that have figured out how to make this real in our state and beyond. It's a lot of hard work, and that's a lot of new territory, but that's possible because of all of your input, especially from we've also got some exciting news on budget, but really hope to spend a good time, a good part of this meeting hearing from you, really envisioning this next juncture of how we can get this technology, this system, better embedded into our business, our industry, and all the things that are important to California in addition to the public uptake through cell phones and automated alerts, so that will be something we hope to walk away from today to really have some brainstorming and a roadmap of what that will take because it occurs to us that we have to, industry needs to understand how this is a benefit and we've got to do the work to help bridge that understanding, and also there may be new technology that has yet to realize that enables us to use EW, so we know all those things, but we want to make sure that you want to apply our efforts at Cal OES to really kind of run. I failed to mention part two, so again, thank you to board members for being here, thank you to all our partners. You can't see them off on camera, but we've got a lot of our subject experts and partner agencies here in the room, and updates and the dialogue, so back to you. Excellent, thank you. Adam, I'm not sure if you want to take a second to introduce yourself before I open it up to the rest of the advisory board members. Sure, yeah, happy to. So Adam Wright, I'm the Chief Operating Officer and Executive Vice President for Pacific Gas, I'm an electric company, moved to California about a year and a half ago from the Midwest, and so earthquakes are a new phenomenon for me. I've experienced a couple of small ones already since I've been here, but very, very happy to represent the utility industry on this advisory board. The utility industry obviously is a very important part of the economic and of infrastructure of the state and of this nation, and so our response and the ability to partner to help people prepare for these types of emergencies is just critical and foundational to our business model and why we exist. So happy to be here and look forward to contributing. Thank you, Adam. Would any other advisory board members in the room or virtually like to make any opening remarks? Hearing none, we'll move right on to review and approve the meeting minutes from the previous meeting. So there is a copy of the meeting minutes in everyone's packet, whether you're received it virtually or in person. Please take a few minutes to review them, and if there's any changes that should be made, let us know. So any changes from anybody on the board? Remember, if you're virtual, you may have to unmute yourself. I'll move approval. Hearing none, do we have a motion to approve the minutes? Sorry. Excellent. Do we have a second? Excellent. All those in favor, say aye. Excellent. Motion passes. With that, we'll discuss the general program updates, which will be covered by yours truly here. Let me make sure that we cued. Excellent. All right. So it's been about eight months since we last met with the advisory board, and a lot of exciting changes have occurred. The first and definitely most important to me is that we are once again fully staffed as of June 1st, 2022. We did have some vacancies and program for a bit there. And obviously that was of a big priority for us. And I can truly say that was the biggest priority and we were able to backfill fairly quickly, not just with my current position, but all the way down the line to the rest of the team. We're very excited about the team. They've hit the ground running, and you're going to get to see some of the exciting work that they've actually worked on in the last eight months. Well, we'll move right along to the 2022 business plan. And we want to thank the board in particularly for your participation during these meetings. Conversations like this are designed to continue to inform the roadmap for EW expansion and innovations going all the way to next year, 2022, 2023. And specifically what's going to be informed is the milestones, our goals, our metrics, and ultimately the future business plan when we submitted in 2023. So thank you all so much. You are going to hear some exciting updates from the system operation side. We were up to 871 contributing stations. And let me tell you, that's every single month we continue on that progress to finally get to that magic number of 1,115. We are going to get a little bit of an update on our research and development work group, particularly on some of the enhancements and some of our previous projects that we have funded here at KELOVS, as well as a little bit on the home base feature, which the advisory board has been previously briefed upon, but it has now rolled out and it is active in everybody's app right now. We are going to get exciting update on the finance front for earthquake warning California and the California earthquake early warning system. We'll talk about current year and as well next year's budget, which would be the 22-23 budget year. Last but not least, our education and outreach has really kicked it up a notch. We will be briefing out on some of the efforts that we took during the earthquake preparedness month of April and some of the partnership engagements that we had, some of the really good media coverage that our preparedness tour received. We're very, very excited. We saw some real tangible results from that. You'll also be seeing a little bit of some of our efforts as it relates to industry engagement and end user enlistment. So really kind of sets the groundwork for us to kind of focus on the overall objective here, which includes advancing the earthquake early warning technology in California. So that concludes the general program update. Please note that we will be saving once again a public comment until after the system operations and research and development sections. So let me make sure, excellent. With that being said, we're gonna move right along into the system operations updates and I will be providing the programmatic updates for the first half, but we are gonna be joined by our Cal OES partner, Dr. Jennifer Strauss for the My Shake app. She is the product manager and will follow me and provide updates on the current status of My Shake. I'm sorry, UC Berkeley, apologies. Okay, make sure that, excellent. So as I already mentioned previously, the California earthquake early warning system network of contributing stations has increased to 871 out of the 1,115 stations that have been identified. That's an increase of 28 stations since we last met. And obviously that's kind of like the end game for at least this for the system operations workgroup. Cal OES and our partners have completed 399 out of the 702 planned and funded EW stations and the increase of 45 stations since October 2021. There are a remaining 303 stations pending completion. Our partners at public safety communications continue to work to conduct more EW seismic stations into the state microwave network and to further secure tower and vault leases. There are an additional 11, excuse me, 11 EW stations online and connected to the state microwave system for a total of 63 out of the 330 stations with 267 remaining. There are an additional 11 PSC tower vault leases that have been completed and we are up to 28 out of the 76 leases that have been identified. I'll touch on a little bit on Q's 21-22. We system ops was allocated about $12.3 million for the 21-22 build down. This funding in particular includes station builds and updates, but also software modernization and equipment purchases. The funding will sunset in April 2024 and will include the proposed 53 new stations as part of this particular fiscal year. 40 proposed real-time stations, 10 updated stations, 12 rebuilt stations and 20 upgraded stations. And of course, we always want to talk a little bit of the challenges that we have been dealing with in previous meetings. And again, today, you will hear from me that permitting is still one of those areas that have slowed down the station builds. Therefore, to deal with this, Cal OES recently established a permitting work group to coordinate resources, to set priorities, system priorities and really to inform decision-making and streamline processes, to really kind of expand our outreach to further identify, stout and execute permits for the installation of approximately 122 federal and state-funded seismic stations by June 2024. The task force is comprised of some of our partners which include USGS, Menlo Park and Pasadena, UC Berkeley, Seismol Lab, Department of General Services and of course, Cal OES. This group will be meeting on a monthly basis to collaborate on the permitting difficulties and share best practices between all the agencies and enlist assistance from each other if needed. Next on the agenda, we do have Dr. Jennifer Strauss, My Shake app product manager, providing us a quick update on the My Shake app. But before that, did you give anything to the deputy? Is that okay? Yes, absolutely. To talk in real and welcome any comments from the advisor, I just wanted to, this is Tina again, I just wanted to comment briefly on the build out. So a lot of numbers that were just, but good news in, things are moving in a positive direction, considering all the challenges, especially with COVID and supply chain that's kind of messed up a lot of things and in society or slowed things down. All the stations are funded, which is fantastic. So while not all complete, there's a pathway at least financially to meet the goal of what we know the saturation needs to be for California. The one area, and I just want to punctuate is that because as you can imagine, and all of you in some way or another, work on land use kind of stuff. So you know how complicated this can be. The team knows where the location needs to be that's optimal. So that could be a private landowner, right? It could be federal government, it could be state government, our public safety communications team, who's kind of attaching all of this to the state microwave network that gives us some backbone for the delivery of the signal. Those are shared lease sites where you've got multiple state agencies kind of bolted on to one tower. So it gets really complicated really fast. I appreciate the team coming together to at least realize as many efficiencies as we can in this permitting one, because it seems to persist. The hardest ones I would imagine you saved for last because we ticked off the easier ones first. But I think as a board, if there are any creative solutions out there that come to mind that we haven't explored, please let us know because we realize that you all work in the space, in your similar space in terms of communications or technology or dealing with land use. And this is an area that we'll push and we'll continue to push, but COVID and equipment delivery, I want to say we'll catch up and those will be behind us, but the permitting one seems to be one that we'll probably just get more complicated as we proceed. And so this is the time to rally as much as we can on solutions. So thanks in advance for any thoughts you have on that. Idea of like, are there any locations within properties owned by our department's agencies? Yeah, certainly. I do believe that there are some stations that are still outstanding that we could definitely use some help with natural resources aside. And we can definitely team with you offline to kind of clearly identify because obviously it would be too many if we had to identify, but I appreciate you making the offer. Sure. I had another similar question. So all of the sites have been IDed or do you need any new targeted? That is correct. I think and you guys will correct me if I'm wrong. So it's, there's some flexibility to kind of move it slightly, right? If like, you know, the state property's here and the private property's here and we get, but there's a, you know, certain very, very precise like distance, they have to be around one another. So it's not as simple as, you know, let's site it in Jeff's area because it's easier. We might be able to do that, but then you might mess up that, Jen's nodding, all right. I got. Yeah, I mean, the density of the stations is set by how the physics of earthquakes work. And so the 10 kilometers in urban areas and around fault zones is really so that you have four stations lighting up at the same time as soon as the waves hit the surface. So you have a little bit of fudge room like Tina said, like a kilometer or two, but we're not trying to hit a target like number of stations all clumped in like one area of California and we're success. We're trying to get good coverage everywhere. And I would add that Southern California is more densely built out than Northern California is at this point. So a lot of our focus permits and the site assessments has been Northern California. Copy that. Like, thank you. Laurie, did you have a question? Yeah, thank you. So I know I've told this to the team, but I want to offer it again, if there are any sites that are on Caltrans property, please, you know, just send those to me and I will work with y'all to get it through our permitting process. Excellent, thanks so much, Laurie Pepper. We will make note of that and we appreciate your willingness to assist. I wanted to open it up to see if there was any other advisory board members that had any comments, either in the room or virtually. In that case, we will turn it over to Dr. Strauss for her part of the system ops briefing. Thank you. Perfect, well, thanks for inviting me to speak at the advisory board meeting. It's always great to see everybody here and now in person. Thank you, Jessica. So I'm here representing the My Shake app, which is funded by the California Office of Emergency Services as part of the CUE system and is powered by the Shake Alert earthquake early warning system. So the My Shake app is a dual purpose app. Our main goal is to provide earthquake early warning alert delivery to the citizens of California who have downloaded the app. We also have a research aspect of the app that is a citizen science effort to use the accelerometers on cell phones to monitor for earthquake motions. I will talk about the former part in the operations section today and then I'm going to talk about the latter piece during the R&D section. Before I get too far into discussion, I would like to thank my team that is working hard to make sure everything works well and is up and running 24 seven. So these are the people that make the My Shake app possible. So our systems operations update for this time is to share that we've had 52 alerts go through the system with 51 actual alerts being sent out since we began operations in October, 2019. All of those alerts are for estimated earthquakes of magnitude four and a half and above and they are sent to phones targeted in the MMI three zone, which is basically low to heavy shaking. We have had 185,000 devices alerted overall across those 52 events. Some of them have been as large as 45,000 people at a time. Some of them has been as small as like four devices because it was in a very unpopulated area of the state. The largest alert that we have sent so far was for the magnitude 5.9 Walker Lake quake that was in July of 2021. And then we also have the magnitude 5.9 Fortuna quake which was in March of 2020. Both of those tied for first place. The largest alert in terms of phones was the magnitude 5.8 Lone Pine event that was in June of 2020 and that was sent to over 47,000 devices at one time. So that's basically what we've been working at and keep those alerts flowing as they come in. On this map, we're trying to show coverage area. A lot of times people think about earthquakes only happening in Los Angeles and only happening where Loma Prieta happened and that the rest of the state doesn't get earthquakes that much. Well, when you're talking about magnitude four and a half earthquakes, not huge magnitude ones, but ones that could potentially cause damage or injuries, there's actually pretty good coverage across the entire state. So if you look at the left-hand map, it shows small dots representing populations and then the dots are color-coded based on the shaking intensity that was estimated for that event and the shaking intensity, all this goes from about three and then we capped it off at five just to give a good color spread to the map. And so you can see the map is pretty much color-coded for most of the population areas of the state all up and down, north to south, east to west. If you look at the right-hand map, might be a little confusing to get two maps with two different colors, but the right-hand map shows the actual ground shaking after the event that everything has been processed and given a actual verifiable earthquake magnitude. You have to remember that for the Qs slash shake alert system, these are really fast estimates that are being done with very, very little data and it's really a testament to the teams that work on that, that we get this close in sort of sub-second amounts of data. But yeah, most of the state is covered. So you too in your area, should think about earthquake safety and earthquake preparedness. The final slide that I have for this section is showing an example of our latency. We put in a couple of tags and flags on the phones to try to get information back as to how quickly we are sending these alerts out. So as an example, the magnitude 4.5 L Monte quake which happened back in 2020 was in the Los Angeles area and we hit a good amount of phones, about 20,000 phones. As you can see from the phones, we got information back from 20% of the phones received the alert in about 1.3 seconds, 50% of the phones in 1.8 seconds and 80% of the phones got the alert within 2.6 seconds of when Shake Alert posted the alert message. And so this is very important to show that we are able to deliver these alerts at scale to people when it matters most. One thing that I'd like to note about the app, I know there might have been a few questions about how we safeguard people's security and privacy. The app is run through crypto wire before every app release because it is available globally and not just through the state of California. It also conforms to the GDPR privacy levels. And so it is an approved sanctioned app on both the Google and Apple Play stores. We have a very extensive privacy policy that goes into all of the nitty gritty of what we do collect, what we don't collect and where that is stored. Jessica was very nice to print out hard copies of that for everyone. So if you're interested, I have a stack over there but I'm also happy to answer any questions or it's available on our website myshake.berkeley.edu. That's what I have for operations and I will see you again in R&D unless you have any questions. Thank you, Dr. Strauss. Real quick, as mentioned, public comment will be open after we hear updates from both system ops and research and development which is up next. At the time, if you wish to make a statement by all means please let us know in the room or in the chat feature in Zoom and the moderator will unmute you. But before we go there, is there any questions from the advisory board? Brian? I just had a question. This is great to see so many people were contacted and wondering, do we have any evidence, any anecdotal evidence or else that would show as of this alert, I was able to run out of the house where I was standing. There was a huge bookcase that smashed to the ground and it saved me. So yes and no, yeah, we have not gotten anything quite that dramatic but we do have a Twitter page and an email, well an email that we get feedback from different users. So after all quakes in large population areas in particular that we see that we do call Twitter and see people saying, oh, I got alert right before the shaking happened or hey, I got out of the way of a book that was about to fall in my head. So no massive furniture movings, but little tiny things we have seen evidence of. I think I recall in the Portola quake, there was somebody who had a large following on social media that posted something and was in the car actually. Oh yeah, yeah, I think you're right. We can find that and share that. I think it'll be things like that that if we're able to share those on social media and that we're able to amplify it, those are the type of things that will really get people downloading it and realizing. Yeah, totally agree, totally agree. Thanks. All right, we're gonna go to the next, I'm sorry, before I move on, is there any other advisory board members virtual or in the room that have any comments or questions? All right, we'll move on to the next slide please. For our next topic, we're gonna continue on into research and development updates with Dr. Straus, so she's just gonna stay there and advance her own slides to the next presentation. Okay, here's another title slide. Hi, I'm Jen, I'm with the My Shake app. In case you are joining us midway. So as I said, the My Shake app is the alerting app. We are a licensed operator for the Shake Alert system and the app for the QS system for the people of California to receive alerts. But we also have a research aspect to the app that's monitoring the accelerometers on phones to see what we can do sort of in the future. And this was really important and we're very thankful that Kaluuya saw the importance of funding not only the alerting side of the house, but the research side of the house because as we know with the system as a whole, funding fundamental research is how we got here in the first place. So the only way that we're going to be able to push forward into the next generation of capabilities is keeping that side really strong. For those of you who don't know, your phones have a sensor in them that's called an accelerometer. So when you're watching like a movie or something on your phone and you started in vertical mode and then you turn your phone and it automatically knows to go into horizontal mode, that's the accelerometer. It knows which way gravity is and it knows which way the phone motion is going. And so we're harnessing that sensor to measure earthquakes. So every time that there is a earthquake early warning that is sent out over my shake, we also send a trigger to record the motion on that sensor. And when we get those waveforms back from some phones we can make really cool plots like the one I'm about to show you right now. So here we see a very scientific plot but I'm going to walk you through it. On the x-axis we have distance. So distance from the epicenter. Where is the center of the earthquake at zero kilometers? And how far away was that phone from the epicenter? On the vertical side, you can see the time of the S wave arrival. So to jog your memory, an earthquake starts, there's a first wave front that arrives the fastest which is called the primary wave. It's a compression wave kind of comes up below your feet. The second wave front is the secondary wave because we're very creative in naming these things. And that's a transverse wave. That's the thing that goes side to side. If you think about people and buildings we're really good at dealing with vertical forces, right? I can jump up and down, ideal with gravity. Buildings and people are really bad dealing with horizontal forces. If I pull a rug out from under you, you're going to fall. And so it's traditionally the S wave that we think of as being the most damaging aspect of an earthquake as it's coming. So we use that as sort of our time thing. If we get that alert to you before the S wave comes, you can take protective action to drop cover and hold on. If we get the alert to you after the S wave arrives, you should still take protective action and drop cover and hold on because it's still the correct thing to do to make sure you're at optimal safety. But even a late alert is gonna give you that sort of cognitive association that the thing that you're experiencing is an earthquake. So you can remember your training to drop cover and hold on. So in here we have a nice horizontal line at the zero mark which means that is when the S wave arrived at that device. And so you can see that we have purple dots and we have some green dots. And all of the green dots are above that line and all the purple dots are below that line. And so the purple dots indicate that the alert arrived with or after the S wave. So those people were ingesting the alert as a safety reminder to drop cover and hold on. It was not a please take protective action soon. It's you're already being affected. However, the green dots, 56% of the people got the alert before the S wave arrived at their location. So they could already begin the drop cover hold on process before the waves get to them. And if you have listened to earthquake country alliance, if you have done your shakeout drills every year, you know that drop is the most important part of drop cover and hold on. And drop is the thing that you can do right away and doesn't take a whole lot of time. And so it's really great to have this sort of data that can really confirm these arrival times in a really diagnostic way and show the success of the system. The second thing that I would like to talk to you about R&D doesn't really have to do with the sensor per se, but it has to do with responding to customer requests. So we take customer feedback very seriously. We try to make sure that everyone is comfortable with the app. Some people were not comfortable sharing their location services so that we could be sure to know if they were in harm's way. So we created something called home base. Home base uses the fact that my shake operates using the military grid reference system. The military grid reference system basically chops up the globe into a bunch of different sized squares and each one of those squares has an ID tag. And so to preserve people's privacy, we were not using detailed location services for daily monitoring. We were identifying people in these squares anyways. We just know you're in the square, we have no idea where. We're not like tracking you in some kind of crazy database, but we're identifying this square has people in it and we're alerting this square. So we took that idea and just kind of ran with it and said, well, maybe we can give people the opportunity to just identify what square they're in and not even turn location services on it all. And so we implemented that these past eight months and it's working very well and people are able to set their location and get their square. User feedback has been very positive so far with the exception of many, many people would like to set multiple home base locations which is not really sensible or workable because you're gonna get an alert for all of those home bases no matter where you are. And so we have been limiting people to just be able to choose one location. We do hope for the citizen science aspect and the research aspect that people will continue to share their location services with us. We only use precise locations when we are recording an actual earthquake event. Otherwise we are only assigning people's locations to these squares. So we're hoping that we still have a lot of participants who continue to use our normal service so that we can make the system better. The final thing that I want to mention is future projects that we're working on on the research side of things. We have two papers that are coming out soon. The first one is really looking at the information that I presented to you in the operations section. It's looking at the latency delivery and how we're serving up alerts for the users. The second paper is written by a previous postdoc of ours named Chin-Kai Kong. And it's using crowdsourcing of the felt reports that people can report after an event and comparing them to other avenues of felt reporting as well as crown truth observations of shaking. So that's a really interesting paper that'll be coming out soon. This year we're going to be working with Cal OES to provide additional language support for the app. It is currently available in both Spanish and English but we are looking at ways to include Chinese, Korean, Tagalog and Vietnamese to the language offerings as well. And finally with the research project we are continuing to push forward on what is possible with this sort of data. And one of the things that we're looking at is using waveform data to validate the alerting area. Most of the time when you look at your shake maps and you're looking at the intensity distributions those are done as a combination of actual sensor recordings and did you feel it responses? And my shake has a really interesting way of measuring shaking like where people are. Like you could be in the fifth story of the building and you have your phone on you and you're probably going to experience shaking in a very different way than somebody sitting on bedrock somewhere on the ground floor. And so we're looking at the shaking intensities that are actually recorded on the devices and seeing what can be said about the urban area. And I believe that is my last slide. And so if you have any questions I'm happy to answer them. Thank you Dr. Strauss. Well, first of all, we'll start with do any board members wish to ask a question or provide comment in the room or virtually? If you are online, please indicate in the chat feature and the moderator will unmute you. Jose, just a quick question for me. This is Jeff Tony for those on Zoom with the home base program. So those are folks that just don't wanna be tracked with location services. Was that the impetus behind it or? Yeah, there's actually two purposes. The first is for people who don't feel comfortable sharing their locations anytime but the secondary purpose is for people who move about quite a bit and they may go into areas where their location services are not linking up. They may be living in a rural area where they don't have very good internet connectivity. And so if they have a default location that is set that even if their location services go in and out a bit and we have stale locations for them that they'll still get an alert. Excellent. I do believe that we have a question on the chat, Adam. Thank you. Appreciate it. And Jen, nice work making a ton of progress and you might have covered this, but maybe I missed it on the purple dots back on the slide title alert arrivals. Kind of curious, how are we set up to assess the purple dots from a problem-solving standpoint? Do we have a team that does root calls, assessments or parent calls, evaluations to determine what improvements we can make to try to get to batting a thousand percent? I think that's what we're going for, right? So technically we are not going for 100% because the physics of the earthquakes itself make it impossible to alert people that are standing right on top of the earthquake. So the way earthquake early warning works is that an earthquake starts about seven to nine kilometers below the surface of the earth. That earthquake has to reach the surface of the earth and be recorded by seismometers that are around the area, which is why from the operation section, having good density of your seismic network is very important. There are four sensors that have to trigger in order for an event to be declared. Then the shaker alert system uses a little bit of time from the earthquake data that is logged on the sensors to then run algorithms to determine how big the earthquake is, where it is. Then it goes through a system that correlates data together from any different algorithms that are running. It takes that information and it packages it up into a series of XML files. Those XML files are then sent out to users like us that redistribute the alerts. So that process in general can take five seconds. So on this plot, the earthquake has already moved out five seconds before we even get the alert zero on this plot. And so if somebody is standing right at the epicenter, there's literally no way for a shaker alert or my shake or cues to get that alert to them. But the idea is that once you move out, we try to have the system go as quickly as possible. There are ways that we're looking at to try to speed up what little that we can. But there's not much wiggle room there. No, all fair points and very, very helpful. It really helps my understanding of it. But if you just take the same distance from the epicenter and just go straight up, I mean, you're gonna have what the numbers show, 56% and 44% effectively. And so I'm just curious if we're learning from the purple dots. And if we do have a target, maybe it's not a hundred percent not gonna bet a thousand, that's fine. Just curious if we have a target that we wanna achieve whatever it is, 60%, 70% and if we're assessing that gap to target. And if we have a similar distance from the epicenter, are we looking at the ones that didn't get notified to determine why not to learn from it to see if we can improve the system? That's my main question is on the continuous learning process. Yeah, no, those are really, really great questions. So the system itself has a target of alerting users in less than five seconds. Obviously we wanna do as best as we can. So that's sort of a good goal to assess. So we really look at it in terms of the time domain and not the distance domain because that's what we have control over. So we have learned over the years that we have sharded our system. We believe that's what we reported on in October to speed things up on our end. We're employing various monitoring ways so that we are aware of what sort of people are having alerts and what sort of people are not having alerts. And we're trying to find ways to shave off those seconds that we can. Okay, thank you. I'll type in the chat kind of my suggestion and we can have it at the takeaway. Thank you. I really appreciate where you're going, Michael. And obviously we want more things in the green bucket closer to the left, right? Less distance between, this is the today technology but we're imagining a future where things just get better and faster and we'll have both the trifecta of reliability, accuracy and speed that come together. So that's absolutely the goal. And I think as we kind of start to broach into the business and industry adopting that, then we're talking about business decisions being made on this technology. So we understand that all those things, including speed are critical, not just for the public, obviously for life safety but also for decision making that's gonna happen hopefully in an automated way. And so really being clear about what's possible today and kind of our commitment to continue to improve is gonna be really important to that dialogue. So I just appreciate you bringing that up because nothing's ever gonna be a hundred percent. That's why this is one of the tools in the toolbox for earthquake safety but our goal is to imagine a future where technology usually gets better, haven't yet to see it get worse that sort of harnesses the latest and all of this is great. And I just appreciate Jen and Berkeley because they designed this in a way to get feedback. Every phone that gets ping gets a ping back, right? So we know what happened, which is fantastic. We're not just relying on people kind of reporting. So this data has been just hugely valuable for us to just kind of see how it's working and then to continue to learn and evolve from that. And just to add, we do take that very seriously and we don't only wait for these events to happen to do that sort of analysis. We have a daily test that has run every single day at 11. It's a silent test, so the users don't see it happening but we test the system and we measure the latency for every single day of the year since October of 2019. And so we're collecting a lot of data to try to, as Tina said, do as best as we can to get those bar a little bit down. Excellent, I think we do have a question online. Lori Pepper, the floor is yours. Thank you and thanks so much for this presentation, Dr. Strauss, I think it's amazing since the app was first launched, launched how far it's come. And of course it's still evolving and growing but it just, I do wanna acknowledge just the incredible work that you and the team have done to date. I wanted to make sure I haven't, I didn't miss anything in your presentation when you were talking about just that some people don't wanna be tracked and having the home-based option. I assume that when you're looking at kind of just the long-term storage of the data points, you're only keeping the location, you're not keeping the location attached to a phone number attached to a user profile. Correct, so the way the My Shake app works is we actually do not require a user profile or any registration information. The phone is only logged on our backend as an ID number and it's like ZYX263, like yaya yaya, like this big number that doesn't mean anything about anything, it's just a token number. And so if you were to have a phone and get rid of that phone and you buy a new phone and you install My Shake on it, you'd be a totally different phone, totally different device. The other thing is the locations that we use to alert people are stored in the Amazon Cloud only for two weeks, two-week cache. The home base ID tags are stored for longer because that's a default, but any transitive transient location that we get from you is only valid for two weeks and that it is scrubbed and not stored anywhere. The only time we store precise locations again is for specific earthquake monitoring like this one and it is stored as a time series data, five minutes of waveform recordings. And again, it's in a database with just that random ID number which for these purposes, if somebody was trying to find this Python code that's been stripped anyways, we just care about the lat-longs. So there's no PII personally identifiable information stored anywhere. You'll notice in the app that home base asks you for an address, but we don't get that. It's only used on your phone to do a lookup table on your phone to assign it to a square. So again, we don't, I wouldn't, I wouldn't even, we've actually had people ask us to like, you know, delete their profile for the app. And I'm like, I legitimately don't even know who you are. I have no way to associate you with anything on the backend. Great, thank you so much. Thank you. I do believe we have one comment on the chat. I'll read it out loud for everybody. One of, this is coming from Adam from PG&E. One of my suggestions would be to orient this against our targets and this meaning our target. Either time or distance and percent notifications we want to achieve and measure performance against that. My experience has shown that improvement happens when we have a target, whatever the appropriate targets are in this case, measure performance against that target, identify when there's a gap to that target and then identify the drivers for the gap and problem solve to close them. Might be useful to have a few views of this along with any high level catchback actions. Thanks. So we'll make a note of that Adam and kind of take it, you know, go back to the lab and see if there's anything we can do to kind of plan against that. I will also like to welcome the speaker of the assembly appointee, Lupita Sanchez Cornejo, who is representing the interests of private businesses. I do believe that Amina has a question as well. Amina? Hi, Dr. Dan. My question is to clarify, when someone has location services turned on, the app basically uses kind of like geofencing to like notify them wherever they are. If they're in LA or they're in San Francisco of, you know, an impending earthquake. If they have it turned off and they're only notifying if they're in that little square, is that accurate? Yes. And it's not precise location services that is used. It's only the sort of smeared out into the MGRS square. So yes, if we have a current location for you, we are going to, you know, alert you based on that location. If you have a home base set, we are also going to alert you at that home base location. So if they both happen to be the same location, you will get one alert. If they happen to be separate locations, whichever one is in harm's way, we'll get the alert. Got it. Okay, thank you. At this point, public comment is now open. If you wish to make a statement, please let us know in the room. If you are online, please indicate in the chat feature and the moderator will unmute you. Here and none, we'll move on to our next presentation. Thank you so much, Dr. Strauss. Next to present is Lori Najura, Deputy Director of Planning, Preparedness and Prevention Directorate. And she will be discussing our finance updates for current and budget year. Lori. Thank you. And I wanted to make two points of clarification for our new members and those designees who maybe this is their first or second meeting. So you've heard the term cues and the system from Canada down to the Mexico border that's the shake alert system. Here in California statutorily, it's referred to as the California earthquake early warning system. And it's powered by shake alert. And so we colloquially call it cues, the acronym C-E-E-W-S. So if you hear cues, that's what we're talking about. The other thing as we advance to the next slide, I wanted to talk to our board members who may be from non-state agencies and are not familiar with the budgeting process. It's already been alluded to. So in any given year, we'll have a budget act that appropriates funding for the system. And we have one year to encumber it, one and a half years to expend, another one and a half to expend and the final half year to close out. So that's why when we say we were appropriated money in 21-22, we have three years before that money finishes out. So on that note, let's take a look at the current year, which only has two days left in it. And this budget that we're working off of today was 17.283 million. It was one time general fund to finish out the build out of the California earthquake early warning system. And it included, Jose already mentioned some of the things that were included that we did. So we are already in contract on some new and updated systems, sorry, stations, improving telemetry through our PSC project. We're continuing our statewide education and outreach campaign. We've got additional development going on on the My Shake app as you just heard and some research and development. Now let's look at the next budget, which is in print. It's awaiting the governor's signature, which will happen today or tomorrow. So we've got some exciting news. It includes $17.1 million ongoing general fund to support education, outreach, operations and research development. Last year's budget included funding for the remaining station build outs, as it's already been mentioned. They're all funded, but not all complete. Over the next couple of years, we'll see all of those. So this year in our funding pattern, we then transition to more maintenance and outreach and research and development. Additionally, this year with the governor support, the administration proposed and the legislature agreed to make early warning out of the general fund on an ongoing basis on the principle that alert and warning is a public safety issue and a core government responsibility. So that's exciting. That's new and different. And then with the funding this year also comes a few new positions, including a dedicated public information officer just for earthquake early warning. And in addition to the budget act, we have some trailer bill language that is gonna require a report next year chronicling our efforts to seek other private and public funding sources or incentives. And it's just a one-time report. So this year with our funding, we anticipate maintaining the existing project, continuing state-wide and instituting targeted outreach and education, which we'll talk a little bit more about today. Concentrating on the adoption of earthquake early warning, automated actions among businesses, other services. And finally looking at some R&D projects in radio and television, other areas to enhance public awareness. Are there any questions? At this point, we'd like to open it up to any board members who wish to ask a question or provide a comment in the room. We'll start with the chief deputy if she has any. Sure, yeah, I would just like to underscore. I mean, we got our first one-time investment in 1617. So you think about the journey in California since then we've been fortunate to have the legislature and the governor support this, and that is entirely due to the promise and the success of the system. And now this pivot, hopefully not final, to kind of recognize there's this core government function that is important to maintain now that we've introduced it to the public. That brings consistency, that brings some reliability and stability to always have that backbone of this be something that the state is continuing to invest in. So it's got to be on all the time. Those first stations that were installed back in 1617 probably have to have some work. So there's things that have to be done that you can understand are ongoing. We also recognize there's an investment that is and will continue to be made by everyone else in order to employ this kind of new, if you wanna call it risk reduction or mitigation technology as it gets better. So there is a balance of interests that is feeding into this. Hopefully this stability that the ongoing funding will provide, which includes staff to keep working on this, will also help with for adopters to see that the state is serious about continuing this program. And we know that it provides tremendous, tremendous promise and value for earthquake safety and it will be something that they want to employ in many other ways, beyond what we're using it for now, for employees, for safety, for manufacturing, critical infrastructure, all those things that can benefit from this and other means of delivery in order to make those things happen. So again, I just wanna underscore that we're very proud to have gotten to this moment and but it's really because of the work that everybody did to bring this to fruition. Certainly in California, I'm not surprised and think any of you are that we've had 51 alerts because earthquakes are very real every day in California. So again, just hopefully we'll have some good news for you in a day or two when everything's final, but I just really want to puncture in the funding part. Thank you. Do any other board members wish to ask a question or provide comment here in the room or virtually? They just a clarifying question. That's fantastic that it's ongoing funding. Is that 17.1 annually on appropriations? Yes, that is correct. Okay, fantastic. Excellent, thank you, Phil. Public comment is now open. If you wish to make a statement or ask questions, please let us know in the room. If you are online, please indicate in the chat feature and the moderator will allow me. All right, hearing none. We're gonna move on to our next presentation, which I will be presenting on the goals for EW outreach and education. So give me one second. First of all, I wanna start out by really kind of restating our overarching goal within this program. And that goal can be best summed up by stating that we want to move towards earthquake early warning technology for all Californians and diversifying the ways in which Californians benefit from earthquake early warning technology, right? And based around this particular overarching goal, we have taken steps within program to try to move that needle forward, so to speak. In fact, one of the ways that we are actively trying to recruit and do outreach is by contacting leaders of state agencies per the prior discussion that occurred with this advisory board. In fact, we can report out that we have not only been able to introduce the EW program to a variety of state agencies, but also provide them information on EW technology and its importance. We've actively tried to seek partnerships for disseminating this information and really try to truly explore where automated actions can be effective within each and every single industry. So for those that attended last meeting, you guys will probably remember the fact that we were at the precipice of sending out a letter to the cabinet of the state of California and we can report that that letter did go out and in fact, one of those, I'm sorry, we did send the template of that letter to the entire advisory board a few months back. And these letters really were done to encourage the downloading of the My Shake app on all state-owned mobile devices. And therefore these letters really kind of affected that change within the cabinet secretaries last December. Some of the letter recipients went beyond the request that the director made and provided information to employees about EW technology and earthquake safety throughout their intranet articles and other means of communication. So really the letter was not just, did not just meet the goal that we originally kind of set out for, it kind of went one step further. We are planning within program to do a next round of similar letters that will go out to constitutional offices and officers from Cal OES from the director's office, but also to look at appointed executive branch leaders. Their purpose will really be to just engage not only the state agencies, but also the engage the industry, the stakeholders and the public through these representatives. That way we can better identify how EW technology can support the representatives regions, their stakeholders, their communities. We do hope to engage in more in-person outreach events, very much like the one that you will hear about later on in this presentation. This particular tour that we did in April really kind of allowed us to go out to the communities and deliver socialization and outreach to the individuals and allowed us to specifically identify and work towards a more equitable outreach strategy and really kind of target some of the underserved communities within each region. One of the key things is for us to gather more buy-in at all levels of government, but eventually as you have heard before, particularly industry, private sectors, I'm sorry, the private sector and specific sectors that we really think are important for the eventuality and game of adopting EW technology but also end user enlistment. So we are currently working on prepping what we're calling outreach packages to really kind of present to key sectors, those sectors being medical transportation and utility sector. These are the starting point. I don't wanna give the impression that these are the only sectors that are working but we are gonna take a targeted approach at first while we develop the methodology of how best to work with each and every single sector as you guys can imagine, every single sector has nuances and we wanna make sure that we don't just do it in a cookie cutter manner, but we do it right. So we are gonna be working with some of the associations for these sectors to kind of truly help to advance that system uptake within California. Now we have seen some successes within these particular sectors and industries, not just in California, but also Washington and Oregon. And really the goal for us is to kind of launch off of that, we want to expand and build upon these successes and truly, this aligns us with aligns the industries I should say with USGS, recently released strategic plan that very much targets the same folks, right? All the sectors and the private sector. At this point in time, we'd like to kind of open it up for discussion over to the board and we have some questions here that kind of will get the conversation going, but will we wanna really kind of hear from everybody as to how we can best engage with stakeholders that you may represent or industries that you may represent. We ultimately feel that each board member obviously chosen very carefully to represent either a key sector or stakeholder group. So we'd love to hear any feedback from you all about whether what should we include, who we should work with, key stakeholder groups, how we can collaborate and leverage. So I'll turn it over to the board for discussion. I'll talk to Mike first, Tina. So a couple of thoughts as we kind of move into this part of the presentation. So this is somewhat following a script that we anticipated. So we did an analysis that we enlisted a company to do a benefit analysis, I don't know, five years ago. And they went through, and this is when it was very much an infancy program and they interviewed all kinds of business, private, public, critical infrastructure, different representatives to understand what would it take? What would it take to make the business case for using earthquake early warning wherever you sit? And the vast majority thought that getting it out to the public and convincing us that way, the collective us that way on the efficacy of this was the best place to start. Because a lot of people have cell phones, relatively low risk considering we had no warnings for earthquake before this technology and then could maybe kind of transfer into the employer using that same cell phone technology that's already available for its employees and then the more sophisticated operations like automated shutoffs and elevator stopping and all those things. So we approach this as a public access first for a lot of reasons, including that. So this is really now we're prepared to make this juncture however we recognize that there is no one size fits all. First of all, an entity needs to understand that this exists and what it can do. And then there's, should I invest in it? What is the thing I'm investing in because it might be technology that actually receives a signal and does something that hasn't yet been, doesn't yet materialize. And each one of you have who are familiar with what the barriers and opportunities towards that path are, right? So medical is not going to be the same as education. It's not going to be the same as utilities, et cetera. So we're really, we really want to ask for your advice at this point because while we have the dedicated staff that's going to really focus on this and kind of to continue on Adam's theme set our ambitious goals for ourselves to get more sector adoption, we need to understand the nuances of what that pathway is because you know best. And obviously we want to start somewhere transit we're going to hear about in a little bit have our a lot of reasons again, not surprising was an early adopter and has been using it for a while but it's at a point where we want to make sure that we're broadening it as much as we possibly can beyond the public kind of cell phone uptake that we've been spending a few years on now. And so this is truly just a brainstorming session but we want to harness your ideas and the outcome is we want to set some goals for ourselves and then we'll go to work and we'll work with USGS and all the CGS and all the partners to figure out then okay on the operator side of this what's that what's it going to take so that we can help help users realize their goals to employ EEW so and then we are fortunate to have a budget for this outreach that we define so we can focus that on what the things that are important you know if that needs to be tailored to be you know and pivot to be more specific to sectors and then we dedicate that bandwidth to it while we're still doing public outreach we can do that so that's the advantage of having the budgetary item for outreach is that we can tailor it to what you think you need for your area as well as any you know recommendations or suggestions that you have beyond that so I just wanted to kind of tee up with that and you know hopefully have you know just a little bit of brainstorming here but really kind of work with you after this meeting to really deepen our understanding of what that pathway would be barriers opportunities and then come up with some again some goals for adoption to go even farther than we have so far. Excellent this point we'll be looking for any comments from the advisory board either on the chat and or in the room. All right excellent we'll start with Jack. Jack. Hi Jack Anderson here representing the Cal State University system I one of the things that that I was thinking about and since our some of our last conversations is is you know it seems like you've got to kind of tackle this from two ends more one up let's say a tactical standpoint and then more on this strategic standpoint and it's you know one of the things that's you know with higher ed students they're very very tech savvy but what we've been learning about in some of our especially recently in the last two years with some of the challenges on the campus the students really like and want face to face contact even though they are tech savvy they grew up with tech they do you know what we've found is is with some of the campuses and some of the hybrid situations they clamor for the face to face so I would just encourage you I mean there's in the CSU system there's you know nearly half a million students, faculty and staff there's a big you know pool of people to for outreach at that I would but I you know it's I think the newsletter blasts and stuff like that that does work that maybe as an introduction the other thing I was thinking about which I think could really dovetail right into your what you're looking at here is to outreach to maybe some synergy with some majors with some specific majors such as civil engineering or something along those lines where they can actually be your partners on the campus and help promote you know when you have like an engineering you know display day or something like that it's just throwing it out there but what we're finding is that even though that you know we're in this high tech mode and oftentimes which is virtual the students really more than appreciate and really want the face to face contact anyway that it's about all I wanted to just kind of say on that one. Excellent, thank you Jack. Laurie Pepper. Thank you. So I have a few thoughts. The first one is thinking about you know kind of not necessarily from the app adoption but looking at kind of system integration when you're looking at something like transit agencies and I know we're gonna get from Metro Lake and I'm very excited to hear their presentation but in the state we have hundreds we've been counting up between like six and 700 transit agencies, they are all independent and the vast majority of them have you know three or four people that work there so even if your title is general manager you're driving a bus so there is no time for business development, there are no resources to hire a procurement attorney. So what we've done through our California Integrated Travel Project is we've tried a different type of procurement strategy where the state will procure the hardware, software, procurement or consulting services. I shouldn't say procure, I should say we set up a master services agreement and all the transit agencies can then purchase through there so we're relieving as much of the burden from them that we can and I know it will likely go beyond transit that could take advantage of that but that is a strategy that if you know Cal OES and I will offer up the Cal ITP team to help you if you're interested whatever the hardware or software pieces of this that would need to be integrated for the system to set something up like that and it might have to be industry by industry. This is something where I think we can make it easy to get the technology out there. The other thing I wanted to recommend is looking at kind of funding guidelines for all of the different funding programs that we have where appropriate it might be interesting to see and consider, you know, prioritize scoring and stuff like that. So in order to kind of start those conversations I would recommend going to some board meetings commissioner meetings, whatever the appropriate kind of executive meetings might be to start that conversation. Obviously within the Cal State departments I'm happy to put you in touch with the right people at probably Caltrans, the CTC, CHP, High Speed Rail there are probably opportunities potential opportunities in there. So those are the things kind of tactically that I would say might get you kind of the biggest bang for your buck. I know you guys are short on time and staff. So I wanted to see what was trying to think about how could we make the most progress or make the most opportunity for progress with the least amount of work. Thank you so much, Laura Bepper. Next we have Erika Gonzalez. I just wanted to kind of comment on the toolkits. I appreciated the customization, you know, given the industry and the targeted approaches I liked the tailored messages and I really appreciated that they were available in seven different languages. I think that helps with outreach and making sure that we're kind of targeting and getting the word out. One industry and I'm not sure if it's included in the business kind of in the business bucket here but it strikes me financial institutions like banks and credit unions. They have, you know, a broad like reach in communities and that may be kind of a target for future outreach packages. And, you know, one of our, the departments to oversee is DFPI. I'm gonna be happy to make that connection helpful. Excellent. I want to turn over to the advisory board members one last time to see if anybody else had any discussion. Okay, Brian. I just want to know, how are we doing in getting people to actually download the app? We're talking about where we're going, but but do we know where we are and what's our goal in getting number of people? So we have over 1.8 million downloads and we continue to push that in our outreach and education. You'll see in a moment here a couple of the events that we specifically have targeted downloads for the My Shake app. That's one tool in the toolbox and the system integration is kind of, it's the more nebulous and it's industries, businesses, services, integrating automated actions like rolling up doors at fire stations or flashing lights and PA at schools and things like that. So those again are other tools in the vast toolbox which is education and outreach and earthquake early warning. So we don't have, we are developing goals with intended metrics for meeting some of that. We just haven't gotten them solidified yet. Our focus with those goals is going to be to target these particular industries just because they're early adopters of the earthquake early warning technology. But that does not mean that we won't be also reaching out to other sectors to also integrate. Tina? Yeah, I would just add that we did actually set kind of early on when we developed the app. We thought that four million downloads was a good target, 10% of the population and we're below that at 1.8. So that's still something we're reaching for. However, if you factor in that My Shake is not the only way that the public is getting alerts because Google, as we've talked about before, has placed it into their operating system. So that just expands, if you figure half-ish phones or Google slash Android, I know other, San Diego has kind of merged this with theirs. So I think that we're way beyond that if you kind of factor in all those things. But it was also important for us to sequence this. It was important for us and for the director and OES is kind of the owners of this program that the state family needed to show a commitment. So 200,000 employees, many of them have cell phones that we needed to walk the walk first. So that was very important for us. And while that doesn't make giant leads in the numbers, it's important for us to demonstrate that commitment. And I think if the entry point to the kind of next broadening is as employers, we take a look at our workforce and who have cell phones and who could download this today, not just for personal, but as a workplace safety, perhaps that's a starting point that's comfortable as we kind of evolve towards the more sophisticated. And I think it was Lori that was, I mean, absolutely. I think, and I know USGS and the partners in the room, they live this every day. I would imagine a question, especially for smaller organizations, is this, well, can you just tell me what to buy? I mean, it's not, they're not gonna necessarily engineer something, there's going to be an appetite at a certain size of a organization for just a thing that's manufactured that can be installed. I know that, for example, the fire services and public safety, the commonly, or at least more commonly understood technologies like the bay doors, elevators, and so accessing and outreaching through those sectors, like engineers and people who design those types of things could be a way to go too. But we also know this has got to be multi-pronged all at the same time, but we just want to be thoughtful and sequence it in the right way. But certainly, we know that we can go a lot farther with just even the public uptake with the app to continue to increase the uptake of that. From the natural resources agency side, we have one of the most public-facing organizations outside of DMV in state parks, and we'd be glad there with the director Armando Contero. And then, as the summer's coming along, it'd be good for, you know, parks and they get information about parks. We could also share information about how to work out how we do that. And do you guys have posters with QR codes or something like that we could send out? Great suggestion, thank you. Yeah, this is actually a really good segue for us to be able to watch one of the videos that really kind of highlights successful implementations within California. So will we actually be selecting the Los Angeles Unified School District implementation? And it's just a quick 32nd video that really kind of speaks for itself. So I won't belabor it, we're gonna get it set up and it will be through Zoom. I will note that because of the Zoom, it will degrade the video quality. So apologies for that, but you'll still get the full benefit of it. And you can go onto the website and see that video and others that we have created for various users of Earthquake Early Warning. Are we, we're running a little bit behind so we're gonna show only one video. As we know with earthquakes, it's a matter of when and not if. Well, we always like to be the gold standard when it comes to safety issues and Earthquake Early Warning is no exception. So what Earthquake Early Warning does for us in the schools is it allows us to take a protective action sooner than we would. So everybody has an opportunity to drop cover and hold on before the shaking even begins to start. And that is going to save lives and prevent injuries. So this video kind of really is a little bit of a teaser of the bigger project that LA Unified has and really we can call out other projects such as Menlo Park Fire District that has automated their bay doors upon Earthquake Early Warning alert or Cedars-Sinai Hospital or actually right now, this is a perfect segue for us to be able to highlight another project within California which is one of the more advanced implementation projects occurring in the state by one of the largest commuter rail systems in the nation. This project no doubt will lead to live saved and a more resilient commuter rail system for MetroLink. So we'll turn it over to Luis Carrosquero. We're gonna queue up the PowerPoint and Luis we will advance on your behalf just saying the next slide. Thank you, Luis. Okay, thank you very much. Good afternoon everybody just doing a mic check and everybody hear me? Copy that. All right, perfect. So yeah, good afternoon everybody Luis Carrosquero Interim Deputy Chief Operating Officer with MetroLink also known as Southern California Regional Rail Authority and I'll be presenting our EEW implementation with our positive train control system. Next slide please. Next slide please and I'll just start off with this map. Sorry, one back please, yes. Okay, so MetroLink is the nation's third largest commuter rail system. We are made up and we're governed by five member agencies. So that's San Bernardino County, Ventura County, LA Metro, Orange County and Riverside County. We operate seven different routes with 62 stations and over 535 route miles. We are host, in other words, we dispatch besides our trains, BNSF and Union Pacific freight trains as well as Amtrak passenger rail service. And we are attending on or in other words we operate on other railroads territories which include the BNSF, the Union Pacific and North County. Our total dispatch or hosted trains is about 325 currently and as far as our positive train control system we deployed a system wide on all of our tracks back in 2015 and we completed the deployment across other railroads, partner railroads by the end of 2018. Next slide please. MetroLink's EEW project automates the stopping or slowing of trains by developing what we call the commuter railway seismic interface or Chrissy to integrate USGS shake alert notifications with our PTC system. So part of the grant and part of the project that we enter was to identify a pilot territory which we identified as a Paris Valley line subdivision. There were various reasons for that. It is close to one of the faults in Southern California. It has relatively small traffic. We run early in the morning and late in the evening but not a lot of traffic in between. So we figured it'd be a good test bed as we developed this, tested this and then we looked to expand across our other territories. Part of the grant and the project included also updating our earthquake response procedures for train operations and field inspections, improving inspections and return to service, prioritizing the inspections based on where the shaking intensity is felt and acid data as opposed to just taking a global radius and epicenter from distance from the epicenter. We would also train our train engineers or train conductors or train dispatchers and our support desk with this new technology and just some information as we were, this grant was funded by a Caltrans Division of Rail and Mass Transportation for 4.87 million. Next slide, please. So how are we leveraging the shake alert and we're feeding it to our PTC? So we already know that through shake alert there are sensors throughout California. It provides detection for earthquakes. It calculates various information including magnitude and epicenter but it also provides the MMI value which we are leveraging and we are then receiving that information. We developed this Chrissy application in the middle. So what it does is it receives this information from shake alert. We established rules for which we would set triggers as to when we alert trains based on the MMI threshold and then we would also then build some logic to be able to determine are there any of our subdivisions tracks that are impacted by the earthquake? Are there any trains at the moment that need to be alerted and then provide the necessary alerts to our maintenance of wave personnel and our dispatching operation center? Next slide, please. So I'm sure everybody knows this but I'll just kind of cover this. So USGS Shake Alert is currently available in California and other states besides California. As far as what we're trying to leverage, we have our P waves, the compression waves which are the first waves to be detected by the sensors before the S waves which are considered to be stronger shaking or the ones that could cause the more damage. Shake alert estimates shaking at grid points across the region and then sends a notification to our subscribers. But the key factor for us that we're trying to address or beat is the amount of advanced warning that we send to the train basically varies based on factors including proximity to the train, soil, geographical features and severity of the earthquake. Next slide, please. All right, there's a lot going on in this presentation but I'll try to encompass the entire system into this one single presentation. So the way that this will work is we have an event which is the earthquake. Then USGS the sensors detect the shaking, the intensity of the earthquake at various locations throughout the state. Shake alert would send that alert to us to the Chrissy application that we have built and then Chrissy does several processing tasks. So one of them is it determines which sensors in the area reported the shaking. And then it then cross-references where are our subdivisions? So in that top right picture, the black line is the fault and then the red line is what would be our metro link line. So we would know that certain segments of the subdivision are impacted more severely than others. And then based on that, we add on are there any trains that are operating at the moment that this alert was received as well as what are the MMI values that we are receiving and what is the appropriate action? So what we have on the bottom of the page is the MMI scale and based on analysis and trying to not send a false alerts to trains, we established different thresholds in which we would send different instructions or alerts to the trains. So what we determined was that if we were to receive an alert with an MMI value from 3.5 to 4.5, we would send an automatic informational message to the train via PTC, which would just basically alert them saying, hey, an earthquake was detected. If you're feeling shaking, notify the operation center. That will be the equivalent of a minor earthquake or end, but if it's even less than 3.5, then we wouldn't send anything out, which is what we have seen fortunately, not going to would since we've deployed the system. Now we go into more of a moderate earthquake in which the MMI value is 4.5 to 5.5. Then what we will send is a mandatory directive to slow down to restricted speed. So what that is is it would, the message through PTC would send a message and the system would be able to warn the engineer that they have a certain amount of time to comply to the speed reduction. If the engineer does not comply with the speed reduction for various reasons, they're distracted, they're incapacitated or whatnot, then the purpose and the objective of PTC is that it will apply the brakes automatically without any intervention from the train engineer. And we apply the same logic that you have a severe earthquake. If we get an MMI of 5.5 or above, then we will send a mandatory directive to stop, in which case we would, as soon as the directive is received by the train through the PTC system, it would apply the brakes. The one caveat is that we do also have to take into consideration that we don't wanna stop the train inside tunnels under overpasses or bridges. So we're constantly monitoring the position of these trains. And when we do get that alert, we know if we're able to apply the brakes immediately or whether we need to wait a couple of seconds before, because the train is in a bridge or in an overpass or in a tunnel. But in a nutshell, that's what we have been able to develop through our system. Next slide, please. So this is just kind of reiterating what I was explaining on the different MMI levels and the different actions that we have for the trains from no advisory below 3.5 to then the minimal earthquake shaking to moderate to then severe, highlighting the no stopping on bridges under overpasses, no tunnels into contact operations. Next slide, please. So along with the functionality of slowing or stopping trains automatically when an earthquake is felt, we also generate automatic reports that we have to send over to our dispatching operation center as well as our maintenance of wait personnel so that way they know which areas of the rail are impacted, which assets need to be prioritized. And we also include maps. So this is just a snippet of kind of what we've been able to build. So the red dots are the different sensors that we are leveraging for the Paris Valley line subdivision. The blue line is our track, the Paris Valley line. The green icons are representations of the different trains that are in the territory at the moment that we receive the shaking. And then we have the ability to generate geofences for grids for the sensors that we're to receive information as well as the geofences that we're able to prioritize inspections due to the severity or the possible impact on the train. Next slide, please. Okay, so as far as the project status, we were able to develop the system. We were able to develop software. We lab and field tested it. We deployed it to production to the Paris Valley line subdivision, the initial version, which was just a notification without an enforceable bulletin. But recently we have successfully been able to deploy what we are calling the final version, which is PTC receiving this information and applying the brakes automatically on the Paris Valley line subdivision. And our final two bullets is basically, we're now mapping the rest of our subdivisions so that way we can expand this across all of our lines and also be able to leverage the lines for which we don't own, but our trains operate to still notify or warn engineers if there is an earthquake that is detected in their area that could impact their operation. Next slide, please. And that would conclude my presentation. I'd be glad to answer any questions. All right, as I'm looking at the time, we're obviously a little short on it. I'm gonna give the opportunity for the advisory board to ask any questions of Louise, but we will have to make a decision as to whether the advisory board will wanna take up the next presentation, which would be the education and outreach presentation that we have for everybody. Or we could further discuss not only the system implementation, but also the MetroLink presentation. So I'll defer over to the board for questions or comments. We'll start with questions on MetroLink. Hi, it's Tina. Thank you for that presentation. And I may have missed this. How many have you actually had some earthquakes where you've employed the train slowing slash stopping? Luckily, none. So to kind of put that in context. So we have been able to, we have the ability to simulate earthquakes. We have a relationship with USGS and ShakeAlert in which we're able to simulate an earthquake with whatever magnitude at whichever location so that we can test that the system is properly receiving alerts and is able to send the necessary alerts. But as far as a live non-stimulated earthquake, luckily we haven't received any that have met a threshold above a 3.5 MMI since we've deployed the system. Do any board members wish to ask a question or provide comments in the room or virtually? If you're online, please indicate it in the chat feature and the moderator will unmute you. I wanna turn it over to Amina. Amina, I know that you had a comment that kind of was related to the system implementation aspect. Yeah, thank you. So I'm with the UC and while, of course, a big part of what we do is house and educate students. Equally big part is research. And so I was gonna recommend maybe calling research out as its own industry. Obviously, we're not the only ones that do it, but we have a lot of high value research and some of these mitigation strategies, these applications could be written into grants and funded that way through the grants and as a way to protect the research. But obviously there's other research entities that could benefit from having their own toolkit and outreach package. Thank you, Amina. That's a great point to raise. Any other comments or questions from the board? Well, the comment is now open. If you wish to make a statement, please let us know in the room. If you are online, please indicate in the chat feature and the moderator will unmute you. Hearing none, I'll turn it back over to the board as to whether we wanna hear the next presentation, education and outreach, or if we wish to table that for the next board meeting so that we may be able to further discuss system implementation if any of the advisory board members have any further comments or points that they would like to raise. I'll just make a suggestion. We have three minutes left. Obviously that's not enough to cover what you were planning to, but maybe can you hit Yvonne or whoever? Can you do the 30-second just highlights of what can be expected and then we can maybe follow up with some written materials to the board. Is that okay with everyone? Okay. Give us one second while we queue up to discuss. Thank you. Hi, everyone. Yvonne Dorontis, I am a senior emergency services coordinator on the education and outreach team. And so in the spirit of highlighting some of our successes from our last meeting to today, we did have our April earthquake preparedness event this year. And so April is California's earthquake preparedness month. And so in the spirit of that, we did host a tour throughout different cities in California. And these cities and events were handpicked by COES and specifically picked due to either high earthquake risk or vulnerable populations. We also targeted both English and Spanish media. And we really made it an effort to reach as wide of an audience as possible. And so as you can see on the slide, here are some of our key metrics, which include from that week, over 10,000 My Shake app downloads an equivalence of 1.1 million in ads. And we also, you know, we're able to do a lot of coordinated messaging and partnerships with our end users. And so I do just wanna highlight some of our stops. And so we did have in San Diego, some individuals come who had heard about it in the news earlier in the morning. And so we're able to come check out the earthquake simulator, which was really the focal point of the tour. And so the earthquake simulator served as a very fun experience for people of all ages to be able to ride it and get a sense for what an earthquake might feel like. And so we were able to have students, seniors of all ages and the reason why the earthquake preparedness event was scheduled during the first week of April was in hopes that families would take advantage of it during the entire earthquake preparedness month and start those conversations of family plans, evacuation routes, what to have in your emergency preparedness kit. And also just so people get a sense of where they live, we were able to talk about different fault lines, we were able to discuss some of their hazards in their community. Next slide, please. Something that kind of really struck out to me was in Salinas, which I'm actually from and the average household size is approximately 15 people in the community of East Salinas, which is where our stop was at. And I had an individual ask me if it was earthquake weather and that's why we were promoting it. And so I think that really speaks to the importance for these events and to be able to educate individuals on, we have over 10,000 earthquakes in California every year and we can expect one at any given moment. And so it's really important for everybody to be on the same page and know that the safest thing to do is to drop cover and hold and to really leverage our current day technology, which is a My Shake app that allows us to get those life-saving seconds to drop cover and hold. And so here are some of the pictures you can see, a little kid there kind of enjoying the ride. And we had a system in place in which individuals would ride the simulator and then come by our booth to be able to get additional information and resources. Yeah, and so that's kind of our key highlights. Well, thank you, Yvonne. We do have a comment from the chat from Jack Anderson out of the California State University System that he does believe that the outreach programs on campus will be the most attractive to students representing the universities. With that being said, Chief Deputy Director, would you like to provide any comments, statements, any closing statements? No, just kidding. I always do, we're a little over time. Thanks for bearing with us. This was a really very helpful, not just the updates from the team, just great appreciation for all that you do every day, but also from the board members. You teed up some good ideas. Keep them flowing to us after this. We'll definitely be reaching out to you to kind of build out this roadmap for what comes next. And I think that we can plan on another meeting and three months-ish from now. We'll hope that the fires and all the other things that happen in our lives are not as daunting as they have been the last couple of years, but we know that things get real busy for many of you as well over the summer. But just look forward to your feedback and continued engagement. Again, if there's anything you can suggest on how we can improve or make this program better, please, please let us know. But thanks for your time today. Thank you. Do any board members wish to, you know, do a final comment and or statement? If you are online, please indicate in the chat feature and the moderator will unmute you. Final public comment is now open. All comments will be limited to three minutes per person. If anybody has any comment, should you like to comment, please indicate that in the chat function of the video if you are virtual or if you're in the room, feel free to speak up. Seeing nothing. Thank you all so much. Sorry for running a little late. We are adjourned.