25 5000 - Intelligent Building Management System (IBMS)

NISHAN TOWER-COM 019 -LUSAIL MARINA, DOHA, QATAR ELECTRICAL SPECIFICATIONS
SECTION 25 5000
INTELLIGENT BUILDING MANAGEMENT SYSTEMS (IBMS)
PART 1 - GENERAL
Drawings and general provisions of the Contract, including General and Supplementary
Conditions and Division 01 Specification Sections, apply to this Section.
1.01 SECTION INCLUDES
A. This Section includes supply, installation and testing of Intelligent Building Management
System.
B. Related Sections include the following: (To be read in strict conjunction with)
1. Division 14 – Section 14 2100 “Electric Traction Elevators”
2. Division 14 – Section 14 2100 “Escalators”
3. Division 27 – Section 27 1500 ““Communications Horizontal Cabling”
4. Division 27 – Section 27 1300 ““Communications Backbone Cabling”
5. Division 26 – Section 26 0526 “Grounding and Bonding for Electrical
Systems”
6. Division 26 – Section 26 0529 “Hangers and Supports for Electrical
Systems”
7. Division 26 – Section 26 0533 “Raceway and Boxes for Electrical Systems”
8. Division 26 – Section 26 0536 “Cable Trays for Electrical Systems”
9. Division 26 – Section 26 0553 “Identification for Electrical Systems”
10. Division 26 – Section 26 2713 “Metering System”
11. Division 26 – Section 26 2413 “Switchboards”
12. Division 26 – Section 26 2419 “Motor Control Centres”
13. Division 26 – Section 26 2923 “Variable Frequency Motor Controls”
14. Division 26 – Section 26 3323 “Central Battery based Emergency Lighting
Systems”
15. Division 26 – Section 26 3353 “Static Uninterruptable Power Supply”
16. Division 26 – Section 26 3600 “Transfer Switches”
17. Division 27 – Section 27 2000 “Data Communications”
18. Division 28 – Section 28 1300 “IP Access Control System”
19. Division 28 – Section 28 2300 “IP Video Surveillance System”
20. Division 28 – Section 28 3100 “Fire Detection and Alarm System”
1.02 SCOPE
A. The IBMS shall serve as global facility management system and be integrated to form
one project-wide system - Intelligent Building Management System (IBMS) with
common operator window. An example of such a solution is Enterprise Building
Integrator (EBI as offered by Honeywell), Total Building Solution (TBS, as offered by
Siemens) or an equivalent solution.
B. The IBMS shall without any special modification support a model of “centralized
command and control across multiple developments”, to enable facility manager to
manage and control multiple projects from a single / multiple command centre(s).
MZ Architects INTELLIGENT BUILDING MANAGEMENT SYSTEM
25 5000- Page 1 of 26
C. The IBMS shall facilitate intelligent management of all building services.
D. The following system shall be incorporated into the IBMS:

1. Mechanical Services (the BAS):
a. Air Conditioning
b. Smoke Ventilation
c. CO Detection & Control
d. Plumbing
2. Energy Management
a. BTU Metering (revenue) and (monitoring)
b. Electrical Energy Metering (monitoring)
c. Water Metering (monitoring)
3. Electrical systems:
a. Lighting Control (common areas)
b. Automatic transfer switch
c. LV Panels, Main / Sub main Switchboards, Distribution Boards & Motor
Control Centres (MCC)
d. Uninterrupted power supplies (UPS)
e. Central Battery System
4. The Security Management System (CCTV, Access Control)
5. Miscellaneous telecommunications systems
6. Elevators and escalators
7. Maintenance Management of all Building Services equipment
8. Provisions for future Facility Management
9. Status only of devices and equipment related to Fire mode operation of the
building. Fire Detection and Alarm system will operate independently, but it will
be integrated to IBMS to provide additional alarm status notification.
1.03 INTEGRATION FUNCTIONALITY
A. Mechanical Services
1. Provide full functionality
B. Energy Management
1. Provide fully functional integration for monitoring purposes
2. Refer to the Schedule of Points for detailed requirements
C. Electrical systems: Automatic transfer switch, LV Panels, Main/ Sub main Switchboards,
Distribution Boards & Motor Control Centres (MCC )
D. Uninterrupted power supplies (UPS)

1. Provide full technical diagnostic capabilities
2. Provide automatic real-time notification to vendor of UPS failure
3. Provide notification of impending UPS shutdown on IBMS
4. Provide coordinated, automatic IP (e.g. through SNMP protocol) and IBMS
equipment shutdown on expiry of UPS battery autonomy time
E. Lighting Control
1. Provide full operational scheduling capabilities for all controlled circuits

25 5000- Page 2 of 26
F. Central Battery System

1. Provide alarm status notification of equipment and devices as defined in the
Schedule of Points
2. Automatic –periodic testing and reporting is excluded from IBMS integration as it
will be carried out by the Central Battery System management
G. The Security Management System

H. Miscellaneous telecommunications systems

1. Provide monitoring and alarm only of major LAN equipment
2. Provide coordinated, automatic LAN (e.g. through SNMP protocol) and IBMS
equipment shutdown on expiry of UPS battery autonomy time
3. Refer to the Schedule of Points for equipment list
I. Elevators and escalators

1. Provide alarm status notification of equipment and devices as defined in the
Schedule of Points
2. Automatic system testing and reporting is excluded from IBMS integration as it
will be carried out by the Elevators and escalators management system
J. Fire Management System

1. Fire Detection and Alarm system will operate independently, but it will be
integrated to IBMS to provide additional alarm status notification of equipment
and devices related to Fire mode operation of the building. Coordinate with Fire
Alarm System supplier.
2. Integrate the Fire Alarm system into the IBMS.
a. Alarm screen with appropriate graphics and location of activated devices
superimposed on relevant part of the building layout shall automatically
appear on designated workstations and audible signal shall alert the
operator. The alarm screen displays the building map in the background
with alarm locations positioned on the map. The alarm screen can span
several pages for buildings with more floors than can fit on a single
screen. The alarm managements system is able navigate between the
pages and zoom in on the floor where the alarm is located.
b. Any Fire Alarm system malfunction shall be annunciated in similar
approved manner
3. Refer to Sequence of Operation for HVAC Controls, for relationship with smoke
control system.
4. Refer to Fire Strategy for integration with Access Control and Security
Management System
1.04 SYSTEM ARCHITECTURE
A. The IBMS shall use IEEE 802.3 Standard Local Area Network (LAN) for
communications
B. Seamless integration is required with guaranteed interoperability for:

1. Data sharing
2. Alarm and event management
3. Scheduling
4. Trending
5. Device and network management

25 5000- Page 3 of 26
C. The IBMS shall use a Client Server architecture based on a modular computer network,
utilizing industry standard operating systems and protocols, and server components
tested for reliable non-stop 7/24 operation.
D. The architecture shall support distributed servers in a Distributed Server Architecture

(DSA) to allow multiple and independent systems to communicate together for data
exchange in order to provide an easy management and avoid duplicate work .
E. The architecture shall provide two levels of processing and control:

1. Central System Level: standard Servers and Workstations.
2. Automation Level: local microprocessor based units that can interact between
them and communicate with the Central System Level providing local processing
and storage. This level shall be as independent as possible in order to provide
full functionalities even in the event of a failure of the Central System or an
outage of communication links.
F. Multiple protocols: the IBMS shall allow communications with a wide variety of
proprietary and third party control devices utilizing off the shelf driver packages. It shall
support BACnet, LON, Modbus and OPC standards for open system communications.
Whenever possible and convenient, open protocols shall be chosen over proprietary
ones.
G. High availability configurations shall be integrated in the system design in order to

