2. From a Manufacturer’s Viewpoint Jay Garbarino, P.E. U.S. Western Regional Sales Manager www.bms-iran.com

3. Why Open Protocols ?

5. Main PC One Operator Workstation One Platform

6. Why Open Protocols ?

7. The Concept Behind Open Protocols Control systems have many common requirements regardless of applications A networked control system is significantly more powerful, flexible, and scaleable than a non-networked control system Businesses can save and make more money with control networks over the long term than they can with non-networked control systems.

8. The Benefits of an Open Protocol - Ability to view the entire network from one platform -Competitive expansion of the network -Eliminates the fear of feeling “locked in” -Interoperability with other building functions: Data sharing Alarming and event management Trending and Scheduling Remote device and network management

9. Open Systems Interconnect- OSI Model Application Presentation Session Transport Physical Data Link Network 7 6 5 4 3 2 1

10. Open Systems Interconnect- OSI Model Application Presentation Session Transport Physical Data Link Network 7 6 5 4 3 2 1 At this layer, the transmission of data between devices is defined. The definition includes cables and connector pinouts, voltage levels, bit timing, and the actual network interface device called a Transceiver.

11. Open Systems Interconnect- OSI Model Application Presentation Session Transport Physical Data Link Network 7 6 5 4 3 2 1 Is involved with transmission, error detection and flow control of the data.

12. Open Systems Interconnect- OSI Model Application Presentation Session Transport Physical Data Link Network 7 6 5 4 3 2 1 Data is formatted for the appropriate communications method such as LAN, WAN (T1), or packet switched technology such as X.25 and/or IP used by TCP/IP.

13. Open Systems Interconnect- OSI Model Application Presentation Session Transport Physical Data Link Network 7 6 5 4 3 2 1 Optimization of data transfer from source to destination by managing network data flow and implementing the quality of service requested by the session layer. Determines packet size based on the communication media.

14. Open Systems Interconnect- OSI Model Application Presentation Session Transport Physical Data Link Network 7 6 5 4 3 2 1 Manages the communication Dialogue between two communicating devices. Establishes rules for initiating and terminating communications between devices and provides error recovery.

15. Open Systems Interconnect- OSI Model Application Presentation Session Transport Physical Data Link Network 7 6 5 4 3 2 1 Data translation and code Conversion between devices With different data formats

16. Open Systems Interconnect- OSI Model Application Presentation Session Transport Physical Data Link Network 7 6 5 4 3 2 1 The User’s interface with the Network. Interacts with user application programs to provide access to the network.

17. Available Open Protocols … Partial List - BACnet -LonWorks -Modbus -Profibus -CAB -ControlNet - DeviceNet -BatiBUS -EIBnet -WorldFIP -N2 Bus

18. Building Automation Control Network Local Operating Network Prominent Open Protocols in the Building Automation Market

19. Versus Both protocols allow for dissimilar manufacturers of products to interoperate over a common network by data sharing, alarm and event management, trending, scheduling and remote device network management.

20. Versus Both protocols allow for the following applications: HVAC Control Fire detection and alarm Security Lighting control Smart Elevator Control Utility company interface …and more

21. Versus Benefits of both Protocols: Single operator workstation for all systems Competitive system expansion Possibility of integrating all building control functions Interoperability

22. Vs. Who’s behind each protocol? Echelon-The developer and distributor of LonWorks a for profit corporation. ASHRAE- A non profit organization that advance the arts and sciences of heating, ventilation, air conditioning, refrigeration and related human factors to serve the evolving needs of the public and ASHRAE members.

23. Purpose: The Standard is to define data communications services and protocols for the computer equipment used for monitoring and control of HVAC&R and other building systems and to define, in addition, an abstract, object- oriented representation of information communicated between such equipment, thereby facilitating the application and use of digital control technology in buildings.

24. Mission The LonMark Association's mission is to enable the easy integration of multi-vendor systems based on LonWorks networks. Today thousands of companies are using LonWorks control networks to provide systems and solutions for building, home, industrial, telecommunications, transportation and other industries. There are millions of LonWorks based devices installed world-wide. The Association provides an open forum for member companies to work together on marketing and technical programs to promote the availability of open interoperable control devices. Purpose The Association has three major functions: Promote benefits of interoperable LonMark products. Provide collaborative marketing programs for companies developing LonMark products. Provide a forum to define application-specific design requirements.

25. Committee for European Standardization CEN TC247 Approved Protocols Levels of Operation Management Level BACnet Automation Level BACnet WorldFIP Profibus FMS EIBnet Field Level EIB, BatiBUS, EHS, LonTalk, BACnet

26. Utilizes four layers: Physical Data link Network Application Utilizes six layers: Physical Data link Network Transport Session Presentation Open Systems Interconnect- OSI Model

27. ASHRAE ANSI/ASHRAE Standard 135-1995 ISO/DIS 16484-6 ISO/TC205 BMA-BACnet Manufacturers Assoc. BTL-BACnet Testing Laboratories BACnet Interest Groups-BIG-NA, BIG-EU, BIG-AA Echelon Neuron Chip LonWorks transceivers LonMark Association Organizations/Standards/Support Groups

