BACnet Global standard for open building management solutions

Christian Mueller Honeywell Building Solutions Germany

About the speaker...

light + building 2006

Christian Mueller

- Honeywell Building Solutions Germany since 1986 Leader Marketing Communication within Honeywell Building Solution Germany Leader of Working Group Marketing and Advisory Board member of the BACnet Interest Group Europe (B.I.G.-EU) since 1999 Member of CEN TC247 WG5 (Integrated Building Management Systems)

light + building 2006

The BACnet history

light + building 2006

He has a real problem ...

The BACnet history

He has got a solution ...

light + building 2006

Increasing demand for integration

light + building 2006

Percentage of construction projects in Germany that demand integration

16 14 12 10 Number (% ) 8 6 4 2 0
g tin igh L e Vid o A cce ss Fir e s nt ke me yst em mo e S ag e r s an h M Ot r gy e

1992 1995 1997 2000

En

I&I Limited The European Market 2000-2005 Intelligent Controls in Buildings

Heterogeneous System Integration

light + building 2006

Resulting systemfunctionality

System A Cost for integrating three systems

System B

System C

CEN/TC247 & ISO/TC205 norms

Protocol Norm EN V 1805-1 ISO 16484-5

light + building 2006

Management layer

BACnet

Automation layer

Protocol BACnet WorldFIP Profibus FMS EIBnet Protocol EIB BatiBus EHS LonTalk

Norm EN V 13321-1 EN V 13321-1 and EN 50170 EN V 13321-1 and EN 50170 EN V 13321-2 Norm EN V 13154-2, DIN VDE 0829 EN V 13154-2 EN V 13154-2 EN V 13154-2 EN 50295

Field layer

AS-i Actuator Sensor-Interface Safety-Bus

BACnet, ISO Norm 16484-5

light + building 2006

Communication layer Management layer and between Management and Automation layer

Protocol: BACnet

Automation layer

BACnet on all functional layers

BACnet DIN EN ISO 16484-5 Includes references to EIA-709.1 LonTalk EN 50090 EIB/KNX

Field layer and between Field and Automation layer

ISO Building Automation model

light + building 2006

BACnet history ...

1987

light + building 2006

1991 1995 1998 2001 2002 2003 2004

Foundation of the ASHRAE (American Society of Heating Refrigeration and Air-Conditioning Engineering) committee SPC135. Team charter: Development of a communication protocol which would be neutral and allow monitoring, control and energy management within buildings. First draft version of the new protocol available BACnet was published as ASHRAE 135-1995 standard. BACnet also becomes ANSI standard BACnet becomes EN 1805-1 and ENV13321 by CEN TC247 FND withdrawn by CEN as ENV ANSI/ASHRAE 135-2001 published BACnet becomes worldwide ISO norm as the only BMSprotocol The first BACnet devices are conformance tested in Europe

What is BACnet?

light + building 2006

BACnet ist a communication standard that allows for data exchange (including complex data) between systems from various vendors BACnet allows for interoperability of devices and systems from various vendors BACnet is most suited for - HVAC control applications (in Europe integrations on
management and automation layer) but also - Integration of life safety systems (fire panels)

Was can BACnet provide?

light + building 2006

BACnet does standardize transactions like: - COS/COV - Alarm/event handling supporting alarm/event priority - Historical data - Data access control - Command priority - File transfer - Save/Restore of programs - Calendar and Scheduling functionality BACnet is independent from any specific hardware, operating system or software platform

BACnet terminology

light + building 2006

Objects - Devices and systems are seen as black boxes consisting

of a number of objects - BACnet objects only define the outside behaviour of the devices and systems no internal functionality is defined

Object properties - Each object has got a number of mandatory (required) and optional properties. - The properties can be read by other devices and systems
and some can be written to. Vendors may define vendor specific properties (interoperability?)

Services - Communication between BACnet devices and systems is

done using specific services. - Services can be used f. e. to read object properties.

BACnet Networking Options

light + building 2006

Ethernet BACnet over IP Serial (RS232/RS485) ARCnet MS/TP LonTalk (is not equal to LonMark!)

