[0:02] Table, and we'll have everyone else do an

[0:05] introduction. If you have any questions, go ahead

[0:07] and throw that into the chat function or

[0:09] do the raise the hand thing. That way,

[0:12] we can make sure that we include you

[0:15] into the dialogue here. So first, before we

[0:17] go around, we'll start with Christy Christy Tidd,

[0:21] Green County Department of Development. Vicky Sheets, Green

[0:26] County Department of Development. Randy Gilbert, Sanitary Engineering

[0:30] Department. DeAngelo Navratil, Greene County Regional Planning. Alright.

[0:36] This is gonna be I don't know how

[0:37] to to really it's kinda like herding cats

[0:39] here, but if everyone who is logged on

[0:41] and has the ability to access a mic,

[0:44] if you just kinda introduce yourself real quick

[0:46] and who you're with. But before we do

[0:48] that, actually, is do we have anyone from

[0:50] Greene County's IT Department on the call? Yes.

[0:54] This is Mitch Fletcher, network admin. Awesome. Thank

[0:58] you so much for coming. Mitch will be

[1:00] our sort of point of contact for any

[1:02] technical related questions that we might receive. Alright.

[1:06] So if you can maybe start with the

[1:08] Jacobs team and then we'll go with everyone

[1:09] else. So Jacobs is our consulting agency that's

[1:13] helping us build this RFP and a one

[1:15] stop shop permitting solution. Yeah. I'll go first.

[1:19] Oh, sorry. Janine, I think you're on mute.

[1:32] Yeah. I got it now. Sorry about that.

[1:34] Janine Dioriso, I'm one of the two key

[1:37] main players helping pull this RFP together, and

[1:41] we'll be walking through the scope of work

[1:43] with you. Yep. I'm Eric Habermeyer with Jacobs.

[1:47] I've been working with Janine just to kinda

[1:49] help put this together. And then I think

[1:51] for the rest, maybe just go alphabetically if

[1:53] you can follow the no. I'll turn it

[1:55] over to Ann. Albert, I think, is the

[1:56] next on the list. Ann Albert, did you

[2:01] there's a lot of echo. Not sure if

[2:18] I'm next, but, this is Michael Bowen with,

[2:21] three s g plus. Good morning, everyone. Eric

[2:24] Sabato, MainStar. Brian Fatka, Maria Delisle, and Sandy

[2:31] Hess, and we are all from the ICC

[2:33] Community Development Solutions. Ben Smith with Tech Systems.

[2:44] This is Ray Barker and Kara McFall with

[2:46] Online Solutions Citizenserve. Eric and team, good morning.

[2:56] This is Austin Kaiser with three s g

[2:58] plus. A little out of order here, so

[3:00] apologize for that one, but good to see

[3:02] you guys. Hey. Good morning. This is Yeah.

[3:07] Might be jumping as well, but Taylor Brodersen,

[3:11] Helen Whiteco, and Savannah Harris all here with

[3:14] Brightly Software SmartGov. Hey. Good morning. This is,

[3:20] Harish Krishna with Tejas Gov together with, my

[3:24] colleague, Nandan Naik from Atlanta, Georgia. This is

[3:30] Gavira Corrido with Cityworks Trimble. Michael Romano, Cityworks

[3:40] Trimble. Janelle Ennis, Cityworks Trimble. I'm not sure

[3:49] if I'm in the right order here, but

[3:50] I guess it makes the most sense for

[3:52] us to introduce ourselves now. My name is

[3:54] Matti Pujalt. I'm here with Tim Sharber. We

[3:57] are both here with NV five Geospatial. Jason

[4:06] Thompson, I'm here with Zipflo. Alright. Is that

[4:21] everyone? The do we miss anyone here? This

[4:24] is this is Shadrick Adams with Greene County

[4:27] Public Health. I'm also responsible for the noise

[4:30] at the beginning of the call, so I

[4:32] apologize to everyone. My mic was on. It's

[4:34] all good. Thanks, Shadrick. This is Chrisana Anderson

[4:37] Lutz. I'm with Greene County Engineer. Thank you.

[4:42] This is Al Kuzma, Greene County Building Regulation.

[4:52] Right. I think that's everyone. Alright. So just

[4:56] a minute, I'll hand things off to the

[4:58] Jacobs team to kinda walk us through this

[5:00] PowerPoint presentation. But before we get started, I'd

[5:03] like to just make sure that we're all

[5:05] tracking the same time frame here. So any

[5:08] questions are due by January 30 by four

[5:12] p. M. Eastern Standard Time. Our responses back

[5:15] to you are due by February 6, '4

[5:17] p. M. And all proposals are due by

[5:20] February 20. And that is eleven a. M.

[5:23] Eastern Standard Time. So with that, I'm going

[5:27] to hand things off to Janine and Jacob's

[5:29] team and they'll walk us through their presentation

[5:31] here. Yeah, thank you. So there's the agenda.

[5:39] Let's hit the purpose of the RFP real

[5:41] quick. Eric, if you can go to that.

[5:44] So that's that schedule overview. Oh, sorry. Eric,

[5:48] can you go back to the schedule overview?

