XML’s Role as a Standard for Building Automation

1. XML’s Role as a Standard for Building Automation Patrick Gannon President & CEO CABA XML Symposium Orlando, 9 February 2005

2. Open Standards for Building Automation • Future Shock – “De-perimiterization” • Information Technology Trends • Service Oriented Architecture • Key Directions in XML & Web Services Standards • What your company can do

3. Businesses have to deal with “Future Shock” daily!

4. Orderly business systems suffer…

5. De-perimiterization

6. A smooth sailing business environment is transformed…

7. Into a fight for your business survival

8. It’s enough to make you want to…

9. Information Technology Trends Technology & Business Economic Trends

10. Cultural Shift Business-to-Business Processes Sales and Distribution Consumer Services Internet Based Delivery The eBusiness Tidal Wave

11. Tidal Wave of Business Shift • Classic 1900’s Companies • Control Delivery • Control Services • Control Information • Have expensive acquisition processes and static relationships • Managed pricing and expectations • Information Age 21st Century • Consumer is empowered by information access • Businesses win by being open • Businesses win by leveraging new mechanisms to drive their own costs down. • Dramatic lower overall cost potential, higher level of services.

12. Structural Changes Increasing Competition Internet Business Models • Declining Customer Loyalty • Shorter Product Lifecycles • Tighter Delivery Deadlines • Product Sophistication • Inventory Constraints • Margin Erosion • Globalization • Outsourced Manufacturing • Multiple Distribution • Channels • Increased Partnering • Internet Strategy • New Markets • New ways to reach customers/suppliers • New systems required Competitive Marketplace 2000s – 2010s 1990s – 2000s 1980s – 1990s Source: BancBoston Robertson Stevens

13. Number of Business Interfaces / Services Complexity 1 Business Partners 10 100 1,000 Customer Service View • New business model requires highly customizable content • Enterprise support view requires self-maintaining components

14. Business Needs • Link traditional data exchanges (EDI or new XML) to business applications • Create business processes based on smart documents • Provide means for trading partners to quickly and easily locate re-usable components • Provide means for trading partners to customize methods to their own internal systems • Implement low cost server and client based solutions

15. XML driven Service Oriented Architecture Business Systems Customers Process Integration Open Web Service Interface Information Services Layer XML XML XML XML XML XML XML XML XML Business Enterprise Services Content Products Data

16. Future Vision for a Service Oriented Architecture

17. The Dawn of a New Era Built on Service Oriented Architecture

18. Vision of a Service-Oriented Architecture • A place where services are ubiquitous and organically integrated into the way we think and work. • A place where both users and providers of information interact through a common focus on services. • A world where technology is implemented within industry frameworks that operate on a global scale, enabled by open, interoperable standards.

19. A Common Web Service Framework Is Essential • To provide a sustainable foundation, • That will allow end-user companies to achieve the payback they require, • To invest widely in the service-oriented architecture.

20. Achieving Sustainable Business Benefits through a Open Standards for Web Services In this post-dot-com era, end user companies are expecting more liquidity and longevity of their assets. To achieve the ROI, Cost Reduction and Service Expansion benefits expected; the widespread deployment of standards-based Web services is essential.

21. Leading the Adoption of Web Services Standards

22. OASIS Mission OASIS drives the development, convergence and adoption of e-business standards.

23. Current Members • Software vendors • User companies • Industry organisations • Governments • Universities and Research centres • Individuals • And co-operation with other standards bodies

24. OASIS Members Represent the Marketplace

25. International Representation

26. OASIS is a member-led, international non-profit standards consortium concentrating on structured information and global e-business standards. • Over 650 Members of OASIS are: • Vendors, users, academics and governments • Organizations, individuals and industry groups • Best known for web services, e-business, security and document format standards. • Supports over 65 committees producing royalty-free and RAND standards in an open process.

27. Key Directions in OASIS Standards for Web Services

