Você está na página 1de 35

Defining “Open”

Building Automation Systems

CSHE 46th Annual Institute


What does an "open" BAS really mean?

Presented by:

Joseph Klotz
Johnson Controls Business Development Manager – BAS
Outline

• Introduction
• Quick History of Building Automation Systems
• Influences on BAS today
• Defining Openness & Considerations
• Open Protocols
• Open Procurement
• Open Application Programing Interfaces (API)
• Open Software, Tools, and Support
• Review and Closing

3
DDC and BAS - where we’ve been

1980 1990 2000 2010


Technology
Market,

Trends

• Direct Digital • Distributed Controls • Supervisory Controllers • Web / IP


Controllers

• Improved operational • More accurate control • Improved user interfaces • Improved availability
Customer
Benefits

efficiency- less staff • Supervisory features • More complex controls anytime-anywhere


• Early energy efficiency • Building-wide scheduling • Open protocols • Lower installation costs
features • Modularized system • Multi-vendor integration • Early IT integration
Products
The
Competitors
The

Brands that have gone away: MCC Powers; Barber-Colman; Robertshaw; Invensys Building Systems; Andover; Anderson
Cornelius; Landis & Gyr; Direct Digital Controllers; Margaux; Computrols; ;CPC; Circon; Walker…
Influences which are changing BAS

Information Technology (IPV6; geolocation; voice recognition)


