City Council Mobility & Infrastructure Committee · Tuesday, September 12, 2023 · City Council Digest

3. APPROVAL OF MINUTES

Minutes of July 11, 2023

packet pp.5–6

▶ Watch from 2:04 Open packet at p.5 ↗

Staff report:

APPROVAL OF MINUTES a) 07-11-23 City Council Mobility & Infrastructure Page (1) Committee Minutes CITY OF ISSAQUAH City Council Mobility & Infrastructure Committee 6:30 PM Council Chambers, 135 E. July 11, 2023 MINUTES Sunset Way, Issaquah WA

4. AGENDA ITEMS

Sewer Master Plan ID 1456

60 min · Matt Ellis, Utility Engineering Manager · packet pp.7–41

Topics: Water

Previously discussed: Environmental Board · Jul 12, 2023

▶ Watch from 0:31 Open packet at p.7 ↗

Staff report:

Meeting Date September 12, 2023

Intelligent Transportation System Draft Plan ID 1525

30 min · Emily Moon, Director, Public Works · packet pp.43–134

Topics: Transportation

▶ Watch from 0:40 Open packet at p.43 ↗

Staff report:

City Administration recommends: • The Committee review the plan and, if no changes or only minor changes are needed, • The Committee recommend the ITS Plan be considered for City Council acceptance.

1743 segments .txt ↗

0:02 ↗ uh good evening and welcome I'm council

0:05 ↗ member Chris Ray and I will be chairing

0:06 ↗ this evening's meeting I'm going to call

0:08 ↗ the September 12 2023 city council

0:11 ↗ mobility and infrastructure committee to

0:13 ↗ order uh with me this evening as council

0:15 ↗ member Barbara D Michelle Deputy council

0:17 ↗ president Zach call

0:20 ↗ um has an excuse absence and will not be

0:22 ↗ with us this evening

0:24 ↗ so we have a few things on the agenda

0:27 ↗ this evening we're going to do public

0:30 ↗ comment

0:31 ↗ um and then we have two agenda items uh

0:33 ↗ ID 1456 Sewer Master Plan nid 1525 the

0:38 ↗ intelligent transportation

0:40 ↗ system draft plan

0:45 ↗ um first on the agenda is public comment

0:47 ↗ so members of the public May address the

0:49 ↗ council this time in person or virtually

0:51 ↗ those who signed up Advance May comments

0:53 ↗ will be called first

0:54 ↗ if you are joining us virtually and

0:56 ↗ would like to make comments please raise

0:57 ↗ your virtual hand

0:59 ↗ if you're on the phone press star three

1:00 ↗ if you're joined by a computer

1:02 ↗ smartphone look for a hand icon the

1:05 ↗ option may vary depending upon your

1:07 ↗ device

1:08 ↗ uh if you're in the room and have not

1:09 ↗ signed up I will ask for speakers for

1:11 ↗ closing this part of the meeting there

1:14 ↗ will also be another public comment

1:16 ↗ opportunity following Council committee

1:19 ↗ questions

1:22 ↗ um on each agenda item so

1:24 ↗ um clerk has anyone signed up to make a

1:26 ↗ public comment this evening

1:29 ↗ sure Ray no one has signed up previously

1:32 ↗ and we have no virtual attendees at this

1:34 ↗ moment I'm crushed

1:36 ↗ uh anybody in the room want to make

1:38 ↗ public comments no okay then we're gonna

1:41 ↗ we're gonna move on if when we get to

1:43 ↗ the the uh each of the agenda items

1:46 ↗ someone does want to make public comment

1:47 ↗ I'll read through the rules

1:49 ↗ but let's get on with our agenda this

1:52 ↗ evening and first thing is the approval

1:54 ↗ of the minutes from our July 11th

1:56 ↗ meeting

1:57 ↗ um if there are any objections or

1:59 ↗ comments on the uh

2:01 ↗ minutes no all right without objection

2:04 ↗ we will approve the minutes from July

2:06 ↗ 11th

2:07 ↗ moving on to our first agenda item which

2:10 ↗ is ID 1456 the Sewer Master Plan uh Matt

2:14 ↗ Ellis utilities engineering manager will

2:16 ↗ be presenting

2:18 ↗ and we will turn it over to Matt

2:26 ↗ all right thank you council members at

2:29 ↗ LS utility engineering manager and we're

2:31 ↗ presenting on the Sewer Master Plan and

2:33 ↗ specifically on some policy questions

2:37 ↗ the purpose is to provide an update on

2:40 ↗ the Sewer Master Plan and discuss all

2:42 ↗ policy statements under development

2:43 ↗ within the Sewer Master

2:47 ↗ um

2:48 ↗ so we have three policy statements the

2:50 ↗ first is the transition of on-site

2:52 ↗ septic systems to City sewers to the

2:54 ↗ city sewer system this was already

2:56 ↗ discussed with Mobility infrastructure

2:59 ↗ in February will not be discussed

3:01 ↗ tonight

3:02 ↗ uh the uh other elements which we will

3:05 ↗ be discussing tonight include

3:06 ↗ maintaining sewer capacity with two

3:09 ↗ policy topics inflow and infiltration

3:12 ↗ capacity impacts and developer capacity

3:15 ↗ impacts we will also discuss policy on

3:17 ↗ our fats oils and grease or our fog

3:20 ↗ program management

3:24 ↗ so the two the direction we will need

3:25 ↗ tonight is on maintaining sewer system

3:28 ↗ capacity uh regarding inflow and

3:31 ↗ infiltration capacity impacts is the

3:33 ↗ mobility infrastructure committee agree

3:35 ↗ with an ini capacity uh impact threshold

3:38 ↗ and for part two uh

3:42 ↗ does the mobility infrastructure

3:43 ↗ committee agree with the developer

3:45 ↗ contributions based on the amount of

3:47 ↗ flow contributing to surcharge and then

3:49 ↗ for policy three fatsoils and grease

3:52 ↗ management is the mobility

3:53 ↗ infrastructure committee agree with a

3:55 ↗ retroactive clause for installing a

3:58 ↗ grease intercept

4:01 ↗ so we'll briefly go through a timeline

4:03 ↗ in the background for the master plan uh

4:06 ↗ provide a overview of the master plan to

4:10 ↗ date uh we'll go through the policies

4:12 ↗ that we'll be discussing uh we will not

4:15 ↗ be talking about the on-site septic

4:16 ↗ system uh code revisions I apologize I

4:19 ↗ apologize for that being on there we

4:20 ↗ will be talking about surcharging

4:22 ↗ capacity protocol CIP development to

4:24 ↗ date fast and then the fog policy

4:30 ↗ here's our timeline we are here today

4:33 ↗ presenting on our proposed policy in

4:35 ↗ October we will be completing the master

4:37 ↗ plan including chapters and presenting

4:39 ↗ red lines to code to mobility and

4:42 ↗ infrastructure we'll also be submitting

4:44 ↗ sipa documents

4:50 ↗ uh in November after Consulting uh

4:53 ↗ consolidating comments we plan to submit

4:54 ↗ the draft master plan to King County

4:56 ↗ neighboring jurisdictions and ecology

4:59 ↗ for concurrent review this process may

5:02 ↗ take some time our original goal was to

5:04 ↗ adapt them adopt the master plan by the

5:06 ↗ end of the year but in reality the

5:08 ↗ review by external agencies May delay

5:11 ↗ formal adoption until we receive

5:13 ↗ concurrence and address any lingering

5:15 ↗ comments so under this current plan we

5:17 ↗ will adopt the official master plan in

5:20 ↗ the first quarter of 2024.

5:24 ↗ a little bit of background the city of

5:27 ↗ issaquah's Sewer Master Plan was last

5:28 ↗ updated in 2002.

5:31 ↗ we've grown from a town of 11

5:33 ↗ 000 people to about 40 000 residents

5:36 ↗ including mixed use and a large

5:38 ↗ commercial District

5:39 ↗ large sections of the city were either

5:41 ↗ built or Incorporated since the last

5:43 ↗ sewerp master plan was developed we were

5:45 ↗ in desperate need

5:47 ↗ to evaluate our system one of the first

5:50 ↗ steps I was creating a new master plan

5:52 ↗ uh uh was

5:55 ↗ calculating our hydraulic model this

5:57 ↗ allowed us to determine how certain

5:59 ↗ demands impacted our system as well as

6:01 ↗ evaluate the effect of intrusion and

6:03 ↗ infiltration someone referred to as ini

6:06 ↗ head on the system this is where Storm

6:08 ↗ surface or groundwater unintentionally

6:11 ↗ enters the sewer system

6:14 ↗ ini has major impacts on sewer capacity

6:16 ↗ and create environmental concerns if a

6:19 ↗ large connection is identified and

6:21 ↗ creates costly Downstream treatment

6:22 ↗ which is managed by King County all

6:25 ↗ sewer systems have ini and the goal is

6:27 ↗ to effectively but economically manage

6:30 ↗ and reduce the amount of ini entering

6:32 ↗ the source

6:33 ↗ work included installing a flow meters

6:35 ↗ and identifying flows and calibrating

6:37 ↗ and recalibrating the model finally we

6:39 ↗ set up identifying a storm and we felt

6:42 ↗ that we felt our system should be able

6:43 ↗ to handle

6:46 ↗ as a first step we provided our

6:47 ↗ consultant with our GIS system in a

6:49 ↗ series of record drives to update the

6:51 ↗ model we then installed a series of flow

6:54 ↗ meters we set about calibrator model

6:57 ↗ using using recently determined water

6:59 ↗ system demands from the water system

7:02 ↗ pipe slopes and evaluated the system

7:04 ↗ developed our dry weather conditions we

7:07 ↗ made sure the meters were in place for a

7:09 ↗ series of storm events so we could check

7:12 ↗ the performance during major storm

7:14 ↗ events we had two tenure storm events

7:17 ↗ during the period that we had

7:23 ↗ uh so this is our current sewer system

7:25 ↗ our pipes are in roon and the Sammamish

7:27 ↗ Plateau Water District's boundaries in

7:29 ↗ Gray

7:30 ↗ we have about 88 miles of conveyanced

7:32 ↗ pipe and four sewer lift stations we do

7:35 ↗ not provide treatment within the city we

7:36 ↗ currently convey Wastewater to King

