1 Scope

This specification was created by a joint working group of the OPC Foundation and FieldComm Group Project Group Device Information Model. It defines the OPC UA Information Model to represent and access Process Automation Devices.

OPC Foundation

OPC is the interoperability standard for the secure and reliable exchange of data and information in the industrial automation space and in other industries. It is platform independent and ensures the seamless flow of information among devices from multiple vendors. The OPC Foundation is responsible for the development and maintenance of this standard.

OPC UA is a platform independent service-oriented architecture that integrates all the functionality of the individual OPC Classic specifications into one extensible framework. This multi-layered approach accomplishes the original design specification goals of:

Platform independence: from an embedded microcontroller to cloud-based infrastructure

Secure: encryption, authentication, authorization and auditing

Extensible: ability to add new features including transports without affecting existing applications

Comprehensive information modelling capabilities: for defining any model from simple to complex

FieldComm Group

FieldComm Group is a global standards-based non-profit member organization consisting of leading process end users, manufacturers, universities and research organizations that work together to direct the development, incorporation and implementation of communication technologies for the process industries. Membership is open to anyone interested in the use of the technologies. In addition to HART and Foundation Fieldbus communication technologies, FieldComm Group is responsible for ongoing development of Field Device Integration (FDI) Technology.

2 Normative references

The following referenced documents are indispensable for the application of this specification. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments and errata) applies.

OPC 10000-1, OPC Unified Architecture - Part 1: Overview and Concepts

3 Terms, abbreviated terms and conventions

3.1 Overview

It is assumed that basic concepts of OPC UA information modelling are understood in this specification. This specification will use these concepts to describe the Process Automation Device Information Model. For the purposes of this document, the terms and definitions given in OPC 10000-1, OPC 10000-3, OPC 10000-4, OPC 10000-5, OPC 10000-7, OPC 10000-8, OPC 10000-19, and OPC 10000-100 as well as the following apply.

Note that OPC UA terms and terms defined in this specification are italicized in the specification.

3.2 OPC UA for PA-DIM terms

3.2.1 Process Automation Device

Industrial Process Automation Device for specific measuring tasks such as flow, level, pressure and temperature as well as for actuators.

3.3 Abbreviated terms

3.4 Conventions used in this document

3.4.1 Conventions for Node descriptions

3.4.1.1 Node definitions

Node definitions are specified using tables (see Table 2).

Attributes are defined by providing the Attribute name and a value, or a description of the value.

References are defined by providing the ReferenceType name, the BrowseName of the TargetNode and its NodeClass.

If the TargetNode is a component of the Node being defined in the table the Attributes of the composed Node are defined in the same row of the table.

The DataType is only specified for Variables; “[<number>]” indicates a single-dimensional array, for multi-dimensional arrays the expression is repeated for each dimension (e.g. [2][3] for a two-dimensional array). For all arrays the ArrayDimensions is set as identified by <number> values. If no <number> is set, the corresponding dimension is set to 0, indicating an unknown size. If no number is provided at all the ArrayDimensions can be omitted. If no brackets are provided, it identifies a scalar DataType and the ValueRank is set to the corresponding value (see OPC 10000-3). In addition, ArrayDimensions is set to null or is omitted. If it can be Any or ScalarOrOneDimension, the value is put into “{<value>}”, so either “{Any}” or “{ScalarOrOneDimension}” and the ValueRank is set to the corresponding value (see OPC 10000-3) and the ArrayDimensions is set to null or is omitted. Examples are given in Table 1.

The TypeDefinition is specified for Objects and Variables.

The TypeDefinition column specifies a symbolic name for a NodeId, i.e. the specified Node points with a HasTypeDefinition Reference to the corresponding Node.

The ModellingRule of the referenced component is provided by specifying the symbolic name of the rule in the ModellingRule column. In the AddressSpace, the Node shall use a HasModellingRule Reference to point to the corresponding ModellingRule Object.

If the NodeId of a DataType is provided, the symbolic name of the Node representing the DataType shall be used.

