432 SPTS/CE Utility Monitoring Control Systems (UMCS) System Administrator (SA)

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: PLCs/RTUs mentioned as "Level 1 and 2 devices of the Purdue Model", but brands/models not specified. The SOW mentions ensuring these devices have current and accurate logic programmed.
• HMI details: HMI/SCADA mentioned as "UMCS frontend" and "Level 4 device". Specific software is not specified, but the SA will provide technical support for the frontend applications.
• Comms details: Network infrastructure mentioned in the context of troubleshooting network connectivity at Levels 4, 2, and 1 of the Purdue Model and Layers 1, 2, and 3 of the OSI Model. Specific media/protocols are not detailed, but the SA will maintai...
• 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.

Related