OPENPUBLICA · PUBLIC MEETING RECORD
Record of Proceedings

City of Waukesha Information Technology Board Meeting Summary - February 4, 2026

Public MeetingsWednesday, February 4, 2026
BodyWaukesha, Wisconsin
SessionPublic Meetings
DateWednesday, February 4, 2026
StatusFILED
Video Record

STREAMING COPY IN PREPARATION — RECORDING AVAILABLE FROM THE ORIGINAL SOURCE

Transcript — Verbatim
0:35

Item four is approval of minutes.

0:37

As I mentioned before our meeting, um our January minutes did not uh get attached, so we'll hold those over till our next meeting to get approved.

0:49

Um that takes us to item five, which is our business items.

0:52

We have a few uh items to talk about tonight.

0:55

And 5A is to review and approve a contract with Main Star for a new permitting code enforcement and inspection system.

1:04

Chris, you want to kick this off?

1:05

Yeah, sure.

1:06

Um our current uh building permit code enforcement um sys system went in in 2014, and um I a couple years ago they gave us notice that they were gonna end support for the on-premise uh version, and so we're gonna have to move out to the cloud, and so we had um we had had some issues with that vendor.

1:31

Uh the product had been sold four times at least four times uh since we've owned it.

1:39

Uh the first sale coming about 30 days after we inked the contract.

1:43

So um it's been it's some of the support's been problematic, and um and so we said, well, if they're gonna force us to go to the cloud, we're gonna take this as an opportunity to um look around and see if there's a a better product out there because essentially the quote that they had given us, there was no real break.

2:06

We're gonna have to pay migration costs and and that sort of thing.

2:12

So uh during the 2025 CIP budget process, this project was approved.

2:19

And so last year we went out to RFP and um reviewed the RFP.

2:25

We we scored them.

2:26

So we have Maria Pandazi from uh she's our deputy community development director, and then uh I have Mark Probuki, he's my uh business solutions architect.

2:37

Uh they've been uh heavily involved with this project, but we went out to RFP.

2:42

Um there was a group from IT community development and engineering.

2:48

Uh we scored the RFPs, we ended up bringing in a handful uh for vendor demonstrations.

2:56

Uh we did went through the demos and uh Main Star is the one that bubbled up to the top.

3:02

And um so this is this is uh what we have before you.

3:08

It is a SAS solution.

3:10

So I did it, I did attach the IT uh uh technical questionnaire uh answers that we got back, and so with that uh we'll open up the floor to questions.

3:24

So operationally, uh Maria can hand uh handle those questions and Mark is super familiar with uh the current product.

3:35

In fact, he's uh he's had to do the troubleshooting for their support um on some stuff, and then he's also pretty f uh really familiar.

3:44

He kind of led the the demo part of the RFP um process.

3:49

So Maria, is there anything you want to add before we pepper you with questions as far as I know this touches your department probably more than any other sound?

3:58

It does, it does.

3:59

We um we probably have at least six thousand either permits, projects, or code cases that go through this software every every year.

4:10

Um and that number is growing.

4:13

Um I think Chris did a good job of explaining our challenges and the the cost of keeping the software moving to the cloud didn't seem to make a lot of sense without assessing better software for us.

4:27

One of the challenges I think in addition to the um the customer support or lack of support or challenge of support, was their customer portal also, so for when contractors are logging in or the general public wants to report something their interface, I think that's the right word.

4:49

Um not IT, but they're you know, what what the public sees is very cumbersome and it's not very customizable.

5:00

Um one thing that I really wanted to see out of new software was a really nice customer facing um piece, and and that's I think what we're gonna get with Main Star.

5:11

So I was I was on council when we implemented track it.

5:16

So I remember that.

5:18

And I I do remember that their customer portal was one of the things that was supposedly a selling point of that product.

5:25

So it's disappointing to hear that that never really well that portal from 2014 is the same portal we have now in 2026.

5:33

I'm sure it's good.

5:34

Yeah, and I think that's the issue.

5:35

I mean, it knows its job, yeah, but it's very difficult to navigate, and it's not, you know, maybe it was okay in 2002.

5:44

Yeah.

5:45

Well, Maria was just uh commenting, she was at a conference a couple years ago for it, and they they talked about one of the jokes that during the keynote was that their uh customer facing portal is what yeah, somebody stood up and said, Oh, it's state of the art for 1972.

6:04

So they I mean I think they acknowledged that it was an issue, or they heard it was an issue, but nothing really ever changed with it.

6:12

So I'm really looking forward to that part of Main Star actually.

6:17

Questions from the board just sounds to me like they rang the money out of it, you know, uh early on 30 days after we saw it and then proceeded to sell it and it for bagged data.

6:33

So yeah.

6:36

So what other um features are you looking forward to in the software compared to what you currently have?

6:43

Um considering how much I mean it appears to be quite a bit more expensive.

6:47

Yeah, annually because of the cloud costs.

6:49

Right.

6:50

Um yeah.

6:51

Uh but it's right in that same ballpark as track it would have been in the cloud.

6:55

Got it.

6:56

Yeah.

6:56

So there was only one out of out of the three that we brought in for demos, there was only one less expensive than this one.

7:06

But it was uh product that really wasn't finished.

7:10

It was kind of like if you were going from paper to electronic, that would have been a first good step.

7:17

Um, but it it but it just wouldn't work for some, you know, uh I mean some of their just calendar functions for scheduling inspectors wasn't there with that product.

7:28

So um there's you know, there's a lot that was left to be desired there.

7:32

Um so but I'll let you finish answering brands.

7:36

No, I think that's that's the thing too with the cost of track it in the cloud would have been similar to this.

7:44

Um in addition, I think there's a lot of um customization that we can do with auto automatic emails and um that would be a little bit easier to adjust and so forth.

7:58

Um right now we can do that, but it's a little bit again, it's just a little cumbersome to do.

8:04

And so um I think that is another feature of general and has a lot of modernized features, is kind of what you're what you're saying.

8:14

Yes.

8:15

You do a lot of the functions, but just in in more efficient and modern way.

8:19

I think that's a good good summary.

8:21

And there's a lot of features like if they're working with the company and then they have uh employees right now.

8:28

Each employee has to have like a login or some shared login.

8:31

Now you can have a company with employees and they can log in as an employee of that company, so you have that relationship.

8:39

So that's a selling point.

8:40

Um if let's say licenses are expiring for contractors, you can email notify them through flexible workflows so you can customize uh you know, let's say you want to change something, track it's gonna hardwired, you have to stick to their flow.

8:54

Um, it's programmed that way with uh more modern infrastructure.

8:58

Most most of the software had this.

9:00

You can flexibly change how you want it to behave.

9:04

You want to send an auto email after they apply, you can set that up.

9:08

You can just you know build it into a workflow.

9:11

Um so there's a lot of features, um, even permits expiring, you can set up uh auto notifies for that saying, hey, your permits expiring.

9:19

Um so it can do that automatically behind the scenes.

9:22

Uh just a lot of features that we're hoping to get uh, you know, but aren't available in track it, they just don't have that.

9:29

Um that's meant to sort of look and feel the UI's kind of dated.

9:33

There's a lot of um bugs in the software.

9:36

Um they're they're listed along.

9:39

Um, but uh we did a lot of like since it's on-prem, we were look at their code and um fix some things, make things work better or look better, but it's just uh been an ongoing challenge.

9:52

They've done, I think they're kind of stretched in on their side.

9:56

Um all their features have been going into the cloud.

10:02

So yeah, all the uh you know updates or fixes are on the cloud platform now.

10:07

So it's just like you're kind of hanging on, and eventually they'll uh cut it off for mobile apps.

10:14

They've actually ended support for that.

10:16

Um, but the the thing is there their mobile app isn't it been working, it's not functional.

10:21

Um they've admitted that, and it's just like well, we can't go to that, it doesn't work, and um so it's kind of like that's kind of the state they're in.

10:31

Right for sure.

10:33

We also spoke with some other communities that use Main Star, and they were very pleased with it.

10:39

They were pleased with their customer support.

10:42

Um, so that also was I think uh selling it.

10:46

One more question.

10:47

What about interfacing with um any other existing systems?

10:50

Is that on your roadmap at all?

10:52

Oh definitely.

10:53

Do they support that pretty seamlessly and they have experience with that?

10:58

Like your financial system, whatever you have to do.

11:01

That was that was part of the RFP questionnaire.

11:04

Uh not only just the RFP even pass that I sent uh you know pages of questions to our our contact there and kind of drilled them on you know our municipal financials, our current integration.

11:17

Uh we're kind of limited, like uh, you know, APIs, but we we're gonna replicate how track it did the file nightly interface um capabilities there to do an API.

11:29

Um we also looked at laser fee showing integration there, that's all capable.

11:33

Uh yeah, GIS is gonna be way improved right now.

11:38

It's just uh I don't even know if I should touch on that, but it kind of goes through four hops from an access database to a temporary SQL database to a job, and it's it's it's kind of so now it'll go it's it's pretty interesting.

11:54

Uh but now it'll go directly to uh is that uh our GIS RESO it'll go directly, um, which is sweet.

12:02

Um so we won't have those hops in there.

12:04

Um some of them some of the vendors had real time, so it's pulling directly.

12:09

This one will just be pulled in uh I believe overnight, which that's kind of fine with the changes.

12:15

We're not making like dramatic changes throughout the data we need to pull in.

12:19

Uh and I think um uh an credit card authorized.net they support fine.

12:25

Um so all of our interface points were there.

12:29

Uh database-wise uh was the most interesting.

12:32

We spent a lot of time on that.

12:34

So we're going with their uh rather than customize all these things, like when you customize software extremely you get into a pickle where you've customized it such that you know, then when they go to support you, oh whoa, you're way different.

12:47

So uh going straight what their offering is, which is gonna be um highly available uh database in the cloud.

12:56