[5:52] Sorry about that. And this is what Eric,

[5:55] Henry was just speaking to. This schedule overview

[5:58] is included in the RFP, so you can

[6:01] see those dates. There is a note underneath

[6:04] that that indicates, you know, these dates could

[6:06] change, but for the most part, this is

[6:09] the solid schedule that Greene County is looking

[6:12] to follow. Eric, you want you can go

[6:16] to the next slide. So how we want

[6:19] to conduct a meeting. So support consultant is

[6:24] us, Jacob. Greene County, and we will present

[6:29] the topics listed in the agenda. We wanna

[6:31] leave thirty minutes at the end for your

[6:34] questions and answers. So let us get through

[6:37] the core content. If you have a question,

[6:41] jot it down, and when we open it

[6:42] up, we'll certainly respond to those. And as

[6:46] Eric said, the hand raise function is gonna

[6:48] help us when we get to that point.

[6:51] All questions we will be documenting any questions

[6:54] that are raised here verbally, but you might

[6:56] notice that in certain instances, we will say,

[6:59] please submit that in writing, because we know

[7:03] that that's gonna be information that, you know,

[7:05] needs to be documented and and pushed back

[7:07] out through, the response to questions. So just

[7:11] be prepared for that. Okay. Eric, the next

[7:15] slide. So purpose of the RFP, Eric Henry

[7:18] gave a nice summary on that. And just

[7:21] to really we're and we're not gonna read

[7:23] all this text, but really focus on key

[7:26] purposes. So technology solution, Greene County is looking,

[7:31] for a permitting and plan review technology solution.

[7:34] That could be one technology that encompasses all

[7:37] the requirements and the things they're looking for,

[7:40] or it could be a technology solution that

[7:43] involves a couple of different technologies. It is

[7:46] important to be mindful, and there's a technology

[7:49] diagram included in the RFP, of the existing

[7:53] technologies that they're working with. In certain instances,

[7:56] a software such as stages that supports building

[8:01] regulation, that's in that's staying. And so you'll

[8:04] notice that there are some requirements around triggering

[8:10] notifications between those two systems and and then

[8:14] some. So take in mind that full suite

[8:18] of software that they currently have in play.

[8:21] There's a couple of mentions of software that

[8:24] is optional. So this just indicates that Greene

[8:27] County is thinking through a few things, about

[8:30] their technology suite as it as it exists.

[8:34] And when we're looking for costing of something

[8:37] like an online phone system, I think is

[8:39] referenced in there, it's labeled as optional. They're

[8:43] considering that as part of the solution if

[8:46] if that's going to improve things for them.

[8:48] So take that in and be mindful of

[8:51] those details when you're looking at them. Overall,

[8:55] they are looking, as Eric said, this one

[8:57] stop. This is this is a lot about

[8:59] a key focus is on customer service and,

[9:03] efficiency and processing permit applications and plan reviews.

[9:08] And so ease of use on the customer

[9:11] side, what what the end user has to

[9:13] interact with simplicity, is a key objective in

[9:17] what they're looking for. Also, you'll see reference

[9:21] to smartly presented. So if I'm a customer,

[9:24] I'm entering what I want to do, what

[9:26] type of business I want to do at

[9:28] Greene County. The system through entering of of

[9:32] few keywords will help present to me the

[9:35] process I need to follow, the permit applications

[9:38] I'm I'm going to need to apply for,

[9:41] the turnaround times that I can expect as

[9:44] these applications go through internal review. So these

[9:49] are key objectives that the county is looking

[9:53] for. And then, of course, on the internal

[9:55] side, having access to whose court is it

[9:58] in now. I've reviewed it. I'm sanitary engineering.

[10:01] I need to now have county engineer do

[10:05] their thing. So, there are timings of push

[10:08] notifications. So notifications and supporting that process is

[10:12] another key objective. The staff are aware of

[10:15] where things are at and and those turnaround

[10:17] times and how they're performing in alignment. So

[10:21] that's an expanded purpose and vision. Eric, you

[10:24] can go to the next slide. So scoop

[10:27] of work. So this is included in appendix

[10:30] b as in boy. Eric, you can move

[10:33] that past that slide. So boring text, I

[10:37] know, but just to emphasize what the county

[10:39] is looking for. So phase one on project

[10:41] definition, you see a couple of key tasks.

[10:45] So the scope of work when we lay

[10:46] this out, we are asking you to present

[10:49] a proposal that more or less follows what

[10:52] is being asked for. You'll see a lot

[10:54] of rigor, in the configuration stage around testing

[10:58] and training. Those are critical elements because we're

[11:01] really on cost client adoption, end user adoption,

[11:06] and ease of use. In the project definition

[11:09] phase, it's just, you know, setting out that

[11:11] project management plan. What is your timeline? What

[11:14] are the key, activities that will be going

[11:17] on? And a key thing this informs is

[11:19] you're working with busy people. Whoever selected will

[11:22] be working with really busy people and they

[11:25] need to know that schedule in advance of

[11:27] when their time is going to be needed

[11:28] so they can plan accordingly. And then, of

[11:31] course, the kickoff meeting to explain how things

