BACnet Basics

Ben H. Dorsey III

VP, Marketing &
Communications
KMC Controls, Inc.

Preview
BACnetthe standard
BACnetthe community
BACnetand you

Caution
BACnet is BIG

Part 1
BACnetthe
standard

What is BACnet?

A book
An open standard
A data communications protocol
An acronym: Building Automation
and Control Networks
A means of integrating building
systems
A way of life!
5

So . . .
BACnet is a data communications
protocol and an agreed-upon set of
rules for creating interoperable
networks of building systems.

Encompassing . . .
Building Automation Systems (BAS)
HVAC Central Plant (Chillers, Boilers,
Large Air Handlers)
Lighting
Perimeter and Object Security
Fire and LifeSafety
Elevators
The integration of all of the above.
7

Who did it?

A working group (standard
project committee) of the
American Society of Heating,
Refrigerating and AirConditioning Engineers
(ASHRAE).
Began work in 1987 under
tremendous opposition (some
said it would NEVER be done).
Published as a standard in
1995.
Supported and maintained by
ASHRAE Standing Standard

Its Alive!!!
By design, the standard is under
continual revision.
First published in 1995.
In recent times, most
manufacturers products have
been designed to the 2004 and
2008 versions of standard.

Not a Reactive Process

Addenda are issued as the
committee works.
Public review and comments
are mandatory and
common.
So, for example, when 2008
was issued, it consisted of
2004 + previously issued
addenda.
(No surprises.)
10

What the Standard

Defines
In essence, the standard defines the
messages that devices exchange and
how they are delivered.

message

transport
11

Further . . .
The rules of the protocol apply to

Electrical signaling
Addressing
Network access (master/slave, peer-to-peer)
Error checking
Flow control
Message sequencing, segmentation,
checkpointing
Presentation format (compression, encryption)
Message format
Source: Mike Newman, BACnet pioneer

12

Another Pyramid?
The protocol can be viewed as a matrix
of layers.
BIBBS
Services
Devices
Objects
Properties

13

Properties
The nucleus to the
BACnet atomthe
smallest piece of
BACnet information
Properties can be
read and written.
Properties can
provide command
control.
They consist of
names and values.

BIBBS
Services
Devices
Objects
Properties

14

Properties
Example: high_limit = 78.0
The standard requires some
properties; other properties are
optional; still others can be
proprietary.
Required properties must be
implemented for each object type.
Optional properties do not have to be
implemented, but if they are, they
must conform to the specification.
15

Property Identifiers
Property types 0 511 are reserved
as standard.
166 of these are currently defined in
the BACnet specification.
Property types above 511 are
proprietary and unique to the vendor.
The Vendor ID property is used to
identify the manufacturer.

16

Objects
Objects are the
fundamental building
blocks (atoms) of the
standard.
Objects represent
data that originates
in physical inputs,
physical outputs, or
software processes.
Each BACnet Object
possesses a number
of properties.

BIBBS
Services
Devices
Objects
Properties

17

Object Types
The standard specifies 25 types of
objects:
Binary Input
Binary Output
Binary Value
Analog Input

Analog Output

Analog Value

Multi-state Input

Multi-state
Output

Multi-state
Value

Averaging

PID Loop

Trend Log

Command

Calendar

Schedule

Life Safety
Zone

Life Safety
Point

Notification
Class

Event
Enrollment

Program

File

Group

Device

Pulse
Converter

Accumulator

18

Objects
Vendors can implement proprietary
object types.
When they do so, they use standard
data types to promote
interoperability.

19

Object IDs
Numerical identifier that combines
object type and instance number.
Object types 0 127 are reserved to
identify standard BACnet objects.
Object types 128 1023 are used to
identify proprietary objects.

20

Object IDs
BACnet devices will support any
mixture of object types up to a limit
of 4,194,303 instances.
Object IDs are typically referred to in
this manner:
Analog Input, 5

21

ObjectsSummary
Objects standardize the organization
of data to facilitate the exchange of
data between different vendors
products.

22

Devices
There are six device
types or profiles specified
by the standard:
Operator Workstation (BOWS)
Building Controller (B-BC)
Advanced Application
Controller (B-AAC)
Application Specific
Controller (B-ASC)
Smart Actuator (B-SA)
Smart Sensor (B-SS)

BIBBS
Services
Devices
Objects
Properties

23

Services
Think of BACnet
services as the
messages that
BACnet devices
send to each
other.
Some services
read and write
properties of one
or more objects.
Other services
send notification
of alarms or
special events.

