Parking Access And Revenue Control System (PARCS) Addendum 1

REQUESTS FOR PROPOSALS
Parking Access and Revenue Control System (PARCS)
Quad Cities International Airport (MLI)
Issued by:
Metropolitan Airport Authority of Rock Island County, IL
Quad Cities International Airport (MLI)

Table of Contents
1. Introduction and Intent ...................................................................................................... 4
2. Procurement Schedule (Tentative) .................................................................................... 4
3. Background and Existing Conditions ................................................................................. 4
4. System Operating Philosophy ........................................................................................... 5
4A. Alternative Operational Philosophy ................................................................................. 5
5. Site Configuration and Lane Quantities ............................................................................. 5
5.1 Entry Lanes (5 Total)....................................................................................................... 5
5.2 Exit Lanes (4 Total) ......................................................................................................... 6
6. Pay-On-Foot (POF) Station ............................................................................................... 7
6A. Administrative Validation/Payment Station .......................................................................... 7
6A.1 Administrative Station Requirement .............................................................................. 7
6A.2 Validation Capabilities .................................................................................................. 7
6A.3 Validation Output .......................................................................................................... 7
6A.5 Pre-Printed Validations ................................................................................................. 8
6A.6 Lost Ticket and Administrative Payments ...................................................................... 8
7. License Plate Recognition (LPR) ....................................................................................... 8
7.1 Entry Behavior ................................................................................................................ 8
7.2 Exit Behavior .................................................................................................................. 8
7.3 LPR Search and Integration ............................................................................................ 8
7A. Monthly Parker Functionality .............................................................................................. 9
7A.1 Monthly Parker Access Methods ................................................................................... 9
7A.2 Monthly Parker and LPR Integration.............................................................................. 9
7A.3 Credential Management................................................................................................ 9
7A.4 Monthly Parker Business Rules................................................................................... 10
7A.5 Reporting and Audit .................................................................................................... 10
7A.6 Optional Mobile Application ......................................................................................... 10
7A.7 Monthly Parker Enrollment and Payment Platform ....................................................... 10
7A.8 Authority Control of Monthly Rates and Complimentary Access ................................... 11
7A.9 Reservation Platform .................................................................................................. 12
8. Premium and Economy Lot Logic .................................................................................... 12
8.1 Unique Lot Flow ............................................................................................................ 12
8.2 Rate Determination ....................................................................................................... 12
8.3 Shared Exit Operation ................................................................................................... 12
9. Payments and PCI Requirements ................................................................................... 13
2

9A.1 Pay Online.................................................................................................................. 13
9A.2 Offline Functionality .................................................................................................... 13
10. Gate Operator Compatibility/Replacement Alternative ....................................................... 13
10.1 Gate Reuse ................................................................................................................ 13
10.2 Gate Replacement Add-Alternative.............................................................................. 13
11. Web-Based Management Portal & Reporting .................................................................... 14
11.1 Portal requirements ..................................................................................................... 14
11.2 Reporting and Search ................................................................................................. 14
11.3 Data Ownership .......................................................................................................... 14
11.4 API Access ................................................................................................................. 14
11.5 Remote Access ........................................................................................................... 14
11.6 Mobile App Access ..................................................................................................... 14
11A. System Status Display Platform ...................................................................................... 15
11A.1 Status Display .......................................................................................................... 15
11A.2 Monitoring Interfaces (Preferred) ............................................................................... 15
11A.3 Web Monitoring ........................................................................................................ 15
11A.4 Email Alerting ........................................................................................................... 15
11B. Network connectivity ...................................................................................................... 15
12. Installation, Training, and Documentation.......................................................................... 15
13. Acceptance Testing .......................................................................................................... 15
14. Pricing and Evaluation ...................................................................................................... 16
15. Reservations of Rights...................................................................................................... 16
Exhibits .................................................................................................................................. 17
EXHIBIT A - Vendor Compliance Matrix ................................................................................. 17
A. General System Architecture .......................................................................................... 17
B. Lane Configuration and Equipment ................................................................................. 18
C. Pay-On-Foot Station ....................................................................................................... 18
D. Lot Logic and Shared Exit............................................................................................... 18
E. License Plate Recognition (LPR) .................................................................................... 19
F. Web Portal, Reporting, and Remote Access .................................................................... 19
EXHIBIT B - Pricing Worksheet.............................................................................................. 20
Pricing Summary ................................................................................................................ 20
EXHIBIT C - Evaluation Scoring Matrix .................................................................................. 20
Evaluation Criteria .............................................................................................................. 20
3

