Wind River Software Maintenance and Licenses

PLEASE READ THIS ENTIRE NOTICE CAREFULLY AS IT CONSTITUES THE ONLY NOTICE THAT WILL BE ISSUED. The Naval Undersea Warfare Center, Division Newport (NUWCDIVNPT) intends to award a firm fixed price purchase order on a Brand Name Requirement basis for Wind River brand software re... (Federal Government | Due 2025-06-06)

CybersecurityPLCRadioRTUSCADATelemetry
Type
RFP
Jurisdiction
Federal Government
Posted
May 30, 2025
Due
Jun 6, 2025
Updated
Jun 5, 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 document specifies the use of VxWorks Operating System, implying the use of PLCs/RTUs that are compatible with this OS. However, specific PLC/RTU brands or models are not explicitly mentioned.
  • HMI details: The document mentions Wind River WorkBench for VxWorks 6.7 and 3.2 for VxWorks 6.8, which are development environments used for creating applications that could include HMI functionality. The document does not explicitly mention a separa...
  • Comms details: Network infrastructure is implied through the cybersecurity clauses (DFARS 252.204-7008, 252.204-7009, 252.204-7012), which require safeguarding covered defense information. However, specific communication media or protocols are not deta...
  • 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.