1. Disclaimer This presentation, for use by the TAC Partner Sales Channel, is designed to mirror very closely Bob Schultz’s DVD whiteboard discussion (Introduction to TAC Open Systems Solutions - 2003) regarding open systems, and the LON world. This presentation should be used with the following points in mind. 1.!!!This IS NOT a sales tool!!! While certain sections of this presentation are suitable for a sales setting, there are specific pieces of information included that should NOT be presented to a potential client. 2. This presentation should be given only after watching the Bob Schultz DVD, and reading the notes associated with each slide. The slides themselves contain as little information as possible in an effort to create credibility for the presenter, and develop a relationship with the audience.

2. Open Systems Terms, System Architecture & Basic Concepts

3. Chapter 1 LON Architecture The Enterprise Level The Hardware Level Channels & Segments Channels & Segments Speed & Interoperability Speed & Interoperability

4. The Enterprise Level Top Down Approach Older systems evolved into TCP/IP – LON started there TCP/IP “The IP Level” Can be the internet, an intranet, or crossover cabling. Any media that will handle TCP/IP.

5. The Enterprise Level TCP/IP “The Server” Primary machine that interacts with the hardware environment. Vista IV Server

6. The Enterprise Level Communicates with hardware through the server. Server/Client architecture implies vendor specific software. Multiple Clients possible Vista IV Workstation “The Client” Server TCP/IP

7. The Enterprise Level Receives and broadcasts information from the server Vista IV Webstation Server TCP/IP Client “The Webserver”

8. The Enterprise Level Receives information from the Webserver. Vista IV Webstation 3CAL Server ClientWebserver TCP/IP The Internet “The Web-Client”

9. The Enterprise Level Basic Enterprise level traffic flow These are pieces of software –not necessarily separate machines. Server ClientWebserver TCP/IP The Internet Web-client

10. Router LON Backbone The Hardware Level Routers Network traffic cop Protocol translation Server ClientWebserver TCP/IP The Internet Web-client

11. The Hardware Level ClientWebserver TCP/IP The Internet Web-client Physical Layer Repeater Server

12. DDDDDD Channels & Segments Segment Segment – A piece of the network defined by the boundaries of any communication governor. 50 device max. Device Device – Any piece of equipment on the network that possesses an Echelon neuron chip & I.D. Channel Channel – Boundaries defined by routers. Usually consists of 2 segments.

13. Channels & Segments Terminators Terminators – Absorb reflecting signals,and improve communication quality. TTTT

14. Channels & Segments Common Misconception – LON is Logically AND Physically Flat. 1 long wire carries all signals causing communications to bog, and system failure. 50 Dev. WRONG

15. The Hardware Level Physically Tiered Logically Flat No device ever more than 3 steps away from the Enterprise Level. “Don’t let anyone ever say we cannot deliver a system with superb communication characteristics.” - Bob Schultz ClientWebserver TCP/IP The Internet Web-client Server 50 Dev.

16. The Hardware Level Vastly scalable. ClientWebserver TCP/IP The Internet Web-client Server

17. Network Speed & Interoperability Interoperability – Defined by: Media, Protocol & Speed Echelon Transceiver forces 78kbs Guarantees interoperability ClientWebserver TCP/IP The Internet Web-client 78 kbps 1.25 Mbps Or 78 kbps 100 Mbps Server

18. Chapter 2 Data Network Bindings Formatting Formatting Echelon Conventions Echelon Conventions Data Transmission Data Transmission

19. Network Bindings Bind Bind – To connect and cause data flow Logically Flat – True peer to peer. Opposite of Managed Communication LonMaker DD Building IBuilding II

20. Data Type – SNVT’s SNVT S tandard N etwork V ariable T ype Basic format for data transmission across a LON-based network. Examples SNVT_temp_f = -273.17 to 1E38 degrees C SNVT_freq_hz = 0 to 6553.5 Hz SNVT_freq_khz = 0 to 6553.5 kHz SNVT_power_f = -1E38 to 1E38 watts SNVT_power_kilo = 0 to 6553.5 kW Multiple syntax possibilities for each process variable

21. Echelon Conventions LonWorks LonWorks – The entirety of the LON protocol. LonMark LonMark – A 3 rd party guarantee of interoperability through the creation of LonMark “profiles”. Customer Freedom Depends on a Lack of Choice for Manufacturers LonWorks provides a choice. LonMark takes it away.

