BACnet vs.

LON Open Discussion Seminar

12/06/2005
LON Presenter: Ron Bernstein LonMark Americas ronb@lonmarkamericas.org BACnet Presenter: Bob Johnson ASHRAE BACnet Committee robjohnson@siemens.com

Moderator: Ryan R. Hoger Illinois Chapter Secretary ryan.hoger@tecmungo.com

LONMARK International
Open Systems Overview

What Keeps People Awake At Night?

Facility Manager Concerns

Operational costs Leveraging investments Revenue generation Facility comfort Regulatory compliance Improving productivity Risk management Safety & security

Specifier Concerns
Litigation Education and training Erosion in fees Tying into legacy systems Coordination of OEM controls Developing and managing an integrated BAS specification Keeping up with

Integrator/Contractor Concerns
Multi-vendor tech support Competitive products Training and education Meeting specifications Product quality Sourcing product Vendor selection Expanding beyond legacy systems Developing a

Open Systems Is The Thread That Ties Everything Together?

Greater choices in vendors and suppliers Increased business opportunities New revenue opportunities Happier building owners and tenants Cost savings

Open Systems Deliver

Freedom to choose now or later
Suppliers Products Systems Integrators Maintenance and support

Open Systems Defined

Open building systems are created using the products and systems from multiple vendors that in the end offer greater flexibility, easier management, higher levels of scalability, and lower life cycle costs.

Traditional Closed System

Single vendor Leads to costly service and system expansion Limits sub-system expansion Limits number of service providers Restricts interoperability with other vendors / systems Limits choices Creates Islands life of the system ! Locks owners in for the of automation

Open System
Multiple vendors Affordable and economical service and system expansion Sub-system and devicelevel expansion at any time Full choice of service providers Facilitate interoperability with other vendors / systems Plethora of choices Flexible, expandable automation Owners retain freedom of choice throughout the lifetime of the system !

What is the LONW ORKS Platform?

Key Concepts
Networks extend beyond computers
Sensors Actuators Controllers Interface panels Displays

Control networks benefit everyone Solutions available for every industry

Industrial controls Building automation Transportation Manufacturers System integrators End-users

Key Terms
LON Local Operating Network The LonTalk Protocol
A device network for control, sensing, and monitoring systems A Protocol designed for use in control networks A published, open standard (ANSI/EIA-709.1, ISO in process) Imbedded in silicon as the Neuron Chip from Cypress Semiconductor and Toshiba Fully backwards compatible since 1990 A family of hardware and software products Supports development and use of control networks An umbrella name for the technology created by Echelon An independent trade organization Dedicated to facilitating interoperable products A Network Operating Systems for managing LONWORKS Networks

The LO NWORKS Platform

LO N MARK Interoperability

LNS LO NWORKS Network Services

SNVTs Standard Network Variable Types SCPTs Standard Configuration Property Types

What Is A Protocol?

Sensor

Actuator

A protocol is the set of rules and procedures intelligent devices use to communicate with each other

The LonTalk Protocol

Sensor

Actuator

Predictive P-persistent CSMA with Optional Collision Detection and Optional Priority Development started in 1983 Cast into silicon in 1990 No changes Fully backwards compatible

http://www.echelon.com/solutions/ opensystems/papers/ovrview.pdf

The LonTalk Protocol

Standards Associations ANSI EIA-709.1 SEMI
Sensor Actuator

IFSF AARR ASHRAE SPC-135 IEEE CEN (ISO in process) LONMARK

Scalability
127 Nodes/Subnet 255 Subnets/Domain 248 Domains/System =127*255*248 =32385x248 nodes/system
Sensor Actuator

??? Systems/Enterprise

Features: Small to Large System Scalability Single Network Database Common Network Tool Set Peer-to-peer Communication Reduced single point of failure

The ISO OSI 7 Layer Protocol Model

OSI Layer
7 6 5 4 3 2 1
Application Presentation Session Transport Network Data Link Physical

Purpose
Application Program Data Interpretation Remote Actions End-to-End Reliability Destination Addressing Media Access & Framing Electrical Interconnect

Services
Standard objects & types, config props, file xfer, network services Network variables, application messages, foreign frames Dialog, remote procedure calls, connection recovery End-to-End acks, service type, pkt sequencing, duplicate detect Unicast & multicast, destination addressing, packet routing Framing, data encoding, CRC, media access, collision detect Media specific details, xceiver type, physical connect

International Standards Organizations Open Systems Interconnect Model - www.iso.org

The Core Technology Cast Into Silicon

