ISO 15745-4:2003/Amd 1:2006

INTERNATIONAL ISO
STANDARD 15745-4
First edition
2003-03-01
AMENDMENT 1
2006-02-15
Industrial automation systems and
integration — Open systems application
integration framework —
Part 4:
Reference description for Ethernet-based
control systems
AMENDMENT 1: PROFINET profiles
Systèmes d'automatisation industrielle et intégration — Cadres
d'intégration d'application pour les systèmes ouverts —
Partie 4: Description de référence pour les systèmes de contrôle fondés
sur Ethernet
AMENDEMENT 1: Profils pour PROFINET

Reference number
ISO 15745-4:2003/Amd.1:2006(E)
©
ISO 2006
ISO 15745-4:2003/Amd.1:2006(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2006
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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(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.
Amendment to ISO 15745-4: was prepared by Technical Committee ISO/TC 184, Industrial automation
systems and integration, Subcommittee SC 5, Architecture, communications and integration frameworks.
1)
This amendment to ISO 15745-4:2003 specifies profiles for PROFINET and, as such, adds to the number of
technology-specific elements and rules in ISO 15745-4 for describing both communication network profiles
and communication-related aspects of device profiles, thus further extending the Application Integration
Framework described in ISO 15745-1.

1) PROFINET is a trade name of PROFIBUS International (PI). This information is given for the convenience of users of
ISO 15745 and does not constitute an endorsement by ISO of the trademark holder or any of its products. Compliance to
this profile does not require use of the trade name PROFINET. Use of the trade name PROFINET requires permission of
PROFIBUS International.
ISO 15745-4:2003/Amd.1:2006(E)

Industrial automation systems and integration —

Open systems application integration framework —
Part 4:
Reference description for Ethernet-based control systems
AMENDMENT 1: PROFINET profiles
Page 1, clause 2
Add the following normative references:
"ISO 639-1:2002, Codes for the representation of names of languages – Part 1: Alpha-2 code
"ISO 15745-3:2003, Industrial automation systems and integration – Open systems application integration
framework – Part 3: Reference description for IEC 61158-based control systems
"ISO/IEC 11578:1996, Information technology -- Open Systems Interconnection -- Remote Procedure
Call (RPC)
"REC-svg-20030114, Scalable Vector Graphics (SVG) 1.1 Specification – W3C Recommendation 14
January 2003, available at
"REC-xpath-19991116, XML Path Language (XPath) Version 1.0 – W3C Recommendation 16 November
"RFC 1101:1989, DNS encoding of network names and other types – Internet Engineering Task Force
(IETF), Request for Comments (RFC)
"RFC 2131:1997, Dynamic Host Configuration Protocol – Internet Engineering Task Force (IETF),
Request for Comments (RFC)"
Page 2, clause 4
Add the following abbreviated terms:
"DAP Device Access Point
"DNS Domain Name System (see RFC 1101)
"GSD Generic Station Description
"GSDML Generic Station Description Markup Language
"ID Identification
"IO Input/Output
"PDU Protocol Data Unit
"SVG Scalable Vector Graphics (see REC-svg-20030114)
"URL Uniform Resource Locator
ISO 15745-4:2003/Amd.1:2006(E)
"UUID Universally Unique Identifier (see ISO/IEC 11578)
"W3C World Wide Web Consortium"
Page 3, subclause 5.2.2
In the second sentence of the second paragraph, replace "(Annex A to Annex C)" with "(see annexes)."
Page 4, Table 1
Add a row with the entries "GSDML" under the "ProfileTechnology name" column and "PROFINET" under the
"Technology" column.
Page 4, subclause 5.3
Add a fourth list item in the first paragraph to read "—  PROFINET (see 6.4)."
In the second paragraph, replace "Annex A to Annex C." with "the annexes."
Page 18
Insert the following new subclause 6.4 before Annex A.
6.4 PROFINET
6.4.1 General
NOTE In addition to the UML terminology and notation in ISO 15745-1:2003, Annex A, the following diagrams make
use of the multiplicity notation (UML V1.4). The multiplicity of an attribute is displayed in squared brackets.
6.4.2 Device profile
6.4.2.1 General
Figure 11 shows the class structure of a GSDML device profile.
DeviceProfile
DeviceIdentity
DeviceFunction
1.*
ApplicationProcess
0.*
Figure 11 — GSDML device profile class diagram
The XML schema representing the GSDML device profile template is defined in D.5.2. The profile header of
the GSDML device profile shall have the following content:

PROFINET Device Profile
1.00
Device Profile for PROFINET Devices
PROFIBUS Nutzerorganisation e. V. (PNO)
2 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
Device

4
1
GSDML


6.4.2.2 Device identity
Figure 12 shows the structure of the DeviceIdentity class.
DeviceIdentity
VendorID
DeviceID
1 1
InfoText VendorName
TextId[1] Value[1]
Figure 12 — DeviceIdentity class diagram
Attributes and semantics of the classes are defined in D.4.2.

