1 Scope

This document specifies mapping specifications for the OPC UA information model of the CSP+ for machine. The specifications specified in this document are recommended to be applied for the case where application software using the CSP+ for machine is an OPC UA server. The image of the application is shown in Figure 1‑1.

Figure 1‑1 – Image of Application from CSP+ for Machine to OPC UA Server

2 Normative References

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

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

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

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

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

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

3 TERMINOLOGY, DEFINITIONS, ABBREVIATIONS

3.1 Terminology

3.1.1 CSP+ for machine

Data set to describe the following information related to the machine

Information related to the machine specifications

Machine information to be released for application software

Data to be acquired from the machine and its acquisition method

Linked information between machine information and machine data

3.1.2 CSPP section

Component of the CSP+ for machine

3.1.3 CSPP part

Component of the section

3.1.4 CSPP element

Component of the part

3.1.5 CSPP item

Detailed information related to the element. Example: Data type, engineering unit

3.2 Abbreviations and Symbols

4 CSP+ FOR MACHINE AND OPC UA

4.1 Introduction to CSP+ for Machine

4.1.1 Overview

The CSP+ for machine is a data set that visualizes machine information to simplify development by application vendors of application software that manages, monitors, and controls the machine, and settings by the machine users. The CSP+ file for machine is CSP+ for machine described in the XML format. The CSP+ for machine contains the following information related to the machine.

Information related to the machine specifications

Machine information to be released for application software (machine information)

Information related to data to be acquired from the machine and its acquisition method (machine data)

Linked information between machine information and machine data

4.1.2 Basic structure of CSP+ for machine

4.1.2.1 CSPP section

The CSP+ for machine consists of four type CSPP sections: FILE section, DEVICE section, COMM_IF section, and BLOCK section. Overview of the CSPP sections is shown in Table 4‑1.

Table 4‑1 – Overview of Sections in CSP+ for Machine

Figure 4‑1 shows the structure image of the CSP+ for machine.

Figure 4‑1 – Structure Image of CSP+ File for Machine

4.1.2.2 CSPP part

The CSPP sections consist of one or more CSPP parts. Figure 4‑2 shows the structure image in a CSPP section.

Figure 4‑2 – Image of CSPP Section Structure

Type of CSPP parts included in the CSPP sections varies depending on the CSPP sections. Type of CSPP parts included in the FILE section is shown in Table 4‑2, type of CSPP parts included in the DEVICE section is shown in Table 4‑3, type of CSPP parts included in the COMM_IF section is shown in Table 4‑4, and type of CSPP parts included in the BLOCK section is shown in Table 4‑5.

Table 4‑2 – CSPP Parts Included in FILE Section

Table 4‑3 – CSPP Parts Included in DEVICE Section

Table 4‑4 – CSPP Parts Included in COMM_IF Section

Table 4‑5 – CSPP Parts Included in BLOCK Section

There are COMM_IF_VARIABLE part and COMM_IF_CONFIGURATION part as CSPP parts managing the machine information. Machine information for realtime monitor is described in the COMM_IF_VARIABLE part and machine information for general purpose is described in the COMM_IF_CONFIGURATION part. As the information allowed for the COMM_IF_VARIABLE part is limited for realtime monitor, description is easy but the application is limited. On the other hand, there is less restrictions on the description for the COMM_IF_CONFIGURATION part where the machine information for the general purpose applications can be described. For example, a window display layout includes a monitoring window for machine information in the COMM_IF_VARIABLE part and a machine parameter read/write window for machine information in the COMM_IF_CONFIGURATION part.

4.1.3 CSPP element and CSPP item

The CSPP parts consist of one or more CSPP elements. The CSPP elements consist of one or more CSPP items. Figure 4‑3 shows the image of the CSPP part structure.

Figure 4‑3 – Image of CSPP Part Structure

CSPP elements included in the CSPP parts consist of CSPP elements specified as specifications of CSP+ for machine and CSPP elements that can be flexibly specified by the machine vendors. In contrast, all the CSPP items included in the CSPP elements are specified by specifications of the CSP+ for machine.

4.1.4 Machine information and machine data

Association information is set from one CSPP element in the COMM_IF_CONFIGURATION part managing machine information to one or more machine data in the BLOCK_MEMORY part or BLOCK_PARAM part. This means that aggregation of more than one machine data creates one machine information. The reason why this structure is required is that the information required by application software needs not only a simple measured value (current value) but also the accompanying information such as the time when the value is measured and accuracy of the value.