Layer in ISO/OSIReference model

BACnetApplicationLayer BACnet Network Layer (allows Routing)

BACnet/IP ISO 8802-2 Type 1

Application

Network

MS/TP

PTP

LonTalk

Data-Link Media-Access

ISO 8802-3 Ethernet

ARCNET RS 485 RS 232 Physical

BACnet Client/Server architecture

light + building 2006

A BACnet device may trigger a service or can react on a service request:

- Client: - Server:

Requests services Offers services

(Service user) (Service provider)

Initiate Service

Execute Service

A DDC-system for example may act as a

- client for various field devices in an automation system, - server for other DDC-systems or for a BMS (Building Management
System) that requests specific data or alarms

light + building 2006

BACnet Objects

light + building 2006

BACnet Objects

Functional list, EN ISO 16484-3

light + building 2006

Object properties

light + building 2006

Standard Objects have required and optional properties defined Vendors may add proprietary object properties or vendor specific objects to a device

required optional

Object_Name Object_Type Present_Value Unit High_Limit Low_Limit

ROOM_TEMP ANALOG INPUT 20.3 62 = C 30.0 15.0

BACnet Services

light + building 2006

BACnet currently includes 38 services on the application layer which are subdivided into 5 categories: - Object Access - Device Management - Alarm and Event - File Transfer - Virtual Terminal

Services - Object Access

light + building 2006

Object access services include services like: - Read and write data (object properties) - Request a specific data range (e. g. to retrieve trend log

data) - Services to create other objects at runtime or delete them (like notification class objects or schedule objects) - Services to add data to lists or remove data from lists (data point and events to/from notification class objects)

Services - Device Management

light + building 2006

Network start-up - Who-Is, I-Am - Who-Has, I-Have Time Synchronization Request device start-up (via network)

BACnet Broadcast Management Device

light + building 2006

The BACnet Broadcast Management Device (BBMD) handles broadcast telegrams (Who-Is, Who-Has, I-Am, I-Have, ) through routers that connect different IP-subnets. The BBMD can be an external device or be integrated in another BACnet device like B-BC, B-OWS.

B-OWS

IP-Router

B-OWS

B-BC IP-Segment A BBMD Function IP-Segment B

B-BC

Services - Alarm- and Event

light + building 2006

Services include - Alarm- and event handling and - COV/COS (Change of Value/State) Request alarm summary list (e. g. after a communication restart) Services to acknowledge alarms

Alarm- and Event handling

light + building 2006

BACnet allows for three different methods for alarm and event handling

- COV Events

One or more recipients subscribe specific changes to state or value from a

COV-server using SubscribeCOV(Property) service. The COV-Server sends changes to the receivers that have subscribed for the event using (Un)ConfirmedCOVNotification

- Intrinsic Event Reporting

The recipient list of alarms and events from specific objects will statically or

dynamically be managed using NotificationClass objects The objects to support intrinsic alarming will have to support various optional properties like the EventEnable property

- Algorithmic Change Events

In order to support algorithmic change events, the EventEnrollment object

needs to be supported. The EventEnrollment object list contains stages and valuesof datapoints that need to be monitored. In case of a limit violation, the distribution of alarms/events can either be handled by the EventEnrollment object itself (if recipients are defined) or via a Notification Class object list if a NC object is defined with the object in alarm.0

The BACnet PICS

light + building 2006

PICS: Protocol Implementation Conformance Statement The PICS is a standard way of describing the BACnet functionality of a specific solution in a kind of table format and contains information about - BACnet services supported - BACnet standard objects supported including information
Whether or not BACnet objects can be created and deleted during

runtime Which object properties are supported and which are read-only

The BACnet PICS

light + building 2006

PICS continued ... - Data Link Layer Options

Description of the network options supported

(like Ethernet, BACnet /IP)

- Special functionality - Restrictions to properties, if exist

e. g. the max. number of characters for a key name or the

character set (e. g. ANSI X3.4)

The BACnet PICS is an important means for end customers and consultants to understand the functionality provided by a BACnet solution. This is achieved through - BACnet Interoperability Building Blocks (BIBBs) - Standard device profiles

BACnet PICS (Extract)

light + building 2006

BACnet Interoperability Building Blocks

light + building 2006

BIBBs Define a set of BACnet services to provide a specific function. BIBBs are either client (A) or server (B) related. There are BIBBs for the following areas of interoperability: (DS) - Data Sharing (AE) - Alarm and Event Notification (SCHED) - Scheduling (T) - Trending (DM) - Device Management (NM) - Network Management (VT) - Virtual Terminal Management

BACnet Interoperability Building Blocks

light + building 2006

BIBBs example: - DS-RP-A (Data Sharing-ReadProperty-A)

BACnet Service ReadProperty Initiate X Execute

BACnet Interoperability Building Blocks

light + building 2006

BIBBs example: - DS-COVP-B (Data Sharing-COVP-B)

(A) is user (Client), (B) is server (Server) (A) subscribes change of value of a specific property from (B) (B) serves (A) with COV of the object property without the need of

polling

BACnet Service SubscribeCOVProperty ConfirmedCOVNotification UnconfirmedCOVNotification

Initiate X X

Execute X

Standard BACnet device profiles

light + building 2006

B-OWS B-BC B-AAC B-ASC B-SA B-SS B-GW

BACnet Operator Workstation, GLT BACnet Building Controller BACnet Advanced Application Controller BACnet Application Specific Controller BACnet Smart Actuator BACnet Smart Sensor BACnet Gateway

Standard BACnet device profiles

light + building 2006

BACnet Interest Group Europe e. V.

light + building 2006

The BACnet Interest Group Europe e. V. (B.I.G.-EU) supports BACnet in Europe: - Web: http://www.big-eu.org - 45 members
(vendors, consultants, system integrators, associations)

- Working groups Marketing and Technology - B.I.G.-EU targets

Bring European market requirements into the standardisation Offer BACnet training Test and certification of BACnet solutions

Further BACnet organisations

light + building 2006

BACnet Interest Group North America BACnet Interest Group AustralAsia BACnet Interest Group Middle-East BMA - BACnet Manufacturers Association - Founded in 2000, USA - Open for all vendors of BACnet products - Develop ways to test/certify BACnet products (BTL-Logo),

Marketing, Training in USA - Intensive contact between B.I.G.-EU and BMA in order to guarantee mutual acknowledgment of BACnet certification

BACnet Tests and Certification

light + building 2006

BMA and BIG-EU develop a common test and certification system The target is to allow for a common, reproducible handling of conformance tests Mutual certification in EU and NA First tests available in EU through accredited test lab (WSP-Lab) Common Logo

BACnet Tests and Certification

light + building 2006

Today extent of the BACnet conformance tests - In USA tests are done based on the BACnet device profiles
(B-SA, B-ASC, ..)

- BIBBS, that can be tested in Europe today

e. g. DS-COV-B had not bee tested in the US, as it had not been a

market requirement so far

- Conformance tests are no BACnet certificates! - What would a BACnet certification be like?
In order to certify a BACnet device, the complete functionality as

specified by the device PICS must be tested. This is not possible today for complex devices like B-BC or B-OWS.

BIBBS, tested in Europe today

light + building 2006

DS-RP-B

- (B) provides data upon request from (A)

DS-WP-B

- (B) allows a value to be changed by (A)

DS-COV-B

- (B) accepts subscription requests from (A) and replies with

COVNotifications

DM-DDB-B

- (B) provides information about itself to (A)

DM-DOB-B

- (B) provides information about its objects upon request from (A)
DM-DCC-B

- (B) responds to comm. control request from (A)

DM-TS-B / DM-UTC-B (UTC Greenwich Mean Time)

- (B) accepts time sync. request from (A)

B-BC Example: Honeywell Excel Web

light + building 2006

LINU X inside !