Layers 1-6 are standard Operating System Run Time Software I/O Device Controllers EEPROM RAM ROM Network Transceiver Interface Microprocessors Serialized ID

l l l

MicroController

l l l l l l l

The LonTalk protocol is imbedded in silicon providing reliable The LonTalk protocol is imbedded in silicon providing reliable communications & processing available from multiple suppliers communications & processing available from multiple suppliers

10

LONWORKS: A Control Networking Technology Platform

Intelligent devices, nodes :

(Actuators, sensors, controllers, equipment)

Communicating using a common protocol ...

Over one or more media.

ANSI EIA-709.3 Free Topology Transceiver EIASimplifies Network Wiring

Polarity Insensitive Loops Buses Star Tree Daisy Chain Any combination of wire 500 meters 64 Nodes

11

MultipleMultiple-Channel Networks Connected with Routers

LONWORKS Routers

True Layer 3 Routing transparent to network devices Intelligently filter network traffic Extend network length Increase maximum device limits on channels Available from multiple vendors for a variety of media types Not a Gateway!

Router

Router

A Single Cohesive Network With EIA-852 Routing

248.17.15.44 131.1.10.6 243.47.185.9

Internet

IP Routers

Company WAN

143.77.105.27

53.107.155.9

12

Typical LonTalk Packet

Packet encoding and size optimized for control
Layer 2 Header Layer 3 Address Information Layer 4 Service Type Layer 5/ 6 Header DATA Layer 2 CRC 2 Bytes Network Variable Selector Service Type ID Transaction Num Addr Format, Domain Length Source Addr (Subnet/Node) Dest Addr (Group) Domain ID (Zero Len Domain) Backlog Priority Alt Path Unsigned Long 2 Bytes 2 Bytes

1 Byte 1 Byte 2 Bytes 1 Byte 0 Bytes 1 Byte 12 Bytes

Command vs. Event-driven Systems Event The old way: command-driven systems require software and device modifications whenever a change is made ON/OFF Command

The right way : event-driven systems in which sensors publish information, and actuators subscribe to the information of interest to them. Data are exchanged using network variables: data from different manufacturers can be exchanged with a common interpretation
Room Temp Temp Set Point

Motion Detector

Lamp

Temp Sensor (Made in USA)

Boiler System (Made in Europe)

Set Point

23
Setpoint Display (Made in China)

13

Adding Devices To An Event-Driven System Event-

Motion

Room Occupied Brightness

Feedback

Motion Detector

Lamp
0% - 100% Key Code

Control Knob
Intruder Arm / Disarm

Alarm

Key Pad

Alarm Bell

Devices are logically connected (bound) together without affecting the application program in the device

Why is LONMARK Important?

Because the Market says so

14

How Mature is the LONWORKS Market?

We have been here

Technology Adoption Life Cycle

Source: Crossing the Chasm By: Geoffrey A. Moore

Open Systems Market Share Consistent with the Technology Adoption Life Cycle

LONWORKS Moving to Widespread Global Acceptance

Now moving here

Open Systems Market Share Consistent with the Technology Adoption Life Cycle

rity ajo M rly Ea s ter op Ad rly Ea rs ato ov Inn s ter op Ad rly Ea rs ato ov Inn rity ajo M rly Ea

rity ajo M te La
Other (Propreitary)

s ard gg La
Total Available Market
Open Systems

Technology Adoption Life Cycle

Source: Crossing the Chasm By: Geoffrey A. Moore

s ard gg La
Total Available Market
Open Systems

rity ajo M te La
Other (Propreitary)

15

Proof of Global Market Acceptance

Formal Industry Standards
Controlled by ANSI Industry Standard EIA 709.1 XML and OBIX standards for the IT world Interoperability Guidelines to CEN for inclusion in EN 14908 standard Working with CECED (appliances) and IFSF (forecourts) on European standards Supporting global ISO standards initiative for LonTalk and L ONM ARK Many others Thousands of installations in buildings, homes, transportation, more Over 50 million installed devices (worldwide) Some of the worlds largest end users are specifying L ONWORKS L ONM ARK International a driving force worldwide 100s of Manufacturers 1000s of products available 1000s of System Integrators/Installers 10,000s of systems installed Multiple markets and applications supported

Market acceptance and momentum

Mechanism to own and foster improvement and promotion

Strong support from enablers

Reality of Open Systems Engineers Perspective

Provide Increased Level of Service Engineer the project 100% upfront Enhance performance through integration Create value for the owner
Competitive bids throughout the lifecycle of the facility Reduction in lifecycle costs Eliminate sole source procurement requirement Maintain consistency across multiple facilities Knowledge of technology applications is critical

Design a system that meets client expectations

