WEBVTT

00:00:00.000 --> 00:00:09.360
 Okay. Good morning and seeing that we have a quorum present, I welcome you to the December

00:00:09.360 --> 00:00:16.560
 16th, 2020 meeting of the mobility committee. First up under items for individual consideration

00:00:16.560 --> 00:00:24.280
 is approval of the minutes. I will entertain action. I'll move approval. I'll second.

00:00:24.280 --> 00:00:32.720
 It is moved and seconded. All in favor. Aye. Okay. Minutes are approved. Moving on to item

00:00:32.720 --> 00:00:37.440
 B. Receiver report, hold the discussion and give staff direction regarding updates from

00:00:37.440 --> 00:00:56.240
 the DCTA. Is DCTA here? Should we put this one off of it? Anyone know? Tracy's checking,

00:00:56.240 --> 00:01:03.120
 I think. I'm checking. She has not communicated. Well, let's move on to item C for the moment.

00:01:03.120 --> 00:01:09.680
 Hopefully we'll be able to circle back and get that update. So item C is receiver report,

00:01:09.680 --> 00:01:13.160
 hold the discussion and give staff direction regarding the city of Denton transportation

00:01:13.160 --> 00:01:18.920
 mobility project status report for the Denton area. And I understand that we do not have

00:01:18.920 --> 00:01:35.020
 our usual text. I'm supposed to with us, but Becky is incredibly prepared. I'm going to

00:01:35.020 --> 00:01:41.120
 ask Brian who's currently sitting at the city hall to pull up the presentation and I'm going

00:01:41.120 --> 00:01:47.120
 to do a brief overview of the items that are in the packet. If there are specific questions,

00:01:47.120 --> 00:01:55.360
 we will be prepared to get those over to Mr. Poulster. And so with that, you'll hear me

00:01:55.360 --> 00:02:01.560
 say next slide for Brian. So Brian, thank you for assisting me as I am remote also.

00:02:01.560 --> 00:02:08.840
 So Brian, next slide please. So today Mr. Poulster has prepared a packet. As you can

00:02:08.840 --> 00:02:14.440
 see here is kind of a project overall summary with different let dates, contractors associated

00:02:14.440 --> 00:02:23.520
 with the project and the construction cost. Next slide. And the FM 2181 project is currently

00:02:23.520 --> 00:02:28.640
 under construction. I think we're all aware that the city has utilities, water and wastewater

00:02:28.640 --> 00:02:33.400
 utilities that are being relocated. And the project is currently under construction with

00:02:33.400 --> 00:02:40.240
 Zachary Construction Company. And the overall construction completion date is currently

00:02:40.240 --> 00:02:50.600
 anticipated for November of 2021. Next slide please. Next slide. The US 377 Fort Worth

00:02:50.600 --> 00:02:56.420
 Drive project is also under construction. There were water and wastewater utility relocations

00:02:56.420 --> 00:03:01.820
 done as part of this project. And then the current construction completion date is February

00:03:01.820 --> 00:03:13.640
 of 2021. Next slide. Next slide. The next project is the I-35E Mayhill project. This

00:03:13.640 --> 00:03:20.400
 is a widening project in this area. And currently to date there are right away acquisitions that

00:03:20.400 --> 00:03:24.840
 are underway. And you can see from the packet there are several parcels that are still either

00:03:24.840 --> 00:03:32.240
 in the negotiation phase or possibly going through the eminent domain phase. And then

00:03:32.240 --> 00:03:38.360
 there are several parcels that are currently in possession of TxDOT. It does appear from

00:03:38.360 --> 00:03:45.600
 the packet that they're working through utility coordination with several different entities.

00:03:45.600 --> 00:03:50.620
 And currently it shows that that right away acquisition is anticipated to be completed

00:03:50.620 --> 00:03:58.440
 this month. The utility relocation is to be completed within April of 2020. And it appears

00:03:58.440 --> 00:04:02.480
 that they are going to be working forward to moving that project to construction in

00:04:02.480 --> 00:04:13.000
 June of 2022. Next slide please. This project is the US I-35E US 77 Dallas Drive Interim

00:04:13.000 --> 00:04:20.040
 Improvements. And the city is currently working with TxDOT in this area. And there's some

00:04:20.040 --> 00:04:27.480
 conversations that have been happening about the actual median opening or opening as you

00:04:27.480 --> 00:04:33.840
 exit off of 35 and get onto Dallas Drive. And so we're working through with TxDOT some

00:04:33.840 --> 00:04:39.480
 interim design and construction in this area. And working through what's the best solution

00:04:39.480 --> 00:04:45.320
 from this area. And it appears that that environmental clearance for this specific project is for

00:04:45.320 --> 00:04:51.800
 January 31st of 2012, which has been quite some time ago. So we will be working with

00:04:51.800 --> 00:04:57.200
 and have been working with TxDOT to work through what are the next steps to get some of these

00:04:57.200 --> 00:05:08.880
 interim phases executed. Next slide please. This project is the I-35, I-35E, I-35W Merge

00:05:08.880 --> 00:05:16.000
 project. As you can see from the graphic, this is basically the Y intersection where

00:05:16.000 --> 00:05:26.480
 35E and 35W come together all the way up to the 77 area north of Denton. Currently, the

00:05:26.480 --> 00:05:31.760
 schematic approval and environmental clearance phase has been completed. It does appear from

00:05:31.760 --> 00:05:38.400
 the information that they're working through right away acquisition, utility relocations

00:05:38.400 --> 00:05:45.240
 are anticipated to be completed in June of 2022. And the project appears to be anticipated

00:05:45.240 --> 00:05:52.100
 to start construction in January of 2023. You can see from the packet below, there are

00:05:52.100 --> 00:05:58.120
 several parcels that they're still working through the right away acquisition on. 60%

00:05:58.120 --> 00:06:04.720
 plans, which are considered plans adequate, were submitted, it appears in November, late

00:06:04.720 --> 00:06:11.000
 November. And TxDOT is working through and negotiating the design fees for the Windsor

00:06:11.000 --> 00:06:18.520
 interchange and that preliminary design of how Windsor Drive itself will interchange with

00:06:18.520 --> 00:06:30.440
 the 35. Next slide please. So I-35 north, segments one and two is the next packet project

00:06:30.440 --> 00:06:36.320
 that you see. It appears that they're working through right away acquisition. And there

00:06:36.320 --> 00:06:41.360
 are several parcels as you can see there that are still in negotiation phase, some that

00:06:41.360 --> 00:06:47.080
 are working through M&A domain and several that are already in possession. It does appear

00:06:47.080 --> 00:06:51.800
 from the packet that they're hoping to have the right away acquisition completed in March

00:06:51.800 --> 00:07:01.920
 of 2021. 100% plans ready for November of 2021 with a December 2022 let date. Next slide

00:07:01.920 --> 00:07:10.240
 please. This project is specific to the I-35W main lanes. And this project is still moving

00:07:10.240 --> 00:07:17.800
 through kind of that environmental clearance phase, schematic phase. The 95% schematic

00:07:17.800 --> 00:07:23.480
 is at the design division currently for review according to the packet information. And this

00:07:23.480 --> 00:07:26.720
 will be one that'll be moving through kind of the process. It's still in the beginning

00:07:26.720 --> 00:07:36.840
 phases according to the information. Next slide. The I-35W frontage road project, TxDOT

00:07:36.840 --> 00:07:43.880
 is currently working through and negotiating for the plans, the schematics and the environmental

00:07:43.880 --> 00:07:50.760
 efforts with HNTB. And they're evaluating the priority project to do what they're possibly

00:07:50.760 --> 00:07:55.600
 are looking into as breakout segments, which would require different portions of the project

00:07:55.600 --> 00:08:01.240
 to be done in different phases. Currently from the packet information, you can see they're

00:08:01.240 --> 00:08:07.440
 working on right away acquisition to be completed in December of 2021, utility relocations to

00:08:07.440 --> 00:08:15.540
 be completed in September of 2023. And it shows the ready to let date of September 2023.

00:08:15.540 --> 00:08:21.760
 They have requested a letter of support from the city and the city has provided that information.

00:08:21.760 --> 00:08:32.800
 So next slide please. The next project is the U.S. 380/U.S. 77 project. And this project

00:08:32.800 --> 00:08:38.960
 is specifically the city's portion of the project is sidewalks in this area. It was

00:08:38.960 --> 00:08:45.520
 awarded to Regal Construction. And that's really the major impact from the city perspective

00:08:45.520 --> 00:08:51.680
 is just the sidewalks itself. And so that project construction is anticipated to start

00:08:51.680 --> 00:09:03.080
 here next month. Next slide please. And the 380 East project. This is specifically a project

00:09:03.080 --> 00:09:08.720
 that looks from the information that they're still working through utility coordination.

00:09:08.720 --> 00:09:15.060
 And it appears that they plan to let this project in May of 2021. And the city currently

00:09:15.060 --> 00:09:20.800
 does not have facilities in this area that are directly impacted, but will make adjustments

00:09:20.800 --> 00:09:27.880
 as needed. And this is specific to the 380 portion from U.S. 377 to the county, I'm sorry,

00:09:27.880 --> 00:09:35.240
 the Collin County line, which is not specifically in the area of which Denton has facilities.

00:09:35.240 --> 00:09:44.880
 Next slide please. Next slide. The loop 288 West project. This project is a project that

00:09:44.880 --> 00:09:51.280
 Denton County is working to begin negotiations with Chank Patel and Yerby for the P.S. and

00:09:51.280 --> 00:09:57.400
 East. Currently the project is showing a right away acquisition completion date of December

00:09:57.400 --> 00:10:06.480
 of 2024. 100% plans appear to be anticipated for June of 2022 and are ready to let date

00:10:06.480 --> 00:10:18.640
 of April of 2026. Next slide please. The FN1515 project, it appears from the information provided

00:10:18.640 --> 00:10:25.280
 that Denton County is currently working with negotiations with LTRA for the P.S. and East.

00:10:25.280 --> 00:10:30.840
 And it appears that the information shows they're working through the right away acquisition.

00:10:30.840 --> 00:10:37.600
 They're hoping to have that completed in January of 2022 with utility relocations completed

00:10:37.600 --> 00:10:44.440
 in December of 2022. And they're ready to let date shows of December of 2022 also to

00:10:44.440 --> 00:10:53.440
 begin that project. Next slide please. The 1173 project, I understand there's been some

00:10:53.440 --> 00:10:59.160
 environmental improvements that are continuing. There was a virtual public hearing that's

00:10:59.160 --> 00:11:06.960
 currently available on the Keep it Moving Dallas website that you see in the packet.

00:11:06.960 --> 00:11:13.160
 And right away mapping is continuing with currently it shows 60 parcels. And that project

00:11:13.160 --> 00:11:22.840
 shows a ready to let date of December of 2023. Next slide. This project is currently also

00:11:22.840 --> 00:11:30.120
 the integrated corridor. It is going through what we call the U.S. 380 feasibility study.

00:11:30.120 --> 00:11:36.640
 You might have seen this information on the city website being able to allow and let individuals

00:11:36.640 --> 00:11:41.640
 know that a public meeting has been scheduled. And this is really a public meeting period

00:11:41.640 --> 00:11:50.560
 of which you can do online comment. That is from December 2nd up until this Thursday which

00:11:50.560 --> 00:12:00.040
 is December 17th. So at the www.keepitmovingdallas.com-U.S. 380 Denton PM2 you can leave your comments

00:12:00.040 --> 00:12:10.480
 specific to the integrated corridor 380 feasibility study project. Next slide. The Bonnie Bray

