Skip to content

Commit 14e264e

Browse files
committed
restructure H2
1 parent ffe6e01 commit 14e264e

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

articles/iot/iot-overview-device-management.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -27,16 +27,14 @@ In an edge-based IoT solution, asset management refers to processes such as regi
2727
- Asset, tags and events creation
2828
- Data flow endpoint creation
2929
- Asset and data flow endpoints secrets management
30-
- Asset updates
31-
- Asset monitoring
3230
- Enabling and disabling assets
3331

34-
In an edge-based IoT solution, an MQTT broker enables bidirectional edge/cloud communication, and powers [event-driven applications](/azure/architecture/guide/architecture-styles/event-driven) at the edge. For example, you can:
32+
In an edge-based IoT solution, *command and control* refers to the processes that let you send commands to assets and receive responses from them. For example, you can:
3533

3634
- Control the cameras pan, tilt, and zoom.
3735
- Capture snapshots from a video stream and publish them to an MQTT topic.
3836
- Publish OPC UA machine status events to the MQTT broker.
39-
- Shut down the lights of a building to save energy.
37+
- Turn off the lights of a building to save energy.
4038

4139
## Primitives
4240

@@ -51,6 +49,7 @@ An edge-based IoT solution can use the following primitives for asset management
5149
- *Schema registry* that lets you define and manage the schema for your assets. Data flows use schemas to deserialize and serialize messages.
5250
- *Akri services* that let you deploy and configure connectivity protocols, such as OPC UA and ONVIF, at the edge. Akri services use the asset and asset endpoint resources in Azure Device Registry to model the different device and protocol connections in your environment.
5351
- *Secret Store extension* to sync the secrets down from the cloud and store them on the edge as Kubernetes secrets. Azure IoT Operations uses Azure Key Vault as the managed vault solution on the cloud, and uses [Azure Key Vault Secret Store extension for Kubernetes](/azure/azure-arc/kubernetes/secret-store-extension) to sync the secrets.
52+
- *Sites* that group Azure IoT Operations instances by physical location and make it easier for OT users to locate and manage assets. Your IT administrator creates sites and assigns Azure IoT Operations instances to them. To learn more, see [What is Azure Arc site manager (preview)?](/azure/azure-arc/site-manager/overview).
5453

5554
To learn more, see [What is asset management in Azure IoT Operations](../iot-operations/discover-manage-assets/overview-manage-assets.md) and [Configure data flows in Azure IoT Operations](../iot-operations/connect-to-cloud/howto-create-dataflow.md).
5655

@@ -63,9 +62,13 @@ To learn more, see [What is asset management in Azure IoT Operations](../iot-ope
6362
- Asset registration in a single unified registry that enables edge and cloud management.
6463
- Defining asset tags and events to enable data flow from OPC UA servers to the MQTT broker.
6564

66-
## Asset endpoint secrets management
65+
## Data flow endpoint creation
6766

68-
## Asset monitoring
67+
## Asset and data flow endpoints secrets management
68+
69+
## Command and control
70+
71+
The MQTT broker enables bidirectional edge/cloud communication, and powers [event-driven applications](/azure/architecture/guide/architecture-styles/event-driven) at the edge.
6972

7073
### [Cloud-based solution](#tab/cloud)
7174

0 commit comments

Comments
 (0)