Not performance specifications Enhance professional service offering

Happy Clients = Recurring Business

16

LONMARK International
Foundation for Open Systems

LONMARK International Overview

Eleven year old industry association Non-profit corporation Governed by independent board of directors Over 300 member companies worldwide Promote the L ONMARK standard through marketing activities Tested and certified nearly 700 devices and controllers Marketing resource for members to promote their products and services

17

LONMARK Membership
Europe 26%

Americas 45%

Asia Pacific 29%

Membership is open to any manufacturer, end-user and system integrator committed to the development and use of open, interoperable products using ANSI/EIA/CEA 709.1 and related standards including European standard EN 14908.

LONMARK Affiliates
Active
Americas Denmark Japan Switzerland UK Adriatic Australia China Germany Korea Russia

In Progress Interested
France Italy Netherlands Poland Sweden

18

LONMARK Americas (LMA)

First L ONMARK affiliate Formed in September 2004 as non-profit mutual benefit corporation Over 130 member companies Focus on local market issues and opportunities Mission: To enhance the success of our members through the education

LONMARK Devices Deliver Interoperability

LONMARK International provides
Powerful forum for end-users, integrators, specifiers and end-users to define industry requirements = equal voice Defines device SNVTs, Objects, Profiles, and System Interoperability design guidelines Product verification and conformance testing Integrator certification
www.lonmark.org

LONMARK certification means devices will interoperate

19

LONMARK Certified Products

700 600 500 400 300 200 100 0
1995 1997 1999 2001 2003 2005*

*includes certifications in process

LONMARK Open System

Management Interface SOAP/XML Web Services Systems Integrator

Connectivity Devices Network Software & Unified Network Tools Database

20

New Technical Developments

Profile Development
Creating profiles for ISO 16484-3 Creating profiles for programmable controllers Creating new profiles for chillers and drives Implementing ISI profiles for home automation and refrigeration

System level expansion

Creating network tool standards Creating connectivity standards for network interfaces, routers and gateways Creating web services standards using oBIX / OASIS

LONMARK & BACnet

A Comparison

21

Comparing Apples & Oranges

LONMARK and BACnet have very little in common Different origins: technology vs. specification Distinctive network architectures Diverse hardware and software requirements

Comparing BACnet and LONMARK

System architecture System and device characteristics Conformance testing and certification Product selection Network management and diagnostic tools XML and Web services Standards support

22

Historical Comparison
1988 Technology invented 1994 LO NMARK Organization formed 1995 1st certified product 1997 LNS 1.0 released 1998 100 certified products 1999 ANSI/EIA standard 1999 200 certified products 2001 300 certified products 2002 Address space increased through ANSI 2002 400 certified products 2004 670 certified products/co-founded oBIX 1987 ASHRAE committee formed 1995 BACnet 1995 Released 2001 BACnet 2001 Released 2002 BTL begins product testing 2002 1st tested product 2002 - XML Work Group established 2003 Becomes ISO Standard 16484-5 2003 32nd tested device 2004 70th tested device

Protocol and Media

Mono protocol
EN 14908 ANSI/EIA 709.1

Multi protocol
Ethernet ARCnet MS/TP (RS 485) PTP (RS 232) LonTalk

Media independent
Free topology Bus topology Power line Fiber optic Wireless

IP tunneling

23

Network Architecture
A bottom up solution focused on device interoperability Open protocol Peer-to-peer network topology Supports tiered architecture A top down solutions focused on HMI integration Open standard Tiered network topology

Master/Slave Architecture (BACnet)

Server Remote Facility Sites
BACnet via Modem

Intranet / Internet IP Network

Source: Automated Logic

BACnet Router Native BACnet Portal BACnet Router

BACnet MS/TP

Other Mfgs BACnet Device(s)

S-Line Controller

Fire

Lighting

Boiler

Chiller Security

Zone Controller

M-Line Controller

Proprietary Equipment/Systems

24

Peer-to-Peer Architecture (LONMARK)

Source: Tour Andover Controls

Mixed Architecture

BACnet

Third-party Modbus Device Third-party Modbus Device

Modbus

LonTalk

Source: Trane

Third-party Modbus Device

25

System and Device Characteristics

LO NMARK International publishes guidelines for physical layer, application layer and product certification requirements Applications published via functional profiles, which define mandatory and optional data elements LO NMARK Functional Profiles (LFP); 69 published; 30 in development Standard data types (SNVT and SCPT; 168 and 279 published respectively) Standards set by ASHRAE; permit vendor to select which standard properties to use for functions to be supported Defines (23) standard objects (rather than functions) which have required and optional properties Provides Interoperability building blocks across 5 defined areas of interoperability (BIBBs: 56) Defines standard property identifiers (166)

