Skip to main content

Integration guideHistorian gateway

AVEVA Historian (Wonderware)

Bring AVEVA Historian process data into batch and quality reviews.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

AVEVA Historian (Wonderware) to SealHistorian gateway

Seal reads
Agreed tags and time windows of process history
Writes back
No
Source of truth
AVEVA Historian (Wonderware)
Set up
Scoped with your team
Neil › Process history review
draft

Compare the process history around this batch exception.

Neil

  • 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.
Reads
Agreed tags and time windows of process history
Returns
  • Time-aligned readings, quality flags and batch references
  • Missing or unmatched information
  • Next steps for your team to review
Illustrative work with AVEVA Historian (Wonderware): a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Bring AVEVA Historian process data into batch and quality reviews in Seal through a scoped integration with the historian’s interfaces, or through exported files collected with Seal Edge. Agree the tags, time windows, units and quality handling before implementation.

Connection setup and permissions

Connect through Seal Edge or a scoped integration. The equipment model, software version and available interfaces determine the connection method.

Related blueprints

2Query AVEVA Historian with the retrieval mode written down.

Route

AVEVA Historian’s time-series data is queried through Microsoft SQL Server, which reaches data stored outside its database through OLE DB.⁠¹ The History table holds one row per stored tag value. The Live table holds one row per tag, updated as each value arrives, though data from store-and-forward or CSV import bypasses it.⁠²³ AVEVA also documents a Historian Data REST API, which returns more than 5,000 results in pages of up to 5,000.⁠⁴

Record identity

A History row is identified by TagName, unique within the Historian system, and DateTime: usually the acquisition time for delta retrieval, and the requested or calculated time for cyclic retrieval.⁠² By default, retrieval converts the stored UTC timestamps to the Historian computer’s local time, daylight saving included.⁠²

Units and quality

The wwUnit column gives the unit in use, and units are case-sensitive: ml is millilitres and ML megalitres.⁠²⁵ Each row carries a Quality indicator and, in OPCQuality, the quality received from the source. Under the GOOD quality rule, values of doubtful quality are left out of calculations.⁠²

Revisions

A stored value can be replaced by a later version while the original is kept, and a latest value with good quality comes back with QualityDetail 202.⁠⁶ After an outage, store-and-forward data reaches the Historian alongside real-time data, so it arrives late.⁠⁷ Retrieval defaults to CYCLIC for analog tables and DELTA for the History table, and interpolated retrieval estimates a value from the readings either side.⁠²⁸

When it fails

Times are an hour out
Local-time conversion, the default, follows daylight saving.⁠² Request UTC, and keep the time zone with every capture in Seal.
Fewer values than expected
In cycle-based modes the number of values returned is not always the cycle count, and delta storage writes a value only when it changes.⁠⁹¹⁰ Keep the retrieval mode with the capture, and do not read a missing row as a missing reading.
Units were not converted
If any requested unit conversion is invalid, none is performed.⁠² Check wwUnit on every row before comparing a value with its specification.

Check one record

Read one tag over an ended batch window in UTC with DELTA retrieval and attach it in Seal. Each row should keep its TagName, DateTime, value, wwUnit and quality, and a row with QualityDetail 202 should show as a revised value.

3Start with the job.

Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.

Discuss this connection →

4Before 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.

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.

Read the assurance detail →

References

  1. 1AVEVA Historian: querying through SQL Server.
  2. 2AVEVA Historian: History table.
  3. 3AVEVA Historian: Live table.
  4. 4AVEVA Historian: Historian Data REST API.
  5. 5AVEVA Historian: engineering units.
  6. 6AVEVA Historian: original and latest values.
  7. 7AVEVA Historian: store-and-forward.
  8. 8AVEVA Historian: interpolated retrieval.
  9. 9AVEVA Historian: cycle-based retrieval.
  10. 10AVEVA Historian: delta storage.