E N D
1. BACnet IT September 8th, 2010 teleconference topics overview
2. BACnet IT goal review Trend: convergence of IT & BAS infrastructure
Can we design a “next-gen” IT-friendly BACnet
Multiple standards bodies are working on new protocols for:
Sensor networks
Energy management
and other “ubiquitous” networking applications
These newer standards use Aggressive Internet technologies like http, REST, XML, ...
The core value of BACnet is in the object model
This should be retained largely unchanged
This would ensure interoperability between current BACnet & BACnet IT
3. Things BACnet IT must fix BBMDs
Difficult to configure
Fragile (breaks if IT changes your IP subnets)
Broadcasts that span multiple subnets
Risk of broadcast storms
Excessive bandwidth usage
Can cause non-linear network degradation as the network size grows
Layer violations
Network addresses leak into application layer
Doesn’t transit NATs
Breaks if IT changes your network addresses
4. Things BACnet IT could fix Address space management
Many address spaces: Device name, Device ID, BACnet network number, base network layer addresses = difficult to maintain!
Improve firewall traversal
BACnet not recognized by firewalls
Use of more standard/Aggressive technologies
Replace BACnet services with comparable Internet standards (e.g. NTP, FTP)
5. Minimal vs. Aggressive Minimal Change only what needs to be changed IT friendliness IP-based network layer, clean IPv6 support Ease deployment and manageability Aggressive Make more substantial changes Bias toward more modern protocols (SSL, HTTP, REST, etc.) Aggressively eliminate other BACnet services in favor of established Internet protocols (e.g. FTP, NTP, Atom) A clean break from the past – an opportunity to rethink BACnet’s object and services model