Note that if a symbolic name of a different namespace is used, it is prefixed by the NamespaceIndex (see3.4.2.2).

Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType, their NodeClass and their BrowseName are specified. A reference to another part of this document points to their definition. Table 2 illustrates the table. If no components are provided, the DataType, TypeDefinition and Other columns may be omitted and only a Comment column is introduced to point to the Node definition.

Each Type Node or well-known Instance Node defined shall have one or more ConformanceUnits defined in Error! Reference source not found. that require the Node to be in the AddressSpace.

The relations between Nodes and ConformanceUnits are defined at the end of the tables defining Nodes, one row per ConformanceUnit. The ConformanceUnits are reflected in the Category element for the Node definition in the UANodeSet (see OPC 10000-6).

The list of ConformanceUnits in the UANodeSet allows Servers to optimize resource consumption by using a list of supported ConformanceUnits to select a subset of the Nodes in an Information Model.

When a Node is selected in this way, all dependencies implied by the References are also selected.

Dependencies exist if the Node is the source of HasTypeDefinition, HasInterface, HasAddIn or any HierarchicalReference. Dependencies also exist if the Node is the target of a HasSubtype Reference. For Variables and VariableTypes, the value of the DataType Attribute is a dependency. For DataType Nodes, any DataTypes referenced in the DataTypeDefinition Attribute are also dependencies.

For additional details see OPC 10000-5.

Components of Nodes can be complex, that is containing components by themselves. The TypeDefinition, NodeClass and DataType can be derived from the type definitions, and the symbolic name can be created as defined in 3.4.3.1. Therefore, those contained components are not explicitly specified; they are implicitly specified by the type definitions.

The Other column defines additional characteristics of the Node. Examples of characteristics that can appear in this column are shown in Table 3.

If multiple characteristics are defined they are separated by commas. The name or the short name may be used.

3.4.1.2 Additional References

To provide information about additional References, the format as shown in Table 4 is used.

References can be to any other Node.

3.4.1.3 Additional sub-components

To provide information about sub-components, the format as shown in Table 5 is used.

3.4.1.4 Additional Attribute values

This type of tables is used in this document to define the default values for specific nodes. The type definition table provides columns to specify the values for required Node Attributes for InstanceDeclarations. To provide information about additional Attributes, the format as shown in Table 6 is used.

There can be multiple columns to define more than one Attribute.

3.4.2 NodeIds and BrowseNames

3.4.2.1 NodeIds

The NodeIds of all Nodes described in this standard are only symbolic names. Annex A defines the actual NodeIds.

The symbolic name of each Node defined in this specification is its BrowseName, or, when it is part of another Node, the BrowseName of the other Node, a “.”, and the BrowseName of itself. In this case “part of” means that the whole has a HasProperty or HasComponent Reference to its part. Since all Nodes not being part of another Node have a unique name in this specification, the symbolic name is unique.

The NamespaceUri for all NodeIds defined in this specification is defined in Annex A. The NamespaceIndex for this NamespaceUri is Server-specific and depends on the position of the NamespaceUri in the server namespace table.

Note that this specification not only defines concrete Nodes, but also requires that some Nodes shall be generated, for example one for each Session running on the Server. The NodeIds of those Nodes are Server-specific, including the namespace. But the NamespaceIndex of those Nodes cannot be the NamespaceIndex used for the Nodes defined in this specification, because they are not defined by this specification but generated by the Server.

3.4.2.2 BrowseNames

The text part of the BrowseNames for all Nodes defined in this specification is specified in the tables defining the Nodes. The NamespaceUri for all BrowseNames defined in this specification is defined in Annex A.

For InstanceDeclarations of NodeClass Object and Variable that are placeholders (OptionalPlaceholder and MandatoryPlaceholder ModellingRule), the BrowseName and the DisplayName are enclosed in angle brackets (<>) as recommended in OPC 10000-3. If the BrowseName is not defined by this specification, a namespace index prefix is added to the BrowseName (e.g., prefix '0' leading to ‘0:EngineeringUnits’ or prefix '2' leading to ‘2:DeviceRevision’). This is typically necessary if a Property of another specification is overwritten or used in the OPC UA types defined in this specification. Table 290 and Table 291 provide a list of namespaces and their indexes as used in this specification.

