Ignition SCADA vs Wonderware vs FactoryTalk

Three Platforms, Three Philosophies

Ignition, Wonderware (AVEVA), and FactoryTalk (Rockwell) represent three fundamentally different approaches to SCADA platform design. Ignition disrupted the market with unlimited licensing and open architecture. Wonderware built an enterprise-grade platform around object-oriented templates and a powerful historian. FactoryTalk delivers the tightest PLC integration available through its native Rockwell ecosystem. Understanding these philosophical differences is essential for selecting the right platform for your application.

Licensing and Cost Structure

Ignition

Ignition uses server-based licensing with unlimited tags, clients, and connections per server. Base platform cost ranges from $3,000-5,000 per module, with typical full installations costing $20,000-40,000 for software. No annual maintenance fees are required, though an optional support subscription provides updates and vendor support. Ignition Edge licenses for remote sites cost $1,500-3,000 each. This model makes Ignition the most cost-effective platform at scale.

Wonderware (AVEVA)

Wonderware licenses by tag count and client count, with additional fees for historian tags, alarm notification recipients, and web clients. A typical mid-size system (10,000 tags, 5 clients, historian) can cost $100,000-200,000 in software licensing alone. AVEVA has transitioned to a subscription model (AVEVA Flex), which provides access to the full software portfolio but requires ongoing annual payments. This can be advantageous for short-term projects but increases long-term costs.

FactoryTalk

FactoryTalk uses a per-display, per-server licensing model with separate SKUs for View SE servers, View SE clients, Historian, VantagePoint (reporting), and Alarms and Events. Licensing complexity is a frequent complaint, with multiple activation keys required for a single system. Costs are competitive with Wonderware for mid-size systems but escalate quickly for large distributed architectures.

Architecture and Scalability

Ignition Architecture

Ignition runs as a Java application on a single gateway server. Multiple gateways can be connected via the Gateway Area Network (GAN) for distributed architectures. The Ignition Edge platform provides local HMI and store-and-forward historian at remote sites, synchronizing data to the central gateway when communication is available. Perspective module delivers HTML5 clients that run on any device with a web browser.

Wonderware Architecture

System Platform uses the ArchestrA framework with a Galaxy Repository that stores all configuration objects. Application servers host runtime instances of ArchestrA objects, and InTouch provides the HMI client experience. The architecture supports multi-server deployments with hundreds of thousands of tags. AVEVA Historian uses a proprietary time-series database optimized for industrial data with excellent compression ratios.

FactoryTalk Architecture

FactoryTalk View SE uses a distributed architecture with HMI servers, data servers, and a FactoryTalk Directory for service discovery. The platform is designed around a Rockwell controller-centric model where tags are defined in the PLC and referenced directly in the SCADA application. FactoryTalk Optix is Rockwell's next-generation platform using .NET and web technologies, but View SE remains the mature and widely deployed option.

Development Environment and Tools

The development experience differs significantly across platforms:

• Ignition: Browser-based Designer with drag-and-drop components, Python (Jython) scripting, and SQL query bindings. Templates and UDTs (User Defined Types) enable reuse. Development is fast and accessible to engineers with moderate programming skills.
• Wonderware: IDE-based development using the ArchestrA IDE and InTouch WindowMaker. Object-oriented template model is powerful for large standardized systems but has a steep learning curve. QuickScript is the proprietary scripting language.
• FactoryTalk: View Studio for display development, with VBA scripting for custom logic. Tag database integrates directly with Studio 5000 for Allen-Bradley controllers, enabling tag browse and import without manual configuration.

Protocol Support and Connectivity

Protocol support is critical for energy applications with diverse field devices:

• Ignition: Built-in drivers for Modbus TCP/RTU, Allen-Bradley (EtherNet/IP, DF1), Siemens S7, OPC-UA, and MQTT/Sparkplug B. Additional protocols available through third-party OPC servers. Community-developed modules extend connectivity further.
• Wonderware: Uses DA Servers (now Communication Drivers) for device connectivity. Extensive library covering most major protocols. OPC-UA and OPC-DA client/server support included.
• FactoryTalk: Best-in-class Allen-Bradley connectivity. Third-party protocols require KEPServerEX or similar OPC servers, adding cost and complexity. OPC-UA support has improved in recent versions.

Which Platform Fits Your Application?

Choose Ignition When

You are building a new system or replacing a legacy platform and want the lowest total cost of ownership. Ignition excels for large distributed systems with many remote sites, organizations wanting to avoid vendor lock-in, projects requiring mobile/web access via Perspective, and companies using MQTT/Sparkplug B for efficient IIoT data transport.

Choose Wonderware When

You have an existing Wonderware investment with trained staff and established templates. Wonderware is strongest for large enterprise deployments requiring standardization across multiple plants, applications needing deep MES integration, and organizations with existing AVEVA Historian infrastructure storing years of historical data.

Choose FactoryTalk When

Your control system is primarily Allen-Bradley and you want the tightest PLC integration available. FactoryTalk fits best for facilities with ControlLogix or CompactLogix controllers, environments already using Studio 5000 for PLC programming, and applications where controller-based alarming is preferred over server-based alarming.

NFM Consulting has implemented all three platforms across Texas energy operations. We provide vendor-neutral assessments to help you select the platform that best fits your technical requirements, existing infrastructure, and budget. Our team includes certified developers for each platform.