ISO/DIS 23247-4

Automation systems and integration -- Digital Twin framework for manufacturing

Titre manque

Standards Content (sample)

DRAFT INTERNATIONAL STANDARD
ISO/DIS 23247-4
ISO/TC 184/SC 4 Secretariat: ANSI
Voting begins on: Voting terminates on:
2020-07-27 2020-10-19
Automation systems and integration — Digital Twin
framework for manufacturing —
Part 4:
Information exchange
Partie 4: Echange d'informations
ICS: 25.040.40; 35.240.50
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
This document is circulated as received from the committee secretariat.
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/DIS 23247-4:2020(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION. ISO 2020
---------------------- Page: 1 ----------------------
ISO/DIS 23247-4:2020(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2020

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: [phone]
Fax: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii © ISO 2020 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/DIS 23247-4:2020(E)
Contents Page

Foreword ........................................................................................................................................................................................................................................iv

Introduction ..................................................................................................................................................................................................................................v

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms and definitions ..................................................................................................................................................................................... 2

4 Networking view of Digital Twin reference architecture for manufacturing .......................................2

4.1 Overview ...................................................................................................................................................................................................... 2

4.2 User network ............................................................................................................................................................................................ 2

4.3 Service network ..................................................................................................................................................................................... 3

4.4 Access network ....................................................................................................................................................................................... 3

4.5 Proximity network ............................................................................................................................................................................... 3

5 Requirements for information exchange in the User network ............................................................................ 3

5.1 Overview ...................................................................................................................................................................................................... 3

5.2 Provisioning ............................................................................................................................................................................................... 3

5.3 On-demand status acquisition ................................................................................................................................................... 3

5.4 Standardized method for information exchange ....................................................................................................... 4

5.5 V erification of exchanged digital model ............................................................................................................................ 4

5.6 Security .......................................................................................................................................................................................................... 4

5.7 Synchronization ..................................................................................................................................................................................... 4

5.8 Exchange of digital models ........................................................................................................................................................... 4

6 Requirements for information exchange in the Service network ..................................................................... 5

7 Requirements for information exchange in Access network ................................................................................. 5

7.1 Overview ...................................................................................................................................................................................................... 5

7.2 Connectivity ............................................................................................................................................................................................... 5

7.3 Standardized method for communication ...................................................................................................................... 5

7.4 Synchronization ..................................................................................................................................................................................... 5

7.5 Transaction method............................................................................................................................................................................ 6

7.6 Support of mobility ............................................................................................................................................................................. 6

7.7 Security .......................................................................................................................................................................................................... 6

8 Requirements for information exchange in Proximity network ........................................................................ 6

8.1 Overview ...................................................................................................................................................................................................... 6

8.2 Support of local connectivity ...................................................................................................................................................... 6

8.3 Support of adaptation ....................................................................................................................................................................... 6

Annex A (informative) Technical discussion -

Implementation options for Digital Twin framework for manufacturing ...............................................7

Bibliography .............................................................................................................................................................................................................................18

© ISO 2020 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/DIS 23247-4:2020(E)
Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards

bodies (ISO member bodies). The work of preparing International Standards is normally carried out

through ISO technical committees. Each member body interested in a subject for which a technical

committee has been established has the right to be represented on that committee. International

organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.

ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of

electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance are

described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the

different types of ISO documents should be noted. This document was drafted in accordance with the

editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of

any patent rights identified during the development of the document will be in the Introduction and/or

on the ISO list of patent declarations received (see www .iso .org/ patents).

Any trade name used in this document is information given for the convenience of users and does not

constitute an endorsement.

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, Industrial automation systems and

integration, Subcommittee SC 4 Industrial data.
A list of all parts in the ISO 23247 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.
iv © ISO 2020 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/DIS 23247-4:2020(E)
Introduction

The ISO 23247 series defines a framework to support the creation of Digital Twins of observable

manufacturing elements including personnel, equipment, materials, manufacturing processes, facilities,

environment, products, and supporting documents.
The scopes of the four parts of this series are defined below:
— Part 1: Overview and general principles

General principles and requirements for developing Digital Twins in manufacturing;

— Part 2: Reference architecture
Reference architecture with functional views;
— Part 3: Digital representation of manufacturing elements
List of basic information attributes for the observable manufacturing elements;
— Part 4: Information exchange

Technical requirements for information exchange between entities within the reference

architecture.

The framework is targeted to all types of manufacturing including discrete and continuous

manufacturing of parts, assemblies and material. The actual type of manufacturing supported by

a particular implementation depends on the standards and technologies available to model the

observable manufacturing elements.

Digital Twin use cases that conform to the framework will be detailed in a series of technical reports

attached to this series. Preliminary outlines for three use cases are given in the Annex of Part 4.

© ISO 2020 – All rights reserved v
---------------------- Page: 5 ----------------------
DRAFT INTERNATIONAL STANDARD ISO/DIS 23247-4:2020(E)
Automation systems and integration — Digital Twin
framework for manufacturing —
Part 4:
Information exchange
1 Scope

This part of ISO 23247 identifies technical requirements for information exchange between entities

within the reference architecture.

The ISO 23247 series defines a framework to guide the creation of Digital Twins of observable

manufacturing elements including personnel, equipment, materials, processes, facilities, environment,

products, and supporting documents.

The requirements for information exchange in the following networks are within the scope of this part

of ISO 23247:
— User network that connects the User entity and Core entity;
— Service network that connects sub-entities within the Core entity;

— Access network that connects the Data collection and device control entity to the Core entity and to

the User entity;

— Proximity network that connects the Data collection and device control entity to the observable

manufacturing elements.
The following are described in other parts of ISO 23247:
— overview and general principles (Part 1);
— reference architecture (Part 2);
— digital representation of manufacturing elements (Part 3).

The following are outside of the scope of ISO 23247, but will be identified as use cases in technical

reports.

— selection of the manufacturing devices and other resources to be represented by Digital Twins;

— selection of the manufacturing processes to be represented by Digital Twins;
— selection of the manufacturing products to be represented by Digital Twins.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements 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 23247-1, Automation systems and integration — Digital Twin framework for manufacturing — Part 1:

Overview and general principles
© ISO 2020 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/DIS 23247-4:2020(E)

ISO 23247-2, Automation systems and integration — Digital Twin framework for manufacturing — Part 2:

Reference architecture
3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 23247-1 apply.

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
4 Networking view of Digital Twin reference architecture for manufacturing
4.1 Overview

ISO 23247-2 defines a reference model for the functional view of Digital Twins in manufacturing. This

part describes the networking view.

Figure 1 shows four types of communication networks based on the reference architecture of

ISO 23247-2.

Figure 1 — Networking view of Digital Twin reference architecture for manufacturing

4.2 User network

The User network connects the User entity with the Core entity. Through this network, the User entity

make use of the digital twin instances managed by the Core entity.

The User network can be both public Internet and also (private) Intranet in case that User entity and

Core entity are implemented in a single private domain.
2 © ISO 2020 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/DIS 23247-4:2020(E)
4.3 Service network

The Service network connects the operation and management sub-entity, application and service

sub-entity, and resource access and interchange sub-entity. The service network is typically a wired

network running IP-based protocols.

The Service network can include both public Internet and also (private) Intranet in case that the Core

entity is implemented in a single private domain.

If the core entity is implemented as a single private system, then a Service network is not needed.

4.4 Access network

The Access network connects the Data collection and device control entity (DCDCE) to the Core entity

and the User entity. Through this network, the Data collection sub-entity transmits data collected from

the observable manufacturing elements (OME) to the Core entity. Through this network, the User entity

and the Core entity transmit information to control the observable manufacturing elements.

The Access network can be a wired communication such as local area network (LAN) or wireless

communication such as wireless LAN (WLAN) and mobile (cellular) network. The Access network

generally adopts IP-based communication protocols regardless of communication type.

4.5 Proximity network

The Proximity network connects DCDCE with OME. Through this network, DCDCE transmits commands

to industrial devices and receives results from sensors.

The Proximity network can be Industrial Ethernet or a proprietary network with a restricted

configuration. Some networks use specialised protocols instead of generic protocols such as IP.

However, if an OME is physically attached or integrated into the DCDCE then the Proximity network is

not necessary.
5 Requirements for information exchange in the User network
5.1 Overview

The User network shall enable the exchange of information between the User entity and the Core

entity for services and applications such as visualization, process monitoring, statistical analysis, and

simulation.
5.2 Provisioning

The User network shall enable the delivery of information to configure a Digital Twin to an initial state.

EXAMPLE 1 The Digital Twin of a product is provisioned at the start of its life from information contained

in Product lifecycle management (PLM). This information may include product requirements, 3D models,

configuration, simulation models, and traceability.

EXAMPLE 2 The Digital Twin of a work cell is provisioned at the start of its life from information in PLM or

other data sources. This information may include kinematics, capacity, capability, certification, and calibration

EXAMPLE 3 The Digital Twin of a process is provisioned at the start of its life from information in PLM or

other data sources. This information may include high-level and low-level process plans, tolerances, fixture, and

cutter requirements.
5.3 On-demand status acquisition

The User network shall enable the delivery of information on the current state of the Digital Twin.

© ISO 2020 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/DIS 23247-4:2020(E)

The User network shall enable the delivery of information on the historical state of the Digital Twin.

EXAMPLE 1 A User entity queries a Core entity, so that it can show the current status of the machine in a

remote location.

EXAMPLE 2 A User entity queries a Core entity, so that it can dynamically predict the remaining life for a cutter.

EXAMPLE 3 Upon decommissioning a Digital Twin informs related Digital Twin that it is no longer valid.

5.4 Standardized method for information exchange
The User network shall use standardized methods for exchanging information.

NOTE As described in Annex A.2.1, examples for standardized protocol include REST and HTTP.

5.5 Verification of exchanged digital model

The standardized method for information exchange should include methods for verifying the syntax

and semantics of the exchanged model and validating its contents.

NOTE As described in Annex A.2.1, examples of information models with methods for checking syntax and

semantics include STEP and QIF.
5.6 Security

The User network shall provide secure methods of communication in terms of authentication,

authorization, data integrity, privacy, confidentiality, etc.

The User network shall provide methods such as digital signatures to authenticate that the correct

information is delivered to the correct application.

The User network shall provide methods to ensure that Digital Twin can be accessed by authorized

parties only.
5.7 Synchronization

The User network shall enable applications to operate on digital models that have been appropriately

synchronized.

NOTE The rate of synchronization depends on the application. Information that is going to be used to prevent

a collision must arrive before the collision. Information that is going to be used to determine a statistical trend

for a quarterly report must arrive before the cut-off date of the report.
5.8 Exchange of digital models

The User network shall enable exchange of information about the digital representation of the OME. The

communication shall allow applications to operate on common models of the OME. Depending upon the

application, the types of elements shown in Figure 2 may need to be modelled for information exchange.

Figure 2 — Type of digital models for exchange
4 © ISO 2020 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/DIS 23247-4:2020(E)

NOTE At the present time, several standards define information for one or more of the OME types but no

single standard defines information for all the OME types.
6 Requirements for information exchange in the Service network

The Service network is used to transmit information between sub-entities of the core entity. As such

this network can be private to a particular implementation of the Core entity and does not need to be

defined by this standard.

NOTE If a Core entity is implemented by multiple organizations. then it can use the User Network to enable

data sharing.
7 Requirements for information exchange in Access network
7.1 Overview

The Access network connects the DCDCE to other entities. The DCDCE collects information about the

OME as they operate using an appropriate streaming protocol. The DCDCE controls the OME by sending

commands in a language understood by the OME.
7.2 Connectivity

The Core entity and User entity are connected to the DCDCE by the Access network. Depending on

the circumstances, the connection may be discovered dynamically using an appropriate protocol or

statically using a known network address. In either case, the connection delivers data about the OME of

interest to the Core entity.

EXAMPLE 1 In a static example, a MTConnect agent for a machine tool on the shop floor may be published

to the network as URL 192.168.0.1:5000. In this case, the Digital Twin for the machine tool uses this address to

listen for changes to its OME.

EXAMPLE 2 In a dynamic example, a MQTT subscriber discovers the availability of a data stream from the

DCDCE responsible for an OME and uses the information to update its Digital Twin.

7.3 Standardized method for communication

The Access network shall provide a standardized method for delivering data to the Core entity. The

method shall include information sufficient to identify the OME, and describe the change that has

occurred.

EXAMPLE 1 The Access network may use MTConnect as a standardized method to transfer data to the Core

entity from the DCDCE.

The Access network shall provide a standardized method for delivering data to control an OME through

the DCDCE.

EXAMPLE 2 The Access network may deliver a CNC program described using ISO 6983 G-code formatting to

the OME from the Core entity or the User entity.
7.4 Synchronization

The Access network shall enable the Digital Twin to be synchronized with the OME at an appropriate rate.

NOTE 1 The bandwidth of the Access network must be sufficient to support the required level of

synchronization.

NOTE 2 The latency requirements for servicing an urgent fault or alarm are different than those for updating

a 3D model.
© ISO 2020 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/DIS 23247-4:2020(E)
7.5 Transaction method

The Access network shall support any of the three types of transaction methods that follow:

— PULL method: requester requests information from the provider;

NOTE 1 In the Access network, the Core entity is the requester and the DCDCE is the information provider.

— PUSH method: sender sends new or changed information to the receiver;

NOTE 2 In the Access network, the Core entity is the receiver and the DCDCE is the sender.

— PUBLISH method: publisher publishes data to be received by the subscribers.

NOTE 3 In the Access network, the Core entity is the subscriber and the DCDCE is the publisher.

The PUBLISH method is recommended, when multiple Core entities are listening to a single DCDCE.

7.6 Support of mobility

If the network location of the DCDCE changes, then the Access network shall maintain the connectivity

to its Digital Twin.
7.7 Security
The following security issues shall be addressed by the Access network:
— Authentication and authorization:

Authentication is the process for establishing the identity of the user or processor. An authorization

permits access rights or privileges to resources. Appropriate authentication and authorization

shall be supported by the Access network;
— Privacy and confidentiality:

Privacy is the ability to secure individual or group information from public attention. Confidentiality

is the ability to secure information within a group. If data generated by the OME and various IoT

devices is private and sensitive, then the Access network shall provide methods such as data

encryption to ensure that it is not disclosed to unauthorized persons and devices.

8 Requirements for information exchange in Proximity network
8.1 Overview

The Proximity network is an interface between the DCDCE and the OME. The Proximity network is not

necessary, if the OME is directly attached or integrated with the DCDCE.
8.2 Support of local connectivity

The Proximity network shall connect the DCDCE to the OME using Industrial Ethernet or a proprietary

network.
8.3 Support of adaptation

The Proximity network shall support adaptation of data received from OME to data that is understood

by DCDCE.
6 © ISO 2020 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/DIS 23247-4:2020(E)
Annex A
(informative)
Technical discussion -
Implementation options for Digital Twin framework for
manufacturing
A.1 Acronyms of protocols

This clause lists acronyms of protocols or standards that can be considered as an implementation

options of Digital Twin framework for manufacturing.
3D PDF 3Dimensional Portable Document Format
ASS Asset Administration Shell
AES Advanced Encryption Standard
AMF Additive Manufacturing File format
API Application Program Interface
AutomationML Automation Markup Language
B2MML Business To Manufacturing Markup Language
CAD Computer Aided Design
CAM Computer Aided Manufacturing
CBC Cipher-Block Chaining
CCM Counter with CBC-MAC
CDD Common Data Dictionary
CFX Connected Factory Exchange
ECDHE Elliptic-curve Diffie–Hellman
EtherCAT Ethernet for Control Automation Technology
HTTP HyperText Transfer Protocol
IPC Inter-Process Communication
ISA International Society of Automation
JSON JavaScript Object Notation
JT Jupiter Tessellation
LwM2M Lightweight Machine to Machine
MOM Manufacturing Operations Management
© ISO 2020 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO/DIS 23247-4:2020(E)
MQTT Message Queuing Telemetry Transport
MTConnect Machine Tool Connect
OCF Open Connectivity Foundation
OPC-UA Open Platform Communications - Unified Architecture
OpenGL Open Graphics Library
OTD Open Technical Dictionary
PLC Programmable Logic Controller
PSK Phase-Shift Keying
QIF Quality Information Framework
RAMI 4.0 Reference Architectural Model Industrie 4.0
RAPINet Real-time Automation Protocols for Industrial Ethernet
RDF Resource Description Framework
REST REpresentational State Transfer
RSA Rivest–Shamir–Adleman
SHA Secure Hash Algorithm
STEP Standard for the Exchange of Product model data
TSN Time-Sensitive Networking
UUID Universal Unique Identifier
URI Uniform Resource Identifier
WebGL Web Graphics Library
XML eXtensible Markup Language
A.2 Information exchange examples

Figure A.1 shows how information may be exchanged within a Digital Twin Framework using currently

available communication protocols.
8 © ISO 2020 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/DIS 23247-4:2020(E)
Figure A.1 — Information exchange examples
In Figure A.1, there are two DCDCE and OME combinations;

— In the first combination (i.e., left DCDCE/OME), data is collected by the DCDCE through the Proximity

network and sent to the Core entity using the Access network. The OME is controlled by the User

entity through the legacy communication channel. For example, a G-code file is written from PLM

and loaded into the control by an operator;

— In the second combination (i.e., right DCDCE/OME), data is collected directly by the DCDCE within a

single system and sent to the Core entity using the Access network. DCDCE is controlled by the User

entity through the Access network between User entity and DCDCE. For example, a modern CNC

control may support direct numerical control for data input and MTConnect for result reporting.

In both combinations, the Core entity receives data from the DCDCE using the Access network and

informs a User entity of conditions that req
...