©2003 Echelon Open Systems for Building Control

2 Agenda Introduction The Value of Open Systems Open Systems Defined L ON W ORKS ® & BACnet – A Perspective Specifying Open Systems Summary

©2003 Echelon Introduction Device Networks

4 Imagine a world where everything is smart

5 where everything is connected

6 All Kinds of Everyday Devices White goods Heaters and air conditioners Lights Pumps and motors Electricity meters Security systems Train brakes Gates and garage doors Conveyor belts Medical alarms Window shades Elevators

7 That Interoperate to Lower Cost, Add Value, Increase Comfort Completion of drying cycle flashes lamp inside home Time of day pricing change changes defrost cycle Motion alarm triggers lamp and generates remote alarm message Away mode of thermostat changes hot water temperature to save energy Activation of TV lowers room lights

©2003 Echelon The Value of Open Systems

9 Market Drivers Owners are dissatisfied with the costs of proprietary systems –Sole-source maintenance contracts –Other operational expenses associated with energy consumption and moves/adds/changes dictate a need to introduce more efficient and cost-effective systems

10 Market Drivers Economic climate dictates focus on productivity –Efficiency demands better value, faster innovation, smarter investment Homeland Security post 9/11 demands Vigilance –Want to know “everything” going on inside “every” building –Insecurity drives desire for integrated Enterprise systems Rapidly changing technology enables disruptive changes in the building automation landscape –The Internet, Web services, ubiquitous communication technologies create expectation of real time information – “everywhere”, “all the time” Demand for Open Systems –Some Specs are now requiring it –Market and Competition is growing

11 Industry Response Focus placed on developing standards that define open systems –The leading standards are associated with BACnet and L ON W ORKS Systems

12 Industry Response All major players deliver products or systems that conform to one or more established open system standard –Many continue to invest and update proprietary product lines Traditional players provide integrated systems (open and proprietary) and web-based access Significant advances made in security equipment and integrated systems Tech-savvy non-traditional players are entering the market

13 Open Systems Promise Owners are attracted to the “Promise” of Open Systems – Better Value for the Entire Building Life Cycle – More and better choices – Faster Innovation

©2003 Echelon Open Systems Defined

15 Open Systems Defined Open building systems are created using the products and systems from multiple vendors that, as a system, offer greater flexibility, easier management, higher levels of scalability, and lower life cycle costs

16 Master/slave Distributed systems Stand-alone controllers Networks Closed, single-vendorOpen, multi-vendor Open Systems A Control Systems Evolution Centralized Home-run Wired Tiered Islands of Proprietary Sub-systems Flat, open, multi-vender

17 Building Management Applications HVAC Components Security Components Elevators G/W/E meters Lighting Components PC’s/TV’s/VCR’s Network Operating System Open Systems Architecture A Better Building Control Model Open BAS

18 Building users and other interest groups Building Owners IntelligentinterchangeabledevicesBuildingManagementInformation IndividualControl by PC or TV Energymanagementservices Flexiblespacemanagement Single source system maintenance Automated profile based control Networkpre-installationmanagement Open Systems An Owners Viewpoint

19 Open Systems Create Opportunity by … Providing a standard system architecture Allowing a comprehensive solution from Device to Enterprise Integration Creating a common tool platform across multiple manufacturers products Simplifying Adds/Moves/Changes as well as Monitoring, Control and Visualization Open Systems are –The basis for Innovation, Differentiation, and Competition –An opportunity for specifiers, integrators and end-users

©2003 Echelon L ON W ORKS & BACnet A Comparison

21 Comparing BACnet and L ON W ORKS Key areas to examine System Architecture System and Device Characteristics Conformance Testing and Certification Product Selection Network Management Diagnostic Tools Market Presence

22 Historical Comparison 1988 – Released by the Echelon Corporation 1994 – LonMark ® Organization formed 1995 – 1 st certified product 1997 – LNS 1.0 released 1998 – 100 th certified product 1999 – ANSI/EIA standard 1999 – 200 th certified product 2001 – 300 th certified product 2002 – Address space increased through ANSI 2002 – 400 th device certified 2003 – 500 th device certified (estimated) 1987 – ASHRAE committee formed 1995 – BACnet1995 Released 2001 – BACnet2001 Released 2002 – BTL begins product testing 2002 – 1 st tested product XML Work Group established 2003 – Becomes ISO Standard – 32 tested devices L ON W ORKS BACnet

