SCADA Gateway Modernization Technical Brief

Role: Principal SCADA Systems Architect with 15+ years leading substation automation and utility communications infrastructure.

Context

• Operating Utility: {{utility_provider}}
• Target Network Segment: {{substation_network_zone}}
• Existing In-Field Protocols: {{legacy_rtu_protocols}}
• Target Modernization Standard: {{target_compliance_standards}}
• High-Availability Latency Budget: {{failover_latency_budget}}
• Physical & Electronic Security Level: {{security_perimeter_tier}}

Task

Draft an engineering modernization brief specifying the gateway migration path from legacy serial/network RTUs to modern compliant substation nodes for {{utility_provider}}, establishing architecture boundaries and deterministic failover parameters.

Method

1. Analyze the telemetry footprint and polling intervals across {{legacy_rtu_protocols}} in {{substation_network_zone}}.
2. Map legacy object addresses, points, and event records to data attributes mandated by {{target_compliance_standards}}.
3. Establish dual-homed network topology requirements aligned with {{security_perimeter_tier}} isolation.
4. Define buffer retention sizing during communication loss to ensure zero loss of Sequence of Events (SOE) logs.
5. Specify deterministic failover switching criteria adhering to {{failover_latency_budget}}.
6. Detail protocol translation latency bounds between upstream master dispatch and local IED controllers.
7. Detail cyber hardening specifications including certificate rotation and role-based access controls.

Constraints

• MUST maintain continuous telemetry visibility without exceeding {{failover_latency_budget}} during primary channel degradation.
• MUST NOT recommend architectures requiring manual onsite key injection during routine field commissioning.
• Keep interface definitions limited to transport, application layer mapping, and network zoning.
• Use unambiguous utility engineering terminology without marketing buzzwords.

Output format

• 1. Executive Modernization Overview (under 120 words)
• 2. Interface and Protocol Translation Matrix (structured table with legacy point types, target mappings, and update cadences)
• 3. Redundancy and Failover Specification (3 numbered technical bullets)
• 4. Security Perimeter Controls (4 concise technical requirements)

Self-review

• Confirm all legacy protocols from {{legacy_rtu_protocols}} are accounted for in the translation matrix.
• Verify that failover timings strictly respect {{failover_latency_budget}}.
• Ensure exact alignment with {{security_perimeter_tier}} requirements.