1. INTRODUCTION AND INTENT
The Metropolitan Airport Authority of Rock Island County (the Authority) is soliciting proposals
from qualified vendors to furnish, install, configure, test, train, and support a Parking Access and
Revenue Control System (PARCS) for Quad Cities International Airport (MLI).
The Authority seeks a turnkey solution that improves customer experience, operational
reliability, payment flexibility, system visibility, and administrative control while remaining right-
sized for the Airport's operational scale.
2. PROCUREMENT SCHEDULE (TENTATIVE)
* RFP Issued: February 23, 2026
* Questions Due: March 6, 2026
* Addenda Issued: March 10, 2026
* Proposals Due: March 20, 2026
* Communication and demonstration scheduling March 23-27, 2026
* Anticipated Award: April 21, 2026
* Target Go-Live Window: July 1, 2026
This schedule merely serves as a guide and the Authority reserves the right to change this
schedule at any time, without notice.
Questions regarding this RFP should be directed to RFPs+PARCS@qcairport.com and be
submitted no later than March 6, 2026. No individual at the airport should be contacted outside
this email and timeline for information regarding this RFP, and any such action may negatively
impact that vendor's standing regarding the selection process. Answers to any questions will be
posted on the website by March 10, 2026.
All RFP responses should be directed to RFPs+PARCS@qcairport.com with the subject
c a "PARC " a h b p March 20, 2026. Only written
responses in the following computer document formats will be accepted: Microsoft Word
(DOCX), Adobe PDF (PDF).
RFP respondents will be contacted after March 20, 2026 for any supplemental information,
demonstrations, etc., if necessary. All respondents will be notified of standing no later than April
21, 2026.
3. BACKGROUND AND EXISTING CONDITIONS
Quad Cities International Airport operates public parking facilities serving commercial passenger
traffic. Parking operations include ticketed entry, centralized exit processing, monthly pass
operation, Pay-On-Foot payment options, and administrative validation.
Parking products include:
* Premium Lot
* Economy Lot
The Authority seeks to enhance and modernize its PARCS to support LPR-assisted processing,
contactless payments, improved reporting, centralized system visibility, and full administrative
control.
4

4. SYSTEM OPERATING PHILOSOPHY
The PARCS shall operate as a ticketed system with LPR-assisted identification, where:
* A physical ticket is issued at entry for customer clarity and fallback use
* License Plate Recognition (LPR) is the primary identifier for transaction tracking and exit
processing
* Exit transactions shall be completed automatically using LPR when confidence
thresholds are met
* Ticket presentations on exit shall be optional during normal exit operations
The physical ticket serves as a customer aid and exception fallback, not the primary credential.
4A. Alternative Operational Philosophy
The Authority is open to a conversation over a purely LPR based operational strategy (no ticket
issued), with physical tickets as a fallback when a license plate cannot be captured. If this is an
option, the authority wishes in its demonstration phase to see how the workflow would work for
ticketless entry.
If this method is an option, the submitter should identify the following:
* Entry handling
o Availability of audible and visual triggers on screen and speaker to inform parker
that a ticket is not issued and to proceed into the lot.
o Handling of ticket issuance when LPR confidence is below the threshold.
o Overall description of entry workflow from vehicle approach to lot entry.
* Exit handling
o Process for exit on LPR Only operations.
o Fallback process if a ticket is not issued.
o Audio and visual cues available to improve passenger instruction
o Overall description of exit workflow from vehicle entering the exit lane, to egress
after payment.
* Paid on Foot Processing
o In a purely LPR only environment, how do paid on foot kiosks function to retrieve
and process tickets.
5. SITE CONFIGURATION AND LANE QUANTITIES
5.1 Entry Lanes (5 Total)
* Premium Lot: 2 entry lanes
* Economy Lot: 3 entry lanes
Each entry lane shall include:
* Ticket dispenser
* Vehicle detection and gate operator
* LPR camera and illuminator
* Lane controller capable of local operation during network interruptions
* Intercom or assistance call capability (via Umojo, SIP, or otherwise indicated) to a
vendor of the airport's choosing
* RFID Reader for staff entry, monthly pass-based entry, and administrative access
5