In contrast, setting association information from the CSPP element in the COMM_IF_VARIABLE part as the machine information to the machine data in the BLOCK_MEMORY part or BLOCK_PARAM part is not allowed. This is because the application is for realtime monitor and all the information required in the machine information can be described. Association between the machine information and machine data is illustrated in Figure 4‑4.

Figure 4‑4 – Structure Image of CSP+ for Machine
(Association between Machine Information and Machine Data)

4.2 Introduction to OPC Unified Architecture

4.2.1 General

The main use case for OPC classic specifications is the online data exchange between devices and HMI or SCADA systems using Data Access functionality. In this use case the device data is provided by an OPC server and is consumed by an OPC client integrated into the HMI or SCADA system. OPC DA provides functionality to browse through a hierarchical namespaces containing data items and to read, write and to monitor these items for data changes. The classic OPC standards are based on Microsoft COM/DCOM technology for the communication between software components from different vendors. Therefore classic OPC server and clients are restricted to Windows PC based automation systems.

OPC UA incorporates all features of classic OPC standards like OPC DA, A&E and HDA but defines platform independent and secure communication mechanisms and generic, extensible and object-oriented modelling capabilities for the information a system wants to expose. OPC UA is directly integrated into devices and is used for configuration, diagnostic and maintenance use cases in addition to online data exchange. OPC UA is an integrated communication interface used from sensor level devices up to enterprise applications.

OPC 10000-6 defines different mechanisms optimized for different use cases. The first version of OPC UA is defining an optimized binary TCP protocol for high performance intranet communication as well as a mapping to accepted internet standards like Web Services. The abstract communication model does not depend on a specific protocol mapping and allows adding new protocols in the future. Features like security and reliability are directly built into the transport mechanisms. Based on the platform independence of the protocols, OPC UA servers and clients can be directly integrated into devices and controllers.

The OPC UA Information Model provides a standard way for Servers to expose Objects to Clients. Objects in OPC UA terms are composed of other Objects, Variables and Methods. OPC UA also allows relationships to other Objects to be expressed.

The set of Objects and related information that an OPC UA Server makes available to Clients is referred to as its AddressSpace. The elements of the OPC UA Object Model are represented in the AddressSpace as a set of Nodes described by Attributes and interconnected by References. OPC UA defines eight classes of Nodes to represent AddressSpace components. The classes are Object, Variable, Method, ObjectType, DataType, ReferenceType and View. Each NodeClass has a defined set of Attributes.

This specification defines Nodes of the OPC UA NodeClasses Object, Method, Variable, ObjectType and DataType.

Objects are used to represent components of a system. An Object is associated to a corresponding ObjectType that provides definitions for that Object.

Methods are used to represent commands or services of a system.

Variables are used to represent values. Two categories of Variables are defined, Properties and DataVariables.

Properties are Server-defined characteristics of Objects, DataVariables and other Nodes. Properties are not allowed to have Properties defined for them.

DataVariables represent the data contents of an Object.

4.2.2 Graphical notation

OPC UA defines a graphical notation for an OPC UA AddressSpace. It defines graphical symbols for all NodeClasses and how different types of References between Nodes can be visualized. Figure shows the symbols for the six NodeClasses used in this specification. NodeClasses representing types always have a shadow.

Figure 4‑5 – OPC UA Graphical Notation for NodeClasses

Figure shows the symbols for the ReferenceTypes used in this specification. The Reference symbol is normally pointing from the source Node to the target Node. The only exception is the HasSubType Reference. The most important References like HasComponent, HasProperty, HasTypeDefinition and HasSubType have special symbols avoiding the name of the Reference. For other ReferenceTypes or derived ReferenceTypes the name of the ReferenceType is used together with the symbol.

Figure 4‑6 – OPC UA Graphical Notation for References

Figure shows a typical example for the use of the graphical notation. Object_A and Object_B are instances of the ObjectType_Y indicated by the HasTypeDefinition References. The ObjectType_Y is derived from ObjectType_X indicated by the HasSubType Reference. The Object_A has the components Variable_1, Variable_2 and Method_1.

