SAES-K-011
-
Upload
irfanshaikh2010 -
Category
Documents
-
view
348 -
download
53
description
Transcript of SAES-K-011
Previous Issue: New Next Planned Update: 27 March 2017
Page 1 of 34
Primary contact: Hamid, Adel Sulaiman on 966-3-8760212
Copyright©Saudi Aramco 2011. All rights reserved.
Engineering Standard
SAES-K-011 27 March 2012
Building Management System
Document Responsibility: HVAC Standards Committee
Saudi Aramco DeskTop Standards
Table of Contents 1 Scope............................................................ 2
2 Conflicts and Deviations................................ 2
3 References.................................................... 2
4 Definitions...................................................... 4
5 System Selection........................................... 7
6 Standard Products......................................... 8
7 Redundancy.................................................. 9
8 Spare and Expansion Capabilities............... 10
9 System Access and Security....................... 10
10 Communication and Network...................... 12
11 Direct Digital Control (DDC)......................... 13
12 Consoles and Workstations......................... 20
13 Operator Graphical Displays........................ 20
14 Alarms and Messages................................. 24
15 History.......................................................... 29
16 Integration and Interface.............................. 30
17 Units of Measurement................................. 30
18 Wiring and Power Supply............................ 30
19 Environmental Conditions............................ 32
20 Documentation............................................. 34
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 2 of 34
1 Scope
This Standard prescribes the minimum mandatory requirements and guidelines
governing the engineering, design, and installation and material specification of
Building Management System (BMS) in Saudi Aramco buildings.
Building Management System (BMS) and the interface with their subsystems are
considered within the scope of this standard. The regulatory, sequential, advanced
controls and optimization implemented in these systems are also included.
The integrated system shall be referred to as the Building Management System (BMS).
The BMS is a system installed in buildings to provide reliable interface, control and
energy management of the building’s mechanical and electrical equipment such as but
not limited to the following:
1) HVAC Equipment
2) Fire Alarm and Fire Suppression
3) Security Access Control, CCTV
4) Building Elevators
5) Power Management Systems
6) Environment Monitoring and Control
This entire standard may be attached to and made a part of purchase orders.
2 Conflicts and Deviations
2.1 Any conflicts between this standard and other applicable Saudi Aramco
Engineering Standards (SAESs), related Materials System Specifications
(SAMSSs), Standard Drawings (SASDs), or industry standards, codes, and
forms shall be resolved in writing by the Company or Buyer Representative
through the Manager, Consulting Services Department, Saudi Aramco, Dhahran
2.2 Direct all requests to deviate from this standard in writing to the Company or
Buyer Representative, who shall follow internal company procedure SAEP-302
and forward such requests to the Manager, Consulting Services Department of
Saudi Aramco, Dhahran.
3 References
All materials, engineering and installation shall comply with the applicable
requirements and standards addressed within the following references:
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 3 of 34
3.1 Saudi Aramco References
Saudi Aramco Engineering Procedures
SAEP-103 Metric Units of Weights and Measure
SAEP-302 Instructions for Obtaining a Waiver of a
Mandatory Saudi Aramco Engineering
Requirement
SAEP-1626 Configuration and Graphics Guidelines
Saudi Aramco Engineering Standards
SAES-J-003 Instrumentation – Basic Design Criteria
SAES-J-004 Instrumentation Symbols and Identification
SAES-J-902 Electrical Systems for Instrumentation
SAES-K-001 Heating, Ventilation and Air Conditioning
SAES-K-002 Air Conditioning System for Essential Operating
Facilities
SAES-K-003 Air Conditioning System for Communications
Buildings
SAES-K-101 Regulated Vendor List (RVL) for HVAC
Equipment
Saudi Aramco Materials System Specifications
34-SAMSS-711 Control Valves
34-SAMSS-820 Instrument Control Cabinets – Indoors
34-SAMSS-831 Instrumentation for Packaged Units
Saudi Aramco Information Protection Manual (IPM)
IPSAG-007 Computer Accounts Security Standards and
Guidelines
ASHRAE, American Society of Heating, Refrigeration and Air Conditioning
Engineers (ASHRAE)
ASHRAE Guideline 13-2007 Specifying Direct Digital Control Systems
ANSI/ASHRAE 135 BACnet - A Data Communication Protocol for
Building Automation and Control Networks
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 4 of 34
The International Electrotechnical Commission
IEC 60050-351 International Electrotechnical Vocabulary — Part
351: Control Technology
IEC 61131-3 Programmable Controllers — Part 3:
Programming languages
The International Organization for Standardization (ISO)
ISO-16484 Building Automation and Control Systems
ISO-14908 Open Data Communication in Building
Automation
NEMA Compliance
NEMA 250 Enclosure for Electrical Equipment
NEMA ICS 1 General Standards for Industrial Controls
NFPA Compliance
NFPA 90A Standard for the Installation of Air Conditioning
and Ventilating Systems
NFPA 92A Smoke-Control Systems
NFPA 70 National Electrical Code (NEC)
Institute of Electrical and Electronics Engineers (IEEE)
IEEE 802.3 CSMA/CD (Ethernet – Based) LAN
IEEE 802.4 Token Bus Working Group (ARCNET – Based)
LAN
Underwriters Laboratories
UL 916 Energy Management Equipment
4 Definitions
4.1 Abbreviations
ACU Air Conditioning Unit
AHU Air Handling Unit
AI Analog Input
AO Analog Output
BI Binary Input
BMS Building Management System
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 5 of 34
BO Binary Output
FIFO First-In, First Out
HMI Human Machine Interface
NC Normally Closed
NO Normally Opened
TCP/IP Transmission Control Protocol
UPS Uninterruptible Power Supply
4.2 Definitions
Architecture: Structure and means by which components and devices of a
system are connected to intercommunicate.
Algorithm: A prescribed set of well-defined rules or processes for the solution
of a problem in a finite number of steps. (See also control algorithm).
Application: Application packages shall be vendor's standard off-the-shelf
offering configurable to meet job-specific requirements. Modification of source
codes unique for Saudi Aramco is not allowed.
Availability: The percent of time a system or component remains on line and
performs as specified.
Building Management System (BMS): BMS is a description for products,
software, and engineering services for remote and centralized automatic
controls, monitoring and optimization, human intervention, and management to
achieve energy – efficient, economical, and safe operation of building services
equipment.
Cascade (Cascade Control): A control scheme composed of two loops where
the setpoint of one loop (the inner loop) is the output of the controller of the
other loop (the outer loop).
Closed Loop Control: A system where the output acts upon the process in such
a way as to reduce the difference between the measured value and the desired
set-point value to zero.
Compatibility: The capability of devices of different types and from different
manufacturers to operate in a specific network under the same conditions and
rules.
Critical: A function which if lost would result in either a major process upset
or loss of operation.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 6 of 34
Critical Regulatory Control: Refers to control of equipment which does not
have an installed spare or backup or where failure of the equipment would result
in a significant an unsafe operating condition. Inputs and Outputs used for
regulatory control in critical applications shall be supplied with redundant I/O
modules. Requirements for redundant inputs and outputs will be specified in the
project FSD.
Control Algorithm: A mathematical representation of the control action to be
performed.
Console: A collection of one or more workstations and associated equipment
such as printers and communications devices used by an individual to interact
with the BMS and perform control and monitoring functions.
Data communication protocol: A protocol is a set of rules that control the
exchange of data over a network.
Direct Digital Control: control of equipment or plant by means of a digital
computer or microprocessor.
Fault-Tolerant: The property of a system which enables it to carry out its
intended function with one or more active hardware or software faults.
Field Device: A physical connection from the input/output interface of a
controller to an item of plant, thereby providing the necessary information or
action for the conditions, states, and values of the process.
Function: Functions within a BMS are referred to as control functions, I/O,
processing, optimization, management, and operator functions.
Gateway: a device that connects two or more dissimilar networks, permitting
information exchange between them.
Interoperability: The capability of devices of different types and from
different manufacturers to exchange information and commands via the
communications network.
Local Area Network (LAN): Network that links a number of nodes within the
same locality.
Firmware: Firmware is a combination of both hardware and software.
Hardware such as ROMs (Read Only Memory) or EPROMs that have software
programs or data recorded on them is considered firmware.
Functional Specification Document (FSD): Written requirements of the
functionality required for a piece of equipment or a system.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 7 of 34
Hardware: Building Management System Hardware consists of field devices,
control devices, cabling, communication and computing devices.
Redundant: A system and/or subsystem that provides for a standby module
with automatic switchover from the active unit to the standby module, in the
event of a failure, without loss of a system function. Both active and standby
modules utilize diagnostics to assist in identifying and locating failures and to
permit modules to be removed for repair and/or replacement.
Software: Software shall be considered programming code, computer
instructions or data that can be stored electronically. The storage devices and
display devices are hardware. Software is often divided into two categories:
Systems Software: Includes the operating system and all the utilities that
enable the computer to function.
Applications Software: Includes programs that do real work for users.
For example, word processors, spreadsheets, and database management
systems fall under the category of applications software.
Transmission Control Protocol (TCP): One of the main protocols in TCP/IP
networks. Whereas the IP protocol deals only with packets, TCP enables two
hosts to establish a connection and exchange streams of data. TCP guarantees
delivery of data and also guarantees that packets will be delivered in the same
order in which they were sent.
VLAN: Virtual Local Area Network, a group of hosts with a common set of
requirements that communicate as if they were attached to the same broadcast
domain, regardless of their physical location.
Workstation: A computer and its associated monitor(s), keyboards(s) and other
peripheral devices which is connected to the BMS and is used to provide Human
Machine Interface functions and/or other maintenance and engineering
functions.
5 System Selection
5.1 Depending on the particular function objectives to be accomplished within any
given project, decisions need to be made regarding selection of the Building
Management System (BMS) system(s) to be utilized.
5.2 This selection is specified by the Company's purchase orders, contracts or job
specifications, including a project-specific FSD.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 8 of 34
5.3 Building Management System (BMS) shall utilize electronic sensing,
microprocessor-based digital control, and electronic actuation to perform control
and functions specified.
5.4 Building Management System (BMS) shall allow user to set up schedules of
operation for equipment or to compare space temperature, outside air conditions,
and equipment capabilities to ensure set points are achieved.
5.5 Building Management System (BMS) shall have the ability to monitor energy
usage.
5.6 Building Management System (BMS) shall offer load shedding when power are
at peak demand to cut back on power usage to prevent blackout.
5.7 Building Management System (BMS) should offer the ability to send alarms or
alerts via email, or telephone to alert building managers of developing problems
and system failures
5.8 Building Management System (BMS) shall be fully expandable with addition of
hardware and/or software. Expansion shall not require removal of existing,
sensors, actuators, or communication networks.
6 Standard Products
6.1 Building Management System (BMS) shall be composed of manufacturers'
standard hardware, software, firmware and application packages.
6.2 A system's standard operating system software shall not be modified to meet any
of Saudi Aramco's requirements.
6.3 All hardware, firmware, software and application that are supplied shall have
been field proven prior to the hardware freeze date as defined in the contract or
purchase order. Field proven is defined as successful installed history of
demonstrated satisfactory operation for a length of six (6) months since the date
of final completion of comparative size and complexity (excluding beta test
period). It shall be possible for Saudi Aramco to verify the field proven status of
the system.
6.4 BMS vendor shall guarantee support of all hardware, firmware and software
associated with BMS and any proprietary equipment for a period of fifteen (15)
years from the hardware freeze date as defined in the contract or purchase order.
Support shall include spare parts, technical support and training. This support
shall not be contingent on the customer upgrading to later releases of software or
hardware.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 9 of 34
6.5 BMS vendor shall provide support for all Commercial Off-The-Shelf (COTS)
products supplied as part of the BMS for a period of five (5) years.
Commentary Note:
It is not the intent of Saudi Aramco to require BMS vendors to service commercially available products which they did not manufacture. The vendor shall, however, guarantee the COTS equipment supplied with the system can be replaced with a similar component for the period specified without loss of functionality to the system and without requiring software upgrades to later releases of the BMS operating system software.
6.6 Withdrawal of product support for BMS vendor manufactured products shall be
notified in writing to Saudi Aramco twelve months in advance.
6.6 Application packages shall be vendor's standard off-the-shelf offering
configurable to meet job-specific requirements. Modification of source codes
unique for Saudi Aramco is not allowed.
6.7 Third-party products incorporated as part of the vendor's systems must have
been approved and certified by the specific vendor. Any substitute must be
approved by Saudi Aramco in writing.
7 Redundancy
7.1 If redundancy is required, based on what is specified on the project FSD, then it
should include but not limited to the following equipment:
a) All Processing Units.
b) Main memory
c) All Power supply modules.
d) All BMS Network Communications Equipment.
e) All communications equipment required for communications between
controllers and I/O units.
h) All Input and Output units used for critical regulatory control.
i) All BMS servers
j) All data storage devices (e.g., hard-drives) used to store system
configuration information or control strategy configuration information.
k) All auxiliary systems communications interface modules, including
communications paths, where either the communications channel is used
to send commands from the BMS to the auxiliary system or data from the
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 10 of 34
auxiliary system is used within a regulatory control strategy within the
BMS.
7.2 A minimum of two electrically and electronically independent operator
workstations shall be provided for each operator's console.
8 Spare and Expansion Capabilities
8.1 Each system shall be supplied with 10% spare per I/O type. The spare I/O shall
be licensed, installed, and wired to termination points.
8.2 Where both redundant and simplex I/O models are used for a signal type, the
requirement for spare I/O shall apply for both types.
8.3 Terminal Blocks spare shall be 20%.
Commentary Note:
Requirements for expansion capacity and spare I/O do not apply to expansion projects where control and I/O are being added to an existing system. For expansion projects, the requirements for spare I/O and expansion capability shall be mutually agreed upon between PMT and Proponent and specified in the project specific FSD. If none are specified in the FSD, the requirements above shall apply.
8.4 Servers and/or Engineering Workstations shall be configured with additional
spare capacity of 40% minimum for hard-drive space, memory, and CPU. CPU
and memory spare requirements shall be verified on the running system during
steady-state conditions with all applicable software running on the system.
9 System Access and Security
9.1 Access Control
9.1.1 Access to Building Management System (BMS) shall be restricted only
to person(s) with legitimate business requirements.
9.1.2 Procedures for control of user registration; de-registration and the
allocation of access rights and privileges for access to building
management systems shall be documented and enforced.
9.1.3 User access to a system shall be restricted by means of User Ids and
Passwords or other suitable technologies for identification and
authentication of users.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 11 of 34
9.2 User Levels
The following user levels shall be configured as a minimum. Additional user
levels may be created based on what is specified in the project FSD:
9.2.1 Operator Level
This user level shall be configured to provide access privileges defined
to enable monitoring and control of equipment located within specific
area(s) to which the level is associated.
9.2.2 Maintenance Level
This user level shall provide access to system diagnostic and
troubleshooting tools. Access to utilities required for backup and restore
of system information and other privileges required to enable
maintenance functions (such as replacement of failed components) shall
also be granted as required.
9.2.3 Engineer Level
This user level is used to grant access privileges for engineers for
monitoring and control of equipment associated with the particular area
to which the role is associated. Access privileges to modify function
parameters (such as alarm limits and tuning constants) shall also be
granted.
9.2.4 Administrator Level
This user level shall provide access to the entire system. Assignment of
users to this role shall be restricted to a limited number of highly trusted
and competent employees. This level shall also contain privileges
necessary for configuration of user role privileges and assignment of
user(s). The level shall contain privileges necessary to administer
individual user IDs and passwords as well as provide access to utilities
required for monitoring and auditing of system access activities.
9.2.5 View Only
This user level shall be used to provide monitoring only access of all
process areas. Access to control operations or access to system
diagnostics, maintenance and configuration utilities shall be restricted.
9.3 Anti-Virus Protection
9.3.1 Anti-virus software shall be installed and configured on all Windows
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 12 of 34
based workstations and servers which are part of the BMS.
9.3.2 Anti-virus software shall be as per Saudi Aramco requirements and
guidelines.
9.3.3 The vendor's recommended procedures shall be followed for
configuration of anti-virus software.
9.3.4 Anti-virus definition files shall be updated on all stations connected to
the BMS every three months or as per the vendor's recommended
update procedures, whichever is more frequent.
9.4 Operating System Software Patch Management
9.4.1 The vendor's recommended procedures for updating of Operating
System (OS) software and OS patch installation shall be followed.
9.4.2 Access privileges for updating of Operating System software shall be
assigned to BMS Administrator only.
9.4.3 Operating System software and OS patches shall not be installed unless
they have been tested and certified by the vendor as being compatible
with the BMS System software.
10 Communication and Network
10.1 Building Management System (BMS) shall be based on an open compatible
protocol such as BACnet, LonWorks, Modbus. No BMS subnet or controller is
to operate that is not open protocol compliant.
10.2 Building Management System (BMS) is to be interconnected to all other BMS
systems via the open protocol over IP and across network.
10.3 The communication speed between the controllers, LAN interface devices, and
operator interface devices shall be sufficient to ensure fast system response time
under any loading condition.
10.4 BMS communication network shall be designed such that no single failure will
degrade the performance of the system.
10.5 Interruptions or fault at any point shall not interrupt communications between
other BMS nodes on the network.
10.6 The BMS Network shall utilize an open architecture capable of all of the
following:
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 13 of 34
10.6.1 Utilizing standard Ethernet communications and operating at a
minimum speed of 10/100 Mb/sec.
10.6.2 The BMS network shall support both copper and optical fiber
communication media.
10.7 A gateway shall communicate with third-party equipment furnished or installed
by others.
10.8 The time between the command override by the operator and the reaction by the
device shall be less than 1 second and the subsequent update at the Operator’s
Station shall be no more than 5 seconds.
10.9 The time from which an object goes into alarm to when it is annunciated at the
display shall not exceed 5 seconds.
11 Direct Digital Control (DDC)
11.1 General Requirement
11.1.1 The scope of work covering the DDC shall include system engineering,
application programming, configuration, integration, testing,
documentation and commissioning.
11.1.2 The DDC shall be used to gather discrete and analog measurements
and provide control monitoring and event logs from the operations in
the specified buildings.
11.1.3 The DDC shall be provided with appropriate terminals for connection
to filed devices. The arrangement shall segregate different signal types
of separate terminal block for DI, DO, AI and AO, communication
circuit and 24 VDC distribution for field devices. Terminal Type,
identification and segregation shall be required by SAES-J-902 and
34-SAMSS-820.
11.1.4 All input and output points shall be individually fused or incorporate
internal short circuit protection. If fuses are used, there shall be a blow
fuse indication.
11.1.5 The DDC shall support remote I/O modules with the specified
minimum distance from the processor and shall have a real-time clock
that enables time scheduling of start and stop commands and set point
changes to the equipment that is being monitored and controlled.
11.1.6 Logic diagram with set points shall be provided for all instruments that
requires an output to other devices such as high temperature alarm,
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 14 of 34
common fault alarm within DDC and other high alarms to remote
signal to manned control room.
11.1.7 The real-time clock shall be provided with a battery backup with an
average life of more than 3 years.
11.1.8 The average CPU Loading of any controller during normal operating
conditions shall not exceed 65% overall or 75% of the manufacturers
recommended maximum loading specification, whichever is lower.
The spare capacity is required to accommodate peak loads during upset
conditions and to provide additional capacity required for
configuration of spare I/O points and associated control algorithms and
to enable the utilization of the spare I/O slots.
11.2 Hardware Requirement
11.2.1 The DDC shall be of the latest model, intelligent type microprocessor
based.
11.2.2 The DDC shall be mounted in an enclosure as per 34-SAMSS-820,
standard.
11.2.3 The DDC shall support a local programming interface via laptop
computer.
11.2.4 Any type of I/O module shall be insertable into any I/O slot reserved
for this purpose.
11.2.5 I/O modules shall be segregated by signal type and voltage level.
11.2.7 All DDC modules shall have internal high voltage surge and fast
transient protection as specified in ANSI/IEEE standard C.37.90.1 or
equivalent IEC specification.
11.2.8 All DDC input/output modules shall be capable of being inserted into
or removed from their mounting assemblies without disturbing the rest
of the system.
11.2.9 All input/output modules shall provide a status LED which indicates
the health or operational condition of the module. The status of the
module shall also be communicated to the system diagnostics software.
11.2.10 The DDC shall provide system diagnostic alarms that provide remote
indication of DDC critical and non-critical conditions such as hardware
faults or CPU loading exceeded.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 15 of 34
11.3 Regulatory Control Implementation
11.3.1 The DDC execution cycle time shall be less than or equal to 1 sec
unless otherwise specified in the project FSD.
11.3.2 Consideration must be taken during design that the I/O scan rate is at
least as fast as the required control algorithm execution rate.
11.1.3 Control loops shall be configured for bump-less transfer between
manual, automatic, cascade and "computer" modes. Bumpless transfer
shall be defined as less than 0.5% deviation when the transfer occurs.
11.3.4 Tracking - Control loops shall be configured to set the output of the
controller equal to the downstream value during the initialization
process. If the downstream value is an output to the field, the initial
output of the controller will equal the position of the field device.
For cascade controllers, the output of the primary controller shall equal
the setpoint of the secondary controller.
11.3.5 Output modules with failsafe functionality shall be configured to safely
shutdown affected process equipment.
11.3.6 Composite tag - Where possible, multiple inputs and outputs for a
single device, such as a pump, shall be combined into a single tag ID.
Operation of the device shall be through this single tag ID.
11.4 Input Functions
11.4.1 The following input functions shall be supplied as standard
configurable items:
a) Square root extraction
b) Linearization of type E, J and K thermocouples
c) Linearization of RTDs/NTC
d) Time-based filtering
e) Digital input totalization
f) Pulse input to frequency conversion
g) Dead band on a per loop basis
11.4.2 Input filtering and signal conditioning shall be performed before
alarms are checked and control calculations are made.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 16 of 34
11.5 Computational Functions
The following computational functions shall be supplied as standard,
configurable items or simple algebraic instructions.
a) Addition/subtraction
b) Lead-lag
c) High/low select
d) Median select
e) Multiply and divide
f) Time average
g) Signal selection switch
h) Exponential polynomial
i) Fifth order polynomial
j) Logarithms
k) Square root
l) Absolute value
11.6 Continuous Control Functions
The following control functions shall be supplied as standard configurable items:
a) Proportional Integral Derivative (PID)
b) Proportional Integral
c) Proportional Derivative
d) Proportional only
e) Integral Only
f) Auto/manual with bias control
g) Ratio control
h) Control (Signal) Selector
i) Output Splitter
j) PID with feed-forward
k) PID with non-linear gain
l) External Feedback
m) Gap action
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 17 of 34
n) Adaptive tuning
11.7 Output Functions
The following output functions shall be supplied as standard configurable items:
a) Linear
b) Linear with clamping (high and low restricted)
c) Non-linear characterization
d) Rate of change limits
e) Output limiting based on application program
f) Output limiting based on discrete input status
11.8 Discrete Control
The following discrete control functions shall be supplied as standard
configurable items:
a) Logic functions -- AND, OR, NOT, NOTAND, NOR, XOR
b) Change of state detect
c) Set/reset flip-flops
d) Timers and counters
e) Comparisons -- greater than, less than, equal to, not equal to
f) Pulse elements -- fixed, maximum, minimum
g) Check for invalid value
h) Flags
11.9 Control Loop Execution Frequency
It shall be possible to select the execution frequency of each control loop.
The following minimum selection shall be available:
a) One second
b) One half (½) of a second
c) One quarter (¼) of a second or less
11.10 Control Modes
11.10.1 It shall be possible to put any individual control loop in a manual
mode; and for an operator to manipulate the output of a control loop
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 18 of 34
while in the manual mode.
11.10.2 In manual mode, an output signal from a field output module must
change within one second from the last operator action that is required
to command the change.
11.10.3 For cascade control, it shall be possible to configure remote setpoints
from other regulatory controllers.
11.10.4 All control blocks that can accept a setpoint shall be capable of being
switched between local setpoint (operator entered) and remote setpoint.
11.10.5 Information shall be transferred between cascaded loops that are in
separate controller modules within 2 seconds.
11.10.6 Information shall be transferred between cascaded loops that are in the
same controller module at whatever the configured block processing
period is for the loop.
11.10.7 Control blocks shall be able to perform automatic mode switching
based on external or internal logic inputs. Mode switching shall
include the following:
a) Auto/manual/Cascade switching
b) Local/remote setpoint switching
11.11 Sequential Control
11.11.1 The system shall provide a graphical configuration tool which
conforms to the IEC 61131-3 guidelines for Structured Text or
Sequential Function Chart.
11.11.2 It shall be possible to modify individual program logic for sequential
functions without interrupting the operation of other sequential
functions that are active.
11.11.3 The system shall have the ability to monitor and control program flow
through sequential functions in real-time.
11.11.4 The following sequential functions shall be supplied as standard
instructions:
a) Relational expressions:
- Equal to
- Not equal to
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 19 of 34
- Less than
- Less than or equal
- Greater than
- Greater than or equal
- IF / IF Then.
b) Calculations:
- Add
- Subtract
- Multiply
- Divide
- Exponentiation (whole and fractional)
- Square root
c) Timers:
- Output true after preset delay
- Output false after preset delay
d) Counters:
- Count up
- Count down
e) Logical expressions:
- And
- Or
- Not
- Exclusive Or
- Single bit memory elements (flip/flops)
f) Hold sequence - Manual or preset time
g) Recycle to prior step
h) Skip 1 or more steps
i) Restart at the beginning
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 20 of 34
12 Consoles and Workstations
12.1 General
12.1.1 Consoles, including panel and screen mounting structures shall be
equipped with tabletop work surfaces.
12.1.2 Where required, telecommunication equipment (e.g., telephones,) shall
be incorporated in separate bay within the same console furniture.
12.2 Operator Consoles
12.2.1 Each station in the operator console shall have access to a networked
printer(s) for alarm logging, reporting and graphical printing.
12.2.2 Consoles that are manned on a continuous basis shall have access to a
networked graphics printer for making hard copies of active displays.
12.2.3 Each Operator Console shall be equipped with a minimum of two
workstations.
12.3 Engineering Workstation
12.3.1 Each engineering workstation shall have access to a networked printer.
12.3.2 Each engineering workstation shall be capable of performing all
operator workstation's functions.
13 Operator Graphical Displays
This section defines graphical displays primarily used by operators to monitor, control
and obtain information via the operator workstation.
13.1 General Operator Graphics Requirements
13.1.1 All graphics shall include the following information in standard
locations:
a) Title
b) Date and time
c) Display name
13.1.2 Colors
The following guidelines on color usage shall be applied unless it
violates the standard conventions designed into the system.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 21 of 34
a) Bright colors shall be used to convey key information such as
process and control information.
b) Data representation of a specific type (alphanumeric, symbolic,
etc.) shall be displayed with the same color sets for specific
conditions on all graphic displays.
13.1.3 Process Lines
a) Process lines shall either be drawn horizontally or vertically.
b) Process line crossovers shall be minimized. Line breaks shall be
used to indicate that crossing lines do not join. Main process
lines for each graphic shall be bold with secondary lines being of
finer width.
13.2 Design Philosophy
13.2.1 Operator displays shall use only standard features provided by the
selected product.
13.2.2 When designing operator displays, a consistent approach shall be used
for the appearance (look-and-feel) and functionality. Avoid using
highly animated objects that may inadvertently divert the operator from
important process information.
13.2.3 The design approach shall include standardized approach for:
Layout - line sizes, equipment representation, orientation, fonts,
titles, etc.
Data representation - process values and alarms
Color choices - process lines, control lines, process equipment,
titles, etc.
Display access and navigation
How status pairs are defined (on/off, open/closed, start/stop, etc.)
Control modes (manual/auto/computer, etc.), either by color or by a
small text next to the controller
Data validity (invalid, out-of-range, unknown status), either by
color or by a small text next to the controller
13.2.4 Wherever possible and practical, library elements, e.g., controller
faceplate template, shall be used when assigning elements to a graphic.
For example, if the background color of a process value indication in a
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 22 of 34
controller element is specified to be flashing red for unacknowledged
alarm condition, solid red for acknowledged alarm condition, and
flashing background color for unacknowledged return-to-normal
alarms, this behavior should be specified in a display convention file
and the element linked to the display convention.
13.3 Display Navigation
13.3.1 Operators shall be able to easily access specific displays and graphics
by pressing dedicated function keys or selecting from a list of displays
in directories and menus, or by typing display or graphic names.
13.3.2 Display navigation shall be configured such that it is possible to move
between related displays and graphics of different detail levels or of the
same detail level with a maximum of two operator actions.
13.3.3 Any graphic display shall be accessible via no more than three operator
actions.
13.3.4 All process graphics shall include a “Previous Display” button or
capabilities which will call-up the previous process graphic when
selected.
13.3.5 When using a windows environment consideration must be given to
prevent the Operator from opening too many windows and potentially
masking important process information.
13.4 Control functions
The operator shall be able to perform all the basic monitoring and control
functions from graphic display or control faceplates. These functions shall
include, but not be limited to, changing process variables, setpoints, switching
control modes, manually driving outputs, or initiating maintenance bypasses for
input points.
13.5 Control Strategies
13.5.1 Control strategy information shall be displayed in such a way that the
operator can determine what is being controlled, which control
strategies are in service, which are out of service, and which are
constrained or limited in some way.
13.5.2 Control strategy information shown on process displays shall be
dynamic, reflecting the actual current state of the strategy.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 23 of 34
13.5.3 The operator shall be able to manipulate the state of the control
strategy from the control graphics.
13.5.4 Controller modes shall be indicated on primary operating display.
13.6 Control Faceplate Displays
13.6.1 Control faceplates shall show dynamic process and status information
about a function block or tag and shall permit an operator to change
required parameter values associated with the function block.
13.6.2 Faceplates shall display the following information as applicable:
Tag ID
Tag Descriptor
Process input, setpoint, and output values displayed numerically
with engineering units.
Process input, setpoint, and output in bar or graphical
representation.
Control Mode (auto/manual) and setpoint status (remote/local).
Visual indication of setpoint and output high and low limits.
Symbolic and alphanumeric indication of discrete states both for
two state devices and multi-state devices.
Visual indication for alarm status, acknowledgeable on a point-by-
point basis.
13.6.3 The following actions shall be possible from each Faceplate as
applicable:
Change control block mode.
Change setpoint and other operator settable parameters.
Issue commands to multi-state devices.
Adjust outputs in manual mode.
13.6.4 Faceplates shall be constructed from templates. The layout and
operational characteristics of the individual faceplates shall be
inherited from the template such that each faceplate constructed from
the template will have the same look and operational characteristics as
the template.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 24 of 34
14 Alarms and Messages
14.1 General
14.1.1 Configuration of Alarms and Messages shall have consistency
guidelines and avoid configuration of unnecessary alarms. Priority
shall be established by severity of consequence and time to respond for
each process variable.
14.1.2 Alarm and messages shall be configured to perform the following:
a) To draw the operator's attention to abnormal conditions within
his area of responsibility, both in the process (process alarms)
under his control and in the BMS equipment (system alarms).
b) To provide information and description to facilitate the operator's
rapid understanding of the abnormal condition.
c) To provide rapid access to the tools needed by the operator to
perform corrective action.
d) To provide a comprehensive historical record, accessible to the
operator and other plant personnel, of the information needed to
assess such abnormal conditions.
e) To prompt the operator for feedback when approval for
automated action or selection from among options is required.
14.1.3 Alarms and messages shall be categorized as follows:
a) Process alarms & messages
b) System alarms & messages
c) Operator actions messages
d) Engineer actions messages
14.2 Process and System Alarms
Any alarm used shall be informative and demand an operator action. Automatic
alarm suppression shall be used to minimize nuisance alarms based on logic
actions and/or events.
14.2.1 General
14.2.1.1 Process and System alarms shall include both audible and
visual annunciation.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 25 of 34
14.2.1.2 BMS modules shall provide identical alarm options.
14.2.2 Alarm Categories and Level Designations
14.2.2.1 Two alarm categories are required as a minimum:
a) PROCESS: abnormal condition that requires immediate
operator action.
b) SAFETY: reserved for safety related alarms such as fire
alarms.
14.2.2.2 Four alarm levels shall be used as a minimum:
HH - high high
H - high
L - low
LL - low low
These levels may be used in association with any category.
However, HH and LL in general indicate an automatic
shutdown response or imminent shutdown condition.
The “pre-alarms” shall be designated H (High) or L (low).
14.2.2.3 All automatic trip setpoints or limits shall be pre-alarmed in
the BMS, including auxiliary systems and regulatory
controls.
14.2.3 Visible Alarm Indication
14.2.3.1 Blinking Feature shall be reserved for unacknowledged
alarm situations only. Blinking shall cease when the alarm is
acknowledged.
14.2.3.2 Alarms - Alarms shall be invisible on the operator graphics,
appearing only while an alarm is active.
14.2.3.3 All alarms shall be displayed with a small red square or
rectangular with its background flashing. The color-coded
background shall remain while the alarm is active.
14.2.3.4 Alarms shall be visually displayed and annunciated (blinking
when unacknowledged) only on the workstation configured
for those alarms.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 26 of 34
14.2.3.5 A “Process Alarm Summary” display showing all active
process alarms assigned to the workstation shall be provided.
Accessing this alarm summary display from any other
display shall require no more than one operator action.
Alarms shall be grouped on this display to allow the operator
to readily identify and respond to alarms and abnormal
conditions in his area of responsibility (e.g., Sorted by
priority, time).
14.2.3.6 A “System Alarm Summary” display showing all active
system alarms shall be provided. Accessing this alarm
summary display from any other display shall require no
more than one operator action.
14.2.3.7 Each alarm indication shall be shown on one of the two
alarm summary displays and on another display which
conveys the significance of that alarm in relation to the
process or to the BMS system.
14.2.3.8 There shall be an indication of the overall process alarm
status of the operator area assigned to each workstation
regardless of which display is in use.
14.2.4 Audible Alarm Indication
14.2.4.1 Distinct audible tones shall be used to distinguish between
the two required alarm categories, i.e., Abnormal Condition,
and SAFETY.
14.2.4.2 A different audible tone shall be used to indicate system
alarms.
14.2.4.3 Audible tone frequencies shall be between 500 Hz and
3000 Hz to ensure that alarms are heard by operators who
might have relatively poor hearing.
14.2.4.4 Audible tone decibel levels shall be loud enough to be heard
over normal control room background noise, but not so loud
as to cause annoyance or discomfort to personnel. For these
reasons, audible alarms should be approximately 25 to 30 dB
above the normal “background” noise level.
14.2.4.5 A variable tone shall be considered to help recognize
priorities, especially for the highest priorities.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 27 of 34
14.2.4.6 The audible alarm signal for an operator console shall
continue until either:
a) a “horn silence” is initiated at the operator console or
b) an active alarm is “selected” (on either alarm
summary or other displays.)
14.2.4.7 Silencing the horn shall not constitute alarm acknowledgment.
14.2.5 Alarm Printing
Printing of alarms at the time of the alarm or event shall be decided on
a per-project basis. Capabilities shall be provided on all systems to
produce a report of alarms and events during user-defined time periods
and to print-out the resulting report.
14.2.6 Alarm Acknowledgment
14.2.6.1 Alarms may be acknowledged only at consoles configured
for those alarms.
14.2.6.2 It shall be possible for an operator to acknowledge any alarm
configured at a workstation by no more than one action.
14.2.6.3 An alarm shall be acknowledgeable only if it is shown on an
active display.
14.2.7 First-Out
First-out alarms shall be used to pinpoint the origin of an automatic
equipment trip.
14.2.8 Nuisance and Inhibited Alarms
14.2.8.1 Nuisance alarms may be caused by a monitored process
variable continuously going into and out of alarm.
This situation shall be minimized by setting appropriate
alarm limits and alarm dead bands.
14.2.8.2 Nuisance alarms may be caused when a process is in a
shutdown or out of service condition for an extended period.
Alarm inhibition on a group basis shall be provided for use
in such situations.
14.2.8.3 A list of inhibited alarms shall be provided and available for
both display and printing. Other system processing
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 28 of 34
functions, e.g., data acquisition, control and logging, shall
continue for inhibited alarms.
14.2.9 The following BMS system alarms and messages shall be implemented
but not limited to:
a) Failed modules,
b) Communication errors,
c) Power supply failures,
d) Cabinet high temperature, smoke or incipient fire detection,
e) Diagnostic error detections and messages.
14.3 Logging of Operation and Engineering Actions
14.3.1 A log shall be available for tracking operation and engineering actions
or changes. Actions shall be further divided into “Operation” or
“Engineering.” Optionally this log should track user name, time of
change and an abbreviated text of the change.
14.3.2 Operation actions include but not limited to normal operator actions
that are to be logged in history files including:
a) Change made to the mode of a controller,
b) Change made to the setpoint of a controller,
c) Change made to the output of a controller,
d) Responses to operator prompts,
e) Toggle of an alarm between inhibit and enable,
f) Change made to alarm limit,
14.3.3 Engineer Actions consist of normal engineer actions that are to be
logged in history files, including but not limited to:
a) Change made to tuning parameters,
b) Download or modification of tag or module configuration,
c) Modification to software used by the BMS,
d) Forcing member of a redundant pair on or off primary status,
e) Placing devices on-line or off-line,
f) Placing a tag on-scan or off-scan,
g) Responses to engineer prompts.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 29 of 34
14.4 Operation and Engineering Prompts
14.4.1 Operator Prompts
14.4.1.1 Operator prompts include operator guidance messages which
require a response. These may be provided by smart
alarming techniques or be part of a semi-automatic sequence
where each step requires operator approval before it is
initiated.
14.4.1.2 Operator prompt message shall also serve as the visual
indication.
14.4.1.3 No password or key is required for this message.
14.4.2 Engineer Prompts
14.4.2.1 Engineer prompts include guidance messages which require
a response from a user performing control system functions.
14.4.2.2 The prompt message shall also serve as the visual indication.
15 History
15.1 On-line History
15.1.1 All BMS configuration parameters, including tag data, workstation
configurations and controller module configurations shall be stored on
redundant on-line media.
15.1.2 On-line historical data shall be stored for access via history trends,
displayed listings, and printed listings.
15.1.1 Circular files on a FIFO basis shall be implemented such that the latest
records are retained when buffer or list overflow occurs.
15.2 Real-Time Performance Management (RTPM)®
15.2.1 Utilities shall be implemented to facilitate gathering, analysis,
distribution and visualization of data through RTPM.
This implemented capability shall allow the recall of the data to enable
the use of all historical data analysis functions.
15.2.2 A method shall be provided to transfer and retrieve historical records
from RTPM.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 30 of 34
16 Integration and Interface
16.1 General Interface Requirement
16.1.1 Interfaces between the BMS and associated subsystems or auxiliary
systems shall use standard hardware and software devices, which are
compliant with industry standard protocol such as BACnet, LonWorks,
and Modbus which is offered as a standard product by both the BMS
system vendor and the subsystem vendor.
16.1.2 Redundant communication interfaces shall be supplied for:
a) Critical subsystems.
b) Subsystems where loss of communication will result in the
significant degradation of control functions.
16.1.3 Where redundant communications are specified, no single component
failure shall result in the loss of communication to any subsystem.
16.2 Time Synchronization
16.2.1 Time clocks for all stations which are part of the BMS shall be
synchronized to 100 milliseconds or better.
16.2.2 Time synchronization using GPS and networked time server which
supports Simple Networked Time Protocol (SNTP) is the preferred
method for synchronization of all servers connected to the BMS.
16.2.3 Synchronization shall be performed at a minimum of once every
24 hours.
17 Units of Measurement
The allowable units of measurement are specified in SAES-J-003 under the section
titled, “Measurement Units” and shall apply.
18 Wiring and Power Supply
18.1 Electrical Wiring
18.1.1 Electrical and wiring up to but excluding vendors' standard cabinets
shall be designed in accordance with Saudi Aramco Engineering
Standard SAES-J-902.
18.1.2 Marshaling cabinets shall be designed in accordance with Saudi
Aramco specification 34-SAMSS-820.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 31 of 34
18.2 Power Supply
18.2.1 Two separate, independent, electric circuits shall be supplied to power
redundant modules. If a simplex UPS is provided, one of the feed to
system redundant power modules shall be supplied from a raw
120 V / 230 V / 240 V power feed.
18.2.2 Power Supply circuits shall be clearly labeled. Branch circuits or
power cords to redundant modules shall be clearly labeled identifying
the circuit that they are connected to.
18.2.3 Redundant internal power supply modules shall be provided for the
following:
a) Controllers
b) Input and output Units
c) Communication Units
18.3 Power Supply and Distribution to BMS Consoles and Workstations
18.3.1 BMS workstations shall be fed from UPS power sources.
This requirement applies to the processor, monitor, and other
peripheral devices associated with the workstation.
18.3.2 For redundant workstations within an operator console, it is acceptable
to supply power to the workstations using either of the configurations
described below:
a) Each workstation shall be fed from a single UPS power circuit;
provided that each workstation is fed from a separate UPS power
source.
b) Each workstation shall be fed from two separate power circuits
utilizing a power switching device to maintain continuous power
on loss of a single circuit. One of these circuits shall be fed from
UPS power source and the other may be fed from utility power.
18.3.3 Workstations which are not supplied in a redundant configuration shall
be powered as described above in 18.3.2.b.
18.3.4 Commercially available multiple outlet power strips (i.e., Tripp-Lite
model UL 24CB-15 or similar) may be used to distribute power to
multiple components of a workstation (i.e. processor, monitor, and
associated peripheral devices) provided that each power strip feeds
equipment associated with a single workstation.
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 32 of 34
18.4 Utility Power
18.4.1 One, duplex-type convenience outlet, rated at 120/230/240 VAC,
15 amp shall be provided within each cabinet for utility power.
Convenience outlets shall be wired to a separate terminal strip which in
turn is sourced from a non-UPS AC distribution panel.
18.4.2 Two, duplex-type convenience outlets, rated at 120/230/240 VAC,
15 amp shall be provided within each console for utility power.
Convenience outlets shall be wired to a separate terminal strip which in
turn is sourced from a non-UPS AC distribution panel. The outlets
shall be placed on opposite sides of the console to enhance availability.
18.5 Grounding
18.5.1 Grounding design shall be per vendor standard recommendations and
per the applicable sections of SAES-J-902; whichever is more
stringent.
18.5.2 Any conflicts in grounding design shall be resolved per the provisions
of Section 2.2.
19 Environmental Conditions
19.1 Air-Conditioned Buildings
19.1.1 Equipment installed in air-conditioned buildings shall be designed for:
a) Ambient temperature range: 10°C to 35°C
b) Ambient relative humidity: 20% to 80%.
19.1.2 Heat dissipation calculations shall be submitted for any cabinet that
houses power supplies, PCs or other heat generating components.
The calculations shall show that the components installed inside the
cabinet will not be exposed to a temperature above their temperature
rating. Ambient temperature outside the cabinet of 25°C shall be used
for calculations.
19.1.3 Cabinets requiring heat dissipation shall comply with requirements of
34-SAMSS-820 Section 6.3.
19.2 Outdoor Environment
19.2.1 All equipment specified for outdoor installation shall be designed to
meet the following outdoor environmental conditions:
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 33 of 34
a) Ambient temperature range:
Outdoor Sheltered = 0°C to 55°C (1)(2)
Outdoor Unsheltered = 0°C to 65°C (2)(3)
b) Ambient relative humidity: 5% to 95% non-condensing.
Commentary Notes:
1) "Sheltered" refers to permanent, ventilated enclosures or buildings, or permanently fixed sunshades with a top and three sides.
2) For equipment which dissipates internal heat and is installed in custom engineered enclosures (e.g., enclosures not included in the original manufacturer's temperature certification), an additional 15°C shall be added to the above maximum temperatures. An example, for the "outdoor unsheltered" case, the equipment shall be designed for a maximum operating temperature of 65 + 15 = 80°C.
3) For the outdoor installations only, the designer can take credit for forced or passive cooling to eliminate or reduce the 15°C heat rise. For example, if vortex coolers are used, the heat removal capacity of the coolers may be subtracted from the generated heat. No more than 15°C reduction in temperature will be given as credit. The designer shall substantiate his claim by providing the support data and calculations.
19.2.2 All equipment specified for outdoor installation shall be compliant
with the following contaminant levels:
19.2.2.1 Dust Concentration
Usual airborne dust concentration is 1 mg/m³. During
sandstorms, dust concentrations may reach 500 mg/m³.
Particle sizes are as follows:
95% of all particles are less than 20 micrometers.
50% of all particles are less than 1.5 micrometers.
19.2.2.2 Elements present in dust include compounds of calcium,
silicon, magnesium, aluminum, potassium, chlorides and
sodium. When wetted (high humidity conditions) these
compounds function as electrolytes and can result in severe
corrosion.
19.2.2.3 Other pollutants present in the atmosphere under the most
extreme conditions are:
Document Responsibility: HVAC Standards Committee SAES-K-011
Issue Date: 27 March 2012
Next Planned Update: 27 March 2017 Building Management System
Page 34 of 34
H2S 20 ppm (vol/vol)
Hydrocarbon 150 ppm (vol/vol)
SO2 10 ppm (vol/vol)
CO 100 ppm (vol/vol)
NOx 5 ppm (vol/vol)
O3 1 ppm (vol/vol)
19.2.3 Equipment which is not enclosed or hermetically sealed, but is situated
outdoors shall be protected against corrosion and operational failure
due to wind-borne sea water spray and the accumulation of wetted salt
(sodium chloride).
20 Documentation
Comprehensive documentation shall be provided as listed below to ensure that the BMS
is engineered and configured in a consistent manner. It also ensures that a BMS project
is executed properly, that operating personnel are provided with accurate drawings and
manuals and that maintenance personnel will be able to trouble shoot and repair the
BMS, post installation.
The following are required:
20.1 Standard vendor manuals and catalogs shall be provided in CD-ROM or other
electronic media. Formats to be in PDF or Microsoft Word.
20.2 Instrument and configuration data bases Microsoft Excel, Access or Intools.
20.3 Three complete copies of all final project documentation shall be submitted in
electronic format on CD-ROM or DVD.
Revision Summary
27 March 2012 New Saudi Aramco Engineering Standard.