7:38 ↗ County Wastewater transmission uh

7:40 ↗ through King County Wastewater

7:42 ↗ transmission Mains to a regional

7:45 ↗ treatment facility

7:47 ↗ we have calibrated our model to design

7:49 ↗ storm and identified areas where we

7:51 ↗ suspect inflow infiltration to be

7:53 ↗ currently occurring

7:55 ↗ we also evaluated future growth and

7:57 ↗ demands and evaluated issues with

7:59 ↗ capacity leaks and how that will impact

8:02 ↗ the environment all this was help work

8:04 ↗ helped influence the CIP Capital

8:07 ↗ Improvement plan that was recently

8:09 ↗ adopted

8:11 ↗ here again is the Basin map and it shows

8:16 ↗ our system Broken Out by Basin the blue

8:18 ↗ and green pipes in the image were the

8:20 ↗ pipes we modeled and we realized it

8:22 ↗ would not be a cost-effective to insert

8:24 ↗ every pipe in the city in the city into

8:26 ↗ the model we focused on truck Mains and

8:29 ↗ Mains that served a large population

8:32 ↗ so that boils down to our first uh

8:34 ↗ policy statement and that's surcharge

8:37 ↗ the image on the screen is basically the

8:39 ↗ worst case scenario where sewer is

8:41 ↗ coming out of the manhole this is not in

8:43 ↗ the city this is a stock photo

8:45 ↗ uh

8:47 ↗ and so when is it an issue uh we had to

8:49 ↗ evaluate the surcharge performance

8:51 ↗ criteria we didn't want sewer to ever

8:52 ↗ back up out of a manhole during a

8:54 ↗ current or future conditions or during a

8:57 ↗ storm event

8:57 ↗ we wanted to make sure I and I and our

8:59 ↗ system was a measurable amount that our

9:01 ↗ system could handle there's no way we

9:03 ↗ can effectively remove all ini entered

9:05 ↗ into the sewer system

9:06 ↗ so we've evaluated the system we wanted

9:08 ↗ to wanted to be good stewards but not

9:11 ↗ expend funds to search out every last

9:13 ↗ impact to buy an ions

9:15 ↗ this could cost millions of dollars

9:18 ↗ we want our our system to function

9:20 ↗ properly we understand that some storm

9:22 ↗ water will enter the system the amount

9:24 ↗ that enters is in line with best

9:25 ↗ practices County thresholds and their

9:28 ↗ neighboring jurisdictions in that regard

9:30 ↗ we looked at critical facilities in

9:32 ↗ areas that we are seeing a lot of ionai

9:35 ↗ interests

9:40 ↗ so we have uh we have especially uh

9:43 ↗ concerned about our lift station

9:45 ↗ performance during storm events and how

9:47 ↗ I I impacts those pumps make sure that

9:50 ↗ they're not getting inundated and that

9:52 ↗ they function properly to reduce wear

9:54 ↗ and tear and extend life performance

9:56 ↗ finally we have a goal to reduce the

9:58 ↗ amount of storm water entering the King

10:00 ↗ County

10:02 ↗ uh uh one of our first orders of uh

10:16 ↗ one of our first orders of business was

10:18 ↗ determine the size of the storm event

10:19 ↗ that our system could handle knowing

10:21 ↗ that someone I could could come into the

10:23 ↗ system The King The King County has a

10:25 ↗ 20-year storm event uh as calibration we

10:29 ↗ elected to do similar and our design

10:30 ↗ storm is between a 20 and 25 year storm

10:33 ↗ a theoretical storm event but it's based

10:36 ↗ on an actual 20 February 2022 storm this

10:41 ↗ is based on rain gauge data we felt

10:42 ↗ using an actual storm it was a useful

10:45 ↗ metric to make sure our system could

10:46 ↗ manage large storm events and not based

10:49 ↗ on theoretical data it all boils down to

10:51 ↗ a policy statement and maintaining our

10:53 ↗ sewer

10:55 ↗ this is the city has two distinct

10:57 ↗ geographic features that we we need to

10:59 ↗ do account for when considering those

11:01 ↗ policy we have the shallow valley floor

11:03 ↗ where sewer lines are typically flat

11:05 ↗ uh and and located in located very

11:09 ↗ shallow below the surface in these areas

11:11 ↗ it's important that we monitor ini

11:13 ↗ entering nurses an abstringent protocol

11:15 ↗ for either reducing the ini or upsizing

11:17 ↗ pipe backup or surcharging and shallow

11:20 ↗ pipes means that there is more risk of

11:22 ↗ sewer backing up into manholes and

11:24 ↗ potentially coming out of the top and

11:25 ↗ creating a health hazard this is roughly

11:28 ↗ half

11:29 ↗ the other areas on mountainsides where

11:31 ↗ sewer lines are on steep grates and can

11:33 ↗ be off oftentimes or deeper in these

11:35 ↗ areas it's not as important where we

11:37 ↗ have strict requirements because if

11:38 ↗ sewer does back up into a sewer line or

11:41 ↗ corresponding manhole pipe is so deep it

11:43 ↗ would be less of a

11:44 ↗ additional additionally it would be a

11:46 ↗ exceedingly expensive to replace site

11:52 ↗ here's an image of a storm event that

11:54 ↗ for a certain section of pipe in our

11:56 ↗ system

11:57 ↗ gray is our normal diurnal use of a

12:00 ↗ section so day and night

12:03 ↗ blue is a storm in question as you can

12:05 ↗ see we observed a lot of storm surface

12:07 ↗ and groundwater entering those

12:08 ↗ particulars

12:10 ↗ this is this is the worst location that

12:13 ↗ we kind of

12:15 ↗ not all our pipe segments look like this

12:17 ↗ this is basically how we model the

12:19 ↗ system and determine areas to focus on

12:21 ↗ for our CIP development

12:23 ↗ okay Matt can I ask you a quick question

12:25 ↗ about this graph yes

12:26 ↗ um so I I actually had this question

12:28 ↗ like what's the ini as a percentage of

12:31 ↗ normal flow and it looked like it's

12:33 ↗ pretty doing a big event it's pretty

12:35 ↗ substantial yes um what's our capacity

12:37 ↗ is there a capacity line you can draw

12:39 ↗ across on this graph I took it out of

12:41 ↗ this graph the the the presentation but

12:44 ↗ it is backing up into the manhole of

12:46 ↗ this location and it's pretty close to

12:48 ↗ the surface okay most locations it's not

12:52 ↗ so when we have that kind of a storm we

12:54 ↗ we run the risk of having some

12:57 ↗ we overflow we evaluated up to the 100

13:00 ↗ Year storm and we weren't

13:02 ↗ charging out of the top but we were we

13:05 ↗ were getting pretty close to that so our

13:07 ↗ protocol is

13:09 ↗ two times the uh depth of the pipe

13:15 ↗ uh I'm sorry one height of the pipe so

13:18 ↗ basically we don't want it to get into

13:19 ↗ the manholes the flat flat part so the

13:22 ↗ in the valley and then in the deep deep

13:24 ↗ uh deep or steep areas we'd allow it to

13:28 ↗ go up to uh twice the

13:32 ↗ yeah because it won't overflow yeah at

13:35 ↗ that point but down the valley where

13:37 ↗ where we're not very deep

13:39 ↗ we're gonna be a little more strict yeah

13:41 ↗ okay thanks

13:47 ↗ as I mentioned we are proposing two

13:49 ↗ different thresholds for investigating

13:50 ↗ and upsizing or repairing type segments

13:53 ↗ our plan is to include upgrades segments

13:55 ↗ of pipe that meet the thresholders

13:58 ↗ to allow backup into manholes during

14:00 ↗ storm events then deep pipes but not in

14:02 ↗ Shallow pipes during storm event

14:04 ↗ plan to be proactive and upsizing for

14:06 ↗ shallow pipes and more lenient the

14:08 ↗ deeper the deeper pipes on hills and

14:11 ↗ deeper segments will allow for more

14:13 ↗ ionize during storm event this allows us

14:15 ↗ to balance the costs we're upsizing with

14:17 ↗ other improvements for our sewer system

14:20 ↗ the alternative to this is to have one

14:22 ↗ threshold basically if sewer exceeds the

14:24 ↗ volume of pipe during a storm event to

14:27 ↗ correct the issue no matter where the

14:28 ↗ pipe is loaded

14:30 ↗ this could ultimately mean our system

14:31 ↗ has more capacity and reduce the amount

14:34 ↗ of storm water

14:36 ↗ it would be much more expensive to

14:37 ↗ implement

14:39 ↗ you have to not pursue this option

14:40 ↗ because it would create more capital

14:42 ↗ projects Place more of a burden on the

14:45 ↗ city's sewer fund alleviate a concern

14:47 ↗ that wasn't in our opinion the most

14:50 ↗ important element

15:01 ↗ uh unfortunately the CIP had been

15:03 ↗ developed before the master plan

15:05 ↗ based on the proposed policy we

15:07 ↗ evaluated for current demands and future

15:09 ↗ growth scenarios

15:11 ↗ and the cipa correlated

15:14 ↗ we had an it we we had to assume a

15:16 ↗ degradation over time meaning our system

15:18 ↗ will contribute more ini in the future

15:20 ↗ the existing pipes and manholes in our

15:22 ↗ system were not maintained

15:24 ↗ you're using the county standard to

15:26 ↗ seven percent increase in ini entering

15:28 ↗ the sewer system for decades

15:30 ↗ the good news is we have a pretty

15:32 ↗ healthy sewer system based on the above

15:34 ↗ criteria criteria we have only one

15:37 ↗ section of pipe that we added to the CIP

15:39 ↗ for investigation

15:41 ↗ this section of pipe is located behind

15:43 ↗ the fish hatchery and on Newport Way

15:46 ↗ this is the Pikes pipe segment that I

15:48 ↗ showed in the previous

15:49 ↗ it is now since it's now on the CIP

15:51 ↗ we've allocated funds to investigate the

15:53 ↗ problem and alleviate the issue our goal

15:56 ↗ is to investigate Upstream sewer

15:57 ↗ connections to see if we find a reason

15:59 ↗ for the ini reducing the source of ini

16:02 ↗ is the most cost effective solution

16:05 ↗ if we can't pinpoint the issue we will

16:07 ↗ consider upsizing the pipe segment

