At the ZEDEDA Transform 2020 event, I was joined by Richard Soley from OMG, Edward Wood from Dispersive Networks, Inc., and Mike Pantaleano from Rockwell Automation where we discussed key #DigitalTwin considerations and use cases ranging from #IIoT to #AR to #VR.
With #COVID19 sweeping the globe, knowledge is our best weapon in fighting this pandemic and associated economic collapse. #DigitalTwin technology is perfectly suited to represent people who have symptoms, are infected, or have recovered.
A process is a series of actions, tasks or steps taken in a linear or sometimes a branching, non-linear sequence in order to achieve a desired outcome.
It’s easy to think of #DigitalTwins as representing discrete systems & subsystems, like an industrial #robot that builds a car in a factory. The reality is that physical entities like humans, machines & environmental systems don’t live in a vacuum.
If you’ve ever worked with an #IoT platform, you might have noticed it typically has you define a simple schema or #DigitalTwin Model for an entire person, machine or environmental system.
To create an historical record of what happens to an instance of a #DigitalTwin throughout its entire lifecycle, you represent this with something called a #DigitalThread.
It’s time to create a #DigitalTwin Instance of a physical entity that is derived from a Digital Twin Model.
As part of my series on #DigitalTwins, 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.
In the event your #IoT platform needs to work with industrial control systems where it’s necessary to send messages to trigger actuators, you’ll define one or more “command properties” in your #DigitalTwin model.
The static properties enumerated by a #DigitalTwin model represents #IoT #data that typically doesn’t change.
Another interesting aspect of a #DigitalTwin Model is the use of virtual, or calculated properties to derive additional #IoT value.
Your #DigitalTwin Model and its telemetry properties are an essential part of the #IoT #data flow from device to #analytics.