ISO 18435-3:2015
(Main)Industrial automation systems and integration — Diagnostics, capability assessment and maintenance applications integration — Part 3: Applications integration description method
Industrial automation systems and integration — Diagnostics, capability assessment and maintenance applications integration — Part 3: Applications integration description method
ISO 18435-3:2015 defines the profiling methodology to use the interoperability templates of ISO 18435‑2. These profiling methods describe the construction and the use of application domain matrix elements (ADMEs), application interaction matrix elements (AIMEs), and an open technical dictionary (OTD) to support the information exchange. In particular, ISO 18435-3:2015 gives guidance related to profiling the information exchange between two applications by establishing the context, conveyance, and contents defined in ISO 18435‑2. ISO 18435-3:2015 is intended to be used in conjunction with ISO 18435‑1 and ISO 18435‑2.
Systèmes d'automatisation industrielle et intégration — Diagnostics, évaluation des moyens et intégration des applications de maintenance — Partie 3: Méthode de description pour l'intégration d'applications
General Information
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 18435-3
First edition
2015-08-01
Industrial automation systems and
integration — Diagnostics, capability
assessment and maintenance
applications integration —
Part 3:
Applications integration description
method
Systèmes d’automatisation industrielle et intégration — Diagnostics,
évaluation des moyens et intégration des applications de
maintenance —
Partie 3: Méthode de description pour l’intégration d’applications
Reference number
ISO 18435-3:2015(E)
©
ISO 2015
---------------------- Page: 1 ----------------------
ISO 18435-3:2015(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2015 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 18435-3:2015(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative reference(s) . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Applications integration description methods . 2
5.1 Introduction to the application integration concept . 2
5.1.1 General. 2
5.1.2 Inter-domain requirements . 4
5.1.3 Intra-domain requirements . 5
5.2 Profiling concept . 6
5.2.1 General. 6
5.2.2 Intra-domain information exchange compatibility . 6
5.2.3 Inter-domain information exchange compatibility . 7
5.3 Basic interoperability requirements for information exchange . 8
5.4 Procedure for the construction of AIMEs and ADMEs . 8
5.4.1 General. 8
5.4.2 Application interoperability requirements .10
5.4.3 Specify content section .11
5.4.4 Specify resource and conveyance requirements .11
5.5 AIME requirements .11
5.5.1 General.11
5.5.2 AIME detailed requirements .11
5.6 Construction of the ADME .12
5.6.1 General.12
5.6.2 Technical dictionary selection .12
5.6.3 Application framework selection .12
5.6.4 Contents section .12
6 Compliance .12
Annex A (normative) Ontology in AIME/ADME .13
Annex B (informative) Smart Pump Information exchange example .20
Annex C (informative) Jam detection example .28
Annex D (informative) EtherNet/IP to OPC Information Exchange .33
Bibliography .38
© ISO 2015 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 18435-3:2015(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.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
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. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical
Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is Technical Committee ISO/TC 184, Industrial automation
systems and integration, Subcommittee SC 5, Architecture, communication and integration frameworks.
ISO 18435 consists of the following parts, under the general title Industrial automation systems and
integration — Diagnostics, capability assessment, and maintenance applications integration:
— Part 1: Overview and general requirements
— Part 2: Descriptions and definitions of application domain matrix elements
— Part 3: Applications integration description method
iv © ISO 2015 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 18435-3:2015(E)
Introduction
ISO 18435 defines a set of integration methods intended to be used when integrating diagnostics,
capability assessment, and maintenance applications with the applications in production, control, and
other manufacturing operations.
ISO 18435-1 provides an overview of the elements as shown in Figure 1 and the rules of a method to
describe an automation application’s integration requirements. The elements include the key aspects
when integrating an automation application with other applications and the relationships of these key
aspects. The rules include the information exchanges to support interoperability within an application
and between applications.
ISO 18435-2 provides the detailed definitions of the Application Interaction Matrix Element (AIME) and
Application Domain Matrix Element (ADME) structures and their relationships. In particular, the steps
for constructing an ADME from a set of AIMEs are described.
This part of ISO 18435 defines a recommended method based on templates to describe the
interoperability between applications in two or more automation domains within an enterprise, at all
levels of an enterprise’s functional and resource hierarchies. The focus is on the production operations
and maintenance operations domains.
Figure 1 — Relationships between the parts of ISO 18435
UML is used to represent information exchange requirements associated with the interoperability and
the integration of plant floor applications, in particular, diagnostics, control, maintenance and production.
The purpose is to focus on how to express the information exchanges:
— about the process, equipment, operators, and materials and other automation assets;
— that are conveyed from control and production systems to various diagnostics and maintenance
systems in order to perform asset management.
The intended benefits for representing information exchanges are to:
— facilitate specifying and procuring open systems that support interoperability among diagnostics
and maintenance applications;
© ISO 2015 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO 18435-3:2015(E)
— reduce the time to develop diagnostics and maintenance solutions that directly address the well-
defined integration requirements;
— provide a means to categorize tools intended to enable and verify interoperability and integration
across applications.
vi © ISO 2015 – All rights reserved
---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO 18435-3:2015(E)
Industrial automation systems and integration —
Diagnostics, capability assessment and maintenance
applications integration —
Part 3:
Applications integration description method
1 Scope
This part of ISO 18435 defines the profiling methodology to use the interoperability templates of
ISO 18435-2. These profiling methods describe the construction and the use of application domain
matrix elements (ADMEs), application interaction matrix elements (AIMEs), and an open technical
dictionary (OTD) to support the information exchange.
In particular, this part of ISO 18435 gives guidance related to profiling the information exchange
between two applications by establishing the context, conveyance, and contents defined in ISO 18435-2.
This part of ISO 18435 is intended to be used in conjunction with ISO 18435-1 and ISO 18435-2.
2 Normative reference(s)
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO 8000 (all parts), Data quality
ISO/IEC 10646, Information technology — Universal Coded Character Set (UCS)
ISO 15745-1, Industrial automation systems and integration — Open systems application integration
framework — Part 1: Generic reference description
ISO 18435-1:2009, Industrial automation systems and integration — Diagnostics, capability assessment
and maintenance applications integration — Part 1: Overview and general requirements
ISO 18435-2:2012, Industrial automation systems and integration — Diagnostics, capability assessment
and maintenance applications integration — Part 2: Descriptions and definitions of application domain
matrix elements
ISO/TS 29002 (all parts), Industrial automation systems and integration — Exchange of characteristic data
ISO/TS 29002-5:2009, Industrial automation systems and integration — Exchange of characteristic
data — Part 5: Identification scheme
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 18435-1 and ISO 18435-2 and
the following apply.
© ISO 2015 – All rights reserved 1
---------------------- Page: 7 ----------------------
ISO 18435-3:2015(E)
3.1
ontology
explicit and consensual specification of concepts of an application domain independent of any use of
these concepts
[SOURCE: ISO 13584-511:2006, 3.1.20]
4 Abbreviated terms
ADME Application Domain Matrix Element
AIME Application Integration Matrix Element
CBM Condition-Based Maintenance
OTD Open Technical Dictionary
UML Unified Modelling Language
XML eXtensible Markup Language
5 Applications integration description methods
5.1 Introduction to the application integration concept
5.1.1 General
The customer applications integration requirements determine the information exchange profiles
that are needed to support the application interoperability requirements. To develop the information
exchange profiles for the applications of interest, it is necessary to determine the existing customer
domain areas of interest.
Clause 5 describes the method for specifying the information contained in the AIME and the ADME for
the information exchange requirements using templates defined in ISO 18435-2. The use of this method
will provide interoperability for the applications in the defined context. As this methodology is used
for integrating additional applications from various domains, this method can be used for verifying if
the information exchange profiles (using the AIME structure) are interoperable as needed by the user.
Figure 2 shows an iterative process to verify the intended interoperability of the application integration.
2 © ISO 2015 – All rights reserved
---------------------- Page: 8 ----------------------
ISO 18435-3:2015(E)
Figure 2 — System design cycle for interoperability
The general structure for the application information exchange profiles are depicted in Figure 3. The
methods for assessing the AIME profile compatibility to support the information exchanges will depend
upon the context and domains of interest.
Figure 3 — Profile elements
The diagnostic and maintenance mission depends on the objectives of integration between different
application domains as shown in Figure 4. The description of this technical mission shall include the
identification of the associated assets for which the mission is defined and the application domains
involved.
The method for describing the information exchange profiles is dependent upon the context established
according to intra- or inter-domain information exchanges. The capability profiles of the resources to
support the information exchange shall be described by the AIME.
NOTE The information exchanges between the allocated resource and definition resources can be described
with a sequence diagram according to ISO 18435-2:2012, 5.2.
Application domain categories are defined in ISO 18435-1 as shown in Figure 4. In this part of ISO 18435,
interoperability templates are described for integration requirements as depicted in ISO 18435-1 for
the interoperability of applications.
© ISO 2015 – All rights reserved 3
---------------------- Page: 9 ----------------------
ISO 18435-3:2015(E)
As an illustration of the methodology using interoperability templates, the diagnostic and control
application domains are used as shown in Figure 4.
Figure 4 — Categories of application domains
5.1.2 Inter-domain requirements
Interoperability templates for inter-domain application interoperability shall require references to
either a specific domain standard or the profile of a specific domain standard, according to ISO 15745,
to specify the context of the integration model.
EXAMPLE 1 As shown in Figure 5, the application in the control application domain could use the IEC 61512
reference model to describe the model construction, terms, and definition used in the interoperability templates
for the ADME. The application in the diagnostic application domain could use the ISO 13374-2 reference model to
describe the corresponding diagnostic ADME.
Thus, when exchanging information between different domains, it is necessary to indicate the context
and then to describe the content information handled by the conveyance mechanism. The context,
conveyance and content information are contained in the ADME using profile specifications. The actual
contents of the information exchange shall be defined by profile specifications.
EXAMPLE 2 An ISO 13374 diagnostic information message, advisory generation, is sent from the diagnostic
application as an event to the IEC 61512 batch control application.
4 © ISO 2015 – All rights reserved
---------------------- Page: 10 ----------------------
ISO 18435-3:2015(E)
Figure 5 — Inter-domain applications interoperability
The terms and definitions of the information models shall reference standards. The terminology and
models of the standards shall be identified and referenced using open technical dictionary (OTD)
concepts. In this part of ISO 18435, the information models and terminology use concepts of an open
technical dictionary as defined in ISO/TS 29002 (see Annex A). The use of a common set of models and
terms for applications in different domains establishes the basis for enabling information exchange.
This applications integration methodology enables the mapping of the inter-domain interoperability
requirements into the AIMEs for each application of interest and the ADMEs between applications.
5.1.3 Intra-domain requirements
Intra-domain application interoperability templates shall use a common context for the applications
information exchange reference model.
EXAMPLE As shown in Figure 6, the control applications and the diagnostic applications have the same
context for the information exchange such that the representation, terms, definitions have the same structure
and meaning. The conveyance and the content sections follow the syntax and semantics of IEC 61512.
Figure 6 — Intra-domain applications interoperability
© ISO 2015 – All rights reserved 5
---------------------- Page: 11 ----------------------
ISO 18435-3:2015(E)
5.2 Profiling concept
5.2.1 General
The general profiling concept is depicted in Figure 7. In ISO 18435-2, the general templates for context,
conveyance, and contents are specified. The template information for intra-domain information
exchange profiles is the information directly from the reference domain standards. For the inter-domain
profiles, the open technical dictionaries (OTDs) will need to be referenced to ensure compatibility
of terms and definitions for the information exchange information. The OTDs shall contain profiling
information for the referenced domains using the methodology of ISO 15745-1; the inter-domain
information exchange may require mapping concepts from two technical dictionaries.
Figure 7 — Profile aggregation
The AIME defines the capability profile to support the information exchange requirements of the
ADME. The capability profiles for intra-domain applications are by definition compatible. For instance
the device profile and communication profiles conform to a common set of specifications.
Devices can be selected and their relevant properties can be identified and referenced by using
component data dictionary such as IEC 61360 [Common Data Dictionary (CDD)]. Device class
identification codes and property identification codes can be used to refer to generic components
characteristics.
NOTE Descriptions of switchgear and controlgear classes are given by IEC 62683 and descriptions of process
equipment are given by IEC 61987.
The capability profiles for inter-domain applications can conform to different device and
communications profiles. The application information exchange profile defines the preferred context
and conveyance profiles to support the information exchange. The capability profiles defined in the
AIMEs shall be checked to verify compatibility. Since the context is specified as a profile referencing a
profile, multiple levels of profile checking are required.
5.2.2 Intra-domain information exchange compatibility
The intra-domain information exchange shall use the same context and conveyance profiles as shown in
Figure 8. For intra-domain information exchange, this reduces the complexity in the selection process
for resource profiles.
6 © ISO 2015 – All rights reserved
---------------------- Page: 12 ----------------------
ISO 18435-3:2015(E)
Figure 8 — Intra-domain information exchange
5.2.3 Inter-domain information exchange compatibility
The inter-domain information exchange requires additional compatibility checking to select the
appropriate resource profiles for the information exchange. The contexts shall be distinguished by
referencing the domains according to ISO 18435-1. The context shall reference a set of definitions
specified by an open technical dictionary. If the contexts use different open technical dictionaries,
the selection of the appropriate entries from each open technical dictionary shall be identified and a
common context established.
The selected resources in each domain shall be checked to provide the conveyance required by the
ADME as shown in Figure 9. Each resource (e.g. device, communications, equipment, software) shall
provide the requisite capabilities defined by the conveyance specification.
© ISO 2015 – All rights reserved 7
---------------------- Page: 13 ----------------------
ISO 18435-3:2015(E)
Figure 9 — Inter-domain exchange
5.3 Basic interoperability requirements for information exchange
The information to be exchanged shall be:
— Defined according to an open technical dictionary
— All information shall use concepts defined in an open technical dictionary. The open technical
dictionary shall meet the requirements of ISO/TS 29002.
NOTE 1 ISO/TS 29002 provides a basic set of requirements for open technical dictionaries. By use of
ISO/TS 29002, a mapping of different contexts is possible.
— Associated with a context by referencing the application domain integration diagram.
EXAMPLE Categories of domains are shown in Figure 4.
— Based on a publicly available information model
NOTE 2 The information may be profiled using the information model; i.e. the characteristic data in the
information exchange may be referenced to a publically available standard.
NOTE 3 The information model should indicate the purpose and use of the information exchange, such as
whether the information exchange is for design, operational, and/or maintenance purposes.
— Based on ISO 8000 data quality standards; the relevant parts shall be specified.
NOTE 4 The information to be exchanged has a formal specification with a syntax that can be checked by a
computer to verify that it meets the master data specification.
NOTE 5 ISO 8000-120 provides requirements for data provenance and provenance record; i.e. the history of
the data and information about the owner of the information (e.g. traceable for time and location). The traceability
can be realized by using the conveyance section of the ADME.
5.4 Procedure for the construction of AIMEs and ADMEs
5.4.1 General
The general concept and a procedure for construction of AIMEs and ADMEs is shown in the example of
Figure 10. The order of the tasks is only shown for illustration.
EXAMPLE 1 A procedure for the construction of AIMEs and ADMEs is shown in Figure 10 below.
8 © ISO 2015 – All rights reserved
---------------------- Page: 14 ----------------------
ISO 18435-3:2015(E)
Figure 10 — Procedure example
The procedure shall perform the following steps:
— Determine the application interoperability requirements for the information exchange
— Specify content section for information exchange using common information model
— Specify resource capabilities and conveyance sections using the rules of the selected application
integration framework.
— Define the identifiers for the AIMEs and ADMEs references as specified in Annex A.
NOTE The conveyance mechanism between the source and destination application must utilise the same
communication service; e.g. when those applications have a common information model of the content but not for
the conveyance, then one application needs to be adapted to send information.
© ISO 2015 – All rights reserved 9
---------------------- Page: 15 ----------------------
ISO 18435-3:2015(E)
EXAMPLE 2 When the conveyance is described in WSDL and uses web service, then the source application will
need to develop the necessary set of capabilities to serve the destination requirements. Alternatively the supplier
can propose to exchange the information using a “fieldbus” standard. The conveyance mechanism would be one
of the fieldbus services.
5.4.2 Application interoperability requirements
5.4.2.1 General
The minimum criteria for interoperability are given in ISO 18435-1:2009, 5.3.
The requirements for interoperability within a common context are defined with respect to
customer/supplier perspective or needs, e.g. using a particular field bus standard (IEC 61784), a
particular device model (ISO 15745-3), a particular application standards (IEC 61512), or using a
particular interface (ISO 13374-2). The aim is to use a common set of vocabulary already defined.
The interoperability will be enabled by completing the actions described in the following sub-clauses.
5.4.2.2 Identify candidate applications and their domain
The candidate applications shall be identified and shall be assigned to their associated domain(s) in
accordance with ISO 18435-1:2009, 5.4. The domain(s) involved within the information exchanges shall
be determined.
EXAMPLE Using ISO 18435-2:2012, Annex B, the Robot Monitoring application is assigned to domain
category identifier, D1.2, and the Robot Control application is assigned to D1.1.
NOTE The domain category identifier, e.g. D1.2 (see ISO 18435-1:2009, 5.4.8), is used to build the AIME.
5.4.2.3 Identify processes
The AIME process profiles (see ISO 18435-2:2012, 6.2.3) of the candidate applications shall be identified.
EXAMPLE 1 Using ISO 18435-2:2012, Annex B, the Robot Monitoring application is associated with the process
RobotConditionMonitoring and the Robot Control application is associated with the process MotionControl.
The AIME common resource profile (see ISO 18435-2:2012, 6.2.3) shall be identified.
EXAMPLE 2 Using ISO 18435-2:2012, Annex B, the Robot Monitoring application is associated with the
resource PLC and the Robot Control application is associated resources PLC, servo drive, and vibration monitor.
5.4.2.4 Select/create information models
The terms and definitions of the information models shall reference standards. The use of a common
set of models and terms for applications in different domains establishes the basis for enabling
information exchange.
EXAMPLE Using ISO 18435-2:2012, Annex B, the Robot Monitoring application is associated with the
industry speci
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.