WEBVTT 00:00:00.000 --> 00:00:05.000 - Good morning and welcome to this meeting 00:00:05.000 --> 00:00:07.800 of the Mobility Committee of the City of Denton. 00:00:07.800 --> 00:00:10.760 We have a quorum, but we have a full house. 00:00:10.760 --> 00:00:13.340 So let's begin our items for individual consideration. 00:00:13.340 --> 00:00:15.540 The first item is consider approval of the minutes 00:00:15.540 --> 00:00:17.380 of February 16th, 2022. 00:00:17.380 --> 00:00:19.140 I'll entertain a motion. 00:00:19.140 --> 00:00:20.560 - I move approval of minutes. 00:00:20.560 --> 00:00:21.620 - Is there a second? 00:00:21.620 --> 00:00:23.380 Okay, all in favor, aye. 00:00:23.380 --> 00:00:24.700 - Aye. - Aye. 00:00:24.700 --> 00:00:26.900 - The minutes are approved. 00:00:26.900 --> 00:00:29.580 The next item is a receiver report 00:00:29.580 --> 00:00:31.320 to hold a discussion regarding the City of Denton 00:00:31.320 --> 00:00:34.980 transportation/mobility project status report. 00:00:34.980 --> 00:00:36.700 Mr. Poulster, good morning. 00:00:36.700 --> 00:00:41.020 - Hello, hello. 00:00:41.020 --> 00:00:42.820 Is that ready for the meeting to go on? 00:00:42.820 --> 00:00:43.660 - That means soft. 00:00:43.660 --> 00:00:46.460 You have to very gently touch it 00:00:46.460 --> 00:00:47.740 for exactly half of a second. 00:00:47.740 --> 00:00:49.060 - I just saw that. 00:00:49.060 --> 00:00:54.660 See, y'all told me that, didn't ya? 00:00:54.660 --> 00:00:58.200 There you go. 00:00:59.860 --> 00:01:01.500 Uh-oh, okay. 00:01:01.500 --> 00:01:02.500 We'll go by Braille. 00:01:02.500 --> 00:01:08.480 No, no, no, we are in the roll. 00:01:08.480 --> 00:01:11.560 I got this stuff memorized. 00:01:11.560 --> 00:01:15.020 So this first sheet, for those of you who are watching, 00:01:15.020 --> 00:01:16.820 this is a project summary. 00:01:16.820 --> 00:01:20.780 It goes over the let dates, who's working on it, 00:01:20.780 --> 00:01:23.260 and then what the construction cost is. 00:01:23.260 --> 00:01:25.620 And these are essentially the projects in the report 00:01:25.620 --> 00:01:29.220 that we'll go over today. 00:01:29.220 --> 00:01:31.540 And it totals, we're chasing about 00:01:31.540 --> 00:01:33.420 two billion dollars worth of improvements 00:01:33.420 --> 00:01:35.900 in and around the City of Denton. 00:01:35.900 --> 00:01:40.500 FM 2181, north-south. 00:01:40.500 --> 00:01:41.940 - Pardon me, John. 00:01:41.940 --> 00:01:44.100 I have the number in my head of 2.4 billion 00:01:44.100 --> 00:01:44.940 for the longest time. 00:01:44.940 --> 00:01:48.660 - So what happens is as projects come off, 00:01:48.660 --> 00:01:52.220 like that 1.4 million for the 380 interim, 00:01:52.220 --> 00:01:55.300 as they come off, we take 'em off the list. 00:01:55.300 --> 00:01:56.140 - Got it. 00:01:58.940 --> 00:02:02.740 - So 2181, we have a completion date of October 22. 00:02:02.740 --> 00:02:05.500 Finally, it's been going on for like 37 years. 00:02:05.500 --> 00:02:11.020 And it's still looking like October will be complete. 00:02:11.020 --> 00:02:16.020 And we are in the last throws of our last shift 00:02:16.020 --> 00:02:19.620 that occurred on March 14th. 00:02:19.620 --> 00:02:21.060 And so from this point forward, 00:02:21.060 --> 00:02:23.780 it's just getting the last bit of pavement down. 00:02:23.780 --> 00:02:26.780 And then I would say sometime in summer, 00:02:26.780 --> 00:02:29.060 we'll get to what we call substantially complete, 00:02:29.060 --> 00:02:31.300 which is where you're driving on the lanes 00:02:31.300 --> 00:02:33.580 in the proper location that you should be. 00:02:33.580 --> 00:02:36.540 And everything else is just ancillary work, 00:02:36.540 --> 00:02:41.260 like growing the grass, moving the signal poles, et cetera. 00:02:41.260 --> 00:02:46.540 So we will definitely be coming back 00:02:46.540 --> 00:02:48.220 with a party on that one. 00:02:48.220 --> 00:02:50.860 - I have a question about that one. 00:02:50.860 --> 00:02:55.740 First of all, I wanna thank staff 00:02:55.740 --> 00:02:58.620 for pushing out the information about, 00:02:58.620 --> 00:03:02.940 there was a closure, where was it? 00:03:02.940 --> 00:03:07.500 At like Ranch Man or Briar Forest, 00:03:07.500 --> 00:03:10.140 somewhere in that area. 00:03:10.140 --> 00:03:12.580 And I know that there have been issues 00:03:12.580 --> 00:03:14.500 with closures in that area in the past. 00:03:14.500 --> 00:03:16.940 So thank y'all for communicating to residents 00:03:16.940 --> 00:03:18.360 so clearly about that one. 00:03:18.360 --> 00:03:23.300 The intersection of Teasley and Robinson 00:03:23.300 --> 00:03:26.020 is really a wreck. 00:03:26.020 --> 00:03:31.020 There's a grade difference and it's just dirt. 00:03:31.020 --> 00:03:33.340 And with the rain we've been having, 00:03:33.340 --> 00:03:35.700 it's already, the dirt is like washed out 00:03:35.700 --> 00:03:38.340 and there's like a huge drop-off. 00:03:38.340 --> 00:03:41.220 And that's a real busy intersection. 00:03:41.220 --> 00:03:43.980 Can we see about maybe getting like asphalt? 00:03:43.980 --> 00:03:45.620 - Yeah, we'll get with Travis Campbell. 00:03:45.620 --> 00:03:48.900 I'll do that as soon as I get out the door. 00:03:48.900 --> 00:03:49.740 - Great, thanks. 00:03:51.660 --> 00:03:53.780 Okay, so your I-35E Mayhill job, 00:03:53.780 --> 00:03:56.580 this is a project from Mayhill up to 288, 00:03:56.580 --> 00:03:59.600 including the northbound and southbound frontage roads 00:03:59.600 --> 00:04:02.660 to 288 and a direct connect with, 00:04:02.660 --> 00:04:06.740 I mean a bypass over Brinker. 00:04:06.740 --> 00:04:10.540 We are ready to let is September 23. 00:04:10.540 --> 00:04:12.320 And we are on track for that. 00:04:12.320 --> 00:04:16.080 If you'll note, we are in the 95% plan review 00:04:16.080 --> 00:04:19.900 and primarily, yeah, all of this from this point, 00:04:19.900 --> 00:04:22.940 we see utilities down or all the utilities 00:04:22.940 --> 00:04:25.700 that we're working on to get relocated 00:04:25.700 --> 00:04:28.540 by that September 23 timeframe. 00:04:28.540 --> 00:04:32.200 We believe that we will make that date. 00:04:32.200 --> 00:04:36.940 TxDOT and City of Dent's been working diligently 00:04:36.940 --> 00:04:40.820 to ensure that the additional scope of work 00:04:40.820 --> 00:04:43.580 that we added to the project doesn't impact 00:04:43.580 --> 00:04:45.820 the city's ability to move their utilities. 00:04:45.820 --> 00:04:50.460 And like I say, we're on track for September 23. 00:04:50.460 --> 00:04:52.380 And the difference between the let date 00:04:52.380 --> 00:04:53.220 and the ready to let is, 00:04:53.220 --> 00:04:55.860 ready to let is when everything's done. 00:04:55.860 --> 00:04:59.220 Ready to let is when the money currently is allocated 00:04:59.220 --> 00:05:02.220 because that's what the date they thought it would be. 00:05:02.220 --> 00:05:05.720 But once we show them that we can hit the 23 date, 00:05:05.720 --> 00:05:06.740 the funding is there. 00:05:06.740 --> 00:05:09.780 It's fully funded at $72 million, 00:05:09.780 --> 00:05:11.620 so we'll be able to move the project up 00:05:11.620 --> 00:05:13.180 to the ready to let date. 00:05:15.420 --> 00:05:16.260 Okay. 00:05:16.260 --> 00:05:22.060 The big job, the merge, 00:05:22.060 --> 00:05:25.140 we will be done with the RIDO acquisition 00:05:25.140 --> 00:05:25.980 at the end of this month. 00:05:25.980 --> 00:05:29.740 There's one parcel left that we have some legal work to do. 00:05:29.740 --> 00:05:33.860 The utilities are ongoing in this corridor. 00:05:33.860 --> 00:05:37.500 They are, you'll see in a second, quite lengthy. 00:05:37.500 --> 00:05:42.500 And we are pushing for a ready to let of August 23 as well. 00:05:43.980 --> 00:05:48.220 And again, the design's essentially done. 00:05:48.220 --> 00:05:55.140 We've been working with TxDOT on the aesthetics 00:05:55.140 --> 00:05:58.260 for this corridor 'cause we wanna be able 00:05:58.260 --> 00:05:59.540 to do some things in the corridor 00:05:59.540 --> 00:06:01.460 that we did in the 35E section 00:06:01.460 --> 00:06:03.500 where we added some aesthetics. 00:06:03.500 --> 00:06:05.540 And we are working on that packet 00:06:05.540 --> 00:06:09.340 to be included in the design and the construction 00:06:09.340 --> 00:06:11.740 of the project by TxDOT. 00:06:12.900 --> 00:06:16.780 And then again, here from utilities all the way down 00:06:16.780 --> 00:06:17.740 to the bottom of the page. 00:06:17.740 --> 00:06:20.980 These are all the utilities that have to get done, 00:06:20.980 --> 00:06:23.180 but we believe that we are gonna make that, 00:06:23.180 --> 00:06:27.620 what was it, August 23 date. 00:06:27.620 --> 00:06:33.560 The interim, that's done. 00:06:33.560 --> 00:06:36.140 We just wanted to leave it in one more month 00:06:36.140 --> 00:06:40.380 'cause it was a good project to see. 00:06:40.380 --> 00:06:42.820 And actually, we were waiting for a couple of the polls 00:06:42.820 --> 00:06:43.940 to be moved. 00:06:43.940 --> 00:06:47.380 And I did check from our last conversation we had 00:06:47.380 --> 00:06:49.220 that caution sign they have 00:06:49.220 --> 00:06:52.900 when there's congestion ahead, it triggers, 00:06:52.900 --> 00:06:55.660 it's not been triggered on this project 00:06:55.660 --> 00:06:57.900 since we've done the interim improvements. 00:06:57.900 --> 00:07:01.740 I don't know what's going on. 00:07:01.740 --> 00:07:06.900 All right, I-35 North, this is the $763 million one. 00:07:06.900 --> 00:07:09.020 It'll be ready to let in December 23. 00:07:09.020 --> 00:07:10.620 Again, it's fully funded. 00:07:10.620 --> 00:07:12.980 We get to that date, we can move the money, 00:07:12.980 --> 00:07:17.060 and that'll go all the way up to the county line. 00:07:17.060 --> 00:07:18.420 Again, lots of utilities. 00:07:18.420 --> 00:07:22.060 35W Frontage Road. 00:07:22.060 --> 00:07:25.060 So we've been waiting for TxDOT 00:07:25.060 --> 00:07:30.540 to enter into a contract with HNTB 00:07:30.540 --> 00:07:32.420 to do the design on this project 00:07:32.420 --> 00:07:34.740 that's environmentally cleared. 00:07:34.740 --> 00:07:36.300 Apparently, they couldn't get to a number, 00:07:36.300 --> 00:07:38.900 so TxDOT terminated that negotiations 00:07:38.900 --> 00:07:42.020 and they're negotiating with an alternate firm. 00:07:42.020 --> 00:07:44.540 They have not told us who that alternate firm is, 00:07:44.540 --> 00:07:48.100 but I told them they're running out of time, 00:07:48.100 --> 00:07:51.620 so we're kind of in a holding pattern on the design 00:07:51.620 --> 00:07:53.580 until TxDOT gets somebody on contract. 00:07:53.580 --> 00:07:59.260 You're at 380, 377 Corridor. 00:07:59.260 --> 00:08:00.620 That's under construction, 00:08:00.620 --> 00:08:03.380 and we're talking about a completion date. 00:08:03.380 --> 00:08:05.860 Here it is right here, December of 23. 00:08:05.860 --> 00:08:10.340 And right now, we're moving a little bit faster 00:08:10.340 --> 00:08:14.540 into phase two on the westbound side, 00:08:14.540 --> 00:08:17.180 and we're using daily closures to do that. 00:08:17.180 --> 00:08:21.060 And we're trying to get the bridges secured, 00:08:21.060 --> 00:08:23.580 the under abutments secured, 00:08:23.580 --> 00:08:28.180 so we can put that center median barrier 00:08:28.180 --> 00:08:29.980 because the accidents that are happening 00:08:29.980 --> 00:08:33.060 on this section of 380 are crossovers. 00:08:33.060 --> 00:08:35.180 And once we get the bridges shored up, 00:08:35.180 --> 00:08:37.780 we can put the physical barrier in the middle 00:08:37.780 --> 00:08:39.980 and it'll preclude those types of accidents. 00:08:39.980 --> 00:08:45.060 380 East, it's under construction. 00:08:45.060 --> 00:08:49.500 It's basically a lot of the dirt removal 00:08:49.500 --> 00:08:53.420 and stormwater work and a lot of culverts. 00:08:53.420 --> 00:08:57.060 And so it's mostly underground work that you're seeing done. 00:08:57.060 --> 00:08:58.740 And I would just say if you don't have to go out there, 00:08:58.740 --> 00:09:00.940 don't go out there 'cause it's pretty rough. 00:09:02.420 --> 00:09:07.420 Okay, the 380 feasibility study has been completed. 00:09:07.420 --> 00:09:12.220 And it essentially says there was a lot of stuff 00:09:12.220 --> 00:09:13.540 about the integrated corridor, 00:09:13.540 --> 00:09:16.220 a lot of stuff about the outer loop in it. 00:09:16.220 --> 00:09:21.060 And the 380 feasibility says we're gonna build a freeway 00:09:21.060 --> 00:09:25.140 on the blue section and we need to add frontage roads 00:09:25.140 --> 00:09:27.780 to the brown section of the loop. 00:09:28.660 --> 00:09:32.660 And so it's closed out and so we're gonna get back 00:09:32.660 --> 00:09:36.380 with TxDOT tomorrow and get some clarity 00:09:36.380 --> 00:09:39.900 on some of the components of your thoroughfare plan 00:09:39.900 --> 00:09:41.020 and the county's thoroughfare plan 00:09:41.020 --> 00:09:42.140 to make sure they're consistent 00:09:42.140 --> 00:09:44.740 with the findings of this report. 00:09:44.740 --> 00:09:47.020 But there'll be things coming off. 00:09:47.020 --> 00:09:50.580 For example, we had references to the integrated corridor. 00:09:50.580 --> 00:09:52.700 That's no longer a thing. 00:09:52.700 --> 00:09:55.060 And so we're just taking the outer loop 00:09:55.060 --> 00:09:57.140 all the way across to Milam. 00:09:57.140 --> 00:09:59.060 And 380 will be the freeway 00:09:59.060 --> 00:10:01.900 and 288 will be turned into a freeway. 00:10:01.900 --> 00:10:06.220 And so we'll get with city staff and TxDOT together 00:10:06.220 --> 00:10:08.020 and then we'll come back to you with recommendations 00:10:08.020 --> 00:10:10.220 on changing your thoroughfare plan 00:10:10.220 --> 00:10:12.500 to acknowledge those things. 00:10:12.500 --> 00:10:16.380 And speaking of Luke 28 West, 00:10:16.380 --> 00:10:18.660 this takes it from 35 all the way around. 00:10:18.660 --> 00:10:20.580 We have Chang Patel on contract. 00:10:20.580 --> 00:10:24.780 And they are doing the design 00:10:24.780 --> 00:10:29.780 and the design is anticipated to be October 23. 00:10:29.780 --> 00:10:32.060 We're shooting for a 26 ready to let date 00:10:32.060 --> 00:10:35.540 because we have a lot of utilities we have to deal with 00:10:35.540 --> 00:10:37.660 in this corridor and not the least of which 00:10:37.660 --> 00:10:41.620 are all the natural gas providers out there 00:10:41.620 --> 00:10:42.820 that we have to avoid. 00:10:42.820 --> 00:10:46.780 1515 LTRA is doing that work. 00:10:46.780 --> 00:10:48.140 We got the reevaluation. 00:10:48.140 --> 00:10:51.620 Remember we came back after we got environmentally cleared, 00:10:51.620 --> 00:10:54.700 removed the traffic circle, made some tweaks 00:10:54.700 --> 00:10:59.700 at the Peterbilt location and some other places. 00:10:59.700 --> 00:11:03.660 And we've got the reeval done. 00:11:03.660 --> 00:11:08.060 So now we're able to finalize the design set 00:11:08.060 --> 00:11:13.060 and go back to hit our schedule for the 1515. 00:11:13.060 --> 00:11:20.780 1173, we hired half associates last month. 00:11:21.980 --> 00:11:25.820 I can't remember to do the PS and E on this job. 00:11:25.820 --> 00:11:29.900 And what we're trying to do is hit a June of next, 00:11:29.900 --> 00:11:34.900 this year for 60% plans adequate 00:11:34.900 --> 00:11:38.180 because when you hit that in June, 00:11:38.180 --> 00:11:41.940 that allows tech stock to start the utility relocations 00:11:41.940 --> 00:11:43.220 on this project. 00:11:43.220 --> 00:11:47.580 And we're trying to get this project to be consistent 00:11:47.580 --> 00:11:51.340 with the 35 jobs so that when we do the 35 job, 00:11:51.340 --> 00:11:54.740 we can, for a billion dollars project, 00:11:54.740 --> 00:11:59.020 you know, 47 million dollars is a rounding error 00:11:59.020 --> 00:12:01.780 and we're gonna try to get that project built with 35. 00:12:01.780 --> 00:12:09.300 Almond Locus, so I think we're working internally on that. 00:12:09.300 --> 00:12:13.420 I'm gonna be quiet at this point. 00:12:21.180 --> 00:12:22.780 Operator Error. 00:12:22.780 --> 00:12:24.060 - Yes, John, thank you so much. 00:12:24.060 --> 00:12:29.020 So we have received plans actually yesterday from TechStot 00:12:29.020 --> 00:12:32.300 for the Almond Locus corridor that's south of the square. 00:12:32.300 --> 00:12:35.060 And then we're gonna be meeting internally to review those. 00:12:35.060 --> 00:12:37.260 The field meetings have been conducted 00:12:37.260 --> 00:12:40.060 and working through that execution plan 00:12:40.060 --> 00:12:41.700 and making sure that we're all in agreement 00:12:41.700 --> 00:12:45.220 with the path forward and the pavement repair in that area. 00:12:45.220 --> 00:12:47.940 So because the plans are completed, 00:12:47.940 --> 00:12:49.500 once we can work through those steps 00:12:49.500 --> 00:12:51.540 of having those internal discussions, 00:12:51.540 --> 00:12:53.980 turning our comments back over to TechStot, 00:12:53.980 --> 00:12:55.780 then they'll give us a schedule from there 00:12:55.780 --> 00:12:58.540 as to what they anticipate to have that area completed. 00:12:58.540 --> 00:12:59.380 So-- 00:12:59.380 --> 00:13:03.620 - Pardon me, so how soon would we get to, 00:13:03.620 --> 00:13:05.620 at least even like a sketchy timetable? 00:13:05.620 --> 00:13:07.340 This is one of the areas, you know, 00:13:07.340 --> 00:13:08.700 we get asked about the most. 00:13:08.700 --> 00:13:11.660 - Sure, we do too, I feel your pain. 00:13:11.660 --> 00:13:16.260 Definitely, what I would anticipate 00:13:16.260 --> 00:13:18.220 is once we can have those internal conversations 00:13:18.220 --> 00:13:20.340 being that we received the plans yesterday 00:13:20.340 --> 00:13:22.420 and can work through that, I would anticipate 00:13:22.420 --> 00:13:24.220 that within the next timeframe 00:13:24.220 --> 00:13:26.100 of when we have the next mobility committee meeting, 00:13:26.100 --> 00:13:27.500 we could be able to produce you 00:13:27.500 --> 00:13:30.060 and provide you a schedule at that time. 00:13:30.060 --> 00:13:31.740 It's gonna take a little bit of time internally 00:13:31.740 --> 00:13:34.020 for us to have those final conversations, 00:13:34.020 --> 00:13:36.540 review that set of plans, but I would hope 00:13:36.540 --> 00:13:39.740 that we would have a rough schedule of that timeframe 00:13:39.740 --> 00:13:41.780 of when they could actually start the construction 00:13:41.780 --> 00:13:42.980 through their maintenance contract 00:13:42.980 --> 00:13:46.220 by the time we have the next mobility committee meeting. 00:13:46.220 --> 00:13:48.740 - And because it's a maintenance contract, 00:13:48.740 --> 00:13:51.300 it's more expeditious and, you know, 00:13:51.300 --> 00:13:54.260 if we get this last part done soon enough, 00:13:54.260 --> 00:13:57.220 I think that we're coming into a good paving season. 00:13:57.220 --> 00:14:00.180 You know, it'll just be a matter of us pressuring them 00:14:00.180 --> 00:14:02.140 to make it a priority. 00:14:02.140 --> 00:14:03.780 I think they already think it is. 00:14:03.780 --> 00:14:07.140 - That's what a priority looks like, okay. 00:14:07.140 --> 00:14:11.860 Can you help us with just like a short explanation 00:14:11.860 --> 00:14:13.860 or some language to answer the question, 00:14:13.860 --> 00:14:15.500 why has it taken so long? 00:14:16.980 --> 00:14:18.900 - Yes, the short answer? 00:14:18.900 --> 00:14:20.700 - Yeah, not the fully technical one, 00:14:20.700 --> 00:14:22.380 but when you can tell your neighbor. 00:14:22.380 --> 00:14:25.300 - Elm and Locust are tech stock project, our roads, 00:14:25.300 --> 00:14:28.500 but they are roads that were older roads 00:14:28.500 --> 00:14:30.380 that were basically put on the system 00:14:30.380 --> 00:14:33.220 when we did some stuff to 377th Street Town. 00:14:33.220 --> 00:14:36.380 City has always had utilities under the pavement 00:14:36.380 --> 00:14:39.100 and that causes problems with the pavement 00:14:39.100 --> 00:14:42.700 and the utilities and this last cycle 00:14:42.700 --> 00:14:43.780 of where the city needed to come in 00:14:43.780 --> 00:14:45.900 and do some very significant improvements 00:14:45.900 --> 00:14:48.580 to the downtown area for the utilities and drainage. 00:14:48.580 --> 00:14:52.740 Tech stock said, look, at one point a couple years ago, 00:14:52.740 --> 00:14:54.900 they held our permits hostage 00:14:54.900 --> 00:14:57.340 'cause they said, we're not gonna let you do the work 00:14:57.340 --> 00:14:59.260 until you agree to take it off system. 00:14:59.260 --> 00:15:00.820 Well, now they've even reversed that 00:15:00.820 --> 00:15:03.780 and we have to like negotiate to get it off system. 00:15:03.780 --> 00:15:05.860 And so that held us up for a while 00:15:05.860 --> 00:15:07.980 and we finally got them to give us the permits 00:15:07.980 --> 00:15:09.340 and then it was a matter of, 00:15:09.340 --> 00:15:10.740 oh, we're gonna take it off system 00:15:10.740 --> 00:15:13.540 but it depends on quality of the road once it's done 00:15:13.540 --> 00:15:15.660 'cause right now we're gonna tear it up 00:15:15.660 --> 00:15:20.100 and we don't wanna go back and do a base repair 00:15:20.100 --> 00:15:22.860 and full depth on those areas that we mess up 00:15:22.860 --> 00:15:25.460 and then you come back behind us and tear it all out 00:15:25.460 --> 00:15:28.020 and fix it to our standards and give it back to us. 00:15:28.020 --> 00:15:29.900 So there was a negotiated battle 00:15:29.900 --> 00:15:32.260 that dealt with that for about a year. 00:15:32.260 --> 00:15:37.260 And so it's just the process of you have a city road, 00:15:37.260 --> 00:15:41.580 it's a state facility with city utilities in it 00:15:41.580 --> 00:15:43.580 and they all have different purposes 00:15:43.580 --> 00:15:47.180 and they all have ways of getting in each other's way. 00:15:47.180 --> 00:15:50.460 - Trying to think of how to make that simpler. 00:15:50.460 --> 00:15:52.380 - I would just like to add to that 00:15:52.380 --> 00:15:56.380 because it's a textile roadway, textile gave us the permit 00:15:56.380 --> 00:15:58.740 to go ahead and do the construction 00:15:58.740 --> 00:16:00.900 for the water and sewer underneath the roadway, 00:16:00.900 --> 00:16:02.500 although it's a textile roadway. 00:16:02.500 --> 00:16:06.560 There's some terminology that we're still working through 00:16:06.560 --> 00:16:09.260 because the city from my understandings, 00:16:09.260 --> 00:16:13.540 understanding was that it was gonna be completely rebuilt 00:16:13.540 --> 00:16:17.420 and with TechStop working through with a maintenance program, 00:16:17.420 --> 00:16:22.020 it's going to have more of a rehabilitation type measure. 00:16:22.020 --> 00:16:26.900 So I'm looking at the types of the useful life 00:16:26.900 --> 00:16:28.700 of the roadway that's going to be constructed 00:16:28.700 --> 00:16:30.100 before the city says, yes, 00:16:30.100 --> 00:16:31.900 that's the path we want to go down. 00:16:31.900 --> 00:16:34.940 So there's a lot of conversations going back and forth, 00:16:34.940 --> 00:16:36.180 just simply from the standpoint 00:16:36.180 --> 00:16:38.300 that yes, we need the roadway completed 00:16:38.300 --> 00:16:40.900 and we need the roadway fixed, obviously, right? 00:16:40.900 --> 00:16:43.540 We all know that, we all have that same concern, 00:16:43.540 --> 00:16:44.760 but I also don't want, 00:16:44.760 --> 00:16:46.860 and I know Danny Kramer's sitting over 00:16:46.860 --> 00:16:48.780 in the area over there, 00:16:48.780 --> 00:16:51.700 but he has the individual with public works 00:16:51.700 --> 00:16:53.620 over the entire street operation, 00:16:53.620 --> 00:16:56.260 the city doesn't wanna accept and take a roadway 00:16:56.260 --> 00:16:59.380 into our system that doesn't meet our standards. 00:16:59.380 --> 00:17:02.800 And so it's a constant conversation, 00:17:02.800 --> 00:17:04.860 making sure that what is constructed 00:17:04.860 --> 00:17:07.060 is something that the city's comfortable with 00:17:07.060 --> 00:17:09.060 to the standard that we're comfortable with, 00:17:09.060 --> 00:17:11.860 because the previous conversations were 00:17:11.860 --> 00:17:13.220 from the understanding that 00:17:13.220 --> 00:17:15.660 if we did this utility work and drainage work, 00:17:15.660 --> 00:17:18.860 the roadway was gonna be completely reconstructed. 00:17:18.860 --> 00:17:21.100 It's now looking as if that's a more 00:17:21.100 --> 00:17:23.620 of a maintenance rehabilitation. 00:17:23.620 --> 00:17:26.420 So we're looking at what does that truly mean? 00:17:26.420 --> 00:17:28.600 And like I said, we got the plans yesterday 00:17:28.600 --> 00:17:30.000 so that we can now evaluate it. 00:17:30.000 --> 00:17:32.500 Staffs had multiple field visits, 00:17:32.500 --> 00:17:35.160 but I myself don't feel comfortable, 00:17:35.160 --> 00:17:37.420 and I know city manager's office 00:17:37.420 --> 00:17:39.180 and then of course, street operations, 00:17:39.180 --> 00:17:40.480 doesn't wanna take something on, 00:17:40.480 --> 00:17:42.340 nor does Textodot at this time 00:17:42.340 --> 00:17:44.540 want to put together that agreement 00:17:44.540 --> 00:17:47.260 that's not something that we can all come to terms with. 00:17:47.260 --> 00:17:49.820 And ultimately it impacts also, 00:17:49.820 --> 00:17:51.920 the roadways further north in this area. 00:17:51.920 --> 00:17:54.140 So it's kind of a catch-22 00:17:54.140 --> 00:17:55.780 because they don't typically allow you 00:17:55.780 --> 00:17:57.580 to have utilities in the roadway. 00:17:57.580 --> 00:17:58.540 Those are past history. 00:17:58.540 --> 00:18:01.300 Those things happen probably in the 20s, 40s. 00:18:01.300 --> 00:18:03.420 I have no idea when that was constructed. 00:18:03.420 --> 00:18:05.500 So just understand the reason 00:18:05.500 --> 00:18:07.040 why it's taking a little bit of time 00:18:07.040 --> 00:18:09.860 is because we wanna make sure if we do say yes, 00:18:09.860 --> 00:18:11.300 we wanna move forward with that turn back 00:18:11.300 --> 00:18:13.380 and take that portion of the roadway over, 00:18:13.380 --> 00:18:14.540 that it's built to a standard 00:18:14.540 --> 00:18:16.020 that the city is comfortable with. 00:18:16.020 --> 00:18:18.560 - So let me try, and go ahead, please. 00:18:18.560 --> 00:18:22.440 - I was gonna wait until you were done. 00:18:22.440 --> 00:18:27.440 Yeah, I just have, what's circulating in my head 00:18:27.440 --> 00:18:32.860 is that any citizen that is driving through, 00:18:32.860 --> 00:18:37.460 of course the complaint is that it's just taking so long 00:18:37.460 --> 00:18:39.380 versus what they actually see. 00:18:39.380 --> 00:18:42.680 Big pipes on the road, things opening up. 00:18:42.680 --> 00:18:46.780 It's obvious that they are expanding 00:18:46.780 --> 00:18:48.240 because the city is growing. 00:18:48.240 --> 00:18:49.580 That's what I say. 00:18:49.580 --> 00:18:51.740 It's road work because the city is growing 00:18:51.740 --> 00:18:54.000 and they need to put bigger pipes in. 00:18:54.000 --> 00:18:57.960 That seems to be the basic type of conversation. 00:18:57.960 --> 00:19:02.820 But now I'm thinking, as I'm hearing, 00:19:02.820 --> 00:19:07.820 that the utilities are literally under the road, right? 00:19:07.820 --> 00:19:09.460 Is that what I heard? 00:19:09.460 --> 00:19:10.300 - Yes, ma'am, that's correct. 00:19:10.300 --> 00:19:13.700 - Because we're going to be upgrading some utilities 00:19:13.700 --> 00:19:17.700 under some roads that are in, already here. 00:19:17.700 --> 00:19:22.220 I appreciate hearing that. 00:19:22.220 --> 00:19:24.700 So generally, where are the utilities located 00:19:24.700 --> 00:19:26.460 when a new road is built? 00:19:26.460 --> 00:19:29.380 - Utilities are always located underneath the roadway. 00:19:29.380 --> 00:19:30.620 - Yeah, on a city road. 00:19:30.620 --> 00:19:31.740 - On a city roadway. 00:19:31.740 --> 00:19:34.220 Elm and Locus are state roads 00:19:34.220 --> 00:19:36.820 and the state doesn't allow utilities under their pavement. 00:19:36.820 --> 00:19:40.820 They'd have a 15-foot parkway on either side of the roadway 00:19:40.820 --> 00:19:44.180 that they allow utilities in 00:19:44.180 --> 00:19:47.020 and all the drainage for the roadway itself 00:19:47.020 --> 00:19:48.980 can be under pavement, 00:19:48.980 --> 00:19:52.140 but the utilities have to be outside in the parkway. 00:19:52.140 --> 00:19:54.140 - So this, I'm sorry. 00:19:54.140 --> 00:19:54.980 - No, go ahead. 00:19:54.980 --> 00:19:56.460 I was just going to say that typically, 00:19:56.460 --> 00:19:59.100 from the city perspective, what John's describing, 00:19:59.100 --> 00:20:01.780 that's called the utility accommodation zone. 00:20:01.780 --> 00:20:03.140 Cities typically don't go 00:20:03.140 --> 00:20:04.860 within the utility accommodation zone. 00:20:04.860 --> 00:20:06.700 We purchase, as you're aware of, 00:20:06.700 --> 00:20:08.580 of course, with the 35 Project, 00:20:08.580 --> 00:20:10.700 easements that are outside the right-of-way line 00:20:10.700 --> 00:20:12.860 so that our facilities can go in, 00:20:12.860 --> 00:20:15.980 water or sewer easements outside the TxDOT roadway. 00:20:15.980 --> 00:20:16.820 Correct. 00:20:16.820 --> 00:20:18.700 - But that can't happen on this roadway 00:20:18.700 --> 00:20:20.340 because it's an older road. 00:20:20.340 --> 00:20:23.060 - Well, the outside of the roadway is the sidewalk 00:20:23.060 --> 00:20:25.580 and then outside the sidewalk is the building. 00:20:25.580 --> 00:20:26.420 - Yeah. 00:20:26.420 --> 00:20:27.260 - So we are-- 00:20:27.260 --> 00:20:28.460 - So you're saying what we want. 00:20:28.460 --> 00:20:31.500 - Yeah, we're restricted. 00:20:31.500 --> 00:20:32.460 And so the good news is, 00:20:32.460 --> 00:20:33.900 the reason why I think the maintenance contract 00:20:33.900 --> 00:20:35.740 is going to go faster than we think 00:20:35.740 --> 00:20:37.180 is because about two months ago, 00:20:37.180 --> 00:20:39.420 the commission threw everybody a curve ball 00:20:39.420 --> 00:20:42.580 and says we may not be interested in turn back anymore. 00:20:42.580 --> 00:20:45.020 And so we may get the road upgraded, 00:20:45.020 --> 00:20:47.460 leave the utilities in the ground, 00:20:47.460 --> 00:20:49.460 and TxDOT come back and later go, 00:20:49.460 --> 00:20:51.180 we're not going to give it to you. 00:20:51.180 --> 00:20:53.140 So then you don't have to maintain it. 00:20:53.140 --> 00:20:53.980 - That's interesting. 00:20:53.980 --> 00:20:56.980 'Cause our call, we're clearly voting. 00:20:56.980 --> 00:20:59.780 I didn't vote for it, but there was a vote on council 00:20:59.780 --> 00:21:01.700 to say that we would take it. 00:21:01.700 --> 00:21:04.620 I'm sorry. 00:21:04.620 --> 00:21:06.700 - Yeah, so I just wanted to, 00:21:06.700 --> 00:21:10.260 I don't know if now is the appropriate time to bring it up, 00:21:10.260 --> 00:21:11.100 but I just wanted to kind of, 00:21:11.100 --> 00:21:13.540 you know me, I like to throw ideas out there 00:21:13.540 --> 00:21:16.420 regardless of whether they're realistic or not. 00:21:16.420 --> 00:21:20.700 But given that we've got Paul and Brittany here today, 00:21:20.700 --> 00:21:23.380 I wonder if now would be a good opportunity 00:21:23.380 --> 00:21:27.340 to talk about this section of roadway 00:21:27.340 --> 00:21:29.620 and the section of roadway to the north. 00:21:29.620 --> 00:21:32.660 I know that the, you know, the phase one area, 00:21:32.660 --> 00:21:34.180 there aren't currently any bus routes 00:21:34.180 --> 00:21:37.500 that run on that roadway, 00:21:37.500 --> 00:21:39.860 but this is, you know, the core of the city. 00:21:39.860 --> 00:21:43.740 And as bus routes change and evolve over the years, 00:21:43.740 --> 00:21:48.180 you know, I hope that we'll have an eye toward roadway design 00:21:48.180 --> 00:21:51.460 that's accommodating of buses. 00:21:51.460 --> 00:21:54.860 You know, maybe that could include a pull-off 00:21:54.860 --> 00:21:57.420 or maybe it's just, I mean, 00:21:57.420 --> 00:21:59.100 I don't know if there are any design standards 00:21:59.100 --> 00:22:01.700 as far as like the quality of the pavement 00:22:01.700 --> 00:22:03.540 that needs to be bolstered 00:22:03.540 --> 00:22:04.980 if there are gonna be buses on it, 00:22:04.980 --> 00:22:06.420 but something to consider I think. 00:22:06.420 --> 00:22:08.620 - So if it stays on system, 00:22:08.620 --> 00:22:11.180 a lot of that, I mean, the pavement thickness 00:22:11.180 --> 00:22:13.340 is gonna be what the pavement thickness needs to be. 00:22:13.340 --> 00:22:16.060 But if it's on system, a lot of that stuff 00:22:16.060 --> 00:22:18.860 to accommodate the transit won't be allowed. 00:22:20.580 --> 00:22:22.060 That was part of the reason why we wanted 00:22:22.060 --> 00:22:24.700 to get it off system because once it's off system, 00:22:24.700 --> 00:22:26.900 you can create it in your own image. 00:22:26.900 --> 00:22:29.860 - And I would also mention that as we look at the plans 00:22:29.860 --> 00:22:33.100 that are being evaluated that we received, 00:22:33.100 --> 00:22:34.580 we also are gonna be looking at 00:22:34.580 --> 00:22:36.980 how the roadway can be striped, right? 00:22:36.980 --> 00:22:40.300 We wanna continue to have the two-lane capacity. 00:22:40.300 --> 00:22:42.260 I realize when you're coming, you know, 00:22:42.260 --> 00:22:45.340 going northbound on Locust, it's actually three lanes, 00:22:45.340 --> 00:22:47.580 but what Nathan is evaluating is looking at 00:22:47.580 --> 00:22:51.540 how we can include bike lanes, pedestrian facilities. 00:22:51.540 --> 00:22:53.220 TxDOT's not evaluating that 00:22:53.220 --> 00:22:55.780 because that's not a part of their overall approach, 00:22:55.780 --> 00:22:57.820 but it's working on that collaboration 00:22:57.820 --> 00:23:01.900 of what can we do to have the roadway striped appropriately 00:23:01.900 --> 00:23:04.100 to make sure that that's a corridor, 00:23:04.100 --> 00:23:06.420 that we do have the pedestrian accommodations 00:23:06.420 --> 00:23:07.740 and the bicycle accommodations 00:23:07.740 --> 00:23:10.660 to bring that multimodal approach to that roadway. 00:23:10.660 --> 00:23:13.100 - So just so you know, 00:23:13.100 --> 00:23:15.820 the reason why they have terminated turnbacks 00:23:15.820 --> 00:23:17.740 is because they found out that communities 00:23:17.740 --> 00:23:19.740 were taking their state facilities, 00:23:19.740 --> 00:23:23.460 reducing capacity and doing everything that Becky just said. 00:23:23.460 --> 00:23:25.460 And so that's when they killed it. 00:23:25.460 --> 00:23:27.540 They took one back from San Antonio 00:23:27.540 --> 00:23:30.100 that they gave to them in 2014, 00:23:30.100 --> 00:23:32.580 and they were about to go to construction with it, so. 00:23:32.580 --> 00:23:34.660 - Because, but what? 00:23:34.660 --> 00:23:37.500 - How dare a city provide accommodations 00:23:37.500 --> 00:23:39.140 for a desk fan? - Yeah, because they added 00:23:39.140 --> 00:23:40.500 facilities? - No, they, 00:23:40.500 --> 00:23:44.540 because they went from number of lanes to less lanes, 00:23:44.540 --> 00:23:46.980 and then they turned them into a multimodal facility. 00:23:46.980 --> 00:23:48.100 So everything you want to do, 00:23:48.100 --> 00:23:49.380 everything that everybody wants to do 00:23:49.380 --> 00:23:50.860 are the things they don't want you to do. 00:23:50.860 --> 00:23:53.740 And I'll be careful on how I say this, 00:23:53.740 --> 00:23:57.020 but there is some irony, or confusion. 00:23:57.020 --> 00:24:00.020 Well, someone's listening. 00:24:00.020 --> 00:24:03.700 They want you to take the road. 00:24:03.700 --> 00:24:05.900 It would be like buying a house from somebody, 00:24:05.900 --> 00:24:06.740 and then they tell you, 00:24:06.740 --> 00:24:09.020 you can't do any remodeling to it, right? 00:24:09.020 --> 00:24:10.820 After it's yours. - Yeah, that's weird. 00:24:10.820 --> 00:24:11.660 - That's what we're doing. 00:24:11.660 --> 00:24:13.820 - You know, I'm sorry to be beating at that horse. 00:24:13.820 --> 00:24:14.660 I know we got more to cover, 00:24:14.660 --> 00:24:17.460 but just a couple loose ends on this topic. 00:24:17.460 --> 00:24:22.420 Am I correct in understanding that the utility work, 00:24:22.420 --> 00:24:23.780 it's not just a matter of upgrading, 00:24:23.780 --> 00:24:26.980 it's part of the PEC-4, this is a question, 00:24:26.980 --> 00:24:29.260 is it part of the PEC-4 deal where, 00:24:29.260 --> 00:24:32.300 you know, it's, where we've done necessary work 00:24:32.300 --> 00:24:34.620 to get that area out of the floodplain? 00:24:34.620 --> 00:24:36.460 Is it connected with that? 00:24:36.460 --> 00:24:38.900 - The utility work, water and sewer construction, 00:24:38.900 --> 00:24:41.540 and also the drainage construction is complete. 00:24:41.540 --> 00:24:43.140 And we are working through what's called 00:24:43.140 --> 00:24:47.500 a LOMAR process to remove the area for phase one and two 00:24:47.500 --> 00:24:49.300 out of the floodplain, you are correct. 00:24:49.300 --> 00:24:50.340 - So it is part of that. 00:24:50.340 --> 00:24:52.860 So it's, we can talk a little more about it offline, 00:24:52.860 --> 00:24:54.380 but it's a really good thing. 00:24:54.380 --> 00:24:58.860 But, and then just to, for me, cap it off. 00:24:58.860 --> 00:25:01.540 So that, that's a good thing, I understand that. 00:25:01.540 --> 00:25:03.340 And then it's the status that the really, 00:25:03.340 --> 00:25:05.220 after the utility work, 00:25:05.220 --> 00:25:07.740 that there hasn't really been a lot of movement 00:25:07.740 --> 00:25:11.140 on the ground because we're in this negotiation 00:25:11.140 --> 00:25:16.140 over which way it's gonna get rebuilt or, you know. 00:25:16.140 --> 00:25:20.140 - So just, the guy that works for me, 00:25:20.140 --> 00:25:21.860 he used to be the area engineer here, 00:25:21.860 --> 00:25:24.540 and he had an anecdotal story with it. 00:25:24.540 --> 00:25:27.220 When he did a resurfacing of Elmer Locus at one point, 00:25:27.220 --> 00:25:30.780 and he, the contractor had, part of the contract 00:25:30.780 --> 00:25:33.420 was to when he discovered base failure, 00:25:33.420 --> 00:25:35.180 he was to repair the base failure, 00:25:35.180 --> 00:25:37.980 and he only had like 15%, whatever. 00:25:37.980 --> 00:25:39.820 And there was one area of Elmer Locus 00:25:39.820 --> 00:25:41.540 where they uncovered the pavement, 00:25:41.540 --> 00:25:45.340 they found a sinkhole big enough to put a car in. 00:25:45.340 --> 00:25:46.180 - Wow. 00:25:46.180 --> 00:25:49.140 - There wasn't anything between the pavement and that hole. 00:25:49.140 --> 00:25:51.300 We weren't sure how the road stayed up. 00:25:51.300 --> 00:25:53.820 And so what the city wants to make sure is, 00:25:53.820 --> 00:25:58.300 is that, you know, you got a pretty two inch overlay, 00:25:58.300 --> 00:25:59.660 it's not on quicksand. 00:25:59.660 --> 00:26:01.280 - Yeah, yeah. 00:26:01.280 --> 00:26:02.120 - And I just-- 00:26:02.120 --> 00:26:03.780 - I'm done, go ahead, did you? 00:26:03.780 --> 00:26:05.020 - Oh yeah, I'm done. 00:26:05.020 --> 00:26:06.420 - One last thing I just wanna mention 00:26:06.420 --> 00:26:07.900 with this entire conversation, 00:26:07.900 --> 00:26:10.500 we're only talking about the green section on the map, 00:26:10.500 --> 00:26:11.900 which is phase one. 00:26:11.900 --> 00:26:14.940 Obviously the blue section on the map, 00:26:14.940 --> 00:26:17.820 we still have water and wastewater utilities to improve. 00:26:17.820 --> 00:26:20.100 We still need a large sum of money 00:26:20.100 --> 00:26:22.780 to do the drainage improvements along that area. 00:26:22.780 --> 00:26:25.140 And then of course a similar conversation with TxDOT 00:26:25.140 --> 00:26:27.900 as to how the roadway will be reconstructed. 00:26:27.900 --> 00:26:30.220 So just wanted to clarify that the conversation 00:26:30.220 --> 00:26:32.540 we're having is just specifically with the areas 00:26:32.540 --> 00:26:36.140 of water insert that's already been completed and drainage. 00:26:36.140 --> 00:26:38.020 South of the courthouse. 00:26:38.020 --> 00:26:38.860 - Yes, sir. 00:26:38.860 --> 00:26:41.020 - Great, okay. 00:26:41.020 --> 00:26:43.860 Thanks for-- 00:26:43.860 --> 00:26:45.660 - Just for the record, all my reports 00:26:45.660 --> 00:26:47.140 that I've gone over really fast. 00:26:47.140 --> 00:26:49.500 When we get to the one for Becky, it takes longer. 00:26:49.500 --> 00:26:52.380 Oh, now we're done. 00:26:52.380 --> 00:26:54.060 - Well, actually-- 00:26:54.060 --> 00:26:54.900 - Actually. 00:26:54.900 --> 00:26:57.460 - I wonder if, you know, the other one 00:26:57.460 --> 00:27:00.460 that I hear the most about is Bonnie Bray, 00:27:00.460 --> 00:27:02.980 especially south of the university. 00:27:02.980 --> 00:27:05.580 Can we include a status on that when we talk about it? 00:27:05.580 --> 00:27:09.060 And, you know, it just, it doesn't feel 00:27:09.060 --> 00:27:14.060 to constituents like we're making any progress there. 00:27:14.060 --> 00:27:16.740 - So Bonnie Bray, phase four-- 00:27:16.740 --> 00:27:17.820 - Bonnie Bray, south of the university. 00:27:17.820 --> 00:27:20.020 - And five, but are you discussing, sir, 00:27:20.020 --> 00:27:25.020 between 380 and say 35, Bonnie Bray? 00:27:25.020 --> 00:27:26.060 - Yeah, south of the university. 00:27:26.060 --> 00:27:26.900 - University and-- 00:27:26.900 --> 00:27:27.740 - Sure. 00:27:27.740 --> 00:27:28.580 - So that's actually-- 00:27:28.580 --> 00:27:29.540 - Yeah, we're down to one lane, you know, 00:27:29.540 --> 00:27:31.700 big pipes along the side and all that, you know. 00:27:31.700 --> 00:27:33.500 - Staff can bring you a separate report 00:27:33.500 --> 00:27:35.180 as part of the staff update. 00:27:35.180 --> 00:27:37.220 If you'd like to continue to hear updates 00:27:37.220 --> 00:27:40.020 on the Bonnie Bray project, we don't have an issue with that. 00:27:40.020 --> 00:27:42.100 It's actually not a part of Mr. Polster's report 00:27:42.100 --> 00:27:46.460 because he's specifically talking about on-system roadways. 00:27:46.460 --> 00:27:47.940 - I thought we changed that, that it was, 00:27:47.940 --> 00:27:50.060 like it had been that for a long, long time. 00:27:50.060 --> 00:27:51.180 It was just textile. 00:27:51.180 --> 00:27:52.940 - No, no, for a long time, it was everything, 00:27:52.940 --> 00:27:55.100 and the stuff that wasn't me, I didn't know anything about, 00:27:55.100 --> 00:27:56.500 I was just putting it in a report. 00:27:56.500 --> 00:27:59.420 - Yeah, yeah, 'cause it's, we used to call it 00:27:59.420 --> 00:28:01.540 the on-system report, but now it's 00:28:01.540 --> 00:28:02.940 City of Denton Transportation. 00:28:02.940 --> 00:28:06.940 I thought we would cover our main, just topics of interest. 00:28:06.940 --> 00:28:11.500 Frankly, this precedes these guys being on here. 00:28:11.500 --> 00:28:13.860 Senator John Ryan asked for that. 00:28:13.860 --> 00:28:14.700 - I think the best way-- 00:28:14.700 --> 00:28:16.620 - It precedes you too, as a matter of fact. 00:28:16.620 --> 00:28:18.180 - Well, thank you. 00:28:18.180 --> 00:28:20.740 I think the best way for us to go about that, 00:28:20.740 --> 00:28:22.700 if you would be amenable to, 00:28:22.700 --> 00:28:25.420 is to have that as a part of our staff update, 00:28:25.420 --> 00:28:27.860 because it's a project that the city staff is managing, 00:28:27.860 --> 00:28:30.460 and it actually is something that we're collaborating 00:28:30.460 --> 00:28:33.220 with the county and the state on, specifically 00:28:33.220 --> 00:28:35.620 because of the funding, and of course because of, 00:28:35.620 --> 00:28:38.140 with COG, but it's not something that Mr. Polster 00:28:38.140 --> 00:28:39.620 would be able to have an update on. 00:28:39.620 --> 00:28:40.460 - Okay. 00:28:40.460 --> 00:28:42.940 - Yeah, if, I would appreciate it if we could get, you know, 00:28:42.940 --> 00:28:46.180 maybe a standing update each month from our staff, 00:28:46.180 --> 00:28:48.180 not from, not from John. 00:28:48.180 --> 00:28:49.020 - On Body, Brain, specifically? 00:28:49.020 --> 00:28:50.980 - Anyone but John. 00:28:50.980 --> 00:28:52.780 - Yes, on Body, Brain, specifically. 00:28:52.780 --> 00:28:53.620 - Sure, that's fine. 00:28:53.620 --> 00:28:56.380 - Since that's such a, such a big project, 00:28:56.380 --> 00:28:59.900 and it's so disruptive to a lot of folks, yeah. 00:29:01.060 --> 00:29:03.540 - Absolutely, we can add that as a part of the staff update. 00:29:03.540 --> 00:29:04.380 - Thank you. 00:29:04.380 --> 00:29:07.260 - Do we want to go over the acronyms? 00:29:07.260 --> 00:29:09.220 - Yes, absolutely. 00:29:09.220 --> 00:29:12.420 Thank you very much. 00:29:12.420 --> 00:29:14.820 - I can't turn it off. 00:29:14.820 --> 00:29:17.260 - Okay. 00:29:17.260 --> 00:29:21.900 I tend to, you know, I realize I tend to do these 00:29:21.900 --> 00:29:24.260 without breaks, is that, are you all right with that? 00:29:24.260 --> 00:29:27.100 Or would you like to take it, take, yeah, yeah, yeah. 00:29:27.100 --> 00:29:27.920 Okay. 00:29:29.500 --> 00:29:30.500 Okay, let me know. 00:29:30.500 --> 00:29:33.100 All right, so we'll move on to the next item. 00:29:33.100 --> 00:29:36.140 Receive a report and hold a discussion regarding updates 00:29:36.140 --> 00:29:38.700 from the Potentum County Transportation Authority. 00:29:38.700 --> 00:29:41.180 - Good morning. 00:29:41.180 --> 00:29:42.020 - Good morning. 00:29:42.020 --> 00:29:47.220 - Put my millennial skills to use. 00:29:47.220 --> 00:29:51.300 Oh, no, not like that. 00:29:51.300 --> 00:29:52.140 Like that. 00:29:52.140 --> 00:29:55.660 All right, good morning, Mayor Potem-Melzer, 00:29:55.660 --> 00:29:56.700 members of the council. 00:29:56.700 --> 00:29:57.900 My name is Brittany Farr. 00:29:57.900 --> 00:29:59.620 I'm the Director of Government Relations 00:29:59.620 --> 00:30:01.940 for Denton County Transportation Authority, 00:30:01.940 --> 00:30:03.140 and we are here today to provide you 00:30:03.140 --> 00:30:06.500 with an update of our activities at DCTA. 00:30:06.500 --> 00:30:09.540 I'll start by introducing our Deputy CEO, 00:30:09.540 --> 00:30:11.060 Mr. Paul Christina. 00:30:11.060 --> 00:30:13.180 As you're no doubt aware, Mr. Raymond Suarez 00:30:13.180 --> 00:30:15.580 submitted his resignation this month. 00:30:15.580 --> 00:30:18.300 As of April 1st, Mr. Christina will be taking over 00:30:18.300 --> 00:30:20.460 as our interim CEO. 00:30:20.460 --> 00:30:22.860 Seeing as how this is both of our first time 00:30:22.860 --> 00:30:23.900 to address this committee, 00:30:23.900 --> 00:30:26.940 we're going to tag team it today, safer in numbers. 00:30:26.940 --> 00:30:28.300 So I'll bring up Mr. Christina. 00:30:28.300 --> 00:30:29.980 He'll introduce himself, 00:30:29.980 --> 00:30:31.500 talk a little bit about our efforts 00:30:31.500 --> 00:30:33.540 around the comprehensive operation 00:30:33.540 --> 00:30:36.220 and fare structure analysis that's going on, 00:30:36.220 --> 00:30:37.300 and then I'll come in at the end 00:30:37.300 --> 00:30:40.260 to provide an overview of the Connect service changes 00:30:40.260 --> 00:30:43.300 that went into effect a couple of weeks ago on March 14th, 00:30:43.300 --> 00:30:45.580 as well as provide our response to the inclement weather 00:30:45.580 --> 00:30:48.660 that struck the region two times in the month of February. 00:30:48.660 --> 00:30:50.620 And then we'll both be here to answer any questions 00:30:50.620 --> 00:30:51.620 that you may have for us. 00:30:51.620 --> 00:30:53.980 So with that, I'll bring Paul up to the podium. 00:30:56.340 --> 00:30:58.820 Welcome, both of you. 00:30:58.820 --> 00:30:59.660 - Thank you very much. 00:30:59.660 --> 00:31:00.980 It's good to be with you. 00:31:00.980 --> 00:31:03.580 Like Brittany said, my name is Paul Christina, 00:31:03.580 --> 00:31:06.780 and I've been given the privilege of leading DCTA 00:31:06.780 --> 00:31:09.540 as an interim CEO beginning April 1st, 00:31:09.540 --> 00:31:10.860 and so I'm pleased to be with you today 00:31:10.860 --> 00:31:13.820 to provide the update on how we're moving forward 00:31:13.820 --> 00:31:15.780 with our comprehensive operations analysis 00:31:15.780 --> 00:31:19.220 that you all have been seeing in progress for some time. 00:31:19.220 --> 00:31:22.860 So at the core of what we're doing 00:31:22.860 --> 00:31:25.540 is that right now we're leveraging ridership data. 00:31:25.540 --> 00:31:28.820 - Do you want to take questions as you go, 00:31:28.820 --> 00:31:30.300 or should we hold them till the end? 00:31:30.300 --> 00:31:31.660 - I'm happy to have a conversation, 00:31:31.660 --> 00:31:33.660 so if you have questions and would like to raise your hand, 00:31:33.660 --> 00:31:35.740 please do, and we can talk through it, 00:31:35.740 --> 00:31:37.460 and that's just fine. 00:31:37.460 --> 00:31:38.940 Thank you for that. 00:31:38.940 --> 00:31:41.580 So right now what we're doing is designing 00:31:41.580 --> 00:31:44.860 an integrated service across all of DCTA's modes, 00:31:44.860 --> 00:31:47.340 and we're doing that by leveraging ridership data 00:31:47.340 --> 00:31:50.780 across GoZone and the Connect service 00:31:50.780 --> 00:31:52.420 in order to be able to make recommendations 00:31:52.420 --> 00:31:55.940 about the proper levels of service among those modes, 00:31:55.940 --> 00:31:58.660 fixed route and on demand, enabling us to implement 00:31:58.660 --> 00:31:59.820 what will be an integrated 00:31:59.820 --> 00:32:03.420 and complementary multimodal system. 00:32:03.420 --> 00:32:06.100 Fair pricing is part of that conversation 00:32:06.100 --> 00:32:08.980 because we believe that we can use the pricing 00:32:08.980 --> 00:32:11.340 of the GoZone service and the Connect service 00:32:11.340 --> 00:32:14.940 to cause riders to make decisions that are best for them 00:32:14.940 --> 00:32:18.700 and for the modes of service that we have available. 00:32:18.700 --> 00:32:20.460 So this chart here just shows 00:32:20.460 --> 00:32:21.740 the way that we're going to do that 00:32:21.740 --> 00:32:23.340 is right now we're in the process 00:32:23.340 --> 00:32:25.500 of looking at the fixed route network, 00:32:25.500 --> 00:32:27.100 and you've seen several revisions of that 00:32:27.100 --> 00:32:29.340 over the course of the last several months, 00:32:29.340 --> 00:32:32.980 and then as we think about how riders will use those 00:32:32.980 --> 00:32:37.140 or access those resources, it's through the GoZone app 00:32:37.140 --> 00:32:39.180 that will enable them to book a ride 00:32:39.180 --> 00:32:42.260 that uses a GoZone vehicle perhaps 00:32:42.260 --> 00:32:45.300 for a portion of their trip and a fixed route vehicle 00:32:45.300 --> 00:32:46.340 for the portion of their trip 00:32:46.340 --> 00:32:48.420 if that's the way that their trip aligns, 00:32:48.420 --> 00:32:50.780 and then like I said, we can use pricing, 00:32:50.780 --> 00:32:52.620 fair structure between those two modes 00:32:52.620 --> 00:32:55.580 to encourage the most efficient use of those resources 00:32:55.580 --> 00:32:57.460 and ultimately being able to deploy 00:32:57.460 --> 00:33:00.780 what is an intermodal solution for riders 00:33:00.780 --> 00:33:02.740 through the app or through the traditional means 00:33:02.740 --> 00:33:04.940 of purchasing tickets like they do today. 00:33:04.940 --> 00:33:12.140 - Does the app show alternate routes 00:33:12.140 --> 00:33:17.060 and estimated time of journey for each of them? 00:33:17.060 --> 00:33:20.020 - I think, so we're going to be going through this tomorrow 00:33:20.020 --> 00:33:23.020 with our board and just where we are in the process. 00:33:23.020 --> 00:33:24.780 It's going to be a very high level, 00:33:24.780 --> 00:33:27.220 but what I think you can expect to see 00:33:27.220 --> 00:33:30.020 is that a rider could put in their current origin, 00:33:30.020 --> 00:33:32.580 their destination, and provide here's the method 00:33:32.580 --> 00:33:34.380 by which you can use transit services 00:33:34.380 --> 00:33:36.700 to get from point A to point B. 00:33:36.700 --> 00:33:41.060 - The reason I ask that is as with any number 00:33:41.060 --> 00:33:44.580 of route planning apps that we all use, 00:33:44.580 --> 00:33:47.180 if the options are presented with the times 00:33:47.180 --> 00:33:50.420 and number of contacts, doesn't that provide incentive enough 00:33:50.420 --> 00:33:53.500 for the rider to go, oh, I want to go 00:33:53.500 --> 00:33:54.420 in the least amount of time 00:33:54.420 --> 00:33:57.300 or I want the one with the least changes. 00:33:57.300 --> 00:33:59.860 - Potentially, and I think that that sort of feedback 00:33:59.860 --> 00:34:03.300 is going to be really good for the public involvement process 00:34:03.300 --> 00:34:05.900 that we'll have over the course of the next 90 days. 00:34:05.900 --> 00:34:07.620 And so beginning about in April, 00:34:07.620 --> 00:34:09.180 again, our board will be briefed on this tomorrow, 00:34:09.180 --> 00:34:10.540 but there'll be a public comment period 00:34:10.540 --> 00:34:12.980 where people can provide that sort of feedback 00:34:12.980 --> 00:34:15.980 that could inform the way that these things get rolled out. 00:34:17.020 --> 00:34:17.860 Yes, ma'am. 00:34:17.860 --> 00:34:24.060 - Does that feedback also include comments from employees? 00:34:24.060 --> 00:34:28.220 - It is going to be an open public comment period 00:34:28.220 --> 00:34:32.460 that anyone will be able to provide input for, 00:34:32.460 --> 00:34:35.900 and when those channels are opened up, 00:34:35.900 --> 00:34:38.020 we're going to do our best effort 00:34:38.020 --> 00:34:40.860 to disseminate the channels for that far and wide 00:34:40.860 --> 00:34:43.820 so that everybody who's interested can make such comments. 00:34:46.740 --> 00:34:47.580 - Okay. 00:34:47.580 --> 00:34:52.540 So here's sort of a couple of bullets 00:34:52.540 --> 00:34:53.820 on where we've been and where we're going. 00:34:53.820 --> 00:34:56.820 It was in the December 2021 board meeting 00:34:56.820 --> 00:34:59.580 that we had the discussion about a COA 00:34:59.580 --> 00:35:02.340 that would be presented in the June 2022 meeting 00:35:02.340 --> 00:35:04.260 here in a few months to talk about 00:35:04.260 --> 00:35:06.340 the evolution of the service. 00:35:06.340 --> 00:35:10.620 We have on our team consultant experts from Accenture 00:35:10.620 --> 00:35:13.860 as well as VIA, who is the on-demand transportation provider 00:35:13.860 --> 00:35:18.060 for the GoZone project who are working 00:35:18.060 --> 00:35:20.580 to develop those alternatives. 00:35:20.580 --> 00:35:22.020 And we will have, like I said, 00:35:22.020 --> 00:35:24.260 a touch point with our board this month 00:35:24.260 --> 00:35:26.060 at tomorrow's board meeting to talk about 00:35:26.060 --> 00:35:27.740 how those things are being developed, 00:35:27.740 --> 00:35:30.020 then again in April and then again in May 00:35:30.020 --> 00:35:32.700 prior to the board making a decision in June, 00:35:32.700 --> 00:35:35.980 and obviously we will continue to use this forum 00:35:35.980 --> 00:35:38.020 as appropriate to provide updates 00:35:38.020 --> 00:35:39.740 on how that project progresses. 00:35:39.740 --> 00:35:43.220 In terms of the fare structure analysis 00:35:43.220 --> 00:35:45.500 and sort of the conversation that's being had, 00:35:45.500 --> 00:35:47.300 these are the things that we know. 00:35:47.300 --> 00:35:52.300 The initial GoZone program had a promotional price 00:35:52.300 --> 00:35:55.900 of 75 cents a ride, and then like I said before 00:35:55.900 --> 00:35:58.180 at the outset, the fare structure that we're considering 00:35:58.180 --> 00:36:02.340 will start there to determine what's the right way 00:36:02.340 --> 00:36:07.020 to engage riders to use the most efficient sort of trip 00:36:07.020 --> 00:36:08.740 to get where they're trying to go. 00:36:08.740 --> 00:36:11.100 We're in the process of that fare structure analysis now 00:36:11.100 --> 00:36:13.420 on tomorrow's conversation with the board 00:36:13.420 --> 00:36:18.420 will be more around what are the limits or boundaries 00:36:18.420 --> 00:36:21.300 of what that fare structure could be. 00:36:21.300 --> 00:36:24.460 - If I may, I don't know how tuned in 00:36:24.460 --> 00:36:25.860 you might've been to this process. 00:36:25.860 --> 00:36:28.660 I'm not quite sure when you joined the organization 00:36:28.660 --> 00:36:32.140 or whatever, but this body drafted a resolution 00:36:32.140 --> 00:36:33.660 that was then approved by council 00:36:33.660 --> 00:36:37.220 and was meant to be instruction to our representative 00:36:37.220 --> 00:36:39.220 at the time who wasn't that interested in representing us. 00:36:39.220 --> 00:36:42.660 But one of the things that was in our resolution 00:36:42.660 --> 00:36:47.020 was a request that we, that the idea 00:36:47.020 --> 00:36:50.060 of a fare free system be evaluated. 00:36:50.060 --> 00:36:51.460 So if you're evaluating fares. 00:36:51.460 --> 00:36:55.300 Now, I think at the outset, a person might say, 00:36:55.300 --> 00:36:57.620 well, that's completely crazy. 00:36:57.620 --> 00:37:01.420 But let me just say a little bit 00:37:01.420 --> 00:37:03.900 about why that's not necessarily the case. 00:37:05.380 --> 00:37:10.060 At the time, we were told that the fare contribution 00:37:10.060 --> 00:37:13.380 to total DCTA revenue is I believe less than half a percent. 00:37:13.380 --> 00:37:14.740 So essentially a rounding error. 00:37:14.740 --> 00:37:19.180 Your revenues are assured because they come from sales tax. 00:37:19.180 --> 00:37:23.060 It's nothing to do with whether you're efficient or not. 00:37:23.060 --> 00:37:24.500 The revenue comes in. 00:37:24.500 --> 00:37:25.340 - Right. 00:37:25.340 --> 00:37:29.940 - I'll offer you a little bit of a model. 00:37:29.940 --> 00:37:32.260 We've got the Thinline Festival is starting this weekend 00:37:32.260 --> 00:37:36.660 and then you've been a sponsor of it in the past and where 00:37:36.660 --> 00:37:42.980 that used to be a paper drink deal, an $8 thing. 00:37:42.980 --> 00:37:46.500 And I was on the board when the decision was made 00:37:46.500 --> 00:37:48.780 and I thought it seemed crazy at first 00:37:48.780 --> 00:37:51.140 to make it a free festival, but it's a game changer. 00:37:51.140 --> 00:37:52.140 It's just a different model. 00:37:52.140 --> 00:37:54.380 It doesn't mean you don't have revenues. 00:37:54.380 --> 00:37:58.020 It means it changes the model. 00:37:58.020 --> 00:38:00.660 Now in that case, the model is greater advertising revenue 00:38:00.660 --> 00:38:02.020 because more people will come to something 00:38:02.020 --> 00:38:03.060 that are free. 00:38:03.060 --> 00:38:08.060 For public transit, it takes away the friction 00:38:08.060 --> 00:38:11.860 so that instead of just providing service carefully 00:38:11.860 --> 00:38:15.860 to the small number of people who are dependent on transit, 00:38:15.860 --> 00:38:17.900 it takes away the psychological barrier. 00:38:17.900 --> 00:38:20.860 Free is a very powerful thing so that even people 00:38:20.860 --> 00:38:23.820 like the people in this room might go, 00:38:23.820 --> 00:38:24.700 I know I can get on. 00:38:24.700 --> 00:38:25.540 There's no friction. 00:38:25.540 --> 00:38:28.020 I don't have to know how it works. 00:38:28.020 --> 00:38:30.380 You know, it's something I can do. 00:38:31.700 --> 00:38:36.540 So that's why I think it's at least worth thinking about 00:38:36.540 --> 00:38:39.940 how would you configure the product 00:38:39.940 --> 00:38:45.100 to mitigate against whatever risks you think come with free. 00:38:45.100 --> 00:38:47.940 Like you have to get out at the end of a ride. 00:38:47.940 --> 00:38:49.620 Maybe there's a definition of what a ride is. 00:38:49.620 --> 00:38:50.860 It's unidirectional. 00:38:50.860 --> 00:38:56.420 But if you wanna meet the real goal of public transit 00:38:56.420 --> 00:38:59.260 of taking cars off the road and improving air quality, 00:38:59.260 --> 00:39:02.180 and really having transit be part of our, 00:39:02.180 --> 00:39:05.260 you know, much bigger part of how our community works, 00:39:05.260 --> 00:39:07.980 could that be evaluated? 00:39:07.980 --> 00:39:11.260 It's a long way to get to the end of that question. 00:39:11.260 --> 00:39:14.580 - I'm gonna jump in as your representative 00:39:14.580 --> 00:39:16.540 on the DCTA board. 00:39:16.540 --> 00:39:19.540 I'm well aware of that resolution, which I hope to draft. 00:39:19.540 --> 00:39:22.780 And this is something that I insisted on 00:39:22.780 --> 00:39:26.900 at our last board meeting that as one of the options 00:39:26.900 --> 00:39:31.580 that we consider when we discuss fare pricing options, 00:39:31.580 --> 00:39:34.700 I wanna see an analysis of eliminating fares, 00:39:34.700 --> 00:39:37.660 but I'll let Paul elaborate on that. 00:39:37.660 --> 00:39:40.460 - Wait, one more little, oh sorry, sorry, please go ahead. 00:39:40.460 --> 00:39:45.460 - And besides, people that make a lot of money 00:39:45.460 --> 00:39:48.780 and have a lot of money, that can afford a lot of things, 00:39:48.780 --> 00:39:50.540 they like free. 00:39:50.540 --> 00:39:54.100 So, and they probably appreciate free 00:39:54.100 --> 00:39:57.060 more than someone that doesn't have as much. 00:39:57.060 --> 00:40:00.220 So, if we're talking about taking cars off the road 00:40:00.220 --> 00:40:05.220 and having them to come to the city for nice free things, 00:40:05.220 --> 00:40:10.500 you know, this additional opportunity to do that 00:40:10.500 --> 00:40:15.500 and satisfy all of that, that's why I voted for it, yes. 00:40:15.500 --> 00:40:16.540 Thank you. 00:40:16.540 --> 00:40:20.180 - Just one little, before you respond to this onslaught 00:40:20.180 --> 00:40:22.860 of demand for free things, 00:40:24.620 --> 00:40:29.620 is there funding that comes to DCTA, 00:40:29.620 --> 00:40:31.780 federal sources I'm imagining, 00:40:31.780 --> 00:40:34.100 that's attached to ridership? 00:40:34.100 --> 00:40:36.300 That's a genuine question, I don't know the answer, 00:40:36.300 --> 00:40:40.140 but is there a funding benefit to increasing ridership? 00:40:40.140 --> 00:40:43.900 - I'm not prepared to speak on those details here today, 00:40:43.900 --> 00:40:47.380 but certainly as we get ready for our conversation tomorrow, 00:40:47.380 --> 00:40:50.540 we can talk about those sorts of things 00:40:50.540 --> 00:40:51.740 and we can come back to this forum 00:40:51.740 --> 00:40:52.940 with more details on that. 00:40:52.940 --> 00:40:56.900 Obviously, the mission of DCTA is to enhance ridership, 00:40:56.900 --> 00:40:58.220 that's the reason that we're here. 00:40:58.220 --> 00:41:01.580 We want as many people to use public transit as possible 00:41:01.580 --> 00:41:03.940 for all the good reasons that you just laid out. 00:41:03.940 --> 00:41:06.940 And so, if that's an interest of this body, 00:41:06.940 --> 00:41:11.020 then we can talk more about that in our board meetings 00:41:11.020 --> 00:41:11.900 and then here as well. 00:41:11.900 --> 00:41:14.060 - Well, I hope, you know, if there is a funding angle 00:41:14.060 --> 00:41:16.660 that can, you know, help in the analysis. 00:41:16.660 --> 00:41:18.060 - Yes, understood. 00:41:18.060 --> 00:41:19.500 - Okay, thanks for that. 00:41:19.500 --> 00:41:22.340 - So obviously, FTA wants to see ridership increase 00:41:22.340 --> 00:41:24.420 across transportation agencies also. 00:41:24.420 --> 00:41:25.660 - There you go. 00:41:25.660 --> 00:41:27.460 - I think that's the answer. 00:41:27.460 --> 00:41:29.820 Okay, so to answer the question about, 00:41:29.820 --> 00:41:32.540 is free going to be considered in the process? 00:41:32.540 --> 00:41:34.540 The answer is yes. 00:41:34.540 --> 00:41:38.140 We heard that feedback from our board in our last meeting 00:41:38.140 --> 00:41:40.580 that we would need to evaluate 00:41:40.580 --> 00:41:44.940 or they would like us to evaluate a no fare option 00:41:44.940 --> 00:41:47.300 or a no fare alternative on the Connect service. 00:41:47.300 --> 00:41:49.660 And so, we will be talking about that 00:41:49.660 --> 00:41:51.100 here in the next few months 00:41:51.100 --> 00:41:54.180 as we lay out this comprehensive operations analysis. 00:41:54.180 --> 00:41:56.460 We've started with the GoZone fare pricing 00:41:56.460 --> 00:41:58.260 and then next month, we'll be bringing, 00:41:58.260 --> 00:42:00.500 layering in GoZone and fixed route 00:42:00.500 --> 00:42:02.660 and that's where you'll begin to hear about 00:42:02.660 --> 00:42:04.580 no fare alternatives on Connect. 00:42:04.580 --> 00:42:10.060 - To clarify, I meant fixed routes broadly, 00:42:10.060 --> 00:42:11.140 including the A train. 00:42:11.140 --> 00:42:12.500 - Okay, very good. 00:42:12.500 --> 00:42:19.860 - You know, if I can strain your patience a little. 00:42:21.340 --> 00:42:23.940 Is there a conceptual reason 00:42:23.940 --> 00:42:27.660 in maybe how the compensation works, the contract works, 00:42:27.660 --> 00:42:30.620 why the same logic wouldn't apply to GoZone? 00:42:30.620 --> 00:42:34.660 Why would you say we'll look at fare-free for Connect, 00:42:34.660 --> 00:42:35.820 but not for GoZone? 00:42:35.820 --> 00:42:39.180 - I expect that could come out in our conversation 00:42:39.180 --> 00:42:43.260 with the board tomorrow about that idea. 00:42:43.260 --> 00:42:45.420 I don't know that we've gotten very far into that idea 00:42:45.420 --> 00:42:47.220 with our board up to this point. 00:42:47.220 --> 00:42:50.820 And so, it's definitely a good conversation 00:42:50.820 --> 00:42:52.620 for us to have as we go through this process. 00:42:52.620 --> 00:42:55.420 So, we'd like to maybe layer that 00:42:55.420 --> 00:42:57.460 into our conversation tomorrow. 00:42:57.460 --> 00:43:00.180 - Thanks for letting us keep you at slide six 00:43:00.180 --> 00:43:02.140 for 10 minutes. 00:43:02.140 --> 00:43:04.700 - There's only a couple more, so we're doing great. 00:43:04.700 --> 00:43:08.820 So, this is just a snapshot of, 00:43:08.820 --> 00:43:11.500 when we talk about potential pricing structures, 00:43:11.500 --> 00:43:14.140 the concept is that there are, 00:43:14.140 --> 00:43:18.100 and again, conceptual discussion only, 00:43:18.100 --> 00:43:22.020 there are fixed pricing models 00:43:22.020 --> 00:43:24.660 that no matter how far you go, this is what the fare is. 00:43:24.660 --> 00:43:26.860 There are variable cost models 00:43:26.860 --> 00:43:28.500 that kind of like an Uber that says, 00:43:28.500 --> 00:43:30.060 when you go this far, it's this much money. 00:43:30.060 --> 00:43:31.860 If you go a little bit farther, it's this much money. 00:43:31.860 --> 00:43:34.540 And then there's a hybrid fare sort of model 00:43:34.540 --> 00:43:37.100 that says the first several miles, 00:43:37.100 --> 00:43:39.820 whatever that might be, are a fixed cost, 00:43:39.820 --> 00:43:41.940 and then beyond that is a variable cost. 00:43:41.940 --> 00:43:43.940 And that's really what we're talking about 00:43:43.940 --> 00:43:46.540 when we talk about the idea of trying to entice riders 00:43:46.540 --> 00:43:48.580 to use fixed routes when it's possible, 00:43:48.580 --> 00:43:49.940 if that's the most efficient way for them 00:43:49.940 --> 00:43:50.980 to make their trip. 00:43:50.980 --> 00:43:56.900 And so here's a snapshot of the multimodal app 00:43:56.900 --> 00:43:59.420 that's being developed right now. 00:43:59.420 --> 00:44:01.380 It would be like you see there, 00:44:01.380 --> 00:44:03.180 a place where proposals of different, 00:44:03.180 --> 00:44:06.980 multiple legs of a single journey can be evaluated, 00:44:06.980 --> 00:44:08.700 and then the rider get to decide 00:44:08.700 --> 00:44:10.700 what is the best route for them. 00:44:10.700 --> 00:44:13.180 And again, we'll go into more conversation on this 00:44:13.180 --> 00:44:14.500 in our board meeting tomorrow, 00:44:14.500 --> 00:44:17.420 otherwise we'll have the folks from VIA on hand with us 00:44:17.420 --> 00:44:19.700 to talk through that. 00:44:19.700 --> 00:44:21.460 - I'm embarrassed that I don't already know this, 00:44:21.460 --> 00:44:24.140 but are we talking about an update 00:44:24.140 --> 00:44:25.220 to the current GoZone app 00:44:25.220 --> 00:44:27.260 or a new app that's being designed? 00:44:27.260 --> 00:44:29.540 - It's an evolution of the current app. 00:44:29.540 --> 00:44:31.020 - Okay, thank you. 00:44:31.020 --> 00:44:35.140 - Yeah, I would just, I'm not to be too repetitive, 00:44:35.140 --> 00:44:39.700 but do you use Google Maps or anything like that for yourself? 00:44:39.700 --> 00:44:41.620 - Yes, sir, I do use Waze, Google Maps. 00:44:41.620 --> 00:44:44.380 - So, I mean, you don't need a price incentive 00:44:44.380 --> 00:44:46.700 to figure out that you want to do the thing 00:44:46.700 --> 00:44:47.740 that's most efficient for you. 00:44:47.740 --> 00:44:49.020 - Correct. - Yeah, okay. 00:44:49.020 --> 00:44:53.620 - Okay, if no other questions, 00:44:53.620 --> 00:44:55.500 I'm happy to turn it over to Brittany 00:44:55.500 --> 00:44:58.020 to talk about the modifications from March. 00:44:58.020 --> 00:45:01.700 Thank you very much, it's very good to meet you, 00:45:01.700 --> 00:45:02.740 look forward to working with you. 00:45:02.740 --> 00:45:04.540 - Of course, thank you. 00:45:04.540 --> 00:45:09.060 - You'll notice I let Paul take the hard stuff, so. 00:45:10.020 --> 00:45:13.380 The kid, so I'm here to go over the changes 00:45:13.380 --> 00:45:15.260 that went into effect with the March service change 00:45:15.260 --> 00:45:17.500 that was instituted on March 14th. 00:45:17.500 --> 00:45:19.580 I know Mr. Suarez was here earlier this year 00:45:19.580 --> 00:45:22.620 to present these changes that were proposed 00:45:22.620 --> 00:45:25.300 and approved at the December 2nd board meeting. 00:45:25.300 --> 00:45:26.980 I'll start by giving you an overlay 00:45:26.980 --> 00:45:30.220 with the blue being what the new routes look like, 00:45:30.220 --> 00:45:34.540 overlaid with the gray that was the previous service. 00:45:34.540 --> 00:45:36.020 And then I want to show you this next slide 00:45:36.020 --> 00:45:38.540 that also lays in the UNT shuttles. 00:45:38.540 --> 00:45:41.380 So you can see even though some of the service 00:45:41.380 --> 00:45:44.620 was appeared to be cut in the southern portion 00:45:44.620 --> 00:45:47.100 that is covered by and large by the UNT shuttles, 00:45:47.100 --> 00:45:48.900 which are also open to the public 00:45:48.900 --> 00:45:52.620 and an opportunity for them to ride fixed route as well. 00:45:52.620 --> 00:45:54.900 Before I start going into the individual changes, 00:45:54.900 --> 00:45:57.340 there's just a couple of points that I want to make 00:45:57.340 --> 00:45:59.860 as far as trends that you'll see 00:45:59.860 --> 00:46:02.740 with the changes that we've made to the fixed route. 00:46:02.740 --> 00:46:04.940 I know Mr. Suarez has talked to you before 00:46:04.940 --> 00:46:07.140 about the importance of both frequency 00:46:07.140 --> 00:46:09.980 and on-time performance in building ridership. 00:46:09.980 --> 00:46:12.180 People won't take the bus if it doesn't show up often 00:46:12.180 --> 00:46:14.180 and if it doesn't show up on time. 00:46:14.180 --> 00:46:17.140 So all of the changes that were put in 00:46:17.140 --> 00:46:20.500 to the March service changes were done with this in mind. 00:46:20.500 --> 00:46:23.460 How do we take our resources and maximize them 00:46:23.460 --> 00:46:24.860 on the segments of ridership 00:46:24.860 --> 00:46:27.020 that have the highest level of ridership 00:46:27.020 --> 00:46:29.220 so we can get the bus there more often 00:46:29.220 --> 00:46:32.060 and we can get the bus there more on time? 00:46:32.060 --> 00:46:34.780 Another point that I want to make is that these changes 00:46:34.780 --> 00:46:38.580 were meant to be temporary as we work through the process 00:46:38.580 --> 00:46:40.940 that Mr. Christina just went over. 00:46:40.940 --> 00:46:43.660 As we look at GOZONE and the A-Train 00:46:43.660 --> 00:46:45.580 and the Connect service and the shuttles 00:46:45.580 --> 00:46:46.900 all working together to create 00:46:46.900 --> 00:46:49.580 a more integrated multimodal system. 00:46:49.580 --> 00:46:52.620 So these will be on all likelihood changing 00:46:52.620 --> 00:46:54.340 with whatever the final service plan 00:46:54.340 --> 00:46:56.520 the board approves later this summer. 00:46:56.520 --> 00:46:59.260 - Pardon me. - Yes, sir. 00:46:59.260 --> 00:47:01.460 - Just so I understand, they're temporary 00:47:01.460 --> 00:47:04.100 in order to meet what temporary objective, 00:47:04.100 --> 00:47:05.620 what are you solving for? 00:47:05.620 --> 00:47:07.580 - Well, three things really. 00:47:07.580 --> 00:47:11.540 Increasing on time performance, increasing frequency 00:47:11.540 --> 00:47:14.260 and then also working within the confines 00:47:14.260 --> 00:47:17.460 of the operational shortages that we have right now. 00:47:17.460 --> 00:47:19.020 Like DART, like Trinity Metro. 00:47:19.020 --> 00:47:20.620 Yeah, yeah, that's exactly right. 00:47:20.620 --> 00:47:22.220 Like many, like the school districts, 00:47:22.220 --> 00:47:24.260 like many across the country, 00:47:24.260 --> 00:47:26.100 we are seeing a shortage in operators. 00:47:26.100 --> 00:47:28.040 And so not being able to make those runs, 00:47:28.040 --> 00:47:30.500 not being able to put out reliable service 00:47:30.500 --> 00:47:32.060 is one of the driving factors 00:47:32.060 --> 00:47:34.340 for modifying these services 00:47:34.340 --> 00:47:36.820 to be able to ensure that we're meeting the demands 00:47:36.820 --> 00:47:38.500 of the highest ridership portions 00:47:38.500 --> 00:47:40.460 and we're getting those buses there on time 00:47:40.460 --> 00:47:41.700 and as frequently as possible. 00:47:41.700 --> 00:47:45.380 - So if circumstances change or the offering changed 00:47:45.380 --> 00:47:47.620 and you're able to recruit, you know, 00:47:47.620 --> 00:47:50.980 if there's a shift and you're able to recruit more operators, 00:47:50.980 --> 00:47:53.380 is the thought that you might, you know, 00:47:53.380 --> 00:47:54.820 re-flesh out the roots? 00:47:54.820 --> 00:47:56.100 - That's certainly a consideration 00:47:56.100 --> 00:47:57.300 I think the board would look into 00:47:57.300 --> 00:48:00.100 when making those service decisions later this summer. 00:48:00.100 --> 00:48:02.300 And this is a plug, if anyone knows any operators, 00:48:02.300 --> 00:48:05.140 please send them to ride dcta.net, so. 00:48:05.140 --> 00:48:09.500 - Do we pay as much as the alternate services 00:48:09.500 --> 00:48:11.700 that an operator might work for? 00:48:11.700 --> 00:48:13.620 - You know, sir, I don't know the answer to that question. 00:48:13.620 --> 00:48:15.300 I can certainly get with our HR department 00:48:15.300 --> 00:48:17.220 and find out where our starting pay measures 00:48:17.220 --> 00:48:20.980 with both public providers as well as private providers, 00:48:20.980 --> 00:48:24.020 which is really one of the industries 00:48:24.020 --> 00:48:26.420 that is siphoning off as more and more of us 00:48:26.420 --> 00:48:27.820 order from Amazon Prime 00:48:27.820 --> 00:48:30.460 and we expect those boxes to be there the next day. 00:48:30.460 --> 00:48:31.620 Those are the kinds of service, 00:48:31.620 --> 00:48:34.540 the CDLs that we're competing with, so. 00:48:34.540 --> 00:48:35.860 But I can certainly look into that 00:48:35.860 --> 00:48:37.420 and we will be prepared to speak to that 00:48:37.420 --> 00:48:39.580 at our next presentation at this committee. 00:48:39.580 --> 00:48:45.580 So with that, this is the new Connect route. 00:48:45.580 --> 00:48:47.860 You'll remember at the end of December, 00:48:47.860 --> 00:48:49.820 Denton Connect route one was suspended 00:48:49.820 --> 00:48:53.300 along with the two routes in Lewisville 21 and 22. 00:48:53.300 --> 00:48:56.060 Another consistent theme across the scheduling 00:48:56.060 --> 00:48:58.460 is that the routes tend to start a little bit later 00:48:58.460 --> 00:49:00.220 and end a little bit sooner. 00:49:00.220 --> 00:49:02.820 And that's capturing the changing shift 00:49:02.820 --> 00:49:04.660 in ridership patterns that we're seeing 00:49:04.660 --> 00:49:06.940 as a result of COVID-19. 00:49:06.940 --> 00:49:10.100 As more folks work from home or have a hybrid schedule, 00:49:10.100 --> 00:49:12.580 they're not having those normal rush hour periods. 00:49:12.580 --> 00:49:15.860 We're actually seeing more travel throughout the midday 00:49:15.860 --> 00:49:17.900 as folks utilize the fixed route, 00:49:17.900 --> 00:49:19.340 the GO zone and the A train 00:49:19.340 --> 00:49:21.860 to accomplish more midday tasks. 00:49:21.860 --> 00:49:25.180 So we've shifted our schedule to accommodate that. 00:49:27.060 --> 00:49:29.940 Oh, it went backwards. 00:49:29.940 --> 00:49:32.180 My millennial skills are failing me. 00:49:32.180 --> 00:49:37.860 So here's the revisions to Denton Connect route two. 00:49:37.860 --> 00:49:39.260 By shortening this route 00:49:39.260 --> 00:49:41.380 and taking out the loop component of it, 00:49:41.380 --> 00:49:44.260 we've been able to increase the frequency of the bus 00:49:44.260 --> 00:49:47.940 from running once every 60 minutes to once every 42 minutes. 00:49:47.940 --> 00:49:49.900 So an 18 minute improvement. 00:49:49.900 --> 00:49:52.940 That's also allowed us to increase the number of routes 00:49:52.940 --> 00:49:54.300 that we can run during the day 00:49:54.300 --> 00:49:56.340 from 13 round trips to 15. 00:49:56.340 --> 00:49:59.780 I'm gonna go through these kind of quickly 00:49:59.780 --> 00:50:00.740 since they've already been presented. 00:50:00.740 --> 00:50:03.060 But if you have any questions, please stop me. 00:50:03.060 --> 00:50:06.660 So this is route three. 00:50:06.660 --> 00:50:09.340 This one we've been able to improve the frequency on that 00:50:09.340 --> 00:50:11.500 from every 46 to 51 minutes, 00:50:11.500 --> 00:50:13.100 depending on the time of day 00:50:13.100 --> 00:50:16.580 to consistently running it every 40 minutes. 00:50:16.580 --> 00:50:19.260 This has been able to increase the number of round trips 00:50:19.260 --> 00:50:21.340 from 14 to 17. 00:50:21.340 --> 00:50:25.940 And we've also made some modifications to now serve stops 00:50:25.940 --> 00:50:28.340 at both Serve Denton and Denton County Health. 00:50:28.340 --> 00:50:35.100 So route four was trimmed down 00:50:35.100 --> 00:50:37.220 and now has an improved frequency 00:50:37.220 --> 00:50:40.500 from every 56 minutes to every 40 minutes. 00:50:40.500 --> 00:50:43.180 And to make up for that cutoff portion there, 00:50:43.180 --> 00:50:48.180 we've also put in a new Denton Connect route five. 00:50:48.180 --> 00:50:50.060 This is a new circular route 00:50:50.060 --> 00:50:52.980 and it has a frequency of every 30 minutes 00:50:52.980 --> 00:50:55.060 and makes 22 round trips every day. 00:50:55.060 --> 00:51:02.100 Route six, we've increased the frequency 00:51:02.100 --> 00:51:04.860 from 50 minutes to 33 minutes. 00:51:04.860 --> 00:51:07.060 So significant improvements on the frequency there. 00:51:07.060 --> 00:51:10.460 And that has allowed us to run this route round trip 00:51:10.460 --> 00:51:13.580 from 13 trips a day up now to 20 routes a day. 00:51:13.580 --> 00:51:18.980 And then finally revised route seven. 00:51:18.980 --> 00:51:22.420 This one has a variable time depending on peak period. 00:51:22.420 --> 00:51:25.980 So it was running every 30 minutes to every 68 minutes, 00:51:25.980 --> 00:51:28.060 depending on the time of day. 00:51:28.060 --> 00:51:29.980 Now it runs every 27 minutes 00:51:29.980 --> 00:51:31.420 and then the last shift of the day 00:51:31.420 --> 00:51:33.020 between seven and eight o'clock, 00:51:33.020 --> 00:51:34.420 it runs at an hour frequency. 00:51:34.420 --> 00:51:36.700 So significant frequency improvements 00:51:36.700 --> 00:51:39.540 during that midday and early peak period. 00:51:39.540 --> 00:51:42.060 We've also been able to increase the number of round trips 00:51:42.060 --> 00:51:44.700 on this route from 22 a day to 24 a day. 00:51:44.700 --> 00:51:46.540 Yes, ma'am. 00:51:48.980 --> 00:51:51.220 (mumbling) 00:51:51.220 --> 00:51:54.420 Okay. 00:51:54.420 --> 00:52:00.260 - I apologize if this sounds really just 00:52:00.260 --> 00:52:03.300 kindergarten level question. 00:52:03.300 --> 00:52:06.060 For a route like this and for the amount of time 00:52:06.060 --> 00:52:09.180 that you're saying that it's gonna take to get that route, 00:52:09.180 --> 00:52:11.020 are there, how many vehicles are on the, 00:52:11.020 --> 00:52:12.100 that's handling this route? 00:52:12.100 --> 00:52:15.060 Is this one vehicle that's just going around and around? 00:52:15.060 --> 00:52:16.580 Are there a couple of vehicles? 00:52:16.580 --> 00:52:18.660 - I'm not sure how many vehicles are dedicated 00:52:18.660 --> 00:52:20.740 to each route, but I can certainly take that back 00:52:20.740 --> 00:52:23.180 and I can figure that out from our operations folks 00:52:23.180 --> 00:52:25.020 and get back to you how many vehicles we run 00:52:25.020 --> 00:52:26.300 on each route each day. 00:52:26.300 --> 00:52:29.380 - 'Cause I'm just hearing varying times, 00:52:29.380 --> 00:52:32.860 take 18 minutes or 30 minutes to go this route. 00:52:32.860 --> 00:52:36.380 That's, it just sounds almost kind of impossible 00:52:36.380 --> 00:52:41.380 for one vehicle to do all of that, so I appreciate that. 00:52:41.380 --> 00:52:42.900 - Yeah, I'll look into it. 00:52:42.900 --> 00:52:44.660 Depending on the route, it may have different vehicles 00:52:44.660 --> 00:52:46.980 on different routes, but that's a very good question. 00:52:46.980 --> 00:52:48.340 I'll find out and we'll definitely get back 00:52:48.340 --> 00:52:52.020 to your office, yeah, I agree. 00:52:52.020 --> 00:52:53.220 - Do you have an office? 00:52:53.220 --> 00:52:54.580 - I do, I have an office. 00:52:54.580 --> 00:52:56.100 (laughs) 00:52:56.100 --> 00:52:58.980 - Or carrier pigeon, whatever motive, whatever, yeah. 00:52:58.980 --> 00:53:00.100 I'll get the same. 00:53:00.100 --> 00:53:04.460 And so now, oh, yes sir. 00:53:04.460 --> 00:53:05.740 - Yeah, before we get off this topic. 00:53:05.740 --> 00:53:06.580 - Sure. 00:53:06.580 --> 00:53:09.700 - So how were these changes communicated 00:53:09.700 --> 00:53:12.700 to the drivers and to the general public? 00:53:12.700 --> 00:53:14.540 - So we have a variety of methods that we use 00:53:14.540 --> 00:53:17.260 to communicate to the general public. 00:53:17.260 --> 00:53:21.500 We did a lot of stuff on our website, social media, 00:53:21.500 --> 00:53:24.020 but we also use traditional methods of public involvement, 00:53:24.020 --> 00:53:26.860 so putting it in the newspaper. 00:53:26.860 --> 00:53:31.540 We've also ordered bags that we have a QR code on them 00:53:31.540 --> 00:53:33.660 that we put on the stops that were closed 00:53:33.660 --> 00:53:35.340 that folks could take, that would take them 00:53:35.340 --> 00:53:37.940 to the trip planner so they would understand. 00:53:37.940 --> 00:53:39.900 But our marketing and communications department 00:53:39.900 --> 00:53:42.620 utilized all of the resources available to us 00:53:42.620 --> 00:53:44.620 to make sure that, most importantly, 00:53:44.620 --> 00:53:47.220 our traveling public knows of these changes. 00:53:47.220 --> 00:53:49.980 And then the changes to the routes communicated 00:53:49.980 --> 00:53:52.980 to the operators were done through our partners at NTMC 00:53:52.980 --> 00:53:55.060 and the close communication that we have 00:53:55.060 --> 00:53:59.380 working with the HTG and NTMC entities. 00:53:59.380 --> 00:54:01.540 - This is sort of anecdotal, 00:54:01.540 --> 00:54:03.740 but from speaking with operators, 00:54:03.740 --> 00:54:06.220 the version that was filtered to me was, 00:54:06.220 --> 00:54:09.860 no idea what's coming, show up one day, 00:54:09.860 --> 00:54:11.700 get the new lefts and rights. 00:54:11.700 --> 00:54:14.700 It sounds like kind of skimpy to me. 00:54:16.340 --> 00:54:18.060 I understand there's an intermediary, 00:54:18.060 --> 00:54:21.180 but I think ultimately we're still responsible 00:54:21.180 --> 00:54:22.860 for quality control. 00:54:22.860 --> 00:54:24.540 I'm just sharing that back to you. 00:54:24.540 --> 00:54:26.220 - Absolutely, and we'll take that feedback back 00:54:26.220 --> 00:54:28.380 and make sure that we do a better job 00:54:28.380 --> 00:54:31.100 of conveying any kind of upcoming changes 00:54:31.100 --> 00:54:33.620 through our channels as well as through NTMC's channels 00:54:33.620 --> 00:54:34.980 with any future changes we have, 00:54:34.980 --> 00:54:36.380 and appreciate that feedback. 00:54:36.380 --> 00:54:40.180 Any other questions on the March service change 00:54:40.180 --> 00:54:42.980 before I move into the fund that was February? 00:54:42.980 --> 00:54:47.980 - I just wanted to address, we were talking about pay, 00:54:47.980 --> 00:54:50.700 and I wanna make sure that David hears that 00:54:50.700 --> 00:54:53.100 as our new representative on the NTMC board. 00:54:53.100 --> 00:54:59.380 Trinity Metro has job postings for brand new trainee 00:54:59.380 --> 00:55:06.900 who does not have a CDL starts at $17 an hour. 00:55:06.900 --> 00:55:11.260 With a CDL, they start at $20 an hour 00:55:11.260 --> 00:55:13.220 and go up to $25 an hour. 00:55:13.220 --> 00:55:18.220 Dart is starting folks with a CDL at $21.13 an hour. 00:55:18.220 --> 00:55:25.700 And NTMC is starting folks, it looks like with a CDL, 00:55:25.700 --> 00:55:32.540 at $14 to $17 an hour. 00:55:32.540 --> 00:55:33.460 - How does that compare? 00:55:33.460 --> 00:55:36.900 - So there's, yeah, somebody who has a CDL 00:55:36.900 --> 00:55:39.420 would have an obvious choice to make. 00:55:39.420 --> 00:55:42.100 So I think if we're gonna address those staffing shortages 00:55:42.100 --> 00:55:45.340 at NTMC, we might need to address that. 00:55:45.340 --> 00:55:47.620 - So if we're serious about having a robust system, 00:55:47.620 --> 00:55:48.980 you need to have operators. 00:55:48.980 --> 00:55:50.300 If you're serious about having operators, 00:55:50.300 --> 00:55:52.500 you've got to offer competitive wages. 00:55:52.500 --> 00:55:56.900 - We'll take that back, thank you, Council Member McGuire. 00:55:56.900 --> 00:56:02.660 So for the increment weather response and next steps, 00:56:02.660 --> 00:56:05.220 I like pictures, not bullets on the slide. 00:56:05.220 --> 00:56:09.540 So I wanna talk you through our response 00:56:09.540 --> 00:56:11.140 to the two winter storms that struck 00:56:11.140 --> 00:56:13.700 the North Texas region in the month of February, 00:56:13.700 --> 00:56:15.180 go over some of our lessons learned 00:56:15.180 --> 00:56:17.260 and then talk you through some of our next steps. 00:56:17.260 --> 00:56:18.900 I apologize, Council Member McGuire, 00:56:18.900 --> 00:56:20.100 it's gonna be almost verbatim 00:56:20.100 --> 00:56:22.460 what I provided the board earlier this month. 00:56:22.460 --> 00:56:26.900 But to begin with, I wanna put a little bit of context 00:56:26.900 --> 00:56:29.340 around how the decision are made 00:56:29.340 --> 00:56:31.660 in these kind of increment weather events. 00:56:32.500 --> 00:56:37.500 When it comes to modifying or suspending any kind of service, 00:56:37.500 --> 00:56:39.580 that's not something that we take lightly. 00:56:39.580 --> 00:56:42.020 We recognize that we are a public service agency 00:56:42.020 --> 00:56:44.420 and that we provide critical lifeline services 00:56:44.420 --> 00:56:46.380 to many of our customers. 00:56:46.380 --> 00:56:48.300 Providing transportation is always one 00:56:48.300 --> 00:56:51.300 of our guiding principles and highest missions. 00:56:51.300 --> 00:56:54.180 When increment weather strikes the North Texas region, 00:56:54.180 --> 00:56:57.340 particularly icy weather like we saw 00:56:57.340 --> 00:57:00.220 through both winter storm Landon and winter storm Oakley, 00:57:00.220 --> 00:57:02.340 safety has to be our highest priority 00:57:02.340 --> 00:57:05.100 and transit agencies across the region 00:57:05.100 --> 00:57:07.100 really have to strike a fine balance 00:57:07.100 --> 00:57:10.380 between providing those critical lifeline services 00:57:10.380 --> 00:57:13.060 and then keeping the safety of our staff, our operators, 00:57:13.060 --> 00:57:15.460 and then our traveling public top of mind. 00:57:15.460 --> 00:57:17.540 So we look at all kinds of things. 00:57:17.540 --> 00:57:20.740 We look at weather conditions, we look at road conditions, 00:57:20.740 --> 00:57:23.300 we look at what our partners across the region are doing, 00:57:23.300 --> 00:57:26.820 what decisions are being made from DART, Trinity Metro, 00:57:26.820 --> 00:57:29.580 other providers, and those are all considerations 00:57:29.580 --> 00:57:32.980 that go into making any kind of service determination, 00:57:32.980 --> 00:57:34.980 augmentation, or suspension. 00:57:34.980 --> 00:57:38.700 So we take that very, very seriously. 00:57:38.700 --> 00:57:40.540 So going into winter storm Landon, 00:57:40.540 --> 00:57:42.580 which did strike the North Texas region 00:57:42.580 --> 00:57:44.980 the first week of February, 00:57:44.980 --> 00:57:49.500 we began that Wednesday meeting regular two-hour periods 00:57:49.500 --> 00:57:51.620 to evaluate the forecast 00:57:51.620 --> 00:57:53.980 and start taking the preliminary steps needed 00:57:53.980 --> 00:57:55.860 to ensure the continuity of service 00:57:55.860 --> 00:57:57.620 when the weather did hit. 00:57:57.620 --> 00:58:00.420 Our contractors, Rio Grande Pacific, 00:58:00.420 --> 00:58:02.460 began that evening by lighting the switch heaters, 00:58:02.460 --> 00:58:04.340 which is the picture of the rail on fire, 00:58:04.340 --> 00:58:06.500 which I think is a very cool picture. 00:58:06.500 --> 00:58:08.660 Those will keep the rail switches from freezing 00:58:08.660 --> 00:58:11.500 and allow us to continue running A-train operations 00:58:11.500 --> 00:58:15.620 during prolonged periods of below freezing temperatures. 00:58:15.620 --> 00:58:17.940 We also had crews out that evening 00:58:17.940 --> 00:58:21.780 laying out biodegradable ice melt at the DCTA stations 00:58:21.780 --> 00:58:25.340 and bus stops and sidewalks and parking lots, 00:58:25.340 --> 00:58:28.340 as well as provided our operators with biodegradable 00:58:28.340 --> 00:58:31.980 ice melt on their vehicles to spot treat as necessary. 00:58:31.980 --> 00:58:33.340 That evening, we did make contact 00:58:33.340 --> 00:58:34.700 with all three of our member cities 00:58:34.700 --> 00:58:36.060 to evaluate their needs 00:58:36.060 --> 00:58:37.980 during the incoming inclement weather. 00:58:37.980 --> 00:58:39.980 We worked closely with the city of Denton 00:58:39.980 --> 00:58:42.620 on their request to provide shuttle services 00:58:42.620 --> 00:58:44.860 to the emergency warming centers 00:58:44.860 --> 00:58:46.780 and shelters at our Daily Bread 00:58:46.780 --> 00:58:48.940 and across the city of Denton. 00:58:48.940 --> 00:58:49.940 For the city of Lewisville, 00:58:49.940 --> 00:58:52.260 we provided a warming bus on standby 00:58:52.260 --> 00:58:53.540 at one of the rail stations 00:58:53.540 --> 00:58:55.820 in case they had any emergency needs 00:58:55.820 --> 00:58:57.780 for warming centers or evacuations 00:58:57.780 --> 00:59:00.260 like they experienced in February of '21. 00:59:00.260 --> 00:59:02.060 And then Highland Village politely declined 00:59:02.060 --> 00:59:03.940 any requests for assistance. 00:59:03.940 --> 00:59:06.540 So moving into Thursday, 00:59:06.540 --> 00:59:09.140 we started meeting regularly at 5 a.m. in the morning 00:59:09.140 --> 00:59:10.900 to evaluate road conditions 00:59:10.900 --> 00:59:13.580 and start making determinations on service. 00:59:13.580 --> 00:59:15.780 Our partners at VIA requested 00:59:15.780 --> 00:59:18.220 that we go ahead and suspend GoZone service. 00:59:18.220 --> 00:59:20.700 And this was done in accordance with similar decisions 00:59:20.700 --> 00:59:23.140 made by VIA-provided service at Trinity Metro 00:59:23.140 --> 00:59:25.260 in the city of Arlington. 00:59:25.260 --> 00:59:27.860 We did decide to continue running the A train 00:59:27.860 --> 00:59:29.020 and the Connect service, 00:59:29.020 --> 00:59:31.180 albeit on a Saturday schedule. 00:59:31.180 --> 00:59:32.820 And then pair transit service 00:59:32.820 --> 00:59:35.900 and the emergency shuttle services ran as normal. 00:59:35.900 --> 00:59:40.260 Moving into Friday, things really got icy. 00:59:40.260 --> 00:59:43.100 Our friends at DART went ahead and made the decision. 00:59:43.100 --> 00:59:45.020 And I worked at DART for nine years 00:59:45.020 --> 00:59:47.740 and never saw it happen to suspend all service 00:59:47.740 --> 00:59:49.820 on both the train and the buses. 00:59:49.820 --> 00:59:51.980 And with that decision, 00:59:51.980 --> 00:59:54.420 that lack of regional connectivity, 00:59:54.420 --> 00:59:56.020 we made the decision to go ahead 00:59:56.020 --> 00:59:58.900 and suspend A train operations. 00:59:58.900 --> 01:00:01.220 We planned on running a limited Connect service, 01:00:01.220 --> 01:00:04.860 but as road conditions deteriorated Friday morning, 01:00:04.860 --> 01:00:07.220 operators had a really hard time getting to work 01:00:07.220 --> 01:00:09.500 and of course, putting their safety first. 01:00:09.500 --> 01:00:11.020 We went ahead and made the decision 01:00:11.020 --> 01:00:14.980 to cancel Connect service and shift those services 01:00:14.980 --> 01:00:17.540 onto providing those critical lifeline services. 01:00:17.540 --> 01:00:19.740 So those operators were deployed 01:00:19.740 --> 01:00:21.540 on the emergency shuttle services 01:00:21.540 --> 01:00:22.980 for the city of Denton 01:00:22.980 --> 01:00:26.140 and then primarily on our paratransit services. 01:00:26.140 --> 01:00:28.060 And on that Friday, 01:00:28.060 --> 01:00:30.700 which was arguably the iciest, most dangerous day, 01:00:30.700 --> 01:00:32.700 the day that DART shut down, 01:00:32.700 --> 01:00:35.500 our operators took nearly two dozen people 01:00:35.500 --> 01:00:37.700 to their dialysis appointments. 01:00:37.700 --> 01:00:39.500 And I know that two dozen people 01:00:39.500 --> 01:00:41.380 for some of the larger agencies 01:00:41.380 --> 01:00:43.180 doesn't sound like a whole lot, 01:00:43.180 --> 01:00:44.780 but to me, that's 22 people 01:00:44.780 --> 01:00:46.180 that could have potentially suffered 01:00:46.180 --> 01:00:49.540 life-threatening ramifications had we not got there. 01:00:49.540 --> 01:00:51.420 And it's a point of pride for me 01:00:51.420 --> 01:00:53.260 that we got those 22 people there 01:00:53.260 --> 01:00:56.540 and I am so proud of our operators and our staff 01:00:56.540 --> 01:00:58.780 for getting those 22 people where they needed to go. 01:00:58.780 --> 01:01:00.940 That's why we get up and come to work every day, 01:01:00.940 --> 01:01:02.460 is to make sure those 22 people 01:01:02.460 --> 01:01:03.900 have the services they need. 01:01:03.900 --> 01:01:07.780 So the shuttles, the UNT shuttles were suspended 01:01:07.780 --> 01:01:09.820 'cause campus was of course closed. 01:01:09.820 --> 01:01:13.740 Via the GoZone service also did not run on Friday. 01:01:13.740 --> 01:01:14.820 Moving into Saturday, 01:01:14.820 --> 01:01:17.500 we had a little bit of break from the ice. 01:01:17.500 --> 01:01:19.660 It was still a hard freeze in the morning, 01:01:19.660 --> 01:01:21.620 which made getting operators to work 01:01:21.620 --> 01:01:23.580 to mark up a little bit difficult. 01:01:23.580 --> 01:01:26.580 But this was GoZone's ability to really step up and shine 01:01:26.580 --> 01:01:28.700 and demonstrate their flexibility. 01:01:28.700 --> 01:01:30.340 As the roads began to thaw, 01:01:30.340 --> 01:01:32.900 as the temperatures did increase throughout the day, 01:01:32.900 --> 01:01:35.020 we were able to launch the GoZone service 01:01:35.020 --> 01:01:37.860 beginning at noon and running until seven o'clock 01:01:37.860 --> 01:01:39.900 when the roads started to refreeze. 01:01:39.900 --> 01:01:42.380 And in that time, we completed nearly 1,100 trips 01:01:42.380 --> 01:01:44.420 on the GoZone service. 01:01:44.420 --> 01:01:45.820 By Sunday, we were back to normal, 01:01:45.820 --> 01:01:47.780 all modes operating regularly 01:01:47.780 --> 01:01:49.820 and we all took a big sigh of relief, 01:01:49.820 --> 01:01:51.340 which lasted for about two weeks 01:01:51.340 --> 01:01:53.380 until winter storm Oakley showed up. 01:01:53.380 --> 01:01:57.020 When that storm struck at the end of February, 01:01:57.020 --> 01:02:00.900 very similar protocols began meeting every two hours, 01:02:00.900 --> 01:02:02.140 reached out to the cities, 01:02:02.140 --> 01:02:04.100 again, got the request from the city of Denton 01:02:04.100 --> 01:02:06.740 to provide the emergency shuttle and warming center, 01:02:06.740 --> 01:02:09.620 which we were able to accommodate. 01:02:09.620 --> 01:02:12.660 As the ice began to fall that Wednesday afternoon, 01:02:12.660 --> 01:02:15.820 UNT made the decision to cancel classes early, 01:02:15.820 --> 01:02:18.660 so we went ahead and suspended the UNT shuttles. 01:02:18.660 --> 01:02:20.740 And then as the roads really started to slick 01:02:20.740 --> 01:02:22.420 as the sun went down, 01:02:22.420 --> 01:02:25.700 we went ahead and suspended the GoZone service at 5 p.m. 01:02:25.700 --> 01:02:27.260 But the A-Train and the Connect service 01:02:27.260 --> 01:02:31.700 did finish their regularly scheduled routes for that day. 01:02:31.700 --> 01:02:33.620 Moving into Thursday, 01:02:33.620 --> 01:02:36.140 we also had the request from VIA 01:02:36.140 --> 01:02:37.580 to suspend the GoZone service, 01:02:37.580 --> 01:02:39.700 again, in conjunction with similar decisions 01:02:39.700 --> 01:02:42.700 that were made at Trinity Metro in the city of Arlington. 01:02:42.700 --> 01:02:47.300 We had planned that Thursday to run a regular Connect service, 01:02:47.300 --> 01:02:49.380 albeit started a little bit later at 10 a.m. 01:02:49.380 --> 01:02:52.260 to give the roads an opportunity to freeze, 01:02:52.260 --> 01:02:54.380 which they did not unfreeze. 01:02:54.380 --> 01:02:57.260 And so we did have an operator shortage 01:02:57.260 --> 01:02:59.180 and once again made that determination 01:02:59.180 --> 01:03:01.820 that those resources would be better shifted 01:03:01.820 --> 01:03:03.700 onto providing those emergency services, 01:03:03.700 --> 01:03:05.340 those lifeline services. 01:03:05.340 --> 01:03:08.380 And then we did continue Route 7, 01:03:08.380 --> 01:03:10.900 which was still showing some ridership as well. 01:03:10.900 --> 01:03:14.220 The A-Train operations also continued that day. 01:03:14.220 --> 01:03:16.940 By Friday, luckily, this was not as long in duration 01:03:16.940 --> 01:03:18.620 as Winter Storm Land, and so by Friday, 01:03:18.620 --> 01:03:20.780 we were back to normal and everything was running 01:03:20.780 --> 01:03:22.220 as per usual. 01:03:22.220 --> 01:03:23.860 And we tried to do our best, 01:03:23.860 --> 01:03:25.540 and I think we were very successful 01:03:25.540 --> 01:03:27.940 in communicating these changes frequently 01:03:27.940 --> 01:03:30.900 to the board member, again, I apologize for all the emails, 01:03:30.900 --> 01:03:33.660 the traveling public, and then to the cities as well. 01:03:33.660 --> 01:03:36.580 So as we're moving into March now, 01:03:36.580 --> 01:03:37.820 and as we've already seen this week, 01:03:37.820 --> 01:03:40.660 hopefully we're moving out of winter weather season 01:03:40.660 --> 01:03:43.220 and straight into tornado season. 01:03:43.220 --> 01:03:46.540 So, but we're not waiting until next winter 01:03:46.540 --> 01:03:48.620 to already start dissecting what we've done 01:03:48.620 --> 01:03:50.660 with our winter weather response. 01:03:50.660 --> 01:03:52.580 We've already been meeting both internally 01:03:52.580 --> 01:03:55.820 and with our partners to evaluate our lessons learned 01:03:55.820 --> 01:03:57.980 and start thinking about next steps. 01:03:57.980 --> 01:04:00.860 A few things that we learned from the two opportunities 01:04:00.860 --> 01:04:03.660 February gave us to respond to winter weather 01:04:03.660 --> 01:04:08.460 is the value of making decisions on a day-by-day basis. 01:04:08.460 --> 01:04:09.980 There's a saying here in Texas, 01:04:09.980 --> 01:04:11.220 if you don't like the weather, 01:04:11.220 --> 01:04:13.060 wait 15 minutes and it will change. 01:04:13.060 --> 01:04:15.660 And that doesn't stop during winter weather events. 01:04:15.660 --> 01:04:19.540 So the ability, as much as some of us were a little cranky 01:04:19.540 --> 01:04:22.220 and uncaffeinated at those 5 a.m. meetings, 01:04:22.220 --> 01:04:23.940 the ability to meet every day, 01:04:23.940 --> 01:04:25.540 to meet with that kind of frequency 01:04:25.540 --> 01:04:27.420 allowed us to be flexible and nimble 01:04:27.420 --> 01:04:30.340 and make decisions as they were presented to us. 01:04:30.340 --> 01:04:33.260 And so short-term decisions, meeting regularly, 01:04:33.260 --> 01:04:35.820 standard operating procedures were definitely 01:04:35.820 --> 01:04:37.700 one of the lessons learned, 01:04:37.700 --> 01:04:40.300 the best practice takeaways that we had. 01:04:40.300 --> 01:04:42.820 Another one is being able to communicate regularly 01:04:42.820 --> 01:04:43.940 with our partners. 01:04:43.940 --> 01:04:47.300 So including VIA, including Rio Grande Pacific, 01:04:47.300 --> 01:04:50.540 including NTMC in our decision-making process 01:04:50.540 --> 01:04:52.580 allows us, again, to be flexible, 01:04:52.580 --> 01:04:54.500 to know what their limitations are 01:04:54.500 --> 01:04:57.620 and then to respond as appropriate. 01:04:57.620 --> 01:04:59.900 And then the last best practice lesson learned 01:04:59.900 --> 01:05:02.020 is communication, communication, communication. 01:05:02.020 --> 01:05:04.780 I cannot overstate the importance of communicating, 01:05:04.780 --> 01:05:06.460 whether it be with this council, 01:05:06.460 --> 01:05:10.620 whether it be with our partners at our different agencies, 01:05:10.620 --> 01:05:12.140 but especially with our traveling public 01:05:12.140 --> 01:05:14.060 and letting them know what's going on 01:05:14.060 --> 01:05:16.500 and what goes into the decision-making process, 01:05:16.500 --> 01:05:19.100 that these decisions aren't made in a vacuum. 01:05:19.100 --> 01:05:22.900 As we look towards the next winter season, 01:05:22.900 --> 01:05:24.540 we're already starting to take a look at things 01:05:24.540 --> 01:05:25.820 that we could do better. 01:05:25.820 --> 01:05:28.260 So how can we start being proactive 01:05:28.260 --> 01:05:31.780 in a way that allows us to continue operations 01:05:31.780 --> 01:05:33.180 as much as we can, again, 01:05:33.180 --> 01:05:35.900 always with that safety component top of mind. 01:05:35.900 --> 01:05:38.100 And then we also know that the City of Denton 01:05:38.100 --> 01:05:40.820 has been interested in having conversations 01:05:40.820 --> 01:05:43.980 with transportation needs for individuals 01:05:43.980 --> 01:05:46.940 to emergency warming centers and shelters, 01:05:46.940 --> 01:05:48.420 even when it's not icy. 01:05:48.420 --> 01:05:50.860 So those are conversations that we're happy to engage with 01:05:50.860 --> 01:05:54.340 with the city as we start planning for next February. 01:05:54.340 --> 01:05:57.020 So with that, that's really all I have 01:05:57.020 --> 01:05:58.580 on the winter weather response. 01:05:58.580 --> 01:06:01.420 And if there are any questions, I'm happy to answer them. 01:06:03.620 --> 01:06:07.300 - Great performance, I mean, with the service. 01:06:07.300 --> 01:06:10.620 - Yeah, and I said this at our last board meeting, 01:06:10.620 --> 01:06:12.020 but I wanna say it here as well, 01:06:12.020 --> 01:06:14.740 that thank you to DCTA staff. 01:06:14.740 --> 01:06:16.100 I know that our staff here at the city 01:06:16.100 --> 01:06:19.540 also did outstanding work during both of those storms 01:06:19.540 --> 01:06:24.540 to keep folks safe and maintain those essential services. 01:06:24.540 --> 01:06:28.020 It was a tricky situation. 01:06:28.020 --> 01:06:30.620 Safety always comes first, obviously, 01:06:30.620 --> 01:06:33.260 and that's a balancing act. 01:06:33.260 --> 01:06:36.220 No, you don't want vehicles on the road unnecessarily, 01:06:36.220 --> 01:06:39.100 but as you said, there are folks who need to get to dialysis. 01:06:39.100 --> 01:06:41.020 And I think that y'all did an excellent job 01:06:41.020 --> 01:06:42.300 of balancing those concerns. 01:06:42.300 --> 01:06:43.220 - Thank you, ma'am. 01:06:43.220 --> 01:06:48.820 - All right, well, with that, that concludes our presentation. 01:06:48.820 --> 01:06:49.660 Thank you again. 01:06:49.660 --> 01:06:50.780 - No, don't leave, don't leave. 01:06:50.780 --> 01:06:53.380 - Aw, man. - Any questions, sorry. 01:06:53.380 --> 01:06:56.620 I figured, you know, DCTA is on the slide, 01:06:56.620 --> 01:06:59.220 therefore we could ask anything related to DCTA. 01:06:59.220 --> 01:07:00.060 I hope that's right. 01:07:00.060 --> 01:07:01.420 - That's fair game. - We like long meetings 01:07:01.420 --> 01:07:02.260 here in Denton. 01:07:02.260 --> 01:07:04.500 - I was wondering, Paul, could you maybe share 01:07:04.500 --> 01:07:07.140 with my colleagues a little bit about what's going on 01:07:07.140 --> 01:07:08.380 with the A train? 01:07:08.380 --> 01:07:11.980 Because there are so many exciting plans in the works 01:07:11.980 --> 01:07:15.780 for the A train with Corinth and Carrollton 01:07:15.780 --> 01:07:19.660 and positive train controls and maybe double tracking. 01:07:19.660 --> 01:07:21.860 - Sure, glad to. 01:07:21.860 --> 01:07:24.740 So in our last board meeting, we provided, 01:07:24.740 --> 01:07:26.780 I provided a briefing on opportunities 01:07:26.780 --> 01:07:28.660 to enhance the value of the A train, 01:07:28.660 --> 01:07:30.900 that really the value that the A train provides 01:07:30.900 --> 01:07:32.820 to our member cities 01:07:32.820 --> 01:07:35.380 and our broader Denton County community. 01:07:35.380 --> 01:07:39.620 The basis of the presentation was, 01:07:39.620 --> 01:07:42.300 we have opportunities for new member cities, 01:07:42.300 --> 01:07:44.580 potentially in Corinth. 01:07:44.580 --> 01:07:47.420 We have opportunities to be in further partnership 01:07:47.420 --> 01:07:49.020 with Dallas area rapid transit 01:07:49.020 --> 01:07:51.740 to get the A train down to Carrollton. 01:07:51.740 --> 01:07:54.140 And we have opportunities to partner 01:07:54.140 --> 01:07:55.700 with the private development community, 01:07:55.700 --> 01:07:58.500 as well as leverage our own land resources 01:07:58.500 --> 01:08:00.540 to do transit oriented development. 01:08:00.540 --> 01:08:02.460 All three of those different things we believe 01:08:02.460 --> 01:08:05.300 would lead to increased ridership on the A train 01:08:05.300 --> 01:08:07.580 and again, causing it to be of greater value 01:08:07.580 --> 01:08:09.220 for our communities. 01:08:09.220 --> 01:08:13.580 And so the vision that was set forth in that meeting 01:08:13.580 --> 01:08:16.180 was the opportunity or the need really 01:08:16.180 --> 01:08:18.740 to evaluate all the different infrastructure components 01:08:18.740 --> 01:08:21.940 that are required to make those things happen. 01:08:21.940 --> 01:08:25.420 And that's enhanced capacity primarily through, 01:08:25.420 --> 01:08:27.980 by increasing speeds, we can increase speeds 01:08:27.980 --> 01:08:30.060 and capacity by doing things like improving 01:08:30.060 --> 01:08:31.580 our positive train control system, 01:08:31.580 --> 01:08:33.740 which is the automated safety overlay 01:08:33.740 --> 01:08:35.620 that sits over top that train 01:08:35.620 --> 01:08:38.140 to make sure that it operates within its boundaries 01:08:38.140 --> 01:08:39.740 as safely as possible. 01:08:39.740 --> 01:08:43.180 Also the addition of track segments in different places 01:08:43.180 --> 01:08:46.140 be a siding so that two trains can pass one another 01:08:46.140 --> 01:08:48.380 or double tracking so that two trains can operate 01:08:48.380 --> 01:08:50.980 in the same space simultaneously 01:08:50.980 --> 01:08:52.380 as they go in opposite directions. 01:08:52.380 --> 01:08:55.140 The old, if a train leaves station A at this time 01:08:55.140 --> 01:08:56.700 and a train leaves station B at this time, 01:08:56.700 --> 01:08:57.540 where do they meet? 01:08:57.540 --> 01:08:59.820 That's the kind of analysis that we're talking about. 01:08:59.820 --> 01:09:04.500 And so the board provided signals 01:09:04.500 --> 01:09:06.780 that it is interested in moving forward 01:09:06.780 --> 01:09:08.380 with understanding what that would take. 01:09:08.380 --> 01:09:09.740 And so we've been in conversation 01:09:09.740 --> 01:09:11.340 with our consultant partners 01:09:11.340 --> 01:09:13.340 who have evaluated different pieces 01:09:13.340 --> 01:09:14.740 of that puzzle over time. 01:09:14.740 --> 01:09:17.140 Like what would it take to add a station at Corinth 01:09:17.140 --> 01:09:18.300 and not degrade performance? 01:09:18.300 --> 01:09:21.860 What would it take to enhance our PTC system? 01:09:21.860 --> 01:09:24.260 But we have not done that evaluation altogether 01:09:24.260 --> 01:09:27.620 because the system of the railroad 01:09:27.620 --> 01:09:29.220 depends on all those different pieces. 01:09:29.220 --> 01:09:31.180 And if we wanna really determine 01:09:31.180 --> 01:09:32.580 what are the most cost effective ways 01:09:32.580 --> 01:09:34.060 to achieve those outcomes, 01:09:34.060 --> 01:09:35.580 we should look at them altogether. 01:09:35.580 --> 01:09:38.140 So since that board meeting had a call 01:09:38.140 --> 01:09:39.980 with our consultant team as recently as yesterday 01:09:39.980 --> 01:09:42.220 to continue to refine the scope of services 01:09:42.220 --> 01:09:44.220 that we can bring back to our board here 01:09:44.220 --> 01:09:46.780 in the near future to say, here's a path forward 01:09:46.780 --> 01:09:48.220 should we choose to take it. 01:09:48.220 --> 01:09:50.180 So thank you for the question. 01:09:50.180 --> 01:09:54.500 - I have several questions about via GoZone. 01:09:54.500 --> 01:09:57.380 If I can hold you a little bit. 01:09:57.380 --> 01:09:58.220 - Sure. 01:09:59.500 --> 01:10:04.260 - Do we have safety expectations in our contract? 01:10:04.260 --> 01:10:09.260 Are there metrics about accidents and frequency and so on? 01:10:09.260 --> 01:10:13.820 Any kind of service level definition related to safety? 01:10:13.820 --> 01:10:18.860 - I would like to be able to really digest the contract 01:10:18.860 --> 01:10:20.820 with these sorts of questions in mind. 01:10:20.820 --> 01:10:21.660 - I'll give you the questions. 01:10:21.660 --> 01:10:22.900 You do not expect me to answer something like that. 01:10:22.900 --> 01:10:23.740 - Okay, great. 01:10:23.740 --> 01:10:24.780 So safety metrics. 01:10:24.780 --> 01:10:26.100 - Okay, yeah. 01:10:26.100 --> 01:10:31.100 - And then obviously the rejoinder is how are we doing? 01:10:31.100 --> 01:10:32.940 How's that looking? 01:10:32.940 --> 01:10:36.980 Do we have average wait time expectations 01:10:36.980 --> 01:10:39.020 with service level metrics in our contract 01:10:39.020 --> 01:10:40.660 and how are we doing? 01:10:40.660 --> 01:10:41.780 - Okay. 01:10:41.780 --> 01:10:45.900 - And last one I wanna in that vein is 01:10:45.900 --> 01:10:49.060 do we have specific service level metrics 01:10:49.060 --> 01:10:54.060 related to having rides available for disabled customers? 01:10:56.340 --> 01:11:01.340 In other words, how many times do we provide a vehicle 01:11:01.340 --> 01:11:05.700 that is, that can take someone with a wheelchair 01:11:05.700 --> 01:11:08.780 or a walk or whatever when it's asked? 01:11:08.780 --> 01:11:09.620 - Right. 01:11:09.620 --> 01:11:13.500 - Is there a correctly equipped vehicle available? 01:11:13.500 --> 01:11:18.500 And obviously these questions are coming from a concern 01:11:18.500 --> 01:11:21.860 that maybe we're not meeting those standards 01:11:21.860 --> 01:11:24.820 or that there aren't standards built into the relationship. 01:11:24.820 --> 01:11:27.940 So, you wanna know, I wanna know. 01:11:27.940 --> 01:11:28.780 - Yeah. 01:11:28.780 --> 01:11:29.620 - We'll talk about it when-- 01:11:29.620 --> 01:11:30.900 - So we will in the conversation 01:11:30.900 --> 01:11:32.300 that we'll have tomorrow at our board meeting, 01:11:32.300 --> 01:11:34.340 we are gonna talk about performance metrics 01:11:34.340 --> 01:11:36.780 like average wait time, seat unavailability, 01:11:36.780 --> 01:11:37.860 those sorts of things. 01:11:37.860 --> 01:11:39.140 We'll have a conversation with the board 01:11:39.140 --> 01:11:42.340 about what are the inputs that can be had 01:11:42.340 --> 01:11:44.900 to improve those things. 01:11:44.900 --> 01:11:48.540 And so we can certainly come back to this body 01:11:48.540 --> 01:11:52.820 with more details around the more robust set of metrics 01:11:52.820 --> 01:11:53.740 that you've just laid out. 01:11:53.740 --> 01:11:55.140 - I'll tell you, the driver safety thing, 01:11:55.140 --> 01:11:59.180 if the anecdotes bear out, that's a really serious concern. 01:11:59.180 --> 01:12:02.540 If there's something systemic in the way 01:12:02.540 --> 01:12:04.540 that they're compensated or managed 01:12:04.540 --> 01:12:07.020 that is leading to a problem there, 01:12:07.020 --> 01:12:11.660 I'm gonna stay from Missouri, you'll tell me, 01:12:11.660 --> 01:12:14.660 but if that is a reality, 01:12:14.660 --> 01:12:18.180 that's gotta go to the top of the list, right? 01:12:18.180 --> 01:12:19.020 - Understood. 01:12:19.020 --> 01:12:22.100 - Okay, that's great, thank you very much. 01:12:22.100 --> 01:12:24.100 I really appreciate you coming in, sharing with us. 01:12:24.100 --> 01:12:24.940 - Oh, please. 01:12:24.940 --> 01:12:34.660 - I wanna preface this by saying that I was on Nextdoor, 01:12:34.660 --> 01:12:38.140 you know the Nextdoor app? 01:12:38.140 --> 01:12:40.700 So there's all kinds of things that are going on. 01:12:40.700 --> 01:12:44.020 But one of the questions that came up 01:12:44.020 --> 01:12:47.000 and it seemed a bit petty. 01:12:47.000 --> 01:12:49.820 And as a city council person, 01:12:49.820 --> 01:12:52.460 I always wanna just jump on there 01:12:52.460 --> 01:12:55.620 and say something, you know, to these people. 01:12:55.620 --> 01:13:00.620 But I know that it has to be in a way that, you know. 01:13:00.620 --> 01:13:03.700 So I just choose not to indulge. 01:13:03.700 --> 01:13:08.700 But the question came up and the concern in the, 01:13:08.700 --> 01:13:10.760 and I'll use this term loosely, 01:13:10.760 --> 01:13:15.760 the pettiness came up as to why the GoZone cars 01:13:17.540 --> 01:13:22.540 do not have the State of Texas registration tags on them. 01:13:22.540 --> 01:13:27.780 And so they're concerned that the vehicles may not be safe 01:13:27.780 --> 01:13:32.700 as if they were not, you know, that's serious, 01:13:32.700 --> 01:13:35.020 but it was just kinda, you know, a first thought that, 01:13:35.020 --> 01:13:36.420 well, what does this matter? 01:13:36.420 --> 01:13:40.020 But it does if we're talking about people riding 01:13:40.020 --> 01:13:44.900 in State of Texas examined vehicles, you know, 01:13:44.900 --> 01:13:48.140 we have to have our cars inspected 01:13:48.140 --> 01:13:50.100 before we get our registration. 01:13:50.100 --> 01:13:53.700 And if we're seeing a lot of cars coming out of Florida 01:13:53.700 --> 01:13:57.740 or wherever these tags are from that's, 01:13:57.740 --> 01:13:58.940 they didn't say that. 01:13:58.940 --> 01:14:01.280 I'm adding that particular part on there 01:14:01.280 --> 01:14:03.660 that it's a safety factor as well. 01:14:03.660 --> 01:14:07.340 So Mayor Pro Tem, I appreciate you bringing 01:14:07.340 --> 01:14:11.340 that conversation up, you know, that topic up of safety. 01:14:11.340 --> 01:14:13.480 This also goes along with that. 01:14:13.480 --> 01:14:16.180 How can we assure our riders 01:14:16.180 --> 01:14:18.980 that they are in the safest vehicles possible, 01:14:18.980 --> 01:14:23.820 especially by having those vehicles registered 01:14:23.820 --> 01:14:24.700 with the State of Texas? 01:14:24.700 --> 01:14:28.300 I don't think I've seen one that shown 01:14:28.300 --> 01:14:32.080 that it was a Texas registered vehicle, 01:14:32.080 --> 01:14:34.720 which thereby means that it's been inspected 01:14:34.720 --> 01:14:38.120 and, you know, and allowed to be on the road. 01:14:38.120 --> 01:14:39.820 - Understood. - Thank you. 01:14:39.820 --> 01:14:41.300 - Yeah, you know, if you can, you know, 01:14:41.300 --> 01:14:45.220 if the general safety issue is substantiated, 01:14:45.220 --> 01:14:47.860 then I'm sure there are many tools 01:14:47.860 --> 01:14:49.120 you're gonna want to look at. 01:14:49.120 --> 01:14:50.060 How are they recruited? 01:14:50.060 --> 01:14:51.700 What are the standards? 01:14:51.700 --> 01:14:53.980 What's the training, right? 01:14:53.980 --> 01:14:55.540 So obvious management stuff. 01:14:55.540 --> 01:14:58.100 Yeah, thank you so much. 01:14:58.100 --> 01:14:59.340 - Okay, thank you. 01:14:59.340 --> 01:15:07.320 - All right, we're on to MC22-08 staff report. 01:15:11.300 --> 01:15:13.960 (door thudding) 01:15:13.960 --> 01:15:31.180 All righty, well, thank you very much 01:15:31.180 --> 01:15:35.620 for having me to allow me to do the staff report today. 01:15:35.620 --> 01:15:37.540 So the first thing that I wanted to start off with, 01:15:37.540 --> 01:15:40.340 I know last month we introduced Brett, 01:15:40.340 --> 01:15:42.740 our new deputy city engineer. 01:15:42.740 --> 01:15:45.500 Trevor also is new to our department 01:15:45.500 --> 01:15:46.960 and is taking the position 01:15:46.960 --> 01:15:49.780 that Rachel Wood previously held. 01:15:49.780 --> 01:15:52.160 And so I wanted to give Trevor a chance to come up 01:15:52.160 --> 01:15:54.820 and introduce himself, talk to y'all a little bit 01:15:54.820 --> 01:15:58.060 about his different roles he's played within the department. 01:15:58.060 --> 01:15:59.980 And we're gonna start off with that. 01:15:59.980 --> 01:16:00.820 So Trevor. 01:16:09.820 --> 01:16:11.340 - Good morning, thanks for having me. 01:16:11.340 --> 01:16:12.540 So my name's Trevor Crane 01:16:12.540 --> 01:16:14.940 and I'm the Deputy Director of Capital Projects. 01:16:14.940 --> 01:16:17.660 I've been with the city almost three years now. 01:16:17.660 --> 01:16:20.500 I originally came in October of 2019 01:16:20.500 --> 01:16:24.020 as a project manager in the Capital Improvements Department. 01:16:24.020 --> 01:16:25.340 Close to about 10 months ago, 01:16:25.340 --> 01:16:28.020 I was promoted to the Public Works Inspections Manager, 01:16:28.020 --> 01:16:31.340 and I've been in that role since, 01:16:31.340 --> 01:16:34.940 or I guess up to about a month now I've been in this role. 01:16:34.940 --> 01:16:37.480 So I'm excited to move into this role. 01:16:37.480 --> 01:16:39.660 I worked with Rachel very closely 01:16:39.660 --> 01:16:42.660 when I was a project manager in that department. 01:16:42.660 --> 01:16:44.260 I was involved in a lot of those policies 01:16:44.260 --> 01:16:46.160 and procedures that we built. 01:16:46.160 --> 01:16:48.020 So I'm excited to be back with that team 01:16:48.020 --> 01:16:49.940 and keep moving this forward. 01:16:49.940 --> 01:16:51.820 - Welcome. 01:16:51.820 --> 01:16:52.660 - Thank you. 01:16:52.660 --> 01:16:59.080 - Thank you, Trevor. 01:16:59.080 --> 01:17:02.720 The unfortunate part is we now have 01:17:02.720 --> 01:17:05.060 a Public Works Inspection Manager position to fill. 01:17:05.060 --> 01:17:07.980 But I am glad to have Trevor in the position that he's in. 01:17:07.980 --> 01:17:10.660 He's doing a fantastic job already. 01:17:10.660 --> 01:17:13.860 So the next item that we wanted to go through 01:17:13.860 --> 01:17:17.440 was the Parkway Street and then the Locust Elm intersections. 01:17:17.440 --> 01:17:19.740 I know Mayor Pro Tem, I believe you asked 01:17:19.740 --> 01:17:21.500 for some additional information. 01:17:21.500 --> 01:17:25.660 We do have individuals from the Traffic Operations Team 01:17:25.660 --> 01:17:28.300 present today that helped work with us on this. 01:17:28.300 --> 01:17:30.500 So specifically, you asked the question 01:17:30.500 --> 01:17:34.420 about when the traffic signal analysis was completed, 01:17:34.420 --> 01:17:36.220 when the signals were brought down, 01:17:36.220 --> 01:17:38.100 and kind of what that process was. 01:17:38.100 --> 01:17:40.260 So I'm gonna paraphrase, but of course 01:17:40.260 --> 01:17:42.380 you have the backup in your information. 01:17:42.380 --> 01:17:45.580 So June 2019, staff did construct 01:17:45.580 --> 01:17:48.100 a traffic signal warrant analysis 01:17:48.100 --> 01:17:50.140 and determined that they thought it was best 01:17:50.140 --> 01:17:52.980 to remove the signals at those intersections. 01:17:52.980 --> 01:17:57.180 And that deactivation occurred in January of 2020. 01:17:57.180 --> 01:18:00.900 And then it kept in that same operation 01:18:00.900 --> 01:18:04.940 until December 8th of 2021. 01:18:04.940 --> 01:18:08.220 During that time frame, that intersection 01:18:08.220 --> 01:18:11.100 operated with a side street stop on Parkway. 01:18:11.100 --> 01:18:13.660 So if you can envision, you're only stopping 01:18:13.660 --> 01:18:16.060 at Parkway at both Elm and Locust. 01:18:16.060 --> 01:18:20.500 So there was free flow of traffic traversing 01:18:20.500 --> 01:18:23.220 up and down Elm and Locust. 01:18:23.220 --> 01:18:26.340 October 8th, our team, along with James Andrews 01:18:26.340 --> 01:18:29.740 and Danny Kramer, Traffic Operations, Street Operations, 01:18:29.740 --> 01:18:33.540 worked through to install that all-way stop. 01:18:33.540 --> 01:18:35.820 So now envision that now we have stop signs 01:18:35.820 --> 01:18:38.380 both at Elm and Locust. 01:18:38.380 --> 01:18:42.020 Then James actually worked to install 01:18:42.020 --> 01:18:44.740 the red flashing beacon. 01:18:44.740 --> 01:18:48.380 And that's actually just at the intersection of Elm. 01:18:48.380 --> 01:18:51.780 What we found, and James did some of this evaluation, 01:18:51.780 --> 01:18:55.300 was folks that are coming northbound on Locust, 01:18:55.300 --> 01:18:57.620 they've just come through the intersection at McKinney, 01:18:57.620 --> 01:18:59.980 so they're not accelerating as quickly, 01:18:59.980 --> 01:19:02.180 and they're noticing that there's a stop sign 01:19:02.180 --> 01:19:03.700 almost immediately. 01:19:03.700 --> 01:19:06.860 Folks that are coming down Elm Street, unfortunately, 01:19:06.860 --> 01:19:09.180 they haven't had a signal since 380. 01:19:09.180 --> 01:19:11.700 They could have picked up a decent rate of speed, 01:19:11.700 --> 01:19:14.140 and we're not always noticing those stop signs 01:19:14.140 --> 01:19:16.500 that were installed at Elm. 01:19:16.500 --> 01:19:21.500 So red flashing beacons are located at that location. 01:19:21.500 --> 01:19:25.980 We did work with PD to assemble crash data, 01:19:25.980 --> 01:19:28.220 and we're working to complete all of that. 01:19:28.220 --> 01:19:29.700 I know we mentioned that we're gonna have 01:19:29.700 --> 01:19:31.500 that crash data available. 01:19:31.500 --> 01:19:32.980 Nathan has some preliminary, 01:19:32.980 --> 01:19:34.580 which he just stepped out of the room, 01:19:34.580 --> 01:19:35.500 preliminary data. 01:19:35.500 --> 01:19:37.700 One of the things that we're working through 01:19:37.700 --> 01:19:38.860 is collecting all of that 01:19:38.860 --> 01:19:41.540 so that we can provide that information to you. 01:19:41.540 --> 01:19:46.220 So something that we're continuing to work with PD on. 01:19:46.220 --> 01:19:48.820 We ourselves, because we're now housed 01:19:48.820 --> 01:19:50.500 right at the corner of that intersection, 01:19:50.500 --> 01:19:52.300 have seen several crashes. 01:19:52.300 --> 01:19:54.180 The data is not exactly adding up 01:19:54.180 --> 01:19:55.620 with the information that we've seen. 01:19:55.620 --> 01:19:57.580 So we're working through that 01:19:57.580 --> 01:19:59.700 so that we can bring that back to the committee. 01:19:59.700 --> 01:20:00.700 And then, of course, 01:20:00.700 --> 01:20:03.420 we're continuing to evaluate the operations. 01:20:03.420 --> 01:20:06.740 I do feel like from the current perspective 01:20:06.740 --> 01:20:10.220 that we see that the all-way stop is working 01:20:10.220 --> 01:20:11.660 in a much better fashion 01:20:11.660 --> 01:20:15.580 than just the stop in the direction of Parkway. 01:20:15.580 --> 01:20:18.220 So wanted to bring that forward. 01:20:18.220 --> 01:20:20.980 Of course, as usual, we provide you the information 01:20:20.980 --> 01:20:23.580 where that was provided in previous Friday reports. 01:20:23.580 --> 01:20:27.340 There was one in October that we provided information 01:20:27.340 --> 01:20:29.900 about the warning signs and the stop signs. 01:20:29.900 --> 01:20:32.700 Any additional questions on that item? 01:20:32.700 --> 01:20:34.700 - Yes, I have one question. - Sure. 01:20:34.700 --> 01:20:38.540 - I travel that, I travel those roads 01:20:38.540 --> 01:20:41.540 'cause I live kind of on the north side. 01:20:41.540 --> 01:20:48.420 Are there any warning signs to prelude the stop signs 01:20:48.420 --> 01:20:52.100 that are going south on Elm? 01:20:52.100 --> 01:20:55.820 Do we get a warning back here that there are stop signs? 01:20:55.820 --> 01:20:58.540 - Well, I travel that every day, too, 01:20:58.540 --> 01:20:59.740 and I'll have to be honest with you. 01:20:59.740 --> 01:21:01.980 I don't know that I've ever noticed that. 01:21:01.980 --> 01:21:03.420 James says yes. 01:21:03.420 --> 01:21:04.500 James, would you like to come up 01:21:04.500 --> 01:21:06.260 and speak where those locations are? 01:21:06.260 --> 01:21:08.780 (man speaking faintly) 01:21:08.780 --> 01:21:09.620 - Okay. 01:21:09.620 --> 01:21:10.980 - The stop ahead signs, that's what they're called. 01:21:10.980 --> 01:21:11.820 - Yes, ma'am. 01:21:11.820 --> 01:21:13.860 So sounds like they're stop ahead signs. 01:21:13.860 --> 01:21:16.380 I would assume they're several hundred feet 01:21:16.380 --> 01:21:20.620 from the intersection north of the intersection 01:21:20.620 --> 01:21:22.580 that actually tell people that there is going to be 01:21:22.580 --> 01:21:23.540 a stop sign ahead. 01:21:23.540 --> 01:21:25.540 And we can look at those exact locations, too, 01:21:25.540 --> 01:21:26.380 if you'd like to know this. 01:21:26.380 --> 01:21:27.980 - Well, I'm gonna drive. - Okay. 01:21:27.980 --> 01:21:29.420 - I gotta go that way anyway when I leave here. 01:21:29.420 --> 01:21:30.260 - Well, great. 01:21:30.260 --> 01:21:32.340 - So I'm gonna come back on Elm 01:21:32.340 --> 01:21:35.620 because my next meeting is over across the way 01:21:35.620 --> 01:21:36.700 at your building. 01:21:36.700 --> 01:21:39.580 So I will see that for myself 01:21:39.580 --> 01:21:42.700 because I don't have it in my head 01:21:42.700 --> 01:21:46.380 as to whether or not I'm told that there's a stop sign. 01:21:46.380 --> 01:21:47.220 - Sure. 01:21:47.220 --> 01:21:50.340 - Ahead, other than then seeing the flashing lights. 01:21:50.340 --> 01:21:51.180 - Absolutely. 01:21:51.180 --> 01:21:52.260 - So, yeah, I'll do that. 01:21:52.260 --> 01:21:53.540 - Okay, great. 01:21:53.540 --> 01:21:54.420 Wonderful. 01:21:54.420 --> 01:21:56.740 So on that item specifically, 01:21:56.740 --> 01:21:58.540 hopefully we've addressed the questions. 01:21:58.540 --> 01:22:00.500 The only thing that we have still we're working through 01:22:00.500 --> 01:22:03.420 with PD is just that crash data specifically 01:22:03.420 --> 01:22:07.420 on the Parkway and Locust and Parkway and Elm. 01:22:07.420 --> 01:22:09.060 Like I mentioned, Nathan is working 01:22:09.060 --> 01:22:11.180 with the police department to continue to collect 01:22:11.180 --> 01:22:13.300 all of that in a fashion that we can present 01:22:13.300 --> 01:22:14.900 that information to you. 01:22:14.900 --> 01:22:18.100 So we will bring that crash data back at the next meeting. 01:22:19.900 --> 01:22:23.340 The next item that was a part of our staff report 01:22:23.340 --> 01:22:27.260 from last month was to get an update kind of on, 01:22:27.260 --> 01:22:30.020 and I think it was quoted saying kind of what's going on 01:22:30.020 --> 01:22:34.140 in the Dearwood, Kingsway, Kingsrow area. 01:22:34.140 --> 01:22:37.580 And so we are working with the development services team 01:22:37.580 --> 01:22:40.060 to provide you information that shows you 01:22:40.060 --> 01:22:42.700 the existing configurations in that area, 01:22:42.700 --> 01:22:45.700 what the mobility plan now shows for that area, 01:22:45.700 --> 01:22:48.860 and then specifically what the development was required 01:22:48.860 --> 01:22:51.620 to do in that area, or asked to do in that area 01:22:51.620 --> 01:22:52.860 as a part of that PD. 01:22:52.860 --> 01:22:55.220 So that'll be a presentation that'll be brought back 01:22:55.220 --> 01:22:56.580 at the April meeting. 01:22:56.580 --> 01:22:58.780 Is there anything else specifically that you'd like 01:22:58.780 --> 01:23:01.500 for us to drill down on that individual item? 01:23:01.500 --> 01:23:05.860 Okay. 01:23:05.860 --> 01:23:09.340 - I just have another question here. 01:23:09.340 --> 01:23:10.180 - Sure. 01:23:10.180 --> 01:23:17.500 - Speaking with the State of Texas group 01:23:17.500 --> 01:23:21.140 and connecting with our city, 01:23:21.140 --> 01:23:25.140 I mean our development issue that we had over there, 01:23:25.140 --> 01:23:28.420 I know that one of the primary concerns 01:23:28.420 --> 01:23:33.420 was whether or not that frontage road would be ready, 01:23:33.420 --> 01:23:36.900 you know, when this development came through. 01:23:36.900 --> 01:23:39.140 And I think that that was one of the things 01:23:39.140 --> 01:23:42.180 that it was highlighted pretty heavily, 01:23:42.180 --> 01:23:43.580 you know, at that point. 01:23:43.580 --> 01:23:46.460 And as we were having that conversation, 01:23:46.460 --> 01:23:49.540 I was trying to connect whether or not 01:23:49.540 --> 01:23:53.300 if we did the service to that community, 01:23:53.300 --> 01:24:01.180 and trying to figure out the timeframe 01:24:01.180 --> 01:24:04.140 that a frontage road would be put in, 01:24:04.140 --> 01:24:09.140 versus the timeframe when the development would be there. 01:24:09.140 --> 01:24:12.100 So the issue is still there, 01:24:12.100 --> 01:24:14.220 because some of the conversation came through 01:24:14.220 --> 01:24:17.500 as to the lot size and all of that other stuff. 01:24:17.500 --> 01:24:22.500 So would you all look into that? 01:24:22.500 --> 01:24:27.220 You know, how closely would the development be done 01:24:27.220 --> 01:24:30.740 versus being able to have a true frontage road? 01:24:30.740 --> 01:24:32.780 - Sure, we can absolutely bring that forward. 01:24:32.780 --> 01:24:34.740 I will mention to you, Mr. Polster made that 01:24:34.740 --> 01:24:36.860 as a part of his presentation. 01:24:36.860 --> 01:24:39.420 You saw where they're just in the very beginning stages. 01:24:39.420 --> 01:24:41.380 So those frontage roads, it's gonna be sometime 01:24:41.380 --> 01:24:43.380 before those are constructed. 01:24:43.380 --> 01:24:45.580 What you will hear in the presentation 01:24:45.580 --> 01:24:48.740 is that the developer, actually myself, 01:24:48.740 --> 01:24:50.740 TexDOT, several on our staff, 01:24:50.740 --> 01:24:54.900 and TexDOT Dallas district office, 01:24:54.900 --> 01:24:56.740 along with the planning department, 01:24:56.740 --> 01:25:00.580 development services team, coordinated with TexDOT 01:25:00.580 --> 01:25:03.860 to see what could be constructed 01:25:03.860 --> 01:25:05.940 since it will be sometime from the frontage road. 01:25:05.940 --> 01:25:07.460 And that's what some of the options were 01:25:07.460 --> 01:25:09.940 that Ms. Wyatt presented at that meeting. 01:25:09.940 --> 01:25:11.180 So we can bring that forward 01:25:11.180 --> 01:25:13.420 so you can kinda understand what the conversations were 01:25:13.420 --> 01:25:15.460 that we had with TexDOT. 01:25:15.460 --> 01:25:17.380 That's gonna be a similar conversation 01:25:17.380 --> 01:25:20.220 anywhere along the Loop 288 corridor 01:25:20.220 --> 01:25:22.340 from 380 all the way to 35, 01:25:22.340 --> 01:25:25.740 and really actually even to the west side of 35, 01:25:25.740 --> 01:25:27.700 where what we call the paper clips are 01:25:27.700 --> 01:25:29.940 until Loop 288 west is connected. 01:25:29.940 --> 01:25:33.660 In that particular area, 01:25:33.660 --> 01:25:36.220 because it's a controlled access freeway, 01:25:36.220 --> 01:25:38.460 direct connection because folks are driving 01:25:38.460 --> 01:25:42.620 60 miles per hour is prohibited. 01:25:42.620 --> 01:25:45.260 So we're not going to, along with ourselves 01:25:45.260 --> 01:25:49.660 and TexDOT, allow connection directly to Loop 288. 01:25:49.660 --> 01:25:51.460 So that's why some sort of frontage road 01:25:51.460 --> 01:25:54.740 will be constructed when folks need to do so. 01:25:54.740 --> 01:25:57.940 So we can bring that back to you, no problem. 01:25:57.940 --> 01:26:00.620 So timing on the actual construction 01:26:00.620 --> 01:26:02.660 of those frontage roads is quite a ways out 01:26:02.660 --> 01:26:04.300 based on Mr. Polster's report. 01:26:06.220 --> 01:26:11.220 The next question that was asked 01:26:11.220 --> 01:26:14.180 was specifically related to Southeast Denton, 01:26:14.180 --> 01:26:17.180 seeing the trucks go through to get to Duncan. 01:26:17.180 --> 01:26:19.900 And I know this is something that Mr. Kramer 01:26:19.900 --> 01:26:22.340 led the charge on with help from 01:26:22.340 --> 01:26:23.700 some of our engineering staff 01:26:23.700 --> 01:26:26.420 and then also our transportation planning staff. 01:26:26.420 --> 01:26:27.500 I think Council Member Byrd, 01:26:27.500 --> 01:26:29.340 this is one of the ones that you brought forward 01:26:29.340 --> 01:26:32.180 asking questions about trucks going through 01:26:32.180 --> 01:26:34.740 to get to Duncan and some signs 01:26:34.740 --> 01:26:36.580 that might need to be installed. 01:26:36.580 --> 01:26:38.580 Traffic operations through James' team 01:26:38.580 --> 01:26:40.780 actually did observe the street sign 01:26:40.780 --> 01:26:42.820 and determined that it needed to be replaced. 01:26:42.820 --> 01:26:45.020 So that happened on March 14th. 01:26:45.020 --> 01:26:47.180 And then you can also see additional information 01:26:47.180 --> 01:26:49.180 that was provided in the Friday report 01:26:49.180 --> 01:26:52.540 in December of 2021. 01:26:52.540 --> 01:26:57.380 So I think that from the street department, 01:26:57.380 --> 01:26:59.620 public works and traffic operations department, 01:26:59.620 --> 01:27:01.740 they feel as if they've installed 01:27:01.740 --> 01:27:05.460 the additional traffic sign measures in that area. 01:27:05.460 --> 01:27:07.700 And I'm not aware of any additional concerns 01:27:07.700 --> 01:27:09.940 that we've received in that area at this time. 01:27:09.940 --> 01:27:13.140 Okay, okay. 01:27:13.140 --> 01:27:17.980 And then of course, the last question that came up 01:27:17.980 --> 01:27:20.900 was kind of talking about the citywide speed study. 01:27:20.900 --> 01:27:22.180 Nathan is leading the charge 01:27:22.180 --> 01:27:24.420 on the citywide speed study for our team. 01:27:24.420 --> 01:27:26.500 And so I would just mention that we're currently 01:27:26.500 --> 01:27:28.260 in the data collection phase. 01:27:28.260 --> 01:27:29.380 That's the exciting part 01:27:29.380 --> 01:27:32.380 'cause we're getting all of the data collected. 01:27:32.380 --> 01:27:35.300 Nathan actually did a fantastic job 01:27:35.300 --> 01:27:37.980 of actually developing a GIS system 01:27:37.980 --> 01:27:40.020 that shows actual points of where the data 01:27:40.020 --> 01:27:43.580 is gonna be collected along with kind of an overview 01:27:43.580 --> 01:27:46.380 that shows the information that will be collected. 01:27:46.380 --> 01:27:48.860 You can see in the report that traffic speed 01:27:48.860 --> 01:27:51.940 and volume counts are being conducted. 01:27:51.940 --> 01:27:53.660 I mean, he's also looking at crash data 01:27:53.660 --> 01:27:56.220 and several other measures so that when we look 01:27:56.220 --> 01:27:59.220 at the speed of the particular roadways, 01:27:59.220 --> 01:28:04.020 there's more data that's going into those conversations 01:28:04.020 --> 01:28:05.100 in that collection. 01:28:05.100 --> 01:28:10.100 We anticipate that that will be completed by late May. 01:28:10.100 --> 01:28:13.940 So typically you wanna collect not when it's spring break 01:28:13.940 --> 01:28:15.820 and not when school's out of season. 01:28:15.820 --> 01:28:17.940 So right now we're working to collect the data 01:28:17.940 --> 01:28:20.540 from now until basically late May. 01:28:20.540 --> 01:28:22.300 Once that data is completed, 01:28:22.300 --> 01:28:25.820 then our staff along with transportation planning 01:28:25.820 --> 01:28:28.980 in development services team will work to coordinate 01:28:28.980 --> 01:28:33.580 and evaluate all of the data to draft a speed study report 01:28:33.580 --> 01:28:35.980 that will be presented not only to this committee 01:28:35.980 --> 01:28:40.940 but then also to city council in that late summer, 01:28:40.940 --> 01:28:43.540 early fall timeframe, August, September 01:28:43.540 --> 01:28:45.620 to get direction from council. 01:28:45.620 --> 01:28:52.980 And of course we completed several Friday report items 01:28:52.980 --> 01:28:54.660 on speed reduction. 01:28:54.660 --> 01:28:57.620 So I wanted to make sure you saw that that was in the June 01:28:57.620 --> 01:29:00.220 and the July Friday reports. 01:29:00.220 --> 01:29:06.700 And then with that, we are gonna move over to our matrix 01:29:06.700 --> 01:29:09.940 that Ms. Logan has provided for us. 01:29:09.940 --> 01:29:13.340 So on the first item, which is the construction 01:29:13.340 --> 01:29:15.740 of Bonnie Bray and the timing, 01:29:15.740 --> 01:29:18.620 we believed that we had addressed that concern 01:29:18.620 --> 01:29:20.020 at the February meeting. 01:29:20.020 --> 01:29:24.020 But as of today, I think that based Mayor Pro Tem 01:29:24.020 --> 01:29:29.020 on your feedback, you'd like to hear a reoccurring conversation 01:29:29.020 --> 01:29:31.420 just to give a brief status update 01:29:31.420 --> 01:29:34.220 as a part of the overall report 01:29:34.220 --> 01:29:37.540 at each one of the mobility committee meetings. 01:29:37.540 --> 01:29:43.780 - Yes, and with specific focus on the torn up area 01:29:43.780 --> 01:29:48.220 kind of from Oak Street South there. 01:29:48.220 --> 01:29:50.980 And I wonder if you'd be able to get something 01:29:50.980 --> 01:29:54.500 into a Friday report before our next mobility committee 01:29:54.500 --> 01:29:56.580 meeting, even two or three sentences. 01:29:56.580 --> 01:29:58.420 It just helped me out, you know, 01:29:58.420 --> 01:30:01.180 try answering these questions, you know, 01:30:01.180 --> 01:30:06.180 when you have a slightly annoyed person behind a door 01:30:06.180 --> 01:30:08.660 that you've knocked on and they're trying to close it, 01:30:08.660 --> 01:30:11.860 you know, that's the kind of answer I need. 01:30:11.860 --> 01:30:14.220 - Sure, we can put something, 01:30:14.220 --> 01:30:15.900 we can work to even maybe try to get something 01:30:15.900 --> 01:30:18.580 in the Friday report this week, if not next week. 01:30:18.580 --> 01:30:20.020 We actually have a change order 01:30:20.020 --> 01:30:21.780 that'll be coming through the system. 01:30:21.780 --> 01:30:24.740 It goes to PUB on Monday and to council on April 5th. 01:30:24.740 --> 01:30:26.420 That'll talk about some of the improvements 01:30:26.420 --> 01:30:28.420 that are gonna be made to expedite 01:30:28.420 --> 01:30:30.740 some of the pavement repairs in that area. 01:30:30.740 --> 01:30:32.780 So definitely something we can bring forward. 01:30:32.780 --> 01:30:34.700 We can, Trevor and I can work on making sure 01:30:34.700 --> 01:30:36.420 that that's in a Friday report. 01:30:36.420 --> 01:30:38.980 So that's not an issue at all. 01:30:38.980 --> 01:30:41.020 - Most recent email I got about that 01:30:41.020 --> 01:30:44.460 from a constituent referenced a car-sized pothole. 01:30:44.460 --> 01:30:47.580 I don't know if you got that one, yeah. 01:30:47.580 --> 01:30:48.900 - Well, if you'll continue to bring those 01:30:48.900 --> 01:30:51.660 to our attention, you know, we received word yesterday 01:30:51.660 --> 01:30:54.260 from TXOT about some concerns on their driveway entrance 01:30:54.260 --> 01:30:56.420 because that's one of the only ways in and out 01:30:56.420 --> 01:30:58.940 of their facility and they drive larger trucks 01:30:58.940 --> 01:30:59.940 through that area. 01:30:59.940 --> 01:31:01.980 If those concerns are brought to our attention, 01:31:01.980 --> 01:31:03.340 whether it's through the project manager, 01:31:03.340 --> 01:31:05.380 engaged it and et cetera, we'll be happy 01:31:05.380 --> 01:31:07.820 to have the contractor go out and evaluate those concerns. 01:31:07.820 --> 01:31:11.100 I know there's been several that Danny assisted with 01:31:11.100 --> 01:31:13.740 during some of the ice and some of the weather conditions. 01:31:13.740 --> 01:31:17.220 So if we're aware of those, we'll work to address them. 01:31:17.220 --> 01:31:19.900 Obviously we understand the roadway needs to be repaved. 01:31:19.900 --> 01:31:21.860 We're working to complete the utility. 01:31:21.860 --> 01:31:25.820 The next item on the Parkway Locust, 01:31:25.820 --> 01:31:28.780 I'm gonna leave that on the overall agenda 01:31:28.780 --> 01:31:31.100 because I wanna make sure that we bring back 01:31:31.100 --> 01:31:32.620 that crash data. 01:31:32.620 --> 01:31:34.380 Nathan's gonna work to collect that 01:31:34.380 --> 01:31:35.940 and present it to you in a manner 01:31:35.940 --> 01:31:38.660 that we can share that information. 01:31:38.660 --> 01:31:42.220 The Kingsrow, we already discussed that. 01:31:42.220 --> 01:31:44.420 That'll come back at the April 20th meeting. 01:31:45.620 --> 01:31:47.580 I guess Council Member Byrd, 01:31:47.580 --> 01:31:49.420 would you like for us to leave the Southeast 01:31:49.420 --> 01:31:51.860 in the neighborhood until you have an opportunity 01:31:51.860 --> 01:31:53.860 to discuss with constituents 01:31:53.860 --> 01:31:56.060 if they're still concerned in that area? 01:31:56.060 --> 01:31:58.100 - I'll be speaking with them on Monday 01:31:58.100 --> 01:32:00.260 at their neighborhood meeting 01:32:00.260 --> 01:32:02.020 and we'll have that conversation. 01:32:02.020 --> 01:32:05.780 By the way, I did notice a nice brand new Dunkin' sign 01:32:05.780 --> 01:32:07.900 up there off of... 01:32:07.900 --> 01:32:11.220 When you cross over Dallas Drive, 01:32:11.220 --> 01:32:14.420 I think it's called Shady Oaks or something like that. 01:32:14.420 --> 01:32:17.700 I never could get the name of that street right. 01:32:17.700 --> 01:32:19.820 But I did notice a brand new sign, 01:32:19.820 --> 01:32:24.820 but I did not notice any signs notifying drivers 01:32:24.820 --> 01:32:30.540 of larger vehicles that this is not a through street area. 01:32:30.540 --> 01:32:33.900 I need to check with that. 01:32:33.900 --> 01:32:36.820 So I'll talk to them on Monday 01:32:36.820 --> 01:32:38.220 and I'll get back with you. 01:32:38.220 --> 01:32:39.420 - No, that'd be fantastic. 01:32:39.420 --> 01:32:42.540 Actually, if you have that opportunity to speak with them 01:32:42.540 --> 01:32:45.140 and then could provide that information to us, 01:32:45.140 --> 01:32:46.500 we'll make sure that we address it 01:32:46.500 --> 01:32:48.820 at our next mobility committee meeting. 01:32:48.820 --> 01:32:50.180 Yes, ma'am, thank you. 01:32:50.180 --> 01:32:52.900 And then of course, the citywide speed study, 01:32:52.900 --> 01:32:54.020 we've given you an update. 01:32:54.020 --> 01:32:56.100 Is that something that you still want us to continue 01:32:56.100 --> 01:32:58.940 to give you a monthly update on or do you feel like 01:32:58.940 --> 01:33:00.540 since we're in the middle of data collection, 01:33:00.540 --> 01:33:03.540 we can wait until the time that data has been collected 01:33:03.540 --> 01:33:06.500 and of course, we're ready to kind of do that draft plan 01:33:06.500 --> 01:33:07.780 or is that something you're wanting us 01:33:07.780 --> 01:33:09.420 to continue to bring back to you? 01:33:10.540 --> 01:33:13.540 - Comments, sorry. - I think I can wait. 01:33:13.540 --> 01:33:18.780 - How about you, do you need a continuous update 01:33:18.780 --> 01:33:22.060 or ready to wait until there's something to report? 01:33:22.060 --> 01:33:26.900 - At least I could be able to let my constituents know 01:33:26.900 --> 01:33:29.460 that we're working on a speed study. 01:33:29.460 --> 01:33:30.460 - Yes, ma'am. 01:33:30.460 --> 01:33:32.780 It's gonna be several months to collect that data 01:33:32.780 --> 01:33:35.620 so we don't anticipate even having that data in 01:33:35.620 --> 01:33:36.940 until late May. 01:33:37.980 --> 01:33:40.700 So we wanna work through the school year 01:33:40.700 --> 01:33:43.740 because that's when normal travel patterns are happening 01:33:43.740 --> 01:33:48.100 and so it'll be late May before Nathan has that data in. 01:33:48.100 --> 01:33:50.020 - I'm happy to wait until there's something to report. 01:33:50.020 --> 01:33:51.260 - Okay, perfect. 01:33:51.260 --> 01:33:52.740 - And also-- - Without objection. 01:33:52.740 --> 01:33:53.580 - Excuse me, sir. 01:33:53.580 --> 01:33:56.900 Also, is this speed study, 01:33:56.900 --> 01:33:58.940 is it including that South Indian version 01:33:58.940 --> 01:34:02.500 of the evil ways that you've renovated? 01:34:02.500 --> 01:34:05.300 - There will be roadways that are included. 01:34:05.300 --> 01:34:08.380 Keep in mind that this is only for roadways 01:34:08.380 --> 01:34:11.180 and that's something we could report on, 01:34:11.180 --> 01:34:13.780 but this is only for roadways where posted speed limit 01:34:13.780 --> 01:34:15.740 is not 30 miles per hour. 01:34:15.740 --> 01:34:19.620 So there's specific lists that were provided previously 01:34:19.620 --> 01:34:22.100 that we evaluated and then Nathan also evaluated 01:34:22.100 --> 01:34:24.540 additional roadways that he wanted to study 01:34:24.540 --> 01:34:26.860 based on conversations that we had 01:34:26.860 --> 01:34:28.940 or questions that come in maybe 01:34:28.940 --> 01:34:31.700 from a speeding perspective, et cetera. 01:34:31.700 --> 01:34:36.100 So definitely roadways that may be traversing that area, 01:34:36.100 --> 01:34:38.060 but not specifically residential streets 01:34:38.060 --> 01:34:39.260 in that downtown area. 01:34:39.260 --> 01:34:44.300 So with that, that is all that we currently have 01:34:44.300 --> 01:34:45.140 on the staff report. 01:34:45.140 --> 01:34:46.140 Is there anything additional 01:34:46.140 --> 01:34:48.100 that either one of you would like to add 01:34:48.100 --> 01:34:50.860 for us to bring back at the April meeting? 01:34:50.860 --> 01:34:55.060 - Yes, I'd like to add a street to the report. 01:34:55.060 --> 01:34:58.140 It's gonna be Swisher Road 01:34:58.140 --> 01:35:02.040 that's off of Shady Shores Road. 01:35:02.040 --> 01:35:07.380 Yes, it's in the city of Denton. 01:35:07.380 --> 01:35:09.300 - Portions are and portions are not. 01:35:09.300 --> 01:35:12.260 - Right, so this particular portion 01:35:12.260 --> 01:35:17.100 is there beautiful homes on the street, 01:35:17.100 --> 01:35:21.340 but the road is not conducive to what they need right now. 01:35:21.340 --> 01:35:22.700 - Okay. 01:35:22.700 --> 01:35:25.100 - Some culvert issues, drainage, 01:35:26.460 --> 01:35:30.040 and I've driven out there and spoken with homeowners 01:35:30.040 --> 01:35:31.540 in that area. 01:35:31.540 --> 01:35:33.820 So that road doesn't have any lights. 01:35:33.820 --> 01:35:37.320 Pavement is worn down. 01:35:37.320 --> 01:35:40.780 So we'll just have to give that road some attention. 01:35:40.780 --> 01:35:44.340 - Okay, well we can look and see if it's scheduled 01:35:44.340 --> 01:35:46.900 or planned as any part of any bond package 01:35:46.900 --> 01:35:48.540 or upcoming CIP. 01:35:48.540 --> 01:35:51.180 If not, we can work with Danny's. 01:35:51.180 --> 01:35:52.660 Okay, perfect. 01:35:52.660 --> 01:35:55.700 So what we'll do is bring back to you 01:35:55.700 --> 01:35:57.860 what phase of 2019 that's in 01:35:57.860 --> 01:36:00.960 and then also when that is scheduled 01:36:00.960 --> 01:36:02.140 and what the anticipation. 01:36:02.140 --> 01:36:04.480 So that'll be a very easy question to answer. 01:36:04.480 --> 01:36:10.500 Absolutely, we can do that. 01:36:10.500 --> 01:36:11.860 I don't have the map in front of me, 01:36:11.860 --> 01:36:13.980 but we all have this handy dandy PDF 01:36:13.980 --> 01:36:15.900 that we keep on our desktop 01:36:15.900 --> 01:36:17.340 so that we can answer those questions. 01:36:17.340 --> 01:36:19.500 So we absolutely can bring that back to you, no problem. 01:36:19.500 --> 01:36:20.700 That'll be very simple. 01:36:20.700 --> 01:36:24.220 - Councilmember McGuire, 01:36:24.220 --> 01:36:26.420 anything you want to add to the list? 01:36:26.420 --> 01:36:28.780 - I'm going over my long list of things 01:36:28.780 --> 01:36:29.920 that I'm thinking about, 01:36:29.920 --> 01:36:34.820 but I don't see anything currently that's relevant here. 01:36:34.820 --> 01:36:36.940 - I think we've done it. 01:36:36.940 --> 01:36:37.780 - Well, wonderful. 01:36:37.780 --> 01:36:38.620 Thank you very much. 01:36:38.620 --> 01:36:40.060 Well, we look forward to bringing back 01:36:40.060 --> 01:36:42.340 these future items to you 01:36:42.340 --> 01:36:44.420 and look forward to hearing from you 01:36:44.420 --> 01:36:46.240 about the Southeast Denton area. 01:36:46.240 --> 01:36:47.340 And then with that, 01:36:47.340 --> 01:36:49.580 I guess we're done with the staff report. 01:36:49.580 --> 01:36:51.940 - All right, thank you. - Thank you very much. 01:36:51.940 --> 01:36:53.700 - All that remains is concluding items. 01:36:53.700 --> 01:36:55.540 Does anyone have any concluding items? 01:36:55.540 --> 01:37:00.620 Seeing none, we are adjourned at 1039.