Relevant Artifacts#
The OPC UA Standard combines reusable Industrial Equipment capability with project-specific MES, Connect IoT, network, security, and machine artifacts. This page summarizes what the package provides, what each implementation must create, and what should be retained at handover.
Exact packaged names may vary between compatible Industrial Equipment releases. Use the installed package as the source for internal implementation names; the responsibilities and configuration contract described here remain consistent.
Implementation Responsibility#
| Area | Delivered capability | Project-specific artifact | Configured or implemented by |
|---|---|---|---|
| MES Resource model | Industrial Equipment properties and attributes used by the integration | Resource instances, hierarchy, state model, automation settings, and eligibility | MES implementation team |
| MES production process | Runtime integration with standard MES operations, Recipe resolution, Data Collection, and Resource states | Products, flows, steps, Recipes, Data Collections, contexts, and state mappings | MES implementation team and process owner |
| Connect IoT | OPC UA Standard controller and driver capability | Automation Manager assignment, Automation Controller Instances, runtime settings, and operational ownership | Solution administrator |
| OPC UA connection | Profile-selection and connection contract | Endpoint, namespace, credentials, certificates, trust, permissions, and optional Resource-specific profiles | Automation and infrastructure teams |
| Machine interface | Standard OPC UA node and handshake contract | OPC UA Server, Resource node tree, machine-specific parameters, and PLC or machine-application logic | Machine supplier or customer automation team |
| Validation and operation | Expected feature, timeout, rollback, reset, and recovery behavior | Test evidence, operating procedures, monitoring, escalation, and support ownership | MES Implementation team |
Delivered Industrial Equipment Capability#
| Delivered area | Capability |
|---|---|
| OPC UA controller and driver definitions | Establish the OPC UA communication path and associate the standard automation behavior with an MES Resource |
| Delivered runtime logic | Performs setup, operation handshakes, Recipe Download, Data Collection, State Synchronization, value conversion, timeout handling, rollback coordination, and diagnostics |
| MES integration logic | Invokes the applicable MES operations and returns the data required to continue the OPC UA interaction |
| Fixed automation contract | Defines the operation, Data Collection handshake, and State nodes documented in Node Reference |
| Dynamic parameter resolution | Resolves Recipe and Data Collection nodes from the actual MES Parameter names instead of delivering machine-specific placeholder parameters |
The following delivered configuration and master-data artifacts form the stable project configuration contract:
| Artifact | Scope | Purpose |
|---|---|---|
EnableAutomationScenarios | Resource property | Enables MES-to-machine automation behavior when set to true |
Recipe Management Enabled | Resource property | Enables Recipe resolution and download during Track In |
IndEqOpcUaBaseNodeId | Resource attribute | Stores the generated fully qualified Resource base NodeId |
IndEqAutomationOperationAllowFIFO | Resource attribute | Controls whether an operation may resolve the first eligible Material when the name is omitted |
IndEqOpcUaParameterDataType | Parameter attribute | Defines the OPC UA conversion type for a Recipe or Data Collection Parameter |
IndEqOpcUaDataTypes | Lookup Table | Provides the supported values for IndEqOpcUaParameterDataType |
IndEqResourceStateResolution | Smart Table | Maps machine main and optional substate values when direct MES state-name matching is not possible |
| OPC UA Server profiles | Configuration | Provide either the complete Default profile or a complete Resource-specific profile |
| Automation timeouts | Configuration | Define the MES-to-Connect-IoT request timeout and the machine-confirmation timeout |
Connection fields, paths, defaults, and profile selection are defined canonically in Configure the OPC UA Connection. Resource and Parameter settings are defined in Configure MES and the Resource.
Standard MES Artifacts to Configure#
The package uses standard MES objects but does not create the project production model. Configure the applicable artifacts before enabling their related features.
| MES artifact | Project use |
|---|---|
| Equipment hierarchy and Resource | Represent the physical equipment, provide its hierarchy identity, and hold the integration settings |
| Resource state model | Define valid states, transitions, reasons, and the current Resource state |
| Material, Product, Flow, Step, and Resource eligibility | Provide the context used to validate Track In, Track Out, and Abort |
| Recipe, Recipe Context, subrecipes, and Parameters | Resolve the process settings downloaded to the machine |
| Data Collection Definition, Material Data Collection Context, readings, and Parameters | Define and store the process-relevant readings posted by the machine |
| MES users, roles, and permissions | Authorize configuration, operation execution, diagnostics, and support activities |
Connect IoT Runtime Artifacts#
| Runtime artifact | Project action |
|---|---|
| Automation Manager | Select and operate the runtime environment that hosts the equipment connection |
| Automation Controller Instance | Create one instance that associates the MES Resource with the delivered OPC UA Standard Controller |
| OPC UA session and subscriptions | Verify that runtime setup creates the session and subscribes to the nodes required by the enabled features |
| Execution history and diagnostics | Retain the information required to investigate setup, operation, Data Collection, and State Synchronization failures |
See Configure Connect IoT for the setup procedure.
Machine-Side Deliverables#
| Machine artifact | Required responsibility |
|---|---|
| OPC UA Server | Expose a reachable endpoint with the agreed identity, security, trust, and node permissions |
| Resource base node and standard folders | Expose the approved Resource hierarchy and the applicable Operation, Recipe, DataCollection, and State structures |
| Machine-specific Recipe and Data Collection nodes | Use the actual MES business Parameter names; placeholder names such as Parameter1 are examples only |
| PLC or machine-application logic | Own request and confirmation values, consume MES outputs and Recipes, publish Data Collection and State values, and reset handshakes |
| Machine security assets | Supply the required server certificate, trust configuration, and authorization for the Connect IoT client identity |
Exclusions#
The Industrial Equipment package provides a reusable interface and runtime implementation, not a commissioned machine integration. It does not provide:
- the machine OPC UA Server, node tree, or PLC and machine-application logic.
- the project-specific production model, Recipes, Data Collections, state model, or state-mapping rows.
- endpoint values, credentials, certificates, trust entries, network access, or machine permissions.
- project Automation Manager assignments or Automation Controller Instances.
- commissioning evidence, recovery procedures, operational monitoring, or support ownership.