LINUX operating system 10/100MBit/s network interface Integrated Web-Server with HTML-pages installed for parameter setting, local operation via browser No need for ActiveX controls Trend capacity can be expanded using standard CF memory cards Up to 1.000 BACnet objects I/O modules based on LonTalk (78kbps, Free topology wiring DIN rail or direct mounting

Upcoming BACnet extensions

light + building 2006

BACnet Web Services Web-Pages - Are designed for humans and are used through WebBrowsers

Web-Services - Automated services through Internet/Intranet used by

applications. - Services to supply other applications with data in a standard way independent from the underlying hard- or software or operating system.

XML used as the data format and SOAP as the protocol - SOAP (Simple Object Access Protocol) is based on http
which allows data to be exchanged through firewalls - IT-system security is not jeopardised

Upcoming BACnet extensions

light + building 2006

BACnet/XML Working-Group target - To link BACnet systems to ERP-applications via WebServices

Annex N BACnet/WS currently in Public Review

BACnet Web Service via SOAP

BACnet BMS, Automation island Application Server BACnet/Web Services via SOAP ERP-Client Application Makes use of Web Services via SOAP

light + building 2006

Some BACnet Projects

Technology compound at the German Parliamentary Buildings Paul-Lbe-

light + building 2006

Haus Reichstag
Marie-ElisabethLders-Haus Jakob-KaiserHaus

Spree

Technology compound at the German Parliamentary Buildings

light + building 2006

Honeywell
Supervisorx BMS

Ethernet (TCP/IP)

Supervisory BMS of the Energy compound

BACnet/IP

Reichstag

Paul-Lbe Haus Jakob-KaiserHaus

Unter den Linden 71 Wilhelmstrae 60

Schadowstr. 12/13 und Dorotheenstr. 88 Dorotheenstrae 88

Unter den Linden 50 Marie-Elisabeth-Lders Haus

Technology compound at the German Parliamentary Buildings

light + building 2006

Building
Reichstaggebude Paul-Lbe-Haus Paul-Lbe-Haus Paul-Lbe-Haus Marie-Elisabeth-Lders-Haus Jakob-Kaiser-Haus Wilhelmstrae 60/ Unter den Linden Schadowstrae 12/13 Dorothenstrae 88 Supervisory BMS at the Reichstag

Vendor
Kieback & Peter Honeywell Honeywell Honeywell JCI ABB Siemens (Landis & Staefa) AutomatedLogic Saia

System
BACnet Gwy Excel 500 IRC BACnet BACnet Tridium/BACnet BACnet BACnet BACnet

No. of dp

30.000 10.000 3.000 500 20.000 30.000 7.000 200 200

Honeywell

BACnet

100.900

Technology compound at the German Parliamentary Buildings

light + building 2006

Access to BACnet objects like schedule, calendar and loop

Building Management with BACnet

light + building 2006

light + building 2006

BACnet/OPC comparison

light + building 2006

The birth of OPC ...

Microsoft

OPC Introduction

light + building 2006

The task: - Get data from a PLC (Programmable logic controller) into an Microsoft based application within a PC-based network.
Prior to OPC a special driver needed to be written and maintained

for each protocol that had to be integrated into a visualisation (SCADA system) - Target:
Provide a standard interface with standard objects (OPC server) that

every PLC-vendor could integrate and that could also be integrated by every vendor of visualisations (OPC client) Provide a standard interface between plant control level and information technology

OPC History
1995

light + building 2006

- A task force composed of Fisher-Rosemount, Rockwell Software, Opto 22,

Intellution, and Intuitive Technology developed a basic, workable, OPC specification. - OPC = Object linking and embedding for process control

1996

- A simplified, stage-one solution was released in August 1996.

OPC foundation group started up.

1998

- OPC becomes an industry standard

1998

- OPC Data Access 2.0 published

2001

- Compliance Testing and Certification program available

2004

- The OPC Foundation has got more than 300 members.

Honeywell is also a member of the OPC Foundation.

OPC Introduction

light + building 2006

OPC (OLE for Process Control) is a Client-/Server Software Interface, based on the Microsoft COM / DCOM component technology. It is used to exchange data between different applications on one machine (COM) or between different applications on a network (DCOM). OPC is not a new bus standard, no norm - It may be compared with a printer driver available with a

printer which is the interface between the hardware and the office application

OPC is best suited for - Simple I/O type of information which need to be integrated
into office applications - Data exchange between software applications

OPC data types, object model

light + building 2006

OPC only supports simple data objects (so called OPC Items). OPC Items consist of - Value, state - Time stamp - Information about the quality of data OPC Object model - OPC Groups are defined on an OPC server. OPC groups
Periodical data transmission Data transmission on a COV/COS

contain OPC Items that are handles in a similar way. E. g.:

- Each OPC Item may have properties defined like

value range, engineering unit

OPC Specifications

light + building 2006

OPC Data Access - Used to move real-time data from PLCs and other control

devices to HMIs and other display clients. Standard on the market is OPC DA 2.04. The Data Access 3 specification is now a Release Candidate.

OPC Alarms & Events - Provides alarm and event notifications on demand

(in contrast to the continuous data flow of Data Access). - OPC Clients can subscribe for alarms and events from the OPC server (OPC-AE 1.10).

OPC Data eXchange - This specification takes OPC from client/server to server-to-server with communication across Ethernet field bus networks.

OPC Specifications

light + building 2006

OPC Historical Data Access - Where OPC Data Access provides access to real-time,

continually changing data, OPC Historical Data Access provides access to data already stored. (OPC DX 1.0)

OPC Security - OPC Security specifies how to control client access to these servers in order to protect this sensitive information and to guard against unauthorized modification of process parameters (OPC Security 1.0) OPC XML-DA - OPC XML-DA is developed to expose plant floor data using
XML and SOAP. Specification still under development

Need more information?

light + building 2006

OPC Foundation web pages - www.opcfoundation.org OPC European membebr web pages - www.opceurope.org

OPC/BACnet Comparison

light + building 2006

BACnet - Vendor independence

ISO Standard, independent

OPC - Vendor independence

De-facto-Industry Standard,

from OS, hardware or vendor

based on Microsoft COM/DCOM technology

- Best suited for

Automation and management

- Best suited for

Move real-time data from

level Peer-to-Peer communication for HVAC control and safety controls

PLC to visualisation and business applications Peer-to-Peer communication possible if OPC data eXchange extension becomes available

- Communication
IP support, Client-Server

- Communication
IP support, Client-Server

OPC/BACnet Comparison

light + building 2006

BACnet

OPC

- Specifications/Profiles
Data Sharing (with priority) Alarms and Events Historical Trends Scheduling Device and Network Management Access Control mechanisms build in BACnet via XML Specification in public review

- Specifications/Profiles
Data Access (DA) Alarm & Events (AE) Historical Trends only few implementations exist, Normally done on SCADA level Scheduling needs to be done on SCADA level Access Control available. Only a few implementations make use of OPC Security OPC XML-DA spec. under development)

