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

Historians: Specialization

This article provides a starter solutions related to obtaining data from a historian, adding context, and modeling the payload on demand via the Intelligence Hub REST Data Server.

What Does This Article Cover?

HighByte Intelligence Hub can be used to create a solution that obtains process values from a historian software, applies context, and makes a modeled payload available to an external system on demand.  There are many variations for this type of solution and the scenario described in this article obtains maintenance order context from SAP and current process values from AVEVA PI System Data Archive for a given unique asset. 

specialization

 

Solution Assumptions  

The following summarizes the assumptions related to the example solution.

  • The solution requires unique identifiers for multiple systems to be mapped.  These associations were made in a PostgreSQL database table. 
  • Maintenance order header information is obtained from SAP per maintenance work center.
  • Average values of process values are obtained from AVEVA PI System Data Archive for specified PI Point Names and a date range.  In this simple example one value is returned per PI Point however an array or values could be associated to the order as well.
  • An external application request payloads from Intelligence Hub by providing a unique asset path and start and end times.
{
"assetPath": "site01/area01/line01/asset01",
"startTime": "2026-08-01T00:00:00.000Z",
"endTime": "2026-08-01T01:00:00.000Z"
}

 

Solution Summary 

The following summarizes the design of the example solution.

  • System unique identifier mappings are maintained in a PostgreSQL database table.  A Lookup Map is used to cache this data and enable queries without burdening the database management system.
  • Maintenance orders are obtained from SAP.  A Lookup Map is used to cache the orders and enable work center queries and avoid many frequent requests to SAP.
  • An Intelligence Hub Pipeline with an API trigger was used so that the data can be requested by an external system.
  • The PI Connection Point Type Input was used to obtain aggregated values for the given points and date range. 
  • An Intelligence Hub Model provides a structure payload.  The schema includes the unique asset path, maintenance order information and aggregated process values from PI.  
  • A project file may be downloaded [here].  

 

 

 

Additional Resources