BMS

Christchurch International Airport Limited Policy & Procedures Manual
CIAL Facilities Services BMS Methodology
BMS METHODOLOGY
1 PURPOSE
This document identifies the methodology used for programming the Christchurch International
Airport Limited (CIAL) BMS.
2 SCOPE
Intended for use by Facilities Services Staff and for use by Consulting Engineers and Contractors to
assist with the design of BMS controlled systems. Included in this document is a detailed
description of how BMS points are designated, and the control philosophy behind this. Also
included in the appendices are examples of actual systems.
3 CONTINUOUS IMPROVEMENT
It is the policy of CIAL Facilities Services to continually improve (for example as needs or
technology changes). This then creates an ongoing need to make alterations to this document. The
reader must ensure that the current version is being used.
To assist CIAL Facilities Services to continually improve, please advise the Manager Airport
Facilities if there is something in this document that is missing or that can be improved upon.
4 COPYRIGHT
Please feel free to copy this document, however before doing so, ensure:
Approval is obtained from the Manager Airport Facilities.
The document is copied in its entirety.
CIAL Facilities Services are acknowledged as the original source.
5 INFORMATION CONTACTS
CIAL Facilities Services staff and the Manager Airport Facilities may be contacted by telephoning
CIAL Facilities Services (ph: 353-7080). The fax number is 353-7090 and the E-mail address is
facilities.services@cial.co.nz. CIAL Facilities Services is located at 818 Wairakei Rd.
6 ASSOCIATED DOCUMENTS
CIAL Facilities Services Procedure - “Requirements for Contractors” document.
CIAL Facilities Services Procedure - “Requirements for Contractors”
CIAL Facilities Services Procedure - “CIAL Asset Numbering Protocol”
CIAL Facilities Services Procedure - “Electrical and Electrical for Mechanical”
CIAL Facilities Services Procedure - “Mechanical Installation”
CIAL Facilities Services Procedure - “Preferred Mechanical and Electrical Materials”
CIAL Facilities Services Procedure - “Split System heat Pump Installation”
Authorised By: Manager Airport Facilities Date Issued: 10 March 2010

Compiled By: HVAC Engineer Index: G205
s:\operations and infrastructure\facilities services\general\standards\bms policy & methodology.doc Page 1 of 44

Appendices - Examples of actual systems
Appendix A - CIAL - IP Address for BMS
Appendix B - Generators Priority Alarm Message Types
Appendix C - CIAL - Apron Expansion Acronyms for Plants Controllers and Devices
Appendix D - B1 Chillers 1 & 2 Condenser Pumps & R4 Cooling Towers CT 1 & 2 Controls
Appendix E - Apogee Graphics
7 CIAL - BUILDING MANAGEMENT SYSTEM (BMS)

7.1 INTRODUCTION
There have been continuous developments over the years to the existing airport terminal, resulting
in a number of control systems being installed. These systems have had numerous extensions,
changes and ongoing alterations occurring, along with changes in technology and manufacturer.
This has left the site, at present, operational but disjointed with respect to the building
management system.
CIAL BMS currently consists of four systems, namely:-
a) Siemens ‘Staefa MS2000’ (DOS based). - This manages systems in the International
Terminal Building, the Antarctic Admin Building, parts of the Domestic Terminal building,
Yard Maintenance Office, Power Centre 5, Western Grass and some other remote parts of
the Terminal.
b) Siemens ‘Staefa MS1800’ (Windows based). – As a backup to the ‘MS2000’ system,

this is used as an alternative for downloading data to the Staefa system.
c) Honeywell ‘XFI’ / ‘EBI’ (Windows based). - This manages systems in the Domestic
Terminal Building, and Antarctic Visitors Centre.
d) Siemens ‘APOGEE’ (Windows based). - This manages systems in the International

Terminal Apron Expansion Building, some parts of the Terminal, and potentially any new
building such as the new Carpark building. Together with the Staefa ‘MS1800’ (Windows
based), it will virtually replace the above Siemens ‘Staefa MS2000’.
The objective is to move towards a system with the capability of an open architecture/protocol that
will provide a fully integrated system with open protocol communications between equipment and
controllers and facilitates flexible use of systems.
This will:-
a) enable the selection, installation and use of products with the best capabilities to be
chosen for the task rather than being “locked” into certain vendor’s proprietary products,
maintenance and processes,
b) enable alternative suppliers of compatible products if the single vendor platform becomes
unsustainable,
c) ideally allow a single front end, capable of interfacing, receiving alarms, controlling and
integrating systems on all the existing and any new control platforms.


For integration of different control systems, the following will be required:-
a) All necessary engineering data from manufacturers is desirable for a successful interface.
b) Training of any new software packages from manufacturers and/or vendors.
c) Manufacturers to provide all necessary engineering software tools and/or workstations

for the open protocol implementation; (such as BACnet) and (LONworks).
d) Vendors with local and experienced qualified support staff 24/7, is desirable.
e) In the unlikely unavailability of local qualified support during emergency, access to next
level of support (such as overseas or equivalent manufacturer support) is desirable.
7.2 SYSTEM DESIGN REQUIREMENTS
It is essential that any investment enhances the benefit of having the entire campus as an
integrated system. TCP/IP is the network solution as this presents an opportunity for closer
integration based on a common building automation standard.
The integrated system will incorporate other specialist 3rd party building systems and will be
applicable to not only the HVAC, but also the fire, security, access control, maintenance, lighting,
power management, electrical systems monitoring etc, providing a seamless control of the building
management. This will require an open relationship between the 3rd parties and the BMS vendor.
The communications platform will be via the existing CIAL site ethernet network, enabling TCP/IP
access and distributed architecture for real-time access, automation and control of devices.
Control systems must have the capability to use Building control industry standard communication
protocols such as BACnet, LONworks, Modbus, etc to enable a truly open system architecture.
7.3 WORKSTATIONS
There shall be two types of workstations; - Operator and Engineering Workstations.
Operator Workstation
a) Will have the facility to access all systems ie: fire alarm (monitoring only), security (with
authority), HVAC, lighting, power management etc.
b) Will be easy to use for non-technical operators; using standard windows type commands
and keystrokes.
c) Will have simple and easy navigation via site plans and simple graphics that tunnel down
to specific areas.
d) Will not require special software or software license keys (dongles). to facilitate access
to graphics, set point and time schedule adjustment and historical trend data.
e) Will be web based enabling all of the above to be accessed via a standard web browser.
f) Will have User Login, providing access that is appropriate for the user type eliminating
tampering and miss-use of the system.


Engineering Workstations
a) Will be centrally located within the BMS/Maintenance control room
b) Will have all the facilities as in Operator Workstation and
a) Will provide full engineering functions as well as a centralised data base back up,
storage and restore facility.
7.4 SITE ARCHITECTURE
The BMS shall have client/server architecture, with capability of an extended system with multiple
servers and stations connected across LANs or WANs.
The internal TCP/IP network will be available and used to link all locations and system types
together around the site.
Control system hardware will require either onboard ethernet connection or be connected by an
ethernet gateway to provide connection into the existing site network at each major plant room
location. Each ethernet connection must be able to 100% support the UDP and TCP/IP protocol
suite.
System Configuration
The BMS shall be configured as a fully distributed intelligent system that includes
Management Level Network (MLN) that supports

o BACnet and OPC over TCP/IP,
o ODBC database access and AdvanceDDE,
o Web access,
o Minimum of 40 simultaneous workstations per BMS server,
o Other building systems of different third-party suppliers with standard open protocol
o Devices and controllers directly utilizing TCP/IP as Automation Level Network (ALN),
or as peer-to-peer Building Level Network (BLN)
o Integration with subsystems including
− HVAC monitoring and control
− Lighting control
− Power Metering and management
− Energy Usage monitoring and management
− Maintenance Management Systems
− Fire monitoring
− Security monitoring
− Access controllers and access card readers
− CCTV systems
− Photo ID integration
− Programmable Logic Controllers (PLC)
− Life safety


− Industrial Control
− Digital video management
− Email, Mobile Phone, paging, and SMS notification
− Other BMS
Building Level Network (BLN) that supports

o Standalone controllers that connects to the MLN via TCP/IP,
o Standalone controllers that connects via RS485 to BMS Server on the MLN,
o Standalone controllers that supports Lonworks, Modbus, BACnet, and other vendor
specific protocols,
o Unlimited Workstations
Floor Level Network (FLN) that supports

