Search

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

94 result(s) for Identifier

OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

8.2.4 Identifier value

Identifier value The Identifier value element is used within the context of the first three elements to identify the Node . Its data type and format is defined by the IdType ... Identifier values of IdType String are restricted to 4096 characters and shall not contain Unicode control characters. Unicode control characters are defined by Unicode C0 and Unicode C1 . Identifier values
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.2.2.9 NodeId

defined NodeIds. IdentifierType Enumeration The format and data type of the identifier. The value may be one of the following: NUMERIC - the value is an UInt32; STRING - the value ... value is a ByteString ; Value UInt32 or String or Guid or ByteString The identifier for a node in the address space of an OPC UA Server . The DataEncoding
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.10 NodeId

string using the format defined in 5.1.12 . NodeIds in NamespaceIndex 0 use the <identifier> form. All other NodeIds use the <namespace-uri> form. The first abnormal ... decoder shall set the NamespaceIndex to 0, the IdType to String and the Identifier to the JSON string
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.11 ExpandedNodeId

ServerIndex to 0, the NamespaceIndex to 0, the IdType to String and the Identifier to the JSON string. When the ServerIndex is 0, decoders shall replace a NamespaceUri with
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

A.3 Numeric Node Ids

Each line in the CSV file has the following fields: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is numeric value for the NodeId . Each SymbolName is unique within the CSV file. The BrowsePath
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.3 ExpandedNodeId

Description IdType The IdentifierType encoded as a JSON number. Allowed values are: 0 - UInt32 Identifier encoded as a JSON number. 1 - A String Identifier encoded as a JSON string ... Guid Identifier encoded as described in 5.4.2.7 . 3 - A ByteString Identifier encoded as described in 5.4.2.8 . This field is omitted for UInt32 identifiers. Id The Identifier . The value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.3.7.4 PubSubConfigurationValueDataType

related PubSubConfiguration2DataType Structure. Name String The name of the referenced PubSub configuration element. Identifier BaseDataType The identifier value used for the referenced element in the PubSub NetworkMessages . The value ... PubSubConneciton , WriterGroup or DataSetWriter . The value is null otherwise. If ConfigurationElement references a PubSubConnection , Identifier will contain the value of the PublisherId . If ConfigurationElement references a WriterGroup , Identifier will contain
OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler

A.1 Namespace and Identifiers for the Scheduler Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

6.2.1 Overview

TypeDefinition Other Subtype of the BaseObjectType defined in OPC 10000-5. 0:HasProperty Variable Identifier 0:String 0:PropertyType M 0:HasComponent Variable WorldFrame 0:BaseDataType {Any} SpatialLocationType ... SpatialObjectsListType shall be used to add application specific identification. The mandatory Property Identifier shall be used to name the SpatialObjectsList . Annex C.3 describes different scenarios
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

9.1 Conformance Units

SpatialObjectType instance shall be of a discrete subtype of SpatialLocationType ( 7.2 ) Server RSL SpatialObject Identifier Supports the variable Identifier of SpatialObjectType ( 6.1 ). Server RSL SpatialObject AttachPoints Supports the folder AttachPoints
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

A.1 Namespace and identifiers for Relative Spatial Location Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

C.3 Example use of the Identifier Property in a multi-server scenario

Example use of the Identifier Property in a multi-server scenario For the use in multi-server scenarios with different servers it might be needed to identify all related SpatialObjectsLists ... bring them in relationship in a higher levelled SpatialObjectsList. For this the Property Identifier of a SpatialObjectsList can be instantiated as the Property Identifier of a SpatialObject contained
OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3

A.1 Namespace and identifiers for IEC 61131-3 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.1.3.3 Object Diagnostics

Table 8 and described below. Presence identifies if there currently is seen an AutoID Identifier (e.g. a code or a transponder) by the device. If supported by a device ... Logbook. The LastAccess FunctionalGroup shall be provided if values for the last AutoID Identifier access are supported for diagnostic purposes. Its predefined parameters are described in the following list: Parameter
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.1.3.10 Variable LastScanTimestamp

belongs to the Variable LastScanData and represents the point of time the last AutoID Identifier was scanned. The value of this Variable shall be equal to the SourceTimestamp ... like UtcTime . The use of this Variable implies the following restrictions. Only one AutoID Identifier can be delivered for a scan. The frequency of scans is limited to the sampling
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.5.3.4 Method KillTag

