SECTION 15970 Building Management System (BMS) Part 1 General
SECTION 15970 Building Management System (BMS) Part 1 General
SECTION 15970 Building Management System (BMS) Part 1 General
PART 1 GENERAL
1.04. ABBREVIATIONS
1.05 DEFINITIONS
C. BACnet: The Building Automation and Control Network open protocol communication
standard developed by ASHRAE (ASHRAE SSPC/135) and which is now an ISO and
ANSI standard., The BACNet components shall be fully compliant with British
standards DD ENV 1805-1: 1998 (Data communication for HV AC Application
Management Net. Building automation and control networking), DD ENV 13321-
1:1999 (Data communication for HV AC application automation net. BACNet,
Profibus, World FIP), ASHRAE BACNet standard SSPC/135 and all other applicable
codes.
D. BACnet Object: A physical or virtual point with a set of associated properties such as a
temperature sensor that has properties including, name, current value, maximum and
minimum values, high and low alarm levels, etc.
H. Binary: A two-state system where a high signal level represents an "ON" condition and
an "OFF" condition is represented by a low signal level.
I. BMS: This shall mean the complete Building Management System including the
components at the Field, Automation and Management Levels.
J. Component: Any individual element of the BMS furnished under this contract
including hardware, software and materials.
K. Control Wiring: This includes conduit, wire, and wiring devices to install complete HV
AC control systems, including motor control circuits, interlocks, sensors, PE and EP
switches, and like devices. This also includes all wiring from node to node, and nodes
to all sensors and points defined in the I/O summary shown on drawings or specified
herein, and required to execute the sequence of operation. Does not include line voltage
power wiring.
O. Gateway: A device that contains an input/output (I/O) software driver to translate input
data from one format to output data in a second format.
T. LonMarkedTM : Device has been certified for compliance with LonMark standards by
the LonMark association.
AA. Peripheral I/O: Input/Output (I/O) equipment used to communicate to and from the
computer and make hard copies of system outputs and magnetic files. Peripherals
include VDU, printers, hard drives, disk drives, and modems, etc.
BB. Portable Operator Tenninal (POT): Pennits remote operator interface to facilitate
network management, node commissioning, diagnostics, and general operator interface
with the BMS. This is a Thin Client PC that shall be able to perfoml any function that
can be undertaken from any other Thin Client PC on the system.
CC. Programmable Device: A device that does not have a pre-established built in
application. An application creation software tool is required for an application to be
created and downloaded to the device.
DD. Router: A device that routes messages destined for a node on another segment sub-net
or domain of the control network. The device controls message traffic based on node
address and priority. Routers shall also serve as communication links between power
line, twisted pair, fibre, coax, and RF media.
EE. Standard Network Variable Type (SNVI'): LonWorks controllers use SNVTsto define
data objects. Each SNVT is identified by a code number that the receiving controller
can use to determine how to interpret the information presented.
FF. Standing Standard Project Committee (SSPC): ASHRAE terminology for a technical
committee that oversees the maintenance of a standard.
GG. Software: Generic term used for those components of the computer systems that are
intangible rather than physical. The term "software" is used to refer to the programs
executed by the computer systems as distinct from the physical hardware of the
computer systems and encompasses any programs such as operating systems,
applications programs, operating sequences and databases. The tenn "software" shall be
interpreted to include firmware if, in the context in which it is used, the term "software"
does not exclude the use of read-only memory and the use of firmware meets all of the
applicable criteria detailed in these specifications.
HH. Unitary Controller: A controller generally designed for a specific application and for a
single piece of equipment. Examples are controllers for V A V and FCU terminal units.
These controllers shall be freely programmable.
II. XIF: "External Interface File" contains the contents of the manufacturer's product
documentation.
1. When they are in upper case, when they are in lower case and when they are
capitalized.
2. In the singular and in the plural.
3. and all grammatical tenses.
A. The following is a description of the overall BMS philosophy that shall be applicable to all BMS.
It is provided for the purpose of placing the work of the PROJECT BMS contract, as identified in
Part 1.07 below, in context with the total work involved in the ELECTRICAL SYSTEM BOTH
POWER and Low Voltage (L.V.) Building Systems.
B. The BMS to serve the monitoring and control requirements at PROJECT shall be provided under
this contract.
C. The required data from the electrical BMS shall be transferred via a gateway as BACnet objects .
D. Refer to schematic diagrams that illustrate the relationship between the various components. This
schematic is not intended to indicate the number of components and neither is it intended to be
the only acceptable configuration. It is provided to illustrate the relationship between the various
components. Different BMS subcontractors may have a slightly different topology that generally
will be acceptable provided that it meets the intent of the detailed specifications.
E. Management Level:
1. It shall be the responsibility of each L V building system installer, including the
Building BMS sub-contractor, to ensure that all the system data is available at the
Management Level Network in the form of BACnet objects. Each L V building
system installer shall provide comprehensive and complete documentation
regarding the BACnet object ID, component IP addresses, databases and other
pertinent information. The intent is that any third party system provider shall be
able to read this data from the network and shall be able to write data in BACnet
format to the third party system.
2. 2 No. Data Servers shall be provided under the PROJECT BMS sub-contract.
The Data Servers shall be installed at the control room. The Data Servers shall be
configured as hot stand-by, fault tolerant servers with redundant database
architecture. The PROJECT BMS sub-contractor shall provide all software for
these servers. Databases shall be SQL compliant and shall be standard.
Proprietary databases shall not be acceptable. The data server software shall be
proven for use in a multi-vendor environment and shall be shown by the
PROJECT BMS sub-contractor to be acceptable to all recognised BMS
manufacturers. The data server operating system shall be Microsoft Windows
2003 Enterprise edition and the web browser shall be the latest version of Internet
Explorer or Netscape Navigator.
3. The routers and gateways that connect the L.V. into the Management Level
Network shall be based on the BACnet/IP requirements of the Management Level
Network.
4. The Portable Operator Terminals (POT) shall also be Thin Clients and shall
interface with the networks at the communications controllers, distributed control
panels and at data ports provided in any mechanical or electrical room where
there is no DDC controller.
5. The Communications Controls Panels (CCP) shall be part of the Management
Level Network, except as noted below. They shall be software programmable
gateways that shall fulfil one or both of the following roles:
F. Automation Level:
1. The automation level shall, primarily, include the DDC controllers that interface
with the field sensors and final control elements. It is anticipated that there will
be 2 types of DDC controller within the BMS architecture:
and not at the Management Level. The gateway shall reside on the same network
as the associated DDC controllers.
5. All Automation Level components shall be on UPS except the unitary
controllers.
6. The BMS Automation Level Networks shall be BACnet or LonWorks. No other
protocols shall be used at the BMS Automation Level.
1. The Field Level shall include the instrumentation interfaced to the Automation
Level DDC controllers such as the temperature, humidity, level, pressure sensors
and switches. It shall also include the :final control elements such as the valve
and damper actuators and the control relays. The control valves associated with
the air systems shall be provided under the BMS sub-contract but the dampers
and large chilled 'water system I valves shall be under the mechanical contract..
All field level cables shall, be in containment and shall be screened and LSF
rated. The control and monitoring signals between the Automation Level
controllers and the Field Level components shall be via industry standard
analogue ranges, except where detailed below, such as 0 to 5V, 0 to 1 OV, 4 to
20 MA, switched 0 and 5V, switched 0 and 1 OV, etc.
incorporate points from the packaged AlC units monitoring and control
system into various BMS sequences of operation.
j. Monitor ambient conditions.
k. Monitor alarm points for the MA TV, P ABX, master clock and radio
paging systems.
l. Monitor and control other points as determined as requesed by the
detailed electrical system design.
3. The mapping of the monitoring and control BACnet objects into the Terminal
and Data Servers and the preparation of data presentation for the third party L.V.
building systems that are integrated at the Automation level. L.V. building
systems serving equipment that is also monitored and controlled by the BMS
DDC controllers shall be integrated at the Automation level. Such L.V. systems
shall be as follows:
a. Chillers
b. VSD
4. The mapping of the monitoring and control EACnet objects into the Terminal
and Data Servers and the preparation of data presentation for the third party L.V.
building systems that are integrated at the Management level. L.V. building
systems serving equipment that is not monitored and controlled by the EMS
DDC controllers shall be integrated at the Management level. Such L.V. systems
shall be as follows:
a. Emergency generator monitoring and control system.
b. The PROJECT EMS shall be a turnkey installation and shall include the
integration of the extra low voltage building systems as detailed in these
specifications. Each BMS shall comprise, at minimum, the following
components:
1. Computer based.
2. Fully networked.
3. Real time.
4. Distributed processing.
5. No single point of failure.
6. All data shall be available as BACnet objects at the Management level network.
D. The BMS shall be configured to ensure reliability of systems operation and control of critical
functions/systems. In general, all monitoring and control of separate systems shall be achieved
via single control panels. Critical inputs of a system shall be wired directly to tlte controlling
panel. Where required, dedicated control panels shall be provided and shall not share any point
monitoring or control witlt other systems.
E. All components of the BMS at the Management Level and at tlte automation level, except for the
unitary controllers, shall operate on UPS. The UPS shall be not be provided by the BMS sub-
contractor. The BMS sub-contractor shall advise tlte Electrical contractor within X 8 weeks of
award of contract what tlte BMS load will be for UPS power.
F. The components furnished under this contract shall be the most recent products offered by tlte
BMS manufacturer that meet the specifications. If there are improved models of any components
furnished under this contract that become available before the on-site commencement of
installation then tltese shall be offered by the BMS sub-contractor to the Employer at no
additional cost to tlte Employer. The Employer shall have the option to accept or decline the
offer. The components offered shall have been in successful operation in at least 2 similar
applications for a minimum of 12 months.
G. The BMS sub-contractor shall provide all software licenses necessary for the legal operation of
the components furnished under this contract. It is intended that a site WIde enterpriselicense
shall be provided for the terminal server software and that it shall cover all Thin Client terminals
accessing the Management Level Network and that tlte addition of Thin Client terminals in the
future shall not require additional licenses.
H. All electrical equipment, devices and components and their installation shall comply with the
latest edition of the IEE Wiring Regulations (BS 7671: 1992 Requirements for electrical
installations) and all associated addenda, the electrical contract specifications for the project and
all other applicable codes, regulations and statutes.
I. A11 components shall be IP 2X finger protected to BS 60529 such that live components cannot
be accidentally touched. Interior enclosures shall be, at minimum, IP 45 to BS 60529 and exterior
enclosures shall be weatherproofIP 65 to BS 60529 unless specifically noted otherwise within
these contract documents.
J. Where there is any conflict between the requirements of the different project contract documents,
statutes, codes, regulations, local ordinances and any requirement of an agency having
jurisdiction over the project, the most stringent requirement shall apply unless determined
otherwise by the Employer. Advise the Engineer of any discrepancy or conflicts between the
various requirements for the project.
L. Equipment, devices and materials shall conform to all performance requirements of the
specifications when exposed to the following interferences:'
1. VHF and UHF signals as generated by external or internal portable or fixed transmitters.
2. AM signals as generated from transmitters.
3. Electrical noise on the building power system, both spurious and harmonics.
4. The installations shall not radiate signals that cause interference to the correct operation
of the Employer's on-site equipment.
5. The BMS and all individual electrical equipment, devices and components shall comply
with the requirements of BS EN 50081-1 (General Emission Standard) and BS EN
50082-1 and 2 (General Immunity Standard), the requirements of the Federal
Communication Commission rules and regulations Part 15, sub part J and all other
applicable codes and statutes with respect to the radiation and conduction of radio
frequency interference.
N. Provide adequate earthing on all equipment to prevent the build-up of electromagnetic voltage
potentials. Provide screening of panels, enclosures, devices, or components that emit
interferences. All monitoring and control and communication cables shall be screened with one
end earthed.
O. Provide the following support for all components furnished under this contract:
A. Each BMS, as installed, shall incorporate a minimum of 20 percent additional hardware (field)
points without adding controllers or 1/0 Point Interface Modules (pIM). The number and type of
the installed spare points shall be uniformly distributed between the installed controllers.
B. The Management level and Automation level networks and network components shall not be
more than 30% loaded.
C. Network architecture shall allow unlimited expandability by the addition of new sub networks
and associated routers, gateways, etc.
B. Repair work shall not include routine maintenance during Defects Liability Period. The cost of
providing routine maintenance during the Defects Liability Period shall be provided separately as
an Optional Price as detailed below.
C. Replace or repair all supplied defective installations. Respond and be on site within four (4) hours
of the Engineer and/or Employer placing a system trouble call for items of an immediate nature
(e.g.: failed component, non-functioning controller, etc.). Response to warranty call out by the
Engineer and/or Employer shall be within 24 hours for items not requiring inunediate attention.
Work to troubleshoot and identify the cause offue BMS system or component failure shall begin
immediately and shall continue until repaired to. the satisfaction of fue Engineer and Employer.
A. Submit an Optional Price for routing maintenance services during the Defects : Liability Period.
The provision of such services shall be at the sole discretion of the Employer who may instruct
accordingly.
B. Provide routine maintenance services during the Defects Liability Period, if such is separately
instructed by the Employer. The maintenance services shall cover routine preventative
maintenance but shall not include emergency maintenance or the cost of replacing defective
materials during the Defects Liability Period.
C. Under routine maintenance components of the BMS shall be selectively inspected and serviced
during the Defects Liability Period. Provide, at minimum, four (4) preventative service
inspections during the Defects Liability Period. Perfornl, at minimum, the following during each
preventative service inspection:
D. The routine maintenance services during the Defects Liability Period shall include 20 hours per
year of programming changes to the BMS as requested by the Employer.
E. Any software upgrades and new software programmes that become standard product offerings
from the BMS sub-contractor and/or BMS equipment vendors during the Defects Liability Period
shall be brought to the attention of the Employer together with the cost and, if the Employer
wishes, he shall purchase the software. If at any time during the Defects Liability Period, software
patches that correct software errors become available the Employer shall be notified immediately
and they shall be made available to the Employer at no additional cost.
F. Update the as-built documentation submitted at the time of taking-over of the Works that may
have been introduced during Defects Liability Period.
G. Detail the minimum number of hours to be spent on routine maintenance during the Defects
Liability Period in the tender submittal. \
H. The BMS sub-contractor shall maintain an inventory of common components in the local office
for the replacement of failed components as detailed under "Spare Parts".
I. Provide replacement components within the specified time periods for the following components.
The subcontractor shall guarantee to the Employer that the delivery of replacement components
will be provided within the specified time periods.
BMS Component Delivery Time
J. The BMS sub-contractor shall replace all consumable items during the Defects Liability Period.
Consumable items shall include, but not be limited to, the following:
1. Toner/ink for those printers furnished under this Contract.
2. Paper for printers furnished under this Contract.
3. Filters for PC furnished under this Contract.
4. Batteries for equipment furnished under this Contract.'
5. CD/Tapes for back up of data and software furnished under this Contract.
6. Other consumable items furnished under this contract that have a life expectancy that
would render them less than 100% effective before the end of the Defects Liability
Period.
K. During the Defects Liability Period the BMS sub-contractor shall maintain a minimum of 10%
spare DCP, CCP and UC of each type installed on site under this contract. At the end of the
warranty period the EMS contractor shall hand over DCP, CCP and UC of each type to the
Employer which shall, at minimum, be equal to 10% of the number of installed DCP, CCP and
UC of each type installed on site under this contract.
L. During the Defects Liability Period the BMS sub-contractor shall maintain a minimum of 10%
spare sensors of each type installed on site under this contract. At the end of the warranty period
the BMS sub-contractor shall hand over sensors of each type to the Employer, which shall, at
minimum, be equal to 10% of the number of installed sensors of each type installed on Site under
this contract.
A. Submit an Optional price to extend the Warranty period and the maintenance during that period
for ten (10) one (I) year periods. The maintenance service contract shall be an all-inclusive labour
and parts contract but the Employer reserves the right to obtain parts from alternative sources.
The requirements during each additional year shall be exactly the same as those detailed in Part
1.10 of this Section.
B. The BMS subcontractor shall enter into a direct contract with the Employer to provide the
maintenance services for a minimum period of ten (10) years. The signing of a maintenance
services contract, if the Employer so chooses, shall be a prerequisite to obtaining substantial
completion. The Employer shall have the option to renew each year if the Employer so wishes.
The BMS subcontractor shall submit the cost for the maintenance service agreement in one of the
following ways:
1. A fixed price for a ten (10) year Agreement with a break-out between labour and parts, or
2. A fixed price for the first year of the ten (10) year Agreement with a break-out between
labour and parts for the first year and a percent value or a table of percent values that the
labour portion of the cost would be escalated at during the succeeding nine (9) years and
a percent value or a table of percent values that the parts portion of the cost would be
escalated at during the succeeding nine (9) years, or
3. A fixed price for the first year of the ten (10) year Agreement with a break-out between
labour and parts for the first year with the annual increase for labour and parts over the
succeeding nine (9) years based on the annual percent increase in a cost of living index
from one year to the : next, the cost of living index to be used is to be specified by the
EMS sub-contractor in the tender submittal.
C. If at any time during the maintenance service contract, software patches that correct software
errors become available the Employer shall be notified immediately and they shall be made
available to the Employer at no additional cost.
D. During the period of the maintenance contract the BMS sub-contractor shall maintain a minimum
of 10% spare DCP, CCP and UC of each type installed on site under this contract. At the end of
the maintenance contract the BMS sub- contractor shall hand over DCP, CCP and UC of each
type to the Employer which shall, at minimum, be equal to 10% of the number of installed DCP,
CCP and UC of each type installed on site under this contract.
E. During the period of the maintenance contract the BMS sub-contractor shall maintain a minimum
of 10% spare sensors of each type installed on site under : this contract. At the end of the Defects
Liability Period the BMS sub-contractor shall hand over sensors of each type to the Employer,
which shall, at minimum, be equal to 10% of the number of installed sensors of each type
installed on site under this contract.
A. Obtain all required pemrits and inspection certificates. All pennits and certificates shall be made
available to the Employer .
B. The latest requirements of all national, county, municipal and other authorities having jurisdiction
shall be met.
D. All electrical work shall comply with the latest edition of the lEE wiring regulations (BS 7671)
1.13 SCHEDULE
A. Complete all requirements of the BMS sub-contract in accordance with the project programme
and prior to the scheduled Substantial Completion date for each phase.
C. Provide to the Engineer a schedule indicating the sequence of work, durations of individual tasks,
delivery dates for all material, devices and equipment and detail any interface that must be
coordinated with any other Contractors.
D. Provide written status reports at required intervals and in a fonnat acceptable to the Engineer. An
updated schedule of work shall be included in each status report.
E. Comply with the Project Construction Schedule. Provide additional staffing or work overtime as
required to comply with the Project Schedule so as not to interfere with other on-site Contractors
in their effort to comply with the Project Schedule. Confinn, prior to tender submittal, that all
equipment, devices, material and services proposed are available and will be delivered
accordingly to comply with the Project Schedule.
F. Provide written Request For Infonnation notices to the Engineer when specific information or
clarification of the specifications is required. Request For information notices shall be provided at
least X 2weeks prior to the need for the information.
A. Provide equipment, devices and materials for interior and exterior applications that shall be
capable of withstanding and operating satisfactorily in, at minimum, the following ambient
conditions:
A. Provide anti virus software for all components that are vulnerable to viruses. Anti virus software
shall be provided with free virus definition updates for the duration of the warranty. Anti virus
software should automatically scan the computer bios and all files opened, created, copied, and/or
received for viruses. Include directions for updating virus definition f1les upon expiration of
warranty within the record documentation.
D. Remote Control System: Configure remote control units, data interface units,
input sensing devices, and output control elements to perform the following
functions:
1. Process variable sensing, signal transmitting, and signal conversion for each
input point.
2. Signal conversion, transmitting, and operation of control drive or other
element for each output point.
3. Receive remote control programs and system data from central
communication system.
4. Manual entry of remote control programs.
5. Storage of data and remote control programs.
6. Execute remote control program commands.
7. Transmit local status data to central communication system.
8. Execute commands received from central communication system.
1.17 QUALIFICATIONS
C. Supplier to have an in-place support facility within 100 miles of the site with,
spare parts inventory and all necessary test and diagnostic equipment.
B. BMS shall comply with UL 916 PAZX and 864 UDTZ and be so listed at the
time of bid. All equipment used in system is to bear appropriate UL listing
label/mark to ensure compliance.
D. Inspection: the Engineer has the right, at all times, to inspect the work, piping
material, equipment, or quality assurance procedures as applicable to confirm
that requirements as set forth are being complied with. Provide all tools,
instruments and equipment necessary to facilitate these inspections.
G. Inspection duties assigned to the Contractor's personnel are to include, but are
not limited to, the following:
1. verify that all non-destructive testing personnel are qualified for the work
being done
2. verify that all components received comply with the Specification and
receipt, inspection and storage of materials comply with requirements of the
Specification
3. verify that the Contractor's storage facilities are maintained
4. verify that rack wiring check and electrical continuity tests are conducted in
accordance with the Specification
5. witness that all hydrostatic tests performed on instrument sensing lines are
in accordance with the Specification and that all tests are properly filled in
signed and submittal for approval
6. witness all pneumatic leak tests performed on instrument sensing lines and
pneumatic tubing required by the Specification
7. verify that all wiring insulation tests are performed in accordance with the
Specification and that all test reports are properly filled in, signed and
submitted for approval
8. verify that assembly and nameplates of the transmitter racks are in
accordance with the Specification
9. verify that all racks, panels and local instruments have been located in
accordance with the Specification
10. verify that all tubing supports are in accordance with the Specification
11. verify that all tubing has been installed in accordance with the Specification
12. verify that all repairs and revisions to instrument components and
assemblies are in accordance with the Specification
13. verify that all repairs and revisions to instrumentation, tubing and their
components is in accordance with the Specification
14. inspect in detail the tubing system or portions of the system as completed
to verify that system or portion of system is correct and complete as
specified prior to the initiation of any flushing, hydrostatic test, or leak test
opera
15. witness the construction loop inspection performed by the Contractor. All
items contlcomponents to conform to the specification requirements and
drawings. Equipment and components to be undamaged as determined by
visual examination. All documentation as required to be complete and on
file. Construction loop inspection, as performed, to comprehensively and
conclusively prove completeness and conformity of the installation to the
Drawings and Specification
16. verify that calibration of instrumentation and control loops is in accordance
with the approved procedures as submitted in the project procedures manual
17. witness the calibrated loop check and verify that all calibration reports are
properly filled in, signed and submitted for approval
18. witness the system operational tests on a sub-system basis to assure
operational integrity and conformance to operational requirements as
specified
19. verify all plant documentation required for plant acceptance is in accordance
with sub-section SUBMITTALS for completeness and conformance.
1.20 TECHNICAL PROPOSALS
A. Technical proposals shall be prepared in accordance with these specifications.
Three copies of the proposal shall be submitted. The technical proposal shall
include the following data/information as a minimum. The order of listing here
is not intended to indicate, nor should it be construed to indicate, the relative
importance of the data/information:
1.21 SUBMITTALS
C. Product Data: Provide for each component, including sensors, control drives and
elements, plug-in circuit boards, and enclosed equipment units. Include cabinet
dimensions, weights, and support point locations for each item of enclosed
equipment.
D. Design Data: Indicate basis of optimization algorithms.
G. Submit software provider's license agreement stating limits on use, copying, and
transferring software.
I. Where installation procedures, or any part thereof, are required to be in accord with the
recommendations of the manufacturer of the material being installed, printed copies of
these recommendations shall be furnished to the Engineer prior to installation.
Installation of the item will not be allowed to proceed until the recommendations are
received.
J. P & I or process flow diagrams: to be completed for each system and submitted for
approval. Instrument symbols and identification to be in accordance with ISA-S5.1.
K. Technical Data Sheets: control and instrumentation technical data sheets (TDS) to be
prepared for each device. TDS to be similar to and meet the intent of ISA-S20, 1975.
L. Loop Diagrams: control and instrument loop diagrams prepared and furnished for all
instrument systems. Typical diagrams are not permitted. Loop diagrams are to be
unique for each loop.
O. Instrument Installation: detail drawings for each field installation are to be furnished.
Details are to include but are not limited to instrument piping details, transmitter rack
details and pipe mounted equipment installation details.
P. Logic Diagrams detailing the operational logic are to be completed for the digital
binary operations. In addition to these drawings, operational logic descriptions are to
be prepared detailing the sequence of operation and operational constraints and
limitations. These drawings are to be in conformance with ISA-S5.2, 1976. Submit
details for each ZPU/SPU separately, in addition to logic diagrams relating Central
Control Room processing functions and resulting operations.
Q. Instrument Schedule listing all devices to be keyed to instrument loop number and
device numbers. Schedule to be submitted in two (2) formats; first, in an alpha-
numeric listing by device type and second, a listing with equipment grouped by loop
number. Schedule to contain as a minimum the following information:
balance of plant equipment but also that equipment furnished as part of packaged
systems and is to be noted as such.
S. Prior to procurement of equipment submit for approval the following drawings and
documents:
T. Prior to start of system installation and construction submit for approval the following
drawings and documents:
V. Prior to system acceptance and turn-over and as a condition of system acceptance, the
following documents are to be submitted in four copies in accordance with
requirements of Division 1:
6. tests and calibration data pertinent to each item installed in the systems.
A. Deliver, store, protect, and handle products to site under provisioins of the Contract
Documents
A. Furnish service and maintenance of building management system for one year from
Date of Substantial Completion.
A. As soon as practicable after approval of materials and equipment and, if possible, not
later than 4 months prior to the date of beneficial use, submit spare parts data for each
different item of equipment furnished. Data to include a complete source of supply, a
list of parts and supplies that are either normally furnished at no extra cost with the
purchase of the equipment, or specified hereinafter as EXTRA MATERIALS to be
furnished as part of the Contract; and a list of additional items recommended by the
manufacturer to assure efficient operation for a period of 360 days at the particular
installation. The foregoing is not to relieve the Contractor of any responsibilities under
the guarantee condition.
PART 2 PRODUCTS
A. Simens
B. Honeywell Trend
C. Automated Logic
D. Satchwell Controls
E. Delta Controls
F KMC
or approved equal.
A. The design of the BMS shall network operator workstations and stand-alone DDC
Controllers.
B. Access to system data shall not be restricted by the hardware configuration of the
Building Management System. The hardware configuration of the BMS network shall
be totally transparent to the user when accessing data or developing control programs.
1. Operator workstations and DDC Controllers shall directly reside on a network such
that communications may be executed directly between DDC Controllers, directly
between workstations and between DDC Controllers and workstations.
2. Systems that operate via polled response or other types of protocols that rely on a
central processor, file server, or similar device to manage panel-to-panel
communications may be considered only if a similar device is provided as a
standby. Upon a failure or malfunction of the primary central processor, the
standby shall automatically, without any operator intervention, assume all BMS
network management activities.
3. All operator devices shall have the ability to access all point status and application
report data or execute control functions for any and all other devices. Access to
data shall be based upon logical identification of building equipment. No hardware
or software limits shall be imposed on the number of devices with global access to
the network data.
4. Network design shall include the following provisions:
a. Provide high-speed data transfer rates for alarm reporting, quick report
generation from multiple controllers and upload/download efficiency
between network devices. System performance shall insure that an alarm
occurring at any DDC Controller is displayed at workstations and/or alarm
printers within 5 seconds.
b. Support of any combination of DDC Controllers and operator workstations
directly connected to the network.
c. Message and alarm buffering to prevent information from being lost.
d. Error detection, correction and retransmission to guarantee data integrity.
e. Synchronization of real-time clocks, to include automatic daylight savings time
updating between all DDC Controllers shall be provided.
C. Telecommunication Capability:
D. Provide all necessary hardware and software for remote communications with all
remote processors, back-up processors and all operator input/output peripheral devices.
Controller hardware for remote communications to be modular. It is to be possible for
each channel to be individually programmed (or re-programmed) for its function and
appropriate baud rate by on-line operator software. Each communications channel to be
fully buffered, and to support asynchronous data transmission and recep. All
communications channels to be able to communicate simultaneously to support the
real-time, multi-tasking, multi-user operating syspecified here. Eacommunication
channel to be dual- trunk fully redundant type; loading to be up to 60% of
manufacturer's recommended limits.
Configuration and control of any system "point" is not to require special software.
Point capacity of system to be a function of available system memory only.
D. Secondary Processing Unit (SPU) to be stand alone or networked DDC panel, fully user
programmable, menu driven, command driven or colour graphics. SPU is to have dual
8 bit CPUs and a modem access. The SPU is to include all the software necessary to
programme end devices and zone controllers and to have up to 150 input/output zone
controller. SPU is to have a 72 hours battery back-up of the data base stored in RAM.
Each SPU is to have the capability to communicate and programme up to 150 zone
controllers.
E. A user friendly programming language is to be used to programme the SPU and the
zone controller connected to it. Further the panel is to have the predefined
software listed below:
- input points
- output points
- pulse points
- annual schedule
- weekly schedule
- alarm
- controller
- totalizer
- trend log
- zone controller access points
- optimized start
- system display
- user access
- scale range
- load shed
F. Zone Processing Unit or Controller (ZPU) to be distributed stand alone DDC controller
for control of various unitary and terminal equipment or controls with built in network
communication for integration into the BMS system. Zone controller is to have flexible
control strategies with user configurable algorithms that reside in a non volatile
memory. Zone controllers are to have a serial port that will allow the connection of
electronic sensors, set point adjustment, overrides at service tools.
H Data Dumpings: if SPU OR ZPU memory fails, the operator shall not have to manually
re-enter system data. Necessary hardware and software are to be supplied to:
- allow periodic dumping of operator entered data onto another storage media
on-line
- reload this data as the operator desires.
Data dumpings are not to interrupt any other system operation (such as operator
input/output, scanning of field hardware, application software execution, etc.)
1.Control processes
2.Energy management applications
3.Alarm management applications including custom alarm messages for
each level alarm for each point in the system.
4. Historical/trend data for points specified
5. Maintenance support applications
6. Custom processes
7. Operator I/O
8. Dial-up communications
9. Manual override monitoring
C. Each DDC Controller shall support:
b. Digital inputs
1) Dry contact closure
2) Pulse Accumulator
3) Voltage Sensing
2. Direct control of pneumatic and electronic actuators and control devices. Each
DDC Controller shall be capable of providing the following control outputs
without the addition of equipment outside the DDC Controller cabinet:
a. Digital outputs (contact closure)
1) Contact closure maintained
2) Contact closure pulsed
3) Contact closure staged
b. Analog outputs
1) 0-20 psi
2) 4-20 mA
3) 0-10 Vdc
D. Each DDC Controller shall have a minimum of 10% spare capacity for future point
connection. The type of spares shall be in the same proportion as the implemented I/O
functions of the panel, but in no case shall there be less than two spares of each
implemented I/O type. Provide all processors, power supplies and communication
controllers complete so that the implementation of a point only requires the addition of
the appropriate point input/output termination module and wiring.
1. Provide sufficient internal memory for the specified control sequences and have at
least 25% of the memory available for future use.
E. DDC Controllers shall provide at least two RS-232C serial data communication ports
for operation of operator I/O devices such as industry standard printers, operator
terminals, modems and portable operator's terminals. DDC Controllers shall allow
temporary use of portable devices without interrupting the normal operation of
permanently connected modems, printers or terminals.
F. As indicated in the point I/O schedule, the operator shall have the ability to manually
override automatic or centrally executed commands at the DDC Controller via local,
point discrete, on-board hand/off/auto operator override switches for digital control type
points and gradual switches for analog control type points. These override switches
shall be operable whether the panel processor is operational or not.
2. DDC Controllers shall monitor the status of all overrides and inform the operator
that automatic control has been inhibited. DDC Controllers shall also collect
override activity information for reports.
G. DDC Controllers shall provide local LED status indication for each digital input and
output for constant, up-to-date verification of all point conditions without the need for
an operator I/O device. Graduated intensity LEDs or analog indication of value shall
also be provided for each analog output. Status indication shall be visible without
opening the panel door.
I. Isolation shall be provided at all peer-to-peenetwork termination, as was all field point
terminations to suppress induced voltage transients consistent with IEEE Standards
587-1980.
J. In the event of the loss of normal power, there shall be an orderly shutdown of all DDC
Controllers to prevent the loss of database or operating system software. Non-volatile
memory shall be incorporated for all critical controller configuration data and battery
backup shall be provided to support the real-time clock and all volatile memory for a
minimum of 72 hours.
1. Upon restoration of normal power, the DDC Controller shall automatically resume
full operation without manual intervention.
2. Should DDC Controller memory be lost for any reason, the user shall have the
capability of reloading the DDC Controller via the local RS-232C port, via
telephone line dial-in or from a network workstation PC.
2.05 DDC CONTROLLER RESIDENT SOFTWARE FEATURES
A. General:
1. All necessary software to form a complete operating system as described in this
specification shall be provided.
2. The software programs specified in this Section shall be provided as an integral
part of DDC Controllers and shall not be dependent upon any higher level
computer for execution.
B. Control Software Description:
1. The DDC Controllers shall have the ability to perform the following pre-tested
control algorithms:
a. Two-position control
b. Proportional control
c. Proportional plus integral control
d. Proportional, integral, plus derivative control
e. Control loop tuning
2. Control software shall include a provision for limiting the number of times each
piece of equipment may be cycled within any one-hour period.
3. The system shall provide protection against excessive demand situations during
start-up periods by automatically introducing time delays between successive start
commands to heavy electrical loads.
4. Upon the resumption of normal power, each DDC Controller shall analyze the
status of all controlled equipment, compare it with normal occupancy scheduling
and turn equipment on or off as necessary to resume normal operations.
C. DDC Controllers shall have the ability to perform any or all the following energy
management routines:
1. Time-of-day scheduling
2. Calendar-based scheduling
3. Holiday scheduling
4. Temporary schedule overrides
5. Start-Stop Time Optimization
6. Automatic Daylight Savings Time Switchover
D. DDC Controllers shall be able to execute custom, job-specific processes defined by the
user, to automatically perform calculations and special control routines.
3. A single process shall be able to incorporate measured or calculated data from any
and all other DDC Controllers on the network. In addition, a single process shall
be able to issue commands to points in any and all other DDC Controllers on the
network.
4. Processes shall be able to generate operator messages and advisories to operator
I/O devices. A process shall be able to directly send a message to a specified
device or cause the execution of a dial-up connection to a remote device such as a
printer or pager.
1. All alarm or point change reports shall include the point's English language
description and the time and date of occurrence.
2. The user shall be able to define the specific system reaction for each point. Alarms
shall be prioritized to minimize nuisance reporting and to speed operator response
to critical alarms. A minimum of six priority levels shall be provided for each
point. Point priority levels shall be combined with user definable destination
categories (PC, printer, DDC Controller, etc.) to provide full flexibility in defining
the handling of system alarms. Each DDC Controller shall automatically inhibit
the reporting of selected alarms during system shutdown and start-up. Users shall
have the ability to manually inhibit alarm reporting for each point.
4. In addition to the point's descriptor and the time and date, the user shall be able to
print, display or store a 200 character alarm message to more fully describe the
alarm condition or direct operator response.
1. DDC Controllers shall store point history data for selected analog and digital
inputs and outputs:
a. Any point, physical or calculated may be designated for trending. Any point,
regardless of physical location in the network, may be collected and stored in
each DDC Controllers point group. Two methods of collection shall be
allowed either by a pre-defined time interval or upon a pre-defined change of
value. Sample intervals of l minute to 7 days shall be provided. Each DDC
Controller shall have a dedicated RAM-based buffer for trend data and shall
be capable of storing a minimum of 25000 data samples.
2. Trend data shall be stored at the DDC Controllers and uploaded to the workstation
when retrieval is desired. Uploads shall occur based upon either user-defined
interval, manual command or when the trend buffers are full. All trend data shall
be available for use in 3rd party personal computer applications.
3. DDC Controllers shall also provide high resolution sampling capability for
verification of control loop performance. Operator-initiated automatic and manual
loop tuning algorithms shall be provided for operator-selected PID control loops as
identified in the point I/O summary. Provide capability to view or print trend and
tuning reports.
a. In automatic mode, the controller shall perform a step response test with a
minimum one-second resolution, evaluate the trend data, calculate the new
PID gains and input these values into the selected LOOP statement.
b. For troubleshooting in manual mode, the operator shallbe able to select
variables to override default values. Calculated PID gains shall then be
reviewed before they are inserted into the selectLOOP statement.
c. Loop shall be capable of being initiated either locally at the DDC Controller,
from a network workstation or remotely using dial-in modems. For all loop
tuning functions, access shall be limited to authorized personnel through
password protection.
G. DDC Controllers shall automatically accumulate and store run-time hours for digital
input and output points as specified in the point I/O summary.
1. The totalization routine shall have a sampling resolution of one minute or less.
2. The user shall have the ability to define a warning limit for run-time totalization.
Unique, user-specified messages shall be generated when the limit is reached.
H. DDC Controllers shall automatically sample, calculate and store consumption totals on
a daily, weekly or monthly basis for user-selected analog and digital pulse input type
points as specified in the point I/O summary.
2. The totalization routine shall have a sampling resolution of one minute or less.
3. The user shall have the ability to define a warning limit. Unique, user-specified
messages shall be generated when the limit is reached.
I. DDC Controllers shall have the ability to count events such as the number of times a
pump or fan system is cycled on and off. Event totalization shall be performed on a
daily, weekly or monthly basis for points as specified in the point I/O summary.
1. The event totalization feature shall be able to store the records associated with a
minimum of 9,999.9 events before reset.
2. The user shall have the ability to define a warning limit. Unique, user-specified
messages shall be generated when the limit is reached.
A. Provide two portable operator terminals with a minimum LCD display of 80 characters
by 25 lines and a full-featured keyboard. The POT shall be handheld and plug directly
into individual distributed control panels as described below. Provide a user-friendly,
English language prompted interface for quick access to system information, not codes
requiring look-up charts.
2. Backup and/or restore DDC Controller data bases for all system panels, not just
the DDC Controller connected to.
3. Display all point, selected point and alarm point summaries.
4. Display trending and totalization information.
5. Add, modify and/or delete any existing or new system point.
6. Command, change setpoint, enable/disable any system point.
7. Program and load custom control sequences as well as standard energy
management programs.
8. Provide connection capability at a room sensor to access controller information.
9. Provide status, setup and control reports.
10. Modify, select and store controller data base.
11. Command, change setpoint, enable/disable any controller point.
C. If the same Portable Operator's Terminal cannot be used for all control processors,
provide separate POTs to accomplish the above functional requirements.
E. Connection of a POT to a distributed control processor shall not interrupt nor interfere
with normal network operation in any way, prevent alarms from being transmitted or
preclude centrally initiated commands and system modification.
B. Standards: all peripheral devices to utilize ASCII (American Standard Code for
Information Interchange) code and to be interfaced to the processing units with
standard RS232 port. Communication versatility is to comply with all methods
previously specified herein.
The above authority keys to be software programmable while system is fully on-
line with at least six (6) priority levels. Each operator authority code to consist of
from one to eleven alphanumeric characters, each individually definable and
modifiable through keyboard entry while the system is online. Minimum of 50
authority codes to be provided. Each authority code to have the following
characteristics:
Unit is to automatically create hardcopy record when an operator has been granted
access.This record to include date and time, which device and which operator was
granted access. System to also have capability to store this record historically (with
or without associated hardcopy record) with future retrieval/analysis capability,
should this mode of recording be preferred. Operator access to be terminated either
by operator command or automatically by the system as predetermined by the
authority access timer.
Operator to have the ability to command points, request information, select entry
method, enter memory changes and edit any number of characters without having
to retype an entire line/screen.
E. Operator Entry: there are to be multiple methods of operator entry. These to consist of,
but are not limited to, the following:
1. tutorial method used as a prompting aid to assist an operator each step of the
way in executing the command function
2. dedicated method which will bypass the tutorial method to allow a quick,
direct command syntax/sequence for system processing. Systems without a
direct command are unacceptable
3. template method used for mass repetitive/data entry of information and
commands. This method to also be used for data base generation, including
such items as point definition, graphic generation, report creation, and
custom/DSC programming/ translation.
Any method of entry is to be verified by the system prior to execution. Any invalid
entries to be highlighted by the system for operator correction. Operator to be able to
request help in any mode of operation at any time to aid in command entry. This help
request to convert mode or provide aid lists on the request parameters. Any operator
entry is not to inhibit any change-of-state COS reporting. Each time an operator
command is issued the system to automatically create a hardcopy record.
F. Function Keys: as an aid to the operator, the system MMI to provide dedicated function
keys (DFK) for common/repetitive operator functions. These functions to be executed
by single operator keystroke. Utilization of dedicated function keys is not to inhibit
any COS reporting or any other simultaneous functions that operator may be
performing. Provide at least 12 DFK/keyboard. Different keyboards to be
programmed to maideal with specific areas or sub-systems (such as electrical, HVAC),
although it is also to be possible for any one to take over completely. Thiis to be
G. Printers: system printers to provide hardcopy data retention of COS, operator initiated
actions, management reports, graphics and trended information. Printers which can be
interfaced include the following:
- color printer
- receive only (RO) printer
Main control station to be provided with one color and two receive only printers.
Secondary stations to be provided with one color and one receive printer.
2. The display provided for system operation shall have a diagonal screen
measurement of no less than 13" and a minimum display resolution of no less than
640 x 480 pixels. Separate controls shall be provided for color, contrasts and
brightness. The screen shall be non-reflective.
B. Provide a printer (RO) for recording alarms, operator transactions and systems reports,
meeting the following minimum requirements:
C. Provide a color printer for printing of graphics and any other screen displays. Printer
shall include as a minimum:
1. 80 Column tractor-feed for normal use with ability to switch to friction feed of
single sheets of paper without any mechanical adjustments.
2. 360 x 360 Dot/Inch image resolution.
3. Draft and letter quality print selection for alpha-numeric operations.
4. Four color mix capability to provide true color printing of screen graphics.
5. Three built-in letter quality fonts from selectable front panel buttons.
6. 32K Buffer to store complete graphics for printing.
A. General: provide Cathode Ray Tubes (CRT) and keyboards to display realtime data,
allow operator commands, perform data base generation and report system activity.
B. CRTs connected to the system to include color CRT with direct video capability having
minimum 480 mm diagonal display with minimum of 48 lines and 80 character/column
screen with refresh rate of 60 times per second. Format of screen to permit output of
dynamic color displays and/or summaries specified hereinafter, while concurrently
displaying the most recent COS occurrence. It is to have detachable, tactile feedback
keyboard having standard typewriter layout plus 10-key numeric key pad and dedicated
function keys.
C. Format CRT to include and display in an individual dedicated and protected area of the
viewing screen the following dynamic information:
Formats are to permit the out of various forms of point displays specified hereinafter,
while concurrently displaying the most recent COS occurrence. Furthermore, while
this information is displayed, the operator to also be able to enter commands to the
system.
E. Any and all CRT screen images to be printable upon single keystroke. While screen
image is being printed, the system is not to inhibit operator utilization of CRT.
F. Color CRT to output chromatic system graphic displays as specified. These chromatic
graphic displays to detail all mechanical and electrical systems listed in the schedule
attached to this Specification. Operator request for a chromatic graphic display is to
cause associated system to be automatically selected and outputted on viewing screen.
When a point is in alarm on the CRT, the operator to be able to display a graphic with a
single keystroke.
A. Transducers: to include, but are not necessarily limited to, temperature sensors, pressure
switches or level switches. Transducer is a device that converts information about a
physical parameter from form in which it is received to some other form, e.g., pressure
to voltage. It is the primary element in an instrumentation and control system, is
inserted in the process flow stream, and provides the signal that can be read, recorded,
alarmed or provides control within a process.
B. Flow Switch to be vane actuated type, designed to mount to pipeline with threaded
coupling 50 mm NPT. Suitably shaped and beveled coupling is welded to pipe and
flow switch is threaded directly into it. Flow switch to be designed for vertical
installation on horizontal pipelines and to be marked to indicate direction of flow.
Actuating vane is linked to pivoted mercury switch. When vane moves with increase in
flow it will trip the switch. Screw fasteners securing actuating vane to be back welded
for added safety. Switch to be SPDT sealed mercury switch with rating 13 amperes. All
materials subject to wetting to be 316 stainless steel. Switch to be in NEMA 4 housing.
Conduit connection to housing to be 20 mm NPT. Perform necessary tests to assure
that flow switch will be operational at specified flow rates. Repeatability of flow rate
actuation point is to be within 0.1 %.
C. Pressure Switch to be flexible diaphragm type, with diaphragm sealed in place with "O"
ring. Diaphragm and ring to be of Buna-N. Diaphragm seals out the process fluid but
transfers pressure variations directly to a spring based piston. Pre-stressed spring to be
adjustable to calibrate operating point of switch. Switch element to be a snap action
contact transfer type transferring on 0.55 mm movement. Switch to be electrically rated
at 480 volt (max) at 15 amps., AC service, and 125 volt, 0.5 amp, DC resistive load.
Pressure connections to be sized for 12 mm NPT fittings and pipe. Electrical
connections use 20 mm NPT conduit. Housings to be weathertight and conform to
NEMA 4 ratings.
D. Differential Pressure Elements to be bellows type with liquid fill. Bellows and center
plate to be completely filled with clean, non corrosive, low freezing point liquid, and to
stand repeated over-ranging in excess of working pressure of instrument housing
without causing calibration change. Temperature compensation to be provided for the
fill. Torque tube assembly to be an integral part of the bellows assembly to transmit
motion. Torque tube assembly to be so designed that it is installed in a preloaded
condito prevent backlash as it rotates through its complete range. Rotation of torque
tube for full scale differential pressure to be 8 deg.+/-10%. Unto operate within
temperatlimits of-5 to +55 deg C. Process connections to be 12 mm NPT.
Perform necessary tests to ensure that PIT meets all operational and manufacturer
specifications.
H. Pressure Transmitter (PT): to be high stability transducer utilizing solid state circuitry.
Output is a 4.0 - 20.0 mA DC signal proportional to sensed pressure. Accuracy of
instrument to be 0.25 % of span. Two barrier type terminals for No.14 wire plus ground
connections to be provided. Process pressure connections to be made through 6 mm
NPT. Conduit for electrical connections to be 20 mm NPT. Instrument to be operational
in a thermal environment of from -29 deg C to +39 deg C.
Perform necessary tests to ensure that pressure transmitter meets all operational
manufacturer specifications.
TIT: integral indicator to have clear glass or polycarbonate window. Shile scale with
black markings and red pointer is to provide indication. Effective length of scale to be
not less than 150mm.
Perform all necessary tests to ensure that temperature indicating transmitter meets all
operational and manufacturer's specifications.
Displacer cage to be of fabricated steel ANSI 600 lb. rating. Length 810 mm.
Equalizing connection to be screwed fittings, 50 mm NPT. Displacer float and
connecting materials to be fabricated of stainless steel.
L. Level Indicating Transmitter (LIT): integrally mounted transmitter, not less than 150
mm in diameter. There are to be screwdriver adjustments for both span and zero
adjustment. Electrical connections to be through 20 mm NPT fittings. An indicator
receiving a 4.0 to 20.0 mA signal calibrated in level indications is to be integrally
mounted with transmitter. It is to be in a NEMA 4 enclosure. Dial to have black
numerals on a white background and to be not less than 75 mm in diameter. Electrical
connections to be through 20 mm NPT fittings.
M. Control Valves:
Spring return type motor, with oil-immersed gear train, die-cast aluminium
case. single 160 degree stroke, double-ended crankshaft, die-cast aluminium
cover with built in transformer and spring to return motor to closed position
on power failure.
Valve rated 115 deg. C maximum water temperature and 860 kPa maximum
pressure for flanged end connections and 1030 kPa for screwed end
connections. Motor rated 50 deg. C maximum ambient temperature.
N. Electric Actuators
Accessories including internal force sensor to switch off motor when force on
stem exceeds factory set force, return spring or hand wheel used on power
failure and end limit switch for status indication.
O. Indicators: are required for operating personnel to monitor the several process control
variables. They are located on control panels. Indicator may be operated electrically,
pneumatically or provide a direct indication. Readout area may be scale and pointer or
level glass.
a. Electrical Indicators are essentially D'Arsonval movements responding to a
signal of 4.0 to 20.0 mA DC. As such they are millimeters calibrated in terms
of the process variable. Meters to have 115 mm dial faces with 270 deg scale
of black numerals on white background. Meter to have nominal accuracy of
not less than 0.5 % of full scale. Electric indicators to have a zero setting
control.
P. Solid State Switch: to be a rack mounted card capable of selecting an analog input
signal and providing an output of contact transfer. Input to unit to be a 4.0 to 20.0 mA
signal applied to a precision resistor. Adjustable reference to be included to provide a
set point. Voltage of this point to be compared with voltage across precision resistor
when input signal exceeds pre-set value, a comparator-amplifier provides a sharp
change in output signal. Transfer contacts to be activated by change in out signal. These
DPDT contacts to be rated at 3 amps., 120 V, 50 hertz or 3 amps., 28 V DC. Operating
parameters to be as follows:
1. Adder-subtracter to be used in all cases where the sum of two to four signals is
required or the difference between two signals is the sought-for parameter.
Module to be a rack-mounted instrument of the non-indicating type. It is to be
mounted in a weatherproof enclosure with easy access to the adjustment controls.
Unit to be easily adjusted on site with capability of changing output equation as
needed. Circuitry of adder-substracter to comprise all solid-state components with
integrated circuit amplifiers to provide stability and longevity. Control signal
inputs to be 0.5 V DC and proportional to the sum of difference of the input
signals. Output load resistance can be between zero and 1850 ohms, as referenced
Care must be taken that input signal is free of noise because a differentiator will
greatly amplify any rapid swing of the input to the point that output is of no
practical value. The Contractor to be responsible for determining rate of change of
pressure that will be deemed unsafe and provide an RC network for unit that will
produce an alarm at unsafe limit.
S. Airflow Sensors:
1. Single point outside air temperature RTD shall be 1000-ohm thin film platinum
resistor sensor with 4-20 mA 2-wire output transmitter with solar shield.
2. Outside air humidity sensor shall be thin film alumina substrate capacitance signal
generating sensor with 4-20 mA 2-wire output transmitter with 0-100% relative
humidity range within +/- 1% RH.Approved Manufacturers:
a. Hy-Cal
b. Viasala
ii Humidity Sensors:
a. Siemens
b. Hycal
c. TCS
d. General astern
e. Vaisala
5. The airflow array shall
be fabricated of galvanized steel or aluminum of adequate gauge to
withstand the velocities to be encountered and with all required
mounting brackets, plates, gaskets, and flanges.
6. Accuracy shall be a
minimum of 3 percent of actual airflow over the designed range of
flow.
7. Provide a companion 4"
Magnehelic gauge, mounted at auxiliary panel, of appropriate span for
each sensor array. Gauges shall be graduated in CFM for airflow
measurement. Provide a phenolic identification tag for each gauge.
8. Approved
Manufacturers:
a. Air Monitor
b. Tek-Aire
c. Dietrich-Standard
d. Ramsey Air
U. Refrigerant leak detection monitoring:
V. Loop-Powered Indicators
1. All temperature and humidity sensors shall be provided with loop powered
indicators mounted on a separate dedicated panel.
A. Type to consist of motorized unit including gear train mounted in cast iron housing
flange mounted electric motor, control cabinet and hand wheel for manual operation.
B. Installation To be suitable for flange mounting directly on valve body, for gate valves
with non rising stem and for manual operation locally. ,
C. Rating to be adequate horse-power and thrust ratings to open and close '" operated
valve smoothly at all conditions of load and pressure.
E. Construction: Weatherproof, with rugged cast iron housing and with hand wheel having
appropriate gearing for emergency manual operation such that maximum applied torque
is 150 Nm. Declutch lever is to disengage drive motor during hand wheel operation and
prevent hand wheel rotating during power operation for safety of personnel. Hand
wheels are to close valve in clockwise direction and are to have arrows and the word
"CLOSE" cast on.
G. Electric Motor. Totally enclosed squirrel cage, induction type conforming to NEMA
Publication No. MGI including character- istics, tests and ratings. Motor is to carry
maximum possible load encountered in valve operation under all normal and abnormal
operating conditions without exceeding nameplate rating and without benefit of service
factor .
B. The valve is to consist of a hytrol main valve, a cover mounted variable orifice
proportioning pilot control and a remote float control. This valve is to be hydraulically
operated, diaphragm actuated, globe pattern. The stem in the main valve to be guided
both top and bottom by a bearing in the valve seat. All necessary repairs in the valve to
be possible without removing the valve from the line. The valve to be all bronze
construction. Mount stainless steel float and float rod in stilling well.
A. The BMS sub-contractor shall provide containment and cables as necessary for a fully
functioning system as detailed in these specifications.
B. Stainless steel flexible metallic conduit shall be provided for the final one (1) metre before
connection from a non-vibrating location to equipment subject to vibration or movement. Flexible
metallic conduit shall be provided for between the last 300mm and the last 100Ornm of
connection to field instrumentation, relays and final control elements as necessary to facilitate the
removal of devices without the disconnection or the bending of the non-flexible conduit.
C. Conduit and trunking shall be securely mounted in accordance with IEE Regulations and shall be
concealed in all areas to which the public have access.
D. Conduit and trunking shall run parallel or perpendicular to the building lines and shall be
installed in a workmanlike manner. Avoid obstructions and crossovers where possible. .
E. Conduit/trunking shall be installed such that any condensation in the conduit cannot run into
BMS equipment. Where necessary conduit shall enter enclosures from the bottom or shall be
sloped up to the enclosure.
F. Junction and pull boxes shall be securely fastened to the conduit, shall be accessible, and shall be
provided where required by code and where necessary to facilitate the pulling of cables. .
H. The BMS sub-contractor shall colour code all conduitltrunking at least every 3,000 mm (10 feet)
along the conduit with a blue and green band at least SOnun wide and colour code every junction
box in a bright yellow
I. Containment shall be provided for all BMS cable except where specifically noted otherwise.
J. BMS monitoring and control cable shall not share conduit with cable carrying voltages in excess
of 48 volts and shall be partitioned from higher voltage cable in trunking.
K. LAN cable shall not share conduit with any other cable or shall be in a dedicated partitioned
compartment in trunking.
L. When cable for digital outputs is installed in conduit it shall be in dedicated conduit and when
installed in trunking shall be partitioned from other cable.
M. All trunking, conduit and accessories shall comply with all applicable codes and standards.
N. Containment shall meet all of the requirements detailed in the electrical contract documents.
A. Provide all cables for the BMS Automation and Field Levels and cable to interconnect the
Management Level devices and the Management Level Network as detailed in these
specifications. Cable shall meet, at minimum, the following requirements:
B. Power wiring shall be sized in accordance with the applicable codes and shall be a minimum of
1.5 sq. rnrn stranded copper. The BMS sub-contractor shall provide all power cable and
containment and shall terminate the power cable at a power outlet close to the component to be
powered and shall provide the power outlet. The MEP contractor shall terminate the power cable
at the MCC/distribution board as applicable.
D. Terminations shall be mechanically and electrically secure. Twist type wire nuts shall not be
acceptable. Insulated tinned copper lugs shall be provided.
E. Cable within panels or enclosures shall be installed in wiring guides.
F. LSF cable not required to be in conduit (refer to requirements for conduit above) shall be routed
parallel and perpendicular with the building column lines. Provide cable rings and supports to
support the cabling. Supports shall be positioned in accordance with BS 7671.
G. All wiring terminations within field panels shall be terminated at terminal stripes
H. Cable run in vertical trunking shall have means of cable support, at minimum, every 3m.
I. Cables shall comply with all applicable codes including, but not limited to, the IEE wiring
regulations latest edition and the electrical contract documents. Where there is a conflict between
any codes, standards, ordinances, regulations or the requirements of the jurisdiction having
authority, the most stringent requirements shall apply.
B. Fibre optic cable (data transmission) shall meet, at minimum, the following requirements :
1. 50 micron core (multi-mode/single mode fibre as necessary to match the fibre provided
by the ICT contractor).
2. 850 nm or 1300 nm LED compatible operation, as requir.ed.
3. Minimum 125 micron cladding.
4. Maximum attenuation of 4.5 db/km (850 nm).
5. Outdoors and below grade fibres shall be run in gel filled tube to protect c against
moisture and micro bending. Tube and fibre shall have a kevlar' braid surrounding, with
suitable outside protective jacketing.
6. Cable shall contain 100% more fibres than required for a single point to- point
communications connection.
7. Outdoor fibre shall be equipped with a central non-conducting member for long pull
applications-
C. Fibre optic cable shall comply with BS EN 69794-1-2: 1999 (Optical fibre cables. Generic
specification -Basic"optical cable ,~test procedures) and all other applicable codes. ..
Choice of additional alarms is left to the discretion of the BMS supplier in accordance
with type of UPS supplied. Capacity to be chosen to meet full extendable capacity
specified, but to be not less than 5 kVA. UPS to comprise an isolation transformer,
input stage followed by a charger/rectifier (220 V AC input-50 Hz, to be coordinated
with Electrical Specification from nearest substation). Battery set to comprise HiCd
cells stacked in series/cascade to provide minimum of 20 minutes back-up, at full load.
System to be equipped with static change-over switch, interruption time being
commensurate with CPU system supplied.
A. General: BMS software package specified herein to be a real time, online, multitasking
and multi-user operating system. All features specified herein to be supplied as a
package to meet the requirements of this specification. With operator performing any
function (data base generation, commanding points, custom programming, requesting
information, etc.), this is not to inhibit receipt/recording/ processing of any change-of-
state (COS).
have a complete data base to include all hardware address assignments, English
language identifiers, operator station assignments, COS response handling, point
type assignments, even program interaction assignments and equation assignments
for each point.
Should A.C. line power be cycled, upon resumption, the system is to automatically
restart and:
- output a power failure message, indicating time and date of occurrence
- initialize processors and communications
- update all time programs
- compare all BMS point conditions before and after power failure and output
only the changed conditions as a COS.
Power fail system to be defined online by operator. Operator to be able to add and
delete loads, add and delete power status points, define power fail system parameters
and enable or disable individual power fail systems. Each BMS point to be
programmable on a per point basis as to its restorability under normal or emergency
power operation.
Program shall allow saving/restoring of operating data. This operating data is that
which:
- keeps current with actual building conditions
- contains system's operator enterable parameters which are time consuming to
re-enter manually
- operator does not ordinarily change to meet the building's operation
requirements.
Each Field Processing Unit to store current state and value of each point within its
central equipment memory and to make this data available through various system
reports. Each point and its data to be addressed by its level identifiers described
herein. Operator to be able to attain point status information by command or
automatically, as pre-programmed, to a designated peripheral device. Accessible
information to be determined by operator's authority level. Point information to
include, but is not limited to, the following:
Point information to provide for outputting information for single point, specific
group of points, specific class of points, type of points, etc. Execution of output
command to be recorded with date and time.
C. Change-Of-State (COS) Reporting: BMS to detect and report any change from each
point's normal status. These changes to include, but are not limited to the following
general categories:
- exceeding or returning to predefined limits
- contact status point changing from normal to trouble or abnormal/alarm;
returning to normal
- point failing to respond to commanded condition (allow sufficient delay to
avoid false alarms due to switch- bounce, contact-bounce, etc.)
- totalization limits exceeded
- any hardware ilure/restoration.
BMS to automatically inhibit COS reporting of analog and binary points upon
their associated HVAC control fan system shutdown. COS reporting of these
associated analog and binary points to remain inhibited for an operator
predetermined time, upon restart of HVAC control fan system. This time should be
sufficient to bring controlled environment back to satisfactory operating
conditions. If any of the associated analog and binary points are in their alarm
condition after the time delay, the system to automatically report the COS status,
as specified for those points.
Logs And Summaries to indicate on a per point basis the hardware communication
status through the use of special character of flags. These indicators to be kept
current with the advisories.
E. Graphics Generation: color graphics generation to be done through any color operator
terminal. While in the generation process, the color terminal is not to be inhibited from
receiving any COS information. Generation of graphics to be accomplished with the
following attributes:
BMS is not to restrict the number to graphics that may be generated. Capability to
be provided for storage of graphics on request in a library for future use in
formatting other graphics.
F. Data Base Generation: This is to be done via fill-in-the blank, mass template entry
method. Operator to be able to online:
1. Load Control:
2. HVAC Control:
Bar And Line Graphical Output to be provided through any color CRT with
each color graphical display capable of being color hardcopy recorded upon a
single keystroke. Each point graphed to be designated with a unique color.
Bar graphs to provide ability for comparative point analysis of up to four
points simultaneously. Systems that do not provide comparative point
analysis are not acceptable.
For each bar and line graph display, the BMS to provide a vertical scale of
either actual values or a percentage scale (operator selectable at each display)
and a horizontal scale which the system is to automatically time base with up
to 200 samples per screen. Compression/interval and dynamic
forward/backward scrolling feature to be available to display "off screen"
historical data values.
BMS to also provide the capability for remote historical data storage to the
PC storage disk unit loading media. Capability to be provided to remotely
store categories in any order desired. Recall of remote stored information to
be by information type directly from loading media. It is not to be necessary
to copy information back onto mass storage disk unit for operator analysis.
Any binary contact, high/low limit of any analog point, energy management
feature or mathematical calculated point value to be capable of being utilized
as a master for event initiated programming. Event initiated programming to
be capable of using the same master to monitor or command multiple slaves.
Any master to be capable of being a master to multiple slaves.
Time totalizations to accumulate data for hours of operation for at least the
following general categories:
- equipment runtime
- binary/digital point status (alarm/off-normal/normal) condition
- analog point status condition.
Each totalized value to have a selectable alarm and reset limit. When totalized
value reaches its alarm limit, a COS message to be output and totalization to
continue. When totalized value reaches it reset limit, a COS message to be
output and total to automatically be reset to zero and totalization continued.
Total to also be able to reset to zero by a manual command.
- system Generation
- system Save and restore
- diagnostic Software.
A. General:
1. The Communications Controls Panels (CCP) shall be part of the Management Level
Network, except as noted below. The CCP shall be software programmable gateways that
shall provide a native BACnet/IP to third party gateway between the Management Level
Network and third party L.V. building systems. Certain of the CCP shall be located at the
Automation Level rather than the Management Level. If a third party system provides
monitoring and control for equipment that is also monitored and controlled by a BMS
DDC controller, then the gateway between the third party system and the BMS shall be at
the Automation Level and not at the Management Level. The gateway shall reside on the
same network as the associated DDC controllers.
a. The third party L.V. systems that shall be integrated at the Automation Level in
PROJECT shall be as follows:
i. chiller system controllers
ii. VSD.
b. The third party L.V. building systems that shall be integrated at the Management
Level in PROJECT shall be as follows:
i. Emergency generator monitoring an~ control system
ii. ETC. 2. At minimum the third party protocols shall include
Modbus, JBus, N2, OPC, and LonWorks.
2. The third party L.V. building system contractor shall provide the gateway and complete
documentation to the BMS sub-contractor. The BMS sub- contractor shall connect the
gateway to the Management Level Network and shall map the BACnet object ills to the
terminal servers and shall advise the third party contractor of the BACnet objects ills to
be mapped to the third party L.V. building system.
3. The third party L.V. building system contractor shall provide the gateway and complete
documentation to the BMS sub-contractor. The BMS sub. contractor shall connect the
gatewayto the Automation Level Network and shall map the BACnet object ills to the
terminal servers and shall advise the third party contractor of the BACnet objects ms to be
mapped to the third party L.V. building system. Inrormation that is provided by third
party systems at the Automation Level shall be available at the Management Level
Network in exactly the same way as information obtained via gateways located at the
Management Level.
4. The intent of this section is to identify the minimum information that shall be made
available at the Management Level Network by the third party L.V. building systems. If
the third party system is able to supply additional information to the Management Level
Network then the third party system contractor shall advise the Employer and the
Employer shall determine which additional information is to be transferred through the
BA Cnet/lP to third party gateway. The third party system contractor shall be responsible
for the interface between the third party system and the Management Level Network.
5. The BMS sub-contractor shall liaise with the manufacturer and/or contractor responsible
for the third party system and shall provide all details regarding the BACnet protocol as
necessary for the third party contractor to implement the interface between the BMS and
the Management or Automatic Level Network.
6. The BMS sub-contractor shall be responsible for the preparation of third party system
data presentation using the data presentation facilities at the tenninal servers. 8. The
interface between the Management or Automation Level Network and the third party
system shall be demonstrated at an off site location. If the test is successful the third party
system contractor shall advise the Engineer and a time shall be established that is
acceptable to the Engineer when the interface can be demonstrated to the Engineer at the
third party system contractor's facility or some other locatio.n acceptable to the Engineer.
The third party system contractor shall be responsible for providing all equipment,
including applicable components of the third party system, necessary to perfonn the
demonstration and for ensuring the presence at the testing of suitably skilled personnel.
The testing of the interface between the Management or Automation Level Network and
the third party system shall verify, at minimum, that:
a. All data communicated from the third party system to the Management Level
Network
b. All data points mapped from the BMS to the third party system are displayed
correctly on the third party system monitor.
c. All mapped points are identical with regard to value, engineering units and
significant digits on both systems.
d. All points mapped from the third party system to the BMS meet all of the
specifications detailed in the contract documents for points directly
monitored/controlled by the BMS.
e. The communications watchdog is functioning correctly. f. Communications speed
between the two systems is satisfactory. g. Both systems restart and
communications between the two systems resume following a power failure
without operator intervention.
7. Each of the third party systems shall be tested on-site without the interface to the
Management Level Network. Once the Engineer has accepted the systems, the systems
shall be interfaced to the Management Level Network and shall be retested as part of the
final acceptance testing.
8. Documentation regarding the third party Management Level Network interfaces shall be
provided in sufficient detail so as to enable a person reasonably skilled in the writing of
real time software applications to add/delete points mapped from one protocol to the
other. At minimum the documentation shall include a detailed description of each
protocol used and the model, version and finnware details of any protocol converter
{gateway) that is used.
9. A watchdog procedure must be implemented by the BMS sub-contractor that enables the
identification of the point of failure, i.e. where in the communications chain between the
two systems did the failure occur . The watchdog function must operate at a frequency
that detects a communications failure within a maximum of 5 seconds for the chillers and
emergency generators and within a maximum of30 seconds for all other interfaces except
the fire alann system that shall implement a check every hour.
10. The third party contractor shall warrant the third party system interface and provide
software support for a minimum of 10 years. Software code associated with the third
party interface shall be deposited at a secure third party establishment if so requested by
the Employer.
1. Each chiller shall have a microprocessor based unit controller. fu addition there shall be a
chiller system control panel that shall supervise and monitor the operation of all chillers.
The chiller system controller shall provide a BACnet interface to output the operating
data, shutdown/cycling messages and a record of the last 4No. cycling or safety
shutdowns for each chiller to the BMS.
2. The chiller system controller/BMS interface, shall at minimum enable the following data
to be transferred from the chiller controllers to the BMS and the Management Level
Network:
a. Entering Chilled Water Temperature (monitoring point)
b. Leaving Chilled Water Temperature (monitoring point)
c. Evaporator Pressure (monitoring point)
d. Auxiliary Oil Pressure (monitoring point)
e. Bearing Pressure (monitoring point)
f. Gear Pressure (monitoring point)
g. vaporator Differential Pressure (monitoring point)
h. Evaporator Temperature (monitoring point)
i. Suction Temperature (monitoring point)
j. Pre-A1ann (Monitoring Point)
k. Gear Box High Temperature Setting (Monitoring Point)
I. Gear Box Low Temperature Setting (Monitoring Point)
m. Oil Compressor Status (Monitoring Point)
n. Flow Safety (Monitoring Point)
o. Motor Safety (Monitoring Point)
p. Motor Run Status (Monitoring Point)
q. Rear Thrust Bearing Temperature (Monitoring Point)
r. Front Thrust Bearing Temperature (Monitoring Point)
s. Gear Oil Temperature (Monitoring Point)
t. Current Limit (Control Point)
u. Chilled Water Supply Temperature Reset (Control Point) v. Chilled Water Pump
Run Status (Monitoring Point) w. Chilled Water Pump Alann (Monitoring Point)
3. The chiller system controller shall, at minimum, enable the following data to be
transferred from the BMS to the chiller controllers:
a. Start/stop chilled water system.
b. fudicate number of chillers required.
b. Chilled water supply temperature reset. Each chiller shall have the same chilled
water supply temperature setpoint.
c. Chiller demand limit reset. Each chiller shall have the same demand limit.
4. The philosophy of BMS chiller control shall be that the BMS shall determine when
chilled water is to be provided and shall determine the number of chillers required. The
chiller system controller shall detennine which chillers to start and the individual chiller
control panels shall undertake the start up procedure. The EMS shall not be able to
override anyofthe chiller safeties such as the minimum time between a shut down and the
next start up or the interlocks with flow proving switches, etc.
5. The chilled water pumps shall be controlled by the chiller unit controllers and the system
controller.
6. The EMS sub-contractor shall obtain all BACnet object IDs from the chiller contractor
and shall map the objects to the terminal server. The BMS sub-contractor shall provide a
schematic display of the points using the graphical user interface.
7. The chiller interface shall be at the automation level such that the failure of the
Management Level Network shall not affect the interchange of information between the
associated EMS controllers and the chillers.
C. Interface between the Management Level Network and the emergency generators:
1. The emergency generator contractor shall provide a BACnet/IP interface to the
Management Level Network.
2. The digital communications interface shall be set up so as to provide, at minimum, the
following monitoring points at the Management Level Network:
a. Generator set summary alarm (If available at the generator control centre the
BMS sub-contractor may alternatively monitor this point via a volt free contact)
D. Interface between Management Level Network and the fire alarm system:
1. There shall be a transfer of information from the Fire Detection. Alann and
Communication System (FAS) to the Management Level Network. The communication
shall be uni-directional from the F AS. to the L.V. building systems Management Level
Network only. The F AS shall be on its own wide area network.
2. The F AS contractor shall provide a BACnet/IP interface to the Management Level
Network
3. Whenever there is a change of status of a detector, input device. zone or fire alarm control
panel electronics, the F AS shall communicate the appropriate information to the L.V.
building systems Management Level Network, regardless of whether the change of status
is the result of an alarm. fault or return to nonnal.
4. The start and end of the message shall be uniquely identified and the message shall
indicate the following information at minimum: 1. Time 2. Date
3. Zone of incidence
4. Indication of whether it is a fire alarm. return to normal or F AS system fault.
5. The FAS shall send a message to all BMS on an operator detem1ined scheduled basis.
initially set at once every hour. The BMS shall generate an alarm if the message is not
received or if the message is not decipherable.
6. The BMS shall automatically shut down all V A V teffi1inal units and FCU serving the
zone of incidence in the event of afire alarm and shall automatically restart equipment
following a return to normal message, as detailed in the Part titled "Equipment Restart
Following a Fire Alarm.. in . this Section of the documents.
7. The BMS sub-contractor shall obtain all BACnet object IDs from the F AS contractor and
shall map the objects to the terminal server. The BMS , subcontractor shall provide a
schematic display of the. points using the : graphical user interface. ,
8. The FAS interface shall be at the Management level.
E. Interface between Management Level Network and the lighting control systems:
1. The lighting contractor shall provide a BACnetlIP interface to the Management Level
Network.
2. The lighting controller BACnet/IP interface for the systems shall be set up so as to
provide, at minimum, the following information to the Management Level Network:
a. Lighting relay status for each individual relay.
b. Lighting load (kW) for each zone.
c. Lighting consumption (kWh) for each zone. d. Monitor zone lighting levels
3. The lighting controller BACnet/IP interface for the systems shall be set up so as to enable
the BMS, at minimum, to undertake the following functions:
a. Lighting relay on and off control for each zone.
b. Set zone lighting levels.
c. Change the schedule for any lighting zone.
d. Ascertain the lighting status (on/oft) and dimming s,tatus of any lighting zone.
4. The BMS sub-contractor shall obtain all BACnet object ills from the lighting controls
contractor and shall map the objects to the terminal server. The BMS subcontractor shall
provide a schematic display of the points using the graphical user interface. .
5. The lighting controller interface shall be at the automation level such that the failure of
the Management Level Network shall not affect the interchange of information between
the associated BMS controllers and the lighting controller.
F. Interface between the Automation Level Network and variable speed drives (VSD):
1. The variable speed drive suppliers shall provide a BACnet or BACnetlIP interface to the
Automation Level Network
2. The digital communications interface shall be set up so as to provide the BMS, at
minimwn, with the following monitoring and control points:
a. Start and stop control.
b. Speed control.
c. Speed reference feedback.
d. Motor operating status.
e. VSD alarm.
f. Motor power in kW.
g. Motor kWh.
h. Motor current.
i. Motor voltage.
j. Hours run.
k. DC link voltage.
1. Thennalload on motor.
m. Thermal load on VSD.
n. Heat sink temperature.
3. The BMS sub-contractor shall obtain all BACnet object IDs from the VSD suppliers and
shall map the objects to the terminal server. The BMS sub-contractor shall provide a
schematic display of the points using the graphical user interface.
4. The VSD interfaces shall be at the automation level such that the failure of the
Management Level Network shall not affect the interchange of infonnation between the
associated BMS controllers and the VSDs.
G. Interface between the Management Level Network and the building security systems:
1. The BSS contractors shall provide a BACnetlIP interface to the Management Level
Network.
2. The building security systems shall communicate all of the data required to meet the
integrated operations detailed in these and the security contract documents via the
BACnet/IP gateway to the Management Level Network.
3. The BMS sub-contractor shall obtain all BACnet object IDs fum the building security
systems contractor and shall map the objects to the terminal server. The BMS sub-
contractor shall provide a schematic display of the points using the graphical user
interface.
H. Interface between the Management Level Network and the uninterruptible power
supplies:
1. BACnet/IP gateways between the Management Level Network and the UPS shall be
provided by the UPS suppliers.
2. The digital communications interface shall be set up so as to provide, at minimum, the
following monitoring and control points:
B. Operation station to have a central processing unit such that it can be configured as a
fully operational stand-alone maintenance management system. Operator display to
consist of a color CRT capable of displaying 48 lines x 80/132 color with a screen size
of 19" and a resolution of 1056 x 400 image points. The printer to be capable of
printing 132 characters per line on standard 8.5 x 11 inch continuous contractor feed
paper at a minimum rate of 220 characters per second. The printer shall be capable of
using fan fold single sheets of paper.
The system to have a minimum of 4 megabytes of random access mass storage and
be expandable to 200 megabytes. Storage may be added by connecting additional
storage units and assigning portions of the programming, data base or maintenance
history to the auxiliary storage devices.
The system to operate through the use of linked menus which guide the operator
to the proper screen or function. The operator to be capable of directly accessing
any system operation without stepping through successive menus. He is to be
capable of directly accessing frequently used functions by a single keystroke
through the use of software designated function keys.
The operator to have access to all system documentation while operating the
system. This to include information detailing the use and operation of the menu,
template, and field in the system. He is to be capable of displaying the information
to either the display or printer. The system to grant operator access to system
functions on a per menu selection basis. A minimum of fifteen passwords shall be
supported.
The system to be capable of executing other facility functions when not executing
maintenance management software. These functions shall include:
- word processing
- accounting
- graphics
- spreadsheets.
C. Data Base: the entire data base to be structured to allow a minimum number of required
entries for facilities where the operation is not data intensive. The system to also be
comprehensive and flexible enough to ensure that additional optional data can be
entered to allow more sophisticated configurations to be created.
The component data base to allow the following data to be entered on either a
mandatory or optional basis:
Separate data to exist for recording information on sub- component parts and repair
parts. Additionally, the system to have the capability of creating user defined
component data base parameters.
The system to allow for a property data base such that non maintainable
components can be tracked as part of the system. All maintainable components
may also have a property record. The property data base shall include such
parameters as:
D. Task Schedules: the system to support a system of master schedules such that
components with similar maintenance requirements can all draw on a single master
schedule. The schedule to be constructed in such a way that minor maintenance
variations between similar components can be accommodated without resorting to
creating additional master schedules. The master schedules to include the following
information:
E. BMS Interface: the system to support an interface data base to the BMS system to
allow the transfer of runtime and alarm data to the work order generator. Components
to be capable of being assigned a minimum of three runtime schedules and one alarm
schedule. The data base to include the following information:
* Alarm Schedule * Runtime Schedules
* Last Runtime Issued * Next Runtime Expected
* Current Runtime * Component ID
F. Work Order Generation: the system to support scheduled work order generation on a
weekly basis, for any segment of the year or seasonally, or by runtimes as accumulated
at the BMS. Scheduling to be done on either a calendar or a fiscal year basis. Work
orders to be sorted before printing by several user selectable criteria. The system to be
capable of generating one million work orders per year.
The system to support a user defined custom work order format. This format is to
be applicable to both scheduled and repair work.
G. Maintenance History to store the following data as a minimum:
Maintenance history to also compute year-to-year totals and other pertinent history
data.
EQUIPMENT: show all chillers, heaters, pumps, air handling units and fans as per mechanical
drawings.
CONTROL POINTS: show all control points relate to all equipment indicated above as per
point list.
PLUMBING CONTROL
DOMESTIC COLD AND HOT WATER SYSTEM: show all control points as per point list.
FIRE PUMP: show layout plan, with location, by colour change status.
ZONE ALARM/FAULT: allow for backup advisory messages in case of alarms generation.
Relay for action to be taken; mechanical equipment shutdown, etc.
ELECTRICAL CONTROL
POWER DISTRIBUTION SYSTEM: system overview with indication of list feeders, main
feeders, tie breaker status, by colour change. Show all control points as per point list.
DIESEL ENGINE SYSTEM: show all control points as per point list.
LIGHTING PANEL BOARDS: system overview with status indication of all contactors.
PART 3 EXECUTION
3.01 EXAMINATION
C. Verify that required utilities are available, in proper locations, and ready for use.
A. Provide a separate DDC Controller for each AHU. Two AHU systems may be placed
on one DDC Controller if sufficient points are available. However, all points associated
with any AHU system must be located on the same DDC Controller.
B. Connect motor controllers, lighting controls, fire alarm and smoke detection devices,
intrusion detection and security access devices, sensing and measurement devices,
electrical controls and relays, programmablelogic controller, under provisions of Div16
related Sections.
B. Field Test: When installation of the system is complete, calibrate equipment and verify
transmission media operation before the system is placed on-line. All testing,
calibrating, adjusting and final field tests shall be completed. Provide a detailed cross-
check of each sensor within the system by making a comparison between the reading at
the sensor and a standard traceable to the National Bureau of Standards. Provide a
cross-check of each control point within the system by making a comparison between
the control command and the field-controlled device. Verify that all systems are
operable from local controls in the specified failure mode upon panel failure or loss of
power. Submit the results of functional and diagnostic tests and calibrations to the
Engineer for final system acceptance.
C. Compliance Inspection Checklist: Submit in the form requested, the following items of
information to the Engineer for verification of compliance to the project specifications.
Failure to comply with the specified information shall constitute non-performance of
the contract. The contractor shall submit written justification for each item in the
checklist that he is unable to comply with. The Engineer will initial and date the
checklist to signify contractor's compliance before acceptance of system.
1. Verify to the Engineer in letter form that supplier has in-place support facility.
Letter shall show location of support facility, name and titles of technical
staff, engineers, supervisors, fitters, electricians, managers and all other
personnel responsible for the completion of the work on this project.
5. Disconnect one DDC Controller from the network to demonstrate that a single
device failure shall not disrupt or halt peer-to-peer communication. Panel to be
disconnected shall be selected by the Engineer.
a. At least one temperature setpoint and at least one status condition, i.e., on or
off for a system or piece of equipment attached to that panel as well as for
points at another DDC Controller on the network.
b. The diagnostic results as specified for a system or piece of equipment attached
to that panel as well as for a system or piece of equipment attached to
another DDC Controller.
c. The ability to add a new point to the DDC Controller with the POT and have
it automatically uploaded to the workstation to modify that panel's stored
database.
A. Adjust setpoints, alarm points, and display configurations so that system performs as
specified.
3.07 CLEANING
A. General Requirements: Provide all services, materials and equipment necessary for the
successful operation of the entire BMS system for a period of one year after completion
of successful performance test. Provide necessary material required for the work.
Minimize impacts on facility operations when performing scheduled adjustments and
non-scheduled work.
B. Description of Work: The adjustment and repair of the system includes all computer
equipment, software updates, transmission equipment and all sensors and control
devices. Provide the manufacturer's required adjustments and all other work necessary.
D. Schedule of Work: Provide two minor inspections at 6 month intervals and two major
inspections offset equally between the minor inspections to effect quarterly inspection
ofalternating magnitude, and all work required as specified. Minor inspections shall
include visual checks and operational tests of all equipment delivered. Major
inspections shall include all work described for minor inspections and the following
work:
E. Emergency Service: Owner will initiate service calls when the system is not
functioning properly. Qualified personnel shall be available to provide service to the
complete system. Furnish owner with a telephone number where service representative
can be reached at all times. Service personnel shall be at the site within 24 hours after
receiving a request for service. Restore the control system to proper operating
condition within 3 days.
H. Software: Provide all software updates and verify operation in the system. These
updates shall be accomplished in a timely manner, fully coordinated with the system
operators, and shall be incorporated into the operations and maintenance manuals, and
software documentation.
3.09 DEMONSTRATION
3.10 TRAINING
A. The Contractor shall provide competent instructors to give full instruction to designated
personnel in the adjustment, operation and maintenance of the system installed rather
than a general training course. Instructors shall be thoroughly familiar with all aspects
of the subject matter they are to teach. All training shall be held during normal work
hours as follows:
C. Provide additional training quarterly for a period of one year from final coof the
project.