Iso/Tc 184/Sc 4/Wg 15 N 114

ISO/TC 184/SC 4/WG 15 N 114

ISO/TC 184/SC 4/WG 15 Digital manufacturing

Email of convenor: [email protected] Convenorship: ANSI (United States)

Text for ISO DIS 23247-1 Ballot r2 Document type: Committee draft

Date of document: 2019-11-21

Expected action: INFO

Background: DIS after editing during November 20 conference call

ISO CD 23247-1:2019(E)

ISO TC 184/SC 4/WG 15

Secretariat: ANSI

Automation systems and integration – Digital Twin framework for manufacturing – Part 1: Overview and general principles

DIS stage

To help you, this guide on writing standards was produced by the ISO/TMB and is available at https://www.iso.org/iso/how-to-write-standards.pdf

A model manuscript of a draft International Standard (known as “The Rice Model”) is available at https://www.iso.org/iso/model_document-rice_model.pdf

ISO CD 23247-1:2019(E)

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 Email: [email protected] Website: www.iso.org

Published in Switzerland

Contents

1 Foreword ...... v 2 Introduction...... vi 3 1 Scope ...... 1 4 2 Normative references ...... 2 5 3 Terms and definitions ...... 2 6 3.1 General terms ...... 2 7 3.1.1 actuator ...... 2 8 3.1.2 area ...... 2 9 3.1.3 control ...... 2 10 3.1.4 element ...... 2 11 3.1.5 enterprise ...... 2 12 3.1.6 entity ...... 3 13 3.1.7 Internet of Things IoT ...... 3 14 3.1.8 management ...... 3 15 3.1.9 physical element ...... 3 16 3.1.10 resource ...... 3 17 3.1.11 sensor ...... 3 18 3.1.12 task ...... 4 19 3.2 Digital Twin manufacturing specific terms ...... 4 20 3.2.1 digital entity ...... 4 21 3.2.2 digital model ...... 4 22 3.2.3 Digital Twin ...... 4 23 3.2.4 Digital Twin modelling ...... 4 24 3.2.5 manufacturing process ...... 4 25 3.2.6 presentation ...... 5 26 3.2.7 representation ...... 5 27 3.2.8 visualization ...... 5 28 3.2.9 view/viewpoint ...... 5 29 3.3 Abbreviated terms ...... 5 30 4 Overview of Digital Twin for manufacturing ...... 7 31 4.1 Concept of Digital Twin...... 7 32 4.2 Digital Twin for manufacturing ...... 7 33 4.3 Applications of Digital Twin for manufacturing ...... 8 34 4.3.1 Real time control ...... 8 35 4.3.2 Off-line analytics ...... 8 36 4.3.3 Predictive maintenance ...... 8 37 4.3.4 Health check ...... 8 38 4.3.5 Engineering design ...... 8 39 4.4 Benefits of Digital Twin for manufacturing ...... 8 40 4.4.1 In-loop planning and validation ...... 8 41 4.4.2 Production scheduling assurance ...... 9 42 4.4.3 Enhanced understanding of manufacturing elements...... 9 43 4.4.4 Dynamic risk management ...... 9 44 4.4.5 Cost reduction ...... 9 45 4.5 Elements of Digital Twin for manufacturing ...... 9 46 4.5.1 Observable manufacturing element ...... 9 47 4.5.2 Digital elements ...... 10 48 5 General principles of Digital Twin framework for manufacturing...... 11 49 5.1 Overview ...... 11

50 5.2 Standardization Scope of Digital Twin framework for manufacturing ...... 11 51 5.2.1 Limitations and boundaries ...... 11 52 5.3 Requirements of Digital Twin for manufacturing...... 12 53 5.3.1 General requirements ...... 12 54 5.3.2 Digital Twin modelling requirements ...... 12 55 5.3.3 Information exchange requirements ...... 13 56 5.4 Hierarchical modelling of Digital Twin for manufacturing ...... 13 57 Bibliography ...... 14

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, 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.

58 Introduction

59 ISO 23247 series defines a framework to support the creation of Digital Twins of observable 60 manufacturing elements including personnel, equipment, materials, processes, facilities, environment, 61 and products.

62 The scope of the four parts of this series are defined below:

63 - Part 1: Overview and general principles

64 Provides an overview of Digital Twin for manufacturing, describes general principles, and 65 provides requirements and guidance for developing a Digital Twin framework for 66 manufacturing;

67 - Part 2: Reference architecture

68 Provides a reference architecture goals and objectives, reference model, and reference 69 architectural views for a Digital Twin framework for manufacturing

70 - Part 3: Digital representation of manufacturing elements

71 Identifies manufacturing elements of the Digital Twin framework for manufacturing that shall 72 be represented in digital models;

73 - Part 4: Information exchange

74 Identifies technical requirements for information synchronization and information exchange 75 within the Digital Twin framework for manufacturing.

76 The types of manufacturing that can be supported by an implementation of the framework will depend 77 on the technologies selected to implement its functional elements.

78 Use cases for Digital Twin framework for manufacturing will be detailed in technical reports attached to 79 this series of standards.

1 Automation systems and integration – Digital Twin framework for 2 manufacturing – Part 1: Overview and general principles

3 1 Scope

4 This part of ISO 23247 provides an overview and general principles of Digital Twin for manufacturing.

5 ISO 23247 series defines a framework to support the creation of Digital Twins of observable 6 manufacturing elements including personnel, equipment, materials, processes, facilities, environment, 7 and products.

8 The following are within the scope of this part of ISO 23247;

9 - scope statement for ISO 23247 as a whole;

10 - overview of ISO 23247;

11 - structure of ISO 23247;

12 - terms and definitions used throughout ISO 23247;

13 - overview of Digital Twin framework for manufacturing;

14 - requirements of Digital Twin for manufacturing.

15 The following are described in other parts of ISO 23247;

16 - reference architecture of the Digital Twin framework for manufacturing (Part 2);

17 - digital representation of manufacturing elements of the Digital Twin framework for

18 manufacturing (Part 3);

19 - information exchange of the Digital Twin framework for manufacturing (Part 4);

20 - use cases of the Digital Twin framework for manufacturing to be detailed in technical reports.

21 The following are outside of the scope of ISO 23247;

22 - selection of the implementation methods and technologies for a Digital Twin for manufacturing;

23 - selection of the communication protocols for a Digital Twin for manufacturing;

24 - selection of the manufacturing devices and other resources to be represented by a Digital Twin;

25 - selection of the manufacturing processes to be represented by a Digital Twin;

26 - selection of the manufacturing products to be represented by a Digital Twin;

27 - design and process planning, and other non-manufacturing stages of the product lifecycle.

28 2 Normative references

29 There are no normative references in this document.

30 3 Terms and definitions

31 For the purposes of this document, the following terms and definitions apply.

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

33 — ISO Online browsing platform: available at https://www.iso.org/obp

34 — IEC Electropedia: available at http://www.electropedia.org/

35 3.1 General terms

36 3.1.1 37 actuator

38 device that provides a physical output in response to an input signal in a predetermined way

39 [SOURCE: ISO/IEC 29182‑ 2]

40 3.1.2 41 area

42 physical, geographical or logical grouping of resources determined by the site

43 [SOURCE: IEC 62264-1:2013]

44 3.1.3 45 control

46 purposeful action on or in a process to meet specified objectives

47 [SOURCE: IEV 351-42-19]

48 3.1.4 49 element

50 basic system part that has the characteristics of state, behaviour, and identification

51 [SOURCE: ISO 14258:1998, 2.2.4]

52 3.1.5 53 enterprise

54 one or more organizations sharing a definite mission, goals and objectives which provides an output 55 such as a product or service

56 [SOURCE: IEC 62264-1:2013]

57 3.1.6 58 entity

59 thing (physical or non-physical) having a distinct existence

60 [SOURCE: ISO/IEC 15459-3:2014, 3.1]

61 3.1.7 62 Internet of Things 63 IoT

64 infrastructure of interconnected entities, people, systems and information resources together with 65 services which processes and reacts to information from the physical and virtual world

66 [SOURCE: ISO/IEC 20924:2018]

67 3.1.8 68 management

69 direction, control, and coordination of work performed to develop a product or perform a service

70 [SOURCE: ISO/IEC/IEEE 24765:2017, 3.3064]

71 3.1.9 72 physical element

73 thing that has material existence in physical world

74 3.1.10 75 resource

76 any device, tool and means, except raw material and final product components, at the disposal of the 77 enterprise to produce goods or services

78 Note 1 to entry: Resources as they are defined here include human resources considered as specific means with a 79 given capability and a given capacity. Those means are considered as being able to be involved in the 80 manufacturing process through assigned tasks. That does not include any modelling of an individual or common 81 behaviour of human resource except in their capability to perform a given task in the manufacturing process (e.g.: 82 transformation of raw material or component, provision of logistic services). That means that human resources 83 are only considered, as the other, from the point of view of their functions, their capabilities and their status (e.g.: 84 idle, busy). That excludes any modelling or representation of any aspect of individual or common «social» 85 behaviour.

86 Note 2 to entry: This definition includes ISO 10303-49 definition.

87 [SOURCE: ISO 15531-1:2004, 3.6.43]

88 3.1.11 89 sensor

90 device that observes and measures a physical property of a natural phenomenon or man-made process 91 and converts that measurement into a signal

92 Note 1 to entry: Signal can be electrical, chemical, etc.

93 [SOURCE: ISO/IEC 29182‑ 2]

94 3.1.12 95 task

96 activities required to achieve a goal

97 Note 1 to entry: These activities can be physical and/or cognitive.

98 [SOURCE: ISO 9241‑ 11:1998, 3.9]

99 3.2 Digital Twin manufacturing specific terms

100 3.2.1 101 digital entity 102 computational and/or data element

103 Note 1 to entry: A digital entity can exist as a cloud service or as a service in a data centre, or as a network element 104 or as an IoT gateway.

105 [SOURCE: ISO/IEC 20924:2018, 3.1.14]

106 3.2.2 107 digital model

108 fit for purpose digital representation of something designed to support decisions related to it

109 Note 1 to entry: It is recognized that some practitioners in some industries may refer to this as a “Digital Twin.” 110 For the purpose of this document, “Digital Twin” refers to a specific subclass of digital models.

111 3.2.3 112 Digital Twin

113 fit for purpose digital representation of some realized thing or process with a means to enable 114 convergence between the realised instance and digital instance at an appropriate rate of 115 synchronisation

116 3.2.4 117 Digital Twin modelling

118 procedure of creating a digital model of an observable element

119 3.2.5 120 manufacturing process

121 structured set of activities or operations performed upon material to convert it from the raw material 122 or a semi-finished state to a state of further completion

123 Note 1 to entry: Manufacturing processes may be arranged in process layout, product layout, cellular layout or 124 fixed position layout. Manufacturing processes may be planned to support make-to-stock, make-to-order, 125 assemble-to-order, etc., based on strategic use and placements of inventories.

126 [SOURCE: ISO 15531-1:2004, 3.6.25]

127 3.2.6 128 presentation

129 manner in which information is displayed for use by a human Note 1 to entry: Digital model can be 130 presented audibly and visually.

131 [SOURCE: ASME Y14.47-2019]

132 3.2.7 representation

133 manner in which information is stored for interpretation by a machine

134 [SOURCE: ASME Y14.47-2019]

135 3.2.8 136 visualization

137 use of computer graphics and image processing to present models or 138 characteristics of processes or objects for supporting human understanding

139 Note 1 to entry: Examples: A display image of a CNC machine milling an aluminium block.

140 Note 2 to entry: scientific visualization; visualization: terms and definition standardized by ISO/IEC [ISO/IEC 141 2382-13:1996].

142 [SOURCE: ISO/IEC 2382:2015, 2125942, Note 1 to entry changed to address manufacturing examples. 143 Note 3 to entry deleted]

144 3.2.9 145 view/viewpoint

146 projection of a model, seen from a given perspective or vantage point and which omits entities that are 147 not relevant to this perspective

148 [SOURCE: ISO/IEC 19501:2005]

149 3.3 Abbreviated terms

150 API Application Program Interface 151 CAD Computer Aided Design 152 CAM Computer Aided Manufacturing 153 DCDCD Data Collecting and Device Controlling Domain 154 DTME Digital Twin of Observable Manufacturing Element 155 ERP Enterprise Resource Planning 156 IE Information Exchange 157 IoT Internet of Things 158 IPC Inter-Process Communication 159 MES Manufacturing Execution System 160 O&M Operation and Management 161 OME Observable Manufacturing Element

162

163 4 Overview of Digital Twin for manufacturing

164 4.1 Concept of Digital Twin

165 A Digital Twin is a fit for purpose digital representation of some realized thing or process with a means 166 to enable convergence between the realised instance and the digital instance at an appropriate rate of 167 synchronisation

168 Digital Twin may exist across the entire life-cycle and can leverage aspects of the virtual environment 169 (high-fidelity, multi-physics, external data sources, etc.), computational techniques (virtual testing, 170 optimisation, prediction, etc.), and aspects of the physical environment (historical performance, 171 customer feedback, cost, etc.) to improve elements of the overall system (design, behaviour, 172 manufacturability, etc.). [15]

173 NOTE Definitions in this document are being harmonized with those in Ad Hoc Group Digital Twin, 174 currently published as ISO/TC 184/SC 1 N517.

175 4.2 Digital Twin for manufacturing

176

177 Figure 1 – Concept of Digital Twin for manufacturing

178 A Digital Twin for manufacturing updates as its physical counterpart changes to represent its status, 179 conditions, product geometries, states of resources, and any other observable status and conditions.

180 A Digital Twin is kept current with its observable manufacturing elements at an appropriate rate of 181 synchronization. Additionally, a Digital Twin for manufacturing may recall previous states of the 182 observable manufacturing elements.

183 The Digital Twin enables functionalities to synchronize its representation with its corresponding 184 observable manufacturing elements by constantly exchanging operational and environmental data.

185 A Digital Twin assists with detecting anomalies in the manufacturing processes and to achieve various 186 functional objectives such as real time control, off-line analytics, health check, predictive maintenance, 187 synchronous monitoring/alarm, manufacturing operations management (MOM) optimization, in- 188 process adaptation, Big Data analytics, machine learning, etc.

189 The visibility into process and execution enabled by Digital Twin for manufacturing enhances business 190 cooperation and multiple other efficiencies such as in-loop planning and validation, production 191 scheduling assurance, enhancement of understanding manufacturing elements, dynamic risk 192 management, cost reduction, etc.

193 Examples of applications and benefits are given in 4.3 and 4.4, but are not limited to those given.

194 4.3 Applications of Digital Twin for manufacturing

195 4.3.1 Real time control

196 A real time control application uses the current state of the Digital Twins to make changes to a 197 manufacturing process in real time.

198 4.3.2 Off-line analytics

199 An off-line analytics application uses the changed state of the Digital Twins to make recommendations 200 about the manufacturing process.

201 4.3.3 Predictive maintenance

202 A predictive maintenance application is a real-time or off-line application that uses the Digital Twins to 203 schedule and adapt maintenance activities for the production equipment.

204 4.3.4 Health check

205 A health check application uses the Digital Twins to check conditions of observable manufacturing 206 elements and if necessary, schedules maintenance.

207 4.3.5 Engineering design

208 An engineering design application uses Digital Twins to learn about previously manufactured products 209 to optimize new and existing product designs.

210 4.4 Benefits of Digital Twin for manufacturing

211 Use case technical reports will provide examples on how to achieve these benefits.

212 4.4.1 In-loop planning and validation

213 Digital Twin for manufacturing facilitates in-loop planning, validation, and adjustment of manufacturing 214 processes through simulation.

215 4.4.2 Production scheduling assurance

216 Digital Twin for manufacturing facilitates real time monitoring of production, allowing management to 217 dynamically adjust the manufacturing throughput to meet a production schedule.

218 4.4.3 Enhanced understanding of manufacturing elements

219 Information of observable manufacturing elements contained within Digital Twins facilitates accurate 220 planning of manufacturing and production schedules.

221 4.4.4 Dynamic risk management

222 Applications of Digital Twin for manufacturing such as real time control, off-line analytics, predictive 223 maintenance, health check, etc., allows management to improve prediction and control of current and 224 future risks.

225 4.4.5 Cost reduction

226 Overall, various applications of Digital Twin for manufacturing reduce manufacturing and management 227 cost.

228 4.5 Elements of Digital Twin for manufacturing

229 4.5.1 Observable manufacturing element

230 An observable manufacturing element is an item that has observable physical presence or operation in 231 manufacturing.

232 4.5.1.1 Personnel

233 Personnel in manufacturing generally include those employees who are engaged directly or indirectly 234 in manufacturing processes.

235 NOTE In Digital Twin for manufacturing, availability and certification level of personnel are examples of digital 236 models.

237 4.5.1.2 Equipment

238 Equipment is a physical element that carries out an operation that is directly or indirectly involved in 239 manufacturing processes. Examples of equipment are hand tools, a CNC machine, a conveyer belt, 240 robots, etc.

241 4.5.1.3 Material

242 Material is physical matter that becomes a part or the whole of a product i.e., metal block, glass panel, 243 etc., or is used to aid manufacturing processes, i.e., cleaning fluid, coolant, etc.

244 4.5.1.4 Process

245 A process is an observable physical operation within manufacturing. Processes are inclusive of 246 manufacturing processes, maintenance processes, management processes, etc.

247 4.5.1.5 Facility

248 Facility is infrastructure that is related to or affects manufacturing. Examples of facility are special 249 purpose rooms, buildings, energy supply, water supply, environmental controllers, etc.

250 4.5.1.6 Environment

251 Environment is necessary condition that shall be supplied by facilities for the correct execution of a 252 manufacturing process. Examples of environmental conditions are temperature, humidity, illuminance, 253 etc.

254 4.5.1.7 Product

255 Product is a desired output or by-product of manufacturing process. Depending on the manufacturing 256 process stage, from a business perspective, a product can be classified as an intermediate product or an 257 end product.

258 4.5.1.8 Supporting document

259 A supporting document is any form of artefact (requirement, plan, model, specification, configuration) 260 that helps manufacturing.

261 4.5.2 Digital elements

262 4.5.2.1 Application of Digital Twin for manufacturing

263 An application operating on the Digital Twin for manufacturing reports on, makes predictions about, or 264 executes adjustments to the current state of manufacturing elements.

265 4.5.2.2 Product definition

266 A product definition is specifications or properties of a product that are necessary to characterise it 267 such as dimensions, tolerances, surface finish, etc.

268 4.5.2.3 Process definition

269 A process definition is a specification of the personnel, equipment, material resources, and operations 270 that are required to perform a manufacturing process.

271

272 5 General principles of Digital Twin framework for manufacturing

273 5.1 Overview

274 The Digital Twin framework for manufacturing provides guidance on how to construct a Digital Twin 275 for manufacturing, specifies how applications can interoperate, and how data from different sources 276 can be integrated. However, it does not specify any implementation technologies.

277 5.2 Standardization Scope of Digital Twin framework for manufacturing

278 5.2.1 Limitations and boundaries

279

280 Figure 2 – High-level Concept of Digital Twin framework for manufacturing

281 Figure 2 shows the high-level concept of Digital Twin framework for manufacturing. Digital Twin and 282 the physical world, depicted as Physical Manufacturing, are connected and synchronized through Data 283 Collection & Device Control medium. Synchronization between digital entities and physical 284 manufacturing elements, either online or offline, ensures that the manufacturing systems are constantly 285 optimized as the Digital Twins receives real-time performance information from the physical system. 286 The Digital Twin is implemented using appropriate methods and tools with specific objective and scope. 287 The integration between model components within a Digital Twin is enabled through application of 288 relevant interoperability standards.

289 A Digital Twin is context-dependent and could be a partial representation of a physical system. It may 290 consist only of relevant data and models that are specifically designed for their intended purpose.

291 5.3 Requirements of Digital Twin for manufacturing

292 5.3.1 General requirements

293 5.3.1.1 Data acquisition

294 A Digital Twin for manufacturing shall collect sensory data using sensors installed on or around 295 manufacturing equipment.

296 NOTE Sensors for the identification and/or detection of presence of personnel might be installed in 297 specific access control facilities

298 5.3.1.2 Communication

299 Communication shall transfer data or information between elements of Digital Twin for manufacturing.

300 5.3.1.3 Presentation

301 Information shall be represented in a format that human or computer can recognize. Examples of a 302 recognizable format are audio, video, image, text, data bitstream, etc.

303 5.3.1.4 Data analysis

304 Data acquired in manufacturing processes shall be analysed to understand the state of observable 305 manufacturing elements.

306 5.3.1.5 Management

307 Digital Twins shall be managed as necessary to optimize resources and maximize benefits.

308 5.3.1.6 Synchronization

309 In Digital Twin implementation, virtual elements and the associated data shall be timely coupled with 310 the corresponding physical or functional element and data.

311 5.3.1.7 Data store

312 A data store shall be present to store data permanently or temporarily for the purpose of data 313 modelling, exchange, analysis, or archiving, etc.

314 5.3.1.8 Simulation

315 A Digital Twin shall simulate manufacturing elements in operation.

316 5.3.1.9 Viewpoint

317 Digital Twin shall support different views for different objectives.

318 5.3.2 Digital Twin modelling requirements

319 5.3.2.1 Fidelity

320 A digital model shall accurately describe the relevant aspects of its physical counterpart.

321 5.3.2.2 Extensibility

322 Digital model of the physical element shall be extensible to support integration, addition, or 323 enhancement.

324 5.3.2.3 Interoperability

325 Digital model of the physical element shall be compatible to other types of digital models, within a given 326 Digital Twin manufacturing system.

327 5.3.2.4 Granularity

328 Digital model of the physical element shall provide an insight at different levels of granularity.

329 5.3.3 Information exchange requirements

330 5.3.3.1 Timely-manner networking

331 In Digital Twin manufacturing, information shall be exchanged between Digital Twin manufacturing 332 system entities within a given time and frequency using appropriate networking protocols.

333 5.3.3.2 Synchronization

334 The status of the digital entities in Digital Twin shall be synchronized with the status of the observable 335 manufacturing elements, or vice versa, using timely-manner networking.

336 5.3.3.3 Accuracy

337 Information shall be kept accurate for exchange.

338 5.3.3.4 Integrity

339 Information shall be maintained unchanged in exchange procedure.

340 5.4 Hierarchical modelling of Digital Twin for manufacturing

341 A Digital Twin for manufacturing may be purposely realized in different abstraction levels, e.g., machine 342 level, area level, site level, and enterprise level. Digital Twin framework for manufacturing may apply to 343 all the levels of the functional and role-based hierarchy defined in IEC 62264-1[5].

344

345 Bibliography

346 [1] ISO 23247-2, Automation systems and integration — Digital Twin framework for manufacturing 347 — Part 2: Reference architecture

348 [2] ISO 23247-3, Automation systems and integration — Digital Twin framework for manufacturing 349 — Part 3: Digital representation of manufacturing elements

350 [3] ISO 23247-4, Automation systems and integration — Digital Twin framework for manufacturing 351 — Part 4: Information exchange

352 [4] ITU-T Y.2061, Requirements for the support of machine-oriented communication applications in 353 the next generation network environment

354 [5] IEC 62264-1:2013, Enterprise-control system integration — Part 1: Models and terminology

355 [6] ISO 14258:1998, Industrial automation systems — Concepts and rules for enterprise models

356 [7] ISO/IEC 15459-3:2014, Information technology — Automatic identification and data capture 357 techniques — Unique identification — Part 3: Common rules

358 [8] ISO/IEC 20924:2018, Information technology — Internet of Things (IoT) — Vocabulary

359 [9] ISO/IEC/IEEE 24765:2017, Systems and software engineering — Vocabulary

360 [10] ISO 15531-1:2004, Industrial automation systems and integration — Industrial manufacturing 361 management data — Part 1: General overview

362 [11] ISO/IEC TR 29181-9:2017, Information technology — Future Network — Problem statement and 363 requirements — Part 9: Networking of everything

364 [12] ISO 9241‑ 11:1998, Ergonomic requirements for office work with visual display terminals (VDTs) 365 — Part 11: Guidance on usability

366 [13] ISO/IEC 2382:2015, Information technology — Vocabulary

367 [14] ISO/IEC 19501:2005, Information technology — Open Distributed Processing — Unified 368 Modeling Language (UML) Version 1.4.2

369 [15] ISO/TC 184/SC 1 N517, Ad Hoc Group: Data Architecture of the Digital Twin

ISO/TC 184/SC 4/WG 15 Digital manufacturing

Email of convenor: [email protected] Convenorship: ANSI (United States)

Text for ISO DIS 23247-2 Ballot r2 Document type: Committee draft

Date of document: 2019-12-09

Expected action: INFO

Background: Latest draft of DIS text.

ISO DIS 23247-2:2019(E)

ISO TC 184/SC 4/WG 15

Secretariat: ANSI

Automation systems and integration — Digital Twin framework for manufacturing — Part 2: Reference architecture

DIS stage

Warning for WDs and CDs This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard. 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 DIS 23247-2:2019(E)

1 © ISO 2019, Published in Switzerland

2 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized 3 otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the 4 internet or an intranet, without prior written permission. Permission can be requested from either ISO at the 5 address below or ISO’s member body in the country of the requester.

6 ISO copyright office 7 Ch. de Blandonnet 8 • CP 401 8 CH-1214 Vernier, Geneva, Switzerland 9 Tel. + 41 22 749 01 11 10 Fax + 41 22 749 09 47 11 [email protected] 12 www.iso.org

13 Contents

14 Foreword ...... iv 15 Introduction...... v 16 1 Scope ...... 1 17 2 Normative references ...... 1 18 3 Terms and definitions ...... 1 19 4 Digital Twin reference architecture for manufacturing goals and objectives ...... 3 20 5 Digital Twin reference models for manufacturing ...... 4 21 5.1 Domain-based reference model ...... 4 22 5.1.1 Domains of Digital Twin for manufacturing ...... 4 23 5.1.2 Observable manufacturing domain ...... 5 24 5.1.3 Data collection and device control domain ...... 5 25 5.1.4 Digital Twin domain ...... 5 26 5.1.5 Digital Twin user domain ...... 5 27 5.2 Entity-based reference model ...... 5 28 5.2.1 Entities of Digital Twin for manufacturing ...... 5 29 5.2.2 Observable manufacturing element ...... 6 30 5.2.3 Data collection and device control entity ...... 6 31 5.2.4 Digital Twin system entity ...... 7 32 5.2.5 Digital Twin user entity ...... 7 33 5.2.6 Cross-system entity ...... 7 34 5.3 Domain-entity mixed reference model ...... 8 35 6 Digital Twin reference architectural views for manufacturing ...... 9 36 6.1 General ...... 9 37 6.2 Functional view ...... 9 38 6.2.1 Functional reference architecture ...... 9 39 6.2.2 Functional entity of observable manufacturing element ...... 9 40 6.2.3 Functional entity of data collection and device control entity ...... 9 41 6.2.4 Functional entity in Digital Twin system entity ...... 10 42 6.2.5 Functional entity in Digital Twin user entity ...... 11 43 6.2.6 Functional entity in cross-system entity ...... 11 44 6.3 Networking view ...... 12 45 6.3.1 Networking reference architecture ...... 12 46 6.3.2 Transmission network ...... 12 47 6.3.3 Service network (optional) ...... 13 48 6.3.4 User network ...... 13 49 Bibliography ...... 14 50 51

52 Foreword

53 ISO (the International Organization for Standardization) is a worldwide federation of national 54 standards bodies (ISO member bodies). The work of preparing International Standards is normally 55 carried out through ISO technical committees. Each member body interested in a subject for which a 56 technical committee has been established has the right to be represented on that committee. 57 International organizations, governmental and non-governmental, in liaison with ISO, also take part in 58 the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all 59 matters of electrotechnical standardization.

60 The procedures used to develop this document and those intended for its further maintenance are 61 described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the 62 different types of ISO documents should be noted. This document was drafted in accordance with the 63 editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).

64 Attention is drawn to the possibility that some of the elements of this document may be the subject of 65 patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of 66 any patent rights identified during the development of the document will be in the Introduction and/or 67 on the ISO list of patent declarations received (see www.iso.org/patents).

68 Any trade name used in this document is information given for the convenience of users and does not 69 constitute an endorsement.

70 For an explanation on the voluntary nature of standards, the meaning of ISO specific terms and 71 expressions related to conformity assessment, as well as information about ISO's adherence to the 72 World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following 73 URL: www.iso.org/iso/foreword.html.

74 This document was prepared by Technical Committee ISO/TC 184, Automation systems and integration, 75 Subcommittee SC 4, Industrial Data.

76 A list of all parts in the ISO 23247 series can be found on the ISO website.

77 Any feedback or questions on this document should be directed to the user’s national standards body. A 78 complete listing of these bodies can be found at www.iso.org/members.html.

79 Introduction

80 ISO 23247 series defines a framework to support the creation of Digital Twins of observable 81 manufacturing elements including personnel, equipment, materials, processes, facilities, environment, 82 products, and supporting documents.

83 The scope of the four parts of this series are defined below:

84 ─ Part 1: Overview and general principles 85 Provides an overview of Digital Twin for manufacturing, describes general principles, and provides 86 requirements and guidance for developing a Digital Twin framework for manufacturing;

87 ─ Part 2: Reference architecture 88 Provides a reference architecture goals and objectives, reference model, and reference architectural 89 views for a Digital Twin framework for manufacturing

90 ─ Part 3: Digital representation of manufacturing elements 91 Identifies manufacturing elements of the Digital Twin framework for manufacturing that shall be 92 represented in digital models;

93 ─ Part 4: Information exchange 94 Identifies technical requirements for information synchronization and information exchange within 95 the Digital Twin framework for manufacturing.

96 The types of manufacturing that can be supported by an implementation of the framework will depend 97 on the technologies selected to implement its functional elements.

98 Use cases for Digital Twin framework for manufacturing will be detailed in a series of technical reports 99 attached to this series.

ISO DIS 23247-2:2019(E)

100 Automation systems and integration — Digital Twin framework 101 for manufacturing — Part 2: Reference architecture

102 1 Scope

103 This part of ISO 23247 provides a reference architecture of Digital Twin for manufacturing.

104 ISO 23247 series defines a framework to support the creation of Digital Twins of observable 105 manufacturing elements including personnel, equipment, materials, processes, facilities, environment, 106 products, and supporting documents.

107 The following are within the scope of this part of ISO 23247;

108 ─ reference architecture goals and objectives, 109 ─ reference model, and 110 ─ reference architectural views

111 The following are described in other parts of ISO 23247;

112 ─ overview and general principles (Part 1) 113 ─ digital representation of manufacturing elements of the Digital Twin framework for manufacturing 114 (Part 3); 115 ─ information exchange of the Digital Twin framework for manufacturing (Part 4); 116 ─ use cases of the Digital Twin framework for manufacturing are to be detailed in technical reports.

