Search

103 result(s) for NodeClasses

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.4.2 Integrated AddressSpace model
  Node s in the AddressSpace are typed according to their use and their meaning. NodeClasses define the metadata for the OPC UA AddressSpace . OPC 10000-3 defines ... NodeClasses . The Base NodeClass defines Attributes common to all Node s, allowing identification, classification, and naming. Each NodeClass inherits these Attributes and may additionally define its own Attributes . To promote
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.4.3 Integrated object model
  Integrated object model The OPC UA Object Model provides a consistent, integrated set of NodeClasses for representing Objects in the AddressSpace . This model represents Objects in terms of their Variables
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  3.3.2 Conventions for defining NodeClasses
  Conventions for defining NodeClasses Clause 4.10 defines AddressSpace NodeClasses . Table 1 describes the format of the tables used to define NodeClasses . Table 1 - NodeClass Table Conventions Name Use Data Type ... NodeClass, including system specific ReferenceTypes . The NodeClass tables only specify how the NodeClasses can be used as SourceNodes of References , not as TargetNodes . If a NodeClass table allows a ReferenceType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.1 Overview
  remainder of Clause 4 defines the concepts of the AddressSpace . Clause 5 defines the NodeClasses of the AddressSpace representing the AddressSpace concepts. Clause 6 defines details on the type model
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.3 Object Model
  each NodeClass represents a different element of the Object Model. Clause 4.10 defines the NodeClasses used to represent this model
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.2 NodeClasses
  NodeClasses NodeClasses are defined in terms of the Attributes and References that shall be instantiated (given values) when a Node is defined in the AddressSpace . Attributes are discussed ... References in 4.4.4 . Clause 5 defines the NodeClasses for the OPC UA AddressSpace . These NodeClasses are referred to collectively as the metadata for the AddressSpace . Each Node in the AddressSpace
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.4.3 Attributes
  Services . These Services are defined in OPC 10000-4 . Attributes are elementary components of NodeClasses . Attribute definitions are included as part of the NodeClass definitions in Clause 4.10 and, therefore
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.1 Overview
  Overview Clause 5 defines the NodeClasses used to define Nodes in the OPC UA AddressSpace . NodeClasses are derived from a common Base NodeClass . This NodeClass is defined first, followed ... those used to organise the AddressSpace and then by the NodeClasses used to represent Objects . The NodeClasses defined to represent Objects fall into three categories: those used to define instances
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.1 General
  Address Space Model defines a Base NodeClass from which all other NodeClasses are derived. The derived NodeClasses represent the various components of the OPC UA Object Model
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.2 Attributes
  restriction that a ReferenceType can only be used by relating Nodes of some NodeClasses with a defined cardinality is a special constraint of a ReferenceType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.3.3.3 HasSubtype References
  parent") but not lowered (e.g. "allow loops"). The constraints concerning which NodeClasses can be referenced are also inherited and can only be further restricted. That
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.1 Object NodeClass
  Nodes . No restrictions are placed on the types of References used or on the NodeClasses of the Nodes that may be referenced. However, restrictions may be defined by the ReferenceType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.5.2 ObjectType NodeClass
  Nodes . No restrictions are placed on the types of References used or on the NodeClasses of the Nodes that may be referenced. However, restrictions may be defined by the ReferenceType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.4 DataVariable
  Nodes . No restrictions are placed on the types of References used or on the NodeClasses of the Nodes that may be referenced. However, restrictions may be defined by the ReferenceType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.5 VariableType NodeClass
  Nodes . No restrictions are placed on the types of References used or on the NodeClasses of the Nodes that may be referenced. However, restrictions may be defined by the ReferenceType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  Nodes . No restrictions are placed on the types of References used or on the NodeClasses of the Nodes that may be referenced. However, restrictions may be defined by the ReferenceType
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.9 Summary of Attributes of the NodeClasses
  Summary of Attributes of the NodeClasses Table 18 summarises all Attributes defined in this document and points out which NodeClasses use them either in an optional (O) or mandatory
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.55 PermissionType
  other than the Value or the RolePermissions Attribute . This Permission is valid for all NodeClasses . ReadRolePermissions 1 The Client is allowed to read the RolePermissions Attribute . This Permission is valid ... NodeClasses . WriteAttribute 2 The Client is allowed to write to Attributes other than the Value , Historizing or RolePermissions Attribute if the WriteMask indicates that the Attribute is writeable. This
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.2 Parameters
  TypeDefinitionNode for the Node to add. This parameter shall be null for all NodeClasses other than Object and Variable in which case it shall be provided. If the server Index
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.2.2 Parameters
  instances of referenceTypeId and all of its subtypes are returned. nodeClassMask UInt32 Specifies the NodeClasses of the TargetNodes . Only TargetNodes with the selected NodeClasses are returned. The NodeClasses are assigned ... VariableType 5 ReferenceType 6 DataType 7 View If set to zero, then all NodeClasses are returned. If the NodeClass is unknown for a remote Node , the nodeClassMask is ignored. resultMask
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.29 ReferenceDescription
  NodeId Type definition NodeId of the TargetNode . Type definitions are only available for the NodeClasses Object and Variable . For all other NodeClasses a null NodeId shall be returned
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  3.3 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.2 Root
  other standard Objects . The " Root " Object shall not reference any other NodeClasses . It is formally defined in Table 100 . Table 100 - Root definition Attribute Value BrowseName Root References
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.3 Views
  Figure 2 - Views organization The " Views " Object shall not reference any other NodeClasses . The " Views " Object is formally defined in Table 101 . Table 101 - Views definition
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.5 Types
  Types " standard Object . The " Types " Object shall not reference any other NodeClasses . It is formally defined in Table 103 . Table 103 - Types definition Attribute Value BrowseName Types
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.6 ObjectTypes
  ObjectTypes " standard Object . The " ObjectTypes " Object shall not reference any other NodeClasses . Figure 4 - ObjectTypes organization The intention of the " ObjectTypes " Object is that
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.7 VariableTypes
  VariableTypes " standard Object . The " VariableTypes " Object shall not reference any other NodeClasses . Figure 5 - VariableTypes organization The intent of the " VariableTypes " Object is that
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.8 ReferenceTypes
  ReferenceTypes " Object . The " ReferenceTypes " Object shall not reference any other NodeClasses . See Clause 11 for a discussion of the standard ReferenceTypes that appear beneath the " ReferenceTypes
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.10 EventTypes
  EventTypes " standard Object . The " EventTypes " Object shall not reference any other NodeClasses . Figure 7 - EventTypes organization The intention of the " EventTypes " Object is that
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  8.2.11 InterfaceTypes
  InterfaceTypes " standard Object . The " InterfaceTypes " Object shall not reference any other NodeClasses . Figure 8 - InterfaceTypes Organization The intention of the " InterfaceTypes " Object is that
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  1 Scope
  with Data Access (DA). It particularly includes additional VariableTypes and complementary descriptions of the NodeClasses and Attributes needed for Data Access, additional Properties , and other information and behaviour. The complete ... address space model, including all NodeClasses and Attributes is specified in OPC 10000-3 . The services to detect and access data are specified in OPC 10000-4 . Annex A specifies
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  A.4 NodeClass mapping
  NodeClass mapping The OPC UA metamodel uses the concept of NodeClasses to define sets of primitive attributes that are present on different types of nodes in the UA address space ... deleted, they should be ignored. For example, in OPC UA, the ObjectType and VariableType NodeClasses contain an attribute IsAbstract that indicates if direct instances of that type are allowed
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  3.3.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.3.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  3.3.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.3.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.3.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  3.3.1 Conventions for Node descriptions
  used, it is prefixed by the NamespaceIndex (see Table 73 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  3.4.1 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  3.4.1 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  4.2.2 Graphical Notation
  graphical notation for an OPC UA AddressSpace . It defines graphical symbols for all NodeClasses and how different types of References between Nodes can be visualized. Figure 1 shows the symbols ... NodeClasses used in this specification. NodeClasses representing types always have a shadow. Figure 1 - OPC UA Graphical Notation for NodeClasses Figure 2 shows the symbols for the ReferenceTypes used
• OPC-30020 – MDIS OPC UA Companion Specification
  4.1 MDIS definitions
  additional details. NodeClass The class of a Node in an AddressSpace . NodeClasses define the metadata for the components of the OPC UA Object Model. They also define constructs, such
• OPC-30020 – MDIS OPC UA Companion Specification
  6.2.2 MDISBaseObjectType Definition
  Node of Variable NodeClass is readable, writeable or both readable and writeable. Other NodeClasses ( Object , Method ) do not support reading or writing and do not fill in this column
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  3.5.1 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  4.2.1 General
  defined set of Attributes . This specification makes use of three essential OPC UA NodeClasses : Objects, Methods and Variables . Objects are used to represent components of a system. An Object
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  4.2.2 Graphical Notation
  graphical notation for an OPC UA AddressSpace . It defines graphical symbols for all NodeClasses and how different types of References between Nodes can be visualized. Figure 1 shows the symbols ... NodeClasses used in this specification. NodeClasses representing types always have a shadow. Figure 1 - OPC UA Graphical Notation for NodeClasses Figure 2 shows the symbols for the ReferenceTypes used
• OPC-30040 – OPC UA for AutomationML - Xxx: OPC UA Information Model for AutomationML
  3.3.2 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass
• OPC-30040 – OPC UA for AutomationML - Xxx: OPC UA Information Model for AutomationML
  4.2.1 General
  defined set of Attributes . This specification makes use of three essential OPC UA NodeClasses : Objects, Methods and Variables . Objects are used to represent components of a system. An Object
• OPC-30040 – OPC UA for AutomationML - Xxx: OPC UA Information Model for AutomationML
  4.2.2 Graphical Notation
  graphical notation for an OPC UA AddressSpace . It defines graphical symbols for all NodeClasses and how different types of References between Nodes can be visualized. Figure 3 shows the symbols ... NodeClasses used in this specification. NodeClasses representing types always have a shadow. Figure 3 - OPC UA Graphical Notation for NodeClasses Figure 4 shows the symbols for the ReferenceTypes used
• OPC-30060 – OPC UA for Tobacco Machine Communication
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  3.3.3.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.3.4.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-30100 – OPC UA for SERCOS Devices
  4.2 OPC UA
  defined set of Attributes. This specification makes use of almost all OPC UA NodeClasses . Objects are used to represent real-world entities such as Devices and (communication) Networks as well
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  3.4.1 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  4.2.1 General
  defined set of Attributes . This specification makes use of three essential OPC UA NodeClasses : Objects, Methods and Variables . Objects are used to represent components of a system. An Object
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  4.2.2 Graphical notation
  graphical notation for an OPC UA AddressSpace . It defines graphical symbols for all NodeClasses and how different types of References between Nodes can be visualised. Figure 3 shows the symbols ... NodeClasses used in this specification. NodeClasses representing types always have a shadow. Figure 3 - OPC UA graphical notation for NodeClasses Figure 4 shows the symbols for the ReferenceTypes used
• OPC-30130 – OPC UA for Control & Communication System Profile(for Machine)
  4.2.1 General
  defined set of Attributes . This specification defines Nodes of the OPC UA NodeClasses Object, Method, Variable, ObjectType and DataType . Objects are used to represent components of a system. An Object
• OPC-30130 – OPC UA for Control & Communication System Profile(for Machine)
  4.2.2 Graphical notation
  graphical notation for an OPC UA AddressSpace . It defines graphical symbols for all NodeClasses and how different types of References between Nodes can be visualized. Figure shows the symbols ... NodeClasses used in this specification. NodeClasses representing types always have a shadow. Figure 4‑5 - OPC UA Graphical Notation for NodeClasses Figure shows the symbols for the ReferenceTypes used
• OPC-30140 – OPC UA for PROFINET
  3.4.1 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass
• OPC-30141 – OPC UA for PROFIenergy
  3.4.1.1 Node definitions
  prefixed by the NamespaceIndex (see [OPC 10000-3] ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their BrowseName
• OPC-30142 – OPC UA for PROFINET Remote IO
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.5.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.5.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives
  3.5.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.6.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-30200 – OPC UA for Commercial Kitchen Equipment
  3.4.1 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass
• OPC-30210-1 – OPC UA for Unattended Retail & Coffee Solutions - Part 1: Core Components
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-30250 – OPC Unified Architecture for DEXPI
  4.2.1 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass
• OPC-30270 – OPC UA for Asset Administration Shell (AAS)
  3.4.1 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass
• OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics
  3.4.1.1 Node definitions
  Namespace is used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of different NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass
• OPC-34100 – OPC UA for Energy Consumption Management
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks
  3.4.1.1 Node Definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration
  3.4.1 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass
• OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions
  3.2.1 Conventions for Node descriptions
  used, it is prefixed by the NamespaceIndex (see 3.2.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management
  3.3.1 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass
• OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-40210 – OPC UA for Geometric Measurement Systems
  4.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 4.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-40223 – OPC UA for Pumps and Vacuum Pumps
  3.3.1 Conventions for Node descriptions
  used, it is prefixed by the NamespaceIndex (see 3.3.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems
  3.4.1 Conventions for Node descriptions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40301 – OPC UA for Flat Glass Processing
  3.5.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.5.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40400-1 – OPC UA for the Powertrain - Part 1: Asset Management
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40444 – OPC UA for Textile Testing Devices
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40450-1 – OPC UA for Joining Systems - Part 1: Base
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management
  3.4.1 Conventions for Node descriptions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-40502 – OPC UA for Computerized Numerical Control (CNC) Systems - for CNC Systems: OPC UA Information Model
  3.3.1 Conventions for Node descriptions
  name of the Node representing the DataType shall be used. Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass
• OPC-40502 – OPC UA for Computerized Numerical Control (CNC) Systems - for CNC Systems: OPC UA Information Model
  4.2.1 General
  defined set of Attributes . This specification makes use of three essential OPC UA NodeClasses : Objects, Methods and Variables . Objects are used to represent components of a system. An Object
• OPC-40502 – OPC UA for Computerized Numerical Control (CNC) Systems - for CNC Systems: OPC UA Information Model
  4.2.2 Graphical Notation
  graphical notation for an OPC UA AddressSpace . It defines graphical symbols for all NodeClasses and how different types of References between Nodes can be visualized. Figure 2 shows the symbols ... NodeClasses used in this specification. NodeClasses representing types always have a shadow. Figure 2 - OPC UA Graphical Notation for NodeClasses Figure 3 shows the symbols for the ReferenceTypes used
• OPC-40503-1 – OPC UA for Metal Forming - Part 1: General
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40504-1 – OPC UA for Cutting Tools - Part 1: Manufacturing
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-40505 – OPC UA for Wireless Machine Tool Peripherals
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40530 – OPC UA for Laser Systems
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40540 – OPC UA for Additive Manufacturing
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40550-1 – OPC UA for Woodworking Machines - Part 1: Vertical Interface
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore, only the used ReferenceType , their NodeClass and their
• OPC-40560 – OPC UA for Mining - General
  3.2.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.2.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40570 – OPC UA for Wire Harness Manufacturing
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40600 – OPC UA for Weihenstephan Standards
  3.4.1 Conventions for Node descriptions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40700 – OPC UA for Surface Technology - General Types
  3.3.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.3.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40701 – OPC UA for Surface Technology - Cleaning and Pretreatment
  3.3.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.3.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40702 – OPC UA for Surface Technology - Organic Coating Technology - Material Supply Systems
  3.3.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.3.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40718 – OPC UA for Surface Technology - Shot Blasting Machinery
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40719 – OPC UA for Plasma Surface Technology
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their
• OPC-40740 – OPC UA for Process Air Extraction and Filtration Systems (PAEFS)
  3.4.1.1 Node definitions
  used, it is prefixed by the NamespaceIndex (see 3.4.2.2 ). Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType , their NodeClass and their