ISO 16100-1:2009

INTERNATIONAL ISO
STANDARD 16100-1
Second edition
2009-12-15
Industrial automation systems and
integration — Manufacturing software
capability profiling for interoperability —
Part 1:
Framework
Systèmes d'automatisation industrielle et intégration — Profil d'aptitude
du logiciel de fabrication pour interopérabilité —
Partie 1: Cadre
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 .iv
Introduction.v
1 Scope.1
2 Normative references.1
3 Terms and definitions .1
4 Abbreviated terms .5
5 Manufacturing application.5
5.1 Reference application framework.5
5.2 Manufacturing domain.6
5.3 Manufacturing processes.7
5.4 Manufacturing resources.7
5.5 Manufacturing information.8
6 Manufacturing software interoperability framework .8
6.1 Manufacturing software unit interoperability .8
6.2 Functional relationships between the manufacturing software units .9
6.3 Services, interfaces and protocols.10
6.4 Manufacturing software unit capability profiling .10
7 Conformance .11
Annex A (informative) Manufacturing application reference model.12
Annex B (informative) Examples of the manufacturing activity reference model.16
Annex C (informative) Use cases .41
Bibliography.45

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-1 was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 5, Architecture, communications and integration frameworks.
This second edition cancels and replaces the first edition (ISO 16100-1:2002), which has been technically
revised.
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 based on multiple capability class structures

iv © ISO 2009 – All rights reserved

Introduction
The motivation for ISO 16100 stems from the industrial and economic environment noted by ISO/TC 184/SC 5.
In particular, there is broad recognition by industry that application software and the expertise to apply that
software are assets of the enterprise. Industry feedback has noted the need for improvement and continued
development of current design and manufacturing standards to enable software interoperability.
ISO 16100 specifies a manufacturing information model that characterizes software-interfacing requirements.
With interfacing requirements clearly expressed, standard interfaces can be more easily and quickly
developed using the Interface Definition Language (IDL) or an appropriate programming language, such as
Java and C++. These standard interfaces are expected to enable the interoperability among manufacturing
software tools (modules or systems).
The Unified Modeling Language (UML) is used in this International Standard for modelling these interfaces.
Also, the manufacturing information model can be used to develop commonly sharable database schema
using languages such as the Extensible Markup Language (XML).
Sectors of the manufacturing industry ⎯ such as automotive, aerospace, machine tool manufacturing,
computer peripheral manufacturing, and mould and die manufacturing ⎯ that intensively use computer-aided
design (CAD), computer-aided manufacturing (CAM), numerical control (NC) programming, computer-aided
engineering (CAE), product data management (PDM) and manufacturing execution systems (MES) will
directly benefit from ISO 16100. The software interface requirements in ISO 16100 will facilitate the
development of:
a) interoperable design and manufacturing software tools leading to shortened product development time;
b) new software tools that can be easily integrated with current technologies leading to more choices in the
market;
c) new application software leading to reduced capital expenditures to replace legacy systems;
d) programming interfaces and database schema leading to cost savings by not having to develop
proprietary interfaces for point-to-point software integration.
The end result will be a reduction in product and manufacturing information management cost and lower
product costs.
ISO 16100 enables manufacturing software integration by providing the following:
⎯ standard interface specifications that allow information exchange among software units in industrial
automation systems developed by different vendors;
⎯ software capability profiling, using a standardized method to enable users to select software units that
meet their functional requirements;
⎯ conformance tests that ensure the integrity of the software integration.
At the time of publication of this edition of this part of ISO 16100, there are five published parts to ISO 16100
and one planned part. This part of ISO 16100 specifies a framework for interoperability of a set of
manufacturing software products used in the manufacturing domain and its integration into a manufacturing
application. ISO 16100-2 specifies a methodology for constructing profiles of manufacturing software
capabilities, and includes a methodology for creating manufacturing software capability profiles as well as for
using these profiles at the developing stage of manufacturing applications. ISO 16100-3 specifies the interface
protocol and templates for various manufacturing application areas. ISO 16100-4 specifies the concepts and
rules for the conformity assessment of the other parts of ISO 16100. ISO 16100-5 specifies a methodology for
profile matching using multiple capability class structures. ISO 16100-6 will specify the interface services and
protocols for matching profiles based on multiple capability class structures.
INTERNATIONAL STANDARD ISO 16100-1:2009(E)

