Presentation Transcript

1. SFPE Tech Talk 2012 BACnet & Integration Topics in Life Safety Systems Jason Falbo, P.Eng, M.B.A VP Engineering The Mircom Group of Companies jfalbo@mircom.com www.mircomgroup.com
2. Roadmap Past Methods of Integration Industry Drivers for Change Details of the BACnet Protocol A quick application example Helpful Links and Self-Study Tips for the Fire Protection Engineer
3. From Hardwired Interfaces to Software Interoperability Brief history of fire alarm systems Integration
4. The Past: Hardwired Interfaces A collection of dry contact inputs/outputs were used to fulfill a correlation matrix to meet a specific project integration objective Relay Logic was used to design complex interfaces Systems were poorly documented if at all and nearly impossible to maintain or extend
5. Integration: complex method Return Air Damper CLOSED End Switch Electrical Supervisory Device Return Air Fire Alarm Damper Actuator Relay Damper Status Monitor Modules Supply Air Damper Actuator Relay Supply Air Damper CLOSED End Switch Supervisory Device Smoke Control: The Old Way Return Air Smoke Damper Pneumatic Actuator Supply Air Damper OPEN Supervisory Device Supply Air Damper Pneumatic Actuator Return Air Damper OPEN End Switch Electrical Supervisory Device Return Air Smoke Damper Actuator Electrical Supervisory Device Supply Damper Actuator Electrical Supervisory Device
6. Trends, History, and Purpose Modern Drivers for Change
7. Industry Trends in interoperability Fire Protection Healthcare Financial Services http://www.hl7.org http://www.xbrl.org/ http://www.bacnet.org/ Saves $$$ Increases 
8. Integration: complex method Return Air Damper CLOSED End Switch Electrical Supervisory Device Return Air Fire Alarm Damper Actuator Relay Damper Status Monitor Modules Supply Air Damper Actuator Relay Supply Air Damper CLOSED End Switch Supervisory Device Smoke Control: The Old Way Return Air Smoke Damper Pneumatic Actuator Supply Air Damper OPEN Supervisory Device Supply Air Damper Pneumatic Actuator Return Air Damper OPEN End Switch Electrical Supervisory Device Return Air Smoke Damper Actuator Electrical Supervisory Device Supply Damper Actuator Electrical Supervisory Device
9. integration: Simplified method FACP with Native BACnet Interface Physical Ethernet port Connection on FACP Main Board MD-871A Main Board BACnet Ethernet Connection
10. The Future: software interfaces BACnet: ANSI/ASHRAE Standard 135-1995: BACNet--A Data Communication Protocol for Building Automation and Control Networks. 1980’s saw a proliferation of computerized building systems and typically systems from a specific manufacturer could not operate with other manufacturer’s products (no “interoperability”) In1987 , Michael Newman of Cornell University formed a committee to investigate creation of interoperable building systems protocol The BACNet standard’s first draft was published in 1991, and it became a standard in 1995 BACNetwas designed to allow interoperable communication of building automation and control systems for applications such as heating, ventilating, air-conditioningcontrol, lightingcontrol, accesscontrol, fire protection systemsand their associated equipment.
11. BACnet standard has been adopted by 612* manufacturers worldwide http://www.bacnet.org/VendorID/index.html *as of September 12th 2012
12. BACnet Implementation BACnet Implementation case study
13. BACnet Setup: Step one (Activate) Use MGC’s Fire Alarm Panel Configurator to activate BACnet functionality: 1. Run TCP/IP Services 2. Activate BACNetServices
14. BACNet Setup step two (Export) Use Configuration tools to export automatically the list of auto-assigned BACNET points for each object in the Fire Alarm Control Panel
15. BACNet Setup step three (Deploy) Provide the list of BACNet points to the BMS system integrator The Integrator will map the auxiliary system activities to FACP point state changes BINARY INPUTS LIFE SAFETY POINTS BINARY INPUTS LIFE SAFETY POINTS
16. Integration : optimized method LIGHTING CONTROL CLIMATE MONITORING SECURITY-OCCUPANT-MONITORING VIDEO-SMOKE-CONFIRMATION SAFE ELEVATOR EGRESS SMOKE MANAGEMENT & CONTROL
17. How Does it Work? BACNET PROTOCOL DEEP DIVEPart I - basics
18. First Start with choice of BACnet network architecture High Speed Backbone LAN (Fire Alarm)Network ID#2 (Fire Alarm)Network ID#3 BACnet Workstation OpenGN (Security & Access Control) Network ID#1 (HVAC/Fan Control) Network ID#4
19. Next: Learn three rules! Every Device has a set of Objects Every Object has a set of Properties Messages & Services describe the above
20. BACnet object model
21. BACNet object properties change based on physical events Addressable relay modeled as binary output (supervised output circuit) Smoke Alarm modeled as binary input (alarm point)
22. Most useful messages & services Who-Is and I-Am Who-Is and I-Am may be used to dynamically bind Device IDs (Device Object Identifiers) to addresses ReadProperty ReadProperty-Request and ReadProperty-Response are used to “receive” a single property of an object from a BACnet device WriteProperty WriteProperty-Request and WriteProperty-Response are used to “transmit” a single property of an object between two BACnet devices
23. Mapping Fire alarm data into BACnet data (Alarm scenario) FIRE ALARM SIDE BACNET/BMS SIDE MANUAL STATION (Device) ADDRESS = N2L4A006 ACTIVITY = TRANSITION FROM NORMAL TO ALARM BINARY INPUT (Object) OBJECTID = 2004006 PRESENT_VALUE = 1 STATUS FLAGS = [1,0,0,0] EPICS (VENDOR DATA KEY) PRESENT_VALUE = ‘0’ IF NORMAL OR ‘1’ IN ALARM STATUS FLAGS = ‘[0,0,0,0]‘ IF NORMAL OR ‘[1,0,0,0]’ IN ALARM
24. DRIVING ADOPTION THROUGH SPECIFICATION & REGULATION LEARN MORE ABOUT BACNET
25. Self study & TIPS Tutorial, Overview http://www.bacnet.org Purchase the Standard http://www.ashrae.org/resources--publications/bookstore/standard-135 Download your own BACNet stack and develop your own interface http://sourceforge.net/projects/bacnet/ Test a product’s BACNet Interoperability level using VTS http://sourceforge.net/projects/vts/ Specify BACNet into your projects! http://fire.nist.gov/bfrlpubs/build99/PDF/b99051.pdf Guide To Specifying BACNet

