BACnet: Pain Points

5 Posts
3 Users
0 Likes
45 Views
(@admin_doc72)
Posts: 493
Member Admin
Topic starter
 

Dear all,

In my role as a PcVue representative in the Workgroup Technical (WG-T) of the BACnet Interest Group Europe (BIG-EU) I need your help.

The BIG-EU aims to become more attractive to integrators in the future and to improve its image amongst integrators. Therefor members of the WG-T are encouraged to get in touch with integrators and internal colleagues from the service department. The aim is to get feedback about the biggest hindrances in BACnet projects (and potential biases against working with BACnet). The feedback shall be used to create methods for providing guidance to BACnet project engineers.

Can you tell from your experience in working with PcVue customers, what are the biggest pain points integrators have with this protocol?

Thanks very much in advance for your contribution! 🙂

 
Posted : 18/03/2021 10:18 pm
BO
 BO
(@b-olombelarcinfo-com)
Posts: 196
Reputable Member
 

Hello,

For me the most painful point is the networking architecture management.
When a BACnet client needs to get devices situated in different subnet or when the network is a mix between public and private subnet, it is very difficult to set the good configuration.
You are lucky if your bacnet client is able to discover a bacnet network through public ip adress, through a gsm or vpn.
And also, even it is very convenient, broadcast message nowadays is a security leak regarding IT requirements, it is more and more filtered by firewalls.

hope it is clear, I tried to sum-up my point of view.

 
Posted : 18/03/2021 11:10 pm
(@m-nauarcinfo-com)
Posts: 49
Trusted Member
 

Hi,
Like Brice said, the main painfull feature is the Broadcasting!!
The second,linked to the first, is BBMD configuration to generate Unicast when you have devices on differents subnets. Form some projects to avoid BBMD configuration inside a Bacnet PLC, you need a Bacnet IP BBMD Router.
Last point : Proprietary items.
Manu

 
Posted : 24/03/2021 9:00 pm
(@admin_doc72)
Posts: 493
Member Admin
Topic starter
 

Brice, Manu, thanks very much to both of you! That is already quite precious, I appreciate!

One more thing: is there anything that we can say about issues on project management level? Like the ease of collaboration with project stakeholders in BACnet projects or such...?

Any other shortcomings for integrators from the fields listed below?

  • Interoperability?
  • Management of data point lists?
  • Tooling?
  • Scalability?
  • Performance?
  • Availability and widespread knowledge of the standard specification?
  • Entry threshold / cost efficiency?
  • Other?
 
Posted : 25/03/2021 3:05 pm
(@admin_doc72)
Posts: 493
Member Admin
Topic starter
 

Hi Armin

For integrators performance is I think a problem. They don't know how many servers they need in case of "big" applications.

Choice between pooling or COV is also a shortcoming mainly when the Scada integrator is not the same than APi Integrator.....

Nico

 
Posted : 31/03/2021 10:13 pm