1 Scope

This document (OPC 40701) specifies a Companion Specification for Surface Technology - Cleaning and Pretreatment machinery.

A cleaning and pretreatment system in this context can be any existing or future cleaning and pretreatment system. The implicit and explicit information model specified by the cleaning and pretreatment system Companion Specification will be defined as a UA companion specification using OPC UA constructs for the purpose of exchanging cleaning and pretreatment system information with OPC UA applications. It defines the required data structures, parameters, methods, state machines etc. for the communication among cleaning and pretreatment systems, between cleaning and pretreatment systems and supporting systems and from cleaning and pretreatment systems into higher level manufacturing systems (e.g. Manufacturing Execution System, MES), for information and diagnostic purposes and to set parameters regarding the cleaning and pretreatment system operation.

2 Normative references

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. 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

http://www.opcfoundation.org/documents/10000-1/

OPC 10000-2, OPC Unified Architecture - Part 2: Security Model

http://www.opcfoundation.org/documents/10000-2/

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

http://www.opcfoundation.org/documents/10000-3/

OPC 10000-4, OPC Unified Architecture - Part 4: Services

http://www.opcfoundation.org/documents/10000-4/

OPC 10000-5, OPC Unified Architecture - Part 5: Information Model

http://www.opcfoundation.org/documents/10000-5/

OPC 10000-6, OPC Unified Architecture - Part 6: Mappings

http://www.opcfoundation.org/documents/10000-6/

OPC 10000-7, OPC Unified Architecture - Part 7: Profiles

http://www.opcfoundation.org/documents/10000-7/

OPC 10000-8, OPC Unified Architecture - Part 8: Data Access

http://www.opcfoundation.org/documents/10000-8/

OPC 10000-16, OPC Unified Architecture - Part 16: State Machines

http://www.opcfoundation.org/documents/10000-16/

OPC 10000-100, OPC Unified Architecture - Part 100: Devices

http://www.opcfoundation.org/documents/10000-100/

OPC 10000-200, OPC Unified Architecture - Part 200: Industrial Automation

http://www.opcfoundation.org/documents/10000-200/

OPC 40001-1, OPC UA for Machinery - Part 1: Basic Building Blocks

http://www.opcfoundation.org/documents/40001-1/

OPC 40001-2, OPC UA for Machinery - Part 2: Machinery Process Values

http://www.opcfoundation.org/documents/40001-2/

OPC 40700, OPC UA for Surface Technology - General Types

http://www.opcfoundation.org/documents/40700/

3 Terms, definitions and conventions

3.1 Overview

It is assumed that basic concepts of OPC UA information modelling, OPC UA for Machinery and OPC UA for Surface Technology - General Types are understood in this specification. This specification will use these concepts to describe the Cleaning and Pretreatment Machinery Information Model. For the purposes of this document, the terms and definitions given in OPC 10000-1, OPC 10000-2, OPC 10000-3, OPC 10000-4, OPC 10000-5, OPC 10000-6, OPC 10000-7, OPC 10000-8, OPC 10000-16, OPC 10000-17, OPC 10000-100, OPC 10000-200, OPC 40001-1, OPC 30081, OPC 40001-2, OPC 10031-4, OPC 40001-3 and OPC 40700 as well as the following apply.

3.2 Abbreviated terms

3.3 Conventions used in this document

3.3.1 Conventions for Node descriptions

3.3.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 (see 3.3.2.2).

Nodes of all other NodeClasses cannot be defined in the same table; therefore only the used ReferenceType, their NodeClass and their 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 ModellingRule 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 8.1 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.3.3.1. Therefore, those containing 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 show in Table 3.

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

3.3.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.3.1.3 Additional sub-components

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

3.3.1.4 Additional Attribute values

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.3.2 NodeIds and BrowseNames

3.3.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 document 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 document, the symbolic name is unique.

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

Note that this document 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 document, because they are not defined by this document but generated by the Server.

3.3.2.2 BrowseNames

