Compare the process history around this batch exception.
Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
AVEVA PI System
Process history review
- Time-aligned readings, quality flags and batch references
- Missing or unmatched information
- Next steps for your team to review
1What’s connected.
Capture a PI tag reading or a completed period of history as a reference in Seal through an IT-approved PI Web API gateway. Captures keep source timestamps, values, units and quality flags, and each history window is fixed, ended and no longer than seven days. AF assets and event frames are not included.
Connection setup and permissions
Seal’s cloud service reads PI through an IT-approved PI Web API gateway with a dedicated read-only account. The historian stays on the site network; an address reachable only from a site computer or VPN will not work.
Each capture is a bounded reference: a current value, or an ended UTC window of up to seven days and at most 1,000 recorded readings. It is not a continuous copy of the historian, and a failed read is not queued on site. The connection does not change setpoints, acknowledge alarms or operate equipment.
Set up AVEVA PI System
- Have site IT provide a PI Web API HTTPS gateway ending in /piwebapi that Seal’s cloud can reach through public DNS with a trusted certificate, and a dedicated read-only user.
- Open Settings → Integrations, find PI Historian and select Set up. Enter the gateway URL and the read-only credentials.
- Choose a Data Archive, search for tags and select a current capture or an ended UTC history window. Compare timestamps, units and quality flags with PI before sharing.
Related blueprints
2Connect in Seal.
Sign in to Seal and open Settings → Integrations. An organisation admin can review the connection and complete the guided setup.
3Before it goes live.
Access and any write-back
Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.