Search

Scope: Core (OPC-10000-*) All specs

75 result(s) for Connections

OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.3.7.3 PubSubConfigurationRefDataType

referencing, it shall be set to 0. ConnectionIndex UInt16 Specifies the index within the Connections array of the PubSubConfiguration if the connection, group, reader or writer bits
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

1 Scope

configuration/parameterisation data (non-safety and safety) using OPC UA PubSub in combination with UAFX Connections and basic diagnostics. A future version of the UAFX specifications is expected to address other
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

3.1.5 ConnectionManager

ConnectionManager entity that interacts with AutomationComponents to establish Connections between FunctionalEntities Note 1 to entry: See OPC 10000-81 for a description of the ConnectionManagerType
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

5.4.1 General

General UAFX defines a mechanism for standardising the exchange of information used for establishing Connections between AutomationComponents (see 6.2 ) in an OfflineEngineering environment (see 6.4 ). From initial AutomationComponent development
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

5.4.3 Application engineering

engineering tool and adds the information needed for Controller A and B Connections . Engineer B may import additional Descriptors describing components used with their Controller or other Controllers
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

5.4.6 System integration

ConnectionManager uses OPC UA Methods exposed by each AutomationComponent to establish the configured Connections when the system goes operational, as shown in Figure 8 . See clause 6.2 for more details ... Connections and the ConnectionManager . See OPC 10000-81 for more details. Figure 8 - Connection establishment
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.1 Controller-to-Controller communication

vendors to describe the Controller's assets, automation functions, and a standard interface for Connections that provides interoperability for exchanging data. AutomationComponents, Assets, and FunctionalEntities also include identification information, allowing ... compatibility to be verified for each Connection . This release of the UAFX specification defines Connections using OPC UA PubSub for data exchange, including the usage of TSN. Connections using
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.2 UAFX Information Model

data information. Future releases are planned to include the exchange of event information. Connections are mapped to a communication model such as PubSub or Client Server and different QoS classes ... application configuration. OPC 10000-81 formally describes Connections . The ConnectionManager , described in OPC 10000-81 , is the entity responsible for establishing Connections . The ConnectionManager may be part of an AutomationComponent
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.4.1 Overview

have relationships to other FunctionalEntities . The Object Model also includes a representation of Connections (communication) between FunctionalEntities . Figure 5 - FunctionalEntity illustration FunctionalEntities are designed to describe the functionality
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.4.2 FunctionalEntityType

describes information related to the status of its functionality, including the status of any Connections . This could include the generation of Events or Alarms related to problems or issues encountered
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.6 FunctionalEntities and applications

monitoring purposes. Information related to these interactions is represented in the FunctionalEntity by Connections (see Figure 8 ). Figure 8 - Example Connection between FunctionalEntities The process of establishing a Connection
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.7.1 Overview

Overview A ConnectionManager is an optional entity that interacts with multiple AutomationComponents to establish Connections between FunctionalEntities . The ConnectionManager can execute on any Server supporting the OPC UA FX Information ... represented by the ConnectionManagerType , which defines functionality and interfaces to manage the establishment of Connections between FunctionalEntities . Several ConnectionManagers within a network could establish Connections independently of each other
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.7.2 Creating / Monitoring / Closing Connections

Creating / Monitoring / Closing Connections Connections to be created are part of a ConnectionManager configuration ( ConnectionConfigurationSet ). An AutomationComponent and the included FunctionalEntities report the status of Connections that are part ... knows when to create a Connection . respond to external or internal commands. monitor the Connections they create. Possible reasons for monitoring Connection status include: An application or ConnectionManager monitors ConnectionEndpoints
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.1 Overview

These concepts include Connection establishment and bidirectional communication. The establishment of Connections further requires concepts such as identity and compatibility verification of Asset and FunctionalEntity , establishing control via ControlGroup selection
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.1 Overview

Overview Connections between FunctionalEntities are designed to exchange data by utilising OPC UA communication models. This revision of the specification supports the PubSub communication model as defined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.2.1 Overview

