--- description: Configure which OPC UA Standard features are enabled and their required MES and machine settings. alias: userguide-equipment-integration-opcua-standard-feature-configuration --- # Configure the Features ## Purpose Enable only the features required by the equipment. Each enabled feature requires a compatible MES process, the corresponding machine nodes, and the correct ownership behavior. Detailed runtime sequences are documented in the [Features](../features/index.md) section. This page defines what must be configured before those sequences can run. ## Feature Matrix | Feature | MES and Industrial Equipment configuration | Machine configuration | Expected result | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | **Track In** | Configure a valid Material process and Resource eligibility. Decide whether `IndEqAutomationOperationAllowFIFO` permits resolution without an explicit Material name | Expose the **Track In** payload and handshake nodes and write the payload before raising the request | MES commits **Track In** after the machine confirms the performed signal within `MachineReplyTimeout` | | **Recipe Download** | Enable Recipe Management, configure `RecipeContext`, and configure the required Recipe Parameters and OPC UA data types | Expose writable Recipe nodes whose Tag Names match the MES Parameter names | The machine receives the Recipe values resolved for the Material and Resource context | | **Data Collection** | Configure `MaterialDataCollectionContext`, the **Data Collection** definition, readings, Parameters, limits, and sample behavior | Expose Material, reading, sample, Parameter, and request nodes with compatible data types | MES validates and stores the machine values in the applicable **Data Collection** Instance | | **Track Out** | Configure a process in which the in-process Material can complete at the Resource | Expose the **Track Out** payload and handshake nodes | MES commits **Track Out** after the machine confirms the performed signal within `MachineReplyTimeout` | | **Abort** | Configure the MES process rules that permit an in-process Material to be aborted | Expose the **Abort** Material and handshake nodes and define the physical response to a performed **Abort** signal | MES commits **Abort** after the machine confirms, without replacing machine safety behavior | | **State Synchronization** | Assign a Resource state model and configure `IndEqResourceStateResolution` only for machine values that do not directly match MES state names | Expose `State.MainState` and, where required, `State.SubState` and `State.Reason` | MES initially aligns with the machine state and subsequently follows valid Resource state transitions | | **Hybrid Initiation** | Enable the MES operation event path for the Resource | Monitor `MESOperationPerformed` even when `MachineOperationRequest` is `false` | An operator-initiated MES operation and a machine-initiated operation converge on the same result handshake without duplication | ## How Features Are Enabled A feature is considered enabled when the Resource `EnableAutomationScenarios` is set to `true` and the corresponding MES process is properly configured. The Resource must have `EnableAutomationScenarios = true` for both operator-initiated and machine-initiated operations. This is required whenever MES sends data, operation results, or control signals through the following path: `MES → Connect IoT → OPC UA Server` For Track In, Track Out, and Abort, enabling `EnableAutomationScenarios` on the Resource enables Connect IoT to process the operation and communicate its result to the OPC UA Server. Recipe Download and Data Collection require additional MES configuration. These features are available only when MES can resolve the corresponding Recipe or Data Collection definition for the applicable process context. Communication initiated by the machine is available when an Automation Controller Instance exists, is running and has a valid OPC UA connection: `OPC UA Server → Connect IoT → MES` When the machine raises a supported request or event, Connect IoT processes it, invokes or reports the corresponding action in MES, and communicates the resulting MES response back to the OPC UA Server when applicable. ## Common Configuration Rules - Configure the Resource and machine node ownership before enabling automatic execution. - Validate all required nodes, data types, and access rights. - Keep machine payload values stable before raising a request. - Set MES-owned performed nodes after MES performs the associated action within its transaction. - Configure `MachineReplyTimeout` and verify that a missing machine confirmation fails and rolls back the operation. - Define how the project reconciles MES and physical state after a missing acknowledgement or interrupted communication. - Validate operator and machine initiation separately for hybrid stations. ## Shared Configuration Decisions The feature matrix identifies the feature-specific prerequisites. The following decisions affect more than one feature and must be agreed before commissioning: | Decision | Required configuration | Detailed reference | | --- | --- | --- | | Material resolution | Set `IndEqAutomationOperationAllowFIFO` deliberately and define when an explicit Material name is mandatory | [Operation Handshake](../features/operation-handshake.md) | | Parameter names and types | Match Recipe and Data Collection Parameter names to OPC UA Tag Names and configure `IndEqOpcUaParameterDataType` | [Configure MES and the Resource](mes-resource-configuration.md#7-configure-parameter-settings-and-naming) | | State resolution | Assign the Resource state model and create `IndEqResourceStateResolution` rows only where direct name matching is not possible | [State Mappings](state-mappings.md) | | Machine confirmation timeout | Configure `MachineReplyTimeout` and verify that a missing confirmation fails and rolls back **Track In**, **Track Out**, or **Abort** | [OPC UA Server Settings](opcua-connection.md#automation-timeout-settings) | | Hybrid initiation | Enable the MES operation event path and ensure the machine monitors `MESOperationPerformed` even when it did not raise `MachineOperationRequest` | [Operation Handshake](../features/operation-handshake.md) | ## Validation Validate every enabled feature, including its normal path, failure behavior, timeout, reset, restart, and applicable initiation modes, by following [Validate and Go Live](../commissioning-and-support/validation-and-go-live.md).