For this type of data storage, events are defined which are saved as binary information subsequently. The results will always be stored at the moment of their occurrence. If dynamic information like actual values, signal states or texts (technostrings, text signals) are configured with these results, the dynamic information at the moment of the result will also be saved.

For event based data, the aggregation will be achieved by the separation of static and dynamic parts in the data. The quantity of the dynamic data arise among other from the number of the used numeric and text fields as well as in the length of the underlying strings (when using text fields).

Examples for the storage space:

• Storage 24 h, cyclical every 1 sec an ingoing event (no outgoing events) with a message text length of 141 characters: 11.5 MB

• Storage 24 h, cyclical every 0.5 sec an ingoing event (no outgoing events) with a message text length of 141 characters: 23.5 MB

Compared to the time-based data, the event-based data need considerably less memory space. For the display of event-based HD data, the view "HD event table" is available in the ibaPDA client and in ibaQPanel.

The application ibaDatCoordinator offers the possibility to generate so called "offline events" and to store them retroactively in an existing HD event store. Different to the time and length-based recordings the events are configured and managed centrally on ibaHD-Server. Therefore, it is possible that multiple ibaPDA servers and ibaDatCoordinator as well write their events on the same event store.