Databases
AuraScore 83/100

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.

Template

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

  1. Calculate ingestion throughput requirements across {{scada_tag_count}} at {{sampling_rate_ms}} resolution.
  2. Audit candidate database engines against security controls specified in {{cybersecurity_framework}}.
  3. Evaluate high-availability clustering and zero-data-loss failover mechanisms to meet {{high_availability_sla}}.
  4. Analyze deadband compression, delta-encoding, and swinging door trending algorithms per engine.
  5. Benchmark concurrent query performance for real-time grid dispatch versus historical sequence-of-events analysis.
  6. Estimate 3-year total cost of ownership against {{target_storage_budget}}.
  7. 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

  1. Modernization Strategy Overview (under 80 words).
  2. SCADA Historian Target Feasibility Matrix (Markdown table with columns: Architecture Target, Ingestion Headroom, High Availability Fit, Compliance Grade, Cost vs Budget, Overall Viability).
  3. 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}}.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-databases
energy-utilities
scada
grid-operations
data-migration