Search

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

90 result(s) for AutomationComponent

OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

3.1.2 AutomationComponent

AutomationComponent entity that performs one or more automation functions and is modelled by an AutomationComponentType Note 1 to entry: See OPC 10000-81 for a description of the AutomationComponentType
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

3.1.1 Asset

Asset Physical or logical elements of an AutomationComponent Note 1 to entry: See OPC 10000-81 for a description of Assets
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

3.1.13 FunctionalEntity

FunctionalEntity element of an AutomationComponent containing the data and methods needed to configure, control and manage functional behaviour Note 1 to entry: See OPC 10000-81 for a description
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

3.2 Abbreviated terms

Abbreviated terms 5G Fifth Generation broadband cellular network AC AutomationComponent APL Advanced Physical Layer C2C Controller-to-Controller C2D Controller-to-Device DCS Distributed Control System DHCP Dynamic Host Configuration
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

4.2 Architecture

functionality for field-level communications. The foundation of the UAFX Information Model is the AutomationComponent . The AutomationComponent is an entity representing one or more Assets that may perform automation functions ... represented by FunctionalEntities . The AutomationComponent can also provide health status. See OPC 10000-81 for more details regarding the AutomationComponent model. OPC UA FX also adds definitions for network services
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

5.3 Interaction Model

roles; however, their functionality is modelled at an abstract level in UAFX as an AutomationComponent (see 6.2 ). While capabilities specific to Compute-to-Compute are not part of UAFX, these
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

5.4.1 General

establishing Connections between AutomationComponents (see 6.2 ) in an OfflineEngineering environment (see 6.4 ). From initial AutomationComponent development to on-site commissioning, engineers exchange offline data using the Descriptor
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

5.4.6 System integration

Figure 7 - Connection commissioning The ConnectionManager uses OPC UA Methods exposed by each AutomationComponent to establish the configured Connections when the system goes operational, as shown in Figure
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.1 Controller-to-Controller communication

else. All communication partners are modelled as AutomationComponents defined in OPC 10000-81 . An AutomationComponent provides an abstract model that allows vendors to describe the Controller's assets, automation functions
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.2 UAFX Information Model

existing companion specifications, where existing definitions are merged into the UAFX Information Model . An AutomationComponent is an entity that performs one or more automation functions. All AutomationComponents are composed ... Assets and FunctionalEntities . An AutomationComponent also contains information related to communication capabilities and diagnostic information. OPC 10000-81 formally describes AutomationComponent , Asset , and FunctionalEntity . A Connection is a logical relationship
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.2 AutomationComponent model

AutomationComponent model This model is provided to model AutomationComponents in OPC UA FX. In OPC UA FX, an AutomationComponent is an entity that performs one or more automation functions
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.5 Relationships between FunctionalEntities and Assets

ReferenceTypes ). Figure 7 - Relationships between FunctionalEntities and Assets Figure 7 also illustrates an AutomationComponent , which provides a grouping of related FunctionalEntities and Assets
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.6 FunctionalEntities and applications

FunctionalEntities and applications Functionality from different FunctionalEntities (in different AutomationComponent s) can be used to construct applications. An application can involve communication between one or more FunctionalEntities . FunctionalEntities
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.7.2 Creating / Monitoring / Closing Connections

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 of the FunctionalEntity
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.2.1 Overview

engineering expectations. There are several scenarios where the verification of various properties of an AutomationComponent is utilised in an automation system: ensuring that AutomationComponents match system engineering expectations during commissioning ... missing Assets like IO modules in a modular IO system); replacing or updating an AutomationComponent or any of its subcomponents. Identity and compatibility verification can be done at any time
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.2.2.3 Asset compatibility

compatible with what was expected by system engineering. An important use case is AutomationComponent replacement. If an identical replacement (same manufacturer, model, and firmware) is unavailable, the vendor could
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.3 ControlGroups

configured by product vendors and be related to the functionality provided by the AutomationComponent (e.g., a drive vendor or function block library vendor). It could also be defined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.1 Overview

Overview The logical functionality of an AutomationComponent is represented by one or more FunctionalEntities described in 4.4 . An important part of the functional model is the data exchange between FunctionalEntities
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.3 Establishing and closing Connections

