CSA Group CSA T2000.1:25 National Standard of Canada Intelligent building systems objective-based Code (IBSC)

Preface

This is the first edition of CSA T2000.1, Intelligent building systems objective-based Code (IBSC).

This Code is considered suitable for use for conformity assessment within the stated scope of the Code.

This Code was prepared by the Subcommittee on Data Protection, Subcommittee on Data Collector, Subcommittee on Data Flow, Subcommittee on Data Management, and Subcommittee on Data Integrity, under the jurisdiction of the Technical Committee on Intelligent Building Systems and the Strategic Steering Committee on Information and Communications Technology, and has been formally approved by the Technical Committee.

This Code has been developed in compliance with Standards Council of Canada requirements for National Standards of Canada. It has been published as a National Standard of Canada by CSA Group.

Notes:

1) Use of the singular does not exclude the plural (and vice versa) when the sense allows.

2) Although the intended primary application of this Code is stated in its Scope, it is important to note that it remains the responsibility of the users of the Code to judge its suitability for their particular purpose.

3) This Code was developed by consensus, which is defined by CSA Policy governing standardization — Code of good practice for standardization as “substantial agreement. Consensus implies much more than a simple majority, but not necessarily unanimity”. It is consistent with this definition that a member may be included in the Technical Committee list and yet not be in full agreement with all clauses of this Code.

4) To submit a request for interpretation of this Code, please send the following information to [email protected] include “Request for interpretation” in the subject line:

a) define the problem, making reference to the specific clause, and, where appropriate, include a graphical image;

b) provide an explanation of circumstances surrounding the actual field condition; and

c) where possible, phrase the request in such a way that a specific “yes” or “no” answer will address the issue.Committee interpretations are processed in accordance with CSA Directives and guidelines governing standardization and are available on the Current Standards Activities page at standardsactivities.csagroup.org.

5) This Code is subject to review within five years from the date of publication. Suggestions for its improvement will be referred to the appropriate committee. To submit a proposal for change, please send the following information to [email protected] include “Proposal for change” in the subject line:

a) Standard designation (number);

b) relevant clause, table, and/or figure number;

c) wording of the proposed change; and

d) rationale for the change.

1 Scope

1.1 General

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 relation to the following data-centric criteria:

a) data protection;

b) data collection;

c) data flow;

d) data management; and

e) data integrity.

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

Notes:

1) Devices or systems that are disconnected and reconnected periodically are within the scope of this Code. 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.3 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.