Uh the alternative would be to create some kind of virtual server in the EC2 instance in AWS, and well, if it goes down, you may be down a few hours, and so that didn't sound too good the more we looked at it.

13:09

Uh and then uh the only there's kind of a pro and con uh with the HA offering uh that we would probably getting at data would be a little bit more difficult because it's they restrict that um because they don't want people going after and running performance, things like that.

13:27

So we may partner with them to build those in their portal uh versus having like our own EC2 instance uh which is a virtual server, and then we can just go at the database all we want.

13:38

Um but the caveat is high high availability, so that seemed to be a better solution, and also being non-customized so that way they can support us right out of the box.

13:52

Thank you.

13:54

This new system will that allow the public to access to submit permit requests and get status updates and be able to put it.

14:03

Yes, our current one does now circa 197, you know, the you know, it's not it's not um very clean and easy to find sometimes.

14:14

Um so we do have that, we have that capability.

14:18

Um but this the way it looks and the way it's formatted on screen is much cleaner, much neater, and we can uh customize that ad notes and things to it where in the track it system.

14:32

It was really challenging to add a note like where you really needed to make a contractor aware of something.

14:39

But yeah, right now we we process all our electrical and plumbing permits, those are auto-issued through you know the contractor uh who's a you know vetted licensed contractor would just apply and get that those permits auto-issued.

14:53

Um certain permits they submit and uh there's plans to review and so that kind of just pauses the process until it moves to the next step.

15:04

But so right now their contractors are able to log in and see the status of their permits now too.

15:09

Well, homeowners be able to build their own.

15:12

Yeah, so right now we have because I like the renewing.

15:16

Yeah, okay.

15:17

I have experienced the permitting process through the city walkshop.

15:22

Oh, you have okay.

15:23

Yes.

15:24

Have you done the e-track it online?

15:26

I did not.

15:27

Okay.

15:28

I was managing the project for my home.

15:30

Okay.

15:31

I walked into the permitted office and just kind of laid out what I'm trying to do.

15:35

Okay.

15:35

And there was all kinds of issues that we don't need to get into this evening.

15:39

But uh I do know it was a very cumbersome and challenging process.

15:43

Uh so I'm hoping that this new software makes things more streamlined.

15:47

Uh, because I also know several other people that like the U projects in the whole and have also experienced you know issues with the current system.

15:56

Yes, so we do have a button.

15:59

What have you, but yeah, I'm very interested because I have some projects coming up.

16:04

Well, this will be for this won't be up and running for a while.

16:08

And it'd be by end of year, but yeah.

16:09

Yeah, so I'll probably still be able to track it.

16:11

But I would write currently right now, I could get logged in or set up an account on your existing system in everyone.

16:17

As a public, yeah.

16:18

Okay.

16:21

Will then the public be able to schedule inspections with the inspectors via this stuff, or do they still have to call?

16:28

Um it's so for building inspections, it probably would be a phone call or an email, just because the inspectors schedule, you know, some inspections may take longer or less time, so they kind of schedule their time right now for electrical and plumbing, it's all scheduled online.

16:52

Okay.

16:52

So what's nice about the newer software is um the way they handle scheduling.

16:59

So right now it's like AMPM, and uh with the newer software, they can do it by hour.

17:06

So you have like say um inspection.

17:10

Um I was always talking to Mark, they'll have the ability to do that.

17:14

They don't have the ability to let's say uh an inspector has meeting in the afternoon, they couldn't like automatically block out a day or every Wednesday or things like that.

17:24

But the scheduling is improved with the new software versus current, so that'll be a bonus.

17:34

And you've already got this in the 2025 budget.

17:38

We need to go.

17:39

So yeah, it was a 2025 project.

17:41

Obviously, uh it's 26.

17:44

Those funds will just carry over.

17:46

Um so yeah.

17:49

Um, I guess from a financial standpoint, just you can pull it up here.

17:59

Um year two.

18:01

Uh so because it's SAS, year one costs are right up front for you know, licensing costs.

18:08

But uh for year two, they uh those costs stay the same as year one, and then starting in year three, there will be a three percent increase in the in the annual costs moving forward.

18:22

So that was one where they wanted to they started off with five percent right away, and so they were pretty open to uh not just this, but the the contract as a whole, all the red lines that uh Brian running, the city attorney had uh had in there, and then I negotiated the costs and and and that sort of thing, and they said yep, all changes accepted.

18:46

So uh they were real easy to work with from that way.

18:49

Uh they've been real responsive to Mark, uh emails, phone calls, all that stuff.

18:54

So it's been a good experience with them thus far.

18:56

So it's a five-year contract.

18:58

No, it's uh this is just showing um that um oh I guess uh in the contract it shows five the first five years, but if you read right underneath that it's uh three percent uh every subsequent year after that.

19:15

What I'm getting at is is that guaranteed though that rate no?

19:19

Three percent is guaranteed forever.

19:21

Okay, fratuity.

19:22

Yeah, yeah.

19:23

Okay.

19:23

Because I was just wondering about you know, there's there's no bandwidth charges, additional storage charges, anything like that.

19:30

No, down the road, nope.

19:32

Okay.

19:32

And we're not under a certain year commitment.

19:37

We're year to year.

19:39

Um yes, I mean not that we would want a project of this size after two or three years, but we're not committed to being locked in.

19:48

Correct.

19:48

Yep.

19:49

If we we just uh there's uh maybe like a 30-day notice or something like that that we have to give.

19:55

So it was 90.

19:57

Is it 90?

20:00

That's still so I got a question about how do we find uh software companies that you know do what this does.

20:09

Do we go to the other municipalities and say, hey, do you guys have a uh uh you know a company that you've worked with or heard about so uh yeah there is a little bit of that.

20:22

We all have uh peers in other municipalities that we know, and and so um you know we'll we'll shoot emails out hey, what are you doing for this?

20:31

And you know, for like us being munis customers, that's for our financial system.

20:38

There are um there are a lot of Munis customers in this area, Brookfield, Wawatosa, um, New Berlin, and so like we have a when Muniz puts their user group on, it's always in the area here because there's so many customers, so uh you know we can talk to them about that.

20:57

Um but is they these software companies, I don't know if they have staff or if they're or if they hire it out, but they watch municipality websites for RFPs to get posted.

21:10

And so as soon as RFPs um hit our website, um those contractors know.

21:18

And you know, there's times where we're doing a little bit of um you know recon prior to uh budget, you know, trying to figure out what a cost of a new system is gonna be, and so we start just kind of doing some research that way, and we may have some phone calls with some with some vendors, and we may put a request for information out there so that we can get a budgetary number, and then any vendor that replies to an RFI when we post the RFP, we do email them a link to the RFP, letting them know that it's been posted just uh as a courtesy.

21:57

As a note, um our current vendor central central square track it did not respond to the RFP.

22:04

That's correct, yeah.

22:06

And we sent it to them.

22:08

Yeah, interesting.

22:12

Yeah.

22:14

And after they wanted it.

22:15

Yeah, but then afterwards, then they wanted to respond to the RFP.

22:19

It was closed already, so yeah.

22:24

No, so surprise, surprise.

22:26

So, Chris, it looks like from uh from a budget standpoint.

22:32

We came in under capital, you know, the capital side of things.

22:39

Yep, which is good.

22:41

Um are you at all concerned about finding an extra sixty thousand dollars in the operating budget for continued support?

22:50

Uh well, Joe Shiro is he's our finance director.

22:55

Um yeah, uh well, as part of our financial management planning, you know, in the five year that we've been doing.

23:02

Um this has been uh uh this this has been part of the number.

23:06

So I've had I've had these dollar amounts, and so what I've been putting in for my forecast uh budget for the planning has been the most expensive one.

23:18

Um which I think was question yeah, it was probably like another uh 50 or 60,000 more than this one.

23:27

Public words does that all the time they build that cushion in there all the time because well, this is for forecasting what our operating budget's going up, so knowing that we're gonna be switching from track it to something else, we needed some kind of number, and so putting the worst case scenario in there is better because now when we update those numbers on the forecast, it'll you know that's basically it's not ideal, but that that number's been planned for and is baked in.

24:01

Yeah, that's not a shock to anybody next year when that's correct, yeah.

24:05

And budget comes around.

24:07

And you know, the cover sheets uh before they before the cover sheets go on the agenda, uh the finance director, the city attorney, and the city administrator all sign off on them.

24:17

Yep, so you know, if you come down here, they've all seen it, they all know what the numbers are and all that good stuff.

24:25

So no surprises, right?

24:27

Yeah, correct.

24:31

Any other questions, comments, concerns?

24:36

So we're looking for approval of this tonight, correct?

24:39

Mm-hmm.

24:44

Um I'll make a motion to approve the uh contract with Main Star as presented.

24:51

Okay, Sean.

25:00

So we have a motion and a second to approve the contract as presented.

25:03

You're gonna roll call us, Chris.

25:06

Any other questions or comments before we go?

25:11

All right.

25:11

Sean?

25:12

Yes.

25:14

Dan?

25:15

Yes.

25:16

Steve?

25:17

Yes.

25:18

Brandon?

25:19

Yes.

25:19

Bob?

25:20

Yes.

25:23

All right.

25:24

There we have it.

25:26

That passed unanimously.

25:28

Thank you very much.

25:30

Thank you, Maria.

25:31

Thanks for coming.

25:32

Thanks for coming, Mark.

25:33

You can hang out longer if you want.

25:44

Thank you.

25:48

Sometimes it is right.

25:51

All right.

25:52

So that takes us to 5B, which is uh we have some policy review stuff to talk about tonight.

26:01

Actually, our next few items.

26:03

But uh this one is annual review and discussion of IT policies parens, no action needed.

26:11

So I I'm assuming these are things that we're not looking to change.

26:15

Right.

26:16

This is with the policies as is.

26:18

Yep.

26:19

Um one of the requirements for all of our policies is that they get an annual review.

