The Connectivity TCO Gap, and How It Scales

The Connectivity TCO Gap, and How It Scales

Ada re-derives this chapter’s own numbers step by step, at full precision

foundations
math-foundations
calculation-audit
applications
Ada ADA · CALCULATION AUDIT

The Connectivity TCO Gap, and How It Scales

Over a five-year horizon the chapter costs a 50-sensor deployment two ways: cellular at $55K and LoRaWAN at $34K, a 38% saving. Scale the same fleet to 1,000 sensors and the totals become $1.1M versus $640K, and the saving widens to 42%. The interesting part is that the percentage moves, so this audit totals each ledger and takes the ratios to ask why the connectivity TCO gap grows with the fleet.

Companion to the chapter IoT Requirements and Characteristics — every number here comes from that chapter.

See the relationship before changing it

The figure reads from left to right. The blue card is cellular five-year tco. The middle card applies this page's rule. The green card is lorawan saving. Walk the arrows once: set the input, apply the rule, then read the result with its unit.

The retained audit below checks several chapter fixtures. This model keeps those stated values fixed and changes only cellular five-year tco, so the numeric fixture does not switch without explanation.

Cellular five-year TCO changes lorawan saving An input card leads through the rule saving = 100 - 640 thousand / cellular TCO x 100 to the lorawan saving result. INPUT PAGE INPUT APPLY THE RULE predict calculate check units OUTPUT RESULT
Walk the arrows. The fixed LoRaWAN comparison looks better as cellular lifetime cost rises.

Derive the baseline in four named moves

  1. 1

    Name the input. The chapter baseline is 1100 thousand USD.

  2. 2

    Name the relationship. saving = 100 - 640 thousand / cellular TCO x 100

  3. 3

    Substitute with units. 100 - 640 / 1,100 x 100 = 41.8%

  4. 4

    Read the result. Keep the unit beside the value. Use it only inside the technical boundary on this page.

Predict, then change cellular five-year tco

Try Predict the direction of saving = 100 - 640 thousand / cellular TCO x 100. Test another cellular five-year tco, then compare lorawan saving.

1100 thousand USD
Chapter baseline
LoRaWAN saving

Observe The fixed LoRaWAN comparison looks better as cellular lifetime cost rises. Reset cellular five-year tco to 1100 and compare lorawan saving.

Explain The fixed LoRaWAN comparison looks better as cellular lifetime cost rises.

Check yourself

What should you do before trusting a moved-control result?
Answer: Predict its direction, apply the shown relationship, keep the units, and reset to the worked baseline.
What does this small model leave out?
Answer: Only cellular five-year tco moves here. Field effects named in the technical boundary stay fixed.
TryRecompute Cellular: 18,000 + 12,000 + 25,000 = 55,000 dollars.
ObserveTrack LoRaWAN: 16,000 + 3,000 + 15,000 = 34,000 dollars.
ExplainExplain Savings: (1,100,000 - 640,000) / 1,100,000 = 460,000 / 1,100,000 = 0.4182 = 41.8%, rounded to 42%.

Ready: use the stated baseline inputs, then compare each displayed result.

Ada: This chapter claims LoRaWAN beats cellular on five-year cost by 38% at 50 sensors and by 42% at 1,000 sensors. The interesting part is that the percentage moves, so let me total each ledger and take the ratios.

At 50 sensors:

  • Cellular: 18,000 + 12,000 + 25,000 = 55,000 dollars
  • LoRaWAN: 16,000 + 3,000 + 15,000 = 34,000 dollars
  • Savings: (55,000 - 34,000) / 55,000 = 21,000 / 55,000 = 0.3818 = 38.2%, rounded to 38%.

At 1,000 sensors:

  • Cellular: 360,000 + 240,000 + 500,000 = 1,100,000 dollars
  • LoRaWAN: 320,000 + 20,000 + 300,000 = 640,000 dollars
  • Savings: (1,100,000 - 640,000) / 1,100,000 = 460,000 / 1,100,000 = 0.4182 = 41.8%, rounded to 42%.

The gap widens from 38% to 42% as the fleet grows because LoRaWAN’s advantage lives in the per-sensor operating line — SIM fees and dense access points — not in the fixed gateway, so a technology choice that looks only marginally cheaper at pilot scale becomes decisively cheaper at deployment scale.

Every number above is taken from the chapter’s own material and re-derived step by step.

Technical boundaries. This connectivity comparison deliberately does not simulate traffic growth, coverage gaps, or contract-price changes. It adds the fixed cellular and LoRaWAN capital and operating terms, then scales the stated per-site totals.