All right, good morning, everyone.

Um, today is February 27th, 2026, and I call the Lake County Technology Committee to order at 8:30 a.m.

In addition to being able to attend in person, remote attendance has been made available to the public via Zoom at the link on the agenda.

This meeting is being recorded through Zoom.

Can you please join me in the Pledge of Allegiance?

I pledge allegiance to the flag of the United States of America and to the Republic for which it stands.

One nation under God, indivisible liberty and justice for all.

Can I get a roll call, please?

Yes.

Member Altenberg.

Here.

Vice Chair Cassman.

Here.

Chair Clark.

Here.

Uh member Dan Forth is absent.

Member Frank.

Here.

Member Peterson.

Member Roberts.

Great.

Is there any addenda to the agenda?

No addenda to the agenda.

Are there any public comments?

No public comments.

Chair's remarks.

I just want to say a number of us went to the NACO conference and really learned a lot about a lot of technology things between AI, data centers, and a lot of information we can really bring back here.

Um right.

Um, we don't have any unfinished business.

Our new business is our consent agenda, which is item 8.1.

Can I get a motion in a second, please?

Motion by Frank, second by Altenburg.

All in favor.

Aye.

Any opposed?

Motion carries.

Um to the regular agenda.

Item 8.2 is a joint resolution accepting a funding agreement for the Supreme Court of Illinois Court Technology Moderniz and approving an emergency appropriation and the amount of $50,000.

Can I have a motion in a second, please?

Motion by Robert, second by Kasmin.

Good morning.

Hi, good morning.

Lisa Wolf, Director of Finance for the uh 19th Circuit Court.

I'm here today to um bring to you our um technology modernization grant.

Uh this year it's $50,000.

It looks quite a bit different than last year, which was almost $1.3 million.

Um however, we utilize we looked to see what how we could utilize these funds and um tried to identify things that may not have gotten replaced this year or things that popped up since our budget that really kind of needed to be replaced.

One of those items is our kids' corner paging system.

Right now, that paging system is not designed when it was excuse me, initially implemented, it was not designed to work in the court tower.

Oh as you can imagine, if we need to reach a parent, we need to we need to update that.

Um, we are looking to implement surface tablets for our pretrial service.

Um, if you have walked by pretrial, you may have noticed um they have a uh stand with clipboards and paper.

So they're collecting information on with pencil and paper right now.

This will automate that, streamline it, eliminate some duplicate entries.

You know, also when you're taking something from a piece of paper that somebody has written and putting it into a system, there's a possibility of errors.

Again, streamlining.

Um, we are also looking at replacing using these fundings for replacing computers at the juvenile detention facility.

Um, this for the specifically for the education program, those computers are reaching their end of their life, and this would be an excellent opportunity to update those.

Um, as well as also some of the um language interpreting devices that we have for the courtrooms.

Um, so if we have say an interpreter and we have say two or three juror members that need interpreting services, they have the earpieces so that way everybody is crystal clear and you're hearing the same thing.

So I'd be happy to answer any questions that you have.

Well, it's really interesting.

And it sounds like I mean this is gonna be really add some efficiency and some really good updating.

Correct.

Yeah, the greatest need.

There was a lot of debates as to where can we use this money to get the greatest good?

I bet because it is it is it's great to see this grant.

It is a lot different.

I know last year was very exciting, so I can tell this is very strategic using it.

So any questions?

Vice Chair.

Yeah, I just want to ask why why the difference in grant funding, or is it just that you come it was for specific projects and you completed those projects?

Um that is at the AOIC level.

Um, I think this is gonna be indicative of grant funding going forward.

We are not that that 1.3 million was an outlier that they knew they had some funding and they were going to assist us with some items, but going forward, the the belt is getting tightened.

I look like a lot of programs.

Everybody's yeah, exactly.

Exactly.

I guess it is, I'm sure this will be something we will hear again.

Yep.

All right.

Any other questions?

All right, all in favor?

Aye.

Any opposed?

Motion carries.

Thank you.

Thank you.

Item 8.3 is a joint resolution resolution authorizing a contract renewal of Oracle Boss application support services with TD Sinex, a DLT solution of Herndon, Virginia, and the amount of 310,032.

