Presentation is loading. Please wait.

Presentation is loading. Please wait.

Jason Falbo, P.Eng, M.B.A VP Engineering The Mircom Group of Companies

Similar presentations


Presentation on theme: "Jason Falbo, P.Eng, M.B.A VP Engineering The Mircom Group of Companies"— Presentation transcript:

1 Jason Falbo, P.Eng, M.B.A VP Engineering The Mircom Group of Companies jfalbo@mircom.com 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 BRIEF HISTORY OF FIRE ALARM SYSTEMS INTEGRATION From Hardwired Interfaces to Software Interoperability

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 OPEN End Switch Electrical Supervisory Device Return Air Damper CLOSED End Switch Electrical Supervisory Device Supply Damper Actuator Electrical Supervisory Device Return Air Smoke Damper Actuator Electrical Supervisory Device Supply Air Damper CLOSED End Switch Supervisory Device Supply Air Damper OPEN Supervisory Device Supply Air Damper Pneumatic Actuator Return Air Smoke Damper Pneumatic Actuator Return Air Fire Alarm Damper Actuator Relay Damper Status Monitor Modules Supply Air Damper Actuator Relay Smoke Control: The Old Way

6 MODERN DRIVERS FOR CHANGE Trends, History, and Purpose

7 INDUSTRY TRENDS IN INTEROPERABILITY HealthcareFinancial Services  http://www.hl7.org  http://www.xbrl.org/ Fire Protection  http://www.bacnet.org/

8 INTEGRATION: COMPLEX METHOD Return Air Damper OPEN End Switch Electrical Supervisory Device Return Air Damper CLOSED End Switch Electrical Supervisory Device Supply Damper Actuator Electrical Supervisory Device Return Air Smoke Damper Actuator Electrical Supervisory Device Supply Air Damper CLOSED End Switch Supervisory Device Supply Air Damper OPEN Supervisory Device Supply Air Damper Pneumatic Actuator Return Air Smoke Damper Pneumatic Actuator Return Air Fire Alarm Damper Actuator Relay Damper Status Monitor Modules Supply Air Damper Actuator Relay Smoke Control: The Old Way

9 net  FACP with Native BACnet Interface  Physical Ethernet port Connection on FACP Main Board MD-871A Main Board net BACnet Ethernet Connection INTEGRATION: SIMPLIFIED METHOD

10 THE FUTURE: SOFTWARE INTERFACES  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  BACNet was designed to allow interoperable communication of building automation and control systems for applications such as heating, ventilating, air-conditioning control, lighting control, access control, fire protection systems and their associated equipment. BACnet: ANSI/ASHRAE Standard 135-1995: BACNet--A Data Communication Protocol for Building Automation and Control Networks.

11 BACNET STANDARD HAS BEEN ADOPTED BY 612* MANUFACTURERS WORLDWIDE CountryVendorsCountryVendorsCountryVendors USA228Netherlands10Finland2 Germany68Hong Kong8Ireland2 Canada51Poland8Slovakia2 Japan51Sweden8New Zealand2 Australia20Austria7Serbia2 United Kingdom 19Taiwan7Spain2 China16Malaysia6Argentina1 Korea15 Czech Republic 5Belgium1 Switzerland15India4Croatia1 Denmark11Israel4Estonia1 France11Brazil3Hungary1 Italy11South Africa3Latvia1 http://www.bacnet.org/VendorID/index.html *as of September 12 th 2012

12 BACNET IMPLEMENTATION CASE STUDY BACnet Implementation

13 BACNET SETUP: STEP ONE (ACTIVATE)  Use MGC’s Fire Alarm Panel Configurator to activate BACnet functionality:  1. Run TCP/IP Services  2. Activate BACNet Services

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  Provide the list of BACNet points to the BMS system integrator  The Integrator will map the auxiliary system activities to FACP point state changes BACNET SETUP STEP THREE (DEPLOY) BINARY INPUTS LIFE SAFETY POINTS

16 CLIMATE MONITORING LIGHTING CONTROL SMOKE MANAGEMENT & CONTROL SECURITY-OCCUPANT- MONITORING VIDEO-SMOKE-CONFIRMATION SAFE ELEVATOR EGRESS INTEGRATION : OPTIMIZED METHOD

17 BACNET PROTOCOL DEEP DIVE PART I - BASICS How Does it Work?

18 FIRST START WITH CHOICE OF BACNET NETWORK ARCHITECTURE High Speed Backbone LAN net BACnet Workstation OpenGN (Security & Access Control) Network ID#1 (HVAC/Fan Control) Network ID#4 (Fire Alarm)Network ID#2 (Fire Alarm)Network ID#3

19 NEXT: LEARN THREE RULES! 1.Every Device has a set of Objects 2.Every Object has a set of Properties 3.Messages & Services describe the above

20 BACNET OBJECT MODEL

21 BACNET OBJECT PROPERTIES CHANGE BASED ON PHYSICAL EVENTS  Smoke Alarm modeled as binary input (alarm point)  Addressable relay modeled as binary output (supervised output circuit)

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 LEARN MORE ABOUT BACNET DRIVING ADOPTION THROUGH SPECIFICATION & REGULATION

25 SELF STUDY & TIPS  Tutorial, Overview  http://www.bacnet.org http://www.bacnet.org  Purchase the Standard  http://www.ashrae.org/resources--publications/bookstore/standard-135 http://www.ashrae.org/resources--publications/bookstore/standard-135  Download your own BACNet stack and develop your own interface  http://sourceforge.net/projects/bacnet/ http://sourceforge.net/projects/bacnet/  Test a product’s BACNet Interoperability level using VTS  http://sourceforge.net/projects/vts/ http://sourceforge.net/projects/vts/  Specify BACNet into your projects!  http://fire.nist.gov/bfrlpubs/build99/PDF/b99051.pdf  Guide To Specifying BACNet http://fire.nist.gov/bfrlpubs/build99/PDF/b99051.pdf

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 APPENDIX A Extra details for those interested

28 BACNET PROTOCOL DEEP DIVE PART II – ADVANCED TOPICS OBJECT MODELLING, SERVICES, SECURITY

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 INTERFACE/ APPLICATION LAYER APPLICATION Event Activation Application Engine GUI Update Service Calls (Who Is, Read Property, Write Property etc.) Request Generated to Application Encode Queue To Application Decoded Queue BACNet Encoder BACNet Decoder NETWORK LAYER Network (LAN, WAN, Internet, etc.) Receive From Application Queue Send To Application Queue TSM MANAGER Receive QueueSending Queue Receiving Thread Sending Thread BACnet PacketNetwork Packet

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 http://www.bacnet.org/Addenda/Add-2004-135g-PR1.pdf

32 BACNET SECURITY - SHARED KEYS BACNet Security Key Pairs General – Network Access Key User Authenticated Application Specific InstallationDistributionDevice-Master

33 BACNET SECURITY – SECURING MESSAGES  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. Encrypted Security Payload – Secured NPDU Control Bit in NPCI is changed to indicate Message contains Network Layer message rather than APDU 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 DeviceBACnet Broadcast Management Device  Used to manage transmissions between networks  NPDU: Network Layer Protocol Data UnitNetwork 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 UnitApplication 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.dochttp://www.bacnet.org/DL-Docs/135-2008-ANNEX- A-rev-2010-11-02.doc  BIBB: BACNet Interoperability Building Blocks


Download ppt "Jason Falbo, P.Eng, M.B.A VP Engineering The Mircom Group of Companies"

Similar presentations


Ads by Google