Skip to content
Global Data Specialists

Archive · listed deadline has passed. This reference listing does not confirm an active solicitation. Check the issuing agency for amendments and current status.

USNS YUMA (T-EPF 8) Chill Water Regulating Valves

Please see attached revised documents for the chill water regulating valves for use onboard the USNS YUMA (T-EPF 8). --- ATTACHMENT: attachment_3.pdf --- Date: 30 APR 2025 MEMORANDUM Subj: USE OF OTHER THAN FULL AND OPEN COMPETITION FOR AN ACQUISITION UNDER THE SIMPLIFIED ACQU... (Federal Government | Due 2025-06-30)

PLCRadioSCADATelemetry
Type
RFP
Jurisdiction
Federal Government
Posted
Jun 2, 2025
Due
Jun 30, 2025
Updated
Jun 10, 2025

The original notice link is unavailable. Search SAM.gov using the notice title above and include inactive notices. This page remains an archive reference.

GDS Notes

  • Estimated value: No budget/value provided; offerors to propose pricing
  • Bid bond required: No
  • Mandatory site visit: Yes
  • Local integrator required: No
  • Construction beyond panels: No
  • PLC details: PLCs/RTUs are not explicitly mentioned in the provided text. The focus is on the chill water regulating valves.
  • HMI details: HMI/SCADA is not explicitly mentioned in the provided text. The focus is on the chill water regulating valves.
  • Comms details: Network infrastructure mentioned but specific media/protocols not detailed
  • Confirm PLC platform, firmware, programming environment, and whether standard libraries/naming conventions are required.
  • Clarify communications path (licensed/unlicensed/cellular), polling rates, and any radio path study or coverage constraints.

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.