ensure operation in critical environments. Redundancy shall apply to both servers and
communication links at the Central System Level.
H. Integrated Maintenance Management

1. The IBMS shall provide an integrated facility for maintenance management of
plant and equipment. The maintenance facility shall tightly integrate with the
IBMS to retrieve data from field devices to determine when equipment or plant in
the field requires maintenance
2. The maintenance facility shall automatically raise a works order request for a
piece of equipment when certain maintenance conditions are met. Types of
configurable maintenance events shall include duty cycles, run hours, and high
data values. The works order shall be automatically printed or emailed to the
configured responsible individual.
3. The user interface shall be based on Web technology, with all regular
maintenance facility interaction occurring through a standard web browser.
Systems that require additional software on client machines to allow viewing and
configuration of the maintenance facility shall not be acceptable.
4. The maintenance facility shall use a standard reporting tool for generation of
maintenance reports. Such reports shall include past and present works orders,
equipment lists and equipment history reports. User customization of reports
shall be possible via the standard reporting tool.
5. The maintenance facility shall store common asset information and provide easy
addition of customer-defined information. User access shall be configurable, to
enable user capabilities to be tailored or limited. It shall be possible to use
equipment templates to allow definition of equipment with common data
requirements without having to repeat data entry.
I. Scheduled Maintenance Parts Inventory Database

1. Aimed at future Facility Manager, this database shall include detailed inventory
of all equipment parts that are to be periodically replaced [in addition to those

25 5000- Page 4 of 26
that happen to be broken and need immediate replacement] e.g. air conditioning
filters, water plant filters / consumables etc.
2. All parts shall be named / bar-coded according to a uniform, project wide system.
Contractor to develop such system for Client’s approval prior to any equipment
order.
3. The Contractor is responsible for ensuring that equipment / parts are bar-coded
accordingly and equipment delivered to site is entered into the database
promptly and correctly.
4. Refer to Project Manager for further requirements.
5. The database shall be backed up periodically with a Windows backup utility to a
separate disk.
1.05 CABLE SPECIFICATION
A. Structured Cabling System shall be used within the buildings as much as practicable
B. In addition, proprietary specification cables most suited to each application as

recommended by manufacturer shall be used.
1.06 PROJECT SPECIFIC CONFIGURATION
A. Project consist of:

1. Building Common Area Services
B. GENERAL PRINCIPLES
1. Integrated approach is used to management of all systems.
2. The CCF at the Engineering Control room at first floor, manned 24 hours 365
days, will manage the entire project.
3. The CCF shall accommodate IBMS workstations, central battery system
workstation, lighting control system workstation, servers, printers UPS and
peripherals including LCD Displays.
4. System Control and Monitoring via the Web: for specifically nominated personals
only without access to an Operator Workstation, the IBMS shall provide the
ability to control and monitor site resources via a standard Intranet site. This
Intranet site should be made accessible and properly formatted for both PCs and
PDAs or handhelds.
5. The system shall perform checks on data integrity of all data acquired from each
device. If an invalid or time out response is received, the data shall be ignored
and the system will record the transaction as an error. Communications statistics
shall be displayed as standard on the system and shall also be available as part
of the reporting system or custom displays.
6. Once a control device is configured and placed in service, the system shall
automatically begin background diagnostic scanning of the device to ensure that
communications are monitored independently of any monitoring scanning.
C. Distributed System Servers (IBMS Servers)

1. Specifically, real-time and history data in any server must be available to any
other server for monitoring and control. Features supported must include:
a. Access: Access to data shall be global, such that users at Operator
Workstations on one server can access data on any other server. It shall
not be necessary to configure more than a single entry in the data base
for an employee or a visitor or an alarm signal, regardless of the number
of servers accessing the data.
25 5000- Page 5 of 26
b. Alarms / Messages: Operators and workstations at any server must be

able to see alarms from any other server. It shall not be necessary to
configure alarms more than once, regardless of the number of servers
accessing the data.
c. Graphics / Reports / Applications: All graphics, reports, and applications
at a server shall have the same distributed access to data on other
servers as described above for operators and workstations. It shall not be
necessary to configure more than one point for each data value or signal,
regardless of the number of servers accessing the data.
D. HOT BACKUP SERVER (IBMS Redundant Server)

1. This facility shall enable the system server to operate in high availability
architecture with no single point of failure.
2. The system shall utilize a pair of similarly configured computers in a hot backup
configuration where at any point in time, one is acting as Primary computer and
the other as the Hot Backup computer. An on-line database duplication
mechanism must be supported in order to ensure perfect synchronization of
recorded data.
3. The database duplication must be performed on a per-transaction basis:
a. To ensure that the duplicated Backup database is consistent at all times
with the Primary database.
b. To avoid unnecessary overloading of field devices caused by duplicate
polling.
4. It must be possible to remove one of the redundant systems for maintenance
without interrupting operation, and upon its reinstatement, re-synchronize the
databases, again without interruption to system operation. A method of manually
initiating a fail over must be provided to assist maintenance operations to a
specific computer. An example of an acceptable high availability database
system solution is Oracle RAC (Real Application Cluster) or equivalent which
allows for multiple nodes on a clustered system to mount and open a single
database on shared disk storage. In case of a single node failure, RAC allows
the database service to continue operation in the remaining working nodes. In
contrast, a non-RAC database presents a single point of failure as it is only
available on a single node. If that node fails, the database service will be down.
5. Failure of either system must be announced via the standard alarming features
of the system. Fail over switching from the failed Primary computer to the Hot
Backup unit shall be accomplished in a totally bump less mode.
6. Duplicating interfaces of field devices (such as card readers, I/O interfaces, etc.)
to two different and independent systems will not be accepted as a valid solution.
7. The server should support adequate RAS features and should have high
availability. Memory should be ECC registered DDR2, DDR3, or FB DRAM of at
least 4GB capacity.
8. Server processors should at least be dual cores.
9. At least 3-disk RAID5 hard disk configuration.
E. CONTROLLERS
Refer to relevant specifications for different systems.
1.07 VENDOR REQUIREMENTS
A. The vendor shall be a recognized leader in Facilities Integration, Building Automation

Systems, Security Management, and Life Safety Management capable of supplying all

25 5000- Page 6 of 26
necessary support services including hardware and software support, configuration

services, system installation and commissioning and on-going support.
1.08 QUALITY ASSURANCE
A. The software supplied, as part of this system shall be developed in an ISO 9001
compliant environment.
1.10 Delegated Design Responsibility:
A. Notwithstanding the drawings and other information provided to the Contractor, the
Contractor shall be fully responsible for the design, detailing of the works described
herein, including (without limitation) the comprehensive engineering analysis by a
qualified professional engineer, and shall provide a complete, and secure installation,
which shall meet the specified performance and design requirements indicated and
which shall be fit for their intended purpose. The Contractor indemnifies the Employer
and Design Consultant from any and all claims, costs and expenses arising from any
loss or damage in connection with any error in or failure of the Contractor’s designed
portion of the Works.
1.11 WARRANTY & MAINTENANCE PERIOD
A. 730 days commencing from the date of issue of the Taking-Over Certificate.
PART 2 - PRODUCTS
2.01 MANUFACTURERS
A. Approved Manufacturers: Subject to compliance with the requirements of the Contract

