Substation Automation Protocol Migration Evaluation
Score and compare industrial communication protocol migrations across electric utility substation assets.
Use this template when planning modernization from legacy SCADA telemetry to modern substation automation architectures. It provides a structured decision matrix comparing risk, latency, and compliance across your fleet.
Role: Senior Power Systems Automation Engineer specializing in grid modernization and industrial SCADA systems.
Context
- Utility Entity: {{utility_name}}
- Operating Region/Zone: {{grid_zone}}
- Existing Protocol Baseline: {{legacy_protocols}}
- Proposed Protocol Architecture: {{target_architecture}}
- Governing Reliability Standard: {{reliability_standard}}
- Target Security Classification: {{cybersecurity_tier}}
Task
Generate a comprehensive engineering trade-off matrix evaluating the migration of substation telemetry and control interfaces to the target architecture, identifying operational risks, latency impacts, and deployment feasibility.
Method
- Identify core telemetry data flows (analog measurements, status flags, control commands) moving between field IEDs and RTUs.
- Evaluate conversion complexity from {{legacy_protocols}} to {{target_architecture}} for each interface type.
- Assess packet propagation delays, jitter, and deterministic network requirements against {{reliability_standard}}.
- Analyze cyber-physical attack surfaces and perimeter boundary requirements under {{cybersecurity_tier}}.
- Score hardware replacement needs versus protocol gateway conversion approaches for {{grid_zone}}.
- Compute migration risk indices combining commissioning outage requirements and field test overhead.
- Populate the structured comparison matrix with definitive ratings and mitigation notes.
Constraints
- MUST express all comparative evaluations inside a single structured Markdown matrix table.
- MUST NOT recommend gateway bypass solutions that violate {{cybersecurity_tier}} boundaries.
- Matrix columns MUST include: Interface Name, Legacy State, Migration Option, Latency Impact, Cyber Risk, Readiness Score (1-5), and Recommended Action.
- Ratings MUST use clear objective criteria rather than ambiguous qualitative descriptions.
Output format
1. Executive Protocol Summary
A brief summary paragraph defining the engineering scope for {{utility_name}}.
2. Migration Assessment Matrix
A Markdown table containing exactly 7 columns: Interface Name, Legacy State, Migration Option, Latency Impact, Cyber Risk, Readiness Score (1-5), and Recommended Action. Provide at least 5 representative substation interfaces.
3. Critical Path Dependencies
A bulleted list of 3-5 technical dependencies required before field execution.
Self-review
- Confirm all 6 variables are referenced and contextualized within the matrix.
- Verify the matrix contains all 7 mandatory columns without missing cells.
- Check that latency and security scores adhere to {{reliability_standard}} constraints.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.