3.4.3 Common Attributes

3.4.3.1 General

The Attributes of Nodes, their DataTypes and descriptions are defined in OPC 10000-3. Attributes not marked as optional are mandatory and shall be provided by a Server. The following tables define if the Attribute value is defined by this specification or if it is server-specific.

For all Nodes specified in this specification, the Attributes named in Table 7 shall be set as specified in the table.

3.4.3.2 Objects

3.4.3.3 Variables

For all Variables specified in this specification, the Attributes named in Table 9 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

3.4.3.4 VariableTypes

For all VariableTypes specified in this specification, the Attributes named in Table 10 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

3.4.3.5 Methods

For all Methods specified in this specification, the Attributes named in Table 11 shall be set as specified in the table. The definitions for the Attributes can be found in OPC 10000-3.

3.4.3.6 Structures

OPC 10000-3 differentiates between different kinds of Structures. The following conventions explain, how these Structures shall be defined.

The first kind are Structures without optional fields where none of the fields allows subtype (except fields with abstract DataTypes). Its definition is in Table 12.

The second kind are Structures with optional fields where none of the fields allows subtypes (except fields with abstract DataTypes). Its definition is in Table 13.

Structures with fields that are optional have an “Optional” column. Fields that are optional have True set, otherwise False.

The third kind are Structures without optional fields where one or more of the fields allow subtypes. Its definition is in Table 14.

Structures with fields that allow subtypes have an “Allow Subtypes” column. Fields that allow subtypes have True set, otherwise False. Fields with abstract DataTypes can always be subtyped.

4 General information about PA-DIM and OPC UA

4.1 Introduction to Process Automation Device

Process Automation Devices are used within Industrial Automation Systems of Chemicals, Oil & Gas, Food & Beverage, Power generation, Metals, Cement, Mining & Minerals, Pulp & Paper, Water & Waste Water and measure pressure, temperature, flow, level, etc. or position valves with control actuators. Process Automation Devices are often connected to Control Systems and Plant Asset Management.

For the lifecycle commissioning, operation or maintenance, a minimum common set of Process Automation Device parameters and functions is necessary. With the concepts of Industrie 4.0 and IoT, the lifecycle is extended and starts already with procurement, which uses Common Data Dictionaries (CDD) like IEC 61987 and ECLASS. Each property (variable, parameter, etc.) within a CDD has a unique identifier (e.g. an IRDI).

This Process Automation Device Companion Specification defines the fieldbus protocol independent Information Model. This model includes a minimum set of parameters to provide interoperability and interchangeability for the main use cases of:

Identification,

Diagnostics,

Process Values and

Configuration

for Pressure, Temperature, Flow, Level, Control Actuator/Positioner applications. This Model includes support for the entire lifecycle.

In relation to this companion specification, the IEC 62769, Field Device Integration (FDI) specification defines the device configuration (online/offline) with a PC tool or mobile device including the definition of the User Interface (UI).

The collaboration of FieldComm Group and OPC Foundation aim is a protocol independent information model.

4.2 Introduction to OPC Unified Architecture

4.2.1 What is OPC UA?

OPC UA is an open and royalty free set of standards designed as a universal communication protocol. While there are numerous communication solutions available, OPC UA has key advantages:

A state of art security model (see OPC 10000-2)

A fault tolerant communication protocol.

An information modelling framework that allows application developers to represent their data in a way that makes sense to them.

OPC UA has a broad scope which delivers for economies of scale for application developers. This means that a larger number of high-quality applications at a reasonable cost are available. When combined with semantic models such as OPC UA for Process Automation Devices – PA-DIM, OPC UA makes it easier for end users to access data via generic commercial applications.

