Using History Transfer Objects
In large enterprise systems, it is often the case that data is archived in different data historians from different vendors in different locations. When undertaking data integration projects, it is necessary to be able to move large amounts of historical data from location to location or to be able to easily import data into a system so it can be accessed more easily. The correct management of these large data transfers is essential to avoid overloading networks and servers and to prevent the loss of any data due to interrupted connections or unprompted downtime of services.
system:inmation contains a whole suite of history transfer options that enable you to move, import and export large amounts of historical data with full control over scheduling and load management. With in built interfaces to most commercial data historians, large history transfer operations are available from one vendor historian to another with minimal configuration of connections. The different history transfer objects also make it easy to transfer data from an external system into system:inmation’s MongoDB repository or to export historical data to different file formats.
This Jumpstart is aimed at users who already have some experience with system:inmation and the different services and components available. It will be most useful for system administrators and power users who are engaged in planning or ongoing data integration projects that require connection to data historians and the transfer of historical data.
This Jumpstart will use the DemoData simulation items that are described in the Lua Scripting Jump Start as examples of tags with historized data to be transferred. The examples will transfer data from one system:inmation MongoDB repository into another system:inmation installation so it is useful to have a system (or test set up using virtual machines) that has installations on multiple machines.
If you have an existing data historian that you would like to connect to and transfer data from (Aspen or OSISoft PI for example), the examples can be tweaked to connect to these systems instead. The fundamentals of the history transfer operations remain the same regardless of the interface being used.