16:09 ↗ segment

16:11 ↗ a couple more questions for you I don't

16:13 ↗ know if you don't mind me kind of

16:14 ↗ getting as we go

16:15 ↗ um but one of them is so as the pipes

16:19 ↗ get older they're more porous and that's

16:22 ↗ why we get ini because uh water can seep

16:25 ↗ into them is that kind of the source of

16:27 ↗ that that's some of it sometimes it's

16:28 ↗ settlement sometimes it could be

16:30 ↗ development has you know another pipe

16:32 ↗ has come in close to that

16:34 ↗ sewer line and and so there's

16:36 ↗ bad connections it could be a whole list

16:39 ↗ of things and so we do have a a annual

16:42 ↗ maintenance program that's part of the

16:44 ↗ CIP to maintain both our manholes as

16:48 ↗ well as our pipes sometimes that means

16:50 ↗ lining the sewer pipes we've been doing

16:52 ↗ that in the South Lakes Sammamish

16:54 ↗ neighborhoods lately for the last five

16:56 ↗ years uh just because those pipes are

16:59 ↗ pretty old and they're all concrete

17:02 ↗ pipes so they they have more of a

17:04 ↗ tendency to allow more water to come

17:06 ↗ into them also High groundwater which

17:08 ↗ makes even worse

17:10 ↗ um did we also find that over time the

17:12 ↗ pipes the capacity of pipes the grades

17:14 ↗ over time also uh not as much because

17:18 ↗ again that was more based on demand so

17:19 ↗ we looked at it from a demand scenario

17:22 ↗ of uh I think it was a 2040 uh with the

17:26 ↗ growth escalation based on the

17:29 ↗ water system master plan uh assumptions

17:33 ↗ we made there plus double checking with

17:35 ↗ our senior with our long-range planner

17:38 ↗ great thank you

17:44 ↗ so uh this leads to policy section 2B

17:48 ↗ developer capacity

17:54 ↗ we want to make we want to make sure

17:55 ↗ under future scenarios that if a large

17:57 ↗ development is constructed corresponding

17:59 ↗ pipes evaluated under this policy

18:02 ↗ developers would be required to analyze

18:04 ↗ the impacts of the development on the

18:05 ↗ existing sewer system

18:07 ↗ if model development is determined to

18:09 ↗ create a surcharge issue for a fight

18:10 ↗ segment outlined in the root the first

18:13 ↗ part of the policy develop a developer

18:15 ↗ will need to contribute to improvements

18:17 ↗ within the cities

18:19 ↗ this is for large private development

18:21 ↗ this does not pertain to single family

18:22 ↗ home renovations or minor Construction

18:27 ↗ uh and here's the table uh if a modeled

18:30 ↗ pipe segment is subject to surcharging

18:32 ↗ and a developer plans to connect to the

18:34 ↗ pipe segment uh then Financial

18:36 ↗ participation for improvements poses

18:40 ↗ uh if surcharging is occurring and the

18:42 ↗ plan development contributes less than

18:44 ↗ 10 of the flow to the pipe they're not

18:46 ↗ responsible for updating the main

18:48 ↗ however if the plane development

18:50 ↗ contributes over 80 of the flow to a

18:52 ↗ pipe segment resulting in search

18:54 ↗ they're responsible for a hundred

18:56 ↗ percent

18:58 ↗ we don't have explicit examples of this

19:00 ↗ uh in our in this city or in others but

19:03 ↗ this is similar to storm water

19:04 ↗ evaluation uh

19:06 ↗ we want to make sure that the growth

19:08 ↗ pays for growth and improvements to the

19:10 ↗ city system is paid for by the

19:11 ↗ responsible parties not rate payers a

19:14 ↗ significant contributor of waste

19:16 ↗ additive

19:18 ↗ so our question to the board tonight is

19:20 ↗ do you concur with this policy statement

19:21 ↗ requiring developers to support sewer

19:23 ↗ upsizing they contribute a measurable

19:26 ↗ amount of

19:30 ↗ and as we go down as I previously

19:33 ↗ previously said the CIP was adopted

19:35 ↗ before completion of the map

19:38 ↗ uh we identified critical critical

19:40 ↗ infrastructure to evaluate such as our

19:43 ↗ existing lift station

19:44 ↗ we included select sewer extensions into

19:47 ↗ the current uh into currently unsured

19:49 ↗ neighborhoods located within the Hundred

19:51 ↗ Year floodplain and within Shoreline

19:53 ↗ buffers uh based on past environmental

19:56 ↗ board and Mobility infrastructure

19:58 ↗ discussion and it included areas of high

20:01 ↗ search

20:03 ↗ so here are the four projects in the CIP

20:06 ↗ who are based on the very preliminary

20:08 ↗ Masters

20:10 ↗ here's how we are going to implement

20:12 ↗ them over the next five years

20:15 ↗ that includes the upper Sycamore

20:17 ↗ extension Highlands lift station

20:19 ↗ improvements South Newport Wildwood

20:21 ↗ sewer remediation that's the one I

20:24 ↗ showed earlier the highlands inflation

20:27 ↗ can you just say two sentences about

20:29 ↗ each one kind of what it is where it is

20:30 ↗ sure the upper Sycamore extension is

20:33 ↗ extending sewer into the Sycamore

20:36 ↗ neighborhood that has historically not

20:37 ↗ had sewer and we're

20:40 ↗ focusing on that

20:41 ↗ extension into

20:44 ↗ um under areas that are within the flood

20:47 ↗ plain uh right next to the creek the

20:50 ↗ highlands lift station improvements is

20:51 ↗ is basically improvements to the Sewer

20:54 ↗ lift station up in the highlands

20:56 ↗ uh South Newport and wildwood Resort

20:59 ↗ remediation is basically improving the

21:01 ↗ capacity of that sewer pipe behind the

21:03 ↗ fish hatchery

21:05 ↗ um or trying to alleviate the ini in the

21:08 ↗ high Highlands infiltration intrusion we

21:10 ↗ identified some ini up in the highlands

21:13 ↗ so it's kind of broad spectrum and

21:15 ↗ that's

21:22 ↗ that leads to fats oils and grease

21:29 ↗ I met one more question of course

21:30 ↗ council member Michelle yes uh could you

21:33 ↗ just go into a little bit more detail

21:34 ↗ about how we will

21:37 ↗ determine

21:39 ↗ um the percentage of developer uh

21:42 ↗ participation is that going to be after

21:45 ↗ the pipes are installed and then we

21:48 ↗ measure it or is it before the

21:51 ↗ development's been approved where where

21:53 ↗ in the development process is this is

21:57 ↗ going to be applied with the developer

21:59 ↗ that's a good question it would be

22:01 ↗ during the uh

22:03 ↗ proposal for the development so

22:05 ↗ basically they come in with a plan

22:06 ↗ they're going to have a high rise or a

22:08 ↗ larger part apartment complex

22:12 ↗ and they would have to connect to our

22:14 ↗ existing source so it's not their pipe

22:17 ↗ that we're evaluating where it's looking

22:18 ↗ at the city's sewer main uh paths just

22:22 ↗ Downstream to see if it is needing to be

22:25 ↗ upside okay all right thank you

22:32 ↗ that's what I was in Greece

22:34 ↗ as part of the Sewer Master Plan we also

22:36 ↗ took a look at our fog program we

22:38 ↗ completed a gap analysis and identified

22:40 ↗ one area of concern that is currently

22:43 ↗ not addressed

22:44 ↗ this does not impact the CIP but will

22:46 ↗ have impact on businesses around

22:49 ↗ businesses contributing fog to the

22:51 ↗ city's sewer system they have

22:53 ↗ appropriate grease interceptors

22:54 ↗ installed or best management practices

22:56 ↗ and

22:57 ↗ this became a requirement in the city in

23:00 ↗ 2014 when the fog program was last

23:03 ↗ however we found a gap in our current

23:05 ↗ code that we need to resolve although

23:08 ↗ all new Greece new Greece and uh Greece

23:11 ↗ generating establishments are required

23:13 ↗ to install grease interceptors a few

23:15 ↗ existing restaurants in town are still

23:17 ↗ operating without internet

23:19 ↗ due to their longevity as at a single

23:21 ↗ location and being grandfathered in

23:22 ↗ we're moving into a space where the

23:24 ↗ previous tenant didn't have a suitable

23:26 ↗ energy

23:28 ↗ I'd really get unregulated fats oils and

23:30 ↗ grease entering the system the system

23:33 ↗ has created blockages in the city's

23:35 ↗ sewer system which has created problems

23:37 ↗ for Downstream customers including

23:39 ↗ sewage backups inside Downstream

23:40 ↗ establishments

23:42 ↗ we're pursuing a retroactive clause for

23:44 ↗ Greece interception installation this

23:46 ↗ would have a financial burden on a few

23:48 ↗ existing establishments

23:50 ↗ We Believe between 10 and 14

23:52 ↗ establishments would be impacted by your

23:54 ↗ proposing requiring these establishments

23:56 ↗ to install a grease Interceptor for one

23:58 ↗ currently

24:00 ↗ retroactive Clause would require

24:02 ↗ existing business owners to actively

24:04 ↗ manage alcoholics the sewer in line with

24:07 ↗ other business establishments

24:09 ↗ a retroactive Clause would be in

24:11 ↗ alignment with neighboring jurisdictions

24:13 ↗ uh

24:14 ↗ typically neighbor neighboring

24:16 ↗ jurisdictions have instituted a

24:18 ↗ retroactive Clause between six months

24:19 ↗ one year as a high as three years for

24:23 ↗ businesses

24:25 ↗ requiring a grease Interceptor varies

24:28 ↗ depending on the size and type of

24:29 ↗ Interceptor installed it depends on the

24:32 ↗ amount of Grease producing

24:34 ↗ the actual sizing and price needs to be

24:36 ↗ completed by a license

24:39 ↗ work also requires a plumbing

24:41 ↗ all said and done the cost for an

24:43 ↗ Interceptor and permit would most likely

24:45 ↗ be three thousand to eight thousand

24:47 ↗ dollars for a standard restaurant

24:51 ↗ evaluated this we came to the conclusion

24:54 ↗ that businesses are just coming out of

24:55 ↗ covid

24:56 ↗ uh this requirement would be a financial