Documents, provide products by one of the following manufactures:
1. Honeywell (USA)
2. Siemens (Germany)
3. Johnson Controls (USA)
4. Schneider (France)
2.02 HARDWARE
A. Servers and Peripherals

1. The IBMS system server computer shall comprise of the following minimum
hardware:
a. Intel Xeon 6 core minimum with 15MB Cache processor running at least
3.0 GHz or latest available.
b. Min 64 GB of registered ECC, DDR4 memory
c. A PCI Express graphics card capable of at least 1280x1024 pixel
resolution and 256K colors, non-interlaced (70 Hz or better vertical
refresh rate) and 4GB of GDDR5 RAM. Two graphics cards are required
when the computer will support 4 LCD monitors.
d. A full function keyboard
e. Mouse pointing device, preferably optical

25 5000- Page 7 of 26
f. 360 GB SSD hard discs minimum of two numbers HDD RAID1- for OS
and 4 number HDD RAID5 for Data configuration.
g. RAID controller card.
h. A DVD / CD ROM RW drive
i. USB 3.0 ports
j. 10/100/1000 Ethernet card
k. 42” LCD Monitor (LCD Display).
2. The system shall be capable of supporting up to 40 simultaneous Operator
Workstation connections using a TCP/IP Local Area Network (LAN) subject to
hardware capacity on the server computer. The Network connection must allow
an unlimited number of casual users access to the 40 connections on a first-
come-first-served basis.
3. Servers shall be provided in dual-redundant configuration
4. Servers shall be provided as rack-mounted industrial computers
5. The servers shall be located in LCF and CCF facilities only
B. Server Rack
1. 42U size of approved make.
2. With lockable doors
C. Operator Workstation
1. The Operator Workstation shall comprise the following minimum hardware:
a. Intel Core i7 processor, 8MB Cache minimum, running at a minimum of
3.0 GHz
b. Min 16 GB of DDR3 SDRAM split over 2 memory channels.
c. A DX10 or better Super VGA graphics card capable of at least 1280x1024
pixel resolution and 256K colors, non-interlaced (70 Hz or better vertical
refresh rate) PCI Express with at least 256MB of GDDR memory.
d. Selected CCF workstation shall support up to four monitors (LCD
Displays). This may require a second graphics card.
e. A 240 GB SSD Hard disk drive.
f. A 12 function-key keyboard and Mouse pointing device, preferably optical
g. A sound card
h. Speakers, preferably attached to workstation for space saving
i. DVD +/-RW drive capable of playing DVD and CDROM discs, and
recording on DVDRW, DVDR, and CDRW disks
j. A microphone
k. USB 3.0 ports
2. 10/100/1000 Ethernet network card
D. Color LCD Displays

1. Color flat screen XVGA monitor with display screen.
2. The monitor shall output advisories in a dedicated and protected area of the
viewing screen, and speakers sound a unique audible tone in the event of
control system hardware malfunctions or restorations, as well as to sound a
unique audible tone in the event of a computer or communications malfunction.
3. Individual point information shall be coded via a minimum eight different colors.
These colors shall be defined with respect to system type and condition.
4. Individual point information shall include, but not be limited to:
a. Point identifier and expanded identifier.
b. Analog value.
c. engineering units
d. Mode units.
25 5000- Page 8 of 26
5. In Control rooms with 3 or more monitors, and when one operator oversees
multiple monitors from multiple workstations, it may be preferred to employ
peripheral sharing a KVM switch (e.g. offered by Belkin) to connect multiple
workstations to a single monitor. In addition to cutting down on the LCD display
and cost and occupied space, a peripheral sharing box allows the operator to sit
in front of a single monitor and easily switch between workstation displays
(similar to a TV tuner switching between TV channels) without leaving his/her
chair.
E. Alarm Printers
1. Alarm printers shall be high speed dot matrix printers to allow alarms to be
printed in real time as they occur. These shall be high quality printers used for
hardcopy alarm systems logs, information summaries, and control system
malfunction advisories. The Printer shall be multi font, black and white output.
2. It shall have a minimum operating speed of 200 characters / second or higher
3. The system shall be capable of establishing the line count per page on site for
form feed control
4. Printer shall be formatted to print on continuous paper.
5. Minimum of 300 dpi.
F. Report Printers
1. High quality, high speed laser printers for hardcopy system printouts.
2. The printer shall be multi font, Colour output.
3. It shall have a minimum operating speed of 200 characters / second or higher
4. Printer shall be formatted to print on standard A3 and A4 paper.
5. Minimum of 300 dpi.
G. Refer the system drawings for the location and quantity of the printers.
2.03 SYSTEM SOFTWARE

1. The IBMS system server shall be based around the latest Microsoft Windows
32/64 bit multi-tasking environment
2. Standard services supported by the server computer operating system will
include the following:
a. Multi-tasking Multi-user support
b. TCP/IP Network Support with firewalls filtering internet traffic.
c. Graphic Display Building Editor
d. Application software
e. Check pointing and recovery.
3. Software at the Operator Workstation shall comprise of:
a. Windows XP Pro SP2
b. TCP/IP Networking
c. Graphic Display Building Editor
d. Application software
4. The networking software shall use the industry standard TCP/IP LAN protocol.
5. All system peripherals shall be capable of being connected to the server
computer via the LAN.
2.04 APPLICATION SERVER SOFTWARE

1. The IBMS system server shall consist of IBMS application software and
database and utilities for backup.
2. Maintenance servers shall host the maintenance database application

25 5000- Page 9 of 26
2.05 APPLICATION WORKSTATION SOFTWARE

1. The workstations will come equipped with web browser and graphics applications
and run-time libraries, network management software, intrusion detection
software, database backup tools, and virus scan software with live virus update.
2. Support of html, xml, Javascript, Java.
3. (Optional) biometrics software and hardware for logging into workstation.
4. It is desirable for the security operator’s workstation to come with face matching
software and automatic car license plate recognition software
2.06 OPERATOR INTERFACE
A. General
1. The operator interface provided by the system shall allow for efficient
communication of operational data and abnormal conditions. Critical areas (such
as alarm icons) shall be visible at all times. A predefined area on the screen shall
provide operator messaging, and this area shall also be visible at all times. A set
of standard displays for configuration, and navigation around the system are to
be provided with every system and shall not require any additional engineering.
The system shall also provide an unlimited number of custom (facility specific)
displays created to meet the needs of the specific facility. In the graphical
display, an ability to zoom in/out on specific areas of the alarm map will be
provided. In the textual display, an ability to sort alarms based on various
parameters (e.g. priority, time, location proximity) will be provided.
2. The tool bar and pull down menus shall be fully configurable. Similarly, such
functions shall also be available via a standard set of Function-Key based
pushbuttons without requiring configuration. The operator interface shall support
the ability to “full screen lock” the window so users cannot access other
applications.
3. It is understood agreed by the contractor that the work herein described shall be
complete in every detail so as to provide a complete and fully functional system
even though every item necessarily involved is not specifically mentioned.
B. Web Browser Operator Interface

1. The operator interface shall also be fully available through a web browser. From
a standard browser such as Microsoft’s Internet Explorer, an operator shall be
able to perform all functions on the same standard and custom displays as used
in the standard operator interface. The browser interface shall provide login and
security authentication in the same way as the standard operator interface.
C. Operator Interface Connection