The OPC UA model is scalable from small devices to ERP systems. OPC UA Servers process information locally and then provide that data in a consistent format to any application requesting data - ERP, MES, PMS, Maintenance Systems, HMI, Smartphone or a standard Browser, for examples. For a more complete overview see OPC 10000-1.

4.2.2 Basics of OPC UA

As an open standard, OPC UA is based on standard internet technologies, like TCP/IP, HTTP and Web Sockets.

As an extensible standard, OPC UA provides a set of Services (see OPC 10000-4) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor-defined information in a standard way. More importantly all OPC UA Clients are expected to be able to discover and use vendor-defined information. This means OPC UA users can benefit from the economies of scale that come with generic visualization and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users.

OPC UA Clients can be any consumer of data from another device on the network to browser based thin clients and ERP systems. The full scope of OPC UA applications is shown in Figure 1.

OPC UA provides a robust and reliable communication infrastructure having mechanisms for handling lost messages, failover, heartbeat, etc. With its binary encoded data, it offers a high-performing data exchange solution. Security is built into OPC UA as security requirements become more and more important especially since environments are connected to the office network or the internet and attackers are starting to focus on automation systems.

4.2.3 Information modelling in OPC UA

4.2.3.1 Concepts

OPC UA provides a framework that can be used to represent complex information as Objects in an AddressSpace which can be accessed with standard services. These Objects consist of Nodes connected by References. Different classes of Nodes convey different semantics. For example, a Variable Node represents a value that can be read or written. The Variable Node has an associated DataType that can define the actual value, such as a string, float, structure etc. It can also describe the Variable value as a variant. A Method Node represents a function that can be called. Every Node has a number of Attributes including a unique identifier called a NodeId and non-localized name called a BrowseName. An Object representing a ‘Reservation’ is shown in Figure 2.

Object and Variable Nodes represent instances and they always have a HasTypeDefinition reference to a Node (ObjectType or VariableType Node) which describes their semantics and structure. Figure 3 illustrates the relationship between an instance and its TypeDefinition.

The type Nodes are templates that define all of the children that can be present in an instance of the type. In the example in Figure 3 the PersonType ObjectType defines two children: First Name and Last Name. All instances of PersonType are expected to have the same children with the same BrowseNames. Within a type the BrowseNames uniquely identify the children. This means Client applications can be designed to search for children based on the BrowseNames from the type instead of NodeIds. This eliminates the need for manual configuration of systems if a Client uses types that multiple Servers implement.

4.2.3.2 Namespaces

OPC UA allows information from many different sources to be combined into a single coherent AddressSpace. Namespaces are used to make this possible by eliminating naming and id conflicts between information from different sources. Each namespace in OPC UA has a globally unique string called a NamespaceUri which identifies a naming authority and a locally unique integer called a NamespaceIndex, which is an index into the Server's table of NamespaceUris. The NamespaceIndex is unique only within the context of a Session between an OPC UA Client and an OPC UA Server- the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed. The Services defined for OPC UA use the NamespaceIndex to specify the Namespace for qualified values.

There are two types of structured values in OPC UA that are qualified with NamespaceIndexes: NodeIds and QualifiedNames. NodeIds are locally unique (and sometimes globally unique) identifiers for Nodes. The same globally unique NodeId can be used as the identifier in a node in many Servers – the node's instance data may vary but its semantic meaning is the same regardless of the Server it appears in. This means Clients can have built-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 are non-localized names qualified with a Namespace. They are used for the 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 do not have that restriction.

4.2.3.3 Companion Specifications

An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes, VariableTypes, DataTypes and ReferenceTypes that represent the concepts used in the vertical market, and potentially also well-defined Objects as entry points into the AddressSpace.

5 Use cases

The use cases covered in this version are listed in Table 15. These use cases can be broken into Telemetric and Asset Management categories. Telemetric use cases publish dynamic data e.g. to a cloud application for remote monitoring. Asset Management use cases require client server interaction with the information model typically for on-premises applications.