established, the ConnectionConfigurationSet includes: address information, e.g., Server address, BrowsePath to the AutomationComponent , FunctionalEntity , etc., optional parameters to be used for verifying the Assets and FunctionalEntities , optional parameters
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.4.2 Operation

Operation The lifetime of a logical connection on an AutomationComponent can be tied to its Status (see 6.6.2 ), which is, in turn, tied to the reception of data or heartbeat
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.5 Persistent and preconfigured objects

restart. Individual logical connections can be marked for persistence (see IsPersistent in 6.6.2 ) . An AutomationComponent can provide preconfigured Objects (e.g., PublishedDataSet or ConnectionEndpoint ). An example might be a FunctionalEntity that
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.2.4 Multiple Connections using multicast network messages

network messages This use case, illustrated in Figure 14 , could be applied to an AutomationComponent (AC_A) communicating with multiple AutomationComponents (AC_B and AC_C). To minimise network bandwidth
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.6 Health

objects to parent objects (e.g., from ConnectionEndpoints to the FunctionalEntity , from FunctionalEntities to the AutomationComponent , or from ConnectionConfigurationSets to the ConnectionManager ). The aggregated health status allows a Client to easily
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.8 Aggregation of OPC UA FX Servers

aggregated. This clause provides some explanation regarding the aggregation of AutomationComponents and ConnectionManagers . The AutomationComponent(s) can be reflected in a higher-level Server . This reflection can include Assets ... exist in the actual Servers , not in the AggregatingServer . Any actions performed against the AutomationComponent in the AggregatingServer are expected to be passed down and performed on the actual Server
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.2 AutomationComponentType definition

LogObjectType O 0:GeneratesEvent ObjectType 0:SystemStatusChangeEventType Defined in OPC 10000-3 ConformanceUnits UAFX AutomationComponent Base Table 5 - AutomationComponentType additional References SourceBrowsePath Reference Type IsForward TargetBrowsePath 3:FunctionalEntities ... UInt32 0:BaseDataVariableType O FunctionalEntities provides a Folder for the FunctionalEntities that this AutomationComponent exposes. The Folder shall be restricted to hold only instances of a type derived from FunctionalEntityType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.3 AcDescriptorType definition

FxVersion 0:PropertyType O 0:HasComponent Object 3:DescriptorFile 0:FileType O ConformanceUnits UAFX AutomationComponent Descriptor The optional DescriptorIdentifier provides a globally unique identifier of the Descriptor of the AutomationComponent ... Marketplace). The optional DescriptorVersion provides the version of the Descriptor used to describe this AutomationComponent . The optional DescriptorFile exposes the Descriptor (defined in OPC 10000-83 ) directly from the AutomationComponent
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.2 EstablishConnections signature

combination of command bits set in CommandMask cannot be processed in the AutomationComponent's current state. Bad_TooManyOperations The requested number of Connections to establish exceeds the MaxConnectionsPerCall capability ... AutomationComponent (see 6.2.6 ). Uncertain The Method was aborted due to errors while executing a command. Depending on the executed commands, one or more of the AssetVerificationResults , ConnectionEndpointConfigurationResults , ReserveCommunicationIdsResults, and CommunicationConfigurationResults
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.3.1 Overview

error, and the EstablishConnections Method Call shall be aborted, as described in 6.2.4.3.11 . An AutomationComponent may support individual commands in EstablishConnections Method Calls or may require that certain commands ... bundled in a single EstablishConnections Method Call . If an AutomationComponent requires bundled commands, the CommandBundleRequired capability shall be provided and set to TRUE (see 6.2.6 ). The set of bundled commands
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.3.9.2 PubSub

described in 6.2.4.3.11 . If communication configuration exceeds capabilities ( PublisherCapabilities , SubscriberCapabilities or ComponentCapabilities ) of the AutomationComponent , FunctionalEntities , InputData or OutputData , or if communication configuration cannot be applied, Bad_ConfigurationError shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.6 AutomationComponentCapabilitiesType

BaseDataVariableType O 3:HasCapability Variable 3:CommandBundleRequired 0:Boolean 0:BaseDataVariableType O ConformanceUnits UAFX AutomationComponent Base <Capability> - is an OptionalPlaceholder (defined in OPC 10000-3 ) to indicate that ... 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
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.7 PublisherCapabilitiesType

