Školenie
Certifikácia
Microsoft Certified: Identity and Access Administrator Associate - Certifications
Demonstrate the features of Microsoft Entra ID to modernize identity solutions, implement hybrid solutions, and implement identity governance.
Tento prehliadač už nie je podporovaný.
Inovujte na Microsoft Edge a využívajte najnovšie funkcie, aktualizácie zabezpečenia a technickú podporu.
In Azure IoT Operations, a key task is to manage the assets that are part of your solution. This article:
Assets are a core element of an Azure IoT Operations solution. In Azure IoT Operations, an asset is a logical entity that you create to represent a real asset. An Azure IoT Operations asset can emit telemetry and events. You use these logical asset instances to reference the real assets in your industrial edge environment.
Assets connect to Azure IoT Operations instances through asset endpoints, which are the OPC UA servers that have southbound connections to one or more assets.
Azure IoT Operations includes several services that help you manage your assets.
The following diagram shows the high-level architecture of Azure IoT Operations. The services that you use to manage assets are highlighted in red:
The following tasks are useful for operations teams in sectors such as industry, retail, and health:
The operations experience web UI lets operations teams perform these tasks in a simplified web interface. The operations experience uses the other services described previously, to complete these tasks. You can also use the Azure IoT Operations CLI to manage assets by using the az iot ops asset set of commands.
The operations experience uses the connector for OPC UA to exchange data with local OPC UA servers. OPC UA servers are software applications that communicate with assets. The connector for OPC UA exposes:
The operations experience uses the media connector and the connector for ONVIF to manage media sources such as cameras. The media connector lets you access media sources such as edge-attached cameras. The connector for ONVIF discovers and registers ONVIF assets such as cameras connected to your cluster.
The operations experience lets users create assets and subscribe to OPC UA tags in a user-friendly interface. Users can create custom assets by providing asset details and configurations. Users can create or import tag and event definitions, subscribe to them, and assign them to an asset.
When you create an asset in the operations experience or by using the Azure IoT Operations CLI extension, that asset is defined in Azure Device Registry.
Device Registry provides a single registry for devices and assets across applications running in the cloud or on the edge. In the cloud, assets are created as Azure resources, which give you management capabilities over them like organizing assets with resource groups and tags. On the edge, the Azure Device Registry creates a Kubernetes custom resource for each asset and keeps the two asset representations in sync.
Device Registry provides several capabilities that help teams to manage assets:
For example, the following set of screenshots shows a single asset, in this case a thermostat, viewed both in cloud management tools and on an Azure IoT Operations cluster. The first screenshot shows the thermostat asset in the operations experience:
This screenshot shows the same thermostat asset in the Azure portal:
And the final screenshot shows the same thermostat asset as a Kubernetes custom resource:
A key requirement in industrial environments is for a common standard or protocol for machine-to-machine and machine-to-cloud data exchange. By using a widely supported data exchange protocol, you can simplify the process to enable diverse industrial assets to exchange data with each other, with workloads running in your Kubernetes cluster, and with the cloud. OPC UA is a specification for a platform independent service-oriented architecture that enables data exchange in industrial environments.
An industrial environment that uses the OPC UA standard, includes the following basic OPC UA elements:
The connector for OPC UA is an OPC UA client that enables data ingress from OPC UA servers into your edge solution based on the OPC UA standard. The connector for OPC UA is installed as part of Azure IoT Operations. You can optionally install an OPC UA simulation server, which lets you test and use the service.
Akri services 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.
Akri services simplify the process of creating assets by automatically onboarding assets with pre-configured datasets and asset endpoints generated by the connectors to represent capabilities and devices on the network.
Currently:
Školenie
Certifikácia
Microsoft Certified: Identity and Access Administrator Associate - Certifications
Demonstrate the features of Microsoft Entra ID to modernize identity solutions, implement hybrid solutions, and implement identity governance.