Configure AVEVA Recipe Management in Standalone Mode using OPC UA Client Server

You can configure AVEVA Recipe Management in Standalone mode to directly communicate with a PLC via an OPC UA server. This requires configuring OI-Gateway in Operations Control Management Console with Add OPCUA Connection option to connect to OPC UA server.

Prerequisite

• Install AVEVA Recipe Management and configure the AVEVA Recipe Management Server feature as Standalone mode.

• Install AVEVA Communication Drivers Pack with PCS Plug-in and Standards – GATEWAY features selected. Refer to the Install documents to install AVEVA Communication Drivers Pack.

To configure OPCUA Connection in OI-Gateway

1. Open Operations Control Management Console and in the left pane, navigate to Operations Integration Server Manager > Default Group > Local > [Admin] Operations Integration Supervisory Servers > Standards - Gateway > OI.GATEWAY.3.

2. Expand OI.GATEWAY.3 and select Configuration.

   In the Global Parameters area, under Client Connectivity, in the PCS Scope Name box, type the name for the PCS scope. The maximum length of the scope name is 32 characters. You can use alphanumeric characters, however, the initial character must be an alphabet. The only valid special character is the underscore (_). This field is case insensitive.

   

3. Right-click Configuration and select Add OPCUA Connection option to configure the connection between OI-Gateway and OPC UA Client Server.

   

   The new instance appears in the tree structure. Rename it with the desired name (say, OPCUACLIENT).

   

4. Select the OPCUACLIENT node and in the OPC UA Server Details area, do the following:

   1. In the OPC UA Server Node box, type the computer name (Node name) or the IP address of the OPC UA Server. The endpoint URL(s) of that Node or Server is automatically displayed in the Endpoint URL box. If you do not have the Node name information, you can manually enter the OPC UA Server endpoint.

      NOTE: You can also click the Browse button to browse, and then select the computer name or IP address of the OPC UA Server.

   2. In the OPC UA Endpoint URL box, type the OPC UA Server endpoint. You can also select an endpoint URL from the Endpoint URL list, if the Node selected in the OPC UA Node box has more than one endpoint URLs.

      NOTE: Click the Refresh button to refresh the endpoint list, if you want to view the list of the latest sever endpoint URIs.

   3. In the OPC UA Server Certificate box, the OPC UA Server Certificate gets displayed. You can also import the valid OPC UA Server certificate.

   4. Select the Security Policy. This field is set to None by default. The selected Security Policy should be the one OPC UA server is configured with. The description of each mode is given in the below table:

      Option	Description
      None	Indicates that no security is applied.
      Basic256Sha256	Indicates that Basic256Sha256 security policy is applied.
      Aes128_Sha256_Rsa0aep	Indicates that Aes128_Sha256_Rsa0aep security policy is applied.
      Aes256_Sha256_RsaPss	Indicates that Aes256_Sha256_RsaPss security policy is applied.

      NOTE: If the Security Policy option is not None, the OPC UA Server’s digital certificate must be trusted and be made available on the UA Client computer.

   5. Select the Security Message Mode. This field is set to None by default.The description of each mode is given in the below table:

      Option	Description
      None	Indicates that no security is applied.
      Sign and Encrypt	Indicates that all messages are signed and encrypted.
      Sign	Indicates that all messages are signed but not encrypted.

      If the Security Message Mode option is not None, the OPC UA Server’s digital certificate must be trusted and be made available on the UA Client computer.

5. In the User Credentials area, do the following:

   1. Select the Anonymous User check box to allow login without the user credentials. This field is selected by default.

      Or

   2. Clear the Anonymous User check box, type a user name and a password in the User Name box and the Password box respectively. The credentials should be of the users configured to access OPC UA server.

   3. User Credentials: You can create a secure connection with the OPC UA Server depending on how the server accepts the connection.

      For example, if an OPC UA Client wants to connect to an OPC UA Server that does not support anonymous connections, the OPC UA client must provide a valid User Name and Password.

   4. Select Test Connection to establish and verify the connection to the configured OPC UA server. When the connection is successful, the OPC UA Namespace available gets listed.

      

6. Right-click OPCUACLIENT node and select Add OPCUAGroup Connection to add the OPCUA group.

   

7. Rename the OPCUAGroup Connection with the desired name (say, DeviceGroup).

   

8. Click Browse OPC Items button to open the OPCUA Tag Browser window.

   

9. In the OPCUA Tag Browser window, navigate to select OPCUA Server URL, expand to select the required OPCUA server tags, and click Add to list.

   

10. Click OK to add the selected device tags.

    

11. Select the Device Items tab and double-click Name field for each added Item Reference node and update with custom tag names for IO references mapping (e.g. MixCI).

    

12. Right-click OI.GATEWAY.3 and select Activate (Auto start after reboot) to activate the OI-Gateway communication.

    

13. Configure AVEVA Recipe Management IO Reference fields with the unique Tags defined in Device Items list of OPCUAGroup connection node.

    To configure IO References in AVEVA Recipe Management,

    1. Navigate to Execution menu, and then select the Equipment.

    2. In the Equipment screen, select IO Map tab.

    3. Select Edit button to update the IO Reference for each recipe status or parameters.

       Syntax to configure IO Reference is <PCS Scopename:Topicname.ItemReferenceTagname>.
       For example, the syntax is TEST:OPCUAClENT_DeviceGroup.MixSI.

       

       NOTE: Ensure that Equipment or Capability Parameters IO are mapped correctly.

    Similarly, you can map status or parameters of a recipe with the required IO references configured in OPC UA server tags.