SCADA Historian Replacement Trade-Off Matrix
Assess replacement architectures for legacy SCADA grid historians against reliability, latency, and compliance benchmarks.
Use this template when an electric or gas utility needs to replace or modernize a legacy plant historian. It yields a structured trade-off matrix examining failover targets, ingestion guarantees, and cybersecurity posture.
Role: Senior SCADA Database Specialist with expertise in critical infrastructure telemetry and substation historian migrations.
Context
- Electric utility name: {{utility_name}}
- Monitored substation count: {{substation_count}}
- Existing historian vendor: {{legacy_historian_vendor}}
- Recovery target: {{failover_rpo_rto}}
- Cybersecurity compliance standard: {{cybersecurity_framework}}
- Annual storage and licensing budget: {{target_storage_budget}}
Task
Develop a comparative trade-off matrix assessing potential database architectures to modernize or replace {{legacy_historian_vendor}} while guaranteeing grid reliability for {{utility_name}}.
Method
- Map data ingress patterns across {{substation_count}} substations using industrial protocols (DNP3, IEC 61850, OPC-UA).
- Document operational bottlenecks, proprietary lock-in risks, and maintenance overhead of {{legacy_historian_vendor}}.
- Identify viable modern historian and distributed database alternative architectures within {{target_storage_budget}}.
- Contrast consistency models, sub-second write durability, and failover capabilities against {{failover_rpo_rto}}.
- Audit compliance controls, role-based access, and immutable audit trails required by {{cybersecurity_framework}}.
- Evaluate schema flexibility for dynamic operational grid tag modifications without downtime.
- Synthesize migration complexity, operational resilience, and licensing impact into a structured trade-off matrix.
Constraints
- MUST evaluate specific disaster recovery scenarios against {{failover_rpo_rto}} thresholds.
- MUST NOT exclude regulatory data segregation rules mandated by {{cybersecurity_framework}}.
- Provide concrete technical justifications rather than generalized vendor claims.
- Limit architectural comparison to practical grid operational environments.
Output format
- Current State Baseline: Table summarizing the bottlenecks and licensing limitations of {{legacy_historian_vendor}}.
- Historian Trade-Off Matrix: Markdown matrix comparing architectural alternatives across 6-8 operational dimensions with scored ratings and trade-off notes.
- Migration Feasibility Assessment: Structured verdict recommending the primary target architecture and initial mitigation steps (under 300 words).
Self-review
- Are the constraints of {{cybersecurity_framework}} explicitly reflected in the matrix criteria?
- Does the evaluation address the scale of {{substation_count}} substations realistically?
- Are failover metrics verified against {{failover_rpo_rto}}?
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.