o Lonworks, Modbus, BACnet, and other vendor specific protocols,
o Standalone specific controllers such as VAV, FCU, HTP, and other DDC controllers
o Other third-party controllers with standard open protocols,
o PDAs
Response Times
The controls system Specialist Controls Sub Contractor (SCSC) will engineer the control systems to
ensure the following maximum response times between update of data at the operator workstation
Alarm or Critical points – 1 sec.
Digital points – 3 secs.
Non-critical points – 5 secs.
Responsibility of SCSC and CIAL IT Engineer
a) Not withstanding the above, it is the responsibility of the SCSC to ensure that all
response times shall be appropriate for the system being controlled. For example, a ‘DO’
for environmental lighting should operate within 0.5 sec of ‘DI’ status change.
b) If data points take longer than this, the SCSC must prove their system performance at
the location of the network connection (without using the existing network).
c) The SCSC will work closely with the CIAL IT engineers to communicate their network
requirements to ensure maximum performance of their system including response time.
d) If CIAL traffic network is too congested, slowing down the response time, CIAL IT
engineers will work to improve this.
e) Responsibility to manage the network and provide the performance required will be by
CIAL IT engineers, but will require collaboration between both parties, even though
there is a line of demarcation and accountability.
f) It is essential for the SCSC to be competent and conversant with ethernet networks and
IT systems.
Integration with CIAL Maintenance Management System (MMS)


The BMS must be able to integrate with CIAL MMS using standard IT protocols such as ODBC, OPC,
etc., for shared database.
Information from the BMS such as ‘Filter dirty’, ‘Fuel tank low’, ‘Run times of systems’, etc shall be
communicated to the MMS in order that automated work orders can be generated.
Equipment shall be identified in the BMS and MMS in accordance with the CIAL asset register
naming protocol.
The Specialist Controls Sub Contractor will adopt the nomenclature and comply with open
architecture protocols to take maximum advantage of the open system architecture.
7.5 REMOTE ACCESS
The CIAL IT department will manage the existing network, with access given only in accordance
with the CIAL IT protocol.
Remote access will provide all of the functions that are available when onsite, without the need for
special software or dongles.
Remote engineering should also be provided via the network connection, though specific software
and dongles maybe required to provide this level of management.
Generally a facility will be provided for tenancies to access the system with restricted control via
on/off push buttons for after hour’s operation, where appropriate. Certain tenants or CIAL staff,
with higher but restricted access shall be able to use the web browser (using their logins) to access
their zones of interest and even change set points or their own schedule of operations instead of
on/off push buttons.
7.6 ENGINEERING
Internal/technical staff will be trained to manage and modify the site wide building control systems.
Not all of the control systems engineering functions may be available through the standard web
browser, where this is applicable vendor specific engineering tools will be provided.
Where these are required for full management and modification of the system, then these tools will
be made available and included in the contract whenever a new type of control system is
introduced to the site. Technical staff training will be included to enable sufficient use of the new
engineering tools by the internal technical staff.
Engineering tools will be supplied with no ongoing maintenance or license fees.
The engineering tools will provide the ability to easily carry out the following functions from any
network connection, without the requirement to connect to each controller locally):
Create / modify / delete physical and virtual points.
Create / modify / delete system function such as alarms, trends, control loops, time schedules,
optimum start/stop etc.
Create / modify / delete programmable control logic, text or graphical based.


Modify programmable control logic on line without the need to download for the changes to
take effect.
Download controller databases.
Upload controller databases.
View dynamic plots of trend data
Run a full compliment of data and history reports (and save to .csv)
Display a full system profile for adding new devices to the network and also controller
diagnostics
7.7 CONTROLLER HARDWARE
All Controllers will have the capability to communicate via standard protocols such as BACnet,
LONworks, Modbus, etc so that integration can occur at any level within the control architecture.
Primary Network Controllers (Automation Level Network ALN)
These controllers:-
Shall be fully programmable and provide standalone operation locally and incorporate built in
energy management strategies such as;
− Peak demand limiting,
− Start-Stop time optimization,
− Equipment scheduling, optimization and sequencing,
− Temperature compensated duty cycling,
− Economizer control,
− Night setback control,
− Automatic Daylight Savings Time switchover,
− Temporary schedule override,
− Holiday scheduling,
− Calendar-based scheduling, and
− Event scheduling.
Must have removable plugs connections to provide easy controller replacement.
Must have a fast enough input scanning to be able to support momentary push button type
inputs eliminating the need for the operator to hold the button, ie: a field response time of no
greater than 3 seconds.
Shall have significant capacity for expansion, trending, and programming. (Limitations of
memory etc. must be disclosed)
Are to be able to communicate back to the CIAL BMS workstation using BACnet/IP and the
existing CIAL TCP/IP network.
Shall have auto sensing of comms fail, TCP/IP Ethernet ports and be compatible to the BACnet
standard.


Shall have standard PID control function. Controllers with the new “Free Adaptive Control
Technology” function which replace PID control functions will be preferred.
Shall support Lonworks, Modbus, BACnet, and other vendor specific protocols,
Secondary Network Controllers (Floor Level Network FLN)
These are usually application based terminal equipment controllers specially designed to control
Fan Coil Units, VAV systems and Heatpumps.
These controllers:-
Shall have the facility to provide standalone operation locally.
Must have removable plugs connections to provide easy controller replacement.
Shall have ‘Afterhours’ push buttons for operation outside of normal operating hours.
Using approved LONworks technology or other approved ‘Open technology’, shall be able to
communicate with the Primary Network Controller/s.
Shall preferably have true differential pressure monitoring transducers onboard, over the mass
flow type devices and “single point hotwire type airflow pickups”, to provide more accurate
volume measurement, especially if used in VAV systems.
Shall be provided with any software tool necessary for commissioning & engineering.
System Note
To assure CIAL of the long term support and maintenance costs of the BMS system;-
All system controllers shall have a documented history of compatibility by design for a
minimum of 15 years.
Future compatibility shall be supported for no less than 10 years.
Compatibility shall be defined as

a) the ability to upgrade existing field panels to current level of technology, and extend
new field panels on a previously installed network.
b) the ability for any existing field panel microprocessor to be connected and directly
communicate with new field panels without bridges, routers or protocol converters.
7.8 CONTROLLER POWER SUPPLY
All controllers must be powered by ‘Essential’ supply, and backed by suitable UPS for at least 5
minutes, to prevent nuisance alarms back to the BMS.
7.9 ALARM NOTIFICATION
The BMS must be able to provide alarm notification via the network to the following
Email (preferred option)
SMS (via email on CIAL network tokens – A separate modem is not permitted on CIAL
networks because of security issues)
Printers


Fax
Alpha numeric pager (via email on CIAL network tokens – A separate modem is not permitted
on CIAL networks because of security issues)
Alarm must be able to be sent simultaneously to various devices based on time of day, alarm
priority, alarm type etc.
The alarm shall be able to escalate after a user defined delay to notify other users.
In the event of any Primary Network Controller or Secondary Network Controller failure/power
down, this must be reported as an Alarm to the above devices.
7.10 SYSTEM GRAPHICS

The control system supplier will provide site web based graphics for each system, using
standard graphics creation software.
The graphics must be able to be created easily, and will be kept as simple as possible and be
user friendly for use by non-technical staff.
Graphics will be stored on a PC based web server (preferred option) or in controller type web
servers.
Graphics shall incorporate graphical picture control link facility to word documents, control
wiring drawings, as built documents by double clicking on the link.
Animation shall be provided to indicate fans and pumps operating and also to show damper
positions.
A point memo function shall be attached to the alarm for easy operator recognition and for
passing on information between operators and engineers regarding the state of the various
systems. Preferably the point memo will automatically be erased and stored in history after
the alarm point has returned to normal and has been acknowledged.
The graphics creation/editing tools will be made available and supplied as part of the contract
if not already on site, with no ongoing maintenance or license fees.
Technical staff training will be included, enabling sufficient and knowledgeable use of the
graphical tools.
Graphics must be able to provide the following minimum functions:-
a) Importing of standard drawing formats, such as Autocad or MicroStation.
b) Animated graphic symbols to easily indicate plant running status.
c) Auto/manual status of outputs and set points. NB:- These must be clearly differentiated
by colour coded or ‘hand’ icon. ‘Manual’ status shown in text is not acceptable.
d) Easy adjustment of set points and time schedules.
e) Point status
Graphic Refresh. A graphic with 20 dynamic points shall update with current data within 8 sec.
and shall automatically refresh every 15 sec.
Configuration and Tuning Screens. Screens used for configuring, calibrating, or tuning points,
PID loops, and similar control logic shall automatically refresh within 6 sec.