Use cases define the content of this Device Information Model. NAMUR Open Architecture (NE175) defines uses cases with parameters, names and semantic ids, which are an important input for the definition of the PA-DIM. Additional details about these use cases can be found in the NAMUR descriptions found on their web site referenced in Section 2.

6 Process Automation Device Information Model overview

6.1 Overview

This specification describes a unified Process Automation Device Information Model (PA-DIM) that enables protocol and vendor independent data exchange. Figure 6 provides an example illustration of a system in which two Devices interact with several applications running in the cloud and accessing generic and product type data. The Information Model of these two devices includes a standardized device model based on PA-DIM. The model also exposes IEC 61987 semantic dictionary IDs. These IDs may be used by OPC UA clients to obtain the definition of vendor specific data the devices may contain.

PA-DIM makes use of the Dictionary Reference model defined in OPC 10000-19 and defines the proper International Registration Data Identifiers (IRDI) for entries in the IEC 61987 CDD. The OPC Foundation added an abstract DictionaryEntryType ObjectType to the OPC 10000-5 specification. It also introduced the IrdiDictionaryEntryType (Subtype of DictionaryEntryType) ObjectType for semantic information and the HasDictionaryEntry Non-Hierarchical ReferenceType to associate the dictionary entry object to any node.

The PA-DIM, illustrated in Figure 7, defines a base device concept and information model, which is intended to be used for Process Automation Devices. This PA-DIM OPC UA Companion Specification defines the OPC UA BrowseNames and corresponding IEC 61987 Semantic CDD Dictionary IDs. For each Node with a dictionary reference to the IEC 61987 Common Data Dictionary, the definition of the referenced IEC 61987 CDD entry applies. It is expected, that ECLASS semantic description will follow the IEC 61987 standardization where applicable.

The PADIMType has a HasDictionaryEntry reference to an IRDI representing a class identifier within the IEC 61987 CDD (e.g. Coriolis Flowmeter, Pressure Transmitter, etc.).

The DisplayName Attribute for all Objects, Variables, and Methods with a DictionaryReference in this specification shall be according to the IEC 61987 attribute “Short name” for CDD properties or to the IEC 61987 attribute “Preferred name” for CDD classes. DisplayNames are used for configuration dialog displays and are defined within IEC 61987 CDD. NAMUR NE131 / NOA device parameter names are in line with IEC 61987 CDD.

PA-DIM defines the Interfaces IAdministrationType for administration purposes and ISignalSetType as a container for process variables (see7.1.2). The PADIMType includes these Interfaces, and additionally it includes the IDeviceHealthType, provided by OPC 10000-100OPC 10000-100. Furthermore PADIMType provides a reference to an IRDI dictionary entry to reference the device class (e.g. Pressure Transmitter or Coriolis Mass Flowmeter) and SubDevices Object for modular devices. In this version of PA-DIM the information model has been extended with additional objects and interfaces for Process Analysers. For more details see section 6.2.

Instances of PADIMType represent devices in the real-world. There might be other OPC UA companion specifications representing different aspects of the same real-world device, potentially represented in the same OPC UA Server. Therefore, the guidelines defined in the OPC UA for Devices specification (OPC 10000-100 Annex C) should be followed, when an OPC UA server represents several companion specifications for the same real-world device.

6.2 Process Analyser

The Object Model for Process Analyser has been extended as shown in Figure 8. The blue marked boxes are from PA-DIM 1.00 and the orange boxes have been added for Process Analysers in version 1.01. Figure 9 and Figure 10 are the extension of Figure 8.

There are special Process Analyser Types and corresponding interfaces shown in Figure 9.

There are special Analytical Signal Types and corresponding interfaces for each Process Analyser, see Figure 10.

6.3 General rules

A device is required to provide mandatory functionality. Optional functionality is not required, but if it is provided, it shall be supported as defined.