1. The operator interface shall be flexible in its connection to the system server(s).
An Ethernet LAN connection shall be used between the Server and the Operator
Workstations. The operator interface shall provide standard dial-up modem
support using Microsoft Remote Access Service (RAS).
2. The operator interface LAN connection shall also be flexible to support both
permanent and casual access to the system server either through the standard
operator interface or through a browser. Licensing shall be based on the
“number of simultaneous operator connections” on a “First Come First Served”
basis. Those users with casual access shall automatically disconnect from the
FMS server after an idle timeout period.
D. Operator Interface Characteristics

25 5000- Page 10 of 26
1. The system shall provide a Windows operator interface with the following
minimum capabilities as standard. No custom programming or scripting shall be
necessary to produce these:
a. Window re-size, Zoom in, Zoom out
b. Dedicated graphics, icons and Pull Down Menus to perform the following
management functions:
1) Associated Alarm Display
2) Alarm or Alert Summary
3) Alarm or Alert Acknowledgement
4) Display Sequence Forward/Backward
5) Previous Display Recall (minimum of 8 displays)
6) Cardholder Detail
7) Pop up face plates
8) Alarm Banner showing highest priority, most recent (or oldest)
unacknowledged alarm
9) System Date and Time Zone
10) Current security Level
11) Workstation connection number
12) Alarm Annunciation
13) Communications Fail Annunciation
14) Operator Message Zone
15) Energy and BAS (HVAC, Mechanical, Electrical, UPS, Generator,
Lighting Control, Central Battery System) Readings. Automatic
Alert/Alarm Trigger Programming by the Operator is desirable.
16) Fire Alarm Reading
17) Security Alarm Reading
18) Disabled Person Alarm Reading and Initiating Communication
19) Elevator and Escalator Malfunction Reading
20) Call for Assistance Reading and Initiating Communication
21) Maintenance Display and Scheduling
22) CCTV Camera Display and Recording
23) History and Trending
24) Reporting
2. These operator interfaces provide operators with the ability to print or display
reports, display and sort events, acknowledge alarms or events, take actions on
alarm triggers such as dispatching crews, display information about card holders
who have entered a controlled door during a period of time, controlling CCTV
cameras, displaying alerts which have not been acknowledged, and a variety of
other actions designed to efficiently manage the site.
2.07 OPERATOR SECURITY AND SIGN-ON
A. Security
1. If necessary, each operator may be assigned a user profile that defines the
following:
a. Security and/or Control Level
b. Operator Identifier
c. Unique Password. Password must follow strict guidelines for secure
passwords (e.g. must not include name or substrings or older passwords)
and must be change periodically (e.g. each month).
d. Area Assignment / Area Profile
e. Start display for that operator
f. Timeout Value for that operator
25 5000- Page 11 of 26
2. Any actions initiated by the operator shall be logged in the Event database by
operator identifier. In addition, any control actions shall only be allowed if the
control level configured in the operator's profile exceeds the level assigned to the
controlled point.
3. Utilities shall be provided to allow administration of the operator passwords.
B. Security Levels
1. The system shall support at least six levels of operator security. The functions
allowed from each security level shall be as follows:
a. Level 1: Signed off mode - View start-up display only.
b. Level 2: View only - The operator shall be able to view displays.
Typically used for an inexperienced operator.
c. Level 3: Permit all Level 1 and 2 functions and in addition the
operator shall be permitted to control points such as start/stop,
disable/enable, etc. and acknowledge alarms as they occur.
d. Level 4: Permit all Level 1 through Level 3 functions in addition to
accessing master time schedules, system peripherals allocation, change
parameters, build reports and use most standard system configuration
displays. This level shall typically be reserved for the system supervisor.
e. Level 5: Permit all Level 1 through Level 4 functions in addition to
accessing the engineering functions such as building and linking displays,
allocating keyboard push button assignments, etc. (Reserved for the
system engineer).
f. Level 6: This is the highest level of station security and shall allow
the user unlimited access to all station functions (Typically reserved for
the system manager).
2. Any operator breach of security shall be visible to the CCF operator.
C. Sign-On/Sign-Off
1. The operator shall be permitted to sign on to the system if the correct Operator
Identity and the Operator Password have been entered. This password shall be
encrypted in the database. It shall also be possible to have the system linked to
Windows such that the operator uses their Windows Account Name and
password to sign on to the system. This ensures that operators only need to
remember one set of credentials.
2. After a series of three unsuccessful attempts to sign-on the Operator
Workstation interface shall be locked for a configurable period of time. This
event will be also made visible to the CCF operator. The lockout period shall be
set via system configuration displays. During Operator Workstation lockout the
other Windows functions of the computer running the Operator Workstation
software shall not be affected.
3. It shall be possible to assign operators either single or multi-user passwords.
Single user passwords enable the operator to sign-on to only a single Operator
Workstation thus preventing simultaneous sign-on be the same operator.
Operators with the highest sign-on security level who may require simultaneous
access to more than one Operator Workstation would typically use the multi-user
password.
4. Each operator shall be assigned a password and a set of authorized areas and
time periods. The operator may sign-off at any time by issuing a sign-off
command.
5. A keyboard time-out feature shall be provided such that the operator shall be
automatically signed off after a defined period of keyboard inactivity. It shall
optionally be possible to configure automatic call-up of a "logged-out" display
when this occurs to hide previously displayed restricted information.
25 5000- Page 12 of 26
D. Duress
1. It shall be possible for an operator to indicate that they are signing on under
duress. The system shall recognize that the operator is signing on under duress
and it shall then be able to issue a control to alert appropriate assistance.
E. Command Partitioning
1. It shall be possible to assign to each operator a set of allowed commands for
each assigned area, where an area is a group of points. These commands can
be mapped against the output state of any given digital point in the respective
area to determine whether a control command is allowed for the particular
operator.
2. With this feature, it shall for example be possible to configure an operator to set
a digital point to ON, but to disallow the same operator from setting the same
digital point to OFF.
2.08 STANDARD SYSTEM DISPLAYS
A. The following displays shall be included as part of the IBMS system:

