ISO/TR 18161:2013

Automation systems and integration - Applications integration approach using information exchange requirements modelling and software capability profiling

ISO/TR 18161:2013 describes an approach for using ISO 16100 and ISO 18435 to specify information exchange requirements between applications. This approach is based on the use of ISO 18435 application integration matrix element (AIME)/application domain matrix element (ADME) templates in conjunction with ISO 16100 manufacturing software unit (MSU) capability profiles. ISO/TR 18161:2013 also provides an example approach as applied to describing the interoperability requirements of the integrated smart pump application, which comprises the pump control application and the pump diagnostics application.

Systèmes d'automatisation et intégration — Approche d'intégration des applications utilisant des exigences d'échange d'informations de modelage et un logiciel de capacité de profilage

General Information

• Status: Published
• Publication Date: 02-Jul-2013
• ICS: 25.040.01 - Industrial automation systems in general
• Technical Committee: ISO/TC 184/SC 5 - Interoperability, integration, and architectures for enterprise systems and automation applications
• Drafting Committee: ISO/TC 184/SC 5/WG 4 - Manufacturing software and its environment
• Parallel Committee: ISO/TC 184/SC 4 - Industrial data
• Current Stage: 6060 - International Standard published
• Start Date: 03-Jul-2013
• Completion Date: 13-Dec-2025

Overview - ISO/TR 18161:2013 applications integration and profiling

ISO/TR 18161:2013 describes an approach for specifying information exchange requirements between applications in industrial automation. It combines information-exchange modelling from ISO 18435 with manufacturing software capability profiling from ISO 16100 to define interoperable application interfaces. The Technical Report includes templates (AIME/ADME) and MSU (Manufacturing Software Unit) capability profiles and illustrates the method with a smart pump example (pump control + pump diagnostics).

Key topics and technical requirements

• Information exchange requirements modelling
  • Use of ISO 18435 elements to model the information exchanged among applications and resources.
  • Construction of Application Interaction Matrix Elements (AIME) and Application Domain Matrix Elements (ADME) to represent required interfaces and interoperability relationships.
• Software capability profiling
  • Use of ISO 16100 manufacturing software unit (MSU) capability profiles to describe software functionality and behavior for integration and lifecycle use.
  • Capability templates and capability class structures (CCS) to organize profile content.
• Application Integration Framework (AIF)
  • Alignment with ISO 15745 application integration modelling to identify key interoperability interfaces and create Application Interoperability Profiles (AIP).
• Practical modelling guidance
  • Context definition from manufacturing domain models (MDM) and manufacturing domain data (MDD).
  • Example procedures and annexes in the report that show constructing AIMEs/ADMEs and MSU profiles (smart pump use case).
• Goal
  • Provide a repeatable, standardized approach for specifying what information needs to be exchanged, how software components must behave, and which capabilities support those exchanges.

Applications and who should use it

• System integrators and automation engineers - to define clear application boundaries and interoperability requirements when integrating control, diagnostics, maintenance or prognostics applications.
• Software vendors and OEMs - to publish MSU capability profiles that enable profile matching and ease integration into customer architectures.
• Plant architects and solution designers - to reduce vendor-specific solutions and support modular system design using standardized AIME/ADME templates.
• Maintenance and lifecycle managers - to ensure diagnostic and prognostic applications interoperate reliably with control systems (illustrated by the smart pump example).

Practical benefits

• Improved clarity of information exchanges and responsibilities between applications
• Easier profile matching and reduced integration cost
• Support for modular, vendor-agnostic architectures and lifecycle reuse of application software

Related standards

• ISO 16100 series (MSU capability profiling; Parts 3 and 5 referenced)
• ISO 18435 (application integration elements; Part 2 referenced; Part 1 overview)
• ISO 15745 (application integration framework and AIP notation)

Keywords: ISO/TR 18161:2013, applications integration, information exchange requirements, software capability profiling, AIME, ADME, MSU capability profiles, application interoperability, smart pump.

Standards Content (Sample)

