If you enjoyed this video you will also find my free newsletter valuable. Join 2500+ subscribers to get weekly actionable tips on the architecture and development of IIoT solutions. → SUBSCRIBE HERE: www.industry40.tv
Export the MatLab, Azure, Chat GPT, Revit, Plant 3D, Civil 3D, Inventor, ENGI file of the Building or Refinery to Excel, prepare Budget 1 and export it to COBRA. Prepare Budget 2 and export it to Microsoft Project. Solve the problems of Overallocated Re-sources, Planning Problems, prepare the Budget 3 with which the construction of the Building or the Refinery is going to be quoted.
I continue to "accidently" stumble upon your videos recently. It means there is something you are doing right ;) Fun aside, nice description of the format. I am working on parts where our company group is on many parts independently working on aspects to realize some forms of digital twins. There is no common understanding what a digital twin is, and therefor too many different tools, formats and vendors are used. I try to bring this together and make aware of the problem. But I am struggeling myself. There is AML, CAEX, IDTA's AAS, DTDL, and other "Standards" from specific vendors. Which one for what? Where is the compatibility? Are there limitations to the ecosystem? Which standard is evolved enough to universally realize complex plants? I struggle with AML and as beautiful as DTDL looks on first glance, it might be just to broad and narrow at the same time to serve as a practical solution. What about other tools for Interfacing this standard? Do we have to develop everything from scratch.... (then I can just develop a suited solution myself)?
Thank you for sharing your experiences and concerns. I can understand the challenges you face, especially when there's an abundance of standards with varying levels of maturity and applicability. And I totally agree that while DTDL offers a broad conceptual framework, it might not be the best fit for every application. The ideal scenario would be standards that can seamlessly interface with each other, but we're not quite there yet.
Thanks for the thorough demonstration Kudzai! I was wondering what would be the next step now that you’ve modeled the digital twin. Would the goal be to simulate using the digital twin? Or is this purely just for modeling semantics?
Thank you for watching and for your feedback, John. The next step would be to connect the digital twin to a real-time data source from the physical entity through IoT Hub or SDKs in the case of Azure Digital Twins. And then also connect the digital twins to real-time dashboards or platforms like Azure Data Explorer or data lakes for analytics.
Thank you for your comment. DTDL is especially useful when you want to model a complete manufacturing line or a whole factory. On the other hand, AAS is helpful for the lifecycle management of assets as it keeps track of data from design and manufacture to operation and decommissioning.
![Data Modelling and Manufacturing Ontologies for Digital Twins - Ep 37 [ Erich Barnstedt, Microsoft ]](/img/1.gif)
If you enjoyed this video you will also find my free newsletter valuable. Join 2500+ subscribers to get weekly actionable tips on the architecture and development of IIoT solutions.
→ SUBSCRIBE HERE: www.industry40.tv
Export the MatLab, Azure, Chat GPT, Revit, Plant 3D, Civil 3D, Inventor, ENGI file of the Building or Refinery to Excel, prepare Budget 1 and export it to COBRA. Prepare Budget 2 and export it to Microsoft Project. Solve the problems of Overallocated Re-sources, Planning Problems, prepare the Budget 3 with which the construction of the Building or the Refinery is going to be quoted.
I continue to "accidently" stumble upon your videos recently. It means there is something you are doing right ;)
Fun aside, nice description of the format.
I am working on parts where our company group is on many parts independently working on aspects to realize some forms of digital twins.
There is no common understanding what a digital twin is, and therefor too many different tools, formats and vendors are used.
I try to bring this together and make aware of the problem. But I am struggeling myself. There is AML, CAEX, IDTA's AAS, DTDL, and other "Standards" from specific vendors. Which one for what? Where is the compatibility? Are there limitations to the ecosystem? Which standard is evolved enough to universally realize complex plants? I struggle with AML and as beautiful as DTDL looks on first glance, it might be just to broad and narrow at the same time to serve as a practical solution. What about other tools for Interfacing this standard? Do we have to develop everything from scratch.... (then I can just develop a suited solution myself)?
Thank you for sharing your experiences and concerns. I can understand the challenges you face, especially when there's an abundance of standards with varying levels of maturity and applicability. And I totally agree that while DTDL offers a broad conceptual framework, it might not be the best fit for every application. The ideal scenario would be standards that can seamlessly interface with each other, but we're not quite there yet.
Thanks for the thorough demonstration Kudzai!
I was wondering what would be the next step now that you’ve modeled the digital twin. Would the goal be to simulate using the digital twin? Or is this purely just for modeling semantics?
Thank you for watching and for your feedback, John. The next step would be to connect the digital twin to a real-time data source from the physical entity through IoT Hub or SDKs in the case of Azure Digital Twins. And then also connect the digital twins to real-time dashboards or platforms like Azure Data Explorer or data lakes for analytics.
Great content. Congrats. Is there a direct connection between the DTDL and the Asset Administration Shell Model (AAS) for Industry 4.0? Tks
Thank you for your comment.
DTDL is especially useful when you want to model a complete manufacturing line or a whole factory. On the other hand, AAS is helpful for the lifecycle management of assets as it keeps track of data from design and manufacture to operation and decommissioning.