1. Alarm Summary Display
2. Event Summary Display
3. Point Detail Template Displays (for each point in the database)
4. Communications Status Displays
5. System Status Displays
6. Operator Scratch-pad Display
7. Face Plates for all common point types
8. Configuration Displays
9. CCTV Camera Displays and Recording
10. Maintenance Display
B. The Alarm Summary, Event Summary, Point Detail, Communications Status, System
Status shall not require any configuration.
C. Systems where standard graphical displays, showing all parameters for each system
Point, do not exist shall not be acceptable.
D. Interface Screens
1. The top-level site map gives the operator a quick status of the site with all kinds
of events displayed, and with additionally the top alarms and alerts and system
readings and command box displayed on the side of the site map.
2. Since all project components including floors in towers as well as underground
and over ground parking, mechanical, exterior, praying hall and energy centers
(see next section “PROJECT COMPONENTS” for complete list) cannot be
clearly displayed on a single screen, a hierarchy of screens is adopted. For
instance, the operator can expand the view of a specific building or zone and
display this view in a separate LCD monitor. From there the operator can zoom
in on a specific floor for an enlarged and clear view of the floor.
3. Specialized command screens are accessible from the command box list ,
displayed next to the top-level site map. By positioning the mouse over a
command in the command box followed by a single click, or by pressing down on
one of the F1-F12 keys. For instance, by pressing down on the Fire alarm
selection, the site map with visible fire alarms (fire alarm only, with no other
events) is displayed. The operator is then offered selection of project
components, and afterwards is offered a selection of floors or levels to choose
from.
25 5000- Page 13 of 26
4. Once the operator reaches the floor on which an alarm or alert has originated, by
moving the mouse –or clicking-- over the particular alarm or alert the operator
can retrieve all information on this event, including type, priority or severity,
physical location, time of alarm or alert activation, and status (acknowledged or
not).
5. An example of a top-level screen for the CCF follows. Thus the entire site map is
absent in the LCFs’ screen hierarchy.
6.
E. Project Components
F. Screen Levels
1. The alarm or alert event is displayed at various site hierarchy levels as follows in
the CCF,
2. Security Management (CCTV and Access Control System)
a. One screen per project component.
b. One screen per Floor
c. One screen for device detail
d. Card Holder Management
e. Guard Tour
3. Digital Video management (CCTV System)
4. Building Management - BAS (HVAC, Mechanical, Electrical, UPS, Generator,
Lighting Control, Central Battery System)
a. One screen per project component showing all systems (HVAC,
Mechanical, Electrical, UPS, Generator, Lighting Control, Central Battery
System)
c. One screen for each equipment/device detail
d. One screen for each system showing the riser
25 5000- Page 14 of 26
5. Life Safety management (Fire Alarm System)

6. Energy Management (Energy Monitoring and BTU Metering)
a. One screen per project component showing all systems (Energy
Monitoring and BTU Metering)
7. Elevator & Escalator Management – (Malfunction Alarm only)
a. One screen per project component
8. Disabled Person Alarm - (Malfunction Alarm only)
9. Call for assistance
2.09 CUSTOM DISPLAYS
A. The IBMS shall include a Graphic Display Building editor for the creation of site specific
graphic displays. It shall allow one-step online building of display static and dynamic
objects. It shall allow the displays drawn using the editor to appear exactly the same
when viewed from an Operator Workstation.
B. Displays shall be created in the HTML format. This is essential so that the displays can
also be viewed through a web browser as well as the normal IBMS operator interface.
The displays must be saved in the standard HTML format. All graphic elements shall be
available as HTML elements.
C. It shall be possible to link dynamic objects to the IBMS database. They shall allow
information to be displayed from the database or to allow an operator to interact with
them in order to make changes in the database and to perform control actions.
D. It shall include static and dynamic display objects on the one display. The editor shall
allow display objects to be manipulated by pointing, clicking and dragging. The editor
shall allow display objects to be drawn, re-sized, copied, grouped, rotated, aligned and
layered over each other. It shall be possible to copy and paste objects within and
between displays.
E. Display Scripting: It shall be possible to further animate display elements using standard
HTML scripts such as JavaScript or VBScript. A script editor supporting one of the
standard script languages shall be provided. By using script programs, individual
elements on the display may be manipulated. A proprietary scripting language or
additional scripting and drawing package shall not be acceptable.
F. Web Technology: All displays including custom displays shall be usable in a standard
Web Browser such as Microsoft’s Internet Explorer without modification. All displays
shall be usable in this manner enabling operators to completely operate the system

25 5000- Page 15 of 26
through a web browser if required. Displays may also incorporate data from an intranet,
the Internet, or ActiveX documents along with other building data.
2.10 ONLINE HELP AND DOCUMENTATION
A. The Operator interface shall also have access to online help and full system
documentation. Online help shall be fully searchable and cross referenced to all
relevant sections of the documentation. It shall be possible to browse the online help
and set “favorites” which link to commonly used sections of the help information. All
manuals shall be available online.
2.11 MONITORING AND CONTROL
A. Monitoring: the system shall support acquisition of data using the following techniques:
1. Periodic Scanning
2. Report by Exception
3. Data on demand
B. In order to minimize communications traffic, the system shall automatically block data
requests using contiguous addresses and the scan intervals to generate scan packets,
optimizing throughput for a given scanning load. The system shall also provide utilities
to examine scan packet allocation for each scan interval, and compile aggregate
statistics on communication link usage.
C. Device Control
1. A method shall be provided for control transactions issued by the operator to
ensure the integrity of the transaction. The priority of the control failure alarm
shall be configurable by the user.
2.12 SYSTEM DATABASE
A. The system shall provide a relational real-time database incorporating data from all
inputs. The database shall be configurable by the end user without the need for any
programming and shall be able to be modified on-line without interrupting operation of
the system. In addition to point-based information, the database shall also provide
historization capabilities for analog, digital, pulse and event based information. This
information shall be accessible by all facilities of the system such as custom displays,
reports, trends, user written applications, etc. The operator can issue a series of
database management commands and queries, and back up the database. The
database maintains event records, maintenance records, as well as cardholder
records.
B. The database uses ODBC (Open Database Connectivity) to allow access of these
databases by any ODBC-compliant tool.
C. The real-time database also triggers alerts to the operator in case of failed transactions,
or for routine backup operations.
D. The database’s cardholder records can be updated from external systems such as
Oracle (PeopleSoft) Human Resources database to remove any duplication with the HR
database system. When the HR database is updated, the cardholder records in the

25 5000- Page 16 of 26
database are updated in turn. The opposite update direction (database’s cardholder
records to HR database) is not permitted.
E. Database Structure
1. The real-time database shall support collection and storage of data.
2. Database backup shall be possible with the system on-line including backup of
historical based data. The backup shall be possible via standard Microsoft
Windows operating system utilities.
F. Grouping of Points
G. The IBMS system shall provide a means by which a number of alarm inputs, outputs
and other related points can be grouped together for more convenient monitoring and
control. Operations on a group of points will be done once and not repeated on all
group members.
H. History Management
1. Collection of historical point data shall be configurable as part of the point
definition. Once configured, this data shall be collected automatically.
2. History shall be able to be archived to an alternative file system or offline media.
Different archive settings shall be available for different history types.
3. History points should be displayed as line or bar charts and in numeric form.
I. Trending
1. The system shall provide flexible trending allowing real-time or archived data to
be trended in a variety of formats. In addition, trend data types shall be able to
be combined to allow for comparisons between data e.g. current real-time data
versus archived data.
2. All trend configurations must be possible on-line without interruption to the
system.
3. This information can guide the operator to take further security actions to
locations near devices with trends of frequent or increasing security breaches, or
to call for replacement of devices which have raised many false alarms in the
past.
4. The history points and statistical trends (averages) can be displayed graphically
as bar charts or in numeric. The system allows for overlaying histories or trends
of a number of points (cameras, card readers, fire alarms,…) on top of each
other for quick event correlation.
J. User Definable Database

In order to support other types of data such as user entered or calculated data from
application programs, the system shall also provide a User Definable database area
that can be fully integrated into the system. Data contained in this database must be
accessible by:
1. Custom Graphics
2. Custom Reports
3. Application Programs
4. Network Applications using a Network API
2.13 EVENT MANAGEMENT
K. It shall be possible to log an event such that it shall be journalized in the event file and
optionally printed on the event printer. The journal shall contain the following event
information:
25 5000- Page 17 of 26
1. Alarms and Alerts

