Building automation and control systems (BACS) — Part 2: Hardware

ISO 16484-2:2004 specifies the requirements for the hardware to perform the tasks within a building automation and control system (BACS). It provides the terms, definitions and abbreviations for the understanding of ISO 16484-2 and ISO 16484-3. ISO 16484-2:2004 relates only to physical items/devices, i.e. devices for management functions, operator stations and other human system interface devices; controllers, automation stations and application specific controllers; field devices and their interfaces; cabling and interconnection of devices; engineering and commissioning tools. ISO 16484-2:2004 shows a generic system model to which all different types of BACS and their interconnections (BACS network) can fit. A graphical concept of the BACS network in terms of LAN topology will be provided in ISO 16484-5.

Systèmes de gestion technique du bâtiment — Partie 2: Équipement

General Information

Status
Published
Publication Date
29-Jul-2004
Current Stage
9093 - International Standard confirmed
Start Date
12-Nov-2008
Completion Date
04-Oct-2018
Ref Project

Buy Standard

Standard
ISO 16484-2:2004 - Building automation and control systems (BACS)
English language
58 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

INTERNATIONAL ISO
STANDARD 16484-2
First edition
2004-08-01
Building automation and control systems
(BACS) —
Part 2:
Hardware
Systèmes de gestion technique du bâtiment —
Partie 2: Équipement
Reference number
ISO 16484-2:2004(E)
ISO 2004
---------------------- Page: 1 ----------------------
ISO 16484-2:2004(E)
PDF disclaimer

This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but

shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In

downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat

accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.

Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation

parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In

the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

