ISO/PRF 21175-1

International
Standard
ISO 21175-1
First edition
Automation systems and
integration — Collaboration
environment requirements
of simulation on different
manufacturing platforms —
Part 1:
Reference model and process
PROOF/ÉPREUVE
Reference number
ISO 21175-1:2026(en) © ISO 2026

ISO 21175-1:2026(en)
© ISO 2026
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
PROOF/ÉPREUVE
ii
ISO 21175-1:2026(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Conformance . 3
6 General framework of CMSE . 3
7 Joint simulation project analysing . 6
8 Joint simulation project realizing . 7
8.1 General .7
8.2 Business and system describing .8
8.3 Software collaboration implementing . .9
8.4 Infrastructure collaboration supporting .11
Annex A (informative) Application of CMSE in the functional hierarchy of IEC 62264-1 . 14
Annex B (informative) Example of use of CMSE in joint simulation project .16
Annex C (informative) The Legend of OPM .29
Bibliography .31
PROOF/ÉPREUVE
iii
ISO 21175-1:2026(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 5, Interoperability, integration, and architectures for enterprise systems and automation
applications.
A list of all parts in the ISO 21175 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
PROOF/ÉPREUVE
iv
ISO 21175-1:2026(en)
Introduction
Open, sharing and self-organization on demand among group enterprises or small and medium-sized
enterprises (SMEs) of manufacturing in the product full life cycle is the trend for the future which calls
for deep collaboration within or among enterprises especially simulation-oriented model collaboration.
At present, collaboration within or among enterprises has developed from simple information-based
collaboration, drawing based collaboration, 3D model-based collaboration to simulation-oriented model
collaboration. Simulation-oriented model collaboration can support global enterprises, virtual enterprises
in industrial cluster and integrated product teams within enterprise to carry out joint innovation, complex
product research and development, virtual fabricate/test/operation/maintenance and other activities in the
product full life cycle, which is of great significance to innovate products and improve their time (to market),
[1]
quality, cost, and service, etc. .
Nowadays, an expanding trend about all kinds of simulation-oriented model collaboration related activities
in the functional hierarchy of manufacturing systems can be observed. In the activities of business planning
and logistics, simulation-oriented model collaboration among different enterprise stakeholders is needed
to improve plant production scheduling, operational management, etc. In the activities of manufacturing
operations management, simulation-oriented model collaboration among different enterprise or department
stakeholders is needed to improve dispatching production, detailed production scheduling, etc. In the
activities of batch control, continuous control and discrete control, simulation-oriented model collaboration
among different department stakeholders is still needed to improve prediction and optimization.
In particular, with the deepening applications of technologies in the manufacturing system such as model
based system engineering, model engineering, cyber-physical system, digital twin, cognition and decision
[2-4]
intelligence (based on the deep reinforcement learning especially) which increase the requirements of
simulation-oriented model collaboration upon different manufacturing platforms. First, the development
scope of the simulation has expanded from the traditional Local Area Network to the global Internet.
Second, the deployment place of the simulation has expanded from the traditional desktop to the pervasive
terminal. Meanwhile, the operation form of the simulation has expanded from the traditional off-line small-
scale sequential verification to the on-line large-scale parallel analysis on demand.
The prerequisite for simulation-oriented model collaboration is simulation interoperability which now is
covered by several existing standards or specifications supporting distributed interactive simulation system
[5,6] [7]
like Discrete Event System Specification (DEVS) , Distributed Interactive Simulation (DIS) , High Level
[8] [9]
Architecture (HLA) , Test and Training Enabling Architecture (TENA) , Functional Mock-up Interface
[10-13] [14]
(FMI)/System Structure and Parameterization (SSP) , Distributed Co-Simulation Protocol (DCP) and
[15] [16]
FIWARE . The Distributed Simulation Engineering and Execution Process (DSEEP) standard describes
the different development steps of a distributed interactive simulation system which is independent of any
distributed interactive simulation architecture like HLA or DIS. However, there are no formal standards
existing for a kind of environment where all kinds of stakeholders involved in the joint simulation project
could improve collaboration to enable on-demand simulation at any time and any place upon different
manufacturing platforms with different infrastructures, operating systems, simulation middleware. The
common problems that exist in the current implementation of joint simulation projects include requesting
the infrastructure device by phone, integrating the software / model offline, and running the simulation
system manually, which bring great inconvenience to the projects. Therefore, a new standard required
for shielding distribution and heterogeneity of them to enable service-oriented share-use, integration and
collaboration, by providing the semantic and pragmatic guarantee plus the general and neutral interface
definition.
This document specifies the reference model (including collaboration environment meta-model and
collaboration environment interface) and the reference process (including joint simulation project analysing,
joint simulation project realizing with the steps of business and system describing, software collaboration
implementing and infrastructure collaboration supporting) of the collaborative modeling and simulation
environment to promote the solution formulation of joint simulation projects.
The annexes provide additional information. Annex A introduces the functional hierarchy defined in
[17]
IEC 62264-1 and its relationship with this document. Annex B shows an example of using collaborative
modelling and simulation environment in a joint simulation project. Annex C illustrates the legend of OPM
used in this document.
PROOF/ÉPREUVE
v
International Standard ISO 21175-1:2026(en)
Automation systems and integration — Collaboration
environment requirements of simulation on different
manufacturing platforms —
Part 1:
Reference model and process
1 Scope
The purpose of this document is to specify a reference model and process for Collaborative Modeling and
Simulation Environment (CMSE), which establishes a general framework of CMSE to provide guidance for
implementation of joint simulation projects. The CMSE which is based on the reference process and the
reference model including neutral interfaces and meta-models can enable service-oriented share-use of
the infrastructure, integration of the software and collaboration of the business to improve collaboration
among all kinds of stakeholders involved in a joint simulation project which needs on-demand simulation
at any time and any place upon different manufacturing platforms owned by different enterprises or by
different departments within an enterprise.
This document can not only be applied to manufacturing enterprises but also be applied to other kinds
of enterprises. It is intended for use by stakeholders who are concerned with developing and deploying
solutions of the joint simulation project based on information and communication technology. It focuses
on simulation activities related cross-platform simulation collaboration capability supporting business
planning and logistics, manufacturing operations management and production control within or among
enterprises, which can cover the levels from 2 to 4 of the functional hierarchy of manufacturing systems in
[28]
IEC 62264-3 .
This document specifies the following:
— the general framework of CMSE;
— the methodology of the joint simulation project analysis and realization by CMSE.
This document does not relate to the simulation irrelevant collaboration environment, and does not specify
the specific approach to implement CMSE in the solution formulation of joint simulation projects.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
3.1
simulation
use of a similar or equivalent system to imitate a real system, so that it behaves like or appears to be the real
system
[18]
[SOURCE: ISO 16781:2021, 3.1.9]
3.2
simulation collaboration
process of two or more participants of a simulation activity working together to complete a simulation task
Note 1 to entry: Collaboration is the process of two or more people, entities or organizations working together to
complete a task or achieve a goal. Simulation collaboration includes three aspects: collaborative modeling, collaborative
simulation and collaborative evaluation.
[19]
[SOURCE: IEEE 1730-2022 ]
3.3
platform
combination of an operating system and hardware that makes up the operating environment in which a
program runs
Note 1 to entry: The platform includes infrastructure, operating system, simulation middleware which are depending
on a simulation activity.
[20]
[SOURCE: ISO/IEC/IEEE 26513:2017, 3.30]
3.4
collaboration environment
kind of software system which enables service-oriented share-use, integration and collaboration upon
different manufacturing platforms, by providing the semantic and pragmatic guarantee plus the general and
neutral interface definition, based on the interoperability of the manufacturing platforms
Note 1 to entry: Interoperability defined in ISO/TS 15926-8 is about ability of different types of computers, networks,
operating systems, and applications to work together effectively, without prior communication, in order to exchange
information in a useful and meaningful manner.
4 Abbreviated terms
DIS distributed interactive simulation
HLA high level architecture
TENA test and training enabling architecture
CMSE collaborative modeling and simulation environment
DEVS discrete event system specification
SES system entity structure
OPM object process methodology
OPD object process diagram
OPL object process language
M&S modeling and simulation
FMI functional mock-up interface
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
DCP distributed co-simulation protocol
DSEEP distributed simulation engineering and execution process
5 Conformance
In order to claim conformity with this document, any particular CMSE in the solution formulation of joint
simulation projects shall be able to be positioned within the general framework defined in this document.
This positioning shall consist of joint simulation project analysing and joint simulation project realizing
which includes the business and system describing, software collaboration implementing and infrastructure
collaboration supporting.
This document conforms with ISO 19450 and with ISO 17649, which was established following the
realization that the next generation of standards needs to be not only machine-readable, but also executable,
so they can be tested and validated for completeness, coherence, and consistence, both within each standard
and across related standards.
6 General framework of CMSE
The general framework of CMSE proposed in this document includes “collaborative modeling and simulation
environment reference model and process enabling”, which is the main process of this document.
Figure 1 is the OPM (ISO 19450) system diagram (SD) of the system specified in this document. This process
fully utilizes the simulation environment reference model and process to promote the solution formulation
of the joint simulation project, as specified in this document.
The joint simulation project can be changed by the process “collaborative modeling and simulation
environment reference model and process enabling” from rigid to flexible. The cross-platform simulation
collaboration capability of joint simulation project can be improved from low to high by the process. The
simulation collaboration reference model and process which support the process exhibit cross-platform
simulation collaboration capability of joint simulation project at state “high”. And simulation stakeholder
group handles “collaborative modeling and simulation environment reference model and process enabling”
and participates in the joint simulation project. The joint simulation project encapsulates or selects
simulation services which response to collaborative environment interface.
Figure 1 — OPM (ISO 19450) top-level system diagram of CMSE
The OPL corresponding to Figure 1 is as follows:
1. Cross-platform simulation collaboration capability of joint simulation project can be high or low.
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
2. Joint simulation project can be flexible or rigid.
3. Simulation stakeholder group participates in joint simulation project.
4. Simulation collaboration reference model and process consists of collaborative modeling and simulation
environment reference model and collaborative modeling and simulation environment reference
process.
5. Collaborative modeling and simulation environment reference model consists of collaborative
environment interface and collaborative environment meta-model.
6. Joint simulation project exhibits cross-platform simulation collaboration capability.
7. Simulation collaboration reference model and process exhibits cross-platform simulation collaboration
capability of joint simulation project with value high.
8. Joint simulation project encapsulate/select collaborative environment services.
9. Collaborative environment services provide services to collaborative environment interface.
10. Collaborative modeling and simulation environment reference model and process enabling changes
cross-platform simulation collaboration capability of joint simulation project from low to high.
11. Collaborative modeling and simulation environment reference model and process enabling changes
joint simulation project from rigid to flexible.
12. Simulation stakeholder group handles collaborative modeling and simulation environment reference
model and process enabling.
13. Collaborative modeling and simulation environment reference model and process enabling requires
simulation collaboration reference model and process.
14. Collaborative modeling and simulation environment reference model and process enabling yields M&S
objectives and project goals.
In Figure 2, “collaborative modeling and simulation environment reference model and process enabling” is
in-zoomed in the OPD. This diagram shows that the “collaborative modeling and simulation environment
reference model and process enabling” has four sub-processes: “project goals deciding”, “modeling and
simulation (M&S) objectives deciding”, “joint simulation project analysing” and “joint simulation project
realizing”. “project goals deciding” yields “project goals”, which can be expressed at levels 2-4 of the
IEC 62264-1 functional hierarchy (see Annex A). “M&S objectives deciding” uses the project goals to develop
a set of M&S objectives, or measures of effectiveness, used to drive the M&S experiment. “joint simulation
project analysing” requires M&S objectives and yields “structured task list”. The last sub-process “joint
simulation project realizing” gets the structured task list and turns the joint simulation project from flexible
to rigid. Meanwhile, it also turns the cross-platform simulation collaboration capability to state high. The
structured task list directs the joint simulation project.
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
Figure 2 — SD1: The main process in Figure 1 in-zoomed, exposing four sub-processes
The OPL corresponding to Figure 2 is as follows:
1. Collaborative modeling and simulation environment reference model and process enabling from SD
zooms in SD1 into project goals deciding, M&S objectives deciding, joint simulation project analysing,
and joint simulation project realizing, which occur in that time sequence.
2. Cross-platform simulation collaboration capability of joint simulation project can be high or low.
3. Joint simulation project can be flexible or rigid.
4. Structured task list directs joint simulation project.
5. Joint simulation project exhibits cross-platform simulation collaboration capability.
6. Simulation collaboration reference model and process exhibits cross-platform simulation collaboration
capability of joint simulation project with value high.
7. Simulation stakeholder group handles collaborative modeling and simulation environment reference
model and process enabling.
8. Collaborative modeling and simulation environment reference model and process enabling requires
simulation collaboration reference model and process.
9. Joint simulation project analysing requires M&S objectives.
10. Joint simulation project analysing yields structured task list.
11. Joint simulation project realizing changes joint simulation project from rigid to flexible.
12. Joint simulation project realizing requires structured task list.
13. Joint simulation project realizing changes cross-platform simulation collaboration capability of joint
simulation project to state high.
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
14. M&S objectives deciding requires project goals.
15. M&S objectives deciding yields M&S objectives.
16. Project goals deciding changes cross-platform simulation collaboration capability of joint simulation
project from state low.
17. Project goals deciding yields project goals.
7 Joint simulation project analysing
The “joint simulation project analysing” is in-zoomed in the OPD in Figure 3. This process, which requires
M&S objectives, involves four sub-processes which include “participant identifying”, “structure analysing”,
“behaviour analysing” and “model construction analysing”. The description of each sub-process and related
objects is expressed in the OPL in Figure 3. The sub-process “participant identifying” yields participants list
while the sub-process “structure analysing” obtains objects list. The “behaviour analysing” requires objects
list and produces process list. The last sub-process “model construction analysing” requires both objects list
and process list and yields model list. participants list, objects list, process list and model list are the parts
of structured task list.
Figure 3 — SD1.1: Joint simulation project analysing in-zoomed
The OPL corresponding to Figure 3 is as follows:
1. Joint simulation project analysing from SD1 zooms in SD1.1 into participant identifying, structure
analysing, behaviour analysing, and model construction analysing, which occur in that time sequence.
2. Structure task list consists of model list, objects list, participants list, and process list.
3. Joint simulation project analysing requires M&S objectives.
4. Participant identifying yields participants list.
5. Structure analysing yields objects list.
6. Model construction analysing requires objects list and process list.
7. Model construction analysing yields model list.
8. Behaviour analysing requires objects list.
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
9. Behaviour analysing yields process list.
8 Joint simulation project realizing
8.1 General
The “joint simulation project realizing” is in-zoomed in the OPD in Figure 4. This process involves three
sub-processes which include “business and system describing”, “software collaboration implementing” and
“infrastructure collaboration supporting”. A description of each sub-process and related objects appear in the
OPL below. “business and system describing” requires structured task list to yields business description and
simulation model description, and “software collaboration implementing” requires these two descriptions
to yield simulation software system. The last process, “infrastructure collaboration supporting”, requires
all three products to yields joint simulation project upon the different infrastructure of the manufacturing
platform at state “flexible”. It should be noted that the “joint simulation project realizing” does not specify
an architecture, and the suitable architecture shall be proposed after fully considering all the aspects of the
business and system.
Figure 4 — SD1.2: Joint simulation project realizing in-zoomed
The OPL corresponding to Figure 4 is as follows:
1. Joint simulation project realizing from SD1 zooms in SD1.2 into business and system describing,
software collaboration implementing, and infrastructure collaboration supporting, which occur in that
time sequence.
2. Joint simulation project can be flexible or rigid.
3. Simulation software system can be deployed or undeployed.
4. Joint simulation project realizing consumes joint simulation project at state rigid.
5. Business and system describing requires structured task list.
6. Business and system describing yields business description and simulation model description.
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
7. Software collaboration implementing requires business description and simulation model description.
8. Software collaboration implementing yields simulation software system.
9. Infrastructure collaboration supporting requires business description and simulation software system.
10. Infrastructure collaboration supporting yields joint simulation project at state flexible.
8.2 Business and system describing
The “business and system describing” is in-zoomed in the OPD in Figure 5. Process “business and system
describing” consists of five sub-processes: “process interaction relationship and method describing”,
“process interaction content describing”, “process resource requirement describing”, “simulation system
describing” and “description documents distributing”. The first three sub-processes require collaborative
environment meta-model and process list and create the different parts of the process description which is
divided into two parts: modeling description such as SES and simulation and evaluation description including
[21,22]
experimental frame-system and M&S objectives . The fourth sub-process requires model list to create
the simulation model description. The last sub-process requires business description and simulation model
description and yields documents required by each of the stakeholders. The specified relationship of sub-
processes and objects is shown in the OPL below.
Figure 5 — SD1.2.1: Business and system describing in-zoomed
NOTE Interaction information is transferred between simulation processes, and the earlier process transfers the
experimental results to the latter process as the initial conditions. Data transmission (and feedback) also is conducted
among the modeling, simulation, and evaluation sub-processes within the simulation process. Collaborative modeling
and simulation or evaluation sub-processes are carried out by the simulation stakeholder group.
The OPL corresponding to Figure 5 is as follows:
1. Business and system describing from SD1.2 zooms in SD1.2.1 into process interaction relationship and
method describing, process interaction content describing, process resource requirement describing,
simulation system describing, and description documents distributing, which occur in that time
sequence.
2. Process description consists of constraint description, identification and indicator description, input/
output content description, and resource requirement description.
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
3. Collaborative environment meta-model consists of interaction information, interaction relationship and
interaction method, and resource requirement.
4. Interaction relationship and interaction method consists of interaction method and interaction
relationship.
5. Interaction information consists of evaluation result, experiment, identifier, model, parameter, scenario,
and simulation data.
6. Business description consists of process description.
7. Modeling description and simulation and evaluation description are process descriptions.
8. Collaborative evaluation, collaborative modeling, collaborative simulation, and workflow are interaction
methods.
9. Simulation and evaluation description consists of M&S objectives and experimental frame-system.
10. Experimental frame-system evaluates M&S objectives.
11. Modeling description consists of SES.
12. Structured task list consists of model list and process list and two more parts.
13. Process interaction relationship and method describing requires interaction relationship and interaction
method and process list.
14. Process interaction relationship and method describing yields constraint description.
15. Process interaction content describing requires interaction information and process list.
16. Process interaction content describing yields identification and indicator description and input/output
content description.
17. Process resource requirement describing requires process list and resource requirement.
18. Process resource requirement describing yields resource requirement description.
19. Simulation system describing requires model list.
20. Simulation system describing yields simulation model description.
21. Description documents distributing requires business description and simulation model description.
22. Description documents distributing yields documents required by each of the stakeholders.
8.3 Software collaboration implementing
This document follows the service-oriented approach and focuses on providing a neutral interface to support
the approach. The software service to which the interface belongs, and the relationship of the service and
the interface have been specified.
“software collaboration implementing” is in-zoomed in the OPD in Figure 6. The process “software
collaboration implementing” is zoomed into “interaction technology selecting”, “activities encapsulating”,
“services integrating”, and “system orchestrating”, which occurs in that time sequence to achieve
encapsulation of the simulation software as the simulation service, and integration of the simulation services
as simulation system. “software collaboration implementing” requires interface of encapsulation and
interface of interaction, which forms collaborative environment interface with other eight interfaces. It also
requires business description and simulation model description. “interaction technology selecting” requires
interface of interaction and yields middleware/protocol such as DEVS, DIS, HLA, TENA, Functional Mock-up
Interface/System Structure and Parameterization, Distributed Co-Simulation Protocol, FIWARE. “activities
encapsulating” requires interface of encapsulation as well as middleware/protocol and yields simulation
software services. When it comes to existing services, “activities encapsulating” goes to “reusable software
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
services selecting”. And it goes to “new software service encapsulating” while the service is new. “services
integrating” requires middleware/protocol and simulation software services to yield bonded service set.
“system orchestrating” requires bonded service set to yield simulation software system as the form of
distributed interactive simulation system.
Figure 6 — SD1.2.2: Software collaboration implementing in-zoomed
The OPL corresponding to Figure 6 is as follows:
1. Software collaboration implementing from SD1.2 zooms in SD1.2.2 into interaction technology selecting,
activities encapsulating, reusable software services selecting, new software service encapsulating,
services integrating, and system orchestrating, which occur in that time sequence.
2. Simulation software system can be deployed or undeployed.
3. Simulation software services can be existing or new.
4. Collaborative environment interface consists of interface of encapsulating and interface of interaction
and 9 more parts.
5. DCP, DEVS, DIS, FIWARE, FMI/SSP, HLA and TENA are middleware/protocol.
6. Simulation software services relates to collaborative environment interface.
7. Simulation software supports simulation software services.
8. Software collaboration implementing requires business description and simulation model description.
9. Interaction technology selecting requires interface of interaction.
10. Interaction technology selecting yields middleware/protocol.
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
11. Activities encapsulating requires interface of encapsulation and middleware/protocol.
12. New software service encapsulating yields simulation software services at state new.
13. Reusable software services selecting requires simulation software services at state existing.
14. Activities encapsulating yields simulation software services.
15. Services integrating requires middleware/protocol and simulation software services.
16. Services integrating yields bonded service set.
17. System orchestrating requires bonded service set.
18. System orchestrating yields simulation software system.
In terms of the manner of implementation, two different cases were in consideration. In the first case, the
software collaboration implementing is only for the current joint simulation project. In this case, the software
collaboration implementing is performed manually. In the second case, the “activities encapsulating”, “service
integrating” and “service orchestrating” could be done with combination of corresponding components built
in other projects. In this case, the software collaboration implementing could be performed automatically.
8.4 Infrastructure collaboration supporting
“infrastructure collaboration supporting” is in-zoomed in the OPD in Figure 7. This process consists of ten
sub-processes: “infrastructure services selecting”, “deploying”, “registering”, “instancing”, “simulation
starting”, “runtime monitoring and controlling”, “result set retrieving”, “instance removing”, “deregistering”
and “clearing” as shown in the diagram. “infrastructure services selecting” requires the infrastructure
services, which response to collaborative environment interface, and changes the infrastructure services
from unselected to selected. Based on the infrastructure which is the hardware system of the manufacturing
platform including simulation computer, digital twins corresponding actual system, semi physical simulator
and AI training server, and simulation software system which deploys to the Infrastructure, “deploying”
requires deployment interface and changes simulation software system from undeployed to deployed.
“registering” requires registration Interface and simulation software system at state “deployed” to yield
simulation software system address from inaccessible to accessible, which is acquired by the simulation
software system and binds to the infrastructure. “instancing” requires instantiation interface and
simulation software system address, then turns the simulation software system Instance to state “created”,
while the simulation software system instance is generated by simulation software system and works on
infrastructure. “simulation starting” requires simulation start interface and the simulation software system
instance to change the simulation software system instance itself from created to prepared. “runtime
monitoring and controlling” requires runtime monitor interface and the simulation software system
instance and changes simulation software system instance between state “running”, “paused” or “stopped”.
“result set retrieving” requires results retrieval interface and simulation software system instance at state
“done”, then it can output simulation result set. “instance removing” requires instance removing interface
and changes simulation software system instance from state “done” to state “removed”. “deregistering”
requires deregistration interface and the simulation software system address to change the simulation
software system address from accessible to inaccessible”. “clearing” requires clearance interface and
simulation software system and changes simulation software system from deployed to undeployed.
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
Figure 7 — SD1.2.3: Infrastructure collaboration supporting in-zoomed
The OPL corresponding to Figure 7 is as follows:
1. Infrastructure collaboration supporting from SD1.2 zooms in SD1.2.3 into infrastructure services
selecting, deploying, registering, instancing, simulation starting, runtime monitoring and controlling,
result set retrieving, instance removing, deregistering, and clearing, which occur in time sequence.
2. Simulation software system can be deployed or undeployed.
3. Simulation software system address can be accessible or inaccessible.
4. Infrastructure services can be selected or unselected.
5. Simulation software system instance can be created, done, prepared, removed or running/paused/
stopped.
6. Collaborative environment interface consists of clearance interface, deployment interface, deregistration
interface, instance removing interface, instantiation interface, registration interface, results retrieval
interface, runtime monitor interface and simulation start interface and two more parts.
7. Infrastructure services response collaborative environment interface.
8. Infrastructure consists of AI training server, digital twins corresponding actual system, semi physical
simulator, and simulation computer.
9. Infrastructure supports infrastructure services.
10. Simulation software system deploys to infrastructure.
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
11. Simulation software system acquires simulation software system address.
12. Simulation software system address binds to infrastructure.
13. Simulation software system generates simulation software system instance.
14. Simulation software system instance works on infrastructure.
15. Infrastructure collaboration supporting requires business description and simulation model
description.
16. Infrastructure services selecting changes infrastructure services from unselected to selected.
17. Infrastructure services selecting requires infrastructure services.
18. Deploying changes simulation software system from undeployed to deployed.
19. Deploying requires deployment interface, infrastructure, and simulation software system.
20. Registering changes simulation software system address from inaccessible to accessible.
21. Registering requires registration interface, simulation software system and simulation software system
address.
22. Instancing requires instantiation interface and simulation software system address.
23. Instancing yields simulation software system instance at state created.
24. Simulation starting changes simulation software system instance from created to prepared.
25. Simulation starting requires simulation software system instance and simulation start interface.
26. Runtime monitoring and controlling changes simulation software system instance from prepared to
running/paused/stopped.
27. Runtime monitoring and controlling requires runtime monitor interface and simulation software
system instance.
28. Result set retrieving requires simulation software system instance at state done and results retrieval
interface.
29. Result set retrieving yields simulation result set.
30. Instance removing changes simulation software system instance from done to removed.
31. Instance removing requires instance removing interface and simulation software system instance.
32. Deregistering changes simulation software system instance from accessible to inaccessible.
33. Deregistering requires deregistration interface and simulation software system address.
34. Clearing changes simulation software system from deployed to undeployed.
35. Clearing requires clearance interface and simulation software system.
PROOF/ÉPREUVE
ISO 21175-1:2026(en)
Annex A
(informative)
Application of CMSE in the functional hierarchy of IEC 62264-1
A.1 General
In this annex, IEC 62264-1 is referenced to explain the scope of CMSE in terms of functional hierarchy of
manufacturing systems. IEC 62264-1 defines functional hierarchically as follows, see Figure A.1.
Figure A.1 — Functional hierarchy (IEC 62264-1:2013, Figure 3)
a) Level 0 defines the actual physical processes.
b) Level 1 defines the activities involved in sensing and manipulating the physical processes. Level 1
typically operates on timeframes of seconds and faster.
c) Level 2 defines the activities of monitoring and controlling the physical processes. Level 2 typically
operates on timeframes of hours, minutes, seconds a
...

