OpenPublica

Accountability starts with access.

© 2026 · Filed for the public record

Use casesAboutAPIPrivacyTermsLinkedIn
Home/St Paul, Minnesota/City Council
OPENPUBLICA · PUBLIC MEETING RECORD
Record of Proceedings

Saint Paul Budget and Policy Committee Meetings on October 21, 2026

City Council — Wednesday, October 21, 2026
BodySt Paul, Minnesota
SessionCity Council
DateWednesday, October 21, 2026
StatusFILED
Video Record
0:00 / 4:02:06

Original source
Transcript — VerbatimClick a timed line to jump · ⧉ to share it

Speaker numbers apply only to this recording.

Speaker 1

8:07

Order.

8:08

Roll call, please.

Speaker 2

8:09

Vice Chair Yang.

8:11

Councilmember Bowie.

8:12

Councilmember Coleman.

8:14

Here.

8:14

Councilmember Kim.

8:16

Here.

8:16

Councilmember Jost.

8:18

Council President Naker.

8:19

Here.

8:20

Chair Johnson.

8:20

Here.

8:21

Five present.

8:22

Two absent, being Vice Chair Yang and Councilmember Bowie, whom are both excused.

Speaker 1

8:29

All right.

8:30

So we are continuing the budget saga.

8:33

And on this episode, don't play.

8:35

We have the Office of Technology and Communications, OTC.

8:39

Welcome, Director.

Speaker 3

8:42

Thank you so much, Chair Johnson.

8:44

Good morning, everybody.

8:46

It is so great to be here.

8:49

Um Council President, Council members.

8:58

This has been the quickest year of my life.

9:02

And um grateful for for some reasons of that, and also just life is passing by too quickly.

9:34

That has been going on since July of twenty twenty-five.

Unassigned speaker

10:00

But part of the decision making that happened during the cyber event was the tough decision to sunset some old legacy technologies whose replacements whose modern systems weren't quite ready for prime time yet.

Speaker 3

10:07

We made that tough decision because we knew something around 60 to 70% of organizations that have a cyber attack experience another attack within six months.

10:15

We wanted to make sure that that did not happen to St.

10:18

Paul and that didn't happen to St.

10:20

Paul.

10:21

But what that meant is that we had systems that we brought in a little bit early, and so we've been working very, very hard over this past year to get those systems working for the city, streamlining our systems and supporting city service.

10:34

OTC has been working so hard over 2026 that right now 30% of my staff of our staff have over 200 hours or more of vacation banked

Unassigned speaker

10:44

up.

Speaker 3

10:45

That was an issue that I, you know, sometimes IT people just don't want to take vacation.

10:50

They really get a lot of satisfaction of their jobs.

10:52

I am, I I used to be one of those.

10:54

Now I know that I need to take full breaks in order to survive.

10:58

But you know, as the leader of this organization, I we made progress in early in my tenure to make sure people were taking their vacations so we didn't have this end of year problem.

11:07

Um that kind of went by the wayside once we had our cyber attack, and we have so much work to do.

11:14

I'll say that I'm continuing continuing to work with my staff to take those vacations.

11:19

We need those breaks, but let's give a quick little example of the dedication we have from this team.

11:23

So one of our talented employees had a Friday blocked a couple of weeks ago on his calendar.

11:29

A meeting came up, and he was at that he was invited to, even though it was shown that he had vacation on his calendar.

11:34

And I told him, hey, don't worry about that meeting.

11:36

I'll step in, right?

11:37

I'll I'll play your role for you so you can take that day of vacation.

11:41

The people who created the meeting went directly to them, him and he, they were like, Can you please be at this

Speaker 4

11:46

meeting?

Speaker 3

11:46

And he was like, Okay, yes, I I am not gonna take a vacation day.

11:49

I'm just saying that just to show the dedication that we have here.

11:52

We are really trying to get the city working so we have that firm baseline of technologies that are modern, secure, and ready to serve the city.

12:00

So I will now jump into my presentation, but I just want to let you know that I love this team so much.

12:05

Um, OTC has the most dedicated, curious, and talented people, and um really the best crew I've ever worked with, and I love coming to the city every

Unassigned speaker

12:12

day.

Speaker 3

12:14

All right.

12:15

Today we'll start with a short summary on the outlook of uh 2027.

