Estimate the daily reading and command workload supported by a smart meter fleet. Enter the active meter count, scheduled reads per meter, service-command rate, and successful communication rate. The calculator separates attempted tasks from completed tasks and reports the expected communication shortfall. This helps size head-end processing, daily operations, and exception queues without treating every scheduled task as successful.
Completed tasks represent expected successful meter interactions, not unique customer outcomes. Failed tasks may enter retries or field-work queues and therefore can create additional workload.
Use separate peak-hour modeling when reads and commands are concentrated into narrow collection windows.
For 100,000 meters, 24 reads per meter, 5 commands per 1,000 meters, and 98.5% success, the system attempts 2,400,500 tasks and completes about 2,364,493 tasks per day.
They are both counted as tasks here, although their data size and processing cost may differ.
The rate is multiplied by active meters and divided by 1,000.
Use a success rate consistent with your reporting definition; retry attempts are not separately added.
Yes. A fractional daily average can represent meters read less often than once per day.
A meter can generate many readings and commands, so task count is not a device count.
| Task type | Daily quantity |
|---|---|
| Meter reads | Meters × reads per meter |
| Remote commands | Meters ÷ 1,000 × command rate |
| Attempted tasks | Reads plus commands |
| Completed tasks | Attempted tasks × success rate |