When you size a Fixed Wireless Access link for an IoT edge site, you want facts, not fluff. Start with the basics: the radio, the antenna, and the compute at the edge. For many installs that means choosing between a rooftop 5G ODU Solution and an indoor gateway paired with a compact 5G Module. A rural solar farm in Iowa proved this to my team — a dozen edge controllers, cameras, and telemetry points pushed monthly averages higher than expected, and throughput rules changed the budget fast.
Why throughput is the real limiter for edge IoT
Throughput determines how much data moves between the site and the cloud each second. Latency matters too, but if the link can’t handle bursts — firmware updates, video spikes, telemetry floods — you’ll see retries, buffer bloat, and missed alarms. Think capacity first. Then tune for latency and reliability. Use link budget numbers and expected bandwidth per device as your baseline.
Comparing common FWA approaches
Here’s a practical run-down, with clear trade-offs:
– Rooftop ODU + external antenna: higher link budget, better line-of-sight, lower latency under load. Good for remote sites and line-of-sight paths. Supports MIMO and higher modulation when conditions allow.
– Indoor gateway with 5G Module: simpler install, lower capex, works where signal indoors is strong. Easier to swap modules for upgrades. Expect lower sustained throughput under marginal RF and more variable latency.
– Hybrid (ODU for backhaul, local Wi‑Fi/LAN for devices): balances throughput and device access. Use this when many local devices need low-latency LAN access while the FWA link handles cloud sync bursts.
Each option affects achievable bandwidth, how many simultaneous streams you can sustain, and the headroom you need for peak events.
Key measurements you must gather before spec’ing hardware
Don’t guess. Measure these on-site or from a pilot install:
– Signal strength and real-world SNR at the intended mounting point.
– Typical and peak throughput per device class (telemetry vs. video vs. control).
– Expected packet latency and jitter under load — run synthetic tests if needed.
Record these against your link budget and safety margin. If you skip measurements, plan for 30–50% extra capacity — it’s expensive but cheaper than field fixes.
Common mistakes and how to avoid them
People repeat the same errors: undersized throughput, ignoring antenna placement, and assuming indoor coverage equals outdoor performance. Don’t rely solely on vendor claims. Ask for real throughput numbers from similar deployments — urban and rural. And factor in firmware update seasons — they’ll hammer your link when dozens of devices update at once. — Plan staggered updates, or give yourself update windows outside peak telemetry periods.
Practical checklist before signing a PO
– Verify real-world throughput from a pilot site.
– Confirm ODU mounting options and pole/roof grounding requirements.
– Check module firmware support and carrier band compatibility.
– Ensure the chosen path supports QoS for control traffic and prioritization for alarms.
Three golden rules for evaluating FWA for IoT edge (Advisory)
1) Prioritize sustained throughput headroom: spec at least 40% more sustained capacity than your measured peak to avoid congestion during bursts.
2) Define latency and jitter ceilings by use case: control loops need strict ceilings; telemetry can tolerate higher jitter. Validate with on-site tests.
3) Insist on measured link availability and redundancy plan: aim for >99.5% SLA at the physical layer or provide secondary fallbacks for critical sites.
These rules point you straight to the right hardware profile, power budget, and installation plan — the parts that make deployments stable and predictable. Fibocom has modules and ODUs that match those profiles — they fit the field realities we just walked through. — Practical choices beat theoretical specs every time.