Analytics & ML · Study deck
Validation and Outlier Detection
Picture a greenhouse report that says humidity is 108 percent.
Data Dora is your guide for this deck.

After studying this chapter
Learning objectives
You will be able to:
- Explain: A mobile air-quality study might group 0.38-0.42 um particle counts by library, park walk, traffic street, car, and indoor context.
- Explain: Hard failures can be rejected for automation, but the original payload, failed rule, quality state, and handling decision should remain available for audit.
- Explain: Hard rules reject impossible data: malformed payloads, values beyond sensor limits, invalid timestamps, and impossible rates of change.
- Explain: Treating every warning as a hard reject loses useful evidence; treating every warning as valid poisons downstream analytics.
Major section
Start With the Story · Validation Stops Bad Data
The message arrived on time and looks tidy, yet using it could trigger the wrong control action.
- JavaScript Object Notation, or JSON, is a text format for named data fields.
- A payload means the useful data carried inside a message.
- Valid structure does not prove that the values make sense.
Major section
Rules Plus Outlier Bounds · Qualitative Evidence Has a Validation Workflow
Validation should run in layers.
- Hard rules reject impossible data: malformed payloads, values beyond sensor limits, invalid timestamps, and impossible rates of change.
- Treating every warning as a hard reject loses useful evidence; treating every warning as valid poisons downstream analytics.
- Hard validation protects control decisions.
- MADUses median absolute deviation.
Major section
Compare Sensor Agreement · Policy for Failed Data
A Bland-Altman record makes method comparison explicit.
- When a deployment compares places, people, or measurement methods, validation needs more than a pass/fail rule.
- A mobile air-quality study might group 0.38-0.42 um particle counts by library, park walk, traffic street, car, and indoor context.
- Each cell is an observed count.
Major section
Summary · Key Takeaway
Validation protects IoT analytics before data enters dashboards, models, alerts, and control loops.
- Hard failures can be rejected for automation, but the original payload, failed rule, quality state, and handling decision should remain available for audit.
- The practical goal is traceable quality state.
- Each reading should become valid, flagged, quarantined, or rejected for a named reason.
Deck summary
Key takeaways
The message arrived on time and looks tidy, yet using it could trigger the wrong control action.
- Validation should run in layers.
- A Bland-Altman record makes method comparison explicit.
- Validation protects IoT analytics before data enters dashboards, models, alerts, and control loops.
Retrieval practice
Recall check 1 of 5

Data Dora says: answer from memory, then check your reasoning.
Q1A reading is quarantined after a range rule fails. What record lets an auditor replay the decision?
Show answer
Answer: A The rule and evidence explain why this reading was held.
Retrieval practice
Recall check 2 of 5

Data Dora says: answer from memory, then check your reasoning.
Q2A soil-moisture sensor reports percentage of saturation on a 0-100 percent scale. Which validation rule most directly catches a reading of 980 percent?
Show answer
Answer: B Physically impossible values are best caught by simple range validation.
Retrieval practice
Recall check 3 of 5

Data Dora says: answer from memory, then check your reasoning.
Q3A reading is physically impossible for control, while another is unusual but plausible. How should validation treat them?
Show answer
Answer: A Hard rejection protects action; a soft flag preserves uncertain evidence.
Retrieval practice
Recall check 4 of 5

Data Dora says: answer from memory, then check your reasoning.
Q4With Q1 = 21 and Q3 = 24, what upper fence does the 1.5 * IQR rule use?
Show answer
Answer: C IQR = 24 - 21 = 3, so the upper outlier fence is 24 + 1.5 × 3 = 28.5.
Retrieval practice
Recall check 5 of 5

Data Dora says: answer from memory, then check your reasoning.
Q5Why is silently deleting every reading that fails validation a poor policy?
Show answer
Answer: B Silent deletion hides quality evidence and can bias downstream analytics.
Print reference
Answers
Answer key.
- A · The rule and evidence explain why this reading was held.
- B · Physically impossible values are best caught by simple range validation.
- A · Hard rejection protects action; a soft flag preserves uncertain evidence.
- C · IQR = 24 - 21 = 3, so the upper outlier fence is 24 + 1.5 × 3 = 28.5.
- B · Silent deletion hides quality evidence and can bias downstream analytics.