ISO 18435-1:2009

INTERNATIONAL ISO
STANDARD 18435-1
First edition
2009-08-15
Industrial automation systems and
integration — Diagnostics, capability
assessment and maintenance
applications integration —
Part 1:
Overview and general requirements
Systèmes d'automatisation industrielle et intégration — Diagnostics,
évaluation des moyens et intégration des applications de
maintenance —
Partie 1: Vue d'ensemble et exigences générales

Reference number
©
ISO 2009
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 2009
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 2009 – All rights reserved

Contents Page
Foreword .v
Introduction.vi
0.1 General .vi
0.2 Asset operation and maintenance lifecycle management integration framework .vi
0.3 Approach.viii
0.4 Intended benefits.viii
0.5 Relationship to other parts of ISO 18435.ix
1 Scope.1
2 Normative references.1
3 Terms and definitions .1
4 Abbreviated terms .4
5 Integration and interoperability of applications.4
5.1 Requirements for integration of applications.4
5.2 Requirements for integration models .5
5.3 Criteria for interoperability and integration.5
5.4 Application domains .6
5.4.1 General .6
5.4.2 Categories of application domains.6
5.4.3 Operations planning and scheduling (D3.1).7
5.4.4 Supervisory control and HMI (D2.1) .7
5.4.5 Control, I/O, operational data historian and panel display (D1.1) .8
5.4.6 Capability assessment and decision support (D3.2) .8
5.4.7 Asset prognostics and health, product quality, safety and environmental management
(D2.2).8
5.4.8 Asset utilization, condition monitoring and quality monitoring (D1.2).9
5.4.9 Maintenance planning and scheduling (D3.3) .9
5.4.10 Maintenance work order management and tracking (D2.3) .9
5.4.11 Asset configuration, calibration, repair and replace (D1.3) .10
5.4.12 Intra-enterprise and inter-enterprise activities (D4.1 and D4.2).10
5.4.13 Resource registry services (D0.1 and D0.2) .10
5.5 Integration within an application .11
5.5.1 Application interoperability model .11
5.5.2 Interoperability and integration of resources in an application .12
5.5.3 Interoperability and integration of processes in an application .12
5.6 Integration within a domain.12
5.6.1 Interoperability and integration of applications in a domain.12
5.6.2 Overview of Matrix Elements .13
6 Integration among domains .14
6.1 Interoperability and integration between applications in different domains .14
6.2 Applications in different domains at the same level in a hierarchy.14
6.3 Applications in different domains at different levels in a hierarchy .15
6.4 Integration requirements across application scenarios .15
6.5 Integration requirements in terms of interoperability templates .15
7 Conformance and compliance .15
7.1 Conformance aspects.15
7.2 Compliance aspects.15
Annex A (informative) Application domain matrix.16
Annex B (informative) Coordinated asset registry service.21
Bibliography .23

iv © ISO 2009 – 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 document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 18435-1 was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 5, Architecture, communications 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
The following parts are under preparation:
⎯ Part 2: Descriptions and definitions of application domain matrix elements
⎯ Part 3: Applications integration description method
Introduction
0.1 General
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 describes application integration models and common application interoperability requirements.
These application integration models are intended to:
a) provide diagnostics, capability assessment, and maintenance applications’ integration reference
architecture for manufacturing assets, such as equipment, automation devices, and software units;
b) enable integration of diagnostics, capability assessment, and maintenance applications with other
applications;
c) provide for a system view context in dealing with asset management lifecycles.
Application integration models are intended to guide users of industry specifications or standards when
integrating diagnostics, capability assessment, and maintenance applications with production and control
applications. These integration models define elements and rules to help identify and select interfaces
described in the interoperability templates. These interoperability templates are used to reference
interoperability profiles based on international standards that are required for integrating the applications
within and at different levels of an enterprise’s functional and resource hierarchies.
The intended users of ISO 18435 are developers of industrial automation applications, especially those that
design, implement, deploy, commission, and operate the required systems which integrate diagnostics,
capability assessment, control, production, and maintenance applications.
0.2 Asset operation and maintenance lifecycle management integration framework
The main focus of ISO 18435 is to describe the integration requirements that manufacturing assets and
resources need to meet in order to support the operation and maintenance phase within a manufacturing
system’s lifecycle (see Figure 1).

