ISO/TS 8102-21

Style Definition: Heading 1: Indent: Left: 0 cm, First
ISO/DTS 8102-21
line: 0 cm
ISO/TC 178
Style Definition: Heading 2: Font: Bold, Indent: Left: 0
cm, First line: 0 cm
ISO/CD TS 8102-21(en)
Style Definition: Heading 3: Font: Bold, Indent: Left: 0
cm, First line: 0 cm
Secretariat: AFNOR
Style Definition: Heading 4: Font: Bold, Indent: Left: 0
cm, First line: 0 cm
Date: 2025-08-25
Style Definition: Heading 5: Font: Bold, Indent: Left: 0
cm, First line: 0 cm
Style Definition: Heading 6: Font: Bold
Style Definition: IntroHeading1: Font: Bold, Indent:
Left: 0 cm, First line: 0 cm
Style Definition: IntroHeading2: Font: Bold, Indent:
Electrical requirements for lifts, escalators and moving walks —
Left: 0 cm, First line: 0 cm
Style Definition: IntroHeading3: Font: Bold, Indent:
Left: 0 cm, First line: 0 cm
Style Definition: IntroHeading4: Font: Bold, Indent:
Left: 0 cm, First line: 0 cm
Style Definition: IntroHeading5: Font: Bold, Indent:
Left: 0 cm, First line: 0 cm
Part 21:
Style Definition: IntroHeading6
On-site and off-site software updates
Style Definition: IntroHeading7
Style Definition: IntroHeading8
Style Definition: IntroHeading9
Style Definition: ANNEX
Style Definition: Key Text
Style Definition: Key Title
Style Definition: List Continue 1
Style Definition: TermNum2: Font: Bold, Indent: Left:
0 cm, First line: 0 cm
Style Definition: TermNum3: Font: Bold, Indent: Left:
0 cm, First line: 0 cm
Style Definition: TermNum4: Font: Bold, Indent: Left:
0 cm, First line: 0 cm
Style Definition: TermNum5: Font: Bold, Indent: Left:
0 cm, First line: 0 cm
Style Definition: TermNum6: Font: Bold
Style Definition: Body Text
Style Definition: boxedText
Style Definition: Boxed List Continue 1
Style Definition: boxedTitle
Style Definition: FooterCentered
Style Definition: FooterPageNumber
Style Definition: FooterPageRomanNumber
Style Definition: FooterCenteredContinued
Style Definition: TPS Markup Base

ISO/CD TSDTS 8102-21:2025(en)
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication
may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying,
or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO
at the address below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
E-mail: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
ISO/CD TSDTS 8102-21:2025(en)
Contents
Foreword . iii
Introduction . iii
Scope . iii
Normative references . iii
Terms, definitions and abbreviated terms . iii
Terms and definitions . iii
Abbreviated terms . iii
Overview of software update . iii
General . iii
EUC domains with relevant security and safety requirements . iii
Management of software update . iii
General . iii
Requirements for software development . iii
Requirements for the deployment of software update . iii
Off-site software update management platform . iii
Technical requirements of the software update . iii
General . iii
Initiation . iii
Delivery . iii
Protection of persons . iii
Compatibility check . iii
Activation . iii
Validation . iii
Completion of software update . iii
Recovery from validation failure . iii
Auditing and reporting . iii
Information for use . iii
(informative) Comparison of on-site and off-site software updates . iii
(informative) Example of a software update sequence . iii
(informative) Product lifecycle and EUC installation lifecycle . iii
Bibliography . iii
Foreword . v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 2
4 Overview of software update . 2
4.1 General. 2
4.2 EUC domains with relevant security and safety requirements . 3
5 Management of software update . 3
5.1 General. 3
iii
ISO/CD TSDTS 8102-21:2025(en)
5.2 Requirements for software development . 3
5.3 Requirements for the deployment of software update . 3
5.4 Off-site software update management platform . 4
6 Technical requirements of the software update . 5
6.1 General. 5
6.2 Initiation . 5
6.3 Delivery . 5
6.4 Protection of persons . 5
6.5 Compatibility check . 5
6.6 Activation . 6
6.7 Validation . 6
6.8 Completion of software update . 7
6.9 Recovery from validation failure . 7
6.10 Auditing and reporting . 7
7 Information for use . 8
Annex A (informative) Comparison of on-site and off-site software updates . 9
Annex B (informative) Example of a software update sequence . 14
Annex C (informative) Product life cycle and EUC installation life cycle . 18
Bibliography . 22

