Merge pull request #294501 from dominicbetts/patch-3

IIoT: OPC UA updates to dataspaces article

Author: prmerger-automator[bot]

articles/iot/howto-iot-industrial-dataspaces.md

@@ -39,9 +39,13 @@ All the required components to enable the industrial dataspace are deployed to A
 
 Providing the Product Carbon Footprint (PCF) is one of the most popular use cases for industrial dataspaces. It's increasingly important in the buying decision for customers. Products with a low PCF are popular, but accurately calculating the PCF is hard. The [Green-House Gas (GHG) Protocol](https://ghgprotocol.org) is a common calculation method for the PCF. It splits up the calculation task into scope 1, scope 2, and scope 3 emissions. This example and reference implementation focuses on calculating scope 2 emissions from the simulated production lines. Scope 2 emissions are the emissions produced during a production process. The simulated stations along the production lines provide energy consumption data. This data is used to calculate the scope 2 carbon footprint for each produced product, if the *marginal carbon intensity* of the electrical energy consumed is known for the location of the simulated production lines. This information is optionally retrieved from a non-Microsoft cloud service operated by [WattTime](https://watttime.org). If the WattTime service isn't configured, the calculation uses an average value.
 
-## IEC 63278 Asset Administration Shell
+## IEC 62541 Open Platform Communication Unified Architecture (OPC UA)
 
-To provide product data in a machine-readable and standardized fashion, this example uses the IEC 63278 Asset Administration Shell (AAS). This example automatically creates an AAS for a sample of the simulated products produced and stores the AAS in an AAS repository. The repository is provided as an open-source reference implementation by the [Digital Twin Consortium](https://www.digitaltwinconsortium.org). This reference implementation supports AAS modeling with [OPC UA](https://opcfoundation.org/about/opc-technologies/opc-ua). This approach simplifies AAS modeling because you can use any OPC UA modeling tool such as the [Siemens OPC UA Modeling Editor (SiOME)](https://support.industry.siemens.com/cs/document/109755133/siemens-opc-ua-modeling-editor-(siome)?dti=0&lc=en-US) or the [CESMII Smart Manufacturing Profile Designer](https://profiledesigner.cesmii.net). The configuration of the deployed AAS repository happens automatically during the deployment workflow and comes with its own dashboard. To access the dashboard, navigate to the **Overview** page of the AAS repository container app from the Azure portal, and select the **Application URL** displayed. Expand the **AAS Environment** tree control to see the individual Asset Admin Shells. Navigate to the **AAS Environment > Objects > Submodels > CarbonFootprint > ProductCarbonFootprint > PCFCO2eq** node in the OPC UA tree and select it to display the calculated scope 2 CO2 PCF.
+This reference implementation supports data modeling in a machine-readable and standardized fashion with [OPC UA](https://opcfoundation.org/about/opc-technologies/opc-ua). This approach is aligned with the new OPC Foundation [Cloud Initiative](https://opcfoundation.org/cloud) and simplifies modeling because it taps into the large OPC UA ecosystem. You can use any OPC UA modeling tool such as the [Siemens OPC UA Modeling Editor (SiOME)](https://support.industry.siemens.com/cs/document/109755133/siemens-opc-ua-modeling-editor-(siome)?dti=0&lc=en-US) or the [CESMII Smart Manufacturing Profile Designer](https://profiledesigner.cesmii.net) with the reference implementation. The reference implementation also uses the OPC UA [Nodeset](https://opcconnect.opcfoundation.org/2017/04/using-nodeset-files-to-exchange-information) file format and the new OpenAPI-compatible [OPC UA REST interface](https://reference.opcfoundation.org/Core/Part6/v105/docs/G.3).
+
+## IEC 63278 Asset Administration Shell (AAS)
+
+To provide product semantics, this example uses the [Submodel templates](https://industrialdigitaltwin.org/en/content-hub/submodels) from the IEC 63278 Asset Administration Shell (AAS). This example automatically creates a Product Caron Footprint (PCF) AAS for a sample of the simulated products produced and stores the AAS in an AAS Repository. The AAS Repository is provided as an open-source reference implementation by the [Digital Twin Consortium](https://www.digitaltwinconsortium.org). The configuration of the deployed AAS Repository happens automatically during the deployment workflow and comes with its own dashboard. To access the dashboard, navigate to the **Overview** page of the AAS Repository container app from the Azure portal, and select the **Application URL** displayed. Expand the **AAS Environment** tree control to see the individual Asset Admin Shells. Navigate to the **AAS Environment > Objects > Submodels > CarbonFootprint > ProductCarbonFootprint > PCFCO2eq** node in the rendered OPC UA tree and select it to display the calculated scope 2 CO2 PCF.
 
 > [!NOTE]
 > The AAS repository has a REST interface that's [OpenAPI](https://swagger.io/specification) compatible. To access the Swagger UI, add `/swagger` to the AAS repository URL in your web browser. To authenticate and authorize with the REST interface, select **Authorize** on the Swagger webpage. Enter `admin` as the username and use the password you chose during deployment of this reference solution for the password, then select **Authorize** followed by **Close**. To try out any of the REST interface methods, select it, select **Try it out**, provide any necessary parameters, and select **Execute**. The response from the AAS repository is available in the **Server response** text box.