Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

Summary

DATS has by default an intermediate database meant for 3rd party integrations. It is based on the Aspen Tech IP21 SQL integration which is supported by many data historians. In the absence of a historian, the DATS SQL Integration Database can be queried directly using Microsoft SQL compliant tools.

Configuration

Big picture: DATS will map an Integration Source to an Integration Destination. Automated processed will pull data from Integration Sources and push them to the DATS SQL Integration Database for consumption.

The SQL Integration Database is usually called rdbms.

Notes:

  • If a sample is deleted or updated in DATS, it is not reconciled in the DATS SQL Integration Database

  • Values in the DATS SQL Integration Database are time series based

Integration Sources

To configure Integration Sources in DATS, we require the following information:

  1. The name of the Source

  2. The Sample Types we will be pulling data in from

  3. For a given combination of above, the names of the Tests

Integration Destinations

For a given Test as configured in the Integration Sources, we will set up an Integration Destination for it. For most 3rd party integrations, the destination is a table in the DATS SQL Integration Database hosted on the DATS database server.

The destination tables are named Tag#Data, where the # is an integer that increases as the number of destinations increase. The destination tables have two columns: TrendTime and TrendValue.

All of the destination tables are indexed in the TagsTable table in the DATS SQL Integration Database database. This is where they are described for human readability.

  • No labels