System Integration

1. System Integration Presented by Carl Wittkowske “Meeting the Challenge”

2. Objectives • GCC System Integration Team and services • Review current techniques • Identify opportunities / minimize risks • Where to get the information • Scenarios • Processes - Acquisition to Fulfillment • A look at the competition • The future ….

3. A Quick Review • First to announce native BACnet 1993 • Trane recognized as the testing agency • BACnet Ethernet / IP • The “Bridge” to Modbus - TSCB • LON - a.k.a. Comm 5 • In 2002 - The mission is...

4. In 2002… • Must position and execute as THE System Integration CompanyHVAC systems controller • a system integration platform • HVAC systems controller • solutions provider • So how are we doing ?

5. Cerberus Div Can We Interface To …? BUS House

6. System Integration Goals • Single seat operation - HVAC, fire, power, security, etc. • Ability to select the best supplier to expand a system • Ability to select the best alternatives when purchasing parts of a system • Maximize infrastructure investment • Trane is pushing for “Open Systems”

7. Trane’s View ofSystem Integration • Automation products will be “interoperable” at both the system and unit control level a.k.a OPEN • Still some sorting out going on - but appears that for our industry: • BACNet at system level • LonTalk at unit control level • Modbus for process control • Result will be factory mounting of all unit controls (efficiency/reliability)

8. Web Browser Web Browser Web Browser Tracer Summit Web Server Client PC Tracer Summit PC Workstation Client PC Internet Other BACnet System BCU Tracer Summit Communications Bridge BACnet Controller Trane Legacy Controllers Security system(future) Client PC BACnet Controller Modbus Power meter ZN521 SCADA Systems Other LonTalk Controller Trane System Integration Offering Trane Legacy Systems

9. Single seat operation - HVAC, Fire, Power, Security, etc. System Controller LAN HVAC 1 HVAC 2 Lights Security Fire Integration Goals

10. System Integration Team GCC System Integration Team • Jennifer Schroer Marketing Product Manager • Avi Baidya Marketing Engineer • John Stojevich SI Engineer • Carl Wittkowske SI Engineer

11. System Integration Lab

12. ALM PWR TRACER SUMMIT Non- Trane LonTalk Device Trane Recognizes BACnet and LonTalk as the Backbone of System Integration! Tracer Summit Desktop Workstation SCADA Bacnet/OPC Server or Third Party BACnet/Ethernet Workstation BACnet/Ethernet LAN Comm5 Link Tracer Summit BCU Third Party System Level Controller SCC/DAC LonMark Device Tracer Comm5 Device BACnet/EIA-232 Third Party Device Third Party Device Third Party BACnet Gateway Proprietary Protocol Third Party System Level Controller Third Party Device Third Party Device Third Party Device Third Party Device Third Party Device

13. Trane Tracer Comm5 Controllers Non-Trane devices that follow SCC or DAC LonMark Functional Profiles Controller that uses Standard Network Variable Types (SNVTs) Serving information from Trane legacy (Comm2/3/4) controllers to third party BACnet systems via a BCU Sharing information between subsystems (HVAC, fire & life safety, lighting, etc.) Communication using Internet Protocol over Ethernet local or wide area networks LonTalk and BACnet BACnet LonTalk

14. BACnet Pros and Cons • BACnet is designed to work on networks and IP • Addresses how to exchange data, trends, and alarms, and manage the network are clearly defined • What comprises a controller is not yet defined - no equipment profiles • Works great on networks!

15. BACnet Objects Supported Analog Input Analog Output Analog Value Binary Input Binary Output Binary Value Calendar Command Device Event Enrollment File Group Loop Multi-State Input Multi-State Output Notification Class Program Schedule Averaging Multi-State Value Trend Log Life-Safety Point Life-Safety Object

16. Alerton Andover Automated Logic * Carrier Cimetrics OPC * CSI (TAC) Delta Dunham-Bush Honeywell Invensys JCI Liebert Lithonia Mammoth McQuay Multistack Phoenix Siemens Simplex Systecon BACnet Vendors Supported • TriaTek • Tridium • York • * OEM Supplier

17. Comm 5 Uses LonWorks • LonWorks includes: • LonTalk protocol packaged in a neuron chip • network management and development tools • LonMark: • an association sponsored by Echelon • member companies sit on committees developing industry profiles for LonWork’s users • has addressed equipment profiles and • working on scheduling, alarming and trending • Recognized by a wider range of industries than BACnet

18. Are all LON Devices Interoperable? • MP501, MP503, LCI’s, ZN51x, ZN517, ZN52xZN524, AH540/541, CH530/531, VM512 • TLC,Tracker, BCU • MP580, CCP • Other manufacturers’ devices into Trane BAS • Trane devices into other BAS System

19. LonTalk Pros and Cons • LonTalk is easy to implement with the use of the neuron chip • LonTalk protocol works great for small controllers • LonTalk allows for sharing information • Profiles are designed to make controllers interchangeable - appear similar • Network management tools are an issue • Limited upon system level networks

20. ABB ACT Andover Bapi Belimo ControlbyLight CSI (the other one) Cristal Controls DanFoss Douglas Lighting GE Prosys Honeywell XL10 Hubell Invensys I/A Series JCI Kele Magnetek(Yaskawa) Siemens - L&G Siemens - Staefa Smart Controls LON Vendors Supported • Square D • Veris

21. Modbus • Industrial defacto standard • Used by many vendors to transfer information between different providers • There are many of third party translators that convert proprietary information to Modbus • Most common protocol is Modbus RTU

