PORTS Program Overview, Governance, and Stakeholder Roles
Domain focus
PORTS (Physical Oceanographic Real-Time System) is NOAA CO-OPS' partnership-based program that delivers real-time and predicted water levels, currents, waves, meteorology, and related observations to mariners and port decision-makers. The exam tests program structure, who does what, and how local needs become funded, operated systems.
Core rules and roles
- NOAA CO-OPS sets national technical standards, operates the central data system, performs QA/QC, and publishes products; it does not unilaterally fund every local sensor.
- A non-federal sponsor (port authority, pilots association, state or local agency) typically provides cost share, site access, and local priority-setting through a PORTS agreement.
- Users-pilots, tug operators, USCG, terminal operators, emergency managers-define requirements; NOAA translates them into siting, sensor, and product specifications.
- PORTS often leverages NWLON (National Water Level Observation Network) stations, but PORTS is a user-driven, port-specific system, not simply a rename of NWLON.
- Data are generally free and open, with metadata and QC flags; governance includes maintenance responsibilities and performance reporting.
Worked example
A port requests a new current meter at a berth. The correct sequence is: document user need (pilot transit), conduct site survey and feasibility, estimate capital and annual O&M, identify sponsor and cost share, execute agreement, install and benchmark, integrate into CO-OPS QC and display, then review performance. Assuming NOAA will pay is a common error.
Traps
Confusing PORTS with NWLON; assuming all PORTS sites are NOAA-owned; treating a local sponsor as a passive funder rather than an operating partner; ignoring the agreement's maintenance and data-quality obligations.