Search

200 result(s) for TypeDefinition

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.2 Creating an Instance
  hierarchical Reference that has the same BrowsePath as an InstanceDeclaration of its TypeDefinition which has an optional or mandatory ModellingRule except for the one based on the InstanceDeclaration . Figure
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.4 OptionalPlaceholder
  intention of the ModellingRule OptionalPlaceholder is to expose the information that a complex TypeDefinition expects from instances of the TypeDefinition to add instances with specific References without defining BrowseNames ... Folder. The ModellingRule OptionalPlaceholder adds no additional constraints on instances of the TypeDefinition . It just provides useful information when exposing a TypeDefinition . When the InstanceDeclaration is complex, i.e. it references
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  6.4.4.4.5 MandatoryPlaceholder
  similar intention as the ModellingRule OptionalPlaceholder . It exposes the information that a TypeDefinition expects of instances of the TypeDefinition to add instances defined by the InstanceDeclaration . However, MandatoryPlaceholder requires that ... ModellingRule MandatoryPlaceholder requires that each instance provides at least one instance with the TypeDefinition of the InstanceDeclaration or a subtype, and is referenced with the same ReferenceType or a subtype
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  C.2.3 Extended notation
  from an Object or Variable to its ObjectType or VariableType the name of the TypeDefinition can be added to the text used in the Node . The TypeDefinition shall either ... additionally is the SourceNode of a HasTypeDefinition . Figure C.2 - Example of using a TypeDefinition inside a Node To display Attributes of a Node additional text can be put inside
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.4.1 Description
  delete additional Nodes and References like child Nodes that exist based on a TypeDefinition . The behaviour is Server specific. When any of the Nodes deleted by an invocation of this
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.1 Overview
  BrowseNames . SimpleAttribute Specifies any Attribute of an Object or Variable Node using a TypeDefinition and a relative path constructed from BrowseNames
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.4.5 SimpleAttributeOperand
  Variable . If this list is empty the Node is the instance of the TypeDefinition . attributeId IntegerId Id of the Attribute . The IntegerId is defined in 7.19 . The Value Attribute shall
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.9 UAMethod
  NodeId of the UAMethod with the same BrowseName contained in the TypeDefinition associated with the Object Node . If the TypeDefinition overrides a Method inherited from a base ObjectType then this
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.15 Example
  /Definition> </UADataType> This Node is an instance of an Object TypeDefinition Node defined in another InformationModel (ns=2;i=341). It has a single Property which ... /References> </UAObject> This Node is an instance of a Variable TypeDefinition Node defined in base OPC UA InformationModel (i=68). The DataType is the base type
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.4 Address Space model
  DataItem is represented by a DataVariable with a specific set of Attribute s. The TypeDefinition reference indicates the type of the DataItem (in this case the AnalogItemType ). Additional characteristics
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.3.1.4 Property
  server is represented in the COM UA Wrapper as a Variable with TypeDefinition as PropertyType . The properties for an item are retrieved using the QueryAvailableProperties call in the DA server
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.1 Event areas
  represented in the A&E COM UA Wrapper as Objects with a TypeDefinition of BaseObjectType . The EventNotifier Attribute for these Objects always has the SubscribeToEvents flag set to True
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  D.2.2 Event sources
  represented in the A&E COM UA Wrapper as Objects with a TypeDefinition of BaseObjectType . If the A&E COM Server supports source filtering then the SubscribeToEvents flag
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  5.1 General
  FiniteStateMachineType and basic ObjectType models presented in OPC 10000-16 . Each Program has a Type Definition that is the subtype of the FiniteStateMachineType. The ProgramStateMachineType describes the Finite State Machine
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.9.2 CertificateDirectoryType
  CertificateDirectoryType This ObjectType is the TypeDefinition for the root of the CertificateManager AddressSpace . It provides additional Methods for Certificate management which are shown in Table 74 . Table 74 - CertificateDirectoryType ObjectType ... Definition Attribute Value BrowseName 2:CertificateDirectoryType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the 2: DirectoryType defined in 6.5.3 . 0:Organizes Object 2:CertificateGroups 0:CertificateGroup
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  8.5.4 KeyCredentialServiceType
  KeyCredentialServiceType This ObjectType is the TypeDefinition for an Object that allows the management of KeyCredentials . It is defined in Table 125 . Table 125 - KeyCredentialServiceType Definition Attribute Value BrowseName 2:KeyCredentialServiceType ... IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in OPC 10000-5 . 0:HasProperty Variable 2:ResourceUri 0:String 0:PropertyType Mandatory 0:HasProperty
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  8.6.2 KeyCredentialConfigurationFolderType
  KeyCredentialConfigurationFolderType This ObjectType is the TypeDefinition for an Folder Object that contains the KeyCredentialConfiguration Objects which may be accessed via the Server . Table 133 - KeyCredentialConfigurationFolderType Definition Attribute Value BrowseName ... KeyCredentialConfigurationFolderType IsAbstract False References NodeClass BrowseName TypeDefinition Modelling Rule Subtype of the 0: FolderType defined in OPC 10000-5 . 0:HasComponent Object 0:<ServiceName> 0:KeyCredentialConfigurationType Optional Placeholder
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  8.6.5 KeyCredentialConfigurationType
  KeyCredentialConfigurationType This ObjectType is the TypeDefinition for an Object that allows the configuration of KeyCredentials used by the Server . It also includes basic status information which report problems accessing ... KeyCredentialConfigurationType Definition Attribute Value BrowseName 0:KeyCredentialConfigurationType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in OPC 10000-5 . 0:HasProperty Variable 0:ResourceUri
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  9.6.4 AuthorizationServiceType
  AuthorizationServiceType This ObjectType is the TypeDefinition for an Object that allows access to an AuthorizationService . It is defined in Table 147 . Table 147 - AuthorizationServiceType Definition Attribute Value BrowseName 2:AuthorizationServiceType ... IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the BaseObjectType defined in OPC 10000-5 . 0:HasProperty Variable 2:ServiceUri 0:String 0:PropertyType Mandatory 0:HasProperty
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  9.7.4 AuthorizationServiceConfigurationType
  AuthorizationServiceConfigurationType This ObjectType is the TypeDefinition for an Object that allows the configuration of an AuthorizationService used by a Server . It is defined in Table 158 . Table 158 - AuthorizationServiceConfigurationType Definition ... Attribute Value BrowseName 0:AuthorizationServiceConfigurationType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Modelling Rule Subtype of the 0:BaseObjectType defined in OPC 10000-5 . 0:HasProperty Variable 0:ServiceUri
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns can be omitted and only a Comment column is introduced to point
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Other BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  4.4.1 Model
  FunctionalGroupType definition Attribute Value BrowseName 1:FunctionalGroupType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of the 0:FolderType defined in OPC 10000-5 0:HasComponent Object ... part of) their References . If a FunctionalGroup can be hidden on an instance the TypeDefinition shall use an appropriate ModellingRule like "Optional". If desirable, Nodes can be also
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  7 Identification of Asset
  ComponentType or 2: DeviceType . An Object representing an asset can have the TypeDefinition 2: ComponentType , 2: DeviceType , or a subtype of one of those ObjectTypes and thus containing the identification ... Object representing an asset can either directly implement those interfaces, or has a TypeDefinition directly or indirectly implementing the interfaces. Usage of 2: Identification Object . An Object representing an asset
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  9.2 Overall health status of an asset
  This can be done either directly on the instance (X:Asset1) or via the TypeDefinition (X:Asset2), as shown in Figure 3 . However, it is also allowed to just provide
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.1 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.1.1 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.1.2 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.1.3 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  7.2 SpatialLocationType
  Value BrowseName SpatialLocationType IsAbstract True ValueRank -2 (Any) DataType BaseDataType References NodeClass BrowseName DataType TypeDefinition Other Subtype of the RelativeValueType defined in 7.1 0:HasComponent Variable Position 0:BaseDataType ... NodeId 0:BaseDataVariableType M The Variable Position informs about a position. Note that the TypeDefinition is not defined in detail, so it is assumed to define, while subtyping from SpatialLocationType
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.1.2 Additional References
  additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type additional subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  3.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  3.4.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  3.4.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-10101 – OPC UA for WoT Binding
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  3.4.1 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 4 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30020 – MDIS OPC UA Companion Specification
  4.1 MDIS definitions
  additional details. ObjectType A Node that represents the TypeDefinition for an Object . See OPC 10000-3 and OPC 10000-5 for additional details. Profile A specific set of capabilities ... additional details. ReferenceType A Node that represents the TypeDefinition of a Reference . The ReferenceType specifies the semantics of a Reference . The name of a ReferenceType identifies how source Nodes
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.4.1 Concepts
  Space Object and Variable Nodes are called Instance Nodes and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship ... between an instance and its TypeDefinition . Type Nodes are templates that define all of the children that can be present in an instance of the type. In the example
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.4.2 Namespaces
  different InformationModels without conflict. The BrowseName is used to identify the children within a TypeDefinition . Instances of a TypeDefinition are expected to have children with the same BrowseName s. TypeDefinitions
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.4.3 Companion Specifications
  Example ObjectType Definition Attribute Value BrowseName BoilerType IsAbstract False Reference NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseObjectType from OPC 10000-3 . 0:HasProperty Variable Pressure Double 0:PropertyType ... Value accessible via the Node (only used for Variable NodeClass Nodes ) and the TypeDefinition is the ObjectType or VariableType for the child. The ModellingRule indicates whether a child is Mandatory