26. The End

    For any questions/comments contact the author via email: Jason Falbo, P.Eng, M.B.A Vice President, Engineering The Mircom Group of Companies (MGC™) jfalbo@mircomgroup.com
27. Extra details for those interested Appendix a
28. OBJECT MODELLING, SERVICES, SECURITY BACNET PROTOCOL DEEP DIVEPart II – advanced topics
29. BACNet message routing BACNet works on Open System Interconnection (OSI) model of networking. BACNet works primarily on the Application, Network and Physical layer of OSI. Other layers were omitted/consolidated to make protocol efficient The diagram on the following slide shows how a packet is routed from a bacnet compatible application layer through the network layer to the physical layer.
30. APPLICATION GUI Update Application Engine Event Activation APPLICATION INTERFACE/ APPLICATION LAYER Service Calls (Who Is, Read Property, Write Property etc.) To Application Decoded Queue Request Generated to Application Encode Queue BACNet Encoder BACNet Decoder NETWORK LAYER Receive From Application Queue Send To Application Queue TSM MANAGER Sending Queue Receive Queue Receiving Thread Sending Thread BACnet Packet Network Packet Network (LAN, WAN, Internet, etc.)
31. BACnet security BACnet Security model is optional to use. The intent of designing this module is to provide peer entity, data origin and operator authentication, as well as data confidentiality and integrity. BACnet Security architecture provides Device Authentications, Data Hiding, User Authentication. BACnet Security model relies on the use of shared secrets called keys. Device Authentications and User Authentication are achieved through the use of message signatures and shared signature keys. Data hiding is achieved through encryption of the secure payload and shared encryption keys. Details on BACnet Security module can be found on : http://www.bacnet.org/Addenda/Add-2004-135g-PR1.pdf
32. Bacnet security - Shared Keys
33. Bacnet security – securing messages Encrypted Security Payload – Secured NPDU Control Bit in NPCI is changed to indicate Message contains Network Layer message rather than APDU The above diagram shows encrypted APDU placed in a security payload. Similarly we can do for NPDU. We can send Secured BVLL message for encrypted NPDU. We can encrypt the message using HMAC, MD5 or SHA-256. APDU
34. Bacnet web services BACnet uses standard way to integrate Web- based application, i.e. using XML, SOAP, WSDL, and UDDI open standards over Internet Protocol.
35. Key Definitions & Terminology BBMD: BACnet Broadcast Management Device Used to manage transmissions between networks NPDU: Network Layer Protocol Data Unit Specially formatted message that a BACNet device transmits over its physical link to route the information correctly APDU: Application Layer Protocol Data Unit EPICS: Electronic Protocol Implementation Conformance Statement Link to downloadable template: http://www.bacnet.org/DL-Docs/135-2008-ANNEX-A-rev-2010-11-02.doc BIBB: BACNet Interoperability Building Blocks