TECHNICAL ISO/TR
REPORT 18161
First edition
2013-07-01
Automation systems and
integration — Applications integration
approach using information exchange
requirements modelling and software
capability profiling
Systèmes d’automatisation et intégration — Approche d’intégration
des applications utilisant des exigences d’échange d’informations de
modelage et un logiciel de capacité de profilage
Reference number
©
ISO 2013
© ISO 2013
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
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO 2013 – All rights reserved

Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 3
5 Applications interoperability requirements modelling . 3
5.1 Application integration framework in ISO 15745 and ISO 18435 . 3
5.2 Elements of information exchanges in ISO 18435 . 4
5.3 Context for information exchange requirements . 5
5.4 Content for information exchange requirements. 6
5.5 Conveyance for information exchange . 7
5.6 ADME for the smart pump application . 7
6 Approach for smart pump application interoperability . 8
6.1 Smart pump system information model . 8
6.2 Resolving ambiguity using OTD . 8
6.3 Application integration using ISO 18435 . 9
7 Constructing AIME and ADME for smart pump application . 9
7.1 Overview . 9
7.2 AIME for pump control application . 9
7.3 AIME for pump diagnostics application .10
7.4 ADME for the integrated smart pump application .10
8 General procedures for achieving application integration .10
Annex A (informative) Modelling smart pump application .12
Annex B (informative) Capability profiling templates of application software units .14
Annex C (informative) Application software unit capability profiles .30
Annex D (informative) AIME and ADME in smart pump application
...............................................................................34
Bibliography .40
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. 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. 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.
The committee responsible for this document is Technical Committee ISO/TC 184, Automation systems
and integration, Subcommittee SC 5, Architecture, communication and integration frameworks.
iv © ISO 2013 – All rights reserved

Introduction
The motivation for ISO 16100 stems from the industrial and economic environment, in particular:
a) a growing base of vendor-specific solutions;
b) user difficulties in applying standards;
c) the need to move to modular sets of system integration tools;
d) the recognition that application software and the expertise to apply that software are assets of
the enterprise.
ISO 16100 is an International Standard for the computer-interpretable and human readable
representation of a capability profile. Its goal is to provide a method to represent the capability of
manufacturing application software relative to its role throughout the life cycle of a manufacturing
application, independent of a particular system architecture or implementation platform. This can
lead to reduced production and information management costs to users and vendors/suppliers of
manufacturing applications.
ISO 18435 provides a framework for harmonized use of industry and international standards in order
to integrate control, diagnostics, prognostics, capability assessment, and maintenance applications. By
using an ISO 15745 application integration modelling approach, key interoperability interfaces can be
identified and concisely documented in terms of profiles.
ISO 18435 also provides the elements and the rules to describe the integration requirements of
an automation application. 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.
This Technical Report describes a use case of modelling the smart pump application described in
Annex A. The detailed manufacturing software unit profiling templates are described in Annex B. The
detailed manufacturing software unit profiles are described in Annex C. The information exchanged
among manufacturing software units in the smart pump application based on ISO 18435 methodology
is described in Annex D.
TECHNICAL REPORT ISO/TR 18161:2013(E)
Automation systems and integration — Applications
integration approach using information exchange
requirements modelling and software capability profiling
1 Scope
This Technical Report describes an approach for using ISO 16100 and ISO 18435 to specify information
exchange requirements between applications. This approach is based on the use of ISO 18435 application
interaction matrix element (AIME)/application domain matrix element (ADME) templates in conjunction
with ISO 16100 manufacturing software unit (MSU) capability profiles.
This Technical Report also provides an example approach as applied to describing the interoperability
requirements of the integrated smart pump application, which comprises the pump control application
and the pump diagnostics application.
2 Normative references
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 16100-3:2005, Industrial automation systems and integration — Manufacturing software capability
profiling for interoperability — Part 3: Interface services, protocols and capability templates
ISO 16100-5:2009, Industrial automation systems and integration — Manufacturing software capability profiling
for interoperability — Part 5: Methodology for profile matching using multiple capability class structures
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
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 16100-3, ISO 16100-5,
ISO 18435-2, and the following apply.
3.1
application domain matrix element
ADME
entry in an application domain matrix to organize information exchange among applications
[SOURCE: ISO 18435-2:2012, 3.2]
3.2
application interaction matrix element
AIME
entry in application interaction matrix to denote the capabilities of the resource to support
information exchange
[SOURCE: ISO 18435-2:2012, 3.4]
3.3
application interoperability profile
AIP
single specification referencing a group of profiles that reference parts of base specifications which may
themselves be profiles
Note 1 to entry: The group of profiles can include process profile(s), information exchange profile(s), resource
profile(s) and sometimes other AIPs.
[SOURCE: ISO 18435-2:2012, 3.5]
3.4
capability class
element within the capability profiling method that represents manufacturing software unit
functionality and behaviour with regard to the software unit’s role in a manufacturing activity, as
denoted in a capability inheritance structure and as deployed in a capability aggregation structure
Note 1 to entry: The role of a MSU changes when used in different manufacturing activities; however, the MSU’s
corresponding capability class is positioned uniquely in an inheritance structure, but can assume different
positions in an aggregation structure.
Note 2 to entry: In this Technical Report, a capability class template is identical to a capability template
(ISO 16100-2:2003, 6.3, gives requirements for capability templates).
[SOURCE: ISO 16100-5:2009, 3.1, modified]
3.5
capability class structure
CCS
hierarchy of capability classes
3.6
capability profiling template
capability template
template
schema for a manufacturing software capability profile
Note 1 to entry: It could be partially filled.
[SOURCE: ISO 16100-3:2005, 3.1.14, modified]
3.7
manufacturing domain data
MDD
unified modelling language (UML) class representing information about manufacturing resources,
manufacturing activities, or items exchanged among manufacturing resources within a particular
manufacturing domain
[SOURCE: ISO 16100-5:2009, 3.3]
3.8
manufacturing domain model
MDM
particular view of a manufacturing domain, consisting of manufacturing domain data and relationships
among them, corresponding to the domain’s applications
[SOURCE: ISO 16100-5:2009, 3.5]
2 © ISO 2013 – All rights reserved

