Exhibit_D_-_Implementation_Delivery_Schedule.pdf

Exhibit D – Implementation Delivery Schedule

Schedule basis. All periods are measured from Notice to Proceed (NTP). The selected Contractor shall develop and maintain a resource-loaded Critical Path Method (CPM) Master Schedule consistent with this baseline and the County-approved implementation schedule.

Schedule Element

Baseline Control Point Requirement

Total implementation

24 months from

NTP

County approval Go-Live targeted in Month 23; final acceptance in Month 24.

Deployment approach

Pilot plus phased rollout Operational continuity

No uncontrolled airport wide “big bang” cutover; parking and revenue operations remain available.

Schedule updates

Monthly; weekly look-ahead CPM critical path

Contractor identifies variance, recovery actions, decisions, and access constraints.

Acceptance Documented gate approval County sign-off

Completion requires accepted deliverables, objective test evidence, and closure of material defects.

Credits Per applicable

Appendix

Contractor-attributable delay

Credits apply to delayed Critical Path Milestones and their associated

Milestone Amounts.

Key Scheduling Principles

a. The Contractor shall preserve airport access, public safety, revenue collection, and parking capacity during every installation wave.

b. Each critical milestone must have measurable entry criteria, exit criteria, responsible parties, County review duration, and approved evidence of completion.

c. Testing shall include normal operations, exception handling, cybersecurity, performance, payment reconciliation, failover, backup/recovery, and rollback.

d. County review periods and decisions shall be visible in the CPM schedule and tracked in the decisions log.

e. A missed or forecast critical milestone requires a written impact analysis and recovery schedule without relieving the Contractor of its obligations.

Miami-Dade County, FL Contract No. RFP0000014

Detailed Milestone Delivery Schedule

Milestone payment percentages are proposed allocations and should be reconciled with the final price schedule. Percentages total 100%.

ID Milestone Timing Required Deliverables / Acceptance Gate Primary Dependencies

Amount Critical

M1 Mobilization and

Baseline CPM

NTP–M1

Approved project management plan, staffing plan, safety/security plan, risk register, document controls, and resource-loaded CPM baseline.

NTP; County access and kickoff 3% Yes

M2 Validated

Requirements M1–M4

Approved requirements traceability matrix, existing-condition survey, lane inventory, operational workflows, reporting requirements, and interface register.

M1; stakeholder workshops; site access

7% Yes

M3 Final Design

Approval M4–M6

100% design package covering lanes, civil, electrical, low-voltage, network, cybersecurity, hosting, redundancy, payment security, signage, and maintenance of traffic.

M2; County design review 10% Yes

M4 Procurement and

Factory Readiness M4–M10

Long-lead equipment released; approved submittals; factory configuration complete;

spare-parts and logistics plans approved.

M3 for final release;

approved products 10% Yes

M5 Software and

Integration Build M6–M12

Configured PARCS platform and completed interfaces for payment, LPR/AVI, financial systems, validations, permits, access control, monitoring, and reporting.

M2–M3; interface access; test data 10% Yes

M6 Factory Acceptance

Test

M10–

M13

Successful FAT, cybersecurity validation, performance testing, defect register, training environment, and approved pilot-release recommendation.

M4–M5; approved

FAT scripts 10% Yes

M7 Pilot Installation

Complete

M13–

M15

Pilot lanes/facility installed with approved traffic controls; devices, networks, power, cameras, kiosks, gates, and signs operational.

M6; permits; lane access windows 8% Yes

Detailed Milestone Delivery Schedule (continued)

ID Milestone Timing Required Deliverables / Acceptance Gate

Primary Dependencies Amount Critical

M8 Pilot Operational

Acceptance

M15–

M16

Pilot passes site acceptance, transaction reconciliation, failover, security, throughput, exception handling, and 30-day operational proving period.

M7; trained pilot users 7% Yes

M9 Phased Airportwide

Deployment

M16–

M20

Remaining facilities and lanes deployed in approved waves while maintaining continuous parking operations and revenue collection.

M8; approved wave/rollback plans 15% Yes

M10 Data Migration and

Training

M17–

M21

Validated migration and reconciliation;

role-based operator, finance, administrator, maintenance, cybersecurity, and help-desk training completed.

M5; clean source data; staff availability 5% Yes

M11 Systemwide SAT and Readiness

M20–

M22

End-to-end SAT, disaster-recovery/failover exercise, PCI evidence, vulnerability remediation, as-builts, SOPs, spares, and operational-readiness approval.

M9–M10; approved

SAT/ORR scripts 5% Yes

M12 Production Go-Live M23

All facilities cut over under an approved command-center, communications, rollback, vendor-support, and revenue-assurance plan.

M11; County Go/No-Go approval 7% Yes

M13 Final Acceptance and Closeout M24

30-day stabilization complete; priority defects closed; final documentation, warranties, licenses, asset inventory, source/configuration records, and support transition accepted.

M12; stabilization metrics achieved 3% Yes

CPM Governance and Acceptance Controls

Control Minimum Requirement

Baseline schedule Submit within 30 calendar days after NTP; include logic, durations, calendars, resources, float, procurement, reviews, permits, testing, deployment waves, training, cutover, and closeout.

Monthly update Provide native CPM file and PDF; status actual starts/finishes, remaining durations, critical/near-critical paths, variance, forecast dates, and corrective actions.

Three-week look-ahead

Update weekly during field installation, testing, migration, and cutover; identify access, staffing, outage, traffic-control, and decision needs.

Schedule recovery When a critical milestone is forecast late, submit impact analysis and recovery plan within five business days, including added resources, resequencing, extended shifts, and risk controls.

County decisions Track all decisions and required-by dates. A Contractor assertion of County-caused critical delay must show contemporaneous notice, schedule logic, impact, and mitigation.

Change control No schedule change alters contractual milestone dates unless approved through the applicable change-order or contract-amendment process.

Milestone acceptance County acceptance requires complete deliverables and objective evidence. Partial delivery, beneficial use, or payment does not constitute final acceptance unless expressly stated.

Go-Live authorization Requires written Go/No-Go approval after operational-readiness review, cybersecurity acceptance, reconciliation validation, support readiness, and approved rollback plan.