Skip to content

Commit b50a7cc

Browse files
authored
Merge pull request #201218 from baanders/6-10-overview
ADT: Add 3D Scenes to Overview
2 parents 85a96aa + 88678ea commit b50a7cc

File tree

1 file changed

+32
-27
lines changed

1 file changed

+32
-27
lines changed

articles/digital-twins/overview.md

Lines changed: 32 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
# Mandatory fields.
33
title: What is Azure Digital Twins?
44
titleSuffix: Azure Digital Twins
5-
description: Overview of Azure Digital Twins, what the service comprises, and how it can be used in a wider cloud solution.
5+
description: Overview of the Azure Digital Twins IoT platform, including its features and value.
66
author: baanders
77
ms.author: baanders # Microsoft employees only
8-
ms.date: 03/24/2022
8+
ms.date: 06/17/2022
99
ms.topic: overview
1010
ms.service: digital-twins
1111

@@ -19,51 +19,56 @@ ms.service: digital-twins
1919

2020
*Azure Digital Twins* is a platform as a service (PaaS) offering that enables the creation of twin graphs based on digital models of entire environments, which could be buildings, factories, farms, energy networks, railways, stadiums, and more—even entire cities. These digital models can be used to gain insights that drive better products, optimized operations, reduced costs, and breakthrough customer experiences.
2121

22-
Azure Digital Twins can be used to design a digital twin architecture that represents actual IoT devices in a wider cloud solution, and which connects to IoT Hub device twins to send and receive live data.
22+
Azure Digital Twins can be used to design a digital twin architecture that represents actual IoT devices in a wider cloud solution, and which connects to [IoT Hub](../iot-hub/iot-concepts-and-iot-hub.md) device twins to send and receive live data.
2323

2424
> [!NOTE]
2525
> IoT Hub **device twins** are different from Azure Digital Twins **digital twins**. While *IoT Hub device twins* are maintained by your IoT hub for each IoT device that you connect to it, *digital twins* in Azure Digital Twins can be representations of anything defined by digital models and instantiated within Azure Digital Twins.
2626
2727
Take advantage of your domain expertise on top of Azure Digital Twins to build customized, connected solutions that:
2828
* Model any environment, and bring digital twins to life in a scalable and secure manner
29-
* Connect assets such as IoT devices and existing business systems
30-
* Use a robust event system to build dynamic business logic and data processing
31-
* Integrate with Azure data, analytics, and AI services to help you track the past and then predict the future
29+
* Connect assets such as IoT devices and existing business systems, using a robust event system to build dynamic business logic and data processing
30+
* Query the live execution environment to extract real-time insights from your twin graph
31+
* Build connected 3D visualizations of your environment that display business logic and twin data in context
32+
* Query historized environment data and integrate with other Azure data, analytics, and AI services to better track the past and predict the future
3233

33-
## Open modeling language
34+
## Define your business environment
3435

3536
In Azure Digital Twins, you define the digital entities that represent the people, places, and things in your physical environment using custom twin types called [models](concepts-models.md).
3637

37-
You can think of these model definitions as a specialized vocabulary to describe your business. For a building management solution, for example, you might define models such as Building, Floor, and Elevator. You can then create digital twins based on these models to represent your specific environment.
38+
You can think of these model definitions as a specialized vocabulary to describe your business. For a building management solution, for example, you might define a model that defines a Building type, a Floor type, and an Elevator type. Models are defined in a JSON-like language called [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/dtdlv2.md), and they describe types of entities according to their state properties, telemetry events, commands, components, and relationships. You can design your own model sets from scratch, or get started with a pre-existing set of [DTDL industry ontologies](concepts-ontologies.md) based on common vocabulary for your industry.
3839

