RFP0000014_RFP_Solicitation.pdf

REQUEST FOR PROPOSALS (RFP)

EVENT NO.: RFP0000014

EVENT TITLE: PARKING ACCESS AND REVENUE CONTROL SYSTEM AT MIA

PRE-PROPOSAL CONFERENCE TO BE HELD:

October 21, 2026 at 10:00 AM (local time) 4200 NW. 36th Street, Miami, Florida 331666 Building 5A, 2nd Floor, Conference Room G

ISSUED BY MIAMI-DADE COUNTY:

Strategic Procurement Department for Miami-Dade Aviation Department

MIAMI-DADE COUNTY CONTACT FOR THIS SOLICITATION:

Ernesto Perez, Procurement Contracting Officer

111 NW 1st Street, Suite 1300, Miami, Florida 33128

Telephone: (305) 375-3001

E-mail: ernesto.perez2@miamidade.gov

PROPOSALS DUE:

Refer to Date and Time Specified in Informs

IT IS THE POLICY OF MIAMI-DADE COUNTY (COUNTY) THAT ALL ELECTED AND APPOINTED COUNTY OFFICIALS AND COUNTY EMPLOYEES SHALL ADHERE TO THE PUBLIC SERVICE HONOR CODE (HONOR CODE). THE HONOR CODE

CONSISTS OF MINIMUM STANDARDS REGARDING THE RESPONSIBILITIES OF ALL PUBLIC SERVANTS IN THE COUNTY.

VIOLATION OF ANY OF THE MANDATORY STANDARDS MAY RESULT IN ENFORCEMENT ACTION.

(SEE IMPLEMENTING ORDER 7-7)

Electronic Proposal responses to this RFP are to be submitted through a secure mailbox at Integrated Financial Resources Management System (INFORMS) until the date and time as indicated in this document. It is the sole responsibility of the Proposer to ensure its Proposal reaches INFORMS before the Solicitation closing date and time. There is no cost to the Proposer to submit a Proposal in response to a Miami-Dade County Solicitation via INFORMS. Electronic Proposal submissions may require the uploading of electronic attachments. The submission of attachments containing embedded documents or proprietary file extensions is prohibited. All documents should be attached as separate files. Proposers must allow sufficient time to complete online forms and upload all Proposal documents. All information and documents must be fully entered, uploaded, acknowledged (“Confirm”) and recorded into INFORMS before the date and time of the INFORMS Solicitation End Date, or the system will stop the process and the submission will be considered late and will not be accepted. No part of a Proposal can be submitted via hardcopy, email, or fax. All expenses involved with the preparation and submission of Proposals to the County, or any work performed in connection therewith, shall be borne by the Proposer(s).

A Proposer may submit a modified Proposal to replace all or any portion of a previously submitted Proposal up until the Proposal due date. The County will only consider the latest version of the Proposal.

Requests for additional information or inquiries must be made in writing and submitted using the question/answer feature provided by INFORMS at https://supplier.miamidade.gov. The County will issue responses to inquiries and any changes to this Solicitation it deems necessary via written addenda issued prior to the Proposal due date and time (see Mandatory Online Forms and Addendum Acknowledgement Section of INFORMS site). Proposers who obtain copies of this Solicitation from sources other than through INFORMS risk the possibility of not receiving addenda and are solely responsible for those risks.

If you submit your proposal and subsequently an Addendum is issued, failure to resubmit the proposal by clicking on the “Submit Proposal” button, after acknowledging Addenda or making any edits to your proposal in INFORMS, will result in your proposal not being received by the County.

https://supplier.miamidade.gov/

Miami-Dade County, FL Event No. RFP0000014

Rev.12.16..2025 2

1.0 PROJECT OVERVIEW AND GENERAL TERMS AND CONDITIONS

1.1 Introduction

Miami-Dade County, hereinafter referred to as the County, as represented by the Miami-Dade County Aviation Department (MDAD), is soliciting Proposals for Parking Access and Revenue Control System (PARCS) at Miami International Airport (MIA). The Selected Proposer shall design, build, install, commission, operate, maintain, and provide lifecycle support for PARCS.

The County anticipates awarding a contract for a seven (7) year period, with one (1), three (3)-year option to renew.

The anticipated schedule for this Solicitation is as follows:

Pre-Proposal Conference: See front cover for date, time, and place. Attendance is recommended but not mandatory.

Should you need an ADA accommodation to participate in Pre-Proposal Conference (i.e., materials in alternate format, sign language interpreter, etc.), please contact the ADA Office five days prior to scheduled conference to initiate your request. The ADA Office may be reached by phone at (305) 869-1859 or contact Melissa Parada-Pla at mparada-pla@flymia.com. TTY users may reach the ADA Office by calling the Florida Relay Service at 711.

Deadline for Receipt of Questions: Refer to Date and Time Specified in INFORMS Proposal Due Date: Refer to Date and Time Specified in INFORMS Evaluation Process: To Be Determined Projected Award Date: To Be Determined

1.2 Definitions

Any or all of following words and expressions may be used in this Solicitation and, if so, shall be construed as follows, except when it is clear from the context that another meaning is intended:

1. The words “Airport” or acronym “MIA” to mean Miami International Airport.