6.4.2.3 Device function
Figure 13 shows the structure of the DeviceFunction class.
DeviceFunction
Family
MainFamily[1]
ProductFamily[0.1]
Figure 13 — DeviceFunction class diagram
Attributes and semantics of the classes are defined in D.4.3.
ISO 15745-4:2003/Amd.1:2006(E)
6.4.2.4 Application process
6.4.2.4.1 General
Figure 14 describes the structure of the ApplicationProcess element. UML classes without an attribute field
are detailed in a separate diagram. Attributes and semantics of the classes are defined in D.4.4.

A)
ApplicationProcess DeviceAccessPointList
DeviceAccessPointItem
1 1.*
A)
ModuleItem
ModuleList
ModuleInfo
ID[1]
ModuleIdentNumber[1]
1 1.* 1
A)
VirtualSubmoduleList
VirtualSubmoduleItem
ValueList ValueItem
GraphicItemRef
ID[1]
Graphics
0.1 1.*
Type[1]
0.1
GraphicItemTarget[1]
1.*
Help
TextId[1]
0.1
Assign
Assignments
Content[1]
TextId[1]
0.1 1.*
ChannelDiagList ChannelDiagItem Name
ErrorType[1] TextId[1]
0.1 1.*
Help
Ref
TextId[1]
ValueItemTarget[0.1]
0.1
ByteOffset[1]
BitOffset[0.1]
BitLength[0.1]
UnitDiagTypeList UnitDiagTypeItem
DataType[1]
UserStructureIdentifier[1]
DefaultValue[1]
0.1 1.*
1.*
AllowedValues[0.1]
Changeable[0.1]
Visible[0.1]
GraphicItem
GraphicsList Embedded TextId[1]
ID[1]
GraphicFile[1]
0.1 1.* 0.1
CategoryItem
CategoryList
ID[1]
TextId[1]
0.1
1.*
Text
ExternalTextList PrimaryLanguage
TextId[1]
Value[1]
1 1 1.*
Text
Language
TextId[1]
xml:lang[1]
Value[1]
0.* 1.*
4 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
A)
see subdiagram for details
Figure 14 — PROFINET ApplicationProcess class diagram
6.4.2.4.2 DeviceAccessPointItem
Figure 15 describes the structure of the DeviceAccessPointItem element. UML classes without an attribute
field are explained in a separate diagram in detail. Attributes and semantics of the classes are defined in D.4.5.
DeviceAccessPointItem
A)
ID[1]
ModuleInfo
PhysicalSlots[1]
ModuleIdentNumber[1]
MinDeviceInterval[1]
DNS_CompatibleName[1]
IOConfigData
AllowedInSlots[0.1]
MaxInputLength[1]
FixedInSlots[1]
MaxOutputLength[1]
ObjectUUID_LocalIndex[1]
MaxDataLength[0.1]
ImplementationType[0.1]
ExtendedAddressAssignmentSupported[0.1]
ModuleItemRef
ModuleItemTarget[1]
UseableModules
AllowedInSlots[0.1]
UsedInSlots[0.1]
1 1.*
FixedInSlots[0.1]
A)
VirtualSubmoduleList
VirtualSubmoduleItem
1 1
GraphicItemRef
Graphics
Type[1]
GraphicItemTarget[1]
0.1
1.*
ApplicationRelations
TimingProperties
AR_BlockVersion[1]
IOCR_BlockVersion[1] SendClock[0.1]
AlarmCR_BlockVersion[1] ReductionRatio[0.1]
0.1 0.1
SubmoduleDataBlockVersion[1]
A)
see subdiagram for details
Figure 15 — PROFINET DeviceAccessPointItem class diagram
6.4.2.4.3 VirtualSubmoduleItem
Figure 16 describes the structure of the VirtualSubmoduleItem element. UML classes without an attribute field
are explained in a separate diagram in detail. Attributes and semantics of the classes are defined in D.4.6.

ISO 15745-4:2003/Amd.1:2006(E)
DataItem
VirtualSubmoduleItem IOData
Input DataType[1]
ID[1] IOPS_Length[0.1] Length[0.1]
Consistency[0.1]
SubmoduleIdentNumber[1] IOCS_Length[0.1] UseAsBits[0.1]
0.1 1.*
TextId[1]
DataItem
DataType[1]
Output
Length[0.1]
Consistency[0.1]
UseAsBits[0.1]
0.1 1.*
A)
TextId[1]
RecordDataList
0.1
A)
ModuleInfo
0.1
GraphicItemRef
Graphics
Type[1]
GraphicItemTarget[1]
0.1 1.*
A)
see subdiagram for details
Figure 16 — PROFINET VirtualSubmoduleItem class diagram

