1. ASHRAE
4/16/10
BAS for Large Campuses
Jeff Lucas, C.E.M
Rocky Mountain Energy Services

2. Systems Integration at it’s Finest

3. BACnet at DCSD
 58 of the district’s 70 buildings contain BACnet
devices
 The BACnet network consists of over 25,000+
hardwired points and 102,000+ BACnet objects
 10 different manufacturers’
 Devices include BAS, VFDs, energy meters,
chillers, condensing boilers and lighting controls

4. Why BACnet is Suited for Multiple
Building Campuses
• BACnet is very scalable
• BACnet/IP allows for the use of existing IT infrastructure
• Specifically designed for BAS applications
• BACnet’s future is determined by the industry including
end users

5. Advantages of BACnet
 Competitive bidding
 Centralized scheduling of building systems
 Centralized alarm management
 Comprehensive data logging
 Web access to control network functions
 Centralized control network management
 Self discovering network
 No need for gateways to facilitate communication over
an IP network

6. Multiple Users
Offsite Contractors Mobile Devices
On Call Staff
Internet / VPN Internet / VPN
BACnet web server
BACnet/IP BACnet/IP
Building DDC Technicians Building Building Any Internal PC
device(s) Engineers Occupants

7. BACnet is Continually Improving
Current BACnet Working Groups
 AP-WG : Applications
 IP-WG : Internet Protocol
 LA-WG : Lighting Applications
 LSS-WG : Life Safety and Security
 MS/TP-WG : Master-Slave/Token-Passing
 NS-WG : Network Security
 OS-WG : Objects and Services
 SG-WG : Smart Grid
 TI-WG : Testing and Interoperability
 WN-WG : Wireless Networking
 XML-WG : XML Applications

8. What are the Possibilities?
 Live utility data from BACnet metering
 Automatic comparisons of historical energy data
 Real time energy use comparisons of prototypical buildings
 Demand response
 One click shutdown of entire campus
 Work order system integration
 Automated building use scheduling
 Integration with weather forecast data
 Real time data feeds to building occupants
 Automatically generated custom reports (manual overrides)
 Documentation integration

9. Tailoring BACnet to the End
User

10. What Features Does the End User
Desire?
 Who will be using the system?
 Will integration be required?
 Are there existing legacy proprietary systems?
 Will Web graphics be necessary?
 What devices will be accessing the system?
 What programming language is preferred?

11. Determine the Necessary Level of
Interoperability
 What points will the end user want to
override
 Schedules and calendars
 PID loops
 Type of routing required
 Type existing network
 Creation and deletion of points
 Will BTL testing be required

12. Selecting a Operator Work Station
(OWS)
 User friendly interface
 Web graphics
 Graphics library and graphics editor
 Multiple users
 System tree organization
 Custom views and point filtering
 Alarm filtering
 System Backups
 BTL Listed?

13. NOW WHAT?

14. BACnet PICS Statement
BACnet Protocol Implementation
Conformance Statement
Annex-A rev 2010-02-11
BTL Listing
Example BTL Listing

15. Customized Live Testing
 Testing must be developed around the end
users needs
 Vendors should demonstrate their product
using local representation
 Test should include local vendor evaluation
including reference projects and customer
references

16. Recommended Testing Objectives
 Determine what objects the manufacturer supports
 Establish which BACnet objects the manufacturer
supports and to what degree a third party BACnet OWS
can edit those objects.
 Verify trending capability
 Test alarms (events)
 Evaluate manufactures’ OWS and software package
 Verify BACnet routing capabilities

17. Example Test
DCSD Vendor interviews

18. Specifications Should Include
 Network architecture requirements
 Points lists
 Alarm requirements
 Address schemes
 Naming conventions
 Third party device integration requirement

19. Typical Low Cost BACnet Network
Architecture
Main OWS
BACnet/IP
BACnet Router
BACnet MS/TP
Chiller Plant
Controller
AHU Controller
VAV Controller
Third Party Device

20. Critical Application BACnet Network
Architecture
Main OWS
BACnet/IP
BACnet Router
BACnet Ethernet
Chiller Plant
AHU Controller Controller
BACnet MS/TP
Third Party
VAV Controller Device
VAV Controller BACnet MS/TP

21. Naming Conventions
 Beware some manufacturers limit characters to
unreasonable lengths
 Decide on acronyms (exp. DAT vs SAT)
 Include building abbreviation in ALL point names
 Include naming convention in control
specifications
 Every alarm MUST include building name or
abbreviation
 Example names:
BLDG#1 AHU#1 SF STATUS
BLDG#2 CHLR#1 CHWS TEMP

22. Address Scheme
Building #1
Main OWS
BACnet/IP
BACnet Router
(10000)
Ethernet Net#10 BACnet Ethernet
Chiller AHU
Boiler Controller Controller Controller
(10100) (10200) (10300)
VAV
Chiller BACnet MS/TP
Controller
Interface
(10301)
(19001)
VAV
Controller
(10302)
MS/TP Net#1020 MS/TP Net#1030
BACnet Device IDs must be unique Network #s limited to 65,534

23. Points List
 Include a points list in every BAS specification
 Specify in points list what points are to be
displayed in graphics
 Points list should include what points shall be
alarmed (events)
 Points list should include alarm types (event
classes)
 Points list should also include any trending
requirements

24. Example Points List
Exp Point List.pdf

25. Equipment Integration
 Many manufactures are offering BACnet
interfaces (lighting, VFDs, chillers, boilers
ect.)
 Many of these interfaces are protocol
gateways
 Beware! Ask to see a demo
 Possible alarm issues
 Many interfaces are not BTL tested

26. Example of Chiller Integration

27. CRAC Unit Integration

28. Example of Power Meter Integration

30. Dealing With IT Staff
 Involve IT early
 Recommend control system be placed on a VLAN
 Advise IT department of possible traffic issues
 Ask for IP addresses early
 Have IT staff designate IP address range for each
building
 Decide on security measures and system
monitoring

31. Lessons Learned
 Not all BACnet control systems are created equal
 Thoroughly plan prior to implementation
 Hire a consultant to help develop an initial plan
and specification
 Prequalify all vendors
 Control systems are only as good as their local
representation
 System commissioning should include verifying
correct BACnet configuration details

32. Questions?
Thank You!