Skip to main content

Integration guideHistorian gateway

GE Proficy Historian

Bring Proficy 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.

GE Proficy Historian to SealHistorian gateway

Seal reads
Agreed tags and time windows of process history
Writes back
No
Source of truth
GE Proficy Historian
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 GE Proficy Historian: a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Bring Proficy 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 Proficy Historian samples with their quality and mode.

Route

The Historian OLE DB provider lets clients query Historian data with SQL; used as a SQL Server linked server, it fetches the data when the query runs.⁠¹² Historian also provides REST APIs for archived data, and an OPC UA HDA server for OPC UA history clients.⁠³⁴

Record identity

The ihRawData table has one row per tag name and timestamp, and each sample carries a quality, a value and a timestamp.⁠⁵⁶ A semicolon is valid in a tag name, so it must be sent as %3B in a REST URI. The ihTags table holds each tag’s engineering units in EngUnits.⁠⁷⁸

Quality and sampling

Raw and current-value REST retrieval give each sample a quality of Good, Not Available, Uncertain or Bad; interpolated and Lab retrieval report the percentage of good samples instead.⁠⁶ Calculated is the default sampling mode in ihQuerySettings, while Lab sampling returns only collected values and never interpolates.⁠⁹¹⁰ Compression stores fewer samples than were collected, which is why interpolation is needed, and raw retrieval cannot return a discarded sample.⁠¹¹¹²

When it fails

A query stops short
The OLE DB provider truncates rows beyond its RowCount setting.⁠⁹ Compare the rows returned with the window, and raise RowCount or split the window.
A reading is blank
Historian tables do not support NULL: a blank space is returned where the server has no value.⁠¹³ Treat a blank as no reading, never as zero.
A tag cannot be found
An unencoded semicolon makes the web service split the tag name.⁠⁷ Encode every semicolon in a tag name as %3B.

Check one record

Query one tag in RawByTime for an ended batch window and attach the samples in Seal. Each should keep its timestamp, value and quality, the units should match EngUnits, and the row count should stay below RowCount, so nothing was cut off.

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. 1GE Vernova Historian: the OLE DB provider.
  2. 2GE Vernova Historian: SQL Server linked servers.
  3. 3GE Vernova Historian: REST APIs.
  4. 4GE Vernova Historian: OPC UA HDA server.
  5. 5GE Vernova Historian: ihRawData table.
  6. 6GE Vernova Historian: returned data fields.
  7. 7GE Vernova Historian: tag names parameter.
  8. 8GE Vernova Historian: ihTags table.
  9. 9GE Vernova Historian: ihQuerySettings table.
  10. 10GE Vernova Historian: Lab sampling mode.
  11. 11GE Vernova Historian: interpolation sampling modes.
  12. 12GE Vernova Historian: raw data sampling modes.
  13. 13GE Vernova Historian: database tables.