Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Waste Management Contracts topic

No spam. Unsubscribe anytime.

Scranton council advances Routeware (formerly Rubicon) waste contract after heated public criticism

2499667 · March 5, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Scranton City Council voted to move an ordinance to a final-reading agenda that would rename and extend the city's waste-management software contract (Rubicon Global LLC to Routeware, Inc.) by 60 months after residents and council members raised performance, data-use and safety concerns.

The Scranton City Council on the evening of the regularly scheduled meeting advanced an ordinance to final-reading that would amend the city's contract with Rubicon Global LLC — renaming the vendor to Routeware, Inc., extending the term by 60 months and updating the price schedule. The move followed public comment and council debate over performance, vendor lock-in, and safety obligations under a new distracted-driving law.

The ordinance (File to Council No. 59 2025; amending File to Council No. 92 of 2021) was read by title and the council voted to move the item to seventh order for possible final passage next week. Council members and residents urged caution and asked for additional operational data before a long-term renewal.

Why it matters: The contract governs the Department of Public Works' routing, data collection and operations-management software for the city's solid waste and recycling fleet. Council members and public speakers said the product has not produced promised savings, and DPW staff reported repeated route errors, alley omissions and equipment concerns since the system's rollout.

Bailey Simrill, a Scranton resident and technology consultant, urged council to delay a multi‑year extension. “I think we should really pause before renewing or extending this contract,” Simrill said, warning that the city had not seen itemized budget savings or independent verification of the product’s return on investment. Simrill also questioned whether taxpayer-funded route and collection data were being used by the vendor to develop commercial products.

Several council members echoed that concern and asked for written contract language about termination rights and performance thresholds. “They failed miserably to perform the past three years,” Council Member Buchanan said of the vendor during debate, adding that leaving a five‑year contract would require proving failure to perform. Council Member King asked the administration for the original renewable-language clause in the contract to clarify whether the city retains a 30/60/90‑day opt‑out.

DPW drivers who met separately with council members told the council that drivers have spent substantial overtime correcting route mapping and that the system’s turn‑by‑turn guidance sometimes resets when drivers deviate to service courtyards or alleys. Council Member McAndrew said drivers have invested time and corrections in the system and that some vehicles are equipped with weight‑recording hardware, though not all trucks were confirmed to have functioning onboard scales.

Council members also raised the impact of Pennsylvania’s new distracted‑driving statute (Title 75) taking effect in June and how mounted versus handheld routing devices might be affected. The administration told council that mounted devices align with state safety standards and that the city retains options to pursue contract remedies if the vendor fails to perform to specifications.

The council's action was procedural: the ordinance passed first reading/reading by title and will appear for possible final passage during next week's meeting. Council members said they could still table the ordinance at final passage if outstanding questions are not answered.

The council also recorded data reported by administration staff that since route optimization launched in December, drivers logged 1,885 "not outs" in the system; the presentation used a previously estimated cost of $63 per go‑back as a reference point. Council members asked for clearer definitions distinguishing a "not out" (driver-logged instance) from a formal go‑back that produces extra trips and costs.

Next steps: Council expects follow-up documentation on the original renewable language in the contract, the number of trucks with functioning scales, an ROI breakdown and responses to CDL/distracted‑driving compliance questions before the item returns for final consideration.

Ending: The first‑reading move preserves the council’s right to table or defeat the ordinance at final vote; members requested supplemental documentation from administration in the coming days.