Parking Access and Revenue Control Services

The vendor is required to provide a parking access and revenue control system (PARCS) for its downtown state campus.
- A parking access and revenue control system (PARCS) to support our parking garages and gated lots.
- Given the complexity of parking operations, administration and operational management entailed, the vision is to provide a comprehensive, integrated, and web-based, and vendor hosted solution on a single platform.
- This modern system will take advantage of the latest in technology, customer service applications for IOS/android mobile devices, and dashboard user interfaces for administrative and field staff use.
- The new system must integrate with the existing parking management system (aims) and agency ERP (workday). Challenges in the past have included:
• System frequently goes offline causing the loss of gate and revenue control
• Delayed gate response time after swipes
• Audio and video communication at entry/exit gates failed
• System inability to handle hybrid permits
• Reports are not robust and cause interface to crash
• Limited functionality with validation codes
- PARCS includes:
• Access for monthly, daily and transient parkers
• System must be designed with an open API system to allow various tokens for entry
• Revenue control for transient parkers
• Point of sale functionality for transient parkers
• Customer interface via smartphone or desktop for all services
• Integrated communications and functionality
• Queries, reports, and data display
• Provide mechanisms to strengthen internal controls and minimize theft and loss of revenue
• Ensure flexibility and scalability for future needs to expand the system
• System connects to surveillance camera for intercom applications in command center.
• Must integrate with workday ERP and aims parking management system.
• System shall be online and operational 99.99% of the time; excludes scheduled preventative maintenance.
• credit card payment system must either use first data merchant services, LLC (a subsidiary of fiserv) as the processor (preferred) or be certified to integrate with fiserv.
- Employee/student requirements.
• Multi-token entry/exit (badge or plate)
• Ability to manage lot entry by day (5x per week, 3x per week, 2x per week)
• Ability to manage multiple location assignments
- Patient-visitor requirements (transient parking).
• Mobile payment option
• Secure pay stations
• Multiple payment options
• Provide electronic coupons/validation that may be presented in lanes or through mobile payment
- Software/reporting requirements
• System must have the ability to accurately document revenues generated by the parking operations
• Dashboard – easily understood by non-parking specialist
• Must have the potential to increase efficiency of operation and maintenance
• Reporting options to include standard and customize reporting options
• Capability to export data to common workplace tools like word or excel
• Provide multiple report view options, visual representation of key performance indicators, and the ability to store queries in multiple output formats
• Ability to run schedule reports
- PARCS software to include:
• Validations reporting
• Web workstation
• Access control
• Revenue management by type/by lot
• Space management
• Count and monitoring (real time)
• The system must document parking activity and generate activity reports.
• All reports shall be available on-line and on demand for client personnel who have proper password access and assigned permissions.
• All reports must query, filter and sort, transactions by date/time, location, field device, unique identifier, transaction type, or license plate number, at a minimum
• Capture, record, and report separately all exception transactions that could not be processed 100% and automatically by the system (card pass-back, entry without permit, etc.)
• The system must support the scheduling of reports to automatically run a desired time or on a desired schedule.
• Users shall be able to designate e-mail recipients for these reports.
• The details of the scheduled reports including email recipients shall be editable after scheduling.
• All reports must query, filter and sort, transactions by date/time, location, field device, unique identifier, transaction type, or license plate number, at a minimum
• Capture, record, and report separately all exception transactions that could not be processed 100% and automatically by the system (card pass-back, entry without permit, etc.)
• The PARCS must be an open-architecture system where all interfaces (hardware and software) conform to national and international organization for standardization (ISO) standards.
- Contract Period/Term: 3 years
- Non-Mandatory Site Visit Date: April 24, 2025
- Questions/Inquires Deadline: April 28, 2025