Ignition as a Building Management System?

Dear Community,

I’m new in the world of Inductive Automation and its ecosystem, and even more in the forum, so please excuse me in advance if I lack any precision.

My background is mainly in industrial automation, traditional SCADA, PLC, OT Networks, etc; however, every now and then a Building Managemen System comes alone and I wonder if feasible to create an application solution using Ignition for this purpose.

So far I know Ignition has drivers for BACnet and Modbus, but I’ll like to have feedback from someone with experience doing this kind of project o applications that can share what are the major pain points of entering this challenge. So, basically, my inquiry here is, Is Ignition a good platform to build a BMS? and what are the major recommendations or advice.

Thank you,


While I don’t have experience in using building management systems myself, I know that most - if not all - of our own campus is managed using Ignition. I’ll see if I can track down who set it up so that they can reach out here.

1 Like

Hi @cperez, unfortunately I don’t have the experience (I come from the same background as yourself). I mainly want to express a similar interest. I have floated the idea of a BMS within the business (although it hasn’t got traction yet) as we have had a major office overhaul due to the pandemic.

I think we would be mainly looking down the IIoT route (MQTT, RESTful API’s etc.). My biggest concern is security (mainly due to this world being new to me and not configuring something correctly).

If I do get traction I will let you know of any pitfalls we come across. Let me know if you come across any further information, as I would be interested.

1 Like

Absolutely. 8.0/8.1 comes with a BacNET driver.

7.9 you can use the likes of KepWare as a BacNET OPC UA Server, or use a hardware black box to change BacNET IP to Modbus TCP.


Hi @cperez. I’m not a professional BMS engineer, so I can’t answer all of your questions. But I can relay my observation while managing our own system at headquarters in Folsom.

This really is a question of “What tool do you want to use?”. Whether to use BMS software or Ignition, or both, depends on your preferences and skill set.

What I have observed is that dedicated BMS systems require a great deal of training in the way they do things… but once you’re trained, its fairly easy to use, and everything you should need is within their “walled garden”. As far as the control logic, they usually have a bunch of premade components (purpose built for Heating and Air, Lighting, etc.) you can lay out and just connect the dots. Outside of re-arranging their pre-built components, you have no real room for custom programming. BMS systems usually have a dedicated controller, with “remote I/O” devices, which removes the need for a separate PLC (again, this is my limited knowledge). You can’t build a custom integration of your own without leaning on the original developers of the BMS software.

Lets take an example… say you had a complete BMS, and then needed to pull data from PLCs elsewhere in your plant that don’t talk BACnet… Lets say every time Line 1 is cutting hardwood, you need the BMS to reduce airflow in that area… You would have to figure out some other way to do it, external to the BMS software (but hey, that’s the job of Integrators, is it not?).

Okay so, as you know, Ignition is a platform that can tie into any source of data and show them up as tags. Now that we have recently added the BACnet driver, Ignition can be a BMS. But you’re not going to have all of the pre-made software components for controlling Variable Air Valves, Supply and Exhaust Fan PID loops, Compressors, Condensers, etc… So you will be building all of that PLC logic yourself (which you may prefer being in full control of, given your background). Additionally, the equipment associated with a BMS may require traditional BMS software to use them (such as the equipment that would actuate a VAV directly, which talks ARCnet across two wires back to a central BMS Controller). Such a BMS controller would then have an ethernet port you could connect to with Ignition’s BACnet driver.

And this is the case we are in with our headquarters. We have VAVs throughout the building, which it was easier for us to use a BMS just to control those… and have a PLC controlling the Air Handling Units on the roof (since we come from an Integrator background with decades of PLC experience), with Ignition tying the two together. Ignition passes tag values back and forth (VAVs need to know what temp the Supply air is, and the AHUs need to know the combined airflow of all VAVs to determine if its safe to turn on Compressors). To be honest, our VAV controller can be a complete BMS on its own (that company could have controlled the whole thing). But I ask you A, what’s the fun in that? and B, would you want to be at the mercy of their programmers? Or would you want all the tools in your belt?

Our decision to integrate everything with Ignition was well founded when we were able to:

  • Alert us if the VAV controller crashes (yeah that happens sometimes)
  • Alert us immediately if there are power outages at the office, before UPS runs out (fun trick).
  • With historical charts and alarms, we were able to pinpoint the cause of our heater units failing!
  • Handle issues with building pressure (exterior doors were blowing open or pulled inward, making it hard for people to come in and out) due to the spec’d exhaust fan not able to run slow enough, or fast enough, to recover from the occasional 20mph winds. We were able to put custom logic to handle this, which wouldn’t have been possible for us to implement in-house with a BMS.
  • Tracking maintenance of equipment for faster debug when they fault.
  • Easily lock out equipment that regularly fails, until it can be repaired.
  • One of our AHUs switches between heating and cooling… having so many data points historically logged allowed us to increase occupant comfort by doing optimizations to the decision to flip modes.
  • We have the ability to pull in any source of data we want, such as mounting our own Weather Station on the roof to determine the exact UV levels to determine if the sun is baking the exterior offices, to get ahead of the cooling curve. The possibilities are endless.

There is no doubt it took us longer to implement our system than it would have taken a traditional BMS solution. But personally, the flexibility we achieved beyond what a BMS can do, is INVALUABLE.

So the choice is yours, depending on your skill set and preferences.

I hope this insight helps you and others.


Wow @mhechtman! I never expected such an elaborated response. People like you give this community its reputation of been very supportive. Thank you for taking the time to explain your experience on the topic, it been very helpful, just what I need to know.

In another hand, I believe is possible to start building an open library for these solutions that can later be accessed from the Exchange site. I’m not very familiar with the platform Github, but I have seen other initiatives been develop in there for similar needs. This could be a good option.

Thanks again for your help, time and effort.


I totally agree with @mhechtman that with the recent introduction of BACnet driver Ignition is now more BMS friendly. However apart from the HVAC control that typically a BMS handles, BMS systems are usually highly integrated from factory with other systems such as access control and video surveillance. If your project is expected to integrate all those features in one platform, you will have to consider the additional labour as well as the required interfaces to do so. I don’t want to discourage anyone, after all I am already involved in the process of providing a BMS solution to one of our customers with Ignition. I am just feeling I have to avoid a lot of hidden mines!


Hi, here in France, Ignition is widely used in BMS or alike systems. We use it in hospital, town council, offices, swimming pool etc. and french integrators leverages all the openness and power of Ignition like web services to interact with room reservation management, energy tariffs or weather to control the installations; MQTT and SpB is also use to modernize legacy installation give the opportunity to all other business application to subscribe to rich and already structured and contextualized data.
Not to mention that you can use module development to enrich the whole thing.
Take a look at not not exactly a BMS but you’ll find all the functionalities you want: Bouygues Energies & Services on LinkedIn: Mise en service du Tramway T9 entre Paris et Orly CCTV, access control, low voltage cc, VoIP (yes, Ignition is an Asterisk IPBX and receive and make call to dockside call terminal), lightning and signalization management, etc.

Another example Gilles NGUYEN - AXONE-IO on LinkedIn: L'optimisation énergétique commence par le pilotage de nos installations

What bothers me is when the question “can Ignition do this or that” is asked. In reality, it’s a platform that can do everything. What’s the difference between a nuclear power plant, an office building, a tramway, a highway, a sewage treatment plant, an assembly plant or a continuous casting? We’re talking about assets. It’s just a matter of changing the prism of our habits.
Dream , Do It