00:12:10.480 --> 00:12:18.120
 Phase 6 project is currently working through its design phase. And there are no additional

00:12:18.120 --> 00:12:22.960
 updates on this project at this time. It's just working through kind of that design phase

00:12:22.960 --> 00:12:28.520
 and working through and coordinating with the high school opening. And basically there's

00:12:28.520 --> 00:12:33.120
 a lot of easement acquisition that's currently working on and going through the process right

00:12:33.120 --> 00:12:43.720
 now. Next slide. Bonnie Bray Phase 7. That is specific to a project that was working

00:12:43.720 --> 00:12:48.680
 through with the city. We have worked with TxDOT and they have requested a lot of the

00:12:48.680 --> 00:12:53.760
 schematic design that was put together for this area. And that project is now being handled

00:12:53.760 --> 00:13:03.160
 through TxDOT. Next slide. The Mayhill Roadway project, as you can see from the graph, the

00:13:03.160 --> 00:13:09.360
 Phase 1 construction is complete. And the city is currently working through the design

00:13:09.360 --> 00:13:16.160
 phase for Phase 2. And that project is currently underway with the in-house capital projects

00:13:16.160 --> 00:13:24.520
 division. Next slide. The McKinney Street project is currently under construction. Phase

00:13:24.520 --> 00:13:30.520
 1 is completed and Phase 2 is currently under construction along with the intersection of

00:13:30.520 --> 00:13:37.360
 the McKinney and Mayhill area. And that project is currently being managed by the capital

00:13:37.360 --> 00:13:45.680
 projects division. Next slide. Hickory Creek Road. I think we can skip currently the project

00:13:45.680 --> 00:13:54.360
 of Phase 1 and 2 is under construction and Phase 3 is under design. And you can go on.

00:13:54.360 --> 00:13:59.080
 And I think that's it, Brian. That's just kind of a summary of terms. So with that,

00:13:59.080 --> 00:14:05.360
 I will answer any questions that anybody might have. I'll do the best I can and anything

00:14:05.360 --> 00:14:10.620
 that I can't answer, I absolutely will work with Mr. Polster. I'm sure he would have had

00:14:10.620 --> 00:14:14.760
 a lot more information to provide to you. And that was really just kind of a high-level

00:14:14.760 --> 00:14:20.600
 overview of the information in the packet. And then like Council Member Meltzer mentioned,

00:14:20.600 --> 00:14:25.440
 Mr. Polster is not feeling well today. So we're happy to provide that information. The packet's

00:14:25.440 --> 00:14:30.560
 also included on the city's website. So with that, I'll entertain any questions that you

00:14:30.560 --> 00:14:43.200
 might have. Council Members? I have a question that you all don't. I have two. Council Member

00:14:43.200 --> 00:14:48.440
 Briggs has a question. Yes, ma'am. Change the way this thing is displayed. Go ahead.

00:14:48.440 --> 00:14:53.640
 Thank you, Chair. Just two questions. On the Loop 288 project, I know that we've talked

00:14:53.640 --> 00:14:59.560
 about that as a whole, but there were some other projects on that regarding frontage

00:14:59.560 --> 00:15:08.400
 roads that we were discussing that were going to come in first. Is there an update on that

00:15:08.400 --> 00:15:15.040
 aspect of it? Yes, ma'am. You probably will recall the city did a letter of support for

00:15:15.040 --> 00:15:21.240
 the Loop 288 West project. And so what currently is happening with that is TxDOT is working

00:15:21.240 --> 00:15:27.640
 through, working to get that consultant on board to work on kind of that design and then

00:15:27.640 --> 00:15:33.880
 look at specifically if there's areas that need to be done in advance of other areas.

00:15:33.880 --> 00:15:39.560
 Currently, it appears in the way that the project's being planned is that those northbound

00:15:39.560 --> 00:15:45.480
 frontage roads will be done first. And so that's the current update at this time is

00:15:45.480 --> 00:15:50.160
 they're working through kind of that next step phase with right-of-way acquisition and

00:15:50.160 --> 00:15:56.400
 moving forward into design. Okay. Just a real quick follow-up, and you may not know, but

00:15:56.400 --> 00:16:03.040
 it would be helpful. The timing of those frontage roads as compared to the full project, I think

00:16:03.040 --> 00:16:08.960
 we saw 2024 as like the loop. So, and I know that the frontage roads we were looking forward

00:16:08.960 --> 00:16:14.760
 to go ahead and get done sooner. So is that whatever that date that is, that would be

00:16:14.760 --> 00:16:21.960
 helpful to know? Absolutely. Sure. We can work with Mr. Poulster and get that type of information.

00:16:21.960 --> 00:16:28.840
 The next question, Chair, I know that on 380 there's the sign flashing, work is about to

00:16:28.840 --> 00:16:36.280
 begin, and I've seen some comments. People are really nervous about what that means.

00:16:36.280 --> 00:16:42.660
 Do you know what the work plan is and what we can expect? Will the one lane be shut down

00:16:42.660 --> 00:16:50.200
 both ways or do we have any idea we can put out ahead for people to expect? And are you

00:16:50.200 --> 00:16:58.700
 talking specifically about east of town? Uh-huh. Yes, ma'am. Absolutely. I can get that information

00:16:58.700 --> 00:17:05.200
 from TxDOT so that we can find out exactly what their, you know, what their traffic control

00:17:05.200 --> 00:17:10.600
 plan is in that specific area so that residents can be aware, and we can work on trying to

00:17:10.600 --> 00:17:15.040
 put that information kind of out on the website and, you know, to our social media front so

00:17:15.040 --> 00:17:19.400
 we can share that information. I have not seen that traffic control plan specifically,

00:17:19.400 --> 00:17:24.480
 so I can't answer that question, but we can work to get that information out to basically

00:17:24.480 --> 00:17:29.160
 educate and allow residents and citizens to know, you know, how that will impact their

00:17:29.160 --> 00:17:33.520
 day-to-day operations. Okay. Thank you so much. No problem.

00:17:33.520 --> 00:17:42.600
 That's one for Ryan. Thank you, Chair. Yeah, I've got a couple of questions. The first

00:17:42.600 --> 00:17:49.680
 one is on 377 regarding the railroad bridge. If they have any ETA on when they might be

00:17:49.680 --> 00:17:54.800
 starting to set that since the project's only two months from completion, and they haven't

00:17:54.800 --> 00:17:58.000
 brought that up at all as far as the dates, and that's probably something that'll have

00:17:58.000 --> 00:18:03.040
 to go back to TxDOT, if I would imagine. Yes, sir. I will work to get an answer on that.

00:18:03.040 --> 00:18:07.000
 I don't have an answer for that. Okay. Because it would make sense that they would set the

00:18:07.000 --> 00:18:13.480
 portion over the southbound roads before they open that. Then the other one is on projects

00:18:13.480 --> 00:18:20.800
 that aren't on here, specifically Bonnie Bray phases three and four. I know we've got the

00:18:20.800 --> 00:18:25.940
 waterline project going in under phase three right now, but that doesn't seem to be having

00:18:25.940 --> 00:18:31.040
 any momentum, and I'm wondering if there's any issues going on on that that we should

00:18:31.040 --> 00:18:34.600
 be made aware of, because I've seen one track that has been sitting in the exact same spot

00:18:34.600 --> 00:18:42.360
 for about three months. Yes, sir. Those two projects specifically are not related to the

00:18:42.360 --> 00:18:48.280
 report that Mr. Polster puts together. Those aren't considered to be a part of his mobility

00:18:48.280 --> 00:18:55.160
 report for an on-system report. We are currently working through with the contractor on that

00:18:55.160 --> 00:19:01.800
 waterline project some concerns and issues that we have with that project specifically,

00:19:01.800 --> 00:19:05.240
 and we're working through those currently, and as soon as there's more information that

00:19:05.240 --> 00:19:09.160
 can be provided, we will absolutely provide that update.

00:19:09.160 --> 00:19:12.840
 All right. Thank you. No problem, sir.

00:19:12.840 --> 00:19:18.640
 Can I have a few questions? Forgive me if you addressed this while I was just in my

00:19:18.640 --> 00:19:27.080
 interface, but my question is regarding whether there's any insight on any possibility of

00:19:27.080 --> 00:19:33.160
 temporarily addressing the issue, and I think I might have heard you say something about

00:19:33.160 --> 00:19:44.120
 the issue of the exit off of 35 onto 380 prior to the larger TxDOT project there, where we

00:19:44.120 --> 00:19:52.720
 identified it as a dangerous and grievous area. Sure. Yes, sir. So specifically where

00:19:52.720 --> 00:20:00.600
 35E and 35W come together at that Y intersection and near that intersection of the 380 exit,

00:20:00.600 --> 00:20:06.440
 we have been in talks with TxDOT. We did have a meeting with them a few weeks back, and

00:20:06.440 --> 00:20:12.720
 we have been collecting data for a traffic study, and that data we have received, so

00:20:12.720 --> 00:20:17.520
 now we're working through that analysis phase. Once that information is collected, we'll

00:20:17.520 --> 00:20:21.080
 then send that information over to TxDOT, and so we're just working through kind of

00:20:21.080 --> 00:20:27.480
 a step process. The city and TxDOT are working in a collaboration partnership to see if there's

00:20:27.480 --> 00:20:32.960
 some temporary measures that can be done in advance of the construction project, knowing

00:20:32.960 --> 00:20:37.560
 that that time frame's a little bit further out, and so we are working through those steps.

00:20:37.560 --> 00:20:41.920
 So at this point, and we're just going through that cycle of collecting the data, working

00:20:41.920 --> 00:20:47.120
 through that study, and then going through the analysis phase to see what measures can

00:20:47.120 --> 00:20:51.680
 be taken. There are several different options that we've discussed with TxDOT and Dallas

00:20:51.680 --> 00:20:58.280
 District just a couple weeks back. So we'll continue to provide updates as those are available.

00:20:58.280 --> 00:21:04.880
 Would you mind giving even sort of flavor of kinds of things that might be under consideration?

00:21:04.880 --> 00:21:10.600
 Sure. There were several different things that were kind of talked about in that area,

00:21:10.600 --> 00:21:17.880
 and really specifically, you know, some of those things are changing the entrance and

00:21:17.880 --> 00:21:24.320
 exit ramp. So at Oak Street, after you go through that intersection, you can enter Oak Street,

00:21:24.320 --> 00:21:28.600
 from Oak Street onto the highway immediately. And so we've talked about kind of flipping

00:21:28.600 --> 00:21:34.360
 those two ramps. So the 380 exit, you will get off sooner when you're traveling northbound,

00:21:34.360 --> 00:21:38.960
 and the Oak Street exit could come onto the highway sooner, or I'm sorry, after that.

00:21:38.960 --> 00:21:43.520
 So just really kind of taking those two entrants and exit ramps and flipping those. And the

00:21:43.520 --> 00:21:47.800
 other thing that's been mentioned, and there are several different things, but the other

00:21:47.800 --> 00:21:53.880
 thing that's been looked at specifically is, you know, flipping where the 380 exit ramp

00:21:53.880 --> 00:21:59.320
 will be sooner, but then keeping that Oak Street traffic and the frontage road traffic

00:21:59.320 --> 00:22:04.400
 working through the intersection at 380, maybe making some modifications to the intersection

00:22:04.400 --> 00:22:12.040
 at 380 and taking that traffic northbound to then enter north of the 380 and 35 interchange

00:22:12.040 --> 00:22:16.720
 in that area. So there's several different options that are being looked at. And based

00:22:16.720 --> 00:22:21.200
 on the traffic study and that information, we'll then work with TxDOT as to what, you