Industrial automation systems and integration — Manufacturing
software capability profiling for interoperability —
Part 1:
Framework
1 Scope
This part of ISO 16100 specifies a framework for the interoperability of a set of software products used in the
manufacturing domain and to facilitate its integration into a manufacturing application (see Annex A for a
discussion of a manufacturing application). This framework addresses information exchange models, software
object models, interfaces, services, protocols, capability profiles and conformance test methods.
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 15745-1, Industrial automation systems and integration — Open systems application integration
framework — Part 1: Generic reference description
ISO 16100 (all parts), Industrial automation systems and integration — Manufacturing software capability
profiling for interoperability
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
advanced planning
production planning over time horizons of months or years using constraint models that treat both materials
and capacity
NOTE In some cases, the planning system includes master production scheduling, material requirements planning or
capacity planning.
3.2
bill of materials
BOM
〈manufacturing〉 list of parts that are scheduled to be manufactured in the factory
NOTE For each part, a BOM contains part number, description, quantity, description, etc. The manufacturing BOM is
the manufacturing version of product structure known as “as-built configuration”.
3.3
CAD/PDM
computer-aided design/product data management
computer systems that are used for product design and modelling, engineering, product data management
and process data management
3.4
capability
〈software〉 set of functions and services with a set of criteria for evaluating the performance of a capability
provider
NOTE This definition differs from that given in ISO 15531-1 and ISO 19439, where capability is defined as the quality
of being able to perform a given activity. See IEC 62264-1 for a general definition of capability.
3.5
capability profiling
selection of a set of offered services defined by a particular interface within a software interoperability
framework
3.6
CAPP/CAM
computer-aided process planning/computer-aided manufacturing
computer systems that are used for process planning and programming of numerically controlled machines
3.7
controller
〈digital systems〉 hybrid hardware/software systems that are used for controlling machines
EXAMPLES Distributed control systems (DCS), programmable logic controllers (PLC), numerical controller (NC), and
supervisory control and data acquisition (SCADA) systems.
3.8
data collection
gathering of information on workpieces, timing, personnel, lots and other critical entities for production
management in a timely manner
3.9
design knowledge
rules and logic that a human designer brings to bear on design problems, including design and
implementation techniques
NOTE Many different types of design knowledge are used in different design activities, such as decomposition
knowledge, assignment knowledge, consolidation knowledge and optimization knowledge.
3.10
design pattern
knowledge of how to convert specifications (e.g. manufacturing capability) into practical forms (e.g. capability
profile template)
3.11
enterprise resource planning
ERP
planning function that includes inventory transaction, cost accounting, order fulfilment and resource tracking
NOTE 1 The planning methodology uses material requirements planning and master production schedule to calculate
requirements for materials and to make recommendations to release replenishment orders when due dates and need
dates are not in phase.
NOTE 2 An alternative definition of enterprise resources planning can be found in ISO 15531-1.
2 © ISO 2009 – All rights reserved

