646-23-405 UD Upgrade 2A130/7W139 Medical Air Systems

https://api.sam.gov/prod/opportunities/v1/noticedesc?noticeid=f3351061735c4c20a724e138f4f6c9d2 --- ATTACHMENT: attachment_1.pdf --- 852.219-75 VA NOTICE OF LIMITATIONS ON SUBCONTRACTING— CERTIFICATE OF COMPLIANCE FOR SERVICES AND CONSTRUCTION (JAN 2023) (DEVIATION) (a) Pursuan... (Federal Government | Due 2025-06-23)

AviationEmergency AlertingPLCRadioSCADATelemetry
Type
RFP
Jurisdiction
Federal Government
Posted
Mar 28, 2025
Due
Jun 23, 2025
Updated
Jun 10, 2025

GDS Notes

  • Estimated value: The magnitude of construction is between $500,000.00 and $1,000,000.00.
  • Bid bond required: Yes
  • Mandatory site visit: Yes
  • Local integrator required: No
  • PLC details: PLCs/RTUs mentioned but brands/models not specified. The project involves upgrading medical air systems, which typically include PLCs for control and monitoring.
  • HMI details: HMI/SCADA mentioned but specific software not specified. The project involves upgrading medical air systems, which typically include HMIs for visualization and control.
  • Comms details: Network infrastructure mentioned but specific media/protocols not detailed. The project involves upgrading medical air systems, which typically require network communication for monitoring and control.
  • Project insights: {"bid_bond_required": "Yes, a bid guarantee is required in an amount not less than 20 percent of the bid price but shall not exceed $3,000,000.00. The Bid Guarantee is to be executed on a SF 24. Failure to furnish the required bid guarantee on the proper fo...
  • 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.