00:22:21.200 --> 00:22:26.160
 know, is the best solution for that and whether, you know, that's something that they can handle

00:22:26.160 --> 00:22:30.080
 through kind of some of their maintenance type contracts and do some temporary measures

00:22:30.080 --> 00:22:35.000
 in advance of the major project that won't happen for a few years.

00:22:35.000 --> 00:22:41.080
 Is the point of the traffic study to determine kind of where, what the pinch point is, whether

00:22:41.080 --> 00:22:47.480
 it's coming from, whether it's coming from exiting off of 35 or, you know, what is it

00:22:47.480 --> 00:22:50.280
 that you're trying to determine in the traffic study?

00:22:50.280 --> 00:22:55.120
 Sure. We're just basically looking at that overall area, trying to decide and figure

00:22:55.120 --> 00:23:02.280
 out exactly where traffic is coming from and whether traffic is using the service road.

00:23:02.280 --> 00:23:07.120
 And that will help make the determinations as to how many cars are going through a particular

00:23:07.120 --> 00:23:12.520
 area. The traffic study specifically was related to that Oak Street interchange and then working

00:23:12.520 --> 00:23:18.280
 through what are measures that could be taken to take traffic off 35 sooner onto that frontage

00:23:18.280 --> 00:23:24.280
 road area. So that specific information then will help an overall analysis of that entire

00:23:24.280 --> 00:23:28.960
 area from really 380 to Oak Street. And we'll be working through those with TxDOT.

00:23:28.960 --> 00:23:35.120
 Great. I really think all the extra attention is merited. Related to that, can you remind

00:23:35.120 --> 00:23:43.280
 us what the timing is on the TxDOT project with the Y versus the completion of the widening

00:23:43.280 --> 00:23:48.280
 of Bonnie Bray? Because they're really related, right? The idea would be to have Bonnie Bray

00:23:48.280 --> 00:23:58.960
 as an operating full capacity bypass while work is going on. So are we back to function

00:23:58.960 --> 00:23:59.960
 that way?

00:23:59.960 --> 00:24:09.080
 Sure. So really, the TxDOT 35E, 35W merge, the current let date for that project is January

00:24:09.080 --> 00:24:17.120
 of 2023. So the specific dates related to the quarter of which that Bonnie Bray phase,

00:24:17.120 --> 00:24:22.240
 we're working through all of those options. But I would tell you at this point, it's very

00:24:22.240 --> 00:24:29.360
 apparent that if that area is within a construction timeframe that other individuals, residents,

00:24:29.360 --> 00:24:35.160
 citizens will be wanting to use Bonnie Bray as an alternate route, specifically if that

00:24:35.160 --> 00:24:39.160
 area is under construction. So we're still working through kind of the timing of that

00:24:39.160 --> 00:24:45.840
 intersection. TxDOT currently tells us that they plan to let within the January 2023 timeframe.

00:24:45.840 --> 00:24:51.560
 And so we're working through when Bonnie Bray construction will happen in that area. So those

00:24:51.560 --> 00:24:55.520
 specific dates are still kind of something that we're working through, but we are absolutely

00:24:55.520 --> 00:24:59.360
 coordinating because we do understand. And I think that's what you're really kind of

00:24:59.360 --> 00:25:04.200
 thinking also from your question is Bonnie Bray would be used as an alternate route.

00:25:04.200 --> 00:25:06.520
 So we're working through the timing of that project particularly.

00:25:06.520 --> 00:25:12.880
 Well, I think the TxDOT funding, just to put that up, the TxDOT funding on Bonnie Bray

00:25:12.880 --> 00:25:16.800
 says that that's how they're thinking of it too. And sort of the worst possible scenario

00:25:16.800 --> 00:25:21.400
 is not pinning that one down and having them both under construction at the same time.

00:25:21.400 --> 00:25:22.400
 Council Member Briggs.

00:25:22.400 --> 00:25:29.560
 Yeah, thank you, Chair. Just to follow up your question about 380 and 35 has sparked

00:25:29.560 --> 00:25:33.360
 another question for me. I appreciate you asking about that. I know it's really important

00:25:33.360 --> 00:25:41.540
 to the community. So when you mentioned TxDOT, their maintenance contracts, was that your

00:25:41.540 --> 00:25:48.360
 way of saying that that's the way they're looking to fund it? Or would the city need

00:25:48.360 --> 00:25:57.320
 to offer matching or how would that be funded? Because I know it's extremely important and

00:25:57.320 --> 00:26:02.960
 it would be a priority for us to fix that intersection. So when you mentioned maintenance

00:26:02.960 --> 00:26:11.880
 contracts, is that where they're looking to kind of fit those projects in? But sure, I

00:26:11.880 --> 00:26:17.600
 don't think all those decisions have completely been made exactly how the funding is a TxDOT

00:26:17.600 --> 00:26:25.080
 roadway and TxDOT will have to look through how their funding will be done. I know maintenance

00:26:25.080 --> 00:26:29.560
 funding is something that has been mentioned. And so really, that's a TxDOT decision as

00:26:29.560 --> 00:26:34.440
 to how they're going to fund that particular project. At this time, what they've asked

00:26:34.440 --> 00:26:39.640
 the city and what our relationship is in the collaboration of trying to find a solution,

00:26:39.640 --> 00:26:46.000
 an interim solution to this situation before the permanent solution of the roadway construction

00:26:46.000 --> 00:26:51.600
 happens is to work through that study, that analysis, then work with the TxDOT folks to

00:26:51.600 --> 00:26:56.000
 find out what the solution is. But currently at this time, the funding is not something

00:26:56.000 --> 00:27:02.280
 that's been completely discussed or decided upon. Although I did mention that TxDOT has

00:27:02.280 --> 00:27:06.800
 looked into and is looking at different things that can be done, whether it's from their

00:27:06.800 --> 00:27:11.920
 maintenance funding or some advanced type of funding that needs to be done to fix that

00:27:11.920 --> 00:27:16.320
 area. But at this time, those specific decisions have not been made. They're still waiting

00:27:16.320 --> 00:27:20.920
 on the data collection, which we're still in that process. And then from there, they'll

00:27:20.920 --> 00:27:26.360
 work through what the solution is and then how it will be funded.

00:27:26.360 --> 00:27:29.880
 Okay. I just mentioned that because it always helps to have funding and know where that's

00:27:29.880 --> 00:27:33.080
 coming from to get a project completed.

00:27:33.080 --> 00:27:38.120
 Sure. Absolutely. And those decisions haven't been made at this time, but you're very much

00:27:38.120 --> 00:27:42.400
 correct that it will take money to make anything happen in that area. So yes, thank you for

00:27:42.400 --> 00:27:43.400
 bringing that up.

00:27:43.400 --> 00:27:55.400
 Now, may I ask you a question regarding Locust Street 77, TxDOT for now. I just want to relate

00:27:55.400 --> 00:28:04.300
 in an incident and give you an opportunity to give me some context. So I speak with a

00:28:04.300 --> 00:28:10.200
 constituent and I brought it up in the context of how it was recently resurfaced as part

00:28:10.200 --> 00:28:17.720
 of an arrangement for TxDOT to put it in good shape before it converts over to city ownership.

00:28:17.720 --> 00:28:28.040
 And this ordinarily very well informed constituent said, "Yeah, we're supposedly going to redo

00:28:28.040 --> 00:28:35.800
 a lot of infrastructure under there, pipes under there." And that seemed to have been

00:28:35.800 --> 00:28:40.080
 totally dropped in that it was a surprise to the city that they went ahead and covered

00:28:40.080 --> 00:28:47.320
 it. I blanched, I had no way to respond to that. I don't recall hearing that something

00:28:47.320 --> 00:28:51.240
 happened that we didn't expect to happen. I would be very surprised if that were the

00:28:51.240 --> 00:28:58.880
 case, but can you provide any context on the sequence of events of needed infrastructure

00:28:58.880 --> 00:29:03.600
 work under Locust Street and resurfacing of Locust Street? I see Council Member Briggs

00:29:03.600 --> 00:29:10.200
 would like to add something as well. Sure, Council Member Briggs.

00:29:10.200 --> 00:29:16.800
 I was just going to mention that that is the case. It is a long section of road and there

00:29:16.800 --> 00:29:26.360
 is a section that isn't the case for, but there is a section that it is true, that it

00:29:26.360 --> 00:29:33.480
 will have to be pulled up and redone in the future. I remember when Mr. Estes was here,

00:29:33.480 --> 00:29:43.280
 he provided a map or a chart of that road for us and it showed which sections that issue

00:29:43.280 --> 00:29:47.880
 related to. Care to confirm?

00:29:47.880 --> 00:29:54.880
 Sure. Absolutely. I wanted to give Council Member Briggs an opportunity to finish her

00:29:54.880 --> 00:30:00.840
 statement. There is a project currently that TxDOT is working on for sidewalks in that

00:30:00.840 --> 00:30:05.000
 area. If you have driven in that area, you will notice there are a lot of new sidewalks

00:30:05.000 --> 00:30:12.800
 along both Elm and Locust. There are projects associated with the utility infrastructure

00:30:12.800 --> 00:30:17.640
 that still needs to be completed in that area and at that time, we will be working with

00:30:17.640 --> 00:30:26.480
 TxDOT for that resurfacing. There are basically this section from really north of the courthouse

00:30:26.480 --> 00:30:32.280
 all the way to 380. There is utility infrastructure, whether it be water, wastewater, or drainage

00:30:32.280 --> 00:30:39.640
 infrastructure that needs to be constructed in that area and TxDOT did resurface in some

00:30:39.640 --> 00:30:48.280
 of that area in advance of that utility reconstruction. There will be a relationship of where we will

00:30:48.280 --> 00:30:54.000
 have to have TxDOT go back through and we are still working through those specifics

00:30:54.000 --> 00:30:58.600
 where that roadway will have to be resurfaced after those utility improvements are made,

00:30:58.600 --> 00:31:04.520
 because you are correct, those utility improvements were not made in advance of that roadway construction.

00:31:04.520 --> 00:31:10.720
 It was a resurfacing of that roadway that TxDOT had planned and executed.

00:31:10.720 --> 00:31:16.760
 Did that make sense from our perspective to do it in that sequence?

00:31:16.760 --> 00:31:20.680
 Really we would love to have the opportunity to get those utilities replaced in advance

00:31:20.680 --> 00:31:26.240
 of that. That was not the opportunity that was presented at this time and do some coordination

00:31:26.240 --> 00:31:32.240
 issues but we will work through that with TxDOT and TxDOT is aware and happy to work

00:31:32.240 --> 00:31:36.880
 through that whole situation with us to allow us to get those infrastructure replaced in

00:31:36.880 --> 00:31:37.880
 that area.

00:31:37.880 --> 00:31:46.960
 Okay, see it leaves me with not a great answer to the constituent. Did we have control over

00:31:46.960 --> 00:31:47.960
 the sequence?

00:31:47.960 --> 00:31:54.920
 No, sir, that is a TxDOT roadway. We work with them to coordinate those opportunities

00:31:54.920 --> 00:32:00.840
 to replace that infrastructure in advance but that is not what happened at this time.

00:32:00.840 --> 00:32:05.640
 There was a coordination issue between the utilities that needed to be replaced along

00:32:05.640 --> 00:32:11.160
 with the storm drain in that area and the resurfacing of that roadway. TxDOT is aware

00:32:11.160 --> 00:32:16.080
 that those utilities do need to be replaced in advance of that roadway.

00:32:16.080 --> 00:32:21.080
 This happened before your tenure, right? This would never happen under DeVine administration.

