Digital Twin Models and Rules

Twin Buildings

As part of my series on Digital Twins, I’ve discussed the creation of a Digital Twin Model which defines a type, or class of physical entity from which instances of digital twins are derived.

Once you’ve added telemetry, virtual, static, or command properties, it’s time to make use of this #metadata with rules.

The first steps in deriving value from streaming telemetry data revolves around pattern matching, key performance indicators (KPIs), & filtering. You therefore need to specify one or more rules to be associated with each “telemetry property” you’ve defined in your digital twin model. This is accomplished through the use of simple operators such as equals, not equals, greater than, greater than or equal to, less than, & less than or equal to.

Let’s say you’ve defined a “telemetry property” for the “left front tire pressure” of a car digital twin model with an “integer” data type and “PSI” unit of measure. To create a “green” KPI between 30 & 35 PSI, you would define a rule looking for values that are >= 30 & <= 35. Using simple IFTTT algorithms, the event processing engine of your Edge or Core IoT platform would apply those rules to incoming data & trigger an action for values outside that range.

Discover more from Rob Tiffany

Subscribe now to keep reading and get access to the full archive.

Continue reading