ISO 15745-4:2003

INTERNATIONAL ISO
STANDARD 15745-4
First edition
2003-11-15
Industrial automation systems and
integration — Open systems application
integration framework —
Part 4:
Reference description for Ethernet-based
control systems
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
Reference number
©
ISO 2003
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 2003
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 2003 — All rights reserved

Contents Page
Foreword.v
Introduction .vi
1 Scope.1
2 Normative references.1
3 Terms and definitions.2
4 Abbreviated terms.2
5 Technology specific elements and rules.3
5.1 Integration models and IAS interfaces .3
5.2 Profile templates.3
5.2.1 General.3
5.2.2 Contents and syntax.3
5.2.3 Header.4
5.3 Technology specific profiles .4
6 Device and communication network profiles for Ethernet-based control systems .4
6.1 ADS-net.4
6.1.1 Device profile.4
6.1.2 Communication network profile.6
6.2 FL-net.10
6.2.1 Device profile.10
6.2.2 Communication network profile.12
6.3 EtherNet/IP.15
6.3.1 Device profile.15
6.3.2 Communication network profile.17
Annex A (normative) ADS-net profile templates .19
A.1 General.19
A.2 ADS-net device profile template description .19
A.2.1 General.19
A.2.2 Semantics of XML schema elements.19
A.2.3 ADS-net_Device_Profile.xsd.21
A.3 ADS-net communication network profile template description.23
A.3.1 General.23
A.3.2 Semantics of XML schema elements.24
A.3.3 ADS-net_CommNet_Profile.xsd.28
Annex B (normative) FL-net profile templates .34
B.1 Device profile template description .34
B.1.1 General.34
B.1.2 DeviceIdentity.34
B.1.3 DeviceManager.34
B.1.4 ApplicationProcess.35
B.1.5 FL-net device profile template XML schemas.35
B.2 FL-net communication network profile template description .39
B.2.1 General.39
B.2.2 ApplicationLayers.39
B.2.3 TransportLayers.40
B.2.4 NetworkManagement.40
Annex C (normative) EtherNet/IP profile templates.48
C.1 General.48
C.2 Device profile template description . 49
C.2.1 Device profile template description – XML based . 49
C.2.2 Device profile template description – XML encapsulation of EDS files . 67
C.3 Communication network profile template description. 69
C.3.1 Communication network profile template description – XML based. 69
C.3.2 Communication network profile template description – XML encapsulation of EDS files . 82
C.4 Electronic Data Sheet (EDS) . 84
C.4.1 Common CIP EDS requirements . 84
C.4.2 EtherNet/IP specific EDS requirements . 123
Bibliography . 125

iv © ISO 2003 — All rights reserved

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 part of ISO 15745 may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
International Standard ISO 15745-4 was prepared by Technical Committee ISO/TC 184, Industrial automation
systems and integration, Subcommittee SC 5, Architecture, communications and integration frameworks.
ISO 15745 consists of the following parts, under the general title Industrial automation systems and integration —
Open systems application integration framework:
 Part 1: Generic reference description
 Part 2: Reference description for ISO 11898-based control systems
 Part 3: Reference description for IEC 61158-based control systems
 Part 4: Reference description for Ethernet-based control systems
Introduction
The application integration framework (AIF) described in ISO 15745 defines elements and rules that facilitate:
 the systematic organization and representation of the application integration requirements using integration
models;
 the development of interface specifications in the form of application interoperability profiles (AIPs) that enable
both the selection of suitable resources and the documentation of the "as built" application.
ISO 15745-1 defines the generic elements and rules for describing integration models and AIPs, together with their
component profiles - process profiles, information exchange profiles, and resource profiles. The context of ISO
15745 and a structural overview of the constituents of an AIP are given in Figure 1 of ISO 15745-1:2003.
This part of ISO 15745 extends the generic AIF described in ISO 15745-1 by defining the technology specific
elements and rules for describing both communication network profiles and the communication related aspects of
1 2 3 4
device profiles specific to Ethernet -based control systems (ADS-net , FL-net and EtherNet/IP™ ). EtherNet/IP™
technology uses a profile of IEC 61158 which is specified in IEC 61784-1.
In particular, this part of ISO 15745 describes technology specific profile templates for the device profile and the
communication network profile. Within an AIP, a device profile instance or a communication network profile
instance is part of the resource profile defined in ISO 15745-1. The device profile and the communication network
profile XML instance files are included in a resource profile XML instance using the ProfileHandle_DataType as
specified in ISO 15745-1:2003, 7.2.5.
AIFs specified using the elements and rules of ISO 15745-1 can be easily integrated with the component profiles
defined using the elements and rules specified in this part.

