Factors and approaches to be considered while designing IoT Gateways

Author: Dhaval Parikh || Director Products & Solutions at VOLANSYS

264

Leveraging production-ready IoT gateway platforms and customizing them to achieve faster time to market and reduced cost for desired configurations and wireless connectivity options

As the trend for IoT is growing with the rising number of connected devices, the demand for IoT gateways has also increased significantly and will continue to grow exponentially. The global IoT gateway market is set to grow at a rate of 30.9% between 2017 and 2023 (as per a research report ‘IoT Node and Gateway Market by Hardware, by End-Use, and Geography-Global Forecast to 2023’ by Markets and Markets). The need for IoT gateways is realized because isolated systems are rapidly transforming to the ubiquitous internet-enabled system (also referred to as ‘connected devices’) that can be used to capture and communicate valuable information by leveraging diverse wireless connectivity technologies to IoT gateways for unified edge-analytics. In other words, IoT gateways play a vital role in by providing the fundamental building blocks to develop secure and powerful wireless connectivity between IoT devices and IoT cloud based applications.

OEMs look forward to offering a gateway/hub to connect their existing wireless devices portfolio considering mainly three major aspects – first, the cost, second is overall efficiency and effectiveness of the system and third, the flexibility that it provides to design customized IoT solutions that evolve over time. While designing IoT gateways, most OEMs would think either of these four approaches:

  1. Design from scratch – Building gateway from scratch based on IoT use case specific requirements with desired form factor, wireless connectivity, and other configurations. While it has its own unique advantages, this approach increases cost and time to market to a great extent.
  2. Open platform based solutions – Leverage open platform-based solutions such as raspberry pi, Arduino, and beaglebone and implement the customized gateway product without extensive programming. This approach is suitable for small IoT applications but not sustainable for a large-scale IoT application.
  3. Fixed configuration-based OEM solution – Purchase a production-ready gateway platform from some well-known vendors and build an IoT application. Most of such vendors have fixed configuration and form factor design. They do not provide the flexibility to customize the architecture for specific needs.
  4. Modular/configurable OEM Gateway solution – Some vendors such as Phytec, VOLANSYS, Digi, etc. provides a production-ready IoT Gateway starter kit platform to build an IoT solution which can be quickly customized with a modular architecture implementation. This white- labelled gateway solution is suitable for both small and large scale IoT applications as it provides flexible architecture and faster time to market.

The first three approaches have multiple demerits which may affect your business in cost-effectiveness or time-efficiency. However, the fourth one is a middle-ground approach which is flexible and the most feasible option to prototype custom configurations-based gateways, allowing early field-trials and can support mass production at reduced time, cost and risk.

Let’s have a look at a detailed comparison of all approaches against the key factors to be considered across an IoT gateway product development lifecycle from prototype to production.

Key factors to consider for Gateway Prototype Design

While designing gateway prototype platforms, there are several areas like form factor design, hardware platform, wireless connectivity, pre-compliance to be considered whether you are building from scratch or leveraging available platforms.

Form Factor Design: IoT gateways combining all functions such as networking, control and data, security, remote operation and centralized management, are generally forced to compromise on size and form factor over fan-less and vent-less designs.

Hardware Platform: For most platforms, the silicon boards, pinouts, and connectors are not friendly enough for using the platform to test the market. Also, traditional prototype design is not compatible with a diverse range of peripherals that restrict the use of gateways in multiple applications.

Wireless Connectivity: Most of the prototype ready gateways available in the market offer limited options for wired and wireless connectivity using standards such as Zigbee, Wi-Fi, LTE, Thread, Z-Wave, Sub-GHz RF, where some of these may not be available as an option.  Also, providing more options for both southbound and northbound connectivity increases the time to market. Solutions that allow product developers to choose from the northbound interface (Wi-Fi, LTE, Ethernet) and southbound interface (Zigbee, Z-wave, LoRaWAN, Sub-GHz) are very rare in the market.

Pre-Compliance: The most critical phase is to get the gateway certified before it is made available in the market, because of the time-consuming certification processes. So, pre-compliance considerations need to be addressed well in time. In today’s fast-paced market, certification ready platforms reduce almost three months in the PDLC prior to product launch. The total time for such products to hit the market increases significantly if the platform is not pre-certified. There are very few gateways presently available in the market, which provide FCC/CE/IC pre-certification along with multiple connectivity options like Zigbee®, Thread, Wi-Fi/3G, and Bluetooth.

Key factors to consider for High Volume Gateway Production

OEMs face multiple challenges while preparing their gateway prototype design for high-volume production. To avoid these challenges, some OEMs might consider selecting a production-ready platform for their gateway requirement. Few factors that OEMs need to consider for high-volume gateway production is explained below.

NRE Charges –  If the gateway prototype platform does not meet the defined product requirements of OEMs before they ship the first unit after production, high NRE charges may reduce company profits due to lack of pre-planning around tooling enclosures, certifications and MOQ of purchases. The total production cost increases mainly because of custom-made products, and divert engineering and production resources from standard, consistent product lines, over to one-off designs with little opportunity to recoup design costs through large-scale production. With reduced NRE charges, OEMs can better spend their investment on promotions and brand development for their solution.

High Volume Supply: For a fast-moving market, 10K is a small volume to be supplied per year. It restricts some players who try to innovate the end-application as the addition of R&D time, prototype development time, production time and time to test the market for an application, increase the total time to launch in the market.

Support for Chip Down or Product Enhancements: A thoughtful product prototype design should be accomplished with a well-architected gateway that is production-ready, and fulfills all critical product requirements. After initial customer trials when production reaches certain volumes, the product should be converted to chip down versions to support large volumes.

Summary:

As explained, during the IoT gateway product development roadmap from prototype to production, OEMs must compromise one or the other factors if a modular approach is not chosen. As designing and creating IoT devices is never easy, Modular IoT Gateway adds real value to your IoT applications. Gateways should be a central consideration when planning any IoT architecture. Selecting the right gateway should often be the starting point, as the gateways play a significant role in all facets of IoT – from connectivity management to monitoring, and data processing to cloud integration.

For more information visit VOLANSYS   or write to business@volansys.com

LEAVE A REPLY