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 16100-5:2009 specifies the methods and rules for matching existing manufacturing software unit (MSU) capability profiles and required capability profiles derived from multiple capability class structures. The methods and rules allow MSUs in manufacturing applications to be evaluated for interoperability and, in some cases, for interchangeability. The following are outside the scope of ISO 16100-5:2009: services for creating, registering and accessing the various templates for the reference manufacturing domain models, the manufacturing domain data and the capability class structures; the conformance tables that reference Type 1 services defined and specified in ISO 16100-3; additional services needed for managing these templates in a database or equivalent object repository.

Systèmes d'automatisation industrielle et intégration — Profil d'aptitude du logiciel de fabrication pour interopérabilité — Partie 5: Méthodologie pour la correspondance de profil utilisant des structures de classe de capacité multiple

General Information

• Status: Published
• Publication Date: 22-Feb-2009
• 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
• Current Stage: 9060 - Close of review
• Start Date: 04-Mar-2025

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 16100-5
First edition
2009-03-01

Industrial automation systems and
integration — Manufacturing software
capability profiling for interoperability —
Part 5:
Methodology for profile matching using
multiple capability class structures
Systèmes d'automatisation industrielle et intégration — Profil d'aptitude
du logiciel de fabrication pour interopérabilité —
Partie 5: Méthodologie pour la correspondance de profil utilisant des
structures de classe de capacité multiple



Reference number
ISO 16100-5:2009(E)
©
ISO 2009

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


COPYRIGHT PROTECTED DOCUMENT