[11:34] are going to move forward. On the next

[11:37] slide, we're starting on phase two, which is

[11:39] really the blueprinting. One thing I really want

[11:42] to emphasize is Greene County staff, people around

[11:46] the table that you're that are on this

[11:48] call, and others did a lot of intense

[11:51] work to envision what they wanted. And so,

[11:55] you'll notice in the, right under the the

[11:58] phase two blueprinting title, it says confirm business

[12:02] processes. A big difference, and this is, something

[12:06] to take note of, we are not asking

[12:08] you to start from scratch and and pull

[12:11] these people through a bunch of, well, how

[12:12] would you like it to be set up?

[12:14] How would you like it to work? They

[12:16] have done a lot of great work toward

[12:18] that end already, and it's very detailed business

[12:21] process diagrams in that appendix b. That is

[12:25] their vision. It's also been couched that, you

[12:28] know, this may be your vision. You may

[12:30] not get a % of of how you

[12:33] want this to work. It may be 90%.

[12:36] That's what we're targeting. Right? It's not a

[12:38] hundred. But nonetheless, that is their vision. So

[12:41] I've they've gone through a lot of effort

[12:43] to do this. So I really wanna emphasize

[12:45] that you're not hitting the you know, from

[12:47] ground zero, you're starting a leg up. And

[12:51] what came out, the tech technical the functional

[12:54] requirements that you see in that Excel spreadsheet

[12:57] that was included in the proposal package, that

[13:01] we're asking you to fill out, those functional

[13:04] requirements are directly related to those business process

[13:08] diagrams by business process listed, and they are

[13:11] categorized by permit type or plan type that

[13:14] is being reviewed. So there is a one

[13:16] to one alignment there. So those diagrams really

[13:19] help understand what the county's asking for, from

[13:23] a vision standpoint, and those functional requirements were

[13:26] asking you to say, can your technology solution

[13:29] do this? Is it out of the box?

[13:32] Is it something that would need to be

[13:33] created? You know? So they have some sense

[13:36] of what your solution how many of those

[13:39] requirements it actually needs. So as part of

[13:42] blueprinting, that system implementation plan, you know, is

[13:47] a task creating the that more detailed technology

[13:50] set of steps, going through the functional requirements,

[13:54] the business process, and then working with their

[13:56] IT designated person around to make sure there's

[14:00] an understanding around data security, any hardware or

[14:05] interfaces to existing software. So, is that blueprinting

[14:10] phase, a lot of work, but there is

[14:12] also a starting point. On the next slide,

[14:16] we show an example of those detailed business

[14:19] process diagrams. I know you can't read that

[14:21] on the slide, but they are in the

[14:23] RFP. Again, you know, you'll kind of notice

[14:26] workflows, and I know technology people are used

[14:29] to looking at these. And you'll see the

[14:32] existing systems reference as well as a generic,

[14:36] blue cylinder data box that is labeled One

[14:39] Stop. That's the technology solution. And so, that,

[14:43] we're seeing what do we want One Stop

[14:45] to do at a particular step. Okay. Next

[14:49] slide. Then, during phase three, that realization phase,

[14:54] the the confirmation of the plan of action,

[14:57] the what what what the team the proposal

[15:00] team is going to be doing to build

[15:01] out. Now you're starting to realize and set

[15:04] up those configurations. Again, you'll you'll see a

[15:07] lot of reference to and they're in the

[15:09] scope of work in that appendix b. It

[15:12] describes what each of those testing steps entail.

[15:16] But for those of you who are technology,

[15:18] it's pretty best practice. Right? But a lot

[15:20] of emphasis on testing, making sure data's flowing

[15:22] because we've got several systems at play here.

[15:26] And then training too. We're not looking for

[15:29] a very simple one day training. This is

[15:32] how you do it. But know that there's

[15:36] a lot of, people not only on the

[15:39] customer side, but on the, internal side that

[15:43] come from different groups. So, the training can't

[15:47] just be this quick one day. There's there's

[15:49] some kind of focused training that needs to

[15:51] go on. Again, because the the long term

[15:54] interest is that they've got a solid technology

[15:57] solution that's accepted and used and loved by

[16:02] staff. Okay. Next one down. And then go

[16:10] live. Of course, being there when things go

[16:13] live, be there for when, questions are being

[16:17] asked. And, in particular, in the costing sheet,

[16:20] you'll see, there's an interest in knowing the,

[16:23] just up to five years, what those annual,

[16:27] five years cost would be, to provide the

[16:30] maintenance and support. Alright. Next one. We're getting

[16:35] to questions, guys. Okay. Last section that I'm

[16:38] gonna talk through, and then we'll toss it

[16:40] back. Go ahead, Eric. So just, this is

[16:43] in the RFP itself, but just, verbalizing is

[16:47] there's the address for where the hard copy

[16:50] proposal should be submitted along with the USB

[16:53] flash drive. So you'll see they're looking for

[16:55] five hard copies. That includes that separate Microsoft

[16:59] Excel spreadsheet where you are responding yes, no,

[17:03] maybe with configuration, those types of things to

