obix: are we there yet? fmoc summer 2005
DESCRIPTION
oBIX: Are we there yet? FMOC Summer 2005. Toby Considine Co-Chair, OASIS oBIX TC [email protected]. 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?. - PowerPoint PPT PresentationTRANSCRIPT
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?
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.
oBIX is:an Interface to Building Control Systems
Which Building Control Systems?
Nearly 50 identified control silos HVAC Access Control Event Management Intrusion Detection Lighting Life / Safety Electric Metering
. . .many more
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
Interface to Building Control Systems
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
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…
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
Why OASIS and Open Standards
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. . .
But let’s get grounded here:
An actual mechanical engineer ponders control systems and the Enterprise. . .
More potential ERPs than all other domains combined
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”?
Why an Enterprise Architecture
Highlight Issues Faced by to Enterprise IT
Discuss Web services and Service Oriented Architectures
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
Better integration continues to be the focus of IT departments
"40% of IT spending is on
integration” — IDC
“ Every $1 for software = $7 to $9
on integration”— Gartner
Marketing
Partners
Web
Partners
Sales
PartnersHistorical 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
Companies want IT to deliver more business value
Source: Accenture I.T. Spending SurveySource: Accenture I.T. Spending Survey
Today’s IT
Desired IT
IncreasesIncreasesValue CreationValue Creation
DecreasesDecreasesMaintenance &Maintenance &
DeliveryDelivery
30%30%New New
CapabilityCapability
70%70%Sustaining & Sustaining &
RunningRunningExistingExisting
CapabilityCapability
45%45%New New
CapabilityCapability
55%55%Existing Existing
CapabilityCapability
SOAPRouter
Backendprocesses
WSDLDocument+
Webservice
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
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 service
description. 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
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.
Qo
S, S
ecu
rity, Ma
na
ge
me
nt &
Mo
nito
ring
(Infra
structu
re S
ervice
)
Da
ta A
rchite
cture
& B
usin
ess In
tellig
en
ce
Layered SOA In
teg
ratio
n A
rchite
cture
(En
terp
rise S
ervice
Bu
s)
service m
odeling
Existing Application Resources and Assets
PackageCustom
Application
Services
Business Process
Components
Process Choreography
Atomic and Composite Services
4
3
2
1
6 7
Enterprise Components
Custom Application
Package
Se
rvice R
eq
ue
stor
Se
rvice P
rovid
er
Presentation Layer85
IndustryModels
Composite service
Atomic service
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
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”
Qo
S, S
ecu
rity, Ma
na
ge
me
nt &
Mo
nito
ring
(Infra
structu
re S
ervice
)
Da
ta A
rchite
cture
& B
usin
ess In
tellig
en
ceLayered Building Automation SOA Standards
Inte
gra
tion
Arch
itectu
re(E
nte
rprise
Se
rvice B
us)
service m
odeling
Existing Application Resources and Assets
PackageCustom
Application
Services
Business Process
Components
Process Choreography
Atomic and Composite Services
4
3
2
1
6 7
Enterprise Components
Custom Application
Package
Se
rvice R
eq
ue
stor
Se
rvice P
rovid
er
Presentation Layer85
IndustryModels
Composite service
Atomic service
Existing Building Controls
oBIX v1.0, AECXML, GBXML
oBIX v2.0
New Business-oriented automation and better IT Systems integration
Other Industries
NIAGARALONMARKSimple BACnet
ProprietaryNIAGRA EJB“LON” WS
BACnet IP oBIX Base Control Protocol v1.0BACnet WS
Other Vertical
Applications
Enterprise Energy
ManagementApplications
on
Native
BACnet
Ad-Hoc Interfaces to Enterprise (if any)oBIX v2 AbstractionsoBIX v2 AbstractionsoBIX v2 Abstractions
Maintenance MgmtEnterprise Energy Mgmt
CommissioningBillingCustomer Experience
Roadmap to oBIX 2.0
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
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?