6.4.2.4.4 RecordDataList
Figure 17 describes the structure of the RecordDataList element. Attributes and semantics of the classes are
defined in D.4.7.
Name
RecordDataList
TextId[1]
0.*
Const
ByteOffset[0.1]
ParameterRecordDataItem
Data[1]
0.*
Index[1]
Length[1]
TransferSequence[0.1]
Ref
ValueItemTarget[0.1]
ByteOffset[1]
BitOffset[0.1]
0.*
BitLength[0.1]
DataType[1]
DefaultValue[1]
AllowedValues[0.1]
Changeable[0.1]
Visible[0.1]
TextId[1]
Figure 17 — PROFINET RecordDataList class diagram
6 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
6.4.2.4.5 ModuleInfo
Figure 18 describes the structure of the ModuleInfo element. Attributes and semantics of the classes are
defined in D.4.8.
ModuleInfo
CategoryRef[0.1]
SubCategory1Ref[0.1]
Name
TextId[1]
InfoText
TextId[1]
VendorName
Value[1]
0.1
OrderNumber
Value[1]
0.1
HardwareRelease
Value[1]
0.1
SoftwareRelease
Value[1]
0.1
Family
MainFamily[1]
ProductFamily[0.1]
0.1
Figure 18 — PROFINET ModuleInfo class diagram
ISO 15745-4:2003/Amd.1:2006(E)

6.4.3 Communication network profile
Figure 19 shows the class structure of a GSDML communication network profile.
CommNetworkProfile
ApplicationLayers
TransportLayers
Figure 19 — PROFINET communication network profile class diagram
NOTE In GSDML the classes of the communication network profile are empty. The reason is that no options of the
communication properties of a PROFINET device are provided.
The XML schema representing the GSDML communication network profile template is defined in D.5.3.

Page 125
Insert the following new Annex D before the Bibliography.

8 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
Annex D
(normative)
PROFINET profile templates
D.1 Overview
PROFINET is an Ethernet based network compliant to IEC 61784-1 (Ed.1) CP 3/3.
PROFINET uses the profile description based on ISO 15745-1. The profile technology name is GSDML
(Generic Station Description Markup Language).
It is not the purpose of the GSDML format to describe technological functions or the graphical user interface of
a device. For this purpose already established concepts (for example Electronic Device Description Language
(EDDL) according IEC 61804-2) are recommended.
By using the GSDML a GSD (Generic Station Description) file is created. In order to distinguish from the
2)
PROFIBUS GSD format described in ISO 15745-3:2003, Annex B, the term "GSDML based file" is used in
this document.
A GSDML based file can contain more than one Device Access Points (DAP). A DAP is a special module
which connects the device to the network.This allows building one file for a family of devices sharing the same
modules (see D.4.4.1 and D.4.5).
D.2 Data types
Table D.1 describes the data types used in the GSDML.
Regular expressions are used as defined in REC-xml-20001006.