To describe the components of an Object on the ObjectType the same NodeClasses and References are used on the Object and on the ObjectType like for ObjectType_Y in the example. The instance Nodes used to describe an ObjectType are instance declaration Nodes.

To provide more detailed information for a Node, a subset or all Attributes and their values can be added to a graphical symbol.

Figure 4‑7 – OPC UA Graphical Notation Example

4.3 Use Case

This section describes an example of the OPC UA server according to Figure 4‑8, as an application example of the application software using the CSP+ for machine.

This example shows that the OPC UA server itself as the application software using the CSP+ for machine does not provide the function for the machine users and other application software such as SCADA and MES provides the monitoring and management functions for the machine users. When the application software using the CSP+ for machine is an OPC UA server, the address space that the OPC UA server discloses to the OPC UA clients is created from the CSP+ for machine based on the specifications specified in this document.

Figure 4‑8 – Operation Image of OPC UA Server Supporting CSP+ for Machine

Since this system configuration is achievable, vendors of application software such as SCADA and MES have the following advantage.

Since not a machine's own communications protocol but the standard OPC UA can be used for communications with machines, the development volume for the communication function can be reduced.

Vendors of OPC UA server application software have the following advantage.

Supporting the CSP+ for machine allows handling many machines supporting the CSP+ for machine as communication partners.

Machine vendors have the following advantages.

Since there is no need to request an application vendor to support the machine's own protocol when requesting the application vendor to develop application software dedicated to the machine, the development cost can be reduced.

Since information to be disclosed to the application software such as process statuses and operation histories of the machine can be limited to the range described in the CSP+ for machine, information related to know-how of the machine can be set to confidential.

5 MACHINE MODEL

5.1 Overview

This chapter specifies the OPC UA information model for machines described by the CSP+ for machine.

5.1.1 Basic policy

This section defines CsppMachineType ObjectType corresponding to all the machines described by the CSP+ for machine, and further defines dedicated ObjectType corresponding to separate machines described by each CSP+ for machine (hereinafter referred to as "CSP+ machine ObjectType"). The CsppMachineType ObjectType should be abstract ObjectType (IsAbstract attribute is "true") inheriting DeviceType ObjectType specified by the OPC 10000-100. The CSP+ machine ObjectType should be non-abstract ObjectType (IsAbstract attribute is "false") inheriting CsppMachineType ObjectType. While inheriting, Node definition corresponding to the information described in the CSP+ for machine is added.

The machine information described by the CSP+ for machine is described as an Object of the CSP+ machine ObjectType.

5.1.2 Model positioning

Positioning of OPC UA information model specified in this document is shown in Figure 6‑1. In addition to the CsppMachineType ObjectType corresponding to the machine, CsppAnalogItemType as VariableType for the CsppMachineType ObjectType is defined.

Figure 6‑1 – Positioning of OPC UA Information Model Related to Machine

5.2 Type Definition

5.2.1 CsppMachineType ObjectType

This section describes the CsppMachineType ObjectType definition and Node definition referred to from the CsppMachineType ObjectType. Figure 6‑2 shows a full picture of the CsppMachineType ObjectType.

Figure 6‑2 – Full Picture of CsppMachineType ObjectType

5.2.1.1 CsppMachineType ObjectType

Definition of the CsppMachineType ObjectType is shown in Table 6‑1.

Table 6‑1 – Definition of CsppMachineType ObjectType

ModellingRule of the ParameterSet Object is Optional in the source of the inheritance but that of the CsppMachineType ObjectType should be Mandatory. The definition of the ParameterSet Object itself is overridden. For details, refer to 5.2.1.2.

Objects shown by <CommIfSection> correspond to COMM_IF section of the CSP+ for machine and take a role to group the machine information held by the machine.

5.2.1.2 ParameterSet Object

The ParameterSet Object takes a role to organize machine information held by the machine Object. Table 6‑2 shows the definition of the ParameterSet Object.

Table 6‑2 – Definition for ParameterSet Object

DataVariables shown by <VariableName> correspond to the CSPP elements in the COMM_IF_VARIABLE part of the CSP+ for machine. The VariableType is DataItemType VariableType specified by the OPC 10000-8 or its derivative type.

DataVariables shown by <ConfigurationName> correspond to the CSPP elements in the COMM_IF_CONFIGURATION part of the CSP+ for machine. The VariableType is DataItemType VariableType specified by the OPC 10000-8 or its derivative type.