disable a transponder. See Annex B for technology specific mappings. Signature KillTag ( [in] ScanData Identifier [in] CodeTypeDataType CodeType [in] ByteString KillPassword [out] AutoIdOperationStatusEnumeration Status ); Argument Description Identifier AutoID Identifier according ... ScanDataEpc where only the parameter UId is relevant for this Method . If the Identifier is provided from a different source than the ScanResult , a ScanData with a ByteString
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.5.3.5 Method LockTag

password is required. See Annex B for technology specific mappings. Signature LockTag ( [in] ScanData Identifier [in] CodeTypeDataType CodeType [in] ByteString Password [in] RfidLockRegionEnumeration Region [in] RfidLockOperationEnumeration Lock [in] UInt32 Offset ... UInt32 Length [out] AutoIdOperationStatusEnumeration Status ); Argument Description Identifier AutoID Identifier according to the device configuration as returned as part of a ScanResult in a scan event or scan method
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.5.3.6 Method SetTagPassword

with encryption enabled. See Annex B for technology specific mappings. Signature SetTagPassword ( [in] ScanData Identifier [in] CodeTypeDataType CodeType [in] RfidPasswordTypeEnumeration PasswordType [in] ByteString AccessPassword [in] ByteString NewPassword [out] AutoIdOperationStatusEnumeration Status ... Argument Description Identifier AutoID Identifier according to the device configuration as returned as part of a ScanResult in a scan event or scan method. The ScanData DataType is defined
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.5.3.7 Method ReadTag

reads a specified area from a tag memory. One Method invocation reads one AutoID Identifier . The Call Service used to invoke the Method can take a list of Methods . Therefore ... Call Service . See Annex B for technology specific mappings. Signature ReadTag ( [in] ScanData Identifier [in] CodeTypeDataType CodeType [in] UInt16 Region [in] UInt32 Offset [in] UInt32 Length [in] ByteString Password
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.5.3.8 Method WriteTag

RFID tag. See Annex B for technology specific mappings. Signature WriteTag ( [in] ScanData Identifier [in] CodeTypeDataType CodeType [in] UInt16 Region [in] UInt32 Offset [in] ByteString Data [in] ByteString Password ... AutoIdOperationStatusEnumeration Status ); Argument Description Identifier AutoID Identifier according to the device configuration as returned as part of a ScanResult in a scan event or scan method. The ScanData DataType
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.5.3.9 Method WriteTagID

Annex B for technology specific mappings. Signature WriteTagID ( [in] ScanData Identifier [in] CodeTypeDataType CodeType [in] ByteString NewUId [in] Byte AFI [in] Boolean Toggle [in] ByteString Password [out] AutoIdOperationStatusEnumeration Status ); Argument ... Description Identifier AutoID Identifier according to the device configuration as returned as part of a ScanResult in a scan event or scan method. The ScanData DataType is defined
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.5.3.11 Variable LastScanAntenna

Variable LastScanData and represents the ID of the antenna with which the last AutoID Identifier was scanned. The Variable can be provided for simple applications where OPC UA Clients ... like UtcTime . The use of this Variable implies the following restrictions. Only one AutoID Identifier can be delivered for a scan. The frequency of scans is limited to the sampling
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.5.3.12 Variable LastScanRSSI

Variable LastScanData and represents the RSSI Value with which the last AutoID Identifier was scanned. The Variable can be provided for simple applications where OPC UA Clients are limited ... like UtcTime . The use of this Variable implies the following restrictions. Only one AutoID Identifier can be delivered for a scan. The frequency of scans is limited to the sampling
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

6.6.3.2 Method GetLocation

will be apparent from the timestamp returned in the result). Signature GetLocation ( [in] ScanData Identifier [in] CodeTypeDataType CodeType [in] LocationTypeEnum LocationType [out] RtlsLocationResult Result ); Argument Description Identifier AutoID Identifier according ... ScanDataEpc where only the parameter UId is relevant for this Method . If the Identifier is provided from a different source than the ScanResult , a ScanData with a ByteString
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

9.3.17 AccessResult

AccessResult This DataType is a structure that defines the result values of an AutoID Identifier access of an AutoID device. Its composition is formally defined in Table 73 . Table ... Subtype of Structure defined in OPC 10000-5 . CodeType CodeTypeDataType Defines the format of Identifier as string. The String DataType CodeTypeDataType and the predefined format strings are defined
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices

A.1 Namespace and identifiers for AutoID Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30050 – OPC UA for PackML - Common Object Model: PackML

A.1 Namespace and identifiers for PackML Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is numeric value for the NodeId . The BrowsePath for an instance Node is constructed by appending
OPC-30060 – OPC UA for Tobacco Machine Communication

A.1 Namespace and identifiers for TMC Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>

A.1 Namespace and identifiers for FDT Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30100 – OPC UA for SERCOS Devices

4.3.2.1 NodeIds

unique. In this "OPC UA for Sercos Devices companion specification", the Identifier for each Node starts with one out of the three possible connection / addressing types Topological (defined
OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture

A.1 Namespace and identifiers for POWERLINK Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30120 – OPC UA for IO-Link Devices and IO-Link Masters - IO-Link: OPC Unified Architecture

A.1 Namespace and identifiers for OPC UA for IO-Link Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30140 – OPC UA for PROFINET

A.1 Namespace and identifiers for OPC UA for PROFINET Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30141 – OPC UA for PROFIenergy

A.1 Namespace and identifiers for OPC UA for PROFIenergy Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30142 – OPC UA for PROFINET Remote IO

A.1 Namespace and identifiers for OPC UA for PROFINET Remote IO Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30200 – OPC UA for Commercial Kitchen Equipment

A.1 Namespace and identifiers for commercial kitchen devices Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30250 – OPC Unified Architecture for DEXPI

A.1 Namespace and identifiers for DEXPI Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30260 – OPC UA for OPEN-SCS - Serialization Object Model: OPEN-SCS

A.1 Namespace and identifiers for OPENSCS-SER Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-30270 – OPC UA for Asset Administration Shell (AAS)

A.1 Namespace and identifiers for I4AAS Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> The SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node, that appears in the specification, and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40077 – OPC UA interfaces for plastics and rubber machinery - Data exchange between injection moulding machines and MES

A.1 Namespace and identifiers for OPC 40077 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40082-1 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 1: Temperature control devices

A.1 Namespace and identifiers for OPC 40082-1 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40082-2 – OPC UA interfaces for plastics and rubber machinery - Peripheral devices - Part 2: Hot runner devices

A.1 Namespace and identifiers for OPC 40082-2 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

A.1 Namespace and identifiers for OPC 40083 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-1 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 1: General Type Definitions

A.1 Namespace and identifiers for OPC 40084-1 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-2 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 2: Extrusion Line

A.1 Namespace and identifiers for OPC 40084-2 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-3 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 3: Extruder

A.1 Namespace and identifiers for OPC 40084-3 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-4 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 4: Haul-off

A.1 Namespace and identifiers for OPC 40084-4 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-5 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 5: Melt pump

A.1 Namespace and identifiers for OPC 40084-5 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-6 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 6: Filter

A.1 Namespace and identifiers for OPC 40084-6 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-7 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 7: Die

A.1 Namespace and identifiers for OPC 40084-7 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-8 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 8: Pelletizer

A.1 Namespace and identifiers for OPC 40084-8 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-9 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 9: Cutter

A.1 Namespace and identifiers for OPC 40084-9 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-10 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 10: Calibrator

A.1 Namespace and identifiers for OPC 40084-10 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-11 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 11: Corrugator

A.1 Namespace and identifiers for OPC 40084-11 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40084-12 – OPC UA interfaces for plastics and rubber machinery - Extrusion - Part 12: Calender

A.1 Namespace and identifiers for OPC 40084-12 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40100-1 – OPC UA for Machine Vision - Part 1: Control, configuration management, recipe management, result management

A.1 Namespace and identifiers for Machine Vision Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40210 – OPC UA for Geometric Measurement Systems

8.13 CorrectionType

TypeDefinition Other Subtype of the BaseObjectType defined in OPC 10000-3 0:HasProperty Variable Identifier 0:String 0:PropertyType 0:Mandatory 0:HasProperty Variable CharacteristicIdentifier 0:String 0:PropertyType ... HasProperty Variable ProgramName 0:String 0:PropertyType 0:Optional Conformance Units GMS CorrectionType Identifier is a unique ID to identify this correction value. CharacteristicIdentifier is a reference to the characteristic
OPC-40210 – OPC UA for Geometric Measurement Systems

10.3 AdditionalSensorType

Other Subtype of the 0:AnalogUnitType defined in OPC 10000-3 0:HasProperty Variable Identifier 0:String 0:PropertyType 0:Mandatory 0:HasComponent Variable Class 0:UInteger 0:MultiStateDiscreteType ... HasProperty Variable Name 0:String 0:PropertyType 0:Optional Conformance Units GMS GMSEquipmentType Identifier is the identifier of the sensor. The Identifier shall be unique within the AddressSpace . Class indicates
OPC-40223 – OPC UA for Pumps and Vacuum Pumps

A.1 Namespace and identifiers for OPC UA for Pumps and Vacuum Pumps Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems

A.1 Namespace and identifiers for OPC UA for Compressed Air Systems Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.2.2 SoftwareIdentificationType

HasProperty Variable 2:SoftwareRevision 0:String 0:PropertyType M, RO 0:HasProperty Variable Identifier 0:String 0:PropertyType M, RO 0:HasProperty Variable 2:Manufacturer 0:LocalizedText 0:PropertyType ... PLL01 1.10.0.3", "V05.01.01.15", "3.1 R1293", "70.0.1". The Identifier Property provides an identifier to distinguish the software component. 2:Manufacturer refers to the manufacturer/producer
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.4.2 ProductionJobListType

OrderedObject >, it is recommended to use the value of the Identifier Property of the respective ProductionJobType instance. The 0:NodeVersion and the 0:GeneralModelChangeEventType inherited from the 0:OrderedListType
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.4.3 ProductionJobType

Node 0:HasProperty Variable CustomerOrderIdentifier 0:String 0:PropertyType O, RO 0:HasProperty Variable Identifier 0:String 0:PropertyType M, RO 0:HasProperty Variable OrderIdentifier 0:String 0:PropertyType ... OrderedObject> ProductionProgramType MP RunsPlanned 0:HasProperty Variable IsValid Boolean PropertyType M, RO The Identifier is the identifier of the job. This Identifier is used to reference
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.4.5 ProductionActiveProgramType

ProductionJobType instance this program is used in. JobIdentifier holds the same content as the Identifier Property of the ProductionJobType instance this program is used in. State is inherited from
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.4.7 ProductionPartType

HasProperty Variable Name 0:String 0:PropertyType M, RO 0:HasProperty Variable Identifier 0:String 0:PropertyType O, RO 0:HasComponent Variable PartQuality PartQuality 0:BaseDataVariableType M, RO 0:HasComponent ... This information often originates from an external system handling production organisation (e.g., MES). The Identifier is used to distinguish and identify an individual part in production in a machine
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.5.3 BaseToolType

inheriting the InstanceDeclarations of that Node. 0:HasProperty Variable Identifier 0:String 0:PropertyType O, RO 0:HasComponent Object Location 0:BaseObjectType O 0:HasProperty Variable Name 0:String ... PropertyType M, RO Location 0:HasProperty Variable PlaceNumber 0:UInt16 0:PropertyType M, RO Identifier is a unique identifier for a tool. The Identifier can be used to provide
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.5.4 ToolType

program or globally, independent of the machine management view, the properties Name and Identifier are provided by the BaseToolType . LastUsage is the time, where the specific tool was the active
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.6.7 PartLoadPrognosisType

available. Otherwhise, if the ProductionType is used instead, it shall be identical to the Identifier property of the ProductionPartType instance the prognosis relates to. PartName shall be identical
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.6.8 PartUnloadPrognosisType

available. Otherwhise, if the ProductionType is used instead, it shall be identical to the Identifier property of the ProductionPartType instance the prognosis relates to. PartName shall be identical
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.6.10 ProductionJobEndPrognosisType

Otherwise, if the ProductionType is used, it shall be identical to the Identifier property belonging to the ProductionJobType the prognosis refers to if modelled in the AddressSpace . Otherwise, it shall ... contain the identifier of the job. [DEPRECATED in version 1.02] The JobNodeId shall reference the 0:NodeId of the ProductionJobType instance the prognosis refers to. The JobNodeId component will
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.6.11 ToolChangePrognosisType

tool magazine or the workspace of the machine. ToolIdentifier is identical to the Identifier property of the tool to change, if applicable. If the tool is not modelled
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.6.12 ToolLoadPrognosisType

tool magazine or the workspace of the machine. ToolIdentifier contains the unique identifier of the tool. This value shall be the same as for the Identifier Property of the BaseToolType
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

8.6.13 ToolUnloadPrognosisType

tool magazine or the workspace of the machine. ToolIdentifier contains the unique identifier of the tool. This value shall be the same as for the Identifier Property of the BaseToolType
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

9.3 NotificationEventType

which means it inherits the InstanceDeclarations of that Node. 0:HasProperty Variable Identifier 0:String 0:PropertyType M, RO Conformance Units MachineTool Notification - Errors and Alerts Identifier is used
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

9.5 ProductionPartTransitionEventType

HasProperty Variable Name 0:String 0:PropertyType M, RO 0:HasProperty Variable Identifier 0:String 0:PropertyType O, RO 0:HasComponent Variable PartQuality PartQuality 0:BaseDataVariableType M, RO 0:HasComponent ... v102 0:BaseObjectType Conformance Units MachineTool Production ProductionPartStateMachineType JobIdentifier is a copy of the Identifier property of the ProductionJobType instance this part belongs to. All other Properties and Components
OPC-40501-1 – OPC UA for Machine Tools - Part 1: Machine Monitoring and Job Management

9.6 ProductionProgramTransitionEventType

transition. Name is used as defined in 8.4.4 . JobIdentifier is a copy of the Identifier property of the ProductionJobType instance this program belongs
OPC-40502 – OPC UA for Computerized Numerical Control (CNC) Systems - for CNC Systems: OPC UA Information Model

A.1 Namespace and identifiers for OPC UA Information Model for CNC Systems

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40540 – OPC UA for Additive Manufacturing

8.6 FeedstockType Definition

inheriting the InstanceDeclarations of that Node 0:HasProperty Variable Identifier 0:String 0:PropertyType M 0:HasProperty Variable ExternalIdentifier 0:String 0:PropertyType O 0:HasProperty Variable Name 0:String ... Cycle 0:UInt32 0:BaseDataVariableType O Conformance Units AdditiveManufacturing Identify & Monitor Feedstock The Identifier is the Identifier of the feedstock. This Identifier is used to determine the type
OPC-40561-1 – OPC UA for Mining - Part 1: Extraction General

A.1 Namespace and identifiers for OPC 40561-1 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40561-2 – OPC UA for Mining - Extraction - Part 2: Shearer Loader

A.1 Namespace and identifiers for OPC 40561-2 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40562-1 – OPC UA for Mining - Loading - Part 1: General

A.1 Namespace and identifiers for OPC 40562-1 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40562-2 – OPC UA for Mining - Loading - Part 2: Hydraulic Excavator

A.1 Namespace and identifiers for OPC 40562-2 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40563-1 – OPC UA for Mining - Transport Dumping - Part 1: General

A.1 Namespace and identifiers for OPC 40563-1 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40563-2 – OPC UA for Mining - Transport Dumping - Part 2: Armoured Face Conveyor

A.1 Namespace and identifiers for OPC 40563-2 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40563-3 – OPC UA for Mining - Transport Dumping - Part 3: Rear Dump Truck

A.1 Namespace and identifiers for OPC 40563-3 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40564-1 – OPC UA for Mining - Mineral Processing - Part 1: General

Annex A OPC 40563-1 Namespace and mappings (Normative)

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40564-2 – OPC UA for Mining - Mineral Processing - Part 2: Rock Crusher

A.1 Namespace and identifiers for OPC 40564-2 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40565-1 – OPC UA for Mining - Development Support - Part 1: General

A.1 Namespace and identifiers for OPC 40565-1 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40565-2 – OPC UA for Mining - Development Support - Part 2: Roof Support System

A.1 Namespace and identifiers for OPC 40565-2 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40565-3 – OPC UA for Mining - Development - Part 3: Dozer

10.1 Namespace and identifiers for OPC 40565-3 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40566-1 – OPC UA for Mining - Monitoring Supervision Services - Part 1: General

A.1 Namespace and identifiers for OPC 40566-1 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40567-1 – OPC UA for Mining - PELO Services - Part 1: General

A.1 Namespace and identifiers for OPC 40567-1 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40567-2 – OPC UA for Mining - PELO Services - Part 2: Face Alignment System

A.1 Namespace and identifiers for OPC 40567-2 Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending
OPC-40600 – OPC UA for Weihenstephan Standards

A.1 Namespace and identifiers for OPC UA for Weihenstephan Standards Information Model

specified in a CSV file with the following syntax: <SymbolName>, <Identifier>, <NodeClass> Where the SymbolName is either the BrowseName of a Type Node ... BrowsePath for an Instance Node that appears in the specification and the Identifier is the numeric value for the NodeId . The BrowsePath for an Instance Node is constructed by appending