Can I get a motion in a second, please?

Motion by Altonberg, second by Roberts.

Good morning.

Good morning.

Chris Blanding, C A O.

Nice to see you all.

Good morning, Mike Maslan, applications manager.

Um, what we have before you is a uh a renewal of a contract, which basically provides support for our current ERP system boss.

Uh, we've been using this company for four years or so.

They are experts in the Oracle environment.

It's uh been we made that decision at that point.

It's very difficult to find these experts and keep them on board if you're trying to hire these folks.

Um so we went this route.

This is a renewal.

What they do is provide functional support for the system when we do our annual or quarterly patches, they provide support there.

Um things like support for the big beautiful bill or no tax on overtime, things like that, as that affects our system.

They help do those uh configurations.

And they will also be doing work for our new ERP system, some of the data conversion and then support of boss as we're ready to decommission that system.

Mike, is there anything you want to add to that?

No, I think that you had some that up well.

Really, what this group of people do is the the configuration, the knobs and levers um that keep the system running.

So when request comes in, uh request comes in for something that may need to be changed or updated.

They're the group that does it.

If there's a problem, something's broken, something not working, they're the group that helps fix it as well.

Great.

Any questions?

And so this this hopefully is going to go away once we've once we've been migrated once we have our new ERP system.

Is that right?

Because this is supporting our legacy system.

Yes, absolutely.

But they are helping with the workday config.

So that's why it's going into the new year through March, I believe, because there's going to be some support needed there.

Yeah.

Absolutely.

The intent is for this to go away.

And I think it'll be good.

Um, you know, we've talked about we're gonna look at all the savings we're gonna have once we've converted over.

So we will look forward to not having um this contract, I think.

So it sounds like so, yeah, there'll be consulting services just to like keep it going until we can be done with it.

And do you think it'll be much more past March?

I mean, I don't know how long we have to run two systems.

I don't know if that's been decided yet once we've converted.

Or is it is that to be determined?

It has not been decided yet.

There's factors uh regarding audit and what kind of access we are basically we are taking data out and where it will be available and historically uh accessible, but what they'll need and for how long into the new year has not yet been determined.

IT always wants to decommon old system as fast as we can, but we obviously have to take into account the the needs of the business and the organization for what they need.

Well, I'm looking for I feel like the longtime storage of some of this information that's on this legacy system, where we're gonna put it to be accessible, what it how it's much it's gonna cost, like how to do this efficiently, it's just a big question.

So I'm looking forward to seeing how this develops.

All right, any other questions?

All right, all in favor?

Aye.

Any opposed?

All right, motion carries.

Item 8.4 is a joint resolution authorizing a contract with Logic Hallis of Downers Grove, Illinois, and the amount of 306,654 dollars for the network hardware replacement project.

Can I get a uh motion, please?

Motion by Kasmin, second by Altonberg.

Uh good morning, everyone.

Eric Carlson, CTO for Legon.

Uh, this one is um several years ago we did our network refresh, which the network is everything that the backbone, the infrastructure.

And we replaced switches.

They sit in closets, they sit in data centers, all your cables plug into that.

That's how you access everything.

Um, there were some switches at that time that still had life left in them.

So we chose to not replace those at this time at that time.

Those are now end of life.

So what this is is to replace those devices, which are end of life, um X number of switches, basically hardware and then implement, and then they will be refreshed and up to security patching standards, et cetera.

I'll glad to have Eric talk more in depth on the technical side there if you have questions.

Otherwise, uh that's it.

I am glad I know I remember before how it was.

I'm glad that you're looking to make sure that just because it's supposed to be in a schedule that these could last longer, but I understand that sometimes this is the time to replace them.

And it's like a hardware issue.

Is there any like specific questions?

All right.

All in favor?

Aye.

Any opposed?

Motion carries.

Item 8.5 is a joint committee, is joint committee action approving a contract modification for a contract with SHI of Somerset, New Jersey, and the amount of 38,066.

Can I get a motion a second?

Motion by Altonberg, second by Kasbin.

This is a contract modification.

We have a piece of software that we use throughout the organization to patch PCs, laptops, and servers.