2. The term “Board” shall mean the Board of County Commissioners of Miami-Dade County.

3. The term “Code” shall mean the Code of Miami-Dade County, Florida.

4. The words “Competitive Selection Committee” to mean the group of individuals who are tasked with reviewing, evaluating and scoring the Proposals submitted in response to this RFP.

5. The words “Contractor” or “Selected Proposer” to mean the Proposer that receives any award of a contract from the County as a result of this Solicitation, also to be known as “the prime Contractor”.

6. The word “County” to mean Miami-Dade County, a political subdivision of the State of Florida.

7. The words “Cybersecurity Products” to mean software and hardware that include technologies, processes, and practices designed to protect information technology networks, devices, programs, and data from attack, damage, or unauthorized access.

8. The term “Days” shall mean calendar days, unless specifically stated as other.

9. The words “Department” or “MDAD” shall mean the Miami-Dade Aviation Department. Where rights are reserved to the County, MDAD may exercise such rights.

10. The words “Final System Acceptance” shall mean MDAD’s formal written confirmation that the complete Parking Access and

Revenue Control System has been fully installed, configured, integrated, tested, commissioned, documented, and staff trainings conducted to operate in accordance with all requirements of the resultant contract. System Acceptance shall occur after the selected Proposer has successfully completed all required acceptance testing; corrected all Critical and Major Deficiencies; resolved all mailto:mparada-pla@flymia.com mailto:mparada-pla@flymia.com

Rev.12.16..2025 3 remaining punch-list items or provided a County-approved corrective action plan for minor items; completed all required training and knowledge transfer; delivered all required documentation, licenses, warranties, spare parts, configurations, source materials, and other deliverables; and demonstrated stable and reliable operation of the System in MIA’s production environment for the required System Stabilization Period.

11. The words “Heightened Security Review” to mean any and all security screening conducted on County employees with access to

Cybersecurity Products or any other additional security screenings or reviews the County Mayor or County Mayor’s designee determines necessary to protect the security of the County’s information technology networks, devices, programs, and data.

12. The words “Implementation Milestone Credit” shall mean a monetary or other compensatory credit due to the County if the Contractor fails to achieve an Implementation Milestone within the applicable timeframe or otherwise satisfy the milestone performance standards established in the resultant contract agreement.

13. The words “Joint Venture” to mean an association of two or more persons, partnerships, corporations, or other business entities under a contractual agreement to conduct a specific business enterprise for a specified period with both sharing profits and losses.

The Joint Venture must be a legally formed entity prior to Proposal submission.

14. The words “Lifecycle Management Plan” shall mean selected Proposer’s comprehensive plan for managing, maintaining, supporting, securing, upgrading, replacing, and ultimately transitioning or retiring all System components throughout their useful and contractual life. The plan should address all hardware, software, firmware, licenses, subscriptions, interfaces, databases, operating systems, third-party products, cloud services, and related infrastructure comprising the Parking Access and Revenue Control System. The plan should identify each component’s expected useful life, manufacturer support period, maintenance requirements, upgrade and replacement schedule, end-of-sale and end-of-support dates, obsolescence risks, cybersecurity requirements, estimated lifecycle costs, and procedures for migration, data preservation, replacement, and disposal without disrupting MIA’s parking operations.

15. The words "Licensed Software" to mean the software component(s) provided pursuant to the Contract.

16. The word “Network” shall mean an interconnected system of devices, servers, and communication infrastructure that enables the secure exchange of data, information, and services across an organization.

17. The words “Turnkey Solution” to mean a complete, fully integrated, and ready-for-use Parking Access and Revenue Control System (PARCS) provided by the Selected Proposer, inclusive of all necessary hardware, software, licenses, equipment, materials, design, configuration, installation, integration, testing, commissioning, training, documentation, and other components and services required to meet the County’s requirements. The Selected Proposer shall be responsible for delivering a fully functional system that satisfies the requirements of this Solicitation and Exhibit A – Technical Requirements, without the need for the County to procure additional products or services necessary for the system’s intended functionality, unless expressly excluded or otherwise specified in the resultant Contract.

18. The words “General Allowance Account” shall mean the designated funding established under the resultant Agreement for County-authorized contingencies, including eligible Consumer Price Index (CPI) adjustments for maintenance and support, eligible Producer Price Index (PPI) adjustments for separately authorized additional equipment, and other approved additional products or services, subject to the limits, approvals, and procedures in Article 53 of Attachment E – Draft Agreement.

19. The words “Produced in the United States” to mean, with respect to Cybersecurity Products, a product for which all development and production occurs in the United States.

20. The word “Proposal” to mean the properly signed and completed written good faith commitment submitted by the Proposer in response to this Solicitation, as amended or modified through negotiations.

21. The word “Proposer” to mean the person, firm, entity or organization, as stated on the Submittal Form, submitting a Proposal to this Solicitation.

22. The words “Responsible Proposer” shall refer to a Proposer that has the capability in all respects to fully perform the contract requirements and the integrity and reliability that will assure good faith performance.

Rev.12.16..2025 4

23. The words “Responsive Proposer” shall refer to a Proposer that has submitted a Proposal that conforms in all material aspects to the Solicitation.

