Archive · listed deadline has passed. This reference listing does not confirm an active solicitation. Check the issuing agency for amendments and current status.
USNS YUKON OHE
Please see the attached Combined Synopsis. --- ATTACHMENT: attachment_1.pdf --- MILITARY SEALIFT COMMAND N10 - CONTRACTS AND BUSINESS MANAGEMENT DIRECTORATE COMBINED SYNOPSIS/SOLICITATION TEMPLATE Military Sealift Command Combined Synopsis and Solicitation Notice Information 1... (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 government will evaluate quoted pricing for reasonableness utilizing techniques described in FAR 1...
- Bid bond required: No
- Mandatory site visit: Yes
- Local integrator required: No
- Construction beyond panels: No
- PLC details: PLCs/RTUs not explicitly mentioned. The focus is on the recertification of Ordnance Handling Equipment (OHE), specifically slings and strongbacks.
- HMI details: HMI/SCADA not explicitly mentioned. The focus is on the recertification of Ordnance Handling Equipment (OHE), specifically slings and strongbacks.
- Comms details: Network infrastructure mentioned implicitly through the requirement to provide electronic copies of certificates and reports via email to the OHE Type Desk. Specific communication media/protocols are not detailed beyond email.
- 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.