Search

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

28 result(s) for AliasNames

OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

Annex D Server Capability Identifiers (Normative)

Supports the PubSub Configuration model defined in OPC 10000-14 . ALIAS Supports the Alias Names Capabilities defined in OPC 10000-17 . SKS Supports the Security Key Server (SKS) Capabilities defined
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

1 Scope

Scope This part of the OPC UA Standard provides a definition of AliasNames functionality. AliasNames provide a manner of configuring and exposing an alternate well-defined name for any Node ... addresses in IP networks. Like a DNS Server, an OPC UA Server that supports AliasNames provides a lookup Method that will translate an AliasName to a NodeId of the related
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

4.5 Device replacement

where the configuration can include the addition of an AliasName . An interface for adding AliasNames and AliasNameCategories would allow a standard configuration to setup the device. In the case where ... device is moved and reconfigured, it may be required to first delete the AliasNames and AliasNameCategories in the device
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

5 AliasNames Information Model overview

AliasNames Information Model overview The AliasNames functionality (illustrated in Figure 1 ) defines a number of ObjectTypes , Methods , DataTypes and References . Figure 2 illustrates an example of the Object model defined ... AliasNames . Figure 1 - AliasNames Overview The model also includes some well-known fixed instances. The key functionality of AliasNames is to reference the information that an AliasName is assigned
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

6.2 AliasNameType ObjectType Definition

Client shall always ignore the namespace associated with an AliasName for comparison with other AliasNames . AliasName can be defined in Namespace 1 (the local Server ) or in some vendor defined ... addition of the new AliasName . This requirement allows aggregating Servers to detect new AliasNames . The deletion and then addition of an AliasName results in a new NodeId for the AliasName
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

6.3.1 Definition

Server defines. They can also include instances of AliasNameCategoryType to allow hierarchical groupings of AliasNames . It includes a mandatory Method for finding instances of AliasNameType in the AliasName hierarchy, starting ... Aliases AliasNameCategoryType instance (see 9.2 ), it would apply the AliasNameSearchPattern to all AliasNames that are defined under TagVariables , Topics and any other AliasNameCategoryType instance in the hierarchy. Well-known AliasNameCategories
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

6.3.2 FindAlias Method

AliasNameSearchPattern A string that can contain wild cards, use to find a list of AliasNames (see OPC 10000-4 - "Wildcard Characters" table for supported wildcards ... sensor). An aggregating Server could also provide the Node . This Method will return the AliasNames in order of preference. That is the Server will return what it recommends
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

6.3.3 FindAliasVerbose Method