Chips: More power, more speed, more memory, lower costs
Cybersecurity
Building Systems Integration
Energy Generation, Energy Storage, Measurement, Management
Boiler Room Bob is retiring
More and more diverse users of BAS
Big Data
Contracting and Procurement
Changing BACnet standards (IPV6; Web Services; Tagging; SPC135 WG)
Other standards (Google Brillo/Weave; Samsung Artik; Apple Homekit;
Allseen Alljoyn
Why defining BAS openness matters

Openness means many different things to different users


Four Categories to help Define OPEN Building Automation Systems

1 Open Protocols

2 Open Procurement

3 Open API’s

4 Open Software Tools and Support


Defining Openness

1 Open Protocols
Built upon and using industry-developed “open” protocols
Ability to connect to and communicate with other vendors’ systems

Advantages:
• Simpler integrations between competitive BAS
• Simpler integrations with meters, lighting, security, fire, etc.
• Common understanding

Disadvantages:
• Version complexities
• Multiple systems supplying and servicing – who takes the lead?
1990’s Building Automation System
Digital Thick Client User
RTU controller Interface Software

Supervisory
Controller
Proprietary
telephone lines
proprietary Controller
Operating
System
Field Controller communication bus

Thick Client User


Interface Software

Field Controllers proprietary


proprietary

RS485 Bus Serial Communication

Master
Controller
BAS Technology: 20 years later

Protocols used in Building Automation Systems

BACnet
LonTalk
Modbus
OPC
IP / Web Services / SOAP
Profibus
Network Controller Protocols
BatiBUS Field Controller Protocols
EIB
KNX
DALI
Remote Browser
INTERNET Browser
UI

ENTERPRISE/MANAGEMENT LAYER
(IT infrastructure) Enterprise IP Network

LonTALK Field Controller Bus


LonTalk LonTalk
LonTalk

LonTalk
communications in
building automations
systems
Remote Browser BAS Server Third Party
configuration
User Interface INTERNET
software

Enterprise IP Network BACnet IP BACnet IP

BACnet Tunneling
BACnet MS/TP
BACnet MS/TP
E

E
E
BACnet Testing Laboratories – controller listings

The BACnet Testing lab is part of BACnet International, a vendor-neutral


organization dedicated to advancing open building automation systems.

BTL defined and tested compatibility


 B-SA – BACnet Smart Actuator

 B-SS - BACnet Smart Sensor

 B-ASC - BACnet Application Specific Controller

 B-AAC - BACnet Advanced Applications Controller

 B-BC - BACnet Building Controller


Modern Building Automation System Architecture

14
Data Integration Levels - summary
Web Services
OPC
Enterprise IT infrastructure IP
Ethernet/IP
Ethernet/IP HTTP, SOAP

Management Building
BACnet BACnet/IP Internet
LonTalk of
Fieldbus Things
Equipment Controller
LonTalk
BACnet MSTP (IoT)

Inputs Outputs
Information Technology Protocols and Evolution
Information Technology Evolution

Languages, Operating Systems, Data Exchange Protocols, and


the “user experience”
Standard PC LAN Architectures
the Internet
.NET
SOAP
XML
Web Services
CyberSecurity
Why is I.T. so important to the BAS world?
R&D Spending

Information
BAS / F&S Technology
Industries
combined

Number of Companies
Why I.T. Matters

Harbor Research, 2001:

“By 2010, there will be one Billion


more internet users than today –

and most of them won’t be humans.”


August 29th 1997
Building I.T.
IP SWITCH / ROUTER
I.T. Integration

Maintenance Center
IT
Internet / VPN
Infrastructure
TCP/IP BAS
Ethernet VLAN

Browser Interface
Site IT/PC Equipment BAS
Server
Site IT/PC Equipment

Site IT/PC Equipment

Control, Status, Schedules


Trends, and Alarm Data
from HVAC, meters, and
other equipment
BACnet MS/TP RS-485 Fieldbus
Information Technology: servers and portals
ERP

Financial Services Portals


Purchasing
 organize and manage multiple
connections
 provide a single point user

Human Resources
interface
 gather and store data from

Internet and IT multiple sources


Infrastructure  provide opportunity for data
Utilities Data Firewall
crunching and analysis

EMAIL
Browser Interface
BAS sharing IT Infrastructure IT network and PC's

Building
with BAS
Buildings with
other BAS
IT Router and
Firewall

other BAS

IT
Infrastructure

Buildings IT infrastructure and


without BAS PC's

BMS VLAN

Other
BAS Sites

Central
Utilities Interior and Exterior
HVAC equipment Energy Lighting Control
BAS Servers Operator Management, Monitoring
Interface and Control
Air Conditioning and
Ventilation Control.
What to consider
1 Open Protocols
Create ability to connect to and communicate with other vendors’ systems

What to consider:
• Why standards matter
• The existing system(s)
• Current & future protocol needs
• Compliance to open protocols
• The system’s (and its provider’s) ability to integrate

Ease of integration 
getting more value from
your BAS investment
Defining Openness
2 Open Procurement
Open BAS = open procurement model
Ability to purchase a BAS from multiple suppliers

Advantages:
• Cost & competitive pressure
• Multiple controllers sources
• Wider talent pool for BAS work/service

Disadvantages:
• Inconsistency
• Upgrades and expansions
• Steeper learning curves & system nuances – mixed systems
• Service: ability to service BAS from all levels
What to consider
2 Open Procurement
Creates the ability and option to buy/contract from multiple sources

What to consider:
• Pre-qualification: products, people, process
• Clear and enforceable specifications and standards
• Mixed BAS products and integrated systems
• Is the contractor fully supported by the manufacturer?
• Warranties
• Day 2 Service
• Additional (annual) costs
• Documentation, documentation, documentation

Multiple sources  initial


and operational savings
Challenges for Multiple Systems using a common “top end”

Web Browser UI The “top end”


components Web Server

BACnet/IP and/or IT standard Ethernet / IP infrastructure


proprietary TCP/IP

Each BAS uses the same configuration and


Network
Controllers ... ... programming tools for the Web Server and
Supervisory Controller, but each BAS OEM
also makes their own modifications.
BACnet MS/TP over RS-485

Each BAS uses


their own Field
Controllers and
their own
proprietary
software tools
Factory Packaged Controls

Advantages
• Factory testing
• Reduced field labor
• Arrive Alive
• No BAS network during construction
• Reduced commissioning time
• Consistent application of sequences
• Lower Risk
Defining Openness
3 Open Application Programming Interfaces (APIs)

Allows end user to develop integrations between devices and the BAS
Ability to access data and then a guide as to what that data means

Advantages: Glossary
• 3rd parties can provide additional offerings API: set of routines,
• Wider talent pool for customization work protocols and tools for
building software apps;
specify how software
components should interact
Disadvantages:
• Security risk Software Developer Kit:
set of software
• User dependency development tools that
allows the creation of apps
for a software package,
hardware platform,
computer system or similar
development platform
What to consider
3 Open APIs
Creates flexibility for building owners to choose or develop “best
in class” interfaces, dashboards and tools

What to consider:
• Understanding building owner’s needs
• Follows modern API practices
• Has robust documentation and sample programs
• Support
• for developers using the API
• for the 3rd party applications
• Licensing costs
• Who owns the data?

Not limited to only what the


manufacturer offers
Defining Openness
4 Open Software Tools & Support
Open user interface and programming & configuration tools
Available for direct purchase by end users

Advantages:
• Wider talent pool for BAS work/service (including DIY)
• Access to factory training and factory support

Disadvantages:

• Inconsistency
• Ability to circumvent training or certification
What to consider

4 Open Software Tools & Support


Creates flexible service and support options

What to consider:
• The KISS principle
• What is best for the facility, for the organization?
• Initial and ongoing costs
• Who provides the tools? Who provides support?
• Verify latest versions are provided; keeping current
• Manufacturer-certified training and support options
• Develop, follow and document standards
• Put it in the specification
Ability to self-perform  not
limited to only using the
installer or manufacturer
How do you define “open” in the context
of a Building Automation System?
 Uses standard protocols
 Access to tools for support & service
 Ability to purchase from multiple suppliers
 System integrates easily with other systems
 All of the above
Questions

Thank You

Você também pode gostar