24. The words “Scope of Services” to mean Section 2.0 of this Solicitation, which details the work to be performed by the Contractor.

25. The word “Solicitation” to mean this Request for Proposals (RFP) document, and all associated addenda and attachments.

26. The word “Subcontractor” to mean any person, firm, entity or organization, other than the employees of the Contractor, who contracts with the Contractor to furnish labor, or labor and materials, in connection with the Services to the County, whether directly or indirectly, on behalf of the Contractor.

27. The words “Work”, “Services”, “Program”, or “Project” to mean all matters and things that will be required to be done by the Contractor in accordance with the Scope of Services, and the terms and conditions of this Solicitation.

1.3 General Proposal Information

Pursuant to Florida Statutes Section 287.05701, Proposers are hereby notified that the County will not request documentation of, or consider, the social, ideological or political interests of a Proposer when determining if a Proposer is a responsible vendor nor will the County give preference to a Proposer based on the Proposer’s social, ideological or political interests.

The County may, at its sole and absolute discretion, reject any and all or parts of any or all Proposals; accept parts of any and all Proposals; further negotiate project elements including but not limited to project fees, revenues or pricing; postpone or cancel at any time this Solicitation process; or waive any irregularities in this Solicitation or in the Proposals received as a result of this process. In the event that a Proposer wishes to take an exception to any of the terms of this Solicitation, the Proposer shall clearly indicate the exception in its Proposal. The County shall treat the Proposer's inclusion of exceptions, assumptions or alternate terms in the Proposal as requests to negotiate project elements, and the inclusion of same shall not result in the Proposal being deemed non-responsive. The County is not bound to accept any exceptions, assumptions or alternates during negotiations, and the County shall consider a Proposal submitted to be an offer to supply goods or services in strict compliance with the terms of this Solicitation. Exceptions, assumptions or alternates may be considered by the County during negotiations to the extent such exceptions, assumptions or alternates do not materially change any provision of the Solicitation. The County reserves the right to request and evaluate additional information from any Proposer regarding Proposer’s responsibility after the submission deadline as the County deems necessary.

The Proposer’s Proposal will be considered a good faith commitment by the Proposer to negotiate a contract with the County, in substantially similar terms to the Proposal offered and, if successful in the process set forth in this Solicitation and subject to its conditions, to enter into a Contract substantially in the terms herein. Proposer’s Proposal shall be irrevocable until Contract award unless the Proposal is withdrawn. A Proposal may be withdrawn in writing only, addressed to the County contact person for this Solicitation, prior to the Proposal due date and time, or upon the expiration of one hundred eighty (180) calendar days after the opening of Proposals.

