EN ISO 16484-5:2017/A1:2020

SLOVENSKI STANDARD
01-julij-2020
Sistemi za avtomatizacijo in regulacijo stavb - 5. del: Protokol za izmenjavo
podatkov - Dopolnilo A1 (ISO 16484-5:2017/Amd 1:2020)
Building automation and control systems (BACS) - Part 5: Data communication protocol -
Amendment 1 (ISO 16484-5:2017/Amd 1:2020)
Systeme der Gebäudeautomation - Teil 5: Datenkommunikationsprotokoll (ISO 16484-
5:2017) - Anderung (ISO 16484-5:2017/Amd 1:2020)
Systèmes d'automatisation et de gestion technique du bâtiment - Partie 5: Protocole de
communication de données - Amendement 1 (ISO 16484-5:2017/Amd 1:2020)
Ta slovenski standard je istoveten z: EN ISO 16484-5:2017/A1:2020
ICS:
35.240.67 Uporabniške rešitve IT v IT applications in building
gradbeništvu and construction industry
97.120 Avtomatske krmilne naprave Automatic controls for
za dom household use
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN ISO 16484-5:2017/A1
EUROPEAN STANDARD
NORME EUROPÉENNE
May 2020
EUROPÄISCHE NORM
ICS 35.240.67; 91.040.01
English Version
Building automation and control systems (BACS) - Part 5:
Data communication protocol - Amendment 1 (ISO 16484-
5:2017/Amd 1:2020)
Systèmes d'automatisation et de gestion technique du
bâtiment - Partie 5: Protocole de communication de
données - Amendement 1 (ISO 16484-5:2017/Amd
1:2020)
This amendment A1 modifies the European Standard EN ISO 16484-5:2017; it was approved by CEN on 18 April 2020.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for inclusion of
this amendment into the relevant national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This amendment exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the
same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2020 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 16484-5:2017/A1:2020 E
worldwide for CEN national Members.

Contents Page
European foreword . 3

European foreword
This document (EN ISO 16484-5:2017/A1:2020) has been prepared by Technical Committee ISO/TC
205 "Building environment design" in collaboration with Technical Committee CEN/TC 247 “Building
Automation, Controls and Building Management” the secretariat of which is held by SNV.
This Amendment to the European Standard EN ISO 16484-5:2017 shall be given the status of a national
standard, either by publication of an identical text or by endorsement, at the latest by November 2020,
and conflicting national standards shall be withdrawn at the latest by November 2020.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the
United Kingdom.
Endorsement notice
The text of ISO 16484-5:2017/Amd 1:2020 has been approved by CEN as EN ISO 16484-
5:2017/A1:2020 without any modification.

INTERNATIONAL ISO
STANDARD 16484-5
Sixth edition
2017-05
AMENDMENT 1
2020-04
Building automation and control
systems (BACS) —
Part 5:
Data communication protocol
AMENDMENT 1
Systèmes d'automatisation et de gestion technique du bâtiment —
Partie 5: Protocole de communication de données
AMENDEMENT 1
Reference number
ISO 16484-5:2017/Amd.1:2020(E)
©
ISO 2020
ISO 16484-5:2017/Amd.1:2020(E)

© ISO 2020
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2020 – All rights reserved