BaseDataVariableType M 0:HasComponent Variable 3:PreconfiguredDataSetOnly 0:Boolean 0:BaseDataVariableType M ConformanceUnits UAFX AutomationComponent PublisherCapabilities Base SupportedPublishingIntervals provides the supported intervals for publishing. An empty array indicates that ... this FunctionalEntity and its sub- FunctionalEntities . If the PublisherCapabilities is referenced from an AutomationComponent , a preconfigured PublishedDataSet shall only reference OutputVariables from FunctionalEntities that are part of the AutomationComponent . When
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.8 SubscriberCapabilitiesType

BaseDataVariableType M 0:HasComponent Variable 3:PreconfiguredDataSetOnly 0:Boolean 0:BaseDataVariableType M ConformanceUnits UAFX AutomationComponent SubscriberCapabilities Base SupportedPublishingIntervals provides the intervals for publications, which this Subscriber is able to receive ... from the FunctionalEntity and its sub- FunctionalEntities . If the SubscriberCapabilities is referenced from an AutomationComponent , a preconfigured StandaloneSubscribedDataSet shall only reference InputVariables from FunctionalEntities that are part of the AutomationComponent
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.2 FxAssetType definition

show relationships between Assets , within Assets , and between Assets and FunctionalEntities and the overall AutomationComponent model (see 11.1 ). The FxAssetType is formally defined in Table 29 . Table 29 - FxAssetType definition ... both shall be provided for Assets listed directly in the Assets Folder of the AutomationComponent . " RevisionCounter is an incremental counter indicating the number of times the configuration data within
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.3 VerifyAsset method

mandatory for top-level Assets (those directly in the Assets Folder in the AutomationComponent ). All optional Variables of AssetCompatibility are optional. ExpectedAdditionalVerificationVariables An array of NodeIdValuePair containing additional verification Variables
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.2 FunctionalEntityType definition

PublisherCapabilities for the FunctionalEntity shall describe additional restrictions of the PublisherCapabilities defined in the AutomationComponent . It can also be further restricted by the PublisherCapabilities provided in OutputData ... empty array, then it shall not change the settings defined in the AutomationComponent (or FunctionalEntity if defined in a sub- FunctionalEntity ). The optional SubscriberCapabilities provide the Subscriber capabilities associated with
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.2 ConnectionEndpointType definition

shall be persistent. Persistent ConnectionEndpoints shall be restored following a power cycle by the AutomationComponent . The restoration of a persistent ConnectionEndpoint shall include: ConnectionEndpoint including references to ControlGroups and communication ... model Objects 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.7.2 ConnectionManagerType definition

would be logged. To facilitate tracking of LogRecords between the ConnectionManager and an AutomationComponent , the ConnectionManager shall provide the SpanContextDataType as part of the EstablishConnection Method Call to each AutomationComponent
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.3.2 Establishing Connections

ConnectionConfigurationSet example The EstablishConnections Method (see 6.2.4 ) is used to establish ConnectionEndpoints on an AutomationComponent . The Method allows for the establishment of multiple Connections with a single Call . The number ... Connections to be established with a single Call may be restricted by the addressed AutomationComponent as indicated by MaxConnectionsPerCall (see 6.2.6 ). The Method provides several commands (see 10.23 ) to verify
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.8.2 ConnectionConfigurationSetType definition

AutomationComponentConfiguration (see 6.14 ). The ServerAddress provides the Connection information to address the referenced AutomationComponent . The ToConnectionEndpointConfiguration Reference is used to link an AutomationComponentConfiguration to ConnectionEndpointConfigurations (see 6.11 ). The ToOutboundFlow Reference
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.14.1 Overview

Overview The AutomationComponentConfigurationType ObjectType holds the information to be used for locating an AutomationComponent within a Server . The AutomationComponentConfigurationType is illustrated in Figure 45 . Figure 45 - AutomationComponentConfigurationType illustration
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.14.2 AutomationComponentConfigurationType definition

