Oct 26, 2022 Mobility Committee on 2022-10-26 10:00 AM

>> Okay. All right. Well, this meeting of the Mobility Committee Wednesday, October the 26th, 2022, 10 a.m. Our first item is to have any individual consideration items on the agendas that individuals are able to comment one time per agenda. Each speaker is going to give a total of three minutes per agenda item. A requested speak card must be completed and returned to the staff liaison before the committee considers the items. Items for individual consideration, MC-22-029, consider the approval of the minutes of September 28, 2022. >> I move approval of the minutes. >> Okay. MC-22-030, receive a report and hold a discussion regarding the City of Denny's Transportation Mobility Project Status Report. Good morning, sir. [ Inaudible ] >> John Bolster, Innovative Transportation Solutions. I'm here to give you an update on your transportation report. So we'll start off with some good news. As you may have noticed if you drive around the southern part of the town, 2181 essentially was open to its final configuration back on October 17th, so road is essentially open and we're now doing punch list items, sod, painting, some of the storm water prevention barricades. They're up for construction, so it's essentially open to traffic after nine years of trauma. So that's good news there. >> It's wonderful news. >> Mayhill, at 35, the project is slowly creeping up in cost, we're at 95 million bucks for that interchange and fringe roads all the way to the new look. The funding was included in its previous August approval of the United Unified Transportation Plan and we are still ready to let in 2023 assuming all of these utilities that are listed here will meet their deadlines or so. Being told by tech site we won't be making these dates, so we should be letting this project go to construction in December of, it says June of 25, but since we got the money in August, it'll be the 23 timeframe. You'll note that a lot of these numbers are highlighted, the reason for that is because of two reasons. One is we were needing to get additional funding previously to the last six months and the other reason is that in the past six months a lot of the costs have gone up. So the I-35E merge project is at $431 million, it's a change and we have those funds and again that project will be letting September of next year. Assuming all these utilities get relocated, but again we're fairly confident that that will happen. And then your I-35 North project, it's got been broken into, it's essentially only three projects. The blue project is the interchange associated with the 455 project and it's going to be built with SN455. Again, it's $792 million is what we have available and right now it's at $749, so we didn't have to change the dollars on it because we had enough money in the project. 35W Furnace Roads, this one six months ago we thought it was $180 million, we asked for $188 million and got that approved in the August UTP, they did a new cost estimate and their current estimate now is $321 million, so somebody's going to have to pay the cost off for that one. But again, we are, it has an actual let date of September 24, so between now and then we'll figure out how to cover a doubling across this project. And this is from 407 North to essentially 2449, where the Luke 28 will come in in the future. And we're also working on picking up somebody to do the Furnace Roads on the southern part of this project in the next UTP update. Okay, 377 and 380 project across the lake. We are anticipating this project being completed in December of next year. There are various phases, we've just switched to our second phase all year this month and so far we seem to be on track. I haven't heard any problems with anything going on out there and I'm assuming if there were problems we'd all hear about it. U288 West Furnace Road project. The chain to tail is in full on design. It's part of what we're doing is working with the city on some thoroughfare plan modifications to make sure the Luke 28 is accommodating the needs of those future roads when this project -- because when they initially designed this project, they used an old thoroughfare plan. So modifying the southern part of the project to make sure it accommodates the city's current thoroughfare plan. Again, it's not cheap as far as the Furnace Roads cost, but we're confident by the time we get to the ready to let date of April 26th that we'll have the money. And remember, the reason why this takes so long from design to ready to let is because of all the utilities out there, the gas wells, the transmission lines. There's a significant number of relocations just with the gas wells along this corridor. And then your 28080 Furnace Road project. We've got ChicoCope working on that. We met with the city earlier this month to get a handle on the incredible number of developments that are going on in this corridor, trying to accommodate, mitigate, and otherwise avoid where possible. But the whole reason we're doing it is because of the development that wants to be in this corridor. So that's our critical path item right now is to get a handle on where the developments are and what can be done in the interim to make sure that they are aware of what we're doing and we're aware of what they're doing. And so what we may end up doing is if we have some areas where the project is in conflict with the development and we can't mediate the issue, if the bottom program passes, we may end up doing some preemptive land banking on this corridor because we can't lose the corridor. Bonnie Bray, segment seven. We're including this and this project. So over here on the far west side of the project for the loop 288 we're including the Bonnie Bray segment seven into the 288 project because it also ties into the frontage road. So again, it's Pacheco Coke who's doing that as part of the 288 design and clearing that part because that part's not clear right now. 1515, nothing really has changed here. We're just continuing to work on finalizing the design. And again, we are looking at a ready to let of October 2024 and we still need the $38 million but we're confident we'll get it. 1173, so we were going pretty quick and fast on this one to add it to the 35 job but I just got called from the engineer saying that the city of Chrome has got some issues with the western part of it. So we're going to go see if we can't meet with them and figure out what their concerns are if there was an administration change from the old mayor to the new mayor, opinions have changed. So we may not hit our mark for having the project what they call plans adequate which is when the design gets far enough along where the utilities can use those plans to determine whether or not they're in conflict so they can start moving. We were thinking we'd get that in December or January. We may end up not having that ability. It won't happen some other time. Outer Lube, this one is LJA is doing the work. What we're looking at is on the eastern portion. There isn't a logical term and I where Cohen kind of left off because they didn't environmentally clear it so they just simply built the road in a pasture for lack of a better word for future development. So we're working with Tech Stock to identify the logical term and I and once we get that done then we'll start into the hard part of the environmental clearance. Alma Locus, I'll leave this to Becky to talk about but we did get the information from Tech Stock and I think the city is reviewing those plans. We are meeting internally next week to go through the pavement section that's been submitted and then I spoke with Travis actually last night and we're going to work till meet and go through all of our comments later part of next week. So working through those logistics of the pavement section that was submitted, the design that was submitted, just making sure we're all on the same page so we can move forward. So we know what we're doing as far as the limits and we know what we're going to do as far as the improvements. What we don't know is the pavement depth and the effects consistent with what the city desires. And then all the resurfacing in the city of Denton proper has been completed and we are now into the striping phase. You'll see where there's where they're striping some of the sections in the north. It was kind of scary yesterday when I was coming back in town, but we should be done by the end of the month on all the striping on 35 resurfacing project in Denton. I think that is it for me. Don't forget to go vote for roads. I'm not going to tell you how to vote. It's just going to take a vote for roads and that's it for me. Any questions? >> Yes, I have a question in regards to the -- back to the loop. >> The outlook? >> The outlook. >> Loop 288. >> Okay. >> The front edge road. Right there. >> Okay. >> So I see that it's highlighted. I see a highlight green. >> This right here? >> Yeah, and then it cuts through. >> Yeah. So what -- okay. I'll wait until you ask. >> Go ahead. >> So what we're attempting to do is to tie 380 to 35 because we're going to have direct connects at 35 here on the loop and the intent is once this part of the loop is basically a freeway with the front edge roads, we want to make the traffic travel up and around the loop to go -- it's just cutting through to go up on 288 and so then you can come in, especially when you get the western part done, you can come in and restrict truck traffic that's just going through your community off of 380. And so in order to make that movement, we need to have a more direct movement from 382, 288, and let me say that that is not the scale. It won't be -- it's actually a lot tighter in, but the intent is to have a direct movement. And then if you want to go into town, you'll have to stop and get off of the box and go through the signal. So the intent is to make it go straight over to 35 as fluidly as possible. >> I-35 between the Oak and 380, as we know, with the changes that were made, with the exit being so close and you all pulled the exit back, it's just no -- it's no reasoning. I mean, it just doesn't seem like there's anything else that could be done because I got hung up in there one time. >> Yeah, I get hung up there all the time. >> And it's just -- >> Say it to one. >> And it's so -- for me, it's so -- it's very scary to see all of those impatient people just pull out in front of cars that are still traveling. >> So the solution is that everything we just built there is going to be torn out when the merge project goes and there'll be a braided ramp there. And so what a braided ramp is is what you need is people getting on and getting off between Oak and 380. That's why all those people are there. >> They're there. >> They're there. And so what we're going to do is your exit ramp will be in the same location as your entrance ramp and it will go up and over and get on a freeway. So you'll separate the movements and that supposedly will solve the problem because what's happening is everybody wants to get on and off to the same location. And just to put it in perspective, if you've gone down south towards like North Fort Worth where Western Center Boulevard is, those are braided ramps. >> Okay. >> So those big bridges where everybody's getting on and off at the same time, that's what will be there on 35. So that should solve the problem. >> So when I am -- I'm almost trying to explain to my husband what's going on. I was going to do this. I got to do this. That Mayhill and that 35. And I notice that the Exxon looks like it's on its way out or it's finally -- >> Yes, ma'am. >> Explain to me what that's going to kind of look like. >> So you see what Luke 288 at Golden Triangle Mall on 35 looks like, the big interchange? That's only 10 lanes. What we're going to do at Mayhill is the same thing. Only it will be 12 lanes that go under the freeway. So it will be a significant larger footprint because you have six lanes coming to Mayhill and six lanes coming up from 2499. So it will be a large structure with three lanes in dual Fs and then a U-turn in both directions. And so that 2499 Mayhill, it's going to run from 35 over to Woodrow like that. All of that is being cleaned up. >> So we've got three projects going on. North of 35 at Mayhill, we are realigning Mayhill through that track to tie it in and go straight up Mayhill, take out that bend at Colorado and Edwards and get rid of that great crossing of the railroad. And then 35 interchange itself with Mayhill will be the 12 lanes and then 2499 to the south is our six lanes. >> Okay, so between Mayhill and Woodrow, Colorado and 35, all of that is going to be a part of this project? >> So we're negotiating that. Because what happened is the old environmental document did not go all the way north to Colorado. And so we've got the Cog City of Denton, Denton County project that's going to redo Mayhill at Colorado. And so we're just figuring out how to just close the gap between the two. We'll figure it out. >> That's what I hadn't heard, you know, all that time. So I know that that is a big deal. >> Yeah, we're not going to do all that work and then have it with us, you'd all call stupid because we didn't fix that. 800 feet of pavement. We'll fix that. We'll get it one way or the other. >> I'm holding your hand. >> Everybody does. >> Thank you. It goes on. >> I'm good. >> Yeah. >> All right. Easy. >> Thank you very much. >> Yeah. >> Thanks. >> I didn't bring anything, so. >> Thank you, John. >> All right. NC22032 received a report holding discussion against that direction regarding Bonnie Gray Street Project Update. [ Inaudible ] >> Morning. I'm Kyle Pettico. I'm a program manager with Capital Improvement. And so today, I'm going to give an overall update on all the projects associated with the Bonnie Gray Corridor and as well as go into staff's findings regarding a potential roundabout at Windsor and Bonnie Gray, associated with the phase six of this project. So here's an overview. The Gantt chart at the bottom, the colors match the map at the right. So starting at the bottom from Rose Lawn to 35 is phase three, Bonnie Gray phase three. That one is currently bidding and is set to close next week. So pending council award, we're looking at a late four-four start construction. And that's approximately an 18-month project. Phase four is in green. That is between I-35 and scripture. That one has funding associated with the 2022 county bond. And the estimated schedule on that pending the approval of the funding is construction start in the beginning of 2024. Phase five is scripture to U.S. 380. That's in pink. That is the same as phase four type of bond 2022 county bond funding and estimated construction start is early 2025. Phase six is the one that we're talking about today. That is U.S. 380, U.S. 77. This one is completed in the design phase and we're ready to send it out to bid pending one final parcel that we have to acquire. It's the -- since there's federal funding, we need to have all the parcels acquired before we commit the project. So regarding a proposed roundabout at Wednesday. So the current plan for phase six that's complete includes construction of a standard signalized intersection with this project that would -- traffic signals, crosswalks for a standard intersection. So on August 16th, 2022 council member Davis requested information regarding the viability of replacing that planned signal with a roundabout. There was previous communication with staff that was provided where staff would -- was committed to look into the viability and research the viability of a roundabout at that intersection. So that's what we're trying to accomplish here even though the project's designed and ready to go. So in this presentation we examine the impacts of this roundabout on the project cost and schedule, any impacts to traffic and then any impacts to pedestrian and pedestrian traffic. Here's a quick cost breakdown. So running through each of these, we'd have to redesign the pavement, redesign the drainage due to the increased footprint. We'd have to add in some temporary pavement to maintain access during construction. We would emit the signal at Windsor which would result in a credit. But then we'd have to perform an environmental reevaluation due to the federal or the textile funding. We'd have to require additional right-of-way which looks -- is approximately a 12-month process if anything most driven domain. We would have to accommodate the fire station at this location. So the proximity of the roundabout to the fire station would require a preemption signal and a bigger traffic study to go into how that would work getting the engines out of the garage and getting such folks proximity to an un-signalized intersection. And then we would also have a large utility relocation cost. We're looking at approximately a two-year delay on this. And base estimate $1 million cost of relocating utilities. We'd have to remove a minimum of three EME towers and relocate a 42-inch water line that would now be under the footprint of the roundabout. So overall we're looking at approximately a three-year delay and $2 million additional cost if we were to add a roundabout at this stage of the project. Here's a brief overview of the utility concerns. So in this overview, this yellow line here is the DME of 138 kVA transmission line. And that's a picture of what the tower transmission line looks like that would have to be relocated to the left there. And that's also the blue line represents the location of the 42-inch water transmission line. So the reason for the 24-month schedule impact on these is both of these have up to 12-month lead times on materials for procurement plus they have very, very limited windows in which we can shut these down to perform any type of relocation because they're both large-scale transmission lines of water and electricity. Regarding funding concerns that we uncovered with this analysis. So due to the inclusion of FHWA funds, this project cannot be sent out to bid until all of our clearance letters for right-of-way utility clearance letters are received. So with that long utility relocation window and the additional right-of-way acquisition, we're looking at a potential, again, 36-month delay to the schedule of the project. So we would also risk, put our federal funds at risk. So right now, we have $11.8 million in federal funding through TxDOT. And if there's a substantial delay due to a late-stage redesign and this reevaluation that the process would have to go through, we would put that funding at risk. So I included a Gantt chart at the bottom showing the different stages of Bonnie Bray. Bonnie Bray 6 is the blue line, again, showing that we're ready to begin this project with construction estimated early next year. The bottom line is if we would add a roundabout and include that 36-month delay, showing that we wouldn't start construction until approximately 2026. So we also analyzed the pedestrian concerns in this area because that's been a bit of a hot topic, especially with the new high school openings. So on this map, I have the new DISD high school highlighted along with the proposed DISD elementary school. This elementary school is estimated to be open in August of 2024. So we're working that phasing in with the current plan for Bonnie Bray, the current construction plan to minimize the impact on that school. But if we face the delay due to adding this roundabout, we wouldn't be starting the improvements on Bonnie Bray until after that school is open. We also had concerns regarding adding a non-signalized pedestrian crossing at that intersection because with the roundabout not having a signalized crossing times, the crosswalks would be basically pedestrians crossing live traffic. So in discussion, this presents what is called a multiple-threat scenario where if a pedestrian is crossing and the first car to see them stops, as they're crossing in front of that car, the pedestrian can't see the second lane and that second lane can't see the pedestrian. So there's no signal to stop traffic that prevents a potential hazard to pedestrian travel, especially considering that this is expected to be a major pedestrian route for both of these schools. So with the Bonnie Bray phase 6 improvements, a 10-foot mixed-use path is being added on the east side of the road and a 6- to 8-foot wide sidewalk is being added along the west side. And then we also had concerns about future expansion. So with the traffic impact analysis performed in 2020, a four-lane divided roadway is expected to be able to take us through 2014 with as far as capacity. As soon as we start to exceed the 28,400 average daily trips, we would have to upsize this to the Bonnie Bray to a six-lane roadway. That was initially anticipated to be common issue around 2040, but that initial traffic analysis didn't take into consideration the development of these DISD properties or the multifamily developments of the mark and the perch, both of them in that Bonnie Bray corridor and the added traffic. So a six-lane upgrade may be required before, earlier than 2040, and this is just an example of what a six-lane roundabout would look like. So through our analysis, staff leaves that replacing, at this stage of the project, so late with this project ready to bid, replacing that intersection, the plan's signalization improvements with a roundabout would cause more negative than positive impacts on the community and on the project itself. It would cause impacts on the traveling public due to pedestrian risks. With crossing that, it would potentially risk a withdrawal of the federal funding that we have assigned to this project. DISD would face a delay of the improvements in this area, causing major traffic impacts on their routes to school when this would eventually take place. And then the neighborhood also has had a lot of complaints about the intersection at Windsor and Bonnie Bray being a four-way stop, and so the neighborhood is very much looking for the signal being installed there with this Bonnie Bray project. So staff recommends against adding a roundabout this phase, but we're searching, we're looking for feedback from Mobility Committee before we present this to Council. Any questions? I'm pretty sold. I tend to be roundabout, agnostic. I don't know a ton about the data regarding their safety as far as collisions or collisions with pedestrians. My first piece of feedback would be, before you bring it before Council, I would say add something in regarding pedestrian safety and roundabouts as far as data. Just so that, because I'm trying to anticipate what Councilmember Davis might say, that depending on what the priorities are, is it worth $2 million if it's a lot safer? Maybe. Is it worth $2 million if it's a little safer? Maybe not. I think that that's a cost-benefit analysis for sure. My feedback would be it's probably not. But I'd say bring that before Council. So what concerns was, and this is a question for anybody in the room who has an idea, what concerns was Councilmember Davis trying to address when he suggested the roundabout? Was it primarily pedestrians? I believe it's because there was communication between Council and previous staff that a roundabout at this location would be analyzed. And they provided emails of that effect to staff that wasn't communicated during the design process. So the design went forward with a standard signal, a signalized intersection, and we're just following up on providing the analysis and providing the information that was promised previously but not communicated. Okay. All right. So his main concern is just, hey, I heard this was happening. Is it not happening? I believe so. Not so much that he's pushing really hard for a roundabout necessarily? Yeah. I would concur with what Kyle states. We've just been made aware of a situation where there is previous communication that happened with previous staff. None of us were here at that time that said, hey, we would evaluate it. So we are wanting to go through the process to physically do the evaluation, which I believe we've done so I'm confident with the work that Kyle's done to show, yes, it is a possible situation. There are a million ways to design something, but from the staff's recommendation and perspective, it slows the project down three years, adds additional $2 million, and from a pedestrian perspective is maybe not the best-case scenario, and it negatively impacts DISD. We actually met with DISD Monday. And one of the things I know Kyle is aware of but I want to highlight is with you, council has already passed an agreement for the Riney Road portion to be included as a part of the Bonnie and Mary Phase Six. We've already coordinated with DISD through an interlocal agreement to add Riney Road construction to the Bonnie and Mary project so that we are working to have even Riney Road improved before the new elementary comes on board too. So all of that will be delayed to then after the – and if you've driven Riney Road, you know the improvements need to be made before the school – it's a very narrow way also – before there's a ton of school traffic on there. We're simply just bringing it forward so that we can get your recommendation. It will go to council next Tuesday, but we felt that it was important to bring it forward just simply from the standpoint that we were not aware of the conversations and it was brought to our attention. So I guess my question is, was it – I guess Councilmember Davis asked you all to evaluate like the feasibility of adding a roundabout, or was it that you were asked to evaluate or someone at some point was asked to evaluate whether a roundabout at that intersection would be beneficial either for traffic flow, for safety, for pedestrians? What was the request? Yeah, the request that we received was basically to – would you look into if a roundabout could be constructed in that area? There's not a lot of information. The information we received is approximately two sentences, which is saying, "Hey, is there a possibility?" and staff saying, "Yes, we're happy to look into the possibility of putting in a roundabout in that area," which would have been a part of the design process if we would have been aware of it. Yeah, yeah. Which we would have done the feasibility assessment and my feelings, and I'm sure Kyle will concur, but we would have still gotten to the same point of a signalized intersection at this location, even with the evaluation being completed. Well, I'll say this. I mean, just my personal feedback, like if this were the work session that we're going to have in front of Council, I would say my top priority there would be pedestrian safety and bike safety because, as you mentioned, there is a ton of multifamily going in there. There are going to be two big schools. Ideally, all the folks who live in those multifamily will be sending their kids to walk to those schools, so hopefully that will be very heavy pedestrian traffic and whatever. If you can put something in here about what evidence you have that a signalized intersection is the safest option anyway, then yeah. Because I know that for smaller roadways, sometimes a roundabout is safer for pedestrians, right? But I think the idea is this is not going to remain a small roadway. So six lanes of traffic is a lot longer to get across than a smaller intersection. I would say I have major concerns about the idea of that becoming a six lane roadway at some point in the future, given how dense it's going to be and hopefully how much pedestrian traffic there will be. I would hope that we can keep it small to prioritize that pedestrian traffic. But regarding the roundabout, I'm sold. Sure. And I would say, too, that on Bonnie Rae Face 6, it has a ten foot side path on one side of the roadway and a five to eight foot, depending on the location and the easement on the west side. So we do have all of that as a part of the design that Kyle's been leading. I wonder, too, if there was an element of this that was like the person who requested this was interested in a roundabout for its traffic calming properties to keep traffic slow. Is there anything else that's in the works in the area for keeping traffic slow on Bonnie Rae and on Windsor? There's going to be multiple signalized intersections throughout. There's already a signal at 380 in Bonnie Rae. There'll be one at Windsor. There'll be one at Riney, Barackoway, and then, of course, one at Bonnie Rae and 77. So you're going to be stopping multiple times along that area where now you don't have that stop. I don't know if there's anything you'd like to add. Well, I think this is it. So we have the school zones that are being established in that area to slow traffic. There we go. Okay. Yeah. They're already implemented for the implementation of the high school, but we will have additional school zones with the new elementary school. So my feedback would be, yeah, just include that, aside about that in the presentation. Sure. Okay. If the point of a roundabout is to slow people down, here are some other ways we're already planning to slow people down. Thank you. Well, I'm not sold on a roundabout because just the massive scale of what it would be in that area. Right. And the number of children. There's just going to be so many families. You all have even been out there when they're doing football games and all of that. All of that's going to be taking place as well. So on Saturday mornings, we're very, very busy. With the parks. And that's another point that I didn't spend a lot of time focusing on. It is in the presentation. It's bringing up with the new high school and with new drivers trying to navigate a complicated roundabout with a lot of school pedestrian traffic. It's not a good solution, but we can add that. I can separate that out and add in some statistics to pilot it. So when this comes to council, I'm sure I'm going to not agree with it going forward. But my question is about Windsor. That's going to be a very large... Are we planning on expanding that in any way? Two lanes? What's going on on Windsor? So Windsor improvements are included with the Westgate project that's currently in design. We're bringing the design contract, I think on the 15th of council, to kick that off. So Windsor, the way it's necked down over by 35. So Windsor's going to be expanded when we rebuild Westgate, when we connect Westgate and log away to a through path there. Windsor's also going to be expanded out to 35 to its current configuration instead of necking down the two lanes. And with the textile I-35 expansion, they're also constructing an overpass, Windsor overpass, to bring it across 35 at that location. So that's going to just seal up that corner, that space there on the east side of Monterrey and of course the west side of Monterrey. I'm just noticing some construction, I guess they're moving utilities or something over there on Windsor. So yeah, that's a sanitary sewer upsizing upgrade. So that's tied together with the sewer master plan, the wastewater master plan. That project's almost completed and that's related to the future utility improvements up around 288, 288, 77 and I-35 that corner. Well that's, I didn't have any additional questions in that regard but I'm just, I'm not going to agree with it. We're just looking forward to having a really nice intersection here so we want to be pleased going through that way. Thank you. Thank you, Sal. Appreciate the feedback and you will see it Tuesday at council. So we'll make some modifications to the presentation and move forward with bringing that to council on Tuesday. Okay so we'll move on to EMC 22-031, Future Items for Mobility Committee Meeting 2022. Alrighty. Thank you so much, Logan. So we don't have any additional items that you asked for from the last meeting, but do want to just kind of go through what's been on the standing agenda. So Bonnie Bray, Kyle just did a great job of bringing you the update on Bonnie Bray Street. The Citywide Speed Study, I think we all know where that stands. We've had those conversations and that presentation was given on the 18th. I will note what you will see coming back and Brett will be working on this with Ismael, our new transportation engineer, is the ordinances specifically related to the speed study and breaking that down into the school zone ordinance versus the ordinance to make the modifications to the roadways with the recommendation. And that will not include the textile roadways at this point. So those ordinances you'll see come back, I believe, we currently have it slated for the December council meeting. On Hickory Creek Road, Phase 3, we did provide an update in the September staff report. There are not a lot of updates to that besides construction has started and moving right along. And then, of course, Ryan Road, same thing, we brought it back in September. And Ryan Road is still on hold until Hickory Creek gets to a point where the construction is to a point where we feel confident that we won't have both roads under construction at the same time. I will mention that Ryan Road is a part of the Denton County bond trip 2022 package. And then the TextDOT response, I just mentioned this, is that we've given all of that information to TextDOT. They told us it takes about six to eight months to receive the response on the citywide speed study. And so we're going to be working through that with them. That's really what we had on the agenda. I don't know if there's anything else that you would like to bring to our attention that you'd like for us to bring back. And Logan, I don't have the date for the November meeting on the top of my head, but I know November and December are going to be coming here before you know it and going to be fast. So one of the things we will want to make sure is that there's something on the agenda that we need to bring back forward because if there's not, there may not be any reason even to hold one of the committee meetings. So let's talk through that. And if I'm open to hearing what you have that you'd like for us to bring forward. I this is a direction. The overlay project is that related to the Microsoft Microsoft. It is now. Yes. Okay. So how are you all going to be handling that situation. Sure. So Microsoft specifically we can bring back a detailed report, you will be receiving a staff report in this Friday's report. Ethan Cox is the director of streets drainage and traffic and I along with several other staff members have been working through that from a contractual perspective. And we will be bringing that forward. Like I said in that in a Friday report item. I mean Ethan's also been in contact with the individuals that made the presentations to counsel on I guess to Tuesday nights ago. So as far as that overall process, not only are we working to make sure that the contractor comes back and we've been holding the contractor accountable to the measures of which they're supposed to be constructing. We also are looking at process improvements internally. And that's something that's being evaluated in a part of that overall. I currently is an ISR may turn to an LSR as we work through that. But that should our anticipation is that will be in your Friday report this week. That's our goal. Was this company nearly finished with that project or were they in the middle of it or were they just getting started when this presentation was done. The contractor has been completed with the work for some time and the presentations that were brought forward are after the fact. I've traveled some roads in my mind. I've said they should have done this road. Why was this road not done? So would it be would it be OK for us to maybe go through it since we're kind of we're having to go back to the contract. There are some roads out there that should have been included in this packet. Yeah. So I will tell you with micro selling we're getting to the point where we're not going to be able to do additional construction when the temperatures get below 40. You cannot do the construction. So we're at a very tight window holding the contractor accountable. We're working to have them completed with everything by November 18th and we're actually meeting for the next three hours to go through this internally and then with the contractor on all of their improvement measures. I would tell you there's particular criteria specifically related to the overall condition index to be used as a part of the overall micro selling. That would be the same thing for crack sale, the same thing for mill and overlay. So if there's particular red ways that you have questions about, I think the engaged in process is a fantastic way to submit that information. Or if you have a list of women, you want to send it to the city manager's office for us to evaluate. But I would tell you that any work to be completed would more than likely be something in next year's package. And we would want to explain to you the reason why it's a micro sale versus a crack sale versus a mill and overlay as it meets the particular criteria. Are you saying mill and overlay? Mill and overlay. And I-L-L. Mill. I-L-L. And. And. Mill and overlay. Mill and overlay. Okay. Yes, I'm sorry. Sometimes I talk really fast and my text is slaying deads and out. Can you tell me if my perception is accurate here? Okay. Because we, you know, staff came to us with a presentation about the micro seal project and explained OPI to us. And we learned about what the criteria were. And am I correct in my perception that the criteria just kind of weren't followed? It was a process error basically? There are some criteria and decisions that were made that we would like to improve in the future. And there are some standards that we're working around what we feel to be the best practice from a best management practice as to move forward. But I will say that the majority of what we're working through right now is, you know, as always with anything, right? We want to continuously improve and we want to make sure that we're adhering to the processes and procedures. And some of those are things that we would like to document better, right? So that's just a process and Ethan's working through those things. But I would tell you in many of the cases too, the contractor did not perform to the level of accuracy that we're comfortable with. And that's the reason why we're on week three of having a weekly meeting with them. And so I would tell you that, you know, that's part of the process is making sure that the contractor is going back and completing the work in the way that we feel like is going to meet the expectation within the small time frame of window that we have. And then of course next year Ethan and I both commit to making sure that it's done in a different manner. Thank you. Thanks for handling that. I mean, hey, mistakes happen in every organization and all you can do is learn from them. Absolutely. You know, especially since roads are, you know, aside from safety, it's the number one topic of any complaint. We're complaining when the roads are bad. We're complaining when they're getting fixed. And then we complain when they're fixed because people are driving too fast. So it just all goes together. Sure. But I was just very curious about, you know, where we were in terms of, you know, correcting. So you can answer that question. And I was certainly engaged in when I'm driving on the road, I'll be one of those people that will get out of my car and take a picture. Sure. And just, you know, to note it. Because I've driven down a few roads and I thought they didn't even get this road, they didn't even get that road. Right. So thank you. Yeah. I'm going to let Ethan add. I was just going to say to your last point about what's the plan for us to address some of the quality issues that we've seen. That is really the purpose of the meetings with our contractor the last few weeks. And we're actually meeting with them, like Becky said today, to review their repair plans. And so I think that is something that we're hoping to line out not just within the staff report, but also communications to the community for those roadways that do need some additional addressing. Did the city make the determination as to which roads were going to be done, or did we rely on this company? No, that was performed by staff. And I think that's where Becky's talking about. There are some process improvements that we need to take a look at. You know, generally the condition of the road is looked at in terms of prescribing maintenance and the type of maintenance that will be performed. You know, for mill and overlay, you are looking at roads that are in good or better condition. It's a preventative treatment. You put a surface on top of the roadway. That's really there to preserve the underlying pavement, prevent oxidation, prevent water from penetrating it. So I think, you know, in some cases when you look at a roadway, you say, "Man, that really needs some work." For micro seal, you're really looking at smaller or moderate, you know, defects like small cracks. Maybe it was patched because a utility was cut. Those are the types of things that we would look at for micro seal. And I think just kind of looking at the process moving forward is making sure, like Becky said, we have a solid process to follow. It's documented well. And then when we push this out to the community, make sure that they understand, yes, your roadway is in good condition. This is a preventative measure so we can make sure that the roadway lasts as long as the -- we can extend the roadway's life as long as we can. Just a common thought process would be more aesthetics than the actual safety feature of the road. Thank you all very much. Did you have anything else? So I have, I guess, a question about -- so obviously 2181 is open now. I know I've reached out to you and also to the county tech stat engineer just with some questions about certain intersections and disability issues and whatever. And so I know that there's going to be kind of an ongoing process of monitoring those intersections, seeing if any other changes or adjustments need to be made. Obviously, that's not a city roadway, so if people have concerns about it, they should not put it in engage then. They can. Okay. So let me talk to you a little bit about that. So Travis and I, Campbell and I, the area engineer for the county have a great relationship. I'm sorry, for tech stat, have a great relationship. He and I actually talked last night. We typically, when we receive response from and engaged in that involves tech stat, we give specific contact information. What he and I discussed last night, and I'm waiting on the information because Logan needs it, is actually providing not only the contact information and telephone number, they have a system similar to Engage Denton where people can submit and I'm waiting on that information. And he's working to get that over to us. He also has links to their standard process of projects that are either in the planning, design, or construction phase. When you're talking specifically about 2181, and you may or may not be aware of this, any signal within the city of Denton, Ethan's team through Traffic Operations and James Andrews is responsible for, that's a collaboration that we do with tech stat. And what I'd mentioned on 2181 is we've received a lot of feedback in regards to Cedar Creek, which is near Geyer High School, Sundown Ranch, and then a couple of other intersections that the questions are about median cuts and signalization. It even came from our own police department and our safety resource officers that are at those high schools, or at the high school I should say. So we've worked on some collaboration. Brett's been a part of those signal conversations also. And there will be some additional signals that are added in some of those locations. Now I say that to tell you Sundown and Cedar Creek we know for sure we're going to be adding signals too. There are other areas where possibilities of signals might be needed, but what we will do in coordinate with tech stat, and I think probably what you've heard is, we will be working through a process to evaluate the road, the safety of the road, the speed of the road, the concerns we get, the complaints if there's crash data. Anything that is a data resource that we can say this is not operating or functioning the way the intention was. And then that's where we would do evaluations of we need to look at this intersection, a study needs to be performed to make sure it meets warrants is what it is called for a signal. And so there's multiple areas throughout 2181. And actually I'll expand that to tell you that tech stat and ourselves will be meeting next week with Brett and Ethan and several other folks to actually talk specifically about signals and areas of which we feel like there are additional signals that are needed. There are a couple on 2499 that have come to our mind. Brett is leading the entire program. So it's a collaboration and there's an actual what's called the Highway Safety Improvement Program that Brett is currently managing. We're single and you're aware of this because this is from RTC. But the HSIP program, we have a number of signals. One specific one that I know has been of interest is at Discovery Park and 77. And so we do have the signal. It's currently in design and Brett's leading that. But we will be installing a signal at that location along with four other locations. But I tell you that to say that those have received the funding. We're paying for the design. The construction is something TechStat pays for up until a certain extent. And then sometimes we have to kick in additional funding. But the approach we're going to use this year for submitting for new Highway Safety Improvement Program projects is to actually involve TechStat on the areas and the PD on the areas of which we've seen situations that maybe require or need an additional signal or large developments. And we also are evaluating a list where certain developments are paying for a portion of a signal. And so they've already put in some participation. So that's something we could submit to say. And I'm just using round numbers. Development X already submitted $125,000. The signal costs $600,000. We're a fourth of the way there or whatever. Can we get the other funding that's needed from TechStat? So we've got several different areas and we're going to approach it a little bit differently this year. That's great. I'm really glad to hear that. Very comprehensive answer. That's fantastic. Any sense of so like if something that's not a signal issue. I'll trust that signal issues are in the works. Like, for example, someone emailed me with a concern about like a visibility issue. And I kind of just emailed that. And he also emailed Travis. And I think you emailed Travis Campbell about that. And TechStat did something that took care of it. Sure. Would you prefer that those types of concerns be sent in through TechStat's version of Engaged In? You know, I think TechStat's preference would be that the sooner they know about a concern, the faster they can fix something, especially if it's a project in construction. If I'm thinking about the one you were referring to where there were three concerns, TechStat's working with the city on solutions in those areas. Like a line of visibility issue? Yes, a site issue. And we actually met with them last Wednesday to go through all of those. A couple of them have already been addressed or are working to be addressed. There's one additional one that's a little bit more difficult. But that response has been given back by TechStat to the individual who brought that to their concern. My apologies for just asking a question that's about my personal curiosity. But what was done to address it? Just because I don't even know. So in certain situations, if the sound wall was in the way, portions of the sound wall could be removed. Or if in certain situations, a lot of times the line of sight is where the stop bar is, because that's where cars have to go to, the stop bar might be moved up. But then we worry about the conflict with the pedestrian traffic. So the stop bar might be moved up, but the pedestrian traffic might have to be rerouted. And so I'll give you an example where we actually pushed the pedestrian traffic kind of at more of an angle and then brought it back across and brought it back up so that we could move the stop bar forward so you could see to get to the intersection. So there's intersection design that goes into those types of conversations. Okay, thank you for that. Of course. That totally answers my question. Okay, perfect. So anything particular that you see as a future item to bring forward? I don't think so. I mean, I even feel like the micro-sealed thing is fine for a Friday report for me. I agree as well. Okay, perfect. So then I would say if anything comes up between now and maybe the week of Thanksgiving or the week before Thanksgiving, then we will look to add it to the agenda. If not, then it might be a possibility that the November 30th meeting, we might skip the November 30th and have the December. I know you mentioned that. We don't have a December 1. We don't have a December 1. But we do have to solidify a 2022 schedule at the next meeting. So we have to have another one. Okay. But it may be just doing that. We're here for a question for Ben, I guess. Is that something that can just be done via email? It typically has to take a vote. Yeah. Okay. We'll come back. We'll come back in November. I'm fine with November. I'm probably not going to be here, but if you would press the finger. Well, since I have no light, I'll be here. We can work through that, too, if there's something that can be done fairly quick through the process. And, you know, of course, John can always bring an update. And there may be something we decide that's a topic maybe that we could bring forward. We'll discuss it. I'm thinking DCTA may also be here, but I'm not 100% on it. Yeah. So DCTA is trying to work to continue to bring you an update, too. We're working to sync up where, Councilmember McGuire, your update's not at the same time as theirs. So there's different. So we can work through that. So we'll see. And I think that that makes sense. And we'll make sure we bring forward the calendar, too, so that we can get the calendar set for the 2023 calendar year. It's hard to believe we're already talking about that. Well, then thank y'all. If nothing else, I know we have the calendar, ITS report, possible DCTA. And then we'll discuss internally if there's anything additional to bring forward. And we appreciate it. Thank you. Well, we will close the meeting at 1110. Thank you. Thank you, everybody. Thank you very much.