26:24

Um so I've looked over the the four policies that are under this item.

26:30

I've looked over um and I'm not recommending any changes to them.

26:35

Okay.

26:36

And um and so unless unless someone on the board wants to make some revisions to them, um I'm I'm good with where they're at.

26:56

Any questions, comments about that?

26:59

Any concerns about the policies as is.

27:01

We've we've seen them, we've approved them.

27:04

If they're working well for you, Chris, and you don't see any concerns.

27:08

I'm I think the board is with you on that.

27:11

Yeah.

27:12

See some nodding heads.

27:15

Okay.

27:17

Well, not uh put a check mark in the annual review box for those four that are presented change management, email, malware, and security awareness.

27:28

And then we have a few that uh we're gonna look at that we do want to make some adjustments to, starting with uh 5C, which is our AI acceptable use policy.

27:39

Didn't we just approve this, Chris?

27:41

We sure did.

27:42

Yep.

27:43

And then it was approved by the council on the 20th.

27:46

So in our January, this one came through.

27:49

Well, you know, some some things, no matter how many times you look at it, right?

27:54

Right.

27:54

Um so there were a couple concerns when it came to uh let me pull this up.

28:05

Um that's the wrong This is Brian Runnings uh uh red uh uh red lines.

28:11

This came back from staff.

28:14

Probably at audience came from staff, that would make sense based on based on the cover sheet.

28:20

Okay.

28:21

So this is um uh under rules of use for the um for the AI acceptable use policy, item or letter C says users must mark AI generated content, example draft prepared using AI.

28:39

And um so once we rolled this out to staff, the question came up as to um well where's the where do we draw the line with this?

28:53

Do I if I'm asking AI to help with grammar, um do I have to mark that uh my grammar was checked by AI and that sort of thing?

29:07

And then ultimately um in my conversations with uh Tony Brown, the Cine uh City Administrator, is we really don't have any practical way to monitor or police this rule.

29:22

And um so for fun, I uh took this and I um this this question about getting rid of this line and I put it in the AI.

29:36

AI thought we should keep it.

29:38

AI said uh you know, rather than just get rid of it, maybe you can modify it and then gave me like this whole decision tree on you know, which would have been like an extra half a page of policy, and then and then and then all the phone calls that come with the decision tree.

30:00

But ultimately, when you look at the other items that are under rules of use, which I uh listed here, um, you know, we're already regulating who can use AI.

30:07

Um we're already already asking um to or telling people they need to verify that data.

30:16

Um we're you know, we talk about you know, like we're not integrating it, we're um you know how it can or cannot be used with employment related decisions, and then understanding that these prompts can become public.

30:32

So I mean, I guess the the point being here is there's all these other safeguards that we have in place, and and quite frankly, if if someone is being asked if they've used AI for any of this stuff, well, why wouldn't you know there's no harm no foul in saying yeah, use it.

30:54

I mean, I think some of the value that we see with what we have for AI right now is the example I gave earlier in grammar, you know, to hey, can you help me reword this email for clarity type of thing and pop it in there?

31:10

And you know, there are some times where you I don't know, I'm sure some of you have been there where you've had an email open for hours as you craft that email and then you go back and redo it and redo it because it's got it, you just got to communicate just right, and you know, maybe maybe with AI you can get there a little bit quicker than so, anyways, there's some good uses, but anyways, so I'm recommending that we just remove item C part in in particular because we don't have a way to police or monitor that, and and then also we have all these other safeguards in place or rules in place on on how to use AI.

31:50

So um that is that's what I'm I'm looking at this evening is just to prove uh the modified AI policy by removing line C from rules of use.

32:08

So we're we're using uh are we polling uh daily, you know, people that are using and you know, city staff that are using it and and just you know, trying to get a handle on how much AI is actually being in used in our for our um for our Microsoft 365 products, which is Microsoft's product is called Copilot.

32:33

For copilot, we can see who's using it and how much they're using it.

32:37

We have that dashboard uh to be able to log in and see that stuff.

32:42

Um some of the things that we're we're looking at and going through with um Defender is the is our um our malware defense um software, and so what we're doing with Defender because it can show us cloud apps that people are accessing, and we're starting to go through and look at what are some of the different AI apps that are out there, and they give us a Defender gives you a ranking on safe not safe, and I forget the scoring system that they use or how they do that, but um starting to go through and look at all the different AI ones, and and there are a lot.

33:25

I mean, for one, it's just pulling every cloud app that Microsoft knows about that people want to try and integrate with um like on ID and stuff like that.

33:36

So going through and finding AIs and just blocking blocking the bad ones right away straight up, and then from there we're gonna start going after the more popular ones once we get some training on co-pilot and training on AI use in general, like helping people with prompts and and stuff like that, kind of the um the AI 101, and then also through our no before system, just a some security awareness training around AI.

34:11

So going back to your uh email comment, you know, you get you you got five different things going on at least every day, and you know, some days are more intense than others.

34:21

You get interrupted, you're you're putting together an email with AI, and you can't remember, you know, especially when you get to be my age, you know what uh what's going on.

34:32

So you go back to your email and you say, AI, would you finish my thought here?

34:38

You know, because you don't take in what you've written so far, and can AI actually do that?

34:45

Yeah, so like if I'm just uh putting an email together, I don't have to think about I don't have to think about all the grammar that goes with it.

34:55

I type my bullet points up and just in a list and say send an email and hit go and then it generates that email.

35:03

And it fills takes those bullet points, puts it in a into a paragraph, you read through it, um, you know, make sure it's accurate, maybe tweak it, make it your own from there.

35:14

But yeah, you don't have uh that's I mean some of those uses of AI are just that.

35:21

It's just you throw your bullet points together and let it figure out how to message that.

35:27

Yeah.

35:28

Say, hey, I'm trying to do this, and I want to do A B C and D.

35:33

And then and then just hit go.

35:37

Oh and then all your all your former prompts from in co-pilot.

35:43

Just like chat GPT, they're just listed on the left side there.

35:47

So you can go back to one that you had were working on like a week or two ago, and uh, because you can rename and retitle those so they're they're actually meaningful, and then you can go back and open that up and re-engage that conversation.

36:04

What was the I guess intention behind that um originally being in the policy from an IT governance standpoint?

36:19

What was the original?

36:20

I mean so the original draft that came to us said that users had to get permission from their supervisor every time they used AI.

36:31

Oh I remember.

36:32

So then we said instead of like that, so instead of that, like let's let's simplify that.

36:39

And I I can't remember if this is part of like Brandon um Brandon had a list of ideas that we incorporated in this, and I don't remember if that was one, but it was one.

36:49

Yeah, and so that's where this so went from getting your supervisor permission to use AI to mark it as um AI being used.

36:59

Yeah, and I I know you know, I know in the in the world out there, there's a lot of talk about that, and you know, a lot of you you see a lot of stuff now, like on even on YouTube and you know media outlets where there is a disclaimer, you know, and even on TV shows, you know, where it says some of this content, you know, may contain AI generated content or this content was generated.

37:27

So I know there's a uh a push to have that out there.

37:34

I'm not concerned at all about eliminating this bullet point from our policy because I think you know, as you laid out the safeguards are there.

37:43

I think I think there will come a time not too far in the future where this stuff is so ubiquitous that it it's not gonna matter, and we're just gonna take for granted that AI probably played a role in the creation of any content that's out there.

38:00

So, you know, I think forward looking, this this bullet point would have probably been eliminated not too far in the future anyway, just as a matter of course.

38:09

But I think I mean so I remember the permission discussion, and I think because I looked at this revised one too, and I thought it was okay at the time too, and that's why I didn't bring up anything because I think there's a distinction between truly AI generated content and then uh like for lack of a better word, augmented content.

38:35

So you you bring your content that you did you created, whether it's a rough draft or whatever, you throw it in there, you have it create something with your content as opposed to prompting it to create something brand new.

38:47

And so those are two kind of different things.

38:50

And if it's something created brand new, really out of a prompt with you know little data and little input outside of that from you, to me that might be something that you would consider saying, hey, you know what, this was AI generated, as opposed to you know, simple grammar or editing or spell checking, you know all that stuff, yeah, or say, hey, rewrite this email because I wanted to soften the tone.

39:13

You know, to me that's just casual use, and so that won't even apply here.

39:17

So but I think it's good to get rid of it because it it probably is too gray.

39:22

Yeah, there's just there is no way to to really police it.

39:25

Um I was thinking that people would self-report that, and that would be kind of the push for people to do that if it's truly you know the majority of it is AI generated.

39:34

That's kind of was my thought process behind it.

39:36

But I think you know, to Dan's point and to what you've shared with us, it's probably best at this point to just get rid of it completely.

39:45

Yeah.

39:46

All right.

39:48

It's gonna come up with vision after readvision.

39:54

Any other questions, comments?

39:57

Okay.

40:00

Um I will make a motion to approve the uh changes to the AI acceptable use policy as presented.

40:09

I'll second it.

40:14

Motion and a second.

40:15

Any other comments before we Chris, do you want to roll call?

40:18

All right, Sean?

40:19

Yes.

40:21

Yes.

40:22

Steve?

40:23

Yes.

40:24

Brandon?

40:25

Yes.

40:25

Bob.

40:26

Yes.

40:30

And that passed unanimously.

40:32

So I assume we'll see that again at next council.

40:38

Chris.

40:39

All right.

40:40

Yes, it will.

40:42

Uh the 17th.

40:46

Okay.

40:51

Takes us to item D review and approve additions to the acceptable use policy.

41:00

Not the AI acceptable use policy.

41:02

The acceptable use policy.

41:05

All right.

41:06

Chris?

41:07

Yes.

41:08

So one of the things that this will go back a few years, Dan.

41:17

One of the things that we talked about for a long time as a board was a mobile device management policy.

41:24

And we never had a good mobile device management system.

41:28