23 System Architecture Description –L ON W ORKS provides for a flat architecture –BACnet provides a tiered architecture –L ON W ORKS flat peer-to-peer networks enable data exchange directly between devices without the need for gateways or custom software –BACnet tiered networks are designed around gateways or custom software to link sub-systems and components/subsystems from different vendors Impact on Openness –Linking sub-systems creates “islands of automation” –Flat architectures require more training, but have lower long-term costs –Integration of different subsystems requires more engineering –Upgrades cost more due to need for gateways and/or custom software

24 BACnet’s Tiered Architecture Source:

25 L ON W ORKS Flat Architecture IP/Ethernet LAN Device Network Operator Interface IP Router

26 System and Device Characteristics L ON M ARK Association sets L ON W ORKS guidelines for physical layer, application layer and product certification requirements Applications published via functional profiles, which define mandatory and optional data elements L ON M ARK Functional Profiles (LFP); 62 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) L ON W ORKS BACnet

27 System and Device Characteristics Description –L ON W ORKS (L ON M ARK Association) enables different manufacturers to produce products that have identical functional characteristics (both data interface and actions taken on shared data) –BACnet allows manufacturers choose unique implementation of specific functions Impact on Openness –Specifiers, integrators and owners must understand that there are degrees to openness Low Range: Can’t substitute devices from other vendors – Vendor Lock High Range: Substitute and extend with any vendor’s products –Addition of new equipment requires involvement from original integrator and manufacturer to understand how specific low level functions were actually implemented in each controller

28 Conformance Testing and Certification LonMark Interoperability Association certifies devices through Certification Centers; test and verify compliance with published functional profiles (mandatory characteristics) Certified products appear at products certified (thru 8/03) BACnet Testing Laboratories (BTL) test and verify manufacturer’s selected use of BACnet Tested products appear at org/btl/default.htm org/btl/default.htm 32 products tested (thru 6/03) L ON W ORKS BACnet

29 Conformance Testing and Certification Description –Certified L ON M ARK devices are assured to provide specified functions –Tested BACnet devices are identified to have one or more non-specific characteristics Impact on Openness –Design and integration of BACnet and L ON W ORKS devices can be expensive –Compliance testing makes life easier for manufacturers but harder for owners –Certification makes life harder for manufacturers but better for end-users

30 Understanding L ON M ARK Certification

31 L ON M ARK Certification Test Results

32 Understanding BTL Test Results

33 BTL Test Results - Example

34 Product Selection Description –L ON M ARK Association has certified 470 devices (as of Aug. 2003) –BACnet has tested 32 devices (as of Aug. 2003) Impact on Openness –There are lots of choices but they reflect a top-down.vs. bottom up approach –Limited competition results in higher prices; few sources for product; few sources for design and integration –Limited product selection may mean that the type of function/product desired is not available

35 Network Management and Diagnostic Tools Description –L ON W ORKS Network Management (design, commission, installation) and Diagnostic Tools available from manufacturers and independent vendors that leverage a standard database –BACnet Network Management and Diagnostic Tools only available from manufacturers Impact on Openness –Multiple “proprietary” tools required to integrate and diagnose multi-vendor Opportunity to remain “locked in” for upgrades –Diagnoses and troubleshooting network issues require “proprietary” tools provided by the same manufacturer that supplied the system/devices – no vendor independence

36 Network Management and Diagnostic Tools Design, Installation and Commissioning tools –Available from manufacturers and independent vendors –Tools permit installation of multi-vendor products Network Diagnostics –Software tools available from manufacturers and independent vendors –Tools permit diagnosis of multi-vendor product networks 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 only; not independent vendors –Proprietary tools do not permit diagnosis of multi-vendor products L ON W ORKS BACnet

37 Market Presence HVAC products and systems available from all major manufacturers including: Honeywell, Invensys, Johnson Controls, McQuay, Siemens, Trane; and many tier 2 suppliers; Products and systems available for Security, Lighting, Fire Alarm and other BAS from a variety of suppliers HVAC products available from Alerton Technologies Inc. (now Novar), Automated Logic Corporation, Delta Controls, Honeywell Korea, Teletrol Systems Inc. L ON W ORKS BACnet

