The $98K Edge Swing, Capital vs Operating

The $98K Edge Swing, Capital vs Operating

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 $98K Edge Swing, Capital vs Operating

The chapter’s Smart Factory Comparison sets a centralized design — 1,000 sensors feeding one $100K central server on $50K/year of bandwidth — against a distributed edge design of 1,000 sensors with $2 microcontrollers ($2K total) on $1K/year. It reports the edge design saving “$147K upfront + $49K/year.” This audit separates capital cost from operating cost to ask what the true one-time swing is, and whether that $147K is really an upfront number.

Companion to the chapter From Mainframes to IoT — every number here comes from that chapter.

See the relationship before changing it

The figure reads from left to right. The blue card is edge sensor count. The middle card applies this page's rule. The green card is upfront 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 edge sensor count, so the numeric fixture does not switch without explanation.

Edge sensor count changes upfront saving An input card leads through the rule saving = 100 thousand USD server - 2 USD x sensor count to the upfront saving result. INPUT PAGE INPUT APPLY THE RULE predict calculate check units OUTPUT RESULT
Walk the arrows. Edge compute capital grows per sensor while the central-server comparison stays fixed.

Derive the baseline in four named moves

  1. 1

    Name the input. The chapter baseline is 1000 sensors.

  2. 2

    Name the relationship. saving = 100 thousand USD server - 2 USD x sensor count

  3. 3

    Substitute with units. 100 - 0.002 x 1,000 = 98.0 thousand USD

  4. 4

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

Predict, then change edge sensor count

Try Predict the direction of saving = 100 thousand USD server - 2 USD x sensor count. Test another edge sensor count, then compare upfront saving.

1000 sensors
Chapter baseline
Upfront saving

Observe Edge compute capital grows per sensor while the central-server comparison stays fixed. Reset edge sensor count to 1000 and compare upfront saving.

Explain Edge compute capital grows per sensor while the central-server comparison stays fixed.

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 edge sensor count moves here. Field effects named in the technical boundary stay fixed.
TryRecompute Edge compute cost: 1,000 x 2 = 2,000 dollars.
ObserveTrack Upfront (capital) saving: 100,000 - 2,000 = 98,000 dollars, which is exactly the $98K the chapter's own quiz gives.
ExplainExplain The chapter's "$147K upfront" is actually 98,000 (upfront capital) + 49,000 (the first year of bandwidth) = 147,000 — a first-year total, not a purely upfront number.

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

Ada: The smart-factory comparison puts a $100K central server against 1,000 edge sensors at $2 each, and reports the distributed design saving “$147K upfront + $49K/year.” The $49K/year is right, and the $147K deserves a second look — so let me separate capital cost from operating cost cleanly.

  • Edge compute cost: 1,000 x 2 = 2,000 dollars
  • Upfront (capital) saving: 100,000 - 2,000 = 98,000 dollars, which is exactly the $98K the chapter’s own quiz gives
  • Bandwidth is a recurring cost, so its saving is annual: 50,000 per year - 1,000 per year = 49,000 per year
  • The chapter’s “$147K upfront” is actually 98,000 (upfront capital) + 49,000 (the first year of bandwidth) = 147,000 — a first-year total, not a purely upfront number.

Keeping the $98K one-time capital saving separate from the $49K-per-year operating saving is the honest way to read edge economics: the capital swing is real, but it is the recurring line that compounds, and folding one year of it into an “upfront” figure quietly overstates the day-one cost advantage.

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

Technical boundaries. This edge-cost model deliberately does not simulate workload variation, maintenance, or changing bandwidth prices. It contrasts the fixed $100-per-device cloud cost with $2-per-device edge compute and the stated $49,000 annual bandwidth saving.