Search

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

77 result(s) for FunctionalEntity

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

Control System DHCP Dynamic Host Configuration Protocol CM ConnectionManager DNS Domain Name Service FE FunctionalEntity FX Field eXchange HMI Human Machine Interface IEC International Electrotechnical Commission IEEE Institute of Electrical
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.2 UAFX Information Model

communication capabilities and diagnostic information. OPC 10000-81 formally describes AutomationComponent , Asset , and FunctionalEntity . A Connection is a logical relationship between FunctionalEntities for exchanging information and coordinating joint operations. Data
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

3.3.2 Usage of Asset and FunctionalEntity

Usage of Asset and FunctionalEntity Clause 6.3 defines an Asset as an Object either derived from FxAssetType or an Object of any type that implements the required Interfaces . Asset (plural ... whether derived from the type or implementing the Interfaces . Clause 6.4 defines a FunctionalEntity as an Object either derived from FunctionalEntityType or an Object of any type that implements
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.2 AutomationComponent model

model, see the definition of FxAssetType in 6.3 . For a detailed description of the FunctionalEntity model, see the definition of FunctionalEntityType in 6.4 . For a description of the available ReferenceTypes
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.4.2 FunctionalEntityType

control and monitor its functionality. This includes input, output, and configuration data. A FunctionalEntity also provides identification information and methods to perform functionality-related verifications. An important part ... FunctionalEntity model is the interaction between FunctionalEntities, which is modelled as a Connection . The FunctionalEntity part of the model includes information such as status, diagnostics, and other information to help
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.4.3 FunctionalEntity type hierarchy

FunctionalEntity type hierarchy A FunctionalEntity can be of varying degrees of complexity and can represent different granularity and abstraction levels, from primitive functionality to an entire application. Various providers could ... representing an entire application, such as a paper machine or a boiler, where the FunctionalEntity has multiple nested SubFunctionalEntities . This document defines the FunctionalEntityType base type. Various companion standards
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.5 Relationships between FunctionalEntities and Assets

FunctionalEntities . A single Asset might be related to zero or more FunctionalEntities . A FunctionalEntity might be related to zero or more Assets . The models for both FunctionalEntities and Assets
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

4.6 FunctionalEntities and applications

arranged into hierarchies or any type of organisation. The details required in a FunctionalEntity for an application are application-specific, but the base functional model is required to describe ... FunctionalEntities so that all interactions can be represented in the same manner. A FunctionalEntity can interact with other FunctionalEntities by exchanging data. This exchange of data can be for control
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.1 Overview

Connections further requires concepts such as identity and compatibility verification of Asset and FunctionalEntity , establishing control via ControlGroup selection, setting ConfigurationData , and communication configuration. These concepts are mapped to existing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.2.3 FunctionalEntity verification

FunctionalEntity verification FunctionalEntity verification ensures that a given FunctionalEntity conforms to what was expected by system engineering. This verification includes checking the FunctionalEntity's author, identifier, or version (issued ... author of a FunctionalEntity ). It also supports checking any Variables defined by the application. It can include checking, for instance, specific additional properties (e.g., the existence and values of optional
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.3 ControlGroups

ControlGroups A FunctionalEntity can support multiple operating modes or groupings of functionality. An example might be a simple PID function block that supports cascade. In non-cascade mode ... ability to externally set the setpoint is blocked in cascade. ControlGroups allow a FunctionalEntity to advertise these different groupings or modes. A FunctionalEntity might define multiple (even nested) ControlGroups . These
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.4 ConfigurationData

ConfigurationData ConfigurationData describes a collection of Variables within a FunctionalEntity that are used to set up and configure its functionality. As part of establishing a Connection between FunctionalEntities , some configuration ... configuration required for the actual communication. The EstablishConnections Method allows any of the FunctionalEntity's ConfigurationData to be set. ConfigurationData can contain Variables that have the AccessLevelEx Attribute NonVolatile
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.1 Overview

illustrates this interaction. A logical connection is represented by two ConnectionEndpoints , one on each FunctionalEntity that is part of the connection. Figure 28 provides a more detailed view ... describe unidirectional data exchange between two FunctionalEntities . Autonomous publisher describes data published by a FunctionalEntity , where the related subscribing ConnectionEndpoint(s) are unknown to the logical connection. Autonomous subscriber describes
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.5 Persistent and preconfigured objects

AutomationComponent can provide preconfigured Objects (e.g., PublishedDataSet or ConnectionEndpoint ). An example might be a FunctionalEntity that includes a preconfigured PublishedDataSet that is used as part of a logical connection
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.2.2 Single Connection using unicast network messages

illustrates the logical connection between the two FunctionalEntities FE_A1 and FE_B1. Each FunctionalEntity contains a PubSubConnectionEndpoint (Con_A1 and Con_B1), which references a DataSetReader and a DataSetWriter
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.6.2.5 DataSetMetaData

Independent of the lifetime of a Connection, another engineering tool can update a FunctionalEntity, including its preconfigured DataSets . In addition, the Descriptor can describe a different version of the FunctionalEntity
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.6 Health

status is aggregated from child 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
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.2 AutomationComponentType definition

Table 5 - AutomationComponentType additional References SourceBrowsePath Reference Type IsForward TargetBrowsePath 3:FunctionalEntities 3:<FunctionalEntity> 0:IsHostedBy True 3:Assets 3:<Asset> The components of the AutomationComponentType ... BrowsePath References NodeClass BrowseName DataType TypeDefinition Others 3:FunctionalEntities 0:Organizes Object 3:<FunctionalEntity> 3:FunctionalEntityType OP 3:Assets 0:Organizes Object 3:<Asset> 3:FxAssetType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.1 Overview

Connections . The ConnectionManager typically calls it. It allows for creating ConnectionEndpoints , establishing control, verifying FunctionalEntity and Asset compatibility, applying ConfigurationData , and configuring the communication model to be used for data
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.2 EstablishConnections signature

NodeId for FunctionalEntityNode was invalid. Bad_InvalidArgument The NodeId for FunctionalEntityNode was not a FunctionalEntity or related to the AutomationComponent on which EstablishConnections was called. Good The NodeId for FunctionalEntityNode ... does not include a feedback signal (PubSubConnectionEndpointParameterDataType Mode is set to Publisher), but the FunctionalEntity requires it (FeedbackSignalRequired is set to TRUE (see 6.4.7 )) . Bad_TypeDefinitionInvalid The requested ConnectionEndpointTypeId does
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.3.3 Command VerifyFunctionalEntityCmd

NotSet , and VerificationVariablesErrors to null or empty. The Method shall be called on the FunctionalEntity identified by FunctionalEntityNode , supplying the ExpectedVerificationVariables as Method Argument . The StatusCode returned by the Verify
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.3.5 Command CreateConnectionEndpointCmd

FALSE, the EstablishConnections implementation shall create a ConnectionEndpoint in the ConnectionEndpoints Folder of the FunctionalEntity identified by FunctionalEntityNode . The created ConnectionEndpoint shall be of the subtype specified in ConnectionEndpointTypeId ... shall exist with a BrowseName that matches Name in the ConnectionEndpoints Folder of the FunctionalEntity identified by FunctionalEntityNode. Its ConnectionEndpointTypeId , InputVariables and OutputVariables shall match what is specified in Parameter
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.5.2 CloseConnections behaviour

ConfigurationData that was applied when establishing the ConnectionEndpoints is vendor-specific. NOTE A FunctionalEntity could provide application-specific behaviour for its ConfigurationData , i.e. it might roll it back
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.7 PublisherCapabilitiesType

PublishSubscribe Object (see OPC 10000-14 ). If PublisherCapabilities is referenced from a FunctionalEntity (see 6.4.2 ) or OutputData (see 6.4.5 ), a preconfigured PublishedDataSet shall only reference OutputVariables of this FunctionalEntity
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.8 SubscriberCapabilitiesType

PublishSubscribe Object (see OPC 10000-14 ). If SubscriberCapabilities is referenced from a FunctionalEntity (see 6.4.2 ) or InputData (see 6.4.4 ), a preconfigured StandaloneSubscribedDataSet shall only reference InputVariables from the FunctionalEntity
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.1 Overview

definition of all functionality in an OPC UA FX Information Model . A FunctionalEntity can provide InputData , OutputData , ConfigurationData , diagnostic information and Methods for manipulating or sharing the data ... SubFunctionalEntities and relationships to other Objects defined in this model or other models. A FunctionalEntity may be implemented using the IFunctionalEntityType Interface . It does not need to be an instance
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.2 FunctionalEntityType definition

FunctionalGroupType O 3:HasSubFunctionalEntity Object 3:<SubFunctionalEntity> 3:FunctionalEntityType OP ConformanceUnits UAFX FunctionalEntity Base The components of the FunctionalEntityType have additional subcomponents, which are defined in Table ... that resolves to the website of the company responsible for this FunctionalEntity . NOTE Multiple instances of FunctionalEntityType could reference the same instance of AuthorUri . The optional AuthorAssignedIdentifier provides a unique
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.3 Verify method

Verify method The Verify Method allows a Client to verify whether a FunctionalEntity meets the expectation of system engineering (e.g., whether it is of the expected author, but also ... null, it shall be verified that NodeId exists. If the NodeId references a FunctionalEntity ApplicationIdentifier , then its Name sub-element shall always be ignored; only its UniqueIdentifier shall be used
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.4 InputsFolderType

HierarchicalReferences Variable 3:<InputVariable> 0:BaseDataType 0:BaseDataVariableType OP ConformanceUnits UAFX FunctionalEntity Base The InputsFolderType provides for the grouping of input variables. It shall be restricted to hold ... empty. The optional SubscriberCapabilities shall only be present on InputData of the FunctionalEntity . It provides the Subscriber capabilities associated with the InputData and describes additional restrictions of the SubscriberCapabilities defined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.5 OutputsFolderType

HierarchicalReferences Variable 3:<OutputVariable> 0:BaseDataType 0:BaseDataVariableType OP ConformanceUnits UAFX FunctionalEntity Base The OutputsFolderType provides for the grouping of output variables. It shall be restricted to hold ... empty. The optional PublisherCapabilities shall only be present on OutputData of the FunctionalEntity . It provides the Publisher capabilities associated with the OutputData and describes additional restrictions of the PublisherCapabilities defined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.6.3 SetStoredVariables method

SetStoredVariables Method allows a Client to store current values of configuration Variables for the FunctionalEntity and its SubFunctionalEntities . The FunctionalEntity shall apply the stored values to the configuration variables after ... shall be the NodeId of a configuration data variable belonging to ConfigurationData of this FunctionalEntity or one of its SubFunctionalEntities. Results An array of StatusCode corresponding to the VariablesToStore input
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.6.4 ClearStoredVariables Method

InvalidArgument The NodeId is not a ConfigurationData Variable or does not belong to this FunctionalEntity or one of its SubFunctionalEntities . Bad_NotSupported The NodeId specifies a Variable that
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.7 FunctionalEntityCapabilitiesType

shall be restricted to holding only Variables that reflect the capabilities of the FunctionalEntity . The FunctionalEntityCapabilitiesType is formally defined in Table 60 . Table 60 - FunctionalEntityCapabilitiesType definition Attribute Value BrowseName ... BaseDataVariableType OP 3:HasCapability Variable 3:FeedbackSignalRequired 0:Boolean 0:BaseDataVariableType O ConformanceUnits UAFX FunctionalEntity Base <Capability> - is an OptionalPlaceholder (defined in OPC 10000-3 ) to indicate that
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.8 ConnectionEndpointsFolderType

HasComponent Variable 3:CommHealth 3:CommHealthOptionSet 0:BaseDataVariableType O, RO ConformanceUnits UAFX FunctionalEntity Base The optional CommHealth aggregates the Status of all ConnectionEndpoints contained in the Folder . The aggregation rules ... defined as follows: If at least one ConnectionEndpoint established at this FunctionalEntity has its Status set to Error , the CommHealth CommError bit shall be set. If at least one ConnectionEndpoint
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.5.1 Overview

ControlGroupType is used to manage the control of the functionality provided by a FunctionalEntity or part of it. ControlGroups are used when some part of a FunctionalEntity ... controlled" by another FunctionalEntity or application. ControlGroups can be used by an application to help understand how the Variables (inputs, outputs, configuration) and Methods are logically related to each
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.5.2 ControlGroupType definition

ControlGroupType definition ControlGroups are part of the FunctionalEntity model and are independent of any communication model ( Client Server , PubSub , etc.). A ControlGroup is used to identify the usage of parts ... FunctionalEntity . ControlGroups may result in a restriction on the grouped items. The restriction can include Objects (input and configuration Variables ) and Method invocations. The restriction can block all changes
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.1 Overview

which InputVariables and/or OutputVariables are exchanged. ConnectionEndpoints reside in the ConnectionEndpoints Folder of a FunctionalEntity . The ConnectionEndpointType is illustrated in Figure 27 . Figure 27 - ConnectionEndpointType illustration A ConnectionEndpoint further describes
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.2 ConnectionEndpointType definition

connected to the ConnectionEndpoint . All referenced Variables shall be in the InputData of the FunctionalEntity related to the ConnectionEndpoint or a SubFunctionalEntity of the FunctionalEntity. The referenced Variables ... ConnectionEndpoint . All referenced Variables shall be listed in the OutputData of the FunctionalEntity related to the ConnectionEndpoint or a SubFunctionalEntity of the FunctionalEntity. The referenced Variables may be a subset
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.2 ConnectionManagerType definition

single call. For example, if there are multiple verification errors (e.g. Asset verification or FunctionalEntity verification), all would be logged. To facilitate tracking of LogRecords between the ConnectionManager
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.3.2 Establishing Connections

constructed out of the AssetVerificationType instances in the AutomationComponentConfiguration . VerifyFunctionalEntityCmd Verify that the FunctionalEntity is the one expected by system engineering. The argument ConnectionEndpointConfigurations ExpectedVerificationVariables that is passed for this ... constructed out of the instance of CommunicationModelConfigurationType . CreateConnectionEndpointCmd Create a ConnectionEndpoint on the FunctionalEntity . Alternatively, use a preconfigured ConnectionEndpoint . The argument ConnectionEndpointConfigurations ConnectionEndpoint that is passed for this command
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.11.2 ConnectionEndpointConfigurationType definition

PortableNodeIdentifierValuePair[] 0:BaseDataVariableType O ConformanceUnits UAFX ConnectionManager Base FunctionalEntityNode specifies the identifier of the FunctionalEntity to configure for this Connection . If a PortableRelativePath is specified, the path shall be relative
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.3 AuditConnectionCleanupEventType

inherits all Properties of the AuditUaFxEventType . The SourceNode for this Event shall be the FunctionalEntity that contained the RemovedEndpoint . RemovedEndpoint identifies the BrowseName of the ConnectionEndpoint that was removed. RelatedEndpoint
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.14 ConnectionEndpointConfigurationDataType

Subtype of Structure defined in OPC 10000-5 FunctionalEntityNode 0:NodeId NodeId of the FunctionalEntity to connect. False ConnectionEndpoint 2:ConnectionEndpointDefinitionDataType Specifies either the information for the ConnectionEndpoint ... created or the NodeId of an existing ConnectionEndpoint . This ConnectionEndpoint is contained in the FunctionalEntity referenced by FunctionalEntityNode . If this parameter is to be omitted, it shall
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.22 FunctionalEntityVerificationResultEnum

FunctionalEntityVerificationResultEnum This enumeration represents the result of FunctionalEntity verification. The enumeration is formally defined in Table 168 . Table 168 - FunctionalEntityVerificationResultEnum items Name Value Description NotSet 0 The verification result ... Match 1 FunctionalEntity matches expectations. Mismatch 2 FunctionalEntity does not match expectations. The FunctionalEntityVerificationResultEnum representation in the AddressSpace is formally defined in Table 169 . Table 169 - FunctionalEntityVerificationResultEnum definition Attribute Value
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.34 OperationalHealthOptionSet

OperationalHealthOptionSet This OptionSet defines flags indicating the health of a FunctionalEntity . The OperationalHealthOptionSet values are formally defined in Table 192 . Table 192 - OperationalHealthOptionSet values Value Bit No. Description Reserved ... Used by CommHealthOptionSet defined in 10.9 OperationalWarning 16 FunctionalEntity indicates a warning. OperationalError 17 FunctionalEntity indicates an error. SubOperationalWarning 18 One of the SubFunctionalEntities indicates a warning. SubOperationalError
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

11.12 HasControlGroup ReferenceType

subtype of HasComponent ReferenceType . The SourceNode of this ReferenceType shall be a FunctionalEntity . The TargetNode of this ReferenceType shall be an instance of ControlGroupType . The HasControlGroup ReferenceType is formally defined ... Comment Subtype of the 0:HasComponent ReferenceType defined in OPC 10000-5 ConformanceUnits UAFX FunctionalEntity Base
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.1 Overview

combination, in that the asset model might use the first approach, and a FunctionalEntity might use the second or third approach or any combination
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

B.3.2.1 Extending an existing type

providing the required UA FX functionality. The illustrated model does not create a separate FunctionalEntity and Asset since the existing model did not differentiate between the asset part ... model. The existing model already defines input/output/configuration data that would be required for a FunctionalEntity , but it does not include the communication aspect of a FunctionalEntity , so the IFunctionalEntity Interface
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

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 in its InputData , OutputData , and ConfigurationData ... existing UA models Another variance would be defining separate Variables in the FunctionalEntity , where the underlying device just references the same memory location for its value, as a Variable being
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

C.2 Usage of OPC UA safety Variables in a FunctionalEntity

Usage of OPC UA safety Variables in a FunctionalEntity Figure C.2 indicates a FunctionalEntity, which includes a SafetyProvider . The FunctionalEntity contains safety and non-safety Variables in its InputData ... OutputData . Figure C.2 - FunctionalEntity with safety data From a FunctionalEntity's perspective, the safety Variables CtrARequest and CtrAResponse are organised within the InputData and OutputData . In addition, these Variables
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.1 Overview

part of the OPC UA FX 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.3.1 Overview

D.3.1 Overview This clause provides examples of functionality that a FunctionalEntity might expose. This includes Inputs , Outputs , ControlGroups and the resulting Connections . It will also describe
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.2 Modelling of FunctionalEntity relationships

D.3.2 Modelling of FunctionalEntity relationships The following types of References provided with this document and OPC 10000-23 are used for modelling FunctionalEntities : HasSubFunctionalEntity indicates that a FunctionalEntity ... nested FunctionalEntity . IsHostedBy indicates that a FunctionalEntity needs the referenced Asset to provide its functionality. IsExecutingOn r elates a FunctionalEntity to the execution environment it is currently executing
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.3 FunctionBlock example

D.3.3 FunctionBlock example Figure D.17 provides an example FunctionalEntity model that could be applied to the single-board computer from the Asset example (MyRaspberryPi). The model shows a subtype ... capability of loading libraries of function blocks, where each function block would be a FunctionalEntity . The model includes a Method that is used to load function block libraries
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.5 Example of nested FunctionalEntities

instantiated in programs. A program is also loaded, where the program is a sub- FunctionalEntity (MyApplicationProgram), and each execution block is represented by a separate FunctionalEntity (Temperature, Humidity, Calculation
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.1 Overview

this information is made available to the controller. This AcmeAnalogueInputModuleType is external to the FunctionalEntity model; think of it as an existing Information Model . The FunctionalEntity then publishes this data ... another controller, HMI, or even other devices as needed. Figure D.20 - Example FunctionalEntity Type The following examples illustrate how InputData and OutputData can be joined with DataSets . Consider, for example
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.2 Using preconfigured DataSets

configured DataSet only This has the consequence that a ConnectionEndpoint established on that FunctionalEntity can only use the preconfigured PublishedDataSet for communication, as illustrated in Figure D.22 . Conn
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.6.3 Using preconfigured and customised DataSets

D.23 - Sample for analogue input module - preconfigured and customised DataSet ConnectionEndpoints established on that FunctionalEntity can use a preconfigured or customised DataSet as illustrated in Figure D.24 . Conn_A, Conn
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.7.2 Example of a simple ControlGroup

D.3.7.2 Example of a simple ControlGroup Figure D.28 shows the FunctionalEntity for a simple temperature monitor based on the Raspberry Pi Sense HAT (see Figure D.5 ). The FunctionalEntity provides ... variable allows the selection of the engineering unit for the Temperature. Figure D.28 - Sample FunctionalEntity for a simple temperature monitor While using the Temperature, the EngineeringUnit for the Temperature should
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.7.3 Example of a complex ControlGroup

Sense HAT and some motors attached through the connectors. Figure D.29 illustrates a sample FunctionalEntity representing this simplified AGV. Figure D.29 - Sample FunctionalEntity for a simplified AGV The Information Model ... functional model Each of the ControlGroups represents an interface provided by the FunctionalEntity to control and monitor the AGV using normalised or raw data. The interface is represented
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.3.8 Verifying FunctionalEntities

D.3.8 Verifying FunctionalEntities A Client is able to verify whether a FunctionalEntity meets the expectations of system engineering. This example demonstrates how to use verification. Figure D.32 - Sample ... FunctionalEntity Figure D.32 illustrates a simple FunctionalEntity . The author defining the AcmeFEType provides mandatory input and output Variables (a, b, c, and d) and optional Variables
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.4.1 Raspberry Pi example

example links the Asset illustrated in D.2.2 for the SenseHat ( Figure D.5 ) with the FunctionalEntity example in D.3.3 for the SenseHat ( Figure D.19 ). It shows the IsExecutingOn Reference between ... 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 the multiple Descriptors that the AC exposes
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.1.2 Single logical connection

EndpointB. Each ConnectionEndpointConfiguration contains all parameters required for creating the ConnectionEndpoint , verifying the affected FunctionalEntity , requesting ControlGroups , and application configuration. The ConnectionConfigurationSet provides two PubSubCommunicationFlowConfiguration Objects, Flow1 and Flow2. They
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

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

F.1.5 ConnectionEndpointConfigurationConfDataType

defined in OPC 10000-5 FunctionalEntityNode 4:NodeIdentifier FunctionalEntityNode specifies the identifier of the FunctionalEntity to configure for the Connection . If a RelativePath is specified, the path shall be relative
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.1 General

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
OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking

5.6.4.2 Application and QoS engineering

contained in the AutomationComponent represent that functional model. Input and output Variables in the FunctionalEntity expose the data to be exchanged using Connections with FunctionalEntities in another Controller . The Variables ... capabilities that this AutomationComponent supports. OPC 10000‑81 provides details about the AutomationComponent , FunctionalEntity , the functional model, PublisherCapabilities , and SubscriberCapabilities . To configure the use of priority-based
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

8.4 Example workflow for sharing a Descriptor in OfflineEngineering

engineering tools and downloaded together with the user programs into the Controllers . The yellow FunctionalEntity and Asset boxes represent the Information Model of the AutomationComponent(s ) in the Controllers
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

F.1.1 AutomationComponent modelling example

four steps: Instantiation of the AutomationComponentType; Creation of the Asset structure; Creation of the FunctionalEntity structure; Creation of the (preconfigured) DataSets. The AML Information Model does not need
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

F.1.4 Creation of the FunctionalEntity structure

F.1.4 Creation of the FunctionalEntity structure In this step of the example, the FunctionalEntity sub-model is created. See Figure F.7 . Figure F.7 - FunctionalEntity sub-model of Filling Machine example ... Core Libraries provide the FunctionalEntityType SUC for defining a FunctionalEntity ). Within each FunctionalEntity , define variables for the input, output, and configuration variables, and link the variables to the FunctionalEntity using
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.5 UAFX FunctionalEntity

UAFX FunctionalEntity Table 6 describes FunctionalEntity related UAFX Information Model ConformanceUnits. For additional information about these items, please refer to OPC 10000‑81 . Table 6 - UAFX FunctionalEntity Category Title Description ... AuthorAssignedVersion Supports the AuthorAssignedVersion Property of the IFunctionalEntity Interface. This also requires the UAFX FunctionalEntity AuthorAssignedIdentifier ConformanceUnit . Server UAFX IFunctionalEntity ApplicationIdentifier Supports the ApplicationIdentifier Property of the IFunctionalEntity Interface . Server
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.2.8 UAFX IFunctionalEntity Run-Time Diagnostic Counters Facet

IFunctionalEntity Run-Time Diagnostic Counters Facet. This Facet includes the functionality needed for tracking FunctionalEntity Connection operation activities. Table 22 - UAFX IFunctionalEntity Run-Time Diagnostic Counters Facet Group Conformance Unit ... Profile Title Optional UAFX FunctionalEntity UAFX IFunctionalEntity Diagnostics FunctionalGroup False UAFX FunctionalEntity UAFX IFunctionalEntity Diagnostics OperationalConnectionCount True UAFX FunctionalEntity UAFX IFunctionalEntity Diagnostics ExistingConnectionCount False UAFX FunctionalEntity UAFX IFunctionalEntity Diagnostics ErrorConnectionCount
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.2.10 UAFX FunctionalEntity Facet

UAFX FunctionalEntity Facet Table 24 describes the details of the UAFX FunctionalEntity Facet. This Facet includes the base functionality for a FunctionalEntity . Table 24 - UAFX FunctionalEntity Facet Group Conformance Unit ... Profile Title Optional UAFX IFunctionalEntity Facet UAFX FunctionalEntity UAFX FunctionalEntity Base False UAFX FunctionalEntity UAFX FunctionalEntity Type True UAFX FunctionalEntity UAFX FunctionalEntity SubFunctionalEntity True
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.2.11 UAFX top-level FunctionalEntity Facet

UAFX top-level FunctionalEntity Facet Table 25 describes the details of the UAFX top-level FunctionalEntity Facet. This Facet includes the functionality needed by a FunctionalEntity that is referenced directly ... AutomationComponentType FunctionalEntities Folder . Table 25 - UAFX top-level FunctionalEntity Facet Group Conformance Unit / Profile Title Optional UAFX FunctionalEntity Facet UAFX FunctionalEntity UAFX IFunctionalEntity AuthorUri False UAFX FunctionalEntity UAFX IFunctionalEntity AuthorAssignedIdentifier
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.5.6 UAFX Offline Descriptor FuntionalEntity Facet

Offline Descriptor FuntionalEntity Facet Table 63 describes the details of the UAFX Offline Descriptor FunctionalEntity Facet. This Facet includes the content elements necessary for describing a FunctionalEntity in a UAFX ... Descriptor file. Table 63 - UAFX Offline Descriptor FunctionalEntity Facet Group Conformance Unit / Profile Title Optional UAFX OfflineEngineering UAFX Descriptor ConfigurationDataFolder VariableStorage False UAFX OfflineEngineering UAFX Descriptor ConnectionEndpoint Base False UAFX