12:19

Uh, we'll do a quick review of 2026 and then really jump into the details of our budget.

Unassigned speaker

12:28

All

Discussion Breakdown — Share of Meeting
Procedural██████████████████████████████30%
Technology and Innovation█████████████████████21%
Legislative Advocacy█████████████13%
Land Use Regulation██████████10%
Public Works████████8%
Budget████4%
Signage████4%
Public Policy████4%
Public Safety██2%
Summary of Proceedings

Saint Paul Budget Committee and City Council Policy Committee – October 21, 2026

On October 21, 2026, the Saint Paul City Council held two sessions: the Budget Committee reviewed the Office of Technology and Communications (OTC) proposed 2027 budget, followed by a City Council Policy Committee discussion of standard operating procedures for honorary street co-naming. Both were discussion and informational sessions; no formal votes were taken. The provided agenda listed only the Budget Committee item, while the raw transcript also includes the Policy Committee meeting.

Budget Committee: OTC 2027 Budget Proposal

  • Roll call showed five members present (Coleman, Kim, Jost, Noecker, Johnson) and two excused (Vice Chair Yang and Councilmember Bowie). OTC leadership presented the 2027 budget proposal.
  • OTC Director highlighted 2026 as a recovery year after the city's cyber event and noted that 60–70% of organizations that experience a cyber attack have another within six months. The department said 30% of staff have more than 200 hours of banked vacation because of the workload.
  • Proposed 2027 general fund changes include an increase of about $1 million; three new enterprise portfolio governance FTEs; three GIS analyst positions moved from Public Works on a budget-neutral basis; a $100,000 request to implement the cyber after-action improvement plan; and reductions including a deputy director position, a management assistant, two vacant positions, $105,000 in website vendor support, and roughly $67,000 in professional services.
  • OTC reported a 2026 protected variance of about $60,000 tied to cyber recovery costs. Two security operations analysts fielded more than 3,000 security alerts in 2026, about 60 per week, and acted on about 1,800; tooling documented at least eight similar attacks that were automatically stopped.
  • Other OTC updates: an after-action report recommended 42 tasks to prepare the city for future incidents; Project Bedrock will modernize the city's core network and infrastructure with core work in 2028–2029; OTC launched an AI Helpbot/support front door and St. Paul.gov 2.0; and HR requested 2027 funding to modernize the payroll/timekeeping platform.
  • The central service fund is proposed to rise by more than $2 million, driven largely by Microsoft enterprise license increases, security-related licensing, global hardware price increases, and the addition of the Polly permitting/licensing system. PEG cable revenues are declining. OTC said local peers have seen Microsoft agreement increases of up to 30%, while hardware costs rose 15–25% globally; St. Paul's hardware increase was closer to 10%. OTC expects the market to stabilize in 2027 but said AI demand makes forecasting uncertain.

Questions and Discussion

  • Council President Noecker asked how the three enterprise portfolio governance FTEs would work. The Director explained they would create a citywide governance structure, including an IT strategy/governance lead, a product council lead, and a portfolio analyst, to manage a portfolio of about 250 requested or in-process projects and stop disconnected technology purchases.
  • Noecker also asked about the $100,000 after-action funding and the central service fund increase. The Director said the money would cover contractor support, project management, and one-time appliance upgrades across 42 tasks, and that the initiative will ultimately cost more than $100,000.
  • Councilmember Kim asked whether the governance FTEs were the same as the GIS positions. The Director said they are separate; the three GIS analysts currently work in Public Works, and centralizing them would add capacity beyond the city's current two-person GIS team.
  • Kim also asked about outstanding cyber-event costs. The Director said OTC had no outstanding expenses and had paid its last third-party attorney bill; the city's emergency management office manages citywide reimbursement and spending questions.
  • Councilmember Jost expressed support for the staffing proposal, saying understaffing can create overtime and lacks redundancy in critical technology and security roles.

