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.
Emerson DeltaV
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 the current value or a completed period of history for a subscribed DeltaV parameter as a reference in Seal, through an IT-approved DeltaV Edge REST API gateway. Alarms, events and batch records are not included, and history readings do not carry per-reading quality or units.
Connection setup and permissions
Seal’s cloud service reads DeltaV Edge through an IT-approved REST API v1 gateway with a dedicated read-only profile. The control system stays on the site network. Lookup uses the exact subscribed parameter path; a partial name does not browse the hierarchy.
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. History readings do not include per-reading quality or units, and Seal does not infer them from the current value. The connection does not change setpoints, acknowledge alarms or operate equipment.
Set up Emerson DeltaV
- Have site IT provide a DeltaV Edge REST API v1 HTTPS gateway ending in /edge/api/v1 that Seal’s cloud can reach through public DNS with a trusted certificate. In Edge Manager, create a dedicated read-only profile marked Available.
- Open Settings → Integrations, find DeltaV and select Set up. Enter the gateway URL and the profile credentials.
- Enter a complete subscribed parameter path, such as SYSTEM/MODULE/BLOCK/PV, and choose a current capture or an ended UTC history window. Compare the readings and timestamps with Edge.
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.