[MATOC AREAIII WORKPLAN ONLY] SMYU 26-1029 REPLACE RADIO ANTENNA PLATFORM HILL 180

PROJECT TITLE: SMYU 26-1029 REPLACE RADIO ANTENNA PLATFORM HILL 180 PROJECT LOCATION: OSAN AB, ROK REPLACE RADIO ANTENNA PLATFORM HILL 180 OSAN AB, SEE SOW AND DRAWINGS IN DETAILS. 1. THIS IS A REQUEST OF PROPOSAL (RFP) ISSUED TO EXISTING MATOC WORK PLAN CONTRACTORS ONLY OF AR... (Federal Government | Due 2025-06-10)

Emergency AlertingPLCRadioSCADATelemetry
Type
RFP
Jurisdiction
Federal Government
Posted
Jun 2, 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
  • Local integrator required: Yes
  • Construction beyond panels: Yes
  • PLC details: PLCs/RTUs are not explicitly mentioned. The project focuses on the structural replacement of the antenna platform.
  • HMI details: HMI/SCADA is not explicitly mentioned. The project focuses on the structural replacement of the antenna platform.
  • Comms details: The project involves replacing a radio antenna platform, implying radio communication is involved. However, the specific communication details, network infrastructure, media, and protocols are not detailed in this RFP.
  • Project insights: {"bid_bond_required": "No bid bond requirement mentioned", "mandatory_site_visit": "Offerors who intend to propose on this solicitation are strongly encouraged to attend the site visit. See site visit clause in Section L for the schedule. This indicates an...
  • 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.