117 The following are outside of the scope of ISO 23247;

118 ─ selection of the implementation methods and technologies for a Digital Twin for manufacturing; 119 ─ selection of the communication protocols for a Digital Twin for manufacturing; 120 ─ selection of the manufacturing devices and other resources to be represented by a Digital Twin; 121 ─ selection of the manufacturing processes to be represented by a Digital Twin; 122 ─ selection of the manufacturing products to be represented by a Digital Twin; 123 ─ design and process planning, and other non-manufacturing stages of the product lifecycle.

124 2 Normative references

125 The following documents are referred to in the text in such a way that some or all of their content 126 constitutes requirements of this document. For dated references, only the edition cited applies. For 127 undated references, the latest edition of the referenced document (including any amendments) applies.

128 ISO 23247-1, Automation systems and integration — Digital Twin for manufacturing framework — Part 129 1: Overview and general principles

130 ISO/IEC 30141, Internet of Things (IoT) — Reference architecture

131 3 Terms and definitions

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

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

135 — IEC Electropedia: available at http://www.electropedia.org/

136 — ISO Online browsing platform: available at https://www.iso.org/obp

137 3.1 138 observable manufacturing domain 139 spatial/logical/functional area of the observable manufacturing resources

140 EXAMPLE Spatial/logical/functional area of machine tool

141 3.2 142 data collection and device control domain 143 spatial/logical/functional area of monitoring and collecting data from observable manufacturing 144 domain, and controlling devices in observable manufacturing domain

145 EXAMPLE Spatial/logical/functional area of machine tool controller

146 3.3 147 data collection and device control entity 148 (a set of) system(s) or device(s) providing data collection and device control in data collection and 149 device control domain

150 3.4 151 Digital Twin domain 152 spatial/logical/functional area of overall operation and management of Digital Twin including 153 provisioning, managing, monitoring, and optimization

154 EXAMPLE Spatial/logical/functional area of Digital Twin server implementing Digital Twin management, 155 simulation, authentication, and authorization

156 3.5 157 Digital Twin system entity 158 set of sub-systems providing functionalities for Digital Twins such as realisation, management, 159 synchronization and simulation

160 3.6 161 Digital Twin user domain 162 spatial/logical/functional area using applications and services provided in the Digital Twin domain

163 3.7 164 Digital Twin user entity 165 system(s) that uses applications and services provided in the Digital Twin system entity

166 4 Digital Twin reference architecture for manufacturing goals and objectives

167 Digital Twin reference architecture for manufacturing defines reference models and architectural 168 views.

169 Digital Twin reference architecture for manufacturing provides guidance for managing Digital Twins in 170 manufacturing. The architecture increases understanding of Digital Twins for stakeholders including 171 device manufacturers, application developers, users, etc.

172 The Digital Twin architecture uses the Internet of Things (IoT) as its defining technology. ISO/IEC 173 30141 defines the IoT reference models to include a domain-based reference model and an entity-based 174 reference model. It also defines reference architectural views including a functional view, a system 175 deployment view, a networking view, and a usage view.

176 This document includes the following descriptions in addition to those contained in ISO/IEC 30141:

177 ─ Digital Twin reference models for manufacturing, describing structure of the domains and structure 178 of the entities; 179 ─ a set of relevant architectures in terms of functional and networking views 180

181

182 Figure 1 – Outline of Digital Twin reference architecture for manufacturing

183 Figure 1 shows outline of Digital Twin reference architecture for manufacturing to define relevant 184 reference models and architectural views derived from requirements specified in ISO 23247-1.

185 5 Digital Twin reference models for manufacturing

186 5.1 Domain-based reference model

187 5.1.1 Domains of Digital Twin for manufacturing

188 Figure 2 shows a domain-based reference model of Digital Twin for manufacturing. Domain-based 189 reference model is useful to describe various tasks that have to be performed in separate areas, by 190 allowing a logical and sometimes physical subdivision. In other words, domains are used to sort 191 functions into areas of responsibility.

192 In Digital Twin for manufacturing, domains are classified into four categories as follows:

193 ─ Digital Twin user domain 194 ─ Digital Twin domain 195 ─ data collection and device control domain 196 ─ observable manufacturing domain

197 Observable manufacturing domain is out of scope of Digital Twin for manufacturing, however, this 198 document describes observable manufacturing domain to enhance understanding of Digital Twin for 199 manufacturing. 200

201

202 Figure 2 – Domain-based Digital Twin reference model for manufacturing

203 This classification is a logical grouping of tasks and functions, which are performed by the functional 204 entities (FE) explained in 6.2. Entities in a domain interact with other entities in other domains by 205 means of a set of networks described in 6.3.

206 5.1.2 Observable manufacturing domain

207 Observable manufacturing domain consists of the physical manufacturing resources such as personnel, 208 equipment, material, process, facility, and environment. Observable manufacturing domain shall be 209 monitored and sensed for data collection and device control in Digital Twin for manufacturing.

210 5.1.3 Data collection and device control domain

211 Data collection and device control domain monitors and collects data from sensory devices in 212 observable manufacturing domain, and control and actuate devices in observable manufacturing 213 domain. Data collection and device control domain links observable manufacturing elements and digital 214 entities for synchronization.

215 5.1.4 Digital Twin domain

216 Digital Twin domain is responsible for overall operation and management of Digital Twin for 217 manufacturing including provisioning, managing, monitoring, and optimization. In detail, digital 218 modeling, presentation, and synchronization of observable manufacturing element are done in Digital 219 Twin domain.

220 Digital Twin domain hosts the applications and services such as simulation, analysis, etc. In addition, 221 Digital Twin domain provides access to entities of Digital Twin for manufacturing and interaction with 222 external entities such as peer Digital Twin domain by guaranteeing interoperability.

223 5.1.5 Digital Twin user domain

224 In Digital Twin for manufacturing, a user can be a person, a device, or a system who uses applications 225 and services provided by Digital Twin domain.

226 5.2 Entity-based reference model

227 5.2.1 Entities of Digital Twin for manufacturing

228 Entity-based reference model breaks down Digital Twin for manufacturing into system level in 229 conjunction with the domain concept, which helps to understand system composition of Digital Twin 230 for manufacturing.

231

232 Figure 3 – Entity-based Digital Twin reference model for manufacturing

233 Figure 3 shows an entity-based Digital Twin reference model for manufacturing. A set of operation and 234 management sub-system entity, application and service sub-system entity, and resource access and 235 interchange sub-system entity digitally represents observable manufacturing elements as Digital Twins, 236 and maintains the Digital Twins, therefore it is called Digital Twin system entity.

237 5.2.2 Observable manufacturing element

238 Observable manufacturing element shall be monitored and sensed, and may be actuated and controlled 239 by data collection and device control entity. It includes personnel, equipment, material, process, etc.

240 5.2.3 Data collection and device control entity

241 5.2.3.1 General

242 Digital Twin shall have one or more data collection and device control entity, because Digital Twin 243 consists of one or more observable manufacturing elements that shall be controlled.

244 5.2.3.2 Data collection sub-entity

245 Data collection sub-entity interacts with the observable manufacturing element by collecting 246 information from monitoring and sensing devices.

247 Digital Twin system entity uses the collected information to synchronize the Digital Twin with its 248 corresponding observable manufacturing element.

249 Data collection sub-entity may include executables in the form of a program or an agent.

250 5.2.3.3 Device control sub-entity

251 Device control sub-entity interacts with the observable manufacturing element by controlling and 252 actuating devices such as CNC controls. Device control sub-entity may include executables in the form of 253 a program or an agent.

254 5.2.4 Digital Twin system entity

255 5.2.4.1 Operation and management sub-system entity

256 Operation and management sub-system entity operates and manages Digital Twin. Operation and 257 management sub-system entity shall maintain information of observable manufacturing element both 258 in production and in design, including digital modeling, presentation, and synchronization. In addition, 259 operation and management sub-system entity supports capabilities related to operation and 260 management of overall Digital Twin system entity such as providing administration functionality to 261 Digital Twin user entity.

262 5.2.4.2 Application and service sub-system entity

263 Digital Twin system entity provides various kinds of applications and services including simulation of 264 manufacturing system, analysis of data captured from observable manufacturing element, reporting of 265 actions such as production, etc. Application and service sub-system entity provides functionalities 266 related to applications and services.

267 5.2.4.3 Resource access and interchange sub-system entity

268 Resource access and interchange sub-system entity provides access to functionalities of Digital Twin 269 system entity to Digital Twin user entity with controlled interfaces for application and service 270 functionalities, administration functionalities, and business functionalities in support of interoperability. 271 Access and interchange control functions may vary depending on the type of Digital Twin user entity 272 requiring authentication, authorization and other necessary actions.

273 5.2.5 Digital Twin user entity

274 As shown in Figure 3, Digital Twin user entity can be any entity that can utilize Digital Twin for 275 manufacturing such as a person, a device, manufacturing execution system (MES)/enterprise resource 276 planning (ERP) systems, or even peer Digital Twin system entity. Appropriate interface shall be offered 277 to Digital Twin user entity, where application specific capabilities are supplied by an underlying 278 application that interacts with Digital Twin system entity by means of APIs controlled by Resource 279 access and interchange sub-system entity.

280 5.2.6 Cross-system entity

281 Cross-system entity is an entity that resides across domains to provide common functionalities such as 282 information exchange, data assurance, security support, etc.

283 5.3 Domain-entity mixed reference model

284 Figure 4 shows a domain-entity mixed reference model. This is a reference model, therefore both 285 domains and entities can be extended, merged, or added depending on practical use cases.

286

287 Figure 4 – Domain-entity mixed Digital Twin reference model for manufacturing

288

289 6 Digital Twin reference architectural views for manufacturing

290 6.1 General

291 This clause defines functional view and networking view of Digital Twin reference architecture for 292 manufacturing.

293 6.2 Functional view

294 6.2.1 Functional reference architecture

295 Digital Twin reference architecture for manufacturing provides an infrastructure to support a large 296 number of Digital Twins. Figure 5 shows a functional reference architecture to support requirements 297 defined in ISO 23247-1.

298

299 Figure 5 – Functional reference architecture of Digital Twin for manufacturing – decomposition 300 of functional entities (FEs)

301 6.2.2 Functional entity of observable manufacturing element

302 Resource-specific FE is a functional entity of an observable manufacturing element. It shall be digitally 303 modelled to be utilized by entities in Digital Twin for manufacturing.

304 6.2.3 Functional entity of data collection and device control entity

305 6.2.3.1 Data collecting FE in data collection sub-entity

306 Data collecting FE provides data collection functionality from observable manufacturing element.

307 6.2.3.2 Data pre-processing FE in data collection sub-entity

308 Data pre-processing FE provides pre-processing functionality for collected data, for example filtering 309 and aggregation.

310 6.2.3.3 Controlling FE in device control sub-entity

311 Controlling FE provides functionality of controlling observable manufacturing element by the request 312 from Digital Twin system entity.

313 6.2.3.4 Actuation FE in device control sub-entity

314 Actuation FE provides functionality of actuating observable manufacturing element by the request from 315 Digital Twin system entity, similarly with controlling FE.

316 6.2.3.5 Identification FE in data collection sub-entity and device control sub-entity

317 Identification FE provides functionality of identifying observable manufacturing element and its data to 318 be collected and controlled uniquely and unambiguously.

319 6.2.4 Functional entity in Digital Twin system entity

320 6.2.4.1 Functional entity in operation and management sub-system entity

321 6.2.4.1.1 Synchronization FE

322 Synchronization FE provides functionality of synchronizing the status of the visualized digital entity 323 with the status of the observable manufacturing element, or vice versa.

324 6.2.4.1.2 Presentation FE

325 Presentation FE provides functionality of presenting observable manufacturing element as digital entity 326 in conjunction with digital modeling FE.

327 6.2.4.1.3 Digital modeling FE

328 Digital modeling FE provides functionality of interpreting information of observable manufacturing 329 element to understand its physical properties, status, etc.

330 6.2.4.1.4 O&M support FE

331 O&M support FE provides functionalities of operating and managing Digital Twin and Digital Twin 332 system entities.

333 6.2.4.2 Functional entity in application and service sub-system entity

334 6.2.4.2.1 Simulation FE

335 Simulation FE provides functionalities of simulation.

336 6.2.4.2.2 Analytic service FE

337 Analytic service FE provides functionality of analysing data collected from observable manufacturing 338 element and the result of simulation.

339 6.2.4.2.3 Reporting FE

340 Reporting FE provides functionality of generating report of production result, analysis on simulation, 341 etc.

342 6.2.4.2.4 Application support FE

343 Application support FE provides functionality of hosting platform for implementing predictive and 344 reactive, open and closed loop applications.

345 6.2.4.3 Functional entity in resource access and interchange sub-system entity

346 6.2.4.3.1 Interoperability support FE

347 Interoperability support FE provides functionality of interworking with other Digital Twin system 348 entity in conjunction with peer interface FE.

349 6.2.4.3.2 Access control FE

350 Access control FE provides functionality of controlling access of Digital Twin user entity to observable 351 manufacturing element in conjunction with security support FE.

352 6.2.4.3.3 Plug & play support FE

353 Plug & play support FE provides functionality of dynamic involvement of observable manufacturing 354 element, i.e., joining and leaving Digital Twin for manufacturing in run time, in conjunction with O&M 355 support FE.

356 6.2.4.3.4 Peer interface FE

357 Peer interface FE provides functionality of interfacing to other Digital Twin entities in conjunction with 358 interoperability support FE.

359 6.2.5 Functional entity in Digital Twin user entity

360 6.2.5.1 User interface FE

361 User interface FE provides Digital Twin user entity with functionality of interfacing to Digital Twin 362 system entity.

363 6.2.6 Functional entity in cross-system entity

364 6.2.6.1 Information exchange FE

365 Information exchange FE provides functionality of exchanging information among entities of Digital 366 Twin for manufacturing by appropriate networking protocols.

367 6.2.6.2 Data assurance FE

368 Data assurance FE provides accuracy and integrity of data in conjunction with security support FE.

369 6.2.6.3 Security support FE

370 Security support FE provides functionality of securing Digital Twin for manufacturing including 371 authentication, authorization, confidentiality, integrity, etc.

372 6.3 Networking view

373 6.3.1 Networking reference architecture

374 Networking reference architecture describes communication network which are involved in Digital 375 Twin for manufacturing.

376 Figure 6 shows three principal communication networks in terms of domain-entity mixture reference 377 model (see 5.3) in Digital Twin for manufacturing. Main role of communication network provides 378 means to exchange information between entities across the different domains.

379 However, data collection and device control entity is physically attached or integrated into observable 380 manufacturing element, therefore communication network between these two entities is not 381 considered in this document.

382

383 Figure 6 – Networking view of Digital Twin reference architecture for manufacturing

384 6.3.2 Transmission network

385 Transmission network connects data collection and device control entity to Digital Twin system entity, 386 i.e., operation and management sub-system entity, application and service sub-system entity, and 387 resource access and interchange sub-system entity. Through this network, data collection sub-entity 388 transmits collected data from observable manufacturing element to the target entities of Digital Twin 389 system entity. In addition, control information for observable manufacturing element is delivered to 390 device control sub-entity from entities of Digital Twin system entity.

391 Typical examples of transmission network can be wired communication such as LAN, and wireless 392 communication such as WLAN and mobile (cellular) network, which generally adopt IP-based 393 communication protocols regardless of communication type.

394 Information exchange between data collection and device control entity, and Digital Twin system entity 395 over transmission network is supported by appropriate communication protocol. For example, 396 MTConnect and OPC-UA can be used as information exchange protocol. ISO 23247-4 defines 397 information exchange over transmission network. However, if data collection and device control entity, 398 and Digital Twin system entity are implemented in one system, it might not be necessary to have 399 transmission network.

400 6.3.3 Service network (optional)

401 Service network connects operation and management sub-system entity, application and service sub- 402 system entity, and resource access and interchange sub-system entity with each other, which are 403 typically wired networks running IP-based protocols.

404 Service network can include both typical Internet and also (private) Intranet in case that Digital Twin 405 system entity is implemented in a single private domain, even a single system. In this case, a service 406 network is not needed and dedicated connections can be applied to a single private domain connecting 407 different entities as well as internal communication within a single system. ISO 23247-4 defines 408 information exchange over service network.

409 6.3.4 User network

410 User network connects Digital Twin user entity with Digital Twin system entity. In case that Digital 411 Twin user entity is one of MES, ERP, other manufacturing management system, and even other Digital 412 Twin system entity, this type of Digital Twin user entity is connected to resource access and interchange 413 sub-system entity over user network.

414 User network is typically based on Internet and uses IP. Such networks can use any of the technologies 415 commonly used to exchange information. ISO 23247-4 defines information exchange over user network.

416 Bibliography

417 [1] The Structure of the Administration Shell: TRILATERAL PERSPECTIVES from France, Italy and 418 Germany, International Paper, Platform Industrie 4.0, 2018

419 [2] IEC 62264-1 (2013), Enterprise-control system integration — Part 1: Models and terminology

420 [3] ISO 23247-4, Automation systems and integration — Digital Twin framework for manufacturing 421 — Part 4: Information exchange

422

423

ISO/TC 184/SC 4/WG 15 Digital manufacturing

Email of convenor: [email protected] Convenorship: ANSI (United States)

Text for ISO DIS 23247-3 Ballot r2 Document type: Committee draft

Date of document: 2019-12-09

Expected action: INFO

Background: Latest draft of DIS text.

ISO DIS 23247-3:2019(E)

ISO TC 184/SC 4/WG 15

Secretariat: ANSI

Automation systems and integration — Digital Twin framework for manufacturing — Part 3: Digital representation of manufacturing elements

DIS stage

To help you, this guide on writing standards was produced by the ISO/TMB and is available at https://www.iso.org/iso/how-to-write-standards.pdf

A model manuscript of a draft International Standard (known as “The Rice Model”) is available at https://www.iso.org/iso/model_document-rice_model.pdf

ISO DIS 23247-3:2019(E)

1 © ISO 2019

2 All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this 3 publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, 4 including photocopying, or posting on the internet or an intranet, without prior written permission. Permission 5 can be requested from either ISO at the address below or ISO’s member body in the country of the requester.

6 ISO copyright office 7 CP 401 • Ch. de Blandonnet 8 8 CH-1214 Vernier, Geneva 9 Phone: +41 22 749 01 11 10 Fax: +41 22 749 09 47 11 Email: [email protected] 12 Website: www.iso.org

13 Published in Switzerland

14 Contents

16 Foreword ...... iv 17 Introduction...... v 18 1 Scope ...... 1 19 2 Normative references ...... 1 20 3 Terms and definitions ...... 2 21 4 Digital representations of observable manufacturing elements ...... 3 22 5 Information attributes of observable manufacturing elements...... 4 23 5.1 General ...... 4 24 5.2 Personnel information...... 5 25 5.3 Equipment information ...... 6 26 5.4 Material information ...... 7 27 5.5 Process information ...... 8 28 5.6 Facility information ...... 9 29 5.7 Environment information...... 10 30 5.8 Product information ...... 11 31 5.9 Supporting document information ...... 12 32 Annex A (informative) Existing technologies for representing manufacturing elements ...... 14 33 Annex B (informative) Example of information attribute ...... 16 34 Bibliography ...... 18 35

36 Foreword

37 ISO (the International Organization for Standardization) is a worldwide federation of national 38 standards bodies (ISO member bodies). The work of preparing International Standards is normally 39 carried out through ISO technical committees. Each member body interested in a subject for which a 40 technical committee has been established has the right to be represented on that committee. 41 International organizations, governmental and non-governmental, in liaison with ISO, also take part in 42 the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all 43 matters of electrotechnical standardization.

44 The procedures used to develop this document and those intended for its further maintenance are 45 described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the 46 different types of ISO documents should be noted. This document was drafted in accordance with the 47 editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).

48 Attention is drawn to the possibility that some of the elements of this document may be the subject of 49 patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of 50 any patent rights identified during the development of the document will be in the Introduction and/or 51 on the ISO list of patent declarations received (see www.iso.org/patents).

52 Any trade name used in this document is information given for the convenience of users and does not 53 constitute an endorsement.

54 For an explanation on the voluntary nature of standards, the meaning of ISO specific terms and 55 expressions related to conformity assessment, as well as information about ISO's adherence to the 56 World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following 57 URL: www.iso.org/iso/foreword.html.

58 This document was prepared by Technical Committee ISO/TC 184, Automation systems and integration, 59 Subcommittee SC 4, Industrial Data.

60 A list of all parts in the ISO 23247 series can be found on the ISO website.

61 Any feedback or questions on this document should be directed to the user’s national standards body. A 62 complete listing of these bodies can be found at www.iso.org/members.html.

63 Introduction

64 ISO 23247 series defines a framework to support the creation of Digital Twins of observable 65 manufacturing elements including personnel, equipment, materials, processes, facilities, environment, 66 products, and supporting documents.

67 The scope of the four parts of this series are defined below:

68 - Part 1: Overview and general principles

69 Provides an overview of Digital Twin for manufacturing, describes general principles, and 70 provides requirements and guidance for developing a Digital Twin framework for 71 manufacturing;

72 - Part 2: Reference architecture

73 Provides a reference architecture goals and objectives, reference model, and reference 74 architectural views for the Digital Twin framework for manufacturing;

75 - Part 3: Digital representation of manufacturing elements

76 Identifies manufacturing elements of the Digital Twin framework for manufacturing that shall 77 be represented in digital models;

78 - Part 4: Information exchange

79 Identifies technical requirements for information synchronization and information exchange 80 between entities of the reference model of the Digital Twin framework for manufacturing.

81 The types of manufacturing that can be supported by an implementation of the framework will depend 82 on the technologies selected to implement its functional elements.

83 Use cases for the Digital Twin framework for manufacturing will be detailed in technical reports 84 attached to this series of standards.

ISO DIS 23247-3:2019(E)

85 Automation systems and integration — Digital Twin framework 86 for manufacturing — Part 3: Digital representation of 87 manufacturing elements

88 1 Scope

89 This part of ISO 23247 identifies the observable manufacturing elements of the Digital Twin framework 90 for manufacturing that shall be represented in digital models.

91 ISO 23247 series defines a framework to support the creation of Digital Twins of observable 92 manufacturing elements including personnel, equipment, materials, processes, facilities, environment, 93 products, and supporting documents.

94 The following are within the scope of this part of ISO 23247;

95 - Digital representations of observable manufacturing elements;

96 - Information for digital representations of observable manufacturing elements.

97 The following are described in other parts of ISO 23247;

98 - overview and general principles (Part 1);

99 - reference architecture of the Digital Twin framework for manufacturing (Part 2);

100 - Information exchange of the Digital Twin framework for manufacturing (Part 4);

101 - use cases of the Digital Twin framework for manufacturing to be detailed in technical reports.

102 The following are outside of the scope of ISO 23247;

103 - selection of the implementation methods and technologies for a Digital Twin for manufacturing;

104 - selection of the communication protocols for a Digital Twin for manufacturing;

105 - selection of the manufacturing devices and other resources to be represented by a Digital Twin;

106 - selection of the manufacturing processes to be represented by a Digital Twin;

107 - selection of the manufacturing products to be represented by a Digital Twin;

108 - design and process planning, and other non-manufacturing stages of the product lifecycle.

109 2 Normative references

110 The following documents are referred to in the text in such a way that some or all of their content 111 constitutes requirements of this document. For dated references, only the edition cited applies. For 112 undated references, the latest edition of the referenced document (including any amendments) applies.

113 ISO 23247-1, Automation systems and integration — Digital Twin framework for manufacturing — Part 114 1: Overview and general principles

115 3 Terms and definitions

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

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

118 — ISO Online browsing platform: available at https://www.iso.org/obp

119 — IEC Electropedia: available at http://www.electropedia.org/

120

121 4 Digital representations of observable manufacturing elements

122 One of the Digital Twin functions is digital representations of observable manufacturing elements. 123 Figure 1 shows the observable manufacturing elements managed by the Digital Twin Entity in the 124 Digital Twin framework for manufacturing reference architecture. 125 Digital representations of observable manufacturing elements shall consider both static and dynamic 126 information. Information that does not change during manufacturing is classified as static information, 127 whereas information that changes during manufacturing is classified as dynamic information. For 128 example, the serial number of a machine is static. However, the amount or the shape of material during 129 manufacturing processes can be dynamic. 130 For Digital Twin modelling of observable manufacturing elements, the information associated with 131 observable manufacturing elements shall be managed by the Digital Twin Entity. 132

133

134 Figure 1 – Digital representations of observable manufacturing elements in reference 135 architecture

136

137 5 Information attributes of observable manufacturing elements

138 5.1 General

139 As explained in Clause 4, a digital representation of an observable manufacturing element shall consider 140 both static and dynamic features of information. In this document, these features are defined as 141 information attributes. 142 The information attributes described in Figure 2 are examples to illustrate the kinds of information that 143 should be represented for a Digital Twin. Many existing standards such as IEC 62264-2 and ISO 10303 144 contain detailed information models for these attributes. An implementation of the framework should 145 select the information models most appropriate for its use case. Static information attribute includes 146 identification, characteristics, schedule, relationship with other manufacturing elements, and 147 description. Dynamic information attribute includes status, location, report, relationship with other 148 manufacturing elements, and description.

149

150

151 Figure 2– Information attributes for observable manufacturing elements

152

153 5.2 Personnel information

154 Personnel in manufacturing generally include those employees who are engaged directly or indirectly 155 in manufacturing processes as described in ISO 23247-1. Static information of the personnel shall 156 include identification, characteristics, schedule and relationship as shown in Table 1.

157 Table 1 – Static information of personnel

Attribute Description Examples Identification Information to identify personnel  employee number Characteristics Classification of personnel  skill  license  certification level  technician / engineer  senior / principal Schedule Working schedule for personnel  working schedule Relationship Static relationship for personnel and other  Person #1 is the boss of manufacturing elements Person #2 Description Additional information and explanation  general information about about the static information of personnel an employee 158

159 The values of dynamic information of personnel are changed during manufacturing processes. Dynamic 160 information of personnel shall include status, location, report and relationship as shown in Table 2.

161 Table 2 – Dynamic information of personnel

