Search
67 result(s) for Information Models
-
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Conceptsdescribes how UA Clients and Servers should interact with them. It also defines Information Models for Certificate management , key credential management, and authorization services. Part 13 ( OPC 10000-13 ) - Aggregates ... basic set of network related components to be used in more specific Information Models . Part 23 ( OPC 10000-23 ) - Common ReferenceTypes Part 23 specifies common types of references between Nodes
-
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts4.3 Design goalsprovide Clients with type definitions for the Objects accessed from the AddressSpace . This allows Information Models to be used to describe the contents of the AddressSpace . OPC UA allows data ... address space model and its own set of Services . OPC UA unifies the previous models into a single integrated address space with a single set of Services . OPC UA PubSub
-
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts5.3.4.4 Support for information modelsSupport for information models The OPC UA AddressSpace supports Information Models . This support is provided through: Node References that allow Objects in the AddressSpace to be related to each other ... industry specific data types to be used. Industry groups can define how their specific information models are to be represented in Server AddressSpace
-
OPC-10000-7 – OPC Unified Architecture - Part 7: Profilesspecific set of features (e.g. a group of services, portions of services or information models) that can be tested as a single entity. ConformanceUnits are the building blocks ... These groups reflect different OPC UA aspects like the Service Sets , security, transport, and Information Models . ConformanceGroups have no impact on testing; they are used only for organizational reasons. These
-
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety6.1 GeneralGeneral Clause 6 describes the integration of this document into the OPC UA Information Models in 6.2 and the resulting Service interfaces in 6.3 . Diagnostic services are described
-
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety6.2.2.1 SafetyACSet ObjectObject derived from DataType SafetyConsumerType for each SafetyConsumer it implements. The corresponding Information Models shown in Figure 3 and Figure 4 shall be used. A description of the graphical notation
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding9.1 OverviewImplementing these workflows requires an OPC UA Information Model . This section builds on existing Information Models and defines the additional types and instances needed to completely implement the workflows. Clause
-
OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model1 ScopeModel for a basic set of network related components to be used in other Information Models . The initial version of this document defines parameter sets for TSN Talkers and Listeners
-
OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Modelfuture ObjectType hierarchies. This allows these grouped parameters to be used in other Information Models independent of ObjectType hierarchies that can be found in the BNM. It is expected that
-
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts4.2 Architecturecore OPC UA functionality for field-level communications. The foundation of the UAFX Information Model is the AutomationComponent . The AutomationComponent is an entity representing one or more Assets that ... future for Motion, I/O, and many types of process instruments. Specifications, including Information Models , developed for those types of products will build upon the AutomationComponent model
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model1 ScopeController-to-Controller, Controller-to-Device, Device-to-Device and Controller/Device-to-Compute. It includes base Information Models for devices and controllers, ensuring smooth, high-speed information flow for critical factory ... process systems. These systems can include safety systems. It is expected that the Information Models specified in this document will be extended to include other specific device or system types
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelModel . It also specifies a number of Interfaces that can be applied to existing Information Models , allowing existing models to be used as part of an OPC UA FX system ... additional guidance on mapping this model to existing Information Models , see Annex B . For an overview of the main OPC UA FX ObjectTypes , see Figure 17 . Figure 17 - Overview
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelB.1 OverviewOverview There are three main approaches for applying OPC UA FX to existing Information Models . Creating a new model based on the OPC UA FX Information Model (see B.2 ). Extending
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.3.1 System perspectivestart the operation). For this case a specialized Client can use additional domain-specific Information Models as part of the update process. An update can be performed manually ... maintained on a regular basis an automatic update is desirable. For this scenario the Information Model also allows the transfer of software to the devices without starting the update process
-
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning4.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-10101 – OPC UA for WoT Binding4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-34.2.3.2 Namespacesturn, means Clients can have built in knowledge of some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30020 – MDIS OPC UA Companion Specification4.1 MDIS definitionssystem or set of systems. The core address space model supports the representation of InformationModels in the AddressSpace . See OPC 10000-5 for a description of the base
-
OPC-30020 – MDIS OPC UA Companion Specification4.3.4.1 Conceptsfunctionality (see OPC 10000-7 ). The OPC Foundation also defines a set of InformationModels that provide a basic set of functionalities. The Data Access specification (see OPC 10000-8 ) provides
-
OPC-30020 – MDIS OPC UA Companion Specification4.3.4.2 Namespacesturn, means Clients can have built in knowledge of some Nodes . OPC UA InformationModels generally define globally unique NodeIds for the TypeDefinitions defined by the InformationModel . QualifiedNames are non-localised ... BrowseNames of Nodes and allow the same names to be used by different InformationModels without conflict. The BrowseName is used to identify the children within a TypeDefinition . Instances
-
OPC-30020 – MDIS OPC UA Companion Specification14.2.3 ClientClient Table 128 defines the Client based ConformanceUnits . These units are related to MDIS InformationModels . Table 129 describes general functionality based ConformanceUnits Table 128 - MDIS Client Information Model ConformanceUnits Category
-
OPC-30060 – OPC UA for Tobacco Machine Communication4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30140 – OPC UA for PROFINET4.2.3.2 Namespacesturn, means Clients can have built in knowledge of some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30141 – OPC UA for PROFIenergy4.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames
-
OPC-30142 – OPC UA for PROFINET Remote IO4.3.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drivesspecific extensions to the standardized Information Model as well as additional independent vendor specific Information Models . Because of PROFINET being real switched Ethernet, the PROFINET network in the OT areas ... edge Device or the cell Controller PLC acting as proxy for the Information Model of the PROFINET Devices under its control. The proxy Devices use PROFINET communication and the PROFIdrive
-
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30200 – OPC UA for Commercial Kitchen Equipment4.3.2 Namespacesturn, means Clients can have built in knowledge of some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30250 – OPC Unified Architecture for DEXPI5.2.3.2 Namespacesturn, means Clients can have built in knowledge of some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30270 – OPC UA for Asset Administration Shell (AAS)4.2.3.2 Namespacesturn, means Clients can have built-in knowledge of some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics4.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-34100 – OPC UA for Energy Consumption Management4.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks4.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40010-1 – OPC UA for Robotics - Part 1: Vertical Integration4.2.3.2 Namespacesturn, means Clients can have built in knowledge of some Nodes . OPC UA Information Models define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System4.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management4.2.3.2 Namespacesturn, means Clients can have built in knowledge of some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring4.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40200 – OPC UA for Weighing Technology4.2.3.2 Namespacesturn, means Clients can have built in knowledge of some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40210 – OPC UA for Geometric Measurement Systems5.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumps4.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems4.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40301 – OPC UA for Flat Glass Processing4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40400-1 – OPC UA for the Powertrain - Part 1: Asset Management4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40444 – OPC UA for Textile Testing Devices4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40450-1 – OPC UA for Joining Systems - Part 1: Base4.3.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management4.2.3.2 Namespacesturn, means Clients can have built in knowledge of some Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40503-1 – OPC UA for Metal Forming - Part 1: General4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40504-1 – OPC UA for Cutting Tools - Part 1: Manufacturing4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40505 – OPC UA for Wireless Machine Tool Peripherals4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40530 – OPC UA for Laser Systems4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40540 – OPC UA for Additive Manufacturing4.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40550-1 – OPC UA for Woodworking Machines - Part 1: Vertical Interface4.2.3.2 Namespaceshave built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40560 – OPC UA for Mining - General4.3.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40570 – OPC UA for Wire Harness Manufacturing4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40600 – OPC UA for Weihenstephan Standards4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40700 – OPC UA for Surface Technology - General Types4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40702 – OPC UA for Surface Technology - Organic Coating Technology - Material Supply Systems4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40718 – OPC UA for Surface Technology - Shot Blasting Machinery4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40719 – OPC UA for Plasma Surface Technology4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
-
OPC-40740 – OPC UA for Process Air Extraction and Filtration Systems (PAEFS)4.2.3.2 Namespacesbuilt-in knowledge of of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances