ISO 20242-4:2011

Industrial automation systems and integration — Service interface for testing applications — Part 4: Device capability profile template

ISO 20242-4:2011 defines the formatting, syntax and semantic rules for describing device and coordinator capabilities with XML schema, and the configuration of devices with XML.

Systèmes d'automatisation industrielle et intégration — Interface de service pour contrôler les applications — Partie 4: Modèle de profil de capacité de dispositif

General Information

• Status: Published
• Publication Date: 05-Dec-2011
• ICS: 25.040.40 - Industrial process measurement and control
• Technical Committee: ISO/TC 184/SC 5 - Interoperability, integration, and architectures for enterprise systems and automation applications
• Drafting Committee: ISO/TC 184/SC 5/WG 6 - Application service interface
• Current Stage: 9060 - Close of review
• Start Date: 02-Sep-2027

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 20242-4
First edition
2011-12-15

Industrial automation systems and
integration — Service interface for testing
applications —
Part 4:
Device capability profile template
Systèmes d'automatisation industrielle et intégration — Interface de
service pour contrôler les applications —
Partie 4: Modèle de profil de capacité de dispositif



Reference number
ISO 20242-4:2011(E)
©
ISO 2011

---------------------- Page: 1 ----------------------
ISO 20242-4:2011(E)

COPYRIGHT PROTECTED DOCUMENT


©  ISO 2011
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO 2011 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 20242-4:2011(E)
Contents Page
Foreword . iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Device capability profile framework . 3
5.1 General . 3
5.2 Creation procedure of DCD, CCD and PID . 4
6 Generic device capability profile template . 6
6.1 General . 6
6.2 Generic DCPT model . 6
6.3 Generic DCPT XML schema . 7
7 Common rules for DCPT . 10
7.1 General . 10
7.2 DCPT header . 11
7.3 Extension of profile template . 12
7.4 Assignment of textual information . 13
7.5 Creating PID . 14
8 Multilingual text elements. 14
Annex A (informative) ASAM GDI device capability profile template . 16
Annex B (informative) Device capability profile templates for manufacturing applications . 35
Annex C (informative) Device capability profile templates for ORiN robot applications . 55
Bibliography . 75