• OPC-30020 – MDIS OPC UA Companion Specification
  10.5.4 Object Aggregation Example
  WaterFlow (32 bit, float) OilFlow (32 bit, float) The following figure illustrates the resulting TypeDefinition with example Object instances. It includes three instances of MDISInstrumentObjectType Objects that represent the flows
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  5.1 Modelling concepts
  shows an example for mapping BACnet properties to OPC UA built-in concepts like TypeDefinition , Attributes or standard OPC UA Properties . Figure 6 - Mapping to OPC UA Attributes and Properties ... BACnet property Object_Type is mapped to the TypeDefinition of the OPC UA Object instance. The BACnet properties Object_Name, Description and Update_Interval are mapped
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.4.3.6 Object EventReporting
  declaration Object EventReporting overrides definitions of the BACnetEventReportingType . The EventAlgorithm component is changed to TypeDefinition BACnetOutOfRangeAlgorithmType and ModellingRule Mandatory if used in the BACnetAnalogType or one of its subtypes
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.9.3.1 EventReporting Object override
  declaration Object EventReporting overrides definitions of the BACnetEventReportingType . The EventAlgorithm component is changed to TypeDefinition BACnetChangeOfStateAlgorithmType and ModellingRule Mandatory if used in the BACnetBinaryInputType . The BACnetChangeOfStateAlgorithmType is defined
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.10.3.1 EventReporting Object override
  declaration Object EventReporting overrides definitions of the BACnetEventReportingType . The EventAlgorithm component is changed to TypeDefinition BACnetCommandFailureAlgorithmType and ModellingRule Mandatory if used in the BACnetBinaryOutputType . The BACnetCommandFailureAlgorithmType is defined
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.11.3.1 EventReporting Object override
  declaration Object EventReporting overrides definitions of the BACnetEventReportingType . The EventAlgorithm component is changed to TypeDefinition BACnetChangeOfStateAlgorithmType and ModellingRule Mandatory if used in the BACnetBinaryValueType . The BACnetChangeOfStateAlgorithmType is defined
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.13.3.1 EventReporting Object override
  declaration Object EventReporting overrides definitions of the BACnetEventReportingType . The EventAlgorithm component is changed to TypeDefinition BACnetChangeOfStateAlgorithmType and ModellingRule Mandatory if used in the BACnetMultiStateInputType . The BACnetChangeOfStateAlgorithmType is defined
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.13.3.2 FaultEvaluation Object override
  declaration Object FaultEvaluation overrides definitions of the BACnetFaultEvaluationType . The FaultAlgorithm component is changed to TypeDefinition BACnetFaultStateAlgorithmType if used in the BACnetMultiStateInputType . The BACnetFaultStateAlgorithmType is defined in 8.25 . On the FaultAlgorithm
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.14.3.1 EventReporting Object override
  declaration Object EventReporting overrides definitions of the BACnetEventReportingType . The EventAlgorithm component is changed to TypeDefinition BACnetCommandFailureAlgorithmType and ModellingRule Mandatory if used in the BACnetMultiStateOutputType . The BACnetCommandFailureAlgorithmType is defined
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.15.3.1 EventReporting Object override
  declaration Object EventReporting overrides definitions of the BACnetEventReportingType . The EventAlgorithm component is changed to TypeDefinition BACnetChangeOfStateAlgorithmType and ModellingRule Mandatory if used in the BACnetMultiStateValueType . The BACnetChangeOfStateAlgorithmType is defined
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.15.3.2 FaultEvaluation Object override
  declaration Object FaultEvaluation overrides definitions of the BACnetFaultEvaluationType . The FaultAlgorithm component is changed to TypeDefinition BACnetFaultStateAlgorithmType if used in the BACnetMultiStateValueType . The BACnetFaultStateAlgorithmType is defined in 8.25 . On the FaultAlgorithm
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.18.3.17 Object EventReporting
  declaration Object EventReporting overrides definitions of the BACnetEventReportingType . The EventAlgorithm component is changed to TypeDefinition BACnetFloatingLimitAlgorithmType and ModellingRule Mandatory if used in the BACnetLoopType . The BACnetFloatingLimitAlgorithmType is defined
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  7.20.3.11 Object EventReporting
  declaration Object EventReporting overrides definitions of the BACnetEventReportingType . The EventAlgorithm component is changed to TypeDefinition BACnetFloatingLimitAlgorithmType and ModellingRule Mandatory if used in the BACnetLoopType . The BACnetBufferReadyAlgorithmType is defined
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  4.3.4.1 Concepts
  Space Object and Variable Nodes are called Instance Nodes and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 5 illustrates the relationship
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  4.3.4.2 Namespaces
  BrowseName is used to identify the children within a TypeDefinitions . Instances of a TypeDefinition are expected to have children with the same BrowseNames . TypeDefinitions are not allowed to have children