The IEC 61987 CDD is the source for the definition of properties according to IEC 61987 specification, which have an IRDI dictionary entry. These definitions include a version at the end after the “#” (e.g. #001). For easier readability, some IRDI dictionary definitions have been copied and added to this specification. Although highly unlikely, the IRDI definitions in this specification may deviate from IEC definitions as the IEC specification may change. In such cases the IEC 61987 CDD specification has precedence over the definitions in this specification.

The IRDI dictionary entries are referenced from the TypeDefinitions in this specification. When instantiating the TypeDefinitions, the instances shall have the same IRDI dictionary entries as defined for the TypeDefinitions in this specification. If an instance is based on a subtype, it shall have all IRDI dictionary entries of the subtype, and of the supertypes, as defined in this specification. The same applies for InstanceDeclarations. All instances based on InstanceDeclarations shall have the same IRDI dictionary entries as their InstanceDeclaration. If the InstanceDeclaration is overridden, also the references to the IRDI dictionary entry objects of the supertypes shall be provided.

Note: As HasDictionaryEntry Reference is a non-hierarchical Reference and the IRDI Objects do not have ModellingRules, the OPC UA Information Model does not force the creation of HasDictionaryEntry references during instantiation automatically.

The primary unit according to IEC 61987 CDD should be used as default unit and may be modified if applicable.

7 PA-DIM Object Types

7.1 PA-DIM Interfaces

7.1.1 IAdministrationType

The IAdministrationType provides the interface to administration variables and methods of the device and is formally defined in Table 16.

DisplayLanguage: is the language used for the local display of the device. ABN597#004 defines language or languages set on the display.

DateOfLastChange: ABN604#001 defines parameter indicating the date and time at which one of the device parameters was changed the last time.

FactoryReset: ABN609#002 property the value of which indicates the kind of reset function to be executed. Note: Properties can be variables or methods according IEC 61987 CDD.

The components of IAdministrationType have additional references which are defined in Table 17.

The child Nodes of the IAdministrationType have additional Attribute values defined in Table 18.

7.1.2 ISignalSetType

The ISignalSetType provides the interface to process variables of the device and is formally defined in Table 19.

SignalSet is a container object for the process variables of the device.

7.1.3 ICalibrationType

The ICalibrationType provides the interface to calibration variables of the sensor resp. signal and is formally defined in Table 20.

The components of ICalibrationType have additional references which are defined in Table 21.

The child Nodes of the ICalibrationType have additional Attribute values defined in Table 22.

7.1.4 IConductivityCalibrationType

The IConductivityCalibrationType provides the interface to conductivity measurement specific calibration variables of the sensor resp. signal and is formally defined in Table 23.

The components of IConductivityCalibrationType have additional references which are defined in Table 24.

The child Nodes of the IConductivityCalibrationType have additional Attribute values defined in Table 25.

7.1.5 IAmperometricCalibrationType

The IAmperometricCalibrationType provides the interface to amperometric measurement specific calibration variables of the sensor resp. signal and is formally defined in Table 26.

The components of IAmperometricCalibrationType have additional references which are defined in Table 27.

The child Nodes of the IAmperometricCalibrationType have additional Attribute values defined in Table 28.

7.1.6 IOpticalFluorescenseQuenchingCalibrationType

The IOpticalFluorescenseQuenchingCalibrationType provides the interface to optical fluorescence quenching measurement specific calibration variables of the sensor resp. signal and is formally defined in Table 29.

The components of IOpticalFluorescenseQuenchingCalibrationType have additional references which are defined in Table 30.

The child Nodes of the IOpticalFluorescenseQuenchingCalibrationType have additional Attribute values defined in Table 31.

7.1.7 IGasChromatographCalibrationType

The IGasChromatographCalibrationType provides the interface to gaschromatograph measurement specific calibration variables of the sensor resp. signal and is formally defined in Table 32.

CalibrationRange1ResponseFactor is defined by IRDI as ABQ024#001 which states "ratio between the concentration of a compound being analysed and the response of the detector to that compound for the calibration range 1".