00:32:21.080 --> 00:32:27.240
 Yes, sir, this did happen before my tenure but I will just tell you that we will work

00:32:27.240 --> 00:32:32.720
 to collaborate as best as we can and we have had those conversations with TxDOT and they

00:32:32.720 --> 00:32:36.400
 are aware that the infrastructure does need to be replaced and are going to coordinate

00:32:36.400 --> 00:32:38.800
 with us the roadway resurfacing.

00:32:38.800 --> 00:32:46.800
 Okay, thanks for fielding that. Anything else on this? All right, thank you for covering.

00:32:46.800 --> 00:32:52.000
 No problem and we will get answers to those other questions that you had too. I appreciate

00:32:52.000 --> 00:32:53.880
 all the questions.

00:32:53.880 --> 00:33:01.120
 All right. I see nobody else pop up on the screen here. I am going to move ahead to item

00:33:01.120 --> 00:33:05.880
 D, staff update regarding hickory bike lane bollard spacing, highway safety improvement

00:33:05.880 --> 00:33:12.480
 program status, mobility plan status and next steps, 88 bike position update, hallway crossing

00:33:12.480 --> 00:33:14.640
 diagonal ramps and markings.

00:33:14.640 --> 00:33:23.640
 Thank you, chair and members of the committee. Brian Yon, traffic engineer. Let me call up

00:33:23.640 --> 00:33:24.640
 presentation.

00:33:24.640 --> 00:33:40.640
 How about we will take questions sort of after each item? That's all right?

00:33:40.640 --> 00:33:52.800
 Something is locked, okay. Totally locked up.

00:33:52.800 --> 00:33:56.240
 I know how that is. When you are interacting with the technology, it's hard to also --

00:33:56.240 --> 00:33:59.840
 I've got this giant screen of my presentation, but I --

00:33:59.840 --> 00:34:09.120
 You want me to smack it for you?

00:34:09.120 --> 00:34:18.200
 Well -- okay. You all can't see it yet either, can you?

00:34:18.200 --> 00:34:19.200
 Not yet.

00:34:19.200 --> 00:34:20.200
 Okay.

00:34:20.200 --> 00:34:24.760
 Did Nicole ever pop in for her update?

00:34:24.760 --> 00:34:27.280
 Do we know?

00:34:27.280 --> 00:34:31.160
 I'm seeing a blank -- oh, there she is.

00:34:31.160 --> 00:34:36.240
 Yeah, I am here. I joined at like 9.02. You all are quite speedy today.

00:34:36.240 --> 00:34:41.400
 Oh, well, you know, tick, tick. We've all got to -- all right. Well, then while Brian

00:34:41.400 --> 00:34:46.960
 Wiley puts to that, we'll go ahead and handle item D, which is receive a report, hold a

00:34:46.960 --> 00:34:50.120
 discussion and give staff direction regarding updates from the DCTA.

00:34:50.120 --> 00:34:51.120
 You're welcome.

00:34:51.120 --> 00:34:52.560
 Thank you. Happy holidays.

00:34:52.560 --> 00:34:53.560
 You too.

00:34:53.560 --> 00:35:01.240
 I do have some exciting updates to share today. We have been working on what we are calling

00:35:01.240 --> 00:35:08.600
 the DCTA priority actions, and so we've got some really big projects on the docket right

00:35:08.600 --> 00:35:14.760
 now. We just concluded task order number one with Accenture for the purpose of the Transformation

00:35:14.760 --> 00:35:21.800
 Initiative, where the contractor or the consultants came in and kind of did a full-body scan

00:35:21.800 --> 00:35:28.240
 of DCTA to determine where we were most efficient, where we were inefficient, and some recommendations

00:35:28.240 --> 00:35:35.440
 for a path forward. So at last week's board meeting, the board did approve a list of priority

00:35:35.440 --> 00:35:41.520
 projects. There were 30 projects in total that are slated for the next five years for

00:35:41.520 --> 00:35:49.360
 the agency, and so we're really excited about that. One of the top five projects was doing

00:35:49.360 --> 00:35:56.720
 an -- bringing in some on-demand service providers to look at where we could make service more

00:35:56.720 --> 00:36:02.080
 efficient, perhaps increase ridership and look at maybe more areas within the three

00:36:02.080 --> 00:36:11.000
 member cities to serve. So we have had an open procurement since -- oh, gosh, the summer,

00:36:11.000 --> 00:36:16.000
 where the board selected two providers, so VIA is one of them, and then a combination

00:36:16.000 --> 00:36:21.760
 of Spare and Lyft is the second provider. And so we have been in coordination with both

00:36:21.760 --> 00:36:28.560
 of those service providers to put together proposals for on-demand service. So at last

00:36:28.560 --> 00:36:36.920
 week's DCTA board meeting, the board did kind of all agree that they would like to see proposals

00:36:36.920 --> 00:36:44.440
 where the majority of fixed routes were removed, and we became primarily an on-demand provider.

00:36:44.440 --> 00:36:51.200
 And so really DCTA being a broker of services. So at this point, based on board direction,

00:36:51.200 --> 00:36:57.880
 specifically in Denton, we would be retaining the UNT routes, and then we would be retaining

00:36:57.880 --> 00:37:04.680
 route three and route seven for a period of time, but really layering on-demand on top

00:37:04.680 --> 00:37:09.480
 of three and seven, so that we can look at data that's provided by the on-demand providers

00:37:09.480 --> 00:37:17.000
 to see is fixed route really the answer in those areas, which staff feels like it is,

00:37:17.000 --> 00:37:24.880
 but looking at on-demand kind of to serve the rest of the city. And Lewisville, respectively,

00:37:24.880 --> 00:37:30.160
 removing routes 21 and 22 and having full on-demand in that city. And we already have

00:37:30.160 --> 00:37:35.960
 a non-demand service in the city of Highland Village. So it's a pretty big change that

00:37:35.960 --> 00:37:41.640
 we're looking at. We plan to have those proposals back and to review them with our board at

00:37:41.640 --> 00:37:49.560
 our January 28th meeting. At that point, the board would provide their insight and their

00:37:49.560 --> 00:37:53.640
 recommendation on which vendor they would like to move forward with. And then we would

00:37:53.640 --> 00:37:58.120
 have in-depth meetings with the vendor, as well as each of the member cities to go through

00:37:58.120 --> 00:38:02.600
 a service plan for the respective city in detail to make sure that we're getting any

00:38:02.600 --> 00:38:07.600
 insight and feedback directly from not just the city's representative on our board, but

00:38:07.600 --> 00:38:15.720
 also city staff. Most likely, we're probably looking at like the May, June, July timeframe

00:38:15.720 --> 00:38:21.080
 for actually launching a service of this type. But that transition plan would be part of

00:38:21.080 --> 00:38:27.680
 that proposal review and those roundtable meetings as well. But with the amount of public

00:38:27.680 --> 00:38:34.600
 involvement that will be required by the FTA due to the actual removal of routes, there's

00:38:34.600 --> 00:38:39.520
 quite a bit of a lead time in order to make a transition like that happen. So it's a pretty

00:38:39.520 --> 00:38:47.960
 big change and a major priority for DCTA. With that on the horizon, we are aware that

00:38:47.960 --> 00:38:52.600
 obviously the number of fixed routes would become much smaller and then the amount of

00:38:52.600 --> 00:39:00.440
 on-demand service would become much larger. So our board has approved the CEO to sign

00:39:00.440 --> 00:39:06.120
 a letter of intent and Trinity Metro did the same thing. And DCTA and Trinity Metro were

00:39:06.120 --> 00:39:12.600
 working together to see how we could leverage Trinity Metro's technologies and their managerial

00:39:12.600 --> 00:39:18.240
 oversight in order to operate those remaining fixed route services. So we are currently

00:39:18.240 --> 00:39:24.360
 in the exploration process, but we anticipate there being some sort of partnership and an

00:39:24.360 --> 00:39:31.200
 alignment with the timing on the transition away from fixed route and to on-demand with

00:39:31.200 --> 00:39:37.640
 Trinity Metro assisting us in managing the fixed route components as well as the ADA

00:39:37.640 --> 00:39:44.120
 paratransit services. So DCTA would retain the direct management of all of the on-demand

00:39:44.120 --> 00:39:50.120
 services in our member cities and contract cities, but we would basically partner with

00:39:50.120 --> 00:39:58.040
 Trinity Metro and leverage their technologies to operate those remaining fixed routes. Again,

00:39:58.040 --> 00:40:05.720
 pretty big change. With regionalism in mind, we are also partnering with DART. So both

00:40:05.720 --> 00:40:15.120
 DCTA and DART signed a letter of intent. They are looking at potentially sharing some rail

00:40:15.120 --> 00:40:23.800
 resources in order to explore and kind of plan an opportunity for joint rail operations

00:40:23.800 --> 00:40:31.760
 in a maintenance facility. So we have the land. Our A train line connects to the DART

00:40:31.760 --> 00:40:38.520
 green line. And so there are some cost efficiencies for both agencies in regard to kind of leveraging

00:40:38.520 --> 00:40:44.400
 that space. And so there is a letter of intent that's been jointly signed by both agencies,

00:40:44.400 --> 00:40:52.840
 but we are right now in the exploration phase of kind of what that would look like. So more

00:40:52.840 --> 00:41:01.440
 to come, but lots of regionalism in mind for sure and lots of big changes. The other program

00:41:01.440 --> 00:41:06.720
 I just wanted to let y'all know about is the TRIP program, which is the transportation

00:41:06.720 --> 00:41:12.560
 reinvestment program that our board recently approved. And that basically takes a certain

00:41:12.560 --> 00:41:20.080
 percentage of prior fiscal year savings and makes it available to the three member cities

00:41:20.080 --> 00:41:26.160
 for the purpose of transit related projects. So that has been approved. The city of Lewisville

00:41:26.160 --> 00:41:32.440
 has submitted their first project that's currently under review. And so that could be for projects

00:41:32.440 --> 00:41:42.640
 such as like sidewalks, access to trails, access to transit. It could be for amenities

00:41:42.640 --> 00:41:50.120
 on trails. And so anything that kind of enhances the customers or the public's experience with

00:41:50.120 --> 00:41:57.640
 mobility. And so that's any type of mobility, walking, cycling, using transit, et cetera.

00:41:57.640 --> 00:42:04.700
 So that program is active. I know in the past council member Briggs has brought up amenities

00:42:04.700 --> 00:42:09.360
 for the trail and things like that. And so just to make sure that y'all are aware of

00:42:09.360 --> 00:42:14.280
 that program, I'm sure that you're having those discussions at council level, but that

00:42:14.280 --> 00:42:22.400
 funding is available for projects that do qualify. That is about it for this time around.

00:42:22.400 --> 00:42:28.440
 Again, we don't operate service on Christmas day or New Year's day, but our customer service

00:42:28.440 --> 00:42:33.880
 teams do remain open just to answer any questions or to help folks reschedule their trips. But

00:42:33.880 --> 00:42:38.120
 I'm happy to answer any questions that you might have.

00:42:38.120 --> 00:42:46.240
 Council member Briggs. The study or report that you mentioned, is

00:42:46.240 --> 00:42:51.280
 that available online or for the public to review and read?

00:42:51.280 --> 00:42:57.880
 Sure. It was included in the December board packet, but I am happy to also send it to

00:42:57.880 --> 00:43:04.240
 this group if you'd like to see it. Yeah, I would like to see it as well.

00:43:04.240 --> 00:43:11.040
 Thank you. That's what we're waiting for.

00:43:11.040 --> 00:43:14.600
 Just so the members here or anybody watching has a better understanding, can you give a