2. Alarm and Alert Acknowledgements
3. Return to Normal
4. Operator Control Actions
5. Operator Login & Security Level Changes
6. On-line database Modifications
7. Communications Alarms
8. System Restart Messages
9. Database changes
L. Standard Displays shall be provided to show the current journal file with the most recent
event at the top of the display (LIFO). Subsequent page forward actions shall allow
display of progressively older events. Sorting and filtering of the journal shall be
possible directly on screen. Filters shall be able to be saved for future use. Filtered
events shall be able to be printed as an event report directly from the Event display.
Ideally pull-down buttons with a variety of sorting and information extraction commands
are available to the operator to relief him from typing any commands.
M. Events may be sorted by time and date, database partition or source of the event. It
shall be possible to apply filters to the list of events to limit the view of events to those
that match the filter. Filters may include multiple dimensions and wildcards and shall
also be able to be saved and restored for reuse.
N. It shall be possible to have an on-line event file as large as the disk capacity can
accommodate. For example, given the appropriate disk space it shall be capable of
storing more than 1,000,000 (one million) events on-line.
O. The event file shall store events online. The system shall be able to automatically or
manually archive these online events periodically, at a time period specified by the user.
Operators shall be notified by an alarm that event archiving is required if manual
operation is chosen. Events may be archived to tape, or to other media such as CD, Zip
drive, DVD, externally-attached mobile hard disc, flash memory stick, or to other file
systems. If archiving does not take place, the event system shall continue to collect
events until it reaches a nominated disk space limit. It shall then overwrite the oldest
events until archiving takes place or more disk space is made available.
P. Archived events may be restored to the system at a later time if required for reporting
purposes. Multiple archives shall be able to be restored at any one time. The system
shall indicate to the operator the range of events in a particular archive file.
Q. The event manager operates on the database which records event information such as
event type, name, time of event activation, and various event status changes and their
times and the person’s name that made these changes. Events include alerts such as
maintenance alerts, point changes of state, cardholder movement, all operator actions,
and changes in system status.
R. The event management system allows the operator to program event triggers. The
operator thereby can specify or modify old trigger settings of devices or parts, which
when met or exceeded, trigger alarms or alerts. For instance, energy alerts can be
triggered if the total consumed energy exceeds a certain BTU limit. A UPS alert is
triggered upon the volume of diesel remaining going below a certain threshold. A
generator alarm is triggered when its oil level dangerously goes below a certain
threshold or their generator temperature exceeds a certain number. Similarly, a central
battery system alert is triggered when the remaining battery energy goes below a
certain number.
25 5000- Page 18 of 26
S. The event manager is supported by a real-time event and maintenance database

system which automatically acts on the occurrence of alarm and alert events based on
pre-programmed actions set by the operator. For instance , upon the occurrence of an
elevator alarm, the database alarm entry for the elevator is set which triggers –if
programmed-- a call to the maintenance crew to immediately head to the elevator to
evacuate trapped people and to repair the malfunction.
T. The system also provides the operator with the ability to change the status of the event
such as acknowledging or deactivating alarms and alerts. Moreover, the event
management system provides the operator with instant notification of various entities
such as building manager, building engineer, security department, based on the nature
of the event. This notification can be in the format of sms messages, or prerecorded
audio message calls to mobile phones, or emails, or pagers.
2.14 ALARM MANAGEMENT
A. Alarm management shall be part of the IBMS and based upon common facilities and
procedures for all systems, SMS included.
B. Alarm Priorities
1. Each monitored point in the system shall be able to be assigned one of four
alarm priorities (Journal, Low, High, Urgent) to individual states. The lowest
priority changes of status shall only be journalized and optionally printed on the
Alarm/Event printer. Higher priority changes of status will appear in the Alarm
Summary and optionally printed on the Alarm/Event printer.
2. Within each of the four alarm types there shall be 15 sub-priorities available.
Each alarm priority shall have a configurable color. It shall be possible to
configure a time such that if an alarm is not acknowledged within this time the
alarm’s priority is elevated to the next level.
3. For each alarm priority, it shall be possible to configure a point such that if any
alarms of this priority occur, the point is controlled to the configured state. This
could be used to drive external enunciators such as sirens or lights. When an
alarm is acknowledged, it shall be possible to automatically issue a reset to a
controller to indicate the alarm is acknowledged and to attempt to reset the alarm
point.
C. Alarm Annunciation
1. Most recent, highest priority alarm message appearing on dedicated alarm
banner on the operator interface. Alarm message appearing on alarm summary
display.
2. Available Tone - based on a “*.wav” or other sound file for each alarm priority
3. Alarm message printed on the alarm printer
4. Alarm indicator flashing on the operator interface
5. Alarms shall be enunciated at the Operator Workstation even if there is no
operator currently signed-on.
D. Alarm Processing
1. Assigning an alarm to the point shall automatically cause the system to perform
the following actions when an alarm occurs:
2. The alarm shall be time stamped to the nearest second and logged in the Event
database with the Point Name (source), Alarm type, Alarm Priority, Point
Description, New value and Engineering Units
3. The point value which is in alarm shall turn red (or other configurable color) and
flash on any standard or custom display which uses that point.
25 5000- Page 19 of 26
E. Alarm Summary
1. Alarms shall be able to be viewed in a consolidated alarm summary which shows
all current or pending alarms on the system. This summary may be sorted by
time and date, database partition or source of the alarm. The fields shown on the
alarm summary must be configurable and it shall be easy to move or change the
alarms fields displayed. It shall be possible to apply filters to the list of alarms to
limit the view of alarms to those that match the filter. It shall be possible for the
operators to add comments to the alarm and these comments shall be stored
with the alarm.
2. Dedicated Alarm Banner and Alarm Indicator
3. A dedicated alarm banner shall appear on all displays showing either the most
recent or oldest (configurable), highest priority, unacknowledged alarm in the
system. This banner shall be clear when there are no unacknowledged alarms
for the operator to process. An alarm indicator shall also appear on all displays.
F. Alarm Logging
1. As well as being logged on the printer, alarms shall be logged to an event file for
future retrieval in alarm reports or archived to removable media.
2. Alarm Response Function Keys
3. The following dedicated function keys shall be provided on the keyboard for
alarm action:
4. ACKNOWLEDGE: After moving the cursor to the point in alarm on the screen
and selecting the point the operator shall be able to acknowledge an alarm by
pressing this key. This action shall be logged in the event file and on the printer
showing the operator ID with the alarm.
5. ALARM SUMMARY: By pressing a dedicated key at any time the operator shall
be able to view a display showing all currently active alarms. The alarm
messages shall be color-coded showing priorities. The operator shall be able to
view the alarms according to priority or sorted based on other fields. It shall be
possible to acknowledge alarms from this display and also go to the associated
display defined for the point.
6. ASSOCIATED DISPLAY: After moving the cursor to the point in alarm on the
screen and selecting the point the operator shall be able to bring up the display
applicable to that alarm by pressing this key. Just selecting the associated
display key directly will bring up the associated display for the point currently on
the alarm banner. This is generally a custom graphic showing the location of the
alarm in the facility.
G. Alarm Link to Digital Video Recordings

The system shall allow the linking and display of digital video recordings pertaining to
alarms. If there is any video footage in digital format that is relevant to an alarm, then
the alarm summary shall indicate this by the use of a special icon on the alarm. By
selecting the icon, the operator can then replay the relevant digital video footage of the
alarm incident.
H. Print Alarms as a Report

The filtered alarm summary should be able to be printed directly as a report. From the
alarm summary page, it shall be possible to view the current filtered list of alarms via a
print preview button. This shows what the alarms will look like when printed to the
configured report printer. From the alarm summary, it shall be possible to print the
alarms directly using the print button.