So it's a system that allows you across the board to push updates when there's a threat or whatever regular patching, it helps automate that process.

This is an add-on to that contract, which will mitigate a security risk we have.

Um not a high critical risk, but something that's on our list to mitigate as well.

It'll it will allow us an operational improvement.

And I'll have Eric speak a little bit about that, please.

Sure.

So the uh the tool itself, uh I guess the biggest risk we have is there's remote software that's installed on everybody's machine.

It allows people to remote in, usually for support reasons, or to just work on a machine that's not you know near you.

Um attackers use this as a way to once they get in an organization, they can now use that tool to move around.

Um it's it's generally recommended to disable that feature.

But if we disable that, then we can't do things like support remote users from help desks.

So this tool um is a secure way to do that.

It's uh it's a like a screen sharing type of remote access tool.

And since we oh, sorry, go ahead.

It provides a more secure way to provide remote support to computers and eliminates that risk that Eric just talked about, basically.

And it then will there are some groups around that are using a different piece and and ours to access the computers to do that remote support.

This will kind of unify us on one tool too, which is a good thing.

Okay, so currently you have a way you're doing this.

It's just that this may be like so.

The reason it's a contract modification is did you like look around and think, okay, this would be better if instead of the way we're doing it right now, we doing this tool might be better for just everybody, and that's why you want to add it into the contract.

Is that it?

Or exactly that's exactly it.

So we have a couple different tools, right?

Some IT departments are using this, we're using some built-in Microsoft tools.

Um, but this allows us to be on one platform.

So managing an endpoint, whether we're patching it or remoting into it, it's all coming through the same platform, which is a great thing as we try to consolidate tools, tool sprawl, those create training problems, risk.

So we get into one, uh, we can kind of control things better.

And will this allow us to have not other tools?

So we don't have to like use those.

Yeah, we worked with the the groups around the county, and I believe they evaluated several things, and everybody thought this was a good solution.

So, yep, they're gonna move to this one.

We're gonna move to it, and it's part of our built-in tool, like I talked about that allows us to do the security patching.

So it's a consolidation.

So, yeah, it is a great thing.

So maybe it'll save us money on not using the other tools and being make it standardized more and our giant list of things that are being used, we could take off some of the things.

Yes.

All right, that thing's good.

Any questions?

All right, all in favor?

Aye.

Any opposed?

All right, motion carries.

Item 8.6 is a joint resolution approving an acceptable use policy.

I'll frame it.

Do I need to get oh yeah?

Can I get a motion in a second, please?

Motion by Frank, second by Roberts.

I'll frame it up.

Uh last time I talked about how we are planning to bring some policies forward this year, targeting two per quarter.

Um they're for the most part foundational security type policies that outline how we're gonna do things as standards across the county, how we're gonna secure things.

So, with the exception of those that will be coming, um, this one is really a user-based policy, right?

It's the acceptable use policy.

We currently have one as part of the onboarding handbook.

Um, it has been revised in 10 years, let's say.

So, what we've done is modernize the policy, put in some new threats, uh, really focus on how the users should report things, et cetera, what they shouldn't do, et cetera.

Um before we talk about that, um, I wanted to highlight the collaborative process we did to get here, which is we're really proud of.

Um we worked, Eric worked with the the IT leaders across the county and our IT liaisons, and really um a lot of pre-work did before it went into even the county policy process where everybody comments and we do that.

Um we worked, Eric worked with the the IT leaders across the county and our IT liaisons, and really um a lot of pre-work did before it went into even the county policy process where everybody comments and we do that um multiple sessions, going through the areas of the policy, discussing it, collaborating, taking their input and putting it into the policy, really looking at it as these are kind of standards that we can all agree to, and we all have different needs too, but let's put those in there or reference it.

So um throughout that process, working with all those folks, it was really great.

Um, and I think it'll lay the groundwork for the future policies.

They're already working on the next two that are teed up.

Um so we really appreciate all of their collaboration and work.

I appreciate Eric's work, uh uh driving the policy work.

So we got all the details.

Everybody said, yep, these are good to go.

Then we put it in the county policy process where we post it, and all the policy coordinators have 10 days to put comments.

