Upload
buingoc
View
230
Download
1
Embed Size (px)
Citation preview
Version Description
V1.4 General Revision
V1.41 Revised to include underscore delimited tags
V1.42 Added the following:
7.4.12 – Status Effect requirement
7.4.13 – Popup menu requirement
Revised Section 7.8 – Alarms to reference
Requirements Specification Enterprise Buil
V2.0 Version number updated to major version change to align with
Handling Subsystem (AHS) Requirements Specification Enterprise Building
Management System (EBMS)
Added the following:
7.4.14 – Mouse Over requ
V2.1 For Circulation
Building Management Systems (BMS)
Standard
DOCUMENT HISTORY
include underscore delimited tags
Status Effect requirement
Popup menu requirement
Alarms to reference Alarm Handling Subsystem (AHS)
Requirements Specification Enterprise Building Management System (EBMS).
Version number updated to major version change to align with Alarm
Handling Subsystem (AHS) Requirements Specification Enterprise Building
Management System (EBMS).
Mouse Over requirement.
Building Management Systems (BMS) Design
Date issued
31/5/2012
28/6/2012
5/6/13
17/6/2013
March 2016
Design
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Name Position
Dennis Spicer Mechanical Engineer
Dennis Harrold Technical Officer
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
CIRCULATION APPROVAL
Position
Mechanical Engineer
Technical Officer
Circulation Approval
i
Approved
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard
TABLE OF CONTENTS
1.0 PURPOSE
2.0 SCOPE
3.0 REFERENCES AND STAND
4.0 DEFINITIONS AND ABBR
5.0 INTRODUCTON
5.1 GENERAL REQUIREMENTS
6.0 BMS SPECIFICATIONS
6.1 GENERAL
6.2 SCOPE BY BMS CONTRACTOR
6.3 SCOPE BY OTHERS
6.4 SYSTEM ENGINEERING
6.5 NETWORK ARCHITECTURE
6.6 FIELD CONTROLLERS
6.7 MINIMUM FIELD DATA REQUIREMENTS
6.8 FIELD SENSORS AND ACTUATORS
6.9 TEMPERATURE SENSORS
6.10 TEMPERATURE - FLUID MEASUREMENT
6.11 SPECIFICATION OF THE LOCAL HEADEND COMPUTER
6.12 SPECIFICATION OF ENCLOSURES, COLOUR, CAB
7.0 SOFTWARE
7.1 SECURITY
7.2 COMMONISED NETWORK AND ADDRESSING SCHEME
7.3 POINT NAMING CONVENTION
7.4 GRAPHICS
7.5 SCHEMATIC GRAPHICS
7.6 TABULAR GRAPHICS
7.7 FLOOR PLANS
7.8 ALARMS
7.9 TIME SCHEDULING
7.10 HISTORY AND TRENDLOGGING
8.0 PLANT CONTROL FUNCTI
8.1 MISCELLANEOUS COMMENTS
APPENDIX A STANDARDISED METHODOLOGY FOADDRESSING
APPENDIX B GRAPHICS STYLE SHEETS
APPENDIX C - PROTOCOL IMPLESTATEMENT (NORMATIVE
Building Management Systems (BMS) Design Standard
Building Management Systems (BMS) Design Standard
TABLE OF CONTENTS
REFERENCES AND STANDARDS
DEFINITIONS AND ABBREVIATIONS
INTRODUCTON
GENERAL REQUIREMENTS
BMS SPECIFICATIONS
SCOPE BY BMS CONTRACTOR
SCOPE BY OTHERS
SYSTEM ENGINEERING
NETWORK ARCHITECTURE
FIELD CONTROLLERS
MINIMUM FIELD DATA REQUIREMENTS
FIELD SENSORS AND ACTUATORS
TEMPERATURE SENSORS
FLUID MEASUREMENT
SPECIFICATION OF THE LOCAL HEADEND COMPUTER
SPECIFICATION OF ENCLOSURES, COLOUR, CABLING AND LABELING
COMMONISED NETWORK AND ADDRESSING SCHEME
CONVENTION
SCHEMATIC GRAPHICS
TABULAR GRAPHICS
TIME SCHEDULING
HISTORY AND TRENDLOGGING
PLANT CONTROL FUNCTIONS
MISCELLANEOUS COMMENTS
DISED METHODOLOGY FOR BACNET ADDRESSING
S STYLE SHEETS
PROTOCOL IMPLEMENTATION CONFORMANCE STATEMENT (NORMATIVE)
Table of Content
Nov 2015
1
2
3
4
5
7
7
8
8 8 9 9
10 11 12 22 22 22
24 LING AND LABELING 25
26
26 26
26 27 29 30 30 30 30 31
32
33
R BACNET 34
35
E 43
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
1.0 PURPOSE
The purpose of this Guideline Requirements and Specifications is to provide a design guide for
Project Managers and Designers developing specifications for Building Monitoring and Control
Systems at the Macquarie University.
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
The purpose of this Guideline Requirements and Specifications is to provide a design guide for
Managers and Designers developing specifications for Building Monitoring and Control
Systems at the Macquarie University.
Purpose
2
The purpose of this Guideline Requirements and Specifications is to provide a design guide for
Managers and Designers developing specifications for Building Monitoring and Control
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
2.0 SCOPE
This document scopes the type of technology and systems that are compatible with the current
MACQUARIE UNIVERSITY BMS system architecture.
NOTE WHERE THIS SYMBOL APPEARS: Overview functionality is included in this document.
It is expected that designers will customize the requirements within their documentation package,
however this specification includes minimum requirements.
Controllers and other system equipment are specified to the extent that compliance with BACnet
and some basic architecture and functionality requirements are met. It is not intended to completely
specify requirements that consultants may need, but is aimed at providing
encouraging vendors to offer innovative solutions. Vendors may offer equipment that exceeds these
specifications.
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
This document scopes the type of technology and systems that are compatible with the current
MACQUARIE UNIVERSITY BMS system architecture.
NOTE WHERE THIS SYMBOL APPEARS: Overview functionality is included in this document.
It is expected that designers will customize the requirements within their documentation package,
however this specification includes minimum requirements.
nd other system equipment are specified to the extent that compliance with BACnet
and some basic architecture and functionality requirements are met. It is not intended to completely
specify requirements that consultants may need, but is aimed at providing minimum and also
encouraging vendors to offer innovative solutions. Vendors may offer equipment that exceeds these
Scope
3
This document scopes the type of technology and systems that are compatible with the current
NOTE WHERE THIS SYMBOL APPEARS: Overview functionality is included in this document.
It is expected that designers will customize the requirements within their documentation package,
nd other system equipment are specified to the extent that compliance with BACnet
and some basic architecture and functionality requirements are met. It is not intended to completely
minimum and also
encouraging vendors to offer innovative solutions. Vendors may offer equipment that exceeds these
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
3.0 REFERENCES AND STAND
Macquarie University, Sydney. MACQUARIE UNIVERSITY Design Guidelines
Macquarie University, Sydney,
Enterprise Building Management System (EBMS)
National Institute of Standards and Technology (NIST).
Building Automation and Contr
American Society of Heating Refrigeration and Air
Implementation Conformance Statement)
American National Standards Institute (ANSI). EIA
AS/NZS 3000:2007 Standards Australia. Electrical Installations
Australian Communications and Media Authority: Radio
Compatibility) Standard 2008
nagement Systems (BMS) Design Standard References
Design Standard_V1.1
REFERENCES AND STANDARDS
Macquarie University, Sydney. MACQUARIE UNIVERSITY Design Guidelines
Macquarie University, Sydney, Alarm Handling Subsystem (AHS) Requirements Specification
Enterprise Building Management System (EBMS)
National Institute of Standards and Technology (NIST). GSA Guide to Specifying Interoperable
Building Automation and Control Systems Using ANSI/ASHRAE Standard 135-1995,
American Society of Heating Refrigeration and Air-conditioning Engineers. BACnet PICs (protocol
Implementation Conformance Statement)
American National Standards Institute (ANSI). EIA-485 Communications Standard
AS/NZS 3000:2007 Standards Australia. Electrical Installations
Australian Communications and Media Authority: Radio-communications (Electromagnetic
Compatibility) Standard 2008
References and Standards
4
Alarm Handling Subsystem (AHS) Requirements Specification
GSA Guide to Specifying Interoperable
1995, BACnet
conditioning Engineers. BACnet PICs (protocol
communications (Electromagnetic
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
4.0 DEFINITIONS AND ABBR
AI, Analog Input a value that can be
AO, Analog Output, value that be read from a controller and written to by software
AV, Analog Value, a holding variable such as a setpoint,
BACnet, Interoperability protocol ASHRAE Standard 135p.
BACnet Advanced Application Controll
BACnet Application Specific Controller (BACnet ASC),
BACnet Building Controller (B
BACnet Operator Workstation (B
BCS, Building Control Station, a high level BMS controller typically connected directly to the
MACQUARIE UNIVERSITY WAN . Commonly used to control chillers, large Air Handling systems and
other complex equipment. Must conform to BACnet B
BI, Binary Input, a digital value read from a controller
BO, Binary Output, a digital value that can be written to by software
BV, Binary Value, a digital holding variable
BMCS Contractor, company employed to del
DSC, Distributed Control System
DMZ, Demilitarized Zone
JACE, Java Application Control Engine (trademark of Tridium Inc.)
LDAP, Lightweight Directory Access Protocol
Lonworks, Echelon Corporation Lonworks
Modbus/RTU, Modbus over serial link (RS
Modbus/TCP, Modbus over IP (Transmission Control Protocol)
MUP, Macquarie University Property
Native BACnet system, a system that can be proven to be designed around the BACnet standard.
NMS, Network Management System, a software system for monitoring network devices.
NTP, Network Time Protocol
SNMP, Simple Network Management Protocol
SMTP, Simple Mail Transfer Protocol
Building Management Systems (BMS) Design Standard Definitions
Design Standard_V1.1
DEFINITIONS AND ABBREVIATIONS
Analog Input a value that can be read from a controller
Analog Output, value that be read from a controller and written to by software
Analog Value, a holding variable such as a setpoint,
Interoperability protocol ASHRAE Standard 135p.
BACnet Advanced Application Controller (BACnet AAC), application controller
BACnet Application Specific Controller (BACnet ASC), application controller for VAV, FCU etc
BACnet Building Controller (B-BC), controller device profile for high level network based controllers.
station (B-OWS), network level workstation
Building Control Station, a high level BMS controller typically connected directly to the
MACQUARIE UNIVERSITY WAN . Commonly used to control chillers, large Air Handling systems and
Must conform to BACnet B-BC device profile.
Binary Input, a digital value read from a controller
Binary Output, a digital value that can be written to by software
Binary Value, a digital holding variable
company employed to deliver individual MACQUARIE UNIVERSITY BMCS
Distributed Control System
, Java Application Control Engine (trademark of Tridium Inc.)
Lightweight Directory Access Protocol
, Echelon Corporation Lonworks network standard
Modbus over serial link (RS-485)
, Modbus over IP (Transmission Control Protocol)
, Macquarie University Property
a system that can be proven to be designed around the BACnet standard.
Network Management System, a software system for monitoring network devices.
Simple Network Management Protocol
Simple Mail Transfer Protocol
Definitions and Abbreviations
5
Analog Output, value that be read from a controller and written to by software
application controller for VAV, FCU etc
controller device profile for high level network based controllers.
Building Control Station, a high level BMS controller typically connected directly to the
MACQUARIE UNIVERSITY WAN . Commonly used to control chillers, large Air Handling systems and
iver individual MACQUARIE UNIVERSITY BMCS
a system that can be proven to be designed around the BACnet standard.
Network Management System, a software system for monitoring network devices.
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
RDC, Remote Distributed Controller, BACnet application oriented controllers
BCS or a BACnet router for supervisory functionality, may reside on a lower speed (78Kbs) peer to
peer LAN. Commonly provide VAV, FCU, small AHU, and Packaged Equipment local control. Required
to support B-AAC or B-ASC profile.
RDP, Remote Desktop Protocol (multi
Terminal Services).
SDD, System Design Document, includes all design information for approval prior to installation
VAV, Variable Air Volume (referencing the controller
AHU, Air Handling Unit
FCU, Fan Coil Unit
ACU, Air Conditioning Unit
MUP, Facilities Management Unit
VPN, Virtual Private Network
KVM Switch, Keyboard/Video/Mouse switching device
SRT, System Restoration Time
UTC, Coordinated Universal Time (
Building Management Systems (BMS) Design Standard Definitions
Design Standard_V1.1
Remote Distributed Controller, BACnet application oriented controllers, typically linked to a
BCS or a BACnet router for supervisory functionality, may reside on a lower speed (78Kbs) peer to
peer LAN. Commonly provide VAV, FCU, small AHU, and Packaged Equipment local control. Required
ASC profile.
Remote Desktop Protocol (multi-channel allowing remote clients to connect to Microsoft
System Design Document, includes all design information for approval prior to installation
Variable Air Volume (referencing the controller/actuator)
Facilities Management Unit
Virtual Private Network
, Keyboard/Video/Mouse switching device
System Restoration Time
Coordinated Universal Time (Temps Universel Coordonné)
Definitions and Abbreviations
6
, typically linked to a
BCS or a BACnet router for supervisory functionality, may reside on a lower speed (78Kbs) peer to
peer LAN. Commonly provide VAV, FCU, small AHU, and Packaged Equipment local control. Required
channel allowing remote clients to connect to Microsoft
System Design Document, includes all design information for approval prior to installation
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
5.0 INTRODUCTON
5.1 GENERAL REQUIREMENTS
Each Building shall be installed with a Tridium
any refurbishment proposed with the existing systems. Where more than two vendors are to be
considered for a building, or other than the existing equipment is proposed, endorsement should be
sought from MUP Technical Services, to permit consideration of maintenance complexity.
Controllers shall be based on ANSI/ASHRAE Standard 135
all Building Control Stations (BCS) and Remote Distributed Controllers (RDC), shal
using the protocols and network standards as defined by ANSI/ASHRAE Standard 135
Non-BACnet-compliant or proprietary equipment or systems (including gateways) shall not be
acceptable.
Macquarie University has an enterprise wide
independent of the Building Management Systems. Each BMS will connect to this server for the
purposes of:
� Web-user access (for viewing and control of room temperature setpoints or other
parameters required by MUP
� Clock Synchronisation and global scheduling
� Alarm Management, event archiving and email notification
� History Logging and trend archiving
� Supervisory Control and Monitoring
� Building energy and utility performance profiling
Each BMS shall completely contro
VAV boxes, heat pumps, fan-
BACnet-compliant components.
Building Management Systems will allow for the use
connection of various equipment. This equipment must terminate on a BACnet BCS or RDC:
� Modbus for devices (PLC, chillers, water meters, electricity meters etc)
� Lonworks or C-Bus (lighting and other device networks)
� KNX (for metering devices and other device networks)
� M-bus (heat meters)
� Fieldbus, DNP, CIP (PLCs and other industrial controls for power generation etc)
� SNMP for IT equipment
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
REQUIREMENTS
Each Building shall be installed with a Tridium Niagara based BMS system. Designers should integrate
any refurbishment proposed with the existing systems. Where more than two vendors are to be
considered for a building, or other than the existing equipment is proposed, endorsement should be
MUP Technical Services, to permit consideration of maintenance complexity.
Controllers shall be based on ANSI/ASHRAE Standard 135-2008, BACnet. The operator’s workstation,
all Building Control Stations (BCS) and Remote Distributed Controllers (RDC), shal
using the protocols and network standards as defined by ANSI/ASHRAE Standard 135
compliant or proprietary equipment or systems (including gateways) shall not be
Macquarie University has an enterprise wide architecture that incorporates a BMS server
independent of the Building Management Systems. Each BMS will connect to this server for the
user access (for viewing and control of room temperature setpoints or other
parameters required by MUP)
Clock Synchronisation and global scheduling
Alarm Management, event archiving and email notification
History Logging and trend archiving
Supervisory Control and Monitoring
Building energy and utility performance profiling
control all mechanical equipment, including all unitary
-coils, AC units, etc., and all air handlers, boilers, chillers,
compliant components.
Building Management Systems will allow for the use of industry standard protocols for the
connection of various equipment. This equipment must terminate on a BACnet BCS or RDC:
Modbus for devices (PLC, chillers, water meters, electricity meters etc)
Bus (lighting and other device networks)
NX (for metering devices and other device networks)
bus (heat meters)
Fieldbus, DNP, CIP (PLCs and other industrial controls for power generation etc)
SNMP for IT equipment
Introducton
7
Niagara based BMS system. Designers should integrate
any refurbishment proposed with the existing systems. Where more than two vendors are to be
considered for a building, or other than the existing equipment is proposed, endorsement should be
MUP Technical Services, to permit consideration of maintenance complexity.
2008, BACnet. The operator’s workstation,
all Building Control Stations (BCS) and Remote Distributed Controllers (RDC), shall communicate
using the protocols and network standards as defined by ANSI/ASHRAE Standard 135–2008, BACnet.
compliant or proprietary equipment or systems (including gateways) shall not be
architecture that incorporates a BMS server
independent of the Building Management Systems. Each BMS will connect to this server for the
user access (for viewing and control of room temperature setpoints or other
l all mechanical equipment, including all unitary equipment such as
coils, AC units, etc., and all air handlers, boilers, chillers, etc using native
of industry standard protocols for the
connection of various equipment. This equipment must terminate on a BACnet BCS or RDC:
Modbus for devices (PLC, chillers, water meters, electricity meters etc)
Fieldbus, DNP, CIP (PLCs and other industrial controls for power generation etc)
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
6.0 BMS SPECIFICATIONS
6.1 GENERAL
Each Building Management System provides a standalone function, independent of the Server or any
other System, unless it is specifically designed to integrate with other buildings or plant.
Each Building Management System provides all local automatic cont
includes all hardware, software and programming necessary to achieve a complete Building
Management System.
6.2 SCOPE BY BMS CONTRACTOR
The BMS contractor is required to provide a complete system. That is, complete with all Softwar
Building Control Stations, Remote Distributed Controllers, field points, field instrumentation, cabling,
actuators, controls programming, alarm programming, time schedules, histories (trend logs),
graphics (with room numbers accurately matching current
requirements sufficient to meet the specification and hand over a fully operational system to MUP.
Interfacing with other systems as set out in the specification.
System engineering documentation and drawings prov
approval. Prepare individual System Design Documents (SDD) for approval prior to the
commencement of installation including hardware layouts, interconnection drawings, and software
configuration from project design
� System Description (to achieve the tender design documents)
� Functional Specification of all controls and software functions
� System Interfaces
� Network topology
� Equipment locations
� Equipment installation and connection drawings
� Bill of Materials
� Maintenance Schedules
� Valve and Actuator selection and design data
� Test Plans
Properly trained and qualified technical specialists must be available during all phases of system
installation, testing and commissioning.
Complete program of Site Acceptance Testing
Testing , the contractor is required to provide completed graphics and database. MUP will not
commence SAT without adequate evidence of completed graphics available.
Complete testing documentation and O&M ma
must be supplied as part of the O&M manuals, as well as logic flow diagrams of the DDC control
programming, workstation software, diagrams, and all other associated project operational
documentation (such as technical manuals) on approved media, the sum total of which accurately
represents the final system. The as
CAD Drawing Standards and to be a format fully compatible with the MUP Record Keepi
An electronic copy on DVD is also required.
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
BMS SPECIFICATIONS
Each Building Management System provides a standalone function, independent of the Server or any
other System, unless it is specifically designed to integrate with other buildings or plant.
Each Building Management System provides all local automatic control for mechanical plant and
includes all hardware, software and programming necessary to achieve a complete Building
CONTRACTOR
The BMS contractor is required to provide a complete system. That is, complete with all Softwar
Building Control Stations, Remote Distributed Controllers, field points, field instrumentation, cabling,
actuators, controls programming, alarm programming, time schedules, histories (trend logs),
graphics (with room numbers accurately matching current space planning floor plans), and all other
requirements sufficient to meet the specification and hand over a fully operational system to MUP.
Interfacing with other systems as set out in the specification.
System engineering documentation and drawings provided in advance of installation works for
approval. Prepare individual System Design Documents (SDD) for approval prior to the
commencement of installation including hardware layouts, interconnection drawings, and software
configuration from project design data:
System Description (to achieve the tender design documents)
Functional Specification of all controls and software functions
System Interfaces
Network topology
Equipment locations
Equipment installation and connection drawings
enance Schedules
Valve and Actuator selection and design data
Properly trained and qualified technical specialists must be available during all phases of system
installation, testing and commissioning.
Complete program of Site Acceptance Testing (SAT). Prior to commencement of Site Acceptance
Testing , the contractor is required to provide completed graphics and database. MUP will not
commence SAT without adequate evidence of completed graphics available.
Complete testing documentation and O&M manuals. Full schematic drawings (electrical and DDC)
must be supplied as part of the O&M manuals, as well as logic flow diagrams of the DDC control
programming, workstation software, diagrams, and all other associated project operational
as technical manuals) on approved media, the sum total of which accurately
represents the final system. The as-built drawings are to be provided in accordance with the MUP
CAD Drawing Standards and to be a format fully compatible with the MUP Record Keepi
An electronic copy on DVD is also required.
BMS Specifications
8
Each Building Management System provides a standalone function, independent of the Server or any
other System, unless it is specifically designed to integrate with other buildings or plant.
rol for mechanical plant and
includes all hardware, software and programming necessary to achieve a complete Building
The BMS contractor is required to provide a complete system. That is, complete with all Software,
Building Control Stations, Remote Distributed Controllers, field points, field instrumentation, cabling,
actuators, controls programming, alarm programming, time schedules, histories (trend logs),
space planning floor plans), and all other
requirements sufficient to meet the specification and hand over a fully operational system to MUP.
ided in advance of installation works for
approval. Prepare individual System Design Documents (SDD) for approval prior to the
commencement of installation including hardware layouts, interconnection drawings, and software
Properly trained and qualified technical specialists must be available during all phases of system
(SAT). Prior to commencement of Site Acceptance
Testing , the contractor is required to provide completed graphics and database. MUP will not
nuals. Full schematic drawings (electrical and DDC)
must be supplied as part of the O&M manuals, as well as logic flow diagrams of the DDC control
programming, workstation software, diagrams, and all other associated project operational
as technical manuals) on approved media, the sum total of which accurately
built drawings are to be provided in accordance with the MUP
CAD Drawing Standards and to be a format fully compatible with the MUP Record Keeping System.
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Comprehensive competency based training for MUP maintenance representatives of at least 5 days
for up to 5 people. The BMS contractor is required to supply competency based training for:
1. Operators
2. Administrators
3. Maintainers
The BMS contractor is required to provide a detailed syllabus outlining the courseware to be covered
in each of the three training competencies.
6.3 SCOPE BY OTHERS
Where the system is required to interface with other building systems in
Air-conditioning, fire, security, laboratory ventilation, chilled water manager, lifts, and MACQUARIE
UNIVERSITY Campus Area Network, the design is required to clearly set out the
interface.
All IP network level devices (Building Control Stations) will be connected to the Campus Wide Area
network. IP addresses will be furnished by Macquarie ITS.
6.4 SYSTEM ENGINEERING
Prepare detailed designs for all functions, equipment, analogue and binary objects, time sched
system databases, graphic displays, controls and energy management programs, logs, and
management reports and all other engineering designs based the tender documents.
Prepare an RMA (Reliability, Availability and Maintainability) strategy to ensure
designed for reliable operation and ease of maintenance during its life. The supplier is to advise the
design life of the system. Design life will not be less than 10 years.
All equipment will be designed for installation with AS3000:200
equipment supplied will comply with ACMA Radiocommunications (Electromagnetic Compatibility)
Standard 2008, and carry the C
Inter-connection between all Building Control Stations (BCS) systems must
structured LAN cabling system. Where applicable Building Control Stations will be connected directly
to the Campus Area Network and will be assigned IP addresses and BACnet addresses by MUP IT.
Provide complete manufacturer’s specificati
of every item supplied. This information is to be provided to MUP for approval in advance of
ordering.
The BMCS Contractor will be required to liaise with Macquarie University MUP to develop graphics
that will be provided to MUP for integration into the MUP BMS Server. All graphics templates for
new systems are to be constructed on a common format such that they can be ported directly to the
MUP Server. The BMS Contractor is to ensure that Graphics ar
University Style-sheets (q.v. APPENDIX B) to allow their graphics to be smoothly integrated to the
Server. Prior to commencement of graphics preparation the contractor is to liaise with MUP to
familiarize themselves with the process of transfer of graphics to the MUP BMS Server.
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
Comprehensive competency based training for MUP maintenance representatives of at least 5 days
for up to 5 people. The BMS contractor is required to supply competency based training for:
The BMS contractor is required to provide a detailed syllabus outlining the courseware to be covered
in each of the three training competencies.
Where the system is required to interface with other building systems including but not limited to
conditioning, fire, security, laboratory ventilation, chilled water manager, lifts, and MACQUARIE
UNIVERSITY Campus Area Network, the design is required to clearly set out the specification
level devices (Building Control Stations) will be connected to the Campus Wide Area
network. IP addresses will be furnished by Macquarie ITS.
ENGINEERING
Prepare detailed designs for all functions, equipment, analogue and binary objects, time sched
system databases, graphic displays, controls and energy management programs, logs, and
management reports and all other engineering designs based the tender documents.
Prepare an RMA (Reliability, Availability and Maintainability) strategy to ensure
designed for reliable operation and ease of maintenance during its life. The supplier is to advise the
design life of the system. Design life will not be less than 10 years.
All equipment will be designed for installation with AS3000:2007 Electrical Installations and in all
equipment supplied will comply with ACMA Radiocommunications (Electromagnetic Compatibility)
Standard 2008, and carry the C-Tick approval mark.
connection between all Building Control Stations (BCS) systems must be via an approved
structured LAN cabling system. Where applicable Building Control Stations will be connected directly
to the Campus Area Network and will be assigned IP addresses and BACnet addresses by MUP IT.
Provide complete manufacturer’s specifications for all items that are supplied. Include vendor name
of every item supplied. This information is to be provided to MUP for approval in advance of
The BMCS Contractor will be required to liaise with Macquarie University MUP to develop graphics
that will be provided to MUP for integration into the MUP BMS Server. All graphics templates for
new systems are to be constructed on a common format such that they can be ported directly to the
MUP Server. The BMS Contractor is to ensure that Graphics are built in accordance with Macquarie
sheets (q.v. APPENDIX B) to allow their graphics to be smoothly integrated to the
Server. Prior to commencement of graphics preparation the contractor is to liaise with MUP to
h the process of transfer of graphics to the MUP BMS Server.
BMS Specifications
9
Comprehensive competency based training for MUP maintenance representatives of at least 5 days
for up to 5 people. The BMS contractor is required to supply competency based training for:
The BMS contractor is required to provide a detailed syllabus outlining the courseware to be covered
cluding but not limited to
conditioning, fire, security, laboratory ventilation, chilled water manager, lifts, and MACQUARIE
specification of each
level devices (Building Control Stations) will be connected to the Campus Wide Area
Prepare detailed designs for all functions, equipment, analogue and binary objects, time schedules,
system databases, graphic displays, controls and energy management programs, logs, and
management reports and all other engineering designs based the tender documents.
Prepare an RMA (Reliability, Availability and Maintainability) strategy to ensure that the system is
designed for reliable operation and ease of maintenance during its life. The supplier is to advise the
7 Electrical Installations and in all
equipment supplied will comply with ACMA Radiocommunications (Electromagnetic Compatibility)
be via an approved
structured LAN cabling system. Where applicable Building Control Stations will be connected directly
to the Campus Area Network and will be assigned IP addresses and BACnet addresses by MUP IT.
ons for all items that are supplied. Include vendor name
of every item supplied. This information is to be provided to MUP for approval in advance of
The BMCS Contractor will be required to liaise with Macquarie University MUP to develop graphics
that will be provided to MUP for integration into the MUP BMS Server. All graphics templates for
new systems are to be constructed on a common format such that they can be ported directly to the
e built in accordance with Macquarie
sheets (q.v. APPENDIX B) to allow their graphics to be smoothly integrated to the
Server. Prior to commencement of graphics preparation the contractor is to liaise with MUP to
h the process of transfer of graphics to the MUP BMS Server.
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
All installations must be designed for safe operation and maintenance and comply with all WHS
regulations and relevant Australian Standards. All controls emanating from the DDC to external
devices must be 24VDC or 24VAC originating from a 240V/24V transformer mounted within the DDC
cabinet or in external switchboards and switched by the internal relays within the DDC control
No DDC controller is to switch 240VAC. All 240 VAC switching must
mechanical Motor Control Centre complying with Australian Standards with relay isolation between
DDC controllers and the mechanical electrical control circuit.
All field engineering software
configuration tools) required to program
All software required to make any
anywhere in the system, including
will be supplied to MUP. All software passwords required to program and make
schedules, trends and related program changes will also become the property of
All software licenses (and license agreements) required to operate and maintain the system will be
provided with written evidence that MUP is the beneficial end user.
6.5 NETWORK ARCHITECTURE
Each system will consist of a networked communication structure (with TCP/IP on gigabit or fast
Ethernet at its highest level).
Inter-connection between BCS’s connected to MACQUARIE UNIVERSITY WAN Data ports must be via
an approved structured LAN cabling system, installed by an MUP qualified cabling contractor.
BACnet/MSTP (where used to link sub
grounded and screened twisted pair. Distances must not exceed the EIA
Each BCS will be assigned private corporate class A IP addresses by the MACQUARIE UNIVERSITY IT
Services.
Systems that support an internal System Manager (such as Chilled Water Manager or Lighting
Manager) are to be monitored through BACnet directly. The BMS should not independently measure
data that is measured more accurately or at higher resolution by the Syst
BACnet Routing will be used to link from IP network segments to RS
floor is to contain routers to provide separation between IP backbone and floor networks of
controllers connected to an RS
a router to lower speed RS-485 BACnet MS/TP networks, with the limitation that no more than 64
devices be routed through the BCS.
Local Workstations or servers are to comply with BACnet Operator Workstation profile (B
must be connected directly to the MACQUARIE UNIVERSITY WAN using BACnet IP.
All proposed BACnet controllers are to be furnished with a BACnet protocol Implementation
Conformance Statement (PICS see APPENDIX C) for approval, prior to commencing des
All BACnet devices are to conform to a BACnet Standardized Device Profile (Annex L) and be
provided with a list of all BACnet Interoperability Building Blocks supported (BIBBs, Annex K).
Preference will be given to BACnet controllers that are BA
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
All installations must be designed for safe operation and maintenance and comply with all WHS
regulations and relevant Australian Standards. All controls emanating from the DDC to external
s must be 24VDC or 24VAC originating from a 240V/24V transformer mounted within the DDC
cabinet or in external switchboards and switched by the internal relays within the DDC control
No DDC controller is to switch 240VAC. All 240 VAC switching must be done in a compliant
mechanical Motor Control Centre complying with Australian Standards with relay isolation between
DDC controllers and the mechanical electrical control circuit.
software and passwords (including programming, admi
required to program all BCS and RDC class controllers will be supplied to MUP
software required to make any system configuration, administrative or
including scheduling and trending applications, or engineering parameters
. All software passwords required to program and make
schedules, trends and related program changes will also become the property of MUP
license agreements) required to operate and maintain the system will be
provided with written evidence that MUP is the beneficial end user.
ARCHITECTURE
Each system will consist of a networked communication structure (with TCP/IP on gigabit or fast
Ethernet at its highest level).
connection between BCS’s connected to MACQUARIE UNIVERSITY WAN Data ports must be via
an approved structured LAN cabling system, installed by an MUP qualified cabling contractor.
BACnet/MSTP (where used to link sub-controllers) must use approved EIA-485 cable with properly
grounded and screened twisted pair. Distances must not exceed the EIA-485 specification.
Each BCS will be assigned private corporate class A IP addresses by the MACQUARIE UNIVERSITY IT
tems that support an internal System Manager (such as Chilled Water Manager or Lighting
Manager) are to be monitored through BACnet directly. The BMS should not independently measure
data that is measured more accurately or at higher resolution by the System Manager.
BACnet Routing will be used to link from IP network segments to RS-485 network segments. Each
floor is to contain routers to provide separation between IP backbone and floor networks of
controllers connected to an RS-485 network. A BCS connected to the BACnet/IP network may act as
485 BACnet MS/TP networks, with the limitation that no more than 64
devices be routed through the BCS.
Local Workstations or servers are to comply with BACnet Operator Workstation profile (B
must be connected directly to the MACQUARIE UNIVERSITY WAN using BACnet IP.
All proposed BACnet controllers are to be furnished with a BACnet protocol Implementation
Conformance Statement (PICS see APPENDIX C) for approval, prior to commencing des
All BACnet devices are to conform to a BACnet Standardized Device Profile (Annex L) and be
provided with a list of all BACnet Interoperability Building Blocks supported (BIBBs, Annex K).
Preference will be given to BACnet controllers that are BACNET TESTING LABORATORIES (BTL) listed.
BMS Specifications
10
All installations must be designed for safe operation and maintenance and comply with all WHS
regulations and relevant Australian Standards. All controls emanating from the DDC to external
s must be 24VDC or 24VAC originating from a 240V/24V transformer mounted within the DDC
cabinet or in external switchboards and switched by the internal relays within the DDC control panel.
be done in a compliant
mechanical Motor Control Centre complying with Australian Standards with relay isolation between
and passwords (including programming, administration and
supplied to MUP.
system configuration, administrative or program changes
or engineering parameters
. All software passwords required to program and make future changes to
MUP.
license agreements) required to operate and maintain the system will be
Each system will consist of a networked communication structure (with TCP/IP on gigabit or fast
connection between BCS’s connected to MACQUARIE UNIVERSITY WAN Data ports must be via
an approved structured LAN cabling system, installed by an MUP qualified cabling contractor.
485 cable with properly
485 specification.
Each BCS will be assigned private corporate class A IP addresses by the MACQUARIE UNIVERSITY IT
tems that support an internal System Manager (such as Chilled Water Manager or Lighting
Manager) are to be monitored through BACnet directly. The BMS should not independently measure
em Manager.
485 network segments. Each
floor is to contain routers to provide separation between IP backbone and floor networks of
d to the BACnet/IP network may act as
485 BACnet MS/TP networks, with the limitation that no more than 64
Local Workstations or servers are to comply with BACnet Operator Workstation profile (B-OWS) and
must be connected directly to the MACQUARIE UNIVERSITY WAN using BACnet IP.
All proposed BACnet controllers are to be furnished with a BACnet protocol Implementation
Conformance Statement (PICS see APPENDIX C) for approval, prior to commencing design work.
All BACnet devices are to conform to a BACnet Standardized Device Profile (Annex L) and be
provided with a list of all BACnet Interoperability Building Blocks supported (BIBBs, Annex K).
CNET TESTING LABORATORIES (BTL) listed.
Building Management Systems (B
MUP Building Management Systems (BMS) Design Standard_V1.1
All top level controllers connected to the MACQUARIE UNIVERSITY IP Network must support
BACnet/IP. At least one BACnet B
communicate as if resident on a L
“Multicasting” or BACnet/IP Broadcast Management Device (BBMD).
Building Control Stations (BCS) must comply with BACnet B
MACQUARIE UNIVERSITY WAN.
BACnet controllers used in VAV, FCU, AHU and other application specific applications can use either
Ethernet/IP (BACnetIP), or RS485 (BACnet MS/TP).
For all BACnet controllers the master BACnet addressing scheme is included in APPENDIX A. BACnet
network addresses and controller devices ID’s will be allocated by Macquarie IT.
6.6 FIELD CONTROLLERS
Direct Digital Controls (DDC) will be distributed to the Building Control Stations (BCS) and Remote
Distributed Controllers (RDC) in accordance with best practice distributed processing.
Building Control Stations (BCS) will support B
capability.
Each BCS must support a field point population of no more than 500 points (not including soft
points) where the BCS is involved in the control strategy. Where a BCS is used solely for routing of
points to the server, then this limit is raised to 1,000 points.
Where the BCS is a JACE (Java Application Control Engine), the following ultimate limits will apply for
the population of field points (dependent on the memory available to the JACE):
� JACE2 64MB 200 Points
� JACE2 128MB 500 Points
� JACE6 128MB 600 Points
� JACE6 256MB 1000 Points
Notwithstanding clause 6.6.4 all designs must ensure that CPU usage of JACE devices does not
exceed 80% (including a spare capacity allowance of 20% of field points). This shall be proven
providing a log of the CPU usage at Site Acceptance Testing (SAT).
Java Heap Memory of JACE2 type devices must not fall below 3MB under normal operations. This
affects the selection of JACE2 devices as these have limited Heap Memory. Where Java heap
memory usage causes available memory to fall below 3MB, a JACE6 or above must be specified.
JACE6 should not fall below 8MB.
JACE engineering must be conducted generally in compliance with the Niagara AX platform guide.
The BCS timeclock must be able to sync
feature flexible block DDC programming, memory for standalone trendlogging of all field points at 30
second intervals for 12 hours, and local alarm buffering for up 500 alarms offline from the server.
The BCS must support a variety of subsystem drivers to allow connection to a variety of device
networks based on other protocols including MODBUS, C
No BCS shall be loaded with more than 32 field devices (RDC) without the e
at the system design stage.
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
All top level controllers connected to the MACQUARIE UNIVERSITY IP Network must support
BACnet/IP. At least one BACnet B-BC connected to the MACQUARIE UNIVERSITY VLAN will be able to
communicate as if resident on a LAN, however any BACnet/IP device must support Annex J
“Multicasting” or BACnet/IP Broadcast Management Device (BBMD).
Building Control Stations (BCS) must comply with BACnet B-BC and be connected directly to the
MACQUARIE UNIVERSITY WAN.
rs used in VAV, FCU, AHU and other application specific applications can use either
Ethernet/IP (BACnetIP), or RS485 (BACnet MS/TP).
For all BACnet controllers the master BACnet addressing scheme is included in APPENDIX A. BACnet
troller devices ID’s will be allocated by Macquarie IT.
Direct Digital Controls (DDC) will be distributed to the Building Control Stations (BCS) and Remote
Distributed Controllers (RDC) in accordance with best practice distributed processing.
Building Control Stations (BCS) will support B-BC profile and incorporate sophisticated high level
Each BCS must support a field point population of no more than 500 points (not including soft
points) where the BCS is involved in the control strategy. Where a BCS is used solely for routing of
ver, then this limit is raised to 1,000 points.
Where the BCS is a JACE (Java Application Control Engine), the following ultimate limits will apply for
the population of field points (dependent on the memory available to the JACE):
JACE2 64MB 200 Points
ACE2 128MB 500 Points
JACE6 128MB 600 Points
JACE6 256MB 1000 Points
Notwithstanding clause 6.6.4 all designs must ensure that CPU usage of JACE devices does not
exceed 80% (including a spare capacity allowance of 20% of field points). This shall be proven
providing a log of the CPU usage at Site Acceptance Testing (SAT).
Java Heap Memory of JACE2 type devices must not fall below 3MB under normal operations. This
affects the selection of JACE2 devices as these have limited Heap Memory. Where Java heap
mory usage causes available memory to fall below 3MB, a JACE6 or above must be specified.
JACE6 should not fall below 8MB.
JACE engineering must be conducted generally in compliance with the Niagara AX platform guide.
The BCS timeclock must be able to synchronise with MQU Time Server (Network Time Protocol),
feature flexible block DDC programming, memory for standalone trendlogging of all field points at 30
second intervals for 12 hours, and local alarm buffering for up 500 alarms offline from the server.
The BCS must support a variety of subsystem drivers to allow connection to a variety of device
networks based on other protocols including MODBUS, C-BUS, EIB-KNX, MBUS and LONWORKS.
No BCS shall be loaded with more than 32 field devices (RDC) without the express approval of MUP
BMS Specifications
11
All top level controllers connected to the MACQUARIE UNIVERSITY IP Network must support
BC connected to the MACQUARIE UNIVERSITY VLAN will be able to
AN, however any BACnet/IP device must support Annex J
BC and be connected directly to the
rs used in VAV, FCU, AHU and other application specific applications can use either
For all BACnet controllers the master BACnet addressing scheme is included in APPENDIX A. BACnet
Direct Digital Controls (DDC) will be distributed to the Building Control Stations (BCS) and Remote
Distributed Controllers (RDC) in accordance with best practice distributed processing.
orate sophisticated high level
Each BCS must support a field point population of no more than 500 points (not including soft
points) where the BCS is involved in the control strategy. Where a BCS is used solely for routing of
Where the BCS is a JACE (Java Application Control Engine), the following ultimate limits will apply for
Notwithstanding clause 6.6.4 all designs must ensure that CPU usage of JACE devices does not
exceed 80% (including a spare capacity allowance of 20% of field points). This shall be proven by
Java Heap Memory of JACE2 type devices must not fall below 3MB under normal operations. This
affects the selection of JACE2 devices as these have limited Heap Memory. Where Java heap
mory usage causes available memory to fall below 3MB, a JACE6 or above must be specified.
JACE engineering must be conducted generally in compliance with the Niagara AX platform guide.
hronise with MQU Time Server (Network Time Protocol),
feature flexible block DDC programming, memory for standalone trendlogging of all field points at 30
second intervals for 12 hours, and local alarm buffering for up 500 alarms offline from the server.
The BCS must support a variety of subsystem drivers to allow connection to a variety of device
KNX, MBUS and LONWORKS.
xpress approval of MUP
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Remote Distributed Controllers (RDC) typically support BACnet B
level packaged or compact flexible air
BACnet/MSTP as the field network. Controllers in MS/TP networks must be capable of operation at
data rates up to 76kbs. No more than 48 field points to be connected to any individual RDC.
Each BCS and RDC shall be equipped with non
data, graphics and logs for at least 3 months without an external power source. Battery supply will
maintain full operation of the BCS for at least 5 minutes without external power.
All BCS and RDC must have Web based console port (RJ45 socket
from any location on the network using only a browser. RDC that require special programming
software tools for viewing of field data and basic configuration (clock, BACnet addressing, local
BACnet field variables) are no
Lonworks tunneling on the MACQUARIE UNIVERSITY network (or VLAN) is not permitted. Any
Lonworks device is to wire in FTT10A cabling direct to a BCS or BACnet to Lonworks gateway that will
connect to the MACQUARIE UNIVERSITY network using BACn
Programming must utilize block DDC logic techniques allowing MUP staff to easily read and
understand the operational logic. B
programming objects (such as LOGIC, MATH etc). Block lib
include analog and digital inputs and outputs, Analog and Boolean Variables, and support
enumerated and string variables. A full suite of logic functions, arithmetic functions, control loops,
time schedules, alarm handling, point type conversion, unit conversion, energy management library
must be available in the controller. In addition to block programming library, controllers may offer
scripting language for complex programming but this must only supplement the
capability.
RDC using BACnet MS/TP must support tunneling such that all field points, DDC programs, DDC logic
functions, alarms, trendlogs, control loops, schedules and all other functionality can be access via the
IP network without requiring the use of a laptop directly plugged in to pre
Analogue to Digital resolution must be at least 12bits for Analog Inputs University and 8bits for
Analogue Outputs University. All inputs and outputs shall be protected against
voltages.
RDC with profile B-BC must have flexible IO capacity. Inputs should be capable of configuration as
either Binary Input (BI) or Analog Input (AI).
6.7 MINIMUM FIELD DATA
DESIGNER NOTE: SELECT POINTS ACCORDING TO SYSTE
6.7.1 MECHANICAL SERVICES
6.7.1.1 VAV Controllers
Must support BACnet ASC or AAC profile and must support as a minimum the following variables:
Point Name AI
Occupied Mode
Start/Stop
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
Remote Distributed Controllers (RDC) typically support BACnet B-AAC or B-ASC profiles for lower
level packaged or compact flexible air-conditioning controls are to be based on BACnet/IP or
he field network. Controllers in MS/TP networks must be capable of operation at
data rates up to 76kbs. No more than 48 field points to be connected to any individual RDC.
Each BCS and RDC shall be equipped with non-volatile memory for the protection of us
data, graphics and logs for at least 3 months without an external power source. Battery supply will
maintain full operation of the BCS for at least 5 minutes without external power.
All BCS and RDC must have Web based console port (RJ45 socket) to allow standalone interrogation
from any location on the network using only a browser. RDC that require special programming
software tools for viewing of field data and basic configuration (clock, BACnet addressing, local
BACnet field variables) are not acceptable.
Lonworks tunneling on the MACQUARIE UNIVERSITY network (or VLAN) is not permitted. Any
Lonworks device is to wire in FTT10A cabling direct to a BCS or BACnet to Lonworks gateway that will
connect to the MACQUARIE UNIVERSITY network using BACnet protocols.
Programming must utilize block DDC logic techniques allowing MUP staff to easily read and
understand the operational logic. B-BC, B-AAC and B-ASC must support a common set of core block
programming objects (such as LOGIC, MATH etc). Block libraries must contain all point types. It must
include analog and digital inputs and outputs, Analog and Boolean Variables, and support
enumerated and string variables. A full suite of logic functions, arithmetic functions, control loops,
rm handling, point type conversion, unit conversion, energy management library
must be available in the controller. In addition to block programming library, controllers may offer
scripting language for complex programming but this must only supplement the
RDC using BACnet MS/TP must support tunneling such that all field points, DDC programs, DDC logic
functions, alarms, trendlogs, control loops, schedules and all other functionality can be access via the
quiring the use of a laptop directly plugged in to pre-program the controller.
Analogue to Digital resolution must be at least 12bits for Analog Inputs University and 8bits for
Analogue Outputs University. All inputs and outputs shall be protected against noise and transient
BC must have flexible IO capacity. Inputs should be capable of configuration as
either Binary Input (BI) or Analog Input (AI).
DATA REQUIREMENTS
DESIGNER NOTE: SELECT POINTS ACCORDING TO SYSTEM REQUIREMENT
MECHANICAL SERVICES
Must support BACnet ASC or AAC profile and must support as a minimum the following variables:
BI AO BO AV
R/W
BMS Specifications
12
ASC profiles for lower
conditioning controls are to be based on BACnet/IP or
he field network. Controllers in MS/TP networks must be capable of operation at
data rates up to 76kbs. No more than 48 field points to be connected to any individual RDC.
volatile memory for the protection of user programs,
data, graphics and logs for at least 3 months without an external power source. Battery supply will
) to allow standalone interrogation
from any location on the network using only a browser. RDC that require special programming
software tools for viewing of field data and basic configuration (clock, BACnet addressing, local
Lonworks tunneling on the MACQUARIE UNIVERSITY network (or VLAN) is not permitted. Any
Lonworks device is to wire in FTT10A cabling direct to a BCS or BACnet to Lonworks gateway that will
Programming must utilize block DDC logic techniques allowing MUP staff to easily read and
ASC must support a common set of core block
raries must contain all point types. It must
include analog and digital inputs and outputs, Analog and Boolean Variables, and support
enumerated and string variables. A full suite of logic functions, arithmetic functions, control loops,
rm handling, point type conversion, unit conversion, energy management library
must be available in the controller. In addition to block programming library, controllers may offer
block programming
RDC using BACnet MS/TP must support tunneling such that all field points, DDC programs, DDC logic
functions, alarms, trendlogs, control loops, schedules and all other functionality can be access via the
program the controller.
Analogue to Digital resolution must be at least 12bits for Analog Inputs University and 8bits for
noise and transient
BC must have flexible IO capacity. Inputs should be capable of configuration as
M REQUIREMENT
Must support BACnet ASC or AAC profile and must support as a minimum the following variables:
BV
R/W
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
6.7.1.2 FCU Controllers
Must support BACnet ASC or AAC
Point Name AI BI
Occupied Mode
Start/Stop
Status (CT Relay) R
Space Temp R
Space Setpoint
Supply Temp R
Filter Condition R
Heating Valve
Cooling Valve
EDH
6.7.1.3 AHU (Variable Volume) Controllers
Must support BACnet B-BC or B
Point Name AI
Occupied Mode
Fire Mode
Space Temp R
Supply Temp (from VAV) R
CO2 (IAQ) R
Damper (2)
Air Flow R
Air Flow Setpoint
Min. Heating Airflow
Cooling/heating
Cooling/Heating mode
EDH
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
Must support BACnet ASC or AAC profile and must support as a minimum the following variables:
BI AO BO AV
R/W
R
R/W
R
R/W
R/W
R/W
ontrollers
BC or B-ASC profile and must support as a minimum the following variables:
BI AO BO AV
R/W
R/W
R/W
R/W
R/W
BMS Specifications
13
profile and must support as a minimum the following variables:
BV
R/W
ASC profile and must support as a minimum the following variables:
BV
R/W
R/W
R
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Start/Stop
Status (Pressure Sw) R
Supply Pres SP
Supply Air Pressure R
Supply Fan Speed
Supply Temp Setpoint
Supply Temp (P/Room) R
Return Air Temp
Return Air Humidity
Damper Cycle (OA/RA)
Min OA Damper
Filter Condition R
Heating Valve
Cooling Valve
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
R/W
R/W
R/W
R/W
R/W
R/W
R
R/W
R/W
BMS Specifications
14
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
6.7.1.4 AHU (Constant Volume) Controllers
Must support BACnet B-BC or B
6.7.1.5 Chiller Manager
Must support BACnet B-BC or B
Chiller data must be delivered directly from the Chiller controller via BACnet such that data is
synchronized between BMS and Chiller Manager.
Point Name AI
Cooling Call
ChW Entering Temp R
ChW Leaving Temp R
CW Leaving Temp R
CW Entering Temp R
Amps R
COP R
Load
Point Name AI
Occupied Mode
Start/Stop
Status (Pressure Sw) R
Supply Temp Setpoint
Space Temp R
Return Air Temp
Return Air Humidity
Damper Cycle (OA/RA)
Min OA Damper
Filter Condition R
Heating Valve
Cooling Valve
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
AHU (Constant Volume) Controllers
BC or B-ASC profile and must support as a minimum the following variables:
BC or B-ASC profile and must support as a minimum the following variables.
Chiller data must be delivered directly from the Chiller controller via BACnet such that data is
synchronized between BMS and Chiller Manager. Pumps data may be derived from a VSD.
AI BI AO BO AV
R/W
BI AO BO AV
R/W
R/W
R/W
R/W
R
R/W
R/W
BMS Specifications
15
profile and must support as a minimum the following variables:
profile and must support as a minimum the following variables.
Chiller data must be delivered directly from the Chiller controller via BACnet such that data is
Pumps data may be derived from a VSD.
AV BV
R/W
BV
R/W
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
ChW Setpoint
Evap refrig Pres R
Evap refrig temp R
Cond refrig Pres R
Cond refrig temp R
Comp Disch refrig temp R
Oil Temp R
Oil pres R
CW Water Flow Status
ChW Flow Status
Chiller Operating Status
Chiller Alarm
Chiller Start/Stop
ChW Pump Start
ChW Pump Status (CT
Relay)
ChW Supply Temp R
ChW Return Temp R
CW Pump Start
CW Pump Status (CT Relay)
CW Supply Temp R
CW Return Temp R
CT Fan Start
CT Fan Status
CT Fan speed
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
R/W
R
R
R
R
R/W
R/W
R
R/W
R
R/W
R
R/W
BMS Specifications
16
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
6.7.1.6 Boiler Controller
Must support BACnet B-BC or B
Point Name
Heating Call
HW Entering Temp
HW Leaving Temp
HW Water Flow Status
Boiler Start
Boiler Status
Boiler Fault
6.7.1.7 Weather Station
The system will receive global variables from the local weather station.
Point Name AI
Ambient
Temperature
R
Ambient
Humidity
R
Wind Speed R
Wind Direction R
Cloud Cover R
Dew Point R
Rain Condition R
Temp prediction
Day+1
R
Temp prediction
Day+2
R
Temp prediction
Day+3
R
Temp prediction
Day+4
R
Temp prediction
Day+5
R
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
BC or B-ASC profile and must support as a minimum the following variables.
AI BI AO BO
R
R
R
R/W
R
R
The system will receive global variables from the local weather station.
BI AO BO AV
BMS Specifications
17
ASC profile and must support as a minimum the following variables.
AV BV
R/W
AV BV
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Barometric
Pressure
R
6.7.1.8 Variable Speed Drive
Must be operated via BACnet or Modbus. The following tables indicates the minimum points
required.
Point Name AI
VSD Status
VSD Fault status
Speed (%)
Output Power R
VSD Start/Stop
VSD setpoint
Controlled Input R
6.7.1.9 Hydraulic and Lift Services/Compressed Air
Point Name AI
Booster Pump
Fail
Booster Pump
low pres
Hot Water Pump
Start
Hot Water Pump
Status
LMR Hi Temp
Sump Pump
Status
Sump Pump Fault
Tank Low Level
Tank Extra Low
Level
Tank High Level
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
Must be operated via BACnet or Modbus. The following tables indicates the minimum points
BI AO BO AV
R
R
R/W
R/W
/Compressed Air
BI AO BO AV
R
R
R/W
R
R
R
R
R
R
R
BMS Specifications
18
Must be operated via BACnet or Modbus. The following tables indicates the minimum points
AV BV
R/W
AV BV
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Supply Pressure R
Compressed Air
Fault
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
R
BMS Specifications
19
Building Management Systems (BMS) Design Sta
MUP Building Management Systems (BMS) Design Standard_V1.1
Electrical
Points
AI
Circuit Breaker
Status
Circuit Breaker
Trip
Phase Fail
Room Temp R
Mains Fail
CRAC Status
CRAC Temp R
CRAC Fault
CRAC Force Start
Generator Status
Generator Run
Generator Start
Generator Fault
Generator Fuel
Low
Battery Charger
Fault
3ph Volts R
Current – A
phase
R
Current – B phase R
Current – C phase R
3ph kW R
3ph kWhr R
3ph kVA R
Power Factor R
Frequency R
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
BI AO BO AV
R
R
R
R
R
R
R/W
R
R
R/W
R
R
R
BMS Specifications
20
AV BV
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
6.7.2 LIGHTING
Lighting system integration with the BMS must be considered within the design to allow flexible
programming of lighting functions with overrides and status’s available to the BMS. Where a lighting
management system (based on C
BMS must include the following points.
Where a contactor based hardwired interface is specified, this must be configured to provide group
control as necessary.
Each BMS controlled lighting circuit is to be equipp
the lighting circuit to the BMS.
Each floor is to be provided with separate lighting controls and a labelled BMS override switch to
permit afterhours users access to lighting.
Point Name AI
External Lighting
Foyer Lighting
Corridor Lighting
BMS Override
Stairwells
Toilets
Security
6.7.3 FIRE SERVICES
Fire alarm monitoring is to provided
Where hardwired fire signals control plant, the BMS is required to place automatic controls in a
mode consistent with the presence of a fire alarm.
VESDA and Gas systems are required to be mo
Point Name AI
General Fire
Alarm
FIP Fault
VESDA Fault
VESDA Level 1
VESDA Level 2
VESDA Level 3
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
Lighting system integration with the BMS must be considered within the design to allow flexible
programming of lighting functions with overrides and status’s available to the BMS. Where a lighting
management system (based on C-Bus, DYnalight, KNX, or other type) is specified, the interface to the
BMS must include the following points.
Where a contactor based hardwired interface is specified, this must be configured to provide group
Each BMS controlled lighting circuit is to be equipped with status monitoring to confirm operation of
the lighting circuit to the BMS.
Each floor is to be provided with separate lighting controls and a labelled BMS override switch to
permit afterhours users access to lighting.
BI AO BO AV
R R/W
R R/W
R R/W
R
R R/W
R R/W
R R/W
Fire alarm monitoring is to provided to the BMS such the BMS is capable of operation in “fire” mode.
Where hardwired fire signals control plant, the BMS is required to place automatic controls in a
mode consistent with the presence of a fire alarm.
VESDA and Gas systems are required to be monitored by the BMS.
BI AO BO AV
R
R
R
R
R
R
BMS Specifications
21
Lighting system integration with the BMS must be considered within the design to allow flexible
programming of lighting functions with overrides and status’s available to the BMS. Where a lighting
type) is specified, the interface to the
Where a contactor based hardwired interface is specified, this must be configured to provide group
ed with status monitoring to confirm operation of
Each floor is to be provided with separate lighting controls and a labelled BMS override switch to
AV BV
to the BMS such the BMS is capable of operation in “fire” mode.
Where hardwired fire signals control plant, the BMS is required to place automatic controls in a
AV BV
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Gas Discharge
Gas Fault
Gas Isolate
6.8 FIELD SENSORS AND ACTUATORS
Dampers, actuators (other than VAV actuators), valves, transducers, relays and field instrumentation
are to be based on standard industrial signaling techniques (4
Field signalling 0-10VDC is preferred such that the
6.9 TEMPERATURE SENSORS
Thermocouple (type K or type T) must be specified for critical or wide range temperature
measurement and provided with suitable industrial grade transmitter providing 0
signaling.
RTD may be used for general temperature measurement. May be used to measure to ±0.5°C with
low drift.
Thermistor (NTC 10K, 30K) may be used for space temperature measurement to approximately
±0.3°C with appropriate linearisation. Where applications call for
drift thermistors should not be used without suitable calibration at recommended intervals.
6.10 TEMPERATURE - FLUID
Indirect Immersion sensors are required that penetrate the pipe to no deeper than half the pipe
diameter. Immersion sensors are to be located so that fluid is mixed sufficiently to measure a true
indication of the temperature. Lagging is to be patched properly such that the immersion well is not
exposed to the ambient. Thermo
between the well and the sensor element. Stainless stain wells are required for corrosive liquids such
as seawater or brine.
Strap on type sensors are not acceptable for control applications, other than for general m
For chilled water systems the following accuracy is mandatory, inclusive of transmitter error, with
maximum non-cumulative drift of ±0.1 °C/year (annual field calibration is required for sensors
specified at higher accuracy):
� Outside air Temperature
� Relative Humidity
� Chilled and Condensor Water Temp mains
� Chilled and Condensor Water Temp other
� Water Temp Delta
� Water Flow
� Water Pressure
� Electrical Power
for VSD
Systems (BMS) Design Standard
Design Standard_V1.1
R
R
R
ACTUATORS
Dampers, actuators (other than VAV actuators), valves, transducers, relays and field instrumentation
are to be based on standard industrial signaling techniques (4-20mA or 0-10VDC).
10VDC is preferred such that the signal can be independently measured.
SENSORS
Thermocouple (type K or type T) must be specified for critical or wide range temperature
measurement and provided with suitable industrial grade transmitter providing 0
D may be used for general temperature measurement. May be used to measure to ±0.5°C with
Thermistor (NTC 10K, 30K) may be used for space temperature measurement to approximately
±0.3°C with appropriate linearisation. Where applications call for greater long term stability and low
drift thermistors should not be used without suitable calibration at recommended intervals.
FLUID MEASUREMENT
Indirect Immersion sensors are required that penetrate the pipe to no deeper than half the pipe
diameter. Immersion sensors are to be located so that fluid is mixed sufficiently to measure a true
indication of the temperature. Lagging is to be patched properly such that the immersion well is not
exposed to the ambient. Thermo-conducting paste is to be used to provide an efficient coupling
between the well and the sensor element. Stainless stain wells are required for corrosive liquids such
Strap on type sensors are not acceptable for control applications, other than for general m
For chilled water systems the following accuracy is mandatory, inclusive of transmitter error, with
cumulative drift of ±0.1 °C/year (annual field calibration is required for sensors
specified at higher accuracy):
Temperature ±1.0 °C
Relative Humidity ±5.0 %
Chilled and Condensor Water Temp mains ±0.1 °C
Chilled and Condensor Water Temp other ±0.3 °C
Water Temp Delta-T (where used for load measure) ±0.05 °C
±1 % FSD
±2 % FSD
±1% of reading, 3kHz
BMS Specifications
22
Dampers, actuators (other than VAV actuators), valves, transducers, relays and field instrumentation
signal can be independently measured.
Thermocouple (type K or type T) must be specified for critical or wide range temperature
measurement and provided with suitable industrial grade transmitter providing 0-10vdc or 4-20mA
D may be used for general temperature measurement. May be used to measure to ±0.5°C with
Thermistor (NTC 10K, 30K) may be used for space temperature measurement to approximately
greater long term stability and low
drift thermistors should not be used without suitable calibration at recommended intervals.
Indirect Immersion sensors are required that penetrate the pipe to no deeper than half the pipe
diameter. Immersion sensors are to be located so that fluid is mixed sufficiently to measure a true
indication of the temperature. Lagging is to be patched properly such that the immersion well is not
e used to provide an efficient coupling
between the well and the sensor element. Stainless stain wells are required for corrosive liquids such
Strap on type sensors are not acceptable for control applications, other than for general monitoring.
For chilled water systems the following accuracy is mandatory, inclusive of transmitter error, with
cumulative drift of ±0.1 °C/year (annual field calibration is required for sensors
±1.0 °C
±5.0 %
±0.1 °C
±0.3 °C
±0.05 °C
±1 % FSD
±2 % FSD
±1% of reading, 3kHz
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Mechanical trade is to be directed to fit a Binder type fitting into the pipework adjacent to every
liquid sensor for the purposed of calibration.
Critical temperature sensors are required to be
instrument and the certificate is to be furnished with the commissioning records. This is mandatory
for any liquid sensor participating in BUILDING OR CHILLER LOAD CALCULATIONS, or CHILLER
STAGING DECISIONS.
Temperature – Air measurement
Space temperature sensors are to be installed 1500mm above the finished floor level.
Sensor housings are to be the aspirating type sealed from wall cavities.
Accuracy of space temperature measurement is to be at least ±0.5 °C, w
no more than 0.1 °C/year.
Space temperature sensors generally should not be co
where design required these features. Sensors shall be mounted in a location (generally 1500AFFL)
consistent with accurate space measurement. Buttons shall be mounted on a standalone standard
sized wallplate conveniently close to the entrance door and shall have a momentary press
mechanism labeled “Airconditioning” and a GREEN lamp to denote that airconditioning
RED lamp may to denote that airconditioning is off.
Duct temperature sensors shall be designed to provide average indication across a section of the
duct, not a point measurement.
Accuracy of Duct temperature measurements is to be at least ±0
no more than 0.1 °C/year.
Active sensors are to be 24VAC powered and provide 0
6.10.1 HUMIDITY MEASUREMENT
For non-demanding environments such as occupied spaces, humidity is to be measured at ±5.0 % in
spaces or ducts, non-condensing environment from 0% to 95% RH and temperature of 23°C.
For demanding environments (such as environmental controlled laboratories) humidity is to be
measured at better than ±3.0 %
RH and temperature of 23°C.
Active sensors are to be 24VAC powered and provide 0
6.10.2 FLOW MEASUREMENT
For chilled water and condenser water applications line size magnetic flow meters are required.
Accuracy required is ±1% of reading.
Active sensors are to be 24VAC powered and provide 0
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
Mechanical trade is to be directed to fit a Binder type fitting into the pipework adjacent to every
liquid sensor for the purposed of calibration.
Critical temperature sensors are required to be “field calibrated” to a NATA traceable master
instrument and the certificate is to be furnished with the commissioning records. This is mandatory
for any liquid sensor participating in BUILDING OR CHILLER LOAD CALCULATIONS, or CHILLER
Air measurement
Space temperature sensors are to be installed 1500mm above the finished floor level.
Sensor housings are to be the aspirating type sealed from wall cavities.
Accuracy of space temperature measurement is to be at least ±0.5 °C, with non
Space temperature sensors generally should not be co-located with occupancy override buttons
where design required these features. Sensors shall be mounted in a location (generally 1500AFFL)
with accurate space measurement. Buttons shall be mounted on a standalone standard
sized wallplate conveniently close to the entrance door and shall have a momentary press
mechanism labeled “Airconditioning” and a GREEN lamp to denote that airconditioning
RED lamp may to denote that airconditioning is off.
Duct temperature sensors shall be designed to provide average indication across a section of the
duct, not a point measurement.
Accuracy of Duct temperature measurements is to be at least ±0.3 °C, with non
Active sensors are to be 24VAC powered and provide 0-10vdc or 4-20mA output.
HUMIDITY MEASUREMENT
demanding environments such as occupied spaces, humidity is to be measured at ±5.0 % in
condensing environment from 0% to 95% RH and temperature of 23°C.
For demanding environments (such as environmental controlled laboratories) humidity is to be
measured at better than ±3.0 % in spaces or ducts, non-condensing environmen
RH and temperature of 23°C.
Active sensors are to be 24VAC powered and provide 0-10vdc or 4-20mA output.
FLOW MEASUREMENT - LIQUIDS
For chilled water and condenser water applications line size magnetic flow meters are required.
equired is ±1% of reading.
Active sensors are to be 24VAC powered and provide 0-10vdc or 4-20mA output.
BMS Specifications
23
Mechanical trade is to be directed to fit a Binder type fitting into the pipework adjacent to every
“field calibrated” to a NATA traceable master
instrument and the certificate is to be furnished with the commissioning records. This is mandatory
for any liquid sensor participating in BUILDING OR CHILLER LOAD CALCULATIONS, or CHILLER
Space temperature sensors are to be installed 1500mm above the finished floor level.
ith non-cumulative drift of
located with occupancy override buttons
where design required these features. Sensors shall be mounted in a location (generally 1500AFFL)
with accurate space measurement. Buttons shall be mounted on a standalone standard
sized wallplate conveniently close to the entrance door and shall have a momentary press
mechanism labeled “Airconditioning” and a GREEN lamp to denote that airconditioning is active, a
Duct temperature sensors shall be designed to provide average indication across a section of the
.3 °C, with non-cumulative drift of
demanding environments such as occupied spaces, humidity is to be measured at ±5.0 % in
condensing environment from 0% to 95% RH and temperature of 23°C.
For demanding environments (such as environmental controlled laboratories) humidity is to be
condensing environment from 0% to 100%
For chilled water and condenser water applications line size magnetic flow meters are required.
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
6.10.3 ABSOLUTE PRESSURE OR DIFFERENTIAL PRESSURE
For chilled water and condenser water applications measuring accuracy shall be at least ±0.5% FS
with a maximum pressure of 25bar. Measuring range shall be selected for equal or better than ±2%
of the measuring range.
Pressure devices shall be fitted with valves for isolation, equalization, and draining. Connections
shall be properly plumbed with 6
Active sensors are to be 24VAC powered and provide 0
Mechanical trade is to be directed to fit a binder type fitting into the pipework adjacent to every
liquid sensor for the purposed o
6.10.4 DIFFERENTIAL PRESSURE
For air sensing applications (such as VAV AHU pressure control) accuracy must be at least
and time constant of no greater than 1 second.
Active sensors are to be 24VAC powered and provide 0
6.10.5 PRESSURE SWITCH –
For air monitoring applications (such as
calibration at less than 2.5Pa in 300Pa range and less than 5Pa in 1000Pa range.
Output shall be voltage free contact (rated a
least 1,000,000 operations.
6.10.6 FAN AND PUMP PROVING
Properly calibrated CT Relays shall be used to prove pump or fan motor operation.
6.10.7 OTHER INSTRUMENTATION
Other instrumentation shall be selected
6.10.8 VALVES AND ACTUATORS
Valves for AHU/FCU shall be selected according to design requirements.
For smaller valves characterized ball valves are acceptable.
Butterfly valves are not to be used for critical co
6.10.9 DAMPER ACTUATORS
Damper actuators shall be selected according to requirement. The designer shall specify the power,
torque rating, action, coupling, spring return, limit switches, manual functions and
necessary to provide clear and consistent specification.
6.11 SPECIFICATION OF THE
The local BMS head end computer
Ghz Intel i7 CPU, 1333FSB, 4GB 800Mhz RAM
this PC will be for local configuration, but also for local browsing to the MUP Server located in the
datacenter.
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
ABSOLUTE PRESSURE OR DIFFERENTIAL PRESSURE - LIQUIDS
For chilled water and condenser water applications measuring accuracy shall be at least ±0.5% FS
with a maximum pressure of 25bar. Measuring range shall be selected for equal or better than ±2%
Pressure devices shall be fitted with valves for isolation, equalization, and draining. Connections
shall be properly plumbed with 6mm copper tube coiled for vibration isolation.
Active sensors are to be 24VAC powered and provide 0-10vdc or 4-20mA output.
Mechanical trade is to be directed to fit a binder type fitting into the pipework adjacent to every
liquid sensor for the purposed of calibration.
DIFFERENTIAL PRESSURE – AIR
For air sensing applications (such as VAV AHU pressure control) accuracy must be at least
and time constant of no greater than 1 second.
Active sensors are to be 24VAC powered and provide 0-10vdc or 4-20mA output.
– AIR
applications (such as filter condition monitoring) switching must be capable of
calibration at less than 2.5Pa in 300Pa range and less than 5Pa in 1000Pa range.
Output shall be voltage free contact (rated at 24VAC/VDC, 250VAC 1A resistive) and capable of at
FAN AND PUMP PROVING – CT RELAY
Properly calibrated CT Relays shall be used to prove pump or fan motor operation.
OTHER INSTRUMENTATION
Other instrumentation shall be selected and sized to meet the consulting engineers’ design.
VALVES AND ACTUATORS
Valves for AHU/FCU shall be selected according to design requirements.
For smaller valves characterized ball valves are acceptable.
Butterfly valves are not to be used for critical control applications. Control Valves are to be specified.
DAMPER ACTUATORS
Damper actuators shall be selected according to requirement. The designer shall specify the power,
torque rating, action, coupling, spring return, limit switches, manual functions and
necessary to provide clear and consistent specification.
THE LOCAL HEADEND COMPUTER
S head end computer/server will provide a small footprint tower format (minimum 3
33FSB, 4GB 800Mhz RAM, 500GB HD, DVD writer, Windows 7
this PC will be for local configuration, but also for local browsing to the MUP Server located in the
BMS Specifications
24
LIQUIDS
For chilled water and condenser water applications measuring accuracy shall be at least ±0.5% FSD
with a maximum pressure of 25bar. Measuring range shall be selected for equal or better than ±2%
Pressure devices shall be fitted with valves for isolation, equalization, and draining. Connections
Mechanical trade is to be directed to fit a binder type fitting into the pipework adjacent to every
For air sensing applications (such as VAV AHU pressure control) accuracy must be at least ±3% FSD
switching must be capable of
t 24VAC/VDC, 250VAC 1A resistive) and capable of at
Properly calibrated CT Relays shall be used to prove pump or fan motor operation.
and sized to meet the consulting engineers’ design.
ntrol applications. Control Valves are to be specified.
Damper actuators shall be selected according to requirement. The designer shall specify the power,
torque rating, action, coupling, spring return, limit switches, manual functions and all other as
tower format (minimum 3
500GB HD, DVD writer, Windows 7). The purpose of
this PC will be for local configuration, but also for local browsing to the MUP Server located in the
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Where a fixed PC is provided as a HMI, it shall be 24inch
6.12 SPECIFICATION OF ENCLOSURES,
All BMS equipment is to be enclosed appropriately to provide environmental, electrical, RFI and
mechanical protection, security against unauthorised access and indication of function. Where
controllers and field equipment are fitted externally (without housings
the equipment must be endorsed by the manufacturer for such use.
All equipment enclosures are to be labelled using a robust, long life and permanent labelling syste
Each enclosure must be fitted with a document pocket allowing local storage of key information and
indication of the drawing numbers where the equipment details will be found.
Cables are to be selected and affixed in accordance with Australian standards
recommendations.
All cables within electrical switchboards are to be clearly labelled. BMS cables must be clearly
identifiable on drawings and schedules to ensure easy traceability.
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
Where a fixed PC is provided as a HMI, it shall be 24inch WUXGA widescreen (1920x1080
ENCLOSURES, COLOUR, CABLING AND LABELING
All BMS equipment is to be enclosed appropriately to provide environmental, electrical, RFI and
mechanical protection, security against unauthorised access and indication of function. Where
ers and field equipment are fitted externally (without housings – such as VAV controllers),
the equipment must be endorsed by the manufacturer for such use.
All equipment enclosures are to be labelled using a robust, long life and permanent labelling syste
Each enclosure must be fitted with a document pocket allowing local storage of key information and
indication of the drawing numbers where the equipment details will be found.
Cables are to be selected and affixed in accordance with Australian standards
All cables within electrical switchboards are to be clearly labelled. BMS cables must be clearly
identifiable on drawings and schedules to ensure easy traceability.
BMS Specifications
25
WUXGA widescreen (1920x1080 pixel)
LABELING
All BMS equipment is to be enclosed appropriately to provide environmental, electrical, RFI and
mechanical protection, security against unauthorised access and indication of function. Where
such as VAV controllers),
All equipment enclosures are to be labelled using a robust, long life and permanent labelling system.
Each enclosure must be fitted with a document pocket allowing local storage of key information and
and manufacturers
All cables within electrical switchboards are to be clearly labelled. BMS cables must be clearly
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
7.0 SOFTWARE
These guidelines relate to the detailed
with the MUP Server. The following guidelines are to be used by the BMS contractor to interface and
integrate with the MUP BMS network.
7.1 SECURITY
The BMS will only be accessible offsite via secure VP
Any BMS computer will be defaulted to deny Remote Desktop, Telnet and other remote access
functions unless approved by MUP. The programming and configuration requirements will be carried
out using built in configuration tools direct to the BMS. These wi
access by passwords.
All BMS computers will be equipped with Anti
Building to Building Communication will be restricted by firewalls to permit only the necessary
BACnet application ports to be opened for data to pass between each building or the MUP Server.
Workstations will be provided with Patch and Hotfix management by MUP IT. Auto
Windows systems is to be turned off unless advised by MUP.
All email services will be re-directed via the University SMTP mail service from the MUP BMS server.
These mail accounts will be protected by antivirus and anti
The local BMS will be accessible only by the system maintainer and the MUP. Profiles will be
required on the system to permit a Supervisor (full access), Engineer (Read/Write/Initiate) and User
(Read Only).
7.2 COMMONISED NETWORK
A master device addressing scheme is required for each building that has a BACnet BMS.
The BACnet network numbe
have a unique address from 1 to 64,000)
BACnet Device IDs (BACnet Devices must have a unique ID in the range 0 to 4,000,000)
BACnet device IDs will be numbered again according to Buildin
The BACnet network and device map is available in APPENDIX A.
All network numbers and device IDs will be allocated by MUP.
7.3 POINT NAMING CONVENTION
The naming of IO points is to be kept uniform, AND IS A MAXIMUM of 40 CH
This guide applies to field IO points and Software Points equally.
� Each Building or Facility has up to a 5 character name (W5A, W19F etc).
� Within each Facility, MUP requires clear identification of the ROOM, examples are:
SWPRM, or 203. The maxi
� There is no space between the Building Name and the Room or Area Name:
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
These guidelines relate to the detailed software functionality of each BMS and how this interacts
with the MUP Server. The following guidelines are to be used by the BMS contractor to interface and
integrate with the MUP BMS network.
The BMS will only be accessible offsite via secure VPN.
Any BMS computer will be defaulted to deny Remote Desktop, Telnet and other remote access
functions unless approved by MUP. The programming and configuration requirements will be carried
out using built in configuration tools direct to the BMS. These will be protected from unauthorised
All BMS computers will be equipped with Anti-malware protection as prescribed by MUP IT.
Building to Building Communication will be restricted by firewalls to permit only the necessary
on ports to be opened for data to pass between each building or the MUP Server.
Workstations will be provided with Patch and Hotfix management by MUP IT. Auto
Windows systems is to be turned off unless advised by MUP.
directed via the University SMTP mail service from the MUP BMS server.
These mail accounts will be protected by antivirus and anti-spamming software.
The local BMS will be accessible only by the system maintainer and the MUP. Profiles will be
the system to permit a Supervisor (full access), Engineer (Read/Write/Initiate) and User
NETWORK AND ADDRESSING SCHEME
A master device addressing scheme is required for each building that has a BACnet BMS.
The BACnet network number will be coded to the building group starting at 11 (Bacnet networks
have a unique address from 1 to 64,000)
BACnet Device IDs (BACnet Devices must have a unique ID in the range 0 to 4,000,000)
BACnet device IDs will be numbered again according to Building Group and Building Group Number.
The BACnet network and device map is available in APPENDIX A.
All network numbers and device IDs will be allocated by MUP.
CONVENTION
The naming of IO points is to be kept uniform, AND IS A MAXIMUM of 40 CHARACTERS.
This guide applies to field IO points and Software Points equally.
Each Building or Facility has up to a 5 character name (W5A, W19F etc).
Within each Facility, MUP requires clear identification of the ROOM, examples are:
SWPRM, or 203. The maximum is 5 characters.
There is no space between the Building Name and the Room or Area Name:
Software
26
software functionality of each BMS and how this interacts
with the MUP Server. The following guidelines are to be used by the BMS contractor to interface and
Any BMS computer will be defaulted to deny Remote Desktop, Telnet and other remote access
functions unless approved by MUP. The programming and configuration requirements will be carried
ll be protected from unauthorised
malware protection as prescribed by MUP IT.
Building to Building Communication will be restricted by firewalls to permit only the necessary
on ports to be opened for data to pass between each building or the MUP Server.
Workstations will be provided with Patch and Hotfix management by MUP IT. Auto-update on
directed via the University SMTP mail service from the MUP BMS server.
The local BMS will be accessible only by the system maintainer and the MUP. Profiles will be
the system to permit a Supervisor (full access), Engineer (Read/Write/Initiate) and User
A master device addressing scheme is required for each building that has a BACnet BMS.
r will be coded to the building group starting at 11 (Bacnet networks
BACnet Device IDs (BACnet Devices must have a unique ID in the range 0 to 4,000,000)
g Group and Building Group Number.
ARACTERS.
Each Building or Facility has up to a 5 character name (W5A, W19F etc).
Within each Facility, MUP requires clear identification of the ROOM, examples are:
There is no space between the Building Name and the Room or Area Name:
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
� For example W5A room203 will be W5A203
� After the Building and area locator fields, there will be an underscore then an Equipment
Field. The equipment field may be
designator and the number. For example:
� AHU2.2 = Airhandling Unit 2.2
� VAV11.23 = VAV Box level 11 number 23
� MSB1.1 = Main Switch Board 1.1
� Chiller 1 = Chiller 1
� Boiler 1 = Boiler 2
� BCS1.1 = Building Control Station 1.1
� RDC2.2 = Remote Distributed Controller 2.2
� After the Equipment Field there will an underscore then a 19 character Point descriptor.
Examples are:
� Heating_Setpoint
� Supply_Air_Velocity
� Average_Temp
� Damper_Position
� Fan_Status
� Chiller_Start/Stop
� Return_Air_Enthalpy
� Supply_Air_Diff Pres
� ChW_Pump_Start/stop
� Return_Water_Temp
� Supply_Water_Temp
7.3.1 Each point thereby named:
<Building> <Area><Equipment><Function>
<BBBBBAAAAA_EEEEEEEEE_FFFFFFFFFFFFFFFFFFF>
For example: “W5A203_VAV1.24_Room_Temperat
Room Temperature)
7.4 GRAPHICS
The specification is indicative only.
covered in the specification.
The graphics will be able to start/stop, monitor
system. All BMS systems will be required to provide a simple to use “web based (that is browser
based)” user interface.
All programming functionality (not graphics) is to be provided via the local Web Based Us
(for ultimate fallback in the case of failure of the Server or networks).
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
For example W5A room203 will be W5A203
After the Building and area locator fields, there will be an underscore then an Equipment
Field. The equipment field may be up to 9 Characters. No space between the Equipment
designator and the number. For example:
AHU2.2 = Airhandling Unit 2.2
VAV11.23 = VAV Box level 11 number 23
MSB1.1 = Main Switch Board 1.1
Chiller 1 = Chiller 1
Control Station 1.1
RDC2.2 = Remote Distributed Controller 2.2
After the Equipment Field there will an underscore then a 19 character Point descriptor.
Supply_Air_Velocity
Return_Air_Enthalpy
Supply_Air_Diff Pres
ChW_Pump_Start/stop
Return_Water_Temp
Supply_Water_Temp
Each point thereby named:
<Building> <Area><Equipment><Function>
<BBBBBAAAAA_EEEEEEEEE_FFFFFFFFFFFFFFFFFFF>
“W5A203_VAV1.24_Room_Temperature” (Building W5A room 203, VAV 1.24,
The specification is indicative only. Designers should ensure that any special needs of the
able to start/stop, monitor and adjust BMS control parameters within the
system. All BMS systems will be required to provide a simple to use “web based (that is browser
All programming functionality (not graphics) is to be provided via the local Web Based Us
(for ultimate fallback in the case of failure of the Server or networks).
Software
27
After the Building and area locator fields, there will be an underscore then an Equipment
up to 9 Characters. No space between the Equipment
After the Equipment Field there will an underscore then a 19 character Point descriptor.
ure” (Building W5A room 203, VAV 1.24,
should ensure that any special needs of the project are
BMS control parameters within the
system. All BMS systems will be required to provide a simple to use “web based (that is browser
All programming functionality (not graphics) is to be provided via the local Web Based Used interface
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
In addition to the above requirement, all key graphics for new buildings is to be created in “Niagara
Px” style pages. These pages will be hosted on the MUP Server. MUP
approve hosting of Px pages on dedicated server in larger buildings. Where graphics are locally
hosted, they are to be provided according to MUP Style guide.
All access to graphics will originate from the MUP Server via hype
The BMS contractor will be provided with graphic style sheet templates by MUP that allow to build
graphics within the frame required by MUP, consistent with the master web
graphics template and sample graphics
Local graphics are to be built using this format such that MUP can transfer selected graphics layout
to the MUP BMS Server. Content is to be built within the “useable viewing area”. MUP will create
the titles and navigation panes required for display and navigation on the Server.
Navigation is be provided on a fixed pane as per the master template. It shall always be possible to
navigate forward and back, to the master page and other relevant pages with one clic
of three clicks will be required to any page.
All graphics dimensions are to be based on a 15.4 INCH WIDESCREEN LAPTOP, 1280 x 800 pixel
screen resolution, or for larger graphics, on a 24 INCH WIDESCREEN USXGA format, 1920x1080 pixels
resolution.
Graphics are to be prepared and sized in accordance with the style sheets such that the title,
navigation pane, body and footer do not overlap the specified areas, measured in mm. Once
transferred, the MUP BMS server will learn and map the graphic poin
System Graphics are to be made available in the specified format such that the graphic templates
will be copied to the MUP BMS server (supplied separately to these works).
The Common Interchange format for various elements wi
backgrounds and photographic images are to be supplied in JPEG format
Logos and Moving images are to be supplied in GIF or PNG format
Line diagrams and schematics are to be supplied in TIF format
The Niagara Px statusEffect property sha
key, as shown below shall be made accessible from the main graphic associated with the relevant
building or area.
Figure 1: BMS Key representing standard
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
In addition to the above requirement, all key graphics for new buildings is to be created in “Niagara
Px” style pages. These pages will be hosted on the MUP Server. MUP may (at its sole discretion)
approve hosting of Px pages on dedicated server in larger buildings. Where graphics are locally
hosted, they are to be provided according to MUP Style guide.
All access to graphics will originate from the MUP Server via hyperlinks created by MUP.
The BMS contractor will be provided with graphic style sheet templates by MUP that allow to build
graphics within the frame required by MUP, consistent with the master web-site style sheets. The
graphics template and sample graphics are located in APPENDIX B of this document.
Local graphics are to be built using this format such that MUP can transfer selected graphics layout
to the MUP BMS Server. Content is to be built within the “useable viewing area”. MUP will create
nd navigation panes required for display and navigation on the Server.
Navigation is be provided on a fixed pane as per the master template. It shall always be possible to
navigate forward and back, to the master page and other relevant pages with one clic
of three clicks will be required to any page.
All graphics dimensions are to be based on a 15.4 INCH WIDESCREEN LAPTOP, 1280 x 800 pixel
screen resolution, or for larger graphics, on a 24 INCH WIDESCREEN USXGA format, 1920x1080 pixels
Graphics are to be prepared and sized in accordance with the style sheets such that the title,
navigation pane, body and footer do not overlap the specified areas, measured in mm. Once
transferred, the MUP BMS server will learn and map the graphic point data directly from the BMS.
System Graphics are to be made available in the specified format such that the graphic templates
will be copied to the MUP BMS server (supplied separately to these works).
The Common Interchange format for various elements will be as follows:
backgrounds and photographic images are to be supplied in JPEG format
Logos and Moving images are to be supplied in GIF or PNG format
Line diagrams and schematics are to be supplied in TIF format
The Niagara Px statusEffect property shall be enabled for each point represented on the graphic. A
key, as shown below shall be made accessible from the main graphic associated with the relevant
: BMS Key representing standard Niagara point status.
Software
28
In addition to the above requirement, all key graphics for new buildings is to be created in “Niagara
may (at its sole discretion)
approve hosting of Px pages on dedicated server in larger buildings. Where graphics are locally
rlinks created by MUP.
The BMS contractor will be provided with graphic style sheet templates by MUP that allow to build
site style sheets. The
are located in APPENDIX B of this document.
Local graphics are to be built using this format such that MUP can transfer selected graphics layout
to the MUP BMS Server. Content is to be built within the “useable viewing area”. MUP will create
Navigation is be provided on a fixed pane as per the master template. It shall always be possible to
navigate forward and back, to the master page and other relevant pages with one click. A maximum
All graphics dimensions are to be based on a 15.4 INCH WIDESCREEN LAPTOP, 1280 x 800 pixel
screen resolution, or for larger graphics, on a 24 INCH WIDESCREEN USXGA format, 1920x1080 pixels
Graphics are to be prepared and sized in accordance with the style sheets such that the title,
navigation pane, body and footer do not overlap the specified areas, measured in mm. Once
t data directly from the BMS.
System Graphics are to be made available in the specified format such that the graphic templates
ll be enabled for each point represented on the graphic. A
key, as shown below shall be made accessible from the main graphic associated with the relevant
Niagara point status.
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
The Niagara Px popupEnabled property shall be enabled for each controllable point represented on
the graphic allowing a right mouse click to access the popup control menu (refer example below).
Figure 2: BMS Key
The Niagara Px mouseOver property shall be enabled with the “Highlight” effect for each
controllable point such that all controllable points shall be highlighted as shown in Figure 3.
Figure 2: Example mouseOver effect showing controllable point highlighted when mouse hovers
7.5 SCHEMATIC GRAPHICS
Schematic Graphics will be provided for all items of plant (AHU, FCU, FAN, CHILLER, BOILER etc)
giving a clear system overview for trouble shooting purposes.
Present an accurate drawing representation of the plant, i.e. if the unit is a multi
graphics shall clearly show this. MUP requires a faithful presentation of the plant, with all air paths,
dampers, valves, pipework and other artifacts correctly represented in type, position, orientation
and labeling.
Include all significant aspects or items associated with plant, i.e. economy cycles, dampers, return air
fans, filters, chilled water and heating water coi
Indicate control variables and set points, zone temperatures, on/off/fault status etc to provide clear
present indication of the status and condition of the plant
Include fan status indication via current relay input for AHUs and current
Include time schedules and trending
Include links with appropriate descriptors to floor plans and other elements or connections of the
system
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
The Niagara Px popupEnabled property shall be enabled for each controllable point represented on
the graphic allowing a right mouse click to access the popup control menu (refer example below).
Figure 2: BMS Key representing standard Niagara point status.
The Niagara Px mouseOver property shall be enabled with the “Highlight” effect for each
controllable point such that all controllable points shall be highlighted as shown in Figure 3.
: Example mouseOver effect showing controllable point highlighted when mouse hovers
over..
GRAPHICS
Schematic Graphics will be provided for all items of plant (AHU, FCU, FAN, CHILLER, BOILER etc)
overview for trouble shooting purposes.
Present an accurate drawing representation of the plant, i.e. if the unit is a multi
graphics shall clearly show this. MUP requires a faithful presentation of the plant, with all air paths,
ves, pipework and other artifacts correctly represented in type, position, orientation
Include all significant aspects or items associated with plant, i.e. economy cycles, dampers, return air
fans, filters, chilled water and heating water coils, ductwork etc.
Indicate control variables and set points, zone temperatures, on/off/fault status etc to provide clear
present indication of the status and condition of the plant
Include fan status indication via current relay input for AHUs and current sensing devices for FCUs.
Include time schedules and trending
Include links with appropriate descriptors to floor plans and other elements or connections of the
Software
29
The Niagara Px popupEnabled property shall be enabled for each controllable point represented on
the graphic allowing a right mouse click to access the popup control menu (refer example below).
representing standard Niagara point status.
The Niagara Px mouseOver property shall be enabled with the “Highlight” effect for each
controllable point such that all controllable points shall be highlighted as shown in Figure 3.
: Example mouseOver effect showing controllable point highlighted when mouse hovers
Schematic Graphics will be provided for all items of plant (AHU, FCU, FAN, CHILLER, BOILER etc)
Present an accurate drawing representation of the plant, i.e. if the unit is a multi-zone unit the
graphics shall clearly show this. MUP requires a faithful presentation of the plant, with all air paths,
ves, pipework and other artifacts correctly represented in type, position, orientation
Include all significant aspects or items associated with plant, i.e. economy cycles, dampers, return air
Indicate control variables and set points, zone temperatures, on/off/fault status etc to provide clear
sensing devices for FCUs.
Include links with appropriate descriptors to floor plans and other elements or connections of the
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Include links to tabulated summary information.
7.6 TABULAR GRAPHICS
For a system containing multiple FCUs (or VAV etc), the tabulated information would contain, FCU
number, rooms served, fan enable, fan status, chilled or hot water valve position, supply air
temperature, room set point, room temperature, duct heater status etc.
The amount of information provided per page shall, per table shall be such as to summarise as much
information as possible on one page, yet remain legible. As an example, for a floor containing 10
FCUs it would be expected that this could be contained on one page.
7.7 FLOOR PLANS
Floors plans must use colour legibly to ensure that adequate contrast is present, however zones are
not to be coloured individually. Background colours shall be in accordance with the Style Sheets. The
principle shall be that if there unless the oper
remain discretely coloured. Exceptions may use contrasting colours.
Include the latest version of the MACQUARIE UNIVERSITY floor plans for each new installation or
update
Include the correct room numbers o
WILL THE RESPONSIBILITY OF THE CONTRACTOR TO CHECK THAT THE ROOM NUMBERS ON FLOORS
PLANS CORRESPOND TO CURRENT ARCHITECTURAL AND SPACE PLANNING AND THAT ROOM
NUMBERS MATCH CURRENT RECORDS.
Indicate all FCU and AHU locations and also indicate in a single line format, the ductwork
layout(excluding flexible ductwork) with any terminal reheats, VAV boxes or other items of
significance shall be shown on the single line ductwork run. Hyperlink from eac
to the relevant schematic.
Allow an operator who is skilled in operating a BMS graphical interface and who has a degree of
familiarity with air conditioning systems to be able to quickly and effectively navigate the system
without reference to external mechanical or architectural drawings for clarification.
A link shall be provided on each building home page to the chiller graphics. Each building shall also
contain a box containing the building chilled water supply temperature.
7.8 ALARMS
Refer to document 2. Macquarie University, Sydney, Alarm Handling Subsystem (AHS)
Requirements Specification Enterprise Building Management System (EBMS)
integration of alarms to the Enterprise Building Management System is to be und
7.9 TIME SCHEDULING
The BMS is to provide local time scheduling for all appropriate building services within the building.
Time Schedules must be BACnet compliance and be readily accessible from each plant graphic.
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
Include links to tabulated summary information.
g multiple FCUs (or VAV etc), the tabulated information would contain, FCU
number, rooms served, fan enable, fan status, chilled or hot water valve position, supply air
temperature, room set point, room temperature, duct heater status etc.
formation provided per page shall, per table shall be such as to summarise as much
information as possible on one page, yet remain legible. As an example, for a floor containing 10
FCUs it would be expected that this could be contained on one page.
Floors plans must use colour legibly to ensure that adequate contrast is present, however zones are
not to be coloured individually. Background colours shall be in accordance with the Style Sheets. The
principle shall be that if there unless the operators’ attention is required, each artefact should
remain discretely coloured. Exceptions may use contrasting colours.
Include the latest version of the MACQUARIE UNIVERSITY floor plans for each new installation or
Include the correct room numbers on each room. Where new work or refurbishments are carried, IT
WILL THE RESPONSIBILITY OF THE CONTRACTOR TO CHECK THAT THE ROOM NUMBERS ON FLOORS
PLANS CORRESPOND TO CURRENT ARCHITECTURAL AND SPACE PLANNING AND THAT ROOM
NUMBERS MATCH CURRENT RECORDS.
ate all FCU and AHU locations and also indicate in a single line format, the ductwork
layout(excluding flexible ductwork) with any terminal reheats, VAV boxes or other items of
significance shall be shown on the single line ductwork run. Hyperlink from each AHU or FCU directly
Allow an operator who is skilled in operating a BMS graphical interface and who has a degree of
familiarity with air conditioning systems to be able to quickly and effectively navigate the system
erence to external mechanical or architectural drawings for clarification.
A link shall be provided on each building home page to the chiller graphics. Each building shall also
contain a box containing the building chilled water supply temperature.
Macquarie University, Sydney, Alarm Handling Subsystem (AHS)
Requirements Specification Enterprise Building Management System (EBMS) for details of how the
integration of alarms to the Enterprise Building Management System is to be undertaken.
The BMS is to provide local time scheduling for all appropriate building services within the building.
Time Schedules must be BACnet compliance and be readily accessible from each plant graphic.
Software
30
g multiple FCUs (or VAV etc), the tabulated information would contain, FCU
number, rooms served, fan enable, fan status, chilled or hot water valve position, supply air
formation provided per page shall, per table shall be such as to summarise as much
information as possible on one page, yet remain legible. As an example, for a floor containing 10
Floors plans must use colour legibly to ensure that adequate contrast is present, however zones are
not to be coloured individually. Background colours shall be in accordance with the Style Sheets. The
ators’ attention is required, each artefact should
Include the latest version of the MACQUARIE UNIVERSITY floor plans for each new installation or
n each room. Where new work or refurbishments are carried, IT
WILL THE RESPONSIBILITY OF THE CONTRACTOR TO CHECK THAT THE ROOM NUMBERS ON FLOORS
PLANS CORRESPOND TO CURRENT ARCHITECTURAL AND SPACE PLANNING AND THAT ROOM
ate all FCU and AHU locations and also indicate in a single line format, the ductwork
layout(excluding flexible ductwork) with any terminal reheats, VAV boxes or other items of
h AHU or FCU directly
Allow an operator who is skilled in operating a BMS graphical interface and who has a degree of
familiarity with air conditioning systems to be able to quickly and effectively navigate the system
erence to external mechanical or architectural drawings for clarification.
A link shall be provided on each building home page to the chiller graphics. Each building shall also
Macquarie University, Sydney, Alarm Handling Subsystem (AHS)
for details of how the
ertaken.
The BMS is to provide local time scheduling for all appropriate building services within the building.
Time Schedules must be BACnet compliance and be readily accessible from each plant graphic.
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
The BMS time clock will be linked to the MACQUARIE UNIVERSITY DNS Server for synchronization
with the MACQUARIE UNIVERSITY SNTP server (Simple Network Time Protocol). Global time
synchronization is required where energy management functions require plant s
predictable times. To ensure this occurs, the server will be required to synchronise all systems to a
centralised clock (set to provide GMT+10 hours). The mechanism will source from the Universities
Network Time Protocol (NTP) server and
BMS with this clock.
The server clock will also provide synchronisation to the change of Australian Eastern Standard
Daylight Saving Time. Each system will be expected to accept and support au
at the appointed dates.
The MUP server will provide a global scheduling system, distributed from the Server to the building
systems and then linked down through BACnet to the individual building system.
The calendars time schedules w
information to be sourced from the MUP Server.
7.10 HISTORY AND TRENDLOGGING
Each BCS shall be capable of local trending into non
offline to the Campus WAN.
The BCS must be sized to ensure that field points are sampled at a rate sufficient to permit effective
and efficient control and history logging functions.
Change of Value (COV) reporting is to be implemented where controllers support it. Changes in
measured value or state shall be updated at the Local User Interface generally within 20 seconds.
History archiving will be a function of the MUP server such that trendlogs in the BACnet system
controllers can learned and up
purposes.
Trendlog requirements will be refined in design however the BMS contractor is to allow delivery
trendlogging initially for:
each point actioned or monitored , i.e. room temperatures, chilled and hot water valves,
damper positions, supply air temperature, fan status, fan enable, etc
Chiller and Condensor water temperatures and pressures
Trendlogs will be programmed for selected critical tuning points (supply temp controlled by valves,
chiller temp etc)for two periods
minute intervals and the previous 12 hours in rolling format in 1 minute intervals.
Long term trends (temperature in spaces etc) shall be uplinked to the MUP server for long term
archiving (at least 2 years).
Building Management Systems (BMS) Design Standard
Design Standard_V1.1
The BMS time clock will be linked to the MACQUARIE UNIVERSITY DNS Server for synchronization
with the MACQUARIE UNIVERSITY SNTP server (Simple Network Time Protocol). Global time
synchronization is required where energy management functions require plant s
predictable times. To ensure this occurs, the server will be required to synchronise all systems to a
centralised clock (set to provide GMT+10 hours). The mechanism will source from the Universities
Network Time Protocol (NTP) server and will be distributed to the building by synchronisation of the
The server clock will also provide synchronisation to the change of Australian Eastern Standard
Daylight Saving Time. Each system will be expected to accept and support automatic change of AEST
The MUP server will provide a global scheduling system, distributed from the Server to the building
systems and then linked down through BACnet to the individual building system.
The calendars time schedules within the BMS are to be exposed via BACnet to enable this
information to be sourced from the MUP Server.
TRENDLOGGING
Each BCS shall be capable of local trending into non-volatile memory with capacity for at least 3 days
BCS must be sized to ensure that field points are sampled at a rate sufficient to permit effective
and efficient control and history logging functions.
Change of Value (COV) reporting is to be implemented where controllers support it. Changes in
easured value or state shall be updated at the Local User Interface generally within 20 seconds.
History archiving will be a function of the MUP server such that trendlogs in the BACnet system
controllers can learned and up-linked at interval to the MUP server for archiving and display
Trendlog requirements will be refined in design however the BMS contractor is to allow delivery
each point actioned or monitored , i.e. room temperatures, chilled and hot water valves,
amper positions, supply air temperature, fan status, fan enable, etc
Chiller and Condensor water temperatures and pressures
Trendlogs will be programmed for selected critical tuning points (supply temp controlled by valves,
chiller temp etc)for two periods over a minimum period of 7 previous days in a rolling format in 15
the previous 12 hours in rolling format in 1 minute intervals.
Long term trends (temperature in spaces etc) shall be uplinked to the MUP server for long term
Software
31
The BMS time clock will be linked to the MACQUARIE UNIVERSITY DNS Server for synchronization
with the MACQUARIE UNIVERSITY SNTP server (Simple Network Time Protocol). Global time
synchronization is required where energy management functions require plant starts to occur at
predictable times. To ensure this occurs, the server will be required to synchronise all systems to a
centralised clock (set to provide GMT+10 hours). The mechanism will source from the Universities
will be distributed to the building by synchronisation of the
The server clock will also provide synchronisation to the change of Australian Eastern Standard
tomatic change of AEST
The MUP server will provide a global scheduling system, distributed from the Server to the building
ithin the BMS are to be exposed via BACnet to enable this
volatile memory with capacity for at least 3 days
BCS must be sized to ensure that field points are sampled at a rate sufficient to permit effective
Change of Value (COV) reporting is to be implemented where controllers support it. Changes in
easured value or state shall be updated at the Local User Interface generally within 20 seconds.
History archiving will be a function of the MUP server such that trendlogs in the BACnet system
rver for archiving and display
Trendlog requirements will be refined in design however the BMS contractor is to allow delivery
each point actioned or monitored , i.e. room temperatures, chilled and hot water valves,
Trendlogs will be programmed for selected critical tuning points (supply temp controlled by valves,
days in a rolling format in 15
Long term trends (temperature in spaces etc) shall be uplinked to the MUP server for long term
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
8.0 PLANT CONTROL FUNCTI
DESIGNER NOTE: THIS IS A GUIDE. SELECT PROGRAM STRATEGIES
REQUIREMENT
Global energy management may be implemented by data point passing from a Building Control
Station (programmed for global energy functions) direct to the local BMS, or ultimately from the
MUP Server. Energy management functions are to be coordinated with MUP.
The intent of all control system strategies should be to provide appropriate comfort control
strategies while minimising energy consumption. The University is committed to reducing its
Greenhouse Gas emissions. This will be achieved by a number of methods, which includes, but is not
limited to;
Minimising plant operating hours.
Providing local on/off control in
engaging staff and students to turn plant on and off as necessary. i.e. staff should be encouraged to
turn systems on and off, however an over
Providing for Air quality monitoring where approved by MUP to modulate ventilation within
acceptance/safe limits while minimizing excess heating and cooling operations.
Where VAV systems or zoned systems are installed, allowing control separation of systems to allow
zones to be shut down when not in use and only the occupied zones to have air supply provided. This
would be achieved by providing multiple local start/stop stations and appropriate control.
Providing the widest practicable dead bands on temperature contr
energisation of zone heating or cooling.
All control systems must be furnished with fully programmable setpoints for heating and cooling.
That is, an authorised operator must be able to independently adjust heating and cooling
while ensuring that software does not permit overlapping heating and cooling operations (other
than specifically required – such as for dehumidification operations).
Not operating special purpose rooms during un
training room that is not continuously occupied would be locally started and stopped (or on demand
by a space booking system), while providing over
purpose schedule.
A wall mounted switch should be the primary preferred means of energizing zone FCUs. Where
motion sensing is specified, it must be clearly designed to operate effectively, be walk tested
properly, and be suitable to the function required. When a user enters the room they should
energise the a/c via the wall switch, provided a master schedule permits continous occupancy. Once
energised the FCU should run, say, for one or two hours with a time delay off. Alternatively the
button may be “push to start” and “push to stop” during nor
should be programmable via a simple adjustment on the user graphic interface. A green indicating
light must be illuminated when the plant is running.
Building Management Systems (BMS) Design Standard Plant
Design Standard_V1.1
PLANT CONTROL FUNCTIONS
NOTE: THIS IS A GUIDE. SELECT PROGRAM STRATEGIES ACCORDING TO
Global energy management may be implemented by data point passing from a Building Control
or global energy functions) direct to the local BMS, or ultimately from the
MUP Server. Energy management functions are to be coordinated with MUP.
The intent of all control system strategies should be to provide appropriate comfort control
e minimising energy consumption. The University is committed to reducing its
Greenhouse Gas emissions. This will be achieved by a number of methods, which includes, but is not
Minimising plant operating hours.
Providing local on/off control in lieu of automatic time clock operation where appropriate and
engaging staff and students to turn plant on and off as necessary. i.e. staff should be encouraged to
turn systems on and off, however an over-riding off function should be provided.
for Air quality monitoring where approved by MUP to modulate ventilation within
acceptance/safe limits while minimizing excess heating and cooling operations.
Where VAV systems or zoned systems are installed, allowing control separation of systems to allow
zones to be shut down when not in use and only the occupied zones to have air supply provided. This
would be achieved by providing multiple local start/stop stations and appropriate control.
Providing the widest practicable dead bands on temperature control loops to avoid unnecessary
energisation of zone heating or cooling.
All control systems must be furnished with fully programmable setpoints for heating and cooling.
That is, an authorised operator must be able to independently adjust heating and cooling
while ensuring that software does not permit overlapping heating and cooling operations (other
such as for dehumidification operations).
Not operating special purpose rooms during un-occupied times. For example, a
training room that is not continuously occupied would be locally started and stopped (or on demand
by a space booking system), while providing over-riding off functionality via a timer or special
should be the primary preferred means of energizing zone FCUs. Where
motion sensing is specified, it must be clearly designed to operate effectively, be walk tested
properly, and be suitable to the function required. When a user enters the room they should
energise the a/c via the wall switch, provided a master schedule permits continous occupancy. Once
energised the FCU should run, say, for one or two hours with a time delay off. Alternatively the
button may be “push to start” and “push to stop” during normal occupied hours. The time delay
should be programmable via a simple adjustment on the user graphic interface. A green indicating
light must be illuminated when the plant is running.
Plant Control Functions
32
ACCORDING TO PROJECT
Global energy management may be implemented by data point passing from a Building Control
or global energy functions) direct to the local BMS, or ultimately from the
The intent of all control system strategies should be to provide appropriate comfort control
e minimising energy consumption. The University is committed to reducing its
Greenhouse Gas emissions. This will be achieved by a number of methods, which includes, but is not
lieu of automatic time clock operation where appropriate and
engaging staff and students to turn plant on and off as necessary. i.e. staff should be encouraged to
for Air quality monitoring where approved by MUP to modulate ventilation within
Where VAV systems or zoned systems are installed, allowing control separation of systems to allow
zones to be shut down when not in use and only the occupied zones to have air supply provided. This
would be achieved by providing multiple local start/stop stations and appropriate control.
ol loops to avoid unnecessary
All control systems must be furnished with fully programmable setpoints for heating and cooling.
That is, an authorised operator must be able to independently adjust heating and cooling setpoints,
while ensuring that software does not permit overlapping heating and cooling operations (other
occupied times. For example, a local FCU serving a
training room that is not continuously occupied would be locally started and stopped (or on demand
riding off functionality via a timer or special
should be the primary preferred means of energizing zone FCUs. Where
motion sensing is specified, it must be clearly designed to operate effectively, be walk tested
properly, and be suitable to the function required. When a user enters the room they should
energise the a/c via the wall switch, provided a master schedule permits continous occupancy. Once
energised the FCU should run, say, for one or two hours with a time delay off. Alternatively the
mal occupied hours. The time delay
should be programmable via a simple adjustment on the user graphic interface. A green indicating
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
If an event of known duration is to be held in the room, i.e. for 5 co
the control strategy shall allow either the time clock to be programmed by MUP to provide
continuous running during this period, or the run on timer could be changed to operate for say 4
hours, for morning or afternoon ses
and once in the afternoon. If the time clock has been energised and the room is vacated earlier than
expected, then the users should be able to turn off the FCU when the room is vacated, whethe
FCU is operating under time clock mode or run on timer mode. Pressing the wall button should turn
off the FCU and bring on the red indicating light. The currently activated time schedule should be
over ridden but the next scheduled FCU start should t
turned on before the time schedule has commenced and the delay off has not reached the end of its
time period before the time schedule commences then the FCU should then run under the time
schedule control until the schedule deenergises the FCU or the occupant turns the FCU off on leaving
the room by pressing the toggle button to stop the unit. The air conditioning room switches to be
located near the entrance to the room and grouped close to the lighting s
The above outline describes the intent of the operation of the control system. A similar control
strategy is envisaged for office spaces and classrooms. Where VAV systems are used a similar control
philosophy should be adopted and modified to suit
stop/start points would need to appropriate to the use of the facility. Ideally the control system for
all VAV systems should provide the capability for each VAV box to be energized locally with a local
start/stop push button. i.e. the main AHU should ramp up to meet only the demand of those VAV
boxes that have been locally activated. VAV boxes should default to the closed position when not
energised. A time clock function as described above should also be included. T
attempt to optimise the balance between the complexities of having too many start/stop zones and
the energy efficiencies gained by zoning the system. i.e. if multiple classrooms are on a system they
would be zoned individually, but an o
stop/start station that might control a number of VAVs.
8.1 MISCELLANEOUS COMMENTS
Local exhaust fans (other than toilet exhaust) must all be provided with local manual controls
Economy cycles should be use
All lecture theatres capable of seating 100 or more persons must incorporate the use of enthalpy
control or heat transfer systems on outside air.
All chilled water pumps and large air
speed, variable frequency drives must be capable of being controlled by the BMS.
Solid State heater contactors are mandated to provide analog control in space environments.
Building Management Systems (BMS) Design Standard Plant
Design Standard_V1.1
If an event of known duration is to be held in the room, i.e. for 5 continuous days, 9 am
the control strategy shall allow either the time clock to be programmed by MUP to provide
continuous running during this period, or the run on timer could be changed to operate for say 4
hours, for morning or afternoon sessions - the FCU would need to be energised once in the morning
and once in the afternoon. If the time clock has been energised and the room is vacated earlier than
expected, then the users should be able to turn off the FCU when the room is vacated, whethe
FCU is operating under time clock mode or run on timer mode. Pressing the wall button should turn
off the FCU and bring on the red indicating light. The currently activated time schedule should be
over ridden but the next scheduled FCU start should take control again to start the unit. If the FCU is
turned on before the time schedule has commenced and the delay off has not reached the end of its
time period before the time schedule commences then the FCU should then run under the time
until the schedule deenergises the FCU or the occupant turns the FCU off on leaving
the room by pressing the toggle button to stop the unit. The air conditioning room switches to be
located near the entrance to the room and grouped close to the lighting switches.
The above outline describes the intent of the operation of the control system. A similar control
strategy is envisaged for office spaces and classrooms. Where VAV systems are used a similar control
philosophy should be adopted and modified to suit the circumstances. The number of local
stop/start points would need to appropriate to the use of the facility. Ideally the control system for
all VAV systems should provide the capability for each VAV box to be energized locally with a local
sh button. i.e. the main AHU should ramp up to meet only the demand of those VAV
boxes that have been locally activated. VAV boxes should default to the closed position when not
energised. A time clock function as described above should also be included. T
attempt to optimise the balance between the complexities of having too many start/stop zones and
the energy efficiencies gained by zoning the system. i.e. if multiple classrooms are on a system they
would be zoned individually, but an open plan office area may be provide with say only one
stop/start station that might control a number of VAVs.
COMMENTS
Local exhaust fans (other than toilet exhaust) must all be provided with local manual controls
Economy cycles should be used where ever possible on air handling units.
All lecture theatres capable of seating 100 or more persons must incorporate the use of enthalpy
control or heat transfer systems on outside air.
All chilled water pumps and large air-handling units incorporating VAV boxes must have variable
speed, variable frequency drives must be capable of being controlled by the BMS.
Solid State heater contactors are mandated to provide analog control in space environments.
Plant Control Functions
33
ntinuous days, 9 am – 5 pm , then
the control strategy shall allow either the time clock to be programmed by MUP to provide
continuous running during this period, or the run on timer could be changed to operate for say 4
the FCU would need to be energised once in the morning
and once in the afternoon. If the time clock has been energised and the room is vacated earlier than
expected, then the users should be able to turn off the FCU when the room is vacated, whether the
FCU is operating under time clock mode or run on timer mode. Pressing the wall button should turn
off the FCU and bring on the red indicating light. The currently activated time schedule should be
ake control again to start the unit. If the FCU is
turned on before the time schedule has commenced and the delay off has not reached the end of its
time period before the time schedule commences then the FCU should then run under the time
until the schedule deenergises the FCU or the occupant turns the FCU off on leaving
the room by pressing the toggle button to stop the unit. The air conditioning room switches to be
witches.
The above outline describes the intent of the operation of the control system. A similar control
strategy is envisaged for office spaces and classrooms. Where VAV systems are used a similar control
the circumstances. The number of local
stop/start points would need to appropriate to the use of the facility. Ideally the control system for
all VAV systems should provide the capability for each VAV box to be energized locally with a local
sh button. i.e. the main AHU should ramp up to meet only the demand of those VAV
boxes that have been locally activated. VAV boxes should default to the closed position when not
energised. A time clock function as described above should also be included. The consultant shall
attempt to optimise the balance between the complexities of having too many start/stop zones and
the energy efficiencies gained by zoning the system. i.e. if multiple classrooms are on a system they
pen plan office area may be provide with say only one
Local exhaust fans (other than toilet exhaust) must all be provided with local manual controls
All lecture theatres capable of seating 100 or more persons must incorporate the use of enthalpy
g VAV boxes must have variable
Solid State heater contactors are mandated to provide analog control in space environments.
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
APPENDIX A STANDARDISED METHODO
COMMONISED NETWORK AND ADDRESSING SCHEME
� A master device addressing scheme is required for each building that has a BMS. This is important
because the MUP BMS Server will need to have a unique address for ea
device.
� The BACnet network number will be coded to the building group starting at 11. There are up to
64,000 BACnet network numbers.
� ALL CONTRACTOR REQUIRING BACNET ADDRESS SPACE ALLOCATIONS ARE TO REFER TO MUP IT
FOR NETWORK AND D
� Networks in Building group “1” will be coded 11001 to 11999 (1,000 possible networks)
BACNET DEVICE IDS
� BACnet device IDs will be numbered again according to Building Group and Building Group
Number. There are up to 4,000,000 devices
� So devices in Building Group 1 will be coded 1100001 to 1199999 (100,000 possible devices in each
Building Group/Building Number)
� Within each Building Group/Number there could be several buildings sharing these device IDs. All
device ID’s will be
MAC ADDRESSES
These will be assigned by the contractors, 1 to 128 on each network (they are sometimes set by DIP switches).
MUP will not control BACnet MAC addresses on MS/TP networks. However BACnet/IP MAC addresses are the
IP address so these are controlled by MUP.
IP ADDRESSES
ZZOnly assigned to devices at the MACQUARIE UNIVERSITY IT LAN level (e.g. Building Controllers, Servers, or
Workstations) – these will assigned by MACQUARIE UNIVERSITY IT department.
Building Management Systems (BMS) Design Standard APPENDIX A Standardis
Design Standard_V1.1
STANDARDISED METHODOLOGY FOR BACNET ADDR
COMMONISED NETWORK AND ADDRESSING SCHEME
A master device addressing scheme is required for each building that has a BMS. This is important
because the MUP BMS Server will need to have a unique address for ea
The BACnet network number will be coded to the building group starting at 11. There are up to
64,000 BACnet network numbers.
ALL CONTRACTOR REQUIRING BACNET ADDRESS SPACE ALLOCATIONS ARE TO REFER TO MUP IT
FOR NETWORK AND DEVICE ID ALLOCATIONS.
Networks in Building group “1” will be coded 11001 to 11999 (1,000 possible networks)
BACnet device IDs will be numbered again according to Building Group and Building Group
Number. There are up to 4,000,000 devices IDs.
So devices in Building Group 1 will be coded 1100001 to 1199999 (100,000 possible devices in each
Building Group/Building Number)
Within each Building Group/Number there could be several buildings sharing these device IDs. All
device ID’s will be allocated by MUP.
These will be assigned by the contractors, 1 to 128 on each network (they are sometimes set by DIP switches).
MUP will not control BACnet MAC addresses on MS/TP networks. However BACnet/IP MAC addresses are the
these are controlled by MUP.
Only assigned to devices at the MACQUARIE UNIVERSITY IT LAN level (e.g. Building Controllers, Servers, or
these will assigned by MACQUARIE UNIVERSITY IT department.
Figure 3. MACQUARIE UNIVERSITY BACnet Addressing
APPENDIX A Standardised Methodology for BACnet
addressing
Nov 2015
34
LOGY FOR BACNET ADDRESSING
A master device addressing scheme is required for each building that has a BMS. This is important
because the MUP BMS Server will need to have a unique address for each building and for each
The BACnet network number will be coded to the building group starting at 11. There are up to
ALL CONTRACTOR REQUIRING BACNET ADDRESS SPACE ALLOCATIONS ARE TO REFER TO MUP IT
Networks in Building group “1” will be coded 11001 to 11999 (1,000 possible networks)
BACnet device IDs will be numbered again according to Building Group and Building Group
So devices in Building Group 1 will be coded 1100001 to 1199999 (100,000 possible devices in each
Within each Building Group/Number there could be several buildings sharing these device IDs. All
These will be assigned by the contractors, 1 to 128 on each network (they are sometimes set by DIP switches).
MUP will not control BACnet MAC addresses on MS/TP networks. However BACnet/IP MAC addresses are the
Only assigned to devices at the MACQUARIE UNIVERSITY IT LAN level (e.g. Building Controllers, Servers, or
BACnet Addressing
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
APPENDIX B GRAPHICS STYLE SHEETS
FORMAT
� graphics to be supplied in MUP BMS Server format. Graphics may be loaded in a suitable station
such that MUP can upload the graphics files to the MUP BMS Server. Points will be discovered and
subscribed from the target system into the Server and graphics re
� Size: 15.4 inch Wide Screen Format for simple graphics, 24 inch Wide Screen Format for Complex
Graphics –Vector Graphics preferred for scalability.
� Resolution: 1280 x 800, or 1920 x 1080 (for detailed chiller graphics)
� Usable Area: As defined in General Dimensions sheet
� Backgrounds: White
� header: colours per attached style sheets
� Points – Read Only : Display real time values in 11 Point Tahoma (BLACK) within an LT GREY
BACKGROUND
� Points – Read and Write : Display real time values in 1
OMACQUARIE UNIVERSITYET Border.
� Points – In Alarm: All points in alarm must “Colour and Blink”
YELLOW, acknowledge must stop flashing, Return to Normal must return to nominal colour scheme
� Clock shown in EST/DST 12pt BOLD SANS SERIF (INSET GREY BACKGROUND)to be placed top right
of screen above RED colour bar
� Standard hyperlinks
Page (prepared by others) and link
� Hyperlinking general
Schematics to tables so that user can navigate top to bottom and horizontally in no more than 3
clicks
STYLE SHEET A – FLOOR PLANS
� CAD file input - Floor plans should derive from AUTOCAD architectural Plans
� Details required
unnecessary detail and layers. Sufficient to allow maintainers to identify the
Location and identification of Plant Items
� Room numbers
background) 11 Point Regular Tahoma BLUE
� Air distribution -
rapidly identify which rooms are served and where air is routed)
point lines for “tee
approach should be a
or obscure significant details (such as room numbers, and other useful architectural detail).
� Equipment Positions
hyperlink to detailed schematic
� Room numbers
background) 11 Point Regular Tahoma BLUE
Building Management Systems (BMS) Design Standard APPENDIX B GRAPHICS
Design Standard_V1.1
STYLE SHEETS
to be supplied in MUP BMS Server format. Graphics may be loaded in a suitable station
such that MUP can upload the graphics files to the MUP BMS Server. Points will be discovered and
subscribed from the target system into the Server and graphics re-mapped
Size: 15.4 inch Wide Screen Format for simple graphics, 24 inch Wide Screen Format for Complex
Vector Graphics preferred for scalability.
Resolution: 1280 x 800, or 1920 x 1080 (for detailed chiller graphics)
s defined in General Dimensions sheet
Backgrounds: White
header: colours per attached style sheets
Read Only : Display real time values in 11 Point Tahoma (BLACK) within an LT GREY
Read and Write : Display real time values in 11 Point Tahoma (BLACK) within an
OMACQUARIE UNIVERSITYET Border.
In Alarm: All points in alarm must “Colour and Blink” – Red Alarms RED, Yellow Alarms
YELLOW, acknowledge must stop flashing, Return to Normal must return to nominal colour scheme
ock shown in EST/DST 12pt BOLD SANS SERIF (INSET GREY BACKGROUND)to be placed top right
of screen above RED colour bar
Standard hyperlinks - All graphics to have inbuilt reverse (back arrow ) link, link to Building Front
Page (prepared by others) and link to Campus Map (prepared by others).
Hyperlinking general – hyperlinks are required from Floor Plans to Schematics and tables and from
Schematics to tables so that user can navigate top to bottom and horizontally in no more than 3
Floor plans should derive from AUTOCAD architectural Plans
Details required - Show perimeters, rooms and internal structures, de
unnecessary detail and layers. Sufficient to allow maintainers to identify the
Location and identification of Plant Items
Room numbers - assigned by University Space planning (prefer direct from original AUTOCAD
background) 11 Point Regular Tahoma BLUE
- Show basic single line duct or pipework layout (sufficient to allow maintainers to
rapidly identify which rooms are served and where air is routed) – 4 point lines for main ducts, 2
point lines for “tee-offs”, lines to be colour coded to MUP approved scheme AHU. A commonsense
approach should be applied to ensure that colour cluttering does not reduce clarity of floor plans
or obscure significant details (such as room numbers, and other useful architectural detail).
Equipment Positions - Show positions of VAV’s, FCU, and AHU (and other major plant
hyperlink to detailed schematic
Room numbers - assigned by University Space planning (prefer direct from original AUTOCAD
background) 11 Point Regular Tahoma BLUE
APPENDIX B GRAPHICS STYLE SHEETS
Nov 2015
35
to be supplied in MUP BMS Server format. Graphics may be loaded in a suitable station
such that MUP can upload the graphics files to the MUP BMS Server. Points will be discovered and
mapped to the Server Points.
Size: 15.4 inch Wide Screen Format for simple graphics, 24 inch Wide Screen Format for Complex
Read Only : Display real time values in 11 Point Tahoma (BLACK) within an LT GREY
1 Point Tahoma (BLACK) within an
Red Alarms RED, Yellow Alarms
YELLOW, acknowledge must stop flashing, Return to Normal must return to nominal colour scheme
ock shown in EST/DST 12pt BOLD SANS SERIF (INSET GREY BACKGROUND)to be placed top right
All graphics to have inbuilt reverse (back arrow ) link, link to Building Front
to Campus Map (prepared by others).
hyperlinks are required from Floor Plans to Schematics and tables and from
Schematics to tables so that user can navigate top to bottom and horizontally in no more than 3
Floor plans should derive from AUTOCAD architectural Plans
Show perimeters, rooms and internal structures, de-cluttered and remove
unnecessary detail and layers. Sufficient to allow maintainers to identify the ROOM Location, Plant
assigned by University Space planning (prefer direct from original AUTOCAD
yout (sufficient to allow maintainers to
4 point lines for main ducts, 2
approved scheme AHU. A commonsense
pplied to ensure that colour cluttering does not reduce clarity of floor plans
or obscure significant details (such as room numbers, and other useful architectural detail).
Show positions of VAV’s, FCU, and AHU (and other major plant) with
assigned by University Space planning (prefer direct from original AUTOCAD
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
� Air distribution -
rapidly identify which rooms are served and where air is routed)
point lines for “tee
approach should be applied to ensure that col
or obscure significant details (such as room numbers, and other useful architectural detail).
� Equipment Positions
hyperlink to detai
� Colour Coding - Colour code to show zoning (Common colour for AHU and associated Zone Labels)
� Hyperlinking - Show hyperlinked list of Plant on left hand navigation pane for quick navigation
� Real time values
place temperature values in clearly labelled and colour coded table below floor plan
� Font - Temp values to be in 11 Point Tahoma, INSET Border
TABLES ARE REQUIRED TO STYLE SHEETS B, C, D AND E
� Use Panes to show physical schematic, with Panes behind for detailed controls and Logs
� User standard graphical objects by preference, unless it is necessary to represent a unique system
or object clearly by other means. Any graphic design objec
supplied in PNG format. Photographic material must be provided in JPEG format.
� If Photographic or schematic depiction of equipment is used
graphics are not available, provide only a g
� Three dimensional pipe is not required (pipes may use 4 pt lines). Colours
(RGB0,0,255); CHWRet Lt Blue (RGB128,128,255); HWFlow Dk Red (RGB192,0,0);HWRet Lt Red
(RGB255,64,64); CWFlow Dk Green (RGB0,128
� Pipe corners must join accurately, if necessary to improve readability headers with blanking ends
can be shown.
� Labelling must clearly indicate where piping joins to other pages and hyperlinks provided.
� Equipment to be lab
� Display value tags (or labels) to use 11pt Tahoma BOLD BLACK
� Real Time Data show below equipment or to the right of labels (11 pt Tahoma REGULAR black
INSET for display only, O
use Labels where it is clear to the user that real time data is associated with plant and the function
of the real data is clearly evident.
� Status may be shown in “Animation”. If animat
display (unless essential to prove or confirm function)
� Real Time data “ display states” to be self explanatory (ie Filter “Dirty”, not Filter Dirty “Active”)
where possible
� De clutter and simplify where po
exceptions clearly)
� Fail to start alarms should show a RED alarm “colour and blink” on the Start/Stop control display
point
� Faults should show clearly as “Fault” or “Normal”
� Start/Stop command o
READ/WRITE)
� Status of equipment (where animation not used) should be shown as “Running” or “Stopped”
Building Management Systems (BMS) Design Standard APPENDIX B GRAPHICS
Design Standard_V1.1
- Show basic single line duct or pipework layout (sufficient to allow
rapidly identify which rooms are served and where air is routed) – 4 point lines for main ducts, 2
point lines for “tee-offs”, lines to be colour coded to MUP approved scheme AHU. A commonsense
approach should be applied to ensure that colour cluttering does not reduce clarity of floor plans
or obscure significant details (such as room numbers, and other useful architectural detail).
Equipment Positions - Show positions of VAV’s, FCU, and AHU (and other major plant) with
hyperlink to detailed schematic
Colour code to show zoning (Common colour for AHU and associated Zone Labels)
Show hyperlinked list of Plant on left hand navigation pane for quick navigation
Real time values -Temperature values may be overlaid on diagram (if space permits). Alternatively
place temperature values in clearly labelled and colour coded table below floor plan
Temp values to be in 11 Point Tahoma, INSET Border
TABLES ARE REQUIRED TO STYLE SHEETS B, C, D AND E – PLANT SCHEMATICS
Use Panes to show physical schematic, with Panes behind for detailed controls and Logs
graphical objects by preference, unless it is necessary to represent a unique system
or object clearly by other means. Any graphic design objects (line or diagrammatic art) must be
supplied in PNG format. Photographic material must be provided in JPEG format.
If Photographic or schematic depiction of equipment is used – it must be accurate. If accurate
graphics are not available, provide only a generally indicative functional object.
Three dimensional pipe is not required (pipes may use 4 pt lines). Colours
(RGB0,0,255); CHWRet Lt Blue (RGB128,128,255); HWFlow Dk Red (RGB192,0,0);HWRet Lt Red
(RGB255,64,64); CWFlow Dk Green (RGB0,128,0); CWRet Lt Green (RGB0,192,0).
Pipe corners must join accurately, if necessary to improve readability headers with blanking ends
Labelling must clearly indicate where piping joins to other pages and hyperlinks provided.
Equipment to be labelled above graphic object (e.g. pump or fan etc) in 11 pt Tahoma BOLD Black
Display value tags (or labels) to use 11pt Tahoma BOLD BLACK
Real Time Data show below equipment or to the right of labels (11 pt Tahoma REGULAR black
INSET for display only, OMACQUARIE UNIVERSITYET for user input or control). It is not necessary to
use Labels where it is clear to the user that real time data is associated with plant and the function
of the real data is clearly evident.
Status may be shown in “Animation”. If animation is used, do not include status field point on
display (unless essential to prove or confirm function)
Real Time data “ display states” to be self explanatory (ie Filter “Dirty”, not Filter Dirty “Active”)
De clutter and simplify where possible allowing quick identification of problems (ie show the
exceptions clearly)
Fail to start alarms should show a RED alarm “colour and blink” on the Start/Stop control display
Faults should show clearly as “Fault” or “Normal”
Start/Stop command of equipment should be indicated as “Start” or “Stop” (OUTPUTS if
Status of equipment (where animation not used) should be shown as “Running” or “Stopped”
APPENDIX B GRAPHICS STYLE SHEETS
Nov 2015
36
Show basic single line duct or pipework layout (sufficient to allow maintainers to
4 point lines for main ducts, 2
offs”, lines to be colour coded to MUP approved scheme AHU. A commonsense
our cluttering does not reduce clarity of floor plans
or obscure significant details (such as room numbers, and other useful architectural detail).
Show positions of VAV’s, FCU, and AHU (and other major plant) with
Colour code to show zoning (Common colour for AHU and associated Zone Labels)
Show hyperlinked list of Plant on left hand navigation pane for quick navigation
overlaid on diagram (if space permits). Alternatively
place temperature values in clearly labelled and colour coded table below floor plan
Use Panes to show physical schematic, with Panes behind for detailed controls and Logs
graphical objects by preference, unless it is necessary to represent a unique system
ts (line or diagrammatic art) must be
supplied in PNG format. Photographic material must be provided in JPEG format.
it must be accurate. If accurate
enerally indicative functional object.
Three dimensional pipe is not required (pipes may use 4 pt lines). Colours -CHWFlow Blue
(RGB0,0,255); CHWRet Lt Blue (RGB128,128,255); HWFlow Dk Red (RGB192,0,0);HWRet Lt Red
,0); CWRet Lt Green (RGB0,192,0).
Pipe corners must join accurately, if necessary to improve readability headers with blanking ends
Labelling must clearly indicate where piping joins to other pages and hyperlinks provided.
elled above graphic object (e.g. pump or fan etc) in 11 pt Tahoma BOLD Black
Real Time Data show below equipment or to the right of labels (11 pt Tahoma REGULAR black
ET for user input or control). It is not necessary to
use Labels where it is clear to the user that real time data is associated with plant and the function
ion is used, do not include status field point on
Real Time data “ display states” to be self explanatory (ie Filter “Dirty”, not Filter Dirty “Active”)
ssible allowing quick identification of problems (ie show the
Fail to start alarms should show a RED alarm “colour and blink” on the Start/Stop control display
s “Start” or “Stop” (OUTPUTS if
Status of equipment (where animation not used) should be shown as “Running” or “Stopped”
Building Management Systems (BMS) Design Sta
MUP Building Management Systems (BMS) Design Standard_V1.1
� System Enable should be shown as “Enabled” or “Disabled”
� VSD control signals should be sho
� Control loops may be shown as dotted lines (LT Blue) indicating control action between Controlling
Variable and Output. Setpoint may be shown with Label “SP” (11 Pt Tahoma Bold Black) under the
Controlled Variable
STYLE SHEETS F – TABLES
� display group data such as all VAV’s attached to a specific zone
� Hyperlinks to be created to allow navigation directly from relevant floors plans or Plant
� Tables to include all operational variables as required to clearly indicate “at a
position of temperatures, modes, setpoints, valves, dampers, and all other real time values as
requires vertically aligned to permit maintainers easy review of all equipment
� All table data is to be reference to Room Numbers and clearl
required)
Building Management Systems (BMS) Design Standard APPENDIX B GRAPHICS
Design Standard_V1.1
System Enable should be shown as “Enabled” or “Disabled”
ol signals should be shown as “ value %” under the equipment
Control loops may be shown as dotted lines (LT Blue) indicating control action between Controlling
Variable and Output. Setpoint may be shown with Label “SP” (11 Pt Tahoma Bold Black) under the
Controlled Variable
display group data such as all VAV’s attached to a specific zone
Hyperlinks to be created to allow navigation directly from relevant floors plans or Plant
Tables to include all operational variables as required to clearly indicate “at a
position of temperatures, modes, setpoints, valves, dampers, and all other real time values as
requires vertically aligned to permit maintainers easy review of all equipment
All table data is to be reference to Room Numbers and clearly colour coded to zone (where
APPENDIX B GRAPHICS STYLE SHEETS
Nov 2015
37
“ value %” under the equipment
Control loops may be shown as dotted lines (LT Blue) indicating control action between Controlling
Variable and Output. Setpoint may be shown with Label “SP” (11 Pt Tahoma Bold Black) under the
Hyperlinks to be created to allow navigation directly from relevant floors plans or Plant
Tables to include all operational variables as required to clearly indicate “at a glance” the relative
position of temperatures, modes, setpoints, valves, dampers, and all other real time values as
requires vertically aligned to permit maintainers easy review of all equipment
y colour coded to zone (where
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard Design Standard_V1.1
8.1.1 SIZING AT 1280X800 (STANDARD WXGA LAPTOP)
Style Sheet – Main Map
Page Title (White on Blue/aqua vignette, 16Pt Sans Serif) Home Back
Logo
Nav
Bar
(Charcoal on
white
11Pt Sans Serif)
60mm
ent Systems (BMS) Design Standard
Design Standard_V1.1
SIZING AT 1280X800 (STANDARD WXGA LAPTOP)
(White on Blue/aqua vignette, 16Pt Sans Serif) Home Back
Browser toolbars
Reserved Title Area
330mm (approx)
50m
m16
0mm
270mm (approx)
APPENDIX B GRAPHICS STYLE SHEETS
Nov 2015Nov 2015
38
210m
m (a
ppro
x)
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Style Sheet A – Floor Plans
Building Management Systems (BMS) Design Standard
APPENDIX B GRAPHICS STYLE SHEETS
Nov 2015
39
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
8.1.2 Style Sheet C – Plant Schematics
Building Management Systems (BMS) Design Standard
Plant Schematics - Piped (large scale)
APPENDIX B GRAPHICS STYLE SHEETS
Nov 2015
40
Building Management Systems (BMS) Design Standard
MUP Building Management Systems (BMS) Design Standard_V1.1
Style Sheet F – Tables
Building Management Systems (BMS) Design Standard
APPENDIX B GRAPHICS STYLE SHEETS
Nov 2015
41
Building Management Systems (BMS) Design Standard
APPENDIX C - Protocol Implementation Conformance Statement (Normative)
MUP Building Management Systems (BMS) Design Standard_V1.1 43
APPENDIX C - PROTOCOL IMPLEMENTATION CONFORMANCE STATEMENT
(NORMATIVE)
(This annex is part of the BACnet Standard and is required for its use.)
BACnet Protocol Implementation Conformance Statement
Date: ____________________________
Vendor Name: Product Name:
Product Model Number:
Application Software Version: _________ Firmware Revision: ________ BACnet Protocol Revision: _____________
Product Description:
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
______________________________________________________________________________________
________________________________________________________
BACnet Standardized Device Profile (Annex L):
� BACnet Operator Workstation (B-OWS)
� BACnet Advanced Operator Workstation (B-AWS)
� BACnet Operator Display (B-OD)
� BACnet Building Controller (B-BC)
� BACnet Advanced Application Controller (B-AAC)
� BACnet Application Specific Controller (B-ASC)
� BACnet Smart Sensor (B-SS)
� BACnet Smart Actuator (B-SA)
List all BACnet Interoperability Building Blocks Supported (Annex K): ______________________________________ ____________________________________________________________________________________________________
_
Building Management Systems (BMS) Design Standard
APPENDIX C - Protocol Implementation Conformance Statement (Normative)
MUP Building Management Systems (BMS) Design Standard_V1.1 44
SEGMENTATION CAPABILITY:
� Able to transmit segmented messages Window Size
� Able to receive segmented messages Window Size
STANDARD OBJECT TYPES SUPPORTED:
An object type is supported if it may be present in the device. For each standard Object Type
supported provide the following data:
1) Whether objects of this type are dynamically creatable using the CreateObject service
2) Whether objects of this type are dynamically deletable using the DeleteObject service
3) List of the optional properties supported
4) List of all properties that are writable where not otherwise required by this standard
5) List of all properties that are conditionally writable where not otherwise required by this standard
6) List of proprietary properties and for each its property identifier, datatype, and meaning
7) List of any property range restrictions
DATA LINK LAYER OPTIONS:
� BACnet IP, (Annex J) ____________
� BACnet IP, (Annex J), Foreign Device ____________
� ISO 8802-3, Ethernet (Clause 7) ____________
� ATA 878.1, 2.5 Mb. ARCNET (Clause 8) ____________
� ATA 878.1, EIA-485 ARCNET (Clause 8), baud rate(s) ____________
� MS/TP master (Clause 9), baud rate(s):
� MS/TP slave (Clause 9), baud rate(s):
� Point-To-Point, EIA 232 (Clause 10), baud rate(s):
� Point-To-Point, modem, (Clause 10), baud rate(s):
� LonTalk, (Clause 11), medium: __________
� BACnet/ZigBee (ANNEX O) ____________
Building Management Systems (BMS) Design Standard
APPENDIX C - Protocol Implementation Conformance Statement (Normative)
MUP Building Management Systems (BMS) Design Standard_V1.1 45
� Other:
DEVICE ADDRESS BINDING:
Is static device binding supported? (This is currently necessary for two-way communication with
MS/TP slaves and certain other devices.) � Yes � No
NETWORKING OPTIONS:
� Router, Clause 6 - List all routing configurations, e.g., ARCNET-Ethernet, Ethernet-MS/TP, etc.
� Annex H, BACnet Tunneling Router over IP
� BACnet/IP Broadcast Management Device (BBMD)
�Does the BBMD support registrations by Foreign Devices? � Yes � No
�Does the BBMD support network address translation? � Yes � No
NETWORK SECURITY OPTIONS:
� Non-secure Device - is capable of operating without BACnet Network Security
� Secure Device - is capable of using BACnet Network Security (NS-SD BIBB)
� Multiple Application-Specific Keys:
� Supports encryption (NS-ED BIBB)
� Key Server (NS-KS BIBB)
CHARACTER SETS SUPPORTED:
Indicating support for multiple character sets does not imply that they can all be supported
simultaneously.
� ISO 10646 (UTF-8) � IBM
/Microsoft
DBCS� ISO 8859-1
� ISO 10646 (UCS-2) � ISO 10646 (UCS-4) � JIS X 0208
If this product is a communication gateway, describe the types of non-BACnet
equipment/networks(s) that the gateway supports:
__________________________________________________________________________________
_____________
__________________________________________________________________________________
_____________