Conformance Testing and Certification

LONMARK International BACnet Testing Laboratories (BTL) certifies devices test and verify through web-based manufacturers certification and selected use of BACnet verification tool Tested products Certified products appear at appear at http://bacnetassoc www.lonmark.org iation.org/btl/defa 670 products certified ult.htm 75 products tested (thru 7/05) (thru 1/05)

26

Product Availability Snap Shot

Access Control - 71
Source: Echelon Corp.

Mechanical Devices - 47 Motor control - 45 Network Management - 55 Plumbing & Irrigation - 12 Power Management - 69 Refrigeration - 46 Security - 130

Actuators - 123 Asset Management - 5 Doors/Windows/Sun Blinds - 103 HVAC - 282 Hospital Equipment 54 Human Machine Interfaces - 95

Life/Fire/Safety 40 Lighting Control 337 Network Infrastructure - 446

Sensors - 168 Software Applications - 79 Wiring Devices - 58

Network Management and Diagnostic Tools

Design, Installation and Commissioning tools
Available from manufacturers and independent vendors Tools permit installation of multi-vendor products

Design, Installation and Commissioning tools

Available from manufacturers only; not independent vendors Proprietary tools do not permit installation of multi-vendor products

Network Diagnostics
Software tools available from manufacturers and independent vendors Tools permit diagnosis of multi-vendor product networks

Network Diagnostics
Software tools available from manufacturers only; not independent vendors Proprietary tools do not permit diagnosis of multivendor products

27

Operator Interface Software

LNS used as HMI communication standard Multiple native LNS HMI solutions Open communication supported through DDE and OPC servers XML and web BACnet intended for use at operator level Several native BACnet HMI solutions Most solutions are manufacturer specific Most HMIs use IP or ARCNET

XML & Web Services

EIA-852 LON/IP tunneling OASIS oBIX standard for web services Many standard products produce native XML All LONMARK SNVTs, SCPTs and profiles available in XML Remote configuration

BACnet XML extending ASHRAE standard Developing automated remote configuration standard Supports BACnet and LONMARK objects

28

Standards Support

ANSI/EIA 709 EN 14908 European standard IEEE 1473 SEMI E54.6 EIA-852 LON/IP tunneling OASIS oBIX web services standard (in progress) ISO/IEC (in progress)

ASHRAE 135 ISO 16484-5 CEN-TC 247 (in progress) Korean National standard

Benefits of Integrated Systems Using Open Standards

Multi-system integration delivers:
Common technical solution results in Less engineering Less training Multi-vendor interoperability delivers Customization of applications Infinite customer solutions Increased reliability and maintainability More efficient use of infrastructure Economic upgrade and migration path Lower costs (for engineering, training, spares inventory, etc.) More transparency of his technical installations Less vendor dependency More efficient building operation

Building operator receives:

29

LONWORKS Delivers
A common communication standard Extensive choice for integrated building solutions
HVAC Life safety Security Lighting Gen sets And more . . .

Global standard
Widely adopted Vendor independent Open Suitable for all types of commercial buildings

Scaleable

Conclusion
Succeeding In An Open Systems World

30

Benefits of LONMARK Open Systems

Reduced cost
Competitive bidding and multi-phase procurement Healthy competition among suppliers and integrators Competitive options for system expansion Standardized and published interfaces Best of breed products and solutions Extends beyond HVAC lighting, sun blinds, boilers, gen sets, access, life safety . . . Scaleable architecture future proof

Increased value

Resources
LONMARK Organization Open Systems Alliance
http://osa.echelon.com www.ansi.org www.iso.org www.lonmark.org www.lonmarkamericas.org

LonTalkProtocol Details White Papers, Documentation, and more Chip Manufacturers LONW ORKS Distributors
www.engenuity.com www.toshiba.com www.cypress.com www.echelon.com

31

Contact Information

Ron Bernstein
Vice Chairman, LONMARK Americas 204 N. El Camino Real #E242 Encinitas, CA 92024 858-756-9923 408-790-3492 fax ronb@lonmarkamericas.org

Overcoming The Myths

Common Questions With Simple Responses

32

LONWORKS Is Not Scalable

Rappongi Hills, Tokyo Worlds largest stand-alone LONW ORKS enabled building project
16,500 LO NWORKS devices primarily hvac&r 2 759,100 m Over 20% savings in energy costs over projection Four zones, 13 Buildings

Mori Tower; Four residential towers