28. Approved OASIS Standards for Web Services • UDDI: Universal Description, Discovery & Integration • Defining a standard method for enterprises to dynamically discover and invoke Web services. • WSRP: Web Services for Remote Portlets • Standardizing the consumption of Web services in portal front ends. • WS-Reliability • Establishing a standard, interoperable way to guarantee message delivery to applications or Web services. • WSS: Web Services Security • Delivering a technical foundation for implementing integrity and confidentiality in higher-level Web services applications.

29. OASIS Web Services Infrastructure Work 14+ OASIS Technical Committees, including: • ASAP: Asynchronous Service Access ProtocolEnabling the control of asynchronous or long-running Web services. • WSBPEL: Business Process Execution LanguageEnabling users to describe business process activities as Web services and define how they can be connected to accomplish specific tasks. • WS-CAF: Composite Application FrameworkDefining an open framework for supporting applications that contain multiple Web services used in combination. • WSDM: Distributed ManagementDefining Web services architecture to manage distributed resources.

30. OASIS Web Services Infrastructure Work • WS-Reliability: Reliable MessagingEstablishing a standard, interoperable way to guarantee message delivery to applications or Web services. • WSN: NotificationAdvancing a pattern-based approach to allow Web services to disseminate information to one another. • WSRF: Resource FrameworkDefining an open framework for modeling and accessing stateful resources.

31. Standardizing Web Services Implementations For communities and across industries: • ebSOA: e-Business Service Oriented ArchitectureAdvancing an eBusiness architecture that builds on ebXML and other Web services technology. • FWSI: Framework for WS ImplementationDefining implementation methods and common functional elements for broad, multi-platform, vendor-neutral implementations of Web services for eBusiness applications. • oBIX: Open Building Information XchangeEnabling mechanical and electrical systems in buildings to communicate with enterprise applications. • Translation WS Automating the translation and localization process as a Web service.

32. Security for Web Services • Most e-business implementations require a traceable, auditable, bookable level of assurance when data is exchanged • IT operations demand “transactional” level of reliable functionality, whether it’s an economic event (booking a sale) or a pure information exchange • Dealings between divisions often need security and reliability as much as deals between companies

33. Approved OASIS Standards for Security • AVDL: Application VulnerabilityStandardizing the exchange of information on security vulnerabilities of applications exposed to networks. • SAML: Security Services Defining the exchange of authentication and authorization information to enable single sign-on. • SPML: Provisioning ServicesProviding an XML framework for managing the allocation of system resources within and between organizations. • XACML: Access ControlExpressing and enforcing authorization policies for information access over the Internet. • XCBF: Common Biometric FormatProviding a standard way to describe information that verifies identity based on human characteristics such as DNA, fingerprints, iris scans, and hand geometry. • WSS: Web Services SecurityAdvancing a technical foundation for implementing integrity and confidentiality in higher-level Web services applications.

34. OASIS Security Work • DSS: Digital Signature Services Defining an XML interface to process digital signatures for Web services and other applications. • PKI: Public Key Infrastructure Advancing the use of digital certificates as a foundation for managing access to network resources and conducting electronic transactions. • WAS: Web Application SecurityCreating an open data format to describe Web application security vulnerabilities, providing guidance for initial threat and risk ratings.

35. What should your company be doing?

36. Reducing Risk in new e-business technologies • Avoid reinventing the wheel • Stay current with emerging technologies • Influence industry direction • Ensure consideration of own needs • Realize impact of interoperability and network effects • Reduce development cost & time • savedevelopment on new technologies • share cost/time with other participants

37. What can your company do? • Participate • Understand the ground rules • Contribute actively Or… • Be a good observer In any case… • Make your needs known • Use cases, functions, platforms, IPR, priorities, availability, tooling • Be pragmatic: standardization is a voluntary process

38. Contact Information: Patrick Gannon President & CEO patrick.gannon@oasis-open.org +1.978.761.3546 • www.oasis-open.org • www.xml.org • www.xml.coverpages.org