• OPC-30050 – OPC UA for PackML - Common Object Model: PackML
  4.3.4.3 Companion Specifications
  Example ObjectType Definition Attribute Value BrowseName WidgetType IsAbstract False Reference NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseObjectType from OPC 10000-5 . HasProperty Variable Color String PropertyType Mandatory HasProperty ... Value accessible via the Node (only used for Variable NodeClass Nodes ) and the TypeDefinition is the ObjectType or VariableType for the child. The ModellingRule indicates whether a child is Mandatory
• OPC-30060 – OPC UA for Tobacco Machine Communication
  3.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-30060 – OPC UA for Tobacco Machine Communication
  3.4.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-30060 – OPC UA for Tobacco Machine Communication
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-30060 – OPC UA for Tobacco Machine Communication
  3.4.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-30060 – OPC UA for Tobacco Machine Communication
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  3.4.1.1 Node definitions
  null or is omitted. Examples are given in Table 1 . The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  3.4.1.2 Additional References
  additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type additional subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  3.4.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  4.2.3.1 Concepts
  their semantics and structure. Figure 3 illustrates the relationship between an instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  7.27 AnalyticalSignalType
  Table 154 - AnalyticalSignalType definition Attribute Value BrowseName AnalyticalSignalType IsAbstract False References NodeClass BrowseName DataType TypeDefinition Other Subtype of AnalogSignalType defined in 7.26 , i.e. inheriting the InstanceDeclarations of that Node ... Conformance Units PA-DIM AnalyticalSignalType AnalogSignal is inherited from AnalogSignalType. In AnalyticalSignalType its TypeDefinition is specialized to PatMeasurementVariableType. The components of AnalyticalSignalType have additional references which are defined in Table
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  3.3.3.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  3.3.3.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  3.3.3.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  3.3.3.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30100 – OPC UA for SERCOS Devices
  4.3.1 Conventions for Node descriptions
  Attribute that is not set "--" will be used. References NodeClass BrowseName DataType TypeDefinition ModellingRule ReferenceType name NodeClass of the Target Node . BrowseName of the target Node ... Int32 where it is either a single-dimensional array or a scalar The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a NodeId of a TypeDefinitionNode
