GAOA TETON DAM RECONSTRUCTION

GAOA TETON DAM RECONSTRUCTION --- ATTACHMENT: attachment_2.pdf --- SOLICITATION, OFFER, AND AWARD (Construction, Alteration, or Repair) 1. SOLICITATION NO. 140L0625R0013 2. TYPE OF SOLICITATION SEALED BID (IFB) INVITATION FOR BID 3. DATE ISSUED PAGE OF PAGES x NEGOTIATED (RFP)... (Federal Government | Due 2025-07-10)

AviationEmergency AlertingPLCRadioSCADATelemetryWater/Wastewater
Type
RFP
Jurisdiction
Federal Government
Posted
Jun 10, 2025
Due
Jul 10, 2025
Updated
Jun 10, 2025

GDS Notes

  • Estimated value: The FAR Magnitude is $5M - $10M.
  • Bid bond required: Yes
  • Mandatory site visit: Yes
  • Local integrator required: No
  • PLC details: PLCs/RTUs are likely to be part of the dam reconstruction, but the RFP does not specify any particular brands or models. The specifications and drawings (Attachment 2 and 1) would contain these details.
  • HMI details: HMI/SCADA systems are likely to be part of the dam reconstruction, but the RFP does not specify any particular software. The specifications and drawings (Attachment 2 and 1) would contain these details.
  • Comms details: Network infrastructure is likely to be part of the dam reconstruction, but the RFP does not specify any particular media/protocols. The specifications and drawings (Attachment 2 and 1) would contain these details.
  • Project insights: {"bid_bond_required": "An offer guarantee is required. See Item 13b on page 1 of the solicitation.", "mandatory_site_visit": "There is a site visit scheduled for 24 June 2025 at 1:00 PM Local Time. See clause instructions below / FAR 52.236-27. The RFP does...
  • Request existing site list (pump stations, wells, tanks), I/O counts, and alarm philosophy before proposing cutover.
  • Confirm PLC platform, firmware, programming environment, and whether standard libraries/naming conventions are required.

Integration Checklist

  • Confirm existing site inventory, I/O counts, and any required standards (tagging, alarms, naming).
  • Request current drawings, network diagrams, and as-built documentation (or plan for discovery).
  • Define acceptance testing: FAT/SAT steps, cutover plan, and rollback expectations.
  • Confirm PLC platform, programming environment, licensing, and source code handoff requirements.
  • Clarify communications path, latency constraints, polling rates, and any coverage/path study requirements.
  • Align with O&M workflows: alarms, reporting, compliance needs, and on-call response expectations.