3.12
machine tool
manufacturing resource of the equipment class, associated with a machine, that enables the capability of
machining
3.13
manufacturing application
group of activities (a process or part thereof), within a manufacturing domain of an enterprise, cooperating to
realize a definite objective or role
3.14
manufacturing execution system
MES
system for producing the desired products or services, including quality control, document management, plant
floor dispatching, work-in-process tracking, detailed product routing and tracking, labour reporting, resource
and rework management, production measurement and data collection
NOTE The Object Management Group defines the information part of manufacturing execution systems (MES) as
systems that deliver information enabling “the optimization of production activities from order launch to finished goods.
Using current and accurate data, MES guides, initiates, responds to, and reports on plant activities as they occur. The
resulting rapid response to changing conditions, coupled with a focus on reducing non-value-added activities, drives
effective plant operations and processes. MES improves the return on operational assets as well as on-time delivery,
inventory turns, gross margin and cash flow performance. MES provides mission-critical information about production
activities across the enterprise and supply chain via bi-directional communications.”
3.15
manufacturing software interoperability
ability to share and exchange information using common syntax and semantics to meet an application-specific
functional relationship across a common interface
3.16
manufacturing software
type of software resource within an automation system that provides value to a manufacturing application by
enabling the flow of control and information among the automation system components involved in the
manufacturing processes, between these components and other enterprise resources, and between
enterprises in a supply chain or demand chain
NOTE CAD/PDM is an example of a manufacturing application.
3.17
manufacturing software component
class of manufacturing software resource intended to support the execution of a particular manufacturing task
3.18
manufacturing software unit
class of software resource, consisting of one or more manufacturing software components, performing a
definite function or role within a manufacturing activity while supporting a common information exchange
mechanism with other units
NOTE A software unit can be modelled using UML as a software object.
3.19
manufacturing system
system coordinated by a particular information model to support the execution and control of manufacturing
processes involving the flow of information, material and energy in a manufacturing plant
3.20
manufacturing software capability
set of manufacturing software functions and services against a set of criteria for evaluating performance under
a given set of manufacturing conditions
NOTE Annex C provides use cases and related scenarios involving manufacturing software capability.
3.21
manufacturing software capability profile
concise representation of a manufacturing software capability to meet a requirement of a manufacturing
application
3.22
product data management
PDM
management of a single, centralized data repository that enables authorized users throughout the company to
access and update current product information
NOTE The Object Management Group defines a product data management (PDM) system as a software tool that
manages engineering information, supports management of product configurations, and supports management of the
product engineering process. The engineering information includes both database objects and “document” objects – sets
of information stored in files that are opaque to the PDM system. This information may be associated with specific
products or specific product designs, or more generally with product families, production processes or the engineering
process itself. The engineering process support usually includes workflow management and concepts of engineering
change and notification. In many manufacturing organizations, the PDM is the central engineering information repository
for product development activities.
3.23
software architecture
fundamental organization of a software system embodied in its components, their relationships to each other
and to the environment, and the principles guiding its design and evolution
[IEEE 1471-2000]
3.24
software environment
other manufacturing resources within the computing system that affect the operational aspects of the
manufacturing software unit
NOTE The software environment can include other systems that interact with the system of interest, either directly via
interfaces or indirectly in other ways. The environment determines the boundaries that define the scope of the system of
interest relative to other systems.
3.25
supply chain planning
usage of information technology to address planning and logistics problems at different levels and
granularities of detail using models for a product line, a production plant or a full chain of multiple demand
sources, suppliers, production plants and distribution means
NOTE Supply chain planning can be used to synchronize production, balancing constraints based on goals including
on-time delivery, minimal inventory and maximum profit.
4 © ISO 2009 – All rights reserved

