You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/digital-twins/about-digital-twins.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,9 @@ ms.custom: mvc
12
12
#Customer intent: As an Azure enterprise customer, I want to know what capabilities Digital Twins has so that I can build next-generation IoT services.
Azure Digital Twins Preview is an Azure IoT service that creates comprehensive models of the physical environment. It can create spatial intelligence graphs to model the relationships and interactions between people, spaces, and devices.
18
20
@@ -47,7 +49,7 @@ Consider a smart utility app that involves several electricity usage meters conn
47
49
48
50
### Digital twin object models
49
51
50
-
[Digital twin object models](./concepts-objectmodel-spatialgraph.md#digital-twins-object-models) are predefined device protocols and data schema. They align your solution’s domain-specific needs to accelerate and simplify development.
52
+
[Digital twin object models](./concepts-objectmodel-spatialgraph.md#digital-twins-object-models) are predefined device protocols and data schema. They align your solution's domain-specific needs to accelerate and simplify development.
51
53
52
54
For example, a room occupancy application might use predefined space types such as campus, building, floor, and room.
These constraints exist to help simplify learning about the new service and its many features.
18
-
19
-
> [!NOTE]
20
-
> These limits will be increased or removed by general availability (GA).
17
+
During the public preview, Azure Digital Twins has the following temporary subscription, instance, and rate limits for existing customers. These constraints exist to help simplify learning about the new service and its many features, and will be increased or removed by general availability (GA).
21
18
22
19
## Per-subscription limits
23
20
24
-
During the public preview, each Azure subscription can create or run only one Azure Digital Twins instance at a time.
25
-
26
-
> [!TIP]
27
-
> If you delete your instance, you can create a new one.
21
+
During the public preview, each Azure subscription can create or run only one Azure Digital Twins instance at a time. If you delete your instance, you can create a new one.
28
22
29
23
## Per-instance limits
30
24
@@ -66,7 +60,7 @@ The following limits set the total number of all user-defined function calls mad
66
60
The following limits cap the total number of all messages your devices can send to your Azure Digital Twins instance:
The Azure Digital Twins service allows you to re-create a digital image of your physical environment. You can then get notified by events in your environment and customize your responses to them.
19
21
20
22
This quickstart uses [a pair of .NET samples](https://github.com/Azure-Samples/digital-twins-samples-csharp) to digitize an imaginary office building. It shows you how to find available rooms in that building. With Digital Twins, you can associate many sensors with your environment. You also can find out if the air quality of your available room is optimal with the help of a simulated sensor for carbon dioxide. One of the sample applications generates random sensor data to help you visualize this scenario.
You can use the Azure Digital Twins Preview service to bring together people, places, and devices in a coherent spatial system. This series of tutorials demonstrates how to use Azure Digital Twins to detect room occupancy with optimal conditions of temperature and air quality.
18
20
19
21
These tutorials will walk you through a .NET console application to build a scenario of an office building. The building has multiple floors and rooms within each floor. The rooms contain devices with attached sensors that detect motion, ambient temperature, and air quality.
@@ -34,7 +36,7 @@ These tutorials use and modify the same samples that the [quickstart to find ava
34
36
35
37
## Prerequisites
36
38
37
-
- An Azure subscription. If you don’t have an Azure account, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
39
+
- An Azure subscription. If you don't have an Azure account, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
38
40
39
41
- The .NET Core SDK. The Azure Digital Twins samples used in these tutorials are written in C#. Make sure to install [.NET Core SDK version 2.1.403 or later](https://www.microsoft.com/net/download) on your development machine to build and run the sample. Check that the right version is installed on your machine by running `dotnet --version` in a command window.
40
42
@@ -143,7 +145,7 @@ The **provisionSample.yaml** file contains the following nodes:
143
145
144
146
-**spaces**: In the Digital Twins object model, `spaces` represent the physical locations. Each space has a `Type`—for example, Region, Venue, or Customer—and a friendly `Name`. Spaces can belong to other spaces, creating a hierarchical structure. The provisionSample.yaml file has a spatial graph of an imaginary building. Note the logical nesting of spaces of type `Floor` within `Venue`, `Area` in a floor, and `Room` nodes in an area.
145
147
146
-
-**devices**: Spaces can contain `devices`, which are physical or virtual entities that manage a number of sensors. For example, a device might be a user’s phone, a Raspberry Pi sensor pod, or a gateway. In the imaginary building in your sample, note how the room named **Focus Room** contains a **Raspberry Pi 3 A1** device. Each device node is identified by a unique `hardwareId`, which is hardcoded in the sample. To configure this sample for an actual production, replace these with values from your setup.
148
+
-**devices**: Spaces can contain `devices`, which are physical or virtual entities that manage a number of sensors. For example, a device might be a user's phone, a Raspberry Pi sensor pod, or a gateway. In the imaginary building in your sample, note how the room named **Focus Room** contains a **Raspberry Pi 3 A1** device. Each device node is identified by a unique `hardwareId`, which is hardcoded in the sample. To configure this sample for an actual production, replace these with values from your setup.
147
149
148
150
-**sensors**: A device can contain multiple `sensors`. They can detect and record physical changes like temperature, motion, and battery level. Each sensor node is uniquely identified by a `hardwareId`, hardcoded here. For an actual application, replace these by using the unique identifiers of the sensors in your setup. The provisionSample.yaml file has two sensors to record *Motion* and *CarbonDioxide*. Add another sensor to record *Temperature*, by adding the following lines, below the lines for the CarbonDioxide sensor. These are provided in provisionSample.yaml as commented-out lines. You can uncomment them by removing the `#` character in the front of each line.
> The Azure Digital Twins preview program is currently at capacity. As a result, new customers are no longer being added and **no additional Azure Digital Twins resources can be created at this time**. If an instance somewhere is deleted, it is possible your resource creation will succeed and you can proceed normally, but this is not guaranteed. Please continue to check back for any update to this status.
0 commit comments