BIBBS
Services
Devices
Objects
Properties

24

Services
BACnet services follow a ClientServer model.
A BACnet client is a device that requests
a service
A BACnet server is a device that
performs a service

25

Categories of Services
Alarm and Event
Routing & event notification

File Access
Accessing & manipulating files contained in devices

Object Access
Read and write properties
Create and delete objects
Manipulate lists of data

Remote Device Management

Remote monitoring and control of devices

Virtual Terminal
Used by a client user to establish a connection to an
application program server in another BACnet
device.
26

Services
ReadProperty
We wish to read the present value for an analog input called SPACE_TEMP
Service= ReadProperty
ObjectIdentifier = (Analog Input, Instance 5)
PropertyIdentifier = Present_Value

Operator Workstation
(client)

MS/TP AAC
(server)

Assuming the target machine can locate the object with this ID and the requested properties, the
result would be:
Service= ReadProperty
ObjectIdentifier = (Analog Input, Instance 5)
PropertyIdentifier = Present_Value
Value = 72.3

The result indicates that the present value of SPACE_TEMP is 72.3

Source: ANSI/ASHRAE Standard 135-2004, page 494

27

BIBBS
BACnet
Interoperability
Building Blocks
BIBBS are collections
of services
BIBBS define 5 areas
of interoperability:
Data Sharing
Alarm and Event
Management
Scheduling
Trending
Device and Network
Management

BIBBS

Services
Devices
Objects
Properties

28

Data Sharing BIBBS

Description

B-OWS

B-BC

DS-RP-A (read property)

DS-RP-B

DS-RPM-A (read property multiple)

DS-RPM-B

B-AAC

B-ASC

B-SA

B-SS

DS-RPC-A (read property conditional)

DS-RPC-B
DS-WP-A (write property)

DS-WP-B
DS-WPM-A (write property multiple)
DS-WPM-B

DS-COV-A
DS-COV-B
DS-COVP-A

29

Alarm & Event

Management BIBBS
Description
AE-N-A (notification)

B-OWS

B-BC

B-AAC

BASC

AE-N-I-B (notification, internal)

AE-N-E-B (notification, external)
AE-ACK-A

AE-ACK-B
AE-ASUM-A (summary)
AE-ASUM-B
AE-ESUM-A (enrollment summary)

AE-ESUM-B
AE-INFO-A
AE-INFO-B
AE-LS-A (life safety)

30

B-SA

B-SS

Scheduling & Trending

BIBBS
Description
SCHED-A

B-OWS

B-BC

B-OWS

B-BC

B-AAC

B-ASC

T-VMT-E-B

T-ATR-B

B-SS

T-VMT-I-B

T-ATR-A (automated trend retrieval)

B-SA

SCHED-E-B (external)

T-VMT-A (viewing & modifying)

BASC

SCHED-I-B (internal)

Description

B-AAC

31

B-SA

B-SS

Device & Network Management BIBBS

(1 of 2)

Description

BOWS

B-BC

DM-DDB-A (dynamic device binding)

DM-DDB-B

DM-DOB-A (dynamic device object)

DM-DOB-B

DM-DCC-A (device communication

control)

DM-DCC-B

B-AAC

BASC

or

or

B-SA

DM-PT-A (private transfer)

DM-PT-B
DM-TM-A (text message)
DM-TM-B
DM-TS-A (time synchronization)
DM-TS-B

32

B-SS

Device & Network Management BIBBS

(2 of 2)

Description

B-OWS

DM-RD-B
DM-BR-A (backup & restore)

B-BC

B-AAC

BASC

DM-BR-B

DM-R-A (restart)
DM-R-B
DM-LM-A (list manipulation)
DM-LM-B
DM-OCD-A (object creation & deletion)
DM-OCD-B
DM-VT-A (virtual terminal)
DM-VT-B
NM-CE-A (connection establishment)

33

B-SA

B-SS

BIBBs Summary
Example: B-BC

Data Sharing

Generation of alarm/event notifications and the ability to direct them to recipients

Maintain a list of unacknowledged alarms/events
Notifying other recipients that the acknowledgement has been received
Adjustment of alarm/event parameters
Ability to schedule output actions, both in the local device and in other devices, both
binary and analog, based on date and time

Trending

provide the values of any of its BACnet objects

retrieve the values of BACnet objects from other devices
allow modification of some or all of its BACnet objects by another device
modify some BACnet objects in other devices

Scheduling

to
to
to
to

Alarm & Event Management

Ability
Ability
Ability
Ability

Collection and delivery of (time, value) pairs