©  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 [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO 2009 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 16100-5:2009(E)
Contents Page
Foreword .iv
Introduction.v
1 Scope .1
2 Normative references .1
3 Terms and definitions.1
4 Abbreviated terms.2
5 Multiple CCSs referenced in manufacturing applications and in MSUs .3
5.1 Profile matching concept .3
5.2 Reuse of MSUs.4
5.3 Registration of MSUs.4
5.4 Applying reusable MSUs to meet requirements of a new manufacturing application.4
5.5 Manufacturing Domain Data.6
5.6 Mapping capability classes to MDDs.8
6 Methods and rules for capability profiling .9
6.1 Templates for MSU capability profiling .9
6.2 CCS template.9
6.3 Capability profile template .11
6.4 MDM Template.17
6.5 MDD templates .19
7 Profile matching based on multiple capability class structures .21
7.1 Capability profile matching procedure.21
7.2 Matching report.25
8 Conformance.26
Annex A (informative)  Process for Generating a MDM and MDDs .35
Annex B (informative)  Example of profile matching using multiple capability classes.36
Bibliography . 50
© ISO 2009 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 16100-5:2009(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 16100-5 was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 5, Architecture, communications and integration frameworks.
ISO 16100 consists of the following parts, under the general title Industrial automation systems and
integration — Manufacturing software capability profiling for interoperability:
⎯ Part 1: Framework
⎯ Part 2: Profiling methodology
⎯ Part 3: Interface services, protocols and capability templates
⎯ Part 4: Conformance test methods, criteria and reports
⎯ Part 5: Methodology for profile matching using multiple capability class structures
The following part is planned:
⎯ Part 6: Interface services and protocols for matching profiles using multiple capability class structures
iv © ISO 2009 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 16100-5:2009(E)
Introduction
The motivation for this part of ISO 16100 stems from the industrial and economic environment noted by
TC 184/SC 5 in its strategic planning discussions, in particular:
⎯ a growing base of vendor-specific solutions;
⎯ user difficulties in applying standards;
⎯ the need to move to modular sets of system integration tools;
⎯ 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 software capability profile. Its goal is to provide a method to represent the capability of manufacturing
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.
Certain diagrams in this part of ISO 16100 are constructed following unified modeling language (UML)
conventions. Because not all concepts embodied in these diagrams are explained in the text, some familiarity
with UML on the part of the reader is assumed.
Annex A describes the process for generating a manufacturing domain model (MDM) and manufacturing
domain data (MDD).
Annex B gives an example of profile matching using multiple capability classes.

© ISO 2009 – All rights reserved v

---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 16100-5:2009(E)

Industrial automation systems and integration — Manufacturing
software capability profiling for interoperability —
Part 5:
Methodology for profile matching using multiple capability
class structures
1 Scope
This part of ISO 16100 specifies the methods and rules for matching existing manufacturing software unit
(MSU) capability profiles and required capability profiles derived from multiple capability class structures. The
methods and rules allow MSUs in manufacturing applications to be evaluated for interoperability and, in some
cases, for interchangeability.
The following are outside the scope of this part of ISO 16100:
⎯ services for creating, registering and accessing the various templates for the reference manufacturing
domain models, the manufacturing domain data and the capability class structures;
⎯ the conformance tables that reference Type 1 services defined and specified in ISO 16100-3;
⎯ additional services needed for managing these templates in a database or equivalent object repository.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 16100-1, Industrial automation systems and integration — Manufacturing software capability profiling for
interoperability — Part 1: Framework
ISO 16100-2:2003, Industrial automation systems and integration — Manufacturing software capability
profiling for interoperability — Part 2: Profiling methodology
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-4:2006, Industrial automation systems and integration — Manufacturing software capability
profiling for interoperability — Part 4: Conformance test methods, criteria and reports
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 16100-1, ISO 16100-2, ISO 16100-3,
ISO 16100-4 and the following apply.
© ISO 2009 – All rights reserved 1

---------------------- Page: 6 ----------------------
ISO 16100-5:2009(E)
3.1
capability class
element within the capability profiling method that represents 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 The role of an 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 In this part of ISO 16100, a capability class template is identical to a capability template (see ISO 16100-
2:2003, 6.3, for requirements for capability templates).
NOTE 3 Adapted from ISO 16100-2:2003, 3.3.
3.2
capability class structure template
extensible markup language (XML) schema representing a hierarchy of capability classes
3.3
manufacturing domain data
unified modeling language (UML) class representing information about manufacturing resources,
manufacturing activities, or items exchanged among manufacturing resources within a particular
manufacturing domain
3.4
manufacturing domain data template
eXtensible markup language (XML) schema representing a manufacturing domain data
3.5
manufacturing domain model
particular view of a manufacturing domain, consisting of manufacturing domain data and relationships among
them, corresponding to the domain's applications
3.6
manufacturing domain model template
eXtensible markup language (XML) schema representing a manufacturing domain model
4 Abbreviated terms
CCS Capability Class Structure
CSI Conformance Statement for the Implementation
MDD Manufacturing Domain Data
MDM Manufacturing Domain Model
MES Manufacturing Operations Management
MSU Manufacturing Software Unit
UML Unified Modeling Language
XML eXtensible Markup Language
2 © ISO 2009 – All rights reserved

---------------------- Page: 7 ----------------------
ISO 16100-5:2009(E)
5 Multiple CCSs referenced in manufacturing applications and in MSUs
5.1 Profile matching concept
Figure 1 shows the concept of the profile matching using multiple capability class structures.
NOTE 1 The capability class structures of the provided MSUs (left side of figure) are assumed to be based on the
existence of a common capability class inheritance tree.
NOTE 2 The actual process for matching profiles uses the same algorithms that exist for matching XML schemas.
Manufacturing Application Developer
(MSU User)
Requirements of
Manufacturing Application #N
analyzing
Activity Tree #N
Activity Activity
#E #F
MSU Provider
Database
Activity Activity
Activity
#E1 #E2
Register or
#E3
Search the capability
MDM #a
class structure
Modeling
(apply ISO 16100)
Capability Class
MDD #aa
Structure #X
Capability Class
Structure #N
Capability
Capability Capability
Class #A
Class #B Class #D
Capability
refer
Class Capability
Capability
Class #F
Structure #1 Class #E
or
Capability CapabCapabilitilityy
refer
Class #B1 CCllasasss #B #B2 2
Capability
register
Class
Capability
Capability
Capability
Capability Class #E1
Class #E2
Class #E3
Class
Structure #2 register
Make templates
Capability Capability
Template #A Template #A
refer
Capability Capability
Template #B Template #D
refer
or
Capability
Capability
Capability
Capability Template #E3
Template #E
register
Template #B Template #B
register
Template
template
Profile
Capability
profile
Profiling
Profile #D
input Capability
Capability
input
Template #E3
register Capability Profile
Capability Capability Capability
Profile #B
Matcher
Profile #A Profile #B Profile #D
output
Capability
Capability
Capability
Profile #G
Profile #B1 Usable MSUs
Profile #B2
integrate MSUs
Manufacturing Application #N

Figure 1 ― Concept of profile matching using multiple capability class structures
© ISO 2009 – All rights reserved 3

---------------------- Page: 8 ----------------------
ISO 16100-5:2009(E)
5.2 Reuse of MSUs
To increase the efficiency of manufacturing application development, MSUs previously deployed in a similar
manufacturing application should be reused. The MSU user shall only consider as candidates for reuse those
MSUs whose capability profiles (see left side of Figure 1) meet his defined matching criteria for its capability
profile (see right side of Figure 1). This part of ISO 16100 specifies a profile matching process wherein the
capability class structures of the profiles being matched can be different, thus resulting in a larger number of
candidate MSUs for reuse.
5.3 Registration of MSUs
A MSU provider registers an MSU so that it is widely available to many potential users of the MSU. The MSU
provider shall perform the following procedures to prepare and register an MSU.
a) Analyze the set of activities that the MSU enables. The MSU can enable one or more activities.
b) Identify the capability class corresponding to each activity and search for the associated CCS to which
the capability class belongs. If an MSU provides capabilities for two or more activities, those activities
can belong to the same CCS or the different CCS.
c) Select the capability template for each capability class identified.
d) If there is no suitable CCS, construct the appropriate CCS and register it using appropriate database
management methods. Then, generate the corresponding template and register that similarly.
e) Create the MSU capability profile by filling in the template(s) selected in procedure (c) or the new
template(s) created in procedure (d), and register the template(s) using appropriate database
management methods.
5.4 Applying reusable MSUs to meet requirements of a new manufacturing application
When a new manufacturing application is developed, the MSU user shall perform the following procedures.
a) Analyze the functional capability requirements of the manufacturing application and create an activity
tree.
b) Create a CCS using existing or new capability classes to match the activity tree created in procedure
(a), or select an existing CCS by using the methodology of ISO 16100-2.
c) For each capability class in the created or selected CCS, fill in the corresponding capability class
template to create the set of required capability profiles.
d) Using a Type 2 capability profile matcher as described in ISO 16100-3, compare the set of required
capability profiles to the available set of MSU capability profiles to find a set of existing MSUs that
matches the set of required capability profiles.
e) Select the set of existing MSUs that meets the requirements of the new manufacturing application.
f) If the set of MSUs that meets the requirements is not found, develop a set of missing MSUs.
g) Combine the set of reused MSUs from procedure (e) and any set of developed MSUs from procedure
(f) to meet the requirements of the new manufacturing application.
Figure 2 shows the implementation of the concept in Figure 1 to develop a new manufacturing application.
4 © ISO 2009 – All rights reserved