25 5000- Page 20 of 26
2.15 MAINTENANCE MANAGEMENT
A. The maintenance management system operates on the database which records entries
for the site’s devices and systems, their operation status (working, nonoperational,
under maintenance), and their scheduled maintenance.
B. The maintenance system allows the operator to schedule maintenance or replacement

of all parts, devices, or systems based on periodic maintenance needs or as a result of
sudden failure, or to query, retrieve or sort any database field, for instance to help assist
the operator in scheduling a group of devices’ maintenance at the same time.
Additionally, the operator may modify device thresholds which automatically trigger
maintenance service (e.g. efficiency dropping below 30%).
C. The system provides the operator with an easy notification or dispatch of maintenance
crew, or site engineer. The system can also generate reports including work orders,
equipment list, and equipment past history.
2.16 BUILDING MANAGEMENT (BAS)
This facility manages HVAC, Mechanical, Electrical, UPS, Lighting Control, and the
Central Battery System. Adjusting control levels, and checking readings from distributed
controllers are the main actions provided by the building management system.
2.17 CARD HOLDER MANAGEMENT
A. This facility operates on the database with has employee records from the Human
Resources database.
B. Cardholder entries include name of the card holder, company title, department or
organization to which the card holder belongs to, employee number.
C. Employees can be issued multiple cards, for instance each one to get them access to a
controlled door in different zones.
D. The system facilitates the process of issuing cards and allows editing many card
holders’ entries at one time by selecting them before the editing.
E. The database supports normal search and retrieve database queries on card holders
information, points such as access controlled doors and access level of card holders,
and access dates (including expiration). Access levels indicate which zones or points
(e.g. elevator) a card holder is allowed to access and at what particular times and days
(weekdays, weekends, holidays).

25 5000- Page 21 of 26
2.18 REPORTING
I. Reporting shall be part of the IBMS and based upon common facilities and procedures
for all systems.
J. The system shall support a flexible reporting package to allow easy generation of report
data. The reports provided shall include pre-configured standard reports for common
requirements such as Alarm Event reports and custom report generation facilities that
are configurable by the user.
K. Standard Reports
Configuration of standard reports shall only require entry of the schedule information,
and other parameters such as Point Name or wildcard, filter information, time interval
for search and destination printer to fully configure the report. Specifically, no
programming or scripting shall be required.
L. Additional Generic or Custom Reports

In addition, configurable report generation facilities must be provided to allow custom
reports to be produced. They shall be able to be configured at any time with the system
online, and shall be able to access any database values.
The database reporting facility generates reports on either the event (alarm and alert),
maintenance, or cardholder records of the database . Reports are generated upon
request by the operator, or automatically initiated by the occurrence of some event.
M. Importing and Exporting
The facility also allows for importing and exporting of data in csv format (for Microsoft
Excel) or plain ASCII.
N. Backup
Event reports display the time when various alarms and alerts were activated, and any
status changes they have had as a result of operator action. Report logs are saved on
files saved to disk and are periodically backed up on other media, and are printed for
hardcopy. The reporting facility allows these operations to stop if desired by the
operator.
O. Search
Moreover, the event reporting facility can report all points matching some search
keywords including status (in alarm, unoperational), time period (occurred between 1pm
and 5pm) and zone (occurred in zone 5). Thus the report will display all events
occurring between certain hours in a certain building. It can also be used to report all
activities by a specific operator between certain times.
P. Cardholder reports
The cardholder reporting facility can report all movements of card holders through
specific controlled doors (door history), list all controlled doors accessible by one
cardholder or by a group of cardholders, or list card information of specific cardholders.
2.19 HISTORICAL DATA ARCHIVING
Q. The system shall support archiving of historical data to allow a continuous record of
history to be built up over a period of time. Archived data shall be stored on the hard
25 5000- Page 22 of 26
disk of the system. The number of archives maintained on the system before transfer to
off-line media shall only be limited by the size of the hard disk. The system shall allow
the user to define the specific intervals of history to be archived to avoid archiving of
unnecessary data.
R. Once archived, the data shall be available for re-trending through the system trend
facilities in combination with the current on-line history or other archives. Providing the
archived history is present on the IBMS Server's hard disk, the trend facilities must be
able to access it transparently for display, when a user scrolls beyond current on-line
history limits.
2.20 Time Schedules
S. It shall be possible to specify time schedules for the control of all IBMS points. A single
time schedule shall define the control to any combination of day and time. The IBMS
time schedule must also provide the ability to override the normal schedule for holidays
or special occasions.
T. Configuring time schedules must be done through a graphical user interface whereby
the operator selects the appropriate time span from a calendar.
U. Where the control device supports an internal time schedule program, the IBMS shall
be able to upload, display, modify and download the control device time schedules.
Support for the control device time schedules shall be in addition to the IBMS time
schedules.
2.21 GUARD TOUR
A. This facility enables the operator to schedule a guard tour where the guard is required
to pass by specific site points such as cameras or door access controllers or fire alarms
in a defined sequence.
B. At each point the guard could be schedule to say switch cameras, disable alarms, or
switch lights on/off.
C. If the right sequence of events is not followed by the guard, alert reports are sent by the
system for review by the operator and other supervisors.
2.22 OPEN INTEGRATION
A. Any of the following Open Protocol Standards shall be used for integration of 3rd party
devices or systems. In coordination with other system suppliers include the Open
Integration protocols required to communicate with other systems. Refer to the drawings
and documentation for the details of other systems to be integrated into the IBMS.
B. BACNET (ANSI / ASHRAE 135)

1. The IBMS system shall be capable of communicating to other building
subsystems using the ASHRAE standard BACnet. The IBMS shall be capable of
acting as both a BACnet Operator Workstation and a BACnet Gateway.
2. An integrated BACnet Operator Workstation shall be provided which allows the
monitoring of BACnet devices via data acquisition and control.

25 5000- Page 23 of 26
C. LonWorks
The IBMS server shall provide a LonWorks Client to allow communication to LonWorks
Controllers. The LonWorks interface shall use LonWorks Network Services (LNS) to
maintain, monitor, and control LonWorks networks.
D. Modbus
The IBMS server shall provide an integrated interface to devices using the Modbus RTU
protocol, where the IBMS server shall be the ‘master’ and the external device or system
shall be the “slave”. The IBMS shall also support user definable data formats for
Modbus devices to accommodate the wide variety of formats in use in the industry.
E. OLE for Process Control (OPC)

The IBMS server shall provide an integrated OPC Client and integrated OPC Server.
F. Advance DDE (if used on the project)

The IBMS server shall provide an Advance DDE Client to allow connection to any
Advance DDE servers as specified by the Advance DDE standard from Rockwell
Software.
G. Data Exchange (if used on the project)

The IBMS system shall have the capability to interface to the point database of other
similar IBMS systems (i.e. nodes) on a TCP/IP network. This shall enable both the
acquiring of point data and issuing control outputs to other IBMS systems.
H. Data Exchange with Microsoft Excel

The system must be capable of exporting bulk data to Microsoft Excel. As a minimum
the following shall be supported:
1. Allow retrieval of data either periodically or snapshot
2. Allow retrieval of data via POINT.PARAMETER requests
3. Allow retrieval of tag names, descriptions etc
4. Allow retrieval historical data
5. Writing of values from Excel back to the supervisory system
I. Accessing the IBMS from third party web pages