So we never put a policy out there because we couldn't enforce the policy.

41:34

We drafted one.

41:35

We created one, but I don't think it ever went to council for approval, if I remember correctly.

41:39

Right.

41:40

So looking through, all right.

41:44

So one of the goals for me this year with ITB is to go through all of our policies and procedures and make sure they're they align with the CIS controls and specifically implementation group one.

42:02

Then just and it's kind of like an audit and verifying that our policies and procedures are aligning with what is considered good cyber hygiene.

42:14

From there, um I want to move to probably next year is verifying that we're in line with implementation group number two.

42:23

So one of implement uh one of the policies that implement implement implementation group one calls for is a mobile device management policy.

42:33

Well, looking at looking over what would be in that policy, um, it made more sense to modify the generic acceptable acceptable use policy with a few lines rather than um create a whole another policy.

42:53

So that's that's what um we have um before you today.

42:59

So it's just um should be just those couple of changes right there and right here.

43:05

So we'll start from the top.

43:08

And so you'll see um we are standardized on iOS devices, so iPhones, iPads.

43:18

We don't we don't use Androids here.

43:21

And um that's uh that's a fun debate.

43:26

My staff and I have on a regular basis, Android versus Apple.

43:30

But um I don't item C under under user responsibility says that all c own iPhones and iPads and other mobile devices.

43:39

That's the just in case someone gets an Android.

43:42

Um shall be enrolled in the city's mobile device management system.

43:46

Uh user shall not remove disable or bypass MDM profiles or security controls installed on city devices.

43:53

All user accounts configured on city mobile devices must use a city issued email address.

44:01

Um right now our MDM is Microsoft Into.

44:08

And we we used Verizon Verizon and FirstNet are basically our two um cellular providers.

44:20

Uh we're almost 100% um first net.

44:24

We still have some Verizon, we're slowly moving over.

44:27

But every device bought through Verizon or FirstNet, and even another uh CDW G is another uh uh vendor that we might buy iPads through.

44:41

Um automatically get enrolled in Apple Business Manager, and then Apple Business Managers integrated with our with Intune.

45:00

So as anyone that buys a uh a device, a city device through Verizon First Net or C DW G, uh it automatically goes to um Apple Business Manager, automatically comes down to Intune, and when they open up that box and start to set up that phone, they get a couple screens in and says you must enroll your device into uh Intune, and it's uh click yes or you don't go any further.

45:18

And so then it automatically enrolls now.

45:22

As we get further down here, um we are really gonna look at two different types of of devices.

45:29

One is a fully managed device.

45:33

So, like our police department and our fire department have um iPhones in in their cars, but they're not assigned to anyone.

45:44

And so squad cars.

45:46

So in order to get an app from the Apple i um Apple App Store, you have to have an Apple ID.

45:55

Well, these phones don't have an Apple ID, so they have no access to the app store.

46:00

So every app that they need, we have to push down to them.

46:05

And so, like for the police department fleet, we have a profile set up in Intune, and when we get a new phone that comes into Intune, we push it, we give it that profile, and then all the apps that the PD wants those fleet phones to have, push down to it.

46:22

Uh fire department's going through a refresh on their iPhones right now, and we're doing the same thing for them.

46:28

So the only way they can get an app is um by request of their supervisor or director, and then they have to tell us yes, you can add this app to the profile.

46:41

The second the second type of device would is commonly known as uh co corporately owned personally enabled um device.

46:51

So basically a corporately owned phone, uh, but now you can sign into it with uh like an Apple ID, and that Apple ID now allows you to be able to go get apps from the app store, and so you can use the phone basically at your discretion.

47:10

So when we look at um plans that we have through um through the government contracts, we're it's 35 bucks a month unlimited data.

47:22

Okay, so we have um we have a lot of not a lot, but we have a pretty good chunk of people that have a city issued phone that need to have a city issued phone, and then they have their personal phone.

47:36

Some of it is because they're afraid to use the city phone for any personal use because they don't want to get in trouble.

47:42

Then the other part of that is they're worried about open records requests.

47:47

So when we get down to these changes here, uh you'll see that with director approval, users may utilize a city issued mobile device for limited personal use in lieu of carrying both a personal and a city device, provided such use creates no additional costs.

48:09

So if we're thinking about are we gonna use up all our data, taxed all that stuff, it doesn't matter, we're unlimited and and it's really affordable.

48:18

Users acknowledge that city devices remain fully managed and monitor IT assets, they're in the Intune system.

48:25

If someone leaves the city, we can unlock that iPhone with Intune, we can wipe that iPhone with Intune, and we can reset that iPhone with Intune.

48:35

And so um, it's kind of one of those things, no harm, no foul.

48:41

Um, we've had we've had people leave the city in a in a in a poor way where they wouldn't uh they were signed into an Apple device with their um personal Apple account and then wouldn't unlock it.

48:59

And because we have had no policy, um, we couldn't do anything about it, and so that phone was basically a brick.

49:07

Now with our plan, we just turn off that phone and we and then we just order a new one for that person's replacement.

49:17

The phone comes free, and so thankfully it's not like we lost a thousand dollars on that device, but what we did lose is any kind of trade-in value that that device might have.

49:30

So, I mean, these devices, these older ones, you know, three, four years old, they don't have a ton of value, but we do get some value, which is a credit back towards the the cell bill.

49:41

Um, so there is some value there, and because that phone, you know, in that in this one particular case that I'm referencing was was useless, we couldn't we couldn't turn it in.

49:52

Oh you know, so uh so the changes to the acceptable use are are just around mobile device management.

50:02

And and really I think this covers us from having to have a full mobile device management policy.

50:11

So with that can you open up the and make the font bigger?

50:15

Yes.

50:16

And what you've got that's beautiful.

50:20

Thank you.

50:21

All right.

50:22

So this is uh this one here says that um mobile devices need to be enrolled in our mobile device management system.

50:30

The way we're set up with now, they are automatically.

50:34

Um and then all user accounts must be configured on city mobile devices using a city issued email.

50:42

So this here ties into this one here, saying that with director approval, you can use a device this in this manner.

50:56

Oh do you have a rough idea of like how many devices live within the city that fall into these categories as far as you know the fully corporate owned, corporate managed that you know, like the squad car phones and fire truck phones and well we'll just say just rough 80 between fire trucks and and squad cars.

51:30

80?

51:31

Yeah.

51:31

Okay.

51:31

This is uh I think it's like 30 something on the fire side and 40 something on the on the on the police side from there, and then you and then um and then how many on the other side of like corporate users that have a uh a city issued phone, yeah.

51:51

Well it uh so that a lot of that depends on the department.

51:55

So um you look at um all right, so there's two in IT.

52:01

Me, uh I have one, and then Greg uh Vanessa has one.

52:05

Okay.

52:06

Then you look at the fire department, and it's their command staff, uh battalion chiefs, division chiefs, assistant chief, and chief.

52:21

Okay, and then and then it's the police department.

52:24

I know it's command staff, but then there's detectives too.

52:27

So um I don't have a good number on that.

52:32

Um but um yeah, because then you have uh DPW, you know, and DPW is engineering, uh the clean water plant, uh city garage, and streets, you know, and there's supervisors, and there's inspectors, stuff like that, and then you have community development.

52:53

Um, they have their building inspectors and the building inspectors have phones and an iPad because the iPad is how they do their building inspections.

53:04

So hundreds.

53:08

Yes, yep, hundreds.

53:10

Because I know Park Rec has yeah, I know Park Rec has iPads.

53:14

Yep, they have iPads and they have iPhones too.

53:16

Assuming some of their directors, managers have phones.

53:21

Yep.

53:22

Yeah.

53:23

Okay.

53:23

Question?

53:24

Yeah, the forestry department uh is does a lot with um like tree inventories and stuff like that, live ownership.

53:33

Yeah, I know they've got a lot of apps that manage inventory and pretty wild, like basically every tree in the city is inventoried.

53:42

Yeah, it's rising.

53:44

Um all these phones, there's always somebody that will try to use and abuse the system.

53:49

Have you experienced that or not?

53:50

Um well here's uh the I don't really know like when you look at using and abusing, you know, is someone live, you know, just streaming YouTube on their phone all day.

54:03

Um are they texting and driving?

54:06

That stuff I can't answer.

54:08

I mean, that's like that'd be tough for me to know.

54:12

Okay, that's fine.

54:13

But like because of the unlimited data, you know, um, it's not like you're running over data and and stuff like that.

54:22

Um yeah.

54:26

How about the um personal information?

54:28

Somebody's in there um are they using the phones?

54:31

Like you go to the store and use the phone to pay for something.

54:35

You can't use these phones to pay for lunch, or you got to no that that has to be tied to a credit card.

54:43

Okay, some of us have city issued credit cards for business, and if you're doing that, well, you you have to turn in that expense report, and you have to justify that.

54:53

This you know, we're not like the business world where we're out buying lunches for um staff for ourselves or anyone else.

55:04

So that's like buying things in the store, going to Home Depot.

55:07

Yeah, I mean you're a my credit cards for like when we go to conferences and buying stuff off of Amazon.

55:13

Okay, I don't and and then like you have these handful of things like our like our wiki for our IT documentation.

55:22

It's a monthly charge, and they don't they won't invoice us that just charge a credit card.

55:28

So stuff like that.

55:31

So that's just how I use my city credit card.

55:35

I can't speak for everyone else, but but that's the only way that you would be able to misuse that.

55:41

But again, that's gonna hit your credit card statement, and you have to you have to provide the receipt.

55:49

So I mean when the credit card statement comes through, uh before my administrative assistant, she grabs all the we put all our receipts in a folder, and then she grabs those, and then she has to put the account number that each one of those line line items has to hit.

56:08

She sends it to me.

56:09

I not only sign the receipt, but then I sign the credit card statement, and then she submits it.

56:16

So I own that thing 100%.

56:19