As further detailed in the Submittal Form, Proposers are hereby notified that all information submitted as part of, or in support of Proposals will be available for public inspection after opening of Proposals, in compliance with Chapter 119, Florida Statutes, (the "Public Record Law”)

Any Proposer who, at the time of Proposal submission, is involved in an ongoing bankruptcy as a debtor, or in a reorganization, liquidation, or dissolution proceeding, or if a trustee or receiver has been appointed over all or a substantial portion of the property of the Proposer under federal bankruptcy law or any state insolvency law, may be found non-responsible.

To request a copy of any code section, resolution and/or administrative/implementing order cited in this Solicitation, contact the Clerk of the Board at (305) 375-5126, Monday- Friday, 8:00 a.m. – 4:30 p.m.

1.4 Cone of Silence

Pursuant to Section 2-11.1(t) of the Code of Miami-Dade County, as amended (the “Code”), a “Cone of Silence” is imposed upon each RFP or RFQ after advertisement and terminates at the time a written recommendation is issued. The Cone of Silence prohibits any communication regarding RFPs or RFQs between, among others:

▪ potential Proposers, service providers, lobbyists or consultants and the County’s professional staff including, but not limited to, the County Mayor and the County Mayor’s staff, County Commissioners or their respective staffs;

Rev.12.16..2025 5

▪ the County Commissioners or their respective staffs and any member of the County's professional staff, other than any professional staff member who is designated by the County Mayor to engage in such communications; or

▪ potential Proposers, service providers, lobbyists or consultants, any member of the County’s professional staff, the Mayor, County Commissioners or their respective staffs and any member of the respective Competitive Selection Committee.

The provisions do not apply to, among other communications:

▪ oral communications with the staff of the Vendor Outreach and Support Services Section, the responsible Procurement Contracting Officer (designated as the County’s contact on the face of the Solicitation), provided the communication is limited strictly to matters of process or procedure already contained in the Solicitation document;

▪ oral communications at pre-Proposal conferences and oral presentations before Competitive Selection Committees during any duly noticed public meeting, public presentations made to the Board of County Commissioners (the “Board”) during any duly noticed public meeting;

▪ recorded contract negotiations and contract negotiation strategy sessions; or

▪ communications in writing at any time with any County employee, official or member of the Board of County Commissioners unless specifically prohibited by the applicable RFP or RFQ documents.

When the Cone of Silence is in effect, all potential vendors, service providers, bidders, lobbyists and consultants shall file a copy of any written correspondence concerning the particular RFP or RFQ with the Clerk of the Board, which shall be made available to any person upon request. The County shall respond in writing (if County deems a response is necessary) and file a copy with the Clerk of the Board, which shall be made available to any person upon request. Written communications may be in the form of e-mail, with a copy to the Clerk of the Board at clerkbcc@miamidade.gov.

All requirements of the Cone of Silence policies are applicable to this Solicitation and must be adhered to. Any and all written communications regarding the Solicitation are to be submitted only to the Procurement Contracting Officer with a copy to the Clerk of the Board. The Proposer shall file a copy of any written communication with the Clerk of the Board. The Clerk of the Board shall make copies available to any person upon request.

1.5 Communication with Competitive Selection Committee Members Proposers are hereby notified that direct communication regarding this Solicitation, written or otherwise, to individual Competitive Selection Committee Members or, to the Competitive Selection Committee as a whole, are expressly prohibited. Any oral communications with Competitive Selection Committee Members other than as provided in Section 2-11.1 of the Code, are prohibited.

1.6 Pre-Proposal Conference

It is highly recommended that Proposers attend the Pre-Proposal Conference in personto become familiar with any conditions which may, in any manner affect the services to be provided. Proposers are advised to carefully examine the requirements and specifications in this Solicitation, and to become thoroughly aware regarding all conditions and requirements that may in any manner affect the work to be performed under the contract. No additional allowances will be made because of lack of knowledge of these conditions. The Conference is as follows:

Pre-Proposal Conference will be held on October 21, 2026 at 10:00 a.m. (Eastern Standard/Daylight Time) at Miami-Dade County Aviation Department, 4200 N.W. 36th Street, Miami, Florida 33166, Building 5A, 2nd Floor, Conference Room G, and will also be available via Teams. To join the Teams meeting, please visit https://www.microsoft.com/en-us/microsoft-teams/join-a-meeting and join Meeting ID: 243 090 776 087 754, Passcode: 5eT63aZ9

Members of the public are not required to enter their name to join the meeting if they do not wish to do so. Members may identify themselves as “Public Attendee.”

Members of the public will be permitted to pose questions at the end of the Conference.

• Meeting Room will open at 10:00 a.m. to admit participants

• Host: Procurement Officer Ernesto Perez

• Host Username: ernesto.perez2@miamidade.gov

• ADA Contact: ernesto.perez2: ernesto.perez2@miamidade.gov

• Link to Teams: https://www.microsoft.com/en-us/microsoft-teams/join-a-meeting mailto:clerkbcc@miamidade.gov https://www.microsoft.com/en-us/microsoft-teams/join-a-meeting mailto:marie.williams@miamidade.gov https://www.microsoft.com/en-us/microsoft-teams/join-a-meeting

Rev.12.16..2025 6

Proposers are requested to arrive promptly as the meeting will start on time, and to have access to and/or a copy of the Solicitation on hand during the Conference. The Cone of Silence does not apply to this meeting, allowing for any questions to be addressed with representatives from Miami-Dade County. This is a public meeting and multiple members of individual community councils may be present. The County is not responsible for any costs incurred by potential Proposers to attend the Conference.

1.7 Public Entity Crimes

Pursuant to Paragraph 2(a) of Section 287.133 of the Florida Statutes, a person or affiliate who has been placed on the convicted vendor list following a conviction for a public entity crime may not submit a Proposal for a contract to provide any goods or services to a public entity; may not submit a Proposal on a contract with a public entity for the construction or repair of a public building or public work; may not submit Proposals on leases of real property to a public entity; may not be awarded or perform work as a contractor, supplier, subcontractor, or consultant under a contract with any public entity; and, may not transact business with any public entity in excess of the threshold amount provided in Section 287.017 of the Florida Statutes for Category Two for a period of thirty-six (36) months from the date of being placed on the convicted vendor list.

1.8 Lobbyist Contingency Fees

a) In accordance with Section 2-11.1(s) of the Code, after May 16, 2003, no person may, in whole or in part, pay, give or agree to pay or give a contingency fee to another person. No person may, in whole or in part, receive or agree to receive a contingency fee.

b) A contingency fee is a fee, bonus, commission or non-monetary benefit as compensation which is dependent on or in any way contingent upon the passage, defeat, or modification of: 1) any ordinance, resolution, action or decision of the County Commission;

2) any action, decision or recommendation of the County Mayor or any County board or committee; or 3) any action, decision or recommendation of any County personnel during the time period of the entire decision-making process regarding such action, decision or recommendation which foreseeably will be heard or reviewed by the County Commission or a County board or committee.

1.9 Collusion

In accordance with Section 2-8.1.1 of the Code, where two (2) or more related parties, as defined herein, each submit a Proposal for any contract, such Proposals shall be presumed to be collusive. The foregoing presumption may be rebutted by the presentation of evidence as to the extent of ownership, control and management of such related parties in preparation and submittal of such Proposals. Related parties shall mean Proposer, the principals, corporate officers, and managers of the Proposer; or the spouse, domestic partner, parents, stepparents, siblings, children or stepchildren of a Proposer or the principals, corporate officers and managers thereof which have a direct or indirect ownership interest in another Proposer for the same contract or in which a parent company or the principals thereof of one Proposer have a direct or indirect ownership in another Proposer for the same contract. Proposals found to be collusive shall be rejected. Proposers who have been found to have engaged in collusion may be considered non-responsible, and may be suspended or debarred, and any contract resulting from collusive bidding may be terminated for default.