HasComponent Object 4:CommunicationModelConfig 4:CommunicationModelConfigurationType O ConformanceUnits UAFX ConnectionManager Base AutomationComponentNode specifies the AutomationComponent that is to be used for establishing Connections . If a PortableRelativePath is specified, the path ... FxRoot . CommandBundleRequired , when TRUE, specifies that the ConnectionManager shall bundle commands to this AutomationComponent . AssetVerification holds the Asset verification parameters for an Asset associated with this AutomationComponent . The AssetVerificationType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.16.3.2 PubSubCommunicationModelConfigurationType definition

PublishedVariable of PublishedVariableDataType or TargetNodeId of FieldTargetDataType ), the path shall start at the hosting AutomationComponent . ConfigurationReferences points to elements within the PubSubConfiguration and indicates whether they are to be added ... 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 . An AutomationComponent may even
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.19 ConnectionDiagnosticsDataType

Connections in the set, e.g. failure to verify Assets on a single AutomationComponent affects all Connections that have ConnectionEndpoints in that AutomationComponent . Finally, some failures affect only single ConnectionEndpoints
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.20 ConnectionStateEnum

both ConnectionEndpoints have been removed (e.g., due to ConnectionEndpoint auto-cleanup or AutomationComponent power-cycle). ConnectionStateEnum combines the Status of all ConnectionEndpoints participating in a Connection (see 10.20 ). For Connection
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.38 RelatedEndpointDataType

starts at FxRoot . ConnectionEndpointName 0:String The name of the ConnectionEndpoint . In case an AutomationComponent does not expose ConnectionEndpoints in its Information Model , ConnectionEndpointName is set to null. A RelatedEndpointDataType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.43.4 PubSubReserveCommunicationIds2DataType

Boolean Set this to TRUE to request transport profile-specific information from the AutomationComponent . For UDP-UADP, if this is set to TRUE, the AutomationComponent shall return the UDP port ... False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 2:PubSubReserveCommunicationIdsDataType ConformanceUnits UAFX AutomationComponent Base UAFX ConnectionManager Base
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.44.4 PubSubReserveCommunicationIdsResult2DataType

profile-specific information needed by the ConnectionManager to create a valid PubSubConfiguration for an AutomationComponent . If transport-specific information was requested for UDP-UADP, this field shall contain ... port number used by the addressed AutomationComponent for receiving UDP unicast traffic, encoded as UInt16. If transport-specific information was not requested, or if AutomationComponent has no transport-specific info
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

12.2 FxRoot

world of a physical Controller , there would only be one instance of an AutomationComponent . In the world of digital twins, there might very well be multiple instances that represent each
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

14.1 Namespace metadata

namespace metadata for this document. Table 254 defines DataTypes that are shared between the AutomationComponent and the ConnectionManager . Table 255 defines the namespace associated with an AutomationComponent . Table 256 defines ... StaticNodeIdTypes 0:IdType[] 0 StaticNumericNodeIdRange 0:NumericRange[] 0:15000 StaticStringNodeIdPattern 0:String Table 255 - AutomationComponent NamespaceMetadata Object Attribute Value BrowseName 3: http://opcfoundation.org/UA/FX/AC / Property DataType Value NamespaceUri 0:String
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

14.2 Handling of OPC UA namespaces

opcfoundation.org/UA/FX/Data / Namespace for common DataType that are shared between a ConnectionManager and an AutomationComponent . Mandatory http://opcfoundation.org/UA/FX/AC / Namespace for NodeIds and BrowseNames defined in the AutomationComponent -related part ... considered an OPC UA FX Server, a Server shall support either the AutomationComponent or the ConnectionManager. Optional http://opcfoundation .org/UA/FX/CM/ Namespace for NodeIds and BrowseNames defined in the ConnectionManager -related
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

A.1 Namespace and identifiers for OPC UA FX Information Model

/UA/FX/Data/ http://opcfoundation.org/UA/FX/AC/ http://opcfoundation.org/UA/FX/CM/ depending on whether it is common data, AutomationComponent , or ConnectionManager -related. Online documentation for the NamespaceUris can be found as follows For Data ... related, here à Will be provided at release time For AutomationComponent-related, here à Will be provided at release time For ConnectionManager-related, here à Will be provided at release
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.2.1 Extending an existing type