ISO/DISPRF 21175-1:2025(en)
ISO/TC 184/SC 5/WG 17
Secretariat: ANSI
Date: 2025-10-312026-03-27
Automation systems and integration — Collaboration environment
requirements of simulation on different manufacturing platforms - —
Part 1:
Reference model and process
PROOF
ISO #####-#:####(X/PRF 21175-1:2026(en)
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication
may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying,
or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO
at the address below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
Fax: +41 22 749 09 47
EmailE-mail: copyright@iso.org
Website: www.iso.org
Published in Switzerland
© ISO #### 2026 – All rights reserved
ii
ISO/DISPRF 21175-1:20252026(en)
Contents
Foreword . iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Conformance . 3
6 General framework of CMSE . 3
7 Joint simulation project analysing . 7
8 Joint simulation project realizing . 9
8.1 General . 9
8.2 Business and system describing . 11
8.3 Software collaboration implementing . 13
8.4 Infrastructure collaboration supporting . 16
Annex A (informative) Application of CMSE in the functional hierarchy of IEC 62264-1 . 22
Annex B (informative) Example of use of CMSE in joint simulation project . 25
Annex C (informative) The Legend of OPM . 47
Bibliography . 49

iii
ISO #####-#:####(X/PRF 21175-1:2026(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
ISO document should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent rights
in respect thereof. As of the date of publication of this document, ISO had not received notice of (a) patent(s)
which may be required to implement this document. However, implementers are cautioned that this may not
represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 184, Automation systems and integration,
Subcommittee SC 5, Interoperability, integration, and architectures for enterprise systems and automation
applications.
A list of all parts in the ISO 21175 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
Field Code Changed
© ISO #### 2026 – All rights reserved
iv
ISO/DISPRF 21175-1:20252026(en)
Introduction
Open, sharing and self-organization on demand among group enterprises or small and medium-sized
enterprises (SMEs) of manufacturing in the product full life cycle is the trend for the future which calls for
deep collaboration within or among enterprises especially simulation-oriented model collaboration. At
present, collaboration within or among enterprises has developed from simple information-based
collaboration, drawing based collaboration, 3D model-based collaboration to simulation-oriented model
collaboration. Simulation-oriented model collaboration can support global enterprises, virtual enterprises in
industrial cluster and integrated product teams within enterprise to carry out joint innovation, complex
product research and development, virtual fabricate/test/operation/maintenance and other activities in the
product full life cycle, which is of great significance to innovate products and improve their time (to market),
[1] [1]
quality, cost, and service, etc. . .
Nowadays, an expanding trend about all kinds of simulation-oriented model collaboration related activities in
the functional hierarchy of manufacturing systems can be observed. In the activities of business planning and
logistics, simulation-oriented model collaboration among different enterprise stakeholders is needed to
improve plant production scheduling, operational management, etc. In the activities of manufacturing
operations management, simulation-oriented model collaboration among different enterprise or department
stakeholders is needed to improve dispatching production, detailed production scheduling, etc. In the
activities of batch control, continuous control and discrete control, simulation-oriented model collaboration
among different department stakeholders is still needed to improve prediction and optimization.
In particular, with the deepening applications of technologies in the manufacturing system such as model
based system engineering, model engineering, cyber-physical system, digital twin, cognition and decision
[2] [2-4]-[4]
intelligence (based on the deep reinforcement learning especially) ) which increase the requirements
of simulation-oriented model collaboration upon different manufacturing platforms. First, the development
scope of the simulation has expanded from the traditional Local Area Network to the global Internet. Second,
the deployment place of the simulation has expanded from the traditional desktop to the pervasive terminal.
Meanwhile, the operation form of the simulation has expanded from the traditional off-line small-scale
sequential verification to the on-line large-scale parallel analysis on demand.
The prerequisite for simulation-oriented model collaboration is simulation interoperability which now is
covered by several existing standards or specifications supporting distributed interactive simulation system
[5],[6] [5,6] [7] [7]
like Discrete Event System Specification (DEVS) ), , Distributed Interactive Simulation (DIS) ), , High
[8] [8] [9] [9]
Level Architecture (HLA) ), , Test and Training Enabling Architecture (TENA) ), , Functional Mock-up
[10]-[13] [10-13]
Interface (FMI)/System Structure and Parameterization (SSP) ), , Distributed Co-Simulation
[14][14] [15] [15]
Protocol (DCP) and FIWARE . . The Distributed Simulation Engineering and Execution Process
[16][16]
(DSEEP) standard describes the different development steps of a distributed interactive simulation
system which is independent of any distributed interactive simulation architecture like HLA or DIS. However,
there are no formal standards existing for a kind of environment where all kinds of stakeholders involved in
the joint simulation project could improve collaboration to enable on-demand simulation at any time and any
place upon different manufacturing platforms with different infrastructures, operating systems, simulation
middleware. The common problems that exist in the current implementation of joint simulation projects
include requesting the infrastructure device by phone, integrating the software / model offline, and running
the simulation system manually, which bring great inconvenience to the projects. Therefore, a new standard
required for shielding distribution and heterogeneity of them to enable service-oriented share-use,
integration and collaboration, by providing the semantic and pragmatic guarantee plus the general and neutral
interface definition.
This document specifies the reference model (including collaboration environment meta-model and
collaboration environment interface) and the reference process (including joint simulation project
analyzinganalysing, joint simulation project realizing with the steps of business and system describing,
software collaboration implementing and infrastructure collaboration supporting) of the collaborative
modeling and simulation environment to promote the solution formulation of joint simulation projects.
v
ISO #####-#:####(X/PRF 21175-1:2026(en)
The annexes provide additional information. Annex AAnnex A introduces the functional hierarchy defined in
[17] [17]
IEC 62264 -1 and its relationship with this standard. Annex Bdocument. Annex B shows an example of
using collaborative modelingmodelling and simulation environment in a joint simulation project.
Annex CAnnex C illustrates the legend of OPM used in this standard textdocument.
© ISO #### 2026 – All rights reserved
vi
DRAFT International Standard ISO/DIS 21175-1:2025(en)

