1. OASIS Open Building Information eXchange Technical Committee Patrick Gannon OASIS President & CEO BuilConn Europe Amsterdam, 9 November 2005 www.oasis-open.org/committees/obix

2. Where does oBIX fit in? What will oBIX do? What happened to all those SOA/WS road maps? Detours and blue highways on the SOA road

3. Where does oBIX fit in to standards?

4. © OASIS 2005 OASIS map of projects: Nov. 2005 Common transport (HTTP, etc.) Common language (XML) Discovery Description Orchestration & Management Security & Access Messaging Data Content ebXML MSG, ebXML IIC, WS-Reliability, WS-RX DSS, PKI, SAML, WS-Security, WS- SX, XCBF SPML, XACML, [DSML] DCML (x3), WSDM, WSRF, WS-Notification ASAP, BTP, CAM, ebXML-BP, WSBPEL, WSCAF, WS-TX AVDL, eGov, Election, eProc, Emergency, Legal XML(4), Materials, oBIX, PLCS, PPS, RemoteControl, TaxXML,TransWS, WAS. XLIFF, [Auto Repair], DITA, EntityRes, Topic Maps Pub.Subj., XDI, XRI ebXML CPPA, HumanML, UIML, WSRP ebXML RegRep, UDDI BCM, [Conformance], ebSOA, FWSI, SOA Blueprints, SOA-RM, Semantic- Execution RELAX NG, XSLT Conformance CIQ, CGM, DocBook, OpenDocument,, UBL S O A

5. © OASIS 2005 OASIS map of projects: Nov. 2005 Common transport (HTTP, etc.) Common language (XML) Discovery Description Orchestration & Management Security & Access Messaging Data Content ebXML MSG, ebXML IIC, WS-Reliability, WS-RX DSS, PKI, SAML, WS-Security, WS- SX, XCBF SPML, XACML, [DSML] DCML (x3), WSDM, WSRF, WS-Notification ASAP, BTP, CAM, ebXML-BP, WSBPEL, WSCAF, WS-TX AVDL, eGov, Election, eProc, Emergency, Legal XML(4), Materials, oBIX, PLCS, PPS, RemoteControl, TaxXML,TransWS, WAS. XLIFF, [Auto Repair], DITA, EntityRes, Topic Maps Pub.Subj., XDI, XRI ebXML CPPA, HumanML, UIML, WSRP ebXML RegRep, UDDI BCM, [Conformance], ebSOA, FWSI, SOA Blueprints, SOA-RM, Semantic- Execution RELAX NG, XSLT Conformance CIQ, CGM, DocBook, OpenDocument,, UBL S O A

6. © OASIS 2005 OASIS: Data Content n AVDL n CGMO WebCGM n CIQ n DocBook n eGov n ElectionML n Emergency Mgmt (Common Alerting) n EPS (Procurement) n LX-Court Filing n LX-eContracts n LX-eNotary n LX-Integ Justice n IHC (Health) n Materials n oBIX n OpenDocument n Product Lifecycle (PLCS) n PPS n Remote Control n TaxXML n Trans WS n UBL n WAS n XLIFF n [Auto Repair] Discovery Description Orchestration & Management Security & Access Messaging Data Content S O A

7. What will oBIX do?

8. © OASIS 2005 many many Today there are many devices, and many methods for connecting them

9. © OASIS 2005 Perspective Building owners want and need: Building Controls that can utilize and leverage the infrastructure of their existing intranets and Internet much longer lifecycle Facilities to be a data source, to help them better run their business: a much longer lifecycle for controls and facility data Easy integration of all facility management tasks so that they can operate more efficiently Conformance to global standards for data and networks, for all business systems

10. © OASIS 2005 Business View Asset Mgmt CMMS Facility Management System FMS Front End SecurityElectricalCCTV Other.. Fire Alarm Alarm HVAC Lighting Integration Business Systems (SAP, Oracle, Energy, Operations, etc.) Integration Owners have integration issues, both across current and future devices, and with the other business systems that want to use the data