Ethernet is used in this document as a synonym for ISO/IEC 8802-3.
ADS-net is a trade name used to describe JIS-TR B0012 (Autonomous Decentralized System network). This information is
given for the convenience of users of ISO 15745 and does not constitute an endorsement by ISO of the trademark, or any
related products. Compliance to this standard does not require use of the trade name ADS-net.
FL-net is a trade name used to describe JEM 1479. This information is given for the convenience of users of ISO 15745 and
does not constitute an endorsement by ISO of the trademark, or any related products. Compliance to this standard does not
require use of the trade name FL-net.
EtherNet/IP™ is a trade name of ControlNet International, Ltd. and Open DeviceNet Vendor Association, Inc. 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 standard does not require use of the trade name EtherNet/IP™. Use of the trade name
EtherNet/IP™ requires permission of either ControlNet International, Ltd. or Open DeviceNet Vendor Association, Inc.
vi © ISO 2003 — All rights reserved

INTERNATIONAL STANDARD ISO 15745-4:2003(E)

Industrial automation systems and integration — Open systems
application integration framework —
Part 4:
Reference description for Ethernet-based control systems
1 Scope
This part of ISO 15745 defines the technology specific elements and rules for describing both communication
network profiles and the communication related aspects of device profiles specific to Ethernet-based control
systems.
NOTE Generic elements and rules for describing integration models and application interoperability profiles, together with
their component profiles (process profiles, information exchange profiles, and resource profiles) are specified in
ISO 15745-1.
This part of ISO 15745 is to be used in conjunction with ISO 15745-1 to describe an application integration
framework.
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 639-2:1998, Codes for the representation of names of languages – Part 2: Alpha-3 code
ISO 15745-1:2003, Industrial automation systems and integration – Open systems application integration
framework – Part 1: Generic reference description
ISO/IEC 7498-4:1989, Information processing systems – Open Systems Interconnection – Basic Reference Model
– Part 4: Management framework
ISO/IEC 8802-3:2000, Information technology – Telecommunications and information exchange between systems
– Local and metropolitan area networks – Specific requirements – Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method and physical layer specifications
ISO/IEC 10646-1:2000, Information technology – Universal Multiple-Octet Coded Character Set (UCS) – Part 1:
Architecture and Basic Multilingual Plane
IEC 61158 (all parts), Digital data communications for measurement and control – Fieldbus for use in industrial
control systems
IEC 61784-1:2003, Digital data communications for measurement and control – Part 1: Profile sets for continuous
and discrete manufacturing relative to fieldbus use in industrial control systems
IEEE Std 754-1985 (R1990), IEEE Standard for Binary Floating Point Arithmetic
JEM 1479:2002, Protocol specification – Factory automation control Link Network (FL-net)
JIS-TR B0012: 2000, Autonomous Decentralized System Network (ADS-net)
REC-xml-20001006, Extensible Markup Language (XML) 1.0 Second Edition – W3C Recommendation 6 October
REC-xmlschema-1-20010502, XML Schema Part 1: Structures – W3C Recommendation 02 May 2001
REC-xmlschema-2-20010502, XML Schema Part 2: Datatypes – W3C Recommendation 02 May 2001
RFC 768:1980, User Datagram Protocol – Internet Engineering Task Force (IETF), Request for Comments (RFC)
RFC 791:1981, Internet Protocol – Internet Engineering Task Force (IETF), Request for Comments (RFC)
RFC 793:1981, Transmission Control Protocol – Internet Engineering Task Force (IETF), Request for Comments
(RFC)
RFC 894:1984, A standard for the Transmission of IP Datagrams over Ethernet Networks – Internet Engineering
Task Force (IETF), Request for Comments (RFC)
RFC 1738:1994, Uniform Resource Locators (URL) – Internet Engineering Task Force (IETF), Request for
Comments (RFC)
RFC 1759:1995, Printer MIB – Internet Engineering Task Force (IETF), Request for Comments (RFC)
UML V1.4, OMG - Unified Modeling Language Specification (Version 1.4, September 2001)
3 Terms and definitions
NOTE The UML terminology and notation used in this document is described in Annex A of ISO 15745-1:2003.
For the purposes of this document, the terms and definitions given in ISO 15745-1 apply.
4 Abbreviated terms
AIF Application Integration Framework
AIP Application Interoperability Profile
ASCII American Standard Code for Information Interchange
CIP Common Industrial Protocol
EDS Electronic Data Sheet
IAS Industrial Automation Systems
IP Internet Protocol (see RFC 791 and RFC 894)
MAC Media Access Control
MCG MultiCast Group
CIP™ is a trade name of ControlNet International, Ltd. and Open DeviceNet Vendor Association, Inc. 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 standard does not require use of the trade name CIP™. Use of the trade name CIP™ requires
permission of either ControlNet International, Ltd. or Open DeviceNet Vendor Association, Inc.
2 © ISO 2003 – All rights reserved

