IIoT, SCADA & Edge Connectivity worked example
OT Data Completeness at 110% tag delivery rate: a worked example
This scenario runs the ot data completeness calculation on the strong side: 110% tag delivery rate, with every other input held at its documented default. Use it when an analytics lead, MES owner, or historian admin needs a clean count of usable tag samples in a period before signing off on a model rebuild or KPI dashboard.
The inputs for this scenario
- Tags published per polling cycle: 500 tags / cycle (unchanged)
- Planned polling cycles in the period: 60 cycles (unchanged)
- Tag delivery rate: 110 % (raised for this scenario; the documented default is 99.5)
- In-spec quality rate: 98 % (unchanged)
Working through the calculation
- Applying the documented formula (Gross tag samples = tags per cycle × planned cycles) to the inputs above produces each figure below.
- At this operating point the engine returns 32,340 tags for complete tag samples per period, the number this scenario is built around.
- At this operating point the engine returns 30,000 tags for gross tag samples per period.
- At this operating point the engine returns -3,000 tags for delivery loss.
- At this operating point the engine returns 660 tags for quality loss.
How this compares with the baseline
- Against the tool's baseline example, where tag delivery rate sits at 99.5% and the headline result is 29,253 tags, this scenario comes in 10.55% above the baseline at 32,340 tags.
- Use it when validating historian coverage, sizing data pipelines, or qualifying a dataset for analytics or ML. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.
Results at a glance
- Complete tag samples per period: 32,340 tags (headline result)
- Gross tag samples per period: 30,000 tags
- Delivery loss: -3,000 tags
- Quality loss: 660 tags
Run it with your numbers
- Every input above is editable in the live OT Data Completeness calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.