Connecting Your Product to the IoT: What You Need to Know and How to Get Started. A Reference Guide for Product Managers, Designers and Engineers

Transcription

1 White Paper Connecting Your Product to the IoT: What You Need to Know and How to Get Started A Reference Guide for Product Managers, Designers and Engineers

2 INTRODUCTION The Internet of Things presents a world of opportunity for organizations in every industry. The Internet of Things (IoT) presents a world of opportunity for organizations in every industry. Products that were traditionally sent out to the field, never to be heard from again, can now come to life, communicating their status, usage patterns and errors, among other things, to the customers who are using them. Organizations can use these data streams to improve product quality, modify existing products, design new products, enhance customer experience and more. But before you can begin using IoT data to your advantage, you must either design an IoT-connected product from the ground up or transform your product into a connected IoT device. The purpose of this white paper is to explain, in a practical manner, the steps required to connect a device to the IoT. GETTING STARTED At the most basic level, a connected product must be enabled to talk. This means sending and/or receiving instructions, updates, data, etc, over the Internet via Ethernet, Wi-Fi, or a cellular connection or bridging to the web through a mobile phone or gateway. The process of connecting a product and selecting the communication method requires decisions determined by the product itself, the purpose for connecting the product, the environment where the product will exist, and user preferences. CONNECTING YOUR PRODUCT TO THE IOT 2

3 Building the Product: Hardware Selection & Design INDUSTRIAL DESIGN In order to connect a device to the Internet, it will need the appropriate technologies, such as sensors, a board and a microprocessor. But before that, there s the practical consideration of the product s form factor and space limitations. Regardless of the type of product you re connecting, you will face limitations on how much you can change the size of the device and, therefore, what type of hardware you can add. For example, a pool pump manufacturer has more liberty with the size of the product than one that makes smoke detectors. Similarly, consider the environment where the product will operate. Will it be subject to the elements and therefore require a weather protection or a waterproof enclosure? Or will it be used in an environment where direct impact is a possibility, meaning the enclosure must be ruggedized? For example, sensors on a smart tractor that measure fertilizer saturation will be exposed to the elements, dirt and fertilizer, among other things, meaning they require more protection than a thermostat. CONNECTING YOUR PRODUCT TO THE IOT 3

4 Internet Connectivity Method In addition to including the hardware necessary for communication, you also need to determine how the product will connect to the Internet to send and receive communications. There are two main approaches direct to Internet or via gateway and a few options within each. DIRECT TO INTERNET When connecting a product or device directly to the Internet, the primary considerations are the conditions in which the device will run, user preference and cost. In the case of a device that operates in a home or small-business setting, connecting to the Internet via a local area network (LAN) may make the most sense. Next, determine whether the device will use Ethernet or Wi-Fi to access the LAN. Many homes now have Wi-Fi, but Wi-Fi is a more expensive option than hard-wired Ethernet. On the other hand, connecting wirelessly eliminates unsightly wires that may require more space and allows for mobility. Example: Connecting a wearable device via an Ethernet cable isn t really a viable option. Alternatively, the device can use a wide area network (WAN), such as cellular 3G/4G, to connect to the Internet. This option is more expensive, but may make sense for a closed corporate network or remote location. GATEWAY When connecting a product to the Internet via a gateway, the gateway communicates with the Internet on the device s behalf. In certain applications, the gateway itself sits on-premises (for example, in the consumer s home) and connects to the local area network (LAN) through Wi-Fi or Ethernet. (In fact, a gateway is ideal for connecting legacy Ethernet-connected products.) A chip in the connecting device allows it to wirelessly connect to and communicate with the gateway. This method of communication is commonly found in low-power scenarios. In other cases, a smartphone can serve as the gateway, communicating with the Internet on the device s behalf. One of two technologies Bluetooth Low Energy (BTLE) or Near Field Communication (NFC) allows the device to communicate with the smartphone. However, this use case requires that a smartphone is available and connected to the device. Gateways provide several benefits in addition to connecting products to the Internet. They make it easy to connect multiple devices that are in one area, such as an array of lights. A gateway also enables manufacturers to change functionality and rules without rolling out a firmware update. Finally, they can make an IoT project more cost-effective. CONNECTING YOUR PRODUCT TO THE IOT 4

5 INTERNET CONNECTIVITY METHOD In addition to today s commercially available standards, a new protocol named Thread is emerging in the smart home space, with the backing of Google and other large tech companies, including Xively. GATEWAY PROTOCOL OPTIONS There are a few standard protocols that allow low-powered radios in your device to connect to a gateway. The most common of these are ZigBee and Z-Wave two open standards that require licensing fees. Some companies, however, forgo standards and write their own proprietary protocols to meet custom needs, or to avoid fees. In addition to today s commercially available standards, a new protocol named Thread is emerging in the smart home space, with the backing of Google and other large tech companies, including Xively. ZigBee s software stack is larger and more complex than Thread s. This can present several disadvantages, such as latency issues and the need to draw more power, which requires more memory and a larger microprocessor. This, in turn, increases costs. That said, ZigBee is well established and used commercially, while Thread is still emerging and evolving. At the same time, Thread has support from Google and other large tech companies, meaning it may become the front-runner in the market for smart home solutions. CONNECTING YOUR PRODUCT TO THE IOT 5