Alarm Response Time. An object that goes into alarm shall be annunciating at the workstation
within 15 sec.
Program Execution Frequency. Custom and standard applications shall be capable of running
as often as once every 5 sec
7.11 DATABASE MANAGEMENT
All new controller and graphic databases will be supplied once the project is complete for inclusion
into their back-up storage facility.
If a modification to an existing control system is required the current database (after a back-up
copy is made), will be provided for modification by the vendor. Once the project is complete the
amended database will be returned. The vendor must take all care to ensure that modification of
the database does not corrupt any part of the other database.
To ensure that multiple data bases of different version and revisions do not exist the BMS
workstation is responsible for all database backups and restores to all ALN controllers from this
common location without the need for separate databases for workstations and controllers.
All Secondary Network Controllers setup parameters and modifications (i.e. PID tuning, setpoints,
parameters etc) shall be updated and held in the controllers and the BMS workstation.
The BMS workstation shall be programmed to automatically back up the entire data base on a
regular time event (adjustable by CIAL staff).
7.12 INTERFACING TO OTHER EQUIPMENT
Any energy meters, generator equipment, PLCs, power meters, lighting control equipment, power
monitoring equipment etc provided by 3rd parties shall be able to communicate with the BMS via
open protocol such as the Modbus RTU protocol, BacNet, etc.
Graphics and schematic drawings etc shall be generated.


8 GENERIC CONTROL PROTOCOL REQUIREMENTS
8.1 The BMS shall be used to directly control building systems (discreet controls shall not be used).
The following schedule shows the minimum functionality, which is expected of the BMS. Note: the schedule does not identify all the details for
controls functionality. The designer shall fully investigate and coordinate BMS controls requirements with CIAL Facilities Services for each
project.
Equipment Functions (Typical) Point Types (Typical) Alarms (with Alarm Messages)
(Typical)
• Start/stop to suit system function • Digital Output • Fan fail

Fans
• Fan Status by differential pressure • Digital Input • Feedback (I/O mismatch)
switch or current transducer
• VSD control • Analog Output
• Fire control (if required) • Digital Input or/and Virtual
• Pressure Control (if Required) • Analog Input
• Duty/standby or Lead/lag control • Virtual
• Run Time total • Virtual
• Start/stop to suit system function • Digital Output • Pump fail
Pumps
• Pump Status by differential pressure • Digital Input • Feedback (I/O mismatch)
switch, current transducer, flow • High Level (if req’d)
switch
• VSD control • Analog Output
• Demand Control (if required) • Analog Input
• High Level Alarm Control (if req’d) • Digital Input
• Pump Motor Overload (if req’d) • Digital Input
• Supply Fan start/stop • Digital Output • Fans fail
Air Handlers • Fans Feedbacks (I/O mismatch)
• Return Fan start/stop • Digital Output


(Typical)
• Smoke Fan start/stop (if required) • Digital Output • Dirty Filter

• Fans Status by differential pressure • Digital Inputs • Smoke alarm.
switches or current transducers
• ‘Negative AHU Pressure’
• Fans VSD control • Analog Outputs
• VSD Faults • Digital Inputs
• Duct Smoke Detector • Digital or Analog Input
• Spring Return Sup.Air Damper • Analog Output / Digital Output
• Spring Return Rtn.Air Damper • Analog Output / Digital Output
• Exhaust Air Damper • Analog Output
• Dampers Position (if Req’d) • Analog Inputs
• Outside Air Quality (Damper Control) • Analog Input
• Outside Air Temperature • Analog Input
• Return Air Quality • Analog Input
• Return Air temperature • Analog Input
• Space Air Quality (Damper Control) • Analog Input
• Supply Air Temperature • Analog Input
• Filter monitoring by differential • Digital or Analog Input
pressure switch or sensor
• Heating valve modulation • Analog Output
• Artesian Cooling valve modulation • Analog Output
• Chill Wtr. Cooling valve modulation • Analog Output
• Humidity modulation if applicable • Analog Output
• Fire and smoke control (from Fire or • Digital Input or/and Virtual
adjacent Fire Zones)
• AfterHrs Control • Digital Input or Virtual
• ‘Suck down’ Control (negative • Analog Input and Virtual

(Typical)
pressure due to faulty dampers)
• FIDs Interface Control • Modbus and Virtual
• Economiser Control (Free Cooling) • Virtual
• Minimum Fresh Air Control • Virtual
• Supply Air Temperature Reset control • Virtual
• Enthalpy Control • Virtual
• High Level Interface to local control • Bacnet, Modbus, or OPC • Flow failure
Chillers panel or/and
• Chiller Failure/fault
• Start/stop or • Digital Outputs
• Water leak in close loop system from
• Arm/Disarm chillers if local control • Digital Outputs water makeup
• Chillers Status • Digital Inputs • High Temperature
• Water temp in/out monitoring • Analog Inputs • Feedback
• Load monitoring from chiller control • Analog Inputs • Wet floor sensor (plantroom only)
panel
• Other Alarms via High level I/F if
• Chiller signal to control condenser flow • Analog Input used.
and clg twr fans
• Chiller faults • Digital Inputs
• Chill Water Flow Switch • Digital Input
• Load Current • Analog Input
• Load Monitoring • Analog Input
• Condensor Pump request (if Req’d) • Digital Input & Output
• Condenser Pump VSD • Analog Output
• Primary W. Pump request (if Req’d) • Digital Input & Output
• Clg. Twr. Fan VSD • Analog Output

(Typical)
• Temperature setpoint reset • Analog Output

• CHW Flow Temp. setpoint Reset • Analog Output
• Water Pressure for Water Leak • Analog Input
Detection in Close Loop system
• Wet Floor Sensor • Digital Input
• Duty and Lead/Lag Control • Virtual
• Demand limiting • Virtual
• Other I/Os if no local panel used • Various Inputs & Outputs
• High Level Interface to local control • Bacnet, Modbus, OPC, or Hard-wiring • Flow failure if applicable
Boilers panel or/and if specialise Controller is used. • Boilers Failure/fault
• Start/stop or • Digital Outputs • High and Low temp
• Arm/Disarm boilers if local control • Digital Outputs • Water leak in close loop system from
water makeup
• Boilers Status • Digital Inputs
• Feedback
• Common and Individual Boiler Flow • Analog Inputs
• Wet floor sensor (plantroom only)
Water temp monitoring
• Common and Individual Boiler Return • Analog Inputs
Water temp monitoring
• Damper modulating for gas boilers • Analog Outputs or Local modulating
control
• Damper monitoring for gas boilers • Analog Inputs
• Boilers faults • Digital Inputs
• Demand limiting • Virtual
• Temperature setpoint reset • Analog Output
• Water Pressure for Water Leak • Analog Input
Detection in Close Loop system
• Wet Floor Sensor • Digital Input

(Typical)
• Diff. Pressure for Bypass valve Control • Analog Input

