AVEVA Pricing in 2026: What Does AVEVA Actually Cost for Manufacturing?
AVEVA (formerly Wonderware, now part of Schneider Electric) has been a dominant force in industrial software for over 30 years. Their products — InTouch HMI, System Platform, Historian, MES, and the newer AVEVA PI System (from the OSIsoft acquisition) — run in thousands of manufacturing plants worldwide. If you've worked in manufacturing for any length of time, you've probably touched an AVEVA product.
But AVEVA's pricing has always been opaque, and the landscape has shifted dramatically since Schneider Electric completed its full acquisition in 2023. Here's what AVEVA actually costs in 2026, what's changed, and whether it still makes sense for your manufacturing operation.
AVEVA's Product Portfolio (and What You're Paying For)
AVEVA sells a broad portfolio of industrial software. Here are the products most relevant to manufacturing:
AVEVA InTouch HMI / Edge
The successor to Wonderware InTouch — SCADA/HMI software for machine and process visualization.
AVEVA System Platform
The engineering and runtime environment for building SCADA applications. System Platform sits underneath InTouch and manages communications, data model, and deployment.
AVEVA Historian (formerly Wonderware Historian)
Time-series database for storing industrial process data. Competes directly with OSIsoft PI (which AVEVA also now owns).
AVEVA PI System (formerly OSIsoft PI)
Enterprise data infrastructure for collecting, storing, and analyzing industrial sensor data. PI System is used by the largest manufacturers and utilities in the world, with over 2 billion sensor streams globally.
AVEVA MES (formerly Wonderware MES)
Manufacturing Execution System for production tracking, quality management, and operational performance management.
AVEVA Unified Operations Center
Cloud-based operations management for multi-site visibility and analytics.
AVEVA Connect
Cloud platform for hosting AVEVA applications and providing enterprise-wide data access.
AVEVA Pricing: What We Know
AVEVA transitioned from perpetual licenses to a subscription model (AVEVA Flex) starting in 2020. Here's the pricing landscape in 2026:
AVEVA Flex Subscription Model
AVEVA Flex uses a token-based subscription system:
- You purchase a pool of Flex tokens (annual subscription)
- Each AVEVA product consumes a specific number of tokens
- You can reallocate tokens between products as needs change
- Tokens are priced per-year with volume discounts
Token pricing (estimated):
| Token Volume | Estimated Price Per Token (Annual) |
|---|---|
| 100 tokens | $500 – $800 |
| 500 tokens | $400 – $600 |
| 1,000+ tokens | $300 – $500 |
| 5,000+ tokens | $250 – $400 |
Product token consumption (estimated):
| AVEVA Product | Estimated Tokens Required |
|---|---|
| InTouch HMI (per runtime client) | 10 – 30 |
| System Platform (per node) | 20 – 50 |
| Historian Server (per server) | 50 – 100 |
| PI System (per server) | 100 – 300 |
| MES (per production line) | 50 – 150 |
| Unified Operations Center | 100 – 300 |
| AVEVA Connect (cloud) | Varies |
Typical Annual Costs by Plant Size
Based on publicly available information and industry benchmarking:
| Plant Size | Typical AVEVA Stack | Estimated Annual Cost |
|---|---|---|
| Small (1 line, 10 machines) | InTouch + Historian | $30,000 – $80,000 |
| Medium (3-5 lines, 50 machines) | System Platform + Historian + MES | $100,000 – $300,000 |
| Large (10+ lines, 200+ machines) | Full stack + PI System | $300,000 – $1,000,000 |
| Enterprise (multi-site) | Everything + AVEVA Connect | $500,000 – $3,000,000+ |
Legacy Perpetual License Costs
Many manufacturers still run perpetual licenses purchased before the Flex transition:
| Product | Perpetual License (One-Time) | Annual Support (20% of license) |
|---|---|---|
| InTouch HMI (Development) | $8,000 – $25,000 | $1,600 – $5,000 |
| InTouch HMI (Runtime) | $2,000 – $8,000 | $400 – $1,600 |
| System Platform (per node) | $10,000 – $40,000 | $2,000 – $8,000 |
| Historian (64 tags) | $5,000 – $15,000 | $1,000 – $3,000 |
| Historian (unlimited tags) | $50,000 – $150,000 | $10,000 – $30,000 |
| MES (per workstation) | $15,000 – $50,000 | $3,000 – $10,000 |
Important: AVEVA has been aggressively pushing customers from perpetual to subscription. New perpetual licenses are increasingly difficult to purchase, and support costs for legacy licenses have been rising to incentivize the transition.
Hidden Costs and Pricing Traps
1. Tag-Based Historian Pricing
AVEVA Historian is priced by the number of tags (data points) it stores. This creates a painful cost curve:
- 500 tags: $10,000 – $20,000 (covers a small operation)
- 5,000 tags: $30,000 – $60,000 (typical medium plant)
- 50,000 tags: $80,000 – $200,000 (large plant)
- Unlimited: $150,000 – $400,000
The problem: as you instrument more equipment and want to monitor more parameters, your historian costs escalate. This creates a perverse incentive to limit monitoring — exactly the opposite of what IIoT is designed to do.
2. Infrastructure Costs
AVEVA software runs on Windows servers. Each product typically requires its own server (or at minimum its own VM):
- Historian server
- System Platform server (Galaxy Repository)
- Application servers (InTouch runtime)
- PI System servers (if using PI)
- SQL Server licenses (required for Historian, MES)
Typical infrastructure cost: $30,000 – $100,000 in server hardware plus $10,000 – $50,000 in Windows Server and SQL Server licensing. This infrastructure requires IT management, patching, backups, and eventual replacement (every 5-7 years).
3. Integration and Development
AVEVA is a platform, not a turnkey solution. You need to:
- Design SCADA graphics — InTouch graphics development ($50 – $150/hour for AVEVA-certified integrators)
- Configure Historian — tag setup, data collection configuration, storage optimization
- Develop reports — AVEVA reporting requires development or third-party tools
- Build dashboards — modern visualization requires additional development or AVEVA's analytics tools
Typical integration cost: $50,000 – $500,000 depending on plant complexity.
4. Training and Certification
AVEVA training courses cost $2,000 – $5,000 per person per course. A competent AVEVA administrator typically needs 3-5 courses:
- InTouch HMI Development
- System Platform Administration
- Historian Administration
- Reporting/Analytics
- MES Configuration (if applicable)
Training cost per administrator: $6,000 – $25,000
5. Annual Escalation
AVEVA Flex subscriptions typically include 5-8% annual price escalation. A $200,000/year subscription becomes $270,000 by year five with compound escalation. This is a significant long-term cost factor that many buyers underestimate.
AVEVA vs. Modern IIoT Platforms
The fundamental question for manufacturers evaluating AVEVA in 2026: do you need an enterprise industrial software platform, or do you need machine monitoring and analytics?
| Factor | AVEVA | Purpose-Built IIoT (e.g., MachineCDN) |
|---|---|---|
| Annual Cost (50-machine plant) | $100,000 – $300,000 | $12,000 – $60,000 |
| Infrastructure Required | Windows servers, SQL Server | None (cloud-native) |
| Deployment Time | 3-12 months | Days |
| IT Resources Required | 1-2 dedicated administrators | Zero |
| PLC Connectivity | OPC server required | Direct (Ethernet/IP, Modbus) |
| Predictive Maintenance | Additional AI/ML add-on | Built-in, AI-powered |
| Multi-Site | Separate installations per site | Single platform, all sites |
| Mobile Access | Extra licensing | Included |
| Historian Included | Separate product/license | Included in platform |
| OEE Monitoring | MES required ($$$) | Native feature |
| Tag Limits | Pay per tag tier | Unlimited |
| Time to Value | 6-18 months | 5 weeks |
The cost differential is striking. For a mid-market manufacturer who needs to monitor equipment, track OEE, and predict failures, AVEVA's total cost of ownership can be 5-20x higher than a cloud-native IIoT platform — while delivering a slower time to value.
Who Should Still Choose AVEVA?
AVEVA makes sense in specific scenarios:
Existing AVEVA Installations
If your plant already runs InTouch and Historian, and your team has AVEVA expertise, incremental expansion within the AVEVA ecosystem may be more efficient than deploying a new platform — at least for the SCADA/HMI layer.
However, even AVEVA shops should consider deploying cloud IIoT alongside AVEVA for analytics, predictive maintenance, and multi-site visibility — capabilities where AVEVA's traditional products lag behind purpose-built IIoT platforms.
Process Control Requirements
AVEVA's strength is deep integration with process control. If you need tight coupling between HMI, historian, and PLC control logic — the kind of integration required for continuous process manufacturing (chemicals, refining, power generation) — AVEVA's integrated stack delivers value that monitoring-only platforms don't.
Enterprise Mandates
Some large enterprises have standardized on AVEVA across all facilities. If corporate IT dictates the software stack, the decision is made for you. But even in these environments, MachineCDN can deploy alongside AVEVA (reading from the same PLCs) to provide capabilities that AVEVA doesn't offer: predictive maintenance, cellular connectivity, and 3-minute deployment.
Regulatory Requirements
Certain regulated industries (nuclear, pharmaceutical, certain chemical processes) require validated SCADA systems with specific certifications. AVEVA's long history of regulatory compliance in these industries is a genuine advantage.
The AVEVA to IIoT Migration Path
For manufacturers spending $100K+ annually on AVEVA and questioning the value:
Step 1: Audit Your AVEVA Usage
What are you actually using? Many plants pay for System Platform licenses but only use InTouch as a standalone HMI. You may be over-licensed.
Step 2: Deploy IIoT in Parallel
Install MachineCDN alongside AVEVA. It reads from the same PLCs — no conflict, no interference. Run both systems for 4-8 weeks and compare:
- Which platform do operators prefer for daily monitoring?
- Which gives maintenance better predictive insights?
- Which provides better multi-site visibility?
Step 3: Evaluate AVEVA Renewal
When your next AVEVA renewal comes up (with its annual escalation), you'll have real data on what you actually need. Many manufacturers find they can:
- Reduce AVEVA licensing by 30-60% (keeping it for HMI/control only)
- Shift analytics, historian, and predictive maintenance to the IIoT platform
- Eliminate server infrastructure costs as AVEVA footprint shrinks
Step 4: Long-Term Architecture
Over 2-3 years, migrate toward a simplified architecture:
- PLCs for machine control (unchanged)
- Cloud IIoT for monitoring, analytics, and predictive maintenance
- AVEVA retained only for safety-critical HMI screens (if needed)
This hybrid approach captures the best of both worlds while dramatically reducing cost and complexity.
The Bottom Line
AVEVA is expensive, complex, and slow to deploy — but it's also deeply entrenched in manufacturing and genuinely capable for process control applications. The question isn't "AVEVA or IIoT?" — it's "what do I need AVEVA for, and what should I do with a purpose-built IIoT platform instead?"
For monitoring, analytics, predictive maintenance, fleet management, and mobile access, cloud-native IIoT platforms deliver more value at a fraction of the cost. For real-time process control, AVEVA still has a role.
Ready to see the difference? Book a demo with MachineCDN and experience what 3-minute deployment and AI-powered predictive maintenance look like — no servers, no SQL licenses, no annual escalation.