24:58 ↗ burden and requires permitting and

25:00 ↗ engineering

25:01 ↗ with that in mind six months to one year

25:04 ↗ maybe too short to require

25:06 ↗ establishments to install a grease

25:07 ↗ intercept but two to three years would

25:09 ↗ be ideal to allow businesses to budget

25:11 ↗ for this elicit quotes

25:18 ↗ so we did bring this to the

25:20 ↗ environmental board in July

25:23 ↗ the environmental board agreed with the

25:25 ↗ steered charging protocol and developer

25:27 ↗ contributions and had no comments on

25:29 ↗ these topics

25:31 ↗ they also generally agreed with the

25:32 ↗ addition of a retractive clause the

25:35 ↗ IMC 1638 regarding the fog regulation

25:40 ↗ at the meeting there was one

25:41 ↗ recommendation for a one-year window for

25:43 ↗ business

25:45 ↗ there's also discussion on who should be

25:48 ↗ responsible for payment either the

25:49 ↗ tenant business owner or the property

25:52 ↗ owner there's more internal discussions

25:54 ↗ we had on that uh last point the grease

25:57 ↗ Interceptor were installed outside of

25:59 ↗ establishment should be the property

26:01 ↗ owner's responsibility as it would be a

26:03 ↗ benefit to the property no matter what

26:05 ↗ type of tenant comes in in the future

26:07 ↗ and would be a larger a larger size

26:10 ↗ facility to accommodate a variety

26:12 ↗ installed inside it would be the

26:14 ↗ business owner's responsibility in size

26:16 ↗ for the specific business meaning the

26:18 ↗ tenant moves out the grease Interceptor

26:20 ↗ may not be sized correctly for the next

26:22 ↗ 10 days

26:24 ↗ friendly staff does not have a

26:25 ↗ recommendation on this there are many

26:28 ↗ complicated contract requirements

26:30 ↗ between tenants and Property Owners

26:32 ↗ regardless this element reports an

26:34 ↗ extended timeline for implementation

26:39 ↗ and we did have a second code revision

26:42 ↗ that we originally presented to the

26:43 ↗ environmental board that we would

26:45 ↗ require mobile food vendors and food and

26:47 ↗ beverage establishments including food

26:49 ↗ trucks and freestanding coffee stands to

26:52 ↗ develop and submit a gray water

26:54 ↗ management

26:55 ↗ if not managed properly gray water or

26:58 ↗ other waste streams can be discharged

26:59 ↗ with a storm system and or surface water

27:02 ↗ made this regionally as a policy we were

27:04 ↗ proposing but after discussion with the

27:06 ↗ environmental board we learned there are

27:08 ↗ Regional discussions on the subject

27:10 ↗ matter that may influence how we address

27:12 ↗ this issue

27:13 ↗ we also we are also about to implement

27:16 ↗ an asset management program within this

27:18 ↗ and are interested in how this can

27:20 ↗ support this

27:23 ↗ from an environmental standpoint there's

27:25 ↗ need to implement this program and

27:26 ↗ policy we want to table the topic until

27:29 ↗ the in-house resources are in line we

27:31 ↗ learned how this is managed from a

27:33 ↗ regional

27:36 ↗ hey Matt just I'm kind of going back to

27:39 ↗ the yes the fog filters

27:42 ↗ um have we had any conversations with

27:43 ↗ local business owners about their their

27:46 ↗ thinking on this what their preferences

27:48 ↗ are if they have any insights we have

27:51 ↗ not

27:59 ↗ when you say one recommendation for a

28:02 ↗ one-year installation was that one

28:04 ↗ person that was one person oh okay and

28:06 ↗ so the rest of the environmental board

28:08 ↗ like the staff recommendation is that

28:11 ↗ what is that what this is the

28:14 ↗ recommendation of a retroactive Clause

28:15 ↗ but there was no those that was the only

28:18 ↗ direction that we provided we were

28:21 ↗ provided

28:24 ↗ oh okay thanks

28:27 ↗ so again here are the uh the direction

28:29 ↗ needed is uh the policy two maintaining

28:32 ↗ sewer capacity uh

28:37 ↗ uh 2A and flow and infiltration capacity

28:40 ↗ impact this is the mobility

28:42 ↗ infrastructure committee agree with the

28:43 ↗ ini capacity impact

28:47 ↗ and then uh 2B developer capacity impact

28:51 ↗ is the mobility infrastructure committee

28:53 ↗ agree with the developer country

28:54 ↗ based on the amount of flow contributing

28:56 ↗ charge

28:57 ↗ and then policy three is a Mobility

28:59 ↗ infrastructure committee agree with a

29:01 ↗ retroactive cause for installing

29:03 ↗ I apologize I do have one year on there

29:06 ↗ but I think we are the staff is

29:08 ↗ recommending

29:09 ↗ every year

29:15 ↗ Michelle any additional questions

29:20 ↗ I I kind of interrupted you as we went

29:22 ↗ so I'm pretty satisfied so we are at now

29:25 ↗ at another public comment opportunity

29:27 ↗ clerk is there anybody

29:31 ↗ um online who is best interested making

29:35 ↗ public comment at this time

29:38 ↗ here array we do have an online attendee

29:40 ↗ I don't see a hand raised at this point

29:44 ↗ online

29:49 ↗ coming up to the the lectern state your

29:52 ↗ name relationship to the city and

29:54 ↗ be sure

30:01 ↗ my name is Catherine Kirkendall I

30:03 ↗ recently moved here from Northern

30:04 ↗ California where I flee from um four

30:07 ↗ fires the size of LA and lost my son my

30:10 ↗ father my I have brothers up here and

30:13 ↗ lived here before in Redmond and was

30:15 ↗ really here right and since I got to

30:17 ↗ King County my U-Haul was stolen and I

30:19 ↗ was attacked and

30:22 ↗ um

30:22 ↗ I I mean I'm sorry I had a counselor

30:25 ↗ because of what happened in California

30:26 ↗ and I had I was paying for neurofeedback

30:29 ↗ therapy which is I think when my

30:30 ↗ counselor my doctors say hey I have the

30:33 ↗ best coping skills I've ever seen

30:34 ↗ because I didn't have furniture I got a

30:36 ↗ studio in Seattle it was a nightmare ODS

30:40 ↗ it was I've never seen anything like it

30:42 ↗ um I just didn't know the neighborhood I

30:43 ↗ was moving into so I got out here to

30:44 ↗ Issaquah I'm a health food cook at the

30:46 ↗ Medina country club and at PCC

30:49 ↗ um I just got moved into this whole

30:51 ↗ nightmare of what's happened in my life

30:53 ↗ life those things at you it's how you

30:55 ↗ get through it is might have my Outlook

30:57 ↗ is but I moved into a place in Issaquah

30:59 ↗ and the sewage is coming up has been

31:02 ↗ doing that for a year the water is

31:04 ↗ coming out they're not nope and I don't

31:06 ↗ know who I figured this was the right

31:08 ↗ place to find out I can wait till after

31:09 ↗ the meeting to see where I can get

31:11 ↗ research somebody to help they just act

31:13 ↗ like it's my fault they won't even give

31:14 ↗ me my deposit time move I go but I'm not

31:16 ↗ even really moved in and I got an 11 000

31:20 ↗ loan to get moved here this all the

31:23 ↗ other you know just so I I'm looking for

31:26 ↗ resources to help me I've I've just

31:28 ↗ swing on for two and a half months I

31:30 ↗ lost two months worth of wages and

31:33 ↗ um

31:34 ↗ I'm at a point where I just kind of need

31:36 ↗ help navigating through this and also

31:38 ↗ maybe trying to find an attorney I've

31:40 ↗ tried all the other resources for two

31:42 ↗ months even the insurance people aren't

31:44 ↗ helping me um they just they tell me one

31:48 ↗ thing and then the next day it's a

31:49 ↗ different story they're very dishonest

31:51 ↗ and maybe because there's so many

31:53 ↗ disasters in the world but that's that's

31:55 ↗ all and I don't know when the

31:56 ↗ appropriate time is

31:57 ↗ I figured this is the right place to get

31:59 ↗ resources it's sewage and water button

32:02 ↗ you're talking right about the

32:02 ↗ neighborhood I live in right there at

32:04 ↗ Creekside

32:05 ↗ um right above the and they have water

32:06 ↗ just going right into the Hatchery and I

32:09 ↗ didn't know I did call the city today

32:11 ↗ and let them know that um

32:13 ↗ that they're Waters they're pumping it

32:16 ↗ out from under their building into the

32:18 ↗ driveway for all the gas and toxins

32:20 ↗ that's going right a few feet above the

32:25 ↗ afterwards does someone could direct me

32:27 ↗ where I could get help and resources and

32:30 ↗ stress and maybe get the owners I can't

32:33 ↗ even get the owners

32:36 ↗ so perfect

32:38 ↗ great thank you so much

32:44 ↗ no I'm not I'm going to leave it in the

32:46 ↗ public works his hands great uh thank

32:50 ↗ you

32:56 ↗ um all right any any other comments I'm

32:59 ↗ not seeing anybody here so we're gonna

33:02 ↗ move on and give Matt some guidance so

33:06 ↗ we got two policy questions maintain the

33:09 ↗ sewer capacity and then also the fat

33:11 ↗ soil and grease management wherever you

33:13 ↗ want to start us off

33:17 ↗ question number one uh on the uh II

33:21 ↗ capacity impact threshold

33:23 ↗ you know I will be honest I don't know

33:25 ↗ if I know enough about the science to

33:27 ↗ really comment on that but it sounds

33:29 ↗ good and so and it sounds like you've

33:32 ↗ done a lot of preliminary work that's

33:35 ↗ been very very good and we've gotten

33:37 ↗ good data from it so yes let's go ahead

33:39 ↗ with that uh on the second one yes

33:42 ↗ absolutely the developer contributions

33:44 ↗ uh based on the amount of flow and

33:46 ↗ thanks for the further explanation about

33:48 ↗ how that would be determined

33:51 ↗ um and then on the last one

33:54 ↗ um I think uh the two to three year

33:57 ↗ uh unless we feel like it's an emergency

33:59 ↗ or I you know when we get those big

34:02 ↗ clogs in the sewer system I understand

34:04 ↗ that that costs us money and time and we