Attribute Description Examples Status Status of personnel  working / paused Location Location information (geographical /  Person #1: WorkUnit #3 relative location) and 50 cm away from Robot #2 Report Work report related to personnel  May 14th 2019: Some hours of work Relationship Dynamic relationship for personnel and  Person #1 and Person #2 other manufacturing elements are working in the WorkUnit #3  Person #1 and Person #2 are 70 cm away from Machine #2. Description Additional information and explanation  dynamic information of about the dynamic information of personnel personnel changing during manufacturing processes

162 NOTE 1 Some working place must have the required minimum personnel for safety reasons. 163 NOTE 2 Various kinds of devices are available to detect the identifier, location, motion, and 164 image of observable manufacturing elements. 165 NOTE 3 Performance may be calculated and represented for manufacturing elements.

166 5.3 Equipment information

167 Equipment is a physical element that carries out an operation that is directly or indirectly involved in 168 manufacturing processes as described in ISO 23247-1. Static information of equipment are shown in 169 Table 3.

170 Table 3 –Static information of equipment

Attribute Description Examples Identification Information to identify equipment  serial number Characteristics Classification of equipment  milling  turning  grinding  pressing Schedule Working schedule for equipment  working schedule  maintenance schedule Relationship Static relationship for equipment and other  Machine #1 operates with manufacturing elements Material #2. Description Additional information and explanation  general information about about the static information of equipment equipment 171 172 The values of dynamic information of equipment are changed during manufacturing processes. 173 Dynamic information of equipment are shown in Table 4.

174 Table 4 – Dynamic information of equipment

Attribute Description Examples Status Status of equipment  on / off  working / breakdown  performance (energy usage, output)  temperature, pressure, sound / noise Location Location information (geographical /  Machine #2: WorkUnit #2 relative location) in Room #3 Report Work report related to equipment  May 14th, 2019 9 AM to 6 PM: Regular Maintenance  May 14th, 2019 11 AM: Machine #1 reports high temperature. Relationship Dynamic relationship for equipment and  Machine #1 is operated by other manufacturing elements Person #2 in WorkCenter #5. Description Additional information and explanation  dynamic information of about the dynamic information of equipment changing equipment during manufacturing processes 175

176 5.4 Material information

177 Material is physical matter that becomes a part or the whole of a product i.e., metal block, glass panel, 178 etc., or is used to aid manufacturing processes, i.e., cleaning fluid, coolant, etc. as described in ISO 179 23247-1. Static information of material shall include identification, characteristics, schedule and 180 relationship as shown in Table 5.

181 Table 5 – Static information of material

Attribute Description Examples Identification Information to identify material  bar code  RFID tag Characteristics Classification of material  handle with care / fragile  toxic  liquid / solid / gas  plastic / steel / rubber / powder Schedule Working schedule for material  input schedule  purchase schedule  inbound / outbound schedule Relationship Static relationship for material and other  Material #1 shall be manufacturing elements managed by person with Skill #2. Description Additional information and explanation  general information about about the static information of material material 182 183 The values of dynamic information of material are changed during manufacturing processes. Dynamic 184 information of material shall include status, location, report and relationship as shown in Table 6.

185 Table 6 – Dynamic information of material

Attribute Description Examples Status Status of material  Tested  Availability  liquid / solid / gas Location Location information (geographical /  Material #1: Shelf #3 in relative location) Warehouse #2 Report Work report related to material  May 14th, 2019: 8 kg of Material #2 is used in WorkUnit #2 Relationship Dynamic relationship for material and other  Material #1 is operated by manufacturing elements a person with Skill #2 in WorkCenter #5. Description Additional information and explanation  dynamic information of about the dynamic information of material material changing during manufacturing processes 186

187 5.5 Process information

188 A process is an observable physical operation within manufacturing as described in ISO 23247-1. Static 189 information of the process shall include identification, characteristics, schedule and relationship as 190 shown in Table 7.

191 Table 7 – Static information of process

Attribute Description Examples Identification Information to identify process  process identifier Characteristics Classification of process  production / maintenance / quality test / inventory  milling / drilling  additive Schedule Working schedule for process  periodic, one time, limit, duration Relationship Static relationship for process and other  ManufacturingProcess #1 manufacturing elements is managed by a person with Skill #3. Description Additional information and explanation  general information about about the static information of process process 192 193 The values of dynamic information of process are changed during manufacturing processes. Dynamic 194 information of process shall include status, location, report and relationship as shown in Table 8.

195 Table 8 – Dynamic information of process

Attribute Description Examples Status Status of process  planned  in-process  finished / incomplete Location Location information (geographical /  Process #1: Machine #2 in relative location) Room #3 Report Work report related to the process  May 14th, 2019: Machine #2 completed MillingOperation #5. Relationship Dynamic relationship for process and other  MillingOperation #1 is manufacturing elements operated by Person #3 with Skill #2 in WorkCenter #3. Description Additional information and explanation  dynamic information of about the dynamic information of process process changing during manufacturing processes 196

197 5.6 Facility information

198 Facility is infrastructure that is related to or affects manufacturing as described in ISO 23247-1. Static 199 information of the facility shall include identification, characteristics, schedule and relationship as 200 shown in Table 9.

201 Table 9 – Static information of facility

Attribute Description Examples Identification Information to identify facility including  serial number environment, energy, etc.  asset number Characteristics Classification of facility  air-conditioning / ventilating Schedule Working schedule for facility  periodic, one time, limit, duration Relationship Static relationship for facility and other  Facility #1 is controlled by manufacturing elements a person with Skill #3 when the temperature exceeds the limits. Description Additional information and explanation  general information about about the static information of facility facility

202 NOTE Some facilities do not have identification, such as doors.

203 The values of dynamic information of facility are changed during manufacturing processes. Dynamic 204 information of facility shall include status, location, report and relationship as shown in Table 10.

205 Table 10 – Dynamic information of facility

Attribute Description Examples Status Status of facility  Normal / abnormal Location Location information (geographical /  Facility #2: Room #3 relative location) Report Work report related to facility  May 14th, 2019 9 AM: Facility #2 reports alarm of high temperature.  May 14th, 2019 10 AM: Person #3 turned on the #Facility 3(air conditioner). Relationship Dynamic relationship for facility and other  Machine #3 is using manufacturing elements Facility (air conditioner) #2 for MillingOperation #3 in Room #2 to be kept at 20 °C. Description Additional information and explanation  dynamic information of about the dynamic information of facility facility changing during manufacturing processes 206

207 5.7 Environment information

208 Environment is necessary condition that shall be supplied by facilities for the correct execution of a 209 manufacturing process as described in ISO 23247-1. Static information of the environment shall include 210 identification, characteristics, schedule and relationship as shown in Table 11.

211 Table 11 – Static information of environment

Attribute Description Examples Identification Information to identify environment  Combination of time, including time and location. sensor ID and sensor value  Combination of time and energy consumption (kWh) Characteristics Classification of environment  temperature / humidity / illuminance Schedule Working schedule for environment  periodic, one time, limit, duration Relationship Static relationship for environment and  Room #2 should be kept at other manufacturing elements 20 °C while manufacturing is being performed. Description Additional information and explanation  general information about about the static information of environment environment

212 NOTE Some environment does not have identification, such as temperature, humidity, and 213 illumination. Environment data has the meaning associated with the time and location.

214 The values of dynamic information of environment are changed during manufacturing processes. 215 Dynamic information of environment shall include status, location, report and relationship as shown in 216 Table 12.

217 Table 12 – Dynamic information of environment

Attribute Description Examples Status Status of environment  Normal / abnormal Location Location information (geographical /  May 14th, 2019 10 AM: relative location) temperature #2 is 25 °C in Room #3. Report Report related to environment  May 14th, 2019 9 AM: Room #2 reports alarm of high temperature that the temperature #2 is 30 °C. Relationship Dynamic relationship for environment and  May 14th, 2019 10 AM: other manufacturing elements Person #3 turned on the Facility #3(air conditioner) to lower Temperature #2 to 20 °C. Description Additional information and explanation  dynamic information of about the dynamic information of environment changing environment during manufacturing processes 218

219 5.8 Product information

220 Product is a desired output or by-product of manufacturing process as described in ISO 23247-1. Static 221 information of the product shall include identification, characteristics, schedule and relationship as 222 shown in Table 13.

223 Table 13 – Static information of product

Attribute Description Examples Identification Information to identify product  product model  serial number Characteristics Classification of product  dimensions  colour Schedule Working schedule for product  periodic, one time, limit, duration Relationship Static relationship for product and other  Product #1 is produced by manufacturing elements Machine #3. Description Additional information and explanation  general information about about the static information of product product 224 225 The values of dynamic information of product are changed during manufacturing processes. Dynamic 226 information of product shall include status, location, report and relationship as shown in Table 14.

227 Table 14 – Dynamic information of product

Attribute Description Examples Status Status of product  in-process  300 of 312 fasteners presently installed  finished  inventory Location Location information (geographical /  Product #2 is in relative location) Warehouse #3 Report Work report related to product  May 14th, 2019 9 AM: Product #2 has passed QualityTest #5.  May 14th, 2019 10 AM: Product #2 has moved to Warehouse #3. Relationship Dynamic relationship for product and other  Product #3 is in process by manufacturing elements Machine #2 for MillingOperation #3. Description Additional information and explanation  dynamic information of about the dynamic information of product product changing during manufacturing processes 228

229 5.9 Supporting document information

230 A supporting document is any form of artefact that helps the applications of Digital Twin for 231 manufacturing as described in ISO 23247-1. Static information of the supporting document shall include 232 identification, characteristics, schedule and relationship as shown in Table 15.

233 Table 15 – Static information of supporting document

Attribute Description Examples Identification Information to identify supporting  document type document  document number Characteristics Classification of supporting document  requirement  plan  model  specification  configuration Schedule Working schedule for supporting document  periodic, one time, limit, duration Relationship Static relationship for supporting document  May 12th, 2019 10 AM: and other manufacturing elements Person #3 produced Document #2. Description Additional information and explanation  general information about about the static information of supporting supporting document document 234 235 The values of dynamic information of supporting document are changed during manufacturing 236 processes. Dynamic information of supporting document shall include status, location, report and 237 relationship as shown in Table 16.

238 Table 16 – Dynamic information of supporting document

Attribute Description Examples Status Status of supporting document  planned  in-process  finished / incomplete Location Location information (geographical /  Document #2 is stored in relative location) Directory #3 Report Work report related to supporting  May 14th, 2019 9 AM: document Person #2 has stored Document #2 in the Directory #5.  May 14th, 2019 10 AM: Person #3 has moved Document #2 to Directory #3. Relationship Dynamic relationship for supporting  Person #3 is planning to document and other manufacturing produce Document #3 for elements DrillingOperation #5 by May 31th, 2019. Description Additional information and explanation  dynamic information of

about the dynamic information of supporting document supporting document changing during manufacturing processes 239

240 Annex A 241 (informative) 242 243 Existing technologies for representing manufacturing elements

244 Existing standards and specifications, including ISO 10303 series, IEC 62264 series, IEC 62714 series, 245 ISO 13399 series, eCl@ss, asset administration shell, IEC 62541 (OPC UA), MTConnect, QIF, and RDF can 246 be used to represent manufacturing elements.

247 ISO 10303, known as Standard for the Exchange of Product Model Data (STEP), series define the 248 computer-interpretable representation of product information and the exchange of product and 249 process data [2]. The objective of ISO 10303 series is to provide a neutral mechanism capable of 250 describing products and their manufacturing processes throughout their life cycle. This mechanism is 251 appropriate not only for neutral file exchange, but also as a basis for implementing and sharing product 252 databases, and as a basis for archiving. STEP series are used for data exchange among CAD/CAM 253 systems and among CAD/CAM and manufacturing systems. The information models for ISO 10303 254 series are described using EXPRESS schemas.

255 ISO 10303-238 specifies an application protocol (AP) for numerically controlled machining and 256 associated processes [2]. ISO 10303-238 includes the information requirements defined by the ISO 257 14649 series data model for numerical controllers, augmented with product geometry, geometric 258 dimensioning and tolerancing, and product data management information.

259 ISO 10303-239 specifies the application protocol for product life cycle support. The scope of ISO 10303- 260 239 includes information for defining and maintaining a complex product, and information required for 261 life configuration change management of a product and its support solution [3]. Also, it includes 262 representation of product assemblies, product through life, specification and planning of activities for a 263 product, the representations of the activity history of a product and product history.

264 ISO 10303-242 specifies the application protocol for managed model-based 3D engineering [4]. The 265 scope of ISO 10303-242 includes products of automotive, aerospace and other mechanical 266 manufacturers and of their suppliers, engineering and product data, product data management, process 267 planning, mechanical design, kinematics, geometric definition and tolerancing and composite design. 268 The ISO 10303 series can be used to define information models and 3D engineering for manufacturing 269 elements.

270 IEC 62264 series are based on ISA-95 [5] [6]. IEC 62264 series and provide consistent terminology that 271 is a foundation for supplier and manufacturer communications. IEC 62264 series also provide 272 consistent information models and object models to integrate control systems with enterprise systems 273 that improve communications among all manufacturing elements involved. B2MML is an XML 274 implementation of the IEC 62264 series, Enterprise-Control System Integration [7]. B2MML consists of 275 a set of XML schemas written using the World Wide Web Consortium's XML Schema language (XSD) 276 that implement the data models in the IEC 62264 series.

277 IEC 62714 series, known as Automation Markup Language (AML), describe the data exchange format 278 using XML schema [8]. AML has been developed to support the data exchange and interconnect in 279 heterogeneous engineering tools in their different disciplines. IEC 62714 series can be used to 280 represent data exchange format among manufacturing elements.

281 ISO 13399 series describe the computer-interpretable representation and exchange of industrial 282 product data about cutting tools and tool holders [9]. ISO 13399 series defines the reference dictionary 283 for cutting items, tool items, adaptive items, etc. ISO 13399 series can be used to represent and 284 exchange data for cutting tools.

285 The eCl@ss (classification and production description) defines tens of thousands of product classes and 286 unique properties including procurement, storage, production and distribution activities [10]. The 287 eCl@ss can be used to define classes and properties for manufacturing elements conformant to IEC 288 61360 and ISO 13854-42.

289 The asset administration shell is part of the I4.0 component as introduced in IEC PAS 63088 [11]. It 290 provides a technology neutral information model and several serializations and mapping. The asset 291 administration shell is one possible concept and specification that can be used to implement twins. 292 Serializations and mappings are provided for XML, JSON, RDF, AutomationML and OPC UA. One of its 293 key features is the separation of the digital representation into a set of sub models. Each sub model 294 represents a specific aspect of the asset that the twin is representing.

295 IEC 62541 (OPC UA) represents the international standard of OPC UA, which is for vertical and 296 horizontal communication in manufacturing and automation, providing semantic interoperability for 297 the world of connected systems [12]. It has been designed for scalability and supports a wide range of 298 application domains, ranging from field level (e.g. devices for measurement or identification, PLCs), to 299 enterprise management support.

300 New information models, based on the OPC UA data model, can be created and eventually derived from 301 OPC UA base information models [12]. The specifications of such Information Models, called Companion 302 Specifications, are regarded as “Industry standard models” because they typically address a dedicated 303 industry problem. The synergy of the OPC UA infrastructure to exchange such industry information 304 models enables interoperability at the semantic level.

305 The MTConnect standard provides a semantic vocabulary for manufacturing equipment to provide 306 structured, contextualized data with no proprietary format [13]. With uniform data by MTConnect 307 standard, developers and integrators can focus on useful, productive manufacturing applications rather 308 than translation. MTConnect data offer more efficient operations, improved production optimization, 309 and increased productivity.

310 QIF (Quality Information Framework) is standardized as an American National Standard supporting 311 Digital Thread concepts in engineering applications ranging from product design through 312 manufacturing to quality inspection [14]. The XML-based QIF standard contains a library of XML 313 schema ensuring both data integrity and data interoperability in Model Based Enterprise 314 implementation.

315 RDF is a standard model for data interchange on the Web [15]. RDF has features that facilitate data 316 merging even if the underlying schemas differ, and it specifically supports the evolution of schemas 317 over time without requiring all the data consumers to be changed.

318 Each technology has its characteristics for digital representation of manufacturing elements. Digital 319 Twin developers should carefully consider which should be used for the target applications.

320 Annex B 321 (informative) 322 323 Example of information attribute

324 Figure B.1 shows a product information attribute.

325

326 Figure B.1 Product information attribute

327 An example of the product information attribute for Figure B.1 is as follows:

328 329 330 331 DTM-Product-0001 332 333 white 334 335 2019-12-03 336 337 Product #1 is produced by Machine #3 338 339 340 341 342 status 343 in-process 344 345 346 relative 347 Warehouse#3 348 349 350 WorkReport 351 05/14/2019 9AM: Product #2 has passed QualityTest #5. 352 353 354 equipment 355 Product #3 is in process by Machine #2 for MillingOperation 356 #3. 357 358 359

360 Bibliography

361 [1] ISO 23247-2, Automation systems and integration – Digital Twin framework for manufacturing – 362 Part 2: Reference architecture

363 [2] ISO 10303-238, Industrial automation systems and integration — Product data representation 364 and exchange — Part 238: Application protocol: Model based integrated manufacturing

365 [3] ISO 10303-239, Industrial automation systems and integration — Product data representation 366 and exchange — Part 239: Application protocol: Product life cycle support

367 [4] ISO 10303-242, Industrial automation systems and integration — Product data representation 368 and exchange — Part 242: Application protocol: Managed model-based 3D engineering

369 [5] IEC 62264-1, Enterprise-control system integration – Part 1: Models and terminology

370 [6] IEC 62264-2, Enterprise-control system integration – Part 2: Objects and attributes for enterprise- 371 control system integration

372 [7] B2MML, http://www.mesa.org/en/B2MML.asp

373 [8] IEC 62714-1, Engineering data exchange format for use in industrial automation systems 374 engineering — Automation Markup Language — Part 1: Architecture and general requirements

375 [9] ISO 13399-60, Cutting tool data representation and exchange — Part 60: Reference dictionary for 376 connection systems

377 [10] eCl@ss, Available at: https://www.eclass.eu/en/standard.html

378 [11] IEC PAS 63088:2017, Smart manufacturing - Reference architecture model industry 4.0 (RAMI4.0)

379 [12] OPC UA, https://opcfoundation.org/

380 [13] MTConnect, Available at: https://www.mtconnect.org/

381 [14] QIF, Available at: https://qifstandards.org/about-qif/

382 [15] RDF, Available at: https://www.w3.org/RDF/

ISO/TC 184/SC 4/WG 15 Digital manufacturing

Email of convenor: [email protected] Convenorship: ANSI (United States)

Text for ISO DIS 23247-4 Ballot r2 Document type: Committee draft

Date of document: 2019-12-09

Expected action: INFO

Background: Latest draft of DIS text.

ISO DIS 23247-4:2019(E)

ISO TC 184/SC 4/WG 15

Secretariat: ANSI

Automation systems and integration – Digital Twin framework for manufacturing– Part 4: Information exchange

Filename: ISO DIS 23247-4 text ver0.2-Dec2019.docx DIS stage

ISO DIS 23247-4:2019(E)

1 © ISO 2019

6 ISO copyright office 7 CP 401 • Ch. de Blandonnet 8 8 CH-1214 Vernier, Geneva 9 Phone: +41 22 749 01 11 10 Fax: +41 22 749 09 47 11 Email: [email protected] 12 Website: www.iso.org

13 Published in Switzerland

14 Contents

15 Foreword ...... v 16 Introduction...... vi 17 1 Scope ...... 1 18 2 Normative references ...... 2 19 3 Terms and definitions ...... 2 20 4 Overview ...... 3 21 5 Requirements for information exchange A (IE-A) ...... 4 22 5.1 Overview ...... 4 23 5.2 Visualization ...... 4 24 5.3 Standardized method for data exchange ...... 4 25 5.4 Transaction method ...... 4 26 5.5 Security ...... 5 27 6 Requirements for information exchange Bs (IE-B1, IE-B2, IE-B3) ...... 5 28 6.1 Overview ...... 5 29 6.2 Digital Twin services ...... 5 30 6.3 Presentation ...... 6 31 6.4 Implementation dependent ...... 6 32 7 Requirements for information exchange C (IE-C) ...... 7 33 7.1 Overview ...... 7 34 7.2 Connectivity ...... 7 35 7.3 Standardized method for data exchange ...... 7 36 7.4 Identification ...... 8 37 7.5 Digital model ...... 8 38 7.6 Applying manufacturing information ...... 8 39 7.7 Synchronization ...... 8 40 7.8 Operation on Information exchange ...... 8 41 7.9 Transaction method ...... 9 42 7.10 Support of near real-time communication ...... 9 43 7.11 Security ...... 9 44 8 Requirements for information exchange D (IE-D) ...... 11 45 8.1 Overview ...... 11 46 8.2 Support of local network...... 11 47 8.3 Support of adaptation ...... 11 48 Annex A (informative) Technical discussion - Implementation options for Digital Twin 49 framework for manufacturing ...... 12 50 A.1 Acronyms of protocols ...... 12 51 A.2 Implementation options for four IEs ...... 14 52 A.2.1 Implementation options for IE-A ...... 14 53 A.2.2 Implementation options for IE-Bs ...... 15 54 A.2.3 Implementation options for IE-C ...... 16 55 A.2.4 Implementation options for IE-D ...... 17 56 A.3 Mapping of Digital Twin with source data ...... 18 57 A.4 Structure of multiple DCDCE and multiple OME ...... 19 58 Bibliography ...... 21

60 Foreword

61 ISO (the International Organization for Standardization) is a worldwide federation of national 62 standards bodies (ISO member bodies). The work of preparing International Standards is normally 63 carried out through ISO technical committees. Each member body interested in a subject for which a 64 technical committee has been established has the right to be represented on that committee. 65 International organizations, governmental and non-governmental, in liaison with ISO, also take part in 66 the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all 67 matters of electrotechnical standardization.

68 The procedures used to develop this document and those intended for its further maintenance are 69 described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the 70 different types of ISO documents should be noted. This document was drafted in accordance with the 71 editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).

72 Attention is drawn to the possibility that some of the elements of this document may be the subject of 73 patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of 74 any patent rights identified during the development of the document will be in the Introduction and/or 75 on the ISO list of patent declarations received (see www.iso.org/patents).

76 Any trade name used in this document is information given for the convenience of users and does not 77 constitute an endorsement.

78 For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and 79 expressions related to conformity assessment, as well as information about ISO's adherence to the 80 World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see 81 www.iso.org/iso/foreword.html.

82 This document was prepared by Technical Committee ISO/TC 184, Industrial automation systems and 83 integration, Subcommittee SC 4 Industrial data.

84 A list of all parts in the ISO 23247 series can be found on the ISO website.

85 Any feedback or questions on this document should be directed to the user’s national standards body. A 86 complete listing of these bodies can be found at www.iso.org/members.html.

88 Introduction

89 90 ISO 23247 series defines a framework to support the creation of Digital Twins of observable 91 manufacturing elements including personnel, equipment, materials, processes, facilities, environment, 92 and products.

93 The scope of the four parts of this series are defined below:

94 - Part 1: Overview and general principles

95 Provides an overview of Digital Twin for manufacturing, describes general principles, and 96 provides requirements and guidance for developing the Digital Twin framework for 97 manufacturing;

98 - Part 2: Reference architecture

99 Provides a reference architecture goals and objectives, reference model, and reference 100 architectural views for the Digital Twin framework for manufacturing

101 - Part 3: Digital representation of manufacturing elements

102 Identifies the observable manufacturing elements of the Digital Twin framework for 103 manufacturing that shall be represented in digital models;

104 - Part 4: Information exchange

105 Identifies technical requirements for information synchronization and information exchange between 106 entities of the reference model of the Digital Twin framework for manufacturing. The types of 107 manufacturing that can be supported by an implementation of the framework will depend on the 108 technologies selected to implement its functional elements.

109 Use cases for the Digital Twin framework for manufacturing will be detailed in technical reports 110 attached to this series of standards.

111 Automation systems and integration – Digital Twin framework for 112 manufacturing– Part 4: Information exchange

113 1 Scope

114 This part of ISO 23247 identifies technical requirements for information synchronization and 115 information exchange between entities of the reference model of the Digital Twin framework for 116 manufacturing.

117 ISO 23247 series defines a framework to support the creation of Digital Twins of observable 118 manufacturing elements including personnel, equipment, materials, processes, facilities, environment, 119 and products.

120 The following are within the scope of this part of ISO 23247;

121 - scope statement for ISO 23247 as a whole;

122 - overview of ISO 23247-4;

123 - requirements for information exchange A;

124 - requirements for information exchange B;

125 - requirements for information exchange C;

126 - requirements for information exchange D.

127 The following are described in other parts of ISO 23247;

128 - overview and general principles (Part 1);

129 - reference architecture of the Digital Twin framework for manufacturing (Part 2);

130 - digital representation of manufacturing elements of the Digital Twin framework for

131 manufacturing (Part 3);

132 - use cases of the Digital Twin framework for manufacturing to be detailed in technical reports.

133 The following are outside of the scope of ISO 23247;

134 - selection of the implementation methods and technologies for a Digital Twin for manufacturing;

135 - selection of the communication protocols for a Digital Twin for manufacturing;

136 - selection of the manufacturing devices and other resources to be represented by a Digital Twin;

137 - selection of the manufacturing processes to be represented by a Digital Twin;

138 - selection of the manufacturing products to be represented by a Digital Twin;

139 - design and process planning, and other non-manufacturing stages of the product lifecycle.

140 2 Normative references

141 The following documents are referred to in the text in such a way that some or all of their content 142 constitutes requirements of this document. For dated references, only the edition cited applies. For 143 undated references, the latest edition of the referenced document (including any amendments) applies.

144 ISO 23247-1, Automation systems and integration — Digital Twin manufacturing framework — Part 1: 145 Overview and general principles

146 ISO 23247-2, Automation systems and integration — Digital Twin manufacturing framework — Part 2: 147 Reference architecture

148 3 Terms and definitions

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

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

151 — ISO Online browsing platform: available at https://www.iso.org/obp

152 — IEC Electropedia: available at http://www.electropedia.org/

153

154 4 Overview

155 [Editorial note] Digital Twin entity will be updated to new name before DIS ballot. (All text, Figure 1~4, 156 Figure A.1~A.4)

157 ISO 23247-2 defines a functional view of Digital Twin reference model for manufacturing. Each entities 158 and observable manufacturing elements in the reference model are peers of information exchange. This 159 document specifies four types of information exchange between entities and observable manufacturing 160 element as shown in Figure 1. In addition, this document defines requirements for each type of 161 information exchange that the functional entities should provide.

162

163 Figure 1 — Reference Architecture of Digital Twin Framework for Manufacturing

164 The four types of information exchange are as follows:

165 ─ The information exchange A (IE-A) is an interface between Digital Twin user entity and Digital 166 Twin entity;

167 ─ The information exchange B1 (IE-B1), information exchange B2 (IE-B2), and information exchange 168 B3 (IE-B3) are the interfaces among three sub-entities within the Digital Twin entity; 169 NOTE The three sub-entities are Operation & management sub-entity, Application & service sub-entity, and 170 Resource access & interchange sub-entity.

171 ─ The information exchange C (IE-C) is an interface between the Digital Twin entity and Data 172 collection and device control entity (DCDCE);

173 ─ The information exchange D (IE-D) is an interface between DCDCE and Observable manufacturing 174 element (OME). 175

176 5 Requirements for information exchange A (IE-A)

177 [Editorial Notes] examine for the need to change some requirements to “shall”(JP06-013). This note to be 178 removed before DIS ballot.

179 5.1 Overview

180 The IE-A is an interface between Digital Twin User Entity and Digital Twin Entity, in which Digital Twin 181 User Entity uses services and applications provided by Digital Twin Entity as shown in Figure 2.

182

183 Figure 2 — Position of information exchange A (IE-A)

184 5.2 Visualization

185 IE-A should support visualization…

186 [Editorial Notes] Add requirements for visualization.

187 5.3 Standardized method for data exchange

188 [Editorial Notes] check for more requirements, if needed (CN-028). This note to be removed before DIS 189 ballot.

190 IE-A should provide standardized method in exchanging data (e.g., use of standardized protocol) for the 191 Digital Twin user entity to use services from the Digital Twin.

192 NOTE Some examples for standardized method are described in Annex A.2.1.

193 5.4 Transaction method

194 IE-A may use any of the three types of transaction method that follows:

195 ─ PULL method: user requests information from the information provider; 196 NOTE 1 In IE-A, Digital Twin user entity is the user, and Digital Twin entity is the information provider in the PULL 197 method.

198 ─ PUSH method: sender sends new or changed information to the receiver; 199 NOTE 2 In IE-A, Digital Twin user entity is the receiver, and Digital Twin entity is the sender in the PUSH method.

200 ─ PUBLISH method: publisher publishes data to be received by the subscribers. 201 NOTE 3 In IE-A, Digital Twin user entity is the subscriber, and Digital Twin entity is the publisher in the PUBLISH 202 method.

203 If Digital Twin user entity consists of one or two dedicated (or exclusive, private) applications, it is 204 possible to use PULL or PUSH method. If Digital Twin user entity consists of multiple arbitrary 205 applications, it is recommended to use PUBLISH method.

206 PUSH method can be used for transferring emergency information that requires immediate action by 207 the receiver. Emergency information includes reports from errors, faults, and warnings. PUSH method 208 can also be used to transfer message for predictive maintenance.

209 5.5 Security

210 IE-A should provide secure method of communication in terms of authentication, authorization, data 211 integrity, privacy, confidentiality, etc.

212 IE-A needs to confirm that correct information is received and delivered to the correct application 213 without being disclosed to unauthorized third party.

214 6 Requirements for information exchange Bs (IE-B1, IE-B2, IE-B3)

215 6.1 Overview

216 The IE-Bs are interfaces among three sub-entities (i.e., Operation & management sub-entity, Application 217 & service sub-entity, and Resource access & interchange sub-entity) within Digital Twin entity. Through 218 IE-Bs, sub-entities exchange information for the Digital Twin entity to provide Digital Twin services for 219 manufacturing as shown in Figure 3.

220 NOTE ISO 23247-2 describes functionalities of the three sub-entities as follows: 221 - Operation & management sub-entity operates and manages Digital Twin entity by maintaining information of the 222 observable manufacturing element; 223 - Application & service sub-entity provides functionalities related to simulation of manufacturing system, analysis of 224 data captured from observable manufacturing element, reporting of action such as production, etc; 225 - Resource access & interchange sub-entity provides access to functionalities to Digital Twin user entity with 226 controlled interfaces for application and service functionalities, administration functionalities, and business 227 functionalities in support of interoperability. 228

229

230 Figure 3 — Position of information exchange Bs (IE-B1, IE-B2, IE-B3)

231 The IE-Bs consists of IE-B1, which is an interface between Operation & management sub-entity and 232 Application & service sub-entity, of IE-B2, which is an interface between Application & service sub- 233 entity and Resource access & interchange sub-entity, and of IE-B3, which is an interface between 234 Operation & management sub-entity and Resource access & interchange sub-entity.

235 6.2 Digital Twin services

236 IE-Bs shall exchange information to provide services for recreating history, services for monitoring the 237 present status for various viewpoints, and services for simulation in order to plan for the future.

238 NOTE Digital Twin entity collects data from observable manufacturing elements through IE-C. Digital Twin entity may use 239 artificial intelligence to analyse the collected data. Based on data analytics, Digital Twin entity can reproduce the past, diagnose 240 the present, and plan for the future.

241 6.3 Presentation

242 IE-Bs should support presentation…

243 [Editorial Notes] Add requirements for presentation.

244 [Editorial Notes] Add requirements regarding QIF (measurement?).

245 6.4 Digital model

246 The Digital Twin of observable manufacturing elements are generated from digital model through 247 synchronization with observable manufacturing elements. IE-C shall have capability to exchange 248 information for presentation of digital model corresponding to the observable manufacturing elements.

249 NOTE Information for presentation includes visualization, static and dynamic information, change history, etc.

250 6.5 Implementation dependent

251 IE-Bs are implementation dependent and it is out of the scope of this document.

252 NOTE The three sub-entities within Digital Twin entity can be implemented in a single system/device or among multiple 253 system/devices. The process or processor that operates within the Digital Twin entity can use function calls, IPC, shared 254 memory or any techniques. Thus, information exchanged in IE-Bs are implementation dependent, and it is out of the scope of 255 this document.

256

257 7 Requirements for information exchange C (IE-C)

258 7.1 Overview

259 The IE-C is an interface between Digital Twin entity and DCDCE, in which the Digital Twin entity collects 260 information from observable manufacturing elements and controls devices in observable 261 manufacturing elements as shown in Figure 4. The Digital Twin entity maintains Digital Twin of 262 observable manufacturing element which is defined in ISO 23247-3.

263 NOTE 1 DCDCE interacts with OME(s). DCDCE monitors, senses, and in some cases, DCDCE performs actuation on OME(s) or 264 controls OME(s). Digital Twin entity uses DCDCE as a mediator to retrieve information of the OME(s) or to control OME(s).

265 NOTE 2 Annex A.4 shows some examples on how the Digital Twin entity and DCDCE are configured using various protocols 266 for collecting and controlling data.

267

268 Figure 4 — Position of information exchange C (IE-C)

269 7.2 Connectivity

270 IE-C shall provide networking capability to allow Digital Twin entity and the DCDCE to connect to the 271 network.

272 IE-C shall provide methods for the Digital Twin entity and the DCDCE to discover, identify, and create 273 relationships with each other.

274 NOTE Multiple devices (including sensors, manufacturing elements) will be participating in the Digital Twin services. The 275 devices can be connected and disconnected any time during the Digital Twin services. Since a device are controlled by the 276 DCDCE, Digital Twin entity will need to handle the join/leave activities of the multiple DCDCEs with plug-and-play support.

277 7.3 Standardized method for data exchange

278 [Editorial Notes] check for more requirements, if needed (CN-039). This note to be removed before DIS 279 ballot.

280 IE-C should provide a standardized method for exchanging data (e.g., use of standardized protocol).

281 NOTE Digital Twin entity acts as an application with DCDCE providing source data of the OME(s) through the use of 282 standardized protocol. The information exchanged in IE-C are characteristics, capabilities, status, location, etc. The ISO 23247- 283 3 defines the contents for this requirement.

284 7.4 Identification

285 IE-C should be able to identify observable manufacturing elements and set unique identification (or 286 name).

287 NOTE There can be Digital Twin for multiple observable manufacturing elements in the Digital Twin entity. There should be 288 an identification scheme to map the observable manufacturing elements with the corresponding Digital Twin. In some cases, 289 the sensors or the actuators are not represented by the Digital Twin, however, they need to provide sensing data or actuation 290 results to the Digital Twin entity. For this reason, Digital Twin entity will need to identify the sensors and the actuators of 291 observable manufacturing elements.

292 7.5

293

294

295 7.6 Applying manufacturing information

296 IE-C should have the capability to interface with manufacturing applications to apply manufacturing 297 information to Digital Twins.

298 NOTE DCDCE can be a manufacturing application such as MES, ERP, O&M system, or another Digital Twin systems for 299 manufacturing. Manufacturing information includes product planning, manufacturing execution, production results, quality 300 test results.

301 7.7 Synchronization

302 [Editorial Notes] check for more requirements on certainty during synchronization(best-effort? 303 Guaranteed communication?), if needed (CN-045). This note to be removed before DIS ballot.

304 IE-C shall have capability to exchange data for synchronization of changes among multiple Digital Twins.

305 NOTE Multiple devices such as production line can consist of multiple Digital Twins. A change in Digital Twin of a single 306 device can have effect on the other related Digital Twin.

307 IE-C shall have capability to exchange data for synchronization of changes from observable 308 manufacturing elements to Digital Twin.

309 IE-C may have capability to exchange data for synchronization of changes from Digital Twin to 310 observable manufacturing elements.

311 Network bandwidth in IE-C should be sufficient to support required level of synchronization.

312 NOTE Massive data from devices and sensors are exchanged in IE-C as with the increase of detailed level synchronization of 313 observable manufacturing elements with Digital Twin. Application needs to check if sufficient network bandwidth is available 314 in IE-C to support such level of synchronization.

315

316 7.8 Operation on Information exchange

317 IE-C shall provide a method for the Digital Twin entity to receive the data of the observable 318 manufacturing elements.

319 IE-C may provide a method for the Digital Twin entity to update/change the data of the observable 320 manufacturing elements.

321 IE-C may provide a method for the Digital Twin entity to control the observable manufacturing 322 elements.

323 IE-C should provide a method for the Digital Twin entity to create necessary Digital Twins for new 324 observable manufacturing elements.

325 IE-C should provide a method for the Digital Twin entity to delete corresponding Digital Twins as with 326 the removal or disconnection of the observable manufacturing elements. IE-C should provide method 327 for the DCDCE to send periodic data to trace changes of the observable manufacturing elements.

328 NOTE 1 Digital Twin entity needs to retrieve periodic data from DCDCE in order to apply any changes to the Digital Twin. The 329 periodic data may be stored to be used in Digital Twin services such as replicating the past, big data analysis.

330 IE-C should provide a method for the DCDCE to stop sending periodic information.

331 IE-C should provide a method for the DCDCE to notify when certain condition occurs.

332 NOTE 2 Dynamic data such as status changes are typical candidates for notification.

333 7.9 Transaction method

334 IE-C may use any of the three types of transaction methods (PULL method, PUSH method, PUBLISH 335 method).

336 PUBLISH method is recommended, if there are multiple Digital Twin systems for manufacturing and 337 multiple manufacturing applications that are receiving data from DCDCE.

338 NOTE The descriptions of the three types of transaction method are in clause 5.3.

339 7.10 Support of near real-time communication

340 IE-C may support near real-time communication, if the Digital Twin needs to receive near real-time 341 information. 342 NOTE The necessity of near real-time communication is application dependent. Urgent fault or alarm that needs immediate 343 attention is one reason to use near real-time communication.

344

345 [Editorial Notes] check for more requirements, if needed (CN-051). This note to be removed before DIS 346 ballot.

347 7.11 Support of twinning of mobile devices

348 IE-C may support mobility, if the Digital Twin needs to show the location of the mobile devices which is 349 one of the observable manufacturing elements.

350 [Editorial note] consider adding requirement(s) for network bandwidth (clause 7.6) and mobility (CN-015, 351 CN-016). This note to be removed before DIS ballot.

352 7.12 Security

353 IE-C may consider security issues as follows:

354 ─ Authentication and authorization: 355 Authentication is a process of establishing the identity of the user or processer. Authorization is 356 permitting access right or privileges to the resources. Authentication and authorization are an issue

357 when multiple observable manufacturing elements are involved in Digital Twin. There are high 358 chances of showing incorrect information when Digital Twin interacts with unauthorized physical 359 devices; 360 ─ Data integrity: 361 Data integrity is completeness, accuracy and consistency of data. Many observable manufacturing 362 elements and IoT devices are involved to create an accurate Digital Twin, which leads to massive 363 data flooding to the Digital Twin. It is critical for the DCDCE to check data integrity, filtering 364 unnecessary and inaccurate data; 365 ─ Privacy and confidentiality: 366 Privacy is an ability to secure individual or group information from public attention. Confidentiality 367 is protection of sensitive and private data from being disclosed to the public. Digital Twin involves 368 twinning of the observable manufacturing elements including personnel, equipment, material, 369 process, facility, and products. Data generated from the observable manufacturing elements and 370 various IoT devices is private and sensitive data for the manufacturer that needs to be protected. It 371 is possible for the Digital Twin to provide methods such as data encryption to ensure that data are 372 not disclosed to the public 373

374 8 Requirements for information exchange D (IE-D)

375 8.1 Overview

376 The IE-D is an interface between DCDCE and OME. The IE-D may not be necessary, if the OME supports 377 direct interface with Digital Twin entity by physically attached or integrated DCDCE to the OME.

378

379 Figure 5 — Position of information exchange D (IE-D)

380 8.2 Support of local network

381 IE-D should be connected with the DCDCE through the local network.

382 NOTE 1 The local network in this document refers to Industrial Ethernet or a proprietary network. Many manufacturing 383 equipment have connectivity with an Industrial Ethernet or proprietary network. Industrial Ethernet is an Ethernet that is 384 used in an industrial environment in limited configurations. Industrial Ethernet provides determinism and real-time control.

385 NOTE 2 Many factories establish a local network (or closed network) in the shop floor to protect internal data from being 386 revealed and being modified by the outside world. The DCDCE can be a part of a gateway of the local network and collect and 387 filter data for Digital Twin support.

388 8.3 Support of adaptation

389 IE-D should support adaptation of data received from OME to data that is understood by DCDCE.

390 IE-D should support adaptation of data received from DCDCE to data that is understood by OME.

391 NOTE Normally, DCDCE have an interface to the global IP network, i.e. external network. DCDCE needs to translate data 392 from local network to data that is understood by the external network. The DCDCE will need to filter unnecessary data and 393 perform pre-processing before delivering it to the external network. DCDCE also needs to translate data from the external 394 network before delivering it to the local network.

395 Annex A 396 (informative) 397 398 Technical discussion - 399 Implementation options for Digital Twin framework for manufacturing

400 A.1 Acronyms of protocols

401 This clause lists acronyms of protocols or standards that can be considered as an implementation 402 options of Digital Twin framework for manufacturing. 403 404 AES Advanced Encryption Standard 405 AMF Additive Manufacturing File format 406 API Application Program Interface 407 AutomationML Automation Markup Language 408 B2MML Business To Manufacturing Markup Language 409 CAD Computer Aided Design 410 CAM Computer Aided Manufacturing 411 CBC Cipher-Block Chaining 412 CCM Counter with CBC-MAC 413 CDD Common Data Dictionary 414 CFX Connected Factory Exchange 415 ECDHE Elliptic-curve Diffie–Hellman 416 EtherCAT Ethernet for Control Automation Technology 417 HTTP HyperText Transfer Protocol 418 IPC Inter-Process Communication 419 ISA International Society of Automation 420 JSON JavaScript Object Notation 421 JT Jupiter Tesslation 422 LwM2M Lightweight Machine to Machine 423 MOM Manufacturing Operations Management 424 MQTT Message Queuing Telemetry Transport 425 MTConnect Machine Tool Connect 426 OCF Open Connectivity Foundation 427 OID Object IDentifier 428 OPC-UA Open Platform Communications - Unified Architecture 429 OpenGL Open Graphics Library 430 OTD Open Technical Dictionary 431 PLC Programmable Logic Controller 432 PSK Phase-Shift Keying 433 QIF Quality Information Framework 434 RAMI 4.0 Reference Architectural Model Industrie 4.0 435 RAPINet Real-time Automation Protocols for Industrial Ethernet

436 REST REpresentational State Transfer 437 RSA Rivest–Shamir–Adleman 438 SHA Secure Hash Algorithm 439 STEP Standard for the Exchange of Product model data 440 TSN Time-Sensitive Networking 441 UUID Universal Unique Identifier 442 URI Uniform Resource Identifier 443 WebGL Web Graphics Library 444 XML eXtensible Markup Language 445

446 A.2 Implementation options for four IEs

447 Figure A.1 describes an implementation options for four IEs using various existing protocols.

448

449 Figure A.1 — Implementation options for four IEs

450 A.2.1 Implementation options for IE-A

451 The implementation options for IE-A are as follows:

452

453 ─ Regarding standardized methods for data exchange, Digital Twin entity can provide web services 454 for the Digital Twin user entity (with web client application) to use services provided by Digital 455 Twin entity through a web interface using HTTP or REST within IE-A. HTTP is a set of rules for 456 transferring files (e.g., text, image, multimedia data) through the web. REST is an architectural style 457 defining set of constraints to be used in web application. The data format that can be used includes 458 JSON, XML, etc. JSON is a lightweight data-interchange format for storing and transporting data. It is 459 a human-readable text consisting of attribute-value pairs and array data types. XML is a text-based 460 format used to share data. To exchange graphical information, it is possible to use API such as 461 WebGL, OpenGL. WebGL is a JavaScript API for rendering 2D/3D graphics. OpenGL is an API for 462 rendering 2D/3D graphics; 463 ─ Digital Twin entity can define open APIs to access services from Digital Twin. Digital Twin user 464 entity can use the open APIs in its applications. Open API (i.e., public API) is an application 465 programming interface that is available to the public. It allows user software (i.e., Digital Twin user 466 entity) to access internal functions of the program (i.e., Digital Twin entity). Web interface is one 467 example of Open API; 468 ─ Digital Twin entity and Digital Twin user entity can use shared memory (e.g. database, cloud) to 469 store the information generated by the Digital Twin entity. Digital Twin user entity can search and 470 fetch the needed information. A schema needs to be defined for accessing information provided by 471 the Digital Twin services.

472 ─ To support visualization, it is possible to use ISO 14306 (i.e., JT) which defines the syntax and 473 semantics of a file format for the 3D visualization and interrogation of lightweight geometry and 474 product manufacturing information derived from CAD systems, using visualization software tools 475 that do not need the full capability of a CAD system. … To provide web-based graphical information, 476 it is possible to use API such as WebGL, OpenGL. WebGL is a JavaScript API for rendering 2D/3D 477 graphics. OpenGL is an API for rendering 2D/3D graphics. 478 ─ [Editorial note] rewriting needed to specify implementation option for visualization: IEC 62714 is an 479 XML based data format for exchanging plant engineering information. Some application uses a 480 factory layout (blueprint) to create initial digital model of the shop floor. 481 [Editorial note] consider adding implementation options for JT, 3DPDF, 3D Rendering 482 (visualization perspective); 483 - JT (ISO 14306:2017, Industrial automation systems and integration — JT file format 484 specification for 3D visualization(visualization) 485 - 3DPDF: 3D PDF is a PDF file with 3D geometry inside. Using any 3D PDF enabled viewer, 486 rotation, zoom and part selection is available within the 3D view. This is often used for 487 documentation, sharing and collaboration. (visualization) 488 - 3D Rendering: 3D computer graphics process of converting 3D models into 2D images on a 489 computer. 3D renders may include photorealistic effects or non-photorealistic styles. 490 (visualization) 491

492 [Editorial note] consider adding implementation option for administration shell (AAS) in IE-A. (Note, The 493 asset administration shell (AAS) provides serializations in JSON, XML and (in work) RDF. (in Work): REST- 494 API - So AAS is an example how to implement IE-A)

495 A.2.2 Implementation options for IE-Bs

496 The implementation options for IE-Bs are as follows:

497 ─ For information exchange in IE-Bs, it is possible to use the same type of protocols, APIs, and 498 descriptive language as in IE-A; 499 ─ To support presentation, … 500 ─ [Editorial note] rewriting needed to specify implementation option for presentation: CAD/CAM 501 information can be used to create the digital model of the observable manufacturing element(s). 502 There are various standards that can be used for digital modelling such as ISO 10303-242 (i.e., 503 STEP AP242), ISO 10303-238 (i.e., STEP AP238), ISO 10303-239 (i.e., STEP AP239), IEC 62714 (i.e., 504 AutomationML). ISO 10303-242 supports managed model-based 3D engineering. ISO 10303-238 505 supports control language for controlling machine tools. ISO 10303-239 supports product lifecycle. 506 Some application uses a factory layout (blueprint) to create initial digital model of the shop floor. 507 [Editorial note] consider adding implementation options for JT, 3DPDF, 3D Rendering (presentation 508 perspective); 509 From https://all3dp.com/3d-file-format-3d-files-3d-printer-3d-cad-vrml-stl-obj/ 510 We simply explain the most common 3D file formats used today: STL, OBJ, FBX, COLLADA, 3DS, IGES; 511 STEP, and VRML/X3D. 512 A 3D file format is used for storing information about 3D models. You may have heard of the most 513 popular formats STL, OBJ, FBX, COLLADA etc. They are widely used in 3D printing, video games, 514 movies, architecture, academia, medicine, engineering, and earth sciences. 515 516

517 ─ To support xxx, it is possible to use standard such as ISO 23952 (i.e., QIF). ISO 23952 is an XML 518 based standard which defines, organizes, and associates quality information. With QIF, the Digital 519 Twin can be adjusted to be synchronized with the measured value. With big data analysis of the QIF 520 measured value, the accuracy of the predictive results can be increased. 521 ─ To provide Digital Twin services, data are gathered and stored from various data sources. Data can 522 be stored in a time table or event driven.

523 A.2.3 Implementation options for IE-C

524 The implementation options for IE-C are as follows:

525 ─ For connectivity between Digital Twin entity and DCDCE, Digital Twin entity can broadcast to the 526 network of its existence, method on connectivity, etc. DCDCE can use that information to connect to 527 the Digital Twin entity. DCDCE can be preconfigured to support plug-and-play with the Digital Twin 528 entity; 529 ─ Regarding standardized method for data exchange, Digital Twin entity can access/manipulate OME 530 using protocols such as MTConnect, OPC-UA, RAMI 4.0 administration shell. Digital Twin entity acts 531 as an application with DCDCE providing source data of the OME(s) through the standardized 532 protocol; 533 ─ Digital Twin entity can access/manipulate IoT devices (e.g., sensors, actuators) using protocols 534 such as OPC-UA, OCF, LwM2M, oneM2M, etc. IoT protocols have defined various data format that 535 are exchanged in the protocols. It is possible to define new data format for customized purposes; 536 ─ Digital Twin entity can access applications such as MES, ERP. Digital Twin entity can get 537 manufacturing-related data or modeling-related data through interface with the application. DCDCE 538 needs to support interface with such applications; 539 ─ Regarding Identification, there are many standards such as ISO 22745, IEC 61360, IEC 61987, ITU-T 540 X.660 | ISO/IEC 9834-1, ITU-T X.667 | ISO/IEC 9834-8, IETF STD 66 that can be used as a reference 541 for identification scheme of OME. ISO 22745 (i.e., OTD) defines database of concepts with 542 associated terms, definitions and images used for description of individuals, organizations, 543 locations, goods, services, processes, rules and regulations. IEC 61360 (i.e., CDD) defines data model 544 to be used for providing classifications and metadata definitions for describing products. The CDD 545 for process automation equipment are defined in IEC 61987. ITU-T X.660 | ISO/IEC 9834-1 (i.e., 546 OID) defines identification mechanism for naming any type of object, concept or ‘thing’ with 547 globally unique name. ITU-T X.667 | ISO/IEC 9834-8 (i.e., UUID) defines identification mechanism 548 using 128-bit number generated by algorithm with values that are based on a machine’s network 549 address to uniquely identify object or entity on the Internet. IETF STD 66 (i.e., URI) is defines 550 identification mechanism with string of characters used to unambiguously indentify a logical or 551 physical resources on the network, of which the best known type is web address (e.g. http://); 552 ─ Regarding digital model, if it is possible to identify the manufacturer and model number of OME 553 from the identification, it is possible to develop an initial digital model of the OME with the pre- 554 stored information such as visualization, capabilities provided, parameter, or standard used; 555 ─ To apply manufacturing information, the standards to consider are in IEC 62264 series (i.e., ISA-95) 556 which define the automated interface between enterprise and control systems. B2MML is an XML 557 implementation of IEC 62264. B2MML can be used to extract information on manufacturing (e.g., 558 asset tracking, inventory management) that can be applied to the Digital Twin for simulation or 559 analytic services. The ISO 16100 series can also be considered, since it defines manufacturing 560 information model that characterizes software-interfacing requirements enabling the 561 interoperability among manufacturing software tools (modules or systems). The ISO 18828 series 562 defines seamless production planning. It can be used as a reference for exchanging information 563 regarding changes of production planning;

564 ─ To support synchronization of changes, it is possible to use standardized data format such as 565 ISO/ASTM 52915(i.e., AMF). ISO/ASTM 52915 is an XML based format for describing objects for 566 additive manufacturing process such as 3D printing; 567 ─ To support PUBLISH method in transaction method, it is possible to use ISO/IEC 20922 which 568 defines Client Server publish/subscribe messaging transport protocol, i.e. MQTT; 569 ─ To support near real-time communication, it is possible to use the IEEE 802.1 series which defines 570 TSN services. TSN is a layer 2 protocol that supports low latency, low delay variation, low packet 571 loss. The participating system/devices need to synchronize time, perform traffic shaping through 572 scheduling in order to reduce switching time which leads to reduction of communication time. It is 573 possible to set priority to data to be delivered with different precedence. Control data or data 574 related to safety can be set with high priority; 575 ─ Regarding security, security algorithms to consider are PSK, ECDHE, CBC, CCM, SHA, RSA, etc.; 576 ─ It is difficult to apply security for services that are overwhelmed with data such as edge computing, 577 cloud, IoT data. Diffie–Hellman key exchange protocol are used for such services.

578 A.2.4 Implementation options for IE-D

579 The implementation options for IE-D are as follows:

580 ─ OME may support global protocols such as MTConnect, OPC-UA, administration shell, etc. In this 581 case OME is integrated with the DCDCE, thus, IE-D is not needed; 582 ─ Regarding support of local network, OME can support proprietary network or Industrial Ethernet 583 protocol (e.g., CFX, EtherCAT, Ethernet/IP, Profinet, Modbus, RAPIENet); 584 ─ Regarding support of adaptation, DCDCE will need to interface with the OME and support 585 adaptation/translation of the protocols used in proprietary network or Industrial Ethernet with the 586 global protocols; 587 ─ Some legacy equipment or devices may not have networking capability. It is possible to use various 588 sensors to collect some information. For example, it is possible to estimate operational status of the 589 equipment with thermal sensor, vibration sensor, sound sensors, electric current, etc.

590

591 A.3 Mapping of Digital Twin with source data

592 Figure A.2 describes the mapping of Digital Twin with various types of source data.

593

594 Figure A.2 — Mapping of Digital Twin with source data

595 Figure A.2 shows four examples of Digital Twin in Digital Twin entity and its mapping with various 596 types of source data. The examples are described as follows:

597 ─ Digital Twin can be a twinning of application using source data from various manufacturing 598 application (i.e., process) such as UI, MES, ERP as shown in example1 of Figure A.2. Application (e.g., 599 UI, MES, ERP) can be the Digital Twin user entity and the OME (provider of source data). For 600 application acting as a Digital Twin user entity, application can utilize results from the Digital Twin 601 entity for planning and analysis. Application acting as an OME provides data regarding 602 manufacturing process such as product planning, manufacturing execution, quality test results; 603 ─ Digital Twin can be twinning of manufacturing operations as shown in example2 of Figure A.2. It 604 combines data from various OMEs such as process, personnel, equipment, environment, product, 605 etc. Digital Twin entity needs to carefully maintain consistency on data received from multiple 606 OMEs by observing and coordinating data with regards to time, location, action, condition, state, 607 etc.; 608 ─ Digital Twin can be twinning of single device of OME as shown in example3 of Figure A.3. It can also 609 use data from the environment (e.g., sensors) for more accurate presentation of the Digital Twin; 610 ─ Digital Twin can be twinning of trends or check-list as shown in example4 of Figure A.3. It can use 611 data from environment (e.g., sensors).

612

613 A.4 Structure of multiple DCDCE and multiple OME

614 Figure A.3 describes how to structure DCDCE with multiple OMEs using different types of protocols. 615 DCDCE can control and manipulate multiple OMEs. The OMEs can use same or different types of 616 protocols.

617

618 Figure A.3 — DCDCE controlling multiple OMEs

619 Figure A.4 describes how to structure Digital Twin entity with multiple DCDCEs using different types of 620 protocols. The Digital Twin entity can control and manipulate multiple DCDCEs.

621

622 Figure A.4 — Digital Twin entity controlling multiple DCDCEs

623 Bibliography

624 [1] ISO 10303-238, Industrial automation systems and integration -- Product data representation 625 and exchange -- Part 238: Application protocol: Application interpreted model for computerized 626 numerical controllers

627 [2] ISO 10303-242, Industrial automation systems and integration -- Product data representation 628 and exchange -- Part 242: Application protocol: Managed model-based 3D engineering

629 [3] ISO 10303-239, Industrial automation systems and integration -- Product data representation 630 and exchange -- Part 239: Application protocol: Product life cycle support

631 [X] ISO 14306, Industrial automation systems and integration — JT file format specification for 3D 632 visualization

633 [4] ISO 16100 series, Industrial automation systems and integration -- Manufacturing software 634 capability profiling for interoperability

635 [5] ISO 18828 series, Industrial automation systems and integration -- Standardized procedure for 636 production systems engineering

637 [6] ISO 22745 series, Industrial automation systems and integration -- Open Technical Dictionaries 638 and their application to master data

639 [7] ISO 23247-2, Automation systems and integration — Digital Twin manufacturing framework — 640 Part 2: Reference architecture

641 [8] ISO 23247-3, Automation systems and integration — Digital Twin manufacturing framework — 642 Part 3: Digital representation of manufacturing elements

643 [9] IEC 62832 series, Industrial-process measurement, control and automation -- Digital Factory 644 framework

645 [10] ISO/ASTM 52915, Specification for additive manufacturing file format (AMF)

646 [11] ISO/CD 23952, Quality Information Framework

647 [12] ISO/IEC 20922, Information technology -- Message Queuing Telemetry Transport (MQTT) v3.1.1

648 [13] ISO/IEC TR 29181-9, Information technology — Future Network — Problem statement and 649 requirements — Part 9: Networking of everything

650 [14] IEC 61360 series, Standard data element types with associated classification scheme

651 [15] IEC 61987 series, Industrial-process measurement and control - Data structures and elements in 652 process equipment catalogues

653 [16] IEC 62264 series, Enterprise-control system integration

654 [17] IEC 62541 series, OPC unified architecture

655 [18] IEC 62714-1, Engineering data exchange format for use in industrial automation systems 656 engineering - Automation Markup Language - Part 1: Architecture and general requirements

657 [19] IEC PAS 63088:2017, Smart manufacturing - Reference architecture model industry 4.0 658 (RAMI4.0)

659 [20] ITU-T X.660 | ISO/IEC 9834-1, Information Technology - Open Systems Interconnection - 660 Procedures for the operation of Object Identifier Registration Authorities: General Procedures 661 and Top Arcs of the International object identifer tree

662 [21] ITU-T X.667 | ISO/IEC 9834-8, Information Technology -- Open Systems Interconnection -- 663 Procedures for the operation of Object Identifier Registration Authorities: Generation and 664 Registration of Universally Unique Identifiers (UUIDs) and their Use as ASN.1 Object Identifier 665 Components

666 [22] IETF RFC 6690, Constrained RESTful Environments (CoRE) Link Format

667 [23] IETF RFC 7230, Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing

668 [24] IETF RFC 7231, Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content

669 [25] IETF RFC 8259, The JavaScript Object Notation (JSON) Data Interchange Format

670 [26] IETF STD 66 (2015), Uniform Resource Identifier (URI): Generic Syntax

671 [27] W3C Extensible Markup Language (XML) 1.0, https://www.w3.org/TR/xml/.

672 [28] http://openconnectivity.org/

673 [29] https://qifstandards.org/

674 [30] http://www.ieee802.org/1/pages/tsn.html

675 [31] http://www.ipc-cfx.org/

676 [32] https://www.json.org/

677 [33] http://www.mesa.org/en/B2MML.asp

678 [34] https://www.mtconnect.org/

679 [35] http://www.onem2m.org/

680 [36] http://www.openmobilealliance.org/wp/Overviews/lightweightm2m_overview.html

681 [37] https://www.plattform-i40.de/PI40/Navigation/EN/InPractice/Online-Library/online- 682 library.html

ISO/TC 184/SC 4/WG 15 Digital manufacturing

Email of convenor: [email protected] Convenorship: ANSI (United States)

ISO CD 23247-1 Collated Comments Final Response LA Document type: Resolution

Date of document: 2019-11-19

Expected action: INFO

Background: For discussion during conference call on 11/20 or 11/21 depending on time zone - 7PM Eastern USA 11/20

Committee URL: https://isotc.iso.org/livelink/livelink/open/tc184sc4wg15 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

Accepted Change title to, "Automation systems and To be updated during DIS US integration – Digital twin framework for 0 TITLE Ge The title is not clear nor grammatically correct. ballot process 001 manufacturing – Part 1: Overview and general principles" ―Digital Twin framework for manufacturing‖ DE Background Ge Why not manufacturing with digital twins. What is Reconsider formulation. Accepted in principle ―digital twin manufacturing‖? 002 ISO 23247 series defines a framework for Digital Change ―a framework for There is a definition for digital twin and for digital Twin in Digital Twin in twin manufacturing framework, but there is no manufacturing as virtual representations of manufacturing‖ to ―a Digital term like ―digital twin manufacturing‖. In DT physical Twin framework for manufacturing framework it is written ―DT in manufacturing elements such manufacturing‖ manufacturing‖: this in fine

FR ge The documents of the ISO 23247 series Align the project on the NWIP. Accepted in principle 01 circulated as CD do not reflect the outline of the Assets are not specifically proposed project NWIP (ISO/TC 184/SC 4/WG 003 mentioned, however, 15 N 17). equipment and facility are The intended scope of the project as stated in the included as types of assets. NWIP was "The Digital Twin is a virtual

representation of manufacturing elements such as personnel,products, assets and process definitions."

FR ge The documents of the ISO 23247 series Consider the current normative landscape. Noted circulated as CD do not reflect the outline of the 02 IEC 62264 is informatively proposed project NWIP (ISO/TC 184/SC 4/WG referenced and listed in 15 N 17). 004 bibliography of this part. The NWIP standards gap analysis listed and IEC 62832 and ISO 16400 summarized: have been determined not - IEC 62264 Enterprise-control system to be referenced in ISO integration, 23247, however they can be listed in bibliography - IEC 62832 Digital factory framework during DIS development if - ISO 16400 Equipment behaviour catalogues for necessary. 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 1 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

virtual production system. These standards are not considered in documents of the ISO 23247 series circulated as CD.

FR ge There is not much additional information to Consider publishing one technical report Part 1 does not have ISO/IEC 30141 is this series of standards, and document. relationship with ISO/IEC 03 particularly provisions are missing. 30141. 005 There are many redondancies between parts. JP0 A comment Ge To say ―Digital Twin‖, consistency management Regenerate the document from scratch. The Digital Twin framework 1(A. common to between physical objects and their digital for manufacturing describes O) four representations shall be a core concern. framework how to relate proposed physical object to digital 006 documernts In other words, how to relate a physical object representation. with its digital representation and how to keep consistency between the two in the Specific technologies that circumstances where the physical object is are to be used to perform constantly changing shall be a keen concern. the synchronization are not prescribed by this standard Imagine the case of removal machining for and left by users’ to select. creating a die. There are many physical objects including work piece, machining tool, etc. During Use cases are to be machining, the shape and material characteristics developed in future reports of the work piece will constantly change. It is the and they will recommend same for the machining tool caused by fatigue. technologies to achieve the qualities described by the How to capture those changes and how to reflect framework in the context of the changes into their digital counterparts shall be specific processes. a core concern for digital twin manufacturing. But, no specification is defined in the proposed four documents concerning how to relate a physical object and its digital representation, and how to keep consistency between the two. The phrases ― detailed modelling‖ and ―dynamic modelling‖ appear with no clear definitions、 which is extremely inappropriate..

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 2 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

There will be changes which can be captured and those which are difficult to capture. Therefore, it is understood that clear statements of in scope issues and out of scope issues should be possible. But, current scope statement says almost nothing. In order to get support from industries, clear answers to the issues raised above is critically important. JP0 A comment Ge The title of the series of standards is digital twin Clear statements required. Accepted in principle 2(A. common to manufacturing framework but no manufacturing O) four specific terms appear. There are many types of Following has been added proposed manufacturing including removal machining for to introduction for 007 documernts creating automotive dies. clarification: What types of manufacturing is in scope and All types of manufacturing what types are not shall be clearly described. should be supported including discrete and continuous manufacturing for individual parts, assemblies or continuous processes. However, the actual types of manufacturing that can be supported by an instance of the framework will depend on the technologies selected to implement its functional elements.

JP0 A comment Ge It is very hard to imagine how to effectively use It is recommended to include real-life examples on Accepted in principle 3(A. common to proposed standards, which is a key requirement how to effectively use proposed standards/ O) four to stimulate manufacturing industry. Use cases are to be proposed developed in future reports 008 documernts and they will recommend technologies to achieve the qualities described by the framework in the context of 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 3 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

specific processes. JP0 A comment Ge ―Overview standard‖ of a series of standards shall See ISO 10303-1 and other ―overview‖ standards Noted 4(A. to the clarify for learning the role of the overview standard. O) proposed The scope and title have document (1) what are in scope of the series of been improved. 009 standards,what are not (2) what are concepts common to all the series of standards (3) what industry problems will be solved by the application of the standards, (4) structure of the series of the standards. But, this document does not satisfy these basic requirements. JP0 Introduction Ge The phrases ―detailed modelling of physical Rewrite from scratch. Accepted in principle 5(A. configurations‖, ―dynamic modelling of…..‖ O) appear. These phrases should be key concepts Introduction has been but no detailed definitions of these phrases rewritten. 010 appear in the document. More elaborate introduction statements are required. KR 59-60 Introduction ed Use a consistent term with other parts and Change to read: Accepted in principle 02 editorial enhancement. ISO 23247 series defines a framework for Digital Introduction has been 021 Twin manufacturing as digital representations of rewritten. observable manufacturing elements including personnel, equipment, material, processes, facilities, environment and products.

Change first sentence to, "ISO 23247 series Accepted in principle US Grammar error and inconsistent terms in first 59 Introduction Ge defines a framework for generating a digital twin in 022 sentence. Introduction has been manufacturing as digital representations of…" rewritten. Provide a definition for "assets" in section 3 or Accepted in principle change the sentence to, "...physical US The term "assets" is ambiguous and not defined 60 Introduction Ge manufacturing elements such as personnel, Introduction has been 023 in the document. products, equipment material, facility, rewritten. environment, and process definitions."

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 4 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

CN 66 Introduction ge Keep consistent between ―Introduction‖ and provides requirements and guidance for Accepted in principle Clause 1 ―Scope‖. developing a Digital Twin manufacturing 024 framework; Introduction has been rewritten. CN 68-69 Introduction ge Keep consistent between part 2 description with Provides a reference architecture goals and Accepted in principle other parts. objectives, reference model, and reference 025 architectural views for a Digital Twin Introduction has been manufacturing framework; rewritten. JP0 1. Scope Ge No meaningful scope statement is given. Revise it. Meaningful in scope and out of scope Accepted in principle 6(A. statements are keen requitements. O) Scope has been rewritten. 011 JP1 4 2. Scope ge The scope states the document provides an Describe the overview of Digital Twin Accepted in principle 0(K. overview of Digital Twin manufacturing. Although manufacturing as a digital model of physical Scope has been rewritten D) ―Digital Twin manufacturing‖ is not defined, , manufacturing elements in the document. and clarified. according to the explanation in Clause 4 it seems 015 a different concept from the concept ―Digital Clause 4 describe the Twin‖ itself, which is defined as a digital model in overview of Digital Twin for 4.2.4. manufacturing and Clause 5 describes Digital Twin On the other hand, ISO/TC 184/SC 4 N 3224 framework for (NWIP) states the following in its ―Scope of the manufacturing. proposed deliverable‖. This ISO xxxxx series defines a framework for Digital Twin manufacturing as virtual representations of physical manufacturing elements such as personnel, products, assets and process definitions. Digital Twin manufacturing is the detailed modeling of physical configurations, and the dynamic modeling of product, process and resource changes during manufacturing. Since this text implies that ―Digital Twin manufacturing‖ is a digital model, the scope text of this document is inconsistent with the NWIP. This document should describe the overview of 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 5 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

Digital Twin manufacturing, as a digital model of physical manufacturing elements. However, this document describes almost nothing about the model and modelling, but it describes mainly functions related to Digital Twin. JP1 4 1 ge ―describes general principles‖ is not specific and 1) Replace ―describes general principles, and Accepted in principle 1(K. not appropriate for scopes. provides guidance for developing a Digital Scope has been rewritten D) Twin manufacturing framework‖ with the ―guidance for developing a Digital Twin and clarified. following text. 016 manufacturing framework‖ sounds strange. Clause 4 describe the provide general principles of Digital Twin Since ―Digital Twin manufacturing framework‖ is overview of Digital Twin for manufacturing framework defined as a conceptual guidelines to support manufacturing and Clause implementation of Digital Twin, ―quidance‖ and 2) Provide guidelines for modelling physical 5 describes Digital Twin ―guideline‖ are duplicated each other. manufacturing elements in the document. framework for manufacturing. The phrase implies providing guidance for a guideline. However, developing the guideline is the task of this document. ISO/TC 184/SC 4 N 3224 (NWIP) states the following in its ―Scope of the proposed deliverable‖. Part 1: Overview and general principles Provides overview of Digital Twin manufacturing and describes general principles to give guidance for developing a Digital Twin manufacturing framework; Since the Digital Twin manufacturing framework is a conceptual guidelines to support implementation of Digital Twin, which is a digital model, this document should provide guidelines for modelling physical manufacturing elements. However, this document describes almost nothing about the model and modelling, but it describes mainly functions related to Digital Twin. FR 4 1 te The scope states: "This document provides an Clarify. Accepted in principle 04 overview of Digital Twin manufacturing ...". Scope has been rewritten 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 6 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

017 This may be interpretated as "This document and clarified. provides an overview of the manufacturing of a Clause 4 describe the Digital Twin..." overview of Digital Twin for manufacturing and Clause 5 describes Digital Twin framework for manufacturing. JP1 5 1 ge The main focus of ISO TC184/SC4 ―Industrial Provide the information view of Digital Twin, Scope has been rewritten 2(K. Data‖ is product data within Industry and especially in terms of data structure. and clarified. D) modelling. ISO TC184/SC4 N1167 ―SC4 Industrial Data Framework‖ describes the ISO 23247 Part 1 does not 018 concept of ―Industrial Reference Models‖ in reference ISO/IEC 30141 Clause 4. and it is not the base of this standard. All standards developed by ISO TC184/SC4 basically should focused on product data and Information view of Digital modelling, instead of functions and activities. Twin, especially in terms of data structure (information This draft is based on ISO/IEC 30141, Internet of attribute) and information Things (IoT) — Reference architecture, and exchange are addressed in focuses on the functional view and the system part 3 and part 4 of ISO view, instead of the information view. Instead of 23247. the information view of Digital Twin.

CN 5 1 ge Keep consistent between ―Introduction‖ and and provides requirements and guidance for Accepted in principle Clause 1 ―Scope‖. developing a Digital Twin manufacturing 019 framework. Scope has been rewritten and clarified. KR 4-5 1 te Add a clause to describe the guidance for Propose to change Accepted in principle 01 developing a Digital Twin manufacturing framework. ―guideline‖ to ―requirements‖ Scope has been rewritten 020 and clarified. JP0 3. Terms Te Justification on why proposed redefinition of Revise it. Accepted 7(A. and terms are necessary shall be given. O) definitions 012 KR 14-17 3.1.1 te Preferred to reference ISO standard. Change to read: Accepted 03

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 7 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

026 3.1.1 actuator device that provides a physical output in response to an input signal in a predetermined way [SOURCE: ISO/IEC 29182‑ 2] KR 62 3.1.11 ed Propose to change to a better definition device that observes and measures a physical Accepted 04 property of a natural phenomenon or man-made process and converts that measurement into a 027 signal Note 1 to entry: Signal can be electrical, chemical, etc. [SOURCE: ISO/IEC 29182‑ 2]

CN 68 3.2 ed Besides the definition of DTM in Introduction, add 3.2.x Digital Twin manufacturing a new subclause for the term ―Digital Twin Digital Twin manufacturing will not be defined in the 028 manufacturing‖ and its definition in 3.2. the detailed modelling of physical configurations, specification as a new term and the dynamic modelling of product, process and the phrase has been and resource changes during manufacturing grammatically corrected to Digital Twin for manufacturing Pick either "digital model" or "digital representation." Or provide a separate definition for each term. For example, "Digital model: a Accepted US 75 3.2.2 Te Providing the same definition for two terms. digital representation of a physical object and Digital representation has 029 serves as a basis for simulating the fabricated been removed design and structural behavior of the part." Remove Note 1. DE 78 Digital Compare to definition of IIC Consider using definition of IIC ISO definition has been model used 030 Question: Information – does it include data and Add definition for information or add note that behaviour? Seems so when reading the other behaviour is included parts of the framework

Is it really always decision-related? US Change definition to, "the procedure of creating a Accepted in principle 81 3.2.3 Te Definition of "digital modeling" is ambiguous 031 digital model of a physical element." Term has been changed to

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 8 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

Digital Twin modelling and the proposed definition has been applied with modification. Change definition to, "An integrated digital model Accepted in principle that combines data from both the cyber-world and US Definition of "digital twin" is incomplete and physical-world to mirror and predict activities, ISO definition has been 84 3.2.4 Te 032 ambiguous performance, outcomes, and/or events over the used life of the digital model’s corresponding physical element." DE 85 Digital twin Assets that a twin may represent should be more Extend definition to also include humans, virtual Accepted in principle broad than just processes and physical elements elements etc 033 (compare figure 1: seems to be the case; see Delete data connections from definition, too ISO definition has been also part 2 of framework: there many more technical, twins are about information not about used manufacturing elements are described) data

e.g. digital model of a manufacturing element that enables convergence between the physical and virtual states of the element at an appropriate rate of synchronisation

Check also IIC definition of twin that focusses on the use cases the twin supports US 88 3.2.5 Te Definition not needed. Remove the term. Accepted 034 CN 90 3.2.5 ge To use the term ―Digital Twin manufacturing‖ conceptual guidelines to support implementation Accepted in principle instead of ―Digital Twin in manufacturing‖. of Digital Twin manufacturing 035 The phrase ―Digital Twin manufacturing‖ has been changed to ―Digital Twin for manufacturing‖ The term and definition are not clear. What is the US Accepted 91 3.2.6 Te purpose of this term? The term appears to make Remove the term. 036 the language in the standard overcomplicated. The definition is inconsistent with the definitions Change definition to align with generally accepted US for "presentation" and "representation" in ASME 105 3.2.8 Te definition of "presentation" or adopt ASME Accepted 037 Y14.47-2019, "presentation: the manner in which Y14.47-2019's definition. information is displayed for use by a human," and

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 9 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

"representation: the manner in which information is stored for interpretation by a machine." US The Note has been 108 3.2.8 Te Note 1 does not apply to the term. Remove Note 1. 038 modified. CN 120-123 3.2.10 te View and viewpoint are two related terms that 3.2.10-1 The ISO dictionary has the should be defined respectively. ISO/IEC architecture view same entry for view and 039 19501:2005 is not proper source for these two work product expressing the architecture of a viewpoint and only makes terms because it does not provide their system from the perspective of specific system distinction. definitions. It is suggested that using ISO/IEC concerns 19514:2017 (SysML standard) or ISO/IEC/IEEE 3.2.10-2 The proposed ISO/IEC 42010:2011 (Architecture description standard) architecture viewpoint standard does not have as reference source. work product establishing the conventions for the valid terms and definitions construction, interpretation and use of architecture for view and viewpoint views to frame specific system concerns [SOURCE: ISO/IEC/IEEE 42010:2011] or 3.2.10-1 view the modeling element that represents the artifact that is presented to the stakeholder 3.2.10-2 viewpoint the point of view of a set of stakeholders by framing the concerns of the stakeholders along with the method for producing a view that addresses those concerns [SOURCE: ISO/IEC 19514:2017]

Note: A view conforms to only one viewpoint to ensure that only one method is applied to the view. The view shall be related to the model that contains the information and the method that produces the view. DE 124 Difficult to check whether there is abbr you are Sort abbreviation alphabetically Not accepted looking for 040 Already in alphabetical order.

CN 133 3.3 ed The abbreviated term ―DTM‖ is never used in four To use ―DTM‖ instead of ―Digital Twin Accepted parts of this standard. manufacturing‖ in proper cases.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 10 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

041 or To delete the abbreviated term ―DTM‖. JP0 4. Overview Te Consistency management between physical Thoruough revision is required. Accepted in principle 8(A. of digital objects and their digital representations is a keen O) twin requirement, but no specification for consistency Dynamic modelling has manufacturi management, in other words detailed been deleted from the 013 ng specifications for ―dynamic modelling‖, is given, document. which is extremely inappropriate. KR 158 4.1 ed Preferred title. Change to read: Not accepted 05 4.1 Concept Changing the title may 042 confuse 4.1 as concept of Digital Twin manufacturing. This clause describes concept of Digital Twin

Note: delete ―The‖ DE 159 4.1 ge The digital twin should remember its history to A digital twin is a digital model of the current and Accepted in principle support e.g. detection of anomalies historical state of a particular physical element or 043 process with data connections that enable Historical aspect has been convergence … added to clause 4.2 Digital Twin for manufacturing. US Replace definition of "digital twin" with the revised 159 4.1 Ge Restated definition of "digital twin" Accepted 044 definition. US Accepted 161 4.1 Ed Subject of the sentence unclear. Replace "It" with the subject of the sentence. 045 Replace to ‖Digital Twin‖ FR 159 4.2 Entire te The differences between "Digital Twin", "Digital Clarify. Accepted in principle subclause Twin manufacturing" and "Digital Twin 05 Terms and definitions have representation" are not clear in this subclause. been clarified. 046 US Provide clear text in the body of the document that Noted 169 4.2 Figure 1 Ge Benefits are not clear here 047 describes the benefits for each listed. Text is given in 4.4 DE 171 The concept really expects that there is an Please Clarify: The applications (and not only DT Accepted in principle integrated model of the complete manufacturing applications) just use the information from the 048 domain, i.e. in a way the sum of all digital models models of the twins depending on the use cases Use cases will be given in a of all twins in the system? It is not the twin that is they are interested in. A Digital Twin should not be TR.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 11 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

a specific kind of digital model (see term a large integrated model of the domain. The clause has been definition section)? written for clarification.

See before: propably the term ―DT manufacturing‖ is misleading: it is exactly one twin that is talked about in this section? FR 171 4.2 te A definition of "Digital Twin manufacturing" is Define "Digital Twin manufacturing". Accepted in principle missing. 06 The phrase ―Digital Twin manufacturing‖ has been 049 changed to ―Digital Twin for manufacturing‖ Accepted in principle Use cases will be given in a US Change to, "A digital twin is used in manufacturing 171 4.2 Ge Sentence incomplete TR. 050 for maintaining a digital model…" The clause has been written for clarification. KR 172 4.2 Ed Improve sentence From Accepted in principle 07 … to represent status, working conditions, product The clause has been geometries, and resource states in a synchronous written. 051 manner. Change to … to represent manufacturing status, manufacturing conditions, product geometries, resource state, and any other observable status and conditions in a synchronous manner. KR 174 4.2 Ed Redundant. Improve sentence. Change to Accepted in principle 08 Digital Twin Representation provides The clause has been functionalities to maintain and synchronize the written. 052 representation of a Digital Twin with its corresponding observable manufacturing elements by constantly exchanging operational and environmental data. 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 12 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

The two sentences between Lines 174 and 177 Accepted in principle US 174 4.2 Te are not technically clear and correct. The Remove Lines 174-177. 053 The clause has been sentences do not provide value to the section. written. DE 178 Add reference to part 3 that explain all these use Accepted cases? 054 Change sentence to, "A digital twin assists with US Accepted 178 4.2 Ge See US-08. detecting anomalies in the manufacturing 055 processes…" Change sentence to, "The visibility into process Accepted in principle US 182 4.2 Ge "Digital twin manufacturing" is not a defined term. and execution enabled by a digital twin enhances Changed to ―Digital Twin for 056 business…" manufacturing‖ KR 186 4.2 ed Follow a way of reference to clause in a Change to read: Accepted 06 document given in ISO/IEC Directive Part 2. Examples of applications, services and benefits 057 are given in 4.3 and 4.4. KR 187 4.3 ed Clause 4.3 describes only Digital Twin Change to read: Accepted manufacturing applications. Also, clause 4.5.2.1 4.3 Applications of Digital Twin manufacturing 09 explains Digital entities with Digital Twin 058 manufacturing application. and change the one in Figure 1. KR 187 4.3 te Besides given Digital Twin manufacturing Propose to add: Accepted in principle 10 application, it is worthwhile to include one of applications explained in TC 184/Ad Hoc Group: 4.3.5 Engineering design New clause has been 059 Data Architecture of the Digital Twin document. added for engineering Digital Twin for engineering design is a virtual design. representation of the design at the point of interest in the lifecycle. In the conceptual development and proposal phase, Digital Twin consists of models that manage requirements and demonstrate the allocation and validation of requirements to functional models with behaviour. KR 189 4.3.1 Ed Reword to match clause title. From Accepted 11 A real time application 060 Change to A real time control application

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 13 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

KR 198 4.3.4 Ed Reword From Accepted 12 … to check physical elements and production processes and if necessary, schedules predictive 061 maintenance. Change to … to check conditions of observable manufacturing elements and if necessary, schedules maintenance. Accepted in principle US Extend the text in Subsections 4.4.1 to 4.4.4 to 200 4.4 Te No benefits listed in each subsection. Text shall be improved for 062 describe expected benefits. DIS. DE 216 Element is a very generic term and difficult to Proposal: Use ―manufacturing element‖ as in part Accepted in principle refer to. You would need to say ―The twin 3. 063 represents an element of Digital Twin The phrase ―Digital Twin Manfucturing‖. And not ―The twin represents an Rename title to ―Manufacturing Elements manufacturing elements‖ entity‖ (IIC) or ―The twin represents an asset‖ represented by a Digital Twin‖ has been changed to (Plattform I4.0) or ―The twin represents a ―elements of Digital Twin for manufacturing element‖ manufacturing‖ DE 216 Since part 3 is describing manufacturing element: Mention that part 3 explains the manufacturing Yes. This is the complete is this a complete list as well? elements and may also add additional ones list. 064 Accepted in principle The phrase ―Digital Twin US Change to, "Elements of Digital Twins used in 216 4.5 Ge "Digital twin manufacturing" is not a defined term. manufacturing elements‖ 065 Manufacturing" has been changed to ―elements of Digital Twin for manufacturing‖ KR 219 4.5.1 Ed Reword Delete ―processes‖ Accepted 13 066 KR 230 4.5.1.3 Ed Reword From Accepted 14 … such as metal block

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 14 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

067 Change to … i.e., metal block, glass panel, etc., KR 239 4.5.1.6 Ed Reword (Plural to singular) From Accepted 15 conditions 068 Change to condition DE 245 4.5.1.8 ge The digital twin should also be able to observe Add a new subsection: Engineering Document. An Accepted in principle engineering documents. Engineering Document is any form of artefact 069 (requirement, plan, model, specification, ―Supporting document‖ is Reasons: configuration) that helps the digital twin added 1. Engineering models are essential to application and services to perform their duties. Part 3 will be revised understand the production process. accordingly. 2. Requirements mentioned in Sect. 5.4, such as fidelity can only be judged relative to the desired models (i.e. the engineering documents) DE 246, See above: product and process seems not be Please explain what exactly the term digital entity Accepted in principle 250, restricted. In Plattform Industrie 4.0 for example is used for 070 2531 asset-instance-representations and asse-type- Clause title has been representations are distinguished. And asset is Please check whether this list is really complete changed to ―digital elements‖ very generic. Here asset = product or process.

In general: not very clear what a digital entity is. The twin itself is propably also a digital entity? Change to, "Manufacturing applications of digital Accepted in principle US twin enable the reporting and adjusting of the 247 4.5.2.1 Te Section is not clear. Also, see US-08. 071 current state of manufacturing equipment and Rephrased for clarification operations." KR 251 4.5.2.2 Ed Reword From Accepted 16 … a specification of the properties of a product that are needed to characterise it such as 072 dimensions, tolerances, surface finish, etc.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 15 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

Change to … specifications or properties of a product that are necessary to characterise it such as dimensions, tolerances, surface finish, etc. JP0 5. Te What are described do not serve as a general Thoruough revision is required. Dynamic modelling has 9(A. principles. Provide detailed specifications for been deleted from this O) ―dynamic modelling‖ for consistency management document between physical objects and their digital 014 counterparts FR 259 5.1 te The sentence explaining the relation between Clarify "Digital Twin manufacturing framework", Accepted "Digital Twin manufacturing framework", "Digital "Digital Twin manufacturing system", "Digital Twin 07 The sentence has been Twin manufacturing system" and "Digital Twin manufacturing" and their relations. written. 073 manufacturing" is obscure.

FR 257 5 Entire te The concept of Digital Twin manufacturing 1- Add ISO/IEC 30141 in the normative This document does not 08 clause framework seems based on JTC 1's references. reference ISO/IEC 30141. ISO/IEC 30141. 074 2- Provide valuable provisions focusing on The added value of this document to industrial data, which is the scope of ISO/IEC 30141 is questionnable; ISO/TC 184/SC 4.

FR 257 5 Entire te The concept of Digital Twin manufacturing Clarify the choice of ISO/IEC 30141 and the This document does not 09 clause framework seems based on JTC 1's absence of reference to the hierarchies of reference ISO/IEC 30141. ISO/IEC 30141. IEC 62264. 075 IEC 62264-1 is referenced The NWIP standards gap analysis listed and and included in summarized IEC 62264 Enterprise-control bibliography. system integration being jointly developped by ISA, IEC/SC 65E and ISO/TC 184:SC 5.

US Change to, "General principles of the digital twin 257 5 Ge See US-01. Accepted 076 framework for manufacturing" Change to, "The digital twin framework for US 259 5.1 Ge See US-01. manufacturing provides guidance on how to Accepted 077 construct a digital twin of a manufacturing system 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 16 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

and … for the purpose of a digital twin in manufacturing, but does…" US Change to, "Standardization scope of the digital 262 5.2 Ge See US-01. Accepted 078 twin framework for manufacturing" Change "Digital Twin Manufacturing Framework" US 264 5.2.1 Figure 2 Ge See US-01. to "Digital Twin Framework for Manufacturing" in Accepted 079 both the figure and the caption US Change to, "Figure 2 shows the high-level concept 266 5.2.1 Ge "Digital twin manufacturing" is not a defined term. Accepted 080 of the digital twin framework for manufacturing" CN 257 5 te Current structure of Clause 5 is as follow: Proposed new structure of Clause 5 as follow: Accepted in principle 5 General principles of Digital Twin 081 manufacturing framework 5 General principles of Digital Twin manufacturing Rearranged 5.1 Overview framework 5.2 Scope of Digital Twin manufacturing 5.1 Overview 5.3  5.4 framework standardization 5.2 Requirements of Digital Twin manufacturing 5.2.1 Limitations and boundaries 5.3 Hierarchical modelling of Digital Twin 5.3 Hierarchical modelling of Digital Twin manufacturing manufacturing 5.4 Scope of Digital Twin manufacturing 5.4 Requirements of Digital Twin manufacturing framework standardization It is suggested rearrange the structure and 5.4.1 Limitations and boundaries putting requirements analysis first according to problem solving or systems engineering process. JP1 257 5 Entire ge The Digital Twin manufacturing framework seems Provide valuable contents focusing on the Accepted in principle 3 Clause based on ISO/IEC 30141, however there is information view. (K.D almost no valuable contents in addition to the Information view of Digital ) original IoT-RA. Twin, especially in terms of data structure (information 082 attribute) and information exchange are already given in part 3 and part 4 CN 259-261 5.1 ge 5.1 is a important statement on the business To copy the sentence ―The Digital Twin Accepted in principle requirements of DTMF. It should be claimed in manufacturing framework provides guidance on 083 Introduction. how to construct a Digital Twin manufacturing Introduction has been system and how applications and data sources updated for clarification. can inter-operate for the purpose of Digital Twin manufacturing, but does not specify any implementation technologies‖ to the 1st paragraph of ―Introduction‖. US 276 5.3 Ge "Digital twin manufacturing" is not a defined term. Change to, "Digital twin" Accepted in principle 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 17 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

084 The phrase ―Digital Twin manufacturing‖ has been changed to ―Digital Twin for manufacturing‖ Accepted in principle

US "Digital twin manufacturing system" is not a The phrase ―Digital Twin 277 5.3 Ge Change to, "Digital twin" 085 defined term. manufacturing‖ has been changed to ―Digital Twin for manufacturing‖ US 277 5.3 Ed Incorrect usage of "i.e.," Change "i.e.," to "e.g.," Accepted 086 Accepted in principle

US The phrase ―Digital Twin 278 5.3 Ge "Digital twin manufacturing" is not a defined term. Change to, "Digital twin" 087 manufacturing‖ has been changed to ―Digital Twin for manufacturing‖ US 278 5.3 Ed Incorrect usage of "etc" Remove "etc" Accepted 088 DE 280ff Please make more clear: what are the Please distinguish requirements to the framework Accepted in principle requirements w.r.t. a twin and what is required by and to the twin itself or to the 089 the framework: then the twin would solve some of environment/infrastructure (=DT Manfuacturing ―management‖ clasue has the requirements. But in the requirement System?) the twin will finally be instantiated been written. ―Management‖ it is already stated that the framework shall manage the twin elements… Accepted in principle

US The phrase ―Digital Twin 280 5.4 Ge "Digital twin manufacturing" is not a defined term. Change to, "Digital twin" 090 manufacturing‖ has been changed to ―Digital Twin for manufacturing‖ Accepted in principle US "Digital twin manufacturing system" is not a 283 5.4 Ge Change to, "Digital twin" ―system‖ has been deleted. 091 defined term. The phrase ―Digital Twin manufacturing‖ has been

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 18 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

changed to ―Digital Twin for manufacturing‖ Accepted in principle

US The phrase ―Digital Twin 288 5.4.1.2 Ge "Digital twin manufacturing" is not a defined term. Change to, "Digital twin" 092 manufacturing‖ has been changed to ―Digital Twin for manufacturing‖ CN 296 5.4.1.5 ge ―Digital Twin framework‖ is a new term without A Digital Twin manufacturing framework shall Accepted in principle definition. It is suggested using the term ―Digital be … 093 Twin manufacturing framework‖. The phrase ―Digital Twin manufacturing framework‖ has been changed to ―Digital Twin framework for manufacturing‖ Accepted in principle US 296 5.4.1.5 Te Incorrect usage of "Digital twin framework" Change to, "Digital twin implementation" 094 ―management‖ clasue has been written. DE 305 So it is not the asset=manufacturing element the Clarify what is simulated by the twin Accepted in principle twin is representing that is simulated but the 095 manufacturing system? The clause has been rewritten US Change "digital twin representation" to "digital 305 5.4.1.8 Ge See US-08. Accepted 096 twin" US Change "digital twin representation" to "digital 307 5.4.1.9 Ge See US-08. Accepted 097 twin" Accepted in principle ―system‖ has been deleted. US "Digital twin manufacturing system" is not a 316 5.4.2.3 Ge Change to, "Digital twin" 098 defined term. The phrase ―Digital Twin manufacturing‖ has been changed to ―Digital Twin for manufacturing‖ DE 318 5.4.2.4 ge Scalability may be misleading: Granularity 099 Scalability is the ability of a system, network or Digital model oft he physical element shall provide Accepted process to change size. But what does scalability an insight at different granularities. 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 19 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: Document: Project:

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

signify in this context? Should the model grow as the system grows? Maybe you mean granularity. Granularity of a model describes the level of detail in which it represents its target system. Accepted in principle

US The phrase ―Digital Twin 321 5.4.3.1 Ge "Digital twin manufacturing" is not a defined term. Change to, "Digital twin" 100 manufacturing‖ has been changed to ―Digital Twin for manufacturing‖ US Change "digital twin representation" to "digital 324 5.4.3.2 Ge See US-08. Accepted 101 twin"

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 20 of 20 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 ISO/TC 184/SC 4/WG 15 N 106

ISO/TC 184/SC 4/WG 15 Digital manufacturing

Email of convenor: [email protected] Convenorship: ANSI (United States)

ISO CD 23247-2 Collated Comments Final Response LA Document type: Resolution

Date of document: 2019-11-19

Expected action: INFO

Background: For discussion during conference call on 11/20 or 11/21 depending on time zone - 7PM Eastern USA 11/20

Committee URL: https://isotc.iso.org/livelink/livelink/open/tc184sc4wg15 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

FR ge The documents of the ISO 23247 series Align the project on the NWIP. Accepted in principle 01- circulated as CD do not reflect the outline of the Assets are not specifically 001 proposed project NWIP (ISO/TC 184/SC 4/WG mentioned; however, 15 N 17). equipment and facility are The intended scope of the project as stated in the included as types of assets. NWIP was "The Digital Twin is a virtual representation of manufacturing elements such as personnel,products, assets and process definitions." FR ge The documents of the ISO 23247 series Consider the current normative landscape. Noted 02- circulated as CD do not reflect the outline of the IEC 62264 is informatively 002 proposed project NWIP (ISO/TC 184/SC 4/WG referenced and listed in 15 N 17). bibliography of this part. The NWIP standards gap analysis listed and IEC 62832 and ISO 16400 summarized: have been determined not to - IEC 62264 Enterprise-control system be referenced in ISO 23247, integration, however they can be listed in bibliography during DIS - IEC 62832 Digital factory framework development if necessary. - ISO 16400 Equipment behaviour catalogues for virtual production system. These standards are not considered in documents of the ISO 23247 series circulated as CD. FR ge The concept of Digital Twin manufacturing 1- Add ISO/IEC 30141 in the normative Accepted 03- framework seems based on JTC 1's references. 003 ISO/IEC 30141. 1. ISO/IEC 30141 has been 2- Provide valuable provisions focusing on added in the normative The added value of this document to industrial data, which is the scope of references. ISO/IEC 30141 is questionnable; ISO/TC 184/SC 4. Discussion: How to deal with 2-? DE GENER Not clear: does the framework describe how to Clarify system boundaries of the reference Accepted 05- AL build a single twin. Or does it describe an architecture 004 infrastructure that can handle a large number of Following text will be added 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 1 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

twins? What is the scope of the reference into 6.2.1. architecture? “Digital Twin reference

architecture for The Entity CSE seems to show that it is the manufacturing provides an handling of a large number of twins. However the infrastructure to support a term “entity” suggerates a single twin… large number of Digital Twins” Digital Twins are managed by DTRE (Digital Twin Representation entity), not by CSE (Cross-system entity). JP A comment ge To say “Digital Twin”, consistency management Regenerate the document from scratch. The Digital Twin framework 01 common to between physical objects and their digital for manufacturing describes (AO) four representations shall be a core concern. framework how to relate -005 proposed physical object to digital documernts In other words, how to relate a physical object representation. with its digital representation and how to keep consistency between the two in the Specific technologies that are circumstances where the physical object is to be used to perform the constantly changing shall be a keen concern. synchronization are not prescribed by this standard Imagine the case of removal machining for and left by users’ to select. creating a die. There are many physical objects including work piece, machining tool, etc. During Use cases are to be machining, the shape and material characteristics developed in future reports of the work piece will constantly change. It is the and they will recommend same for the machining tool caused by fatigue. technologies to achieve the qualities described by the How to capture those changes and how to reflect framework in the context of the changes into their digital counterparts shall be specific processes. a core concern for digital twin manufacturing. But, no specification is defined in the proposed four documents concerning how to relate a physical object and its digital representation, and how to keep consistency between the two. The phrases “ detailed modelling” and “dynamic modelling” appear with no clear definitions、

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 2 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

which is extremely inappropriate.. There will be changes which can be captured and those which are difficult to capture. Therefore, it is understood that clear statements of in scope issues and out of scope issues should be possible. But, current scope statement says almost nothing. In order to get support from industries, clear answers to the issues raised above is critically important. JP A comment ge The title of the series of standards is digital twin Clear statements required. Accepted in principal 02 common to manufacturing framework but no manufacturing (AO) four specific terms appear. There are many types of Following has been added to -006 proposed manufacturing including removal machining for introduction for clarification: documernts creating automotive dies. All types of manufacturing What types of manufacturing is in scope and what should be supported types are not shall be clearly described. including discrete and continuous manufacturing for individual parts, assemblies or continuous processes. However, the actual types of manufacturing that can be supported by an instance of the framework will depend on the technologies selected to implement its functional elements. JP A comment ge It is very hard to imagine how to effectively use It is recommended to include real-life examples Accepted in principal 03 common to proposed standards, which is a key requirement on how to effectively use proposed standards/ (AO) four to stimulate manufacturing industry. Following has been added to -007 proposed introduction for clarification: documernts All types of manufacturing should be supported including discrete and continuous manufacturing for individual parts, assemblies

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 3 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

or continuous processes. However, the actual types of manufacturing that can be supported by an instance of the framework will depend on the technologies selected to implement its functional elements. JP Throughout ge Meaningless number appears at the left of each Remove them. Acknowledged 04 of the line. (AO) document The number in left side of -008 document is for easy pointing to give comments for the ballot. In IS publication stage, this number will be totally removed. US 0 TITLE ge The title is not clear nor grammatically correct. Change title to, "Automation systems and Accepted in principle 01- integration – Digital twin framework for 009 manufacturing – Part 2: Reference architecture" Changed to “Automation systems and integration – Digital Twin framework for manufacturing – Part 2: Reference architecture"

US 0 WHOLE ge See CD 23247-1 Comment US-08 to remove Change "digital twin representation" to "digital Accepted 02- DOCUMEN "Digital Twin Representation" twin" throughout entire document 010 T The term “Digital Twin Representation” is architectural point of view and implies a set of systems and functionalities to manage and maintain Digital Twins. US 0 WHOLE ge "Digital twin manufacturing" is not a defined term. Change to, "Digital twin" throughout entire Accepted in principle 03- DOCUMEN document 011 T Changed to “Digital Twin for manufacturing”.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 4 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

See US01-009. US 0 WHOLE ge See US-01. Change "digital twin manufacturing framework" Accepted in principle 04- DOCUMEN to "digital twin framework for manufacturing" Changed to “Digital Twin 012 T throughout entire document. framework for manufacturing” JP Introduction ge What are written are not appropriate as Acknowledged 05 explanations in “Introduction”. (AO) Revised Introduction of Part -013 Many phrases appear without definition or 1 will replace the Introduction detailed specification, such as of Part 2. “Deatiledmodelling”, “Dynamic modelling”, etc. See US05-014. US 80 Introduction ge Duplicated text from CD 23247-1 is not Ensure consistency between CD 23247-1 and -2 Accepted 05- consistent. Introductions. 014 Introduction of Part 1 will be used. DE 81 ge See other comment w.r.t. definition of a twin, Aligned usage of definition of twin in all parts Acknowledged 01- should then be aligned 015 Revised Introduction of Part 1 will replace the Introduction of Part 2. See US05-014. DE 83 ge Why detailed modelling: it has to be as detailed Remove detailed from sentence Acknowledged 02- as needed. Detailing is not a quality in itself 016 Revised Introduction of Part 1 will replace the Introduction of Part 2. See US05-014. DE 83 ge The term “Digital Twin Manufacturing” is very Improve definition of DT Manufacturing and use Acknowledged 03- difficult to understand and to use. Compare to consistently in all part of DT Framework 017 findings for part 1. Revised Introduction of Part 1 will replace the Introduction of Part 2. e.g. What exactly is it? And what is its relationship to See US05-014. the twins? Is it the infrastructure for the twins? Is Explain DT manufacturing by using the term it the name for the complete system that also digital twin. Same for the other terms. 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 5 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

contains twins. Explain what a twin exactly is representing Or is it: A twin consists of a) a DT manufacturing b) a DTRE c) … Introduce term of composite or hierarchical twin Not very clear… (or similar)

If a twin either represents a product how can it then also represent the process and describe all relevant manufacturing aspects. Or is it a composite twin that uses other twins?

How many manufacturing elements are represented by a single twin? It seems a twin can represent a large number of manufacturing elements at once. Why not only one element and the compose

more complex twin out of the atomic twins? In part 1 hierarchical twin are mentioned. KR 85-87 Introduction ed Editorial enhancement Change to read: Acknowledged 01- 018 Digital Twin manufacturing maintains a digital Revised Introduction of Part model that continuously updates and changes 1 will replace the Introduction as the physical counterpart changes to represent of Part 2. manufacturing status, manufacturing conditions, See US05-014. product geometries, resource state, and any other observable status and conditions in a synchronous manner. KR 88-91 Introduction ed Editorial enhancement Change to read: Acknowledged 02- 019 Digital Twin Representation provides Revised Introduction of Part functionalities to maintain and synchronize the 1 will replace the Introduction representation of a Digital Twin with its of Part 2. corresponding observable manufacturing 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 6 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

elements by constantly exchanging operational See US05-014. and environmental data. KR 90 Introduction ed Use a consistent term with other parts. Change “physical manufacturing elements” with Acknowledged 03- “observable manufacturing elements”. 020 Revised Introduction of Part 1 will replace the Introduction of Part 2. See US05-014. CN 96 Introduction ge To use the term “Digital Twin manufacturing” The visibility into process and execution enabled Acknowledged 01- instead of “Digital Twin for manufacturing”. by Digital Twin manufacturing enhances 021 business cooperation and various efficiencies. Revised Introduction of Part 1 will replace the Introduction of Part 2. See US05-014. KR 99 Introduction ed Use a consistent term with other parts. Change “physical manufacturing elements” with Acknowledged 04- “observable manufacturing elements”. 022 Revised Introduction of Part 1 will replace the Introduction of Part 2. See US05-014. CN 103 Introduction ge Keep “Introduction” consistent between part 1 provides requirements and guidance for Acknowledged 02- and part 2. developing a Digital Twin manufacturing 023 framework; Revised Introduction of Part 1 will replace the Introduction of Part 2. See US05-014. CN 106 Introduction ge Keep consistent between part 2 description with Provides a reference architecture goals and Acknowledged 03- other parts. objectives, reference model, and reference 024 architectural views for a Digital Twin Revised Introduction of Part manufacturing framework; 1 will replace the Introduction of Part 2. See US05-014. KR 123 1 ed Use a consistent term with other parts. Change “physical manufacturing elements” with Accepted 05- “observable manufacturing elements”. 025 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 7 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

KR 123 1 ed Consistency with other parts Add “environment” Accepted 06- 026 FR 123 1 ed A comma is missing. Replace by: Accepted 04- 027 "personnel, equipment, material, processes, facilities, and products" JP 125 1 ge The scope is not consistent with the following 1) Make the scope text consistent with the Acknowledged 06 scope text stated in ISO/TC 184/SC 4 N 3224 scope text in the NWIP. (KD) (NWIP). 1. Requirements of Digital -028 2) Provide requirements for Digital Twin Twin framework for Part 2: Reference architecture manufacturing realization in terms of manufacturing are information modelling physical elements. defined in Part 1. Provides a reference architecture, set of terms and definitions, and requirements for Digital Twin The overall scopes of manufacturing realization in terms of information Part 1 – Part 4 do not modelling, in-loop simulation, information differ from the scope of exchange, and identification of information NWIP, but re-arranged objects; between each part for enhancement. Requirements for Digital Twin manufacturing realization in terms of information modelling It will be asked to SC 4 physical elements seem not specified in the Secretariat to be document. necessary of scope change ballot. 2. Technical Reports on use cases will cover requirements for Digital Twin for manufacturing in terms of information modelling physical elements JP 125 1 ge ISO TC184/SC4 N1167 “SC4 Industrial Data Provide the information view of Digital Twin, Acknowledged 07 Framework” states the following in 1.2 Out of especially in terms of data structure, instead of (KD) Scope. providing the architecture view. Information view of Digital -029 Twin, especially in terms of Any architecture or definition of how STEP/SC4 data structure (information standards support the industrial requirement is attribute) and information out of scope. exchange are addressed in 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 8 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

Part 3 and Part 4. CN 144 4 ge “Digital Twin manufacture” is a new term without Digital Twin manufacturing reference Accepted in principle 04- definition. It is suggested using “a Digital Twin architecture outlines what the overall structured 030 manufacturing system” instead. approach for the construction of a Digital Twin Digital Twin reference manufacturing system should be. architecture for manufacturing outlines what the overall structured approach for the construction of a Digital Twin for manufacturing should be. KR 144 4 ed Editorial enhancement Change “the construction of Digital Twin Accepted in principle 07- manufacture” with “the construction of Digital 031 Twin manufacturing”. See CN04-030. KR 145 4 ed Choose better word that suits manufacturing Change to read: Accepted in principle 08- 032 Digital Twin manufacturing reference Digital Twin reference architecture provides guidance for developing architecture for Digital Twin manufacturing. manufacturing provides guidance for developing Digital Twin for manufacturing and aims to give a better understanding of Digital Twin for manufacturing to the stakeholders of such systems, including device manufacturers, application developers, users, etc. KR 147 4 ed “Customers” and “Users” seem to be somewhat Change to read: Accepted 09- redundant and vague. 033 including device manufacturers, application See KR08-032. developers, users, etc. KR 149-151 4 ed Editorial enhancement Change to read: Accepted in principle 10- 034 - Digital Twin manufacturing reference - Digital Twin reference models, describing structure of the domains models for and structure of the entities; manufacturing, describing structure of - a set of relevant architectures in terms of 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 9 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

functional and networking views the domains and structure of the entities; - a set of relevant architectures in terms of functional and networking views KR 155-156 4 ed Editorial enhancement Change to read: Accepted in principle 11- 035 Figure 1 shows outline of Digital Twin Figure 1 shows outline of manufacturing reference architecture defining Digital Twin reference relevant reference models and architectural architecture for views derived from requirements specified in manufacturing to define ISO 23247-1. relevant reference models and architectural views derived from requirements specified in ISO 23247-1. CN 158 5 ge The title of Clause 5 should use plural for the 5 Digital Twin manufacturing reference models Accepted 05- word “model”.

036 JP 158 5 Entire ge The Digital Twin manufacturing framework seems Provide valuable contents focusing on the Acknowledged 08 Clause based on ISO/IEC 30141, however there is information view. (KD) almost no valuable contents in addition to the Clause 5 gives reference -037 original IoT-RA. models in terms of Digital Twin for manufacturing based on IoT reference architecture. Information view (that is Information attribute) and information exchange are given in Part 3 and Part 4. KR 160-165 5.1 ed Move clause 5.1 to more appropriate place and Add the follows before line 148 and remove Accepted 12- improve text. subclause 5.1: 038 Digital Twin encompasses Internet of Things (IoT) as its data collecting and controlling technology as well as conceptual background. ISO/IEC 30141 defines IoT reference models

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 10 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

including domain-based reference model and entity-based reference model, and also defines reference architecture by providing several reference architectural views including functional view, system deployment view, networking view, and usage view. By reference to ISO/IEC 30141, this document has the following descriptions: FR 166 5.2 ed Complicated acronyms (OMSD, ASSD, RAISD, Remove or simplify the acronyms. Accepted 05- DCDCD, PMD) have bben added on top of 039 ISO/IEC 30141 that does not help because too Acronyms will be removed. long and difficult to pronounce. KR 170 5.2.1 ed Editorial enhancement Change “. Mainly” with “, in other words” Accepted 13-

040 CN 172 5.2.1 ge According to Fig 2, there are three not four kinds In Digital Twin manufacturing framework, Not accepted 06- of domains inside the box of Digital Twin domains are classified into three categories ... 041 manufacturing framework. Physical manufacturing domain is one of four categories. KR 172-174 5.2.1 ed Editorial enhancement Change to read: Accepted in principle 14- 042 In Digital Twin manufacturing framework, In Digital Twin framework for domains are classified into four categories as manufacturing, domains are follows: classified into four categories as follows: KR 176-178 5.2.1 te To avoid confusion of domain-based reference Remove OMSD, ASSD and RAISD from DTRD. Accepted 15- model and entity-based reference model, sub- 043 domain is not required in DTRD. This shall be consistent in other parts. KR 180-182 5.2.1 ed Editorial enhancement and use a consistent term Change to read: Accepted in principle 16- with other parts. 044 Observable manufacturing domain (OMD) is out Observable manufacturing of scope of Digital Twin manufacturing domain is out of scope of framework, however, this document describes Digital Twin framework for OMD to enhance understanding of Digital Twin manufacturing, however, this manufacturing. document describes

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 11 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

observable manufacturing domain to enhance understanding of Digital Twin for manufacturing. CN 181 5.2.1 ge To use the term “Digital Twin manufacturing” … however this document includes PMD to Not accepted 07- instead of “Digital Twin for manufacturing”. show the whole reference architecture of Digital 045 Twin manufacturing. See US03-011 and KR16- 044. KR 184-185 5.2.1 Figure 2 te If KR15 is accepted, remove OMSD, ASSD and Modified Figure 2: Accepted 17- RAISD from DTRD in Figure 2. 046

This shall be consistent in other parts. US 185 5.2.1 Figure 2 te Need explaining the arrows between domains. If not, draw an arrow between OMSD and Acknowledged 06- OMSD interacting with RAISD passes through RAISD. Please refer fig 1 in the part 4 047 ASSD? See KR17-046 KR 187-189 5.2.1 ed Follow a way of reference to clause and Change to read: Accepted in principle 18- subclause in a document given in ISO/IEC 048 Directive Part 2. This classification is a logical grouping of tasks This classification is a logical and functions, which are performed by Digital grouping of tasks and Twin manufacturing framework entities functions, which are explained in 5.3 and functional entities (FE) performed by Digital Twin explained in 6.2 in detail. Entities in domain framework entities for interact with other entities by means of a set of manufacturing explained in networks described in 6.3. 5.3 and functional entities (FE) explained in 6.2 in detail. Entities in domain 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 12 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

interact with other entities by means of a set of networks described in 6.3. KR 190 5.2.2 ed Use a consistent term with other parts. Change the title of subclause 5.2.2 with Accepted in principle 19- “Observable manufacturing domain (OMD)” 049 Observable manufacturing domain See FR 05-039. KR 191-194 5.2.2 te Use a consistent term with other parts and Change to read: Accepted in principle 20- editorial enhancement. 050 “OMD consists of the physical manufacturing Observable manufacturing resources such as personnel, equipment, domain consists of the material, process, facility, and environment. physical manufacturing OMD shall be monitored and sensed for data resources such as personnel, collection and device control in Digital Twin equipment, material, manufacturing framework”. process, facility, and environment. Observable manufacturing domain shall be monitored and sensed for data collection and device control in Digital Twin framework for manufacturing

Example: Spatial/logical/functional area of machine tool is an example of observable manufacturing domain See US03-011 and FR 05- 039. DE 196 DCDCD It is not clear whether DCDCD is one program Perhaps it helps to formulate a sentence with Accepted 04- that is used by many twins. Or is one DCDCD for digital twin and DCDCD in one sentence to 051 each twin? describe the relationship. Domain is useful to describe various tasks that have to be performed in separate areas, by allowing a logical and (See other comment: does DT consists of DTRE 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 13 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

and DCDCD or does DT = DTRE or …) sometimes physical subdivision, in other words, domains are used to sort functions into areas of responsibility. Therefore, domain is not a program, but entity can be programs and systems that is used by Digital Twin. Following text will be added in new clause under 5.x.x Data collection and device control entity “Digital Twin for manufacturing shall have one or more data collection and device control entity, because Digital Twin for manufacturing consists of one or more observable manufacturing elements that shall be controlled.” KR 197-200 5.2.3 ed Editorial enhancement Change to read: Accepted in principle 21- 052 DCDCD is a logical domain which monitors and Data collection and device collects data from sensory devices in OMD, and control domain is a logical control and actuate devices in OMD. DCDCD domain which monitors and links observable manufacturing elements and collects data from sensory digital entities for synchronization. devices in observable manufacturing domain, and control and actuate devices in observable manufacturing domain. Data collection and device control domain links observable manufacturing elements and digital entities for synchronization.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 14 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

See FR 05-039. KR 202 5.2.4 te To avoid confusion of domain-based reference Change to read: Accepted in principle 22- model and entity-based reference model, sub- 053 domain is not required in DTRD. 5.2.4 Digital Twin Representation domain 5.2.4 Digital Twin domain (DTRD) See KR15. Digital Twin domain is DTRD is responsible for overall operation and responsible for overall management of Digital Twin manufacturing operation and management including provisioning, managing, monitoring, of Digital Twin for and optimization. In detail, digital modeling, manufacturing including presentation, and synchronization of observable provisioning, managing, manufacturing element are done in DTRD. monitoring, and optimization. In detail, digital modeling, Digital Twin applications and services are hosted presentation, and in DTRD such as simulation, analysis, etc. In synchronization of addition, DTRD provides access to entities of observable manufacturing Digital Twin manufacturing framework and element are done in Digital interaction with external entities such as peer Twin domain. DTRD by guaranteeing interoperability. Digital Twin applications and EXAMPLE Spatial/logical/functional area of services are hosted in Digital Digital Twin server implementing Digital Twin Twin domain such as management, simulation, and authentication and simulation, analysis, etc. In authorization is an are example of DTRD. addition, Digital Twin domain provides access to entities of Digital Twin framework for manufacturing and interaction with external entities such as peer Digital Twin domain by guaranteeing interoperability. EXAMPLE Spatial/logical/functional area of Digital Twin server implementing Digital Twin management, simulation, and authentication and authorization is an are example of Digital Twin

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 15 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

domain.

See US02-010, US03-011, US04-012 and FR05-039. KR 203-218 5.2.4.1 te To avoid confusion of domain-based reference Remove 5.2.4.1, 5.2.4.2, and 5.2.4.3 Accepted 23- model and entity-based reference model, sub- 054 5.2.4.2 domain is not required in DTRD. 5.2.4.3 See KR15. KR 230-231 5.3.1 Figure 3 te Data collection and device control are separate Change Figure 3 as follows: Accepted in principle 24- functions; therefore, they shall be separate 055 entities. Remove acronyms and add arrow between OMSE and Use a consistent term with other parts. RAISE. See US07-056

US 231 5.3.1 Figure 3 te Need explaining the arrows between domains. If not, draw an arrows between OMSE and Accepted 07- OMSE interacting with RAISE passes through RAISE. Please refer fig 1 in the part 4 056 ASSE? KR 232-233 5.3.1 te Use a consistent term with other parts and Change to read: Accepted in principle 25- editorial enhancement 057 Figure shows an entity-based Digital Twin Figure 3 shows an entity- manufacturing reference model. A set of OMSE, based Digital Twin reference ASSE, and RAISE digitally represents model for manufacturing. A observable manufacturing elements as Digital set of operation and Twins, and maintains the Digital Twins, therefore management sub-system it is called Digital Twin Representation entity. entity, application and service sub-system entity, and resource access and 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 16 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

interchange sub-system entity digitally represents observable manufacturing elements as Digital Twins, and maintains the Digital Twins, therefore it is called Digital Twin entity. See US02-010, US03-011, US04-012 and FR05-039. KR 235 5.3.2 te Use a consistent term with other parts. Change the title of 5.3.2 as follows: Accepted in principle 26- 058 5.3.2 Observable manufacturing element (OME) 5.3.2 Observable manufacturing element See FR05-039. KR 236-237 5.3.2 ed Editorial correction for use of a consistent term. Change to read: Accepted in principle 27- 059 OME shall be monitored and sensed, and may Observable manufacturing be actuated and controlled by DCDCE. It element shall be monitored includes personnel, equipment, material, and sensed, and may be process, etc. actuated and controlled by data collection and device control entity. It includes personnel, equipment, material, process, etc. See FR05-039. KR 239 5.3.3 ed Editorial correction for use of a consistent term. Change PME with OME. Accepted in principle 28- 060 PME will be replaced by Observable manufacturing element. See FR05-039. KR 238-244 5.3.3 te According to KR24, 5.3.3 shall be restructured. If KR24 is accepted, change 5.3.3 to read: Accepted in principle 29- 061 5.3.3 Data collection and device control 5.3.3 Data collection and entity (DCDCE) device control entity 5.3.3.1 Data collection sub-entity (DCLT_SE) 5.3.3.1 Data collection sub- 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 17 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

DCLT_SE interacts with the OME by monitoring entity and sensing for data collection, therefore may Data collection sub-entity include sensors and other data collecting interacts with the observable devices. manufacturing element by DCLT_SE communicates with Digital Twin monitoring and sensing for Representation entities (DTRE), i.e., OMSE, data collection, therefore ASSE and RAISE, for support of generating, may include sensors and synchronizing, and managing Digital Twins, other data collecting devices. exactly speaking, digital entities of observable Data collection sub-entity manufacturing elements. Therefore, DCLT_SE communicates with Digital may include executables in the form of a Twin entities, i.e., operation program or agent such as Administration Shell in and management sub- Industrie 4.0. system entity, application 5.3.3.2 Device control sub-entity (DCTR_SE) and service sub-system entity and resource access DCTR interacts with the OME by controlling and and interchange sub-system actuating for device control, therefore may entity, for support of include controller and other actuating devices. generating, synchronizing, Like DCLT_SE, DCTR_SE may include and managing Digital Twins, executables in the form of a program or agent. exactly speaking, digital entities of observable manufacturing elements. Therefore, data collection sub-entity may include executables in the form of a program or agent. Digital Twin shall have one or more data collection sub- entity, because Digital Twin consists of one or more observable manufacturing elements that shall be monitored. 5.3.3.2 Device control sub- entity Device control sub-entity

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 18 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

interacts with the observable manufacturing element by controlling and actuating for device control, therefore may include controller and other actuating devices. Like data collection sub-entity, device control sub-entity may include executables in the form of a program or agent. Digital Twin shall have one or more device control entity, because Digital Twin consists of one or more observable manufacturing elements that shall be controlled. DE 244 For our understanding the asset administration e.g. Acknowledged 06- shell is a DTRE and not a DCDCE. Plattform I4.0 062 does not have an explicit term to refer how to AAS in Industrie 4.0 is a collect and get the data needed from the sources good example to explain [1] describes a specific reference model for a Digital Twin Reference (like DCDCE). It is all part of the asset digital twin called asset administration shell but administration shell. This framework explains how Architecture and it entities. does not distinguish between DTRE and However, there are a lot of (in an architectural point of view) a twin should be DCDCE. built and which functional entities need to be reference models for smart considered. So this is very helpful and manufacturing, therefore it complementary. might be not appropriate to Line 310 pick up AAS only as an With “asset administration shell in detail” example. Plattform Industrie 4.0 provides a specification Remove “such as how a digital modelling FE could be realized in a Administration Shell in harmonized way. Industrie 4.0” https://www.plattform- i40.de/PI40/Redaktion/DE/Downloads/Publikatio n/2018-verwaltungsschale-im-detail.html

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 19 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

KR 261 5.3.5 ed Editorial enhancement Change to read: Accepted in principle 30- 063 As shown in Figure 3, DTUE can be any entity As shown in Figure 3, Digital that can utilize Digital Twin manufacturing such Twin user entity can be any as human, a device, MES/ERP systems, or even entity that can utilize Digital peer DTRE. Twin for manufacturing such as human, a device, MES/ERP systems, or even peer Digital Twin entity.

See US02-010 and FR05- 039. KR 270-271 5.4 Figure 4 te According to KR24, Figure 4 shall be modified. If KR24 is accepted, change Figure 4 as follows: Accepted 31- 064

US 271 5.4.1 Figure 4 te Need explaining the arrows between domains. If not, draw an arrow between OMSE and Accepted 08- OMSE interacting with RAISE passes through RAISE. Please refer fig 1 in the part 4 065 ASSE? KR 275 6.1 ed Editorial enhancement Change to read: Accepted in principle 32- 066 Clause 6 defines functional view and networking This clause defines view of Digital Twin manufacturing based on IoT functional view and reference architecture defined in ISO/IEC 30141. networking view of Digital Twin reference architecture for manufacturing based on

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 20 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

IoT reference architecture defined in ISO/IEC 30141. CN 162, 276 5, 6 te Seeing that IoT reference architecture of ISO/IEC 1. As for part 1 and part 2 of ISO 23247, it is Partly accepted 08- 30141 is a key and unique reference of ISO suggested that using general terms, “Digital 067 23247, the framework, reference models, Twin framework”, “Digital Twin reference Proposal 1 is not accepted reference architecture views of Digital Twin architecture”, “Digital Twin reference models”, because general Digital Twin manufacturing proposed in ISO 23247 are “Digital Twin reference architecture views” as in not the scope of this main topics. supposed to be applicable for not only Digital standard. Twin for manufacturing but any general Digital 2. It is suggested that providing specific Proposal 2 is accepted in Twin. business/stakeholders/system requirement principle, further Technical analysis for Digital Twin Manufacturing from the Reports on use cases will perspective of architecture, representation and information change in part 1 or part 2. cover this proposal. 3. It is suggested that keeping the topics of part Proposal 3 is accepted and 3 and part 4 unchanged focusing the further Technical Reports on representation and information change of use cases will cover specific specific Digital Twin Manufacturing application Digital Twin for scenarios. manufacturing application scenarios KR 278-280 6.2.1 ed Change subclause title and the corresponding Change to read: Accepted 33- text. 6.2.1 Functional reference architecture 068 Figure 5 show a functional reference architecture to support requirements defined in ISO 23247-1. KR 281-283 6.2.1 Figure 5 te According to KR24, Figure 5 shall be modified. If KR24 is accepted, change Figure 5 as follows: Accepted in principle 34- 069 Figure 5 – Functional reference architecture of Digital Twin framework for manufacturing – decomposition of functional entities (FEs)

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 21 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

Figure 5 – Functional reference architecture of Digital Twin manufacturing framework – decomposition of functional entities (FEs) KR 284-287 6.2.2 ed Classification of resource-specific FE is not clear. Change to read: Accepted 35- If it is some function that an entity in OME can 070 perform, it shall be represented by Digital Twin Resource-specific FE is a functional entity of an representation entity so that entities in DCDCE observable manufacturing element. It shall be can utilize that function. digitally modelled to be utilized by entities in Digital Twin manufacturing framework. If not, what else can it be? This shall not be out of scope. KR 289 6.2.3.1 ed According to KR24, it is beneficial to change the Change to read: Accepted in principle 36- title of subclause 6.2.3.1. 6.2.3.1 Data collecting FE in DCLT_SE 071 6.2.3.1 Data collecting FE in data collection sub-entity

See FR05-039. KR 291 6.2.3.2 ed According to KR24, it is beneficial to change the Change to read: Accepted in principle 37- title of subclause 6.2.3.2. 6.2.3.2 Data pre-processing FE in DCLT_SE 072 6.2.3.2 Data pre-processing FE in data collection sub- entity

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 22 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

See FR05-039. KR 294 6.2.3.3 ed According to KR24, it is beneficial to change the Change to read: Accepted in principle 38- title of subclause 6.2.3.3. 6.2.3.3 Controlling FE in DCTR_SE 073 6.2.3.3 Controlling FE in device control sub-entity

See FR05-039. KR 296 6.2.3.4 ed According to KR24, it is beneficial to change the Change to read: Accepted in principle 39- title of subclause 6.2.3.4. 6.2.3.4 Actuation FE in DCTR_SE 074 6.2.3.4 Actuation FE in device control sub-entity

See FR05-039. KR 299 6.2.3.5 ed According to KR24, it is beneficial to change the Change to read: Accepted in principle 40- title of subclause 6.2.3.5. 6.2.3.5 Identification FE in both DCLT_SE and 075 6.2.3.5 Identification FE in DCTR_SE both data collection sub- entity and device control sub- entity

See FR05-039. CN 326 6.2.4.2.4 ge The example “Node.js” is too specific and cannot To delete it or change with another example. Accepted 09- play the exemplification role.

076 “Node.js” will be removed. KR 353-362 6.3.1 ed Change subclause title and editorial Change to read: Accepted in principle 41- enhancement. 6.2.1 Networking reference architecture 6.2.1 Networking reference 077 architecture Networking reference architecture describes communication network which are involved in Networking reference Digital Twin manufacturing framework. architecture describes communication network Figure 6 shows three principal communication which are involved in Digital networks in terms of domain-entity mixture Twin framework for 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 23 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

reference model (see 5.4) in Digital Twin manufacturing. manufacturing framework. Main role of communication network provides means to Figure 6 shows three principal communication exchange information between entities across the different domains. networks in terms of domain- entity mixture reference However, DCDCE is physically attached or model (see 5.4) in Digital integrated into OME, therefore communication Twin framework for network between these two entities is not manufacturing. Main role of considered in this document. communication network provides means to exchange information between entities across the different domains. However, data collection and device control entity is physically attached or integrated into observable manufacturing element, therefore communication network between these two entities is not considered in this document.

See US02-010 and FR05- 039. KR 361-362 6.3.1 Figure 6 te According to KR24, Figure 6 shall be modified. If KR24 is accepted, change Figure 6 and Accepted in principle 42- caption as follows: 078 Figure 6 – Networking reference architecture of Digital Twin framework for manufacturing

See US02-010

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 24 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-11-05 Document: Project: ISO 23247-2

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the secretariat NC1 number Subclause Figure/ comment2 (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

Figure 6 – Networking reference architecture of Digital Twin manufacturing framework KR 366 6.3.2 te Use a consistent term with other parts. Change “physical manufacturing resources” with Accepted 43- “observable manufacturing elements”. 079

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 25 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 ISO/TC 184/SC 4/WG 15 N 107

ISO/TC 184/SC 4/WG 15 Digital manufacturing

Email of convenor: [email protected] Convenorship: ANSI (United States)

ISO CD 23247-3 Collated Comments Final Response LA Document type: Resolution

Date of document: 2019-11-19

Expected action: INFO

Background: For discussion during conference call on 11/20 or 11/21 depending on time zone - 7PM Eastern USA 11/20

Committee URL: https://isotc.iso.org/livelink/livelink/open/tc184sc4wg15 Template for comments and secretariat observations Date:2019-10-04 Document: Project: ISO 23247-3

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/Table comment2 secretariat

DE- 199 ge All OPC UA companion specifications provide a Add paragraph w.r.t. OPC UA Companion Accepted specification for special manufacturing domains. Specifications. 001

DE- 237 ge Mention ISO 13854-42? Extend with: eCl@ss Accepted 002 can be used to define classes and properties for

manufacturing elements

conformant to IEC 61360 and ISO 13854-42 DE- 237 ed eClass eCl@ss (correct typo) Accepted 003

FR ge The documents of the ISO 23247 series circulated Align the project on the NWIP. Accepted in principle 01- as CD do not reflect the outline of the proposed 004 project NWIP (ISO/TC 184/SC 4/WG 15 N 17). Identical to Part 1-003. The intended scope of the project as stated in the Assets are not specifically NWIP was "The Digital Twin is a virtual mentioned, however representation of manufacturing elements such as equipment and facility are personnel,products, assets and process included as types of assets. definitions."

FR ge The documents of the ISO 23247 series circulated Consider the current normative landscape. Resolved 02- as CD do not reflect the outline of the proposed 005 project NWIP (ISO/TC 184/SC 4/WG 15 N 17). Identical to Part1-004. The NWIP standards gap analysis listed and IEC 62264 is informatively summarized: referenced and listed in bibliography of this part. - IEC 62264 Enterprise-control system integration, IEC 62832 and ISO 16400 - IEC 62832 Digital factory framework have been determined not to - ISO 16400 Equipment behaviour catalogues for be referenced in ISO 23247, virtual production system. however they can be listed in These standards are not considered in documents bibliography during DIS of the ISO 23247 series circulated as CD. development if necessary.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial Page 1 of 11 Template for comments and secretariat observations Date:2019-10-04 Document: Project: ISO 23247-3

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/Table comment2 secretariat

FR te Many standards and consortia specifications Analyse the current standards and consortia Acknowledged 03- already specify information for personnel, specifications and provide usefull provisions. 006 equipment, material, processes, facility, Analysis of the current environment and product. standards and consortia specifications are described This document does not provide any requirement in Annex A. on such informartion but only examples. For the requirement, see JP04 (K.D)-008, 2). KR 1 te Update the scope. Change to read: Accepted in principle 01- 007 The scope has been This document defines the attributes of static and improved. dynamic information to represent observable manufacturing elements. JP04 103 1 ge The scope is not consistent with the following 1) Make the scope text consistent with the scope 1) Accepted in principle (K.D)- scope text stated in ISO/TC 184/SC 4 N 3224 text in the NWIP. Scope has been improved. 008 (NWIP). 2) Provide requirements for mapping physical Part 3: Digital representation of physical manufacturing elements into a Digital Twin in See KR01-007. manufacturing elements terms of information structure. Mapping of externally defined manufacturing 2) Accepted elements including product, process and resources definitions with their characteristics to “shall” will be added for provide digital representations for manufacturing requirements in twinning; corresponding text. “Mapping” and “identifying” have different meanings. The original scope in the NWIP implies that the document spefifies requirements for mapping physical manufacturing elements into a Digital Twin, but the scope in CD means only listing types of manufacturing elements to be included in Digital Twins. KR 118-129 4 te Use a consistent term with other parts and update Change to read: Accepted with modification 04- the explanation of Figure 1 Digital Twin is digital representation of observable 009 manufacturing element. Figure 1 shows Digital Twin One of the Digital Twin of observable manufacturing elements (DTME) functions is digital managed by Digital Twin Representation entity representation of observable (DTRE) in Digital Twin manufacturing reference manufacturing element. 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial Page 2 of 11 Template for comments and secretariat observations Date:2019-10-04 Document: Project: ISO 23247-3

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/Table comment2 secretariat

