ISO/IEC TR 30172:2023

ISO/IEC TR 30172
Edition 1.0 2023-10
TECHNICAL
REPORT
colour
inside
Internet of things (loT) - Digital twin – Use cases

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about
ISO/IEC copyright or have an enquiry about obtaining additional rights to this publication, please contact the address
below or your local IEC member National Committee for further information.

IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
CH-1211 Geneva 20 www.iec.ch
Switzerland
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigendum or an amendment might have been published.

IEC publications search - webstore.iec.ch/advsearchform IEC online collection - oc.iec.ch
The advanced search enables to find IEC publications by a Discover our powerful search engine and read freely all the
variety of criteria (reference number, text, technical publications previews. With a subscription you will always
committee, …). It also gives information on projects, replaced have access to up to date content tailored to your needs.
and withdrawn publications.
Electropedia - www.electropedia.org
IEC Just Published - webstore.iec.ch/justpublished
The world's leading online dictionary on electrotechnology,
Stay up to date on all new IEC publications. Just Published
containing more than 22 000 terminological entries in English
details all new publications released. Available online and
and French, with equivalent terms in 18 additional languages.
once a month by email.
Also known as the International Electrotechnical Vocabulary

(IEV) online.
IEC Customer Service Centre - webstore.iec.ch/csc

If you wish to give us your feedback on this publication or
need further assistance, please contact the Customer Service
Centre: sales@iec.ch.
ISO/IEC TR 30172
Edition 1.0 2023-10
TECHNICAL
REPORT
colour
inside
Internet of things (loT) - Digital twin – Use cases

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 35.020; 35.240 ISBN 978-2-8322-7604-4

– 2 – ISO/IEC TR 30172:2023
© ISO/IEC 2023
CONTENTS
FOREWORD . 5
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms and definitions . 7
4 Abbreviated terms . 9
5 Applications . 9
5.1 Application domains . 9
5.2 Life cycle stage coverage. 10
6 Use cases . 10
6.1 Overview. 10
6.2 Properties . 10
6.3 Basic statistics . 11
6.3.1 Use cases by application domain . 11
6.3.2 Use cases by status of life cycle . 13
7 Use case summaries . 14
Annex A (informative) Use case template . 16
A.1 General . 16
A.2 Description of use case . 16
A.2.1 Name of use case . 16
A.2.2 Digital twin application area or context of use . 16
A.2.3 Version management . 17
A.2.4 Basic information to use case . 17
A.2.5 Scope of use case (bullet points) . 18
A.2.6 Objectives of use case (bullet points) . 18
A.2.7 Narrative of use case . 18
A.2.8 Entities which need to be modelled as digital entities in use case . 19
A.2.9 Actors: people, organizations or systems . 19
A.2.10 Life cycle of digital twin system in use case . 20
A.2.11 Key performance indicators (KPIs) of use case . 21
A.2.12 Digital infrastructures . 21
A.2.13 Referenced standards and standardization committees (optional) . 22
A.2.14 Referenced papers or patent (optional) . 22
A.2.15 Relation with other known use cases, for example common
requirements (optional) . 22
A.2.16 General remarks (optional) . 22
A.2.17 Challenges and issues (optional) . 22
A.2.18 Data security, privacy and trustworthiness (optional) . 23
A.2.19 User requirements and interactions with other actors (optional) . 23
A.3 Drawings or diagrams depicting the use case . 23
A.3.1 Drawing of use case . 23
A.3.2 Data flow diagram of use case (optional) . 23
A.3.3 Sequence diagram(s) of use case (optional) . 23
A.3.4 Deployment diagram(s) of use case (optional) . 24
A.3.5 Others (optional) . 24
Annex B (informative) Collected use cases . 25

