Discussion Topics. Integrated System Definition. Two Primary Characteristics. Understanding and Specifying Open Protocol Syracuse, NY April 2009

Transcription

1 Discussion Topics 1. Key characteristics of integrated systems 2. Integrated Systems evolution & pros/cons encountered Understanding and Specifying Open Syracuse, NY April Role of open protocols in systems integration 4. Communicating systems vs. Integrated systems 5. Specifying integrated systems 6. Integrated Systems the next evolutionary stage 7. Summary Presentation by: Zig Lewicki Integrated System Definition The connection of various equipment & subsystems such that they operate in harmony to achieve optimized system performance. Optimized performance goal examples: Optimized building efficiency Energy efficiency Equipment performance and maintenance Occupant comfort, health, and/or safety Space utilization (computer room vs. storage closet) Etc. How far do you take this concept? Two Primary Characteristics Single user interface (Front-End) Integration of building equipment and subsystems Copyright Carrier Corp

2 Integrated Systems Types Integrated Systems Types 100% Integrated Equip. w/ BAS 100% Single Mfgr Integrated Equipment Equip. / w/bas Total Equipment Single HVAC Manufacturer Project Types Custom BAS Multiple HVAC Manufacturers Single Mfgr Equipment / Total Equipment Custom BAS 0% 0% Project Types The Evolution of Integrated Systems The Beginning One Controls Vendor You can t know where you re going until you know where you ve been. Proprietary -- Author Unknown Copyright Carrier Corp

3 Benefits/Pitfalls Integrated Controls Movement + Access to job through a single front end + Single source of responsibility for controls High labor costs (engineering & install) Finger pointing at equipment level Performance and consistency issues Owners get locked in Why it started & why it makes sense More Cost Effective Higher Equipment Reliability, Performance, and Energy Efficiency Optimized for System Performance Higher, Consistent Quality Connecting Proprietary Systems & Equipment Different Vendors Connecting Proprietary Systems & Equipment Same Vendor Proprietary Proprietary Copyright Carrier Corp

4 Benefits/Pitfalls Open Movement + Single Front end + Consistent quality + Advanced control algorithms + More cost effective + Single source of responsibility (equipment) Proprietary Open N2 s a new source of finger pointing s costly Owners still locked in Open Equipment Level Open s Open Open N2 N2 Supporting one is good, but more is better Copyright Carrier Corp

5 Why Multi-protocol? Open s Flexibility needs/choice vary by customer, region, building type, contractor, etc. Open Standalone or Other N2 Supporting one is good, but more is better Johnson N2 Field selectable Allows specification to be more flexible Allows for changes down the line without significant cost Benefits/Pitfalls Systems Interaction + Single Front end + Consistent quality + Reduced labor cost + Owners not locked in + Reduced integration cost (fewer gateways) Open N2 No single source of responsibility Different compliance levels possible More pressure on specifying engineer to specify and enforce levels of integration and system performance Copyright Carrier Corp

6 Sub-Systems VAV System Bi-directional communication a must Control schemes must work together Reaping the Benefits of Integrated Systems How do we get there? The Importance of Good Specifications Specifying an Integrated System Suddenly, a heated discussion broke out between the king and the moat contractor. 3 Key Elements: 1. Front-End User Interface 2. Open s 3. The C in DDC Copyright Carrier Corp

7 Front-End User Interface Intuitive, interactive graphics floor plans, equipment, subsystems Processed information screens Alarms receipt, processing, management, and notification of alarms Remote system access (web-based technology) Use of open standards (IT industry standards and BAS industry standards) Integrated reporting packages, historical information, audit logs & storage Ease of operational changes (schedules, setpoints, strategies, etc.) Secure user access Etc. Key Be Specific Require Full Feature Delivery & Implementation Open s Main communications backbone Specify protocol standards compliance Match front-end to protocol Should allow for expansion & future open bids Subsystems HVAC, Lighting, Fire, Access, Monitoring, etc. Acceptable protocol options & compliance stds. Clear list of interface points & interaction Equipment level Acceptable protocol options & compliance stds. Clear list of interface points & interaction The C in DDC Next Industry Movement * The System is the Product * Equipment sequence specifications Systems sequence specifications for system-wide optimization & interaction Scheduling, alarms, temperature optimization, building energy strategies, subsystem coordination, shared global data, etc. Three Scenarios 1. Multi-Vendor throughout down to equipment level 2. Multi-Vendor to the subsystem level 3. One Vendor Open Gatewa y Copyright Carrier Corp

8 Basics What is? Where is used? and Other Open s What is? Building Automation and Control NETwork A defined protocol for Data communication between Building Controls This protocol outlines rules for: Electrical Signaling Addressing Network Access (Master / Slave, Peer-to-Peer) Error Checking Flow Control Message Sequencing, Segmentation, Check-pointing Presentation Format Message Format Where is used? is designed for use in commercial building applications: HVAC Control Building automation and control Integration of fire, life safety systems Lighting Control Maintenance management Alarm reporting and response Smart elevators Interface to Utilities and Other s LON (Local Operating Network) Lonworks is a jack of all trades (common to many industries) Lonworks is based on dedicated, proprietary hardware (Network on a chip) MODBUS MODBUS comes from the Process Control Industry No HVAC Manufacturer uses MODBUS as a standard, although many support it MODBUS, is a very simple protocol For example, scanning points for alarm limits, adding units to point data, mapping registers all must be accomplish by a front end processor MODBUS, because of its simplicity, is a great in-between protocol has been developed for buildings and facilities provides system scheduling, trends and alarms is a protocol on multiple communications media (transport) can be developed as new media emerge Copyright Carrier Corp

9 Appeal: Native Field Architecture LON: End device manufacturers Mechanical Equipment Manufacturers Quick solution quick fix 100% OPEN FROM TOP TO BOTTOM Intranet / Internet IP Network Server : Simple data retrieval Ancillary equipment (Metering) : BAS Manufacturers Commercial HVAC & EMS customers Link Fire Native MS/TP Lighting Boiler Chiller Security Proprietary Equipment/Systems Router Router Other Mfg s Device(s) Zone Customer Concerns Practical Results of : Scalability/Extensibility Practical Application / Availability Procurement Avoiding dead-end technology Open Standards Customers can choose the best technology, receive competitive pricing and have a common Graphical User Interface (GUI) Integration is simpler using over TCP/IP networks and other media, reducing initial cost and cost of ownership Control vendor does not have a proprietary lock on the customer.the customer has a choice! Copyright Carrier Corp

10 SUMMARY Questions? ASHRAE Building Subsystems Integration Multi-vendor Software Only Copyright Carrier Corp