4 Abbreviated terms
ADID Application Domain Integration Diagram
ADME Application Domain Matrix Element
AIF Application Integration Framework
AIME Application Interaction Matrix Element
AIP Application Interoperability Profile
CCS Capability Class Structure
IG Identification Guide
MDD Manufacturing Domain Data
MDM Manufacturing Domain Model
MSU Manufacturing Software Unit
OTD Open Technical Dictionary
PID Proportional Integral Derivative
PLC Programmable Logic Controller
UML Unified Modelling Language
VFD Variable Frequency Drive
XML eXtensible Markup Language
5 Applications interoperability requirements modelling
5.1 Application integration framework in ISO 15745 and ISO 18435
The application integration framework (AIF) that is explained in ISO 15745-1 provides a basis for
integrating an automation and control system architecture within a manufacturing application
architecture.
An integrated manufacturing application can be modelled as a combination of a set of manufacturing
processes, resources and a set of information exchange among the manufacturing resources, as shown
in Figure 1. Manufacturing resources can be further divided as several types of communication
networks, devices, software, equipment, material, and personnel necessary to support the processes
and information exchanges required by the application.
A set of manufacturing resources that satisfy a set of interoperability and integration requirement is
needed to realize a manufacturing application. An integrated manufacturing application is enabled by a
manufacturing system consisting of a set of integrated manufacturing resources.
The categories of application domains of interest are enumerated in ISO 18435-1 and represented using
an application domain integration diagram (ADID).
Figure 1 — Application integration model
5.2 Elements of information exchanges in ISO 18435
ISO 18435 focuses on integration of applications. ISO 16100 focuses on interoperability of MSUs, including
manufacturing information exchange either within one application or within different applications. The
information exchange among resources is represented by ISO 18435.
ISO 18435-1 provides an overview of the integration requirements of a manufacturing application. The
focus is on the production operations and maintenance operations domains, including the capability
assessment activities.
ISO 18435-2 provides the detailed definitions of the AIME and ADME structures and their relationships.
General procedures for constructing AIMEs and ADMEs are also described.
An AIME represents capabilities provided by a set of resources of an application in order to exchange
information with another set of resources associated with another application.
The set of AIMEs that represents the resource capabilities that meet the information exchange
requirements to support the interoperability of two applications comprises a key part of an ADME.
ADME that qualifies interoperability relationship between two applications is elaborated in Figure 2.
Clause A.1 has an example of an integrated application which describes the smart pump application.
The capability profiles of MSUs are obtained by filling adequate capability templates. Annex C shows the
examples of capability profiles for the smart pump applications.
4 © ISO 2013 – All rights reserved

