The most recent publication the "BACnet | A Data Communication Protocol for Building Automation and Control Networks" standard is ANSI/ASHRAE Standard 135-2012 and supersedes ANSI/ASHRAE Standard 135-2010. Past publications include 2008, 2004, 2001, and 1995.

"BACnet was designed to gracefully improve and evolve as both computer technology and demands of building automation systems change."

(ref: forward of Std 135-2012)

The most current definition of BACnet Web Services in Std 135-2012 can be found in "ANNEX N - BACnet/WS WEB SERVICES INTERFACE (NORMATIVE)", beginning on page 915. This BACnet module for Drupal references this as BACnet Web Services 1 (BWS1).

The ASHRAE Standard Project Committee 135 (the BACnet committee) released "Proposed Addendum am to Standard 135-2012, BACnet® - A Data Communication Protocol for Building Automation and Control Networks" for first public review April 2014.

The proposed changes are summarized below.
135-2012am-1 Extend BACnet/WS with RESTful services for complex data types and subscriptions, p. 10
135-2012am-2 Extract data model from Annex Q into separate common model
135-2012am-3 Rework Annex Q to be an XML syntax for the common model
135-2012am-4 Add a JSON syntax for the common model
135-2012am-5 Replace Annex N SOAP services with a migration guide.
135-2012am-6 Change Clause 21 identifiers to use a consistent format.

This 1st 60-day Publication Public Review occurred from April 11 to June 10, 2014 . Comments received are under review by the BACnet committee and a second public review is eminent.

So, for the sake of this BACnet module for Drupal, we'll plan to reference the next final publication (2015?) as BACnet Web Services 2 (BWS2).

Hopefully, recognizing this now is the means to account for a single migration path for both D7 to D8 and well as BWS1 to BWS2, simultaneously, in the present dev effort.

Comments

dbt102’s picture

dbt102 commented

This issue was posted as a result of clarifying phone calls and emails from those involved in the present community review process. While the current code is simple, stable and error free, there is an expressed desire to make it even elegant prior to the stable release of Phase 1 (ref: Roadmap). However, the module is presently getting favorable reviews.

So, I'm changing the status to "postponed" for now, keeping it in the Phase 1 roadmap. If we can implement this change prior to final approval, great! If not, we'll get it I'n at the start of Phase 2.

dbt102’s picture

dbt102 commented
Status: Active » Postponed
dbt102’s picture

dbt102 commented

One notable change to watch for, that is presently being worked on, will the the addition of the BACnet_UI module to better accommodate additional features and ease the upgrade path.

  • dbt102 committed 838011a on 7.x-1.x 
    #2337583#comment-9145193 by dbt: Added BACnet_UI to incorporate RESTful...
dbt102’s picture

dbt102 commented
Status: Postponed » Closed (fixed)

Support has been added for future BACnet Standards.

On the block configuration page, start for BWS2 prototype block has been added.

Integral to BWS2 integration is incorporation of the concept BACnet Vendor ID. As a BACnet client, ASHRAE has assigned #751 to use for this purpose. At http://dev-openenergy-rest-service.gotpantheon.com a RESTful server has been setup and tagged with #754 (also assigned by ASHRAE).

The client makes the call to the server for a point value, the server replies by sending that point value, along with the ID # of the client and server involved in this transaction.

Additional functionality will be incorporated upon completion of phase 1 approval/release of a stable project version.

Changing status to closed/fixed, as functional testing mechanism has been built into BWS2 portion of module, and BWS1 has been successfully test against several different live systems.