Exhibit_B_-_Beach_Ramp_Locations.pdf

Exhibit B is a supplementary document for Volusia County, Florida's Beach Maintenance Request for Proposals #26-P-05MC, listing 38 vehicle access ramps across the county's coastal jurisdiction. The document identifies specific beach ramp locations by asset number and street address, spanning from North County areas including Ormond Beach and Daytona Beach through Daytona Beach Shores, New Smyrna Beach, Wilbur-by-the-Sea, and Ponce Inlet. The Beach Maintenance contract requires the selected contractor to commence full operations on October 1, 2026, and encompasses comprehensive maintenance services for approximately 47 miles of coastal shoreline. A mandatory pre-proposal meeting is scheduled for December 12, 2025, at 9:00 AM, with written questions due by January 7, 2026. Proposals must be submitted electronically through the County's eProcurement Portal by January 21, 2026, at 3:01 PM. The contract will be awarded for an initial five-year term with two potential five-year renewal options, contingent on mutual agreement and County Council approval.

Evaluation will be based on cost (20%), experience and references (25%), equipment (25%), and operational plan (30%), with a local preference of up to 5% discount available for Volusia County-area businesses. The contractor must maintain a $300,000 performance bond and comply with Florida Department of Environmental Protection ramp grading permits and U.S. Fish and Wildlife Service Incidental Take Permit conditions. Required insurance includes Commercial General Liability, Workers' Compensation, and Motor Vehicle Liability coverage. Services encompass beach ramp grading, garbage and recycling collection from 800 trash cans at 350 locations, bulk debris removal, sea turtle nesting season rut raking, beach porter services, and fire pit transportation, with pricing structured per location, per collection point, and hourly rates for specialized services. No specific incumbent vendor or set-aside designations for disadvantaged enterprises are identified in the available documentation.