2)
PROFIBUS is a trade name of PROFIBUS International (PI). This information is given for the convenience of users of
ISO 15745 and does not constitute an endorsement by ISO of the trademark holder or any of its products. Compliance to
this profile does not require use of the trade name PROFIBUS. Use of the trade name PROFIBUS requires permission of
PROFIBUS International.
ISO 15745-4:2003/Amd.1:2006(E)
Table D.1 — Data types
Name Definition Schema Description
Boolean http://www.w3.org/2001/XMLSchema See (REC-xmlschema-2-20010502)
Enumeration GSDML-DeviceProfile-v1.0.xsd String with defined content
IdT GSDML-Primitives-v1.0.xsd Used for object identification.
The value list shall comply with the following regular
expression:
(\S(.)*\S)|\S
NormalizedString http://www.w3.org/2001/XMLSchema See (REC-xmlschema-2-20010502)
Token http://www.w3.org/2001/XMLSchema See (REC-xmlschema-2-20010502)
RefIdT GSDML-Primitives-v1.0.xsd Used for object reference
Unsigned8 GSDML-Primitives-v1.0.xsd Unsigned integer in range 0.255
Unsigned16 GSDML-Primitives-v1.0.xsd Unsigned integer in range 0.65535
Unsigned32 GSDML-Primitives-v1.0.xsd Unsigned integer in range 0. 4294967295
ValueList GSDML-Primitives-v1.0.xsd Base type for a list including ranges of unsigned
values. The value list shall comply with the following
regular expression:
((\d+\.\.\d+)|(\d+))(( \d+\.\.\d+)|( \d+))*
If a range is defined, the value left from “.” shall be
less than the value right from “.” (see Example 1).
SignedValueList GSDML-Primitives-v1.0.xsd Base type for a list including ranges of signed
values. The value list shall comply with the following
regular expression:
((\-?\d+\.\.\-?\d+)|(\-?\d+))(( \-?\d+\.\.\-?\d+)|( \-
?\d+))*
If a range is defined, the value left from “.” shall be
less than the value right from “.” (see Example 2).
EXAMPLE 1 Valid ValueList contents:
1 2 3 4
5 12211
0.6
5.12
0.34 36 38
EXAMPLE 2 Valid SignedValueList contents:
1 2 3 4
-12 5 12211
0.6
-5.12
0.34 36 38
D.3 General rules
D.3.1 Version control
If a GSDML based file is already released, it is important that the identification of objects remains unchanged.
Therefore the content of the attributes corresponding to the following XPath expressions (see REC-xpath-
19991116) shall not be changed in a new version of a GSDML based file:
//DeviceAccessPointItem/@ID
//ModuleList/ModuleItem/@ID
//VirtualSubmoduleItem/@ID
10 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
//ValueItem/@ID
//GraphicItem/@ID
//CategoryItem/@ID
D.3.2 Rules for the name of a GSDML based file
The name of a GSDML based file shall be composed of the six fields below in the following order:
⎯ "GSDML"
⎯ The version ID in format Vx.y whereby “x” and “y” are unsigned numbers. The version ID refers to the ID
of the GSDML Schema used.
⎯ Vendor name
⎯ Device family name
⎯ Release date of the GSDML based file in format yyyymmdd
⎯ “.xml” (file extension)
As a delimiter between the fields the dash character “-“ (ASCII 45 decimal) shall be used.
EXAMPLE   "GSDML-V1.0-Lieferant-ET200X-20030818.xml"
Already released files shall not be changed without changing the filename. When building a new version of a
GSDML based file, the release date shall be changed.
If more than one version of a GSDML based file is installed, the engineering system can use the release date
to determine the newest version.
D.3.3 Schema location in a GSDML based file
An XML schema validator needs information about the location of the assigned schema file. Therefore the
attribute xsi:schemaLocation of the ISO15745Profile root element is specified.
To use the same location for all GSDML based files, the relative path “.\xsd” shall be used for the schema
files.
D.3.4 Identification of objects
Some elements in the GSDML schema can be addressed by an identifier. This identifier is an attribute with
the name “ID”. See D.3.2 for the valid range of this attribute.
The Identification of objects shall be kept unique over all elements of the same category as described in the
following table. (For example, all Identification of objects of Object of type “ModuleItem” shall be kept unique)
Document wide unique IDs are not necessary.
Table D.2 shows the addressable elements. The right column shows all those objects where the items of the
left column are being referenced in. These references use the IDs in question as a means of addressing.
ISO 15745-4:2003/Amd.1:2006(E)
Table D.2 — Object identification
Type Referring Elements
DeviceAccessPointItem Reserved for future use.
ModuleItem Attribute ModuleItemTarget of the element UseableModules/ModuleItemRef (see
D.4.5.5).
VirtualSubmoduleItem Reserved for future use.
ValueItem Attribute ValueItemTarget of all Ref elements.
CategoryItem Attributes CategoryRef and SubCategory1Ref of the element ModuleInfo (see D.4.8.1).
GraphicItem Referenced from the element Graphics/GraphicItemRef (see D.4.8.10).

D.3.5 Language support
The language support is based on the concepts of XML. Language dependent strings can be kept within the
GSDML based file or separated in another file. Both strategies can be combined.
The different strings are placed in the form of dictionaries inside the GSDML. Every language dependent text
shall have a "TextId" attribute referencing an entry of a dictionary.
EXAMPLE 1





< Text TextId="ID_COMM_ERROR" Value = "Communication error"/>


< Text TextId="ID_COMM_ERROR" Value = "Kommunikationsfehler"/>


< Text TextId="ID_COMM_ERROR" Value = "Erreur de communication"/>


The ExternalTextList shall have an element PrimaryLanguage. The text strings defined within the
PrimaryLanguage element are used if a text string is missing in the selected language. For a GSDML based
file the primary language shall be english.
The Language elements of the ExternalTextList shall have an attribute "xml:lang" for identification of the
selected language. The codes for the representation of names of languages shall comply with ISO 639-1:2002.
In addition strings can reside in a external file – no changes are needed in the GSDML based file itself to
support a new language. The name of the external file shall be built by the name of the corresponding GSDML
based file name appending the string "-Text-" and the ISO 639-1:2002 compliant two letter code.
EXAMPLE 2 "GSDML-V1.0-Lieferant-ET200X-20030818-Text-fr.xml"
External files shall be located relative to the GSDML based file in a subdirectory. The name of the
subdirectory shall be built of the two letter language code of the language of the external file. (ISO 639-
1:2002)
The coding of the XML file (e.g. UTF-8) is not regulated by the GSDML. Any coding compliant with the rules of
the XML specification is allowed.