1.10 Contracting with Entities of Foreign Countries of Concern Prohibited By submitting a proposal or otherwise entering into, a contract under this Solicitation, the Proposer affirms that it is not in violation of Section 287.138, Florida Statutes (F.S.) titled Contracting with Entities of Foreign Countries of Concern Prohibited. Proposer further affirms that it is not giving a government of a foreign country of concern, as listed in Section 287.138, F.S., access to an individual’s personal identifying information if: a) the Proposer is owned by a government of a foreign country of concern; b) the government of a foreign country of concern has a controlling interest in the Proposer; or c) the Proposer is organized under the laws of or has its principal place of business in a foreign country of concern as is set forth in Paragraphs 2(a)–(c) of Section 287.138, F.S.

This affirmation by the Proposer shall be in the form attached to this Solicitation as Contracting with Entities of Foreign Countries of Concern Prohibited Affidavit.

1.11 Purpose Driven Procurement Practices

The County is committed to responsible stewardship of resources. To the extent allowed by law, the County will continue to explore and pursue purpose driven procurement, development and business practices that: (a) are environmentally friendly; (b) foster and integrate local community benefits including, opportunities for local and small business participation, internships, job fairs, mentorship, vocational and technical training; (c) support safe and fair labor practices and ethical behavior, and (d) maximize fiscally responsible “high value, high impact” actions.

Rev.12.16..2025 7

1.12 Human Trafficking Affidavit

By entering into, amending, or renewing a contract under this Solicitation, the Proposer affirms that it does not use coercion for labor or services and complies with the provisions of Section 787.06, Florida Statutes (“F.S.”), “Human Trafficking”. This attestation by the Proposer shall be in the form attached to this Solicitation as the Human Trafficking Affidavit.

1.13 Title VI Solicitation Notice

As a condition of a grant award, the Sponsor shall demonstrate that it complies with the provisions of Title VI of the Civil Rights Act of 1964 (42 U.S.C. §§ 2000d et seq) and implementing regulations (49 CFR part 21) including amendments thereto, the Airport and Airway Improvement Act of 1982 (49 U.S.C. § 47123), the Age Discrimination Act of 1975 (42 U.S.C. 6101 et seq.), Section 504 of the Rehabilitation Act of 1973 (29 U.S.C. § 794 et seq.), the Americans with Disabilities Act of 1990 (42 U.S.C. § 12101, et seq.), U.S.

Department of Transportation and Federal Aviation Administration (FAA) Assurances, and other relevant civil rights statutes, regulations, or authorities, including any amendments or updates thereto. Guidelines for Contract Provisions for Obligated Sponsors and Airport Improvement Program Projects Issued on March 17, 2026, Page 27. This may include, as applicable, providing a current Title VI Program Plan to the FAA for approval, in the format and according to the timeline required by the FAA, and other information about the communities that will be benefited and impacted by the project. A completed FAA Title VI Pre-Grant Award Checklist is required for every grant application, unless excused by the FAA. The Sponsor shall affirmatively ensure that when carrying out any project supported by this grant that it complies with all federal nondiscrimination and civil rights laws based on race, color, national origin, sex, creed, age, disability, genetic information, in consideration for federal financial assistance. The Department’s and FAA’s Office of Civil Rights may provide resources and technical assistance to recipients to ensure full and sustainable compliance with Federal civil rights requirements. Failure to comply with civil rights requirements will be considered a violation of the agreement or contract and be subject to any enforcement action as authorized by law.

2.0 SCOPE OF SERVICES

2.1 Background

MIA utilizes a Parking Access and Revenue Control System (PARCS) which encompasses a combination of manual and automated equipment and software that controls parking access by patrons and provides for revenue accountability through various layers and types of systems. MDAD intends to replace the currently installed PARCS to align with current technological improvements in the industry. The Selected Proposer shall configure, design commission, operate, maintain, and provide lifecycle support for the PARCS solution under a integrated implementation, and maintenance delivery model in which MDAD shall hold title to all deployed hardware, perpetual software licenses, and configuration data. The Selected Proposer shall serve as the single third-party service provider responsible for the PARCS system for the duration of the resulting agreement and any exercised renewal options.

The PARCS shall provide monitored ingress and egress control, transient and contract parking management, automated and attended payment processing, license plate recognition (LPR), and integration with Park Assist (parking guidance system), SunPass (Florida’s electronic toll system), and the Department's reservation, accounting, identity, and reporting platforms. The PARCS shall serve no fewer than 15,414 public and employee parking spaces across the Dolphin Garage, Flamingo Garage, Park 1, Park 6, Park 8, the High Vehicle Lot, with the ability to scale additional facilities.

MDAD's strategic intent is to procure a multiple entry and exit methods, including traditional paper-ticket processing, credit-card-in / credit-card-out (CCI/CCO), SunPass, RFID employee/VIP credentials, and advance-reservation digital credentials, so that MDAD may determine the appropriate mix of methods for its customer base. App-driven ticketless entry/exit and LPR-driven ticketless entry/exit shall be available as optional, MDAD-activatable capabilities that MDAD may enable, expand, or restrict over the term as customer demographics, technology adoption, and operational needs evolve. License Plate Recognition (LPR) shall not serve as the primary authorization method for entry or exit; where used, LPR shall support and enhance vehicle identification, transaction matching, exception resolution, and revenue assurance.