© ISO/IEC 2023
B.1 Smart building – Smart building operation based on digital twins . 25
B.1.1 Description of use case . 25
B.1.2 Drawings or diagrams depicting the use case . 37
B.2 Industrial smart park – Digital twin based industrial smart park design and
construction . 39
B.2.1 Description of use case . 39
B.2.2 Drawings or diagrams depicting the use case . 46
B.3 Smart city – Digital twin based smart city management system . 49
B.3.1 Description of use case . 49
B.3.2 Drawings or diagrams depicting the use case . 59
B.4 Smart energy – Construction and application of digital twins for a large oil
and gas processing facility . 61
B.4.1 Description of use case . 61
B.4.2 Drawings or diagrams depicting the use case . 73
B.5 Smart building – Monitoring of water . 74
B.5.1 Description of use case . 74
B.5.2 Drawings or diagrams depicting the use case . 82
B.6 Smart Power Grid – Smart grid operation based on a digital twin . 82
B.6.1 Description of use case . 82
B.6.2 Drawings or diagrams depicting the use case . 90
B.7 Smart construction life cycle – Construction-phase digital twin model . 91
B.7.1 Description of use case . 91
B.7.2 Drawings or diagrams depicting the use case . 104
B.8 Smart building – Residential explicit demand response – Consumer
behavioural digital twin for energy demand prediction . 106
B.8.1 Description of use case . 106
B.8.2 Drawings or diagrams depicting the use case . 119
B.9 Smart city - Greater Hobart Digital Twin . 120
B.9.1 Description of use case . 120
B.9.2 Drawings or diagrams depicting the use case . 129
B.10 Smart city - NSW Spatial Digital Twin . 130
B.10.1 Description of use case . 130
B.10.2 Drawings or diagrams depicting the use case . 138
B.11 Transport - Sydney Trains Engineering and Maintenance Digital Twin . 138
B.11.1 Description of use case . 138
B.11.2 Drawings or diagrams depicting the use case . 145
B.12 Transport - TfNSW Infrastructure Delivery Digital Twin . 148
B.12.1 Description of use case . 148
B.12.2 Drawings or diagrams depicting the use case . 155
B.13 Smart energy – From grid planning to grid operation and maintenance,
based on grid digital twin(s) . 157
B.13.1 Description of use case . 157
B.13.2 Drawings or diagrams depicting the use case . 164
B.14 Smart energy – Electrical field level subsystem digital twin, as the basis for
its specification, commissioning, operation and maintenance . 165
B.14.1 Description of use case . 165
B.14.2 Drawings or diagrams depicting the use case . 174
Bibliography . 177

Figure 1 – Distribution of use cases collected in Annex B by application domains . 12

– 4 – ISO/IEC TR 30172:2023
© ISO/IEC 2023
Figure 2 – Statistics on adopted key technologies from use cases in JTC 1/AG 11
report . 13
Figure B.1 – Geometric analysis of safety prevention . 94
Figure B.2 – Identification of close proximity events between heavy machinery. 95
Figure B.3 – Safety training scenario . 95
Figure B.4 – Segmented construction components after voxel space point matching . 96
Figure B.5 – Sample defect predictions . 96
Figure B.6 – On-site defect visualization, defect confirmation, and addition of remedial
work . 97
Figure B.7 – Use case diagram: before construction starts. 104
Figure B.8 – Use case diagram: during construction . 105

Table 1 – List of use cases in JTC 1/AG 11 report . 12
Table 2 – List of use cases by status of life cycle . 14
Table 3 – List of use cases . 14
Table A.1 – Description of some qualitative indicators . 21

© ISO/IEC 2023
INTERNET OF THINGS (IoT) –
DIGITAL TWIN – USE CASES
FOREWORD
1) ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC
participate in the development of International Standards through technical committees established by the
respective organization to deal with particular fields of technical activity. ISO and IEC technical committees
collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental,
in liaison with ISO and IEC, also take part in the work.
2) The formal decisions or agreements of IEC and ISO on technical matters express, as nearly as possible, an
international consensus of opinion on the relevant subjects since each technical committee has representation
from all interested IEC and ISO National bodies.
3) IEC and ISO documents have the form of recommendations for international use and are accepted by IEC and
ISO National bodies in that sense. While all reasonable efforts are made to ensure that the technical content of
IEC and ISO documents is accurate, IEC and ISO cannot be held responsible for the way in which they are used
or for any misinterpretation by any end user.
4) In order to promote international uniformity, IEC and ISO National bodies undertake to apply IEC and ISO
documents transparently to the maximum extent possible in their national and regional publications. Any
divergence between any IEC and ISO document and the corresponding national or regional publication shall be
clearly indicated in the latter.
5) IEC and ISO do not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC and ISO marks of conformity. IEC and ISO are not
responsible for any services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this document.
7) No liability shall attach to IEC and ISO or their directors, employees, servants or agents including individual
experts and members of its technical committees and IEC and ISO National bodies for any personal injury,
property damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including
legal fees) and expenses arising out of the publication, use of, or reliance upon, this ISO/IEC document or any
other IEC and ISO documents.
8) Attention is drawn to the Normative references cited in this document. Use of the referenced publications is
indispensable for the correct application of this document.
9) Attention is drawn to the possibility that some of the elements of this ISO/IEC document may be the subject of
patent rights. IEC and ISO shall not be held responsible for identifying any or all such patent rights.
ISO/IEC TR 30172 has been prepared by subcommittee 41: Internet of Things and Digital Twin,
of ISO/IEC joint technical committee 1: Information technology. It is Technical Report.
The text of this Technical Report is based on the following documents:
Draft Report on voting
JTC1-SC41/335/DTR JTC1-SC41/363/RVDTR