---------------------- Page: 9 ----------------------
ISO 16100-5:2009(E)
Flow for developing
Flow for registering existing MSU
new manufacturing application
Requirementsof the manufacturing application
Specification of existing MSU
Analyze requirements for manufacturing application
Consider use case of existing MSU
Manufacturing Domain Model
Consider activity tree of manufacturing application
Make capability class structure
Make capability class structure
Capability Class Structure
Manufacturing Domain Data
Make Capability Templates
Make Capability Templates
Capability Template
Profiling (fill in templates)
Profiling (fill in templates)
Required Capability Profile
Type 2 Matcher
MSU’s Capability Profile
Comparison with the existing capability profiles
(see Figure 12 for detail)
Register Capabiilty Templates
[find same capability profiles]
[could not find same capability profiles]
Reuse existing MSU
Develop new MSU
New MSU

Existing MSU
Develop manufacturing application

Figure 2 ― Application development process with capability template, capability profile, and CCS
© ISO 2009 – All rights reserved 5

---------------------- Page: 10 ----------------------
ISO 16100-5:2009(E)
5.5 Manufacturing Domain Data
Figure 3 shows the MDD, MDM, CCS, Capability Class and their associations with the other manufacturing
domain elements.
Manufacturing Domain
1
1
+contains
1.*
-represents
Manufacturing Application
1
Manufacturing Domain Model
1 11
*
Manufacturing Information
1 -enables
1
-enables
1.* 1.*
1
1
Capability Class Structure Manufacturing Process
-constrains
1 1
-describes
1
1
*
-sequences
Exchanged Application Information 1.*
Manufacturing Resource
*
-constrains
-constrains
*
-constrains
1.*
Manufacturing Activity
*
*
Capability Class
1
1
-maps
*
-enables
+constrains
-organizes
1
1
1.*
1.*
*
1
Manufacturing Function
Manufacturing Domain Data
1.*
-access

