AVEVA CONNECT™ Integration Architecture
| Platform: | AvailableWebNot availableMobile |
|---|---|
| Plan Type: | Not availableBasicNot availableEssentialNot availablePremiumAvailableEnterprise |
| User Type: | Not availableRequesterNot availableFull UserAvailableAdministrator |
The AVEVA CONNECT integration reads stream data from your AVEVA CONNECT tenant over a secure, read-only connection. Your operational data already lives in AVEVA®'s cloud platform, so MaintainX® connects directly to AVEVA CONNECT on your behalf.
Unlike the Ignition®, Kepware®, and MQTT integrations, it doesn't need an on-premise agent or module in your network.
How It Connects​
When you set up a connector instance, MaintainX uses the client ID and client secret from your AVEVA CONNECT tenant to authenticate. It then polls your selected streams for new readings on a recurring schedule. For more information, see Data Freshness. MaintainX matches each new reading to its tag. After you map the tag to a meter, the reading is stored on that meter, where it can trigger automations and feed monitors that raise alerts.
Security​
Read-Only Access​
The AVEVA CONNECT integration operates in read-only mode. MaintainX receives stream readings from AVEVA CONNECT but never writes data or commands back to AVEVA CONNECT or any AVEVA product. Your AVEVA environment isn't affected by MaintainX connectivity.
Secure Outbound Communication​
MaintainX initiates every request to AVEVA CONNECT. Nothing needs to be installed on your network, and no inbound firewall changes are required on your side.
Secure Credential Storage​
Your client secret is stored encrypted and is only ever used to request short-lived access tokens from AVEVA CONNECT. Those access tokens are also cached encrypted and are never persisted in plain text.
Connection Health​
If AVEVA CONNECT rejects your credentials, for example because the client secret was rotated or revoked, MaintainX can't poll your streams. The connector instance's status changes to reflect the authentication failure.
You can't update credentials on an existing connector instance. To resume polling, create a new connector instance with current credentials. For more information, see Authentication Errors.
Data Freshness​
MaintainX polls each connector instance's selected streams approximately every 2 minutes. This cadence applies to all data currently in scope for this Beta. Backfilling gaps from an extended outage or bringing in historical data that predates the connection is planned for a future release.