1 00:00:02,399 --> 00:00:05,200 Table, and we'll have everyone else do an 2 00:00:05,200 --> 00:00:07,759 introduction. If you have any questions, go ahead 3 00:00:07,759 --> 00:00:09,519 and throw that into the chat function or 4 00:00:09,519 --> 00:00:12,080 do the raise the hand thing. That way, 5 00:00:12,080 --> 00:00:15,085 we can make sure that we include you 6 00:00:15,085 --> 00:00:17,485 into the dialogue here. So first, before we 7 00:00:17,485 --> 00:00:21,885 go around, we'll start with Christy Christy Tidd, 8 00:00:21,885 --> 00:00:26,365 Green County Department of Development. Vicky Sheets, Green 9 00:00:26,365 --> 00:00:30,480 County Department of Development. Randy Gilbert, Sanitary Engineering 10 00:00:30,480 --> 00:00:36,160 Department. DeAngelo Navratil, Greene County Regional Planning. Alright. 11 00:00:36,160 --> 00:00:37,440 This is gonna be I don't know how 12 00:00:37,440 --> 00:00:39,280 to to really it's kinda like herding cats 13 00:00:39,280 --> 00:00:41,600 here, but if everyone who is logged on 14 00:00:41,600 --> 00:00:44,160 and has the ability to access a mic, 15 00:00:44,160 --> 00:00:46,054 if you just kinda introduce yourself real quick 16 00:00:46,054 --> 00:00:48,614 and who you're with. But before we do 17 00:00:48,614 --> 00:00:50,054 that, actually, is do we have anyone from 18 00:00:50,054 --> 00:00:54,454 Greene County's IT Department on the call? Yes. 19 00:00:54,454 --> 00:00:58,040 This is Mitch Fletcher, network admin. Awesome. Thank 20 00:00:58,040 --> 00:01:00,120 you so much for coming. Mitch will be 21 00:01:00,120 --> 00:01:02,840 our sort of point of contact for any 22 00:01:02,840 --> 00:01:06,680 technical related questions that we might receive. Alright. 23 00:01:06,680 --> 00:01:08,200 So if you can maybe start with the 24 00:01:08,200 --> 00:01:09,800 Jacobs team and then we'll go with everyone 25 00:01:09,800 --> 00:01:13,615 else. So Jacobs is our consulting agency that's 26 00:01:13,615 --> 00:01:15,295 helping us build this RFP and a one 27 00:01:15,295 --> 00:01:19,054 stop shop permitting solution. Yeah. I'll go first. 28 00:01:19,054 --> 00:01:32,150 Oh, sorry. Janine, I think you're on mute. 29 00:01:32,630 --> 00:01:34,790 Yeah. I got it now. Sorry about that. 30 00:01:34,950 --> 00:01:37,910 Janine Dioriso, I'm one of the two key 31 00:01:37,910 --> 00:01:41,635 main players helping pull this RFP together, and 32 00:01:41,635 --> 00:01:43,555 we'll be walking through the scope of work 33 00:01:43,555 --> 00:01:47,075 with you. Yep. I'm Eric Habermeyer with Jacobs. 34 00:01:47,075 --> 00:01:49,635 I've been working with Janine just to kinda 35 00:01:49,635 --> 00:01:51,600 help put this together. And then I think 36 00:01:51,600 --> 00:01:53,680 for the rest, maybe just go alphabetically if 37 00:01:53,680 --> 00:01:55,200 you can follow the no. I'll turn it 38 00:01:55,200 --> 00:01:56,640 over to Ann. Albert, I think, is the 39 00:01:56,640 --> 00:02:01,119 next on the list. Ann Albert, did you 40 00:02:01,119 --> 00:02:18,950 there's a lot of echo. Not sure if 41 00:02:18,950 --> 00:02:21,110 I'm next, but, this is Michael Bowen with, 42 00:02:21,190 --> 00:02:24,950 three s g plus. Good morning, everyone. Eric 43 00:02:24,950 --> 00:02:31,145 Sabato, MainStar. Brian Fatka, Maria Delisle, and Sandy 44 00:02:31,145 --> 00:02:33,385 Hess, and we are all from the ICC 45 00:02:33,385 --> 00:02:41,785 Community Development Solutions. Ben Smith with Tech Systems. 46 00:02:44,000 --> 00:02:46,560 This is Ray Barker and Kara McFall with 47 00:02:46,560 --> 00:02:56,239 Online Solutions Citizenserve. Eric and team, good morning. 48 00:02:56,239 --> 00:02:58,000 This is Austin Kaiser with three s g 49 00:02:58,000 --> 00:03:00,005 plus. A little out of order here, so 50 00:03:00,005 --> 00:03:02,405 apologize for that one, but good to see 51 00:03:02,405 --> 00:03:07,525 you guys. Hey. Good morning. This is Yeah. 52 00:03:07,525 --> 00:03:11,205 Might be jumping as well, but Taylor Brodersen, 53 00:03:11,205 --> 00:03:14,780 Helen Whiteco, and Savannah Harris all here with 54 00:03:14,780 --> 00:03:19,820 Brightly Software SmartGov. Hey. Good morning. This is, 55 00:03:20,060 --> 00:03:24,540 Harish Krishna with Tejas Gov together with, my 56 00:03:24,540 --> 00:03:30,985 colleague, Nandan Naik from Atlanta, Georgia. This is 57 00:03:30,985 --> 00:03:40,185 Gavira Corrido with Cityworks Trimble. Michael Romano, Cityworks 58 00:03:40,185 --> 00:03:49,220 Trimble. Janelle Ennis, Cityworks Trimble. I'm not sure 59 00:03:49,220 --> 00:03:50,740 if I'm in the right order here, but 60 00:03:50,740 --> 00:03:52,020 I guess it makes the most sense for 61 00:03:52,020 --> 00:03:54,864 us to introduce ourselves now. My name is 62 00:03:54,864 --> 00:03:57,424 Matti Pujalt. I'm here with Tim Sharber. We 63 00:03:57,424 --> 00:04:06,065 are both here with NV five Geospatial. Jason 64 00:04:06,065 --> 00:04:21,670 Thompson, I'm here with Zipflo. Alright. Is that 65 00:04:21,670 --> 00:04:24,765 everyone? The do we miss anyone here? This 66 00:04:24,765 --> 00:04:27,245 is this is Shadrick Adams with Greene County 67 00:04:27,245 --> 00:04:30,205 Public Health. I'm also responsible for the noise 68 00:04:30,205 --> 00:04:32,045 at the beginning of the call, so I 69 00:04:32,045 --> 00:04:34,765 apologize to everyone. My mic was on. It's 70 00:04:34,765 --> 00:04:37,885 all good. Thanks, Shadrick. This is Chrisana Anderson 71 00:04:37,885 --> 00:04:42,580 Lutz. I'm with Greene County Engineer. Thank you. 72 00:04:42,900 --> 00:04:45,780 This is Al Kuzma, Greene County Building Regulation. 73 00:04:52,604 --> 00:04:56,685 Right. I think that's everyone. Alright. So just 74 00:04:56,685 --> 00:04:58,525 a minute, I'll hand things off to the 75 00:04:58,525 --> 00:05:00,285 Jacobs team to kinda walk us through this 76 00:05:00,285 --> 00:05:03,724 PowerPoint presentation. But before we get started, I'd 77 00:05:03,724 --> 00:05:05,164 like to just make sure that we're all 78 00:05:05,164 --> 00:05:08,870 tracking the same time frame here. So any 79 00:05:08,870 --> 00:05:12,070 questions are due by January 30 by four 80 00:05:12,070 --> 00:05:15,110 p. M. Eastern Standard Time. Our responses back 81 00:05:15,110 --> 00:05:17,110 to you are due by February 6, '4 82 00:05:17,110 --> 00:05:20,630 p. M. And all proposals are due by 83 00:05:20,630 --> 00:05:23,685 February 20. And that is eleven a. M. 84 00:05:23,765 --> 00:05:27,285 Eastern Standard Time. So with that, I'm going 85 00:05:27,285 --> 00:05:29,125 to hand things off to Janine and Jacob's 86 00:05:29,125 --> 00:05:31,765 team and they'll walk us through their presentation 87 00:05:31,765 --> 00:05:38,290 here. Yeah, thank you. So there's the agenda. 88 00:05:39,250 --> 00:05:41,330 Let's hit the purpose of the RFP real 89 00:05:41,330 --> 00:05:44,370 quick. Eric, if you can go to that. 90 00:05:44,370 --> 00:05:48,210 So that's that schedule overview. Oh, sorry. Eric, 91 00:05:48,210 --> 00:05:49,729 can you go back to the schedule overview? 92 00:05:52,095 --> 00:05:55,055 Sorry about that. And this is what Eric, 93 00:05:55,215 --> 00:05:58,815 Henry was just speaking to. This schedule overview 94 00:05:58,815 --> 00:06:01,375 is included in the RFP, so you can 95 00:06:01,375 --> 00:06:04,015 see those dates. There is a note underneath 96 00:06:04,015 --> 00:06:06,580 that that indicates, you know, these dates could 97 00:06:06,580 --> 00:06:09,460 change, but for the most part, this is 98 00:06:09,460 --> 00:06:12,180 the solid schedule that Greene County is looking 99 00:06:12,180 --> 00:06:16,180 to follow. Eric, you want you can go 100 00:06:16,180 --> 00:06:19,875 to the next slide. So how we want 101 00:06:19,875 --> 00:06:24,195 to conduct a meeting. So support consultant is 102 00:06:24,195 --> 00:06:29,155 us, Jacob. Greene County, and we will present 103 00:06:29,155 --> 00:06:31,870 the topics listed in the agenda. We wanna 104 00:06:31,870 --> 00:06:34,830 leave thirty minutes at the end for your 105 00:06:34,830 --> 00:06:37,710 questions and answers. So let us get through 106 00:06:37,710 --> 00:06:41,070 the core content. If you have a question, 107 00:06:41,070 --> 00:06:42,750 jot it down, and when we open it 108 00:06:42,750 --> 00:06:46,765 up, we'll certainly respond to those. And as 109 00:06:46,765 --> 00:06:48,605 Eric said, the hand raise function is gonna 110 00:06:48,605 --> 00:06:50,285 help us when we get to that point. 111 00:06:51,645 --> 00:06:54,285 All questions we will be documenting any questions 112 00:06:54,285 --> 00:06:56,845 that are raised here verbally, but you might 113 00:06:56,845 --> 00:06:59,405 notice that in certain instances, we will say, 114 00:06:59,970 --> 00:07:03,010 please submit that in writing, because we know 115 00:07:03,010 --> 00:07:05,090 that that's gonna be information that, you know, 116 00:07:05,090 --> 00:07:07,970 needs to be documented and and pushed back 117 00:07:07,970 --> 00:07:11,570 out through, the response to questions. So just 118 00:07:11,570 --> 00:07:15,170 be prepared for that. Okay. Eric, the next 119 00:07:15,170 --> 00:07:18,905 slide. So purpose of the RFP, Eric Henry 120 00:07:18,905 --> 00:07:21,545 gave a nice summary on that. And just 121 00:07:21,545 --> 00:07:23,305 to really we're and we're not gonna read 122 00:07:23,305 --> 00:07:26,665 all this text, but really focus on key 123 00:07:26,665 --> 00:07:30,985 purposes. So technology solution, Greene County is looking, 124 00:07:31,305 --> 00:07:34,880 for a permitting and plan review technology solution. 125 00:07:34,880 --> 00:07:37,920 That could be one technology that encompasses all 126 00:07:37,920 --> 00:07:40,480 the requirements and the things they're looking for, 127 00:07:40,560 --> 00:07:43,040 or it could be a technology solution that 128 00:07:43,040 --> 00:07:46,625 involves a couple of different technologies. It is 129 00:07:46,625 --> 00:07:49,745 important to be mindful, and there's a technology 130 00:07:49,745 --> 00:07:53,425 diagram included in the RFP, of the existing 131 00:07:53,425 --> 00:07:56,785 technologies that they're working with. In certain instances, 132 00:07:56,785 --> 00:08:01,080 a software such as stages that supports building 133 00:08:01,080 --> 00:08:04,760 regulation, that's in that's staying. And so you'll 134 00:08:04,760 --> 00:08:10,360 notice that there are some requirements around triggering 135 00:08:10,360 --> 00:08:14,360 notifications between those two systems and and then 136 00:08:14,360 --> 00:08:18,385 some. So take in mind that full suite 137 00:08:18,385 --> 00:08:21,025 of software that they currently have in play. 138 00:08:21,745 --> 00:08:24,305 There's a couple of mentions of software that 139 00:08:24,305 --> 00:08:27,425 is optional. So this just indicates that Greene 140 00:08:27,425 --> 00:08:30,705 County is thinking through a few things, about 141 00:08:30,705 --> 00:08:34,360 their technology suite as it as it exists. 142 00:08:34,360 --> 00:08:37,240 And when we're looking for costing of something 143 00:08:37,240 --> 00:08:39,959 like an online phone system, I think is 144 00:08:39,959 --> 00:08:43,480 referenced in there, it's labeled as optional. They're 145 00:08:43,480 --> 00:08:46,385 considering that as part of the solution if 146 00:08:46,385 --> 00:08:48,785 if that's going to improve things for them. 147 00:08:48,785 --> 00:08:51,505 So take that in and be mindful of 148 00:08:51,505 --> 00:08:54,785 those details when you're looking at them. Overall, 149 00:08:55,185 --> 00:08:57,345 they are looking, as Eric said, this one 150 00:08:57,345 --> 00:08:59,720 stop. This is this is a lot about 151 00:08:59,720 --> 00:09:03,240 a key focus is on customer service and, 152 00:09:03,480 --> 00:09:08,200 efficiency and processing permit applications and plan reviews. 153 00:09:08,520 --> 00:09:11,080 And so ease of use on the customer 154 00:09:11,080 --> 00:09:13,735 side, what what the end user has to 155 00:09:13,735 --> 00:09:17,495 interact with simplicity, is a key objective in 156 00:09:17,495 --> 00:09:21,095 what they're looking for. Also, you'll see reference 157 00:09:21,095 --> 00:09:24,695 to smartly presented. So if I'm a customer, 158 00:09:24,695 --> 00:09:26,695 I'm entering what I want to do, what 159 00:09:26,695 --> 00:09:28,830 type of business I want to do at 160 00:09:28,830 --> 00:09:32,430 Greene County. The system through entering of of 161 00:09:32,430 --> 00:09:35,710 few keywords will help present to me the 162 00:09:35,710 --> 00:09:38,670 process I need to follow, the permit applications 163 00:09:38,670 --> 00:09:40,830 I'm I'm going to need to apply for, 164 00:09:41,315 --> 00:09:44,995 the turnaround times that I can expect as 165 00:09:44,995 --> 00:09:49,235 these applications go through internal review. So these 166 00:09:49,394 --> 00:09:53,075 are key objectives that the county is looking 167 00:09:53,075 --> 00:09:55,950 for. And then, of course, on the internal 168 00:09:55,950 --> 00:09:58,750 side, having access to whose court is it 169 00:09:58,750 --> 00:10:01,950 in now. I've reviewed it. I'm sanitary engineering. 170 00:10:01,950 --> 00:10:05,709 I need to now have county engineer do 171 00:10:05,709 --> 00:10:08,465 their thing. So, there are timings of push 172 00:10:08,465 --> 00:10:12,225 notifications. So notifications and supporting that process is 173 00:10:12,225 --> 00:10:15,345 another key objective. The staff are aware of 174 00:10:15,345 --> 00:10:17,745 where things are at and and those turnaround 175 00:10:17,745 --> 00:10:21,259 times and how they're performing in alignment. So 176 00:10:21,259 --> 00:10:24,220 that's an expanded purpose and vision. Eric, you 177 00:10:24,220 --> 00:10:27,180 can go to the next slide. So scoop 178 00:10:27,180 --> 00:10:30,459 of work. So this is included in appendix 179 00:10:30,459 --> 00:10:33,420 b as in boy. Eric, you can move 180 00:10:33,420 --> 00:10:37,115 that past that slide. So boring text, I 181 00:10:37,115 --> 00:10:39,595 know, but just to emphasize what the county 182 00:10:39,595 --> 00:10:41,755 is looking for. So phase one on project 183 00:10:41,755 --> 00:10:44,875 definition, you see a couple of key tasks. 184 00:10:45,035 --> 00:10:46,634 So the scope of work when we lay 185 00:10:46,634 --> 00:10:49,079 this out, we are asking you to present 186 00:10:49,079 --> 00:10:52,279 a proposal that more or less follows what 187 00:10:52,279 --> 00:10:54,680 is being asked for. You'll see a lot 188 00:10:54,680 --> 00:10:58,680 of rigor, in the configuration stage around testing 189 00:10:58,680 --> 00:11:01,959 and training. Those are critical elements because we're 190 00:11:01,959 --> 00:11:06,225 really on cost client adoption, end user adoption, 191 00:11:06,225 --> 00:11:09,105 and ease of use. In the project definition 192 00:11:09,105 --> 00:11:11,265 phase, it's just, you know, setting out that 193 00:11:11,265 --> 00:11:14,145 project management plan. What is your timeline? What 194 00:11:14,145 --> 00:11:17,105 are the key, activities that will be going 195 00:11:17,105 --> 00:11:19,870 on? And a key thing this informs is 196 00:11:19,870 --> 00:11:22,670 you're working with busy people. Whoever selected will 197 00:11:22,670 --> 00:11:25,230 be working with really busy people and they 198 00:11:25,230 --> 00:11:27,230 need to know that schedule in advance of 199 00:11:27,230 --> 00:11:28,990 when their time is going to be needed 200 00:11:28,990 --> 00:11:31,865 so they can plan accordingly. And then, of 201 00:11:31,865 --> 00:11:34,265 course, the kickoff meeting to explain how things 202 00:11:34,265 --> 00:11:37,145 are going to move forward. On the next 203 00:11:37,145 --> 00:11:39,465 slide, we're starting on phase two, which is 204 00:11:39,465 --> 00:11:42,665 really the blueprinting. One thing I really want 205 00:11:42,665 --> 00:11:46,370 to emphasize is Greene County staff, people around 206 00:11:46,370 --> 00:11:48,290 the table that you're that are on this 207 00:11:48,290 --> 00:11:51,250 call, and others did a lot of intense 208 00:11:51,250 --> 00:11:55,090 work to envision what they wanted. And so, 209 00:11:55,650 --> 00:11:58,290 you'll notice in the, right under the the 210 00:11:58,290 --> 00:12:02,764 phase two blueprinting title, it says confirm business 211 00:12:02,764 --> 00:12:06,365 processes. A big difference, and this is, something 212 00:12:06,365 --> 00:12:08,444 to take note of, we are not asking 213 00:12:08,444 --> 00:12:11,180 you to start from scratch and and pull 214 00:12:11,180 --> 00:12:12,940 these people through a bunch of, well, how 215 00:12:12,940 --> 00:12:14,620 would you like it to be set up? 216 00:12:14,620 --> 00:12:16,380 How would you like it to work? They 217 00:12:16,380 --> 00:12:18,380 have done a lot of great work toward 218 00:12:18,380 --> 00:12:21,500 that end already, and it's very detailed business 219 00:12:21,500 --> 00:12:25,195 process diagrams in that appendix b. That is 220 00:12:25,195 --> 00:12:28,875 their vision. It's also been couched that, you 221 00:12:28,875 --> 00:12:30,635 know, this may be your vision. You may 222 00:12:30,635 --> 00:12:33,435 not get a % of of how you 223 00:12:33,435 --> 00:12:36,155 want this to work. It may be 90%. 224 00:12:36,155 --> 00:12:38,075 That's what we're targeting. Right? It's not a 225 00:12:38,075 --> 00:12:41,600 hundred. But nonetheless, that is their vision. So 226 00:12:41,600 --> 00:12:43,680 I've they've gone through a lot of effort 227 00:12:43,680 --> 00:12:45,520 to do this. So I really wanna emphasize 228 00:12:45,520 --> 00:12:47,680 that you're not hitting the you know, from 229 00:12:47,680 --> 00:12:51,360 ground zero, you're starting a leg up. And 230 00:12:51,755 --> 00:12:54,955 what came out, the tech technical the functional 231 00:12:54,955 --> 00:12:57,675 requirements that you see in that Excel spreadsheet 232 00:12:57,675 --> 00:13:01,115 that was included in the proposal package, that 233 00:13:01,115 --> 00:13:04,075 we're asking you to fill out, those functional 234 00:13:04,075 --> 00:13:08,110 requirements are directly related to those business process 235 00:13:08,110 --> 00:13:11,630 diagrams by business process listed, and they are 236 00:13:11,630 --> 00:13:14,910 categorized by permit type or plan type that 237 00:13:14,910 --> 00:13:16,990 is being reviewed. So there is a one 238 00:13:16,990 --> 00:13:19,550 to one alignment there. So those diagrams really 239 00:13:19,550 --> 00:13:23,875 help understand what the county's asking for, from 240 00:13:23,875 --> 00:13:26,675 a vision standpoint, and those functional requirements were 241 00:13:26,675 --> 00:13:29,795 asking you to say, can your technology solution 242 00:13:29,795 --> 00:13:32,355 do this? Is it out of the box? 243 00:13:32,355 --> 00:13:33,955 Is it something that would need to be 244 00:13:33,955 --> 00:13:36,350 created? You know? So they have some sense 245 00:13:36,350 --> 00:13:39,550 of what your solution how many of those 246 00:13:39,550 --> 00:13:42,350 requirements it actually needs. So as part of 247 00:13:42,350 --> 00:13:47,310 blueprinting, that system implementation plan, you know, is 248 00:13:47,470 --> 00:13:50,865 a task creating the that more detailed technology 249 00:13:50,865 --> 00:13:54,065 set of steps, going through the functional requirements, 250 00:13:54,065 --> 00:13:56,545 the business process, and then working with their 251 00:13:56,545 --> 00:14:00,145 IT designated person around to make sure there's 252 00:14:00,145 --> 00:14:05,550 an understanding around data security, any hardware or 253 00:14:05,550 --> 00:14:10,590 interfaces to existing software. So, is that blueprinting 254 00:14:10,590 --> 00:14:12,510 phase, a lot of work, but there is 255 00:14:12,510 --> 00:14:16,750 also a starting point. On the next slide, 256 00:14:16,750 --> 00:14:19,230 we show an example of those detailed business 257 00:14:19,230 --> 00:14:21,515 process diagrams. I know you can't read that 258 00:14:21,515 --> 00:14:23,195 on the slide, but they are in the 259 00:14:23,195 --> 00:14:26,635 RFP. Again, you know, you'll kind of notice 260 00:14:26,635 --> 00:14:29,515 workflows, and I know technology people are used 261 00:14:29,515 --> 00:14:32,235 to looking at these. And you'll see the 262 00:14:32,235 --> 00:14:36,040 existing systems reference as well as a generic, 263 00:14:36,280 --> 00:14:39,640 blue cylinder data box that is labeled One 264 00:14:39,640 --> 00:14:43,720 Stop. That's the technology solution. And so, that, 265 00:14:43,720 --> 00:14:45,560 we're seeing what do we want One Stop 266 00:14:45,560 --> 00:14:49,805 to do at a particular step. Okay. Next 267 00:14:49,805 --> 00:14:54,605 slide. Then, during phase three, that realization phase, 268 00:14:54,605 --> 00:14:57,324 the the confirmation of the plan of action, 269 00:14:57,485 --> 00:15:00,045 the what what what the team the proposal 270 00:15:00,045 --> 00:15:01,725 team is going to be doing to build 271 00:15:01,725 --> 00:15:04,290 out. Now you're starting to realize and set 272 00:15:04,290 --> 00:15:07,970 up those configurations. Again, you'll you'll see a 273 00:15:07,970 --> 00:15:09,970 lot of reference to and they're in the 274 00:15:09,970 --> 00:15:12,370 scope of work in that appendix b. It 275 00:15:12,370 --> 00:15:15,570 describes what each of those testing steps entail. 276 00:15:16,209 --> 00:15:18,130 But for those of you who are technology, 277 00:15:18,130 --> 00:15:20,035 it's pretty best practice. Right? But a lot 278 00:15:20,035 --> 00:15:22,835 of emphasis on testing, making sure data's flowing 279 00:15:22,835 --> 00:15:25,635 because we've got several systems at play here. 280 00:15:26,115 --> 00:15:29,715 And then training too. We're not looking for 281 00:15:29,715 --> 00:15:32,835 a very simple one day training. This is 282 00:15:32,835 --> 00:15:36,040 how you do it. But know that there's 283 00:15:36,040 --> 00:15:39,160 a lot of, people not only on the 284 00:15:39,160 --> 00:15:43,320 customer side, but on the, internal side that 285 00:15:43,320 --> 00:15:47,480 come from different groups. So, the training can't 286 00:15:47,480 --> 00:15:49,560 just be this quick one day. There's there's 287 00:15:49,560 --> 00:15:51,695 some kind of focused training that needs to 288 00:15:51,695 --> 00:15:54,735 go on. Again, because the the long term 289 00:15:54,735 --> 00:15:57,615 interest is that they've got a solid technology 290 00:15:57,615 --> 00:16:02,095 solution that's accepted and used and loved by 291 00:16:02,095 --> 00:16:10,530 staff. Okay. Next one down. And then go 292 00:16:10,530 --> 00:16:13,410 live. Of course, being there when things go 293 00:16:13,410 --> 00:16:17,090 live, be there for when, questions are being 294 00:16:17,090 --> 00:16:20,745 asked. And, in particular, in the costing sheet, 295 00:16:20,745 --> 00:16:23,705 you'll see, there's an interest in knowing the, 296 00:16:23,945 --> 00:16:26,905 just up to five years, what those annual, 297 00:16:27,065 --> 00:16:30,585 five years cost would be, to provide the 298 00:16:30,585 --> 00:16:35,649 maintenance and support. Alright. Next one. We're getting 299 00:16:35,649 --> 00:16:38,529 to questions, guys. Okay. Last section that I'm 300 00:16:38,529 --> 00:16:40,370 gonna talk through, and then we'll toss it 301 00:16:40,370 --> 00:16:43,089 back. Go ahead, Eric. So just, this is 302 00:16:43,089 --> 00:16:46,850 in the RFP itself, but just, verbalizing is 303 00:16:47,105 --> 00:16:50,145 there's the address for where the hard copy 304 00:16:50,145 --> 00:16:53,105 proposal should be submitted along with the USB 305 00:16:53,105 --> 00:16:55,665 flash drive. So you'll see they're looking for 306 00:16:55,665 --> 00:16:59,025 five hard copies. That includes that separate Microsoft 307 00:16:59,025 --> 00:17:02,385 Excel spreadsheet where you are responding yes, no, 308 00:17:03,720 --> 00:17:06,359 maybe with configuration, those types of things to 309 00:17:06,359 --> 00:17:09,400 each of those requirements, and then an electronic 310 00:17:09,400 --> 00:17:13,559 copy. So both the proposal itself and that. 311 00:17:13,560 --> 00:17:15,640 And then the cost proposal, they want in 312 00:17:15,640 --> 00:17:22,815 a separate field envelope. Alright, Eric. So the 313 00:17:22,815 --> 00:17:28,255 proposal requirements, you're used to seeing these categories. 314 00:17:28,575 --> 00:17:31,535 There are indications of page limits, so it 315 00:17:31,535 --> 00:17:34,140 gives some sense of detail on what's being 316 00:17:34,140 --> 00:17:39,580 looked for. Just clear writing, nailing the what 317 00:17:39,580 --> 00:17:41,900 is being asked for and and providing that 318 00:17:41,900 --> 00:17:46,300 exactly is a key. Right? Simplicity and clarity 319 00:17:46,300 --> 00:17:49,655 is is is gonna be the key. You'll 320 00:17:49,655 --> 00:17:52,695 notice on the e, item e, the proposed 321 00:17:52,695 --> 00:17:56,135 technology solution, that's pretty short, two pages. It's 322 00:17:56,135 --> 00:17:58,855 a basic statement of, okay, are the needs 323 00:17:58,855 --> 00:18:01,655 that we have. What do you propose from 324 00:18:01,655 --> 00:18:03,575 a technology? You may be teaming up with 325 00:18:03,575 --> 00:18:07,100 another technology provider, or you may have the 326 00:18:07,100 --> 00:18:09,740 whole enchilada in one suite. But the point 327 00:18:09,740 --> 00:18:12,220 is is is that section is to say, 328 00:18:12,220 --> 00:18:14,700 what is it? We're not looking for a 329 00:18:14,700 --> 00:18:17,340 bunch of salesy material. We know sometimes people 330 00:18:17,340 --> 00:18:19,100 will go their route of in a section 331 00:18:19,100 --> 00:18:22,355 like that, you know, throwing in 10 brochures. 332 00:18:22,434 --> 00:18:24,355 That's not what we're looking for. We're looking 333 00:18:24,355 --> 00:18:27,075 for simplicity and clarity. Please state exactly what 334 00:18:27,075 --> 00:18:29,715 you're proposing. And then it's in that item 335 00:18:29,715 --> 00:18:32,835 f where we want you to detail out 336 00:18:32,835 --> 00:18:35,350 the approach. And, again, the the key nugget 337 00:18:35,350 --> 00:18:37,750 here is the approach is the scope of 338 00:18:37,750 --> 00:18:40,950 work that's detailed out in appendix b as 339 00:18:40,950 --> 00:18:43,590 in boy. So if you follow that scope 340 00:18:43,590 --> 00:18:48,565 of work, obviously, you're professionals. There are variations 341 00:18:48,565 --> 00:18:51,764 from that, which is fine and understandable. But 342 00:18:51,764 --> 00:18:54,164 for the most part, you have the messaging 343 00:18:54,164 --> 00:18:58,485 around intense testing, good training. Those are key 344 00:18:58,485 --> 00:19:04,300 nuggets. Okay? Almost there. Okay. The cost proposal 345 00:19:04,300 --> 00:19:08,860 sheet, which is appendix a, you'll notice just 346 00:19:08,860 --> 00:19:10,700 out of the gate that in the table 347 00:19:10,700 --> 00:19:14,225 itself, each of the, from the scope of 348 00:19:14,225 --> 00:19:16,385 work, each of the numbered scope of work 349 00:19:16,385 --> 00:19:19,345 items are listed there. The titles are listed 350 00:19:19,345 --> 00:19:22,145 there, and that's where we're emphasizing, please follow 351 00:19:22,145 --> 00:19:24,785 this approach. Right? How much would it cost 352 00:19:24,785 --> 00:19:26,305 you to get through that, you know, the 353 00:19:26,305 --> 00:19:30,710 estimate, any expense costs associated? On the expense 354 00:19:30,710 --> 00:19:33,429 cost, you know, if there's a lot of 355 00:19:33,429 --> 00:19:35,429 work you can do remotely and you're not 356 00:19:35,429 --> 00:19:37,830 having to travel in, especially if you're not 357 00:19:37,830 --> 00:19:40,710 local, that's gonna, you know, weigh well. So 358 00:19:40,710 --> 00:19:42,945 you're balancing out that need of being in 359 00:19:42,945 --> 00:19:45,025 person and the value of that versus work 360 00:19:45,025 --> 00:19:48,945 you can be doing offline. And then on, 361 00:19:49,105 --> 00:19:50,865 what's flashed up on the screen is the 362 00:19:50,865 --> 00:19:54,785 second page of that. You'll see reference to 363 00:19:54,785 --> 00:19:59,539 the interpieces, a potential for data migration if 364 00:19:59,539 --> 00:20:01,460 the decision is to get rid of one 365 00:20:01,460 --> 00:20:05,460 of their existing technologies, because this new technology 366 00:20:05,460 --> 00:20:08,260 solution might place this. I say that with 367 00:20:08,260 --> 00:20:10,580 the disclaimer. There has been no decision towards 368 00:20:10,580 --> 00:20:13,445 that end. It's just a potential, and we're 369 00:20:13,445 --> 00:20:18,884 leaving options open where where decisions still need 370 00:20:18,884 --> 00:20:22,164 to be made. There are references in the 371 00:20:22,164 --> 00:20:27,080 interfaces two to three non Greene County, so 372 00:20:27,080 --> 00:20:32,440 statewide systems where different groups or divisions at 373 00:20:32,440 --> 00:20:34,840 Greene County must interact with. You've got a 374 00:20:34,840 --> 00:20:38,525 system like TOCAY. You've got the health department 375 00:20:38,525 --> 00:20:41,485 uses HDIS. These are statewide systems. They are 376 00:20:41,485 --> 00:20:44,605 not going away. So, you'll see referenced and 377 00:20:44,605 --> 00:20:47,885 described in the RFP. And we've already had 378 00:20:47,885 --> 00:20:52,080 conversations with those entities. But a a very 379 00:20:52,080 --> 00:20:56,320 simple data exchange, whether that's a direct integration 380 00:20:56,640 --> 00:20:59,680 or, a data export from those systems where 381 00:20:59,680 --> 00:21:02,480 someone manually is bringing that into the new 382 00:21:02,480 --> 00:21:05,294 technology system on the Greene County side, which 383 00:21:05,294 --> 00:21:08,654 that latter is the more practical of what's 384 00:21:08,654 --> 00:21:10,495 gonna happen based on what we know. Those 385 00:21:10,495 --> 00:21:14,335 statewide systems don't want Greene County systems, you 386 00:21:14,335 --> 00:21:16,975 know, feeding information in and out and exchanging. 387 00:21:16,975 --> 00:21:20,159 So that data export process is is the, 388 00:21:20,480 --> 00:21:25,279 route that is most likely. So but please 389 00:21:25,279 --> 00:21:28,799 look at those costing things as, let's put 390 00:21:28,799 --> 00:21:30,320 them in here as if it were an 391 00:21:30,320 --> 00:21:32,880 integration on a couple of those data points 392 00:21:33,045 --> 00:21:36,965 just for cost comparison and as prompted there. 393 00:21:38,005 --> 00:21:40,405 I'm probably confused that just read what's written 394 00:21:40,405 --> 00:21:42,245 there, which is please give us a cost 395 00:21:42,245 --> 00:21:44,405 for an integration. But, again, for your back 396 00:21:44,405 --> 00:21:47,205 pocket, most likely, will be a manual export 397 00:21:47,205 --> 00:21:54,460 import. Okay. Almost done, Eric. Okay. The the, 398 00:21:54,780 --> 00:21:58,220 functional and technical, requirements response work, which is 399 00:21:58,220 --> 00:22:03,435 that Excel spreadsheet. Again, it supports the listing 400 00:22:03,435 --> 00:22:06,395 of requirements as defined by Greene County staff. 401 00:22:07,435 --> 00:22:10,715 We would like you to submit that, you 402 00:22:10,715 --> 00:22:13,275 know, along with your proposal that's helping with 403 00:22:13,275 --> 00:22:15,835 the evaluation that the voting members are gonna 404 00:22:15,835 --> 00:22:18,750 be going through. It doesn't count on your 405 00:22:18,750 --> 00:22:21,390 proposal page limit, and you can see the 406 00:22:21,390 --> 00:22:23,869 number of different types listed there. So, functional, 407 00:22:24,190 --> 00:22:26,750 how do we want it to behave? The 408 00:22:26,750 --> 00:22:32,995 notification, routing, you know, display performance metrics against 409 00:22:32,995 --> 00:22:35,794 processing time, those types of things. On the 410 00:22:35,794 --> 00:22:39,475 technical requirements, that was heavily led by Greene 411 00:22:39,475 --> 00:22:44,210 County IT, to help describe the technology environment, 412 00:22:44,210 --> 00:22:46,929 any data and security requirements, those types of 413 00:22:46,929 --> 00:22:49,730 things. And you'll see that categorization when you 414 00:22:49,730 --> 00:22:53,809 look at that workbook. Again, there's two worksheets, 415 00:22:53,809 --> 00:23:02,655 functional requirements, technical requirements. Okay? You can't read 416 00:23:02,655 --> 00:23:04,735 that. That's just an image of what it 417 00:23:04,735 --> 00:23:06,895 is. So you have the requirements listed on 418 00:23:06,895 --> 00:23:10,015 the left, the category that it falls into, 419 00:23:10,015 --> 00:23:12,390 and you're filling out those four blue columns 420 00:23:12,390 --> 00:23:15,270 with, and there's some acronyms there that that 421 00:23:15,270 --> 00:23:18,710 indicate, yes, the my technology solution can wholly 422 00:23:18,710 --> 00:23:22,870 meet this. No problem. Or it can't. Right? 423 00:23:22,870 --> 00:23:26,310 So and we recognize that a % of 424 00:23:26,310 --> 00:23:29,645 everything Greene County has envisioned may or may 425 00:23:29,645 --> 00:23:37,645 not be possible. Alright? The proposal evaluation criteria, 426 00:23:37,645 --> 00:23:40,950 this is directly from the RFP. So we're 427 00:23:40,950 --> 00:23:43,990 quality of the proposal references. Where have you 428 00:23:43,990 --> 00:23:46,309 done something similar? We know it may not 429 00:23:46,309 --> 00:23:50,629 be exactly similar, but, those references are important. 430 00:23:51,510 --> 00:23:55,190 Your just general qualifications and experience. Is this 431 00:23:55,190 --> 00:23:57,665 your first time ever doing this, or have 432 00:23:57,665 --> 00:24:00,065 you done this, you know, 5,000,000 times kind 433 00:24:00,065 --> 00:24:03,425 of a thing? That ability to meet desired 434 00:24:03,425 --> 00:24:06,545 functionality, again, that workbook that has the functional 435 00:24:06,545 --> 00:24:11,610 and technical requirements, that's, you know, an important 436 00:24:12,570 --> 00:24:15,850 extremely important consideration for the voting members. And 437 00:24:15,850 --> 00:24:17,929 then we've got the cost listed out as 438 00:24:17,929 --> 00:24:21,690 well. And I think that's probably the last 439 00:24:21,690 --> 00:24:26,315 slide for me. Eric Henry, I'm gonna toss 440 00:24:26,315 --> 00:24:28,155 it back to you if you've got someone 441 00:24:28,155 --> 00:24:30,475 there who can do this last section on 442 00:24:30,475 --> 00:24:32,235 the contract forms and then we can open 443 00:24:32,235 --> 00:24:34,395 it up to q and a. I I 444 00:24:34,395 --> 00:24:36,315 don't believe we have anyone from legal on 445 00:24:36,315 --> 00:24:38,640 the call. All I'll say about this is 446 00:24:38,640 --> 00:24:41,840 these are required documents for your submittal of 447 00:24:41,840 --> 00:24:44,560 of your bid. If you have any questions, 448 00:24:44,560 --> 00:24:45,920 I'd ask that you send those in writing 449 00:24:45,920 --> 00:24:47,360 so we can have our legal team go 450 00:24:47,360 --> 00:24:50,080 ahead and review them. Then I'll put out 451 00:24:50,080 --> 00:24:52,240 some sort of FAQ available to all to 452 00:24:52,240 --> 00:24:55,625 make sure that those answers are able to 453 00:24:55,625 --> 00:24:58,505 be reviewed by everyone once spent. So that's 454 00:24:58,505 --> 00:25:00,504 all I have to say about that section 455 00:25:00,585 --> 00:25:09,540 time being. Respond, I mean, about that. I 456 00:25:09,540 --> 00:25:10,980 don't know if Jeanine, you wanna go over 457 00:25:10,980 --> 00:25:14,020 that or I feel like it's self explanatory, 458 00:25:14,020 --> 00:25:18,020 but I'm happy to encourage questions, comments on 459 00:25:18,020 --> 00:25:24,934 this. Okay. Alright. Well, let's since that's a 460 00:25:24,934 --> 00:25:26,934 nice segue, let's go ahead and open it 461 00:25:26,934 --> 00:25:30,934 up for questions. Think Eric, Hob Habermeer, if 462 00:25:30,934 --> 00:25:32,934 you can, do that, we can open it 463 00:25:32,934 --> 00:25:37,100 up. So that was a lot. It may 464 00:25:37,100 --> 00:25:39,900 rest, where let's go ahead and and open 465 00:25:39,900 --> 00:25:42,539 it up for questions. And as, Eric Henry 466 00:25:42,539 --> 00:25:44,620 suggested, if you don't mind using your hand 467 00:25:44,620 --> 00:25:46,780 raise, that'll give some sense of order to 468 00:25:46,780 --> 00:25:57,395 any questions. Let's see. And Eric Habermeyer, you 469 00:25:57,395 --> 00:25:59,475 can help me. Why am I not seeing 470 00:25:59,475 --> 00:26:05,409 the hand raised? Okay. Who's that? Taylor Roderson? 471 00:26:05,409 --> 00:26:08,369 Yeah. Thank you. Can you hear me okay? 472 00:26:08,769 --> 00:26:13,010 Yep. Yes. We can hear you. Perfect. So 473 00:26:13,010 --> 00:26:15,970 I'm looking at it's mentioned a couple of 474 00:26:15,970 --> 00:26:20,825 times the interfaces that are required and optional, 475 00:26:21,305 --> 00:26:24,025 and I'm specifically looking at page 18 where 476 00:26:24,025 --> 00:26:27,304 it has them, labeled out in a table. 477 00:26:27,945 --> 00:26:29,865 I was curious, and I can kinda ask 478 00:26:29,865 --> 00:26:31,919 these questions one by one, but I was 479 00:26:31,919 --> 00:26:35,039 hoping to get a better sense of exactly 480 00:26:35,039 --> 00:26:38,240 what each of these systems is used for 481 00:26:38,240 --> 00:26:42,559 today. And secondarily to that question would be 482 00:26:42,720 --> 00:26:46,355 if the solution that we're bidding on could 483 00:26:46,355 --> 00:26:49,955 help consolidate some of these other systems. Is 484 00:26:49,955 --> 00:26:51,955 that something you'd like us to propose as 485 00:26:51,955 --> 00:26:54,914 well, or is the county looking to definitely 486 00:26:55,155 --> 00:26:57,155 keep all of those in place and just 487 00:26:57,155 --> 00:27:02,670 integrate? So sorry. Long question. It's a great 488 00:27:02,670 --> 00:27:05,150 question. One thing that popped into my mind, 489 00:27:05,150 --> 00:27:07,150 Eric Henry, I'm stalling for time because I'm 490 00:27:07,150 --> 00:27:08,990 gonna toss it to you as the official 491 00:27:08,990 --> 00:27:12,095 kind of take the questions and farm it 492 00:27:12,095 --> 00:27:14,575 out. But, Eric Coppermeyer, if you don't mind, 493 00:27:14,575 --> 00:27:16,735 I think, having the RFP, maybe we could 494 00:27:16,735 --> 00:27:19,294 even pull up that page 18 might be 495 00:27:19,294 --> 00:27:23,214 helpful. Yep. I'm pulling it up right now. 496 00:27:24,014 --> 00:27:28,480 Okay. And, Taylor, to oh, sorry. There is 497 00:27:28,480 --> 00:27:30,640 a diagram that I think is helpful. I 498 00:27:30,640 --> 00:27:34,240 think it's figure two one that shows the 499 00:27:34,240 --> 00:27:37,840 different technologies in play, and there's some commentary 500 00:27:37,840 --> 00:27:40,674 about what type of information is desired to 501 00:27:40,674 --> 00:27:43,235 be shared. Is that all the details at 502 00:27:43,235 --> 00:27:45,315 the moment? No. But it gives that high 503 00:27:45,315 --> 00:27:49,554 level. So anyway, Eric Henry, did I spell 504 00:27:49,554 --> 00:27:51,960 enough for you? So for the first part 505 00:27:51,960 --> 00:27:53,640 of your question, I would leave that to 506 00:27:53,640 --> 00:27:58,520 the individual departments to answer specifically. The second 507 00:27:58,520 --> 00:28:00,280 part, I'm gonna give you kind of a 508 00:28:00,280 --> 00:28:03,240 nuanced answer. It's just probably not super helpful, 509 00:28:03,240 --> 00:28:06,704 but in a perfect world, consolidation would happen. 510 00:28:07,024 --> 00:28:10,544 That being said, it feels like it's it's 511 00:28:10,544 --> 00:28:13,904 so burdensome and so complicated that it's unattainable, 512 00:28:13,904 --> 00:28:17,370 but I'd be happy to look at proposals 513 00:28:17,370 --> 00:28:19,850 that have that function in there. But it's 514 00:28:19,850 --> 00:28:21,850 not something that I'm requiring at this time, 515 00:28:21,850 --> 00:28:26,330 if that makes sense. So if I'm hearing 516 00:28:26,330 --> 00:28:29,930 that correctly, you know, being able to interface, 517 00:28:29,930 --> 00:28:31,690 you would want us to outline but would 518 00:28:31,690 --> 00:28:35,095 also be open to a recommendation where we 519 00:28:35,095 --> 00:28:40,294 may be able to consolidate. Correct. Okay. Yeah. 520 00:28:40,294 --> 00:28:50,190 That's helpful. And I do see the 2.1, 521 00:28:50,190 --> 00:28:52,110 so that's really helpful as well. But if 522 00:28:52,110 --> 00:28:55,150 any of the departments have any other detail 523 00:28:55,150 --> 00:28:56,990 that would be helpful for us on the 524 00:28:56,990 --> 00:29:02,455 different systems, definitely open to hearing that. I 525 00:29:02,455 --> 00:29:04,855 don't put you on the spot. What do 526 00:29:04,855 --> 00:29:08,215 you I I I don't. Okay. We'll start 527 00:29:08,215 --> 00:29:09,895 with the media room that we have here, 528 00:29:09,895 --> 00:29:11,015 then we'll open it up to the people 529 00:29:11,015 --> 00:29:14,215 on the call. So go to Randy with 530 00:29:14,215 --> 00:29:17,575 sanitary first. Yeah. With sanitary, we use the 531 00:29:17,575 --> 00:29:24,510 Cityworks. CityWorks is our main AMS asset management 532 00:29:24,510 --> 00:29:27,070 system. We have the add on for the 533 00:29:27,070 --> 00:29:31,795 PLL for all of our permitting, and all 534 00:29:31,795 --> 00:29:34,675 of our historical permits are listed or are 535 00:29:34,675 --> 00:29:37,795 contained in that software. So that is a 536 00:29:37,795 --> 00:29:44,380 very vital piece of, history for us. While 537 00:29:44,380 --> 00:29:47,660 it is listed as an optional, someone's going 538 00:29:47,660 --> 00:29:49,180 to have to make a very good case 539 00:29:49,180 --> 00:29:55,020 to me to move away from it. I 540 00:29:55,785 --> 00:29:57,705 that's not going to be a decision that's 541 00:29:57,705 --> 00:30:00,745 made likely. I'll I'll just say that. We 542 00:30:00,745 --> 00:30:02,665 spent too much time and effort getting where 543 00:30:02,665 --> 00:30:05,065 we're at. It's gonna have to be a 544 00:30:05,065 --> 00:30:07,305 very great solution to move me away from 545 00:30:07,305 --> 00:30:11,490 it. So I do wanna make that comment. 546 00:30:11,490 --> 00:30:13,170 Now Tokay is the other one that we 547 00:30:13,170 --> 00:30:17,410 utilize that's on this list. That's our backflow 548 00:30:17,410 --> 00:30:21,425 prevention system. We keep track of all the 549 00:30:21,425 --> 00:30:28,065 backflow devices in our system. Again, that's a 550 00:30:28,065 --> 00:30:29,985 software that we've just we spent a lot 551 00:30:29,985 --> 00:30:32,305 of time getting up and running. If there's 552 00:30:32,305 --> 00:30:35,520 another solution, I guess we'd be we'd entertain 553 00:30:35,520 --> 00:30:38,880 it. But, again, it has it would have 554 00:30:38,880 --> 00:30:42,400 to have all of the abilities that that 555 00:30:42,400 --> 00:30:44,799 software has it that we're used to and 556 00:30:44,799 --> 00:30:48,765 our plumbers are used to before we would 557 00:30:48,765 --> 00:30:56,045 consider moving. Deandra? Sure. So for regional planning, 558 00:30:56,045 --> 00:30:58,205 we don't directly work with any of these 559 00:30:58,205 --> 00:31:01,245 interfaces aside from GIS, but we use that 560 00:31:01,245 --> 00:31:05,700 more for research purposes and for zoning research 561 00:31:05,700 --> 00:31:08,260 and helping our people who call us with 562 00:31:08,260 --> 00:31:10,900 questions on that. The only thing that we 563 00:31:10,900 --> 00:31:14,340 would be looking for directly is the online 564 00:31:14,340 --> 00:31:16,980 payment system because right now, we don't have 565 00:31:16,980 --> 00:31:20,445 anything. We only take cash and checks at 566 00:31:20,445 --> 00:31:22,125 the moment, so that's something that other departments 567 00:31:22,125 --> 00:31:26,605 have obviously modernized on, and that's something we're 568 00:31:26,605 --> 00:31:31,500 really gonna need assistance with. Awesome. Thank you. 569 00:31:32,060 --> 00:31:33,020 I'm trying to think off the top of 570 00:31:33,020 --> 00:31:35,340 my head. So let's go with public health. 571 00:31:35,500 --> 00:31:40,860 Chad. Chadwick? Yeah. Chadwick here. We utilize the 572 00:31:40,860 --> 00:31:44,940 program known as HDIS. That's health district information 573 00:31:44,940 --> 00:31:50,164 systems. It's a very old, archaic database program 574 00:31:51,045 --> 00:31:54,485 that encompasses just about everything that happens at 575 00:31:54,485 --> 00:31:57,605 a health district from environmental to community health, 576 00:31:58,165 --> 00:32:03,500 billing, receiving, tracking time, and mileage, all sorts 577 00:32:03,500 --> 00:32:07,820 of things. Despite its age, we are not 578 00:32:07,820 --> 00:32:11,100 looking for a replacement within the scope of 579 00:32:11,100 --> 00:32:15,654 this of this proposal. Because it is so 580 00:32:15,654 --> 00:32:20,695 old and somewhat sensitive, we want an export 581 00:32:20,695 --> 00:32:24,455 only function with HDIS. That is we send 582 00:32:24,455 --> 00:32:29,095 out our plumbing information into the one stop 583 00:32:29,095 --> 00:32:32,830 shop database that we're proposing here, but it 584 00:32:32,830 --> 00:32:37,310 would not be two way. Yeah. Sorry. I'm 585 00:32:37,310 --> 00:32:39,070 gonna chime in here. This is Janine. And 586 00:32:39,070 --> 00:32:42,110 that's indicated in the RFP as you just 587 00:32:42,110 --> 00:32:44,510 said. Right? And I'm saying this for all 588 00:32:44,510 --> 00:32:48,535 the proposers. Tokay that was referenced by Randy 589 00:32:48,535 --> 00:32:52,055 Gilbert, which is the backflow prevention, that is 590 00:32:52,055 --> 00:32:54,295 not intended to go away. It's just the 591 00:32:54,295 --> 00:32:59,335 export activity. HDIS is another system that's used 592 00:32:59,335 --> 00:33:02,539 at the state level that's not going away, 593 00:33:02,860 --> 00:33:07,500 as well as a system called SWPPP. You'll 594 00:33:07,500 --> 00:33:11,180 see that reference. That's a statewide, you know, 595 00:33:11,180 --> 00:33:13,740 system as well. So, again, with those three 596 00:33:13,740 --> 00:33:17,975 in particular, there's no replacement of that functionality 597 00:33:17,975 --> 00:33:27,015 desired. Thank you. Let's go with Prasanna, are 598 00:33:27,015 --> 00:33:29,400 you there for the accounting engineer? Yeah. I 599 00:33:29,400 --> 00:33:31,880 am. Yeah. I just like to reiterate what 600 00:33:31,880 --> 00:33:34,360 Janine just said, which is that SwiftTrack is 601 00:33:34,360 --> 00:33:37,400 definitely something that we cannot replace. We're not 602 00:33:37,400 --> 00:33:41,560 looking to replace. It's integral to what we 603 00:33:41,560 --> 00:33:43,560 do with our storm water, and it does 604 00:33:43,560 --> 00:33:45,284 an excellent excellent job with that. So we're 605 00:33:45,284 --> 00:33:47,605 gonna go ahead and keep that the way 606 00:33:47,605 --> 00:33:51,684 that it is. Apia is newer for us 607 00:33:52,005 --> 00:33:54,325 and we are really liking the way that 608 00:33:54,325 --> 00:33:57,924 it works. So we don't need to have 609 00:33:57,924 --> 00:34:04,970 it replaced. But Apia is something that we 610 00:34:04,970 --> 00:34:07,290 would consider if necessary, if someone had something 611 00:34:07,290 --> 00:34:12,725 better out there. But it's working right now. 612 00:34:13,045 --> 00:34:18,165 So that's about it. Fantastic. And last, certainly 613 00:34:18,165 --> 00:34:22,165 not least, Al of the building department. Yeah. 614 00:34:22,165 --> 00:34:25,285 Sage is, we're committed to that program. It's 615 00:34:25,285 --> 00:34:31,659 our permit tracking system, plan review, also keeps 616 00:34:31,659 --> 00:34:35,099 track of all our inspections. So, we're well 617 00:34:35,099 --> 00:34:39,260 invested in that. We like it, and we 618 00:34:39,260 --> 00:34:43,465 wanna keep it. Although, I do wanna keep 619 00:34:43,465 --> 00:34:47,145 it open mind just in case there's something 620 00:34:47,145 --> 00:34:50,105 else out there. But, you know, that would 621 00:34:50,105 --> 00:34:52,744 be pretty exceptional for us to give up 622 00:34:52,744 --> 00:34:56,860 on stages. And if anybody has So let 623 00:34:56,860 --> 00:34:59,100 me let me do a summary here for 624 00:34:59,100 --> 00:35:01,500 people on the phone who are, like, wait. 625 00:35:01,500 --> 00:35:04,620 What's going on? There's, like, existing plan review, 626 00:35:04,620 --> 00:35:07,260 permitting systems at certain and this is in 627 00:35:07,260 --> 00:35:09,660 the RFP, but we're just verbalizing. You've got 628 00:35:09,865 --> 00:35:12,985 building regulation. Al just spoke and he spoke 629 00:35:12,985 --> 00:35:16,025 about stages, and that's indicated as something that 630 00:35:16,025 --> 00:35:19,305 is not going away in the RFP. Stages 631 00:35:19,305 --> 00:35:24,105 currently only handle plan, review and permitting tracking 632 00:35:24,105 --> 00:35:27,920 for building regulation. The challenge is is that 633 00:35:27,920 --> 00:35:32,640 other divisions who need communication and coordination and 634 00:35:32,640 --> 00:35:35,680 and process flow to be supported as a 635 00:35:35,680 --> 00:35:38,640 whole unit, is the county and these divisions 636 00:35:38,640 --> 00:35:42,704 working together, a system like Sage's is not 637 00:35:42,704 --> 00:35:47,105 currently supporting them. Similarly, when Randy Gilbert over 638 00:35:47,105 --> 00:35:50,464 sanitary engineering was describing his use of Cityworks 639 00:35:50,464 --> 00:35:53,025 for their asset management, that is not going 640 00:35:53,025 --> 00:35:58,380 away. They're using, in to a a certain 641 00:35:58,380 --> 00:36:01,340 degree, the PLL module of CityWorks. But, again, 642 00:36:01,340 --> 00:36:04,300 it's just sanitary engineering. And you heard Randy 643 00:36:04,300 --> 00:36:07,494 say, and it's labeled as optional. If the 644 00:36:07,494 --> 00:36:11,335 new technology solution that we're asking for through 645 00:36:11,335 --> 00:36:15,895 this RFP, does a with BAM job, right, 646 00:36:15,895 --> 00:36:18,695 and could convince the Randy Gilbert and sanitary 647 00:36:18,695 --> 00:36:22,910 engineering to release the CityWorks PLL component, then 648 00:36:22,910 --> 00:36:25,470 that's what happens or vice versa. CityWorks PLL 649 00:36:25,470 --> 00:36:28,349 is proposed to support larger divisions. I know 650 00:36:28,349 --> 00:36:30,670 we got some CityWorks people. So you gotta 651 00:36:30,670 --> 00:36:33,234 think of that, you know, it's the challenge 652 00:36:33,234 --> 00:36:35,875 is it's being used, stages and both Cityworks 653 00:36:35,875 --> 00:36:38,835 are being used by single group when it 654 00:36:38,835 --> 00:36:41,635 needs to support all their groups or a 655 00:36:41,635 --> 00:36:47,000 whole new technology solution is in play. So 656 00:36:47,000 --> 00:36:49,720 that's kind of the big overview if you 657 00:36:49,720 --> 00:36:53,000 hear people saying my plan in permitting review 658 00:36:53,000 --> 00:36:57,400 software is not going away because it's already 659 00:36:57,400 --> 00:37:03,705 supporting me. Did that confuse the matter or 660 00:37:03,865 --> 00:37:08,505 bring clarity? I think that was really helpful. 661 00:37:08,505 --> 00:37:10,585 I think all the feedback is helpful in 662 00:37:10,585 --> 00:37:15,299 understanding where each department is. So thank you 663 00:37:15,299 --> 00:37:21,460 very much. Looks like we have the next 664 00:37:21,460 --> 00:37:30,035 question from Matthew. Yeah. Hey. Matthew here from 665 00:37:30,035 --> 00:37:35,075 NV5 Geospatial. Out of curiosity, will Jacobs be, 666 00:37:35,715 --> 00:37:41,450 providing a proposal to this RFP? No. We 667 00:37:41,450 --> 00:37:45,530 are we we are not. We're a partner 668 00:37:45,530 --> 00:37:49,450 with Greene County in getting the RFP ready 669 00:37:49,450 --> 00:37:54,635 in alignment with their needs. Our role on, 670 00:37:56,235 --> 00:38:00,955 the implementation phase of it is is TBD, 671 00:38:01,275 --> 00:38:03,435 but but if there is a role there, 672 00:38:03,435 --> 00:38:06,309 we would be helping to manage the implementation 673 00:38:06,309 --> 00:38:09,109 and serve as a gatekeeper to answer questions, 674 00:38:09,109 --> 00:38:13,190 those types of things. Okay. Great. Thank you. 675 00:38:27,025 --> 00:38:34,900 Other questions? This is Taylor again, if it's 676 00:38:34,900 --> 00:38:38,180 okay. I had one more. The RFP points 677 00:38:38,180 --> 00:38:41,540 to 15 I think it was 15 unique 678 00:38:41,540 --> 00:38:46,555 dashboards. Are there specific data points and dashboards 679 00:38:46,555 --> 00:38:49,675 that the county is referencing for those 15 680 00:38:49,914 --> 00:38:52,714 or just looking for the ability to create 681 00:38:52,714 --> 00:38:59,450 custom dashboards? Great question. So, yes. So think 682 00:38:59,450 --> 00:39:02,970 of the end user that 15 number is 683 00:39:02,970 --> 00:39:06,730 up to, I believe that's the language, but 684 00:39:06,730 --> 00:39:09,305 that's the intent anyway. Think of the end 685 00:39:09,305 --> 00:39:11,865 users within the county. So you have, you 686 00:39:11,865 --> 00:39:17,865 know, executive leadership is interested in tracking metrics. 687 00:39:17,865 --> 00:39:19,785 How are we doing? In particular, are we 688 00:39:19,785 --> 00:39:23,490 being responsive to customers? We have stated out 689 00:39:23,490 --> 00:39:25,730 there that, you know, once you submit an 690 00:39:25,730 --> 00:39:29,170 application, it takes so many days to process. 691 00:39:29,490 --> 00:39:31,730 How are we as an internal group performing 692 00:39:31,730 --> 00:39:33,570 against that? So I'm making this up because 693 00:39:33,570 --> 00:39:35,810 we haven't yet defined those dashboards. What would 694 00:39:35,810 --> 00:39:37,475 they like on their dashboard if they could 695 00:39:37,475 --> 00:39:40,435 pick, like, 10 things? But that's the idea. 696 00:39:40,435 --> 00:39:44,115 So executive leadership, the the directors of each 697 00:39:44,115 --> 00:39:49,555 of the divisions, Randy Gilbert, you know, etcetera, 698 00:39:49,555 --> 00:39:53,060 Stephanie Gough, they will have specific for their 699 00:39:53,060 --> 00:39:56,100 own group and their responsibilities, you know, kind 700 00:39:56,100 --> 00:39:58,020 of keeping an eye on the ball and 701 00:39:58,020 --> 00:40:00,900 making sure things are proceeding process wise and 702 00:40:00,900 --> 00:40:02,660 they have a sufficient time. So those are 703 00:40:02,660 --> 00:40:05,060 the types of metrics more aligned with performance 704 00:40:05,060 --> 00:40:08,645 metrics, but still TBD. In the RFP itself, 705 00:40:08,645 --> 00:40:11,685 I think we're requesting the cost associated with 706 00:40:11,685 --> 00:40:13,605 if you were out of the gate to 707 00:40:13,605 --> 00:40:16,005 build a dashboard for them, how much would 708 00:40:16,005 --> 00:40:18,645 that level of effort be with the intent 709 00:40:18,645 --> 00:40:21,560 that they would, through the training, would then 710 00:40:21,560 --> 00:40:25,240 have the competency internal to create, you know, 711 00:40:25,720 --> 00:40:28,920 random dashboards, ad hoc reports, should they need 712 00:40:28,920 --> 00:40:31,720 to beyond that. So we're just looking for 713 00:40:31,720 --> 00:40:35,080 the pricing of the dashboard piece actually creating 714 00:40:35,080 --> 00:40:45,285 them. Okay. Thank you. Hey, everybody. This is 715 00:40:45,285 --> 00:40:48,780 Michael Vaughn from DraftG Plus. I had a 716 00:40:48,780 --> 00:40:51,180 question about the getting back to the two 717 00:40:51,180 --> 00:40:53,580 way integrations with some of the various systems. 718 00:40:53,580 --> 00:40:55,900 Are is it known at this time whether 719 00:40:55,900 --> 00:40:59,420 systems like Tokay and Sages, do they have, 720 00:40:59,420 --> 00:41:02,220 like, a an open API that that that 721 00:41:02,220 --> 00:41:04,964 can be accessed and leveraged? Or is that 722 00:41:05,045 --> 00:41:07,605 is the expect is the expectation that that 723 00:41:07,605 --> 00:41:10,484 will be investigated and and and included in 724 00:41:10,484 --> 00:41:15,045 the response? Great question. So we headed that 725 00:41:15,045 --> 00:41:17,845 off. We did work with Greene County to 726 00:41:17,845 --> 00:41:20,390 reach out to representatives from each of those 727 00:41:20,390 --> 00:41:23,510 software vendors, to get clarity on that, you 728 00:41:23,510 --> 00:41:26,789 know, would would you be open to a 729 00:41:26,789 --> 00:41:29,670 a connection through an API or, you know, 730 00:41:29,670 --> 00:41:31,750 or or do you have strict rules about 731 00:41:31,750 --> 00:41:35,244 that? And absolutely, say no. All of them 732 00:41:35,244 --> 00:41:39,005 indicated the preference was for that manual export. 733 00:41:39,485 --> 00:41:44,605 So but they also referenced, potential for API 734 00:41:44,605 --> 00:41:48,070 connection. So does it need to be further 735 00:41:48,070 --> 00:41:50,470 discussed with them once they see the actual 736 00:41:50,470 --> 00:41:52,230 data points of what we're looking for? And 737 00:41:52,230 --> 00:41:53,990 we did kinda summarize that for them so 738 00:41:53,990 --> 00:41:57,830 they saw that it's really about notifications of 739 00:41:57,830 --> 00:41:59,990 when something is done. So when something is 740 00:41:59,990 --> 00:42:02,295 done, for example, in SwiftTrack, which is a 741 00:42:02,295 --> 00:42:06,214 statewide system, it works well. That the the 742 00:42:06,214 --> 00:42:09,255 status of whatever's being done in SwiftTrack is 743 00:42:09,255 --> 00:42:11,895 pushed into that one stop portal so the 744 00:42:11,895 --> 00:42:14,214 customer truly has. Can the customer go to 745 00:42:14,214 --> 00:42:17,015 SwiftTrack separately? Of course. But we wanna bring 746 00:42:17,015 --> 00:42:19,420 it all together to them in one place. 747 00:42:19,580 --> 00:42:23,260 So it's really primarily notification of where the 748 00:42:23,260 --> 00:42:26,220 process is at within those other systems. So 749 00:42:26,220 --> 00:42:28,860 that's the that's the the the type of 750 00:42:28,860 --> 00:42:33,065 information, But, yes, definitely needs to be further 751 00:42:33,065 --> 00:42:35,465 discussed with them. But those connections are made. 752 00:42:35,465 --> 00:42:39,465 They're aware of the potential request coming. And 753 00:42:39,705 --> 00:42:42,185 if we cost it what that API, just 754 00:42:42,185 --> 00:42:46,160 simple notification of process integration is, then we 755 00:42:46,160 --> 00:42:48,560 know that cost associated with that option if 756 00:42:48,560 --> 00:42:54,720 those in entities say yes. Okay. Great. So 757 00:42:54,720 --> 00:42:56,720 so I'm thinking about in thinking about the 758 00:42:56,720 --> 00:42:59,405 proposal, you know, our our our our charge 759 00:42:59,405 --> 00:43:01,805 is to investigate, well, a, the possibility of 760 00:43:01,805 --> 00:43:04,045 whether or not that's that's that can happen. 761 00:43:04,285 --> 00:43:06,925 But just the the cost associated with whatever 762 00:43:06,925 --> 00:43:11,005 development work would be required, you know, from 763 00:43:11,005 --> 00:43:13,070 the platform that we're proposing, the one stop 764 00:43:13,070 --> 00:43:15,550 shop platform, if you will, and and what 765 00:43:15,550 --> 00:43:18,030 that would take to to to essentially push 766 00:43:18,030 --> 00:43:22,430 that data into into these these other platforms. 767 00:43:22,510 --> 00:43:24,270 But in terms of the return data, the 768 00:43:24,270 --> 00:43:26,775 things that are triggered in in the the 769 00:43:26,775 --> 00:43:28,615 Sages and the ToeCase of the world, you 770 00:43:28,615 --> 00:43:30,375 know, that would require a little bit further 771 00:43:30,375 --> 00:43:33,255 exploration with those entities in order to in 772 00:43:33,255 --> 00:43:34,775 order to get that return data, if you 773 00:43:34,775 --> 00:43:38,079 will. Am am I understanding that correctly? Yeah. 774 00:43:38,079 --> 00:43:40,240 No. And you raised a very valid point, 775 00:43:40,240 --> 00:43:44,079 and I I I hear you. How about 776 00:43:44,079 --> 00:43:47,359 this? Greene County will note this as a 777 00:43:47,359 --> 00:43:51,760 question that we officially respond to, in writing. 778 00:43:52,605 --> 00:43:55,805 And do you mind just submitting that making 779 00:43:55,805 --> 00:43:57,645 sure you submit that question in writing, and 780 00:43:57,645 --> 00:43:59,645 then the county will have a response because 781 00:43:59,645 --> 00:44:01,965 you raised a valid point towards that end. 782 00:44:02,765 --> 00:44:04,765 Yeah. Yeah. Absolutely. We'll we'll make sure we 783 00:44:04,765 --> 00:44:08,045 get something submitted. Thank you, guys. Bye. Yep. 784 00:44:13,400 --> 00:44:18,760 What else? Hi. Kara McFall, Citizenserv. Will you 785 00:44:18,760 --> 00:44:21,720 be providing the copy of the recording of 786 00:44:21,720 --> 00:44:31,934 this conference? Eric Henry? I'm okay with it. 787 00:44:31,934 --> 00:44:40,710 Excellent. Thank you so much. Yeah. And it's 788 00:44:40,710 --> 00:44:44,150 it's a big it's a big, RFP. I 789 00:44:44,150 --> 00:44:48,630 think you probably all noted that, and in 790 00:44:48,630 --> 00:44:51,590 particular, the, I forget the name of the 791 00:44:51,590 --> 00:44:54,405 woman who brought it up. Taylor. Taylor. Thank 792 00:44:54,405 --> 00:44:59,525 you. You know, that technology diagram in 2.1 793 00:44:59,525 --> 00:45:04,565 gives you that sense of, complexity, that they're 794 00:45:04,565 --> 00:45:08,610 looking for with these different systems in play. 795 00:45:09,010 --> 00:45:12,690 But at the same time, just that if 796 00:45:12,770 --> 00:45:15,570 you keep that primary objective in mind, simplicity 797 00:45:15,650 --> 00:45:19,025 on customer, I'm coming to I'm sitting at 798 00:45:19,025 --> 00:45:22,785 home. I'm going I'm logging on. I'm typing 799 00:45:22,785 --> 00:45:24,705 in a few keywords about what I wanna 800 00:45:24,705 --> 00:45:27,505 do. And based on a search function, a 801 00:45:27,505 --> 00:45:32,145 search engine, the system is communicating to me 802 00:45:32,829 --> 00:45:36,030 the process I need to follow, the permits 803 00:45:36,030 --> 00:45:40,670 I need to apply for, expected turnaround times, 804 00:45:41,230 --> 00:45:45,390 right, processing times, and I'm able to follow 805 00:45:45,390 --> 00:45:49,175 and see where my application is in at 806 00:45:49,175 --> 00:45:52,455 the at any point in time. I also 807 00:45:52,455 --> 00:45:56,135 know when I'm required to do something and 808 00:45:56,135 --> 00:46:00,695 how long it's taken me. Right? And then 809 00:46:01,380 --> 00:46:05,859 internally, again, the the same functionality is there 810 00:46:05,859 --> 00:46:08,180 where internally they're able to see each other's 811 00:46:08,180 --> 00:46:11,220 comments on plans. They're able to see tag 812 00:46:11,220 --> 00:46:14,260 who's next because someone did just did something 813 00:46:14,260 --> 00:46:18,205 in the field. So that vision really speaks 814 00:46:18,205 --> 00:46:21,485 to efficiency and clarity of where I'm at 815 00:46:21,485 --> 00:46:24,205 in the process. So those are the key 816 00:46:24,205 --> 00:46:28,045 objectives. Even though there's a lot of existing 817 00:46:28,045 --> 00:46:31,030 technologies at play here, If you kind of 818 00:46:31,030 --> 00:46:33,030 think of it in that manner, it really 819 00:46:33,030 --> 00:46:39,190 keeps that end goal in mind. Alright. I'm 820 00:46:39,190 --> 00:46:41,349 very wordy. The county knows this, so I'll 821 00:46:41,349 --> 00:46:42,950 stop. Eric, I'm gonna toss it back to 822 00:46:42,950 --> 00:46:48,214 you. I have nothing to really add there. 823 00:46:50,615 --> 00:46:53,015 Is there anything that we can clarify further 824 00:46:53,015 --> 00:46:55,654 on or for anyone in the audience as 825 00:46:55,654 --> 00:47:04,420 far as that last question goes? Any additional 826 00:47:04,420 --> 00:47:13,395 questions? Well, not seeing any, so I guess 827 00:47:13,395 --> 00:47:14,755 we can give you about an hour and 828 00:47:14,755 --> 00:47:18,515 ten minutes back in your day there. If 829 00:47:18,515 --> 00:47:21,395 you wouldn't mind submitting any follow on questions 830 00:47:21,395 --> 00:47:23,235 in writing, that way we can make sure 831 00:47:23,235 --> 00:47:25,235 we provide it as clear as a response 832 00:47:25,235 --> 00:47:28,290 as possible. And, yeah, thank you for your 833 00:47:28,290 --> 00:47:31,570 interest, and enjoy the rest of your day. 834 00:47:33,650 --> 00:47:35,250 Thank you. Bye. Thank you.