4 Abbreviated terms
AGV Automatic Guided Vehicle
APT Automated Programmed Tool
BOM Bill of Materials
CAD Computer-Aided Design
CAM Computer-Aided Manufacturing
CAPP Computer-Aided Process Planning
ERP Enterprise Resource Planning
MES Manufacturing Execution System
NC Numerical Control
PDM Product Data Management
SCM Supply Chain Management
SCADA Supervisory Control and Data Acquisition
SQC Statistical Quality control
XML Extensible Markup Language
UML Unified Modeling Language
5 Manufacturing application
5.1 Reference application framework
The interoperability framework for manufacturing software is based upon a more general interoperability
framework for manufacturing applications. Such an application interoperability framework, which is explained
in further detail in ISO 15745-1, provides a basis for integrating an automation and control system architecture
within a manufacturing application architecture.
An integrated manufacturing application shall be modelled as a combination of a set of manufacturing
resources and a set of information units whose data structure, semantics and behaviour can be shared and
exchanged among the manufacturing resources, as shown in Figure 1. Manufacturing resources are
communication networks, devices, software, equipment, material and personnel necessary to support the
processes and information exchanges required by the application.
In this application integration model, the various elements of the model have shared interfaces and exchange
material, energy and information in a cooperative and coordinated manner. The manufacturing processes can
cooperate with each other if the functions performed by the various elements of the model can interoperate
with each other. When software units perform some of these functions, it is necessary for the software units to
be interoperable with the other elements, as well as with each other.
Manufacturing
Application
Manufacturing 1.*
Manufacturing
Process
Resource
1.*
Manufacturing Manufacturing
Automation Device
Information
1.*
1.*
Equipment
Manufacturing
and Infrastructure
Personnel
1.* 1.*
Raw Material and
Manufacturing
Manufactured
Software Unit
1.*
1.*
Part
NOTE Boxes represent classes of objects (things). Lines connecting boxes represent associations between objects
(things). An association has two roles (one in each direction). A role may optionally be named by a label. A role from A to
B is closest to B, and vice versa. Roles are one-to-one unless otherwise noted. A role can have a multiplicity, e.g. a role
marked with “1.*” is used to denote many as in a one-to-many or many-to-many association. A diamond at the end of an
association line denotes a part-of relationship. A shaded diamond at the end of an association line denotes a composition
aggregation relationship. The absence of at least one type of aggregated element deletes the object instance of the
composition aggregation class. An unshaded diamond denotes a collection aggregation relationship. An object instance of
a collection aggregation class can be formed even if some of the types of aggregated elements are not present. For
example, Manufacturing Application owns (is comprised of) Manufacturing Process, Manufacturing Information and
Manufacturing Resources. This notation is taken from ISO/IEC 19501.
Figure 1 — Class diagram of a partial model of a manufacturing application
5.2 Manufacturing domain
The manufacturing domain that includes discrete, batch and continuous control encompasses many types of
industries. The automotive industry is an example of an industry employing discrete control; the
pharmaceutical industry is an example of an industry employing batch control; the petrochemical industry is an
example of an industry employing continuous control. For manufacturing software, the interface between plant
management systems and floor control systems is described by the same method regardless of whether
control systems are discrete, batch or continuous. Similarly, the control flow inside a control system is also
described by the same method regardless of whether the system is discrete, batch or continuous.
Even as the manufacturing domain applies to many industries, the relationship between firms in these
industries is changing rapidly due to recent developments in IT infrastructure, as is the case in supply chain
management systems. Therefore, ISO 16100 sets a target manufacturing domain to include the
manufacturing operation and control activity, the discrete control activity, the batch control activity, the
continuous control activity and the manufacturing process design activity, as shown in Figure 2.
6 © ISO 2009 – All rights reserved

