Summary of "Aveva Changing Pricing?"
High-level summary
AVEVA’s HMI/SCADA and digital operations portfolio is shifting pricing, packaging, and go-to-market (GTM) to support cloud convergence, lower barriers to adoption, accelerate growth, and protect its installed base. The strategy centers on simplifying procurement with user-based subscriptions, offering a low-cost Starter option to capture early adopters, and prioritizing an interoperability layer (Connect) as the integration plane.
Context
- Portfolio: ~150 products (creates buyer confusion; need for clearer GTM messaging).
- Strategic intent: protect and grow the installed base while making AVEVA an attractive vendor for net-new customers.
- Core technical focus: interoperability and a common data model (Connect) that everything plugs into first.
Pricing & packaging
Three-tier “Ops Control” licensing model
-
Full edition
- Enterprise-wide (no site limit).
- No public price provided in the transcript.
-
Site edition
- User-based subscription.
- Market perception: ~$170–$180 per user/month.
- Typical 25-user minimum → roughly $50,000/year per site.
-
Starter edition
- Fixed architecture, lower entry price: ~ $25,000/year.
- Includes redundant object servers, historians, comms drivers (on-prem).
- Includes AVEVA Connect with 5 Connect users and unlimited tag streams up into Connect.
- Constrains architecture; expansions are purchased as nodes/servers.
Rationale and quoting benefits
- User-based subscription simplifies quoting versus node/server/architecture-based pricing.
- Removes need for complex architecture review at quote time.
- Allows architecture to change without reapproval of CAPEX.
- Starter fixed build lowers the entry cost and captures early adopters, with clear expansion paths.
Trials, developer access and strategic objective
- InTouch dev licensing was removed; InTouch runs fully functional for two hours without a license to enable hands-on evaluation.
- Result: InTouch grew ~25% year over year despite the loss of dev license revenue.
- Strategic objective: make subscription the preferred choice by giving users broad access per user and simplifying procurement.
Key metrics, KPIs and timelines
- Pricing KPIs:
- Target site economics: ≈ $50k/year for a 25-user Site edition.
- Starter target: ≈ $25k/year to lower entry barrier.
- Product adoption:
- InTouch growth: ~25% YoY after lowering dev friction.
- Market signals:
- Industry event growth: ~67 companies last year → >125 this year; >70% of attendees were end users.
- Time-to-value:
- Digital maturity cycles compressing: where transformation used to take 3–5 years, the target is now ~18–24 months using modern interoperability/architectures.
- Quote: “digital maturity cycles are compressing — where digital transformation used to take 3–5 years, the target is now ~18–24 months.”
Frameworks, processes and playbooks
Pricing and packaging playbook
- Move from architecture/node-based quotes to user-based subscription pricing to simplify sales and accelerate buying decisions.
- Offer a low-cost fixed Starter package to capture early adopters and provide a clear upgrade path to user-based subscriptions.
Go-to-market playbook
- Twofold GTM:
- Defend the installed base by reducing friction and offering integrated upgrade paths.
- Pivot to growth by making AVEVA attractive to new customers.
- Maintain partner/integrator programs, consignment/dev entitlements for system integrators to enable proof-of-concept builds.
- Messaging: focus conversations on business problems and outcomes rather than product features or pipeline metrics.
Product & architecture playbook
- Prioritize an interoperability layer/common data model (Connect) as the core integration plane.
- Start with business goals and metrics; choose the architecture to meet those goals (don’t start by asking for a Unified Namespace as an end in itself).
- Emphasize open standards (Sparkplug v4, i3x API) and device architectures that enable plugin/discovery/driverless integration.
Concrete examples, case studies and anecdotes
- Walker’s example: an engineer used distributor-provided dev licenses to build POCs inside plants and then sold the solution internally—demonstrates value of low-friction dev entitlements.
- InTouch change: removing dev licensing and enabling a 2-hour functional run materially increased adoption and revenue (InTouch +25% YoY).
- Starter package: practical lower entry point that includes core components and unlimited streams to Connect to convert smaller sites.
- Interoperability & M&A: vendors supporting i3x API / open interoperability are more attractive acquisition targets because they plug into larger ecosystems more easily.
- Meisterhub demo: built an MSQL connector in 21 minutes using cloud code—example of modern tooling and APIs speeding integrations (demo context).
Quick-win tactical recommendation for buyers
- Start by evaluating Connect (the integration plane) to understand how the suite fits together before choosing architectures or individual products.
Open standards & ecosystem plays
- Key standards:
- Sparkplug v4: topic/structure changes enabling improved data flows.
- i3x API: interoperability and ontologies enabling driverless discovery and plug-and-play integration.
- Combined potential: Sparkplug v4 + i3x can enable zero-configuration discovery (analogous to modern printer driver/plug-and-play experience).
- Strategic advice: vendors should support i3x and Sparkplug to ease customer integrations and increase attractiveness for M&A.
Organizational priorities & investment signals
- Invest where interoperability and developer friction reduction accelerate adoption; prioritize Connect and common data models.
- Product consolidation & marketing: clarify GTM so customers can see which subset of 150 products solves a specific business problem.
- Execution risk: many project failures stem from poorly defined business goals, not technology shortcomings.
Actionable recommendations
Vendors
- Embrace user-based subscription pricing with a clear lower-cost Starter option.
- Publish clear TCO comparisons and example business goals to help buyers compare subscription vs perpetual models.
- Adopt open interoperability standards (i3x, Sparkplug v4) to improve integrability and M&A value.
Integrators / partners
- Use consignment/dev entitlements or trial modes to let internal advocates prototype and demonstrate value.
- Position solutions around business outcomes rather than technology buzzwords (e.g., UNS).
Buyers (manufacturers)
- Start initiatives by defining measurable business goals; select architectures to meet those goals.
- Evaluate the integration plane (Connect or equivalent) first to understand how data will flow.
- Consider Starter packages to reduce entry cost and iterate to a full user-based subscription as needs grow.
Risks & tradeoffs
- Subscription TCO can be harder for buyers/accountants to calculate compared with perpetual license + maintenance; vendors must provide clarity and examples.
- Reducing developer friction (free/dev access) reduces short-term entitlement revenue but can increase adoption and long-term growth (InTouch example).
- Fixed-architecture Starter lowers entry barrier but may lock customers into constrained configurations unless expansion paths are clear.
Presenters and sources
- Walker D. Reynolds — host (Industry 4 Community Podcast)
- John Krajewski (John K) — Vice President of Product Management, AVEVA (HMI & SCADA / digital operations)
- Mentioned / referenced:
- Arland Nipper (Sparkplug advocate)
- Joe Stanzic (distributor anecdote)
- Meisterhub (demo)
- Inductive Automation
- i3x (interoperability API)
- Sparkplug v4
- Event/organizers/participants: Flow (Jeff Neper), Tanya, Travis, Matt
(End of summary.)
Category
Business
Share this summary
Is the summary off?
If you think the summary is inaccurate, you can reprocess it with the latest model.
Preparing reprocess...