Integrated Integrated
Application Y
Application X
1.N 1.M
Resource
Resource
1.*
1.*
Process
Process
1.* 1.*
Information
Information
Exchange
Exchange
1.*
ADME
(X, Y)
1.*
1.*
AIME AIME
Activities
Activities
Figure 2 — AIME and ADME
The purpose of the ADME is to describe the interoperability and integration requirements that are
required by the applications. The general concept of an ADME is to model the information exchanges
between applications using the application interoperability profile (AIP) notation as described in
ISO 15745-1. The ADME supports the information exchange between the applications based upon the
capabilities identified in the AIMEs. The complete set of AIMEs that represents the information exchange
requirements for realizing the interoperability of two applications comprises an ADME.
5.3 Context for information exchange requirements
The context for the information should be established using the application domain of interest as
described in ISO 18435-1.
A manufacturing process is modelled as a set of activities that follow a specific sequence. Each activity
is associated with a set of functions. The functions are implemented by manufacturing resources, such
as MSUs shown as the left part of Figure 3. These MSUs enable information exchanges associated with
the functions performed.
Context for the information exchange can be derived from the activities and capability class structure
(CCS) shown in Figure 3. Clause A.2 has an example of CCS for the smart pump application. According
to an ISO 16100 methodology, each capability class has a capability template. Examples of capability
templates for the smart pump application are shown in Annex B.
Integrated
Manufacturing
Applicaon
Capability
Acvity 1 Acvity 2
....... Class
(MSU 1) (MSU 2)
Capability Capability
Sub Acvity 1 Sub Acvity 2
.......
Class Class
(MSU 11) (MSU 12)
Capability Capability
Resource 1 Resource 2 .
Class Class
(MSU 111) (MSU 112)
Capability
Profile Template
Class
= Concrete class for
profile
Profile
Profile
.......
.......
Template
Template
Class
Instance
Profile . Profile .
Figure 3 — Activity tree of an application
5.4 Content for information exchange requirements
5.4.1 Application requirements capability profile
The information exchanged between the MSUs provides the content for the ADME structure as described
in the manufacturing domain data (MDD).
Application requirements capability profile in ISO 16100 describes an activity model in Figure 3. The
activities also describe information exchange among the resources or MSUs involved in the activity.
These information items exchanged typically include, input/output information in a MSU execution (such
as recipes, geometric data, schedules, or other activity parameters needed to perform the application),
control information (such as commands and requests for service), and status information (such as faults,
equipment status reports, alerts, and quality information).
The manufacturing domain model (MDM) is a particular view of a manufacturing domain, consisting of
MDDs and relationships among them, corresponding to the domain’s applications as shown in Figure 4.
A set of MDDs works like a terminology set in the applicable domain. MDDs represent different types
of manufacturing information, including those that are exchanged between the resources within an
application and between applications.
Information items pertaining to control of the actions of the equipment and device, e.g. the pump and
the variable frequency drive (VFD) in Figure A.1, are usually handled by MSUs but are not included in
this example.
6 © ISO 2013 – All rights reserved