• Duty and Lead/Lag Control • Virtual
• Local VAV controllers with all • Local specific VAV controllers with all • Out of temperature range
VAV boxes necessary Temperature and Air flow relevant Analog & Digital I/Os for air • Filter blockage if applicable
control by damper modulation with flow rate, air volume dampers
• Feedback
electric reheat or heating coil valve modulation, temperature readings,
modulation and/or recool by chill reheats and recool, incl. of
water valve modulation or dx cooling room/space temperature.
where applicable
• Airflow control by in duct velocity • Analog Output
sensor
• Individual supply Air Temperature • Analog Input
sensor in VAV box where Applicable
• Filter monitoring where applicable • Digital Input
• AHU Supply air duct temperature • Analog Input
• Minimum and Maximum air volume • Virtual
setpoints (litres/sec0
• Air volume monitoring (litres) • Virtual
• Room/Space temperature setpoint • Virtual or via high Level Interface
• Occupied/Unoccupied mode • Virtual
• Heating/Cooling demand • Virtual
• Dampers override mode • Virtual
• Dampers position • Virtual
• Fire Control • Virtual
• Heating and cooling actuators • Analog Outputs to be 0-10V preferably


(Typical)
• Local FCU controllers with all • Local specific FCU controllers with all • Out of temperature range
Fan Coil Units necessary Fan and temperature relevant Analog & Digital I/Os for • Filter blockage
control with electric reheat or heating start/stop, status, air flow rate,
• Feedback
coil valve modulation and chill water temperature readings, modulating
or Artesian cooling valve modulation heating and cooling, incl. of
room/space temperature.
• Digital Output
• Fan assisted where applicable
• Digital Input
• Fan status where applicable
• Analog Input
• Individual Supply Air Temperature
sensor in FCU box for monitoring
• Digital Input
• Filter monitoring
• Virtual or via high Level Interface
• Room/Space temperature setpoint
• Virtual
• Occupied/Unoccupied mode
• Virtual
• Heating/Cooling demand
• Virtual
• Fire Control
• Analog Outputs to be 0-10V preferably
• Heating and cooling actuators
• Virtual
• Run Time total
• Refer separate document on split • High level Modbus, or Bacnet Interface • Out of temperature range
Heatpumps system or Various I/Os to BMS for controls
• Filter blockage
and monitoring
• General fault
• Local Heatpump controllers with all • Local specific Heatpump controllers
necessary Fan, compressors, reversing with all relevant Analog & Digital I/Os • Feedback
valve, fresh air damper for free for start/stop, status, temperature
cooling, and temperature control with readings, staging of compressors, incl.
CO2 control where applicable of room/space temperature.
• Temperature setpt control by BMS via • High level Modbus, or Bacnet Interface
high level interface or via Local BMS specific Heatpump
controller.
• Supply Air Temperature sensor • Analog Input


(Typical)
monitoring
• Return Air Temperature sensor • Analog Input
monitoring
• Room/Space temperature setpoint • Virtual or via high Level Interface
• Occupied/Unoccupied mode • Virtual
• Heating/Cooling demand • Virtual
• Fire Control • Virtual
• Fresh Air CO2 Control • Virtual
• Free Cooling Damper Control • Analog or Digital Output
• Filter monitoring • Digital Input
• Control of condensing water • Various Analog & Digital I/Os • High / low temp for condensing water.
Cooling Towers temperature by bypass modulating
• Low water level
valve, modulating condenser pump
vsd, and cooling tower fan VSD based • High / low ORP
on pipeline temperature sensor supply
to chiller, or signal from Chiller local • High TDS
control panel, incl of • Excessive make up water volume.
• Clg. Twr. Fans Start/Stop • Digital Outputs • Excessive Drainage
• Clg. Twr. Fans Status • Digital Inputs • VSD Fault
• Clg. Twr. Fans VSDs • Analog Outputs • Fan fault
• Clg.Twr. Basin Temperature • Analog Input • Feedback
• Monitor condensing water flow and • Analog Inputs
return temperature.
• Condenser water Flow switch • Digital Input
• Biocide dosing on/off control base on • Digital Outputs
ORP transducer.
• Bio Pump status • Digital Input

(Typical)
• TDS on/off control by solenoid dump • Digital Outputs

valve by conductivity transducer.
• Conductivity monitoring in ppm • Analog Input
• Corrosion inhibitor on/off control • Various Analog & Digital I/Os or
based on recommendation from Water
• Separate Local Controller
treatment Consultant.
• Corrosion Inhibitor Low Level
• Digital Input
• Filter Control including
• Various Analog & Digital I/Os and/or
• Separate Local Controller (eg Amiad)
• Monitoring Make-up water
• Analog Input
• Monitoring Excessive Drainage
• Digital Input and Virtual
• Various Temperature Setpts
• Virtual
• Run Time total
• Virtual
• Pumps Start/stop and staging to suit • Digital Outputs • Pump fail

Artesian Cooling cooling demand
• Feedback
Systems • Pumps status via flow or differential • Digital Inputs
• Flow and return differential water
pressure switches or current
temperature to comply with resource
transducers
consent
• VSD control and/or soft start • Digital and Analog Outputs
• Pump Lock out where applicable
• Water Pressure Monitoring • Analog Input
• System shutdown
• Shutdown system via pressure control • Digital Output
• Low and High Water pressure
• Flow and return water temperature • Analog Inputs
monitoring
• Water Level monitoring • Analog Input
• Low water level • Digital Inputs
• Flow Rate / Volume of Water Flow • Analog Inputs with Local metering

(Typical)
• Duty/standby and/or Lead/lag control • Virtual

• Various Temperature & pressure • Virtual
Setpts
• Cooling Demands • Virtual
• Return Water Pressure at plantrooms • Analog Inputs
• Return water modulating valve control • Analog Outputs
at plantrooms by pressure setpt
• Pumps Start/stop and staging to • Digital Outputs • Pump fail
Potable Water pressure setpt of 560Kpa (adjustable)
• Feedback
Systems • Pumps status via flow or differential • Digital Inputs
• Flow and return differential water
pressure switches or current
temperature to comply with resource
transducers
consent
• VSD control and/or soft start • Digital and Analog Outputs
• VSD faults
• VSD Faults • Digital Inputs
• Pump Lock out
• Flow water pressure monitoring • Analog Input
• Flow Water Pressure Alarm
• Tank Water Pressure / Water level in • Analog Input
• Tank water Pressure Alarm
Tank
• Fire Sprinkler Flow Switch operated
• Compressor Start/Stop • Digital Output
• Excessive pump start
• Compressor Status • Digital Input
• Low water level • Digital Inputs if applicable
• Flow Rate / Volume of Water Flow • Analog Inputs with Local metering
where applicable
• Fire Sprinkler Flow switch • Analog Input
• Pressure Chart Recorder Activation • Digital Output
• Pumps and Chart Recorder Reset • Digital Output
• Fire Sprinkler Control (increase • Virtual
Pressure setpt to 660Kpa)


(Typical)
• Duty/standby or Lead/lag pumps • Virtual

control
• Number of Pump starts • Virtual
• Excessive pump start • Virtual
• Pump Controls and/or • Local PLC Controls and/or • Pump fail
Sewage and Sump
• Pump Start • Digital Output • Pump Overload
Pumps
• Pump Status • Digital Input • High Level
• Pump failure / Overload Monitoring • Digital Input • Feedback where applicable
• High Water level monitoring • Digital and/or Analog Input • Comms fail where applicable
• Comms fail if remote monitoring • Digital Input
• Mains fail status • Digital Input • General fault
UPS
• Battery Status • Digital Input • Mains fail
• General fault • Digital Input
• (Also Refer separate document) • Local Controller with I/Os to BMS or • (Refer separate document)
Standby Generator
• Bacnet, ModBus or similar High Level • Refer Appendix for Alarm Messages
Interface
• Maximum Demand Warning • Digital Input
• Maximum Demand Signal • Digital Input
• Generator Start/Stop • Digital Output
• Generator Status • Digital Input
• Generator Co-Gen Status • Digital Input
• Generator ‘Not-in-Auto’ Status • Digital Input
• Generator Pre-Warning • Digital Input
• Generator Shutdown • Digital Input

(Typical)
• Generator Fuel Solenoid • Digital Input

• Generator Fuel Tank Level or • Analog Input
• Generator Fuel Tank High Level • Digital Input
• Water Pump where applicable • Digital Output
• Generator Rtn. Water Temperature • Analog Input
• Return Water Temperature Bypass • Analog Output
valve Control
• Voltage if applicable • Analog Input
• Power factor if applicable • Analog Input
• Mains Fail • Digital Input
• Lighting Level Sensor • Digital Input
Lighting
• FIDs data from FIDS I/F PC • Modbus or similar data
• Lighting Circuit On/Off to Lighting PLC • Digital Outputs to Lighting PLC via
Modbus
• AfterHrs switch • Digital Input
• Outside light time scheduling on/off • PLC Outputs
based on light sensor, time schedule,
FIDs, and afterhrs switch.
• Departure and Arrivals flight schedule • ‘FTP’ data or ‘SQL’ from FIDs server to • Comms Fail
FIDS Interface monitoring to control plants and lights BMS via Modbus or similar
• FIDs Error
for different zones including
• STA, STD, ETA, ETD, ATA, ATD, Gate
Number,
• Comms failure
• FIDs Error failure


(Typical)
• Monitor amps, volts, power factor, • High Level Bacnet, ModBus or similar • Low voltage
Main switchboards KW, KVA, KVAr via meter with high Interface
(MSB) level interface. and/or
• Mains Fail • Digital Input
• Main Breaker Status • Digital Input
• Voltage • Analog Input
• Current • Analog Input
• Power Factor • Analog Input
• Real Power / Demand (KW) • Analog Input
• Apparent Power (KVA) • Analog Input
• Reactive Power (KVAR) • Analog Input
• Metering • Analog Input (Network)
• Monitor phase failure at point of • Digital Input • Phase failure
Motor control supply to cabinet
cabinets (MCC) • Controlled restart of equipment • Digital Output
following re-establishment of power
supply
• Fire Fan Controls Interface with Fire • Modbus, Digital Inputs, or High Level
Fire Alarm Panel (Fire Zones) Bacnet
• Fire Fans Status to FFCP • Digital Outputs
• Lift Machine Room Temperature • Analog Input • High temperature Alarm
Lift System
• Other Faults, etc • Modbus, Digital Inputs, or High Level
Bacnet
• Other Interface where required • Modbus, Digital Inputs, or High Level
Security System Bacnet


9 ACTION
9.1 WORK ON THE BMS SYSTEM TYPICALLY INVOLVES THE
FOLLOWING:
Specifications of Project
Operations description
Engineering
Drawings including schematics and wiring
I/O Points schedule
Acronyms with reference to the ‘Asset Numbering Protocol’
Plant / Asset acronym labels
Material Schedule followed by the Purchasing Order
Installing and Wiring Controllers and devices
Ethernet connection with IT
Programming (including trending all relevant points)
Graphics and Trending
Commissioning including Urgent Alarm testing to Pagers / Cellphones
Staff training especially on graphics and alarm handling
Fine Tuning to acceptable performance using trends / plotters to prove the result
Hard copy printouts of the I/O points and programs, including Urgent alarm messages
O & M Manual (Electronic and Hard Copy) 1 copy to Drawing Office and 1 to HVAC
Handover / Sign Off
Queries / Defects
Revisit after 1 or 3 months
9.2 I/O POINTS
9.2.1 PURPOSE
This section identifies the layout of AS1000 / APOGEE / Honeywell hardware points in the I/O
spreadsheets and the methodology used for listing and describing typical existing plant items
controlled and/or monitored by the BMS.
9.2.2 ARCHITECTURE / SYSTEM PROFILE / CONFIGURATION
(To be added at in the next draft)
9.2.3 ACRONYMS ACCORDING TO CIAL ASSET NUMBERING PROTOCOL
These acronyms shall have a maximum of 30 characters including spaces. By nature of the
varying plant to be controlled, there are no fixed protocols, but the typical I/O sheets give

s:\operations and infrastructure\facilities services\general\standards\bms policy & methodology.doc Page 2

good working examples to follow. These protocols must be followed closely to ensure there is
continuity and compatibility with existing acronyms. Refer to the appendix for examples.
Each completed I/O sheet must be submitted to the HVAC Controls Engineer for approval prior
to programming.
9.2.4 I/O TYPE
The hardware will be selected from the “Preferred Mechanical & Electrical materials list”; the
only exception is where the hardware has been supplied with a propriety piece of equipment.
9.2.5 ALARM
This lists the “Priority” of the alarm from a predefined list programmed into the Desigo /
APOGEE Insight / Honeywell EBI Work-Station.
9.2.6 ALARM CONDITION, PRIORITY AND DELAY
This briefly defines for which conditions the alarm will be generated.
Change of State alarms
High / Low alarms
Feedback alarms
9.2.7 ALARM DELAY
This is the time in seconds or minutes that the alarm will be delayed in generating if that point
is outside it’s normal programmed parameters. This delay will apply for control and feedback
operation.
9.2.8 ALARMS TO PAGER AND CELLPHONE
Day - BMS Alarm Pager and Duty Electrician Cellphone.
Night - BMS Alarm Pager and Duty 1st On Call Cellphone.
9.2.9 REPORTS
(To be completed at a later date)
9.2.10 ACCESS LEVEL
Assign access levels for different operators to appropriate graphics and I/O points such as
setpt adjustment, etc. documentation.
9.2.11 ETHERNET NETWORK (TCIP CONFIGURATION)
Refer appendix for example of IP address assignment.
9.2.12 GRAPHICS
Graphics shall be kept as simple as possible and user friendly for use by non-technical
operators. Refer appendix for an example of the graphics.


9.2.13 FILING
2 copies of the latest version of the programmer’s sheet are to be supplied to CIAL Facilities
Services for inclusion in documentation.


Appendix A - CIAL – IP Address for BMS
CIAL - IP Address for BMS for Siemens APOGEE and Honeywell EBI
3-May-07 NB:- Cannot accept underscore
Requested Site /
Current IP New VLAN
By For project Name of Device Cabling to BLN Node System Name Node or Host Name of device Patch #
Address Address
Others/CIAL name
Gen-I Reserved Gen-I In-House HSRP 192.168.21.1
Gen-I Reserved Gen-I In-House CoreSA1 192.168.21.2
Gen-I Reserved Gen-I In-House CoreSB1 192.168.21.3
Gen-I Reserved Gen-I In-House 192.168.21.4
Sng BMS - Colour Printer BMS - HP PSC Colour Printer Colour Printer CIAL Network 178 105BHC BMS CLR_PRT MYD7 TB3-21 202.14.167.35 -
SSL(JA)/Sng BMS - Apogee/EBI Upgrade SNG desktop Workstation CIAL Network 105 105BHCSNG_PC AUB43001ZZ TB3-2 DHCP DHCP
SSL(JA)/Sng BMS - Apogee/EBI Upgrade Apogee2 PC Workstation CIAL Network 105 105BHCAPOGEE2_PC SGH421OCWG TB3-5 DHCP or DHCP
202.14.167.68
?
Sng BMS - Apogee Upgrade XLAN MS1800 (on Apogee2 PC) ITB HB01 NCRS 3 Port A CIAL Network 105 XLAN MS1800 XLAN MS1800 NCR3-A 192.168.0.2 -
SSL(JA)/Sng BMS - DESIGO DESIGO PC database server ITB HB01 NCRS 2 Port A DESIGO Network 105 105BHCDESIGO_PC 105BHC DESIGO PC TB3-3 202.14.167.20 -

s:\operations and infrastructure\facilities services\general\standards\bms policy & methodology.doc

Page 26 of 44
Requested Site /
Current IP New VLAN
Address Address
Others/CIAL name
SSL(JA)/Sng BMS - Apogee Upgrade (apogee1) Apogee1 PC database server HB01 HVAC Office Apogee1 LAN 105 105BHCAPOGEE1_PC - TB3-4 202.14.167.190 192.168.21.11
SSL.(JA)/Sng BMS - Apogee Upgrade Staefa NCRS 0 Host ITB HB01 NCRS 0 E-Port NCR 105 105BHCHB01STAEFA_NCR XLAN APOG TB1-9 202.14.167.193 192.168.21.12
Sng BMS - FIDs I/F (2good4you) BMS - FIDs I/F PC ITB HB01 CIAL Eq.Rm. CIAL Network 105 105BHCFIDSIF_PC FIDSLINK TB1-36 202.14.168.6 -
SSL(JA)/Sng BMS - Apron Expansion Apogee E.Microserver 200 ITB Pl.Rm. R4 1052HCPRR4_RBLN01 0/21 1052HCPRR4_LMEC021 Node 21 - PlRm.R4 AEM TF3-12 202.14.167.192 192.168.21.13
SSL(JA)/Sng BMS - AirNZ VIP Apogee E.LMEC ITB Pl.Rm. R4 105GHCITB_BLN 105 1052FCPRR4_ELMEC01 1052FC PRR4 ELMEC01 TF3-13 - 192.168.21.14
SSL(JA)/Sng BMS - Apron Expansion Apogee E.Microserver 200 ITB Pl.Rm. G52 105GHCPRG52_RBLN01 0/31 105GHCPRG52_LMEC031 Node 31 - PlRm. G52 AEM 51-20 202.14.167.191 192.168.21.15
SSL(JA)/Sng BMS - Apron Expansion RS485 - PRG52_MEC031 105GHCPRG52_RBLN01 0/42 105GHCPRG52_MEC042 Node 42 - PlRm. G52 AEM - - -
SSL(JA)/Sng BMS - Apron Expansion RS485 - PRG52_MEC031 105GHCPRG52_RBLN01 0/53 105GHCPRG52_MEC053 Node 53 - PlRm. G52 AEM - - -
SSL.(JA)/Sng BMS - Apogee Smart II Driver Apogee Sm II Driver (AEM 200) ITB HB01 CIAL Eq.Rm. 105BHCHB01_RBLN01 0/1 105BHCHB01_SMD01 Node 1 - Smart 2 Driver AEM TB1-10 202.14.167.167 192.168.21.16
SSL.(JA)/Sng BMS - R3F4&F5 SMVU Upgrade Apogee E.LMEC ITB Pl.Rm. R3 105GHCITB_BLN 105 1052FCPRR3_ELMEC01 1052FC PRR3 ELMEC 01 AC-186 202.14.167.194 192.168.21.17
SSL.(JA)/Sng BMS - R3F4&F5 SMVU Upgrade For BMS Laptop use ITB Pl.Rm. R3 - - - - AC-187 DHCP 192.168.21.18
SSL(JA)/Sng BMS - HBS For BMS Laptop use ITB HG04 - - - - TG4-39 DHCP 192.168.21.19
SSL(JA)/Sng BMS - HBS Apogee E.LMEC ITB HG04 105GHCITB_BLN 105 105GHCHG04HBS_ELMEC01 105GHC HG04HBS ELMEC 01 TG4-40 202.14.167.189 192.168.21.20
SSL(JA)/Sng BMS - Emirates Ramp Office Apogee E.MEC ITB HG53 ERO 105GHCITB_BLN 105 105GHCHG53ERO_EMEC01 105GHC HG53 ERO EMEC 01 TG52-20 202.14.167.196 192.168.21.21
SSL(Ja)/Sng BMS - ModBus Driver Apogee MODbus Driver ITB HB01 CIAL Eq.Rm. 105GHCITB_BLN 105 105BHCHB01_EMBDC01 105BHC HB01 MBD 01 TB1-26 202.14.167.201 192.168.21.22
SSL(Ja)/Sng BMS - Spare Spare for future ITB HB01 CIAL Eq.Rm. 105GHCITB_BLN 105 Spare Spare TB1-27 202.14.167.207 192.168.21.23
SSL(Ja)/Sng BMS - Lighting Apogee MODbus Driver 105BHCHB01_EMBDC01 105GHCITB_BLN 105 105BHCHB01_EMBDC01 FLN 1 - 105B Moeller PLC - - -
SSL(Ja)/Sng BMS - Pwr Metering Apogee MODbus Driver 105BHCHB01_EMBDC01 105GHCITB_BLN 105 105BHCHB01_EMBDC01 FLN 2 - 100 Power Meters LAN - - -
SSL(Ja)/Sng BMS - Fire Alarm Upgrade Apogee MODbus Driver 105BHCHB01_EMBDC01 105GHCITB_BLN 105 105BHCHB01_EMBDC01 FLN 3 - 105B FireFinder FFCP - - -


Page 27 of 44
Requested Site /
Current IP New VLAN
Address Address
Others/CIAL name
SSL(AM)/Sng BMS - TDP Car Park Building Generator Transfer Sw ModBus CarPark Bldg Lvl Gnd. 105GHCITB_BLN 105 105BHCHB01_EMBDC01 FLN 6 - 179 Generator8 179GT-04 202.14.167.157 192.168.21.24
SSL(Ja)/Sng BMS - ModBus Driver Apogee MODbus Driver - - - - FLN 253 - 105B Diagnostics LAN - - -
SSL(JA)/Sng BMS - Fire Alarm Upgrade PRR1 EPXC 01 ITB Pl.Rm. R1 105GHCITB_BLN 105 1052FCPRR1_EPXC01 1052FC PRR1 EPXC 01 TF5-26 202.14.167.174 192.168.21.25
SSL(JA)/Sng BMS - Fire Alarm Upgrade For Laptop use ITB Pl.Rm. R1 TF5-27 DHCP 192.168.21.26
SSL(JA)/Sng BMS - Fire Alarm Upgrade PRR2 EPXC 01 ITB Pl.Rm. R2 105GHCITB_BLN 105 1052FCPRR2_EMEC01 1052FC PRR2 EMEC 01 TF5-28 202.14.167.176 192.168.21.27
SSL(JA)/Sng BMS - Fire Alarm Upgrade For Laptop use ITB Pl.Rm. R2 - - - - TF5-29 DHCP 192.168.21.28
SSL(JA)/Sng BMS - Fire Alarm Upgrade Spare ITB Pl.Rm. R3 105GHCITB_BLN 105 Spare Spare AC-257 202.14.167.177 192.168.21.29
SSL(JA)/Sng BMS - Fire Alarm Upgrade For Laptop use ITB Pl.Rm. R3 - - - - AC-258 DHCP 192.168.21.30
SSL(JA)/Sng BMS - Fire Alarm Upgrade PRR4 EMEC 02 ITB Pl.Rm. R4 105GHCITB_BLN 105 1052FCPRR4_EMEC02 1052FC PRR4 EMEC 02 TS3-1 202.14.167.178 192.168.21.31
SSL(JA)/Sng BMS - Fire Alarm Upgrade For Laptop use ITB Pl.Rm. R4 - - - - TS3-2 DHCP 192.168.21.32
SSL(JA)/Sng BMS - Fire Alarm Upgrade PRG52 EPXC 01 ITB Pl.Rm. G52 105GHCITB_BLN 105 105GFCPRG52_EPXC01 105GFC PRG52 EPXC 01 TG51-115 202.14.167.179 192.168.21.33
SSL(JA)/Sng BMS - Fire Alarm Upgrade For Laptop use ITB Pl.Rm. G52 - - - - TG51-116 DHCP 192.168.21.34
SSL(JA)/Sng BMS - T1 AirNZ Chk/In FCUs Apogee E.MEC T1 Sw.Bd.Rm G4 105GHC T1_BLN 103 103GHCSBRG4_EMEC01 103GHC SBRG4 EMEC 01 B-69 202.14.167.195 192.168.21.35
SSL(JA)/Sng BMS - T1 AirNZ Chk/In FCUs For BMS Laptop use - - - - - B-70 DHCP 192.168.21.36
SSL(AM)/Sng BMS - TDP Car Park Building Apogee E.MEC CarPark Bldg Lvl Gnd. 179GHC CPB_BLN 179 179GHCDB0101E_EMEC01 179GHC DB0101E EMEC 01 179GT-08 202.14.167.148 192.168.21.37
SSL(AM)/Sng BMS - TDP Car Park Building DB11E EPXC 01 CarPark Bldg Lvl 1 179GHC CPB_BLN 179 1791HCDB11E_EPXC01 1791HC DB11E EPXC 01 179GT-12 202.14.167.149 192.168.21.38
SSL(AM)/Sng BMS - TDP Car Park Building MCP01 EPXC 01 CarPark Bldg Lvl 4 179GHC CPB_BLN 179 1794HCMCP01_EPXC01 1794HC MCP01 EPXC 01 1794T-15 202.14.167.154 192.168.21.41


Page 28 of 44
Requested Site /
Current IP New VLAN
Address Address
Others/CIAL name
SSL(AM)/Sng BMS - TDP Car Park Building MHI BACnet Gateway Virtual N/A - for Soft Controller 179GHC CPB_BLN 179 1794HC MHI BGW VIRTUAL 179:APOGEE1/5420 SoftC - - -
SSL(AM)/Sng BMS - TDP Car Park Building MHI PAC BACnet Gateway CarPark Bldg Lvl 4 1794HC CPB_MHI_BGW 179 BACDev_1000 NODE 1 - MHI_PAC_GATEWAY 1794T-11 202.14.167.158 192.168.21.45
BMS - Honeywell EBI
Requested By Site New VLAN

For project Name of Device Cabling to BLN System Name Node or Host Name of device Patch # IP Address
Others / CIAL name Address
HWL BMS - EBI Upgrade (imoncall) EBI PC database server EBI Master Server EBI Network 105 105BHCEBI_PC 105BHC EBI PC TB3-6 192.168.20.200 192.168.21.200
HWL BMS - EBI Upgrade BMS EBI Alarm Printer ITB Basement BMS Office CIAL Network 105 105BHC HB01 BMS EBI_PRT 105BHC HB01 BMS EBI PRT Serial to EBI server -
HWL BMS - EBI Upgrade BMS EBI AFS Alarm Printer AFS Tower CIAL Network 178 1782HC AFS BMS EBI_PRT 1782HC AFS BMS EBI PRT AFS 192.168.20.229 192.168.21.201
HWL BMS - EBI Domestic T1 Upgrade Dom.T1 BNA-2DN BNPS ITB Basement BMS Office 103GHC T1_BNA BNPS 103 103GHCT1_BNABNPS 103GHC T1 BNA BNPS TB3-22 192.168.20.201 192.168.21.202
HWL BMS - EBI Domestic T1 Upgrade BNA-A_003 (Ch 1) Dom.T1 BNA-2DN BNPS RTU 21-28 103 DELTANET Ch 1 BNA-A_003 - - - -
HWL BMS - EBI Domestic T1 Upgrade BNA-A_005 (Ch 2) Dom.T1 BNA-2DN BNPS RTU 11-14, 16-18 103 DELTANET Ch 2 BNA-A_005 - - - -
HWL BMS - EBI AVC Upgrade A.V.C. BNA-2DN BNPS 1st Flr MCC Room 1271HC AVC_BNA BNPS 127 1271HC AVC_BNABNPS 1271HC AVC BNA BNPS Hub 192.168.20.202 192.168.21.203


Page 29 of 44
Requested By Site New VLAN

For project Name of Device Cabling to BLN System Name Node or Host Name of device Patch # IP Address
Others / CIAL name Address
HWL BMS - EBI AVC Upgrade BNA-B_004 (Ch 1) A.V.C. BNA-2DN BNPS RTU 41-45 103 DELTANET Ch 1 BNA-B_004 - - - -
HWL BMS - Penguin Colony Antarctic V.Centre BNA-1CS Penguin Gnd Equip.Rm 1271HC AVC_BNA 1 127 127GHC AVC PENG_BNA1 127GHC AVC PENG BNA 1 A-21 192.168.20.203 192.168.21.204
BMS APOGEE1 Server details
IP Address 202.14.167.190
Subnet mask 255.255.255.0
Gateway 202.14.167.2
DNS
Preferred DNS 202.14.167.204
Alternate DNS 202.14.167.173
DNS Suffix cial.co.nz
BMS EBI Server details
IP Address 192.168.20.200
Subnet mask 255.255.255.0
Gateway 192.168.20.1
DNS
Preferred DNS
Alternate DNS
DNS Suffix cial.co.nz


Page 30 of 44
Appendix B – Generators Priority Alarm Message Types

13-Jun-06
Generators Priority 1 Alarm Message Types
Generator X Condition from local controller Generator X
OFF (Not
General Not-in-Auto CoGen OFF CoGen ON Pre-Warning Shutdown ON (Running)
Running)
Generator Standby (Auto Normal Alm Message E Normal N/A Alm Message G Alm Message H N/A Normal
Mode)
MSB Y Mains NonEss Alm Message A Alm Message E Normal N/A Alm Message G Alm Message H Normal Alm Message J
Fail
Max Demand Warning - Alm Message B Alm Message E Alm Message F Normal Alm Message G Alm Message H Normal Alm Message K
Start Generators
Max Demand Control Alm Message C Alm Message E Alm Message F Normal Alm Message G Alm Message H Normal Alm Message K
Period - Start Generators
B1 Keyswitch - Start Alm Message D Alm Message E Alm Message F Normal Alm Message G Alm Message H Normal Alm Message K
Generators

Compiled By: HVAC Engineer Index: Index: G205
Page 31 of 44
Christchurch International Airport Limited
CIAL Facilities Services
Local CoGen Test N/A Alm Message E N/A Priority 2 Alm - Alm Message G Alm Message H Priority 2 Alm - N/A
Message L Message M
Manual Generator Run N/A Alm Message E N/A N/A Alm Message G Alm Message H Priority 2 Alm - N/A
Message M
Alarm Message Type NB:
A MSB Y Mains NonEss Fail N/A - means it will never happen
B Max Demand Warning Started Normal - means No alm message or return to Normal
C Max Demand Control Period Started
D Generators Keyswitch Enabled Useful I/O Point Description
E Generator X Not-in-Auto Mode 1/Rsudi 160 Max Demand Warning Signal
F Generator X Started - Co-Gen Fail 1/Rsudi 161 Max Demand Control Period Signal
G Generator X Warning 1/Rsdi 154 B1 keyswitch - Start all generators
H Generator X Shutdown
I - NB:- Generators start on either of the following conditions:-
J MSB Y Mains NonEss Fail - Generator X Fail To Start 1) During a Max Demand Warning OR Control Period signal, AND