00:43:14.600 --> 00:43:19.360
 brief description of where seven and three are as to where we're going to continue to

00:43:19.360 --> 00:43:24.680
 have some bus service? Sure, absolutely. So route three runs basically

00:43:24.680 --> 00:43:32.920
 from the DBTC out to like where the Salvation Army is located. So there's a lot of human

00:43:32.920 --> 00:43:41.040
 services, agencies, apartment complexes, as well as some justice departments are located

00:43:41.040 --> 00:43:48.360
 along that route. So it's heavily what we would consider a transit dependent population

00:43:48.360 --> 00:43:56.400
 and access to human services, which from FTA's Title VI perspective is a critical area for

00:43:56.400 --> 00:44:02.720
 fixed route service. Based on data, it also meets the criteria of a minimum of 10 boardings

00:44:02.720 --> 00:44:08.440
 per hour along that route, which is why we're recommending that we at least test out that

00:44:08.440 --> 00:44:14.680
 route. And then route seven runs from the DDTC through downtown, through UNT, and then

00:44:14.680 --> 00:44:22.360
 out to Razor Ranch. There are some human services centers located along that route, but it's

00:44:22.360 --> 00:44:29.840
 also just a very highly dense area, specifically with traffic to downtown apartment complexes,

00:44:29.840 --> 00:44:36.120
 to university, and then Razor Ranch. And so it again, in the analysis that was done, exceeds

00:44:36.120 --> 00:44:42.400
 the threshold of 10 boardings per hour. So the goal is really to kind of keep those routes

00:44:42.400 --> 00:44:49.440
 for a period of time, I am assuming probably about three months, and we will layer on-demand

00:44:49.440 --> 00:44:54.040
 service on top of it. And we'll really be able to do some A and B testing. And so we'll

00:44:54.040 --> 00:45:00.720
 be able to see, are we garnering additional riders because those who use the fixed route

00:45:00.720 --> 00:45:05.800
 prefer to use the fixed route, but we're getting new people who would prefer to use the on-demand?

00:45:05.800 --> 00:45:09.800
 Or is that on-demand service cannibalizing the fixed route, and the folks using the fixed

00:45:09.800 --> 00:45:15.120
 route really prefer the on-demand? And that's data that we just don't have right now. We

00:45:15.120 --> 00:45:20.720
 don't have hour-by-hour or constituent-based data for our routes. And so that's going to

00:45:20.720 --> 00:45:25.480
 give us the opportunity to get some true A and B testing done and have that data and

00:45:25.480 --> 00:45:30.840
 have that discussion with our board to make the best decision for the community.

00:45:30.840 --> 00:45:38.640
 I'm certainly interested in hearing and seeing what the results of real behavior would be

00:45:38.640 --> 00:45:43.400
 rather than the predetermined conclusion that we're moving away from fixed routes. So during

00:45:43.400 --> 00:45:50.920
 that testing period, the routes that I talked about, fixed routes, we talked about keeping

00:45:50.920 --> 00:45:59.480
 up, roughly what percent of Denton ridership do those fixed routes represent?

00:45:59.480 --> 00:46:07.200
 I would hate to throw out a number, but of the eight fixed routes that are in Denton,

00:46:07.200 --> 00:46:12.400
 those are the two best performing routes. But I can certainly follow up with an exact

00:46:12.400 --> 00:46:15.200
 percentage. I can get that for you. I have that available.

00:46:15.200 --> 00:46:19.160
 Yeah, rough would be fine. I don't need it exactly. I mean, just, you know, are we talking

00:46:19.160 --> 00:46:27.200
 about, you know, by, are we pruning away the 80% of miles that only represent 20% of ridership?

00:46:27.200 --> 00:46:33.320
 That would be like the ideal answer, right? That would be, you know, very efficient. So

00:46:33.320 --> 00:46:35.360
 I'd be interested in understanding that.

00:46:35.360 --> 00:46:37.360
 Sure. I can absolutely follow up.

00:46:37.360 --> 00:46:48.360
 And then my other question is, in the study that led to this recommendation, that's now

00:46:48.360 --> 00:46:56.280
 being contemplated, what was the degree of, or amount of input from transit dependent

00:46:56.280 --> 00:47:00.760
 members of the public?

00:47:00.760 --> 00:47:11.920
 So let me clarify. The Accenture report was an analysis that was based on an in-depth

00:47:11.920 --> 00:47:20.760
 exploration of DCTA in their current state. The Accenture report does not recommend moving

00:47:20.760 --> 00:47:27.400
 away from fixed route and moving to on-demand. So that was not part of the scope of work.

00:47:27.400 --> 00:47:32.560
 It did, part of the scope of work, however, was to say, how are your routes performing

00:47:32.560 --> 00:47:42.160
 against standards? And so it was really the DCTA board's decision in looking at performance

00:47:42.160 --> 00:47:47.940
 and how effective and efficient that service is to say, okay, how do we address the inefficient

00:47:47.940 --> 00:47:55.720
 service? And so we have had these MAS contracts under, we've had them under contract for two

00:47:55.720 --> 00:48:02.160
 and a half years and we hadn't leveraged them other than for some contract city work that

00:48:02.160 --> 00:48:07.040
 we have in Frisco and McKinney. And so it was really a collaboration from the board

00:48:07.040 --> 00:48:14.320
 and saying, how can we provide more service? How can we provide more efficient service

00:48:14.320 --> 00:48:18.840
 and take some of this maybe inefficient fixed route service off the road? So you won't,

00:48:18.840 --> 00:48:23.480
 in the Accenture report that I'm happy to send out, you won't see a recommendation to

00:48:23.480 --> 00:48:29.640
 remove fixed routes and add on-demand. That was really kind of an output after the board

00:48:29.640 --> 00:48:35.360
 had reviewed those, that report and had been having some ongoing discussion about maybe

00:48:35.360 --> 00:48:41.920
 what does the future of service look like? So are there plans in any part of this process

00:48:41.920 --> 00:48:52.240
 to get input from transit dependent members? Yes, 100%. So the FTA requires us to partake

00:48:52.240 --> 00:48:58.040
 in the public involvement process. So basically what would happen is we would get the MAS

00:48:58.040 --> 00:49:03.000
 proposals from Viet and Spare next month. We would share them with our board. Hopefully

00:49:03.000 --> 00:49:08.360
 we would have one for recommendation. Once the board approves that, we would then have

00:49:08.360 --> 00:49:12.800
 a workshop with the member cities and the city staff to kind of tweak those service

00:49:12.800 --> 00:49:19.080
 proposals. Once those tweaks are done, we would then take that kind of final proposed service

00:49:19.080 --> 00:49:26.960
 plan model out to the public. And because this is such a major deviation from the typical

00:49:26.960 --> 00:49:34.600
 way we provide service, we would do most likely like two plus months worth of in-depth public

00:49:34.600 --> 00:49:40.320
 involvement where we're going out, we're virtually going out to different groups, talking to

00:49:40.320 --> 00:49:46.160
 them about what the changes are, how that might impact them positively or negatively,

00:49:46.160 --> 00:49:53.640
 to collect that feedback. Our board cannot formally and officially approve a service change

00:49:53.640 --> 00:49:59.280
 of this magnitude without reviewing the public feedback in conjunction with the materials

00:49:59.280 --> 00:50:06.880
 for approval. Councilmember Briggs. Thank you, Chair. During this conversation, of course,

00:50:06.880 --> 00:50:14.720
 I came up with other questions. So if you would just allow me just a couple. On demand

00:50:14.720 --> 00:50:21.880
 costs, are they the same as the fixed route cost? It really depends on frequency and the

00:50:21.880 --> 00:50:26.600
 number of people that you're carrying. There are situations where on-demand service can

00:50:26.600 --> 00:50:31.840
 be more expensive than fixed route. There are also situations where it can be drastically

00:50:31.840 --> 00:50:36.280
 cheaper than fixed route. So it's really going to depend on how many vehicles per hour we

00:50:36.280 --> 00:50:42.880
 have on the road and how many people we're carrying. Okay. So I'm just, I have a little

00:50:42.880 --> 00:50:49.920
 concern about eliminating those fixed routes. I think that that is a good part of a successful

00:50:49.920 --> 00:50:53.760
 bus system. And I know that on-demand is, you know, coming up, but I don't know that

00:50:53.760 --> 00:51:01.200
 that's the solution. And when we talk about improving performance, I don't know that elimination

00:51:01.200 --> 00:51:10.800
 is the way to improve a performance. I think it might be easiest. And so if we eliminate

00:51:10.800 --> 00:51:16.080
 fixed routes for majority of them and go to on-demand service, which is a contract that

00:51:16.080 --> 00:51:24.080
 eliminates overhead, right? That eliminates staff buses, bus routes. So does that mean

00:51:24.080 --> 00:51:31.880
 you take in less tax money from the residents of Denton if you're not spending it? No, because

00:51:31.880 --> 00:51:37.080
 the, the half cent sales tax was voted in. So we would still receive that half cent sales

00:51:37.080 --> 00:51:42.640
 tax. I believe, and I don't want to speak on behalf of the board, but I believe the

00:51:42.640 --> 00:51:51.600
 thought process is we spend the same, but we're able to offer much better and more service.

00:51:51.600 --> 00:51:56.800
 So we're able to cover a larger service area with more frequency, which then becomes much

00:51:56.800 --> 00:52:02.840
 more convenient for the consumer. So it also allows them to go like from curb to curb versus

00:52:02.840 --> 00:52:09.240
 having to go to a stop. We're able to cover areas that currently don't have service now

00:52:09.240 --> 00:52:13.640
 rather than waiting 30 minutes during peak and an hour during off-peak, maybe you're

00:52:13.640 --> 00:52:19.160
 only waiting 10 minutes for a ride. So I think that the thought process is, is if we could

00:52:19.160 --> 00:52:24.080
 provide more coverage and more frequent service within the current, what we're currently spending

00:52:24.080 --> 00:52:29.320
 on fixed route, that would be the best plan forward.

00:52:29.320 --> 00:52:37.080
 Well, if it, if it costs more money, it's not going to be equitable for all bus riders.

00:52:37.080 --> 00:52:43.840
 So I just, this is one of my last meetings and I just want to make the comment that whatever

00:52:43.840 --> 00:52:49.840
 changes are made, please make sure that there's equity in, in your decision for, for all of

00:52:49.840 --> 00:52:57.140
 us. Absolutely. And as part of the FTA requirement, we will do a title six analysis and that specifically

00:52:57.140 --> 00:53:01.960
 addresses equity. Certainly there will be some trade-offs that we will have to discuss

00:53:01.960 --> 00:53:07.000
 with our board. So moving to a more on-demand model, what does that do from an equity or

00:53:07.000 --> 00:53:11.800
 a title six perspective, but also what does that do from a federal funding perspective?

00:53:11.800 --> 00:53:20.080
 Because our federal funding is based on total ridership and on the on-demand TMCs track

00:53:20.080 --> 00:53:25.400
 ridership differently. And we're, they're still working with the FTA on, on how to kind

00:53:25.400 --> 00:53:31.360
 of officially count ridership that would then go toward our federal funding. So there are

00:53:31.360 --> 00:53:38.000
 what Accenture would call, would be some considerations that our board needs to weigh before making

00:53:38.000 --> 00:53:41.200
 this decision. Thank you.

00:53:41.200 --> 00:53:51.000
 Yes, and I did see a study for mass service in Louisville. Is that something that was

00:53:51.000 --> 00:53:57.960
 done through DCTA? Did y'all get that, those numbers, or was that someone else who did?

00:53:57.960 --> 00:54:02.120
 We have not, through our mass contracts, we have not done a proposal specifically for