22. Trane UnderstandsModbus “Open Protocol” is Here to Stay... Tenant Services Desktop Workstation Tracer Summit Laptop Workstation Modbus* BACnet/Ethernet LAN Modbus ASCII, RTU, TCP/IP Controllers Tracer Summit BCU Tracer Summit Communications Bridge ALM PWR TRACER SUMMIT Many industrial controllers such as variable speed drives, switch gear, gen sets, PLCs, etc. BACnet EIA-232 Modbus RTU Third Party BACnet Gateway Third Party Modbus Device Third Party Modbus Device *Many other protocols can be supported through a third-party gateway Third Party Device Third Party Device Third Party Modbus Device UCP2 Chiller Controller

23. ABB Airflow Alan Bradley B&G Danfoss Fireye GE PLC Honeywell RM7800 Liebert Magnetek Onan/Cumins Square D TSI Veris Modbus Vendors Supported Modbus Server *using TSCB

24. Identifying Opportunities & Evaluating Risks • Understanding and working with your customer • Working with other vendors • Misperceptions in the industry • Gotchas • Tools

25. Working with the Customer • Who is the dog and where is his tail? • Trane BAS or others BAS • Is other vendor going to play ball? • local rep not the sporting type • What protocol is being used? • Who is to provide what? • ask the customer to make the call

26. Working With Other Vendors • Companies claiming support with questionable implementation • Don’t protect the owner from being tied into one company at the front end • Lon-based system controllers require separate service tools • BACnet may have problems with incompatible transmission medium

27. Misperceptions • “...I should be able to interchange open controllers” • Expect interoperability to be the same as buying and setting up a PC and peripherals • Expect interoperability allows lower installation and maintenance costs

28. Gotchas • Unique, vendor-specific setup tools and processes • Additional equipment required • May be LON….but that is about it • Installed by others or others to install • network management conflicts • self-installing devices • improper documentation

29. Tools • TraneNet tranenetlax1/BAS/Home/index.htm • GCC Marketing • Other sales offices • SI Team, training class, demo room • Initiate the “Process” • coming in a NY minute

30. SI Support • TraneNet - extensive information • can we interface to? • sales support • operations support • competitive information • system architectures • industry issues

31. Look at TraneNet

32. Supported Interface

33. Not On the List? • It works but we have no info/contact • It doesn’t work • Never tried - there’s always the RATSI • Rent-A-Tech for system integration • Start with the acquisition process • 1.Acquisition • 2.Evaluation • 3.Development

34. SI Acquisition • Check on TraneNet if supported interface • Verify hardware and model number • Call Trane GCC • hardware description / model • quantity of devices • technical information, objectives • manufacturer representative contact

35. SI Evaluation“Risk Assessment” • Compare against similar requests / confirm • Does it fit a business strategy / sales potential / time required? • Trane is the client or server ? • Will perform technical document review • Contact other manufacturer or representative • Will supply initial budgetary quote to requestor

36. SI Development • When server, will negotiate directly with vendor • Obtain sample product(s) for testing • manufacturer supplies, purchase, field supplied or traded • Bench tests, documents, and reports • RATSI - on-site testing and qualification • Technical support

37. Too Far Down the Road Before GCC?

38. Competitive Challenges • Trane offensive approach • Most competitors - defensive approach • See you all handouts!

39. How to Approach Division 17 Specifications Love ‘em or leave ‘em?

40. Why Division 17? • No place for telecommunications! • technology implementation often poorly planned • buildings not designed to support technology infrastructure • requirements addressed late in construction process

41. What is Division 17? • Organizational model to effectively integrate planning, estimating and design of copper, fiber, data,voice, video and other low voltage systems • Maximize benefits of a common, facility based infrastructure • establish meaningful budgets • plan how technology is integrated

42. Division 17 DEAD...Soon To Be • Master Format Draft 2, Scheme A • Division 35 - HVAC • Division 38 - communications • Division 39 - integrated automation and control • HVAC, life safety, plumbing/fluid process, conveying systems, electrical, energy monitoring, communication, IT/business

43. What Makes a Good Controls Specification? • Performance orientation - not prescriptive • Clear language that is obtainable on the job site • Designs that meet owner’s needs a.k.a. ICS • Can readily be enforced and delivered

44. Challenges with DDC Specifications • Controls is a specialized area • Consultants rely on vendors for assistance in this area • Tendency to re-use a “master spec” without specific tailoring • Rapidly changing technology makes it hard to specify properly • Interoperable systems are tough to specify!

45. Technology Challenges • Just keeping up • costly • resource consuming • Maintaining support for legacy systems • Choosing what technology to use • “IT” force carries a lot of weight

46. Web-Server New Challenges • Daily operator functions, not designed to allow complete access to system • Web-server seats sold in blocks, with specific names & passwords • Most web-server are PC based • Software sets up the web-server and I.D. needed to make changes • Question - does the user really want internet access?

47. Call to Action ! • Rely on and promote open standards and common technologies • Utilize standard tools • don’t get trapped “developing technology” • Industry is not plug and play • Consider legacy systems - gateways • Technology is not the solution it is a tool to provide a solution • Project tracking

48. Summary • System integration is becoming more mainstream • As we progress interoperable solutions will become easier to specify and install • Not all vendors implement standards in the same way • Use the tools - TraneNet and SI Team • We are growing !

49. What’s Down the Road? • BACnet enhancements • Rover pass-thru • New TSCB drivers • Security • Enterprise systems • TNG

50. Questions ? ? ?