Skip to main content

Integration guideHistorian gateway

Aspen InfoPlus.21

Bring InfoPlus.21 process history 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.

Aspen InfoPlus.21 to SealHistorian gateway

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

1What’s connected.

Bring InfoPlus.21 process history 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 flags with site IT 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

2Read InfoPlus.21 history by record, with its quality status.

Route

AspenTech lists OPC, ODBC, COM and REST services among InfoPlus.21’s standard interfaces.⁠¹ Its ports article lists Aspen SQLplus on ports 10014 and 50014, an OPC DA server that uses DCOM, and OPC UA servers whose ports are set in a configuration file.⁠² An AspenTech article gives SQLplus queries that export a tag’s history to a .txt or .csv file, the kind of export Seal Edge can collect.⁠³

Record identity

In that query, history is selected by record name from IP_AnalogDef and returned as IP_TREND_TIME, IP_TREND_QSTATUS and IP_TREND_VALUE: a time, a quality status and a value for each reading.⁠³ AspenTech’s SQLplus example reads a record’s units from its ip_eng_units field.⁠⁴

History

An IP_AnalogDef record has three history repeat areas, each configured on its own, and Best Fit values are a separate history held in the repository named by IP_BF_REPOSITORY.⁠⁵

When it fails

A query returns no data and no error
If a SQLplus BETWEEN range puts the later time first, the query raises no error and returns no data.⁠⁵ Check that each window starts before it ends before reporting a gap.
A read returns part of the window
When a disk history read error occurs, some but not all of the requested history may be returned.⁠⁵ Compare the readings received with the window requested, and mark the capture incomplete rather than filing it.
Other users wait while a query runs
Each database transaction, read or write, locks the whole InfoPlus.21 database while it runs.⁠⁴ Keep reads to the agreed tags and windows, and schedule large exports with site IT.

Check one record

Export one tag’s history for a completed batch window with SQLplus and attach it in Seal. Every reading should keep its IP_TREND_TIME, IP_TREND_QSTATUS and value, the units should match the record’s ip_eng_units, and the first and last times should fall inside the window requested.

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. 1AspenTech: Aspen InfoPlus.21.
  2. 2AspenTech: InfoPlus.21 ports and services.
  3. 3AspenTech: export tag history with SQLplus.
  4. 4AspenTech: SQLplus record queries and database locking.
  5. 5AspenTech: IP_AnalogDef history repositories.