Configure AVEVA Recipe Management in Standalone Mode using OI Gateway

You can configure AVEVA Recipe Management in Standalone mode to directly communicate with a PLC via an OPCUA Client. For this, you need to configure OPCUA Client in OI Gateway under Operations Integration Server Manager to establish communication with the OPCUA server.

Note: After the upgrade, the ArchestrA.ASBOPCUAClientService option which was used earlier for configuring OPCUA Client to connect with the OPCUA server will be unavailable in Configure ArchestrA Services window.

Prerequisite

To successfully establish communication between OI Gateway and AVEVA Recipe Management in Standalone mode, install and configure the following products in the sequence given below:

• Install AVEVA Recipe Management.

• Install and configure the latest version of AVEVA Communication Drivers Pack (CDP) with PCS Plug-in and Standards – GATEWAY features selected. Refer the Communication Drivers Pack – Standards - Gateway Driver User Guide for more information. Contact the Technical Support team to get the CDP executable files and related documents or access Knowledge and Support Center to download.

• Configure the AVEVA Recipe Management Server feature in Standalone mode.

• For AVEVA Recipe Management to communicate to OPCUA server, configure OPCUA Connection using OI Gateway in Operations Control Management Console

To configure OPCUA Connection in OI Gateway

1. From the Windows Start menu, point to Programs, AVEVA, and then click the Operations Control Management Console.

2. 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.

3. 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.

   

4. Click Save icon located at the top-right corner of the dialog box.

5. Right-click Configuration and select Add OPCUA Connection option to configure connection to OPCUA Server.

   

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

   

6. Select the RMOPCUACONNECTION node and in the OPCUA Server Details area, do the following:

   1. In the OPCUA Server Node box, type the computer name (Node name) or the IP address of the OPCUA 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 OPCUA Server endpoint.

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

   2. In the OPCUA Endpoint URL box, type the OPCUA Server endpoint. You can also select an endpoint URL from the Endpoint URL list, if the Node selected in the OPCUA 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 OPCUA Server Certificate box, the OPCUA Server Certificate gets displayed. You can also import the valid OPCUA Server certificate.

   4. Select the Security Policy. This field is set to None by default. The selected Security Policy should be the one OPCUA 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 OPCUA Server’s digital certificate must be trusted and be made available on the OPCUA 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 OPCUA Server’s digital certificate must be trusted and be made available on the OPCUA Client computer.

7. 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 OPCUA server.

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

      NOTE: If an OPCUA Client wants to connect to an OPCUA Server that does not support anonymous connections, the OPCUA client must provide a valid User Name and Password.

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

      

   5. Click Save icon located at the top-right corner of the dialog box.

To configure OPCUA Group Object

8. Right-click RMOPCUACONNECTION node and select Add OPCUAGroup Connection to add the OPCUA group.

   

9. Rename the OPCUAGroup Connection with the desired name (say, DeviceGroup). Provide the following details:

   • Update Interval: Define the frequency at which the Gateway Communication Driver should request for data updates from the OPCUA Server.

   • Data Sampling Interval: Define the frequency at which the OPCUA server should sample its underlying source for data changes. If exception-based reporting is supported by the OPC UA server, this parameter may be set to 0 to request exception-based data changes.

     Since the Update Interval indicates how often the Gateway Communication Driver retrieves the data from the OPCUA server, you should set the Data Sampling Interval at a rate faster than the Update Interval.

     For example, if you set the Update Interval as 5000 ms and the Data Sampling Interval as 1000 ms, then the Gateway Communication Driver records 5 data samples every 5 seconds.

   • Read Only: Leave this option unchecked.

   • Demand Read: Leave this option unchecked.

   

10. Click Browse OPCUA Server button to open the OPCUA Tag Browser window.

    

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

    

12. Click OK to add the selected device tags.

    

13. 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. VAR, MixSI, MixCS, and so on).

    Click Save icon located at the top-right corner of the dialog box.

    

To activate OI.GATEWAY.3

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

  

To configure IO References in AVEVA Recipe Management

To configure AVEVA Recipe Management IO Reference fields with the unique Tags defined in Device Items list of OPCUAGroup connection node, follow the steps below:

14. Navigate to Configuration > Equipment menu, and then select the Equipment.

15. In the Equipment Details screen, click Check Out, and then select IO Map tab.

16. Click Edit button and provide the IO Reference for each recipe status or parameters. The IO references must match the tag names configured in OPCUA server.

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

    

    NOTE: Ensure that Equipment or Capability Parameters IO are mapped correctly with the unique Tags defined in Device Items list of OPCUAGroup connection node.