Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Pavement Management topic
No spam. Unsubscribe anytime.
Council reviews Kimley‑Horn pavement‑management tool, weighs funding scenarios and public engagement
Summary
City staff demonstrated a pavement‑management website built from a recent Kimley‑Horn road survey that models budget scenarios, maintenance needs and multi‑year project planning. Council members discussed town halls, funding options and follow‑up steps; no formal vote was taken.
Becky (staff member) presented a pavement‑management website populated with Kimley‑Horn’s road survey and said the tool will help the city “break down what we're going to do project wise and prioritize what to do when.” The demonstration showed street segments, recent work history and a pavement condition index (PCI) for individual sections and for the network as a whole.
The tool allows staff to run multi‑year scenarios showing how different annual budgets affect PCI. Becky said a $1,000,000‑per‑year scenario was used as a demonstration and that, under that assumption, the citywide PCI would decline several points over five years; she showed alternate scenarios including $2,500,000 per year and a “no work” option. Becky also noted Kimley‑Horn retains underlying video and data and that the city has access to the site on an annual subscription basis.
Why it matters: the site translates road‑condition data into lane‑mile treatment needs and cost estimates (crack seal, overlays, seal coat, minor rehabilitation) so the city can prioritize work and present concrete funding choices to residents.
Council members urged broader public engagement and clearer funding proposals before any outreach. Rich (council member) said he wanted taxpayers who previously faced local improvement districts “to be part of the decision a little bit more actively,” and argued the mayor and a larger group of residents should be involved. Denise (council member) asked whether the contract included ongoing support; Becky replied the subscription is annual and that she would ask Kimley‑Horn for an on‑call contract or a fee to answer follow‑up questions.
The presentation included detailed cost breakdowns the site produced for 2025: Becky cited a $561,000 estimate for crack seal/base repairs and seal coat work and identified smaller line items such as a roughly $20,000 mill/overlay package. The dashboard also showed lane‑mile totals by treatment type for each year of the scenario. Becky exported portions of the database to an Excel file (about 100 pages) and said she would ask Kimley‑Horn to add more flexible export filters.
Staff and council discussed a separate heavy‑haul construction project on East Ocean Shores Boulevard that is scheduled to stage in October and finish in late 2026–early 2027. Becky said she had spoken with John Shaw and that the contractor expects “over 3,000 truckloads” of rock, which could cause additional pavement deterioration; she added the contractor will be “paying to repair the damage they’ve done,” and that both the city and the contractor will capture baselines of road condition ahead of the hauling.
Next steps described in the meeting were all procedural rather than formal votes: staff will ask Kimley‑Horn for rates to provide on‑call follow‑up, schedule a local vendor to review crack‑seal opportunities, and prepare draft funding options staff could present at a town hall. Denise suggested an advisory ballot to voters as an option in November 2026 to test public preferences among funding choices; council members did not commit to a date or a directive. No motions or votes occurred on the pavement plan during the discussion.
The presentation also identified additional asset layers the city could add to the system, such as signs and pavement markings, and Becky said the city has not purchased those layers but could enable them through Kimley‑Horn if it chooses. Becky closed by saying the tool should help the city maintain a high PCI if staff and council align on budget priorities.
