Configuration Guide#
Purpose#
This section is the implementation runbook for getting a machine connected and operational. It is intentionally generic: it identifies what must be configured and verified without assuming a specific machine builder, OPC UA Server, network topology, or production process.
Configuration is complete only when all four layers agree:
- the MES manufacturing model identifies what can be produced and how.
- the Resource settings identify how the machine is integrated.
- Connect IoT OPC UA Client can communicate and execute the documented processes.
- the machine exposes and implements the agreed OPC UA contract.
Configuration Map#
| Phase | Main outcome | Detailed page |
|---|---|---|
| MES modeling | Resource, hierarchy, flows, recipes, data collections, and state model support the intended process | MES Modeling |
| Resource configuration | Resource native and Industrial Equipment settings are correct | Configure MES and the Resource |
| Machine contract | Fixed nodes, dynamic parameters, data types, ownership, and behavior are agreed | OPC UA Address Space |
| OPC UA connection | Endpoint, identity, security, certificates, profile, base node, namespace, and access work | Configure the OPC UA Connection |
| Connect IoT | The Resource connection, Automation Manager, runtime process, profile selection, OPC UA session, and subscriptions are operational | Configure Connect IoT |
| Features | Operations, Recipe, Data Collection, State, FIFO, and hybrid behavior are configured as required | Configure the Features |
| Acceptance | Normal, failure, missing-acknowledgement, restart, and recovery scenarios pass with evidence | Validate and Go Live |
Who Configures What#
| Owner | Responsibilities |
|---|---|
| MES solution team | Configures the Resource, process eligibility, Recipe and Data Collection contexts, state model, Smart Tables, security, and representative test data |
| Infrastructure and security team | Provides network routing, DNS, firewall access, certificates, credentials, trust configuration, and ownership of secrets and certificate renewal |
| Machine and automation team | Implements the OPC UA Server, Resource node tree, PLC handshake, node data types, access rights, and machine-side recovery behavior |
| Business and process owner | Approves Material selection, FIFO usage, operation behavior, Recipe and process-data requirements, and business acceptance scenarios |
The exact setting names and paths are consolidated in the settings reference below.
Settings Reference#
Settings are grouped by ownership:
| Group | Scope |
|---|---|
| OPC UA Server Settings | Profile selection, namespace, endpoint, authentication, security, certificates, and automation timeouts |
| Resource Settings | Base node, FIFO, and automation and Recipe enabling properties |
| Parameter Settings and Naming | Parameter data types, OPC UA node names, and conversion rules |
| State Mappings | Machine-to-MES Resource state resolution |
Configuration entries are stored under /IndEq/Automation/. Resource attributes and properties are maintained on MES business objects. Treat secret values and private keys according to the deployment security policy.
Only settings explicitly documented in this section are part of the OPC UA Standard configuration contract.