Search

58 result(s) for FunctionalEntities

• 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
  3.1.9 Connection
  Connection logical communication relationship between FunctionalEntities for exchanging information and coordinating joint operations
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  4.2 Architecture
  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
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  5.4.1 General
  more details regarding OfflineEngineering and Descriptors . Assets and FunctionalEntities being used in applications, their available input, output, and configuration data, and communication capabilities are shared between engineers using Descriptors
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  6.1 Controller-to-Controller communication
  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
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  6.2 UAFX Information Model
  that performs one or more automation functions. All AutomationComponents are composed of Assets and FunctionalEntities . An AutomationComponent also contains information related to communication capabilities and diagnostic information ... formally describes AutomationComponent , Asset , and FunctionalEntity . A Connection is a logical relationship between FunctionalEntities for exchanging information and coordinating joint operations. Data and event information can be exchanged. The first
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  3.3.2 Usage of Asset and FunctionalEntity
  FunctionalEntityType or an Object of any type that implements the required Interface . FunctionalEntity (plural FunctionalEntities ) is used throughout this document to designate an instance of such an Object , regardless
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.2 AutomationComponent model
  also include items that are not physical, such as firmware or licenses. FunctionalEntities encapsulate logical functionality, which can include function blocks, IO module functionality, drive functionality, sensor functionality, actuator functionality ... more complex logical items. FunctionalEntities can be related to Assets, and the representation of such relationships is included in the model. Both Assets and FunctionalEntities can be nested. The Information
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.4.1 Overview
  Overview FunctionalEntities encapsulate logical functionality. The OPC UA FX Information Model defines an Object Model for FunctionalEntities . Figure 5 illustrates the Object Model, which includes general information about the FunctionalEntityType ... input variables, output variables, and diagnostic information. FunctionalEntities can be nested or have relationships to other FunctionalEntities . The Object Model also includes a representation of Connections (communication) between FunctionalEntities . Figure
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.4.2 FunctionalEntityType
  FunctionalEntityType The FunctionalEntityType defines the base information and functionality that all FunctionalEntities provide. The FunctionalEntityType provides data and methods to control and monitor its functionality. This includes input, output ... functionality-related verifications. An important part of the FunctionalEntity model is the interaction between FunctionalEntities, which is modelled as a Connection . The FunctionalEntity part of the model includes information such
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.4.3 FunctionalEntity type hierarchy
  abstraction levels, from primitive functionality to an entire application. Various providers could define FunctionalEntities. For example: there are primitive FunctionalEntities that only generate output data, like a temperature sensor ... only receive input data, like a relay; more complex FunctionalEntities like a motion axis can receive control data, perform a calculation or action, provide status/feedback data, expose methods for operation
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.5 Relationships between FunctionalEntities and Assets
  Relationships between FunctionalEntities and Assets Assets can be related to FunctionalEntities . A single Asset might be related to zero or more FunctionalEntities . A FunctionalEntity might be related to zero ... more Assets . The models for both FunctionalEntities and Assets are independent. Specific References only link them (see Figure 7 for an illustration and 11.1 for details on ReferenceTypes ). Figure