00:54:02.120 --> 00:54:09.600
 Louisville. As part of this open procurement, both Via and Spare did provide original proposals.

00:54:09.600 --> 00:54:13.560
 And within those proposals, they carved out pieces of Denton and pieces of Louisville

00:54:13.560 --> 00:54:18.120
 where they made some recommendations. But that was before our board had kind of made

00:54:18.120 --> 00:54:23.240
 some decisions about the future of service. And so that's why we're asking Via and Spare

00:54:23.240 --> 00:54:31.160
 to come back with an additional proposal. So not a direct proposal for Louisville DCTA

00:54:31.160 --> 00:54:35.640
 was not involved. Okay. Well, and based on what I saw on there,

00:54:35.640 --> 00:54:41.280
 and again, this was prior to this, there was substantial savings by switching to the mass

00:54:41.280 --> 00:54:47.760
 in the Louisville area. I can't remember the exact percentage, but you know, it was

00:54:47.760 --> 00:54:55.960
 about 900,000. And for about 100,000, they could add in Sunday service. So the ability

00:54:55.960 --> 00:55:02.680
 to add services by changing over to this where our ridership is at that below 10 is definitely

00:55:02.680 --> 00:55:08.760
 there. Some of the other things that have been contemplated are holiday service, which

00:55:08.760 --> 00:55:14.240
 we currently don't, or longer hours where right now we're cutting off at 930. If we

00:55:14.240 --> 00:55:20.040
 could get a little bit later, maybe up to midnight even with mass service, that would

00:55:20.040 --> 00:55:24.520
 be very beneficial to people who right now when they want to go down to Dallas, they

00:55:24.520 --> 00:55:28.400
 have to drive because unless you're going to finish everything up and be able to get

00:55:28.400 --> 00:55:33.200
 back to Denton by 930, the train doesn't work for you.

00:55:33.200 --> 00:55:39.560
 So absolutely, absolutely. The cost efficiencies with on demand allow us to kind of scale up

00:55:39.560 --> 00:55:45.280
 and scale down much more efficiently than we could with fixed route, 100%. And so we

00:55:45.280 --> 00:55:49.480
 are looking at part of those proposals will include what does it look like if we add Sunday

00:55:49.480 --> 00:55:55.880
 service? What does it look like if we just like you said, Mr. Ryan, if we increase our

00:55:55.880 --> 00:56:01.520
 time frequency and, you know, look at days of the week and holidays. So I mean, there

00:56:01.520 --> 00:56:05.760
 are definitely some benefits to moving to an on demand model for sure.

00:56:05.760 --> 00:56:10.080
 Right. And I wasn't, I had to step out of the board meeting the other day, I wasn't

00:56:10.080 --> 00:56:16.440
 there to hear what the final vote was on how to proceed. Was there also going, were you

00:56:16.440 --> 00:56:21.920
 also going to look at changing the bus routes to 15 minutes so that matched up and didn't

00:56:21.920 --> 00:56:26.920
 create, because right now our bus runs every 30 minutes and on demand was going to be 10

00:56:26.920 --> 00:56:37.240
 minute peak and 15 minute off peak was estimated time for pick up. So there's an equity there

00:56:37.240 --> 00:56:43.320
 that why would you wait 30 minutes for a bus when you could get an on demand in 10 or 15?

00:56:43.320 --> 00:56:47.960
 Absolutely. We didn't get into that level, but I would anticipate that as we look at

00:56:47.960 --> 00:56:52.920
 these proposals from both Viet and spare that any recommendations they make and then through

00:56:52.920 --> 00:56:57.280
 the workshops with each member city, like once we have that final service plan, then

00:56:57.280 --> 00:57:01.400
 we would go back and look at any of our existing fixed routes that are continuing to operate

00:57:01.400 --> 00:57:06.080
 and we would tweak so that those connection points would make sense. And then that whole

00:57:06.080 --> 00:57:11.800
 service plan, that comprehensive service plan is what we would then take to the public.

00:57:11.800 --> 00:57:20.520
 Well, if I can make an unsolicited suggestion, if it were up to me to present of this, you

00:57:20.520 --> 00:57:24.640
 know, sort of large change to the public, I'd include all the good stuff and not just

00:57:24.640 --> 00:57:29.880
 that we're going to cut things. And I know there are some people who very sincerely believe

00:57:29.880 --> 00:57:35.960
 it would be in the best interest of Denton to not fund public transit and instead fund

00:57:35.960 --> 00:57:41.000
 the ability to write checks to corporations for economic development. That's a really

00:57:41.000 --> 00:57:49.120
 poor framing. If in fact you can be moving toward, you know, greater service to the public

00:57:49.120 --> 00:57:55.000
 and, you know, it may well be the case that if fully understood, you know, that on demand

00:57:55.000 --> 00:58:03.960
 may provide better service to those same individuals. But all those good things, later hours or

00:58:03.960 --> 00:58:10.920
 a train, you know, holistically one picture versus the other, it might be, you know, might

00:58:10.920 --> 00:58:15.480
 be more tolerable. Absolutely. I feel like we're going to find out a lot in the next

00:58:15.480 --> 00:58:22.160
 60 days. So the next 30 dedicated to kind of our board's decision on those two on demand

00:58:22.160 --> 00:58:29.460
 proposals and then the following 30 days kind of tweaking the final proposal and developing

00:58:29.460 --> 00:58:34.320
 something to take to the public. So I feel like we're still in the exploration phase,

00:58:34.320 --> 00:58:38.880
 but that we'll have so much more to share over the next 60 days for sure.

00:58:38.880 --> 00:58:45.920
 Okay. Interesting times. Thanks for coming to update us. Absolutely. Thank you for having

00:58:45.920 --> 00:58:52.280
 me. Okay. Do we think we can do item D now? We're going to try it one more time. So let

00:58:52.280 --> 00:59:00.220
 me work so seamlessly for Becky's presentation. I already read the whole thing. So, okay.

00:59:00.220 --> 00:59:07.440
 So can you see that? Yes. All right. Let me go to full screen. Okay. So again, good morning

00:59:07.440 --> 00:59:11.680
 everyone. Brian Young, city traffic engineer here to talk to you just about a couple of

00:59:11.680 --> 00:59:16.560
 things. Just give you some updates. The first one is the Hickory street bike lane bollards.

00:59:16.560 --> 00:59:25.760
 We put these in, I believe in June and our spacing at the time based on what we were

00:59:25.760 --> 00:59:31.940
 reading from the manufacturer, we put them at 40 feet. We've since discovered that this

00:59:31.940 --> 00:59:38.240
 allows because our speeds are a little bit lower, this allows the drivers to actually

00:59:38.240 --> 00:59:44.920
 enter the bike lane and temporarily park to load or unload or make some other maneuver.

00:59:44.920 --> 00:59:48.680
 And so our plan moving forward, this probably won't happen until after the beginning of

00:59:48.680 --> 00:59:54.400
 the year, just based on crew availability. We do have material on hand and in stock.

00:59:54.400 --> 00:59:58.520
 But we're going to go ahead and in those areas where they're 40 feet apart, we're going to

00:59:58.520 --> 01:00:03.400
 install an intermediary bollard. So it's a 20 foot spacing. And we think that's going

01:00:03.400 --> 01:00:09.320
 to be a much better solution. We've talked with the vendor and they're on board with

01:00:09.320 --> 01:00:15.400
 the 20 foot spacing as well. So over the next couple of months, you'll see that situation

01:00:15.400 --> 01:00:24.800
 change a little bit. And moving forward, we will also set a maximum of 30 foot spacing.

01:00:24.800 --> 01:00:30.780
 And a lot of it's speed based, but we just find that the closer spacing of the bollards

01:00:30.780 --> 01:00:35.360
 just kind of tightens up, gives a little bit more of a visual barrier and tightens up that

01:00:35.360 --> 01:00:39.080
 security on the bike lane. >> Would you mind if we stop for questions

01:00:39.080 --> 01:00:44.600
 between each item? That requires you to take it down so I can see.

01:00:44.600 --> 01:00:48.280
 >> Okay. >> That's a technical challenge, I know.

01:00:48.280 --> 01:00:54.680
 See, I had a feeling. That's one of our breaks. >> Thank you so much for looking into this

01:00:54.680 --> 01:01:03.160
 and adding more. I guess my question is, so are you going to add ones in the add some?

01:01:03.160 --> 01:01:07.960
 Are you going to just be resetting all of them and adding additional ones?

01:01:07.960 --> 01:01:11.160
 >> So we talked with staff and I think what we're going to do because they're 40 feet

01:01:11.160 --> 01:01:16.360
 apart is just to go ahead and put additional bollards to change to a 20 foot spacing, leave

01:01:16.360 --> 01:01:24.480
 what's there and add one in the middle. It's not difficult to remove them and relocate

01:01:24.480 --> 01:01:29.240
 them, but I think the 20 foot spacing is still going to be satisfactory. We're going to like

01:01:29.240 --> 01:01:34.160
 that a lot better than the 40. It didn't make sense to move them, just the staff time to

01:01:34.160 --> 01:01:37.800
 move them from a 40 to a 30 or a 20, it just didn't make sense.

01:01:37.800 --> 01:01:45.480
 >> I agree. I know it will happen quicker that way too. And so just to clarify, these

01:01:45.480 --> 01:01:49.600
 are already, you've ordered these and then they'll just be installed?

01:01:49.600 --> 01:01:57.120
 >> Correct. We bought extra when we purchased these for the Hickory and the Welch. And so

01:01:57.120 --> 01:02:01.560
 we've got enough on hand, we think, to finish out this project. If not, we can certainly

01:02:01.560 --> 01:02:09.020
 order the turnaround time. There's not a lot of lead time on these. It's not a high demand

01:02:09.020 --> 01:02:13.080
 product so they typically have some in stock and they can deliver those fairly quickly.

01:02:13.080 --> 01:02:19.580
 We have other streets that we've got planned for implementation as well. So we'll be ordering

01:02:19.580 --> 01:02:22.240
 additional stock in the near future in any case.

01:02:22.240 --> 01:02:28.160
 >> Is there any kind of learning or, I mean, I guess, I guess there's no official international

01:02:28.160 --> 01:02:33.460
 standard or we would have followed it, but what are we basing 40 on? What are we basing

01:02:33.460 --> 01:02:35.860
 20 on other than it's better than 40?

01:02:35.860 --> 01:02:42.520
 >> So the vendor has a range. There's a recommended range of spacing on devices and it's really

01:02:42.520 --> 01:02:50.480
 based on speed so we picked kind of on the high end of the range initially for just cost

01:02:50.480 --> 01:02:57.000
 effective and what we're finding is that the higher end of the range, if people are motivated

01:02:57.000 --> 01:03:01.640
 to try and get into that bike lane, they will. It allows them to. So we just need, in certain

01:03:01.640 --> 01:03:07.280
 areas we wouldn't, we may not have to, but specifically along Hickory adjacent to the

01:03:07.280 --> 01:03:11.320
 commercial where people want to just run in real quick and pick up their pizza that they

01:03:11.320 --> 01:03:18.480
 ordered, we're finding some violations and so we just, in that type of area we're just

01:03:18.480 --> 01:03:21.560
 going to be consistent and take it to a 20 foot spacing.

01:03:21.560 --> 01:03:28.040
 >> Do we know what's implemented in other cities that are similarly situated and have

01:03:28.040 --> 01:03:29.040
 similar problems?

01:03:29.040 --> 01:03:36.360
 >> Again, it's across the board. It's some cities, if you've got a lot of vehicular traffic