OSI Open System Interconnection
TCD Transaction CoDe
TCP Transmission Control Protocol (see RFC 793)
UDP User Datagram Protocol (see RFC 768)
UML Unified Modeling Language (see UML V1.4)
XML eXtensible Markup Language (see REC-xml-20001006)

5 Technology specific elements and rules
5.1 Integration models and IAS interfaces
The AIP developer shall develop the integration model using the rules described in ISO 15745-1, and shall ensure
that the Ethernet-based device and communication network profiles (whether representing the interface
requirements or those derived from existing devices/communication networks) include the necessary IAS interfaces.
The IAS interfaces included in the profile shall be identified in the header section (see ISO 15745-1:2003, 7.2.2).
NOTE IAS interfaces are described in ISO 15745-1:2003, Annex B.
5.2 Profile templates
5.2.1 General
The Ethernet based technology specific profile templates are derived from the generic profile templates specified in
ISO 15745-1:2003, clause 7.
5.2.2 Contents and syntax
ISO 15745 specifies profile templates that are XML schemas (REC-xmlschema-1-20010502 and REC-xmlschema-
2-20010502) and use a common general structure. The device and communication network profiles based on these
templates typically contain:
 information needed to identify the connected device,
 a description of device data that can be accessed via the network,
 a description of the communication capabilities supported by the device,
 additional vendor-specific information.
However, some Ethernet-based technologies use specific legacy ASCII syntax. Hence, for backward compatibility,
template definitions of any technology (Annex A to Annex C) include all or a relevant subset of the following:
 communication network and device profile templates, as defined in ISO 15745-1,
 ISO 15745 template to encapsulate files with legacy ASCII syntax ("wrapper"),
 legacy ASCII syntax.
5.2.3 Header
The profile template header defined in ISO 15745-1:2003, 7.2.2, is used for Ethernet technology specific profile
templates. Each technology uses one or more names to identify the technology or its particular component(s) (see
Table 1). The selected name shall be stored in the ProfileTechnology attribute in the header section.
Table 1 — ProfileTechnology names
ProfileTechnology name Technology
ADS-net ADS-net
FL-net FL-net
EtherNet/IP EtherNet/IP
CIP EtherNet/IP
EDS EtherNet/IP
5.3 Technology specific profiles
The technology specific communication network profile structure and communication related aspects of device
profile structure based on Ethernet technologies are described in clause 6. The technologies included are:
 ADS-net (see 6.1)
 FL-net (see 6.2)
 EtherNet/IP (see 6.3)
The related profile template definitions are specified in Annex A to Annex C.
6 Device and communication network profiles for Ethernet-based control systems
6.1 ADS-net
6.1.1 Device profile
6.1.1.1 General
Figure 1 shows the class structure of the ADS-net device profile.

4 © ISO 2003 – All rights reserved

DeviceProfile
0.*
ApplicationProcess
DeviceIdentity
0.1
DeviceManager
1.*
DeviceFunction
Figure 1 — ADS-net device profile class diagram
—The available formats for ADS-net device profiles are described in A.2.
The XML schema representing the ADS-net device profile template is defined in A.2.3. The file name of this XML
schema shall be “ADS-net_Device_Profile.xsd”.
NOTE The ADS-net device profile class diagrams shown in Figure 1 define the main classes. These classes are further
decomposed; details are defined in Annex A.
The XML schema representing the ADS-net device profile template is defined in A.2.
6.1.1.2 Device identity
The DeviceIdentity class contains attributes that enable the unique identification of the device, and supports
services that enable retrieval of information from the device.
These attributes provide:
 manufacturer's identification (VendorName);
 device identification (ProductCode, ProductRevision, DeviceName).
