Inferensys

Glossary

Bad Data Detection

Bad data detection is the statistical process of identifying and eliminating gross measurement errors, sensor failures, or communication noise from a power system's measurement set before they corrupt the state estimation solution.
Large-scale analytics wall displaying performance trends and system relationships.
MEASUREMENT INTEGRITY

What is Bad Data Detection?

Bad Data Detection encompasses the statistical techniques used to identify gross measurement errors, sensor failures, or communication noise before they corrupt the state estimate.

Bad Data Detection is the algorithmic process of identifying and eliminating gross measurement errors in power system telemetry before they corrupt the state estimator solution. It applies statistical hypothesis tests, primarily the Chi-Square test and Normalized Residual test, to analyze the discrepancy between raw sensor measurements and the estimated network state, flagging anomalies that exceed a defined confidence threshold.

When a measurement's normalized residual—its deviation divided by its standard deviation—exceeds a statistical limit (typically 3 sigma), it is classified as bad data and removed or corrected. This process is critical for maintaining observability integrity, as a single faulty SCADA reading or communication noise spike can propagate through the Weighted Least Squares algorithm, distorting voltage profiles and misleading grid operators about the true system state.

BAD DATA DETECTION

Core Statistical Techniques

Statistical hypothesis testing frameworks used to identify, isolate, and eliminate gross measurement errors before they corrupt the state estimate.

01

Chi-Square Test

A global hypothesis test applied to the sum of weighted squared residuals from the state estimation solution. The test statistic follows a Chi-Square distribution with degrees of freedom equal to the measurement redundancy.

  • Null Hypothesis (H₀): No bad data exists in the measurement set.
  • Detection Logic: If the computed objective function exceeds a critical threshold (e.g., χ² at 95% confidence), the null hypothesis is rejected, indicating the presence of at least one gross error.
  • Limitation: Identifies that bad data exists but does not locate which specific measurement is corrupted.
95%
Typical Confidence Threshold
02

Normalized Residual Test

The primary method for identifying specific bad measurements after the Chi-Square test flags a problem. Each measurement residual is divided by its corresponding residual standard deviation to compute the normalized residual.

  • Largest Normalized Residual (LNR) Test: The measurement with the highest absolute normalized residual is statistically the most likely to be bad data.
  • Threshold Logic: If the LNR exceeds a critical value (typically 3.0 for a 3-sigma rule), it is flagged for removal.
  • Iterative Process: The suspect measurement is removed and the state estimation is re-run until the Chi-Square test passes.
3.0
Standard LNR Threshold
04

Hypothesis Testing Framework

Bad data detection is formalized as a binary hypothesis test with controlled error probabilities to balance sensitivity against false alarms.

  • Type I Error (α): False positive—flagging a valid measurement as bad. Typically set to 1% or 5%.
  • Type II Error (β): False negative—failing to detect actual bad data. Minimized by maximizing measurement redundancy.
  • Detection Probability: The power of the test increases with larger measurement errors and higher redundancy. A 20% gross error in a measurement with high sensitivity is detected with near certainty.
1-5%
False Positive Rate
05

Gross Error Sources

Bad data originates from multiple points in the measurement-to-control pipeline, each with distinct statistical signatures.

  • Sensor Drift: Gradual calibration decay in current transformers (CTs) and potential transformers (PTs) producing biased measurements.
  • Communication Noise: Bit errors in SCADA telemetry frames causing sporadic spikes in reported values.
  • Time Skew: Mismatched timestamps between asynchronous SCADA scans creating apparent inconsistencies that are not physical.
  • Topology Mismatch: An incorrect breaker status in the network model causes the estimator to solve the wrong topology, producing large residuals on multiple adjacent measurements.
06

Least Absolute Value (LAV) Estimation

An alternative estimation criterion that inherently rejects bad data without requiring iterative detection-removal cycles. Instead of minimizing the sum of squared residuals, LAV minimizes the sum of absolute residuals.

  • Automatic Rejection: The LAV estimator naturally places zero weight on outlier measurements, effectively identifying and discarding bad data in a single solution.
  • Breakdown Point: LAV can tolerate up to 50% contaminated measurements if redundancy is sufficient, far exceeding WLS robustness.
  • Computational Cost: Historically more expensive than WLS, but modern interior-point linear programming solvers have made LAV practical for online distribution system state estimation.
BAD DATA DETECTION

Frequently Asked Questions

Clear, technical answers to the most common questions about identifying and mitigating gross measurement errors in power system state estimation.

Bad data detection is a statistical post-processing module that identifies gross measurement errors, sensor failures, or communication noise before they corrupt the final state estimate. After the state estimator converges, the algorithm analyzes the measurement residuals—the difference between the raw telemetry and the estimated values. If a residual is statistically too large, the corresponding measurement is flagged as suspect. The core principle is that a single gross error on one meter will propagate through the Weighted Least Squares (WLS) solution, distorting the residuals of many measurements, but the largest normalized residual typically points to the source. This process is critical for maintaining the integrity of Distribution System State Estimation (DSSE) in modern smart grids.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.