Ignition, FactoryTalk, and AVEVA: compare the fit before the license.
Your installed equipment, operators, support arrangements, and required functions matter more than a brand preference. Compare named products and editions, not entire vendor portfolios.
| Decision | Ignition | FactoryTalk | AVEVA / existing Wonderware |
|---|---|---|---|
| Installed fit | Confirm drivers and required application modules. | Identify the installed product and Rockwell integration needs. | Identify InTouch, System Platform, or other installed products. |
| Licensing | Specify modules, edition, redundancy, and support. | Obtain a quote for the exact product, capacity, and client model. | Obtain a quote for the exact product, capacity, and subscription terms. |
| Migration effort | Scope screens, alarms, history, and interfaces to rebuild. | Assess whether the existing application can be upgraded. | Assess supported upgrade paths for the existing application. |
| Handover | Agree editable projects, licenses, documentation, and training. | Agree source files, software access, and maintenance support. | Agree source files, software access, and maintenance support. |
Name the actual products
FactoryTalk and AVEVA are product families. An installed FactoryTalk View application, an InTouch system, and an AVEVA System Platform deployment have different architectures and migration needs. Record the product, version, licenses, dependencies, and support status you actually own.
Reasons to keep an existing platform
A supported application with reliable backups, trained operators, available engineering support, and a clear expansion path may be worth improving. A platform change brings screen redevelopment, testing, training, and historical-data work even when the replacement license looks attractive.
Reasons to evaluate Ignition
Consider Ignition when browser-based applications, mixed equipment, modular functionality, and broader data integration fit your requirements. Verify the required modules, third-party components, redundancy, support, and deployment architecture in a current proposal.
Test the difficult parts before committing
Build a small proof of concept using representative controllers, screens, alarms, historical queries, and access requirements. Test a connection failure and a recovery. Include the operators who will use the screens, then compare the complete implementation and support cost.
Let’s define your first integration project.
Tell us which controllers and software you use, what you want to improve, and your production constraints. Start with a 15-minute project discussion.