© ISO 2011 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 20242-4:2011(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 20242-4 was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 5, Interoperability, integration, and architectures for enterprise systems and automation
applications.
ISO 20242 consists of the following parts, under the general title Industrial automation systems and
integration — Service interface for testing applications:
 Part 1: Overview
 Part 2: Resource management service interface
 Part 3: Virtual device service interface
 Part 4: Device capability profile template
The following parts are under preparation:
 Part 5: Application program service interface
 Part 6: Conformance test methods, criteria and reports
iv © ISO 2011 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 20242-4:2011(E)
Introduction
The motivation for ISO 20242 stems from the desire of international automotive industries and their suppliers
to facilitate the integration of automation and measurement devices, and other peripheral components for this
purpose, into computer-based applications. ISO 20242 defines rules for the construction of device drivers and
their behaviour in the context of an automation and/or measurement application.
The main goal of ISO 20242 is to provide users with:
 independence from the computer operating system;
 independence from the device connection technology (device interface/network);
 independence from device suppliers;
 the ability to ensure compatibility between device drivers and connected devices, and their behaviour in
the context of a given computer platform;
 independence from the technological device development in the future.
ISO 20242 does not necessitate the development of new device families or the use of special interface
technologies (networks). It encapsulates a device and its communication interface to make it compatible with
other devices of that kind for a given application.
© ISO 2011 – All rights reserved v

---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 20242-4:2011(E)

Industrial automation systems and integration — Service
interface for testing applications —
Part 4:
Device capability profile template
1 Scope
This part of ISO 20242 defines the formatting, syntax and semantic rules for describing
 device and coordinator capabilities with XML schema, and
 the configuration of devices with XML.
NOTE This part of ISO 20242 does not address the coordinator configuration, which will be addressed elsewhere in
the ISO 20242 series.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 15745-1, Industrial automation systems and integration — Open systems application integration
framework — Part 1: Generic reference description
ISO 20242-1, Industrial automation systems and integration — Service interface for testing applications —
Part 1: Overview
ISO 20242-3, Industrial automation systems and integration — Service interface for testing applications —
Part 3: Virtual device service interface
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 20242-1, ISO 20242-3 and the
following apply.
3.1
communication object
existing object which may be accessed with a communication function to read or write a value
[ISO 20242-1:2005, definition 2.3]
© ISO 2011 – All rights reserved 1

---------------------- Page: 6 ----------------------
ISO 20242-4:2011(E)
3.2
coordinator
program with a specified interface to handle the access of an application program to one or more device
drivers and to manage real-time application aspects, synchronization and events
[ISO 20242-1:2005, definition 2.4]
3.3
coordinator capability description
text file containing information about the capabilities of coordinators in a defined format (i.e. structure, syntax)
3.4
device capability description
text file containing information about the capabilities of virtual devices in a defined format (i.e. structure,
syntax)
[ISO 20242-1:2005, definition 2.5]
3.5
device driver
software module providing an ISO 20242-specified interface with service functions to call a platform adapter to
access physical devices
[ISO 20242-2:2010, definition 3.1]
3.6
function object
instance describing one capability of a virtual device
[ISO 20242-3:2011, definition 3.4]
3.7
operation
instance describing one complete procedure
[ISO 20242-3:2011, definition 3.5]
3.8
parameterization instance description
information about the configuration of a coordinator and of virtual devices
3.9
virtual device
representation of one or more physical devices and/or stand-alone software modules that provide an
unambiguous view of the resources of a communication interface
[ISO 20242-3:2011, definition 3.7]
4 Abbreviated terms
CCD Coordinator Capability Description
DCD Device Capability Description
DCPT Device Capability Profile Template
PID Parameterization Instance Description
2 © ISO 2011 – All rights reserved

---------------------- Page: 7 ----------------------
ISO 20242-4:2011(E)
VD Virtual Device
VDSI Virtual Device Service Interface
XML eXtensible Markup Language
5 Device capability profile framework
5.1 General
For the design of device capability profile templates (DCPTs), device capability descriptions (DCDs) and
coordinator capability descriptions (CCDs), a device capability profile framework as shown in Figure 1 shall be
used. The generic DCPT shall use the generic information exchange profile template of ISO 15745-1 as a
skeleton and shall be constructed in XML schema. The technology-specific DCPT describes technology-
specific capabilities and shall extend the generic DCPT in XML schema. A DCD describes capabilities of
virtual devices in a device driver and shall extend a technology-specific DCPT in XML schema. A CCD
describes capabilities of a coordinator and shall extend a technology-specific DCPT in XML schema. A CCD
imports DCDs for device drivers and describes capabilities of a system. A parameterization instance
description (PID) describes configurations of a coordinator and device drivers. A PID shall be constructed by
instantiations of one CCD and one to many DCDs. The PID is a realization of the information exchange profile
in ISO 15745-1 and can be used together with other profiles of ISO 15745.
<>
ISO15745-1::

GenericDCPT
GenericInformationExchangeProfileTemplate
<>
TechnologySpecificDCPT TechnologySpecificCapability
<>
<> <>
<>
CoordinatorCapability CCD DCD DeviceCapability
<> <>
:InformationExchangeProfile :PID
<>
(from ISO15745-1)

Figure 1 — Class diagram of device capability profile framework
Figure 2 shows the class diagram of CCD and DCD in the framework. The generic DCPT specifies the
aggregate of the generic CCD and generic DCD. The generic CCD describes generic capabilities of a
coordinator. The generic DCD describes generic capabilities of virtual devices. The technology-specific CCD
in a technology-specific DCPT shall inherit the generic CCD and describes technology-specific capabilities of
a coordinator. The technology-specific DCD shall inherit the generic DCD and describes technology-specific
capabilities of virtual devices.
© ISO 2011 – All rights reserved 3

---------------------- Page: 8 ----------------------
ISO 20242-4:2011(E)

GenericDCPT TechnologySpecificDCPT CCD PID
<>
GenericCCD TechnologySpecificCCD (CoordinatorSpecificCCD) (CCD instance)
0.*
DCD
1.* <>
GenericDCD TechnologySpecificDCD (DeviceSpecificCCD) (DCD instance)

Figure 2 — Class diagram of CCD and DCD
The coordinator-specific CCD shall inherit the technology-specific CCD and describes coordinator-specific
capabilities. The name of a coordinator-specific CCD can be described by the coordinator-specific name. The
device-specific DCD shall inherit the technology-specific DCD and shows device-specific capabilities. The
name of a device-specific DCD can be described by the device-driver-specific name. Between the generic
CCD and the generic DCD, there shall be an aggregation relation as shown in Figure 2. A generic CCD may
contain one to many generic DCDs. Different generic CCDs may use the same generic DCD. Generic DCDs
may exist without a generic CCD. The coordinator-specific CCD and the device-specific DCD have the
aggregation relation from inheritance. A CCD can import the DCDs of device drivers. The CCD instance in a
PID shall be an XML instance of the coordinator-specific CCD XML schema. A DCD instance in a PID shall be
an XML instance of a device-specific DCD XML schema. The XML tag name of a CCD instance shall be the
name of the coordinator-specific CCD. The XML tag name of a DCD instance shall be the name of the device-
specific DCD.
5.2 Creation procedure of DCD, CCD and PID
5.2.1 General
Figure 3 shows the creation procedure of DCD and CCD. Clause 6 defines the generic DCPT in XML schema.
The technology of each service interface defines technology-specific capabilities as a technology-specific
DCPT.
NOTE Technology-specific DCPTs for ASAM GDI, MICX and ORiN are described in Annexes A, B and C.
The vendor of a device, equipment or software module shall extend the technology-specific DCD of the
technology-specific DCPT with the capabilities of the device or equipment. The resulting DCD XML schema
shall be provided together with a device driver. The vendor of a coordinator shall extend the
technology-specific CCD of the technology-specific DCPT with the capabilities of the coordinator. The
resulting CCD XML schema shall be provided with the coordinator. A configuration tool can import the CCD
and the required DCDs to create the PID XML instance with the configuration data for the required application.
The PID shall contain all required instances with names and values. The coordinator can read the PID XML
instance and perform a coordinator setup and the configuration of devices, equipment or software modules.
The configuration shall be performed via the virtual device service interface (VDSI) of the device drivers as
defined in ISO 20242-3.
4 © ISO 2011 – All rights reserved

---------------------- Page: 9 ----------------------
ISO 20242-4:2011(E)
Device C
Coordinator
Capabilities
Device B
Parameters
Generic Technology- Technology-
Capabilities
Device A and
Specific
DCPT Specific
Capabilities Device
Capabilities
DCPT
(XML Schema) Configurations
(XML Schema)
DCD C
(XML Schema)
DCD B
Technology-
Generic
(XML Schema)
Specific
Extension
DCD
Extension DCD A
DCD
(XML Schema)
Import
Coordinator
Capabilities
Technology-
Generic
CCD PID
Specific
CCD
Extension (XML Schema) (XML Instance)
Extension
CCD

NOTE In this figure, a cylinder shape shows the XML file and a paper shape shows the capability or configuration
information. A solid arrow shows the extension of the XML schema file. A broken arrow shows the injection of capability or
configuration information. A small dotted arrow shows the application of the XML schema.
Figure 3 — Creation procedure of CCD and DCD
5.2.2 Device capability description (DCD)
The DCD shall be an XML schema and shall contain the following:
 identification information of the device driver;
 a description of device capabilities of virtual devices supported by the device driver.
5.2.3 Coordinator capability description (CCD)
The CCD shall be an XML schema and shall contain the following:
 identification information of the coordinator software;
 a description of coordinator capabilities;
 qualification of the supported application program service interface.
5.2.4 Parameterization instance description (PID)
The PID shall be an XML instance and shall contain the following:
 identification information of the PID as information exchange profile of ISO 15745;
 a description of parameterization instances with application-defined names;
 configuration data for the device drivers.
© ISO 2011 – All rights reserved 5

---------------------- Page: 10 ----------------------
ISO 20242-4:2011(E)
6 Generic device capability profile template
6.1 General
The generic DCPT defines the common structure of DCPT and is not dependent on technology of a service
interface. A technology-specific DCPT extends the generic DCPT.
6.2 Generic DCPT model
The generic DCPT extends the information of the VDSI model in ISO 20242-3. Figure 4 shows the class
structure of the generic DCPT. The information exchange profile is the root class and contains the ISO 15745
header and the ISO 15745 body. The ISO 15745 header describes the identification information of a profile.
The ISO 15745 body contains one or more generic CCDs. The information exchange profile, the ISO 15745
header and the ISO 15745 body are defined in ISO 15745-1.

InformationExchangeProfile
1.*
GenericCCD
0.*
1.*
GenericDCD
1.*
VirtualDevice
0.*
FunctionObject
0.* 0.*
CommunicationObject Operation

Figure 4 — Class diagram of generic DCPT model
The generic CCD is an abstract class that describes generic capabilities of a coordinator. The number of
generic CCDs is equal to the number of coordinators.
A generic CCD contains generic DCDs. The generic DCD is an abstract class that describes generic
capabilities of device drivers. The number of generic DCDs is equal to the number of device drivers.
6 © ISO 2011 – All rights reserved

---------------------- Page: 11 ----------------------
ISO 20242-4:2011(E)
A generic DCD contains virtual devices. The virtual device is an abstract class that describes generic
capabilities of virtual devices.
A virtual device contains function objects. The function object is an abstract class that describes generic
capabilities of functions of virtual devices.
A function object contains communication objects and operations.
The communication object is an abstract class that describes generic capabilities of communication objects
defined in ISO 20242-3.
The operation is an abstract class that describes generic capabilities of operations defined in ISO 20242-3.
6.3 Generic DCPT XML schema
The generic DCPT XML schema in Figure 5 describes the information exchange profile template. The generic
DCPT XML schema includes the generic CCD XML schema and refers to the generic CCD element. The
DCPT header used in the annotation part of Figure 5 is defined in 7.2.

      xmlns="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
      targetNamespace="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
      elementFormDefault="qualified">


 
 
  GenericDCPT
  1.0
  Generic DCPT
  GenericDCPT.xsd
  2011-07-01
 
 







 
 
  
  
 
 




 
 
  
  
  
  
                          fixed="InformationExchange"/>
            minOccurs="0"/>
            minOccurs="0"/>
© ISO 2011 – All rights reserved 7

---------------------- Page: 12 ----------------------
ISO 20242-4:2011(E)
  
                          fixed="CSI"
         minOccurs="0"        maxOccurs="unbounded"/>
 
 



 
                         fixed="1"/>
                         fixed="1"/>
                         fixed="None"/>
 



 
 
 
 
 
 
 
 
 
 
 



 
 
  
  
  
  
  
  
  
  
  
  
  
  
 
 
  
  
  
 
 




 
 
  
 
 


Figure 5 — Generic DCPT XML schema
8 © ISO 2011 – All rights reserved

---------------------- Page: 13 ----------------------
ISO 20242-4:2011(E)
The generic CCD XML schema in Figure 6 describes the generic CCD template. The generic CCD XML
schema includes the generic DCD XML schema and refers to the generic DCD element. The DCPT header
used in the annotation part of Figure 5 is defined in 7.2.

      xmlns="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
      targetNamespace="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
      elementFormDefault="qualified">


 
 
  GenericCCD
  1.0
  Generic CCD
  GenericCCD.xsd
  2011-07-01
 
 









 
 
 
 
           use="required"  fixed="CCD"/>


Figure 6 — Generic CCD XML schema
The generic DCD XML schema in Figure 7 describes the generic DCD template. It includes templates of the
virtual device, the function object, the communication object and the operation. The DCPT header used in the
annotation part of Figure 5 is defined in 7.2.

      xmlns="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
      targetNamespace="http://www.osi.ch/iso/ISO20242-4/GenericDCPT"
      elementFormDefault="qualified">


 
 
  GenericDCD
  1.0
  Generic DCD
  GenericDCD.xsd
  2009-03-16
 
 



       type="GenericDCDType" abstract="true"/>

© ISO 2011 – All rights reserved 9

---------------------- Page: 14 ----------------------
ISO 20242-4:2011(E)

 
 
 
 
           use="required"   fixed="DCD"/>


       type="VirtualDeviceType" abstract="true"/>


 
 
 
 
           use="required"   fixed="MODULE"/>


       type="FunctionObjectType" abstract="true"/>


 
 
 
 
 
           use="required"   fixed="INTERFACE"/>


       type="CommunicationObjectType" abstract="true"/>


 


       type="OperationType" abstract="true"/>


 
           use="required"   fixed="OPERATION"/>



Figure 7 — Generic DCD XML schema
7 Common rules for DCPT
7.1 General
The common rules shall be used for the e
...