Then we got some great comments from different point of view, not technical point of view where um, hey, you're you define this differently here or use this word, great input.

So we tweak some of that, always having a different point of view.

Uh so we took all those comments and integrated them and then went back to that group and kind of explained, yep, we took all your input, thank you, and we've made our policy better.

So our intention is to have this policy and the next, the one that follows this um approved today.

We really weren't gonna get this is like a 14-page policy or something.

It's acceptable use.

It's really telling people what they should do, what they shouldn't do, what it references our cyber policy, our AI policy, et cetera.

And they'll have uh this when they onboard, they will be presented with this policy and that they have Reddit and will follow it.

And it seemed to add, Eric.

That was a pretty good sum up.

Um try.

Yeah, I think we what we always call the the user acceptance acceptable use policy is it's the at the end of the day, the user is the human firewall to our network.

It's usually where the problems come.

Somebody clicks on something or does something.

And so you have to have clear expectations for your users, and they have to be modernized.

Things have changed in the last 10 years.

And so we've really worked to make sure that we're following the latest things, and that we're also referencing the new things we've done, like except uh the training Chris mentioned, and that we have an AI policy, and you you need to follow those because they they protect us.

So can you speak to the state templates basically?

Sure.

So when we were developing these policies, I don't know if you've ever tried to write policy.

It can be written everyone has their own point of view, and you you download templates, you bring consultants in, they bring their framework.

So we follow NIST framework.

That's what the county has has been using for years for our security program.

And as we started trying to figure out what's the best approach to uh how do we start with policies because there's a lot to them.

Um we worked with a consultant and we came to the fact that the state of Illinois, they publish all their security policies.

They follow NIST, they follow Illinois state law, obviously.

And we use those policies, so they're freely downloadable as basically our foundation.

So we start with that as the uh baseline that gets us kind of going, and then we incorporated everything that was in the existing policy, and then working with everybody to make sure it follows what what the county is because we're different than the state.

Um, but it was a great way to get us off the ground running and following the right framework, the right governance, um, and speeding that process up because it is repeatable policies, should be pretty consistent across the board.

Thanks, Jared.

Well, I want to congratulate you on um I think you got a nice balance of not reinventing the wheel yet, um, tailoring it to the county and getting input from the actual users.

I really appreciate um the work and intentionality that went behind that.

Um really really appreciate it.

Is is this and I'm glad to see that we'll all for sure be rowing in the same direction, because I think that's critical with any type of policy like this.

Um and all every everyone who has access to the system will will be adhering to this policy or just across the board.

I mean, all the departments all the yeah, it's it's meant to apply to anyone that connects to the Lake County network.

So whether you're a vendor or a third-party person, they also agree to that policy.

What's acceptable to do on our network?

Great, thank you.

Member Frank.

Thank you, Chair.

Um, I think the process of you know getting feedback from a users and departments is is really important uh in the development of the policy.

Can you talk a little bit about how it's going to get socialized?

What is the education process so that it's not just a policy that sits on the books, but it's, you know, people are aware of it and and are thinking about compliance.

party person they also agree to that policy what's what's acceptable to do on our network great thank you member frank thank you chair um i think the process of you know getting feedback from a users and departments is is really important uh in the development of the policy can you talk a little bit about how it's going to get socialized what is the education process so that it's not just a policy that sits on the books but it's you know people are aware of it and and are thinking about compliance yeah that's a great great point um we tend to focus on AI awareness and cybersecurity awareness um the in general awareness for this will be part of let's say we do our lunch and learns our training programs uh we are developing those so we will take that's a great suggestion to specifically focus on some of the newer things in here and refreshers we do it through our uh our IT newsletters and things like that but we will incorporate some of these new things I I appreciate that uh suggestion it it it is the challenge right it's how do you get people to read policies because they're that excited to do it so we always any new employee on boarding is going to get the policy and as we'll we'll work with the departments because they on board differently and they communicate to their departments in in many different ways and I think one of the future things we'll be bringing forward is a way to uh standardize our policies how we hold them and then how we can send them out to users have them sign off on them and make that an automated process because to date that doesn't exist.

Thank you.

Thank you.

Member reference I I love the idea of having somebody sign off because that really held them accountable that they read it and they're gonna follow it.

