Skip to main content

πŸ›‘οΈ Data Reliability & Accuracy

This section documents the known areas of concern that affect the reliability and accuracy of data flowing through the platform β€” from the physical sensor, through IoT connectivity, into the software pipeline, and finally to device recharge/billing. It also covers the tools available to investigate issues and two journeys to follow depending on how much you already know about the problem.

Why this matters

Bad or missing data anywhere in this chain shows up as a bad customer-facing number β€” an incorrect flow reading, a stale dashboard, or a false leakage alert. This section exists to make investigating "why is this data wrong?" fast and repeatable.


🚦 Pick Your Journey​

There are two ways to use this section, depending on what you know when you start:

🎯 Journey A β€” I know my symptom🧩 Journey B β€” I don't know what's wrong
When to useYou already know what's failing β€” a specific alert, an offline device, a symptom someone described.Something's off but you don't yet know where the fault is.
How it worksLook up your symptom in a table, jump straight to its debug steps.Work through 4 checkpoints in order (Connectivity β†’ Data Arrival β†’ Data Correctness β†’ Billing). Each checkpoint lists the likely causes right there before you move to the next.
Go to🎯 Symptom Lookup🧩 Diagnostic Funnel
Not sure which to pick?

Default to 🎯 Symptom Lookup first β€” if your symptom isn't listed there, it'll point you to 🧩 Diagnostic Funnel automatically.


πŸ—ΊοΈ How to Navigate This Section​

Summary: Every investigation starts with one question β€” do you know the symptom? If yes, go straight to 🎯 Symptom Lookup; if not, work the 🧩 Diagnostic Funnel checkpoint by checkpoint. Both roads lead to the same area docs for verification steps, with the Monitoring Tools Reference available to look up any tool along the way.


πŸ—‚οΈ Areas of Concern (Reference)​

Both journeys link into these factor pages for the detailed verification steps. Use them directly if you already know which area the issue is in:

AreaDescription
πŸ”§ Sensor SideIssues originating from sensor selection, installation, damage, or configuration.
πŸ“‘ IoTConnectivity and hardware issues at the IoT device level.
πŸ’» Software IssuesIssues in the data pipeline and system architecture.
πŸ’³ Recharge IssuesIssues caused by device recharge or payment failures.

βœ… How It All Fits Together​

  1. 🎯 Symptom Lookup (Journey A) β€” know your symptom? Jump straight to the fix.
  2. 🧩 Diagnostic Funnel (Journey B) β€” don't know yet? Work the funnel, checkpoint by checkpoint.
  3. πŸ”§ Sensor Side / πŸ“‘ IoT / πŸ’» Software Issues / πŸ’³ Recharge Issues β€” both journeys land here for the detailed verification steps per factor.
  4. πŸ“˜ Monitoring Tools Reference β€” what each tool (Uptime Metrics, Offline Dashboard, Data Integrity Alerts, IoT Telemetry, Data Validation, Unit Reset, User Logs) shows and where to find it. Both journeys link back to this as needed β€” read it upfront if you're not yet familiar with the tools, or look things up as you go.
Status legend

Factors are tagged 🟒 Mitigation in place where an automated tool/alert already covers them, or 🟑 Status: partial/gap where verification currently relies on a manual check β€” these are the open items to prioritize automating.