1 / 26

“Interoperability of Diverse Security Systems – a Framework Approach” September 2008

“Interoperability of Diverse Security Systems – a Framework Approach” September 2008. Steve Lucas – Security Business Manager Scott Muench – Senior Application Engineer. © 2008 Tridium, Inc. Agenda. What is a Framework? Why Utilize a Framework? Industry Trends Emerging Standards

nida
Download Presentation

“Interoperability of Diverse Security Systems – a Framework Approach” September 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. “Interoperability of Diverse Security Systems – a Framework Approach”September 2008 Steve Lucas – Security Business Manager Scott Muench – Senior Application Engineer © 2008 Tridium, Inc.

  2. Agenda • What is a Framework? • Why Utilize a Framework? • Industry Trends • Emerging Standards • Framework Concepts • Example Solutions • Summary of Benefits • Q & A

  3. What is a Framework? • From Wikipedia • Framework, a basic conceptual structure used to solve or address complex issues. • Software Framework, a re-usable design for a software system (or subsystem). A software framework may include support programs, code libraries, a scripting language, or other software to help develop and glue together the different components of a software project.

  4. Why Use a Framework? • Integration only makes sense if it adds value • All stakeholders must agree • CFO, COO, CIO, Facilities Director, Security and Safety Director, Energy Manager • Test the business model then design a technology architecture • Think about usage scenarios and general information transfer required to meet the needs of the tenant and stakeholders • Model the interactions between systems • Develop an Architecture to represent the physical world • “Think, Model, Architect”

  5. Industry Trends • Closed Proprietary, OEM Driven Industry • Similar to the state of the BAS industry in early 90s • Industry Push to Open Systems • IP movement results in many like devices that need to communicate • No open standards…Wiegand reader communication protocol is the one exception • Emergence of many standards organizations • Increasing Role of IT Departments / Systems • Global permissions through corporate IT security policy • Convergence of physical and logical security • Network utilization issues associated with IP video

  6. Industry Trends (Cont) • Devices Moving to IP Network • Recent migration from serial based communications to IP • Network topology flattening, systems becoming more distributed • POE solutions becoming reality • Web Based Solutions Becoming More Accepted • No PC required, standard web browser access • Remote access pros and cons • Flattening of architecture • Facilities Seeking Integration with Rest of Building • Access control integrated with HVAC for energy management • Common user experience for all building systems

  7. Emerging Standards • Security Industry Association (SIA) • Open Systems Integration and Performance Standards (OSIPS) • Access Point Controller • Access Control Roles • Digital Video Standards • ASHRAE BACnet • Access Door Object Type • Access Point Object • OASIS oBIX • Common Alerting Protocol • Common Biometric Format • Directory Services Markup Language

  8. CFO HVAC Lighting Fire XML SQL HTTPHTML Facility Management ODBC SNMP JDBC FTP Security SMTP WAP Maintenance Energy And More Not One Protocol Will Dominate Systems Enterprise MODBUS Open System Framework LEGACY

  9. Traditional Security • Isolated Systems each with dedicated workstations Card Access Video Intrusion

  10. Current Security • Diverse systems, many different connections • Complexity creates barriers to true interoperability Card Access Video Intrusion

  11. Normalized Security • Diverse systems normalized to common object model • Interaction between security systems and unified workstation Card Access Video Intrusion

  12. Intelligent Building • Interaction between security systems and other building systems • Unified user experience Card Access Video Intrusion HVAC Lighting

  13. Card Access Tenant Billing Video Energy Intrusion Elevator HVAC Lighting Framework Example Unoccupied building, Saturday night System Interaction:

  14. Card Access Tenant Billing Video Energy Intrusion Elevator HVAC Lighting Framework Example “Access Granted, Zone 4” Scott swipes card at main entrance, works on 4th floor South System Interaction:

  15. Card Access Tenant Billing Video Energy Intrusion Elevator HVAC Lighting Framework Example “Access Granted, Zone 4” Video system needs to verify and record Scott’s entrance “Camera Preset 1, Initiate Recording” HTTP System Interaction:

  16. Card Access Tenant Billing Video Energy Intrusion Elevator HVAC Lighting Framework Example “Access Granted, Zone 4” Alarm system armed, need to disarm 4th floor intrusion zone “Camera Preset 1, Initiate Recording” HTTP “Disarm Intrusion Zone 4” LEGACY System Interaction:

  17. Card Access Tenant Billing Video Energy Intrusion Elevator HVAC Lighting Framework Example “Access Granted, Zone 4” Allow access to 4th floor “Camera Preset 1, Initiate Recording” HTTP “Disarm Intrusion Zone 4” LEGACY “Floor 3 Enable” XML System Interaction:

  18. Card Access Tenant Billing Video Energy Intrusion Elevator HVAC Lighting Framework Example “Access Granted, Zone 4” It is hot in Scott’s office, turn on AC “Camera Preset 1, Initiate Recording” HTTP “Disarm Intrusion Zone 4” LEGACY “Floor 3 Enable” “Zone 4 Occupied” XML System Interaction:

  19. MODBUS® Card Access Tenant Billing Video Energy Intrusion Elevator HVAC Lighting Framework Example “Access Granted, Zone 4” Scott needs light on 4th floor hallway and office “Camera Preset 1, Initiate Recording” HTTP “Circuit 1, 2 ON” “Disarm Intrusion Zone 4” LEGACY “Floor 3 Enable” “Zone 4 Occupied” XML System Interaction:

  20. MODBUS® Card Access Tenant Billing Video Energy Intrusion Elevator HVAC Lighting Framework Example “Access Granted, Zone 4” Lights and AC for Scott used 50 kWH “Camera Preset 1, Initiate Recording” “Totalize light and HVAC for Zone 4” HTTP “Circuit 1, 2 ON” “Disarm Intrusion Zone 4” LEGACY “Floor 3 Enable” “Zone 4 Occupied” XML System Interaction:

  21. MODBUS® Card Access Tenant Billing Video Energy Intrusion Elevator HVAC Lighting Framework Example “Access Granted, Zone 4” “Generate / email Invoice for Sat” Invoice Scott for $150 of after hours energy usage SMTP “Camera Preset 1, Initiate Recording” “Totalize light and HVAC for Zone 4” HTTP “Circuit 1, 2 ON” “Disarm Intrusion Zone 4” LEGACY “Floor 3 Enable” “Zone 4 Occupied” XML System Interaction:

  22. Central Server Full client workstations Isolated Systems Host Based Server Client Workstation Traditional Architecture Local Area Network Energy HVAC Video Access Control Intrusion Lighting Elevator Control

  23. Network topology is flattening Systems becoming more distributed Integrations through IP open protocols Embedded Controller Web Browser Local Area Network HVAC Energy Access Control Video Intrusion Elevator Control Lighting Framework Architecture Tenant Billing

  24. Think about Advantages from a Business Perspective • Multi-tenant Office Building • Marketed as Class A, High tech, Energy efficient, “Green”, Comfortable and Safe • Systems being installed: • Card Access/Elevator Access • HVAC • Lighting • Energy Monitoring • Business Enterprise • HVAC and Lights from 7am-7pm M-F • After hours usage billed extra • What degree of systems integration makes sense? • Where can I derive value?

  25. Benefits of a Framework Approach • Open Architecture • Maximum freedom of choice for end users • Competitive marketplace • Ease of systems integration / interoperability • Reduced installation / upgrade costs • Vendor / protocol neutral platform • Niagara Framework • Solutions focused, open framework architecture • Capability to support many different communication protocols – legacy and open standards • Integrated application development tools to customize solutions • Scalable, embedded solution with built in internet standards

  26. Q & A • We would like your feedback on today’s TridiumTALK • If you have any further questions, comments or topic suggestions, please email them to SalesSupport@Tridium.com • Exhibiting at ASIS – Booth # 4905 – stop by and see us! Steve Lucas Rick Weisensale Scott Muench

More Related