12 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
D.3.6 Notation of elements and attributes for schema extensions
In GSDML schema extensions the names of elements and attributes shall be composed as follows:
⎯ First character shall be either a decimal number ("0" to "9") or a capital letter in the range "A" to "Z".
⎯ The following characters shall be in the range "0" to "9" or "a" to "z". Capital letters in the Range "A" to "Z"
can be used in order to improve the readability.
⎯ Abbreviations shall be used in capital form followed by an "_" character when one or more characters are
following.
⎯ The first character after the "_" character shall be either a decimal number ("0" to "9") or a capital letter in
the range "A" to "Z
NOTE In GSD up to revision 5 the “_” character is often used to separate parts of keywords in order to make the
keywords more readable. Sometimes upper and lower case letters were used for the same purpose.
D.4 Element description
D.4.1 General
Regular expressions are used as defined in REC-xml-20001006.
D.4.2 Device identity related elements
D.4.2.1 DeviceIdentity
Contains general information about a device. Each element shall contain attributes as shown in Table D.3
Table D.3 — Attributes of element DeviceIdentity
Name Type Use Description
VendorID NormalizedString Required Contains the vendor specific part of the DeviceIdentNumber.
The value shall comply with the following regular expression:
0x[0-9,a-f,A-F]{1,4}.
The VendorID is assigned by vendor association.
Manufacturers of devices have to apply for the VendorID at
the appropriate vendor association. For PROFINET the
responsible association to assign a unique VendorID is the
tradename owner.
DeviceID NormalizedString Required Contains the device specific part of the DeviceIdentNumber.
The DeviceID is a unique ID for all devices of a vendor. The
vendor has to keep this ID unique.
The value shall comply with the following regular expression:
0x[0-9,a-f,A-F]{1,4}.
D.4.2.2 DeviceIdentity/InfoText
Contains human readable additional text information about a device.
Use: Required.
Each element shall contain at least one attribute out of Table D.4.
ISO 15745-4:2003/Amd.1:2006(E)
Table D.4 — Attribute of element InfoText
Name Type Use Description
TextId Token Required Contains the ID of a text as a reference into the
ExternalTextList (see D.4.4.24).

D.4.2.3 DeviceIdentity/VendorName
Contains the name of the device vendor.
Use: Required
Each element shall contain the attribute as shown in Table D.5.
Table D.5 — Attribute of element VendorName
Name Type Use Description
Value Token Required Contains the name of the device vendor.

D.4.3 Device function related elements
D.4.3.1 DeviceFunction
The DeviceFunction element shall contain the element "Family".
Use: Required
Attributes: None
D.4.3.2 DeviceFunction/Family
The device shall be assigned to a function class. In addition to the main family, a device can be assigned to a
vendor specific product family.
Each element shall contain at least one attribute out of Table D.6.
14 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
Table D.6 — Attributes of element Family
Name Type Use Description
MainFamily Enumeration Required Contains the assignment to a function class.
One of the following values are allowed:
0: “General”
1: “Drives”
2: “Switching devices”
3: “I/O”
4: “Valves”
5: “Controllers”
6: “HMI”
7: “Encoders”
8: “NC/RC”
9: “Gateway”
10: “Programmable Logic Controllers”
11: “Ident systems”
12: “PROFIBUS PA Profile”
ProductFamily xsd:string Optional Contains the vendor specific assigment of the device to
a product family.
D.4.4 Application process related elements
D.4.4.1 DeviceAccessPointList
GSDML shall contain information about one or more different access points of the same family. This element
contains the list of specified DAP.
Use: Required
Attributes: none
D.4.4.2 ModuleList
This list contains all modules that are described within this GSDML based file.
Use: Required
Attributes: none
D.4.4.3 ModuleList/ModuleItem
This element contains subelements to describe the properties of a module.
Use: One or more
Each element shall contain attributes as shown in Table D.7.
ISO 15745-4:2003/Amd.1:2006(E)
Table D.7 — Attributes of element ModuleItem
Name Type Use Description
ID IdT Required Contains the Unique ID to be referenced by the element
UseableModules/ModuleItemRef (see D.4.5.5).
To be upward compatible from GSD, see ISO 15745-3:2003,
Annex B, the Value of the ID should be the same as the
parameter Module_Reference of the keyword Module in GSD,
see ISO 15745-3:2003, Annex B.
ModuleIdentNumber NormalizedString Required Contains the Module Ident Number of the module.
The value shall comply with the following regular expression:
0x[0-9,a-f,A-F]{1,8}
D.4.4.4 ModuleList/ModuleItem/ModuleInfo
See D.4.7.
D.4.4.5 ModuleList/ModuleItem/VirtualSubmoduleList
See D.4.6.
D.4.4.6 ModuleList/ModuleItem/Graphics
See D.4.7.
D.4.4.7 ValueList
The ValueList element contains elements for the assignment of values to text strings.
See D.4.7.4 for an example of the ValueList.
Use: Optional
Attributes: None
D.4.4.8 ValueList/ValueItem
The ValueItem element groups all value objects and can be referenced from the “UserDataItem/Data” element.
Use: One or more
Each element shall contain attributes as shown in Table D.8.
Table D.8 — Attribute of element ValueItem
Name Type Use Description
ID IdT Required Contains the ID of the ValueItem element to be referenced
from the attribute TextTarget of the element Ref.

