Comprehensive Parking and Transportation Management System

The vendor required to provide comprehensive parking and transportation management system that may include hardware, software, analytics, customer-facing tools, and operational support.
- The system should support a largely ungated, pay-by-plate and pay-by-space environment, while remaining flexible enough to accommodate gated or controlled-access facilities where required.
- Functional areas
1. Permit management and sales 
•    The system should support a fully virtual permit environment, including: functionally using the customer’s license plate as their primary credential; daily, weekly, semesterly, and annual permitting options; scheduled payroll deductions and recurring payment options; pro-rating, refunds, returns, and virtual inventory management; permit and customer classifications and eligibility rules; supplemental and upgraded permitting ability (e.g., ADA-accessible, electric vehicle charging, carpooling, or other special access permissions; support for multiple vehicles, family members, and shared permits; waitlisting and reserved space management; contractor, vendor, and departmental permit workflows; automated notifications, expirations, and audit and action logs of users.
2. Payment and financial management 
•    The system should provide intuitive point-of-sale and digital payment options; pay-by-plate functionality; transparent transaction fee structures; departmental billing and reconciliation workflows; import or export and integrative functionality with PeopleSoft and other university financial systems; robust reporting and reconciliation tools. 
•    The university requires that all transactions be processed through Fiserv.
3. Event parking management 
•    The system should include integrative event parking capabilities, including: online event intake and request workflows; inventory management for parking spaces, equipment, and staffing; conflict detection and overbooking prevention; event-specific permitting, validation, and enforcement; pricing and billing by department and event; robust reporting tools including day-of event analytics; communications to event planners, guests, and staff; event-level utilization, revenue, and performance reporting.
4. Enforcement and compliance 
•    The system should support modern, efficient enforcement operations, including: license plate recognition (LPR)-based enforcement using fixed and mobile (vehicle-mounted) cameras; compatibility with iOS and android handheld devices; electronic citation issuance and delivery; officer activity tracking and reporting; zone-based, preferably ai assisted, route planning; geo-fenced timekeeping; integration capabilities with security systems and body worn camera workflows, where applicable.
5. Occupancy, analytics, and wayfinding 
•    The system should provide real-time and predictive occupancy data; public-facing availability displays and wayfinding; ai-driven forecasting and utilization analytics; custom dashboards and reports for varying user roles.
6. Safety, security, and integrations 
•    The system should integrate with: university police department cctv and other security platforms (Motorola and avigilon); CBORD and CSGOLD card access and mobile credential systems; banner and PeopleSoft systems; university single sign-on (SSO) and duo mobile authenticator, where applicable. 
•    Compatibility with parking guidance systems, Genetec, and park-Zen are required. 
•    Respondent should note any other system compatibility.
7. Customer service and communications 
•    Respondents should describe customer support models, including hours, channels, and service level agreements (SLAs); dispute, refund, and error resolution workflows; division of responsibilities between respondent, respondent’s vendors or any of its subcontractors, and university; and mass communication and notification capabilities, including channels and precautions pertaining to personally identifying information (PII).