Hi, I am Dr. Shrikanth, pediatric gastroenterology consultant at Manipa Hospital in Banyur. So today I am going to talk to you about pancreatitis in children. So we will see what exactly is this pancreatitis, why it happens, how to diagnose and what are the treatment options available. So pancreatitis is an important organ in the abdominal cavity which helps for two things. One is to digest whatever and second thing is to produce insulin which controls the glucose balance in the body. So this is an essential organ inside us and when there is swelling in the pancreas, this organ and we label it as pancreatitis. So if it happens suddenly for the first time it is something called acute pancreatitis because of some unfortunate reasons it can be removed. So then if it is happening again and again so when it is called as acute different pancreatitis and because of these problems if there is any permanent damage in the pancreas like formation of stone, the dilatation of the ductile system in the pancreas then we label it as chronic pancreatitis. So these are the different types of pancreatitis which you see in children. One of the important reason is an infection. So it is not very scary because they completely recover out of this infection. I would say it is good to have infection as a reason for pancreatitis rather than anything else. Apart from that children can get injury or their abdomen either they can fall and get injured or trauma or any other reason. So then they can get the pancreas damaged. Various other reasons like we label it as metabolic problems and genetic problems and if there is any structural problems like if the pancreas has not developed properly by birth. So these are the various reasons why children do develop pancreatitis. So how do we diagnose it? So there are various test and blood investigations to help us and the imaging of the abdomen either MRI or CT scan or simply an ultrasoundography of the abdomen can help us exactly diagnose the pancreas. So let us see what is the treatment option for pancreas. It depends what is the reason. So here exactly finding out the reason is important because that will guide us about the treatment and also it will tell us what is going to happen in the future in terms of pancreatitis. Whether it is going to repeat, whether it is going to resolve completely or whatever other course it would take. So this is how we get to know and after that genetic causes has become one of the important reason for pancreatitis in children and with advent of genetic diagnosis we are detecting more and more genetic reasons as a cause for pancreatitis. So these are the reasons for pancreatitis but for certain reasons there is treatment but for certain we do not have any specific treatments but we can adequately manage with various procedures. So in treatment of pancreatitis one of the important procedure is endoscopic pancreatic duct strengthening for certain congenital reasons. So yes it is important procedure which is done here and it is going to give good results for many of the reasons of pancreatitis and most of our patients who have undergone this procedure because of various means of pancreatitis are doing excellent. So I would assure you that at Manipal we have a great team to perform all this procedure first of all to diagnose exactly what is the reason for pancreatitis and also exactly guiding about the future course of pancreatitis because unfortunately if it is not treated properly there is a risk of permanent damage to the pancreatitis and also damage to the insulin producing cells which can produce diabetes also. So I would caution you that not to neglect pancreatitis but get adequate treatment in a timely manner so that a child can get the best care at appropriate time.


control. Here we go. Nice start off that inside gate. They charge in the first turn and the other three riders have disappeared off to the safe defensive duty. It's cleared off once again. It's bike time. All he wants to do is ride his bike and just look at that start. He makes the bike, doesn't lift, just goes forwards. Everybody else goes across the track. The water is on and we're off and running. It's Jason Groll. Comes out of gate number three. Smashing start from the Australian. Woffendon comes through in second place and Frick has come round the outside of Robert Lambert. One, two, and four. One being the most advantageous, but three statistically not so good, but Jason Groll really pulled clear on the way to the corner. Green light comes on and away we go. Holder's made a great start from gate number two. That's a smashing start from the answer. Dudek roaring round the outside. What a move from Dudek. Brilliant stuff from him. He was a little untidy, but he got the grip. The first turn for Patrick Dudek. Jack Holder initially makes a good get away from gate two, pulls clear of the pack, but Dudek just realizes he's got a lot more traction around the outside. He gets a war. What a move from Smashing. That is that run round that first corner rid that we've become accustomed to seeing. Yeah, we've got Dan Buely on the inside. It looks like he's made a pretty good start. He's run clear there, but Smashing has been watching the monitors, he's been watching every race. He knew where the speed was and where the grip was. Just got himself there just ahead of Ty Woffendon. Ty not able to get there early enough to put the charge and move. Smashing over too far and that just gave him the perfect run.


Bismillahir Rahmanir Rahmanir Rahim. Welcome back to Corporate Governance. We've been talking about various dimensions and now we are going to be coming to the close of corporate governance. We've seen that how different factors, different schools of thought, different dimensions, different frameworks, different aspects, different institutions, and how the world is basically clicking, how the world has changed in the past 20 years, and how it has drastically changed in the past 100 years. The dimensionalities of corporate governance are more virtual than real anymore. The large corporations manufacturing powerhouses like General Electric and like the three automobile companies of Detroit and the manufacturing concerns around the world have actually been diminished in size by the virtual world, by organizations which are more futuristic in design and more futuristic in context and are more out of the box approach towards business and business dynamics. We've also seen that corporate governance, the models of the UK, the models of USA, the European models, and the far Eastern Japanese model, and then again in Europe, the dominating basically German corporate model, all of these models have their own nuances, have their own intricacies, have their own assimilation of the local context of business. But yet now it's a globalized world and therefore there is a great need for convergence of corporate governance and a more international language which can be understood by all corporates while doing business. So therefore the future of corporate governance is a completely different ball game altogether and there is a need to bring that convergence together and that adaptability by all of the different regions, all of the different continents of the world and finding out a common language which is implemented by corporations at the small level, at the medium level, and also at the large level. Now, ladies and gentlemen, when we see the future of corporate governance, each of the systems is facing pressure to change. The long-term stakeholder orientation of the German and Japanese systems is under insistent pressure to deliver shareholder value, particularly from overseas investment institutions. So now what we see is that there is this cross investment taking place. It's not only the national investment which is taking place, but national economies are now overwhelmingly being invested by global investors and these global investors have their own expectations and also want to be able to understand the language of business in each country and ensure that their investments are safe and in that safety net, they want to also ensure that best practices are being followed which can be implemented or replicated around the world and they can implement or replicate their own systems, their own value systems under a corporate governance umbrella. We've seen that the Anglo-American approach is itself being challenged by international national and community agencies to recognize wider social and environmental responsibilities. Look at what is happening now. We see a huge flux of climate change. We see weathers changing. We see terrains changing. We see crops changing. We are seeing how different communities are being changed due to the uncertainty of the environment, of the climate and again, the challenges of the environment of the future. Wars are going to be fought over water. How is all of that changing? What has to be done to recognize these environmental responsibilities and also social contributions? These are extremely important and they have to be made a part and parcel of a corporate frameworks. Within the corporate governance models and again, we have to see that how these organizations can individually and collectively combat these challenges, these uncertainties of the future and that is becoming very, very important. The German and Japanese systems are faced with demands for increased transparency and disclosure. If we look at the future and a future model could be as one option, a unity system as there is strong convergence towards the global system which assembles the best elements of both major governance systems and combines them together. So again, we are talking about the combination of best practices, finding out what is the best implementable practices in one system and in the other system and in this case looking at the Far Eastern model and the European model and then putting them together and seeing that how they can be implemented by countries across the world. So that could be one viable option. Now, if we look at the Anglo-American model then we see a universal market-based system as anticipated by the Chicago School of Financial Economics representing the triumph of the rules-based outsider system. So now the second option is is that we define the rules which are universal rules and then again through third parties ensure that they are being implemented by different corporations and they are being followed without any discrimination or without any misinterpretation of the rules and the regulations and that could be another form of this or we could even combine the future option one with the future option two that we can look at the best of the two systems the European and the Far Eastern and then also look at the rules and regulations which you see in the Anglo model and the Anglo-American model and then put them together and find out the best possible framework which can be followed globally and then also ensure that within them we have the social and the environmental factor so that the future generations are saved and we can save our planet from the vast disasters of the environment and of the climate which already we are feeling and that again is creating huge challenges for nations, for corporations, for societies and for communities and also for individuals that that is the future and we have to find out the best way possible and then go for its implementation across the board thank you so much