D.4.4.9 ValueList/ValueItem/Help
The Help element contains additional help information about the ValueItem parameter.
Use: Optional.
16 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
Each element shall contain at least one attribute out of Table D.9
Table D.9 — Attribute of element Help
Name Type Use Description
TextId Token Required Contains the ID of a text as a reference into the
ExternalTextList (see D.4.4.24).

D.4.4.10 ValueList/ValueItem/Assignments
This element contains an unlimited number of "Assign" elements.
Use: Optional.
Attributes: None.
D.4.4.11 ValueList/ValueItem/Assignments/Assign
The Assign element contains the assignment between the content of a parameter and the textual
representation.
Use: One or more
Each element shall contain attributes as shown in Table D.10.
Table D.10 — Attributes of element Assign
Name Type Use Description
Content NormalizedString Required Contains the value to assign to a text reference.
The value shall comply with the following regular
expression:
\-?[\d+]{1,20}
Within an element Assignments the attribute Content of all
child elements Assign shall be unique.
TextId Token Required Contains the ID of the language dependent text in the
ExternalTextList (see D.4.4.24).
Within an element Assignments the attribute TextId of all
child elements Assign shall be unique.

D.4.4.12 ChannelDiagList
Specifies a list of - channel type specific - error texts.
NOTE Used for help information.
Use: Optional
Attributes: None
D.4.4.13 ChannelDiagList/ChannelDiagItem
A ChannelDiagItem contains attributes to specify the error type of a specific channel.
Use: One or more
ISO 15745-4:2003/Amd.1:2006(E)
Each element shall contain attributes as shown in Table D.11.
Table D.11 — Attributes of element ChannelDiagItem
Name Type Use Description
ErrorType Unsigned16 Required Contains the error type where the diagnostic text
definitions can be assigned.
D.4.4.14 ChannelDiagList/ChannelDiagItem/Name
Contains the language dependent text information.
Use: Required
Each element shall contain attributes as shown in Table D.12.
Table D.12 — Attribute of element Name
Name Type Use Description
TextId Token Required Contains the ID of a text as a reference into the
ExternalTextList (see D.4.4.24).

D.4.4.15 ChannelDiagList/ChannelDiagItem/Help
Contains the language dependent help information.
Use: Optional
Each element shall contain attributes as shown in Table D.13.
Table D.13 — Attribute of element Help
Name Type Use Description
TextId Token Required Contains the ID of a text as a reference into the
ExternalTextList (see D.4.4.24).

D.4.4.16 UnitDiagTypeList
The UnitDiagTypeList assigns diagnostic values to manufacturer specific status and error messages.
Use: Optional
Attributes: None
D.4.4.17 UnitDiagTypeList/UnitDiagTypeItem
Use: One or more
Each element shall contain attributes as shown in Table D.14.
18 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
Table D.14 — Attributes of element UnitDiagTypeItem
Name Type Use Description
UserStructureIdentifier Unsigned16 Required Describes the User Structure Identifier of the alarm request
block. The UserStructureIdentifier shall be in the range
from "0" to "32767". Within the UnitDiagTypeList (see
D.4.4.16) the UserStructureIdentifier shall be unique.

D.4.4.18 UnitDiagTypeList/UnitDiagTypeItem/Ref
The Ref element contains information about a diagnostic data item within an alarm data object.
This element shall have the same attributes as defined in D.4.7.4.
The “ByteOffset” attribute of this element refers to the “additional alarm info” block of an alarm request PDU -
the header information is not included.
D.4.4.19 GraphicsList
This element contains a list of GraphicItems (see D.4.4.20).
Use: Optional
Attributes: None
D.4.4.20 GraphicsList/GraphicItem
A GraphicItem carries the information for the symbolic representation of a Device, Module, or Submodule.
Use: One or more
Each element shall contain attributes as shown in Table D.15.
Table D.15 — Attributes of element GraphicItem
Name Type Use Description
ID IdT Required Contains the ID of the GraphicItem element to be referenced from the
element Graphics/GraphicItemRef (see D.4.8.10).
GraphicFile String Required Contains the file name without file extension. The format depends on the
type of the GraphicItem which is defined by the attribute Type of the
element GraphicItemRef.
D.4.4.21 GraphicsList/GraphicItem/Embedded
This element is used to describe the graphical information inside the GSDML based file in SVG format (see
REC-svg-20030114).
NOTE Scaleable Vector Graphics (SVG) is a language for describing two-dimensional vector and mixed
vector/raster graphics in XML.
Use: Optional
Attributes: None
ISO 15745-4:2003/Amd.1:2006(E)
D.4.4.22 CategoryList
This element contains a list of CategoryItem (see D.4.4.23).
NOTE 1 GSDML allows building of module and submodule categories. These categories can be used to group the
modules and submodules within a catalog of an engineering tool. For example all analog input modules can be placed in
one section of the catalog. This makes it easier to find the required module for the user or the engineering tool.
NOTE 2 Assigning module does not impact the runtime characteristics of a module or submodule.
Use: Optional
Attributes: None
D.4.4.23 CategoryList/CategoryItem
A CategoryItem defines the information within a single category.
Use: One or more
Each element shall contain attributes as shown in Table D.16.
Table D.16 — Attributes of element CategoryItem
Name Type Use  Description
ID IdT Required Contains the ID of the CategoryItem element to be referenced from the attribute
CategoryRef or SubCategory1Ref of the element ModuleInfo (see D.4.8.1).
TextId Token Required Contains the ID of a text as a reference into the ExternalTextList (see D.4.4.24).

