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.

Today I would like to talk about the concept of a digital twin. I will explain this term using few examples - from digital twin of a simple sensor to complete factory. I will cover what is needed to provide business value from a digital twin and how to extend this concept. Video Sensor A simple sensor can be described by its: metadata - for example: serial number vendor range of measured values readings (data it gathers from the environment).