iv
ISO/CD TSDTS 8102-21:2025(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
ISO 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 drawnISO draws attention to the possibility that some of the elementsimplementation of this
document may beinvolve the subjectuse of (a) patent(s). ISO takes no position concerning the evidence,
validity or applicability of any claimed patent rights. in respect thereof. As of the date of publication of this
document, ISO had not received notice of (a) patent(s) which may be required to implement this document.
However, implementers are cautioned that this may not represent the latest information, which may be
obtained from the patent database available at www.iso.org/patents. ISO shall not be held responsible for
identifying any or all such patent rights. 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 178, Lifts, escalators and moving walks.
A list of all parts in the ISO 8102 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.
v
ISO/CD TSDTS 8102-21:2025(en)
Introduction
[1]
This document complements ISO 8102-20:2022 for specific topic ofISO 8102-20 for software and parameter
updates.
Lifts, escalators, and moving walks ([referred to as the equipment under control (EUC) in this document]
contain executable code and parameters which require occasional updates.
Such executable code and parameters can be dynamically written or modified during execution and this can
impact the safety and security of the EUC. Therefore, fulfilment of safety and security requirements must be
ensured when either the executable code and/or the parameters, or both, are modified.
In this document, the term "software"software is used for both executable code and parameters, because the
same safety and security requirements of the EUC apply, independent of whether the executable code or a
parameter is updated.
vi
ISO/CD TSDTS 8102-21:2025(en)
Electrical requirements for lifts, escalators and moving walks —
Part 21:
On-site and off-site software updates
1 Scope
This document coversspecifies means for software updates including parameter modifications for lifts,
escalators, and moving walks (hereafter referred as EUC, [(equipment under control). Update (EUC)]. It is
applicable to process steps carried out on-site and off-site are covered.
This document doesIt is not applyapplicable to to EUC that are installed before the date of its publication.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
IEC 62443-3-2:2020, Security for industrial automation and control systems — Part 3-2: Security risk
assessment for system design
IEC/TS 62443-1-1:2009, Industrial communication networks — Network and system security — Part 1-1:
Terminology, concepts and models
ISO 8102-20:2022, Electrical requirements for lifts, escalators and moving walks — Part 20: Cybersecurity
ISO 8102-20:2022, Electrical requirements for lifts, escalators and moving walks — Part 20: Cybersecurity
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 8102-20:2022, IEC/TS 62443-1-
1:2009, IEC 62443-3-2:2020 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at https://www.electropedia.org/
3.1.1
software
either executable code and/, or configuration parameters, or both
Note 1 to entry: Change of the value of a configuration parameter of an executable software typically impacts behaviour
of a component or a system.
3.1.2
software update
process of updating software (3.1)
Note 1 to entry: In this document the term software update also covers parameter modifications.
ISO/CD TSDTS 8102-21:2025(en)
3.1.3
software package
collection of software (3.1) and information necessary for the software update (3.2)
3.1.4
important function
function or capability belonging to the equipment under control (EUC) domains: "safety, ", "essential" or
"alarm".
[2]
Note 1 to entry: The EUC domains are described in ISO 8102-20:2022.ISO 8102-20:2022 and 4.2.
3.1.5
equipment under control owner
EUC owner
Formatted: Term(s) Admitted
individual or organization responsible for the equipment under control (EUC)
[2]
[SOURCE: ISO 8102-20:2022, TermISO 8102-20:2022 , 3.1.3]
3.1.53.1.6
activation
step in the software update (3.2) when an executable code either becomes executable on an equipment under
control (EUC and/) or parameter(s) become active on an EUC, or both
3.1.63.1.7
on-site
at the site of the equipment under control (EUC) installation with physical access to the EUC
3.1.73.1.8
validation
confirmation, through the provision of objective evidence, that the requirements for a specific intended use or
application have been fulfilled
[SOURCE: ISO 9000:2005, 3.8.13]
[3]
[SOURCE: ISO 9000:2015 , 3.8.13, modified — Deleted Notes to entry 1 to 3.]
3.2 Abbreviated terms
EUC equipment under control
4 Overview of software update
4.1 General
This document describes generic steps of a software update process. Steps of a software update can be carried
out either on-site or off-site, by manual or automatic means. In this document on-site software update refers
to a software update carried out by a person at the site of the EUC installation with physical access to the EUC.
Off-site software update refers to a software updatesupdate, which cannot be considered as on-site.
Technical requirements for software update steps are defined in Clause 6.
ExampleAn example illustration of on-site and off-site software update, and advantages and disadvantages of
each method can be foundare provided in Annex A.
An example of a software update sequence is described in Annex B.
ISO/CD TSDTS 8102-21:2025(en)
Contextual information related to the product lifecyclelife cycle and installation lifecycle can be foundlife cycle
is provided in Annex C.
4.2 EUC domains with relevant security and safety requirements
EUC functions are divided toino four domains Safety, Essential, Alarm: "safety", "essential", "alarm" and
[2]
Other"other" in accordance with ISO 8102-20:2022,ISO 8102-20:2022 , Table 1. When the EUC is installed in
the building, cybersecurity requirements given in ISO 8102-20:2022 and other safety requirements given in
standards calling for use of this document, shall be met. The software of the three domains Safety,
Essential"safety", "essential" and Alarm,"alarm", may be updated after the installation of the EUC provided
that, if the requirements of this document, cybersecurity requirements given in ISO 8102-20:2022 and other
[2]
EUC requirements given in standards calling for use of this documentISO 8102-20:2022 are met, including
EUC safety requirements.
NOTE This document does not set any requirements for the domain Other."other".
5 Management of software update
5.1 General
This clause gives requirements on the management of software update:
a) requirements for the software development process;
Formatted: Numbered + Level: 1 + Numbering Style: a,
b, c, … + Start at: 1 + Alignment: Left + Aligned at: 0
b) requirements for the deployment of the software that apply both to on-site and off-site software updates;
cm + Indent at: 0 cm
c) requirements for an off-site software update management platform.
ChangeA change of a configuration parameter value shall be considered as software development if the impact
to the behaviorbehaviour of the component or the system has not been evaluated earlier during the software
development process.
5.2 Requirements for software development
The software development process shall complybe in accordance with the secure development lifecyclelife
cycle defined in ISO 8102-20:2022, clauseClause 4 and with the requirements given in standards calling for
use of this document, including processes relevant to safety requirements.
5.3 Requirements for the deployment of software update
5.3.1 Purpose of software update
The purpose of the software update shall be documented as peraccording to Clause 7 a).
EXAMPLE Purposes include:
— providing new features by the software update;
— cybersecurity or safety issues fixed by the software update;
— altering existing functions by the software update.
5.3.2 Preparations for software update
Preparations for a software update shall include at least the following.:
ISO/CD TSDTS 8102-21:2025(en)
— A process to record information about the current executable code identification, identification of
parameter sets or individual parameter values.
— A process to determine which delivery method(s) are used for the software update.
— A process to determine the EUC target(s) for the software update.
— A process to specify conditions to perform the software update.
— A process to specify corrective actions to be performed in the event of an unsuccessful software update,
including the information to the owner in case of unavailability (see the noteWARNING below).
— A process to specify the need for special equipment, a skilled person or actions to complete the software
update.
— A process to provide the information in the software update package about the software update, including
the necessary compatibility check information. See 6.5.1.
NOTE
WARNING — Unavailability of the EUC can lead to a hazardous situation in the building. Hazardous
Formatted: Notice
situations that can arise during the software update to consider include, but are not limited to, a
temporary loss of lift service where lift availability is critical to the operation of the facility, for
example hospitals. Mitigation can be established to address such hazards, such as planned deployment
rolloutroll-out of the software update.
5.4 Off-site software update management platform
5.4.1 Requirements for th
...