© ISO 2004

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 ISO at the address below or

ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2004 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 16484-2:2004(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.

International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.

The main task of technical committees is to prepare International Standards. Draft International Standards

adopted by the technical committees are circulated to the member bodies for voting. Publication as an

International Standard requires approval by at least 75 % of the member bodies casting a vote.

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.

ISO 16484-2 was prepared by the European Committee for Standardization (CEN) in collaboration with

Technical Committee ISO/TC 205, Building environment design, in accordance with the Agreement on

technical cooperation between ISO and CEN (Vienna Agreement).

Throughout the text of this document, read "...this European Standard..." to mean "...this International

Standard...".

ISO 16484 consists of the following parts, under the general title Building automation and control systems

(BACS):
— Part 1: Overview and definitions
— Part 2: Hardware
— Part 3: Functions
— Part 4: Applications
— Part 5: Data communication protocol
— Part 6: Data communication — Conformance testing
— Part 7: Project implementation
© ISO 2004 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 16484-2:2004(E)

Contents Page

Foreword......................................................................................................................................................................v

Introduction.................................................................................................................................................................vi

1 Scope ..............................................................................................................................................................1

2 Normative references....................................................................................................................................1

3 Terms and definitions ...................................................................................................................................2

4 Abbreviations, acronyms and symbols, ...................................................................................................27

5 Requirements...............................................................................................................................................29

5.1 BACS components ......................................................................................................................................29

5.1.1 Hardware components and system functionality ....................................................................................29

5.1.2 System configuration..................................................................................................................................29

5.1.3 Basic hardware performance criteria ........................................................................................................30

5.2 Management devices...................................................................................................................................30

5.2.1 General .........................................................................................................................................................30

5.2.2 Data processing device, server station.....................................................................................................31

5.2.3 Peripherals ...................................................................................................................................................31

5.2.4 Interfaces......................................................................................................................................................33

5.2.5 Alarm indication and annunciation devices .............................................................................................34

5.3 Control devices............................................................................................................................................34

5.3.1 General .........................................................................................................................................................34

5.3.2 Controller......................................................................................................................................................36

5.3.3 Application specific controller...................................................................................................................42

5.4 Field devices ................................................................................................................................................43

5.4.1 General .........................................................................................................................................................43

5.4.2 Coupling module .........................................................................................................................................43

5.4.3 Local override/indication device................................................................................................................44

5.4.4 Sensors.........................................................................................................................................................45

5.4.5 Actuators......................................................................................................................................................47

5.4.6 Room device ................................................................................................................................................50

5.5 Cabling..........................................................................................................................................................50

5.6 System communications ............................................................................................................................51

5.6.1 General .........................................................................................................................................................51

5.6.2 Interconnection of devices within networks.............................................................................................53

5.6.3 Interconnection of devices between networks.........................................................................................53

5.6.4 Communications protocol..........................................................................................................................54

5.7 Engineering/commissioning tools.............................................................................................................54

5.7.1 General .........................................................................................................................................................54

5.7.2 Engineering tools ........................................................................................................................................54

5.7.3 Commissioning tools ..................................................................................................................................54

Annex A (informative) General safety requirements and environmental conditions.........................................56

A.1 General .........................................................................................................................................................56

A.2 National annexes .........................................................................................................................................56

Annex ZA (normative) Normative references to international publications with their corresponding

European publications................................................................................................................................57

Bibliography..............................................................................................................................................................58

iv © ISO 2004 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 16484-2:2004(E)
Foreword

This document (EN ISO 16484-2:2004) has been prepared by CEN /TC 247, "Building Automation, Controls and

Building Management", the secretariat of which is held by the SNV, in collaboration with ISO/TC 205 "Building

Environment Design".

This document has to be implemented at national level, either by publication of an identical text or by

endorsement, by February 2005, and conflicting national standards have to be withdrawn by February 2005.

The EN ISO 16484-2 is part of the EN ISO 16484 series of International Standards under the general title

Building Automation and Control Systems (BACS), which will comprise the following parts:

Part 1: Overview and Vocabulary
Part 2: Hardware
Part 3: Functions
Part 4: Applications
Part 5: Data communication - Protocol
Part 6: Data communication - Conformance testing
Part 7: Project specification and implementation

In this standard, Annex A: General safety requirements and environmental conditions and the Bibliography are

both informative.

The Annex ZA Normative references to international publications with the corresponding European publications,

is normative.

NOTE National annexes may contain information provided for easier implementation, e.g. an alphabetical index or national

footnotes.

According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following

countries are bound to implement this European Standard: Austria, Belgium, Cyprus, Czech Republic, Denmark,

Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg,

Malta, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland and United

Kingdom
© ISO 2004 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO 16484-2:2004(E)
Introduction

This series of standards is intended for design of new buildings and retrofit of existing buildings for an

acceptable indoor environment, practical energy conservation and efficiency.
The application of this series of standards for BACS is envisaged as follows:

- the environmental design for all building types requires complex methods for automation and control. The

functional integration of services other than HVAC e.g. lighting and electric power distribution control, security

control, transportation, maintenance management or facilities management is a general task for all parties

employed to develop an integrated multi-application system. This integration allows the user to take advantage

of synergies between the different applications. This standard will give guidance to architects, consultants and

contractors as well as to users on how to share such resources,

- the innovation cycles between devices, systems and networks vary. To make it possible to add and to change

existing devices, and extend the building automation and control network, several interfaces both proprietary and

standardized are defined between the BACS network and the other systems. A manufacturer can design a

product, both to meet his specific marketing objectives and to give the option to integrate that special device into

a multi-application BACS. Interfaces are also defined in appropriate parts of this standard along with the

necessary communications protocol and conformance test required to support the inter-working of devices,

- a manufacturer, a systems house, or an electrical or mechanical contractor can assemble an implementation of

a building automation and control system,

- the application of this standard is not to standardize the hardware and software design or the architecture of a

System, but to define the process for the creation of project specifications, where functionality and the quality of

the solution are clearly defined.

The purpose of this series of standards is intended for use by those involved in the design, manufacture,

engineering, installation, commissioning, operational maintenance and training of BACS when contracted, i.e.:

 as a guide to the terminology of the building automation and control trade. Unambiguous terminology is

required for a complete and accurate conveyance of the intent and details of this standard;

 in product development, to avoid unnecessary duplication of function or terminology, but should not place a

restraint on the evolution of new products, systems or applications;

 as a basis for interfacing products and systems. In order to interoperate, the elements of a BACS require a

unified data communication protocol and information model;

 as a basis for drawing up a project specification for the procurement of building automation and control

products for systems suppliers and customers;

 as a code of practice for expertly commissioning prior to handover of a system;

 by educational establishments wishing to train people in the field of building automation and control systems.

This entire series of BACS standards consists of the following contents:
Part 1: Overview and definitions (in preparation)

Part 1 of this standard describes the objectives and interrelationships of all parts of this standard. It provides an

overview and detailed information about the structure of the related series of standards for the BACS industry.

This part of the standard provides also the vocabulary with terms and definitions for the understanding of the

entire series of this standard and it contains a translation of the main terms in English, French, Russian, and

German in an informative annex.
vi © ISO 2004 – All rights reserved
---------------------- Page: 6 ----------------------
ISO 16484-2:2004(E)

This ongoing work is coordinated at expert level with standards work from ISO/TC 205 WG 3 and CEN/TC 247/

WG 3, WG 4, WG 5 and WG 6.
Part 2: Hardware (refer to the scope of this part)
Part 3: Functions

Part 3 of this standard specifies the requirements for the overall functionality and engineering services to

achieve building automation and control systems. It defines terms, which shall be used for specifications and it

gives guidelines for the functional documentation of project/application specific systems. It provides a template

for documentation of plant/application specific functions, called BACS function list in annex A.

The informative function block examples explain a method to display the referenced functions in system

documentation; they do not standardize the method for programming functions and applications.

This Part 3 of the standard covers the following:

Requirements and definitions regarding BACS and application software, generic functions for plant/project

specific applications and engineering functions for building controls and operations. It provides communication

functions for the integration of other dedicated special system processes. The functional requirements in this

part of the standard are subdivided as follows:
 System management and application software:

describes the requirements for plant independent system and human system interface programs related to a

project, including the operating system. This standard does not dedicate the following system functionality to

any particular hardware, e.g.:

 system diagnostics, watchdog, redundancy, time keeping, access control, log lists;

 point identification, event message handling, print control;
 database, statistics, data archiving, remote access;
 system communications.

 Human system interface (HSI), point information presentation, graphics, alarms, time scheduling

 Engineering process and tool software:

describes the requirements for configuring of the hardware and control strategies, the system management

and the commissioning process.
 BACS application processing programs and plant/application specific functions:

describes the requirements for plant, application and / or project specific functions and a method for the

documentation of a project. The functions are subdivided into the following types:

 input and output functions;
 processing functions;
 management functions and required communications;
 operator functions.

Part 3 defines a method for creating the procurement specifications containing all essential elements required for

the operational functioning of a BACS. The successful installation and operation of a BACS requires that its

procurement be based on a complete specification with accurately defined functions.

The standard provides a template called the ‘BACS function list’ that can be found in annex A (normative). Its

purpose is to determine and document the options for plant / application specific functionality. Further

© ISO 2004 – All rights reserved vii
---------------------- Page: 7 ----------------------
ISO 16484-2:2004(E)

explanations can be given in form of plant/control descriptions, control flow chart diagrams, and plant/control

schematics. Examples are given in annex B (informative). The exact specifications will be project-specific.

Information about the standardized functions is given in the form of informative examples as function-blocks,

textual, and graphical descriptions in 5.5.

It is recognized, that functions can be described and implemented in many different ways, depending on:

 climatic differences;
 cultural and regional differences;
 national regulations.
Part 4: Applications

Part 4 of this standard specifies the requirements for specific communicating applications/devices, e.g. for

general room automation and for sophisticated optimization of controls for heating, fan coil and induction units,

CAV, VAV and radiant cooling.

This work will be coordinated at expert level with standards work from ISO/TC 205 WG 3 and CEN/TC 247.

Part 5: Data Communication – Protocol

Part 5 of this standard specifies data communication services and objects for computer equipment and

controllers used for monitoring and control of HVAC&R and other systems of building services.

This protocol provides a comprehensive set of objects for conveying encoded binary, analog, and alphanumeric

data between devices including, but not limited to:
 input measuring: analog input object;
 output positioning/set-point: analog output object;
 binary input counting;
 input state: binary input object, multi-state input;
 output switching: binary output object, multi-state output;

 values: analog value, binary value, multi-state value, accumulated value, averaging object, trend log object;

 text string;
 schedule information;
 alarm and event information;
 files; and
 control programs and parameters respectively.

This protocol models each building automation and control system as a collection of data structures called

objects, the properties of which represent various aspects of the hardware, software, and operation of the

device. These objects provide a means of identifying and accessing information without requiring knowledge of

the details of the device's internal design or configuration.

An overview of possible integration with other systems in buildings, e.g. fire, security, access control, maintenance

and facilities management, is shown in Figure 1 of Part 2 of this standard.
viii © ISO 2004 – All rights reserved
---------------------- Page: 8 ----------------------
ISO 16484-2:2004(E)
Part 6: Data Communication – Conformance testing

Part 6 of the standard specifies the technical requirements of the conformance test suite and the methods for

testing the products for the conformance with the protocol. It provides a comprehensive set of procedures for

verifying the correct implementation of each capability claimed on a BACS network protocol implementation

conformance statement (PICS) including:

a) support of each claimed BACS network service, either as an client (initiator), server (executor), or both;

