Industrial teams assessing LoRa technology for the Internet of Things (IoT) are evaluating more than a wireless link. They need to consider how sensors, gateways, network services and application systems fit together—and whether the approach suits the information their operation needs to collect. Semtech’s fiscal 2019 annual report positioned its LoRa devices and radio-frequency technology as a platform for low-power wide area networks (LPWANs), with applications that included industrial automation, metering and other connected equipment.
The report is a historical snapshot, not a statement of today’s deployment levels or product roadmap. Its figures and descriptions nevertheless illustrate how the company framed LoRa’s role in IoT infrastructure and what automation decision-makers should examine when assessing a wireless sensing architecture.
LoRa technology and the industrial IoT use case
Semtech described IoT as a way to connect large numbers of devices to cloud-based systems, where data could be used for analysis and operational decision-making. In industrial settings, that broad idea includes applications such as automated meter reading, instrumentation and equipment monitoring. These use cases depend on connecting sensors and other endpoints with the systems that collect or use their information.
LoRa technology was presented as a radio-frequency platform for LPWAN applications. The company highlighted low power and long range as characteristics that made its wireless products suitable for machine-to-machine and IoT applications. For an automation team, the relevant question is not simply whether a technology can connect a device. It is whether the complete system can support the required endpoints, coverage, data flow and integration needs of the application.
The report also described LoRa-based products as part of Semtech’s broader Wireless and Sensing portfolio, alongside specialized sensing products and power devices. This matters when planning an implementation: an IoT deployment involves devices at the edge, but also the surrounding network and application components needed to put their data to work.
What the fiscal 2019 network figures indicate
Semtech reported that 243,000 LoRa-based gateways had been deployed globally by the end of fiscal 2019. It said those gateways were capable of supporting 1.2 billion LoRa-based end nodes. The report separately put cumulative deployed LoRa-based end nodes at 87 million. These measures describe different things: gateway capacity is not the same as the number of endpoints actually deployed.
The annual report also noted that more than 100 LoRaWAN-based network operators were active worldwide at the end of 2018. Together, these figures show the distinction between several parts of an IoT ecosystem:
- End nodes are the connected devices or endpoints that generate or transmit data.
- Gateways form part of the network infrastructure supporting communication with those endpoints.
- Network operators and services provide another layer in the broader deployment model.
For system integrators and plant leaders, the practical takeaway is to assess actual network availability and application requirements rather than treating a headline capacity figure as proof of local coverage or an implementation guarantee. The report’s figures were global and specific to its reporting period.
Assessing LoRa for automation projects
Start with the application
Define what the connected device needs to report and how the information will be used. The source identifies industrial automation, automated meter readers and IoT among the relevant application areas, but it does not prescribe a single architecture for them. Requirements will depend on the specific monitoring or control task and the surrounding system.
Map the full connection path
Consider how data moves from the sensing device through the wireless network and into the application that consumes it. Semtech announced its first LoRa Cloud Services platform for location-based services during fiscal 2019, illustrating that the ecosystem could extend beyond radio devices and gateways. The report does not provide implementation details, so teams should establish which network and service components are required for their own deployment.
Consider the supplier and integration context
Semtech’s report describes its Wireless and Sensing products as serving industrial, medical and communications applications, and notes that its LoRa products were predominantly sold through distributors. For procurement and project planning, this is a reminder to clarify product sourcing and technical support arrangements early, alongside interface and integration requirements. A reported customer design win, or the existence of a product platform, does not by itself establish that a solution will meet a particular plant’s needs.
Innovation and infrastructure are different measures
Semtech reported record net sales of $627.2 million for fiscal 2019 and cited growth across its product groups. It also identified IoT, data centers and mobile markets as growth areas shaped by trends including connectivity and mobility. Those corporate results provide business context, but they should not be confused with evidence of performance in an individual industrial installation.
For technical decision-makers, a disciplined evaluation should keep the levels of evidence separate: company-wide results, ecosystem deployment figures, product characteristics and application-specific validation answer different questions. The annual report provides context on the first three, while each project still needs requirements-based engineering and integration planning.
Conclusion: make the system fit the operational need
Semtech’s fiscal 2019 report presented LoRa technology as a low-power wireless platform for LPWAN and IoT applications, with industrial automation and metering among its target uses. Its gateway and end-node figures also demonstrate why network capacity, deployed endpoints and local suitability should be considered separately. Automation teams evaluating LoRa should begin with the application, trace the complete data path and verify the network and integration requirements for their environment. That approach keeps the decision grounded in operational needs rather than broad market claims.