39-
*Models* are defined in a JSON-like language called [Digital Twins Definition Language (DTDL)](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/dtdlv2.md), and they describe twins by their state properties, telemetry events, commands, components, and relationships. Here are some other capabilities of models:
40-
* Models define semantic *relationships* between your entities so that you can connect your twins into a graph that reflects their interactions. You can think of the models as nouns in a description of your world, and the relationships as verbs.
41-
* You can specialize twins using model *inheritance*. One model can inherit from another.
42-
* You can design your own model sets from scratch, or get started with a pre-existing set of [DTDL industry ontologies](concepts-ontologies.md) based on common vocabulary for your industry.
40+
>[!TIP]
41+
>DTDL is also used for data models throughout other Azure IoT services, including [IoT Plug and Play](../iot-develop/overview-iot-plug-and-play.md) and [Time Series Insights](../time-series-insights/overview-what-is-tsi.md). This compatibility helps you connect your Azure Digital Twins solution with other parts of the Azure ecosystem.
4342
44-
DTDL is also used for data models throughout other Azure IoT services, including [IoT Plug and Play](../iot-develop/overview-iot-plug-and-play.md) and [Time Series Insights](../time-series-insights/overview-what-is-tsi.md). This compatibility helps you connect your Azure Digital Twins solution with other parts of the Azure ecosystem.
43+
Once you've defined your data models, use them to create [digital twins](concepts-twins-graph.md) that represent each specific entity in your environment. For example, you might use the Building model definition to create several Building-type twins (Building 1, Building 2, and so on). You can also use the relationships in the model definitions to connect twins to each other, forming a conceptual graph.
4544

46-
## Live execution environment
45+
You can view your Azure Digital Twins graph in [Azure Digital Twins Explorer](concepts-azure-digital-twins-explorer.md), which provides an interface to help you build and interact with your graph:
4746

48-
Digital models in Azure Digital Twins are live, up-to-date representations of the real world. Using the relationships in your custom DTDL models, you'll connect twins into a live graph representing your environment.
47+
:::image type="content" source="media/concepts-azure-digital-twins-explorer/azure-digital-twins-explorer-demo.png" alt-text="Screenshot of Azure Digital Twins Explorer, showing a graph of nodes representing digital twins." lightbox="media/concepts-azure-digital-twins-explorer/azure-digital-twins-explorer-demo.png":::
4948

50-
You can visualize your Azure Digital Twins graph in [Azure Digital Twins Explorer](concepts-azure-digital-twins-explorer.md), which provides the following interface for interacting with your graph:
49+
## Contextualize IoT and business system data
5150

52-
:::image type="content" source="media/concepts-azure-digital-twins-explorer/azure-digital-twins-explorer-demo.png" alt-text="Screenshot of Azure Digital Twins Explorer, showing a graph of nodes representing digital twins." lightbox="media/concepts-azure-digital-twins-explorer/azure-digital-twins-explorer-demo.png":::
51+
Digital models in Azure Digital Twins are live, up-to-date representations of the real world.
52+
53+
To keep digital twin properties current against your environment, you can use [IoT Hub](../iot-hub/about-iot-hub.md) to connect your solution to IoT and IoT Edge devices. These hub-managed devices are represented as part of your twin graph, and provide the data that drives your model. You can create a new IoT Hub to use with Azure Digital Twins, or [connect an existing IoT Hub](how-to-ingest-iot-hub-data.md) along with the devices it already manages.
54+
55+
You can also drive Azure Digital Twins from other data sources, using [REST APIs](concepts-apis-sdks.md) or connectors to other Azure services like [Logic Apps](../logic-apps/logic-apps-overview.md). These methods can help you input data from business systems and incorporate them into your twin graph.
56+
57+
Azure Digital Twins provides a rich event system to keep your graph current, including data processing that can be customized to match your business logic. You can connect external compute resources, such as [Azure Functions](../azure-functions/functions-overview.md), to drive this data processing in flexible, customized ways.
5358

54-
Azure Digital Twins provides a rich event system to keep that graph current with data processing and business logic. You can connect external compute resources, such as [Azure Functions](../azure-functions/functions-overview.md), to drive this data processing in flexible, customized ways.
59+
## Query for environment insights
5560