Device & Network Management

Ability
Ability
Ability
Ability
Ability
Ability
Ability

to
to
to
to
to
to
to

respond to queries about its status

respond to requests for information about any of its objects
respond to communication control messages
synchronize its internal clock upon request
perform re-initialization upon request
upload its configuration and allow it to be subsequently restored
command half-routers to establish and terminate connections

34

Transport Options

BACnet IP
BACnet Ethernet (8802-3)
Master Slave/Token Passing (MSTP)
ARCnet
LonTalk
Point-To-Point (PTP)

35

Transport Comparison

BACnet IP

Popular, fast. No real

performance difference
between this and 8802-3.
Use BBMD or PAD router to
get across an IP router.

Broadcast issues.

BACnet 8802-3

Popular, fast. No real

performance difference
between this and IP.

Cannot get across IP

routers.

MSTP

Very popular, especially as a

low-level bus technology for
AACs and ASCs. Uses EIA485 signaling over twisted
pair wiring.

Lower performance.

36

BACnet Layers vs OSI

Layers
Standard OSI Reference Model

Application

BACnet Layers

Presentation
Session
Transport
Network

BACnet Application Layer

Application

BACnet Network Layer

Network

ISO8802-2 (IEE 8802.3)

Type 1
ISO8802-3
(IEE 802.3)

Equivalent OSI Layer

MS/TP

Data Link

PTP
LonTalk

ARCNET

EIA-485

Physical

EIA-232

Data Link
Physical

Source: ANSI/ASHRAE Standard 135-2004, page 9

37

Auxiliary Devices
Routers
Useful when networks using different
BACnet transport options need to
exchange data.*
Operator Workstation on
BACnet IP network

Router

BACnet MSTP Controller Network

*This concept is referred to as

Internetworking.

38

Auxiliary Devices
Gateways
Useful when devices on a BACnet
network must exchange data with
devices on a non-BACnet network.*
Gateway

*This is also
Internetworking.

BACnet network

Proprietary Network
39

So, whats the

difference?
A router is really a pass-through
device. It doesnt change the form
or content of the message but just
the packagingmuch like
repackaging a standard USPS letter
for sending via Fedex.
A gateway has to translate and is
inherently more complex. It opens
the letter, translates it into a
second language, and puts it back
into some sort of envelope and
sends it on.

Source: Mike Newman, BACnet pioneer

40

How Does BACnet

Work?
Objects

Application Language

Representing
Information

Making Requests
and Interoperating

Services

Transport System

LANs
Internetworking
Source: David Fisher, PolarSoft

41

Typical System View

Operator
Workstation

Management Level

Ethernet or IP LAN
Router

Gateway

Integration Level

MSTP LAN

Proprietary LAN

Field Controller Level

ASCs & AACs

Proprietary Controllers

Application Level
BACnet-enabled Applications & other apps
42

Part 2

BACnetthe
community

Engineers & Educators

Members of ASHRAE
12 standard regions with 7-16 chapters in
each
Beyond America, ASHRAE reaches into
Canada and South America.
Beyond the Americas, ASHRAE reaches into

Hong Kong
Malaysia
Philippines
Singapore
Taiwan
Thailand

Middle East
Scotland
India
Wales
Africa
Ireland
Europe
Scandinavia
England

44

SSPC 135
Consists of 7 working groups:
Applications
Lighting Applications
Life Safety & Security
Network Security
Objects & Services
Utility Integration
XML & Web Services

45

Manufacturers, Integrators,
Owners
BACnet International
Formed in January 2000 to
"encourage the successful use of the
data communication protocol,
"BACnet", in building automation and
control systems, through
interoperability and compliance
testing, educational programs, and
promotional activities."

46

Corporate BI Members

47

Plugfests
Among the many initiatives undertaken
by BACnet International are
interoperability workshops or
plugfests.
Dozens of member compnaies routinely
take part in these 3-day events for
validating product interoperability.

48

Interests Groups
BIGs consist of users, integrators,
manufacturers, contractors, and
other interested parties.

BIG-SU

BIGFI
49

BTL
BACnet Testing Laboratories
Established under direction
and continued supervision of
BACnet International in Feb
2000
Our goal is to improve
interoperability between
BACnet products through a
combination of BTL lab
testing, multi-vendor
interoperability testing, and
adherence to the BTL's device
implementation guidelines.
(Jim Butler, BTL Manager)
Lists products by issuing
mark

50

BTL
Has freedom to make requirements
above and beyond the minimum
requirements specified in the
standard.
Manufacturers are given pretest
guidelines.
Requires an extended engineering
commitment of manufacturers.