And so anyone else has to do that.

56:22

Um can you put your personal credit card and cell phone in like the Apple wallet and do that as if you're at the grocery store or whatever else and tap tap to pay?

56:32

Yeah, absolutely.

56:33

You can do that.

56:35

Again, but that would be your personal one on there.

56:37

Okay.

56:39

And the other thing too, with it being enrolled in Intune, we don't allow jail broken iPhones, which means when if it's jailbroken, they can go download apps off of any place that has an app for an iPhone.

56:56

Okay.

56:57

They're forced to go through the app app store.

56:59

What's the phrase?

57:00

You said jail, what no, what's it called again?

57:02

It's called jail jailbreaking an iPhone.

57:04

Jailbreak, okay.

57:05

Yeah.

57:06

So yeah, it's basically saying my phone is in like some kind of Apple jail right now, because I can only go to the Apple store.

57:14

So if I jailbreak it, now I can go get apps from wherever.

57:17

Okay.

57:18

Which is uh that's an issue.

57:21

And that's part of the issue with me and Android devices.

57:26

The amount of bad apps that get into the uh the Google Play Store.

57:30

Um it's just it's just a constant news cycle about that.

57:35

Is Apple perfect?

57:37

No, but I mean if you're gonna compare Apples to Apples on um bad apps and app stores.

57:45

Now we'll see what happens in the EU with uh with what they're doing with that.

57:51

What are they doing?

57:52

Um they're forcing Apple to open it up to other app stores.

57:56

I don't know if that's gone through, but I know that was uh a big conversation.

58:02

Will we be following them?

58:03

You think?

58:04

I don't know.

58:04

There's some there's some good things that they do over there, and we don't follow them, right?

58:09

Um and then there's you know, so interesting.

58:16

Hey, but if but that is that is between the owner and that Apple device from a corporate standpoint, it's gonna be in our mobile device management.

58:25

We would not allow them to use any other app store except Apple if that same policy was applied here in the States.

58:32

All right, we still get to control that.

58:36

So we don't allow users to what do we allow?

58:45

Let me let me ask it this way.

58:46

What do we allow from a user standpoint from uh DYOD, bring your own device standpoint if anything?

58:55

Well so people who live in both worlds who have a corporate and a personal phone, or maybe don't have uh corporate, uh a city owned phone, they can't do like they can't read their email on their phone, or can they?

59:10

They can't.

59:11

We it just like you, you can put your city email on your phone, right?

59:17

Still on my iPad.

59:18

Yeah, we we allow that.

59:20

We allow um people to connect their phone to get email, even if it's their personal.

59:27

Um so where does that line get drawn?

59:30

I guess is my question of what can they and what can they or can't they do from that point?

59:36

We don't uh we don't let uh personal devices touch the the network.

59:43

They could be on guest net.

59:44

The the real yeah cow cow network.

59:48

Yeah, cow and yes, cow guest, yeah.

59:51

Um that's what they're they can be on a guest net because that's not our network.

59:55

So and even even iPhones and iPads um that are being used all over the city.

1:00:02

We tell them do not try and join uh the the cow wifi.

1:00:08

If they can get into Office 365 through their phone, or or any mobile device and iPad, whatever.

1:00:18

And you know, potentially touch any apps that are in there, but that's through you know a secured mechanism.

1:00:27

So that's okay.

1:00:28

Well, it's through it's you know, they're getting those apps from the Apple App Store, you know, and then they're signing in, and everyone has MFA.

1:00:38

And so that's the other thing too.

1:00:41

Like when you look at like uh BYOD, I mean we are um I mean we're we're zero trust here, so we don't let people bring their um stuff here to work on.

1:00:55

Um you can't uh put our VPN client on your home computer.

1:01:00

Um now you can access you can do all the Office 365 stuff from any computer and any browser, but again, your your MFA and all that stuff, so you're more secure.

1:01:13

And so accessing those cloud apps I'm I'm fine with it.

1:01:20

Plugging into my network, no.

1:01:22

Okay.

1:01:22

So because then how do you know?

1:01:25

Yeah, how do you know, right?

1:01:27

And in closing through VPN.

1:01:30

Yep.

1:01:30

So VPN is uh they're only on um city devices.

1:01:35

Okay.

1:01:37

I don't have an issue with that.

1:01:39

I just I you know from a corporate, like from a personal standpoint.

1:01:45

We have we have a different mantra where I work, which surprises me because they force us to put a lot of we have a BYOD policy that forces us to basically put apps on our personal device and to have a personal device that has like authenticator apps and stuff on it, which I think is ridiculous because it's my personal device.

1:02:07

Well, but I guess that's my you know that's that's my cross to bear, and that's my you know responsibility for wanting to continue to work there.

1:02:16

That's the that's the one app that's the one app that we we've asked people to put on their personal phones, but it's an authenticator app.

1:02:23

It's not like we're asking you to put the full suite of apps on there just to get in.

1:02:30

But it makes my personal device a mission critical piece of my ability to do my job.

1:02:37

Oh and that shouldn't be my responsibility to do in in my personal opinion.

1:02:44

Yeah, we're I don't want to get off topic road many things in many different industries.

1:02:52

I healthcare primarily.

1:02:54

Yeah.

1:02:56

Okay.

1:02:58

Well, I think I mean I think what what's here makes sense from you know the justification of uh you know having it there.

1:03:07

I think you know, I think operationally we're doing what we we need to be doing, and this supports that.

1:03:13

Yeah, I mean, this isn't really a change to anything operationally, it's just kind of documenting how we're already doing things right, yeah, and coming into compliance with uh best practices, best practices and standards, standards and practices that we're trying to meet.

1:03:35

Any other specific language under the section I which is with director approval?

1:03:41

Is it director U or any directory?

1:03:45

Uh so my staff, if they had uh a phone, they would have to have my approval.

1:03:51

Um DPW, they have to get Alex Damien, the director of public work, director of the department that they work in.

1:03:57

Okay, yeah.

1:04:02

Chris, I did have oh, never mind.

1:04:05

That's the next one.

1:04:07

I'm I'm good with this.

1:04:11

All right, anyone want to motion?

1:04:13

Yeah.

1:04:15

Motion that we will approve the acceptable use policy.

1:04:22

And I'll second that.

1:04:26

So we have a motion to approve the changes to the acceptable use policy as presented.

1:04:32

All right, any other questions, comments before we vote?

1:04:35

Chris, call the role.

1:04:36

Sean?

1:04:37

Yes.

1:04:38

Ann?

1:04:39

Yes.

1:04:39

Steve?

1:04:40

Yes.

1:04:41

Brandon?

1:04:41

Yes.

1:04:42

Bob?

1:04:43

Yes.

1:04:46

And that passed unanimously.

1:04:50

Okay.

1:04:51

Takes us to item E.

1:04:55

And Chris, I assume that'll be moving on to council at our next meeting.

1:05:00

Yes.

1:05:00

Okay.

1:05:01

Now, item E.

1:05:02

Review and discuss enterprise asset management policy.

1:05:07

Okay.

1:05:08

So this is a uh a new policy.

1:05:12

Um before you guys.

1:05:15

I thought we had talked about this once last year, but um, because I actually had a date on the original uh starting to wrap my brain we had was I had a date of like April of 25 at the bottom.

1:05:29

Yeah.

1:05:29

And then I went and I looked through all of our uh agendas last year and uh could never find it.

1:05:37

So I'm like, all right.

1:05:38

Um I guess I never brought this through.

1:05:43

So um yeah, so basically um the enterprise um asset management policy is basically saying that we need to have our assets in an asset management system.

1:05:57

We need to understand what we what we own, what's on our network, um, and really kind of manage that whole uh device lifecycle from um from procurement through recycle basically.

1:06:16

Oh we um take a look at the policy here.

1:06:22

Um we define what an enterprise so here's the purpose of the policy.

1:06:30

Um enterprise asset management is the process of procuring, identifying, tracking, maintaining, and disposing of an asset owned by an enterprise.

1:06:38

The enterprise asset management policy uh provides the processes and procedures for governing the enterprise asset lifecycle.

1:06:47

Um we go through the definitions, and I'm not looking for action tonight.

1:06:53

This is first presentation to you guys, so you can see it.

1:06:57

Um look it over, and then I'll bring it back in April, and um and we can we can do some more with it.

1:07:06

So it's uh your standard definitions, what that looks like, um user responsibilities, and then the IT responsibilities.

1:07:16

So first, from an acquisition standpoint, we this is um so this is the same language that we have in our software policy, and it's uh basically um they have to be acquired um through the city using the city purchasing policy through IT.

1:07:39

IT has to be involved.

1:07:41

Um we have to review that I and then the capital projects part of it, which you guys are very familiar with.

1:07:49

Um then when we look at um going four down, this is really like what what we need to do and and how we manage assets now.

1:07:59

So um we assign unique identifiers uh to every asset.

1:08:06

Typically, we just use uh the serial number of the device as the unique identifier.

1:08:11

Um we are starting to put actual asset tags on workstations and laptops.

1:08:19

We're not asset tagging like docking stations or monitors or or phones, um, just um just uh laptops and desktops, and then within the asset management system, this is the this is the uh this is what we're collecting.

1:08:39

So when we when we order laptops and they come in, they have uh they have all the barcodes on the outside of the package, and so we take a barcode reader and we scan them into our asset management system, and so we already have the serial number, um, the make, the model, all that stuff, and then when we bring it in there, we put the purchase costs in there, we put the warranty expiration date in there, and then we put the the device's expiry date in there.

1:09:12

So we get a four-year warranty with devices that we buy that's based that's um mandated by state contract.

1:09:22

So uh HP laptop will have a four-year warranty, and we put a six-year expiry uh date on it.

1:09:30

So we are now replacing devices every uh six years.

1:09:35

It used to be five, three years of warranty, and then run it for two without.

1:09:40