[17:06] each of those requirements, and then an electronic

[17:09] copy. So both the proposal itself and that.

[17:13] And then the cost proposal, they want in

[17:15] a separate field envelope. Alright, Eric. So the

[17:22] proposal requirements, you're used to seeing these categories.

[17:28] There are indications of page limits, so it

[17:31] gives some sense of detail on what's being

[17:34] looked for. Just clear writing, nailing the what

[17:39] is being asked for and and providing that

[17:41] exactly is a key. Right? Simplicity and clarity

[17:46] is is is gonna be the key. You'll

[17:49] notice on the e, item e, the proposed

[17:52] technology solution, that's pretty short, two pages. It's

[17:56] a basic statement of, okay, are the needs

[17:58] that we have. What do you propose from

[18:01] a technology? You may be teaming up with

[18:03] another technology provider, or you may have the

[18:07] whole enchilada in one suite. But the point

[18:09] is is is that section is to say,

[18:12] what is it? We're not looking for a

[18:14] bunch of salesy material. We know sometimes people

[18:17] will go their route of in a section

[18:19] like that, you know, throwing in 10 brochures.

[18:22] That's not what we're looking for. We're looking

[18:24] for simplicity and clarity. Please state exactly what

[18:27] you're proposing. And then it's in that item

[18:29] f where we want you to detail out

[18:32] the approach. And, again, the the key nugget

[18:35] here is the approach is the scope of

[18:37] work that's detailed out in appendix b as

[18:40] in boy. So if you follow that scope

[18:43] of work, obviously, you're professionals. There are variations

[18:48] from that, which is fine and understandable. But

[18:51] for the most part, you have the messaging

[18:54] around intense testing, good training. Those are key

[18:58] nuggets. Okay? Almost there. Okay. The cost proposal

[19:04] sheet, which is appendix a, you'll notice just

[19:08] out of the gate that in the table

[19:10] itself, each of the, from the scope of

[19:14] work, each of the numbered scope of work

[19:16] items are listed there. The titles are listed

[19:19] there, and that's where we're emphasizing, please follow

[19:22] this approach. Right? How much would it cost

[19:24] you to get through that, you know, the

[19:26] estimate, any expense costs associated? On the expense

[19:30] cost, you know, if there's a lot of

[19:33] work you can do remotely and you're not

[19:35] having to travel in, especially if you're not

[19:37] local, that's gonna, you know, weigh well. So

[19:40] you're balancing out that need of being in

[19:42] person and the value of that versus work

[19:45] you can be doing offline. And then on,

[19:49] what's flashed up on the screen is the

[19:50] second page of that. You'll see reference to

[19:54] the interpieces, a potential for data migration if

[19:59] the decision is to get rid of one

[20:01] of their existing technologies, because this new technology

[20:05] solution might place this. I say that with

[20:08] the disclaimer. There has been no decision towards

[20:10] that end. It's just a potential, and we're

[20:13] leaving options open where where decisions still need

[20:18] to be made. There are references in the

[20:22] interfaces two to three non Greene County, so

[20:27] statewide systems where different groups or divisions at

[20:32] Greene County must interact with. You've got a

[20:34] system like TOCAY. You've got the health department

[20:38] uses HDIS. These are statewide systems. They are

[20:41] not going away. So, you'll see referenced and

[20:44] described in the RFP. And we've already had

[20:47] conversations with those entities. But a a very

[20:52] simple data exchange, whether that's a direct integration

[20:56] or, a data export from those systems where

[20:59] someone manually is bringing that into the new

[21:02] technology system on the Greene County side, which

[21:05] that latter is the more practical of what's

[21:08] gonna happen based on what we know. Those

[21:10] statewide systems don't want Greene County systems, you

[21:14] know, feeding information in and out and exchanging.

[21:16] So that data export process is is the,

[21:20] route that is most likely. So but please

[21:25] look at those costing things as, let's put

[21:28] them in here as if it were an

[21:30] integration on a couple of those data points

[21:33] just for cost comparison and as prompted there.

[21:38] I'm probably confused that just read what's written

[21:40] there, which is please give us a cost

[21:42] for an integration. But, again, for your back

[21:44] pocket, most likely, will be a manual export

[21:47] import. Okay. Almost done, Eric. Okay. The the,

[21:54] functional and technical, requirements response work, which is

[21:58] that Excel spreadsheet. Again, it supports the listing

[22:03] of requirements as defined by Greene County staff.

[22:07] We would like you to submit that, you

[22:10] know, along with your proposal that's helping with

[22:13] the evaluation that the voting members are gonna

[22:15] be going through. It doesn't count on your

[22:18] proposal page limit, and you can see the

[22:21] number of different types listed there. So, functional,

[22:24] how do we want it to behave? The

[22:26] notification, routing, you know, display performance metrics against

[22:32] processing time, those types of things. On the

[22:35] technical requirements, that was heavily led by Greene

[22:39] County IT, to help describe the technology environment,

[22:44] any data and security requirements, those types of

[22:46] things. And you'll see that categorization when you

[22:49] look at that workbook. Again, there's two worksheets,

[22:53] functional requirements, technical requirements. Okay? You can't read