Operations (e.g.
Implementation
Commissioning
Design End of Life
Production & Maintenance)
0DQXIDFWXULQJ6\VWHP/LIH&\FOH

Other standards (e.g
Other
ISO10303
ISO 18435
IEC 62264, ISO 13374)
standards
Figure 1 — Scope of ISO 18435 in the lifecycle of a manufacturing system
In Figure 2, the diagnostics and maintenance related activities are shown in a framework, where several
combinations of these activities, as distinguished in scope by the ovals, provide effective mechanisms for
adapting maintenance strategies to various changes in manufacturing operations, such as changes in
production requirements, changes in operational conditions and environment, and changes to continuously
improve manufacturing assets during their lifecycle.
vi © ISO 2009 – All rights reserved

For example, the first combination of activities deals with the operational phase of maintenance task execution,
which consists of maintenance task planning, involving asset inspection, monitoring and diagnostics, followed
by treatment or repair if needed, and ends in the evaluation of maintenance results. These activities are
mainly concerned with controlling routine maintenance tasks.
The second combination of activities focuses on maintenance strategy planning that involves the selection of
an approach for performing maintenance appropriate to each asset with options such as breakdown
maintenance (BM), time-based maintenance (TBM) and condition-based maintenance (CBM). The
maintenance strategies can be improved based on diagnostic capability assessment and maintenance
histories.
The third combination of activities includes manufacturing asset design improvement driven by inputs from
maintenance strategy planning. The design improvements drive maintenance strategy planning. This third
cycle seeks to minimize maintenance costs or reduce maintenance effort and time through asset improvement.

Design data
and
Asset
modification
improvement
record
Design / Maintenance
improvement strategy planning
Maintenance
Maintenance
and (BM/TBM/CBM) strategy
and diagnostics
selection
modification
history
Maintenance
task execution
Maintenance
strategy
Discrepancies
Level R3
Evaluation of
Level R2
Maintenance
maintenance
task planning
result
Monitoring /
Levels R0, R1
diagnosis &
if necessary,
repair
Figure 2 — Framework for maintenance management of manufacturing assets
Although condition-based maintenance (CBM) can be regarded as an advanced strategy, it is not always the
most cost-effective method. When failures of machines or components are not critical, the breakdown
maintenance (BM) approach is preferable. When the remaining useful life of machines or components can be
estimated, time-based maintenance (TBM) is preferred.
ISO 18435 addresses the first cycle of maintenance task execution and the integration of maintenance
applications with the other manufacturing applications, especially in the case of condition-based maintenance.
The following are examples of integration issues concerning aspects of quality, cost and delivery:
a) quality aspect: conditions of manufacturing assets, kept by the maintenance tasks, used in product quality
assurance;
b) cost aspect: trade off between maintenance cost and production loss due to malfunction, unsafe condition
and inefficiency of assets;
c) delivery (time) aspect – coordinating maintenance schedule with production schedule.
0.3 Approach
In ISO 18435, the definitions and concepts in other international standards, such as IEC 62264, ISO 15745,
and ISO 13374, are used to describe the functions and interfaces that gather information about the process,
equipment, operators, and materials and other manufacturing assets and convey the information to various
diagnostics and maintenance sub-systems in order to perform asset management. The information exchanges
are denoted by a set of schemas that describe the conveyed information and the usage of the required
interoperability interfaces.
In particular, reference is made to applicable concepts and definitions provided in ISO 15745, ISO 13374,
IEC 61499, IEC 61131, IEC 62264, IEC 61915, ISO/IEC 15459-1, MIMOSA OSA-CBM and
MIMOSA OSA-EAI.
0.4 Intended benefits
In a manufacturing enterprise, an appropriately integrated asset management system can provide critical
information to improve the productivity of the manufacturing assets deployed. Ideally, effective and timely
asset maintenance enables these assets to provide the services required by the production system.
In the past, the information about the process, equipment, operator and material that is already provided by
many industrial automation systems and control devices, was not fully utilized in the manufacturing process.
Today, with increasing use of digital signal processing in these devices, the available information can now be
more effectively analyzed closer to the manufacturing process and used in the diagnostics, capability
assessment, control, and maintenance applications. In addition, some of this information can be extracted via
interfaces already present in the control system, without adding additional sensors to the manufacturing
process. This increased information access capability needs to be presented in a standardized form to other
analysis tools that diagnose process, material and equipment problems via well-defined interfaces.
Other benefits that can be gained are as follows:
a) end users can facilitate the specification and procurement of open, integrated and safe systems by
referencing pre-defined diagnostics and maintenance application interoperability profiles;
b) system integrators can reduce the time to develop diagnostics and maintenance solutions by using
generic tools based on ISO 18435;
c) suppliers of diagnostics and maintenance products and services can provide and develop new offerings
using generic tools based on ISO 18435;
d) system aspects of safety management can be improved with an easy access to critical information.
Integration increases the likelihood of the system to realize process optimization per the performance and
capacity targets of the application and the business requirements, such as, cost, safety, security, and
environmental compatibility.
The application integration models and interoperability schemas can provide equipment and field device
suppliers, system integrators, and application designers a means to assess the suitability of diagnostic and
maintenance components when integrating the required condition monitoring, maintenance scheduling and
asset management systems with other manufacturing applications.
viii © ISO 2009 – All rights reserved