And now when you look at the demands of laptops and desktops nowadays, there's so much that is web-based, so many applications that are web-based that there's not that demand for the CPU and the RAM, and they all have solid state drives nowadays too.

1:10:00

So they just they last longer and they perform like they were new longer.

1:10:08

Eventually you start hearing that thing grinding away and all that stuff.

1:10:12

So that's that's what we do.

1:10:13

Um start two years ago, the state contract changed, so we get a four-year warranty.

1:10:21

And so that's what we do.

1:10:22

Now when we image the laptop before we deploy it, um we put an agent that connects back to our asset management system, and that so it scans it and then pulls all the software in too.

1:10:38

So we have a our software inventory um is built through that that agent as well.

1:10:45

Um and then it also grabs the Mac address, the IP address.

1:10:50

Um it does um, you know, when we were first building out the asset management system with the client, it did pull all the model serial number and all that other stuff, and um, so um that's what we need to do.

1:11:06

So when we look at um when we look at mobile devices, when they go into Intune, um we export I the iPhones and the iPads out of Intune, our mobile device management system to a CSV, and then we can pull them into our asset management system, and we can synchronize um that way.

1:11:33

And then um, and then verifying enterprise asset inventory every three months.

1:11:38

So a lot of that is um we have different categories for our assets, they're either in store, that means they're sitting on the shelf ready to go, they're in use in repair on loan, expired, or disposed.

1:11:53

So uh, you know, as my techs are going through and doing their PC replacement cycles, it's going back through not only in the asset management system but an active directory and making sure uh what was replaced was removed from AD and has got its proper uh state inside um asset management system.

1:12:16

We also track uh the department and then site.

1:12:21

Um so if it's a fire department, it might that site could be station one, two, three, four, or five.

1:12:27

Um this is the discoveries um portion of it.

1:12:32

Um so part of this is if um if we come across assets that are not in the inventory, we need to figure out why they're not there, and uh that sort of thing.

1:12:48

So we've been doing this long enough where um where all of our lap, all of our devices are are in there now, and um, so it's not really like a big surprise.

1:13:01

Um let's see.

1:13:03

Um yeah, so permanently air gap systems must be approved by IT.

1:13:09

So we have two critical infrastructure utilities on our network, water utility, um, and the wastewater clean water plant, and um, and they have their their SCADA system is air gap.

1:13:22

So any asset that's being bought and being put on there, we we we talk it through with them.

1:13:29

All those PLCs and stuff like that on their SCADA network, we don't touch that is that is for them, they are the experts with that.

1:13:37

We just make sure their SCADA networks uh stay protected.

1:13:42

Um Chris, what's PLC you send you?

1:13:46

Uh programmable logic controller.

1:13:48

Okay.

1:13:49

Uh so it's what controls all the switches and pumps and pulleys and all the manufacturing or water system.

1:13:57

Okay, very good, thank you.

1:13:59

Um, and then we define uh control disposal here.

1:14:04

Um one of the things that we'll get into at a later date with uh with uh data management um is we train our end users not to put any data that's worth anything on their local device.

1:14:19

We everything should be shared to um OneDrive, SharePoint, the network, or stored in uh in a system, but never on the laptop itself, and so I typically do uh a yearly reminder email saying, hey, just reminder, don't store your data locally because if we come up to a laptop and it's have and it has issues, we're gonna give it maybe 15-20 minutes of troubleshooting, and if it's just not right, now we're gonna re-image it, and we'll start from there.

1:14:54

So documenting the removal of the enterprise asset from the enterprise within the asset inventory, so that's making sure that it's removed.

1:15:01

So that's making sure that it's removed.

1:15:04

Um and then the company that hauls our uh electronics away, they give us a certificate of destruction.

1:15:12

Um, and that's got the serial number and all that stuff uh of the device.

1:15:17

So then we can take that and we can attach it to the asset and uh inside the asset management system, and then we can um and then we can change that device to um disposed.

1:15:31

Is that on the same schedule as uh for the residents of the city of Walkershaw, those three three dates that we've got per year for uh electronics?

1:15:41

No, we we have a Gaylord uh back on the dock here, and we fill it up, and when it's full, we call we call up a company.

1:15:49

It's not it's not John's or whoever no, this isn't John's either.

1:15:54

I can't remember the name.

1:15:55

Yeah, and I know you can go to the drop off.

1:15:56

We don't know, we don't we have a we have a company that uh specializes in getting the valuable stuff, yeah.

1:16:04

And then making sure like all those laptops and stuff aren't just let you you know ending up in a landfill.

1:16:12

Question is there a chance that they could take the laptops and take information, try to find information about the city.

1:16:17

Um take the laptops and kind of go through them and find information or not um well that's why we that's why we worked with the company we do work with the e cycle, so that we don't have to do um so we don't have to go through the process of wiping the drives and stuff like that because that believe it or not, wiping a drive is actually time consuming if you're gonna do it the correct way.

1:16:38

Okay, um, because a quick wipe that stuff.

1:16:42

We have a guy that works on digital forensics right here, so he'll tell you a quick wipe, you can get that stuff back pretty quick.

1:16:50

Um but um so that's why we get the certificate of destruction.

1:16:55

We used to like for police department hard drives, we used to stack those things, and then we um in the in the data centers we were replacing computers and laptops, we pull the drive, stack them, and then we would have a company come out and shred them on site.

1:17:12

Take a bit of a fire, yeah.

1:17:14

So the whole machine the actual machine we shredded, they should yeah, so yeah, literally like a paper shredder, but they were shredding hard drives, and ground grind them basically.

1:17:26

That's what we do, right?

1:17:27

So we do we do um so we do e we do e-cycling with our stuff, so we have a company that does that, and then they um also do the certified uh certificate of destruction for white uh destroying the drives.

1:17:43

Uh and then on control just disposal, that's basically lost or stone, just report it uh back to us, and then um, you know the penalties of violations that every policy has.

1:18:00

So with that, you've got a lot more discussion or questions.

1:18:04

You have a tool set that is managing this, right?

1:18:08

This is we have a third-party software piece of the case.

1:18:12

Yeah, it's the the same software that we use for our service desk, does our asset inventory.

1:18:19

Um, and that's that's where we we keep it.

1:18:23

Um yeah, so we have you know, every laptop, every computer, all 300 plus cameras around the city and buildings and everywhere else.

1:18:35

Um we are working on iPhones and iPads right now, and um, and then you know, every printer.

1:18:44

Um when I click on if we go into an asset, um, because just about everyone has two monitors at their station, right?

1:18:53

We can see the serial number of the docking station that that assets plugged into, plus the serial number of the monitors that are plugged into that dock.

1:19:01

So um, and so then actually when we put the cost in for a laptop, we actually figure in the cost of a docking station too, even though we don't necessarily have to buy a dock every time, but we just what we because we use that for knowing how many laptops or workstations we have to replace in the upcoming years and the cost of what it's gonna do.

1:19:27

We're budgeted for so that if uh if this next version of the HP Z book doesn't work with uh the current docking station because the doc can't supply enough power or whatever it is, um, or we need an an extra graphics card for a third monitor in that dock or whatever, we can uh we we have that budgeted for.

1:19:53

I was just gonna ask um why you weren't tracking those assets in the same way, but you bundle it in.

1:20:00

Do you what about for insurance purposes?

1:20:02

Do you like for example if you had a fire and you have a way to track all the monitors and and everything else that are those tracked separately?

1:20:12

Those are well, they're in our they're attached to that asset.

1:20:16

Right.

1:20:16

So we would we would have it.

1:20:18

You do track them.

1:20:19

You just don't tag them.

1:20:21

Yeah, we don't asset tag them, and we don't have like a specific, I don't I can't go in and click on monitors and see every monitor.

1:20:29

I click on the asset, and then I can see the monitors.

1:20:31

So yeah, so let's just say um we had a fire and it wiped out all the computers in the clerk's office.

1:20:39

We'd be able to go in our asset management system and see every asset that was in there, including their laptops, their diverse stations, their monitors, their MF um their MFPs or MFDs, whatever you want to call them.

1:20:56

So do you track all the accessories?

1:20:57

So I would you kind of classify them as accessories then too, the machine in a way.

1:21:02

So um I think I think it might even pick up the keyboard and mouse.

1:21:08

Yeah, okay.

1:21:09

I was just curious how you how you manage those.

1:21:12

Yeah.

1:21:12

The the ones that were concerned, docking station monitors are what we're most concerned with.

1:21:18

Um because docking stations in particular, um, because there's a uh you know, a cost to them if if we're replacing a computer and it needs a dock and we didn't factor in the dock, well that's four or five hundred dollars.

1:21:34

We we we didn't budget for um yeah, I think I think laptops are like over three hundred dollars more this year than they were last year.

1:21:45

Yeah, same model.

1:21:46

Yeah, maybe even four.

1:21:48

Yeah, I've seen three thousand, five thousand, five thousand, seven thousand.

1:21:52

Yeah, old school laptops now.

1:21:55

So there's that uh chip costs, yeah.

1:21:58

That's great.

1:21:59

The memory and storage process.

1:22:00

Yeah.

1:22:01

And monitors, I mean, you know, monitors, they might last 30 years.

1:22:06

They might last two, you know.

1:22:08

For the most part, they're they're stable, and they'll just last forever.

1:22:14

Well, yeah, I was gonna say probably a good seven to ten years.

1:22:18

They'll last longer than the PC.

1:22:20

Yeah, it's I mean that's easily.

1:22:22

Yep, okay.

1:22:23

Network equipment and stuff in this uh well, I'll have to go see if we have it in our asset man.

1:22:30

So we have a we have a different system for all of our switches and firewalls.

1:22:34

It's our network monitor, and that has our inventory.

1:22:38

And so that network mark monitor not only has an inventory of everything, but you know, it shows the relationship where the switches are connected.

1:22:47

We monitor, you know, the um what's the bandwidth monitoring flow um Vita?