• OPC-30140 – OPC UA for PROFINET
  3.4.1 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-30140 – OPC UA for PROFINET
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 7 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all the children that can be present in an instance of the type. In the example in Figure
• OPC-30141 – OPC UA for PROFIenergy
  3.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-30141 – OPC UA for PROFIenergy
  3.4.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-30141 – OPC UA for PROFIenergy
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-30141 – OPC UA for PROFIenergy
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 4 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30142 – OPC UA for PROFINET Remote IO
  3.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-30142 – OPC UA for PROFINET Remote IO
  3.4.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-30142 – OPC UA for PROFINET Remote IO
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-30142 – OPC UA for PROFINET Remote IO
  3.4.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-30142 – OPC UA for PROFINET Remote IO
  4.3.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 5 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.5.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.5.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.5.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.5.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 6 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  3.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  3.4.1.2 Additional References
  additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type additional subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  3.4.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  6.7.1 BMPs with assigned text array
  EnumValueType structure as specified in Table 20 . The representing Variable shall have the TypeDefinition 0:BaseDataVariableType and the Value shall have the 0:Enumeration DataType created as described above
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  3.5.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  3.5.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  3.5.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  3.5.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 7 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  3.4.1 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  4.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30250 – OPC Unified Architecture for DEXPI
  4.2.1 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-30250 – OPC Unified Architecture for DEXPI
  5.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all the children that can be present in an instance of the type. In the example in Figure
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  3.4.1 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... Table 2 illustrates the Type Definition Table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 5 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  5.1 General rules for the mapping of the AAS metamodel to the OPC UA information model
  model. Example: AASSubmodelType has OPC UA components with OPC UA TypeDefinition AASSubmodelElementType. A submodel element may have the idShort "MaxRotationSpeed". Then the BrowseName of the component
• OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases
  4.2.3.1 Concepts
  AddressSpace Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 2 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  3.4.1.1 Node definitions
  null An Int32 where it is either a single-dimensional array or scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name ... definition. This is illustrated in Table 2 . If no components are provided, the DataType , TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  3.4.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which are either relative to the TypeDefinition
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type additional subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  3.4.1.4 Additional Attribute values
  Child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 7 illustrates the relationship between ... instance and its TypeDefinition . Type Nodes are templates that define all the children that can be present in an instance of the type. In the example in Figure
• OPC-34100 – OPC UA for Energy Consumption Management
  3.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-34100 – OPC UA for Energy Consumption Management
  3.4.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-34100 – OPC UA for Energy Consumption Management
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath Reference NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-34100 – OPC UA for Energy Consumption Management
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 5 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  3.4.1.1 Node Definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  3.4.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  3.4.1.3 Additional Sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  3.4.1.4 Additional Attribute Values
  Child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  7.3 No duplicated Nodes
  MachineryBuildingBlocks Object may lead to several paths to the same Node in a TypeDefinition (see for example Figure 7 ). When instantiating such a TypeDefinition it is recommended to keep this
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  12.2 MachineryItemState_StateMachineType
  State machine representing the state of a machinery item References Node Class BrowseName DataType TypeDefinition Other Subtype of the 0:FiniteStateMachineType defined in OPC 10000-16 , i.e. inheriting the InstanceDeclarations ... States or Transitions have a ModellingRule , i.e., they are only provided in the TypeDefinition , not on the instance. The CurrentState Variable (inherited from StateMachineType ) contains the information of the current
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  13.2 MachineryOperationModeStateMachineType
  State machine representing the operation mode of a MachineryItem References Node Class BrowseName DataType TypeDefinition Other Subtype of the 0:FiniteStateMachineType defined in OPC 10000-16 , i.e. inheriting the InstanceDeclarations ... States or Transitions have a ModellingRule , i.e., they are only provided in the TypeDefinition , not on the instance. The CurrentState Variable (inherited from StateMachineType ) contains the information of the current
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  15.2 MachineryLifetimeCounterType
  MachineryLifetimeCounterType Definition Attribute Value BrowseName MachineryLifetimeCounterType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype of the 0:FolderType defined in OPC 10000-5 0:HasComponent Variable <LifetimeVariable ... lifetime variable available, the AddIn should be defined as optional on the TypeDefinition and should not be provided on the instance if there is no lifetime variable. The child Nodes
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  3.4.1 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 4 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 5 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all the children that can be present in an instance of the type. In the example in Figure
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  3.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  3.4.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath Reference NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  7.3.2 Variable CraneAxisFunction
  Variable CraneAxisFunction To be extendable for vendor specific extensions later, the TypeDefinition is MultiStateValueDiscreteType with its mandatory Properties EnumValues and ValueAsText must be filled with the supported values which