6.1.1.3 Device manager
The DeviceManager class contains attributes and supports services that enable the monitoring and configuration of
the device.
These attributes provide:
 device status (DeviceState).
6.1.1.4 Device function
The DeviceFunction class contains attributes and supports services that enable the management (e.g.
configuration) of a function of the device.
These attributes provide:
 data field number (DFNO);
 logical node number (LNODENO);
 mode (MODE).
6.1.1.5 Application process
The ApplicationProcess class contains the attributes and support services that enable the communication control
among application programs executed on ADS-net.
These attributes provide:
 producer TCD list (Producer-TCD-List);
 consumer TCD list (Consumer-TCD-List);
 priority (Priority).
6.1.2 Communication network profile
6.1.2.1 General
Figure 2 shows the class structure of the ADS-net communication network profile.

CommNetworkProfile
ApplicationLayers
1.*
DataField
AliveNotification
0.1
ErrorNotification
1.*
MessageSelection
TransportLayers
1.*
UDP-IPObject
1.*
EthernetObject
0.1
NetworkManagement
1.*
Nm-Configuration
1.*
Nm-MessageSelection
1.*
Nm-Performance
1.*
Nm-Fault
Figure 2 — ADS-net communication network profile class diagram
6 © ISO 2003 – All rights reserved

The available formats for ADS-net communication network profiles are described in A.3.
The XML schema representing the ADS-net communication network profile template is defined in A.3.3. The file
name of this XML schema shall be “ADS-net_CommNet_Profile.xsd”.
6.1.2.2 Application layers
6.1.2.2.1 General
The ADS-net ApplicationLayers class represents the combined profiles for the upper 3 OSI layers of the ADS-net
communication network integration model. It states the supported application service elements and their associated
services.
Figure 3 shows the definition of the ADS-net ApplicationLayers class.

ApplicationLayers
1.* 1.*
MessageSelection
DataField
Producer-TCD-List
DFNO
Consumer-TCD-List
NETADDR
Producer-MCG-List
BCADDR
Consumer-MCG-List
NETMASK
MCG-Table
1 0.1
AliveNotification ErrorNotification
ND-Name CNT-Mode-Alive
OS-Name Mode-Alive-List
TM-Out CNT-Error
Chg-Time ERR-Name
IPADDR ERR-List
Mod-NO
ERR-NO
CNT-Option
Option-List
Figure 3 — ADS-net ApplicationLayers class diagram
6.1.2.2.2 DataField
6.1.2.2.2.1 General
ADS-net defines a domain named “data field” where subsystems share information by peer-to-peer message
passing. Each node computer transmits messages on a multicast basis to the data field it belongs to, and the other
node computers belonging to the same data field can receive the data autonomously. Multiple computers belong to
a data field to send or receive data. Multicast group (MCG), a group of node computers belonging to the data field,
is also introduced to localize the multicast.
DataField defines properties used to control a data field. DataField attributes provide in particular:
— data field number (DFNO);
— multicast group table (MCG-Table).
6.1.2.2.2.2 AliveNotification
A “keep alive” message is transmitted to the data field periodically to notify the status of the sender node computer
to the other node computers.
AliveNotification defines the properties used to check the status of node computers. AliveNotification attributes
provide in particular:
 node name (ND-Name);
— time out (TM-Out).
6.1.2.2.2.3 ErrorNotification
When a fault occurs in a node computer, the fault information is included in the “keep alive” message that is
transmitted to the data field during a “keep alive” message transmission cycle. Any node computer belonging to the
same data field can detect the fault (error) status.
ErrorNotification defines properties describing this fault information. ErrorNotification attributes provide in particular:
 error name (ERR-Name);
— error list (ERR-List).
6.1.2.2.3 MessageSelection
TCD is an identifier of a message defined uniquely in a data field. The transmitter sends a TCD-assigned message
to a specified data field on a multicast basis, while each node computer belonging to the same data field
autonomously selects only the relevant messages based on their TCD.
MessageSelection defines properties used for this message exchange. MessageSelection attributes provide in
particular:
 producer TCD list (Producer-TCD-List);
 consumer TCD list (Consumer-TCD-List);
