Digital twins can represent anything in the physical world across the past, present and future, but they’re consumed today from dashboards and charts. Business-critical insights are distilled down to...
Updated May 24, 2022
Version 4.0
Blog Post
Since the initial preview, there have a been a few welcome updates, including the integration with Data History.
However, there is one thing that currently frustrates the scene management process.
Imagine you are not setting up a scene for the first time, but extending/amending the scene in line with changes to either your physical environment, or because you are adding new use cases to an existing Digital Twin solution. I have found there are several places within the tools where the current state of the underlying ADT environment is somehow cached by the 3D Scenes Build tools. One example is, when you add a new property to a twin, and want to change a 3D Scenes Behaviour to use that new property value. It does not appear on the available properties unless you delete the Behaviour and start again. Another example is when you have a scene based on an ADT instance without ADX Data History capture enabled, then later enable Data History. This does not enable the creation of a Data History Widget within an existing Behaviour, only a new Behaviour.
The provision of contextual 'refresh' button on each Build Tool which pulls twins/configuration data from the underlying ADT instance would solve both these issues.