6 Microprocessor Selection & Firmware Development Once you ve determined how your product will connect to the Internet, your next consideration is the microprocessor chip that is, the actual brain of your connected device. Many products already contain a microprocessor for managing the device s local operations. For example, a pool pump likely contains some simple electronics to turn it on and off, or to increase and decrease its speed. Other products, such as a valve, have no electronics at all. In order to control the product over the Internet, however, it is necessary to add intelligence in the form of a microprocessor. There are several important considerations when selecting a microprocessor, including price point and what connectivity method you have selected. In addition to the choice of physical hardware, you must also select and develop the software stack to run on that hardware, known as the device s firmware. This instructive code must be written by an in-house developer or by a partner who helps select a chip and writes the code for that processor. In general, the more higher-powered the device is, the easier it is to develop the firmware. Your device s firmware must play two roles: controlling the device itself (reading sensors and sending commands) and talking to the cloud. In many cases, the cloud communication will be facilitated by an agent that a cloud partner provides. PROCESSOR CONNECTING YOUR PRODUCT TO THE IOT 6

7 MICROPROCESSOR SELECTION & FIRMWARE DEVELOPMENT 1. Power flexibility Do you need a battery or hardwired power? Hardware Considerations Connectivity Can your device be hardwired or does it need to connect via cellular, Bluetooth, or Wi-Fi? Onboard sensors Does your existing device already have sensors or will you need to add new ones? There are several factors to consider when selecting connectivity hardware. These questions will help you make an informed decision based on the specific design needs of your product Size Is your product small, like a smoke detector, or do you have plenty of space to work with, like a Zamboni? Durability Will your device be in a climate-controlled space? Or will it be exposed to rough conditions like weather or dust? 6. Ease of integration Does integration require hands-on, embedded engineering, or can it be more plug-and-play? 7. Customization How easy is it to extend the IoT capabilities of your device? 8. Processing power How much data does your device need to process? CONNECTING YOUR PRODUCT TO THE IOT 7

8 MICROPROCESSOR SELECTION & FIRMWARE DEVELOPMENT With these considerations in mind, we ve compared four of the most common connectivity hardware options. Gateway Bolt-On Bluetooth Assembled BEST FOR Network of edge devices Larger form factor devices Harsh environments BEST FOR Commercial fleet management Continuous feedback on environmental factors Rapid proof-of-concepts BEST FOR Devices used in conjunction with a smartphone Wearables and apparel Location-based services BEST FOR Use-case flexibility Products with physical size and power usage constraints High-volume production PROS Variety of connectivity options Simple to add to harsh environments Ability to aggregate discrete device and sensor data PROS Easy to install Includes pre-bundled sensors Simple to add to harsh environments PROS Small form factor (size of a postage stamp) Portable Easiest to set up connectivity PROS Highest level of security protection Plug-and-play expansion cards for rapid prototyping Small form factor Lowest power consumption CONS No built-in sensors included Requires continuous power supply Larger form factor CONS No customization in sensors No flexibility in form factor Limited choices in connectivity options CONS Connectivity only through another device Limited to the security and data capabilities of Bluetooth CONS Integration requires engineering work Product-specific hardware boards require design and manufacturing SEE A CUSTOMER USE CASE Freight Farms LEARN MORE ABOUT THIS HARDWARE OPTION Bosch XDK LEARN MORE FROM A XIVELY PARTNER Silicon Labs SEE A CUSTOMER USE CASE Halo s Connected Smoke Detector CONNECTING YOUR PRODUCT TO THE IOT 8

9 Connecting to the Cloud Once an intelligent device begins talking, it s critical to secure the information from corruption or hacking. There are two primary considerations regarding securing and collecting data generated by a connected device. The first is how you ll control access, while the second is which messaging protocol makes the most sense for you. CONTROLLING ACCESS TO DATA When it comes to controlling access to data, there are two key considerations: device authentication and device authorization. Device authentication provides a unique set of credentials for every device. Credentials can be assigned when the product is designed and manufactured, or when it connects to its home for the first time. Device authentication ensures that the device is who/what it claims to be, much like your online banking app requires proof of who you are before providing access to your accounts. Device authorization means managing who can do what types of activities with the device, such as viewing data and remotely controlling or updating it. To enable this protection, you must either manually set up a system to establish permissions or use an IoT platform that includes user authorization as a feature. Device authorization ensures that users cannot access data or functionality that could otherwise create a security risk; this is similar to a corporate setting where only certain employees have permission to access financial information, for example. Once data arrives at the cloud-based IoT system, its storage and security are determined in large part by the IoT solution and/or the cloud provider. CHOOSING A MESSAGING PROTOCOL When communicating with the cloud (whether directly or via a gateway), devices can use one of a number of messaging protocols. The two leading choices are a publish-and-subscribe model or a call-andresponse model. The most common publish-and-subscribe style protocol is MQTT, a leading machineto-machine or IoT connectivity protocol. In this paradigm, devices and users subscribe to information channels they are acting on, and messages published to those channels are delivered in real time. This means the device is actively listening and waiting for a message to come in. Call-and-response, on the other hand, is typified by the HTTP protocol that is also used by web browsers to load web pages. Instead of actively listening, the device and its users call in to periodically ask for updates. This means all actors in the system proactively query for information in order to receive messages in real time, thus increasing traffic. MQTT is more commonly used in IoT applications because it can simultaneously deliver information to many actors, and because it is far more lightweight and less resource intensive than HTTP. At a high level, open messaging protocols like MQTT and HTTP are more popular than proprietary protocols because they provide the flexibility to plug into additional ecosystems. Typically, the more integration you enable with your product, the more likely it is that consumers will buy it, the more flexible it becomes for future functionality, and so on. CONNECTING YOUR PRODUCT TO THE IOT 9

