Main purpose of the monitoring database is to provide data for reports. It can also be used by 3rd party applications to get detailed monitoring data with historical values.

Monitoring database stores information about the kiln:

·kiln campaigns;

·refractory brick zones and brick zone replacement history;

·kiln shell drilling and repairs.

Monitoring database stores measurements from every kiln rotation:

·revolution time;

·active alarms;

·min/max/average temperature for every alarm zone;

·min/max/average temperature and thickness for every brick zone;

·analysis objects' measurements;

·tire slip values;

·burning zone temperatures.

Database internal structure is described here.

When monitoring database is updated

To reduce the amount of stored data (and also to speed up report generation) measurements from several kiln revolutions are combined together:

1.IRT KilnMonitor accumulates measurements from several successive kiln revolutions for 5 minutes. After that IRT KilnMonitor combines accumulated measurements into one record and writes it into the database.

2.If a measured value does not change much, it is saved to the database less frequently (every 15 minutes).

3.Active alarms are accumulated and saved to the database every 5 minutes.

Application INI file Linescano.ini contains the update periods and parameters that define what is a significant measurement change and what is not (REVSDB section).

Creating monitoring database

Monitoring database is created automatically when monitoring is started for the first time. If IRT KilnMonitor is upgraded from an older version that did not have any monitoring database, monitoring database will be filled with data taken from the kiln history,

During data import IRT KilnMonitor may ask you to link a historical brick zone installation date with a kiln campaign. This is necessary to do because older versions of IRT KilnMonitor did not support kiln campaigns.

Rebuilding monitoring database

It is possible to rebuild monitoring database, overwriting the existing one. This possibility should be used in the following situations:

1.There is a problem: you get errors/warnings related to the monitoring database during kiln monitoring.

2.If you just upgraded from an older version of IRT KilnMonitor which did not have monitoring database and want to relink campaigns and brick zones installation dates.

In other situations rebuilding the database is not recommended because detailed monitoring data is lost: a monitoring database contains information about every kiln rotation and alarm, while a kiln history saves data according to a storage plan.

To rebuild the database use main menu System | Rebuild Monitoring Database on the Start-up screen.