5.2.1.3 Object corresponding to COMM_IF section

Object corresponding to the COMM_IF section takes a role to make machine Object group the machine information per CSPP section. In addition, it takes a role to organize the COMM_IF_VARIABLE part and COMM_IF_CONFIGURATION part in the COMM_IF section. Table 6‑3 shows the definition of the Object.

Table 6‑3 – Definition of Object Corresponding to COMM_IF Section

Objects shown by <CommIfVariablePart> correspond to COMM_IF_VARIABLE part of the CSP+ for machine and take a role to group machine information for realtime monitor held by the machine.

Objects shown by <CommIfConfigurationPart> correspond to COMM_IF_CONFIGURATION part of the CSP+ for machine and take a role to group machine information for general purpose held by the machine.

5.2.1.4 Object corresponding to COMM_IF VARIABLE part

Object corresponding to the COMM_IF_VARIABLE part takes a role to group the machine information for realtime monitor held by the machine Object per part. Table 6‑4 shows the definition of the Object.

Table 6‑4 – Definition of Object Corresponding to COMM_IF VARIABLE Part

5.2.1.5 Object corresponding to COMM_IF_CONFIGURATION part

Object corresponding to the COMM_IF_CONFIGURATION part takes a role to group the machine information for general purpose held by the machine Object per part. Table 6‑5 shows the definition of the Object.

Table 6‑5 – Definition of Object Corresponding to COMM_IF_CONFIGURATION Part

5.2.2 CsppAnalogItemType VariableType

This section defines the CsppAnalogItemType VariableType to describe machine information accompanying measurement period of the machine information described by the CSP+ for machine. Table 6‑6 shows the definition of the VariableType.

Table 6‑6 – Definition of CsppAnalogItemType VariableType

The Duration Property shows the duration in which applicable variable is calculated or measured in millisecond unit.

5.2.3 CSP+ machine ObjectType

Definition of the CSP+ machine ObjectType is shown in Table 6‑7.

Table 6‑7 – Definition of CSP+ Machine ObjectType

Definition of a Node referred to from the CSP+ machine ObjectType is determined by the description of the CSP+ for machine corresponding to applicable CSP+ machine ObjectType. Rules for the mapping to determine the description of the CSP+ for machine are shown in Chapter 7.

5.3 Machine Object and Entry Point

The machine Object indicating one machine should be an instantiated CSP+ machine ObjectType corresponding to the applicable machine and referred to by using HasComponent Reference from the DeviceSet entry point specified by the OPC 10000-100. Figure 6‑3 illustrates the relationship among the entry point, machine Objects, and CSP+ machine ObjectType. Figure 6‑3 illustrates three machines, two machine Objects for the machine A, and one machine Object for the machine B.

Figure 6‑3 – Image of Relationship among Entry Point, Machine Object,
and CSP+ Machine ObjectType

6 MAPPING

6.1 Overview

This chapter specifies rules to create CSP+ machine ObjectType from the CsppMachineType ObjectType based on the information described in the CSP+ for machine.

Inheriting rules not specified in this document for mandatory Attributes, Properties and DataVariables of the CsppMachineType ObjectType should depend on the implementation of application creating CSP+ machine ObjectType (OPC UA Server). The instantiation of machine Object from the CSP+ machine ObjectType should also depend on the implementation of application (OPC UA Server).

6.2 FILE Section

No rules are specified to use the information described in the FILE section to create CSP+ machine ObjectType. However, DATA item value of Language element as one of COMMON information may be indirectly used to show locale of a string. For details, refer to specifications of each rule.

6.3 DEVICE Section

6.3.1 Header information

Label names described in the DEVICE section header are used as part of BrowseName Attribute values of the CSP+ machine ObjectType. Specifically, a text "CsppDeviceType" connected after an Attribute value is handled as the BrowseName Attribute value. For example, when the label name is "ABC", its BrowseName Attribute value becomes "ABCCsppDeviceType".

No rules are specified to use any information other than the above to create CSP+ machine ObjectType.

6.3.2 DEVICE_INFO part

6.3.2.1 Header information

No rules are specified to use the information described in the DEVICE_INFO part header to create CSP+ machine ObjectType.

6.3.2.2 COMMON information CSPP element