Supply Chain
Management
Plant Management
Product Design
Enterprise
Resource
Management
Target
Manufacturing
Operation and Control
Manufacturing
Domain of
Process Design
ISO 16100
Discrete
Continuous
Control
Control
Batch
Control
NOTE The dark grey shaded area delimits the scope of a manufacturing domain in ISO 16100.
Figure 2 — Target domain of ISO 16100
5.3 Manufacturing processes
A manufacturing process shall be modelled as a set of activities that follow a specific sequence. Each activity
shall be associated with a set of functions performed according to a time schedule or triggered by a set of
events.
The functions associated with a manufacturing process shall be viewed as being implemented through a set of
manufacturing resources. The manufacturing resources shall be considered to be selected and configured to
support the material, information and energy flows required by the specified sequence of manufacturing
activities associated with a process.
When a manufacturing process must cooperate and coordinate with another process, the respective functions
of these interacting processes are considered to be able to cooperate and coordinate with each other. Such a
situation requires that the cooperating and coordinating functions meet a common set of criteria and a set of
conditions for interoperability. The software units that implement these functions shall meet a related set of
criteria and conditions for interoperability.
5.4 Manufacturing resources
The manufacturing resources required by a manufacturing application shall be organized in terms of the type
of flow being managed and supported among the manufacturing processes ― material, control, information or
energy flow. The set of integrated flows can be used to represent an integrated manufacturing application or
manufacturing system architecture.
The set of integrated manufacturing resources shall form a manufacturing system architecture that fulfils a set
of manufacturing application requirements. These manufacturing resources, including the manufacturing
software units, shall provide the functions associated with the manufacturing processes.
The combined capabilities of the various software units, in an appropriate operating environment, provide the
required functionality to control and monitor the manufacturing processes according to the production plan and
the allocated resources.
An operating environment shall be distinguished by the manufacturing resources needed by the associated
set of software units. These manufacturing resources include the processing, storage, user interface,
communications and peripheral devices, as well as other system software required for executing the software
units.
5.5 Manufacturing information
A set of information structures shall provide the knowledge infrastructure to manage the various types of flows
within a manufacturing application. These information sets shall include data pertaining to the product, the
process and the equipment.
The manufacturing software units shall be the primary means for handling, transforming and maintaining these
information structures.
6 Manufacturing software interoperability framework
6.1 Manufacturing software unit interoperability
Within a context of a manufacturing application, a manufacturing software unit is considered to be capable of
performing a specific set of functions defined by a manufacturing system architecture. In performing these
sets of functions, the manufacturing software unit is cooperating and conducting transactions with other
manufacturing software units.
The functions performed by each software unit shall be those as described by the manufacturing application
architecture. The information exchanged between these software units shall enable the coordinated execution
of these manufacturing functions.
The software interoperability of a set of manufacturing activities shall be described in terms of the
interoperability of the set of software units associated with each manufacturing activity.
A software interoperability framework consists of a set of elements and rules for describing the capability of
software units to support the requirements of a manufacturing application. The capability to support the
requirements shall cover the ability of the software unit to execute and to exchange data with other software
units operating in the same manufacturing system or in different manufacturing systems used in the
application.
A software interoperability framework shall be based on the following aspects:
a) syntax and semantics shared between manufacturing software units;
b) functional relationships between the manufacturing software units;
c) services, interfaces and protocols offered by the manufacturing software units;
d) ability to provide manufacturing software unit capability profiling.
The framework elements shall consist of the roles, the activities and the artefacts associated with the software
entities when dealing with the manufacturing process, information and resources. The framework rules shall
address the relationships, templates and conformance statements needed to construct a capability class (see
ISO 16100-2), a profile class (see ISO 16100-2) and a component class (see ISO 16100-3). Framework
elements for multiple capability class structures are covered in ISO 16100-5 and ISO 16100-6.
8 © ISO 2009 – All rights reserved

The organization, relationships and tasks pertaining to the software unit and its manufacturing software
components shall be expressed in terms of the relevant framework elements and rules described in other
parts of ISO 16100.
Figure 3 shows the relationships between the aspects of the software interoperability framework and the
derivation of this framework from a generic application interoperability framework.
Software Interoperability Framework
Generic Application Interoperability Framework derived from

(Methodology and Rules for Interoperability)
• Software architecture and design
pattern
 Modelling tools
 Manufacturing software unit
 Languages for syntax and semantics
interfaces, services, protocols
 Generic application interoperability
 Interface definition methodology
model
(formal language)
constrains profiled by
used to create
Software Capability Profiling
Domain Specific Modelling of Functional
 Classes of manufacturing activity,
Relationships
software unit capability, software

capability profile, software
mapped to
 Application model
component
 Information model
 Software functionalities
 Environmental model
 Manufacturing application
interoperability criteria
 Constraints from other
manufacturing resources
 Non-functional properties of the
software unit
 Template(s)
