Archive · listed deadline has passed. This reference listing does not confirm an active solicitation. Check the issuing agency for amendments and current status.
Pressure Tank Inspection and Maintenance
Amendment 3 The purpose of this amendment is to correct an error in evaluation criteria. Soliciation closing date is extended to 5 June 2025. Amendment 2 The purpose of this cprrect CLIN ittems from the solicitation . Added ELIN sheet attachment. The closing date will be chang... (Federal Government | Due 2025-06-05)
AviationCybersecurityEmergency AlertingPLCRadioSCADATelemetry
Type
RFP
Jurisdiction
Federal Government
Posted
Jun 2, 2025
Due
Jun 5, 2025
Updated
Jun 5, 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. The ELINs provide estimated quantities for each item, and the offeror is to provide unit prices and am...
- Bid bond required: No
- Mandatory site visit: Yes
- Local integrator required: No
- Construction beyond panels: No
- PLC details: PLCs/RTUs mentioned but brands/models not specified. The focus is on the air compressor component of the system.
- HMI details: HMI/SCADA mentioned but specific software not specified. The contractor must ensure the entire system is at 100% operational efficiency to pass the DEKRA inspection.
- Comms details: Network infrastructure mentioned but specific media/protocols not detailed. The focus is on the operational efficiency of the pressure tank system and air compressor components.
- 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.
- Define remote access method, auditing/log retention, and IT/OT segmentation boundaries.