About the configuration subsystem

Configuration data is information about elements that make up the AVEVA Historian, such as tag definitions, I/O Server definitions, and storage locations for historical data files. Configuration data is relatively static and does not change frequently during normal plant operation. The Configuration subsystem stores and manages configuration data.

Setting up the required databases and included entities (such as tables, stored procedures, and views) to support a typical factory environment would take countless hours. However, when you install the Historian, all of these entities are defined for you, allowing you to quickly start using AVEVA Historian.

Configuration data is stored in SQL Server tables in the Runtime database. If you are already using InTouch HMI software, you can easily import much of this information from existing InTouch applications, thus preserving your engineering investment. If you are using Application Server, much of the AVEVA Historian configuration is handled automatically by Application Server. You can also use the Operations Control Management Console to manually add definitions and configure the system. You can make bulk modifications to your Historian configuration or migrate the configuration from one Historian to another using the AVEVA Historian Database Export/Import Utility.

You can reconfigure the system at any time with no interruption in the acquisition, storage, and retrieval of unaffected tags. Configuration data can be stored with a complete revision history.