The text part of the BrowseNames for all Nodes defined in this document is specified in the tables defining the Nodes. The NamespaceUri for all BrowseNames defined in this document is defined in 9.2.

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 document, 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 document. Table 60 provides a list of namespaces and their indexes as used in this document.

3.3.3 Common Attributes

3.3.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.3.3.2 Objects

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

3.3.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.3.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.3.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.3.4 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 to Cleaning and Pretreatment Machinery and OPC UA

4.1 Introduction to Cleaning and Pretreatment Machinery

Cleaning and pretreatment machinery plays a vital role in ensuring that workpieces are free from interfering contaminants before entering subsequent production steps. Cleaning and pretreatment processes remove unwanted residues and prepare components for further processing. The importance of cleaning is evident in its ability to eliminate production media and agents, chips, and other contaminants that accumulate during manufacturing, ensuring that each component is suitably prepared for the next production stage while maintaining specified quality requirements of the final product. There are several types of cleaning and pretreatment machinery available. Through-line systems allow components to move continuously through the cleaning process, making them ideal for high-volume production where speed and consistency are essential. Chamber cleaning systems facilitate multiple cleaning processes within a single chamber or designated zone, integrating several steps into one compact unit. Line immersion systems consist of multiple chambers or zones through which a workpiece is passed. In these systems, the process is not necessarily sequential, as the workpiece may skip certain baths or zones, and not all zones need to be active at once depending on the active cleaning recipe. The information model covers these machine types using a modular approach introduced in OPC 40700, OPC UA for Surface Technology - General Types, which allows for the specific machine to be represented by multiple zones with their respective machine components. By means of sensors, process data like power consumption, media consumption, temperature, pressure etc. can be recorded and used for process monitoring and control.

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 Surface Technology - Cleaning and Pretreatment, 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, 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 as BrowseName. An Object representing a 'Reservation' is shown in Figure 2.

Object and Variable Nodes represent instances and they always reference a TypeDefinition (ObjectType or VariableType) Node which describes their semantics and structure. Figure 3 illustrates the relationship between 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 reconfiguration of systems if a Client uses types that multiple Servers implement.

OPC UA also supports the concept of sub-typing. This allows a modeller to take an existing type and extend it. There are rules regarding sub-typing defined in OPC 10000-3, but in general they allow the extension of a given type or the restriction of a DataType. For example, the modeller may decide that the existing ObjectType in some cases needs an additional Variable. The modeller can create a subtype of the ObjectType and add the Variable. A Client that is expecting the parent type can treat the new type as if it was of the parent type. Regarding DataTypes, Subtypes can only restrict. If a Variable is defined to have a numeric value, a sub type could restrict it to a float.

References allow Nodes to be connected in ways that describe their relationships. All References have a ReferenceType that specifies the semantics of the relationship. References can be hierarchical or non-hierarchical. Hierarchical references are used to create the structure of Objects and Variables. Non-hierarchical are used to create arbitrary associations. Applications can define their own ReferenceType by creating Subtypes of an existing ReferenceType. Subtypes inherit the semantics of the parent but may add additional restrictions. Figure 4 depicts several References, connecting different Objects.

The figures above use a notation that was developed for the OPC UA specification. The notation is summarized in Figure 5. UML representations can also be used; however, the OPC UA notation is less ambiguous because there is a direct mapping from the elements in the figures to Nodes in the AddressSpace of an OPC UA Server.

A complete description of the different types of Nodes and References can be found in OPC 10000-3 and the base structure is described in OPC 10000-5.

OPC UA specification defines a very wide range of functionality in its basic information model. It is not required that all Clients or Servers support all functionality in the OPC UA specifications. OPC UA includes the concept of Profiles, which segment the functionality into testable certifiable units. This allows the definition of functional subsets (that are expected to be implemented) within a companion specification. The Profiles do not restrict functionality, but generate requirements for a minimum set of functionality (see OPC 10000-7)

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

5.1 Identify machines in a standardized way

Machines of different manufacturers shall be identifiable in a standardized manner. To realize this, a number of basic and static information like manufacturer name and serial number are offered on the information model.

5.2 Current status of the machine

