A. The successful Offeror will be responsible for all services necessary to ensure the successful implementation of the System. This includes but is not limited to, managing the project, handling installation and configuration, performing necessary data conversion, and providing hardware (excluding vehicles). In addition, the Offeror will be responsible for conducting training and offering go-live support to ensure a smooth transition and operational success. The system and services must comply with applicable codes and regulations. B. The System will provide all enforcement and administrative functions and associated services that the Current System does, and meet all additional requirements listed herein. C. The System will provide all parking permit capabilities and services required for a unified parking management system as listed herein. i. The System must support online and in-person parking permit applications and payments. Costs per vehicle parking permit will be between $25 and $50. ii. Parking permit types to be managed include: a) Residential parking permits b) Temporary residential visitor parking permits c) Commercial parking permits d) City-owned garage parking permits e) City employee parking permits iii. Residential parking permits applications will be restricted to addresses associated with each parking district. iv. Residential and commercial parking permit applications will require applicants to provide supporting documentation (i.e. proof of address), and a review process to approve/reject applications. v. Temporary residential visitor parking permits will be allowed (potentially at cost) for holders of residential parking permits. vi. All types of parking permits are to be issued to a single vehicle by license plate number (i.e. no hangtags or stickers). vii. The System must allow permits holders to transfer permits to other vehicles (i.e., when a resident purchases a new vehicle). viii. The System must generate the daily GL Export file for parking permits and ticket payments. The GL account for ticket payments is different from the GL account for permit payments. D. Successful offeror will be responsible for data conversion of all outstanding, unpaid tickets from the Current System into the System. Import of existing parking permits is not required. E. The System must ensure security measures of sensitive data such as personal and payment information, to protect against unauthorized access. It must also maintain high availability during normal business operations hours, ensuring uptime and minimal disruptions to users accessing parking permit services both online and in person. Performance should be optimized to handle peak loads efficiently, especially during typical workday hours when demand for parking services may be at its highest. Regular monitoring and incident response protocols should be in place to quickly address any issues affecting security, availability, or system performance. F. Optional Scope of Work – The following additional tasks are not required but will be considered if proposed: i. License Plate Recognition (LPR) – vehicle-based, handheld, or other means of automatically detecting the license plate of a vehicle in a parking permit district to determine if it has a valid parking permit. a) Vehicle-based LPR must support both perpendicular and parallel parked vehicles. b) Collected LPR data must not be retained for vehicles not issued tickets.