Miami-Dade County, FL RFP No. RFP0000014

Rev. 8.1.2025

ATTACHMENT A - PROPOSER INFORMATION

Nothing in this Solicitation shall in any way be utilized to request documentation relating to or authorizing consideration of a proposer's social, political, or ideological interests when determining if the proposer is a responsible vendor or give a preference to a proposer based on the proposer's social, political, or ideological interests.

1. Proposer’s Experience and Past Performance

1. Describe the Proposer’s past performance and experience and state the number of years that the Proposer has been in existence, the current number of employees, and the primary markets served. Include specific information regarding prior experience in designing, supplying, installing, commissioning, operating, and providing ongoing maintenance and lifecycle support for PARCS solutions of comparable scope at airports for a preferred five (5) years. Proposer should provide evidence of at least one airport PARCS engagement currently in production in which the Proposer delivered the system under a integrated delivery and serves as the operator of the owner-held system, providing day-to-day parking operations, maintenance, and lifecycle support.

2. Provide a detailed description of up to three (3) comparable contracts (similar in scope of services to those requested herein) which the Proposer has either ongoing or completed within the past five (5) years. In lieu of the comparable contracts from the Proposer, the County will consider the contractual experience from Proposer’s proposed Subcontractor or proposed key personnel, in accordance with Resolution No. 1122-21.

For each comparable contract please provide:

a) Customer and facility name;

b) Contract value and period of performance;

c) Number of parking spaces, facilities, and entry and exit lanes;

d) Annual transaction and revenue volume;

e) System architecture and major components;

f) Ticketless, license plate recognition (LPR), reservation, payment, and mobile capabilities;

g) Systems and third parties integrated;

h) Implementation, operations, and maintenance responsibilities;

i) Planned and actual implementation dates and costs;

j) System availability and applicable service level agreement (SLA) performance; and

k) Customer reference (contract person, phone number and email)

3. Comparable Outcomes and Performance. For the projects identified above, describe performance results demonstrating the Proposer’s ability to:

a) Protect and reconcile parking revenue;

b) Maintain parking operations during implementation and cutover;

c) Meet lane-throughput and system-availability targets;

d) Achieve LPR and payment-processing accuracy;

e) Reduce equipment failures and repair times;

f) Improve customer experience; and

g) Deliver projects within the approved schedule and budget.

h) Identify the baseline, measurement period, achieved result, and source of the supporting data.

4. Relevant Implementation and Operational Challenges. Describe two significant challenges encountered on comparable projects, including at least:

a) One implementation, integration, migration, or cutover challenge; and

b) One post-implementation operational, maintenance, cybersecurity, or revenue-reconciliation challenge.

For each, explain the cause, impact, corrective action, final outcome, and lessons that will be applied to the MIA project.

5. Past-Performance Disclosures. Identify any comparable contract during the past five years involving:

a) Material schedule delay or cost overrun;

b) Failure to meet service levels;

c) Unplanned interruption of parking or payment operations;

d) Revenue loss or material reconciliation discrepancy;

e) Cybersecurity or payment-card incident;

f) Assessment of liquidated damages or service credits;

g) Cure notice, default, termination, or material claim; or

h) Dispute concerning system acceptance.

i) Explain the circumstances, responsibility, corrective action, and final disposition.

6. List all contracts which the Proposer has performed for Miami-Dade County. The County will review all contracts the Proposer has performed for the County in accordance with Section 2-8.1(g) of the Miami-Dade County Code, which requires that “a Bidder’s or Proposer’s past performance on County Contracts be considered in the selection of Consultants and Contractors for future County Contracts.” As such, the Proposer must list and describe all work performed for Miami-Dade County and include for each project: (i) name of the County Department which administers or administered the contract, (ii) description of work, (iii) total dollar value of the contract, (iv) dates covering the term of the contract, (v) County contact person and phone number, (vi) statement of whether Proposer was the prime contractor or subcontractor, and (vii) the results of the project.