The user would like to monitor information about a specific MachineryItem, like the state or operation mode, for example to get a quick overview of the current state and bottlenecks (localization of errors), to recognize trends or to determine the relevant times (productive time, standby time, etc.) for subsequent KPI calculations (e.g. for calculating reliability and availability). Further information for the KPI calculation might be necessary.

5.3 Quality assurance/traceability

The user wants to be able to create a good and comprehensive representation of process parameters using standardized modelling of process values. This should enable the monitoring and traceability of production processes and consumption of energy and process media.

5.4 M2M communication and orchestration

The information model should allow a higher-level control system to oversee production and organize the orchestration of several machines in the production chain. This also requires the exchange of data between the respective machines. One purpose of this orchestration is to allow for energy and resource flexibility in scheduling and triggering cleaning jobs/ recipes in relation to the available energy and resource supply and cost.

5.5 Find all components of a machine

With the help of a standardized information model structure, components of a machine must be mapped in the same way in the different machine objects. This enables the standardized location of machine components.

5.6 Illustration of the physical systems network

If several systems are in a line, the information model should make it possible to visualize the points of contact between the different plant sections using references.

5.7 Preventive Maintenance

The standardized modelling of different counters should make it possible to provide data to fulfil the use case of preventive maintenance.

5.8 Harmonizing with existing standards

If available, the customer wants to be able to fall back on cross-industry preparatory work and comply with existing standards. The OPC UA for Machinery standard should be mentioned here in particular. If possible and sensible, different building blocks from OPC UA for Machinery should be implemented in the information model of the material supply system.

6 Cleaning and Pretreatment Machinery Information Model overview

This section provides an overview of the OPC UA information model for cleaning and pretreatment machinery.

The information model is based on and extends the Companion Specification for Surface Technology (ST) - General Types (STGeneral), which is structured to represent the physical machine and its system components in a modular way. This is necessary due to the complex and varied nature of cleaning and pretreatment machinery, that was described in Section 4.1, allowing for a large variety in machine construction and configuration.

The approach of STGeneral is to model a cleaning and pretreatment machine as a collection of different systems, representing different zones or functionalities of the overall machine (e.g. cleaning zone, rinsing zone, handling system etc.).

A visual example of a machine layout is depicted in Figure 6. Each one of these systems is modelled as a machine in accordance with OPC UA for Machinery and can contain additional components of 3:MachineComponentsType, which serve to model the structure and location of sensors in single systems in more detail (e.g. multiple heating elements, pumps and a tank or vessel within a cleaning zone).

The different Systems of a cleaning and pretreatment machine can be modelled as Subtypes of the abstract 9:STSysType inherited from STGeneral. On its first level, it contains folders for 3:MachineryBuildingBlocks as well as AddIns for Monitoring and Components. Each system can be identified, and relevant process parameters can be monitored either on the system or on the component level.

The structure of the overall cleaning and pretreatment machine can be modelled using the 0:IsPhysicallyConnectedTo and 0:Controls references (e.g. to describe a specific sequence of zones or systems within a machine).

The AddIn Components contains the sub-components of a specific System. Components are Subtypes of the abstract 9:STCompType inherited from STGeneral. The Structure of 9:STCompType is similar to 9:STSysType but does not contain additional sub-components and is primarily used to identify and describe components and to monitor specific process parameters on the component level.

7 OPC UA ObjectTypes

Each instance of a cleaning and pretreatment machine consists of a set of multiple subsystems (Subtypes of 9:STSysType) and their respective components (Subtypes of 9:STCompType) that are controlled by a single machine controller (PLC). 9:STSysType and 9:STCompType are abstract types inherited from STGeneral that serve to standardize the general modelling logic of machinery in the surface technology sector. The Subtypes defined in this Companion Specification serve to extend this modelling logic and to standardize subsystems, components and process parameters specific to cleaning and pretreatment machinery.

Figure 7 shows all ObjectTypes which are defined by this companion specification.

7.1 STSysAuxiliaryType ObjectType Definition

The STSysAuxiliaryType provides relevant variables and parameters for controlling and monitoring auxiliary systems or zones of a cleaning and pretreatment machine and is formally defined in Table 15.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

