Pay Parking Mobile Payment Application

The Vendor is required to provide mobile payment service providers to supply mobile parking applications and associated technology to supplement and integrate with the City’s on/off-street parking pay stations and parking enforcement technology (Genetec).
- The City utilizes a Parking-as-a-Service model in which equipment supply and maintenance are provided by a third-party contractor, while enforcement is managed internally by the City’s Division.
- Mobile parking transactions currently represent a growing portion of overall parking activity and are expected to continue increasing over the term of this Contract.
- The City currently utilizes a single-provider mobile payment application and intends to transition to a model that supports multiple providers accessible through a unified interface.
- Required to integrate with:
• Existing and future parking paystations
• The city’s parking enforcement systems, including genetec ALPR and fieldticket
• The city’s preferred payment processor
- Implementation and Deployment
1. Deployment and Implementation
• Full deployment of the solution within thirty (30) calendar days of Contract execution
• Completion of all system configuration, integration, and testing prior to launch
• Coordination with the City and third-party providers as required
• Completion of user acceptance testing and validation of system Functionality
• Provision of all documentation, training, and implementation support
2. Customer Support and Service Level
• Provision of customer service through a dedicated call centre
• Minimum system availability of 99.9 percent excluding scheduled maintenance
• Support hours aligned with the city’s parking enforcement hours
• Escalation procedures for all issues including critical failures
• Defined response and resolution timelines
3. System Integration
• Full integration with the City’s existing and future systems, including:
• Genetec ALPR enforcement systems
• Fieldticket ticketing system
• Existing and future parking paystations
• Provision of all APIS and integration tools
• Contractor responsible for all integration costs and coordination
4. Software and System Updates
• Provision of all application, software, and firmware updates at no cost to the City
• Minimum thirty (30) days advance notice of updates
• Detailed description of changes and impacts
• Testing to ensure continuity of service prior to deployment
- Application Requirements
1. Core Functionality
• Parking session initiation, extension, and termination
• Countdown timer and expiry notifications
• Geo-location and zone identification
• Mobile and web-based access
• Support for iOS and android platforms
• Ability to support future operating systems with material market Presence
2. Customer Interface and Transaction Process
• Clear display of parking rates and options
• Confirmation of Licence plate and location
• Transaction summary prior to payment
• Confirmation of completed transaction
• Automated expiry reminders
• Option to extend parking sessions where permitted
• Issuance of electronic receipts with full cost breakdown
3. Cloud-based Management and Reporting Tools
• Access to operational and financial reporting
• Ability to generate custom reports
• Real-time system monitoring and alerts
• Audit and revenue control features
• Remote configuration of parking rates and zones
• Detailed operational, enforcement, utilization, and revenue reporting capabilities to support city and regional reporting requirements, including translink-related reporting where applicable
- Multi-Provider Environment Requirements
• Compatibility with a multi-provider payment environment
• Ability to operate within a standardized zone structure defined by the city
• Provision of consistent and reliable data for enforcement purposes
• Prevention of duplicate or conflicting transactions
• Support for a unified user experience across providers
• The city is seeking operational models where either the city or the contractor may act as merchant of record
• Clearly identify processing model and limitations
- Payment Processing and Financial Model
1. Payment Processing
• Integration with major payment processors such as county
• Ability to support future payment service providers as required by the city
• Identification of whether the proposed model requires the city or the contractor to act as merchant of record
• Description of PCI responsibilities, payment flow, and operational impacts associated with the proposed model
2. Convenience Fee Model
• The contractor will be compensated through a convenience fee charged to the end user
• No direct cost to the city unless otherwise proposed
• All convenience fees must be clearly disclosed to users
• All convenience fees are subject to prior written approval by the city
• No changes to fees without city approval
3. Financial Submission Requirements
• Proposed convenience fee structure
• Any alternative pricing models
• Pricing for both city merchant of record and contractor merchant of record models, where available
• Identification of any PCI, transaction processing, gateway, licensing, or related costs associated with each proposed model
• Estimated annual revenue projections based on city-provided data
• Identification of any costs to the city
• Any proposed revenue-sharing arrangements.