Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Procurement Fleet Parts topic
No spam. Unsubscribe anytime.
Council hears initial briefing on proposed $40 million auto‑parts contract for city fleet
Summary
City procurement staff presented a first discussion of a proposed $40 million agreement with auto‑parts supplier Napa to cover parts for Tampa’s fleet; staff said current annual parts spend is about $7.5–8 million and the contract ceiling provides flexibility for inflation and tariffs. Formal approval is scheduled for May 15.
Tampa — City staff held a first discussion with the Tampa City Council on a proposed $40,000,000 agreement to supply auto parts for the city fleet and answered council questions about the contract ceiling, eligible uses and budget treatment.
Avia Collino, director with Duponton Asset Management, told council members the item (agenda item 65) requests approval for a $40,000,000 agreement with Napa. “It is a 4 year contract which spans 5 business years,” Collino said, and she added staff would answer council questions.
Council members asked why the contract ceiling was set higher than recent annual spending. Collino said the city is currently “trending at about 7,500,000.0 in parts per year,” and that the $10,000,000 annual ceiling being requested is intended to allow for inflation and potential tariff impacts. She emphasized the city is not guaranteeing $10,000,000 per year to the vendor but is asking for the expenditure authority to accommodate variability.
Council members also clarified eligible uses. Staff said the contract funds can be used for auto parts for the entire municipal fleet, including police and fire vehicles and marine vessels maintained by the city.
Councilmember Carlson asked what would happen if the city spent less than the ceiling in a given year; Dennis Rojero, the city CFO, explained underspending can either be reappropriated by council if identified in time or fall to fund balance at year end for later appropriation.
The briefing closed with staff noting no vote would be taken at the meeting; formal approval was scheduled for May 15.
Ending: Staff will return to the council on May 15 for an approval vote; council members requested clarification on budget controls and the intended uses of the contract authority ahead of that vote.
