Note on date discrepancy: The agenda, minutes, and transcript all indicate the meeting took place on April 28, 2026 at 4:00 p.m. The required date provided for this summary is April 29, 2026. The following summary reflects the content of the April 28 meeting.
The Rochester Public Utility (RPU) Board met on April 28, 2026, at 4:00 p.m. in the RPU Community Room. The board approved a consent agenda, awarded a bid for manhole rebuilds, accepted the 2025 audit report, and authorized expenditures and funding mechanisms for several water and electric infrastructure projects. All votes were unanimous.
It is 401 and I apologize, guys. This meeting is now called to order. As a reminder, this uh it's going to be recorded and recording will be available on the city website. And then the first item we have on the agenda is the approval of the agenda. And I'm just gonna turn it over to the general manager for a quick uh would like to suggest that we change the order of the agenda and take item 5D and move it ahead of 5A, maintaining the numbering just to accommodate our auditors' travel schedule and get them out of the meeting a little bit earlier. So I would uh offer an amendment to the order of the agenda moving 5D ahead of 5A. I'll move to uh approve the uh adjust the amended uh agenda for this night's meeting. Thank you so much. Motion second, any discussion? Hearing none, all in favor, say aye. Aye. Second. Oh, I apologize. Second. Second. Thank you, Wendy. Any discussion? Hearing none, all in favor say aye. Aye. Aye. Opposed? Carries. Perfect. Yeah. Next up, we have our safety moment or our cyber safety moment with Director of Information Technology, Mr. Kelchan. Thank you. And uh so good afternoon, everyone. Uh safety and security both start with awareness and kind of in an homage to some of our practices that we've had in the past and some of the safety moments with Bob Cook. Uh I figured I'd start us off with a story. Um so recently I was at a sporting event um and I happened to park in one of those managed parking lots with the meters in them. You know, the ones where you pull in, get your number, and then you're supposed to go up to a kiosk effectively to pay for your parking. So when I started walking up to the kiosk sign, you know, the kiosk looked right color, had all the it was the city of Minneapolis, all that kind of fun stuff on it. But then I finally got to the QR code sticker and notice it was kind of torn on one corner. So I paused for a second. And it basically raised a simple question. Is this the original QR code? Or did somebody else place a new one over the top of it? And this situation kind of reflects something that happens a lot now, and we've been seeing more in the cybersecurity industry, uh, QR code phishing. Basically, where attackers place a fraudulent QR code um over the top of another thing, and they often do it in public places, um, so that when you scan them, uh you're redirected to a fake payment page or to capture your login credentials or something like that. And because QR codes are kind of hard to visually verify, people tend to trust them more than links and things along those lines. So the takeaway is really straightforward. That two-second pause can obviously prevent a really big issue. Um, if something looks altered or out of place, just don't scan it. Use a trusted app, uh go directly to the official website for the parking place, or choose an alternative alternative payment method. And that same kind of small habit scales. The same quick verification step, you know, applies to links, attachments, and login requests. And pausing is a really simple control, but it's one of the most effective cybersecurity ones that we have. So thank you guys for your time. Thank you so much for that.