Over 170,000 points monitored LONWORKS/IP integration using i.LON servers Mori Building general developer/operator
Urban developer operating more than a hundred buildings Extensive use of LO NWORKS planned for worlds tallest building Shanghai World Financial Center

LONWORKS Is Not Suitable For Large Projects

Multi-sourced product availability, ability to support phased system implementation, use of an open standard, and a common tool chain sold the U.S. Army Corps of Engineers
The single most important reason is its capability to support design and specification of a system that could be implemented in an open

33

There Is No Standard Specification For LONWORKS

Reference material available from
LONMARK International
www.lonmark.org

U.S. Army Corps of Engineers

http://www.hnd.usace.army.mil/UMCS/UM CSIIContractInfo.aspx

BACnet Offers A More Complete Solution

Feature
Open standard technology Flat system architecture without proprietary gateways Peer-to-peer device exchange HVAC, security, and fire support Energy, metering, transportation system support Weather, water, waste water, power generator support Monitoring and operating values Time program, grouping, trending Product certification program Rules -based certified interoperability program Web-based certification tool Suitable for high data volume, complex function devices Proven scalability Self -installation option Back-up / restore tools Remote device management IT compliance (IP, Ethernet) Common device and network management tools Common device and network diagnostics tools Implementation cost per node

BACnet LONW ORKS

Low

?

Medium-High

34

More Comparison Data

LONWORKS Certification process available and well defined Many devices available
Not all encompassing

BACnet Conformance testing process available but incomplete Fewer devices available
Not all encompassing

Application specific controllers are common Single platform/tool for device configuration possible Peer-to-peer architecture w/single media Less defined supv. functions
Fewer options/functionality Alms/scheduling/trends

Programmable controllers are more common Multiple vendor-specific tools required for device configuration Hierarchical architecture/media More defined supv. functions
More options/functionality Alms/scheduling/trends

Standard database/mgmt available Easier to understand/specify Can be proprietary

Proprietary databases/mgmt Difficult to understand/specify Most systems proprietary

BACnet Is Less Expensive

Hardware cost is typically only 20 to 25% of a projects cost. Software tool ease of use and capabilities of the project personnel are the dominant factor in project costs. Most BACnet jobs are single vendor solutions delivered in a proprietary way.
Products are given away to win maintenance agreement The programmable controllers have to be programmed. The applications specific devices have to be configured. Devices have to be addressed. Network data flow has to be established. The Operator Work Stations have to be set up. Reports have to be created.

There are certain functions that have to be accomplished to complete a system

Creating an accurate cost model is extremely difficult

35

The LonTalk Protocol Can Only Run On A Neuron Chip

The LonTalk protocol can, and has been ported to run on other Microprocessors including those from Intel, Motorola, Toshiba, and others

Echelon Controls The LonTalk Protocol

The LonTalk protocol is under the control of different standards organizations, including ANSI, CEN and soon ISO The protocol is available on the ANSI website www.ansi.org

36

Echelon Charges A Royalty For Every Device Sold

Echelon administers the unique 48bit ID in each Neuron chip and charges chip licensees an insignificant administration fee Porting the protocol to any processor does not require obtaining a unique ID, hence no fee is necessary

LNS is a Proprietary Network Operating System

LNS (LONWORKS Network Services) an open network management and database structure developed by Echelon for the management and maintenance of LONW ORKS networks. Anyone can implement an LNS application or Plugin. LNS based applications and Plugins are available from dozens of sources in the open market. No one company has greater access into the LNS structure than any other company (including Echelon). The LNS network management database and network management structure is openly documented and accessible to anyone.

37

XML/Web Services Will Replace LONWORKS At The Device Level

XML usually runs on Ethernet which is not designed to provide the services, performance, addressing, messaging types, security, or reliability required for control networks There will be a need for a device level communication protocol for long into the foreseeable future There is a greater risk to BACnet which relies heavily on Ethernetlevel communications

You Must Pay Echelon For Every Node Installed On Network

You can install an entire L ONWORKS network without ever buying anything from Echelon Echelon chose to provide a very low cost tool to the market and scale the cost based upon usage and, hence, making an extremely cost effective, scaleable tool set. Other manufacturers have developed competitive tools and have their own pricing structures that have no Echelon royalties

38

You Must Use Gateways To Connect More Than 128 devices

LONWORKS networks can contain up to 32,385 devices on one domain with up to 248 domains per system in a flat, peer-to-peer network No gateways or tiered architectures are required to scale a L ONWORKS network

LONWORKS Does Not Support Scheduling,

Trending, Alarming and Data Logging

