---
description: Configure Connect IoT project setup and value ownership for the OPC UA Standard integration.
alias: userguide-equipment-integration-opcua-standard-connect-iot-setup
---

# Configure Connect IoT

## Purpose

This page describes the **OPC UA Standard** configuration and responsibilities required to connect an MES Resource to the machine. General **Connect IoT** concepts and administration are not covered in this section.

See [Connect IoT concepts](https://help.criticalmanufacturing.com/tutorials/modules/connect-iot-equipment-integration/connectiot/connect-iot/) and [Connect IoT administration](https://help.criticalmanufacturing.com/operationguide/application-administration/connect-iot/connectiotadministration/).

System responsibilities are defined in [Architecture and Responsibilities](../modeling/architecture.md). This page focuses on the project setup and on ownership of the exchanged values.

## Prerequisites

Before starting the equipment connection:

- A compatible Industrial Equipment package and Connect IoT package are deployed.
- The Resource is enabled for equipment integration.
- An Automation Controller Instance exists and associates the Resource with the OPC UA Standard Controller.
- The Resource has `EnableAutomationScenarios` set to `true`.
- The selected OPC UA Server profile is complete.
- The Resource hierarchy resolves to the expected base node.
- The Automation Manager runtime can reach the OPC UA endpoint.

## Setup Procedure

1. Select the **Automation Manager** that will host the equipment connection.
2. Associate **OPC UA Standard Controller** with the exact **MES Resource** and the intended **Automation Manager**.
3. Configure the server profile, `Namespace`, and timeouts as defined in [Configure the OPC UA Connection](opcua-connection.md).
4. Configure the Resource attributes and enabled features.
5. Start the equipment connection.
6. Verify the selected profile, endpoint, namespace, and Resource base node.
7. Verify subscriptions to machine-owned trigger nodes.
8. Verify write access to MES-owned handshake and Recipe nodes.
9. Verify the MES event path for operator-initiated or hybrid operations.
10. Perform the feature and recovery tests before releasing the Resource.

## Startup Behavior

When the connection starts, Connect IoT:

1. resolves the Resource base node and enabled-feature nodes.
2. loads the connection values from the profile selected by the canonical [Profile Selection Rule](opcua-connection.md#profile-selection-rule).
3. establishes the OPC UA session.
4. performs the initial state synchronization.
5. subscribes to the machine-owned request and state nodes.
6. reports the connection as ready only when the required setup succeeds.

The initial state synchronization does not rely on the State transitions. Normal state changes received after startup use the Resource state model's transition validation.