7. In order to understand the financial capabilities and stability of the Proposer, and that of any joint venture or affiliated entities, the County requests that the following historical financial information be submitted from either the proposing corporate entity or the majority equity owners:

a. Audited or reviewed comparative financial statements for the last three (3) fiscal years prepared in accordance with generally accepted accounting principles (GAAP) or International Financial Reporting Standards (IFRS), reflecting current financial conditions; if there are no audited or reviewed financial statements available, then provide federal income tax returns filed with the Internal Revenue Service (IRS) for the previous three (3) fiscal periods.

b. An interim balance sheet and income statement for any period of time in excess of six months of the financial statements submitted as part of (a) above.

c. Proposer shall state all significant financial events occurring subsequent to the closing date of the submitted audited financial statements and is no such events have occurred, state that fact.

8. List and describe all bankruptcy petitions (voluntary or involuntary) which has been filed by or against the

Proposer, its parent or subsidiaries, predecessor organization(s), or any wholly-owned subsidiary during the past three (3) years. Include in the description the disposition of each such petition.

9. Describe past performance on comparable PARCS engagements, including those with a integrated implementation and commercial model.

10. Describe experience with PARCS, LPR, Europay Mastercard Visa (EMV), SunPass toll-tag integration, and airport reservation system integration.

2. Key Personnel and Subcontractors Performing Services

11. Identify all key personnel including Program Manager and Service Manager. Provide an organization chart showing all key personnel, including their titles, to be assigned to this project. This chart must clearly identify the Proposer’s employees and those of the subcontractors or subconsultants and shall include the functions to be performed by the key personnel. All key personnel includes all partners, managers, seniors and other professional staff that will perform work and/or services in this project.

12. The Program Manager should hold a current Project Management Professional (PMP) certification issued by the Project Management Institute (PMI) and should have successfully led at least two (2) PARCS implementations or comparably complex airport technology system projects of similar size and scope within the five (5) years preceding the solicitation’s closing date. The Proposer shall identify the proposed Program Manager and provide documentation demonstrating compliance with these requirements as part of its proposal.

13. Identify Subcontractors, if any. List the names and addresses of all first tier subcontractors, and describe the extent of work to be performed by each first tier subcontractor. Describe the experience, qualifications and other vital information, including relevant experience on previous similar projects, of the Subcontractors who will be assigned to this project.

14. Describe the experience, qualifications and other vital information, including relevant experience on previous similar projects, of all key personnel, including those of Subcontractors, who will be assigned to this project.

Please include: (i) names; (ii) titles; (iii) roles/functions to be performed; and (iv) copies of applicable certifications/accreditations. Address relevant experience, qualifications and other vital information on previous similar contracts, that qualifies the key personnel to perform the services as specified in Solicitation Section 2.0 – Scope of Services and Exhibit A – Technical Requirements. Provide resumes, if available, with job descriptions including any key personnel of subcontractors who will be assigned to this contract. Resumes should be limited to 2 pages.

15. Technical and Operational Team Capability. Describe the qualifications and availability of the personnel responsible for:

a) PARCS architecture and configuration;

b) Lane and field-equipment engineering;

c) Systems and application programming interface (API) integrations;

d) Payment processing and Payment Card Industry Data Security Standard (PCI DSS) compliance;

e) Cybersecurity and network engineering;

f) Data migration and reconciliation;

g) Testing and quality assurance;

h) Training and organizational readiness;

i) Revenue assurance;

j) Customer assistance;

k) Preventive and corrective maintenance; and

l) Disaster recovery and business continuity.

m) Identify which functions will be performed by employees, subcontractors, manufacturers, or other third parties.

16. Staffing Continuity and Local Response. Describe how the Proposer will:

a) Retain key personnel through implementation and stabilization;

b) Obtain MDAD approval before replacing key personnel;

c) Provide replacements with equal or greater qualifications;

d) Maintain sufficient local field-service and spare-parts resources;

e) Provide 24/7 operational and emergency coverage; and

f) Address simultaneous incidents, vacancies, absences, and workload surges.