Full information on the voting for its approval can be found in the report on voting indicated in
the above table.
The language used for the development of this Technical Report is English.
This document was drafted in accordance with ISO/IEC Directives, Part 2, and developed in
accordance with ISO/IEC Directives, Part 1, available at www.iec.ch/members_experts/refdocs
and www.iso.org/directives.
IMPORTANT – The "colour inside" logo on the cover page of this document indicates
that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this document using a colour printer.

– 6 – ISO/IEC TR 30172:2023
© ISO/IEC 2023
INTRODUCTION
This document provides use cases of digital twin applications in various domains using the
template modified from IEC 62559-2 use case template and ISO/IEC TR 22417 use case
template. Use case templates used in ISO/IEC JTC 1/AG 8, ISO/IEC JTC 1/AG 11 and
ISO/IEC JTC 1/SC 41/AG 25 are also considered for the template in this document.
The use case template includes two parts: Description of use case; Drawings or diagrams
depicting the use case. To collect use cases, the first step is to identify application domains of
digital twin (DTw) systems and to provide a use case template. Contributors were requested to
submit use cases using the provided template.
For improving the quality of the use case description, a guidance is provided to contributors.
The guidance includes DTw concepts and reference models for preparing use cases.
By investigating use cases, it is possible to find the new technical requirements from the market,
accelerating the transformation of science and technology achievements.
The use case template helps to group and categorize the use cases according to the identified
application domains. Readers of this document can find use cases that relate to the desired
application domain and can find original submissions of use cases in Annex A, which includes
all submissions of use cases.
© ISO/IEC 2023
INTERNET OF THINGS (IoT) –
DIGITAL TWIN – USE CASES
1 Scope
This document provides a collection of representative use cases of digital twin applications in
a variety of domains, for example, smart manufacturing and smart cities.
This document is applicable to all types of organization (for example, commercial enterprises,
government agencies, and not-for-profit organizations).
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following
addresses:
• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.1
digital twin
DTw
digital representation of a target entity (3.2) with data connections that enable convergence
between the physical and digital states at an appropriate rate of synchronization
Note 1 to entry: Digital twin has some or all of the capabilities of connection, integration, analysis, simulation,
visualization, optimization, collaboration, etc.
Note 2 to entry: Digital twin can provide an integrated view throughout the life cycle of the target entity.
[SOURCE: ISO/IEC 30173:–, 3.1.1]
3.2
entity
thing (physical or non-physical) having a distinct existence
EXAMPLE Person, object, event, idea, process, etc.
[SOURCE: ISO/IEC 20924:2021, 3.1.18, modified – The domain "" and the
example have been added.]
3.3
physical entity
entity in the physical world that can be the subject of sensing and/or actuating
[SOURCE: ISO/IEC 20924:2021, 3.1.27]