Most suppliers implement their own solutions for scheduling, trending, alarming and data logging either at the controller or in the HMI LONMARK International has published standards in this area and is actively developing additional solutions

39

Writing Open Systems Specifications

A Survival Guide

Ensure Openness
Learn the technologies, options, and market directions Make sure you are getting a real Open System Verify you will not be locked in on any level of the system Encourage multi-subsystem integration for maximum efficiency Start from good open specification framework

40

Include All Essential Network Components

Devices
The controllers on the network Applications specific devices Programmable devices Packaged equipment Scheduling, Alarming, Data logging

Tools
Design Tools Commissioning Tools Database issues Plugins Scheduling, Alarming, Data logging

Infrastructure

Host Interface

PC Based The wire the nodes connect to Web Based The routers that pass the data Flexibility and Choices Termination Enterprise Connectivity Traffic issues IT Interface Systems architecture Large project architecture Design for the future IT Routing Scalability issues When are gateways necessary?

Dont get locked in!

LONMARK Devices
LONMARK Device Specifications
LONMARK (SNVTs, SCPTs, and object Model) LONMARK Device Profiles LONMARK Guidelines for Manufacturer Specific Features

LONMARK Device Certification

Application Specific Devices Freely Programmable Controllers

41

Device Specification Guidance Controller Selection

All application specific devices shall be L ONMARK certified. Controllers must support an ANSI/EIA/CEA 709.3 network interface, the FT-10 channel. Controllers from multiple manufactures may be used to meet the system specification.

Device Specification Guidance

LONW ORKS based, non-LONMARK Certified Controllers
Such as:
freely programmable controllers gateways

These devices often have changeable network interfaces. Often these device are not yet certified These device must either:
Support the standard LO NMARK node dynamic interface. (Preferred choice) Or Supply an interface XIF file for a valid static interface device definition. This XIF should satisfy LO NMARK node interface certification requirements. Note allowing this option may require additional network reconfiguration steps with some network tools. This is considered a legacy device support allowance for changeable type devices.

42

Device Specification Guidance

Specify certain LONMARK Functional Profiles or even a set of profiles to satisfy system control requirements.
8010 (VAV Controller) 8020 (Fan Coil Controller) 8060 (Thermostat Controller) 8030 (Roof Top Unit Controller) Constant Volume Airhandler

Specify Standard Generic LONMARK Objects for other control system requirements
Sensor Object Actuator Object Controller Object

Device Specification Guidance

All devices with user defined network variable types (UNVTs), must be supplied LONMARK resource files that define formatting for these UNVTs. Require application plug-in support for a standard network management tool for certain or all devices.
VAV controllers RTU controllers Devices with UCPTs (User defined configuration properties) Plug-ins may not be required for devices that use standard SNVT, SCPT, and generic LO NMARK objects to implement functionality.

43

LONMARK Infrastructure
LONMARK Channels
Channel Types Media / Wire Termination / Wiring rules Channel Design Specifications

LONMARK System Message Routing

709.1 Routing 852 / 709.1 Routing

Other Application Layers and Gateways

Multiple System Object Models (Application Layers) Specification Guidance

Specification Guidance Infrastructure (Media / Wire)

LONW ORKS /IP Channel
Use IT wiring standard references. IP Backbone
(Switched 100Mbit,Gigabit Ethernet)

TP/XF-1250 Channel
Junction Box and Wiring Guidelines for Twisted Pair LONW ORKS Networks Echelon Engineering Bulletin
http://www.echelon.com/support/documentation/bulletin/005-0023-01M.pdf .

FT-10 Channel
Junction Box and Wiring Guidelines for Twisted Pair LONW ORKS Networks Echelon Engineering Bulletin
http://www.echelon.com/support/documentation/bulletin/005-0023-01M.pdf .

PL-20 Channel
per manufacturer specifications

44

Specification Guidance Infrastructure (Message Routing)

709.1 routers should be used to connect multiple channels of L ONMARK devices in the system. This creates a logically flat network (like the Internet). Use gateways for legacy system interfaces. System shall be implemented using peer-to-peer communication, without requiring a host or zone controller to

Specification Guidance
Infrastructure (Message Routing) EIA 852/709.1 routers shall be used to route LonTalk messages over IP between twisted-pair L ONMARK channels. Use gateways for:
Legacy system interfaces Web services interface Web page interfaces Other required application layer support

System should be implemented using peer-to-peer communication, without requiring a host or zone

45

Network Tools and Front Ends

Tool and HMI Connections
Windows Workstations (with Web gateway) Laptop computers

Thin (Web) Clients

LONWORKS /IP Backbone

(LAN-Switched 100Mbit,Gigabit Ethernet or WAN/Internet)

