Smart Grid Telemetry Database Sizing and Partitioning Brief
Formulate an architectural brief for ingesting, partitioning, and retaining high-frequency smart meter time-series data.
Use this template when designing or scaling time-series database clusters for AMI and grid sensor telemetry. It guides database engineers through ingestion throughput calculations, retention tiering, and partitioning strategies.
Role: Senior Time-Series Database Architect specializing in utility grid operations.
Context
- Utility operator: {{utility_operator}}
- Active meter and sensor fleet: {{meter_fleet_size}}
- Telemetry sampling frequency: {{sampling_frequency}}
- Target database engine: {{primary_database_engine}}
- Hot storage retention requirement: {{hot_retention_window}}
- Regulatory cold archive window: {{compliance_retention_period}}
Task
Produce an engineering brief outlining database architecture, sharding mechanisms, chunk sizing, and continuous aggregation policies to sustain smart grid telemetry ingestion without performance degradation.
Method
- Calculate raw write throughput per second based on {{meter_fleet_size}} and {{sampling_frequency}}.
- Compute daily and annual uncompressed versus compressed storage volumes for {{primary_database_engine}}.
- Define the optimal time and spatial partitioning keys to balance write distributor loads across cluster nodes.
- Establish the chunk interval sizing for hot storage to keep active working tables entirely in memory.
- Design downsampling rollups and continuous aggregate views for hourly and daily load profiling.
- Detail the automated data lifecycle policy moving records from {{hot_retention_window}} to {{compliance_retention_period}}.
- Specify backup and point-in-time recovery strategies tailored to append-heavy time-series tables.
Constraints
- MUST calculate exact data throughput figures using the provided fleet size and sampling frequency.
- MUST NOT recommend general-purpose relational schemas without explicit time-series optimizations.
- MUST define storage tiering transition triggers specifically for {{utility_operator}}.
- Keep technical specifications direct, modular, and implementation-ready.
Output format
- Section 1: Ingestion Throughput & Storage Footprint Calculations
- Section 2: Partitioning & Sharding Strategy
- Section 3: Downsampling & Rollup Architecture
- Section 4: Lifecycle Tiering & Cold Archive Schedule Total word count must remain between 400 and 650 words.
Self-review
- Confirm all 6 variables are referenced and contextualized.
- Verify storage calculations directly match the math implied by {{meter_fleet_size}} and {{sampling_frequency}}.
- Ensure all 7 method steps are addressed in order.
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.