Overview This clause illustrates how Connections utilise the PubSub communication model, focusing on three use cases relevant in the context of industrial automation and the design of AutomationComponents . These
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.2.3 Multiple Connections using unicast network messages

Multiple Connections using unicast network messages This use case, illustrated in Figure 13 , typically applies to AutomationComponents that host multiple FunctionalEntities and/or nested FunctionalEntities . Figure 13 - Multiple Connections using unicast ... network messages (aggregated) Figure 13 illustrates two Connections , each between two PubSubConnectionEndpoints . Each PubSubConnectionEndpoint on AC_A (and similarly on AC_B) references a DataSetWriter (and DataSetReader) that is located
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.2.5 DataSetMetaData

DataSetMetaData Connections are configured by an engineering tool on behalf of Descriptors and are deployed to a ConnectionManager (see 5.5.2 ). Independent of the lifetime of a Connection, another engineering tool
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.7 AliasNames and OPC UA FX

actual configuration is available. They can be exchanged between vendors, allowing vendors to configure Connections without having all the required data defined. The resolution of this configuration information into
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.9 Well Known Roles

BrowseName Suggested Permissions 3:ConnectionAdmin The Role is allowed to establish, close, and modify Connections between FunctionalEntities . This includes reading and writing connection configuration settings, reading endpoint and connection capabilities ... executing methods related to the management of Connections . It is intended to be a non-human Role . For a detailed description of Roles
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.1 Overview

FunctionalEntities in a given model. It exposes a Method that is used to establish Connections between FunctionalEntities . An overview of the AutomationComponentType is illustrated in Figure 18 . Figure 18 - AutomationComponentType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.2 AutomationComponentType definition

AutomationComponentCapabilitiesType Folder that describes the functionality provided by an AutomationComponent (e.g., number of supported Connections , etc.). The optional ConformanceName provides the URL to the product's listing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.1 Overview

Overview The EstablishConnections Method establishes one or more Connections . The ConnectionManager typically calls it. It allows for creating ConnectionEndpoints , establishing control, verifying FunctionalEntity and Asset compatibility, applying ConfigurationData , and configuring ... used for data exchange. It is recommended that this Method be restricted to Client connections that have the well-known Role ConnectionAdmin as defined in Clause
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.2 EstablishConnections signature

AssetVerifications shall be null or empty. ConnectionEndpointConfigurations Provides configuration information for Connections . For a formal definition of the ConnectionEndpointConfigurationDataType, see 10.14 . If CommandMask VerifyFunctionalEntityCmd , CreateConnectionEndpointCmd , EstablishControlCmd , SetConfigurationDataCmd , ReassignControlCmd , SetCommunicationConfigurationCmd ... empty. CommunicationConfigurations Provides the ConfigurationData specific to the communication model utilised by the provided Connections . For a formal definition of the CommunicationConfigurationDataType , see 10.10 . If CommandMask SetCommunicationConfigurationCmd is set, CommunicationConfigurations
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.5.1 CloseConnections signature

CloseConnections signature This Method disables one or more Connections . Optionally, it also removes these Connections . It is recommended that this Method has the execute privilege for the well-known Role ... StatusCode[] Results ); Table 22 - CloseConnections Method arguments Argument Description ConnectionEndpoints The list of Connections to be closed. Remove When TRUE, the Objects dynamically created for the Connection are removed. Results
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.6 AutomationComponentCapabilitiesType

rules associated with an OptionalPlaceholder. The optional SupportsPersistence indicates whether this AutomationComponent supports persistent Connections. For additional details on persistence, see 6.6 . If this capability is not present ... FALSE, the AutomationComponent does not support persistent Connections. The optional MaxFunctionalEntities indicates the maximum number of FunctionalEntities that the AutomationComponent can support . The optional MaxConnections indicates the maximum number
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.7 PublisherCapabilitiesType

part of the AutomationComponent . When the preconfigured PublishedDataSet is used in a ConnectionConfigurationSet , Connections shall be established to one or more of the FunctionalEntities whose variables are present
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.8 SubscriberCapabilitiesType