0.5 Relationship to other parts of ISO 18435
The different parts of ISO 18435 are briefly described in Table 1 and illustrated in Figure 3.
In Figure 3, the focuses of the various parts of ISO 18435 are shown as dotted-line areas that bound specific
portions of the UML class diagram representing the integration model for an application and between
applications.
Table 1 — Outline of ISO 18435
Part Description
Overview of the integration approach and the application integration model elements, their relationships
ISO 18435-1
and a description of general requirements in terms of selected industry application scenarios.
Descriptions and definitions of application domain matrix elements and application interaction matrix
a
ISO 18435-2
elements which represent the application-to-application integration requirements.
a
ISO 18435-3 Applications integration description method in terms of interoperability profile templates.
a
Under preparation.
This part of ISO 18435 provides an overview of the elements and the rules of a method to describe a
manufacturing application’s integration requirements. The elements include the key aspects when integrating
a manufacturing 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-1 ISO 18435-3
(ISO 18435-2)
ADME
Application Application
1.*
•Process
1.*
Resource
1.*
Activities 1.*
Information Exchange
(ISO 18435-2)
AIME
Figure 3 — Relationships within ISO 18435
ISO 18435-2 will provide 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 will be described.
ISO 18435-3 will define a recommended method to describe the interoperability and integration requirements
between applications in two or more manufacturing domains within a manufacturing enterprise. The focus will
be on the production operations and maintenance operations domains.
INTERNATIONAL STANDARD ISO 18435-1:2009(E)