34:07 ↗ have to clear those and so uh but on the

34:10 ↗ other hand these I think what you're

34:12 ↗ describing is long-term businesses that

34:15 ↗ have been here in Issaquah for a number

34:17 ↗ of years

34:18 ↗ um and this will be uh something of a

34:20 ↗ surprise to them so I think two to three

34:22 ↗ year retroactive Clause would be

34:25 ↗ appropriate

34:27 ↗ um

34:28 ↗ yeah as you say these restaurants are

34:30 ↗ coming out of covid they're just getting

34:32 ↗ back on their feet again

34:34 ↗ um and even though business looks like

34:37 ↗ it's very very good right now we don't

34:39 ↗ know what's coming down the pike either

34:40 ↗ so um I think the two to three year

34:42 ↗ period would be good

34:44 ↗ so that's that those are my comments

34:47 ↗ thank you um I'm pretty much in

34:49 ↗ alignment I think the first one uh the

34:51 ↗ ini capacity impacts I I think it's very

34:54 ↗ smart to separate the flat from the

34:57 ↗ slopes um because we do have a finite

34:59 ↗ amount of money let's focus it where we

35:01 ↗ make an obvious difference so I think

35:02 ↗ that's very smart

35:04 ↗ um and and clearly if we're getting a

35:06 ↗ development that's going to make a

35:07 ↗ significant impact on our capacity

35:10 ↗ um asking them to pay their share fair

35:11 ↗ share is absolutely appropriate

35:14 ↗ um

35:15 ↗ I agree

35:16 ↗ um

35:17 ↗ I'm gonna say I don't disagree which is

35:19 ↗ like agreeing because it's double

35:21 ↗ negative on the uh one or the two to

35:23 ↗ three year on the The Fog fog traps

35:27 ↗ um but I would like us to reach out to

35:29 ↗ the business community at least the ones

35:31 ↗ we think will be uh impacted and and get

35:33 ↗ a sense of what what they're where

35:36 ↗ they're at they yeah

35:38 ↗ they may have a different uh point of

35:40 ↗ view but I'm not opposed to a longer

35:42 ↗ period of waiting because I agree it's

35:45 ↗ it's

35:46 ↗ this is a difficult time and we're just

35:48 ↗ getting back on our feet after coven so

35:50 ↗ um but based on their feedback I we're

35:52 ↗ kind of making fun of it but

35:55 ↗ um looks looks great

35:56 ↗ team awesome uh anything else

36:00 ↗ all right thank you we're gonna we're

36:02 ↗ gonna move on then thank you

36:05 ↗ this is always so riveting to do sewer

36:08 ↗ system I mean I'm

36:10 ↗ I'm just honored that we get to do it um

36:13 ↗ so we're gonna move on to the next

36:15 ↗ agenda item which is ID 1525 one of my

36:18 ↗ favorites intelligent transportation

36:20 ↗ system we have the draft plan and it's

36:22 ↗ going to be presented by the director of

36:24 ↗ Public Works Emily Moon so Emily

36:27 ↗ welcome

37:12 ↗ good evening happy to be here

37:17 ↗ this is a big moment

37:19 ↗ big moment

37:21 ↗ as chair Ray has eagerly anticipated

37:25 ↗ um I am very happy to be talking about

37:27 ↗ the its plan

37:29 ↗ uh

37:31 ↗ first before we start

37:35 ↗ um I would like

37:37 ↗ see if my slides actually down there we

37:39 ↗ go

37:40 ↗ uh I would like to say thank you to the

37:42 ↗ buddy system that I brought with me this

37:45 ↗ evening uh we we have had many many

37:49 ↗ people on staff and consultants and

37:53 ↗ other subject matter experts help us in

37:56 ↗ designing this plan

37:57 ↗ uh this plan has been in development as

38:02 ↗ a as a focal point in

38:06 ↗ concentrated effort for over a year

38:09 ↗ but as council members know a lot of

38:13 ↗ precursors to the plans actual

38:15 ↗ development many years beyond that so I

38:18 ↗ wanted to say thanks to the team we have

38:20 ↗ a few people here tonight we have

38:23 ↗ members from our Public Works

38:26 ↗ engineering team we have it

38:29 ↗ folks here that have helped with the

38:32 ↗ plan and we have our super subject

38:36 ↗ matter expert our senior signal Tech as

38:39 ↗ well

38:40 ↗ so thank you all for all your hard work

38:43 ↗ putting this together it was an

38:45 ↗ excellent collaboration

38:48 ↗ this like the Sewer Master Plan was way

38:52 ↗ overdue another plan that was 20 plus

38:56 ↗ years old

38:57 ↗ so that's another reason why I'm happy

39:00 ↗ to be here to finally be able to say

39:02 ↗ we're going to

39:03 ↗ communicate how we're going to take our

39:06 ↗ intelligent transportation system into

39:08 ↗ the next era

39:11 ↗ so the question before you tonight is do

39:14 ↗ you agree

39:15 ↗ uh with how the plan has been shaped and

39:19 ↗ do you have any desires to make

39:22 ↗ uh direct us to make any changes to the

39:24 ↗ plan before you can recommend it to the

39:28 ↗ full Council for acceptance

39:33 ↗ I want to talk a little bit about just

39:35 ↗ what this plan is I've defined its for

39:39 ↗ you I will be saying its as we go

39:42 ↗ because otherwise it's very long

39:44 ↗ term intelligent Transportation Systems

39:48 ↗ so this plan is wholly focused on our

39:52 ↗ technology hardware and software and the

39:56 ↗ data that we get from using that

39:58 ↗ technology and the resources and the

40:01 ↗ practices that we have in place to

40:04 ↗ manage that system

40:06 ↗ and that's all in an effort to improve

40:08 ↗ our traffic flow reduce traffic delays

40:11 ↗ and also increase safety in our

40:13 ↗ transportation system

40:18 ↗ the its World though is vast and always

40:22 ↗ changing as we learn more so we're we

40:26 ↗ wanted to express that to you in terms

40:29 ↗ of it being a universe of things many

40:31 ↗ possibilities that we could invest in

40:34 ↗ that we could Implement technology

40:37 ↗ equipment policies and procedures

40:41 ↗ and so a big effort in this plan was to

40:43 ↗ just look at that landscape and think

40:46 ↗ about what might work here what seems

40:49 ↗ appropriate for our needs in this

40:51 ↗ community

40:54 ↗ and that that landscape as I said is

40:59 ↗ always changing and we have to keep that

41:00 ↗ in mind as we review this plan as we

41:02 ↗ talk about its implementation over the

41:05 ↗ years technologies always evolving we

41:08 ↗ will need to be nimble in execution of

41:11 ↗ this plan but also in how we refine it

41:13 ↗ as we go

41:16 ↗ there's no predefined path

41:19 ↗ to the outcomes that we are seeking

41:22 ↗ there are probably numerous

41:23 ↗ opportunities for us to get there and I

41:26 ↗ think that's a great thing it's a great

41:28 ↗ thing

41:29 ↗ the its plan

41:32 ↗ took that whole universe and refined the

41:36 ↗ options available to US based on our

41:39 ↗ criteria which we'll talk about a little

41:41 ↗ bit later

41:43 ↗ we boiled it down to a collection of

41:45 ↗ actions projects policies procedures

41:48 ↗ practices that we could choose among

41:51 ↗ to collect and use our data to further

41:53 ↗ our transportation system objectives

41:57 ↗ then we further refined into the CIP

42:01 ↗ and we described a plan for the next six

42:04 ↗ years

42:06 ↗ we applied that first layer of

42:09 ↗ implementation planning what might be

42:12 ↗ feasible in the next six years what can

42:14 ↗ we get done

42:16 ↗ what can we get done in a given year

42:17 ↗ what can we get done span of six what

42:20 ↗ funding resources might we have and how

42:24 ↗ do we need to think about the sequencing

42:25 ↗ of these projects

42:28 ↗ and lastly we refined even further got

42:31 ↗ down to the budget the biennial budget

42:34 ↗ and that is where we implement the first

42:37 ↗ two years of the CIP we established the

42:40 ↗ resources for implementation and we set

42:43 ↗ the biannual work plan

42:46 ↗ so we took the universe we boiled it

42:49 ↗ down to about 50 original projects and

42:53 ↗ then we further refined into about 26

42:55 ↗ that are in the its plan and then there

42:58 ↗ are 12 blasts I'll talk about the plus

43:01 ↗ that are in the CIP right now

43:04 ↗ and then lastly you see this little

43:06 ↗ inject for concurrency and the

43:09 ↗ concurrency policy update will help

43:12 ↗ inform the its plan that update will

43:15 ↗ include some discussion and decisions

43:17 ↗ that will help us understand a little

43:20 ↗ bit better how we should situate the

43:22 ↗ hierarchy of policies and projects in

43:25 ↗ the plan just a couple examples of that

43:28 ↗ are a couple of Technologies and

43:31 ↗ techniques called leading pedestrian

43:33 ↗ interval and our Transit signal

43:36 ↗ prioritization you'll hear me talk about

43:38 ↗ those projects probably again too

43:42 ↗ performance measurement was one of the

43:45 ↗ topics we discussed the last time that I

43:46 ↗ was here to talk about its

43:48 ↗ with so many options available to us

43:54 ↗ we

43:55 ↗ have to also be mindful of those choices

43:59 ↗ being constrained two time resources

44:02 ↗ money

44:03 ↗ and

44:05 ↗ that environment constantly changing

44:07 ↗ evolving we're going to have to be

44:09 ↗ strategic about where we spend our money

44:11 ↗ and which Technologies we lean into

44:15 ↗ we also have a long implementation

44:17 ↗ period and so we have many opportunities

44:20 ↗ to be able to evaluate over time how

44:22 ↗ well we are doing and to correct if we

44:25 ↗ need to add different layers

44:28 ↗ Etc

44:30 ↗ so we're dedicated to making sure that

44:32 ↗ we have strong performance measures for

44:34 ↗ this program and we'll be evaluating the

44:37 ↗ return on investment as we make future

44:40 ↗ decisions about implementation of these

44:43 ↗ projects

44:46 ↗ on this slide I've said that we're going

44:47 ↗ to measure performance at the project

44:49 ↗ level and that is appropriate not only

44:55 ↗ to look at it at as a whole but at the

