EN ISO 16484-1:2024
(Main)Building automation and control systems (BACS) - Part 1: Project specification and implementation (ISO 16484-1:2024)
Building automation and control systems (BACS) - Part 1: Project specification and implementation (ISO 16484-1:2024)
This document specifies guiding principles for project design and implementation and for the integration of other systems into the building automation and control systems (BACS).
This document specifies the phases required for the BACS project, including
— design (determination of project requirements and production of design documents including technical specifications),
— engineering (detailed function and hardware design),
— installation (installing and commissioning of the BACS), and
— completion (handover, acceptance and project finalization).
This document also specifies the requirements for as-built documentation and training.
This document is not applicable to operation and maintenance, nor is it applicable to retro or continuous commissioning, including a commissioning authority.
Systeme der Gebäudeautomation (GA) - Teil 1: Projektplanung und -ausführung (ISO 16484-1:2024)
Dieses Dokument legt Leitsätze der Projektplanung und ausführung und der Integration anderer Systeme in die GA-Systeme fest.
Es beschreibt die für ein GA-Projekt erforderlichen Phasen, wie:
Planung (Bestimmung der Projektanforderungen und Erstellen von Auslegungsdokumenten einschließlich technischer Spezifikationen);
technische Bearbeitung (en: Engineering) (detaillierte Planung der Funktionen und der Hardware);
Installation (Montage und Inbetriebnahme des GA-Systems);
Abschluss (Übergabe, Abnahme und Fertigstellung).
Dieses Dokument legt außerdem die Anforderungen an die Bestandsdokumentation und die Schulung fest.
Dieses Dokument gilt weder für die Bedienung und die Instandhaltung, noch für eine nachträgliche oder laufende Inbetriebnahme, einschließlich eines Inbetriebnahmemanagements.
Systèmes de gestion technique du bâtiment (SGTB) - Partie 1: Spécifications et mise en œuvre d'un projet (ISO 16484-1:2024)
Le présent document spécifie les principes directeurs pour la conception et la mise en œuvre du projet ainsi que pour l’intégration d’autres systèmes dans les systèmes de gestion technique du bâtiment (SGTB).
Le présent document spécifie les phases requises pour le projet de SGTB, telles que
— la conception (détermination des exigences du projet et production des documents de conception incluant les spécifications techniques),
— l’ingénierie (conception détaillée des fonctions et du matériel),
— l’installation (installation et mise en service du SGTB), et
— la finalisation (réception technique, acte de réception technique et achèvement technique du projet).
Le présent document spécifie également les exigences relatives à la documentation et à la formation conformes à l’exécution.
Le présent document ne s’applique pas au fonctionnement et à la maintenance, ni à la mise en service rétroactive ou à la mise en service continue impliquant une autorité de mise en service.
Sistemi za avtomatizacijo in regulacijo stavb - 1. del: Specifikacija projekta in izvedba (ISO 16484-1:2024)
Standard ISO 16484-1:2010 določa vodilna načela za projektiranje in izvedbo ter integracijo drugih sistemov v sisteme za avtomatizacijo in regulacijo stavb (BACS).
Standard ISO 16484-1:2010 določa faze, ki so potrebne za projekt sistema za avtomatizacijo in regulacijo stavb, vključno s/z:
zasnovo (določanje projektnih zahtev in priprava projektne dokumentacije, vključno s tehničnimi specifikacijami),
inženiringom (podrobno delovanje in zasnova strojne opreme),
namestitvijo (namestitev in začetek uporabe sistema za avtomatizacijo in regulacijo stavb) in
zaključkom (predaja, prevzem in zaključek projekta).
Standard ISO 16484-1:2010 prav tako določa zahteve za dokumentacijo izvedenih del in usposabljanje.
Standard ISO 16484-1:2010 se ne uporablja za upravljanje in vzdrževanje, kot tudi ne za izvajanje za nazaj ali nenehno izvajanje, vključno z organom za izvajanje.
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-april-2024
Sistemi za avtomatizacijo in regulacijo stavb - 1. del: Specifikacija projekta in
izvedba (ISO 16484-1:2024)
Building automation and control systems (BACS) - Part 1: Project specification and
implementation (ISO 16484-1:2024)
Systeme der Gebäudeautomation (GA) - Teil 1: Projektplanung und -ausführung (ISO
16484-1:2024)
Systèmes de gestion technique du bâtiment (SGTB) - Partie 1: Spécifications et mise en
oeuvre d'un projet (ISO 16484-1:2024)
Ta slovenski standard je istoveten z: EN ISO 16484-1:2024
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-1
EUROPEAN STANDARD
NORME EUROPÉENNE
January 2024
EUROPÄISCHE NORM
ICS 91.040.01; 35.240.67 Supersedes EN ISO 16484-1:2010
English Version
Building automation and control systems (BACS) - Part 1:
Project specification and implementation (ISO 16484-
1:2024)
Systèmes de gestion technique du bâtiment (SGTB) - Systeme der Gebäudeautomation (GA) - Teil 1:
Partie 1: Spécifications et mise en œuvre d'un projet Projektplanung und -ausführung (ISO 16484-1:2024)
(ISO 16484-1:2024)
This European Standard was approved by CEN on 23 December 2023.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a 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 European Standard 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, Türkiye 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
© 2024 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 16484-1:2024 E
worldwide for CEN national Members.
Contents Page
European foreword . 3
European foreword
This document (EN ISO 16484-1:2024) 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 European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by July 2024, and conflicting national standards shall be
withdrawn at the latest by July 2024.
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.
This document supersedes EN ISO 16484-1:2010.
Any feedback and questions on this document should be directed to the users’ national standards
body/national committee. A complete listing of these bodies can be found on the CEN website.
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, Türkiye and the
United Kingdom.
Endorsement notice
The text of ISO 16484-1:2024 has been approved by CEN as EN ISO 16484-1:2024 without any
modification.
International
Standard
ISO 16484-1
Second edition
Building automation and control
2024-01
systems (BACS) —
Part 1:
Project specification and
implementation
Systèmes de gestion technique du bâtiment (SGTB) —
Partie 1: Spécifications et mise en œuvre d'un projet
Reference number
ISO 16484-1:2024(en) © ISO 2024
ISO 16484-1:2024(en)
© ISO 2024
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
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
ISO 16484-1:2024(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 3
5 Requirements and recommendations . 4
5.1 Overview .4
5.1.1 General .4
5.1.2 Phases of the BACS project .4
5.1.3 Documentation.5
5.1.4 Training .5
5.1.5 Reviewing and improving building performance .5
5.1.6 Graphical overview .5
5.2 Design phase .6
5.2.1 General .6
5.2.2 Determination of project requirements .7
5.2.3 Project planning and organization.11
5.2.4 Design documents and technical specification . 12
5.2.5 Contract . 13
5.3 Engineering phase . 13
5.3.1 General . 13
5.3.2 Project planning and coordination details . 13
5.3.3 Detailed hardware and function design . 13
5.3.4 Approval of design submittals .14
5.3.5 Hardware configuration .14
5.3.6 Control strategy configuration .14
5.3.7 Management and operator function configuration . 15
5.3.8 System test . 15
5.4 Installation phase .16
5.4.1 General .16
5.4.2 Installation .16
5.4.3 BACS commissioning .17
5.5 Completion phase .18
5.5.1 General .18
5.5.2 System demonstration .19
5.5.3 Operator training .19
5.5.4 Handover .19
5.5.5 Acceptance . 20
5.5.6 Finalization . 20
5.5.7 Completion decision . 20
5.6 Documentation . 20
5.6.1 General . 20
5.6.2 User documents . 20
5.6.3 Datasheets . 20
5.6.4 Operation and maintenance documents . 20
5.7 Training .21
6 Review and improvement of building performance .21
Bibliography .22
iii
ISO 16484-1:2024(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 document 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).
ISO draws attention to the possibility that the implementation of this document may involve the use 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.
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 environment 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).
This second edition cancels and replaces the first edition (ISO 16484-1:2010), which has been technically
revised.
The main changes are as follows:
— updating of normative references;
— updating of terms and definitions;
— mention of cyber security measures and wireless communication.
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.
iv
ISO 16484-1:2024(en)
Introduction
The ISO 16484 series is aimed at the design of new buildings and the retrofitting of existing buildings for an
acceptable indoor environment, practical energy conservation and efficiency.
The ISO 16484 series is applicable to building automation and control systems (BACS), as follows:
— The environmental design for all building types requires complex methods of automation and control.
The functional integration of services other than heating, ventilating and air conditioning (HVAC) is a
general task for all parties employed to develop an integrated multi-application system. The integration
comprises, for example, lighting and electric power distribution control, security control, transportation,
maintenance management or facilities management. This system integration allows the user to take
advantage of synergies between the different applications. The ISO 16484 series gives guidance to
architects, consultants and contractors as well as guidance to users on how to share such resources.
— The innovation cycles between devices, systems and networks vary. In order 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 their 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 the ISO 16484 series along with the necessary communications protocol and
conformance test required to support the interworking of devices.
— A manufacturer, a systems house, or an electrical or mechanical contractor can assemble the
implementation of a building automation and control system.
— The application of the ISO 16484 series 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 the
functionality and the quality of the solution are clearly defined.
The ISO 16484 series 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 guideline 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 the ISO 16484 series;
— in product development, to avoid unnecessary duplication of function or terminology, but not necessarily
placing 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 procurement;
— as a code of practice for expert commissioning;
— by educational establishments wishing to train people in the field of BACS.
v
International Standard ISO 16484-1:2024(en)
Building automation and control systems (BACS) —
Part 1:
Project specification and implementation
1 Scope
This document specifies guiding principles for project design and implementation and for the integration of
other systems into the building automation and control systems (BACS).
This document specifies the phases required for the BACS project, including
— design (determination of project requirements and production of design documents including technical
specifications),
— engineering (detailed function and hardware design),
— installation (installing and commissioning of the BACS), and
— completion (handover, acceptance and project finalization).
This document also specifies the requirements for as-built documentation and training.
This document is not applicable to operation and maintenance, nor is it applicable to retro or continuous
commissioning, including a commissioning authority.
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.
ISO/IEC 14763-2, Information technology — Implementation and operation of customer premises cabling —
Part 2: Planning and installation
ISO 16484-2, Building automation and control systems (BACS) — Part 2: Hardware
ISO 16484-5, Building automation and control systems (BACS) — Part 5: Data communication protocol
ISO 16484-6, Building automation and control systems (BACS) — Part 6: Data communication conformance
testing
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 16484-2, ISO 16484-5, ISO 16484-6
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/
ISO 16484-1:2024(en)
3.1
acceptance
decision and act of signing the handover (3.10) document during the completion (3.6) phase
Note 1 to entry: The transfer of the responsibility for the system(s) from the supplier to the customer or their
representative can be a legal act.
3.2
building performance
set of measurable building characteristics
Note 1 to entry: This includes e.g. energy efficiency, indoor air quality, moisture management and thermal comfort.
Note 2 to entry: This is also influenced by building construction and utilization, installed technical services and their
operation.
3.3
building automation and control system (BACS) commissioning
BACS commissioning
project and system-specific process of calibrating field devices, testing data points, adjusting parameters,
verifying sequences of operation and other functionalities for the various elements of a BACS application
Note 1 to entry: The BACS commissioning is a part of the engineering (3.7) services and includes commissioning
activities at the installation phase.
Note 2 to entry: Commissioning reports are proof of the completeness of tasks and work.
Note 3 to entry: There are country variations in the naming of the term “commissioning” and variations in the tasks
covered by this term.
3.4
commissioning process
systematic application of processes and procedures designed to ensure that the project objectives are
achieved and maintained throughout the building lifetime
Note 1 to entry: The commissioning process begins at project conception and continues through to the pre-design,
design, construction, start-up, turnover and occupancy to the operation phase.
Note 2 to entry: Details of how to conduct the commissioning process are outside the scope of this document.
3.5
commissioning authority
entity identified by the owner who leads, plans, schedules and coordinates the commissioning team to
implement the commissioning process (3.4)
Note 1 to entry: In some countries, there are “certified commissioning authorities”.
3.6
completion
project phase where, when handover (3.10) and finalization (3.8) are achieved, the implementation of the
building automation and control system (BACS) project can be considered as completed
3.7
engineering
acquiring and applying technical knowledge to design and implement devices, systems and processes that
realize the desired objective
Note 1 to entry: This includes project and system-specific services for planning, configuring and commissioning of the
various parts of a building automation and control system (BACS).
3.8
finalization
task during the project completion (3.6) phase where the supplier resolves outstanding items
ISO 16484-1:2024(en)
3.9
functional description
overall description that explains how each part of the system/plant is expected to operate, interact and be
interacted with
Note 1 to entry: The description covers material energy and signal flow of a plant or a system. Functions/operations
are described as: storing, transmitting, converting, transforming and interlinking.
3.10
handover
formal process that transfers a system or part of a system usage from the supplier to the customer or their
representative
Note 1 to entry: The transfer of the operational responsibility for the system from the supplier to the customer can be
a legal act or be agreed by contract.
3.11
installation instruction
document that explains how to install a technical device
Note 1 to entry: There can be several installation instructions for a device, e.g. mechanical, electrical.
Note 2 to entry: Installation instructions can be found from many sources, e.g. directives, standards, guidelines,
professional recommendations, manufacturer's instructions for products.
3.12
interoperability
seamless interworking of devices and functions in a system and ability of a system to work with or use the
parts or equipment of another system
Note 1 to entry: Functions may be, e.g. data sharing, event and alarm management, scheduling, trend and event
logging, device and network management.
3.13
migrate, verb
modernize the implemented software or the hardware under extensive utilization of the present
infrastructure
3.14
system integration
bringing together subsystems into one system to function together as a system
4 Abbreviated terms
For the purposes of this document, the symbols, abbreviations and acronyms given in ISO 16484-2,
ISO 16484-5, ISO 16484-6 and the following apply.
BACS building automation and control system
EMC electromagnetic compatibility
EMP electromagnetic pulse
HVAC heating, ventilating and air conditioning
LEMP lightning electromagnetic pulse
UPS uninterruptible power supply
VPN virtual private network
ISO 16484-1:2024(en)
5 Requirements and recommendations
5.1 Overview
5.1.1 General
The BACS project normally commences after the client appoints a BACS consultant or supplier.
The quality of the implementation of a BACS is dependent on the design of building systems and the
specification of the commissioning process. In order to produce and maintain the required quality of
building performance after the implementation has been completed, application of a commissioning process
for review and improvement of commissioned values is recommended. Retro or continuous commissioning,
including a commissioning authority, is not within the scope of this document.
5.1.2 Phases of the BACS project
5.1.2.1 General
Subclause 5.1.2 specifies the main actions and decisions required in order to implement a project in the
different phases (see Figure 1). It serves for all the parties involved in the different phases of a project.
The phases of a project associated with the implementation of a BACS are as follows. For all cybersecurity
measures, IEC/TS 62443-1-1 should be taken into account.
5.1.2.2 Design phase
The design phase consists of
a) the determination of project requirements,
b) the project planning and organization,
c) the technical specification, and
d) the establishment of a contract.
5.1.2.3 Engineering phase
The engineering phase consists of
a) project planning and coordination,
b) detailed function and hardware specification design,
c) engineering design approval,
d) hardware configuration,
e) control strategy and processing functions configuration,
f) management and operator functions configuration, and
g) system testing.
5.1.2.4 Installation phase
The installation phase consists of
a) installing, and
b) BACS commissioning.
ISO 16484-1:2024(en)
5.1.2.5 Completion phase
The completion phase consists of
a) system demonstration,
b) operator training,
c) handover,
d) acceptance,
e) finalization, and
f) completion decision.
5.1.3 Documentation
Work done during the engineering, installation and completion phases serves as a basis for providing as-
built documentation (see 5.6).
5.1.4 Training
Work done during the engineering, installation and completion phases serves as a basis for providing
training (see 5.7).
5.1.5 Reviewing and improving building performance
This phase has been included for completeness. It does not form part of a BACS project but, after
completion, improved building performance (according to the actual use) can be achieved by the BACS if the
commissioned values are reviewed and amended periodically, providing improved energy performance and
reduced operating costs. This can be achieved through the commissioning process, which is not covered in
this document.
5.1.6 Graphical overview
A possible sequence of the important decisions and activities in each phase is shown in Figure 1. It is not
prescriptive; some activities can be carried out earlier or later, depending on the project requirements, e.g.
documentation and training.
ISO 16484-1:2024(en)
Figure 1 — Process and structure of BACS project implementation
5.2 Design phase
5.2.1 General
Subclause 5.2 specifies tasks to be carried out in the design process of the various parts of a BACS. It is
assumed that at the start of the design process, the information necessary in order to accommodate a BACS
is available. The tasks to perform are project and system-specific.
ISO 16484-1:2024(en)
The design phase covers the following areas:
a) determination of project requirements;
b) project planning and organization;
c) design documents and technical specification;
d) the contract.
Owners and users of buildings can benefit from the integration of various technical building systems. In cases
of system integration, it is important that parties agree on the particular meaning of system integration
with respect to the specific project requirements. Project management consideration shall be given to the
functional operation responsibility for attached subsystems.
5.2.2 Determination of project requirements
5.2.2.1 Overview
To meet the client's requirements, the general project requirements for the BACS should take into account
the following:
a) general considerations;
b) integration requirements;
c) physical attributes;
d) occupational needs;
e) system requirements;
f) site and client-specific requirements.
Attention should also be given to energy performance in accordance to ISO 52120-1 and ISO 52127-1.
The description of project requirements shall be approved by the client.
5.2.2.2 General considerations
When determining the system requirements, the following factors should be taken into account:
a) building structure, e.g. metal frame, concrete, size, thermally active building components, historical
construction (listed objects);
b) type of building(s), e.g. high rise, one storey, open campus, tunnel;
c) building usage type and profile, e.g. hospital, single/multi-tenant, industrial, commercial, residential;
d) space usage profile, e.g. occupation schemes, diverse usage of space, continuous operation;
e) system integrity including off-site considerations, e.g. communication infrastructure and topology,
availability, reliability, response time, safety and security, redundancy;
f) EMC, EMP and LEMP requirements according to IEC 62305-4;
g) intended organization of operation and technical services, e.g. third party, caretaker, trade segregation,
user account levels;
h) energy supply needs, e.g. alternative energy systems, load shedding, energy monitoring;
i) safety and security systems integration with BACS and mutual interaction, e.g. fire system, access
control system, interoperability area and integration depth;
ISO 16484-1:2024(en)
j) implementation of the project by phases, e.g. timescales for each phase, constraints on plant shutdowns,
impact on continuous operation;
k) budget, e.g. change contingency, overtime work;
l) future usage, e.g. spare capacity, flexibility, future intended extensions;
m) application of the commissioning process.
5.2.2.3 Integration requirements
5.2.2.3.1 Overview
This document specifies general considerations for integration that shall be implemented in the following
categories:
a) integration/implementation;
b) integration/operation;
c) integration/function;
d) integration/infrastructure.
5.2.2.3.2 Integration/general considerations
As for integration, the following should be generally considered:
a) the deployment of special system integration consultants;
b) the allocation of responsibilities, e.g. for subsystem functionality and interfaces, for delivery of
integration of subsystems;
c) vendor and manufacturer independence, e.g. standardized protocols, profiles and interfaces;
d) enhanced energy performance, e.g. interdisciplinary operations of HVAC, blinds and lighting controls;
e) compatibility, e.g. software/hardware versions of subsystems, protocol versions, proprietary protocols;
f) interoperability, e.g. data sharing, event and alarm management, scheduling, trend and event logging,
device and network management;
g) functional interaction, e.g. fans disabled by fire conditions;
h) single seat operation, e.g. shared computer, consolidated user information and alarms;
i) infrastructure sharing, e.g. wireless, structured cabling (e.g. Ethernet), shared computer;
j) commissioning, e.g. availability and interaction of subsystems;
k) interoperability diagnostics, e.g. event recording, device and object binding integrity, protocol analysing.
5.2.2.3.3 Integration/implementation
As regards the implementation of the integration, the following should be considered:
a) responsibilities, e.g. supplier of subsystems for its functionality and interfaces, party for the delivery of
integration of subsystems;
b) compatibility, e.g. change control, software/hardware versions, protocol versions, proprietary protocol
details;
c) commissioning, e.g. sequence of commissioning from subsystems to primary system.
ISO 16484-1:2024(en)
5.2.2.3.4 Integration/operation
As regards the effective operation of an integrated system, the following should be considered:
a) the number and types of data points, e.g. values, alarms, point/object names and mnemonics;
b) the depth of information required, e.g. limits, scheduling, trends;
c) the human system interfaces (HSI), e.g. single computer multi applications, single application, web
browser, access rights;
d) the user actions required, e.g. monitoring, commanding, acknowledgement, local overrides.
Integration can be achieved by multiple applications on a single computer (e.g. a web browser) or a single
application that handles all information (e.g. full graphical representation of information). The information
can be used either for the purpose of monitoring or commanding, or both.
5.2.2.3.5 Integration/function
The following points for the interoperability of integration should be considered:
a) function types to perform in which systems, e.g. time scheduling, maximum demand and other BACS
functions from ISO 16484-3;
b) interactions, dependencies and priorities, e.g. smoke exhaust fans, plant activation from access system;
c) system behaviour in case of abnormality, e.g. default values, partial system/device restart, maintenance
shutdown;
d) number and types of shared data points, e.g. outdoor air temperature, scheduling, trending.
5.2.2.3.6 Integration/infrastructure
Infrastructure includes common physical items that facilitate communication and media sharing.
Consideration should be given to the following regarding the infrastructure of integration:
a) installation, e.g. wireless access points, cabling systems, power over Ethernet, grounding, communication
protocols, topology;
b) network management, e.g. addresses, VPN, firewalls, remote access, access rights, segmentation;
c) network capacity, e.g. bandwidth, normal and abnormal usage;
d) availability and reliability, e.g. redundancy, setup and commissioning of integrated, decentralized and
autonomous systems.
5.2.2.4 Physical attributes
Building infrastructure and plant equipment influence physical attributes of BACS and should be considered
along with the following:
a) new equipment and its ability to be monitored and controlled, e.g. adding monitoring and control;
b) existing equipment and its ability to be monitored and controlled, e.g. reuse, adding functionality;
c) existing controls or BACS, e.g. integrate, migrate, replace;
d) space, e.g. for cabinets, wall mountings, HSI;
e) HSI, e.g. local display, operator workstation;
f) local conditions, e.g. environmental, temperature, humidity, seismic risk, extreme weather;
ISO 16484-1:2024(en)
g) cabling, e.g. topology, media type, size, rating, environment;
h) power supply, e.g. frequency, voltage, emergency power supply, UPS.
5.2.2.5 Occupational needs
The client's requirements will influence the scope and attributes of BACS and should be considered along
with the following:
a) priorities for operation of the building, e.g. emergency situations, normal conditions, overrides;
b) occupancy profile, e.g. schedules/calendar, setpoints, operating modes, daylight saving, energy use;
c) energy performance, e.g. energy usage, energy savings;
d) comfort conditions, e.g. thermal, visual, acoustic, air quality;
e) HSIs, e.g. local override/indication devices, operator and monitoring units or panels, operator work
stations including visual display units, internet browser on different types of platforms.
5.2.2.6 System requirements
The client's requirements will influence the design of BACS and should be considered along with the
following:
a) priorities for operation, e.g. safety of personnel, protection of equipment, occupancy profile, comfort,
energy savings, cost savings, reliability, indoor air quality;
b) control strategies (see ISO 16484-3);
c) management functions (see ISO 16484-3), e.g. data storage, data retrieval;
d) maintenance management aspects, e.g. condition-based monitoring, local/remote reporting;
e) energy management needs;
f) alarm strategy, e.g. categories, priorities, delivery, routing;
g) HSI, e.g. localization, multi-language, graphics quality, types, functionality;
h) system support, e.g. remote access, technical support;
i) system performance, e.g. accuracy, response time, display response;
j) system reliability, e.g. availability, redundancy;
k) documentation, e.g. format and media, content, quantity, compliance certificates.
5.2.2.7 Site and client specific requirements
The needs at the site and the client specific requirements influence the documentation and delivery of the
BACS and should be considered along with the following:
a) installation, e.g. electrical, mechanical, controls;
b) commissioning and handover, e.g. witness testing, process for uncompleted actions, summer/winter
operation, phased delivery, documentation of the results;
c) training, e.g. instructions for use, operation and maintenance, system/product training;
d) documentation, e.g. language, content, media, certificates, software licences and backup;
e) post completion, e.g. warranty/guarantee, spare parts, maintenance and software updates;
ISO 16484-1:2024(en)
f) application of the commissioning process, e.g. required qualification and role of commissioning
authority.
5.2.3 Project planning and organization
5.2.3.1 Overview
A clear management and reporting structure shall be described for all parties involved. The process shall
allow for resolution of issues raised during the project and include
a) project planning,
b) project organization,
c) definition of responsibilities,
d) details of specific constraints, and
e) change management.
5.2.3.2 Project planning
The project plan defines the milestones, tasks and deliverables that will drive the project. It details
dependencies on other trades that affect the BACS timetable and identifies who is responsible for doing what,
as well as the deadlines. A timetable detailing the BACS design, engineering, installation/commissioning and
completion phases shall be provided.
5.2.3.3 Organization
Details of the roles and relationships within the organization required to deliver t
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...