• 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 ... specific, but the base functional model is required to describe the interaction between the FunctionalEntities so that all interactions can be represented in the same manner. A FunctionalEntity can interact
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.7.1 Overview
  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 Model ... 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. For example, a ConnectionManager
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.7.2 Creating / Monitoring / Closing Connections
  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, and Clients can monitor this
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.2.1 Overview
  level that is compatible with what is expected by system engineering. For FunctionalEntities , a verification Method is defined, which can be used to verify instance-specific properties (e.g., identity properties
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.4 ConfigurationData
  configure its functionality. As part of establishing a Connection between FunctionalEntities , some configuration might be required. This configuration is separate from the configuration required for the actual communication. The EstablishConnections
• 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 ... connections are supported (see Figure 10 ): Bidirectional connections describe bidirectional data exchange between two FunctionalEntities . Unidirectional connections with heartbeat describe unidirectional data exchange in one direction and a heartbeat message
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.3 Establishing and closing Connections
  AutomationComponent , FunctionalEntity , etc., optional parameters to be used for verifying the Assets and FunctionalEntities , optional parameters to be used for establishing control, optional parameters to be used for configuring
• 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.2 Single Connection using unicast network messages
  This use case, illustrated in Figure 12 , describes a single logical connection between two FunctionalEntities located on the AutomationComponents A and B, each containing a Publisher , a Subscriber ... single PubSubConnectionEndpoint . Both FunctionalEntities could be publishing data (bidirectional Connection ), or only one could be publishing data while the other publishes a heartbeat (unidirectional connection with heartbeat). Figure 12 - Single
• 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
  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
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.6 Health
  Health Assets , FunctionalEntities , ConnectionEndpoints , and ConnectionConfigurationSets provide general health status and diagnostic conditions. This 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 allows a Client to easily detect whether diagnostic conditions are present somewhere in the Information
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.8 Aggregation of OPC UA FX Servers
  reflected in a higher-level Server . This reflection can include Assets and FunctionalEntities , but it is expected that the communication model (between FunctionalEntities ) will only exist in the actual Servers
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.9 Well Known Roles
  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, and executing
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.1 Overview
  Overview The AutomationComponentType ObjectType provides for a grouping of Assets and FunctionalEntities in a given model. It exposes a Method that is used to establish Connections between FunctionalEntities . An overview
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.2 AutomationComponentType definition
  Subtype of the 0:BaseObjectType defined in OPC 10000-5 0:HasComponent Object 3:FunctionalEntities 0:FolderType M 0:HasComponent Object 3:Assets 0:FolderType M 0:HasComponent Object ... UAFX AutomationComponent Base Table 5 - AutomationComponentType additional References SourceBrowsePath Reference Type IsForward TargetBrowsePath 3:FunctionalEntities 3:<FunctionalEntity> 0:IsHostedBy True 3:Assets 3:<Asset> The components
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.9.2 PubSub
  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 be set in the Result
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.7 PublisherCapabilitiesType
  preconfigured PublishedDataSet shall only reference OutputVariables of this FunctionalEntity and its sub- FunctionalEntities . If the PublisherCapabilities is referenced from an AutomationComponent , a preconfigured PublishedDataSet shall only reference OutputVariables from FunctionalEntities ... used in a ConnectionConfigurationSet , Connections shall be established to one or more of the FunctionalEntities whose variables are present in the DataSet . An empty array indicates that no preconfigured PublishedDataSets
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.8 SubscriberCapabilitiesType
  preconfigured StandaloneSubscribedDataSet shall only reference InputVariables from the FunctionalEntity and its sub- FunctionalEntities . If the SubscriberCapabilities is referenced from an AutomationComponent , a preconfigured StandaloneSubscribedDataSet shall only reference InputVariables from FunctionalEntities ... used in a ConnectionConfigurationSet , Connections shall be established to one or more of the FunctionalEntities whose variables are present in the DataSet . An empty array indicates that no preconfigured StandaloneSubscribedDataSets
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.2 FxAssetType definition
  model to 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
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.2 FunctionalEntityType definition
  Annex B . Annex C provides a description of how to apply SafetyData to FunctionalEntities . Table 41 - FunctionalEntityType definition Attribute Value BrowseName 3:FunctionalEntityType IsAbstract False References Node Class BrowseName DataType ... provide the Publisher capabilities associated with this FunctionalEntity . They also apply to all sub- FunctionalEntities of this FunctionalEntity . The PublisherCapabilities for the FunctionalEntity shall describe additional restrictions of the PublisherCapabilities
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.5.2 ControlGroupType definition
  choice of ControlGroup would lock the functionality into a specific mode. More complex FunctionalEntities might also restrict which ControlGroups are available based on configuration settings. The ControlGroupType is formally defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.6.1 Overview
  Overview A ConnectionEndpoint is used to represent an endpoint of a Connection between two FunctionalEntities for data exchange. It provides information about which InputVariables and/or OutputVariables are exchanged. ConnectionEndpoints reside ... determined for a given communication model. Figure 28 illustrates a Connection between two FunctionalEntities and the use of PubSubConnectionEndpointType to represent the exchanged Variables , as well as corresponding References
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  9.1.1 Overview
  subtype of the BaseDataVariableType and holds the aggregated health of Assets and FunctionalEntities . The AggregatedHealthType is illustrated in Figure 51 . Figure 51 - AggregatedHealthType illustration
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  9.1.2 AggregatedHealthType definition
  AggregatedOperationalHealth shall be the aggregation of the OperationalHealth of the AutomationComponent's top-level FunctionalEntities . The aggregation rule is defined as a logical OR of the OperationalHealth ... level FunctionalEntities
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.1 AggregatedHealthDataType
  Assets AggregatedOperationalHealth 3:OperationalHealthOptionSet Aggregation of the OperationalHealth of the AutomationComponent's top-level FunctionalEntities The AggregatedHealthDataType representation in the AddressSpace is formally defined in Table 122 . Table 122 - AggregatedHealthDataType
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  12.2 FxRoot
  related to OPC UA FX. It may contain multiple AutomationComponents that include Assets and FunctionalEntities . It may also contain, at most, one ConnectionManager . NOTE    AutomationComponents are part of the Server
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  13.1 Overview
  During the establishment of a logical connection ( Connection) , the ConnectionManager needs to locate the FunctionalEntities and the Servers on which they reside. The ConnectionConfigurationSets contain the information from which this
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.2.1 Extending an existing type
  instance would just reference the existing MyModelInstance from both the Assets Folder and the FunctionalEntities Folder . It is important to understand that this is just an illustration of one possible
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  C.3 Usage of OPC UA safety Variables in Connections
  CtrARequest, CtrAResponse à CtrBResponse) and, in addition, data exchange between other Variables of these FunctionalEntities (e.g., Out_X5  IN_A1). OPC 10000-15 uses the terms unidirectional and bidirectional from
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.1 Overview
  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.2 Modelling of FunctionalEntity relationships
  References provided with this document and OPC 10000-23 are used for modelling FunctionalEntities : HasSubFunctionalEntity indicates that a FunctionalEntity has a nested FunctionalEntity . IsHostedBy indicates that a FunctionalEntity needs ... sensor that is dual-ported and wired to two different input signals. These two FunctionalEntities could be related with RepresentsSameEntityAs. RepresentsSameFunctionalityAs (symmetric) relates two entities representing the same functionality. This
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.5 Example of nested FunctionalEntities
  D.3.5 Example of nested FunctionalEntities Figure D.19 illustrates an ExecutionEngine in which libraries have been loaded as well as a program. There are two libraries loaded. One that provides ... application that was loaded since each was provided by a different vendor. The Sub FunctionalEntities all have their own AuthorUri and other properties, but they are not illustrated for simplicity
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.1.1 Overview
  complete set. A ConnectionConfigurationSet can contain a single logical connection between two FunctionalEntities , multiple logical connections between FunctionalEntities located on two AutomationComponents , or multiple logical connections between FunctionalEntities located
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.1.2 Single logical connection
  each referenced by an AutomationComponentConfiguration, AC_A and AC_B, which hold the FunctionalEntities involved in this logical connection. AC_A and AC_B contain the parameters for verifying Assets
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.4.7 PubSub DataSets
  possible combinations of DataSets exist for an information flow on a Connection between two FunctionalEntities to be configured: Preconfigured DataSets exist on both endpoints. A preconfigured DataSet exists on just ... network message. For example, if the ConnectionConfigurationSet has three Connections between two AutomationComponents (different FunctionalEntities ), the PubSub configuration might be a single DataSet with all the required Variables . Alternatively
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.4.2 Application and QoS engineering
  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 ... data to be exchanged using Connections with FunctionalEntities in another Controller . The Variables PublisherCapabilities and SubscriberCapabilities, also contained in the AutomationComponent , describe communication capabilities such as publishing intervals and, most
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.4.5 Connection establishment and operation
  this end, the ConnectionManager invokes the EstablishConnections Method on the AutomationComponents that reference the FunctionalEntities being connected, as depicted in Figure 12 label A. For details on Address
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  6.3 Descriptor with configuration information
  sharing. Configuration information dependent on the type of AutomationComponent : Controller configurations typically contain the FunctionalEntities together with input and output Variables , DataSets , and the publisher and subscriber capabilities ... devices, the configuration typically contains the values for the parameters for the built-in FunctionalEntities , the built-in DataSets , and the publisher and subscriber capabilities. For modular devices, the configuration
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  8.4 Example workflow for sharing a Descriptor in OfflineEngineering
  Asset boxes represent the Information Model of the AutomationComponent(s ) in the Controllers . The FunctionalEntities contain input groups, output groups, data types, names, capabilities and other information
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  F.1.1 AutomationComponent modelling example
  filling machine The Information Model of the filling machine is modelled with three FunctionalEntities : one for the fill level measurement, one for the actuation of the valve that supplies
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  F.1.4 Creation of the FunctionalEntity structure
  model of Filling Machine example The following steps are needed to define the FunctionalEntities : Creation of the FunctionalEntityType instances (The OPC UA FX AML Core Libraries provide the FunctionalEntityType
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  5.1 Overview
  ConformanceUnits for various features of FxAssets . UAFX FunctionalEntity Defines ConformanceUnits for various features of FunctionalEntities . UAFX ConnectionManager Defines ConformanceUnits for various features of ConnectionManagers . UAFX Ethernet Networking Features Defines ConformanceUnits
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  5.2.3 UAFX AutomationComponent
  Includes the MaxFunctionalEntities Variable in the ComponentCapabilities Folder and supports the claimed number of FunctionalEntities . Server UAFX AutomationComponent MaxConnectionsPerCall Includes the MaxConnectionsPerCall Variable in the ComponentCapabilities Folder and supports
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  6.6.2.7 UAFX IFunctionalEntity Facet
  details of the UAFX IFunctionalEntity Facet. This Facet includes the functionality common to all FunctionalEntities . Table 21 - UAFX IFunctionalEntity Facet Group Conformance Unit / Profile Title Optional UAFX FunctionalEntity UAFX IFunctionalEntity
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  6.6.2.11 UAFX top-level FunctionalEntity Facet
  includes the functionality needed by a FunctionalEntity that is referenced directly by the AutomationComponentType FunctionalEntities Folder . Table 25 - UAFX top-level FunctionalEntity Facet Group Conformance Unit / Profile Title Optional UAFX
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  6.6.4.6 UAFX ConnectionManager 2024 Facet
  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 Group Conformance