Page 32 of 44
K Generator X Fail To Start between the adjustable time schedule (default 7:30 - 20:30 hrs)
Priority 2 Alm Message L Generator X on Test - Co-Gen ON 2) When B1 "All generators Start" Keyswitch operate
Priority 2 Alm Message M Generator X - Manual ON

Page 33 of 44
Appendix C
CIAL - Apron Expansion Acronyms for Plants Controllers and Devices
NB:- HVAC zones HF08 and HF09 used instead of H108 and H109; Rest of zones follows new Acronym structure
Plants / Controllers / Devices First Acronyms Proposal Agreed Acronyms (30 Aug 2004) Plant and asset label
***AHU A*** 1052HM_AHUR04HF08 R04-HF08
AHU A Supply Air Fan 1052HMAHUR04HF08_SAF 1052HMAHUR04HF08_SAF R04-HF08-SAF
AHU A Space Temperature 1 1051HCAHUR4F8_RMT1 1051HMAHUR04HF08_RMT1 HF08-RMT1
AHU A Space Humidity 1051HCAHUR4F8_RMH 1051HMAHUR04HF08_RMH HF08-RMH
AHU A Diffuser 1 position 1051HCAHUR4F8_DIF1 1051HMAHUR04HF08_DIF1 HF08-DIF1
AHU A Return Air Damper 1051HCAHUR4F8_RAD 1051HMAHUR04HF08_RAD HF08-RAD
**VAV** 1051HMAHUR04HF08_VAV01 HF08-VAV01
VAV A1 Damper Position 1051HCAHUR4F8VAV01_DMP 1051HMAHUR04HF08VAV01_DMP HF08-VAV01-DMP
**FCU** 1051HMHF08_FCU01 HF08-FCU01