Capability
Action
Name
Actions---
Methods in the action
Performed by         Method
methods
Status
Device
Equipment
Tools utility
Material Workpiece / Substance / Item
Resources---
Support the methods
Secondary material
to fulfill the action
Human
…………….
Instruction / prescription
Recipe
Constraints---
Quality requirement
in the methods
/ actions
Order / Control data / Product data /
Input data
Manufacturing data
Output data
Action performance report /
Progress state / Product data /
Standard time
Manufacturing data
Actual time
Information exchanged---
between the methods             Start  time
/actions
End time
Standard cost
Actual cost
…………….
Predecessor
Relationship--- Successor
between MDDs or actions
……………….
MDDs
Figure 4 — Partial activity model represented by MDDs
5.4.2 MDDs used in ADME Content
Within a specific manufacturing domain, a manufacturing application can be represented as a set of
MDDs. MDDs provide information about various aspects within a specific manufacturing domain. MDDs
that represent information exchange between applications in the domain are used to enumerate the
content section in the ADME. MDDs in Annex C are examples of ADME contents for the integrated smart
pump application information exchange requirements.
5.5 Conveyance for information exchange
The ADME conveyance section captures resource types and specific configuration required to support
information exchanges enumerated in the content section of the same ADME. Interoperability requirements
expressed in the context section present the constraints to be addressed by the resource configurations.
Clause D.4 shows one possible example of the conveyance section to support integration of the pump
control and the pump diagnostics applications. The channel in the conveyance section is configured to
support information exchange to meet the requirements of the integrated smart pump application.
5.6 ADME for the smart pump application
The context, content and conveyance section noted in 5.3, 5.4 and 5.5 form the ADME for expressing the
information exchange requirements that support interoperability of the pump control and the pump
diagnostics applications within the integrated application of the smart pump application.
6 Approach for smart pump application interoperability
6.1 Smart pump system information model
The asset design environment provides a wealth of information operating and managing the
manufacturing assets, e.g. a pump in certain manufacturing processes. ISO 15926 facilitates integration
of asset information to support the life-cycle activities and processes of production facilities. ISO 15926
provides a model and library classes and templates for representing life-cycle information about technical
installation and their components. Figure 5 shows the pump information model based on ISO 15926.

Figure 5 — Pump model based on ISO 15926
The information model based on ISO 15926 can be utilized in conjunction with ISO 18435 framework to
enable information exchange. By using an ISO 15745 based application integration modelling approach,
information exchange requirements for key interoperability interfaces can be identified and concisely
documented in terms of resource-specific AIMEs. These AIMEs enumerate a set of particular standards
for enabling context-, content- and conveyance-oriented exchanges to enable the asset interoperability
and integration of applications dealing with asset information structures.
6.2 Resolving ambiguity using OTD
There are no well-defined methods to define the relationships between the terms and definitions common
to the design environment and the operational environment. Many terms and definitions associated with
assets used in both the design context and the operational context are often ambiguous or inconsistent.
Their interpretation or meaning depends on the particular context. The open technical dictionary (OTD)
based on ISO 22745 resolve the ambiguity or inconsistency of these terms and definitions. The benefits
8 © ISO 2013 – All rights reserved