So I think that's a really good way to make sure the employees that not because you're getting onboarding for new employees you current employees need to follow this understand it.

Sign off on it.

Including us including us vice chair this is just an idea and feel free to use or not um but I know Jennifer was saying she can have um AI generate quiz questions pretty easily I'm just wondering when I do state trainings like online they have a question time so they'll you'll you'll read part of it and then you'll get some questions and you can't move forward unless you answer them correctly.

So if there are points that we definitely want to make sure that people know I'm I'm wondering if it would make sense to break it up a little bit and then have a little tutorial with questions for each section not not long not long questions but like just to make sure that they understand and and everybody's complying yeah I think these are great suggestions as we're brainstorming yeah I think now I think we should specifically as I'm hearing this yeah have an acceptable use policy overview or session and invite folks to it and and then use some of those so I think that's great.

Member Roberts well to your point we can't even get past Ninja going on to that next question.

Yeah so Ninja is interesting.

Yeah well I I do want to thank you both and everyone and everybody on this committee that you have this working group because you know this is the collaboration that we've been needing for a long time.

And so to get everybody to agree in the whole county with all the departments to these standards is so important.

And because you know I know even for our own insurance and our own protection like having these policies are like you know we have to and we and the other it and so it's you one of my questions is how do we hold people accountable like our in this use like what if somebody just does not follow this policy like is there anything in the policy that says you know you get a you have to get taught you know get spoken to by your manager it gets does it get escalated are there things you know or is it more of a you should just follow it that is a great question.

I often say well I don't know I almost want to defer to county mystery um it's policy enforcement in general um IT policies and certain things like cybersecurity awareness and we talk about that tend to be highlighted okay how many people have done it um what if they don't do it well let's you know cut off their network access or talk to them etc but I think that gets to policy in general how do you enforce a policy in general and what if they don't do it we are we are using the the carrot method I guess with like things like cybersecurity following up hey um reminder that you should do this and that gets us great success in adoption rate so um and we we heard at NACO some some talking about how they do cut people off the network but that presents other problems and challenges so um I'm not really answering the question overall policy but we would probably use the carrot method to say here's why we're trying to do this and individually reach out to folks who haven't done it.

We've already adopted some and um, you know, in just in general is you know, there's ways that doesn't have to be, but even having to have a discussion with someone, you know, like you're gonna have to talk to your manager.

I mean, having to go talk to someone and explain why you didn't follow the policy can be a pretty good incentive not to do that again.

And so um, because these are important policies for a reason, right?

This protects Lake County, it protects us all our residents from you know, potential bad actors.

And so, you know, as as kind of like member Frank said, too, we don't want this just to be a policy that's in a drawer somewhere.

So how do we make people engage with it and and understand it and then also have incentives to follow it?

And it's not just, I mean, acceptable use.

I'm hoping I guess I shouldn't hope.

People should follow this, and we're gonna make sure, but but but you know, and and we're doing the next one too, which is uh, you know, identification and authentic authentic authentication policy.

And there's gonna be more.

And so as we have more and more policies, I do think maybe we could just think holistically on how we educate people on them and the importance to them, how it affects them, and then have some type of follow-up um in case that they aren't followed, because we have these for an important reason.

Um I I hopefully maybe we can continue that part of the discussion.

But I am really happy.

I remember, yeah, talking about acceptable use policy.

I think one of the first days we had this committee.

So I'm I just can't thank you both enough and everybody who participating in this.

I think that this this framework you've developed with speaking with everybody has really changed the conversation.

I hear from people all over the county now that are like, oh, you know, we have you you listen, you know, everyone's listening, taking that input and creating something that works for everybody is um really uh been a game changer.

So I'm really happy to see this.

I'm happy to see more coming forward.

Um and uh thank you.

And as I said, these are important and uh yeah, I'm glad to do this today.

So acceptable use, um, and just to review everything is just how people use our technology, right?

Okay.

All right.

Are there any other questions?

All right.

Well, all in favor.

Aye, all right.

Any opposed?

Motion carries, which brings me to 8.7, a joint resolution approving an identification and authentic authentication policy.