The resulting agreement is structured as a integrated implementation, and maintenance engagement. Title to all deployed hardware, perpetual software licenses, and configuration baselines shall vest in MDAD at Final System Acceptance. The Department shall pay (i) a fixed, milestone-based capital price for the implementation phase, and (ii) a fixed recurring fee for ongoing operation, maintenance, customer-facing services, and lifecycle support of the MDAD-owned PARCS. All parking revenue collected through the system shall remain the property of the Department and shall be remitted in accordance with the terms of the resulting agreement.

Rev.12.16..2025 8

The resulting agreement shall include service, data ownership and portability provisions, exit-transition obligations, and continuous-improvement commitments aligned with MDAD's enterprise technology and revenue assurance standards. Detailed technical and performance requirements are set forth in Exhibit A, Technical Requirements.

2.2 Services to be Provided

The Selected Proposer shall provide a turn-key, integrated implementation, and maintenance PARCS solution. Upon Final System Acceptance, MDAD shall hold title to deployed hardware, perpetual software licenses, and configuration baselines, and the Selected Proposer shall serve as the single third-party service provider responsible for ongoing operation, maintenance, customer-facing services, and lifecycle support of the system. The solution shall be a PARCS solution comprised of, at a minimum: hybrid cloud/edge core software, lane controllers and field hardware, automated entry and exit equipment, LPR cameras, pay-on-foot and pay-in-lane payment devices, customer assistance/intercom infrastructure, a customer-facing web and mobile experience, a back-office operations and reporting suite, and all required integrations to specified third-party systems, and MDAD's existing parking, reservation, and finance ecosystem. The PARCS shall utilize commercial off-the-shelf hardware and peripherals to the maximum extent feasible and shall not require bespoke customization to satisfy core business rules.

As the core platform of the PARCS, the solution shall include, but is not limited to:

a. Entry and exit lane control across all in-scope public and employee facilities

b. App-driven ticketless processing as optional, with CCI/CCO as an acceptable alternate primary flow, and paper ticket issuance as a fallback only. LPR serves as the recognition sensor and revenue assurance technology supporting these flows.

c. SunPass and Park Assist integration, plus identity, payment gateway, reservation, and BI integrations

d. Centralized configuration, rate engine, exception handling, and revenue reporting

e. Customer self-service for accounts, vehicles, payment methods, receipts, and disputes

f. Field-monitored, gated lane operation with underwriters laboratories (UL) 325–compliant operators and entrapment protection

The Selected Proposer shall perform the general services to be provided described herein. The PARCS shall meet all required functionality to support the Department's parking operations and the traveling public, while enabling refresh and evolution of the PARCS over the contract term.

2.2.1 General Requirements

The Selected Proposer shall be responsible for the design, manufacture, supply, installation, integration, testing, commissioning, maintenance, and lifecycle support of the MDAD-owned PARCS at MIA. Services shall include, but are not limited to:

a. Project management, program administration, and coordination

b. System engineering and detailed design and stakeholder design workshops

c. System development, configuration, integration, factory acceptance testing (FAT) and site acceptance testing

(SAT), and commissioning

d. All required coordination with the Department's designated representative (the Airport Representative (AR))

e. In-person end-user training (technical-support, and train-the-trainer) of Department operations, finance, information technology (IT), maintenance representatives. Refresher training may be conducted online or through recorded sessions.

f. Monitoring, preventive maintenance, and corrective maintenance.

g. Warranty management, software lifecycle management, and patch/upgrade delivery

h. All requirements of Exhibit A- Technical Requirements

2.2.2 Reporting and Scheduling

Selected Proposer will provide lifecycle support for the MDAD-owned PARCS, and shall prepare, maintain, and submit to MDAD all documents required to install, test, operate, and continuously improve the system. Such documents include, but are not limited to:

Rev.12.16..2025 9

a. Project management plan (PMP) and master schedule

b. System design (30%, 60%, 90%, and for-construction submittals)

c. Implementation, phasing, and cutover plans (including lane-by-lane impact and rollback)

d. Submittal documents for each major component and integration

e. Installation work plans and method statements

f. Stakeholder communication plan

g. Quality assurance, FAT, SAT, user acceptance testing (UAT), and system validation plans and results

h. Operations runbooks, standard operating procedures (SOP), and end-user documentation

i. As-built drawings, network diagrams, and configuration baselines

j. Ongoing service reports, service performance reports, and root-cause analyses

2.2.3 Coordination and Integration of Systems and Devices

The Selected Proposer shall coordinate with the AR, MDAD personnel, and various outside vendors to minimize operational impact. Additionally, the Selected Proposer shall coordinate with the providers of the following systems (or successor) and ensure the proposed solution supports all required integrations. The Selected Proposer shall conduct a thorough review and assessment of all necessary interfaces. The systems listed in Exhibit A, Section 2.1.4 Integration Requirements, represent the primary integrations currently anticipated; however, the Selected Proposer shall identify and address any additional interfaces necessary to provide a fully functional and integrated solution.