CalibrationRange1LowerRangeValue is defined by IRDI as ABQ025#001 which states "volume concentration value assigned to the lower range end-value of calibration range 1".

CalibrationRange1UpperRangeValue is defined by IRDI as ABQ026#001 which states "volume concentration value assigned to the upper range end-value of calibration range 1".

CalibrationRange2ResponseFactor is defined by IRDI as ABQ027#001 which states "ratio between the concentration of a compound being analysed and the response of the detector to that compound for the calibration range 2".

CalibrationRange2LowerRangeValue is defined by IRDI as ABQ028#001 which states "volume concentration value assigned to the lower range end-value of calibration range 2".

CalibrationRange2UpperRangeValue is defined by IRDI as ABQ029#001 which states "volume concentration value assigned to the upper range end-value of calibration range 2".

CalibrationRange3ResponseFactor is defined by IRDI as ABQ030#001 which states "ratio between the concentration of a compound being analysed and the response of the detector to that compound for the calibration range 3".

CalibrationRange3LowerRangeValue is defined by IRDI as ABQ031#001 which states "volume concentration value assigned to the lower range end-value of calibration range 3".

CalibrationRange3UpperRangeValue is defined by IRDI as ABQ032#001 which states "volume concentration value assigned to the upper range end-value of calibration range 3".

The components of IGasChromatographCalibrationType have additional references which are defined in Table 33.

The child Nodes of the IGasChromatographCalibrationType have additional Attribute values defined in Table 34.

7.1.8 IPhCalibrationType

The IPhCalibrationType provides the interface to pH measurement specific calibration variables of the sensor resp. signal and is formally defined in Error! Reference source not found..

The components of IPhCalibrationType have additional references which are defined in Table 36.

The child Nodes of the IPhCalibrationType have additional Attribute values defined in Table 37.

7.1.9 IGeneralDeviceConditionSetType

The IGeneralDeviceConditionSetType provides the interface to condition variables of the device and its components and is formally defined in Table 38.

<DeviceComponentIdentifier> is an optional placeholder for an object containing the condition variables related to a specific device component.

7.1.10 ITocDeviceConditionSetType

The ITocDeviceConditionSetType provides the interface to TOC device specific condition variables and is formally defined in Table 40.

The components of ITocDeviceConditionSetType have additional references which are defined in Table 41.

The child Nodes of the ITocDeviceConditionSetType have additional Attribute values defined in Table 42.

7.1.11 IFlameIonisationDeviceConditionSetType

The IFlameIonisationDeviceConditionSetType provides the interface to FID specific condition variables and is formally defined in Table 43.

The components of IFlameIonisationDeviceConditionSetType have additional references which are defined in Table 44.

The child Nodes of the IFlameIonisationDeviceConditionSetType have additional Attribute values defined in Table 45.

7.1.12 IGasChromatographDeviceConditionSetType

The IGasChromatographDeviceConditionSetType provides the interface to gas chromatograph device specific condition variables and is formally defined in Table 46

The components of IGasChromatographDeviceConditionSetType have additional references which are defined in Table 48.

The child Nodes of the IGasChromatographDeviceConditionSetType have additional Attribute values defined in Table 48.

7.1.13 IFtnirOrFtirDeviceConditionSetType

The IFtnirOrFtirDeviceConditionSetType provides the interface to Fourier Transform Near-Infrared Spectroscopy or Fourier Transform Infrared Spectroscopy device specific condition variables and is formally defined in Table 49.

The components of IFtnirOrFtirDeviceConditionSetType have additional references which are defined in Table 50.

The child Nodes of the IFtnirOrFtirDeviceConditionSetType have additional Attribute values defined in Table 51.

7.1.14 IDiodeArrayDeviceConditionSetType

The IDiodeArrayDeviceConditionSetType provides the interface to Diode array spectrometer device specific condition variables and is formally defined in Table 52.

The components of IDiodeArrayDeviceConditionSetType have additional references which are defined in Table 53.

The child Nodes of the IDiodeArrayDeviceConditionSetType have additional Attribute values defined in Table 54.

