1 00:00:00,000 --> 00:00:07,900 Good morning. Welcome to the mobility committee meeting. Seeing that we have a quorum present, 2 00:00:07,900 --> 00:00:13,540 we'll begin with considering approval of the minutes. I'll entertain a motion. After the 3 00:00:13,540 --> 00:00:25,980 minutes of September 11th. Okay. Minutes are approved. I must confess to you that I've 4 00:00:25,980 --> 00:00:29,940 been approached a couple of months in a row saying we don't really have any action items 5 00:00:29,940 --> 00:00:35,440 is it okay if we don't meet and we're meeting if you're not happy about being here you can 6 00:00:35,440 --> 00:00:40,280 blame me because I asked for the agenda items that we're talking about for when we don't 7 00:00:40,280 --> 00:00:45,420 have action items that there are things that we can keep making progress on and I'm looking 8 00:00:45,420 --> 00:00:54,460 forward to a good discussion. So one of the first ones is item B. Oh, you have to vote 9 00:00:54,460 --> 00:01:02,800 on the minutes? Okay. All in favor of approval of the minutes? Aye. Approved. Now item B. 10 00:01:02,800 --> 00:01:07,440 If you -- it's to receive a report, hold a discussion, provide direction on the metropolitan 11 00:01:07,440 --> 00:01:12,240 transportation plan policy bundle, a program in which applicants can receive transportation 12 00:01:12,240 --> 00:01:17,020 development credits. And you may recall that we had this item before and we gave direction 13 00:01:17,020 --> 00:01:23,360 that this is a pretty good list of ideas and that we should first of all see if we can 14 00:01:23,360 --> 00:01:31,760 meet the requirements, but also in general, you know, keep chipping away at it. Not stopping 15 00:01:31,760 --> 00:01:36,880 ourselves necessarily at 10, but just seeing if there are other good ideas we might want 16 00:01:36,880 --> 00:01:44,320 to adopt. So anyway, happy to move forward in here. Okay. So my name is -- traffic engineer 17 00:01:44,320 --> 00:01:50,800 for the city. I'll be the new staff liaison for this particular committee and -- welcome 18 00:01:50,800 --> 00:01:56,900 and congratulations. Thank you. And for this particular item, I would like Katie to present 19 00:01:56,900 --> 00:02:01,720 the item and then if there are any discussions, questions, we're more than happy to answer 20 00:02:01,720 --> 00:02:19,600 any questions. Can y'all hear me okay? Bring this up. Okay. So we've got -- okay. Good 21 00:02:19,600 --> 00:02:23,760 morning, committee members. Thank you for being here today. My name is Katie Welch and 22 00:02:23,760 --> 00:02:28,120 I'm from the capital projects department and I'm going to be giving an overview on the 23 00:02:28,120 --> 00:02:35,280 metropolitan transportation plan policy bundle. So to begin with an overview of what the program 24 00:02:35,280 --> 00:02:40,000 is, the north central Texas council of governments has a metropolitan transportation plan that 25 00:02:40,000 --> 00:02:46,360 they call mobility 2045 that lays out a blueprint for how the region will meet the transportation 26 00:02:46,360 --> 00:02:53,000 goals and needs over the next 20 plus years. And included in this metropolitan plan are 27 00:02:53,000 --> 00:02:58,440 recommended policies, programs, and procedures that they encourage public entities within 28 00:02:58,440 --> 00:03:04,560 the DFW area to pursue in order to help meet these needs. The council of governments however 29 00:03:04,560 --> 00:03:09,120 knows that infrastructure projects alone are not going to help completely meet the needs 30 00:03:09,120 --> 00:03:13,480 and the goals over the next 20 years. So they kind of came up with this program in order 31 00:03:13,480 --> 00:03:20,280 to encourage cities to voluntarily adopt these recommended policies. So the way the program 32 00:03:20,280 --> 00:03:25,660 works is that applicants who apply, if they meet at least 50% of the policies like you 33 00:03:25,660 --> 00:03:31,200 were saying, then they get something called transportation development credits. And what 34 00:03:31,200 --> 00:03:36,960 these credits are, are they can be used to help offset local funding matches whenever 35 00:03:36,960 --> 00:03:41,600 we have transportation projects that require a local match that are federally funded. So 36 00:03:41,600 --> 00:03:45,040 these credits will be used towards the local match and we'll end up saving the city some 37 00:03:45,040 --> 00:03:51,640 money on the project throughout construction. So that's just an overview of the program. 38 00:03:51,640 --> 00:03:56,480 But today we were going to go into the different policies, where we're at with them, and some 39 00:03:56,480 --> 00:04:03,040 next steps on how this application process works. So there's a total of 21 policies in 40 00:04:03,040 --> 00:04:08,400 the program. And in order for the city to qualify to get the credits, we have to meet 41 00:04:08,400 --> 00:04:12,280 at least 10 of them. And as you can see up here in all of the different colors, these 42 00:04:12,280 --> 00:04:17,800 are kind of the categories they span. There's 11 different topic areas that the policies 43 00:04:17,800 --> 00:04:23,280 fall into. And the way that we've broken them up to present today are going to be policies 44 00:04:23,280 --> 00:04:29,120 that we are currently satisfying in the city and that all we need to do is gather documentation, 45 00:04:29,120 --> 00:04:33,240 but we'll be good to go for submission. We have a category of policies that we're most 46 00:04:33,240 --> 00:04:37,360 likely satisfying. We need to confirm with the Council of Governments that what we're 47 00:04:37,360 --> 00:04:42,100 doing will meet the criteria of what they're expecting, just to make sure when we submit 48 00:04:42,100 --> 00:04:46,000 we're not missing anything and we end up not getting the credit for it. So those are ones 49 00:04:46,000 --> 00:04:50,440 we have a couple questions on. And then we have a set of policies in this program that 50 00:04:50,440 --> 00:04:55,920 we may or may not be already doing as a city and we need to do some further research into 51 00:04:55,920 --> 00:05:01,320 in order to see what our next steps will be to fully check them off the list. 52 00:05:01,320 --> 00:05:06,160 So we were going to start today with the five policies that we are currently meeting. All 53 00:05:06,160 --> 00:05:12,720 we have to do is gather documentation but these are going to be ready to go. They include 54 00:05:12,720 --> 00:05:17,880 having a clean fleet policy in place, which we do as a city. Engaging in school siting 55 00:05:17,880 --> 00:05:23,300 coordination, which involves the city, local independent school districts, and then TextDOT 56 00:05:23,300 --> 00:05:27,440 meeting together to talk about future growth plans, which the city has engaged in. So we've 57 00:05:27,440 --> 00:05:33,120 got that one ready. Engaging in storm water management practices for sustainable storm 58 00:05:33,120 --> 00:05:38,400 water management. Having transit funding, which means we're contributing to our local 59 00:05:38,400 --> 00:05:42,520 transit authority. We do that. So we've got that one check marked. And then having an 60 00:05:42,520 --> 00:05:47,280 idling restrictions policy in place, we've got that one good to go as well. And I'm kind 61 00:05:47,280 --> 00:05:51,440 of briefly going through these, but if you have any questions about specifics or what 62 00:05:51,440 --> 00:05:56,680 more information stop me and we can go into more detail. 63 00:05:56,680 --> 00:06:02,120 So these next eight are ones that we're more than likely meeting, but we want to coordinate 64 00:06:02,120 --> 00:06:06,120 and confirm with council of governments that what we're doing meets their requirements. 65 00:06:06,120 --> 00:06:11,960 So I was going to briefly read through these. We've got copper theft, parking management, 66 00:06:11,960 --> 00:06:18,120 safe access to schools, railroad safety, land use strategies, clean construction, complete 67 00:06:18,120 --> 00:06:24,060 streets policy, and something they call transit funding level two. The good news is that if 68 00:06:24,060 --> 00:06:28,560 we get confirmation that we're meeting these eight, that puts us at 13, which means we've 69 00:06:28,560 --> 00:06:35,800 got the 10 required ones off check marked off and are above the 50% threshold. So next 70 00:06:35,800 --> 00:06:38,800 steps are really going to be confirming that we've got these. And I think that will get 71 00:06:38,800 --> 00:06:42,720 us through the finish line for the application. 72 00:06:42,720 --> 00:06:52,840 So if we meet more than the 50%, say 13, say we end up getting 20, do we get any more funding? 73 00:06:52,840 --> 00:06:57,040 I was wondering that too. That's something I need to confirm with council of governments 74 00:06:57,040 --> 00:07:00,640 because I was thinking that would be good if it worked that way. So I can get back to 75 00:07:00,640 --> 00:07:07,960 you on that. Any other questions on this slide in particular? 76 00:07:07,960 --> 00:07:14,560 >> Seeing none. 77 00:07:14,560 --> 00:07:19,760 >> And then these last eight policies are going to be ones that we're saying we may or may 78 00:07:19,760 --> 00:07:25,800 not meet. Really what that means is we either have partial activities in place that are 79 00:07:25,800 --> 00:07:29,160 going towards these policies or we don't have anything at all, but we need to do some more 80 00:07:29,160 --> 00:07:34,480 internal research within the city to see what we're doing, work with cog to figure out what 81 00:07:34,480 --> 00:07:38,040 our next steps are going to be and kind of get a timeline in place to see if we'll get 82 00:07:38,040 --> 00:07:43,400 these before the April deadline, which I'll get to in the next slide. So these are going 83 00:07:43,400 --> 00:07:50,920 to be urban thoroughfare revitalization, traffic integration, traffic incident management, 84 00:07:50,920 --> 00:07:56,760 city oriented development, wrong way driving policies, securing transportation infrastructure, 85 00:07:56,760 --> 00:08:03,440 employer trip reduction program and unmanned aircraft system policies. So these eight, 86 00:08:03,440 --> 00:08:08,180 some of the next steps for these are going to be determining next steps for what will 87 00:08:08,180 --> 00:08:12,800 make these whole and then kind of prioritizing which ones we want to pursue and working with 88 00:08:12,800 --> 00:08:17,360 the committee to see which ones we're interested in, what we want to try to get on our application 89 00:08:17,360 --> 00:08:19,320 for the spring deadline. 90 00:08:19,320 --> 00:08:23,760 I thought I remember hearing in one or another legislative briefing that unmanned aircraft 91 00:08:23,760 --> 00:08:28,600 systems are going to be regulated at other than local level. 92 00:08:28,600 --> 00:08:33,400 You know, it's interesting you say that because someone had mentioned to me that this one 93 00:08:33,400 --> 00:08:40,500 may or may not stay on this list for the 2019 policy bundle program. This is, they haven't 94 00:08:40,500 --> 00:08:44,160 released the official application yet, so this is kind of information we have working 95 00:08:44,160 --> 00:08:50,280 with them up until that point. So that actually may be why someone had said that. So that's 96 00:08:50,280 --> 00:08:55,440 good to know. They said they should be releasing the official list in the next couple weeks 97 00:08:55,440 --> 00:09:01,240 and that everything will stay the same except that one may or may not be on there. 98 00:09:01,240 --> 00:09:07,440 So we can provide an update once we get the official list. 99 00:09:07,440 --> 00:09:15,520 So going on to the schedule for this application process, so within sometime this month of 100 00:09:15,520 --> 00:09:20,000 November we should be receiving the application. We've sent in our request, so as soon as they're 101 00:09:20,000 --> 00:09:25,680 ready to release we'll be on the list to get the application. And it will be due in spring 102 00:09:25,680 --> 00:09:31,960 of 2019. They haven't released the official due date yet, but they, in talking with Council 103 00:09:31,960 --> 00:09:37,000 of Governments, they said that more than likely March 2019 will be the early deadline, April 104 00:09:37,000 --> 00:09:42,320 will be the final deadline, so it gives us a month to submit and then have any questions 105 00:09:42,320 --> 00:09:48,960 addressed if there's any problems with our application. So that's kind of what they're 106 00:09:48,960 --> 00:09:53,920 saying is going to be the schedule as of now. And so in the meantime, what our next steps 107 00:09:53,920 --> 00:09:58,800 are going to be between now and spring is finalizing the documentation on the five that 108 00:09:58,800 --> 00:10:04,040 we know we're meeting, working with Council of Governments to confirm the eight that we're 109 00:10:04,040 --> 00:10:07,880 pretty positive we're meeting, tying up any loose ends, if there's anything we may be 110 00:10:07,880 --> 00:10:13,920 short on, gathering that documentation, and then those last eight that we have, determining 111 00:10:13,920 --> 00:10:17,560 next steps and kind of prioritizing which ones we want to try to get on that application 112 00:10:17,560 --> 00:10:25,600 as well. So we'll submit in spring. They said it'll take a couple of months to review applications, 113 00:10:25,600 --> 00:10:30,800 determine funding levels, but around May of '19 we can start talking with the Council 114 00:10:30,800 --> 00:10:35,200 of Governments about which transportation project or projects we want to use these credits 115 00:10:35,200 --> 00:10:42,760 towards and start getting that on their radar. So that'll be the process. And that's what 116 00:10:42,760 --> 00:10:45,280 I have for you. 117 00:10:45,280 --> 00:10:51,760 On the process, because I do see, and I know that some of these items are from various 118 00:10:51,760 --> 00:10:59,520 departments, so will the responsible department be the one that is going to reach out and 119 00:10:59,520 --> 00:11:04,200 see if that qualifies, or is there going to be one person in charge of the application 120 00:11:04,200 --> 00:11:08,480 doing all of these things, just for clarity? 121 00:11:08,480 --> 00:11:13,040 It's going to be one person in charge of the overall application, coordinating with the 122 00:11:13,040 --> 00:11:18,160 internal departments, coordinating with COG, and making sure all of our loose ends are 123 00:11:18,160 --> 00:11:23,160 tied up and everything we have is together. So there'll be staff contacts, but one person 124 00:11:23,160 --> 00:11:24,160 managing the information. 125 00:11:24,160 --> 00:11:28,320 Yes, there will be one project manager that keeps tabs on everything. That way you're 126 00:11:28,320 --> 00:11:32,320 not lost in translation pretty much. 127 00:11:32,320 --> 00:11:38,320 Right. And so my follow-up question to that, if there is something within the eight that 128 00:11:38,320 --> 00:11:44,400 we think we are, will there be plenty of time to get those documents or policies to Council 129 00:11:44,400 --> 00:11:51,920 for update or amendments if there's something that we need to change? 130 00:11:51,920 --> 00:11:56,480 That's a good question. There may be time. We're going to assess through December, so 131 00:11:56,480 --> 00:12:02,120 we do have three months to get it on the agenda and see if there are some ordinances that 132 00:12:02,120 --> 00:12:07,200 are required to put this in place, to get us across the line, at least for the first 133 00:12:07,200 --> 00:12:11,480 hand. Definitely we'll make an effort to get it done. 134 00:12:11,480 --> 00:12:15,960 I do think in the next couple of weeks we're really going to hit hard on working with Council 135 00:12:15,960 --> 00:12:20,440 of Governments to determine next steps. So ordinances we have in place right now that 136 00:12:20,440 --> 00:12:25,440 we think are from 2015, for example, that we think will get us there. If we find out 137 00:12:25,440 --> 00:12:32,960 otherwise, we'll make sure to prioritize that as one of the first things we do. 138 00:12:32,960 --> 00:12:40,640 So clearly to respond to the incentive, your priority is clearing the five and then the 139 00:12:40,640 --> 00:12:49,000 eight, and we can lose three and still secure the credits. But what I hoped that we might 140 00:12:49,000 --> 00:12:58,520 do in this session is to see among us, staff and the committee, see if the others that 141 00:12:58,520 --> 00:13:02,800 are the ones that just on their own merits, we just think are good ideas worth pursuing, 142 00:13:02,800 --> 00:13:06,520 and maybe if there's some that we feel more strongly about than others. 143 00:13:06,520 --> 00:13:09,800 So you're talking about the last eight that we're talking about. Can you pull up the 144 00:13:09,800 --> 00:13:13,600 slides so that we can... Because we've previously given direction 145 00:13:13,600 --> 00:13:18,720 that yeah, if there's things we already meet and we can get money, we're in favor of that. 146 00:13:18,720 --> 00:13:25,560 So this is beyond that. Are these good ideas that we would just like to take as suggestions? 147 00:13:25,560 --> 00:13:29,360 We can go through these if you want and give you an update on where we're at with each 148 00:13:29,360 --> 00:13:35,920 of these eight. We've got some notes on partial activities we're doing. So if we want to start 149 00:13:35,920 --> 00:13:40,600 with the urban thoroughfare revitalization... Maybe if you wouldn't mind touching on sort 150 00:13:40,600 --> 00:13:45,240 of what's the objective of each one? Of each one, yes. Okay. So for this first 151 00:13:45,240 --> 00:13:50,960 one, it's implement land use and transportation programs and policies to revitalize and redevelop 152 00:13:50,960 --> 00:13:55,840 aging infrastructure to provide context-sensitive solutions for urban thoroughfares on the state 153 00:13:55,840 --> 00:14:00,120 roadway systems and other important community roadways is the description they give. 154 00:14:00,120 --> 00:14:01,880 Yeah, what does that mean? I know. 155 00:14:01,880 --> 00:14:06,160 Context-sensitive... So quick answer to that one. It's a pretty 156 00:14:06,160 --> 00:14:13,320 long discussion, but are we communicating or integrating our transportation solutions 157 00:14:13,320 --> 00:14:19,880 with the land use? That's the bigger picture. Are we working with the development community 158 00:14:19,880 --> 00:14:25,240 and with our planning department so that we have the right type of mix of land uses that 159 00:14:25,240 --> 00:14:33,880 contributes towards the transportation system that exists? In a sense, if you have a Elmond 160 00:14:33,880 --> 00:14:40,080 Locust, in future, whenever development comes along that street, when we're planning Elmond 161 00:14:40,080 --> 00:14:45,600 Locust, can we plan bike lanes or can we plan wider sidewalks with the new development and 162 00:14:45,600 --> 00:14:51,080 land use coming in place? So that's... Are you taking big picture and making sure that 163 00:14:51,080 --> 00:14:56,920 all your land uses and the transportation system lines up? That's the context-sensitive 164 00:14:56,920 --> 00:15:00,320 nature of the design. So what would count as evidence of our doing 165 00:15:00,320 --> 00:15:03,080 that? And so the reason this is one that we need 166 00:15:03,080 --> 00:15:08,320 to do a little further research on is we have mention of context-sensitive solutions in our 167 00:15:08,320 --> 00:15:15,000 comprehensive plan, the Denton 2030 plan, and then we also redevelop our aging infrastructure. 168 00:15:15,000 --> 00:15:18,900 A lot of our capital projects are doing that right now. So what we need to do is work with 169 00:15:18,900 --> 00:15:23,560 development services and see if we have any formal policies in place. I believe this is 170 00:15:23,560 --> 00:15:29,640 one that needs governing body approval, so something that's been approved by our council, 171 00:15:29,640 --> 00:15:33,200 our comprehensive plan has. So it's just going to be a little more coordination with development 172 00:15:33,200 --> 00:15:39,200 services, determining what they're doing, working with council of governments to determine 173 00:15:39,200 --> 00:15:44,120 does this meet the criteria? So a bit more research than that previous eight that you 174 00:15:44,120 --> 00:15:48,160 had seen up there. So on the engineering side, we did take to 175 00:15:48,160 --> 00:15:54,240 council our transportation criteria manuals, and that really ties the complete street portion 176 00:15:54,240 --> 00:16:00,480 on the transportation side. So yes, we have some components on the development services 177 00:16:00,480 --> 00:16:05,760 side and some components in the transportation side. All we have to do at this point is are 178 00:16:05,760 --> 00:16:10,960 these enough and fit the CAWC criteria? That's the only thing that we're going to look into 179 00:16:10,960 --> 00:16:16,880 and see if they're accepting that. If not, then if there is a formal ordinance or what 180 00:16:16,880 --> 00:16:21,040 is required, and that's why this is on this list where we don't know yet. We don't have 181 00:16:21,040 --> 00:16:24,040 enough information to make that decision. >> Any other questions? 182 00:16:24,040 --> 00:16:28,800 >> Well, just more of a comment, that we are also working on the zoning map update, which 183 00:16:28,800 --> 00:16:33,560 kind of when you see thoroughfare revitalization, it feels like that kind of hits on that a 184 00:16:33,560 --> 00:16:39,280 little bit, and so I don't know if that would -- if that needs to be passed or not ahead 185 00:16:39,280 --> 00:16:41,880 of time. >> Do you have a comment, Todd? 186 00:16:41,880 --> 00:16:46,480 >> So to go in line with what you're saying, part of what goes with the zoning update is 187 00:16:46,480 --> 00:16:52,100 the master thoroughfare plan that we're creating and updating this year. That would be a big 188 00:16:52,100 --> 00:16:55,680 component of that, because that's really where you address the context-sensitive nature of 189 00:16:55,680 --> 00:17:00,720 these corridors, as you specifically stated in that plan. This is the process we'll utilize 190 00:17:00,720 --> 00:17:04,960 for design as we go through putting these projects in the ground, and you lay out the 191 00:17:04,960 --> 00:17:08,480 groundwork for what does that look like. So we'll visit those cross-sections and what 192 00:17:08,480 --> 00:17:14,560 do they look like, not from an engineering sense but from a true visual and contextual 193 00:17:14,560 --> 00:17:17,960 sense, what are those elements, what are some examples, how does that get rolled in, and 194 00:17:17,960 --> 00:17:23,240 then that would go back to council for approval. >> So it's kind of like the complete streets 195 00:17:23,240 --> 00:17:25,980 objective? >> It is. It is absolutely the complete streets 196 00:17:25,980 --> 00:17:28,720 objective. >> Okay. So part of what I'm listening for 197 00:17:28,720 --> 00:17:32,760 is to describe these as, you know, will it actually lead us to -- like, we don't need 198 00:17:32,760 --> 00:17:36,680 extra brownie points, but will it lead us to do something different that, you know, 199 00:17:36,680 --> 00:17:40,920 is constructive and sounds like it would, and that's actually one of our eight things 200 00:17:40,920 --> 00:17:46,240 we agreed to work on, you know, through a treat, so, okay. 201 00:17:46,240 --> 00:17:47,240 >> Awesome. >> Carry on. 202 00:17:47,240 --> 00:17:52,200 >> Okay. So the next one we have is called integration. 203 00:17:52,200 --> 00:17:57,400 What this has to do with is integrating all of our traffic operation systems between public 204 00:17:57,400 --> 00:18:01,600 sector entities, including the sharing of data and video is the description they give 205 00:18:01,600 --> 00:18:07,520 for this particular policy. So the thing that we are currently doing that 206 00:18:07,520 --> 00:18:12,320 we think may get us a check mark on this one is the Waze initiative. 207 00:18:12,320 --> 00:18:16,080 We are currently right now with that kind of looking at the risk assessment of data 208 00:18:16,080 --> 00:18:20,200 sharing with -- through this Waze program and are going to be working with our risk 209 00:18:20,200 --> 00:18:25,880 management and legal team to kind of get a risk management plan in place, but we're thinking 210 00:18:25,880 --> 00:18:31,120 that may be what we can end up pursuing to check this one off. 211 00:18:31,120 --> 00:18:36,040 >> But again, not in terms of, like, the brownie points, because the checking off doesn't benefit 212 00:18:36,040 --> 00:18:45,320 us anymore, but in terms of the substantive, you know, policy benefit, it's what this might 213 00:18:45,320 --> 00:18:50,280 spark us to do. This is all a question, like, did I understand 214 00:18:50,280 --> 00:18:51,280 you. The thing we might be doing is integrating 215 00:18:51,280 --> 00:18:52,280 with Waze. >> Yes. 216 00:18:52,280 --> 00:18:57,240 And sharing traffic data both ways. >> Some of the other things that we're doing 217 00:18:57,240 --> 00:19:01,400 that would fall under the same category is we build out our fiber optic network with 218 00:19:01,400 --> 00:19:06,520 IT. We integrate all of our signals with that. 219 00:19:06,520 --> 00:19:10,120 That in and of itself wouldn't get you there, but what it does is the agreement we have 220 00:19:10,120 --> 00:19:14,800 with TechStop where we'll integrate their system with our system so that they can see 221 00:19:14,800 --> 00:19:18,560 the corridors along I-35. Most communities have some kind of arrangement 222 00:19:18,560 --> 00:19:21,520 along the interstate system where they're already doing that. 223 00:19:21,520 --> 00:19:25,320 So items of that nature would also come into play here. 224 00:19:25,320 --> 00:19:29,880 We're also looking at, you know, another potential would be with the rail system as we put in 225 00:19:29,880 --> 00:19:35,000 quiet zones, we also put in video and audio monitoring so that we can actively understand 226 00:19:35,000 --> 00:19:38,000 when the horns are blown. That would be something we'd add into that 227 00:19:38,000 --> 00:19:41,840 system as well. >> Okay. 228 00:19:41,840 --> 00:19:45,520 So the next one is going to be traffic incident management. 229 00:19:45,520 --> 00:19:49,720 This one is implementing comprehensive and coordinated approaches to traffic incident 230 00:19:49,720 --> 00:19:54,360 management. And they say requiring a comprehensive coordinated 231 00:19:54,360 --> 00:19:59,520 interagency approach to traffic incident management in the North Texas region, including tracking 232 00:19:59,520 --> 00:20:05,900 performance measures based on regional definitions, collecting data and monitoring progress. 233 00:20:05,900 --> 00:20:10,240 This applies to local governments, they say, that responds to freeway incidents. 234 00:20:10,240 --> 00:20:14,860 >> So Todd started talking about this. This is coordinated with TechStop and making 235 00:20:14,860 --> 00:20:22,440 sure us as a local government responding to emergency, you know, services or, you know, 236 00:20:22,440 --> 00:20:31,440 accidents or any of the -- anything on the freeways or the TechStop highways, how prepared 237 00:20:31,440 --> 00:20:37,000 are we and what is our plan and how do we communicate in an efficient way? 238 00:20:37,000 --> 00:20:42,400 So putting that traffic management center, connecting it through fiber, monitoring it, 239 00:20:42,400 --> 00:20:46,440 once we have that in place, we're already working towards it, and then we can better 240 00:20:46,440 --> 00:20:52,200 communicate with TechStop and/or other cities that are responding to the same incident on 241 00:20:52,200 --> 00:20:59,280 the border or somewhere in the whole region. So yeah, at some point we will address this, 242 00:20:59,280 --> 00:21:03,160 but with the traffic management center not ready, we're not there yet, but definitely 243 00:21:03,160 --> 00:21:09,880 we're working on this. >> The next one is freight-oriented development. 244 00:21:09,880 --> 00:21:16,080 So this is in regards to enhancing freight-oriented land use sustainability by requiring local 245 00:21:16,080 --> 00:21:22,400 governments to adopt compatible zoning requirements in properties adjacent to freight-oriented 246 00:21:22,400 --> 00:21:26,760 development areas. >> And what is the goal of the freight, you 247 00:21:26,760 --> 00:21:34,680 know, focus in this? >> So this is more in line of -- when you're 248 00:21:34,680 --> 00:21:40,800 looking at a transportation system overall, one of the largest components is freight. 249 00:21:40,800 --> 00:21:46,000 How do you deliver goods? Are you using rail, which is one of the major 250 00:21:46,000 --> 00:21:54,240 ones, air, water, or the last one is roadways? So if you're really dependent on the roadway 251 00:21:54,240 --> 00:21:59,800 system and truck traffic to deliver that kind of goods, that means you're not really better 252 00:21:59,800 --> 00:22:06,800 planning or differentiating or making an effort to have a full, complete street segment in 253 00:22:06,800 --> 00:22:09,880 there. So you're more focused on delivering goods 254 00:22:09,880 --> 00:22:17,080 through a street network, but on our end, what they want to see, and most of these local 255 00:22:17,080 --> 00:22:22,080 agencies do, is do they have a freight plan? Do they have different options for freight? 256 00:22:22,080 --> 00:22:27,360 How are they addressing that? So we do have some type of land use and freight 257 00:22:27,360 --> 00:22:32,520 integration on our west side of the city by the airport where there are railroads coming 258 00:22:32,520 --> 00:22:36,800 in, there are connections, nodes, as well as the airport is right there, and then our 259 00:22:36,800 --> 00:22:43,100 land use lends to it as far as warehousing, manufacturing, industrial, that helps integrate 260 00:22:43,100 --> 00:22:48,800 that piece, and we're planning in that direction. So that becomes our freight area and freight 261 00:22:48,800 --> 00:22:55,760 corridor, and that's separate from our entire other operations and other use of our street 262 00:22:55,760 --> 00:22:58,880 network. >> Take pressure off of the street network. 263 00:22:58,880 --> 00:23:05,680 >> Correct. >> So the next one is wrongway driving. 264 00:23:05,680 --> 00:23:12,080 This is basically having these policies in place that prevent wrongway driving accidents, 265 00:23:12,080 --> 00:23:16,840 and one thing that we need to do further research on is work with our police department to kind 266 00:23:16,840 --> 00:23:21,120 of get some data on the past eight to ten years, how many wrongway driving accidents 267 00:23:21,120 --> 00:23:25,360 have we had? Do we have policies in place already that are preventing this? Mechanisms 268 00:23:25,360 --> 00:23:31,720 in place that are preventing this? So that was going to be our next steps on this item. 269 00:23:31,720 --> 00:23:34,600 >> Wouldn't getting rid of one-way streets fix that? 270 00:23:34,600 --> 00:23:44,680 >> Actually, this policy is more focused on freeways and roadways, more so than local 271 00:23:44,680 --> 00:23:52,040 streets. Our internal arterials are not so much the target. It's more of the crashes 272 00:23:52,040 --> 00:23:57,040 that occur on highways and freeways, where the speeds are really high if you get in the 273 00:23:57,040 --> 00:24:02,120 wrong direction, and what are the different things that you're doing to prevent that at 274 00:24:02,120 --> 00:24:08,880 the ramps, on ramps, and that's the real focus of this particular one. 275 00:24:08,880 --> 00:24:15,920 >> So not Oak Street? Okay. 276 00:24:15,920 --> 00:24:21,080 >> The next policy is going to be securing transportation infrastructure. What this one 277 00:24:21,080 --> 00:24:27,440 focuses on is are we participating regionally in the identification and development of a 278 00:24:27,440 --> 00:24:32,920 security plan for the top ten regionally identified transportation infrastructure components is 279 00:24:32,920 --> 00:24:37,760 the description they give. So basically, are we coordinating regionally in helping contribute 280 00:24:37,760 --> 00:24:46,960 input to a plan for securing our major transportation mechanisms throughout the region? And so we 281 00:24:46,960 --> 00:24:50,800 need to speak with council of governments and kind of see what opportunities are out 282 00:24:50,800 --> 00:24:55,520 there. We haven't really had that conversation yet, so that's the next steps for that particular 283 00:24:55,520 --> 00:24:58,560 item. Did you have anything to add on that one? 284 00:24:58,560 --> 00:25:04,480 >> No, I think that's pretty simple. >> The next second to last is employer trip 285 00:25:04,480 --> 00:25:11,160 reduction program. This is basically working with council of governments to have some education 286 00:25:11,160 --> 00:25:16,980 programs here within the city to encourage employee trip sharing, ride sharing to work. 287 00:25:16,980 --> 00:25:20,080 And so that's just another one that we need to reach out to council of governments and 288 00:25:20,080 --> 00:25:27,840 see what opportunities are out there for us. >> I would also recommend our economic development 289 00:25:27,840 --> 00:25:35,440 department and we also have the economic development board who has the chamber and the university 290 00:25:35,440 --> 00:25:40,800 and a lot of the high employers sitting on the board, and so getting some information 291 00:25:40,800 --> 00:25:46,200 out to them may be a good start as well, the way to get that out into the community. 292 00:25:46,200 --> 00:25:52,800 >> Okay. Thank you. And then -- oh, yes. >> I was going to say on the employer trip 293 00:25:52,800 --> 00:25:58,120 reduction program, I'm not sure if the program that DCTA has just recently started out by 294 00:25:58,120 --> 00:26:02,600 the airport -- on airport road would qualify for that or not, but it's a possibility. 295 00:26:02,600 --> 00:26:09,000 >> That's something that we are checking with Cog. I thought it did, but we'll see. It does 296 00:26:09,000 --> 00:26:13,120 look into how can we reduce the number of people that are taking cars into that particular 297 00:26:13,120 --> 00:26:20,200 area, so it does have some -- >> So of these -- we'll leave the last one 298 00:26:20,200 --> 00:26:23,520 off, right, because we don't know if it's going to stay on. 299 00:26:23,520 --> 00:26:25,960 >> Oh, yeah, that's true. >> But, you know, so these -- the ones that 300 00:26:25,960 --> 00:26:32,800 -- how can we help you -- well, first of all, do we, you know, like this list? You know, 301 00:26:32,800 --> 00:26:36,720 are these things that we actually want to work on? And then which of these actually 302 00:26:36,720 --> 00:26:42,200 require some new policy development? From what I'm hearing, like, yes, the first one 303 00:26:42,200 --> 00:26:46,480 is complete streets, integration is the ways thing, so you might need to be bringing that 304 00:26:46,480 --> 00:26:53,440 back to us. And sounds like employer trip production program would be a new thing. The 305 00:26:53,440 --> 00:26:58,360 others are -- this is all a question. The others, it sounds like it's more a question 306 00:26:58,360 --> 00:27:03,720 of seeing if we happen to be aligning with what they're interested in anyway to get extra 307 00:27:03,720 --> 00:27:12,280 points, but, you know, where can we help you by giving direction on policy for something 308 00:27:12,280 --> 00:27:15,320 new that you weren't already doing? Is there anything? 309 00:27:15,320 --> 00:27:20,720 >> I think the employer trip production program is something that we need to look into. Definitely 310 00:27:20,720 --> 00:27:27,000 we need more research time to get -- understand what's required and what are the policy implications 311 00:27:27,000 --> 00:27:31,320 so that we have better understanding out of these eight. There are five that really need 312 00:27:31,320 --> 00:27:36,480 a council action or really need a policy in this initiative that's lacking within the 313 00:27:36,480 --> 00:27:44,240 city. Once we get to that phase, I think at a later date, most likely around February 314 00:27:44,240 --> 00:27:49,240 timeframe, we can have a better idea on these. Obviously we'll have a better idea of the 315 00:27:49,240 --> 00:27:53,880 remaining eight and move forward with that part, but these will have a better idea and 316 00:27:53,880 --> 00:28:00,520 research to complete it so that by the time we apply, we're already working on these. 317 00:28:00,520 --> 00:28:05,700 Better idea would be bring it back and say these are the five that we need more direction 318 00:28:05,700 --> 00:28:09,840 from the council. >> I just want to add here that a lot of these 319 00:28:09,840 --> 00:28:17,320 that we see would make our air quality better. And so I am in favor and a proponent of that, 320 00:28:17,320 --> 00:28:22,280 and I think it would just -- a lot of these implement in our key focus areas across the 321 00:28:22,280 --> 00:28:28,320 city as well. >> There's double benefits to both reasons 322 00:28:28,320 --> 00:28:35,300 to do the policy. >> To the extent that we're beyond the requirements 323 00:28:35,300 --> 00:28:42,320 for the credits, you know, I personally wouldn't feel all that constrained to make sure that 324 00:28:42,320 --> 00:28:47,720 it meets what NCT cog wants. That's a good thing, I guess. But if we want to do something 325 00:28:47,720 --> 00:28:53,080 that we think is better or, you know, I don't feel we need to feel constrained by them, 326 00:28:53,080 --> 00:28:59,280 it's just, you know, we can feel inspired by them by seeing their list. But, you know, 327 00:28:59,280 --> 00:29:03,520 I think it's more important that we do what we think is great policy for Denton than that 328 00:29:03,520 --> 00:29:12,320 we necessarily check the box on these. >> I would agree with that statement and I'd 329 00:29:12,320 --> 00:29:18,560 say the other thing is there are more than just this policy bundle that these particular 330 00:29:18,560 --> 00:29:28,520 items affect at cog. There are other recognitions that go out that we can apply for. It's not 331 00:29:28,520 --> 00:29:34,400 just trying to get these transportation credits that these affect. They affect many things 332 00:29:34,400 --> 00:29:40,720 across the board at that level. >> So have you gotten what's gettable today 333 00:29:40,720 --> 00:29:42,920 that would be helpful in moving forward? >> Yeah, definitely. 334 00:29:42,920 --> 00:29:44,880 >> We'll sit tight and wait for you to come back? 335 00:29:44,880 --> 00:29:47,240 >> Definitely. >> Yeah, thanks so much for reviewing this. 336 00:29:47,240 --> 00:29:50,040 Have you presented to us before? >> This is my first time. 337 00:29:50,040 --> 00:29:53,000 >> This is your maiden voyage? >> Yes, thank you for your time today. 338 00:29:53,000 --> 00:29:55,520 >> Congratulations. >> Thank you. I appreciate that. 339 00:29:55,520 --> 00:30:02,920 >> I'm going to go ahead and escape out of this. Are you up next? 340 00:30:02,920 --> 00:30:12,080 >> Okay. So we'll close out that item and move on to item C. And this is another one 341 00:30:12,080 --> 00:30:21,000 where you're here because I've held you hostage. You know, my request to Preetam was that we 342 00:30:21,000 --> 00:30:26,400 -- especially when we don't have other pressing matters, look quarter by quarter or six months 343 00:30:26,400 --> 00:30:33,400 by six months at the confluence of text odd plan projects and our plan projects to see 344 00:30:33,400 --> 00:30:37,840 where, you know, there might be problems that we should be communicating about or that we 345 00:30:37,840 --> 00:30:41,520 might want to change. I don't want to end up in a situation where I'm knocking on people's 346 00:30:41,520 --> 00:30:46,160 doors and they say I complain and they just tell me it's the other department. So let's 347 00:30:46,160 --> 00:30:51,320 look forward. So with that, item C, receive a report, hold a discussion, provide direction 348 00:30:51,320 --> 00:30:58,080 on the status of Texas Department of Transportation and city of Denton capital projects. 349 00:30:58,080 --> 00:31:08,860 >> Thank you, Chair. And as Chair Meltzer mentioned that we had a brief discussion. What was -- what 350 00:31:08,860 --> 00:31:14,400 conversation did he have with Mark Nelson who was the previous staff liaison about this 351 00:31:14,400 --> 00:31:22,360 particular item. And what I got from the discussion I had was how do we overlay -- it's more of 352 00:31:22,360 --> 00:31:30,520 a how do we present a big picture on the schedule of when these big capital projects that the 353 00:31:30,520 --> 00:31:36,400 city has will be under construction along with all the big projects that text odd is 354 00:31:36,400 --> 00:31:43,640 working on and kind of start laying out the timeline overlap, understand the traffic impacts 355 00:31:43,640 --> 00:31:48,960 where would traffic be impacted and give a big picture. So I'm going to start with a 356 00:31:48,960 --> 00:31:54,320 brief description of three of our projects that's a start, but we're going to expand 357 00:31:54,320 --> 00:31:59,560 at some point and towards the end of the presentation, their next steps. But I'll talk about three 358 00:31:59,560 --> 00:32:04,200 of our projects and then how they integrate or overlay with three of the big text odd 359 00:32:04,200 --> 00:32:09,960 projects that are either under construction or will be soon in the next six months. 360 00:32:09,960 --> 00:32:14,960 This project, this particular one is Hickory Creek Road. We've already completed design. 361 00:32:14,960 --> 00:32:22,440 It's out to bid. And by February 2019, we'll go out to construction on this project. We 362 00:32:22,440 --> 00:32:28,320 don't know currently how far our dollars will stretch. So depending on the alternate bids 363 00:32:28,320 --> 00:32:34,120 that we have, we might end up -- the first segment would be green and then or some portion 364 00:32:34,120 --> 00:32:40,120 all the way to River Pass. So there are different components. It may end at Montecito depending 365 00:32:40,120 --> 00:32:46,720 on the bids that we get. But definitely this portion, the first segment on the east side 366 00:32:46,720 --> 00:32:54,160 where it connects to 2181 will be under construction starting February 2019 and it's almost a two 367 00:32:54,160 --> 00:33:00,520 and a half year project and it will be under construction. So that's the first one. Next 368 00:33:00,520 --> 00:33:07,560 one, big one is vintage Boulevard. It's called Bonnie Bray Phase 2. The way the funding is 369 00:33:07,560 --> 00:33:12,200 set up through RTR, it was connecting to Bonnie Bray and that's why it's called Bonnie Bray 370 00:33:12,200 --> 00:33:22,040 Phase 2. But vintage between I-35W and 377 is another one that will be starting construction 371 00:33:22,040 --> 00:33:31,160 in the fall of next year right around the end of or beginning in midsummer kind of deal. 372 00:33:31,160 --> 00:33:37,040 And then the construction is another two years on this particular project too. And then these 373 00:33:37,040 --> 00:33:43,680 are the small transportation projects. This is the third one, Dallas Drive at Teasley. 374 00:33:43,680 --> 00:33:48,640 We have started construction, some part of it. Initial message boards are already out 375 00:33:48,640 --> 00:33:54,840 there. And then it's a smaller project, three month construction period. The next one that's 376 00:33:54,840 --> 00:34:00,800 right at the tail end of it and that does affect other projects that are going on on 377 00:34:00,800 --> 00:34:06,640 tech stock is Colorado and the Loop. We're currently working with the bank to make sure 378 00:34:06,640 --> 00:34:12,680 their accesses are restored by the time we're done with this project and they get enough 379 00:34:12,680 --> 00:34:20,480 access. So that's scheduled to begin in February and in April. It's a two month project. These 380 00:34:20,480 --> 00:34:24,960 particular projects are capacity enhancement, adding turn lanes at each of these intersections, 381 00:34:24,960 --> 00:34:32,920 making it better, improving traffic flow. So the overlay, this is the first project, 382 00:34:32,920 --> 00:34:36,360 Hickory Creek. >> Can you go back to the -- 383 00:34:36,360 --> 00:34:41,240 >> Absolutely. >> So the Dallas Drive Teasley Lane, I'm pretty 384 00:34:41,240 --> 00:34:44,520 excited about that. I think it's going to be great when it's done. But of course you 385 00:34:44,520 --> 00:34:48,380 hear comments and you listen. I don't know if you're aware of those. If you could just 386 00:34:48,380 --> 00:34:54,280 address, because some people say right now that they wish that the I-35 project could 387 00:34:54,280 --> 00:35:00,360 be done first and then I've also heard this is the only way out of town right now or that 388 00:35:00,360 --> 00:35:05,200 the timing just doesn't seem right. Can you address that? Because from what I understand, 389 00:35:05,200 --> 00:35:09,760 there's another timing aspect where this needs to be complete before something else opens 390 00:35:09,760 --> 00:35:13,360 to help the traffic flow. So if you could just -- 391 00:35:13,360 --> 00:35:19,600 >> Correct. So there are a couple things. Interchanges, if you look at the big picture 392 00:35:19,600 --> 00:35:25,840 here, there are -- I can open up a -- just for discussion purposes, I can open up a map 393 00:35:25,840 --> 00:35:41,360 because that's always a better way. So if you look at the overall big picture, currently 394 00:35:41,360 --> 00:35:47,520 there is construction on Brinker interchange way down here. The Loop 288 interchange is 395 00:35:47,520 --> 00:35:55,960 under construction. This ramp, particular on ramp is closed. That's why all this traffic 396 00:35:55,960 --> 00:36:04,440 is now almost diverted to this one interchange. People have learned over the last few months 397 00:36:04,440 --> 00:36:10,840 that 377 is an alternative. So a lot of them go down 377 and get onto the freeway as much 398 00:36:10,840 --> 00:36:18,540 as they can. So these two currently are working as the main interchanges for the city, especially 399 00:36:18,540 --> 00:36:25,680 on the south side. It's very congested. The next thing that is -- so this particular textile 400 00:36:25,680 --> 00:36:31,440 project is going to go on almost -- current schedule, they're saying is July 2019, which 401 00:36:31,440 --> 00:36:36,760 we don't think is realistic. It's most likely going to be towards the end of next year, 402 00:36:36,760 --> 00:36:43,760 which puts us in a whole construction mode for another year for this particular area. 403 00:36:43,760 --> 00:36:51,560 The other thing that is also happening is U.S. 377 south of 35 will be soon under construction. 404 00:36:51,560 --> 00:36:57,800 They have led the contract. There is a pre-construction meeting this month. They're going to start 405 00:36:57,800 --> 00:37:02,120 with the utilities portion of it, which means they're not going to touch the lanes. They're 406 00:37:02,120 --> 00:37:07,600 going to work on the side, similar to what they did on FM 2181. They're working on the 407 00:37:07,600 --> 00:37:13,500 side on the ditches. They're not really touching the main lanes of travel. So this is not really 408 00:37:13,500 --> 00:37:19,000 going to impact the traffic initially when they're working on the utilities. But in the 409 00:37:19,000 --> 00:37:23,560 next three to four months, once they're done with the utilities, they will start working 410 00:37:23,560 --> 00:37:30,040 on some of the lanes. And once that happens, then we've lost the window to do anything 411 00:37:30,040 --> 00:37:35,080 at this intersection because that was our window where this is not going to happen for 412 00:37:35,080 --> 00:37:40,160 end another year. This is starting soon in the next few months. So this is our right 413 00:37:40,160 --> 00:37:46,440 window where we just get in and get this thing done or go through the pain. I mean, I understand. 414 00:37:46,440 --> 00:37:52,720 I'm in the same boat getting in and out. I use this intersection every day. So it's a 415 00:37:52,720 --> 00:37:58,040 matter of we have to go through the growing pains, and it's going to be better. But we 416 00:37:58,040 --> 00:38:05,120 have this really slim window. This project is two years far. And so that's why we are 417 00:38:05,120 --> 00:38:10,280 trying to push. And we understand that there will be some congestion to that end. What 418 00:38:10,280 --> 00:38:18,200 we're doing is if you look at the construction plans, there is a lot of curb work here, which 419 00:38:18,200 --> 00:38:24,200 won't really impact any of the through lanes. So we're making sure that all the curb work 420 00:38:24,200 --> 00:38:31,160 is outside and not really impacting the capacity or the ability for motorists to make the turns. 421 00:38:31,160 --> 00:38:36,440 So that's one area that we'll be focusing on initially, phase one. Phase two is working 422 00:38:36,440 --> 00:38:42,640 inside. And we are trying to make sure that that happens off peak hours when there is 423 00:38:42,640 --> 00:38:48,680 not that much traffic or if required, some night closures. So that's the direction we're 424 00:38:48,680 --> 00:38:54,760 taking to make sure we alleviate construction pains while they're going. 425 00:38:54,760 --> 00:38:59,880 I'm sorry to be a little dense, but it would help me if you spelled it out. Why is it important 426 00:38:59,880 --> 00:39:06,440 that this not be done at the same time as 377 or the 35, that segment of 35? 427 00:39:06,440 --> 00:39:12,640 So what is happening today is this interchange is experiencing all the traffic. 428 00:39:12,640 --> 00:39:14,800 Yeah, I get why that needs to be done. It's horrible. 429 00:39:14,800 --> 00:39:20,360 So this backs up all the way to this intersection. And at this particular intersection, there's 430 00:39:20,360 --> 00:39:27,280 traffic from all directions trying to go to the freeway. And one of the issues is as a 431 00:39:27,280 --> 00:39:33,920 relief for this interchange, this functions a relief wealth. So people when they really 432 00:39:33,920 --> 00:39:39,200 are making a decision right at Bell and Eagle, some of them do use that route to get under 433 00:39:39,200 --> 00:39:46,240 the freeway and some of them continue using that. So if this is also under construction, 434 00:39:46,240 --> 00:39:50,520 that relief wealth is gone at that point. And we're only focusing on one interchange. 435 00:39:50,520 --> 00:39:56,080 That made it much easier for me. Now I understand. But people bring it up. I can say for now, 436 00:39:56,080 --> 00:40:01,880 consider going out 377. That's great. 437 00:40:01,880 --> 00:40:09,120 Any other questions? I can go back. I think that covers a lot of the points in the presentation. 438 00:40:09,120 --> 00:40:18,920 So let's go back to Hickory Creek and FM2181. They are going to overlap. FM2181 is currently 439 00:40:18,920 --> 00:40:24,560 under construction. And they're barely wrapping up the utility. So it will be under construction, 440 00:40:24,560 --> 00:40:29,860 lane widening in this particular area by Hickory Creek. At the same time, we're starting construction 441 00:40:29,860 --> 00:40:38,640 early next year on Hickory Creek. So this is an access or a major connection for all these 442 00:40:38,640 --> 00:40:46,480 residential areas and neighborhoods. So there will be traffic impacts associated with it. 443 00:40:46,480 --> 00:40:54,420 We are trying to make sure our traffic control plans and plans for shifting lane traffic 444 00:40:54,420 --> 00:40:59,000 and making sure that our Hickory Creek is accessible throughout the construction. So 445 00:40:59,000 --> 00:41:04,160 making sure that traffic flows through this particular area during construction. But at 446 00:41:04,160 --> 00:41:11,160 the same time, when these two projects are going in, there will be some traffic bleeding 447 00:41:11,160 --> 00:41:18,320 into the neighborhoods and using the streets. Is there a sort of best alternate route that 448 00:41:18,320 --> 00:41:23,720 we would recommend to people living north and south of the Blue Line? 449 00:41:23,720 --> 00:41:28,280 Todd has an answer. So part of what we develop with every one 450 00:41:28,280 --> 00:41:36,680 of these projects is a detour route. Now, no detour map is foolproof until traffic actually 451 00:41:36,680 --> 00:41:41,300 hits it and people will try to find alternative routes. One of the things we would encourage 452 00:41:41,300 --> 00:41:47,720 anybody to do, because I can't control a person's mind and where they want to go, what we can 453 00:41:47,720 --> 00:41:52,640 do is try to encourage that behavior as best as we can. And then we are actively engaged 454 00:41:52,640 --> 00:41:57,920 in the construction phase. Please contact the project manager, contact Pre-Tamari, and 455 00:41:57,920 --> 00:42:02,680 we'll get the right people out there. We'll go look at it. Usually these construction 456 00:42:02,680 --> 00:42:07,960 detour maps and phasing, they become very fluid because things you just don't think 457 00:42:07,960 --> 00:42:14,080 of, they occur during construction as people start to divert around it. We try very hard 458 00:42:14,080 --> 00:42:19,400 to plan for that up front. We give maps and signs and try to route that traffic around 459 00:42:19,400 --> 00:42:24,920 to the most logical place, but people do find alternatives on their own. As soon as we hear 460 00:42:24,920 --> 00:42:28,960 about them, we get engaged with the police department if it's necessary, or we get out 461 00:42:28,960 --> 00:42:33,200 there and we start making shifts to signs, add signage, do some other things that we 462 00:42:33,200 --> 00:42:38,240 need to to make sure that we can lessen the impact on those neighborhoods. But it is something 463 00:42:38,240 --> 00:42:42,080 that we are actively engaged on construction projects. We just don't let them go and go 464 00:42:42,080 --> 00:42:43,080 tough. 465 00:42:43,080 --> 00:42:50,280 >> Yeah. And I get that. And, you know, I've experienced many of your clever detours. But, 466 00:42:50,280 --> 00:42:55,700 you know, just as in the previous example where, you know, it wasn't obvious to me, 467 00:42:55,700 --> 00:43:00,880 but that, like, maybe through social media it was just the suggestion we put out, like, 468 00:43:00,880 --> 00:43:08,000 hey, think of going 377, you know, instead of Teasley right now, like a kind of plan 469 00:43:08,000 --> 00:43:13,760 ahead kind of thought. You know, I wonder if there can be part of public engagement where 470 00:43:13,760 --> 00:43:20,360 we just communicate. In other words, you're sort of at the last opportunity to make a 471 00:43:20,360 --> 00:43:22,840 different choice when you get to the detour, right? 472 00:43:22,840 --> 00:43:29,080 >> So part of what we're dealing with is could we have done these things earlier? Yes. If 473 00:43:29,080 --> 00:43:34,560 we had been engaged in a lot of this earlier, your conversations with the public would have 474 00:43:34,560 --> 00:43:38,560 been a lot more often, a lot more frequent, and we would have gotten some of these comments 475 00:43:38,560 --> 00:43:43,200 that way. A lot of these projects are going to construction and hadn't had that put into 476 00:43:43,200 --> 00:43:47,240 it. So projects going forward, we'll have a conversation all the way throughout the 477 00:43:47,240 --> 00:43:51,920 design process, much less right here, right before we go to construction. We do have on 478 00:43:51,920 --> 00:43:55,400 all these projects public meetings that we will be going out to the public to address 479 00:43:55,400 --> 00:44:01,320 what is our -- what do we have currently for our detour routes, our maps, looking at them, 480 00:44:01,320 --> 00:44:06,640 get feedback from folks. We can accommodate where we can and we absolutely want to because 481 00:44:06,640 --> 00:44:10,520 these folks do know where their routes are. I mean, I know my neighborhood and the way 482 00:44:10,520 --> 00:44:15,480 I get to work, I know that very well and I know the side streets. Some of the folks that 483 00:44:15,480 --> 00:44:20,840 drive through the area don't. So that's where the routes, these detour routes, these detour 484 00:44:20,840 --> 00:44:24,880 maps and the signs that go with them, yes, we want that feedback. We haven't had the 485 00:44:24,880 --> 00:44:30,880 lead up time on some of these projects in an effort to get them out the door that we 486 00:44:30,880 --> 00:44:35,920 would have liked to have had. Going forward, we've learned we have to talk more frequently, 487 00:44:35,920 --> 00:44:41,000 we have to communicate back and forth more frequently where those issues and pinch points 488 00:44:41,000 --> 00:44:46,760 for you, but we also have to understand that it's not going to be free flowing like it 489 00:44:46,760 --> 00:44:50,800 is today when going to construction. It is going to be difficult for a while, but we 490 00:44:50,800 --> 00:44:55,400 will do everything we can to absolutely try to make some kind of accommodation where we 491 00:44:55,400 --> 00:45:00,280 can. I think I'm saying a different and easier thing because you're talking about hearing 492 00:45:00,280 --> 00:45:05,200 the input, which is very good and very important and all four. I'm just saying even when you're 493 00:45:05,200 --> 00:45:12,320 right on the brink of it, just for messaging out helpful tips on plan ahead, alternate 494 00:45:12,320 --> 00:45:20,360 routes, you could tell them that day, you know, just as a kind of -- that's what I'm 495 00:45:20,360 --> 00:45:26,000 teeing up as a suggestion. And, yeah, like, could we -- you're looking at me like I'm 496 00:45:26,000 --> 00:45:32,800 from another planet. Is that sort of reasonable? And I think that is something that I know 497 00:45:32,800 --> 00:45:40,920 we're working with PIO on. I know we're working with our public information office with is 498 00:45:40,920 --> 00:45:46,160 exactly that, where we can have something that does come up more on a -- hey, I know 499 00:45:46,160 --> 00:45:49,920 we're going to have some construction impacts today that weren't there yesterday so we can 500 00:45:49,920 --> 00:45:54,520 release that information as early as possible or even better two or three days ahead of 501 00:45:54,520 --> 00:45:59,760 time so folks are aware of them. It's coming. It's just tougher to get to immediately. 502 00:45:59,760 --> 00:46:06,280 But I'm just saying just to go one more step, not just this is happening, but here's some 503 00:46:06,280 --> 00:46:11,200 suggestions. What suggestions are you talking about? 504 00:46:11,200 --> 00:46:17,980 Like go through 377 instead of Teasley or whatever you suggest people here do. Consider 505 00:46:17,980 --> 00:46:23,160 planning your trip -- trip planning. Consider planning going whatever way to the west. 506 00:46:23,160 --> 00:46:26,360 We probably are saying the same thing. To me, when I'm talking about a detour route 507 00:46:26,360 --> 00:46:31,240 and detour maps and doing them up front, it's exactly that. It's looking at it from a regional 508 00:46:31,240 --> 00:46:36,800 basis and not just, hey, by the way, there's a road you got to turn left here. It's getting 509 00:46:36,800 --> 00:46:40,400 broader. We haven't done that in the past really well. I mean, you look at that in some 510 00:46:40,400 --> 00:46:45,000 of the areas where we have some signs out today for maintenance work, they show up all 511 00:46:45,000 --> 00:46:50,200 of a sudden and then, you know, if we had known eight blocks ahead of time, we could 512 00:46:50,200 --> 00:46:54,560 have pushed somebody this way instead of oh, my goodness, you're right on it now. 513 00:46:54,560 --> 00:46:58,360 But I think what we can do, in addition to what Ty is doing, they're creating those detour 514 00:46:58,360 --> 00:47:02,920 maps way ahead of time. It's working directly with PIO because a lot of it is based on -- could 515 00:47:02,920 --> 00:47:07,720 be weather related. If the project was going to start on a Monday, but it's rained and 516 00:47:07,720 --> 00:47:12,000 so they're not going to close the street until maybe Wednesday, then it's more about pushing 517 00:47:12,000 --> 00:47:16,600 those detour maps out literally right on the brink of when the road is going to be closed. 518 00:47:16,600 --> 00:47:21,320 So it's kind of front of mind to the user, whether it's on social media or the website 519 00:47:21,320 --> 00:47:26,160 or whatever the case may be, a blast, an email. So I think we can do a little bit better in 520 00:47:26,160 --> 00:47:30,560 getting the word out right up to the brink of the project or the road being closed so 521 00:47:30,560 --> 00:47:34,360 that the traffic, the community public is alerted. 522 00:47:34,360 --> 00:47:38,920 >> I think we'll sort of stand or fall on the public size based entirely on this. 523 00:47:38,920 --> 00:47:39,920 >> Right. 524 00:47:39,920 --> 00:47:42,560 >> During this period. There's so much going on. 525 00:47:42,560 --> 00:47:47,040 >> And it is good conversation. We're coming back to council, the entire council, on the 526 00:47:47,040 --> 00:47:53,160 7th, to fold in all these city projects that are folded in with the TechStop projects and 527 00:47:53,160 --> 00:48:00,580 our overall communications plan is we're looking at doing a special citizens newsletter that's 528 00:48:00,580 --> 00:48:06,120 outside of the norm that highlights all of these projects and gives a little bit of descriptor 529 00:48:06,120 --> 00:48:13,520 with the map that will be mailed out to the community and again continue to reinforce 530 00:48:13,520 --> 00:48:18,320 those communication efforts because things will change. Once that thing is printed, if 531 00:48:18,320 --> 00:48:22,520 we have a lot of rain, it's already outdated. So we're going to have to continually update 532 00:48:22,520 --> 00:48:25,860 that in a digital format. 533 00:48:25,860 --> 00:48:31,880 >> Just a comment that I think the waste thing we were talking about earlier is kind of what 534 00:48:31,880 --> 00:48:39,320 the solution would be for this type of last minute redirection. So just a comment there 535 00:48:39,320 --> 00:48:44,620 that, you know, there are tools available that once we start using them will definitely 536 00:48:44,620 --> 00:48:45,620 help. 537 00:48:45,620 --> 00:48:49,040 >> And it may be just as easy as just encouraging people to download the Waze app just so you 538 00:48:49,040 --> 00:48:50,040 have the latest and greatest. 539 00:48:50,040 --> 00:48:51,040 >> Yeah. 540 00:48:51,040 --> 00:48:53,440 >> Again, not to endorse something, but that is something that the COG I know is working 541 00:48:53,440 --> 00:48:59,600 pretty closely with to get that information real time. So those detours and those notifications 542 00:48:59,600 --> 00:49:03,640 online or excuse me, on your phone are done while you're driving and in a safe manner, 543 00:49:03,640 --> 00:49:06,360 of course, but while you're in route. 544 00:49:06,360 --> 00:49:09,720 >> Can you go back one slide? 545 00:49:09,720 --> 00:49:10,720 >> Yep. 546 00:49:10,720 --> 00:49:17,640 >> Because I travel this area very frequently. And have we looked at -- I know it's part 547 00:49:17,640 --> 00:49:25,600 of the future construction project between 2181 and 2499, a stop light at Hickory Creek 548 00:49:25,600 --> 00:49:30,400 and I know it's part of that project, but right now that would create a huge relief 549 00:49:30,400 --> 00:49:35,200 because that traffic gets back to -- that's a turn I don't make intentionally. I will 550 00:49:35,200 --> 00:49:40,640 find a way around that, that it would route people away from the 2181 and give them an 551 00:49:40,640 --> 00:49:43,600 easy way to get back out to 35. 552 00:49:43,600 --> 00:49:50,240 >> Correct. So that's a separate project, Hickory Creek East, and we are including a 553 00:49:50,240 --> 00:49:55,400 traffic signal design. We're looking at that particular -- as part of the design. So once 554 00:49:55,400 --> 00:50:00,760 this design is completed and it goes to construction, that signal will be implemented at 2499 and 555 00:50:00,760 --> 00:50:01,760 Hickory Creek. 556 00:50:01,760 --> 00:50:06,480 >> And have we looked at potentially trying to get that in place sooner rather than waiting 557 00:50:06,480 --> 00:50:13,960 until that construction to allow 2499 to become the relief for 2181? Because right now there's 558 00:50:13,960 --> 00:50:18,000 not -- you've got Robinson that goes across or you've got to go all the way down to the 559 00:50:18,000 --> 00:50:20,880 bottom that's right now under construction. 560 00:50:20,880 --> 00:50:25,200 >> So that is a possibility. They're working on the warrants analysis. Once we have that, 561 00:50:25,200 --> 00:50:30,720 we'll send it to TechStat. And TechStat needs to approve that. But we can expedite to an 562 00:50:30,720 --> 00:50:34,160 earlier stage the signal. So signal can be a starting point. 563 00:50:34,160 --> 00:50:44,160 >> Last I heard there had been 15 accidents at that intersection already. So it's warranted. 564 00:50:44,160 --> 00:50:45,160 >> Wow. 565 00:50:45,160 --> 00:50:51,320 >> And since that road only opened in April, that's not a very long time period to have 566 00:50:51,320 --> 00:50:52,320 that many accidents. 567 00:50:52,320 --> 00:50:56,400 >> Yes, and that's why that lane collider is in place. We've worked with TechStat to 568 00:50:56,400 --> 00:51:00,760 put that in place so that they get out safely. 569 00:51:00,760 --> 00:51:07,880 >> How far away are we from, you know, from being able to consider executing a Waze partnership? 570 00:51:07,880 --> 00:51:17,280 >> We're at least three to four months out. One of the biggest challenges is how are softwares 571 00:51:17,280 --> 00:51:23,440 that are integrated. Towards the end of the presentation, I'll show you a map. We have 572 00:51:23,440 --> 00:51:30,300 some type of database and software that projects on a map. It's GIS based. Translating that 573 00:51:30,300 --> 00:51:35,920 into what Waze requires as far as their data and pulling that into their system. So IT 574 00:51:35,920 --> 00:51:41,880 is looking at what kind of information we share, what is the risk associated with it, 575 00:51:41,880 --> 00:51:45,680 and then what kind of information we get back and what is the risk associated with that. 576 00:51:45,680 --> 00:51:50,400 So IT is looking at the risk and the legal component. So I'm thinking it's going to be 577 00:51:50,400 --> 00:51:55,500 more than three to four months before we can actually say, yes, we're ready to launch this 578 00:51:55,500 --> 00:52:00,400 app immediately. In the meantime, we're working on this map and we're thinking of launching 579 00:52:00,400 --> 00:52:07,440 this on our website so that way it's more helpful to have some kind of picture or create 580 00:52:07,440 --> 00:52:13,520 some newsletter. So we have our own steps, but the ultimate goal is Waze. 581 00:52:13,520 --> 00:52:19,360 >> Is there anything that we can do to create more resources or, you know, anything that 582 00:52:19,360 --> 00:52:25,040 would make that happen faster? I think it's a very exciting, you know, kind of silver 583 00:52:25,040 --> 00:52:30,480 bullet. I really appreciate Councilmember Briggs pointing out, you know, maybe the obvious, 584 00:52:30,480 --> 00:52:36,160 you know, that if that were a formal partnership and we're communicating to the public, that 585 00:52:36,160 --> 00:52:43,320 we're going into a historic, never quite seen before period of road construction activity 586 00:52:43,320 --> 00:52:47,320 and we want to get everyone through it, you know, and here's something simple you can 587 00:52:47,320 --> 00:52:52,040 do and it answers all of these things, right? You don't have to have a separate communication 588 00:52:52,040 --> 00:52:58,680 effort about each one. You know, that sounds like a really easy thing to communicate. So, 589 00:52:58,680 --> 00:53:07,160 yeah, what can we do to help? >> Let us check. Let us check and we'll work 590 00:53:07,160 --> 00:53:11,600 on that. Let staff work on that and we'll see what we can do to expedite that. 591 00:53:11,600 --> 00:53:17,240 >> Okay, very exciting. So, yeah, carry on. >> Yeah, I think I have a couple more integrations. 592 00:53:17,240 --> 00:53:22,520 This is Vintage and this is in the later part of next year that Vintage Boulevard will be 593 00:53:22,520 --> 00:53:29,320 under construction, but US 377 is already under construction. The reason these are connected 594 00:53:29,320 --> 00:53:37,360 is Vintage is the last connection between I-35W and 377 to get in town. Else you have 595 00:53:37,360 --> 00:53:44,900 to go through the Y and then go back south. So Vintage is a connector and definitely the 596 00:53:44,900 --> 00:53:53,960 traffic on Vintage as well as 377 is somehow connected where it provides a route for people 597 00:53:53,960 --> 00:53:59,360 coming from the south using 35W. So, both of these will be under construction and there 598 00:53:59,360 --> 00:54:03,880 will be certain impacts. We will definitely have detour routes and we'll make sure that, 599 00:54:03,880 --> 00:54:08,320 I think there is a Crawford Road on the south and there are a couple earlier exits work 600 00:54:08,320 --> 00:54:15,360 with TXDOT to make sure we have the right detour plans in place. The last one, I think 601 00:54:15,360 --> 00:54:20,360 we already talked about this in pretty detail. This is the small transportation projects 602 00:54:20,360 --> 00:54:25,560 and the I-35 interchange project. So, if you have any questions, I want to really get to 603 00:54:25,560 --> 00:54:33,760 the next steps. All right, so what we're not looking at and there are certain other CIP 604 00:54:33,760 --> 00:54:39,320 projects, if you focus on this particular area, there is a FM 1515 project which is 605 00:54:39,320 --> 00:54:44,760 currently under design. We don't know the schedule as far as construction goes. It's 606 00:54:44,760 --> 00:54:51,160 a TXDOT project, but we're working with TXDOT to make sure that the alignment, the facility, 607 00:54:51,160 --> 00:54:56,840 everything aligns with what the city wants. Better connection in this area as far as connection 608 00:54:56,840 --> 00:55:02,600 to all the businesses Peter built and obviously the airport at the end. And then along the 609 00:55:02,600 --> 00:55:09,880 same line we have Bonnie Bray which is a multi-stage project. Currently it will start, the work 610 00:55:09,880 --> 00:55:14,800 will start on the utility side. It's a north-south water main and then after that it will be 611 00:55:14,800 --> 00:55:24,760 followed by the roadway project. So, this is coming soon. McKinney will be under construction 612 00:55:24,760 --> 00:55:31,160 pretty soon, early next year and Mayhill is already under construction. So, I wanted to 613 00:55:31,160 --> 00:55:37,440 bring this to light that there are other projects going on in the city. On top of all the street 614 00:55:37,440 --> 00:55:43,080 maintenance projects, these are smaller street maintenance projects where it's either reconstruction, 615 00:55:43,080 --> 00:55:48,920 rehab, mill and overlay. So, there is some construction going on where the traffic will 616 00:55:48,920 --> 00:55:55,560 be detoured, traffic will have other routes that they need to follow. So, in the big picture 617 00:55:55,560 --> 00:56:02,260 what we're trying to focus on, I'm sorry, you have a question. Yes, on the next six 618 00:56:02,260 --> 00:56:09,040 months it says, so from Hinkle and University on up, that's all in my district. So, except 619 00:56:09,040 --> 00:56:16,160 for just that one little area over off of Westway is District 2. My question is, have 620 00:56:16,160 --> 00:56:20,600 all of these already had the utilities moved and wastewater and water and they're just 621 00:56:20,600 --> 00:56:29,640 waiting, they're on a list for the streets? By and large, yes. Windsor is a little different 622 00:56:29,640 --> 00:56:34,240 because we have put both the water, wastewater and streets bundle into a, we've bundled 623 00:56:34,240 --> 00:56:39,800 them into one overall project. That will get bid out to a contractor who will then do all 624 00:56:39,800 --> 00:56:44,080 three components, but they'll do it continuously as they move through the neighborhood. And 625 00:56:44,080 --> 00:56:48,880 so when it says next six months, that just means a start within the next six months and 626 00:56:48,880 --> 00:56:56,480 not completed. Correct. Correct. Alright, thank you. So then looking at the big picture, 627 00:56:56,480 --> 00:57:01,920 if we start overlaying some of these projects, almost every entry point to the city is under 628 00:57:01,920 --> 00:57:08,080 construction. Yeah, so that's kind of a big deal, right? That is a big deal. And our ultimate 629 00:57:08,080 --> 00:57:15,320 goal is to have something like this with individual name tags, meaning this will be under construction 630 00:57:15,320 --> 00:57:21,840 from this point to this point, understanding what overlaps each other, and then also creating 631 00:57:21,840 --> 00:57:28,640 some sort of detours or understanding what are the options that residents should start 632 00:57:28,640 --> 00:57:34,520 using in particular areas, focusing on single areas. Are any of these things, like when 633 00:57:34,520 --> 00:57:42,800 you look at it with the overlay, does it suggest that we ought to sequence some of this a little 634 00:57:42,800 --> 00:57:53,120 differently or are we just grinding the city to a halt? That's a careful balancing act 635 00:57:53,120 --> 00:57:56,400 because what you're seeing here is what's going under construction in the next six months 636 00:57:56,400 --> 00:57:59,800 and not what we're looking at going under construction in the next 24 months. Yes, that 637 00:57:59,800 --> 00:58:04,320 is something we're evaluating, but it's a much bigger task than just what you see on 638 00:58:04,320 --> 00:58:08,640 these maps. That's what I wanted to look at each quarter by quarter. So we're looking 639 00:58:08,640 --> 00:58:14,640 at it, we meet weekly to have exactly that discussion. What goes out when, because there's 640 00:58:14,640 --> 00:58:20,720 so many other factors that go into it than just purely construction itself. It's right 641 00:58:20,720 --> 00:58:28,000 away acquisition, the utilities being in or out of the way. This is an interesting mix 642 00:58:28,000 --> 00:58:34,100 of priorities to try to juggle constantly. So yes, we absolutely evaluate construction 643 00:58:34,100 --> 00:58:38,800 schedules as the idealistic priority one when we want everything to go, but then there's 644 00:58:38,800 --> 00:58:43,880 always something that comes in next. Oh, TxDOT is now slid their schedule back six months. 645 00:58:43,880 --> 00:58:51,000 Okay, now we're pushing everything. So it's a constant menagerie of things. We're struggling 646 00:58:51,000 --> 00:58:57,440 really hard to pull all this together, but it's something we'll be doing and we can bring 647 00:58:57,440 --> 00:59:09,520 as a quarterly update. What does it look like now? That's problem identification. Okay, 648 00:59:09,520 --> 00:59:18,440 we're sealing off the city. Good thing, bad thing. You decide. What do we do? That looks 649 00:59:18,440 --> 00:59:26,160 hellish and basically where the lines cross. What do you do? Absolutely. We're working 650 00:59:26,160 --> 00:59:32,220 through that. It's not easy. I mean, we have spent quite a bit of time and I do not want 651 00:59:32,220 --> 00:59:36,240 to- It's an ambitious plan. It's an ambitious plan and I don't want to lose sight of just 652 00:59:36,240 --> 00:59:41,760 where we started a year and a half ago where we had no plans. We had nothing. We weren't 653 00:59:41,760 --> 00:59:46,960 going anywhere. We didn't even know how much this was going to cost. So we are there and 654 00:59:46,960 --> 00:59:50,600 you're asking exactly the right questions, which are also the same questions we're asking 655 00:59:50,600 --> 00:59:56,160 questions. How do you do this in a way that one, we're going to make people mad. Absolutely. 656 00:59:56,160 --> 01:00:01,440 But two, how do we kind of mitigate that as much as possible? We are also seeing on here 657 01:00:01,440 --> 01:00:06,800 what you don't see on here is what are we trying to get ahead of? TechStat is not going 658 01:00:06,800 --> 01:00:11,240 to be done in a year and move out. They're going to be done with what you see on the 659 01:00:11,240 --> 01:00:14,960 books right now in a year or two years and then they're going to move into the next phase 660 01:00:14,960 --> 01:00:22,000 of I-35 construction, on the next phase of 380. So they're going to be here in our pocket, 661 01:00:22,000 --> 01:00:27,640 in our back door for the next five to 10 years working on these things. What we're doing 662 01:00:27,640 --> 01:00:32,560 now, yes, is painful, but we're trying to get ahead of the curve and not go through 663 01:00:32,560 --> 01:00:37,120 what you've seen other communities much larger than us, like a Fort Worth or Dallas, constantly 664 01:00:37,120 --> 01:00:42,380 go through right now where I got to catch up with these major expansions as TechStat's 665 01:00:42,380 --> 01:00:46,600 doing the work. And then we don't have any relief routes. So the city then engages in 666 01:00:46,600 --> 01:00:51,920 after they're already in construction on these major interstates in that construction even 667 01:00:51,920 --> 01:00:56,560 worse than what we're dealing with right now. So it's not going to be fun. You're asking 668 01:00:56,560 --> 01:01:00,860 exactly the right question and I appreciate you making us ensuring and holding us accountable 669 01:01:00,860 --> 01:01:06,000 to toe the line, to really reach out to the public, make sure they understand it's not 670 01:01:06,000 --> 01:01:10,760 fun for us either to try to balance all these things, but it is a challenge and we welcome 671 01:01:10,760 --> 01:01:16,360 the opportunity to make that happen as a team working with the community, not against each 672 01:01:16,360 --> 01:01:17,360 other. 673 01:01:17,360 --> 01:01:22,520 I can tell you what people usually say. You're talking to someone who really agitated to 674 01:01:22,520 --> 01:01:32,080 get a lot of stuff going. So I get the irony. But I know what people say is how about finish 675 01:01:32,080 --> 01:01:38,760 one thing and then do the next, right? That's what they say to me. But part of what I'm 676 01:01:38,760 --> 01:01:41,800 hearing you say is yeah, but there's eight things behind this. 677 01:01:41,800 --> 01:01:42,800 Exactly. 678 01:01:42,800 --> 01:01:47,360 We are catching up a lot of things that have been in the backlog. So it's more of we have 679 01:01:47,360 --> 01:01:52,520 a crunch timeline. We have a specific timeline for delivering all our bond projects. So it's 680 01:01:52,520 --> 01:01:58,840 more of we are trying to sequence it more appropriately in different parts of the city 681 01:01:58,840 --> 01:02:05,840 and in concert with whatever's happening with take stop facilities. So yes, a lot of stuff. 682 01:02:05,840 --> 01:02:11,520 And as Todd alluded to, there was a lot more projects coming in. There was a Mayhill interchange 683 01:02:11,520 --> 01:02:19,000 and the bridge project coming in pretty soon. And it will be under design. So a lot more 684 01:02:19,000 --> 01:02:24,560 take stop projects will continue in this area. And we're trying to make sure that we have 685 01:02:24,560 --> 01:02:30,200 other routes that would relieve or provide a relief already constructed in place, example 686 01:02:30,200 --> 01:02:34,520 Bonnie Bray when the 35 goes in. 687 01:02:34,520 --> 01:02:41,140 So I just want to say that I really like seeing all the blue because I do hear, you know, 688 01:02:41,140 --> 01:02:46,640 I know that it's going to be frustrating, but I hear a lot of my car is broken thanks 689 01:02:46,640 --> 01:02:51,320 to your streets. There's too many potholes. My street has been, you know, looks like a 690 01:02:51,320 --> 01:02:55,640 third world country for, you know, years. Why aren't you doing this? And I mean, I see 691 01:02:55,640 --> 01:02:59,400 on there, you know, I know that the Kings Row section is going to be there. I mean, 692 01:02:59,400 --> 01:03:05,880 I see things that are actually getting done. And for me, I mean, I appreciate that. Four 693 01:03:05,880 --> 01:03:10,160 years on council hearing the same thing over and over again, you know, finally being able 694 01:03:10,160 --> 01:03:14,600 to say, you know, look, here is our plan. And this is what we're going to do. And it's 695 01:03:14,600 --> 01:03:20,800 going to be painful for a little while. But, you know, so I just wanted to say thank you 696 01:03:20,800 --> 01:03:28,120 for doing this. I know we're going to have some issues with traffic, but I do think that, 697 01:03:28,120 --> 01:03:34,720 you know, taking care of a lot of the streets within the city is a really big deal. 698 01:03:34,720 --> 01:03:39,080 And I think the other thing too, and appreciate the statements and comments and everything 699 01:03:39,080 --> 01:03:47,080 is taken to heart. What you're seeing here is a different team of folks in a different 700 01:03:47,080 --> 01:03:50,720 approach. And so working that in working in a collaborative fashion with not only the 701 01:03:50,720 --> 01:03:54,880 engineering, the folks on the boots on the ground, the operations, the community, the 702 01:03:54,880 --> 01:04:01,280 folks that communicate, working with the public and the businesses. I mean, it's a full effort. 703 01:04:01,280 --> 01:04:07,760 And again, it's we're making so many more strides today than we did just 18 months ago. 704 01:04:07,760 --> 01:04:13,560 And so some of that is, I mean, I commute through these streets as well and those alternate 705 01:04:13,560 --> 01:04:18,880 routes, you know, luckily I've got a, you know, kind of the hotline to this guy. Like, 706 01:04:18,880 --> 01:04:25,360 why is the street closed at 8 o'clock or this lane of traffic? And so he hears it from me 707 01:04:25,360 --> 01:04:31,880 on a very frequent basis, but it is we're so much further along. And because we were 708 01:04:31,880 --> 01:04:36,840 behind and have been behind, it is about playing catch up. And so, you know, when we came to 709 01:04:36,840 --> 01:04:41,600 council back during the budget process to need the additional monies to make, to finish 710 01:04:41,600 --> 01:04:47,080 out the bond program and it's, you know, city manager said, we're going to make everybody 711 01:04:47,080 --> 01:04:55,160 mad. And that's unfortunate, but that's the only way we're going to be able to get those 712 01:04:55,160 --> 01:05:02,760 projects completed as timely as we can because time is money. The longer we wait, it's going 713 01:05:02,760 --> 01:05:06,720 to cost us more. And we don't want to come back to the well, to the council. So we've 714 01:05:06,720 --> 01:05:09,960 got to get these projects out. I know they're being very aggressive, getting these things 715 01:05:09,960 --> 01:05:15,840 bundled out. So all the suggestions are great. And again, those detour maps, the getting 716 01:05:15,840 --> 01:05:20,600 with PCO and make sure that those things are communicated as frequently as we can get those 717 01:05:20,600 --> 01:05:24,120 out. And because these guys need to be working on project management and we need to let the 718 01:05:24,120 --> 01:05:27,720 experts communicate and work hand in glove with those efforts. 719 01:05:27,720 --> 01:05:32,920 >> I was going to suggest, what would you think about just, you know, providing with 720 01:05:32,920 --> 01:05:38,320 a little bit of presentation this map to the public engagement committee? Here's what's 721 01:05:38,320 --> 01:05:49,360 coming. I can tell you why. Help. >> Like I said, we'll be bringing this along 722 01:05:49,360 --> 01:05:53,840 with what Jessica and her team is working on for communications to this next -- obviously 723 01:05:53,840 --> 01:06:00,320 not today, but the following is the 27th of November. And then if we need to bring it 724 01:06:00,320 --> 01:06:04,000 to the committee on citizen engagement, that's absolutely possible. We certainly can do that 725 01:06:04,000 --> 01:06:08,520 with the same presentation. >> Yeah, I'm sure they feel happy to be included. 726 01:06:08,520 --> 01:06:10,680 >> Absolutely. >> By the way, who's the room manager here? 727 01:06:10,680 --> 01:06:14,400 Just want to know, when do we need to clear so they can change up the -- 728 01:06:14,400 --> 01:06:17,880 >> I think it's probably before 1130, right? Or 1115? 729 01:06:17,880 --> 01:06:21,320 >> Yeah, okay. I mean, I don't think we have a lot more to cover. 730 01:06:21,320 --> 01:06:22,560 >> No, I don't. >> Okay. 731 01:06:22,560 --> 01:06:28,280 >> Yeah, well, just kind of a question or comment on this, because the title says projects 732 01:06:28,280 --> 01:06:33,320 under construction and several of those aren't under construction yet or they'll be starting 733 01:06:33,320 --> 01:06:40,520 in the next six months, I guess. One project I don't see on there is Forest Ridge, which 734 01:06:40,520 --> 01:06:49,720 was supposed to be spring of 2019. >> Okay. I can check on that one. I'll make 735 01:06:49,720 --> 01:06:54,480 sure it gets on the map. >> Okay. 736 01:06:54,480 --> 01:07:00,320 >> Yeah, I think what we're trying to do, this is a GIS-based map, which feeds actively 737 01:07:00,320 --> 01:07:05,200 every single project that goes to construction through our software system that tracks these 738 01:07:05,200 --> 01:07:09,240 projects. So we're trying to get better in presenting the information that we already 739 01:07:09,240 --> 01:07:15,640 had and staff knew at the staff level, but it was hard to present it on a map. So we've 740 01:07:15,640 --> 01:07:20,880 gotten this far and there might be some glitches and some of the projects may be dropped. But 741 01:07:20,880 --> 01:07:26,580 this is something that will form a platform that we push forward to Waze. And once Waze 742 01:07:26,580 --> 01:07:31,320 understands each of these projects and what is the timeline associated, construction started 743 01:07:31,320 --> 01:07:36,560 here, phase 1 completed here, phase 2, all the different elements, then that's the information 744 01:07:36,560 --> 01:07:42,120 that they can communicate with all the motorists and drivers in the area. So I apologize. I 745 01:07:42,120 --> 01:07:48,200 mean, we're still working through the kinks. >> All right. Can we agree to have as our 746 01:07:48,200 --> 01:07:55,120 goal rather than to make everyone mad, to take this unusual circumstance to impress 747 01:07:55,120 --> 01:08:03,200 the citizens with how well we manage this historic level effort? That's a goal. They 748 01:08:03,200 --> 01:08:07,880 know it's a huge thing we're undertaking, but let's make sure they do and let's impress 749 01:08:07,880 --> 01:08:12,800 them with how well we communicate. >> One last question, a follow-up question. 750 01:08:12,800 --> 01:08:21,440 Will this map or one like it be on the streets webpage? Because I know that there is a map 751 01:08:21,440 --> 01:08:26,120 on there, but you have to kind of know where you want and you click. And they're not all 752 01:08:26,120 --> 01:08:32,360 on there at once. There's just a few. And so I'm just curious, because the way that 753 01:08:32,360 --> 01:08:36,160 it is now, if you type in something and it shows you the start date and the end date, 754 01:08:36,160 --> 01:08:41,640 it's very helpful. But if you have future ones on there, too, so that people know that, 755 01:08:41,640 --> 01:08:46,240 you know, oh, my street is going to be, you know, in a few months. And then it just kind 756 01:08:46,240 --> 01:08:51,400 of calms them down and they're more prepared for it than a door hanger the night before. 757 01:08:51,400 --> 01:08:57,560 >> I think what might be helpful in that vein, because I know some folks are -- the GIS doesn't 758 01:08:57,560 --> 01:09:00,740 scare them and they'll go click on the different layers and they can play with it. Some folks 759 01:09:00,740 --> 01:09:05,960 it does and it's like, what is all this? So I think the intent, part of what Preetam was 760 01:09:05,960 --> 01:09:10,080 alluding to is we wanted to have more of a PDF version that you could double click and 761 01:09:10,080 --> 01:09:14,540 just see it. That gets updated periodically. And then some folks would go to GIS and see 762 01:09:14,540 --> 01:09:19,080 all that information. Some folks just -- I want the whole map because I don't want to 763 01:09:19,080 --> 01:09:25,120 go through all that. So yes, we'll do that. >> All right. So I look forward to seeing 764 01:09:25,120 --> 01:09:30,740 you all on the cover of Infrastructure Communication Magazine. Let's carry on. We've got a little 765 01:09:30,740 --> 01:09:33,720 bit more to go. Is there more on this? >> That's it. 766 01:09:33,720 --> 01:09:39,480 >> All right. You don't want any more questions. So item D, receiver report, hold the discussion 767 01:09:39,480 --> 01:09:44,680 and provide direction regarding Texas Department of Transportation on system projects in the 768 01:09:44,680 --> 01:09:51,120 Denton area to include the 35 express project. >> So this is a lot of the projects are covered 769 01:09:51,120 --> 01:10:08,640 under what we talked about. Let me see if I can -- there we go. 770 01:10:08,640 --> 01:10:16,640 So as you can see, there's several projects that TxOTR is working within the city. Let 771 01:10:16,640 --> 01:10:27,240 me just go one at a time. FM 2181. Currently, their schedule says February 20 construction 772 01:10:27,240 --> 01:10:34,480 is -- wow, they updated that. It used to be -- well, no. FM 2181 will be constructed and 773 01:10:34,480 --> 01:10:45,520 completed by 2020. They almost -- as far as utilities, there is at most conflict relocation 774 01:10:45,520 --> 01:10:52,840 has been completed. So that was one of the items that was remaining. I don't see any 775 01:10:52,840 --> 01:11:01,400 updates on this one. This construction is moving forward. And I think there is some 776 01:11:01,400 --> 01:11:05,400 concerns from the contractor. >> There is one concern that may impact the 777 01:11:05,400 --> 01:11:11,840 schedule of this project. Even more than it has. The general contractor that this contract 778 01:11:11,840 --> 01:11:19,080 was awarded to, MCM construction, it appears that they are in danger of not being able 779 01:11:19,080 --> 01:11:27,040 to complete this project. They may be insolvent before too long. So conversations have already 780 01:11:27,040 --> 01:11:32,040 been initiated between TxOTR and their bonding company. So the bonding company is starting 781 01:11:32,040 --> 01:11:35,920 to look into the pathway of them taking over the project. Now, the thing I would tell you 782 01:11:35,920 --> 01:11:42,480 is anytime a bonding company gets into management of the project, it takes time. Because they 783 01:11:42,480 --> 01:11:46,240 work through the legal issues, then who is doing what, holding certain folks' feet to 784 01:11:46,240 --> 01:11:51,400 the fire, who do they find bringing to the table to do other things, and then it's just 785 01:11:51,400 --> 01:11:57,400 a much more convoluted process. The potential here is that this could push out longer than 786 01:11:57,400 --> 01:12:03,820 February of 2020 just because now we had an underperforming contractor. It is not getting 787 01:12:03,820 --> 01:12:08,920 any better. The contractor themselves is having some financial issues. And it could present 788 01:12:08,920 --> 01:12:15,460 itself in a much bigger delay than just what we're seeing right now. 789 01:12:15,460 --> 01:12:21,680 And does this have to do with the issue that TxOTR has to choose the low-bid contractor? 790 01:12:21,680 --> 01:12:22,680 Yes. 791 01:12:22,680 --> 01:12:28,060 Okay. So yeah, I just want you guys to know that that is on the legislative agenda for 792 01:12:28,060 --> 01:12:32,320 the Dallas Regional Committee. I think it is also... 793 01:12:32,320 --> 01:12:34,840 It hasn't come to RTC yet. 794 01:12:34,840 --> 01:12:40,720 Okay. So that is something that we are going to be looking and asking to change because 795 01:12:40,720 --> 01:12:47,520 of the issues that it causes. 796 01:12:47,520 --> 01:12:56,000 Okay. So this is US377. I started talking about this earlier. As mentioned, it's under 797 01:12:56,000 --> 01:13:00,680 construction. We'll have a pre-construction meeting this month. And utilities will start 798 01:13:00,680 --> 01:13:07,440 soon either end of this year or the next year. And then the construction will go all the 799 01:13:07,440 --> 01:13:19,920 way through... It doesn't have a date here, but I mentioned it was 2021 in the presentation. 800 01:13:19,920 --> 01:13:25,760 Moving on to the next... We did have a open house just to inform public in October for 801 01:13:25,760 --> 01:13:31,000 this particular project. We did receive some comments. We're following up with responses. 802 01:13:31,000 --> 01:13:37,320 And most of the comments were addressed by TxOT. 803 01:13:37,320 --> 01:13:41,460 One of the comments that was not addressed by TxOT at that meeting is what their detour 804 01:13:41,460 --> 01:13:45,640 routes are. So they can get that information out. 805 01:13:45,640 --> 01:13:51,240 We have asked them and they've not provided the detour route. But typically what they 806 01:13:51,240 --> 01:13:58,640 do is they do leave the lanes open for traffic. There is no full closures unless it's a few 807 01:13:58,640 --> 01:14:06,220 hours to transfer. But they have flagging operations typically. They have one lane operations. 808 01:14:06,220 --> 01:14:10,600 They don't fully... They will have to on that project at least 809 01:14:10,600 --> 01:14:14,360 a couple of times shut down completely because of the railroad bridge. 810 01:14:14,360 --> 01:14:23,680 And we've asked for the detour for the railroad bridge particularly. We'll get that to you. 811 01:14:23,680 --> 01:14:47,600 I-35 Mayhill improvements. This is part of the... I'm not sure what... 812 01:14:47,600 --> 01:14:52,920 This is the interchange improvement project. It's not even started. It will start under 813 01:14:52,920 --> 01:14:59,200 design. So they're probably letting for design in December of 2019. They're going through 814 01:14:59,200 --> 01:15:06,480 the process of getting the plans completed by fall of next year. 815 01:15:06,480 --> 01:15:13,280 And then after that they'll go to construction. So it's currently under design. They've hired 816 01:15:13,280 --> 01:15:17,800 LTRA to do the design. And this is a full interchange upgrade. 817 01:15:17,800 --> 01:15:24,920 So this particular project will put this interchange in the final configuration. So they don't 818 01:15:24,920 --> 01:15:28,360 have to go back and do it when they come back on phase two. 819 01:15:28,360 --> 01:15:33,920 This is similar to what's currently happening at the Loop 288. It's going to the final configuration. 820 01:15:33,920 --> 01:15:38,600 The frontage roads will be in their final location. And then when they come back with 821 01:15:38,600 --> 01:15:44,720 35 next phase widening project, they don't have to update these interchanges. So it's 822 01:15:44,720 --> 01:15:50,880 currently under design. Loop 288 Brinker Mayhill, I mentioned about 823 01:15:50,880 --> 01:15:59,000 this project. This is... They're still claiming July 2019. But it's not going to likely happen. 824 01:15:59,000 --> 01:16:05,080 We're thinking more towards the end of next year. We'll keep you posted as TxDOT releases 825 01:16:05,080 --> 01:16:10,000 more information. But at this point they're still saying July 2019. 826 01:16:10,000 --> 01:16:15,800 Can you remind me when the original completion date was supposed to be? 827 01:16:15,800 --> 01:16:21,240 It was November 2018. Or even before that, it was June or July of 2018. 828 01:16:21,240 --> 01:16:22,240 This past summer? Correct. 829 01:16:22,240 --> 01:16:25,820 And now you're saying the end of next year? 830 01:16:25,820 --> 01:16:29,840 Towards the end of next year is the most likely. 831 01:16:29,840 --> 01:16:39,440 Yeah, the bucky's already open. It was supposed to coincide with bucky's. 832 01:16:39,440 --> 01:16:44,460 This is I-35 North. This is north of 380. They're currently going through the environmental 833 01:16:44,460 --> 01:16:52,120 phase. They're considering getting the environmental clearance by March of 2019. And they don't 834 01:16:52,120 --> 01:16:56,320 intend to start any construction until September 2022. 835 01:16:56,320 --> 01:17:00,400 So that's the plan. This is just the north of the city all the way to the boundary of 836 01:17:00,400 --> 01:17:09,240 the county. I-35W Main Lanes, they're barely starting 837 01:17:09,240 --> 01:17:16,120 -- there are no deadlines at this point. As you can see, this has just been dreamed 838 01:17:16,120 --> 01:17:20,020 up as a project. And they're barely starting on this. 839 01:17:20,020 --> 01:17:26,380 They have HNTP online. And they have completed 30% schematics. 840 01:17:26,380 --> 01:17:32,480 So the next phase is getting into design phase and then into construction after that. 841 01:17:32,480 --> 01:17:40,340 The limits of this project is all the way to -- I would say it's killer, almost killer. 842 01:17:40,340 --> 01:17:52,120 And then starting at Denton. US-380 East. This project is currently -- I'm sorry. 843 01:17:52,120 --> 01:17:55,160 It received the environmental clearances last year. 844 01:17:55,160 --> 01:18:02,500 It's under the right of way acquisition phase. I think that was completed in 2019. 845 01:18:02,500 --> 01:18:06,880 They don't intend to start construction until 2021. 846 01:18:06,880 --> 01:18:12,720 It is currently -- this particular segment is currently getting -- it's under design. 847 01:18:12,720 --> 01:18:15,520 And they're working with the city. They've contacted us. 848 01:18:15,520 --> 01:18:20,600 And we're dealing with some of these connections at this particular end, talking about how 849 01:18:20,600 --> 01:18:28,840 the city envisions this particular street. Loop 28 West. 850 01:18:28,840 --> 01:18:34,800 This is -- this is a long-term project. It doesn't really go into construction all 851 01:18:34,800 --> 01:18:40,600 the way in another 20 years. But the schematic will be approved early next 852 01:18:40,600 --> 01:18:41,960 year. 30% schematic. 853 01:18:41,960 --> 01:18:48,880 We're working with TxDOT, identifying the interchanges that we anticipate with all our 854 01:18:48,880 --> 01:18:54,240 arterials going through in this particular area. I know this map is turned a little bit. 855 01:18:54,240 --> 01:18:59,280 But if you can imagine, this is 35 on the north side and 35W on the south side. 856 01:18:59,280 --> 01:19:06,080 We are anticipating different streets to cross, especially Jim Crystal and some of the others. 857 01:19:06,080 --> 01:19:11,640 So we're making sure all our interchanges get into the schematics, that way when TxDOT 858 01:19:11,640 --> 01:19:16,240 goes for design, they're all reincorporated. Yes. 859 01:19:16,240 --> 01:19:21,000 Have we looked at trying to push the date up on this at all? 860 01:19:21,000 --> 01:19:25,640 I mean, because this is just service roads only. And the let date right now is scheduled 861 01:19:25,640 --> 01:19:29,120 for 2026. Correct. 862 01:19:29,120 --> 01:19:34,960 Which means it's probably going to be closer to 2030. 863 01:19:34,960 --> 01:19:42,640 This is very important for when they actually do the interchange of 35W, 35E, when they 864 01:19:42,640 --> 01:19:50,600 do that, as well as routing traffic around that area when 35 north starts. 865 01:19:50,600 --> 01:19:55,600 So I can't start and Todd can end, but we're working with John Polsker. 866 01:19:55,600 --> 01:20:02,680 And as he has informed us, we can start working on this particular piece earlier. 867 01:20:02,680 --> 01:20:09,040 There are some funds that can be obligated. We're going to start with furnitures, definitely. 868 01:20:09,040 --> 01:20:15,000 But working with him, he doesn't see why we cannot move forward earlier on this project. 869 01:20:15,000 --> 01:20:19,480 But I think if Todd can end. I think so much of this comes down to a funding 870 01:20:19,480 --> 01:20:23,320 structure for TxDOT and when they can put the funds to it. 871 01:20:23,320 --> 01:20:26,520 They're always willing to accelerate something if we're willing to put some of the funds 872 01:20:26,520 --> 01:20:30,720 to it or all of the funds. But it really does come into where does it lay 873 01:20:30,720 --> 01:20:37,080 out for them as well. But we do meet with them on a bi-weekly basis. 874 01:20:37,080 --> 01:20:40,480 TxDOT and a larger group with John Polsker, our representative. 875 01:20:40,480 --> 01:20:45,000 And we push these items, you know, what are the time frames here, we're constantly throwing 876 01:20:45,000 --> 01:20:48,800 those things at them. And them talking to us as well about what 877 01:20:48,800 --> 01:20:53,040 are the items and concerns they have. So it's a much more collaborative group than 878 01:20:53,040 --> 01:20:59,760 what I had seen in the past in other cities. TxDOT does have a schedule just like us and 879 01:20:59,760 --> 01:21:07,040 they got some financial restraints as well. Well, thinking of our previous presentation 880 01:21:07,040 --> 01:21:13,280 on COG funding for projects, this may be, I don't know if this would be something that 881 01:21:13,280 --> 01:21:18,960 we could qualify for, for extra funding through them to help get the project along because 882 01:21:18,960 --> 01:21:24,800 I do know that this would relieve some of the internal city traffic and put some of 883 01:21:24,800 --> 01:21:29,240 the freight in the trucks to keep them moving around rather than causing those backups. 884 01:21:29,240 --> 01:21:36,200 So just something to maybe a project we could think about using those funds for. 885 01:21:36,200 --> 01:21:48,160 FM1515, I mentioned earlier, it's under design currently and it's under 30 percent schematic, 886 01:21:48,160 --> 01:21:53,520 which is a great phase for us to, you know, move it, make recommendations. 887 01:21:53,520 --> 01:21:58,960 Once the 30 percent schematic is locked for TxDOT, it typically becomes a real big issue 888 01:21:58,960 --> 01:22:02,600 to get it through environmental again. So this is a good time, we're working with 889 01:22:02,600 --> 01:22:14,120 them, we have some alternatives we're looking at realigning Airport Road 1515. So the schedule 890 01:22:14,120 --> 01:22:20,840 on this one is environmental clearance by December of 2020. 891 01:22:20,840 --> 01:22:33,880 FM1173, this is on the north side of the city where it meets or intersects 35E and majority 892 01:22:33,880 --> 01:22:43,240 of this project is in crumb area but we have this eastern end that connects and ultimately 893 01:22:43,240 --> 01:22:51,640 this particular end will be realigned to match up to 77, US 77 here. Currently what is happening 894 01:22:51,640 --> 01:22:57,520 is people go south and then connect through and then get on to 77 but this will be realigned 895 01:22:57,520 --> 01:23:05,800 as part of that project to connect to US 77. Schematic approval, it is, I mean, they're 896 01:23:05,800 --> 01:23:10,000 working on it, they most likely will get things racked up. Currently the schedule says end 897 01:23:10,000 --> 01:23:22,840 of this year or so. I mean, we'll see. And I think that's the last one. I think that's 898 01:23:22,840 --> 01:23:27,080 the last one. Actually, I suppose formally I would have 899 01:23:27,080 --> 01:23:31,280 to close this item and then reopen the other item. I had a question back on the policy 900 01:23:31,280 --> 01:23:36,080 bundles. I don't know if we've ever covered, how much do we stand to get in credits if 901 01:23:36,080 --> 01:23:44,720 we hit the, you know, minimum 10? So part of it is unclear but it is transportation 902 01:23:44,720 --> 01:23:51,040 development credits that can be used towards our 20% local match. So how much per policy 903 01:23:51,040 --> 01:23:55,520 - But is it like a dollar or? It is just credit. It's credit. It's not really 904 01:23:55,520 --> 01:24:02,640 a dollar amount but the way it works is they can use, we can use those credits as cash 905 01:24:02,640 --> 01:24:09,840 or our share of 20% match for any project. So that boosts our share in terms of if we 906 01:24:09,840 --> 01:24:14,600 have a project that's 100 million instead of putting in 20 million, we can just come 907 01:24:14,600 --> 01:24:18,680 up with 10 and then the other 10 it'll be matched. So that's the whole program. 908 01:24:18,680 --> 01:24:21,920 But with no limit, with anything that has a match? 909 01:24:21,920 --> 01:24:27,360 Yes, anything, any project. The way it's set up, any project that has a local match, the 910 01:24:27,360 --> 01:24:32,920 transportation development, any transportation projects. Okay, I'd be curious to know like 911 01:24:32,920 --> 01:24:36,880 how much that might mean at some future meeting. Yes, we'll get a value amount. 912 01:24:36,880 --> 01:24:45,600 Or maybe in a note back to us. Okay, so we're done with item D. We're on to staff reports, 913 01:24:45,600 --> 01:24:53,360 matrix. Anything for the matrix? This is the matrix and I think there are, we're still 914 01:24:53,360 --> 01:25:01,480 working on this old gateway plan but I think Todd can talk about the two items here, the 915 01:25:01,480 --> 01:25:07,240 ELM and LOCUS turned back. Go ahead and I'm going to cover three. 916 01:25:07,240 --> 01:25:13,600 So on the ELM/LOCUS turn back, we did have a minor setback that we're working through. 917 01:25:13,600 --> 01:25:21,360 So PEC 4 was the lead up to the ELM/LOCUS turn back, phases 1 and 2. That bid came in 918 01:25:21,360 --> 01:25:28,180 higher than we anticipated. So we will have a piece of that that we're looking at multiple 919 01:25:28,180 --> 01:25:33,000 alternatives to recover. We'll have to re-bid the project to get better pricing. We've identified 920 01:25:33,000 --> 01:25:39,480 several places where we believe that impacted it. But we are looking at a schedule recovery 921 01:25:39,480 --> 01:25:45,240 potential in that we may have internal crews just do the crossing at Locust so that TxDOT 922 01:25:45,240 --> 01:25:52,680 is, their timeline to start doing the reconstruction of Locust itself isn't impacted. We continue 923 01:25:52,680 --> 01:25:58,920 with the Locust reconstruction beginning next summer. Then the summer following that would 924 01:25:58,920 --> 01:26:07,000 still be ELM. Questions? 925 01:26:07,000 --> 01:26:12,760 And then on number three, city council back in October, on October the 16th approved the 926 01:26:12,760 --> 01:26:21,920 change order to design the improvements along Hickory, the sidewalk improvements along with 927 01:26:21,920 --> 01:26:26,320 the lighting and some drainage improvements. My request is that that could come off the 928 01:26:26,320 --> 01:26:34,120 matrix since it's being worked on. Any objections? Seeing, yes, Pat? 929 01:26:34,120 --> 01:26:41,480 I just have a question about the matrix. Because I recall several times I asked about and it 930 01:26:41,480 --> 01:26:46,840 may have come up and then fallen back off and came up but with the last Tuesday meeting 931 01:26:46,840 --> 01:26:53,120 there were some citizens that spoke on protected bike lanes and I had asked for a presentation 932 01:26:53,120 --> 01:26:59,280 on protected bike lanes for a while and I'd like to request that again, especially now 933 01:26:59,280 --> 01:27:04,440 that we're doing our mobility plan and complete streets and because there are several different 934 01:27:04,440 --> 01:27:12,060 options that we can talk about when it comes to that and I would like to have that added 935 01:27:12,060 --> 01:27:15,360 back to the matrix. 936 01:27:15,360 --> 01:27:20,000 So quick clarification, do you want it as an agenda item so that the presentation we 937 01:27:20,000 --> 01:27:25,200 can talk about and present it or do you want it as a matrix item? 938 01:27:25,200 --> 01:27:27,000 A presentation. 939 01:27:27,000 --> 01:27:41,320 Okay. We all concur. Anything else on the matrix? Going once, going twice. Okay. Concluding 940 01:27:41,320 --> 01:27:47,760 items, speeches or anything? Public oratory of any kind. 941 01:27:47,760 --> 01:27:53,880 On the road work, it says that Spencer is going to be done on 11/28 and I'm just going 942 01:27:53,880 --> 01:28:00,980 to ask for clarification that that's still the finish date. If anybody knows or can get 943 01:28:00,980 --> 01:28:11,040 back to me on that, Spencer Road, it says the complete date is 11/28 which is coming 944 01:28:11,040 --> 01:28:12,800 up really soon. 945 01:28:12,800 --> 01:28:16,640 That is still a goal to turn it back to two-way traffic. We'll still be doing some auxiliary 946 01:28:16,640 --> 01:28:21,520 stuff off on the parkway to clean up and then make some connections at the end but yes it'll 947 01:28:21,520 --> 01:28:25,840 be open to two-way traffic by the end of the month. 948 01:28:25,840 --> 01:28:32,880 Okay. And there's still some issues being reported downtown with the walk signals and 949 01:28:32,880 --> 01:28:40,000 I just I would still I would like to request that our group take a walk downtown and see 950 01:28:40,000 --> 01:28:46,080 how those are implemented at some point. 951 01:28:46,080 --> 01:28:55,320 Maybe when it's not 20 degrees. When it's a little warmer but not a whole lot warmer. 952 01:28:55,320 --> 01:29:07,640 Minimum 40 degrees, should we say? I have a question. I've got one and I don't know 953 01:29:07,640 --> 01:29:12,880 if it's necessary to put it on this or if I can meet with you all separately on it but 954 01:29:12,880 --> 01:29:18,240 I know most of the signals along 35 are kind of interlocked between the two sides of the 955 01:29:18,240 --> 01:29:24,560 road. Bonnie Bray does not appear to be that way and I'm just questioning whether it's 956 01:29:24,560 --> 01:29:29,360 it is that way and just poorly set up or if we can just take a look at what Bonnie Bray 957 01:29:29,360 --> 01:29:34,200 and 35 does how those stop lights interconnect. 958 01:29:34,200 --> 01:29:45,640 I just have a kind of general question. What list is it that contains these sort of little 959 01:29:45,640 --> 01:29:53,320 things that I and I'm sure others throw your way like the question about whether the lane 960 01:29:53,320 --> 01:30:04,000 alignment is right going south of the square and then and they request to look at a bump 961 01:30:04,000 --> 01:30:12,160 out on Hickory and Miller for visibility when making a left there. You know, too small for 962 01:30:12,160 --> 01:30:21,520 the matrix. It's not a road construction list. Is there a list of little requests? 963 01:30:21,520 --> 01:30:29,240 Yes. Which is a great segue. We have a few members of our expanded traffic engineering 964 01:30:29,240 --> 01:30:33,600 section here and that is part of what they're charged with doing is keeping up with that 965 01:30:33,600 --> 01:30:41,900 running list and giving Preetam was our only traffic section. As you can imagine him trying 966 01:30:41,900 --> 01:30:46,400 to keep tabs on that and everything else we're doing was very difficult. It's still a challenging 967 01:30:46,400 --> 01:30:51,460 job even when you have four people trying to work on that now. Just for the city our 968 01:30:51,460 --> 01:30:58,760 size there's so many of those. This group that we have here today they do that for us. 969 01:30:58,760 --> 01:31:05,020 It's ongoing and we're just getting into a rhythm. We've not had this group put together 970 01:31:05,020 --> 01:31:08,520 but for about two or three weeks now. Want to make some quick introductions? 971 01:31:08,520 --> 01:31:19,960 Sure. We absolutely could. When I call your name. The first one is Becky and she is transitioning. 972 01:31:19,960 --> 01:31:25,760 She will be soon transitioning to taking over what Kim is doing right now to be the admin 973 01:31:25,760 --> 01:31:31,720 person for the minutes and everything for this particular committee as well as she will 974 01:31:31,720 --> 01:31:37,280 be logging all the information that we're currently talking about. We're first starting 975 01:31:37,280 --> 01:31:39,720 with a spreadsheet. You have to wave because I can't tell which 976 01:31:39,720 --> 01:31:43,440 person was Becky. Okay. Thanks. 977 01:31:43,440 --> 01:31:50,560 So currently we're starting with a list in Excel but ultimately we want to tie it down 978 01:31:50,560 --> 01:31:55,760 to a map similar to this where you can pull it up and say well we received 50 complaints 979 01:31:55,760 --> 01:32:01,760 in this in the last year or whatever it is. She's tasked to do that and track it and make 980 01:32:01,760 --> 01:32:07,160 sure we're responding, make sure we're following up on some of these requests. 981 01:32:07,160 --> 01:32:15,280 The next one back is Tracy Beck and she is a senior engineer there. She used to work 982 01:32:15,280 --> 01:32:20,920 for development review in the development review department. She has text out background 983 01:32:20,920 --> 01:32:26,520 so she's been working with text out for quite a while, has enough knowledge of all the text 984 01:32:26,520 --> 01:32:31,360 out projects that have been in place. She will be addressing some of these concerns 985 01:32:31,360 --> 01:32:37,520 as well as running some of the projects. Our new traffic person, traffic engineer is 986 01:32:37,520 --> 01:32:45,600 Pam and she will be more focused on the signal timing parts, signal design, timing, operations, 987 01:32:45,600 --> 01:32:52,760 signage and a lot of that. And yes, she was tasked to look at ADA wise what do we do with 988 01:32:52,760 --> 01:32:58,280 the signals and walk signals in downtown. So it may be fixed even before we get there 989 01:32:58,280 --> 01:33:03,120 with the temperatures. And then yes, Mark Oliphant who's not here 990 01:33:03,120 --> 01:33:08,640 currently, that's another addition. And Mike and Betty have all seen him and probably met 991 01:33:08,640 --> 01:33:10,960 him. He's great. 992 01:33:10,960 --> 01:33:15,080 Welcome everyone. Yeah, and really glad to have you, so appreciate 993 01:33:15,080 --> 01:33:23,680 your contributions. I think that's it. So at 1134 we will stand 994 01:33:23,680 --> 01:33:25,000 adjourned. Great.