![inductive automation ignition date today inductive automation ignition date today](https://www.icontrols.com.au/wp-content/uploads/2021/02/Badge-Distributor@2x.png)
- INDUCTIVE AUTOMATION IGNITION DATE TODAY INSTALL
- INDUCTIVE AUTOMATION IGNITION DATE TODAY DRIVER
- INDUCTIVE AUTOMATION IGNITION DATE TODAY SOFTWARE
Because the back-end gateways are only used for communicating with various devices, they don't need any visualization system modules like Vision or Perspective but simply need the device driver modules. It should also be noted that as you scale out even more, the cost doesn't increase dramatically. This has the benefit of spreading the communications load out to multiple points in the network instead of having everything communicate through one location. The tag and I/O gateways communicate solely with the devices and can then push this data to the front-end gateway which supplies it to the clients. You'll notice that as the number of devices in the facility grew, we split the Ignition system into a front-end gateway and multiple back-end or tag and I/O gateways. This is what we call a scaled-out architecture where the load on the Ignition system has been scaled out over multiple Ignition gateways instead of pushing all the data through one central system. While Ignition may be unlimited, we typically find that users run into a limitation of the hardware as their facility grows. The first is a growth in density of data and operations at the facility. With growing systems, we typically see two types of growth.
![inductive automation ignition date today inductive automation ignition date today](https://inductiveautomation.com/static/images/whats_new/8.1/a-new-perspective-for-the-plant-floor.png)
As your Ignition use grows, you may find that you need to adopt a new architecture to fit your facility's growing needs. Of course, there are variations on this such as adding redundancy or placing the Ignition server and/or database server within a cloud-based environment.
INDUCTIVE AUTOMATION IGNITION DATE TODAY INSTALL
This simple architecture is where most users start when they first install Ignition at their facility. It can then relay this data to any number of clients running throughout the facility. Typically, you would have an Ignition server sitting somewhere within the facility communicating with one or more databases and also communicating with one or more PLCs. To start, one of the simplest architectures that we can think of is what we call the standard architecture, which you can see in the image here. These examples can be thought of more as a guide to help you plan out what you need to do within your facility. What's important to understand is that there are not correct architectures and incorrect architectures, and you certainly don't have to follow any of these examples we have here. The architecture gives us an idea of where Ignition sits within a facility's infrastructure as well as how it communicates with various things throughout the plant such as PLCs, databases, and even the clients. How the Ignition Gateway or gateways are set up in a facility is what we like to call the Ignition system architecture. Companies can even have multiple facilities each with their own unique needs for the software.
INDUCTIVE AUTOMATION IGNITION DATE TODAY SOFTWARE
Every company can use the Ignition software in unique ways depending on the needs of their facility.