44:58 ↗ project level because again we will have

45:00 ↗ choices

45:01 ↗ after each project and each project is

45:04 ↗ is Standalone in nature to some degree

45:07 ↗ connected in another degree so each

45:10 ↗ project will be aligned with a subset of

45:14 ↗ the objectives from the plan so not

45:17 ↗ every project

45:19 ↗ corresponds to every objective in the

45:22 ↗ plan but we want to be really deliberate

45:24 ↗ about saying this is what we're trying

45:25 ↗ to achieve with this particular project

45:28 ↗ so we're going to assess if those

45:30 ↗ targeted outcomes are achieved by those

45:33 ↗ projects as we go and uh I can give you

45:37 ↗ some examples of some performance

45:39 ↗ measures we talked about a few of these

45:40 ↗ last time but some of the things we

45:42 ↗ intend to measure are the efficient use

45:45 ↗ of our infrastructure we have some

45:47 ↗ multimodal goals we need to get better

45:49 ↗ at being able to

45:52 ↗ quantify that

45:54 ↗ safety measures

45:56 ↗ such as number of collisions red light

45:58 ↗ running near misses are examples of

46:01 ↗ those

46:02 ↗ system reliability is really important

46:05 ↗ to us percentage of equipment that's

46:08 ↗ replaced according to its life cycle as

46:11 ↗ an example of that travel times

46:13 ↗ efficiency of travel I could go on and

46:16 ↗ on lots of opportunities to measure how

46:19 ↗ well these projects are helping us

46:21 ↗ achieve our outcomes

46:24 ↗ and then lastly we have some pilot

46:26 ↗ projects we want to make sure that as

46:29 ↗ this technology is changing that it's

46:32 ↗ working for us the way that we thought

46:34 ↗ it would

46:35 ↗ we have projects in the CIP or in the

46:39 ↗ its plan that maybe years out technology

46:42 ↗ is going to change as we get there we

46:44 ↗ may need to try a few along the way

46:47 ↗ before we settle on the piece that is

46:50 ↗ going to work with all the other things

46:51 ↗ that we're implementing so that's why we

46:54 ↗ have set up this opportunity for

46:56 ↗ performance measurement in terms of

46:57 ↗ pilot projects

47:01 ↗ our project timeline we are nearing the

47:04 ↗ finish line I will just

47:07 ↗ comment on this slide that on box number

47:09 ↗ two between October 2022 and March 2023

47:14 ↗ we were before this committee and the

47:18 ↗ transportation Advisory Board talking

47:21 ↗ about core components of the plan those

47:23 ↗ core components were the its plan goals

47:26 ↗ objectives the top objectives the

47:30 ↗ priority objectives and are proposed a

47:33 ↗ proposed approach to implementation and

47:36 ↗ therefore their priority projects

47:38 ↗ our hope is that we'll be back before

47:40 ↗ City Council in October if you're happy

47:43 ↗ with the plan we're going to talk to tab

47:45 ↗ one more time before we come back to the

47:48 ↗ full Council but our hope is that we can

47:51 ↗ get the plan accepted so that we can

47:53 ↗ move forward with implementation both

47:55 ↗ through the CIP and the operating budget

48:01 ↗ I'm not going to read you these slides

48:03 ↗ but we we have a mission statement for

48:06 ↗ the plan we

48:09 ↗ are focused on many

48:11 ↗ high level objectives such as improving

48:16 ↗ health safety security movement of

48:19 ↗ people and so on

48:22 ↗ this is not

48:24 ↗ dissimilar to what you see in some of

48:26 ↗ our other Mobility or Transportation

48:28 ↗ plans the difference here is the focus

48:31 ↗ on technology this plan is really about

48:33 ↗ the technology and the data that we get

48:35 ↗ from the system

48:38 ↗ our plan components include

48:41 ↗ six goals first is improve the safety of

48:44 ↗ the transportation system second is

48:46 ↗ improve the efficiency and

48:48 ↗ sustainability of the transportation

48:50 ↗ system the third is to provide traveler

48:52 ↗ information to help inform root and mode

48:55 ↗ choice and the fourth is to plan and

48:58 ↗ deploy cost efficient and effective its

49:01 ↗ technology the fifth is to integrate

49:04 ↗ City its efforts with regional partners

49:07 ↗ and the six is Monitor Transportation

49:09 ↗ performance measures and utilize this

49:12 ↗ information to improve safety and

49:14 ↗ efficiency of the transportation system

49:20 ↗ our plan being a data driven plan has a

49:24 ↗ lot of charts and graphs

49:26 ↗ we have done a significant body of work

49:30 ↗ trying to get our infrastructure loaded

49:33 ↗ into our GIS system and so this is just

49:37 ↗ one example of how we are now able to

49:41 ↗ graphically depict some elements of our

49:44 ↗ its infrastructure this is our

49:47 ↗ Communications network but we also show

49:50 ↗ a bunch of different assets for the its

49:54 ↗ plan our signal controllers time where

49:57 ↗ we have time and plans signal cabinets

49:59 ↗ detection equipment pedestrian Crossing

50:02 ↗ equipment emergency vehicle preemption

50:04 ↗ traffic cameras Dynamic messaging signs

50:08 ↗ safety Technologies such as school zone

50:11 ↗ flashers rectangular rapid flashing

50:14 ↗ beacons rrfbs you'll hear me say that

50:17 ↗ again

50:18 ↗ and Driver feedback signs

50:21 ↗ this one in particular is our

50:23 ↗ Communications Network

50:25 ↗ there's just another example where we

50:27 ↗ have our cameras and our Dynamic message

50:29 ↗ signs or our DMs

50:31 ↗ important tool for our community

50:36 ↗ another example of how data is

50:38 ↗ represented in the plan this is a table

50:42 ↗ of our field devices some of those I

50:45 ↗ rattled off just an a way of showing you

50:48 ↗ that we spent quite a bit of time

50:50 ↗ cataloging what do we have where is it

50:53 ↗ and thinking through the life cycles and

50:56 ↗ and replacement needs for this

50:59 ↗ infrastructure

51:04 ↗ the plan also includes some thoughts

51:07 ↗ about Staffing what do we need in order

51:09 ↗ to implement these projects and to keep

51:11 ↗ up with our current inventories needs

51:14 ↗ the replacement the repairs

51:17 ↗ the plan articulates a need for 2.5

51:21 ↗ additional ftes to implement what you

51:25 ↗ see in the its plan

51:28 ↗ we will have future conversations with

51:30 ↗ Council about resourcing we're not doing

51:33 ↗ that tonight but I I think it's an

51:36 ↗ important part of our discussion about

51:39 ↗ these comprehensive plans to talk about

51:41 ↗ what will it take to implement and so

51:43 ↗ staff has spent quite a bit of time

51:45 ↗ thinking about what resources they might

51:48 ↗ need in order to take on additional

51:50 ↗ projects or to keep up with our current

51:54 ↗ inventory needs

51:56 ↗ the Staffing plan also includes a

51:58 ↗ recommendation for two reclassifications

52:01 ↗ which we will be pursuing uh next few

52:06 ↗ months and as we approach next year's

52:09 ↗ budget

52:16 ↗ this graphic shows up in the plan a

52:18 ↗ couple of times

52:19 ↗ we are in the performed State this is

52:24 ↗ the way that we operate right now we're

52:26 ↗ trying to move all the way over to

52:28 ↗ optimize so the perform State means that

52:31 ↗ right now we are very focused on

52:34 ↗ operations and maintenance activities

52:36 ↗ and reactive fashion very ad hoc get out

52:40 ↗ there fix that thing

52:42 ↗ we want to move further to the right to

52:44 ↗ managed via this plan where we are

52:48 ↗ making some deliberate decisions that

52:49 ↗ are based on data where we can monitor

52:52 ↗ the system

52:54 ↗ where we can act earlier because we see

52:57 ↗ problems coming

52:58 ↗ and we are able to test some solutions

53:03 ↗ have some plans and some strategic

53:06 ↗ processes

53:07 ↗ and then lastly goal is to get to

53:10 ↗ optimize where we'll be really data

53:12 ↗ driven proactively managing the system

53:14 ↗ and leveraging resources and partners

53:22 ↗ we've talked about our implementation

53:25 ↗ approach I'm not going to spend much

53:26 ↗ time on that tonight we talked about

53:27 ↗ that in advance of prioritizing the

53:30 ↗ projects for the CIP so you know that

53:34 ↗ our near-term effort is going to be

53:37 ↗ heavily focused on building that

53:38 ↗ Readiness we need to build the

53:41 ↗ foundation that we can then

53:43 ↗ add additional new technology on top of

53:48 ↗ so we're going to be spending quite a

53:50 ↗ bit of time over the next couple of

53:52 ↗ years at least working on annual

53:53 ↗ equipment upgrades

53:56 ↗ replacing equipment that is reached the

53:59 ↗ end of its life and also working on

54:02 ↗ policies procedures creating a detailed

54:05 ↗ Communications Network plan

54:08 ↗ that will Design the network for what we

54:10 ↗ need in order to bring it to that next

54:13 ↗ advanced level

54:16 ↗ also our annual upgrade program I just

54:19 ↗ wanted to add that we did add a new

54:22 ↗ signal Tech position this Summer that

54:25 ↗ was a position that Council authorized

54:28 ↗ in the springtime in order to help us

54:31 ↗ with this debt that we had on our

54:34 ↗ infrastructure and I also Council gave

54:38 ↗ approval for some new replacement

54:40 ↗ programs in the CIP

54:47 ↗ there are 26 its projects in this plan

54:51 ↗ that have unique identifying numbers I

54:55 ↗ say that because the its project numbers

54:58 ↗ are not synonymous with the CIP project

55:01 ↗ numbers I can create a little bit of

55:02 ↗ confusion but we try to crosswalk them a

55:05 ↗ bit in the plan so that you could see

55:07 ↗ that connectivity

55:09 ↗ not all of the its

55:12 ↗ projects are included in the CIP again

55:15 ↗ that's because it's constrained to the

55:17 ↗ six years there's the reality of funding

55:20 ↗ that comes into play but also some of

55:25 ↗ the its projects are located in current

55:28 ↗ or future operating budgets

55:31 ↗ some may be dependent on earlier

