GDACS IO POWER SUPPLIES

GDACS IO POWER SUPPLIES --- ATTACHMENT: attachment_1.pdf --- SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30 1. REQUISITION NUMBER 0044009030 PAGE OF 1 29 2. CONTRACT NO. 3. AWARD/ 4. ORDER NUMBER EFFECTIVE DATE 5. SOLICITATION... (Federal Government | Due 2025-06-10)

AviationPLCRadioRTUSCADATelemetryWater/Wastewater
Type
RFP
Jurisdiction
Federal Government
Posted
Jun 4, 2025
Due
Jun 10, 2025
Updated
Jun 10, 2025

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: The power supplies are for use on OPTO22 EB-2 A/D processors, which are components often used with PLCs or RTUs. The document does not explicitly mention PLCs or RTUs by brand or model, but refers to 'GDACS RTU 5.1VDC Power Supplies'.
  • HMI details: HMI/SCADA is implied as the GDACS system is a SCADA system, but no specific HMI/SCADA software is mentioned.
  • Comms details: Network infrastructure mentioned but specific media/protocols not detailed. The document refers to the GDACS SCADA system, implying a network, but doesn't specify communication details.
  • 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.