AliasNameSearchPattern A string that can contain wild cards, use to find a list of AliasNames (see OPC 10000-4 - "Wildcard Characters" table for supported wildcards
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

6.3.4 AddAliasesToCategory Method

specified below, the arguments are defined in Table 9 . Signature AddAliasesToCategory( [in] String[] AliasNames, [in] ExpandedNodeId[] TargetNodes, [in] String[] TargetServers, [in] NodeId TargetReferenceType, [out] StatusCode[] ErrorCodes ); Table 9 - AddAliasesToCategory Method ... Arguments Argument Description AliasNames An array of the string part of the AliasName . It is Server specific as to what namespace the AliasName is added to. TargetNodes An array
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

6.3.5 DeleteAliasesFromCategory Method

DeleteAliasesFromCategory Method The DeleteAliasesFromCategory Method allows a Client to remove AliasNames from the AliasNameCategory . The signature of this Method is specified below; the arguments are defined in Table 13 . This ... cannot delete AliasName instances that are from the aggregated Server . Signature DeleteAliasesFromCategory ( [in] String[] AliasNames, [in] ExpandedNodeId [] TargetNodes, [out] StatusCode[] ErrorCodes ); Table 13 - DeleteAliasesFromCategory Method Arguments Argument Description AliasNames
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

7.1 Overview

Overview The following DataTypes are defined for the AliasNames model
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

8.1 Overview

Overview The following References are defined for the AliasNames model
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

A.1 Overview

Overview A number of examples are provided to help illustrate how AliasNames function. This includes a Client using an AliasName Server , inside of a Server , in an aggregating Server
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

A.2 AliasNames used within a single Server

AliasNames used within a single Server Figure A.1 illustrates how this model can be used inside of a Server . This sample includes multiple instances of AliasNameCategoryType . The figure illustrates that ... Objects could be referenced by more than one instance of AliasNameType . Figure A.1 - AliasNames in a Server example The figure describes an information model for a well. This model contains
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

A.4 Standalone AliasNames Server

Standalone AliasNames Server The standalone AliasNames Server illustrated in Figure A.3 provides a list of AliasNames that reference Nodes in multiple separate Servers . This type of configuration could be used ... Servers that do not have the resources to manage AliasNames on their own. It could also be used in a system where the configuration of AliasNames occurs after the devices
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

A.5 Client use of an AliasName Server

Client use of an AliasName Server AliasNames allow a Client to find TagVariables or Topics easily. Many industrial systems assign tags to specific measurement or sensors. These tags follow established ... actual address/location of this sensor is often not known when the Client is configured. AliasNames can be used to resolve this tag to the actual sensor in the system
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

B.1 Aggregating Server with a collection of Aggregates

aggregating Server as shown in Figure B.1 could also collect all of the AliasNames defined in underlying Servers and just build a composite list of these AliasNames . Since ... AliasNames are required to exist under the mandatory Aliases Object , it is simple for an aggregating Server to browse the AddressSpace and build a list. The aggregating Server shall merge
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

B.2 GDS

optional behaviour which this example illustrates. What is required is the availability of all AliasNames in the mandatory TagVariables folder and Topics folder, but a GDS could also choose ... structure of these categories is not defined. Figure B.2 - GDS with merged AliasNames example For additional information about a GDS and AliasNames see Annex
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

C.1 Overview

Overview A Global Discovery Server (GDS) that supports AliasNames, provides AliasNames functionality, but the target Nodes referenced are in other Servers. The AliasName s are aggregated from the Servers that ... capability (for information on capabilities see OPC 10000-12 ). Additional examples on aggregating AliasNames can be found in the aggregating Server section ( B.1 ). A GDS implementation also requires additional behaviour
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

C.2 Register a Server

Register a Server A GDS that includes support for AliasNames shall automatically aggregate all instances of AliasNameType that are available in any Server that has registered with ... location in the tree. Figure C.2 illustrates the process a GDS that supports AliasNames would follow. Figure C.2 - Server Registration Process [Note: a GDS could encounter a large list
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.1.1 Overview

aggregating Server or GDS , needs to be able to discover the Servers that support AliasNames . Furthermore, the aggregating Server or GDS needs to be able to detect if a Server ... that contains AliasNames has had updates to the AliasName definitions. An aggregating Server or GDS could Subscribe for the LastChange Variable on AliasNameCategoryType instances to detect when a value
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.2.2 AliasUpdateDataType

Description AliasUpdateDataType Structure ApplicationUri String The ApplicationInstance associated with the Server that has the AliasNames defined. (this is the Server that needs to be browsed for any updates). Categories AliasCategoryUpdateDataType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.7 AliasNames and OPC UA FX

AliasNames and OPC UA FX AliasNames is a concept in OPC UA (defined in OPC 10000-17 ) that allows defining alternate names for Objects , Variables or Methods in an AddressSpace ... into categories. The FindAlias method returns the ExpandedNodeId for the actual Object / Variable / Method . AliasNames are most commonly used for configuration management, but can also be used for DataSet /topic
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.1 General

Configuration resolution A ConnectionManager shall be able to resolve NodeIds using PortableNodeIds , PortableRelativePaths or AliasNames . The following provides an illustration of what needs to be done for each possible Node
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

13.3.4 AliasName provided

AliasName provided If the ConnectionConfigurationSet contains AliasNames ( Figure 72 provides an overview of the configuration), then the Client should perform the following steps: Connect to the well-known ... aggregating Server ) that supports AliasNames. This is typically preconfigured in all Servers since the GDS also provides other functionality, such as certificate management or discovery. See 6.7.2 for additional information
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

8.1 Overview

Overview For the discovery of assets, this specification uses the concept of AliasNames , as defined in OPC 10000-17 . AliasNames define an additional name for any Node of a Server ... used to categorize AliasNames and provide filter functionality on the AliasNames . The same AliasName can be represented by several Nodes , for example, if managed in different Servers . Using AliasNames simplifies
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

8.2.2 AssetsByProductInstanceUri

AssetsByProductInstanceUri The AssetsByProductInstanceUri Object is formally defined in Table 12 . All AliasNames organized by this category shall be assets having a 2: ProductInstanceUri (see section 7 ). The string part
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

8.2.3 AssetsByAssetId

AssetsByAssetId The AssetsByAssetId Object is formally defined in Table 12 . All AliasNames organized by this category shall be assets having a 2: AssetId (see section 7 ). The string part ... AssetId is set by the user, this might not be the case. Assigning AliasNames in the context of this Object is done by 2: AssetId . The 2: ProductInstanceUri should only