Additionally, the Selected Proposer shall provide, coordinate and ensure the proposed solution integrates with the following devices:

- Peripheral devices: PCI / lane controllers

- ticket dispensers (where retained)

- receipt printers,

- Europay, Mastercard, Visa (EMV) terminals,

- Intercoms,

- Plate cameras,

- Context cameras,

- Automated vehicle identification (AVI)

- Radio frequency identification (RFID) readers, and presence sensors

2.2.4 Software

The Selected Proposer shall provide, configure, integrate, license, host, implement, support, and maintain all software necessary for the complete operation of the turnkey PARCS solution, including, as applicable, operating systems, databases, payment applications and kernels, interfaces, supervisory tools, reporting capabilities, and management consoles.

The County will consider fully cloud-based, on-premises, or hybrid solutions, provided the proposed architecture satisfies all functional, performance, cybersecurity, availability, integration, data ownership, business continuity, and disaster recovery requirements of this Solicitation. Proposers shall clearly identify the proposed deployment model and all software components, third-party products, hosting services, licenses, subscriptions, and dependencies required for the solution.

For each software component, the Proposer shall identify:

1. Whether it is provided under a perpetual license, subscription, Software-as-a-Service (SaaS), or other licensing arrangement;

2. The proposed licensee or subscriber of record;

3. All applicable license terms, subscription fees, usage limitations, renewal requirements, and third-party dependencies; and

4. The County’s rights and the procedures applicable upon expiration or termination of the resulting agreement, including continued use, assignment or transfer where commercially available, data export, system transition, and migration assistance.

Rev.12.16..2025 10

Any perpetual licenses purchased by the County shall be issued in MDAD’s name or transferred to MDAD no later than Final System Acceptance. For subscription, SaaS, or cloud-hosted components that cannot be assigned or transferred due to the publisher’s standard licensing terms, the selected Proposer shall ensure that MDAD can maintain service continuity, obtain its data in a complete and commonly usable format, and transition the applicable services to MDAD, its designee, or a successor provider without unreasonable restrictions or additional transfer fee

2.2.5 Program and Service Managers

The Selected Proposer shall designate a Program Manager for the implementation period and a Service Manager for the operations period, each of whom shall serve as the primary point of contact and report directly to the Airport Representative (AR).

Any replacement of the Program Manager or Service Manager shall require the MDAD prior written approval.

Replacement personnel shall possess qualifications and experience equal to or greater than those of the personnel originally proposed.

2.2.6 Installation, Ongoing Operation and Lifecycle Support

The Selected Proposer shall be responsible for the following installation, operation, and lifecycle items:

a. Coordinating with the AR to ensure that the local area network, wide area network, internet connectivity, and any required dedicated circuits are properly provisioned and configured to support the PARCS

b. Labeling, tagging (including RFID asset tags where required), and inventorying all PARCS components in MDAD's asset/configuration management database

c. Warranty, maintenance, and twenty-four (24) hours a day, seven (7) days a week, production support, including on-site response per Exhibit A, Section 2.15.5 Service Levels.

d. Refresh of field hardware and software across the term in accordance with the Lifecycle Management Plan

e. Maintenance of cybersecurity posture aligned to National Institute of Standards and Technology Cybersecurity

Framework (NIST CSF) 2.0, Payment Card Industry Data Security Standard (PCI DSS) v4.0.1, and applicable Miami-Dade County and federal information-security requirements

f. Assurance of continuous revenue, including reconciliation, exception management, and audit support

g. Verification of system operability and proper installation through completion of all required test plans, witnessed by the AR or the AR's designee.

h. Performance of all installation and maintenance work to minimize disruption to the Airport, its tenants, ground transportation operations, and the traveling public. The Contractor shall coordinate with the AR to schedule work in public areas during off-peak windows. Work performed during off-peak hours, including software updates and operating-system patching, shall not incur additional cost to the Department. Maintenance windows shall be coordinated with the AR in advance.

i. Utilization of existing data drops, conduit pathways, and electrical power outlets where feasible. If existing power, structured cabling, or millwork is inadequate to support the new PARCS equipment, the Contractor shall notify the AR, propose a remediation plan, and, upon written approval, perform the required modifications. All such modifications shall comply with Miami-Dade County construction, electrical, and life-safety codes and shall be coordinated with airport operations.

2.3 Payment Schedule

The Proposer shall provide its proposed price to provide Services within Attachment C, Price Proposal Schedule. Payment schedule to be negotiated with the selected proposer based on completed milestones.

2.4 System Functionality

For further details please see Exhibit A. Technical Requirements

2.5 Maintenance and Technical Support

The selected Proposer shall provide the County with standard software maintenance services and technical support covering, as listed below:

A. All software shall be of the most recent release and all software upgrades issued by the selected Proposer shall be available to the County at no additional charge. The software maintenance plan shall include the installation of new releases by the selected Proposer, at no additional cost to the County.

Rev.12.16..2025 11

B. Proposer shall provide internal user support through phone, chat or ticket system for System functionalities such as communications, updating rates, and updating the website.

C. Corrections of substantial defects in the software Solutions so that the Solution will operate according to specifications and shall be resolved as Severity Level 1. See Technical Support Services Chart.