b) support of each claimed BACS network object-type, including both required properties and each claimed

optional property;
c) support of the BACS network layer protocol;
d) support of each claimed data link option, and
e) support of all claimed special functionality.
Part 7: Project specification and implementation

Part 7 of this standard specifies methods for project specification and implementation of BACS and for

integration of other systems into the BACS. This standard defines terms to be used for project specifications and

gives guidelines for integration of other systems.
a) Project specification and implementation:

This clause of the standard describes the procedures (codes of practice) required for the following:

 project specification;

These procedures also contain an example for a plant/system/customer premises wide unique

structured addressing system for data point identification;
 engineering;
 installation;
 project handover.
b) System integration:

This clause of the standard describes the special requirements/procedures for the integration and

implementation of intersystem communication with foreign systems and the interconnection of other

units/devices with integrated communications interfaces, e.g. chillers, elevators.

© ISO 2004 – All rights reserved ix
---------------------- Page: 9 ----------------------
ISO 16484-2:2004(E)
1 Scope

This part of the standard specifies the requirements for the hardware to perform the tasks within a BACS. It

provides the terms, definitions, and abbreviations for the understanding of Part 2 and Part 3.

Part 2 relates only to physical items/devices, i.e.:
 operator stations and other human system interface devices;
 devices for management functions;
 control devices, automation stations and application specific controllers;
 field devices and their interfaces;
 cabling and interconnection of devices;
 engineering and commissioning tools.