instance as described in the companion specification, but it would also require the AutomationComponent instance that is required by UA FX. This AutomationComponent instance would just reference the existing MyModelInstance
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.4 Parallel use of OPC UA FX and existing UA models

independent models. This is illustrated in Figure B.7 . In the illustration, an AutomationComponent was created and populated with a FunctionalEntity as well as an instance of FxAssetType . The FunctionalEntity organizes
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.1 Overview

Information Model . This includes individual Assets examples, individual FunctionalEntity examples and examples of an AutomationComponent that includes both Assets and FunctionalEntities
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.2.4 Verifying Assets

also be used to verify Assets that might not be directly linked to the AutomationComponent , i.e., they are not in the Assets folder but only referenced from existing Assets
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.4.1 Raspberry Pi example

D.4.1 Raspberry Pi example Figure D.34 provides an illustration of a full AutomationComponent . It omits some instances in nested Objects . This example links the Asset illustrated in D.2.2 ... shows the IsExecutingOn Reference between the MyApplicationProgram FunctionalEntity and the MyRaspberryPiInstance Asset. Figure D.34 - AutomationComponent example Figure D.35 provides a zoomed-in view of the AutomationComponent MyRaspberryPiAC. It illustrates
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.2.1 Overview

contained Connections . The configuration information required as input to call EstablishConnections on a particular AutomationComponent can be retrieved by following the References starting at each of the AutomationComponents listed ... secure Session based on the information contained in the ServerAddress (see 13.3.2 ) for each AutomationComponent . The ConnectionManager must resolve all PortableNodeIdentifiers contained in the configuration information (see 13.3.3 ). NOTE
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.2.2.1 For logical connections between two AutomationComponents

Publisher and its corresponding Subscribers . However, unique IDs could be generated by the addressed AutomationComponent and are not known by the ConnectionManager beforehand. OPC 10000-14 provides two ways ... generating unique IDs by the AutomationComponent , either by providing a null ID when configuring PubSub or by reserving IDs. Assuming a simple example, where a ConnectionManager processes a ConnectionConfigurationSet containing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.2.2.2 For logical connections between multiple AutomationComponents

this scenario, six Calls are needed in total (2 Calls per AutomationComponent ). The Calls to different AutomationComponents can be issued in parallel. If all logical connections are related ... AutomationComponent in our sample, this would be AC1. The sequence could be optimised as follows: The ConnectionManager calls EstablishConnections on AC1 using the ReserveCommunicationIdsCmd to reserve WriterGroupIds and DataSetWriterId
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.1 Overview

E.10 - Configuring PubSub CommunicationModelConfig contains the PubSub configuration elements to be applied to the AutomationComponent . The ConnectionManager uses the configuration information in Flow1 and Sub1 to update the communication model
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

provided in UAFX as part of a FunctionalEntity or as part of an AutomationComponent . For this version of the document, it is recommended to provide preconfigured DataSets as part ... FunctionalEntity . Use cases for DataSets as part of an AutomationComponent could be added in a later version of this document. When establishing communication, the DataSet and the Publisher's DataSetMetaData
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.5 Interaction with an SKS

side (i.e., the SKS) and the key usage side (i.e., Publisher, Subscriber ). If an AutomationComponent calls GetSecurityKeys on the SKS or an SKS calls SetSecurityKeys on the AutomationComponent with ... specific SecurityGroupId , all WriterGroups and DataSetReaders utilising the SecurityGroupId on the AutomationComponent will get the new set of keys. PubSubKeyPushTargets are used on the SKS to manage the distribution
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.1 Overview

using PubSub as a communication model, the ConnectionConfigurationSet contains a PubSubConfiguration Variable for each AutomationComponent's CommunicationModelConfig that has a DataType that is a large structure. This structure is passed ... EstablishConnections Method to provide the required information to the AutomationComponent to configure PubSub communication on that AutomationComponent . An OPC UA Client could adjust some information that is inside this data
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.3 ConnectionConfigurationSet and ReaderGroup