o RFID readers are required to support both Indala 26bit and MIFARE DESFire
EV3
* Lane status indicators as proposed
o Red/Green traffic indicator that should automatically shift if the lane becomes
unusable due to a fault or error which would inhibit vehicles from entering.
5.2 Exit Lanes (4 Total)
* Four shared exit lanes serving both Premium and Economy Lots
Each exit lane shall include:
* Unattended EMV payment terminal supporting chip and contactless, including mobile
wallets
* Ticket reader
* LPR camera and illuminator
* RFID reader for staff egress and monthly pass-based operation
o RFID readers are required to support both Indala 26bit and MIFARE DESFire
EV3
* Vehicle detection and gate operator
* Intercom or assistance call capability (via Umojo, SIP, or otherwise indicated) to a
vendor of the airport's choosing.
* Administrate access via badge scan to issue lost tickets or conduct administrative
functions such as kiosk restart and troubleshooting.
6

6. PAY-ON-FOOT (POF) STATION
The system shall include one Pay-On-Foot station located within the terminal:
* POF Station 1 (Cashless)
o EMV Chip
o EMV Contactless, including mobile wallets
o RFID Reader
RFID readers are required to support both Indala 26bit and MIFARE
DESFire EV3
POF stations shall support:
* Payment by ticket or license plate lookup
* Validation processing
* Intercom or assistance call capability (via Umojo, SIP, or otherwise indicated) to a
vendor of the airport's choosing
* Administrate access via badge scan to issue lost tickets or conduct administrative
functions such as kiosk restart and troubleshooting.
6A. ADMINISTRATIVE VALIDATION/PAYMENT STATION
6A.1 Administrative Station Requirement
The PARCS shall include an administrative station (web portal preferred, but otherwise
indicated) located in the Airport Administration Office for direct parking transaction
management.
The administrative station shall support:
* Ticket validation
* Lost ticket issuance
* Plate-based transaction lookup and payment
* Manual transaction resolution without lane use
This station should be either a web-based page for transactions accessible by Authority-owned
devices or dedicated hardware should the addition of EMV hardware on Authority computers not
be possible.
6A.2 Validation Capabilities
Validation shall be fully configurable by the Authority, including:
* Validation by time, price, and lot
* Partial, full, and indefinite validations
* Validation against ticket, license plate, or both
No validation rules shall be vendor restricted.
6A.3 Validation Output
Validation shall be provided via:
* Printed barcode or QR code credentials, uniquely identifiable and auditable
* Direct electronic validation against ticket or plate records
7