[23:02] that. That's just an image of what it

[23:04] is. So you have the requirements listed on

[23:06] the left, the category that it falls into,

[23:10] and you're filling out those four blue columns

[23:12] with, and there's some acronyms there that that

[23:15] indicate, yes, the my technology solution can wholly

[23:18] meet this. No problem. Or it can't. Right?

[23:22] So and we recognize that a % of

[23:26] everything Greene County has envisioned may or may

[23:29] not be possible. Alright? The proposal evaluation criteria,

[23:37] this is directly from the RFP. So we're

[23:40] quality of the proposal references. Where have you

[23:43] done something similar? We know it may not

[23:46] be exactly similar, but, those references are important.

[23:51] Your just general qualifications and experience. Is this

[23:55] your first time ever doing this, or have

[23:57] you done this, you know, 5,000,000 times kind

[24:00] of a thing? That ability to meet desired

[24:03] functionality, again, that workbook that has the functional

[24:06] and technical requirements, that's, you know, an important

[24:12] extremely important consideration for the voting members. And

[24:15] then we've got the cost listed out as

[24:17] well. And I think that's probably the last

[24:21] slide for me. Eric Henry, I'm gonna toss

[24:26] it back to you if you've got someone

[24:28] there who can do this last section on

[24:30] the contract forms and then we can open

[24:32] it up to q and a. I I

[24:34] don't believe we have anyone from legal on

[24:36] the call. All I'll say about this is

[24:38] these are required documents for your submittal of

[24:41] of your bid. If you have any questions,

[24:44] I'd ask that you send those in writing

[24:45] so we can have our legal team go

[24:47] ahead and review them. Then I'll put out

[24:50] some sort of FAQ available to all to

[24:52] make sure that those answers are able to

[24:55] be reviewed by everyone once spent. So that's

[24:58] all I have to say about that section

[25:00] time being. Respond, I mean, about that. I

[25:09] don't know if Jeanine, you wanna go over

[25:10] that or I feel like it's self explanatory,

[25:14] but I'm happy to encourage questions, comments on

[25:18] this. Okay. Alright. Well, let's since that's a

[25:24] nice segue, let's go ahead and open it

[25:26] up for questions. Think Eric, Hob Habermeer, if

[25:30] you can, do that, we can open it

[25:32] up. So that was a lot. It may

[25:37] rest, where let's go ahead and and open

[25:39] it up for questions. And as, Eric Henry

[25:42] suggested, if you don't mind using your hand

[25:44] raise, that'll give some sense of order to

[25:46] any questions. Let's see. And Eric Habermeyer, you

[25:57] can help me. Why am I not seeing

[25:59] the hand raised? Okay. Who's that? Taylor Roderson?

[26:05] Yeah. Thank you. Can you hear me okay?

[26:08] Yep. Yes. We can hear you. Perfect. So

[26:13] I'm looking at it's mentioned a couple of

[26:15] times the interfaces that are required and optional,

[26:21] and I'm specifically looking at page 18 where

[26:24] it has them, labeled out in a table.

[26:27] I was curious, and I can kinda ask

[26:29] these questions one by one, but I was

[26:31] hoping to get a better sense of exactly

[26:35] what each of these systems is used for

[26:38] today. And secondarily to that question would be

[26:42] if the solution that we're bidding on could

[26:46] help consolidate some of these other systems. Is

[26:49] that something you'd like us to propose as

[26:51] well, or is the county looking to definitely

[26:55] keep all of those in place and just

[26:57] integrate? So sorry. Long question. It's a great

[27:02] question. One thing that popped into my mind,

[27:05] Eric Henry, I'm stalling for time because I'm

[27:07] gonna toss it to you as the official

[27:08] kind of take the questions and farm it

[27:12] out. But, Eric Coppermeyer, if you don't mind,

[27:14] I think, having the RFP, maybe we could

[27:16] even pull up that page 18 might be

[27:19] helpful. Yep. I'm pulling it up right now.

[27:24] Okay. And, Taylor, to oh, sorry. There is

[27:28] a diagram that I think is helpful. I

[27:30] think it's figure two one that shows the

[27:34] different technologies in play, and there's some commentary

[27:37] about what type of information is desired to

[27:40] be shared. Is that all the details at

[27:43] the moment? No. But it gives that high

[27:45] level. So anyway, Eric Henry, did I spell

[27:49] enough for you? So for the first part

[27:51] of your question, I would leave that to

[27:53] the individual departments to answer specifically. The second

[27:58] part, I'm gonna give you kind of a

[28:00] nuanced answer. It's just probably not super helpful,

[28:03] but in a perfect world, consolidation would happen.

[28:07] That being said, it feels like it's it's

[28:10] so burdensome and so complicated that it's unattainable,

[28:13] but I'd be happy to look at proposals

[28:17] that have that function in there. But it's

[28:19] not something that I'm requiring at this time,

[28:21] if that makes sense. So if I'm hearing

[28:26] that correctly, you know, being able to interface,

[28:29] you would want us to outline but would

[28:31] also be open to a recommendation where we

[28:35] may be able to consolidate. Correct. Okay. Yeah.