10 Selecting an Expert Partner The process of connecting a device to the Internet can be complex. Rather than becoming an expert on the various protocols and technologies involved, you can partner with a solution provider like Xively. The choice of third-party partners includes a variety of approaches, with some requiring more work on the part of the product manufacturer and others less. Some providers, for example, offer prepackaged solutions that include everything required for connecting a device to the Internet. About 80% of the time, companies can use one of these prepackaged solutions with elements that fit all their needs, as opposed to building something more customized. A kit or prepackaged solution enables companies to save time and resources, and fast-track their way to the IoT. On the rare occasion that a product can t be addressed with a prepackaged solution, a third-party partner can also help you build a custom solution. CONNECTING YOUR PRODUCT TO THE IOT 10

11 Managing a Fleet of Devices Once your product is connected to the IoT, you need a way to manage it. Device management capabilities will vary depending on the solution you choose. Some offer basic capabilities, while more robust solutions provide more flexibility and control over your devices in the field. Here are some capabilities and features to look for when considering a device management solution. VISIBILITY INTO THE ENTIRE FLEET OF DEPLOYED DEVICES DIAGNOSTIC TOOLS ABILITY TO PUSH FIRMWARE UPGRADES TO DEVICES ABILITY TO EXTRACT DATA IN RAW FORMAT ABILITY TO INTEGRATE WITH OTHER ECOSYSTEMS ABILITY TO EASILY INTEGRATE WITH OTHER TOOLS, SUCH AS CRM OR ANALYTICS You ve connected your product to the Internet and implemented a solution to effectively manage it. Now it s time to consider how to use the data generated by your connected product to improve business. This involves considering your users, what applications they use and how you can use the device data. It s also important to consider where you are importing device data such as in your CRM or ERP system and how it can be leveraged. Similarly, consider the different permissions, views and applications you can provide to commercial and consumer users to improve their experience with your product. Given these considerations, your IoT implementation must continuously evolve and improve which brings you to a critical point: You re not done just because you ve connected a product to the Internet. Your finished state is when you see the data it delivers impacting your business. CONNECTING YOUR PRODUCT TO THE IOT 11

12 h CONCLUSION And here s the good news. The Xively Connected Product Management (CPM) platform makes it easy for companies to not only model and connect a product to the IoT, but also to use connected product data to improve business. Xively helps companies structure data and make it actionable, enabling them to define new features, proactively manage users and integrate data with existing business systems. With Xively CPM, companies have robust device management capabilities, including provisioning, configuration, monitoring, administration, firmware and software updates and connected product fleet management and dashboards all delivered via a single solution. Xively CPM also provides device and end-user identity management capabilities to secure devices and their data. Remote support allows devices to autonomously communicate issues to manufacturers while providing critical context that can be used for automated or manual troubleshooting, regardless of location. And Xively CPM s APIs seamlessly integrate connected product data with the rest of the business. Learn more about Xively Connected Product Management. IT S EASY TO GET STARTED WITH XIVELY. No matter the stage of your IoT effort, Xively can help you build, launch and manage your connected products and services. Xively (formerly known as Cosm and Pachube) is a division of LogMeIn Inc. (LOGM), a global, public company that is a leading provider of essential remote services. Organizations worldwide rely on LogMeIn s access and collaboration products, suite of SaaS customer care and remote IT management. Xively is built on LogMeIn s cloud platform, Gravity, which handles over 255 million devices, users and customers across seven data centers worldwide. GET IN TOUCH Xively by LogMeIn offers an award-winning IoT platform, along with secure connected device solutions for companies building smart products and Internet of Things services. T F xivelyinfo@logmein.com

13 Guide Connectivity Considerations CONNECTING A PRODUCT IS COMPLICATED. Here s a breakdown of the most common connectivity hardware to help you select the right one for your product. Still not sure? Contact a Xively expert about your specific needs. GOOD BETTER BEST GATEWAY Example: Option Wireless CloudGate BOLT-ON Example: Bosch XDK All-in-One Platform PHONE BLUETOOTH Example: Silicon Labs Thunderboard React Kit ASSEMBLED Example: TI Launchpad plus BoosterPack Plug-ins Power Flexibility Connectivity Options Onboard Sensors Size Durability Ease of Integration Customization Processing Power CONNECTING YOUR PRODUCT TO THE IOT 13