– 8 – ISO/IEC TR 30172:2023
© ISO/IEC 2023
3.4
digital entity
computational element comprising data elements and procedural elements
[SOURCE: ISO/IEC 30173:–, 3.1.5]
3.5
life cycle
evolution of a system, product, service, project or other human-made entity from conception
through retirement
[SOURCE: ISO/IEC/IEEE 15288:2023, 3.21]
3.6
conformity
process of analysis to determine whether a digital twin meets the specified requirements and
to form a judgement as to whether the digital entity is fit for its corresponding physical entity
3.7
reliability
ability of an item to perform a required function under given conditions for a given time interval
[SOURCE: IEC 62657-1:2017, 3.1.12, modified – Note 1 to entry and note 2 to entry have been
deleted.]
3.8
verification
confirmation, through the provision of objective evidence, that specified requirements have
been fulfilled
[SOURCE: ISO 9000:2015, 3.8.12, modified – The notes to entry have been deleted.]
3.9
validation
confirmation, through the provision of objective evidence, that the requirements for a specific
intended use or application have been fulfilled
[SOURCE: ISO 9000:2015, 3.8.13, modified – The notes to entry have been deleted.]
3.10
robustness
degree to which a system or component can function correctly in the presence of invalid inputs
or stressful environmental conditions
[SOURCE: ISO/IEC/IEEE 24765:2017, 3.3555]
3.11
fidelity
ability to accurately describe the relevant aspects of the physical counterpart within a well-
defined set of conditions by its digital model
3.12
traceability
ability to trace the history, application or location of an object
[SOURCE: ISO 9000:2015, 3.6.13, modified – Note 1 to entry and note 2 to entry have been
deleted.]
© ISO/IEC 2023
3.13
synchronization
action of making the states of target and digital entity synchronized, using network
for real time system
[SOURCE: ISO/IEC 30173:–, 3.1.20]
3.14
reconfigurability
ability of an artefact to be changed through configuration changes rather than having to modify
its underlying structure or its code or both
3.15
interoperability
ability of two or more different systems to exchange information and to use the information that
has been exchanged
[SOURCE: ISO/TS 27790:2009, 3.39, modified – In the definition, "systems or components" has
been replaced by "different systems".]
4 Abbreviated terms
2D two dimensional
3D three dimensional
AI artificial intelligence
APP application
BIM building information modelling
DTw digital twin
ERP enterprise resource planning
GIS geographic information system
HVAC heating, ventilation, and air conditioning
IED intelligent electronic device
KPI key performance indicator
LGA land grid array
MES manufacturing execution system
MQTT message queuing telemetry transport
PC personal computer
PLC programmable logic controller
R&D research and development
SCADA supervisory control and data acquisition
5 Applications
5.1 Application domains
DTw application domains can be classified into industry-based categories, and specific use
cases can serve as examples for each category. The application domains listed below are the
targeted areas for collecting use cases related to DTw; however, there may be other areas that
are not included in this list.
– building or construction
– 10 – ISO/IEC TR 30172:2023
© ISO/IEC 2023
– urban
– energy
– healthcare
– manufacturing
– home appliance
– mining
– telecommunications
– aerospace
– marine
– environmental monitoring
– transport
5.2 Life cycle stage coverage
The following life cycle stages, based on ISO/IEC 30173:– , are considered as target phases
to collect use cases:
– inception
– design and development
– verification and validation
– deployment
– operation and monitoring
– re-evaluation
– retirement.
6 Use cases
6.1 Overview
Twelve use cases, based on the use case template described in Annex A, have been collected
in Annex B. Some use cases include trademarks such as company names, product names, or
service names. This information is given for the convenience of users of this document and
does not constitute an endorsement by ISO or IEC.
The template provided in Annex A includes two parts: description of use case, and drawings or
diagrams depicting the use case.
– Description of use case includes the following elements: name of use case, application area,
version management, basic information to use case, scope of use case, objectives of use
case, entities that need to be modelled as digital entities in use case, actors, life cycle of
the digital twin system in use case, key performance indicators (KPIs) of use case, digital
infrastructures.
– Drawings or diagrams depicting the use case includes the following elements: drawing of
use case, data flow diagram of use case, sequence diagram(s) of use case, deployment
diagram(s) of use case.
6.2 Properties
Description of the use case includes the following.
– Name of the use case to be provided by the contributor of the use code.
___________
Under preparation. Stage at the time of publication: ISO/IEC FDIS 30173:2023.

