specifying lighting and building management systems … filebacnet and lighting history • did you...
TRANSCRIPT
ExponationAIA Provider Number: 70119700
Specifying Lighting and Building
Management Systems (BMS) with
BACnet, today and in the futureLEDSSMW16-S#11
Scott Ziegenfus, Hubbell Lighting11.15.16
Credit(s) earned on completion of
this course will be reported to AIA
CES for AIA members.
Certificates of Completion for both
AIA members and non-AIA
members are available upon
request.
This course is registered with AIA
CES for continuing professional
education. As such, it does not
include content that may be
deemed or construed to be an
approval or endorsement by the
AIA of any material of construction
or any method or manner of
handling, using, distributing, or
dealing in any material or product._______________________________________
Questions related to specific materials, methods,
and services will be addressed at the conclusion
of this presentation.
This session will cover the fundamentals of
BACnet, including a primer on BACnet
terminology, the items needed to specify for
BMS interoperability and conformance to the
BACnet standard. It will elaborate on the new
items developed by the Lighting Application
Working Group within BACnet to make
specifying lighting and BMS Integration easier
and what's next in BACnet standards
development for lighting.
Course
Description
Learning
Objectives
• Learn enough BACnet Basics to specify
successfully
• Showcase BMS integration with BACnet and how it
works with Lighting.
• Share what to include and where to include for
successful BMS integration with BACnet in
integration specifications.
• Highlight what has been done and is being done in
the future make it easier and more inclusive in
specifying Lighting for BMS and BACnet
integration.
IES Annual Conference
•Scott Ziegenfus CEM, CLEP, CDSM, GGP, GPCP, LEED AP
•Government and Industry Relations Manager
•Hubbell Lighting, Inc.
•701 Millennium Blvd.
•Greenville, SC 29607
•m: 484.225.6345
•w: www.Hubbelllighting.com
• ASHRAE SSPC 135 BACnet Committee
Member since 2010
• SSPC 135 Data Modeling Working
Group Convener/Chair
• BACnet International Education
Committee Co-Chair
• BACnet International “Leader of the
Pack” Award recipient
BACnet and Lighting History
• Did you know?
• BACnet is ANSI/ASHRAE SSPC 135 BACnet Standard
• BACnet standard first committee meeting 1987
• BACnet standard first published in 1995
• BACnet achieved the status ISO 16484-5 in 2003
BUT
• 2001 was the first meeting of the Lighting Application –Working Group
• only 2 lighting Control Companies attended
Iconic BACnet Graphics by H. Michael Newman, “Father of BACnet”
BACnet Communication Basics
CLIENT(A Side)
SERVER(B Side)
service
request (What, How, and for How Long)
response (the way the Client requests)
• DEVICES and OBJECTS = WHAT is Controlled
• SERVICES = HOW it is controlled
CLIENT CANNOT TALK TO CLIENT
OR
A side cannot talk to A Side
SERVER CANNOT TALK TO SERVER
OR
B side cannot talk to B Side
BACnet Communication Basics
Clause 12
OBJECTS = WHAT BACnet communicates
• The standard specifies 55 types of objects:
• Access Credential
• Access Door
• Access Point
• Access Rights
• Access User
• Access Zone
• Accumulator
• Alert Enrollment
• Analog Input: Sensor input
• Analog Output: Control output
• Analog Value
• Averaging
• Binary Input: Switch input
• Binary Lighting Output
• Binary Output
• Binary Value
• Bit String Value
• Calendar
• Channel Object
• Character String Value
• Command
• Credential Data Input
• Date Pattern Value
• Date Value
• Date Time Pattern Value
• Date Time Value
• Device
• Event Enrollment:
• Event Log
• File:
• Global Group
• Group
• Integer Value
• Large Analog Value
• Life Safety Point
• Life Safety Zone
• Lighting Output
• Load Control
• Loop
• Multi-state Input:
• Multi-state Output:
• Multi-state Value
• Network Security
• Notification Class
• Notification Forwarder
• Octet String Value
• Positive Integer Value
• Program
• Pulse Converter
• Schedule
• Structured-View
• Time Pattern Value
• Time Value
• Trend Log
• Trend Log Multiple
BACnet Communication Basics
SERVICES = HOW BACnet communicates
• BIBB = A service or collection of services
to perform a function
• BIBB Example 1) is the Dynamic Device Binding (DM-DDB) = In plain English is BACnet device
discovery using the WHO-IS and I-AM services. DM-DDB-A is the client side and DM-DDB-B is
the server side.
• BIBB Example 2) is the Change of Value (DS-COV) = In plain English is automatic real-time
feedback using the Subscribe COV, Confirmed COV Notification, and Unconfirmed COV
Notification services. DS-COV-A is the client side and DS-COV-B is the server side.
BACnet Communication Basics
DEVICE PROFILES = WHAT ARE YOU?STANDARD DEVICE Type
• Device Profile is defined by a minimum set of BIBBs (A and/or B side)
• standard types in Annex L of the ANSI/ASHRAE standard 135-2012, BACnet
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)
It’s ALL
about the
BIBBs
B-AWS B-OWS B-OD B-BC B-AAC B-ASC B-SA B-SS
Data Sharing DS-RP-A,B DS-RP-A,B DS-RP-A,B DS-RP-A,B DS-RP-B DS-RP-B DS-RP-B DS-RP-B
DS-RPM-A DS-RPM-A DS-RPM-A DS-RPM-B
DS-WP-A DS-WP-A DS-WP-A DS-WP-A,B DS-WP-B DS-WP-B DS-WP-B
DS-WPM-A DS-WPM-A DS-WPM-B DS-WPM-B
DS-AV-A DS-V-A DS-V-A
DS-AM-A DS-M-A DS-M-A
Alarm & Event Mgmt AE-N-A AE-N-A AE-N-A AE-N-I-A AE-N-I-A
AE-ACK-A AE-ACK-A AE-ACK-B AE-ACK-B
AE-INFO-B AE-INFO-B
AE-ESUM-B
AE-AS-A AE-AS-A
AE-AVM-A AE-VM-A
AE-AVN-A AE-VN-A AE-VN-A
AE-ELVM-A
Scheduling SCHED-AVM-A SCHED-VM-A SCHED-E-B SCHED-I-B
Trending T-VMT-I-A T-V-B T-VMT-I-B
T-ATR-B
Device and Network Management DM-DDB-A,B DM-DDB-A,B DM-DDB-A,B DM-DDB-A,B DM-DDB-A,B DM-DDB-B DM-DDB-B DM-DDB-B
DM-ANM-A
DM-ADM-A
DM-DOB-B DM-DOB-B DM-DOB-B DM-DOB-B DM-DOB-B DM-DOB-B DM-DOB-B DM-DOB-B
DM-DCC-A DM-DCC-B DM-DCC-B DM-DCC-B
DM-MTS-A DM-MTS-A
DM-TS-B
or
DM-UTC-B
DM-TS-B
or
DM-UTC-B
DM-OCD-A
DM-RD-A DM-RD-B DM-RD-B
DM-BR-A DM-BR-B
Operator Work Stations Controllers
Operator Work
Stations
Controllers
BACnet Communication Basics
• Changes in the Device Profiles• Profile Families
• A fundamental shift is happening to make specifying easier without the need for a PhD level of
understanding in BACnet because of a new “family” approach to BACnet device profiles. This
new approach just appeared in the newly available 2016 publishing of the BACnet standard.
Iconic BACnet Graphics by H. Michael
Newman, “Father of BACnet”
Proper / Required Documentation• Protocol Implementation Conformance Statement
• REQUIRED Documentation (not a sell sheet or spec sheet)
• It is exact detailed information on WHAT and HOW your device communicates using BACnet
(not just a list of objects)
• Blank PICS in ANNEX A of the standard
• Downloadable blank PICS available at www.bacnet.org/DL-Docs
• It is a specific 2 page questionnaire
Who ARE
you?
What are
your BIBBs ?
What type of
infrastructure
Security?
Networking?
Do I know
your
Device
Profile?
What Verison
of BACnet?
Your objects
are What?
Tested by 3rd Party Testing
• 4 Labs have license to test BACnet MBS GmbH SoftDEL Systems Private
Germany India
DIAL GmbH iHome Lab
Germany Germany
• Testing Mark Administration• BTL Listing through BACnet International
DOMESTIC
http://www.bacnetinternational.net/btl/
• WSPCert Certification through BACnet Interest Group-EUROPE (BIG-EU)
INTERNATIONAL
http://www.big-eu.org/en/products/certified-products/
• Testing Follows the ASHRAE SSPC 135.1 testing standard
• Each device based on its profile will be tested
• Must PASS Minimum 70 tests for a Simple Sensor (B-SS) to a
BACnet Controller (B-BC) 360+ testsB-AWS B-OWS B-OD B-BC B-AAC B-ASC B-SA B-SS
300 240 110 360 210 100 80 70
Points List
Example from Trane
Chiller Integration guide
“The industry has long used the general-purpose term "points", which
could refer to sensor inputs, control outputs or control values, with
different characteristics according to manufacturer”Bill Swan, Alerton Technologies, Inc
• The PICs are the technical specifications for BMS
• Points lists are WHAT each object does in your system
• No points list is like you asking what a lighting system does and they tell you it is distributed
and has an IP 65 rating, YES but what does it do?!
Some Rules of Thumb
• INSIST ON A PICS• If a company does not have the 2 page required document that
has a blank downloadable form and is REQUIRED by the standard that they can just fill out, what else did they miss in the 1000+ page standard that might be a long and costly issue on a project?
• MAKE SURE IT IS TESTED • The BACnet standard is over 1300+ page book of technical
instructions, do not rely on any engineer reading it all correctly or the same as another engineer. Even the committee members that write the standard argue about the standard!
Specifying BACnet for Lighting
• Coordination Issues
• Traditionally Building Management Systems has been under the
Mechanical Engineer sometimes putting all the integration
specifications under Division 23 (HVAC).
• Lighting under Division 26 means trades may never see it.
• Specifiers and installers understand the functionality and workings of
systems they are responsible for but may not be invested in or
understand what is involved in the integration to the BMS
• Leading to general statements in CSI Specs like “Building integrator shall
provide integration of the lighting control system with Building
Automation Systems using BACnet.”
Specifying BACnet for Lighting
25 13 00 Integrated Automation Control and Monitoring Network
All control systems to be integrated with the Building Management
System (BMS) shall conform to ANSI/ASHRAE Standard 135,
BACnet standard.
• CSI Recommendations
• Use Division 25 - Integrated Automation !!!!
• Added in the CSI Master Spec as a "place holder" for integration but
not used today (or used VERY little)
• A central place for all Integration and communication specifications
between systems
• Add all common protocol requirements to Lighting Division
- 26 09 43 System Integration (Division 26 Lighting)
- Controller and operator interface communication shall conform to
ANSI/ASHRAE Standard 135, BACnet/IP Annex J standard
Lighting system should have a Sequence of Operation for
Integration for BMS Integration
• WHO DOES WHAT?
� Time clock BMS or Lighting or combination or Scheduling Object?
� BMS building sweep covers lighting and what about areas with
Occupancy Sensors?
� Does the lighting system need to provide real time feedback to the
BMS with no polling required?
� How much control vs monitoring does the BMS systems have over the
lighting system?
� Sharing DATA does your Occupancy area correlate to HVAC zones?
CSI Recommendations
1.01 Lighting BACnet Interface Object Creation Requirements
1.01.1 Equipment Supplier shall create objects using the table below based on the following requirements:
1.01.1.1 The individual lighting device is called a ZONE. Lighting devices such ballasts, occupancy/vacancy sensors, daylight sensors and local controllers are considered ZONEs. Create all lighting devices as a separate ZONEs.
1.01.1.2 There are one or more ZONEs grouped into AREAs. An AREA is normally the space that is served by one HVAC Air Terminal Unit. If a VAV box serves more than one office, each office shall be set up as an AREA. If there is more than one lighting device (i.e., ballasts, occupancy/vacancy sensors, daylight sensors and local controllers) in a given AREA, create each lighting device as a separate ZONE.
1.01.1.3 The group of AREAs that are served by one HVAC Air Terminal Unit is called a DOMAIN. AREAs may or may not be contiguous. 1.01.1.4 The graphic below shows the relationship between the ZONEs, AREAs and the DOMAIN for typical group of offices found in the Work.
Examples supplied by Appin Associates, Grant Wichenko President
Gateways vs Embedded
• 3rd Party Gateways• 3rd Party Gateways are protocol translators translating each
command from BACnet to a protocol known by the lighting system
• Used many times as the initial entry into BMS integration
• Using a gateway, like any translation, information maybe lost and
many times does not have the same meaning making them a
negative condemnation for BMS integrators.
• Embedded BACnet stack puts the responsibility of BACnet on the
company embedding it.
• PICS needs to be Company Specific not of the entire gateway.
Translating two computer languages is like translating two human
languages. Words don’t mean exactly the same thing from one language to
another and it takes extra time waiting for everything to be translated. Try
using Google to translate a letter and then give that letter to someone who
can speak the other language fluently and watch the expression on their
face. They will probably break up laughing.
The Term Native
• Native
� Industry term not a technical term usually means embedded
� Not defined in the BACnet Standard or by an authoritative source
� Is nowhere in the 1300+ page BACnet standard (ANSI/ASHRAE
standard 135-2012, BACnet)
� “Native” is relative for your frame of reference
� May or may not be conformant with the BACnet standard!
What is the meaning of 'natural' on the label of food?
From a food science perspective, it is difficult to define a food product that is 'natural' because the
food has probably been processed and is no longer the product of the earth. That said, FDA has
not developed a definition for use of the term natural or its derivatives. However, the agency has
not objected to the use of the term if the food does not contain added color, artificial flavors, or
synthetic substances.
http://www.fda.gov/aboutfda/transparency/basics/ucm214868.htm
Like a food labeled “Natural”???
Conformance to the Standard
• Is a clause in the BACnet standard
� Has exact requirements
� It is clear in the “Table of Contents”
� It insists on a PICS
� Asks to be tested
� Only 4 pages
IT’S IN
THERE
Lighting Specific Objects
• Lighting Output Object (analog) - The new object is made specifically for Lighting
offering features used in lighting applications, such as:
- Blink-warn for Afterhours
- Continuous control of lighting level
- Ramping to a level at a fixed rate of change Fading to a level time
- Incremental stepping values up and down.
- Feedback for actual value of physical lighting
- Total Power and Instantaneous power of loads
- Min and Mav value for High and Low end trim
• Lighting Output Object (Binary) – Same as analog Plus functions that have clear
equivalencies to similar functions in DALI-based lighting systems such as:
• Elapsed Time and Reset indicated accumulated number of seconds that the light was ON
• Strike_Count and Reset the number of times the light has transitioned from OFF to ON
(Approved October 27, 2012.)
(Approved July 3, 2014.)
Lighting Specific Objects Coming
• Staged Value Object
- Changing thresholds between scenes with deadband availability. Common use is
Daylighting
• Color Value Object
- Describe color using X and Y model coordinates on the CIE chromaticity diagram
• Color Temperature Object
– the Lighting Output (LO) object is based on a white light with variable intensity from 0 to
100% luminance.. A given lighting output must be capable of varying its color temperature
over a range of color temperatures.
(Just voted to 2nd Public Review)
(In full Committee SSPC )
(In working Group )
Lighting Specific BIBBs
• Data Sharing-Lighting Output-A (DS-LO-A)
• Data Sharing-Advanced Lighting Output-A (DS-ALO-A)
• Data Sharing-Lighting Output-B (DS-LO-B)
• Data Sharing-Binary Lighting Output-B (DS-BLO-B)
• Device Management – Lighting Output Management-A (DM-LOM-A)
• Data Sharing-Lighting View-A (DS-LV-A)
• Data Sharing-Lighting Advanced View-A (DS-LAV-A)
• Data haring-Lighting Modify-A (DS-LM-A)
• Data Sharing-Lighting Advanced Modify-A (DS-LAM-A)
BIBB = A service or collection of services to
perform a function
(Just voted to 2nd Public Review)
Lighting Specific Device Profiles
• Lighting Operator Interfaces- BACnet Advanced Lighting Workstation (B-ALWS)
- BACnet Lighting Operator Display (B-LOD)
• Lighting Control Stations - BACnet Advanced Lighting Control Station (B-ALCS)
- BACnet Lighting Control Station (B-LCS)
• Lighting Controllers - BACnet Lighting Supervisor (B-LS)
- BACnet Lighting Device (B-LD)
(In 2nd Public Review)
Lighting Control / Monitor Software
Smart switch or dimmer
Touchscreen
Keypads
BACnet /IPv6
• NEW in the 2016 publication
• Now BACnet /IP = IPv4 and BACnet /IPv6 = IPv6
BACnet /NL Stack
BVLL
ARCNETEIA-485
ISO 8802-3(IEEE 802.3)Ethernet
ISO 8802-2 (IEEE 802.3)Type 1
EIA-232
MS/TP PTP
LonTalk
UDP/IPv4
ZVLL
ZigBee CBA
IEEE 802.15.4
BVLL IPv6
UDP/IPv6
IP Datalink
= Current BACnet Definitions
BACnet Application
BACnet Application Layer
BACnet Network Layer
BACnet /IT
• BACnet over HTTP
• Gets BACnet out of the transportation business moving the message
• Can use standard Network security protocols like TLS.
• Just voted into advisory public review (APR)
BACnet Web Services
• NEW in the 2016 publication
• HTTP REST (REpresentational State Transfer) model
• eXtensible Data Structures used
- Control Systems Markup Language (CSML) “Native XML” • Choice of XML or JSON
• defining, transmitting, and storing BMS and other application data.
• Security is provided by TLS (https:) and a profile of OAuth 2.0
• Uses URIs (e.g. https://bws.example.com/path/to/data) to access data
• The data model and services are protocol independent, and can therefore be used to model and access data from any source,. CLASIC BACNETT KNX T LONWORKS TETC
Points to Remember
� Must have a Proper PICS
� Should be 3rd Party certified
� Make sure you supply a points list
� Sequence of operation defining Lightings role vs BMS role
in lighting and how they work together
� Use division 25 it is for integration
� Lighting is getting easier should be more defined within the
next 12 to 24 months
� BACnet /WS and BACnet /IT is being built for IoT and
those systems talking IoT