part of the AutomationComponent . When the preconfigured StandaloneSubscribedDataSet is used in a ConnectionConfigurationSet , Connections shall be established to one or more of the FunctionalEntities whose variables are present
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.7 FunctionalEntityCapabilitiesType

present and set to TRUE, the FunctionalEntity requires a feedback signal for all Connections . A feedback signal is represented by the reception of either data or a heartbeat. The following
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.2 ConnectionEndpointType definition

Established control on related ControlGroups Communication model Objects An AutomationComponent indicates support for persistent Connections ; see SupportsPersistence in 6.2.6 . Non-persistent ConnectionEndpoints following a power cycle behave
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.3 PubSubConnectionEndpointType definition

empty String . Annex E provides examples of PubSubConnectionEndpoints for the various types of Connections
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.1 Overview

ConnectionManager uses the configuration data stored in a ConnectionConfigurationSet (see 6.8 ) to establish Connections . Optional Methods are provided by ConnectionManagerType to allow Clients to manage editing and trigger the processing ... Connections . A ConnectionManager is represented by an instance of ConnectionManagerType ; see 12 for details on its location in the UAFX Information Model . Figure 34 - ConnectionManagerType illustration ConnectionConfigurationSets may be serialised
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.2 ConnectionManagerType definition

only instances of ConnectionConfigurationSetType, which provide the data required by a ConnectionManager to establish Connections . This Folder may also contain other Folders that can be used to organise the ConnectionConfigurationSets ... more ConnectionConfigurationSets in a single Call . ProcessConnectionConfigurationSets causes the ConnectionManager to manage Connections contained in one or more ConnectionConfigurationSets in a single Call (see 6.7.5 ). In addition, vendor-specific means
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.3.2 Establishing Connections

Establishing Connections To establish Connections defined in a ConnectionConfigurationSet , the ConnectionManager shall use the sequence of Calls illustrated in Figure 36 to the EstablishConnections Method on the involved AutomationComponents ... establish ConnectionEndpoints on an AutomationComponent . The Method allows for the establishment of multiple Connections with a single Call . The number of Connections to be established with a single Call
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.3.3 Closing Connections

Closing Connections To close Connections defined in a ConnectionConfigurationSet , a ConnectionManager shall use the CloseConnections Method on the AutomationComponents (see 6.2.5 ). A ConnectionManager may remove or disable the Connections ... CloseConnections returns any error, the ConnectionManager shall complete closing all Connections in the ConnectionConfigurationSet and initiate a ProcessingToError transition in the ConnectionConfigurationSetStateMachine (see 6.9 ). If any of the ConnectionEndpoints require
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.5.1 Overview

requested ConnectionConfigurationSets according to the specified Action : ActionEstablishConnectionsEnabled , ActionEstablishConnectionsDisabled , and ActionEstablishConnections - establish all Connections contained in the ConnectionConfigurationSets (see 6.7.5.3 ) ActionRemoveConnections - disable and remove all Connections contained in the ConnectionConfigurationSets ... ActionEnableConnections - enable the communication model for all Connections contained in the ConnectionConfigurationSets (see 6.7.5.3.3 ) ActionDisableConnections - disable the communication model for all Connections contained in the ConnectionConfigurationSets
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.5.3.1 ActionEstablishConnectionsEnabled / ActionEstablishConnectionsDisabled / ActionEstablishConnections

ActionEstablishConnections Calling ProcessConnectionConfigurationSets with Action set to ActionEstablishConnectionsEnabled , ActionEstablishConnectionsDisabled , or ActionEstablishConnections shall establish the Connections contained in the ConnectionConfigurationSets and their related communication model. Establishing connections shall follow the behaviour ... requested Action as follows: Calling ProcessConnectionConfigurationSets with Action set to ActionEstablishConnectionsEnabled shall establish all Connections contained in the ConnectionConfigurationSets with a disabled communication model and include EnableCommunicationCmd in the command
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.5.3.2 ActionRemoveConnections

ActionRemoveConnections Calling ProcessConnectionConfigurationSets with Action set to ActionRemoveConnections shall remove all Connections contained in the ConnectionConfigurationSets and their related communication model. For each ConnectionConfigurationSet , the ConnectionManager shall call the CloseConnections
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.5.3.3 ActionEnableConnections