6A.5 Pre-Printed Validations
The Authority should be able to issue pre-printed validations without the need to enter ticket or
plate records which can be set for various validation lengths and issued as needed.
6A.6 Lost Ticket and Administrative Payments
The administrative station shall support:
* Lost ticket issuance per Authority rules
* Plate-based payment without ticket presentation
* Processing of payment or lost ticket with or without the vending of a gate.
* Full audit logging of all actions
7. LICENSE PLATE RECOGNITION (LPR)
7.1 Entry Behavior
At entry, the system shall:
* Capture license plate images
* Generate plate strings with confidence scoring
* Associate plates to issued tickets
* Store images and data for audit and search
7.2 Exit Behavior
At exit, the system shall:
* Identify vehicles by plate
* Retrieve associated transactions
* Apply rates based on lot of entry
* Complete exit without ticket presentation when confidence thresholds are met
Ticket presentation shall reconcile records and flag mismatches.
7.3 LPR Search and Integration
At a minimum, the system shall support:
* Full historical plate search
* Complete transaction history per vehicle
* Plate image review with confidence data
* Store logs and plate records for a minimum of 365 days.
The Authority requests verification of integration capability with third-party platforms such as
security or video management systems (Genetec) to centralize plate reporting and searching. At
a minimum, data should be accessible via an API call, or regularly and automatically exportable
via SFTP, for integration at Authority discretion.
Such integration is preferred but not required and will not affect the decision of the proposal.
8

7A. MONTHLY PARKER FUNCTIONALITY
7A.1 Monthly Parker Access Methods
The PARCS shall support monthly parking access using one or more of the following
methods:
* RFID and NFC physical credential (card, fob, or equivalent) REQUIRED
* Mobile phone-based application or digital credential
* License Plate Recognition (LPR) as a credential
The system shall allow monthly parkers to enter and exit the parking facility an unlimited (or
determined) number of times, subject to Authority-defined rules.
The system shall allow the Authority to configure anti-passback rules to allow or disallow
multiple scans at a location, at the authority's discretion, based on an assigned role or parkers
group.
Submitters should include examples/screenshots of monthly parking methods in action.
7A.2 Monthly Parker and LPR Integration
Monthly parker functionality shall piggyback onto the LPR subsystem to allow ticketless
operation.
The system shall support:
* Association of one or more license plates to a monthly parker account
* Plate-based identification at entry and exit without ticket issuance
* Optional issuance of a physical ticket only if required for exception handling
When a recognized monthly parker vehicle is detected by LPR:
* The gate shall open automatically without ticket issuance
* The transaction shall be logged as a monthly parker event
* No revenue transaction shall be recorded per entry or exit
o Unless an automated payment/card-on-file "Express Pay" method is supported
and configured.
7A.3 Credential Management
The system shall allow authorized Authority personnel to:
* Create, modify, suspend, and terminate monthly parker accounts
* Assign and revoke RFID, NFC, mobile, and plate-based credentials
* Configure effective dates and expiration dates
* Support temporary vehicle changes or multiple vehicles per account, subject to Authority
policy
Credential management shall be available through the web-based management portal and shall
not require vendor intervention.
9

7A.4 Monthly Parker Business Rules
The system shall support configurable rules including:
* Allowed parking products or lots for monthly parkers
* Time-based access restrictions, if any
* Concurrent use rules for multiple vehicles on a single account
* Rates and charges associated with rules
* Grace periods and exception handling
All rules shall be configurable by the Authority at any time without support intervention.
7A.5 Reporting and Audit
The system shall provide reporting for monthly parking, including:
* Active monthly parker accounts
* Entry and exit activity by credential and by plate
* Credential usage history
* Exceptions and access denials
Monthly parker activity shall be searchable by:
* Account
* Credential
* License plate
* Date and time range
7A.6 Optional Mobile Application
If a mobile application is provided, vendors shall describe:
* Supported platforms
* Credential provisioning method
* Offline behavior
* Security controls
A mobile application is preferred but not required.
7A.7 Monthly Parker Enrollment and Payment Platform
The PARCS shall include support for monthly parker enrollment and payment through a
publicly accessible platform provided and supported by the vendor.
The enrollment and payment platform shall allow members of the public to:
* Enroll as monthly parkers
* Pay monthly parking fees through secure online payment methods
* Establish recurring or manual payment options, subject to Authority policy
10