38 Market Presence L ON W ORKS 1 BACnet 2 ² Data from BACnet Manufacturers Association 2000 survey and BTL website (Aug. 2003) ¹ Data from Echelon website and LonMark Interoperability Association as of mid As of July 2002

©2003 Echelon Specifying Open Understand & Help Define a Customer’s Needs

40 The Questions 1. Can the devices from different manufacturers be installed and commissioned on the same physical wire and be capable of true peer to peer communication? "All devices (nodes) on the network shall be capable of true peer to peer communication, without requiring a host or zone controller." 2. Have the devices been tested for interoperable compliance? "All devices (nodes) on the network shall conform to the LonMark Interoperability Standards version 3.0 or higher and be LonMark tested and certified for compliance on the open systems network." 3. Is the integrator meeting the requirements for the network infrastructure? “The network infrastructure shall conform to the published guidelines for wire type, length, number of nodes per channel, termination, and other relevant wiring and infrastructure criteria.”

41 The Questions 4. Are the network management and commissioning tools available from multiple sources and can all the nodes be installed with these tools? If a node needs custom configuration, is there a plugin available for use in a standard tool. "All devices (nodes) on the network shall be able to be installed and configured using a standard network management tool such as LonMaker for Windows or other LNS based tool. No non-open tool set for installation or configuration will be accepted. All tools must be generally available for purchase to any integrator from multiple sources." 5. Are the front end tools proprietary and closed? "Any host PC interface shall use openly available software packages that are non-exclusive. No closed software will be accepted. Software must be generally available on the market from multiple sources." 6. Who is doing the work on your building? “Integration of the controls network shall be performed by a qualified network integrator. A qualified network integrator must have attended at least 40 hours of training and have prior successful open systems jobs experience.”

42 7. Do you have control over your building? “All configuration tools, installation tools, Plugins, 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.” 8. Are your tools open? “No exclusive or non-open integration tools, devices, or host software shall be used as part of this open system.” 9. How are you connecting to your data network? “If Internet or IP connectivity is specified all devices connecting to the LAN shall use the IP protocol. Any LAN to LON gateways or routers shall use the standard IP protocol stack (Cisco Certified) and shall be transparent to the devices on the network (layer 3 routing).” 10. What controls are you using? “The control system shall be installed using the best available products from the currently available suppliers that meets the system specification. Controllers from multiple manufactures are encouraged.” Bonus Question: 11. Are you certain your network was designed and installed correctly? “System integrator shall provide a protocol analyzer log summary for each channel for a minimum of 48 hours showing system performance. The statistical summary shall show that all bandwidth utilization and error limits are within acceptable range and that there are no network traffic problems, node communication problems, or system sizing problems. The Questions

43 Specifying Open Understand & Help Define a Customer’s Needs Do you need a whole-building approach to systems integration? Is it important to be able to run the system from an application, like energy management or a performance contract? What about the future? XML? SOAP? IP?

44 Specifying Open Understand & Help Define a Customer’s Needs Is centralized control & sequencing required? How important is it to be able to replace a device with one from another manufacturer at a later date? I want to master my own destiny. Can I get all the necessary documentation, configuration information, configuration tools, programs, drivers, and other software or licensing from my suppliers?

45 Specifying Open Understand & Help Define a Customer’s Needs How many times have you been locked in? Do you want to be able to walk away? Do I need multiple front ends? Can I switch?

©2003 Echelon Get Informed

47 L ON W ORKS Open System Specifications Reference material available: –Echelon OSA Website : Open System Specification Framework and Design Guide – ork.pdfhttp://osa.echelon.com/Program/PDFs/guidelines/OpenSpecFramew ork.pdf

48 L ON W ORKS Open System Specifications Reference material available: –LonMark Website: LonMark Building Automation System Master Specification

49 L ON W ORKS Open System Specifications Reference material available: –Army Corps of Engineers

50 BACnet Open System Specifications Reference material available: –Allerton Website:

51 BACnet Open System Specifications Reference material available: –Trane Website: p#specify p#specify

52 Summary Market is going open There is a range to Openness –We have a responsibility to educate the end-users and ourselves –Need to commit time and become the expert Open Systems are an OPPORTUNITY to expand your business

©2003 Echelon Thank You!