The SCADA platform you pick today will run your plant for 15-20 years — outlasting the PLCs beneath it and the MES above it. Four platforms (Ignition, AVEVA, FactoryTalk, WinCC) cover ~80% of industrial SCADA deployments in 2026, and each one is the right choice for a specific situation — and the wrong choice for everything else. Ignition wins on licensing economics for multi-vendor plants. AVEVA dominates process industries with PI Historian + ISA-88 batch. FactoryTalk locks in seamless Allen-Bradley integration. WinCC owns the Siemens S7 ecosystem. Pick wrong and you'll spend the next two decades paying license premiums, fighting integration tax, or chasing platform migrations. This guide breaks down the architecture patterns, the platform comparison, the 8 weighted selection criteria, and the mistakes that lock greenfield projects in. Book a SCADA selection assessment for your project.
Why SCADA Selection Locks You In For 15-20 Years
Five compounding reasons make SCADA the highest-stakes platform decision in greenfield manufacturing. Most teams underestimate how durable these decisions are — and discover the lock-in only when the migration estimate arrives a decade later.
01
Tag Databases Don't Migrate Cleanly
Custom scripts, complex alarm hierarchies, recipe systems, and historian mappings are platform-specific. Migration tools handle 60-70% — the remaining 30% is full re-engineering.
02
Operator Training Compounds
5+ years of muscle memory on screens, navigation patterns, and alarm response. Switching platforms means retraining hundreds of operators across multiple shifts.
03
Integrator Ecosystem Lock-In
Your integrator built expertise on a platform. Their team's certifications, code libraries, and project templates are platform-specific. Switching forces vendor change too.
04
Compliance Documentation Re-Validation
FDA-validated pharma SCADA, IEC 62443-compliant security configurations, and audit trail documentation cost months to recreate on a new platform.
05
Licensing Sunk Cost
Per-tag or per-client licenses purchased over 10+ years create a sunk-cost trap. CFOs reject migration even when total TCO favors switching.
The 4 SCADA Architecture Patterns
Architecture choice is more durable than platform choice. The architecture determines how the platform deploys, scales, and integrates — and which platforms are even eligible for your project. Four patterns dominate 2026 greenfield SCADA design.
Pattern 1
Traditional Client-Server
Fat-client workstations connect to a central SCADA server. Reliable but limited mobile/web access. Phasing out for new greenfield projects — but still common in legacy retrofits.
Best for
Legacy retrofits · fixed-location HMI · validated process plants
Pattern 2
Web-Based / Browser-Native
HTML5 designer and clients run in any modern browser. Cross-platform (Windows, Linux, macOS), mobile-friendly, easier deployment. Ignition Perspective and FactoryTalk Optix lead this pattern.
Best for
Greenfield mid-market · multi-site · mobile operator access
Pattern 3
Hybrid Edge + Central
Edge SCADA at each plant for real-time control + central SCADA for aggregation, KPIs, and corporate visibility. Resilient to network failures, scales to multi-site networks. MQTT/Sparkplug B is the glue.
Best for
Multi-site networks · UNS architecture · enterprise rollouts
Pattern 4
Cloud-Native SCADA
No on-premise server. Cellular edge gateway connects to cloud SCADA (Inductive Cloud, AVEVA Connect, FactoryTalk Hub). Production-ready in 2026 for distributed assets. Site live in hours instead of weeks.
Best for
Distributed remote assets · oil/gas pads · water utilities
Pick a SCADA Platform That Survives the Next Two Decades
iFactory's automation advisory team runs vendor-neutral SCADA platform evaluations — architecture mapping, TCO modeling, MQTT/UNS-readiness assessment, IEC 62443 security review, and weighted scoring matrices. Built for the 20-year horizon, not the cheapest bid.
Platform Comparison · Top 4 Side-by-Side
This vendor-neutral comparison summarizes the trade-offs across seven critical dimensions. No platform wins on every dimension — and that's the point. Match the platform to your specific situation, not to industry buzz.
Dimension
Ignition
AVEVA
FactoryTalk
WinCC
Licensing Model
Unlimited tags · per-server
Per-tag · enterprise
Per-client · token (Optix)
Per-tag · enterprise
PLC Vendor Fit
Universal · OPC UA
Universal · OPC UA
Allen-Bradley native
Siemens S7 native
MQTT / Sparkplug B
Native (built-in)
Available · add-on
Native (Optix) · add-on (SE)
Available · add-on
Web-Native
Yes · Perspective
Partial · client
Yes · Optix
Yes · Unified
Cross-Platform OS
Win · Linux · macOS
Windows only
Win · Linux (Optix)
Windows · limited Linux
Best Fit
Multi-vendor greenfield
Process industries · scale
Allen-Bradley shops
Siemens shops
Need a deeper comparison tailored to your industry and PLC stack? Book a platform shortlist session with our advisory team.
8 Weighted Selection Criteria
Without a weighted scoring matrix, vendor demos all look great. With one, the differences become quantitative. Adjust the weights to your project — but cover all eight criteria. The 8 dimensions below capture 90%+ of the lifetime cost and risk variance between platforms.
Selection Criterion
Weight
What to Evaluate
Licensing Model & TCO
20%
10-year TCO across tag growth, client expansion, modules, support contracts. Per-tag vs unlimited matters at scale.
PLC Stack Alignment
15%
Native PLC support reduces integration tax. Multi-vendor environments favor universal OPC UA platforms.
MQTT / Sparkplug B Native
15%
UNS architecture is now standard. Native Sparkplug B beats add-on adapters. Default spec on most 2026 tenders.
Cybersecurity (IEC 62443)
15%
Native RBAC · audit logs · encryption · certificate management · IEC 62443 SL-2+ alignment
Web & Mobile Access
10%
Browser-native HMI · mobile apps · responsive design · operator + maintenance + executive views
Scalability Roadmap
10%
Tag count ceiling · multi-site architecture · cloud connectivity · template-based engineering
Integrator Ecosystem
10%
Local certified integrators · talent pool · community support · documentation depth
Vendor Stability
5%
Financial stability · roadmap clarity · acquisition risk · 15-20 year continuity probability
Want a custom-weighted scoring matrix for your project? Connect with our SCADA advisors for a tailored framework.
5 Selection Mistakes That Lock You In For 20 Years
The same five mistakes appear in nearly every SCADA project that locks teams into platforms they later regret. Each is preventable at selection stage — and each costs millions to undo later.
01
Picking by Demo, Not by TCO
Vendor demos all look great. The 10-year TCO model — licensing, tag growth, client expansion, support — reveals 30-100% cost differences that no demo can mask.
02
Letting the Integrator Pick the Platform
Integrators recommend what they're certified on. Their preference may or may not fit your situation. Owner-led platform selection comes first; integrator selection second.
03
Ignoring MQTT / Sparkplug B Readiness
UNS and Sparkplug B are now default 2026 tender requirements. Picking a platform without native MQTT means add-on integration cost — and limits future architecture options.
04
Underestimating Licensing Growth
Per-tag and per-client licensing compounds. A 5,000-tag system grows to 20,000 in 5 years. Unlimited licensing platforms look expensive Day 1 — and pay back by Year 3 at scale.
05
Skipping the Cybersecurity Review
IEC 62443 alignment varies dramatically across platforms. RBAC depth, audit logs, certificate management, and patch cadence determine whether you'll pass an OT security audit in 2027.
Avoid these mistakes with a structured selection process. Book a SCADA evaluation workshop with our advisors.
Expert Perspective
The right SCADA platform isn't the best platform — it's the platform that fits your situation. End-to-end Rockwell shop? FactoryTalk. Pure Siemens greenfield? WinCC. Process industry at scale with PI Historian dependency? AVEVA. Multi-vendor plant with UNS architecture? Ignition. The selection mistakes I see are almost always one of two patterns: a CIO who picked the platform their last company used regardless of fit, or an integrator who picked the platform they're certified on regardless of TCO. Owner-led selection, weighted scoring matrix, and a 10-year TCO model fix both problems. The platform is a 20-year decision — spend the eight weeks to run it properly.
— Greenfield SCADA Selection Best Practice
15-20 yr
SCADA platform operational lifecycle
8 wks
Typical selection process duration
30-100%
10-year TCO variance across platforms
~80%
Greenfield share covered by top 4 platforms
Bottom Line · Pick the Platform That Fits, Not the Loudest Demo
SCADA selection is a 20-year commitment with 30-100% TCO variance, 6-figure migration costs, and operational disruption nobody wants twice. The right answer isn't the best platform on every dimension — it's the platform that aligns with your PLC stack, your scale, your architecture (UNS-native or not), your industry regulation, and your team's capability. Run the weighted scoring matrix. Build the 10-year TCO model. Test MQTT/Sparkplug readiness. Validate IEC 62443 alignment. Then pick the platform your future self will thank you for — not the one your current integrator is most comfortable with. The eight weeks of selection rigor pays for itself many times over across the next two decades.
Make the SCADA Decision That Pays Off for 20 Years
iFactory's advisory team runs vendor-neutral SCADA platform selection — architecture analysis, TCO modeling, MQTT/UNS readiness review, IEC 62443 alignment, integrator ecosystem mapping. Built for the 20-year horizon, not the cheapest bid sheet.
Frequently Asked Questions
What are the top SCADA platforms for greenfield manufacturing in 2026?
Four platforms cover ~80% of industrial SCADA deployments: Ignition (multi-vendor plants, UNS architecture, unlimited tag licensing), AVEVA System Platform (process industries at scale, PI Historian, ISA-88 batch), Rockwell FactoryTalk (Allen-Bradley plants, View SE + Optix), and Siemens WinCC (Siemens S7-1500 greenfield, native TIA Portal integration).
Which SCADA platform is best for a greenfield factory?
Depends on your situation. Multi-vendor PLC environment + UNS → Ignition. Process industry + scale + PI Historian → AVEVA. End-to-end Allen-Bradley shop → FactoryTalk. Greenfield Siemens S7-1500 → WinCC. No platform is "best" universally — fit matters more than feature parity. Run a weighted scoring matrix tied to your specific PLC stack, scale, and architecture.
What is MQTT / Sparkplug B and why does it matter for SCADA selection?
MQTT is a lightweight messaging protocol; Sparkplug B is an MQTT specification for industrial data with built-in semantics. Together they enable the Unified Namespace (UNS) architecture — a single data backbone connecting all OT systems. Now the default spec on most 2026 SCADA tenders. Platforms without native Sparkplug B support are losing pitches. Prioritize native support over add-on adapters.
What are the most important SCADA selection criteria?
Eight weighted dimensions: Licensing & 10-year TCO (20%), PLC stack alignment (15%), MQTT/Sparkplug B native (15%), Cybersecurity IEC 62443 (15%), Web/mobile access (10%), Scalability roadmap (10%), Integrator ecosystem (10%), Vendor stability (5%). Adjust weights to your project — but cover all eight. They capture 90%+ of lifetime cost and risk variance.
How long does a SCADA platform selection process take?
~8 weeks for a $5M+ SCADA scope: requirements definition, vendor RFI to 5-7 platforms, weighted scoring evaluation, reference customer site visits, hands-on POC with top 2, TCO modeling, and final selection. SCADA is a
15-20 year decision with 30-100% TCO variance across platforms — the eight weeks pays for itself many times over.
Book a selection process review to scope yours.
