Search

200 result(s) for browseName

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.3.1 Conventions for AddressSpace figures
  text line in the rectangle identifies the NodeClass and the second line contains the BrowseName . When one line is used, it contains the BrowseName . Node rectangles may contain boxes used
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.3.2 Conventions for defining NodeClasses
  defined in this standard are defined by their name, which is mapped to the BrowseName having the NamespaceIndex 0, which represents the Namespace for OPC UA. The Use column (optional
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.5.2 Properties
  allowed to have Properties defined for them. To easily identify Properties , the BrowseName of a Property shall be unique in the context of the Node containing the Properties
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.6.4 Instantiation of complex TypeDefinitionNodes
  TYPE". It also contains a Variable "SP" having the same BrowseName as the Variable "SP" used by the TypeDefinitionNode and thereby reflects the structure defined ... TypeDefinitionNode . A TypeDefinitionNode or an InstanceDeclaration shall never reference two Nodes having the same BrowseName using forward hierarchical References . Instances based on InstanceDeclarations shall always keep the same BrowseName
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.10.3 AddIn model
  subtype shall be used. The AddIn ObjectType shall include the definition of a default BrowseName using the DefaultInstanceBrowseName Property . Instances of such an AddIn should use this default BrowseName ... instantiated multiple times in the same parent, only one instance can have the default BrowseName . The definition of an AddIn and its use with a default BrowseName is illustrated
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.4 BrowseName
  BrowseName Nodes have a BrowseName Attribute that is used as a non-localised human-readable name when browsing the AddressSpace to create paths out of BrowseNames . The TranslateBrowsePathsToNodeIds Service defined ... used to follow a path constructed of BrowseNames . A BrowseName should never be used to display the name of a Node . The DisplayName should be used instead for this purpose
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.5 DisplayName
  display the name of the Node to the user. They should not use the BrowseName for this purpose. The Server may maintain one or more localised representations for each DisplayName
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.2 Attributes
  NodeClass inherits the base Attributes from the Base NodeClass defined in 5.2 . The inherited BrowseName Attribute is used to specify the meaning of the ReferenceType as seen from the SourceNode ... example, the ReferenceType with the BrowseName "Contains" is used in References that specify that the SourceNode contains the TargetNode . The inherited DisplayName Attribute contains a translation
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.1 Object NodeClass
  Object is created based on an InstanceDeclaration then it shall have the same BrowseName as its InstanceDeclaration
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.2 ObjectType NodeClass
  Icon Property contains a relatively small image. DefaultInstanceBrowseName O QualifiedName Allows the definition of BrowseName on an ObjectType that all instances should use by default. This Property has no ModellingRule
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.4 Client-side creation of Objects of an ObjectType
  addition to the AddNodes Service ObjectTypes may have a special Method with the BrowseName " Create ". This Method is used to create an Object of this ObjectType . This Method ... output arguments of this Method depend on the ObjectType ; the only commonality is the BrowseName identifying that this Method will create an Object based on the ObjectType . Servers should
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.2 Variable NodeClass
  Variable is created based on an InstanceDeclaration (see 4.6 ) it shall have the same BrowseName as its InstanceDeclaration . The other References are described separately for Properties and DataVariables
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.3 Properties
  points to the VariableType of the Property . Since Properties are uniquely identified by their BrowseName , all Properties shall point to the PropertyType defined in OPC 10000-5 . Properties shall always ... HasProperty Reference pointing to a Variable Node defines this Node as a Property . The BrowseName of a Property is always unique in the context of a Node
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  context of this Method . The Variable referenced by a HasArgumentDescription ReferenceType shall use a BrowseName equal to the name of the Argument it describes. The Namespace of the BrowseName shall
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.2 Encoding Rules for different kinds of DataTypes
  these DataEncodings are text based and make use of Name portion the DataType BrowseName . For this reason, the BrowseName for all DataTypes should be Strings that start with a letter ... contain only letters, digits or the underscore (_). If a DataType has a BrowseName that does not meet these requirements it will be transformed using the Name encoding rules defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.3 DataType NodeClass
  Each concrete Structured DataType shall point to at least one DataTypeEncoding Object with the BrowseName "Default Binary" or "Default XML" having the NamespaceIndex 0. The BrowseName ... DataType , i.e. a DataType shall not point to two DataTypeEncodings having the same BrowseName . Standard Properties NodeVersion O String The NodeVersion Property is used to indicate the version
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.8.5.2 DataTypeRefinement Objects
  referenced using a Reference of HasFieldDescription ReferenceType (see 7.25 ) or a subtype. The BrowseName of the Variable shall use a BrowseName equal to the name of the field. The Namespace ... BrowseName shall be ignored by a Client when performing an equality check with a field name. A DataTypeRefinement Object shall not reference any Node with a HasFieldDescription or subtype which
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.4 Similar Node of InstanceDeclaration
  InstanceDeclaration A similar Node of an InstanceDeclaration is a Node that has the same BrowseName and NodeClass as the InstanceDeclaration and in cases of Variables and Objects the same TypeDefinitionNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.6 BrowseName within a TypeDefinitionNode
  BrowseName within a TypeDefinitionNode A BrowsePath within a TypeDefinitionNode which include targets of forward hierarchical References shall have a BrowseName that is unique within the TypeDefinitionNode, this same restriction applies ... that any InstanceDeclaration within the InstanceDeclarationHierarchy can be uniquely identified by a sequence of BrowseName
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.2.7 Attribute Handling of InstanceDeclarations
  exist regarding the Attributes of InstanceDeclarations when the InstanceDeclaration is overridden or instantiated. The BrowseName and the NodeClass shall never change and always be the same as the original InstanceDeclaration
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.2 Attributes
  except for the NodeId . Inherited Attribute values may be overridden by the subtype, the BrowseName and DisplayName values should be overridden. Special rules apply for some Attributes of VariableTypes
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.2 Fully-inherited InstanceDeclarationHierarchy
  subtype of "AlphaType". The name in each box is the BrowseName and the number is the NodeId . Figure 25 - Subtyping TypeDefinitionNodes An InstanceDeclarationHierarchy can be fully described
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.3.3.3 Overriding InstanceDeclarations
  InstanceDeclaration with the same BrowsePath . An overridden InstanceDeclaration shall have the same NodeClass and BrowseName . The TypeDefinitionNode of the overridden InstanceDeclaration shall be the same or a subtype ... Node may specify new values for the Node Attributes other than the NodeClass or BrowseName , however, the restrictions on Attributes specified in 6.2.7 apply. Any Attribute provided by the overridden
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.1 Overview
  Node . If a Node has an InstanceDeclaration then it shall have the same BrowseName and NodeClass as the InstanceDeclaration and, in cases of Variables and Objects , the same TypeDefinitionNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.2 Creating an Instance
  InstanceDeclaration itself or another Node in the AddressSpace that has the same TypeDefinitionNode and BrowseName . If new copies are created, then the Attribute values of the InstanceDeclarations are used ... ModellingRule do not appear in the instance. Instances may have children with duplicate BrowseName s; however, only one of those children will correspond to the InstanceDeclaration . Figure 27 - An Instance
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.2 Optional
  instance, this can be the same Node or two different Nodes with the same BrowseName (similar Node to InstanceDeclaration F). Not considered in the example is if the instances have
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.4 OptionalPlaceholder
  InstanceDeclarations are not further considered for instantiating the TypeDefinition . It is recommended that the BrowseName and the DisplayName of InstanceDeclarations having the OptionalPlaceholder ModellingRule should be enclosed within angle brackets ... ModellingRule shall remain OptionalPlaceholder . For Methods, the ModellingRule OptionalPlaceholder is used to define the BrowseName where subtypes and instances provide more information. The Method definition with the OptionalPlaceholder only defines
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.5 MandatoryPlaceholder
  when the DeviceType requires that at least one DeviceParameter shall exist without specifying the BrowseName for it, it uses MandatoryPlaceholder as shown in Figure 37 . Device A is a valid ... same ReferenceType or a subtype as the InstanceDeclaration . It does not require a specific BrowseName and thus cannot be used for the TranslateBrowsePathsToNodeIds Service (see OPC 10000-4 ). When
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.22.1 Overview
  TargetNode shall be a Variable which represents a field of the Structure DataType. The BrowseName of a DataVariable which is exposed shall be the same as the field name ... Structure DataType . The NamespaceIndex of the BrowseName shall be the same as the NamespaceIndex of the Structure DataType which first defines the field. The exposed fields shall be the same
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.22.2 Differences between HasStructuredComponent and ExposesItsArray
  concepts handle this differently, as described in this section. Using the HasStructuredComponent ReferenceType , the BrowseName of the subvariable is defined and reflects the place in the array. That ... subscribing to the corresponding IndexRange on the parent Variable . Using the ExposesItsArray ModellingRule , the BrowseName of the subvariables are not defined and do not reflect the place in the array
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.25 HasFieldDescription
  TargetNode of this ReferenceType shall be a Variable of BaseDataVariableType or a subtype. The BrowseName of the Variable shall have the same name as the field of the Structured DataType ... further restricted. It is not allowed to reference two Variables with the same BrowseName using the HasFieldDescription ReferenceType or a subtype from the same SourceNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  7.29 AllowedSubtype
  Variable shall follow the rules defined in 5.8.6 . It is recommended that the BrowseName of the Variable describes the used DataType including its ValueRank. However, it should ... same Namespace . It is not allowed to reference two Variables with the same BrowseName using the AllowedSubtype ReferenceType or a subtype from the same SourceNode
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.3 QualifiedName
  This Built-in DataType contains a qualified name. It is, for example, used as BrowseName . Its elements are defined in Table 25 . The name part of the QualifiedName is restricted
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.51 StructureField
  children of the Variable that contains the Structure Value . In this case the BrowseName of the DataVariable shall be the same as the StructureField name and the NamespaceIndex ... BrowseName shall be the same as the Structure DataType Node NamespaceIndex . OPC 10000-6 defines a number of DataEncodings which specify how to serialize Structure DataTypes . Some of these DataEncodings
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  A.4.2 Properties or DataVariables
  Clause 4 there are also syntactical differences. A Property is identified by its BrowseName , that is, if Properties having the same semantic are used several times, they should always have ... same BrowseName . The same semantic of DataVariables is captured in the VariableType . If it is not clear which concept to use based on the semantic described in Clause 4 , then
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.2 Notation
  Node which is either optional (0..1) or required (1), such as BrowseName to Base in Figure B.2 . Figure B.2 - Notation (I) UML object diagrams are used to display ... displayed as the role name of the TargetNode . The value of the OPC Attribute BrowseName is represented by the UML object name, for example the BrowseName of the UML object
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  B.3.6 Variable and VariableType
  SourceNode of a HasProperty Reference shall have a unique BrowseName in the context
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.2 Simple notation
  Near the line has to be a text containing the string-part of the BrowseName of the ReferenceType . Any asymmetric ReferenceType Asymmetric ReferenceTypes are represented as lines between Nodes with ... Near the line has to be a text containing the string-part of the BrowseName of the ReferenceType . Any hierarchical ReferenceType Asymmetric ReferenceTypes that are subtypes of HierarchicalReferences should
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.3 Extended notation
  shown, including the text used in the graphical representation of a Node . The BrowseName contains the NamespaceIndex and a String . Such a structure can be exposed as [<NamespaceIndex ... String> where the NamespaceIndex is optional. For example, a BrowseName can be "1:MyName". Instead of that, "MyName" can also be used. This rule applies
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.4.1 Description
  this Service specifying the NodeId of "Boiler1" as starting Node and the BrowseName of the "HeatSensor" as browse path. The Service would return the NodeId ... subscribe to its Value Attribute . If a Node has multiple targets with the same BrowseName , the Server shall return a list of NodeIds . However, since one of the main purposes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.29 ReferenceDescription
  TargetNode is a local Node the nodeId shall contain the namespace index. browseName 1 QualifiedName The BrowseName of the TargetNode . displayName LocalizedText The DisplayName of the TargetNode . nodeClass 1 NodeClass ... index in the ExpandedNodeId indicates that the TargetNode is a remote Node , then the browseName , nodeClass and typeDefinition may be null or empty. If they are not null or empty
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.30 RelativePath
  should be followed. Subtypes are included if this value is TRUE. targetName QualifiedName The BrowseName of the target node. The final element may have an empty targetName . In this situation ... current path cannot be followed any further if no targets with the specified BrowseName exist. A RelativePath can be applied to any starting Node . The targets of the RelativePath
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  A.2 BNF of RelativePath
  ReferenceType> A string delimited by the '<' and '>' symbols specifies the BrowseName of a ReferenceType to follow. By default, any References of the subtypes the ReferenceType are followed ... well. A '#' placed in front of the BrowseName indicates that subtypes should not be followed. A '!' in front of the BrowseName is used to indicate that the inverse Reference should
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.2 Used type model
  notation, custom ReferenceTypes are listed as a named Reference . For Properties , the BrowseName , NodeId , and Value are shown. The Nodes that are included in a View (View1) are enclosed
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.3.3 Example Notes
  translated to the IntegerId of the Attribute . Also in all of the examples the BrowseName is included in the result table for clarity; normally this would not be returned
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  description of the value. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being ... defined in the same table; therefore only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition. Table
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  4.1 NodeIds
  actual NodeIds . The symbolic name of each Node defined in this standard is its BrowseName , or, when it is part of another Node , the BrowseName of the other Node ... BrowseName of itself. In this case "part of" means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  5.1 General
  DisplayName is a LocalizedText . Each server shall provide the DisplayName identical to the BrowseName of the Node for the LocaleId "en". Whether the server provides translated names
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  provided by the StaticNodeIdTypes, StaticNumericNodeIdRange and StaticStringNodeIdPattern Properties . Table 22 - NamespaceMetadataType definition Attribute Value BrowseName NamespaceMetadataType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined ... PropertyType Optional HasProperty Variable ModelVersion SemanticVersionString PropertyType Optional Conformance Units Base Info ServerType The BrowseName of instances of this type shall be derived from the represented namespace. This
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.14 NamespacesType
  Server . It is formally defined in Table 23 . Table 23 - NamespacesType definition Attribute Value BrowseName NamespacesType IsAbstract False References NodeClass BrowseName Data Type TypeDefinition Modelling Rule Subtype of the BaseObjectType ... ObjectType contains a list of NamespaceMetadataType Objects representing the namespaces in the Server . The BrowseName of an Object shall be derived from the namespace represented by the Object . This
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.2 BaseEventType
  AddressSpace is formally defined in Table 25 . Table 25 - BaseEventType definition Attribute Value BrowseName BaseEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined ... Server does not have a description, it shall return the string part of the BrowseName of the Node associated with the Event . Severity is an indication of the urgency
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.31 BaseModelChangeEventType
  AddressSpace is formally defined in Table 55 . Table 55 - BaseModelChangeEventType definition Attribute Value BrowseName BaseModelChangeEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseEventType defined ... SourceName for Events of this type shall be the String part of the BrowseName of the View ; for the whole AddressSpace it shall be "Server
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.33 SemanticChangeEventType
  AddressSpace is formally defined in Table 57 . Table 57 - SemanticChangeEventType definition Attribute Value BrowseName SemanticChangeEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseEventType defined ... SourceName for Events of this type shall be the String part of the BrowseName of the View , for the whole AddressSpace it shall be "Server". The additional Property
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.12 DataTypeRefinementType definition
  Instances of this ObjectType represent a DataTypeRefinement and are given a unique name. Each BrowseName of a DataTypeRefinement Object shall be unique, i.e., there shall not be two DataTypeRefinement Objects ... Server having the same BrowseName . The ObjectType is formally defined in Table 70 . Table 70 - DataTypeRefinementType definition Attribute Value BrowseName DataTypeRefinementType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.13 SubtypeRestrictionType definition
  Instances of this ObjectType represent a SubtypeRestriction and are given a unique name. Each BrowseName of a SubtypeRestriction Object shall be unique, i.e., there shall not be two SubtypeRestriction Objects ... Server having the same BrowseName . The ObjectType is formally defined in Table 71 . Table 71 - SubtypeRestrictionType definition Attribute Value BrowseName SubtypeRestrictionType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.3 PropertyType
  used as the type definition for all Properties . Properties are defined by their BrowseName and therefore they do not need a specialised type definition. It is not allowed to subtype ... VariableType . It is formally defined in Table 73 . Table 73 - PropertyType definition Attribute Value BrowseName PropertyType IsAbstract False ValueRank -2 (-2 = Any) DataType BaseDataType References NodeClass BrowseName DataType TypeDefinition ModellingRule
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.6 ServerStatusType
  VariableType is formally defined in Table 76 . Table 76 - ServerStatusType definition Attribute Value BrowseName ServerStatusType IsAbstract False ValueRank -1 (-1 = Scalar) DataType ServerStatusDataType References NodeClass BrowseName DataType TypeDefinition Modelling Rule ... NOTE Containing Objects and Variables of these Objects and Variables are defined by their BrowseName defined in the corresponding TypeDefinitionNode . The NodeId is defined by the composed symbolic name described
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.9 SamplingIntervalDiagnosticsArrayType
  type will provide a Variable of the SamplingIntervalDiagnosticsType VariableType having the sampling rate as BrowseName . The VariableType is formally defined in Table 79 . Table 79 - SamplingIntervalDiagnosticsArrayType definition Attribute Value BrowseName ... IsAbstract False ValueRank 1 (1 = OneDimension) ArrayDimensions {0} (0 = UnknownSize) DataType SamplingIntervalDiagnosticsDataType References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseDataVariableType defined in 7.4 . HasComponent Variable SamplingIntervalDiagnostics SamplingIntervalDiagnosticsDataType
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.11 SubscriptionDiagnosticsArrayType
  this type will provide a Variable of the SubscriptionDiagnosticsType VariableType having the SubscriptionId as BrowseName . The VariableType is formally defined in Table 81 . Table 81 - SubscriptionDiagnosticsArrayType definition Attribute Value BrowseName ... IsAbstract False ValueRank 1 (1 = OneDimension) ArrayDimensions {0} (0 = UnknownSize) DataType SubscriptionDiagnosticsDataType References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseDataVariableType defined in 7.4 . HasComponent Variable SubscriptionDiagnostics SubscriptionDiagnosticsDataType SubscriptionDiagnosticsType
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.13 SessionDiagnosticsArrayType
  this type will provide a Variable of the SessionDiagnosticsVariableType VariableType , having the SessionDiagnostics as BrowseName . Those Variables will also be referenced by the SessionDiagnostics Objects defined by their type ... VariableType is formally defined in Table 83 . Table 83 - SessionDiagnosticsArrayType definition Attribute Value BrowseName SessionDiagnosticsArrayType IsAbstract False ValueRank 1 (1 = OneDimension) ArrayDimensions {0} (0 = UnknownSize) DataType SessionDiagnosticsDataType References NodeClass BrowseName
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.15 SessionSecurityDiagnosticsArrayType
  this type will provide a Variable of the SessionSecurityDiagnosticsType VariableType , having the SessionSecurityDiagnostics as BrowseName . Those Variables will also be referenced by the SessionDiagnostics Objects defined by their type ... users, but only to authorised users. Table 85 - SessionSecurityDiagnosticsArrayType definition Attribute Value BrowseName SessionSecurityDiagnosticsArrayType IsAbstract False ValueRank 1 (1 = OneDimension) ArrayDimensions {0} (0 = UnknownSize) DataType SessionSecurityDiagnosticsDataType References Node Class Browse
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  7.29 BitFieldType
  field defined by the BitFieldDefinitions shall also be exposed as a child DataVariable . The BrowseName of the DataVariable shall be the same as the BitFieldDefinition name field and the NamespaceIndex ... BrowseName shall be the same as the BitFieldDefinition name field's NamespaceIndex . Optional bit fields may be defined by using the Optional Modeling Rule for the child DataVariable which represents
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  A.3 Numeric Node Ids
  SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node or the BrowsePath for an Instance Node that appears ... file. The BrowsePath for an instance Node may be constructed by appending the BrowseName of the instance Node to BrowseName for the containing instance or type. A '_' character is used
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.2 UANodeSet
  which can be added to any Node . The Node in the NodeSet defines the BrowseName , DataType and ValueRank . The UANodeSet aliases are a list of string substitutions for NodeIds . UANodeSet
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.3 UANode
  serialized as a String . The syntax of the serialized String is defined in 5.3.1.10 . BrowseName QualifiedName A QualifiedName serialized as a String with the form: <namespace index ... class/field name in auto generated code. It should only be specified if the BrowseName cannot be used for this purpose. This field does not appear in the AddressSpace
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.9 UAMethod
  single Object Node . It is the NodeId of the UAMethod with the same BrowseName contained in the TypeDefinition associated with the Object Node . If the TypeDefinition overrides a Method inherited
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.12 DataTypeDefinition
  unique name for the data type. This name should be the same as the BrowseName for the containing DataType. SymbolicName String A symbolic name for the data type that
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  6.4.3 SyntaxReferenceEntryType ObjectType definition
  this type are not required in the AddressSpace . Table 48 - SyntaxReferenceEntryType Definition Attribute Value BrowseName SyntaxReferenceEntryType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the DictionaryEntryType defined ... corresponding field in Table 38 . The namespace for the NodeId and the BrowseName Attributes of instances of the SyntaxReferenceEntryType shall be the URI of the Syntax Reference as defined
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.3.1.2 Branch
  level branch (the root) should be represented by an Object where the BrowseName is the Server ProgId. The OPC DA Address space hierarchy is discovered using the ChangeBrowsePosition from ... Items and Properties. The name returned from the BrowseOPCItemIds enumString is used as the BrowseName and the DisplayName for each Branch. See also clause A.3.1.5 . The ItemId obtained using
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.3.1.3 Item
  types The name of the item in the DA Server is used as the BrowseName and the DisplayName for the Node in the COM UA Wrapper. See also clause A.3.1.5
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.3.1.4 Property
  Property: The description of a property in the DA server is used as the BrowseName and the DisplayName of the Node in the COM UA Wrapper. The PropertyID and ItemID
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.4.2.2 Object Nodes
  assigned 3 properties: UA Browse Name (Property ID: 613): The value of the BrowseName attribute of the node in the OPC UA Server is assigned to this property. UA Description
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.4.2.3 Variable Nodes
  assigned to this property. UA Browse Name (Property ID: 613): The value of the BrowseName attribute of the node in the OPC UA Server is assigned to this property
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.1 Event areas
  flag set to True. The root Area is represented by an Object with a BrowseName that depends on the UA Server . It is always the target of a HasNotifier Reference ... GetQualifiedAreaName Method s. The Area name returned by BrowseOPCAreas is used as the BrowseName and DisplayName for each Area Node . The QualifiedAreaName is used to construct the NodeId . The NamespaceURI
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.3 Event categories
  represented in the UA Server as ObjectTypes which are subtypes of BaseEventType . The BrowseName and DisplayName of the ObjectType Node for Simple and Tracking Event Types are constructed by appending
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.4 Event attributes
  targets of HasProperty Reference s from the ObjectTypes which represent the Event Categories. The BrowseName and DisplayName are the description for the Event Attribute . The data type of the Event
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.5 Event subscriptions
  NodeId of BaseConditionClassType Node for non- Condition Event Types. ConditionClassName dwEventType Set to the BrowseName of the ConditionClassType for the Event Category of Condition Event Type. To set "BaseConditionClass
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  4.2.7 Program Control Methods
  Halted state to the Ready state. All Program Control Methods are defined with their BrowseName on the ProgramStateMachineType with the OptionalPlaceholder ModellingRule . As defined in OPC 10000-3 , this rule
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.2.2 HistoricalDataConfigurationType
  formally defined in Table 3 . Instances of the HistoricalDataConfigurationType use the standard BrowseName as defined in 5.2.4 . Table 3 - HistoricalDataConfigurationType definition Attribute Value BrowseName HistoricalDataConfigurationType IsAbstract False References NodeClass BrowseName ... AddressSpace is defined in Table 58 . Table 5 - ExceptionDeviationFormat definition Attribute Value BrowseName ExceptionDeviationFormat IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0:Enumeration type defined
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.2.4 Historical Data Configuration Object
  Table 6 . If a HistoricalDataNode has configuration defined then one instance shall have a BrowseName of 'HA Configuration'. Additional configurations can be defined with different BrowseNames . It is highly recommended ... referenced using the HasHistoricalConfiguration ReferenceType . Table 6 - Historical Access configuration definition Attribute Value BrowseName HA Configuration References Node Class BrowseName DataType TypeDefinition ModellingRule HasTypeDefinition Object Type HistoricalDataConfigurationType Defined in Table
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  5.7.3 Default configuration
  Server Object. If HistoricalDataNodes exist without a referenced configuration, an Object with a BrowseName of " DefaultHAConfiguration " shall be exposed. If HistoricalEventNodes exist without configuration, an object with ... BrowseName of " DefaultHEConfiguration " shall be exposed. For any Node that does not have a referenced historical configuration but does support history, the default appropriate configuration shall be applied
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.7.5 Create Endpoint Workflow
  CertificateGroups Object on the ApplicationConfiguration instance. It is used to create the BrowseName for the new CertificateGroup Object . New CertificateType Required? Checks if a new CertificateType is required. Add CertificateType
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.3.3 CertificateGroupFolderType
  AddressSpace . This type is defined in Table 43 . Table 43 - CertificateGroupFolderType Definition Attribute Value BrowseName 0:CertificateGroupFolderType IsAbstract False References Node Class BrowseName Data Type TypeDefinition Modelling Rule Subtype ... Certificate . This Object shall leave CertificateTypes list empty. Any additional CertificateGroups shall have a BrowseName where the Name is unique within the CertificateGroupFolder
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.3.4 CertificateGroupDataType
  updated at once. The Name of the record is the name portion of the BrowseName of the associated CertificateGroup Object in the AddressSpace . It may not be possible to delete ... AddressSpace is defined in Table 45 . Table 45 - CertificateGroupDataType Definition Attribute Value BrowseName 0:CertificateGroupDataType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0:BaseConfigurationRecordDataType defined
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.5.5 BaseConfigurationRecordDataType
  Object in the AddressSpace then this shall be the Name portion of the BrowseName . If the record does not have a matching Object, then Name is only unique within ... AddressSpace is defined in Table 66 . Table 68 - BaseConfigurationRecordDataType Definition Attribute Value BrowseName 0:BaseConfigurationRecordDataType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0: Structure DataType defined
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.5.8 ConfigurationUpdatedAuditEventType
  ConfigurationFile Object ). The SourceName for Events of this type shall be the BrowseName of the configuration owner. Its representation in the AddressSpace is formally defined in Table 73 . Table ... ConfigurationUpdatedAuditEventType Definition Attribute Value BrowseName 0:ConfigurationUpdatedAuditEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the 0: AuditEventType defined in OPC 10000-5 . 0:HasProperty Variable
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  8.6.3 CreateCredential
  String ProfileUri [in] String[] EndpointUrls [out] NodeId CredentialNodeId ); Argument Description Name This the BrowseName of the new Object . ResourceUri The ResourceUri uniquely identifies the resource that accepts the KeyCredentials ... AddressSpace representation for the CreateCredential Method . Table 134 - CreateCredential Method AddressSpace Definition Attribute Value BrowseName 0:CreateCredential References NodeClass BrowseName DataType TypeDefinition ModellingRule 0:HasProperty Variable 0:InputArguments Argument
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  9.7.5 AuthorizationServiceConfigurationDataType
  updated at once. The Name of the record is the name portion of the BrowseName of the associated AuthorizationServiceConfiguration Object in the AddressSpace . If multiple ServiceCertificates are specified the first ... AddressSpace is defined in Table 160 . Table 160 - AuthorizationServiceConfigurationDataType Definition Attribute Value BrowseName 0:AuthorizationServiceConfigurationDataType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0: BaseConfigurationRecordDataType defined
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  10.2 Handling of OPC UA Namespaces
  create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName ... cannot be used to unambiguously identify a Node . Different Nodes may have the same BrowseName . They are used to build a browse path between two Nodes or to define
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  4.2.2.1 General
  already defined by its type definition. All Instances of the FolderType use the standard BrowseName of 'AggregateFunctions'. The HasComponent Reference is used to relate a ServerCapabilities Object and/or any HistoryServerCapabilitiesType ... AggregateFunctions is formally defined in Table 3 . Table 3 - Aggregate Functions Definition Attribute Value BrowseName AggregateFunctions References Node Class BrowseName DataType TypeDefinition ModellingRule HasTypeDefinition Object Type FolderType Defined
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  4.2.2.2 AggregateFunctionType
  This Object is formally defined in Table 4 . Table 4 - AggregateFunctionType Definition Attribute Value BrowseName AggregateFunctionType IsAbstract False References Node Class BrowseName DataType Type Definition Mod. Rule Subtype ... Description Attribute provides a localized description of the Aggregate . Table 5 specifies the BrowseName and Description Attributes for the standard Aggregate Objects . The description is the localized
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.3.2.4 FieldMetaData
  this field the key in the KeyValuePair structure is the BrowseName of the Property and the value in the KeyValuePair structure is the Value of the Property . If the DataSetMessage ... AddressSpace is defined in Table 8 . Table 8 - FieldMetaData definition Attributes Value BrowseName FieldMetaData IsAbstract False Subtype of Structure defined in OPC 10000-5 . Conformance Units PubSub Parameters Discovery
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.3.8.2 SelectedFields
  SelectedFields by specifying the PublishedEventsType NodeId as typeId in the SimpleAttributeOperand and the BrowseName of the extension field in the browsePath of the SimpleAttributeOperand . The index into the list
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.10.3.2 ParentNodeName
  ParentNodeName This parameter with DataType String defines the BrowseName and DisplayName of the parent Node for the Variables representing the fields of the subscribed DataSet
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.3.2 PublishSubscribeType
  ObjectType is formally defined in Table 232 . Table 232 - PublishSubscribeType definition Attribute Value BrowseName PublishSubscribeType IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of PubSubKeyServiceType defined ... Variable represents a DataSetClass . For each Variable , the Name field of the BrowseName equals the Name in the DataSetMetaData . The Object is formally defined in Table 233 . Table 233 - PublishSubscribeType
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.10.4 Status Object
  Status Object PubSub ObjectTypes that require a status Object add a component with the BrowseName Status
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.12.2 Supported configuration properties
  different PubSub components. A configuration property is described by Variables with the following information: BrowseName of the Variable is used as Key for the property. DataType of the Variable defines
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.13.1 PubSubStatusEventType
  PubSubStatusEventType is formally defined in Table 333 . Table 333 - PubSubStatusEventType definition Attribute Value BrowseName PubSubStatusEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of SystemEventType defined ... PubSubConnectionType , PubSubGroupType , DataSetWriterType or DataSetReaderType Object associated with the Event . The SourceName is the BrowseName of the SourceNode . The ConnectionId Property is the NodeId of the PubSubConnectionType Object associated with
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.6 FiniteStateMachineType
  machine are represented with instances of the StateType ObjectType. Each State shall have a BrowseName which is unique within the StateMachine and shall have a StateNumber which shall also ... StateMachine . Be aware that States in a SubStateMachine may have the same StateNumber or BrowseName as States in the parent machine. A concrete subtype of FiniteStateMachineType shall define at least
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.7 FiniteStateVariableType
  FiniteStateVariableType is formally defined in Table 7 . Table 7 - FiniteStateVariableType definition Attribute Value BrowseName FiniteStateVariableType DataType LocalizedText ValueRank -1 (-1 = Scalar) IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling ... type hierarchy. The Name Property is inherited from StateVariableType. Its Value shall be the BrowseName of one of the State Objects of the FiniteStateMachineType . The Number Property is inherited from
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.8 FiniteTransitionVariableType
  FiniteTransitionVariableType is formally defined in Table 8 . Table 8 - FiniteTransitionVariableType definition Attribute Value BrowseName FiniteTransitionVariableType DataType LocalizedText ValueRank -1 (-1 = Scalar) IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling ... hierarchy. The Name Property is inherited from the TransitionVariableType. Its Value shall be the BrowseName of one of the Transition Objects of the FiniteStateMachineType . The Number Property is inherited from
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.4.19 Special Restrictions on subtyping StateMachines
  State defined on the supertype another Node of the same ObjectType having the same BrowseName and the same StateNumber shall be defined on the subtype. For each Transition defined ... supertype another Node of the same ObjectType having the same BrowseName and the same TransitionNumber shall be defined on the subtype. All references defining the StateMachine ( HasCause , HasEffect , FromState , ToState
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  6.2 AliasNameType ObjectType Definition
  AliasNameType is formally defined in Table 1 . Table 1 - AliasNameType Definition Attribute Value BrowseName AliasNameType IsAbstract False References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined ... ConformanceUnits AliasName Base This ObjectType has no Properties or Variables . The BrowseName of the Object is used as the alias name. The string part of the BrowseName shall
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  7.2 AliasNameDataType
  Table 17 - AliasNameDataType DataType structure Name Type Description AliasNameDataType Structure AliasName QualifiedName The AliasName ( BrowseName of the Node ). ReferencedNodes ExpandedNodeId[] The Nodes referenced by the AliasName . Its representation ... AddressSpace is defined in Table 18 . Table 18 - AliasNameDataType Definition Attribute Value BrowseName AliasNameDataType References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of the Structure defined
• OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names
  7.3 AliasNameVerboseDataType
  Table 19 - AliasNameVerboseDataType DataType structure Name Type Description AliasNameVerboseDataType Structure AliasName QualifiedName The AliasName ( BrowseName of the Node ). ReferencedNodes ExpandedNodeId[] The Nodes referenced by the AliasName . ServerUris String[] The ServerUri ... AddressSpace is defined in Table 20 . Table 20 - AliasNameVerboseDataType Definition Attribute Value BrowseName AliasNameVerboseDataType References Node Class BrowseName DataType TypeDefinition Modelling Rule Subtype of the Structure defined
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  4.2.2 AddRole Method
  combination of the NamespaceUri and RoleName parameters are used to construct the BrowseName for the new Node . The BrowseName shall be unique within the RoleSet Object . If the optional Properties ... NamespaceUri qualifies the RoleName . If this value is null or empty then the resulting BrowseName will be qualified by the Server's NamespaceUri . RoleNodeId The NodeId assigned by the Server
• OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference
  5.3 IRDI ISO/IEC 11179-6 conformant DictionaryEntryType
  Inductive distance sensor, Design of analog output Table 3 - IrdiDictionaryEntryType Definition Attribute Value BrowseName IrdiDictionaryEntryType IsAbstract False References NodeClass BrowseName DataType / TypeDefinition ModellingRule Subtype of the DictionaryEntryType defined ... shall be a unique string. This identifier is used for the NodeId and the BrowseName Attributes of instances of the DictionaryEntryType . The IdentifierType of the NodeId shall be STRING
• OPC-10000-19 – OPC Unified Architecture - Part 19: Dictionary Reference
  5.4 URI based dictionary entry type
  dictionary entries that use URIs as unique identifiers. Table 4 - UriDictionaryEntryType Definition Attribute Value BrowseName UriDictionaryEntryType IsAbstract False References NodeClass BrowseName DataType / TypeDefinition ModellingRule Subtype of the DictionaryEntryType defined ... unique URI string. This identifier is used for the NodeId and the BrowseName Attributes of instances of the DictionaryEntryType . The IdentifierType of the NodeId shall be STRING_1 with
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.1 Overview
  file system is represented by an instance of the FileDirectoryType with the BrowseName FileSystem . All directories below the root directory are represented by instances of the FileDirectoryType or a subtype
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.3.2 FileSystem Object
  file directory structures is declared by aggregating an instance of the FileDirectoryType with the BrowseName FileSystem as illustrated in Figure 1 . Figure 1 - FileSystem example The Object representing the root ... file directory structure shall have the BrowseName FileSystem . An OPC UA Server may have different FileSystem Objects in the AddressSpace . HasComponent is used to reference a FileSystem from aggregating Objects
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  8.1 Signed Ticket Encoding
  subtype is "opc-ticket+json". The type parameter is the name from BrowseName of the Structure . For example, the value for a DeviceIdentityTicketType is: opc-ticket+json;type
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  10.2 Handling of OPC UA Namespaces
  create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName ... cannot be used to unambiguously identify a Node . Different Nodes may have the same BrowseName . They are used to build a browse path between two Nodes or to define
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.5.1.2 IetfBaseNetworkInterfaceType definition
  IetfBaseNetworkInterfaceType is formally defined in Table 58 . Table 58 - IetfBaseNetworkInterfaceType definition Attribute Value BrowseName IetfBaseNetworkInterfaceType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype of the BaseObjectType HasInterface ObjectType ... Object <InterfaceName>   BaseObjectType OP  Conformance Units BNM IETF Interface Base Info The BrowseName of this Object shall be the same as the ifName of the corresponding IETF object
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  5.5.2.4 DeletePriorityMappingEntry method
  InvalidState The state of this ConnectionConfigurationSetType instance is "Processing". Bad_BrowseNameInvalid The BrowseName for the mapping entry is invalid. Table 67 - DeletePriorityMappingEntry Method AddressSpace definition Attribute Value BrowseName ... DeletePriorityMappingEntry References Node Class BrowseName DataType TypeDefinition Other HasProperty Variable InputArguments Argument[] PropertyType
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  A.2 Modelling Examples for PriorityMappingEntries and IetfBaseNetworkInterface
  address variable of type NetworkAddressDataType . If the networkInterface String of the NetworkAddressDataType matches the BrowseName of one Object in the NetworkInterfaces folder, it links the transmission or reception
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  A.3 Connecting LldpPortInformationType and IetfBaseNetworkInterfaceType
  Figure A-4 shows an example of this reference for the IetfBaseNetworkInterface with the BrowseName eth0. Figure A-4 - Connection between LLDP and IetfInterfaces
• OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes
  5.1 Overview
  potentially other Nodes might reference the ReferenceDescription Variable using the HasReferenceDescription ReferenceType . The BrowseName of a ReferenceDescription Variable should be the BrowseName of the ReferenceType , or in case of ambiguities ... prefixed with the BrowseName of the ReferenceType followed by a suffix making the BrowseName unique in that context. In case of an inverse Reference ( IsForward set to FALSE), the BrowseName
• OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler
  10.2 Handling of OPC UA Namespaces
  create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName ... cannot be used to unambiguously identify a Node . Different Nodes may have the same BrowseName . They are used to build a browse path between two Nodes or to define
• OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler
  A.1 Namespace and Identifiers for the Scheduler Information Model
  SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node or the BrowsePath for an Instance Node that appears ... NodeId . The BrowsePath for an Instance Node is constructed by appending the BrowseName of the instance Node to the BrowseName for the containing instance or type. An underscore character
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.1 Overview
  Properties . Because it is instance-specific, the SerializationValue DataType Node is dynamically created. Its BrowseName and NodeId are Server -specific and could be GUID-based. In the Type-based serialization
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.2 Limitations
  characters used in BrowseNames to letters (lower- and uppercase), digits and the underscore ('_'). The BrowseName must not start with a digit. Special characters (e.g. '@', '*', etc.) shall not be used
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.3 ConfigureSerialization Method
  KeyValuePair Structures containing the desired settings. The key field of each Structure contains the BrowseName of a serialization filter Property . The value field contains the desired value ... allowed to be included Table 4 - ConfigureSerialization Method AddressSpace definition Attribute Value BrowseName ConfigureSerialization References NodeClass BrowseName DataType TypeDefinition Other HasProperty Variable InputArguments Argument[] PropertyType M HasProperty Variable OutputArguments Argument
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.6 ConsiderSubElementSerializationProperties Property
  True, SerializationEntities referenced by elements of the SerializationScope which have the same BrowseName as the SerializationEntity referenced by the SerializationStartNode are considered for the SerializationProcess . If false, only the SerializationEntity ... SerializationEntity of a child node in the subtree originating from the SerializationStartNode with the BrowseName "ObjectSerialization" will be considered. "Variable2" has such a SerializationEntity . This SerializationEntity
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.8 CustomMetaDataRef Property
  this Property is the NodeId of this other Variable . A KeyValuePair with the BrowseName of this Variable as key and the NodeId of this Variable as value is added
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.4.2 SerializationFieldDataType of Variables without Children
  children, the Variable is represented by a single Structure field with the BrowseName of the Variable as field name. The SerializationFieldDataType of the Variable equals the DataType of the Variable
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.4.3 SerializationFieldDataType of Variables with Children
  children of the serialized Variable. The name of each of those fields equals the BrowseName of the mapped child. Servers shall make sure that field names are unique
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  5.5 LogRecord structure
  source of the LogRecord , this could be the string-part of the BrowseName of the SourceNode. True Message 0:LocalizedText Provides a human-readable and localizable text description ... AddressSpace is formally defined in Table 10 Table 10 - LogRecord definition Attribute Value BrowseName LogRecord IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0:Structure defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.5 Command CreateConnectionEndpointCmd
  FunctionalEntityNode . The created ConnectionEndpoint shall be of the subtype specified in ConnectionEndpointTypeId. The BrowseName shall be set to Name, and all Variables shall be set according to Parameter . The appropriate ... IsPreconfigured is set to TRUE, a preconfigured ConnectionEndpoint (see 5.5.5 ) shall exist with a BrowseName that matches Name in the ConnectionEndpoints Folder of the FunctionalEntity identified by FunctionalEntityNode. Its ConnectionEndpointTypeId
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.7 PublisherCapabilitiesType
  Object . It is formally defined in Table 27 . Table 27 - PublisherCapabilitiesType definition Attribute Value BrowseName 3:PublisherCapabilitiesType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype ... preconfigured PublishedDataSets (see 5.5.5 ), where the name is the string part of the BrowseName of a PublishedDataSet that is listed in the PublishedDataSets Folder tree of the PublishSubscribe Object
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.8 SubscriberCapabilitiesType
  Object . It is formally defined in Table 28 . Table 28 - SubscriberCapabilitiesType definition Attribute Value BrowseName 3:SubscriberCapabilitiesType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype ... preconfigured StandaloneSubscribedDataSets (see 5.5.5 ), where the name is the string part of the BrowseName of a StandaloneSubscribedDataSet that is listed in the SubscribedDataSets Folder tree of the PublishSubscribe Object
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.3 VerifyAsset method
  AssetVerificationModeEnum . ExpectedVerificationVariables An array of KeyValuePair containing verification Variables . Key shall be the BrowseName of the Variable to verify (relative to the Asset this Method is being called ... defined in Table 33 . Table 33 - VerificationVariablesErrors StatusCodes Result Code Description Bad_BrowseNameInvalid The BrowseName for the verification Variable is invalid or was passed more than once. Bad_TypeMismatch
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.2 ConnectionManagerType definition
  ConnectionManagerType is formally defined in Table 77 . Table 77 - ConnectionManagerType definition Attribute Value BrowseName 4:ConnectionManagerType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype of the 0:BaseObjectType ... defined in Table 78 . Table 78 - ConnectionManagerType additional subcomponents BrowsePath References Node Class BrowseName DataType TypeDefinition Others 5:Diagnostics 0:HasComponent Variable 4:EstablishCallCount 0:UInt32 0:BaseDataVariableType
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.12.2 ConnectionEndpointParameterType definition
  ConnectionEndpointParameterType is formally defined in Table 96 . Table 96 - ConnectionEndpointParameterType definition Attribute Value BrowseName 4:ConnectionEndpointParameterType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype of the 0:BaseObjectType ... PreconfiguredSubscribedDataSet 0:String 0:BaseDataVariableType O ConformanceUnits UAFX ConnectionManager Base Name specifies the BrowseName of the ConnectionEndpoint to create. This name shall be unique within the FunctionalEntity's ConnectionEndpoints Folder
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  8.3 AuditConnectionCleanupEventType
  AddressSpace is formally defined in Table 110 . Table 110 - AuditConnectionCleanupEventType definition Attribute Value BrowseName 3:AuditConnectionCleanupEventType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 3:AuditUaFxEventType, which ... this Event shall be the FunctionalEntity that contained the RemovedEndpoint . RemovedEndpoint identifies the BrowseName of the ConnectionEndpoint that was removed. RelatedEndpoint points to the former related ConnectionEndpoint (i.e., the other
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  8.9 EstablishConnectionErrorEventType
  structure. The mapping also applies to related actions. Table 116 - EstablishConnectionErrorEventType definition Attribute Value BrowseName 4:EstablishConnectionErrorEventType IsAbstract True References Node Class BrowseName Note Subtype of the 0:BaseLogEventType. ConformanceUnits ... NodeId of the ConnectionConfigurationSet that is being processed . SourceName shall be the BrowseName of the Connection that was being created. If the error is not related to a specific Connection
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  8.10 CloseConnectionErrrorEventType
  AddressSpace is formally defined in Table 117 . Table 117 - CloseConnectionErrorEventType Attribute Value BrowseName 4:CloseConnectionErrorEventType IsAbstract True References Node Class BrowseName Note Subtype of the 0:BaseLogEventType. ConformanceUnits UAFX ConnectionManager ... NodeId of the ConnectionConfigurationSet that the connection belonged to . SourceName shall be the BrowseName of the Connection that was being closed. Message describes the issue. It shall include a description
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.18.2 ConnectionEndpointParameterDataType definition
  Structure Subtype of Structure defined in OPC 10000-5 Name 0:String Specifies the BrowseName of the ConnectionEndpoint . ConnectionEndpointTypeId 0:NodeId Specifies the well-known NodeId of the type definition ... AddressSpace is formally defined in Table 159 . Table 159 - ConnectionEndpointParameterDataType definition Attribute Value BrowseName 2:ConnectionEndpointParameterDataType IsAbstract True References NodeClass BrowseName Definition Subtype of the 0:Structure defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.19 ConnectionDiagnosticsDataType
  Description ConnectionDiagnosticsDataType Structure Subtype of Structure defined in OPC 10000-5 Name 0:QualifiedName BrowseName of the related < Connection > Node in the ConnectionConfigurationSet . LastActivity 4:LastActivityMask The last ... AddressSpace is formally defined in Table 163 . Table 163 - ConnectionDiagnosticsDataType definition Attribute Value BrowseName 4:ConnectionDiagnosticsDataType IsAbstract False References NodeClass BrowseName Definition Subtype of the 0:Structure defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.40 PortableRelativePathElement
  followed. Subtypes are included if this value is TRUE. TargetName 0:PortableQualifiedName The BrowseName of the target node. The final element may have an empty TargetName . In this situation ... AddressSpace is formally defined in Table 205 . Table 205 - PortableRelativePathElement definition Attribute Value BrowseName 4:PortableRelativePathElement IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0:Structure defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  14.2 Handling of OPC UA namespaces
  uses namespaces to create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike ... NodeIds , the BrowseName cannot be used to unambiguously identify a Node . Different Nodes may have the same BrowseName . They are used to build a browse path between two Nodes
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.3 ConnectionConfigurationSetConfDataType
  Type Description Allow Subtypes ConnectionConfigurationSetConfDataType Structure Subtype of Structure defined in OPC 10000-5 BrowseName 0:String String part of the BrowseName of the ConnectionConfigurationSet . False ConnectionConfigurationSetFolder 0:String[] Optional ... AddressSpace is formally defined in Table F.2 . Table F.2 - ConnectionConfigurationSetConfDataType definition Attribute Value BrowseName 4:ConnectionConfigurationSetConfDataType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the 0:Structure defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.5 ConnectionEndpointConfigurationConfDataType
  Boolean Flag indicating if the FunctionalEntityNode options can be modified. True Name 0:String BrowseName of the ConnectionEndpoint to create in the AutomationComponent . False NameSelection 0:String[] Selection list options ... AddressSpace is formally defined in Table F.6 . Table F.6 - ConnectionEndpointConfigurationConfDataType definition Attribute Value BrowseName 4:ConnectionEndpointConfigurationConfDataType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the 0:Structure defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.6 CommunicationFlowConfigurationConfDataType
  Name Type Description Optional CommunicationFlowConfigurationConfDataType Structure Subtype of Structure defined in OPC 10000-5 BrowseName 0:String BrowseName of the information flow. False FlowProperties 0:KeyValuePair[] The KeyValuePair array provides ... AddressSpace is formally defined in Table F.9 . Table F.9 - CommunicationFlowConfigurationConfDataType definition Attribute Value BrowseName 4:CommunicationFlowConfigurationConfDataType IsAbstract True References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the 0:Structure defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.8 SubscriberConfigurationConfDataType
  Name Type Description Optional SubscriberConfigurationConfDataType Structure Subtype of Structure defined in OPC 10000-5 BrowseName 0:String BrowseName of the flow. False Address 4:AddressSelectionDataType Address specifies the network address ... AddressSpace is formally defined in Table F.13 . Table F.13 - SubscriberConfigurationConfDataType definition Attribute Value BrowseName 4:SubscriberConfigurationConfDataType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the 0:Structure defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.9 AutomationComponentConfigurationConfDataType
  Type Description Allow Subtypes AutomationComponentConfigurationConfDataType Structure Subtype of Structure defined in OPC 10000-5 BrowseName 0:String BrowseName of the AutomationComponent . False AutomationComponentNode 4:NodeIdentifier AutomationComponentNode specifies the AutomationComponent that ... AddressSpace is formally defined in Table F.15 . Table F.15 - AutomationComponentConfigurationConfDataType definition Attribute Value BrowseName 4:AutomationComponentConfigurationConfDataType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the 0:Structure defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.11 ServerAddressConfDataType
  Name Type Description Optional ServerAddressConfDataType Structure Subtype of Structure defined in OPC 10000-5 BrowseName 0:String BrowseName of the Server address. False Address 0:UriString Address is specified ... AddressSpace is formally defined in Table F.19 . Table F.19 - ServerAddressConfDataType definition Attribute Value BrowseName 4:ServerAddressConfDataType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the 0:Structure defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.3.3.1 CloseAndUpdate signature
  F.40 - CloseAndUpdate OperationResult Element Result Codes ResultCode Description Bad_BrowseNameDuplicated A ConnectionConfigurationSet with the BrowseName already exists in the ConnectionConfigurationSetFolder . The ConnectionConfigurationSet cannot be added. Bad_NoMatch A ConnectionConfigurationSet with ... BrowseName does not exist in the ConnectionConfigurationSetFolder . The ConnectionConfigurationSet cannot be removed or replaced. Bad_NothingToDo No ConnectionConfigurationSetOperation was specified. Bad_InvalidArgument An invalid combination of ConnectionConfigurationSetOperation
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.3.3.2.1 Overview
  CloseAndUpdate Method allows for adding, removing, or replacing ConnectionConfigurationSets . ConnectionConfigurationSets are addressed by BrowseName and ConnectionConfigurationSetFolder
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.3.3.2.3 ElementRemove
  removes the ConnectionConfigurationSet from the ConnectionConfigurationSetFolder. For ElementRemove, all elements of the ConnectionConfigurationSetConfDataType except BrowseName and ConnectionConfigurationSetFolder are ignored and may be set to null or empty by the caller
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.3.4 ConnectionConfigurationSetOperation
  configuration. The ConnectionConfigurationSet to be removed is identified via the string part of the BrowseName and the ConnectionConfigurationSetFolder . All other elements in the ConnectionConfigurationSetConfDataType are ignored in this case ... configuration. The ConnectionConfigurationSet to be replaced is identified via the string part of the BrowseName and the ConnectionConfigurationSetFolder . Bits 3:7 are reserved for future use. The ConnectionConfigurationSetOperation representation
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.4.2 Application and QoS engineering
  PubSubCommunicationFlowConfiguration sender and receiver Address parameters. A NetworkInterface Variable may either be the BrowseName of a physical interface or a VLAN interface. The NetworkInterface Variable may also
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  6.5.3 Network interface representation and default configuration
  UAFX Station shall at least provide the default VLAN interface with the BrowseName as defined in Table 2 and a HasLowerLayerInterface reference to the respective physical network for each ... shall assume the value defined in Table 2 . Table 2 - Default VLAN interface values BrowseName VlanId (default) <physical-interface>. 100 Note: The BrowseName of the default VLAN interface
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  A.9 Instance mapping
  given to setting the URIs properly to reflect the correct NamespaceUri for both the BrowseName and the Node . In the InstanceHierarchy, an empty or missing NamespaceUri (of the BrowseName ... cases, the URI attributes shall contain valid URIs that reflect the correct Node and BrowseName URIs
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.1 Node definitions
  description of the value. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being ... defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition. Table
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.2 Additional References
  type or well-known instance, uniquely identified within a namespace by the BrowseName . References can be to any other Node
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.2.1 NodeIds
  actual NodeIds . The symbolic name of each Node defined in this document is its BrowseName , or, when it is part of another Node , the BrowseName of the other Node ... BrowseName of itself. In this case "part of" means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.2.2 BrowseNames
  InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended ... BrowseName is not defined by this document, a namespace index prefix is added to the BrowseName (e.g., prefix '0' leading to '0:EngineeringUnits' or prefix '2' leading to '2:DeviceRevision
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.3.1 General
  DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical to the BrowseName of the Node for the LocaleId "en". Whether the server provides translated names
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.4.1 Model
  FunctionalGroup . FunctionalGroups can be nested. FunctionalGroups can directly be instantiated. In this case, the BrowseName of a FunctionalGroup should indicate its purpose. A list of well-known BrowseNames ... formally defined in Table 14 . Figure 3 - FunctionalGroupType Table 14 - FunctionalGroupType definition Attribute Value BrowseName 1:FunctionalGroupType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0:FolderType
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.4.2 Well-Known FunctionalGroup BrowseNames
  FunctionalGroup that corresponds to the described purpose, they should use the well-known BrowseName with the Namespace of this specification. Table 15 - Well-Known 1:FunctionalGroupType BrowseNames BrowseName Purpose Configuration
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.5.6 SupportInfo Interface
  Table 27 . Figure 8 - Support information Interface Table 27 - ISupportInfoType definition Attribute Value BrowseName 1:ISupportInfoType IsAbstract True References NodeClass BrowseName DataType TypeDefinition Other Subtype of the BaseInterfaceType defined ... Table 28 . Table 28 - 1:ISupportInfoType Additional Subcomponents Source Path References Node Class BrowseName Data Type TypeDefinition Other 1:DeviceTypeImage 0:HasComponent Variable 1:<ImageIdentifier> 0:Image
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  5.2 ProtocolType
  protocol that is supported by a Device (respectively by its ConnectionPoint ) or Network . The BrowseName of each instance of a ProtocolType shall define the Communication Profile (see Figure 18 ). Figure ... hierarchy with instances that represent specific communication profiles Table 45 - ProtocolType definition Attribute Value BrowseName 1:ProtocolType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0:BaseObjectType
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.3.1 General
  online data for a topology element are kept in an associated Object with the BrowseName Online as illustrated in Figure 27 . The Online Object is referenced via an IsOnline Reference ... offline ParameterSet and its corresponding counterpart in the online ParameterSet shall have the same BrowseName . Their NodeIds shall be different, though, since this is the identifier passed by the Client
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.4.3 TransferServices Object
  This Object is used as container for the TransferServices Methods and shall have the BrowseName Transfer . HasComponent is used to reference from a Device to its "TransferServices" Object
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  7.2 LockingServices Type
  formally defined in Table 65 . Figure 31 - LockingServicesType Table 65 - LockingServicesType definition Attribute Value BrowseName 1:LockingServicesType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0:BaseObjectType ... DefaultInstanceBrowseName Property - defined in OPC 10000-3 - is used to specify the recommended BrowseName for instances of the LockingServicesType . Its Value is defined in Table 66 . Table 66 - LockingServicesType Attribute
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  7.3 LockingServices Object
  used as container for the LockingServices Methods and Properties and should have the BrowseName Lock . It shall be referenced using HasComponent or HasAddIn from the lock-owner Object (for example
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.3.11 AddIn model
  Identification FunctionalGroup (see B.2 ) that implements IVendorNameplateType . For the AddIn instance the fixed BrowseName "SoftwareUpdate" shall be used. This model gives any device, hardware- or software-component
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.4.1.14 DefaultInstanceBrowseName
  AddIn model as specified in 8.3.11 . It is used to specify the BrowseName of the instance of the SoftwareUpdateType . It always has the value "SoftwareUpdate". Table 77 - SoftwareUpdateType
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.7.3 Package metadata
  SoftwareUpdate Only for solution packages (see 8.7.5 ) True Table 121 - PackageMetadata definition Attribute Value BrowseName 2:PackageMetadata IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of 0:Structure defined ... target Node on the device. False Table 123 - UpdateTarget definition Attribute Value BrowseName 2:UpdateTarget IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of 0:Structure defined
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  12.2 Handling of OPC UA namespaces
  create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName ... cannot be used to unambiguously identify a Node . Different Nodes can have the same BrowseName . They are used to build a browse path between two nodes or to define
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.1 Node definitions
  description of the value. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being ... defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition. Table
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.2 Additional References
  type or well-known instance, uniquely identified within a namespace by the BrowseName . References can be to any other Node
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.2.1 NodeIds
  actual NodeIds . The symbolic name of each Node defined in this document is its BrowseName , or, when it is part of another Node , the BrowseName of the other Node ... BrowseName of itself. In this case "part of" means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.2.2 BrowseNames
  InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended ... BrowseName is not defined by this document, a namespace index prefix is added to the BrowseName (e.g., prefix '0' leading to '0:EngineeringUnits' or prefix '2' leading to '2:DeviceRevision
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.3.1 General
  DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical to the BrowseName of the Node for the LocaleId "en". Whether the server provides translated names
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  7 Identification of Asset
  Different Options for Identification of Asset The 2: Identification Object shall have the BrowseName 2: Identification and shall be referenced with a hierarchical Reference from the Object representing an asset
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  10.5.2 DocumentationLinksType
  Assets. It is formally defined in Table 29 . Table 29 - DocumentationLinksType Definition Attribute Value BrowseName DocumentationLinksType IsAbstract False Description AddIn to link documentation provided by the manufacturer ... user. References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0:BaseObjectType Type defined in OPC 10000-5 0:HasProperty Variable 0:DefaultInstanceBrowseName 0:QualifiedName PropertyType 0:HasComponent Variable
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  10.5.3 AddLink Method
  should be writable, so the end-user can change the URI. In addition, the BrowseName , DisplayName , and Description might be writable. Servers might restrict the execution of this Method ... Arguments and AddressSpace representation, respectively. Signature AddLink ( [in] 0:UriString LinkToExternalSource, [in] 0:QualifiedName BrowseName, [in] 0:LocalizedText DisplayName, [in] 0:LocalizedText Description, [out] 0:NodeId LinkVariable); Table 31 - AddLink
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  10.6 Requirements
  used. This specification just defines the use of the standardized BrowseName "Requirements" (defined in the Namespace of this specification). Servers might provide the requirements using different access paths
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  10.7 Capabilities
  used. This specification just defines the use of the standardized BrowseName "Capabilities" (defined in the Namespace of this specification). Servers might provide the capabilities using different access paths
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  13.2 Local Time
  used to expose the local time of the asset, i.e. a Property with BrowseName 0: LocalTime having the DataType 0: TimeZoneDataType or a subtype. Servers may set the 0: LocalTime
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  13.3.2 HierarchicalLocation Property
  Property Each asset exposing the hierarchical location as Property has a Property with the BrowseName "HierarchicalLocation" (defined in the Namespace of this specification) and the DataType String
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  13.4.2 OperationalLocation Property
  Property Each asset exposing the operational location as Property has a Property with the BrowseName "OperationalLocation" (defined in the Namespace of this specification) and the DataType String
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  13.5 Digital Location
  Each digital asset exposing the digital location has a Property with the BrowseName "DigitalLocation" (defined in the Namespace of this specification) and the DataType String or a subtype
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  16.2 Handling of OPC UA Namespaces
  create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName ... cannot be used to unambiguously identify a Node . Different Nodes may have the same BrowseName . They are used to build a browse path between two Nodes or to define
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.1 Node definitions
  description of the value. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being ... defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition. Table
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.2 Additional References
  type or well-known instance, uniquely identified within a namespace by the BrowseName . References can be to any other Node
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.2.1 NodeIds
  actual NodeIds . The symbolic name of each Node defined in this document is its BrowseName , or, when it is part of another Node , the BrowseName of the other Node ... BrowseName of itself. In this case "part of" means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.2.2 BrowseNames
  InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended ... BrowseName is not defined by this document, a namespace index prefix is added to the BrowseName (e.g., prefix '0' leading to '0:EngineeringUnits' or prefix '2' leading to '2:DeviceRevision
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.3.1 General
  DisplayName is a LocalizedText . Each Server shall provide the DisplayName identical to the BrowseName of the Node for the LocaleId "en" unless specified differently in the specification. Whether
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  8.2 Handling of OPC UA Namespaces
  create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName ... cannot be used to unambiguously identify a Node . Different Nodes may have the same BrowseName . They are used to build a browse path between two Nodes or to define
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.1 Conventions for Node descriptions
  description of the value. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being ... defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition. Table
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.1.1 Additional References
  type or well-known instance, uniquely identified within a namespace by the BrowseName . References can be to any other Node
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.2.1 NodeIds
  actual NodeIds . The symbolic name of each Node defined in this document is its BrowseName , or, when it is part of another Node , the BrowseName of the other Node ... BrowseName of itself. In this case "part of" means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.2.2 BrowseNames
  InstanceDeclarations of NodeClass Object and Variable that are placeholders ( OptionalPlaceholder and MandatoryPlaceholder ModellingRule ), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended ... BrowseName is not defined by this document, a namespace index prefix is added to the BrowseName (e.g., prefix '0' leading to '0:EngineeringUnits' or prefix '2' leading to '2:DeviceRevision
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.3.1 General
  DisplayName is a LocalizedText . Each server shall provide the DisplayName identical to the BrowseName of the Node for the LocaleId "en". Whether the server provides translated names
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  9.2 Handling of OPC UA Namespaces
  create unique identifiers across different naming authorities. The Attributes NodeId and BrowseName are identifiers. A Node in the UA AddressSpace is unambiguously identified using a NodeId . Unlike NodeIds , the BrowseName ... cannot be used to unambiguously identify a Node . Different Nodes may have the same BrowseName . They are used to build a browse path between two Nodes or to define
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.1.1 Node definitions
  description of the value. References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass . If the TargetNode is a component of the Node being ... defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition. Table
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.1.2 Additional References
  type or well-known instance, uniquely identified within a namespace by the BrowseName . References can be to any other Node
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.2.1 NodeIds
  actual NodeIds . The symbolic name of each Node defined in this document is its BrowseName , or, when it is part of another Node , the BrowseName of the other Node ... BrowseName of itself. In this case "part of" means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part