D. Periodic updates of the Solution may incorporate

• Corrections of any substantial defects

• Fixes of any minor bugs

• Fixes due to any conflicts with mandatory operating security patches, to be resolved as Severity

Level 1 E. Updates to the Solution shall be provided as determined by legally mandated requests F. Updates to the Solution shall be provided in order to maintain PCI compliance requirements G. MDAD preferred escalation and response times are listed below:

Severity Definition Response Time

Resolution Time Status

Frequency Update

1=Critical

A major component of the System, whether hardware or software, is in a non-responsive state and severely affects Users’ productivity or operations. A high impact problem which affects the Users.

15 minutes 1 Hour 15 minutes

2=Urgent

Any component failure or loss of functionality not covered in Severity 1, which is hindering operations, such as, but not limited to: excessively slow response time;

functionality degradation; error messages; backup problems; or issues affecting the use of a module or the data.

1 Hour 4 Hours 30 minutes

3=Important Lesser issues, questions, or items that minimally impact the workflow or require a work around.

4 hours 24 Hours 4 Hours

4=Minor Issues, questions, or items that don’t impact the workflow.

Issues that can easily be scheduled such as an upgrade or patch.

8 hours

72 hours for an acceptable work around until final resolution

Weekly Status Call

Refer to Exhibit A, 2.15.5 for additional service level response and resolution targets.

2.6 Implementation Services

The proposed Solution shall be fully implemented, including completion of customization, configuration, integration, testing, user training, go-live, stabilization, and Final System Acceptance within twenty-four (24) months from the County’s issuance of Notice to Proceed (NTP). (For further details on implementation requirements please see Exhibit A.)

2.7 PCI Compliance Requirements

The proposed Software solution shall comply with Payment Card Industry (PCI) Security Standards. The County’s current process for establishing and maintaining such compliance is outlined in Draft Form of Agreement, Article 48, Payment Card Industry Data Security Compliance, attached herein.

2.8 Cloud Based Service

If the proposed solution is a cloud-based Software-as-a-Service (SaaS) solution, it shall be accessible through industry-standard web browsers and include all software updates, upgrades, patches, and enhancements made generally available to other customers at no additional cost to the County. The solution shall also provide robust application programming interfaces (APIs) to support secure data integration and transfer to the County’s Microsoft Azure Data Lake.

2.9 System Availability

The selected Proposer shall provide the services at or above the minimum service levels set forth in Exhibit A, Section 2.15.5.

Availability shall be measured monthly for each applicable service or active lane group, as identified in the service-level table.

Rev.12.16..2025 12

Scheduled maintenance that has been approved in advance by the County and any other County-approved exclusions expressly identified in the resultant agreement shall be excluded from the availability calculation.

If the selected Proposer fails to meet an applicable monthly availability target, the County shall be entitled to the applicable service credit/refund equal to the monthly hosting amount following the month in which less than target % uptime occurred or other remedy stated in the resultant contract agreement.

2.10 Business Continuity and Disaster Recovery

The County seeks a high availability/fault tolerant solution. The County requires the Solution to have industry-accepted fully automated backup capabilities for the purpose of disaster recovery. This should include all database and application data. The Proposer will show documented proof of reliable infrastructure, disaster recovery, and redundancy.

2.11 Data Integrity

The Solution should ensure the integrity of the data. Interruptions in processing due to incidents such as aborted transactions, hardware failures, or network unavailability should not result in inaccurate or inconsistent data residing in the Solution. If data transfers occur, the Solution should provide a method of audit validation to ensure all data sent was received in the target application.

2.12 Scalability

The Solution should be able to scale up to handle increased load without any performance impact on operations to facilitate demand.

2.13 Pass-through Charges to Customers

Proposer shall clearly specify any pass-through charges to the parking customer. Any proposed pass-through charges are subject to MDAD’s approval.

2.14 Removal of Current PARCS

As part of the implementation and transition to the new Parking Access and Revenue Control System (PARCS), the selected Proposer shall plan, coordinate, perform, and document the decommissioning, removal, handling, transportation, disposition, and, when directed by the County, relocation or reallocation of the County's existing PARCS equipment and related components identified by the County.

All removal activities shall be coordinated with the implementation, testing, cutover, and commissioning of the new PARCS and shall be performed in a manner that minimizes disruption to airport parking operations, revenue collection, customer service, customer access, ingress and egress, and traffic flow.

The selected Proposer shall :

1. Removal and Transition Plan. Prior to commencing removal activities, submit a removal and transition plan (Plan) for County review and approval. The Plan shall identify the proposed sequence of work, schedule, staffing, equipment staging areas, access requirements, safety measures, proposed disposition of removed equipment, and measures to maintain continuity of parking and revenue collection operations throughout implementation and cutover.

2. Inventory of Existing Equipment. In coordination with the County, prepare an inventory of existing PARCS equipment designated for removal. The inventory shall identify, to the extent available, the equipment type, quantity, location, County asset identification number and/or serial number, and County-directed disposition.

3. Coordination with System Cutover. Existing PARCS equipment shall not be removed, disconnected, disabled, or otherwise taken out of service until authorized by the County.