Part of COMMON information CSPP elements in the DEVICE_INFO part is mapped to Attributes and Properties of the CSP+ machine ObjectType.

Table 7‑1 shows the mapping specifications.

Table 7‑1 – Mapping Specifications for COMMON Information CSPP Elements of DEVICE_INFO Part

*1: One of bit string type, signed integral data type, unsigned integral data type, or STRING (x)

6.3.2.3 CSPP element other than COMMON information

No rules are specified to use any CSPP elements other than COMMON information to create CSP+ machine ObjectType.

6.3.3 DEVICE_IF part

No rules are specified to use the information described in the DEVICE_IF part to create CSP+ machine ObjectType.

6.4 COMM_IF Section and BLOCK Section

6.4.1 Basic policy

Basic policy to apply information described in the COMM_IF section and BLOCK section for creating CSP+ machine ObjectType is as follows.

CSPP elements specified in the COMM_IF_VARIABLE part and COMM_IF_CONFIGURATION part are mapped to each DataVariable referred to from ParameterSet Object of CSP+ machine ObjectType by using HasComponent Reference.

The DataVariables above are grouped both per CSPP section and per CSPP part. FunctionalGroupType Objects are created only for the number of CSPP sections and CSPP parts for grouping purpose, the Objects corresponding to the CSPP sections are referred to from the CSP+ machine ObjectType by using HasComponent Reference, and the Objects corresponding to the CSPP parts are referred to from the Objects corresponding to the sections using the HasComponent Reference.

Attribute and Property information held by the DataVariables (e.g. engineering unit, minimum collection cycle) are configured based on the CSPP elements in the BLOCK_MEMORY part and BLOCK_PARAM part referred to from the element corresponding to the DataVariables, and CSPP element or CSPP part to which the CSPP element belongs.

The image of the basic policy is shown in Figure 7‑1.

Figure 7‑1 – Image of Relationship between COMM_IF Section, BLOCK Section,
and CSP+ Machine ObjectType

6.4.2 COMM_IF section header information

From the information described in the COMM_IF section header, LABEL name is mapped to the BrowseName Attribute of the FunctionalGroupType Object (refer to 5.2.1.3) and LABEL2 name is mapped to the DisplayName Attribute of the same Object above.

6.4.3 BLOCK section header information

No rules are specified to use the information described in the BLOCK section header to create CSP+ machine ObjectType.

6.4.4 COMM_IF_INFO part

No rules are specified to use the information described in the COMM_IF_INFO part to create CSP+ machine ObjectType.

6.4.5 BLOCK_INFO part

No rules are specified to use the information described in the BLOCK_INFO part to create CSP+ machine ObjectType.

6.4.6 COMM_IF_VARIABLE part, COMM_IF_CONFIGURATION part

6.4.6.1 Header information

From the information described in the COMM_IF_VARIABLE part and COMM_IF_CONFIGURATION part headers, LABEL name is mapped to the BrowseName Attribute of the FunctionalGroupType Object (refer to 5.2.1.4 and 5.2.1.5) and LABEL2 name is mapped to the DisplayName Attribute of the same Object above.

No rules are specified to use any information other than the above to create CSP+ machine ObjectType.

6.4.6.2 CSPP element

CSPP elements specified in the COMM_IF_VARIABLE part and COMM_IF_CONFIGURATION part are mapped to each DataVariable referred to from ParameterSet Object of CSP+ machine ObjectType by using HasComponent Reference. The VariableType of each DataVariable is determined based on the following rules depending on the item values of the BLOCK_MEMORY part and BLOCK_PARAM part CSPP elements referred to from item values of each CSPP element and the CSPP elements.

CSPP elements that specify ENUM to the RANGE item are mapped to the DataVariables in one of VariableTypes: TwoStateDiscreteType, MultiStateDiscreteType, and MultiStateValueDiscreteType.

Data type is boolean type: TwoStateDiscreteType VariableType

CODE item values of entire elements are assigned in a serial number starting from 0 in ENUM part: MultiStateDiscreteType VariableType

Any case other than the above: MultiStateValueDiscreteType VariableType

All the CSPP elements other than the above referring to BLOCK_PARAM part including P_Period element are mapped to the DataVariable of the CsppAnalogItemType VariableType.