architecture. Figure 1 shows Digital Twin DTME shall consider both static and dynamic of observable manufacturing information. Information fixed to an OME that does elements managed by Digital not change during manufacturing is classified as Twin Entity in Digital Twin static information, whereas information that framework for manufacturing continuously changes during manufacturing is reference architecture. classified as dynamic information. For example, the Digital Twin of observable geographical location of a fixed machine is static manufacturing elements however the amount or the shape of material during shall consider both static and manufacturing processes can be dynamic. dynamic information. For digital modelling of OME, information Information fixed to an associated with OME shall be properly identified by observable manufacturing Digital Modelling FE. element that does not change during manufacturing is classified as static information, whereas information that changes during manufacturing is classified as dynamic information. For example, the serial number of a machine is static. However, the amount or the shape of material during manufacturing processes can be dynamic. For Digital Twin modelling of observable manufacturing elements, information associated with observable manufacturing elements shall be properly identified by Digital Twin Entity. KR 118-all 4 te Change “Physical Manufacturing Element (PME)” Change to read: Accepted 03- and “manufacturing element” as “Observable Observable Manufacturing Element (OME) 010 Manufacturing Element (OME)” to use a consistent term with other parts KR 117 4 te Change clause title Change to read: Accepted 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial Page 3 of 11 Template for comments and secretariat observations Date:2019-10-04 Document: Project: ISO 23247-3

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/Table comment2 secretariat