of ISO 8000 (data quality) can be realized using ISO 22745 by specifying the data requirements for
messages containing master data that is exchanged between organizations; specifically requirements
for syntax, semantic encoding, and portability.
ISO 22745’s main facilitator is the OTD, a repository of concept identifiers and associated descriptions
used to define individual data elements. Once each element is described with the concept identifier from
the OTD, the descriptive elements can be stored, sent, received, and displayed by different organizations
without losing any meaning.
ISO 22745 also includes guidelines for the use of identification guides (IG). An IG is a set of rules for
describing a particular class of items to meet the requirements of a data recipient. An IG is specified
using an XML schema. If all elements are included in the description, this IG facilitates the machine-
aided analysis of data quality because clear understanding is possible of what data are required without
a person having to review the data. The use of an IG in constructing master data for product catalogues
can be a pattern for use of concept identifiers in constructing application information exchange profiles
(i.e. AIMEs and ADMEs).
The concept identifiers used in the context, content and conveyance sections of the AIMEs and ADMEs
provide references registered in the OTD. These references point to the standards that define the
information exchange objects. The concept identifiers are also used to fill in the capability profiles and
templates required by the applications to be integrated.
NOTE 1 ISO 29002 provides a framework for mapping the ISO 22745 OTD concept identifiers to other concept
identifier schemes. IEC 61987 definitions (list of device properties, classifications), ISO 13584 (parts libraries)
and ISO 15926 object identifiers can be expressed in terms of ISO 22745 concept identifiers. The use of other
concept identifiers and the details of these mappings are outside the scope of this Technical Report.
NOTE 2 Concept identifiers are not used in the XML examples in the annexes, for better human readability.
6.3 Application integration using ISO 18435
ISO 18435 specifies provisions that applications are expected to satisfy, in terms of a set of
interoperability profiles. For example, if a diagnostic application requires flow information from the
control application controlling a pump to assess the overall asset condition, these two applications need
to have compatible profiles for this particular information exchange. The purpose of the ADME is to
describe the information exchange requirements of the applications. For each application, interfaces
used for information exchange are described using the AIME. The AIME details the resource capabilities
that meet the information exchange requirements to support the interoperability of two applications.
A set of AIMEs represents the interface profiles supported by the applications and the corresponding
resources and these AIMEs comprise an ADME.
7 Constructing AIME and ADME for smart pump application
7.1 Overview
The integrated smart pump application consists of two separate applications: control application and
diagnostics application. By integrating these two separate applications, the resulting smart pump
application exhibits an intelligent behaviour, e.g. changing pump operation modes according to pump
diagnostics results to protect the equipment or processes. The sequence diagram in Figure D.1 in the
Annex D illustrates the example information exchange between pump control application and pump
diagnostics application for the integrated smart pump application to achieve integration.
7.2 AIME for pump control application
The control application for the pump consists of two separate applications with corresponding MSUs,
i.e. one for pump proportional integral derivative (PID) control and the other for data acquisition from
the sensors. AIMEs from the PID control and the data acquisition form one ADME which is not described
in this Technical Report. Once these two applications are integrated, one resulting AIME can be formed
by replicating the context section and the conveyance section from the ADME. Symbolic names in the
matrix elements inside AIMEs and ADMEs are all replaced by the concept identifiers already registered
in the reference OTD. Figure 5 illustrates the use of concept identifiers inside an AIME. The left hand side
of Figure 6 shows the conveyance section without the concept identifiers. The right hand side of Figure 6
shows the concept identifiers used in the conveyance section of the AIME.

… …
Diagnostics Example DiagnosticsExample
type=”tFlowRateReq”> type="0161-1#01-080761#1">
Flow Rate Request Flow Rate Request

type=”tFlowRateRes”> type="0161-1#01-018902#1">
Flow Rate Response FlowRate Response

… …
type=”ISO15745_ENet_CommNet_Profile" type=”0161-1#01-1074537#1”>
Ethernet/IP ISO15745-2 Profile Ethernet/IPISO15745-2 Profile


… …
Figure 6 — Concept identifiers inside AIME
Clause D.2 shows the AIME for the pump control application.
7.3 AIME for pump diagnostics application
The pump diagnostics application consists of single application with one corresponding MSU. If an
AIME does not exist, one can be constructed. Necessary information can be obtained from the specific
part of the MSU that contains methods, resources and information items to form the conveyance and
context sections of the AIME. Symbolic names in the matrix elements inside AIMEs are all replaced by
the concept identifiers already registered in the reference OTD.
Clause D.3 shows the AIME for the pump diagnostics application.
7.4 ADME for the integrated smart pump application
Elements of all the sections from the integrated application’s ADME is derived from the pump control and
pump diagnostics AIMEs and information items contained in the capability profiles of the pump control
and the pump diagnostics MSUs. All the remaining symbolic names in the ADMEs are all replaced by the
concept identifiers already registered in the reference OTD. The concept identifiers used in the matrix
elements need to be selected from the IG to qualify the allowable collections. The allowable collections
can be analysed to determine if they meet the interoperability requirements of the integrated smart
pump application.
Clause D.4 shows the ADME for the integrated smart pump application.
8 General procedures for achieving application integration
The procedure of modelling application interoperability is as follows.
a) Specify domain(s) of interest(s) from ISO 18435 ADID and identify corresponding applications for
information exchange, e.g. control and diagnostics domains.
10 © ISO 2013 – All rights reserved