Automation systems and integration — Collaboration Environment
Requirementsenvironment requirements of Simulationsimulation on
Different Manufacturing Platforms —
different manufacturing platforms —
Part 1:
Reference Modelmodel and Processprocess
1 Scope
The purpose of this document is to specify a reference model and process for Collaborative Modeling and
Simulation Environment (CMSE), which establishes a general framework of CMSE to provide guidance for
implementation of joint simulation projects. The CMSE which is based on the reference process and the
reference model including neutral interfaces and meta-models can enable service-oriented share-use of the
infrastructure, integration of the software and collaboration of the business to improve collaboration among
all kinds of stakeholders involved in a joint simulation project which needs on-demand simulation
at any time and any place upon different manufacturing platforms owned by different enterprises or by
different departments within an enterprise.
This document can not only be applied to manufacturing enterprises but also be applied to other kinds of
enterprises. It is intended for use by stakeholders who are concerned with developing and deploying solutions
of the joint simulation project based on information and communication technology. It focuses on simulation
activities related cross-platform simulation collaboration capability supporting business planning and
logistics, manufacturing operations management and production control within or among enterprises, which
[28]
can cover the levels from 2 to 4 of the functional hierarchy of manufacturing systems in IEC 62264-3 .
This document specifies the following:
— — the general framework of CMSE;
— — the methodology of the joint simulation project analysis and realization by CMSE.
This document does not relate to the simulation irrelevant collaboration environment, and does not specify
the specific approach to implement CMSE in the solution formulation of joint simulation projects.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— — ISO Online browsing platform: available at https://www.iso.org/obp
— — IEC Electropedia: available at https://www.electropedia.org/
3.1 3.1
simulation
use of a similar or equivalent system to imitate a real system, so that it behaves like or appears to be the real
system
[18] [18]
[SOURCE: ISO 16781:2021 ,, 3.1.9]
3.2 3.2
simulation collaboration
process of two or more participants of a simulation activity working together to complete a simulation task
Note 1 to entry: Collaboration is the process of two or more people, entities or organizations working together to
complete a task or achieve a goal. Simulation collaboration includes three aspects: collaborative modeling, collaborative
simulation and collaborative evaluation.
[19][19]
[SOURCE: IEEE 1730-2022 ]]
3.3 3.3
platform
combination of an operating system and hardware that makes up the operating environment in which a
program runs
Note 1 to entry: The platform includes infrastructure, operating system, simulation middleware which are depending on
a simulation activity.
[20] [20]
[SOURCE: ISO/IEC/IEEE 26513:2017 ,, 3.30]
3.4 3.4
collaboration environment
kind of software system which enables service-oriented share-use, integration and collaboration upon
different manufacturing platforms, by providing the semantic and pragmatic guarantee plus the general and
neutral interface definition, based on the interoperability of the manufacturing platforms
Note 1 to entry: Interoperability defined in ISO/TS 15926-8:2011 is about ability of different types of computers,
networks, operating systems, and applications to work together effectively, without prior communication, in order to
exchange information in a useful and meaningful manner.
4 Abbreviated terms
DIS distributed interactive simulation
HLA high level architecture
TENA test and training enabling architecture
CMSE collaborative modeling and simulation environment
DEVS discrete event system specification
SES system entity structure
OPM object process methodology
OPD object process diagram
OPL object process language
M&S modeling and simulation
FMI functional mock-up interface
ISO/DISPRF 21175-1:20252026(en)
DCP distributed co-simulation protocol
DSEEP distributed simulation engineering and execution process
5 Conformance
In order to claim conformity with this document, any particular CMSE in the solution formulation of joint
simulation projects shall be able to be positioned within the general framework defined in this document. This
positioning shall consist of joint simulation project analyzinganalysing and joint simulation project realizing
which includes the business and system describing, software collaboration implementing and infrastructure
collaboration supporting.
This document conforms with ISO 19450 – Object-process methodology and with ISO 17649 – Model-based
standards authoring, which was established following the realization that the next generation of standards
mustneeds to be not only machine-readable, but also executable, so they can be tested and validated for
completeness, coherence, and consistence, both within each standard and across related standards.
6 The General Frameworkframework of CMSE
The general framework of CMSE proposed in this standarddocument includes “collaborative modeling and
simulation environment reference model and process enabling”, which is the main process of this
standarddocument.
Figure 1Figure 1 is the OPM( (ISO 19450) system diagram (SD) of the system specified in this
standarddocument. This process fully utilizes the simulation environment reference model and process to
promote the solution formulation of the joint simulation project, as specified in this standarddocument.
The joint simulation project can be changed by the process “collaborative modeling and simulation
environment reference model and process enabling” from rigid to flexible. The cross-platform simulation
collaboration capability of joint simulation project can be improved from low to high by the process. The
simulation collaboration reference model and process which support the process exhibit cross-platform
simulation collaboration capability of joint simulation project at state “high”. And simulation stakeholder
group handles “collaborative modeling and simulation environment reference model and process enabling”
and participates in the joint simulation project. The joint simulation project encapsulates or selects simulation
services which response to collaborative environment interface.
Figure 1 —— OPM (ISO 19450) top-level system diagram of CMSE
The OPL corresponding to Figure 1Figure 1 is as follows:
1) Cross-platform simulation collaboration capability of joint simulation project can be high or low.
2) Joint simulation project can be flexible or rigid.
3) Simulation stakeholder group participates in joint simulation project.
4) Simulation collaboration reference model and process consists of collaborative modeling and simulation
environment reference model and collaborative modeling and simulation environment reference process.
5) Collaborative modeling and simulation environment reference model consists of collaborative
environment interface and collaborative environment meta-model.
6) Joint simulation project exhibits cross-platform simulation collaboration capability.
7) Simulation collaboration reference model and process exhibits cross-platform simulation collaboration
capability of joint simulation project with value high.
ISO/DISPRF 21175-1:20252026(en)
8) Joint simulation project encapsulate/select collaborative environment services.
9) Collaborative environment services providesprovide services to collaborative environment interface.
10) Collaborative modeling and simulation environment reference model and process enabling changes
cross-platform simulation collaboration capablitycapability of joint simulation project from low to high.
11) Collaborative modeling and simulation environment reference model and process enabling changes joint
simulation project from rigid to flexible.
12) Simulation stakeholder group handles collaborative modeling and simulation environment reference
model and process enabling.
13) Collaborative modeling and simulation environment reference model and process enabling requires
simulation collaboration reference model and process.
14) Collaborative modeling and simulation environment reference model and process enabling yields M&S
objectives and project goals.
In Figure 2Figure 2,, “collaborative modeling and simulation environment reference model and process
enabling” is in-zoomed in the OPD. This diagram shows that the “collaborative modeling and simulation
environment reference model and process enabling” has four sub-processes: “project goals deciding”,
“modeling and simulation (M&S) objectives deciding”, “joint simulation project analyzinganalysing” and “joint
simulation project realizing”. “project goals deciding” yields “project goals”, which can be expressed at levels
2-4 of the IEC 62264-1 functional hierarchy (see Annex AAnnex A).). “M&S objectives deciding” uses the
project goals to develop a set of M&S objectives, or measures of effectiveness, used to drive the M&S
experiment. “joint simulation project analyzinganalysing” requires M&S objectives and yields “structured task
list”. The last sub-process “joint simulation project realizing” gets the structured task list and turns the joint
simulation project from flexible to rigid. Meanwhile, it also turns the cross-platform simulation collaboration
capability to state high. The structured task list directs the joint simulation project.
Figure 2— SD1: The main process in Figure 1Figure 1 in-zoomed, exposing four sub-processes
The OPL corresponding to Figure 2Figure 2 is as follows:
ISO/DISPRF 21175-1:20252026(en)
1) Collaborative modeling and simulation environment reference model and process enabling from SD
zooms in SD1 into project goals deciding, M&S objectives deciding, joint simulation project
analyzinganalysing, and joint simulation project realizing, which occur in that time sequence.
2) Cross-platform simulation collaboration capability of joint simulation project can be high or low.
3) Joint simulation project can be flexible or rigid.
4) Structured task list directs joint simulation project.
5) Joint simulation project exhibits cross-platform simulation collaboration capability.
6) Simulation collaboration reference model and process exhibits cross-platform simulation collaboration
capability of joint simulation project with value high.
7) Simulation stakeholder group handles collaborative modeling and simulation environment reference
model and process enabling.
8) Collaborative modeling and simulation environment reference model and process enabling requires
simulation collaboration reference model and process.
9) Joint simulation project analyzinganalysing requires M&S objectives.
10) Joint simulation project analyzinganalysing yields structured task list.
11) Joint simulation project realizing changes joint simulation project from rigid to flexible.
12) Joint simulation project realizing requires structured task list.
13) Joint simulation project realizing changes cross-platform simulation collaboration capability of joint
simulation project to state high.
14) M&S objectives deciding requires project goals.
15) M&S objectives deciding yields M&S objectives.
16) Project goals deciding changes cross-platform simulation collaboration capability of joint simulation
project from state low.
17) Project goals deciding yields project goals.
7 Joint simulation project analyzinganalysing
The “joint simulation project analyzinganalysing” is in-zoomed in the OPD in Figure 3Figure 3. This process,
which requires M&S objectives, involves four sub-processes which include “participant identifying”, “structure
analyzing”, “behavior analyzinganalysing”, “behaviour analysing” and “model construction
analyzinganalysing”. The description of each sub-process and related objects is expressed in the OPL in
Figure 3Figure 3. The sub-process “participant identifying” yields participants list while the sub-process
“structure analyzinganalysing” obtains objects list. The “behavior snalyzingbehaviour analysing” requires
objects list and produces process list. The last sub-process “model construction analyzinganalysing” requires
both objects list and process list and yields model list. participants list, objects list, process list and model list
are the parts of structured task list.
Figure 3— SD1.1: Joint simulation project analyzinganalysing in-zoomed
The OPL corresponding to Figure 3Figure 3 is as follows:
1) Joint simulation project analyzinganalysing from SD1 zooms in SD1.1 into participant identifying,
structure analyzing, behavior analyzinganalysing, behaviour analysing, and model construction
analyzinganalysing, which occur in that time sequence.
2) Structure task list consists of model list, objects list, participants list, and process list.
3) Joint simulation project analyzinganalysing requires M&S objectives.
4) Participant identifying yields participants list.
5) Structure analyzinganalysing yields objects list.
6) Model construction analyzinganalysing requires objects list and process list.
ISO/DISPRF 21175-1:20252026(en)
7) Model construction analyzinganalysing yields model list.
8) Behavior analyzingBehaviour analysing requires objects list.
9) Behavior analyzingBehaviour analysing yields process list.
8 Joint simulation project realizing
8.1 General
The “joint simulation project realizing” is in-zoomed in the OPD in Figure 4Figure 4. This process involves
three sub-processes which include “business and system describing”, “software collaboration implementing”
and “infrastructure collaboration supporting”. A description of each sub-process and related objects appear
in the OPL below. “business and system describing” requires structured task list to yields business description
and simulation model description, and “software collaboration implementing” requires these two descriptions
to yield simulation software system. The last process, “infrastructure collaboration supporting”, requires all
three products to yields joint simulation project upon the different infrastructure of the manufacturing
platform at state “flexible”. It should be noted that the “joint simulation project realizing” does not specify an
architecture, and the suitable architecture shall be proposed after fully considering all the aspects of the
business and system.
Figure 4— SD1.2: Joint simulation project realizing in-zoomed
The OPL corresponding to Figure 4Figure 4 is as follows:
1) Joint simulation project realizing from SD1 zooms in SD1.2 into business and system describing, software
collaboration implementing, and infrastructure collaboration supporting, which occur in that time
sequence.
2) Joint simulation project can be flexible or rigid.
ISO/DISPRF 21175-1:20252026(en)
3) Simulation software system can be deployed or undeployed.
4) Joint simulation project realizing consumes joint simulation project at state rigid.
5) Business and system describing requires structured task list.
6) Business and system describing yields business description and simulation model description.
7) Software collaboration implementing requires business description and simulation model description.
8) Software collaboration implementing yields simulation software system.
9) Infrastructure collaboration supporting requires business description and simulation software system.
10) Infrastructure collaboration supporting yields joint simulation project at state flexible.
8.2 Business and system describing
The “business and system describing” is in-zoomed in the OPD in Figure 5Figure 5. Process “business and
system describing” consists of five sub-processes: “process interaction relationship and method describing”,
“process interaction content describing”, “process resource requirement describing”, “simulation system
describing” and “description documnetsdocuments distributing”. The first three sub-processes require
collaborative environment meta-model and process list and create the different parts of the process
description which is divided into two parts: modeling description such as SES and simulation and evaluation
[21],[22] [21,22]
description including experimental frame-system and M&S objectives . . The fourth sub-process
requires model list to create the simulation model description. The last sub-process requires business
description and simulation model description and yields documents required by each of the stakeholders. The
specified relationship of sub-processes and objects is shown in the OPL below.
Figure 5— SD1.2.1: Business and system describing in-zoomed
NOTE Interaction information is transferred between simulation processes, and the earlier process transfers the
experimental results to the latter process as the initial conditions. Data transmission (and feedback) also is conducted
among the modeling, simulation, and evaluation sub-processes within the simulation process. Collaborative modeling
and simulation or evaluation sub-processes are carried out by the simulation stakeholder group.
The OPL corresponding to Figure 5Figure 5 is as follows:
1) Business and system describing from SD1.2 zooms in SD1.2.1 into process interaction relationship and
method describing, process interaction content describing, process resource requirement describing,
simulation system describing, and description documents distributing, which occur in that time sequence.
2) Process description consists of constraint description, identification and indicator description,
input/output content description, and resource requirement description.
ISO/DISPRF 21175-1:20252026(en)
3) Collaborative environment meta-model consists of interaction information, interaction relationship and
interaction method, and resource requirement.
4) Interaction relationship and interaction method consists of interaction method and interaction
relationship.
5) Interaction information consists of evaluation result, experiment, identifier, model, parameter, scenario,
and simulation data.
6) Business description consists of process description.
7) Modeling description and simulation and evaluation description are process descriptions.
8) Collaborative evaluation, collaborative modeling, collaborative simulation, and workflow are interaction
methods.
9) Simulation and evaluation description consists of M&S objectives and experimental frame-system.
10) Experimental frame-system evaluates M&S objectives.
11) Modeling description consists of SES.
12) Structured task list consists of model list and process list and two more parts.
13) Process interaction relationship and method describing requires interaction relationship and interaction
method and process list.
14) Process interaction relationship and method describing yields constraint description.
15) Process interaction content describing requires interaction information and process list.
16) Process interaction content describing yields identification and indicator description and input/output
content description.
17) Process resource requirement describing requires process list and resource requirement.
18) Process resource requirement describing yields resource requirement description.
19) Simulation system describing requires model list.
20) Simulation system describing yields simulation model description.
21) Description documents distributing requires business description and simulation model description.
22) Description documents distributing yields documents required by each of the stakeholders.
8.3 Software collaboration implementing
This document follows the service-oriented approach, and focuses on providing a neutral interface to support
the approach. The software service to which the interface belongs, and the relationship of the service and the
interface have been specified.
“software collaboration implementing” is in-zoomed in the OPD in Figure 6Figure 6. The process “software
collaboration implementing” is zoomed into “interaction technology selecting”, “activities encapsulating”,
“services integrating”, and “system orchestrating”, which occurs in that time sequence to achieve
encapsulation of the simulation software as the simulation service, and integration of the simulation services
as simulation system. “software collaboration implementing” requires interface of encapsulation and interface
of interaction, which forms collaborative environment interface with other eight interfaces. It also requires
business description and simulation model description. “interaction technology selecting” requires interface
of interaction and yields middleware/protocol such as DEVS, DIS, HLA, TENA, Functional Mock-up
Interface/System Structure and Parameterization, Distributed Co-Simulation Protocol, FIWARE. “activities
encapsulating” requires interface of encapsulation as well as middleware/protocol and yields simulation
software services. When it comes to existing services, “activities encapsulating” goes to “reusable software
services selecting”. And it goes to “new software service encapsulating” while the service is new. “services
integrating” requires middleware/protocol and simulation software services to yield bonded service set.
“system orchestrating” requires bonded service set to yield simulation software system as the form of
distributed interactive simulation system.
ISO/DISPRF 21175-1:20252026(en)