D.4.4.24 ExternalTextList
The ExternalTextList contains language dependent text strings.
Use: Required
Attributes: none
D.4.4.25 ExternalTextList/PrimaryLanguage
The PrimaryLanguage element contains the text definitions of the primary language which shall be used, if a
text in the selected language is not available. For GSDML the primary language is english.
Use: Required
Attributes: none
D.4.4.26 ExternalTextList/PrimaryLanguage/Text
The PrimaryLanguage element
Use: Required
Attributes: See Table D.17.
20 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
Table D.17 — Attributes of element Text
Name Type Use Description
TextId xsd:string Required Contains the unique ID for referencing a text. The TextId
shall be kept unique within the parent element
PrimaryLanguage or Language
Value xsd:string Required Contains the language dependent text.

D.4.4.27 ExternalTextList/Language
The Language element contains the text definitions of the specified language.
Use: One for each language.
Attributes: See Table D.18.
Table D.18 — Attributes of element Language
Name Type Use Description
xml:lang xsd:language Required Specifies the language of the text in subelement
Text/@Value
D.4.4.28 ExternalTextList/Language/Text
The Language element.
Use: Required
Attributes: See Table D.17.
D.4.5 DeviceAccessPoint related elements
D.4.5.1 DeviceAccessPointItem
This element describes the characteristics of a DAP.
Use: One for each DAP.
Each element shall contain attributes as shown in Table D.19.
ISO 15745-4:2003/Amd.1:2006(E)
Table D.19 — Attributes of element DeviceAccessPointItem
Name Type Use Description
ID ID Required Contains the ID of the element
PhysicalSlots ValueList Required This list describes which slots are
supported by the DAP. The
Slotnumber of the DAP itself shall
be part of the list.
ModuleIdentNumber NormalizedString Required Contains the Module Ident Number
of the module.
The value shall comply with the
following regular expression: 0x[0-
9,a-f,A-F]{1,8}
MinDeviceInterval Unsigned16 Required This time specifies the minimum
interval for sending cyclic IO data.
Basic clock tick is 31,25
microseconds. The value of this
element contains the multiplier of
the basic clock tick (see Example)
ImplementationType NormalizedString Optional Contains a description of the
standard implementation in the DAP
for example, standard software,
controller or ASIC (Application
Specific Integrated Circuit) solution.
DNS_CompatibleName NormalizedString Required Describes default name of a device
compliant with the Domain Name
System (DNS) rules according to
RFC 1101 (see Note)
ExtendedAddressAssignmentSupported Boolean Optional In PROFINET IO each IO Device
shall implement the Discovery and
Configuration protocol (DCP) for
assignment of the IP addresses.
If the DAP supports another way of
IP address assignment like Dynamic
Host Configuration Protocol (DHCP)
according RFC 2131, this attribute
has to be set to “true”.
Default: “false”
AllowedInSlots ValueList Optional Defines,which slots the DAP can be
placed in. If not defined, the DAP
cannot be placed into other slots as
defined in attribute "FixedInSlots"
FixedInSlots ValueList Required Specifies the slot number of the
DAP when the device is configured
in the engineering tool.
For a non redundant DAP, only one
slot number is allowed in the list. It
is recommended to use "0" as
slotnumber.
If the attribute "AllowedInSlots" is
used, the slots defined in
"FixedInSlots" shall be a subset of
the slots defined by the attribute
"AllowedInSlots".
ObjectUUID_LocalIndex Unsigned16 Required Specifies the Instance field of the
Object UUID.
EXAMPLE MinDeviceInterval =32 means that the device is able to send/receive data every millisecond.
NOTE Attribute DNS_CompatibleName can be used by the engineering system to build a unique name of station.

22 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
D.4.5.2 ModuleInfo
See D.4.8.1.
D.4.5.3 IOConfigData
This element contains information about the quantity of IO data.
Use: Required
Each element shall contain attributes as shown in Table D.20.
Table D.20 — Attributes of element IOConfigData
Name Type Use Description
MaxInputLength Unsigned 16 Required Contains the maximum length of the data in octets which
can be transferred from the IO Device to the IO

