Two layer summary aggregation

The second layer summary aggregates KPI summary at the entity level. Both direct and indirect entity relationships are supported for two layer aggregation.

Currently, single layer of grouping attributes support busy hour and summary. In single layer of aggregation, if the lower entity, that is Cell uses time average aggregation, the focal entity, that is BSC, also uses time average aggregation. In two layer aggregation, the entity and focal entity can have different aggregations. For example Cell can use time average aggregation and BSC can use entity aggregation. Both layers need a defined summary. The first layer aggregation is based on the second layer summary table. The second layer aggregation is based on the raw traffic data.

Data availability for the second layer aggregation is based on the last successful run time and available date from the first layer summary. If the last successful run of the first layer summary is newer than second layer summary, the first layer summary data is refreshed and hence the second layer summary needs to refresh. The late data check during data availability lookup is only supported for simple summary table. Complex summary that composes of multiple fields or UDCs support only previous day recalculation.