22. Data Transmission Send & Pray Low Priority data Ex – send OA temp to all VAV for display on stat. Send 3x’s & Pray Less Mid Priority data 99.9% effective Acknowledged Critical data Ex- Outside Air temp to a process controller Send PrayPray Less Get it?Got it.

23. Chapter 3 Devices & Intra-level Communications Application Specific Devices Application Specific Devices Programmable Devices Programmable Devices Server/Device Communication Server/Device Communication Software Software

24. Application Specific Devices A.S. Devices – Pre-determined logic by manufacturer. Configuration necessary. VAV, Heat Pump…etc. controllers LON-Based Sensors LON-Based Actuators TAC Xenta 101 Fan Coil ASC TAC Xenta 102 AX VAV ASC Belimo GM24 LON Actuator LON products add capability to contractors. More tools

25. Programmable Devices Programmable Devices – Custom applications. Device is empty of logic off the shelf. Programmer in control. With I/O Sensors and Actuators wired in. Without I/O Logic only. No sensors or actuators wired in. TAC Xenta 401 Programmable Controller TAC Xenta 302 Programmable Controller

26. Server Device Communication Node-to-Node, more specifically, ASD-to-ASD communication in the LON World is fairly specific. DD Open LonTalk In a TAC environment, data can be passed using public communication, specific to TAC. Programmable Controllers TA Network Variables TAC Xenta 401 TAC Xenta 302

27. Server Device Communication LonTalk does not handle Server to Hardware communications well. Automatic Time Scheduling Trend Logs Alarm Handling Operator Functions Test Manual Control Server Using Public Communication brings the total installed cost down! TCP/IP R PLR R R TAC Xenta 302 Public Communication

28. Software Open Systems “modularize” software.

29. Software Main Functions Addressing Configuration (ASC) Application Creation HMI Human Machine Interface LonMaker for Windows TAC Menta TAC Vista IV Workstation

30. Software LonMaker for Windows Created by Echelon Addresses all nodes Binds all Network Communication Visio Based LNS Plug-in Support Creates As-built Reports

31. Software TAC Menta Extensive “Block” Library Real-time Simulation & Trend Logging Off-line programming

32. Software TAC Vista IV Workstation HMI Alarm Handling Trend Logging Manual Control Automated Scheduling

33. Chapter 4 Single & Multi-Vendor Solutions Single Vendor/Single Building Multi-Vendor Multi-Vendor Multi-Vendor/Multi-Building – LON Multi-Vendor/Multi-Building – LON Multi-Vendor/Multi-Building BACnet Multi-Vendor/Multi-Building BACnet

34. Single Vendor/Single Building Device Functionality Client TCP/IP Server R R R PLR TAC Xenta 101TAC Xenta 302 ASC’s have no memory All Data flows to P.C. for processing Values

35. Single Vendor/Single Building Device Functionality Client TCP/IP Server R R R PLR Data Collection Alarms Schedules Trends ASC’s have no memory All Data flows to P.C. for processing Values Alarm Generation Trend Storing Automated Schedules

36. Multi-Vendor Several logic only devices, placed high in the system architecture Client TCP/IP Server Logic only devices (401’s) TrendsAlarm Gen. Schedules

37. Multi-Vendor NAC translates pure LON into HMI protocol. Client TCP/IP Server Network Area Controller (NAC) i.e. – JACE Box

38. Multi-Vendor Only pure LON SNVT’s are allowed to cross the DMZ Client TCP/IP Server = DMZ – 100% LON SNVT

39. Multi-Vendor/Multi-Building - LON 1 Vendor controls the I.P. Level. That vendor is in the driver’s seat with the client. More of a service contract at this level. Very little physical labor. Building I Building II Building III ===

40. Multi-Vendor/Multi-Building - LON TAC can service a building even if the HMI doesn’t belong to us. Building I Building II Building III ===

41. Multi-Vendor/Multi-Building BACnet BACnet uses multiple HMI’s 1 system designated as lead All subordinate servers pass information to lead

42. Summing It Up Physically Tiered – Logically Flat Ladder/Rung Architecture Interoperability Speed, Media, Protocol LonMark Association Modular Software Single/Multi Vendor Systems Campus & Multi-Building Systems

43. Keep in Mind Build a vocabulary & a Dictionary Be SPECIFIC Plan Ahead

44. Data Transmission Send & Pray Low Priority data Ex – send OA temp to all VAV for display on stat. Send 3x’s & Pray Less Mid Priority data 99.9% effective Acknowledged Critical data Ex- Outside Air temp to a process controller Send Acknowledged