Figure 3 — Relationships of software interoperability aspects
6.2 Functional relationships between the manufacturing software units
Within the manufacturing domain shown in Figure 2, there can be one or more operational software units that
cooperate through a specific interface/protocol to perform a single manufacturing function required in that
domain. This is realized in the software environment of a specific computing system as one of the components
of the manufacturing resources, enabled by a specific design pattern performing a specific role. Conversely, a
single software unit can perform one or more manufacturing functions. One or more manufacturing functions
can interoperate with each other to execute, control, monitor or manage a particular manufacturing activity. A
series of activities can be conducted in a particular sequence to complete a manufacturing process. Figure 4
shows various classes including those used to represent a software unit and its surrounding elements and
associations within an environment of a manufacturing application.
In this framework, the sequence and schedule of functions performed is determined by the sequence and
schedule of the activities that comprise a particular process. The manufacturing software units deployed to
perform the functions are considered to execute according to the required sequence and schedule of their
associated functions.
The interoperability of the manufacturing processes shall be viewed in terms of the interoperability of the
functions, which, in turn, shall be viewed in terms of the interoperability of the manufacturing resources,
including the manufacturing software units. Examples of information flow among design, manufacturing
planning and execution activities are provided in Annex B.
Manufacturing Domain
contains 1.*
Manufacturing Application
enables
1.* 1.*
enables
1.*
Manufacturing Resources
Manufacturing Process
Manufacturing Information
sequences 1.*
1.*
Computing System
Manufacturing Activity
constrains
constrains
operates
1.*
Manufacturing Function
Software Environment
Software Architecture
1.*
Manufacturing Software Unit
enables
Software Design Pattern
Interface / Protocol
Role
Datatype
1.*
Figure 4 — Class diagram of a software unit and its surroundings and associations within a
manufacturing application
A software unit shall be modelled as a set of software components that have been linked to perform a definite
manufacturing function. Each software unit shall be represented as a UML object.
A manufacturing software unit shall provide a service interface for use in its configuration, execution and
maintenance.
The capability of a software unit to perform a manufacturing function shall include a description of the set of
services available at its service interface. The capability of a manufacturing software unit shall be concisely
stated in a capability profile described in XML.
The sequence and timing of the manufacturing activities determines the specified criteria for the
interoperability of the associated set of manufacturing software units.
Information structures included or referenced in a capability profile are defined in ISO 16100-2.
6.3 Services, interfaces and protocols
A manufacturing software unit shall be modelled as a set of manufacturing software components that have
been linked to perform a definite manufacturing function.
Manufacturing software units shall interoperate with one another, in support of a manufacturing activity, when
the services requested by the former can be provided by the latter, using the same operating environment.
The services, interfaces and protocols are defined in ISO 16100-3.
6.4 Manufacturing software unit capability profiling
A concise statement of the capability of a manufacturing software unit shall be expressed using a capability
profile. The capability profile shall include class of manufacturing activity, the software function performed, the
manufacturing application criteria, resource conditions or configurations (software enablers), measurement
10 © ISO 2009 – All rights reserved

units, name of the manufacturing software unit, data exchanged, the service interface and the associated
operating conditions.
EXAMPLE
Class of Manufacturing Activity: Production Control
Software Functions: Scheduling, operation, monitoring, reporting, alarming
Manufacturing application criteria: completeness, timeliness, accuracy
Resource conditions or configurations: operating system peripherals, networks, drivers, performance monitors
Measurement units: Mean Time Between Failure, Mean Time To Repair, Number Of People To Repair (per skill type)
Name of manufacturing software unit: RSI Enterprise Batch
The profile shall provide a minimum level of information and be organized in a format that is XML-based to
address the use cases enumerated in Annex C.
The structure, syntax and taxonomy of manufacturing software capability profiles are defined in ISO 16100-3.
7 Conformance
The concepts and rules for conformity assessment of capability profiles are defined in ISO 16100-4.

Annex A
(informative)
Manufacturing application reference model
A.1 Model of a manufacturing enterprise
A.1.1 Activity domains
The processes within a manufacturing enterprise can be represented as a set of activities (see Figure A.1).
The number of domains and the names may differ from one enterprise model to another. In this part of
ISO 16100, the domain classes defined in the manufacturing enterprise reference architecture noted in
ISO 15704:2000, Clause B.3, will be referenced.