11. © OASIS 2005 Challenges n Today many vendors are using XML and web services in their products, but in a non-standardized method that will not work with other devices or systems n Common standards are needed sooner rather then later, that work both within building systems, as well as with other business management systems

12. © OASIS 2005 Open Standards n Open standards are expected by owners today l Single seat operations, bringing data onto one dashboard l Extensibility: allow multiple re-uses tomorrow of data and events (identifications, events, alarms) used today l Avoiding vendor lock-in in many domains, and permitting modular changes in the future n BACnet, LonWorks, etc. are fine solutions, but neither was designed for the Internet, or loosely coupled asynchronous systems on any network. They do not have the SOA virtues of ready integration with other heterogenous legacy systems, or future needs

13. © OASIS 2005 Internet Standards n Internet standards (SOA & Web Services) are the future. These include l Physical -- Ethernet, TCP/IP l Human readable and interrogatable -- Web page-like l Machine readable - XML, SOAP, SOA n Global IT data standards for open communications between devices and applications

14. © OASIS 2005 context Data specifications must work within a context to be useful IP TCP URIs SMTP IMAP / POP3 HTML ASCII / Unicode Typical e-mail Almost all real-world data installations are composed of multiple standards

15. © OASIS 2005 OASIS: Infrastructure Standards n ebXML Registry n UDDI Spec Messaging n ebXML Messaging n ebXML IIC n WSRM TC (WS-Reliability) n WS-Reliable Exchange Discovery XML Discovery Description Orchestration & Management Security & Access Messaging Data Content S O A The transport, messaging and data repository functions -- getting data reliably from place to place -- are entirely solved in XML

16. © OASIS 2005 OASIS: Orchestration & Management Standards n ASAP n Business Transactions n CAM n ebXML-BP n WSBPEL n WS-CAF n WS-TX n DCML-Adoption n DCML-Apps & Services n DCML- Framework n WSDM (Mgmt) n WS-Notification n WS-Resource Framework XML Discovery Description Orchestration & Management Security & Access Messaging Data Content S O A Device vendors have well-established, powerful methods for network topology, device states, transactions and notifications between devices

17. © OASIS 2005 OBIX architecture Client PC’s w Browser (Anywhere) Intranet Enterprise Application Servers Network based controller Room Controller Room Controller BACnet LonTalk Controller LonTalk Controller Network based controller LonTalk Controller LonWorks Other XML based system Controller Other Protocols Common data structure over Ethernet / TCP-IP / HTTP O B I X

18. © OASIS 2005 Standards needed for:  Industry specific standards needed to define:  Data Modeling, units, accuracy, time standards, etc. for exchange of data  Definition of services for functions such as alarms, schedules, trends, etc.  Security in terms of both data authentication and encryption  Methods for network discovery and configuration  Must work for all facility management (HVAC, Lighting, Security, Energy, Electrical, Blinds, etc.)

19. © OASIS 2005 n Launched project at Buil Conn 2003 n Identified need to become an open standard n Transitioned to OASIS, with CABA consent, in 2004 n Strong technical progress made – internally at an v 0.7 release in March 2005 n Successful public demonstration with four vendors in March 2005 n An experimental Java oBIX Toolkit already out: sourceforge.net/projects/obix n Plan to release v 1.0 in early 2006 Progress in oBIX

20. © OASIS 2005 n oBIX Technical (XML) Standards Subcommittee l Producing the Base Control Protocol: XML formats, the Discovery Service, point control services and alarms n Power Systems Subcommittee l Power Metering, Power Analysis and Power Generation l Created Power Systems Services Requirements n Security Systems Subcommittee l Access Control, Intrusion Detection, CCTV Monitoring and Fire Detection & Life Safety Systems n Enterprise Requirements Subcommittee l Focused on what the enterprise, i.e., the owner or operator of a facility, wants from the building l Created Use Cases document n Roadmap Subcommittee l Goals and Directions for future work Participation in OASIS oBIX TC

21. © OASIS 2005 Contact Information: Patrick Gannon President & CEO patrick.gannon@oasis-open.org +1.978.761.3546 n www.oasis-open.org n www.xml.org n www.xml.coverpages.org