So this one is, as I said, with the exception of the acceptable use, really you could call them IT security policies, this one and the others that are coming forward.

So really not a whole lot that is user or employee.

It's really IT.

So working collaboratively with the IT groups and saying, are these standards that we all feel make sense and we can all do and set for a minimum standard?

Some what might do uh more in-depth standards based on let's say HIPAA, et cetera.

But can we agree on these type of uh standards?

And that was where the collaboration was great with those folks because uh they know their offices, their departments.

And so we really didn't have we took some, we took all the input and it was collaborative to to generate the policy.

And then when it got to the policy coordinator, the the county process, there was really no questions because it's really kind of a a tech geared policy.

I think there was a couple um maybe grammar or some of those standardization questions, but we we integrated everything into that.

Anything you want to clarify or I would say the acceptable use policy is probably the most exciting policy we'll bring forward, right?

Because it's it affects all of us and we all use computers.

The f the rest of the policies coming forward are IT governance policies.

How do we do things?

We do all the things that are in these policies.

Um, like this policy is about making sure that users that are on our network, we know who they are and that they've authenticated at a minimum standard that we set.

And we those standards change over the years as as vulnerabilities come out, we increase things.

Um, but we want to make sure everyone's doing the same thing across all departments, across how people um get onto the network.

So you'll see this policy is gonna focus on identification.

There'll be policies in the future on access control, meaning what what can they access once they're on the network?

And then there'll be policies about how we handle data.

Is the data sensitive?

Do we label it as sensitive?

You know, so you're gonna see more of this in their governance policy, so they're not exciting.

Um and they really don't affect the end users directly.

They don't have to really sign off on them.

They're just making sure that we provide governance across how we do things as a foundational thing.

So uh it's really just bringing our maturity to that level now.

That is exciting, but very important.

And I forgot, can I get a motion in a second?

Motion by Altonberg, second by Kasmin.

And um, yeah, I mean, so could you just give an example?

I think I know what identification authentication policy is, but just an example of one.

Um so user IDs, right?

If somebody's is connecting to the network, we want to make sure that everybody that's connecting um has a unique user ID so we can identify that person and what who that is on our network.

Um and then those user IDs, but they may be privileged.

So if you have um you need to access sensitive data, or you need to get into the Oracle system, and you have rights, who those people are and follow those type of identification.

So separate accounts for those users.

So it really defines those things, who users are, what groups they should be in or should not be in.

And then on the other side is how do we know that when that person connected to the network that they're actually them?

So it's identification.

So the authentication is the other side of this.

So really making sure that when people authenticate, um, they follow what we how we do that.

You guys know we all use beyond identity, that's how we do it.

Yeah, that's another example, the multi-factor that we're gonna use multi-factor.

I heard at one of the NACO sessions when guy said the first thing, first takeaway is multi-factor.

If you're not doing it for everything, personal, and and we are, and that's where we I would say we lead the way because we we we did this uh a year or so ago.

Um uh MFA.

So another thing, hey, we're gonna use this as standard.

Does that work across the county, work with our partners?

So I think for us on this committee, I don't, you know, we don't necessarily have opinions on this, right?

Because you're the ones figuring it out.

But I think it's so important that you've had the discussions with everybody at the county, and now it's gonna be standard that we know everybody on the network is our file is following this policy.

And I think these policies will be, I mean, they're important for our network security and everything, but again, also for our business insurance.

I mean, things like that insurance to make sure we have these policies in place and that we know everybody on our network is follow-well, should be following them.

Um, and so I'm really looking forward to see them.

And I kind of think it's very exciting authentication stuff.

So I'm happy to see it.

I'd like to say again, then to that point, thank you to all the uh departments and offices that have taken their time to really work on these, and we really appreciate it because it is countywide policy and it has to work.

It you're only as strong as your weakest links.

So we really agree.

Exactly.

With us, and it's been a great process.

Yeah, exactly.

This will just make us all stronger.

All right, any questions?

All right, all in favor?

Aye.

Any opposed?

Motion carries.

Yay, two more uh policies adopted.

Uh all right, uh the item uh nine is director's report.

Um, I thought I would just give a brief update on the ERP uh project.

Um we did talk last time and so I just want to give some updates.