Figure 3 ― Relationship between manufacturing domain and manufacturing application
MDDs represent different types of manufacturing information, including those that are exchanged between the
resources within an application and between applications.
Figure 4 shows an example of a structure of a MDM with multiple MDDs. The process an MDM creator follows
to create an MDM and MDDs is described in Annex A.
6 © ISO 2009 – All rights reserved

---------------------- Page: 11 ----------------------
ISO 16100-5:2009(E)
MDM #1
Relationship #1 MDD #B
1
MDD #A
-attribute B-1
Role 1A
-attribute A-1 Role 1B*
-attribute B-2
-attribute B-3
-attribute A-2
Role 2A Role 3A
1 1
Relationship #3
Relationship #2
Role 2C Role 3D
1 1.*
MDD #C
MDD #D
Role 4D Role 6D
-attribute C-1
-attribute D-1
-attribute C-2
-attribute C-3
Role 5D
Relationship #4 Relationship #5 Relationship #6
Role 4E Role 5F Role 6G
MDD #E MDD #F MDD #G
-attribute E-1 -attribute F-1 -attribute G-1
-attribute F-2

Figure 4 ― Example structure of a MDM
Within a specific manufacturing domain, the MDM creator can represent a manufacturing application as a set
of MDDs. An MDD provides information about various aspects of a manufacturing application such as:
a) manufacturing resources (e.g. MSU, equipment, automation devices, personnel, material, work-in-
process inventory);
b) manufacturing processes (e.g. operations, activities);
c) manufacturing information exchanged (e.g. product data, recipe, manufacturing data, quality data);
d) relationships among the resources, processes and information exchanged.(e.g. data flow, network
configuration, work flow).
In Figure 5, each MDD within a specific manufacturing domain consists of attributes and a set of relationships
with other MDDs in the same domain using a relationship class. The relationship constraint and relationship
type attributes in the relationship class delineate the allowed relationships among the MDDs within the specific
MDM. The MDM creator shall descriptively name the MDD exchanged among manufacturing functions or
among manufacturing activities such that each MDD is unique in the target manufacturing domain.




© ISO 2009 – All rights reserved 7

---------------------- Page: 12 ----------------------
ISO 16100-5:2009(E)
MDM in specific manufacturing domain




1 1
contains contains

2.* 1.*

Relationship between two MDDs
MDD in specific manufacturing domain
attribute 1 - relationship name

relates
- relationship type
…
- relationship constraint
attribute x
2 1.*
- role name

- direction
- multiplicity

