Draft Details

Review start date:Mar 22, 2024
Review end date:May 21, 2024
Contact email:mary.morgan(at)csagroup.org
Draft Scope/Description:

This Code specifies objective-based requirements for system interoperability and for the safety, security, and privacy of persons and/or property against vulnerabilities of an intelligent building system (IBS) network. This Code also specifies requirements for resource efficiency and indoor air quality.

This Code outlines operational requirements for IBS networks in relations to the following data-centric criteria:

a)    data protection;
b)   data collectors;
c)    data flow;
d)   data management; and
e)    data integrity.

1.1 Inclusions

This Code applies to the following which should be considered to meet the objectives of this Code:  

a)    all type of data (including personal data) collected, processed, stored, or transmitted by the IBS network;

b)   all devices and systems that collect, process, store, or transmit data from building systems connected physically and/or logically to the IBS network;

c)    all devices and systems intended to be connected to the IBS network; and

d)   all resources required to manage or use the IBS network.


1)    Devices or systems that are disconnected and reconnected periodically are within the scope of this document. Systems or devices with no intention to reconnect are considered outside its scope.

2)    Cloud-connected systems are included as part of the IBS network.

1.2 Terminology

In this Code, “shall” is used to express a requirement, i.e., a provision that the user is obliged to satisfy in order to comply with the Code; “should” is used to express a recommendation or that which is advised but not required; and “may” is used to express an option or that which is permissible within the limits of the Code. 

Notes accompanying clauses do not include requirements or alternative requirements; the purpose of a note accompanying a clause is to separate from the text explanatory or informative material.

Notes to tables and figures are considered part of the table or figure and may be written as requirements.

Annexes are designated normative (mandatory) or informative (non-mandatory) to define their application.

You may comment on any section of this document by clicking the “Submit Comment” link at the bottom of the relevant section.