XML Applications<\/p>\n\n\n\n
The Data Modeling Working Group is responsible for developing the BACnet framework(s) for complex data models both on the wire and in other machine-readable formats (such as CSML and JSON). They work in cooperation with the other working groups (AP, SG, etc.) to ensure that the framework(s) developed meet the needs of their specific use cases.<\/p>\n\n\n\n
This group was formed in November 2012. Convener: Scott Ziegenfus<\/a>, Hubbell Lighting<\/p>\n\n\n\n Join us as a Volunteer<\/a><\/p>\n\n\n\n The EL-WG is developing extensions to allow the monitoring of elevator systems with the BACnet protocol.<\/p>\n\n\n\n Integrating elevators into BACnet systems permits common observation and reporting stations for alarms and other events from elevators along with other BACnet building systems. Making elevators’ self-aware energy usage available to the building systems will also be a key element in building energy-efficiency systems and the Smart Grid.<\/p>\n\n\n\n Convener: Coleman Brumley, Jr.\u00a0 PassiveLogic <\/p>\n\n\n\n Join us as a Volunteer<\/a><\/p>\n\n\n\n This group recently completed the development of a new secure datalink layer for BACnet, BACnet\/SC (defined in Addendum bj<\/em>), that is built upon WebSockets and TLS. Future projects will include the development of new BACnet functionality that will complement BACnet\/SC, such as enhancements to the Network Port Object.<\/p>\n\n\n\n Since the design of BACnet began in 1987, much has changed in the world of computers, networking technology, and building automation systems. BACnet has been sufficiently flexible to handle many of these changes, but more changes are coming that may further challenge BACnet’s architecture. Here are some of the changes that could affect the requirements for building automation systems:<\/p>\n\n\n\n The BACnet IT working group’s primary task will be to enumerate the general communication requirements of building automation systems that will be deployed over the next several years and evaluate BACnet against those requirements. To the extent that BACnet does not meet those requirements, the working group will discuss, at a high level, how BACnet could be modified or redesigned in order to better meet those requirements. Based on the outcome of those discussions, the working group members might initiate projects to investigate various design options.<\/p>\n\n\n\n Convener: Jim Butler<\/a>, Cimetrics<\/p>\n\n\n\n Join us as a Volunteer<\/a><\/p>\n\n\n\n This group will work on issues relating to lighting applications.<\/p>\n\n\n\n This group will research, draft, and propose additions to the BACnet to support the requirements of lighting control applications. The group will work in cooperation with the NEMA Lighting Control Council, and the Illumination Engineering Society Controls Committee.<\/p>\n\n\n\n This group was formed in January 2001, and held its kick-off meeting on March 30, 2001, at NIST. The meeting centered on a discussion of the various functional aspects of lighting systems (dimming with various ramping and timing parameters, override situations, integration with other building systems, etc.) and what communication requirements these implied. Convener: Steve Karg<\/a>, The Watt Stopper \/ Legrand<\/p>\n\n\n\n Join us as a Volunteer<\/a><\/p>\n\n\n\n The goal of this group is to determine whether new objects and services are needed to facilitate the use of BACnet in life safety and security applications and, if so, to develop them.<\/p>\n\n\n\n This new group will research, draft, and propose additions to the BACnet to support the requirements of life safety and security applications. The first systems to be tackled were fire alarm and control systems. The group has developed several new objects and services to this end.<\/p>\n\n\n\n The group has completed work on the life safety features of BACnet needed for fire alarm systems. Attention is now focused on security system requirements.<\/p>\n\n\n\n The white paper “Physical Access Control with BACnet”<\/a> (updated September 2008) represents the ongoing conceptual work of the LSS-WG for extending the BACnet standard into the realm of Physical Access Control.<\/p>\n\n\n\n Convener: David Ritter<\/a>, Delta Controls<\/p>\n\n\n\n Join us as a Volunteer<\/a><\/p>\n\n\n\n This group will work on issues relating to network authentication, and the authorizing and transfer of control from one device to another.<\/p>\n\n\n\n The Network Security Working Group works on a variety of AAA (Authentication\/Authorization\/Auditing) topics and collaborates on security aspects with other groups such as the DM-WG (BACnet Web Services) and the IT-WG (BACnet Secure Connect). In addition to protecting communications, the group’s scope also includes Auditing and Reporting mechanisms to track network actors and their actions.<\/p>\n\n\n\n This group was formed in January 2001, and is working on assessing the various threats to building automation and control systems and determining the appropriate countermeasures. If you are interested in participating in the work of this WG, please contact the convener.<\/p>\n\n\n\n Convener: Dave Robin<\/a>, BSC Softworks<\/p>\n\n\n\n Join us as a Volunteer<\/a><\/p>\n\n\n\n This group is working on infrastructure issues related to new objects and services and the refinement of existing general-purpose objects and services.<\/p>\n\n\n\n This group is working on “infrastructure” modifications needed to support new objects or new services. The addition of, and refinements to, existing general-purpose objects and services are typically prepared by this group.<\/p>\n\n\n\n Some of the many issues under discussion are:<\/p>\n\n\n\n Convener: Frank Neher<\/a>, Lutron (fneher@lutron.com)<\/p>\n\n\n\n Join us as a Volunteer<\/a><\/p>\n\n\n\n This group is tasked with maintenance of the BACnet protocol stack. This includes maintenance of all of the link layers (Clauses 7 to 11, Annex J, Annex O, and Annex U), the network layer (Clause 6) and the application layer (Clause 5).<\/p>\n\n\n\n This new working group was created in Spring 2017 to include all work from the former IP-WG and MSTP-WG. The maintenance of the network layer and application layer in Clause 5 was moved from the OS-WG to this new group, in support of the OS-WG to focus on objects, services, and related parts of the standard.<\/p>\n\n\n\n The topics under discussion are:<\/p>\n\n\n\n Convener: Michael Osborne<\/a>, Reliable Controls (mosborne@reliablecontrols.com)<\/p>\n\n\n\n Join us as a Volunteer<\/a><\/p>\n\n\n\n The Semantic Interoperability Working Group is developing a comprehensive way to apply semantic formalisms to represent the context of building system data and relationships between the associated building systems and components. The objective of this work is to enable applications to find and understand the information in an automated way. This will facilitate the development and implementation of building analytics tools and enterprise knowledge applications that can implement a number of building system functions.<\/p>\n\n\n\n This working group is the home for development of proposed ASHRAE standard 223P Semantic Data Model for Analytics and Automation Applications in Buildings. It is also developing guidance for enhancements to the BACnet standard that relate to the use of the Tags properties in BACnet objects.<\/p>\n\n\n\n Join us as a Volunteer<\/a><\/p>\n\n\n\n This group will work on issues relating to communication between building automation and control systems and utility providers with a new focus on Smart Grid technologies.<\/p>\n\n\n\n The Smart Grid WG is all about enabling the building to be an active participant in the operation of the electric grid. This includes integration of facility load as a resource (demand response), customer owned generation (distributed generation), and customer owned storage (electrical, thermal, pumped water, etc.). SG-WG is working to define a building energy services interface (ESI) that receives OpenADR signals, market signals, utility meter data, and weather feeds, and then communicates on the internal BACnet network to manage consumption and receive load forecasts. The ESI can then provide external grid services (e.g., DR response) and serve data via BACnet web services to building clients (e.g., OpenADR signals, load history and forecasts).<\/p>\n\n\n\n SG-WG is evaluating different use cases to understand the required data, use of objects and services, storage and other details required to then serve data to external clients in FSGIM (ASHRAE 201) format via BACnet web services (Annex W). We are also examining semantic tags relevant to smart grid as input to the ASHRAE 223 semantic tag standard.<\/p>\n\n\n\n If you are interested in participating in the work of this WG, please contact the convener.<\/p>\n\n\n\n Convener: David Holmberg<\/a>, NIST<\/p>\n\n\n\n Join us as a Volunteer<\/a><\/p>\n\n\n\n This group is to serve as a liaison to the BACnet Testing Laboratories Working Group within BACnet International.<\/p>\n\n\n\n This group’s mandate is to extend and maintain Standard 135.1 – the BACnet Testing Standard, to extend and maintain the BACnet Interoperability Building Block definitions and Device Profiles, and to identify and resolve existing interoperability issues in the BACnet standard itself.<\/p>\n\n\n\n This group had its first meeting in Atlanta in November 2006. One of its main objectives will be to actively cooperate with the BTL-WG in a joint effort to reduce the time and work required to identify and resolve issues in the testing and specification of interoperable products.<\/p>\n\n\n\nElevator Working Group (EL-WG)<\/h3>\n\n\n\n
Information Technology Working Group (IT-WG)<\/h3>\n\n\n\n
Lighting Applications Working Group (LA-WG)<\/h2>\n\n\n\n
If you are interested in participating in the work of this WG, please contact the convener.<\/p>\n\n\n\nLife Safety and Security Working Group (LSS-WG)<\/h3>\n\n\n\n
Network Security Working Group (NS-WG)<\/h3>\n\n\n\n
Objects and Services Working Group (OS-WG)<\/h3>\n\n\n\n
Protocol Stack Working Group (PS-WG)<\/h3>\n\n\n\n
Semantic Interoperability Working Group (SI-WG)<\/h3>\n\n\n\n
Smart Grid Working Group (SG-WG)<\/h3>\n\n\n\n
Testing and Interoperability Working Group (TI-WG)<\/h3>\n\n\n\n