51

Part 3
BACnetand you

BACnet & You

Why go BACnet?
Engineer & owner considerations
Is it really interoperable?
Whats next?

53

BACnet Benefits
It is an accepted standard
domestically (ASHRAE/ANSI 1352004), in Europe (CEN TC 247), and
worldwide (ISO 16484-5).
It was developed specifically for
building systems.
While HVAC is at its roots, the
standard nicely incorporates other
integrated functions.

54

BACnet Benefits
It can be implemented on low-cost
networks (dedicated or shared)
and is extremely flexible in LAN
types.
BACnet devices are costcompetitive with long-standing
proprietary devices.
The standard specifically provides
for scheduling, trending, and
alarming.
55

BACnet Benefits
It is easily scalable at all levels for
any size job.
It is completely open and not
dependent on specific hardware.
It provides for automatic device
discovery (saving installation costs).

56

BACnet Challenges
It does not specify hardware
configuration. Therefore,
configuration tools (required for
initial device setup) vary by
manufacturer.
No standard application types are
defined; therefore, its not yet plug-nplay.

57

Considerations
Become familiar with PICS
Protocol Implementation
Conformance Statements
Defined format
Specify device type, BIBBS supported,
Object Types supported, and Data
Link layer transport options.
Required for each BACnet device
Available to you

58

Considerations
Become familiar with PICS.
Look for native BACnet.
Native BACnet typically refers to a
device that inherently represents data
in BACnet format and communicates
utilizing BACnet messaging. Native
BACnet devices can be connected to
a BACnet system without requiring a
gateway device or software driver to
translate to and from any proprietary
protocols. (Source: Delta Controls website)
59

Considerations
Become familiar with PICS.
Look for native BACnet.
Specify BTL listed products.
This is the BACnet communitys seal
of approval.
Note exception for operator
workstations (no testing yet
provided).

60

Considerations

Become familiar with PICS.

Look for native BACnet.
Specify BTL listed products.
Need spec writing assistance?
Do not go to the standard
(at least for this purpose).
Use your manufacturers reps.
Try www.ctrlspecbuilder.com.
61

Considerations

Become familiar with PICS.

Look for native BACnet.
Specify BTL listed products.
Get spec writing assistance if
needed.
Use protocol analyzers.

62

Considerations

Become familiar with PICS.

Look for native BACnet.
Specify BTL listed products.
Get spec writing assistance if
needed.
Use protocol analyzers.
Demand training.

63

Is it really
Interoperable?
YES!

64

Sample
Interoperability

450 Golden Gate, San

FranciscoPhillip Burton
Federal Building
Landmark BACnet
installation using two
vendor systems (Alerton
BACtalk and Trane Tracer
Summit) on BACnet
network.
9000 points, over 1000
VAV terminal units, 8 large
AHUs, 13 single-zone AHUs
65

Sample
Interoperability

Paducah Community College,

Kentucky
BACnet installation using two
vendor systems (Alerton and
Reliable Controls) on BACnet
network.
6 buildings, 1000 points

66

Sample
Interoperability
NY Metropolitan
Hospital, Manhattan
BACnet installation
using two vendor
systems (Delta
Controls and KMC
Controls) on BACnet
network.
Recent isolation wing
renovation brought
KMC AACs onto the
Delta ORCAview
network.

67

Sample
Interoperability/Integrati
on
University of Arizona
435 total buildings.
BACnet IP campus WAN
Numerous vendor
systems featuring BMA
members Automated
Logic Corporation and
FieldServer
Technologies
ALCs WebCTRL
manages the front end.
FieldServer integrates
numerous devices and
systems (including
Modbus, LonWorks, and
Simplex) into the
BACnet network.
68

Where is BACnet
Going?
BACnet support of IP
communications lays the
necessary groundwork for
enterprise-wide challenges.
To meet these challenges,
however, will require greater
utilization of Internet protocols
developed in the IT realm.

69

XML & Web Services

Not really applicable to field-level controllers
but high-level communications.
XML provides for examining high-level data
while not being dependent on the
communication protocol of the BAS, such as
BACnet.
So, BACnet manufacturers need to support
XML in the operator workstation, for example.
Further, web services, such as .NET, provide
for greater possibilities in information
exchange.
The SSPC 135 XML Working Group is defining
how data can be exchanged consistently
between building automation systems and
other enterprise management systems.
70

Further Resources
www.bacnet.org
www.bacnetinternational.org

71

So, what are you

waiting for?

72