All the CSPP elements other than the above in data type of bit string type, signed integral data type, unsigned integral data type, BCD integral data type, or real data type, are mapped to the DataVariable of the AnalogItemType VariableType.

All the CSPP elements other than the above are mapped to the DataVariable of the DataItemType VariableType.

Part of items of each CSPP element is mapped to Attributes and Properties of the DataVariables. Table 7‑2 shows the mapping specifications. Instead of description omission in the COMM_IF_VARIABLE part and COMM_IF_CONFIGURATION part, the mapping specifications shown in the Table 7‑2 are also applied to the items described in the P_Value element of the BLOCK_MEMORY part.

Table 7‑2 – Mapping Specifications for COMM_IF_VARIABLE Part
and COMM_IF_CONFIGURATION Part Elements

*1: For the COMM_IF_CONFIGURATION part CSPP element only

*2: For the COMM_IF_VARIABLE part CSPP element only

6.4.7 BLOCK_MEMORY part, BLOCK_PARAM part

6.4.7.1 Header information

No rules are specified to use the information described in the BLOCK_MEMORY part and BLOCK_PARAM part headers to create CSP+ machine ObjectType.

6.4.7.2 Preset label CSPP element

Elements having preset labels in the BLOCK_MEMORY part and BLOCK_PARAM part are mapped not to CSP+ machine ObjectType but to a machine Object with the CSP+ machine ObjectType instantiated.

Some of elements having preset labels in the BLOCK_MEMORY part and BLOCK_PARAM part are mapped to Attributes and Properties of DataVariables as mapping destination for the elements specified in the COMM_IF_CONFIGURATION as its reference source, and others are mapped to return values for the Services (Read, Publish, Republish) to be executed for the DataVariables. Table 7‑3 shows the mapping specifications.

Table 7‑3 – Mapping Specifications for BLOCK_MEMORY Part and BLOCK_PARAM Part CSPP Elements

*1: For a Read Service, the results[] value corresponds to the DataValue DataType. For a Publish or Republish Service, the Value element of the notificationData[] element in the notificationMessage value corresponds to the DataValue DataType.

6.4.7.3 CSPP element other than preset label

No rules are specified to use the information for the elements other than the preset label in the BLOCK_MEMORY part and BLOCK_PARAM part to create CSP+ machine ObjectType.

6.4.8 ENUM part

6.4.8.1 Header information

No rules are specified to use the information described in the ENUM part header to create CSP+ machine ObjectType.

6.4.8.2 CSPP element

6.4.8.2.1 TwoStateDiscreteType VariableType

When the data type of reference source CSPP element in the ENUM part is boolean type, map the reference source CSPP element to the DataVariable of the TwoStateDiscreteType VariableType. Map two CSPP elements of the ENUM part to Properties of the DataVariable based on the following rules.

Assign the CSPP element with the CODE item value 0 to the FalseState Property and map the CSPP element with CODE item value 1 to the TrueState Property.

When the LABEL2 item of the CSPP element is specified, set the item value to the text element of the Value Attribute for corresponding Property. Set the DATA item value of the Language element in the FILE_INFO part to the Locale element.

When the LABEL2 item of the CSPP element is not specified, set the LABEL item value to the text element of the Value Attribute. Set "en-US" to the Locale element.

6.4.8.2.2 MultiStateDiscreteType VariableType

When CODE item values of entire CSPP elements of ENUM part are assigned in a serial number starting from 0, map the reference source CSPP element to the DataVariable of the MultiStateDiscreteType VariableType. Map the CSPP elements of the ENUM part to Properties of the DataVariable based on the following rules.

Sort the CSPP elements in the ascending order of the CODE item value to be assigned to each element of the EnumStrings Property (Note: the Property above is array type) in a sequential order.

When the LABEL2 item of the CSPP element is specified, set the item value to the text element of the Value Attribute for the corresponding element of the EnumStrings Property. Set the DATA item value of the Language element in the FILE_INFO part to the Locale element.

When the LABEL2 item of the CSPP element is not specified, set the LABEL item value to the text element. Set "en-US" to the Locale element.

6.4.8.2.3 MultiStateValueDiscreteType VariableType

When CODE item values of entire CSPP elements of ENUM part are not assigned in a serial number starting from 0, map the reference source CSPP element to the DataVariable of the MultiStateValueDiscreteType VariableType. Map the CSPP elements of the ENUM part to the DataVariable Property based on the following rules.