Figure 6— SD1.2.2: Software collaboration implementing in-zoomed
The OPL corresponding to Figure 6Figure 6 is as follows:
1) Software collaboration implementing from SD1.2 zooms in SD1.2.2 into interaction technology selecting,
activities encapsulating, reusable software services selecting, new software service encapsulating,
services integrating, and system orchestrating, which occur in that time sequence.
2) Simulation software system can be deployed or undeployed.
3) Simulation software services can be existing or new.
4) Collaborative environment interface consists of interface of encapsulating and interface of interaction and
9 more parts.
5) DCP, DEVS, DIS, FIWARE, FMI/SSP, HLA and TENA are middleware/protocol.
6) Simulation software services relates to collaborative environment interface.
7) Simulation software supports simulation software services.
8) Software collaboration implementing requires business description and simulation model description.
9) Interaction technology selecting requires interface of interaction.
10) Interaction technology selecting yields middleware/protocol.
11) Activities encapsulating requires interface of encapsulation and middleware/protocol.
12) New software service encapsulating yields simulation software services at state new.
13) Reusable software services selecting requires simulation software services at state existing.
14) Activities encapsulating yields simulation software services.
15) Services integrating requires middleware/protocol and simulation software services.
16) Services integrating yields bonded service set.
17) System orchestrating requires bonded service set.
18) System orchestrating yields simulation software system.
In terms of the manner of implementation, two different cases were in consideration. In the first case, the
software collaboration implementing is only for the current joint simulation project. In this case, the software
collaboration implementing is performed manually. In the second case, the “activities encapsulating”, “service
integrating” and “service orchestrating” could be done with combination of corresponding components built
in other projects. In this case, the software collaboration implementing could be performed automatically.
8.4 Infrastructure collaboration supporting
“infrastructure collaboration supporting” is in-zoomed in the OPD in Figure 7Figure 7. This process consists
of ten sub-processes: “infrastructure services selecting”, “deploying”, “registering”, “instancing”, “simulation
starting”, “runtime monitoring and controlling”, “result set retrieving”, “instance removing”, “deregistering”
and “clearing” as shown in the diagram. “infrastructure services selecting” requires the infrastructure services,
which response to collaborative environment interface, and changes the infrastructure services from
unselected to selected. Based on the infrastructure which is the hardware system of the manufacturing
platform including simulation computer, digital twins corresponding actual system, semi physical simulator
ISO/DISPRF 21175-1:20252026(en)
and AI training server, and simulation software system which deploys to the Infrastructure, “deploying”
requires deployment interface and changes simulation software system from undeployed to deployed.
“registering” requires registration Interface and simulation software system at state “deployed” to yield
simulation software system address from inaccessible to accessible, which is acquired by the simulation
software system and binds to the snfrastructure.infrastructure. “instancing” requires instantiation interface
and simulation software system address, then turns the simulation software system Instance to state
“created”, while the simulation software system instance is generated by simulation software system and
works on infrastructure. “simulation starting” requires simulation start interface and the simulation software
system instance to change the simulation software system instance itself from created to prepared. “runtime
monitoring and controlling” requires runtime monitor interface and the simulation software system instance
and changes simulation software system instance between state “running”, “paused” or “stopped”. “result Set
retreivingset retrieving” requires results retrieval interface and simulation software system instance at state
“done”, then it can output simulation result set. “instance removing” requires instance removing interface and
changes simulation software system instance from state “done” to state “removed”. “deregistering” requires
deregistration interface and the simulation software system address to change the simulation software system
address from accessible to inaccessible”. “clearing” requires clearance interface and simulation software
system and changes simulation software system from deployed to undeployed.
ISO/DISPRF 21175-1:20252026(en)