Figure 5 ― Relationship between MDD and MDM
Figure 5 shows the relationship between a MDM and a minimum of two MDDs. These MDDs can typically
form tree structures and have their relationships constrained by the relationship class noted in Figure 5. There
is also the possibility of implementing specific class definitions specified as external classes from some related
standards applicable to a particular manufacturing domain.
5.6 Mapping capability classes to MDDs
The MSU provider or MSU user models his activity tree based on the MDM from the requirements of the
manufacturing application. The MSU provider or MSU user shall, in order to distinguish a particular activity in
an activity tree, label an activity with an unambiguous and unique name, along with semantic information
expressed in terms of a sequence of MDDs. The activities in the activity tree form the CCS. MSU providers
and manufacturing application developers specify capability classes using a common set of MDDs.
Figure 6 shows two different CCSs mapped from their respective manufacturing activity trees. CCS #1 and
CCS #2 are distinct structures, with some of the capability classes in the two CCSs being the same. These
same capability classes can be recognized when a capability profile corresponding to a capability class is
described using MDDs from the same MDM.
Each capability class in a structure is formed based on the services of a MDD or combined MDDs in the MDM.
The canonical expression of a capability class includes specific lists of attributes, methods, and resources.
8 © ISO 2009 – All rights reserved

---------------------- Page: 13 ----------------------
ISO 16100-5:2009(E)
Capability Class Structure #1 Capability Class Structure #2
Manufacturing Application
Manufacturing Application
Class#2
Class #1
Capability
Capability
Capability Capability Capability Class #B Class #E
Class #A Class #B Class #D
Capability Capability
Class # B1 Class #B3
Capability Capability
Class #B1 Class #B2
Capability Capability
Class #B11 Class #B12
Capability Capability
Capability Capability
Class #B11
Class #B12
Class #B122
Class #B121
MDD #1 MDD #2 MDD #3 MDD #4 MDD #5 MDD #6 MDD #n
……………
Manufacturing Domain Model

Figure 6 ― Multiple capability classes described using MDDs from the same MDM
6 Methods and rules for capability profiling
6.1 Templates for MSU capability profiling
The following four templates are used in MSU capability profiling when there are multiple capability class
structures:
a) CCS template;
b) Capability template;
c) MDM template;
d) MDD template.
6.2 CCS template
6.2.1 Conceptual structure
The CCS template shall contain, at a minimum, the following elements:
a) CCS Creator Name;
b) CCS ID;
c) ID for each capability class;
d) Parent Node ID for each capability class (the root node has no value for its Parent Node ID);
© ISO 2009 – All rights reserved 9

---------------------- Page: 14 ----------------------
ISO 16100-5:2009(E)
e) Child Node ID(s) for each capability class.
Figure 7 shows a conceptual structure of a CCS template.
CCS Creator Name
CCS ID
CCS Root Node ID
Capability Class ID
Parent Node ID(s)
Child Node ID(s)
Figure 7 ― Conceptual structure of a CCS template
6.2.2 Formal structure
The MSU provider or MSU user shall describe CCS templates using XML schemas. The formal structure of
the CCS template shall be as follows.



 
 
  
  
   
  
  
  
  
   
  
  
  
  
   
  
  
  
 
 


 
 
  
  
  
 
 
  
  
   
  
  
 
 
  
  
   
     
   
   
  
  
10 © ISO 2009 – All rights reserved

---------------------- Page: 15 ----------------------
ISO 16100-5:2009(E)
 
 



6.3 Capability profile template
6.3.1 Conceptual structure
A capability profile template shall contain a Common Part in accordance with ISO 16100-2:2003, 6.3, and
ISO 16100-3:2005, 7.2.2, and a Specific Part in accordance with ISO 16100-2:2003, 6.3. The Specific Part
shall, at a minimum, contain the elements identified in ISO 16100-2 along with the following additional elements:
a) Reference MDM Name;
b) MDD Description Format (e.g. list of MDD objects);
c) MDD Description (e.g. time ordered access to MDD objects).
Figure 8 shows a conceptual structure of a capability profile template.
© ISO 2009 – All rights reserved 11

---------------------- Page: 16 ----------------------
ISO 16100-5:2009(E)

Common Part
Template ID
Capability Class Name and Reference CCS
Software Unit ID
Vendor Name
Version Number & History
Computing Facilities Required
Processor
OperatingSystem&Options
Langu
...