Page 34 of 44
FCU A1 Space Temperature 105GHCF8FCU01_RMT 1051HMHF08FCU01_RMT HF08-FCU01-RMT
FCU A1 Fan 105GHCF8FCU01_SAF 1051HMHF08FCU01_SAF HF08-FCU01-SAF
FCU A Bypass Valve Cooling 105GHCF8FCUBP_CWV 1051HMHF08FCUBP_CWV ? HF08-FCUBP-CWV
FCU A Bypass Valve Heating 105GHCF8FCUBP_HWV 1051HMHF08FCUBP_HWV ? HF08-FCUBP-HWV
FCU A Diff Pressure Cooling 105GHCF8FCUBP_CDP 1051HMHF08FCUBP_CDP ? HF08-FCUBP-CDP
FCU A Diff Pressure Heating 105GHCF8FCUBP_HDP 1051HMHF08FCUBP_HDP ? HF08-FCUBP-HDP
***AHU B*** 1052HM_AHUR04HF09 R04-HF09
AHU B Supply Air Fan 1052HMAHUR04HF09_SAF R04-HF09-SAF
AHU B Space Temperature 1 1051HCAHUR4F9_RMT1 1051HMAHUR04HF09_RMT1 HF09-RMT1
AHU B Space Humidity 1051HCAHUR4F9_RMH 1051HMAHUR04HF09_RMH HF09-RMH
AHU B Return Air Damper 1051HCAHUR4F9_RAD 1051HMAHUR04HF09_RAD HF09-RAD

