Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ System Platform

Area and data storage relocation

  • Last UpdatedAug 12, 2025
  • 1 minute read

The System topology will evolve throughout the application's life cycle. As this evolution takes place, you must determine the data storage implications. The System Platform framework designed to be extremely flexible. It is very easy to move an entire area of objects from one AppEngine to another. But it is important to remember that the AppEngine defines where the historical data for hosted objects will be sent. If using multiple Historians, and the topology is modified, there may be an impact on the location of stored data.

When designing the system topology, note that the locations of the historical data clients may impact the end design. This is particularly true when portions of the application are separated by low bandwidth or intermittent network connectivity. Client applications should not be required to access the historian over these poor connections. One solution to this is to have local historians that service the computers that are locally situated with good network connections.

Related Links
TitleResults for “How to create a CRG?”Also Available in