02- Digital Twin of observable manufacturing element 011

JP05 125 4 ge The following sentence is the only requirement Provide valuable requirements for mapping physical Accepted (K.D)- using “shall” in the document. manufacturing elements into a Digital Twin in terms See JP04 (K.D)-008, 2). 012 For the digital representation of manufacturing of information structure. element, it shall be modelled in terms of information associated with manufacturing elements. KR 130-131 4 Figure 1 ed Change the title of Figure 1 Change to read: Accepted in principle 06- Figure 1 – DTME in Digital Twin manufacturing Figure 1 – Digital Twin of 013 reference architecture Observable Manufacturing

Elements in reference architecture KR 130-131 4 Figure 1 te Update Figure 1 to emphasize to “digital model” Change to read: Accepted in principle 05- and to change “digital model” as “Digital Twin of Digital Twin of observable manufacturing element Figure 1 has redrawn as 014 observable manufacturing element (DTME)” in (DTME) comments. DTRE according to the definition in Part 1

131 4 Figure 1 Ge “Digital Model” in the DTRE frame should be Ensure consistency with CD 23247-1 and -2. Accepted US- consist with CD 23247-1 and -2. 015 See KR05-014.

KR 133 5 ed Change the title of clause 5 to express a digital Change to read: Accepted in principle 07- model. 5 Information for DTME 016 5 Information for Digital Twin of Observable Manufacturing Elements US- 133 5 Te Section 5 does not provide definitions of Complete the section by providing requirements Accepted information for digital representation. All tables are and/or guidance for information for digital 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial Page 4 of 11 Template for comments and secretariat observations Date:2019-10-04 Document: Project: ISO 23247-3

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/Table comment2 secretariat