Industrial automation systems and integration — Diagnostics,
capability assessment and maintenance applications
integration —
Part 1:
Overview and general requirements
1 Scope
This part of ISO 18435 defines an integration modelling method and its use to integrate diagnostics, capability
assessment, prognostics and maintenance applications with production and control applications. The
integration of other application aspects, such as security, is outside the scope of ISO 18435.
NOTE 1 Other parts of ISO 18435 will define the activity domain matrix elements and the detailed integration methods
between applications in the application domain integration diagram.
NOTE 2 It is recognized that security is an important aspect of many applications; however, security will not be
addressed in ISO 18435.
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.
IEC 62264-1, Enterprise-control system integration — Part 1: Models and terminology
IEC 62264-2, Enterprise-control system integration — Part 2: Object model attributes
IEC 62264-3, Enterprise-control system integration — Part 3: Activity models of manufacturing operations
management
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
activity
set of actions performed by a set of actors
NOTE An activity can also be performed by the actors' agents.
3.2
application
ordered set of processes, performed by a set of resources, coordinated by a set of interactions intended to
accomplish a definite objective
3.3
behaviour
observable activities of a component via its effect on its environment and/or through its measurable attributes
3.4
capability assessment
evaluation of the ability or capacity of a manufacturing asset to provide a resource to the system
3.5
component
〈resource〉 part of a system that plays a particular role, by providing some or all of a system’s functions when
performing a task
3.6
control application
type of manufacturing application that monitors availability and identifies the conditions of manufacturing
assets and provides other applications with such information in order to accomplish a manufacturing
production objective
3.7
diagnostics application
type of manufacturing application that monitors and checks the continued availability of manufacturing assets,
and notifies the other manufacturing applications of any conditions or constraints on such availability
3.8
data historian
capability of a system to collect operating information of that system
3.9
integration
system condition or activity to realize the condition in which components of a system are organized to
collaborate, coordinate and interoperate while exchanging items, as needed, to perform a system’s task
3.10
interaction
transaction involving multiple resources to accomplish some part of a system’s function
EXAMPLE Examples include coordination, collaboration, cooperation, unwitting assistance, witting non-interference,
and even competition.
3.11
interface
set of services and related service mechanisms, available via a logical or physical access point, provided by a
resource, in order to transfer or exchange information, material, energy, and other manufacturing aspects
NOTE ISO/IEC 10746-2:1996, 8.4, defines “interface” as “an abstraction of the behaviour of an object that consists of
a subset of the interactions of that object together with a set of constraints on when they may occur”.
3.12
interoperability
capability of two or more entities to exchange items in accordance with a set of rules and mechanisms
implemented by an interface in each entity, in order to perform their respective tasks
NOTE 1 Examples of entities include devices, equipment, machines, people, processes, applications, software units,
systems and enterprises.
NOTE 2 Examples of items include information, material, energy, control, assets and ideas.
2 © ISO 2009 – All rights reserved

3.13
maintenance application
type of manufacturing application that manages the reconfiguration, removal, replacement or repair of the
manufacturing assets, and notifies the other manufacturing applications of such activities
3.14
manufacturing application
set of manufacturing processes, related resources and information exchange involved in the manufacture of a
product or the provision of a service
3.15
manufacturing asset
tangible, uniquely identified system with a defined role in the manufacturing process
NOTE Manufacturing assets include structural, mechanical, electrical, electronics and software components, but they
do not include human resources, process materials, financial assets and in-process materials.
3.16
manufacturing process
set of processes in manufacturing involving a flow and/or transformation of material, information, energy,
control, or any other element in a manufacturing area
3.17
manufacturing resource
physical or logical entity that enables a manufacturing process
NOTE Manufacturing resources include (but are not limited to) manufacturing assets such as equipment, machinery,
software, automation units, control devices, instrumentation, tooling, and other resources, e.g. operators, materials, fuels
and the physical plant wherein the resources are deployed.
3.18
path
association established between functional units for conveying information
3.19
process
temporal or logical ordering of a set of activities, events, or tasks performed under a set of conditions
3.20
production segment
sequence of process segments and product segments
NOTE See IEC 62264-2.
3.21
resource
entity used to accomplish a task
3.22
role
set of characteristics that distinguish a resource’s ability to exhibit a set of required behaviours
3.23
system
set of resources that jointly accomplishes one or more functions of an application’s process
NOTE The set of resources can be, for example, software, hardware or personnel.
3.24
task
set of actions intended to accomplish a set of functions
3.25
transaction
exchange of an entity at an interface using a service defined by the resource
4 Abbreviated terms
ADID Application Domain Integration Diagram
ADME Application Domain Matrix Element
AIME Application Interaction Matrix Element
AIRD Application Integration Relationship Diagram
ERP Enterprise Resource Planning
UID Unique ID (of asset for its entire lifetime)
UML Unified Modelling Language
XML eXtensible Mark-up Language
5 Integration and interoperability of applications
5.1 Requirements for integration of applications
The requirements for the integration of applications shall be described in terms of:
a) generic interoperability templates that enumerate an application's resource interfaces and the constraints
on those interfaces;
b) specific interoperability profiles for integration across target applications.
As shown in the use case diagram in Figure 4, the manufacturing applications addressed by the integration
model described in ISO 18435 reside either within a single domain or in different domains. Inter-domain
integration involves at least two applications each residing in a different domain. Intra-domain integration
involves two or more applications that reside within the same domain.
The integration requirements for applications in both intra-domain and inter-domain cases shall include the
provisions to support the interoperability of these applications. ISO 18435 defines a description method to
capture these integration requirements for both cases in the form of interoperability profiles and templates.
4 © ISO 2009 – All rights reserved