Page 35 of 44
***AHU C*** 105GHM_AHUG52H151 G52-H151
AHU C Supply Air Fan 105GHMAHUG52H151_SAF G52-H151-SAF
AHU C Space Temperature 1 105GHCAHUG52F9_RMT1 1051HMAHUG52H151_RMT1 H151-RMT1
AHU C Space Humidity 1 105GHCAHUG52F9_RMH1 1051HMAHUG52H151_RMH1 H151-RMH1
AHU C Diffuser 1 position 105GHCAHUG52F9_DIF1 1051HMAHUG52H151_DIF1 H151-DIF1
AHU C Return Air Damper 105GHCAHUG52F9_RAD 105GHMAHUG52H151_RAD H151-RAD
**FCU** 105GHMHG51_FCU01 HG51-FCU01
FCU C1 Space Temperature 105GHCG51FCU01_RMT 105GHMHG51FCU01_RMT HG51-FCU01-RMT

Page 36 of 44
FCU C1 Fan 105GHCG51FCU01_SAF 105GHMHG51FCU01_SAF HG51-FCU01-SAF
FCU C Cooling Bypass W/Valve 1051HCAHUR4FCUBP_CWV 1051HMHG51FCU_CBPWV HG51-FCU-CBP-WV
FCU C Heating Bypass W/Valve 1051HCAHUR4FCUBP_HWV 1051HMHG51FCU_HBPWV HG51-FCU-HBP-WV
FCU C Clg. Bypass Diff Pressure 1051HCAHUR4FCUBP_CDP 1051HMHG51FCU_CBPDP HG51-FCU-CBP-DP
FCU C Htg. Bypass Diff Pressure 1051HCAHUR4FCUBP_HDP 1051HMHG51FCU_HBPDP HG51-FCU-HBP-DP
***AHU D*** 105GHM_AHUG52HG52 G52-HG52
AHU D Supply Air Fan 105GHMAHUG52HG52_SAF G52-HG52-SAF
AHU D Space Temperature 1 105GHCAHUG52G52_RMT1 105GHMAHUG52HG52_RMT1 HG52-RMT1
AHU D Space Humidity 1 105GHCAHUG52G52_RMH1 105GHMAHUG52HG52_RMH1 HG52-RMH1
AHU D Diffuser 1 position 105GHCAHUG52G52_DIF1 105GHMAHUG52HG52_DIF1 HG52-DIF1
AHU D Return Air Damper 105GHCAHUG52G52_RAD 105GHMAHUG52HG52_RAD HG52-RAD