We did have a steering committee meeting yesterday just to update that group.

Um what we as a to refresh where we have been working on is use cases, so and alignment across the county.

Um, how how certain processes that we want to potentially change and make it more efficient or standardized or streamlined, et cetera, take advantage of the software that we're putting in work day.

What might those challenges be?

How can we uh address those up front and get alignment so that then when it gets down to the work streams where all the the hard work does and how to make it happen, they understand we're in alignment on how to do that.

So those have been taking place over the fast past few weeks.

At a certain point, you're gonna hit great healthy debate and discussion on different points of view, and those are pinned if they get too long because we we want to try to get through all the the easy stuff, let's say.

And then there will be follow-up use case sessions.

They are scheduled where we'll address those stickier points, which we got to work together and everybody's at the table.

And I feel we have great collaboration again there.

But yeah, we're gonna hit some of those part points and find alignment that we can all work with, and then we can move on.

The work stream meetings are gonna be scheduled, that's where the work gets done.

We really want the alignment done before that, so it's a delicate dance to get there, but it's all gonna kind of be happening in the next couple weeks.

Um, the use cases are key to that, and then getting the meetings going where they're actually configuring again.

That way, then we understand how much work we need to that we have already done that will still work and how what we need to tweak and what we need to really change, and that will guide how much time and effort we need to do at this point.

Um so that is scheduled.

We did meet and review a governance charter, which outlines the goals of the project at a high level, the guiding principles.

We could we spelled out what standardized streamline and simplify kind of mean and point everybody to this North Star.

We read that uh overview that with all the team leads and project members, like a hundred plus people, and that has been distributed.

So that's kind of like our go-to guide to say here's how we're operating.

We all this is what how we're gonna make decisions, how we'll escalate decisions, what your roles are, how the project's gonna function.

And so we did that.

That was a key point to framing all this up.

And we are then looking at, I mentioned the go live date still.

We were really honing in on that.

Collaboration is great.

It does take time.

And to get it right, you need to spend the right amount of time on it.

So we are looking at the go live dates, any risks to um not uh to give us more time, let's say, whether it's we penciled in nine one, I think I talked about, let's say it may move.

If we can give ourselves four more weeks or eight more weeks, great collaboration, some of the unknowns on the work we may need to redo.

Um, so we are working with that rapidly, and we should have an answer to that in the next week or so.

Um, but focusing on what are the risks of that?

Are there any from a project standpoint from an operational standpoint, etc.?

Um, so that is another key point we're working on.

It's really all I kind of wanted to update you on, which is kind of happened in the interim.

Once we really get going in the next couple of weeks, these will be more in depth as the project really going.

The updates will be sorry.

So it sounds like you're still on track and that you'll know more about the final date and everything soon, it sounds like you'll have the more penciled in a little harder date in a couple of weeks.

With any project, I was just clarifying, you could use more time.

So yeah, if we don't the the time is to do the collaboration and the unknowns of what we need to redo.

So we want to set ourselves up for success.

So we're really focusing, we could use more time.

So what are the risks to that?

And then um to say we're on track, we'll come more that way.

But yes, so far we are, but we need more time.

So we do have our funding deadline.

So we know we we are getting this done.

We're still on track for that.

Clear consideration, absolutely.

Yeah.

And you can use a lot of the work that was done last year, right?

It's so it's you said it's just figuring out what you can use from before and how to move it forward.

We believe in hope, but until we start understanding, get some of this alignment.

Um, if if you were we aren't in alignment, we had just uh configured something somewhere, there might be more uh change to it.

And then we have to consider the time it takes to do that as well.

Well, maybe by your next meeting, we'll I guess we'll know more.

It sounds like so thank you for the update.

Any questions about the update?

All right, yeah.

Cannot wait for this system to be on line.

Neither can I.

I know.

I'm sure the whole county is filling that way.

All right, thank you very much.

Thank you.

All right.

Is there a county administrator?

No county administrators.

I believe there's no executive session.

Are there are there any members or marks?

All right.

Well, then I declare this meeting adjourned.

Our next meeting is April 3rd, 2026.

Sounds like spring, April 3rd.

All right, everyone, have a good rest of your day.