• OPC-40082-1 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 1: Temperature control devices
  10.2 InternalMeasuringPoint
  whether the temperature of the main or the return is to be controlled. The TypeDefinition is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText must be filled with the supported values
• OPC-40082-1 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 1: Temperature control devices
  10.19 PumpControlMode
  PumpControlMode Description: Defines to which setpoint or function the pump is controlled. The TypeDefinition is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText must be filled with the supported values
• OPC-40082-1 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 1: Temperature control devices
  10.20.5 ThermocoupleType and CommunicationProtocolType
  used communication protocol between the sensor and the control system of the TCD. The TypeDefinition for both Variables is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText must be filled with
• OPC-40082-1 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 1: Temperature control devices
  10.22.5 Sink
  Sink Description: Defines where the medium is to be emptied The TypeDefinition is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText must be filled with the supported values out of Table
• OPC-40082-1 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 1: Temperature control devices
  10.22.6 Mode
  Mode Description: Defines how the medium is to be emptied. The TypeDefinition is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText must be filled with the supported values out of Table
• OPC-40082-1 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 1: Temperature control devices
  10.25.12 ControlMode
  ControlMode Description: Defines to which setpoint the external channel is controlled The TypeDefinition is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText must be filled with the supported values
• OPC-40082-2 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 2: Hot runner devices
  9.8 ActiveSetValues
  used set temperature for the temperature zones is selected (see 14 HRDTemperatureType ). The TypeDefinition for the Variable is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText shall be filled with
• OPC-40082-2 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 2: Hot runner devices
  9.9 ReactionOnDisconnect, SessionNameForReactionOnDisconnect, SetReactionOnDisconnect
  case of a disconnection from the OPC UA client specified by SessionNameForReactionOnDisconnect . The TypeDefinition for the ReactionOnDisconnect is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText shall be filled with ... SetReactionOnDisconnect Method AddressSpace Definition Attribute Value BrowseName SetReactionOnDisconnect References Node Class BrowseName DataType TypeDefinition Modelling Rule HasProperty Variable InputArguments Argument[] PropertyType Mandatory Note: It is not neceesary to include
• OPC-40082-2 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 2: Hot runner devices
  13.3 ThermocoupleType and CommunicationProtocolType
  used communication protocol between the sensor and the control system of the HRD. The TypeDefinition for both Variables is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText shall be filled with
• OPC-40082-2 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 2: Hot runner devices
  15.3 SetValueType / ActualType
  actual values of the zone should therefore not be visible. For SetValueType the TypeDefinition is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText shall be filled with the supported values