Inter-Domain
Integration
Integration of
Extends
applications
Intra-Domain
Integration
Extends
System
Integrator
Figure 4 — Applications integration requirements
5.2 Requirements for integration models
An integration model for integrating applications shall describe the following:
a) a set of applications to be integrated, including the distinguishing aspects of these specific target
applications;
b) a set of domains formed by these applications within an application domain integration diagram of a
manufacturing enterprise;
c) a set of interoperability interfaces, provided by the applications' resources and used in the information
exchanges among the applications.
5.3 Criteria for interoperability and integration
Two or more entities shall be considered to interoperate in the following cases:
a) when they exchange information;
b) when the information is exchanged in accordance with a set of rules and mechanisms;
c) when they have a common understanding of the information.
Two or more entities shall be considered integrated in the following cases:
⎯ when each one has a distinguishable structure, behaviour, or boundary;
⎯ when the behaviour is perceived to be accomplished by the integrated entities and not by an individual
entity;
⎯ when the entities collaborate, coordinate, and interoperate as needed to perform tasks.
NOTE Entities can be applications, resources, or processes.
These criteria are further elaborated in 5.5 and 5.6.
5.4 Application domains
5.4.1 General
In an enterprise, each manufacturing application uses resources that participate in particular roles to perform
specific tasks to accomplish the enterprise’s mission. The applications initiate information exchange with other
applications using interfaces that are provided by the resources.
The applications in an enterprise can be distinguished in terms of the processes, the sequence of activities in
the processes, the tasks that are scheduled and performed during the activities, the specific functions and the
required resources used when performing the tasks.
As defined in IEC 62264, the applications in an enterprise shall be distinguished to be resident at some level
in a hierarchy of concurrently running applications. Each level in a hierarchy is distinguished by the types of
functions performed, the types of resources involved in the tasks, the types of activities and processes
conducted, the types of information produced and consumed by the functions, as well as the information
structures exchanged with the other levels in the hierarchy.
Within each level, one or more applications categorized to provide the same generic type of function can form
a distinct set of applications. In ISO 18435, each distinct function set shall be called a manufacturing
application domain. Each application domain shall be modelled to consist of one or more applications that can
satisfy a set of interoperability requirements associated with the specific domain.
When each integrated application in a domain satisfies the domain’s specific set of interoperability
requirements, then the domain shall be referred to as an integrated domain.
5.4.2 Categories of application domains
In ISO 18435, the categories of application domains of interest are enumerated below and shall be
represented using an Application Domain Integration Diagram (ADID), as shown in Figure 5.
Some of the application domains at Level R3 of an enterprise hierarchy are as defined in IEC 62264.
a) Production and control applications in application domains D3.1, D2.1, and D1.1
1) D3.1: Operations planning and scheduling
2) D2.1: Supervisory control and HMI
3) D1.1: Control, I/O, operational data historian and panel display
b) Capability assessment, prognostics and diagnostics applications in application domains D3.2, D2.2, and
D1.2
1) D3.2: Capability assessment and decision support
2) D2.2: Asset prognostics and health, product quality, safety and environmental management
3) D1.2: Asset utilization, condition monitoring and quality monitoring
c) Maintenance, configuration, and repair applications in application domains D3.3, D2.3, and D1.3
1) D3.3: Maintenance planning and scheduling
2) D2.3: Maintenance work order management and tracking
3) D1.3: Asset configuration, calibration, repair, and replace
6 © ISO 2009 – All rights reserved