I was just speaking in San Francisco last week and they were less mellow than you guys. So let's try that one more time. Good morning. Good morning. Morning. Much better. So good morning. My name is David Blank, gentlemen. I am the technical evangelist for a company called AppSera. We're a company out in San Francisco that, in case you haven't heard of us, makes software that DevOps love because it lets you take whatever workload you want in the public clouds and privately move it around, have a policy thing and so on. But that's not what I'm going to talk about. What I do want to make sure to do is because the thing that I tend to hate the most is technical talks that are really marketing talks. I can't stand them. I don't know if anybody here has the same despise of them as much as I do. However, it is the case during my talk that I would like to say a couple of things that might possibly be construed as a marketing-like thing. And so here's what I'm going to propose I do. I have these three wooden blocks. I'm going to put it up here. What I am proposing to do is any time I say anything that sounds like a marketing-like thing, I will take one of the blocks away. And this is my total amount of things that I could possibly say to this market. But you know you're not going to get an entire marketing talk. Now I'm only going to do this if the audience agrees this is a fine compromise. Are you cool with this? Yeah. Yes? OK, good. Then let's go forward. So I think the thing we need to do is we need to start at the end. What I want to do is I want to start at sort of the idea of what's a production environment? What's crucial in the production environment? To my mind, production environments are kind of all about trust, right? Because you have to figure out, like, what are the things that I'm running in my production environment, you know, from a software perspective, and et cetera? You've got to kind of understand what can the things I'm running consume in terms of resources, CPU and disk and network bandwidth and that sort of stuff. You probably want to know where is my workload running? Is it running in this data center? Is it running in Sweden where it can't be because of data protection laws? Is it running on the machines that have a high memory? Is it running on PCI certified machines and such things like this and that sort of stuff? So you probably care about where it runs. And finally, and probably one of the things that comes up when we talk about security, like the last talk, is what can that thing talk to, right? Can it talk to other workloads? Can it talk to the big bad internet? Can the big bad internet see it often in production environments? This is considered bad, right? So, and I think that there's nobody in the room here who would disagree with the sense that the bigger the production environment, kind of the harder it is, right? If you have more dots, keep you making sure all the dots connected properly tends to be trickier. So here's what I want to do. And I want to also say, by the way, this is something else that we've all found out is that when you have multiple clouds, it tends to be super hard. So here's what I propose to do. I want to tell you my answer to dealing with this sort of stuff. But my answer unfortunately has sort of, let's see, there should be sound in the answer. I'm going to change the sound. Oh, there it is. Can you pop this out of it? Oh, I can. I'm not sure we can. I think that's on the answer. So the problem that I have is my answer to this sort of thing is a word that typically gets associated with sleepy time. And here it is. We're now like in the middle of the morning, your caffeine has started to warm up. So I just want to warn you about that. Yes, I'm sorry. See, you're already joining. So the thing that I want to talk about is this little word here. And if it's a little difficult for you in the back to read, it's this word. Okay, so this is what I want to talk about. Now the tricky thing with policy is when I say policy, most people think about these awesome books like the CDP, Security Policy, Procedure Handbook, which is riveting. I'm telling you, but we should work with a movie. Marketing? I'm not marketing for CDP. Too late. Handbook, you know, like the fiscal handbook or maybe your employee manager, right? So the thing is, is that typically when people get into the policy realm, they think that it's like this, right? If you've ever been in a meeting where your company is deciding policy, it either looks a little bit like this, which happens to be the U.N., or let me just do a quick show of hands. How many people in this room have been in a meeting about policy, per se? Okay, did that meeting look a lot like this? Roughly? But so what I want to do is I want to tell you that policy can be a lot sexier than this. And if you don't believe me, here's a slide which is actually from our graphic artist who's saying that this is what policy looks like. But I don't find this sufficiently sexy, so I'm going to do this. Okay, so I just want to be clear. Is this now sexier? Okay, great. So here's the thing. When the car reporter is smiling, that's a good sign. So here's what I want to give you. I don't call it a jazzy. So I think that probably your environment looks a little bit like this, right? Where you're trying to move down this road, you're going straight down this road, or maybe it looks a little bit more like this, or, I know this sounds like a car commercial at this point. Or it's a little bit more like this, more like that, or chances are your environment actually is more like this, right? And so one of the things that I want to point out about this and about these pictures that you may or may not have noticed is these things over here, these white and red things. What are they called? Guardrails, exactly. So here's the thing. My assertion is, is that if you have the proper policies in place, and we're going to talk about that, that you can put these guardrails up. And what happens is that the people that need to use your system can go as fast as they want, and you can sleep at night because they can't do things that I'm supposed to. Now, here's my goal. My goal is to make, is to sort of make you guys rise up. Rise up with your pitchforks and your torches and demand policy from your tools, from your redenders, from everybody outside who is sponsoring the conference.  And just because I know that you're an awesome peak audience, where does this fly from? Where's this from? Young Frankenstein. Somebody is from London. Young Frankenstein, yeah. See, this is why I love the DevOps crowd because they know stuff like this. Okay, so what sort of things am I talking about? I'm starting talking about these awesome scenarios where somebody comes to me and says, it's 2 AM, you know, the developer comes to you, and I'm sure more member will make whatever I'm working on work better. I mean, that's lots more memory, you know? Or is there malware in a public Docker image? What malware? Like for example, if you go pull down the MySQL official image from Docker Hub, it's got shell shock in it. Awesome, let's put that in production. Or the containers talking to who knows what, right? You know, nobody knows. You know, nobody knows. It shouldn't be doing anything at all. Or, hey, I can't believe how timely this is. If the newest OpenSL, XSL exploits some sort of combination of gruesome and fluffy, right? This is basically the new version of it.  Whatever it's called, I don't know what the latest one can be called. Or what version of Java are we using, really? That one, or who has the database credentials, and what can I do? Right, these are all these things. So the way to start, I think, thinking about this, is to look at your environment and figure out where is the policy now. And in my experience, in environments, policies are in one or two places. Either you have a department or a person or whatever whose job it is to make sure that you're in compliance and that the policies are being followed, right? And they look a lot like somebody at the border? Yes. Now, the tricky thing about this scenario is it means that everything you do is maximally frictional, because it means that you have to do a mother-may-eye every time you want to do something, because it's going to go through this person or group of people. And that group of people doesn't scale, because they're people. So that's kind of probably it. Now, the other place that you typically have is what I would call sort of the Wild Wild West, right? Where we're in a company and anybody with a credit card can get more resources. Now, if you have spent any time watching any Wild Wild West movies, you're very aware that invariably somebody catches a stray bullet in the middle of the movie, because, well, we didn't properly buttress the things in the mines, the mine fell down, or we forgot to back up that database, because we weren't following that procedure, that sort of stuff. Now, often what happens is you have this awesome combination of the two things, where you have, OK, it's too annoying to go through the compliance or whatever it is doing in the security or the stuff, so I'm going to go out and make my own little shadow IT thing. And guess what? The shadow IT thing goes a lot like the Wild Wild West. And so you and your environment have both things, and yay, you win. It's the worst of both worlds. So what would be better? So one thing that would be better would be to make sure that you have some sort of policy system that is pervasive, explicit, so you can say what you really mean and make sure it's taken care of. And we'll talk about that. And this is where the Robocop picture comes from. That's cosplay Robocop, so it's not copyright school. You want to make sure that it's automatically enforced, because any sort of policy system that requires a human to go, yep, this was fine, is not the one you want. You shouldn't let the machines do what the machines do well, but make sure that the people do what the people do well and don't confuse you as a person like Google, Todd Underwood, said, let's stop feeding blood to the machines. And I really, really believe that. So let's talk about what it means to be enforced, where you have to enforce it. Well, the easy one is what we talked about, right? We talked about resource limits. You want to make sure that you can say stuff, and this is where you see most often about is your only allowed to consume this amount of CPU or memory or just spaced out sort of stuff, right? That all makes sense. We all kind of understand that implicitly. It's kind of important to be able to specify what can talk to what. And here's your little tip on that. It's important that it's per port, not per container VM or container VM or whatever, because it's not uncommon for people to say, okay, cool, my app has to talk to my database servers. I'm just gonna put the connectivity to the two of them. And so congratulations now I have this awesome, transitive trust thing, this bi-directional trust where I say, oh, they can talk to each other. Which means that if, for example, the SQL, you know, the database server gets popped, it can have all the fun it wants attacking your app container or VM, right? Because you've set up this nice bi-directional trust fully there. My assertion is you need to be more granular, is that sort of thing. And per protocol as well, in theory. Okay, it's also important, as you can probably guess, to constrain whether from a workload you can talk out and whether things can see yet. And if in fact you're using containers, as many of us in this room are, and you have the thing where containers can come up and down where they want, you need to be able to say, oh, well the service that is using that container has this URL, you need to be able to make sure that when you move the container from here to there, the URL points, you know, gets pointed in some way to the right way. And that makes sense. It multi-cloud and stuff like that. Software components and version control, it would be really super swell to be able to say, from now on, we are only using Java 1.9, 7, 12, whatever it is now, right? It would be really swell to be able to say, anything that is running this current using 1.7, that's fine, but from now on we only allow 1.8. You need to be able to say something about what kind of things are being run out there. Similarly, you need to say things about deployment. It is only possible, and this goes towards the previous talk, you want to be able to have something in your deployment pipeline that says, do not deploy anything that has any known vulnerabilities. Do not deploy anything that doesn't pass their scanner. It's perfectly reasonable. You're gonna want to do stuff like that, so you need to control your deployment pipeline. And here's another tricky thing that I think that comes up, that people don't think about it until they are forced to think about it. So you have a situation where you have a developer and she's writing some code that goes and does some database access and having a hard time, it's not working. And so she comes to you and says, hey, can you show me the logs from my application? I really need to see them. And so you have a few choices. Choice number one is, give that person access to your database server. Here's the SSHDs go for it, right? Anybody in the room like that option? No? Other possibility is, okay, here's a copy of your logs, but that's kind of static, right? Because then you write it on a query, so that kind of stinks. So really you need to come up with a third option that allows you to be able to say, let me stream your logs so you can see your logs, right? That's kind of crucial to come up with some services in the long run. Otherwise you set up bad things. And because we're talking about policy, it's also crucial who can actually edit it. Okay, and I'm gonna say this one. This one is gonna allow me to take one of these away. Is that okay? Can I agree? Can I get the agreement? This is fine? Yes? We're gonna say one thing, this is not the major thing in that app series, but one thing that we do is kind of cool that I find fun because I like to talk about it. So one of the things that we do is we will, if you're having, say, an application talk to a database server, we will set up something where when you set up this connection, we'll stick something in the middle, an inline component. They don't like me saying man in the middle because that makes people hear. But let's just call that an inline something, or a man in the middle, but we all understand where your application talks to it, it talks to the real database. And the thing that you can do with that sort of scenario is a few things. One, you can do this ephemeral credential thing where my thing in the middle will hold the real credentials for the database and I will give these fake credentials that are only good for the connection between it and the thing in the middle for that length of that time to talk. And so that developer or that developer's source code repo or anything else can contain credentials, but they don't mean anything. And so it talks to that using these credentials and then it does the real thing and it sits in the middle. But that's not where it gets fun because if you can be in the middle of a conversation and I suggest that you think about this as an interesting paradigm, because usually you're shot away because it's usually in security vulnerability, you can do things like, hey, don't allow my application to drop any databases, right? If you understand the wire protocol for say MySQL and if you do, I'm so sorry. But let's assume you do understand the wire protocol. If you understand it, the application can say, hey, drop table, drop table, drop table, and you can just ignore it because you know what it's doing. All right, so there's lots of interesting stuff you can do, or you can introduce some artificial latency where you can avoid things like the Knightsbridge Capital story, so we're in the middle of New York. How many people here know the Knightsbridge Capital story? How many people don't know it? Let's try that one. Okay, so enough people here.  So Knightsbridge Capital was an awesome thing and you should go get the SEC report and if you don't, you can't find it, send me a email and I'll send it to you. Where they had, if I remember correctly, eight different servers that were doing high-frequency training and they managed to put the wrong piece of software in one of the eight. Then for about 45 minutes at very high speeds because that's what they did, it took, you know, the actual training took place except for this one here that was doing it wrong. And the one that was doing it wrong over here managed to take the valuation of their company down by 75% in 45 minutes. They had to do the bankruptcy thing and change their name and stuff like that, but anyway, so you don't need that thing. So you can just imagine that if you had something in the middle that was acting like a circuit breaker that that might stop stuff like that. Just an idea. Okay, so here's the question I want to ask you. All these things I asked about policy, what did I leave out? Come on, let's edit this slide together, okay? What did I leave out that you would want in a policy system?  Uh-uh. Say it. Say it. Excellent. Excellent. Next, please. What else do you need in a policy system to make it usable for you? Be useful. Say it. Be useful. Nice. I wonder what debugging in as well because for sure that's a hard problem. Two more. Documentation. Say it. Documentation. So you wanted to be semi-self-documenting? Sort of stuff like that, how do you do that? One more and I'll let you out the hook. Yes, sir. Impact analysis. Oh, I love that. I really love that. So in my opinion, there are five other things that you needed to make sure are in a policy system. Auditing off for mediation, troubleshooting you about getting documentation impact analysis. Just an idea. So instead of like leaving you like without a compass, not knowing where we're gonna go with this or where you can actually find this, let's talk about where you might be able to find policy systems like this. Now here's the sad news. You're not gonna find it necessarily from your cloud provider. AWS is a little further along as they often are in some ways in terms of being able to set policy around EC2 instance parameters and network typologies and stuff like that. Azure has actually done it better since I made this slide but prior to this time it had role-based access control with exactly three set roles. And if you didn't like those roles, you'd have those three roles. And if you didn't like those roles, you can still have those three roles, right? Google Compute Engine, this is obviously out of date, a little bit out of date, but still was this really awesome thing where basically it said, hey, if you have edit permission, congratulations, you can do stuff, which is not the granular you're looking for. And for both of you who have the pleasure of dealing with soft player, I don't know how many people do, when I asked them about their, where is policy in their system? They're like, well, the policies can be found in our web app GUI sort of thing. And so I went onto the GUI and counted the number checkboxes, there were about 70 of them. Not all of them were policy, but oh, you know, I'd say that's just bad. Okay, so how about in your platform? Anybody know what this is? Oh, you must know this logo. Somebody that's, I know this guy does. Yeah, right. So sorry, as far as I can tell, they're getting a little bit better along these lines, but at the moment, their policy, there isn't much policy to be there, but they're isolated and stuff that's getting better. This one here, what was this? Am I causing people to have traumas since this is what I showed these logos, right? Sorry, this is what? Loud open stack. App open stack. Okay, so not yet. So open stack has a project out there called Congress. And Congress' idea at the moment is you feed into Congress all of the events that go on in your open stack instance, and it will tell you whether something violated policy. And then maybe it'll do a remediation step for you, which doesn't sound like the greatest idea to me, but you know, maybe you like it. But anyway, it's not my favorite. This one, at least one person dressed up for my talk, I appreciate that. Yeah, so Kubernetes is the one that's a little further along because it's got things like the analytic constraint resource limits, where I just get quotas and stuff like that. And that's very cool. And I think it's getting a little bit better, stuff like that. And here we go, I'm pulling one more of these. Okay, one of the things that we spend a lot of time thinking about and happen to spend a lot of time is about policy. We have a fairly sophisticated policy agent and stuff like that. If you want to check this out, there's a URL then, I always check it out. Okay, so here I am coming towards the end of my talk. The key thing that I want to point out to you is now you have your own pitchfork, you have your own torch, and I would like you to please take these things and go demand policy systems in what you're using. And that's what I want to say. So that's the end of my talk. Oh, and the other thing I guess I probably should mention is, because I am kind of in the DevOps world, I did have an extra one of these just in case. So anyway, thank you very much. That's the end of my talk.