01:03:36.360 --> 01:03:44.360
 that are going to a 15 foot spacing, 30 seems to be kind of a universal average, but again

01:03:44.360 --> 01:03:50.800
 a 30 foot spacing is more than a car. Easily can maneuver, especially a small car, can

01:03:50.800 --> 01:03:55.640
 maneuver into the bike lane to temporarily park if you don't see any cyclists, even if

01:03:55.640 --> 01:04:00.460
 you do, people don't care, but we're going to take a little bit now, a little bit towards

01:04:00.460 --> 01:04:05.600
 the lower end and use that 20 foot spacing. I think we're going to find that that's going

01:04:05.600 --> 01:04:08.400
 to work for us in most places in town.

01:04:08.400 --> 01:04:12.840
 >> Or it could set off like an arms war, where now everyone switches to Mini Coopers.

01:04:12.840 --> 01:04:16.720
 >> Yes, the slalom run, yes. Or skateboarders.

01:04:16.720 --> 01:04:22.760
 >> Okay, thank you. I'm going to continue now, thank you.

01:04:22.760 --> 01:04:26.680
 >> John, did you have any question on this?

01:04:26.680 --> 01:04:29.680
 >> No, I'm fine.

01:04:29.680 --> 01:04:40.360
 >> Okay, thanks. All right. I can't see this. The next one is Highway Safety Improvement

01:04:40.360 --> 01:04:48.160
 Program. This is a program really funded and led by the state by which we identify locations

01:04:48.160 --> 01:04:56.400
 that have high fatality and serious injury crash history, and typically we will focus

01:04:56.400 --> 01:05:03.640
 on intersections that are signalized because those are normally where the fatalities occur,

01:05:03.640 --> 01:05:11.840
 but they're also some of the easily fixed locations. We've got six locations currently

01:05:11.840 --> 01:05:19.520
 underway with this program. The three in green are actually under -- they've been bid and

01:05:19.520 --> 01:05:28.720
 awarded and are going to construction early spring of 2021, and that's McKinney at Mockingbird,

01:05:28.720 --> 01:05:35.920
 McKinney at Audra, and Teasley at 35. So those will either be modified or reconstructed.

01:05:35.920 --> 01:05:43.760
 You've seen Council agenda item not too long ago about the funding, and we had to pay some

01:05:43.760 --> 01:05:51.440
 overage on those, so those are moving forward to construction in early '21. I guess it's

01:05:51.440 --> 01:05:57.880
 Magento. The ones on 288 are nearing completion of design. Those will be awarded probably

01:05:57.880 --> 01:06:05.040
 bid and awarded May of '21 going to construction later that year. I guess King's Row at 288,

01:06:05.040 --> 01:06:11.240
 McKinney at 288, and University at 288. So those three intersections will be receiving

01:06:11.240 --> 01:06:17.760
 primarily technology upgrades, but King's Row is a full reconstruction. Again, you saw

01:06:17.760 --> 01:06:24.080
 a Council agenda item on that not too long ago as well. When they're on system, we have

01:06:24.080 --> 01:06:29.280
 the advantage of paying for 100% of the construction, and when they're off system like McKinney

01:06:29.280 --> 01:06:36.800
 at Mockingbird, we pay 10%. So it's still a good deal, even if we have to pay our 10%.

01:06:36.800 --> 01:06:39.980
 But just to give you a quick update on the status of those projects, you'll see the three

01:06:39.980 --> 01:06:45.000
 in green there go to construction in a matter of months, and probably a year from now, you'll

01:06:45.000 --> 01:06:49.600
 see those in the Magento color go to construction along 288 as well.

01:06:49.600 --> 01:06:58.400
 >> Okay. I want to take it down to see if there's a question. Anybody? Councilmember

01:06:58.400 --> 01:07:02.240
 Briggs. >> You mentioned McKinney and Mockingbird.

01:07:02.240 --> 01:07:10.840
 That's a T intersection. Well, what will be done there? Just a new light? Like a --

01:07:10.840 --> 01:07:15.820
 >> So a lot of these are technology upgrades, which gives us the opportunity to sense traffic

01:07:15.820 --> 01:07:24.080
 better. Well, we're, you know, advancing to LED street light attachments. A lot of it's

01:07:24.080 --> 01:07:29.620
 inside the cabinet, really, rather than the uprights themselves. So it's either -- they

01:07:29.620 --> 01:07:34.840
 may be getting some -- if it's an old intersection, and I don't want to speak at a turn on McKinney

01:07:34.840 --> 01:07:42.800
 and Mockingbird, some of them are getting new. They're 25, 30 years old. They've paid

01:07:42.800 --> 01:07:49.520
 their dues and they're ready to be upgraded. Some are span wire, and that's the wood pole

01:07:49.520 --> 01:07:54.920
 with the cable across and the lights. Those are going to a steel upright with a mast arm.

01:07:54.920 --> 01:08:01.960
 And then -- but the bulk of the improvements are technology based, just giving us, you

01:08:01.960 --> 01:08:06.720
 know, better connectivity, running fiber, changing out the controllers to the modern

01:08:06.720 --> 01:08:11.880
 version that we're using. So a lot of it is just really technology. It creates a safer

01:08:11.880 --> 01:08:15.440
 intersection because we have better equipment in the field.

01:08:15.440 --> 01:08:20.680
 >> Thank you. >> But when I asked about this in full council,

01:08:20.680 --> 01:08:25.240
 some of the technology enhancements were described as improving sensing.

01:08:25.240 --> 01:08:27.760
 >> Right, detection. >> As pedestrians and cyclists.

01:08:27.760 --> 01:08:34.420
 >> Yes, yes. We're working with our provider, our vendor, to, again, I think I mentioned

01:08:34.420 --> 01:08:41.040
 that they are -- pedestrian detection module is in testing mode, beta testing, and they're

01:08:41.040 --> 01:08:47.360
 developing a cyclist bike detection module. So this particular device is that fisheye

01:08:47.360 --> 01:08:51.400
 camera that hangs over the intersection and really looks at all four of the approaches

01:08:51.400 --> 01:08:57.640
 at once versus having four different cameras. So it allows us to do a lot of things because

01:08:57.640 --> 01:09:02.160
 it sees everything at once. It's a single device that's looking at all the input, and

01:09:02.160 --> 01:09:08.360
 we don't have to interface between different devices. We've had good success with it, and

01:09:08.360 --> 01:09:13.840
 the vendors continue to add modules. We can collect data with this camera, and we can

01:09:13.840 --> 01:09:19.000
 sense, you know, now we can sense pedestrians, or we will be able to soon, and they're working

01:09:19.000 --> 01:09:23.280
 on bicycle detection. So it's a very robust device, and that's really what we're moving

01:09:23.280 --> 01:09:26.600
 towards in the future, using this everywhere in town.

01:09:26.600 --> 01:09:38.640
 >> That's great. Okay. >> So the next one is the mobility plan update.

01:09:38.640 --> 01:09:46.540
 So we have finished our community input. That ended in October. And the month of December,

01:09:46.540 --> 01:09:52.200
 Walter P. Moore, our consultant, is finalizing the draft final, whatever you want to call

01:09:52.200 --> 01:09:56.840
 it, the final draft or the draft final report and associated maps, and this is all three

01:09:56.840 --> 01:10:03.320
 maps, the bike plan, the PED plan, and the transportation thoroughfare plan, what we

01:10:03.320 --> 01:10:10.760
 used to call it. They will be submitting that to staff for review this month, and we will

01:10:10.760 --> 01:10:16.840
 be taking probably most of January to go through that with a fine-tooth comb, make sure all

01:10:16.840 --> 01:10:22.520
 of the citizen input that can be addressed has been addressed, and returning that, our

01:10:22.520 --> 01:10:27.360
 comments, back to Walter P. Moore, and then in the month of February, they will be taking

01:10:27.360 --> 01:10:33.280
 our comments, rolling that into the document, rolling out, again, that draft final report

01:10:33.280 --> 01:10:38.800
 for -- we're looking in March to begin a work session with council to start talking

01:10:38.800 --> 01:10:46.360
 about the document itself and the maps you've seen, but a lot of the associated text and

01:10:46.360 --> 01:10:50.360
 policies, et cetera, you have not, so we'll spend the month of March going through that

01:10:50.360 --> 01:10:56.840
 with council and looking forward to an April adoption. Hopefully by the end of April, we'll

01:10:56.840 --> 01:11:01.520
 have all of the questions answered, and I'll be ready to move forward with the formal adoption

01:11:01.520 --> 01:11:06.200
 of the immobility plan update.

01:11:06.200 --> 01:11:07.200
 >> Questions?

01:11:07.200 --> 01:11:11.400
 >> Sure, there are questions.

01:11:11.400 --> 01:11:12.400
 >> Okay.

01:11:12.400 --> 01:11:13.400
 >> Sure.

01:11:13.400 --> 01:11:19.000
 >> Oh, excellent. Moving along.

01:11:19.000 --> 01:11:26.000
 So the senior planner by civil ministry coordinator position was advertised in November, and the

01:11:26.000 --> 01:11:31.040
 way we structured it was we were leaving it open until filled, so as of now, we've got

01:11:31.040 --> 01:11:37.520
 probably 17, 18 applications. Staff is going through those applications and looking at

01:11:37.520 --> 01:11:45.080
 each candidate, and our goal is to identify those that we are most interested in and start

01:11:45.080 --> 01:11:52.280
 interviews in January, so we'll be coming back to you either January or February with

01:11:52.280 --> 01:12:00.440
 some feedback on the process there, but we -- again, this is an interesting combination,

01:12:00.440 --> 01:12:05.600
 to say the least, of skill sets that we're looking for, so the qualified candidates are

01:12:05.600 --> 01:12:09.680
 few and far between. Like I said, we've got -- I've looked at them, we've got several

01:12:09.680 --> 01:12:16.840
 very good candidates. I don't know that anybody is 100% satisfies all the different demands,

01:12:16.840 --> 01:12:23.880
 but we're looking for that -- the right person. It's obviously some of it can be learned on

01:12:23.880 --> 01:12:32.480
 the job, but that right person that fits the characters and the, you know, the expertise

01:12:32.480 --> 01:12:36.720
 and the experience that we're looking for, like I say, I think we've got a couple in

01:12:36.720 --> 01:12:41.800
 the pool right now, but we're going to continue to accept applications until we decide that,

01:12:41.800 --> 01:12:46.040
 you know what, we found the right person, so we'll hopefully be conducting those interviews

01:12:46.040 --> 01:12:49.840
 in January and have some more information for you following that.

01:12:49.840 --> 01:13:04.240
 >> Council member, questions? Are you looking for someone who is mostly an engineer or someone

01:13:04.240 --> 01:13:10.360
 who's got that -- not to say that engineers couldn't have this skill set, but are you

01:13:10.360 --> 01:13:15.840
 looking for the skill set involved in a lot of public engagement?

01:13:15.840 --> 01:13:20.000
 >> So very much the latter. Yeah, if it was going to be an engineer, it would have to

01:13:20.000 --> 01:13:26.320
 be an engineer with crayons, as I call it, but very much a planner type person. It is

01:13:26.320 --> 01:13:35.080
 a different approach. Planners just -- their education, their background is typically not

01:13:35.080 --> 01:13:40.200
 like an engineer's, and we really appreciate that those characteristics in this type of

01:13:40.200 --> 01:13:49.200
 role are key. That public engagement and the experience even, and the jobs knowledge is

01:13:49.200 --> 01:13:54.240
 very, very different from engineering. It's not necessarily 100% data-driven. It's the

01:13:54.240 --> 01:14:01.160
 softer side, and it's folding in the community needs and desires and combining those and