[28:40] That's helpful. And I do see the 2.1,

[28:50] so that's really helpful as well. But if

[28:52] any of the departments have any other detail

[28:55] that would be helpful for us on the

[28:56] different systems, definitely open to hearing that. I

[29:02] don't put you on the spot. What do

[29:04] you I I I don't. Okay. We'll start

[29:08] with the media room that we have here,

[29:09] then we'll open it up to the people

[29:11] on the call. So go to Randy with

[29:14] sanitary first. Yeah. With sanitary, we use the

[29:17] Cityworks. CityWorks is our main AMS asset management

[29:24] system. We have the add on for the

[29:27] PLL for all of our permitting, and all

[29:31] of our historical permits are listed or are

[29:34] contained in that software. So that is a

[29:37] very vital piece of, history for us. While

[29:44] it is listed as an optional, someone's going

[29:47] to have to make a very good case

[29:49] to me to move away from it. I

[29:55] that's not going to be a decision that's

[29:57] made likely. I'll I'll just say that. We

[30:00] spent too much time and effort getting where

[30:02] we're at. It's gonna have to be a

[30:05] very great solution to move me away from

[30:07] it. So I do wanna make that comment.

[30:11] Now Tokay is the other one that we

[30:13] utilize that's on this list. That's our backflow

[30:17] prevention system. We keep track of all the

[30:21] backflow devices in our system. Again, that's a

[30:28] software that we've just we spent a lot

[30:29] of time getting up and running. If there's

[30:32] another solution, I guess we'd be we'd entertain

[30:35] it. But, again, it has it would have

[30:38] to have all of the abilities that that

[30:42] software has it that we're used to and

[30:44] our plumbers are used to before we would

[30:48] consider moving. Deandra? Sure. So for regional planning,

[30:56] we don't directly work with any of these

[30:58] interfaces aside from GIS, but we use that

[31:01] more for research purposes and for zoning research

[31:05] and helping our people who call us with

[31:08] questions on that. The only thing that we

[31:10] would be looking for directly is the online

[31:14] payment system because right now, we don't have

[31:16] anything. We only take cash and checks at

[31:20] the moment, so that's something that other departments

[31:22] have obviously modernized on, and that's something we're

[31:26] really gonna need assistance with. Awesome. Thank you.

[31:32] I'm trying to think off the top of

[31:33] my head. So let's go with public health.

[31:35] Chad. Chadwick? Yeah. Chadwick here. We utilize the

[31:40] program known as HDIS. That's health district information

[31:44] systems. It's a very old, archaic database program

[31:51] that encompasses just about everything that happens at

[31:54] a health district from environmental to community health,

[31:58] billing, receiving, tracking time, and mileage, all sorts

[32:03] of things. Despite its age, we are not

[32:07] looking for a replacement within the scope of

[32:11] this of this proposal. Because it is so

[32:15] old and somewhat sensitive, we want an export

[32:20] only function with HDIS. That is we send

[32:24] out our plumbing information into the one stop

[32:29] shop database that we're proposing here, but it

[32:32] would not be two way. Yeah. Sorry. I'm

[32:37] gonna chime in here. This is Janine. And

[32:39] that's indicated in the RFP as you just

[32:42] said. Right? And I'm saying this for all

[32:44] the proposers. Tokay that was referenced by Randy

[32:48] Gilbert, which is the backflow prevention, that is

[32:52] not intended to go away. It's just the

[32:54] export activity. HDIS is another system that's used

[32:59] at the state level that's not going away,

[33:02] as well as a system called SWPPP. You'll

[33:07] see that reference. That's a statewide, you know,

[33:11] system as well. So, again, with those three

[33:13] in particular, there's no replacement of that functionality

[33:17] desired. Thank you. Let's go with Prasanna, are

[33:27] you there for the accounting engineer? Yeah. I

[33:29] am. Yeah. I just like to reiterate what

[33:31] Janine just said, which is that SwiftTrack is

[33:34] definitely something that we cannot replace. We're not

[33:37] looking to replace. It's integral to what we

[33:41] do with our storm water, and it does

[33:43] an excellent excellent job with that. So we're

[33:45] gonna go ahead and keep that the way

[33:47] that it is. Apia is newer for us

[33:52] and we are really liking the way that

[33:54] it works. So we don't need to have

[33:57] it replaced. But Apia is something that we

[34:04] would consider if necessary, if someone had something

[34:07] better out there. But it's working right now.

[34:13] So that's about it. Fantastic. And last, certainly

[34:18] not least, Al of the building department. Yeah.

[34:22] Sage is, we're committed to that program. It's

[34:25] our permit tracking system, plan review, also keeps

[34:31] track of all our inspections. So, we're well

[34:35] invested in that. We like it, and we

[34:39] wanna keep it. Although, I do wanna keep

[34:43] it open mind just in case there's something

[34:47] else out there. But, you know, that would

[34:50] be pretty exceptional for us to give up

[34:52] on stages. And if anybody has So let

[34:56] me let me do a summary here for

[34:59] people on the phone who are, like, wait.

[35:01] What's going on? There's, like, existing plan review,