Policy Committee: Honorary Street Co-Naming SOPs

  • In the second session, the Policy Committee discussed whether and how to restart honorary street co-naming. The council adopted a resolution on September 9, 2026, to restore the practice subject to council approval of standard operating procedures; no additional co-namings can be approved until those SOPs are adopted.
  • Public Works representative Randy Newton shared a partial inventory of 13 known co-named locations, with eight resolutions located, adopted between 2012 and 2017. Most segments were under a mile and were signed at four or fewer intersections. Public Works recommended limiting co-namings to continuous street segments, using logical and consistent sign spacing, capping signed intersections at four, requiring a whereas statement explaining the choice, and having Public Works review locations and intersections in future resolutions.
  • Councilmember Bowie presented a proposal to route applications through the Heritage Preservation Commission and PED, with criteria including significant contribution to Saint Paul, geographic connection, historical or cultural significance, community support, and optional council sponsorship. Councilmember Johnson's proposal, based on Ward One's draft with her office's edits, included similar criteria plus a 10-year sunset, no taxpayer funding, and a reviewing commission to be developed by staff. Both proposals made clear the co-name would be honorary and would not replace the legal street name.
  • Assistant Mayor and PED Director McMahon questioned the proposed use of the Heritage Preservation Commission, noting HPC is focused on the built environment and on permanent street renamings, which have much larger resident impact. Councilmember Johnson also opposed placing the process with HPC, favored a 10-year sunset, and said her office's suggested edits were not incorporated. Councilmember Jost opposed restarting co-naming entirely, arguing resources should go to public safety and infrastructure needs such as pedestrian crossings, street lighting, and street markings. Councilmember Kim noted both proposals are honorary only and asked about differences from the petition-based street renaming process. Council President Noecker said third-party review was important to avoid political naming decisions, and raised the need to vet negative history and prevent a slippery slope with limited staff capacity.

Key Outcomes

  • Budget Committee: No vote was taken. The OTC budget proposal will continue through the city budget process, and OTC committed to sending written follow-up answers to council questions.
  • Policy Committee: No vote was taken. Councilmember Bowie will continue working with the administration and council colleagues to refine the SOP proposal. Unresolved items include the review body, sunset provisions, sign and cost specifications, public safety concerns, county-road requests, and whether and how to vet honorees' full histories.

Meeting Transcript

Order. Roll call, please. Vice Chair Yang. Councilmember Bowie. Councilmember Coleman. Here. Councilmember Kim. Here. Councilmember Jost. Council President Naker. Here. Chair Johnson. Here. Five present. Two absent, being Vice Chair Yang and Councilmember Bowie, whom are both excused. All right. So we are continuing the budget saga. And on this episode, don't play. We have the Office of Technology and Communications, OTC. Welcome, Director. Thank you so much, Chair Johnson. Good morning, everybody. It is so great to be here. Um Council President, Council members. This has been the quickest year of my life. And um grateful for for some reasons of that, and also just life is passing by too quickly. That has been going on since July of twenty twenty-five. But part of the decision making that happened during the cyber event was the tough decision to sunset some old legacy technologies whose replacements whose modern systems weren't quite ready for prime time yet. We made that tough decision because we knew something around 60 to 70% of organizations that have a cyber attack experience another attack within six months. We wanted to make sure that that did not happen to St. Paul and that didn't happen to St. Paul. But what that meant is that we had systems that we brought in a little bit early, and so we've been working very, very hard over this past year to get those systems working for the city, streamlining our systems and supporting city service. OTC has been working so hard over 2026 that right now 30% of my staff of our staff have over 200 hours or more of vacation banked up. That was an issue that I, you know, sometimes IT people just don't want to take vacation. They really get a lot of satisfaction of their jobs. I am, I I used to be one of those. Now I know that I need to take full breaks in order to survive. But you know, as the leader of this organization, I we made progress in early in my tenure to make sure people were taking their vacations so we didn't have this end of year problem. Um that kind of went by the wayside once we had our cyber attack, and we have so much work to do. I'll say that I'm continuing continuing to work with my staff to take those vacations. We need those breaks, but let's give a quick little example of the dedication we have from this team. So one of our talented employees had a Friday blocked a couple of weeks ago on his calendar. A meeting came up, and he was at that he was invited to, even though it was shown that he had vacation on his calendar. And I told him, hey, don't worry about that meeting. I'll step in, right? I'll I'll play your role for you so you can take that day of vacation. The people who created the meeting went directly to them, him and he, they were like, Can you please be at this meeting?

SUMMARIZED BY OPENPUBLICA AI
TRANSCRIPT VIA PUBLIC VIDEO
openpublica.com