Jackson's City Council ratified a 12-month renewal of the Cityworks license and maintenance agreement with Azteca Systems, LLC on Oct. 6, according to item 13 of the regular meeting agenda. Cityworks is the software the city uses to manage all non-emergency constituent service requests, the 311 tickets that route potholes, illegal dumping, and code complaints to the right department.

The same week, bids closed on the system that is meant to replace or absorb it. Proposals for the city's Enterprise Resource Planning system, RFP No. 20477-092226, were due Oct. 6 at 3:30 p.m., according to the solicitation posted on the city's procurement portal, jacksonmsbids.com. The RFP calls for a cloud-based ERP covering permitting, code enforcement, 311 resident services, stormwater management, and public works asset tracking.

The two documents point in opposite directions. The city is paying to keep the old constituent-service platform running for another year while it shops for a system that, by the RFP's own language, must integrate with existing tools including Tyler Munis and Cityworks. The RFP says the city prefers a single vendor solution but will consider a phased approach, and that it may award modules separately to different vendors.

The addendum that answered vendor questions, posted to the city's bid page on Oct. 6, sets the timeline in plain terms. The anticipated project start date is Oct. 1, 2027, and the desired go-live date is also Oct. 1, 2027, according to the addendum. That is roughly a year after the bids closed and nearly two years after the RFP was issued in August 2026.

The addendum also confirms the money question the city has not answered. The RFP states the project is anticipated to be funded through a combination of general-fund appropriations and federal grant allocations, subject to City Council approval, and that federal grant requirements including 2 CFR Part 200 may apply. No dollar figure appears in the solicitation. Third-party estimate ranges for the opportunity run from $750,000 to $3.5 million on one procurement tracker and $2.5 million to $9 million on another, but those are outside estimates, not city numbers.

That gap matters because the city is already carrying the cost of the system it is trying to leave behind. The Cityworks renewal is a recurring annual expense, and comparable Azteca contracts elsewhere run in the tens of thousands of dollars a year, with pricing tiered by population. Jackson's own contract value is not stated in the agenda item, which authorizes the mayor to execute the renewal without naming a figure.

The council agenda also shows the city is not waiting on the ERP to fix its revenue systems. Item 8 introduces an ordinance amending the solid waste facility disposal fees in Section 106-148 of the city code, a separate fee schedule tied to the Byram landfill. Item 12 sets a public hearing on the district plan for the Downtown Jackson Business Improvement District, the 65-block assessment district managed by Downtown Jackson Partners that charges commercial property owners 10 cents per square foot.

Read together, the Oct. 6 agenda is a portrait of a city patching legacy systems while it waits on a procurement that will not produce working software until at least late 2027. The ERP is the largest single software purchase on the city's horizon. The Cityworks renewal is the bridge to it.

There is a specific question no one has answered publicly: what happens to the Cityworks contract if the ERP vendor selected in 2027 offers a 311 module that duplicates it? The RFP requires proposers to identify any requirements outside their proposed scope in the Functional Requirements Matrix, and it allows the city to award modules separately. That structure leaves open the possibility that Jackson pays for Cityworks and a competing 311 platform at the same time. The purchasing manager named on the solicitation, Monica Oliver, is reachable at procurement@jacksonms.gov and would be the person who could say whether the renewal term is meant to run past the ERP go-live.

What's next: The city has not published a notice of intent to award, and the RFP ties every milestone to council approval with no date attached. Proposals are binding for 180 days from the deadline, which carries them to about early April 2027. Watch the council's agenda for the award order, which will carry the first real dollar figure attached to the project, and watch for the cost proposal, which the RFP says becomes public after award.

The addendum's Oct. 1, 2027 start date is the number to hold onto. If the council does not award by spring 2027, that date slips, and the Cityworks renewal the council just ratified becomes the second or third bridge contract for software the city has already decided to replace.