Page 37 of 44
***DAIKEN UNITS***
Daiken A/C Enable 2&4 1051HCF52_HTP02,4 1051HMH152_HTP02,4 H152-HTP02,4
Daiken A/C Setpoint 2&4 1051HCF52_HTP02,4_RMTSP 1051HMH152HTP02,4_RMTSP N/A

Page 38 of 44
Daiken A/C Fan Status 2&4 1051HCF52_HTP02,4_S 1051HMH152HTP02,4_FS H152-HTP02,4
Daiken A/C Space Temperature 2&4 1051HCF52_HTP02,4_RMT 1051HMH152HTP02,4_RMT H152-HTP02,4-RMT
***SPILL FANS***
SPF-C1 105RHCF51_EAF01 105RHMH151_EAF01 H151-EAF01

Page 39 of 44
***SMOKE EXTRACT FANS***
SF1 105RHMFF02HF08_SEF01 FF02-HF08-SEF01
SF2 105RHMFF02HF08_SEF02 FF02-HF08-SEF02
SF3 105RHMFF02H151_SEF03 FF02-H151-SEF03
Queries
Where are the bypass valves?
Where is FCU C1 located?

Page 40 of 44
Appendix D
B1 Chillers 1 & 2
Condenser Pumps
& R4 Cooling Towers
CT 1 & 2
Controls
“ B1CH* ”
( NCRS 1 / Trk 1 / RS0D )
TABLE OF CONTENTS Page
Description – ................................................................................................ 42
Rev. Description Drw. Chk. Auth Date
CIAL
B1 Chill 1&2
A d C dP
R4 Cl T CT1 & 2
E i i C t l
D t D tN
ME / HVAC /
1/1/D/B1CH
B1CHCNCT.DOC Pg 41 of 2

Description:
NCRS 1 / Trk 1 / RS0D
B1 Chillers 1 & 2 Condenser Pumps and R4 Cooling Towers CT1 & 2 Controls
The BMS receives a DI signal from each chiller requesting the respective condenser pump to
start.
The BMS also receives a 0 – 10 V signal from each chiller system. This signal indirectly
represents the cooling demand from the condenser water for that chiller.
These signals are sent from the B1 Chillers’ COP panel.
Control Strategy.
The 0 – 10 V signal from the COP panel controls the condenser pump VSD from 5 – 50 Htz.
At the same time, the 0 – 10 V signal varies the condenser return water temperature setpt
from 20 to 29 Deg.C.
The two cooling tower fan VSDs are then subsequently PI controlled by the variable Cond.
RWT setpt.
(Eg. PI Output 40 –70 % = Fan A VSD 10 – 64 Htz. and
PI Output 70 – 100 % = Fan B VSD 10 – 64 Htz. )
The controls are identical for Chillers 1 & 2 condenser system and respective cooling towers
CT1 and CT2.

Appendix E



BMS

Uploaded by

Document Information

Original Description:

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

BMS

Uploaded by

Copyright:

Available Formats

Christchurch International Airport Limited Policy & Procedures Manual

CIAL Facilities Services BMS Methodology

 Approval is obtained from the Manager Airport Facilities.

 The document is copied in its entirety.

 CIAL Facilities Services are acknowledged as the original source.

 CIAL Facilities Services Procedure - “Requirements for Contractors”

 CIAL Facilities Services Procedure - “CIAL Asset Numbering Protocol”

 CIAL Facilities Services Procedure - “Electrical and Electrical for Mechanical”

 CIAL Facilities Services Procedure - “Mechanical Installation”

 CIAL Facilities Services Procedure - “Preferred Mechanical and Electrical Materials”

 CIAL Facilities Services Procedure - “Split System heat Pump Installation”

Authorised By: Manager Airport Facilities Date Issued: 10 March 2010

s:\operations and infrastructure\facilities services\general\standards\bms policy & methodology.doc Page 1 of 44

 Appendices - Examples of actual systems

Appendix A - CIAL - IP Address for BMS

Appendix B - Generators Priority Alarm Message Types

Appendix E - Apogee Graphics

7 CIAL - BUILDING MANAGEMENT SYSTEM (BMS)

CIAL BMS currently consists of four systems, namely:-

b) Siemens ‘Staefa MS1800’ (Windows based). – As a backup to the ‘MS2000’ system,

d) Siemens ‘APOGEE’ (Windows based). - This manages systems in the International

Authorised By: Manager Airport Facilities Date Issued: 10 March 2010

s:\operations and infrastructure\facilities services\general\standards\bms policy & methodology.doc Page 2 of 44

For integration of different control systems, the following will be required:-

b) Training of any new software packages from manufacturers and/or vendors.

c) Manufacturers to provide all necessary engineering software tools and/or workstations

7.2 SYSTEM DESIGN REQUIREMENTS

There shall be two types of workstations; - Operator and Engineering Workstations.

Authorised By: Manager Airport Facilities Date Issued: 10 March 2010

s:\operations and infrastructure\facilities services\general\standards\bms policy & methodology.doc Page 3 of 44

a) Will be centrally located within the BMS/Maintenance control room

b) Will have all the facilities as in Operator Workstation and

7.4 SITE ARCHITECTURE

 Management Level Network (MLN) that supports

− HVAC monitoring and control

− Power Metering and management

− Energy Usage monitoring and management

− Maintenance Management Systems

− Access controllers and access card readers

− Programmable Logic Controllers (PLC)

Authorised By: Manager Airport Facilities Date Issued: 10 March 2010

s:\operations and infrastructure\facilities services\general\standards\bms policy & methodology.doc Page 4 of 44

− Digital video management

− Email, Mobile Phone, paging, and SMS notification

 Building Level Network (BLN) that supports

 Floor Level Network (FLN) that supports

 Alarm or Critical points – 1 sec.

 Digital points – 3 secs.

 Non-critical points – 5 secs.

Responsibility of SCSC and CIAL IT Engineer

Integration with CIAL Maintenance Management System (MMS)

Authorised By: Manager Airport Facilities Date Issued: 10 March 2010

s:\operations and infrastructure\facilities services\general\standards\bms policy & methodology.doc Page 5 of 44

7.5 REMOTE ACCESS

Engineering tools will be supplied with no ongoing maintenance or license fees.

 Create / modify / delete physical and virtual points.

 Create / modify / delete programmable control logic, text or graphical based.

Authorised By: Manager Airport Facilities Date Issued: 10 March 2010

s:\operations and infrastructure\facilities services\general\standards\bms policy & methodology.doc Page 6 of 44

 Download controller databases.

 Upload controller databases.

 View dynamic plots of trend data

7.7 CONTROLLER HARDWARE

Approval is obtained from the Manager Airport Facilities.

The document is copied in its entirety.

CIAL Facilities Services are acknowledged as the original source.

CIAL Facilities Services Procedure - “Requirements for Contractors”

CIAL Facilities Services Procedure - “CIAL Asset Numbering Protocol”

CIAL Facilities Services Procedure - “Electrical and Electrical for Mechanical”

CIAL Facilities Services Procedure - “Mechanical Installation”

CIAL Facilities Services Procedure - “Preferred Mechanical and Electrical Materials”

CIAL Facilities Services Procedure - “Split System heat Pump Installation”

Appendices - Examples of actual systems

Management Level Network (MLN) that supports

Building Level Network (BLN) that supports

Floor Level Network (FLN) that supports

Alarm or Critical points – 1 sec.

Digital points – 3 secs.

Non-critical points – 5 secs.

Create / modify / delete physical and virtual points.

Create / modify / delete programmable control logic, text or graphical based.

Download controller databases.

Upload controller databases.

View dynamic plots of trend data

Must have removable plugs connections to provide easy controller replacement.

Shall have the facility to provide standalone operation locally.

Must have removable plugs connections to provide easy controller replacement.

Future compatibility shall be supported for no less than 10 years.

Compatibility shall be defined as

Email (preferred option)

Graphics must be able to provide the following minimum functions:-