Components is an add-in used to assign components (e.g. of STCompType) to the system.

The components of the STSysAuxiliaryType have additional subcomponents which are defined in Table 16.

ParticleCountClassXLiquid is a placeholder to represent the measured or calculated number of particles of a specified size class (Size Class X) in liquid of the rinsing or cleaning stage in relation to a reference volume as specified by VDA 19/ISO 16232. This parameter can be re-used for each Size Class required for evaluation. Suggested unit: -.

7.2 STSysCleaningType ObjectType Definition

The STSysCleaningType provides relevant variables and parameters for controlling and monitoring a cleaning station or zone of a cleaning and pretreatment machine and is formally defined in Table 17.

Components is an add-in used to assign components (e.g. of STCompType) to the system.

The components of the STSysCleaningType have additional subcomponents which are defined in Table 18.

7.3 STSysConveyorType ObjectType Definition

The STSysConveyorType provides relevant variables and parameters for controlling and monitoring conveyor-systems or zones of a cleaning and pretreatment machine and is formally defined in Table 19. The Conveyor System serves to feed the workpiece to the cleaning and pretreatment machine and remove it after the cleaning and pretreatment process has concluded.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

Components is an add-in used to assign components (e.g. of STCompType) to the system.

The components of the STSysConveyorType have additional subcomponents which are defined in Table 20.

MovementSpeed describes the speed at which the parts are transported through a cleaning machine. Movement speed is crucial for the quality of a cleaning process. Suggested unit: m/s.

7.4 STSysDryingType ObjectType Definition

The STSysDryingType provides relevant variables and parameters for controlling and monitoring a drying station or zone of a cleaning and pretreatment machine and is formally defined in Table 21.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

Components is an add-in used to assign components (e.g. of STCompType) to the system.

The components of the STSysDryingType have additional subcomponents which are defined in Table 22.

EmissionControl refers to the concentration of pollutants released into a volume of air from industrial, automotive, or other sources. It plays a crucial role in minimizing environmental impact and ensuring compliance with regulatory standards for air quality. Suggested unit: ppm.

Humidity represents the measured or calculated actual relative humidity in the process chamber as well as the surrounding atmosphere. Suggested unit: %.

7.5 STSysHandlingType ObjectType Definition

The STSysHandlingType provides relevant variables and parameters for controlling and monitoring a handling station or zone of a cleaning and pretreatment machine and is formally defined in Table 23. Handling encompasses operations that serve to move the workpiece between other zones or systems of the cleaning and pretreatment machine.

Components is an add-in used to assign components (e.g. of STCompType) to the system.

The components of the STSysHandlingType have additional subcomponents which are defined in Table 24.

7.6 STSysMaterialSupplyType ObjectType Definition

The STSysMaterialSupplyType provides relevant variables and parameters for controlling and monitoring a material supply system, station or zone of a cleaning and pretreatment machine and is formally defined in Table 25.

Components is an add-in used to assign components (e.g. of STCompType) to the system.

The components of the STSysMaterialSupplyType have additional subcomponents which are defined in Table 26.

7.7 STSysQualityControlType ObjectType Definition

The STSysQualityControlType provides relevant variables and parameters for controlling and monitoring a quality control system, station or zone of a cleaning and pretreatment machine and is formally defined in Table 27.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

Components is an add-in used to assign components (e.g. of STCompType) to the system.

The components of the STSysQualityControlType have additional subcomponents which are defined in Table 28.

ParticleCountClassXPart is a placeholder to represent the measured or calculated number of particles of a specified size class (Size Class X) extracted from a workpiece or part in relation to a reference area as specified by VDA 19/ISO 16232. This parameter can be re-used for each Size Class required for evaluation. Suggested unit: -.

ParticleCountClassXLiquid is a placeholder to represent the measured or calculated number of particles of a specified size class (Size Class X) in liquid of the rinsing or cleaning stage in relation to a reference volume as specified by VDA 19/ISO 16232. This parameter can be re-used for each Size Class required for evaluation. Suggested unit: -.

