SCADA Telemetry Database Cutover Checklist

Role: Principal Industrial Data Architect specializing in utility SCADA telemetry backends.

Context

• Operating utility: {{utility_operator}}
• Legacy data store: {{source_database_engine}}
• Destination platform: {{target_timeseries_db}}
• Total telemetry streams: {{telemetry_tag_volume}}
• Allowable cutover window: {{max_cutover_downtime}}
• Active raw retention duration: {{retention_policy_window}}

Task

Produce a comprehensive SCADA telemetry database cutover checklist to transition high-frequency sensor streams from legacy storage to a purpose-built time-series engine without losing critical grid state observations.

Method

1. Evaluate historical data backfill parity across all registered tags in {{source_database_engine}}.
2. Verify write throughput capacity on {{target_timeseries_db}} against burst peak rates from {{telemetry_tag_volume}}.
3. Validate downsampling rollups and chunk partition alignment configured for {{retention_policy_window}}.
4. Configure dual-ingestion pipelines to stream concurrent telemetry into both database layers.
5. Run automated delta queries to confirm timestamp precision and value fidelity across parallel streams.
6. Execute traffic cutover for upstream grid analytics clients within {{max_cutover_downtime}}.
7. Inspect real-time ingestion latency metrics and alert triggers post-switchover for {{utility_operator}}.

Constraints

• MUST mandate zero-data-loss verification before terminating legacy write paths.
• MUST NOT exceed the scheduled maintenance window of {{max_cutover_downtime}}.
• Include explicit verification criteria for edge telemetry timestamp skew.
• Keep all checklist items atomic with actionable binary verification states.

Output format

• Section 1: Pre-Cutover Ingestion Readiness Checklist (4-6 items with Pass/Fail checkboxes)
• Section 2: Live Cutover Execution Steps Checklist (5-7 sequential items with verification commands)
• Section 3: Post-Cutover Integrity and Rollback Safeguards (4-5 items with monitoring thresholds)

Self-review

• Check that {{target_timeseries_db}} and {{source_database_engine}} specific validations are present.
• Verify that all checklist items are actionable and binary.
• Confirm no migration downtime thresholds exceed {{max_cutover_downtime}}.