017 "examples." There are no requirements or representation See JP04 (K.D)-008, 2). guidance in Section 5. The section is incomplete.

SE- 5.1 te The notation of static and dynamic information is Static information is static for a certain period in Accepted with modification 018 confusing, it is obvious that for example time. information like identification of a manufacturing resource is somehow stable over time, but Text has been changed to information is subject for change and that can be meet the requirements of the addressed using for example the concept of comment. effectivity. KR 135-139 5.1 te Use a consistent term with other parts and editorial Change to read: Accepted with modification 09- enhancement As explained in 4, a DTME of an observable 019 manufacturing element shall consider both static As explained in Clause 4, a and dynamic features of information. In this Digital Twin of an observable document, these features are defined as manufacturing element shall information attributes. consider both static and Static information attribute includes identification, dynamic features of characteristics, schedule, and relationship with information. In this other observable manufacturing elements. document, these features Dynamic information attribute includes status, are defined as information location, report, and relationship with other attributes. manufacturing elements. The information attributes Figure 2 shows the attributes of information. described in Figure 2 are examples to illustrate the kinds of information that should be represented for a Digital Twin. Many existing standards such as IEC 62264-2 and ISO 10303 contain detailed information models for these attributes. An implementation of the framework should select the information models most appropriate for its use case. Static information attribute includes identification, characteristics, schedule, 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial Page 5 of 11 Template for comments and secretariat observations Date:2019-10-04 Document: Project: ISO 23247-3

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/Table comment2 secretariat

