Here is the latest edition of the IoT Central Digest. Encourage your friends and colleagues to be a part of our community. Forward this to them. They can join IoT Central here. You can contribute your thoughts on IoT here.
Posted by Scott Allen
The phrase, “the future is here,” is overused and has evolved into a catchphrase for companies struggling to position themselves in times of technological or digital transformations. Still, the sentiment is understood, especially in times like today, where the Internet of Things is quite literally changing the way we think about hardware and software. We’d like to offer an addendum to the phrase: “The future is here more quickly than we thought it would be.” With that in mind, we wanted to provide some advice for companies across the industrial sector for the best ways to optimize operations for the Industrial IoT.
Posted by Vivart Kapoor
We all know HTTP (hypertext transfer protocol). These are the first 4 alphabets which see on any URL of a website you open in your browser. In simple terms, it is a list of rules that define do’s and don’ts of communication between web browser and web server. It is like you (web browser) going to ATM (webserver) to get some cash (request). Here the HTTP will describe the complete procedure – enter pin, amount, etc. You get your cash (result) once you follow the mentioned steps. Quite simple.
The World Wide Web (WWW) works on HTTP as it is the only protocol used there for the data transfer. However, this is not the case in the Industrial (I) IoT world. Here we have a bunch of protocols to choose depending on the type of application or so-called “use case”. The most common among them are MQTT, CoAP and of course HTTP. Before we discuss them, let us first have a look at certain networking terminologies and definitions.
Guest Post by Daniel Elizalde
Every new technology trend brings speculation and talk about a “killer app” that will be the solution to all of our problems. Tech publications and blogs produce countless articles searching for the “killer app” for the iPhone, the Cloud, Blockchain, Artificial Intelligence, and of course, IoT. We’ve also even seen the same hype for development processes. I can’t tell you how many times I’ve heard that Agile is that silver bullet. Or maybe it was Lean, or Kanban? Hard to keep track. But as a Product Manager, we can’t keep chasing the next big thing all the time. It’s true we need to understand where technology is going, but we need to be more pragmatic and realize there is no single “killer app” for anything. Particularly for IoT.
Posted by Mohit Bhardwaj
Connecting smart buildings to smart grid, smart transportation, & other smart services is the need of the hour to truly manifest the potential of IoT. However, communicating with numerous systems made up of different protocols is a major challenge faced by integrators. Protocol converters are widely used to convert protocol A to B, but such devices do not offer ease of configuration and flexibility demanded by IoT. The solution to this is a universal gateway – a device that transacts data between two or more data sources using communication protocols specific to each of them. The Universal gateway is also termed as a universal protocol gateway. Such products include a combination of hardware & software, and used to connect data from one automation system like building automation to another like a smart grid.
Photo Credit: Markus Spiske