[35:04] permitting systems at certain and this is in

[35:07] the RFP, but we're just verbalizing. You've got

[35:09] building regulation. Al just spoke and he spoke

[35:12] about stages, and that's indicated as something that

[35:16] is not going away in the RFP. Stages

[35:19] currently only handle plan, review and permitting tracking

[35:24] for building regulation. The challenge is is that

[35:27] other divisions who need communication and coordination and

[35:32] and process flow to be supported as a

[35:35] whole unit, is the county and these divisions

[35:38] working together, a system like Sage's is not

[35:42] currently supporting them. Similarly, when Randy Gilbert over

[35:47] sanitary engineering was describing his use of Cityworks

[35:50] for their asset management, that is not going

[35:53] away. They're using, in to a a certain

[35:58] degree, the PLL module of CityWorks. But, again,

[36:01] it's just sanitary engineering. And you heard Randy

[36:04] say, and it's labeled as optional. If the

[36:07] new technology solution that we're asking for through

[36:11] this RFP, does a with BAM job, right,

[36:15] and could convince the Randy Gilbert and sanitary

[36:18] engineering to release the CityWorks PLL component, then

[36:22] that's what happens or vice versa. CityWorks PLL

[36:25] is proposed to support larger divisions. I know

[36:28] we got some CityWorks people. So you gotta

[36:30] think of that, you know, it's the challenge

[36:33] is it's being used, stages and both Cityworks

[36:35] are being used by single group when it

[36:38] needs to support all their groups or a

[36:41] whole new technology solution is in play. So

[36:47] that's kind of the big overview if you

[36:49] hear people saying my plan in permitting review

[36:53] software is not going away because it's already

[36:57] supporting me. Did that confuse the matter or

[37:03] bring clarity? I think that was really helpful.

[37:08] I think all the feedback is helpful in

[37:10] understanding where each department is. So thank you

[37:15] very much. Looks like we have the next

[37:21] question from Matthew. Yeah. Hey. Matthew here from

[37:30] NV5 Geospatial. Out of curiosity, will Jacobs be,

[37:35] providing a proposal to this RFP? No. We

[37:41] are we we are not. We're a partner

[37:45] with Greene County in getting the RFP ready

[37:49] in alignment with their needs. Our role on,

[37:56] the implementation phase of it is is TBD,

[38:01] but but if there is a role there,

[38:03] we would be helping to manage the implementation

[38:06] and serve as a gatekeeper to answer questions,

[38:09] those types of things. Okay. Great. Thank you.

[38:27] Other questions? This is Taylor again, if it's

[38:34] okay. I had one more. The RFP points

[38:38] to 15 I think it was 15 unique

[38:41] dashboards. Are there specific data points and dashboards

[38:46] that the county is referencing for those 15

[38:49] or just looking for the ability to create

[38:52] custom dashboards? Great question. So, yes. So think

[38:59] of the end user that 15 number is

[39:02] up to, I believe that's the language, but

[39:06] that's the intent anyway. Think of the end

[39:09] users within the county. So you have, you

[39:11] know, executive leadership is interested in tracking metrics.

[39:17] How are we doing? In particular, are we

[39:19] being responsive to customers? We have stated out

[39:23] there that, you know, once you submit an

[39:25] application, it takes so many days to process.

[39:29] How are we as an internal group performing

[39:31] against that? So I'm making this up because

[39:33] we haven't yet defined those dashboards. What would

[39:35] they like on their dashboard if they could

[39:37] pick, like, 10 things? But that's the idea.

[39:40] So executive leadership, the the directors of each

[39:44] of the divisions, Randy Gilbert, you know, etcetera,

[39:49] Stephanie Gough, they will have specific for their

[39:53] own group and their responsibilities, you know, kind

[39:56] of keeping an eye on the ball and

[39:58] making sure things are proceeding process wise and

[40:00] they have a sufficient time. So those are

[40:02] the types of metrics more aligned with performance

[40:05] metrics, but still TBD. In the RFP itself,

[40:08] I think we're requesting the cost associated with

[40:11] if you were out of the gate to

[40:13] build a dashboard for them, how much would

[40:16] that level of effort be with the intent

[40:18] that they would, through the training, would then

[40:21] have the competency internal to create, you know,

[40:25] random dashboards, ad hoc reports, should they need

[40:28] to beyond that. So we're just looking for

[40:31] the pricing of the dashboard piece actually creating

[40:35] them. Okay. Thank you. Hey, everybody. This is

[40:45] Michael Vaughn from DraftG Plus. I had a

[40:48] question about the getting back to the two

[40:51] way integrations with some of the various systems.

[40:53] Are is it known at this time whether

[40:55] systems like Tokay and Sages, do they have,

[40:59] like, a an open API that that that

[41:02] can be accessed and leveraged? Or is that

[41:05] is the expect is the expectation that that

[41:07] will be investigated and and and included in

[41:10] the response? Great question. So we headed that

[41:15] off. We did work with Greene County to

[41:17] reach out to representatives from each of those

[41:20] software vendors, to get clarity on that, you

[41:23] know, would would you be open to a