Network Tools and Front Ends

Tool and HMI Connections
HMI Tool Commissioning tool Thin (Web) Clients

Network Database

LONWORKS /IP Backbone

(LAN-Switched 100Mbit,Gigabit Ethernet or WAN/Internet)

Network Database

Shared or Interchangeable database

46

Specifying Tool Functional Support

Specify the functions you require:
Network commissioning. Network variable read and write control and monitor capability. Manufacturer supported configuration plug-in standard. System application support (Scheduling, Alarming, Data logging). General Device configuration management. Basic diagnostics of devices. Support LO NMARK standard resource files. Upgrading device firmware. Advanced low-level diagnostics of devices.

And where you require them supported:

from any IP connected PC workstation over a standard 852 connection. from any 709.1 channel direct connection to all device on all channels from any IP connected device via a web page. from any IP connected PC via web services.

Network Tool Guidelines

All devices (nodes) on the network should be installed and configured using a standard network management tool. Network Management tool should support device plug-ins. This may be specific to
a network application framework.

Sourcing requirements. Tools must be available from multiple (N) sources.

47

Specification Guidance Network Tools

Network tools must support:
Standard LONMARK resource files Read in XIF file from device or from file.

See L ONMARK system definition for more suggested specifications.

Specification Guidance Network Tools

Any host PC GUI interface shall use openly available software packages that are non-exclusive. Devices must communicate to the GUI workstation using Standard Network Variable Types (SNVT) Standard Configuration Property Types (SCPTs) as defined by LONMARK. No non-standard communication to

48

Specification Guidance Network Tool Ownership

All configuration tools, installation tools, network management tools, plug-ins, databases, software shall remain with the job and be owned by the property. All software tools shall be properly licensed and conveyed at contract sign-off. When in doubt, ask!

Specification Guidance Integrator Qualification

Work shall be performed by a qualified network integrator. Network integrator must have technical staff members who have attended at least 40 hours of LONW ORKS network design and network management tool training. Must have IT connectivity and network troubleshooting experience. Shall provide references of prior successful experience. Must demonstrate ability and intent to design, architect, and install a open, flat, LONWORKS system and have on staff at a minimum two technically trained members.

49

System / Network Verification

The system integrator shall provide a protocol analyzer log summary for each channel for a minimum of 24 hours showing system performance. The statistical summary shall show that all bandwidth utilization and error limits are within acceptable ranges and that there are no network traffic problems, node communication problems, or system sizing problems.

Writing Open Specs

Dont write generic open specifications BACnet and L ONWORKS can be implemented together, but it creates greater problems Most BACnet jobs are delivered in a proprietary way
Vendor specific controllers Vendor specific head-end Vendor specific maintenance agreement

Most BACnet controllers are not interoperable nor interchangeable Connectivity is complex and risky

50

The International Standard Protocol for Building Automation and Control Networks
Bob Johnson Software Engineer System Architecture and Applications Siemens Building Technologies Buffalo Grove, IL robjohnson@siemens.com

BACnet Facts
Initial development and continuous enhancement by ASHRAE committee SPC/SSPC-135 since 1987. ASHRAE guidelines guarantee open membership to both end-users and producers. Specification additions and enhancements are subject to public review and comment. Adopted by ANSI, ISO and CEN (ISO 16484-5). Freely distributed. No licenses required. Technology and hardware independent. Used worldwide by hundreds of vendors.

51

BACnet Working Groups

Utility Integration Lighting Life Safety

Objects and Services

XML IP MS/TP Applications

Network Security

BACnet Interest Groups Worldwide

52

BACnet Testing Resources

ASHRAE Standard 135.1, Method of Test for Conformance to BACnet. - Provides detailed compliance test procedures. - Supports pre-testing. BACnet Testing Laboratories (BTL) - Performs formal testing of BACnet devices using SSPC-135.1 Test Procedures. - Assures compliance to the BACnet Standard . - Awards BTL Listing to compliant devices. BTL Plugfest - Permits vendors to test their BACnet products with BACnet devices from other vendors . - Last year more than 75 BACnet engineers representing 22 companies attended. - Round-table testing added in 2005.

Historical Situation Custom Integration Traditionally, several tools have been available to implement custom integration, such as...
Standard Protocols (Modbus, OPC, ...) Vendor-Specific Open Protocols Custom Gateways Integration Workstations ...

53

Transitioning to BACnet: Islands of Automation

Migration to a BACnet solution and integration of non-BACnet devices results in a mixed architecture.

State of the Art Complete BACnet Solution