EXAMPLE Application domain D1.2 can be considered as a single application that monitors the condition of
manufacturing assets and performs diagnostics to determine if the asset is still able to perform its task. The resources
assigned to perform the application’s task need to support the required interoperability interfaces in order to act as an
integrated system.
D4.1 – Intra-enterprise activities: Business Planning, Orders & Production, D4.2 – Inter-enterprise activities: Supply Chain Planning, Logistics Strategy

Level R4
and Maintenance
Enterprise / Site
D3.1 - Operations D3.2 – Capability Assessment & D3.3 - Maintenance
Level R3
Planning & Scheduling Order Fulfillment Planning & Scheduling
Area
D2.1 - Supervisory Control & Human- D2.2 - Asset Prognostics and Health, D2.3 - Maintenance
Level R2
Machine Interface Quality, Safety, & Environmental Execution & Tracking
Work Center
Management
D1.1 – Control, I/O, Data Acquisition, D1.2 - Asset Condition Monitoring &  D1.3 - Asset Configuration,
Level R1
Data Historian, Asset Utilization & Sample / Test / Diagnostic Calibration & Repair / Replace
Work Unit
Displays & Quality Monitoring
D0.1 – Non-asset Resource D0.2 - Asset
Level R0
Identification and Location Identification and Location
Asset
Non-asset Resources Assets
(Equipment / Facilities / Serialized Components /
(Material / Personnel / Utilities)
Sensors / Transducers / Software / Documents)

NOTE 1 This figure only includes domains which are significantly related to operation and maintenance integration,
such as production control, maintenance, and capability management.
NOTE 2 The arrows between and across levels indicate that transactions can occur between any levels and any
columns (e.g. D1.1 can communicate to D3.2).
NOTE 3 Domains are related to the reference levels. An implementation can have all reference domains, some can
have less. It is advisable that any implementation map back to these application reference domains. Any application
domain on this picture can interact with any other application domain. An implementation defines the interfaces exposed
by the associated applications with reference to these application domains.
Figure 5 — Application Domain Integration Diagram (ADID)
5.4.3 Operations planning and scheduling (D3.1)
Applications in Domain D3.1 shall correspond to production operations planning and scheduling based upon
production commitments issued by the business applications in the application domains D4.1 and D4.2. The
D3.1 applications shall be modelled to have information exchanges with the applications which can be in the
following application domains: D2.1, D3.2, D3.3 and D2.2. Examples of specific information exchanges are
described in Annex A.
5.4.4 Supervisory control and HMI (D2.1)
Applications in domain D2.1 shall correspond to supervisory control and operator interface functions that
enable production requirements to be converted to control system task planning and scheduling. These
functions also monitor the status of control system execution and provide displays and operator interfaces to
enable supervisory personnel and applications to monitor and to intervene in the process being controlled.
The D2.1 applications shall be modelled to have information exchanges with the applications which can be in
the following application domains: D3.1, D3.2, D2.2, D2.3, D1.1 and D1.2. Examples of specific information
exchanges are described in Annex A.
5.4.5 Control, I/O, operational data historian and panel display (D1.1)
Applications in application domain D1.1 shall correspond to closed loop control and the operation of input /
output devices that interface with the plant floor processes, equipment, machinery and personnel. These
applications shall include but may not be limited to the following:
a) plant floor data archiving and access to historical data access;
b) recording which assets were used with a specific lot of material;
c) track the production line and assets' productivity and downtime due to quality problems, changeovers,
equipment failure, fail-safe position, preventive maintenance, etc.;
d) process and equipment control;
e) process and equipment data acquisition.
The D1.1 applications shall be modelled to have information exchanges with the applications which can be in
the following application domains: D2.1, D2.2, D1.2, D1.3, D0.1 and D0.2. Examples of specific information
exchanges are described in Annex A.
NOTE By altering the control or configuration of an asset subject to new constraints (e.g. energy, lifetime, and
throughput), the utilization of the asset could be improved or changed. Panel displays allow operators to view the
operating state of the equipment and provide control engineers with the ability to change the operational capability of the
asset.
5.4.6 Capability assessment and decision support (D3.2)
Applications in application domain D3.2 shall correspond to evaluations of current and future manufacturing
operations capabilities within the manufacturing enterprise. These applications shall also include, but not be
limited to, the following:
a) forecasts of capabilities needed for a particular production segment based on projected production levels;
b) projected probability of success and impact assessment (environmental, safety, and financial) for an
entire production facility or line over time based upon future demands and regulatory constraints;
c) recommend resource commitments to support manufacturing operations based on other information,
such as:
1) production output and quality level over time;
2) direct/indirect costs, scrap output, environmental risk, safety risk, unexpected downtime risk;
3) shift and seasonal factors.
The D3.2 applications shall be modelled to have information exchanges with the applications which can be in
the following application domains: D3.1, D3.3, D4.1, D4.2, D2.1, D2.2, and D2.3. Examples of specific
information exchanges are described in Annex A.
5.4.7 Asset prognostics and health, product quality, safety and environmental management (D2.2)
Applications in application domain D2.2 shall correspond to asset prognostics and asset health assessment
that estimate an asset's remaining useful life and, consequently, when to perform the next major maintenance
action. These applications shall also include, but not be limited to, the following:
a) prognostics using other intelligent agents (e.g. ISO 13374 agent) to determine the current health of an
asset based upon diagnoses of abnormal states (e.g. ISO 13374 Health Assessment functions);
b) synthesis of complex data and events (alarms, operating changes, etc.) to develop operations and
maintenance advisories and schedule modifications;
8 © ISO 2009 – All rights reserved