Assign the elements of the EnumValues Property (Note: the Property above is array type) in the ascending order described in the ENUM part.

Set the CODE item value of the CSPP element to the Value element of the Value Attribute for the corresponding element of the EnumValues Property.

When the LABEL2 item of the CSPP element is specified, set the item value to the text element of the Display element in the Value Attribute for the corresponding element of the EnumValues Property. Set the DATA item value of the Language element in the FILE_INFO part to the locale element for the Display element.

When the LABEL2 item of the CSPP element is not specified, set the LABEL item value to the text element. Set "en-US" to the Locale element.

7 DATA TYPE MAPPING

Mapping rules from data type in CSP+ for machine to the OPC UA DataType are shown in Table 8‑1.

Table 8‑1 – Mapping Rules between Data Type in CSP+ for Machine and OPC UA DataType

8 PROFILE AND NAMESPACE

8.1 Namespace Metadata

Table 9‑1 shows the namespace metadata for this specifications. This Object is used to provide the version information and static Nodes of the namespace. For the static Nodes, all Attributes of all servers are the same, including value Attributes. For details, refer to OPC 10000-5.

Information on the namespace metadata is provided as Object of type NamespaceMetadataType. This Object is a component of Namespaces Object which is a part of the Server Object. The NamespaceMetadataType ObjectType and its Property are defined in OPC 10000-5.

The version information is also provided as a part of ModelTableEntry in the UANodeSet XML file. The UANodeset XML schema is defined in OPC 10000-6.

Table 9‑1 – NamespaceMetadata Object for this Specification

8.2 OPC UA Conformance Unit and Profile

This section defines the profiles and conformance units of the OPC UA information model which are related to CSP+ for machine. Profiles are defined as a name of grouped conformance units.

The Profile which is to be a Facet is expected to be combined with other Profiles to define full functions of the OPC UA Server or Client.

Table 9‑2 shows the Facet which can be used by a Server where companion specifications of the Information Model of CSP+ for machine are implemented.

Table 9‑2 – CSP+ for machine Server Facet Definition

Table 9‑3 shows the Facet which can be used by a Client where companion specifications of the Information Model of CSP+ for machine are implemented.

Table 9‑3 – CSP+ for machine Client Facet Definition

8.3 Handling of the OPC UA Namespace

Namespaces are used to generate identifiers which are unique among various naming authorities. NodeIds and BrowseNames of Attributes are identifiers. Nodes in the UA Address Space are definitely identified by the NodeIds. In contrast to the NodeIds, BrowseNames cannot be used to definitely identify Nodes. Different Nodes may share a same BrowseName. BrowseNames are used to create a browse path between two Nodes or define standard Properties.

A server may select the use of a same namespace for NodeIds and BrowseNames. However, for example, when a local server grants standard Properties, their BrowseNames must have a namespace of the standardizing body even though the namespace of the NodeIds reflect other things. All of NodeId for Nodes which are not defined in this specifications must not use the standard namespace.

Table 9‑4 lists mandatory/optional namespaces used by the server.

Table 9‑4 – Namespace used in CSPPlusForMachine Server

Table 9-5 provides a list of namespaces and their index used for BrowseNames in this specification. The default namespace of this specification is not listed since all BrowseNames without prefix use this default namespace.

9 Untitled

10 APPENDIX A: Namespace and Mapping

10.1 A.1 Namespace and Identifiers of the Information Model of CSP+ for Machine

This appendix defines numeric identifiers for all numeric type NodeId that are defined in this specifications. The identifiers are specified in the following syntax in CSV files.

< SymbolName >, < Identifier >, < NodeClass >

'SymbolName' described above refers to BrowseName of a Type Node or BrowsePath of an Instance Node when the identifier of the NodeId is a numerical value in the Instance Node in this specifications.

Browse paths of instance Nodes are described by connecting the BrowseName of the instance or type which holds it with the BrowseName of the target Instance Node. The underscore ("_") is used as a delimiter for BrowseNames of paths.

The NamespaceUri for all NodeIds is defined in the following.

http://www.opcfoundation.org/UA/CSPPlusForMachine/

The CSV file for the specifications of this version is available from the following.

http://www.opcfoundation.org/UA/schemas/CSPPlusForMachine/1.0/NodeIds.csv