7.1.15 IRamanDeviceConditionSetType

The IRamanDeviceConditionSetType provides the interface to Raman spectrometer device specific condition variables and is formally defined in Table 55.

The components of IRamanDeviceConditionSetType have additional references which are defined in Table 56.

The child Nodes of the IRamanDeviceConditionSetType have additional Attribute values defined in Table 57.

7.1.16 INonDispersiveInfraredSignalConditionSetType

The INonDispersiveInfraredSignalConditionSetType provides the interface to NDIR measurement signal specific condition variables and is formally defined in Table 58.

The components of INonDispersiveInfraredSignalConditionSetType have additional references which are defined in Table 59.

The child Nodes of the INonDispersiveInfraredSignalConditionSetType have additional Attribute values defined in Table 60.

7.1.17 ITocSignalConditionSetType

The ITocSignalConditionSetType provides the interface to TOC measurement signal specific condition variables and is formally defined in Table 61.

The components of ITocSignalConditionSetType have additional references which are defined in Table 62.

The child Nodes of the ITocSignalConditionSetType have additional Attribute values defined in Table 63.

7.1.18 IParamagneticSignalConditionSetType

The IParamagneticSignalConditionSetType provides the interface to paramagnetic measurement signal specific condition variables and is formally defined in Table 64.

The components of IParamagneticSignalConditionSetType have additional references which are defined in Table 65.

The child Nodes of the IParamagneticSignalConditionSetType have additional Attribute values defined in Table 66.

7.1.19 IThermalConductivitySignalConditionSetType

The IThermalConductivitySignalConditionSetType provides the interface to thermal conductivity measurement signal specific condition variables and is formally defined in Table 67.

The components of IThermalConductivitySignalConditionSetType have additional references which are defined in Table 68.

The child Nodes of the IThermalConductivitySignalConditionSetType have additional Attribute values defined in Table 69.

7.1.20 ITunableDiodeLaserSignalConditionSetType

The ITunableDiodeLaserSignalConditionSetType provides the interface to TDL measurement signal specific condition variables and is formally defined in Table 70.

The components of ITunableDiodeLaserSignalConditionSetType have additional references which are defined in Table 71.

The child Nodes of the ITunableDiodeLaserSignalConditionSetType have additional Attribute values defined in Table 72.

7.1.21 IZirconiumDioxideSignalConditionSetType

The IZirconiumDioxideSignalConditionSetType provides the interface to Zirconium dioxide measurement signal specific condition variables and is formally defined in Table 73.

The components of IZirconiumDioxideSignalConditionSetType have additional references which are defined in Table 74.

The child Nodes of the IZirconiumDioxideSignalConditionSetType have additional Attribute values defined in Table 75.

7.1.22 IPhSignalConditionSetType

The IPhSignalConditionSetType provides the interface to pH measurement signal specific condition variables and is formally defined in Table 76.

The components of IPhSignalConditionSetType have additional references which are defined in Table 77.

The child Nodes of the IPhSignalConditionSetType have additional Attribute values defined in Table 78.

7.1.23 IConductivitySignalConditionSetType

The IConductivitySignalConditionSetType provides the interface to conductivity measurement signal specific condition variables and is formally defined in Table 79.

The components of IConductivitySignalConditionSetType have additional references which are defined in Table 80.

The child Nodes of the IConductivitySignalConditionSetType have additional Attribute values defined in Table 81.

7.1.24 IAmperometricSignalConditionSetType

The IAmperometricSignalConditionSetType provides the interface to amperometric measurement signal specific condition variables and is formally defined in Table 82.

The components of IAmperometricSignalConditionSetType have additional references which are defined in Table 83.

The child Nodes of the IAmperometricSignalConditionSetType have additional Attribute values defined in Table 84.

7.1.25 IAmperometricGasDetectorSignalConditionSetType

The IAmperometricGasDetectorSignalConditionSetType provides the interface to Amperometric Electrochemical signal specific condition variables and is formally defined in Table 85