Note: After proposal submission, but prior to the award of any contract issued as a result of this Solicitation, the Proposer has a continuing obligation to advise the County of any changes, intended or otherwise, to the key personnel identified in its proposal.

3. Proposed PARCS Solution, Architecture, and Integrations

17. Describe the proposed PARCS and explain how system solution hardware, software, cloud, edge, network, mobile, customer-facing, and back-office components work together to meet MDAD’s operational and business objectives.

Provide a traceability cross-reference connecting the proposal narrative, architecture documents, and supporting evidence to the applicable Compliance Matrix requirement IDs. Clearly identify:

a) Standard, currently available functionality;

b) Configurable functionality;

c) Third-party functionality;

d) Functionality requiring customization or future development;

e) Assumptions and dependencies; and

f) Exceptions or limitations.

18. Architecture, Resilience, and Scalability. Provide a logical and physical architecture describing:

a) Cloud, on-premises, hybrid, and edge components;

b) Production, test, training, and disaster-recovery environments;

c) Lane controllers and field equipment;

d) Network topology and security boundaries;

e) Payment-card environment;

f) Data flows and storage locations;

g) Monitoring and administrative tools; and

h) All single points of failure.

Explain how the architecture:

h) Maintains lane operations during loss of connectivity;

i) Prevents loss or duplication of transactions;

j) Reconciles locally stored transactions after restoration;

k) Meets the required recovery time objective (RTO) and recovery point objective (RPO);

l) Accommodates peak transaction volume; and

m) Scales to at least 150% of the current footprint without material redesign.

19. Customer and Operational Workflows. Describe the end-to-end workflows for:

a) App-driven ticketless parking (optional feature);

b) Credit-card-in/credit-card-out;

c) SunPass;

d) Reservations;

e) Contract, employee, and VIP parking;

f) Validations;

g) LPR mismatch or unreadable plate;

h) Lost credential or unavailable payment method;

i) Manual gate opening;

j) Refunds and disputes;

k) Equipment or interface failure; and

l) Paper-ticket fallback.

For each workflow, identify the gate-decision authority, payment authorization point, exception controls, audit records, customer communications, and recovery process.

20. For every required integration, provide an interface schedule identifying:

a) Source and destination system;

b) Business purpose;

c) Data exchanged;

d) Proposed interface method;

e) Real-time, near-real-time, or batch frequency;

f) Authentication and encryption;

g) Error handling, retry, and reconciliation;

h) Monitoring and alerting;

i) Responsible parties;

j) Required third-party cooperation;

k) Testing method; and

l) Comparable production experience.

The schedule should address SunPass, Park Assist, Propel, GateKeeper, FDLE, the payment processor, Microsoft Entra ID, Azure Data Lake, Power BI, Salesforce, SIEM, ITSM, and successor systems.

21. Revenue Assurance and Financial Controls. Describe how the solution will ensure that every parking session and financial transaction is:

a) Uniquely identified;

b) Recorded completely and accurately;

c) Associated with the correct rate and payment;

d) Protected from unauthorized modification;

e) Reconciled across lanes, payment systems, reservations, SunPass, and the general ledger;

f) Flagged when an exception occurs; and

g) Retained with a complete audit trail.

Provide sample revenue, exception, manual-opening, refund, dispute, chargeback, open-session, and reconciliation reports.

22. Cybersecurity, Privacy, and Payment Security. Describe how the solution addresses security across its full lifecycle, including secure development, vulnerability disclosure, software supply-chain risk, access control, encryption, logging, monitoring, incident response, backup integrity, recovery, remote vendor access, LPR privacy, data retention, and secure disposal.

Provide:

a) Current PCI DSS responsibility matrix and applicable Attestation of Compliance;

b) Secure software-development lifecycle description;

c) Vulnerability and patch-management process;

d) Independent penetration-test summary;

e) Cyber-incident notification process;

f) Subprocessor and hosted-data locations; and

g) Security responsibilities retained by MDAD.