FluorescencePart represents the measured fluorescence intensity of the component surface in relation to excitation power as a measure of the part cleanliness level regarding organic contaminants (oils, cooling lubes, release agents). Typically an aggregated characteristic output e.g. an average of multiple points sampled across the surface or functional areas. Suggested unit: - or RFU (relative fluorescence units).

QualityIndexPart represents the calculated Index Score of the quality-determining parameters of the components. Suggested unit: -.

ParticleWeightPart describes the particle fraction of the components determined by wash extraction in accordance with VDA 19/ISO 16232 in relation to a reference surface. Suggested unit: mg/cm².

NonVolatileResidualsPart describes the proportion of non-volatile components on the part in relation to a reference surface. Suggested unit: mg/m².

ResidualGasAnalysisWater describes the outgassing rate of water with atomic mass unit 18 remaining in a vacuum system. Suggested unit: mbar*l/s.

ResidualGasAnalysisLightHydrocarbons describes the outgassing rate of high-volatility hydrocarbons with atomic mass unit 45 - 100 remaining in a vacuum system. Suggested unit: mbar*l/s.

ResidualGasAnalysisHeavyHydrocarbons describes the outgassing rate of low-volatility hydrocarbons with atomic mass unit 101 - 200 remaining in a vacuum system. Suggested unit: mbar*l/s.

7.8 STSysRinsingType ObjectType Definition

The STSysRinsingType provides relevant variables and parameters for controlling and monitoring a rinsing station or zone of a cleaning and pretreatment machine and is formally defined in Table 29.

Components is an add-in used to assign components (e.g. of STCompType) to the system.

The components of the STSysRinsingType have additional subcomponents which are defined in Table 30.

7.9 STSysTreatmentType ObjectType Definition

The STSysTreatmentType provides relevant variables and parameters for controlling and monitoring a fluid treatment system, station or zone of a cleaning and pretreatment machine and is formally defined in Table 31.

Components is an add-in used to assign components (e.g. of STCompType) to the system.

The components of the STSysTreatmentType have additional subcomponents which are defined in Table 32.

7.10 STCompCondenserType ObjectType Definition

The STCompCondenserType provides relevant variables and parameters for controlling and monitoring a condenser component of a cleaning and pretreatment machine and is formally defined in Table 33.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

The components of the STCompCondenserType have additional subcomponents which are defined in Table 34.

Temperature represents the measured or calculated actual temperature. Suggested unit: °C.

7.11 STCompCoolerType ObjectType Definition

The STCompCoolerType provides relevant variables and parameters for controlling and monitoring a cooler component of a cleaning and pretreatment machine and is formally defined in Table 35.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

The components of the STCompCoolerType have additional subcomponents which are defined in Table 36.

CoolingPower represents the measured or calculated actual electric real power consumption of a component used for a cooling task. Suggested unit: kW.

Temperature represents the measured or calculated actual temperature. Suggested unit: °C.

7.12 STCompDryerType ObjectType Definition

The STCompDryerType provides relevant variables and parameters for controlling and monitoring a dryer component of a cleaning and pretreatment machine and is formally defined in Table 37.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

The components of the STCompDryerType have additional subcomponents which are defined in Table 38.

DryerPower represents the measured or calculated actual electric real power consumption of a component used for a drying task. Suggested unit: kW.

Temperature represents the measured or calculated actual temperature. Suggested unit: °C.

Humidity represents the measured or calculated actual relative humidity in the process chamber as well as the surrounding atmosphere. Suggested unit: %.

7.13 STCompHeaterType ObjectType Definition

The STCompHeaterType provides relevant variables and parameters for controlling and monitoring a heater component of a cleaning and pretreatment machine and is formally defined in Table 39.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

The components of the STCompHeaterType have additional subcomponents which are defined in Table 40.

HeatingPower represents the measured or calculated actual electric real power consumption of a component used for a heating task. Suggested unit: kW.

Temperature represents the measured or calculated actual temperature. Suggested unit: °C.

EmissionControl refers to the concentration of pollutants released into a volume of air from industrial, automotive, or other sources. It plays a crucial role in minimizing environmental impact and ensuring compliance with regulatory standards for air quality. Suggested unit: ppm.