• OPC-40082-3 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 3: LSR Dosing Systems
  9.10 DeliveryType
  systems support the selection of the DeliveryType , the Property can be writeable. Therefore, the TypeDefinition is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText must be filled with the supported values
• OPC-40082-3 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 3: LSR Dosing Systems
  9.11 DeliveryPressure, DeliveryPressureMeasuringPoint
  systems support the selection of the position, the Property can be writeable. Therefore, the TypeDefinition is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText must be filled with the supported values
• OPC-40082-4 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 4: Dosing Systems
  13.2 MaterialClass
  which can be used for the recipe calculation by the server or client. The TypeDefinition is 0:MultiStateValueDiscreteType, values are given in Table 35 . Vendor specific classes can be used
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  3.2.1 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. illustrates the relationship between an instance ... TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure 3 the PersonType
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  22.6 Status
  ActualValue is within the tolerances or has passed a tolerance or min/max value. The TypeDefinition is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText shall be filled with the supported values
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  22.8 MonitoringSensitivity
  sensitivity defines how closely the tolerances are set during the automatic limit setting. The TypeDefinition is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText must be filled with the supported values
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  22.9 AlarmSuppression
  alarms of a monitored parameter e.g. during start up or a setpoint jump. The TypeDefinition is MultiStateValueDiscreteType , so the Properties EnumValues and ValueAsText must be filled with the supported values
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  29.2 DensityUnit
  DensityUnit In the MaterialType the Density has the TypeDefinition AnalogUnitType which includes the used unit. AnalogUnitType cannot be used as InputArgument of a method. Therefore, the MaterialListType has the Property
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  3.3.1 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 4 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 4 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring
  3.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... content/structure of a Type definition table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring
  3.4.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring
  3.4.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath Reference NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances, and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 3 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all the children that can be present in an instance of the type. In the example in Figure
• OPC-40200 – OPC UA for Weighing Technology
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances, and they always reference a TypeDefinition (ObjectType or VariableType ) Node which describes their semantics and structure. Figure 7 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all the children that can be present in an instance of the type. In the example in Figure
• OPC-40200 – OPC UA for Weighing Technology
  Agreement of Use
  LossInWeightScaleType BREAKING CHANGE 7.26 added mandatory HopperFillLevel and HopperWeight added BinWeight Change of TypeDefinition of accepted and rejected statistics in CheckweigherStatisticType BREAKING CHANGE 7.19 changed <PackagesRejectedBySystem> and TotalPackagesRejected ... RejectedStatisticCounterType changed TotalPackagesAccepted to AcceptedStatisticCounterType Changed TypeDefinition of ThresholdValueNodeId in ConditionSleepType 7.35 TypeDefinition of ThresholdValueNodeId in ConditionSleepType changed to BaseDataVariableType Integration of Statistics from CS Industrial Automation BREAKING CHANGE Using
• OPC-40210 – OPC UA for Geometric Measurement Systems
  4.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point
• OPC-40210 – OPC UA for Geometric Measurement Systems
  4.4.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-40210 – OPC UA for Geometric Measurement Systems
  4.4.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath References NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-40210 – OPC UA for Geometric Measurement Systems
  4.4.1.4 Additional Attribute values
  child Nodes BrowsePath <Attribute name> Attribute BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table The values of attributes
• OPC-40210 – OPC UA for Geometric Measurement Systems
  5.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 6 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-40223 – OPC UA for Pumps and Vacuum Pumps
  3.3.1 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-40223 – OPC UA for Pumps and Vacuum Pumps
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. illustrates the relationship between an instance ... TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure 3 the PersonType
• OPC-40223 – OPC UA for Pumps and Vacuum Pumps
  7.32 MeasurementsType ObjectType Definition
  Component. Measurements defined in this ObjectType have an additional Subcomponent with the TypeDefinition 0:PropertyType and the BrowseName KindOfQuantity defined in Table 72 . In this Variables the measurements ... MeasurementsType Definition Attribute Value BrowseName MeasurementsType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype of the 2:FunctionalGroupType defined in OPC 10000-100 , i.e. inheriting the InstanceDeclarations