1:22:54

No, it's the uh speed of there's a protocol with Cisco switches where you can see how much bandwidth is being used.

1:23:02

NetFlow, I think is what it's called.

1:23:05

Something like that.

1:23:06

So it does all that stuff, and then but it also backs up the configs of all our switches every night, too.

1:23:12

So nice because if you lose one, it's a pretty quick restore, which we just uh we're having a small issue with we have a small firewall that connects the police department to badger net, and we're having uh issue with it, and that was something that we've been meaning to replace, and so we had the replacement firewall sitting in a box, so we we were able to log in to it and get the get the config off, but the config wasn't backed off initially.

1:23:48

So we got the config off of it, had to do some tweaking because it's a different model, you know, went from a 50f to a 70f 4048.

1:23:58

But that sort of thing there, I mean, if we if we would have lost that badger net firewall without any kind of config.

1:24:04

Oh I mean, it would yeah, it would just have been a pain in the butt because there's a huge ACL on there.

1:24:13

Because if you're not if you're not on that list, you're not going to the state, you know what I mean?

1:24:18

So is this a new policy per se?

1:24:22

Or is it this one here?

1:24:23

Yeah, yeah.

1:24:23

Yeah, okay.

1:24:25

So if you look at uh CIS controls, uh number one policy, asset management.

1:24:31

And that is all like you know from a control standpoint, how how do you protect something you don't know you have?

1:24:41

Right.

1:24:46

Or is it just you've just been doing it for your software all the time?

1:24:50

We've just been doing it all this time.

1:24:51

Gotcha.

1:24:52

Yeah, yeah.

1:25:00

And then um, and then it was a combination of the spreadsheet and this um asset management part because we had the the client that was reporting, and then um uh yeah, I don't know, a handful of years ago um is when we went formally full asset management inside this uh software because tax would get done report replacing a computer and they wouldn't update the spreadsheet.

1:25:27

So uh do we have a mean number uh you know per uh C or not not seat, but you know, for each employee, do we have a mean number of what that looks like IT wise per year, what that cost is.

1:25:45

Oh what do you mean by like so you know we've got 500 and some employees and the mean number, it doesn't matter what their position within the city is, but the mean number to support them with our IT.

1:26:01

No, I mean we know what their devices cost, we know what their software licensing costs, but I mean I think about like Muni Court.

1:26:14

That's that's one department.

1:26:16

Now they're small, yeah, but that's one department that doesn't call us very often.

1:26:20

Oh, really?

1:26:21

Yeah.

1:26:23

And you know, they they're basically using um you know, Microsoft Office and then their municipal court software system.

1:26:31

And if there's ever a problem with that with that system, they call their vendor directly.

1:26:37

Um but yeah, you know, some some departments uh use this more than others, and some users use us more than others.

1:26:52

But we don't do like internal chargebacks, so I mean we can see um uh tickets open and closed and what was done and stuff like that.

1:27:02

Yeah, but um do you do uh like uh copier is it are the copiers you gotta log into it and make your copies so they know how to how to uh you know plan for resource and and newer copiers as time comes along, you know.

1:27:20

Yep, we have a uh we have we we track those devices too.

1:27:24

We have a life cycle for them.

1:27:26

Um we do use managed print services, um, and so they manage those devices.

1:27:32

Now we used to re uh we basically have the big ones, they're on a 10-year replacement cycle.

1:27:40

That's because that's where finance decided to depreciate them.

1:27:44

Um our managed print services, they'll tell you like until uh the repair is 50% more of the value of that, then we're not then we won't ask you to replace it.

1:27:57

That's um that's and that's it's within our contract.

1:28:00

So um boy, we've recently we've replaced some printers at 13, 14 years old.

1:28:08

That's great.

1:28:08

And they're finally just like and the managed print service provider didn't ask us to replace it.

1:28:16

We just got sick of fixing it.

1:28:19

And it's like, well, look how old it is.

1:28:21

Let's replace it.

1:28:23

So it's funny.

1:28:30

So the one the one question I had, just because of how this reads to me.

1:28:36

Um with regards to disposal, we don't we don't eliminate those out of uh inventory, we just mark them as disposed.

1:28:49

Yes.

1:28:50

So there's a record of this once upon a time was an asset and now it's gone.

1:28:56

Yeah.

1:28:57

So that the very last bullet points E3 sub I for uncontrolled disposal, it says the enterprise assets must also be removed from the inventory.

1:29:11

When I read that, I I that reads to me as if we're taking it out of the inventory list altogether, as opposed to marking it as disposed.

1:29:25

Yeah, that should be uh yeah, that should be reworded.

1:29:28

That that just it read funny to me, so I wanted to ask about that because I I would assume we would be keeping track of, you know, and I guess I don't know, you know, if there's a records retention thought behind any of this as far as you know, I could see I could see a persnickety constituent out there doing like some kind of open records request for like all of our IT expenditures for the last X number of years.

1:30:00

And I would think that this would be something that would you know be discoverable potentially under some kind of not that I'm giving anybody an idea out there, but I'm saying probably uh state guidelines on this type of record.

1:30:14

Yeah, and if I recall it's it it's probably it's probably anywhere from it's either three, five or seven years.

1:30:22

Yeah, I was thinking of five or seven.

1:30:24

So whatever the length, I think sometimes it's also the length of what your uh your um replacement policy is plus a year.

1:30:33

I mean they do have lots of different things, just depends on the record.

1:30:35

Yeah, I suppose you guys do it then.

1:30:37

And then the other thing I was gonna suggest uh what Dan was talking about is maybe if it is lost or stolen, it's marked that way.

1:30:44

You have another instead of disposed, it would be marked that way, and you get that record that way to track it and and you know, just kind of change the wording around a little bit.

1:31:05

All right.

1:31:07

Let's make the note on the policy as we speak.

1:31:10

Just out of curiosity, do you um encrypt your laptops?

1:31:14

Yeah.

1:31:15

Okay, so if they're taken and I mean in theory, they it without knowing anything else, they're they're not really usable.

1:31:24

Right.

1:31:25

That's good though.

1:31:26

Yeah.

1:31:26

That's a good symbol for NSIC level.

1:31:29

Unless you take them.

1:31:31

Well, yeah.

1:31:32

It's a pain in the butt if you have.

1:31:35

It takes a while.

1:31:36

Yeah.

1:31:37

It's it's a pain in the butt if uh when if you are replacing hardware or even updating the BIOS.

1:31:45

Um put in your big bit locker record.

1:31:48

Yeah, bit locker.

1:31:49

Yeah, your 48 digit key.

1:31:50

What is it?

1:31:51

48 characters.

1:31:53

48 characters.

1:31:55

That's a long password.

1:31:56

And you can't copy and paste it, so you gotta type and then we type in that.

1:32:01

I think I'll BIOS change too because our top one of our taxes offside was doing it, and I had to put that key in about eight times and finally.

1:32:09

Yeah, and then it finally works.

1:32:10

I just yeah, it was.

1:32:11

Or you go into BitLocker and BitLocker shows like three or four different ones.

1:32:15

You're like, shoot, why?

1:32:18

Exactly.

1:32:19

Surprise.

1:32:20

Yeah.

1:32:23

All right.

1:32:23

Uh so I made note um that uh that instead of remo we're gonna we're gonna create a we'll create a state like this here, like an asset state.

1:32:39

Um we'll probably just make it lost lost or stolen, or maybe we'd make two more.

1:32:46

And then that way um if that happens, it won't be removed from inventory, but we will uh mark it as lost or stolen in its in its state.

1:32:59

I would also suggest that you do look at the um record retention laws and just add a statement about that, you know, we'll maybe we'll re keep these assets this amount of time.

1:33:10

Yeah, so if there was an open records and someone did that, that would be all you'd be required to pull that.

1:33:17

Yeah.

1:33:18

I mean, it's been three three years now since we went full on and just started throwing everything inside there.

1:33:27

So it's fine for now, but there's gonna be a point where we're gonna want to purge that database.

1:33:33

Right.

1:33:33

Yeah.

1:33:38

All right.

1:33:39

Very good.

1:33:40

I think it looks good, Chris.

1:33:42

I mean, I read through it and it you know made sense on the face of it.

1:33:46

I was just I mean, I'm I I knew we were doing this, and I assume we were doing this.

1:33:52

I was just curious, like how we were doing it in terms of tool set or you know, where we were storing this, because I know I I've I've worked in enough companies to know that this kind of thing is done sometimes on a very ad hoc, you know, spreadsheets, homegrown databases, tools.

1:34:12

Well, trust me, and it's I've seen for the I've asked for the PC replacement schedule and been given it, and like, oh wait, that's the wrong version.

1:34:23

So it's nice, like you know, uh one of the things like last year uh was the first year all the COVID laptops need to be replaced.

1:34:35

And if we weren't using uh our asset management system for the replacement schedule, we would have we would have just gone through the budget process and then and and then all of a sudden been like, oh crap, you know, we have like 30, 40 extra laptops that need to be replaced right now.

1:34:54

Right.

1:34:56

Was that ARPA money that was used back then for that?

1:35:00

Is that was that ARPA money that was used back then for that uh no that's that way ARPA was do it was different.

1:35:04

Okay.

1:35:05

There was COVID reimbursement money.

1:35:07

Yeah we probably could have ourselves back for Marpa money but we didn't oh yeah we used that in other ways yeah I just figured they must have had a different tracking way of doing things because they were just throwing it out like candy.

1:35:22