1. Web-page controls and a web server interface to the IBMS shall be provided,
which allow other users to monitor & control a variety of IBMS -supervised
functions via their own Web pages created for their own Intranet or Internet and
viewed from a standard web-browser. For example, it shall be possible for
building manager to be able to view floor graphics, and to be able to monitor and
control security information fromn outside of the project.
2. It shall be possible to limit web browser access to IBMS facilities by means of
standard web and networking techniques.
J. Paging and external annunciation of System Alarms

The IBMS shall optionally provide a facility for sending alarm text from configured points
to the following external systems:
1. Alphanumeric pagers
2. Digital mobile phones with text message (SMS) support
3. Mobile call with prerecorded audio message to convey the alarm
4. Email
5. SNMP message.
K. Each point’s paging priority threshold shall be individually configurable, and individually
enabled or disabled. Each external device configured in the system shall have

25 5000- Page 24 of 26
individually selectable times and days of operation, an alarm priority threshold, and an
alternative device for use in escalation of unacknowledged alarms.
L. Server Scripting Engine

1. The IBMS system must have the ability to extend its functionality easily by the
addition of small script code to certain server functions. This will enable
additional customer specific functionality to be easily added to point, report and
server processing. For example, a script shall enable a calculation to be
performed and a number of points to be controlled based on another point going
into alarm state. Scripts shall be able to be attached to point processing, report
generation, server startup and shutdown, or executed on a periodic basis.
2. The scripting engine must support a standard scripting language such as
Microsoft’s VBScript. Access to the scripts shall be though an inbuilt scripting
editor which provides key work support and syntax checking as well as an
extensive range of online help including a large number of worked examples.
Proprietary scripting languages shall not be acceptable.
2.23 DIAGNOSTIC CAPABILITIES
A. The IBMS system must enable easy diagnostics of the health of the system. All
diagnostic information shall be viewable through an easy to use user interface and shall
be able to be easily exported as a stand alone collection of material for later analysis.
This information shall include the following:
1. Communications traces to selected controllers
2. All system log files
3. Details on system software installation
4. Application status information
B. It shall not be necessary to be an expert user in the system to gather diagnostic

information.
PART 3 - EXECUTION
3.01 TRAINING
A. Engage a factory-authorized service representative to train Owner's maintenance

personnel to adjust, operate, and maintain BAS/ IBMS.
3.02 JOB-SITE / TEST & INSPECTION
A. A minimum of 10 working days notice must be given to the client, associated

representative and engineer prior to the test proposed date.
B. If the performance test results are outside the specified tolerances, manufacturer will be
allowed to make adjustments and retest. Manufacturer will assume all expenses
incurred for the Employer's representatives to witness the retest. The onsite test shall
also include third party system interface testing. The third party interfaces shall be fully
demonstrated to the Engineer. The demonstration shall include all hardware and
software components associated with the interfaces. Third party system supplier's
authorized representatives shall be available during the interface testing. The training

25 5000- Page 25 of 26
shall be specific to the project and shall include class room type instructions and "hands
on" instructions.
3.03 CONFIGURATION SERVICES
A. The vendor shall supply all necessary configuration services including field controller
configuration, database configuration, data entry, etc.
3.04 INSTALLATION SERVICES
A. The vendor shall provide installation services for the system including validation
services if necessary.
3.05 (OPTIONAL) HARDWARE ENHANCEMENT
A. For a specific fee to be paid at hardware upgrade, the vendor shall be able to provide
hardware upgrade of servers, workstations, and network equipment, or specific
components such as processors and memory DIMMs.
3.06 SOFTWARE ENHANCEMENT & SOFTWARE SUPPORT
A. The vendor shall provide a comprehensive software maintenance enhancement

program for on-going support of the system.
END OF SECTION

25 5000- Page 26 of 26

25 5000 - Intelligent Building Management System (IBMS)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

25 5000 - Intelligent Building Management System (IBMS)

Uploaded by

Copyright:

Available Formats

NISHAN TOWER-COM 019 -LUSAIL MARINA, DOHA, QATAR ELECTRICAL SPECIFICATIONS

INTELLIGENT BUILDING MANAGEMENT SYSTEMS (IBMS)

1.01 SECTION INCLUDES

C. The IBMS shall facilitate intelligent management of all building services.

D. The following system shall be incorporated into the IBMS:

1.03 INTEGRATION FUNCTIONALITY

D. Uninterrupted power supplies (UPS)

MZ Architects INTELLIGENT BUILDING MANAGEMENT SYSTEM

F. Central Battery System

G. The Security Management System

H. Miscellaneous telecommunications systems

I. Elevators and escalators

J. Fire Management System

1.04 SYSTEM ARCHITECTURE

B. Seamless integration is required with guaranteed interoperability for:

MZ Architects INTELLIGENT BUILDING MANAGEMENT SYSTEM

D. The architecture shall support distributed servers in a Distributed Server Architecture

E. The architecture shall provide two levels of processing and control:

G. High availability configurations shall be integrated in the system design in order to

H. Integrated Maintenance Management

I. Scheduled Maintenance Parts Inventory Database

MZ Architects INTELLIGENT BUILDING MANAGEMENT SYSTEM

1.05 CABLE SPECIFICATION

B. In addition, proprietary specification cables most suited to each application as

1.06 PROJECT SPECIFIC CONFIGURATION

A. Project consist of:

C. Distributed System Servers (IBMS Servers)

b. Alarms / Messages: Operators and workstations at any server must be

D. HOT BACKUP SERVER (IBMS Redundant Server)

1.07 VENDOR REQUIREMENTS

A. The vendor shall be a recognized leader in Facilities Integration, Building Automation

MZ Architects INTELLIGENT BUILDING MANAGEMENT SYSTEM

necessary support services including hardware and software support, configuration

1.08 QUALITY ASSURANCE

1.10 Delegated Design Responsibility:

1.11 WARRANTY & MAINTENANCE PERIOD

A. Approved Manufacturers: Subject to compliance with the requirements of the Contract

A. Servers and Peripherals

MZ Architects INTELLIGENT BUILDING MANAGEMENT SYSTEM

D. Color LCD Displays

2.03 SYSTEM SOFTWARE

2.04 APPLICATION SERVER SOFTWARE

MZ Architects INTELLIGENT BUILDING MANAGEMENT SYSTEM

2.05 APPLICATION WORKSTATION SOFTWARE

2.06 OPERATOR INTERFACE

B. Web Browser Operator Interface

C. Operator Interface Connection

D. Operator Interface Characteristics

MZ Architects INTELLIGENT BUILDING MANAGEMENT SYSTEM

2.07 OPERATOR SECURITY AND SIGN-ON

2.08 STANDARD SYSTEM DISPLAYS

A. The following displays shall be included as part of the IBMS system:

5. Life Safety management (Fire Alarm System)

2.09 CUSTOM DISPLAYS

MZ Architects INTELLIGENT BUILDING MANAGEMENT SYSTEM

2.10 ONLINE HELP AND DOCUMENTATION

2.11 MONITORING AND CONTROL

2.12 SYSTEM DATABASE

MZ Architects INTELLIGENT BUILDING MANAGEMENT SYSTEM

J. User Definable Database

2.13 EVENT MANAGEMENT

1. Alarms and Alerts

S. The event manager is supported by a real-time event and maintenance database

2.14 ALARM MANAGEMENT