A complete BACnet solution includes BACnet Workstations, Building Controllers , Field Controllers , HMI Devices and Tools

54

The Main Elements of BACnet

Objects

Represent data and application functionality Data exchange, event notification, commands Networking Technologies

Services

Transports

55

An Example BACnet Object

A BACnet Object is more than just a value...

Property Object_Identifier Object_Name Object_Type Present_Value Status_Flags

Event_State State_Text Priority_Array

Multistate Value

Relinquish_Default Notification_Class Alarm_Values Event_Enable Notify_Type Event_Time_Stamps

Value MV:1 "Conference Room L5 Mode" Multistate Value Occupied In_Alarm False Fault False Overridden False Out_Of_Service False Normal "Unoccupied", "Occupied", "Standby", "Emergency" Manual-Life-Safety -Automatic-Life-Safety -Critical-Equipment-Control -Minimum -On-Off -Manual-Operator -Peak-Demand-Limiting -Schedule Occupied Unoccupied 7 Emergency To-Offnormal Event 10:40:00, Oct 5 2005 -10:50:00, Oct 5, 2005

BACnet Services Versatile standard services for: Alarm & Event Notification
Acknowledgement, Reset, Status Synchronization

Object Access Functions

Read and Write of property values and data buffers

File Transfer Functions

Transfer data files to and from devices .

Management Functions
Discover devices and objects, initialize devices, communications control

56

BACnet Transports BACnet supports multiple networking technologies and transport protocols. Ethernet IP Point-to-Point MSTP (EIA-485) ARCnet LonTalk (ANSI 709.1) New transports may be added as needed... In addition, BACnet Web Services is in the final stages of the standardization process!

Profiles and Protocol Conformance Standard device functionality packages and functional tests are defined by the BACnet committee. Conformance is certified by the BTL. BACnet Interoperability Building Blocks (BIBBs)
Standard packages of object and service requirements for specific features, such as Data Sharing, Alarm and Event Management , Scheduling, Trending, Device and Network Management .

Device Profiles
Standard packages BIBBs for various classes of devices , such as Building Controllers, Application Specific Controllers, and Workstations.

57

BIBBs and Profiles Example Profile - BACnet Building Controller (B-BC)

Object and service requirements :
Interoperability BIBB Area Data Sharing DS-RP-A,B DS-RPM-A,B DS-WP-A,B DS-WPM-A,B Alarm & Event AE-N-I-B Management AE-ACK-B AE-INFO-B AE-ESUM-B Scheduling SCHED-E-B Trending Device & Network Management TM-VMT-I -B T-ATR-B DM-DDB-A,B DM-DOB-A,B DM-DCC-B DM-TS-B or DM-UTC-B DM-RD-B DM-BR-B NM-CE-A Description Read Property Read Property Multiple Write Property Write Property Multiple Generate Alarm & Event Notifications Process Acknowledgments Provide Current Event State Summary Provide Current State of All Event Reporting Objects. Provide Time and Date Scheduling for Objects on the Local Device and Other Network D evices. Provide Trend Logging Services. Provide Trend Buffer Status Notifications. Device Discovery Services. Object Discovery Services. Execute Communications Control Requests. Execute Time Synchronization Requests. Execute Reinitialize Device Requests. Execute Backup and Restore Requests. Establish and Terminate Network Connections.

BIBBs and Profiles Example BIBB Device Backup and Restore

The device shall provide its configuration file (s) for upload and allow the file(s) to be written to recover its configuration.

BACnet Service AtomicReadFile AtomicWriteFile ReinitializeDevice

Initiate

Execute x x x

Device Management-Backup and Restore-B (DM-BR-B)

58

Device Profiles The BACnet standard specifies profiles for:

Operator Workstation B-OWS

Application Specific Controller B-ASC

Protocol Implementation A Protocol Implementation Conformance Statement (PICS) indicates the capabilities of a BACnet device. Manufacturer, model, and versioning information Supported networking technologies and transport protocols Supported services Supported object types Supported character sets

59

Every Major Controls Vendor Now Supports BACnet

BMA BACnet Vendors

Other BACnet Vendors

BACnet Resources

www.ashrae.org www.bacnet.org

www.bacnetassociation.org

www.bacnetassociation.org/btl

60

Thanks for attending, See you in January 2006!

Short Intermission, then Return for Open Discussion

12/06/2005
LON Presenter: Ron Bernstein LonMark Americas ronb@lonmarkamericas.org BACnet Presenter: Bob Johnson ASHRAE BACnet Committee robjohnson@siemens.com

Moderator: Ryan R. Hoger Illinois Chapter Secretary ryan.hoger@tecmungo.com

61