55:34 ↗ projects so we'll we'll incorporate them

55:37 ↗ into the CIP when they're ready to go

55:39 ↗ some hinge on policy decisions that we

55:42 ↗ mentioned with our concurrency policy

55:44 ↗ update some have also been collapsed and

55:47 ↗ Consolidated into a single CIP project

55:50 ↗ and then others are out there in the

55:53 ↗ future and will be recommended when we

55:54 ↗ get to that point

55:58 ↗ these are the projects that are in the

56:01 ↗ CIP there are 12 plus

56:04 ↗ the plus is the rrfb replacement program

56:09 ↗ we've had a lot of debate about whether

56:11 ↗ to call that an its project or not

56:13 ↗ different people see it different ways

56:16 ↗ eventually there will be no discussion

56:18 ↗ on that point because hopefully we will

56:20 ↗ get to a place where we have rrfbs that

56:22 ↗ have a little bit more intelligence than

56:24 ↗ the ones that we have today but we as

56:28 ↗ staff do consider it part of our

56:30 ↗ transportation system our Mobility

56:33 ↗ system and so that is included the

56:36 ↗ replacement program for the rrfbs is in

56:38 ↗ the CIP

56:43 ↗ in addition to the capital projects the

56:46 ↗ its plan spells out some policies other

56:49 ↗ plans memorandums of understanding that

56:52 ↗ are recommended over the next few years

56:55 ↗ and I've listed a few examples of those

57:01 ↗ and then lastly there's a little

57:03 ↗ discussion on funding ever-changing

57:06 ↗ landscape on funding but the operating

57:08 ↗ budget currently has about 1.25 million

57:13 ↗ dollars dedicated in labor equipment and

57:15 ↗ materials that is put toward our its

57:18 ↗ infrastructure

57:22 ↗ our CIP has a variety of funding sources

57:24 ↗ too right now what's named in the CIP

57:28 ↗ for these projects includes the TBD

57:31 ↗ sales tax it's been proposed

57:34 ↗ general fund funding source and

57:37 ↗ undetermined right that's usually what

57:39 ↗ we see for those later years in the plan

57:43 ↗ and then lastly grants are available and

57:47 ↗ our consultant had a little bit of

57:49 ↗ discussion at the end of the plan about

57:51 ↗ the types of grants that may be

57:52 ↗ available to our projects

57:57 ↗ we've been fortunate to receive some

57:59 ↗ really good feedback as we

58:01 ↗ were in development on this plan uh

58:05 ↗ largely we have heard from everyone that

58:09 ↗ we've spoken to that there is an

58:11 ↗ understanding and support for our focus

58:13 ↗ on those near-term foundational efforts

58:16 ↗ to build our readiness

58:18 ↗ agreement that the projects that we had

58:21 ↗ proposed or aligned with goals that were

58:23 ↗ described in the plan

58:25 ↗ and that we should make an effort to get

58:27 ↗ to the optimized State make the

58:29 ↗ Investments was one of the things I

58:31 ↗ think chair Ray even said last time

58:34 ↗ and a desire to have staff keep our

58:38 ↗ transportation Advisory board and the

58:40 ↗ city council engaged on those future

58:42 ↗ policy questions so that we can continue

58:45 ↗ to stay flexible adjust our plan as

58:47 ↗ needed

58:50 ↗ I also wanted to mention that two

58:52 ↗ committee members at least last time

58:55 ↗ said don't forget security system

58:57 ↗ security we want to see that in the plan

59:01 ↗ may not have jumped out at you so I want

59:03 ↗ to speak to that

59:05 ↗ um

59:06 ↗ there's always a bit of caution when we

59:08 ↗ start talking about system Security in

59:10 ↗ our in our plans but I want to verbalize

59:12 ↗ that we are committed to that we talk

59:16 ↗ about it often we are in the process of

59:20 ↗ developing additional policies I.T in

59:23 ↗ particular has been heavily involved in

59:25 ↗ the effort to make sure that our

59:27 ↗ hardware and software is up to Snuff

59:31 ↗ and give you a few examples of work that

59:33 ↗ has been completed

59:35 ↗ so in 2023 all its devices are now in a

59:39 ↗ firewall Network

59:41 ↗ seems like step one

59:43 ↗ of security and so they're separate from

59:46 ↗ other City networks

59:48 ↗ also this year we

59:51 ↗ restricted remote access to its devices

59:55 ↗ another key component of ensuring some

59:58 ↗ security for the system others there are

1:00:01 ↗ other examples of work that we completed

1:00:02 ↗ this year I'm going to give you a couple

1:00:04 ↗ ideas of things that we are targeting in

1:00:07 ↗ 2024

1:00:09 ↗ we are targeting enforcement of those

1:00:13 ↗ network access controls to prevent

1:00:16 ↗ unknown devices

1:00:18 ↗ you probably get those pop-up messages

1:00:20 ↗ anytime you log on from a different

1:00:22 ↗ device we will have something similar to

1:00:26 ↗ ensure that our network is not

1:00:27 ↗ connecting with anyone who shouldn't be

1:00:30 ↗ and then we will also be reviewing all

1:00:34 ↗ its applications and further Hardware

1:00:36 ↗ hardening of them in 2024. we have a we

1:00:41 ↗ have a list of activities that are all

1:00:43 ↗ geared around enhancing security it is a

1:00:45 ↗ focal point

1:00:46 ↗ uh it's embedded in in the projects and

1:00:50 ↗ and practices that we have

1:00:57 ↗ so next steps are to uh

1:01:01 ↗ dialogue with the transportation

1:01:03 ↗ Advisory Board in a couple weeks and

1:01:08 ↗ ensure that they have no further changes

1:01:11 ↗ to the plan

1:01:13 ↗ they know that

1:01:16 ↗ their responsibility was largely around

1:01:19 ↗ the big picture elements and so now just

1:01:21 ↗ as we're doing with you we're showing

1:01:23 ↗ the whole but uh most of the work that

1:01:26 ↗ has been done over the last few months

1:01:28 ↗ since we last spoke I just was focused

1:01:31 ↗ on those technical aspects of the plan

1:01:33 ↗ and then we hope to be back before the

1:01:35 ↗ city council in October for acceptance

1:01:37 ↗ so with that question that we had for

1:01:41 ↗ you is do you desire any changes to the

1:01:43 ↗ plan at this time or are you ready to

1:01:48 ↗ recommend its acceptance to the city

1:01:50 ↗ council

1:01:53 ↗ all right thanks

1:01:55 ↗ council member do you show any questions

1:01:57 ↗ at this point

1:01:58 ↗ I have a couple

1:02:00 ↗ so I will rattle them off

1:02:03 ↗ um

1:02:05 ↗ so the you you listed the mou with with

1:02:09 ↗ washnut was that something that they

1:02:11 ↗ were amenable to and that we can

1:02:13 ↗ reasonably move forward with I mean that

1:02:15 ↗ could it's just that sr900 is a big

1:02:18 ↗ arterial and IA 90 is a bigger arterial

1:02:22 ↗ and those are theirs so that's that's

1:02:24 ↗ kind of wondering how that process was

1:02:26 ↗ going yeah yeah

1:02:29 ↗ I believe that they are okay

1:02:31 ↗ uh the

1:02:34 ↗ we will have to see the details of

1:02:36 ↗ course of that but I will say that we

1:02:39 ↗ have had a significant amount of

1:02:41 ↗ dialogue with them on some other matters

1:02:44 ↗ and I feel like there's a little bit

1:02:47 ↗ more willingness to partner with the

1:02:49 ↗ city on a bunch of fronts so I'm hopeful

1:02:54 ↗ cool

1:02:55 ↗ um so you mentioned that this its

1:02:58 ↗ technology is fairly Dynamic and

1:02:59 ↗ evolving really fast and we'll have a

1:03:01 ↗ hard time kind of projecting what's out

1:03:03 ↗ there but

1:03:04 ↗ um are you thinking about how we stay

1:03:06 ↗ current with with this evolving

1:03:08 ↗ technology and how we going forward

1:03:11 ↗ evolve the plan say wow here's the new

1:03:13 ↗ the newest latest greatest does that fit

1:03:16 ↗ into our vision

1:03:17 ↗ um and if so how do we do that and how

1:03:19 ↗ do we stay on top of the

1:03:21 ↗ the technology it's

1:03:23 ↗ it's no it's only going to accelerate

1:03:27 ↗ not slow down yes yes

1:03:30 ↗ a bunch of different ways I think we can

1:03:32 ↗ stay informed and engaged on that front

1:03:35 ↗ uh we pride ourselves in taking

1:03:39 ↗ advantage of regional resources National

1:03:42 ↗ opportunities for training connectivity

1:03:46 ↗ so it's reading it's attending

1:03:48 ↗ conferences trainings it's talking with

1:03:51 ↗ our colleagues in other places

1:03:54 ↗ so that's a that's a piece of it we also

1:03:58 ↗ engage with other subject matter experts

1:04:01 ↗ or Consultants about future projects

1:04:05 ↗ we've left I I think a few projects open

1:04:09 ↗ to

1:04:11 ↗ not name a particular make model of a

1:04:16 ↗ technology

1:04:17 ↗ so I think we will not be locked in and

1:04:21 ↗ we'll have that flexibility to change as

1:04:24 ↗ we as we learn as we go

1:04:30 ↗ all right uh we have another opportunity

1:04:33 ↗ for public comment I'll start with the

1:04:36 ↗ room anybody in the room interested in

1:04:38 ↗ making comment today no okay

1:04:41 ↗ do you think anybody online expressed an

1:04:43 ↗ interest in public comment at this time

1:04:47 ↗ chair Ray we currently have no virtual

1:04:49 ↗ attendees all right I guess that's a no

1:04:51 ↗ all right then let's uh let's move on to

1:04:54 ↗ our kind of directional statements and

1:04:58 ↗ I'm going to pick on you again

1:05:01 ↗ well there's only two of us it's pretty

1:05:03 ↗ hard not to be the first person to

1:05:05 ↗ comment

1:05:07 ↗ um you know uh in our last Community

1:05:09 ↗ survey we heard once again from our

1:05:12 ↗ community that uh transportation and the

1:05:16 ↗ smooth flow of traffic was uh if it's

1:05:18 ↗ not their first priority it's very close

