A lot of people get annoyed with having a single set of servers at the data centers for all the production sites. The problem with this is that if a site loses communication to the central server, it's going to be blank and no longer it can collect the MES data. So we should have servers at each local production sites.
Now we have a local database for each production site. How can we get the MES data in the local data center reflect in the global data center also? That's where a setting in the MES modules comes into play. There is a way to perform all the data analysis locally as well as remote. All three production sites storing the information locally, push the data up to the data center. If anyone of them lose connection to the data center then we can use the cache it had on the local database to have a backup.
How you can do redundancy on Ignition servers?
Wherever you have single Ignition server, add one and simply make them redundant. It is very easy to set them up. You just have to enable it and turn on the setting, Ignition will synchronize the projects for you. The Ignition platform provides redundancy, which means that all the MES modules automatically get redundancy built into them.
All the configurations and the screens for each clients are going to be in a single server. So within this site you can open up any number of runtimes inorder to view the MES data, to start production run and to collect samples. You can also open up a client at home through VPN connection or do a connection to the local LAN there. It's a very simple architecture and its common for companies who have independent sites where they wanted to work on themselves.