Hi, Charles. This is Ashley with Oxone Toyota. I just wanted to send you over a quick video greeting that way you can see who you are working with. Thank you so much for taking the time to speak with me about your recent interest in a new RAV4. Since you're going to wait until about July before you end up purchasing, please let me know if you need anything in the meantime. Feel free to give me a call. My number is<PHONE_NUMBER> or you can also email me back.


Mayor, do you have a mic check? We came through here. Thank you. Sorry, I had my mind turned down. I'm assuming you can hear me now. Yeah, we can. Well, it is four o'clock. I do recognize the quorum. Let's go ahead and get started and call the roll. Thank you, Mayor. Council Member McDonald. Here. Council Member Rogers. President. Mayor Rogers. Thank you. Thank you, Mayor. As a record show that all. Climate action subcommittee members are present. Great. Let's go ahead and start our day with our public comment for non-agenda items. If you have a comment that's within this committee's jurisdiction, but it's not on the agenda, hit the raise hands feature on your zoom. And I don't see any hands. We'll keep moving through our agenda. Let's go to item number three, department reports. We'll go ahead and. Announce both. We've got a department report item from Rob sprinkle, and he is the deputy director of traffic engineering. He'll be providing an update on the city's. Progress. For the compliance with electric vehicle infrastructure training program. We call it. For short. And he'll discuss the requirements due to recently enacted legislation. Rob. Great. Thanks, Tasha. Hi, as Tasha mentioned, my name's Rob sprinkle and the deputy director in traffic engineering. I also oversee our electrical division, which is why I'm here today in that capacity.  Back in February, Peter Martin brought forward the electric vehicle infrastructure training program or the V. E. V. I. T. P. Certification that's required under assembly bill. 841. And if you recall, the requirement. Is set up to provide at least 25% of the electrical staff. Having the certification when they perform. Service or installation on EV chargers that supply 25 kilowatts or more charging power. To. To a vehicle. So we're going to do the installation or service of these. And this is a requirement when. The funding is from PUC. The energy commission or air board. The city of Petaluma passed a little more strict ordinance that required that 50% of the electricians on site are certified under this program. And that they are. Providing that. For any charger that's being installed, regardless of the The kilowatt output. So the city Santa Rosa is. From that. Back up from that meeting back in February. The subcommittee was very supportive of following the 50% certification of. The personnel doing these installations and. And maintenance efforts. And the city. Since then has included in our boiler spate boiler plate language for contracts. To include 50%. Of our. Electricians be certified under this program. It was asked that we come forward with a policy. To go back to council and do this. But we were hoping that. Addressing this in our job specifications and would be an adequate solution as it is much more immediate. And if there's any other changes in the future that we want to make to this, we can simply change the language in our. Specifications to address that. So for instance, if there was. A desire to have all of the electricians certified. We could go through that process and change that. And we could go through that process. And that would then all the contracts from that. Point forward would then be required to apply by that. Those rules. In addition to that, we're also having all of our electricians that are on site. In public works. Go through the same. Process of getting the certification for the, for safety reasons when they work on any of these chargers. So with that, I'd like to move on to the next slide. So I think that's a great question. For safety reasons when they work on any of these chargers. So with that, I'd just like to get feedback if that's an amicable solution for the subcommittee and if we're reaching the goals of having, uh, meeting the training requirements that that you were desiring and meeting the outcome of, uh, the AB. 841. Requirements. And I'm looking to see if there's any questions from. Committee members. I think what would be helpful is if, uh, committee members had something in writing to be able to point to when we're asked about the policy, just because council members come and go and see staff members come and go. And so something in writing that we can point to, to show to people. Yeah, your request was heard and we've implemented it. And we didn't do it through an ordinance, but we did. We were able to implement it through our, you know, our job descriptions or whatever have you. I think that'd be really helpful. So I'm going to go to the council suffice for that. I think so. Yeah. We can definitely talk about that offline. Uh, as well. Go to public comment and see if there are any questions. On the departmental report. All right. Seeing none. Uh, Rob, you and I can check in on, uh, on an offline, but I appreciate the effort and the, the work from the team, uh, on addressing the need. Great. Thank you. No, uh, no question, mayor. I'm sorry. I'm sorry. I'm sorry for chair, but I did want to say that I appreciate you guys incorporating everything and trying to find a good way to, to do it and implement. Um, what we knew needed to be done. Great. Thank you. All right. Let's move on to item 4.1. Hello again. Um, introducing the upcoming code. Adoptions all electric only requirements and proposals. Well, good afternoon, mayor Rogers, council member McDonald, council member Rogers. Um, my, how time has flown. I believe the last time I addressed this subcommittee was in late 2019. When the city of Santa Rosa underwent, uh, quite the process of adopting. And setting the example for the entire North Bay of adopting an all electric only, uh, ordinance. Uh, for low rise residential construction. So I really can't believe it's been three years already. But, uh, Here we are getting ready to, uh, adopt codes again. Jesse, maybe it feels that way. It took a year and a half of litigation. That, that it was, uh, uh, edge of the seat for a period of, uh, year and a half. I, I certainly, uh, city attorney's office was keeping me updated on many aspects of that. And here we are. We were fruitful. We set the example. Uh, we showed the Santa Rosa did it right. And we, we proved it. That we did everything the way that it's supposed to be done. So here we are fast forward near the end of 2022. We're, we're, uh, working diligently on adopting the entire, uh, course of building codes and included in those. Oh, it is an element that back in, uh, 2019, uh, our first, uh, approach at, at the ordinance, uh, thank you for bringing up the slide. We can go to slide two, please. Now having lessons learned and learning from the industry, it's been, uh, quite refreshing. Uh, I've been, uh, teamed up with, uh, uh, an area, uh, California, uh, entity called MBA energy. And they are a group that has come together and it's not just focused on the Bay Area and the North Bay. It's the entirety of California. And what do these new codes and reach codes mean? So now, uh, being, having one that has set the example, everybody's following behind and everybody's going to, uh, not everybody, but a large number of jurisdictions will have reach codes coming up. So what it means for us now, uh, previous electric code code was, uh, founded in the energy code. Now as the slide, uh, proposes that the, the requirement, uh, live in the California green building standards code. And, uh, with that, it's a much more simplified process, but still gains all the, uh, benefits of this all electric ordinance. So what we're proposing moving forward really models, what we did before, maintaining the requirement that new low rise residential construction, the all electric only meeting a more refined definition of, of all electric building. Uh, next slide, please. So again, I spoke a little bit about the background, uh, because it was so forefront in the area of the council at that time chose to do a very refined and standalone ordinance. Addressing specifically the all electric only, uh, gave us the opportunity to do significant outreach, uh, for, for stakeholders, developers, citizens. Um, you, I believe we, we did a really fine job of reaching all corners of, of our area in trying to, uh, establish some consistency in, in how we, how we established the, our local ordinance. Um, one thing that was a really key element back then was we were required to, uh, execute a cost effectiveness study to show that the changes to the energy code at the time were cost effective. And we did leverage a, a study that was actually executed by PG and E for the purpose of going all record. And it was proven and upheld by the California energy commission and by this, our city council that it was proven to be cost effective. So for, uh, 2023, the codes are actually the 2022s becoming effective in 2023. Uh, we will amend the California green building. Uh, standards code again, uh, repeating some of the information that it still meets the intent. Uh, there are no tricks about it. It really actually simplifies it. Um, so that that's, um, Why this, this group and their hard work with the city council found this, this approach for us. And you'll see in, uh, about the fifth or sixth statement there, the energy commission has determined that reach codes specifically for decarbonization do not require a cost effectiveness study. So everything we did before we now don't have to do. So again, hopefully making our lives a little more straightforward. Next slide, please. So just some of the, the items specifically identified in climate action plan and how this relates. Very easy to see. And there are many other, other benefits as well. Um, the long-term sustainability greenhouse gases. Uh, climate change, uh, trying to approach and address our, our portion or small portion of the climate, climate change with, with, with, uh, other benefits. Hopefully, uh, the reduced reduction of the fossil fuel usage and certainly, uh, an element that really played out, uh, I believe rather well in our last adoption was the cleaner and healthier buildings. The, the, the, the, the fumes and, and such for using fossil fuels within a home, uh, cooking, the, the, the particulate, matter and burn fossil fuels in a home, you know, without having this, this fossil fuel, the opportunity to really reduce that interior environment, contaminants exist with these cleaner homes, not having fossil fuels burned inside of them. Next slide, please. So, uh, all electric moving forward and some lessons learned. Um, the benefit of the, the, the, the, the, the, the, moving forward and some lessons learned, um, the benefit so far, uh, approximately 1000 new units, uh, have been permitted. Meaning as I put in parentheses, they're, they're either built in construction or applied for, uh, meet this requirement of no match, no fuels, no fossil fuels connected to them for all aspects of utilizing the home for heating, water, heating, cooking, uh, any elements that's all electric only. And what this does encompass is, is quite the range of different types of construction from the single family dwelling to the accessory dwelling unit, which is an extremely, uh, viable and popular, uh, uh, pursuit for, for, um, construction now for by design, uh, hopefully by design, affordable housing, uh, ADU production has significantly increased and continues to increase. So we have a lot of those that show up, uh, one offs that you don't see or hear about until they come in and it's refreshing to see the numbers. I don't have the numbers, but we do have a dashboard that can provide the number of ADUs. Uh, other types of construction do include the multi family three story, uh, construction. Uh, we've had a few of those construction constructed or in construction here, uh, town home style, uh, construction, uh, uh, through different areas of the city of Santa Rosa all incorporate this all electric only, uh, element now. So I believe we're making, making gains, having success. And as time goes on, more and more, uh, permitting will just increase these numbers. Um, one thing we did do locally and as proposed last time, uh, for the adoption was to exempt these ADUs. Um, and then we, uh, we, uh, we, uh, that we at the time called them attached. That was an element that followed state law that was still developing for accessory dwelling units. Back then in the 17, 18, 19 era, the state was still, uh, developing their codes. And now they have these codes, uh, and laws that really give the possibility to develop ADUs, uh, in the city of Santa Rosa. Um, and then, uh, they also have a new legal accessory structure, garage, um, things like that. So the hope here in the proposal is to allow the exemption for those buildings that were literally converting that are, they're typically in the, in the rationale behind it is. These ADUs are creating created on parcels that are already served by fossil fuels. And many times they're being converted within a portion of a, they're being converted by fossil fuels. So the exemption made sense then it appears to make sense now. Um, to not penalized, so to speak, someone trying to do a, uh, an affordable construction project, converting a garage, converting space within their home, converting space within their detached garage, um, to add additional cost part of the, you know, I'll try to provide a little background for that part of that cost effectiveness, even though we don't have to, uh, execute cost effectiveness. If you develop, uh, property that already has a fossil fuel and don't use it, say on an accessory dwelling unit, you may be inclined to have to use additional costs to in, install electric type heat pumps or stoves or, or other elements that. Don't benefit from the cost effectiveness of not installing gas infrastructure to the parcel. So one of the main elements of the cost effectiveness study was that you don't have to install gas infrastructure. And there were ranging costs from four to $14,000 for that. So even though cost effectiveness isn't a part of the, the requirement now that is still an element that is extremely important to those that are trying to develop ADUs, most applicants for ADUs are families that are trying to develop either a mechanism to gain more revenue from their property to afford high costs of mortgages and things like that. A couple of other other exemptions are proposed and they don't stray from the exemptions that existed in 2019. One being, uh, reconstructed buildings lost in a disaster or calamity. In 2019, we really were forced into an exemption for rebuilds anyway. The governor at that time signed AB 178 or 179, I believe, which exempted all rebuilds, declared disasters, rebuilds in the declared disasters from photovoltaic. You can't build a home that doesn't have photovoltaic to meet, to be all electrical. It costs a lot of money again, but it costs extremely more. So that's following the same suit, but establishing in our ordinance that we continue to allow rebuilds from disasters for folks that are rebuilding and don't have to literally pay to have gas infrastructure removed from their parcel to rebuild. And that's a key element here is if a disaster rebuild or any disaster in town burned down. And we say they have to be all electric. They will likely have to pay the cost to have PG and E remove the gas lateral from the parcel. On this meeting with MBA energy, I had a rep from PG and E, and it's inconsistent right now across the state where they do and don't charge for that. But I do know for a fact that I have a developer here in Santa Rosa that would have been charged by PG and E. So that's a, that's some foundational rationale for why we want to consider exempting buildings lost in a disaster or calamity. And then the other one follows the exact same line where that infrastructure exists on the parcel and the owner would have to pay to have it removed. So again, we don't have to consider cost effectiveness, but I do hear the stories every day on costs of construction and it's, it's, it's a tough sell. I will certainly sell it, but when people tell me how much it's costing them to build an ADU and we add another five to $15,000 on it, they, they, they don't become very happy. Next slide, please. So please, if you can forget that you read number three. I learned from one of my esteemed colleagues, deputy director Osburn, that that has real no effect. The idea was that if somebody had a fully developed plan that they had already put a lot of money into this development of gas infrastructure, but that's not the case. So please ignore number three. I did strike it from the proposed ordinance and I made it in, I got it out of the earlier part of the ordinance or the presentation. So for, for our, our purpose today is, is looking for any feedback on what I've presented, how we, we propose to move forward. And if the, the exemptions seem reasonable and, and are supported to move forward to the October 25th, first public hearing for the coded option. And I believe that's it. All right. Council member Rogers. Council member McDonald any questions. Diana, go ahead. Thank you. I just have a couple of questions when it comes to equipment. Is this upping the timeline from what the state of California is requiring, is putting us in alignment with what the state of California is requiring. We're still in advance of the state of California. So my only caution on this is because I know the procurement of equipment specifically on rebuilds for electric equipment when it comes to HVAC and other things, there's a delay in that. So my concern about us moving it up on the timeline, I can tell you with the new rules in California, which is around 2023 with it, when everything has to be electrified, I'm just worried that we're pushing it and it's going to delay projects from being done because they can't get the equipment in until after the first of the year. That's actually what we're kind of contending with right now on a, a change out of equipment. It won't come in until 2023. If people are putting in 2022 equipment, the, if they want to add an air conditioner, they're not going to be able to match up their coils to their new HVAC equipment. So the concern I have on this is it meets our climate goals. It meets everything like that, but what does it do to people that are trying to actually build the developers that are trying to get their projects finished when we see a huge increase of cost to construction. So if you could give me any feedback specifically on what happens in this case, if we're trying to implement something in November, say, and then something's delayed till after January, are we going to allow those to go through? Right. Very good points and good question. Thank you for that. So there's one really good key fortunate element to this in that we're really not proposing to do anything differently than what we've done for the last three years. So that's our local builders, contractors, developers. They are keyed into what, what it takes. Another fortunate element is say a project starts now or maybe even started earlier in this year. Every, all of the requirements are based on those requirements in place at the time that they applied. So say we, we issued a permit and they're not going to get their equipment till 2023. They get to meet the old requirements. And to, to stack a little bit on top of that, I forgot to add the new, the new energy code, which we're really not touching with this is significantly more stringent yet again, which you're hearing in the new energy code literally has within it the ability to construct an all electric only building without making it a requirement. They have the option to do what they, they calculate values and efficiencies. Most homes without the requirement to be all electric may go electric and fuel, but the ability now let is, is within that energy code, which it didn't exist before. So that's just something I wanted to put out there that I, I forgot to mention that that's why we had such a harder time on the adoption last time is we had to build a pretty significant portion of our ordinance to tell people how to do it. Now we simply define all electric only building and say meet it because the energy code tells you how. I hope that helps. That does the concern was really around these projects that are currently going on if we move up this timeline that we aren't going to delay any of those specifically. So thank you so much for that and the presentation. I appreciate it. Natalie, any questions. I don't have any questions. I think the exemptions are good. I think they did a good job. And it's a change for a lot of people. I just moved into my all electric home, but it's kind of the same thing except for the stove. All right. Thank you, Jesse. My only question is only tangentially related. This is the first I saw data that showed that we've got a thousand homes that have been built. All electric since we passed the ordinance. Do we have a comparison? How many homes have been built? That didn't have to meet the, the all electric ordinance versus how many did. Do we have any feedback from, from the folks who had to do the building any, any additional costs that we didn't anticipate from doing it? And it'd be great if we could get a number. And I know this isn't your purview, but perhaps Tasha or somebody else that we work closely with or our CPA, maybe we can get an analysis of how much we've actually reduced greenhouse gas emissions from buildings just by those thousand homes coming online. And we've talked about this before the, the new greenhouse gas emission inventory for Sonoma County, which goes through 2020, which would have taken some of this ordinance in some of the impacts of this ordinance in that did show a significant drop in building GHGs. It'd be great if we can figure out how to attribute that to different policies that we've passed. Thank you, Mr. Mayor. And I will do my utter best to find that other data. You've heard, heard historically our systems aren't really great for data. We continue to improve them. And honestly, we have a couple of agencies out there that have requested documentation to help build that data for us. They are offering to scour our information. We have one being Bayron and I believe Sonoma clean power as well. So they've requested permitting information to hopefully really bring us to some of that real raw data that you're looking for. And I bet too, I know one of the groups that was particularly interested when we did this three years ago and have continued to kind of carry the mantle. I want to say it's the building decarbonization group. I could look up their, their, their actual technical title, but perhaps they'd be interested if we just tell them how many homes and how many square feet those homes were, they might be able to do a rough analysis for us. I will put that on my list and hopefully have information on the 25th. Cool. All right. It's going to public comment on the item. If you're interested, go ahead and hit the raise hand feature on your zoom. I'm seeing no comment. So go ahead and bring it back. I don't know if you need a motion and a second Jesse, but it did sound like you've got pretty unanimous support from subcommittee members about moving this forward to the city council. I do have everything I need. Thank you, Mr. Mayor. And really appreciate your time. And again, much smoother time this year, we're going to be, we've set the example. So I'm proud of city of Santa Rosa for the work we already did. And here we are again. I feel we're still leaving the back. I appreciate the work on it. We'll move on to item 4.2. Speaking of leading the pack. And I'm happy to introduce Matt. Wilcox. He is a. Planner from a TPW and he will be presenting the city bus short range transit plan. And the service override and. Sorry. Priorities. I'm having a hard time talking today. Okay. Take it away, Matt. Good evening. So this presentation is to go over the, what we've kind of accomplished so far with the short range transit plan and also some of our service priorities. You know, the short range transit plan is kind of our preeminent planning process. But as you've, you heard in our previous presentations on it, we have changed since the previous iterations of it. This time around in regards to how we're responding to the pandemic across the Bay Area as transit agencies. And then also in tandem with that, we have our transit integration process with head of Luma transit and Sonoma County transit. So some of the items in the presentation are also related to that effort. So this is kind of a catch all presentation on what we have in the planning and service area. I don't know if anybody else can see the presentation, but I can't. There it is. So we can go to the next slide since that's the title page. So for just a kind of a brief. Overview of what our ridership has been doing. There's a very obvious drop in the pandemic. And then last fiscal year, we had our highest ridership at 95,000 in the month of May. So that was, that was some good growth coming out of the pandemic. And we were certainly pleased to see that, but going into the current fiscal year, we go to the next slide. Some highlights here and these are outdated. And fortunately, we have some good news to go forward into September. But in August, we had 108,000. That was our first month since the pandemic that we had achieved over a hundred thousand rides. In the previous fiscal year, about 36% of our monthly rides were free. That's 35,000 riders a month. And that August number was about a 41% increased year over year. And then on the right side of the slide, we can see our youth rides. We have been total for the fiscal year, 245,626. The JC with 36,000 and changed veterans 19, almost 20,000 and then paratransit riders, which are also free or about 27,000. And just some updates on those numbers. In September, we actually had a 110,978. So a hundred was 111 rides. Our free rides accumulated to in September alone were 48,800. So those are a combination of those fair categories you see on the right hand side of the screen and youth were 33,515 of those rides. So a substantial number of trips on city bus in the month of September did not require individuals to pay. So very good news on that front. And we can go to the next slide. So this is the timeline that we showed at our study session. It's been modified. And we have some tweaks to it given what we learned as we went through the process of making the draft plan, which we turned in this month. That draft plan didn't contain a lot of the service planning stuff that we had hoped to have in it. It was mostly related to MTC's requirements for the financial outlook for us going forward based off of their scenarios. So this timeline is accurate for what we will do for the short-range transit plan as required by MTC. But there are other planning efforts that we intend to go forward with that may end up on a different timeline and may require different council action as more like a service plan because we still have routes that are currently suspended. We have some potential modification to routes. So to do our due diligence and make sure we do it right, we want to extend that timeline beyond what the MTC requirement is. If we want to go to the next slide. So the requirements for the SLRTP this time around for for us are prescribed by MTC. Usually we do a there are things we need to include in it, but we do more so have the ability to make a service plan based off our own projections. This time MTC prescribed what we needed to do for service or for our revenue envelopes for each of these scenarios you see here. And so as we went through this process, we actually found that we've kind of already exceeded what they expected even in the robust recovery. So the intent is if we do go forward, we will go through the scenario process that MTC prescribed and we'll wait for their feedback from the draft. But in regards to our actual service planning efforts, we will probably create what is essentially a fourth scenario that's more in line with the projected numbers that we expect with that with ridership and funding. So we're going to kind of do a two fold. And hopefully that will result in a robust planning process that we can then improve the service with. And we go to the next slide. So as I mentioned, we want to go through this process as a service planning process, not just what the SRTP is being as it's laid out by MTC. So things that we're looking at is how do we apply more frequent service in the system? How do we make our alignments more direct service? That's more bi-directional, strong anchors, spacing of routes and connectivity. And all of these are planning principles. And it's not to say that we'll redesign all of our routes, but these are things that we're keeping in mind. And also, you know, with the coordination with the other transit operators in the Bay Area, not Bay Area, but Sonoma County, you know, we're especially looking at the spacing connectivity part of it. It's not just how our routes are spaced, but how they interact with Sonoma County transit. And also the connectivity, not only between our local routes when people make transfers, but making better transfers between us and Sonoma County transit are smart. These are the things that we want to look at as we go through the service planning part of it's not necessarily the SRTP, but we're kind of, it's all layered together. So to speak, we can go to the next slide. So the efforts that are currently underway to, we're improving regional coordination. We should go to the next slide. There we, sorry, can we go back? I was thrown off of my notes, my apologies. So we, as part of the SRTP, or not part of the SRTP, but our regional efforts to coordinate with Sonoma County transit and Potaluma transit. We're, one of those first steps is to align holidays service level. So right now we are moving from our regular weekday service on Martin Luther King Day, or at least that's the intent. President's Day, day after Thanksgiving, Christmas Eve, New Year's Eve to a Saturday level service. And this would bring us in alignment with Sonoma County transit and Potaluma transit, who have the same service level, their Saturday schedule on those, on those days. And being able to message and synchronize, there's a consistent expectation across the ridership in Sonoma County about, you know, when they go to ride the bus on those days, they can expect the same level of service and can then plan accordingly and make their connections if need be. And we can go to the next slide. So as a lead up to the cancel item on 1025, we did some outreach to the public around the holiday service, but also to touch in some of the service priorities that we'll be looking at as we move through our service planning process. So we asked the public kind of a trade off of, you know, what is most important to you? Is it frequency? Is it later service on weekdays? Or is it equal weekend service? And then we also asked the public how we could better serve the areas are, you know, which areas can we serve that we do not currently serve? So we looked at the map and those areas were North of Pioneer, West of Coffee, Fountain Grove, South of Bellevue, into the Moreland Avenue neighborhood, Santa Rosa Avenue, south of ELSA towards where Freedmen's Home Improvement is. And then also south of the fairgrounds where Brookwood continues. And then finally, as I mentioned, we asked the public how those Saturday schedules would affect their ability to use city bus and move about the city. And we put in three very specific categories. You know, it does not affect me at all. It will affect me a little, but I'll be able to get where I need to go. And then lastly, I will not be able to make the trips that I need to make that day. And that's kind of the most problematic is people not being able to get where they need to go with these changes. We can go to the next slide. So much like the data on the, or the second slide, this survey was open between when we submitted this and things have slightly changed. The 54% is now 56% of respondents are unaffected by the holiday service. And then interestingly enough, New Year's Eve became one of the most problematic days with 20%. And the rest of the holidays with respondents saying that they would be unable to make the trips for about 17% of respondents. And we had roughly 250 respondents to this survey. As for the service priorities, 30 minute service was ranked the highest followed by service that operates until 10pm on weekdays. And then lastly, a Saturday level service on Sunday. And then location served area north of Piner, west of Coffee Lane, which kind of teased in with our high Piner high ridership. So I imagine a lot of those people responded there saying they want more direct service, I suppose, to having to walk down Fulton. And then the next highest there was on the southeast side of Santa Rosa, down towards Friedman's. So not only did we do the kind of anecdotal evidence from the public with the survey, but we also, as you'll see in the staff report, as it's related to the item of making holiday, those five holidays, Saturday service, we also got the data and looked at the ridership. And there's a consistent 30% drop in ridership on those days historically. It's not equal to Saturday, but there is certainly a drop in ridership and would be more in line with what we would expect from a Saturday level of service for us. Let me go to the next slide. And then, as I mentioned, we're doing our outreach. And one of the more specific things that we're going to bring to the public in the coming months is a change to the Route 9. And this on the page is an example of what we're using as a outreach tool and what we'll probably be using on some of our other Route specific outreach. Just kind of getting the facts out there in a very concise manner, providing multiple outlets for feedback, whether people want to call, mail, they can respond online. These eight and a half by 11 sheets will also be in Spanish so people can comment in multiple languages and their feedback will be heard. For this Route 9 specifically, it's creating a bidirectional service that will go between Coddingtown and the transit mall. And we're also going to be looking at our Route 18, which is kind of circuitous at the current, in its current state. So we want to kind of look and see if there's ways to strain that out and make it more efficient. And then as, you know, talks of annexation of the southern part of, in the southern part of the city happen, looking at potential realignments of the 12 and 15 and making sure that those services then meet the needs. And we've mentioned before, it's not necessarily tied to any sort of annexation, but that's also part of our effort to coordinate with Sonoma County transit as we look about how services overlap or don't overlap or where we can provide better service to residents all over Sonoma County, not necessarily within the city limits. And then lastly, we're also going to take a look at the Oakmont service to make sure that that's meeting the needs of the community. It's been a while since we've really sat down and figured out, you know, this is the best structure for the service. So that's another one that we're going to be reviewing to make sure that it's meeting the needs of that community. And we can go to the next slide, which is questions or comments. Thank you so much, Matt. I'm looking to my colleagues to see if you have any questions. Go ahead, Diana. I just want to thank you for all the outreach that you've been doing to make sure that we're meeting the needs of the community and looking at like the times that will work best for people. And specifically, obviously in my area in D3, I have Oakmont. So I really appreciate the outreach to that part of the community and everything that you've done to make sure that we're on target. So thank you so much. Okay. All right. I think one of the things that I always find, Matt and Rachel and team is not only do I love the data that you give us, but you always give us a sneak peek at the next month data. And I try to write down fervorously the numbers so that we can, you know, talk about them and not have to wait for them to come back. And I appreciate the, the sneak peek always. Really it's encouraging work and want to thank you all for your work, particularly on the ties study and moving things together. So we have a cohesive network. Let me go to public comment and see if anybody has anything to add. All right. I'm not seeing anything. So great work on the presentation. And I look forward to the next step from this. Oh, go ahead. Good Natalie. Chair, you always confuse me because when you say questions and I'm like, I don't have a question. And then you guys give comments. So my comment would be your team always amazes me at looking at the need at looking at what our resources are. Getting feedback from the community and implementing the implementation. And when we don't have resources, where can you go get the resources? So Matt, Gary and Rachel, I know that it's not only you guys that do this, but from the management all the way to the drivers to the people that clean our transit, your team is amazing. And I just wanted to let you guys know that. So please keep doing what you're doing. It makes all of us look great. So thank you very much. Thanks for that. All right, Diana. Any comments? I do what I want Natalie. If I want to make a comment, I want to ask a question. Just do what you want. All right, we'll move on then.  I'll turn that over to Tasha. Great. Thank you. So on our future items list, we have coming up in November. We're going to have a conversation about wildfire mitigation and resiliency from presented by Paul Lowenthal. And we'll hear about essentially what is happening. That over time we've been doing, which is perfect timing considering we're in fire season. So we're looking forward to that. And then in December on the 14th, we will have a status update on the Santa Rosa forward. And that will include our climate action plan as well. And this will be perfect timing because it's going to also include the release of the greenhouse gas inventory and forecast. So we'll be looking forward to that. And hoping that you will be able to provide staff with direction and. Provide them with some insight and about the general plan process moving forward. We look forward to that. And that's all I have for you. There will be future updates as well. Coming on our standard items, but we hope to fill up those other spots. And like I said, December 14th will be our. Our next item. We'll have one right before the holidays and then November night. That's going to be our next one. Great. And I don't know if I'll be able to join us on the night. So if not, I'll have one of the other council members. Chair of the committee will make sure we have a quorum. Let's go to public comment. And see if there are any comments. I'm going to bring it back. Any comment. From the committee. It's a little hesitant now. No, I have none. When is she ever hesitant? No mayor. I have none. All right. Thank you, team. We'll go ahead and adjourn. Thank you. Thank you, everybody.