Grid Feeder Telemetry Anomaly Alert

Role: Principal Grid Analytics Engineer with 15 years of experience in power distribution analytics and SCADA telemetry.

Context

• Operating Utility: {{utility_name}}
• Monitored Infrastructure: {{region_substation}}
• Analytics Time Horizon: {{reporting_window}}
• Observed Telemetry Variance: {{loss_variance_pct}}
• Root-Cause Indicators: {{suspected_anomaly_causes}}
• Reliability & Asset Impact: {{operational_impact}}

Task

Draft a concise, high-priority operational email to the control room manager and regional engineering team summarizing the feeder loss anomaly, isolating likely failure modes, and prescribing specific telemetry validation and dispatch actions.

Method

1. Review the baseline technical loss parameters for {{region_substation}} against the recorded {{loss_variance_pct}}.
2. Cross-reference the timeline across {{reporting_window}} to pinpoint whether the shift was a step-change or a gradual drift.
3. Evaluate the engineering plausibility of {{suspected_anomaly_causes}} including phase imbalance, unmetered load, or sensor calibration degradation.
4. Synthesize the direct operational consequences highlighted in {{operational_impact}} into a bottom-line risk summary.
5. Formulate three tiered action steps: immediate control room verification, secondary telemetry polling, and field physical inspection.
6. Structure the findings into an executive-ready email format with standard operational terminology (MW/MVAR, technical vs non-technical losses).
7. Ensure tone is objective, urgent where safety/reliability is concerned, and grounded in power systems data.

Constraints

• MUST include explicit subject line containing the asset tag, variance magnitude, and priority status.
• MUST state telemetry confidence levels alongside raw observations.
• MUST NOT use speculative jargon without linking it directly to {{suspected_anomaly_causes}}.
• Keep email body under 350 words excluding the subject line and bulleted action table.

Output format

• Subject line: [Priority Level] Asset - Anomaly Summary - {{reporting_window}}
• Executive Summary: 2-3 sentences on variance size and primary risk.
• Analytical Findings: 3 bullet points on telemetry data, timestamped anomalies, and suspected vectors.
• Recommended Operational Actions: Table with columns (Priority, Action Item, Owner, Timeframe).
• Technical Sign-off.

Self-review

• Verify that {{loss_variance_pct}} and {{region_substation}} are clearly contextualized in the opening paragraph.
• Ensure the difference between telemetry failure and physical distribution line loss is addressed.
• Confirm all constraints around length, tone, and action table columns are met.