The latest NodeIds are available from the following.

http://www.opcfoundation.org/UA/schemas/CSPPlusForMachine/NodeIds.csv

The electronic version of the full information model defined in this specifications is also available. It conforms to the schema of the information model in the XML format which is defined in OPC 10000-6. The information model schema for this version is available from the following.

http://www.opcfoundation.org/UA/schemas/CSPPlusForMachine/1.0/Opc.Ua.CSPPlusForMachine.Nodeset2.xml

The latest information model schema is available from the following.

http://www.opcfoundation.org/UA/schemas/CSPPlusForMachine/Opc.Ua.CSPPlusForMachine.Nodeset2.xml

10.2 A.2 Profile URI in the Information Model of CSP+ for Machine

Table A-1 defines the profile URI in the information model of CSP+ for machine.

RELATED SPECIFICATIONS

None.

Agreement of Use

COPYRIGHT RESTRICTIONS

This specification is provided "as is" by the OPC Foundation and the international open network organization CC-Link Partner Association (hereinafter referred to as "CLPA").

This specification may be distributed through computer systems such as e-mail, and printed or copied as long as the content remains unchanged and the document is not modified.

OPC Foundation and CLPA do not guarantee usability for any purpose and shall not be made liable for any case using the content of this specification.

The user of this specification agrees to indemnify OPC Foundation and CLPA and their officers, directors and agents harmless from all demands, claims, actions, losses, damages (including damages from personal injuries), costs and expenses (including attorneys' fees) which are in any way related to activities associated with its use of content from this specification.

This specification shall not be used in conjunction with company advertising, shall not be sold or licensed to any party.

The intellectual property and copyright is solely owned by the OPC Foundation and CLPA.

PATENTS

The attention of adopters is directed to the possibility that compliance with or adoption of OPC or CLPA specifications may require use of an invention covered by patent rights. OPC Foundation or CLPA shall not be responsible for identifying patents for which a license may be required by any OPC or CLPA specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OPC or CLPA specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents.

WARRANTY AND LIABILITY DISCLAIMERS

WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE OPC FOUDATION NOR CLPA MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OPC FOUNDATION NOR CLPA BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The entire risk as to the quality and performance of software developed using this specification is borne by you.

RESTRICTED RIGHTS LEGEND

This Specification is provided with Restricted Rights. Use, duplication or disclosure by the U.S. government is subject to restrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202 -3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer Software clause at DFARs 252.227 -7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as applicable. Contractor / manufacturer are the OPC Foundation, 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260-1830

COMPLIANCE

The combination of CLPA and OPC Foundation shall at all times be the sole entities that may authorize developers, suppliers and sellers of hardware and software to use certification marks, trademarks or other special designations to indicate compliance with these materials as specified within this document . Products developed using this specification may claim compliance or conformance with this specification if and only if the software satisfactorily meets the certification requirements set by CLPA or the OPC Foundation. Products that do not meet these requirements may claim only that the product was based on this specification and must not claim compliance or conformance with this specification.

TRADEMARKS

Most computer and software brand names have trademarks or registered trademarks. The individual trademarks have not been listed here.

GENERAL PROVISIONS

Should any provision of this Agreement be held to be void, invalid, unenforceable or illegal by a court, the validity and enforceability of the other provisions shall not be affected thereby.

This Agreement shall be governed by and construed under the laws of Japan.

This Agreement embodies the entire understanding between the parties with respect to, and supersedes any prior understanding or agreement (oral or written) relating to, this specification.

This document describes the OPC UA information model in "Control & Communication System Profile Specification (for Machine)".

The Control & Communication System Profile for machine (hereinafter referred to as "CSP+ for machine") is a data set that visualizes machine information to simplify development by application vendors of application software that manages, monitors, and controls the machine, and settings by the machine users. The CSP+ for machine contains the following information related to the machine described.

Information related to the machine specifications

Machine information to be released for application software (machine information)

Information related to data to be acquired from the machine and its acquisition method (machine data)

Linked information between machine information and machine data

The CSP+ for machine is generally handled as CSP+ file for machine described in the XML format.

This document specifies the mapping of information written in the CSP+ for machine to the OPC UA information model. The specifications specified here are applied for the case where application software using the CSP+ for machine is an OPC UA server.