c) predicting an asset's future health grade and diagnostic faults with an associated probability;
d) estimating impact of asset health on product quality, safety levels and environmental compliance.
The D2.2 applications shall be modelled to have information exchanges with the applications which can be in
the following application domains: D3.1, D3.2, D3.3, D4.1, D4.2, D2.1, and D2.3. Examples of specific
information exchanges are described in Annex A.
5.4.8 Asset utilization, condition monitoring and quality monitoring (D1.2)
Applications in application domain D1.2 shall correspond to asset condition monitoring and diagnostics that
acquire and convert plant floor data (e.g. the ISO 13374 Data Acquisition block) into specific descriptors
(features) of interest. These applications shall also include, but not be limited to, the following:
a) use of signal processing algorithms to extract specific descriptors of interest (e.g. the ISO 13374 Data
Monitoring block);
b) comparison of these descriptors against expected baseline profile values or condition monitoring limits to
trigger certain output of enumerated state indicators (e.g. level low, level normal, level high, “alert”,
“alarm”, etc);
c) generating condition monitoring alerts based on defined condition monitoring limits or baselines (e.g. the
ISO 13374 State Detection block);
d) generating asset utilization assessments based on operational context, sensitive to current operational
state or operational environment;
e) performing sampling and testing of equipment and process machinery similar to those done with
laboratory information management systems;
f) performing embedded diagnostic applications that return fault codes if abnormal conditions in the asset
are detected.
The D1.2 applications shall be modelled to have information exchanges with the applications which can be in
the following application domains: D1.1, D1.3, D2.1, D2.2, D2.3, D0.1, and D0.2. Examples of specific
information exchanges are described in Annex A.
5.4.9 Maintenance planning and scheduling (D3.3)
Applications in application domain D3.3 shall correspond to maintenance operations planning and scheduling
based upon production commitments issued by application domain D3.1 applications. The D3.3 applications
then generate detailed maintenance plans for application domain D2.3 applications.
The D3.3 applications shall be modelled to have information exchanges with the applications which can be in
the following application
...