This part of this standard shows a generic system model to which all-different types of BACS and their

interconnections (BACS network) can fit. A graphical concept of the BACS network in terms of LAN and inter-

network topology will be provided in Part 5 of this standard.
National annexes:

National annexes may specify the local requirements of physical and electrical characteristics, the verifications

for BACS devices and equipment, and the code of practice for the physical installation of systems. The annexes

shall refer to the regional implementations of the relevant IEC standards.
2 Normative references

The following referenced documents are indispensable for the application 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 60050-351 International Electrotechnical Vocabulary — Part 351: Automatic control

Degrees of protection provided by enclosures (IP code)
IEC 60529:1989
+ AMD1:1999
Insulation coordination for equipment within low-voltage systems — Part 1:
IEC 60664-1:1992
+AMD1:2000 Principles, requirements and tests
+AMD2:2002

IEC 60715:1981 Dimensions of low-voltage switchgear and controlgear — Standardized mounting on

rails for mechanical support of electrical devices in switchgear and controlgear
+AMD1:1995
installations
Programmable controllers — Part 3: Programming languages
IEC 61131-3:2003

ISO/IEC 2382-1:1993 Information technology — Vocabulary — Part 1: Fundamental terms

ISO/IEC 2382-18:1999 Information technology — Vocabulary — Part 18: Distributed data processing

ISO/IEC 2382-26:1993 Information technology — Vocabulary — Part 26: Open Systems Interconnection

Information technology — Open Systems Interconnection — Basic reference model —
ISO/IEC 7498-1:1994
Part 1: The basic model
Information technology — Open Distributed Processing — Reference model — Part 2:
ISO/IEC 10746-2:1998
Foundations
Standardization and related activities — General vocabulary
ISO/IEC Guide 2:1996
© ISO 2004 – All rights reserved 1
---------------------- Page: 10 ----------------------
ISO 16484-2:2004(E)
3 Terms and definitions

This clause presents the vocabulary used in this Part 2 and Part 3 of the standard for BACS.

The terms and definitions listed in this standard but defined by other relevant ISO/IEC International Standards are

repeated below for convenience in most cases.

NOTE Other language versions may contain an alphabetical index in National Annexes.

For the purposes of this standard, the following terms and definitions apply.
3.1
3-point control

control function with a three-position output that can assume only three discrete values: zero and two values with

opposite signs. These output values are used to position with two binary signals providing three control states

EXAMPLE
a) opening, stopped, closing;
b) more, neutral, less;
c) heating, neutral, cooling.
3.2
access control

method for determining or restricting access to system and network resources

[Part 5, 3.2.1]
cf. access control system (3.3)
NOTE 1 Also refer to security and operator authentication.

NOTE 2 Data privacy protection is the framework conditions protecting personal data from being used by any one other

than the owner (regulated by national law).

NOTE 3 Data security is the framework conditions to protect data from direct or indirect manipulation or unauthorized use.

Data manipulation includes loss of data, destruction or falsification of data.

NOTE 4 Data security means are the measures and equipment to secure and maintain the safety of data.

3.3
access control system
1) a dedicated special system for security
cf. access control (3.2)

2) automatic checking of access rights under organizational measures and barrier/door control for

buildings/rooms, including registration of events
NOTE An access control system belongs to security systems.
3.4
acknowledge

the recognition and/or registration of an event (e.g. alarm) by an operator

NOTE An acknowledgement can be invoked by an operator using a physical device, or by using a human system interface

e.g. selecting an Icon on a VDU.
3.5
acknowledgement

a function that allows a destination node to inform a sending node of the receipt of a

protocol-data-unit
[ISO/IEC 7498-1:1994]
2 © ISO 2004 – All rights reserved
---------------------- Page: 11 ----------------------
ISO 16484-2:2004(E)
3.6
actuator

field device (3.80) that interfaces to control a plant process, operated electrically, pneumatically, or

hydraulically. It influences the mass flow or energy flow
c.f. positioning actuator (3.153)

NOTE 1 A control valve is the combination of a valve with its operating element.

NOTE
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.