You and Your Company Name go

Here

Jay Garbarino, P.E.

Delta Controls

Your Company Background

Delta Controls History

Established ESC as consulting firm for
energy management solutions in 1980
Developed first DDC system in 1983
Introduced high speed communication
(1 million bits/s) in 1986 (Intelli-Sys)
Developed Delta Partner sales network
across Canada and into USA 1986-88

Agenda:

Current Direction of Building Automation

BACnet
Lonworks
Demos
Delta ORCAWeb demo

An Overview of...

An Overview of...

An Introduction - What is BACnet?

Acronym for
Building Automation and Control Network

Protocol

Open data communications protocol:

standard
means of communicating between computers and devices and
share data regardless of the equipment manufacturer

Allows different systems to operate in a

coherent automation & control system
Internationally recognized standard

since 1995 (NIST, CEN)

An Introduction - What is BACnet for

?

Integration of the building technical services

HVAC, Electrical, Fire, Security, etc.

Interoperability of DDC products from different

manufacturers
Packaged equipment controllerschillers,
boilers, heat pumps, packaged roof-top
AHUs
DDC systems operating different buildings or
building areas

An Introduction - Why was BACnet

developed ?
Competitive pricing for large scale
additions to existing systems
Long term flexibility in vendor
selection
Lower integration costs (vs.
proprietary interfaces)
Higher integration functionality

An Introduction - Who created

BACnet?
ASHRAE Standards Committee
Alerton Controls
Andover Controls
Automated LogicTeletrol
AutoMatrix
Delta Controls
Honeywell
Johnson Controls

Siebe (Invensys)
Siemens (Landis & Steafa)
PolarSoft
Carrier
McQuay International
Trane Company

Cimetrics
Orion
Cornell University
NIST

BACnet System
Architecture

Illustrated with Delta ORCA System

Management
Level
Windows XP

Operator Workstation
(OWS)

Windows XP

OWS

IP

Primary LAN

Ethernet LAN
BACnet / IP

PTP
(EIA-232)

Automation
Level
Router

Advanced
Application
Controller
Field
Level

Sub-level
LAN

MS/TP
EIA4
8
5

Application Specific Controllers

Building Controller

BACnet Additions (Annex J) - BACnet

IP
BACnet/IP

Approved by Committee
DEV 3001

BACnet over the Internet

IP routing based on UDP/IP

DEV 3002

BACnet/IP

ARCNET
ARCNET

Ethernet
Ethernet

DEV 11
DEV

DEV 22
DEV

DEV 33
DEV

DEV 2001
2001
DEV
LON
LON

MS/TP
MS/TP

DEV 1001
1001
DEV

DEV 2002
2002
DEV

DEV 1002
1002
DEV

DEV 1003
1003
DEV

DEV 4001
4001
DEV

DEV 4002
4002
DEV

An Introduction - What BACnet

doesnt provide ...
Device Set-up/Configuration
Common programming language
Operator Look & Feel
Total Plug & Play connectivity

Specifying BACnet - The Simplified

Process
1.

Determine why BACnet is a requirement

(one OWS, multi-vendor product interfacing
or data sharing, future expansion, etc.).
The reasons will in turn determine how
detailed the specifications need to be.

2.

Lay out a proposed architecture and

determine at what levels in the system
BACnet is desired.
For each network level in the system
determine the media that will be used. If it
is specified up-front, then each vendor is
responsible for routing to this media if
routers become necessary.

3.

Specifying BACnet - The Simplified

Process
4.

Select BACnet interoperability functions for

each device using BIBBS:
Data Sharing
Alarms & Events
Time Schedules
Trend logs
Device & Network Management

5.

Determine who is responsible for system

integration.

Lonworks - what is it?

Facility Connect- June

2002
The Benefits Of LonTalk
LonTalk is another communications protocol that has gained wide acceptance in
the BAS world. Developed by the Echelon Corporation and a group of control and
HVAC systems manufacturers, it shares many similarities with BACnet in terms of
functionality and the ability to allow components from multiple vendors to work
together. (While the two systems are not directly compatible, they can be used in
the same BAS with the help of translator components.)
Although LonTalk did not become adopted as a standard by ANSI or ASHRAE, it
did attain a significant following, and LonTalk-compatible systems and
components are widely available.

Lonworks and BACnet

What are some of the real differences

Lonworks

BACnet

Proprietary protocol built into a chip

Consensus developed standard

set

protocol

Originated from transportation

Initiated by Cornell University,

industry, Echelon Corporation

owner driven

Protocol in use in many industrial

Protocol optimized for the building

type applications thus is relatively

automation industry

generic
Device level protocol - determines

Functional view point of protocol -

set of characteristics, inputs, outputs,

objects and services

setpoints, for each type of device

Processor limits to Neuron chip

Standard network chip for

small applications

Ethernet/Arcnet

separate processor required for

RS485 (MS/TP) can have

larger applications

application imbedded with network

What are some of the real differences

Lonworks

BACnet

Network communication speeds of

Multiple networks topologies

78,000 to 1.5 mbaud Lontalk

include Ethernet, Arcnet, RS485

(MS/TP), RS232 (PTP), Lontalk
Speeds vary from 10 mbaud down
to 9600 baud.

Network packet sizing of 256 bytes

Network packet sizing from 30

bytes to 1500 bytes at Ethernet

What are some of the real differences

Lonworks

BACnet

Network manager per island of

There is no master controller,

control, only one master

system architectures vary in

degrees of distributed control. Not a
BACnet limitation

Priority level of control is limited to

16 levels of priority from Manual

predefined profiles

life safety, operator commands,

general control languages etc.

Pricing varies depending if the

MS/TP is very inexpensive and

application required can be supported

doesnt require a second processor

directly by the Neuron chip. If not a

Ethernet and Arcnet have separate

second processor must be added.

network chips thus more expensive

Only manufactured by limited set of

Standard chips mean mass

companies

production

What are the different network topologies

Network Topologies - A

Attempts to adapt to the

BACnet to other systems

industry standard
System is still proprietry

proprietary messages over

LAN

Connects two dissimiliar

controller

systems at the OWS level

controller

Proprietary network
segment

Configuration A

Network Topologies - B

BACnet to other systems

Attempt to adapt
Lonwork

Proprietary messages over

LAN

System is still proprietary

when you want to do an
expansion
May have limited
capabilities through

Gateway
controller

controller

Lonworks network
segment

Gateway
Configuration B

Network Topologies - C

Customer can now

interoperate different

BACnet

manufactures systems
May not have the network

Gateway

bandwidth (performance) at

controller

the subnet level

controller

Lonworks network
segment

Configuration C

Network Topologies - D

Customer can now

interoperate different

BACnet

manufactures systems
Provides for Lonwork islands

controller

of control

controller

BACnet network segment

Gateway
Lonworks

Configuration D

When you see this symbol

BTL MARK

you know it works!

BTL
BACnet Interoperability Workshops
A behind closed doors event that promotes the
advancement of our industry and the standard
Two workshops to date

BTL Product Testing and Listing

Limited testing abilities at this time
Testing simple devices first and then
progressing to the more complex devices

Two Websites
http://www.bacnetassociation.org/

BMA Website
(the claims)

BTL Website
(the tested facts)

Web Based Access

Delta ORCAView Web Server

Designed for remote access from the web
Provides for Tenant Portals
Wireless and PDA