oasis open building information exchange technical committee patrick gannon oasis president &...

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

Upload: george-robinson

Post on 27-Dec-2015

215 views

Category:

Documents


0 download

TRANSCRIPT

OASIS Open Building Information eXchange Technical Committee

Patrick GannonPatrick GannonOASIS President & CEOOASIS President & CEO

BuilConn Europe BuilConn Europe Amsterdam, 9 November 2005Amsterdam, 9 November 2005

www.oasis-open.org/committees/obixwww.oasis-open.org/committees/obix

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

Where does oBIX fit in to standards?

© OASIS 2005

OASIS map of projects: Nov. 2005Common 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 AS O A

© OASIS 2005

OASIS: Data Content AVDL CGMO WebCGM CIQ DocBook eGov ElectionML Emergency Mgmt

(Common Alerting) EPS (Procurement) LX-Court Filing LX-eContracts LX-eNotary LX-Integ Justice

IHC (Health) Materials oBIX OpenDocument Product Lifecycle

(PLCS) PPS Remote Control TaxXML Trans WS UBL WAS XLIFF [Auto Repair]

Discovery

Description

Orchestration & Management

Security & Access

Messaging

Data Content

S O AS O A

What will oBIX do?

© OASIS 2005

Today there are manymany devices, and manymany methods for

connecting them

© OASIS 2005

Perspective

Building owners want and need:• Building Controls that can utilize and

leverage the infrastructure of their existing intranets and Internet

• Facilities to be a data source, to help them better run their business: a much longer much longer lifecyclelifecycle 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

© OASIS 2005

Business View

Asset MgmtAsset Mgmt CMMSCMMS

Facility Management SystemFacility Management System

FMS Front EndFMS Front End

SecuritySecurity

ElectricalElectrical

CC

TVC

CTV

Other ..

Other ..

FireFire

Alarm

Alarm

HVA

CH

VAC

LightingLighting

IntegrationIntegration

Business Systems(SAP, Oracle, Energy, Operations, etc.)

Inte

gra

tion

Inte

gra

tion

Owners have integration issues, both across current and future devices, and with the other business systems that want to use the data

© OASIS 2005

Challenges

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

Common standards are needed sooner rather then later, that work both within building systems, as well as with other business management systems

© OASIS 2005

Open Standards Open standards are expected by owners today

Single seat operations, bringing data onto one dashboard

Extensibility: allow multiple re-uses tomorrow of data and events (identifications, events, alarms) used today

Avoiding vendor lock-in in many domains, and permitting modular changes in the future

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

© OASIS 2005

Internet Standards

Internet standards (SOA & Web Services) are the future. These include

Physical -- Ethernet, TCP/IP

Human readable and interrogatable -- Web page-like

Machine readable - XML, SOAP, SOA

Global IT data standards for open communications between devices and applications

© OASIS 2005

Data specifications must work within a contextcontext to be useful

IPTCP

URIs

SMTP

IMAP / POP3

HTML

ASCII / UnicodeTypical e-mail

Almost all real-world data installations are composed of multiple standards

© OASIS 2005

OASIS: Infrastructure Standards

ebXML Registry UDDI Spec

Messaging ebXML Messaging ebXML IIC WSRM TC (WS-Reliability) WS-Reliable Exchange

Discovery

XML

Discovery

Description

Orchestration & Management

Security & Access

Messaging

Data Content

S O AS O A

The transport, messaging and data repository functions -- getting data reliably from place to

place -- are entirely solved in XML

© OASIS 2005

OASIS: Orchestration & Management Standards

ASAP Business

Transactions CAM ebXML-BP WSBPEL WS-CAF WS-TX

DCML-Adoption DCML-Apps &

Services DCML-

Framework WSDM (Mgmt) WS-Notification WS-Resource

FrameworkXML

Discovery

Description

Orchestration & Management

Security & Access

Messaging

Data Content

S O AS O A

Device vendors have well-established, powerful methods for network topology, device states,

transactions and notifications between devices

© OASIS 2005

OBIX architecture Client PC’sw Browser (Anywhere)

Intranet

EnterpriseApplication

Servers

Network based

controller

RoomController

Room Controller

BACnet LonTalk Controller

LonTalk Controller

Network based

controller

LonTalk Controller

LonWorks

Other XML

based system

Controller

Controller

Other Protocols

Common data structure over Ethernet / TCP-IP / HTTP

O B I XO B I XO B I XO B I X

© 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.)

© OASIS 2005

Launched project at Buil Conn 2003 Identified need to become an open standard Transitioned to OASIS, with CABA consent, in

2004 Strong technical progress made – internally at an

v 0.7 release in March 2005 Successful public demonstration with four

vendors in March 2005 An experimental Java oBIX Toolkit already out:

sourceforge.net/projects/obix Plan to release v 1.0 in early 2006

Progress in oBIX

© OASIS 2005

oBIX Technical (XML) Standards Subcommittee Producing the Base Control Protocol: XML formats, the Discovery

Service, point control services and alarms Power Systems Subcommittee

Power Metering, Power Analysis and Power Generation Created Power Systems Services Requirements

Security Systems Subcommittee Access Control, Intrusion Detection, CCTV Monitoring and Fire

Detection & Life Safety Systems Enterprise Requirements Subcommittee

Focused on what the enterprise, i.e., the owner or operator of a facility, wants from the building

Created Use Cases document Roadmap Subcommittee

Goals and Directions for future work

Participation in OASIS oBIX TC

© OASIS 2005

Contact Information:

Patrick Gannon

President & CEO

[email protected]

+1.978.761.3546

www.oasis-open.org www.xml.org www.xml.coverpages.org