[41:26] a connection through an API or, you know,

[41:29] or or do you have strict rules about

[41:31] that? And absolutely, say no. All of them

[41:35] indicated the preference was for that manual export.

[41:39] So but they also referenced, potential for API

[41:44] connection. So does it need to be further

[41:48] discussed with them once they see the actual

[41:50] data points of what we're looking for? And

[41:52] we did kinda summarize that for them so

[41:53] they saw that it's really about notifications of

[41:57] when something is done. So when something is

[41:59] done, for example, in SwiftTrack, which is a

[42:02] statewide system, it works well. That the the

[42:06] status of whatever's being done in SwiftTrack is

[42:09] pushed into that one stop portal so the

[42:11] customer truly has. Can the customer go to

[42:14] SwiftTrack separately? Of course. But we wanna bring

[42:17] it all together to them in one place.

[42:19] So it's really primarily notification of where the

[42:23] process is at within those other systems. So

[42:26] that's the that's the the the type of

[42:28] information, But, yes, definitely needs to be further

[42:33] discussed with them. But those connections are made.

[42:35] They're aware of the potential request coming. And

[42:39] if we cost it what that API, just

[42:42] simple notification of process integration is, then we

[42:46] know that cost associated with that option if

[42:48] those in entities say yes. Okay. Great. So

[42:54] so I'm thinking about in thinking about the

[42:56] proposal, you know, our our our our charge

[42:59] is to investigate, well, a, the possibility of

[43:01] whether or not that's that's that can happen.

[43:04] But just the the cost associated with whatever

[43:06] development work would be required, you know, from

[43:11] the platform that we're proposing, the one stop

[43:13] shop platform, if you will, and and what

[43:15] that would take to to to essentially push

[43:18] that data into into these these other platforms.

[43:22] But in terms of the return data, the

[43:24] things that are triggered in in the the

[43:26] Sages and the ToeCase of the world, you

[43:28] know, that would require a little bit further

[43:30] exploration with those entities in order to in

[43:33] order to get that return data, if you

[43:34] will. Am am I understanding that correctly? Yeah.

[43:38] No. And you raised a very valid point,

[43:40] and I I I hear you. How about

[43:44] this? Greene County will note this as a

[43:47] question that we officially respond to, in writing.

[43:52] And do you mind just submitting that making

[43:55] sure you submit that question in writing, and

[43:57] then the county will have a response because

[43:59] you raised a valid point towards that end.

[44:02] Yeah. Yeah. Absolutely. We'll we'll make sure we

[44:04] get something submitted. Thank you, guys. Bye. Yep.

[44:13] What else? Hi. Kara McFall, Citizenserv. Will you

[44:18] be providing the copy of the recording of

[44:21] this conference? Eric Henry? I'm okay with it.

[44:31] Excellent. Thank you so much. Yeah. And it's

[44:40] it's a big it's a big, RFP. I

[44:44] think you probably all noted that, and in

[44:48] particular, the, I forget the name of the

[44:51] woman who brought it up. Taylor. Taylor. Thank

[44:54] you. You know, that technology diagram in 2.1

[44:59] gives you that sense of, complexity, that they're

[45:04] looking for with these different systems in play.

[45:09] But at the same time, just that if

[45:12] you keep that primary objective in mind, simplicity

[45:15] on customer, I'm coming to I'm sitting at

[45:19] home. I'm going I'm logging on. I'm typing

[45:22] in a few keywords about what I wanna

[45:24] do. And based on a search function, a

[45:27] search engine, the system is communicating to me

[45:32] the process I need to follow, the permits

[45:36] I need to apply for, expected turnaround times,

[45:41] right, processing times, and I'm able to follow

[45:45] and see where my application is in at

[45:49] the at any point in time. I also

[45:52] know when I'm required to do something and

[45:56] how long it's taken me. Right? And then

[46:01] internally, again, the the same functionality is there

[46:05] where internally they're able to see each other's

[46:08] comments on plans. They're able to see tag

[46:11] who's next because someone did just did something

[46:14] in the field. So that vision really speaks

[46:18] to efficiency and clarity of where I'm at

[46:21] in the process. So those are the key

[46:24] objectives. Even though there's a lot of existing

[46:28] technologies at play here, If you kind of

[46:31] think of it in that manner, it really

[46:33] keeps that end goal in mind. Alright. I'm

[46:39] very wordy. The county knows this, so I'll

[46:41] stop. Eric, I'm gonna toss it back to

[46:42] you. I have nothing to really add there.

[46:50] Is there anything that we can clarify further

[46:53] on or for anyone in the audience as

[46:55] far as that last question goes? Any additional

[47:04] questions? Well, not seeing any, so I guess

[47:13] we can give you about an hour and

[47:14] ten minutes back in your day there. If

[47:18] you wouldn't mind submitting any follow on questions

[47:21] in writing, that way we can make sure

[47:23] we provide it as clear as a response

[47:25] as possible. And, yeah, thank you for your

[47:28] interest, and enjoy the rest of your day.

[47:33] Thank you. Bye. Thank you.

Mandatory Pre-Bid Meeting Recording

Transcript