Digital twin platforms should provide an open Application Programming Interface (API) that allows any system to interact with the master Digital Twin.
Sensative’s view on this. You shouldn’t settle for a multi-twin-multi-domain-multi-supplier situation, that is just making the old school siloed systems even worse. A supplier that provides the whole end-to-end solution for a specific problem (sensor – data – storage – analytics – Twin) should actually not even be considered as a supplier if it isn’t built for data sharing from the bottom up.
“Multiple digital twins acting in unison will be complex and inevitably too complex for straightforward integration. Multiple digital twins need the tools to bring all their information together to create a “digital master” and then manage any changes to that digital master for all systems and user processes. “. This means integration on top of all twins. Why shouldn’t the “master twin” be the complete twin, making the rest of the half-baked twins obsolete?
Integration should be done very much closer to the data source so that you have ONE unified data stream to your master digital twin, disregarding IoT or legacy tech, standards, or other data sources. This is what horizontal real-time integration is all about. This is what Yggio is all about.
Integrating Digital Twins should mean that they share data sources, not that you need to create a master super twin (a twin of twins). Think about redundant data, or latency issues when twins are used for control, not only documentation.
