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.
Glossary
Bad Data Detection

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.
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.
Core Statistical Techniques
Statistical hypothesis testing frameworks used to identify, isolate, and eliminate gross measurement errors before they corrupt the state estimate.
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.
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.
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.
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.
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.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
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.
Related Terms
Explore the statistical tests, robust estimators, and cyber-physical attack vectors that define the frontier of measurement integrity in distribution system state estimation.
Normalized Residual Test
The primary statistical hypothesis test for identifying gross measurement errors. The residual (difference between measured and estimated value) is divided by its standard deviation to create a normalized index. If this index exceeds a predefined statistical threshold (typically 3.0), the measurement is flagged as bad data and removed from the estimation process. This test relies on the assumption that measurement noise follows a Gaussian distribution.
Chi-Square Test for Bad Data
A global detection test that evaluates the sum of squared weighted residuals against a Chi-Square distribution. If the objective function value exceeds a critical threshold determined by the degrees of freedom, the test indicates the presence of bad data somewhere in the measurement set. Unlike the normalized residual test, this method does not identify which specific measurement is erroneous, requiring subsequent largest normalized residual identification.
Least Absolute Value (LAV) Estimation
A robust state estimation criterion that minimizes the sum of absolute residuals rather than squared residuals. This approach automatically rejects outliers by assigning zero weight to measurements with large deviations, effectively performing bad data suppression without iterative re-weighting. LAV is particularly effective in distribution systems where communication noise and sensor drift produce non-Gaussian error distributions.
Huber M-Estimator
A maximum-likelihood-type estimator that bridges the gap between WLS and LAV. It applies quadratic weighting to small residuals (maintaining Gaussian efficiency) and linear weighting to large residuals (providing outlier resilience). The transition point is controlled by a tuning constant. This prevents a single bad measurement from corrupting the entire state estimate while preserving statistical optimality for clean data.
False Data Injection Attack (FDIA)
A cyber-physical attack vector where an adversary manipulates measurement data in a way that deliberately bypasses conventional bad data detection. By constructing an attack vector that lies in the column space of the Jacobian matrix, the injected errors cancel out in the residual calculation. This corrupts the state estimate without triggering the Chi-Square or normalized residual alarms, requiring advanced measurement redundancy analysis for mitigation.
Measurement Redundancy Analysis
The engineering practice of ensuring sufficient critical measurement pairs and critical sets exist to detect and identify bad data. A measurement is critical if its removal renders the system unobservable, meaning bad data on that measurement cannot be detected. Redundancy analysis identifies these vulnerabilities and guides the placement of additional sensors or pseudo-measurements to strengthen the bad data detection capability of the state estimator.

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.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us