UNSPSC 95121639: Pipeline carrying bridge

A bridge that spans an obstacle for the benefit of a pipeline

UNSPSC 95121639 Pipeline carrying bridge, a Commodity code, reflects state and local procurement of bridge structures designed to carry utility lines or pipelines across waterways, roadways, and other obstacles—a specialized infrastructure category distinct from standard vehicular or pedestrian bridges. Recent solicitations under this code show minimal direct activity; the overwhelming majority of bridge work in the state and local pipeline shows conventional bridge replacement, rehabilitation, and new construction for roadway and pedestrian use, with no recent opportunities explicitly specifying pipeline-carrying bridge design or fabrication.

The code sees scattered geographic activity across Florida (Orange County, Pinellas County, Collier County, Volusia County), Georgia (Bulloch County, City of Marietta, Jekyll Island), Texas (Williamson County, Denton County, City of Waco, City of McKinney), Mississippi (Perry County, Hinds County, Jones County, Smith County), Oregon (Washington County, Marion County), and Pennsylvania (Montgomery County), alongside activity in the District of Columbia, North Carolina, and Wisconsin. Issuing bodies span county governments, municipalities, state departments of transportation, special districts, and regional authorities. Representative recent opportunities illustrate the category mismatch: Washington County, Oregon issued an ITB for Bridge #23952 railing retrofit (due July 29, 2026, estimated value $110,000); Orange County, Florida solicited bids for Horizon West Trail Phase 1A multi-use trail with a prestressed concrete pile-supported boardwalk (due August 13, 2026, estimated value $5.657 million); and the City of Waco and TxDOT solicited bids for the Speegleville Bridge Over Middle Bosque Replacement with two 670-foot spans (due July 29, 2026, estimated engineering cost $17.3 million). None of these opportunities reference pipeline or utility line carrying capacity as a primary scope driver. The code appears inactive for its intended purpose; procurement officers should verify whether the taxonomy applies to actual pipeline-bridge work or whether this code represents a data classification mismatch in the local procurement system.