relationship with other manufacturing elements, and description. Dynamic information attribute includes status, location, report, relationship with other manufacturing elements, and description. KR 134 5.1 ed Change the title of subclauses of 5 to express Change to read: Accepted in principle 08- attribute of information. 5.1 Attributes of information 5.1 Information attributes 020

KR 141 5.1 Figure 2 ed Change the title of Figure 2. Change to read: Accepted in principle 11- Figure 2 – Information attributes for DTME (if KR03 Figure 2 – Information 021 is accepted) attributes for Digital Twin Observable Manufacturing Element KR 140-141 5.1 Figure 2 Te Change the Figure 2 for the clear meaning Change to read: Accepted with modification 10- 022

KR 150 5.2 NOTE 2 ed Use a consistent term with other parts and editorial Change to read: Accepted with 12- enhancement. Various kinds of devices are available to detect 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial Page 6 of 11 Template for comments and secretariat observations Date:2019-10-04 Document: Project: ISO 23247-3

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/Table comment2 secretariat

023 identifier, location, motion, and image of observable modification manufacturing elements. Various kinds of devices are available to detect the identifier, location, motion, and image of observable manufacturing elements. KR 152 5.2 NOTE 3 ed Use a consistent term with other parts and editorial Change to read: Accepted in principle 13- enhancement. Key performance indicator (KPI) including 024 KPI will be replaced by performance and defective rate may be calculated performance. and represented for observable manufacturing elements. See US-025. US- 152 5.2 Table 2 Ed NOTE3: KPI? No definition, or a typo. Define KPI Accepted in principle 025 KPI will be replaced by performance.

KR 165 5.4 Table 5 ed In relationship, material shall be managed by Change to read: Accepted with modification 14- person with Skill #2. Material #1 shall be managed person with Skill #2. 026 Material #1 shall be managed by a person with Skill #2. KR 173 5.5 Table 7 ed In relationship, process shall be managed by Change to read: Accepted with modification 15- person with Skill #3. ManufacturingProcess #1 shall be managed by 027 person with Skill #3. ManufacturingProcess #1 shall be managed by a person with Skill #3. KR 180 5.6 Table 9 ed In relationship, facility hall be managed by person Change to read: Accepted with modification 16- with Skill #3. Facility #1 shall be controlled by person with Skill 028 #3 when the temperature exceeds the limits. Facility #1 shall be controlled by a person with Skill #3 when the temperature exceeds the limits.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial Page 7 of 11 Template for comments and secretariat observations Date:2019-10-04 Document: Project: ISO 23247-3

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/Table comment2 secretariat

JP03( A comment Ge It is very hard to imagine how to effectively use It is recommended to include real-life examples on Resolved A.O)- common to proposed standards, which is a key requirement to how to effectively use proposed standards/ 029 four proposed stimulate manufacturing industry. This standard gives high- documernts level aspect of Digital Twin manufacturing including reference architecture, therefore it is beneficial to show real implementation of Digital Twin manufacturing in further document, for example, additional TR for guidelines for implementing Digital Twin manufacturing. JP02( A comment Ge The title of the series of standards is digital twin Clear statements required. Accepted in principal A.O)- common to manufacturing framework but no manufacturing 030 four proposed specific terms appear. There are many types of Identical to Part 1-003. documernts manufacturing including removal machining for Following has been added to creating automotive dies. introduction for clarification: What types of manufacturing is in scope and what All types of manufacturing types are not shall be clearly described. should be supported including discrete and continuous manufacturing for individual parts, assemblies or continuous processes. However, the actual types of manufacturing that can be supported by an instance of the framework will depend on the technologies selected to implement its functional elements. JP01( A comment Ge To say “Digital Twin”, consistency management Regenerate the document from scratch. Identical to Part 1-006. A.O)- common to between physical objects and their digital 031 four proposed representations shall be a core concern. documernts The Digital Twin framework In other words, how to relate a physical object with for manufacturing describes its digital representation and how to keep framework how to relate consistency between the two in the circumstances physical object to digital where the physical object is constantly changing representation.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial Page 8 of 11 Template for comments and secretariat observations Date:2019-10-04 Document: Project: ISO 23247-3

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/Table comment2 secretariat

shall be a keen concern. Specific technologies that Imagine the case of removal machining for are to be used to perform the creating a die. There are many physical objects synchronization are not including work piece, machining tool, etc. During prescribed by this standard machining, the shape and material characteristics and left by users’ to select. of the work piece will constantly change. It is the Use cases are to be same for the machining tool caused by fatigue. developed in future reports How to capture those changes and how to reflect and they will recommend the changes into their digital counterparts shall be technologies to achieve the a core concern for digital twin manufacturing. qualities described by the framework in the context of But, no specification is defined in the proposed specific processes. four documents concerning how to relate a physical object and its digital representation, and how to keep consistency between the two. The phrases “ detailed modelling” and “dynamic modelling” appear with no clear definitions、which is extremely inappropriate.. There will be changes which can be captured and those which are difficult to capture. Therefore, it is understood that clear statements of in scope issues and out of scope issues should be possible. But, current scope statement says almost nothing. In order to get support from industries, clear answers to the issues raised above is critically important. SE- ANNEX A te Missing reference to relevant ISO 10303 standard ISO 10303-239 specifies an information model that Accepted in principle 032 defines what information can be exchanged and represented to support a product through life. The ISO 10303-239 specifies the modelling scope of AP 239 covers: Histories as well application protocol for as Design, Individuals as well as Designs, Fleets as product life cycle support. well as Individuals, Equipment and Resources as The scope of ISO 10303-239 well as Product, States as well as Faults/Failures, includes information for Schedules and Plans as well as Tasks, Change defining and maintaining a process across all, Allow for Why?, Enable complex product, and feedback & traceability. information required for through life configuration change management of a 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial Page 9 of 11 Template for comments and secretariat observations Date:2019-10-04 Document: Project: ISO 23247-3

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/Table comment2 secretariat

product and its support solution. Also, it includes representation of product assemblies, product through life, specification and planning of activities for a product, the activity history of a product and product history. DE- 229 Annex A ge The asset administration shell is a generic digital Consider adding a paragraph for asset Accepted 033 model for twins. It provides different serializations administration shell. E.g. and mappings. One is for AutomationML , another The asset administration shell is part of the I4.0 for OPC UA. Besides there are also serializations component as introduced in IEC PAS 63088. It for xml, JSON and RDF. (AML, OPC and RDF will provides a technology neutral information model be published in V1.1) and several serializations and mapping. The asset administration shell is one possible concept and specification that can used to implement twins. Serializations and mappings are provided for xml, JSON, RDF, AutomationML and OPC UA. One of its key features is the separation of the digital representation into a set of so-called submodels. Each submodel represents a specific aspect of the asset the twin is representing. US- 246 Annex B Ge “MTConnect Assets” Add reference of MTConnect Accepted 034

US- 62 Introduction Ge Duplicated text from CD 23247-1 is not consistent. Ensure consistency between CD 23247-1 and -3 Accepted in principle 035 Introductions. Introduction has been copied from Part 1.

US- 0 TITLE Ge The title is not clear nor grammatically correct. Change title to, "Automation systems and Accepted 036 integration – Digital twin framework for manufacturing – Part 3: Digital representation of manufacturing elements"

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial Page 10 of 11 Template for comments and secretariat observations Date:2019-10-04 Document: Project: ISO 23247-3

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/Table comment2 secretariat

US- 0 WHOLE Ge See US-01. Change "digital twin manufacturing framework" to Accepted 037 DOCUMENT "digital twin framework for manufacturing" throughout entire document. See US-036.

US- 0 WHOLE Ge "Digital twin manufacturing" is not a defined term. Change to, "Digital twin" throughout entire Accepted in principle 038 DOCUMENT document “Digital twin manufacturing" has been changed to “Digital Twin for manufacturing”. See US-036.

US- 0 WHOLE Ge See CD 23247-1 Comment US-08 to remove Change "digital twin representation" to "digital twin" Accepted 039 DOCUMENT "Digital Twin Representation" throughout entire document See US-036.

ISO/TC 184/SC 4/WG 15 Digital manufacturing

Email of convenor: [email protected] Convenorship: ANSI (United States)

ISO CD 23247-4 Collated Comments Final Response LA Document type: Resolution

Date of document: 2019-11-19

Expected action: INFO

Background: For discussion during conference call on 11/20 or 11/21 depending on time zone - 7PM Eastern USA 11/20

Committee URL: https://isotc.iso.org/livelink/livelink/open/tc184sc4wg15 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

FR ge The documents of the ISO 23247 series Align the project on the NWIP. Identical to Part 1-003. circulated as CD do not reflect the outline of the -001 proposed project NWIP (ISO/TC 184/SC 4/WG Accepted in principle. 15 N 17). The personnel, products, The intended scope of the project as stated in the and process are mentioned NWIP was "The Digital Twin is a virtual in the CD. representation of manufacturing elements such as personnel, products, assets and process Assets are not specifically definitions." mentioned;

however, equipment and facility are included as types of assets.

FR ge The documents of the ISO 23247 series Consider the current normative landscape. Identical to Part 1-004. circulated as CD do not reflect the outline of the -002 proposed project NWIP (ISO/TC 184/SC 4/WG Acknowledged. 15 N 17). IEC 62264 is informatively referenced and listed in The NWIP standards gap analysis listed and bibliography of Part 3. summarized: IEC 62832 and ISO 16400 - IEC 62264 Enterprise-control system have been determined not integration, to be referenced in ISO 23247, however they can - IEC 62832 Digital factory framework be listed in bibliography during DIS development if - ISO 16400 Equipment behaviour catalogues for necessary. virtual production system.

These standards are not considered in documents of the ISO 23247 series circulated as CD.

FR ge These considerations are irrelevant at the Leave these considerations to industrial network Acknowledged

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 1 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

information level of ISO/TC 184/SC 4 where there standards bodies such IEC/SC 65C. -003 is no expertise in this field. This document identifies technical requirements on information exchange to support digital twin for manufacturing.

It does not define any communication protocols.

This scope is within SC 4.

US 0 TITLE Ge The title is not clear nor grammatically correct. Change title to, "Automation systems and Identical to Part 1-001. integration – Digital twin framework for -004 manufacturing – Part 4: Information exchange" Accepted

To be updated during DIS ballot process

“Digital Twin framework for manufacturing”

US 0 WHOLE Ge See CD 23247-1 Comment US-08 to remove Change "digital twin representation" to "digital Identical to Part 2-010. DOCUMEN "Digital Twin Representation" twin" throughout entire document -005 T Accepted

US 0 WHOLE Ge "Digital twin manufacturing" is not a defined term. Change to, "Digital twin" throughout entire Identical to Part 2-011. DOCUMEN document -006 T Accepted in principle

Changed to “Digital Twin for manufacturing”.

See US-004

US 0 WHOLE Ge See US-01. Change "digital twin manufacturing framework" to Identical to Part 2-012. DOCUMEN "digital twin framework for manufacturing" Accepted in principle -007 T throughout entire document.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 2 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

Changed to “Digital Twin framework for manufacturing”

JP0 A comment Ge To say “Digital Twin”, consistency management Regenerate the document from scratch. Identical to Part 1-006. 1(A. common to between physical objects and their digital Accepted in principle O) four representations shall be a core concern. proposed The Digital Twin framework -008 documernts In other words, how to relate a physical object for manufacturing with its digital representation and how to keep describes framework how consistency between the two in the to relate physical object to circumstances where the physical object is digital representation. constantly changing shall be a keen concern. Specific technologies that Imagine the case of removal machining for are to be used to perform creating a die. There are many physical objects the synchronization are not including work piece, machining tool, etc. During prescribed by this standard machining, the shape and material characteristics and left by users to select. of the work piece will constantly change. It is the same for the machining tool caused by fatigue. Use cases are to be developed in future reports How to capture those changes and how to reflect and they will recommend the changes into their digital counterparts shall be technologies to achieve the a core concern for digital twin manufacturing. qualities described by the framework in the context of But, no specification is defined in the proposed specific processes. four documents concerning how to relate a physical object and its digital representation, and how to keep consistency between the two.

The phrases “ detailed modelling” and “dynamic modelling” appear with no clear definitions 、 which is extremely inappropriate..

There will be changes which can be captured and those which are difficult to capture.

Therefore, it is understood that clear statements

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 3 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

of in scope issues and out of scope issues should be possible. But, current scope statement says almost nothing.

In order to get support from industries, clear answers to the issues raised above is critically important.

JP0 A comment Ge The title of the series of standards is digital twin Clear statements required. Identical to Part 1-007. 2(A. common to manufacturing framework but no manufacturing O) four specific terms appear. There are many types of Accepted in principle proposed manufacturing including removal machining for Following has been added -009 documernts creating automotive dies. to introduction for clarification: What types of manufacturing is in scope and what types are not shall be clearly described. All types of manufacturing should be supported including discrete and continuous manufacturing for individual parts, assemblies or continuous processes. However, the actual types of manufacturing that can be supported by an instance of the framework will depend on the technologies selected to implement its functional elements.

JP0 A comment Ge It is very hard to imagine how to effectively use It is recommended to include real-life examples on Identical to Part 1-008. 3(A. common to proposed standards, which is a key requirement how to effectively use proposed standards/ Accepted in principle O) four to stimulate manufacturing industry. proposed Following has been added -010 documernts to introduction for clarification: All types of manufacturing should be supported including discrete and 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 4 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

continuous manufacturing for individual parts, assemblies or continuous processes. However, the actual types of manufacturing that can be supported by an instance of the framework will depend on the technologies selected to implement its functional elements. Technical Reports will follow on use cases.

JP 125 1 ge “information exchange within the Digital Twin Make the scope text consistent with the scope text Accepted 04 manufacturing framework” sounds strange, in the NWIP, by replacing “within the Digital Twin (K.D because “Digital Twin manufacturing framework” manufacturing framework” with “between entities Changes have been made ) is defined as “conceptual guidelines to support of the Digital Twin manufacturing reference to the scope of Part 4. implementation of Digital Twin in manufacturing”. model”. -011 Information exchange within conceptual gudelines doesn‟t make sence.

ISO/TC 184/SC 4 N 3224 (NWIP) states as follows.

Part 4: Information exchange

Identifies technologies such as network protocols, APIs, description languages, etc., for information synchronization, exchange and management of digitally represented manufacturing twins.

The document seems specifying requirements for information exchange:

between Digital Twin User Entity (DTUE) and Digital Twin Representation Entity (DTRE)

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 5 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

among three sub-system entities within the DTRE

between the DTRE and Data Collection and Device Control Entity (DCDCE)

between DCDCE and Physical Manufacturing Element (PME)

JP 125 1 ge Specifying requirements for exchanging Acknowledged 05 information between functions like entities of the (K.D Digital Twin manufacturing reference model This document is to identify ) seems out of scope of ISO TC184/SC4, but it technical requirements on seems under scope of ISO TC184/SC5 which is information exchange to -012 titled with “Interoperability, integration, and support digital twin for architectures for enterprise systems and manufacturing. automation applications”. The current scope is within SC 4.

Also, it is better to develop framework series in single standard organization to alignment, management of the framework series.

Any requirements identified should be addressed by ISO TC184/SC 5.

JP 140 ge There is no requirement that is stated with “shall” Accepted 06 in the document. (K.D The “shall” be added to the ) requirements that can be changed as appropriate -013

CN 1 TE The overall feeling is that the standard is Accepted in principle conceptual and framed, and we should refine the

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 6 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

content to support the application. -014 Use cases for Digital Twin framework for manufacturing are to be developed in future technical reports and they will recommend technologies to support application.

CN 4 TE Add information interaction requirements for Accepted in principle network Bandwidth -015 Requirements for bandwidth are application dependent.

Bandwidth will be addressed by the use cases documented in the technical reports.

CN 4 TE Add information interaction requirements for Accepted in principle network Mobility -016 Requirements for mobility are application dependent.

Mobility will be addressed by the use cases documented in the technical reports.

US 86 Introduction Ge Duplicated text from CD 23247-1 is not Ensure consistency between CD 23247-1 and -4 Identical to Part 2-014. consistent. Introductions. -017 Accepted.

Introduction is changed to align with part 1.

KR 96, 105 Introduction ed Use a consistent term with other parts. Change “physical manufacturing elements” with Accepted in principle.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 7 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

01 “observable manufacturing elements”. Introduction is changed to -018 align with part 1.

See US-017 for this comment.

KR 141-143 4 te This document defines information exchange in Change to read: Accepted in principle. 02 entity-based Digital Twin manufacturing reference Digital Twin manufacturing model. So, “functional view for the Digital Twin ISO 23247-2 defines a functional view of Digital has been changed to -019 manufacturing reference architecture” is incorrect. Twin manufacturing reference model. Each Digital Twin for entities and observable manufacturing elements in manufacturing (US-007). the reference model are peers of information exchange. This document specifies four types of information exchange between entities and observable manufacturing element as shown in Figure 1. In addition, this document defines requirements for each type of information exchange that the functional entities should provide.

DE 144 ge Why is there no interface between two DTRE? Please clarify Acknowledged

-020 Peer DT is one of the users (DTUE) of DTRE.

Communication between DTREs are made through IE-A. Thus, there is no need for separate interface between DTREs.

KR 144 4 Figure 1 te ISO 23247-1 use OME, not PME. Use a Change “Physical Manufacturing Element (PME)” Accepted 03 consistent term with ISO 23247-1. with “Observable Manufacturing Element (OME)”.

-021

KR 144 4 Figure 1 te ISO 23247-2 use presentation FE, not Change to “presentation FE”. Accepted 04 visualization FE

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 8 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

-022

KR 144 4 Figure 1 te If ISO 23247-2‟s CD comment KR-24 (Figure 3) is Change Figure 1 as follows. Accepted in principle 05 accepted, change DCDCE with 2 sub-entities. DTRE has been changed -023 to Digital Twin entity (US- 005).

Also, IE-B has been changed to IE-B1, IE-B2, IE-B3(DE-024).

DE 149 IE-B Either the three subsystems are really different, Please clarify Accepted in principle then why is the interface between ASSE and -024 OMSE the same as between ASSE and RAISE? 1. The interface between OMSE is not allowed to communicate with ASSE and OMSE and RAISE? interface between ASSE and RAISE are same in terms of its usage for exchanging information for providing digital twin services.

If there is a need to differentiate IE-Bs, it is possible to use IE-B1, IE- B2, IE-B3, as shown in the figure.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 9 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

If the figure is agreed, Figure 1, Figure 3, and description of IE-B will be changed.

2. Please make a note of the line (IE-B) between OMSE and RAISE.

Note, DTRE has been changed to Digital Twin entity (US-005).

KR 155-156 4 te Use a consistent term with other parts. Change “Physical Manufacturing Element (PME)” Accepted 06 with “Observable Manufacturing Element (OME)”.

-025

DE 160 5.1 ge Typo Through Accepted

-026

KR 160-161 5.1 ed Editorial correction and enhancement. Change to read: Accepted 07 The IE-A is an interface between DTUE and -027 DTRE, in which DTUE uses services and applications provided by OMSE, ASSE and RAISE as shown in Figure 2.

CN 5.2 TE should specify the method for data exchange Accepted in principle

-028 Method for data exchange is application dependent.

Use cases for Digital Twin framework for manufacturing are to be developed in future

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 10 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

technical reports and they will recommend technologies to specify the method for data exchange.

DE 187ff IE-B Very difficult to understand because OMSE, Explain shortly tasks of MSE, ASSE and RAISE Accepted. ASSE and RAISE were not yet mentioned before -029 (only in part 3) OMSE, ASSE, and RAISE are defined in ISO 23247-2. However, for better understanding of this document, short description will be added.

KR 190-191 6.1 ed Editorial correction and enhancement. Change to read: Accepted in principle 08 Through IE-B, OMSE, ASSE, and RAISE Digital Twin manufacturing -030 exchange information for the DTRE to provide has been changed to Digital Twin manufacturing services as shown in Digital Twin for Figure 3. manufacturing (US-007).

Also, DTRE has been changed to Digital Twin entity (US-005).

KR 192 6.1 Figure 3 ed ISO 23247-2 use presentation FE, not Change to “presentation FE”. Accepted. 09 visualization FE

-031

KR 197-199 6.2 NOTE ed Use a consistent term with other parts. Change to read: Accepted in principle. 10 Editorial enhancement. NOTE Through IE-C, DTRE collects data from DTRE has been changed -032 observable manufacturing elements. DTRE may to Digital Twin entity (US- use artificial intelligence to analyse the collected 005). data. Based on data analytics, DTRE can reproduce the past, diagnose the present, and plan for the future.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 11 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

KR 208-209 7.1 ed Use a consistent term with other parts. Change to read: Accepted in principle. 11 Editorial correction and enhancement. The IE-C is an interface between DTRE and DTRE has been changed -033 DCDCE, in which the DTRE collects information to Digital Twin entity (US- from observable manufacturing elements and 005). controls devices in observable manufacturing elements as shown in Figure 4.

KR 210-211 7.1 NOTE 1 te Use a consistent term with other parts. Change to read: Accepted in principle. 12 Editorial correction and enhancement. NOTE 1 DCDCE interacts with OME(s). DCDCE DTRE has been changed -034 monitors, senses, and in some cases, DCDCE to Digital Twin entity (US- performs actuation on OME(s) or controls OME(s). 005). DTRE uses DCDCE as a mediator to retrieve information of the OME(s) or to control OME(s).

KR 212-213 7.1 NOTE 2 ed Editorial correction and enhancement. Change to read: Accepted in principle. 13 NOTE 2 Annex A.4 shows some examples on DTRE has been changed -035 how the DTRE and DCDCE are configured using to Digital Twin entity (US- various protocols for collecting and controlling 005). data.

KR 214 7.1 Figure 4 te If ISO 23247-3‟s CD comment KR-04 (Figure 1) is Change Figure 4 to align with ISO 23247-3. Accepted in principle. 14 accepted, add DTME to DTRE. DTRE has been changed -036 The reason is, clause 7.5 talks about digital to Digital Twin entity (US- model which is related to DTME. This part should 005). describe the use of DTME, especially in clause 7.5

Also add description as follows.

The DTRE maintains Digital Twin of observable manufacturing element (DTME) which is defined in

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 12 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

ISO 23247-3.

KR 216-222 7.2 NOTE ed Editorial correction and enhancement. Change to read: Accepted in principle. 15 NOTE Multiple devices (including sensors, DTRE has been changed -037 manufacturing elements) will be participating in to Digital Twin entity (US- the Digital Twin services. The devices can be 005). connected and disconnected any time during the Digital Twin services. Since a device are controlled by the DCDCE, DTRE will need to handle the join/leave activities of the multiple DCDCEs with plug-and-play support.

DE 220 DTRE Does DTRE describe 1 Twin or the handling of all Please clarify Acknowledged twins of a system? -038 ISO 23247-2 describes the details of DTRE supporting a large number of twins.

Clause 7.7 describes synchronization of multiple twins which implies handling of multiple twins.

DTRE can support multiple digital twin instances. For example, one DTRE can handle one or more twins.

Note, DTRE has been changed to Digital Twin entity (US-005).

CN 7.3 TE If we ca give specific method exchanging data Accepted in principle

-039 Method for exchanging data is application dependent.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 13 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

Use cases for Digital Twin framework for manufacturing are to be developed in future technical reports and they will recommend technologies to specify the method on exchanging data.

KR 225 7.3 te Use a consistent term with other parts. Change PME with OME. Accepted. 16

-040

KR 229 7.4 te Use a consistent term with other parts. Change “manufacturing element” with “observable Accepted. 17 manufacturing element”.

-041

KR 230-233 7.4 NOTE te Use a consistent term with other parts. Change to read: Accepted in principle. 18 Editorial correction and enhancement regarding NOTE There can be Digital Twin for multiple DTRE has been changed -042 KR-14. observable manufacturing elements in the DTRE. to Digital Twin entity (US- There should be an identification scheme to map 005). the observable manufacturing elements with the corresponding Digital Twin. In some cases, the sensors or the actuators are not represented by the Digital Twin, however, they need to provide sensing data or actuation results to the DTRE. For this reason, DTRE will need to identify the sensors and the actuators of observable manufacturing elements.