1:05:20 ↗ and the whole field of transportation is

1:05:23 ↗ the a top concern for our community so

1:05:26 ↗ so

1:05:27 ↗ um first of all commend the staff and be

1:05:31 ↗ for being very proactive and getting

1:05:33 ↗ this plan after

1:05:36 ↗ what 14 16 18 years whatever it was uh

1:05:40 ↗ back on the table and really doing the

1:05:42 ↗ hard work to get it up and ready to go

1:05:45 ↗ um we saw what happened when the

1:05:48 ↗ technology and some of our equipment

1:05:51 ↗ simply got out of you know out of sync

1:05:54 ↗ and we had no plan for how to how to

1:05:56 ↗ bring ourselves back up so this is

1:05:58 ↗ really exciting uh Emily and I were

1:06:01 ↗ talking on the way in here about the

1:06:04 ↗ fact that our traffic is back to pre

1:06:06 ↗ pandemic in some cases I think it's

1:06:09 ↗ worse than pre-pandemic I was just took

1:06:12 ↗ me the longest time to get down from the

1:06:14 ↗ plateau to this meeting tonight so this

1:06:18 ↗ is very very needed and I think this

1:06:20 ↗ plan is going to set us up for Success

1:06:23 ↗ um and

1:06:24 ↗ um so yes I do think that we're ready to

1:06:27 ↗ take it in front of the full Council for

1:06:29 ↗ approval so that we can start to move

1:06:31 ↗ forward

1:06:33 ↗ um the only comment I would add is that

1:06:35 ↗ I will bet that most people in the squad

1:06:39 ↗ don't know that we have an intelligent

1:06:40 ↗ transportation

1:06:42 ↗ and so when we get this uh when we start

1:06:45 ↗ moving forward on this let's think about

1:06:46 ↗ how do we tell this good story to the

1:06:49 ↗ community and that what they are

1:06:51 ↗ concerned about we are working on that

1:06:54 ↗ we we are really taking this seriously

1:06:55 ↗ we're putting some investment into

1:06:59 ↗ um

1:06:59 ↗ uh improving the efficiency of our

1:07:02 ↗ transportation system

1:07:04 ↗ especially as

1:07:06 ↗ as this traffic situation gets worse and

1:07:09 ↗ worse

1:07:10 ↗ um so that they do know that we are

1:07:12 ↗ working on it and that things are

1:07:14 ↗ happening whether they can actually see

1:07:16 ↗ a lot of it or not uh same thing with

1:07:19 ↗ the Metroflex as we as we get into that

1:07:23 ↗ um we need to really communicate that

1:07:25 ↗ again we heard you we listened to you

1:07:27 ↗ and here's something that we're doing

1:07:29 ↗ about it so but I really think that

1:07:32 ↗ you've done a wonderful job of pulling

1:07:33 ↗ this uh plan together

1:07:35 ↗ um and I don't have any major changes or

1:07:38 ↗ even minor changes to it so let's take

1:07:41 ↗ it to the full Council and I I think

1:07:44 ↗ it's we usually talk about whether it

1:07:47 ↗ should go on consent agenda or the full

1:07:48 ↗ agenda I think it's something we need to

1:07:51 ↗ talk about

1:07:52 ↗ um fully with the full Council I would

1:07:54 ↗ expect that it will be received very

1:07:56 ↗ favorably but I still think it would be

1:07:59 ↗ better on the full agenda than on the

1:08:01 ↗ consent agenda so those are my comments

1:08:04 ↗ great thanks

1:08:05 ↗ so is it an item for adoption acceptance

1:08:10 ↗ by the council then is that the plan yes

1:08:12 ↗ okay

1:08:14 ↗ I I agree with you by the way oh good on

1:08:17 ↗ that on that one

1:08:19 ↗ um but um I I tried not to word Smith

1:08:23 ↗ but I I it was one I just couldn't help

1:08:25 ↗ myself and it's on the mission statement

1:08:27 ↗ and it's improved the safety health and

1:08:29 ↗ security and movement of goods people

1:08:30 ↗ and Services I think people come before

1:08:32 ↗ Goods

1:08:35 ↗ so you know just it's you know anyway it

1:08:39 ↗ it just hit me as I read it so um that's

1:08:41 ↗ my my one and only Wordsmith

1:08:44 ↗ um so at a conceptual level

1:08:46 ↗ um you know I think this is really clear

1:08:47 ↗ I'm really excited about this it's

1:08:49 ↗ something

1:08:50 ↗ I don't know this is my sixth year I've

1:08:52 ↗ wanted to see for at least six years and

1:08:53 ↗ probably didn't know it existed before

1:08:55 ↗ that but I think this is really

1:08:57 ↗ something that we need to do and

1:09:00 ↗ to council member D Michelle's point

1:09:03 ↗ the community is hungry for anything we

1:09:06 ↗ can do to move people through the city

1:09:08 ↗ more effectively and this is one of the

1:09:12 ↗ few really viable tools we have to do

1:09:14 ↗ that so Bravo on this

1:09:17 ↗ um I'm also excited because it's going

1:09:18 ↗ to generate a wealth of data

1:09:20 ↗ that help you to make that transition

1:09:22 ↗ from being essentially a reactive

1:09:25 ↗ organization into you know up that

1:09:27 ↗ maturity scale into a an optimized one

1:09:30 ↗ and I think that's very exciting both

1:09:32 ↗ from a traffic flow perspective but also

1:09:34 ↗ and maybe more importantly from a safety

1:09:36 ↗ perspective so so that's that's exciting

1:09:39 ↗ to me

1:09:41 ↗ um

1:09:43 ↗ I like oh that's what I just said never

1:09:45 ↗ mind I want to say it again

1:09:47 ↗ um

1:09:48 ↗ so my I have two concerns and these are

1:09:51 ↗ kind of the looking forward things so

1:09:52 ↗ one is we've got a lot of investing to

1:09:55 ↗ do to get caught up because we developed

1:09:57 ↗ a lot of technical debt over the last X

1:09:58 ↗ number of years

1:09:59 ↗ so

1:10:01 ↗ um happy to make that investment so that

1:10:03 ↗ we can take the next step forward

1:10:05 ↗ but I need someone to promise that we

1:10:07 ↗ won't let this happen again and that we

1:10:09 ↗ will continue to invest in this so that

1:10:12 ↗ we stay current and that we are pushing

1:10:14 ↗ the envelope because I think this is

1:10:16 ↗ really a critical thing for the

1:10:17 ↗ long-term health of our community and

1:10:21 ↗ then maybe just because I'm Emergency

1:10:23 ↗ Management is top of mind right now

1:10:26 ↗ um but I I appreciate the work that's

1:10:28 ↗ been done around security and hardening

1:10:30 ↗ access to the intelligent transportation

1:10:33 ↗ system but I think it's something that

1:10:34 ↗ needs to be included also in the

1:10:36 ↗ Emergency Management plan that if

1:10:37 ↗ somehow we were to be compromised that

1:10:39 ↗ we we've got a plan for what the heck

1:10:41 ↗ we're going to do because the the chaos

1:10:44 ↗ that you could create if you took over

1:10:46 ↗ our signaling system would be uh you

1:10:49 ↗ know not maybe as bad as taking down the

1:10:51 ↗ sewer system which would be worse

1:10:54 ↗ um but it would be um

1:10:55 ↗ it'd be kind of catastrophic

1:10:58 ↗ I guess that was my my timer to stop

1:11:01 ↗ talking

1:11:03 ↗ um but that's but I'm really excited

1:11:04 ↗ about the plan holy uh uh supported I I

1:11:08 ↗ like the approach of laying out the

1:11:09 ↗ long-term vision and then carving it up

1:11:11 ↗ into the CIP six year vision and then

1:11:14 ↗ the five things for the the current

1:11:16 ↗ budget cycle so

1:11:17 ↗ um let's let's get going let's stop

1:11:19 ↗ talking let's get going

1:11:21 ↗ all right anything else you need from us

1:11:23 ↗ no thank you very much for your comments

1:11:25 ↗ all right

1:11:30 ↗ well that brings us to our last agenda

1:11:33 ↗ item which is any announcements council

1:11:34 ↗ member D Michelle do you have an

1:11:35 ↗ announcement yeah this one's for Andrea

1:11:38 ↗ Snyder

1:11:39 ↗ um uh I just wanted to share if you

1:11:43 ↗ haven't heard that the City of Paris

1:11:45 ↗ France a band

1:11:48 ↗ um electric scooters so

1:11:52 ↗ following up on previous conversations

1:11:55 ↗ um and then when I attended the Eastside

1:11:58 ↗ Transportation partnership met with both

1:12:01 ↗ the uh the other two Regional

1:12:03 ↗ Partnerships the North and the South and

1:12:06 ↗ we all met at the Puget Sound Regional

1:12:07 ↗ Council

1:12:08 ↗ and we heard about the climate their

1:12:10 ↗ climate action plan and their plans for

1:12:13 ↗ electrification of the Metro's Fleet and

1:12:16 ↗ the question was raised

1:12:17 ↗ um is Metro uh looking at e-bikes as a

1:12:23 ↗ solution to that last mile conundrum and

1:12:26 ↗ the answer to that question was a robust

1:12:28 ↗ yes so I just thought we might keep our

1:12:32 ↗ eyes on that maybe instead of the

1:12:35 ↗ electric scooters

1:12:38 ↗ sorry Andrew that's the good news and

1:12:40 ↗ then there's the bad news so

1:12:42 ↗ anyway uh so it was a really interesting

1:12:46 ↗ response to the question because I

1:12:48 ↗ thought they were going to say what and

1:12:50 ↗ they said oh no we've been talking about

1:12:51 ↗ that for a while now so so uh anyway

1:12:54 ↗ let's keep our eyes on that all right

1:12:56 ↗ and that that is my sharing for tonight

1:12:59 ↗ well I appreciate that and I read about

1:13:01 ↗ about Paris too and I thought that was

1:13:03 ↗ kind of interesting about the scooters

1:13:05 ↗ all right well we have no further

1:13:07 ↗ business so we are adjourned at

1:13:10 ↗ 7 44. good night

Approved minutes

The minutes PDF below is the canonical record. Structured parsing of attendance and motions for this body's minutes format is not yet implemented — open the PDF for the full content.

Open PDF