Fort Smith 911 Governing Board Regular Meeting – June 25, 2026
All right, we'll go ahead and call this meeting in order the June 25th, 2026, 911 Governing Board regular meeting.
Baker here.
Clark?
Here.
Cooper here.
Congress?
Here.
Digman here.
Herm.
Here.
Judge Holtz is absent today.
Kinslow?
Here.
Seismic.
Okay.
Next up on the agenda is the approval of minutes.
Everybody has had a chance to review the minutes.
We have a motion to approve.
Okay.
Motion by Congress, second by Dington.
Any discussion?
Seeing none, all in favor, say aye.
Aye.
Any opposed?
Moving on to the financial report.
Overall, we are way on track on our budget.
We are actually 7.1% under our projected balance for this time.
The second quarter reimbursement that we get from the state of Arkansas was deposited last week.
It's not reflected on this report, but it has uh got notification yesterday that we have received that.
Most of the encumbrances you have are going to be related to the consolidation expenses.
We are waiting to get into that.
Um other than that, there's not really a whole lot to report on that unless there's any particular questions.
I do have a question.
Okay, what was the workers' column?
Was it over budget?
Well halfway through where it says it.
100% that's over is red.
Yeah.
Actually, I don't, I don't I really don't know what that is because of the the salaries, the budgeted in the actual.
We don't have anybody on duty, but this was coming out of ERP.
It says the revised budget matches the actual, so I don't think there'll be any additional expenses.
Yeah, I mean, is that what maybe that's what that is is the premium for the salaries?
It's not an actual yeah.
Okay.
Well, I mean, it is it is an actual expense.
Yes.
But there's not going to be any additional, so the 100% should be that's the workers' company for everybody for 2026.
It's not that we have anybody.
Right.
Right.
So question ahead.
Okay.
We have a motion.
What are we paying property insurance?
We're paying property insurance on whole off 4501 for a road.
Which will go away as soon as we can sell that.
Yes.
I actually talked to Ann with City and said as soon as that thing sells, let her know that it's coming on.
So I'm sorry.
I mean, bikes.
I don't know.
Small ones.
Small.
Motion to approve the financial report.
Second.
Motion by Herm.
Second by Clark.
Any further discussion?
All in favor say aye.
Aye.
Any opposed.
Alright.
So the item one.
The status of the CAD model and RMS setting.
February of 26th.
We discovered a breach by the vendor, Pro Phoenix, that violated both the terms of our agreement and the FBIC just security policy.
As a result, the vendor access to Pro Phoenix was immediately revoked.
And any progress toward reunifying the CAD with Sebastian County agencies was stopped.
The River Valley Fort Smith, River Rally Communications Center, Fort Smith, which is the fire department.
Have been operating with uh since September of this year, and have been operating without vendor support since that incident occurred in February.
We were waiting for the crime information, Arkansas Crime Information Center, ACIC, to give a recommendation on proceeding that came in early April.
That proceeding was such that while they would allow ProPhoenix to continue to operate, we had to do additional steps in order to maintain our tournament.
Because that trust relationship has been broken, because this has happened and can't be undone, and we don't believe it is fully able to be resolved despite what Pro Phoenix has said.
In late April, we notified Pro-Phoenix that they are a material breach of contract.
We are terminating the contract.
We have also asked for the full refund of the amount that we've paid pro-Phoenix to this point, the amount of 1.2 million dollars.
The issue before us now is that while we're waiting on the negotiations, we are still without a unified CAT, and that we need to move forward with this unified CAT.
I have a before the board a proposal, that is the exact same thing as what Pro Phoenix was offering to all of the agencies in Sebastian County.
Full unified CAD mobile RMS and jail management system.
It is um quite well not quite a lot, but it is uh significantly less expensive than Pro-Phoenix.
And we have to move forward.
So what I'm coming to the board is if you notice on page nine of the packet, I placed a 911 fund performance chart for you to review, and which says that our 911 fund is sitting at a 2.3 million dollars at this point.
What I'm proposing is I'm proposing a revision amendment to the 2026 budget in the amount, which the agenda was incorrect.
I mistyped the amount is going to be 379,272.46 cents.
I'm requesting this allocation uh as an amendment to the 26 operating budget with the understanding that upon any negotiated settlement that we receive from Pro Phoenix, it will reimburse the 911 fund.
Once the contract is approved, should we approve this uh allocation and the contract is approved?
We will immediately become beginning implementing uh the software system meeting with all of the agencies and preparing for that launch.
So that's where we're at right now.
At this point, if uh we would we'd like to discuss, I would uh entertain a motion to approve this resolution.
Motion, second, it's been moved and seconded any discussion.
Beyond this amount, does everything uh settlement go into this department's budget or just what we're going to the general fund?
We depend on the yeah.
I'm only asking when the uh settlement comes back to replenish in this amount, but put back.
I mean, it's funded out of the general funds.
Right, right.
Predict the one point one prime, one point two years seeking back.
Did that come from that one?
That came from the general fund.
Wasn't there some funds to not support this in the city or not?
Whether what part of the funds were about the one eighty-eight-ish part of that that's part of that one point two?
But I mean, well, we also put that back in.
Did we take that out of the budget?
Come out of the general fund.
1.5 million dollars was approved by the board of directors in 2021, 2022 for this project, the cattle RMS project.
There was a fund created, that money was placed into that fund, and it's been I mean, sort of being spent out of that since then.
Um, I know the answer to this question, Wes, but the rest of the board would probably appreciate hearing it.
Did you uh do your due diligence and getting um central square the proposed new vendor uh get the best possible price that we could get?
Yes, the the central square.
When we did the evaluation, we evaluated seven seven different CAD and RMS vendors, and Central Square and Pro Phoenix came up and they scored exactly the same.
This was from an extensive research done for with a number of police officers, dispatchers, firefighters, and during the evaluation, as I said, the the score came back exactly the same.
We then brought them back for a second evaluation, scored them again and again they scored exactly the same.
Right.
Um we went with Pro Phoenix with Pro Phoenix, issues arise, we went back to Central Square, and Central Square is the one that's given this bit.
I will also tell that the uh police department looked into uh the Motorola product and it came in uh quite a bit more expensive.
Uh 1.8 million dollars over what this cost is, and so uh Central Square has given us a tremendous amount of incentives.
Um we've we've looked and it was what was evaluated.
This is a benefit.
One of the issues that I put before Central Square is I said that I've got multiple agencies in the county.
I want them to be able to use it just as they were with Pro Phoenix, and that's exactly what's happening.
Every agency will have mobile access, RMS access, CAD access.
We're gonna update the jail on it, it's going to be integrated exactly as Pro Phoenix was, and it's actually over the long next five years, it's going to actually save us money.
One of the issues that I said is that I would not be able to come to this board unless they could get at or below what we would be creating Pro Phoenix when they got below.
So what were we supposed to pay Pro Phoenix?
And we haven't paid them anything.
This year's payment would have been 197,000.
That's the service and agreement fees.
Every year beyond that, it was going to raise five percent, right?
Central Square is going to charge us 198,000.
But instead of raising 5% every year, next year it'll be 198,000.
And then it'll only raise 2% the next three years, rather than 5%.
So over the long term, the service and subscription fees year to year will be significantly less than what Pro Phoenix was.
The uh the actual implementation cost for ProPhoenix, the initial cost was a little bit less than $1 million.
If you include the multi-jurisdiction, it was right at $1 million.
Versus $300.
Yes.
Well how much $300,000.
And that actual implementation cost was something that carved few years ago.
Was that what we're saying?
We've been working on several years of my life.
October 25, September, October 25.
Okay.
This has been a years-long process.
This is an extremely heavy lift for an organization of our size for the complexity and the importance of this software, not just the CAD part of it, which I mean that obviously affects the dispatching calls and everything, but the RMS, I mean, our ability to collect data to retrieve that data and use it in meaningful ways.
Um, so I mean, the good news is is that we've we've won what we've learned in the process what we need to know, and so uh I don't it's not gonna be that big of a lift now to go through with a you know a new vendor.
Um usually the implementation starts cheap.
No, I just I I obviously uh our hope is that we don't have similar issues with uh Central square as we've had with Pro Phoenix.
Yes, the benefit uh to where we at today is that we spent all this time working on Pro Phoenix, you know, it's and nobody was more mad about this than me.
When this incident occurred, I had all these guys here that we were working on setting it up, and then all of a sudden it goes to full stop.
But that turned out to be a benefit, because now I've already got all the agencies, I've got all the users that they need, I've got all their computer systems they need.
So I don't have to go around and start gathering this stuff once we have our kickoff meeting.
I've already got it.
And they said typical implementation for this, six to eighteen months.
I'm gonna try to beat that six month mark.
So the 379 is implementation.
That's all, yes, sir.
Okay, that's that's full implementation cost, training, installation, and the first year subscription.
We had hardware, we had hardware costs and that was involved in the Pro Phoenix as well that we won't have with this.
You obviously don't know what the settlement will look like, yeah.
And that's and that's why I was coming to the board with this.
We don't know what the settlement has looked like.
Uh the attorneys have the attorneys have been talking.
Uh ProPhoenix is retained lawyer out of the rock, it's been talking with Kobe Roe, our city attorney regarding any type of settlement.
Uh I can tell you that uh Colby assured us that we're in a good position.
Ultimately, the mistake was within ProPhoenix, and that he feels like that the city is in a good position to recoup some of that funds.
But the ultimately, whatever settlement comes back will go to the board for uh will go to the board for approval.
Um and if there isn't a settlement that we like, then the next step would be litigation.
Litigation could take quite a while, which is why I'm asking for this in order to get us started.
We're we're functioning all part of the time right now.
I mean, with no support, uh, if we encounter a problem that we're not able to handle in-house, uh, we're gonna be dead in the water, and we cannot have that.
If I could give an example, this weekend uh the station alerting for the fire department for Phoenix home for several hours.
And then when it finally started going, it dumped every call into the station alerting, and it tied up the fire radio channel so much we had to call Jeremy with Motorola and stop that channel and move to the operation until we could get it cleared up.
So cheap paper is absolutely correct.
We are on borrow time.
Uh we have no support right now.
We can't.
Plus we have to have the implementation done to flip that switch.
So I mean, we're on we're still borrowing time right until we've got this ready to go.
So is that pro phoenix snuck in somewhere?
No, I just think that that was it's a it was an issue just within the software itself.
Well, I mean, we got off the access, so they can't.
We pulled away from that, we're pulled away from the violation of contract.
Did they sneak that in on you or is it just got missed, or you know, and how big are they?
Could that drive, could this affect them with multi-ages that could have been bankruptcy and we don't see it down?
Not sure.
Kind of wonder, but that's usually what happens when someone screws it out.
They go bankrupt and nobody sees any money, or depending on the dollar I'm saying.
I think so.
I mean, they've got a lot, they're just we're the only ones down in this region, they're heavy north and northeast, and they've got a lot of customers.
I mean, we've gone to the conference, it's a huge deal, but didn't think that's the one thing about where the support is based at.
I'm assuming Central Square, we did cover that.
That was the very first question.
Okay.
Just have to ask because Arkansas has there.
Good afternoon.
I'm Dr.
West Milo.
Where's your support located?
Yeah, and how long have you been using Central Square?
All of it.
Central Square owns our legacy system, yes.
For several years.
1997.
So the scores, the support is there, you are familiar with it.
But we are we're getting their newest product, yes.
Yes, we're upgrading to their newest product.
Excuse me.
Their product, yes, but their support we are familiar with, but uh they are fully CGS compliant and several other agencies, so so I know when we switched to ProPhoenix, we were not able to move the legacy data, and we currently have a antiquated system set up and running to access all of the data that we maintain since 1997.
Since this is a central square product, are they going to be able to migrate that data from PSSI and ISIS into the new GATRMS?
No.
The quote that here is just for the ProPhoenix data conversion.
Everything we've done from ProPhoenix to today, or when we go live, that will be converted.
The ISIS data that we have won't be converted, but because of the standard of data validation that's in PSSI that's needed for the new technology technological part of CAD, they're it's corruptible.
I mean, there's there's some you've been in it, you know it's it's it's pretty messed up.
So what we're proposing to do and what we're working with Central Square on is to come up with a hook uh that would be able to access the SQL data with the legacy system.
We're gonna move it over uh to a new server.
I believe Dan and James have talked about uh process with that, and then we develop our own API into the Central Square part.
But if there's a way to save that data and make it more accessible, we and I would be interested in.
I know the 911 board is not probably interested in that, but at least the part of it would certainly uh be interested in preserving that if possible.
There's a lot that can be done, including searching other systems, you know.
Should we let's say for Greenwood, you know, they have their legacy system, they freeze their data and rather than convert it, I put in the hook.
So when you type in search for West Mile, it searches for Smith PD records, Sebastian County records, and green root records all at the once and it's within the county.
That's after we got a development, we got to figure it out.
We need to build first, and then as we start going live and we start coming into this and becoming more of a centralized unified public safety county, we can start looking at stuff like that.
But all of that would have been true if we were staying on ProPhoenix, yes, we build something like that.
Yes, that's correct.
That was the plan with ProPhoenix is the same thing with the legacy BSS ICAP.
Does this affect anything with Tyler?
What the county currently has with the not until we go live.
Uh the legacy system.
I was talking to um John Miller, and the legacy data is the same thing we're gonna do with the police department, we're gonna freeze it, we're gonna come back.
The jail uh portion of it, all of the integrations that we had that we needed with the courts, we're gonna have.
Um, I mean, it's all the integrations that the jail needs with uh the like the commissary and the the jail calls and stuff, all of that was included in this cost.
So I made sure I said this is the integrations we needed, it mirrors what we have, what we're trying to get started, so we're all on that same system.
No unexpected costs with Tyler.
Well, I hope not, no.
Yeah, the other questions.
How is their fire RMS?
They don't have one.
The reason we went with Pro Phoenix instead.
What we all end up doing is exactly what you're either what you're doing now, uh API.
Basically, your system we're gonna be piping into the CAD calling information into the fire department system, but they have because they didn't have one.
That was part of the reason uh we ended up going with Pro Phoenix.
They pair up with first new separate company.
There are three large ones.
Well, the smaller departments they do get sneaked.
Your fireworks.
They do interface with that.
Are they going to?
I'm sure we can get them to do it.
Yes, sir.
Would there be an overall cost that would support all the fire departments in the county?
Not with this.
Not with this quote.
Um, what we can do was we'll get and find a solution for that.
This is just CAD and mobile, and then the APIs with the fire agencies to get us going with that.
It might be further down the road.
Yeah, if you have some idea what that costs would be.
No, not for that.
So we essentially we would have to find, you know, some sort of uh fire RMS that would be acceptable and could pull them into it, but we would connect it all the same.
It's just it wouldn't be called central square.
I mean, I think a lot of the smaller communities in South Sebastian County were looking forward to seeing.
I know.
What Profix?
Yes, to get them FEMA compliant.
Yes.
Nobody's more mad about it than me.
We'll just have to look because I mean you'll have I think with image trend, I think it was about 4,000 or one time fee patch it.
You know, different ones will be different, working with you know, so you'll have to look at a new one.
You know, you'll have your one-time fees for the software license.
Some of them don't have an RMS provider at all.
Yeah, so yeah.
So you're confident with the Fort Smith Fire Department's RMS will communicate with this.
Yeah, oh yeah.
We've already Corey's already been talking with them, and any other questions?
So the motion on the floor is going with Cat or the uh Central Square vendor at the 300 plus thousand.
The motion on the floor is to augment the budget the funding for that, there would need to be another motion to approve that.
So on the motion on the floor to increase the budget funding, start with Conger.
Yes, Dingman?
Yes.
Yes, folks is not present.
Kinslow.
Yes.
Baker?
Yes.
Clark?
Yes.
Cooper, yes.
Okay.
Now we can entertain a motion to accept the Central Square.
So to recommend the receipt.
Yes.
The motion is to recommend that the state board directors approves the contract with Central Square to begin implementation.
Yes.
That's what I thought.
Okay.
Sounds good to me.
Perfect.
Who seconded?
Discussion.
Okay.
Dingman?
Yes.
Hearn?
Yes.
Ken Slok?
Yes.
Seismic.
Yes.
Baker?
Yes.
Clark?
Yes.
Cooper?
Yes.
Congress?
Yes.
Okay.
Motion passes.
So we will go to item number two on the agenda.
Is an update on our consolidation.
You guys should see what they're doing upstairs.
I've had radio folks and IT networking folks and all kinds of stuff going on, getting us ready to go.
Next week, we're going to start testing the rural fire paging system from this location.
So I've talked to Chief Sizemore and Chief Blunt and a few others about sending test pages, getting that done.
We're setting up the counted tornado siren activation, kind of streamlining everything of the new radio uh equipment is being outfitted and ready to go.
We've run into some additional expenses that I'm bringing before you that would be out of the 400,000 consolidation reimbursement that we're getting from the state 911 board.
As you remember, for uh as a reminder, the 400,000 dollar allocation was approved in the March meeting in order to allow for these type of expenses.
I've talked to CJ Ingall about every expense.
The expenses that I have before you are reimbursable for that.
The first one is for some Fortnite network hardware.
This is for the RVCC network infrastructure, creating a uh you know, a network domain, so to speak.
The cost of that is 30,834 and 52 cents.
The next one is with SHI International Corporation, and this is for our Microsoft Office software tenant and licenses.
This is for our active directory, our storage, and for the email uh tenant that comes with all the the government because we're.gov, we have to use government.
Cost of that is ten thousand to nineteen and five cents.
Uh the voice products, we are now updating our nice informed system.
We had to add and remove and switch around some channels.
We're gonna make we clean we cleaned it up, we're gonna make it a little bit more efficient.
This involves how we're we're putting calls into the consoles, and so now that we are adding additional phone channels, we've also got additional radio channels, and so we are going to be bringing in the Sebastian County radio channels that have usually been recorded with the sheriff's office.
We're going to be bringing over into uh the NICE inform, we're going to need to do some reconfiguration.
There is a small interface that I need because of the increased channel count.
That cost is a one thousand six hundred and thirty-two dollars of nice uh voice product.
Finally, the ATT, uh, we were having some issues.
Our our city lines are with Cox Communications.
Our emergency 911 lines are through ATT.
We were having some interface issues between Cox and ATT into the VESTA call handling equipment at each one of the consults.
After conferring with City IT staff, county IT staff, both ATT and Cox, the solution uh that I have for this is that we will be uh outfitting non-emergency admin lines also through ATT.
And what that's going to do is that it if you're at a console, you pick up the VESTA console phone, you'll answer a non-emergency or a 911 emergency call and be able to transfer, which is what the problems we were having is that transfer between the two systems.
Or excuse me, I went with uh the county IT director and his staff uh starting on July 6th of the consolidation.
We're going to switch over their main phone tree.
Um the Portsmouth police phone tree will remain the same.
Any type of uh call that's coming in, we've sent to the 5100, which is going to be the main dispatch number.
I'm going to port that number over from the COC system to this ATT system, and then they're going to have the eight concurrent lines and stuff.
One-time cost of implementation.
I literally just got it yesterday, 1,500, and it'll be a 430, 433.4 cents a month after that.
The one-time cost is going to be part of the reimbursement from the state.
The monthly cost, I have enough in the budget to handle that already for that.
So having said that, after all of these expenses, I listed in the consolidation packet where you were.
We were we started with 400,000 in the state of Arkansas reimbursement.
Uh, the March 2026 approved expenses totaling 303,790 45.
And then today's requested expensive 42,685.57 plus 1500, gives us uh a total remaining balance of 53,523.
Um we're gonna keep that there for right now, uh, as we get to consolidated, which is a little over a week away.
So once we get consolidated and get moving, if there's any additional expenses that arise, I will be coming to the board for that into that amount.
Once we are ready consolidated and all set, I will take all of these invoices, send them off to Arkansas 91 board, and uh for approval for our reimbursement, and then we will get that reimbursement to the state.
Then you're 53,000, you said that includes the 1500.
It does, no, it's 53,000 minus 1500.
So 52.
So you need a motion to approve 44185 and change adding in the 1500s?
Yes.
I'll make that position.
Okay, okay.
James, you might answer and question.
Absolutely.
Can you talk to us about the support of that network hardware?
If you had any involvement in the procurement of this, and uh a little bit, so um RBCC is becoming its own entity, and uh the proper way to think about this is that they need to have their own.gov, which um Dr.
Milan and others have been working on.
They need to have their own network.
So uh the lines portion of the quote that you see in your packet is for two forty-game firewalls.
This gives us the redundancy uh and the reliability building to support that.
I believe there was actually a switch in there as well, just to make sure you got the port sensory needed for all of your consults, from this whatnot.
So is this hardware that can be moved when the RBCC moves out of the police?
Yeah, we aren't lift it and shipped it, no problem.
Okay, chief.
To that point, everything that I'm doing right now is with I have okay.
Black James said lift it and shift it.
Thank you, yes, sir.
I know this probably was early on too uh slept since then, but are we saving saving our dollars by creating our own domain?
Is that something that's required by the state, or is that something that's a safeguard for the RBCC to have its own domain and that's it's not required for the state.
However, setting up the RBCC the way it is set up because we are serving much more than City of Fort Smith, municipalities, governments, uh it's prudent to become a dot gov to reassure security resiliency, redundancy, so that say, for instance, well, I mean with ACIC, so that we could set up a process by which our uh communication with the law enforcement agencies in the county is secure with the sieges data.
This is uh we had a CGIS audit earlier this year uh from ACIC, and they've identified some steps for us to take to become more compliant.
This is this is becoming part of it.
In fact, very soon we're gonna be switching the police department.
Are you already doing it?
They got to switch over to a dot gov.
Okay, so this is this is all towards the eye of cybersecurity, and with us being within the city but still serving everybody else.
We felt this was the best way to make this our entity so that we can better communicate safely.
Okay.
Any other questions?
Okay, so motion to approve the um clerk and guy.
All right, so uh let's see.
Um, cancel.
Yes, man.
Yes, Baker, yes, Clark, yes, Cooper.
Yes, Conquer?
Yes, David.
Yes.
Okay, the second one, or though, excuse me.
The last item on the agenda is the bylaws.
When we first became incorporated for the interlocal agreement, excuse me, when we sent the plan to the state for developing the river valley communications Center, one of the priorities of this board was to develop a set of bylaws that governs how we conduct our meetings, how we deal with procurement, how we how we as a board operates.
And so doing, I was able to put together some bylaws.
Special thanks to Tim Hearn who sat down with me and gave me some very very good advice that it was much appreciated on developing and making these bylaws as good as we as good as they are.
Okay.
Presented these to you.
I mean, the email these to you after the March meeting.
I'm hoping that we have had a chance to review these, suggest anything from that.
Should we approve the meeting or the bylaws today?
It requires a two-thirds vote.
Okay, which is going to be seven people of the nine.
Yes.
And so and we approve the bylaws today.
And the Sebastian County Forum Board for approving.
And then once that's uh developed, we would then elect the officers and begin uh operating under the bylaws as to be resolved.
To that, any discussion questions?
So on the secretary, are you gonna have an elected position from the board for that?
I don't know.
I believe I believe it was that I would do that.
Fine, but I'll see it in here.
Because usually that's the case is the executive director serves as secretary of the board.
I don't know if anyone there wants to do the minutes.
Okay, here it is, section 3.6.
Secretary.
The executive director shall serve as the secretary of the board in except his ego capacity.
Is that not in the packet?
No.
No, it's not.
Okay.
No, 3.06 just says what the secretary is.
That's it.
Well then, sorry about that, but that's that had since been updated.
I guess that didn't come across.
I apologize for that.
Is this meeting being recorded?
Yes.
Just audio?
Yes.
So do you have any other thing that might be left out?
Do we need to do that?
Oh, that was that was the main thing, and there was a couple of you could mind.
It I think it was calling a meeting.
We changed that time.
And then um so there's 3.6 that we changed and we moved.
By laws amended by two-thirds affirmative vote.
Oh, here it is.
Proposed amendment has been submitted in writing.
If we wanted to make an amendment, uh it has to be submitted in writing to all board members, no fewer than 30 business days.
I think that was the change because we went um is that in the bylaws?
Yes.
Okay, so we don't have them now, so that didn't count.
I'm sorry.
We don't have them right now, so that section to what you said and then vote on it as a disprinted amended.
Okay, you know, and that's the thing because you want to buy if you want to table it to the September meeting, that'll be fine because I think even by then that'll give me time to in actuality.
I mean, I'm gonna have to go before both boards anyway because that'll be budget season.
If the finalized version that we have in the packet is not it's it's not the finalized version it isn't the change I would recommend that we table this in September so I can get the the amended budget or the amended amendment bylaws to you and so is it well did you know an objection to that what he was saying about the two executive directors or you didn't see you no more that's what I heard no no no I think it's my suggestion I think I'll go to we were talking I had secretary being being one of the you guys you don't want that and so it was it was to change to where I'm the secondary I thought well that's a good job I'm doing it anyway so I think you'd have that to the IT yes I mean unless it sets us back.
No I kind of like having it frankly I mean as long as we get this done by the end of the year we can even start clean in January so I'll make a motion to table it seconds.
Motion by Baker seconds by Hearn all in favor?
Aye.
Any opposed okay does anybody have any new business?
I don't necessarily is it is it okay to guess if there's anything from the audience please chief did you have or have the police department over there not really but appreciate you guys calling Dr.
Milan maybe you expound on the computer system for for those of us car computers is it gonna be touch screen based like y'all force minutes or is it going to be it works either one same thing you can either put the hotkeys on the keyboard and use them or if you have touch screen you can use it.
We are switching our phone lines at Greenwood and uh currently going through the document as well.
So we receive several phone calls a day that probably should go through the 911 system and we have to reroute is there going to be a way that we can transfer those calls to 911 just with the touch of absolutely all it takes is you get into the um the audio auto attendant you just make a little change and that's what it goes.
On the horizon there's a lot of technology out there dealing with AI like you you put in the prompts and everything and then somebody calls depending on what they need will automatically push them out to what it is you know if they call and say you know hey welcome to River Valley Communications Center what can I do for you well I just need to know when the Greenwood Christmas parade starts they can either say well it starts at six o'clock on this day or hang on let me transfer the Greenwood police department that type of thing but that's you know that's quite a bit of ways.
We actually previewed a bit of that earlier of it it's just it's it's still too young.
Yeah because you know exactly everybody knows exactly what's going to happen.
They're gonna call hi how am I helping operator every time and it's gonna come straight to the dispatch so might as well just push it in there anyway.
So we'll be working with you with that and we can get that set up too much.
If you have one yes yes sir just for our planning purposes is there going to be one centralized VPN or does each department have the room on this system no this is a hosted solution you will not need a VPN okay that's one of the things I told them because we were supposed to go to go to that say no VPNs they said we are finalizing the 2027 budget.
It's due on Monday.
Once I get that set up, I will be sending that to each of you for review via email, and that will be for up for approval like the September board meeting.
The next board meeting is it's set for that last Thursday, the 24th, at one o'clock.
I've got to find a location for that area in here where we need to be, okay.
So anything else?
Yes, sir.
One other I should have mentioned this.
Walk us through what July 6 looks like for someone like us and for a back.
My absolute goal is that July 6th, you won't you won't you won't notice any difference.
We're going to be spending next week, making sure all systems are in place.
Because of the precarious situation that Prophoenix has put us in, I've had to create an island inside an island.
So we have set up Sebastian County dispatch computers on three of my consoles.
Okay.
And so Tyler, CAD that you all are using, all the mobile links that you were using, all of the phone numbers that you were using, all of the radio channels that you were using are all going to be the same.
The only difference is instead of the dispatcher being across the street, you're going to be in this building.
I'm working very very hard to make sure that on your perspective it's seamless and you don't notice any change.
There might be some hiccups as we get started, you know, because I gotta bring, I gotta bring one over, then another over.
We're gonna be operating a lien on radios.
We'll have plenty until we bring the other three over.
But there are three dedicated positions specifically for that.
Okay, so there you from your perspective, July 6th, you shouldn't see any change.
You mentioned something about uh power paging.
Is it going to be doing testing next week?
Next week, next week.
Maybe even a couple of tornado siren testings on Wednesday.
Joe Beth, y'all do Wednesday testing, don't you?
We may do that from here, just to make sure that that's up and running.
Uh I will tell you on the topic of tornado sirens.
I'm meeting tomorrow morning.
I'm meeting with a gentleman from Goddard Enterprises.
He is uh federal signal uh maintenance in based in Oklahoma City or Tulsa, I believe.
He's going to be in town and he's going to talk to me.
Kind of similar to what we worked with a couple years ago to see what a status is of our tornado and civil defense sirens in the county.
Ways we can improve, we can use we can be more efficient.
Um we received the the Motorola services agreement for the city of Fort Smith that includes our Fort Smith tornado sirens maintenance and upkeep that I will assume in 2027.
Um so I'm trying to find ways in which to save the money with that, uh is see if somebody can do the very same cost.
The very same thing at a reduced cost of what motorola is charges.
Uh so just to kind of give you an update by that for the uh police and fire chiefs out of here.
I may be uh getting with you guys uh in order to come check out your tornado sirens and see what it is that needs to happen depending on the uh depending on the city.
So just kind of research and seeing what this is and bring that to see what we can do.
I have got I've got one, I've got two grants in the mix right now.
I've applied for two grants.
Uh the first one is uh a ten million dollar grant department of transportation uh for building a facility.
I'm waiting to hear back on that, and then I'm also going to I've applied for a Department of Justice grants to help uh update the radios in Sebastian County to that avid template with AWIP to be able to refresh and get the radios up and running for that, um, and then I'm gonna probably have another grant that I've that come across my desk a couple weeks ago that's due in September.
So that's where we sit.
Thank you.
Okay, thanks, guys.
Fort Smith 911 Governing Board Regular Meeting – June 25, 2026
The Fort Smith 911 Governing Board met on June 25, 2026, to address the termination of a vendor contract for CAD/RMS software, approve a new vendor, review consolidation progress, consider additional expenses, and discuss proposed bylaws. The board took several votes and tabled the bylaws for further revision.
Consent Calendar
- Approval of Minutes: Minutes from the previous meeting were approved by a voice vote (motion by Congress, second by Dington).
- Financial Report: The board approved the financial report (motion by Herm, second by Clark). The report showed the budget was 7.1% under the projected balance for this time. The second-quarter state reimbursement had been received but not yet reflected. Encumbrances were primarily related to consolidation expenses.
Discussion Items
- Termination of ProPhoenix Contract and New Vendor Selection: The executive director reported that on February 26, 2026, a breach by vendor ProPhoenix was discovered, violating terms and FBIC security policy. Vendor access was revoked, and the Arkansas Crime Information Center (ACIC) recommended steps allowing ProPhoenix to continue only with additional compliance. The board was notified of a material breach in late April and the contract is being terminated. The city is seeking a full refund of the $1.2 million paid. A new proposal from Central Square for a unified CAD, mobile RMS, and jail management system was presented. The implementation cost is $379,272.46 (amended from an earlier incorrect figure), covering training, installation, and the first-year subscription. The request is for a 2026 budget amendment funded from the $2.3 million 911 fund, with reimbursement expected from any ProPhoenix settlement. Central Square scored equally with ProPhoenix in prior evaluations and offers a lower service fee ($198,000 with 2% annual increases vs. ProPhoenix's 5% increases). Implementation is expected in 6–18 months; current operations are unsupported and at risk (e.g., a recent fire station alerting failure). The board discussed legacy data migration, fire RMS compatibility, and support location. Central Square support is U.S.-based and familiar to the agency.
- Consolidation Update: The executive director reported progress on consolidating the River Valley Communications Center (RVCC), including testing rural fire paging next week and tornado siren activation. Additional expenses were presented: Fortinet network hardware ($30,834.52), Microsoft Office software tenant/licenses ($10,219.05), NICE inform system updates ($1,632), and AT&T non-emergency line implementation ($1,500 one-time, $433.40/month). These expenses are reimbursable from the state's $400,000 consolidation grant. After previous approved expenses ($303,790.45) and today's requested expenses ($44,185.57 including the AT&T one-time cost), a remaining balance of about $52,023 is expected.
- Bylaws Discussion and Tabling: Proposed bylaws for board governance were presented but the packet lacked final revisions (e.g., section 3.6 on the secretary role). An amendment requiring 30 business days' written notice for bylaw changes was noted. The board decided to table approval until the September meeting (motion by Baker, second by Hearn) to allow for finalized revisions.
Key Outcomes
- Budget Amendment Approved: Motion to increase the 2026 budget by $379,272.46 for Central Square implementation passed unanimously (8-0 with Judge Holtz absent).
- Central Square Contract Approved: Motion to recommend that the state board of directors approve the contract with Central Square passed unanimously (8-0).
- Consolidation Expenses Approved: Motion to approve the additional consolidation expenses totaling $44,185.57 (including $1,500 for AT&T lines) passed unanimously (8-0).
- Bylaws Tabled: Motion to table approval of bylaws to the September meeting passed unanimously.
- Next Meeting: Scheduled for Thursday, September 24, 2026, at 1:00 PM (location to be determined).
Meeting Transcript
All right, we'll go ahead and call this meeting in order the June 25th, 2026, 911 Governing Board regular meeting. Baker here. Clark? Here. Cooper here. Congress? Here. Digman here. Herm. Here. Judge Holtz is absent today. Kinslow? Here. Seismic. Okay. Next up on the agenda is the approval of minutes. Everybody has had a chance to review the minutes. We have a motion to approve. Okay. Motion by Congress, second by Dington. Any discussion? Seeing none, all in favor, say aye. Aye. Any opposed? Moving on to the financial report. Overall, we are way on track on our budget. We are actually 7.1% under our projected balance for this time. The second quarter reimbursement that we get from the state of Arkansas was deposited last week. It's not reflected on this report, but it has uh got notification yesterday that we have received that. Most of the encumbrances you have are going to be related to the consolidation expenses. We are waiting to get into that. Um other than that, there's not really a whole lot to report on that unless there's any particular questions. I do have a question. Okay, what was the workers' column? Was it over budget? Well halfway through where it says it. 100% that's over is red. Yeah. Actually, I don't, I don't I really don't know what that is because of the the salaries, the budgeted in the actual. We don't have anybody on duty, but this was coming out of ERP. It says the revised budget matches the actual, so I don't think there'll be any additional expenses. Yeah, I mean, is that what maybe that's what that is is the premium for the salaries? It's not an actual yeah. Okay. Well, I mean, it is it is an actual expense. Yes. But there's not going to be any additional, so the 100% should be that's the workers' company for everybody for 2026. It's not that we have anybody. Right. Right.
openpublica.com