KR 235 7.5 te Relationship of digital model and digital twin is not Add sentence. Accepted 19 clear. The DTME is generated from digital model -043 through synchronization with observable

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 14 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

manufacturing elements.

KR 236 7.5 te Use a consistent term with other parts. Change “manufacturing element” with “observable Accepted 20 manufacturing element”.

-044

CN 7.7 TE About "Synchronization", Whether the certainty of Accepted in principle. information exchange can be added to the -045 requirements The certainty of information exchange is dependent on the use case/application.

Use cases for Digital Twin framework for manufacturing are to be developed in future technical reports and they will recommend technologies to specify the requirement for the certainty of information exchange.

DE 247 7.7 ge spelling and grammar Can consist Accepted

-046

KR 247-249 7.7 NOTE ed Editorial enhancement. Change to read: Accepted 21 NOTE Multiple devices such as production line -047 can consists of multiple Digital Twins. A change in Digital Twin of a single device can have effect on the other related Digital Twin.

KR 250, 252 7.7 te Use a consistent term with other parts. Change “manufacturing element” with “observable Accepted 22 manufacturing element”.

-048

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 15 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

KR 255-258 7.8 te Use a consistent term with other parts. Change “manufacturing element” with “observable Accepted 23 manufacturing element”.

-049

DE 260 7.8 ge spelling and grammar Should provide methods or should provide a Accepted method -050 “should provide a method”

CN 7.10 TE About "Near-real time communication",Whether Accepted in principle the requirements can be further specified -051 The requirements for near- real time communication is dependent on the use case/applications.

KR 282, 7.11 te Use a consistent term with other parts. Change “manufacturing element” with “observable Accepted 24 285, manufacturing element”. 292, 293 -052

DE 261 7.11 ge spelling and grammar Data generated from manufacturing elements and Accepted various IoT devices is private -053

DE 295 7.11 ge spelling and grammar Provide methods Accepted

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 16 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

-054

KR 299-301 8.1 ed Use a consistent term with other parts. Change to read: Accepted in principle 25 Editorial correction and enhancement. The IE-D is an interface between DCDCE and DTRE has been changed -055 OME. The IE-D may not be necessary, if the OME to Digital Twin entity (US- supports direct interface with DTRE by physically 005). attached or integrated DCDCE to the OME.

KR 302 8.1 Figure 5 te Use a consistent term with other parts. Change Figure 5 as follows Accepted 26

-056

DE 307 8.2 ge spelling and grammar Many manufacturing equipments Not accepted

-057 There is no plural form for equipment.

DE 309 8.2 ge spelling and grammar Many factories establish a local network Accepted

-058

KR 313-314 8.3 te Use a consistent term with other parts. Change PME with OME. Accepted 27

-059

DE 315 8.3 ge spelling and grammar Normally, DCDCE have an interface to the … Accepted

-060

DE 316 8.3 ge spelling and grammar Data from the local network to data that is Accepted understood …

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 17 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

-061

DE 317 8.3 ge Spelling and grammar Before delivering it to … Accepted

-062

DE 318 8.3 ge Spelling and grammar Delivering it … Accepted

-063

US 324 A.1 Ed Missing “MTConnect” in Acronyms of protocols Add MTConnect in the section Accepted

-064

DE 366 Asset administration shell (AAS) supports Add administration shell to DTRE because it Accepted. different deployment scenarios and serializations. defines payload for IE-A -065 Main concern is DTRE. AAS can be deployed on Administration shell (AAS) PME and it can be realized with OPC UA: so this is added to Digital Twin is fine as well. entity.

KR 366 A.2 Figure A.1 te Use a consistent term with other parts. Change PME with OME. Accepted 28

-066

DE 370 A.2.1 ge Spelling and grammar Standardized methods for data exchange, DTRE Accepted in principle can provide web services for the … -067 DTRE has been changed to Digital Twin entity (US- 005).

DE 371 A.2.1 ge Spelling and grammar Through a web interface Accepted

-068

DE 374 The asset administration shell (AAS) provides Mention AAS as example how to implement IE-A Accepted. serilaizations in JSON, XML and (in work) RDF. -069 (in Work): REST-API - So AAS is an example Text for implantation option 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 18 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

how to implement IE-A for AAS in IE-A will be added.

SC4/WG 15 will Contact DE to ask for help.

KR 395 A.2.3 te Use a consistent term with other parts. Change manufacturing elements with OME. Accepted 29

-070

KR 397 A.2.3 te Use a consistent term with other parts. Change PME with OME. Accepted 30

-071

KR 404 A.2.3 te The description is not an example of identification Change “Regarding Identification” to “Regarding Accepted (7.4). It is example to digital model (7.5). digital model” -072

KR 404-405 A.2.3 te Use a consistent term with other parts. Change PME with OME. Accepted 31

-073

KR 404 A.2.3 te There are many standards that can be used as a Add description as follows. Accepted reference for identification. Add description for -074 identification. there are many standards such as ISO 22745, IEC 61360, IEC 61987, ITU-T X.660 | ISO/IEC 9834-1, ITU-T X.667 | ISO/IEC 9834-8, IETF STD 66 that can be used as a reference for identification scheme of OME. ISO 22745 (i.e., OTD) defines database of concepts with associated terms, definitions and images used for description of individuals, organizations, locations, goods, services, processes, rules and regulations. IEC 61360 (i.e., CDD) defines data model to be used for providing classifications and metadata

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 19 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

definitions for describing products. The CDD for process automation equipment are defined in IEC 61987. ITU-T X.660 | ISO/IEC 9834-1 (i.e., OID) defines identification mechanism for naming any type of object, concept or „thing‟ with globally unique name. ITU-T X.667 | ISO/IEC 9834-8 (i.e., UUID) defines identification mechanism using 128-bit number generated by algorithm with values that are based on a machine‟s network address to uniquely identify object or entity on the Internet. IETF STD 66 (i.e., URI) is defines identification mechanism with string of characters used to unambiguously indentify a logical or physical resources on the network, of which the best known type is web address (e.g. http://);

Also, add reference to

ISO 22745, IEC 62832, IEC 61360, IEC 61987, ITU-T X.660 | ISO/IEC 9834-1, ITU-T X.667 | ISO/IEC 9834-8, and IETF STD 66

Also, add abbreviation in A.1 as follows.

CDD, OID, OTD, UUID, URI,

US 407 A.2.3 Te “To support presentation and visualization, Add related standard of presentation and Accepted in principle CAD/CAM information”. The paragraph only visualization, -075 descripted “CAD/CAM information”, didn‟t Text for implantation option mention presentation and visualization such as for presentation (IE-B) and JT ,3DPDF,3D rendering… visualization (IE-A) will be added.

Project leaders and the SC 4/WG 15 meeting will further study on how to 1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 20 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

handle the description of JT, 3DPDF, 3D rendering.

KR 408 A.2.3 te Use a consistent term with other parts. Change “manufacturing element(s)” with Accepted 32 “observable manufacturing element”.

-076

KR 420 A.2.3 te Regarding applying manufacturing information, Add description as follows. Accepted 33 ISO 16100 series and ISO 18828 series can also be reference. Add description on how those The ISO 16100 series can also be considered, -077 standards can be referenced. since it defines manufacturing information model that characterizes software-interfacing requirements enabling the interoperability among manufacturing software tools (modules or systems). The ISO 18828 series defines seamless production planning. It can be used as a reference for exchanging information regarding changes of production planning.

Also, add reference to

ISO16100 series, ISO 18828 series

US 421 A.2.3 Te ISO 23952 (i.e., QIF) should not be an example Data ISO 23952 (i.e., QIF) should be an example Accepted. of IE-C of IE-A or IE-B -078 QIF will be added to IE-B, and removed from IE-C.

US 425 A.2.3 Ge “To provide graphical information, it is possible to Remove the text. Accepted in principle. use API such as WebGL, OpenGL. WebGL is a -079 JavaScript API for rendering 2D/3D graphics. The text “To provide OpenGL is an API for rendering 2D/3D graphics” graphical information, it is does not belong in this paragraph. possible to use API such as WebGL, OpenGL. WebGL is a JavaScript API for rendering 2D/3D graphics.

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 21 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

OpenGL is an API for rendering 2D/3D graphics” belongs to IE-A, so it will be moved to IE-A.

KR 441-445 A.2.4 te Use a consistent term with other parts. Change PME with OME. Accepted 34

-080

US 444 A.2.4 Te Ethernet/IP is widely used open Industrial Change to, "...protocol (e.g., CFX, EtherCAT, Accepted Ethernet protocol. Ethernet/IP, Profinet, Modbus, RAPIENet);" -081

KR 454 A.3 Figure A.2 te Use a consistent term (PME->OME)with other Change Figure A.2 as follows Accepted in principle 35 parts. DTRE has been changed -082 For enhancement, add role of applications (ERP, to Digital Twin entity (US- MES, UI. Etc.) in the arrow. 005).

Add legend to ERP, MES, UI).

Sensors/actuators in DCDCE are also a part of OME, so, figure is incorrect. Use OMEs of different types for better understanding.

Relationship between digital twin in DTRE and OME are not clear, and is difficult to map different types of digital twin with the description. It is better to add identifiers for digital twin.

KR 458-468 A.3 te Change description to align with figure A.2 Change to read: Accepted in principle 36 - Digital Twin can be a twinning of application DTRE has been changed -083 using source data from various manufacturing to Digital Twin entity (US- application (i.e., process) such as UI, MES, ERP 005). as shown in example1 of Figure A.2. Application (e.g., UI, MES, ERP) can be the user of DTUE and the OME (provider of source data). For

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 22 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

application acting as a user of DTUE, application can utilize results from the DTRE for planning and analysis. Application acting as an OME provides data regarding manufacturing process such as product planning, manufacturing execution, quality test results;

- Digital Twin can be twinning of manufacturing operations as shown in example2 of Figure A.2. It combines data from various OMEs such as process, personnel, equipment, environment, product, etc. DTRE needs to carefully maintain consistency on data received from multiple OMEs by observing and coordinating data with regards to time, location, action, condition, state, etc.;

- Digital Twin can be twinning of single device of OME as shown in example3 of Figure A.3. It can also use data from the environment (e.g., sensors) for more accurate presentation of the Digital Twin;

- Digital Twin can be twinning of trends or check- list as shown in example4 of Figure A.3. It can use data from environment (e.g., sensors).

KR 470-472 A.4 te Use a consistent term with other parts. Change PME with OME. Accepted 37

-084

DE 441, 396 Administration shell is no protocol, it offers a The Asset Administration is designed for Accepted. technology neutral metamodel + API plus implementing IE-A: applications should access -085 different serializations in xml, JSON, rdf (in work), information from twins and not directly from the Will remove AAS in Figure AutomationML and OPC UA and (in work) asset it is representing. A.3 and Figure A.4.

The first API that will be realized is the REST- In Plattform I4.0 different deployment scenarios API. are distinguished. One scenario is that the twin is deployed directly on the physical device. As is described in this case IE-D is not needed. In this

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 23 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

case the asset administration shell can be realized as an OPC UA server using the OPC UA Companions Specification for Asset Administration Shell (in work). However, other serializations of the asset administration shell like the one with JSON and REST would be used for IE-A and not for IE-C!!

The asset administration shell is not distinguishing between IE-D and IE-C. In general there it is no standardized or preferred way described for asset administration shell how to access the data from the asset.

KR 474-475 A.4 Figure A.3 te Use a consistent term with other parts. Change PME with OME. Accepted 38

-086

KR 478 A.4 Figure A.4 te Use a consistent term with other parts. Change PME with OME. Accepted 39

-087

DE 480 Bibliography Since asset administration shell is mentioned Add references to asset administration shell Accepted corresponding references should be added documents, e.g. link of online-library or single -088 documents

https://www.plattform- i40.de/PI40/Navigation/EN/InPractice/Online- Library/online-library.html

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 24 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 Template for comments and secretariat observations Date: 2019-08-14 Document: TC184-SC4_N3379 Project: ISO 23247-4

MB/ Line Clause/ Paragraph/ Type of Comments Proposed change Observations of the NC1 number Subclause Figure/ comment2 secretariat (e.g. 17) (e.g. 3.1) Table/ (e.g. Table 1)

1 MB = Member body / NC = National Committee (enter the ISO 3166 two-letter country code, e.g. CN for China; comments from the ISO/CS editing unit are identified by **) 2 Type of comment: ge = general te = technical ed = editorial page 25 of 25 ISO/IEC/CEN/CENELEC electronic balloting commenting template/version 2012-03 ISO/TC 184/SC 4/WG 15 N 109

ISO/TC 184/SC 4/WG 15 Digital manufacturing

Email of convenor: [email protected] Convenorship: ANSI (United States)

Text for ISO DIS 23247-1 Ballot r1 Document type: Committee draft

Date of document: 2019-11-19

Expected action: INFO

Background: For discussion during conference call on 11/20 or 11/21 depending on time zone - 7PM Eastern USA 11/20

ISO CD 23247-1:2019(E)

ISO TC 184/SC 4/WG 15

Secretariat: ANSI

Automation systems and integration – Digital Twin framework for manufacturing – Part 1: Overview and general principles

CD stage

To help you, this guide on writing standards was produced by the ISO/TMB and is available at https://www.iso.org/iso/how-to-write-standards.pdf

A model manuscript of a draft International Standard (known as “The Rice Model”) is available at https://www.iso.org/iso/model_document-rice_model.pdf

ISO CD 23247-1:2019(E)

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 Email: [email protected] Website: www.iso.org

Published in Switzerland

Contents

1 Foreword ...... v 2 Introduction...... vi 3 1 Scope ...... 1 4 2 Normative references ...... 2 5 3 Terms and definitions ...... 2 6 3.1 General terms ...... 2 7 3.1.1 actuator ...... 2 8 3.1.2 area ...... 2 9 3.1.3 control ...... 2 10 3.1.4 element ...... 2 11 3.1.5 enterprise ...... 2 12 3.1.6 entity ...... 3 13 3.1.7 Internet of Things IoT ...... 3 14 3.1.8 management ...... 3 15 3.1.9 physical element ...... 3 16 3.1.10 resource ...... 3 17 3.1.11 sensor ...... 3 18 3.1.12 task ...... 4 19 3.2 Digital Twin manufacturing specific terms ...... 4 20 3.2.1 digital entity ...... 4 21 3.2.2 digital model digital representation ...... Error! Bookmark not defined. 22 3.2.3 digital modelling ...... Error! Bookmark not defined. 23 3.2.4 Digital Twin ...... 4 24 3.2.5 Digital Twin manufacturing framework ...... Error! Bookmark not defined. 25 3.2.6 Digital Twin Representation ...... Error! Bookmark not defined. 26 3.2.7 manufacturing process ...... 4 27 3.2.8 presentation ...... 5 28 3.2.9 visualization ...... 5 29 3.2.10 view/viewpoint ...... 5 30 3.3 Abbreviated terms ...... 5 31 4 Overview of Digital Twin manufacturing ...... 6 32 4.1 The concept of Digital Twin ...... 6 33 4.2 Digital Twin manufacturing ...... 6 34 4.3 Applications and services of Digital Twin manufacturing ...... 7 35 4.3.1 Real time control ...... 7 36 4.3.2 Off-line analytics ...... 7 37 4.3.3 Predictive maintenance ...... 7 38 4.3.4 Health check ...... 7 39 4.4 Benefits of Digital Twin manufacturing ...... 7 40 4.4.1 In-loop planning and validation ...... 7 41 4.4.2 Production scheduling assurance ...... 7 42 4.4.3 Enhanced understanding of manufacturing elements...... 8 43 4.4.4 Dynamic risk management ...... 8 44 4.4.5 Cost reduction ...... 8 45 4.5 Elements of Digital Twin manufacturing ...... 8 46 4.5.1 Observable manufacturing elements ...... 8 47 4.5.2 Digital entities ...... 9 48 5 General principles of Digital Twin manufacturing framework ...... 10 49 5.1 Overview ...... 10

50 5.2 Scope of Digital Twin manufacturing framework standardization ...... 10 51 5.2.1 Limitations and boundaries ...... 10 52 5.3 Hierarchical modelling of Digital Twin manufacturing ...... Error! Bookmark not defined. 53 5.4 Requirements of Digital Twin manufacturing ...... 11 54 5.4.1 General requirements ...... 11 55 5.4.2 Digital modelling requirements ...... 11 56 5.4.3 Information exchange requirements ...... 12 57 Bibliography ...... 13

Foreword

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

This document was prepared by Technical Committee ISO/TC 184, 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.

58 Introduction

62 The scope of the four parts of this series are defined below:

63 - Part 1: Overview and general principles

64 Provides an overview of Digital Twin for manufacturing, describes general principles, and 65 provides requirements and guidance for developing a Digital Twin framework for 66 manufacturing;

67 - Part 2: Reference architecture

68 Provides a reference architecture goals and objectives, reference model, and reference 69 architectural views for a Digital Twin framework for manufacturing

70 - Part 3: Digital representation of manufacturing elements

71 Identifies manufacturing elements of the Digital Twin framework for manufacturing that shall 72 be represented in digital models;

73 - Part 4: Information exchange

74 Identifies technical requirements for information synchronization and information exchange 75 within the Digital Twin framework for manufacturing.

76 The types of manufacturing that can be supported by an implementation of the framework will depend 77 on the technologies selected to implement its functional elements.

78 Use cases for Digital Twin framework for manufacturing will be detailed in a series of technical reports 79 attached to this series.

1 Automation systems and integration – Digital Twin framework for 2 manufacturing – Part 1: Overview and general principles

3 1 Scope

4 This part of ISO 23247 provides an overview and general principles of Digital Twin for manufacturing.

8 The following are within the scope of this part of ISO 23247;

9 - scope statement for ISO 23247 as a whole;

10 - overview of ISO 23247;

11 - structure of ISO 23247;

12 - terms and definitions used throughout ISO 23247;

13 - overview of Digital Twin framework for manufacturing;

14 - requirements of Digital Twin for manufacturing.

15 The following are described in other parts of ISO 23247;

16 - reference architecture of the Digital Twin framework for manufacturing (Part 2);

17 - digital representation of manufacturing elements of the Digital Twin framework for

18 manufacturing (Part 3);

19 - information exchange of the Digital Twin framework for manufacturing (Part 4);

20 - use cases of the Digital Twin framework for manufacturing are to be detailed in technical

21 reports.

22 The following are outside of the scope of ISO 23247;

23 - selection of the implementation methods and technologies for a Digital Twin for manufacturing;

24 - selection of the communication protocols for a Digital Twin for manufacturing;

25 - selection of the manufacturing devices and other resources to be represented by a Digital Twin;

26 - selection of the manufacturing processes to be represented by a Digital Twin;

27 - selection of the manufacturing products to be represented by a Digital Twin;

28 - design and process planning, and other non-manufacturing stages of the product lifecycle.

29 2 Normative references

30 There are no normative references in this document.

31 3 Terms and definitions

32 For the purposes of this document, the following terms and definitions apply.

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

34 — ISO Online browsing platform: available at https://www.iso.org/obp

35 — IEC Electropedia: available at http://www.electropedia.org/

36 3.1 General terms

37 3.1.1 38 actuator

39 device that provides a physical output in response to an input signal in a predetermined way

40 [SOURCE: ISO/IEC 29182‑ 2]

41 3.1.2 42 area

43 physical, geographical or logical grouping of resources determined by the site

44 [SOURCE: IEC 62264-1:2013]

45 3.1.3 46 control

47 purposeful action on or in a process to meet specified objectives

48 [SOURCE: IEV 351-42-19]

49 3.1.4 50 element

51 basic system part that has the characteristics of state, behaviour, and identification

52 [SOURCE: ISO 14258:1998, 2.2.4]

53 3.1.5 54 enterprise

55 one or more organizations sharing a definite mission, goals and objectives which provides an output 56 such as a product or service

57 [SOURCE: IEC 62264-1:2013]

58 3.1.6 59 entity

60 thing (physical or non-physical) having a distinct existence

61 [SOURCE: ISO/IEC 15459-3:2014, 3.1]

62 3.1.7 63 Internet of Things 64 IoT

65 infrastructure of interconnected entities, people, systems and information resources together with 66 services which processes and reacts to information from the physical and virtual world

67 [SOURCE: ISO/IEC 20924:2018]

68 3.1.8 69 management

70 direction, control, and coordination of work performed to develop a product or perform a service

71 [SOURCE: ISO/IEC/IEEE 24765:2017, 3.3064]

72 3.1.9 73 physical element

74 thing that has material existence in physical world

75 3.1.10 76 resource

77 any device, tool and means, except raw material and final product components, at the disposal of the 78 enterprise to produce goods or services

79 Note 1 to entry: Resources as they are defined here include human resources considered as specific means with a 80 given capability and a given capacity. Those means are considered as being able to be involved in the 81 manufacturing process through assigned tasks. That does not include any modelling of an individual or common 82 behaviour of human resource except in their capability to perform a given task in the manufacturing process (e.g.: 83 transformation of raw material or component, provision of logistic services). That means that human resources 84 are only considered, as the other, from the point of view of their functions, their capabilities and their status (e.g.: 85 idle, busy). That excludes any modelling or representation of any aspect of individual or common «social» 86 behaviour.

87 Note 2 to entry: This definition includes ISO 10303-49 definition.

88 [SOURCE: ISO 15531-1:2004, 3.6.43]

89 3.1.11 90 sensor

91 device that observes and measures a physical property of a natural phenomenon or man-made process 92 and converts that measurement into a signal

93 Note 1 to entry: Signal can be electrical, chemical, etc.

94 [SOURCE: ISO/IEC 29182‑ 2]

96 3.1.12 97 task

98 activities required to achieve a goal

99 Note 1 to entry: These activities can be physical and/or cognitive.

100 [SOURCE: ISO 9241‑ 11:1998, 3.9]

101 3.2 Digital Twin manufacturing specific terms

102 3.2.1 103 digital entity 104 computational and/or data element

105 Note 1 to entry: A digital entity can exist as a cloud service or as a service in a data centre, or as a network element 106 or as an IoT gateway.

107 [SOURCE: ISO/IEC 20924:2018, 3.1.14]

108 3.2.2 109 digital model

110 fit for purpose digital representation of something designed to support decisions related to it

111 Note 1 to entry: It is recognized that some practitioners in some industries may refer to this as a “Digital Twin.” 112 For the purpose of this document, “Digital Twin” refers to a specific subclass of digital models.

113 3.2.3 114 Digital Twin

115 fit for purpose digital representation of some realized thing or process with a means to enable 116 convergence between the realised instance and digital instance at an appropriate rate of 117 synchronisation

118 3.2.4 119 Digital Twin modelling

120 procedure of creating a digital model of an observable element

121 3.2.5 122 manufacturing process

123 structured set of activities or operations performed upon material to convert it from the raw material 124 or a semi-finished state to a state of further completion

125 Note 1 to entry: Manufacturing processes may be arranged in process layout, product layout, cellular layout or 126 fixed position layout. Manufacturing processes may be planned to support make-to-stock, make-to-order, 127 assemble-to-order, etc., based on strategic use and placements of inventories.

128 [SOURCE: ISO 15531-1:2004, 3.6.25]

129 3.2.6 130 presentation

131 manner in which information is displayed for use by a human Note 1 to entry: Digital model can be 132 presented audibly and visually.

133 [SOURCE: ASME Y14.47-2019]

134 3.2.7 representation

135 manner in which information is stored for interpretation by a machine [SOURCE: ASME Y14.47-2019]

136 3.2.8 137 visualization

138 use of computer graphics and image processing to present models or 139 characteristics of processes or objects for supporting human understanding

140 Note 1 to entry: Examples: A display image of a CNC machine milling an aluminium block.

141 Note 2 to entry: scientific visualization; visualization: terms and definition standardized by ISO/IEC [ISO/IEC 142 2382-13:1996].

143 [SOURCE: ISO/IEC 2382:2015, 2125942, Note 1 to entry changed to address manufacturing examples. 144 Note 3 to entry deleted]

145 3.2.9 146 view/viewpoint

147 projection of a model, seen from a given perspective or vantage point and which omits entities that are 148 not relevant to this perspective

149 [SOURCE: ISO/IEC 19501:2005]

150 3.3 Abbreviated terms

151 API Application Program Interface 152 CAD Computer Aided Design 153 CAM Computer Aided Manufacturing 154 DCDCD Data Collecting and Device Controlling Domain 155 DTME Digital Twin of Observable Manufacturing Element 156 ERP Enterprise Resource Planning 157 IE Information Exchange 158 IoT Internet of Things 159 IPC Inter-Process Communication 160 MES Manufacturing Execution System 161 O&M Operation and Management 162 OME Observable Manufacturing Element 163

164 4 Overview of Digital Twin for manufacturing

165 4.1 Concept of Digital Twin

166 A Digital Twin is a fit for purpose digital representation of some realized thing or process with a means 167 to enable convergence between the realised instance and digital instance at an appropriate rate of 168 synchronisation

169 Digital Twin may exist across the entire life-cycle and can leverage aspects of the virtual environment 170 (high-fidelity, multi-physics, external data sources, etc.), computational techniques (virtual testing, 171 optimisation, prediction, etc.), and aspects of the physical environment (historical performance, 172 customer feedback, cost, etc.) to improve elements of the overall system (design, behaviour, 173 manufacturability, etc.). [15]

174 NOTE Definitions in this document are being harmonized with those in Ad Hoc Group Digital Twin, 175 currently published as ISO/TC 184/SC 1 N517.

176 4.2 Digital Twin for manufacturing

177

178 Figure 1 – Concept of Digital Twin for manufacturing

179 A Digital Twin for manufacturing updates as its physical counterpart changes to represent its status, 180 conditions, product geometries, resource state, and any other observable status and conditions.

181 A Digital Twin is kept current with its observable manufacturing elements at an appropriate rate of 182 synchronization. Additionally, a Digital Twin for manufacturing may recall previous states of the 183 observable manufacturing elements.

184 The Digital Twin enables functionalities to synchronize its representation with its corresponding 185 observable manufacturing elements by constantly exchanging operational and environmental data. A 186 Digital Twin assists with detecting anomalies in the manufacturing processes and to achieve various 187 functional objectives such as real time control, off-line analytics, health check, predictive maintenance, 188 synchronous monitoring/alarm, manufacturing operations management (MOM) optimization, in- 189 process adaptation, Big Data analytics, machine learning, etc.

190 The visibility into process and execution enabled by Digital Twin for manufacturing enhances business 191 cooperation and multiple other efficiencies such as in-loop planning and validation, production 192 scheduling assurance, enhancement of understanding manufacturing elements, dynamic risk 193 management, cost reduction, etc.

194 Examples of applications and benefits are given in 4.3 and 4.4, but are not limited to those given.

195 4.3 Applications of Digital Twin for manufacturing

196 4.3.1 Real time control

197 A real time control application uses the current state of the Digital Twins to make changes to a 198 manufacturing process in real time.

199 4.3.2 Off-line analytics

200 An off-line analytics application uses the changed state of the Digital Twins to make recommendations 201 about the manufacturing process.

202 4.3.3 Predictive maintenance

203 A predictive maintenance application is a real-time or off-line application that uses the Digital Twins to 204 schedule and adapt maintenance activities for the production equipment.

205 4.3.4 Health check

206 A health check application uses the Digital Twins to check conditions of observable manufacturing 207 elements and if necessary, schedules maintenance.

208 4.3.5 Engineering design

209 An engineering design application uses Digital Twins to learn about previously manufactured products 210 to optimize new and existing product designs.

211 4.4 Benefits of Digital Twin for manufacturing

212 4.4.1 In-loop planning and validation

213 Digital Twin for manufacturing facilitates in-loop planning, validation, and adjustment of manufacturing 214 processes through simulation.

215 4.4.2 Production scheduling assurance

216 Digital Twin for manufacturing facilitates real time monitoring of production, allowing management to 217 dynamically adjust the manufacturing throughput to meet a production schedule.

218 4.4.3 Enhanced understanding of manufacturing elements

219 Information of observable manufacturing elements contained within Digital Twins facilitates accurate 220 planning of manufacturing and production schedules.

221 4.4.4 Dynamic risk management

225 4.4.5 Cost reduction

226 Overall, various applications of Digital Twin for manufacturing reduce manufacturing and management 227 cost.

228 4.5 Elements of Digital Twin for manufacturing

229 4.5.1 Observable manufacturing element

230 An observable manufacturing element is an item that has observable physical presence or operation in 231 manufacturing.

232 4.5.1.1 Personnel

233 Personnel in manufacturing generally include those employees who are engaged directly or indirectly 234 in manufacturing processes.

235 NOTE In Digital Twin for manufacturing, availability and certification level of personnel are examples of digital 236 models.

237 4.5.1.2 Equipment

241 4.5.1.3 Material

242 Material is physical matter that becomes a part or the whole of a product i.e., metal block, glass panel, 243 etc., or is used to aid manufacturing processes, i.e., cleaning fluid, coolant, etc.

244 4.5.1.4 Process

245 A process is an observable physical operation within manufacturing. Processes are inclusive of 246 manufacturing processes, maintenance processes, management processes, etc.

247 4.5.1.5 Facility

248 Facility is infrastructure that is related to or affects manufacturing. Examples of facility are special 249 purpose rooms, buildings, energy supply, water supply, environmental controllers, etc.

250 4.5.1.6 Environment

254 4.5.1.7 Product

258 4.5.1.8 Supporting document

259 A supporting document is any form of artefact (requirement, plan, model, specification, configuration) 260 that helps the applications of Digital Twin for manufacturing.

261 4.5.2 Digital elements

262 4.5.2.1 Application of Digital Twin for manufacturing

263 An application operating on the Digital Twin for manufacturing reports on or makes adjustments to the 264 current state of manufacturing equipment and operations.

265 4.5.2.2 Product definition

266 A product definition is specifications or properties of a product that are necessary to characterise it 267 such as dimensions, tolerances, surface finish, etc.

268 4.5.2.3 Process definition

269 A process definition is a specification of the personnel, equipment, material resources, and operations 270 that are required to perform a manufacturing process.

271

272 5 General principles of Digital Twin framework for manufacturing

273 5.1 Overview

274 The Digital Twin framework for manufacturing provides guidance on how to construct a Digital Twin 275 for manufacturing and specifies how applications can interoperate and how data from different sources 276 can be integrated. However, it does not specify any implementation technologies.

277 5.2 Standardization Scope of Digital Twin framework for manufacturing

278 5.2.1 Limitations and boundaries

279 280 Figure 2 – High-level Concept of Digital Twin framework for manufacturing