© ISO/IEC 2023
– Digital twin application area or context of use.
– Version management: the status of the version of the use case.
– Basic information to use case: descriptions of basic information of the use case that
includes:
1) conditions (limitations) of use;
2) maturity of the use case, for example, in business operation, realized in demonstration
project, realized in R&D, in preparation, visionary;
3) generic, regional or national relation;
4) vertical application area, for example, automotive industry, petrochemical industry, and
aviation industry;
5) keywords for classification, for example, system integration, performance evaluation,
information exchange, IT security, and AI application.
– Scope of use case: the scope that defines the aspects covered by the limits use case or
indicates the purview and limitations of the use case.
– Objectives of use case: the intention of the use case, in other words, what is to be
accomplished and who will be benefited by the use case and how.
– Narrative of use case.
– Entities that need to be modelled as digital entities in the use case.
– Actors: people, organizations or systems.
– Life cycle of the digital twin system in use case: refers to 5.3 life cycle stage(s) or phase(s)
coverage.
– Key performance indicators (KPIs) of use case.
– Digital infrastructures: description of digital infrastructures employed in the use cases.
– Referred standards and standardization committees.
– Referred papers or patent.
– Relation with other known use cases, for example, common requirements.
– Challenges and issues: descriptions of challenges and issues in the use case.
– Data security, privacy, and trustworthiness: issues relating to description of data, privacy,
and trustworthiness in the use case.
– User requirements and interactions with other actors.
See Clause A.2 for details.
6.3 Basic statistics
6.3.1 Use cases by application domain
6.3.1.1 Use cases in Annex B
Distribution of use cases in Annex B by application domain is shown in Figure 1.

– 12 – ISO/IEC TR 30172:2023
© ISO/IEC 2023
Figure 1 – Distribution of use cases collected in Annex B by application domains
6.3.1.2 Use cases in report of AG 11
Twenty-eight use cases have been collected from JTC 1/AG 11 report on DTw. The use case
names and application fields are shown in Table 1. Statistics on distribution of use cases in
JTC 1/AG 11 report by application domain are shown in Figure 2.
Table 1 – List of use cases in JTC 1/AG 11 report
Use case name Application domain
Optimization of production execution Manufacturing
Dicastal Morocco factory Manufacturing
Product intelligent manufacturing production line Manufacturing
Product Intelligent Assembly Process Simulation and Optimization Manufacturing
Electro-hydraulic servo valve assembly process Manufacturing
On Digital Twin in Additive Manufacturing Manufacturing
Digital Twin for massive smart manufacturing Manufacturing
Visual monitoring system for small and medium-sized machining automatic
Manufacturing
production line
Visual monitoring system for assembly process Manufacturing
The generative design and additive manufacturing of mass customized footwear
Manufacturing
lattices
Research and Application of Digital Twin Technology in Joint Ship Hull Workshop Manufacturing
Integrated Digital System for Smart Ship Pipeline Factory Manufacturing
Luxury cruise sheet section turning device Manufacturing
Dynamic scheduling of manufacturing tasks between multiple robots Manufacturing
On-machine measurement for tool-life optimization Manufacturing
Advanced Metrology Manufacturing
Integrated Digital System for Smart Ship Pipeline Factory Manufacturing
Digital Twin Technology Applied to the Automated Driving Test and Evaluation
Manufacturing
System
Digital twin system of tobacco industry chain Manufacturing
Research on the construction and application of digital twin in intelligent oil and gas
Energy
pipeline network
Smart Cities with Digital Twin Technology Urban
Digital Twin City Smart Control Cloud-Platform Urban
Elderly Healthcare Services Using Digital Twin Healthcare

© ISO/IEC 2023
Use case name Application domain
Prototype Twinning Prototyping
Digital Intelligence Huaguoyuan Community
Digital Twin of Supply Chain for Automotive Industry Supply Chain
Use of AI systems digital twins for conformity assessment General Scenario
Digital Twin Solution for Thermal Fluid Systems based on Flownex General Scenario

Figure 2 – Statistics on adopted key technologies from use cases in JTC 1/AG 11 report
6.3.1.3 Use cases in IEC SRD 62913-2-3 and IEC SRD 62913-2-4
A list of described use cases in IEC SRD 62913-2-3 and IEC SRD 62913-2-4 can be also
considered:
– IEC SRD 62913-2-3-S050 "Process data related to the smart home behaviour to aggregate
(forecasting, real-time), assess the value of, and certify flexibilities"
– IEC SRD 62913-2-3-S053 "Process data related to the Smart Building behaviour to
aggregate (forecasting, real-time), assess the value of, and certify flexibilities"
– IEC SRD 62913-2-3-S069 "Elaborate a charge or discharge schedule"
– IEC SRD 62913-2-3-S079 "Forecast electricity price"
– IEC SRD 62913-2-3-S080 "Forecast power demand"
– IEC SRD 62913-2-3-S091 "Perform renewable energy forecasts"
– IEC SRD 62913-2-4-S007 "Forecast FCR capacity of an EV aggregate"
6.3.2 Use cases by status of life cycle
Distribution of each of the Annex B use case by status of life cycle is shown in Table 2.

