Tag: device

Posted on

IoT Smoke Detector

For most people, the home smoke detector is the first Internet of Things #IoT sensor/device they’ve ever come in contact with.

It may or may not CONNECT to a remote monitoring service over the Internet.

It COLLECTS air.

It ANALYZES the air looking for smoke using either an ionization chamber or photo-detector.

It ACTS on the insights derived from this analysis and sounds an alarm if smoke is detected. The battery on this device typically lasts a year before the annoying beeping sound begins.

Amazingly, this self-contained IoT device and analytics platform doesn’t require mythical AI powers to deliver value to the customer.

Don’t overthink it.

Posted on

Digital Twin Models and Virtual Properties

Twin Towser

Another interesting aspect of a #DigitalTwin Model is the use of virtual, or calculated properties to derive additional #IoT value. #IIoT

While “virtual properties” don’t have a 1:1 relationship with the “telemetry properties” (sensors) I described in my previous post, that are actually sending data from a device, they’re super-valuable. The value assigned to a virtual property is typically derived from a mathematical combination of values from one or more telemetry properties and possibly other reference data. For instance, calculating miles per hour (speed) of a car is a good example of a virtual property where a combination of telemetry properties like the rotating drive shaft and magnetic sensors use simple analytics to tell you how fast you’re going.

While not always necessary, virtual properties deliver additional value and insights.