I posted some technical content but never mentioned if it is worth it to be a professional IoT Consultant. As an IoT Consultant, you have many responsibilities: help to define the Business Use Case help to predict the potential Business Value provided by some new prototype assist in Solution Architecture design ensure that the designed system is secure at every layer: device, connectivity, cloud backend … You need to have strong technical background:

Video Introduction Today I will present a simple serverless IoT architecture. Serverless is a popular designing concept for cloud applications. It is not always obvious that it can be used in IoT systems. I will show a sample design of a system with three Thermometers and Fan (illustrating an air conditioning device). Overview Those connected devices have very limited capabilities: Thermometers are able to send readings to the cloud Fan is able to receive commands (on/off) from the cloud MQTT Topics Before we start actual implementation, we need to define MQTT Topics used in our system.

Video Introduction Today I would like to talk about the role of an IoT Consultant and the Cost Factors of the IoT solutions. In my opinion, the IoT Consultant should engage in defining the Business Use Case, not only the Technical Solution for the Business Use Case. The role of an IoT Consultant is to be the Trusted Advisor for the Business/Product/Service Owner. Today I will cover the cost factor perspective.

Video Introduction Hello, it’s LMtx. Today I would like to talk about the PoC design checklist. The PoC (Proof of Concept) is used to verify assumptions regarding the business value provided by a new solution. We should focus on the business value, not the technical details of the future initiative. It is very common that people dive deep into technical feasibility and forget about the required business outcome. Let’s say that we avoided that trap and clearly defined the business goals.

Introduction Today I will show how to connect the IoT Device (represented as an IoT Thing) to the AWS IoT Core. As a starting point, I will use the IoT Thing that we configured in my previous post. Let’s review our current setup: On-Premise and Cloud I will use the mosquitto client to test the connectivity between IoT Device and the AWS IoT Core. Preparation We need to copy credentials to our IoT Device:

Today I will build on top of my previous post - the concept of a digital twin. I will explain how to: represent a physical device (like a temperature sensor) in AWS IoT Thing Registry manage the metadata of IoT Devices in a consistent and scalable way organize IoT Devices in Logical Groups (for instance to efficiently manage all IoT Devices attached to the same piece of factory equipment) create the x509 Certificate and attach it to the IoT Thing as a proof of an identity After reading this post, you will understand the core concepts of the AWS IoT Thing Registry.