– 14 – ISO/IEC TR 30172:2023
© ISO/IEC 2023
Table 2 – List of use cases by status of life cycle
Status of life cycle Numbers of use cases
Inception phase 4
Design and development phase 6
Installation phase 4
Deployment phase 11
Operation and monitoring phase 4
Re-evaluate phase 3
Retirement phase 2
7 Use case summaries
Table 3 shows summary information for each of the use cases, including use case name,
application domain, and status.
Table 3 – List of use cases
Corresponding Application
Use case name Status of life cycle
clause number domain
Smart building operation based Building or
B.1 Deployment phase
on digital twins construction
Digital twin based industrial
B.2 smart park design and Urban Deployment phase
construction
Digital twin based smart city
B.3 Urban Re-evaluate phase
management system
Construction and application of
digital twins for a large oil and
B.4 Energy Deployment phase
gas processing facility
Deployment phase;
Building or
B.5 Monitoring of Water
construction
Installation phase
Deployment phase;
Smart grid operation based on
B.6 Power grid
digital twin
Operation and monitoring phase
Construction-phase digital twin Building or
B.7 Design and development phase
model construction
Design and development phase;
Consumer behavioural digital
Building or
B.8 twin for energy demand Deployment phase;
construction
prediction
Installation phase
B.9 Greater Hobart Digital Twin Urban Design and development phase
B.10 NSW Spatial Digital Twin Urban Deployment phase
Sydney Trains Engineering and
B.11 Transport Inception phase
Maintenance Digital Twin
Inception phase;
TfNSW Infrastructure Delivery
B.12 Transport
Digital Twin
Design and development phase
© ISO/IEC 2023
Corresponding Application
Use case name Status of life cycle
clause number domain
Inception phase;
Design and development phase;
Verification and validation phase;
From grid planning to grid
B.13 operation and maintenance, Energy Deployment phase;
based on grid digital twin(s)
Operation and monitoring phase;
Re-evaluate phase;
Retirement phase
Inception phase;
Design and development phase;
Verification and validation phase;
Electrical field level subsystem
digital twin, as the basis for its
B.14 Energy Deployment phase;
specification, commissioning,
operation and maintenance
Operation and monitoring phase;
Re-evaluate phase;
Retirement phase
– 16 – ISO/IEC TR 30172:2023
© ISO/IEC 2023
Annex A
(informative)
Use case template
A.1 General
This Annex A is the template used for collecting use cases. The terms used in that template
were defined in 5.1.
The template is based on:
– IEC 62559-2
– ISO/IEC TR 22417
– template developed by JTC 1/AG 8
– template developed by JTC 1/SC 41/AG 25
– template developed by JTC 1/AG 11
A.2 Description of use case
A.2.1 Name of use case
ID Name of use case
For example, xx (Application area)-xx( Application scenario)-xx(National Body)

A.2.2 Digital twin application area or context of use
Application area or context of use
For example, manufacturing, agriculture, digital marketing, education, energy, finance
technology, healthcare, home or service robotics, ICT, logistics, and city management.

© ISO/IEC 2023
A.2.3 Version management
Changes Date Name Approval status (optional)
or version Author(s) or
committee
For For example: For example: draft, for comments,
example, xx(year)- for ballot
V1.0 xx(month)-
xx(day)
A.2.4 Basic information to use case
Source(s) or Link Conditions (limitations) of use (optional)
literature (optional) (optional)

Maturity of use case
□ in business operation
□ realized in demonstration project
□ realized in R&D
□ in preparation
□ visionary
Generic, regional or national relation

Vertical application area
For example, Automotive industry, petrochemical industry, and aviation industry.

Well-known or related commercial or existing use cases (optional)

– 18 – ISO/IEC TR 30172:2023
© ISO/IEC 2023
Keywords for classification
For example, system integration, performance evaluation, information exchange, IT
security, and AI application.
A.2.5 Scope of use case (bullet points)
Scope of use case
Include but not limited to following items:
• Describe xxxx in xxx scenario;
• Describe xxx among xxx systems;
• Describe digital twin system architecture in xxx scenario;
• Describe requirements about xxx in xxx area or scenario

A.2.6 Objectives of use case (bullet points)
Objectives of use case
• Objective 1: to obtain, realize, minimize or satisfy xxx
• Objective 2: xxx
• …
A.2.7 Narrative of use case
Narrative of use case
Short description – max. 3 sentences

