Processing flow of the aggregation function
The aggregation process using Summary Actions will be carried out in the following order ① to ④.
① Event occurrence
The aggregation process of summary actions is triggered by the same event processing timing as the logging function. When an event occurs, if it is determined that the time when the event occurred is the time when aggregation should be performed, aggregation will be performed automatically. There are three types of events: "Periodic event", "Scheduled event", and "Tag event".
|
|
Logging will be performed at the specified interval from the start of online operation. |
|
|
Logging is performed at a fixed time. Logging can be performed every minute or every hour. |
|
|
Logging is done by evaluating a tag value. |
② Data collection
When a summary action is executed due to an event, it collects the data required for logging (as agreed with logging by the logging function).
③ Save route log
Route logs (historical data) will be saved (agreement with logging via the logging function).
④ Saving the aggregate log
After the root log is saved, if it is determined that it is time to perform the aggregation process, the aggregation will be performed. The aggregation results will be saved as aggregation log data according to the definitions in the aggregation log section of the Summary Master. The order in which the aggregation is performed will be the order defined in the aggregation log section defined in the Summary Master.