— producer MCG list (Producer-MCG-List);
— consumer MCG list (Consumer-MCG-List).
6.1.2.3 Transport layers
6.1.2.3.1 General
The ADS-net TransportLayers class represents the combined profiles for the lower 4 OSI layers of the
communication network integration model. The TransportLayers class is divided into one or more Ethernet based
objects and a UDP/IP object.
8 © ISO 2003 – All rights reserved

6.1.2.3.2 EthernetObject
EthernetObject defines properties of Ethernet used to implement ADS-net. EthernetObject attributes provide:
— media type (MediaType);
— communication rate (CommRate);
— indicators (Indicators);
— MAC address (MACAddress);
— error log (ErrorLog).
6.1.2.3.3 UDP-IPObject
UDP-IPObject defines properties of UDP/IP used to implement ADS-net. UDP-IPObject attributes provide.
— IP address (IPADDR);
— multicast group information (UDP-IP-MCGs);
—
host name (HostName);
— error log (ErrorLog).
6.1.2.4 Network management
6.1.2.4.1 General
The ADS-net NetworkManagement class represents the network configuration and performance adjustment
capabilities of the ADS-net communication network integration model.
It is further divided into several classes, as shown in Figure 2.
6.1.2.4.2 Nm-Configuration
6.1.2.4.2.1 General
Nm-Configuration defines properties of network configuration related to ADS-net. Nm-Configuration attributes
provide in particular:
 active data field number list (ActiveDataFieldNoList);
 active node number list (ActiveNodeNoList);
 active multicast group number list (ActiveMulticastGroupNoList).
6.1.2.4.2.2 Nm-MessageSelection
Nm-MessageSelection defines properties used for the management of message selection. Nm-MessageSelection
attributes provide in particular:
— active producer TCD supported list (ActiveProducerTCDSupportedList);
— active consumer TCD supported list (ActiveConsumerTCDSupportedList).
6.1.2.4.2.3 Nm-Performance
Nm-Performance defines properties used for performance monitoring. Nm-Performance attributes provide:
 number of messages exchanged (MessageTransaction).
6.1.2.4.3 Nm-Fault
Nm-Fault defines properties used for fault monitoring. Nm-Fault attributes provide in particular:
 fault node list (FaultNodeList).
6.2 FL-net
6.2.1 Device profile
6.2.1.1 General
Figure 4 shows the class structure of the FL-net device profile.

DeviceProfile
0.*
ApplicationProcess
DeviceIdentity
DeviceManager
1.*
DeviceFunction
Figure 4 — FL-net device profile class diagram
The available formats for FL-net device profiles are described in B.1.
The XML schema representing the FL-net device profiles template is defined in B.1.5. The file name of this XML
schema shall be “FL-net_Device_Profile.xsd”.
NOTE 1 The FL-net device profile class diagrams shown in Figure 4 define the main classes. Some classes are further
decomposed; details are defined in Annex B.
NOTE 2 All these classes are mapped to the same XML schema defined in B.1.5.
6.2.1.2 Device identity
The DeviceIdentity class is defined in Figure 5, and the sub-classes are described in Table 2.

10 © ISO 2003 – All rights reserved

DeviceIdentity
VendorCode
ProductName
0.1
DeviceType 1
ProductCode
ProductRevision
Figure 5 — FL-net DeviceIdentity class diagram
Table 2 — Elements of DeviceIdentity object
Class elements Description
VendorCode Code of the manufacturer or vendor of the device
ProductName Vendor specific name of the product
ProductCode Unique ID, identifying the product. The format is at the vendor’s discretion
ProductRevision Vendor specific revision number of the product
DeviceType FL-net specific Device type (see Table B.1)

6.2.1.3 Device manager
6.2.1.3.1 General
Figure 6 shows the class structure of the DeviceManager object.