Does your does your tool set have some uh AI built into it where it alerts you uh when things are getting close to end of life or do you have to go through and query that um we have reports that uh show the next five year replacement schedule okay so um so we see some tools exactly how many and then that helps you manage that so I would think that would be a big bonus to having a well yeah having uh a tool set involved in that yeah the um you know the one thing that it doesn't do well is the software inventory because it inventories every piece of every soft Microsoft uh application that's installed in Windows and you can't get rid of it because it keeps bringing it back and then like some other shortfalls of it that we're just dealing with are like you know everyone has you know a version of Adobe they're all set to automatically update but there are you know it doesn't matter if it's Adobe Acrobat um every version is its own uh piece of software sure and so like we were we try and do license tracking in there well it says well you know we own a hundred uh copies of Adobe but there's all these you know this one isn't licensed because you're only licensed for dot three not dot two yeah but anyways any other thoughts on this I think any other you good with the feedback you've gotten yeah okay so we'll we're not gonna take action on this since it's the first time we've seen it Chris is gonna bring it back on our next meeting April next month say pass April by the IT on on this date so at the bottom I don't know what does that mean we have to vote on that no no that's just the placeholder okay the it's always the pass date uh by ITV date and then uh the pass by council date and then and then I have uh a spot on the employee internet site so when you go to IT policies it shows when it was approved by council and the last annual review of ITV.

1:37:48

So I I looked at that policy I'm like I don't remember passing this and then I I looked at I I went down and looked at that exact thing and I'm like well there's a date on it maybe we did I didn't go back through the agendas to make sure one way or another but I was con I was uh wondering about that so 2025 good question right yeah okay uh that takes us to item six communications and referrals um Chris you want to mention the board member celebration so everyone should have got an invite from Rebecca Peterson um next next uh ITB meeting would have been March 4th but there's uh celebration dinner for people that have served on on boards and that's one of the things that we're trying to do is recognize um people like you that take time out of their schedules to serve as um you know citizen board members and so there's a dinner at Tuscan hall on March 4th and uh so if you are able to make it that'd be great I thought it's perfect for us because we already had something planned.

1:38:59

Yeah you were planning to be here and you can um and you get to bring you know a plus one so um I know uh Paul's gonna be there and and his wife Lori so Paul's wife Laurie was just appointed uh as our municipal judge through April 30th um because uh judge wimmer passed away unexpectedly um a couple weeks back that's gonna hold what's the hour I 6 p.m 6 p.m okay I think if I threw it's like drinks and then six oh yeah six or seven is the uh let me pull that up real quick yeah 5 30 is drinks and six or seven is uh dinner meal no Chris thanks for thanks for remembering and putting that on the agenda because I remember seeing that email and it yeah totally slipped my mind but I do remember it being on the same night as our as our meeting so certainly if you can make it I'm signed up so and and if you haven't RSVP'd to Rebecca yeah please do so I don't think I have so I should probably do that if I Mr Manning

1:40:20

Manny Yeah go February 18th to uh RSVP okay thank you yeah there we go five thirty doors open cash bar and dinner and then program all right Wednesday March 4th yeah all right that night off work all right okay um but any other communications Chris from IT that's it that's it anything from the board no okay um item seven on our agenda is adjournment is there any objection to adjourning hearing and seeing no objection we're adjourned by unanimous consent at 742 all right thanks everybody thank you

Discussion Breakdown — Share of Meeting
Technology and Innovation█████████████████████████████████████████████93%
Procedural██5%
Fiscal Sustainability2%
Summary of Proceedings

City of Waukesha Information Technology Board Meeting Summary - February 4, 2026

The Information Technology Board met on Wednesday, February 4, 2026, at 6:00 PM in the City Hall Training Room. The board approved a contract for a new permitting system, revised the AI Acceptable Use Policy, and added mobile device management provisions to the Acceptable Use Policy. They also reviewed an Enterprise Asset Management Policy without taking action. The meeting was adjourned at 7:42 PM.

Discussion Items

  • Item 5A: Review and approve contract with MaintStar for permitting, code enforcement, and inspection system – Chris (IT Director) presented the need to replace the current Track It system (implemented 2014, sold multiple times, support ending). An RFP was conducted; MaintStar was selected. Maria Pandazi (Deputy Community Development Director) and Mark Probuki (Business Solutions Architect) detailed the system's benefits: improved customer portal, flexible workflows, better scheduling, and integration with existing systems. The contract is year-to-year with a 90-day notice, annual costs same for years 1-2 then 3% increases from year 3 onward. The city's finance director, city attorney, and city administrator signed off. The board discussed the system's features and cost. Unanimously approved.
  • Item 5B: Annual Review and Discussion of IT Policies (No action needed) – Chris reviewed four policies: Change Management, Email, Malware Defense, and Security Awareness. No changes were recommended. The board acknowledged the review.
  • Item 5C: Review and approve edits to the AI Acceptable Use Policy – Chris proposed removing the requirement (Item C under Rules of Use) that users must mark AI-generated content with a disclaimer (e.g., "draft prepared using AI"). Reason: impractical to enforce and other safeguards exist. The board discussed the distinction between AI-generated and augmented content. Unanimously approved.
  • Item 5D: Review and approve additions to the Acceptable Use Policy – Chris introduced mobile device management (MDM) provisions: all city-owned iPhones, iPads, and other mobile devices must be enrolled in Microsoft Intune; users cannot remove, disable, or bypass MDM profiles; all user accounts must use city-issued email addresses. With director approval, users may use city devices for limited personal use. The board discussed device types (fully managed vs. corporately owned personally enabled), inventory (hundreds of devices), and policies. Unanimously approved.
  • Item 5E: Review and discuss Enterprise Asset Management Policy – Chris presented a new policy covering asset lifecycle from procurement to disposal. The board suggested clarifying language on disposal states (e.g., "lost or stolen" vs. "disposed") and incorporating record retention requirements. No action taken; policy will be revised and brought back in April.

Key Outcomes

  • Motion to approve the MaintStar contract passed unanimously (5-0).
  • Motion to approve edits to the AI Acceptable Use Policy passed unanimously (5-0).
  • Motion to approve additions to the Acceptable Use Policy passed unanimously (5-0).
  • The Enterprise Asset Management Policy will be revised and presented for approval at the next meeting (April 2026).
  • The board was reminded of the Board Member Celebration Dinner on March 4, 2026, at Tuscan Hall (RSVP by February 18).

Meeting Transcript

Item four is approval of minutes. As I mentioned before our meeting, um our January minutes did not uh get attached, so we'll hold those over till our next meeting to get approved. Um that takes us to item five, which is our business items. We have a few uh items to talk about tonight. And 5A is to review and approve a contract with Main Star for a new permitting code enforcement and inspection system. Chris, you want to kick this off? Yeah, sure. Um our current uh building permit code enforcement um sys system went in in 2014, and um I a couple years ago they gave us notice that they were gonna end support for the on-premise uh version, and so we're gonna have to move out to the cloud, and so we had um we had had some issues with that vendor. Uh the product had been sold four times at least four times uh since we've owned it. Uh the first sale coming about 30 days after we inked the contract. So um it's been it's some of the support's been problematic, and um and so we said, well, if they're gonna force us to go to the cloud, we're gonna take this as an opportunity to um look around and see if there's a a better product out there because essentially the quote that they had given us, there was no real break. We're gonna have to pay migration costs and and that sort of thing. So uh during the 2025 CIP budget process, this project was approved. And so last year we went out to RFP and um reviewed the RFP. We we scored them. So we have Maria Pandazi from uh she's our deputy community development director, and then uh I have Mark Probuki, he's my uh business solutions architect. Uh they've been uh heavily involved with this project, but we went out to RFP. Um there was a group from IT community development and engineering. Uh we scored the RFPs, we ended up bringing in a handful uh for vendor demonstrations. Uh we did went through the demos and uh Main Star is the one that bubbled up to the top. And um so this is this is uh what we have before you. It is a SAS solution. So I did it, I did attach the IT uh uh technical questionnaire uh answers that we got back, and so with that uh we'll open up the floor to questions. So operationally, uh Maria can hand uh handle those questions and Mark is super familiar with uh the current product. In fact, he's uh he's had to do the troubleshooting for their support um on some stuff, and then he's also pretty f uh really familiar. He kind of led the the demo part of the RFP um process. So Maria, is there anything you want to add before we pepper you with questions as far as I know this touches your department probably more than any other sound? It does, it does. We um we probably have at least six thousand either permits, projects, or code cases that go through this software every every year. Um and that number is growing. Um I think Chris did a good job of explaining our challenges and the the cost of keeping the software moving to the cloud didn't seem to make a lot of sense without assessing better software for us. One of the challenges I think in addition to the um the customer support or lack of support or challenge of support, was their customer portal also, so for when contractors are logging in or the general public wants to report something their interface, I think that's the right word. Um not IT, but they're you know, what what the public sees is very cumbersome and it's not very customizable. Um one thing that I really wanted to see out of new software was a really nice customer facing um piece, and and that's I think what we're gonna get with Main Star. So I was I was on council when we implemented track it. So I remember that. And I I do remember that their customer portal was one of the things that was supposedly a selling point of that product. So it's disappointing to hear that that never really well that portal from 2014 is the same portal we have now in 2026. I'm sure it's good. Yeah, and I think that's the issue. I mean, it knows its job, yeah, but it's very difficult to navigate, and it's not, you know, maybe it was okay in 2002. Yeah. Well, Maria was just uh commenting, she was at a conference a couple years ago for it, and they they talked about one of the jokes that during the keynote was that their uh customer facing portal is what yeah, somebody stood up and said, Oh, it's state of the art for 1972. So they I mean I think they acknowledged that it was an issue, or they heard it was an issue, but nothing really ever changed with it. So I'm really looking forward to that part of Main Star actually. Questions from the board just sounds to me like they rang the money out of it, you know, uh early on 30 days after we saw it and then proceeded to sell it and it for bagged data. So yeah. So what other um features are you looking forward to in the software compared to what you currently have? Um considering how much I mean it appears to be quite a bit more expensive. Yeah, annually because of the cloud costs.

SUMMARIZED BY OPENPUBLICA AI
TRANSCRIPT VIA PUBLIC VIDEO
openpublica.com