01:14:01.160 --> 01:14:05.400
 marrying those up to what we can and can't do, but yes, it's very much the latter of

01:14:05.400 --> 01:14:06.400
 your two choices there.

01:14:06.400 --> 01:14:10.680
 >> Okay. What else you got?

01:14:10.680 --> 01:14:22.000
 >> One more. Well, there was one more. Oh, it's here. It's not a separate page. So the

01:14:22.000 --> 01:14:29.040
 last one is the -- we're calling now the all-way crossing, no longer the all-crosswalk. The

01:14:29.040 --> 01:14:34.480
 committee on persons with disabilities has asked us to take the word "walk" out of it,

01:14:34.480 --> 01:14:42.320
 since not everyone using this is walking. We met with them in November to get their

01:14:42.320 --> 01:14:57.600
 guidance on the type of ramp, and let me share another -- I've got another -- well, it doesn't

01:14:57.600 --> 01:15:05.580
 show up here. Okay. I'll go back to this. So if you remember, these four intersections

01:15:05.580 --> 01:15:11.480
 are the ones around the square, and I was trying to share my explorer. I've got Google

01:15:11.480 --> 01:15:18.800
 maps up. The intersections around the square adjacent to the actual square are fairly spartan,

01:15:18.800 --> 01:15:26.900
 a lot of concrete, not a lot of plantings or furniture, et cetera, but the corners away

01:15:26.900 --> 01:15:34.960
 from the courthouse have significant amounts of landscaping, or some have traffic signal

01:15:34.960 --> 01:15:41.400
 hardware, some have street furniture, and what we went to the COPWD to gain was their

01:15:41.400 --> 01:15:46.480
 preference on the type of ramp, the accessible ramp for these diagonal crossings, and that's

01:15:46.480 --> 01:15:51.720
 really what this project is focusing on, is the diagonals. If you remember, you approved

01:15:51.720 --> 01:15:59.160
 the continuation of the all-ped phase and asked staff to go back and add the diagonal

01:15:59.160 --> 01:16:03.520
 crossings with ramps and markings so that everybody knows that they can go across instead

01:16:03.520 --> 01:16:08.600
 of making an L shape to get across from one corner to the next. So this program, this

01:16:08.600 --> 01:16:13.800
 project is really focused on putting in those diagonal crossings, and associated with those

01:16:13.800 --> 01:16:20.680
 crossings is the new accessible ramping that's required to get to those diagonal crossings.

01:16:20.680 --> 01:16:25.800
 We offered the committee a couple of different options. One would be what they call a transition

01:16:25.800 --> 01:16:30.480
 where you lay the entire curb down all the way around the radius, and then you put the

01:16:30.480 --> 01:16:35.040
 tactile surfaces where your crossings are going to be. They didn't like that because

01:16:35.040 --> 01:16:44.040
 they were afraid that there may be some tipping issues with chairs or scooter-type devices,

01:16:44.040 --> 01:16:49.360
 and then what they settled on was very much like what we have, is a directional ramp in

01:16:49.360 --> 01:16:55.320
 the middle of the radius pointing diagonally to another directional ramp across the intersection.

01:16:55.320 --> 01:17:03.520
 And so we are now working towards a design contract with a consultant, because we don't

01:17:03.520 --> 01:17:08.600
 want to do this necessarily in-house. It could become a fairly complicated design if we've

01:17:08.600 --> 01:17:14.520
 got to move signal hardware, and we do want to determine what the impact is on the plantings

01:17:14.520 --> 01:17:19.480
 that are there. A lot of the landscaping, we're going to try and salvage as much of

01:17:19.480 --> 01:17:25.480
 it as we can, obviously, or maybe move it to other areas around the crossing. But that's

01:17:25.480 --> 01:17:29.960
 our next step is that consultant contract, and we hope to have that in place and be able

01:17:29.960 --> 01:17:36.080
 to bring a contract to council for approval if need be, if the dollar amount is high enough

01:17:36.080 --> 01:17:41.480
 in the month of January, so if not, then early February. So with that, I believe that is

01:17:41.480 --> 01:17:46.480
 the last thing I've got, and I'll stop sharing and take questions.

01:17:46.480 --> 01:17:55.880
 Questions? You're nearly about to ask something. Go ahead.

01:17:55.880 --> 01:18:04.120
 Well, maybe a question, maybe just a statement. So on the diagonal crossway, will there be

01:18:04.120 --> 01:18:10.080
 on the all-way crossing, will there be paintings as well?

01:18:10.080 --> 01:18:14.740
 Yes, yes. We'll have to modify the signals. We'll have to put push buttons close to those

01:18:14.740 --> 01:18:19.080
 ramps, and then we'll have the accessible ramps themselves, and then the markings that

01:18:19.080 --> 01:18:25.120
 go across. The other way to do the, what they call the ped scramble, this all-way crossing,

01:18:25.120 --> 01:18:31.640
 is to simply color the entire intersection, but we've got a lot of pavers and we've got

01:18:31.640 --> 01:18:37.200
 a lot of treatments down there. I think just the regular white markings will be adequate.

01:18:37.200 --> 01:18:43.480
 Anything else? All right. Thank you.

01:18:43.480 --> 01:18:44.480
 All right, thank you.

01:18:44.480 --> 01:18:54.680
 A lot of good stuff going on. So we're at concluding remarks. Is that what it's called?

01:18:54.680 --> 01:19:01.360
 Concluding items. Okay. I'm going to go to Councilmember Ryan, because he so hogs the

01:19:01.360 --> 01:19:02.360
 spotlight.

01:19:02.360 --> 01:19:14.080
 Yeah, yeah. So true. Thank you, Chair. We used to have a matrix for mobility that I

01:19:14.080 --> 01:19:20.000
 haven't seen in the last few meetings. I'm wondering if there was a reason, or I guess,

01:19:20.000 --> 01:19:24.080
 if it's possible to bring it back, I'd like to see it come back. One of the items I had

01:19:24.080 --> 01:19:31.880
 on that matrix was any of the major projects, and some of them got picked up by ITS, by

01:19:31.880 --> 01:19:37.760
 John Bolster's group on that sheet, but not all of them did. Some of the other big projects

01:19:37.760 --> 01:19:43.240
 that I think about are the other Bonneberry phases and Hickory Street that I'd like to

01:19:43.240 --> 01:19:48.240
 see in more than just that one line that we have on the Friday reports.

01:19:48.240 --> 01:19:55.280
 Sure. Councilmember Ryan, we can absolutely work through bringing back that matrix and

01:19:55.280 --> 01:20:00.520
 adding additional items as they come up and working through the agenda. If there are some

01:20:00.520 --> 01:20:05.840
 standard items that you want to see, something that we make an update to on the monthly basis,

01:20:05.840 --> 01:20:10.960
 we absolutely can do that. So we'll work to recreate that matrix and make sure that the

01:20:10.960 --> 01:20:15.640
 items that are appropriate are on there and be able to fulfill that for you. That's no

01:20:15.640 --> 01:20:16.640
 problem at all.

01:20:16.640 --> 01:20:20.240
 I think it's sort of anything bigger than a bread box, right? I mean, we kind of know

01:20:20.240 --> 01:20:26.240
 what the major items are. I trust you to draw the line, but I agree with Councilmember Ryan,

01:20:26.240 --> 01:20:33.000
 you know, whether it's Textud or City, we kind of want to see that overview.

01:20:33.000 --> 01:20:39.200
 Sure. I think sometimes it's very interesting to see the projects that are included in Mr.

01:20:39.200 --> 01:20:43.200
 Polster's report. Some of them are, you know, kind of projects that also Textud is working

01:20:43.200 --> 01:20:47.800
 with us on and so we can work to provide that update to some of those major projects without

01:20:47.800 --> 01:20:51.440
 a problem. That's no issue at all.

01:20:51.440 --> 01:20:55.200
 Councilmember Briggs?

01:20:55.200 --> 01:20:58.720
 Thank you. Also, I was wondering about the matrix as well, because I know there were

01:20:58.720 --> 01:21:04.960
 a few items that were listed on there still. So I just want to go ahead and plug those.

01:21:04.960 --> 01:21:11.160
 I know that the road diet for Carol was something that I had asked for and I think was coming

01:21:11.160 --> 01:21:15.360
 back at some point. Just want to throw that out there to see if that was still on there

01:21:15.360 --> 01:21:25.700
 and add a couple more as I'm leaving. I'd like to see you guys discuss the Cyclodea

01:21:25.700 --> 01:21:32.200
 Open Streets event maybe next year if that would be a possibility. And also, I know that

01:21:32.200 --> 01:21:38.240
 Bell is closed right now for, I think, water distribution, but in the process I mentioned

01:21:38.240 --> 01:21:45.120
 that it was suggested to maybe be closed permanently and it opened up some conversation. So if

01:21:45.120 --> 01:21:52.240
 you guys could discuss that or have a presentation on the future of Bell as with the mobility

01:21:52.240 --> 01:21:58.960
 discussion coming up. I think that would be helpful for individuals out here. Thank you.

01:21:58.960 --> 01:22:08.000
 Well, if I may, a couple items. About two years ago, I asked your predecessors to put

01:22:08.000 --> 01:22:13.680
 together a map just so we could see holistically. It might be something that would be good right

01:22:13.680 --> 01:22:20.480
 after John's, you know, here's all the money page. It would be actually a sequence of overlays.

01:22:20.480 --> 01:22:25.160
 Tell me if this is like a ridiculously heavy lift, but if not, I think it would be useful.

01:22:25.160 --> 01:22:31.000
 A map that shows here's everything being worked on in the present timeframe, whether text

01:22:31.000 --> 01:22:37.160
 out or city. Then next layer would be here's everything in the next cycle. I don't know

01:22:37.160 --> 01:22:42.320
 what the reasonable time cuts are. I don't want to be arbitrary about it, but you know,

01:22:42.320 --> 01:22:47.000
 maybe it's construction season if there is such a thing. So for simplicity sake, let's

01:22:47.000 --> 01:22:52.680
 say here's the 2020 view, here's the 2021 view, everything that's going on. What's our

01:22:52.680 --> 01:23:01.680
 city look like? You know, and then subsequent years and, you know, the ability to overlay

01:23:01.680 --> 01:23:08.680
 to say here's everything that's going to happen. It definitely led to just our clear perception

01:23:08.680 --> 01:23:15.240
 among us that oh, every way in or out of DEN is going to be getting worked on at the same

01:23:15.240 --> 01:23:20.400
 time. You know, it's something to just be able to understand and communicate. So, you

01:23:20.400 --> 01:23:27.160
 know, I'd be interested in knowing whether that's reasonable, helpful to you, and not,

01:23:27.160 --> 01:23:34.000
 you know, not just a backbreaking lift, but you have to answer that now. And then lastly,

01:23:34.000 --> 01:23:40.880
 I would just like to comment that participation in these council committees is entirely optional

01:23:40.880 --> 01:23:47.060
 for council members, and council member Briggs has served on this committee and many, many

01:23:47.060 --> 01:23:58.160
 others willingly and energetically and constructively. And I'm grateful for all of her participation

01:23:58.160 --> 01:24:05.520
 to date. I know we'll have other opportunities to wish you well in your next endeavors, but

01:24:05.520 --> 01:24:10.040
 from the point of view of this committee, thank you.

01:24:10.040 --> 01:24:16.560
 Thank you. And thanks to staff for all your hard work. Thank you.

01:24:16.560 --> 01:24:20.340
 With that, we will adjourn at 1025.

01:24:20.340 --> 01:24:24.240
 Have a good day.