📊 Understanding Data Aggregation in KYP Connect App
To provide accurate and fast reporting on the Organization Dashboard, the KYP Connect App aggregates collected data at two levels:
👤 User level
🏢 Unit level
This aggregation runs in the background and usually doesn’t impact the displayed data. However, in some edge cases, such as moving or deleting users, you may notice mismatches between user and unit totals.
This article explains those scenarios to help you analyze data more confidently.
🔁 How Aggregation Works
When data is sent by the KYP Connect App:
It is stored separately for both the user and their assigned unit.
This enables quick display and flexible reporting.
However, unit totals may not always match the sum of their users' data, especially when users are:
Moved to a different unit
Deleted
📋 Dashboards Affected by Aggregation
The following dashboards use the Parent Aggregate logic:
✅ Measurement Coverage
✅ Process Distribution
✅ Productivity Overview
✅ Headcount Coverage
✅ Process Resource Matrix
✅ Tool Use & Tool Use Aggregated
✅ Work Location
✅ Transaction Volume
✅ Passive Time Overview
🔄 Moving a User to a New Unit
When a user is moved from one unit to another:
🔸 Past data remains with the original unit.
🔸 The new unit starts receiving user data only from the moment of the change.
🔸 Data on dashboards like Headcount Coverage or Measurement Coverage will take up to 2 days to update, because of preloaded (latched) values.
📦 Example:
Assumption:
2 users (User 1 and User 2)
8 hours/day, 20 workdays/month
Initially both assigned to Unit A
On Jan 31, User 2 is moved to Unit B
View | Date Range | Unit A | User 1 | Unit B | User 2 |
|---|---|---|---|---|---|
🔍 Unit Summary | Jan 01 – Jan 31 | 320h | 160h | 0h | 160h |
🔍 Unit Summary | Feb 01 – Feb 28 | 160h | 160h | 160h | 160h |
🔍 Total | Jan 01 – Feb 28 | 480h | 320h | 160h | 320h |
❌ Deleting a User
When a user is deleted:
🟢 Their data remains visible under the unit they belonged to.
🔴 Their personal user data will be lost from the dashboards.
🔁 It can take up to 2 days for dashboards (like Headcount/Measurement Coverage) to fully update due to expected capacity values.
📦 Example:
Assumption:
2 users (User 1 and User 2)
Both worked Jan, User 2 deleted on Jan 31
View | Date Range | Unit A | User 1 |
|---|---|---|---|
🔍 Jan 01 – Jan 31 | 320h | 160h | |
🔍 Feb 01 – Feb 28 | 160h | 160h | |
🔍 Total | Jan 01 – Feb 28 | 480h | 320h |
🧠 Good to Know
📌 Exclude Out of Office (OOO) Might Not Work as Expected
If a user is moved or deleted, their Not-Measured Time might still appear in dashboards, even when the OOO toggle is enabled — because that time is still associated with the original unit.
📈 FTE Is Not Aggregated Yet
At the moment, FTE (Full-Time Equivalent) is still calculated based on user assignments. It’s not yet aggregated at the unit level, but this will be added in a future update.