Grid Historian Database Migration Architecture Matrix
Assess database target architectures for migrating legacy SCADA historians to scalable modern data stores.
Use this template when modernizing legacy operational technology data historians in electric transmission and distribution grids. It structures a technical feasibility matrix across ingestion, compliance, and reliability criteria.
Role: Senior Industrial Database Administrator specializing in OT-IT convergence and power grid SCADA telemetry.
Context
- Grid Transmission Operator: {{grid_operator_name}}
- Total Active SCADA Points: {{scada_tag_count}}
- Substation Telemetry Sampling Rate: {{sampling_rate_ms}}
- High Availability SLA: {{high_availability_sla}}
- Mandatory Cybersecurity Standard: {{cybersecurity_framework}}
- Annual Storage and Compute Budget: {{target_storage_budget}}
Task
Analyze target database architectures to replace legacy grid SCADA historians and generate a comprehensive feasibility matrix assessing performance, resilience, and compliance for electrical telemetry.
Method
- Calculate ingestion throughput requirements across {{scada_tag_count}} at {{sampling_rate_ms}} resolution.
- Audit candidate database engines against security controls specified in {{cybersecurity_framework}}.
- Evaluate high-availability clustering and zero-data-loss failover mechanisms to meet {{high_availability_sla}}.
- Analyze deadband compression, delta-encoding, and swinging door trending algorithms per engine.
- Benchmark concurrent query performance for real-time grid dispatch versus historical sequence-of-events analysis.
- Estimate 3-year total cost of ownership against {{target_storage_budget}}.
- Map migration complexity from existing OPC-UA and MQTT substation data streams for {{grid_operator_name}}.
Constraints
- MUST evaluate distributed SQL, dedicated time-series, and industrial cloud historian architectures.
- MUST explicitly evaluate compliance controls required under {{cybersecurity_framework}} (e.g., NERC CIP access controls).
- MUST NOT propose database targets with single points of failure across control room zones.
- Data retrieval ratings MUST guarantee sub-second latency for contingency dispatch queries.
Output format
- Modernization Strategy Overview (under 80 words).
- SCADA Historian Target Feasibility Matrix (Markdown table with columns: Architecture Target, Ingestion Headroom, High Availability Fit, Compliance Grade, Cost vs Budget, Overall Viability).
- Risk and Mitigation Summary (3-5 structured bullet points).
Self-review
- Throughput calculations accurately reflect {{scada_tag_count}} at {{sampling_rate_ms}} frequency.
- Failover ratings strictly meet the threshold defined in {{high_availability_sla}}.
- Security evaluations directly reference requirements from {{cybersecurity_framework}}.
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.