ActionEnableConnections Calling ProcessConnectionConfigurationSets with Action set to ActionEnableConnections shall enable all Connections contained in the ConnectionConfigurationSets . For each ConnectionConfigurationSet , the ConnectionManager shall call the EstablishConnections Method, containing the EnableCommunicationCmd
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.5.3.4 ActionDisableConnections

ActionDisableConnections Calling ProcessConnectionConfigurationSets with Action set to ActionDisableConnections shall disable all Connections contained in the ConnectionConfigurationSets . For each ConnectionConfigurationSet , the ConnectionManager shall call the CloseConnections Method (see 6.2.5 ) with Remove
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.6 ConnectionManagerCapabilitiesType

capability of the ConnectionManager Information Model to report the status of all the Connections created by this ConnectionManager that have a ConnectionEndpoint on this Server. If this capability ... provided, or false, the ConnectionManager Information Model does not report the current status of Connections. NOTE In some cases, this status might include the status of the remote Connection . MonitorsAllConnectionEndpoints
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.8.1 Overview

Overview The ConnectionConfigurationSetType is an ObjectType representing one or more Connection configurations. Connections are grouped in a set, for example, to allow sharing communication model configurations by multiple Connections ... expose the ConnectionConfigurationSets in its AddressSpace . A ConnectionConfigurationSet exposes diagnostic information about the Connections as part of its Information Model . It also allows Connection configurations to be available for modification
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.8.2 ConnectionConfigurationSetType definition

occurs during the Connection establishment sequence, establishing the set shall stop, and all established Connections that are part of this set shall be closed (see 6.7.3.2 ). It is recommended that ... ConnectionConfigurationSet by having a different NodeId . ConnectionsDiagnostics provides an array of diagnostic information for Connections included in this ConnectionConfigurationSet . There shall be one element in this array for each
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.9.1 Overview

machine is defined as a mechanism to coordinate actions executed internally (a ConnectionManager establishing Connections ) that involve the processing of a ConnectionConfigurationSet . The States and Transitions that comprise the state
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.9.2 ConnectionConfigurationSetStateMachineType definition

this State indicates that it is currently being processed by the ConnectionManager (i.e., Connections are being established). Internals of the processing executed in this State are described in 6.7.5.3 . Error ... vendor-specific means. While in State Processing , the ConnectionManager establishes or closes the Connections contained in the ConnectionConfigurationSet ; for details, see 6.7.5.3 . ProcessingToReady - This transition shall be initiated
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.13.2 CommunicationFlowConfigurationType definition

ConnectionManager Base PubSubCommunicationFlowConfigurationType indicates the usage of PubSub as the communication model for the Connections . It is formally defined in 6.13.3 . ClientServerCommunicationFlowConfigurationType may be defined in a future release ... indicate the usage of Client Server as the communication model for the Connections
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.14.2 AutomationComponentConfigurationType definition

UAFX ConnectionManager Base AutomationComponentNode specifies the AutomationComponent that is to be used for establishing Connections . If a PortableRelativePath is specified, the path shall be relative to FxRoot . CommandBundleRequired , when TRUE ... CommunicationModelConfig provides the ConfigurationData specific to the communication model utilised by the Connections
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.16.1 Overview

CommunicationModelConfigurationType ObjectType provides the configuration data specific to the communication model utilised by the Connections . The CommunicationModelConfigurationType is illustrated in Figure 47 . Figure 47 - CommunicationModelConfigurationType illustration PubSubCommunicationModelConfigurationType provides the configuration ... data specific to the usage of PubSub as the communication model for the Connections . It is formally defined in 6.16.3 . ClientServerCommunicationModelConfigurationType indicates the usage of Client Server as the communication
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.16.3.2 PubSubCommunicationModelConfigurationType definition

PubSubCommunicationModelConfiguration The PubSubConfiguration modifies the existing PubSub configuration on the addressed Server when establishing Connections . The PubSubConfiguration2DataType is defined in OPC 10000-14 . Namespaces contains namespace URIs for NamespaceIndex used ... identifiers in the PubSubConfiguration . OPC UA FX allows multiple ConnectionManagers to establish Connections to a single AutomationComponent independently of each other. It also allows any Client to establish Connections
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