56-
You can also extract insights from the live execution environment, using Azure Digital Twins' powerful *query API​*. The API lets you query with extensive search conditions, including property values, relationships, relationship properties, model information, and more. You can also combine queries, gathering a broad range of insights about your environment and answering custom questions that are important to you.
61+
Azure Digital Twins provides a powerful query API​ to help you extract insights from the live execution environment. The API can query with extensive search conditions, including property values, relationships, relationship properties, model information, and more. You can also combine queries, gathering a broad range of insights about your environment and answering custom questions that are important to you. For more details about the language used to craft these queries, see [Query language](concepts-query-language.md).
5762

58-
## Input from IoT and business systems
63+
## Visualize environment in 3D Scenes Studio (preview)
5964

60-
To keep the live execution environment of Azure Digital Twins up to date with the real world, you can use [IoT Hub](../iot-hub/about-iot-hub.md) to connect your solution to IoT and IoT Edge devices. These hub-managed devices are represented as part of your twin graph, and provide the data that drives your model.
65+
Azure Digital Twins [3D Scenes Studio (preview)](concepts-3d-scenes-studio.md) is an immersive visual 3D environment, where end users can monitor, diagnose, and investigate operational digital twin data with the visual context of 3D assets. With a digital twin graph and curated 3D model, subject matter experts can leverage the studio's low-code builder to map the 3D elements to digital twins in the Azure Digital Twins graph, and define UI interactivity and business logic for a 3D visualization of a business environment. The 3D scenes can then be consumed in the hosted 3D Scenes Studio, or in a custom application that leverages the embeddable 3D viewer component.
6166

62-
You can create a new IoT Hub for this purpose with Azure Digital Twins, or [connect an existing IoT Hub](how-to-ingest-iot-hub-data.md) along with the devices it already manages.
67+
Here's an example of a scene in 3D Scenes Studio, showing how digital twin properties can be visualized with 3D elements:
6368

64-
You can also drive Azure Digital Twins from other data sources, using REST APIs or connectors to other services like [Logic Apps](../logic-apps/logic-apps-overview.md).
69+
:::image type="content" source="media/quickstart-3d-scenes-studio/studio-full.png" alt-text="Screenshot of a sample scene in 3D Scenes Studio." lightbox="media/quickstart-3d-scenes-studio/studio-full.png":::
6570

66-
## Output data for storage and analytics
71+
## Share twin data to other Azure services
6772

6873
The data in your Azure Digital Twins model can be routed to downstream Azure services for more analytics or storage.
6974

@@ -80,18 +85,18 @@ Here are some things you can do with event routes in Azure Digital Twins:
8085

8186
Flexible egress of data is another way that Azure Digital Twins can connect into a larger solution, and support your custom needs for continued work with these insights.
8287

83-
## Azure Digital Twins in a solution context
88+
## Sample solution architecture
8489

8590
Azure Digital Twins is commonly used in combination with other Azure services as part of a larger IoT solution.
8691

87-
A sample architecture of a complete solution using Azure Digital Twins may contain the following components:
92+
A possible architecture of a complete solution using Azure Digital Twins may contain the following components:
8893
* The Azure Digital Twins service instance. This service stores your twin models and your twin graph with its state, and orchestrates event processing.
8994
* One or more client apps that drive the Azure Digital Twins instance by configuring models, creating topology, and extracting insights from the twin graph.
9095
* One or more external compute resources to process events generated by Azure Digital Twins, or connected data sources such as devices. One common way to provide compute resources is via [Azure Functions](../azure-functions/functions-overview.md).
9196
* An IoT hub to provide device management and IoT data stream capabilities.
9297
* Downstream services to provide things like workflow integration (like Logic Apps), cold storage (like Azure Data Lake), or analytics (like Azure Data Explorer or Time Series Insights).
9398

94-
The following diagram shows where Azure Digital Twins lies in the context of a larger Azure IoT solution.
99+
The following diagram shows where Azure Digital Twins might lie in the context of a larger sample Azure IoT solution.
95100

96101
:::image type="content" source="media/overview/solution-context.png" alt-text="Diagram showing input sources, output services, and two-way communication with both client apps and external compute resources." border="false" lightbox="media/overview/solution-context.png":::
97102

0 commit comments

Comments
 (0)