DataSetMessages from different NetworkMessages . However, it is recommended that the PubSubConfiguration generated for an AutomationComponent contains a ReaderGroup for each PubSubCommunicationFlowConfiguration. By this, common parameters (e.g., SecurityGroupId, SecurityKeyServices, TransportSettings
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.2.4 Extensibility

embedded into other Structures , e.g., the ConnectionConfigurationSet -related Structure has an array of AutomationComponent -related Structures . Therefore, each Structure has an additional field with an array of KeyValuePairs that
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.5 ConnectionEndpointConfigurationConfDataType

modified. True Name 0:String BrowseName of the ConnectionEndpoint to create in the AutomationComponent . False NameSelection 0:String[] Selection list options for the endpoint name. True NameModify 0:Boolean Flag ... They must be filled in by the ConnectionManager after getting the NodeIds from the AutomationComponent during connection establishment. True SubscribedDataSetData 0:StandaloneSubscribedDataSetDataType If not null, it specifies a SubscribedDataSet
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

F.1.9 AutomationComponentConfigurationConfDataType

F.1.9 AutomationComponentConfigurationConfDataType This Structure DataType holds the information related to the AutomationComponent participating in a Connection . It is semantically equivalent to the AutomationComponentConfigurationType as defined in 6.13.2 . The AutomationComponentConfigurationConfDataType ... Subtype of Structure defined in OPC 10000-5 BrowseName 0:String BrowseName of the AutomationComponent . False AutomationComponentNode 4:NodeIdentifier AutomationComponentNode specifies the AutomationComponent that is to be used for establishing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

G.1 Diagnostics Client

monitor only one side of a 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 ... AggregatedCurrentState reported by the ConnectionManager . It will not need to connect to each AutomationComponent . If collecting diagnostics from a ConnectionManager that monitors only one side of a Connection
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.2 Application and QoS engineering

create the UAFX Information Model representing that program. This Information Model consists of an AutomationComponent representing the entity being created by Engineer A. Part of the AutomationComponent is the functional ... model representing the logical functionality of the User Program. FunctionalEntities contained in the AutomationComponent represent that functional model. Input and output Variables in the FunctionalEntity expose the data
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

1 Scope

purpose of this document is to define a data format for the sharing of AutomationComponent information between the participants in the OfflineEngineering workflow. OfflineEngineering is a design phase activity
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

4 Overview

Overview OfflineEngineering is an essential phase in the lifecycle of an AutomationComponent . By allowing the Controls Engineer to define, program, configure and partially validate the operation of an AutomationComponent before ... deploying the AutomationComponent in physical hardware, the Controls Engineer will be more confident that the AutomationComponent performs the automation functions reliably and correctly once the physical AutomationComponent is in place
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

5.1 Descriptor fundamentals overview

more AutomationComponents . This information may contain data provided by the vendor of the AutomationComponent or configuration data produced by Controls Engineers in the OfflineEngineering phase. A Descriptor is a digitally
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

5.2 Descriptor organization

Models . A worked-out example of the configuration of the Information Model of an AutomationComponent using the UAFX Information Model can be found in Annex F . Attachment files contain information ... useful for understanding and using the AutomationComponent in engineering, operation, or another phase of the AutomationComponent life cycle. This information can be considered supplemental to the information from the Information
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

5.3 References in a Descriptor

example, a Descriptor created by a Controls Engineer containing configuration information for an AutomationComponent usually contains a reference to a Descriptor with the product information provided by the AutomationComponent vendor
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

5.4 OPC UA FX AML Information Model files

File is an OPC UA FX AML file with an Information Model of the AutomationComponent . The OPC UA FX AML libraries that are used in an Information Model file
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

6.2 Descriptor with product information

vendor's engineering tool. Typically, the product information contains an Information Model of the AutomationComponent that can be used to start the configuration and supplemental documentation, like user manuals, drawings ... understanding and using the product. In OPC UA FX, the information of the AutomationComponent product contains the Asset and functional structure, (pre-configured) DataSets , capabilities, and the property name defined
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

6.3 Descriptor with configuration information

Descriptor with configuration information contains the Information Model that incorporates the configuration of AutomationComponent . The product information can also be part of a Descriptor with configuration information, for example ... information. The configuration information provided may be different, depending on the type of the AutomationComponent or the use case for sharing. Configuration information dependent on the type of AutomationComponent : Controller
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

6.5 Descriptor for modular AutomationComponents

Descriptor for modular AutomationComponents In this example, the product information for a modular AutomationComponent that has been pre-configured with a known set of allowable modules is considered. In this ... example, the modular AutomationComponent consists of a head end and a number of modules that can be either attached to the head end or to slots in a chassis
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

7.3.4 Attachment files

files are useful for providing additional information for the understanding and usage of the AutomationComponent . No specific format is required for attachment files. The file name extension and the content
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

8.2 Requirements for engineering tools

Requirements for engineering tools Since the Information Model for an AutomationComponent in a Descriptor is modelled as an AML InternalElement within an AML InstanceHierarchy or an AML SystemUnitClass, the tools
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

8.3.1 Descriptor Export

cases for the export of a Descriptor are: The types of vendor-specific AutomationComponent products are made available in a Descriptor as OPC UA FX AML types for usage ... OfflineEngineering projects. An OPC UA FX Information Model of an AutomationComponent configuration is provided in a Descriptor for further sharing with other engineering tools. The Descriptor Export function uses
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

8.3.2 Descriptor Import

import are the import of an OPC UA FX Information Model of an AutomationComponent product and the import of an AutomationComponent configuration. Before starting the engineering work, a Controls Engineer ... must select and procure the product data information for an AutomationComponent . Typically, the selection and procurement of the production data information will be made in one of three different options
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

8.3.5 Conversion to an internal model

data of the Information Model AML files into the internal representation of the AutomationComponent used by the engineering tool. An overview of the tasks for conversion to an internal model
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

8.4 Example workflow for sharing a Descriptor in OfflineEngineering

changing the configuration of a Descriptor in a subsequent engineering step for the same AutomationComponent or using the information of the exported Descriptor for the configuration of another AutomationComponent ... rules as in 8.3.2 apply. In the case of subsequent engineering on the same AutomationComponent , data that was configured in a previous step may need to be changed
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

A.11.1 AutomationComponent

A.11.1 AutomationComponent An AutomationComponent is either modelled as AML InternalElement as part of an AML InstanceHierarchy or as AML SystemUnitClass (SUC). If the AutomationComponent is modelled as InternalElement
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

F.1.1 AutomationComponent modelling example

F.1.1 AutomationComponent modelling example This annex provides a worked-out example of the configuration of the Information Model of an AutomationComponent using the UAFX Information Model . This modelling process ... product data. The next stage may include the configuration data, such that the AutomationComponent can be set up and commissioned. The current stage is complete when the model
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

F.1.2 Instantiation of the AutomationComponentType

library. Figure F.2 - Instantiation of the SUC AutomationComponentType The top level of the AutomationComponent instance contains important Variables for product data: ConformanceName : Provides the URL to the product's listing ... conformance test can be found; ComponentCapabilities : Describes limits on the functionality provided by an AutomationComponent (e.g., number of supported logical connections, etc.); PublisherCapabilities and SubscriberCapabilities : Limits on the AutomationComponent
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

F.1.4 Creation of the FunctionalEntity structure

PublisherCapabilities and SubscriberCapabilities structure exists in the FunctionalEntity sub-model at three levels: AutomationComponent , FunctionalEntity and InputData and OutputData levels. In Figure F.8 , a FunctionalEntity "FillControl" is created
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.3 UAFX AutomationComponent

UAFX AutomationComponent Table 4 describes AutomationComponent related UAFX Information Model ConformanceUnits. For additional information about these items, please refer to OPC 10000‑81 . Table 4 - UAFX AutomationComponent Category Title Description ... AutomationComponent Server UAFX AutomationComponent Base Supports the AutomationComponentType and its related types. It also includes at least one instance of the AutomationComponentType . Server UAFX AutomationComponent SupportsPersistence Includes the SupportsPersistence Variable
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.5.4 UAFX Offline Descriptor AutomationComponent Facet

UAFX Offline Descriptor AutomationComponent Facet Table 61 describes the details of the UAFX Offline Descriptor AutomationComponent Facet. This Facet includes the content elements necessary for describing an AutomationComponent ... UAFX Descriptor file. Table 61 - UAFX Offline Descriptor AutomationComponent Facet Group Conformance Unit / Profile Title Optional UAFX OfflineEngineering UAFX Descriptor AcDescriptor DescriptorIdentifier False UAFX OfflineEngineering UAFX Descriptor AutomationComponent Base False