Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Azure Digital Twins

Azure Digital Twins is a platform that provides organizations with the foundation they need to create the next generation of IoT solutions. With Azure Digital Twins, you can virtually replicate the physical world by modeling the relationships between people, places, and devices in a special intelligence graph. You can use predefined data schema that are aligned to a solution’s domain-specific needs and that can accelerate and simplify it’s creation. You can query data in the context of a space rather than from disparate sensors. And you can build solutions that scale and replicate across multiple tenants.

More details are available in the Azure Digital Twins documentation. If you have a technical issue, please open a post on the developer forums through Stack Overflow.

  1. Easier management of schema changes

    We would need a way to mass update the modal changes and reflect to all nodes of the type being updated.

    When I add a simple field to one of the nodes of the modal scheme I need to go through all the nodes of that type and change the metadata.

    Need an easier way to handle modal metadata changes.

    One idea could be to extend the ADT viewer. Another would be an api to update metadata for all nodes of the type being updated.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the feedback! As we gather more feedback and understand more scenarios with regards to model versioning, we certainly want to continue to support updating twin data at scale. Please continue to upvote and provide feedback so that we can keep moving in the right direction!

    In the meantime, check out this article on managing model versioning in our documentation – https://docs.microsoft.com/en-us/azure/digital-twins/how-to-manage-model#model-versioning

  2. Add support for geospatial property arrays, not just telemetry arrays

    To support use cases in relation to spatial digital twins for eg. government, energy, smart cities, utilities etc. the inability to associate a twin to a geospatial definition is a limitation. Sure we can relate a twin to a geospatial definition held elsewhere, but the inclusion of location properties (point, polyline, polygon, arrays etc) would really open up the use case possibilities of standalone ADT

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Azure Digital Twins

Categories

Feedback and Knowledge Base