23. Data Ownership, Portability, and Vendor Independence. Identify every software component as perpetual, subscription, or SaaS and provide:

a) Licensee of record;

b) License term and restrictions;

c) Included upgrades and enhancements;

d) Data-access and export methods;

e) API restrictions or transaction charges;

f) Proprietary dependencies;

g) Assignment or reissuance procedure;

h) Administrative access available to MDAD; and

i) Exit costs or technical barriers.

Explain how MDAD or a successor operator can continue operating the system and obtain all data, configurations, credentials, documentation, and licenses without dependence on the incumbent Contractor.

24. Provide a proposed milestone schedule for the design, configuration, implementation, testing, commissioning, and final acceptance of the PARCS. The proposed schedule shall identity, at a minimum:

a. Project kickoff and planning;

b. Site assessment and design;

c. County review and approval of design documents;

d. Equipment and software procurement;

e. Factory Acceptance Testing;

f. Site preparation and installation;

g. System configuration and integration;

h. Data migration;

i. Lane Acceptance Testing;

j. System Acceptance Testing;

k. Training and knowledge transfer;

l. Go-live and transition to production;

m. System stabilization period;

n. Correction of deficiencies and punch-list items; and

o. Final System Acceptance.

For each milestone, identify the anticipated start date, completion date, duration, responsible party, dependencies, required County participation, proposed milestone progress payment schedule, and associated deliverables. Clearly identify all critical-path activities, assumptions, proposed implementation phases, system downtime, and activities that may affect MIA parking operations.

The schedule should be presented in a clear format, such as a Gantt chart, and should state the total number of calendar days from Notice to Proceed through Final System Acceptance. The proposed schedule will be subject to County negotiations with the selected Proposer and will serve as the basis for developing the final project schedule following contract award.

25. Describe the Proposer’s warranty program demonstrating the Proposer shall provide remediation for any non-conforming Work identified during testing and during the first twelve (12) months of operation, at no cost to the Department.

26. The Proposer shall also describe how current technologies, including LPR, mobile credentials, reservation systems, geofencing, digital signage, parking-space monitoring, or other proposed technologies could reduce the need for physical gates, booths, islands, or extensive reconstruction.

(a) An optional feature that, if adopted by MDAD, would operate in conjunction with conventional parking access and payment methods;

(b) Ticketless entry and exit; An optional feature currently under review by MDAD that, if adopted, would complement conventional ticket-based entry and exit methods;

(c) Reservation-based entry and exit;

(d) Credit-card-in/credit-card-out (CCI/CCO) transactions;

(e) SunPass transactions;

(f) License Plate Recognition (LPR) mismatch resolution;

(g) Offline lane operation and subsequent resynchronization;

(h) Manual gate opening and the associated audit trail;

(i) Rate and validation configuration;

(j) Refund and dispute processing;

(k) Revenue reconciliation;

(l) Exception identification and investigation;

(m) Real-time lane monitoring;

(n) Equipment or interface failure alerts;

(o) Role-based user administration;

(p) Standard report generation and export;

(q) Data publication through APIs or to Microsoft Azure Data Lake;

(r) Customer receipt retrieval;

(s) Accessible and multilingual customer interfaces; and

(t) System health and Service Level Agreement (SLA) dashboards.

(u) Valet

Note: The demonstration should depict the currently available production version of the proposed solution. Any mock-up, prototype, third-party component, customization, or functionality requiring future development shall be clearly identified in the video and Proposal. The video is intended to supplement the written Proposal and Compliance Matrix and shall not modify the Proposal or introduce functionality, exceptions, assumptions, or commitments not otherwise included in the Proposal. The County reserves the right to request a live demonstration of the same or additional functionality during Oral Presentations. The video should not exceed 30 minutes.

4. Implementation, Testing, Training, and Transition Approach

27. Provide an Integrated Implementation Plan and preliminary critical-path schedule covering:

a) Mobilization and discovery;

b) Site surveys and design workshops;

c) 30%, 60%, 90%, and for-construction designs;

