George Washington Bridge ITS replacement | scope and forecast guide
Review the George Washington Bridge intelligent transportation system forecast, including equipment, software interfaces and procurement questions for GCs.
Author
Ido Gedanken, CEOPublished

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.
Book a demo- Type
- Guide
- Read
- 2 min
- Published
On this page
The forecast describes replacement of intelligent transportation system equipment, including signs, traffic detectors, infrastructure and software, at the George Washington Bridge. Its stated objectives include faster detection and response to congestion-causing incidents, customer notification and traffic management. GWB244327 in the Port Authority construction forecast.
Forecast reference and status
The Port Authority forecast workbook lists GWB Replacement of existing ITS, reference GWB244327, for 2027 Q4. This is forecast procurement timing, not a bid due date or construction schedule. George Washington Bridge is a cross-Hudson facility; the forecast does not establish the precise work limits on either side. The agency construction procurement page explains the forecast context; a forecast entry does not establish an active solicitation. Check current agency advertisements and issued documents before a bid decision.
This is independent Piper analysis of the forecast, checked November 15, 2026, not an agency notice. The forecast does not establish an award, construction start or final package boundaries.
Scope boundaries for field equipment and software
For a systems estimator, the boundary between field devices, communications infrastructure and software is as important as the equipment count. The forecast does not identify the device inventory, limits or integration architecture.
Record each unresolved boundary with its source and trade owner; confirm quantities in the issued documents before pricing.
Questions for the issued documents
The following are estimating questions, not confirmed project requirements:
- Which signs and detectors are being replaced, and what existing infrastructure can be reused?
- Where do field installation, software configuration and integration with existing systems begin and end?
- What commissioning, cutover and system acceptance responsibilities are included in the issued documents?
Request the solicitation, drawings, specifications, bid form and all addenda when issued. Compare the actual work limits and obligations to trade quotations, then document exclusions and unresolved interfaces before carrying a price. The public construction bid review helps structure that review; use the addenda review method if issued documents change. The public project directory provides a route to other named projects.
Reviewing the issued bridge documents
Once the team has the actual documents, Piper's scope-generation workflow can be used with documents supplied by the user to help organize scope review. Estimators still need to resolve project-specific boundaries and price the work against the controlling documents.
Related reading
NYC public construction bid review: connect the requirement to the number
A NYC public-bid review should trace owner requirements into scope, quotes, schedule and the final number. A practical review map for small GC precon teams.

Construction addenda management for GC estimators
Addenda are official bid-document revisions. Log them, distribute them, retakeoff the deltas, and require subcontractor acknowledgments so your estimate and every bid reflect the final scope.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
See Piper on your project
Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.