AVEVA PI System
Connect process history, alarms and events with batch and lab records.
Put this connection to work Set up AVEVA PI System in the docs
Compare the process history around this batch exception.
Agree the records and transfer direction for this job, then connect the evidence to the work your team needs to review.
AVEVA PI System
Process history review
- Time-aligned readings, events and batch references
- Missing or unmatched information
- Next steps for your team to review
What’s connected.
Connect AVEVA PI System (formerly OSIsoft PI) using Seal's IoT App via OPC HDA/UA interfaces or custom SDK/API integrations. Ingest time-series process data, batch context, alarms, and events into Seal. Link critical process parameters to batch records (EBR), quality events, or LIMS results for enhanced traceability and compliance reporting.
Connection setup and permissions
Connect through Seal’s IoT app or a scoped integration. The instrument model, software version and available interfaces determine the connection method.
Before it goes live.
Access and write-back
Reading records and writing back are separate decisions. Define which records are in scope, whose permissions apply and which changes require 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.