7.14 STCompPressurizedAirType ObjectType Definition

The STCompPressurizedAirType provides relevant variables and parameters for controlling and monitoring a pressurized air component of a cleaning and pretreatment machine and is formally defined in Table 41.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

The components of the STCompPressurizedAirType have additional subcomponents which are defined in Table 42.

Temperature represents the measured or calculated actual temperature. Suggested unit: °C.

PressurizedAirPressure specifies the pressure of pressurized air used to remove solvent or dirt, typically measured in bar. Exact measurement is essential to ensure proper operation of the drying or cleaning process. Suggested unit: bar.

PressurizedAirVolumeflow refers to volume of pressurized air passing through a system or component within a specific time frame, typically measured in liters per minute or cubic meters per hour. Accurate control of pressurized airflow is essential for ensuring efficient system operation and meeting process requirements. Suggested unit: m³/h.

7.15 STCompPumpType ObjectType Definition

The STCompPumpType provides relevant variables and parameters for controlling and monitoring a pump component of a cleaning and pretreatment machine and is formally defined in Table 43.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

The components of the STCompPumpType have additional subcomponents which are defined in Table 44.

Temperature represents the measured or calculated actual temperature. Suggested unit: °C.

EmissionControl refers to the concentration of pollutants released into a volume of air from industrial, automotive, or other sources. It plays a crucial role in minimizing environmental impact and ensuring compliance with regulatory standards for air quality. Suggested unit: ppm.

MediaPressure refers to the pressure exerted by a fluid or gas within a system, such as in pipes or tanks. Proper control of media pressure is crucial for ensuring system efficiency, safety, and optimal performance in industrial and operational processes. Suggested unit: bar.

MediaVolumeFlow refers to the volume of fluid or gas passing through a system or component within a specific time frame, typically measured in liters per minute or cubic meters per hour. Accurate control of media volumeflow is essential for ensuring efficient system operation and meeting process requirements. Suggested unit: l/h.

InverterFrequency represents the measured or calculated actual frequency of an electrical inverter. Suggested unit: Hz.

InverterPower represents the measured or calculated actual power of an electrical inverter. Suggested unit: kW.

PumpVibration represents the relative vibration intensity caused by errors in the pump's runout. Suggested unit: %.

7.16 STCompStirrerType ObjectType Definition

The STCompStirrerType provides relevant variables and parameters for controlling and monitoring a stirrer component of a cleaning and pretreatment machine and is formally defined in Table 45.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

The components of the STCompStirrerType have additional subcomponents which are defined in Table 46.

StirrerSpeed describes the rotational speed of a mechanical stirrer component. Suggested unit: RPM.

7.17 STCompUltrasonicEmitterType ObjectType Definition

The STCompUltrasonicEmitterType provides relevant variables and parameters for controlling and monitoring an ultrasonic emitter component of a cleaning and pretreatment machine and is formally defined in Table 47.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

The components of the STCompUltrasonicEmitterType have additional subcomponents which are defined in Table 48.

UltrasonicPower is the electrical power with which the ultrasonic transducers in an ultrasonic bath are driven - the input power. It is an important parameter for the quality of a cleaning process to ensure proper operation and quality. Suggested unit: W.

UltrasonicFrequency refers to the acoustic frequency with which ultrasonic transducers are driven in a cleaning bath. The ultrasonic frequency is an important parameter for the quality of a cleaning process to ensure proper operation and quality. Suggested unit: Hz.

7.18 STCompValveType ObjectType Definition

The STCompValveType provides relevant variables and parameters for controlling and monitoring a valve component of a cleaning and pretreatment machine and is formally defined in Table 49.

Monitoring represents a collection of variables that are not assigned to a component but to the overall system.

The components of the STCompValveType have additional subcomponents which are defined in Table 50.

ValveOpeningAngle describes the opening angle of a valve. Suggested unit: °.

ValveOpeningTime describes the opening time of a valve. Suggested unit: s.

7.19 STCompVesselType ObjectType Definition