Complete description
© ISO/IEC 2023
A.2.8 Entities which need to be modelled as digital entities in use case
Entity name  Data Model type Requirements or
constraints on the models
For example, robot,
sensor, building,
person, and car.
NOTE
(1) Data: can include asset data, operational data, context data, metadata, operational history, maintenance history,
and knowledge.
(2) Model type: can include physical model, chemical model, statistical model, AI model, engineering model, and
metamodel.
(3) The types of requirements or constraints on the models: can involve performance requirements of the models,
input and output requirements of the models, and important constraints. Constraints: can include legal contracts,
legal regulations, and others (including regional regulations).
A.2.9 Actors: people, organizations or systems
Actor name Actor type Actor description Actor interactions
(Transactions
between Actors)
For example,
(optional)
Actor : xxx
n
□ system actor
□ business
actor: role:
______
□ system actor
□ business
actor: role:
______
□ system actor
□ business
actor: role:
______
□ system actor
□ business
actor: role:
______
□ system actor
□ business
actor: role:
______
– 20 – ISO/IEC TR 30172:2023
© ISO/IEC 2023
□ system actor
□ business
actor: role:
______
NOTE 1 According to IEC 62559-2:
(1) Actor refers to people, organizations or systems that communicates and interacts, such as, consumer, customer
energy management system, distribution management system, distribution system operator, meter operator, and
system operator.
NOTE 2 These actors can include people, software applications, systems, databases, and even the power system
itself.
The entities in A.2.8 refer to the objects that will be modelled as digital models in the digital space. The actors in
A.2.9 refer to the people, organizations or systems that will trigger or have influences on the digital twin system. The
business actor refers to the people, organizations that can apply, trigger or have influences on the digital twin
systems.
(2) Actor type is divided into system actors and business actors.
– System actors are covering functions or devices. For example, in the energy system area, system actors
are defined in the interface reference model (IEC 61968-1).
– A business actor specifies in fact a "role"; roles can be taken by diverse entities.
Typical examples for actors or roles in the energy system:
– "Meter operator" is a role that can be taken either by a specific company or by a distribution system operator
(DSO) company;
– "Aggregator" is a role that could be taken by many entities like a DSO company, an energy service company
(ESCO) or an energy supplier.
(3) Examples of actors given in IEC 62559-2:2015, Table A.1 are as follows:
Consumer refers to end user of electricity, gas, water or heat.
NOTE 3 As the consumer can also generate energy using a distributed energy resource, the consumer is sometimes
called the "prosumer".
Customer energy management system refers to energy management system for energy customers to optimize the
utilization of energy according to supply contracts or other economic targets. Customer energy management system
is responsible for gathering flexibilities within the customer premises and providing them to an aggregator, and
therefore does not directly participate in flexibility markets.
A.2.10 Life cycle of digital twin system in use case
Life cycle of digital twin system in use case
□ inception phase
□ design and development phase
□ verification and validation phase
□ deployment phase
□ operation and monitoring phase
□ re-evaluate phase
□ retirement phase
© ISO/IEC 2023
A.2.11 Key performance indicators (KPIs) of use case
Name Description Reference to mentioned use case
objectives
For Objective x, xxxx.
NOTE Some qualitative indicators, such as synchronization, reliability, verification, robustness, traceability,
reconfigurability and some quantitative indicators can be taken into consideration. The description of some qualitative
indicators is given in Table A.1 and defined in Clause 3.
Table A.1 – Description of some qualitative indicators
Name Description
conformity process of analysis to determine whether a digital twin meets the specified requirements
and to form a judgement as to whether the digital entity is fit for its corresponding
physical entity
synchronization action of making the states of target and digital entity synchronized, using network for
real time system
NOTE Synchronization is the measurement of or process by which the correspondence
between a DTw and its target is measured or achieved.
reliability ability of an item to perform a required function under given conditions for a given time
interval
verification confirmation, through the provision of objective evidence, that specified requirements
have been fulfilled
validation confirmation, through the provision of objective evidence, that the requirements for a
specific intended use or application have been fulfilled
robustness degree to which a system or component can function correctly in the presence of invalid
inputs or stressful environmental conditions
fidelity ability to accurately describe the relevant aspects of the physical counterpart within a
well-defi
...