• OPC-40223 – OPC UA for Pumps and Vacuum Pumps
  7.49 DriveMeasurementsType ObjectType Definition
  Component. Measurements defined in this ObjectType have an additional Subcomponent with the TypeDefinition 0:PropertyType and the BrowseName KindOfQuantity defined in Table 107 . In this Variables the measurements ... DriveMeasurementsType Definition Attribute Value BrowseName DriveMeasurementsType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype of the 2:FunctionalGroupType defined in OPC 10000-100 , i.e. inheriting the InstanceDeclarations
• OPC-40223 – OPC UA for Pumps and Vacuum Pumps
  7.50 InletConnectionMeasurementsType ObjectType Definition
  Component. Measurements defined in this ObjectType have an additional Subcomponent with the TypeDefinition 0:PropertyType and the BrowseName KindOfQuantity defined in Table 110 . In this Variables the measurements ... InletConnectionMeasurementsType Definition Attribute Value BrowseName InletConnectionMeasurementsType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype of the 2:FunctionalGroupType defined in OPC 10000-100 , i.e. inheriting the InstanceDeclarations
• OPC-40223 – OPC UA for Pumps and Vacuum Pumps
  7.51 OutletConnectionMeasurementsType ObjectType Definition
  Component. Measurements defined in this ObjectType have an additional Subcomponent with the TypeDefinition 0:PropertyType and the BrowseName KindOfQuantity defined in Table 113 . In this Variables the measurements ... OutletConnectionMeasurementsType Definition Attribute Value BrowseName OutletConnectionMeasurementsType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype of the 2:FunctionalGroupType defined in OPC 10000-100 , i.e. inheriting the InstanceDeclarations
• OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems
  3.4.1 Conventions for Node descriptions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. illustrates the relationship between an instance ... TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure 4 the PersonType
• OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems
  6.6 Alarms and Conditions
  defined: EmergencyStop, Service, Shutdown, and Warning. An OptionalPlaceholder Object <Event> with the TypeDefinition ConditionType is defined. If a manufacturer or system integrator adds additional alarms or conditions ... Event>, a concrete subtypes of the abstract ConditionType has to be used as TypeDefinition. To comply with Annex B of OPC 10000-9 - Part 9: Alarms and Conditions
• OPC-40301 – OPC UA for Flat Glass Processing
  3.5.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point
• OPC-40301 – OPC UA for Flat Glass Processing
  3.5.1.2 Additional References
  Additional References SourceBrowsePath Reference Type Is Forward TargetBrowsePath SourceBrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows of a nested table. ReferenceType name True = forward ... TargetBrowsePath points to another Node , which can be a well-known instance or a TypeDefinition . You can use BrowsePaths here as well, which is either relative to the TypeDefinition
• OPC-40301 – OPC UA for Flat Glass Processing
  3.5.1.3 Additional sub-components
  used. Table 5 - <some>Type Additional Subcomponents BrowsePath Reference NodeClass BrowseName DataType TypeDefinition Others BrowsePath is always relative to the TypeDefinition . Multiple elements are defined as separate rows
• OPC-40301 – OPC UA for Flat Glass Processing
  4.2.3.1 Concepts
  Address Space Object and Variable Nodes represent instances and they always reference a TypeDefinition ( ObjectType or VariableType ) Node which describes their semantics and structure. Figure 6 illustrates the relationship between ... instance and its TypeDefinition . The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure
• OPC-40400-1 – OPC UA for the Powertrain - Part 1: Asset Management
  3.4.1.1 Node definitions
  Int32 where it is either a single-dimensional array or a scalar. The TypeDefinition is specified for Objects and Variables . The TypeDefinition column specifies a symbolic name for a NodeId ... their definition. Table 3 illustrates the table. If no components are provided, the DataType, TypeDefinition and ModellingRule columns may be omitted and only a Comment column is introduced to point