Figure 7— SD1.2.3: Infrastructure collaboration supporting in-zoomed
The OPL corresponding to Figure 7Figure 7 is as follows:
1) Infrastructure collaboration supporting from SD1.2 zooms in SD1.2.3 into infrastructure services
selecting, deploying, registering, instancing, simulation starting, runtime monitoring and controlling,
result set retrivingretrieving, instance removing, deregistering, and clearing, which occur in time
sequence.
2) Simulation software system can be deployed or undeployed.
3) Simulation software system address can be accessible or inaccessible.
4) Infrastructure services can be selected or unselected.
5) Simulation software system instance can be created, done, prepared, removed or
running/paused/stopped.
6) Collaborative environment interface consists of clearance interface, deployment interface, deregistration
interface, instance removing interface, instantiation interface, registration interface, results retrieval
interface, runtime monitor interface and simulation start interface and two more parts.
7) Infrastructure services response collaborative environment interface.
8) Infrastructure consists of AI training server, digital twins corresponding actual system, semi physical
simulator, and simulation computer.
9) Infrastructure supports infrastructure services.
10) Simulation software system deploys to infrastructure.
11) Simulation software system acquires simulation software system address.
12) Simulation software system address binds to infrastructure.
13) Simulation software system generates simulation software system instance.
14) Simulation software system instance works on infrastructure.
15) Infrastructure collaboration supporting requires business description and simulation model description.
16) Infrastructure services selecting changes infrastructure services from unselected to selected.
17) Infrastructure serviecesservices selecting requires infrastructure services.
18) Deploying changes simulation software system from undeployed to deployed.
19) Deploying requires deployment interface, infrastructure, and simulation software system.
20) Registering changes simulation software system address from inaccessible to accessible.
21) Registering requires registration interface, simulation software system and simulation software system
address.
22) Instancing requires instantiation interface and simulation software system address.
23) Instancing yields simulation software system instance at state created.
24) Simulation starting changes simulation software system instance from created to prepared.
25) Simulation starting requires simulation software system instance and simulation start interface.
26) Runtime monitoring and controlling changes simulation software system instance from prepared to
running/paused/stopped.
27) Runtime monitoring and controlling requires runtime monitor interface and simulation software system
instance.
28) Result set retrivingretrieving requires simulation software system instance at state done and results
retrieval interface.
29) Result set retrivingretrieving yields simulation result set.
30) Instance removing changes simulation software system instance from done to removed.
31) Instance removing requires instance removing interface and simulation software system instance.
32)
...