DeviceManager
CommuServiceManager
DeviceIDSpecRev
0.1
DeviceState
Figure 6 — FL-net DeviceManager class diagram
6.2.1.3.2 DeviceIDSpecRev
The DeviceIDSpecRev object shall describe the revision of FL-net identity object.
6.2.1.3.3 CommuServiceManager
The CommuServiceManager object shall describe the communication service, which is responsible for monitoring
and configuration.
6.2.1.3.4 DeviceState
The DeviceState object shall describe the states of the device.
6.2.1.4 Device function
The DeviceFunction object contains attributes and supports services that enable the management (e.g.
configuration) of a function of the device.
NOTE The device function class is not defined in ISO 15745-4.
6.2.1.5 Application process
The ApplicationProcess object contains attributes and supports services that correspond to the application
requirement.
These attributes provide in particular:
— plant name (PlantName).
To allow specific representation of the application process, additional sub-classes and additional attributes may be
defined to describe the application process.
6.2.2 Communication network profile
6.2.2.1 General
Figure 7 shows the class structure of the FL-net communication network profile.
12 © ISO 2003 – All rights reserved

CommNetworkProfile
1 1
ApplicationLayers NetworkManagement
1.* 1.*
ComMemoryInterface Configuration
1.* 1.*
MessageService ServiceSelection
0.1 1.*
ErrorNotification PerformanceManager
1 1.*
TransportLayers FaultManager
1.*
UDP-IPObject
1.*
EthernetBasedObject
Figure 7 — FL-net communication network profile class diagram
The available formats for FL-net communication network profiles are described in B.2.
The XML schema representing the FL-net communication network profile template is defined in B.2.4.5. The file
name of this XML schema shall be “FL-net_CommNet_Profile.xsd”.
6.2.2.2 ApplicationLayers
6.2.2.2.1 General
The FL-net ApplicationLayers class represents the combined profiles for the upper 3 OSI layers of the FL-net
communication network integration model. It states the supported application service elements and their associated
services.
It is further divided into several classes, as shown in Figure 7.
NOTE The ApplicationLayers object is fully specified in JEM 1479:2002.
6.2.2.2.2 ComMemoryInterface
The ComMemoryInterface object defines the properties associated with common memory interface. The elements
of the ComMemoryInterface object are specified in B.2.2.1.
6.2.2.2.3 MessageService
The MessageService object defines the properties associated with message services in the device. The elements
of the MessageService object are specified in B.2.2.2.
6.2.2.2.4 ErrorNotification
The ErrorNotification object defines the properties associated with error items related to the network and the device.
The elements of the ErrorNotification object are specified in B.2.2.3.
6.2.2.3 TransportLayers
6.2.2.3.1 General
The FL-net TransportLayers class represents the combined profiles for the lower 4 OSI layers of the FL-net
communication network integration model.
It is further divided into several classes, as shown in Figure 7.
6.2.2.3.2 EthernetBasedObject
The EthernetBasedObject object defines the properties associated with physical layer of FL-net. The elements of
the EthernetBasedObject object are specified in B.2.3.1.
6.2.2.3.3 UDP-IPObject
The UDP-IPObject object defines the properties associated with data link layer configuration and monitoring. The
elements of the UDP-IPObject object are specified in B.2.3.2.
6.2.2.4 NetworkManagement
6.2.2.4.1 General
The FL-net NetworkManagement class represents the network configuration and performance adjustment
capabilities of the FL-net communication network integration model.
It is further divided into several classes, as shown in Figure 7.
NOTE The NetworkManagement object is fully specified in JEM 1479:2002.
6.2.2.4.2 Configuration
The Configuration object defines the properties associated with the initial set-up and modification of the
configuration. The elements of the Configuration object are specified in B.2.4.1.
6.2.2.4.3 ServiceSelection
The ServiceSelection object defines the properties associated with network communication services. The elements
of the ServiceSelection object are specified in B.2.4.2.
6.2.2.4.4 PerformanceManager
The PerformanceManager object defines the properties associated with performance of data exchange in the
network. The elements of the PerfomanceManager object are specified in B.2.4.3.
14 © ISO 2003 – All rights reserved

