Aveva API
Multiple real REST surfaces exist with public docs: on-prem PI Web API and the cloud CONNECT data services API with OAuth 2.0. Nothing is self-serve; you build against a customer's deployed PI System or a paid CONNECT tenant. Docs sprawl across OSIsoft, AVEVA, and Wonderware brandings.
Frequently asked questions
Aveva scores D on the API Report Card. Multiple real REST surfaces exist with public docs: on-prem PI Web API and the cloud CONNECT data services API with OAuth 2.0. Nothing is self-serve; you build against a customer's deployed PI System or a paid CONNECT tenant. Docs sprawl across OSIsoft, AVEVA, and Wonderware brandings.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
AVEVA is a Cambridge, UK-headquartered global industrial software company (LSE-listed until October 2023, when Schneider Electric completed its take-private at an enterprise value of ~£9.5B).
CMMS/Maintenance, broadly, industrial OT (operational technology) software for asset-intensive process and discrete industries: oil & gas (upstream, midstream, refining, petrochemicals), chemicals, power generation (thermal, nuclear, renewables), transmission & distribution utilities, water & wastewater, mining & metals, pulp & paper, food & beverage, pharma & life sciences, marine, infrastructure (rail, airports, smart cities), and EPCs (engineering, procurement, construction contractors). Control room operators use AVEVA System Platform, Plant SCADA, InTouch, and Edge HMIs to monitor and control plant equipment 24/7 with real-time alarm management, trend displays, and operator graphics.
Very high within industrial OT. AVEVA reports ~6,500 employees, ~5,500 partners, ~5,700 certified developers, and customers in 100+ countries.
AVEVA holds the canonical operational time-series and engineering data for a large share of the world's heavy industry: every analog tag (temperature, pressure, flow, level, vibration, current, voltage, pH, density, composition) sampled from PLCs, DCSs, smart sensors, and lab instruments at refineries, power plants, chemical complexes, mines, water treatment plants, pharma facilities, food plants, paper mills, and offshore platforms, stored in PI Data Archive and Wonderware Historian at sub-second resolution and multi-decade retention; every digital tag (valve position, motor run/stop, alarm state, batch step, equipment mode); every Asset Framework element, attribute, template, and analysis defining the plant's logical/physical model and KPIs; every alarm and event from the SCADA layer (System Platform, Plant SCADA, InTouch) with operator acknowledgements and shift annotations; every batch genealogy record (Batch Management, recipe, equipment used, operators, in-process tests, deviations) for ISA-88-compliant pharma, chemicals, and food production; every MES production order, work instruction, downtime event, OEE calculation, and quality record; every 3D engineering model, P&ID, isometric drawing, datasheet, equipment list, line list, and tag database from E3D / Engineering / Diagrams (frequently the as-built digital-twin record for assets worth $100M-$10B); every Asset Information Management bundle handed over from EPC to operator at plant commissioning; every preventive maintenance schedule, work order, and rounds-and-readings observation in AVEVA Work Tasks and Mobile Operator; every predictive-analytics anomaly score and failure prediction trained on the historian data; and every CONNECT-shared stream, namespace, and community that federates this data to partners (OEMs, EPCs, service providers), customers, regulators, and downstream analytics platforms.
Mixed. AVEVA itself dates to 1967 (originally CADCentre at Cambridge University) and shipped PDMS, the original 3D plant design system, in 1976; OSIsoft's PI System dates to 1980; Wonderware InTouch dates to 1987; Citect SCADA (now Plant SCADA) dates to 1973.
API access is gated behind a customer-deployed PI System or a paid CONNECT subscription, there is no self-serve developer sandbox open to anonymous developers, blocking horizontal multi-tenant integrators from building against AVEVA without per-customer onboarding. PI Web API authentication is split across Kerberos, Basic, Bearer (Windows Identity Service), and anonymous modes depending on customer deployment, with no consistent OAuth surface, each new customer integration requires negotiating the auth mode the customer has enabled. Full sourced list under Sources below.
Common alternatives include Siemens Digital Industries (WinCC, MindSphere/Insights Hub, Comos, Teamcenter), Rockwell Automation (FactoryTalk, FactoryTalk Optix, Plex), Honeywell Process Solutions (Experion, Forge, Uniformance), Emerson (Ovation, DeltaV, AspenTech IP.21, Plantweb), GE Digital / GE Vernova (Proficy iFIX, Proficy CIMPLICITY, Proficy Historian, APM), Hexagon AB (PPM, SmartPlant, j5). Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.
Yes. Supergood maintains an unofficial Aveva API and MCP server so AI agents and internal tools can read and write Aveva data. See the Aveva integration docs at supergood.ai/docs/aveva-api.