d) Permitting and approvals;

e) Equipment procurement and staging;

f) Interface design and development;

g) Test-bed implementation;

h) Pilot installation;

i) Lane-by-lane deployment;

j) Data migration;

k) Training;

l) Cutover rehearsals;

m) Production cutover;

n) Operational stabilization; and

o) Final System Acceptance.

p) Identify dependencies, County responsibilities, third-party responsibilities, long-lead items, decision deadlines, schedule contingencies, and acceptance milestones.

28. Provide the proposed phasing, cutover, and rollback approach for replacing the existing PARCS without materially disrupting:

a) Public and employee parking access;

b) Revenue collection;

c) Reservations and validations;

d) SunPass processing;

e) Customer assistance;

f) Parking availability information; and

g) Financial reconciliation.

h) Identify the maximum anticipated lane outages by facility, required off-peak work, temporary operating procedures, contingency equipment, go/no-go criteria, and authority for initiating rollback.

29. Describe the process for discovering, cleansing, mapping, migrating, validating, and reconciling:

a) Customer accounts;

b) Vehicle and plate records;

c) Permits and credentials;

d) Reservations;

e) Rates and validations;

f) Historical transactions;

g) Open parking sessions;

h) Financial balances; and

i) Audit records.

j) Provide proposed acceptance tolerances, exception-resolution procedures, parallel-run methodology, reconciliation reports, and responsibility for correcting migration errors.

30. Management and Quality Assurance. Explain how the Proposer will:

a) Establish bidirectional traceability from each requirement to design, configuration, test evidence, and acceptance;

b) Control requirements and configuration changes;

c) Review designs and submittals;

d) Prevent nonconforming work;

e) Manage defects by severity;

f) Verify corrective actions;

g) Maintain configuration baselines; and

h) Obtain MDAD approval at defined quality gates.

31. Provide the proposed testing strategy for FAT, SAT, UAT, performance, endurance, failover, cybersecurity, accessibility, payment, integration, migration, and operational readiness testing. Identify:

a) Test environment and test-data requirements;

b) Entry and exit criteria;

c) MDAD witnessing;

d) Requirements traceability;

e) Defect severity and retesting rules;

f) Performance loads and acceptance thresholds;

g) Evidence packages;

h) Go-live readiness criteria; and

i) Final System Acceptance criteria.

32. Provide a role-based training and readiness plan for MDAD oversight, operations, finance, IT, cybersecurity, maintenance, supervisors, customer-assistance staff, and trainers. Address:

a) Learning objectives by role;

b) Training environment;

c) Hands-on exercises;

d) MIA workflows;

e) Training schedule;

f) Attendance and completion records;

g) Proficiency assessment;

h) Train-the-trainer activities;

i) Editable materials and recordings;

j) Refresher training; and

k) Training following major upgrades.

l) Training should be evaluated based on demonstrated readiness and knowledge transfer—not merely the number of training hours.

33. Describe the Proposer's methodology and technology tools for data extraction, mapping, transformation, and loading of historical data from the existing system into the proposed PARCS solution. Identify the approach for coordinating with the incumbent software provider to obtain historical data in a mutually agreed-upon file format, including the proposed procedures for mapping the extracted and transformed data to the proposed solution's database structure and completing the data load.

34. Implementation Risk-Matrix. Submit a project-specific risk register identifying the most significant technical, operational, schedule, supply-chain, integration, migration, cybersecurity, stakeholder, and revenue risks.

a) For each risk, provide probability, impact, owner, preventive action, contingency, early-warning indicator, and escalation threshold.

35. The Proposer shall provide a conceptual configuration for accommodating valet operations, considering the limitations of the existing Flamingo Garage layout. The proposed configuration shall identify recommended entrances and exits, traffic-flow patterns, and measures to prevent traffic conflicts, vehicle crossovers, and backups while maintaining access during peak airport traffic periods and preventing unauthorized entry or exit.

5. Operations, Maintenance, Service Levels, and Lifecycle Support