- Conformance tests
BACnet Test Lab at Stuttgart is

- Conformance tests
Compliance Tests available through

capable to provide first basic BACnet conformance tests

the OPC Foundation

OPC/BACnet Comparison

light + building 2006

BACnet - Planning and Start-up

BACnet is not Plug & Play

OPC - Planning and Start-up

OPC allows for Plug & Play if

f. e. due to optional object properties A in depth comparison of the PICS is required Test installation recommended

Binding:
Data documentation can be exchanged via standard EDEFormat or BACnet solutions often allow for address space browsing

the network is correctly been set up. No optional object properties Configuration of DCOM in complex network environment can be tricky. Many times firewalls do not allow for port 15 (OPC/DCOM) to be open as several virus attacks (like W32Lovsan) came through this port Binding:
OPC solutions often allow for address space browsing

BACnet and OPC complement each other

light + building 2006

BACnet is most suitable if it comes to ... - Building Management applications (alarming with

acknowledgement, scheduling, save and restore of application programs, command priority, Peer-to-Peer data communication) - Data exchange between devices (e. g. an energy management application requires data from various DDC systems on the LAN for peak load control)

OPC is best suited if it comes to ... - Simple data exchange between a SCADA system and a PLC
or integration of a fire panels into a Visualisation - Data exchange with IT- or ERP (Business) applications