Controller. This length is defined by the sum of the input
data of all used submodules, the corresponding IO
producer status and the IO consumer status of the used
output submodules.
MaxOutputLength Unsigned 16 Required Contains the maximum length of the data in octets which
can be transferred from the IO Controller to the IO

Device. This length is defined by the sum of the output
data of all used submodules, the corresponding IO
producer status and the IO consumer status of the used
input submodules.
MaxDataLength Unsigned 16 Optional Contains the maximum length of the output and input
data in octets. MaxDataLength shall not be less than the
highest value of MaxInputLength or MaxOutputLength.
It shall not be greater than the sum of MaxInputLength
and MaxOutputLength. If this keyword is not provided,
the maximum length is the sum of MaxInputLength and
MaxOutputLength.
D.4.5.4 UseableModules
The UseableModules element contains a list of module references referring to modules of the element
ModuleList. Only modules within this list are compatible with the DAP.
An engineering tool shall not be able to configure other modules for this DAP.
Use: Required
Attributes: None
D.4.5.5 UseableModules/ModuleItemRef
This element references a module of the ModuleList being compatible with a DAP.
Use: One or more
Each element shall contain attributes as shown in Table D.21.
ISO 15745-4:2003/Amd.1:2006(E)
Table D.21 — Attributes of element ModuleItemRef
Name Type Use Description
ModuleItemTarget RefIdT Required References an element ModuleList/ModuleItem (see D.4.4.3).
AllowedInSlots ValueList Optional Defines in which slots the module can be placed.
If this attribute is not defined, the module can be placed into all slots.

UsedInSlots ValueList Optional Defines in which slots the module is placed by default.
Those built-in modules can be removed with an engineering tool.
If the attribute AllowedInSlots is used, the slots defined in UsedInSlots
shall be a subset of the slots defined by the attribute AllowedInSlots.
FixedInSlots ValueList Optional Defines in which slots the module is placed by default.
Those built-in modules cannot be removed with an engineering tool.
If the attribute AllowedInSlots is used, the slots defined in FixedInSlots
shall be a subset of the slots defined by the attribute AllowedInSlots.

D.4.5.6 VirtualSubmoduleList
This element contains a list of VirtualSubmoduleItem (see D.4.6.1).
Use: Required
Attributes: None
D.4.5.7 VirtualSubmoduleList/VirtualSubmoduleItem
See D.4.6.1.
D.4.5.8 Graphics
See D.4.7.
D.4.5.9 Graphics/GraphicItemRef
See D.4.7.
D.4.5.10 ApplicationRelations
This element contains information about the application relations implemented in an IO Device.
The VersionInformation attributes are needed to check, if the structure of the connect PDU
(iPNIO_D_Connect-REQ-PDU) complies with the functionality of an IO Device. The engineering tool has to fill
in the version information into the connect PDU with this attributes.
Use: Optional
Each element shall contain attributes as shown in Table D.22.
24 © ISO 2006 – All rights reserved

ISO 15745-4:2003/Amd.1:2006(E)
Table D.22 — Attributes of element ApplicationRelations
Name Type Use Description
AR_BlockVersion Unsigned 16 Required Contains the version information about
the AR block.
IOCR_BlockVersion Unsigned 16 Required Contains the version information about
the IO communication relationship (CR)
block, called CR block.
AlarmCR_BlockVersion Unsigned 16 Required Contains the version information about
the alarm block.
SubmoduleDataBlockVersion Unsigned 16 Required Contains the version information about
the submodule data block.
D.4.5.11 ApplicationRelations/TimingProperties
This element defines the timing behaviour for sending cyclic IO data.
Use: Optional
Each element shall contain attributes as shown in Table D.23.
Table D.23 — Attributes of element TimingProperties
Name Type Use Description
SendClock ValueList Optional Contains a list of cycle times supported
by the DAP for sending cyclic data.

Basic clock tick is 31,25 microseconds.
Each value of this element contains the
multiplier of the basic clock tick and can
be in the range "1" to "128" (see
Example).
Default is “32”.
ReductionRatio ValueList Optional The send clock interval can be reduced
by a reduction. This attribute describes
the supported reduction ratios of a DAP.
Each value of this element shall be in the
range "1" to " 16384".
EXAMPLE SendClock="16, 32, 64" means that the DAP is able to send cyclic data in interval 500µs, 1ms or 2ms.

D.4.6 Submodule related elements
D.4.6.1 VirtualSubmoduleItem
This element defines the characteristics of a submodule as part of a module.
Use: Required
Each element shall contain attributes as shown in Table D.24.
ISO 15745-4:2003/Amd.1:2006(E)
Table D.24 — Attributes of element VirtualSubmoduleItem
Name Type Use Description
ID IdT Required Contains the ID of the element

SubmoduleIdentNumber NormalizedString Required Contains the Submodule Ident Number for
identification purposes. In this release of the
...