Migrating From Wonderware To Ignition Part 1
A few short years ago, Wonderware was the hot software on the market. Now, on a nearly weekly basis, Corso is getting calls from facilties currently using Wonderware (WW) looking at migrating to Ignition.
Instead of issuing a blanket statement of Ignition is better than WW. Alex is going to help take us on a deep dive of the differences.
P.S. Wonderware friends, please don’t hate us. Everyone really is asking these questions…
Ease of use and deployment
Similar architectures here, server/client based systems all follow a similar deployment structure.
Wonderware you need to be aware of clients and development licenses. Ignition, if you have a developer open on your computer at home and also at work, that’s not going to be an issue.
What do you mean we have work/life balance issues?
3rd party vendor options and connectivity
Very similar functionality here, can either use built-in communication drivers in either system, OPC-DA and OPC-UA servers, or something like Kepware if there are not built-in drivers.
Much of this will depend on what you currently have or are looking for in the future. Please feel free to contact us and we’ll happily walk you through what this could mean for your system.
Historian capture, Store and Forward, out of the box tools
What do you think?
Ready to make your decision? Or want to have a more in-depth conversation about this? Please feel free to reach out and we’ll have a more in-depth conversation.