re: Bacnet Installation Dilemma

Daryl Clasen — Fri, 13 Nov 2009 21:54:20 GMT

The architecture isn't necessarily the problem. The vendors implementation of the protocol is the problem. It doesn't even require a "master integrator". Simply it requires the ability for open configuration tools down to device level. This owner unfortunately has multiple subsystems. This will be significantly more expensive situation to rectify.

re: Bacnet Installation Dilemma

ronpadilla — Fri, 13 Nov 2009 14:37:27 GMT

There are 2 inherent problems with the implimentation of this architecture. The first is that all BACnet control systems utilize some sort of proprietary software to write the appropriate application programs. In your specification, it should include the provisions to add this to each system as well as the hardware and interface cables to the project and it should be licensed to you as the owner. All database files that were used to create these applications should be stored on this hardware and be in your possession prior to acceptance. In these cases, it must also be clear that you define all parameters that you want to be exposed to the network. This includes read values as well as write values. For instance, set points and differentials for control programs do not get automatically exposed to the network for read/write interfaces with a network controller or front end.

The second problem is that the Front End hardware and software was purchased from a Controls Manufacturer which most likely has a license agreement that states that other contractors do not have the right to use this software or hardware. The "Front End" must be purchased from a third party manufacturer that provides these software/hardware solutions from a variety of distribution sources. When you have this, you can specify that the work on the front end can be performed by an authorized system integrator of that product.

We have a multi-year contract with a large school district who we have worked with to develop this 2 piece specification. They have standardized on using our services in an open book pricing agreement to handle all of their Front End needs (as well as standards) and bid out the controls. They have used LonWorks as their standard, but the solution will work with BACnet also if done properly. One of our biggest roles for the owner is that we prepare the network level point databases that will be used for all control applications and this is provided in the specifications for each building. The controls contractor who is successful will get an electronic spreadsheet of all points and naming conventions for all of their controllers on the network. We work with them to develop these and test to verify that these were actually installed properly.

In doing this to the extent necessary, you will get competitive bidding, network standards, and have choices as to who will service and maintain these systems.

Today, the biggest problem that owners face is that the consulting engineering community does not fully understand all of these issues. Thus, they are not addressed in specifications the way they should be.

We have been a front runner in creating the teams with the proper technologies and expertise to address these issues for over 4 years now. Unfortunately the owners and engineers are only beginning to see the value of what we call the Master Integrator.

Automation and Protocols - All Comments

re: Bacnet Installation Dilemma

re: Bacnet Installation Dilemma