36. Describe the proposed Steady-State Operating Model following Final System Acceptance, including:

a) Service-management organization;

b) Network or system operations center;

c) Customer-assistance function;

d) Remote support;

e) Local field maintenance;

f) Revenue-assurance function;

g) Cybersecurity monitoring;

h) Manufacturers and subcontractors;

i) Hours and location of coverage; and

j) Escalation to executive management.

k) Provide a responsibility matrix distinguishing Contractor, subcontractor, manufacturer, third-party, and MDAD responsibilities.

37. Describe how the Proposer will monitor and meet each required SLA.

For each SLA, identify:

a) Data source;

b) Measurement formula;

c) Monitoring tool;

d) Reporting frequency;

e) Exclusions;

f) Escalation threshold;

g) Corrective-action process; and

h) Service-credit calculation.

Provide sample dashboards showing lane, application, portal, interface, device, network, transaction, and customer-assistance performance.

38. Provide the Preventive and Corrective Maintenance Program for every major asset class. Address:

a) Preventive-maintenance frequency;

b) Remote diagnostic capability;

c) Dispatch and triage;

d) Technician skill requirements;

e) On-site response;

f) Repair and replacement;

g) Post-repair testing;

h) Repeat-failure analysis;

i) Maintenance records;

j) Mean Time Between Failure;

k) Mean Time to Repair; and

l) Chronic equipment replacement.

39. Provide the proposed spare-parts inventory by component and location and explain how the quantities were calculated. Describe:

a) Reorder points and replenishment times;

b) Critical and long-lead components;

c) Manufacturer support commitments;

d) End-of-sale and end-of-support notification;

e) Alternate sourcing;

f) Firmware and model compatibility;

g) Emergency stock; and

h) Procedures for addressing supply-chain disruption.

40. Provide a preliminary Lifecycle Management Plan showing the expected:

a) Useful life of each major component;

b) Software and firmware support period;

c) Patch and upgrade cadence;

d) Hardware refresh schedule;

e) Technology-health assessment;

f) Capacity review;

g) Compatibility testing;

h) Treatment of components reaching end of support.

i) Explain how refresh activities will be completed without avoidable downtime or loss of transaction and configuration data.

41. Describe the ongoing controls used to detect, investigate, correct, and report:

a) Missing or duplicate transactions;

b) Rate discrepancies;

c) Manual gate openings;

d) Unreadable or mismatched plates;

e) Failed payments;

f) Open sessions;

g) Refunds and fee waivers;

h) Reservation or SunPass discrepancies;

i) Chargebacks; and

j) Cash variances, if applicable.

k) Explain how operating data, incident trends, customer complaints, equipment failures, and financial exceptions will be analyzed during monthly and quarterly reviews to drive measurable improvement.

42. Describe how the Proposer will maintain or restore parking and revenue operations following:

a) Loss of cloud connectivity;

b) Network failure;

c) Data-center or hosted-service outage;

d) Database corruption;

e) Cyberattack or ransomware;

f) Payment-processor outage;

g) Third-party interface failure;

h) Power loss; or

i) Major field-equipment failure.

j) Provide the proposed recovery sequence, communications plan, manual procedures, backup validation, annual exercise, Recovery Time Objective (RTO / Recovery Point Objective (RPO) verification, and after-action process.

43. Provide a detailed approach for transition to MDAD or a successor operator at expiration or termination. Address:

a) Transition staffing and duration;

b) Parallel operations;

c) Knowledge transfer;

d) Administrative credentials;

e) Software and SaaS license assignment;

f) Configuration and source files;

g) APIs and interface documentation;

h) Asset and spare-parts inventories;

i) Open incidents and maintenance history;

j) Data extraction in nonproprietary formats;

k) Continued service during transition;

l) Transition fees; and

m) Certification of data return and destruction.

Proposer’s Exception

44. Identify if Proposer has taken any exception to the terms of this Solicitation. If so, indicate what alternative is being offered and the cost implications of the exception(s).