b) Profile the information exchange requirements between applications based on ISO 15745
profiling methodology.
c) Identify elements of application integration model of ISO 15745, i.e. information exchanges and
MSU resources that enable exchanges, e.g. information exchange between the pump control and the
pump diagnostics applications.
d) ISO 16100 MSU capability profiles need to exhibit information exchange and application capabilities.
e) Retrieve or construct the CCS for application requirements. CCSs are expressed in terms of concept
identifiers based on ISO 22745 OTD.
f) Identify AIMEs which fulfil the necessary information exchange between applications resources
including MSUs.
g) Identify ADMEs which fulfil the necessary information exchange between applications.
h) If the capability requirements of the applications are provided by the ISO 16100 required
capability profiles:
1) use capability requirements of ISO 16100 and fill in AIMEs and ADMEs corresponding contexts;
2) use capability requirements of ISO 16100 and fill in AIMEs and ADMEs corresponding conveyance;
3) use capability requirements of ISO 16100 and fill in AIMEs and ADMEs corresponding contents.
i) If the capability requirements of the applications are provided by the ISO 18435 ADMEs:
1) use capability requirements of ISO 18435 ADMEs in context, content, and conveyance sections
to construct ISO 16100 required profiles to obtain corresponding MSUs;
2) use MSU identifiers from the ISO 16100 profile matcher to fill in the resource sections of the
ADMEs and corresponding AIMEs;
3) update the ADMEs and AIMEs accordingly.
Annex A
(informative)
Modelling smart pump application
A.1 Application of smart pump system
The integrated smart pump system information model described in this annex is extended from the
conventional ISO 15926 pump model illustrated in Figure 5. Figure A.1 shows the system diagram for
the smart pump as an example.
Figure A.1 — Smart pump system diagram
There are three MSUs in the integrated smart pump application in this example. The pump control
application consists of a programmable logic controller (PLC), and appropriate input and communication
modules to process sensor information and communicate with VFD for adjusting the pump speed. There
are two MSUs in the pump control application:
— data acquisition MSU acquires the sensor data from the sensors, e.g. flow rate, discharge pressure
and temperature;
— pump control MSU has pump control capability, e.g. speed and PID control for flow and pressure.
It is assumed that these two MSUs along with other resources comprising the pump control application
are already integrated within the pump control application as described in 7.2 and the information
exchange within the pump control application is not discussed in this annex.
The stand-alone pump diagnostics application has one MSU: pump diagnostics MSU receives sensor
information from the pump control application, performs diagnostics, and sends the diagnostics result
back to the pump control application.
12 © ISO 2013 – All rights reserved

The data flow is as follows:
a) sensor information, e.g. flow, discharge pressure and temperature, is read by MSU1 (data acquisition)
of the pump control application;
b) necessary sensor data are sent to pump diagnostics application to perform pump diagnostics;
c) pump diagnostics, e.g. cavitation detection, is performed by MSU2 of pump diagnostics application;
d) the diagnostic result, e.g. degree of pump cavitation, is sent back to pump control application;
e) MSU3 of the pump control application changes the pump operation profile, e.g. it slows down the
pump to protect the equipment or process.
A.2 Integrated smart pump application CCS
The following XML example represents the CCS of the integrated smart pump application.

spaceSchemaLocation=”C:\SmartPump1108\SmartPumpCCS.xsd”>
































Annex B
(informative)
Capability profiling templates of application software units
B.1 Smart pump data acquisition capability profiling template
The following XML example represents the MSU capability template for the data acquisition MSU.







type=”xs:string” />
/>











































14 © ISO 2013 – All rights reserved



/>




type=”xs:string” />










































...