Order
CUSTOMER
Enterprise/Control
Processing
Boundary Product
Shipping
Production
Administration
Scheduling Product Cost
Accounting
Cost
Capacity
Supplier Objectives
Product
Schedule
Performance
and Costs Inventory
Purchase
Manufacturing Control
Order Req.
Procurement
Standards
Operation and
Control
Process Data
Material and
QA Results
Material and
Purchasing
Energy
Energy Inventory
QA Results
Requirements Order Status
Maintenance
Quality
Requests
Work Report, Order
Accounting Assurance
Material and
Requirement
Costs Diagnostic
Know How
Energy Control
Self-Check Requests
Corporate
Marketing
Maintenance
R&D
and Sales
Management
NOTE Figure adapted from IEC 62264-1.
Figure A.1 — Activity diagram of a partial model of a manufacturing application
These activity domains can be organized in a hierarchical fashion, wherein the Production Control activity
domain and its sub-domains can be placed at Level 3 and below, while all the other enterprise activity
domains can be positioned at Level 4 and higher. The hierarchical arrangement of the domains will allow more
detailed treatment of the manufacturing process requirements (see Figure A.2). A different grouping may
result if the target domain were some activity other than Production Control.
The classes of functions to be used in distinguishing a manufacturing software capability can be defined in
terms of the following characteristics:
a) generic activity type;
b) domain category as noted in the principal domains described in this clause and the sub-domains of the
Production Control domain;
c) flow type supported by the associated manufacturing process.
12 © ISO 2009 – All rights reserved

Although different enterprises use different names for the functions in these activity domains and these
domains may have varying functional boundaries, these functions can be distinguished by their input, output
and processing operations. The functions within each sub-domain can be enumerated and these functions are
referenced to distinguish the manufacturing software capability descriptions.

Level 4
Business Planning and Logistic s
Plant Production Scheduling,
Operational Management, etc.
Level 3
Manufacturing
Operations and Contr ol
Dispatching Production, Detailed Production

Scheduling, Reliability Assurance, etc.

Levels
2,1,0
Continuous Discrete
Batch
Control Control
Control
Unit Cell Line
NOTE Figure adapted from IEC 62264-1.
Figure A.2 — Hierarchical arrangement of enterprise domains
A.1.2 Business planning and logistics level
The activity domains within the business planning and logistics level can be grouped as follows:
a) purchasing, procurement and product cost accounting;
b) production scheduling, product inventory control and quality assurance;
c) material and energy flow control and management;
d) marketing and sales, order processing, product shipping management;
e) corporate services, such as accounting, human resources, research and development, information
technology support, legal, standardization and trade.
A.1.3 Customer relationship management
The Customer Relationship Management activity domain includes functions such as marketing, sales,
partnering, integrator support, order processing and other coordination functions.
The Integrated e-Commerce activity sub-domain involves functions such as electronic data interchange, web
ordering, business-to-business electronic storefront and business-to-consumer electronic storefront.
A.2 Corporate services
The Accounting activity sub-domain involves functions such as general ledger, bank book, accounts
receivable, accounts payable, currency management, assets depreciation and other financial transaction
support.
The Quoting and Estimating sub-domain involves functions such as standard product routing, labour
performance and shop floor cost control.
The Human Resource Management activity domain includes functions such as payroll, human resources
support, time and attendance, organizational chart maintenance, applicant handling, and employee training
and retention.
A.3 Material and energy management
The Material and Energy Planning and Control activity sub-domain involves functions such as bill of material,
production order processing, master scheduling and material requirements planning.
The Advanced Materials Management sub-domain involves functions such as returned material authorization,
advanced distribution, serial lot management, shipping, RF data collection for distribution, and request for
quotation.
The Capacity Requirements Planning sub-domain involves functions such as manufacturing cost accounting
and standard product costing.
The Distribution activity sub-domain involves functions such as inventory management, order entry, purchase
order and receiving, traffic and transportation, and packaging and labelling for distribution.
A.4 Engineering support
The Engineering Support activity domain involves functions of product design, process design engineering,
installation and support, such as engineering change management, facility environmental management and
monitoring.
A.5 Manufacturing operations and control level
The Production C
...