Skip to content
  • There are no suggestions because the search field is empty.

Reference Solution: AspenTech IP.21 Tag Value Changes for Narrow Table

This article captures the design considerations when obtaining tag value changes from IP.21 and creating a data payload for a narrow table.​

What Does This Article Cover?

An Intelligence Hub solution can be created to query AspenTech IP.21 using a rolling time window to obtain all tag value changes.  The solution can be configured to shape the data payload so that the values for all tags are written to the same values column.  The following describes how this solution can be created.

Design Assumptions

The following are some of the design considerations.

  • This design approach should be used when it is necessary to obtain all tag value changes.  ​
  • The Reference Solution's Connection Input caches data for performance considerations.  If tags are added or deleted in IP.21 the changes would not be reflected in the Intelligence Hub solution until the cache interval expires. 
  • The reference solution captures the IP.21 tag name.  The assumption is that the narrow table might be complemented by a table containing tag metadata like description, tag type and more.

Overall Solution Configuration​

The following describes the Intelligence Hub configuration objects.​

  • A Connection Input is used to obtain all in scope tag names from the IP.21 tag definition tables.
  • A Condition creates a comma separated string of all in scope tag names.
  • A second Connection Input contains a query that obtains all value changes for a parameterized date range filtered for the in-scope tag names.  
  • A Model is used to define the desired output schema.
  • A Pipeline is configured with the optimal polling frequency considering latency and performance.
  • The Pipeline calculates and maintains the state of the rolling date range.
  • The Pipeline obtains the values for the rolling data range and formats the desired payload.
  • A Write stage sends the payload to a Connection Output for the respective data store. ​​

Pipeline Configuration ​

The following describes the Intelligence Hub Pipeline design​.

  • Trigger the Pipeline considering latency and Pipeline performance.
  • Calculate the rolling date range and consider the required data format for IP.21.
  • Read the array of value changes from IP.21
  • Breakup the incoming array of data.
  • Map the payload to the desired schema using the Intelligence Hub Model.
  • Buffer transactions using a strategy that aligns with the solution requirements for latency.  It may be beneficial to buffer transactions for a cloud data warehouse, like Snowflake for example.
  • Consider the use of the Buffer Key​.
  • Create the desired file format ​for the data lake if applicable.
  • Write to the data lake configuring the desired file name format.

Other Considerations 

The following should be considered related to this design ​

  • The IP.21 Connection Input query should be capable of obtaining thousands of tag value changes.​
  • The tag's data type could be obtained from IP.21 and published to the target system using a second complementary data pipeline.

Solution Video

The following video captures a reference solution.

 

Additional Resources