1 / 25

oBIX: Are we there yet? FMOC Summer 2005

oBIX: Are we there yet? FMOC Summer 2005. Toby Considine Co-Chair, OASIS oBIX TC Toby.Considine@unc.edu. Overview of Presentation. The Five Questions: What is oBIX (short version)? Why OASIS and Web Services? Why an Enterprise Architecture? Where we are now? What can I do to help?.

tilden
Download Presentation

oBIX: Are we there yet? FMOC Summer 2005

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. oBIX: Are we there yet?FMOC Summer 2005 Toby Considine Co-Chair, OASIS oBIX TC Toby.Considine@unc.edu

  2. Overview of Presentation The Five Questions: • What is oBIX (short version)? • Why OASIS and Web Services? • Why an Enterprise Architecture? • Where we are now? • What can I do to help?

  3. oBIX is:an Interface to Building Control Systems • Enabling mechanical and electrical control systems in buildings to communicate with enterprise applications • oBIX promises to improve operational effectiveness, giving facility managers and building owners increased knowledge and control of their properties.

  4. Which Building Control Systems? • Nearly 50 identified control silos • HVAC • Access Control • Event Management • Intrusion Detection • Lighting • Life / Safety • Electric Metering . . .many more

  5. Interface to Building Control Systems • What kind of data can we get from control systems? • Simple: • Room Temperature of Lobby • Lengthy: • List of people currently in East Wing with time of entry • Complex: • Current state of all systems across an entire campus • Reports: • Variation of internal humidity of sports hall over the last 6 months

  6. Why Enterprise Interface to Control Systems? • Mundane • Energy = Money • Transforming • Power Grid Reliability • Hydrogen Economy • Knowledge-based M&R • Vision: Control Systems as stars in • Minority Report • Terminator

  7. But there are so many standards… • oBIX is an open standard developed around XML to support web services and service oriented architecture This leads to…

  8. Why OASIS and Open Standards • Open – all technical details freely available • Building – any and all building systems • Information – pertinent system data • eXchange – interoperability • Cost of non-interoperability (15.8B / year) • http://www.bfrl.nist.gov/oae/publications/gcrs/04867.pdf

  9. Why OASIS and Web Services? • OASIS is a not-for-profit, international consortium dedicated to the development, convergence, and adoption of e-business standards. • OASIS Standards are developed through an open process, one that provides for fairness, transparency and full participation from theentire community. • oBIX is an OASIS Technical committee developing a standard for communication between building controls and the enterprise • OASIS Standards: UDDI, WSDL, WSDM, WS-Security, SAML, WS-Policy, BPEL. . .

  10. But let’s get grounded here: An actual mechanical engineer ponders control systems and the Enterprise. . . More potential ERPs than all other domains combined

  11. oBIX is not just about buildings • oBIX is about Buildings and the Enterprise based upon Enterprise IT standards and Enterprise architectures So what does it mean when we say “Enterprise IT standards”?

  12. Why an Enterprise Architecture • Highlight Issues Faced by to Enterprise IT • Discuss Web services and Service Oriented Architectures

  13. Challenges and issues facing business today • Provide a flexible business model • The marketplace is changing - businesses need to change too • Many existing IT systems are inhibitors to change: complex and inflexible • Existing integrations can be inhibitors to change: multiple technologies, point-to-point integration, inflexible models • Drive down cost • Eliminate duplicate systems • Re-use, don't re-build • Time to market • Simplify skills base • Reduce cycle time and costs for external business processes • Move from manual transactions with suppliers towards automated transactions • Facilitate flexible dealings with partners with minimal process or IT impact • Integrate across the enterprise • Integrate historically separate systems • Completion of mergers and acquisitions • Across physical and technology barriers

  14. Marketing Partners Partners Partners Sales Web Better integration continues to be the focus of IT departments "40% of IT spending is on integration” — IDC • Historical limitations: • Monolithic applications can’t be reused • Ad hoc integration creates connections that are difficult to change/maintain • Lack of standards limits ability to deliver meaningful interoperability “ Every $1 for software = $7 to $9 on integration” — Gartner

  15. 30% New Capability 45% New Capability 70% Sustaining & RunningExisting Capability Increases Value Creation 55% Existing Capability Decreases Maintenance & Delivery Companies want IT to deliver more business value Today’s IT Desired IT Source: Accenture I.T. Spending Survey

  16. What is a Web service? • A Web service is: • a software component whose interface is described via WSDL • is capable of being accessed via standard network protocols such as SOAP over HTTP. • a software system designed to support interoperable machine-to-machine interaction over a network. • easy to combine and recombine to meet the needs of customers, suppliers and business partners because it is: • built on open standards and therefore do not require custom-coded connections for integration • self-contained and modular SOAP Router Backend processes WSDL Document + Web service

  17. What is SOA? • A service-oriented architecture (SOA) is an enterprise-scale IT system architecture in which application functions are built as business aligned components (or "services") that are loosely-coupled and well-defined to support interoperability, and to improve flexibility and re-use. • An SOA separates out the concerns of the Service requestors and Service Providers (and Brokers). • A Service is a discoverable software resource which has a servicedescription. The service description is available for searching, binding and invocation by a service requestor. The service description implementation is realized through a service provider who delivers quality of service requirements for the service requestor. Services can be governed by declarative policies. • SOA is not a product– it is about aligning IT and business needs

  18. An IT Consultant view of Web Services • Web services can be a part of the answer • Service Oriented Architecture (SOA) is another part • The two are not the same thing: • Most of today's production Web services systems aren't service oriented architectures - they're simple remote procedure calls or point-to-point messaging via SOAP or well structured integration architectures • Most of today's production service oriented architectures don't primarily use Web services - they use ftp, batch files, asynchronous messaging etc. - mature technologies • Achieving the promoted benefits requires both SOA and Web services • Organizations should get interested in the combination of SOA + Web services • business flexibility requires IT flexibility • business flexibility enables a company to support the one constant of change business Thanks to Steve Graham, whose power Points I stole.

  19. service modeling Layered SOA Service Requestor Presentation Layer 5 Integration Architecture (Enterprise Service Bus) QoS, Security, Management & Monitoring (Infrastructure Service) Data Architecture & Business Intelligence 6 7 8 4 Business Process Process Choreography Services 3 Atomic and Composite Services Service Provider Components 2 Enterprise Components Existing Application Resources and Assets 1 Package Custom Application Industry Models Custom Application Package Composite service Atomic service

  20. Where is oBIX now? • 6 Vendor interoperability demo of v0.6 at April 2005 Builcon • v0.8 is current working draft • V1.0 due out in Fall 2005 • Strong support from Niagra, LONMARK, et al. • Many back-room conversations with BACnet-WS committee

  21. Building Automation and Enterprise Systems • Use Web services and SOA to make IT systems and Building Automation easier to integrate • Evolve oBIX 2.0 to align with the WSDM approach • Provides an abstraction over base Building Automation data • Better PM for enterprise developers • Define the “CIM” equivalent for resources in the BC • This might be AECXML or GBXML (Green Building XML) • Define the “capabilities” of the Building Automation system • Abstract and encapsulate the underlying physical device representation • Get building automation systems “on the bus”

  22. service modeling Layered Building AutomationSOA Standards Service Requestor Presentation Layer 5 Integration Architecture (Enterprise Service Bus) QoS, Security, Management & Monitoring (Infrastructure Service) Data Architecture & Business Intelligence 6 7 8 4 Business Process New Business-oriented automation and better IT Systems integration Process Choreography Services 3 oBIX v2.0 Atomic and Composite Services Service Provider Components 2 oBIX v1.0, AECXML, GBXML Enterprise Components Existing Application Resources and Assets 1 Package Custom Application Existing Building Controls Industry Models Custom Application Package Composite service Atomic service

  23. Customer Experience Billing Commissioning Enterprise Energy Mgmt Maintenance Mgmt BACnet WS oBIX Base Control Protocol v1.0 oBIX v2 Abstractions oBIX v2 Abstractions oBIX v2 Abstractions Enterprise Energy Management Other VerticalApplications BACnet IP “LON” WS NIAGRA EJB Proprietary Simple BACnet LONMARK NIAGARA Other Industries Roadmap to oBIX 2.0 Ad-Hoc Interfaces to Enterprise (if any) Applications on Native BACnet

  24. What Can I do? • As we move controls interfaces from API to Business Process, we need abstract models that • Hide internal complexity • Expose simpler Interface • Express Business Function

  25. We need work on the Enterprise Abstraction Models • Capabilities Models • One for each control silo • Analytics Models • M&V – Self Commissioning • Tenant Models • Cross-Silos “The Room” • Uses: Schedules and Variable Costs Can you help?

More Related