6.2.2.4.5 FaultManager
The FaultManager object defines the properties associated with fault items of FL-net. The elements of the
FaultManager object are specified in B.2.4.4.
6.3 EtherNet/IP
6.3.1 Device profile
6.3.1.1 General
Figure 8 shows the class structure of the EtherNet/IP device profile.
DeviceProfile
DeviceIdentity
ApplicationProcess
0.*
DeviceManager
0.1
Assembly
0.*
Parameter
DeviceFunction
1.* 0.*
ParameterGroup
0.*
Figure 8 — EtherNet/IP device profile class diagram
The available formats for EtherNet/IP device profiles are described in C.2.
The XML schema representing the EtherNet/IP device profile template is defined in C.2.1.3.3. The file name of this
XML schema shall be “CIP_Device_Profile.xsd”.
NOTE The EtherNet/IP device profile class diagram shown in Figure 8 defines the main classes. These classes are further
decomposed; details are defined in Annex C.
The XML schema representing the encapsulation of a legacy EtherNet/IP EDS into the ISO 15745 device profile
template is defined in C.2.2.2. The file name of this XML schema shall be “EDS_Device_Profile_wrapper.xsd”. The
legacy EDS ASCII syntax itself is described in C.4.
6.3.1.2 Device identity
The DeviceIdentity class contains attributes which uniquely identify the device, and supports services which allow
the retrieval of this information from the device.
These attributes provide in particular:

manufacturer's identification (name and identification code);
 device identification (device type, product name, revision, serial number);
 device classification;
 location of storage of additional information (e.g. icons).
6.3.1.3 Device manager
The DeviceManager class contains attributes and supports services used to monitor and configure the device.
These attributes provide in particular:
 revision of the EtherNet/IP identity object;
 information on device structure (for devices integrated in a modular system).
Services allow:
 device reset;
 retrieval of DeviceManager attributes.
6.3.1.4 Device function
The DeviceFunction class contains attributes and supports services which enable the management (e.g.
configuration) of a function of the device.
EXAMPLE Examples of DeviceFunction objects are Overload, Presence Sensing, Analogue Input, and Discrete Output
objects.
NOTE The DeviceFunction class is not defined in ISO 15745-4.
6.3.1.5 Application process
Figure 9 shows the class structure of the ApplicationProcess class.
ApplicationProcess
0.1
0.1 0.1
Assembly Parameter ParameterGroup
AssemblyClass ParameterClass Group
0.1 0.1 0.*
AssemblyInstance ParameterInstance
0.1 0.1
Assem Param
0.* 0.*
Figure 9 — EtherNet/IP ApplicationProcess class diagram
The Assembly class assembles several application process data items into a single block for optimisation of
communications. The Parameter class provides a standardized interface for accessing individual application
process data items. The ParameterGroup class specifies groups of related parameters for a specific purpose (e.g.
configuration, monitoring).
16 © ISO 2003 – All rights reserved

The Assembly class and the Parameter class support attributes and services both at the class and instance levels.
The Assem, Param and Group classes specify individual instances of the main classes.
NOTE The Assembly class and the Parameter class correspond to the EtherNet/IP Assembly object and Parameter
objects. The Assembly object is fully specified in IEC 61158-5:2003 and IEC 61158-6:2003 (Type 2).
6.3.2 Communication network profile
6.3.2.1 General
Figure 10 shows the class structure of the EtherNet/IP communication network profile.
CommNetworkProfile
1 0.1
ApplicationLayers TransportLayers NetworkManagement
0.1
NM-EtherNetIPLinkObject
0.1
ConnectionManager ENPhysicalLayer
0.1
1 NM-TCPIPInterfaceObject
0.1
MessageRouter EtherNetIPLinkObject
0.1
NM-ConnectionManager
0.1
TCPIPInterfaceObject
0.1
NM-MessageRouter
0.1
EncapsulationProtocol
0.1
Ports
Figure 10 — EtherNet/IP communication network profile class diagram
The available formats for EtherNet/IP communication network profiles are described in C.3.
The XML schema representing the EtherNet/IP communication network profile template is defined in C.3.1.3. The
file name of this XML schema shall be “ENet_CommNet_Profile.xsd”.
The XML schema representing the encapsulation of a legacy EtherNet/IP EDS into the ISO 15745 communication
network profile template is defined in C.3.2.2. The file name of this XML schema shall be
“EDS_CommNet_Profile_wrapper.xsd”. The legacy EDS ASCII syntax itself is described in C.4.
6.3.2.2 Application layers
The EtherNet/IP ApplicationLayers class represents the combined profiles for the upper 3 OSI layers of the
EtherNet/IP communication network integration model.
It is further divided into several classes, as shown in Figure 10:
 ConnectionManager defines the properties associated with connections and connection management;
 MessageRouter defines the properties associated with internal message routing in the device.
NOTE The correspo
...