ISO 16484-5:2017/Amd.1:2020(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national
standards bodies (ISO member bodies). The work of preparing International Standards is normally
carried out through ISO technical committees. Each member body interested in a subject for which a
technical committee has been established has the right to be represented on that committee.
International organizations, governmental and non-governmental, in liaison with ISO, also take part in
the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all
matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. International Standards are 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 205, Building environmental design, in
collaboration with the European Committee for Standardization (CEN) Technical Committee CEN/TC
247, Building Automation, Controls and Building Management, in accordance with the Agreement on
technical cooperation between ISO and CEN (Vienna Agreement).
A list of all parts in the ISO 16484 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.
ISO 16484-5:2017/Amd.1:2020(E)
(This foreword is not part of the standard. It is merely informative and does not contain requirements necessary for
conformance to the standard.)
FOREWORD
The purpose of this addendum is to add several independent substantive changes to the BACnet standard. The changes
are summarized below.
135-2016bd-1. Add Staging Object Type.
135-2016be-1. Add Lighting BIBBS and Device Profiles.
135-2016bi -1. Add Audit Reporting.
135-2016bi -2. Change DeviceCommunicaitonControlService for Audit Reporting.
135-2016bi -3. Modify Logging Objects to Allow for Extremely Large Logs.
135-2016bk -1. Expand the reserved range of BACnetPropertyIdentifier.
135-2016bl - 1. Clarify Result(-) response for failed WritePropertyMultiple requests.
135-2016bl - 2. Clarify ReadPropertyMultiple response on OPTIONAL when empty.
135-2016bl - 3. Clarify Out_Of_Service.
135-2016bm-1. Reduce allowed range for Usage Timeout.
135-2016bm-2. Specify design choices for MS/TP devices.
125-2016bm-3. Handle unwanted MS/TP frames in IDLE state.
135-2016bn-1. Make SCHED BIBBs consistent on supported datatypes, and add BOOLEAN.
135-2016bn-2. Clarify COV and COVP related BIBBs.
135-2016bn-3. Clock is required for support of AE-ACK-A.
135-2016bp-1. Make rules for POST consistent with rules for PUT.
135-2016bp-2. Make 'type' consistent at all levels and introduce 'effectiveType'.
135-2016bp-3. Fully specify the behavior of "includes".
135-2016bp-4. Remove the path syntax from the 'select' query parameter.
135-2016bp-5. Resolve conflicting statements about configuring external authorization servers.
135-2016bp-6. Remove incorrect table for callback formats.
135-2016bp-7. Allow plain text POSTs for primitive data.
135-2016bp-8. Allow extended error numbers.
135-2016bp-9. Add new error numbers.
135-2016bp-10. Add formal definition for JSON equivalent to XML's .
135-2016bp-11. Specify 'name' safety check for setting data.
135-2016bp-12. Specify how to evaluate relative paths for collections of links.
135-2016bp-13. Allow proprietary categories for the 'metadata' query.
135-2016bq-1. Fix the Absentee_Limit property of the Access Credential object type.
135-2016bq-2. Ensure that the denied or granted access event is generated last.

In the following document, language to be added to existing clauses of EN ISO 16484-5 and Addenda is indicated
through the use of italics, while deletions are indicated by strikethrough. Where entirely new subclauses are proposed to
be added, plain type is used throughout.

The use of placeholders like X, Y, Z, X1, X2, etc., should not be interpreted as literal values of the final standard. These
placeholders will be assigned actual numbers/letters only with incorporation of this addendum into the standard for
republication.
iv © ISO 2020 – All rights reserved

ISO 16484-5:2017/Amd.1:2020(E)
Building automation and control systems (BACS) —
Part 5:
Data communication protocol
AMENDMENT 1
135-2016bd-1 Add a Staging Object Type

Rationale
The Staging object type provides a way for BACnet devices to map analog values onto multiple Binary Value, Binary
Output, or Binary Lighting Output objects.

A common use case is in lighting applications, where a level, identified by a numeric value, sets the appropriate values of
multiple binary outputs (on or off).

Support of this new object type is excluded from all data sharing BIBBs for life safety and access control.

[Insert new Clause 12.X]
12.X Staging Object Type
The Staging object type defines a standardized object whose properties represent the externally visible characteristics of a
staged value. A "Staging" maps a numeric value onto multiple discrete ranges that define individual “stages” (Nstages).
Each Staging object is associated with a collection of references to binary valued objects (N ). Each Staging object
references
may therefore control Binary Output, Binary Value, or Binary Lighting Output objects. Every stage specifies an arbitrary
combination of ACTIVE/INACTIVE values to be written to these referenced objects. Stages are defined by a limit, a
deadband, and the collection of values for the referenced objects.

Figure 12-X shows a typical Staging object application with four stages (Nstages =4) and two referenced binary objects
(N = 2).
references
ISO 16484-5:2017/Amd.1:2020(E)
Bit cleared -> INACTIVE
Bit set -> ACTIVE
Max_Pres_value = Stages[4].Limit
Stages[4].Values =
Stage 4
Stages[3].Limit
STAGE Stage 33 Stages[3].Values =
Stages[2].Limit
STAGE Stage 22 Stages[2].Values =
Stages[1].Limit
Stages[1].Values =
STAGE Stage 11
Min_Pres_Value
Target_References[1]={Device 2222, Binary Output 5}
Target_References[2]={Device 3333, Binary Output 27}

Figure 12-X. Typical Staging Application (Nstages =4, Nreferences = 2)

Present_Value > (Stages[2].Limit + Stages[2].Deadband)
Present_Value
Present_Stage = 3
Stage 3
Stages[2].Deadband
Stages[2].Limit
Stages[2].Deadband
Stage 2
Present_Value < (Stages[2].Limit - Stages[2].Deadband)
Present_Stage = 2
t
Present_Stage: 2 3 2 3 2
Figure 12-X2. Stage Limits incorporate hysteresis through the use of a Deadband around each Limit

Stages are defined by limits with a symmetrical deadband. A deadband greater than zero is used to prevent unwanted
oscillation when the Present_Value is close to a limit. As the Present_Value increases, if it rises above the limit for a
stage plus the deadband for that stage, the Present_Stage transitions to that stage+1. Similarly, as the Present_Value
...