9.2.1 Overview

describes the attributes to be applied to open secure communication to the Server . Multiple Connections may refer to the same instance of ServerAddressType . The ServerAddressType is illustrated in Figure
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.19 ConnectionDiagnosticsDataType

remaining bits to indicate the kind of processing that has just finished. For all Connections for which all required operations were successfully finished, a ConnectionManager shall clear the Error ... NoError and shall set EndpointStatus (1 and/or 2) to Good . For all Connections for which not all operations required in the last processing were successfully finished, a ConnectionManager shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.1 Overview

functionality that a FunctionalEntity might expose. This includes Inputs , Outputs , ControlGroups and the resulting Connections . It will also describe the use of pre-configured DataSets and dynamically created DataSets
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.7.4 Using ControlGroups with Connections

D.3.7.4 Using ControlGroups with Connections ControlGroups can be used with Connections . This example is an extension of the simple ControlGroup . Assume that the EngineeringUnit of Temperature (see Figure D.28 ) should
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.2.1 Overview

E.2.1 Overview The ConnectionManager uses the information in the ConnectionConfigurationSet to establish all contained Connections . The configuration information required as input to call EstablishConnections on a particular AutomationComponent ... NOTE The interaction of the ConnectionManager with AutomationComponents to establish Client Server -based Connections will be provided in a future version of this document. If a PubSubCommunicationModelConfiguration was generated
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.1 Overview

ConnectionConfigurationSet. Note, however, that as shown in E.1.3 , a ConnectionConfigurationSet can contain multiple Connections , which could have different connection types. The examples provide illustrations of how PubSub communication
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

F.1.5 ) or within the vendor-specific download format. A ConnectionConfigurationSet might contain multiple Connections that all need to communicate as a set. In this case, the ConnectionManager and/or the engineering ... tool can also optimise communication by grouping Variables for multiple Connections into a single DataSet or into a single network message. For example, if the ConnectionConfigurationSet has three Connections between
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.5 Interaction with an SKS

