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.
-
Making a graph viewer available in the Azure portal
To easily get a clear overview of the Digital Twins hierarchy of spaces, it would be great to add a (readonly) graph viewer for Digital Twins. A graph viewer has already been build and published to GitHub. Why not add this option to the Azure portal as the Digital Twins Explorer. (https://github.com/Azure/azure-digital-twins-graph-viewer)
Optionaly the explorer could be used to add, modify of delete spaces, devices or sensors in a non-readonly mode.20 votesThanks for the suggestion! Though this was for the previous version of Azure Digital Twins, this is still relevant with the latest version’s sample – the ADT Explorer. This is a great idea and we’d love to see more feedback on this, but we have not planned this yet
Check out the new ADT Explorer sample – https://github.com/Azure-Samples/digital-twins-explorer
Also, check out the latest version of Azure Digital Twins – https://docs.microsoft.com/en-us/azure/digital-twins/overview-differences
-
Enhance the current space graph model of digital twin to define store to persist historical sensor data to Cosmos or HD Insight..
Current Space graph model of digital twin does not store historical information, such as sensor data. Model should have capability to define the store and attached to Sensor(s) and other model
7 votes -
Add previous state in Digital Twin Property Change Events
In the new public preview, change events can be routed to external compute. In this event, the updated values of Digital Twin properties are included. I think it would be valuable to also include the previous state. This would also be valuable for relationship changes, when an item moves through the graph it can be important to know where it came from.
6 votesThis is a great idea! We’ll update the item once it’s on the near term roadmap.
Keep the votes coming!
Alex
Digital Twins PM Team -
Integrate Elastic/AzureSearch to add full text index and searching functionality
It would be really helpful to be able to search for values within the content of the Digital Twins, e.g. searching in the names, properties, keys and attachments of the nodes within the Azure Twin tree.
4 votesThanks for the feedback! Since your post, we’ve released a new version of Azure Digital Twins that involves a new query language. Read more about it here: https://docs.microsoft.com/en-us/azure/digital-twins/concepts-query-language
Thanks,
-Riley -
Support for building the Azure Digital Twin special model from the existing automation systems.
Support for building the Azure Digital Twin special model from the existing automation systems which are based on Industry standard like ISA95, ISA106, AutomationML
3 votesThanks for the feedback! We’re working towards collaborating with industry professionals to build out industry-specific ontologies for customers to use. We’re certainly investigating the manufacturing space, please continue to give us feedback as we learn how we can support this area.
Thanks,
-Riley -
Chunked Blob Upload & Custom Storage Container
Would be nice to be able to upload blobs using chunked API that Azure Blob Storage already uses. Also, would be nice to be able to associate a Storage Container with Space, so that all the blobs in that Space hierarchy would be stored there. Thanks!
2 votesHi Simon, thanks for submitting the suggestion! To clarify, what is the content/data you looking to upload to ADT in a chunked fashion?
Taylor
Azure Digital Twins Team -
Run timers on the twin and fire events when these expire
Set up the Orleans timers using JSON configuration and use the digital twin to trigger delayed events after some telemetry occurs.
Examples:
1) Assume a noisy device that aggregates its state to the parent, but only after stabilizes.
2) The twin reports an alarm to the building manager and waits before reporting to the supervisor, giving some time to investigate or clear the problem.
3) For process enforcement, important to know when things don't happen on time.1 voteThis is a great idea! We’ll update this request if progress is made on this work item.
Keep the votes coming!
Alex
PM: Digital Twins Team -
Support for message enrichments on Twin.Update event notifications
A way to enrich the messages generated and sent to endpoints.
One example is enrich at least with modal parent dtId of the entity being updated.
1 voteThis is a great idea! We’ll update this request once the work is in progress.
Keep the votes coming!
Alex
PM: Digital Twins Team -
Not possible to see the details of endpoints already created
Please include a way to see details of the endpoints created. Which eventhub for example an endpoint is pointing out to is not possible to find out as of now.
1 voteThis is a great ideal! We’ll update the request status once this work is underway.
Keep the votes coming!
Alex
PM: Digital Twins Team -
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 voteThanks 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
- Don't see your idea?