DataHub Integrates to Multiple Historians

Store and Retrieve Data 

DataHub supports connections to a wide range of historian systems for storing of any of the many types of data that can be brought into DataHub including OPC DA, UA, A&E, A&C, MQTT, SQL databases, spreadsheets, DDE, and more.  By leveraging an external historian, you can then utilize any of the analytical, reporting, or graphing tools that are available for your chosen historian. 

• AVEVA PI Server, Historian, & Insight
• InfluxDB OSS, Enterprise and Cloud
• Amazon Kinesis
• Apache Kafka (V11+)
• Azure Event Hubs (V11+)
• OPC HDA (read/write client only) & conversion to OPC UA (V11+)
• ODBC (V11+)
• RESTful systems

DataHub also supports store and forward and when used with InfluxDB, secure tunneling of historical data is supported. 

Have questions? Ask an Expert

AVEVA PI System (formerly OSISoft PI)

PI system users have worked with our TOP Server and OmniServer products for many years. Now they can benefit from DataHub's ability to feed real-time data into the PI system using the PI Web API, a RESTful interface.

• Read/write access
• Rapid data throughput of up to 20,000 writes/second with millisecond time resolution
• Collect from any supported DataHub source
• Store & Forward capable
• Act as an OPC UA HDA server for PI data
• Combine with other DataHub features for robust solutions 

Amazon Kinesis

Stream any data you can get into DataHub to Amazon Kinesis in real-time to make it available for big data applications, analytics, dashboards, preventative maintenance, production planning and more. 

• Rapid data throughput of up to 50,000 writes/second with millisecond time resolution
• Collect from any supported DataHub source and write it to Kinesis
• Allows for data sampling - First, Last, Mean, Min, Max, Min & Max
• Store & Forward Capable
• Combine with other DataHub features for robust solutions 

Azure Event Hubs

Using the External Historian feature in DataHub, you can stream/write data to Azure Event Hubs. Flexible configuration options assure you can get any data that's in DataHub out to Azure Event Hubs. 

• Connection access policy definition
• Write to a specific partition if required 
• Producer count support if maintaining time order is critical for your application
• Flexible document definition for 1 to N points
• Adjustable message split count to optimize throughput
• Configurable Buffering 
• Optional configurable modification of point names
• Data Sampling to optimize writing to match receive rate capacity of destination

ODBC Connections

F0r some historians, their only or preferred way of access by third parties is via ODBC.  For those systems, starting with DataHub V11 and newer, you can use ODBC to integrate those historians.

Flexible configuration options include:

• Buffering with user configurable limits on amount of time to hold or number of point to hold before sending to database with option for no buffering
• Optional Read only connections
  
• Visual Editor for configurable database specific syntax / SQL commands with templates for PostgreSQL, Oracle, MySQL, & SQL Server
• Inserts can include multiple points in one command
• Configurable table and column mappings for point, value, quality, timestamp & row index for query & insert statements
• Optional configurable modification of point names
• Data Sampling to optimize writing to match receive rate capacity of destination

Licensing External Historian Connections

DataHub Historian connections can be added to any DataHub Solutions Pack or unique configuration of features. 

You can include the feature in a new license purchase or add it on later.  

When you license the Apache Kafka or Azure Event Hubs connector in DataHub you receive functionality for writing/sending data to those systems as External Historians, but also to receive data through the Event Streams connector.

For pricing, please request a quote. You can also request a consultation with a solutions architect to help you decide what you need.