push model configuration, it is recommended that the ConnectionManager establish the Connections on the AutomationComponents before updating the SKS . It is recommended to perform as much configuration as possible ... available. For a pull model configuration, it is recommended that the ConnectionManager establish the Connections on the AutomationComponents after updating the SKS . If the SKS rejects GetSecurityKeys (e.g., SecurityGroups have
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.3 ConnectionConfigurationSetConfDataType

grouping is needed, the parameter is a null or empty String array. False Connections 4:ConnectionConfigurationConfDataType[] A list of Connection configurations to be established. False CommunicationFlows 4:CommunicationFlowConfigurationConfDataType[] A list ... communication model-specific configurations to apply to Connections. True ServerAddresses 4:ServerAddressConfDataType[] A list of addressing information for AutomationComponents . False AutomationComponentConfigurations 4:AutomationComponentConfigurationConfDataType[] A list of AutomationComponents used for Connection
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.9 AutomationComponentConfigurationConfDataType

AutomationComponentNode 4:NodeIdentifier AutomationComponentNode specifies the AutomationComponent that is to be used for establishing Connections . If a RelativePath is specified, the path shall be relative to FxRoot . False AutomationComponentNodeSelection ... CommunicationModelConfig 4:CommunicationModelConfigurationDataType Provides the ConfigurationData specific to the communication model utilised by the Connections . If the optional CommunicationModelConfig is to be omitted, the field shall be set to null
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.3.3.2.3 ElementRemove

Method on all affected AutomationComponents (see 6.2.5 ) with Remove set to TRUE for all Connections contained in the ConnectionConfigurationSet
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.3.3.2.4 ElementReplace

affected AutomationComponents (see 6.2.5 ) with Remove set to TRUE for all contained Connections in the ConnectionConfigurationSet . The operation ElementReplace does not include processing the new ConnectionConfigurationSet . Processing can be triggered
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

G.1 Diagnostics Client

Connection (the side that is in the local AutomationComponent ) or it could not monitor Connections at all (see Figure G.1 ). The ConnectionManager has capabilities (see 6.7.6 ) indicating the behaviour
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.1 Overview

network containing UAFX Stations (see 6.4.3 ) and other IA-stations (see 6.4 ) such that Connections can be handled with appropriate QoS. With this release , UAFX Stations can use Best Effort
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.1 General

this clause follows the general workflow from OPC 10000-80 for the configuration of Connections between FunctionalEntity inputs and outputs. The workflow described in this clause goes into the details ... related to configuring the QoS required by those Connections . This workflow is divided into four phases: Application and QoS engineering, network configuration, system integration, and connection establishment and operation
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.2 Application and QoS engineering

final step, Connection configurations are transferred to a ConnectionManager that establishes the Connections during the workflow's connection establishment and operation phase (see 5.6.4.5 ). This subclause describes the details ... Input and output Variables in the FunctionalEntity expose the data to be exchanged using Connections with FunctionalEntities in another Controller . The Variables PublisherCapabilities and SubscriberCapabilities, also contained in the AutomationComponent
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.4 System integration

system integration phase, a System Commissioner makes the necessary adjustments to adapt the Connections and network configurations for the existing network using a generic OPC UA Client or vendor-specific
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.5 Connection establishment and operation

operation The connection establishment and operation phase begins with the ConnectionManager establishing the Connections described in its Information Model . Connection establishment is either initiated by the ConnectionManager's internal logic ... Figure 11 - PubSub QoS and addressing configuration variables The ConnectionManager establishes Connections using the Connection configuration as set up by the Controls Engineer (see 5.6.4.2 ) and System Commissioner
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

6.3 Descriptor with configuration information

subscriber capabilities, whereas non-relevant information would not be included. For configuration of the Connections , a special set of configuration information is needed that describes the ConnectionConfigurationSets . This
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

8.3.2 Descriptor Import

needs to know what data Controller A is providing or is required for the Connections . After receiving the Descriptor , Engineer B imports it into an engineering tool and uses
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.3 UAFX AutomationComponent

MaxConnections Variable in the ComponentCapabilities Folder a nd supports the claimed number of Connections . Note the actual maximum number of connections supported may be reduced during runtime due to resource ... Variable in the ComponentCapabilities Folder a nd supports at least the claimed number of Connections . Server UAFX AutomationComponent MaxFunctionalEntities Includes the MaxFunctionalEntities Variable in the ComponentCapabilities Folder and supports
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.6 UAFX ConnectionManager

File content. Server UAFX ConnectionManager Exposes CCSs Exposes a ConnectionConfigurationSet for each of its Connections . Client UAFX Client ConnectionManager VerifyAsset Is capable of issuing the VerifyAssetCmd command of the EstablishConnections
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.4.5 UAFX SKS Push 2023 Facet

Push Facet . This Facet includes the Security Key Server functionality needed for securing UAFX Connections using the push model . This Facet supersedes the UAFX SKS Push Facet . Table 44 - UAFX
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.4.6 UAFX ConnectionManager 2024 Facet

ConnectionManager 2024 Facet. This Facet includes the functionality a UAFX ConnectionManager needs to establish Connections between FunctionalEntities . This Facet supersedes the UAFX ConnectionManager Facet . Table 45 - UAFX ConnectionManager 2024 Facet
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.4.7 UAFX ConnectionManager Connection Monitoring Facet

Connection Monitoring Facet. This Facet includes the functionality needed for a ConnectionManager to monitor Connections . Table 46 - UAFX ConnectionManager Connection Monitoring Facet Group Conformance Unit / Profile Title Optional UAFX ConnectionManager
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

Agreement of Use

Feature Do we need a Conformance Unit requiring a minimum number of UAFX Connections Added UAFX AutomationComponent MinConnections CU and the new CU to the new UAFX AutomationComponent 2024 Facet ... Added CU UAFX ConnectionManager Exposes CCSs - Exposes a ConnectionConfigurationSet for each of its Connections . 9787 Errata The Base Bridge Component Facet description contains misleading text. Removed the phrase "describes