28. LonTalk-Proprietary Protocols Supported MS/TP (RS485) PTP (RS232) ARCnet Ethernet BACnet IP-TCP/IP LonTalk

29. Twisted Pair Power line Radio Frequency Coaxial Cabling Fiber optics Twisted Pair Power line Radio Frequency Coaxial Cabling Fiber optics Communications Media

30. Varies with protocol used: MS/TP- 78kbps PTP-78 kbps LonTalk (see below) Ethernet- up to +1000 Mbps ARCnet- 2.5 Mbps BACnet IP Twisted pair- up to 1.25 Mbps FTT twisted pair- 78 kbps Link power twisted pair-78 kbps Communications Transmission speed

31. Object oriented-Input, output, software processes i.e. points, schedules, alarms Standard Network Variable Types SNVTs there is a list of over 100 SNVTs i.e. temperature, energy, power, speed Common Applications Framework

32. Manufacturer dependent Area- 99 nodes System-99 nodes Subnet-99 Objects per device- manufacture dependent Address-by area, system, subnet, and object type Subnets per domain-255 Nodes per subnet-127 Nodes per domain-32,385 Groups per domain-255 Nodes per group-63 Number of domains- 281,474,976,710,656 Network Size

33. Manufacturer dependent Neuron Chip-manufactured under license by Motorola and Toshiba Hardware

34. Object oriented programming and Communications -manufacture dependent PICS List Third party suppliers Binding SNVTs-tells the device which other devices it should talk to and what information it should share. Software

35. Object oriented Plug-n-Play- provides a means of identifying and accessing information without requiring knowledge of the Details of the device’s internal design or configuration. Initializing devices via service pins Binding each individual SNVTs Connectivity

36. Johnson Router BACnet over Ethernet BACnet over LonTalk Carrie r Staefa Siebe Router Teletrol Controller Trane Controller Cimetrics Router SEIMENS Siebe Controller BACnet over Ethernet Johnson Router Johnson Controller HONEYWEL L Controller BACnet over ARCnet BACnet over MS/TP Cornell PowerMac Siebe PC Trane PC Operator Workstation NIST Diagnostic Software BACnet Interoperability Demonstration

37. LonWorks Control Network Valves Sensors Remote Client Electronic Ballast-Lights Actuators Man Machine Interface

38. Why LonWorks? –End device oriented systems –Smaller networks –Simple systems –Expansion plans are minimal

39. LonWorks Control Network Valves Sensors Remote Client Electronic Ballast-Lights Actuators Man Machine Interface

40. Why BACnet? –Larger networks-application driven –Controller oriented –Need to move large amounts of information –Complex systems –Future expansion

46. Source: Frost & Sullivan, North American Building Protocol Analysis, 2001 Vs.

47. Source: Frost & Sullivan, North American Building Protocol Analysis, 2001 Vs.

48. Benefits of BACnet No charge for its use—anyone may develop implementation without cost. Maintained by an ASHRAE committee representing all sectors of the industry. Designed specifically for building control. Can be implemented in devices of any size. Can be readily enhanced and improved. Not tied to present technologies.

49. Why Should BACnet Succeed? User Demand No fixed architecture Object model is easily extended Doesn’t depend on current technology Broad participation in its development Many vendors are committed to it Global interest

51. BACnet Interoperability Demonstration

52. Johnson Router BACnet over Ethernet BACnet over LonTalk Carrie r Staefa Siebe Router Teletrol Controller Trane Controller Cimetrics Router SEIMENS Siebe Controller BACnet over Ethernet Johnson Router Johnson Controller HONEYWEL L Controller BACnet over ARCnet BACnet over MS/TP Cornell PowerMac Siebe PC Trane PC Operator Workstation NIST Diagnostic Software BACnet Interoperability Demonstration

54. BACnet Interoperable Building Blocks Data Sharing Alarm & Event Management Time Scheduling Trending BIBBs Device and Network Management

55. Operator Workstation Building Controller Advanced Application Controller Application Specific Controller Smart Sensor / Actuator BACnet Device Profiles

56. BACnet Interoperability Building Blocks. The workstation shall support the following BIBBs: Data SharingAlarm & EventSchedulingTrendingDevice & Network Mgmt. DS-RP-A,BAE-N-ASCHED-AT-VMT-ADM-DDB-A,B DS-RPM-AAE-ACK-A T-ATR-ADM-DOB-A,B DS-WP-AAE-ASUM-A DM-DCC-A DS-WPM-AAE-ESUM-A DM-TS-A DM-UTC-A DM-RD-A DM-BR-A NM-CE-A

57. Specifying BACnet - The Simplified Process 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. 1. Lay out a proposed architecture and determine at what levels in the system BACnet is desired. 2. 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.

58. Specifying BACnet - The Simplified Process Select BACnet interoperability functions for each device using BIBBS: Data Sharing Alarms & Events Time Schedules Trend logs Device & Network Management 4. Determine who is responsible for system integration. 5.5.